CISCO-WIRELESS-DOCS-EXT-MIB :: cwdxHeSuChOverState

MIB Reference — IPNetwork Monitor · Updated September 14, 2026

All MIBsCISCO-WIRELESS-DOCS-EXT-MIBcwdxHeSuChOverState

cwdxHeSuChOverState

Module: CISCO-WIRELESS-DOCS-EXT-MIB

OID (symbolic): CISCO-WIRELESS-DOCS-EXT-MIB::cwdxHeSuChOverState

OID (numeric): 1.3.6.1.4.1.9.9.169.1.3.6.1.7

Node type: OBJECT-TYPE

Type: INTEGER

Access: read-only

Description: The status of the specified channel override operation. The enumerations are: messageSent(1): the HE has sent a RNG-RSP message with channel override to the Subscriber-unit. commandNotActive(2): the command is not in active mode due to this entry's row status is not in active yet. noOpNeeded(3): The downstream frequency and the upstream channel Id in this entry are the same as original ones when this entry's row status is set to active, so HE does not need to do any operation. SuNotFound(4): The SU is not found in the HE at the time when the command becomes active. waitToSendMessage(5): specified the operation is active and HE is waiting to send a RNG-RSP message with channel override to the Subscriber-unit. timeOut(6): specified the operation is timed out. That is, the HE cannot send a RNG-RSP message with channel override to the Subscriber-unit within the time specified in the object of cwdxHeSuChOverTimeExpiration. The possible reason is that the Subscriber-unit does not repeat the initial ranging.

The possible state change diagram is as below: [commandNotActive ->] waitToSendMessage -> messageSent or timeOut. [commandNotActive ->] noOpNeeded or SuNotFound.

What is cwdxHeSuChOverState?

This read-only object reports the current status of a channel-override operation, such as whether the RNG-RSP message with channel override has been sent, the command isn't active yet, no operation was needed, the SU wasn't found, or the attempt timed out. Admins check this to determine whether a manually issued channel move actually succeeded or is stuck. For example, seeing cwdxHeSuChOverState report suNotFound(4) would tell an admin the MAC address they specified isn't currently registered at the headend, explaining why the channel move never took effect.

Examples

Walk all instances (SNMPv2c):

snmpwalk -v2c -c public <target> 1.3.6.1.4.1.9.9.169.1.3.6.1.7
snmpwalk -v2c -c public <target> CISCO-WIRELESS-DOCS-EXT-MIB::cwdxHeSuChOverState

Get a specific instance (index 1):

snmpget -v2c -c public <target> 1.3.6.1.4.1.9.9.169.1.3.6.1.7.1
snmpget -v2c -c public <target> CISCO-WIRELESS-DOCS-EXT-MIB::cwdxHeSuChOverState.1

Start monitoring Cisco DOCSIS headend devices with a free 30-day trial of IPNetwork Monitor. Create custom SNMP monitor using the CISCO-WIRELESS-DOCS-EXT-MIB::cwdxHeSuChOverState OID value, configure state conditions and alerts, and monitor any Cisco DOCSIS headend devices 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.9ciscoCAT2600-MIB
1.3.6.1.4.1.9.9ciscoMgmtCISCO-SMI
Numeric OIDNameModule
1.3.6.1.4.1.9.9.169ciscoWirelessDocsExtMIBCISCO-WIRELESS-DOCS-EXT-MIB
1.3.6.1.4.1.9.9.169.1ciscoWirelessDocsExtMIBObjectsCISCO-WIRELESS-DOCS-EXT-MIB
1.3.6.1.4.1.9.9.169.1.3cwdxHeSuCpeObjectsCISCO-WIRELESS-DOCS-EXT-MIB
1.3.6.1.4.1.9.9.169.1.3.6cwdxHeSuChOverTableCISCO-WIRELESS-DOCS-EXT-MIB
1.3.6.1.4.1.9.9.169.1.3.6.1cwdxHeSuChOverEntryCISCO-WIRELESS-DOCS-EXT-MIB
1.3.6.1.4.1.9.9.169.1.3.6.1.7cwdxHeSuChOverStateCISCO-WIRELESS-DOCS-EXT-MIB