ERI-DNX-NEST-SYS-MIB :: xNdrCmdStatus

MIB Reference — IPNetwork Monitor · Updated October 05, 2026

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

xNdrCmdStatus

Module: ERI-DNX-NEST-SYS-MIB

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

OID (numeric): 1.3.6.1.4.1.644.2.4.1.11.3.1.16

Node type: OBJECT-TYPE

Type: INTEGER

Access: read-write

Description: The command status for this ndr 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

NDR Device Commands used in SET Command (1..99) update-ndr (1) change an aspect of current nest N+1 Redundancy

Response States used in GET RESPONSE Command (100..199) update-successful (101) ndr data has been successfully changed

NDR Config Error Codes used in GET RESPONSE Command (200..799) err-general-ndr-config-error (200) Unknown ndr configuration error occurred. err-invalid-ndr-group-type (201) Configured NDR Group type not in valid range err-invalid-ndr-command (202) Unrecognized NDR command-action err-invalid-ndr-autoswitch (203) NDR Auto Switchover value not in valid range err-invalid-ndr-chassis (204) NDR Chassis Type value not in valid range err-invalid-ndr-dual-bb (205) NDR Dual Broadband Group value not in valid err-invalid-ndr-dual-psx (206) NDR Dual PSX Power Supply value not in valid 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 xNdrCmdStatus?

A command/response object used to change this expansion nest's N+1 redundancy configuration: an admin sets it to update-ndr(1) to apply a change, and the agent overwrites it with a response code such as update-successful(101) or an error like err-invalid-ndr-chassis(204). This field must be included in the same SET request as any other NDR 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.3.1.16
snmpwalk -v2c -c public <target> ERI-DNX-NEST-SYS-MIB::xNdrCmdStatus

Get a specific instance (index 1):

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

Set instance 1 (SNMPv2c):

snmpset -v2c -c private <target> 1.3.6.1.4.1.644.2.4.1.11.3.1.16.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::xNdrCmdStatus 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.3xNdrTableERI-DNX-NEST-SYS-MIB
1.3.6.1.4.1.644.2.4.1.11.3.1xNdrEntryERI-DNX-NEST-SYS-MIB
1.3.6.1.4.1.644.2.4.1.11.3.1.16xNdrCmdStatusERI-DNX-NEST-SYS-MIB