Table Of Contents
1:1 Timing, Communication, and Control Card Redundancy
Prerequisites for 1:1 Timing, Communication, and Control Card Redundancy
Restrictions for 1:1 Timing, Communication, and Control Card Redundancy
Information About 1:1 Timing, Communication, and Control Card Redundancy
How to Configure 1:1 Timing, Communication, and Control Card Redundancy
Initiating Timing, Communication, and Control Card Switchover
Displaying the Redundancy Status of a Specific Timing, Communication, and Control Card
Displaying the Redundancy Status of All the Timing, Communication, and Control Cards
Feature Information for 1:1 Timing, communication, and Control Card Redundancy
1:1 Timing, Communication, and Control Card Redundancy
First Published: January 8, 2009Last Updated: March 20, 2009The Timing, Communication, and Control (TCC) card operates in 1:1 redundancy configuration where each TCC card has its own dedicated backup card in case of failure (hot standby mode). Only the active TCC card provides functionality in the RF Gateway 10 (RFGW-10) Universal Edge Quadrature Amplitude Modulation (UEQAM) chassis. The standby TCC card is accessible from other line cards, but does not provide any functionality.
Finding Feature Information
Your software release may not support all the features documented in this module. For the latest feature information and caveats, see the release notes for your platform and software release. To find information about the features documented in this module, and to see a list of the releases in which each feature is supported, see the "Feature Information for 1:1 Timing, communication, and Control Card Redundancy" section.
Use Cisco Feature Navigator to find information about platform support and Cisco IOS, Catalyst OS, and Cisco IOS XE software image support. To access Cisco Feature Navigator, go to http://www.cisco.com/go/cfn. An account on Cisco.com is not required.
Contents
•
Prerequisites for 1:1 Timing, Communication, and Control Card Redundancy
•
Restrictions for 1:1 Timing, Communication, and Control Card Redundancy
•
Information About 1:1 Timing, Communication, and Control Card Redundancy
•
How to Configure 1:1 Timing, Communication, and Control Card Redundancy
•
Feature Information for 1:1 Timing, communication, and Control Card Redundancy
Prerequisites for 1:1 Timing, Communication, and Control Card Redundancy
•
Two TCC cards must be installed in the Cisco RFGW-10 UEQAM chassis in slots 13 and 14.
Restrictions for 1:1 Timing, Communication, and Control Card Redundancy
•
Both the TCC cards should synchronize its clock with the same DTI server.
Information About 1:1 Timing, Communication, and Control Card Redundancy
The Timing, Communication, and Control (TCC) card is part of the Cisco RF Gateway 10 chassis. The TCC is 1:1 redundant and the standby will be a hot standby.
How to Configure 1:1 Timing, Communication, and Control Card Redundancy
There is no TCC redundancy configuration command. The system automatically configures slots 13 and 14 in a 1:1 protection scheme (no user provisioning is needed for TCC redundancy).
•
Initiating Timing, Communication, and Control Card Switchover
•
Displaying the Redundancy Status of a Specific Timing, Communication, and Control Card
•
Displaying the Redundancy Status of All the Timing, Communication, and Control Cards
Initiating Timing, Communication, and Control Card Switchover
To force a switchover from the active TCC to the standby TCC, use the following command in privileged EXEC mode on the Supervisor:
Router# redundancy tcc-group switchover from slot [slot]Displaying the Redundancy Status of a Specific Timing, Communication, and Control Card
This section describes how to display the redundancy status of a particular TCC. The commands are executed on the Supervisor.
SUMMARY STEPS
1.
enable
2.
show redundancy tcc slot [slot]
DETAILED STEPS
Displaying the Redundancy Status of All the Timing, Communication, and Control Cards
This section describes how to display the redundancy status of all the TCC cards in the RF Gateway 10 chassis. The commands are executed on the Supervisor.
SUMMARY STEPS
1.
enable
2.
show redundancy tcc all
DETAILED STEPS
Example
The following example shows sample output of the show redundancy tcc all command:
Router# show redundancy tcc allMy PeerSlot State Slot Role--------------------------------13 - 14 -14 Ready None ActiveAdditional References
The following sections provide references related to the 1:1 Timing, Communication, and Control Card Redundancy feature.
Related Documents
Related Topic Document TitleCisco RFGW-10 commands
Cisco RF Gateway 10 Command Reference
http://www.cisco.com/en/US/docs/cable/rf_gateway/command/reference/RFGW-10_Book.html
New Software Features in Cisco IOS Release 12.2(44)SQ
Cisco RF Gateway 10 New Features List
http://www.cisco.com/en/US/docs/cable/rf_gateway/feature/list/rfgw10_featlist.html
Standards
Standard TitleNo new or modified standards are supported by this feature, and support for existing standards has not been modified by this feature.
—
MIBs
RFCs
RFC TitleNo new or modified RFCs are supported by this feature, and support for existing RFCs has not been modified by this feature.
—
Technical Assistance
Command Reference
The following commands are introduced or modified in the feature or features documented in this module. For information about these commands, see the Cisco RF Gateway 10 Command Reference at http://www.cisco.com/en/US/docs/cable/rf_gateway/command/reference/RFGW-10_Book.html. For information about all Cisco IOS commands, use the Command Lookup Tool at http://tools.cisco.com/Support/CLILookup or the Cisco IOS Master Command List, All Releases, at http://www.cisco.com/en/US/docs/ios/mcl/allreleasemcl/all_book.html.
•
redundancy tcc-group switchover from slot [slot]
•
show redundancy tcc slot [slot]
•
show redundancy tcc all
Feature Information for 1:1 Timing, communication, and Control Card Redundancy
Table 1 lists the release history for this feature.
Not all commands may be available in your Cisco IOS software release. For release information about a specific command, see the command reference documentation.
Use Cisco Feature Navigator to find information about platform support and software image support. Cisco Feature Navigator enables you to determine which Cisco IOS, Catalyst OS, and Cisco IOS XE software images support a specific software release, feature set, or platform. To access Cisco Feature Navigator, go to http://www.cisco.com/go/cfn. An account on Cisco.com is not required.
Note
Table 1 lists only the Cisco IOS software release that introduced support for a given feature in a given Cisco IOS software release train. Unless noted otherwise, subsequent releases of that Cisco IOS software release train also support that feature.
Glossary
EQAM—Edge Quadrature Amplitude Modulation. A network element, which receives MPEG-TS frames over a network interface such as Ethernet, and modulates them onto QAM carriers for use on an HFC plant.
LCRED—Line Card Redundancy
TCC—Timing, Communication, and Control
CCDE, CCENT, Cisco Eos, Cisco HealthPresence, the Cisco logo, Cisco Lumin, Cisco Nexus, Cisco StadiumVision, Cisco TelePresence, Cisco WebEx, DCE, and Welcome to the Human Network are trademarks; Changing the Way We Work, Live, Play, and Learn and Cisco Store are service marks; and Access Registrar, Aironet, AsyncOS, Bringing the Meeting To You, Catalyst, CCDA, CCDP, CCIE, CCIP, CCNA, CCNP, CCSP, CCVP, Cisco, the Cisco Certified Internetwork Expert logo, Cisco IOS, Cisco Press, Cisco Systems, Cisco Systems Capital, the Cisco Systems logo, Cisco Unity, Collaboration Without Limitation, EtherFast, EtherSwitch, Event Center, Fast Step, Follow Me Browsing, FormShare, GigaDrive, HomeLink, Internet Quotient, IOS, iPhone, iQuick Study, IronPort, the IronPort logo, LightStream, Linksys, MediaTone, MeetingPlace, MeetingPlace Chime Sound, MGX, Networkers, Networking Academy, Network Registrar, PCNow, PIX, PowerPanels, ProConnect, ScriptShare, SenderBase, SMARTnet, Spectrum Expert, StackWise, The Fastest Way to Increase Your Internet Quotient, TransPath, WebEx, and the WebEx logo are registered trademarks of Cisco Systems, Inc. and/or its affiliates in the United States and certain other countries.
All other trademarks mentioned in this document or website are the property of their respective owners. The use of the word partner does not imply a partnership relationship between Cisco and any other company. (0812R)
Any Internet Protocol (IP) addresses used in this document are not intended to be actual addresses. Any examples, command display output, and figures included in the document are shown for illustrative purposes only. Any use of actual IP addresses in illustrative content is unintentional and coincidental.
© 2009 Cisco Systems, Inc. All rights reserved.

