---
oid: "1.3.6.1.4.1.13742.4.3.2"
short-description: "reorderexternalSensorTableEntries OBJECT-TYPE"
last-modified: "2021-09-13"
parent-oid: "1.3.6.1.4.1.13742.4.3"
---

## OID: `1.3.6.1.4.1.13742.4.3.2`

```asn1
{iso(1) identified-organization(3) dod(6) internet(1) private(4) enterprise(1) 13742 pdu(4) externalSensors(3) reorderexternalSensorTableEntries(2)}
```

### Description

```asn1
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.
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"
```

**Classification:** MIB object for network management

### Child OIDs

No child OID

### Terms of Use

[Terms of use](https://oid-base.com/disclaimer.htm.md)

**Note to implementers:**: The OID repository is constantly updated but does not necessarily store the latest (or most accurate) version of this formal description. For an implementation, it is recommended to search the web for a more recent description. If this is the case, please update the above description.