> Either tweak your module code to include the length of the index
> string, or redefine this INDEX clause to read
> INDEX { IMPLIED fx25Name }
I tried to add IMPLIED keyword and it works fine now.
There is just a small problem on the OID index of this table
ribInRteEntry OBJECT-TYPE
SYNTAX RibInRteEntry
ACCESS not-accessible
STATUS mandatory
DESCRIPTION "Route dans la rib in"
INDEX {IMPLIED ribInRteAdjName , ribInRteId}
::= {ribInTable 1}
Is it possible to display ribInRteAdjName with string format and keep
ribInRteId as an integer ?
With use of IMPLIED keyword I obtain:
STNA-ATN-MIB::ribInRteAdjName.'bis5.' = STRING: "bis5"
And I would have:
STNA-ATN-MIB::ribInRteAdjName.'bis5'.1 = STRING: "bis5"
>Hmmm.....
>I have to say that I'm surprised.
>I'd have expected that to fail in the same way.
>Unless the definition of 'mobName' has a fixed size SYNTAX,
>while fx25Name doesn't?
Me too ! The definition is exactly the same between mobName and
fx25Name. These objects are both variable-length objects.
Is the behaviour of snmpget changed since UCDSNMP4.1.2 (the toolkit I
used before migration to netsnmp5.0.8) ? With UCD, requests on variable
length indexes worked fined without specifying IMPLIED keyword or length
of indexes.
Fabrice.
PS: Dave, thank you very much for your very helpful support !
_____________________________________________________________________
MSN Messenger, nouvelle version ! Personnalisez vos messages, jouez en
ligne et communiquez en temps réel par vidéo! http://ifrance.com/_reloc/m
-------------------------------------------------------
This sf.net email is sponsored by:ThinkGeek
Welcome to geek heaven.
http://thinkgeek.com/sf
|
