Re: problem with get_next when ipAddress as table index
Dave Shield <[email protected]>
| Newsgroups | gmane.network.net-snmp.user |
|---|---|
| Message-ID | <CAKoMtGbO2p2jzNpTKe2mUPy6Zzrst2t5kDa3LL5ak+ALNJ+4aA@mail.gmail.com> |
On 23 July 2012 17:06, Naama Bar Menachem <[email protected]> wrote: > I don't think it is the reason for the issue for 2 reasons: > 1. I see that the LAST index is actually updated (table-id) and all > other 3 are not updated (all of type ipAddress) The issue is not whether the index values are changed or not. The problem that I was pointing out was that you are building the response OID from those index values, but the code only seems to include the first one. The obvious way to check this would be to issue a single "snmpgetnext" request for an instance within this table, and report what answer you get back. > 2. I have another table with multiple indices, all integers, and with > same code (which is automatically generated by mib2c) it works fine If you say so - then fine. I've no idea what the code of the two modules actually looks like, so cannot really comment whether it is the same or not. Dave ------------------------------------------------------------------------------ Live Security Virtual Conference Exclusive live event will cover all the ways today's security and threat landscape has changed and how IT managers can respond. Discussions will include endpoint security, mobile security and the latest in malware threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/ _______________________________________________ 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