Difference between revisions of "Template:FAQ:Applications 08"
(5.4 release synchronisation) |
(Latest FAQ revision - preparing for 5.5 release) |
||
| Line 19: | Line 19: | ||
to denote a particular object in a specific MIB module. Note that this | to denote a particular object in a specific MIB module. Note that this | ||
uses the name of the '''module''', not the name of the file. | uses the name of the '''module''', not the name of the file. | ||
| − | + | However, if <CODE>'snmpwalk'</CODE> | |
| − | + | ||
displays the object by name, this is unlikely to be the cause, | displays the object by name, this is unlikely to be the cause, | ||
and you should look closely at the exact object name you are using. | and you should look closely at the exact object name you are using. | ||
| + | In particular, see the [[FAQ:Applications_09|next entry]]. | ||
Latest revision as of 09:19, 28 May 2009
If a general snmpwalk shows a particular entry, but asking for it more specifically gives a "sub-identifier not found:" or "Unknown Object Identifier" error, then that's a problem with the tool, rather than the agent.
Firstly, make sure that you're asking for the object by the right name.
Object descriptors are case-sensitive, so asking for 'sysuptime' will
not be recognised, but 'sysUpTime' will.
Alternatively, the object may be defined in a MIB that hasn't been loaded. Try loading in all the MIB files:
snmpget -m ALL -v1 -c public localhost sysUpTime.0
or specify the name of the appropriate MIB explicitly:
snmpget -v1 -c public myhost RFC1213-MIB::sysUpTime.0
to denote a particular object in a specific MIB module. Note that this
uses the name of the module, not the name of the file.
However, if 'snmpwalk'
displays the object by name, this is unlikely to be the cause,
and you should look closely at the exact object name you are using.
In particular, see the next entry.
