|
|
Table Of Contents
debug call rsvp-sync func-trace
debug cable env
To display information about the Cisco uBR7246 universal broadband router 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 env
no debug cable env
Syntax Description
This command has no arguments or keywords.
Command Modes
Privileged EXEC
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 uBR7246 console.
Examples
The following is sample output from the debug cable env command:
Router# debug cable envENVM: ps id=0xFF0, v=0x2050, r=0xC0AB, pstype=1ENVM: ps id=0x2FD0, v=0x2050, r=0x24201, pstype=27ENVM: Sensor 0: a2dref=131, a2dact=31, vref=12219, vact=1552Alpha=8990, temp=27Table 39 describes the significant fields shown in the display.
debug cable err
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 err
no debug cable err
Syntax Description
This command has no arguments or keywords.
Command Modes
Privileged EXEC
Usage Guidelines
This command is used to display unexpected Data-over-Cable Service Interface Specifications (DOCSIS) MAC protocol messages. When the Cisco uBR7246 universal broadband router does not expect to receive a specific MAC message, an error message and hexadecimal dump are printed. Other miscellaneous error conditions may result in output.
Examples
The following is sample output from the debug cable err command:
Router# debug cable errThis is a UCD MessageThis is a MAP MessageThis is a RNG_RSP MessageThis is a REG_RSP MessageThis is a UCC_REQ MessageThis is a BPKM_RSP MessageThis is a TRI_TCD MessageThis is a TRI_TSI MessageThis is a unrecognized MCNS messageERROR:######TICKS PER MSLOT NOT POWER OF 2####debug cable freqhop
To display debug messages for frequency hopping, use the debug cable freqhop command in privileged EXEC mode. To disable debugging output, use the no form of this command.
debug cable freqhop
no debug cable freqhop
Syntax Description
This command has no arguments or keywords.
Defaults
Debugging for frequency hopping is not enabled.
Command Modes
Privileged EXEC
Command History
Examples
The following is sample output from the debug cable freqhop command:
Router# debug cable freqhopCMTS freqhop debugging is onRelated Commands
debug cable hw-spectrum
Displays debug information about spectrum management (frequency agility).
debug 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 this command.
debug cable hw-spectrum
no debug cable hw-spectrum
Syntax Description
This command has no arguments or keywords.
Defaults
Debugging for spectrum management is not enabled.
Command Modes
Privileged EXEC
Command History
12.0
This command was introduced as debug cable specmgmt.
12.0(4)XI
This command was renamed as debug cable hw-spectrum.
Examples
The following is sample output from the debug cable hw-spectrum command:
Router# debug cable hw-spectrumCMTS specmgmt debugging is ondebug cable interface
To perform debugging on a specified 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 interface-type interface-number [mac-address address | mask | verbose]
no debug cable interface interface-type interface-number mac-address address
Syntax Description
Command Modes
Privileged EXEC
Command History
Usage Guidelines
You can repeat this debug command for other interfaces. Each time you specify a different cable interface or MAC address, debugging is turned on for this cable interface or MAC address.
If you enter two debug commands with the same interface or MAC address, but with different mask or verbose keywords, the router treats both commands as the same. In this case, the latest debug information supersedes the previous debugging information.
Examples
The following example demonstrates how to enable debugging on interface c3/0:
Router# debug cable interface c3/0The following example demonstrates how to enable detailed debugging on interface c3/0:
Router# debug cable interface c3/0 verboseThe following example demonstrates how to enable debugging on interface c3/0 for all traffic coming from modems with MAC addresses 0010.00xx.xxxx:
Router# debug cable interface c3/0 mac-address 0010.0000.0000 ffff.ff00.0000Related Commands
Enables debugging on traffic from modems with the specified MAC address or MAC address range.
debug cable keyman
To activate debugging of traffic encryption key (TEK) and key-encrypting key (KEK) baseline privacy key activity, use the debug cable keyman command in privileged EXEC mode. To disable debugging output, use the no form of this command.
debug cable keyman
no debug cable keyman
Syntax Description
This command has no arguments or keywords.
Command Modes
Privileged EXEC
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 will be displayed on the Cisco uBR7246 console. This command is used to display encryption key management debugging output.
Examples
The following is sample output from the debug cable keyman command:
Router# debug cable keymanRead Verify DES failed with SID %2xVerify key failed with SID %2x : setvalue = %llx, readback = %llxVerify iv failed with SID %2x : setvalue = %llx, readback = %llxNext TEK lifetime check is set to %u seconds.Next Multicast TEK lifetime check is set to 1 seconds[UCAST_TEK] :", idbp->hw_namestring);show_sid_key_chain(ds, &ds->mcast_sid_key_list_hdr);[MCAST_TEK] :", idbp->hw_namestring);buginf("\nSID : %4x\t", sidkey->sid);buginf("seq : %2x\t current : %2x\n", sidkey->key_seq_num,sidkey->current_key_num);buginf(" Status[0] : %x\tDES IV[0] : %llx\tKey Life[0]: %u sec\n",sidkey->key_status[0], sidkey->des_key[0].iv,compute_remain_lifetime(&sidkey->des_key[0]));buginf(" Status[1] : %x\tDES IV[1] : %llx\tKey Life[1]: %u sec\n",sidkey->key_status[1], sidkey->des_key2131].iv,compute_remain_lifetime(&sidkey->des_key[1]));debug cable mac
To display MAC-layer information for the specified cable modem, use the debug cable mac command in privileged EXEC mode. To disable debugging output, use the no form of this command.
debug cable mac
no debug cable mac
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 modems on your network. The Cisco uBR7246 universal broadband router will become flooded with console printouts.
Examples
The following example shows the return for the MAC layer:
Router# debug cable mac19: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/U0Table 40 describes the significant fields shown in the display.
Related Commands
show controllers cable
Displays interface controller information for the specified slot.
debug cable mac-address
To enable debugging for a specified MAC address, use the debug cable mac-address command in privileged EXEC mode. To turn off debugging output, use the no form of this command.
debug cable mac-address address [mask | verbose]
no debug cable mac-address address
Syntax Description
address
Specifies the MAC address of the interface.
mask
(Optional) Specifies the MAC address validation address.
verbose
(Optional) Displays detailed debug information.
Command Modes
Privileged EXEC
Command History
Usage Guidelines
You can repeat this debug command for other MAC addresses. Each time you specify a different MAC address, debugging is turned on for this MAC address.
If you enter two debug commands with the same MAC address, but with different mask or verbose keywords, the router treats both commands as the same. In this case, the latest debug information supersedes the previous debugging information.
Examples
The following example demonstrates how to enable debugging for all traffic coming from all interfaces of modems with the MAC address 0010.00xx.xxxx:
Router# debug cable mac-address 0010.0000 ffff.ff00.000Related Commands
debug cable map
To display map debugging messages, use the debug cable map command in privileged EXEC mode. To disable debugging output, use the no form of this command.
debug cable map
no debug cable map
Syntax Description
This command has no arguments or keywords.
Command Modes
Privileged EXEC
Command History
Examples
The following example displays all the 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 223A sample Map without any data grant------------------ 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:40A sample Map with data grant(s)------------------ 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 41 describes the significant fields shown in the display.
Related Commands
show controllers cable
Displays interface controller information for the specified slot.
debug cable-modem bpkm
To debug baseline privacy information, use the debug cable-modem bpkm command in privileged EXEC mode. To disable debugging output, use the no form of this command.
debug cable-modem bpkm {errors | events | packets}
no debug cable-modem bpkm {errors | events | packets}
Syntax Description
Command Modes
Privileged EXEC
Command History
11.3 NA
This command was introduced for the Cisco uBR900 series cable access router.
Usage Guidelines
Baseline privacy key management exchanges take place only when both the Cisco uBR900 series and the cable modem termination system (CMTS) are running code images that support baseline privacy, and the privacy class of service is enabled via the configuration file that is downloaded to the cable modem. Baseline privacy code images for the Cisco uBR900 series contain "k1" in the code image name.
Examples
The following is sample output from the debug cable-modem bpkm errors command when the headend does not have privacy enabled:
Router# debug cable-modem bpkm errorscm_bpkm_fsm(): machine: KEK, event/state: EVENT_4_TIMEOUT/STATE_B_AUTH_WAIT, new state: STATE_B_AUTH_WAITcm_bpkm_fsm(): machine: KEK, event/state: EVENT_4_TIMEOUT/STATE_B_AUTH_WAIT, new state: STATE_B_AUTH_WAIT%LINEPROTO-5-UPDOWN: Line protocol on Interface cable-modem0, changed state to downcm_bpkm_fsm(): machine: KEK, event/state: EVENT_1_PROVISIONED/STATE_A_START, new state: STATE_B_AUTH_WAIT%LINEPROTO-5-UPDOWN: Line protocol on Interface cable-modem0, changed state to upRelated Commands
debug cable-modem bridge
To debug bridge filter processing information, use the debug cable-modem bridge command in privileged EXEC mode. To disable debugging output, use the no form of this command.
debug cable-modem bridge
no debug cable-modem bridge
Syntax Description
This command has no arguments or keywords.
Command Modes
Privileged EXEC
Command History
11.3 NA
This command was introduced for the Cisco uBR900 series cable access router.
Usage Guidelines
When the interface is down, all bridge table entries learned on the Ethernet interface are set to discard because traffic is not bridged until the cable interface has completed initialization. After the interface (the line protocol) is completely up, bridge table entries learned on the Ethernet interface program the cable MAC data filters. The cable MAC hardware filters out any received packets whose addresses are not in the filters. In this way, the cable interface only receives packets addressed to its own MAC address or an address it has learned on the Ethernet interface.
Examples
The following example is sample output from the debug cable-modem bridge command:
Router# debug cable-modem bridge%LINEPROTO-5-UPDOWN: Line protocol on Interface cable-modem0, changed state to downshutcm_tbridge_add_entry(): MAC not initialized, discarding entry: 00e0.fe7a.186fno shutcm_tbridge_add_entry(): MAC not initialized, discarding entry: 00e0.fe7a.186f%LINEPROTO-5-UPDOWN: Line protocol on Interface cable-modem0, changed state to upcm_tbridge_add_entry(): Adding entry 00e0.fe7a.186f to filter 2Related Commands
debug cable-modem driver
To enable debugging on the WAN interface card (WIC) and the high-speed WAN interface card (HWIC) driver, use the debug cable-modem driver command in privileged EXEC mode. To disable debugging output, use the no form of this command.
debug cable-modem driver [detail | error]
no debug cable-modem driver [detail | error]
Syntax Description
detail
(Optional) Provides additional detailed debugging information.
error
(Optional) debugs driver error paths.
Command Default
This command is disabled by default.
Command Modes
Privileged EXEC
Command History
Usage Guidelines
You can debug error messages by enabling debugging to provide detailed information.
You can enable or disable debugging by using the debug condition interface cable-modem port command. If a condition interface is enabled for one port, debugging is disabled for the remaining ports.
Examples
The following example shows how to turn cable-modem (CM) driver debugging on:
Router# debug cable-modem driverCM driver debugging is onRelated Commands
debug condition interface cable-modem port
Enables debugging messages for additional interfaces.
debug cable-modem error
To enable debugging messages for the cable interface driver, use the debug cable-modem error command in privileged EXEC mode. To disable debugging output, use the no form of this command.
debug cable-modem error
no debug cable-modem error
Syntax Description
This command has no arguments or keywords.
Command Modes
Privileged EXEC
Command History
Usage Guidelines
This command displays detailed output about the sanity checking of received frame formats, the acquisition of downstream QAM/forward error correction (FEC) lock, the receipt or nonreceipt of SYNC messages from the cable modem termination system (CMTS), reception errors, and bandwidth request failures.
Examples
The following is sample output from the debug cable-modem error command:
Router# debug cable-modem error*Mar 7 20:16:29: AcquireSync(): Update rate is 100 Hz*Mar 7 20:16:30: 1st Sync acquired after 1100 ms.*Mar 7 20:16:30: Recovery loop is locked (7/9)*Mar 7 20:16:30: 2nd Sync acquired after 100 ms.*Mar 7 20:16:30: Recovery loop is locked (10/15)Related Commands
debug cable-modem interrupts
To debug cable modem interrupts, use the debug cable-modem interrupts command in privileged EXEC mode. To disable debugging output, use the no form of this command.
debug cable-modem interrupts
no debug cable-modem interrupts
Syntax Description
This command has no arguments or keywords.
Command Modes
Privileged EXEC
Command History
Examples
The following is sample output from the debug cable-modem interrupts command for Cisco uBR900 series interrupts:
Router# debug cable-modem interrupts*** BCM3300_rx_mac_msg_interrupt ****** BCM3300_rx_mac_msg_interrupt ***### BCM3300_tx_interrupt ###*** BCM3300_rx_mac_msg_interrupt ***### BCM3300_tx_interrupt ###*** BCM3300_rx_mac_msg_interrupt ***### BCM3300_tx_interrupt ###### BCM3300_tx_interrupt ###### BCM3300_tx_interrupt ###### BCM3300_tx_interrupt ###Related Commands
debug cable-modem mac
To troubleshoot the MAC layer for cable modems, use the debug cable-modem mac command in privileged EXEC mode. To disable debugging output, use the no form of this command.
debug cable-modem mac {log [verbose] | messages}
no debug cable-modem mac {log [verbose] | messages}
Syntax Description
log
Displays the real-time MAC log.
verbose
(Optional) Displays periodic MAC-layer events, such as ranging.
messages
Displays MAC layer management messages.
Command Modes
Privileged EXEC
Command History
Usage Guidelines
Of all the available debug cable-modem commands, the most useful is debug cable-modem mac log.
MAC log messages are written to a circular log file even when debugging is not turned on. These messages include time stamps, events, and information pertinent to these events. Enter the debug cable-modem mac log command to view MAC log messages. If you want to view this information without entering debug mode, enter the show controllers cable-modem number mac log command. The same information is displayed by both commands.
If the Cisco uBR900 series interface fails to come up or resets periodically, the MAC log will show what happened. For example, if an address is not obtained from the Dynamic Host Configuration Protocol (DHCP) server, an error is logged, initialization starts over, and the Cisco uBR900 series cable access server router scans for a downstream frequency. The debug cable-modem mac log command displays the log from the oldest to the newest entry.
After initial ranging is successful (dhcp_state has been reached), further RNG-REQ/RNG-RSP messages and watchdog timer entries are suppressed from output unless the verbose keyword is used. Note that
CMAC_LOG_WATCHDOG_TIMERentries while in the maintenance_state are normal when the verbose keyword is used.Examples
The following example is sample output from the debug cable-modem mac log command. The fields of the output are the time since bootup, the log message, and in some cases a parameter that gives more detail about the log entry.
Router# debug cable-modem mac log*Mar 7 01:42:59: 528302.040 CMAC_LOG_LINK_DOWN*Mar 7 01:42:59: 528302.042 CMAC_LOG_RESET_FROM_DRIVER*Mar 7 01:42:59: 528302.044 CMAC_LOG_STATE_CHANGE wait_for_link_up_state*Mar 7 01:42:59: 528302.046 CMAC_LOG_DRIVER_INIT_IDB_SHUTDOWN 0x08098D02*Mar 7 01:42:59: 528302.048 CMAC_LOG_LINK_DOWN*Mar 7 01:43:05: 528308.428 CMAC_LOG_DRIVER_INIT_IDB_RESET 0x08098E5E*Mar 7 01:43:05: 528308.432 CMAC_LOG_LINK_DOWN*Mar 7 01:43:05: 528308.434 CMAC_LOG_LINK_UP*Mar 7 01:43:05: 528308.436 CMAC_LOG_STATE_CHANGE ds_channel_scanning_state*Mar 7 01:43:05: 528308.440 CMAC_LOG_WILL_SEARCH_DS_FREQUENCY_BAND 88/453000000/855000000/6000000*Mar 7 01:43:05: 528308.444 CMAC_LOG_WILL_SEARCH_DS_FREQUENCY_BAND 89/93000000/105000000/6000000*Mar 7 01:43:05: 528308.448 CMAC_LOG_WILL_SEARCH_DS_FREQUENCY_BAND 90/111250000/117250000/6000000*Mar 7 01:43:05: 528308.452 CMAC_LOG_WILL_SEARCH_DS_FREQUENCY_BAND 91/231012500/327012500/6000000*Mar 7 01:43:05: 528308.456 CMAC_LOG_WILL_SEARCH_DS_FREQUENCY_BAND 92/333015000/333015000/6000000*Mar 7 01:43:05: 528308.460 CMAC_LOG_WILL_SEARCH_DS_FREQUENCY_BAND 93/339012500/399012500/6000000*Mar 7 01:43:05: 528308.462 CMAC_LOG_WILL_SEARCH_DS_FREQUENCY_BAND 94/405000000/447000000/6000000*Mar 7 01:43:05: 528308.466 CMAC_LOG_WILL_SEARCH_DS_FREQUENCY_BAND 95/123015000/129015000/6000000*Mar 7 01:43:05: 528308.470 CMAC_LOG_WILL_SEARCH_DS_FREQUENCY_BAND 96/135012500/135012500/6000000*Mar 7 01:43:05: 528308.474 CMAC_LOG_WILL_SEARCH_DS_FREQUENCY_BAND 97/141000000/171000000/6000000*Mar 7 01:43:05: 528308.478 CMAC_LOG_WILL_SEARCH_DS_FREQUENCY_BAND 98/219000000/225000000/6000000*Mar 7 01:43:05: 528308.482 CMAC_LOG_WILL_SEARCH_DS_FREQUENCY_BAND 99/177000000/213000000/6000000*Mar 7 01:43:05: 528308.486 CMAC_LOG_WILL_SEARCH_SAVED_DS_FREQUENCY 663000000*Mar 7 01:43:05: 528308.488 CMAC_LOG_WILL_SEARCH_USER_DS_FREQUENCY 663000000*Mar 7 01:43:07: 528310.292 CMAC_LOG_DS_64QAM_LOCK_ACQUIRED 663000000.528383.992 CMAC_LOG_STATE_CHANGE registration_state528384.044 CMAC_LOG_REG_REQ_MSG_QUEUED528384.050 CMAC_LOG_REG_REQ_TRANSMITTED528384.052 CMAC_LOG_REG_RSP_MSG_RCVD528384.078 CMAC_LOG_COS_ASSIGNED_SID 1/4528384.102 CMAC_LOG_RNG_REQ_QUEUED 4528384.102 CMAC_LOG_REGISTRATION_OK528384.102 CMAC_LOG_STATE_CHANGE establish_privacy_state528384.102 CMAC_LOG_STATE_CHANGE maintenance_state528388.444 CMAC_LOG_RNG_REQ_TRANSMITTED528388.444 CMAC_LOG_RNG_RSP_MSG_RCVD528398.514 CMAC_LOG_RNG_REQ_TRANSMITTED528398.516 CMAC_LOG_RNG_RSP_MSG_RCVD528408.584 CMAC_LOG_RNG_REQ_TRANSMITTED528408.586 CMAC_LOG_RNG_RSP_MSG_RCVD528414.102 CMAC_LOG_WATCHDOG_TIMER528418.654 CMAC_LOG_RNG_REQ_TRANSMITTED528418.656 CMAC_LOG_RNG_RSP_MSG_RCVD528428.726 CMAC_LOG_RNG_REQ_TRANSMITTED528428.728 CMAC_LOG_RNG_RSP_MSG_RCVD528438.796 CMAC_LOG_RNG_REQ_TRANSMITTED528438.798 CMAC_LOG_RNG_RSP_MSG_RCVD528444.102 CMAC_LOG_WATCHDOG_TIMER528444.492 CMAC_LOG_LINK_DOWN528444.494 CMAC_LOG_RESET_FROM_DRIVER528444.494 CMAC_LOG_STATE_CHANGE wait_for_link_up_state528444.494 CMAC_LOG_DRIVER_INIT_IDB_SHUTDOWN 0x08098D02528444.494 CMAC_LOG_LINK_DOWN528474.494 CMAC_LOG_WATCHDOG_TIMER528504.494 CMAC_LOG_WATCHDOG_TIMER528534.494 CMAC_LOG_WATCHDOG_TIMER0 events dropped due to lack of a chunkThe line "0 events dropped due to lack of a chunk" at the end of a display indicates that no log entries were discarded due to a temporary lack of memory, which means the log is accurate and reliable.
The following example compares the output of the debug cable-modem mac log command with the debug cable-modem mac log verbose command. The verbose keyword displays periodic events such as ranging.
Router# debug cable-modem mac logCable Modem mac log debugging is onRouter#Router# debug cable-modem mac log verboseCable Modem mac log debugging is on (verbose)Router#574623.810 CMAC_LOG_RNG_REQ_TRANSMITTED574623.812 CMAC_LOG_RNG_RSP_MSG_RCVD574627.942 CMAC_LOG_WATCHDOG_TIMER574633.880 CMAC_LOG_RNG_REQ_TRANSMITTED574633.884 CMAC_LOG_RNG_RSP_MSG_RCVD574643.950 CMAC_LOG_RNG_REQ_TRANSMITTED574643.954 CMAC_LOG_RNG_RSP_MSG_RCVD574654.022 CMAC_LOG_RNG_REQ_TRANSMITTED574654.024 CMAC_LOG_RNG_RSP_MSG_RCVD574657.978 CMAC_LOG_WATCHDOG_TIMER574664.094 CMAC_LOG_RNG_REQ_TRANSMITTED574664.096 CMAC_LOG_RNG_RSP_MSG_RCVD574674.164 CMAC_LOG_RNG_REQ_TRANSMITTED574674.166 CMAC_LOG_RNG_RSP_MSG_RCVDRouter# no debug cable-modem mac log verboseCable Modem mac log debugging is offRouter#574684.234 CMAC_LOG_RNG_REQ_TRANSMITTED574684.238 CMAC_LOG_RNG_RSP_MSG_RCVDThe following is sample output from the debug cable-modem mac messages command. This command causes received cable MAC management messages to be displayed in a verbose format.
Router# debug cable-modem mac messagesdynsrv dynamic service mac messagesmap map messages receivedreg-req reg-req messages transmittedreg-rsp reg-rsp messages receivedrng-req rng-req messages transmittedrng-rsp rng-rsp messages receivedsync Sync messages receiveducc-req ucc-req messages receiveducc-rsp ucc-rsp messages transmitteducd UCD messages received<cr>The dynsrv keyword displays Dynamic Service Add or Dynamic Service Delete messages during the off-hook/on-hook transitions of a phone connected to the Cisco uBR900 series cable access router.
In addition, sent REG-REQ messages are displayed in hexadecimal dump format. The output from this command is very verbose and is usually not needed for normal interface debugging. The command is most useful when attempting to attach a Cisco uBR900 series cable access router to a cable modem termination system (CMTS) that is not Data-over-Cable Service Interface Specifications (DOCSIS)-qualified.
For a description of the displayed fields of each message, refer to the DOCSIS Radio Frequency Interface Specification, v1.0 (SP-RFI-I04-980724).
Router# debug cable mac messages*Mar 7 01:44:06:*Mar 7 01:44:06: UCD MESSAGE*Mar 7 01:44:06: -----------*Mar 7 01:44:06: FRAME HEADER*Mar 7 01:44:06: FC - 0xC2 == MAC Management*Mar 7 01:44:06: MAC_PARM - 0x00*Mar 7 01:44:06: LEN - 0xD3*Mar 7 01:44:06: MAC MANAGEMENT MESSAGE HEADER*Mar 7 01:44:06: DA - 01E0.2F00.0001*Mar 7 01:44:06: SA - 00E0.1EA5.BB60*Mar 7 01:44:06: msg LEN - C1*Mar 7 01:44:06: DSAP - 0*Mar 7 01:44:06: SSAP - 0*Mar 7 01:44:06: control - 03*Mar 7 01:44:06: version - 01*Mar 7 01:44:06: type - 02 == UCD*Mar 7 01:44:06: RSVD - 0*Mar 7 01:44:06: US Channel ID - 1*Mar 7 01:44:06: Configuration Change Count - 4*Mar 7 01:44:06: Mini-Slot Size - 8*Mar 7 01:44:06: DS Channel ID - 1*Mar 7 01:44:06: Symbol Rate - 8*Mar 7 01:44:06: Frequency - 20000000*Mar 7 01:44:06: Preamble Pattern - CC CC CC CC CC CC CC CC CC CC CC CC CC CC 0D 0D*Mar 7 01:44:06: Burst Descriptor 0*Mar 7 01:44:06: Interval Usage Code - 1*Mar 7 01:44:06: Modulation Type - 1 == QPSK*Mar 7 01:44:06: Differential Encoding - 2 == OFF*Mar 7 01:44:06: Preamble Length - 64*Mar 7 01:44:06: Preamble Value Offset - 56*Mar 7 01:44:06: FEC Error Correction - 0*Mar 7 01:44:06: FEC Codeword Info Bytes - 16*Mar 7 01:44:06: Scrambler Seed - 0x0152*Mar 7 01:44:06: Maximum Burst Size - 1*Mar 7 01:44:06: Guard Time Size - 8*Mar 7 01:44:06: Last Codeword Length - 1 == FIXED*Mar 7 01:44:06: Scrambler on/off - 1 == ON*Mar 7 01:44:06: Burst Descriptor 1*Mar 7 01:44:06: Interval Usage Code - 3*Mar 7 01:44:06: Modulation Type - 1 == QPSK*Mar 7 01:44:06: Differential Encoding - 2 == OFF*Mar 7 01:44:06: Preamble Length - 128*Mar 7 01:44:06: Preamble Value Offset - 0*Mar 7 01:44:06: FEC Error Correction - 5*Mar 7 01:44:06: FEC Codeword Info Bytes - 34*Mar 7 01:44:06: Scrambler Seed - 0x0152*Mar 7 01:44:06: Maximum Burst Size - 0*Mar 7 01:44:06: Guard Time Size - 48*Mar 7 01:44:06: Last Codeword Length - 1 == FIXED*Mar 7 01:44:06: Scrambler on/off - 1 == ON*Mar 7 01:44:06: Burst Descriptor 2*Mar 7 01:44:06: Interval Usage Code - 4*Mar 7 01:44:06: Modulation Type - 1 == QPSK*Mar 7 01:44:06: Differential Encoding - 2 == OFF*Mar 7 01:44:06: Preamble Length - 128*Mar 7 01:44:06: Preamble Value Offset - 0*Mar 7 01:44:06: FEC Error Correction - 5*Mar 7 01:44:06: FEC Codeword Info Bytes - 34*Mar 7 01:44:06: Scrambler Seed - 0x0152*Mar 7 01:44:06: Maximum Burst Size - 0*Mar 7 01:44:06: Guard Time Size - 48*Mar 7 01:44:06: Last Codeword Length - 1 == FIXED*Mar 7 01:44:06: Scrambler on/off - 1 == ON*Mar 7 01:44:06: Burst Descriptor 3*Mar 7 01:44:06: Interval Usage Code - 5*Mar 7 01:44:06: Modulation Type - 1 == QPSK*Mar 7 01:44:06: Differential Encoding - 2 == OFF*Mar 7 01:44:06: Preamble Length - 72*Mar 7 01:44:06: Preamble Value Offset - 48*Mar 7 01:44:06: FEC Error Correction - 5*Mar 7 01:44:06: FEC Codeword Info Bytes - 75*Mar 7 01:44:06: Scrambler Seed - 0x0152*Mar 7 01:44:06: Maximum Burst Size - 0*Mar 7 01:44:06: Guard Time Size - 8*Mar 7 01:44:06: Last Codeword Length - 1 == FIXED*Mar 7 01:44:06: Scrambler on/off - 1 == ON*Mar 7 01:44:06:*Mar 7 01:44:06:*Mar 7 01:44:06: MAP MESSAGE*Mar 7 01:44:06: -----------*Mar 7 01:44:06: FRAME HEADER*Mar 7 01:44:06: FC - 0xC3 == MAC Management with Extended Header*Mar 7 01:44:06: MAC_PARM - 0x02*Mar 7 01:44:06: LEN - 0x42*Mar 7 01:44:06: EHDR - 0x00 0x00*Mar 7 01:44:06: MAC MANAGEMENT MESSAGE HEADER*Mar 7 01:44:06: DA - 01E0.2F00.0001.*Mar 7 01:44:17: RNG-RSP MESSAGE*Mar 7 01:44:17: ---------------*Mar 7 01:44:17: FRAME HEADER*Mar 7 01:44:17: FC - 0xC2 == MAC Management*Mar 7 01:44:17: MAC_PARM - 0x00*Mar 7 01:44:17: LEN - 0x2B*Mar 7 01:44:17: MAC MANAGEMENT MESSAGE HEADER*Mar 7 01:44:17: DA - 00F0.1EB2.BB61.*Mar 7 01:44:20: REG-REQ MESSAGE*Mar 7 01:44:20: ---------------*Mar 7 01:44:20: C20000A5 000000E0 1EA5BB60 00F01EB2*Mar 7 01:44:20: BB610093 00000301 06000004 03010104*Mar 7 01:44:20: 1F010101 0204003D 09000304 001E8480*Mar 7 01:44:20: 04010705 04000186 A0060200 0C070101*Mar 7 01:44:20: 080300F0 1E112A01 04000000 0A020400*Mar 7 01:44:20: 00000A03 04000002 58040400 00000105*Mar 7 01:44:20: 04000000 01060400 00025807 04000000*Mar 7 01:44:20: 3C2B0563 6973636F 06105E4F C908C655*Mar 7 01:44:20: 61086FD5 5C9D756F 7B730710 434D5453*Mar 7 01:44:20: 204D4943 202D2D2D 2D2D2D2D 0C040000*Mar 7 01:44:20: 00000503 010100*Mar 7 01:44:20:*Mar 7 01:44:20:*Mar 7 01:44:20: REG-RSP MESSAGE*Mar 7 01:44:20: ---------------*Mar 7 01:44:20: FRAME HEADER*Mar 7 01:44:20: FC - 0xC2 == MAC Management*Mar 7 01:44:20: MAC_PARM - 0x00*Mar 7 01:44:20: LEN - 0x29*Mar 7 01:44:20: MAC MANAGEMENT MESSAGE HEADER*Mar 7 01:44:20: DA - 00F0.1EB2.BB61Related Commands
debug cable-modem map
To display the timing from MAP messages to synchronized messages and the timing between MAP messages on a Cisco uBR900 series cable access router, use the debug cable-modem map command in privileged EXEC mode. To disable debugging output, use the no form of this command.
debug cable-modem map
no debug cable-modem map
Syntax Description
This command has no arguments or keywords.
Command Modes
Privileged EXEC
Command History
Examples
The following is sample output from the debug cable-modem map command:
Router# debug cable-modem mapCable Modem MAP debugging is onRouter#*Mar 7 20:12:08: 595322.942: Min MAP to sync=72*Mar 7 20:12:08: 595322.944: Max map to map time is 40*Mar 7 20:12:08: 595322.982: Min MAP to sync=63*Mar 7 20:12:08: 595323.110: Max map to map time is 41*Mar 7 20:12:08: 595323.262: Min MAP to sync=59*Mar 7 20:12:08: 595323.440: Max map to map time is 46*Mar 7 20:12:09: 595323.872: Min MAP to sync=58Related Commands
debug cable-modem rbcp
To activate debugging on the modem router blade control port (RBCP) code, use the debug cable-modem rbcp command in privileged EXEC mode. To disable debugging output, use the no form of this command.
debug cable-modem rbcp {events | messages | states}
Syntax Description
Command Default
This command is disabled by default.
Command Modes
Privileged EXEC
Command History
Usage Guidelines
When no keyword is selected, the debug cable-modem rbcp command enables miscellaneous RBCP debugging.
When the messages keyword is enabled, a debug message is generated for every RBCP request and response.
Cisco IOS software RBCP support also contains its own debug facility with the debug scp data and debug scp packets commands.
Debugging can be also be enabled or disabled using the debug condition interface cable-modem port command. If debugging is enabled for one port, debugging is disabled for the remaining ports.
Examples
Router# debug cable-modem rbcp messagesCM rbcp messages debugging is onRelated Commands
debug cable-modem startup
To enable modem initialization code debugging, use the debug cable-modem startup command in privileged EXEC mode. To disable debugging output, use the no form of this command.
debug cable-modem startup
no debug cable-modem startup
Syntax Description
This command has no arguments or keywords.
Command Default
This command is disabled by default.
Command Modes
Privileged EXEC
Command History
Usage Guidelines
Debugging can also be enabled or disabled using the debug condition interface cable-modem port command. If debugging is enabled for one port, debugging is disabled for the remaining ports.
Examples
The following example shows that cable-modem (CM) startup debugging is turned on:
Router# debug cable-modem startupCM startup debugging is onRelated Commands
debug condition interface cable-modem port
Enables debugging messages for additional interfaces.
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 this command.
debug cable phy
no debug cable phy
Syntax Description
This command has no arguments or keywords.
Command Modes
Privileged EXEC
Usage Guidelines
This command activates debugging of messages generated in the cable physical sublayer (PHY), which is where upstream and downstream activity between the Cisco uBR7246 router and the hybrid fiber-coaxial (HFC) network is controlled. When this command is activated, any messages generated in the cable PHY will be displayed on the Cisco uBR7246 console.
Examples
The following is sample output from the debug cable phy command:
Router# debug cable phycmts_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 this command.
debug cable privacy
no debug cable privacy
Syntax Description
This command has no arguments or keywords.
Command Modes
Privileged EXEC
Usage Guidelines
This command activates debugging of baseline privacy. When this command is activated, any messages generated by the spectrum manager will be displayed on the Cisco uBR7246 console.
Examples
The following is sample output from the debug cable privacy command:
Router# debug cable privacyRemoving both odd and even keys for sid %x.Invalid Len for TLV_SERIAL_NUM_TYPE : %d.Invalid Len for TLV_MANUF_ID_TYPE : %d.Invalid Len for TLV_MANUF_ID_TYPE : %d.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
Usage Guidelines
This command activates debugging of QoS. When this command is activated, any messages related to QoS parameters will be displayed on the Cisco uBR7246 console.
Examples
The following is sample output from the debug cable qos command:
Router# debug cable qosCMTS_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 cable modems on the hybrid fiber-coaxial (HFC) network, use the debug cable range command in privileged EXEC mode. To disable debugging output, use the no form of this command.
debug cable range
no debug cable range
Syntax Description
This command has no arguments or keywords.
Command Modes
Privileged EXEC
Usage Guidelines
This command activates debugging of ranging messages from cable modems on the hybrid fiber-coaxial (HFC) network. When this command is activated, any ranging messages generated when cable modems request or change their upstream frequencies will be displayed on the Cisco uBR7246 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 is sample output from the debug cable range command when a modem first seeks to establish a link to the Cisco uBR7246 universal broadband router:
Router# debug cable rangeGot 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 SID value of 0 indicates that the modem has no assigned service identifier. The "CM mac address" is the MAC address of the radio frequency (RF) interface of the modem, not its Ethernet interface. The "Timing offset" is a measure of the distance between the modem and the Cisco uBR7246 universal broadband router 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.
The following is sample output when the modem is first assigned a SID during initial maintenance:
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 sample output when the modem is reassigned the same 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 sample output when the modem is polled by the Cisco uBR7246 universal broadband router during station maintenance. Polling happens at a minimum rate of once every 10 seconds.
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/U0debug cable reset
To display reset messages from cable interfaces, 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
Usage Guidelines
This command activates display of reset messages from cable interfaces.
Examples
The following is sample output from the debug cable reset command when the interface is reset due to complete loss of receive packets:
Router# debug cable resetResetting CMTS interface.debug cable specmgmt
To debug spectrum management (frequency agility) on the hybrid fiber-coaxial (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
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 uBR7246 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 is sample output from the debug cable specmgmt command:
Router# debug cable specmgmtcmts_next_frequency(0x60A979AC, 1, 1)The following is sample output when the frequency hop was commanded:
add_interface_to_freq(0x60BD3734, 0x60C44F68)The following is sample output when the interface was added to the interface list of a frequency:
set_upstream(0x60A979AC,1,21000000,-5)The following is sample output when the spectrum management has set the frequency and power level of an upstream port:
cmts_frequency_hop_decision(0x60B57FEC)debug cable startalloc
To debug channel allocations on the hybrid fiber-coaxial (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
Usage Guidelines
This command activates debugging of any channel allocations on the HFC network. When this command is activated, any messages generated when channels are allocated to cable modems on the HFC network will be displayed on the Cisco uBR7246 console.
Examples
The following is sample output from the debug cable startalloc command:
Router# debug cable startallocMAP startalloc adjusted by <n> mslotsThis output indicates time-slot Manufacturing Automation Protocol (MAP) processing is active.
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.
Defaults
Debugging for Telco return events is not enabled.
Command Modes
Privileged EXEC
Command History
Examples
The following is sample output from the debug cable telco-return command:
Router# debug cable telco-returnCMTS telco-return debugging is onRelated Commands
Debugs upstream channel change messages generated when cable modems request or are assigned a new channel.
debug cable ucc
To debug upstream channel change (UCC) messages generated when cable modems 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
Usage Guidelines
This command activates debugging of any UCC messages generated when cable modems request or are assigned a new channel. When this command is activated, any messages related to upstream channel changes will be displayed on the Cisco uBR7246 console.
Examples
The following is sample output from the debug cable ucc command when moving a modem from one upstream channel to another:
Router# debug cable uccSID 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 2debug 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
Usage Guidelines
This command activates debugging of any UCD messages. UCD messages contain information about upstream channel characteristics and are sent to the cable modems on the hybrid fiber-coaxial (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 will be displayed on the Cisco uBR7246 console.
Examples
The following is sample output from the debug cable ucd command:
Router# debug cable ucdUCD MESSAGE-----------FRAME HEADERFC - 0xC2 ==MAC_PARM - 0x00LEN - 0xD3MAC MANAGEMENT MESSAGE HEADERDA - 01E0.2F00.0001SA - 0009.0CEF.3730msg LEN - C1DSAP - 0SSAP t - 0control - 03version - 01type - 02 ==US Channel ID - 1Configuration Change Count - 5Mini-Slot Size - 4DS Channel ID - 1Symbol Rate - 8Frequency - 10000000Preamble Pattern - CC CC CC CC CC CC CC CC CC CC CC CC CCCC 0D 0DBurst Descriptor 0Interval Usage Code - 1Modulation Type - 1 == QPSKDifferential Encoding - 2 == OFFPreamble Length - 64Preamble Value Offset - 56FEC Error Correction - 0FEC Codeword Length - 16Scrambler Seed - 0x0152Maximum Burst Size - 2Guard Time Size - 8Last Codeword Length - 1 == FIXEDScrambler on/off - 1 == ONBurst Descriptor 1Interval Usage Code - 3Modulation Type - 1 == QPSKDifferential Encoding - 2 == OFFPreamble Length - 128Preamble Value Offset - 0FEC Error Correction - 5FEC Codeword Length - 34Scrambler Seed - 0x0152Maximum Burst Size - 0Guard Time Size - 48Last Codeword Length - 1 == FIXEDScrambler on/off - 1 == ONBurst Descriptor 2Interval Usage Code - 4Modulation Type - 1 == QPSKDifferential Encoding - 2 == OFFPreamble Length - 128Preamble Value Offset - 0FEC Error Correction - 5FEC Codeword Length - 34Scrambler Seed - 0x0152Maximum Burst Size - 0Guard Time Size - 48Last Codeword Length - 1 == FIXEDScrambler on/off - 1 == ONBurst Descriptor 3Interval Usage Code - 5Modulation Type - 1 == QPSKDifferential Encoding - 2 == OFFPreamble Length - 72Preamble Value Offset - 48FEC Error Correction - 5FEC Codeword Length - 75Scrambler Seed - 0x0152Maximum Burst Size - 0Guard Time Size - 8Last Codeword Length - 1 == FIXEDScrambler on/off - 1 == ONThe UCD MESSAGE is :0xC2 0x00 0x00 0xD3 0x00 0x00 0x01 0xE00x2F 0x00 0x00 0x01 0x00 0x09 0x0C 0xEF0x37 0x30 0x00 0xC1 0x00 0x00 0x03 0x010x02 0x00 0x01 0x05 0x04 0x01 0x01 0x010x08 0x02 0x04 0x00 0x98 0x96 0x80 0x030x10 0xCC 0xCC 0xCC 0xCC 0xCC 0xCC 0xCC0xCC 0xCC 0xCC 0xCC 0xCC 0xCC 0xCC 0x0D0x0D 0x04 0x25 0x01 0x01 0x01 0x01 0x020x01 0x02 0x03 0x02 0x00 0x40 0x04 0x020x00 0x38 0x05 0x01 0x00 0x06 0x01 0x100x07 0x02 0x01 0x52 0x08 0x01 0x02 0x090x01 0x08 0x0A 0x01 0x01 0x0B 0x01 0x010x04 0x25 0x03 0x01 0x01 0x01 0x02 0x010x02 0x03 0x02 0x00 0x80 0x04 0x02 0x000x00 0x05 0x01 0x05 0x06 0x01 0x22 0x070x02 0x01 0x52 0x08 0x01 0x00 0x09 0x010x30 0x0A 0x01 0x01 0x0B 0x01 0x01 0x040x25 0x04 0x01 0x01 0x01 0x02 0x01 0x020x03 0x02 0x00 0x80 0x04 0x02 0x00 0x000x05 0x01 0x05 0x06 0x01 0x22 0x07 0x020x01 0x52 0x08 0x01 0x00 0x09 0x01 0x300x0A 0x01 0x01 0x0B 0x01 0x01 0x04 0x250x05 0x01 0x01 0x01 0x02 0x01 0x02 0x030x02 0x00 0x48 0x04 0x02 0x00 0x30 0x050x01 0x05 0x06 0x01 0x4B 0x07 0x02 0x010x52 0x08 0x01 0x00 0x09 0x01 0x08 0x0A0x01 0x01 0x0B 0x01 0x01debug callback
To display callback events when the router is using a modem and a chat script to call back on a terminal line, use the debug callback command in privileged EXEC mode. To disable debugging output, use the no form of this command.
debug callback
no debug callback
Syntax Description
This command has no arguments or keywords.
Command Modes
Privileged EXEC
Usage Guidelines
This command is useful for debugging chat scripts on PPP and AppleTalk Remote Access Protocol (ARAP) lines that use callback mechanisms. The output provided by the debug callback command shows you how the call is progressing when used with the debug ppp or debug arap commands.
Examples
The following is sample output from the debug callback command:
Router# debug callbackTTY7 Callback process initiated, user: exec_test dialstring 123456TTY7 Callback forced wait = 4 secondsTTY7 Exec Callback Successful - await exec/autoselect pickupTTY7: Callback in effectRelated Commands
Displays ARAP events.
debug ppp
Displays information on traffic and exchanges in an internetwork implementing the PPP.
debug call fallback detail
To display details of the call fallback, use the debug call fallback detail command in privileged EXEC mode. To disable debugging output, use the no form of this command.
debug call fallback detail
no debug call fallback detail
Syntax Description
This command has no arguments or keywords.
Defaults
Disabled
Command Modes
Privileged EXEC
Command History
Usage Guidelines
Every time a call request is received, the debug call fallback detail command displays in the command-line interface (CLI) cache lookup and call acceptance/rejection information. Use this command to monitor call requests as they enter the call fallback subsystem.
If you have a large amount of calls in your router, enabling this command can cause delays in your routing functions as the debug statistics are constantly compiled and sent to your terminal. Also, debug messages on your terminal may make for difficult CLI configuring.
Examples
The following example depicts a call coming in to 10.1.1.4 with codec g729r8. Because there is no cache entry for this destination, a probe is sent and values are inserted into the cache. A lookup is performed again, entry is found, and a fallback decision is made to admit the call.
Router# debug call fallback detailWhen cache is empty:debug call fallback detail:2d19h:fb_lookup_cache:10.1.1.4, codec:g729r82d19h:fb_lookup_cache:No entry found.2d19h:fb_check:no entry exists, enqueueing probe info... 10.1.1.4, codec:g729r82d19h:fb_main:Got FB_APP_INQ event2d19h:fb_main:Dequeued prob info: 10.1.1.4, codec:g729r82d19h:fb_lookup_cache:10.1.1.4, codec:g729r82d19h:fb_lookup_cache:No entry found.2d19h:fb_cache_insert:insert:10.1.1.4, codec:g729r82d19h:fb_cache_insert:returning entry:10.1.1.4, codec:g729r82d19h:fb_initiate_probe:Creating probe... 10.1.1.4, codec:g729r82d19h:fb_initiate_probe:Created and started on probe #13, 10.1.1.4, codec:g729r82d19h:fb_lookup_cache:10.1.1.4, codec:g729r82d19h:fb_lookup_cache:Found entry.2d19h:fb_check:returned FB_CHECK_TRUE, 10.1.1.4, codec:g729r82d19h:fb_main:calling callback function with:TRUEThe following example depicts a call coming in to 10.1.1.4 with codec g729r8. A lookup is performed, entry is found, and a fallback decision is made to admit the call.
Router# debug call fallback detailWhen cache is full:2d19h:fb_lookup_cache:10.1.1.4, codec:g729r82d19h:fb_lookup_cache:Found entry.2d19h:fb_check:returned FB_CHECK_TRUE, 10.1.1.4, codec:g729r82d19h:fb_main:calling callback function with:TRUEdebug call fallback probe
To display details of the call fallback probes, use the debug call fallback probe command in privileged EXEC mode. To disable debugging output, use the no form of this command.
debug call fallback probe
no debug call fallback probe
Syntax Description
This command has no arguments or keywords.
Defaults
Disabled
Command Modes
Privileged EXEC
Command History
Usage Guidelines
Every time a probe is received, the debug call fallback probe command displays in the command-line interface (CLI) network traffic information collected by the probe. Use this command to monitor the network traffic information the probes carry as they enter the call fallback subsystem and log cache entries.
If you have frequent return of probes to your router, enabling this command can cause delays in your routing functions as the debug statistics are constantly compiled and sent to your terminal. Also, debug messages on your terminal may make for difficult CLI configuring.
Examples
The following example depicts a call coming in to 10.1.1.4 and codec type g729r8. Because there is no cache entry for this IP address, a g729r8 probe is initiated. The probe consists of 20 packet returns with an average delay of 43 milliseconds. The "jitter out" is jitter from source to destination router and "jitter in" is jitter from destination to source router. The delay, loss, and Calculated Planning Impairment Factor (ICPIF) values following g113_calc_icpif are the instantaneous values, whereas those values following "New smoothed values" are the values after applying the smoothing with weight 65.
Router# debug call fallback probe2d19h:fb_initiate_probe:Probe payload is 322d19h:fb_main:NumOfRTT=20, RTTSum=120, loss=0, delay=43, jitter in=0, jitter out=0-> 10.1.1.4, codec:g729r82d19h:g113_calc_icpif(delay (w/codec delay)=43, loss=0, expect_factor=10) Icpif=02d19h:fb_main:Probe timer expired, 10.1.1.4, codec:g729r82d19h:fb_main:NumOfRTT=20, RTTSum=120, loss=0, delay=43, jitter in=0, jitter out=0-> 10.1.1.4, codec:g729r82d19h:g113_calc_icpif(delay (w/codec delay)=43, loss=0, expect_factor=10) Icpif=02d19h:fb_main:New smoothed values:inst_weight=65, ICPIF=0, Delay=43, Loss=0 -> 10.1.1.4, codec:g729r8debug call filter detail
To display details of the debug trace inside the generic call filter module (GCFM), use the debug call filter detail command in privileged EXEC mode. To disable debugging output, use the no form of this command.
debug call filter detail
no debug call filter detail
Syntax Description
This command has no arguments or keywords.
Defaults
No default behavior or values
Command Modes
Privileged EXEC
Command History
Examples
The following sample output from the debug call filter detail command shows the detailed activity of the GCFM, which is the internal module that controls the debug filtering.
Router# debug call filter detail5d18h: gcfm_call_get_hash_address: hashtable index = 3455d18h: gcfm_call_search_hash:no found5d18h: gcfm_init_call_record:5d18h: gcfm_init_percall_matchlist:5d18h: === list 1: service_state=2, callp's: 05d18h: gcfm_call_get_hash_address: hashtable index = 3455d18h: gcfm_call_enlist: count before this enlist 0 on 624D60005d18h: gcfm_call_enlist: tail is empty guid=C2E4C789-214A-11D4-804C-000A8A389BA85d18h: gcfm_call_get_hash_address: hashtable index = 3455d18h: gcfm_call_search_hash: search requested guid=C2E4C789-214A-11D4-804C-000A8A389BA8 vs the entry guid=C2E4C789-214A-11D4-804C-000A8A389BA85d18h: gcfm_call_search_hash: found5d18h: gcfm_update_percall_condlist_context:5d18h: gcfm_update_percall_condlist_context: check cond = 25d18h: gcfm_copy_match_cond:5d18h: gcfm_update_cond_through_matchlist:5d18h: gcfm_check_percond_with_matchlist: check match-list 15d18h: gcfm_matchlist_percond_check:5d18h: gcfm_matchlist_percond_check: check cond=25d18h: gcfm_matchlist_percond_check: compare 42300 to configured 423005d18h: gcfm_check_cond_tel_number:5d18h: gcfm_check_cond_tel_number: matched5d18h: gcfm_matchlist_percond_check: checked result is 15d18h: gcfm_is_bitfield_identical:5d18h: gcfm_update_cond_through_matchlist: service=1, percallmatchlist tag=1,current_status = 1, service_filter=05d18h: gcfm_percall_notify_condition: not linked call recordTable 42 describes the significant fields shown in the display.
Related Commands
debug call filter inout
To display the debug trace inside the generic call filter module (GCFM), use the debug call filter inout command in privileged EXEC mode. To disable debugging output, use the no form of this command.
debug call filter inout
no debug call filter inout
Syntax Description
This command has no arguments or keywords.
Defaults
No default behavior or values
Command Modes
Privileged EXEC
Command History
Examples
The following sample output from the debug call filter inout command shows the incoming and outgoing activity of the GCFM, which is the internal module that controls the debug filtering.
Router# debug call filter inout5d18h: gcfm_generate_guid: component ISDN gets guid5d18h: gcfm_percall_register: component ISDN5d18h: gcfm_percall_register: component ISDN return selected=05d18h: gcfm_percall_notify_condition: component ISDN for sync=15d18h: gcfm_percall_notify_condition: component ISDN successfully selected = 05d18h: gcfm_check_percall_status: component TGRM5d18h: gcfm_check_percall_status: component TGRM return selected=05d18h: gcfm_check_percall_status: component TGRM5d18h: gcfm_check_percall_status: component TGRM return selected=05d18h: gcfm_percall_register: component VTSP5d18h: gcfm_percall_register: component VTSP for return selected value 05d18h: gcfm_percall_notify_condition: component VTSP for sync=15d18h: gcfm_percall_notify_condition: component VTSP successfully selected = 05d18h: gcfm_percall_register: component CCAPI5d18h: gcfm_percall_register: component CCAPI for return selected value 05d18h: gcfm_check_percall_status: component NUMBER-TRANSLATION5d18h: gcfm_check_percall_status: component NUMBER-TRANSLATION return selected=05d18h: gcfm_percall_register: component VOICE-IVR-V25d18h: gcfm_percall_register: component VOICE-IVR-V2 for return selected value 05d18h: gcfm_check_percall_status: component NUMBER-TRANSLATION5d18h: gcfm_check_percall_status: component NUMBER-TRANSLATION5d18h: gcfm_check_percall_status: component DIAL-PEER5d18h: gcfm_check_percall_status: component DIAL-PEER return selected=05d18h: gcfm_check_percall_status: component NUMBER-TRANSLATION5d18h: gcfm_check_percall_status: component DIAL-PEER5d18h: gcfm_check_percall_status: component DIAL-PEER return selected=05d18h: gcfm_check_percall_status: component NUMBER-TRANSLATION5d18h: gcfm_check_percall_status: component DIAL-PEER5d18h: gcfm_check_percall_status: component DIAL-PEER return selected=05d18h: gcfm_check_percall_status: component NUMBER-TRANSLATION5d18h: gcfm_check_percall_status: component DIAL-PEER5d18h: gcfm_check_percall_status: component DIAL-PEER return selected=05d18h: gcfm_check_percall_status: component NUMBER-TRANSLATION5d18h: gcfm_check_percall_status: component DIAL-PEER5d18h: gcfm_check_percall_status: component DIAL-PEER return selected=05d18h: gcfm_check_percall_status: component DIAL-PEER5d18h: gcfm_check_percall_status: component NUMBER-TRANSLATION5d18h: gcfm_percall_register: component CCAPI5d18h: gcfm_percall_register: component CCAPI for return selected value 05d18h: gcfm_percall_register: component VOICE-IVR-V25d18h: gcfm_percall_register: component VOICE-IVR-V2 for return selected value 05d18h: gcfm_percall_notify_condition: component VOICE-IVR-V2 for sync=15d18h: gcfm_percall_notify_condition: component VOICE-Router#IVR-V2 successfully selected = 15d18h: gcfm_percall_register: component H3235d18h: gcfm_percall_register: component H323 for return selected value 15d18h: gcfm_check_percall_status: component NUMBER-TRANSLATION5d18h: gcfm_check_percall_status: component NUMBER-TRANSLATION return selected=15d18h: gcfm_check_percall_status: component NUMBER-TRANSLATION5d18h: gcfm_check_percall_status: component NUMBER-TRANSLATION return selected=15d18h: gcfm_check_percall_status: component NUMBER-TRANSLATION5d18h: gcfm_check_percall_status: component NUMBER-TRANSLATION return selected=15d18h: gcfm_check_percall_status: component NUMBER-TRANSLATION5d18h: gcfm_check_percall_status: component NUMBER-TRANSLATION return selected=15d18h: gcfm_clear_condition: component VOICE-IVR-V25d18h: gcfm_clear_condition: component VOICE-IVR-V2 successfully5d18h: gcfm_check_percall_status: component NUMBER-TRANSLATION5d18h: gcfm_check_percall_status: component NUMBER-TRANSLATION return selected=05d18h: gcfm_percall_deregister: component CCAPI5d18h: gcfm_percall_deregister: component CCAPI successfully5d18h: gcfm_percall_deregister: component H3235d18h: gcfm_percall_deregister: component H323 successfully5d18h: gcfm_percall_deregister: component ISDN5d18h: gcfm_percall_deregister: component ISDN successfully5d18h: gcfm_percall_deregister: component VOICE-IVR-V25d18h: gcfm_percall_deregister: component VOICE-IVR-V2 successfully5d18h: gcfm_check_percall_status: component NUMBER-TRANSLATION5d18h: gcfm_check_percall_status: component NUMBER-TRANSLATION return selected=05d18h: gcfm_percall_deregister: component CCAPI5d18h: gcfm_percall_deregister: component CCAPI successfully5d18h: gcfm_percall_deregister: component VTSP5d18h: gcfm_percall_deregister: component VTSP successfully5d18h: gcfm_percall_deregister: component VOICE-IVR-V25d18h: gcfm_terminate_track_guid: component VOICE-IVR-V2 terminate, success5d18h: gcfm_percall_deregister: component VOICE-IVR-V2 successfullyTable 43 describes the significant fields shown in the display.
Related Commands
debug call-mgmt
To display debugging information for call accounting, including modem and time slot usage, for active and recent calls, use the debug call-mgmt command in privileged EXEC mode. To disable debugging output, use the no form of this command.
debug call-mgmt
no debug call-mgmt
Syntax Description
This command has no arguments or keywords.
Defaults
No default behavior or values
Command Modes
Privileged EXEC
Command History
Examples
The following is sample output after the debug call-mgmt command has been enabled:
Router# debug call-mgmtCall Management debugging is onRouter#Dec 26 13:57:27.710: msg_to_calls_mgmt: msg type CPM_NEW_CALL_CSM_CONNECT receivedDec 26 13:57:27.714: In actv_c_proc_message,access type CPM_INSERT_NEW_CALL,call type CPM_ISDN_ANALOG:CSM completed connecting a new modem call...Dec 26 13:57:45.906: msg_to_calls_mgmt: msg type CPM_NEW_CALL_ISDN_CONNECT receivedDec 26 13:57:45.906: In actv_c_proc_message,access type CPM_INSERT_NEW_CALL,call type CPM_ISDN_ANALOG:Added a new ISDN analog call to the active-calls listCC-Slot#7, DSX1-Ctrlr#17, DS0-Timeslot#1Mdm-Slot#1, Mdm-Port#3, TTY#219...Dec 26 13:58:25.682: Call mgmt per minute statistics:active list length: 1history list length: 3Dec 26 13:58:25.682: 0 timeslots active at slot 7, ctrlr 1Dec 26 13:58:25.682: 0 timeslots active at slot 7, ctrlr 2Dec 26 13:58:25.682: 0 timeslots active at slot 7, ctrlr 3Dec 26 13:58:25.682: 0 timeslots active at slot 7, ctrlr 4Dec 26 13:58:25.682: 0 timeslots active at slot 7, ctrlr 5Dec 26 13:58:25.682: 0 timeslots active at slot 7, ctrlr 6Dec 26 13:58:25.682: 0 timeslots active at slot 7, ctrlr 7Dec 26 13:58:25.682: 0 timeslots active at slot 7, ctrlr 8Dec 26 13:58:25.682: 0 timeslots active at slot 7, ctrlr 9Dec 26 13:58:25.682: 0 timeslots active at slot 7, ctrlr 10Dec 26 13:58:25.682: 0 timeslots active at slot 7, ctrlr 11Dec 26 13:58:25.682: 0 timeslots active at slot 7, ctrlr 12Dec 26 13:58:25.682: 0 timeslots active at slot 7, ctrlr 13Dec 26 13:58:25.686: 0 timeslots active at slot 7, ctrlr 14Dec 26 13:58:25.686: 0 timeslots active at slot 7, ctrlr 15Dec 26 13:58:25.686: 0 timeslots active at slot 7, ctrlr 16Dec 26 13:58:25.686: 1 timeslots active at slot 7, ctrlr 17Dec 26 13:58:25.686: 0 timeslots active at slot 7, ctrlr 18Dec 26 13:58:25.686: 0 timeslots active at slot 7, ctrlr 19Dec 26 13:58:25.686: 0 timeslots active at slot 7, ctrlr 20Dec 26 13:58:25.686: 0 timeslots active at slot 7, ctrlr 21Dec 26 13:58:25.686: 0 timeslots active at slot 7, ctrlr 22Dec 26 13:58:25.686: 0 timeslots active at slot 7, ctrlr 23Dec 26 13:58:25.686: 0 timeslots active at slot 7, ctrlr 24Dec 26 13:58:25.686: 0 timeslots active at slot 7, ctrlr 25Dec 26 13:58:25.686: 0 timeslots active at slot 7, ctrlr 26Dec 26 13:58:25.686: 0 timeslots active at slot 7, ctrlr 27Dec 26 13:58:25.686: 0 timeslots active at slot 7, ctrlr 28Router# clear int as1/03Dec 26 13:58:26.538: msg_to_calls_mgmt: msg type CPM_VOICE_CALL_REJ_NO_MOD_AVAIL receivedDec 26 13:58:26.538: In actv_c_proc_message,access type CPM_REMOVE_DISC_CALL,call type CPM_ISDN_ANALOG:Removed a disconnected ISDN analog callCC-Slot#7, DSX1-Ctrlr#17, DS0-Timeslot#1Dec 26 13:58:26.538: Mdm-Slot#1, Mdm-Port#3, TTY#219Table 44 describes the significant fields shown in the display.
debug call rsvp-sync events
To display events that occur during Resource Reservation Protocol (RSVP) setup, use the debug call rsvp-sync events command in privileged EXEC mode. To disable debugging output, use the no form of this command.
debug call rsvp-sync events
no debug call rsvp-sync events
Syntax Description
This command has no arguments or keywords.
Defaults
No default behavior or values
Command Modes
Privileged EXEC
Command History
Usage Guidelines
It is highly recommended that you log the output from the debug call rsvp-sync events command to a buffer, rather than sending the output to the console; otherwise, the size of the output could severely impact the performance of the gateway.
Examples
The following example shows a portion of sample output for a call initiating RSVP when using the debug call rsvp-sync events command:
00:03:25: Parameters: localip: 10.19.101.117 :localport: 1666000:03:25: Parameters: remoteip: 10.19.101.116 :remoteport: 1756800:03:25: QoS Primitive Event for Call id 0x1 : QoS Listen00:03:25: Lookup to be done on hashkey 0x1 in hash table 0x61FC249800:03:25: Hashed entry 0x1 in call table 0x61FC249800:03:25: Entry Not found00:03:25: Parameters: localip: 10.19.101.11700:03:25: remoteip: 10.19.101.11600:03:25: QoSpcb : 0x61FC34D800:03:25: Response Status : 0Starting timer for call with CallId 0x1 for 10000 secs00:03:25: Handling QoS Primitive QoS Listen00:03:25: Establishing RSVP RESV state : rsvp_request_reservation()00:03:25: For streams from 10.19.101.116:17568 to 10.19.101.117:1666000:03:25: RSVP Confirmation required00:03:25: QoS Primitive Event for Call id 0x1 : QoS Resv00:03:25: Lookup to be done on hashkey 0x1 in hash table 0x61FC249800:03:25: Hashed entry 0x1 in call table 0x61FC249800:03:25: Initiating RVSP PATH messages to be Sent : reg_invoke_rsvp_advertise_sender()00:03:25: Advertizing for streams to 10.19.101.116:17568 from 10.19.101.117:1666000:03:25: RESV notification event received is : 200:03:25: Received RESVCONFIRM00:03:25: RESV CONFIRM message received from 10.19.101.116 for RESV setup from 10.19.101.11700:03:25: RESV event received is : 000:03:25: RESV message received from 10.19.101.116:17568 for streams from 10.19.101.117:1666000:03:25: RESERVATIONS ESTABLISHED : CallId: 1 Stop timer and notify Session Protocol of Success (ie. if notification requested)00:03:25: Invoking spQoSresvCallback with SuccessRelated Commands
debug call rsvp-sync func-trace
To display messages about software functions called by Resource Reservation Protocol (RSVP), use the debug call rsvp-sync func-trace command in privileged EXEC mode. To disable debugging output, use the no form of this command.
debug call rsvp-sync func-trace
no debug call rsvp-sync func-trace
Syntax Description
This command has no arguments or keywords.
Defaults
No default behavior or values
Command Modes
Privileged EXEC
Command History
12.1(3)XI1
This command was introduced.
12.1(5)T
This command was integrated into Cisco IOS Release 12.1(5)T.
12.2(2)XB1
This command was implemented on the Cisco AS5850.
Usage Guidelines
It is highly recommended that you log the output from the debug call rsvp-sync func-trace command to a buffer, rather than sending the output to the console; otherwise, the size of the output could severely impact the performance of the gateway.
Examples
The following example shows a portion of sample output for a call initiating RSVP when using the debug call rsvp-sync func-trace command in conjunction with the debug call rsvp-sync events command:
00:03:41: Entering Function QoS_Listen00:03:41: Parameters:localip:10.10.101.116 :localport:1756800:03:41:remoteip:10.10.101.117 :remoteport:000:03:41: Entering Function qos_dequeue_event00:03:41: Entering Function process_queue_event00:03:41: QoS Primitive Event for Call id 0x2 :QoS Listen00:03:41: Entering Function get_pcb00:03:41: Entering Function hash_tbl_lookup00:03:41:Lookup to be done on hashkey 0x2 in hash table 0x61FAECD800:03:41: Entering Function hash_func00:03:41:Hashed entry 0x2 in call table 0x61FAECD800:03:41:Entry Not found00:03:41: Entering Function qos_dequeue_pcb00:03:41: Entering Function qos_initialize_pcb00:03:41: Parameters:localip:10.10.101.11600:03:41: remoteip:10.10.101.11700:03:41: QoSpcb :0x61FAFD1800:03:41: Response Status :000:03:41: Entering Function hash_tbl_insert_entry00:03:41: Entering Function hash_func00:03:41: Handling QoS Primitive QoS Listen00:03:41: Entering Function qos_dequeue_hash_port_entry00:03:41: Entering Function qos_port_tbl_insert_entry00:03:41: Entering Function hash_func00:03:41: Doing RSVP Listen :rsvp_add_ip_listen_api()Related Commands
debug call threshold
To see details of the trigger actions, use the debug call threshold command in privileged EXEC mode. To disable debugging output, use the no form of this command.
debug call threshold module
no debug call threshold
Syntax Description
module
The module argument can be one of the following:
•
core—Traces the resource information.
•
Defaults
Disabled
Command Modes
Privileged EXEC
Command History
Examples
The following is sample output from the debug call threshold core command:Router# debug call threshold coreRSCCAC Core info debugging is onThe following is sample output from the debug call threshold detail command:
Router# debug call threshold detailAll RSCCAC info debugging is ondebug call treatment action
To debug the call treatment actions, use the debug call treatment action command in privileged EXEC mode. To disable debugging output, use the no form of this command.
debug call treatment action
no debug call treatment action
Syntax Description
This command has no arguments or keywords.
Defaults
Disabled
Command Modes
Privileged EXEC
Command History
Examples
Debug actions are performed on calls by call treatment. The following sample output shows that call treatment is turned on:
Router# debug call treatment actionCall treatment action debugging is ondebug capf-server
To collect debug information about the CAPF server, use the debug capf-server command in privileged EXEC mode. To disable collection of debug information, use the no form of this command.
debug capf-server {all | error | events | messages}
no debug capf-server
Syntax Description
all
Collect all CAPF information available.
error
Collect only information about CAPF errors.
events
Collect only information about CAPF status events.
messages
Collect only CAPF system messages.
Command Default
Collection of CAPF debug information is disabled.
Command Modes
Privileged EXEC
Command History
12.4(4)XC
This command was introduced.
12.4(9)T
This command was integrated into Cisco IOS Release 12.4(9)T.
Usage Guidelines
This command is used with Cisco Unified CallManager Express phone authentication.
Examples
The following example shows debug messages for the CAPF server.
Router# debug capf-server all001891: .Jul 21 18:17:07.014: %IPPHONE-6-UNREGISTER_NORMAL: ephone-1:SEP000E325C9A43 IP:10.10.10.194 Socket:3 DeviceType:Phone has unregistered normally.001892: .Jul 21 18:17:20.495: New Connection from phone, socket 1001893: .Jul 21 18:17:20.495: Created New Handshake Process001894: .Jul 21 18:17:20.499: SSL Handshake Error -6983001895: .Jul 21 18:17:21.499: SSL Handshake Error -6983001896: .Jul 21 18:17:22.555: SSL Handshake Successful001897: .Jul 21 18:17:22.555: ephone_capf_send_auth_req:001898: .Jul 21 18:17:22.555: ephone_capf_ssl_write: 12 bytes001899: .Jul 21 18:17:22.711: ephone_capf_ssl_read: Read 35 bytes001900: .Jul 21 18:17:22.711: ephone_capf_handle_phone_msg: msgtype 2001901: .Jul 21 18:17:22.711: ephone_capf_process_auth_res_msg: SEP000E325C9A43 AuthMode 2001902: .Jul 21 18:17:22.711: ephone_capf_send_delete_cert_req_msg: SEP000E325C9A43001903: .Jul 21 18:17:22.711: ephone_capf_ssl_write: 8 bytes001904: .Jul 21 18:17:23.891: ephone_capf_ssl_read: Read 12 bytes001905: .Jul 21 18:17:23.891: ephone_capf_handle_phone_msg: msgtype 14001906: .Jul 21 18:17:23.891: certificate delete successful for SEP000E325C9A43001907: .Jul 21 18:17:24.695: ephone_capf_release_session: SEP000E325C9A43001908: .Jul 21 18:17:24.695: ephone_capf_send_end_session_msg: SEP000E325C9A43001909: .Jul 21 18:17:24.695: ephone_capf_ssl_write: 12 bytes001910: .Jul 21 18:17:25.095: %IPPHONE-6-REG_ALARM: 22: Name=SEP000E325C9A43 Load=7.2(2.0) Last=Reset-Reset001911: .Jul 21 18:17:25.099: %IPPHONE-6-REGISTER: ephone-1:SEP000E325C9A43 IP:10.10.10.194 Socket:2 DeviceType:Phone has registered.001912: .Jul 21 18:18:05.171: %IPPHONE-6-UNREGISTER_NORMAL: ephone-1:SEP000E325C9A43 IP:1.1.1.127 Socket:2 DeviceType:Phone has unregistered normally.001913: .Jul 21 18:18:18.288: New Connection from phone, socket 1001914: .Jul 21 18:18:18.288: Created New Handshake Process001915: .Jul 21 18:18:18.292: SSL Handshake Error -6983001916: .Jul 21 18:18:19.292: SSL Handshake Error -6983001917: .Jul 21 18:18:20.348: SSL Handshake Successful001918: .Jul 21 18:18:20.348: ephone_capf_send_auth_req:001919: .Jul 21 18:18:20.348: ephone_capf_ssl_write: 12 bytes^Z001920: .Jul 21 18:18:20.492: ephone_capf_ssl_read: Read 35 bytes001921: .Jul 21 18:18:20.492: ephone_capf_handle_phone_msg: msgtype 2001922: .Jul 21 18:18:20.492: ephone_capf_process_auth_res_msg: SEP000E325C9A43 AuthMode 2001923: .Jul 21 18:18:20.492: ephone_capf_send_PhKeyGenReq_msg: SEP000E325C9A43 KeySize 1024001924: .Jul 21 18:18:20.492: ephone_capf_ssl_write: 13 bytes001925: .Jul 21 18:18:20.540: ephone_capf_ssl_read: Read 8 bytes001926: .Jul 21 18:18:20.540: ephone_capf_handle_phone_msg: msgtype 17001927: .Jul 21 18:18:20.540: ephone_capf_process_req_in_progress: SEP000E325C9A43 delay 0sh001928: .Jul 21 18:18:21.924: %SYS-5-CONFIG_I: Configured from console by user1 on consoledebug cas
To debug channel-associated signaling (CAS) messages and to debug the establishment of a time-division multiplexing (TDM) connection between a DS0 and a digital modem, use the debug cas command in privileged EXEC mode. To disable debugging output, use the no form of this command.
debug cas slot slot number port port number
no debug cas slot slot number port port number
Syntax Description
slot slot number
Slot and slot number. Valid values are 0 and 1.
port port number
Port and port number. Valid values are 0 and 1.
Defaults
Disabled
Command Modes
Privileged EXEC
Command History
Usage Guidelines
When the NM-xCE1T1PRI network module is used with an NM-xDM and a DS0-group is configured under the controller, you can use the debug cas command to debug CAS signaling messages and the establishment of a TDM connection between a DS0 and a digital modem. Use the debug cas command to identify and troubleshoot call connection problems on a T1/E1 interface. With this command, you can trace the complete sequence of incoming and outgoing calls.
Examples
The following shows an example session to enable debugging CAS and generate troubleshooting output:
Router# show debugRouter# debug cas slot 1 port 0CAS debugging is onRouter#debug-cas is on at slot(1) dsx1(0)Router# show debugCAS debugging is onThe following example shows output for the first outgoing call:
Router# p 1.1.1.2Type escape sequence to abort.Sending 5, 100-byte ICMP Echos to 1.1.1.2, timeout is 2 seconds:*Mar 2 00:17:45: dsx1_alloc_cas_channel: channel 0 dsx1_timeslot1(0/0): TX SEIZURE (ABCD=0001)(0/0): RX SEIZURE_ACK (ABCD=1101)(0/1):RX_IDLE (ABCD=1001)(0/2): RX_IDLE (ABCD=1001)(0/3): RX_IDLE(ABCD=1001)(0/4): RX_IDLE (ABCD=1001)(0/5): RX_IDLE (ABCD=1001)(0/6):RX_IDLE (ABCD=1001)(0/7): RX_IDLE (ABCD=1001)(0/8): RX_IDLE(ABCD=1001)(0/9): RX_IDLE (ABCD=1001)(0/10): RX_IDLE (ABCD=1001)(0/11):RX_IDLE (ABCD=1001)(0/12): RX_IDLE (ABCD=1001)(0/13): RX_IDLE(ABCD=1001)(0/14): RX_IDLE (ABCD=1001)(0/16): RX_IDLE (ABCD=1001)(0/17):RX_IDLE (ABCD=1001)(0/18): RX_IDLE (ABCD=1001)(0/19): RX_IDLE(ABCD=1001)(0/20): RX_IDLE (ABCD=1001)(0/21): RX_IDLE(ABCD=1001).(0/22): RX_IDLE (ABCD=1001)(0/23): RX_IDLE(ABCD=1001)(0/24): RX_IDLE (ABCD=1001)(0/25): RX_IDLE (ABCD=1001)(0/26):RX_IDLE (ABCD=1001)(0/27): RX_IDLE (ABCD=1001)(0/28): RX_IDLE(ABCD=1001)(0/29): RX_IDLE (ABCD=1001)(0/30): RX_IDLE(ABCD=1001)...(0/0): RX ANSWERED (ABCD=0101).Success rate is 0 percent (0/5)Router#*Mar 2 00:18:13.333: %LINK-3-UPDOWN: Interface Async94, changed state to up*Mar 2 00:18:13.333: %DIALER-6-BIND: Interface As94 bound to profile Di1*Mar 2 00:18:14.577: %LINEPROTO-5-UPDOWN: Line protocol on Interface Async94, changed state to upRouter# p 1.1.1.2Type escape sequence to abort.Sending 5, 100-byte ICMP Echos to 1.1.1.2, timeout is 2 seconds:!!!!!Success rate is 100 percent (5/5), round-trip min/avg/max = 160/180/236 msThe following example shows that the call is cleared on the router:
Router# clear int dialer 1Router#(0/0): TX IDLE (ABCD=1001)(0/0): RX IDLE (ABCD=1001)*Mar 2 00:18:28.617: %LINK-5-CHANGED: Interface Async94, changed state to reset*Mar 2 00:18:28.617: %DIALER-6-UNBIND: Interface As94 unbound from profile Di1*Mar 2 00:18:29.617: %LINEPROTO-5-UPDOWN: Line protocol on Interface Async94, changed state to downet2-c3745-1#*Mar 2 00:18:33.617: %LINK-3-UPDOWN: Interface Async94, changed state to downThe following example shows a subsequent outbound CAS call:
Router# p 1.1.1.2Type escape sequence to abort.Sending 5, 100-byte ICMP Echos to 1.1.1.2, timeout is 2 seconds:*Mar 2 00:18:40: dsx1_alloc_cas_channel: channel 5 dsx1_timeslot6(0/5): TX SEIZURE (ABCD=0001)(0/5): RX SEIZURE_ACK(ABCD=1101)....(0/5): RX ANSWERED (ABCD=0101).Success rate is 0 percent (0/5)Router#*Mar 2 00:19:08.841: %LINK-3-UPDOWN: Interface Async93, changed state to up*Mar 2 00:19:08.841: %DIALER-6-BIND: Interface As93 bound to profile Di1*Mar 2 00:19:10.033: %LINEPROTO-5-UPDOWN: Line protocol on Interface Async93, changed state to upRouter# p 1.1.1.2Type escape sequence to abort.Sending 5, 100-byte ICMP Echos to 1.1.1.2, timeout is 2 seconds:!!!!!Success rate is 100 percent (5/5), round-trip min/avg/max = 160/167/176msThe following example shows the call cleared by the switch:
Router#(0/5): TX IDLE (ABCD=1001)(0/5): RX IDLE (ABCD=1001)*Mar 2 00:19:26.249: %LINK-5-CHANGED: Interface Async93, changed state to reset*Mar 2 00:19:26.249: %DIALER-6-UNBIND: Interface As93 unbound from profile Di1*Mar 2 00:19:27.249: %LINEPROTO-5-UPDOWN: Line protocol on Interface Async93, changed state to downRouter#*Mar 2 00:19:31.249: %LINK-3-UPDOWN: Interface Async93, changed state to downThe following example shows an incoming CAS call:
Router#(0/0): RX SEIZURE (ABCD=0001)*Mar 2 00:22:40: dsx1_alloc_cas_channel: channel 0 dsx1_timeslot1(0/0): TX SEIZURE_ACK (ABCD=1101)(0/0): TX ANSWERED (ABCD=0101)Router#*Mar 2 00:23:06.249: %LINK-3-UPDOWN: Interface Async83, changed state to up*Mar 2 00:23:06.249: %DIALER-6-BIND: Interface As83 bound to profile Di1*Mar 2 00:23:07.653: %LINEPROTO-5-UPDOWN: Line protocol on Interface Async83, changed state to upRelated Commands
show debug
Displays information about the types of debugging that are enabled for your router.
debug ccaal2 session
To display the ccaal2 function calls during call setup and teardown, use the debug ccaal2 session command in privileged EXEC mode. To disable debugging output, use the no form of this command.
debug ccaal2 session
no debug ccaal2 session
Syntax Description
This command has no arguments or keywords.
Defaults
Debugging for ATM Adaptation Layer type 2 (AAL2) sessions is not enabled.
Command Modes
Privileged EXEC
Command History
Usage Guidelines
Use this command when troubleshooting an AAL2 trunk setup or teardown problem.
Examples
The following example shows sample output from the debug ccaal2 session command for a forced shutdown of a voice port:
Router# debug ccaal2 sessionCCAAL2 Session debugging is onRouter# configure terminalEnter configuration commands, one per line. End with CNTL/Z.Router(config)# voice-port 2/0:0Router(config-voiceport)# shutdown00:32:45:ccaal2_call_disconnect:peer tag 000:32:45:ccaal2_evhandle_call_disconnect:Entered00:32:45:ccaal2_call_cleanup:freeccb 1, call_disconnected 100:32:45:starting incoming timer:Setting accept_incoming to FALSE and00:32:45:timer 2:(0x622F6270)starts - delay (70000)00:32:45:ccaal2_call_cleanup:Generating Call record00:32:45:cause=81 tcause=81 cause_text=unspecified00:32:45:ccaal2_call_cleanup:ccb 0x63FF1700, vdbPtr 0x62DFF2E0freeccb_flag=1, call_disconnected_flag=100:32:45:%LINK-3-UPDOWN:Interface recEive and transMit2/0:0(1),changed state to Administrative ShutdownThe following example shows sample output from the debug ccaal2 session command for a trunk setup on a voice port:
Router# debug ccaal2 sessionRouter(config-voiceport)# no shutdownRouter(config-voiceport)#00:35:28:%LINK-3-UPDOWN:Interface recEive and transMit2/0:0(1),changed state to up00:35:35:ccaal2_call_setup_request:Entered00:35:35:ccaal2_evhandle_call_setup_request:Entered00:35:35:ccaal2_initialize_ccb:preferred_codec set(-1)(0)00:35:35:ccaal2_evhandle_call_setup_request:preferred_codecset(5)(40). VAD is 100:35:35:ccaal2_call_setup_trunk:subchannel linkingsuccessfulccaal2_receive:xmitFunc is NULL00:35:35:ccaal2_caps_ind:PeerTag = 4900:35:35: codec(preferred) = 1, fax_rate = 2, vad = 200:35:35: cid = 56, config_bitmask = 258, codec_bytes = 40,signal_type=800:35:36:%HTSP-5-UPDOWN:Trunk port(channel) [2/0:0(1)] is upRouter(config-voiceport)#Related Commands
debug ccfrf11 session
To display the ccfrf11 function calls during call setup and teardown, use the debug ccfrf11 session command in privileged EXEC mode. To disable debugging output, use the no form of this command.
debug ccfrf11 session
no debug ccfrf11 session
Syntax Description
This command has no keywords or arguments.
Command Modes
Privileged EXEC
Command History
Usage Guidelines
Use this command to display debug information about the various FRF.11 VoFR service provider interface (SPI) functions. Note that this debug command does not display any information regarding the proprietary Cisco switched-VoFR SPI.
This debug is useful only when the session protocol is "frf11-trunk."
Examples
The following is sample output from the debug ccfrf11 session command:
Router# debug ccfrf11 sessionINCOMING CALL SETUP (port setup for answer-mode):*Mar 6 18:04:07.693:ccfrf11_process_timers:scb (0x60EB6040) timer (0x60EB6098) expired*Mar 6 18:04:07.693:Setting accept_incoming to TRUE*Mar 6 18:04:11.213:ccfrf11_incoming_request:peer tag 800:callingNumber=+2602100,calledNumber=+3622110*Mar 6 18:04:11.213:ccfrf11_initialize_ccb:preffered_codec set(-1)(0)*Mar 6 18:04:11.213:ccfrf11_evhandle_incoming_call_setup_request:calling +2602100,called +3622110 Incoming Tag 800*Mar 6 18:04:11.217:ccfrf11_caps_ind:PeerTag = 800*Mar 6 18:04:11.217: codec(preferred) = 4, fax_rate = 2, vad = 2*Mar 6 18:04:11.217: cid = 30, config_bitmask = 0, codec_bytes = 20, signal_type=2*Mar 6 18:04:11.217: required_bandwidth 8192*Mar 6 18:04:11.217:ccfrf11_caps_ind:Bandwidth reservation of 8192 bytes succeeded.*Mar 6 18:04:11.221:ccfrf11_evhandle_call_connect:EnteredCALL SETUP (MASTER):5d22h:ccfrf11_call_setup_request:Entered5d22h:ccfrf11_evhandle_call_setup_request:Entered5d22h:ccfrf11_initialize_ccb:preffered_codec set(-1)(0)5d22h:ccfrf11_evhandle_call_setup_request:preffered_codec set(9)(24)5d22h:ccfrf11_call_setup_trunk:subchannel linking successful5d22h:ccfrf11_caps_ind:PeerTag = 8105d22h: codec(preferred) = 512, fax_rate = 2, vad = 25d22h: cid = 30, config_bitmask = 1, codec_bytes = 24, signal_type=25d22h: required_bandwidth 65005d22h:ccfrf11_caps_ind:Bandwidth reservation of 6500 bytes succeeded.CALL TEARDOWN:*Mar 6 18:09:14.805:ccfrf11_call_disconnect:peer tag 0*Mar 6 18:09:14.805:ccfrf11_evhandle_call_disconnect:Entered*Mar 6 18:09:14.805:ccfrf11_call_cleanup:freeccb 1, call_disconnected 1*Mar 6 18:09:14.805:ccfrf11_call_cleanup:Setting accept_incoming to FALSE and startingincoming timer*Mar 6 18:09:14.809:timer 2:(0x60EB6098)starts - delay (70000)*Mar 6 18:09:14.809:ccfrf11_call_cleanup:Alive timer stopped*Mar 6 18:09:14.809:timer 1:(0x60F64104) stops*Mar 6 18:09:14.809:ccfrf11_call_cleanup:Generating Call record*Mar 6 18:09:14.809:cause=10 tcause=10 cause_text="normal call clearing."*Mar 6 18:09:14.809:ccfrf11_call_cleanup:Releasing 8192 bytes of reserved bandwidth*Mar 6 18:09:14.809:ccfrf11_call_cleanup:ccb 0x60F6404C, vdbPtr 0x610DB7A4freeccb_flag=1, call_disconnected_flag=1Related Commands
Posted: Mon Jul 2 07:34:35 PDT 2007
All contents are Copyright © 1992--2007 Cisco Systems, Inc. All rights reserved.
Important Notices and Privacy Statement.