ERI-DNX-T3-MIB :: t3CmdStatus

MIB Reference — IPNetwork Monitor · Updated October 05, 2026

All MIBs › ERI-DNX-T3-MIB › t3CmdStatus

t3CmdStatus

Module: ERI-DNX-T3-MIB

OID (symbolic): ERI-DNX-T3-MIB::t3CmdStatus

OID (numeric): 1.3.6.1.4.1.644.2.4.2.1.1.1.1.17

Node type: OBJECT-TYPE

Type: LinkCmdStatus

Access: read-write

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

T3 Link Commands used in SET Command (1..99) update-link-config(1), Change existing Link Configuration

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

T3 Port Config Error Codes used in GET RESPONSE Command (100..699) err-general-link-config-error (400) Unknown link configuration error occurred err-invalid-link-status (401) Unrecognized link status setting err-invalid-link-framing (402) Line framing type not valid for link type err-invalid-link-command (403) Unrecognized link command-action err-invalid-link-op-mode (407) Configured M13 Op mode not valid for port; verify other link parameters match desired new mode err-invalid-link-rem-loop (408) Remote Loop type not valid for t3 frame type err-invalid-link-ais (409) Unrecognized t3 AIS selection 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 t3CmdStatus?

A command/response control: an admin writes a numeric command such as update-link-config to apply pending changes to this T3 port's configuration row, and the agent overwrites the value with a response code (e.g. 101 for success, or an error code like 402 for invalid framing) indicating the outcome.

Examples

Walk all instances (SNMPv2c):

snmpwalk -v2c -c public <target> 1.3.6.1.4.1.644.2.4.2.1.1.1.1.17
snmpwalk -v2c -c public <target> ERI-DNX-T3-MIB::t3CmdStatus

Get a specific instance (index 1):

snmpget -v2c -c public <target> 1.3.6.1.4.1.644.2.4.2.1.1.1.1.17.1
snmpget -v2c -c public <target> ERI-DNX-T3-MIB::t3CmdStatus.1

Set instance 1 (SNMPv2c):

snmpset -v2c -c private <target> 1.3.6.1.4.1.644.2.4.2.1.1.1.1.17.1 s <value>

Start monitoring Eastern Research Inc. (ERI) DNX digital cross-connect/multiplexer (T3/DS3 interface card) with a free 30-day trial of IPNetwork Monitor. Create custom SNMP monitor using the ERI-DNX-T3-MIB::t3CmdStatus OID value, configure state conditions and alerts, and monitor any Eastern Research Inc. (ERI) DNX digital cross-connect/multiplexer (T3/DS3 interface card) 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.2devicesERI-DNX-SMC-MIB
Numeric OIDNameModule
1.3.6.1.4.1.644.2.4.2.1dnxT3ERI-DNX-T3-MIB
1.3.6.1.4.1.644.2.4.2.1.1t3ConfigERI-DNX-T3-MIB
1.3.6.1.4.1.644.2.4.2.1.1.1t3PortConfigTableERI-DNX-T3-MIB
1.3.6.1.4.1.644.2.4.2.1.1.1.1t3PortConfigEntryERI-DNX-T3-MIB
1.3.6.1.4.1.644.2.4.2.1.1.1.1.17t3CmdStatusERI-DNX-T3-MIB