To: | nv-l@lists.us.ibm.com |
---|---|
Subject: | Re: [nv-l] Events available inNetView |
From: | James Shanks <jshanks@us.ibm.com> |
Date: | Fri, 19 Dec 2003 12:12:28 -0500 |
Delivery-date: | Fri, 19 Dec 2003 17:17:47 +0000 |
Envelope-to: | nv-l-archive@lists.skills-1st.co.uk |
Reply-to: | nv-l@lists.us.ibm.com |
Sender: | owner-nv-l@lists.us.ibm.com |
Your questions would be easier to answer if you specified the specific trap ids when you talk about traps, so that we can be sure that we are all talking about the same traps. But basically you get Router Down, (58916971) as opposed to Node Down (58916865) when the node that has all it's interfaces down is a router, according to NetView's definition, rather than just a node. Look at the definition of the host in the object database with ovobjprint. It will say whether the device is a node or a router. The rest of your questions pertain to the netmon feature called RFI, or Router Fault Isolation. You should find the doc we ship on that and read it. Basically when RFI is enabled, then when netmon detects that all the interfaces which lead to a network are down, he will mark that network as unreachable, and stop trying to poll devices in it, and stop sending all the those individual Interface Down (58916867), and Node Down (58916865) events for the devices in that network. They instead become unreachable. Routers become unreachable when the networks they are connected to become unreachable and thus so do the router interfaces which connect to those networks. When the routers and router interfaces which caused the problem are back on line, the networks become reachable again. That trap is sent rather than the hundreds of others which indicate that everything else in the network is now back up. That's the gist of it. James Shanks Level 3 Support for Tivoli NetView for UNIX and Windows Tivoli Software / IBM Software Group
Hi Group members, NetView provides - besides many, many other Events - the following specific Events: * NVNDWN & NVNUP .................... Node down & up * NVIDWN & NVIUP ......................... Interface down & up * ROUTDOWN & ROUTERUP ......Router down & up * ROUTUNREACH ............................. Router unreachable * IUNREACH ......................................... Interface unreachable After reading the descriptions for these Events came up with some questions: * What's the difference between ROUTDOWN and NVNDWN ? (do NVDWN Events include Router down & Switch down Events ? Why are there additionally ROUTDOWN & ROUTERUP Events available ?) * There are only ROUTUNREACH & IUNREACH Events in the Event Configuration List and no "reachable" Events. Which "Clear" Alarms are generated when a Router/Interface is reachable again ? Thank you very much for any help that allows me to understand the meaning of the different Events. Cordially, Georg Gangl _____________________________ Ing. Georg Gangl Bundesrechenzentrum Ges.m.b.H. Hintere Zollamtsstrasse 4 A-1033 Wien Gruppe I-PS-NW Netzwerke Tel.: 00 43 (1) 711 23 - 3891 DW Fax.: 00 43 (1) 711 23 - 3897 DW mailto:Georg.Gangl@brz.gv.at -------------------------------------------------- |
<Prev in Thread] | Current Thread | [Next in Thread> |
---|---|---|
|
Previous by Date: | [nv-l] Sending events to TEC - hostname missing (sometimes), Bernard Disselborg |
---|---|
Next by Date: | Re: [nv-l] Events available inNetView, James Shanks |
Previous by Thread: | [nv-l] Events available inNetView, Georg Gangl |
Next by Thread: | Re: [nv-l] Events available inNetView, James Shanks |
Indexes: | [Date] [Thread] [Top] [All Lists] |
Archive operated by Skills 1st Ltd
See also: The NetView Web