10-09-2002 04:50 AM - edited 03-02-2019 01:56 AM
Hi,
I am using a SNMP walk file, based on Cisco Catalyst 1900 (OS V9.00.04). The file is created using a simple walk utility, which just performs GetNext commands. The table '1.3.6.1.2.1.17.4.3.1.1' is returned in a non-lexicographical order:
1.3.6.1.2.1.17.4.3.1.1.0.192.29.220.183.95: \x00 C0 1D DC B7 5F
1.3.6.1.2.1.17.4.3.1.1.0.80.139.155.43.176: \x00 50 8B 9B 2B B0
1.3.6.1.2.1.17.4.3.1.1.0.16.164.162.91.98: \x00 10 A4 A2 5B 62
1.3.6.1.2.1.17.4.3.1.1.0.48.25.55.195.27: \x00 30 19 37 C3 1B
1.3.6.1.2.1.17.4.3.1.1.0.48.25.55.195.26: \x00 30 19 37 C3 1A
1.3.6.1.2.1.17.4.3.1.1.0.48.25.55.195.25: \x00 30 19 37 C3 19
1.3.6.1.2.1.17.4.3.1.1.0.48.25.55.195.24: \x00 30 19 37 C3 18
...
The question is:
a. Is this a normal/SNMP-compliant behavior? In other words - is it OK for SNMP tables to be returned not in the order of their index?
b. We didn't encounter this behavior with other Cat 1900 series switches (or with any other switches at all). Is there an OS version that fixes this behavior?
Thanks,
Ilan Assayag
Software Team Leader
Rit Technologies Ltd.
10-09-2002 11:27 PM
Hi,
After investing the RFC's, it does seems there is a bug in the SNMP support (RFC 1905 [SNMPv2, section 4.2.2 and 4.2.3] and RFC1157 [SNMPv1, section 4.1.3])
However, I still don't know whether there is an OS version that fixes this bug, and if so - what version (issue b).
If anybody knows ....
Thanks,
Ilan
10-10-2002 02:52 PM
You can look at the CCO Bug Toolkit to search for any known issues related to this.
Discover and save your favorite ideas. Come back to expert answers, step-by-step guides, recent topics, and more.
New here? Get started with these tips. How to use Community New member guide