|
Hints are deleted by ovtopofix -A.
If I'm not mistaken, netmon reads the entire seedfile during its startup process before doing anything else. It adds "hints" (in the ObjectDB) for every seed entry that isn't already discovered. So I'm "guessing" that after all the hints have been created, there isn't further need for those entries to be kept in the seedfile, regardless of whether or not the device has been discovered yet. netmon will then attempt to discover those hints while also performing all of its other duties such as status polling, daily config checks, and servicing other requests such as demandpoll, but I don't think it needs to refer back to the seedfile after that, and since the seed entries are in the ObjectDB as hints, you can most likely even restart netmon and it still wouldn't need to see those same list of entries in the seedfile. Anyway have any comments on this ? Becki, look for hints in the ObjectDB (using ovobjprint |grep <blah>) for your seed entries (that have not yet been discovered) to check this theory ..... Gareth
i had thought about having little seedfiles, in fact, that is what we were initially doing but because there's no "okay, I'm done" message in netview, I'm never certain when to swap out to the next one. From: nv-l-bounces@lists.ca.ibm.com [mailto:nv-l-bounces@lists.ca.ibm.com] On Behalf Of Gareth Holl Sent: Friday, May 25, 2007 4:33 PM To: Tivoli NetView Discussions Subject: Re: [NV-L] How big can a seedfile be One thing you could try is to take the IPs of a small group of devices that aren't being discovered and add them to a new seedfile. Then temporarily configure netmon to use that seedfile and see what happens. May want to copy all your entries that have polling/processing directives as well, just for good measure. I'm not really sure what is or isn't standard practise for the majority of customers, but I'd say that a "best practise" could be to remove entries from the "active" seedfile that have already been discovered (no need to seed them anymore). You can always keep a master copy of a seedfile that has every single IP you would like to store in a seedfile for some other later use. The only entries you need to keep in an active seedfile are those with "directives" such as HSRP (%) or SNMP Status polling ($) or the locking of the SNMP Address (=), etc. All other entries can be removed once discovered. Cheers, Gareth
Ford had a PMR opened in 2003 to ask that question and the answer was pretty big, as I recall. However I think it is possible that the problem is that when you specify every address, then at startup netmon is going to check on every address whether it exists or not. I think I would enable tracing on netmon, then watch netmon.trace when you do a netmon -y. It posts a message when it is done loading that includes the word "sucessfully". Try putting a misspelled node name at the end and see if the reload calls it out. If you ping the address you are looking for (from the commandline) and grep it in netmon.trace, you will see if netmon is getting around to trying to add it or is trying but giving up for some other reason. It's just not how it was intended to be used, so it is not optimized for it. As for the link business, I just tried it and it worked fine. Moved a seedfile to somewhere else, and added a link where it was, and did a netmon -y. The resulting message in netmon.trace says it was loaded successfully. Cordially, Leslie A. Clark IT Services Specialist, Network Mgmt Information Technology Services Americas IBM Global Services (248) 552-4968 Voicemail, Fax, Pager
What is the limit, if there is one, on the size of a seedfile? Right now, mine is huge: -rw-rw---- 1 bkain1 bkain1 16783342 May 23 19:07 seedfile (this is on suse linux 9) And it seems like the addresses that were
added at the end are not getting discovered, yet I can snmp walk them.
And can the seedfile a link, as specified in netmon.lrf, or does
that have to be the actual file listed? Thanks_______________________________________________ _______________________________________________ NV-L mailing list NV-L@lists.ca.ibm.com Unsubscribe:NV-L-leave@lists.ca.ibm.com http://lists.ca.ibm.com/mailman/listinfo/nv-l (Browser access limited to internal IBM'ers only) |
