Jeff Gehlbach wrote: > On Apr 17, 2008, at 12:41 PM, Niels van Drimmelen wrote: >> As you see the "2560" buffer is there. The problem is when you do a >> snmpgetnext on .2560.2, you don't get back the .2560.3 OID but a >> different >> one: >> >> snmpgetnext -v2c -cpublic 10.9.7.1 . >> 1.3.6.1.4.1.9.9.147.1.2.2.1.1.4.2560.2 >> >> output: >> >> .1.3.6.1.4.1.9.9.147.1.2.2.2.1.3.40.6 = STRING: "number of connections >> currently in use by the entire firewall" > > That's rather odd. What happens if you use v1 instead of v2c? And > what SNMP protocol version is OpenNMS set to use for this node? >
Like Shawn already mentioned, v2c or v1 doesn't matter. I did some additional testing using two different PIX firewalls: -PIX515E with pixos 7.2.3: identical behaviour as ASA 7.2.3 (the version we use on our ASA5520's) -PIX515E with pixos 6.3.5: works as expected. So my best guess: Cisco did a booboo. Cheers, Niels ------------------------------------------------------------------------- This SF.net email is sponsored by the 2008 JavaOne(SM) Conference Don't miss this year's exciting event. There's still time to save $100. Use priority code J8TL2D2. http://ad.doubleclick.net/clk;198757673;13503038;p?http://java.sun.com/javaone _______________________________________________ Please read the OpenNMS Mailing List FAQ: http://www.opennms.org/index.php/Mailing_List_FAQ opennms-devel mailing list To *unsubscribe* or change your subscription options, see the bottom of this page: https://lists.sourceforge.net/lists/listinfo/opennms-devel
