setany(ADMN)
setany --
management utility that retrieves and sets variables in an SNMP entity
Syntax
setany [ -f defns_file ]
entity_addr community_string
[ variable_name -<i/o/d/a/c/g/t/s/n> value ]
...
Description
setany does a GET request to
get the current values of the variables to be set, then
performs a SET request on the variables.
The arguments are the entity name or address in internet
dot notation, the community string for access to the
SNMP entity, and a triplet for each variable to
be set consisting of: the variable name in dot notation, an
´i', 'o', 'd', 'a', 'c', 'g', 't', 's', or 'n'
preceded by a dash to indicate if the variable's value is
being given as an integer, an octet string (in hex
notation), an object identifier (in dot notation), an
IP address (in dot notation), a counter, a gauge,
time-tick, a string, or null, followed by the value.
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.
For example:
setany 128.169.1.1 suranet0 "ifAdminStatus.2" -i 3
This sets the administrative status of interface 2 to 3 (down).
setany -f cisco.objects cisco_box secure_comm tsMsgttyLine.0 -i -1
will cause the terminal server message to be sent to all the tty lines.
The actions that take place during a SET
request are that a GET request is issued
for the variable. The variable name returned from this
request is used in the SET request.
See also
getid(ADMN),
getmany(ADMN),
getmet(ADMN),
getnext(ADMN),
getone(ADMN),
getroute(ADMN),
getsub(ADMN),
mosy(ADMN),
post_mosy(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
setany 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
© 2003 Caldera International, Inc. All rights reserved.
SCO OpenServer Release 5.0.7 -- 11 February 2003