Cisco Broadband Cable Command Reference Guide

debug hccp plane
debug hccp plane
Syntax Description
Command History
4-88
Cisco Broadband Cable Command Reference Guide
Chapter 4 Cisco Cable Modem Termination System Debugging Commands
To display debug messages for HCCP-related messages sent between the router’s control plane and data
backplane, use the debug hccp plane command in privileged EXEC mode. To disable HCCP group
debug message output, use the no form of this command.
debug hccp plane {message | packet | syncpulse}
no debug hccp plane {message | packet | syncpulse}
message Display debugging messages for the inter-plane messages that occur.
packet Display a partial dump of packets that are sent between the control plane and
data backplane.
syncpulse Display debugging messages related to the “heartbeat” packets that are sent
between the control plane and data backplane to synchronize events.
Release Modification
12.2(4)BC1 This command was introduced for the Cisco uBR10012 router.
12.2(4)XF1,
12.2(4)BC1
Support was added for the N+1 RF Switch with the Cisco uBR10012 router.
12.2(11)BC1 Support was added for the N+1 RF Switch with the Cisco uBR7246VXR
router. The syncpulse option also was added.
Usage Guidelines The processor card and line cards on the Cisco uBR10012 router chassis communicate with each other
using the control plane (which is on the processor card) and the data backplane (the backplane into which
the line cards are installed). The debug hccp plane command displays debugging messages related to
the messages and packets that are transmitted between the control plane and data backplane.
Note You must use the debug hccp events command to activate HCCP event debugging before the debug
hccp plane command will generate any debug output.
Examples The following example shows typical output that is produced by the debug hccp plane message
command:
Router# debug hccp events
Router# debug hccp plane message
HCCP inter-plane message debugging is on
Mar 7 08:47:26.513: HCCP 1 Working 4: Control plane sending message BECOME_ACTIVE_STRUCT
Mar 7 08:47:26.513: HCCP 1 Working Cable7/1/0: Control plane sending message FORWARDING
Mar 7 08:47:26.513: HCCP 1 Working 1: Control plane sending message STOP_SYNC
Mar 7 08:47:26.513: HCCP 1 Working 5: Control plane sending message STOP_SYNC
Mar 7 08:47:26.513: HCCP 2 Working 5: Control plane sending message BECOME_ACTIVE_STRUCT
Mar 7 08:47:26.513: HCCP 2 Working Cable7/0/1: Control plane sending message FORWARDING
Mar 7 08:47:26.513: HCCP 2 Working 4: Control plane sending message STOP_SYNC
Mar 7 08:47:26.513: HCCP 1 Protect 80: Data plane sending message FAILURE_SYNCPULSE
OL-1581-05