All MIBs › ERI-DNX-HDS3-MIB › hds3CmdStatus
hds3CmdStatus
Module: ERI-DNX-HDS3-MIB
OID (symbolic): ERI-DNX-HDS3-MIB::hds3CmdStatus
OID (numeric): 1.3.6.1.4.1.644.2.4.2.2.1.1.1.26
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
HDS3 Link Commands used in SET Command (1..199) update-link-config(1), Change existing Link Configuration
Response States used in GET RESPONSE Command (200..399) update-successful (201) Link data has been successfully changed
HDS3 Port Config Error Codes used in GET RESPONSE Command (400..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 hds3 frame type err-invalid-link-ais (409) Unrecognized hds3 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.
What is hds3CmdStatus?
This read-write command/status register drives configuration changes for the HDS-3 port row: an admin SETs a command code like update-link-config(1), and the agent overwrites it with a response code such as update-successful(201) or a numbered error like err-invalid-link-op-mode(407). Checking this value after a SET confirms whether the port change actually took effect.
Examples
Walk all instances (SNMPv2c):
snmpwalk -v2c -c public <target> 1.3.6.1.4.1.644.2.4.2.2.1.1.1.26 snmpwalk -v2c -c public <target> ERI-DNX-HDS3-MIB::hds3CmdStatus
Get a specific instance (index 1):
snmpget -v2c -c public <target> 1.3.6.1.4.1.644.2.4.2.2.1.1.1.26.1 snmpget -v2c -c public <target> ERI-DNX-HDS3-MIB::hds3CmdStatus.1
Set instance 1 (SNMPv2c):
snmpset -v2c -c private <target> 1.3.6.1.4.1.644.2.4.2.2.1.1.1.26.1 s <value>
SNMPv3 example:
snmpget -v3 -l authPriv -u snmpv3-user -a SHA -A "AuthPassword1" -x AES -X "PrivPassword1" <target> hds3CmdStatus.1
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::hds3CmdStatus 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 OID | Name | Module |
|---|---|---|
| 1 | iso | LANART-AGENT |
| 1.3 | org | AirPair-MIB |
| 1.3.6 | dod | AirPair-MIB |
| 1.3.6.1 | internet | AirPair-MIB |
| 1.3.6.1.4 | private | AirPair-MIB |
| 1.3.6.1.4.1 | enterprises | AirPair-MIB |
| 1.3.6.1.4.1.644 | eriEnterpriseRoot | ERI-ROOT-SMI |
| 1.3.6.1.4.1.644.2 | eriProducts | ERI-ROOT-SMI |
| 1.3.6.1.4.1.644.2.4 | dnx | ERI-DNX-SMC-MIB |
| 1.3.6.1.4.1.644.2.4.2 | devices | ERI-DNX-SMC-MIB |
| Numeric OID | Name | Module |
|---|---|---|
| 1.3.6.1.4.1.644.2.4.2.2 | dnxHDS3 | ERI-DNX-HDS3-MIB |
| 1.3.6.1.4.1.644.2.4.2.2.1 | hds3Config | ERI-DNX-HDS3-MIB |
| 1.3.6.1.4.1.644.2.4.2.2.1.1 | hds3PortConfigTable | ERI-DNX-HDS3-MIB |
| 1.3.6.1.4.1.644.2.4.2.2.1.1.1 | hds3PortConfigEntry | ERI-DNX-HDS3-MIB |
| 1.3.6.1.4.1.644.2.4.2.2.1.1.1.26 | hds3CmdStatus | ERI-DNX-HDS3-MIB |