You won't get a Node down unless ALL the interfaces on that Node are down.
Since one is administratively down and this progates as if it were normal (so
that the node is not perpetually yellow) , you will never get anything but a
Node marginal event for this device (though this will change in V6). So you
will have to look for Node Marginal, rather than Node Down events for this node
and others like it.
James Shanks
Tivoli (NetView for UNIX) L3 Support
Patrick McNeil <patrick_mcneil@yahoo.com> on 01/19/2000 12:29:14 PM
Please respond to patrick_mcneil@yahoo.com
To: NV-L@UCSBVM.UCSB.EDU
cc: (bcc: James Shanks/Tivoli Systems)
Subject: Node Down Event Generation
I have run into an interesting situation. I have several sites that go down
on a regular basis. I have event rules setup to correlate the Interface
down to interface up and interface down to node down, thus accomplishing
sending only a single page for each of the devices.
The problem I am having is that a node down event is not sent for some of
the sites (however a node up is sent). I was wondering what actually
generates a node down event?
I have looked at these sites and they all have the following configuration:
1 Serial connection (in 2 of the sites they have about 5 serial)
2 Ethernet connections (1 administratively down)
1 loop back address.
What I was wondering is since the administratively down interface never
sends an interface down message (since it was already down), does a node
down message not get generated?
Since there are only a few (about 12) sites like this now, I can modify the
rules to accommodate this for now, but I would like a different fix if it is
available.
My net view system is still only running 5.1.1 if that makes a difference.
We will soon be upgrading to the 5.1.2 version.
Patrick
|