reorderexternalSensorTableEntries
PDU-MIB ·
.1.3.6.1.4.1.13742.4.3.2
Object
This is an operation. It has write-only semantics.
GET operation will return the empty string.
For SET operations, it specifies the new order of the externalSensorTable entries.
a) The list must contain entries for each managed sensor, even if the sensor is not being moved.
b) The list must not have more than 16 entries.
c) 1 <= Valid sensorID <= 16
d) The length of the list is the value of the largest sensorID in the
original (before the move) list of managed sensors.
e) Each sensorID must appear only once in the list.
f) If there are missing numbers in the original list of sensorIDs,
then each missing number must be indicated by a comma.
EXAMPLE 1: Managed sensors have IDs 1,2,3,4,5
Move 1 to 13; 2 to 8; 3 to 9; 4 is not moved; 5 moves to 2
Existing Position New Position
1 --> 13
2 --> 8
3 --> 9
4 --> 4
5 --> 2
Since the largest sensorID before the move is 5, the length of the list is 5
Comma separated list is 13,8,9,4,2
EXAMPLE 2: Managed sensors have IDs 2,5,6,7,11
Sensor IDs 1,3,4,8,9,10 do not appear in the list.
These positions must be indicated by commas.
Move 2 to 13; 5 to 8; 6 to 9; 7 to 16; 11 does not move
Existing Position New Position
2 --> 13
5 --> 8
6 --> 9
7 --> 16
11 --> 11
Since the largest sensorID before the move is 11, the length of the list is 11
Comma separated list is ,13,,,8,9,16,,,,11
Context
- MIB
- PDU-MIB
- OID
.1.3.6.1.4.1.13742.4.3.2- Type
- scalar
- Access
- readwrite
- Status
- current
- Parent
- externalSensors
- Groups
- 1
Net-SNMP examples
How SNMP and these commands workScalars have one instance, identified by the .0 suffix.
Read the scalar instance
/usr/bin/snmpget -v2c -c '<community>' -Pud -Ir -OQUv -m 'PDU-MIB' -M '/opt/observium/mibs/raritan:/opt/observium/mibs/rfc:/opt/observium/mibs/net-snmp' 'udp:<hostname>:161' 'PDU-MIB::reorderexternalSensorTableEntries.0'
More examples
Translate to a numeric OID
/usr/bin/snmptranslate -Pud -Ir -On -m 'PDU-MIB' -M '/opt/observium/mibs/raritan:/opt/observium/mibs/rfc:/opt/observium/mibs/net-snmp' 'PDU-MIB::reorderexternalSensorTableEntries'
Syntax
- Source
- SNMPv2-TCDisplayString
- Base type
OctetString- Display format
255a
Type Description
Represents textual information taken from the NVT ASCII
character set, as defined in pages 4, 10-11 of RFC 854.
To summarize RFC 854, the NVT ASCII repertoire specifies:
- the use of character codes 0-127 (decimal)
- the graphics characters (32-126) are interpreted as
US ASCII
- NUL, LF, CR, BEL, BS, HT, VT and FF have the special
meanings specified in RFC 854
- the other 25 codes have no standard interpretation
- the sequence 'CR LF' means newline
- the sequence 'CR NUL' means carriage-return
- an 'LF' not preceded by a 'CR' means moving to the
same column on the next line.
- the sequence 'CR x' for any x other than LF or NUL is
illegal. (Note that this also means that a string may
end with either 'CR LF' or 'CR NUL', but not with CR.)
Any object defined using this syntax may not exceed 255
characters in length.
Values & Constraints
Type Constraints
range: 0..255
Conformance
Member of