ERI-DNX-HDS3-MIB :: hds3LIUCmdStatus

MIB Reference — IPNetwork Monitor · Updated September 14, 2026

All MIBsERI-DNX-HDS3-MIBhds3LIUCmdStatus

hds3LIUCmdStatus

Module: ERI-DNX-HDS3-MIB

OID (symbolic): ERI-DNX-HDS3-MIB::hds3LIUCmdStatus

OID (numeric): 1.3.6.1.4.1.644.2.4.2.2.2.2.1.12

Node type: OBJECT-TYPE

Type: INTEGER

Access: read-write

Description: This is the command status for the LIU Framer Row. 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

Commands used in SET Command (1..99) update (1) Can be used optionally when activating loops and berts in order to get status code back in response clearErrors (14) Resets all error counters and bert test time to zero

Response States used in GET RESPONSE Command (100..199) update-successful (101) Test action has been successfully performed clear-successful (114) Error counts have been successfully cleared

Error Codes used in GET RESPONSE Command (200..799) err-general-liu-error (200) Unknown LIU request error occurred. err-invalid-loop-type (202) Unrecognized loop selection err-invalid-bert-type (203) Unrecognized bert selection err-test-in-progress (205) Requested action cannot be performed during bert err-field-cannot-be-set (206) Read-only field was included in SET request err-invalid-command (208) Unrecognized Test Command requested 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 hds3LIUCmdStatus?

This read-write command/status register drives LIU test actions: an admin SETs a code like update(1) or clearErrors(14), and the agent replaces it with a response such as update-successful(101) or an error like err-invalid-loop-type(202). Admins check the returned value after a SET to confirm a loopback or BERT command actually took effect.

Examples

Walk all instances (SNMPv2c):

snmpwalk -v2c -c public <target> 1.3.6.1.4.1.644.2.4.2.2.2.2.1.12
snmpwalk -v2c -c public <target> ERI-DNX-HDS3-MIB::hds3LIUCmdStatus

Get a specific instance (index 1):

snmpget -v2c -c public <target> 1.3.6.1.4.1.644.2.4.2.2.2.2.1.12.1
snmpget -v2c -c public <target> ERI-DNX-HDS3-MIB::hds3LIUCmdStatus.1

Set instance 1 (SNMPv2c):

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

Start monitoring Eastern Research Inc. (ERI) DNX digital cross-connect/multiplexer (Hybrid DS3 card) with a free 30-day trial of IPNetwork Monitor. Create custom SNMP monitor using the ERI-DNX-HDS3-MIB::hds3LIUCmdStatus OID value, configure state conditions and alerts, and monitor any Eastern Research Inc. (ERI) DNX digital cross-connect/multiplexer (Hybrid DS3 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.2dnxHDS3ERI-DNX-HDS3-MIB
1.3.6.1.4.1.644.2.4.2.2.2hds3DiagERI-DNX-HDS3-MIB
1.3.6.1.4.1.644.2.4.2.2.2.2hds3LIUTableERI-DNX-HDS3-MIB
1.3.6.1.4.1.644.2.4.2.2.2.2.1hds3LIUEntryERI-DNX-HDS3-MIB
1.3.6.1.4.1.644.2.4.2.2.2.2.1.12hds3LIUCmdStatusERI-DNX-HDS3-MIB