..."having about 2 Maps opened in read-write mode"...?
My understanding is you can have JUST ONE r/w-map.
And collections checking IP-Status are accurate just on this one and only
read-only-maps have to be refreshed to be accurate!
Solution: Create "static" collections (isRouter, isWhatever, vendor, ...)
to get the "live"-status on both r/w- AND r/o-maps.
iT-AUSTRIA / OE2100 / TK-NET
Tel (mobil) 0664 1908469
Tel (iT-A) 21717 58948
FAX (iT-A) 21717 58979
Mailto:Ralph.Schiffinger AT erstebank DOT at
Von: Stephan Schwalb [SMTP:sschwalb AT DEBIS DOT DE]
Gesendet am: Dienstag, 15. Juni 1999 11:50
An: NV-L AT UCSBVM.ucsb DOT edu; Schiffinger Ralph 2100
Betreff: collection update problem
we like to know if somebody experienced the same problem in the past:
Running NV 5.1.1 on AIX 4.2.1 with ~1000 routers (15000 objects),
having about 2 Maps opened in read-write mode.
We sometimes have the phenomenon that some of our collection doesn't
provide any changes on the GUI. These collections are checking the
ip-status (isNode=true && IPstatus=critical). After restarting NV,
collections are working well, but after some time collections run into
getting rid of nodes beeing IPstatus=normal (green) and collecting new
having switched to IPstatus=critical.
So our Nodes_Down Collection shows up friendly colored with nobody
having any use of it anymore. The database like the ip-map keep on the
actual status and also if querying the collection through CLI (nvUtil)
gives the right status back.
The only way to handle this is to delete/recreate the collection (only
solution as the problem comes back soon) or restore old database.
Mit freundlichen Gruessen / With kind regards / Saludos
Systems engineer - Networkmanagement
debis - Systemhaus
Tel.: +49 (711)-17-49971
Fax : +49 (711)-17-49663
email: sschwalb AT dbmail.debis DOT de or sschwalb AT debis DOT de