is an SNMP application that uses SNMP GETBULK requests to query a
network entity efficiently 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 GETBULK 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 MIB-2.
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 behaviour.
Include the given OID in the search range. Normally
uses GETBULK requests starting with the OID you specified and returns
all results in the MIB tree after 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
field in the GETBULK PDUs. This specifies the number of supplied
variables that should not be iterated over. The default is 0.
Upon completion of the walk, print the number of variables found.
field in the GETBULK PDUs. This specifies the maximum number of
iterations over the repeating variables. The default is 10.
In addition to these options,
takes the common options described in the
In contrast to
this information will typically be gathered in a single transaction
with the agent, rather than one transaction per variable found.
is thus more efficient in terms of network utilisation, which may be
especially important when retrieving large tables.
As the name implies,
utilizes the SNMP GETBULK message, which is not available in SNMP v1.