All MIBs › RDN-CMTS-MIB › rdnIfCmtsCmStatusValue
rdnIfCmtsCmStatusValue
Module: RDN-CMTS-MIB
OID (symbolic): RDN-CMTS-MIB::rdnIfCmtsCmStatusValue
OID (numeric): 1.3.6.1.4.1.4981.2.2.8.1.9
Node type: OBJECT-TYPE
Type: INTEGER
Access: read-only
Description: Current Cable Modem connectivity state. Returned status information is the CM status as assumed by the CMTS, and indicates the following events:
init-o(1) Option file transfer was started. init-t(2) Time-of-day (TOD) exchange was started. init-r1(3) CM sent initial ranging parameters. init-r2(4) CM is ranging. init-rc(5) Ranging is complete. dhcp-d (6) DHCP Discover was sent by CM. dhcp-o (7) DHCP Offer was received. dhcp-req(8) DHCP Request was sent by CM. dhcp-ack(9) DHCP Ack was received, IP address was assigned by DHCP server. online(10) CM registered; enabled for data. online-d(11) CM registered, but network access for the CM is disabled. online-un(12) CM registered, but not enabled data. Fail to verify modems Identity by BPI module. online-pk(13) CM registered; baseline privacy interface (BPI) enabled, and key encryption key (KEK)is assigned. online-pt(14) CM registered; BPI enabled, and traffic encryption key (TEK) is assigned. reject-m(15) CM did attempt to register; registration was refused due to bad mic. reject-c(16) CM did attempt to register; registration was refused due to bad COS. reject-r(17) CM did attempt to register, registration was refused due to unavailable resource. reject-pk(18) KEK modem key assignment is rejected. reject-pt(19) TEK modem key assignment is rejected. offline(20) CM is considered to be offline.
What is rdnIfCmtsCmStatusValue?
Read-only enumeration reporting a cable modem's detailed connectivity state as tracked by the CMTS, spanning DOCSIS provisioning stages from init-o (option file transfer) through dhcp-ack, to online/online-d/online-pk/online-pt (registered, with varying BPI encryption states), several reject-* failure states, and offline. Admins read this to pinpoint exactly where in the provisioning process a problem modem is stuck, e.g. reject-m indicating a bad MIC (likely a config file or shared-secret mismatch) versus dhcp-d meaning it never got past sending a DHCP Discover.
Examples
Walk all instances (SNMPv2c):
snmpwalk -v2c -c public <target> 1.3.6.1.4.1.4981.2.2.8.1.9 snmpwalk -v2c -c public <target> RDN-CMTS-MIB::rdnIfCmtsCmStatusValue
Get a specific instance (index 1):
snmpget -v2c -c public <target> 1.3.6.1.4.1.4981.2.2.8.1.9.1 snmpget -v2c -c public <target> RDN-CMTS-MIB::rdnIfCmtsCmStatusValue.1
Start monitoring Motorola CMTS platforms (upstream/downstream channel config, cable-modem registration/reset) with a free 30-day trial of IPNetwork Monitor. Create custom SNMP monitor using the RDN-CMTS-MIB::rdnIfCmtsCmStatusValue OID value, configure state conditions and alerts, and monitor any Motorola CMTS platforms (upstream/downstream channel config, cable-modem registration/reset) from a single console.
OID Breakdown
Upper-level ancestors (7 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.4981 | riverdelta | RDN-MIB |
| Numeric OID | Name | Module |
|---|---|---|
| 1.3.6.1.4.1.4981.2 | rdnCmtsMib | RDN-CMTS-MIB |
| 1.3.6.1.4.1.4981.2.2 | rdnCmtsMiscObjects | RDN-CMTS-MIB |
| 1.3.6.1.4.1.4981.2.2.8 | rdnIfCmtsCmStatusTable | RDN-CMTS-MIB |
| 1.3.6.1.4.1.4981.2.2.8.1 | rdnIfCmtsCmStatusEntry | RDN-CMTS-MIB |
| 1.3.6.1.4.1.4981.2.2.8.1.9 | rdnIfCmtsCmStatusValue | RDN-CMTS-MIB |