Deleting and letting NetView automatically readd the collection "egg" fixed the problem.

Thanks for the help.

-----Original Message-----
From: Leslie Clark [mailto:lclark AT US.IBM DOT COM]
Sent: Tuesday, March 23, 1999 10:24 PM
To: NV-L AT UCSBVM.ucsb DOT edu
Subject: Re: Wrong bitmap in collection

Is this a new discovery of the network? Usually this is something you see
when you are first
discovering. The nvcold daemon often notices new devices before the rest if
Netview is
done with them. So they will have the correct bitmap in the IP Internet
submaps, but
the generic one in the Collection. Nvcold has no mechanism for re-checking
symbols.

If that's your situation, then deleting the collection egg and letting it
re-evaluate clears it up.
When I say delete, I mean you Edit..Delete the 'egg' , not its contents or
its definition. It
reappears, you open it, and things look better.

There are other, more troublesome causes for similar symptoms, but if you
have not tried
this, do this first.

Cordially,

Leslie A. Clark
IBM Global Services - Systems Mgmt & Networking

What would cause the wrong bitmap to be displayed for an object in a
collection?

I've got about 30 objects that appear in a collection as the generic
non-snmp supported box, but ipmap shows up as the correct bitmap. I can
demandpoll the object in the collection and see than snmp does function
properly. I know everything if fine in my oid_to_type because ipmap
displays
the object properly.

I'm running NV v5.1 on AIX v4.2.1.

________________________________________
Thanks,
Sean Davidson

Sr. Network Systems Engineer
Publix Super Markets, Inc.
P.O. Box 32015
Lakeland, Fl. 33802-2015
Email - sean.davidson AT publix DOT com
Voice - (941) 686-8754 x6889
Fax - (941)616-5659

 <<...>>