RE: [nv-l] netmon and SNMP communities

["Barr, Scott" <Scott_Barr@csgsystems.com>]

Ah, my bad. I mis-understood.

 

Obviously, the alternate community names file needs to contain the additional community name. (sounds like you did that)

 

Is the "-h" parameter turned on in netmon? I am not sure that makes a difference during discovery.

-----Original Message-----
From: owner-nv-l@lists.us.ibm.com [mailto:owner-nv-l@lists.us.ibm.com]On Behalf Of Federico Vidal
Sent: Wednesday, November 26, 2003 10:09 AM
To: nv-l@lists.us.ibm.com
Subject: RE: [nv-l] netmon and SNMP communities

Scott:

 

First of all, thanks.

I did as you told me to and got the netmon.trace, but it only shows the community used with already discovered nodes... The thing is that, because of my seed file (!@oid  0), no nodes with communities other than the default were discovered, which are the ones I try to poll AND discover.

-----Mensaje original-----
De: Barr, Scott [mailto:Scott_Barr@csgsystems.com]
Enviado el: Miércoles, 26 de Noviembre de 2003 11:57 a.m.
Para: nv-l@lists.us.ibm.com
Asunto: RE: [nv-l] netmon and SNMP communities

During times of problem - use the netmon -a 175 command and look in /usr/OV/log/netmon.trace to see if the community name is different than the one reported in xnmsnmpconf. Thats the bug Leslie is referring to.

-----Original Message-----
From: owner-nv-l@lists.us.ibm.com [mailto:owner-nv-l@lists.us.ibm.com]On Behalf Of Leslie Clark
Sent: Wednesday, November 26, 2003 8:42 AM
To: nv-l@lists.us.ibm.com
Subject: Re: [nv-l] netmon and SNMP communities

Do you have maintenance on this 7.1.3? There were problems with communities that were fixed.

Cordially,

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

"Federico Vidal" <fvidal@tecsystem.com.ar> Sent by: owner-nv-l@lists.us.ibm.com 11/26/2003 12:16 PM Please respond to nv-l

To:        "Nv-L (E-mail)" <nv-l@lists.us.ibm.com>         cc:                 Subject:        [nv-l] netmon and SNMP communities

Hello List:

I have a customer with Netview 7.1.3 on Linux who tries to discover his network with it. The thing is that, having a seed file that only discovers SNMP devices ( !@oid 0 ), he can't discover any device beside the ones using the default community. Any device that has another SNMP community different than the default, can't be discovered.

I will give full details: Looking into the matter, i found that the SNMP configuration (xnmsnmpconf) is correct because I can manually poll these devices using snmpwalk without specifying community. I found that netmon is the one who is using wrong communities to poll because the cisco agents in the network keep telling that netview causes authentication failure, thus netview doesnt discover any device due to the seed file.

This is very strange to me, because i thought that the netview engine used the same snmp configuration that CLI commands.

Another detail is that before this problem occurred, my customer changed the netview's IP address, so I ran reset_ci to solve the apparent problem but nothing happenned....

What could be happening???? My last resort is to deinstall but I would like to solve this issue as a Netview supporter.

Thanks in advance.

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