nv-l
[Top] [All Lists]

Re: Problem found in 5.1.1

To: nv-l@lists.tivoli.com
Subject: Re: Problem found in 5.1.1
From: James Shanks <James_Shanks@TIVOLI.COM>
Date: Wed, 10 Mar 1999 08:56:27 -0500
Reply-to: Discussion of IBM NetView and POLYCENTER Manager on NetView <NV-L@UCSBVM.UCSB.EDU>
Sender: Discussion of IBM NetView and POLYCENTER Manager on NetView <NV-L@UCSBVM.UCSB.EDU>
As I explained, the problem is only in the first CD of 5.1.1

NetView V5.1 is unaffected by that problem (but by others or there would
not be a 5.1.1).

As long as you have a valid current maintenance contract you will be
autoshipped the next release, whatever it is, whenever that release is made
generally available.

James Shanks
Tivoli (NetView for UNIX) L3 Support



Jeanie Cham <yccham@NCS.COM.SG> on 03/10/99 05:12:32 AM

Please respond to Discussion of IBM NetView and POLYCENTER Manager on
      NetView <NV-L@UCSBVM.UCSB.EDU>

To:   NV-L@UCSBVM.UCSB.EDU
cc:    (bcc: James Shanks)
Subject:  Re: Problem found in 5.1.1





Does this problem apply to Netview 5.1?  Will customers who purchased
Netview
5.0 who have received an auto-shipment of Netview 5.1, receive yet another
auto-shipment of Netview 5.1.1?

cheers,
Jeanie

James Shanks wrote:

> If you have not yet installed the new NetView patch, 5.1.1, then please
> DON'T, until you get  a copy autoshipped, or at least until the current
> copies have been replaced at Software Distribution.
>
> If you have installed, 5.1.1 already, then with my sincerest apologies,
> please read on.
>
> We have found a major problem that was shipped in the NetView UNIX 5.1.1
> patch.
> The main symptom of the problem is that routers will not have the correct
> status.
> If an interface on a router changes status, the new status is not
> propagated.  If an interface
> is acknowledged, the router's status is not updated.  Lastly, if the
router
> is unmanaged and then managed, the status remains UNKNOWN (blue).  APAR
> IX88166 has been opened to address the problem and is now fixed.
>
> The problem was caused by the fix for APAR IX82669.  We have removed the
> code for IX82669 and are planning to reship 5.1.1 to manufacturing.
> However, some customers have already received 5.1.1, and may have already
> installed it.
>
> If you have already installed 5.1.1, then your  map database has probably
> already been
> erroneously updated to not propagate status for some routers.  Not all
> routers will have the problem.   There are several options at this point.
> But first, you  must  install the ovw_binary efix from the ftp server
> (IX88166.AIX.V511.tar.Z).  Solaris and Digital efixes will be available
by
> the end of the week (they take longer to build).
>
> Option 1:
>        The best way to  recover is to go to a backup database that was
> saved before 5.1.1 was installed.
>
> Option 2:
>        If you did not backup your databases,  you can use the NetView
> Configuration Utility to
>        regenerate  his maps (Control->Restart automatic  map generation).
> But,  WARNING: this   option will  cause all map customization to be
lost.
>
> Option 3:
>        The  last option is to  find all of the routers that have the
> incorrect status and change the Symbol  Status Source
> (Edit->Modify/Describe->Symbol) to Symbol.  Then change  the Symbol
Status
> Source back to Compound.  This process can be extremely time consuming.
>
> We understand that none of these options is easy and that they all put a
> burden on you,
> the customer.  For that you have our sincerest apologies.  But other than
> try to institute procedures to insure that this kind of oversight ( a
major
> bug of this sort getting through the
> release verification process) there is little we can do at this point.
We
> are sorry.  And we have begun meeting to put a stricter review process in
> place.
>
> Note: If you have 5.1.1 and have not installed it, you  can either wait
for
> the new 5.1.1 CD or install the 5.1.1 image that you already have and
apply
> the efix BEFORE starting the GUI.  We suggest you  wait for the new CD.
>
> This means, of course, we will have two different versions of 5.1.1 in
the
> field.  If a you experience an ovw_binary problem, it will be important
to
> know which version you are  running.  To do that, do the
>   ls -l /usr/OV/bin/ovw_binary
>  command.  If the date on this ovw_binary is Jan 29, it is the ovw_binary
> from the first 5.1.1 CD, and must be replaced.  If the date is Mar 9, it
is
> from the efix or the new CD.
>
> Please feel free to post  any questions/concerns you may have about this.
>
> Regretfully
>
> James Shanks
> Tivoli (NetView for UNIX) L3 Support

<Prev in Thread] Current Thread [Next in Thread>

Archive operated by Skills 1st Ltd

See also: The NetView Web