I used to see this more often, then I didn't for a while, and now I'm
seeing it again. I don't know for sure, but I suspect it might have to
do with timing. Maybe during a rush of discovery, name resolution
times out. The IP Hostname field gets updated later, but you are
stuck with the Selection Name. I usually find that if I later delete and
rediscovery those nodes, they get rediscovered with the hostname
as the Selection Name. Which makes lots of other things work better.
If you have the time, you might want to take this up with Support and
see if they can find any reason for it. It is a little annoying when you
try to do searches or autmation later on.
Cordially,
Leslie A. Clark
IBM Global Services - Systems Mgmt & Networking
Detroit
danny@UK.IBM.COM@tkg.com on 10/10/2000 06:57:34 AM
Please respond to IBM NetView Discussion <nv-l@tkg.com>
Sent by: owner-nv-l@tkg.com
To: nv-l@tkg.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@uk.ibm.com
Tel: 665520 (01926-465520)
MOBX: 275520 (07967-275520)
_________________________________________________________________________
NV-L List information and Archives: http://www.tkg.com/nv-l
|