nv-l
[Top] [All Lists]

RE: Object Label

To: nv-l@lists.tivoli.com
Subject: RE: Object Label
From: "Leslie Clark" <lclark@us.ibm.com>
Date: Sun, 24 Jun 2001 14:40:20 -0400
Let me add a wrinkle here to Don's very good advice (I do it that way at
almost
every customer site): If you change the name of the device by updating name
resolution, and the label of the router changes to that new name, you still
will see
that the interface cards have Selection Names of OldNodeName:ifDescr. This
is
because the name change does not trickle down.  You have to delete those
interfaces and rediscover them for them to get the new Selection Name
(which
will be NewNodeName:ifDescr). Either delete the node and rediscover, or
delete
the interface cards (not all at once) and demandpoll.

Either way, the Label of the interface will be the IP Address, or the
ifDescr, depending
on what the device reports and how you have ipmap configured.

Cordially,

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


"Davis, Donald" <donald.davis@firstcitizens.com>@tkg.com on 06/22/2001
02:15:07 PM

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:  RE: [NV-L] Object Label




The  Interface LABEL will never display anything other that the IP Address
of that  interface.
The  event log will display the resolved name of the Router (not
interface) if  it can be resolved.
If  your DNS has different names for each interface on a router (as Cisco
Systems  suggests) then you MUST prevent NetView from
using  DNS for those IP Addresses. You will end up with multiple routers
where only one should be drawn.
DNS  overrides NetView's logic as to what interfaces belong to a particular
device.

My  recommendation is:
If you have multiple names for the same router in DNS, fix your  DNS.
Get  those "unique interface names" out of there or NetView will be
severely  confused.
Do not  allow NetView to use a DNS for those routers!
Override it as I previously suggested with /etc/hosts and
/etc/netsvc.conf.

If you  do not or cannot (politics) manage your DNS, then this is your only
solution.
Example etc/hosts file:

10.1.1.1  ciscoXYZ    #  Main IP  Address
10.2.1.1  ciscoXYZ    #   Serial2/0
10.3.1.1  ciscoXYZ    #   Serial2/1
10.4.1.1  ciscoXYZ    #  FastEthernet0/0
10.5.1.1   ciscoXYZ    #  FastEthernet1/0
10.6.1.1   ciscoXYZ    #  FastEthernet3/0

Note that every interface on router ciscoXYZ resolves  to the same hostname
!!! This is VERY important !!!

James, Feel free to jump in here...  :)

Don Davis


-----Original Message-----
From: Stamper, Steve  [mailto:Steve_Stamper@foremost.com]
Sent: Friday, June 22, 2001  12:54 PM
To: 'IBM NetView Discussion'
Subject: RE: [NV-L]  Object Label


Ya  but....  What if you have specific interfaces with labels in the  DNS?
How can you get the interface to pickup the Name and not the IP  Address?



Thanks² - Steve Stamper

-----Original Message-----
From: Davis, Donald  [mailto:donald.davis@firstcitizens.com]
Sent: Friday, June 22,  2001 11:11 AM
To: 'IBM NetView Discussion'
Subject: RE:  [NV-L] Object Label


Santosh,
Placing an entry in /etc/hosts will cause NetView to update the  selection
name when the node is demand (or configuration)  polled.
When you demand poll the node after putting the sysname in  /etc/host, you
should see "New name found ...." in the output  window.
The label of the node will change to this new name. The label of the
interface itself will Always be the IP Address.
I  have been told that the label change may not happen immediately,
depending  how busy NetView is doing other things.

This entry in /etc/hosts will cause the  SelectionName and thus the label
to be updated with  "SuperXyzRouter".
/etc/hosts
10.2.3.123     SuperXyzRouter   #  Comment

Be  certain that you have an /etc/netsvc.conf file and it is configured
like  this:

/etc/netsvc.conf
hosts=local,bind4

(The number after bind is the version of bind that you are  running.)
If  you have not configured /etc/resolv.conf for a nameserver, the
netsvs.conf  file is not needed.
This will cause the OS to check /etc/hosts before going to  DNS.

Don Davis


-----Original Message-----
From: z_esm_karekars  [mailto:z_esm_karekars@bharatpetroleum.com]
Sent: Friday, June  22, 2001 4:00 AM
To: 'IBM NetView Discussion'
Subject:  RE: [NV-L] Object Label



Hi Don,

Can U please be little clear on this, I  could enter the Interface IP
addresses in /etc/hosts file locally ( Infact  I had done it earlier but
could not work on that more that time. I tried  demand poll after I did the
same which did not helped me) How will the  interface pickup the Name from
hosts file then, please advice.

Regards,
Santosh

   ----------
   From:   Davis,  Donald[SMTP:donald.davis@firstcitizens.com]
   Reply To:        IBM NetView Discussion
   Sent:   Thursday, June 21, 2001 7:47 PM
   To:     'IBM  NetView Discussion'
   Subject:        RE: [NV-L] Object Label

   Santosh,
   NetView does NOT do this natively (like  HP OpenView does). NetView uses
   only the resolved name.
   The workaround is to write a script that  does an SNMPGET for the
   sysName and writes it to /etc/hosts so that  NetView can resolve to that
   insted of the DNS name. You will need to  modify /etc/netsvcs.conf so
   that local comes before bind.


   Don  Davis

     -----Original Message-----
     From: z_esm_karekars [mailto:z_esm_karekars@bharatpetroleum.com]
     Sent: Thursday, June 21,  2001 9:59 AM
     To: 'nv-l@tkg.com'
     Subject: [NV-L] Object Label


     Hi,

     I had Netview 6.0.1 on AIX  4.3.3.

     How can the Router Interfaces pick up the  System Description
     "RouterName:I/FName" in place of IP address which  comes by default.

     It's very very urgent.

     Regards,
     Santosh

   
------------------------------------------------------------------------------


   This electronic mail and any files transmitted with  it are confidential
   and are intended solely for the use of individual or  entity to whom
   they are addressed. If you are not the intended recipient  or the person
   responsible for delivering the electronic mail to the  intended
   recipient, be advised that you have received this electronic  mail in
   error and that any use, dissemination, forwarding, printing, or  copying
   of this electronic mail is strictly prohibited. If you have  received
   this electronic mail in error, please immediately notify the  sender by
   return mail.

   
============================================================================== 


<Prev in Thread] Current Thread [Next in Thread>

Archive operated by Skills 1st Ltd

See also: The NetView Web