Well, as I recall -
The Node Down delete is done by netmon which means that reverse address
resolution must be working. Normally, netmon would not add a device he
could not resolve so this problem does not arise but with loadhosts you in
effect said "I know better" and forced a database add of an admittedly
bogus node. Now netmon cannot resolve it to prove to itself that it is in
fact down (because that's when nodes get deleted -- after they have been
down for a specified length of time). And it would have had to have been
"up" for some period of time if memory serves me to qualify for the delete
as well. But don't quote me on that. I don't work on netmon and
everything I know is second-hand.
Other than deleting this node from the GUI I don't know how you can get
rid of it gracefully.
James Shanks
Tivoli (NetView for UNIX) L3 Support
Jeff Fitzwater <jfitz@PRINCETON.EDU> on 05/17/99 04:40:30 PM
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/Tivoli Systems)
Subject: Auto Delete of Node Down ???
Any ideas on this???
Netview 5.1 with good 5.1.1 patch.
Since there is no cammand-line way to remove a host, I thought I would
investigate the SNMP config parameter of "Node Down Delete Interval".
YES it does delete nodes when the time expires and you can set this for
default or host specific values via GUI.
It does however appear that if the host is not DNS resolvable for some
reason (The reverse lookup is not set) and the host is down when it was
created, then it will never get removed when the timer expires.
We do have some host that we ping in other countries that do not have
reverse name resolution set up.
I did a simple test by creating a host via the "LOADHOSTS" command using
a bogus IP with bogus name and it would not get deleted.
Q. Is this the way it works or is it a bug?
Thanks for any help.
Jeff Fitzwater
Princeton University
|