Re: how should agents handle an 'out-of-range' index ?
Fulko Hew <[email protected]>
| Newsgroups | gmane.network.net-snmp.user |
|---|---|
| Message-ID | <[email protected]> |
On Tue, Sep 14, 2010 at 11:55 AM, Fulko Hew <[email protected]> wrote: ... snip ... > When I ran this test (snmpgetnext), the agent died and needed to be restarted. > The variable I was querying was: > > 1.3.6.1.4.1.2021.8.1.103.4294967295 aka 'UCD-SNMP-MIB:extIndex'. > > (FYI. it also happens on other variables.) > ... snip ... > Although this may have been addressed/fixed in newer versions of Net-SNMP > I just built 5.6.rc2 and tried it. snmpgetnext -v1 -cpublic -Ir localhost 1.3.6.1.4.1.2021.8.1.103.4294967295 Unfortunately, this release candidate also dies with a segmentation violation. ... snip ... ------------------------------------------------------------------------------ Start uncovering the many advantages of virtual appliances and start using them to simplify application deployment and accelerate your shift to cloud computing. http://p.sf.net/sfu/novell-sfdev2dev _______________________________________________ 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