getnext(ADMN)
getnext --
management utility that retrieves variables from an SNMP entity
Syntax
getnext [ -f defns_file ]
entity_addr community_string
variable_name
[ variable_name ] ...
Description
getnext is an SNMP application to
retrieve a set of individual variables from an
SNMP entity using a GET-NEXT
request. The arguments are the entity's address, the
community string for access to the SNMP entity,
and the variable name(s) expressed as either dot-notation
or the variable name as it appears in the MIB
document.
The optional argument
-f
is used to specify a file containing the
mosy(ADMN)
and
post_mosy(ADMN)
compiled list of object names and their numeric Object Identifiers,
in addition to the objects in the standard MIB.
This allows the user
to dynamically augment the number of objects that can be recognized
by the management utility.
It should be noted that since the function
utilizes the powerful GET-NEXT operator,
the variable returned will be a fully qualified object
identifier lexicographically greater than that which was
entered. For instance:
getnext suzzy public system interfaces
would return the variables sysDescr.0 and
ifNumber.0.
getnext -f cisco.objects cisco_box public romId domainName
would return the variables
romId.0
and
domainName.0.
See also
getid(ADMN),
getmany(ADMN),
getmet(ADMN),
getone(ADMN),
getroute(ADMN),
getsub(ADMN),
mosy(ADMN),
post_mosy(ADMN),
setany(ADMN),
snmpd(ADMN),
snmpd.conf(SFF),
snmpd.comm(SFF),
snmpd.peers(SFF),
snmpd.trap(SFF),
snmpstat(ADMN),
trap_rece(ADMN),
trap_send(ADMN)
Standards conformance
getnext is conformant with:
RFC 1155 (STD 16), RFC 1156,
RFC 1157 (STD 15), RFC 1213 (STD 17),
RFC 1227,
RFC 1231, RFC 1354, RFC 1398,
RFC 1389, RFC 1471, RFC 1473
© 2003 Caldera International, Inc. All rights reserved.
SCO OpenServer Release 5.0.7 -- 11 February 2003