This is the mail archive of the
ecos-discuss@sourceware.org
mailing list for the eCos project.
SNMP lockup
- From: Grant Edwards <grante at visi dot com>
- To: ecos-discuss at sources dot redhat dot com
- Date: Fri, 8 May 2009 20:51:52 +0000 (UTC)
- Subject: [ECOS] SNMP lockup
I've run across a problem where certain "get" requests for
certain OIDs cause a lock-up. I can still ping the box, but
everything else is dead (all my user tasks are dead and the box
won't respond to any further SNMP requests).
The OIDs that are causing the problem are
.1.3.6.1.2.1.2.2.1.n.0
That's a query for an attribute of network interface #0. Which
attribute depends on n: 6==physAddr, 2=name, etc. That last
feild (.0) in the OID is the interface number.
Network interface 1 is the ethernet interface, and interface 2
is the loopback interface. Requests for attributes of those
interfaces work fine. [Asking for other unrecognized or
out-of-range OIDs seems to return the proper error codes.]
There isn't an interface 0, but some SNMP programs (e.g. the
really expensive ones from HP and Cisco) send requests for OID
.1.3.6.1.2.1.2.2.1.6.0 to my eCos-based widget and locking it
up. It order to keep the eCos-based boxes running, my
customers have to disable SNMP suppert in the eCos-based
product or exclude the eCos-based products from the address
range to which said expensive SNMP apps are allowed to talk.
Has anybody seen this behavior before? Any ideas on how to fix
it?
--
Grant Edwards grante Yow! PEGGY FLEMMING is
at stealing BASKET BALLS to
visi.com feed the babies in VERMONT.
--
Before posting, please read the FAQ: http://ecos.sourceware.org/fom/ecos
and search the list archive: http://ecos.sourceware.org/ml/ecos-discuss