Table of Contents
Advertisement
Chapter 5
Cisco CMTS Debugging Commands
debug cable registration
Jul 4 14:31:37.475: This TLV is GOOD
Jul 4 14:31:37.475: Found CMTS MIC
Jul 4 14:31:37.475: CMTS Mic: A7 E4 15 6 F9 2F BA 81 FE 22 E4 92 5F 81 D4 BB
Jul 4 14:31:37.475: This TLV is GOOD
Jul 4 14:31:37.475: Found modem ip
Jul 4 14:31:37.475: The modem ip value is 10.200.69.90
Jul 4 14:31:37.475: This TLV is GOOD
Jul 4 14:31:37.475: Found modem capabilities
Jul 4 14:31:37.475: Modem Caps Length is 18
Jul 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 06
Jul 4 14:31:37.475: 0x0010: 01 00
Jul 4 14:31:37.475: Concatenation is on for this CM
Jul 4 14:31:37.475: Unknown capability type 2: Ignored
Jul 4 14:31:37.475: Unknown capability type 3: Ignored
Jul 4 14:31:37.475: Unknown capability type 4: Ignored
Jul 4 14:31:37.475: Unknown capability type 5: Ignored
Jul 4 14:31:37.475: Unknown capability type 6: Ignored
Jul 4 14:31:37.475: This TLV is GOOD
Jul 4 14:31:37.475: Finished parsing REG Request
Jul 4 14:31:37.475: Sec sids obtained for all requested classes of service
Jul 4 14:31:37.475: Performing connection admission control (CAC) for each Sid
Jul 4 14:31:37.475: CAC Status for ClassID:5 is CAC_SUCCESS
Jul 4 14:31:37.475: Building a GOOD REG-RSP
Jul 4 14:31:37.475: Adding Modem Caps to the Response to REG RSP
Jul 4 14:31:37.475: Registration Status: ok (0)
Jul 4 14:31:37.475: ClassId:5 assigned QoS Sid:3
Jul 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 03
Jul 4 14:31:37.475: Adding Modem Caps to Response:
Jul 4 14:31:37.475: 0x0000: 05 03 01 01 01
Jul 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 F9
Jul 4 14:31:37.475: 0x0010: 40 54 00 17 00 00 03 01 07 00 00 03 00 01 07 01
Jul 4 14:31:37.479: 0x0020: 01 05 02 02 00 03 05 03 01 01 01
Jul 4 14:31:37.479: Registration Response Transmitted
The 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/U0
Jun 28 12:17:36.171: Found Network Access TLV
Jun 28 12:17:36.171: Found Class Of Service TLV Block
Jun 28 12:17:36.171: Found Max CPEs TLV
Jun 28 12:17:36.171: Found TFTP Server Provisioned CM Address TLV
Jun 28 12:17:36.171: Found CM-MIC TLV
Jun 28 12:17:36.171: Found CMTS-MIC TLV
Jun 28 12:17:36.171: Found Modem Capabilities TLV
Jun 28 12:17:36.171: Found CM IP Address TLV
Jun 28 12:17:36.171: Computing CMTS-MIC to validate REG-REQ data.
Jun 28 12:17:36.171: CMTS_MIC(rfc2104) failed text + key
Jun 28 12:17:36.171: CMTS_MIC(rfc2104) passed
Jun 28 12:17:36.171: REG-RSP Status : ok (0)
Jun 28 12:17:36.171: Registration Response Transmitted
Cisco Broadband Cable Command Reference Guide
5-65
OL-1581-08
Advertisement
Table of Contents
