---
oid: "1.3.6.1.4.1.644.2.4.1.11.2.1"
short-description: "xSlotEntry OBJECT-TYPE"
last-modified: "2018-01-03"
parent-oid: "1.3.6.1.4.1.644.2.4.1.11.2"
---

## OID: `1.3.6.1.4.1.644.2.4.1.11.2.1`

```asn1
{iso(1) identified-organization(3) dod(6) internet(1) private(4) enterprise(1) 644 eriProducts(2) dnx(4) sysMgr(1) eXpansionNestAdmin(11) xSlotTable(2) xSlotEntry(1)}
```

### Description

```asn1
xSlotEntry OBJECT-TYPE
SYNTAX XSlotEntry
MAX-ACCESS not-accessible
STATUS current
DESCRIPTION
"The conceptual row of the Slot Configuration table. A row in this
table can not be created or deleted. A row in this table can be
modified by providing valid values for either the Slot Name,
Configured Device Type, Device Redundancy, or Slot Command Status.
Deleting the Slot Configuration using the Slot Command Status
value of 'delete-slot-config' will result in the removal of all
configured connections associated with that slot number. The
xnmSlotCfgCmdStatus field must be included as a variable in a
SET PDU for the action to take effect. If the xnmSlotCfgCmdStatus is
missing from the SET PDU, the GET RESPONSE will contain the SNMP error
status of 'genErr' for and an error index equal to the last variable."
INDEX { xSlotNestAddr }
```

**Classification:** MIB object for network management

### Child OIDs

- `1.3.6.1.4.1.644.2.4.1.11.2.1.2`: `xSlotDeviceType(2)`
- `1.3.6.1.4.1.644.2.4.1.11.2.1.3`: `xSlotActualDeviceType(3)`
- `1.3.6.1.4.1.644.2.4.1.11.2.1.4`: `xSlotDeviceState(4)`
- `1.3.6.1.4.1.644.2.4.1.11.2.1.5`: `xSlotAlarmLevel(5)`
- `1.3.6.1.4.1.644.2.4.1.11.2.1.6`: `xSlotDeviceName(6)`
- `1.3.6.1.4.1.644.2.4.1.11.2.1.7`: `xSlotDeviceVersion(7)`
- `1.3.6.1.4.1.644.2.4.1.11.2.1.8`: `xSlotDeviceRedundancy(8)`
- `1.3.6.1.4.1.644.2.4.1.11.2.1.9`: `xSlotMiscState(9)`
- `1.3.6.1.4.1.644.2.4.1.11.2.1.10`: `xSlotCmdStatus(10)`
- `1.3.6.1.4.1.644.2.4.1.11.2.1.11`: `xSlotRawDeviceState(11)`

### 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.
