ERI-DNX-NEST-SYS-MIB :: xNestCmdStatus

MIB Reference — IPNetwork Monitor · Updated October 05, 2026

All MIBs › ERI-DNX-NEST-SYS-MIB › xNestCmdStatus

xNestCmdStatus

Module: ERI-DNX-NEST-SYS-MIB

OID (symbolic): ERI-DNX-NEST-SYS-MIB::xNestCmdStatus

OID (numeric): 1.3.6.1.4.1.644.2.4.1.11.1.1.11

Node type: OBJECT-TYPE

Type: INTEGER

Access: read-write

Description: The command status for this nest configuration row/record. The value used in a SET will be replaced by a response value in the GET RESPONSE indicating success or failure.

Default Response State used in GET RESPONSE Command ready-for-command (0) initial default status for a row

Nest Device Commands used in SET Command (1..99) update-nest-config (1) change an aspect of current nest configuration delete-nest-config (2) remove existing Nest Configuration. Deleting the Nest Configuration using the Nest Command Status will result in the removal of all configured connections associated with that nest number. switch-mgr-cards (3) Perform Switchover to Standby SMC/XNM card in associated Nest reset-device-cards (4) Reset all device cards in associated Nest clear-device-errors (5) Clear error counters for all channel cards in associated Nest switch-xcc-cards (6) Perform Switchover to Standby XCC card in associated Nest switch-xlink-cards (7) Perform Switchover to Standby XLC card in associated Nest.

Response States used in GET RESPONSE Command (100..199) update-successful (101) nest data has been successfully changed delete-successful (102) nest data has been successfully removed switch-mgr-successful (103) nest system managers has been successfully switched reset-successful (104) nest device cards have been issued reset requests clear-successful (105) nest device cards have been issued clear error requests switch-xcc-successful (106) nest xcc's has been successfully switched switch-xlink-successful (107) nest xlink cards has been successfully switched

Nest Config Error Codes used in GET RESPONSE Command (200..799) err-general-nest-config-error (200) Unknown nest configuration error occurred. err-invalid-nest-type (201) Configured nest type not in valid range err-invalid-nest-command (202) Unrecognized nest command-action err-invalid-nest-name (203) Configured nest name too long err-invalid-nest-alrm (204) Configured nest alarm contacts not in valid range err-invalid-nest-ndr (205) N+1 Redundancy not supported for nest err-invalid-nest-option (206) Dual XCC/XLC or Dual SMC option not valid err-cannot-delete-online-nest (207) Nest cannot be online when deleting configuration err-nest-not-present (208) Nest not ready for command err-data-locked-by-another-user (450) Another administrative user is making changes to this part of the system via a terminal session. Check Event Log for user name err-snmp-parse-failed (500) Agent could not parse variable err-invalid-snmp-type (501) Variable ASN type does not match Agent defined type err-invalid-snmp-var-size (502) Variable size is too big

What is xNestCmdStatus?

A command/response object used to change this nest's configuration: an admin sets it to values like update-nest-config(1), switch-mgr-cards(3), or reset-device-cards(4) to act on the nest, and the agent overwrites it with a response code (e.g. update-successful(101) or an error like err-invalid-nest-type(201)) indicating the result. This field must be included in the same SET request as any other nest changes for them to take effect.

Examples

Walk all instances (SNMPv2c):

snmpwalk -v2c -c public <target> 1.3.6.1.4.1.644.2.4.1.11.1.1.11
snmpwalk -v2c -c public <target> ERI-DNX-NEST-SYS-MIB::xNestCmdStatus

Get a specific instance (index 1):

snmpget -v2c -c public <target> 1.3.6.1.4.1.644.2.4.1.11.1.1.11.1
snmpget -v2c -c public <target> ERI-DNX-NEST-SYS-MIB::xNestCmdStatus.1

Set instance 1 (SNMPv2c):

snmpset -v2c -c private <target> 1.3.6.1.4.1.644.2.4.1.11.1.1.11.1 i <value>

Start monitoring Eastern Research Inc. DNX-88/DNX-11 nest multiplexer chassis (slot/redundancy administration) with a free 30-day trial of IPNetwork Monitor. Create custom SNMP monitor using the ERI-DNX-NEST-SYS-MIB::xNestCmdStatus OID value, configure state conditions and alerts, and monitor any Eastern Research Inc. DNX-88/DNX-11 nest multiplexer chassis (slot/redundancy administration) from a single console.

OID Breakdown

Upper-level ancestors (10 from the standard OID tree / other modules)
Numeric OIDNameModule
1isoLANART-AGENT
1.3orgAirPair-MIB
1.3.6dodAirPair-MIB
1.3.6.1internetAirPair-MIB
1.3.6.1.4privateAirPair-MIB
1.3.6.1.4.1enterprisesAirPair-MIB
1.3.6.1.4.1.644eriEnterpriseRootERI-ROOT-SMI
1.3.6.1.4.1.644.2eriProductsERI-ROOT-SMI
1.3.6.1.4.1.644.2.4dnxERI-DNX-SMC-MIB
1.3.6.1.4.1.644.2.4.1sysMgrERI-DNX-SMC-MIB
Numeric OIDNameModule
1.3.6.1.4.1.644.2.4.1.11eXpansionNestAdminERI-DNX-NEST-SYS-MIB
1.3.6.1.4.1.644.2.4.1.11.1xNestCfgTableERI-DNX-NEST-SYS-MIB
1.3.6.1.4.1.644.2.4.1.11.1.1xNestCfgEntryERI-DNX-NEST-SYS-MIB
1.3.6.1.4.1.644.2.4.1.11.1.1.11xNestCmdStatusERI-DNX-NEST-SYS-MIB