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.
    

Imported Objects

ciscoMgmtCISCO-SMI
ifIndexIF-MIB
InetAddress, InetAddressTypeINET-ADDRESS-MIB
SnmpAdminStringSNMP-FRAMEWORK-MIB
OBJECT-GROUP, MODULE-COMPLIANCE, NOTIFICATION-GROUPSNMPv2-CONF
MODULE-IDENTITY, NOTIFICATION-TYPE, OBJECT-TYPE, Integer32, Counter32SNMPv2-SMI
TruthValue, DisplayStringSNMPv2-TC

Objects

ciscoCableAvailabilityMIB .1.3.6.1.4.1.9.9.242
ciscoCableAvailabilityMIBObjects .1.3.6.1.4.1.9.9.242.1
ccaHCCPObjects .1.3.6.1.4.1.9.9.242.1.1
ccaHCCPVersion .1.3.6.1.4.1.9.9.242.1.1.1
ccaHCCPGroupTable .1.3.6.1.4.1.9.9.242.1.1.2
ccaHCCPGroupEntry .1.3.6.1.4.1.9.9.242.1.1.2.1
ccaHCCPGroupID .1.3.6.1.4.1.9.9.242.1.1.2.1.1
ccaHCCPGroupAuthentication .1.3.6.1.4.1.9.9.242.1.1.2.1.2
ccaHCCPGroupAuthKeyChain
.1.3.6.1.4.1.9.9.242.1.1.2.1.3
ccaHCCPGroupHelloTime .1.3.6.1.4.1.9.9.242.1.1.2.1.4
ccaHCCPGroupHoldTime .1.3.6.1.4.1.9.9.242.1.1.2.1.5
ccaHCCPGroupRevertEnable
.1.3.6.1.4.1.9.9.242.1.1.2.1.6
ccaHCCPGroupProtectIpAddrType
.1.3.6.1.4.1.9.9.242.1.1.2.1.7
ccaHCCPGroupProtectIpAddress
.1.3.6.1.4.1.9.9.242.1.1.2.1.8
ccaHCCPGroupIfTable .1.3.6.1.4.1.9.9.242.1.1.3
ccaHCCPGroupIfEntry
.1.3.6.1.4.1.9.9.242.1.1.3.1
ccaHCCPGroupIfStatus .1.3.6.1.4.1.9.9.242.1.1.3.1.1
ccaHCCPGroupIfRevertTime .1.3.6.1.4.1.9.9.242.1.1.3.1.2
ccaHCCPGroupIfTrackEnable
.1.3.6.1.4.1.9.9.242.1.1.3.1.3
ccaHCCPGroupIfState .1.3.6.1.4.1.9.9.242.1.1.3.1.4
ccaHCCPGroupIfLastSwitchReason .1.3.6.1.4.1.9.9.242.1.1.3.1.5
ccaHCCPGroupIfOnTransitions
.1.3.6.1.4.1.9.9.242.1.1.3.1.6
ccaHCCPGroupIfOffTransitions
.1.3.6.1.4.1.9.9.242.1.1.3.1.7
ccaHCCPGroupTrackInterfaceTable .1.3.6.1.4.1.9.9.242.1.1.4
ccaHCCPGroupTrackInterfaceEntry
.1.3.6.1.4.1.9.9.242.1.1.4.1
ccaHCCPGroupTrackIfID .1.3.6.1.4.1.9.9.242.1.1.4.1.1
ccaHCCPGroupTrackIfDescr .1.3.6.1.4.1.9.9.242.1.1.4.1.2
ccaHCCPMemberTable .1.3.6.1.4.1.9.9.242.1.1.5
ccaHCCPMemberEntry
.1.3.6.1.4.1.9.9.242.1.1.5.1
ccaHCCPMemberID .1.3.6.1.4.1.9.9.242.1.1.5.1.1
ccaHCCPMemberIpAddrType
.1.3.6.1.4.1.9.9.242.1.1.5.1.2
ccaHCCPMemberIpAddress
.1.3.6.1.4.1.9.9.242.1.1.5.1.3
ccaHCCPMemberState .1.3.6.1.4.1.9.9.242.1.1.5.1.4
ccaHCCPMemberSwitchNow
.1.3.6.1.4.1.9.9.242.1.1.5.1.5
ccaHCCPMemChanSwitchTable .1.3.6.1.4.1.9.9.242.1.1.6
ccaHCCPMemChanSwitchEntry
.1.3.6.1.4.1.9.9.242.1.1.6.1
ccaHCCPMemChanSwitchID .1.3.6.1.4.1.9.9.242.1.1.6.1.1
ccaHCCPMemChanSwitchSnmpEnable
.1.3.6.1.4.1.9.9.242.1.1.6.1.10
ccaHCCPMemChanSwitchType .1.3.6.1.4.1.9.9.242.1.1.6.1.2
ccaHCCPMemChanSwitchIpAddrType
.1.3.6.1.4.1.9.9.242.1.1.6.1.3
ccaHCCPMemChanSwitchIpAddress
.1.3.6.1.4.1.9.9.242.1.1.6.1.4
ccaHCCPMemChanSwitchModule .1.3.6.1.4.1.9.9.242.1.1.6.1.5
ccaHCCPMemChanSwitchProtIpAddrType
.1.3.6.1.4.1.9.9.242.1.1.6.1.6
ccaHCCPMemChanSwitchProtIpAddr
.1.3.6.1.4.1.9.9.242.1.1.6.1.7
ccaHCCPMemChanSwitchProtModule .1.3.6.1.4.1.9.9.242.1.1.6.1.8
ccaHCCPMemChanSwitchPosition .1.3.6.1.4.1.9.9.242.1.1.6.1.9
ccaHCCPOnOffNotificationEnable
.1.3.6.1.4.1.9.9.242.1.1.7
ciscoCableAvailabilityMIBNotificationsPrefix .1.3.6.1.4.1.9.9.242.2
ciscoCableAvailabilityMIBNotifications .1.3.6.1.4.1.9.9.242.2.0
ciscoCableAvailabilityMIBConformance .1.3.6.1.4.1.9.9.242.3
ciscoCableAvailabilityMIBCompliances .1.3.6.1.4.1.9.9.242.3.1
ciscoCableAvailabilityMIBGroups .1.3.6.1.4.1.9.9.242.3.2

Notifications/Traps

NameOIDDescription
ccaHCCPOnNotification



.1.3.6.1.4.1.9.9.242.2.0.1
tion 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.
ccaHCCPOffNotification



.1.3.6.1.4.1.9.9.242.2.0.2
tion 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.