Event Notification Management Information Base for Data over Cable Service Interface Specifications (DOCSIS)-Compliant Cable Modems and Cable Modem Termination Systems
updated by
- rfc-9141 — Updating References to the IETF FTP Service
Extracted elements (22)
The MIB maps DOCSIS events (defined in Appendix H of DOCSIS 1.1 OSSI and Appendix D of DOCSIS 2.0 OSSI) to notification objects organized by functional category rather than individual event, so that one SNMP notification type covers an entire event category and the specific event details are carried in varbindings.
Notifications defined in this MIB are also subject to the notification control mechanisms defined in RFC 3413 (SNMP Applications), meaning both docsDevCmNotifControl/docsDevCmtsNotifControl and RFC 3413 controls must be satisfied for a notification to be emitted.
Deployment of SNMP versions prior to SNMPv3 is NOT RECOMMENDED; implementers SHOULD use SNMPv3 with full cryptographic mechanisms (authentication and privacy) to protect access to this MIB.
DOCSIS devices SHOULD support a minimum set of standard DOCSIS Notifications to enable successful management of DOCSIS devices and networks, as defined in conjunction with DOCSIS OSSI specifications.
If the device is rebooted, the value of docsDevCmtsNotifControl SHOULD revert to the default value (empty bit string, all notifications disabled).
docsDevCmBpiInitNotif reports BPI initialization failure during CM registration; docsDevCmBPKMNotif reports Baseline Privacy Key Management (BPKM) operation failure; both carry the standard CM varbinding set.
docsDevCmDCCReqFailNotif, docsDevCmDCCRspFailNotif, and docsDevCmDCCAckFailNotif report failures in the three-way Dynamic Channel Change request/response/acknowledgement handshake as detected on the CM, each carrying the standard CM varbinding set.
docsDevCmDHCPFailNotif reports DHCP operation failure on the CM; its varbinding list extends the standard CM set with docsDevServerDhcp (IP address of the DHCP server).
docsDevCmDynamicSANotif reports failure of a dynamic security association operation on the CM, carrying the standard CM varbinding set including DOCSIS capability and modulation type.
docsDevCmDynServReqFailNotif, docsDevCmDynServRspFailNotif, and docsDevCmDynServAckFailNotif report failures in the three-way dynamic service request/response/acknowledgement handshake on the CM side, each carrying the standard CM varbinding set.
docsDevCmInitTLVUnknownNotif reports that an unknown TLV was encountered during TLV parsing; varbindings include docsDevEvLevel, docsDevEvId, docsDevEvText, ifPhysAddress (CM MAC), docsIfCmCmtsAddress, docsIfDocsisBaseCapability, docsIfCmStatusDocsisOperMode, and docsIfCmStatusModulationType.
docsDevCmNotifControl is a read-write BITS object with 16 named bits (cmInitTLVUnknownNotif through cmDCCAckFailNotif) used to individually enable or disable each CM notification type; the default value is the empty set (all disabled).
docsDevCmSwUpgradeCVCFailNotif reports that code file verification failed during a secure software upgrade attempt, using the standard CM varbinding set without the software filename/server fields.
docsDevCmSwUpgradeInitNotif, docsDevCmSwUpgradeFailNotif, and docsDevCmSwUpgradeSuccessNotif report software upgrade initiation, failure, and success respectively; each extends the standard varbindings with docsDevSwFilename and docsDevSwServer.
docsDevCmTODFailNotif reports failure of a time-of-day operation on the CM; its varbindings extend the standard CM set with docsDevServerTime (IP address of the time server).
docsDevCmtsBpiInitNotif and docsDevCmtsBPKMNotif report BPI initialization failure and BPKM operation failure as detected by the CMTS, each carrying CMTS-side varbindings including the CM's MAC address and DOCSIS registration mode.
docsDevCmtsDynamicSANotif reports failure of a dynamic security association operation as detected by the CMTS; docsDevCmtsDCCReqFailNotif, docsDevCmtsDCCRspFailNotif, and docsDevCmtsDCCAckFailNotif report DCC handshake failures detected by the CMTS.
docsDevCmtsNotifControl is a read-write BITS object with 12 named bits (cmtsInitRegReqFailNotif through cmtsDCCAckFailNotif) used to individually enable or disable each CMTS notification type; the default value is the empty set (all disabled).
The CMTS notification group defines parallel counterparts to CM notifications: docsDevCmtsInitRegReqFailNotif, docsDevCmtsInitRegRspFailNotif, and docsDevCmtsInitRegAckFailNotif report registration handshake failures as detected by the CMTS, with varbindings including docsIfCmtsCmStatusMacAddress (CM's MAC) and ifPhysAddress (CMTS cable interface MAC).
IANA assigned OID { mib-2 132 } (docsDevNotifMIB) in the SMI Numbers registry for this MIB module.
Notification messages expose sensitive device information (event priority, event ID, CM DOCSIS capability, QOS level, upstream modulation type, CM cable interface MAC address, and CMTS cable card MAC address) that could be harvested to map the network topology.
Setting docsDevCmNotifControl or docsDevCmtsNotifControl without access control can flood the network with notifications (disrupting service) or suppress notifications (masking failures); both objects have MAX-ACCESS read-write and must be protected.