I believe what you are seeing is that the Selection Name for the node
changed,
but the Selection Name for the interface cards did not change. That is not
a
problem for basic Netview function, but may cause you a problem if you have
made Smartsets/Collections based on interface names, or have scripts that
use nvUtil or nvdbformat or nvdbimport that depend on the names of the
interface card. The only I know to do about that is to delete and
rediscover
the node (or just the interfaces) . The names on the interface cards are
manufactured at discovery time and not revisited. If you are ambitious you
could report it to Support and maybe they will take it as a defect to fix
some day.
Cordially,
Leslie A. Clark
IBM Global Services - Systems Mgmt & Networking
Detroit
Peter Cho <chop@tdbank.ca>@tkg.com on 08/15/2000 11:09:41 AM
Please respond to IBM NetView Discussion <nv-l@tkg.com>
Sent by: owner-nv-l@tkg.com
To: IBM NetView Discussion <nv-l@tkg.com>
cc:
Subject: [NV-L] DNS name change of routers/switches
We're planning to make a large number of DNS name changes to
routers and switches to follow a standard. After changing a switch name as
a test, I see that NetView picks up the new name and the map appears
correct. Using "Locate ==> Objects" from the map, I can find the
device using the old name and new name.
Can this cause problems down the road? Is there a way to cleanup the
database? or do we have to delete and add again?
Thanks. Peter.
_________________________________________________________________________
NV-L List information and Archives: http://www.tkg.com/nv-l
|