CT-DAREGISTRY-MIB :: ctDARegistryOperStatus

MIB Reference — IPNetwork Monitor · Updated October 05, 2026

All MIBs › CT-DAREGISTRY-MIB › ctDARegistryOperStatus

ctDARegistryOperStatus

Module: CT-DAREGISTRY-MIB

OID (symbolic): CT-DAREGISTRY-MIB::ctDARegistryOperStatus

OID (numeric): 1.3.6.1.4.1.52.4497.1.1.4

Node type: OBJECT-TYPE

Type: INTEGER

Access: read-only

Description: The mandatory operational state of the subsystem. The testing(3) state indicates that no operational functions can be passed. If ctDARegistryAdminStatus is down(2) then ctDARegistryOperStatus should be down(2). If ctDARegistryAdminStatus is changed to up(1) then ctDARegistryOperStatus should change to up(1) if the subsystem is ready to function; it should change to dormant(5) if the subsystem is waiting for external actions; it should remain in the down(2) state if and only if there is a fault that prevents if from going to the up(1) state. The notPresent state is a refinement on the down state which indicates that the relevant interface is down specifically because some component (typically, a hardware component) is not present in the managed system. The lowerLayerDown state is also a refinement on the down state. This new state indicates that this system runs on top of one or more interfaces (see ifStackTable) and that this system is down specifically because one or more of these lower-layer interfaces are down.

What is ctDARegistryOperStatus?

This read-only INTEGER reports the mandatory operational state of the subsystem, which must be down(2) whenever ctDARegistryAdminStatus is down(2), and which becomes up(1) or dormant(5), waiting on some condition, once admin status is set to up(1). An admin polls this to verify whether a subsystem that was administratively enabled has actually become operational. For example, if admin status was set to up(1) but this object remains dormant(5), the admin knows the subsystem is still waiting on a dependency before it can fully activate.

Examples

Walk all instances (SNMPv2c):

snmpwalk -v2c -c public <target> 1.3.6.1.4.1.52.4497.1.1.4
snmpwalk -v2c -c public <target> CT-DAREGISTRY-MIB::ctDARegistryOperStatus

Get a specific instance (index 1):

snmpget -v2c -c public <target> 1.3.6.1.4.1.52.4497.1.1.4.1
snmpget -v2c -c public <target> CT-DAREGISTRY-MIB::ctDARegistryOperStatus.1

Start monitoring Legacy Cabletron Demand Access WAN equipment with a free 30-day trial of IPNetwork Monitor. Create custom SNMP monitor using the CT-DAREGISTRY-MIB::ctDARegistryOperStatus OID value, configure state conditions and alerts, and monitor any Legacy Cabletron Demand Access WAN equipment from a single console.

OID Breakdown

Upper-level ancestors (8 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.52cabletronCabletron-MIB
1.3.6.1.4.1.52.4497ctSSACT-DARADIUS-MIB
Numeric OIDNameModule
1.3.6.1.4.1.52.4497.1ctDARegistryTableCT-DAREGISTRY-MIB
1.3.6.1.4.1.52.4497.1.1ctDARegistryEntryCT-DAREGISTRY-MIB
1.3.6.1.4.1.52.4497.1.1.4ctDARegistryOperStatusCT-DAREGISTRY-MIB