OID repository
OID Repository
http://oid-info.com
Display OID:
 
Action itemiso(1) Action itemidentified-organization(3) Action itemdod(6) Action iteminternet(1) Action itemprivate(4) Action itementerprise(1) Action item9 Action itemciscoMgmt(9)  

Navigating the OID tree

ciscoCableAvailabilityMIB(242)
child OIDs: Child OID separator ciscoCableAvailabilityMIBObjects(1) Child OID separator ciscoCableAvailabilityMIBNotificationsPrefix(2) Child OID separator ciscoCableAvailabilityMIBConformance(3) Child OID separator
 
Separation line
 
OID description

   
OID: (ASN.1 notation)
(dot notation)
(OID-IRI notation)

Description:

ciscoCableAvailabilityMIB MODULE-IDENTITY
LAST-UPDATED "200302200000Z"
ORGANIZATION "Cisco Systems, Inc."
CONTACT-INFO
"Cisco Systems
Customer Service
Postal: Cisco Systems
170 West Tasman Drive
San Jose, CA 95134
U.S.A.
Phone: +1 800 553-NETS
E-mail: cs-ubr@cisco.com"
DESCRIPTION
"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."
REVISION "200302200000Z"
DESCRIPTION
"Changed range of object ccaHCCPMemChanSwitchPosition
and added ciscoCableAvailabilityComplianceRev1 to
allow MIN-ACCESS as read-only for the same."
REVISION "200111250000Z"
DESCRIPTION
"Initial version of this MIB module."


 
Short URLs for this page:

Disclaimer: The owner of this site does not warrant or assume any liability or responsibility for the accuracy, completeness, or usefulness of any information available on this page (for more information, please read the complete disclaimer).
All rights reserved, Orange © 2024
Tree display Parent OID: ciscoMgmt(9) First child OID: ciscoCableAvailabilityMIBObjects(1) First sibling OID: ciscoTcpMIB(6) Previous sibling OID: cggsnQosMIB(241) Next sibling OID: ciscoHealthMonitorMIB(243) Last sibling OID: ciscoVoiceCard(300576)
Separation line
OID helper Webmaster Bullet 4 Nov 2020 Bullet Page top