Can you distinguish them based on this:
Some devices you discover with the seedfile and others you don't?
Some you discovery by the address nearest you, and some you don't?
You can have an entry in a big long seedfile, and netview can discover
the same device by another address before it gets to that entry in the
seedfile. Those may be processed differently. The subsequent merge
might cause this behavior. But forced rediscovery by a resolved address
usually clears it up.

Cordially,

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


danny AT UK.IBM DOT [email protected] on 10/10/2000 06:57:34 AM

Please respond to IBM NetView Discussion <nv-l AT tkg DOT com>

Sent by:  owner-nv-l AT tkg DOT com


To:   nv-l AT tkg DOT com
cc:
Subject:  [NV-L] Selection name is IP address not hostname





Hi All

We have a problem where some devices report their "Selection Name" as an IP
address instead of their hostname. We can not identify any differences
between devices that display their hostname as their Selection Name (good)
and those that display an IP address (bad).

We believe that all of the offending devices are routers.

Name resolution method is identical for good and bad nodes as is the IP
address type used in the seedfile.

Any ideas what would cause the Selection Name to be set to the IP address
instead of the hostname?

Cheers,

Danny Williams
ITS SB Tivoli
Certified AIX Specialist - (ATE, ASP + HACMP)
IBM Global Services
E-mail: danny AT uk.ibm DOT com
Tel: 665520 (01926-465520)
MOBX: 275520 (07967-275520)


_________________________________________________________________________
NV-L List information and Archives: http://www.tkg.com/nv-l