I am almost positive you have a netmon bug here. The key is the object
number 60387 with a selection name of 0. Then after that the objects that
are messed up have a selection name of one off of their object number. This
is EXACTLY what we saw with those Sentinal devices. CALL SUPPORT.
-----Original Message-----
From: Francois Le Hir/Quebec/IBM [mailto:flehir@ca.ibm.com]
Sent: Wednesday, October 31, 2001 9:54 AM
To: nv-l@tkg.com
Subject: [NV-L] RE: ovwdb filling up with objects
I get a lot of "stange" entries with ovobjprint -s
How should I interperet entries like:
273 "netview:en2" This is
our netview server
272 "netview:en0283" ?
271 "netview:en0282" ?
270 "netview:en0281" ?
252 "netview:en0"
253 "netview"
250 "Selection Name250"
249 "Selection Name"
2881 "mapdb"
2882 "CollectionRootObject"
1019369
"Interface:192.84.100.11053770"
1023411 "01023410"
1054042 "nveventsObj"
761190 "Selection Name761190"
759219 "Selection Name759219"
730035 "0730034"
581798 "0581797"
465328 "0465327"
402401 "0402400"
60387 "0"
.....
Thanks,
Regards,
Francois Le Hir
Network Projects & Consulting Services
IBM Global Services
Phone: (514) 205 6695 Pager: (514) 854 5709
>Date: Mon, 29 Oct 2001 15:38:41 -0500
>From: "Leslie Clark" <lclark@us.ibm.com>
>Subject: RE: ovwdb filling up with objects
>You can dump a nice list of the objects with
> ovobjprint -s > obj.list
>This puts them in the order they were created in (object
>id). It is sometimes useful to sort them on the selection
>name, so you can see what objects are getting multiples
>made for them.
>
>Cordially,
>
>Leslie A. Clark
>IBM Global Services - Systems Mgmt & Networking
>Detroit
|