RE: netsnmp_extract_table_info(request) is different torequest->requestvb->name in first run.

> From: [email protected] 
> [mailto:[email protected]] On 
> Behalf Of Torben Surmer
> Sent: Monday, October 15, 2007 1:09 AM

> I have a question concerning the netsnmp_extract_table_info() 
> function.
> 
> My example:
> 
>   for (request = requests; request; request = request->next) {     
>         char szT1[80], szT2[80];     
>         table_info  = netsnmp_extract_table_info(request);
>         
> snprint_objid(szT1,sizeof(szT1)-1,request->requestvb->name,req
> uest->requestvb->name_length);
>         
> snprint_objid(szT2,sizeof(szT2)-1,table_info->index_oid,table_
> info->index_oid_len);     
>         snmp_log(LOG_INFO, "szT1: (%s), szT2: (%s)\n",szT1,szT2);
> ...
> 
> }
> 
> has an ouput like this:
> 
> =>(NET-SNMP-MIB::netSnmp.99.1.2.3.67.80.85)(ccitt)<=
> *********************************
> why is here table_info->index_oid not filled?
> *********************************
> =>(NET-SNMP-MIB::netSnmp.99.1.3.3.67.80.85)(.3.67.80.85)<=
> =>(NET-SNMP-MIB::netSnmp.99.1.4.3.67.80.85)(.3.67.80.85)<=
> =>(NET-SNMP-MIB::netSnmp.99.1.5.3.67.80.85)(.3.67.80.85)<=
> =>(NET-SNMP-MIB::netSnmp.99.1.6)(.3.67.80.85)<=
> 
> why is in the first run the table_info->index_oid *NOT* .3.67.80.85 ?

	Are you sure that a NET-SNMP-MIB::netSnmp.99.1.2.3.67.80.85 object was returned in the request? (ccitt=0.0, which is also used as a "null OID").


	HTH,

Mike

-------------------------------------------------------------------------
This SF.net email is sponsored by: Splunk Inc.
Still grepping through log files to find problems?  Stop.
Now Search log events and configuration files using AJAX and a browser.
Download your FREE copy of Splunk now >> http://get.splunk.com/
_______________________________________________
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