RE: SNMP Walk behaviour

"Nirmal Choudhary" <[email protected]>
Newsgroups gmane.network.net-snmp.user
Message-ID <22F058C3ED9D784E90CE473F2A9847F00266EA77@in-exchange>
Thanks Thomas,
	I am using "Red Hat Enterprise Linux Server release 5". We have
our own Net-SNMP SubAgent. Is this the problem in snmpd or in our
SubAgent. We have tested our SubAgent on "Red Hat Enterprise Linux ES
release 4". There it works fine. I am wondering if it is some
configuration problem or something else? 
So, if you have any ideas then please guide me in this scenario.

Regards,
Nirmal

-----Original Message-----
From: Thomas Anders [mailto:[email protected]] 
Sent: Monday, January 21, 2008 1:36 AM
To: Nirmal Choudhary
Cc: [email protected]
Subject: Re: SNMP Walk behaviour

Nirmal Choudhary wrote:
> 	I am using Net-SNMP-5.2.4. When I do snmpwalk then it gives the
> following error:
> 
> snmpwalk -v2c -c public 172.25.10.137 sipCommonMIB
[...]
> Error in packet.
> Reason: (genError) A general failure occured
> Failed object: SIP-COMMON-MIB::sipCommonMethodStatsInbounds.1."UPDATE"
> 
> When I run the command again then it gives above error for some other
> OID. Even SNMP Get and Get Next work properly for the OID which is
> giving problem. I mean snmpwalk is behaving abnormally. Sometime it
> gives error and sometime it doesn't. 

This error is produced by the *agent* running on 172.25.10.137 (and sent
across the wire) rather than by client-side snmpwalk. You need to
consult the vendor of that agent.


+Thomas



-------------------------------------------------------------------------
This SF.net email is sponsored by: Microsoft
Defy all challenges. Microsoft(R) Visual Studio 2008.
http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/
_______________________________________________
Net-snmp-users mailing list
[email protected]
Please see the following page to unsubscribe or change other options:
https://lists.sourceforge.net/lists/listinfo/net-snmp-users
lmpx.com only provides a reader for public news (NNTP) servers. It is not affiliated with the servers or forums shown here and is not responsible for the content of articles, which is written by their respective authors.