nv-l
[Top] [All Lists]

Re: [nv-l] Status propagation

To: nv-l@lists.tivoli.com
Subject: Re: [nv-l] Status propagation
From: Stephen Hochstetler <shochste@us.ibm.com>
Date: Fri, 29 Aug 2003 11:59:25 -0500
Delivered-to: mailing list nv-l@lists.tivoli.com
Delivery-date: Fri, 29 Aug 2003 17:59:56 +0100
Envelope-to: nv-l-archive@lists.skills-1st.co.uk
List-help: <mailto:nv-l-help@lists.tivoli.com>
List-post: <mailto:nv-l@lists.tivoli.com>
List-subscribe: <mailto:nv-l-subscribe@lists.tivoli.com>
List-unsubscribe: <mailto:nv-l-unsubscribe@lists.tivoli.com>
Mailing-list: contact nv-l-help@lists.tivoli.com; run by ezmlm



Brian,

There are sometimes some very valid reasons for something to show up as
red, when it is actually up.    Some investigation will help you resolve
those.   First, start with the NetView product documentation.   It is
actually better than many other technical products.

Do you have a whole router showing red, or only some interfaces under that
router?    Work at the interface level to get all of those green first.
For Discovery, NetView must be able to ping one interface of a router, and
read the SNMP information of that router to discover all the other
interfaces.    However, if NetView cannot ping an interface, it turns it
red.    You say the interface is up..ok.   Now, from NetView, can you ping
that interface IP address?    If you can and it is red, then try to
"Unmanage" that interface and then "Manage" the interface.   It should now
be green.     If you cannot ping that interface from NetView, but the
interface is up, then you may have an IP routing problem between NetView
and the device.   You need to resolve that at which point the interface
should return to green. (after the next polling, which is usually in 5 min)

If you can ping an interface, but it stays Red after unmanage/manage, then
you probably want to call the IBM support desk for their help.

--------------------------
Also, verify that you still have SNMP access to the router in question,
from NetView.    NetView would have it initially to discover the device.
But if someone reconfigured the community string in the device, NetView may
no longer be able to see configuration changes in that device.   This
leaves interfaces in the NetView screens that no longer exist.   If that IP
address got moved over to another router it would make it pingable again.
But Netview would reflect the IP address in the wrong router.


Stephen Hochstetler              shochste@us.ibm.com
International Technical Support Organization at IBM
Office - 512-838-6198 (t/l 678)       FAX - 512-838-6931
http://www.redbooks.ibm.com


---------------------------------------------------------------------
To unsubscribe, e-mail: nv-l-unsubscribe@lists.tivoli.com
For additional commands, e-mail: nv-l-help@lists.tivoli.com

*NOTE*
This is not an Offical Tivoli Support forum. If you need immediate
assistance from Tivoli please call the IBM Tivoli Software Group
help line at 1-800-TIVOLI8(848-6548)


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

Archive operated by Skills 1st Ltd

See also: The NetView Web