For one MIB table which I use, type of index is IPADDRESS.
Table iteration approach has been used, for implementation.
A problem is that I got a different index for GET and GET_NEXT SNMP operation
(index is in the different order).
Example (radiusServerPort is the name of the column in the MIB table):
a GET request will return: radiusServerCurrentMode.192.168.1.20: (INTEGER): 0
a GET_NEXT request will return: radiusServerCurrentMode.20.1.168.192:
(INTEGER): 0
I check request and index is in the right order.
In MIB browser, for the GET_NEXT operation I got
Operation: Get next
Request binding:
1: radiusServerPrimaryMode.192.168.1.20 (INTEGER) null
Response binding:
1: radiusServerCurrentMode.20.1.168.192 (INTEGER) 0
Is anybody has any idea why I got index in the opposite order?
Thnaks.
------------------------------------------------------------------------------
Let Crystal Reports handle the reporting - Free Crystal Reports 2008 30-Day
trial. Simplify your report design, integration and deployment - and focus on
what you do best, core application coding. Discover what's new with
Crystal Reports now. http://p.sf.net/sfu/bobj-july
_______________________________________________
Net-snmp-users mailing list
Net-snmp-users@lists.sourceforge.net
Please see the following page to unsubscribe or change other options:
https://lists.sourceforge.net/lists/listinfo/net-snmp-users
