If you setting hex values correct format is:
snmpset($source_ip,$community,"$oid","x","10 10 10 10");
snmpset
(PHP 4, PHP 5, PHP 7)
snmpset — Setzt den Wert eines SNMP-Objekts
Beschreibung
bool snmpset
( string
$host
, string $community
, string $object_id
, string $type
, mixed $value
[, int $timeout = 1000000
[, int $retries = 5
]] )
Die Funktion snmpset() wird benutzt, um den Wert eines
SNMP Objekts zu setzen, das mit
object_id angegeben wird.
Parameter-Liste
-
host -
Der Hostname des SNMP-Agent (Server).
-
community -
Die "write community".
-
object_id -
Die SNMP-Objektkennung.
-
type -
The MIB defines the type of each object id. It has to be specified as a single character from the below list.
types = The type is taken from the MIB i INTEGER u INTEGER s STRING x HEX STRING d DECIMAL STRING n NULLOBJ o OBJID t TIMETICKS a IPADDRESS b BITS If
OPAQUE_SPECIAL_TYPESwas defined while compiling the SNMP library, the following are also valid:types U unsigned int64 I signed int64 F float D double Most of these will use the obvious corresponding ASN.1 type. 's', 'x', 'd' and 'b' are all different ways of specifying an OCTET STRING value, and the 'u' unsigned type is also used for handling Gauge32 values.
If the MIB-Files are loaded by into the MIB Tree with "snmp_read_mib" or by specifying it in the libsnmp config, '=' may be used as the
typeparameter for all object ids as the type can then be automatically read from the MIB.Note that there are two ways to set a variable of the type BITS like e.g. "SYNTAX BITS {telnet(0), ftp(1), http(2), icmp(3), snmp(4), ssh(5), https(6)}":
- Using type "b" and a list of bit numbers. This method is not recommended since GET query for the same OID would return e.g. 0xF8.
- Using type "x" and a hex number but without(!) the usual "0x" prefix.
See examples section for more details.
-
value -
Der neue Wert.
-
timeout -
Die Zahl der Mikrosekunden bis zum ersten Timeout.
-
retries -
Die Anzahl der Wiederholungsversuche, wenn Timeouts auftreten.
Rückgabewerte
Gibt bei Erfolg TRUE zurück. Im Fehlerfall wird FALSE zurückgegeben.
Wenn der SNMP-Host den Datentyp zurückweist, wird eine E_WARNING Meldung in der Art "Warning: Error in packet. Reason: (badValue) The value given has the wrong type or length." erzeugt. Wenn eine unbekannte oder ungültige OID angegeben wird, wird die Warnung wohl "Could not add variable" lauten.
Beispiele
Beispiel #1 Verwendung von snmpset()
<?php
snmpset("localhost", "public", "IF-MIB::ifAlias.3", "s", "foo");
?>
Beispiel #2 Verwendung von snmpset() zum Setzen von BITS SNMP Objektkennungen
<?php
snmpset("localhost", "public", 'FOO-MIB::bar.42', 'b', '0 1 2 3 4');
// or
snmpset("localhost", "public", 'FOO-MIB::bar.42', 'x', 'F0');
?>
add a note
User Contributed Notes 4 notes
deivis dot jakstas at gmail dot com ¶
11 years ago
slawrance at technologist dot com ¶
18 years ago
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
n NULLOBJ
b BITS
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"
ch at lathspell dot de ¶
8 years ago
Note that there are two ways to set a variable of the type BITS like e.g.:
SYNTAX BITS {telnet(0), ftp(1), http(2), icmp(3), snmp(4), ssh(5), https(6)}
1. Using type "b" and a list of bit numbers like:
snmpset('FOO-MIB::bar.42', 'b', '0 1 2 3 4');
with the disadvantage that the success is not easily verifyable as an snmpget() for the same OID would return e.g. 0xF8.
2. Using type "x" and a hex number but without(!) the usual "0x" prefix:
snmpset('FOO-MIB::bar.42', 'x', 'F0');
tridman ¶
11 years ago
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.
