Hi Jeff, It is very simple: SNMP4J-Agent expects the OID of the TableEntry object (=the conecptual row OID). Thus, create the table with "x.x.x.3.1" and everything will be work as expected.
The reason for this, is the generic OID handling of SNMP4J-Agent which does not differentiate between scalars, tables, and complex region registrations. Best regards, Frank Jeff Ramin wrote: > Hi folks. > > I'm implementing an SNMP agent in an application, and I'm having > problems getting tables to work properly. > > Let's say the OID of the table is x.x.x.3, and it has 3 columns. After I > add a row to the table and walk the MIB, I'd expect to see output like: > > x.x.x.3.1.1.1 = value > x.x.x.3.1.2.1 = value > x.x.x.3.1.3.1 = value > > However, when the table is walked, the resulting OIDs are missing the > row number. So, the output is instead: > > x.x.x.3.1.1 = value > x.x.x.3.2.1 = value > x.x.x.3.3.1 = value > > I've been banging my head on this one for a couple days. Can anybody > suggest what I'm doing wrong? > > Thanks! > > > -- AGENT++ http://www.agentpp.com http://www.snmp4j.com http://www.mibexplorer.com http://www.mibdesigner.com _______________________________________________ SNMP4J mailing list [email protected] http://lists.agentpp.org/mailman/listinfo/snmp4j
