Debug Command Reference: Commands debug lane client through debug mmoip transfer

Table Of Contents

debug lane client

debug lane config

debug lane finder

debug lane server

debug lane signaling

debug lapb

debug lapb-ta

debug lat packet

debug lex rcmd

debug link monitor

debug list

debug llc2 dynwind

debug llc2 errors

debug llc2 packet

debug llc2 state

debug lnm events

debug lnm llc

debug lnm mac

debug local-ack state

debug management event

debug mdss

debug media resource provisioning all

debug media resource provisioning errors

debug media resource provisioning events

debug mediacard

debug mgcp all

debug mgcp endpoint

debug mgcp endptdb

debug mgcp errors

debug mgcp events

debug mgcp gcfm

debug mgcp inout

debug mgcp media

debug mgcp nas

debug mgcp packets

debug mgcp parser

debug mgcp src

debug mgcp state

debug mgcp tracelevel-default

debug mgcp voipcac

debug mls rp

debug mls rp ip multicast

debug mmoip aaa

debug mmoip send email

debug mmoip send fax

debug mmoip transfer

debug lane client

To display information about a LAN Emulation Client (LEC), use the debug lane client command in privileged EXEC mode. To disable debugging output, use the no form of this command.

debug lane client {all | le-arp | mpoa | packet | signaling | state | topology} [interface interface]
no debug lane client {all | le-arp | mpoa | packet | signaling | state | topology} [interface interface]
Syntax Description

all

Displays all debug information related to the LEC.

le-arp

Displays debug information related to the LAN Emulation (LANE) Address Resolution Protocol (ARP) table.

mpoa

Displays debug information to track the following:

•MPOA specific TLV information in le-arp requests/responses

•Elan-id and local segment TLV in lane control frames

•When a LANE client is bound to an MPC/MPS

packet

Displays debug information about each packet.

signaling

Displays debug information related to client switched virtual circuits (SVCs).

state

Displays debug information when the state changes.

topology

Displays debug information related to the topology of the emulated LAN (ELAN).

interface interface

(Optional) Limits the debugging output to messages that relate to a particular interface or subinterface. If you enter this command multiple times with different interfaces, the last interface entered will be the one used to filter the messages.

Defaults

If the interface number is not specified, the default will be the number of all the mpoa lane clients.

Command Modes

Privileged EXEC

Command History

Release

Modification

12.0(1)T

This command was introduced.

Usage Guidelines

The debug lane client all command can generate a large amount of output. Use a limiting keyword or specify a subinterface to decrease the amount of output and focus on the information you need.

Examples

The following example shows output for debug lane client packet and debug lane client state commands for an LEC joining an ELAN named elan1:

Router# debug lane client packet

Router# debug lane client state

The LEC listens for signaling calls to its ATM address (Initial State):

LEC ATM2/0.1: sending LISTEN
LEC ATM2/0.1: listen on 39.020304050607080910111213.00000CA05B40.01
LEC ATM2/0.1: received LISTEN

The LEC calls the LAN Emulation Configuration Server (LECS) and attempts to set up the Configure Direct VC (LECS Connect Phase):

LEC ATM2/0.1: sending SETUP
LEC ATM2/0.1: callid 0x6114D174
LEC ATM2/0.1: called party 39.020304050607080910111213.00000CA05B43.00
LEC ATM2/0.1: calling_party 39.020304050607080910111213.00000CA05B40.01

The LEC receives a CONNECT response from the LECS. The Configure Direct VC is established:

LEC ATM2/0.1: received CONNECT
LEC ATM2/0.1: callid 0x6114D174
LEC ATM2/0.1: vcd 148

The LEC sends a CONFIG REQUEST to the LECS on the Configure Direct VC (Configuration Phase):

LEC ATM2/0.1: sending LANE_CONFIG_REQ on VCD 148
LEC ATM2/0.1: SRC MAC address 0000.0ca0.5b40
LEC ATM2/0.1: SRC ATM address 39.020304050607080910111213.00000CA05B40.01
LEC ATM2/0.1: LAN Type 2
LEC ATM2/0.1: Frame size 2
LEC ATM2/0.1: LAN Name elan1
LEC ATM2/0.1: LAN Name size 5

The LEC receives a CONFIG RESPONSE from the LECS on the Configure Direct VC:

LEC ATM2/0.1: received LANE_CONFIG_RSP on VCD 148
LEC ATM2/0.1: SRC MAC address 0000.0ca0.5b40
LEC ATM2/0.1: SRC ATM address 39.020304050607080910111213.00000CA05B40.01
LEC ATM2/0.1: LAN Type 2
LEC ATM2/0.1: Frame size 2
LEC ATM2/0.1: LAN Name elan1
LEC ATM2/0.1: LAN Name size 5

The LEC releases the Configure Direct VC:

LEC ATM2/0.1: sending RELEASE
LEC ATM2/0.1: callid 0x6114D174
LEC ATM2/0.1: cause code 31

The LEC receives a RELEASE_COMPLETE from the LECS:

LEC ATM2/0.1: received RELEASE_COMPLETE
LEC ATM2/0.1: callid 0x6114D174
LEC ATM2/0.1: cause code 16

The LEC calls the LAN Emulation Server (LES) and attempts to set up the Control Direct VC (Join/Registration Phase):

LEC ATM2/0.1: sending SETUP
LEC ATM2/0.1: callid 0x61167110
LEC ATM2/0.1: called party 39.020304050607080910111213.00000CA05B41.01
LEC ATM2/0.1: calling_party 39.020304050607080910111213.00000CA05B40.01

The LEC receives a CONNECT response from the LES. The Control Direct VC is established:

LEC ATM2/0.1: received CONNECT
LEC ATM2/0.1: callid 0x61167110
LEC ATM2/0.1: vcd 150

The LEC sends a JOIN REQUEST to the LES on the Control Direct VC:

LEC ATM2/0.1: sending LANE_JOIN_REQ on VCD 150
LEC ATM2/0.1: Status 0
LEC ATM2/0.1: LECID 0
LEC ATM2/0.1: SRC MAC address 0000.0ca0.5b40
LEC ATM2/0.1: SRC ATM address 39.020304050607080910111213.00000CA05B40.01
LEC ATM2/0.1: LAN Type 2
LEC ATM2/0.1: Frame size 2
LEC ATM2/0.1: LAN Name elan1
LEC ATM2/0.1: LAN Name size 5

The LEC receives a SETUP request from the LES to set up the Control Distribute VC:

LEC ATM2/0.1: received SETUP
LEC ATM2/0.1: callid 0x6114D174
LEC ATM2/0.1: called party 39.020304050607080910111213.00000CA05B40.01
LEC ATM2/0.1: calling_party 39.020304050607080910111213.00000CA05B41.01

The LEC responds to the LES call setup with a CONNECT:

LEC ATM2/0.1: sending CONNECT
LEC ATM2/0.1: callid 0x6114D174
LEC ATM2/0.1: vcd 151

A CONNECT_ACK is received from the ATM switch. The Control Distribute VC is established:

LEC ATM2/0.1: received CONNECT_ACK

The LEC receives a JOIN response from the LES on the Control Direct VC.

LEC ATM2/0.1: received LANE_JOIN_RSP on VCD 150
LEC ATM2/0.1: Status 0
LEC ATM2/0.1: LECID 1
LEC ATM2/0.1: SRC MAC address 0000.0ca0.5b40
LEC ATM2/0.1: SRC ATM address 39.020304050607080910111213.00000CA05B40.01
LEC ATM2/0.1: LAN Type 2
LEC ATM2/0.1: Frame size 2
LEC ATM2/0.1: LAN Name elan1
LEC ATM2/0.1: LAN Name size 5

The LEC sends an LE ARP request to the LES to obtain the broadcast and unknown server (BUS) ATM NSAP address (BUS connect):

LEC ATM2/0.1: sending LANE_ARP_REQ on VCD 150
LEC ATM2/0.1: SRC MAC address 0000.0ca0.5b40
LEC ATM2/0.1: SRC ATM address 39.020304050607080910111213.00000CA05B40.01
LEC ATM2/0.1: TARGET MAC address ffff.ffff.ffff
LEC ATM2/0.1: TARGET ATM address 00.000000000000000000000000.000000000000.00

The LEC receives its own LE ARP request via the LES over the Control Distribute VC:

LEC ATM2/0.1: received LANE_ARP_RSP on VCD 151
LEC ATM2/0.1: SRC MAC address 0000.0ca0.5b40
LEC ATM2/0.1: SRC ATM address 39.020304050607080910111213.00000CA05B40.01
LEC ATM2/0.1: TARGET MAC address ffff.ffff.ffff
LEC ATM2/0.1: TARGET ATM address 39.020304050607080910111213.00000CA05B42.01

The LEC calls the BUS and attempts to set up the Multicast Send VC:

LEC ATM2/0.1: sending SETUP
LEC ATM2/0.1: callid 0x6114D354
LEC ATM2/0.1: called party 39.020304050607080910111213.00000CA05B42.01
LEC ATM2/0.1: calling_party 39.020304050607080910111213.00000CA05B40.01

The LEC receives a CONNECT response from the BUS. The Multicast Send VC is established:

LEC ATM2/0.1: received CONNECT
LEC ATM2/0.1: callid 0x6114D354
LEC ATM2/0.1: vcd 153

The LEC receives a SETUP request from the BUS to set up the Multicast Forward VC:

LEC ATM2/0.1: received SETUP
LEC ATM2/0.1: callid 0x610D4230
LEC ATM2/0.1: called party 39.020304050607080910111213.00000CA05B40.01
LEC ATM2/0.1: calling_party 39.020304050607080910111213.00000CA05B42.01

The LEC responds to the BUS call setup with a CONNECT:

LEC ATM2/0.1: sending CONNECT
LEC ATM2/0.1: callid 0x610D4230
LEC ATM2/0.1: vcd 154

A CONNECT_ACK is received from the ATM switch. The Multicast Forward VC is established:

LEC ATM2/0.1: received CONNECT_ACK

The LEC moves into the OPERATIONAL state.

%LANE-5-UPDOWN: ATM2/0.1 elan elan1: LE Client changed state to up

The following output is from the show lane client command after the LEC joins the emulated LAN as shown in the debug lane client output:

Router# show lane client

LE Client ATM2/0.1 ELAN name: elan1 Admin: up State: operational
Client ID: 1 LEC up for 1 minute 2 seconds
Join Attempt: 1
HW Address: 0000.0ca0.5b40 Type: token ring Max Frame Size: 4544
Ring:1 Bridge:1 ELAN Segment ID: 2048
ATM Address: 39.020304050607080910111213.00000CA05B40.01
VCD rxFrames txFrames Type ATM Address
0 0 0 configure 39.020304050607080910111213.00000CA05B43.00
142 1 2 direct 39.020304050607080910111213.00000CA05B41.01
143 1 0 distribute 39.020304050607080910111213.00000CA05B41.01
145 0 0 send 39.020304050607080910111213.00000CA05B42.01
146 1 0 forward 39.020304050607080910111213.00000CA05B42.01

The following example shows debug lane client all command output when an interface with LECS, an LES/BUS, and an LEC is shut down:

Router# debug lane client all

LEC ATM1/0.2: received RELEASE_COMPLETE
LEC ATM1/0.2: callid 0x60E8B474
LEC ATM1/0.2: cause code 0
LEC ATM1/0.2: action A_PROCESS_REL_COMP
LEC ATM1/0.2: action A_TEARDOWN_LEC
LEC ATM1/0.2: sending RELEASE
LEC ATM1/0.2: callid 0x60EB6160
LEC ATM1/0.2: cause code 31
LEC ATM1/0.2: sending RELEASE
LEC ATM1/0.2: callid 0x60EB7548
LEC ATM1/0.2: cause code 31
LEC ATM1/0.2: sending RELEASE
LEC ATM1/0.2: callid 0x60EB9E48
LEC ATM1/0.2: cause code 31
LEC ATM1/0.2: sending CANCEL
LEC ATM1/0.2: ATM address 47.00918100000000613E5A2F01.006070174820.02
LEC ATM1/0.2: state ACTIVE event LEC_SIG_RELEASE_COMP => TERMINATING
LEC ATM1/0.3: received RELEASE_COMPLETE
LEC ATM1/0.3: callid 0x60E8D108
LEC ATM1/0.3: cause code 0
LEC ATM1/0.3: action A_PROCESS_REL_COMP
LEC ATM1/0.3: action A_TEARDOWN_LEC
LEC ATM1/0.3: sending RELEASE
LEC ATM1/0.3: callid 0x60EB66D4
LEC ATM1/0.3: cause code 31
LEC ATM1/0.3: sending RELEASE
LEC ATM1/0.3: callid 0x60EB7B8C
LEC ATM1/0.3: cause code 31
LEC ATM1/0.3: sending RELEASE
LEC ATM1/0.3: callid 0x60EBA3BC
LEC ATM1/0.3: cause code 31
LEC ATM1/0.3: sending CANCEL
LEC ATM1/0.3: ATM address 47.00918100000000613E5A2F01.006070174820.03
LEC ATM1/0.3: state ACTIVE event LEC_SIG_RELEASE_COMP => TERMINATING
LEC ATM1/0.2: received RELEASE_COMPLETE
LEC ATM1/0.2: callid 0x60EB7548
LEC ATM1/0.2: cause code 0
LEC ATM1/0.2: action A_PROCESS_TERM_REL_COMP
LEC ATM1/0.2: state TERMINATING event LEC_SIG_RELEASE_COMP => TERMINATING
LEC ATM1/0.3: received RELEASE_COMPLETE
LEC ATM1/0.3: callid 0x60EB7B8C
LEC ATM1/0.3: cause code 0
LEC ATM1/0.3: action A_PROCESS_TERM_REL_COMP
LEC ATM1/0.3: state TERMINATING event LEC_SIG_RELEASE_COMP => TERMINATING
LEC ATM1/0.1: received RELEASE_COMPLETE
LEC ATM1/0.1: callid 0x60EBC458
LEC ATM1/0.1: cause code 0
LEC ATM1/0.1: action A_PROCESS_REL_COMP
LEC ATM1/0.1: action A_TEARDOWN_LEC
LEC ATM1/0.1: sending RELEASE
LEC ATM1/0.1: callid 0x60EBD30C
LEC ATM1/0.1: cause code 31
LEC ATM1/0.1: sending RELEASE
LEC ATM1/0.1: callid 0x60EBDD28
LEC ATM1/0.1: cause code 31
LEC ATM1/0.1: sending RELEASE
LEC ATM1/0.1: callid 0x60EBF174
LEC ATM1/0.1: cause code 31
LEC ATM1/0.1: sending CANCEL
LEC ATM1/0.1: ATM address 47.00918100000000613E5A2F01.006070174820.01
LEC ATM1/0.1: state ACTIVE event LEC_SIG_RELEASE_COMP => TERMINATING
LEC ATM1/0.1: received RELEASE_COMPLETE
LEC ATM1/0.1: callid 0x60EBDD28
LEC ATM1/0.1: cause code 0
LEC ATM1/0.1: action A_PROCESS_TERM_REL_COMP
LEC ATM1/0.1: state TERMINATING event LEC_SIG_RELEASE_COMP => TERMINATING
LEC ATM1/0.2: received RELEASE_COMPLETE
LEC ATM1/0.2: callid 0x60EB6160
LEC ATM1/0.2: cause code 0
LEC ATM1/0.2: action A_PROCESS_TERM_REL_COMP
LEC ATM1/0.2: state TERMINATING event LEC_SIG_RELEASE_COMP => TERMINATING
LEC ATM1/0.3: received RELEASE_COMPLETE
LEC ATM1/0.3: callid 0x60EB66D4
LEC ATM1/0.3: cause code 0
LEC ATM1/0.3: action A_PROCESS_TERM_REL_COMP
LEC ATM1/0.3: state TERMINATING event LEC_SIG_RELEASE_COMP => TERMINATING
LEC ATM1/0.2: received RELEASE_COMPLETE
LEC ATM1/0.2: callid 0x60EB9E48
LEC ATM1/0.2: cause code 0
LEC ATM1/0.2: action A_PROCESS_TERM_REL_COMP
LEC ATM1/0.2: state TERMINATING event LEC_SIG_RELEASE_COMP => IDLE
LEC ATM1/0.3: received RELEASE_COMPLETE
LEC ATM1/0.3: callid 0x60EBA3BC
LEC ATM1/0.3: cause code 0
LEC ATM1/0.3: action A_PROCESS_TERM_REL_COMP
LEC ATM1/0.3: state TERMINATING event LEC_SIG_RELEASE_COMP => IDLE
LEC ATM1/0.1: received RELEASE_COMPLETE
LEC ATM1/0.1: callid 0x60EBD30C
LEC ATM1/0.1: cause code 0
LEC ATM1/0.1: action A_PROCESS_TERM_REL_COMP
LEC ATM1/0.1: state TERMINATING event LEC_SIG_RELEASE_COMP => TERMINATING
LEC ATM1/0.1: received RELEASE_COMPLETE
LEC ATM1/0.1: callid 0x60EBF174
LEC ATM1/0.1: cause code 0
LEC ATM1/0.1: action A_PROCESS_TERM_REL_COMP
LEC ATM1/0.1: state TERMINATING event LEC_SIG_RELEASE_COMP => IDLE
LEC ATM1/0.2: received CANCEL
LEC ATM1/0.2: state IDLE event LEC_SIG_CANCEL => IDLE
LEC ATM1/0.3: received CANCEL
LEC ATM1/0.3: state IDLE event LEC_SIG_CANCEL => IDLE
LEC ATM1/0.1: received CANCEL
LEC ATM1/0.1: state IDLE event LEC_SIG_CANCEL => IDLE
LEC ATM1/0.1: action A_SHUTDOWN_LEC
LEC ATM1/0.1: sending CANCEL
LEC ATM1/0.1: ATM address 47.00918100000000613E5A2F01.006070174820.01
LEC ATM1/0.1: state IDLE event LEC_LOCAL_DEACTIVATE => IDLE
LEC ATM1/0.2: action A_SHUTDOWN_LEC
LEC ATM1/0.2: sending CANCEL
LEC ATM1/0.2: ATM address 47.00918100000000613E5A2F01.006070174820.02
LEC ATM1/0.2: state IDLE event LEC_LOCAL_DEACTIVATE => IDLE
LEC ATM1/0.3: action A_SHUTDOWN_LEC
LEC ATM1/0.3: sending CANCEL
LEC ATM1/0.3: ATM address 47.00918100000000613E5A2F01.006070174820.03
LEC ATM1/0.3: state IDLE event LEC_LOCAL_DEACTIVATE => IDLE

The following output is from the debug lane client mpoa command when the lane interface is shut down:

Router# debug lane client mpoa

Router#conf t
Enter configuration commands, one per line. End with CNTL/Z.
Router(config)#int atm 1/1/0.1
Router(config-subif)#shutdown
Router(config-subif)#
00:23:32:%LANE-5-UPDOWN:ATM1/1/0.1 elan elan2:LE Client changed state to down
00:23:32:LEC ATM1/1/0.1:lec_inform_mpoa_state_chg:DOWN
00:23:32:LEC ATM1/1/0.1:lec_inform_mpoa_state_chg:DOWN
Router(config-subif)#
Router(config-subif)#
Router(config-subif)#
Router(config-subif)#exit
Router(config)#exit

The following output is from the debug lane client mpoa command when the lane interface is started (not shut down):

Router# debug lane client mpoa

Router#conf t
Enter configuration commands, one per line. End with CNTL/Z.
Router(config)#int atm 1/1/0.1
Router(config-subif)#
Router(config-subif)#
Router(config-subif)#no shutdown
Router(config-subif)#
00:23:39:LEC ATM1/1/0.1:lec_process_lane_tlv:msg LANE_CONFIG_RSP, num_tlvs 14
00:23:39:LEC ATM1/1/0.1:elan id from LECS set to 300
00:23:39:LEC ATM1/1/0.1:lec_process_lane_tlv:msg LANE_JOIN_RSP, num_tlvs 1
00:23:39:LEC ATM1/1/0.1:elan id from LES set to 300
00:23:39:LEC ATM1/1/0.1:lec_append_mpoa_dev_tlv:
00:23:39:LEC ATM1/1/0.1:got mpoa client addr 47.0091810000000050E2097801.0050A
29AF42D.00
00:23:39:%LANE-5-UPDOWN:ATM1/1/0.1 elan elan2:LE Client changed state to up
00:23:39:LEC ATM1/1/0.1:lec_inform_mpoa_state_chg:UP
00:25:57:LEC ATM1/1/0.1:lec_process_lane_tlv:msg LANE_ARP_REQ, num_tlvs 1
00:25:57:LEC ATM1/1/0.1:lec_process_dev_type_tlv: lec 47.0091810000000050E
2097801.00500B306440.02
type MPS, mpc 00.000000000000000000000000.000000000000.00
mps 47.0091810000000050E2097801.00500B306444.00, num_mps_mac 1, mac 0050.0b3
0.6440
00:25:57:LEC ATM1/1/0.1:create mpoa_lec
00:25:57:LEC ATM1/1/0.1:new mpoa_lec 0x617E3118
00:25:57:LEC ATM1/1/0.1:lec_process_dev_type_tlv:type MPS, num _mps_mac
1
00:2t 5:57:LEC ATM1/1/0.1:lec_add_mps:
remote lec 47.0091810000000050E2097801.00500B306440.02
mps 47.0091810000000050E2097801.00500B306444.00 num_mps_mac 1, mac 0050.0b30
.6440
00:25:57:LEC ATM1/1/0.1:mpoa_device_change:lec_nsap 47.0091810000000050E20978
01.00500B306440.02, appl_type 5
mpoa_nsap 47.0091810000000050E2097801.00500B306444.00, opcode 4
00:25:57:LEC ATM1/1/0.1:lec_add_mps:add mac 0050.0b30.6440, mps_mac 0x617E372
C
00:25:57:LEC ATM1/1/0.1:mpoa_device_change:lec_nsap 47.0091810000000050E20978
01.00500B306440.02, appl_type 5
mpoa_nsap 47.0091810000000050E2097801.00500B306444.00, opcode 5
00:25:57:LEC ATM1/1/0.1: mps_mac 0050.0b30.6440
00:25:57:LEC ATM1/1/0.1:lec_append_mpoa_dev_tlv:
00:25:57:LEC ATM1/1/0.1:got mpoa client addr 47.0091810000000050E2097801.0050A
29AF42D.00
Router(config-subif)#exit
Router(config)#exit

The following output is from the debug lane client mpoa command when the ATM major interface is shut down:

Router# debug lane client mpoa

Router# conf t
Enter configuration commands, one per line. End with CNTL/Z.
Router(config)#int atm 1/1/0
Router(config-if)# shutdown
Router(config-if)#
00:26:28:LANE ATM1/1/0:atm hardware reset
00:26:28:%LANE-5-UPDOWN:ATM1/1/0.1 elan elan2:LE Client changed state to down
00:26:28:LEC ATM1/1/0.1:lec_inform_mpoa_state_chg:DOWN
00:26:28:LEC ATM1/1/0.1:lec_inform_mpoa_state_chg:DOWN
00:26:28:%MPOA-5-UPDOWN:MPC mpc2:state changed to down
00:26:28:LEC ATM1/1/0.1:mpoa_to_lec:appl 6, opcode 0
00:26:30:%LINK-5-CHANGED:Interface ATM1/1/0, changed state to administratively
down
00:26:30:LANE ATM1/1/0:atm hardware reset
00:26:31:%LINEPROTO-5-UPDOWN:Line protocol on Interface ATM1/1/0, changed stat
e to down
Router(config-if)#
00:26:31:LEC ATM1/1/0.1:mpoa_to_lec:appl 6, opcode 0

00:26:32:LANE ATM1/1/0:atm hardware reset
00:26:32:LEC ATM1/1/0.1:lec_inform_mpoa_state_chg:DOWN
00:26:34:LEC ATM1/1/0.1:lec_inform_mpoa_state_chg:DOWN
Router(config-if)# exit
Router(config)# exit

The following output is from the debug lane client mpoa command when the ATM major interface is started:

Router# debug lane client mpoa

Router# conf t
Enter configuration commands, one per line. End with CNTL/Z.
Router(config)# int atm 1/1/0
Router(config-if)# no shutdown
00:26:32:LANE ATM1/1/0:atm hardware reset
00:26:32:LEC ATM1/1/0.1:lec_inform_mpoa_state_chg:DOWN
00:26:34:%LINK-3-UPDOWN:Interface ATM1/1/0, changed state to down
00:26:34:LANE ATM1/1/0:atm hardware reset
00:26:41:%LINK-3-UPDOWN:Interface ATM1/1/0, changed state to up
00:26:42:%LINEPROTO-5-UPDOWN:Line protocol on Interface ATM1/1/0, changed stat
e to up
00:27:10:%LANE-6-INFO:ATM1/1/0:ILMI prefix add event received
00:27:10:LANE ATM1/1/0:prefix add event for 470091810000000050E2097801 ptr=0x6
17BFC0C len=13
00:27:10: the current first prefix is now:470091810000000050E2097801
00:27:10:%ATMSSCOP-5-SSCOPINIT:- Intf :ATM1/1/0, Event :Rcv End, State :Act
ive.
00:27:10:LEC ATM1/1/0.1:mpoa_to_lec:appl 6, opcode 0

00:27:10:%LANE-3-NOREGILMI:ATM1/1/0.1 LEC cannot register 47.0091810000000050E
2097801.0050A29AF428.01 with ILMI
00:27:10:%LANE-6-INFO:ATM1/1/0:ILMI prefix add event received
00:27:10:LANE ATM1/1/0:prefix add event for 470091810000000050E2097801 ptr=0x6
17B8E6C len=13
00:27:10: the current first prefix is now:470091810000000050E2097801
00:27:10:%LANE-5-UPDOWN:ATM1/1/0.1 elan elan2:LE Client changed state to down
00:27:10:LEC ATM1/1/0.1:lec_inform_mpoa_state_chg:DOWN
00:27:10:LEC ATM1/1/0.1:mpoa_to_lec:appl 6, opcode 0

00:27:10:%MPOA-5-UPDOWN:MPC mpc2:state changed to up
00:27:10:LEC ATM1/1/0.1:mpoa_to_lec:appl 6, opcode 1

00:27:12:LEC ATM1/1/0.1:lec_process_lane_tlv:msg LANE_CONFIG_RSP, num_tlvs 14
00:27:12:LEC ATM1/1/0.1:elan id from LECS set to 300
00:27:12:LEC ATM1/1/0.1:lec_process_lane_tlv:msg LANE_JOIN_RSP, num_tlvs 1
00:27:12:LEC ATM1/1/0.1:elan id from LES set to 300
00:27:12:LEC ATM1/1/0.1:lec_append_mpoa_dev_tlv:
00:27:12:LEC ATM1/1/0.1:got mpoa client addr 47.0091810000000050E2097801.0050A
29AF42D.00
00:27:12:%LANE-5-UPDOWN:ATM1/1/0.1 elan elan2:LE Client changed state to up
00:27:12:LEC ATM1/1/0.1:lec_inform_mpoa_state_chg:UP
Router(config-if)# exit
Router(config)# exit
Related Commands

Command

Description

debug modem traffic

Displays MPC debug information.

debug mpoa server

Displays information about the MPOA server.

debug lane config

To display information about a LAN Emulation (LANE) configuration server, use the debug lane config command in privileged EXEC mode. To disable debugging output, use the no form of this command.

debug lane config {all | events | packets}
no debug lane config {all | events | packets}
Syntax Description

all

Displays all debugging messages related to the LANE configuration server. The output includes both the events and packets types of output.

events

Displays only messages related to significant LANE configuration server events.

packets

Displays information on each packet sent or received by the LANE configuration server.

Command Modes

Privileged EXEC

Usage Guidelines

The debug lane config output is intended to be used primarily by a Cisco technical support representative.

Examples

The following is sample output from the debug lane config all command when an interface with LECS, an LES/BUS, and an LEC is shut down:

Router# debug lane config all

LECS EVENT ATM1/0: processing interface down transition
LECS EVENT ATM1/0: placed de-register address 0x60E8A824 (47.00918100000000613E5A2F01.006070174823.00) request with signalling
LECS EVENT ATM1/0: ilmiDeRegisterAddress: sendSetRequestToILMI failure; interface down ?
LECS EVENT ATM1/0: placed de-register address 0x60EC4F28 (47.007900000000000000000000.00A03E000001.00) request with signalling
LECS EVENT ATM1/0: ilmiDeRegisterAddress: sendSetRequestToILMI failure; interface down ?
LECS EVENT ATM1/0: placed de-register address 0x60EC5C08 (47.00918100000000613E5A2F01.006070174823.99) request with signalling
LECS EVENT ATM1/0: ilmiDeRegisterAddress: sendSetRequestToILMI failure; interface down ?
LECS EVENT ATM1/0: tearing down all connexions
LECS EVENT ATM1/0: elan 'xxx' LES 47.00918100000000613E5A2F01.006070174821.01 callId 0x60CE0F58 deliberately being disconnected
LECS EVENT ATM1/0: sending RELEASE for call 0x60CE0F58 cause 31
LECS EVENT ATM1/0: elan 'yyy' LES 47.00918100000000613E5A2F01.006070174821.02 callId 0x60CE2104 deliberately being disconnected
LECS EVENT ATM1/0: sending RELEASE for call 0x60CE2104 cause 31
LECS EVENT ATM1/0: elan 'zzz' LES 47.00918100000000613E5A2F01.006070174821.03 callId 0x60CE2DC8 deliberately being disconnected
LECS EVENT ATM1/0: sending RELEASE for call 0x60CE2DC8 cause 31
LECS EVENT ATM1/0: All calls to/from LECSs are being released
LECS EVENT ATM1/0: placed de-register address 0x60EC4F28 (47.007900000000000000000000.00A03E000001.00) request with signalling
LECS EVENT ATM1/0: ilmiDeRegisterAddress: sendSetRequestToILMI failure; interface down ?
LECS EVENT ATM1/0: ATM_RELEASE_COMPLETE received: callId 0x60CE0F58 cause 0
LECS EVENT ATM1/0: call 0x60CE0F58 cleaned up
LECS EVENT ATM1/0: ATM_RELEASE_COMPLETE received: callId 0x60CE2104 cause 0
LECS EVENT ATM1/0: call 0x60CE2104 cleaned up
LECS EVENT ATM1/0: ATM_RELEASE_COMPLETE received: callId 0x60CE2DC8 cause 0
LECS EVENT ATM1/0: call 0x60CE2DC8 cleaned up
LECS EVENT ATM1/0: UNKNOWN/UNSET: signalling DE-registered
LECS EVENT: UNKNOWN/UNSET: signalling DE-registered
LECS EVENT ATM1/0: UNKNOWN/UNSET: signalling DE-registered
LECS EVENT ATM1/0: placed de-register address 0x60E8A824 (47.00918100000000613E5A2F01.006070174823.00) request with signalling
LECS EVENT ATM1/0: ilmiDeRegisterAddress: sendSetRequestToILMI failure; interface down ?
LECS EVENT ATM1/0: placed de-register address 0x60EC5C08 (47.00918100000000613E5A2F01.006070174823.99) request with signalling
LECS EVENT ATM1/0: ilmiDeRegisterAddress: sendSetRequestToILMI failure; interface down ?
LECS EVENT ATM1/0: tearing down all connexions
LECS EVENT ATM1/0: All calls to/from LECSs are being released
LECS EVENT: config server 56 killed

debug lane finder

To display information about the finder internal state machine, use the debug lane finder command in privileged EXEC mode. To disable debugging output, use the no form of this command.

debug lane finder
no debug lane finder
Syntax Description

This command has no arguments or keywords.

Command Modes

Privileged EXEC

Usage Guidelines

The debug lane finder command output is intended to be used primarily by a Cisco technical support representative.

Examples

The following is sample output from the debug lane finder command when an interface with LECS, LES/BUS, and LEC is shut down:

Router# debug lane finder

LECS FINDER ATM1/0.3: user request 1819 of type GET_MASTER_LECS_ADDRESS queued up
LECS FINDER ATM1/0: finder state machine started
LECS FINDER ATM1/0: time to perform a getNext on the ILMI
LECS FINDER ATM1/0: LECS 47.00918100000000613E5A2F01.006070174823.00 deleted
LECS FINDER ATM1/0: ilmi_client_request failed, answering all users
LECS FINDER ATM1/0: answering all requests now
LECS FINDER ATM1/0: responded to user request 1819
LECS FINDER ATM1/0: number of remaining requests still to be processed: 0
LECS FINDER ATM1/0.2: user request 1820 of type GET_MASTER_LECS_ADDRESS queued up
LECS FINDER ATM1/0: finder state machine started
LECS FINDER ATM1/0: time to perform a getNext on the ILMI
LECS FINDER ATM1/0: ilmi_client_request failed, answering all users
LECS FINDER ATM1/0: answering all requests now
LECS FINDER ATM1/0: responded to user request 1820
LECS FINDER ATM1/0: number of remaining requests still to be processed: 0
LECS FINDER ATM1/0.1: user request 1821 of type GET_MASTER_LECS_ADDRESS queued up
LECS FINDER ATM1/0: finder state machine started
LECS FINDER ATM1/0: time to perform a getNext on the ILMI
LECS FINDER ATM1/0: ilmi_client_request failed, answering all users
LECS FINDER ATM1/0: answering all requests now
LECS FINDER ATM1/0: responded to user request 1821
LECS FINDER ATM1/0: number of remaining requests still to be processed: 0

debug lane server

To display information about a LAN Emulation (LANE) server, use the debug lane server command in privileged EXEC mode. To disable debugging output, use the no form of this command.

debug lane server [interface interface]
no debug lane server [interface interface]
Syntax Description

interface interface

(Optional) Limits the debugging output to messages relating to a specific interface or subinterface. If you use this command multiple times with different interfaces, the last interface entered is the one used to filter debugging messages.

Command Modes

Privileged EXEC

Usage Guidelines

The debug lane server command output is intended to be used primarily by a Cisco technical support representative. The debug lane server command can generate a substantial amount of output. Specify a subinterface to decrease the amount of output and focus on the information you need.

Examples

The following is sample output from the debug lane server command when an interface with LECS, LES/BUS, and LEC is shut down:

Router# debug lane server

LES ATM1/0.1: lsv_lecsAccessSigCB called with callId 0x60CE124C, opcode ATM_RELEASE_COMPLETE
LES ATM1/0.1: disconnected from the master LECS
LES ATM1/0.1: should have been connected, will reconnect in 3 seconds
LES ATM1/0.2: lsv_lecsAccessSigCB called with callId 0x60CE29E0, opcode ATM_RELEASE_COMPLETE
LES ATM1/0.2: disconnected from the master LECS
LES ATM1/0.2: should have been connected, will reconnect in 3 seconds
LES ATM1/0.3: lsv_lecsAccessSigCB called with callId 0x60EB1940, opcode ATM_RELEASE_COMPLETE
LES ATM1/0.3: disconnected from the master LECS
LES ATM1/0.3: should have been connected, will reconnect in 3 seconds
LES ATM1/0.2: elan yyy client 1 lost control distribute
LES ATM1/0.2: elan yyy client 1: lsv_kill_client called
LES ATM1/0.2: elan yyy client 1 state change Oper -> Term
LES ATM1/0.3: elan zzz client 1 lost control distribute
LES ATM1/0.3: elan zzz client 1: lsv_kill_client called
LES ATM1/0.3: elan zzz client 1 state change Oper -> Term
LES ATM1/0.2: elan yyy client 1 lost MC forward
LES ATM1/0.2: elan yyy client 1: lsv_kill_client called
LES ATM1/0.3: elan zzz client 1 lost MC forward
LES ATM1/0.3: elan zzz client 1: lsv_kill_client called
LES ATM1/0.1: elan xxx client 1 lost control distribute
LES ATM1/0.1: elan xxx client 1: lsv_kill_client called
LES ATM1/0.1: elan xxx client 1 state change Oper -> Term
LES ATM1/0.1: elan xxx client 1 lost MC forward
LES ATM1/0.1: elan xxx client 1: lsv_kill_client called
LES ATM1/0.2: elan yyy client 1 released control direct
LES ATM1/0.2: elan yyy client 1: lsv_kill_client called
LES ATM1/0.3: elan zzz client 1 released control direct
LES ATM1/0.3: elan zzz client 1: lsv_kill_client called
LES ATM1/0.2: elan yyy client 1 MC forward released
LES ATM1/0.2: elan yyy client 1: lsv_kill_client called
LES ATM1/0.2: elan yyy client 1: freeing client structures
LES ATM1/0.2: elan yyy client 1 unregistered 0060.7017.4820
LES ATM1/0.2: elan yyy client 1 destroyed
LES ATM1/0.3: elan zzz client 1 MC forward released
LES ATM1/0.3: elan zzz client 1: lsv_kill_client called
LES ATM1/0.3: elan zzz client 1: freeing client structures
LES ATM1/0.3: elan zzz client 1 unregistered 0060.7017.4820
LES ATM1/0.3: elan zzz client 1 destroyed
LES ATM1/0.1: elan xxx client 1 released control direct
LES ATM1/0.1: elan xxx client 1: lsv_kill_client called
LES ATM1/0.1: elan xxx client 1 MC forward released
LES ATM1/0.1: elan xxx client 1: lsv_kill_client called
LES ATM1/0.1: elan xxx client 1: freeing client structures
LES ATM1/0.1: elan xxx client 1 unregistered 0060.7017.4820
LES ATM1/0.1: elan xxx client 1 destroyed
LES ATM1/0.1: elan xxx major interface state change
LES ATM1/0.1: cleanupLecsAccess: discarding all validation requests
LES ATM1/0.1: shutting down
LES ATM1/0.1: elan xxx: lsv_kill_lesbus called
LES ATM1/0.1: elan xxx: LES/BUS state change operational -> terminating
LES ATM1/0.1: cleanupLecsAccess: discarding all validation requests
LES ATM1/0.2: elan yyy major interface state change
LES ATM1/0.2: cleanupLecsAccess: discarding all validation requests
LES ATM1/0.2: shutting down
LES ATM1/0.2: elan yyy: lsv_kill_lesbus called
LES ATM1/0.2: elan yyy: LES/BUS state change operational -> terminating
LES ATM1/0.2: cleanupLecsAccess: discarding all validation requests
LES ATM1/0.3: elan zzz major interface state change
LES ATM1/0.3: cleanupLecsAccess: discarding all validation requests
LES ATM1/0.3: shutting down
LES ATM1/0.3: elan zzz: lsv_kill_lesbus called
LES ATM1/0.3: elan zzz: LES/BUS state change operational -> terminating
LES ATM1/0.3: cleanupLecsAccess: discarding all validation requests
LES ATM1/0.1: elan xxx: lsv_kill_lesbus called
LES ATM1/0.1: cleanupLecsAccess: discarding all validation requests
LES ATM1/0.1: elan xxx: lsv_kill_lesbus called
LES ATM1/0.1: cleanupLecsAccess: discarding all validation requests
LES ATM1/0.1: elan xxx: stopped listening on addresses
LES ATM1/0.1: elan xxx: all clients killed
LES ATM1/0.1: elan xxx: multicast groups killed
LES ATM1/0.1: elan xxx: addresses de-registered from ilmi
LES ATM1/0.1: elan xxx: LES/BUS state change terminating -> down
LES ATM1/0.1: elan xxx: administratively down
LES ATM1/0.2: elan yyy: lsv_kill_lesbus called
LES ATM1/0.2: cleanupLecsAccess: discarding all validation requests
LES ATM1/0.2: elan yyy: lsv_kill_lesbus called
LES ATM1/0.2: cleanupLecsAccess: discarding all validation requests
LES ATM1/0.2: elan yyy: stopped listening on addresses
LES ATM1/0.2: elan yyy: all clients killed
LES ATM1/0.2: elan yyy: multicast groups killed
LES ATM1/0.2: elan yyy: addresses de-registered from ilmi
LES ATM1/0.2: elan yyy: LES/BUS state change terminating -> down
LES ATM1/0.2: elan yyy: administratively down
LES ATM1/0.3: elan zzz: lsv_kill_lesbus called
LES ATM1/0.3: cleanupLecsAccess: discarding all validation requests
LES ATM1/0.3: elan zzz: lsv_kill_lesbus called
LES ATM1/0.3: cleanupLecsAccess: discarding all validation requests
LES ATM1/0.3: elan zzz: stopped listening on addresses
LES ATM1/0.3: elan zzz: all clients killed
LES ATM1/0.3: elan zzz: multicast groups killed
LES ATM1/0.3: elan zzz: addresses de-registered from ilmi
LES ATM1/0.3: elan zzz: LES/BUS state change terminating -> down
LES ATM1/0.3: elan zzz: administratively down
LES ATM1/0.3: cleanupLecsAccess: discarding all validation requests
LES ATM1/0.2: cleanupLecsAccess: discarding all validation requests
LES ATM1/0.1: cleanupLecsAccess: discarding all validation requests
debug lane signaling

To display information about LANE Server (LES) and Broadcast and Unknown Server (BUS) switched virtual circuits (SVCs), use the debug lane signaling command in privileged EXEC mode. To disable debugging output, use the no form of this command.

debug lane signaling [interface interface]
no debug lane signaling [interface interface]
Syntax Description

interface interface

(Optional) Limits the debugging output to messages relating to a specific interface or subinterface. If you use this command multiple times with different interfaces, the last interface entered is the one used to filter debugging messages.

Command Modes

Privileged EXEC

Usage Guidelines

The debug lane signaling command output is intended to be used primarily by a Cisco technical support representative. The debug lane signaling command can generate a substantial amount of output. Specify a subinterface to decrease the amount of output and focus on the information you need.

Examples

The following is sample output from the debug lane signaling command when an interface with LECS, LES/BUS, and LEC is shut down:

Router# debug lane signaling

LANE SIG ATM1/0.2: received ATM_RELEASE_COMPLETE callid 0x60EB565C cause 0 lv 0x60E8D348 lvstate LANE_VCC_CONNECTED
LANE SIG ATM1/0.2: lane_sig_mc_release: breaking lv 0x60E8D348 from mcg 0x60E97E84
LANE SIG ATM1/0.2: timer for lv 0x60E8D348 stopped
LANE SIG ATM1/0.2: sent ATM_RELEASE request for lv 0x60E8D468 in state LANE_VCC_CONNECTED
LANE SIG ATM1/0.2: sent ATM_RELEASE request for lv 0x60E8D3D8 in state LANE_VCC_CONNECTED
LANE SIG ATM1/0.2: sent ATM_RELEASE request for lv 0x60E8D2B8 in state LANE_VCC_CONNECTED
LANE SIG ATM1/0.3: received ATM_RELEASE_COMPLETE callid 0x60EB5CA0 cause 0 lv 0x60E8BEF4 lvstate LANE_VCC_CONNECTED
LANE SIG ATM1/0.3: lane_sig_mc_release: breaking lv 0x60E8BEF4 from mcg 0x60E9A37C
LANE SIG ATM1/0.3: timer for lv 0x60E8BEF4 stopped
LANE SIG ATM1/0.3: sent ATM_RELEASE request for lv 0x60E8C014 in state LANE_VCC_CONNECTED
LANE SIG ATM1/0.3: sent ATM_RELEASE request for lv 0x60E8BF84 in state LANE_VCC_CONNECTED
LANE SIG ATM1/0.3: sent ATM_RELEASE request for lv 0x60E8BE64 in state LANE_VCC_CONNECTED
LANE SIG ATM1/0.2: received ATM_RELEASE_COMPLETE callid 0x60EB9040 cause 0 lv 0x60E8D468 lvstate LANE_VCC_DROP_SENT
LANE SIG ATM1/0.2: lane_sig_mc_release: breaking lv 0x60E8D468 from mcg 0x60E97EC8
LANE SIG ATM1/0.2: timer for lv 0x60E8D468 stopped
LANE SIG ATM1/0.3: received ATM_RELEASE_COMPLETE callid 0x60EB97D4 cause 0 lv 0x60E8C014 lvstate LANE_VCC_DROP_SENT
LANE SIG ATM1/0.3: lane_sig_mc_release: breaking lv 0x60E8C014 from mcg 0x60E9A3C0
LANE SIG ATM1/0.3: timer for lv 0x60E8C014 stopped
LANE SIG ATM1/0.1: received ATM_RELEASE_COMPLETE callid 0x60EBCEB8 cause 0 lv 0x60EBBAF0 lvstate LANE_VCC_CONNECTED
LANE SIG ATM1/0.1: lane_sig_mc_release: breaking lv 0x60EBBAF0 from mcg 0x60E8F51C
LANE SIG ATM1/0.1: timer for lv 0x60EBBAF0 stopped
LANE SIG ATM1/0.1: sent ATM_RELEASE request for lv 0x60EBBC10 in state LANE_VCC_CONNECTED
LANE SIG ATM1/0.1: sent ATM_RELEASE request for lv 0x60EBBB80 in state LANE_VCC_CONNECTED
LANE SIG ATM1/0.1: sent ATM_RELEASE request for lv 0x60EBBA60 in state LANE_VCC_CONNECTED
LANE SIG ATM1/0.1: received ATM_RELEASE_COMPLETE callid 0x60EBEB00 cause 0 lv 0x60EBBC10 lvstate LANE_VCC_DROP_SENT
LANE SIG ATM1/0.1: lane_sig_mc_release: breaking lv 0x60EBBC10 from mcg 0x60E8F560
LANE SIG ATM1/0.1: timer for lv 0x60EBBC10 stopped
LANE SIG ATM1/0.2: received ATM_RELEASE_COMPLETE callid 0x60E8B174 cause 0 lv 0x60E8D2B8 lvstate LANE_VCC_RELEASE_SENT
LANE SIG ATM1/0.2: timer for lv 0x60E8D2B8 stopped
LANE SIG ATM1/0.3: received ATM_RELEASE_COMPLETE callid 0x60E8B990 cause 0 lv 0x60E8BE64 lvstate LANE_VCC_RELEASE_SENT
LANE SIG ATM1/0.3: timer for lv 0x60E8BE64 stopped
LANE SIG ATM1/0.2: received ATM_RELEASE_COMPLETE callid 0x60EB7FE0 cause 0 lv 0x60E8D3D8 lvstate LANE_VCC_RELEASE_SENT
LANE SIG ATM1/0.2: timer for lv 0x60E8D3D8 stopped
LANE SIG ATM1/0.3: received ATM_RELEASE_COMPLETE callid 0x60EB8554 cause 0 lv 0x60E8BF84 lvstate LANE_VCC_RELEASE_SENT
LANE SIG ATM1/0.3: timer for lv 0x60E8BF84 stopped
LANE SIG ATM1/0.1: received ATM_RELEASE_COMPLETE callid 0x60EBB6D4 cause 0 lv 0x60EBBA60 lvstate LANE_VCC_RELEASE_SENT
LANE SIG ATM1/0.1: timer for lv 0x60EBBA60 stopped
LANE SIG ATM1/0.1: received ATM_RELEASE_COMPLETE callid 0x60EBE24C cause 0 lv 0x60EBBB80 lvstate LANE_VCC_RELEASE_SENT
LANE SIG ATM1/0.1: timer for lv 0x60EBBB80 stopped
LANE SIG ATM1/0.1: sent ATM_CANCEL_NSAP request for lv 0x0 in state NULL_VCC_POINTER
LANE SIG ATM1/0.1: sent ATM_CANCEL_NSAP request for lv 0x0 in state NULL_VCC_POINTER
LANE SIG ATM1/0.2: sent ATM_CANCEL_NSAP request for lv 0x0 in state NULL_VCC_POINTER
LANE SIG ATM1/0.2: sent ATM_CANCEL_NSAP request for lv 0x0 in state NULL_VCC_POINTER
LANE SIG ATM1/0.3: sent ATM_CANCEL_NSAP request for lv 0x0 in state NULL_VCC_POINTER
LANE SIG ATM1/0.3: sent ATM_CANCEL_NSAP request for lv 0x0 in state NULL_VCC_POINTER
LANE SIG ATM1/0.1: received ATM_CANCEL_NSAP for nsap 00.000000000000050000000000.000000000000.00
LANE SIG ATM1/0.1: received ATM_CANCEL_NSAP for nsap 00.000000000000050000000000.000000000000.00
LANE SIG ATM1/0.2: received ATM_CANCEL_NSAP for nsap 00.000000000000050000000000.000000000000.00
LANE SIG ATM1/0.2: received ATM_CANCEL_NSAP for nsap 00.000000000000050000000000.000000000000.00
LANE SIG ATM1/0.3: received ATM_CANCEL_NSAP for nsap 00.000000000000050000000000.000000000000.00
LANE SIG ATM1/0.3: received ATM_CANCEL_NSAP for nsap 00.000000000000050000000000.000000000000.00
debug lapb

To display all traffic for interfaces using Link Access Procedure, Balanced (LAPB) encapsulation, use the debug lapb command in privileged EXEC mode. To disable debugging output, use the no form of this command.

debug lapb
no debug lapb
Syntax Description

This command has no arguments or keywords.

Command Modes

Privileged EXEC

Usage Guidelines

This command displays information on the X.25 Layer 2 protocol. It is useful to users familiar with the LAPB protocol.

You can use the debug lapb command to determine why X.25 interfaces or LAPB connections are going up and down. It is also useful for identifying link problems, as evidenced when the show interfaces EXEC command displays a high number of rejects or frame errors over the X.25 link.

Caution Because the debug lapb command generates a substantial amount of output, use it when the aggregate of all LAPB traffic on X.25 and LAPB interfaces is fewer than five frames per second.

Examples

The following is sample output from the debug lapb command (the numbers 1 through 7 at the top of the display have been added in order to aid documentation):

1 2 3 4 5 6 7
Serial0: LAPB I CONNECT (5) IFRAME P 2 1
Serial0: LAPB O REJSENT (2) REJ F 3
Serial0: LAPB O REJSENT (5) IFRAME 0 3
Serial0: LAPB I REJSENT (2) REJ (C) 7
Serial0: LAPB I DISCONNECT (2) SABM P
Serial0: LAPB O CONNECT (2) UA F
Serial0: LAPB O CONNECT (5) IFRAME 0 0
Serial0: LAPB T1 CONNECT 357964 0

Each line of output describes a LAPB event. There are two types of LAPB events: frame events (when a frame enters or exits the LAPB) and timer events. In the sample output, the last line describes a timer event; all of the other lines describe frame events. Table 203 describes the first seven fields.

Table 203 debug lapb Field Descriptions

Field

Description

First field (1)

Interface type and unit number reporting the frame event.

Second field (2)

Protocol providing the information.

Third field (3)

Frame event type. Possible values are as follows:

•I—Frame input

•O—Frame output

•T1—T1 timer expired

•T3—Interface outage timer expired

•T4—Idle link timer expired

Fourth field (4)

State of the protocol when the frame event occurred. Possible values are as follows:

•BUSY (RNR frame received)

•CONNECT

•DISCONNECT

•DISCSENT (disconnect sent)

•ERROR (FRMR frame sent)

•REJSENT (reject frame sent)

•SABMSENT (SABM frame sent)

Fifth field (5)

In a frame event, this value is the size of the frame (in bytes). In a timer event, this value is the current timer value (in milliseconds).

Sixth field (6)

In a frame event, this value is the frame type name. Possible values for frame type names are as follows:

•DISC—Disconnect

•DM—Disconnect mode

•FRMR—Frame reject

•IFRAME—Information frame

•ILLEGAL—Illegal LAPB frame

•REJ—Reject

•RNR—Receiver not ready

•RR—Receiver ready

•SABM—Set asynchronous balanced mode

•SABME—Set asynchronous balanced mode, extended

•UA—Unnumbered acknowledgment

In a T1 timer event, this value is the number of retransmissions already attempted.

Seventh field (7)

(This field will not print if the frame control field is required to appear as either a command or a response, and that frame type is correct.)

This field is only present in frame events. It describes the frame type identified by the LAPB address and Poll/Final bit. Possible values are as follows:

•(C)—Command frame

•(R)—Response frame

•P—Command/Poll frame

•F—Response/Final frame

•/ERR—Command/Response type is invalid for the control field. An ?ERR generally means that the data terminal equipment (DTE)/data communications equipment (DCE) assignments are not correct for this link.

•BAD-ADDR—Address field is neither Command nor Response

A timer event only displays the first six fields of debug lapb command output. For frame events, however, the seventh field documents the LAPB control information present in the frame. Depending on the value of the frame type name shown in the sixth field, the seventh field may or may not appear.

After the Poll/Final indicator, depending on the frame type, three different types of LAPB control information can be printed.

For information frames, the value of the N(S) field and the N(R) field will be printed. The N(S) field of an information frame is the sequence number of that frame, so this field will rotate between 0 and 7 for (modulo 8 operation) or 0 and 127 (for modulo 128 operation) for successive outgoing information frames and (under normal circumstances) also will rotate for incoming information frame streams. The N(R) field is a "piggybacked" acknowledgment for the incoming information frame stream; it informs the other end of the link which sequence number is expected next.

RR, RNR, and REJ frames have an N(R) field, so the value of that field is printed. This field has exactly the same significance that it does in an information frame.

For the FRMR frame, the error information is decoded to display the rejected control field, V(R) and V(S) values, the Response/Command flag, and the error flags WXYZ.

In the following example, the output shows an idle link timer action (T4) where the timer expires twice on an idle link, with the value of T4 set to five seconds:

Serial2: LAPB T4 CONNECT 255748
Serial2: LAPB O CONNECT (2) RR P 5
Serial2: LAPB I CONNECT (2) RR F 5
Serial2: LAPB T4 CONNECT 260748
Serial2: LAPB O CONNECT (2) RR P 5
Serial2: LAPB I CONNECT (2) RR F 5

The next example shows an interface outage timer expiration (T3):

Serial2: LAPB T3 DISCONNECT 273284

The following example output shows an error condition when no DCE to DTE connection exists. Note that if a frame has only one valid type (for example, a SABM can only be a command frame), a received frame that has the wrong frame type will be flagged as a receive error (R/ERR in the following output). This feature makes misconfigured links (DTE-DTE or DCE-DCE) easy to spot. Other, less common errors will be highlighed too, such as a too-short or too-long frame, or an invalid address (neither command nor response).

Serial2: LAPB T1 SABMSENT 1026508 1
Serial2: LAPB O SABMSENT (2) SABM P
Serial2: LAPB I SABMSENT (2) SABM (R/ERR)
Serial2: LAPB T1 SABMSENT 1029508 2
Serial2: LAPB O SABMSENT (2) SABM P
Serial2: LAPB I SABMSENT (2) SABM (R/ERR)

The output in the next example shows the router is misconfigured and has a standard (modulo 8) interface connected to an extended (modulo 128) interface. This condition is indicated by the SABM balanced mode and SABME balanced mode extended messages appearing on the same interface.

Serial2: LAPB T1 SABMSENT 1428720 0
Serial2: LAPB O SABMSENT (2) SABME P
Serial2: LAPB I SABMSENT (2) SABM P
Serial2: LAPB T1 SABMSENT 1431720 1
Serial2: LAPB O SABMSENT (2) SABME P
Serial2: LAPB I SABMSENT (2) SABM P
debug lapb-ta

To display debugging messages for Link Access Procedure, Balanced-Terminal Adapter (LAPB-TA), use the debug lapb-ta command in privileged EXEC mode. To disable debugging output, use the no form of this command.

debug lapb-ta [error | event | traffic]
no debug lapb-ta [error | event | traffic]
Syntax Description

error

(Optional) Displays LAPB-TA errors.

event

(Optional) Displays LAPB-TA normal events.

traffic

(Optional) Displays LAPB-TA in/out traffic data.

Defaults

Debugging for LAPB-TA is not enabled.

Command Modes

Privileged EXEC

Command History

Release

Modification

12.0(4)T

This command was introduced.

Examples

The following is sample output from the debug lapb-ta command with the error, event, and traffic keywords activated:

Router# debug lapb-ta error

LAPB-TA error debugging is on

Router# debug lapb-ta event

LAPB-TA event debugging is on

Router# debug lapb-ta traffic

LAPB-TA traffic debugging is on

Mar 9 12:11:36.464:LAPB-TA:Autodetect trying to detect LAPB on
BR3/0:1
Mar 9 12:11:36.464: sampled pkt: 2 bytes: 1 3F.. match
Mar 9 12:11:36.468:LAPBTA:get_ll_config:BRI3/0:1
Mar 9 12:11:36.468:LAPBTA:line 130 allocated for BR3/0:1
Mar 9 12:11:36.468:LAPBTA:process 79
Mar 9 12:11:36.468:BR3/0:1:LAPB-TA started
Mar 9 12:11:36.468:LAPBTA:service change:LAPB physical layer up,
context 6183E144 interface up, protocol down
Mar 9 12:11:36.468:LAPBTA:service change:, context 6183E144 up
Mar 9 12:11:36.468:LAPB-TA:BR3/0:1, 44 sent
2d14h:%LINEPROTO-5-UPDOWN:Line protocol on Interface BRI3/0:1, changed state to up
2d14h:%ISDN-6-CONNECT:Interface BRI3/0:1 is now connected to 60213
Mar 9 12:11:44.508:LAPB-TA:BR3/0:1, 1 rcvd
Mar 9 12:11:44.508:LAPB-TA:BR3/0:1, 3 sent
Mar 9 12:11:44.700:LAPB-TA:BR3/0:1, 1 rcvd
Mar 9 12:11:44.700:LAPB-TA:BR3/0:1, 3 sent
Mar 9 12:11:44.840:LAPB-TA:BR3/0:1, 1 rcvd
Mar 9 12:11:44.840:LAPB-TA:BR3/0:1, 14 sent
Mar 9 12:11:45.852:LAPB-TA:BR3/0:1, 1 rcvd
Mar 9 12:11:46.160:LAPB-TA:BR3/0:1, 2 rcvd
Mar 9 12:11:47.016:LAPB-TA:BR3/0:1, 1 rcvd
Mar 9 12:11:47.016:LAPB-TA:BR3/0:1, 10 sent
debug lat packet

To display information on all local-area transport (LAT) events, use the debug lat packet command in privileged EXEC mode. To disable debugging output, use the no form of this command.

debug lat packet
no debug lat packet
Syntax Description

This command has no arguments or keywords.

Command Modes

Privileged EXEC

Usage Guidelines

For each datagram (packet) received or sent, a message is logged to the console.

Caution This command severely impacts LAT performance and is intended for troubleshooting use only.

Examples

The following is sample output from the debug lat packet command:

Router# debug lat packet

LAT: I int=Ethernet0, src=0000.0c01.0509, dst=0900.2b00.000f, type=0, M=0, R=0
LAT: I int=Ethernet0, src=0800.2b11.2d13, dst=0000.0c01.7876, type=A, M=0, R=0
LAT: O dst=0800.2b11.2d13, int=Ethernet0, type= A, M=0, R=0, len= 20, next 0 ref 1

The second line of output describes a packet that is input to the router. Table 204 describes the fields in this line.

Table 204 debug lat packet Field Descriptions

Field

Description

LAT:

Indicates that this display shows LAT debugging output.

I

Indicates that this line of output describes a packet that is input to the router (I) or output from the router (O).

int = Ethernet0

Indicates the interface on which the packet event took place.

src = 0800.2b11.2d13

Indicates the source address of the packet.

dst=0000.0c01.7876

Indicates the destination address of the packet.

type=A

Indicates the message type (in hexadecimal notation). Possible values are as follows:

•0 = Run Circuit

•1 = Start Circuit

•2 = Stop Circuit

•A = Service Announcement

•C = Command

•D = Status

•E = Solicit Information

•F = Response Information

The third line of output describes a packet that is output from the router. Table 205 describes the last three fields in this line.

Table 205 debug lat packet Field Descriptions

Field

Description

len= 20

Indicates the length (in hexadecimal notation) of the packet (in bytes).

next 0

Indicates the link on the transmit queue.

ref 1

Indicates the count of packet users.

debug lex rcmd

To debug LAN Extender remote commands, use the debug lex rcmd command in privileged EXEC mode. To disable debugging output, use the no form of this command.

debug lex rcmd
no debug lex rcmd
Syntax Description

This command has no arguments or keywords.

Command Modes

Privileged EXEC

Examples

The following is sample output from the debug lex rcmd command:

Router# debug lex rcmd

LEX-RCMD: "shutdown" command received on unbound serial interface- Serial0
LEX-RCMD: Lex0: "inventory" command received
Rcvd rcmd: FF 03 80 41 41 13 00 1A 8A 00 00 16 01 FF 00 00
Rcvd rcmd: 00 02 00 00 07 5B CD 15 00 00 0C 01 15 26
LEX-RCMD: ACK or response received on Serial0 without a corresponding ID
LEX-RCMD: REJ received
LEX-RCMD: illegal CODE field received in header: <number>
LEX-RCMD: illegal length for Lex0: "lex input-type-list"
LEX-RCMD: Lex0 is not bound to a serial interface
LEX-RCMD: encapsulation failure
LEX-RCMD: timeout for Lex0: "lex priority-group" command
LEX-RCMD: re-transmitting Lex0: "lex priority-group" command
LEX-RCMD: lex_setup_and_send called with invalid parameter
LEX-RCMD: bind occurred on shutdown LEX interface
LEX-RCMD: Serial0- No free Lex interface found with negotiated MAC address 0000.0c00.d8db
LEX-RCMD: No active Lex interface found for unbind

The following output indicates that a LAN Extender remote command packet was received on a serial interface that is not bound to a LAN Extender interface:

LEX-RCMD: "shutdown" command received on unbound serial interface- Serial0

This message can occur for any of the LAN Extender remote commands. Possible causes of this message are as follows:

•FLEX state machine software error

•Serial line momentarily goes down, which is detected by the host but not by FLEX

The following output indicates that a LAN Extender remote command response has been received. The hexadecimal values are for internal use only.

LEX-RCMD: Lex0: "inventory" command received
Rcvd rcmd: FF 03 80 41 41 13 00 1A 8A 00 00 16 01 FF 00 00
Rcvd rcmd: 00 02 00 00 07 5B CD 15 00 00 0C 01 15 26

The following output indicates that when the host router originates a LAN Extender remote command to FLEX, it generates an 8-bit identifier that is used to associate a command with its corresponding response:

LEX-RCMD: ACK or response received on Serial0 without a corresponding ID

This message could be displayed for any of the following reasons:

•FLEX was busy at the time that the command arrived and could not send an immediate response. The command timed out on the host router and then FLEX finally sent the response.

•Transmission error.

•Software error.

Possible responses to Config-Request are Config-ACK, Config-NAK, and Config-Rej. The following output shows that some of the options in the Config-Request are not recognizable or are not acceptable to FLEX due to transmission errors or software errors:

LEX-RCMD: REJ received

The following output shows that a LAN Extender remote command response was received but that the CODE field in the header was incorrect:

LEX-RCMD: illegal CODE field received in header: <number>

The following output indicates that a LAN Extender remote command response was received but that it had an incorrect length field. This message can occur for any of the LAN Extender remote commands.

LEX-RCMD: illegal length for Lex0: "lex input-type-list"

The following output shows that a host router was about to send a remote command when the serial link went down:

LEX-RCMD: Lex0 is not bound to a serial interface

The following output shows that the serial encapsulation routine of the interface failed to encapsulate the remote command datagram because the LEX-NCP was not in the OPEN state. Due to the way the PPP state machine is implemented, it is normal to see a single encapsulation failure for each remote command that gets sent at bind time.

LEX-RCMD: encapsulation failure

The following output shows that the timer expired for the given remote command without having received a response from the FLEX device. This message can occur for any of the LAN Extender remote commands.

LEX-RCMD: timeout for Lex0: "lex priority-group" command

This message could be displayed for any of the following reasons:

•FLEX too busy to respond

•Transmission failure

•Software error

The following output indicates that the host is resending the remote command after a timeout:

LEX-RCMD: re-transmitting Lex0: "lex priority-group" command

The following output indicates that an illegal parameter was passed to the lex_setup_and_send routine. This message could be displayed due to a host software error.

LEX-RCMD: lex_setup_and_send called with invalid parameter

The following output is informational and shows when a bind occurs on a shutdown interface:

LEX-RCMD: bind occurred on shutdown LEX interface

The following output shows that the LEX-NCP reached the open state and a bind operation was attempted with the FLEX's MAC address, but no free LAN Extender interfaces were found that were configured with that MAC address. This output can occur when the network administrator does not configure a LAN Extender interface with the correct MAC address.

LEX-RCMD: Serial0- No free Lex interface found with negotiated MAC address 0000.0c00.d8db

The following output shows that the serial line that was bound to the LAN Extender interface went down and the unbind routine was called, but when the list of active LAN Extender interfaces was searched, the LAN Extender interface corresponding to the serial interface was not found. This output usually occurs because of a host software error.

LEX-RCMD: No active Lex interface found for unbind

debug link monitor

To display the statistics of the executing process, use the debug link monitor command in privileged EXEC mode. To disable debugging output, use the no form of this command.

debug link monitor
no debug link monitor
Syntax Description

This command has no arguments or keywords.

Defaults

No default behavior or values

Command Modes

Privileged EXEC

Command History

Release

Modification

12.3(1)

This command was introduced.

Usage Guidelines

This command is used to display the statistics, which are used for debugging the status of the various conditions occurred during execution of the monitoring process.

Examples

The following example enables link monitoring statistics:

Router# debug link monitor

%DEBUG-ENABLED Error Rate Link Monitor

The following example disables link monitoring statistics:

Router# no debug link monitor

%DEBUG-DISABLED Error Rate Link Monitor
Related Commands

Command

Description

debug all

Enables debugging for link monitoring.

no debug all

Disables debugging for link monitoring.

clear counters

Clears show interface counters on all interfaces.

show link monitor debug

Show link monitor error statistics.

debug list

To filter debugging information on a per-interface or per-access list basis, use the debug list command in privileged EXEC mode. To disable debugging output, use the no form of this command.

debug list [list] [interface]
no debug list [list] [interface]
Syntax Description

list

(Optional) An access list number in the range from 1100 to 1199.

interface

(Optional) The interface type. Allowed values are the following:

•channel—IBM Channel interface

•ethernet—IEEE 802.3

•fddi—ANSI X3T9.5

•null—Null interface

•serial—Serial

•tokenring—IEEE 802.5

•tunnel—Tunnel interface

Command Modes

Privileged EXEC

Usage Guidelines

The debug list command is used with other debug commands for specific protocols and interfaces to filter the amount of debug information that is displayed. In particular, this command is designed to filter specific physical unit (PU) output from bridging protocols. The debug list command is supported with the following commands:

•debug llc2 errors

•debug llc2 packets

•debug llc2 state

•debug rif

•debug sdlc

•debug token ring

Note All debug commands that support access list filtering use access lists in the range from 1100 to 1199. The access list numbers shown in the examples are merely samples of valid numbers.

Examples

To use the debug list command on only the first of several Logical Link Control, type 2 (LLC2) connections, use the show llc2 command to display the active connections:

Router# show llc2

SdllcVirtualRing2008 DTE: 4000.2222.22c7 4000.1111.111c 04 04 state NORMAL
SdllcVirtualRing2008 DTE: 4000.2222.22c8 4000.1111.1120 04 04 state NORMAL
SdllcVirtualRing2008 DTE: 4000.2222.22c1 4000.1111.1104 04 04 state NORMAL

Next, configure an extended bridging access list, numbered 1103, for the connection you want to filter:

access-list 1103 permit 4000.1111.111c 0000.0000.0000 4000.2222.22c7 0000.0000.0000 0xC 2 eq 0x404

The convention for the LLC debug list command filtering is to use dmac = 6 bytes, smac = 6 bytes, dsap_offset = 12, and ssap_offset = 13.

Finally, you invoke the following debug commands:

Router# debug list 1103

Router# debug llc2 packet

LLC2 Packets debugging is on
for access list: 1103

To use the debug list command for Synchronous Data Link Control (SDLC) connections, with the exception of address 04, create access list 1102 to deny the specific address and permit all others:

access-list 1102 deny 0000.0000.0000 0000.0000.0000 0000.0000.0000 0000.0000.0000 0xC 1 eq 0x4
access-list 1102 permit 0000.0000.0000 0000.0000.0000 0000.0000.0000 0000.0000.0000

The convention is to use dmac = 0.0.0, smac = 0.0.0, and sdlc_frame_offset = 12.

Invoke the following debug commands:

Router# debug list 1102

Router# debug sdlc

SDLC link debugging is on
for access list: 1102

To enable SDLC debugging (or debugging for any of the other supported protocols) for a specific interface rather than for all interfaces on a router, use the following commands:

Router# debug list serial 0

Router# debug sdlc

SDLC link debugging is on
for interface: Serial0

To enable Token Ring debugging between two MAC address, 0000.3018.4acd and 0000.30e0.8250, configure an extended bridging access list 1106:

access-list 1106 permit 0000.3018.4acd 8000.0000.0000 0000.30e0.8250 8000.0000.0000
access-list 1106 permit 0000.30e0.8250 8000.0000.0000 0000.3018.4acd 8000.0000.0000

Invoke the following debug commands:

Router# debug list 1106

Router# debug token ring

Token Ring Interface debugging is on
for access list: 1106

To enable routing information field (RIF) debugging for a single MAC address, configure an access list 1109:

access-list 1109 permit permit 0000.0000.0000 ffff.ffff.ffff 4000.2222.22c6 0000.0000.0000

Invoke the following debug commands:

Router# debug list 1109
Router# debug rif

RIF update debugging is on
for access list: 1109
Related Commands

Command

Description

debug llc2 errors

Displays LLC2 protocol error conditions or unexpected input.

debug llc2 packet

Displays all input and output from the LLC2 protocol stack.

debug llc2 state

Displays state transitions of the LLC2 protocol.

debug rif

Displays information on entries entering and leaving the RIF cache.

debug rtsp

Displays information on SDLC frames received and sent by any router serial interface involved in supporting SDLC end station functions.

debug token ring

Displays messages about Token Ring interface activity.

debug llc2 dynwind

To display changes to the dynamic window over Frame Relay, use the debug llc2 dynwind command in privileged EXEC mode. To disable debugging output, use the no form of this command.

debug llc2 dynwind
no debug llc2 dynwind
Syntax Description

This command has no arguments or keywords.

Command Modes

Privileged EXEC

Examples

The following is sample output from the debug llc2 dynwind command:

Router# debug llc2 dynwind

LLC2/DW: BECN received! event REC_I_CMD, Window size reduced to 4
LLC2/DW: 1 consecutive I-frame(s) received without BECN
LLC2/DW: 2 consecutive I-frame(s) received without BECN
LLC2/DW: 3 consecutive I-frame(s) received without BECN
LLC2/DW: 4 consecutive I-frame(s) received without BECN
LLC2/DW: 5 consecutive I-frame(s) received without BECN
LLC2/DW: Current working window size is 5

In this example, the router receives a backward explicit congestion notification (BECN) and reduces the window size to 4. After receiving five consecutive I frames without a BECN, the router increases the window size to 5.

Related Commands

Command

Description

debug llc2 errors

Displays LLC2 protocol error conditions or unexpected input.

debug llc2 packet

Displays all input and output from the LLC2 protocol stack.

debug llc2 state

Displays state transitions of the LLC2 protocol.

debug llc2 errors

To display Logical Link Control, type 2 (LLC2) protocol error conditions or unexpected input, use the debug llc2 errors command in privileged EXEC mode. To disable debugging output, use the no form of this command.

debug llc2 errors
no debug llc2 errors
Syntax Description

This command has no arguments or keywords.

Command Modes

Privileged EXEC

Examples

The following is sample output from the debug llc2 errors command from a router ignoring an incorrectly configured device:

Router# debug llc2 errors

LLC: admstate: 4000.1014.0001 0000.0000.0000 04 04 REC_RR_RSP
LLC: admstate: 4000.1014.0001 0000.0000.0000 04 04 REC_RR_RSP
LLC: admstate: 4000.1014.0001 0000.0000.0000 04 04 REC_RR_RSP
LLC: admstate: 4000.1014.0001 0000.0000.0000 04 04 REC_RR_RSP
LLC: admstate: 4000.1014.0001 0000.0000.0000 04 04 REC_RR_RSP
LLC: admstate: 4000.1014.0001 0000.0000.0000 04 04 REC_RR_RSP

Each line of output contains the remote MAC address, the local MAC address, the remote service access point (SAP), and the local SAP. In this example, the router receives unsolicited RR frames marked as responses.

Related Commands

Command

Description

debug list

Filters debugging information on a per-interface or per-access list basis.

debug llc2 dynwind

Displays changes to the dynamic window over Frame Relay.

debug llc2 packet

Displays all input and output from the LLC2 protocol stack.

debug llc2 state

Displays state transitions of the LLC2 protocol.

debug llc2 packet

To display all input and output from the Logical Link Control, type 2 (LLC2) protocol stack, use the debug llc2 packet command in privileged EXEC mode. To disable debugging output, use the no form of this command.

debug llc2 packet
no debug llc2 packet
Syntax Description

This command has no arguments or keywords.

Command Modes

Privileged EXEC

Usage Guidelines

This command also displays information about some error conditions as well as internal interactions between the Common Link Services (CLS) layer and the LLC2 layer.

Examples

The following is sample output from the debug llc2 packet command from the router sending ping data back and forth to another router:

Router# debug llc2 packet

LLC: llc2_input
401E54F0: 10400000 .@..
401E5500: 303A90CF 0006F4E1 2A200404 012B5E 0:.O..ta* ...+
LLC: i REC_RR_CMD N(R)=21 p/f=1
LLC: 0006.f4e1.2a20 0000.303a.90cf 04 04 NORMAL REC_RR_CMD (3)
LLC (rs): 0006.f4e1.2a20 0000.303a.90cf 04 04 REC_RR_CMD N(R)=42
LLC: 0006.f4e1.2a20 0000.303a.90cf 04 04 txmt RR_RSP N(R)=20 p/f=1
LLC: llc_sendframe
401E5610: 0040 0006F4E1 2A200000 .@..ta* ..
401E5620: 303A90CF 04050129 00 N 0:.O...). 2012
LLC: llc_sendframe
4022E3A0: 0040 0006F4E1 .@..ta
4022E3B0: 2A200000 303A90CF 04042A28 2C000202 * ..0:.O..*(,...
4022E3C0: 00050B90 A02E0502 FF0003D1 004006C1 .... ......Q.@.A
4022E3D0: D7C9D5C 0.128
C400130A C1D7D7D5 4BD5F2F0 WIUGD...AWWUKUrp
4022E3E0: F1F30000 011A6071 00010860 D7027000 qs....`q...`W.p.
4022E3F0: 00003B00 1112FF01 03000243 6973636F ..;........Cisco
4022E400: 20494F53 69 IOSi
LLC: 0006.f4e1.2a20 0000.303a.90cf 04 04 txmt I N(S)=21 N(R)=20 p/f=0 size=90
LLC: llc2_input
401E5620: 10400000 303A90CF .@..0:.O
401E5630: 0006F4E1 2A200404 282C2C00 02020004 ..ta* ..(,,.....
401E5640: 03902000 1112FF01 03000243 6973636F .. ........Cisco
401E5650: 20494F53 A0 IOS
LLC: i REC_I_CMD N(R)=22 N(S)=20 V(R)=20 p/f=0
LLC: 0006.f4e1.2a20 0000.303a.90cf 04 04 NORMAL REC_I_CMD (1)
LLC (rs): 0006.f4e1.2a20 0000.303a.90cf 04 04 REC_I_CMD N(S)=20 V(R)=20
LLC (rs): 0006.f4e1.2a20 0000.303a.90cf 04 04 REC_I_CMD N(R)=44
LLC: INFO: 0006.f4e1.2a20 0000.303a.90cf 04 04 v(r) 20

The first three lines indicate that the router has received some input from the link:

LLC: llc2_input
401E54F0: 10400000 .@..
401E5500: 303A90CF 0006F4E1 2A200404 012B5E 0:.O..ta* ...+

The next line indicates that this input was an RR command with the poll bit set. The other router has received sequence number 21 and is waiting for the final bit.

LLC: i REC_RR_CMD N(R)=21 p/f=1

The next two lines contain the MAC addresses of the sender and receiver, and the state of the router when it received this frame:

LLC: 0006.f4e1.2a20 0000.303a.90cf 04 04 NORMAL REC_RR_CMD (3)
LLC (rs): 0006.f4e1.2a20 0000.303a.90cf 04 04 REC_RR_CMD N(R)=42

The next four lines indicate that the router is sending a response with the final bit set:

LLC: 0006.f4e1.2a20 0000.303a.90cf 04 04 txmt RR_RSP N(R)=20 p/f=1
LLC: llc_sendframe
401E5610: 0040 0006F4E1 2A200000 .@..ta* ..
401E5620: 303A90CF 04050129 00 N 0:.O...). 2012
Related Commands

Command

Description

debug list

Filters debugging information on a per-interface or per-access list basis.

debug llc2 dynwind

Displays changes to the dynamic window over Frame Relay.

debug llc2 errors

Displays LLC2 protocol error conditions or unexpected input.

debug llc2 state

Displays state transitions of the LLC2 protocol.

debug llc2 state

To display state transitions of the Logical Link Control, type 2 (LLC2) protocol, use the debug llc2 state command in privileged EXEC mode. To disable debugging output, use the no form of this command.

debug llc2 state
no debug llc2 state
Syntax Description

This command has no arguments or keywords.

Command Modes

Privileged EXEC

Usage Guidelines

Refer to the ISO/IEC standard 8802-2 for definitions and explanations of debug llc2 state command output.

Examples

The following is sample output from the debug llc2 state command when a router disables and enables an interface:

Router# debug llc2 state

LLC (stsw): 0006.f4e1.2a20 0000.303a.90cf 04 04, NORMAL -> AWAIT (P_TIMER_EXP)
LLC(rs): 0006.f4e1.2a20 0000.303a.90cf 04 04, AWAIT -> D_CONN (P_TIMER_EXP)
LLC: cleanup 0006.f4e1.2a20 0000.303a.90cf 04 04, UNKNOWN (17)
LLC (stsw): 0006.f4e1.2a20 0000.303a.90cf 04 04, ADM -> SETUP (CONN_REQ)
LLC: normalstate: set_local_busy 0006.f4e1.2a20 0000.303a.90cf 04 04
LLC (stsw): 0006.f4e1.2a20 0000.303a.90cf 04 04, NORMAL -> BUSY (SET_LOCAL_BUSY)
LLC: Connection established: 0006.f4e1.2a20 0000.303a.90cf 04 04, success
LLC (stsw): 0006.f4e1.2a20 0000.303a.90cf 04 04, SETUP -> BUSY (SET_LOCAL_BUSY)
LLC: busystate: 0006.f4e1.2a20 0000.303a.90cf 04 04 local busy cleared
LLC (stsw): 0006.f4e1.2a20 0000.303a.90cf 04 04, BUSY -> NORMAL (CLEAR_LOCAL_BUSY)
Related Commands

Command

Description

debug list

Filters debugging information on a per-interface or per-access list basis.

debug llc2 dynwind

Displays changes to the dynamic window over Frame Relay.

debug llc2 errors

Displays LLC2 protocol error conditions or unexpected input.

debug llc2 packet

Displays all input and output from the LLC2 protocol stack.

debug lnm events

To display any unusual events that occur on a Token Ring network, use the debug lnm events command in privileged EXEC mode. To disable debugging output, use the no form of this command.

debug lnm events
no debug lnm events
Syntax Description

This command has no arguments or keywords.

Command Modes

Privileged EXEC

Usage Guidelines

Unusual events include stations reporting errors or error thresholds being exceeded.

Examples

The following is sample output from the debug lnm events command:

Router# debug lnm events

IBMNM3: Adding 0000.3001.1166 to error list
IBMNM3: Station 0000.3001.1166 going into preweight condition
IBMNM3: Station 0000.3001.1166 going into weight condition
IBMNM3: Removing 0000.3001.1166 from error list
LANMGR0: Beaconing is present on the ring
LANMGR0: Ring is no longer beaconing
IBMNM3: Beaconing, Postmortem Started
IBMNM3: Beaconing, heard from 0000.3000.1234
IBMNM3: Beaconing, Postmortem Next Stage
IBMNM3: Beaconing, Postmortem Finished

The following message indicates that station 0000.3001.1166 reported errors and has been added to the list of stations reporting errors. This station is located on Ring 3.

IBMNM3: Adding 0000.3001.1166 to error list

The following message indicates that station 0000.3001.1166 has passed the "early warning" threshold for error counts:

IBMNM3: Station 0000.3001.1166 going into preweight condition

The following message indicates that station 0000.3001.1166 is experiencing a severe number of errors:

IBMNM3: Station 0000.3001.1166 going into weight condition

The following message indicates that the error counts for station 0000.3001.1166 have all decayed to zero, so this station is being removed from the list of stations that have reported errors:

IBMNM3: Removing 0000.3001.1166 from error list

The following message indicates that Ring 0 has entered failure mode. This ring number is assigned internally.

LANMGR0: Beaconing is present on the ring

The following message indicates that Ring 0 is no longer in failure mode. This ring number is assigned internally.

LANMGR0: Ring is no longer beaconing

The following message indicates that the router is beginning its attempt to determine whether any stations left the ring during the automatic recovery process for the last beaconing failure. The router attempts to contact stations that were part of the fault domain to detect whether they are still operating on the ring.

IBMNM3: Beaconing, Postmortem Started

The following message indicates that the router is attempting to determine whether any stations left the ring during the automatic recovery process for the last beaconing failure. It received a response from station 0000.3000.1234, one of the two stations in the fault domain.

IBMNM3: Beaconing, heard from 0000.3000.1234

The following message indicates that the router is attempting to determine whether any stations left the ring during the automatic recovery process for the last beaconing failure. It is initiating another attempt to contact the two stations in the fault domain.

IBMNM3: Beaconing, Postmortem Next Stage

The following message indicates that the router has attempted to determine whether any stations left the ring during the automatic recovery process for the last beaconing failure. It has successfully heard back from both stations that were part of the fault domain.

IBMNM3: Beaconing, Postmortem Finished

Explanations follow for other messages that the debug lnm events command can generate.

The following message indicates that the router is out of memory:

LANMGR: memory request failed, find_or_build_station()

The following message indicates that Ring 3 is experiencing a large number of errors that cannot be attributed to any individual station:

IBMNM3: Non-isolating error threshold exceeded

The following message indicates that a station (or stations) on Ring 3 is receiving frames faster than they can be processed:

IBMNM3: Adapters experiencing congestion

The following message indicates that the beaconing has lasted for over 1 minute and is considered a "permanent" error:

IBMNM3: Beaconing, permanent

The following message indicates that the beaconing lasted for less than 1 minute. The router is attempting to determine whether either station in the fault domain left the ring.

IBMNM: Beaconing, Destination Started

In the preceding line of output, the following can replace "Started": "Next State," "Finished," "Timed out," and "Cannot find station n."

debug lnm llc

To display all communication between the router/bridge and the LAN Network Managers (LNMs) that have connections to it, use the debug lnm llc command in privileged EXEC mode. To disable debugging output, use the no form of this command.

debug lnm llc
no debug lnm llc
Syntax Description

This command has no arguments or keywords.

Command Modes

Privileged EXEC

Usage Guidelines

One line is displayed for each message sent or received.

Examples

The following is sample output from the debug lnm llc command:

Router# debug lnm llc

IBMNM: Received LRM Set Reporting Point frame from 1000.5ade.0d8a.
IBMNM: found bridge: 001-2-00A, addresses: 0000.3040.a630 4000.3040.a630
IBMNM: Opening connection to 1000.5ade.0d8a on TokenRing0
IBMNM: Sending LRM LAN Manager Accepted to 1000.5ade.0d8a on link 0.
IBMNM: sending LRM New Reporting Link Established to 1000.5a79.dbf8 on link 1.
IBMNM: Determining new controlling LNM
IBMNM: Sending Report LAN Manager Control Shift to 1000.5ade.0d8a on link 0.
IBMNM: Sending Report LAN Manager Control Shift to 1000.5a79.dbf8 on link 1.

IBMNM: Bridge 001-2-00A received Request Bridge Status from 1000.5ade.0d8a.
IBMNM: Sending Report Bridge Status to 1000.5ade.0d8a on link 0.
IBMNM: Bridge 001-2-00A received Request REM Status from 1000.5ade.0d8a.
IBMNM: Sending Report REM Status to 1000.5ade.0d8a on link 0.
IBMNM: Bridge 001-2-00A received Set Bridge Parameters from 1000.5ade.0d8a.
IBMNM: Sending Bridge Parameters Set to 1000.5ade.0d8a on link 0.
IBMNM: sending Bridge Params Changed Notification to 1000.5a79.dbf8 on link 1.
IBMNM: Bridge 001-2-00A received Set REM Parameters from 1000.5ade.0d8a.
IBMNM: Sending REM Parameters Set to 1000.5ade.0d8a on link 0.
IBMNM: sending REM Parameters Changed Notification to 1000.5a79.dbf8 on link 1.
IBMNM: Bridge 001-2-00A received Set REM Parameters from 1000.5ade.0d8a.
IBMNM: Sending REM Parameters Set to 1000.5ade.0d8a on link 0.
IBMNM: sending REM Parameters Changed Notification to 1000.5a79.dbf8 on link 1.
IBMNM: Received LRM Set Reporting Point frame from 1000.5ade.0d8a.
IBMNM: found bridge: 001-1-00A, addresses: 0000.3080.2d79 4000.3080.2d7

As the output indicates, the debug lnm llc command output can vary somewhat in format.

Table 206 describes the significant fields shown in the display.

Table 206 debug lnm llc Field Descriptions

Field

Description

IBMNM:

Displays LLC-level debugging information.

Received

Router received a frame. The other possible value is Sending, to indicate that the router is sending a frame.

LRM

The function of the LLC-level software that is communicating as follows:

•CRS—Configuration Report Server

•LBS—LAN Bridge Server

•LRM—LAN Reporting Manager

•REM—Ring Error Monitor

•RPS—Ring Parameter Server

•RS—Ring Station

Set Reporting Point

Name of the specific frame that the router sent or received. Possible values include the following:

•Bridge Counter Report

•Bridge Parameters Changed Notification

•Bridge Parameters Set

•CRS Remove Ring Station

•CRS Report NAUN Change

•CRS Report Station Information

•CRS Request Station Information

•CRS Ring Station Removed

•LRM LAN Manager Accepted

•LRM Set Reporting Point

•New Reporting Link Established

•REM Forward MAC Frame

•REM Parameters Changed Notification

•REM Parameters Set

•Report Bridge Status

•Report LAN Manager Control Shift

•Report REM Status

•Request Bridge Status

•Request REM Status

•Set Bridge Parameters

•Set REM Parameters

from 1000.5ade.0d8a

If the router has received the frame, this address is the source address of the frame. If the router is sending the frame, this address is the destination address of the frame.

The following message indicates that the lookup for the bridge with which the LAN Manager was requesting to communicate was successful:

IBMNM: found bridge: 001-2-00A, addresses: 0000.3040.a630 4000.3040.a630

The following message indicates that the connection is being opened:

IBMNM: Opening connection to 1000.5ade.0d8a on TokenRing0

The following message indicates that a LAN Manager has connected or disconnected from an internal bridge and that the router computes which LAN Manager is allowed to change parameters:

IBMNM: Determining new controlling LNM

The following line of output indicates which bridge in the router is the destination for the frame:

IBMNM: Bridge 001-2-00A received Request Bridge Status from 1000.5ade.0d8a.

debug lnm mac

To display all management communication between the router/bridge and all stations on the local Token Rings, use the debug lnm mac command in privileged EXEC mode. To disable debugging output, use the no form of this command.

debug lnm mac
no debug lnm mac
Syntax Description

This command has no arguments or keywords.

Command Modes

Privileged EXEC

Usage Guidelines

One line is displayed for each message sent or received.

Examples

The following is sample output from the debug lnm mac command:

Router# debug lnm mac

LANMGR0: RS received request address from 4000.3040.a670.
LANMGR0: RS sending report address to 4000.3040.a670.
LANMGR0: RS received request state from 4000.3040.a670.
LANMGR0: RS sending report state to 4000.3040.a670.
LANMGR0: RS received request attachments from 4000.3040.a670.
LANMGR0: RS sending report attachments to 4000.3040.a670.
LANMGR2: RS received ring purge from 0000.3040.a630.
LANMGR2: CRS received report NAUN change from 0000.3040.a630.
LANMGR2: RS start watching ring poll.
LANMGR0: CRS received report NAUN change from 0000.3040.a630.
LANMGR0: RS start watching ring poll.
LANMGR2: REM received report soft error from 0000.3040.a630.
LANMGR0: REM received report soft error from 0000.3040.a630.
LANMGR2: RS received ring purge from 0000.3040.a630.
LANMGR2: RS received AMP from 0000.3040.a630.
LANMGR2: RS received SMP from 0000.3080.2d79.
LANMGR2: CRS received report NAUN change from 1000.5ade.0d8a.
LANMGR2: RS start watching ring poll.
LANMGR0: RS received ring purge from 0000.3040.a630.
LANMGR0: RS received AMP from 0000.3040.a630.
LANMGR0: RS received SMP from 0000.3080.2d79.
LANMGR0: CRS received report NAUN change from 1000.5ade.0d8a.
LANMGR0: RS start watching ring poll.
LANMGR2: RS received SMP from 1000.5ade.0d8a.
LANMGR2: RPS received request initialization from 1000.5ade.0d8a.
LANMGR2: RPS sending initialize station to 1000.5ade.0d8a.

Table 207 describes the significant fields shown in the display.

Table 207 debug lnm mac Field Descriptions

Field

Description

LANMGR0:

Indicates that this line of output displays MAC-level debugging information. 0 indicates the number of the Token Ring interface associated with this line of debugging output.

RS

Indicates which function of the MAC-level software is communicating as follows:

•CRS—Configuration Report Server

•REM—Ring Error Monitor

•RPS—Ring Parameter Server

•RS—Ring Station

received

Indicates that the router received a frame. The other possible value is sending, to indicate that the router is sending a frame.

request address

Indicates the name of the specific frame that the router sent or received. Possible values include the following:

•AMP

•initialize station

•report address

•report attachments

•report nearest active upstream neighbor (NAUN) change

•report soft error

•report state

•request address

•request attachments

•request initialization

•request state

•ring purge

•SMP

from 4000.3040.a670

Indicates the source address of the frame, if the router has received the frame. If the router is sending the frame, this address is the destination address of the frame.

As the output indicates, all debug lnm mac command messages follow the format described in Table 207 except the following:

LANMGR2: RS start watching ring poll
LANMGR2: RS stop watching ring poll

These messages indicate that the router starts and stops receiving AMP and SMP frames. These frames are used to build a current picture of which stations are on the ring.

debug local-ack state

To display the new and the old state conditions whenever there is a state change in the local acknowledgment state machine, use the debug local-ack state command in privileged EXEC mode. To disable debugging output, use the no form of this command.

debug local-ack state
no debug local-ack state
Syntax Description

This command has no arguments or keywords.

Command Modes

Privileged EXEC

Examples

The following is sample output from the debug local-ack state command:

Router# debug local-ack state

LACK_STATE: 2370300, hashp 2AE628, old state = disconn, new state = awaiting
LLC2 open to finish
LACK_STATE: 2370304, hashp 2AE628, old state = awaiting LLC2 open to finish,
new state = connected
LACK_STATE: 2373816, hashp 2AE628, old state = connected, new state = disconnected
LACK_STATE: 2489548, hashp 2AE628, old state = disconn, new state = awaiting
LLC2 open to finish
LACK_STATE: 2489548, hashp 2AE628, old state = awaiting LLC2 open to finish,
new state = connected
LACK_STATE: 2490132, hashp 2AE628, old state = connected, new state = awaiting
linkdown response
LACK_STATE: 2490140, hashp 2AE628, old state = awaiting linkdown response,
new state = disconnected
LACK_STATE: 2497640, hashp 2AE628, old state = disconn, new state = awaiting
LLC2 open to finish
LACK_STATE: 2497644, hashp 2AE628, old state = awaiting LLC2 open to finish,
new state = connected

Table 208 describes the significant fields shown in the display.

Table 208 debug local-ack state Field Descriptions

Field

Description

LACK_STATE:

Indicates that this packet describes a state change in the local acknowledgment state machine.

2370300

System clock.

hashp 2AE628

Internal control block pointer used by technical support staff for debugging purposes.

old state = disconn

Old state condition in the local acknowledgment state machine. Possible values include the following:

•Disconn (disconnected)

•awaiting LLC2 open to finish

•connected

•awaiting linkdown response

new state = awaiting LLC2 open to finish

New state condition in the local acknowledgment state machine. Possible values include the following:

•Disconn (disconnected)

•awaiting LLC2 open to finish

•connected

•awaiting linkdown response

debug management event

To monitor the activities of the Event MIB in real time on your routing device, use the debug management event command in privileged EXEC mode. To disable debugging output, use the no form of this command.

debug management event
no debug management event
Syntax Description

This command has no arguments or keywords.

Defaults

Debugging output is disabled.

Command Modes

Privileged EXEC

Command History

Release

Modification

12.1(3)T

This command was introduced.

Usage Guidelines

The debug management event command prints messages to the screen whenever the Event MIB evaluates a specified trigger. These messages are given in real-time, and are intended to be used by technical support engineers for troubleshooting purposes. Definitions for the OID (object identifier) fields can be found in the EVENT-MIB.my file, available for download from the Cisco MIB website on http://www.cisco.com/public/sw-center/netmgmt/cmtk/mibs.shtml.

Examples

The following is sample output from the debug management event command:

Router# debug management event

Event Process Bool: Owner aseem, Trigger 01
Event Bool process: invoke event
Event Bool process: no wildcarding
Event: OID ifEntry.10.3
Event getValue abs: 69847284
Event Bool process: Trigger Fired !
mteSetNotifyObjects:
Event execOnFiring: sending notification
Event: OID ifEntry.10.1
Event add_objects: Owner , Trigger
Event add_objects: Owner aseem, Trigger sethi
Event Found Owner: aseem
Event Found Name: sethi
Event: OID ifEntry.10.1
Event: sending trap with 7 OIDs
Event: OID mteHotTrigger.0
Event: OID mteHotTargetName.0
Event: OID mteHotContextName.0
Event: OID ifEntry.10.3
Event: OID mteHotValue.0
Event: OID ifEntry.10.1
Event: OID ifEntry.10.1
Event mteDoSets: setting oid
Event mteDoSets: non-wildcarded oid
Event: OID ciscoSyslogMIB.1.2.1.0
Event Thresh Process: Owner aseem, Trigger 01
Event Thresh process: invoke rising event
Event Thresh process: invoke falling event
Event Thresh process: no wildcarding
Event: OID ifEntry.10.3
Event getValue abs: 69847284
Event Existence Process: Owner aseem, Trigger 01
Event Exist process: invoke event
Event Exist process: no wildcarding
Event: OID ifEntry.10.3
Event getValue abs: 69847284
Event Check ExistTrigger for Absent
Event Check ExistTrigger for Changed

Router# no debug management event
Related Commands

Command

Description

show management event

Displays the SNMP Event values that have been configured on your routing device through the use of the Event MIB.

debug mdss

To display the run-time errors and sequence of events for the multicast distributed switching services (MDSS), use the debug mdss command in privileged EXEC mode. To disable debugging output, use the no form of this command.

debug mdss {all | error | event}
no debug mdss {all | error | event}
Syntax Description

all

Displays both errors and sequence of events for MDSS.

error

Displays the run-time errors for MDSS.

event

Displays the run-time sequence of events for MDSS.

Defaults

Debugging is not enabled.

Command Modes

Privileged EXEC

Command History

Release

Modification

12.0(5)T

This command was introduced.

Examples

The following example shows output using the debug mdss command with the all keyword:

Router# debug mdss all

mdss all debugging is on

Router# clear ip mroute *

Router#
01:31:03: MDSS: got MDFS_CLEARALL
01:31:03: MDSS: --> mdss_flush_all_sc
01:31:03: MDSS: enqueue a FE_GLOBAL_DELETE
01:31:03: MDSS: got MDFS_MROUTE_ADD for (0.0.0.0, 224.0.1.40)
01:31:03: MDSS: --> mdss_free_scmdb_cache
01:31:03: MDSS: got MDFS_MROUTE_ADD for (0.0.0.0, 239.255.158.197)
01:31:03: MDSS: got MDFS_MROUTE_ADD for (192.1.21.6, 239.255.158.197)
01:31:03: MDSS: got a MDFS_MIDB_ADD for (192.1.21.6, 239.255.158.197,
Vlan21) +Vlan22
01:31:03: MDSS: -- mdss_add_oif
01:31:03: MDSS: enqueue a FE_OIF_ADD (192.1.21.6, 239.255.158.197,
Vlan21) +Vlan22
01:31:03: MDSS: mdb (192.1.21.6, 239.255.158.197) fast_flags |
MCACHE_MTU
01:31:03: MDSS: got a MDFS_MIDB_ADD for (192.1.21.6, 239.255.158.197,
Vlan21) +Vlan23
01:31:03: MDSS: -- mdss_add_oif
01:31:03: MDSS: enqueue a FE_OIF_ADD (192.1.21.6, 239.255.158.197,
Vlan21) +Vlan23
01:31:03: MDSS: mdb (192.1.21.6, 239.255.158.197) fast_flags |
MCACHE_MTU
01:31:03: MDSS: got a MDFS_MIDB_ADD for (192.1.21.6, 239.255.158.197,
Vlan21) +Vlan24
01:31:03: MDSS: -- mdss_add_oif
01:31:03: MDSS: enqueue a FE_OIF_ADD (192.1.21.6, 239.255.158.197,
Vlan21) +Vlan24
01:31:03: MDSS: mdb (192.1.21.6, 239.255.158.197) fast_flags |
MCACHE_MTU
01:31:03: MDSS: got a MDFS_MIDB_ADD for (192.1.21.6, 239.255.158.197,
Vlan21) +Vlan25
01:31:03: MDSS: -- mdss_add_oif
01:31:03: MDSS: enqueue a FE_OIF_ADD (192.1.21.6, 239.255.158.197,
Vlan21) +Vlan25
01:31:03: MDSS: mdb (192.1.21.6, 239.255.158.197) fast_flags |
MCACHE_MTU
01:31:03: MDSS: got a MDFS_MIDB_ADD for (192.1.21.6, 239.255.158.197,
Vlan21) +Vlan26
01:31:03: MDSS: -- mdss_add_oif

01:31:03: MDSS: enqueue a FE_OIF_ADD (192.1.21.6, 239.255.158.197,
Vlan21) +Vlan26
01:31:03: MDSS: mdb (192.1.21.6, 239.255.158.197) fast_flags |
MCACHE_MTU
01:31:03: MDSS: got a MDFS_MIDB_ADD for (192.1.21.6, 239.255.158.197,u
Vlan21) +Vlan27
Related Commands

Command

Description

debug mls rp ip multicast

Displays information about MLSP.

debug media resource provisioning all

To display debugging messages related to all media resource provisioning, use the debug media resource provisioning all command in privileged EXEC mode. To disable debugging output, use the no form of this command.

debug media resource provisioning all
no debug media resource provisioning all
Syntax Description

This command has no arguments or keywords.

Command Modes

Privileged EXEC

Command History

Release

Modification

12.3(8)T

This command was introduced.

Examples

The following is sample output from the debug media resource provisioning all command:

Router# debug media resource provisioning all
.
.
.
Media resource provisioning all debugging is on.
Disabling profile will disconnect active CONFERENCING calls,
do you want to continue ? [yes/no]
*Jul 8 18:46:36: rpm_if_profile_exist ::profile id 10, service TRANSCODING
*Jul 8 18:46:36: rpm_get_rscid_profile_info Profile with profile id :10, service :TRANSCODING does not exist
*Jul 8 18:46:36: rpm_if_profile_exist ::profile id 10, service CONFERENCING
*Jul 8 18:46:36: rpm_if_profile_exist ::profile id 10, service TRANSCODING
*Jul 8 18:46:36: rpm_get_rscid_profile_info Profile with profile id :10, service :TRANSCODING does not exist
*Jul 8 18:46:36: rpm_if_profile_exist ::profile id 10, service CONFERENCING
Must be yes or no
Router(config-dspfarm-profile)#
Router(config-dspfarm-profile)#
Router(config-dspfarm-profile)#
Router(config-dspfarm-profile)# no shutdown
Router(config-dspfarm-profile)#
*Jul 8 18:46:42: rpm_user_enable_profile ::profile id 10, service CONFERENCING
*Jul 8 18:46:44:%DSPRM-5-UPDOWN:DSP 10 in slot 1, changed state to up
*Jul 8 18:46:44: rpm_rscprv_update ::provider_id 1 rsc_id 2 rsc_grp_state 4num_channel_delta 0
*Jul 8 18:46:44: rpm_rscprv_update resource update from resource provider 1 is successful
Router(config-dspfarm-profile)#
Router(config-dspfarm-profile)# exit
Router(config)# exit
Related Commands

Command

Description

debug media resource provisioning errors

Displays debugging messages related to media resource provisioning errors.

debug media resource provisioning events

Displays debugging messages related to media resource provisioning events.

debug media resource provisioning errors

To display debugging messages related to media resource provisioning errors, use the debug media resource provisioning errors command in privileged EXEC mode. To disable debugging output, use the no form of this command.

debug media resource provisioning errors
no debug media resource provisioning errors
Syntax Description

This command has no arguments or keywords.

Command Modes

Privileged EXEC
Command History

Release

Modification

12.3(8)T

This command was introduced.

Examples

The following is sample output from the debug media resource provisioning errors command:

Router# debug media resource provisioning errors

Media resource provisioning errors debugging is on

Router# no debug media resource provisioning errors

Media resource provisioning errors debugging is off
Related Commands

Command

Description

debug media resource provisioning all

Displays debugging messages related to all media resource provisioning.

debug media resource provisioning events

Displays debugging messages related to media resource provisioning events.

debug media resource provisioning events

To display debugging messages related to media resource provisioning events, use the debug media resource provisioning events command in privileged EXEC mode. To disable debugging output, use the no form of this command.

debug media resource provisioning events
no debug media resource provisioning events
Syntax Description

This command has no arguments or keywords.

Command Modes

Privileged EXEC
Command History

Release

Modification

12.3(8)T

This command was introduced.

Examples

The following is sample output from the debug media resource provisioning events command:

Router# debug media resource provisioning events

Media resource provisioning events debugging is on

Router# no debug media resource provisioning events

Media resource provisioning events debugging is off
Router#
Related Commands

Command

Description

debug media resource provisioning all

Displays debugging messages related to all media resource provisioning.

debug media resource provisioning errors

Displays debugging messages related to media resource provisioning errors.

debug mediacard

To display Digital Signal Processor Resource Manager (DSPRM) debugging information, use the debug mediacard command in privileged EXEC mode. To disable debugging output, use the no form of this command.

debug mediacard {all | errors | events | message}
no debug mediacard {all | errors | events | message}
Syntax Description

all

Debugs DSPRM errors, events, and messages.

errors

Debugs DSPRM errors.

events

Debugs DSPRM events.

message

Debugs DSPRM messages.

Defaults

No default behavior or values

Command Modes

Privileged EXEC

Command History

Release

Modification

12.3(8)XY

This command was introduced on the Communication Media Module.

12.3(14)T

This command was integrated into Cisco IOS Release 12.3(14)T.

Usage Guidelines

Use the debug mediacard errors command to debug active calls. You should use the debug mediacard all command during minimum traffic periods only; using the debug mediacard all command during active calls can significantly impact system performance.

Examples

The following is sample output from the debug mediacard command:

Router# debug mediacard messages

Media Card service messages debugging is on
*Mar 1 07:45:06.362: > CREATE_CONFERENCE (0x1) , pktLen 56, confId 1, instId 1
7483, seqNo 27983, Payload (24 bytes): confType 3, agcMode 1, spkrUpdateReportMo
de 1, maxActSpkr 3
*Mar 1 07:45:06.362: > CREATE_CHANNEL (0x64) , pktLen 100, confId 1, instId 26
625, seqNo 27984, Payload (68 bytes): rxCodecType 1, suppressRx 1, rxCNG 2, rxPL
C 2, rxVAD 2, rxToneDet 1, rxSpkrPriority 1, rxInactiveTimeOut 7200, rxPacketSiz
e 20, rxRTPPayloadType 0
*Mar 1 07:45:06.362: txCodecType 2, suppressTx 1, txVAD 1, AGC 1, txSSRC 167
860472, txPacketSize 20, txRTPPayloadType 0
*Mar 1 07:45:06.362: < CREATE_CONFERENCE_ACK (0x4001) , pktLen 116, confId 1,
instId 0, seqNo 27983, Payload (84 bytes): status 0 (Normal Completion), param1
3, param2 0
*Mar 1 07:45:06.362: < CREATE_CHANNEL_ACK (0x4064) , pktLen 116, confId 1, ins
tId 26625, seqNo 27984, Payload (84 bytes): status 0 (Normal Completion), param1
0, param2 0
*Mar 1 07:45:06.362: > CREATE_CONFERENCE (0x1) , pktLen 56, confId 2, instId
All possible debugging has been turned off
MTP#26625, seqNo 27985, Payload (24 bytes): confType 3, agcMode 1, spkrUpdateRep
ortMode 1, maxActSpkr 3
*Mar 1 07:45:06.362: > CREATE_CHANNEL (0x64) , pktLen 100, confId 2, instId 26
626, seqNo 27986, Payload (68 bytes): rxCodecType 2, suppressRx 1, rxCNG 2, rxPL
C 2, rxVAD 2, rxToneDet 1, rxSpkrPriority 1, rxInactiveTimeOut 7200, rxPacketSiz
e 20, rxRTPPayloadType 0
*Mar 1 07:45:06.366: txCodecType 1, suppressTx 1, txVAD 1, AGC 1, txSSRC 167
858296, txPacketSize 20, txRTPPayloadType 0
*Mar 1 07:45:06.366: < CREATE_CONFERENCE_ACK (0x4001) , pktLen 116, confId 2,
instId 0, seqNo 27985, Payload (84 bytes): status 0 (Normal Completion), param1
3, param2 0

Router# debug mediacard events

Media Card service events debugging is on
*Mar 1 07:47:53.926: ms_ac_open_rtp_sockets: loc_ipaddr = 10.1.80.24 loc_mac<00
03.feac.c842> rem_ip<0.0.0.0> rem_port<0>
*Mar 1 07:47:53.926: ms_ac_get_unique_udp_port: rtcp_socket = 6255F490
*Mar 1 07:47:53.926: ms_ac_get_unique_udp_port: SLOT3 Port<3450> is assigned!
*Mar 1 07:47:53.926: ms_ac_open_local_rtp: rtpinfo 64382A3C, local_port =23930
*Mar 1 07:47:53.926: ms_ac_rtp_enq: Sent msg 101 to DSPFARM
*Mar 1 07:47:53.926: ms_ac_open_remote_rtp: rtpinfo 64382A3C, loc_ipaddr = 10.1
.80.24 loc_udp_prt <23930> ,loc_mac<0003.feac.c842>
*Mar 1 07:47:53.926: ms_ac_open_remote_rtp: remote_ipaddr = 10.1.2.15 remote_ud
p_prt <17932>
*Mar 1 07:47:53.926: ms_ac_nexthop_macaddr idb<630BDFCC> nexthop<10.1.80.1>
*Mar 1 07:47:53.926: ms_ac_nexthop_macaddr ptr<6301F5AC> through<GigabitEtherne
t1/0> nexthop<10.1.80.1>
*Mar 1 07:47:53.926: ms_ac_after_found_mac <10.1.2.15>'s mac <00d0.002a.7400> f
ound
*Mar 1 07:47:53.926: ms_ac_check_xcode_rem_ip: rtpinfo <64382A3C> other_rtpinfo
<0>
*Mar 1 07:47:53.926: ms_ac_rtp_enq: Sent msg 103 to DSPFARM
*Mar 1 07:47:53.942: ms_ac_open_rtp_sockets: loc_ipaddr = 10.1.80.24 loc_mac<00
03.feac.c842> rem_ip<0.0.0.0> rem_port<0>
*Mar 1 07:47:53.942: ms_ac_get_unique_udp_port: rtcp_socket = 6256C9B4
*Mar 1 07:47:53.942: ms_ac_get_unique_udp_port: SLOT3 Port<1778> is assigned!
*Mar 1 07:47:53.942: ms_ac_open_local_rtp: rtpinfo 6438353C, local_port =22258
*Mar 1 07:47:53.942: ms_ac_rtp_enq: Sent msg 101 to DSPFARM
*Mar 1 07:47:53.942: ac_validate_xcode_params: codeDec<2> codeEnc<1> decDur<20>
encDur<20>
*Mar 1 07:47:53.942: ac_open_xcode_channel: codeDec<1> codeEnc<2> decDur<20> en
cDur<20> VADen<0> prf_id<4>
*Mar 1 07:47:53.942: reserve_xcode_resource: reserve xcode resource:codecDec<1>
codecEnc<2>
*Mar 1 07:47:53.942: al
Related Commands

Command

Description

show mediacard

Displays information about the media card.

debug mgcp all

To enable all debug traces for Media Gateway Control Protocol (MGCP), use the debug mgcp all command in privileged EXEC mode. To disable debugging output, use the no form of this command.

debug mgcp all [tracelevel {critical | moderate | verbose}]
no debug mgcp all
Syntax Description

tracelevel

(Optional) Sets the priority level for this debug trace.

•critical—Displays only high-priority debug information.

•moderate—Displays medium- and high-priority debug information.

•verbose—Displays all debug information. This is the default level.

Command Default

MGCP debugging is disabled.

Command Modes

Privileged EXEC

Command History

Release

Modification

12.1(1)T

This command was introduced.

12.1(3)T

Additional information was displayed for the gateways.

12.1(5)XM

The output was modified to display parameters for the MGCP channel-associated signaling (CAS) PBX and ATM adaptation layer 2 (AAL2) permanent virtual circuit (PVC) features.

12.2(2)T

The output was modified to display parameters for the MGCP channel-associated signaling (CAS) PBX and ATM adaptation layer 2 (AAL2) permanent virtual circuit (PVC) features.

12.2(11)T

This command was implemented on the Cisco AS5350, Cisco AS5400, and Cisco AS5850.

12.2(13)T

This command was implemented on the Cisco 7200 series images.

12.4(4)T

The tracelevel keyword was added.

Usage Guidelines

This command enables the following MGCP debug commands:

•debug mgcp endptdb

•debug mgcp errors

•debug mgcp events

•debug mgcp gcfm

•debug mgcp inout

•debug mgcp media

•debug mgcp nas

•debug mgcp packets

•debug mgcp parser

•debug mgcp src

•debug mgcp state

•debug mgcp voipcac

Caution Using the debug mgcp all command may severely impact network performance.

Examples

The following is sample output from the debug mgcp all command:

Router# debug mgcp all

This may severely impact network performance. Continue[confirm]
Media Gateway Control Protocol all debugging is on, trace-level Verbose

Router#
*Sep 10 17:20:24.408: //-1/xxxxxxxxxxxx/MGCP/mgcp_count_active_mgc_msg_stat(240):[lvl=1]MGC stat - 192.168.1.200, total=8, succ=5, failed=1
*Sep 10 17:20:24.408: MGCP Packet received from 192.168.1.200:7979--->
CRCX 6 aaln/S2/SU1/1 MGCP 1.0
M: recvonly
C: 1
<---

*Sep 10 17:20:24.408: //-1/xxxxxxxxxxxx/MGCP/mgcpapp_process_mgcp_msg(3318):[lvl=0] : <NEW MGCP MSG From CA>
*Sep 10 17:20:24.408: //-1/xxxxxxxxxxxx/MGCP/mgcp_parse_packet(316):[lvl=0]call mgcp_parse_header

*Sep 10 17:20:24.408: //-1/xxxxxxxxxxxx/MGCP/mgcp_parse_packet(320):[lvl=0]out mgcp_parse_header

*Sep 10 17:20:24.408: //-1/xxxxxxxxxxxx/MGCP/mgcp_parse_packet(360):[lvl=1]SUCCESS: - MGCP Header parsing was OK

*Sep 10 17:20:24.408: //-1/xxxxxxxxxxxx/MGCP/mgcp_string_parse(186):[lvl=0]return code=1.
*Sep 10 17:20:24.408: //-1/xxxxxxxxxxxx/MGCP/mgcp_parse_parameter_lines(725):[lvl=1]return parse function in mgcp_parm_rules_array[6].
*Sep 10 17:20:24.408: //-1/xxxxxxxxxxxx/MGCP/mgcp_parse_conn_mode(4762):[lvl=0](in_ptr: recvonly)

*Sep 10 17:20:24.408: //-1/xxxxxxxxxxxx/MGCP/mgcp_parse_conn_mode(4780):[lvl=0]tmp_ptr:(recvonly)

*Sep 10 17:20:24.408: //-1/xxxxxxxxxxxx/MGCP/mgcp_parse_conn_mode(4816):[lvl=0]tmp_ptr:(recvonly)

*Sep 10 17:20:24.408: //-1/xxxxxxxxxxxx/MGCP/mgcp_parse_conn_mode(4822):[lvl=0]match recvonly recvonly

*Sep 10 17:20:24.408: //-1/xxxxxxxxxxxx/MGCP/mgcp_parse_conn_mode(4830):[lvl=0]case MODE_RECVONLY

*Sep 10 17:20:24.408: //-1/xxxxxxxxxxxx/MGCP/mgcp_parse_conn_mode(4894):[lvl=0]SUCCESS: Connection Mode parsing is OK

*Sep 10 17:20:24.408: //-1/xxxxxxxxxxxx/MGCP/mgcp_string_parse(186):[lvl=0]return code=1.
*Sep 10 17:20:24.408: //-1/xxxxxxxxxxxx/MGCP/mgcp_parse_parameter_lines(725):[lvl=1]return parse function in mgcp_parm_rules_array[1].
*Sep 10 17:20:24.408: //-1/xxxxxxxxxxxx/MGCP/mgcp_parse_call_id(840):[lvl=0]in_ptr: 1

*Sep 10 17:20:24.408: //-1/xxxxxxxxxxxx/MGCP/mgcp_parse_call_id(883):[lvl=1]SUCCESS: Call ID string(1) parsing is OK

*Sep 10 17:20:24.408: //-1/xxxxxxxxxxxx/MGCP/mgcp_val_mandatory_parms(12428):[lvl=0]Entered
*Sep 10 17:20:24.408: //-1/xxxxxxxxxxxx/MGCP/mgcp_val_comp_mp_parms(14923):[lvl=0]Entered
*Sep 10 17:20:24.408: //-1/xxxxxxxxxxxx/MGCP/mgcp_val_comp_mp_parms(14928):[lvl=1] - lcon_opt_ptr could not be obtained
*Sep 10 17:20:24.412: //-1/xxxxxxxxxxxx/MGCP/mgcp_parse_packet(378):[lvl=2]SUCCESS: END of Parsing
*Sep 10 17:20:24.412: //-1/xxxxxxxxxxxx/MGCP/xgcp_endpt_name_parse_a(1339):[lvl=0]aaln/S2/SU1/1
*Sep 10 17:20:24.412: //-1/xxxxxxxxxxxx/MGCP/xgcp_endpt_name_parse_aaln_slot(1632):[lvl=0]2/SU1/1
*Sep 10 17:20:24.412: //-1/xxxxxxxxxxxx/MGCP/xgcp_endpt_name_parse_digit(1600):[lvl=0]2/SU1/1
*Sep 10 17:20:24.412: //-1/xxxxxxxxxxxx/MGCP/xgcp_endpt_name_parse_aaln_slot(1641):[lvl=0] : ifn 0x665449A8, slot:2
*Sep 10 17:20:24.412: //-1/xxxxxxxxxxxx/MGCP/xgcp_endpt_name_parse_aaln_su(1773):[lvl=0]1/1
*Sep 10 17:20:24.412: //-1/xxxxxxxxxxxx/MGCP/xgcp_endpt_name_parse_digit(1600):[lvl=0]1/1
*Sep 10 17:20:24.412: //-1/xxxxxxxxxxxx/MGCP/xgcp_endpt_name_parse_aaln_port(1807):[lvl=0]1
*Sep 10 17:20:24.412: //-1/xxxxxxxxxxxx/MGCP/xgcp_endpt_name_parse_digit(1600):[lvl=0]1
*Sep 10 17:20:24.412: //-1/xxxxxxxxxxxx/MGCP/mgcp_endpt_get_endpt_offset(2590):[lvl=0]endpt NULL
*Sep 10 17:20:24.412: //-1/xxxxxxxxxxxx/MGCP/xgcp_endpt_get_by_ifn(1326):[lvl=0]Entered
*Sep 10 17:20:24.412: //-1/xxxxxxxxxxxx/MGCP/xgcp_endpt_get_tree_link_by_ifn(1145):[lvl=0]Entered
*Sep 10 17:20:24.412: //-1/xxxxxxxxxxxx/MGCP/xgcp_endpt_compute_key(196):[lvl=0]type 2 slot 0002 subunit 0001
*Sep 10 17:20:24.412: //-1/xxxxxxxxxxxx/MGCP/xgcp_endpt_get_tree_link_by_ifn(1157):[lvl=0]computed key 0x2081FF01
Related Commands

Command

Description

debug mgcp endpoint

Enables debug traces for a specific MGCP endpoint.

debug mgcp tracelevel-default

Sets the trace level globally for all MGCP debug traces.

mgcp

Starts the MGCP daemon.

mgcp debug-header

Enables the display of MGCP module-dependent information in the debug header.

show debugging

Displays the types of debugging that are enabled.

show mgcp

Displays MGCP configuration information.

voice call debug

Specifies the format of the debug header.

debug mgcp endpoint

To enable debug traces for a specific Media Gateway Control Protocol (MGCP) endpoint, use the debug mgcp endpoint command in privileged EXEC mode. To disable debugging output for the endpoint, use the no form of this command.

debug mgcp endpoint endpoint-name {all [tracelevel {critical | moderate | verbose}] | errors | events [tracelevel {critical | moderate | verbose}] | media [tracelevel {critical | moderate | verbose}] | packets}
no debug mgcp endpoint endpoint-name {all | errors | events | media | packets}
Syntax Description

endpoint-name

Name of the MGCP endpoint for which to enable debugging. Must be a fully specified and supported endpoint.

all

Displays MGCP errors, events, media, and packets for the specified endpoint.

errors

Displays MGCP errors for the specified endpoint.

events

Displays MGCP events for the specified endpoint.

media

Displays MGCP tone and signal events for the specified endpoint.

packets

Displays MGCP packets for the specified endpoint.

tracelevel

(Optional) Sets the priority level for the all, events, or media debug trace.

•critical—Displays only high-priority debug information.

•moderate—Displays medium- and high-priority debug information.

•verbose—Displays all debug information. This is the default level.

Note This keyword is not available for errors or packets debugging.

Command Default

Debugging for specific endpoints is not enabled.

Command Modes

Privileged EXEC

Command History

Release

Modification

12.4(4)T

This command was introduced.

Usage Guidelines

This command enables debugging for a specific MGCP endpoint. You can enable the same type of debugging globally for all endpoints by using the debug mgcp all, debug mgcp errors, debug mgcp events, debug mgcp media, and debug mgcp packets commands.

Trace levels allow you to control the amount of debug information that is displayed in the output from MGCP debug commands. Reducing the amount of output displayed on the console port makes it easier to locate the correct debug information and limits the impact to network performance.

This command sets the trace level for the specific endpoint. You can set the trace level globally for all MGCP debug commands and endpoints by using the debug mgcp tracelevel-default command. Setting the endpoint-specific trace level takes precedence over the global trace level.

Note Trace levels are not supported for errors or packets debugging because all of the output from those commands is set to high priority.

Examples

The following is sample output from the debug mgcp endpoint command:

Router# debug mgcp endpoint aaln/S2/SU1/1 events tracelevel critical

Media Gateway Control Protocol events debugging for endpoint aaln/S2/SU1/1 is on, trace-level Critical

Router#
*Sep 10 17:46:13.100: //-1/xxxxxxxxxxxx/MGCP|aaln/S2/SU1/1|-1|-1/mgcp_idle_crcx(4875):[lvl=2]callp(0x63E313E0), current state CALL_IDLE, event EV_CREATE_CONN
*Sep 10 17:46:13.100: //7/9D04EB218005/MGCP|aaln/S2/SU1/1|-1|-1/<VOICE>/mgcp_invoke_app_sm(570):[lvl=2]MGCP:FSM done- callp(63E313E0), new state CALL_CONNECTING, event EV_CREATE_CONN
*Sep 10 17:46:13.104: //8/9D04EB218005/MGCP|aaln/S2/SU1/1|-1|-1/<VOIP>/mgcp_call_pre_conference(223):[lvl=2]call p(0x63E311D0), current state CALL_CONNECTING, event EV_CALL_CONNECT
*Sep 10 17:46:13.104: //8/9D04EB218005/MGCP|aaln/S2/SU1/1|-1|-1/<VOIP>/mgcp_call_connect(7331):[lvl=2]callp(0x63 E311D0), current state CALL_CONNECTING, event EV_CALL_CONNECT
*Sep 10 17:46:13.104: //8/9D04EB218005/MGCP|aaln/S2/SU1/1|-1|-1/<VOIP>/mgcp_invoke_app_sm(570):[lvl=2]MGCP:FSM done- callp(63E311D0), new state CALL_CONFERENCING, event EV_CALL_CONNECT
*Sep 10 17:46:13.104: //7/9D04EB218005/MGCP|aaln/S2/SU1/1|-1|-1/<VOICE>/mgcp_call_proceeding(6306):[lvl=2]callp( 0x63E313E0), current state CALL_CONNECTING, event EV_CALL_PROCEED
*Sep 10 17:46:13.104: //7/9D04EB218005/MGCP|aaln/S2/SU1/1|-1|-1/<VOICE>/mgcp_call_connect(7331):[lvl=2]callp(0x6 3E313E0), current state CALL_CONNECTING, event EV_CALL_PROCEED
*Sep 10 17:46:13.104: //7/9D04EB218005/MGCP|aaln/S2/SU1/1|-1|-1/<VOICE>/mgcp_invoke_app_sm(570):[lvl=2]MGCP:FSM done- callp(63E313E0), new state CALL_CONFERENCING, event EV_CALL_PROCEED
*Sep 10 17:46:13.108: //7/9D04EB218005/MGCP|aaln/S2/SU1/1|-1|-1/<VOICE>/mgcp_ignore_ccapi_ev(4316):[lvl=2]callp( 0x63E313E0), current state CALL_CONFERENCING, event EV_CONF_RDY
*Sep 10 17:46:13.108: //7/9D04EB218005/MGCP|aaln/S2/SU1/1|-1|-1/<VOICE>/mgcp_invoke_app_sm(570):[lvl=2]MGCP:FSM done- callp(63E313E0), new state CALL_CONFERENCING, event EV_CONF_RDY
*Sep 10 17:46:13.108: //7/9D04EB218005/MGCP|aaln/S2/SU1/1|-1|-1/<VOICE>/mgcp_call_modified(7710):[lvl=2]callp(0x 63E313E0), current state CALL_CONFERENCING, event EV_MODIFY_DONE
*Sep 10 17:46:13.108: //7/9D04EB218005/MGCP|aaln/S2/SU1/1|-1|-1/<VOICE>/mgcp_invoke_app_sm(570):[lvl=2]MGCP:FSM done- callp(63E313E0), new state CALL_CONFERENCING, event EV_MODIFY_DONE
*Sep 10 17:46:13.108: //7/9D04EB218005/MGCP|aaln/S2/SU1/1|-1|-1/<VOICE>/mgcp_voice_mode_done(7994):[lvl=2]callp( 0x63E313E0), current state CALL_CONFERENCING, event EV_VOICE_MODE_DONE, minor ev(d): 138, minor ev
*Sep 10 17:46:13.112: //7/9D04EB218005/MGCP|aaln/S2/SU1/1|-1|-1/<VOICE>/mgcp_invoke_app_sm(570):[lvl=2]MGCP:FSM done- callp(63E313E0), new state CALL_ACTIVE, event EV_VOICE_MODE_DONE
*Sep 10 17:46:23.104: //7/9D04EB218005/MGCP|aaln/S2/SU1/1|-1|-1/<VOICE>/mgcp_invoke_app_sm(570):[lvl=2]MGCP:FSM done- callp(63E313E0), new state CALL_ACTIVE, event EV_MEDIA_EVT
Related Commands

Command

Description

debug mgcp all

Enables all debug traces for MGCP.

debug mgcp errors

Enables debug traces for MGCP errors.

debug mgcp events

Enables debug traces for MGCP events.

debug mgcp media

Enables debug traces for MGCP tone and signal events.

debug mgcp packets

Enables debug traces for MGCP packets.

debug mgcp tracelevel-default

Sets the trace level globally for all MGCP debug traces.

mgcp

Starts the MGCP daemon.

mgcp debug-header

Enables the display of MGCP module-dependent information in the debug header.

show debugging

Displays the types of debugging that are enabled.

show mgcp

Displays MGCP configuration information.

voice call debug

Specifies the format of the debug header.

debug mgcp endptdb

To enable debug traces for all Media Gateway Control Protocol (MGCP) endpoints, use the debug mgcp endptdb command in privileged EXEC mode. To disable debugging output, use the no form of this command.

debug mgcp endptdb [tracelevel {critical | moderate | verbose}]
no debug mgcp endptdb
Syntax Description

tracelevel

(Optional) Sets the priority level for this debug trace.

•critical—Displays only high-priority debug information.

•moderate—Displays medium- and high-priority debug information.

•verbose—Displays all debug information. This is the default level.

Command Default

MGCP debugging for endpoints is disabled.

Command Modes

Privileged EXEC

Command History

Release

Modification

12.2(2)XA

This command was introduced.

12.2(11)T

This command was integrated into Cisco IOS Release 12.2(11)T.

12.4(4)T

The tracelevel keyword was added.

Usage Guidelines

This command enables debugging globally for all MGCP endpoints. You can limit debugging to a specific endpoint by using the debug mgcp endpoint command.

Trace levels allow you to control the amount of debug information that is displayed in the output from MGCP debug commands. Reducing the amount of output displayed on the console port makes it easier to locate the correct debug information and limits the impact to network performance.

Examples

The following is sample output from the debug mgcp endptdb command used with the debug mgcp packets command:

Router# debug mgcp packets

Media Gateway Control Protocol packets debugging for all endpoints is on

Router# debug mgcp endptdb

Media Gateway Control Protocol endpoint database debugging for all endpoints is on, trace-level Verbose

Router#
*Sep 10 11:39:16.467: MGCP Packet received from 192.168.1.200:7979--->
CRCX 27 aaln/S2/SU1/1 MGCP 1.0
M: recvonly
C: 1
<---

*Sep 10 11:39:16.467: //-1/xxxxxxxxxxxx/MGCP/xgcp_endpt_name_parse_a(1339):[lvl=0]aaln/S2/SU1/1
*Sep 10 11:39:16.467: //-1/xxxxxxxxxxxx/MGCP/xgcp_endpt_name_parse_aaln_slot(1632):[lvl=0]2/SU1/1
*Sep 10 11:39:16.467: //-1/xxxxxxxxxxxx/MGCP/xgcp_endpt_name_parse_digit(1600):[lvl=0]2/SU1/1
*Sep 10 11:39:16.467: //-1/xxxxxxxxxxxx/MGCP/xgcp_endpt_name_parse_aaln_slot(1641):[lvl=0] : ifn 0x665449A8, slot:2
*Sep 10 11:39:16.467: //-1/xxxxxxxxxxxx/MGCP/xgcp_endpt_name_parse_aaln_su(1773):[lvl=0]1/1
*Sep 10 11:39:16.467: //-1/xxxxxxxxxxxx/MGCP/xgcp_endpt_name_parse_digit(1600):[lvl=0]1/1
*Sep 10 11:39:16.467: //-1/xxxxxxxxxxxx/MGCP/xgcp_endpt_name_parse_aaln_port(1807):[lvl=0]1
*Sep 10 11:39:16.467: //-1/xxxxxxxxxxxx/MGCP/xgcp_endpt_name_parse_digit(1600):[lvl=0]1
*Sep 10 11:39:16.467: //-1/xxxxxxxxxxxx/MGCP/xgcp_endpt_get_by_ifn(1326):[lvl=0]Entered
*Sep 10 11:39:16.467: //-1/xxxxxxxxxxxx/MGCP/xgcp_endpt_get_tree_link_by_ifn(1145):[lvl=0]Entered
*Sep 10 11:39:16.467: //-1/xxxxxxxxxxxx/MGCP/xgcp_endpt_compute_key(196):[lvl=0]type 2 slot 0002 subunit 0001
*Sep 10 11:39:16.467: //-1/xxxxxxxxxxxx/MGCP/xgcp_endpt_get_tree_link_by_ifn(1157):[lvl=0]computed key 0x2081FF01
*Sep 10 11:39:16.467: //-1/xxxxxxxxxxxx/MGCP/xgcp_endpt_get_state(3758):[lvl=0]endpt aaln/S2/SU1/1
*Sep 10 11:39:16.467: //-1/xxxxxxxxxxxx/MGCP/xgcp_endpt_default_get_state(3779):[lvl=0]endpt aaln/S2/SU1/1
*Sep 10 11:39:16.479: MGCP Packet sent to 192.168.1.200:7979--->
200 27 OK
I: D

v=0
c=IN IP4 192.168.1.79
m=audio 16870 RTP/AVP 0 8 99 101 102 2 15 103 4 104 105 106 107 18 100
a=rtpmap:99 G.729a/8000
a=rtpmap:101 G.726-16/8000
a=rtpmap:102 G.726-24/8000
a=rtpmap:103 G.723.1-H/8000
a=rtpmap:104 G.723.1-L/8000
a=rtpmap:105 G.729b/8000
a=rtpmap:106 G.723.1a-H/8000
a=rtpmap:107 G.723.1a-L/8000
a=rtpmap:100 X-NSE/8000
a=fmtp:100 200-202
a=X-sqn:0
a=X-cap: 1 audio RTP/AVP 100
a=X-cpar: a=rtpmap:100 X-NSE/8000
a=X-cpar: a=fmtp:100 200-202
a=X-cap: 2 image udptl t38
<---
Related Commands

Command

Description

debug mgcp all

Enables all debug traces for MGCP.

debug mgcp endpoint

Enables debug traces for a specific MGCP endpoint.

debug mgcp tracelevel-default

Sets the trace level globally for all MGCP debug traces.

mgcp

Starts the MGCP daemon.

mgcp debug-header

Enables the display of MGCP module-dependent information in the debug header.

show mgcp

Displays MGCP configuration information.

voice call debug

Specifies the format of the debug header.

debug mgcp errors

To enable debug traces for Media Gateway Control Protocol (MGCP) errors, use the debug mgcp errors command in privileged EXEC mode. To disable debugging output, use the no form of this command.

debug mgcp errors
no debug mgcp errors
Syntax Description

This command has no arguments or keywords.

Command Default

MGCP error debugging is disabled.

Command Modes

Privileged EXEC

Command History

Release

Modification

12.1(1)T

This command was introduced.

12.1(3)T

Additional information was displayed for the gateways.

12.1(5)XM

The output was modified to display parameters for the MGCP channel-associated signaling (CAS) PBX and ATM adaptation layer 2 (AAL2) permanent virtual circuit (PVC) features.

12.2(2)T

The output was modified to display parameters for the MGCP channel-associated signaling (CAS) PBX and ATM adaptation layer 2 (AAL2) permanent virtual circuit (PVC) features.

12.2(2)XA

The endpoint endpoint-name keyword and argument were added.

12.2(11)T

This command was implemented on the Cisco AS5350, Cisco AS5400, and Cisco AS5850.

12.2(13)T

This command was implemented on the Cisco 7200 series images.

12.4(4)T

The endpoint endpoint-name keyword and argument were removed and replaced by the debug mgcp endpoint command.

Usage Guidelines

This command enables error debugging globally for all MGCP endpoints. You can limit debugging to a specific endpoint by using the debug mgcp endpoint command.

Examples

The following is sample output from the debug mgcp errors command:

Router# debug mgcp errors

*Oct 16 12:09:05.538: MGC stat - 10.208.237.83, total=1029, succ=998, failed=0- mgcp_parse_header()- Request Verb FOUND AUEP
- mgcp_parse_request_header()- MGCP_V10, start check for profile
- mgcp_parse_header: mgcp_parse_request_header returns status: 0

*Oct 16 12:09:05.538: MGCP Packet received from 10.208.237.83-
AUEP 9634549 S0/DS1-0/1@AS5300 MGCP 1.0

F: I

*Oct 16 12:09:05.542: -- mgcp_parse_packet() - call mgcp_parse_header
- mgcp_parse_header()- Request Verb FOUND AUEP
- mgcp_parse_request_header()- MGCP_V10, start check for profile
- mgcp_parse_header: mgcp_parse_request_header returns status: 0
- mgcp_parse_packet() - out mgcp_parse_header
- SUCCESS: mgcp_parse_packet()-MGCP Header parsing was OK
- mgcp_parse_parameter_lines(), code_str:: I, code_len:2, str:F: I
- mgcp_parse_parameter_lines(str:F: I) -num_toks: 28
- mgcp_parse_parameter_lines() check NULL str(I), in_ptr(F: I)
- mgcp_parse_parameter_lines() return Parse function in mgcp_parm_rules_array[14]
- mgcp_parse_req_info(I) is called
- mgcp_parse_req_info() - tmp_ptr:(I)
- SUCCESS: Request Info parameter line (F:) parsing OK
- mgcp_val_mandatory_parms()
Related Commands

Command

Description

debug mgcp all

Enables all debug traces for MGCP.

debug mgcp endpoint

Enables debug traces for a specific MGCP endpoint.

mgcp

Starts the MGCP daemon.

mgcp debug-header

Enables the display of MGCP module-dependent information in the debug header.

show mgcp

Displays MGCP configuration information.

voice call debug

Specifies the format of the debug header.

debug mgcp events

To enable debug traces for Media Gateway Control Protocol (MGCP) events, use the debug mgcp events command in privileged EXEC mode. To disable debugging output, use the no form of this command.

debug mgcp events [tracelevel {critical | moderate | verbose}]
no debug mgcp events
Syntax Description

tracelevel

(Optional) Sets the priority level for this debug trace.

•critical—Displays only high-priority debug information.

•moderate—Displays medium- and high-priority debug information.

•verbose—Displays all debug information. This is the default level.

Command Default

MGCP events debugging is disabled.

Command Modes

Privileged EXEC

Command History

Release

Modification

12.1(1)T

This command was introduced.

12.1(3)T

Additional information was displayed for the gateways.

12.1(5)XM

The output was modified to display parameters for the MGCP channel-associated signaling (CAS) PBX and ATM adaptation layer 2 (AAL2) permanent virtual circuit (PVC) features.

12.2(2)T

The output was modified to display parameters for the MGCP channel-associated signaling (CAS) PBX and ATM adaptation layer 2 (AAL2) permanent virtual circuit (PVC) features.

12.2(2)XA

The endpoint endpoint-name keyword and argument were added.

12.2(11)T

This command was implemented on the Cisco AS5350, Cisco AS5400, and Cisco AS5850.

12.2(13)T

This command was implemented on the Cisco 7200 series images.

12.4(4)T

The endpoint endpoint-name keyword and argument were removed and replaced by the debug mgcp endpoint command. The tracelevel keyword was added.

Usage Guidelines

This command enables events debugging globally for all MGCP endpoints. You can limit debugging to a specific endpoint by using the debug mgcp endpoint command.

Trace levels allow you to control the amount of debug information that is displayed in the output from MGCP debug commands. Reducing the amount of output displayed on the console port makes it easier to locate the correct debug information and limits the impact to network performance.

Examples

The following is sample output from the debug mgcp events command:

Router# debug mgcp events

Media Gateway Control Protocol events debugging for all endpoints is on, trace-level Verbose

Router#
*Sep 10 09:22:41.276: //-1/xxxxxxxxxxxx/MGCP/mgcpapp_stw_call_back(316):[lvl=0]timer type 1
*Sep 10 09:22:41.276: //-1/xxxxxxxxxxxx/MGCP/mgcpapp_process_timers(1431):[lvl=0]timer of type 1 expired.
*Sep 10 09:22:41.276: //-1/xxxxxxxxxxxx/MGCP|aaln/S2/SU1/1|-1|-1/mgcp_remove_old_ack(712):[lvl=1]Removing ack: (trans ID 15) : 250 15 OK
P: PS=0, OS=0, PR=0, OR=0, PL=0, JI=0, LA=0

*Sep 10 09:22:42.300: //-1/xxxxxxxxxxxx/MGCP/mgcp_count_active_mgc_msg_stat(240):[lvl=1]MGC stat - 192.168.1.200, total=18, succ=14, failed=2
*Sep 10 09:22:42.300: //-1/xxxxxxxxxxxx/MGCP/mgcpapp_process_mgcp_msg(3318):[lvl=0] : <NEW MGCP MSG From CA>
*Sep 10 09:22:42.300: //-1/xxxxxxxxxxxx/MGCP/mgcp_endpt_get_endpt_offset(2590):[lvl=0]endpt NULL
*Sep 10 09:22:42.300: //-1/xxxxxxxxxxxx/MGCP|aaln/S2/SU1/1|-1|-1/mgcpapp_setup_per_call_data(2487):[lvl=1]mgcpap p_setup_per_call_data: callp: 63E313E0, vdbptr: 65822AF8, state: CALL_IDLE
*Sep 10 09:22:42.300: //-1/xxxxxxxxxxxx/MGCP/mgcp_endpt_get_notified_entity(439):[lvl=0]Entered
*Sep 10 09:22:42.300: //-1/xxxxxxxxxxxx/MGCP/mgcp_endpt_get_notified_entity(458):[lvl=1]ne callagenthost:7979, ne addr 192.168.1.200:7979
*Sep 10 09:22:42.300: //-1/xxxxxxxxxxxx/MGCP/xlate_mgcp_ev(921):[lvl=1]hdr_type 1
*Sep 10 09:22:42.300: //-1/xxxxxxxxxxxx/MGCP|aaln/S2/SU1/1|-1|-1/mgcpapp_process_mgcp_event(2615):[lvl=1]Process ing Incoming Message [CRCX 16]
*Sep 10 09:22:42.300: //-1/xxxxxxxxxxxx/MGCP|aaln/S2/SU1/1|-1|-1/mgcpapp_invoke_mgcp_sm(2559):[lvl=1]Msg In-Progress(Active) [INVVERB 0], await_ev=0, queued=0x00000000
*Sep 10 09:22:42.300: //-1/xxxxxxxxxxxx/MGCP|aaln/S2/SU1/1|-1|-1/mgcp_process_deferred_queue(3362):[lvl=0]Entere d
*Sep 10 09:22:42.300: //-1/xxxxxxxxxxxx/MGCP/mgcp_store_endpt_and_ntfy_entity_name(4464):[lvl=0]Entered
*Sep 10 09:22:42.300: //-1/xxxxxxxxxxxx/MGCP|aaln/S2/SU1/1|-1|-1/mgcp_invoke_app_sm(535):[lvl=0]MGCP:calling FSM- callp(63E313E0)
*Sep 10 09:22:42.300: //-1/xxxxxxxxxxxx/MGCP|aaln/S2/SU1/1|-1|-1/mgcp_idle_crcx(4875):[lvl=2]callp(0x63E313E0), current state CALL_IDLE, event EV_CREATE_CONN
*Sep 10 09:22:42.300: //-1/xxxxxxxxxxxx/MGCP/mgcp_init_modem_relay_params(103):[lvl=0]modem-relay-enabled=0, mr-gw-xid=0
*Sep 10 09:22:42.300: //-1/xxxxxxxxxxxx/MGCP|aaln/S2/SU1/1|-1|-1/mgcp_compute_debugsy_hdr(274):[lvl=0]Building Debugsy header
*Sep 10 09:22:42.300: //-1/C537F3F38008/MGCP|aaln/S2/SU1/1|-1|-1/<VOICE>/mgcp_compute_debugsy_hdr(383):[lvl=0]GU ID[C537F3F38008] assigned to call_id[-1], endpt[aaln/S2/SU1/1], mgcp_call_id[n/a], conn_id[0]
*Sep 10 09:22:42.300: //-1/C537F3F38008/MGCP|aaln/S2/SU1/1|-1|-1/<VOICE>/mgcp_idle_crcx(4961):[lvl=0]calls mgcp_allocate_if()
*Sep 10 09:22:42.300: //-1/C537F3F38008/MGCP|aaln/S2/SU1/1|-1|-1/<VOICE>/mgcp_idle_crcx(5006):[lvl=1]get capability
*Sep 10 09:22:42.300: //-1/C537F3F38008/MGCP|aaln/S2/SU1/1|-1|-1/<VOICE>/mgcp_compute_debugsy_hdr(274):[lvl=0]Bu ilding Debugsy header
*Sep 10 09:22:42.304: //-1/C537F3F38008/MGCP|aaln/S2/SU1/1|-1|-1/<VOICE>/mgcp_compute_debugsy_hdr(383):[lvl=0]GU ID[C537F3F38008] assigned to call_id[-1], endpt[aaln/S2/SU1/1], mgcp_call_id[1], conn_id[0]
*Sep 10 09:22:42.304: //-1/C537F3F38008/MGCP|aaln/S2/SU1/1|-1|-1/<VOICE>/mgcp_idle_crcx(5093):[lvl=0]Default aal2 vc = 1 1-pvc,2-svc
*Sep 10 09:22:42.304: //-1/xxxxxxxxxxxx/MGCP/mgcp_init_vox_if_record(6781):[lvl=0]reusing records. conn_type: 2, vox if_type: 1
*Sep 10 09:22:42.304: //-1/xxxxxxxxxxxx/MGCP/mgcp_compute_debugsy_hdr(274):[lvl=0]Building Debugsy header
Related Commands

Command

Description

debug mgcp all

Enables all debug traces for MGCP.

debug mgcp endpoint

Enables debug traces for a specific MGCP endpoint.

debug mgcp tracelevel-default

Sets the trace level globally for all MGCP debug traces.

mgcp

Starts the MGCP daemon.

mgcp debug-header

Enables the display of MGCP module-dependent information in the debug header.

show mgcp

Displays MGCP configuration information.

voice call debug

Specifies the format of the debug header.

debug mgcp gcfm

To enable generic call filter module (GCFM) debug traces for Media Gateway Control Protocol (MGCP), use the debug mgcp gcfm command in privileged EXEC mode. To disable debugging output, use the no form of this command.

debug mgcp gcfm [tracelevel {critical | moderate | verbose}]
no debug mgcp gcfm
Syntax Description

tracelevel

(Optional) Sets the priority level for this debug trace.

•critical—Displays only high-priority debug information.

•moderate—Displays medium- and high-priority debug information.

•verbose—Displays all debug information. This is the default level.

Command Default

MGCP GCFM debugging is disabled.

Command Modes

Privileged EXEC

Command History

Release

Modification

12.4(4)T

This command was introduced.

Usage Guidelines

This command enables GCFM debugging globally for all MGCP endpoints.

Trace levels allow you to control the amount of debug information that is displayed in the output from MGCP debug commands. Reducing the amount of output displayed on the console port makes it easier to locate the correct debug information and limits the impact to network performance.

Examples

The following is sample output from the debug mgcp gcfm command:

Router# debug mgcp gcfm

Media Gateway Control Protocol gcfm debugging for all endpoints is on, trace-level Verbose

Router#
*Sep 10 09:24:52.692: //-1/12F030978009/MGCP|aaln/S2/SU1/1|-1|-1/<VOICE>/mgcp_gcfm_percall_register(315):[lvl=2] GCFM Inactive
*Sep 10 09:24:52.692: //-1/12F030978009/MGCP|aaln/S2/SU1/1|-1|-1/<VOIP>/mgcp_gcfm_percall_register(315):[lvl=2]G CFM Inactive
Router#
Related Commands

Command

Description

debug call filter inout

Displays the debug trace inside the GCFM.

debug mgcp endpoint

Enables debug traces for a specific MGCP endpoint.

debug mgcp tracelevel-default

Sets the trace level globally for all MGCP debug traces.

mgcp

Starts the MGCP daemon.

mgcp debug-header

Enables the display of MGCP module-dependent information in the debug header.

show mgcp

Displays MGCP configuration information.

voice call debug

Specifies the format of the debug header.

debug mgcp inout

To enable debug traces for all Media Gateway Control Protocol (MGCP) entry and exit endpoints, use the debug mgcp inout command in privileged EXEC mode. To disable debugging output, use the no form of this command.

debug mgcp inout [tracelevel {critical | moderate | verbose}]
no debug mgcp inout
Syntax Description

tracelevel

(Optional) Sets the priority level for this debug trace.

•critical—Displays only high-priority debug information.

•moderate—Displays medium- and high-priority debug information.

•verbose—Displays all debug information. This is the default level.

Command Default

Debugging of MGCP entry and exit endpoints is disabled.

Command Modes

Privileged EXEC

Command History

Release

Modification

12.4(4)T

This command was introduced.

Usage Guidelines

Trace levels allow you to control the amount of debug information that is displayed in the output from MGCP debug commands. Reducing the amount of output displayed on the console port makes it easier to locate the correct debug information and limits the impact to network performance.

Examples

The following is sample output from the debug mgcp inout command:

Router# debug mgcp inout

Media Gateway Control Protocol inout debugging for all endpoints is on, trace-level Verbose

Router#
*Sep 10 09:26:37.780: //-1/xxxxxxxxxxxx/MGCP/mgcp_count_active_mgc_msg_stat(240):[lvl=1]MGC stat - 192.168.1.200, total=22, succ=18, failed=2
*Sep 10 09:26:37.780: //-1/xxxxxxxxxxxx/MGCP/mgcp_parse_packet(316):[lvl=0]call mgcp_parse_header

*Sep 10 09:26:37.780: //-1/xxxxxxxxxxxx/MGCP/mgcp_string_parse(186):[lvl=0]return code=1.
*Sep 10 09:26:37.780: //-1/xxxxxxxxxxxx/MGCP/mgcp_parse_conn_mode(4762):[lvl=0](in_ptr: recvonly)

*Sep 10 09:26:37.780: //-1/xxxxxxxxxxxx/MGCP/mgcp_parse_conn_mode(4894):[lvl=0]SUCCESS: Connection Mode parsing is OK

*Sep 10 09:26:37.780: //-1/xxxxxxxxxxxx/MGCP/mgcp_string_parse(186):[lvl=0]return code=1.
*Sep 10 09:26:37.784: //-1/xxxxxxxxxxxx/MGCP/mgcp_parse_call_id(840):[lvl=0]in_ptr: 1

*Sep 10 09:26:37.784: //-1/xxxxxxxxxxxx/MGCP/mgcp_parse_call_id(883):[lvl=1]SUCCESS: Call ID string(1) parsing is OK

*Sep 10 09:26:37.784: //-1/xxxxxxxxxxxx/MGCP/mgcp_val_mandatory_parms(12428):[lvl=0]Entered
*Sep 10 09:26:37.784: //-1/xxxxxxxxxxxx/MGCP/xgcp_endpt_name_parse_a(1339):[lvl=0]aaln/S2/SU1/1
*Sep 10 09:26:37.784: //-1/xxxxxxxxxxxx/MGCP/xgcp_endpt_name_parse_aaln_slot(1632):[lvl=0]2/SU1/1
*Sep 10 09:26:37.784: //-1/xxxxxxxxxxxx/MGCP/xgcp_endpt_name_parse_digit(1600):[lvl=0]2/SU1/1
*Sep 10 09:26:37.784: //-1/xxxxxxxxxxxx/MGCP/xgcp_endpt_name_parse_aaln_su(1773):[lvl=0]1/1
*Sep 10 09:26:37.784: //-1/xxxxxxxxxxxx/MGCP/xgcp_endpt_name_parse_digit(1600):[lvl=0]1/1
*Sep 10 09:26:37.784: //-1/xxxxxxxxxxxx/MGCP/xgcp_endpt_name_parse_aaln_port(1807):[lvl=0]1
*Sep 10 09:26:37.784: //-1/xxxxxxxxxxxx/MGCP/xgcp_endpt_name_parse_digit(1600):[lvl=0]1
*Sep 10 09:26:37.784: //-1/xxxxxxxxxxxx/MGCP/mgcp_endpt_get_endpt_offset(2590):[lvl=0]endpt NULL
*Sep 10 09:26:37.784: //-1/xxxxxxxxxxxx/MGCP/xgcp_endpt_get_by_ifn(1326):[lvl=0]Entered
*Sep 10 09:26:37.784: //-1/xxxxxxxxxxxx/MGCP/xgcp_endpt_get_tree_link_by_ifn(1145):[lvl=0]Entered
*Sep 10 09:26:37.784: //-1/xxxxxxxxxxxx/MGCP/xgcp_endpt_compute_key(196):[lvl=0]type 2 slot 0002 subunit 0001
*Sep 10 09:26:37.784: //-1/xxxxxxxxxxxx/MGCP/xgcp_endpt_get_state(3758):[lvl=0]endpt aaln/S2/SU1/1
*Sep 10 09:26:37.784: //-1/xxxxxxxxxxxx/MGCP/xgcp_endpt_default_get_state(3779):[lvl=0]endpt aaln/S2/SU1/1
*Sep 10 09:26:37.784: //-1/xxxxxxxxxxxx/MGCP/mgcp_endpt_get_notified_entity(439):[lvl=0]Entered
*Sep 10 09:26:37.784: //-1/xxxxxxxxxxxx/MGCP/mgcp_endpt_get_notified_entity(458):[lvl=1]ne callagenthost:7979, ne addr 192.168.1.200:7979
*Sep 10 09:26:37.784: //-1/xxxxxxxxxxxx/MGCP/xlate_mgcp_ev(921):[lvl=1]hdr_type 1
*Sep 10 09:26:37.784: //-1/xxxxxxxxxxxx/MGCP|aaln/S2/SU1/1|-1|-1/mgcpapp_invoke_mgcp_sm(2559):[lvl=1]Msg In-Progress(Active) [INVVERB 0], await_ev=0, queued=0x00000000
*Sep 10 09:26:37.784: //-1/xxxxxxxxxxxx/MGCP|aaln/S2/SU1/1|-1|-1/mgcp_process_deferred_queue(3362):[lvl=0]Entere d
*Sep 10 09:26:37.784: //-1/xxxxxxxxxxxx/MGCP/mgcp_store_endpt_and_ntfy_entity_name(4464):[lvl=0]Entered
*Sep 10 09:26:37.784: //-1/xxxxxxxxxxxx/MGCP|aaln/S2/SU1/1|-1|-1/mgcp_idle_crcx(4875):[lvl=2]callp(0x63E313E0), current state CALL_IDLE, event EV_CREATE_CONN
*Sep 10 09:26:37.784: //-1/xxxxxxxxxxxx/MGCP/mgcp_init_modem_relay_params(103):[lvl=0]modem-relay-enabled=0, mr-gw-xid=0
*Sep 10 09:26:37.784: //-1/xxxxxxxxxxxx/MGCP|aaln/S2/SU1/1|-1|-1/mgcp_compute_debugsy_hdr(274):[lvl=0]Building Debugsy header
*Sep 10 09:26:37.784: //-1/5193F3E0800A/MGCP|aaln/S2/SU1/1|-1|-1/<VOICE>/mgcp_compute_debugsy_hdr(383):[lvl=0]GU ID[5193F3E0800A] assigned to call_id[-1], endpt[aaln/S2/SU1/1], mgcp_call_id[n/a], conn_id[0]
*Sep 10 09:26:37.784: //-1/5193F3E0800A/MGCP|aaln/S2/SU1/1|-1|-1/<VOICE>/mgcp_verify_supp_reqdet_ev(10645):[lvl= 0]Entered
*Sep 10 09:26:37.784: //-1/5193F3E0800A/MGCP|aaln/S2/SU1/1|-1|-1/<VOICE>/mgcp_verify_supp_signal_ev(10685):[lvl= 0]Entered
*Sep 10 09:26:37.784: //-1/5193F3E0800A/MGCP|aaln/S2/SU1/1|-1|-1/<VOICE>/mgcp_compute_debugsy_hdr(274):[lvl=0]Bu ilding Debugsy header
Related Commands

Command

Description

debug mgcp all

Enables all debug traces for MGCP.

debug mgcp tracelevel-default

Sets the trace level globally for all MGCP debug traces.

mgcp

Starts the MGCP daemon.

mgcp debug-header

Enables the display of MGCP module-dependent information in the debug header.

show mgcp

Displays MGCP configuration information.

voice call debug

Specifies the format of the debug header.

debug mgcp media

To enable debug traces for Media Gateway Control Protocol (MGCP) tone and signal events, use the debug mgcp media command in privileged EXEC mode. To disable debugging output, use the no form of this command.

debug mgcp media [tracelevel {critical | moderate | verbose}]
no debug mgcp media
Syntax Description

tracelevel

(Optional) Sets the priority level for this debug trace.

•critical—Displays only high-priority debug information.

•moderate—Displays medium- and high-priority debug information.

•verbose—Displays all debug information. This is the default level.

Command Default

MGCP media debugging is disabled.

Command Modes

Privileged EXEC

Command History

Release

Modification

12.2(2)XA

This command was introduced.

12.2(11)T

This command was implemented on the Cisco AS5350, Cisco AS5400, and Cisco AS5850.

12.2(13)T

This command was implemented on the Cisco 7200 series images.

12.4(4)T

The endpoint endpoint-name keyword and argument were removed and replaced by the debug mgcp endpoint command. The tracelevel keyword was added.

Usage Guidelines

This command enables media debugging globally for all MGCP endpoints. You can limit debugging to a specific endpoint by using the debug mgcp endpoint command.

Trace levels allow you to control the amount of debug information that is displayed in the output from MGCP debug commands. Reducing the amount of output displayed on the console port makes it easier to locate the correct debug information and limits the impact to network performance.

Examples

The following is sample output from the debug mgcp media command:

Router# debug mgcp media

Media Gateway Control Protocol media events debugging for all endpoints is on, trace-level Verbose

Router#
*Sep 10 09:27:48.928: //-1/7BFBA9F9800B/MGCP|aaln/S2/SU1/1|-1|-1/<VOICE>/mgcp_verify_supp_reqdet_ev(10645):[lvl= 0]Entered
*Sep 10 09:27:48.928: //-1/7BFBA9F9800B/MGCP|aaln/S2/SU1/1|-1|-1/<VOICE>/mgcp_verify_supp_signal_ev(10685):[lvl= 0]Entered
*Sep 10 09:27:48.928: //-1/7BFBA9F9800B/MGCP|aaln/S2/SU1/1|-1|-1/<VOICE>/process_request_ev(5800):[lvl=1]callp 63E313E0, voice_if 6663CA38
*Sep 10 09:27:48.928: //-1/7BFBA9F9800B/MGCP|aaln/S2/SU1/1|-1|-1/<VOICE>/process_detect_ev(6007):[lvl=0]callp 63E313E0, voice_if 6663CA38
*Sep 10 09:27:48.928: //-1/7BFBA9F9800B/MGCP|aaln/S2/SU1/1|-1|-1/<VOICE>/process_signal_ev(5500):[lvl=0]callp 63E313E0, voice_ifp 6663CA38
*Sep 10 09:27:48.928: //-1/7BFBA9F9800B/MGCP|aaln/S2/SU1/1|-1|-1/<VOICE>/mgcp_process_quarantine_mode(6096):[lvl =0]callp 63E313E0, voice_if 6663CA38
*Sep 10 09:27:48.928: //-1/7BFBA9F9800B/MGCP|aaln/S2/SU1/1|-1|-1/<VOICE>/mgcp_process_quarantine_mode(6149):[lvl =0]Q mode not found, Reset default values
*Sep 10 09:27:48.928: //-1/7BFBA9F9800B/MGCP|aaln/S2/SU1/1|-1|-1/<VOICE>/mgcp_process_quarantine_mode(6168):[lvl =1]Q mode: process=0, loop=0
*Sep 10 09:27:48.936: //19/7BFBA9F9800B/MGCP|aaln/S2/SU1/1|-1|-1/<VOICE>/mgcp_process_pending_t38_port_switch(16 49):[lvl=1]conn_recp->conn_id: 0x0
*Sep 10 09:27:48.940: //19/7BFBA9F9800B/MGCP|aaln/S2/SU1/1|-1|-1/<VOICE>/process_deferred_request_events(5724):[ lvl=0]Entered
Related Commands

Command

Description

debug mgcp all

Enables all debug traces for MGCP.

debug mgcp endpoint

Enables debug traces for a specific MGCP endpoint.

debug mgcp tracelevel-default

Sets the trace level globally for all MGCP debug traces.

mgcp

Starts the MGCP daemon.

mgcp debug-header

Enables the display of MGCP module-dependent information in the debug header.

show mgcp

Displays MGCP configuration information.

voice call debug

Specifies the format of the debug header.

debug mgcp nas

To enable network access server (NAS) (data) events for Media Gateway Control Protocol (MGCP), use the debug mgcp nas command in privileged EXEC mode. To disable debugging output, use the no form of this command.

debug mgcp nas [tracelevel {critical | moderate | verbose}]
no debug mgcp nas
Syntax Description

tracelevel

(Optional) Sets the priority level for this debug trace.

•critical—Displays only high-priority debug information.

•moderate—Displays medium- and high-priority debug information.

•verbose—Displays all debug information. This is the default level.

Command Default

MGCP NAS event debugging is disabled.

Command Modes

Privileged EXEC

Command History

Release

Modification

12.2(2)XB

This command was introduced.

12.2(11)T

This command was implemented on the Cisco AS5350, Cisco AS5400, and Cisco AS5850.

12.2(13)T

This command was implemented on the Cisco 7200 series images.

12.4(4)T

The tracelevel keyword was added.

Usage Guidelines

Trace levels allow you to control the amount of debug information that is displayed in the output from MGCP debug commands. Reducing the amount of output displayed on the console port makes it easier to locate the correct debug information and limits the impact to network performance.

Examples

The following is sample output for the debug mgcp nas command with the debug mgcp packets command also enabled:

Router# debug mgcp nas

Media Gateway Control Protocol nas pkg events debugging for all endpoints is on, trace-level Verbose

Router# debug mgcp packets

Media Gateway Control Protocol packets debugging for all endpoints is on

Router#
*Sep 10 11:51:41.863: MGCP Packet received from 192.168.1.200:7979--->
CRCX 34 aaln/S2/SU1/1 MGCP 1.0
X:57
M: nas/data
C:3
L:b:64, nas/bt:modem, nas/cdn:3000, nas/cgn:1000

C: 1
<---

*Sep 10 11:51:41.863: //-1/xxxxxxxxxxxx/MGCP/mgcp_chq_nas_pkg(779):[lvl=0]Full string: nas/bt:modem

*Sep 10 11:51:41.863: //-1/xxxxxxxxxxxx/MGCP/mgcp_chq_nas_pkg(791):[lvl=1]string past slash: bt

*Sep 10 11:51:41.863: //-1/xxxxxxxxxxxx/MGCP/mgcp_chq_nas_pkg(792):[lvl=1]string past colon: modem

*Sep 10 11:51:41.863: //-1/xxxxxxxxxxxx/MGCP/mgcp_chq_nas_pkg(779):[lvl=0]Full string: nas/cdn:3000

*Sep 10 11:51:41.863: //-1/xxxxxxxxxxxx/MGCP/mgcp_chq_nas_pkg(791):[lvl=1]string past slash: cdn

*Sep 10 11:51:41.863: //-1/xxxxxxxxxxxx/MGCP/mgcp_chq_nas_pkg(792):[lvl=1]string past colon: 3000

*Sep 10 11:51:41.863: //-1/xxxxxxxxxxxx/MGCP/mgcp_chq_nas_pkg(779):[lvl=0]Full string: nas/cgn:1000

*Sep 10 11:51:41.863: //-1/xxxxxxxxxxxx/MGCP/mgcp_chq_nas_pkg(791):[lvl=1]string past slash: cgn

*Sep 10 11:51:41.863: //-1/xxxxxxxxxxxx/MGCP/mgcp_chq_nas_pkg(792):[lvl=1]string past colon: 1000
Related Commands

Command

Description

debug mgcp all

Enables all debug traces for MGCP.

debug mgcp tracelevel-default

Sets the trace level globally for all MGCP debug traces.

mgcp

Starts the MGCP daemon.

mgcp debug-header

Enables the display of MGCP module-dependent information in the debug header.

show mgcp

Displays MGCP configuration information.

voice call debug

Specifies the format of the debug header.

debug mgcp packets

To enable debug traces for Media Gateway Control Protocol (MGCP) packets, use the debug mgcp packets command in privileged EXEC mode. To disable debugging output, use the no form of this command.

debug mgcp packets [input-hex]
no debug mgcp packets [input-hex]
Syntax Description

input-hex

(Optional) Displays MGCP incoming packets in hexadecimal format.

Command Default

MGCP packets debugging is disabled.

Command Modes

Privileged EXEC

Command History

Release

Modification

12.1(1)T

This command was introduced.

12.1(3)T

Additional information was displayed for the gateways.

12.1(5)XM

The output was modified to display parameters for the MGCP channel-associated signaling (CAS) PBX and ATM adaptation layer 2 (AAL2) permanent virtual circuit (PVC) features.

12.2(2)T

The output was modified to display parameters for the MGCP channel-associated signaling (CAS) PBX and ATM adaptation layer 2 (AAL2) permanent virtual circuit (PVC) features.

12.2(2)XA

The endpoint endpoint-name keyword and argument and the input-hex keyword were added.

12.2(11)T

This command was implemented on the Cisco AS5350, Cisco AS5400, and Cisco AS5850.

12.2(13)T

This command was implemented on the Cisco 7200 series images.

12.4(4)T

The endpoint endpoint-name keyword and argument were removed and replaced by the debug mgcp endpoint command.

Usage Guidelines

This command enables packet debugging globally for all MGCP endpoints. You can limit debugging to a specific endpoint by using the debug mgcp endpoint command.

Trace levels allow you to control the amount of debug information that is displayed in the output from MGCP debug commands. Reducing the amount of output displayed on the console port makes it easier to locate the correct debug information and limits the impact to network performance.

Examples

The following is sample output from the debug mgcp packets command:

Router# debug mgcp packets

Media Gateway Control Protocol packets debugging for all endpoints is on

Router#
*Sep 10 11:57:26.795: MGCP Packet received from 192.168.1.200:7979--->
CRCX 38 aaln/S2/SU1/1 MGCP 1.0
M: recvonly
C: 1
<---

*Sep 10 11:57:26.795: //-1/xxxxxxxxxxxx/MGCP|aaln/S2/SU1/1|-1|-1/mgcpapp_invoke_mgcp_sm(2569):[lvl=0]CHECK DATA CALL for aaln/S2/SU1/1

*Sep 10 11:57:26.807: MGCP Packet sent to 192.168.1.200:7979--->
200 38 OK
I: 10

v=0
c=IN IP4 192.168.1.79
m=audio 18876 RTP/AVP 0 8 99 101 102 2 15 103 4 104 105 106 107 18 100
a=rtpmap:99 G.729a/8000
a=rtpmap:101 G.726-16/8000
a=rtpmap:102 G.726-24/8000
a=rtpmap:103 G.723.1-H/8000
a=rtpmap:104 G.723.1-L/8000
a=rtpmap:105 G.729b/8000
a=rtpmap:106 G.723.1a-H/8000
a=rtpmap:107 G.723.1a-L/8000
a=rtpmap:100 X-NSE/8000
a=fmtp:100 200-202
a=X-sqn:0
a=X-cap: 1 audio RTP/AVP 100
a=X-cpar: a=rtpmap:100 X-NSE/8000
a=X-cpar: a=fmtp:100 200-202
a=X-cap: 2 image udptl t38
<---
Related Commands

Command

Description

debug mgcp all

Enables all debug traces for MGCP.

debug mgcp endpoint

Enables debug traces for a specific MGCP endpoint.

debug mgcp tracelevel-default

Sets the trace level globally for all MGCP debug traces.

mgcp

Starts the MGCP daemon.

mgcp debug-header

Enables the display of MGCP module-dependent information in the debug header.

show mgcp

Displays MGCP configuration information.

voice call debug

Specifies the format of the debug header.

debug mgcp parser

To enable debug traces for the Media Gateway Control Protocol (MGCP) parser and builder, use the debug mgcp parser command in privileged EXEC mode. To disable debugging output, use the no form of this command.

debug mgcp parser [tracelevel {critical | moderate | verbose}]
no debug mgcp parser
Syntax Description

tracelevel

(Optional) Sets the priority level for this debug trace.

•critical—Displays only high-priority debug information.

•moderate—Displays medium- and high-priority debug information.

•verbose—Displays all debug information. This is the default level.

Command Default

MGCP parser and builder debugging is disabled.

Command Modes

Privileged EXEC

Command History

Release

Modification

12.1(1)T

This command was introduced.

12.1(3)T

Additional information was displayed for the gateways.

12.1(5)XM

The output was modified to display parameters for the MGCP channel-associated signaling (CAS) PBX and ATM adaptation layer 2 (AAL2) permanent virtual circuit (PVC) features.

12.2(2)T

The output was modified to display parameters for the MGCP channel-associated signaling (CAS) PBX and ATM adaptation layer 2 (AAL2) permanent virtual circuit (PVC) features.

12.2(11)T

This command was implemented on the Cisco AS5350, Cisco AS5400, and Cisco AS5850.

12.2(13)T

This command was implemented on the Cisco 7200 series images.

12.4(4)T

The tracelevel keyword was added.

Usage Guidelines

Trace levels allow you to control the amount of debug information that is displayed in the output from MGCP debug commands. Reducing the amount of output displayed on the console port makes it easier to locate the correct debug information and limits the impact to network performance.

Examples

The following is sample output from the debug mgcp parser command:

Router# debug mgcp parser

Media Gateway Control Protocol parser debugging for all endpoints is on, trace-level Verbose

Router#
*Sep 10 11:58:51.283: //-1/xxxxxxxxxxxx/MGCP/mgcp_parse_packet(316):[lvl=0]call mgcp_parse_header

*Sep 10 11:58:51.283: //-1/xxxxxxxxxxxx/MGCP/mgcp_parse_packet(320):[lvl=0]out mgcp_parse_header

*Sep 10 11:58:51.283: //-1/xxxxxxxxxxxx/MGCP/mgcp_parse_packet(360):[lvl=1]SUCCESS: - MGCP Header parsing was OK

*Sep 10 11:58:51.283: //-1/xxxxxxxxxxxx/MGCP/mgcp_string_parse(186):[lvl=0]return code=1.
*Sep 10 11:58:51.283: //-1/xxxxxxxxxxxx/MGCP/mgcp_parse_parameter_lines(725):[lvl=1]return parse function in mgcp_parm_rules_array[6].
*Sep 10 11:58:51.283: //-1/xxxxxxxxxxxx/MGCP/mgcp_parse_conn_mode(4762):[lvl=0](in_ptr: recvonly)

*Sep 10 11:58:51.283: //-1/xxxxxxxxxxxx/MGCP/mgcp_parse_conn_mode(4780):[lvl=0]tmp_ptr:(recvonly)

*Sep 10 11:58:51.283: //-1/xxxxxxxxxxxx/MGCP/mgcp_parse_conn_mode(4816):[lvl=0]tmp_ptr:(recvonly)

*Sep 10 11:58:51.283: //-1/xxxxxxxxxxxx/MGCP/mgcp_parse_conn_mode(4822):[lvl=0]match recvonly recvonly

*Sep 10 11:58:51.283: //-1/xxxxxxxxxxxx/MGCP/mgcp_parse_conn_mode(4830):[lvl=0]case MODE_RECVONLY

*Sep 10 11:58:51.283: //-1/xxxxxxxxxxxx/MGCP/mgcp_parse_conn_mode(4894):[lvl=0]SUCCESS: Connection Mode parsing is OK

*Sep 10 11:58:51.283: //-1/xxxxxxxxxxxx/MGCP/mgcp_string_parse(186):[lvl=0]return code=1.
*Sep 10 11:58:51.283: //-1/xxxxxxxxxxxx/MGCP/mgcp_parse_parameter_lines(725):[lvl=1]return parse function in mgcp_parm_rules_array[1].
*Sep 10 11:58:51.283: //-1/xxxxxxxxxxxx/MGCP/mgcp_parse_call_id(840):[lvl=0]in_ptr: 1

*Sep 10 11:58:51.283: //-1/xxxxxxxxxxxx/MGCP/mgcp_parse_call_id(883):[lvl=1]SUCCESS: Call ID string(1) parsing is OK

*Sep 10 11:58:51.283: //-1/xxxxxxxxxxxx/MGCP/mgcp_val_mandatory_parms(12428):[lvl=0]Entered
*Sep 10 11:58:51.283: //-1/xxxxxxxxxxxx/MGCP/mgcp_val_comp_mp_parms(14923):[lvl=0]Entered
*Sep 10 11:58:51.283: //-1/xxxxxxxxxxxx/MGCP/mgcp_val_comp_mp_parms(14928):[lvl=1] - lcon_opt_ptr could not be obtained
*Sep 10 11:58:51.283: //-1/xxxxxxxxxxxx/MGCP/mgcp_parse_packet(378):[lvl=2]SUCCESS: END of Parsing
*Sep 10 11:58:51.283: //-1/95915C328011/MGCP|aaln/S2/SU1/1|-1|-1/<VOICE>/mgcp_validate_version_with_call_agent_s erv_type(8322):[lvl=1]req_msg_version: 5, config_version: 5
*Sep 10 11:58:51.283: //-1/xxxxxxxxxxxx/MGCP/mgcp_validate_net_type(6601):[lvl=1] lcnw_valid=0, lc_con_valid=0
*Sep 10 11:58:51.287: //-1/xxxxxxxxxxxx/MGCP/mgcp_validate_net_type(6710):[lvl=1]Network type/conection type valid = 1. connection type = 1 [1->RTP, 2->AAL1_SDT, 4->AAL2]
*Sep 10 11:58:51.287: //-1/xxxxxxxxxxxx/MGCP/mgcp_get_qos(2665):[lvl=1]MGCP msg qos value=0
*Sep 10 11:58:51.287: //-1/xxxxxxxxxxxx/MGCP/mgcp_init_dyn_payload_types(2899):[lvl=1]used payload type map = 2F400003
*Sep 10 11:58:51.287: //-1/xxxxxxxxxxxx/MGCP/get_voip_peer_info(7155):[lvl=1]No SDP connection info
*Sep 10 11:58:51.287: //-1/95915C328011/MGCP|aaln/S2/SU1/1|-1|-1/<VOIP>/mgcp_select_codec_only(897):[lvl=1]num supprt codec=14
*Sep 10 11:58:51.287: //-1/95915C328011/MGCP|aaln/S2/SU1/1|-1|-1/<VOIP>/mgcp_select_codec_only(1061):[lvl=0]glob codec=1 (syn=1)
*Sep 10 11:58:51.287: //-1/95915C328011/MGCP|aaln/S2/SU1/1|-1|-1/<VOIP>/mgcp_select_codec_only(1063):[lvl=0]supp list=
*Sep 10 11:58:51.287: //-1/95915C328011/MGCP|aaln/S2/SU1/1|-1|-1/<VOIP>/mgcp_select_codec_only(1067):[lvl=0] 1
*Sep 10 11:58:51.287: //-1/95915C328011/MGCP|aaln/S2/SU1/1|-1|-1/<VOIP>/mgcp_select_codec_only(1067):[lvl=0],2
*Sep 10 11:58:51.287: //-1/95915C328011/MGCP|aaln/S2/SU1/1|-1|-1/<VOIP>/mgcp_select_codec_only(1067):[lvl=0],7
Related Commands

Command

Description

debug mgcp all

Enables all debug traces for MGCP.

debug mgcp tracelevel-default

Sets the trace level globally for all MGCP debug traces.

mgcp

Starts the MGCP daemon.

mgcp debug-header

Enables the display of MGCP module-dependent information in the debug header.

show mgcp

Displays MGCP configuration information.

voice call debug

Specifies the format of the debug header.

debug mgcp src

To enable debug traces for the System Resource Check (SRC) Call Admission Control (CAC) process for Media Gateway Control Protocol (MGCP), use the debug mgcp src command in privileged EXEC mode. To disable debugging output, use the no form of this command.

debug mgcp src [tracelevel {critical | moderate | verbose}]
no debug mgcp src
Syntax Description

tracelevel

(Optional) Sets the priority level for this debug trace.

•critical—Displays only high-priority debug information.

•moderate—Displays medium- and high-priority debug information.

•verbose—Displays all debug information. This is the default level.

Command Default

MGCP SRC debugging is disabled.

Command Modes

Privileged EXEC

Command History

Release

Modification

12.2(2)XB

This command was introduced.

12.2(8)T

This command was integrated into Cisco IOS Release 12.2(8)T.

12.2(11)T

This command was implemented on the Cisco AS5350, Cisco AS5400, and Cisco AS5850.

12.2(13)T

This command was implemented on the Cisco 7200 series images.

12.4(4)T

The tracelevel keyword was added.

Usage Guidelines

Trace levels allow you to control the amount of debug information that is displayed in the output from MGCP debug commands. Reducing the amount of output displayed on the console port makes it easier to locate the correct debug information and limits the impact to network performance.

Examples

The following is sample output from the debug mgcp src command:

Router# debug mgcp src

Media Gateway Control Protocol System Resource Check CAC debugging for all endpoints is on, trace-level Verbose

Router#
*Sep 10 12:01:14.403: //-1/EADF209C8013/MGCP|aaln/S2/SU1/1|-1|-1/<VOIP>/mgcp_set_call_counter_control(8163):[lvl =1]Outgoing call with 1 network leg, flag=TRUE
*Sep 10 12:03:01.051: //35/EADF209C8013/MGCP|aaln/S2/SU1/1|-1|-1/<VOICE>/mgcp_reset_call_direction(8184):[lvl=1] Reseting incoming_call flag=FALSE in voice_if
Related Commands

Command

Description

debug mgcp all

Enables all debug traces for MGCP.

debug mgcp tracelevel-default

Sets the trace level globally for all MGCP debug traces.

mgcp

Starts the MGCP daemon.

mgcp debug-header

Enables the display of MGCP module-dependent information in the debug header.

show mgcp

Displays MGCP configuration information.

voice call debug

Specifies the format of the debug header.

debug mgcp state

To enable state traces for Media Gateway Control Protocol (MGCP), use the debug mgcp state command in privileged EXEC mode. To disable debugging output, use the no form of this command.

debug mgcp state [tracelevel {critical | moderate | verbose}]
no debug mgcp state
Syntax Description

tracelevel

(Optional) Sets the priority level for this debug trace.

•critical—Displays only high-priority debug information.

•moderate—Displays medium- and high-priority debug information.

•verbose—Displays all debug information. This is the default level.

Command Default

MGCP state debugging is disabled.

Command Modes

Privileged EXEC

Command History

Release

Modification

12.2(2)XB

This command was introduced.

12.2(8)T

This command was integrated into Cisco IOS Release 12.2(8)T.

12.4(4)T

The tracelevel keyword was added.

Usage Guidelines

Trace levels allow you to control the amount of debug information that is displayed in the output from MGCP debug commands. Reducing the amount of output displayed on the console port makes it easier to locate the correct debug information and limits the impact to network performance.

Examples

The following is sample output from the debug mgcp state command:

Router# debug mgcp state

Media Gateway Control Protocol state transition debugging for all endpoints is on, trace-level Verbose

Router#
*Sep 10 12:08:02.755: //39/DE454D0E8015/MGCP|aaln/S2/SU1/1|-1|-1/<VOICE>/mgcp_set_call_state(7562):[lvl=2]callp( 0x63E313E0) old state=CALL_IDLE new state=CALL_CONNECTING
*Sep 10 12:08:02.755: //40/DE454D0E8015/MGCP|aaln/S2/SU1/1|-1|-1/<VOIP>/mgcp_set_call_state(7562):[lvl=2]callp(0 x63E311D0) old state=CALL_IDLE new state=CALL_CONNECTING
*Sep 10 12:08:02.755: //39/DE454D0E8015/MGCP|aaln/S2/SU1/1|-1|-1/<VOICE>/mgcp_set_call_state(7562):[lvl=2]callp( 0x63E313E0) old state=CALL_CONNECTING new state=CALL_CONNECTING
*Sep 10 12:08:02.759: //40/DE454D0E8015/MGCP|aaln/S2/SU1/1|-1|-1/<VOIP>/mgcp_set_call_state(7562):[lvl=2]callp(0 x63E311D0) old state=CALL_CONNECTING new state=CALL_CONFERENCING
*Sep 10 12:08:02.759: //39/DE454D0E8015/MGCP|aaln/S2/SU1/1|-1|-1/<VOICE>/mgcp_set_call_state(7562):[lvl=2]callp( 0x63E313E0) old state=CALL_CONNECTING new state=CALL_CONFERENCING
*Sep 10 12:08:02.759: //40/DE454D0E8015/MGCP|aaln/S2/SU1/1|-1|-1/<VOIP>/mgcp_set_call_state(7562):[lvl=2]callp(0 x63E311D0) old state=CALL_CONFERENCING new state=CALL_CONFERENCING
*Sep 10 12:08:02.763: //39/DE454D0E8015/MGCP|aaln/S2/SU1/1|-1|-1/<VOICE>/mgcp_set_call_state(7562):[lvl=2]callp( 0x63E313E0) old state=CALL_CONFERENCING new state=CALL_ACTIVE
*Sep 10 12:08:02.763: //40/DE454D0E8015/MGCP|aaln/S2/SU1/1|-1|-1/<VOIP>/mgcp_set_call_state(7562):[lvl=2]callp(0 x63E311D0) old state=CALL_CONFERENCING new state=CALL_ACTIVE
Related Commands

Command

Description

debug mgcp all

Enables all debug traces for MGCP.

debug mgcp tracelevel-default

Sets the trace level globally for all MGCP debug traces.

mgcp

Starts the MGCP daemon.

mgcp debug-header

Enables the display of MGCP module-dependent information in the debug header.

show mgcp

Displays MGCP configuration information.

voice call debug

Specifies the format of the debug header.

debug mgcp tracelevel-default

To set the trace level globally for all Media Gateway Control Protocol (MGCP) debug traces, use the debug mgcp tracelevel-default command in privileged EXEC mode. To reset the trace level to the default value, use the no form of this command.

debug mgcp tracelevel-default {critical | moderate | verbose}
no debug mgcp tracelevel-default {critical | moderate | verbose}
Syntax Description

critical

Only high-priority debug information is displayed.

moderate

Medium- and high-priority debug information is displayed.

verbose

All debug information is displayed. This is the default value.

Command Default

The default trace level for all MGCP debug commands is verbose.

Command Modes

Privileged EXEC

Command History

Release

Modification

12.4(4)T

This command was introduced.

Usage Guidelines

Trace levels allow you to control the amount of debug information that is displayed in the output from MGCP debug commands. Reducing the amount of output displayed on the console port makes it easier to locate the correct debug information and limits the impact to network performance.

This command sets the trace level globally for all MGCP debug commands and endpoints. You can set the trace level independently for a specific endpoint by using the debug mgcp endpoint command. The endpoint-specific trace level takes precedence over the global trace level set with this command.

Note This command applies only to MGCP debug commands that are issued after the default trace level is set. For example, if you enable several debug commands and then change the default trace level, the new trace level does not apply to any previously enabled MGCP debug commands.

Examples

The following example sets the default trace level to critical for all MGCP debug traces:

Router# debug mgcp tracelevel-default critical

Router# debug mgcp events

Media Gateway Control Protocol events debugging for all endpoints is on, trace-level Critical

Router# debug mgcp state

Media Gateway Control Protocol state transition debugging for all endpoints is on, trace-level Critical

Notice that if the default trace level is then changed, as in the following example, the new trace level applies only to any MGCP debug commands that are issued after the default trace level is changed:

Router# debug mgcp tracelevel-default verbose

Router# debug mgcp voipcac

Media Gateway Control Protocol VoIPCAC debugging for all endpoints is on, trace-level Verbose

Router# show debug

MGCP:
Media Gateway Control Protocol events debugging is on, trace level Critical
Media Gateway Control Protocol VoIPCAC debugging is on, trace level Verbose
Media Gateway Control Protocol state transition debugging is on, trace level Critical
Related Commands

Command

Description

debug mgcp all

Enables all debug traces for MGCP.

debug mgcp endpoint

Enables debug traces for a specific MGCP endpoint.

mgcp debug-header

Enables the display of MGCP module-dependent information in the debug header.

show mgcp

Displays MGCP configuration information.

voice call debug

Specifies the format of the debug header.

debug mgcp voipcac

To enable debug traces for the Voice over IP (VoIP) Call Admission Control (CAC) process at the Media Gateway Control Protocol (MGCP) application layer, use the debug mgcp voipcac command in privileged EXEC mode. To disable debugging output, use the no form of this command.

debug mgcp voipcac [tracelevel {critical | moderate | verbose}]
no debug mgcp voipcac
Syntax Description

tracelevel

(Optional) Sets the priority level for this debug trace.

•critical—Displays only high-priority debug information.

•moderate—Displays medium- and high-priority debug information.

•verbose—Displays all debug information. This is the default level.

Command Default

MGCP VoIP CAC debugging is disabled.

Command Modes

Privileged EXEC

Command History

Release

Modification

12.2(2)XB

This command was introduced.

12.2(8)T

This command was integrated into Cisco IOS Release 12.2(8)T.

12.2(11)T

This command was implemented on the Cisco AS5350, Cisco AS5400, and Cisco AS5850.

12.2(13)T

This command was implemented on the Cisco 7200 series images.

12.4(4)T

The tracelevel keyword was added.

Usage Guidelines

Trace levels allow you to control the amount of debug information that is displayed in the output from MGCP debug commands. Reducing the amount of output displayed on the console port makes it easier to locate the correct debug information and limits the impact to network performance.

Examples

The following is sample output from the debug mgcp voipcac command:

Router# debug mgcp voipcac

Media Gateway Control Protocol VoIPCAC debugging for all endpoints is on, trace-level Verbose

Router#
*Sep 10 12:04:47.747: //-1/6A09713E8014/MGCP|aaln/S2/SU1/1|-1|-1/<VOICE>/mgcp_idle_crcx(5251):[lvl=0]Check for HP and QOS combination
*Sep 10 12:04:47.751: //-1/6A09713E8014/MGCP|aaln/S2/SU1/1|-1|-1/<VOICE>/mgcp_idle_crcx(5451):[lvl=0]CAC success
*Sep 10 12:04:47.751: //-1/6A09713E8014/MGCP|aaln/S2/SU1/1|-1|-1/<VOIP>/set_up_voip_call_leg(3918):[lvl=0]get voice interface
*Sep 10 12:04:47.751: //-1/6A09713E8014/MGCP|aaln/S2/SU1/1|-1|-1/<VOIP>/set_up_voip_call_leg(4441):[lvl=0]Initia lize VoIP CAC record stored in
VoIP interface struct
*Sep 10 12:04:47.751: //38/6A09713E8014/MGCP|aaln/S2/SU1/1|-1|-1/<VOIP>/mgcp_connect_peer_vox_call_leg(1546):[lv l=0]set_up_voip_call_leg returns OK
*Sep 10 12:04:47.759: //37/6A09713E8014/MGCP|aaln/S2/SU1/1|-1|-1/<VOICE>/process_signal_request_list(5608):[lvl= 0]Entered
Related Commands

Command

Description

debug mgcp all

Enables all debug traces for MGCP.

debug mgcp tracelevel-default

Sets the trace level globally for all MGCP debug traces.

mgcp

Starts the MGCP daemon.

mgcp debug-header

Enables the display of MGCP module-dependent information in the debug header.

show mgcp

Displays MGCP configuration information.

voice call debug

Specifies the format of the debug header.

debug mls rp

To display various Internetwork Packet Exchange (IPX) Multilayer Switching (MLS) debugging elements, use the debug mls rp command in privileged EXEC mode. To disable debugging output, use the no form of this command.

debug mls rp {error | events | ipx | locator | packets | all}
no debug mls rp {error | events | ipx | locator | packets | all}
Syntax Description

error

Displays MLS error messages.

events

Displays a run-time sequence of events for the Multilayer Switching Protocol (MLSP).

ipx

Displays IPX-related events for MLS, including route purging and changes to access lists and flow masks.

locator

Identifies which switch is switching a particular flow of MLS explorer packets.

packets

Displays packet contents (in verbose and hexadecimal formats) for MLSP messages.

all

Displays all MLS debugging events.

Defaults

Debugging is not enabled.

Command Modes

Privileged EXEC

Command History

Release

Modification

12.0(5)T

This command was introduced.

Examples

The following shows sample output from the debug mls rp ipx command:

Router# debug mls rp ipx

IPX MLS debugging is on
Router# conf t
Enter configuration commands, one per line. End with CNTL/Z.
Router(config)# int vlan 22
Router(config-if)# no ipx access-group out
05:44:37:FCP:flowmask changed to destination
Related Commands

Command

Description

debug dss ipx event

Displays debugging messages for route change events that affect IPX MLS.

debug mls rp ip multicast

To display information about Multilayer Switching Protocol (MLSP), use the debug mls rp ip multicast command in privileged EXEC mode. To disable debugging output, use the no form of this command.

debug mls rp ip multicast {all | error | events | packets}
no debub mls rp ip multicast {all | error | events | packets}
Syntax Description

all

Displays all multicast MLSP debugging information, including errors, events, and packets.

error

Displays error messages related to multicast MLSP.

events

Displays the run-time sequence of events for multicast MLSP.

packets

Displays the contents of MLSP packets.

Defaults

Debugging is not enabled.

Command Modes

Privileged EXEC

Command History

Release

Modification

12.0(5)T

This command was introduced.

Usage Guidelines

Only one of the keywords is required.

Examples

The following example shows output from the debug mls rp ip multicast command using the error keyword:

Router# debug mls rp ip multicast error

mlsm error debugging is on
chtang-7200#
06:06:45: MLSMERR: scb is INACTIVE, free INSTALL_FE
06:06:46: MLSM: --> mlsm_proc_sc_ins_req(10.0.0.1, 224.2.2.3, 10)

The following example shows output from the debug mls rp ip multicast command using the event keyword:

Router# debug mls rp ip multicast event

mlsm events debugging is on
Router#
3d23h: MSCP: incoming shortcut flow statistic from Fa2/0.11
3d23h: MLSM: Flow_stat: (192.1.10.6, 239.255.158.197), byte :537792
packet:8403
3d23h: MLSM: byte delta:7680 packet delta:120, time delta: 10
3d23h: MSCP: incoming shortcut flow statistic from Fa2/0.11
3d23h: MLSM: Flow_stat: (192.1.10.6, 239.255.158.197), byte :545472
packet:8523
3d23h: MLSM: byte delta:7680 packet delta:120, time delta: 10
3d23h: MSCP: Router transmits keepalive_msg on Fa2/0.11
3d23h: MSCP: incoming shortcut keepalive ACK from Fa2/0.11
3d23h: MLSM: Include-list: (192.1.2.1 -> 0.0.0.0)
3d23h: MSCP: incoming shortcut flow statistic from Fa2/0.11
3d23h: MLSM: Flow_stat: (192.1.10.6, 239.255.158.197), byte :553152
packet:8643

The following example shows output from the debug mls rp ip multicast command using the packet keyword:

Router# debug mls rp ip multicast packet

mlsm packets debugging is on
Router#
Router#
Router#
Router#
**23h: MSCP(I): 01 00 0c cc cc cc 00 e0 1e 7c fe 5f 00 30 aa aa
...LLL.`.|~_.0
..23h: MSCP(I): 03 00 00 0c 01 07 01 05 00 28 01 02 0a c7 00 10
.........(...G
..23h: MSCP(I): a6 0b b4 ff 00 00 c0 01 0a 06 ef ff 9e c5 00 00
&.4...@...o..E
3d23h: MSCP(I): 00 00 00 09 42 c0 00 00 00 00 00 00 25 0b
....B@......%.
3d23h:
**23h: MSCP(O): 01 00 0c 00 00 00 aa 00 04 00 01 04 00 00 aa aa
......*.......
LL23h: MSCP(O): 03 00 00 0c 00 16 00 00 00 00 01 00 0c cc cc cc
.............L
..23h: MSCP(O): aa 00 04 00 01 04 00 24 aa aa 03 00 00 0c 01 07
*......$**....
..23h: MSCP(O): 01 06 00 1c c0 01 02 01 aa 00 04 00 01 04 00 00
....@...*.....
3d23h: MSCP(O): 00 0b 00 00 00 00 00 00 01 01 0a 62 ...........b

3d23h:
**23h: MSCP(I): 01 00 0c cc cc cc 00 e0 1e 7c fe 5f 00 24 aa aa
...LLL.`.|~_.$
..23h: MSCP(I): 03 00 00 0c 01 07 01 86 00 1c 01 02 0a c7 00 10
.............G
..23h: MSCP(I): a6 0b b4 ff 00 00 00 0b 00 00 c0 01 02 01 00 00
..4.......@...
3d23h: MSCP(I): 00 00
3d23h:
Related Commands

Command

Description

debug mdss

Displays information about MDSS.

debug mmoip aaa

Note Effective with Release 12.3(8)T, the debug mmoip aaa command is replaced by the debug fax mmoip aaa command. See the debug fax mmoip aaa command for more information.

To display output that relates to authentication, authorization, and accounting (AAA) services with store-and-forward fax, use the debug mmoip aaa command in privileged EXEC mode. To disable debugging output, use the no form of this command.

debug mmoip aaa
no debug mmoip aaa
Syntax Description

This command has no arguments or keywords.

Defaults

No default behavior or values

Command Modes

Privileged EXEC

Command History

Release

Modification

12.0(4)T

This command was introduced.

12.2(4)T

This command was implemented on the Cisco 1750 access router.

12.3(8)T

This command was replaced by the debug fax mmoip aaa command.

Examples

The following output shows how the debug mmoip aaa command provides information about AAA for the on-ramp or off-ramp gateways:

Router# debug mmoip aaa

5d10h:fax_aaa_begin_authentication:User-Name = mmoip-b.cisco.com
5d10h:fax_aaa_begin_authentication:fax_account_id_origin = GATEWAY_ID
5d10h:fax_aaa_end_authentication_callback:Authentication successful
The following output shows how the debug mmoip aaa command provides information about AAA for the off-ramp gateway:

Router# debug mmoip aaa

5d10h:fax_aaa_start_accounting:User-Name = mmoip-b.cisco.com
5d10h:fax_aaa_start_accounting:Calling-Station-Id = gmercuri@mail-server.cisco.com
5d10h:fax_aaa_start_accounting:Called-Station-Id = fax=571-0839@mmoip-b.cisco.com
5d10h:fax_aaa_start_accounting:fax_account_id_origin = GATEWAY_ID
mmoip-b#ax_aaa_start_accounting:fax_msg_id = <37117AF3.3D98300E@mail-server.cisco.com>
5d10h:fax_aaa_start_accounting:fax_pages = 2
5d10h:fax_aaa_start_accounting:fax_coverpage_flag = TRUE
5d10h:fax_aaa_start_accounting:fax_connect_speed = 14400bps
5d10h:fax_aaa_start_accounting:fax_recipient_count = 1
5d10h:fax_aaa_start_accounting:fax_auth_status = USER SUCCESS
5d10h:fax_aaa_start_accounting:gateway_id = mmoip-b.cisco.com
5d10h:fax_aaa_start_accounting:call_type = Fax Send
5d10h:fax_aaa_start_accounting:port_used = slot:0 vfc port:0
5d10h:fax_aaa_do_offramp_accounting tty(6), Stopping accounting
5d10h:fax_aaa_stop_accounting:ftdb->cact->generic.callActiveTransmitBytes = 18038
5d10h:fax_aaa_stop_accounting:ftdb->cact->generic.callActiveTransmitPackets = 14

The following output shows how the debug mmoip aaa command provides information about AAA for the on-ramp gateway:

Router# debug mmoip aaa

5d10h:fax_aaa_start_accounting:User-Name = mmoip-b.cisco.com
5d10h:fax_aaa_start_accounting:Calling-Station-Id = FAX=408@mail-from-hostname.com
5d10h:fax_aaa_start_accounting:Called-Station-Id = FAX=5710839@mail-server.cisco.com
5d10h:fax_aaa_start_accounting:fax_account_id_origin = GATEWAY_ID
5d10h:fax_aaa_start_accounting:fax_msg_id = 00391997233216263@mmoip-b.cisco.com
5d10h:fax_aaa_start_accounting:fax_pages = 2
5d10h:fax_aaa_start_accounting:fax_connect_speed = 14400bps
5d10h:fax_aaa_start_accounting:fax_auth_status = USER SUCCESS
5d10h:fax_aaa_start_accounting:email_server_address = 1.14.116.1
5d10h:fax_aaa_start_accounting:email_server_ack_flag = TRUE
5d10h:fax_aaa_start_accounting:gateway_id = mmoip-b.cisco.com
5d10h:fax_aaa_start_accounting:call_type = Fax Receive
5d10h:fax_aaa_start_accounting:port_used = Cisco Powered Fax System slot:1 port:4
5d10h:fax_aaa_do_onramp_accounting tty(5), Stopping accounting
5d10h:fax_aaa_stop_accounting:endb->cact->generic.callActiveTransmitBytes = 26687
5d10h:fax_aaa_stop_accounting:ftdb->cact->generic.callActiveReceiveBytes = 18558
5d10h:fax_aaa_stop_accounting:ftdb->cact->generic.callActiveReceivePackets = 14
debug mmoip send email

To test connectivity between the T.37 on-ramp gateway and the e-mail server by sending a test e-mail to a specified e-mail address, use the debug mmoip send email command in privileged EXEC mode.

debug mmoip send email string
Syntax Description

string

E-mail address of the sender; for example, mailuser@mail-server.com. There is no default.

Defaults

This command is not enabled.

Command Modes

Privileged EXEC

Command History

Release

Modification

12.0(4)T

This command was introduced.

12.2(4)T

This command was introduced on the Cisco 1750 access router.

12.2(8)T

This command was implemented on the Cisco 1751 access routers, Cisco 3725 access routers, and Cisco 3745 access routers.

12.2(13)T

This feature was implemented on the Cisco 7200 series routers.

Examples

The debug mmoip send email command is used to test connectivity between the on-ramp gateway and the e-mail server. Basically, this debug command sends an e-mail message to the recipient specified in the e-mail address string. There is no specific output associated with the debug mmoip send email command; to see how the on-ramp gateway and e-mail server interact when processing the test e-mail message, enable the debug fmail client command.

The following example tests connectivity between the on-ramp gateway and the e-mail server by sending a test e-mail message to mailuser@mail-server.com:

Router# debug fmail client
Router# debug mmoip send email mailuser@mail-server.com

01:22:59:faxmail_client_send_test:Sending the test message to
ilya@mail-server.com from testing@mmoip-a.cisco.com...
01:22:59:faxmail_client_send_test:Opening client engine.
01:22:59:faxmail_client_send_test:Sending 59 bytes ...
01:22:59:faxmail_client_send_test:Done sending test email.
Related Commands

Command

Description

debug fmail client

Displays e-mail parameters (such as Mail from and Envelope to and Envelope from) and the progress of the SMTP client.

debug mmoip send fax

To send a T.37 off-ramp test fax, use the debug mmoip send fax command in privileged EXEC mode.

debug mmoip send fax string
Syntax Description

string

E.164 telephone number to be used for sending the test fax. There is no default.

Defaults

This command is not enabled.

Command Modes

Privileged EXEC

Command History

Release

Modification

12.0(4)T

This command was introduced.

12.2(4)T

This command was implemented on the Cisco 1750 access router.

12.2(8)T

This command was implemented on the Cisco 1751 access routers, Cisco 3725 access routers, and Cisco 3745 access routers.

12.2(13)T

This feature was introduced on the Cisco 7200 series routers.

Examples

The debug mmoip send fax command is used to test connectivity between the off-ramp gateway and a recipient fax device. Basically, this debug command sends a test fax transmission to the recipient specified in the telephone number string. There is no specific output associated with the debug mmoip send fax command.

The following example sends a test fax message to the telephone number 5550839:

Router# debug mmoip send fax 5550839

The following output shows that the off-ramp gateway is placing a fax call:

01:28:18:ftsp_offramp_match_digits:phone number to translate:5550839
01:28:18: destPat(5......), matched(1), prefix() peer_tag(1)
01:28:18:ftsp_offramp_match_digits:target:710839
01:28:18:fap_offcm:tty(4), Got dial message00:00:00.000:AT&F\Q0S7=255

Class 2 modem tracing begins, including modem initialization.

00:00:00.008:AA
00:00:00.068:TT
00:00:00.128:&F\Q0S7=255
00:00:00.128:
OK

00:00:00.128:E0V1
00:00:00.140:ATE0
OK

00:00:00.140:AT+FCLASS=2
00:00:00.148:
OK

00:00:00.148:+FDCC=..;+FBOR=
00:00:00.168:AT+FLID
00:00:00.180:
OK

00:00:00.180:ATDTW710839

The following output shows that the fax transmission is complete; in this particular example, there was a transmission error, and the modem timed out.
01:28:25:ftsp_setup_for_oc:tty4, callid=0xA
01:28:25:ftsp_setup_for_oc ctl=0, cas grp=-1, snmp_ix=30
01:28:25:ftsp_off_ramp_active_call_init tty4 callid=0xA, snmp_ix=30
01:29:18:fap_offpmt:tty(4), TxPhaseA:modem timeout
01:29:18:%FTSP-6-FAX_DISCONNECT:Transmission er
debug mmoip transfer

To send output of the Tag Image File Format (TIFF) writer to a TFTP server, use the debug mmoip transfer command in privileged EXEC mode.

debug mmoip transfer prefix-filename tftp-server-name
Syntax Description

prefix-filename

Name of the TIFF file. The format for the TIFF filename is "telephone-number.TIFF."

tftp-server-name

TFTP server to which the output from the TIFF writer is sent.

Defaults

Sending output of the TIFF writer to a TFTP server is disabled.

Command Modes

Privileged EXEC

Command History

Release

Modification

12.0(4)T

This command was introduced.

12.2(4)T

This command was implemented on the Cisco 1750 access router.

Examples

The debug mmoip transfer command sends the content of the fax data received to the TFTP server named by the tftp-server-name variable into the file identified by the prefix-filename variable. Each page of the fax transmission is a separate file, designated by the letter "p", followed by the page number.

For example, the following command transfers the received fax content to a TFTP server named "keyer". The first page of the transmission goes to the file named "/tftpboot/test/testp1.tiff", the second page goes to the file named "/tftpboot/test/testp2.tiff" and so on.

Router# debug mmoip transfer /tftpboot/test/test keyer

The named files must exist on the TFTP server and be writable in order for the debug operation to be successful.

all	Displays all debug information related to the LEC.
le-arp	Displays debug information related to the LAN Emulation (LANE) Address Resolution Protocol (ARP) table.
mpoa	Displays debug information to track the following: •MPOA specific TLV information in le-arp requests/responses •Elan-id and local segment TLV in lane control frames •When a LANE client is bound to an MPC/MPS
packet	Displays debug information about each packet.
signaling	Displays debug information related to client switched virtual circuits (SVCs).
state	Displays debug information when the state changes.
topology	Displays debug information related to the topology of the emulated LAN (ELAN).
interface interface	(Optional) Limits the debugging output to messages that relate to a particular interface or subinterface. If you enter this command multiple times with different interfaces, the last interface entered will be the one used to filter the messages.

Command	Description
debug modem traffic	Displays MPC debug information.
debug mpoa server	Displays information about the MPOA server.

all	Displays all debugging messages related to the LANE configuration server. The output includes both the events and packets types of output.
events	Displays only messages related to significant LANE configuration server events.
packets	Displays information on each packet sent or received by the LANE configuration server.

Field	Description
First field (1)	Interface type and unit number reporting the frame event.
Second field (2)	Protocol providing the information.
Third field (3)	Frame event type. Possible values are as follows: •I—Frame input •O—Frame output •T1—T1 timer expired •T3—Interface outage timer expired •T4—Idle link timer expired
Fourth field (4)	State of the protocol when the frame event occurred. Possible values are as follows: •BUSY (RNR frame received) •CONNECT •DISCONNECT •DISCSENT (disconnect sent) •ERROR (FRMR frame sent) •REJSENT (reject frame sent) •SABMSENT (SABM frame sent)
Fifth field (5)	In a frame event, this value is the size of the frame (in bytes). In a timer event, this value is the current timer value (in milliseconds).
Sixth field (6)	In a frame event, this value is the frame type name. Possible values for frame type names are as follows: •DISC—Disconnect •DM—Disconnect mode •FRMR—Frame reject •IFRAME—Information frame •ILLEGAL—Illegal LAPB frame •REJ—Reject •RNR—Receiver not ready •RR—Receiver ready •SABM—Set asynchronous balanced mode •SABME—Set asynchronous balanced mode, extended •UA—Unnumbered acknowledgment In a T1 timer event, this value is the number of retransmissions already attempted.
Seventh field (7) (This field will not print if the frame control field is required to appear as either a command or a response, and that frame type is correct.)	This field is only present in frame events. It describes the frame type identified by the LAPB address and Poll/Final bit. Possible values are as follows: •(C)—Command frame •(R)—Response frame •P—Command/Poll frame •F—Response/Final frame •/ERR—Command/Response type is invalid for the control field. An ?ERR generally means that the data terminal equipment (DTE)/data communications equipment (DCE) assignments are not correct for this link. •BAD-ADDR—Address field is neither Command nor Response

error	(Optional) Displays LAPB-TA errors.
event	(Optional) Displays LAPB-TA normal events.
traffic	(Optional) Displays LAPB-TA in/out traffic data.

Field	Description
LAT:	Indicates that this display shows LAT debugging output.
I	Indicates that this line of output describes a packet that is input to the router (I) or output from the router (O).
int = Ethernet0	Indicates the interface on which the packet event took place.
src = 0800.2b11.2d13	Indicates the source address of the packet.
dst=0000.0c01.7876	Indicates the destination address of the packet.
type=A	Indicates the message type (in hexadecimal notation). Possible values are as follows: •0 = Run Circuit •1 = Start Circuit •2 = Stop Circuit •A = Service Announcement •C = Command •D = Status •E = Solicit Information •F = Response Information

Field	Description
len= 20	Indicates the length (in hexadecimal notation) of the packet (in bytes).
next 0	Indicates the link on the transmit queue.
ref 1	Indicates the count of packet users.

Command	Description
debug all	Enables debugging for link monitoring.
no debug all	Disables debugging for link monitoring.
clear counters	Clears show interface counters on all interfaces.
show link monitor debug	Show link monitor error statistics.

list	(Optional) An access list number in the range from 1100 to 1199.
interface	(Optional) The interface type. Allowed values are the following: •channel—IBM Channel interface •ethernet—IEEE 802.3 •fddi—ANSI X3T9.5 •null—Null interface •serial—Serial •tokenring—IEEE 802.5 •tunnel—Tunnel interface

Command	Description
debug llc2 errors	Displays LLC2 protocol error conditions or unexpected input.
debug llc2 packet	Displays all input and output from the LLC2 protocol stack.
debug llc2 state	Displays state transitions of the LLC2 protocol.
debug rif	Displays information on entries entering and leaving the RIF cache.
debug rtsp	Displays information on SDLC frames received and sent by any router serial interface involved in supporting SDLC end station functions.
debug token ring	Displays messages about Token Ring interface activity.

Command	Description
debug list	Filters debugging information on a per-interface or per-access list basis.
debug llc2 dynwind	Displays changes to the dynamic window over Frame Relay.
debug llc2 packet	Displays all input and output from the LLC2 protocol stack.
debug llc2 state	Displays state transitions of the LLC2 protocol.

Field	Description
IBMNM:	Displays LLC-level debugging information.
Received	Router received a frame. The other possible value is Sending, to indicate that the router is sending a frame.
LRM	The function of the LLC-level software that is communicating as follows: •CRS—Configuration Report Server •LBS—LAN Bridge Server •LRM—LAN Reporting Manager •REM—Ring Error Monitor •RPS—Ring Parameter Server •RS—Ring Station
Set Reporting Point	Name of the specific frame that the router sent or received. Possible values include the following: •Bridge Counter Report •Bridge Parameters Changed Notification •Bridge Parameters Set •CRS Remove Ring Station •CRS Report NAUN Change •CRS Report Station Information •CRS Request Station Information •CRS Ring Station Removed •LRM LAN Manager Accepted •LRM Set Reporting Point •New Reporting Link Established •REM Forward MAC Frame •REM Parameters Changed Notification •REM Parameters Set •Report Bridge Status •Report LAN Manager Control Shift •Report REM Status •Request Bridge Status •Request REM Status •Set Bridge Parameters •Set REM Parameters
from 1000.5ade.0d8a	If the router has received the frame, this address is the source address of the frame. If the router is sending the frame, this address is the destination address of the frame.

Field	Description
LANMGR0:	Indicates that this line of output displays MAC-level debugging information. 0 indicates the number of the Token Ring interface associated with this line of debugging output.
RS	Indicates which function of the MAC-level software is communicating as follows: •CRS—Configuration Report Server •REM—Ring Error Monitor •RPS—Ring Parameter Server •RS—Ring Station
received	Indicates that the router received a frame. The other possible value is sending, to indicate that the router is sending a frame.
request address	Indicates the name of the specific frame that the router sent or received. Possible values include the following: •AMP •initialize station •report address •report attachments •report nearest active upstream neighbor (NAUN) change •report soft error •report state •request address •request attachments •request initialization •request state •ring purge •SMP
from 4000.3040.a670	Indicates the source address of the frame, if the router has received the frame. If the router is sending the frame, this address is the destination address of the frame.

Field	Description
LACK_STATE:	Indicates that this packet describes a state change in the local acknowledgment state machine.
2370300	System clock.
hashp 2AE628	Internal control block pointer used by technical support staff for debugging purposes.
old state = disconn	Old state condition in the local acknowledgment state machine. Possible values include the following: •Disconn (disconnected) •awaiting LLC2 open to finish •connected •awaiting linkdown response
new state = awaiting LLC2 open to finish	New state condition in the local acknowledgment state machine. Possible values include the following: •Disconn (disconnected) •awaiting LLC2 open to finish •connected •awaiting linkdown response

all	Displays both errors and sequence of events for MDSS.
error	Displays the run-time errors for MDSS.
event	Displays the run-time sequence of events for MDSS.

Command	Description
debug mls rp ip multicast	Displays information about MLSP.

Command	Description
debug media resource provisioning errors	Displays debugging messages related to media resource provisioning errors.
debug media resource provisioning events	Displays debugging messages related to media resource provisioning events.

Command	Description
debug media resource provisioning all	Displays debugging messages related to all media resource provisioning.
debug media resource provisioning events	Displays debugging messages related to media resource provisioning events.

all	Debugs DSPRM errors, events, and messages.
errors	Debugs DSPRM errors.
events	Debugs DSPRM events.
message	Debugs DSPRM messages.

Release	Modification
12.3(8)XY	This command was introduced on the Communication Media Module.
12.3(14)T	This command was integrated into Cisco IOS Release 12.3(14)T.

Release	Modification
12.1(1)T	This command was introduced.
12.1(3)T	Additional information was displayed for the gateways.
12.1(5)XM	The output was modified to display parameters for the MGCP channel-associated signaling (CAS) PBX and ATM adaptation layer 2 (AAL2) permanent virtual circuit (PVC) features.
12.2(2)T	The output was modified to display parameters for the MGCP channel-associated signaling (CAS) PBX and ATM adaptation layer 2 (AAL2) permanent virtual circuit (PVC) features.
12.2(11)T	This command was implemented on the Cisco AS5350, Cisco AS5400, and Cisco AS5850.
12.2(13)T	This command was implemented on the Cisco 7200 series images.
12.4(4)T	The tracelevel keyword was added.

Command	Description
debug mgcp endpoint	Enables debug traces for a specific MGCP endpoint.
debug mgcp tracelevel-default	Sets the trace level globally for all MGCP debug traces.
mgcp	Starts the MGCP daemon.
mgcp debug-header	Enables the display of MGCP module-dependent information in the debug header.
show debugging	Displays the types of debugging that are enabled.
show mgcp	Displays MGCP configuration information.
voice call debug	Specifies the format of the debug header.

endpoint-name	Name of the MGCP endpoint for which to enable debugging. Must be a fully specified and supported endpoint.
all	Displays MGCP errors, events, media, and packets for the specified endpoint.
errors	Displays MGCP errors for the specified endpoint.
events	Displays MGCP events for the specified endpoint.
media	Displays MGCP tone and signal events for the specified endpoint.
packets	Displays MGCP packets for the specified endpoint.
tracelevel	(Optional) Sets the priority level for the all, events, or media debug trace. •critical—Displays only high-priority debug information. •moderate—Displays medium- and high-priority debug information. •verbose—Displays all debug information. This is the default level. Note This keyword is not available for errors or packets debugging.

Command	Description
debug mgcp all	Enables all debug traces for MGCP.
debug mgcp errors	Enables debug traces for MGCP errors.
debug mgcp events	Enables debug traces for MGCP events.
debug mgcp media	Enables debug traces for MGCP tone and signal events.
debug mgcp packets	Enables debug traces for MGCP packets.
debug mgcp tracelevel-default	Sets the trace level globally for all MGCP debug traces.
mgcp	Starts the MGCP daemon.
mgcp debug-header	Enables the display of MGCP module-dependent information in the debug header.
show debugging	Displays the types of debugging that are enabled.
show mgcp	Displays MGCP configuration information.
voice call debug	Specifies the format of the debug header.

Release	Modification
12.2(2)XA	This command was introduced.
12.2(11)T	This command was integrated into Cisco IOS Release 12.2(11)T.
12.4(4)T	The tracelevel keyword was added.

Command	Description
debug call filter inout	Displays the debug trace inside the GCFM.
debug mgcp endpoint	Enables debug traces for a specific MGCP endpoint.
debug mgcp tracelevel-default	Sets the trace level globally for all MGCP debug traces.
mgcp	Starts the MGCP daemon.
mgcp debug-header	Enables the display of MGCP module-dependent information in the debug header.
show mgcp	Displays MGCP configuration information.
voice call debug	Specifies the format of the debug header.

Release	Modification
12.2(2)XB	This command was introduced.
12.2(11)T	This command was implemented on the Cisco AS5350, Cisco AS5400, and Cisco AS5850.
12.2(13)T	This command was implemented on the Cisco 7200 series images.
12.4(4)T	The tracelevel keyword was added.

Release	Modification
12.2(2)XB	This command was introduced.
12.2(8)T	This command was integrated into Cisco IOS Release 12.2(8)T.
12.2(11)T	This command was implemented on the Cisco AS5350, Cisco AS5400, and Cisco AS5850.
12.2(13)T	This command was implemented on the Cisco 7200 series images.
12.4(4)T	The tracelevel keyword was added.

critical	Only high-priority debug information is displayed.
moderate	Medium- and high-priority debug information is displayed.
verbose	All debug information is displayed. This is the default value.

error	Displays MLS error messages.
events	Displays a run-time sequence of events for the Multilayer Switching Protocol (MLSP).
ipx	Displays IPX-related events for MLS, including route purging and changes to access lists and flow masks.
locator	Identifies which switch is switching a particular flow of MLS explorer packets.
packets	Displays packet contents (in verbose and hexadecimal formats) for MLSP messages.
all	Displays all MLS debugging events.