Re: [NV-L] Switch getting red (down) all the time.

["José Gomes" <zeca011@gmail.com>]

Francois, thanks for the help.

 

Unfortunately (or not...) when I use the community string shown by xnmsnmpconf in the snmpwalk command I do NOT get a timeout. Isn't it strange???

 

Any other idea??

 

Thanks.

 

On 08/01/07, Francois Le Hir <flehir@ca.ibm.com> wrote:

The issue is that netview doesn't get an snmp response using the community string it knows for that device and using the ip address it selected ( 172.21.12.1).

you can try the following:

xnmsnmpconf -res 6509cpd
to find out what snmp information netview knows about the device. If the community string is wrong, then you need to update it in xnmsnmpconf or add it in communityname.conf to let netview discover it.

snmpwalk -c <community string as found in previous step> 172.21.12.1 system
if you get an answer (and not a timeout) then everything should work fine ...
if you get a timeout, maybe 172.21.12.1 is not an interface able to answer you. You can fix it to something else using '=' in the netmon seed file.

Salutations, / Regards,

Francois Le Hir
Network Projects & Consulting Services
IBM Global Technology Services

"José Gomes" < zeca011@gmail.com>

"José Gomes" <zeca011@gmail.com>
Sent by: nv-l-bounces@lists.ca.ibm.com

01/08/2007 09:16 AM

Please respond to
Tivoli NetView Discussions <nv-l@lists.ca.ibm.com >

To	nv-l@lists.ca.ibm.com
cc
Subject	[NV-L] Switch getting red (down) all the time.

Hi all,

First, sorry about the post. I know there are many posts related to
the same subject but the fact is that I could not solve my problem by
applying the solutions proposed on any of them.

Well, we have Netview 7.1.4 running on a Linux machine. I started
working with it just a few months ago but, at least in this period,
almost everything ever worked very very well. The only exception is
the status of a cisco 6509 switch, that remains down (red) on Netview
all the time. When I try a ping, its status changes to marginal but a
little bit after it turns down again.

As I said, I've read many posts about this topic. As far as I
understood, it must be a snmp status test problem, since the ping
works fine but snmp test do not. One thing which I think that
corroborates this thesis is the output of a quicktest, which gives:

Title: Quicktest
Name or IP Address: 6509cpd
Poll Results
11:15:31 ***** Starting Quick Test of node 6509cpd *****
11:15:31 Interface 172.21.26.1(Vlan525) (down since 12/31/05 13:36:07)
11:15:31 Interface 172.21.255.1(Loopback0) (down since 12/22/06 16:45:58)
11:15:31 Interface 172.21.255.5(Loopback1) (down since 12/31/05 13:36:07)
11:15:31 Interface 172.23.1.1(Vlan900) (down since 12/22/06 16:46:12)
11:15:31 Interface 192.168.253.2(Vlan107) (down since 01/05/07 14:54:01)
11:15:31 Interface 172.21.1.35(Vlan2) (down since 12/31/05 13:36:07)
11:15:31 Interface 0.0.0.0(swcpd:5:swd5:6) (down since 01/19/38 00:14:07)
11:15:31 Interface 0.0.0.0(swcpd:6:swd5:5) (down since 01/19/38 00:14:07)
11:15:31 Current Polling parameters
11:15:31 The next SNMP Status Poll is scheduled for 01/08/07 11:15:30.
11:15:31   Get number of interfaces
11:15:43 SNMP request timed out (172.21.12.1)
11:15:43 ***** End of Quick Test for node 6509cpd *****

Could this SNMP time out be my problem? How could I solve it?

Let me say that when I try MIB browsing at this switch everything goes
OK. Isn't it strange???

Thanks in advance,
Bruno.

_______________________________________________
NV-L mailing list
NV-L@lists.ca.ibm.com
Unsubscribe:NV-L-leave@lists.ca.ibm.com
http://lists.ca.ibm.com/mailman/listinfo/nv-l  (Browser access limited to internal IBM'ers only)

_______________________________________________
NV-L mailing list
NV-L@lists.ca.ibm.com
Unsubscribe:NV-L-leave@lists.ca.ibm.com
http://lists.ca.ibm.com/mailman/listinfo/nv-l (Browser access limited to internal IBM'ers only)

_______________________________________________
NV-L mailing list
NV-L@lists.ca.ibm.com
Unsubscribe:NV-L-leave@lists.ca.ibm.com
http://lists.ca.ibm.com/mailman/listinfo/nv-l (Browser access limited to 
internal IBM'ers only)