is an SNMP application that uses SNMP GETNEXT requests to query a
network entity for a tree of information.
An object identifier (OID) may be given on the command line. This OID
specifies which portion of the object identifier space will be
searched using GETNEXT requests. All variables in the subtree
below the given OID are queried and their values presented to the user.
Each variable name is given in the format specified in
If no OID argument is present,
will search the subtree rooted at SNMPv2-SMI::mib-2
(including any MIB object values from other MIB modules,
that are defined as lying within this subtree).
If the network entity has an error processing the request packet, an
error packet will be returned and a message will be shown, helping to
pinpoint why the request was malformed.
If the tree search causes attempts to search beyond the end of the
MIB, the message "End of MIB" will be displayed.
Do not check whether the returned OIDs are increasing. Some agents
(LaserJets are an example) return OIDs out of order, but can
complete the walk anyway. Other agents return OIDs that are out of
order and can cause
to loop indefinitely. By default,
tries to detect this behavior and warns you when it hits an agent
acting illegally. Use
to turn off this check.
Include the given OID in the search range. Normally
uses GETNEXT requests starting with the OID you specified and returns
all results in the MIB subtree rooted at that OID. Sometimes, you may
wish to include the OID specified on the command line in the printed
results if it is a valid OID in the tree itself. This option lets you
do this explicitly.
In fact, the given OID will be retrieved automatically if the main
subtree walk returns no useable values. This allows a walk of a
single instance to behave as generally expected, and return the
specified instance value.
This option turns off this final GET request, so a walk of a
single instance will return nothing.
Upon completion of the walk, print the number of variables found.
Upon completion of the walk, print the total wall-clock time it took
to collect the data (in seconds). Note that the timer is started just
before the beginning of the data request series and stopped just after
it finishes. Most importantly, this means that it does not include
snmp library initialization, shutdown, argument processing, and any
In addition to these options,
takes the common options described in the