index defined as IMPLIED to avoid length oid, but nothing happens :-(

Torben Surmer <[email protected]>
Newsgroups gmane.network.net-snmp.user
Message-ID <[email protected]>
Hello to all,
 
I try to avoid the length subidentifier in net-snmp tables. I was adviced to define the table index as IMPLIED OBJECT IDENTIFIER. To test this tip, I changed the netSnmpIETFWGTable from the NET-SNMP-EXAMPLES-MIB as follows
NET-SNMP-EXAMPLES-MIB extract:
>>
netSnmpIETFWGEntry OBJECT-TYPE    SYNTAX      NetSnmpIETFWGEntry    MAX-ACCESS  not-accessible    STATUS      current    DESCRIPTION "A row describing a given working group"    INDEX   { IMPLIED nsIETFWGName }    ::= {netSnmpIETFWGTable 1 }
<<
I left the rest of the MIB file unchanged.
 
After creating the c-file   - mib2c -c mib2c.create-dataset.conf netSnmpIETFWGTable and compiling the subagent, I made the snmpset like shown in the tutorial
%snmpset localhost .1.3.6.1.4.1.8072.2.2.1.1.2.\"sming\" s "David" 
the result was:
NET-SNMP-MIB::netSnmp.2.2.1.1.2.5.115.109.105.110.103 = STRING: "David"
 
I have expected that the length subidentifier "5" would have been disappeared, but it didn´t. What have I done wrong?
 
Thank for advice.
Torben
 
 
 
 
 
_________________________________________________________________
Express yourself instantly with MSN Messenger! Download today it's FREE!
http://messenger.msn.click-url.com/go/onm00200471ave/direct/01/

-------------------------------------------------------------------------
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
lmpx.com only provides a reader for public news (NNTP) servers. It is not affiliated with the servers or forums shown here and is not responsible for the content of articles, which is written by their respective authors.