Home/Catalog/CISCO-CABLE-AVAILABILITY-MIB

CISCO-CABLE-AVAILABILITY-MIB

AI MIB Summary

The CISCO-CABLE-AVAILABILITY-MIB manages the Hot Standby Connection to Connection Protocol (HCCP) on Cisco Cable Modem Termination Systems (CMTS) to monitor RF MAC interface states within HCCP groups and execute automatic traffic failover between Protect and Working members. It tracks specific failure conditions such as linecard crashes, interface shutdowns, and wiring faults to trigger switchover in N+1 or 1+1 redundancy configurations.

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.
Main OID:
ciscoCableAvailabilityMIB.1.3.6.1.4.1.9.9.242
54
Objects
Active
Status
7
Dependencies

Imported Objects

Objects

54 total
Object Name
ciscoCableAvailabilityMIBThis 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.
MODULE-IDENTITY
.1.3.6.1.4.1.9.9.242
ciscoCableAvailabilityMIBObjects
OBJECT IDENTIFIER
.1.3.6.1.4.1.9.9.242.1
ccaHCCPObjects
OBJECT IDENTIFIER
.1.3.6.1.4.1.9.9.242.1.1
ccaHCCPVersionThe current version of HCCP features. others(1) : Any other HCCP Version other than the following list. version1(2) : HCCP Version 1.0 supports for 1+1 Availability. (1 RF MAC protecting 1 RF MAC without load sharing on the same upstream and downstream frequencies with DOCSIS1.0+ features) version2(3) : HCCP Version 2.0 supports for 1+1 Availability. (1 RF MAC protecting 1 RF MAC without load sharing on the same upstream and downstream frequencies with DOCSIS1.1 features) version3(4) : HCCP Version 3.0 supports for N+1 Availability. (1 RF MAC protecting N RF MAC without load sharing on different upstream and downstream frequencies with DOCSIS1.1 features).ro
Enumeration
.1.3.6.1.4.1.9.9.242.1.1.1
ccaHCCPGroupTableThis table contains information of the HCCP groups on the CMTS. A HCCP group consists of a set of Working along with a Protect and each group is identified by a unique group ID number. Only members within a group are allowed to communicate with each other via HCCP messaging.
SEQUENCE OF CcaHCCPGroupEntry
.1.3.6.1.4.1.9.9.242.1.1.2
ccaHCCPGroupEntryA set of attributes of a HCCP group on the CMTS. An entry in this table exists for each configured HCCP group on the CMTS.
CcaHCCPGroupEntry
.1.3.6.1.4.1.9.9.242.1.1.2.1
ccaHCCPGroupIDIdentification of the HCCP protection group. Only members of the same group talk to each other via HCCP messaging.
Integer32
.1.3.6.1.4.1.9.9.242.1.1.2.1.1
ccaHCCPGroupAuthenticationThe value of this object specifies the type of authentication method used. none(1) : No authentication is performed on that group. md5(2) : The MD5 Message Digest algorithm. text(3) : Authentication based on a textual string.ro
Enumeration
.1.3.6.1.4.1.9.9.242.1.1.2.1.2
ccaHCCPGroupAuthKeyChainThis object is the name of a globally configured key chain. It is used to enable authentication and determine the set of keys which may be used on a particular group. If ccaHCCPGroupAuthentication is text(3), it is used as the authentication password. If ccaHCCPGroupAuthentication is md5(2), it is used as the message digest for md5. If a key chain has not been configured, no authentication is performed on that group.ro
SnmpAdminString (SNMP-FRAMEWORK-MIB)
.1.3.6.1.4.1.9.9.242.1.1.2.1.3
ccaHCCPGroupHelloTimeHello time is the interval(in milliseconds) between consecutive HELLO messages. HELLO is a one-way message in HCCP sent from Protect to all Working in the group. It indicates that Protect is ready to receive data and expects HELLO_ACK. HELLO message indicates the existence and state of Protect. Failing to send this message indicates Protect is not in service.ro
Integer32
.1.3.6.1.4.1.9.9.242.1.1.2.1.4
ccaHCCPGroupHoldTimeHold time is the interval(in milliseconds) between the time of receiving the last HELLO ACK message and the time to assume that the cable interface is out of service. In the case of Working, it is the interval in milliseconds between the time when the Working receives a HELLO message and the time to assume that Protect has failed. In the case of Protect, it is the interval in milliseconds between the time when the Protect sends last HELLO message without seeing HELLO_ACK and the time to assume that Working has failed. It is carried by HELLO message and is used by Protect and all Working.ro
Integer32
.1.3.6.1.4.1.9.9.242.1.1.2.1.5
ccaHCCPGroupRevertEnableEnable or disable the Protect to revert switchover after Working is restored to operation. It can be disabled (default) if user wants to perform some tests before revert switching.ro
TruthValue (SNMPv2-TC)
.1.3.6.1.4.1.9.9.242.1.1.2.1.6
ccaHCCPGroupProtectIpAddrTypeThe type of internet address of ccaHCCPGroupProtectIpAddress.ro
InetAddressType (INET-ADDRESS-MIB)
.1.3.6.1.4.1.9.9.242.1.1.2.1.7
ccaHCCPGroupProtectIpAddressThe IP address of the Protect interface for the group that sends the HELLO message.ro
InetAddress (INET-ADDRESS-MIB)
.1.3.6.1.4.1.9.9.242.1.1.2.1.8
ccaHCCPGroupIfTableThis table provides the mapping of the RF MAC interfaces on the CMTS to its functionality in the HCCP group. It indicates if the RF MAC interface has been configured as Protect or as a Working.It provides interface specific configuration and state information as well as statistics.
SEQUENCE OF CcaHCCPGroupIfEntry
.1.3.6.1.4.1.9.9.242.1.1.3
ccaHCCPGroupIfEntryA mapping of a RF MAC interface to its configured functionality as Protect or Working. It provides interface specific configuration and state information as well as statistics. Entries in this table exist for each ifEntry with ifType of docsCableUpstream(129).
CcaHCCPGroupIfEntry
.1.3.6.1.4.1.9.9.242.1.1.3.1
ccaHCCPGroupIfStatusThe value of this object identifies if the interface is functioning as Working or Protect in the HCCP group.ro
Enumeration
.1.3.6.1.4.1.9.9.242.1.1.3.1.1
ccaHCCPGroupIfRevertTimeRevert time used by Working specifies the time interval to wait before automatic revert switching. Within that time interval, manual switchover is allowed to happen.ro
Integer32
.1.3.6.1.4.1.9.9.242.1.1.3.1.2
ccaHCCPGroupIfTrackEnableEnable or disable failover based on interface state. The interface can be any interface on the router, which is monitored by keep alive timer. If it is set to true, ccaHCCPGroupTrackInterfaceTable contains the list of interfaces that are being tracked. By default the current interface is under tracking.ro
TruthValue (SNMPv2-TC)
.1.3.6.1.4.1.9.9.242.1.1.3.1.3
ccaHCCPGroupIfStateThe current state of the HCCP group. The members can either be forwarding traffic or blocking all traffic.ro
Enumeration
.1.3.6.1.4.1.9.9.242.1.1.3.1.4
ccaHCCPGroupIfLastSwitchReasonThe reason for last switch. none(1) : No switchover has occurred. holdTimeExpire(2) : Occurs when HCCP fails to hear HELLO/HELLO_ACK and the hold time expires. hwIfDown(3) : Occurs when the hardware interface is down. (eg shut/no shut) failTest(3) : Failover was CLI initiated or SNMP initiated through ccaHCCPGroupSwitchNow. failLinkDown(4) : Failure in the cable wiring or a hardware interface. failBundleDown(5) : A bundled interface failure. internal(6) : All other failures .ro
Enumeration
.1.3.6.1.4.1.9.9.242.1.1.3.1.5
ccaHCCPGroupIfOnTransitionsNumber of times the value of ccaHCCPGroupIfState transitioned from 'blocking' to 'forwarding'.ro
Counter32
.1.3.6.1.4.1.9.9.242.1.1.3.1.6
ccaHCCPGroupIfOffTransitionsNumber of times the value of ccaHCCPGroupIfState transitioned from 'forwarding' to 'blocking'.ro
Counter32
.1.3.6.1.4.1.9.9.242.1.1.3.1.7
ccaHCCPGroupTrackInterfaceTableThis table contains the attributes of all the interfaces that are being tracked by this group. The interface can be any interface on the chassis, which is monitored by a keep alive timer.
SEQUENCE OF CcaHCCPGroupTrackInterfaceEntry
.1.3.6.1.4.1.9.9.242.1.1.4
ccaHCCPGroupTrackInterfaceEntryA set of attributes of an interfaces being tracked within a group.
CcaHCCPGroupTrackInterfaceEntry
.1.3.6.1.4.1.9.9.242.1.1.4.1
ccaHCCPGroupTrackIfIDThe value of this object uniquely identifies an interface that is being tracked within this group.
Integer32
.1.3.6.1.4.1.9.9.242.1.1.4.1.1
ccaHCCPGroupTrackIfDescrA textual string containing information about the interface that is being tracked. This corresponds to the ifDescr of the tracked interface.ro
DisplayString
.1.3.6.1.4.1.9.9.242.1.1.4.1.2
ccaHCCPMemberTableThis table contains the attributes of HCCP members. Each RF MAC interface configured for HCCP is called a HCCP member. Entries in this table are created for all members. In the case of Protect, it gives information of all the Working members under it's protection group. In the case of Working, it gives information about itself.
SEQUENCE OF CcaHCCPMemberEntry
.1.3.6.1.4.1.9.9.242.1.1.5
ccaHCCPMemberEntryA configurable attributes of a HCCP member within a group.
CcaHCCPMemberEntry
.1.3.6.1.4.1.9.9.242.1.1.5.1
ccaHCCPMemberIDThe value of this object identifies the Working member's ID inside a group. Members within the same group are uniquely identified by this ID. The ID can be reused outside the group.
Integer32
.1.3.6.1.4.1.9.9.242.1.1.5.1.1
ccaHCCPMemberIpAddrTypeThe type of internet address of ccaHCCPMemberIpAddress.ro
InetAddressType (INET-ADDRESS-MIB)
.1.3.6.1.4.1.9.9.242.1.1.5.1.2
ccaHCCPMemberIpAddressThe IP address of the member. If the member functions as Working it represents an IP address on its interface. However in case of Protect, it represents IP address of the Working member that are being protected.ro
InetAddress (INET-ADDRESS-MIB)
.1.3.6.1.4.1.9.9.242.1.1.5.1.3
ccaHCCPMemberStateThe current status of to this HCCP group member. If the RF MAC interface is Working, this represents the status of the Working member. active(1) : Working member is forwarding traffic. standby(2) : Working member is blocking traffic. If the RF MAC interface is Protect, this represents the Protect status to this member. active(1) : The Protect is taking over and forwarding the traffic from this Working member which is now blocking. standby(2) : The Protect is standby(blocking). This means that Working member is forwarding traffic and thus works fine. nonFunctional(3): This member is disabled.ro
Enumeration
.1.3.6.1.4.1.9.9.242.1.1.5.1.4
ccaHCCPMemberSwitchNowThis object is used to initiate the switchover. When it is set to true(1) and this interface is Protect, it will cause the switchover to specified Working member. When it is set to true(1), and if this interface is Working, it will cause the switchover to the Protect in it's protection group. Switchover can thus be initiated by either the Protect or the Working. Reading this object will always return false(2).rw
TruthValue (SNMPv2-TC)
.1.3.6.1.4.1.9.9.242.1.1.5.1.5
ccaHCCPMemChanSwitchTableThis is an adjunct to ccaHCCPMemberTable. It provides information of HCCP member channel switches. It specifies the RF channel switch type, the RF switch over group and the RF switch module. The upconvertor IP addresses can also be retrieved from this table. This table does not exist if no channel switch has been enabled for this member in the group.
SEQUENCE OF CcaHCCPMemChanSwitchEntry
.1.3.6.1.4.1.9.9.242.1.1.6
ccaHCCPMemChanSwitchEntryA set of attributes of the channel switch specifying the channel switch details per member (ccaHCCPMemberID) on an interface (ifType is docsCableMaclayer(127)) of a HCCP group.
CcaHCCPMemChanSwitchEntry
.1.3.6.1.4.1.9.9.242.1.1.6.1
ccaHCCPMemChanSwitchIDUniquely identifies the entry for channel switch for a member. The channel switch is the RF component that allows downstream and upstream channel switching.
Integer32
.1.3.6.1.4.1.9.9.242.1.1.6.1.1
ccaHCCPMemChanSwitchTypeType of the channel switch. others(1) : Any other channel switch which is not in the following list. ucWavecom(2) : Represents the Wavecom upconvertor. rfSwitchGrp(3) : Weinschel channel switch. If ccaHCCPMemChanSwitchModule represents the bitmap of selected modules inside a RF switch chassis. rfSwitchModule(4) : Weinschel channel switch. If ccaHCCPMemChanSwitchModule represents the switch module number inside RF switch chassis.ro
Enumeration
.1.3.6.1.4.1.9.9.242.1.1.6.1.2
ccaHCCPMemChanSwitchIpAddrTypeThe type of internet address of ccaHCCPMemChanSwitchIpAddress.ro
InetAddressType (INET-ADDRESS-MIB)
.1.3.6.1.4.1.9.9.242.1.1.6.1.3
ccaHCCPMemChanSwitchIpAddressThe Ipv4 Address of channel switch. It represents the IP address of the upconverter that this Working member connects to if ccaHCCPMemChanSwitchType is ucWavecom(2). It specifies the RF Switch's IP address if ccaHCCPMemChanSwitchType is rfSwitchGrp(3) or rfSwitchModule(4).ro
InetAddress (INET-ADDRESS-MIB)
.1.3.6.1.4.1.9.9.242.1.1.6.1.4
ccaHCCPMemChanSwitchModuleThe module number of channel switch for this member . It is the module number on the upconverter that this member connects to if ccaHCCPMemChanSwitchType is ucWavecom(2). It specifies the RF Switch module number inside an RF Switch chassis if ccaHCCPMemChanSwitchType is rfSwitchModule(4). It is the bitmap of selected modules inside a RF Switch chassis if ccaHCCPMemChanSwitchType is rfSwitchGrp(3).ro
Integer32
.1.3.6.1.4.1.9.9.242.1.1.6.1.5
ccaHCCPMemChanSwitchProtIpAddrTypeThe type of internet address of ccaHCCPMemChanSwitchProtIpAddr.ro
InetAddressType (INET-ADDRESS-MIB)
.1.3.6.1.4.1.9.9.242.1.1.6.1.6
ccaHCCPMemChanSwitchProtIpAddrThe IP address of the Wavecom upconvertor that is connected to the corresponding Protect for this Working member. This object is meaningful only if ccaHCCPMemChanSwitchType is ucWavecom(2) and has no meaning for other types of switches and is ignored in this case.ro
InetAddress (INET-ADDRESS-MIB)
.1.3.6.1.4.1.9.9.242.1.1.6.1.7
ccaHCCPMemChanSwitchProtModuleThe module number on the Wavecom upconvertor that is connected to the corresponding Protect for this Working member. This object is meaningful only if ccaHCCPMemChanSwitchType is ucWavecom(2).ro
Integer32
.1.3.6.1.4.1.9.9.242.1.1.6.1.8
ccaHCCPMemChanSwitchPositionThe position within a switch module for this Working member. This object is valid for ccaHCCPMemChanSwitchType rfSwitchGrp(3) and rfSwitchModule(4).rw
Integer32
.1.3.6.1.4.1.9.9.242.1.1.6.1.9
ccaHCCPMemChanSwitchSnmpEnableThis object is used to enable SNMP remote control on the Wavecom upconvertor. When it is set to true(1), SNMP remote control is enabled on the upconvertor. When it is set to false(2), SNMP remote control is disabled and front panel manual operation is enabled. This object is meaningful only if ccaHCCPMemChanSwitchType is ucWavecom(2).rw
TruthValue (SNMPv2-TC)
.1.3.6.1.4.1.9.9.242.1.1.6.1.10
ccaHCCPOnOffNotificationEnableAn indication of whether the ccaHCCPOnNotification and ccaHCCPOffNotification are enabled or disabled.rw
TruthValue (SNMPv2-TC)
.1.3.6.1.4.1.9.9.242.1.1.7
ciscoCableAvailabilityMIBNotificationsPrefix
OBJECT IDENTIFIER
.1.3.6.1.4.1.9.9.242.2
ciscoCableAvailabilityMIBNotifications
OBJECT IDENTIFIER
.1.3.6.1.4.1.9.9.242.2.0
ccaHCCPOnNotificationA 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.
NOTIFICATION-TYPE
.1.3.6.1.4.1.9.9.242.2.0.1
ccaHCCPOffNotificationA 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.
NOTIFICATION-TYPE
.1.3.6.1.4.1.9.9.242.2.0.2
ciscoCableAvailabilityMIBConformance
OBJECT IDENTIFIER
.1.3.6.1.4.1.9.9.242.3
ciscoCableAvailabilityMIBCompliances
OBJECT IDENTIFIER
.1.3.6.1.4.1.9.9.242.3.1
ciscoCableAvailabilityMIBGroups
OBJECT IDENTIFIER
.1.3.6.1.4.1.9.9.242.3.2
CISCO-CABLE-AVAILABILITY-MIB - SNMP MIB Reference | MIBs Explorer