Brad, the fact that the node was deleted overnight confirms James'
proposition, that the node down delete interval is related to the
configuration poll interval. A demandpoll and a configuration poll
are not the same thing. Your config poll interval is probably the
default, which is one day. If you examine the output of demandpoll
you will see that it includes the timestamp for the next configuration
poll for that node.
The design supposed that you do not want to do config polls too
frequently since they generate a fair amount of network traffic. The
expectation is that the node down delete interval will be longer than
the config poll interval - hence the defaults of 1 day and 1 week.
In real life, though, I find that customers generally delete things
manually
when they know they have been removed from the network. Otherwise
you are might well be masking a real network problem. So I don't
think automatic deletion is used too much. Anybody else?
So now, just to be nosey, let me ask what problem you are trying to
solve with this rapid deletion of down nodes? Maybe someone will
have a suggestion for an alternate solution.
Cordially,
Leslie A. Clark
IBM Global Services - Systems Mgmt & Networking
James,
Sorry about forgetting to include the subject and releases. NV 5.1.1 on an
AIX
4.2.1
It appears that the nodes will eventually get deleted but I don't
understand
what triggers it.
I've done a demand poll and the objects remain.
I've closed and re-opened the user interfaces - the objects remain.
I've done an ovstop / ovstart - the objects remain.
I've gone home and returned - the objects disappeared.
My goal is to find an easy way for Operations to remove remote offices that
have
been relocated. (Averages 20-30 offices / month. The new office is
typically
created using new addresses / names and then the old office equipment
recycled).
I've written a script that determines the objects that belong to an office
based on the router in the remote office. The script updates a collection
called
"Garbage" with the appropriate rules. I can have the map administrator
manually
remove these items, but it would be ideal for NetView to then delete these
objects based on the Node Down Interval. Using this technique, I can give
the
script to operations knowing the worst they can do is run it for an active
office and even then NetView isn't going to delete it unless the office is
actually down.
Brad Martin
MetLife
"James Shanks" <James_Shanks@TIVOLI.COM> on 11/10/99 05:17:06 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: Brad Martin/Bsg/MetLife/US)
Subject: Re: node down delete interval (was blank)
I'm not the netmon guy so I am just guessing. But my understanding is that
the
node down delete thing would only be checked when a config check was done.
Have
you tried demand polling the thing?
James Shanks
Tivoli (NetView for UNIX) L3 Support
Brad Martin <bmartin@METLIFE.COM> on 11/10/99 03:51:35 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:
If I understand the Node Down Delete Interval in the SNMP Configuration
Dialog
correctly, I should be able to create a collection that has a node down
delete
interval that is very short. For instance, I should be able to place a
router
that has been critical into a collection and then specify that nodes within
that
collection are to deleted if they've been down for more than 30 minutes.
However when I create a collection with one node that's critical and then
configure the SNMP node down interval to 5 minutes, nothing happens. Does
anyone
have an explanation?
Thanks,
Brad Martin
MetLife
|