-
Cisco IOS CMTS Cable Command Reference
-
Cisco IOS CMTS Cable Command Reference Title
-
Introduction
-
Cable Commands: a through cable-modem
-
Cable Commands: cable a through cable c
-
Cable Commands: cable d
-
Cable Commands: cable e through cable i
-
Cable Commands: cable l
-
Cable Commands: cable m
-
Cable Commands: cable p through cable r
-
Cable Commands: cable s
-
Cable Commands: cable t
-
Cable Commands: cable u through cable w
-
Cable Commands: ca through cr
-
Cable Commands: d through h
-
Cable Commands: i through p
-
Cable Commands: q through sg
-
Cable Commands: show a through show cable l
-
Cable Commands: show cable m through show cable t
-
Cable Commands: show ch through show cr
-
Cable Commands: show d through show i
-
Cable Commands: show m through show z
-
Cable Commands: snmp through w
-
Appendix A: Cable Debug Commands
-
Appendix B: Cisco CMTS Router ROM Monitor Commands
-
Table Of Contents
Appendix A: Cable Debug Commands
debug cable admission-control flow-categorization
debug cable service-ds-selection
debug cable subscriber-monitoring
debug cable wbcmts admission-control
debug cable-modem mac messages
debug cable-modem mac messages dynsrv
debug crypto ipsec client ezvpn
debug hccp fast-failure-detection
Appendix A: Cable Debug Commands
Revised: November 13, 2009, OL-15510-10
Additional debug commands are documented in the Cisco IOS Debug Command Reference, available on Cisco.com and the Documentation CD-ROM.
CautionThe debug commands are primarily intended for use in controlled test and troubleshooting situations with a limited volume of traffic. You should use caution when enabling debug messages because sending these messages to the console consumes system resources. Turning on too many types of debug messages can adversely affect the router's network performance, depending on what messages are being displayed and the type of traffic that is occurring.
New Commands
Modified Commands
debug c10k-jacket
To enable debugging information for the Wideband SIP, use the debug c10k-jacket command in privileged EXEC mode. To disable debugging output, use the no form of this command.
debug c10k-jacket [events | plugin | spa-audits | spa-events | spa-vft]
no debug c10k-jacket
Syntax Description
Command Default
No Wideband SIP debug messages are enabled.
Command Modes
Privileged EXEC (#)
Command History
Usage Guidelines
The debug c10k-jacket command is intended for use by Cisco technical support personnel.
Caution
Examples
The following example shows how to enable the debug c10k-jacket spa-vft debug messages for the Wideband SIP.
Router# debug c10k-jacket spa-vftc10k jacket SPA VFT calls debugging is onRouter#Sep 6 17:10:47.410: cr10k_wbcmts_rcv_spa_event: wbcmts spa event recv of type 3Sep 6 17:10:47.410: NB chan stats: 1 entries.Sep 6 17:10:47.414: cr10k_wbcmts_rcv_spa_event: wbcmts spa event recv of type 2Sep 6 17:10:47.414: WB chan stats: 1 entries.Related Commands
debug cable
To enable debugging of the cable interface, use the debug cable command in privileged EXEC mode. To disable debugging output, use the no form of the command.
debug cable
no debug cable
Syntax Description
This command has no arguments or keywords.
Command Modes
Privileged EXEC
Command History
Usage Guidelines
This command enables debugging of the cable interfaces. To avoid excessive output that could interfere with router performance, you should limit debugging to a particular cable interface, using the debug cable interface command, before giving the debug cable command.
Examples
The following shows sample output from the debug cable bpiatp command:
Router# debug cableRouter# debug cable interface c3/0CMTS interface debugging is onRouter#Jun 25 08:36:37.339: cmts_helper_forward 00e0.a3b6.f0af no matchJun 25 08:36:37.339: cmts_dhcp_glean: type=2 sid 0 IP=221.222.151.182 dhcp mac=0Jun 25 08:36:40.339: cmts_helper_forward 00e0.a3b6.f0af no matchJun 25 08:39:13.419: Failed to find CM with mac address 0006.28dc.37fdJun 25 08:39:13.419: Failed to find CM with mac address 00d0.bad3.c0cdJun 25 08:39:13.419: Failed to find CM with mac address 0003.e350.9cdbJun 25 08:39:40.527: Lookup failed - unable to find CM with SID 0Jun 25 08:38:53.583: Lookup failed - unable to find CM with SID 0
Note
Related Commands
debug cable admission-control
To enable automatic Admission Control troubleshooting processes on the Cisco CMTS, use the debug cable admission-control command in privileged EXEC mode. To disable debugging mode, use the no form of this command.
debug cable admission-control {cpu | memory | us-bandwidth | ds-bandwidth}
no debug cable admission-control
Syntax Description
Command Default
Admission Control and Service Flow Admission Control debugging is disabled by default.
Command Modes
Privileged EXEC
Command History
Usage Guidelines
Admission Control debugging processes have some impact to resources on the Cisco CMTS. Any one of the command options can be used for selective debugging and to minimize impact.
For additional Admission Control feature information, refer to the following document on Cisco.com:
•
For additional information for Service Flow Admission Control, commencing in Cisco IOS Release 12.3(21)BC, refer to the following document on Cisco.com:
•
Examples
The following example illustrates CPU debugging with Admission Control:
Router# debug cable admission control cpu*Sep 12 23:08:53.255: CPU admission control check succeeded*Sep 12 23:08:53.255: System admission control check succeeded*Sep 12 23:08:53.255: CPU admission control check succeeded*Sep 12 23:08:53.255: System admission control check succeededThe following example illustrates memory debugging with Admission Control:
Router# debug cable admission control memory*Sep 12 23:08:53.255: CPU admission control check succeeded*Sep 12 23:08:53.255: System admission control check succeeded*Sep 12 23:08:53.255: CPU admission control check succeeded*Sep 12 23:08:53.255: System admission control check succeededThe following example illustrates event debugging with Admission Control:
Router# debug cable admission control event*Sep 12 23:15:22.867: Entering admission control check on PRE and it's a cm-registration*Sep 12 23:15:22.867: Admission control event check is TRUEThe following example illustrates upstream throughput debugging with Admission Control:
Router# debug cable admission control us-bandwidthOct 8 23:29:11: Failed to allocate US bandwidth for CM 0007.0e01.9b45 in adding a new service entryThe following example illustrates downstream throughput debugging with Admission Control:
Router# debug cable admission control ds-bandwidthOct 8 23:29:11: Failed to allocate DS bandwidth for CM 0007.0e01.1db5 in adding a new service entryRelated Commands
debug cable admission-control flow-categorization
To display service flow categorization results, enabled when a service flow is classified, use the debug cable admission-control flow categorization command in Privileged EXEC mode. This command displays the application by which it was categorized, along with which rule is matched. Use the no form of this command to disable this debugging.
debug cable admission-control flow-categorization
no debug cable admission-control flow-categorization
Command Default
Debugging for Service Flow Admission Control is disabled by default on the Cisco CMTS, through Cisco IOS Release 12.3(21a) enables this feature by default, with associated default functions.
Command Modes
Privileged EXEC
Command History
12.3(21)BC
This command was introduced for the Cisco uBR10012 router and the Cisco uBR7246VXR router.
Usage Guidelines
For additional information for Service Flow Admission Control, commencing in Cisco IOS Release 12.3(21)BC, refer to the following document on Cisco.com:
•
Examples
Below is a shortened example of the information displayed when the debug cable admission-control flow-categorization command is enabled on the Cisco CMTS. This command displays interface-level information.
Router# debug cable admission-control flow-categorizationint ca 5/1/1 sfid 55 identified as video pcmm priority 6 matched.Related Commands
debug cable arp
To enable debugging of the Address Resolution Protocol (ARP) when it is used on the cable interface, use the debug cable arp command in privileged EXEC mode. To disable debugging output, use the no form of the command.
debug cable arp
no debug cable arp
Syntax Description
This command has no arguments or keywords.
Command Modes
Privileged EXEC
Command History
Usage Guidelines
The debug commands are primarily intended for use in controlled test and troubleshooting situations with a limited volume of traffic. In particular, avoid using the debug cable arp command on an interface with a significant number of CMs, because the resulting volume of debug output could impact system performance. Cisco recommends that when you use the debug cable arp command, you limit its output to a particular interface or CM, using the debug cable interface or debug cable mac-address commands.
Examples
The following shows typical output for a particular cable modem using the debug cable arp command:
Router# debug cable arpCMTS arp debugging is onRouter# debug cable mac-address 0020.4072.7418ARPGLEAN cmts glean idb Cable3/0 MAC 0020.4072.7418 SID 2 ipaddr 31.0.0.2Related Commands
debug cable arp filter
To display debugging messages about the filtering of Address Resolution Protocol (ARP) broadcasts, use the debug cable arp filter command in privileged EXEC mode. To the debugging messages, use the no form of this command.
debug cable arp filter
no debug cable arp filter
Syntax Description
This command has no arguments or keywords.
Command Default
No default behavior or values.
Command Modes
Privileged EXEC
Command History
12.2(15)BC2
This command was introduced for the Cisco uBR7246VXR and Cisco uBR10012 universal broadband routers.
Usage Guidelines
If you suspect a particular CM is generating a large volume of ARP traffic, you can enable debugging for that particular CM using the debug cable arp command. If the ARP traffic is excessive, you can enable ARP filtering on the associated cable interface using the cable arp filter command. To show the results of that ARP filtering, use the debug cable arp filter command.
Tip
Examples
The following example shows how to enable debugging messages for ARP filtering for a particular MAC address, and samples of the typical messages that can be displayed:
Router# debug cable mac-address 000C.0102.0304Router# debug cable arp filterCMTS arp filter debugging is ONRouter#ARP Req Filter = T shdw 000C.0102.0304 sip 10.11.13.1 dhdw 00C0.0809.0A0B dip 192.168.100.14 cnt 2ARP Req Filter = T src_ip 10.11.13.1 dst_ip 192.168.100.14The following example shows how to enable debugging messages for ARP filtering for a particular SID on a cable interface:
Router# debug cable interface cable c5/0 sid 31Router# debug cable arp filterCMTS arp filter debugging is ONRouter#Related Commands
debug cable bpiatp
To enable debugging of the Baseline Privacy Interface (BPI) handler, use the debug cable bpiatp command in privileged EXEC mode. To disable debugging output, use the no form of the command.
debug cable bpiatp
no debug cable bpiatp
Syntax Description
This command has no arguments or keywords.
Command Modes
Privileged EXEC
Command History
Usage Guidelines
This command activates debugging of the BPI feature. When this command is activated, the Cisco CMTS displays debugging information for any BPI-related messages that the CMTS sends or receives.
Note
Tip
Examples
The following shows sample output from the debug cable bpiatp command:
Router# debug cable interface c3/0Router# debug cable bpiatpCMTS bpi_atp debugging is onRouter#SID : 1 Latest : 2 Current : 1Status[0] : 1 DES Key[0] : DBF08460BF8073B DES IV[0] : D8F26C81A2F01BCKey Life[0]: 392 secStatus[1] : 1 DES Key[1] : BEC1CAE02022349 DES IV[1] : 198C1AB9255113DCKey Life[1]: 87 secReq : 1 Rply : 1 Rej : 0 Inv : 0Upstream Pri SID : 1SID : 1 Even Key : D7C2230BF019D02 Even IV : D8F26C81A2F01BCSID : 1 Odd Key : BD875702048A401 Odd IV : 198C1AB9255113DCSID : 2002 Latest : 2 Current : 1Status[0] : 1 DES Key[0] : 237C029E0879190B DES IV[0] : 166B0B6207580457Key Life[0]: 219 secStatus[1] : 1 DES Key[1] : B8020021FDF1AB5 DES IV[1] : 7A10B6E235E196EKey Life[1]: 69 secCM List:0050.f112.3414IP List:224.0.1.3Req : 0 Rply : 0 Rej : 0 Inv : 0Upstream QoS SID : 0SID : 0 Even Key : FFFF0000FFFF0000 Even IV : FFFF0000FFFF0000SID : 0 Odd Key : FFFF0000FFFF0000 Odd IV : FFFF0000FFFF0000Related Commands
debug cable bundle
To enable debugging of the bundling of cable interfaces, use the debug cable bundle command in privileged EXEC mode. To disable debugging output, use the no form of the command.
debug cable bundle [pkt]
no debug cable bundle [pkt]
Syntax Description
pkt
(Optional) Displays detailed information about packets that are transmitted over the cable bundle.
Command Modes
Privileged EXEC
Command History
12.0(7)XR, 12.1(0)6SC, 12.1(2)EC1
This command was introduced.
12.1(3a)EC
Subinterface support was added.
Usage Guidelines
This command activates debugging for cable interfaces that are bundled together into a master/slave relationship, using the cable bundle command.
Note
Tip
Examples
The following shows typical output from the debug cable bundle command for a particular cable interface:
Router# debug cable interface c3/0Router# debug cable bundle00:53:23: Sending multicast packet to bundle int Cable3/000:53:23: Unicast packet sent out bundle int Cable3/0 to 0003.e3fa.5e2100:53:24: Sending multicast packet to bundle int Cable3/000:53:25: Sending multicast packet to bundle int Cable3/000:53:26: Sending multicast packet to bundle int Cable3/0Router#Related Commands
debug cable cm-status
To enable debugging information for cable modem (CM) status messages on the Cisco CMTS routers, use the debug cable cm-status command in privileged EXEC mode. To stop the display of debug messages, use the no form of this command.
debug cable cm-status
no debug cable cm-status
Syntax Description
This command has no arguments or keywords.
Command Modes
Privileged EXEC (#)
Command History
Examples
The following example shows how to enable debugging output using the debug cable cm-status command:
Router# debug cable cm-statusCMTS CM-STATUS message debugging is onApr 27 07:01:21.659: cmts_send_cm_status_test_msg: SEND IPC to Cable5/0/1 type 139 if_num 1 len 272Apr 27 07:01:21.631: Cable5/0/1: CM 001e.6bfa.f5bc CM-STATUS msgApr 27 07:01:21.631: CM-STATUS:Apr 27 07:01:21.631: 0x0000: 01 03 05 01 01Apr 27 07:01:21.631: Send T4 Timeout to USR event handlingRelated Commands
debug cable classifiers
To display debugging messages for DOCSIS packet classifiers, use the debug cable classifiers command in privileged EXEC mode. To stop the display of debugging messages, use the no form of this command.
debug cable classifiers
no debug cable classifiers
Syntax Description
No additional keywords or syntax components are required.
Command Modes
Privileged EXEC mode
Command Default
DOCSIS packet classifier debugging is disabled by default.
Usage Guidelines
The debug cable classifiers command provides detailed information about the allocation, removal, activation and deactivation of packet classifiers. Generally, classifiers are used to identify IP packets by source port, destination port, or type of service. Classifiers are associated with service flows. For example, packet classifiers are dynamically created in most VOIP deployments and this debug command can be used to troubleshoot issues related to these classifiers as VOIP calls are created and torn down.
Because this command can produce a large volume of debug information, use this command only when you have also enabled debugging for a particular MAC address, set of MAC addresses, or a MAC address mask, using the debug cable mac-address command.
Examples
The following example enables classifier debugging for a single MAC address:
Router# debug cable mac-address 000a.73fa.dbaaRouter# debug cable classifiersCMTS Packet Classifiers debugging is onThe following enables classifier debugging for all MAC addresses with Organizational Unique Identifier (OUI) OUI 0013.11:
Router# debug cable mac-addr 0013.1100.0000 ffff.ff00.0000Routerv# debug cable classifiersCMTS Packet Classifiers debugging is onThe following example illustrates sample output of the debug cable classifiers command for the given MAC addresses:
Feb 7 18:43:50.181: CFR cmts_deactivate_us_srv_flow_act_cfrs 000a.73fa.dbaa sid 1 sfid 3 st 2 dir 0 prov 1 adm 1 act 1Feb 7 18:43:50.181: CFR cmts_remove_cm_srv_flow_cfrs 000a.73fa.dbaa sid 1 sfid 3 st 2 dir 0 prov 1 adm 0 act 0Feb 7 18:43:50.181: CFR cmts_deactivate_ds_srv_flow_act_cfrs 000a.73fa.dbaa sid 0 sfid 4 st 2 dir 1 prov 2 adm 2 act 2Feb 7 18:43:50.181: CFR cmts_remove_cm_srv_flow_cfrs 000a.73fa.dbaa sid 0 sfid 4 st 2 dir 1 prov 2 adm 0 act 0Feb 7 18:43:50.181: CFR cmts_deactivate_us_srv_flow_act_cfrs 000a.73fa.dbaa sid 1 sfid 3 st 2 dir 0 prov 3 adm 0 act 0Feb 7 18:43:50.181: CFR cmts_deactivate_us_srv_flow_act_cfrs 000a.73fa.dbaa sid 1 sfid 3 st 1 dir 0 prov 3 adm 3 act 0Feb 7 18:43:50.181: CFR cmts_activate_us_srv_flow_act_cfrs 000a.73fa.dbaa sid 1 sfid 3 st 2 dir 0 prov 3 adm 3 act 3Feb 7 18:43:50.181: CFR cmts_deactivate_ds_srv_flow_act_cfrs 000a.73fa.dbaa sid 0 sfid 4 st 2 dir 1 prov 4 adm 0 act 0Feb 7 18:43:50.181: CFR cmts_deactivate_ds_srv_flow_act_cfrs 000a.73fa.dbaa sid 0 sfid 4 st 1 dir 1 prov 4 adm 4 act 0Feb 7 18:43:50.181: CFR cmts_activate_ds_srv_flow_act_cfrs 000a.73fa.dbaa sid 0 sfid 4 st 2 dir 1 prov 4 adm 4 act 4Feb 7 18:43:50.181: CFR cmts_set_cfr_params 000a.73fa.dbaa cfrid 1 pri 0 ord 0 dir 0 st 2 phsi 0Feb 7 18:43:50.181: CFR cmts_activate_cfr 000a.73fa.dbaa cfrid 1 pri 1 ord 0 dir 0 st 2Feb 7 18:43:50.181: CFR cmts_add_pkt_cfr 000a.73fa.dbaa cfrid 1 pri 1 ord 0 dir 0 st 1 phsi 0Feb 7 18:43:50.181: CFR cmts_handle_cfr_parsed_data CFR_ADD 000a.73fa.dbaa sfid 0 action 0 dir 0 type 0 cfrid 0 pri 1 ord 0 dir 0 st 1 phsi 0Feb 7 18:43:50.181: CFR cmts_set_cfr_params 000a.73fa.dbaa cfrid 2 pri 0 ord 0 dir 1 st 2 phsi 0Feb 7 18:43:50.181: CFR cmts_activate_cfr 000a.73fa.dbaa cfrid 2 pri 1 ord 0 dir 1 st 2Feb 7 18:43:50.181: CFR cmts_add_pkt_cfr 000a.73fa.dbaa cfrid 2 pri 1 ord 1 dir 1 st 1 phsi 0Feb 7 18:43:50.181: CFR cmts_handle_cfr_parsed_data CFR_ADD 000a.73fa.dbaa sfid 0 action 0 dir 1 typRelated Commands
debug cable dynsrv
Displays information about DOCSIS 1.1 dynamic service flow messages.
debug cable qos
Activates quality-of-service (QoS) debugging.
debug cable cm-ctrl
To enable debugging information for CM-CTRL messages on the Cisco CMTS routers, use the debug cable cm-ctrl command in privileged EXEC mode. To stop the display of debug messages, use the no form of this command.
debug cable cm-ctrl
no debug cable cm-ctrl
Syntax Description
This command has no arguments or keywords.
Command Modes
Privileged EXEC (#)
Command History
Examples
The following example shows how to enable debugging information for CM-CTRL messages using the debug cable cm-ctrl command:
Router# debug cable cm-ctrlCMTS CM-CTRL message debugging is onApr 27 06:53:54.695: CM-CTRL-REQ IPC Msg:*Apr 27 06:53:54.695: 0x0000: 01 06 00 1E 6B FA F5 BC 02 02 00 00 03 04 00 00*Apr 27 06:53:54.695: 0x0010: 13 88 04 02 00 00 05 01 00 06 01 01 07 01 03 08*Apr 27 06:53:54.695: 0x0020: 01 02 0B 01 01Apr 27 06:53:54.647: cmts_clc_proc_cm_ctrl_req calledApr 27 06:53:54.647: cmts_clc_proc_cm_ctrl_req: calling cmts_cm_ctrl_handle_ipc bdy_len 37Apr 27 06:53:54.647: CM-CTRL-IPC Recv:Apr 27 06:53:54.647: 0x0000: 01 06 00 1E 6B FAF5 BC 02 02 00 00 03 04 00 00Apr 27 06:53:54.647: 0x0010: 13 88 04 02 00 00 05 01 00 06 01 01 07 01 03 08Apr 27 06:53:54.647: 0x0020: 01 02 0B 01 01Apr 27 06:53:54.647: CM-CTRL IPC encode MAC: 001e.6bfa.f5bc, timeout: 5000, retry: 0,Apr 27 06:53:54.647: CM-CTRL IPC encode tid: 0, pending: 0, num_tlvs: 1,Apr 27 06:53:54.647: CM-CTRL-REQ CM node: Cable5/0/1, CM 001e.6bfa.f5bc is enqueuedApr 27 06:53:54.651: CM-CTRL encode MAC: 001e.6bfa.f5bc, timeout: 5000, retry: 0,Apr 27 06:53:54.651: CM-CTRL encode tid: 0, pending: 0, num_tlvs: 1,Apr 27 06:53:54.651: TLV[0]: type 3, result: 2, value: 0x01000000Apr 27 06:53:54.651: CM-CTRL: Cable5/0/1 CM 001e.6bfa.f5bc control bitmask: 0x07FEApr 27 06:53:54.651: CM-CTRL-REQ TLV:Apr 27 06:53:54.651: 0x0000: 03 01 01Apr 27 06:53:54.651: CM-CTRL-REQ Msg:Apr 27 06:53:54.651: 0x0000: C2 00 00 1D 00 00 00 1E 6B FA F5 BC 00 19 2F E6Apr 27 06:53:54.651: 0x0010: 06 79 00 0B 00 00 03 04 2A 00 00 00 03 01 01Apr 27 06:53:54.651: CM-CTRL-REQ: Cable5/0/1, CM 001e.6bfa.f5bc enqueued locallyApr 27 06:53:54.651: CM-CTRL-RSP Timer started.Apr 27 06:53:54.651: CM-CTRL-REQ is sent to CM.Apr 27 06:53:54.659: cmts_cm_ctrl_rsp calledApr 27 06:53:54.659: Received CM-CTRL-RSP msg from 001e.6bfa.f5bc transaction id (0)Apr 27 06:53:54.659: CM-CTRL-RSP:Apr 27 06:53:54.659: 0x0000: C2 00 00 1D 9C 24 00 19 2F E6 06 79 00 1E 6B FAApr 27 06:53:54.659: 0x0010: F5 BC 00 0B 00 00 03 04 2B 00 00 00 03 01 00Apr 27 06:53:54.659: CM-CTRL-RSP: Cable5/0/1 CM 001e.6bfa.f5bc timeout 5000 retry 0.Apr 27 06:53:54.659: CM-CTRL-RSP:Apr 27 06:53:54.659: 0x0000: 03 01 00Apr 27 06:53:54.659: CM-CTRL-REQ MAC: 001e.6bfa.f5bc, timeout: 5000, retry: 0,Apr 27 06:53:54.659: CM-CTRL-REQ tid: 0, pending: 1, num_tlvs: 1.Apr 27 06:53:54.659: CM-CTRL decode req_msg->tid: 0, rsp_msg->tid: 0.Apr 27 06:53:54.659: TLV CM reinitialize SuccessRelated Commands
debug cable config-file
To display information about the DOCSIS configuration files that CMTS generates internally, use the debug cable config-file command in the Privileged EXEC mode. To disable the debugging output, use the no form of this command.
Note
debug cable config-file
no debug cable config-file
Syntax Description
This command has no arguments or keywords.
Defaults
No default behavior or values.
Command Modes
Privileged EXEC (#)
Command History
Usage Guidelines
This command shows the DOCSIS configuration files debug messages that the Cisco CMTS generated internally. These configuration files may be generated with the internal configuration file editor using the cable config-file command and its subcommands, or through the "dynamic shared secret" functionality using the cable dynamic-secret command.
Caution
Examples
The following example enables debugging for the internally generated configuration files using the conditional and config-file debug command.
Enable conditional debugs using one of the following commands:
Router# debug cable mac-address 0000.aaaa.bbbbor
Router# debug cable interface cable 6/1/0 verbose
Enable the config-file debug using the following commands:
Router# debug cable config-fileCMTS config file debugging is onRouter# show debugCMTS:CMTS config file debugging is onCMTS specific:Debugging is on for Address 0000.aaaa.bbbb, Mask ffff.ffff.ffffRouter#When debugging is turned on and the Cisco CMTS internally generates a DOCSIS configuration file for transmission to a CM that matches the conditional debug, the CMTS displays the following message:
Server instance created for modem 001a.c3ff.e3f0. Local 3.0.0.1 Read request from CM 001a.c3ff.e3f0 (3.0.0.119) File successfully downloaded to CM 001a.c3ff.e3f0When debugging is turned on and a verbose keyword is used in the conditional debugs, the Cisco CMTS displays the following message:
Server instance created for modem 001a.c3ff.e3f0. Local 3.0.0.1config: Searching download image for 001a.c3ff.e3f0: not found Generated tftp config file:0x0000: 03 01 01 04 1F 01 01 01 02 04 05 F5 E1 00 03 040x0010: 05 F5 E1 00 04 01 00 05 04 00 00 00 00 06 02 070x0020: D0 07 01 01 11 2A 01 04 00 00 00 0A 02 04 00 000x0030: 00 0A 03 04 00 00 02 58 04 04 00 00 00 01 05 040x0040: 00 00 00 01 06 04 00 00 02 58 07 04 00 00 00 3C0x0050: 12 01 0A 06 10 D8 CB DD 33 6A 2D 49 AE E1 EE DE0x0060: 1D E5 90 4A 35 07 10 69 7B F1 67 8A 82 F0 74 F00x0070: 0D A1 89 B3 8D 9C F7 FFConfig file for 001a.c3ff.e3f0, Size 120 Read request from CM 001a.c3ff.e3f0 (3.0.0.119) TFTP Server: Sent OACK to CM 001a.c3ff.e3f0 TFTP Server: ACK from CM 001a.c3ff.e3f0 for block 0 Sending block 1, Size 120 to CM 001a.c3ff.e3f0 TFTP Server: ACK from CM 001a.c3ff.e3f0 for block 1 File successfully downloaded to CM 001a.c3ff.e3f0
Note
Related Commands
debug cable dcc
To display information about DOCSIS 1.1 Dynamic Channel Change (DCC) messages, use the debug cable dcc command in Privileged EXEC mode. To disable debugging output for DCC messages, use the no form of this command.
debug cable dcc
no debug cable dcc
Syntax Description
This command has no arguments or keywords.
Command Default
No default behavior or values.
Command Modes
Privileged EXEC
Command History
12.1(7)CX
This command was introduced for DOCSIS 1.1 operation.
12.2(4)BC1
Support was added to the Release 12.2 BC train.
Usage Guidelines
This command shows debugging messages about the DCC Request (DCC-REQ) message that the CMTS sends to the CM, and about the DCC Response (DCC-RSP) message that the CM sends in reply.
Caution
Tip
Note
Examples
The following examples show typical output for the debug cable dcc command. The following example shows the debug output from a DCC-REQ message that instructs the CM to change its upstream channel to channel 1, using the default initialization technique (option 0, the CM is to reinitialize its MAC layer, requiring a complete reregistration):
Router# debug cable int c3/0Router# debug cable dccCMTS DCC encodings debugging is onRouter#00:02:57: Found DCC TLV00:02:57: US Channel ID 100:02:57: received a DCC_RSP. upstream = 1.The following example shows the debug output from a DCC-REQ message that instructs the CM to change its upstream channel to channel 1, using initialization technique 4 (the CM is to continue its normal operations after synchronizing to the new channel).
0:04:29: Found DCC TLV00:04:29: US Channel ID 100:04:29: Found DCC TLV00:04:29: Init Tech 400:04:29: received a DCC_RSP. upstream = 1.00:04:29: CM new state = 1500:04:30: DCC-RSP-NEW-TIMEOUT: CmMac->00ac.0000.0070 OrgId->3277000:04:30: DCC-RSP-ARRIVE is lost.00:04:30: received a DCC_RSP. upstream = 0.00:04:30: ERROR: Received DCC-RSP-ARRIVE w/o DCC-REQ.00:04:30: DCC-ACK Message Contents:00:04:30: 0x0000: C2 00 00 1A 00 00 00 30 EB 15 2E 97 00 AC 00 0000:04:30: 0x0010: 00 70 00 08 00 00 03 02 19 00 80 0200:04:30: DCC-ACK-SENT: CM->0030.eb15.2e97 TranscId->32770The following example shows the debug output from a DCC-REQ message that instructs the CM to change its upstream channel to channel 2, using initialization technique 4, and substituting a new service flow ID (SFID) of 160 for the current SFID of 14.
00:05:19: Found DCC TLV00:05:19: US Channel ID 200:05:19: Found DCC TLV00:05:19: Init Tech 400:05:19: Found DCC TLV00:05:19: SFID Substitute old 14 new 16000:05:19: received a DCC_RSP. upstream = 0.00:05:19: CM new state = 1500:05:20: DCC-RSP-NEW-TIMEOUT: CmMac->00ac.0000.0070 OrgId->3277100:05:20: DCC-RSP-ARRIVE is lost.00:05:20: received a DCC_RSP. upstream = 1.00:05:20: ERROR: Received DCC-RSP-ARRIVE w/o DCC-REQ.00:05:20: DCC-ACK Message Contents:00:05:20: 0x0000: C2 00 00 1A 00 00 00 30 EB 15 2E 97 00 AC 00 0000:05:20: 0x0010: 00 70 00 08 00 00 03 02 19 00 80 0300:05:20: DCC-ACK-SENT: CM->0030.eb15.2e97 TranscId->32771The following example shows the debug output from a DCC-REQ message that specifies an upstream channel with a frequency that is not a multiple of 62,500 Hz, which is required by the DOCSIS specification:
00:07:28: Found DCC TLV00:07:28: US Channel ID 200:07:28: Found DCC TLV00:07:28: Init Tech 400:07:28: Found DCC TLV00:07:28: ERROR: DS frequency not a multiple of 62500Hz.00:07:28: Not able to parse the TLVs.Related Commands
debug cable tlvs
Displays debugging messages about the TLV values used for service flow encodings, classifier encodings, and PHS rules.
debug cable dci
To display information about DOCSIS 1.1 Device Class Identification (DCI) messages, use the debug cable dci command in privileged EXEC mode. To disable debugging output for DCI messages, use the no form of this command.
debug cable dci
no debug cable dci
Syntax Description
This command has no arguments or keywords.
Command Modes
Privileged EXEC
Command History
12.1(4)CX
This command was introduced for DOCSIS 1.1 operation.
12.2(4)BC1
Support was added to the Release 12.2 BC train.
Usage Guidelines
This command shows debugging messages about the DCI-REQ messages that the Cisco CMTS receives from CMs.
Note
Examples
The following example shows typical output displayed by the debug cable dci command:
Router# debug cable interface c3/0Router# debug cable dciCMTS dci debugging is onRouter#DCI-REQ: CM->1234.5678.abcd SID->1Device Class 1st half->0000000000000000 Device Class 2nd half->0000000000000001Related Commands
debug cable dhcp
To enable debugging of the Dynamic Host Configuration Protocol (DHCP) when it is used on the cable interface, use the debug cable dhcp command in privileged EXEC mode. To disable debugging output, use the no form of the command.
debug cable dhcp
no debug cable dhcp
Syntax Description
This command has no arguments or keywords.
Command Modes
Privileged EXEC
Command History
Usage Guidelines
The debug commands are primarily intended for use in controlled test and troubleshooting situations with a limited volume of traffic. In particular, avoid using the debug cable dhcp command on an interface with a significant number of CMs, because the resulting volume of debug output could impact system performance. Cisco recommends that when you use the debug cable dhcp command, you limit its output to a particular interface or CM, using the debug cable interface or debug cable mac-address commands.
Examples
The following shows typical debugging messages for the debug cable dhcp command for a particular cable modem that is acquiring a DHCP address:
Router# debug cable dhcpCMTS dhcp debugging is onRouter# debug cable mac-address 0020.4072.7418Router# clear cable modem 0020.4072.7418 resetRouter#DHCPINFO hwidb Cable3/1 MAC 0020.4072.7418 SID 2 dhcp_op 1DHCPINFO wan info circuit 80010006 remote_system_id 0020.4072.7418 remote_device_class 0DHCP cmts_helper_forward idb Cable3/1.1 client 0020.4072.7418 31.1.1.1DHCPGLEAN input idb Cable3/1.1 MAC 0020.4072.7418 type 1DHCPGLEAN hwidb Cable3/1 found for MAC 0020.4072.7418DHCPGLEAN cmts glean hwidb Cable3/0 mac 0020.4072.7418 sid 2 ipaddr 0.0.0.0DHCPGLEAN input idb Cable3/1.1 MAC 0020.4072.7418 type 2DHCPGLEAN hwidb Cable3/1 found for MAC 0020.4072.7418DHCPGLEAN SID 2 MAC 0020.4072.7418 on Cable3/0 mapped to swidb Cable3/1.1 ipaddr 31.0.0.2DHCPINFO hwidb Cable3/1 MAC 0020.4072.7418 SID 2 dhcp_op 1DHCPINFO wan info circuit 80010006 remote_system_id 0020.4072.7418 remote_device_class 0DHCP cmts_helper_forward idb Cable3/1.1 client 0020.4072.7418 31.1.1.1 HostDHCPGLEAN input idb Cable3/1.1 MAC 0020.4072.7418 type 3DHCPGLEAN hwidb Cable3/1 found for MAC 0020.4072.7418DHCPGLEAN cmts glean hwidb Cable3/0 mac 0020.4072.7418 sid 2 ipaddr 0.0.0.0DHCPGLEAN input idb Cable3/1.1 MAC 0020.4072.7418 type 5DHCPGLEAN hwidb Cable3/1 found for MAC 0020.4072.7418DHCPGLEAN cmts glean hwidb Cable3/0 mac 0020.4072.7418 sid 0 ipaddr 31.0.0.2DHCPGLEAN SID 2 MAC 0020.4072.7418 on Cable3/0 mapped to swidb Cable3/1.1 ipaddr 31.0.0.2Related Commands
debug cable dsg
To enable general, Downstream Channel Descriptor (DCD), or packet-related debugging for Advanced-mode DOCSIS Set-Top Gateway (A-DSG) on a Cisco CMTS router, use the debug cable dsg command in privileged EXEC mode. To disable A-DSG debugging, us the no form of this command.
debug cable dsg [dcd | pkt]
no debug cable dsg
Syntax Description
dcd
(Optional) Enables DCD-related debugging. Can be combined with pkt.
pkt
(Optional) Enables packet-related debugging. Can be combined with dcd.
Command Default
A-DSG debugging is disabled by default.
Command Modes
Privileged EXEC (#)
Command History
Usage Guidelines
Because this command can produce a large volume of information, use this command only when you have also enabled debugging for a particular interface or MAC address, using the debug cable interface and debug cable mac-address commands, respectively.
Examples
When you use the debug cable dsg dcd command, it shows DCD counters. If the configuration is changed, the whole DCD message content is displayed, including the MAC header. This display is derived from running information. The following sample illustrates one example:
Router# debug cable dsg dcd23:30:45: Constructing DCD for Cable4/123:30:45: Cable4/1 DCD change_count 923:30:45: Cable4/1 DCD datagram size 626, msg len 624, ehdr type_or_len 606,tlv size 59723:30:45: Cable4/1 84485 DCD msg sent, 9 change count increased, 0 fails23:30:46: Constructing DCD for Cable4/123:30:46: Cable4/1 DCD change_count 923:30:46: Cable4/1 DCD datagramsize 626, msg len 624, ehdr type_or_len 606,tlv size 59723:30:46: Cable4/1 84486 DCD msg sent, 9 change count increased, 0 fails23:31:27: DSG VSIF group id 1, vendor index 1, sense 123:31:27: vendor 1 value len 123:31:27: Cable4/1 DCD is config dirty.23:30:47: DSG VSIF group id 1, vendor index 1, sense 123:30:47: vendor 1 value len 123:30:47: Cable4/1 DCD is config dirty.23:30:47: Constructing DCD for Cable4/123:30:47: client list 1 tlv length 2, clnts_tlv_size 423:30:47: Rule 1 all cfr IDs tlv size 423:30:47: Rule 1 VSIF tlv size = 3623:30:47: Encode Cable4/1 rule 1 with tunnel 1,tlv size 6023:30:47: client list 2 tlv length 4, clnts_tlv_size 623:30:47: Rule 2 all cfr IDs tlv size 423:30:47: Encode Cable4/1 rule 2 with tunnel 2,tlv size 2623:30:47: client list 3 tlv length 4, clnts_tlv_size 623:30:47: Rule 3 all cfr IDs tlv size 423:30:47: Encode Cable4/1 rule 3 with tunnel 3,tlv size 2623:30:47: client list 4 tlv length 4, clnts_tlv_size 623:30:47: Rule 4 all cfr IDs tlv size 423:30:47: Encode Cable4/1 rule 4 with tunnel 4,tlv size 2623:30:47: client list 5 tlv length 4, clnts_tlv_size 623:30:47: Rule 5 all cfr IDs tlv size 423:30:47: Encode Cable4/1 rule 5 with tunnel 5,tlv size 2623:30:47: client list 6 tlv length 4, clnts_tlv_size 623:30:47: Rule 6 all cfr IDs tlv size 423:30:47: Encode Cable4/1 rule 6 with tunnel 6,tlv size 2623:30:47: client list 7 tlv length 4, clnts_tlv_size 623:30:47: Rule 7 all cfr IDs tlv size 423:30:47: Encode Cable4/1 rule 7 with tunnel 7,tlv size 2623:30:47: client list 8 tlv length 4, clnts_tlv_size 623:30:47: Rule 8 all cfr IDs tlv size 423:30:47: Encode Cable4/1 rule 8 with tunnel 8,tlv size 2623:30:47: client list 9 tlv length 4, clnts_tlv_size 623:30:47: Rule 9 all cfr IDs tlv size 423:30:47: Encode Cable4/1 rule 9 with tunnel 9,tlv size 2623:30:47: client list 10 tlv length 4, clnts_tlv_size 623:30:47: Rule 10 all cfr IDs tlv size 423:30:47: Encode Cable4/1 rule 10 with tunnel 10,tlv size 2623:30:47: client list 11 tlv length 8, clnts_tlv_size 1023:30:47: Rule 11 all cfr IDs tlv size 423:30:47: Encode Cable4/1 rule 11 with tunnel 11,tlv size 3023:30:47: Cable4/1 TLV size for all rules 32423:30:47: Encode Cable4/1 cfr 1, tlv size 1723:30:47: Encode Cable4/1 cfr 2, tlv size 1723:30:47: Encode Cable4/1 cfr 3, tlv size 1723:30:47: Encode Cable4/1 cfr 4, tlv size 1723:30:47: Encode Cable4/1 cfr 5, tlv size 1723:30:47: Encode Cable4/1 cfr 6, tlv size 1723:30:47: Encode Cable4/1 cfr 7, tlv size 2523:30:47: Encode Cable4/1 cfr 8, tlv size 1723:30:47: Encode Cable4/1 cfr 9, tlv size 1723:30:47: Encode Cable4/1 cfr 10, tlv size 1723:30:47: Encode Cable4/1 cfr 11, tlv size 1723:30:47: Cable4/1 DSG Addr Table tlv size = 51923:30:47: Cable4/1 downstream VSIF tlv size = 3623:30:47: Cable4/1 clnt cfg tlv size = 3823:30:47: Cable4/1 DCD change_count 1023:30:47: Cable4/1 DCD datagramsize 586, msg len 584, ehdr type_or_len 566,tlv size 55723:30:47: Cable4/1 DCD msg 0x62463F8C, size=586C2000248 000001E0 2F000001 000C31F6 F4710236 00000303 20000A01 01323A0101010201 01040201 00050601 005E0101 14060200 012B0608 03ABCABC AB2B1A0803000DF9 0A043030 30310B0D 45363031 30313238 3A303532 32321801 0102020101040403 02095105 0601005E 01011E06 02000232 18010103 02010104 0404020001050601 005E0101 28060200 03321801 01040201 01040403 02070105 0601005E01013206 02000432 18010105 02010104 04040200 02050601 005E0101 3C06020005321801 01060201 01040403 02000605 0601005E 01014606 02000632 1801010702010104 04040200 03050601 005E0101 50060200 07321801 01080201 0104040402000405 0601005E 01011906 02000832 18010109 02010104 04040200 05050601005E0101 33060200 09321801 010A0201 01040404 02000605 0601005E 0101470602000A32 1C01010B 02010104 08020600 504D0000 01050600 504D0000 010602000B170F02 02000105 01010906 0504E601 0114170F 02020002 05010109 060504E601011E17 0F020200 03050101 09060504 E6010128 170F0202 00040501 0109060504E60101 32170F02 02000505 01010906 0504E601 013C170F 02020006 05010109060504E6 01014617 17020200 07050101 090E0504 E6010150 090203E8 0A021388170F0202 00080501 01090605 04E60101 19170F02 02000905 01010906 0504E60123:30:45: DSG VSIF group id 1, vendor index 1, sense 123:30:45: vendor 1 value len 10133170F 0202000A 05010109 060504E6 01014717 0F020200 0B050101 09060504E0191986 33242B06 0803ABCA BCAB2B1A 0803000D F90A0430 3030310B 0D45363031303132 383A3035 323223:30:47: Cable4/1 84487 DCD msg sent, 10 change count increased, 0 fails23:30:48: Constructing DCD for Cable4/123:30:48: Cable4/1 DCD change_count 1023:30:48: Cable4/1 DCD datagramsize 586, msg len 584, ehdr type_or_len 566,tlv size 55723:30:48: Cable4/1 84488 DCD msg sent, 10Related Commands
debug cable dynamic-secret
To display debugging messages for the Dynamic Shared Secret feature, use the debug cable dynamic-secret command in privileged EXEC mode. To stop the display of debugging messages, use the no form of this command.
debug cable dynamic-secret
no debug cable dynamic-secret
Syntax Description
This command has no arguments or keywords.
Command Default
No default behavior or values
Command Modes
Privileged EXEC
Command History
12.2(15)BC1
This command was introduced for Cisco uBR7100 series, Cisco uBR7200 series, and Cisco uBR10012 routers.
Usage Guidelines
Tip
Examples
The following example shows how to enable debugging output using the debug cable dynamic-secret command:
Router# debug cable dynamic-secretCMTS dynamic-secret debugging is onRouter#The following example shows typical output for a cable modem that is reset and reregisters while the Dynamic Shared Secret feature is enabled:
02:15:59: Closing file for modem 00c0.2345.6789: New modem state from resetting to offline02:16:10: Found file name in BOOT_FILE option02:16:10: Parsing IP address from 10.10.35.200, len 10.. Got 10.10.35.200Setting 10 bytes to PAD02:16:10: Config file for 00c0.2345.6789 set to 10.8.35.200:/cm/UBsgvca698. Was 10.10.35.200:/cm/config.cm02:16:10: Discarding contents of /cm/config.cm @ 10.10.35.20002:16:10: FIle /cm/config.cm from 10.10.35.200 read successfully02:16:10: Found file name in BOOT_FILE option02:16:10: Parsing IP address from 10.10.35.200, len 10.. Got 10.10.35.200Setting 10 bytes to PAD02:16:10: Config file for 00c0.2345.6789 set to 10.10.35.200:/cm/wrkldJKDHS. Was 10.10.35.200:/cm/config.cm02:16:15: Registration request from 00c0.2345.6789, SID 1 on Cable3/0/U002:16:15: TLV-Block Bytes:02:16:15: 0x0000: 03 01 01 04 1F 01 01 01 02 04 00 3D 09 00 03 0402:16:15: 0x0010: 00 01 F4 00 04 01 07 05 04 00 01 86 A0 06 02 0002:16:15: 0x0020: 00 07 01 00 12 01 0A 06 10 97 C2 BA 04 6A 76 BD02:16:15: 0x0030: AC 40 FA E6 EB CD 49 E9 54 07 10 89 86 20 E2 7302:16:15: 0x0040: 16 EE 01 0B 24 4A 65 F8 55 93 90 0C 04 03 12 0102:16:15: 0x0050: 09 08 03 00 06 28 05 1E 02 01 01 03 01 01 04 0102:16:15: 0x0060: 01 06 01 01 07 01 00 08 01 04 0A 01 01 0B 01 0802:16:15: 0x0070: 0C 01 01 01 01 0102:16:15: Found Network Access TLV02:16:15: Ntw Access Control : 102:16:15: Found Class Of Service TLV Block02:16:15: Class Id : 102:16:15: Maximum Downstream Rate : 400000002:16:15: Maximum Upstream Rate : 12800002:16:15: Upstream Traffic Priority : 702:16:15: Guaranteed Minimum Upstream Rate : 10000002:16:15: Maximum Upstream Transmit Burst : 002:16:15: Privacy Enable : 002:16:15: Found Max CPEs TLV02:16:15: Maximum Number Of CPEs : 1002:16:15: Found CM-MIC TLV02:16:15: CM MIC:02:16:15: 0x0000: 97 C2 BA 04 6A 76 BD AC 40 FA E6 EB CD 49 E9 5402:16:15: Found CMTS-MIC TLV02:16:15: CMTS MIC:02:16:15: 0x0000: 89 86 20 E2 73 16 EE 01 0B 24 4A 65 F8 55 93 9002:16:15: Found CM IP Address TLV02:16:15: Modem IP Address : 10.18.1.902:16:15: Vendor Id:02:16:15: 0x0000: 00 06 2802:16:15: Found Modem Capabilities TLV02:16:15: DOCSIS Version : 102:16:15: Fragmentation Support : 102:16:15: Payload Header Suppresion Support : 102:16:15: Privacy Support : 102:16:15: Downstream SAID Support : 002:16:15: Upstream SID Support : 402:16:15: Tx Equalizer Taps Per Symbol : 102:16:15: Tx Equalizer Taps Support : 802:16:15: DCC Support : 102:16:15: Concatenation Support : 102:16:15: Computing CMTS-MIC using Dynamic Secret to validate REG-REQ data.02:16:15: CMTS_MIC(rfc2104) failed text + key02:16:15: CMTS_MIC(rfc2104) passed02:16:15: Performing admission control check02:16:15: Mapping Primary DOCSIS 1.0 CoS block into service flows02:16:15: Added Modem Capabilities TLV:02:16:15: 0x0000: 05 1E 02 01 01 03 01 01 04 01 01 06 01 01 07 0102:16:15: 0x0010: 00 08 01 04 0A 01 01 0B 01 08 0C 01 01 01 01 0102:16:15: ClassId:1 assigned SID:102:16:15: Added Service Class Data TLV:02:16:15: 0x0000: 01 07 01 01 01 02 02 00 0102:16:15: REG-RSP Status : ok (0)02:16:15: Closing file for modem 00c0.2345.6789: New modem state from init(o) to online02:16:15: Registration Response TransmittedRouter#The following example shows the typical messages that are shown when you use the clear cable modem lock command to clear the lock on one or more cable modems that have failed the Dynamic Shared Secret checks and were locked into restrictive quality of service (QoS) configurations:
Router# clear cable modem all lock01:46:37: Closing file for modem 00c0.2854.73f5: New modem state from online to offline01:46:37: Closing file for modem 00c0.734e.b4aa: New modem state from online(pt) to offline01:46:37: Closing file for modem 00c0.7366.17cb: New modem state from init(d) to offline01:46:37: Closing file for modem 00c0.80bc.22b5: New modem state from online to offlineRouter#The following debug message is displayed when the CMTS has verified the CMTS MIC in a Data-over-Cable Service Interface Specifications (DOCSIS) configuration file against the shared secret that is configured on a cable interface:
Validated against Shared secretThe CMTS displays the following debug message when the CMTS has verified the CMTS MIC in a DOCSIS configuration file against one of the 16 possible secondary shared secrets that are configured on a cable interface:
Validated against secondary secret 11The CMTS displays the following debug message when the CMTS obtains a new DOCSIS configuration file from the TFTP server. The CMTS keeps this file in its internal cache for 30 seconds, so that it can be used for other cable modems that might request it.
Creating new cache for config-file.cm @ 10.10.10.21The CMTS displays the following debug messages when it receives a registration request or TFTP request for a DOCSIS configuration file from a device that is not a cable modem. This can indicate that a user is trying to manually download a DOCSIS configuration file so that it can be decoded and modified.
MAC address 0102.0304.0506 not of a CMMAC Address 0102.0304.0506, IP address 10.10.10.13 is not a modemThe CMTS displays the following debug message when it receives a TFTP request for an unknown TFTP server. This can indicate that a user is trying to download a DOCSIS configuration file from a local TFTP server.
TFTP server unknown for CM 0102.0304.0506The CMTS displays the following debug message when it receives a TFTP request for a non-cable interface. This can indicate that a user is trying to spoof an IP or Ethernet MAC address, and is trying to access a TFTP server through the Internet or a local network.
TFTP request from a non-cable interface GE1/0/0 ignoredThe CMTS displays the following debug messages when it receives a TFTP request for a DOCSIS configuration file that is not available on the TFTP server:
16:11:33: Could not locate bootfile name for 0102.0304.050616:11:33: Cannot locate config-file.cm requested by CM 0102.0304.050616:11:33: Closing file for modem 0102.0304.0506: New modem state from init(rc) to offlineRelated Commands
debug cable dynsrv
To display information about DOCSIS 1.1 dynamic service flow messages, use the debug cable dynsrv command in privileged EXEC mode. To disable debugging output, use the no form of this command.
debug cable dynsrv
no debug cable dynsrv
Syntax Description
This command has no arguments or keywords.
Command Modes
Privileged EXEC
Command History
Usage Guidelines
This command activates dynamic service flow debugging, which displays a debugging message whenever one of the following DOCSIS 1.1 dynamic service messages is processed:
•
•
•
Each type of dynamic service message includes a request (DSA-REQ, DSC-REQ, DSD-REQ) and a response (DSA-RSP, DSC-RSP, DSD-RSP).
Do not use this command when you have a large number of active CMs on your network, because it could generate a huge amount of output to the console port.
Note
Tip
Examples
The following example shows typical output displayed by the debug cable dynsrv command:
Router# debug cable interface c3/0Router# debug cable dynsrvCMTS dynsrv debugging is onRouter#*May 5 05:15:36.531: DSA-REQ-RECD: OrgMac->0050.734e.b5b1 OrgId->52*May 5 05:15:36.531: DSx-STATE-CREATED: OrgMac->0050.734e.b5b1 OrgId->52*May 5 05:15:36.531: DSA-REQ TLV Information:*May 5 05:15:36.531: Type Subtype Subtype Length Value*May 5 05:15:36.531: 24 10*May 5 05:15:36.531: 19 2 89*May 5 05:15:36.531: 20 4 20000*May 5 05:15:36.531: 80 69*May 5 05:15:36.531: DSA-REQ: Requested QoS Parameter Information:*May 5 05:15:36.531: Srv Flow Ref: 0 Grant Size: 89 Grant Intvl: 20000*May 5 05:15:36.531: Requested QoS parameters match QoS Profile:3 (G729)*May 5 05:15:36.531: DSA-REQ-SID-ASSIGNED: CM 0050.734e.b5b1 SID 11*May 5 05:15:36.531: DSA-RSP-SEND: OrgMac->0050.734e.b5b1 OrgId->52*May 5 05:15:36.531: DSA-RSP msg TLVs*May 5 05:15:36.531: Type:Length:Value*May 5 05:15:36.531: US QoS Encodings 24:8*May 5 05:15:36.531: SID 3:2:11*May 5 05:15:36.531: Service Flow Reference 1:2:0*May 5 05:15:36.531: DSA-RSP hex dump:*May 5 05:15:36.531: 0x0000: C2 00 00 26 00 00 00 50 73 4E B5 B1 00 10 0B AF*May 5 05:15:36.531: 0x0010: BC 54 00 14 00 00 03 01 10 00 00 34 00 18 08 03*May 5 05:15:36.531: 0x0020: 02 00 0B 01 02 00 00 00Related Commands
debug cable encap
To enable debugging of encapsulated packets that are transmitted over the cable interface, use the debug cable encap command in privileged EXEC mode. To disable debugging output, use the no form of the command.
debug cable encap
no debug cable encap
Syntax Description
This command has no arguments or keywords.
Command Modes
Privileged EXEC
Command History
Usage Guidelines
The debug cable encap command displays debugging messages about the following types of encapsulated packets:
•
•
The debug commands are primarily intended for use in controlled test and troubleshooting situations with a limited volume of traffic. In particular, avoid using the debug cable encap command on an interface with a significant number of CMs, because the resulting volume of debug output could impact system performance. Cisco recommends that when you use the debug cable encap command, you limit its output to a particular interface or CM, using the debug cable interface or debug cable mac-address commands.
Examples
The following shows typical output for the debug cable encap command. Messages are shown for both CEF adjacency and MAC-layer encapsulation events:
Router# debug cable encapCMTS encap debugging is onRouter# clear adjacencyENCAPSTR hwidb Cable3/1 idb Cable3/1.1 mac 0020.4072.7418 ipaddr 31.0.0.2 linktype 7ENCAPSTR 0020.4072.7418 SID 2 STR 00000000800200204072741800D0582770540800Router# ping 31.0.0.2Type escape sequence to abort.Sending 5, 100-byte ICMP Echos to 31.0.0.2, timeout is 2 seconds:!!!!!Success rate is 100 percent (5/5), round-trip min/avg/max = 4/5/8 msRouter#VENCAP hwidb Cable3/0 idb Cable3/1.1 mac 0020.4072.7418 ip 31.0.0.2 linktype 7VENCAP 0020.4072.7418 SID 2 STR 00000076800200204072741800D0582770540800VENCAP hwidb Cable3/0 idb Cable3/1.1 mac 0020.4072.7418 ip 31.0.0.2 linktype 7VENCAP 0020.4072.7418 SID 2 STR 00000076800200204072741800D0582770540800VENCAP hwidb Cable3/0 idb Cable3/1.1 mac 0020.4072.7418 ip 31.0.0.2 linktype 7VENCAP 0020.4072.7418 SID 2 STR 00000076800200204072741800D0582770540800VENCAP hwidb Cable3/0 idb Cable3/1.1 mac 0020.4072.7418 ip 31.0.0.2 linktype 7VENCAP 0020.4072.7418 SID 2 STR 00000076800200204072741800D0582770540800VENCAP hwidb Cable3/0 idb Cable3/1.1 mac 0020.4072.7418 ip 31.0.0.2 linktype 7VENCAP 0020.4072.7418 SID 2 STR 00000076800200204072741800D0582770540800Related Commands
debug cable envm
To display information about the Cisco CMTS physical environment, including internal temperature, midplane voltages, fan performance, and power supply voltages, use the debug cable env command in privileged EXEC mode. To disable debugging output, use the no form of this command.
debug cable envm
no debug cable envm
Syntax Description
This command has no arguments or keywords.
Command Modes
Privileged EXEC
Command History
Usage Guidelines
This command is used to debug the sensor circuitry used to measure internal temperature, midplane voltages, fan performance, and power supply voltages on the Cisco CMTS console.
Examples
The following example shows sample output displayed by the debug cable envm command
Router# debug cable envmENVM: ps id=0xFF0, v=0x2050, r=0xC0AB, pstype=1ENVM: ps id=0x2FD0, v=0x2050, r=0x24201, pstype=27NVM: Sensor 0: a2dref=131, a2dact=31, vref=12219, vact=1552 Alpha=8990, temp=27Table 212 provides description for the output.
Related Commands
show environment
Displays the temperature and voltage information for the chassis.
debug cable error
To display errors that occur in the cable MAC protocols, use the debug cable err command in privileged EXEC mode. To disable debugging output, use the no form of this command.
debug cable error
no debug cable error
Syntax Description
This command has no arguments or keywords.
Command Modes
Privileged EXEC
Command History
Usage Guidelines
This command displays unexpected DOCSIS MAC protocol messages. When the Cisco CMTS does not to expect to receive a specific MAC message, or if a packet contains errors in size or content, an error message and a hex dump of the packet are printed. Other miscellaneous error conditions may also show up in output.
Examples
The following shows typical output displayed by the debug cable error command.
Router# debug cable errorRouter#00:19:22: Receive data error, status=0x0D0400:19:22: Receive data error:00:19:22: Prepended data:5C 1E 00 02 00 5F 58 5F 01 12 36 FF F2 00 00 0000:19:22: Packet data (size=36):00:19:22: 0x000: C2 00 00 1E 8E 07 00 E0 1E D7 CC 94 00 50 73 1800:19:22: 0x010: E9 F1 00 0C00:19:22:debug cable flap
To display information about the operation of the CM flap list that is maintained for the cable interfaces, use the debug cable flap command in the Privileged EXEC mode. To disable debugging output, use the no form of this command.
debug cable flap
no debug cable flap
Syntax Description
This command has no arguments or keywords.
Defaults
No default behavior or values.
Command Modes
Privileged EXEC (#)
Command History
Usage Guidelines
This command shows debugging messages about the operation of the CM flap list that is maintained for the cable interfaces.
Caution
Examples
The following example enables debugging for the CM flap list:
Router# debug cable flapCMTS flap debugging is onRouter# show debugCMTS:CMTS flap debugging is onRouter#When debugging is turned on and a CM is added to the flap list the Cisco CMTS displays the following message:
Cable modem <<mac address>> added to flap-listWhen debugging is turned on and a CM is removed from the flap list, the Cisco CMTS displays the following message:
Cable modem <<mac address>> removed from flap-list (<<number>> seconds after last flap)When debugging is turned on and the Cisco CMTS checks the flap list for aged out CMs that need to be removed from the list, the CMTS displays the following message:
CMTS flap list aging check (interval = 120 min)Related Commands
debug cable fn
To enable debugging information for cable fiber nodes, use the debug cable fn command in privileged EXEC mode. To disable debugging output, use the no form of this command.
debug cable fn
no debug cable fn
Syntax Description
This command has no keywords or arguments.
Command Default
No cable fiber node debug messages are enabled.
Command Modes
Privileged EXEC (#)
Command History
Usage Guidelines
The debug cable fn command is intended for use by Cisco technical support personnel.
Caution
For general (non-wideband) information on CMTS debugging commands, see the Cisco Broadband Cable Command Reference Guide.
Examples
The following example shows how to enable debug messages for cable fiber nodes:
Router# debug cable fnCMTS fiber node debugging is on...The following sample messages are displayed when RF channels 0 and 1 are removed from fiber node 1:
Router(config)# cable fiber 1 Router(config-fiber-node)# no downstream modular-cable 3/0/0 rf-channel 0 - 1 ...*Nov 7 17:42:27.903: fn_get_cdb: cdb slot 3(3) subslot 0(0)appl_no 0(0)*Nov 7 17:42:27.903: cfg_cable_fn_cmd: fiber-node 1 status 0x01 cmd 3 sense 0*Nov 7 17:42:27.903: no downstream FN 1, 3/0/0 port range 0 - 1 *Nov 7 17:42:27.903: no downstream FN 1, 3/0/0 bg_rfch 0000000000000004 *Nov 7 17:42:27.903: set FN 1 status old 0x01 to new 0x01 *Nov 7 17:42:27.903: fn_freq_unique: FN 1 *Nov 7 17:42:27.903: prim_rfch 35 slot 8 subslot 1 unit 0 *Nov 7 17:42:27.903: prim_rfch 35 freq 555000000 channel_id 203 *Nov 7 17:42:27.903: bg_rfch 2 slot 3 subslot 0 unit 2 *Nov 7 17:42:27.903: fn_get_cdb: cdb slot 3(3) subslot 0(0)appl_no 0(2) *Nov 7 17:42:27.903: bg_rfch 2 freq 711000000 channel_id 26 *Nov 7 17:42:27.903: clr FN 1 status old 0x01 to new 0x01 *Nov 7 17:42:27.903: fn_channel_id_unique: FN 1 *Nov 7 17:42:27.903: prim_rfch 35 slot 8 subslot 1 unit 0 *Nov 7 17:42:27.903: prim_rfch 35 freq 203 channel_id 203 *Nov 7 17:42:27.903: bg_rfch 2 slot 3 subslot 0 unit 2 *Nov 7 17:42:27.903: fn_get_cdb: cdb slot 3(3) subslot 0(0)appl_no 0(2) *Nov 7 17:42:27.903: bg_rfch 2 freq 711000000 channel_id 26 *Nov 7 17:42:27.903: clr FN 1 status old 0x01 to new 0x01 *Nov 7 17:42:27.903: fn_bundle_same: FN 1 *Nov 7 17:42:27.903: prim_rfch 35 slot 8 subslot 1 unit 0 *Nov 7 17:42:27.903: prim_rfch 35 nb_hwidb Cable8/1/0 bundle 1 *Nov 7 17:42:27.903: bg_rfch 2 slot 3 subslot 0 unit 2 *Nov 7 17:42:27.903: fn_get_cdb: cdb slot 3(3) subslot 0(0)appl_no 0(2) *Nov 7 17:42:27.903: clr FN 1 status old 0x01 to new 0x01 *Nov 7 17:42:27.903: cfg_cable_fn_cmd: fiber-node 1 status 0x01 *Nov 7 17:42:35.267: FN 1 save context status 0x01(0x01) *Nov 7 17:42:35.267: FN 1 status 0x01 saved status 0x01) *Nov 7 17:42:35.267: fiber-node 1 update SG status = 0x01 *Nov 7 17:42:35.267: DS-SG: Updating Association Table from DS-SG. Current: 0x1 New: 0x0 *Nov 7 17:42:35.267: DS-SG: Updating the Wideband Channel Mask: 0x0Related Commands
debug cable freqhop
To display debug messages for frequency hopping, use the debug cable freqhop command in privileged EXEC mode. Use the no form of this command to disable debugging output.
debug cable freqhop
no debug cable freqhop
Syntax Description
This command has no arguments or keywords.
Command History
Examples
The following example shows how to display debug messages for frequency hopping:
router# debug cable interface c6/0router# debug cable freqhopCMTS freqhop debugging is onrouter#Sep 27 10:36:41.202: Cable5/0 U0: last hop delta: 1Sep 27 10:36:42.202: Cable5/0 U0: last hop delta: 2debug cable hw-spectrum
To display debug messages for spectrum management (frequency agility), use the debug cable hw-spectrum command in privileged EXEC mode. To disable debugging output, use the no form of the command.
debug cable hw-spectrum
no debug cable hw-spectrum
Syntax Description
This command has no arguments or keywords.
Command Modes
Privileged EXEC
Command History
11.3 NA
This command was introduced as debug cable specmgmt.
12.0(4)XI
This command was enhanced and renamed to debug cable hw-spectrum.
Examples
The following shows how to enable debug cable hw-spectrum debugging.
Router# debug cable hw-spectrumCMTS spectrum analyzer debugging is onRouter#Related Commands
debug cable specmgmt
Displays debugging output for the CMTS spectrum analyzer process.
debug cable interface
To display debug messages for a specific cable interface, or for traffic related to a specific MAC address or Service ID (SID) on that interface, use the debug cable interface command in privileged EXEC mode. To disable debugging output, use the no form of this command.
debug cable interface cable {slot/port | slot/subslot/port} [mac-address address [mask] | sid number [track] | [verbose]]
no debug cable interface cable {slot/port | slot/subslot/port} [mac-address address [mask] | sid number [track] | [verbose] ]
Syntax Description
Defaults
Debugging for the cable interfaces is not enabled, which means most of the other debug cable commands will not display any output, even when debugging is enabled.
Command Modes
Privileged EXEC
Command History
Usage Guidelines
The debug cable interface command must be used to enable debugging on a cable interface before other debug commands can be used on that interface. The mac-address and sid options can be used to restrict the debug output to only those messages that are related to a specific MAC address or SID, so that the volume of debug messages does not affect system performance.
Examples
The following example shows how to enable debugging on the cable interface in slot 6:
Router# debug cable interface c6/0Router# show debugCMTS specific:Debugging is on for Cable6/0Router#The following shows how to enable verbose debugging on the cable interface in slot 6:
Router# debug cable interface c6/0 verboseRouter# show debugCMTS specific:Debugging is on for Cable6/0 (verbose)Router#The following example shows how to enable debugging on the cable interface in slot 6 for all traffic coming from CMs and other devices with MAC addresses that match the address range 0010.0000.0000 through 0010.00FF.FFFF (0010.00xx.xxxx):
Router# debug cable interface c6/0 mac-address 0010.0000.0000 FFFF.FF00.0000Router# show debugCMTS specific:Debugging is on for Cable6/0, Address 0010.0000.0000, Mask ffff.ff00.0000Router#Related Commands
debug cable ipv6
To enable debugging of IPv6 transactions on a cable interface on a Cisco CMTS router, use the debug cable ipv6 command in privileged EXEC mode. To disable debugging output, use the no form of the command.
debug cable ipv6 [db | dhcp | nd | source-verify]
no debug cable ipv6 [db | dhcp | nd | source-verify]
Syntax Description
Command Modes
Privileged EXEC (#)
Command History
Usage Guidelines
The debug commands are primarily intended for use in controlled test and troubleshooting situations with a limited volume of traffic. In particular, avoid using the debug cable ipv6 command on an interface with a significant number of CMs, because the resulting volume of debug output could impact system performance. Cisco recommends that when you use the debug cable ipv6 command, you limit its output to a particular interface or CM, using the debug cable interface or debug cable mac-address commands.
Related Commands
debug cable keyman
To activate debugging of TEK and KEK BPI key management, use the debug cable keyman command in privileged EXEC mode. To disable debugging output, use the no form of the command.
debug cable keyman
no debug cable keyman
Syntax Description
This command has no arguments or keywords.
Command Modes
Privileged EXEC
Command History
Usage Guidelines
This command activates debugging of the TEK and KEK baseline privacy key activity. When this command is activated, all activity related to KEK and TEK keys is displayed on the Cisco CMTS console. This command is used to display encryption key management debugging output.
Note
Examples
The following shows typical output from the debug cable keyman command.
Router# debug cable keymanRouter#Dec 11 23:16:19.139: CMTS Received AUTH REQ.Dec 11 23:16:19.139: Created a new CM key for 0010.7b43.aa2f.Dec 11 23:16:19.139: CMTS generated AUTH_KEY.Dec 11 23:16:19.139: Input : 23FD16A701FD2091Public Key :Dec 11 23:16:19.139: 30 68 02 61 00 C1 26 6F 53 3E CE 17 AB 18 84 C5Dec 11 23:16:19.139: 63 B3 A2 DA 66 29 96 13 23 B8 A3 C8 AF B7 CF C8Dec 11 23:16:19.139: 54 6B 16 14 E2 9B 12 0B 34 79 51 DA 18 AB DE 8CDec 11 23:16:19.139: 65 8F 0B 8A AB 25 3B 88 F1 6D 53 5F 64 C3 3E 50Dec 11 23:16:19.139: 81 57 AA C5 8F CE 4F 3C A8 96 2F 60 0F F6 30 E6Dec 11 23:16:19.139: 91 61 29 42 E1 C2 96 0F CB 10 EF F9 0D 6F 45 76Dec 11 23:16:19.139: 1D 17 FD 26 6D 02 03 01 00 01Dec 11 23:16:19.139:Dec 11 23:16:19.139: RSA publlic Key subject:Dec 11 23:16:19.143: 30 7C 30 0D 06 09 2A 86 48 86 F7 0D 01 01 01 05Dec 11 23:16:19.143: 00 03 6B 00 30 68 02 61 00 C1 26 6F 53 3E CE 17Dec 11 23:16:19.143: AB 18 84 C5 63 B3 A2 DA 66 29 96 13 23 B8 A3 C8Dec 11 23:16:19.143: AF B7 CF C8 54 6B 16 14 E2 9B 12 0B 34 79 51 DADec 11 23:16:19.143: 18 AB DE 8C 65 8F 0B 8A AB 25 3B 88 F1 6D 53 5FDec 11 23:16:19.143: 64 C3 3E 50 81 57 AA C5 8F CE 4F 3C A8 96 2F 60Dec 11 23:16:19.143: 0F F6 30 E6 91 61 29 42 E1 C2 96 0F CB 10 EF F9Dec 11 23:16:19.143: 0D 6F 45 76 1D 17 FD 26 6D 02 03 01 00 01Dec 11 23:16:19.155: RSA encryption result = 0Dec 11 23:16:19.155: Output :Dec 11 23:16:19.155: 88 5F 67 22 86 68 2B 1D A6 F4 E9 62 43 58 1A C8Dec 11 23:16:19.155: 49 97 7E 81 EE EF B0 DD C4 42 30 FD 24 B0 54 2EDec 11 23:16:19.155: 01 CC 84 53 BD 71 50 9D B3 82 4D 7B 49 42 E1 F0Dec 11 23:16:19.155: 2D 67 3D 46 CB 27 4D 60 16 00 4D EE E1 F3 FD 1DDec 11 23:16:19.155: 9C E6 03 3C 77 C8 3A 44 B9 FA 34 2E 44 1B 69 F4Dec 11 23:16:19.155: AA 68 BF BB A5 43 9B F7 85 82 ED 39 45 02 92 56Dec 11 23:16:19.155: CMTS sent AUTH response.Dec 11 23:16:24.267: CMTS Received TEK REQ.Dec 11 23:16:24.267: Message Digest Verification Failed.Dec 11 23:16:24.267: Sending KEK INVALID.Dec 11 23:16:24.323: CMTS Received AUTH REQ.Dec 11 23:16:24.323: Find a match CM key for abcd.0123.4455Related Commands
debug cable l2-vpn
To display debugging messages for the Layer 2 mapping of cable modems to particular permanent virtual connections (PVC) or to a virtual local area network (VLAN), use the debug cable l2-vpn command in privileged EXEC mode. To stop the display of debugging messages, use the no form of this command.
debug cable l2-vpn [conditional]
no debug cable l2-vpn [conditional]
Note
Syntax Description
Command Default
No default behavior or values
Command Modes
Privileged EXEC
Command History
Usage Guidelines
The debug cable l2-vpn command displays status information for the mapping of cable modems to PVCs on an ATM interface (see the cable vc-map command) or to a VLAN on an Ethernet, Fast Ethernet, or Gigabit Ethernet interface (see the cable dot1q-vc-map command). The debug messages show when a cable modem is mapped to a PVC or VLAN, when the mapping is changed or removed, and when packets are sent and received over the mapping.
The conditional option displays information for each packet that is sent and received over an ATM PVC or VLAN mapping. Because this can produce a large volume of debug information, the conditional option can be used only when you have also enabled debugging for a particular interface or MAC address, using the debug cable interface and debug cable mac-address commands, respectively.
Examples
The following example shows typical output for the debug cable l2-vpn command when a cable modem is mapped to an ATM PVC:
Router# debug cable l2-vpnCMTS L2 VPN debugging is onRouter# configure terminalRouter(config)# cable l2-vpn-service atm-vcRouter(config)# cable vc-map 0007.0e03.69f9 ATM2/0 1/16d00h: Associating vc ATM2/0.1 1/1 to CM 0007.0e03.69f9 sid 0x16d00h: Writing vc-map info to sid 0x1Router(config)#The following example shows typical output for the debug cable l2-vpn command when a cable modem is mapped to an IEEE 802.1Q VLAN:
Router# debug cable l2-vpnCMTS L2 VPN debugging is onRouter# configure terminalRouter(config)# cable l2-vpn-service dot1qRouter(config)# cable dot1q-vc-map 0007.0e03.69f9 FastEthernet0/0 5Router(config)#Set promiscuous mode for FastEthernet0/0Mapped DS srv flow 13 on Cable5/0 to FastEthernet0/0 VLAN 5Mapped US srv flow 11 sid 31 on Cable5/0 to FastEthernet0/0 VLAN 5The following example shows typical output for the debug cable l2-vpn command when a mapping is deleted:
Router# debug cable l2-vpnCMTS L2 VPN debugging is onRouter# configure terminalRouter(config)# no cable vc-map 0007.0e03.69f9 ATM2/0 1/16d00h: Disassociating vc ATM2/0.1 1/1 from CM 0007.0e03.69f9 sid 0x16d00h: Erasing vc-map info to sid 0x1Router(config)#The following example shows typical output for the conditional option. This example shows output for traffic to and from one particular cable modem. Each debug message shows the size of the packet, the source and destination MAC addresses, the cable interface and SID being used, and the ATM interface and PVC/PVI being used.
Router# debug cable mac-address 000C.0807.06.05Router# debug cable l2-vpn conditionalCMTS L2 VPN conditional debugging is on6d00h: Fwd pkt size 74 from 000C.0807.0605 on Cable4/0:0x1 to 0900.2b00.000f on ATM2/0:1/16d00h: Fwd pkt size 74 from 000C.0807.0605 on Cable4/0:0x1 to 0900.07ff.ffff on ATM2/0:1/16d00h: Fwd pkt size 1028 from 000C.0807.0605 on Cable4/0:0x1 to 0002.4a1d.dc1d on ATM2/0:1/16d00h: Send pkt size 1020 encsize 6 from 0002.4a1d.dc1d on ATM2/0:1/1 to 000C.0807.0605 on Cable4/0:0x16d00h: Fwd pkt size 74 from 000C.0807.0605 on Cable4/0:0x1 to 0900.07ff.ffff on ATM2/0:1/1Router#Related Commands
debug cable load-balance
To display debugging messages for load-balancing operations on the router, use the debug cable load-balance command in privileged EXEC mode. To stop the display of debugging messages, use the no form of this command.
debug cable load-balance [error]
no debug cable load-balance [error]
Syntax Description
error
(Optional) Displays debugging messages about errors that might occur during load-balancing operations about the actual number of CMs that are active on a channel.
Command Default
No default behavior or values
Command Modes
Privileged EXEC
Command History
12.2(15)BC1
This command was introduced for the Cisco uBR7246VXR and Cisco uBR10012 routers.
Usage Guidelines
The debug cable load-balance command displays debugging output for when cable modems come online those cable interfaces that are part of a load balance group. It also displays debugging messages when cable modems are moved to achieve balanced loads on those cable interfaces.
Tip
Examples
The following example shows typical output for the debug cable load-balance command for a particular cable interface:
Router# debug cable interface c3/0Router# debug cable load-balanceCMTS load balancing debugging is on*Feb 13 13:39:21.594 PDT: lb: Removing Modem entry 0050.7318.e615: at target (upstream)*Feb 13 13:39:50.754 PDT: lb: US request from Cable3/0/U0[0050.7366.1f7b]: target U3 [enforce], 0 retries*Feb 13 12:53.010 PDT: lb: Moving Modem 0050.7366.218b from Cable3/0/U0 to U2*Feb 13 13:40:03.034 PDT: lb: Moving Modem 0050.7366.1c7f from Cable3/0/U1 to U2*Feb 13 13:40:04.790 PDT: lb: US request from Cable3/0/U1[0050.7318.e615]: target U2 [enforce], 0 retries*Feb 13 13:40:11.150 PDT: lb: Removing Modem entry 0050.7318.e615: at target (upstream)*Feb 13 13:40:23.042 PDT: lb: Moving Modem 0050.7366.21c7 from Cable3/0/U0 to U3*Feb 13 13:40:23.042 PDT: lb: Moving Modem 0050.7366.2197 from Cable3/0/U0 to U3*Feb 13 13:40:23.042 PDT: lb: Moving Modem 0050.7366.1f75 from Cable3/0/U0 to U3Router#The following example shows typical output for the debug cable load-balance command when the error option is used to display messages about possible errors in the number of CMs that are active on the interface.
Router# debug cable interface c5/1/0Router# debug cable load-balance errorRouter#CMTS load balancing error debugging is onlb: c5/1/0/U4: Total modems: 126 active modems: 123c5/1/0: delete_sid_state on modem 0001.0203.0405 in state offlineRelated Commands
debug cable mac-address
To display debug information for a specific CM, use the debug cable mac command in privileged EXEC mode. The no form of this command disables debugging output.
debug cable mac-address address [address-mask] [verbose]
no debug cable mac-address address [address-mask] [verbose]
Syntax Description
Command Modes
Privileged EXEC
Command History
Usage Guidelines
You can repeat this command for other MAC addresses. Each time you specify a different MAC address, debugging is turned on for that particular MAC address.
If you enter two commands with the same MAC address, but with different values for the mask or verbose keywords, the router treats both commands as the same. In this case, the latest debugging information supersedes the previous debugging information.
Note
Examples
The following example demonstrates how to enable debugging for all traffic coming from cable interface 3/0 of CMs with the MAC address 00E0.1Exx.xxxx:
Router# debug cable interface c3/0Router# debug cable mac-address 00E0.1E00.0000 ffff.ff00.0000Router#004042: Jul 2 08:47:13.656: Ranging Modem 00E0.1E23.4567, SID 73 on Interface Cable3/U0004043: Jul 2 08:47:13.656: Ranging request from 00E0.1E23.4567, SID 73 [73] on Interface Cable3/U0004044: Jul 2 08:47:13.656: Timing error 0, power error 0.25dB, freq error 4 (adjust 0)004045: Jul 2 08:47:13.656: Ranging successful
Tip
Related Commands
debug cable mac-protocol
To display MAC-layer information for a specific CM, use the debug cable mac command in privileged EXEC mode. The no form of this command disables debugging output.
debug cable mac-protocol
no debug cable mac-protocol
Syntax Description
This command has no arguments or keywords.
Command Modes
Privileged EXEC
Command History
Usage Guidelines
Do not use this command if you have a large number of CMs on your network. The Cisco CMTS will become flooded with console printouts.
Examples
The following example shows the return for the MAC layer:
router# debug cable mac-protocolCMTS mac debugging is on19:46:27: Ranging Modem with Sid 1 on i/f : Cable6/0/U019:46:27: Got a ranging request19:46:27: SID value is 1 on Interface Cable6/0/U019:46:27: CM mac address 00:E0:1E:B2:BB:0719:46:27: Timing offset is 019:46:27: Power value is FE0, or 0 dB19:46:27: Freq Error = 0, Freq offset is 019:46:27: Ranging has been successful for SID 1 on Interface Cable6/0/U019:46:29: Ranging Modem with Sid 2 on i/f : Cable6/0/U019:46:29: Got a ranging request19:46:29: SID value is 2 on Interface Cable6/0/U019:46:29: CM mac address 00:E0:1E:B2:BB:8F19:46:29: Timing offset is 119:46:29: Power value is 1350, or 0 dB19:46:29: Freq Error = 0, Freq offset is 019:46:29: Ranging has been successful for SID 2 on Interface Cable6/0/U019:46:32: Ranging Modem with Sid 3 on i/f : Cable6/0/U019:46:32: Got a ranging request19:46:32: SID value is 3 on Interface Cable6/0/U019:46:32: CM mac address 00:E0:1E:B2:BB:B119:46:32: Timing offset is FFFFFFFF19:46:32: Power value is 1890, or -1 dB19:46:32: Freq Error = 0, Freq offset is 019:46:32: Ranging has been successful for SID 3 on Interface Cable6/0/U019:46:34: Ranging Modem with Sid 5 on i/f : Cable6/0/U0
Tip
Related Commands
debug cable mac-scheduler
To display information for the MAC layer's scheduler and admission control activities, use the debug cable mac-scheduler command in privileged EXEC mode. The no form of this command disables debugging output.
debug cable mac-scheduler [admission control | upstream-utilization | ubg]
no debug cable mac-scheduler [admission control | upstream-utilization | ubg]
Syntax Description
Command Modes
Privileged EXEC
Command History
Usage Guidelines
Do not use this command if you have a large number of CMs on your network. The Cisco CMTS will become flooded with console printouts.
Caution
Examples
The following example shows debugging being turned on for the MAC scheduler:
Router# debug cable mac-schedulerCMTS scheduler debugging is onRouter#The following example shows admission-control debugging being turned on for a particular CM with the MAC address of 000C.1234.5678, and the typical messages that appear if the CM cannot register because the channel is oversubscribed.
Router# debug cable mac-address 000C.1234.5678 verboseRouter# debug cable mac-scheduler admission-controlCMTS scheduler debugging is onRouter#Oct 23 09:38:56.701: MSCHED_CAC: Admit req for US service flow.Oct 23 09:38:56.701: SFID=3 SID=1 AdmQoS=5Oct 23 09:38:56.701: Admission check for BE serviceOct 23 09:38:56.701: Min rsvd rate : 1800000 bpsOct 23 09:38:56.701: Failed to allocate bandwidthOct 23 09:38:56.701: Admit req rejected.The following example shows the debugging output for upstream bonding groups on a particular CM with the MAC address of 001e.6bfb.153c:
Router# debug cable mac-address 001e.6bfb.153c verboseRouter# debug cable mac-scheduler ubgCMTS mac-scheduler ubg debugging is on5:38:17 PM?Jul 21 12:07:01.318: cmts_schedule_solc_bgrant:Sid=8 US[2] sc=0/0 type=5 bytes:1605 cbi_p:0xE326494Jul 21 12:07:01.318: cmts_schedule_solc_bgrant: num_chan: 4, avail_chan: 4Jul 21 12:07:01.318: cmts_schedule_solc_bgrant: shp_delay = 0 partial_len = 0 num_bytes = 6420Jul 21 12:07:01.318: cmts_sched_alloc_sbi_p: Alloc sbi_p: 0x1FB7F984Jul 21 12:07:01.318: cmts_sched_alloc_bg_pgrant_p: alloc bg_pg_p: 0x1FB87938Jul 21 12:07:01.318: cmts_sched_slotq_enq_bpgrant:bg_pg_p:0x1FB87938 sid:8 US[2] sbip:0x1FB7F984 bytes:0 ref:1Jul 21 12:07:01.318: cmts_sched_slotq_enq_breq: US[1]: sbip:0x1FB7F984 sbi.tbytes:1605 ref:2 Sid=8 bytes:1605, mslots:75Jul 21 12:07:01.318: cmts_sched_slotq_enq_breq: US[2]: sbip:0x1FB7F984 sbi.tbytes:3210 ref:3 Sid=8 bytes:1605, mslots:75Jul 21 12:07:01.318: cmts_sched_slotq_enq_breq: US[3]: sbip:0x1FB7F984 sbi.tbytes:4815 ref:4 Sid=8 bytes:1605, mslots:75Jul 21 12:07:01.318: cmts_sched_slotq_enq_breq: US[4]: sbip:0x1FB7F984 sbi.tbytes:6420 ref:5 Sid=8 bytes:1605, mslots:75Jul 21 12:07:01.318: cmts_sched_free_sbi_p: sbi_p:0x1FB7F984 Sid=8 ref:5Jul 21 12:07:01.318: cmts_sched_free_sbi_p: sbi_p:0x1FB7F984 Sid=8 ref:4Jul 21 12:07:01.318: cmts_sched_free_sbi_p: sbi_p:0x1FB7F984 Sid=8 ref:3Jul 21 12:07:01.318: cmts_sched_free_sbi_p: sbi_p:0x1FB7F984 Sid=8 ref:2Jul 21 12:07:01.322: cmts_sched_free_sbi_p: sbi_p:0x1FB7F984 Sid=0 ref:1Jul 21 12:07:01.322: cmts_sched_free_sbi_p: Free sbi_p: 0x1FB7F984Jul 21 12:07:01.322: cmts_sched_free_bg_pgrant_p: free bg_pg_p: 0x1FB87938Related Commands
debug cable map
To display debugging messages for DOCSIS MAC-layer MAP messages, use the debug cable map command in privileged EXEC mode. The no form of this command disables debugging output.
debug cable map [error | sid [sid-num] ]
no debug cable map [error | sid [sid-num] ]
Syntax Description
Command Modes
Privileged EXEC
Command History
Examples
The following example shows how to display all MAP messages, with and without data grants:
Router# debug cable map19:41:53: On interface Cable6/0, sent 5000 MAPs, 1321 MAPs had grant(s)Long Grants 13256993, Total Short Grants 223------------------ MAP MSG --------------------us_ch_id: 1 ucd_count: 5 num_elems: 9 reserved: 0Alloc Start Time: 33792 Ack Time: 33618Rng_bkoff_start: 0 Rng_bkoff_end: 2Data_bkoff_start: 1 Data_bkoff_end: 3:sid:16383 iuc:1 mslot_offset:0sid:0 iuc:7 mslot_offset:40------------------ MAP MSG ---------------------us_ch_id: 1 ucd_count: 5 num_elems: 7 reserved: 0Alloc Start Time: 33712 Ack Time: 33578Rng_bkoff_start: 0 Rng_bkoff_end: 2Data_bkoff_start: 1 Data_bkoff_end: 3sid:2 iuc:6 mslot_offset:0sid:16383 iuc:1 mslot_offset:16sid:0 iuc:7 mslot_offset:40Table 0-215 describes the fields displayed by the debug cable map command.
The following shows typical output for the debug cable map error command:
Router# debug cable int cable 4/0Router# debug cable map errorCMTS map errors debugging is ONRouter#00:11:21: ##### Bad IE-offset for prenull IE[1]#####---------------------- MAP MSG ---------------------us_ch_id: 1 ucd_count: 11 num_elems: 4 reserved: 0Alloc Start Time: 20007713 Ack Time: 20007291Rng_bkoff_start: 0 Rng_bkoff_end: 3Data_bkoff_start: 0 Data_bkoff_end: 4sid:16383 iuc:1 mslot_offset:0sid:16383 iuc:1 mslot_offset:0sid:16383 iuc:1 mslot_offset:158sid:0 iuc:7 mslot_offset:160Related Commands
show controllers cable
Displays interface controller information for the specified slot.
debug cable metering
To enable debugging of usage-based billing operations, use the debug cable metering command in privileged EXEC mode. To turn off debugging messages, use the no form of this command.
debug cable metering
no debug cable metering
Syntax Description
This command has no arguments or keywords.
Command Modes
Privileged EXEC
Command History
Examples
The following example shows how to enable debugging for usage-based billing on the Cisco CMTS, and then shows examples of the debugging messages that can be displayed.
Router# debug cable meteringCMTS metering debug is ONRouter#Cannot get Metering CMTS IP/MAC Addresses.CMTS Billing ip address interface name c6/0CMTS SFLOG File BBCMTS_20000708-120931 open failed (23)CMTS Metering open file CMTS0120000708-120931 successfully.CMTS Metering LOCAL data to write 5600, wrote 4800 to file local fileCMTS Metering data to write 6400, wrote 6400 to file B_20000708-120931CMTS Metering invalid FD for metering fileCMTS Metering Produce Metering - END Time= 2002-05-25T14:41:29ZCMTS Metering closed fileCMTS Metering: xml end queue data malloc failed.CMTS Metering file header len=480CMTS Metering: xml header enqueue failed.CMTS Metering: xml header enqueue OK.CMTS Metering: xml end queue data malloc failed.CMTS Metering xml_ending len 128CMTS Metering: xml end enqueue OK.CMTS Metering element header length 440CMTS Metering sflog read buf = 4800CMTS Metering: malloc failed.CMTS Metering: SFLOG file 4800 size tx failed.CMTS Metering: SFLOG tx OK 4800 size.Cmts Metering: SFLOG file doesn't existCMTS Metering abort producing billing due to file open failure.CMTS Metering: enqueue failedCMTS Metering get invalid CM.CMTS Metering valid cm 192.168.100.101, prim sid 13CMTS Metering interval 30Invalid Metering Timer Expired...Stop Timer.Related Commands
debug cable mdd
To display debugging messages of the MAC domain descriptor, use the debug cable mdd command in privileged EXEC mode. To turn off debugging, use the no form of this command.
debug cable mdd
no debug cable mdd
Syntax Description
This command has no arguments or keywords.
Command Modes
Privileged EXEC (#)
Command History
Examples
The following is a sample output of the debug cable mdd command:
Router# debug cable mddCMTS mdd debugging is onRouter#Jul 7 20:57:27.038: Cable8/0/0: size 228 mdd_tlv_size 198 num_frag 1 seq_num 1test_mdd_tlv_length 0Jul 7 20:57:27.038: Cable8/0/0 MDD datagram size 228, msg len 226, ehdr type_or_len 208, tlv_size 198 max_pak_size 1518Jul 7 20:57:27.038: MDD MESSAGEJul 7 20:57:27.038: FRAME HEADERJul 7 20:57:27.038: FC, MAC_PARM, LEN - 0xC2, 0x00, 0x00E2Jul 7 20:57:27.038: MAC MANAGEMENT MESSAGE HEADERJul 7 20:57:27.038: DA, SA - 01E0.2F00.0001, 0014.F1E5.3818Jul 7 20:57:27.038: msg LEN - 0x00D0Jul 7 20:57:27.038: DSAP, SSAP - 0, 0Jul 7 20:57:27.038: control, version, type - 0x03, 0x04, 0x21Jul 7 20:57:27.038: 0x00D0: 01 02 07 07 01 01 01 02 02 00 00 08 01 01 09 01Jul 7 20:57:27.038: 0x00E0: 00 0C 01 01Jul 7 20:57:35.038: Non-primary MDD from Cable8/0/0 to RFID 961:Jul 7 20:57:35.038: message dump:Jul 7 20:57:35.038: 0x0000: C2 00 00 1C 9C 24 01E0 2F 00 00 01 00 14 F1 E5Jul 7 20:57:35.038: 0x0010: 38 18 00 0A 00 00 03 04 21 00 01 01 01 62Jul 7 20:57:35.038: Non-primary MDD from Cable8/0/0 to RFID 962:Jul 7 20:57:35.038: message dump:Jul 7 20:57:35.038: 0x0000: C2 00 00 1C 9C 24 01 E0 2F 00 00 01 00 14 F1 E5Jul 7 20:57:35.038: 0x0010: 38 18 00 0A 00 00 03 04 21 00 01 01 01 63Jul 7 20:57:35.038: Non-primary MDD from Cable8/0/0 to RFID 963:Jul 7 20:57:35.038: message dump:Jul 7 20:57:35.038: 0x0000: C2 00 00 1C 9C 24 01 E0 2F 00 00 01 00 14 F1 E5Jul 7 20:57:35.038: 0x0010: 38 18 00 0A 00 00 03 04 21 00 01 01 01 64Related Commands
debug cable md-sg
To enable debugging information for MAC domain service group messages, use the debug cable md-sg command in privileged EXEC mode. To turn off debugging, use the no form of this command.
debug cable md-sg
no debug cable md-sg
Syntax Description
This command has no arguments or keywords.
Command Modes
Privileged EXEC (#)
Command History
Examples
The following is a sample output of the debug cable md-sg command:
Router# debug cable md-sgCMTS md-sg debugging is onRouter#Jul 7 21:04:24.938: Ambiguity Resolution: B_INIT_RNG_REQ notified (us = 1).Jul 7 21:04:24.938: Ambiguity Resolution Validate Candidate: (B_INIT_RNG_REQ) found[ 1 ] uschan = 0x1, reachable = 0x1, failed = 0x0.Jul 7 21:04:24.938: Ambiguity Resolution: Done (case 1 b_init) with sg_id = 1.Jul 7 21:04:38.858: Ambiguity Resolution: B_INIT_RNG_REQ notified (us = 1).Jul 7 21:04:38.858: Ambiguity Resolution Validate Candidate: (B_INIT_RNG_REQ) found[ 1 ] uschan = 0x1, reachable = 0x1, failed = 0x0.Jul 7 21:04:38.858: Ambiguity Resolution: Done (case 1 b_init) with sg_id = 1.Jul 7 21:04:50.438: Ambiguity Resolution: B_INIT_RNG_REQ notified (us = 1).Jul 7 21:04:50.438: Ambiguity Resolution Validate Candidate: (B_INIT_RNG_REQ) found[ 1 ] uschan = 0x1, reachable = 0x1, failed = 0x0.Jul 7 21:04:50.438: Ambiguity Resolution: Done (case 1 b_init) with sg_id = 1.Jul 7 21:04:52.898: Ambiguity Resolution: B_INIT_RNG_REQ notified (us = 1).Jul 7 21:04:52.898: Ambiguity Resolution Validate Candidate: (B_INIT_RNG_REQ) found[ 1 ] uschan = 0x1, reachable = 0x1, failed = 0x0.Jul 7 21:04:52.898: Ambiguity Resolution: Done (case 1 b_init) with sg_id = 1.Jul 7 21:05:06.938: Ambiguity Resolution: B_INIT_RNG_REQ notified (us = 1).Jul 7 21:05:06.938: Ambiguity Resolution Validate Candidate: (B_INIT_RNG_REQ) found[ 1 ] uschan = 0x1, reachable = 0x1, failed = 0x0.Jul 7 21:05:06.938: Ambiguity Resolution: Done (case 1 b_init) with sg_id = 1.Jul 7 21:05:08.378: Ambiguity Resolution: B_INIT_RNG_REQ notified (us = 1).Jul 7 21:05:08.378: Ambiguity Resolution Validate Candidate: (B_INIT_RNG_REQ) found[ 1 ] uschan = 0x1, reachable = 0x1, failed = 0x0.Jul 7 21:05:08.378: Ambiguity Resolution: Done (case 1 b_init) with sg_id = 1.Jul 7 21:05:22.538: Ambiguity Resolution: B_INIT_RNG_REQ notified (us = 1).Jul 7 21:05:22.538: Ambiguity Resolution Validate Candidate: (B_INIT_RNG_REQ) found[ 1 ] uschan = 0x1, reachable = 0x1, failed = 0x0.Jul 7 21:05:22.538: Ambiguity Resolution: Done (case 1 b_init) with sg_id = 1.Jul 7 21:05:24.998: Ambiguity Resolution: B_INIT_RNG_REQ notified (us = 1).Jul 7 21:05:24.998: Ambiguity Resolution Validate Candidate: (B_INIT_RNG_REQ) found[ 1 ] uschan = 0x1, reachable = 0x1, failed = 0x0.Jul 7 21:05:24.998: Ambiguity Resolution: Done (case 1 b_init) with sg_id = 1.Jul 7 21:05:36.818: Ambiguity Resolution: B_INIT_RNG_REQ notified (us = 1).Jul 7 21:05:36.818: Ambiguity Resolution Validate Candidate: (B_INIT_RNG_REQ) found[ 1 ] uschan = 0x1, reachable = 0x1, failed = 0x0.Jul 7 21:05:36.818: Ambiguity Resolution: Done (case 1 b_init) with sg_id = 1.Related Commands
debug cable phs
To display the activities of the payload header suppression and restoration (PHS) driver, use the debug cable phs command in privileged EXEC mode. The no form of this command disables debugging output.
debug cable phs
no debug cable phs
Syntax Description
This command has no arguments or keywords.
Command Modes
Privileged EXEC
Command History
12.1(4)CX
This command was introduced.
12.2(4)BC1
Support was added to the Release 12.2 BC train.
Usage Guidelines
Do not use this command when you have a large number of active CMs on your network, because it could generate a huge amount of output to the console port.
This command displays the output for both the upstream and downstream drivers. The upstream receive driver restores headers that have been suppressed by CMs, and the downstream driver suppresses specific fields in packet header before forwarding a frame to the CM.
Examples
The following example shows typical output from PHS debugging:
Router# debug cable phsCMTS payload header suppression debugging is on00:02:55: New PHS rule: 1 (SFID: 9)size : 34mask : 00 00 00 03 FC 00 00 00 field: 00 00 00 00 00 00 00 00Add PHS rule 1 to CFR ID 100:02:57: New PHS rule: 1 (SFID: 11)size : 34mask : 00 00 00 03 FC 00 00 00 field: 00 00 00 00 00 00 00 00Add PHS rule 1 to CFR ID 1Router#debug cable phy
To activate debugging of messages generated in the cable physical layer, use the debug cable phy command in privileged EXEC mode. To disable debugging output, use the no form of the command.
debug cable phy
no debug cable phy
Syntax Description
This command has no arguments or keywords.
Command Modes
Privileged EXEC
Command History
Usage Guidelines
This command activates debugging of messages generated in the PHY system, which is the physical layer where upstream and downstream activity between the Cisco CMTS and the HFC network is controlled. When this command is activated, any messages generated in the PHY system are displayed on the Cisco CMTS console.
Examples
The following is typical output from the debug cable phy command.
cmts_phy_init: mac_version == BCM3210_FPGAbcm3033_set_tx_sym_rate(5056941)stintctl = 0x54484800bcm3033_set_tx_if_freq(44000000)stfreqctl = 0x5BAAAAAAcmts_phy_init_us: U0 part_id = 0x3136, revid = 0x05, rev_id2 = 0x64cmts_phy_init: mac_version == BCM3210_FPGAMedia access controller chip version.bcm3033_set_tx_sym_rate(5056941)stintctl = 0x54484800Physical layer symbol rate register value.00:51:49: bcm3033_set_tx_if_freq(44000000)00:51:49: stfreqctl = 0x5BAAAAAAPhysical layer intermediate frequency (IF) register value.00:51:49: cmts_phy_init_us: U0 part_id = 0x3136, revid = 0x05, rev_id2 = 0x64Physical layer receiver chip part version.debug cable privacy
To activate debugging of baseline privacy, use the debug cable privacy command in privileged EXEC mode. To disable debugging output, use the no form of the command.
debug cable privacy
no debug cable privacy
Syntax Description
This command has no arguments or keywords.
Command Modes
Privileged EXEC
Command History
Usage Guidelines
This command activates debugging of the Baseline Privacy Interface (BPI) feature. When this command is activated, the BPI handler generates a debugging message whenever the BPI state changes or a BPI-related event occurs.
Tip
Note
Examples
The following is typical output from the debug cable privacy command:
02:32:08: CMTS Received AUTH REQ.02:32:08: Created a new CM key for 0030.96f9.65d9.02:32:08: CMTS generated AUTH_KEY.02:32:08: Input : 70D158F106B0B7502:32:08: Public Key:02:32:08: 0x0000: 30 68 02 61 00 DA BA 93 3C E5 41 7C 20 2C D1 8702:32:08: 0x0010: 3B 93 56 E1 35 7A FC 5E B7 E1 72 BA E6 A7 71 9102:32:08: 0x0020: F4 68 CB 86 A8 18 FB A9 B4 DD 5F 21 B3 6A BE CE02:32:08: 0x0030: 6A BE E1 32 A8 67 9A 34 E2 33 4A A4 0F 8C DB BD02:32:08: 0x0040: D0 BB DE 54 39 05 B0 E0 F7 19 29 20 8C F9 3A 6902:32:08: 0x0050: E4 51 C6 89 FB 8A 8E C6 01 22 02 34 C5 1F 87 F602:32:08: 0x0060: A3 1C 7E 67 9B 02 03 01 00 0102:32:08: RSA public Key subject:02:32:08: 0x0000: 30 7C 30 0D 06 09 2A 86 48 86 F7 0D 01 01 01 0502:32:08: 0x0010: 00 03 6B 00 30 68 02 61 00 DA BA 93 3C E5 41 7C02:32:08: 0x0020: 20 2C D1 87 3B 93 56 E1 35 7A FC 5E B7 E1 72 BA02:32:08: 0x0030: E6 A7 71 91 F4 68 CB 86 A8 18 FB A9 B4 DD 5F 2102:32:08: 0x0040: B3 6A BE CE 6A BE E1 32 A8 67 9A 34 E2 33 4A A402:32:08: 0x0050: 0F 8C DB BD D0 BB DE 54 39 05 B0 E0 F7 19 29 2002:32:08: 0x0060: 8C F9 3A 69 E4 51 C6 89 FB 8A 8E C6 01 22 02 3402:32:08: 0x0070: C5 1F 87 F6 A3 1C 7E 67 9B 02 03 01 00 0102:32:08: RSA encryption result = 002:32:08: RSA encrypted output:02:32:08: 0x0000: B6 CA 09 93 BF 2C 05 66 9D C5 AF 67 0F 64 2E 3102:32:08: 0x0010: 67 E4 2A EA 82 3E F7 63 8F 01 73 10 14 4A 24 ED02:32:08: 0x0020: 65 8F 59 D8 23 BC F3 A8 48 7D 1A 08 09 BF A3 A802:32:08: 0x0030: D6 D2 5B C4 A7 36 C4 A9 28 F0 6C 5D A1 3B 92 A202:32:08: 0x0040: BC 99 CC 1F C9 74 F9 FA 76 83 ED D5 26 B4 92 EE02:32:08: 0x0050: DD EA 50 81 C6 29 43 4F 73 DA 56 C2 29 AF 05 5302:32:08: CMTS sent AUTH response.02:32:08: CMTS Received TEK REQ.02:32:08: Created a new key for SID 2.02:32:08: CMTS sent KEY response.Related Commands
debug cable qos
To activate quality-of-service (QoS) debugging, use the debug cable qos command in privileged EXEC mode. To disable debugging output, use the no form of this command.
debug cable qos
no debug cable qos
Syntax Description
This command has no arguments or keywords.
Command Modes
Privileged EXEC
Command History
Usage Guidelines
This command activates debugging of QoS. When this command is activated, any messages related to QoS parameters are displayed on the Cisco CMTS console.
Examples
The following is typical output from the debug cable qos command:
CMTS_QOS_LOG_NO_MORE_QOS_INDEXModems cannot add more entries to the class of service table.CMTS_QOS_LOG_NOMORE_QOSPRF_MEMMemory allocation error when creating class of service table entry.CMTS_QOS_LOG_NO_CREATION_ALLOWEDClass of service entry cannot be created by modem. Use CLI or SNMPinterface instead of the modem's TFTP configuration file.CMTS_QOS_LOG_CANNOT_REGISTER_COS_SIDA service identifier (SID) could not be assigned to the registering modem.CMTS_QOS_LOG_CANNOT_DEREGISTER_COS_SIDThe modem's service identifier (SID) was already removed.CMTS_QOS_LOG_MSLOT_TIMEBASE_WRAPPEDThe 160 KHz timebase clock drives a 26-bit counter which wraps aroundapproximately every 7 minutes. This message is generated every time itwraps around.debug cable range
To display ranging messages from CMs on the HFC network, use the debug cable range command in privileged EXEC mode. To disable debugging output, the no form of the command.
debug cable range
no debug cable range
Syntax Description
This command has no arguments or keywords.
Command Modes
Privileged EXEC
Command History
Usage Guidelines
This command activates debugging of ranging messages from CMs on the HFC network. When this command is activated, any ranging messages generated when CMs request or change their upstream frequencies are displayed on the Cisco CMTS console. Use this command to display the details of the initial and station maintenance procedures. The initial maintenance procedure is used for link establishment. The station maintenance procedure is used for link keepalive monitoring.
Examples
The following shows typical output from the debug cable range command.
Got a ranging requestSID value is 0 on Interface Cable3/0/U0CM mac address 00:10:7B:43:AA:21 Timing offset is 33123E 1E 3F FF 00 00 59 BF 01 15 F8 01 A7 00 0C F0The following output shows typical output when a CM first seeks to establish a link to the Cisco CMTS. The service identifier (SID) value of 0 indicates that the modem has no assigned SID. The CM mac address is the MAC address of the modem's radio frequency (RF) interface, not its Ethernet interface. The Timing offset is a measure of the distance between the modem and the Cisco CMTS, expressed in 10.24 MHz clocks. This value is adjusted down to zero by the maintenance procedures. The first 16 bytes of the prepended header of the message are dumped in hexadecimal.
CM mac address 0010.7b43.aa21found..Assigned SID #2 on Interface Cable3/0/U0Timing offset is CF0Power value is 15F8, or -1 dBFreq Error = 423, Freq offset is 1692Ranging Modem with Sid 2 on i/f : Cable3/0/U0The following is typical output when the CM is first assigned a SID during initial maintenance:
Initial Range Message Received on Interface Cable3/0/U0CMTS reusing old sid : 2 for modem : 0010.7b43.aa21Timing offset is CF0Power value is 15F8, or -1 dBFreq Error = 423, Freq offset is 1692Ranging Modem with Sid 2 on i/f : Cable3/0/U0The following is typical output when the modem is reassigned the same SID during initial maintenance.
Ranging Modem with Sid 2 on i/f : Cable3/0/U0Got a ranging requestSID value is 2 on Interface Cable3/0/U0CM mac address 00:10:7B:43:AA:21Timing offset is 0Power value is 1823, or -1 dBFreq Error = 13, Freq offset is 0Ranging has been successful for SID 2 on Interface Cable3/0/U0Output occurs when the modem is polled by the CMTS during station maintenance. Polling happens at a minimum rate of once every 10 seconds.
debug cable receive
To display debug messages for messages received on the upstream from a CM, use the debug cable receive command in privileged EXEC mode. To stop displaying debug messages, use the no form of this command.
debug cable receive
no debug cable receive
Syntax Description
This command has no arguments or keywords.
Command Modes
Privileged EXEC
Command History
12.0(7)XR
This command was introduced.
12.1(1)T, 12.1(2)EC1
This command was disabled.
12.1(11b)EC
This command was removed.
Examples
The following command enables debugging of upstream messages:
router# debug cable receiveCMTS debug Rx debugging is onThe debug cable receive command was disabled in Cisco IOS Release 12.1 T, 12.1 EC, and later releases, although it still appears in the CLI until Cisco IOS Release 12.1(11b)EC. To monitor the packets received from the CMs, use the debug ip packet command instead.
Because the debug ip packet command produces a large volume of messages, you must use it together with an access list to restrict the messages to a particular CM or CPE device to avoid affecting system performance. For example, the following commands would set up an access list that monitors all traffic being sent between the hosts with the two specified IP addresses:
router# configure terminalrouter(config)# access-list 150 permit ip host ip-address-1 host ip-address-2router(config)# access-list 150 permit ip host ip-address-2 host ip-address-1router(config)# exitrouter# debug ip packet 150 detailRelated Commands
debug cable transmit
Enables debugging for transmitted packets.
debug ip packet
Enables debugging of IP packets received and transmitted by the router.
debug cable registration
To display debug messages for the CM registration process, use the debug cable registration command in privileged EXEC mode. To stop displaying debug messages, use the no form of this command.
debug cable registration
no debug cable registration
Syntax Description
This command has no arguments or keywords.
Command Modes
Privileged EXEC
Command History
Usage Guidelines
The debug cable registration command displays messages about the registration request and response messages sent and received by the CMTS when a CM initiates the DOCSIS registration process. To see the relevant messages, you must also enable debugging for a particular interface or CM using the debug cable interface or debug cable mac-address commands.
Examples
The following shows typical debugging output from a registration process:
router# debug cable interface c3/0 verboserouter# debug cable registrationCMTS registration debugging is onJul 4 14:31:37.471: Registration request from 0001.9659.3ef7, SID 3 on Cable3/0/U2Jul 4 14:31:37.471: Found a network access control parameterJul 4 14:31:37.471: The Ntw Access Control is 1Jul 4 14:31:37.475: This TLV is GOODJul 4 14:31:37.475: Found a class of service blockJul 4 14:31:37.475: The CLASS ID : 5Jul 4 14:31:37.475: The MAX DS RATE : 3000000Jul 4 14:31:37.475: The MAX US RATE : 2000000Jul 4 14:31:37.475: This TLV is GOODJul 4 14:31:37.475: Found vendor extensionsJul 4 14:31:37.475: Cisco Vendor ID Field found(ok)Jul 4 14:31:37.475: No. of requested phone lines is 2Jul 4 14:31:37.475: This TLV is GOODJul 4 14:31:37.475: Found vendor extensionsJul 4 14:31:37.475: Cisco Vendor ID Field found(ok)Jul 4 14:31:37.475: IP precedence specific subtype foundJul 4 14:31:37.475: IP Precedence value: 0 Rate Limit: 10000Jul 4 14:31:37.475: This TLV is GOODJul 4 14:31:37.475: Found Max CPEJul 4 14:31:37.475: The Max CPE is 10Jul 4 14:31:37.475: This TLV is GOODJul 4 14:31:37.475: Found CM MICJul 4 14:31:37.475: CM Mic: 5A D5 58 DC E8 2B 5B 24 6E 4E 69 84 17 B9 AB 36Jul 4 14:31:37.475: This TLV is GOODJul 4 14:31:37.475: Found CMTS MICJul 4 14:31:37.475: CMTS Mic: A7 E4 15 6 F9 2F BA 81 FE 22 E4 92 5F 81 D4 BBJul 4 14:31:37.475: This TLV is GOODJul 4 14:31:37.475: Found modem ipJul 4 14:31:37.475: The modem ip value is 10.200.69.90Jul 4 14:31:37.475: This TLV is GOODJul 4 14:31:37.475: Found modem capabilitiesJul 4 14:31:37.475: Modem Caps Length is 18Jul 4 14:31:37.475: Modem Caps values:Jul 4 14:31:37.475: 0x0000: 01 01 01 02 01 00 03 01 00 04 01 00 05 01 00 06Jul 4 14:31:37.475: 0x0010: 01 00Jul 4 14:31:37.475: Concatenation is on for this CMJul 4 14:31:37.475: Unknown capability type 2: IgnoredJul 4 14:31:37.475: Unknown capability type 3: IgnoredJul 4 14:31:37.475: Unknown capability type 4: IgnoredJul 4 14:31:37.475: Unknown capability type 5: IgnoredJul 4 14:31:37.475: Unknown capability type 6: IgnoredJul 4 14:31:37.475: This TLV is GOODJul 4 14:31:37.475: Finished parsing REG RequestJul 4 14:31:37.475: Sec sids obtained for all requested classes of serviceJul 4 14:31:37.475: Performing connection admission control (CAC) for each SidJul 4 14:31:37.475: CAC Status for ClassID:5 is CAC_SUCCESSJul 4 14:31:37.475: Building a GOOD REG-RSPJul 4 14:31:37.475: Adding Modem Caps to the Response to REG RSPJul 4 14:31:37.475: Registration Status: ok (0)Jul 4 14:31:37.475: ClassId:5 assigned QoS Sid:3Jul 4 14:31:37.475: Adding Service Class Data TLV:Jul 4 14:31:37.475: 0x0000: 01 07 01 01 05 02 02 00 03Jul 4 14:31:37.475: Adding Modem Caps to Response:Jul 4 14:31:37.475: 0x0000: 05 03 01 01 01Jul 4 14:31:37.475: Registration Response:Jul 4 14:31:37.475: 0x0000: C2 00 00 29 00 00 00 01 96 59 3E F7 00 30 7B F9Jul 4 14:31:37.475: 0x0010: 40 54 00 17 00 00 03 01 07 00 00 03 00 01 07 01Jul 4 14:31:37.479: 0x0020: 01 05 02 02 00 03 05 03 01 01 01Jul 4 14:31:37.479: Registration Response TransmittedThe following example shows what can occasionally occur when a shared secret has been implemented. Some CMs calculate the MD5 Message Integrity Check (MIC) over the length of the registration TLV parameters as well as the length of the shared secret itself, while other CMS calculate the MIC value only over the length of the registration TLV parameters. The Cisco CMTS attempts to verify the MIC and shared secret values using the first technique, and if that fails, the CMTS then uses the second technique to verify the CM.
Jun 28 12:17:36.171: Registration request from 00c0.abcd.ef01, SID 58 on Cable5/0/U0Jun 28 12:17:36.171: Found Network Access TLVJun 28 12:17:36.171: Found Class Of Service TLV BlockJun 28 12:17:36.171: Found Max CPEs TLVJun 28 12:17:36.171: Found TFTP Server Provisioned CM Address TLVJun 28 12:17:36.171: Found CM-MIC TLVJun 28 12:17:36.171: Found CMTS-MIC TLVJun 28 12:17:36.171: Found Modem Capabilities TLVJun 28 12:17:36.171: Found CM IP Address TLVJun 28 12:17:36.171: Computing CMTS-MIC to validate REG-REQ data.Jun 28 12:17:36.171: CMTS_MIC(rfc2104) failed text + keyJun 28 12:17:36.171: CMTS_MIC(rfc2104) passedJun 28 12:17:36.171: REG-RSP Status : ok (0)Jun 28 12:17:36.171: Registration Response TransmittedThe following example shows typical output when a CM attempts to come online without downloading a DOCSIS configuration file from a TFTP server through the Cisco CMTS cable interface, when the cable tftp-enforce command has been used.
Router# debug cable interface c3/0 verboseRouter# debug cable registrationCMTS registration debugging is onMay 14 22:33:21.474: Registration request from 5555.7366.12fb, SID 2 on Cable3/0/U0May 14 22:33:21.474: Cable Modem sent Registration Request without attempting TFTPSLOT 3/0: May 14 22:33:21.474: %UBR7200-4-REGISTRATION_BEFORE_TFTP: <133>CMTS[Cisco]:<????????> Registration request unexpected: Cable Modem did not attempt TFTP. CM Mac Addr <5555.7366.12fb>Registration failed for Cable Modem 5555.7366.12fb on interface Cable3/0/U0:CoS/Sflow/Cfr/PHS failed in REG-REQMay 14 22:33:21.474: REG-RSP Status : failure (2)May 14 22:33:21.474: Registration Response:May 14 22:33:21.474: 0x0000: C2 00 00 1B 00 00 00 50 73 4E B4 19 00 05 00 E0May 14 22:33:21.474: 0x0010: 56 AC 00 09 00 00 03 01 07 00 00 02 02May 14 22:33:21.474: Registration Response Transmitted
Tip
Related Commands
debug cable remote-query
To display debug messages for remote modem queries, use the debug cable remote-query command in privileged EXEC mode. To stop displaying debug messages, use the no form of this command.
debug cable remote-query
no debug cable remote-query
Syntax Description
This command has no arguments or keywords.
Command Modes
Privileged EXEC
Command History
Examples
The following example shows typical debugging output for a successful poll of the CMs:
router# debug cable remote-queryremote-query debugging is on.For IP address 209.165.200.223Nov 10 15:56:50.241: docsIfSignalQualityEntry.5.4 = 380Nov 10 15:56:50.241: docsIfMibObjects.2.2.1.3.2 = 360Nov 10 15:56:50.245: docsIfDownstreamChannelEntry.6.4 = -30Nov 10 15:56:50.245: docsIfUpstreamChannelEntry.6.3 = 12422Nov 10 15:56:50.249: docsIfSignalQualityEntry.6.4 = 0Nov 10 15:56:50.477:The following example shows typical debugging output when the waiting queue at the CMTS is empty:
SNMP proxy exec got event, but queue is emptyThe following example shows typical debugging output when you try to modify the polling interval or community string while the polling in is progress:
Community string if modified will not be reflected
Note
Related Commands
debug cable reset
To display debugging messages when cable interfaces are reset due to the complete loss of received packets, use the debug cable reset command in privileged EXEC mode. To disable debugging output, use the no form of this command.
debug cable reset
no debug cable reset
Syntax Description
This command has no arguments or keywords.
Command Modes
Privileged EXEC
Command History
Usage Guidelines
This command activates display of reset messages from cable interfaces.
Examples
The following shows typical output from the debug cable reset command:
Router# debug cable resetCMTS reset debugging is onRouter#Resetting CMTS interface. Num SIDs = 32 Ranging count = 10Elapsed time: 21 secondsdebug cable rfmib
To display debugging messages about when the DOCSIS-IF-MIB MIB is updated, use the debug cable rfmib command in privileged EXEC mode. To disable debugging output, use the no form of this command.
debug cable rfmib
no debug cable rfmib
Syntax Description
This command has no arguments or keywords.
Command Modes
Privileged EXEC
Command History
Usage Guidelines
This command displays debugging messages when the counters in the DOCSIS-IF-MIB are updated.
Note
http://www.cisco.com/go/mibsExamples
The following shows typical output from the debug cable rfmib command:
Router# debug cable rfmibCMTS RFMIB debugging is onRouter#CMTS is calculating utilization.Calculating all utilization data.Polling and calculating all channels utilization data.Polling and calculating all channels utilization data.Cable7/0/0 DScur_snmp_ifOutOctets 29282580cur_snmp_total_bytes 3348841605last_snmp_ifOutOctets 27327636last_snmp_total_bytes 3126121018Cable7/0/0 DS, delta_outoctets 1954944, delta_total_bytes 222720587, chan_utilization 1Cable7/0/0 US 2cur_snmp_total_ms 36065552cur_snmp_ucast_grnt_ms 11287cur_snmp_used_cntn_ms 1238last_snmp_total_ms 33665428last_snmp_ucast_grnt_ms 10807last_snmp_used_cntn_ms 1238Cable7/0/0 US 2 delta_total_ms 2400124, delta_ucast_grnt_ms 480, delta_used_cntn_ms 0, chan_utilization 0debug cable service-ds-selection
To enable the debugging for downstream selection, use the debug cable service command in privileged EXEC mode. To disable debugging for downstream-selection, use the no form of the command.
debug cable service-ds-selection {event|timer}
no debug cable service {event|timer}
Syntax Description
event
Enables debug messages for Cable downstream selection events.
timer
Enables debug messages for Cable downstream selection timer.
Command Default
No debug messages for downstream selection are enabled.
Command Modes
Privileged EXEC
Command History
Usage Guidelines
The debug cable service command is intended for use by Cisco Systems technical support personnel.
Examples
The following example shows how to enable debugging for downstream selection events:
Router debug cable service-ds-selection eventRelated Commands
Command
test cable voice
Manually set voice tag of a cable modem to test downstream channel selection for a voice-enabled modem.
debug cable specmgmt
To debug spectrum management (frequency agility) on the HFC network, use the debug cable specmgmt command in privileged EXEC mode. To disable debugging output, use the no form of this command.
debug cable specmgmt
no debug cable specmgmt
Syntax Description
This command has no arguments or keywords.
Command Modes
Privileged EXEC
Command History
11.3NA
This command was introduced.
12.0(4)XI
This command was removed and replaced by the debug cable hw-spectrum command.
Usage Guidelines
This command activates debugging of spectrum management (frequency agility) on the HFC network. When this command is activated, any messages generated due to spectrum group activity will be displayed on the Cisco CMTS console. Spectrum group activity can be additions or changes to spectrum groups, or frequency and power lever changes controlled by spectrum groups.
Examples
The following shows sample output from the debug cable specmgmt command:
Router# debug cable specmgmtCMTS specmgmt debugging is onRouter#reassign-blind: U0 not present or shutdowndebug cable startalloc
To debug channel allocations on the HFC network, use the debug cable startalloc command in privileged EXEC mode. To disable debugging output, use the no form of this command.
debug cable startalloc
no debug cable startalloc
Syntax Description
This command has no arguments or keywords.
Command Modes
Privileged EXEC
Command History
Usage Guidelines
This command activates debugging of the channel allocations on the HFC network. When this command is activated, any messages generated when channels are allocated to CMs on the HFC network are displayed on the Cisco CMTS console.
Caution
Examples
The following shows sample output from the debug cable startalloc command:
Router# debug cable startallocRouter#00:53:27: Cable3/U0 MAP startalloc adjusted by 1 mslots00:53:27: Cable4/U0 MAP startalloc adjusted by 3 mslots00:53:27: Cable3/U0 MAP startalloc adjusted by 5 mslots00:53:27: Cable4/U0 MAP startalloc adjusted by 4 mslots00:53:28: Cable3/U0 MAP startalloc adjusted by 4 mslots00:53:28: Cable4/U0 MAP startalloc adjusted by 5 mslotsdebug cable subscriber-monitoring
To display enforce-rule debug messages for subscriber traffic management on the Cisco CMTS routers, use the debug cable subscriber-monitoring command in privileged EXEC mode. To stop the display of debug messages, use the no form of this command.
debug cable subscriber-monitoring
no debug cable subscriber-monitoring
Syntax Description
This command has no arguments or keywords.
Command Default
No default behavior or values
Command Modes
Privileged EXEC (#)
Command History
Usage Guidelines
Because this command can produce a large volume of debug information, use this command only when you have also enabled debugging for a particular interface or MAC address, using the debug cable interface and debug cable mac-address commands, respectively.
Examples
The following example shows how to enable debugging output using the debug cable subscriber-monitoring command:
Router# debug cable subscriber-monitoringsubscriber monitoring debugging is oncmts_enf_map_sm_to_qos: enforced=9, penalty_life_time=10080cmts_enf_map_sm_to_qos: Found rule #=9, rule_name=name, dir=UScmts_enf_map_sm_to_registered_qos1: us smp=0x00, ds smp=0x1FRelated Commands
debug cable telco-return
To display debug messages for telco-return events, use the debug cable telco-return command in privileged EXEC mode. To disable debugging output, use the no form of this command.
debug cable telco-return
no debug cable telco-return
Syntax Description
This command has no arguments or keywords.
Command Modes
Privileged EXEC
Command History
Usage Guidelines
This command is supported only in images that support telco-return operation (-t-).
Examples
The following is sample output from the debug cable telco-return and debug cable telco-return msg commands:
Router# debug cable telco-returnRouter# debug cable telco-return msg01:17:31:Sending TCD message:TLV type = 1TLV len = 56Factory default flag: 1Phone number 1: 5551212Service provider name:uBR7246Connection threshold: 10Username: guestPassword: passwordDHCP authenticate: 1DHCP server: 10.10.255.255PPP authentication: 2Manual dial: 1Sending TSI message:DS channel IP address: 10.10.10.10Registration IP address:10.10.10.10CMTS boot time: 3080626752DS channel ID: 0Epoch: 1Related Commands
debug cable telco-return msg
Displays the Telephony Channel Descriptor (TCD) and Termination System Information (TSI) messages.
debug cable telco-return msg
To display the Telephony Channel Descriptor (TCD) and Termination System Information (TSI) messages that are sent downstream to the telco-return CMs, use the debug cable telco-return msg command in privileged EXEC mode. To disable debugging output, use the no form of this command.
debug cable telco-return msg
no debug cable telco-return msg
Syntax Description
This command has no arguments or keywords.
Command Modes
Privileged EXEC
Command History
Usage Guidelines
This command is supported only in images that support telco-return operation (-t-).
Examples
The following is sample output from the debug cable telco-return msg command:
Router# debug cable telco-returnRouter# debug cable telco-return msg01:17:31:Sending TCD message:TLV type = 1TLV len = 56Factory default flag: 1Phone number 1: 5551212Service provider name:uBR7246Connection threshold: 10Username: guestPassword: passwordDHCP authenticate: 1DHCP server: 10.10.255.255PPP authentication: 2Manual dial: 1Sending TSI message:DS channel IP address: 10.10.10.10Registration IP address:10.10.10.10CMTS boot time: 3080626752DS channel ID: 0Epoch: 1Related Commands
debug cable tlvs
To display the Type/Length/Value encodings (TLVs) parsed by the DOCSIS 1.1 TLV parser/encoder, use the debug cable tlvs command in privileged EXEC mode. The no form of this command disables debugging output.
debug cable tlvs
no debug cable tlvs
Syntax Description
This command has no arguments or keywords.
Command Modes
Privileged EXEC
Command History
Usage Guidelines
This command displays the TLVs for service flow encodings, classifier encodings, and PHS rules. Do not use this command when you have a large number of active CMs on your network because it could generate a huge amount of output to the console port.
Examples
The following example shows typical output for the debug cable tlvs command:
Router# debug cable tlvsCMTS TLV encodings debugging is on00:02:06: Registration request from 0003.e350.9b8d, SID 3 on Cable3/0/U000:02:06: TLV-Block Bytes:00:02:06: 0x0000: 03 01 01 12 01 10 1D 01 00 16 0F 01 01 01 03 0200:02:06: 0x0010: 00 04 09 06 03 04 0A 0A 00 02 18 07 01 02 00 0100:02:06: 0x0020: 06 01 07 18 07 01 02 00 02 06 01 07 18 07 01 0200:02:06: 0x0030: 00 03 06 01 01 18 07 01 02 00 04 06 01 01 19 0700:02:06: 0x0040: 01 02 00 09 06 01 07 19 07 01 02 00 0A 06 01 0100:02:06: 0x0050: 19 07 01 02 00 0B 06 01 01 19 07 01 02 00 0C 0600:02:06: 0x0060: 01 01 06 10 33 E0 BA 7A DA 81 1B 9B 8E 37 F5 3300:02:06: 0x0070: 1C 84 E7 4D 07 10 01 0C C8 DB F9 26 B7 D2 DD 0A00:02:06: 0x0080: 00 58 1E 14 15 FD 0C 04 0A 0A 00 02 08 03 00 0300:02:06: 0x0090: E3 05 21 02 01 01 03 01 01 04 01 01 05 01 00 0600:02:06: 0x00A0: 01 01 07 01 00 08 01 04 09 01 00 0A 01 01 0B 0100:02:06: 0x00B0: 08 01 01 0100:02:06: Found Network Access TLV00:02:06: Ntw Access Control : 100:02:06: Found Max CPEs TLV00:02:06: Maximum Number Of CPEs : 1600:02:06: Found Privacy Enable TLV00:02:06: Privacy Enable : 000:02:06: Found Upstream Packet Classifier TLV00:02:06: Classifier Reference : 100:02:06: Service-Flow Reference : 400:02:06: Found IP Packet Classifier Sub-TLV00:02:06: Source Address : 10.10.0.200:02:06: Found Upstream Service Flow TLV00:02:06: Service Flow Reference : 100:02:06: QoS Parameter Set Type : 0x700:02:06: Found Upstream Service Flow TLV00:02:06: Service Flow Reference : 200:02:06: QoS Parameter Set Type : 0x700:02:06: Found Upstream Service Flow TLV00:02:06: Service Flow Reference : 300:02:06: QoS Parameter Set Type : 0x100:02:06: Found Upstream Service Flow TLV00:02:06: Service Flow Reference : 400:02:06: QoS Parameter Set Type : 0x100:02:06: Found Downstream Service Flow TLV00:02:06: Service Flow Reference : 900:02:06: QoS Parameter Set Type : 0x700:02:06: Found Downstream Service Flow TLV00:02:06: Service Flow Reference : 1000:02:06: QoS Parameter Set Type : 0x100:02:06: Found Downstream Service Flow TLV00:02:06: Service Flow Reference : 1100:02:06: QoS Parameter Set Type : 0x100:02:06: Found Downstream Service Flow TLV00:02:06: Service Flow Reference : 1200:02:06: QoS Parameter Set Type : 0x100:02:06: Found CM-MIC TLV00:02:06: CM MIC:00:02:06: 0x0000: 33 E0 BA 7A DA 81 1B 9B 8E 37 F5 33 1C 84 E7 4D00:02:06: Found CMTS-MIC TLV00:02:06: CMTS MIC:00:02:06: 0x0000: 01 0C C8 DB F9 26 B7 D2 DD 0A 00 58 1E 14 15 FD00:02:06: Found CM IP Address TLV00:02:06: Modem IP Address : 10.10.0.200:02:06: Vendor Id:00:02:06: 0x0000: 00 03 E300:02:06: Found Modem Capabilities TLV00:02:06: DOCSIS Version : 100:02:06: Fragmentation Support : 100:02:06: Payload Header Suppresion Support : 100:02:06: IGMP Support : 000:02:06: Privacy Support : 100:02:06: Downstream SAID Support : 000:02:06: Upstream SID Support : 400:02:06: Optional Filtering Support : 000:02:06: Tx Equalizer Taps Per Symbol : 100:02:06: Tx Equalizer Taps Support : 800:02:06: Concatenation Support : 100:02:06: Performing admission control check00:02:06: Added Modem Capabilities TLV:00:02:06: 0x0000: 05 21 02 01 01 03 01 01 04 01 01 05 01 00 06 0100:02:06: 0x0010: 01 07 01 00 08 01 04 09 01 00 0A 01 01 0B 01 0800:02:06: 0x0020: 01 01 0100:02:06: Sfref = 1, SFID = 700:02:06: Added Service Flow Parameters TLV:00:02:06: 0x0000: 18 11 01 02 00 01 02 04 00 00 00 07 03 02 00 0300:02:06: 0x0010: 06 01 0700:02:06: Sfref = 2, SFID = 4300:02:06: Added Service Flow Parameters TLV:00:02:06: 0x0000: 18 11 01 02 00 02 02 04 00 00 00 2B 03 02 00 0B00:02:06: 0x0010: 06 01 0700:02:06: Sfref = 3, SFID = 4400:02:06: Added Service Flow Parameters TLV:00:02:06: 0x0000: 18 0D 01 02 00 03 02 04 00 00 00 2C 06 01 0100:02:06: Sfref = 4, SFID = 4500:02:06: Added Service Flow Parameters TLV:00:02:06: 0x0000: 18 0D 01 02 00 04 02 04 00 00 00 2D 06 01 0100:02:06: Sfref = 9, SFID = 800:02:06: Added Service Flow Parameters TLV:00:02:06: 0x0000: 19 0D 01 02 00 09 02 04 00 00 00 08 06 01 0700:02:06: Sfref = 10, SFID = 4600:02:06: Added Service Flow Parameters TLV:00:02:06: 0x0000: 19 0D 01 02 00 0A 02 04 00 00 00 2E 06 01 0100:02:06: Sfref = 11, SFID = 4700:02:06: Added Service Flow Parameters TLV:00:02:06: 0x0000: 19 0D 01 02 00 0B 02 04 00 00 00 2F 06 01 0100:02:06: Sfref = 12, SFID = 4800:02:06: Added Service Flow Parameters TLV:00:02:06: 0x0000: 19 0D 01 02 00 0C 02 04 00 00 00 30 06 01 0100:02:06: Cfr-ref = 1, CFID = 1, SF-ref 4, SFID 4500:02:06: Added Classifier Parameters TLV:00:02:06: 0x0000: 16 19 01 01 01 03 02 00 04 02 02 00 01 04 04 0000:02:06: 0x0010: 00 00 2D 09 06 03 04 0A 0A 00 0200:02:06: REG-RSP Status : ok (0), REG-ACK required from CM (0)00:02:06: Reg-Ack wait state successfully created00:02:06: Registration Response:00:02:06: 0x0000: C2 00 00 D9 00 00 00 03 E3 50 9B 8D 00 00 00 0000:02:06: 0x0010: 30 30 00 C7 00 00 03 01 07 00 00 03 00 05 21 0200:02:06: 0x0020: 01 01 03 01 01 04 01 01 05 01 00 06 01 01 07 0100:02:06: 0x0030: 00 08 01 04 09 01 00 0A 01 01 0B 01 08 01 01 0100:02:06: 0x0040: 18 11 01 02 00 01 02 04 00 00 00 07 03 02 00 0300:02:06: 0x0050: 06 01 07 18 11 01 02 00 02 02 04 00 00 00 2B 0300:02:06: 0x0060: 02 00 0B 06 01 07 18 0D 01 02 00 03 02 04 00 0000:02:06: 0x0070: 00 2C 06 01 01 18 0D 01 02 00 04 02 04 00 00 0000:02:06: 0x0080: 2D 06 01 01 19 0D 01 02 00 09 02 04 00 00 00 0800:02:06: 0x0090: 06 01 07 19 0D 01 02 00 0A 02 04 00 00 00 2E 0600:02:06: 0x00A0: 01 01 19 0D 01 02 00 0B 02 04 00 00 00 2F 06 0100:02:06: 0x00B0: 01 19 0D 01 02 00 0C 02 04 00 00 00 30 06 01 0100:02:06: 0x00C0: 16 19 01 01 01 03 02 00 04 02 02 00 01 04 04 0000:02:06: 0x00D0: 00 00 2D 09 06 03 04 0A 0A 00 0200:02:06: Registration Response Transmitted00:02:06: Registration acknowledgement from 0003.e350.9b8d, SID 3 on Cable3/0/U000:02:06: REG-ACK confirmation code : 0The following is a sample output displaying the TLVs on a Cisco uBR10012 router:
Router#debug cable tlvsCMTS TLV encodings debugging is on*Jul 7 19:39:28.366: Found Modem Capabilities TLV*Jul 7 19:39:28.366: Found Upstream Service Flow TLV*Jul 7 19:39:28.366: Found Downstream Service Flow TLV*Jul 7 19:39:28.366: Found Privacy Enable TLV*Jul 7 19:39:28.366: Subscriber Mgmt Filter Group Length: 20*Jul 7 19:39:28.366: Found Subscriber Mgmt Filter Group Type*Jul 7 19:39:28.366: Subscriber Mgmt Filter Group Length >= 20*Jul 7 19:39:28.366: Found Subscriber Mgmt. Control TLV: 35*Jul 7 19:39:28.366: Found Subscriber Mgmt IP table TLV*Jul 7 19:39:28.366: Found Vendor Specific Information TLVJul 7 19:39:28.394: Found CMTS-MIC TLVJul 7 19:39:28.394: Found Network Access TLVJul 7 19:39:28.394: Found Max CPEs TLVJul 7 19:39:28.394: Found Upstream Service Flow TLVJul 7 19:39:28.394: Found Downstream Service Flow TLVJul 7 19:39:28.394: Found Privacy Enable TLVJul 7 19:39:28.394: Found CM-MIC TLVJul 7 19:39:28.394: Found Modem Capabilities TLVJul 7 19:39:28.394: Found CM IP Address TLVRelated Commands
debug cable tod
To display debugging for the local time-of-day (ToD) server on the Cisco CMTS, use the debug cable tod command in privileged EXEC mode. To disable debugging output, use the no form of this command.
debug cable tod
no debug cable tod
Syntax Description
This command has no arguments or keywords.
Command Modes
Privileged EXEC
Command History
11.3 NA
This command was introduced.
12.2(11)BC2
Support for this command was added to the Release 12.2 BC train.
Usage Guidelines
This command displays information about the operation of the ToD server that is onboard the Cisco CMTS. Before this command will display any output, you must also use the debug cable interface command to enable debugging operations on each interface that has CMs you wish to monitor.
Examples
The following example shows typical output for the debug cable tod command:
Router# debug cable interface c3/0Router# debug cable todTOD server debugging is onRouter#000104: Jun 8 05:48:08.783: tod: Received request from 10.1.1.27 (0001.9659.4411) on Cable3/0000105: Jun 8 05:48:15.015: tod: Received request from 10.1.1.32 (0030.96f9.65d9) on Cable3/0000106: Jun 8 05:48:16.363: tod: Received request from 10.3.3.10 (0001.9659.43fd) on Cable3/0000107: Jun 8 05:48:17.335: tod: Received request from 10.2.2.43 (0002.fdfa.0a35) on Cable3/0For telco-return CMs, the ToD server verifies that the IP address for the CM making the ToD request is on the correct cable interface, so as to prevent IP spoofing. If the IP address and interface do not match, the following message is printed:
000104: Jun 8 05:48:08.783: tod: Cant match output i/f for telco returnRelated Commands
debug cable interface
Enables debugging on a specific cable interface.
debug cable mac-address
Enables debugging for MAC-layer information for a specific CM.
debug cable transmit
To display debug messages for messages that the CMTS transmits on the cable interface, use the debug cable transmit command in privileged EXEC mode. To stop displaying debug messages, use the no form of this command.
debug cable transmit
no debug cable transmit
Syntax Description
This command has no arguments or keywords.
Command Modes
Privileged EXEC
Command History
12.0(7)XR
This command was introduced.
12.1(1)T, 12.1(2)EC1
This command was disabled.
12.1(11b)EC
This command was removed.
Examples
The following command enables debugging of messages that the CMTS transmits on the cable interface:
Router# debug cable transmitCMTS debug transmit debugging is onRouter#The debug cable transmit command was disabled in Cisco IOS Release 12.1 T, 12.1 EC, and later releases, although it still appears in the CLI until Cisco IOS Release 12.1(11b)EC. To monitor the packets transmitted by the CMs, use the debug ip packet command instead.
Because the debug ip packet command produces a large volume of messages, you must use it together with an access list to restrict the messages to a particular CM or CPE device to avoid affecting system performance. For example, the following commands would set up an access list that monitors all traffic being sent between the hosts with the two specified IP addresses:
router# configure terminalrouter(config)# access-list 150 permit ip host ip-address-1 host ip-address-2router(config)# access-list 150 permit ip host ip-address-2 host ip-address-1router(config)# exitrouter# debug ip packet 150 detailRelated Commands
debug cable receive
Enables debugging for received packets.
debug ip packet
Enables debugging of IP packets received and transmitted by the router.
debug cable ubg
To enable debugging information for upstream bonding groups, use the debug cable ubg command in privileged EXEC mode. To turn off debugging, use the no form of this command.
debug cable ubg
no debug cable ubg
Syntax Description
This command has no arguments or keywords.
Command Modes
Privileged EXEC (#)
Command History
Examples
The following is a sample output of the debug cable ubg command:
Router#debug cable ubgCMTS UBG assignment info debugging is onApr 27 02:28:57.140: CM 001a.c3ff.d59e UBG input TCS: 0x000000FF; mtc_cap: 4Apr 27 02:28:57.140: CM 001a.c3ff.d59e UBG trace: Configure UBG listApr 27 02:28:57.140: UBG 1(4): bitmap 0x0000000F, attrib 0xA0000000Apr 27 02:28:57.140: UBG 2(4): bitmap 0x000000F0, attrib 0xA0000000Apr 27 02:28:57.140: UBG 3(1): bitmap 0x00000004, attrib 0xA0000000Apr 27 02:28:57.140: UBG 4(2): bitmap 0x00000003, attrib 0xA0000000Apr 27 02:28:57.140: UBG 5(1): bitmap 0x00000001, attrib 0xA0000000Apr 27 02:28:57.140: UBG 6(1): bitmap 0x00000002, attrib 0xA0000000Apr 27 02:28:57.140: UBG 7(2): bitmap 0x00000030, attrib 0xA0000000Apr 27 02:28:57.140: UBG 8(1): bitmap 0x00000010, attrib 0xA0000000Apr 27 02:28:57.140: UBG 9(1): bitmap 0x00000020, attrib 0xA0000000Apr 27 02:28:57.140: UBG 65536(1): bitmap 0x00000001, attrib 0x20000000Apr 27 02:28:57.140: UBG 65537(1): bitmap 0x00000002, attrib 0x20000000Apr 27 02:28:57.140: UBG 65538(1): bitmap 0x00000004, attrib 0x20000000Apr 27 02:28:57.140: UBG 65539(1): bitmap 0x00000008, attrib 0x20000000Apr 27 02:28:57.140: UBG 65540(1): bitmap 0x00000010, attrib 0x20000000Apr 27 02:28:57.140: UBG 65541(1): bitmap 0x00000020, attrib 0x20000000Apr 27 02:28:57.140: UBG 65542(1): bitmap 0x00000040, attrib 0x20000000Apr 27 02:28:57.140: UBG 65543(1): bitmap 0x00000080, attrib 0x20000000Apr 27 02:28:57.140: CM 001a.c3ff.d59e UBG trace: ubg after MC & mtc cap matchApr 27 02:28:57.140: UBG 1(4): bitmap 0x0000000F, attrib 0xA0000000Apr 27 02:28:57.140: UBG 2(4): bitmap 0x000000F0, attrib 0xA0000000Apr 27 02:28:57.140: UBG 3(1): bitmap 0x00000004, attrib 0xA0000000Apr 27 02:28:57.140: UBG 4(2): bitmap 0x00000003, attrib 0xA0000000Apr 27 02:28:57.140: UBG 5(1): bitmap 0x00000001, attrib 0xA0000000Apr 27 02:28:57.140: UBG 6(1): bitmap 0x00000002, attrib 0xA0000000Apr 27 02:28:57.140: UBG 7(2): bitmap 0x00000030, attrib 0xA0000000Apr 27 02:28:57.140: UBG 8(1): bitmap 0x00000010, attrib 0xA0000000Apr 27 02:28:57.140: UBG 9(1): bitmap 0x00000020, attrib 0xA0000000Apr 27 02:28:57.140: UBG 65536(1): bitmap 0x00000001, attrib 0x20000000Apr 27 02:28:57.140: UBG 65537(1): bitmap 0x00000002, attrib 0x20000000Apr 27 02:28:57.140: UBG 65538(1): bitmap 0x00000004, attrib 0x20000000Apr 27 02:28:57.140: UBG 65539(1): bitmap 0x00000008, attrib 0x20000000Apr 27 02:28:57.140: UBG 65540(1): bitmap 0x00000010, attrib 0x20000000Apr 27 02:28:57.140: UBG 65541(1): bitmap 0x00000020, attrib 0x20000000Apr 27 02:28:57.140: UBG 65542(1): bitmap 0x00000040, attrib 0x20000000Apr 27 02:28:57.140: UBG 65543(1): bitmap 0x00000080, attrib 0x20000000Apr 27 02:28:57.140: CM 001a.c3ff.d59eSF_REQ: 0x00000000, SF_FOR: 0x00000000,CM_REQ: 0x00000000, CM_FOR: 0x00000000Apr 27 02:28:57.140: CM 001a.c3ff.d59e UBG trace: ubg after SF attrib matchApr 27 02:28:57.140: UBG trace: input queueApr 27 02:28:57.140: UBG 1(4): bitmap 0x0000000F, attrib 0xA0000000Apr 27 02:28:57.140: UBG 2(4): bitmap 0x000000F0, attrib 0xA0000000Apr 27 02:28:57.140: UBG 3(1): bitmap 0x00000004, attrib 0xA0000000Apr 27 02:28:57.140: UBG 4(2): bitmap 0x00000003, attrib 0xA0000000Apr 27 02:28:57.140: UBG 5(1): bitmap 0x00000001, attrib 0xA0000000Apr 27 02:28:57.140: UBG 6(1): bitmap 0x00000002, attrib 0xA0000000Apr 27 02:28:57.140: UBG 7(2): bitmap 0x00000030, attrib 0xA0000000Apr 27 02:28:57.140: UBG 8(1): bitmap 0x00000010, attrib 0xA0000000Apr 27 02:28:57.140: UBG 9(1): bitmap 0x00000020, attrib 0xA0000000Apr 27 02:28:57.140: UBG 65536(1): bitmap 0x00000001, attrib 0x20000000Apr 27 02:28:57.140: UBG 65537(1): bitmap 0x00000002, attrib 0x20000000Apr 27 02:28:57.140: UBG 65538(1): bitmap 0x00000004, attrib 0x20000000Apr 27 02:28:57.140: UBG 65539(1): bitmap 0x00000008, attrib 0x20000000Apr 27 02:28:57.140: UBG 65540(1): bitmap 0x00000010, attrib 0x20000000Apr 27 02:28:57.140: UBG 65541(1): bitmap 0x00000020, attrib 0x20000000Apr 27 02:28:57.140: UBG 65542(1): bitmap 0x00000040, attrib 0x20000000Apr 27 02:28:57.140: UBG 65543(1): bitmap 0x00000080, attrib 0x20000000Apr 27 02:28:57.140: CM 001a.c3ff.d59e UBG trace: ubg after CM attrib matchApr 27 02:28:57.140: UBG trace: input queueApr 27 02:28:57.140: UBG 1(4): bitmap 0x0000000F, attrib 0xA0000000Apr 27 02:28:57.140: UBG 2(4): bitmap 0x000000F0, attrib 0xA0000000Apr 27 02:28:57.140: UBG 3(1): bitmap 0x00000004, attrib 0xA0000000Apr 27 02:28:57.140: UBG 4(2): bitmap 0x00000003, attrib 0xA0000000Apr 27 02:28:57.140: UBG 5(1): bitmap 0x00000001, attrib 0xA0000000Apr 27 02:28:57.140: UBG 6(1): bitmap 0x00000002, attrib 0xA0000000Apr 27 02:28:57.140: UBG 7(2): bitmap 0x00000030, attrib 0xA0000000Apr 27 02:28:57.140: UBG 8(1): bitmap 0x00000010, attrib 0xA0000000Apr 27 02:28:57.140: UBG 9(1): bitmap 0x00000020, attrib 0xA0000000Apr 27 02:28:57.140: UBG 65536(1): bitmap 0x00000001, attrib 0x20000000Apr 27 02:28:57.140: UBG 65537(1): bitmap 0x00000002, attrib 0x20000000Apr 27 02:28:57.140: UBG 65538(1): bitmap 0x00000004, attrib 0x20000000Apr 27 02:28:57.140: UBG 65539(1): bitmap 0x00000008, attrib 0x20000000Apr 27 02:28:57.140: UBG 65540(1): bitmap 0x00000010, attrib 0x20000000Apr 27 02:28:57.160: UBG 65543 bg_bitrate 2560001 avail_bitrate 2560000Apr 27 02:28:57.160: UBG 65543 Scale Factor 9 Rank 23040000Apr 27 02:28:57.160: CM 001a.c3ff.d59e Output UBG 7: 0x00000030Apr 27 02:28:57.160: UBG mgmt: UBG 7 SF QueueApr 27 02:28:57.160: CM 001a.c3ff.d59e SF 22debug cable ucc
To debug upstream channel change (UCC) messages generated when CMs request or are assigned a new channel, use the debug cable ucc command in privileged EXEC mode. To disable debugging output, use the no form of this command.
debug cable ucc
no debug cable ucc
Syntax Description
This command has no arguments or keywords.
Command Modes
Privileged EXEC
Command History
Usage Guidelines
This command activates debugging of any upstream channel change (UCC) messages generated when CMs request or are assigned a new channel. When this command is activated, any messages related to upstream channel changes are displayed on the Cisco CMTS console.
Examples
The following is typical output from the debug cable ucc command:
Router# debug cable uccRouter#SID 2 has been registeredMac Address of CM for UCC00:0E:1D:D8:52:16UCC Message Sent to CMChanging SID 2 from upstream channel 1 to upstream channel 2Related Commands
debug cable ucd
To debug upstream channel descriptor (UCD) messages, use the debug cable ucd command in privileged EXEC mode. To disable debugging output, use the no form of this command.
debug cable ucd
no debug cable ucd
Syntax Description
This command has no arguments or keywords.
Command Modes
Privileged EXEC
Command History
Usage Guidelines
This command activates debugging of any upstream channel descriptor (UCD) messages. UCD messages contain information about upstream channel characteristics and are sent to the CMs on the HFC network. Cable modems that are configured to use enhanced upstream channels use these UCD messages to identify and select an enhanced upstream channel to use. When this command is activated, any messages related to upstream channel descriptors are displayed on the Cisco CMTS console.
Examples
The following is typical output from the debug cable ucd command:
UCD MESSAGE-----------FRAME HEADER
