Template:FAQ:Applications 04

If you can see most of the standard information (not just the system and hrSystem groups), but not in the vendor-specific 'enterprises' tree, then once again there are several possible causes.

Firstly, it's possible that the agent does not implement this particular enterprise tree. Remember that adding a MIB to the client tools does not automatically add support for these object to the agent. See the AGENT section for more information.

Alternatively, it may be that the agent does implement some or all of this enterprise tree, but the access control settings are configured to block access to it.

The simplest way to checks whether the agent implements a given portion of the OID tree is to run

       snmpwalk .... nsModuleName
   

and look for index values that fall in the area of interest. (Always assuming that you have access to this particular section of the Net-SNMP enterprise tree, of course!)

Checking the access control settings can be done by examining the tables vacmAccessTable and vacmViewTreeFamilyTable.
Note that these are used to configure access control for all versions of SNMP - not just SNMPv3.

The third possibility is that simply isn't any information in the specified tree. For example, several of the tables in the UCDavis enterprise tree (such as prTable, extTable, dskTable and fileTable) require explicit configuration in the snmpd.conf file. If you query this particular tables without the necessary configuration entries, then they will be empty.

Finally, if you can't see anything from any enterprise-specific tree, then this may be down to how you are asking for the information. By default, if snmpwalk is run without an explicitly starting OID, then it will display the contents of the 'mib-2' tree, containing most of the IETF-standard management information supported by the agent.

When the agent reaches the end of this tree, it will return the first enterprise-specific value, snmpwalk will recognise that this marks the end of the (implicit) requested tree, and stop. No enterprise-specific information will be displayed.

To walk the whole tree, and see all the information that the agent supports, specify a starting point of '.iso' or '.1'. To walk a specific enterprise subtree, specify the root of this tree as the starting point - e.g:

       snmpwalk -v1 -c public localhost UCD-SNMP-MIB::ucdavis

There is more information about particular UCD-specific subtrees in the AGENT section.

If you're walking a specific tree, but failing to see anything in it, then the most likely cause is that the agent simply does not implement those particular MIB objects. Or if it does, that the access control or other configuration settings mean that there's nothing for you to see there.

However, if you're trying a basic 'snmpwalk' with no explicit OID specified, then this would also explain why you're not seeing any enterprise-specific results.

By default, unless given an explicit starting OID, then the 'snmpwalk' command will display the contents of the 'mib-2' tree, containing most of the IETF-standard management information supported by the agent. When the agent reaches the end of this tree, it will return the first enterprise-specific value, and 'snmpwalk' will recognise that this marks the end of the (implicit) request tree, and stop. No enterprise-specific information will be displayed.

To walk the whole tree, and see all the information that the agent supports, specify a starting point of '.iso' or '.1'.

To walk a specific enterprise subtree, specify the root of this tree as the starting point - e.g:

       snmpwalk -v1 -c public localhost UCD-SNMP-MIB::ucdavis
 

There is more information about particular UCD-specific subtrees in the Agent section.