Netview pays no attention whatever the system names as defined in the internal
snmp configuration of the box. It relies entirely on name resolution of the
addresses. I believe what you were changing were the labels, which is usually
not worth the effort.
.I find this very frustrating, since we have a few machines
with multiple interfaces for different purposes, but only
refer to them by their internal name.
And this is the usual case. What you call the 'internal name' is what should be
DNS or in /etc/hosts for ALL of the ip addresses that are configured in the box.
In /etc/hosts you put in an entry for each address, and you put the SAME name
next to each of them. Delete and rediscover the device or box, and Netview
will rediscover it, label it with that name, and add all interfaces underneath
Note that for Netview to realize that these addresses are on the same device
it is best if the device has snmp enabled, and it has ipforwarding turned on.
even in the absence of this, Netview will make a guess based on the name
resolution and draw the device as a 'router', ie something with more than one
interface, and promote it to the top level of the map (IP Internet level
If your DNS is returning different names for each interface, you can override
in the /etc/hosts in the Netview box. Make a file /etc/netsvc.conf and put in it
and AIX will resolve the names using the hosts file before checking DNS.
Note: SP nodes often are configured without snmp enabled and without
ipforwarding enabled; the nodes then show up as separate hosts, all at
the lowest level of the map heirarch (segment level submap). If you think of
them as all the same system, you could just put all of the addresses in the
hosts file with the same name. Or talk to your DNS guys about reverse-lookup.
Leslie A. Clark
IBM Global Services - Systems Mgmt & Networking
(248) 552-4968 Voicemail, Fax, Pager
---------------------- Forwarded by Leslie Clark/Southfield/IBM on 08/29/99
11:30 AM ---------------------------
Sean Aaron <sean.aaron AT UCOP DOT EDU> on 08/27/99 08:49:43 PM
Please respond to Discussion of IBM NetView and POLYCENTER Manager on NetView
<NV-L AT UCSBVM.UCSB DOT EDU>
To: NV-L AT UCSBVM.UCSB DOT EDU
Subject: how to edit the ovobjdb?
I've just installed Tivoli Netview 5.1.1 on a host in our IBM SP frame
and when discovery was done the other nodes in the frame were identified
by the names on the frame interface and not for their network
I've already completely deleted the object representing the SP network,
and changed the object names of the symbols and their remaining
interfaces to the hostname on the external interface, but when I create
a collection that has these nodes in it, their symbols always show up
with the internal interface name.
Doing an ovobjprint|grep spf shows that two fields retain the original
name: 11 and 224 which are IP Name and IP Hostname, respectively.
These two fields appear to be defined in the IP Map "object" and cannot
be changed through the GUI...at least not so far as I can see.
I've had similar problems with other machines where Netview seems to
arbitrarily assign the name of the object/symbol based on one of the
interfaces and not on the machine's internal hostname...I find this very
frustrating, since we have a few machines with multiple interfaces for
different purposes, but only refer to them by their internal name. In
the case of a Sun I've had this problem with, I cannot change the object
name at all...I get told that it already exists, and I can find the
entries for the hostname in the ovobjdb, but there is no object I can
locate in the gui with this name...very strange.
I'd rather not have to rename symbols every time I create a new
collection, and I can't believe that there is no way to assign
object/symbol name based on machine hostname.
The easy solution would be to do a global replacement in the database,
but I can't find any way to do that in documentation or in the
faq/knowledgebase at the Tivoli support site.
Any pointers would be greatly appreciated.
Running Netview 5.1.1 on an IBM RS6000 SP node model 9076 with AIX 4.3
in a mixed AIX/Solaris/MVS/VM/NT environment.
UNIX System Administrator
University of California
Office of the President