snmprealwalk
If you have importet the MIB-Files into the MIB Tree with "snmp_read_mib" you may use '=' as the "type" parameter.
In this case the type will also be taken from the loaded mib file. (Octest strings will be interpreted like strings though)
Comes in handy for a more dynamic use of snmpset.
snmpset
(PHP 4, PHP 5)
snmpset — Set an SNMP object
Description
bool snmpset
( string $hostname
, string $community
, string $object_id
, string $type
, mixed $value
[, int $timeout
[, int $retries
]] )
snmpset() is used to set the value of an SNMP object specified by the object_id .
Parameters
- hostname
-
The SNMP agent.
- community
-
The write community.
- object_id
-
The SNMP object.
- type
-
- value
-
- timeout
-
- retries
-
Return Values
Returns TRUE on success or FALSE on failure.
add a note
User Contributed Notessnmpset
tridman
19-Apr-2007 04:19
19-Apr-2007 04:19
deivis dot jakstas at gmail dot com
28-Dec-2006 03:53
28-Dec-2006 03:53
If you setting hex values correct format is:
snmpset($source_ip,$community,"$oid","x","10 10 10 10");
slawrance at technologist dot com
21-Jul-1999 09:01
21-Jul-1999 09:01
The "type" parameter must be one of the following, depending on the type of
variable to set on the SNMP host:
i INTEGER
u unsigned INTEGER
t TIMETICKS
a IPADDRESS
o OBJID
s STRING
x HEX STRING
d DECIMAL STRING
If OPAQUE_SPECIAL_TYPES was defined while compiling the SNMP library, the
following are also valid:
U unsigned int64
I signed int64
F float
D double
As an example, using "i" would set an integer, and "s" would set a string. If the SNMP host rejects the data type, you might get the following message: "Warning: Error in packet. Reason: (badValue) The value given has the wrong type or length."
If you specify an unknown or invalid OID, you might get a "Could not add variable" message. When specifying an absolute OID (one that is already resolved) that is completely numeric, prepend it with a period. For example, an OID that could enable/disable Ethernet ports on an Asante hub might be "1.3.6.1.2.1.22.1.3.1.1.3.6.4.0", but you would need to use ".1.3.6.1.2.1.22.1.3.1.1.3.6.4.0" in the OID parameter so that the SNMP library won't try to resolve an already resolved OID. Friendly, unresolved OIDs do not need the period prepended, such as "system.SysContact.0"