CISCO-CABLE-AVAILABILITY-MIB
This is the MIB module for management of Hot Standby
Connection to Connection Protocol (HCCP) features. HCCP is
a Cisco proprietary solution for High System Availability
for Cable Modem Termination Systems (CMTS).
The HCCP protocol is primarily responsible for failure
detection and to initiate switchover from one CMTS to
another.
The CMTS protection is at the RF mac domain level,
where protecting and working CMTS cable interfaces operate
on the same downstream and upstream frequency.
HCCP Terminology:
HCCP group: A set of RF MAC interfaces which communicate
using HCCP messaging.
HCCP member: Each RF MAC interface configured for HCCP.
Protect: A member in a HCCP group which acts as the
hot standby and protecting other members.
Working: The member in a HCCP group that is being
protected.
Thus a 'HCCP group' consists of 'HCCP members' which are
RF MAC interfaces configured to function as 'Protect' or
'Working'.
Some RF mac interfaces are configured to form a
'HCCP group' and members within one 'HCCP group'
communicate with each other using HCCP messaging.
By HCCP messaging, some member acting as 'Protect' or
hot standby can detect a failure on the other members
which are designated as 'Working' in the same HCCP group.
The 'Protect' can then take over traffic on the failed
interface.
Protection scenarios can be N+1 or 1+1. In the N+1
protection scenario, there is only one CMTS designated
for protection of N CMTS.
For example in 1+1 : When one linecard fails, the other
automatically takes over its traffic. During normal
operation, only one linecard forwards traffic, the other
linecard stands by and listens to the messages passed
from the active one. While in the standby mode, the
linecard does not forward traffic. HCCP will automatically
switchover to the standby in cases of software failures
(crash), linecard insertion/removal, interface shutdowns
and cable wiring failures etc.
Both Protect and Working are preconfigured on the CMTS
and all HCCP configuration must comply with the actual
cable plant deployment for correct operation of the HCCP
protocol.
This MIB includes objects to support the HCCP feature
on the CMTS.
- Source file
CISCO-CABLE-AVAILABILITY-MIB- Last revised
- Identity
ciscoCableAvailabilityMIB- Base OID
1.3.6.1.4.1.9.9.242
Imported Objects
| CISCO-SMI | ciscoMgmt |
| IF-MIB | ifIndex |
| INET-ADDRESS-MIB | InetAddress InetAddressType |
| SNMP-FRAMEWORK-MIB | SnmpAdminString |
| SNMPv2-CONF | MODULE-COMPLIANCE (no object page) NOTIFICATION-GROUP (no object page) OBJECT-GROUP (no object page) |
| SNMPv2-SMI | Counter32 Integer32 MODULE-IDENTITY (no object page) NOTIFICATION-TYPE (no object page) OBJECT-TYPE (no object page) |
| SNMPv2-TC | DisplayString TruthValue |
Net-SNMP examples using the cisco MIB directory Show commands
These commands use the standard Observium installation path and load the selected MIB variant before the RFC and Net-SNMP directories.
Translate the module identity
/usr/bin/snmptranslate -Pud -Ir -On -m 'CISCO-CABLE-AVAILABILITY-MIB' -M '/opt/observium/mibs/cisco:/opt/observium/mibs/rfc:/opt/observium/mibs/net-snmp' 'CISCO-CABLE-AVAILABILITY-MIB::ciscoCableAvailabilityMIB'
Walk the MIB subtree
/usr/bin/snmpbulkwalk -v2c -c '<community>' -Pud -Ir -OQUs -m 'CISCO-CABLE-AVAILABILITY-MIB' -M '/opt/observium/mibs/cisco:/opt/observium/mibs/rfc:/opt/observium/mibs/net-snmp' 'udp:<hostname>:161' 'CISCO-CABLE-AVAILABILITY-MIB::ciscoCableAvailabilityMIB'
Objects (52)
Showing 52 of 52 objects
Object legend
Object type
Icons distinguish tables, entry rows, columns, scalars, and structural nodes.
SNMPv2-TCTruthValue
Syntax
Blue badges identify the value syntax. Connected badges read as defining module and convention.
IF-MIBifIndex
Table index
Green identifies an index object; yellow names its module when the index is defined elsewhere.
r/w
deprecated
obsolete
Access and status
r/w means read-write. Grey labels mark definitions retained for compatibility.
OBS ✓
Observium use
The indicator appears only when Observium directly references that object.
ifOperStatus
.1.3.6.1.2.1…
Names and OIDs
Object names link to their detail pages. Hover or focus a linked name or badge for available definition details.
.1.3.6.1.4.1.9.9.242 |
||
.1.3.6.1.4.1.9.9.242.1 |
||
.1.3.6.1.4.1.9.9.242.1.1 |
||
|
Enumeration
|
.1.3.6.1.4.1.9.9.242.1.1.1 |
|
.1.3.6.1.4.1.9.9.242.1.1.2 |
||
.1.3.6.1.4.1.9.9.242.1.1.2.1 |
||
|
Integer32
|
.1.3.6.1.4.1.9.9.242.1.1.2.1.1 |
|
|
Enumeration
|
.1.3.6.1.4.1.9.9.242.1.1.2.1.2 |
|
.1.3.6.1.4.1.9.9.242.1.1.2.1.3 |
||
|
millisecondsInteger32
|
.1.3.6.1.4.1.9.9.242.1.1.2.1.4 |
|
|
millisecondsInteger32
|
.1.3.6.1.4.1.9.9.242.1.1.2.1.5 |
|
.1.3.6.1.4.1.9.9.242.1.1.2.1.6 |
||
.1.3.6.1.4.1.9.9.242.1.1.2.1.7 |
||
.1.3.6.1.4.1.9.9.242.1.1.2.1.8 |
||
.1.3.6.1.4.1.9.9.242.1.1.3 |
||
.1.3.6.1.4.1.9.9.242.1.1.3.1 |
||
|
Enumeration
|
.1.3.6.1.4.1.9.9.242.1.1.3.1.1 |
|
|
Integer32
|
.1.3.6.1.4.1.9.9.242.1.1.3.1.2 |
|
.1.3.6.1.4.1.9.9.242.1.1.3.1.3 |
||
|
Enumeration
|
.1.3.6.1.4.1.9.9.242.1.1.3.1.4 |
|
|
Enumeration
|
.1.3.6.1.4.1.9.9.242.1.1.3.1.5 |
|
.1.3.6.1.4.1.9.9.242.1.1.3.1.6 |
||
.1.3.6.1.4.1.9.9.242.1.1.3.1.7 |
||
.1.3.6.1.4.1.9.9.242.1.1.4 |
||
.1.3.6.1.4.1.9.9.242.1.1.4.1 |
||
|
Integer32
|
.1.3.6.1.4.1.9.9.242.1.1.4.1.1 |
|
|
OctetString
|
.1.3.6.1.4.1.9.9.242.1.1.4.1.2 |
|
.1.3.6.1.4.1.9.9.242.1.1.5 |
||
.1.3.6.1.4.1.9.9.242.1.1.5.1 |
||
|
Integer32
|
.1.3.6.1.4.1.9.9.242.1.1.5.1.1 |
|
.1.3.6.1.4.1.9.9.242.1.1.5.1.2 |
||
.1.3.6.1.4.1.9.9.242.1.1.5.1.3 |
||
|
Enumeration
|
.1.3.6.1.4.1.9.9.242.1.1.5.1.4 |
|
.1.3.6.1.4.1.9.9.242.1.1.5.1.5 |
||
.1.3.6.1.4.1.9.9.242.1.1.6 |
||
.1.3.6.1.4.1.9.9.242.1.1.6.1 |
||
|
Integer32
|
.1.3.6.1.4.1.9.9.242.1.1.6.1.1 |
|
.1.3.6.1.4.1.9.9.242.1.1.6.1.10 |
||
|
Enumeration
|
.1.3.6.1.4.1.9.9.242.1.1.6.1.2 |
|
.1.3.6.1.4.1.9.9.242.1.1.6.1.3 |
||
.1.3.6.1.4.1.9.9.242.1.1.6.1.4 |
||
|
Integer32
|
.1.3.6.1.4.1.9.9.242.1.1.6.1.5 |
|
.1.3.6.1.4.1.9.9.242.1.1.6.1.6 |
||
.1.3.6.1.4.1.9.9.242.1.1.6.1.7 |
||
|
Integer32
|
.1.3.6.1.4.1.9.9.242.1.1.6.1.8 |
|
|
Integer32
|
.1.3.6.1.4.1.9.9.242.1.1.6.1.9 |
|
.1.3.6.1.4.1.9.9.242.1.1.7 |
||
.1.3.6.1.4.1.9.9.242.2 |
||
.1.3.6.1.4.1.9.9.242.2.0 |
||
.1.3.6.1.4.1.9.9.242.3 |
||
.1.3.6.1.4.1.9.9.242.3.1 |
||
.1.3.6.1.4.1.9.9.242.3.2 |
Dependencies (9) 7 direct · 2 transitive Show tree and compile order Hide dependency details
Each imported module is resolved in the importing module's source directory first, then through the normal default-variant rules.
Dependency tree
Dependency-first compile order
- SNMPv2-SMIrfc
- CISCO-SMIcisco
- SNMPv2-TCrfc
- IANAifType-MIBrfc
- SNMPv2-CONFrfc
- SNMPv2-MIBrfc
- IF-MIBrfc
- INET-ADDRESS-MIBrfc
- SNMP-FRAMEWORK-MIBrfc
- CISCO-CABLE-AVAILABILITY-MIBciscoselected
Conformance Groups (3)
Compliance Statements (2)
OID
.1.3.6.1.4.1.9.9.242.3.1.1The compliance statement for CMTS devices that implement
the Hot Standby Connection to Connection Protocol.
the Hot Standby Connection to Connection Protocol.
Required groups
| mandatory | ccaHCCPGroup | |
| mandatory | ccaHCCPMemberGroup | |
| mandatory | ccaHCCPNotificationGroup |
OID
.1.3.6.1.4.1.9.9.242.3.1.2The compliance statement for CMTS devices that implement
the Hot Standby Connection to Connection Protocol.
the Hot Standby Connection to Connection Protocol.
Required groups
| mandatory | ccaHCCPGroup | |
| mandatory | ccaHCCPMemberGroup | |
| mandatory | ccaHCCPNotificationGroup |
Object refinements
| Object | Access | Syntax | Description |
|---|---|---|---|
| ccaHCCPMemChanSwitchPosition | readonly | Write access is not required. |
Notifications / Traps (2)
| Name | OID | Description |
|---|---|---|
.1.3.6.1.4.1.9.9.242.2.0.1 |
A notification that is sent when failover occurred and
this interface is taking over the traffic from the peer. For example if Protect is taking over a Working member from it's protection group,this notification is sent by the Protect. When Working is restored to operation and is now taking over from the Protect, this notification is sent by Working. |
|
.1.3.6.1.4.1.9.9.242.2.0.2 |
A notification that is sent when failover occurs and this
interface is turning over all traffic to it's peer and is now blocking. For example if Protect is taking over a Working member from it's protection group,this notification is sent by the Working. When Working is restored to operation and is now taking over from the Protect, this notification is sent by Protect. |