nv-l
[Top] [All Lists]

RE: [nv-l] hostname changed

To: nv-l@lists.us.ibm.com
Subject: RE: [nv-l] hostname changed
From: "Stringfellow, William" <William.Stringfellow@bankofamerica.com>
Date: Tue, 13 Apr 2004 16:14:30 -0700
Delivery-date: Wed, 14 Apr 2004 00:23:34 +0100
Envelope-to: nv-l-archive@lists.skills-1st.co.uk
Reply-to: nv-l@lists.us.ibm.com
Sender: owner-nv-l@lists.us.ibm.com
Thread-index: AcQhnsvxeDQNucwVRwag7NmvDCvSywADe0Gg
Thread-topic: [nv-l] hostname changed
Maybe you can get your network administrators to implement separate read only and read/write access lists on the routers and not include NetView on the read/write list.  Then it doesn't make any difference what you do with NetView.
 
    Regards,
        Bill
 

Bill Stringfellow
EDS - Bank of America Account Team
Network Management Support
CA4-704-02-03
2000 Clayton Road, Building D
Concord, CA 94520

Office:     925.692.7283
Fax:        925.675.1763
Email:     william.stringfellow@eds.com
Cell:       925.765.2648

-----Original Message-----
From: owner-nv-l@lists.us.ibm.com [mailto:owner-nv-l@lists.us.ibm.com]On Behalf Of Leslie Clark
Sent: Tuesday, April 13, 2004 2:30 PM
To: nv-l@lists.us.ibm.com
Subject: RE: [nv-l] hostname changed


As a 'best practice' tip in this subject, I make it a practice to code the defualt 'set' community in Netview (in the xnmsnmpconf dialog) to something bad like 'badCommunity'. This is to prevent all users of the Motif interface from having access without knowing the community.

If someone tries to use the mib browser to do a set, and the default configured in Netview is valid, then the set will work.  If you don't code a default 'set' community in xnmsnmpconf, it tries the read community. Sometimes that is correct. I code it to something else just to be sure.

Cordially,

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



James Shanks/Raleigh/IBM@IBMUS
Sent by: owner-nv-l@lists.us.ibm.com

04/13/2004 11:53 AM
Please respond to
nv-l

To
nv-l@lists.us.ibm.com
cc
Subject
RE: [nv-l] hostname changed






You can do it as an operator, but NetView, that is, netmon does not do it by itself.  Let's get clear about that.


And as I indicated, there are several ways that a smart Cisco administrator can disable this function altogether, and should.


James Shanks
Level 3 Support  for Tivoli NetView for UNIX and Windows
Tivoli Software / IBM Software Group


"Federico Vidal" <fvidal@tecsystem.com.ar>
Sent by: owner-nv-l@lists.us.ibm.com

04/13/2004 02:55 PM
Please respond to
nv-l

To
<nv-l@lists.us.ibm.com>
cc
Subject
RE: [nv-l] hostname changed







Jean-Michel,

Yes, you can do it by SNMP.
Just verify that the SNMP agent on the device you want to change the hostname is configured correctly to allow Netview to change the Hostname (sysName).

The SNMP variable that holds the hostname is mib-2.system.sysName.0 .
The SNMP Agent must have configured a RW community (and allow the Netview IP to access the agent).
Netview must use this community name to issue a set request on the MIB variable of the device.

Regards,

Federico Vidal
IBM Certified Deployment Professional
Tecsystem S.R.L.
e-mail: fvidal@tecsystem.com.ar
Tel: (5411)-4704-6667 ext. 109




-----Mensaje original-----
De: TURATI, JEAN-MICHEL [mailto:JEAN-MICHEL.TURATI@disney.com]
Enviado el: Tuesday, April 13, 2004 12:04 PM
Para: nv-l@lists.us.ibm.com
Asunto: [nv-l] hostname changed



Can Netview change a device's hostname on its own ? I don't mean in the
Netview database or on the map but on the device itself.
Network administrators believe Netview changes hostname in running config of
some Cisco devices. I am rather doubtful.

Jean-Michel TURATI
Euro Disney SCA  Bâtiment Genie
BP 100  77777 Marne la Vallée Cedex 4
Tél: +(33).1.64.74.32.86 Fax: +(33).1.64.74.40.03




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

Archive operated by Skills 1st Ltd

See also: The NetView Web