nv-l
[Top] [All Lists]

RE: [nv-l] Object Turn Red after Ping

To: <nv-l@lists.us.ibm.com>
Subject: RE: [nv-l] Object Turn Red after Ping
From: "Barr, Scott" <Scott_Barr@csgsystems.com>
Date: Fri, 5 Nov 2004 14:42:43 -0600
Delivery-date: Fri, 05 Nov 2004 20:43:51 +0000
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: AcTDdkNMakpt79MtQzq54ZN/fM2ahQAAIywQ
Thread-topic: [nv-l] Object Turn Red after Ping

I have managed to have this problem several times. This is how it happened to me:

 

  1. Put a Solaris box in my seed file with SNMP polling forced.
  2. Do not specify a community string in xnmsmpconf (this is the mistake)
  3. Discover the box using netmon –y
  4. Short time later, box shows up in discovery – red
  5. Ping the box – green
  6. Short time later box turns red again

 

This occurred for me, because the Solaris sub-agent will respond to an SNMPWALK with public community string (mind you, it’s not a valid response, but it’s enough to get NETMON to acknowledge it’s discovered. Since we always force our boxes to be SNMP managed, and since xnmsnmpconf is not configured, I am using SNMP polling, but SNMP is not actually working. I can see this also occurring if I had the SNMP address in xnmsnmpconf wrong (due to a host file or dns error for the interface I discovered not being the actual interface I’m polling. Therefore I may be specifying the wrong community string, and thus an snmp timeout occurs) At this point, I ping the box it turns green and when the next status poll occurs (snmp status poll) it fails and turns the box back red.

 

Not sure how you would have done this on a router, but it can be done by even by the best of us.

 

 

 


From: owner-nv-l@lists.us.ibm.com [mailto:owner-nv-l@lists.us.ibm.com] On Behalf Of free lancer
Sent: Friday, November 05, 2004 2:29 PM
To: nv-l@lists.us.ibm.com
Subject: Re: [nv-l] Object Turn Red after Ping

 

Mark,

I checked snmpwalk on interface as well as ip.. and they seem very fine.. This is a router basically going up and down..now may be as you said i need to check the snmp version on other end if it's faulty..

thanks,

Larry

Mark Sklenarik <marksk@us.ibm.com> wrote:


Hi Larry,
What you are describing sound like a something we have experienced with fault snmp agent,  SNMPv3 agents or Red Hat 3.0  snmp agents.
This may occur when NetView is configured to perform status checking using SNMP, but the snmp agent is not responding even thought you can ping the NIC.  Also, check to make sure you can snmpwalk both the "ip" and "interface" MIB tables on the agent.  
NetView 7.1.3 FP3 works best went communicating with a SNMPv1 agent.  
In the case of Red Hat 3.0 we found that the agent (net-snmp) had a problem with indexing between the "interface" and "ip" index and address tables. We found that we had to update Red Hat 3.0 net-snmp c! ode to "net-snmp-5.0.9-2-30E.6" to resolve problem.

 Mark F Sklenarik
 IBM SWG Tivoli Solutions
 Quality Assurance

  Business Impact Management and Event Correlation
 Software Quality Engineer
 IBM Corporation

 

                              

 



free lancer <larrytechie@yahoo.com>
Sent by: owner-nv-l@lists.us.ibm.com

11/05/2004 02:12 PM

Please respond to
nv-l

To

nv-l@lists.us.ibm.com

cc

 

Subject

[nv-l] Object Turn Red after Ping

 

 

 




Hi,
We have Netview 7.1.3 FP3 on AIX 5.1. There is some strange behavior on some of the deivces on the Map. There are showing up as red on map. When i ping them, they come back up as green and status is up and right after some time they go red again. But there is no problem of events coming in from those devices. I'm cluless in here. Could some out there help me please.
Many Thanks,
Larry.
 


Do you Yahoo!?
Check out the new Yahoo! Front Page. www.yahoo.com


Do you Yahoo!?
Check out the new Yahoo! Front Page. www.yahoo.com

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

Archive operated by Skills 1st Ltd

See also: The NetView Web