Description 1
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. The format is a comma separated list specifying the new order of the existing table entries. n1,n2,n3,n4,n5,n6,n7,n8,n9,n10,n11,n12,n13,n14,n15,n16 where n1,n2,n3,n4,n5,n6,n7,n8,n9,n10,n11,n12,n13,n14,n15,n16 is a permuation of 1,2,3,4,5,6,7,8,9,10,11,12,13,14,15,16 Note that this implies that each of the numbers 1-16 must appear exactly once For example, if the value is 16,3,6,9,1,2,4,5,7,8,10,11,12,14,13,15 then the table is rearranged so that the existing entries are moved as follows: Existing Position New Position 1 --> 5 2 --> 6 3 --> 2 4 --> 7 5 --> 8 6 --> 3 7 --> 9 8 --> 10 9 --> 4 10 --> 11 11 --> 12 12 --> 13 13 --> 15 14 --> 14 15 --> 16 16 --> 1
Original text from OID Repository
reorderexternalSensorTableEntries OBJECT-TYPE
SYNTAX DisplayString
MAX-ACCESS read-write
STATUS current
DESCRIPTION
"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.
The format is a comma separated list specifying the new order of the
existing table entries.
n1,n2,n3,n4,n5,n6,n7,n8,n9,n10,n11,n12,n13,n14,n15,n16
where n1,n2,n3,n4,n5,n6,n7,n8,n9,n10,n11,n12,n13,n14,n15,n16 is a permuation of
1,2,3,4,5,6,7,8,9,10,11,12,13,14,15,16
Note that this implies that each of the numbers 1-16 must appear exactly once
For example, if the value is 16,3,6,9,1,2,4,5,7,8,10,11,12,14,13,15
then the table is rearranged so that the existing entries are moved as follows:
Existing Position New Position
1 --> 5
2 --> 6
3 --> 2
4 --> 7
5 --> 8
6 --> 3
7 --> 9
8 --> 10
9 --> 4
10 --> 11
11 --> 12
12 --> 13
13 --> 15
14 --> 14
15 --> 16
16 --> 1
"
Sources for this description
Description 2
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
Sources for this description
Multiple manufacturers; see the original MIB MIB copies (LibreNMS/Observium Community)
See 1 matching source record