Cisco IOS Debug Command Reference, Release 12.3 T - Debug Commands: debug packet through debug redundancy [Cisco IOS Software Releases 12.3 T]

Table Of Contents

debug packet

debug pad

debug piafs events

debug pots

debug pots csm

debug ppp

debug pppatm

debug ppp bap

debug ppp multilink events

debug ppp multilink fragments

debug ppp multilink negotiation

debug pppoe

debug priority

debug proxy h323 statistics

debug pvcd

debug pxf tbridge

debug qllc error

debug qllc event

debug qllc packet

debug qllc state

debug qllc timer

debug qllc x25

debug qos ha

debug radius

debug radius accounting

debug radius local-server

debug ras

debug redundancy

debug packet

To display per-packet debugging output, use the debug packet command in privileged EXEC mode. To disable debugging output, use the no form of this command.

debug packet [interface number [vcd vcd-number] | vc vpi/vci | vc-name]
no debug packet [interface number [vcd vcd-number] | vc vpi/vci | vc-name]
Syntax Description

interface number

(Optional) interface or subinterface number.

vcd vcd-number

(Optional) Number of the virtual circuit designator (VCD).

vc vpi/vci

(Optional) Virtual path identifier (VPI) and virtual channel identifier (VCI) numbers of the VC.

vc-name

(Optional) Name of the PVC or SVC.

Defaults

Debugging for packets is disabled by default.

Command Modes

Privileged EXEC

Command History

Release

Modification

9.21

This command was introduced.

12.2(13)T

Support for Apollo Domain and Banyan VINES was removed.

Usage Guidelines

The debug packet command displays all process-level packets for both outbound and inbound packets. This command is useful for determining whether packets are being received and sent correctly. The output reports information online when a packet is received or a transmission is attempted.

For sent packets, the information is displayed only after the protocol data unit (PDU) is entirely encapsulated and a next hop VC is found. If information is not displayed, the address translation probably failed during encapsulation. When a next hop VC is found, the packet is displayed exactly as it will be presented on the wire. Having a display indicates that the packets are properly encapsulated for transmission.

For received packets, information is displayed for all incoming frames. The display can show whether the sending station properly encapsulates the frames. Because all incoming frames are displayed, this information is useful when performing back-to-back testing and corrupted frames cannot be dropped by an intermediary switch.

The debug packet command also displays the initial bytes of the actual PDU in hexadecimal. This information can be decoded only by qualified support or engineering personnel.

Caution Because the debug packet command generates a substantial amount of output for every packet processed, use it only when traffic on the network is low so other activity on the system is not adversely affected.

Examples

The following is sample output from the debug packet command:
Router# debug packet
2/0.5(I): VCD:0x9 VCI:0x23 Type:0x0 SAP:AAAA CTL:03 OUI:000000 TYPE:0800 Length0x70
4500 002E 0000 0000 0209 92ED 836C A26E FFFF FFFF 1108 006D 0001 0000 0000
A5CC 6CA2 0000 000A 0000 6411 76FF 0100 6C08 00FF FFFF 0003 E805 DCFF 0105
Table 237 describes the significant fields shown in the display.

Table 237 debug packet Field Descriptions

Field

Description

2/0.5

Indicates the subinterface that generated this packet.

(I)

Indicates a receive packet. (O) indicates an output packet.

VCD: 0xn

Indicates the virtual circuit associated with this packet, where n is some value.

DM: 0xnnnn

Indicates the descriptor mode bits on output only, where nnnn is a hexadecimal value.

TYPE:n

Displays the encapsulation type for this packet.

Length:n

Displays the total length of the packet including the headers.

The following two lines of output are the binary data, which are the contents of the protocol data unit (PDU) before encapsulation:
4500 002E 0000 0000 0209 92ED 836C A26E FFFF FFFF 1108 006D 0001 0000 0000
A5CC 6CA2 0000 000A 0000 6411 76FF 0100 6C08 00FF FFFF 0003 E805 DCFF 0105
The following is sample output from the debug packet command:
Router# debug packet
Ethernet0: Unknown ARPA, src 0000.0c00.6fa4, dst ffff.ffff.ffff, type 0x0a0
data 00000c00f23a00000c00ab45, len 60
Serial3: Unknown HDLC, size 64, type 0xaaaa, flags 0x0F00
Serial2: Unknown PPP, size 128
Serial7: Unknown FRAME-RELAY, size 174, type 0x5865, DLCI 7a
Serial0: compressed TCP/IP packet dropped
Table 238 describes the significant fields shown in the display.

Table 238 debug packet Field Descriptions

Field

Description

Ethernet0

Name of the Ethernet interface that received the packet.

Unknown

Network could not classify this packet. Examples include packets with unknown link types.

ARPA

Packet uses ARPA-style encapsulation. Possible encapsulation styles vary depending on the media command mode (MCM) and encapsulation style.

Ethernet (MCM)—Encapsulation Style:

•ARP

•ETHERTALK

•ISO1

•ISO3

•LLC2

•NOVELL-ETHER

•SNAP

FDDI (MCM)—Encapsulation Style:

•ISO1

•ISO3

•LLC2

•SNAP

Frame Relay—Encapsulation Style:

•BRIDGE

•FRAME-RELAY

ARPA
(continued)

Serial (MCM)—Encapsulation Style:

•BFEX25

•BRIDGE

•DDN-X25

•DDNX25-DCE

•ETHERTALK

•FRAME-RELAY

•HDLC

•HDH

•LAPB

•LAPBDCE

•MULTI-LAPB

•PPP

•SDLC-PRIMARY

•SDLC-SECONDARY

•SLIP

•SMDS

•STUN

•X25

•X25-DCE

Token Ring (MCM)—Encapsulation Style:

•3COM-TR

•ISO1

•ISO3

•MAC

•LLC2

•NOVELL-TR

•SNAP

•VINES-TR

src 0000.0c00.6fa4

MAC address of the node generating the packet.

dst.ffff.ffff.ffff

MAC address of the destination node for the packet.

type 0x0a0

Packet type.

data...

First 12 bytes of the datagram following the MAC header.

len 60

Length of the message (in bytes) that the interface received from the wire.

size 64

Length of the message (in bytes) that the interface received from the wire. Equivalent to the len field.

flags 0x0F00

HDLC or PP flags field.

DLCI 7a

The DLCI number on Frame Relay.

compressed TCP/IP packet dropped

TCP header compression is enabled on an interface and the packet is not HDLC or X25.

debug pad

To display debugging messages for all packet assembler/disassembler (PAD) connections, use the debug pad command in privileged EXEC mode. To disable debugging output, use the no form of this command.

debug pad
no debug pad
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

This command was introduced in a release prior to Cisco IOS Release 12.0.

Examples

Use the debug pad command to gather information to forward to the Cisco Technical Assistance Center (TAC) to assist in troubleshooting a problem that involves PAD connections.

The following example shows output of the debug pad and debug x25 event commands for an incoming PAD call destined for a terminal line. The incoming PAD call is rejected by the terminal line because the selected network closed user group (CUG) has not been subscribed to by the caller:
Router# debug pad
Router# debug x25 event
Serial1/1:X.25 I R1 Call (16) 8 lci 8
  From (7):2001534 To (9):200261150
  Facilities:(2)
    Closed User Group (basic):99
  Call User Data (4):0x01000000 (pad)
pad_svc_announce:destination matched 1
PAD:incoming call to 200261150 on line 130 CUD length 4
!PAD130:Incoming Call packet, Closed User Group (CUG) service protection, selected network 
CUG not subscribed
PAD:CUG service protection Cause:11 Diag:65
Serial1/1:X.25 O R1 Clear (5) 8 lci 8
  Cause 0, Diag 65 (DTE originated/Facility code not allowed)
Serial1/1:X.25 I R1 Clear Confirm (3) 8 lci 8
The following example shows the output of the debug pad command for an outgoing PAD call initiated from a terminal line with a subscribed CUG that bars outgoing access:
!PAD130:Outgoing Call packet, Closed User Group - CUG service validation, selected CUG 
!bars outgoing access
PAD130:Closing connection to .  In 0/0, out 0/0
debug piafs events

To check the debugging messages for Personal Handyphone Internet Access Forum Standard (PIAFS) calls, use the debug piafs events command in privileged EXEC mode. To disable debugging output, use the no form of this command.

debug piafs events
no debug piafs events
Syntax Description

This command has no arguments or keywords.

Defaults

No default behavior or values

Command Modes

Privileged EXEC

Command History

Release

Modification

12.2(8)T

This command was introduced on Cisco 803, Cisco 804, and Cisco 813 routers.

Usage Guidelines

The debug piafs events command provides debugging information for the PIAFS calls on the router, including the inband negotiation process.

Examples

The debug piafs events command was configured to provide the following information for PIAFS calls:
Router# debug piafs events
02:16:39:PIAFS events debugging is on
02:16:167516180371:PIAFS: RX <- CDAPI :cdapi_route_call Request
02:16:167517398148:PIAFS: RX <- CDAPI :CDAPI_MSG_CONNECT_IND
02:16:171798691839:PIAFS: TX -> CDAPI :CDAPI_MSG_SUBTYPE_ALERT_REQ
02:16:167503724545:PIAFS: TX -> CDAPI :CDAPI_MSG_CONNECT_RESP
02:16:167503765504:PIAFS: TX -> CDAPI :CDAPI_MSG_CONN_ACTIVE_REQ
02:16:167503724544:PIAFS: RX <- CDAPI :CDAPI_MSG_CONN_ACTIVE_IND
02:16:171798691839:PIAFS:Network allotted Channel :B1
02:16:167503765504:PIAFS:Enabling QMC in PIAFS mode for B1
02:16:171798691839:PIAFS:piafs_driver_enable_settings()
02:16:167503765504:PIAFS:The speed is :64
02:16:167503724544:PIAFS:Starting 64 kbps PIAFS Incoming
02:16:39:PIAFS:RX <- NEGO_SYNC_REQUEST[GSN:13 RSN:1 CRSN:1 SISN:
255]
02:16:39:PIAFS:Updating conf resp num
02:16:39:PIAFS:TX -> NEGO_SYNC_RECEPTION[GSN:1 RSN:1 CRSN:13 SISN:
255]
02:16:39:PIAFS:RX <- NEGO_SYNC_REQUEST[GSN:14 RSN:1 CRSN:1 SISN:
255]
02:16:39:PIAFS:TX -> NEGO_SYNC_RECEPTION[GSN:2 RSN:2 CRSN:13 SISN:
255]
02:16:39:PIAFS:RX <- NEGO_SYNC_REQUEST[GSN:15 RSN:1 CRSN:1 SISN:
255]
02:16:39:PIAFS:TX -> NEGO_SYNC_RECEPTION[GSN:3 RSN:3 CRSN:13 SISN:
255]
02:16:39:PIAFS:RX <- NEGO_SYNC_REQUEST[GSN:16 RSN:1 CRSN:1 SISN:
255]
02:16:39:PIAFS:TX -> NEGO_SYNC_RECEPTION[GSN:4 RSN:4 CRSN:13 SISN:
255]
02:16:39:PIAFS:RX <- NEGO_SYNC_REQUEST[GSN:17 RSN:1 CRSN:1 SISN:
255]
02:16:39:PIAFS:TX -> NEGO_SYNC_RECEPTION[GSN:5 RSN:5 CRSN:13 SISN:
255]
02:16:39:PIAFS:RX <- NEGO_SYNC_REQUEST[GSN:18 RSN:1 CRSN:1 SISN:
255]
02:16:39:PIAFS:TX -> NEGO_SYNC_RECEPTION[GSN:6 RSN:6 CRSN:13 SISN:
255]
02:16:39:PIAFS:RX <- NEGO_SYNC_REQUEST[GSN:19 RSN:1 CRSN:1 SISN:
255]
02:16:39:PIAFS:TX -> NEGO_SYNC_RECEPTION[GSN:7 RSN:7 CRSN:13 SISN:
255]
02:16:39:PIAFS:RX <- CONTROL_REQUEST(comm parameter)[Seq No:0]
02:16:39:PIAFS:Rx Parameters:
02:16:39:PIAFS:  Data Protocol:Version 1
02:16:39:PIAFS:  Control Protocol:Version 1
02:16:39:PIAFS:  RTF value:9
02:16:39:PIAFS:  Compression:V.42bis
02:16:39:PIAFS:  Frame Length:80
02:16:39:PIAFS:  Frame Number:63
02:16:39:PIAFS:TX -> CONTROL_RECEPTION[0]
02:16:39:PIAFS:ACKed all the Rx control parameters
02:16:39:PIAFS:Piafs layer up & Main FSM set to DATA
02:16:39:PIAFS:Compression v42bis enabled
02:16:39:PIAFS:V42BIS:v42bis_init()
02:16:39:PIAFS:V42BIS:v42bis_init()
02:16:39:PIAFS:V42BIS:Negotiated Values for P1, P2 are - 4096 , 250
02:16:39:PIAFS:Incoming call invoking ISDN_CALL_CONNECT
02:16:39:%LINK-3-UPDOWN:Interface BRI0:1, changed state to up
02:16:39:PIAFS:RX <- CONTROL_REQUEST(comm parameter)[Seq No:0]
02:16:39:PIAFS:Rx Parameters:
02:16:39:PIAFS:  Data Protocol:Version 1
02:16:39:PIAFS:  Control Protocol:Version 1
02:16:39:PIAFS:  RTF value:9
02:16:39:PIAFS:  Compression:V.42bis
02:16:39:PIAFS:  Frame Length:80
02:16:39:PIAFS:  Frame Number:63
02:16:39:PIAFS:TX -> CONTROL_RECEPTION[0]
02:16:39:PIAFS:ACKed all the Rx control parameters
02:16:39:PIAFS:RX <- CONTROL_REQUEST(comm parameter)[Seq No:0]
02:16:39:PIAFS:Rx Parameters:
02:16:39:PIAFS:  Data Protocol:Version 1
02:16:39:PIAFS:  Control Protocol:Version 1
02:16:39:PIAFS:  RTF value:9
02:16:39:PIAFS:  Compression:V.42bis
02:16:39:PIAFS:  Frame Length:80
02:16:39:PIAFS:  Frame Number:63
02:16:39:PIAFS:TX -> CONTROL_RECEPTION[0]
02:16:39:PIAFS:ACKed all the Rx control parameters
02:16:39:PIAFS:RX <- CONTROL_REQUEST(comm parameter)[Seq No:0]
02:16:39:PIAFS:Rx Parameters:
02:16:39:PIAFS:  Data Protocol:Version 1
02:16:39:PIAFS:  Control Protocol:Version 1
02:16:39:PIAFS:  RTF value:9
02:16:39:PIAFS:  Compression:V.42bis
02:16:39:PIAFS:  Frame Length:80
02:16:39:PIAFS:  Frame Number:63
02:16:39:PIAFS:TX -> CONTROL_RECEPTION[0]
02:16:39:PIAFS:ACKed all the Rx control parameters
02:16:39:PIAFS:RX <- CONTROL_REQUEST(comm parameter)[Seq No:0]
02:16:39:PIAFS:Rx Parameters:
02:16:39:PIAFS:  Data Protocol:Version 1
02:16:39:PIAFS:  Control Protocol:Version 1
02:16:39:PIAFS:  RTF value:9
02:16:39:PIAFS:  Compression:V.42bis
02:16:39:PIAFS:  Frame Length:80
02:16:39:PIAFS:  Frame Number:63
02:16:39:PIAFS:TX -> CONTROL_RECEPTION[0]
02:16:39:PIAFS:ACKed all the Rx control parameters
02:16:39:PIAFS:RX <- CONTROL_REQUEST(comm parameter)[Seq No:0]
02:16:39:PIAFS:Rx Parameters:
02:16:39:PIAFS:  Data Protocol:Version 1
02:16:39:PIAFS:  Control Protocol:Version 1
02:16:39:PIAFS:  RTF value:9
02:16:39:PIAFS:  Compression:V.42bis
02:16:39:PIAFS:  Frame Length:80
02:16:39:PIAFS:  Frame Number:63
02:16:39:PIAFS:TX -> CONTROL_RECEPTION[0]
02:16:39:PIAFS:ACKed all the Rx control parameters
02:16:39:PIAFS:RX <- CONTROL_REQUEST(comm parameter)[Seq No:0]
02:16:39:PIAFS:Rx Parameters:
02:16:39:PIAFS:  Data Protocol:Version 1
02:16:39:PIAFS:  Control Protocol:Version 1
02:16:39:PIAFS:  RTF value:9
02:16:39:PIAFS:  Compression:V.42bis
02:16:39:PIAFS:  Frame Length:80
02:16:39:PIAFS:  Frame Number:63
02:16:39:PIAFS:TX -> CONTROL_RECEPTION[0]
02:16:39:PIAFS:ACKed all the Rx control parameters
02:16:39:PIAFS:RX <- CONTROL_REQUEST(comm parameter)[Seq No:0]
02:16:39:PIAFS:Rx Parameters:
02:16:39:PIAFS:  Data Protocol:Version 1
02:16:39:PIAFS:  Control Protocol:Version 1
02:16:39:PIAFS:  RTF value:9
02:16:39:PIAFS:  Compression:V.42bis
02:16:39:PIAFS:  Frame Length:80
02:16:39:PIAFS:  Frame Number:63
02:16:39:PIAFS:TX -> CONTROL_RECEPTION[0]
02:16:39:PIAFS:ACKed all the Rx control parameters
02:16:39:PIAFS:piafs_setmap() tx_map FFFFFFFF
02:16:39:PIAFS:piafs_setmap() rx_map 0
02:16:41:PIAFS:PPP:Autoselect sample 7E
02:16:41:PIAFS:PPP:Autoselect sample 7EFF
02:16:41:PIAFS:PPP:Autoselect sample 7EFF7D
02:16:41:PIAFS:PPP:Autoselect sample 7EFF7D23
02:16:41:PIAFS:piafs_setmap() tx_map FFFFFFFF
02:16:41:PIAFS:piafs_setmap() rx_map 0
02:16:42:PIAFS:piafs_setmap() tx_map A0000
02:16:42:PIAFS:piafs_setmap() rx_map 0
Table 239 describes the significant fields shown in the display.

Table 239 debug piafs events Field Descriptions

Field

Description

RX <- CDAPI :cdapi_route_call Request

The call distributor application programming interface (CDAPI) in the router receives an ISDN call request from the switch.

RX <- CDAPI :CDAPI_MSG_CONNECT_IND

The CDAPI in the router receives a connection indicator message from the switch.

TX -> CDAPI :CDAPI_MSG_SUBTYPE_ALERT_REQ

The CDAPI in the router transmits an alert request to the switch.

TX -> CDAPI :CDAPI_MSG_CONNECT_RESP

The CDAPI in the router transmits a connect response message to the switch.

TX -> CDAPI :CDAPI_MSG_CONN_ACTIVE_REQ

The CDAPI in the router transmits a connection active request to the switch.

RX <-CDAPI:CDAPI_MSG_CONN_ACTIVE_IND

The CDAPI in the router receives a connection active indicator from the switch.

Enabling QMC in PIAFS mode for B1

QMC (global multichannel parameters) are being enabled in PIAFS mode for the B1 channel.

piafs_driver_enable_settings()

The PIAFS driver is enabling the settings.

Starting 64 kbps PIAFS Incoming

The speed of the transmission in kbps. In this case, the speed is 64 kbps.

RX <- NEGO_SYNC_REQUEST[GSN: RSN: CRSN: SISN:]

The router receives a PIAFS negotiation synchronization request frame from the peer PIAFS device. The frame contains the following: general sequence number (GSN), reception sequence number (RSN), confirmation response sequence number (CRSN), and synchronization initiation sequence number (SISN).

Updating conf resp num

The confirmation response number is being updated.

TX -> NEGO_SYNC_RECEPTION[GSN: RSN: CRSN: SISN: ]

The router transmits a PIAFS negotiation synchronization reception message to the peer PIAFS device. The message includes the GSN, RSN, CRSN, and SISN.

RX <- CONTROL_REQUEST

The router receives a PIAFS control request frame that includes communication parameters.

Rx Parameters

The communication parameters are as follows.

  Data Protocol

The version of the data protocol.

  Control Protocol

The version of the control protocol.

  RTF value

Round-trip frame value.

  Compression

The compression standard.

  Frame Length

The length of the frame, in bytes.

  Frame Number

The number of packets per frame.

TX -> CONTROL_RECEPTION

The router transmits a PIAFS control reception frame.

ACKed all the Rx control parameters

The control reception frame acknowledges all the communication parameters that were received from the peer.

Piafs layer up & Main FSM set to DATA

The PIAFS protocol is active on the router. The router is ready to receive data from the peer device.

Compression v42bis enabled

The compression protocol v42bis is enabled.

V42BIS:v42bis_init()

The v42bis compression protocol has been initiated.

V42BIS:Negotiated Values for P1, P2 are - 4096 , 250

In this example, P1 is the total count of encoded words when v42bis compression is enabled. P2 is the maximum letter line length for the V42bis compression.

Incoming call invoking ISDN_CALL_CONNECT

An incoming ISDN call connection message is received.

PPP

The PPP layer on the router becomes active and starts to process the PPP frame from the peer PIAFS device.

debug pots

To display information on the telephone interfaces, use the debug pots command in privileged EXEC mode. To disable debugging output, use the no form of this command.

debug pots {driver | csm} [1 | 2]
no debug pots {driver | csm} [1 | 2]
Syntax Description

driver

Displays driver debug information.

csm

Displays Content Switching Module (CSM) debug information.

1

(Optional) Displays information for telephone port 1 only.

2

(Optional) Displays information for telephone port 2 only.

Command Modes

Privileged EXEC

Usage Guidelines

The debug pots command displays driver and CSM debug information for telephone ports 1 and 2.

Examples

The following is sample output from the debug pots driver 1 command. This sample display indicates that the telephone port driver is not receiving caller ID information from the ISDN line. Therefore, the analog caller ID device attached to the telephone port does not display caller ID information.
Router# debug pots driver 1
00:01:51:POTS DRIVER port=1 activate ringer: cadence=0 callerId=Unknown
00:01:51:POTS DRIVER port=1 state=Idle drv_event=RING_EVENT
00:01:51:POTS DRIVER port=1 enter_ringing
00:01:51:POTS DRIVER port=1 cmd=19
00:01:51:POTS DRIVER port=1 activate disconnect
00:01:51:POTS DRIVER port=1 state=Ringing drv_event=DISCONNECT_EVENT
00:01:51:POTS DRIVER port=1 cmd=1A
00:01:51:POTS DRIVER port=1 enter_idle
00:01:51:POTS DRIVER port=1 ts connect: 0 0
00:01:51:POTS DRIVER port=1 cmd=D
00:01:51:POTS DRIVER port=1 report onhook
00:01:51:POTS DRIVER port=1 activate tone=SILENCE_TONE
00:01:51:POTS DRIVER port=1 state=Idle drv_event=TONE_EVENT
00:01:51:POTS DRIVER port=1 activate tone=SILENCE_TONE
00:01:51:POTS DRIVER port=1 state=Idle drv_event=TONE_EVENT
00:01:53:POTS DRIVER port=1 activate ringer: cadence=0 callerId=Unknown
00:01:53:POTS DRIVER port=1 state=Idle drv_event=RING_EVENT
00:01:53:POTS DRIVER port=1 enter_ringing
00:01:53:POTS DRIVER port=1 cmd=19
00:01:55:POTS DRIVER port=1 cmd=1A
00:02:49:POTS DRIVER port=1 state=Ringing drv_event=OFFHOOK_EVENT
00:02:49:POTS DRIVER port=1 cmd=1A
00:02:49:POTS DRIVER port=1 enter_suspend
00:02:49:POTS DRIVER port=1 cmd=A
00:02:49:POTS DRIVER port=1 report offhook
00:02:49:POTS DRIVER port=1 activate connect: endpt=1 calltype=TWO_PARTY_CALL
00:02:49:POTS DRIVER port=1 state=Suspend drv_event=CONNECT_EVENT
00:02:49:POTS DRIVER port=1 enter_connect: endpt=1 calltype=0
00:02:49:POTS DRIVER port=1 cmd=A
00:02:49:POTS DRIVER port=1 ts connect: 1 0
00:02:49:POTS DRIVER port=1 activate connect: endpt=1 calltype=TWO_PARTY_CALL
00:02:49:POTS DRIVER port=1 state=Connect drv_event=CONNECT_EVENT
00:02:49:POTS DRIVER port=1 enter_connect: endpt=1 calltype=0
00:02:49:POTS DRIVER port=1 cmd=A
00:02:49:POTS DRIVER port=1 ts connect: 1 0
00:02:55:POTS DRIVER port=1 state=Connect drv_event=ONHOOK_EVENT
00:02:55:POTS DRIVER port=1 enter_idle
00:02:55:POTS DRIVER port=1 ts connect: 0 0
00:02:55:POTS DRIVER port=1 cmd=D
00:02:55:POTS DRIVER port=1 report onhook
00:02:55:POTS DRIVER port=1 activate tone=SILENCE_TONE
00:02:55:POTS DRIVER port=1 state=Idle drv_event=TONE_EVENT
00:02:55:POTS DRIVER port=1 activate tone=SILENCE_TONE
00:02:55:POTS DRIVER port=1 state=Idle drv_event=TONE_EVENT
The following is sample output from the debug pots csm 1 command. This sample display indicates that a dial peer contains an invalid destination pattern (555-1111).
Router# debug pots csm 1
01:57:28:EVENT_FROM_ISDN:dchanidb=0x66CB38, call_id=0x11, ces=0x2 bchan=0x0, event=0x1, 
cause=0x0
01:57:28:Dial peer not found, route call to port 1
01:57:28:CSM_PROC_IDLE:CSM_EVENT_ISDN_CALL, call_id=0x11, port=1
01:57:28:Calling number `5551111'
01:57:40:CSM_PROC_RINGING:CSM_EVENT_VDEV_OFFHOOK, call_id=0x11, port=1
01:57:40:EVENT_FROM_ISDN:dchan_idb=0x66CB38, call_id=0x11, ces=0x2 bchan=0x0, event=0x4, 
cause=0x0
01:57:40:CSM_PROC_CONNECTING:CSM_EVENT_ISDN_CONNECTED, call_id=0x11, port=1
01:57:47:CSM_PROC_CONNECTING:CSM_EVENT_VDEV_ONHOOK, call_id=0x11, port=1
01:57:201863503872: %ISDN-6-DISCONNECT:Interface BRI0:1 disconnected from unknown, call 
lasted 5485 seconds
01:57:47: %ISDN-6-DISCONNECT:Interface BRI0:1 disconnected from unknown, call lasted 5485 
seconds
01:57:47:EVENT_FROM_ISDN:dchan _idb=0x66CB38, call_id=0x11, ces=0x2 bchan=0xFFFFFFFF, 
event=0x0, cause=0x1
01:57:47:CSM_PROC_NEAR_END_DISCONNECT:CSM_
debug pots csm

To activate events from which an application can determine and display the status and progress of calls to and from plain old telephone service (POTS) ports, use the debug pots csm command in privileged EXEC mode.

debug pots csm
Syntax Description

This command has no arguments or keywords.

Command Modes

Privileged EXEC

Command History

Release

Modification

12.1.(2)XF

This command was introduced on the Cisco 800 series routers.

Examples

To see debugging messages, enter the logging console global configuration mode command as follows:
Router(config)# logging console 
Router(config)# exit
Debugging messages are displayed in one of two formats that are relevant to the POTS dial feature:
hh:mm:ss: CSM_STATE: CSM_EVENT, call id = ??, port = ?
or
hh:mm:ss: EVENT_FROM_ISDN:dchan_idb=0x???????, call_id=0x????, ces=? bchan=0x????????, 
event=0x?, cause=0x??
Table 240 describes the significant fields shown in the display.

Table 240 debug pots csm Field Descriptions

Command Elements

Description

hh:mm:ss

Timestamp (in hours, minutes, and seconds).

CSM_STATE

One of the call CSM states listed in Table 241.

CSM_EVENT

One of the CSM events listed in Table 242.

call id

Hexadecimal value from 0x00 to 0xFF.

port

Telephone port 1 or 2.

EVENT_FROM_ISDN

A CSM event. Table 242 shows a list of CSM events.

dchan_idb

Internal data structure address.

ces

Connection end point suffix used by ISDN.

bchan

Channel used by the call. A value of 0xFFFFFFFF indicates that a channel is not assigned.

event

A hexadecimal value that is translated into a CSM event. Table 243 shows a list of events and the corresponding CSM events.

cause

A hexadecimal value that is given to call-progressing events. Table 244 shows a list of cause values and definitions.

Table 241 shows the values for CSM states.

Table 241 CSM States

CSM State

Description

CSM_IDLE_STATE

Telephone on the hook.

CSM_RINGING

Telephone ringing.

CSM_SETUP

Setup for outgoing call in progress.

CSM_DIALING

Dialing number of outgoing call.

CSM_IVR_DIALING

Interactive voice response (IVR) for Japanese telephone dialing.

CSM_CONNECTING

Waiting for carrier to connect the call.

CSM_CONNECTED

Call connected.

CSM_DISCONNECTING

Waiting for carrier to disconnect the call.

CSM_NEAR_END_DISCONNECTING

Waiting for carrier to disconnect the call.

CSM_HARD_HOLD

Call on hard hold.

CSM_CONSULTATION_HOLD

Call on consultation hold.

CSM_WAIT_FOR_HOLD

Waiting for carrier to put call on hard hold.

CSM_WAIT_FOR_CONSULTATION_HOLD

Waiting for carrier to put call on consultation hold.

CSM_CONFERENCE

Waiting for carrier to complete call conference.

CSM_TRANSFER

Waiting for carrier to transfer call.

CSM_APPLIC_DIALING

Call initiated from Cisco IOS command-line interface (CLI).

Table 242 shows the values for CSM events.

Table 242 CSM Events

CSM Events

Description

CSM_EVENT_INTER_DIGIT_TIMEOUT

Time waiting for dial digits has expired.

CSM_EVENT_TIMEOUT

Near- or far-end disconnect timeout.

CSM_EVENT_ISDN_CALL

Incoming call.

CSM_EVENT_ISDN_CONNECTED

Call connected.

CSM_EVENT_ISDN_DISCONNECT

Far end disconnected.

CSM_EVENT_ISDN_DISCONNECTED

Call disconnected.

CSM_EVENT_ISDN_SETUP

Outgoing call requested.

CSM_EVENT_ISDN_SETUP_ACK

Outgoing call accepted.

CSM_EVENT_ISDN_PROC

Call proceeding and dialing completed.

CSM_EVENT_ISDN_CALL_PROGRESSING

Call being received in band tone.

CSM_EVENT_ISDN_HARD_HOLD

Call on hard hold.

CSM_EVENT_ISDN_HARD_HOLD_REJ

Hold attempt rejected.

CSM_EVENT_ISDN_CHOLD

Call on consultation hold.

CSM_EVENT_ISDN_CHOLD_REJ

Consultation hold attempt rejected.

CSM_EVENT_ISDN_RETRIEVED

Call retrieved.

CSM_EVENT_ISDN_RETRIEVE_REJ

Call retrieval attempt rejected.

CSM_EVENT_ISDN_TRANSFERRED

Call transferred.

CSM_EVENT_ISDN_TRANSFER_REJ

Call transfer attempt rejected.

CSM_EVENT_ISDN_CONFERENCE

Call conference started.

CSM_EVENT_ISDN_CONFERENCE_REJ

Call conference attempt rejected.

CSM_EVENT_ISDN_IF_DOWN

ISDN interface down.

CSM_EVENT_ISDN_INFORMATION

ISDN information element received (used by NTT IVR application).

CSM_EVENT_VDEV_OFFHOOK

Telephone off the hook.

CSM_EVENT_VDEV_ONHOOK

Telephone on the hook.

CSM_EVENT_VDEV_FLASHHOOK

Telephone hook switch has flashed.

CSM_EVENT_VDEV_DIGIT

DTMF digit has been detected.

CSM_EVENT_VDEV_APPLICATION_CALL

Call initiated from Cisco IOS CLI.

Table 243 shows the values for events that are translated into CSM events.

Table 243 Event Values

Hexadecimal Value

Event

CSM Event

0x0

DEV_IDLE

CSM_EVENT_ISDN_DISCONNECTED

0x1

DEV_INCALL

CSM_EVENT_ISDN_CALL

0x2

DEV_SETUP_ACK

CSM_EVENT_ISDN_SETUP_ACK

0x3

DEV_CALL_PROC

CSM_EVENT_ISDN_PROC

0x4

DEV_CONNECTED

CSM_EVENT_ISDN_CONNECTED

0x5

DEV_CALL_PROGRESSING

CSM_EVENT_ISDN_CALL_PROGRESSING

0x6

DEV_HOLD_ACK

CSM_EVENT_ISDN_HARD_HOLD

0x7

DEV_HOLD_REJECT

CSM_EVENT_ISDN_HARD_HOLD_REJ

0x8

DEV_CHOLD_ACK

CSM_EVENT_ISDN_CHOLD

0x9

DEV_CHOLD_REJECT

CSM_EVENT_ISDN_CHOLD_REJ

0xa

DEV_RETRIEVE_ACK

CSM_EVENT_ISDN_RETRIEVED

0xb

DEV_RETRIEVE_REJECT

CSM_EVENT_ISDN_RETRIEVE_REJ

0xc

DEV_CONFR_ACK

CSM_EVENT_ISDN_CONFERENCE

0xd

DEV_CONFR_REJECT

CSM_EVENT_ISDN_CONFERENCE_REJ

0xe

DEV_TRANS_ACK

CSM_EVENT_ISDN_TRANSFERRED

0xf

DEV_TRANS_REJECT

CSM_EVENT_ISDN_TRANSFER_REJ

Table 244 shows cause values that are assigned only to call-progressing events.

Table 244 Cause Values

Hexadecimal Value

Cause Definitions

0x01

UNASSIGNED_NUMBER

0x02

NO_ROUTE

0x03

NO_ROUTE_DEST

0x04

NO_PREFIX

0x06

CHANNEL_UNACCEPTABLE

0x07

CALL_AWARDED

0x08

CALL_PROC_OR_ERROR

0x09

PREFIX_DIALED_ERROR

0x0a

PREFIX_NOT_DIALED

0x0b

EXCESSIVE_DIGITS

0x0d

SERVICE_DENIED

0x10

NORMAL_CLEARING

0x11

USER_BUSY

0x12

NO_USER_RESPONDING

0x13

NO_USER_ANSWER

0x15

CALL_REJECTED

0x16

NUMBER_CHANGED

0x1a

NON_SELECTED_CLEARING

0x1b

DEST_OUT_OF_ORDER

0x1c

INVALID_NUMBER_FORMAT

0x1d

FACILITY_REJECTED

0x1e

RESP_TO_STAT_ENQ

0x1f

UNSPECIFIED_CAUSE

0x22

NO_CIRCUIT_AVAILABLE

0x26

NETWORK_OUT_OF_ORDER

0x29

TEMPORARY_FAILURE

0x2a

NETWORK_CONGESTION

0x2b

ACCESS_INFO_DISCARDED

0x2c

REQ_CHANNEL_NOT_AVAIL

0x2d

PRE_EMPTED

0x2f

RESOURCES_UNAVAILABLE

0x32

FACILITY_NOT_SUBSCRIBED

0x33

BEARER_CAP_INCOMPAT

0x34

OUTGOING_CALL_BARRED

0x36

INCOMING_CALL_BARRED

0x39

BEARER_CAP_NOT_AUTH

0x3a

BEAR_CAP_NOT_AVAIL

0x3b

CALL_RESTRICTION

0x3c

REJECTED_TERMINAL

0x3e

SERVICE_NOT_ALLOWED

0x3f

SERVICE_NOT_AVAIL

0x41

CAP_NOT_IMPLEMENTED

0x42

CHAN_NOT_IMPLEMENTED

0x45

FACILITY_NOT_IMPLEMENT

0x46

BEARER_CAP_RESTRICTED

0x4f

SERV_OPT_NOT_IMPLEMENT

0x51

INVALID_CALL_REF

0x52

CHAN_DOES_NOT_EXIST

0x53

SUSPENDED_CALL_EXISTS

0x54

NO_CALL_SUSPENDED

0x55

CALL_ID_IN_USE

0x56

CALL_ID_CLEARED

0x58

INCOMPATIBLE_DEST

0x5a

SEGMENTATION_ERROR

0x5b

INVALID_TRANSIT_NETWORK

0x5c

CS_PARAMETER_NOT_VALID

0x5f

INVALID_MSG_UNSPEC

0x60

MANDATORY_IE_MISSING

0x61

NONEXISTENT_MSG

0x62

WRONG_MESSAGE

0x63

BAD_INFO_ELEM

0x64

INVALID_ELEM_CONTENTS

0x65

WRONG_MSG_FOR_STATE

0x66

TIMER_EXPIRY

0x67

MANDATORY_IE_LEN_ERR

0x6f

PROTOCOL_ERROR

0x7f

INTERWORKING_UNSPEC

Examples

This section provides debug output examples for three call scenarios, displaying the sequence of events that occur during a POTS dial call or POTS disconnect call.

Call Scenario 1

In this example call scenario, port 1 is on the hook, the application dial is set to call 4085552221, and the far-end successfully connects.
Router# debug pots csm
Router# test pots 1 dial 4085552221#
Router#
The following output shows an event indicating that port 1 is being used by the dial application:
01:58:27: CSM_PROC_IDLE: CSM_EVENT_VDEV_APPLICATION_CALL, call id = 0x0, port = 1
The following output shows events indicating that the CSM is receiving the application digits of the number to dial:
01:58:27: CSM_PROC_APPLIC_DIALING: CSM_EVENT_VDEV_DIGIT, call id = 0x0, port = 1
01:58:27: CSM_PROC_APPLIC_DIALING: CSM_EVENT_VDEV_DIGIT, call id = 0x0, port = 1
01:58:27: CSM_PROC_APPLIC_DIALING: CSM_EVENT_VDEV_DIGIT, call id = 0x0, port = 1
01:58:27: CSM_PROC_APPLIC_DIALING: CSM_EVENT_VDEV_DIGIT, call id = 0x0, port = 1
01:58:27: CSM_PROC_APPLIC_DIALING: CSM_EVENT_VDEV_DIGIT, call id = 0x0, port = 1
01:58:27: CSM_PROC_APPLIC_DIALING: CSM_EVENT_VDEV_DIGIT, call id = 0x0, port = 1
01:58:27: CSM_PROC_APPLIC_DIALING: CSM_EVENT_VDEV_DIGIT, call id = 0x0, port = 1
01:58:27: CSM_PROC_APPLIC_DIALING: CSM_EVENT_VDEV_DIGIT, call id = 0x0, port = 1
01:58:27: CSM_PROC_APPLIC_DIALING: CSM_EVENT_VDEV_DIGIT, call id = 0x0, port = 1
01:58:27: CSM_PROC_APPLIC_DIALING: CSM_EVENT_VDEV_DIGIT, call id = 0x0, port = 1
The following output shows that the telephone connected to port 1 is off the hook:
01:58:39: CSM_PROC_APPLIC_DIALING: CSM_EVENT_VDEV_OFFHOOK, call id = 0x0, port = 1
The following output shows a call-proceeding event pair indicating that the router ISDN software has sent the dialed digits to the ISDN switch:
01:58:40: EVENT_FROM_ISDN:dchan_idb=0x280AF38, call_id=0x8004, ces=0x1 bchan=0x0, 
event=0x3, cause=0x0 
01:58:40: CSM_PROC_ENBLOC_DIALING: CSM_EVENT_ISDN_PROC, call id = 
0x8004, port = 1
The following output shows the call-progressing event pair indicating that the telephone at the far end is ringing:
01:58:40: EVENT_FROM_ISDN:dchan_idb=0x280AF38, call_id=0x8004, ces=0x1 bchan=0xFFFFFFFF, 
event=0x5, cause=0x0
01:58:40: CSM_PROC_ENBLOC_DIALING: CSM_EVENT_ISDN_CALL_PROGRESSING, call id = 0x8004, port 
= 1
The following output shows a call-connecting event pair indicating that the telephone at the far end has answered:
01:58:48: EVENT_FROM_ISDN:dchan_idb=0x280AF38, call_id=0x8004, ces=0x1 bchan=0xFFFFFFFF, 
event=0x4, cause=0x0
01:58:48: CSM_PROC_CONNECTING: CSM_EVENT_ISDN_CONNECTED, call id = 0x8004, port = 1
The following output shows a call-progressing event pair indicating that the telephone at the far end has hung up and that the calling telephone is receiving an in-band tone from the ISDN switch:
01:58:55: EVENT_FROM_ISDN:dchan_idb=0x280AF38, call_id=0x8004, ces=0x1 bchan=0xFFFFFFFF, 
event=0x5, cause=0x10
01:58:55: CSM_PROC_CONNECTED: CSM_EVENT_ISDN_CALL_PROGRESSING, call id = 0x8004, port = 1
The following output shows that the telephone connected to port 1 has hung up:
01:58:57: CSM_PROC_CONNECTED: CSM_EVENT_VDEV_ONHOOK, call id = 0x8004, port = 1
The following output shows an event pair indicating that the call has been terminated:
01:58:57: EVENT_FROM_ISDN:dchan_idb=0x280AF38, call_id=0x8004, ces=0x1 bchan=0xFFFFFFFF, 
event=0x0, cause=0x0
01:58:57: CSM_PROC_NEAR_END_DISCONNECT: CSM_EVENT_ISDN_DISCONNECTED, call id = 0x8004, 
port = 1
813_local#
Call Scenario 2

In this example scenario, port 1 is on the hook, the application dial is set to call 4085552221, and the destination number is busy.
Router# debug pots csm
Router# test pots 1 dial 4085552221#
Router#
The following output shows that port 1 is used by the dial application:
01:59:42: CSM_PROC_IDLE: CSM_EVENT_VDEV_APPLICATION_CALL, call id = 0x0, port = 1
The following output shows the events indicating that the CSM is receiving the application digits of the number to call:
01:59:42: CSM_PROC_APPLIC_DIALING: CSM_EVENT_VDEV_DIGIT, call id = 0x0, port = 1
01:59:42: CSM_PROC_APPLIC_DIALING: CSM_EVENT_VDEV_DIGIT, call id = 0x0, port = 1
01:59:42: CSM_PROC_APPLIC_DIALING: CSM_EVENT_VDEV_DIGIT, call id = 0x0, port = 1
01:59:42: CSM_PROC_APPLIC_DIALING: CSM_EVENT_VDEV_DIGIT, call id = 0x0, port = 1
01:59:42: CSM_PROC_APPLIC_DIALING: CSM_EVENT_VDEV_DIGIT, call id = 0x0, port = 1
01:59:42: CSM_PROC_APPLIC_DIALING: CSM_EVENT_VDEV_DIGIT, call id = 0x0, port = 1
01:59:42: CSM_PROC_APPLIC_DIALING: CSM_EVENT_VDEV_DIGIT, call id = 0x0, port = 1
01:59:42: CSM_PROC_APPLIC_DIALING: CSM_EVENT_VDEV_DIGIT, call id = 0x0, port = 1
01:59:42: CSM_PROC_APPLIC_DIALING: CSM_EVENT_VDEV_DIGIT, call id = 0x0, port = 1
01:59:42: CSM_PROC_APPLIC_DIALING: CSM_EVENT_VDEV_DIGIT, call id = 0x0, port = 1
The following output shows an event indicating that the telephone connected to port 1 is off the hook:
01:59:52: CSM_PROC_APPLIC_DIALING: CSM_EVENT_VDEV_OFFHOOK, call id = 0x0, port = 1
The following output shows a call-proceeding event pair indicating that the telephone at the far end is busy:
01:59:52: EVENT_FROM_ISDN:dchan_idb=0x280AF38, call_id=0x8005, ces=0x1 bchan=0x0, 
event=0x3, cause=0x11
01:59:52: CSM_PROC_ENBLOC_DIALING: CSM_EVENT_ISDN_PROC, call id = 0x8005, port = 1
The following output shows a call-progressing event pair indicating that the calling telephone is receiving an in-band busy tone from the ISDN switch:
01:59:58: EVENT_FROM_ISDN:dchan_idb=0x280AF38, call_id=0x8005, ces=0x1 bchan=0xFFFFFFFF, 
event=0x5, cause=0x0
01:59:58: CSM_PROC_ENBLOC_DIALING: CSM_EVENT_ISDN_CALL_PROGRESSING, call id = 0x8005, port 
= 1
The following output shows an event indicating that the calling telephone has hung up:
02:00:05: CSM_PROC_ENBLOC_DIALING: CSM_EVENT_VDEV_ONHOOK, call id = 0x8005, port = 1
The following output shows an event pair indicating that the call has been terminated:
02:00:05: EVENT_FROM_ISDN:dchan_idb=0x280AF38, call_id=0x8005, ces=0x1 bchan=0xFFFFFFFF, 
event=0x0, cause=0x0
02:00:05: CSM_PROC_NEAR_END_DISCONNECT: CSM_EVENT_ISDN_DISCONNECTED, call id = 0x8005, 
port = 1
Call Scenario 3

In this example call scenario, port 1 is on the hook, the application dial is set to call 4086661112, the far end successfully connects, and the command test pots disconnect terminates the call:
Router# debug pots csm
Router# test pots 1 dial 4086661112
Router#
The following output follows the same sequence of events as shown in Call Scenario 1:
1d03h: CSM_PROC_IDLE: CSM_EVENT_VDEV_APPLICATION_CALL, call id = 0x0, port = 1
1d03h: CSM_PROC_APPLIC_DIALING: CSM_EVENT_VDEV_DIGIT, call id = 0x0, port = 1
1d03h: CSM_PROC_APPLIC_DIALING: CSM_EVENT_VDEV_DIGIT, call id = 0x0, port = 1
1d03h: CSM_PROC_APPLIC_DIALING: CSM_EVENT_VDEV_DIGIT, call id = 0x0, port = 1
1d03h: CSM_PROC_APPLIC_DIALING: CSM_EVENT_VDEV_DIGIT, call id = 0x0, port = 1
1d03h: CSM_PROC_APPLIC_DIALING: CSM_EVENT_VDEV_DIGIT, call id = 0x0, port = 1
1d03h: CSM_PROC_APPLIC_DIALING: CSM_EVENT_VDEV_DIGIT, call id = 0x0, port = 1
1d03h: CSM_PROC_APPLIC_DIALING: CSM_EVENT_VDEV_DIGIT, call id = 0x0, port = 1
1d03h: CSM_PROC_APPLIC_DIALING: CSM_EVENT_VDEV_DIGIT, call id = 0x0, port = 1
1d03h: CSM_PROC_APPLIC_DIALING: CSM_EVENT_VDEV_DIGIT, call id = 0x0, port = 1
1d03h: CSM_PROC_APPLIC_DIALING: CSM_EVENT_VDEV_DIGIT, call id = 0x0, port = 1
1d03h: CSM_PROC_APPLIC_DIALING: CSM_EVENT_VDEV_OFFHOOK, call id = 0x0, port = 1
1d03h: EVENT_FROM_ISDN:dchan_idb=0x2821F38, call_id=0x8039, ces=0x1
   bchan=0x0, event=0x3, cause=0x0
1d03h: CSM_PROC_ENBLOC_DIALING: CSM_EVENT_ISDN_PROC, call id = 0x8039, port = 1
1d03h: EVENT_FROM_ISDN:dchan_idb=0x2821F38, call_id=0x8039, ces=0x1
   bchan=0xFFFFFFFF, event=0x5, cause=0x0
1d03h: CSM_PROC_ENBLOC_DIALING: CSM_EVENT_ISDN_CALL_PROGRESSING, call id = 0x8039, 
    port = 1
Router# test pots 1 disconnect
The test pots disconnect command disconnects the call before you physically need to put the telephone back on the hook:
1d03h: CSM_PROC_CONNECTING: CSM_EVENT_VDEV_APPLICATION_HANGUP_CALL, call id = 0x8039, 
     port = 1
1d03h: EVENT_FROM_ISDN:dchan_idb=0x2821F38, call_id=0x8039, ces=0x1
   bchan=0xFFFFFFFF, event=0x0, cause=0x0
1d03h: CSM_PROC_DISCONNECTING: CSM_EVENT_ISDN_DISCONNECTED, call id = 0x8039,  
    port = 1
1d03h: CSM_PROC_DISCONNECTING: CSM_EVENT_TIMEOUT, call id = 0x8039, port = 1
debug ppp

To display information on traffic and exchanges in an internetwork implementing the Point-to-Point Protocol (PPP), use the debug ppp command in privileged EXEC mode. To disable debugging output, use the no form of this command.

debug ppp {packet | negotiation | error | authentication | compression | cbcp}
no debug ppp {packet | negotiation | error | authentication | compression | cbcp}
Syntax Description

packet

Displays PPP packets being sent and received. (This command displays low-level packet dumps.)

negotiation

Displays PPP packets sent during PPP startup, where PPP options are negotiated.

error

Displays protocol errors and error statistics associated with PPP connection negotiation and operation.

authentication

Displays authentication protocol messages, including Challenge Authentication Protocol (CHAP) packet exchanges and Password Authentication Protocol (PAP) exchanges.

compression

Displays information specific to the exchange of PPP connections using Microsoft Point-to-Point Compression (MPPC). This command is useful for obtaining incorrect packet sequence number information where MPPC compression is enabled.

cbcp

Displays protocol errors and statistics associated with PPP connection negotiations using Microsoft Callback (MSCB).

Command Modes

Privileged EXEC

Usage Guidelines

Use the debug ppp command when trying to find the following:

•The Network Control Protocols (NCPs) that are supported on either end of a PPP connection

•Any loops that might exist in a PPP internetwork

•Nodes that are (or are not) properly negotiating PPP connections

•Errors that have occurred over the PPP connection

•Causes for CHAP session failures

•Causes for PAP session failures

•Information specific to the exchange of PPP connections using the Callback Control Protocol (CBCP), used by Microsoft clients

•Incorrect packet sequence number information where MPPC compression is enabled

Refer to Internet RFCs 1331, 1332, and 1333 for details concerning PPP-related nomenclature and protocol information.

Caution The debug ppp compression command is CPU-intensive and should be used with caution. This command should be disabled immediately after debugging.

Examples

The following is sample output from the debug ppp packet command as seen from the Link Quality Monitor (LQM) side of the connection. This example depicts packet exchanges under normal PPP operation.
Router# debug ppp packet
PPP Serial4(o): lcp_slqr() state = OPEN magic = D21B4, len = 48
PPP Serial4(i): pkt type 0xC025, datagramsize 52
PPP Serial4(i): lcp_rlqr() state = OPEN magic = D3454, len = 48
PPP Serial4(i): pkt type 0xC021, datagramsize 16
PPP Serial4: I LCP ECHOREQ(9) id 3 (C) magic D3454
PPP Serial4: input(C021) state = OPEN code = ECHOREQ(9) id = 3 len = 12
PPP Serial4: O LCP ECHOREP(A) id 3 (C) magic D21B4
PPP Serial4(o): lcp_slqr() state = OPEN magic = D21B4, len = 48
PPP Serial4(i): pkt type 0xC025, datagramsize 52
PPP Serial4(i): lcp_rlqr() state = OPEN magic = D3454, len = 48
PPP Serial4(i): pkt type 0xC021, datagramsize 16
PPP Serial4: I LCP ECHOREQ(9) id 4 (C) magic D3454
PPP Serial4: input(C021) state = OPEN code = ECHOREQ(9) id = 4 len = 12
PPP Serial4: O LCP ECHOREP(A) id 4 (C) magic D21B4
PPP Serial4(o): lcp_slqr() state = OPEN magic = D21B4, len = 48
PPP Serial4(i): pkt type 0xC025, datagramsize 52
PPP Serial4(i): lcp_rlqr() state = OPEN magic = D3454, len = 48
PPP Serial4(i): pkt type 0xC021, datagramsize 16
PPP Serial4: I LCP ECHOREQ(9) id 5 (C) magic D3454
PPP Serial4: input(C021) state = OPEN code = ECHOREQ(9) id = 5 len = 12
PPP Serial4: O LCP ECHOREP(A) id 5 (C) magic D21B4
PPP Serial4(o): lcp_slqr() state = OPEN magic = D21B4, len = 48
PPP Serial4(i): pkt type 0xC025, datagramsize 52
PPP Serial4(i): lcp_rlqr() state = OPEN magic = D3454, len = 48
PPP Serial4(i): pkt type 0xC021, datagramsize 16
PPP Serial4: I LCP ECHOREQ(9) id 6 (C) magic D3454
PPP Serial4: input(C021) state = OPEN code = ECHOREQ(9) id = 6 len = 12
PPP Serial4: O LCP ECHOREP(A) id 6 (C) magic D21B4
PPP Serial4(o): lcp_slqr() state = OPEN magic = D21B4, len = 48
PPP Serial4(i): pkt type 0xC025, datagramsize 52
PPP Serial4(i): lcp_rlqr() state = OPEN magic = D3454, len = 48
PPP Serial4(i): pkt type 0xC021, datagramsize 16
PPP Serial4: I LCP ECHOREQ(9) id 7 (C) magic D3454
PPP Serial4: input(C021) state = OPEN code = ECHOREQ(9) id = 7 len = 12
PPP Serial4: O LCP ECHOREP(A) id 7 (C) magic D21B4
PPP Serial4(o): lcp_slqr() state = OPEN magic = D21B4, len = 48
Table 245 describes the significant fields shown in the display.

Table 245 debug ppp packet Field Descriptions

Field

Description

PPP

PPP debugging output.

Serial4

Interface number associated with this debugging information.

(o), O

Packet was detected as an output packet.

(i), I

Packet was detected as an input packet.

lcp_slqr()

Procedure name; running LQM, send a Link Quality Report (LQR).

lcp_rlqr()

Procedure name; running LQM, received an LQR.

input (C021)

Router received a packet of the specified packet type (in hexadecimal notation). A value of C025 indicates packet of type LQM.

state = OPEN

PPP state; normal state is OPEN.

magic = D21B4

Magic Number for indicated node; when output is indicated, this is the Magic Number of the node on which debugging is enabled. The actual Magic Number depends on whether the packet detected is indicated as I or O.

datagramsize 52

Packet length including header.

code = ECHOREQ(9)

Identifies the type of packet received. Both forms of the packet, string and hexadecimal, are presented.

len = 48

Packet length without header.

id = 3

ID number per Link Control Protocol (LCP) packet format.

pkt type 0xC025

Packet type in hexadecimal notation; typical packet types are C025 for LQM and C021 for LCP.

LCP ECHOREQ(9)

Echo Request; value in parentheses is the hexadecimal representation of the LCP type.

LCP ECHOREP(A)

Echo Reply; value in parentheses is the hexadecimal representation of the LCP type.

To elaborate on the displayed output, consider the partial exchange. This sequence shows that one side is using ECHO for its keepalives and the other side is using LQRs.
Router# debug ppp packet
PPP Serial4(o): lcp_slqr() state = OPEN magic = D21B4, len = 48
PPP Serial4(i): pkt type 0xC025, datagramsize 52
PPP Serial4(i): lcp_rlqr() state = OPEN magic = D3454, len = 48
PPP Serial4(i): pkt type 0xC021, datagramsize 16
PPP Serial4: I LCP ECHOREQ(9) id 3 (C) magic D3454
PPP Serial4: input(C021) state = OPEN code = ECHOREQ(9) id = 3 len = 12
PPP Serial4: O LCP ECHOREP(A) id 3 (C) magic D21B4
PPP Serial4(o): lcp_slqr() state = OPEN magic = D21B4, len = 48
The first line states that the router with debugging enabled has sent an LQR to the other side of the PPP connection:
PPP Serial4(o): lcp_slqr() state = OPEN magic = D21B4, len = 48
The next two lines indicate that the router has received a packet of type C025 (LQM) and provides details about the packet:
PPP Serial4(i): pkt type 0xC025, datagramsize 52
PPP Serial4(i): lcp_rlqr() state = OPEN magic = D3454, len = 48
The next two lines indicate that the router received an ECHOREQ of type C021 (LCP). The other side is sending ECHOs. The router on which debugging is configured for LQM but also responds to ECHOs.
PPP Serial4(i): pkt type 0xC021, datagramsize 16
PPP Serial4: I LCP ECHOREQ(9) id 3 (C) magic D3454
Next, the router is detected to have responded to the ECHOREQ with an ECHOREP and is preparing to send out an LQR:
PPP Serial4: O LCP ECHOREP(A) id 3 (C) magic D21B4
PPP Serial4(o): lcp_slqr() state = OPEN magic = D21B4, len = 48
The following is sample output from the debug ppp negotiation command. This is a normal negotiation, where both sides agree on Network Control Program (NCP) parameters. In this case, protocol type IP is proposed and acknowledged.
Router# debug ppp negotiation
ppp: sending CONFREQ, type = 4 (CI_QUALITYTYPE), value = C025/3E8
ppp: sending CONFREQ, type = 5 (CI_MAGICNUMBER), value = 3D56CAC
ppp: received config for type = 4 (QUALITYTYPE) acked
ppp: received config for type = 5 (MAGICNUMBER) value = 3D567F8 acked (ok)
PPP Serial4: state = ACKSENT fsm_rconfack(C021): rcvd id 5
ppp: config ACK received, type = 4 (CI_QUALITYTYPE), value = C025
ppp: config ACK received, type = 5 (CI_MAGICNUMBER), value = 3D56CAC
ppp: ipcp_reqci: returning CONFACK.
 (ok)
PPP Serial4: state = ACKSENT fsm_rconfack(8021): rcvd id 4
Table 246 describes significant fields shown in the display.

Table 246 debug ppp negotiation Field Descriptions

Field

Description

ppp

PPP debugging output.

sending CONFREQ

Router sent a configuration request.

type = 4 (CI_QUALITYTYPE)

Type of LCP configuration option that is being negotiated and a descriptor. A type value of 4 indicates Quality Protocol negotiation; a type value of 5 indicates Magic Number negotiation.

value = C025/3E8

For Quality Protocol negotiation, indicates NCP type and reporting period. In the example, C025 indicates LQM; 3E8 is a hexadecimal value translating to about 10 seconds (in hundredths of a second).

value = 3D56CAC

For Magic Number negotiation, indicates the Magic Number being negotiated.

received config

Receiving node has received the proposed option negotiation for the indicated option type.

acked

Acknowledgment and acceptance of options.

state = ACKSENT

Specific PPP state in the negotiation process.

ipcp_reqci

IPCP notification message; sending CONFACK.

fsm_rconfack (8021)

Procedure fsm_rconfack processes received CONFACKs, and the protocol (8021) is IP.

The first two lines indicate that the router is trying to bring up LCP and will use the indicated negotiation options (Quality Protocol and Magic Number). The value fields are the values of the options themselves. C025/3E8 translates to Quality Protocol LQM. 3E8 is the reporting period (in hundredths of a second). 3D56CAC is the value of the Magic Number for the router.
ppp: sending CONFREQ, type = 4 (CI_QUALITYTYPE), value = C025/3E8
ppp: sending CONFREQ, type = 5 (CI_MAGICNUMBER), value = 3D56CAC
The next two lines indicate that the other side negotiated for options 4 and 5 as requested and acknowledged both. If the responding end does not support the options, a CONFREJ is sent by the responding node. If the responding end does not accept the value of the option, a Configure-Negative-Acknowledge (CONFNAK) is sent with the value field modified.
ppp: received config for type = 4 (QUALITYTYPE) acked
ppp: received config for type = 5 (MAGICNUMBER) value = 3D567F8 acked (ok)
The next three lines indicate that the router received a CONFAK from the responding side and displays accepted option values. Use the rcvd id field to verify that the CONFREQ and CONFACK have the same ID field.
PPP Serial4: state = ACKSENT fsm_rconfack(C021): rcvd id 5
ppp: config ACK received, type = 4 (CI_QUALITYTYPE), value = C025
ppp: config ACK received, type = 5 (CI_MAGICNUMBER), value = 3D56CAC
The next line indicates that the router has IP routing enabled on this interface and that the IPCP NCP negotiated successfully:
ppp: ipcp_reqci: returning CONFACK.
In the last line, the state of the router is listed as ACKSENT.
PPP Serial4: state = ACKSENT fsm_rconfack(C021): rcvd id 5\
The following is sample output from when the debug ppp packet and debug ppp negotiation commands are enabled at the same time.

The following is sample output from the debug ppp negotiation command when the remote side of the connection is unable to respond to LQM requests:
Router# debug ppp negotiation
ppp: sending CONFREQ, type = 4 (CI_QUALITYTYPE), value = C025/3E8
ppp: sending CONFREQ, type = 5 (CI_MAGICNUMBER), value = 44B7010
ppp: sending CONFREQ, type = 4 (CI_QUALITYTYPE), value = C025/3E8
ppp: sending CONFREQ, type = 5 (CI_MAGICNUMBER), value = 44B7010
ppp: sending CONFREQ, type = 4 (CI_QUALITYTYPE), value = C025/3E8
ppp: sending CONFREQ, type = 5 (CI_MAGICNUMBER), value = 44B7010
ppp: sending CONFREQ, type = 4 (CI_QUALITYTYPE), value = C025/3E8
ppp: sending CONFREQ, type = 5 (CI_MAGICNUMBER), value = 44B7010
ppp: sending CONFREQ, type = 4 (CI_QUALITYTYPE), value = C025/3E8
ppp: sending CONFREQ, type = 5 (CI_MAGICNUMBER), value = 44B7010
ppp: sending CONFREQ, type = 4 (CI_QUALITYTYPE), value = C025/3E8
ppp: sending CONFREQ, type = 5 (CI_MAGICNUMBER), value = 44B7010
ppp: sending CONFREQ, type = 4 (CI_QUALITYTYPE), value = C025/3E8
ppp: sending CONFREQ, type = 5 (CI_MAGICNUMBER), value = 44B7010
ppp: sending CONFREQ, type = 4 (CI_QUALITYTYPE), value = C025/3E8
ppp: sending CONFREQ, type = 5 (CI_MAGICNUMBER), value = 44B7010
ppp: sending CONFREQ, type = 4 (CI_QUALITYTYPE), value = C025/3E8
ppp: sending CONFREQ, type = 5 (CI_MAGICNUMBER), value = 44B7010
ppp: sending CONFREQ, type = 4 (CI_QUALITYTYPE), value = C025/3E8
ppp: sending CONFREQ, type = 5 (CI_MAGICNUMBER), value = 44B7010
ppp: sending CONFREQ, type = 4 (CI_QUALITYTYPE), value = C025/3E8
ppp: sending CONFREQ, type = 5 (CI_MAGICNUMBER), value = 44B7010
ppp: sending CONFREQ, type = 4 (CI_QUALITYTYPE), value = C025/3E8
ppp: sending CONFREQ, type = 5 (CI_MAGICNUMBER), value = 44C1488
The following is sample output when no response is detected for configuration requests (with both the debug ppp negotiation and debug ppp packet commands enabled):
Router# debug ppp negotiation
Router# debug ppp packet
ppp: sending CONFREQ, type = 4 (CI_QUALITYTYPE), value = C025/3E8
ppp: sending CONFREQ, type = 5 (CI_MAGICNUMBER), value = 44DFDC8
PPP Serial4: O LCP CONFREQ(1) id 14 (12) QUALITYTYPE (8) 192 37 0 0 3 232
   MAGICNUMBER (6) 4 77 253 200
ppp: TIMEout: Time= 44E0980 State= 3
ppp: sending CONFREQ, type = 4 (CI_QUALITYTYPE), value = C025/3E8
ppp: sending CONFREQ, type = 5 (CI_MAGICNUMBER), value = 44DFDC8
PPP Serial4: O LCP CONFREQ(1) id 15 (12) QUALITYTYPE (8) 192 37 0 0 3 232
   MAGICNUMBER (6) 4 77 253 200
ppp: TIMEout: Time= 44E1828 State= 3
ppp: sending CONFREQ, type = 4 (CI_QUALITYTYPE), value = C025/3E8
ppp: sending CONFREQ, type = 5 (CI_MAGICNUMBER), value = 44DFDC8
PPP Serial4: O LCP CONFREQ(1) id 16 (12) QUALITYTYPE (8) 192 37 0 0 3 232
   MAGICNUMBER (6) 4 77 253 200
ppp: TIMEout: Time= 44E27C8 State= 3
ppp: sending CONFREQ, type = 4 (CI_QUALITYTYPE), value = C025/3E8
ppp: sending CONFREQ, type = 5 (CI_MAGICNUMBER), value = 44DFDC8
PPP Serial4: O LCP CONFREQ(1) id 17 (12) QUALITYTYPE (8) 192 37 0 0 3 232
   MAGICNUMBER (6) 4 77 253 200
ppp: TIMEout: Time= 44E3768 State= 3
The following is sample output from the debug ppp error command. These messages might appear when the Quality Protocol option is enabled on an interface that is already running PPP.
Router# debug ppp error
PPP Serial3(i): rlqr receive failure. successes = 15
PPP: myrcvdiffp = 159 peerxmitdiffp = 41091
PPP: myrcvdiffo = 2183 peerxmitdiffo = 1714439
PPP: threshold = 25
PPP Serial4(i): rlqr transmit failure. successes = 15
PPP: myxmitdiffp = 41091 peerrcvdiffp = 159
PPP: myxmitdiffo = 1714439 peerrcvdiffo = 2183
PPP: l->OutLQRs = 1 LastOutLQRs = 1
PPP: threshold = 25
PPP Serial3(i): lqr_protrej() Stop sending LQRs.
PPP Serial3(i): The link appears to be looped back.
Table 247 describes the significant fields shown in the display.

Table 247 debug ppp error Field Descriptions

Field

Description

PPP

PPP debugging output.

Serial3(i)

Interface number associated with this debugging information; indicates that this is an input packet.

rlqr receive failure

Request to negotiate the Quality Protocol option is not accepted.

myrcvdiffp = 159

Number of packets received over the time period.

peerxmitdiffp = 41091

Number of packets sent by the remote node over this period.

myrcvdiffo = 2183

Number of octets received over this period.

peerxmitdiffo = 1714439

Number of octets sent by the remote node over this period.

threshold = 25

Maximum error percentage acceptable on this interface. This percentage is calculated by the threshold value entered in the ppp quality number interface configuration command. A value of 100 - number (100 minus number) is the maximum error percentage. In this case, a number of 75 was entered. This means that the local router must maintain a minimum 75 percent non-error percentage, or the PPP link will be considered down.

OutLQRs = 1

Local router's current send LQR sequence number.

LastOutLQRs = 1

The last sequence number that the remote node side has seen from the local node.

The following is sample output from the debug ppp authentication command. Use this command to determine why an authentication fails.
Router# debug ppp authentication
Serial0: Unable to authenticate. No name received from peer
Serial0: Unable to validate CHAP response. USERNAME pioneer not found.
Serial0: Unable to validate CHAP response. No password defined for USERNAME pioneer
Serial0: Failed CHAP authentication with remote.
Remote message is Unknown name
Serial0: remote passed CHAP authentication.
Serial0: Passed CHAP authentication with remote.
Serial0: CHAP input code = 4 id = 3 len = 48
In general, these messages are self-explanatory. Fields that can show optional output are outlined in Table 248.

Table 248 debug ppp authentication Field Descriptions

Field

Description

Serial0

Interface number associated with this debugging information and CHAP access session in question.

USERNAME pioneer not found.

The name pioneer in this example is the name received in the CHAP response. The router looks up this name in the list of usernames that are configured for the router.

Remote message is Unknown name

The following messages can appear:

•No name received to authenticate

•Unknown name

•No secret for given name

•Short MD5 response received

•MD compare failed

code = 4

Specific CHAP type packet detected. Possible values are as follows:

•1—Challenge

•2—Response

•3—Success

•4—Failure

id = 3

ID number per LCP packet format.

len = 48

Packet length without header.

The following shows sample output from the debug ppp command using the cbcp keyword. This output depicts packet exchanges under normal PPP operation where the Cisco access server is waiting for the remote PC to respond to the MSCB request. The router also has debug ppp negotiation and service timestamps msec commands enabled.
Router# debug ppp cbcp
Dec 17 00:48:11.302: As8 MCB: User mscb Callback Number - Client ANY
Dec 17 00:48:11.306: Async8 PPP: O MCB Request(1) id 1 len 9
Dec 17 00:48:11.310: Async8 MCB: O  1  1  0  9  2  5  0  1  0 
Dec 17 00:48:11.314: As8 MCB: O Request Id 1 Callback Type Client-Num delay 0
Dec 17 00:48:13.342: As8 MCB: Timeout in state WAIT_RESPONSE
Dec 17 00:48:13.346: Async8 PPP: O MCB Request(1) id 2 len 9
Dec 17 00:48:13.346: Async8 MCB: O  1  2  0  9  2  5  0  1  0 
Dec 17 00:48:13.350: As8 MCB: O Request Id 2 Callback Type Client-Num delay 0
Dec 17 00:48:15.370: As8 MCB: Timeout in state WAIT_RESPONSE
Dec 17 00:48:15.374: Async8 PPP: O MCB Request(1) id 3 len 9
Dec 17 00:48:15.374: Async8 MCB: O  1  3  0  9  2  5  0  1  0 
Dec 17 00:48:15.378: As8 MCB: O Request Id 3 Callback Type Client-Num delay 0
Dec 17 00:48:17.398: As8 MCB: Timeout in state WAIT_RESPONSE
Dec 17 00:48:17.402: Async8 PPP: O MCB Request(1) id 4 len 9
Dec 17 00:48:17.406: Async8 MCB: O  1  4  0  9  2  5  0  1  0 
Dec 17 00:48:17.406: As8 MCB: O Request Id 4 Callback Type Client-Num delay 0
Dec 17 00:48:19.426: As8 MCB: Timeout in state WAIT_RESPONSE
Dec 17 00:48:19.430: Async8 PPP: O MCB Request(1) id 5 len 9
Dec 17 00:48:19.430: Async8 MCB: O  1  5  0  9  2  5  0  1  0 
Dec 17 00:48:19.434: As8 MCB: O Request Id 5 Callback Type Client-Num delay 0
Dec 17 00:48:21.454: As8 MCB: Timeout in state WAIT_RESPONSE
Dec 17 00:48:21.458: Async8 PPP: O MCB Request(1) id 6 len 9
Dec 17 00:48:21.462: Async8 MCB: O  1  6  0  9  2  5  0  1  0 
Dec 17 00:48:21.462: As8 MCB: O Request Id 6 Callback Type Client-Num delay 0
Dec 17 00:48:23.482: As8 MCB: Timeout in state WAIT_RESPONSE
Dec 17 00:48:23.486: Async8 PPP: O MCB Request(1) id 7 len 9
Dec 17 00:48:23.490: Async8 MCB: O  1  7  0  9  2  5  0  1  0 
Dec 17 00:48:23.490: As8 MCB: O Request Id 7 Callback Type Client-Num delay 0
Dec 17 00:48:25.510: As8 MCB: Timeout in state WAIT_RESPONSE
Dec 17 00:48:25.514: Async8 PPP: O MCB Request(1) id 8 len 9
Dec 17 00:48:25.514: Async8 MCB: O  1  8  0  9  2  5  0  1  0 
Dec 17 00:48:25.518: As8 MCB: O Request Id 8 Callback Type Client-Num delay 0
Dec 17 00:48:26.242: As8 PPP: I pkt type 0xC029, datagramsize 18
Dec 17 00:48:26.246: Async8 PPP: I MCB Response(2) id 8 len 16
Dec 17 00:48:26.250: Async8 MCB: I  2  8  0  10  2  C  C  1  32  34  39  32  36  31  33  0 
Dec 17 00:48:26.254: As8 MCB: Received response
Dec 17 00:48:26.258: As8 MCB: Response CBK-Client-Num 2 12 12,  addr 1-2492613
Dec 17 00:48:26.262: Async8 PPP: O MCB Ack(3) id 9 len 16
Dec 17 00:48:26.266: Async8 MCB: O  3  9  0  10  2  C  C  1  32  34  39  32  36  31  33  0 
Dec 17 00:48:26.270: As8 MCB: O Ack Id 9 Callback Type Client-Num delay 12
Dec 17 00:48:26.270: As8 MCB: Negotiated MCB with peer
Dec 17 00:48:26.390: As8 LCP: I TERMREQ [Open] id 4 len 8 (0x00000000)
Dec 17 00:48:26.390: As8 LCP: O TERMACK [Open] id 4 len 4
Dec 17 00:48:26.394: As8 MCB: Peer terminating the link
Dec 17 00:48:26.402: As8 MCB: Initiate Callback for mscb at 2492613 using Async
The following is sample output from the debug ppp compression command with service timestamps enabled and shows a typical PPP packet exchange between the router and Microsoft client where the MPPC header sequence numbers increment correctly:
Router# debug ppp compression
00:04:14: BR0:1 MPPC: Decomp - hdr/exp_cc# 0x2003/0x0003
00:04:14: BR0:1 MPPC: Decomp - hdr/exp_cc# 0x2004/0x0004
00:04:14: BR0:1 MPPC: Decomp - hdr/exp_cc# 0x2005/0x0005
00:04:14: BR0:1 MPPC: Decomp - hdr/exp_cc# 0x2006/0x0006
00:04:14: BR0:1 MPPC: Decomp - hdr/exp_cc# 0x2007/0x0007	
Table 249 describes the significant fields shown in the display.

Table 249 debug ppp compression Field Descriptions

Field

Description

interface

Interface enabled with MPPC.

Decomp - hdr/

Decompression header and bit settings.

exp_cc#

Expected coherency count.

0x2003

Received sequence number.

0x0003

Expected sequence number.

The following shows sample output from debug ppp negotiation and debug ppp error commands, which can be used to troubleshoot initial PPP negotiation and setup errors. This example shows a virtual interface (virtual interface 1) during normal PPP operation and CCP negotiation.
Router# debug ppp negotiation error
Vt1 PPP: Unsupported or un-negotiated protocol. Link arp
VPDN: Chap authentication succeeded for p5200
Vi1 PPP: Phase is DOWN, Setup
Vi1 VPDN: Virtual interface created for dinesh@cisco.com
Vi1 VPDN: Set to Async interface
Vi1 PPP: Phase is DOWN, Setup
Vi1 VPDN: Clone from Vtemplate 1 filterPPP=0 blocking
Vi1 CCP: Re-Syncing history using legacy method
%LINK-3-UPDOWN: Interface Virtual-Access1, changed state to up
Vi1 PPP: Treating connection as a dedicated line
Vi1 PPP: Phase is ESTABLISHING, Active Open
Vi1 LCP: O CONFREQ [Closed] id 1 len 25
Vi1 LCP:    ACCM 0x000A0000 (0x0206000A0000)
Vi1 LCP:    AuthProto CHAP (0x0305C22305)
Vi1 LCP:    MagicNumber 0x000FB69F (0x0506000FB69F)
Vi1 LCP:    PFC (0x0702)
Vi1 LCP:    ACFC (0x0802)
Vi1 VPDN: Bind interface direction=2
Vi1 PPP: Treating connection as a dedicated line
Vi1 LCP: I FORCED CONFREQ len 21
Vi1 LCP:    ACCM 0x000A0000 (0x0206000A0000)
Vi1 LCP:    AuthProto CHAP (0x0305C22305)
Vi1 LCP:    MagicNumber 0x12A5E4B5 (0x050612A5E4B5)
Vi1 LCP:    PFC (0x0702)
Vi1 LCP:    ACFC (0x0802)
Vi1 VPDN: PPP LCP accepted sent & rcv CONFACK
Vi1 PPP: Phase is AUTHENTICATING, by this end
Vi1 CHAP: O CHALLENGE id 1 len 27 from "l_4000"
Vi1 CHAP: I RESPONSE id 20 len 37 from "dinesh@cisco.com"
Vi1 CHAP: O SUCCESS id 20 len 4
Vi1 PPP: Phase is UP
Vi1 IPCP: O CONFREQ [Closed] id 1 len 10
Vi1 IPCP:    Address 15.2.2.3 (0x03060F020203)
Vi1 CCP: O CONFREQ [Not negotiated] id 1 len 10
Vi1 CCP:    MS-PPC supported bits 0x00000001 (0x120600000001)
Vi1 IPCP: I CONFREQ [REQsent] id 1 len 34
Vi1 IPCP:    Address 0.0.0.0 (0x030600000000)
Vi1 IPCP:    PrimaryDNS 0.0.0.0 (0x810600000000)
Vi1 IPCP:    PrimaryWINS 0.0.0.0 (0x820600000000)
Vi1 IPCP:    SecondaryDNS 0.0.0.0 (0x830600000000)
Vi1 IPCP:    SecondaryWINS 0.0.0.0 (0x840600000000)
Vi1 IPCP: Using the default pool
Vi1 IPCP: Pool returned 11.2.2.5
Vi1 IPCP: O CONFREJ [REQsent] id 1 len 16
Vi1 IPCP:    PrimaryWINS 0.0.0.0 (0x820600000000)
Vi1 IPCP:    SecondaryWINS 0.0.0.0 (0x840600000000)
Vi1 CCP: I CONFREQ [REQsent] id 1 len 15
Vi1 CCP:    MS-PPC supported bits 0x00000001 (0x120600000001)
Vi1 CCP:    Stacker history 1 check mode EXTENDED (0x1105000104)
Vi1 CCP: Already accepted another CCP option, rejecting this STACKER
Vi1 CCP: O CONFREJ [REQsent] id 1 len 9
Vi1 CCP:    Stacker history 1 check mode EXTENDED (0x1105000104)
Vi1 IPCP: I CONFACK [REQsent] id 1 len 10
Vi1 IPCP:    Address 15.2.2.3 (0x03060F020203)
Vi1 CCP: I CONFACK [REQsent] id 1 len 10
Vi1 CCP:    MS-PPC supported bits 0x00000001 (0x120600000001)
Vi1 CCP: I CONFREQ [ACKrcvd] id 2 len 10
Vi1 CCP:    MS-PPC supported bits 0x00000001 (0x120600000001)
Vi1 CCP: O CONFACK [ACKrcvd] id 2 len 10
Vi1 CCP:    MS-PPC supported bits 0x00000001 (0x120600000001)
Vi1 CCP: State is Open
Vi1 IPCP: I CONFREQ [ACKrcvd] id 2 len 22
Vi1 IPCP:    Address 0.0.0.0 (0x030600000000)
Vi1 IPCP:    PrimaryDNS 0.0.0.0 (0x810600000000)
Vi1 IPCP:    SecondaryDNS 0.0.0.0 (0x830600000000)
Vi1 IPCP: O CONFNAK [ACKrcvd] id 2 len 22
Vi1 IPCP:    Address 11.2.2.5 (0x03060B020205)
Vi1 IPCP:    PrimaryDNS 171.69.1.148 (0x8106AB450194)
Vi1 IPCP:    SecondaryDNS 171.69.2.132 (0x8306AB450284)
Vi1 IPCP: I CONFREQ [ACKrcvd] id 3 len 22
Vi1 IPCP:    Address 11.2.2.5 (0x03060B020205)
Vi1 IPCP:    PrimaryDNS 171.69.1.148 (0x8106AB450194)
Vi1 IPCP:    SecondaryDNS 171.69.2.132 (0x8306AB450284)
Vi1 IPCP: O CONFACK [ACKrcvd] id 3 len 22
Vi1 IPCP:    Address 11.2.2.5 (0x03060B020205)
Vi1 IPCP:    PrimaryDNS 171.69.1.148 (0x8106AB450194)
Vi1 IPCP:    SecondaryDNS 171.69.2.132 (0x8306AB450284)
Vi1 IPCP: State is Open
Vi1 IPCP: Install route to 11.2.2.5
debug pppatm

To enable debug reports for PPP over ATM (PPPoA) events, errors, and states, either globally or conditionally, on an interface or virtual circuit (VC), use the debug pppatm command in privileged EXEC mode. To disable debugging output, use the no form of this command.

debug pppatm {event | error | state} [interface atm interface-number [subinterface-number]] vc {[vpi/vci]vci | virtual-circuit-name}
no debug pppatm {event | error | state} [interface atm interface-number [subinterface-number] vc {[vpi/]vci | virtual-circuit-name}
Syntax Description

event

PPPoA events.

error

PPPoA errors.

state

PPPoA state.

interface atm interface-number [subinterface-number]

(Optional) Specifies a particular ATM interface by interface number and optionally a subinterface number separated by a period.

vc [vpi/]vci virtual-circuit-name

(Optional) Virtual circuit (VC) keyword followed by a virtual path identifier (VPI), virtual channel identifier (VCI), and VC name. A slash mark is required after the VPI.

Defaults

No default behavior or values

Command Modes

Privileged EXEC

Command History

Release

Modification

12.2(13)T

This command was introduced.

Usage Guidelines

Each specific PPPoA debug report must be requested on a separate command line; see the "Examples" section.

Examples

The following is example output of a PPPoA session with event, error, and state debug reports enabled on ATM interface 1/0.10:
Router# debug pppatm event interface atm1/0.10
Router# debug pppatm error interface atm1/0.10
Router# debug pppatm state interface atm1/0.10
00:03:08: PPPATM: ATM1/0.10 0/101 [1], Event = Clear Session
00:03:08: PPPATM: ATM1/0.10 0/101 [1], Event = Disconnecting
00:03:08: PPPATM: ATM1/0.10 0/101 [1], Event = AAA gets dynamic attrs
00:03:08: PPPATM: ATM1/0.10 0/101 [1], Event = AAA gets dynamic attrs
00:03:08: PPPATM: ATM1/0.10 0/101 [1], Event = SSS Cleanup
00:03:08: PPPATM: ATM1/0.10 0/101 [0], State = DOWN
00:03:08: PPPATM: ATM1/0.10 0/101 [0], Event = Up Pending
00:03:16: PPPATM: ATM1/0.10 0/101 [0], Event = Up Dequeued
00:03:16: PPPATM: ATM1/0.10 0/101 [0], Event = Processing Up
00:03:16: PPPATM: ATM1/0.10 0/101 [2], Event = Access IE allocated
00:03:16: PPPATM: ATM1/0.10 0/101 [2], Event = Set Pkts to SSS
00:03:16: PPPATM: ATM1/0.10 0/101 [2], Event = AAA gets retrived attrs
00:03:16: PPPATM: ATM1/0.10 0/101 [2], Event = AAA gets nas port details
00:03:16: PPPATM: ATM1/0.10 0/101 [2], Event = AAA gets dynamic attrs
00:03:16: PPPATM: ATM1/0.10 0/101 [2], Event = AAA gets dynamic attrs
00:03:16: PPPATM: ATM1/0.10 0/101 [2], Event = AAA unique id allocated
00:03:16: PPPATM: ATM1/0.10 0/101 [2], Event = No AAA method list set
00:03:16: PPPATM: ATM1/0.10 0/101 [2], Event = SSS Request
00:03:16: PPPATM: ATM1/0.10 0/101 [2], State = NAS_PORT_POLICY_INQUIRY
00:03:16: PPPATM: ATM1/0.10 0/101 [2], Event = SSS Msg Received = 1
00:03:16: PPPATM: ATM1/0.10 0/101 [2], State = PPP_START
00:03:16: PPPATM: ATM1/0.10 0/101 [2], Event = PPP Msg Received = 1
00:03:16: PPPATM: ATM1/0.10 0/101 [2], State = LCP_NEGOTIATION
00:03:27: PPPATM: ATM1/0.10 0/101 [2], Event = PPP Msg Received = 4
00:03:27: PPPATM: ATM1/0.10 0/101 [2], Event = HW Switch support FORW = 0
00:03:27: PPPATM: ATM1/0.10 0/101 [2], Event = Access IE get nas port
00:03:27: PPPATM: ATM1/0.10 0/101 [2], Event = AAA gets dynamic attrs
00:03:27: PPPATM: ATM1/0.10 0/101 [2], Event = AAA gets dynamic attrs
00:03:27: PPPATM: ATM1/0.10 0/101 [2], Event = PPP Msg Received = 5
00:03:27: PPPATM: ATM1/0.10 0/101 [2], Event = Set Pkts to SSS
00:03:27: PPPATM: ATM1/0.10 0/101 [2], State = FORWARDED
Table 250 describes the significant fields shown in the display.

Table 250 debug pppatm Field Descriptions

Field

Description

Event

Reports PPPoA events for use by Cisco engineering technical assistance personnel.

State

Reports PPPoA states for use by Cisco engineering technical assistance personnel.

Related Commands

Command

Description

atm pppatm passive

Places an ATM subinterface into passive mode.

show pppatm summary

Displays PPPoA session counts.

debug ppp bap

To display general Bandwidth Allocation Control Protocol (BACP) transactions, use the debug ppp bap command in privileged EXEC mode. To disable debugging output, use the no form of this command.

debug ppp bap [error | event | negotiation]
no debug ppp bap [error | event | negotiation]
Syntax Description

error

(Optional) Displays local errors.

event

(Optional) Displays information about protocol actions and transitions between action states (pending, waiting, idle) on the link.

negotiation

(Optional) Displays successive steps in negotiations between peers.

Command Modes

Privileged EXEC

Usage Guidelines

Do not use this command when memory is scarce or in very high traffic situations.

Examples

The following types of events generate the debugging messages displayed in the figures in this section:

•A dial attempt failed.

•A BACP group was created.

•A BACP group was removed.

•The precedence of the group changed.

•Attempting to dial a number.

•Received a BACP message.

•Discarding a BACP message.

•Received an unknown code.

•Cannot find the appropriate BACP group on input.

•Displaying the response type.

•Incomplete mandatory options notification.

•Invalid outgoing message type.

•Unable to build an output message.

•Sending a BACP message.

•Details about the sent message (type of message, its identifier, the virtual access interface that sent it).

The following is sample output from the debug ppp bap command:
Router# debug ppp bap
BAP Virtual-Access1: group "laudrup" (2) (multilink) without precedence created
BAP laudrup: sending CallReq, id 2, len 38 on BRI3:1 to remote
BAP Virtual-Access1: received CallRsp, id 2, len 13
BAP laudrup: CallRsp, id 2, ACK
BAP laudrup: attempt1 to dial 19995776677 on BRI3
 ---> reason BAP - Multilink bundle overloaded
BAP laudrup: sending StatusInd, id 2, len 44 on Virtual-Access1 to remote
BAP Virtual-Access1: received StatusRsp, id 2, len 1
BAP laudrup: StatusRsp, id 2, ACK
Table 251 describes the significant fields shown in the display.

Table 251 debug ppp bap Field Descriptions

Field

Description

BAP Virtual-Access1:

Identifier of the virtual access interface in use.

group "laudrup"

Name of the BACP group.

sending CallReq

Action initiated; in this case, sending a call request.

on BRI3:1 to remote

Physical interface being used.

BAP laudrup: attempt1 to dial 19995776677 on BRI3

---> reason BAP - Multilink bundle overloaded

Call initiated, number being dialed, and physical interface being used.

Reason for initiating the BACP call.

BAP laudrup: sending StatusInd, id 2, len 44 on Virtual-Access1 to remote

Details about the sent message: It was a status indication message, had identifier 2, had a BACP datagram length 44, and was sent on virtual access interface 1. You can display information about the virtual access interface by using the show interfaces virtual-access EXEC command. (The length shown at the end of each negotiated option includes the 2-byte type and length header.)

The debug ppp bap event command might show state transitions and protocol actions, in addition to the basic debug ppp bap command.

The following is sample output from the debug ppp bap event command:
Router# debug ppp bap event
BAP laudrup: Idle --> AddWait
BAP laudrup: AddWait --> AddPending
BAP laudrup: AddPending --> Idle
The following is sample output from the debug ppp bap event command:
Router# debug ppp bap event
Peer does not support a message type
No response to a particular request
No response to all request retransmissions
Not configured to initiate link addition
Expected action by peer has not occurred
Exceeded number of retries
No links available to call out
Unable to provide phone numbers for callback
Maximum number of links in the group
Minimum number of links in the group
Unable to process link addition at present
Unable to process link removal at present
Not configured/unable to initiate link removal
Link addition completed notification
Link addition failed notification
Determination of location of the group config
Link with specified discriminator not in group
Link removal failed
Call failure with status
Failed to dial specified number
Discarding retransmission
Unable to find received identifier
Received StatusInd when no call pending
Discarding message with no phone delta
Unable to send message in particular state
Received a zero identifier
Request has precedence
The error messages displayed might be added to the basic output when the debug ppp bap error command is used. Because the errors are very rare, you might never see these messages.
Router# debug ppp bap error
Unable to find appropriate request for received response
Invalid message type of queue
Received request is not part of the group
Add link attempt failed to locate group
Remove link attempt failed to locate group
Unable to inform peer of link addition
Changing of precedence cannot locate group
Received short header/illegal length/short packet
Invalid configuration information length
Unable to NAK incomplete options
Unable to determine current number of links
No interface list to dial on
Attempt to send invalid data
Local link discriminator is not in group
Received response type is incorrect for identifier
The messages displayed might be added to the basic output when the debug ppp bap negotiation command is used:
Router# debug ppp bap negotiation
BAP laudrup: adding link speed 64 kbps for type 0x1 len 5
BAP laudrup: adding reason "User initiated addition", len 25
BAP laudrup: CallRsp, id 4, ACK
BAP laudrup: link speed 64 kbps for types 0x1, len 5 (ACK)
BAP laudrup: phone number "1: 0 2: ", len 7 (ACK)
BAP laudrup: adding call status 0, action 0 len 4
BAP laudrup: adding 1 phone numbers "1: 0 2: " len 7
BAP laudrup: adding reason "Successfully added link", len 25
BAP laudrup: StatusRsp, id 4, ACK
Additional negotiation messages might also be displayed for the following:
Received BAP message
Sending message
Decode individual options for send/receive
Notification of invalid options
The following shows additional reasons for a particular BAP action that might be displayed in an "adding reason" line of the debug ppp bap negotiation command output:
"Outgoing add request has precedence"
"Outgoing remove request has precedence"
"Unable to change request precedence"
"Unable to determine valid phone delta"
"Attempting to add link"
"Link addition is pending"
"Attempting to remove link"
"Link removal is pending"
"Precedence of peer marked CallReq for no action"
"Callback request rejected due to configuration"
"Call request rejected due to configuration"
"No links of specified type(s) available"
"Drop request disallowed due to configuration"
"Discriminator is invalid"
"No response to call requests"
"Successfully added link"
"Attempt to dial destination failed"
"No interfaces present to dial out"
"No dial string present to dial out"
"Mandatory options incomplete"
"Load has not exceeded threshold"
"Load is above threshold"
"Currently attempting to dial destination"
"No response to CallReq from race condition"
Table 252 describes the reasons for a BACP Negotiation Action.

Table 252 Explanation of Reasons for BACP Negotiation Action

Reason

Explanation

"Outgoing add request has precedence"

Received a CallRequest or CallbackRequest while we were waiting on a CallResponse or CallbackResponse to a sent request. We are the favored peer from the initial BACP negotiation, so we are issuing a NAK to our peer request.

"Outgoing remove request has precedence"

Received a LinkDropQueryRequest while waiting on a LinkDropQueryResponse to a sent request. We are the favored peer from the initial BACP negotiation, therefore we are issuing a NAK to our peer request.

"Unable to change request precedence"

Received a CallRequest, CallbackRequest, or LinkDropQueryRequest while waiting on a LinkDropQueryResponse to a sent request. Our peer is deemed to be the favored peer from the initial BACP negotiation and we were unable to change the status of our outgoing request in response to the favored request, so we are issuing a NAK. (This is an internal error and should never be seen.)

"Unable to determine valid phone delta"

Received a CallRequest from our peer but are unable to provide the required phone delta for the response, so we are issuing a NAK. (This is an internal error and should never be seen.)

"Attempting to add link"

Received a LinkDropQueryRequest while attempting to add a link; a NAK is issued.

"Link addition is pending"

Received a LinkDropQueryRequest, CallRequest, or CallbackRequest while attempting to add a link as the result of a previous operation; a NAK is issued in the response.

"Attempting to remove link"

Received a CallRequest or CallbackRequest while attempting to remove a link; a NAK is issued.

"Link removal is pending"

Received a CallRequest, CallbackRequest, or LinkDropQueryRequest while attempting to remove a link as the result of a previous operation; a NAK is issued in the response.

"Precedence of peer marked CallReq for no action"

Received an ACK to a previously unfavored CallRequest; we are issuing a CallStatusIndication to inform our peer that there will be no further action on our part as per this response.

"Callback request rejected due to configuration"

Received a CallbackRequest but we are configured not to accept them; a REJect is issued to our peer.

"Call request rejected due to configuration"

Received a CallRequest but we are configured not to accept them; a REJect is issued to our peer.

"No links of specified type(s) available"

We received a CallRequest but no links of the specified type and speed are available; a NAK is issued.

"Drop request disallowed due to configuration"

Received a LinkDropQueryRequest but we are configured not to accept them; a NAK is issued to our peer.

"Discriminator is invalid"

Received a LinkDropQueryRequest but the local link discriminator is not contained within the bundle; a NAK is issued.

"No response to call requests"

After no response to our CallRequest message, a CallStatusIndication is sent to the peer informing that no more action will be taken on behalf of this operation.

"Successfully added link"

Sent as part of the CallStatusIndication informing our peer that we successfully completed the addition of a link to the bundle as the result of the transmission of a CallRequest or the reception of a CallbackRequest.

"Attempt to dial destination failed"

Sent as part of the CallStatusIndication informing our peer that we failed in an attempt to add a link to the bundle as the result of the transmission of a CallRequest or the reception of a CallbackRequest. The retry field with the CallStatusIndication informs the peer of our intentions.

"No interfaces present to dial out"

There are no available interfaces to dial out on to attempt to add a link to the bundle, and we will not retry the dial attempt.

"No dial string present to dial out"

We do not have a dial string to dial out with to attempt to add a link to the bundle, and we are not going to retry the dial attempt. (This is an internal error and should never be seen.)

"Mandatory options incomplete"

Received a CallRequest, CallbackRequest, LinkDropQueryRequest, or CallStatusIndication and the mandatory options are not present, so a NAK is issued in the response. (A CallStatusResponse is an ACK, however).

"Load has not exceeded threshold"

Received a CallRequest or CallbackRequest but we are issuing a NAK in the response. We are monitoring the load of the bundle, and so we determine when links should be added to the bundle.

"Load is above threshold"

Received a LinkDropQueryRequest but we are issuing a NAK in the response. We are monitoring the load of the bundle, and so we determine when links should be removed from the bundle.

"Currently attempting to dial destination"

Received a CallbackRequest which is a retransmission of one that we previously ACK'd and are dialing the number suggested in the request. We are issuing an ACK because we did so previously, even though our peer never saw the previous response.

"No response to CallReq from race condition"

We issued a CallRequest but failed to receive a response, and we are issuing a CallStatusIndication to inform our peer of our intention not to proceed with the operation.

debug ppp multilink events

To display information about events affecting multilink groups established for Bandwidth Allocation Control Protocol (BACP), use the debug ppp multilink events command in privileged EXEC mode. To disable debugging output, use the no form of this command.

debug ppp multilink events
no debug ppp multilink events
Syntax Description

This command has no arguments or keywords.

Command Modes

Privileged EXEC

Usage Guidelines

Caution Do not use this command when memory is scarce or in very high traffic situations.

Examples

The following is sample output from the debug ppp multilink events command:
Router# debug ppp multilink events
MLP laudrup: established BAP group 4 on Virtual-Access1, physical BRI3:1
MLP laudrup: removed BAP group 4
Other event messages include the following:
Unable to find bundle for BAP group identifier
Unable to find physical interface to start BAP
Unable to create BAP group
Attempt to start BACP when inactive or running
Attempt to start BACP on non-MLP interface
Link protocol has gone down, removing BAP group
Link protocol has gone down, BAP not running or present
Table 253 describes the significant fields shown in the display.

Table 253 debug ppp multilink events Field Descriptions

Field

Description

MLP laudrup

Name of the multilink group.

established BAP group 4

Internal identifier. The same identifiers are used in the show ppp bap group command output.

Virtual-Access1

Dynamic access interface number.

physical BRI3:1

Bundle was established from a call on this interface.

removed BAP group 4

When the bundle is removed, the associated BACP group (with its ID) is also removed.

debug ppp multilink fragments

To display information about individual multilink fragments and important multilink events, use the debug ppp multilink fragments command in privileged EXEC mode. To disable debugging output, use the no form of this command.

debug ppp multilink fragments
no debug ppp multilink fragments
Syntax Description

This command has no arguments or keywords.

Command Modes

Privileged EXEC

Usage Guidelines

Caution The debug ppp multilink fragments command has some memory overhead and should not be used when memory is scarce or in very high traffic situations.

Examples

The following is sample output from the debug ppp multilink fragments command when used with the ping EXEC command. The debug output indicates that a multilink PPP packet on interface BRI 0 (on the B channel) is an input (I) or output (O) packet. The output also identifies the sequence number of the packet and the size of the fragment.
Router# debug ppp multilink fragments 
Router# ping 7.1.1.7
Type escape sequence to abort.
Sending 5, 100-byte ICMP Echos to 7.1.1.7, timeout is 2 seconds:
!!!!!
Success rate is 100 percent (5/5), round-trip min/avg/max = 32/34/36 ms
Router#
2:00:28: MLP BRI0: B-Channel 1: O seq 80000000: size 58
2:00:28: MLP BRI0: B-Channel 2: O seq 40000001: size 59
2:00:28: MLP BRI0: B-Channel 2: I seq 40000001: size 59
2:00:28: MLP BRI0: B-Channel 1: I seq 80000000: size 58
2:00:28: MLP BRI0: B-Channel 1: O seq 80000002: size 58
2:00:28: MLP BRI0: B-Channel 2: O seq 40000003: size 59
2:00:28: MLP BRI0: B-Channel 2: I seq 40000003: size 59
2:00:28: MLP BRI0: B-Channel 1: I seq 80000002: size 58
2:00:28: MLP BRI0: B-Channel 1: O seq 80000004: size 58
2:00:28: MLP BRI0: B-Channel 2: O seq 40000005: size 59
2:00:28: MLP BRI0: B-Channel 2: I seq 40000005: size 59
2:00:28: MLP BRI0: B-Channel 1: I seq 80000004: size 58
2:00:28: MLP BRI0: B-Channel 1: O seq 80000006: size 58
2:00:28: MLP BRI0: B-Channel 2: O seq 40000007: size 59
2:00:28: MLP BRI0: B-Channel 2: I seq 40000007: size 59
2:00:28: MLP BRI0: B-Channel 1: I seq 80000006: size 58
2:00:28: MLP BRI0: B-Channel 1: O seq 80000008: size 58
2:00:28: MLP BRI0: B-Channel 2: O seq 40000009: size 59
2:00:28: MLP BRI0: B-Channel 2: I seq 40000009: size 59
2:00:28: MLP BRI0: B-Channel 1: I seq 80000008: size 58
debug ppp multilink negotiation

Note Effective with Release 11.3, the debug ppp multilink negotiation command is not available in Cisco IOS software.

To display information about events affecting multilink groups established controlled by Bandwidth Allocation Control Protocol (BACP), use the debug ppp multilink negotiation command in privileged EXEC mode. To disable debugging output, use the no form of this command.

debug ppp multilink negotiation
no debug ppp multilink negotiation
Syntax Description

This command has no arguments or keywords.

Command Modes

Privileged EXEC

Command History

Release

Modification

11.3

This command was removed and is not available in Cisco IOS software.

Usage Guidelines

Caution Do not use this command when memory is scarce or in very high traffic situations.

Examples

The following sample output shows Link Control Protocol (LCP) and Network Control Program (NCP) messages that might appear in debug ppp multilink negotiation command. These messages show information about PPP negotiations between the multilink peers.
Router# debug ppp multilink negotiation
ppp: sending CONFREQ, type = 23 (CI_LINK_DISCRIMINATOR), value = 0xF
PPP BRI3:1: received config for type = 23 (LINK_DISCRIMINATOR) value = 0xA acked
Router# debug ppp multilink negotiation
ppp: sending CONFREQ, type = 1 (CI_FAVORED_PEER), value = 0x647BD090
PPP Virtual-Access1: received CONFREQ, type 1, value = 0x382BBF5 (ACK)
PPP Virtual-Access1: BACP returning CONFACK
ppp: config ACK received, type = 1 (CI_FAVORED_PEER), value = 0x647BD090
PPP Virtual-Access1: BACP up 
Table 254 describes the significant fields shown in the display.

Table 254 debug ppp multilink negotiation Field Descriptions

Field

Description

sending CONFREQ, type = 23 (CI_LINK_DISCRIMINATOR), value = 0xF

Sending a configuration request and the value of the link discriminator. Each peer assigns a discriminator value to identify a specific link. The values are significant to each peer individually but do not have to be shared.

PPP BRI3:1:

Physical interface being used.

CI_FAVORED_PEER

When the PPP NCP negotiation occurs over the first link in a bundle, the BACP peers use a Magic Number akin to that used by LCP to determine which peer should be favored when both implementations send a request at the same time. The peer that negotiated the higher number is deemed to be favored. That peer should issue a negative acknowledgment to its unfavored peer, which in turn should issue a positive acknowledgment, if applicable according to other link considerations.

PPP Virtual-Access1: BACP returning CONFACK

Returning acknowledgment that BACP is configured.

PPP Virtual-Access1: BACP up

Indicating that the BACP NCP is open.

debug pppoe

To display debugging information for PPP over Ethernet (PPPoE) sessions, use the debug pppoe command in privileged EXEC mode. To disable debugging output, use the no form of this command.

debug pppoe {data | errors | events | packets} [rmac remote-mac-address | interface type number [vc {[vpi/]vci | vc-name}] [vlan vlan-id]]
no debug pppoe {data | errors | events | packets} [rmac remote-mac-address | interface type number [vc {[vpi/]vci | vc-name}] [vlan vlan-id]]
Syntax Description

data

Displays data packets of PPPoE sessions.

errors

Displays PPPoE protocol errors that prevent a session from being established, or displays errors that cause an established session to be closed.

events

Displays PPPoE protocol messages about events that are part of normal session establishment or shutdown.

packets

Displays each PPPoE protocol packet that is exchanged.

rmac remote-mac-address

(Optional) Remote MAC address. Debugging information for PPPoE sessions sourced from this address will be displayed.

interface type number

(Optional) Interface for which PPPoE session debugging information will be displayed.

vc

(Optional) Displays debugging information for PPPoE sessions for a specific permanent virtual circuit (PVC).

vpi/

(Optional) ATM network virtual path identifier (VPI) for the PVC. In the absence of the slash (/) and a vpi value, the vpi value defaults to 0.

vci

(Optional) ATM network virtual channel identifier (VCI) for the PVC.

vc-name

(Optional) Name of the PVC.

vlan vlan-id

(Optional) IEEE 802.1Q VLAN identifier.

Command Modes

Privileged EXEC

Command History

Release

Modification

12.2(13)T

This command was introduced. This command replaces the debug vpdn pppoe-data, debug vpdn pppoe-error, debug vpdn pppoe-events, and debug vpdn pppoe-packet commands available in previous Cisco IOS releases.

12.2(15)T

This command was modified to display debugging information on a per-MAC address, per-interface, and per-VC basis.

12.3(2)T

The vlan vlan-id keyword and argument were added.

12.3(7)XI3

This command was integrated into Cisco IOS Release 12.3(7)XI3.

Examples

The following examples show sample output from the debug pppoe command:
Router# debug pppoe events interface atm1/0.10 vc 101 
PPPoE protocol events debugging is on 
Router# 
00:41:55:PPPoE 0:I PADI  R:00b0.c2e9.c470 L:ffff.ffff.ffff 0/101 ATM1/0.10 
00:41:55:PPPoE 0:O PADO, R:00b0.c2e9.c470 L:0001.c9f0.0c1c 0/101 ATM1/0.10 
00:41:55:PPPoE 0:I PADR  R:00b0.c2e9.c470 L:0001.c9f0.0c1c 0/101 ATM1/0.10 
00:41:55:PPPoE :encap string prepared 
00:41:55:[3]PPPoE 3:Access IE handle allocated 
00:41:55:[3]PPPoE 3:pppoe SSS switch updated 
00:41:55:[3]PPPoE 3:AAA unique ID allocated 
00:41:55:[3]PPPoE 3:No AAA accounting method list 
00:41:55:[3]PPPoE 3:Service request sent to SSS 
00:41:55:[3]PPPoE 3:Created  R:0001.c9f0.0c1c L:00b0.c2e9.c470 0/101 ATM1/0.10 
00:41:55:[3]PPPoE 3:State REQ_NASPORT    Event MORE_KEYS 
00:41:55:[3]PPPoE 3:O PADS  R:00b0.c2e9.c470 L:0001.c9f0.0c1c 0/101 ATM1/0.10 
00:41:55:[3]PPPoE 3:State START_PPP    Event DYN_BIND 
00:41:55:[3]PPPoE 3:data path set to PPP 
00:41:57:[3]PPPoE 3:State LCP_NEGO    Event PPP_LOCAL 
00:41:57:PPPoE 3/SB:Sent vtemplate request on base Vi2 
00:41:57:[3]PPPoE 3:State CREATE_VA    Event VA_RESP 
00:41:57:[3]PPPoE 3:Vi2.1 interface obtained 
00:41:57:[3]PPPoE 3:State PTA_BIND    Event STAT_BIND 
00:41:57:[3]PPPoE 3:data path set to Virtual Acess 
00:41:57:[3]PPPoE 3:Connected PTA 
Router# debug pppoe errors interface atm1/0.10
PPPoE protocol errors debugging is on 
Router# 
00:44:30:PPPoE 0:Max session count(1) on mac(00b0.c2e9.c470) reached. 
00:44:30:PPPoE 0:Over limit or Resource low. R:00b0.c2e9.c470 L:ffff.ffff.ffff 0/101 
ATM1/0.10 
Table 255 describes significant fields shown in the displays.

Table 255 debug pppoe Field Descriptions

Field

Description

PPPoE

PPPoE debug message header.

0:

PPPoE session ID.

I PADI

Incoming PPPoE Active Discovery Initiation packet.

R:

Remote MAC address.

L:

Local MAC address.

0/101

Virtual path identifier (VPI)/virtual channel identifier (VCI) of the PVC.

ATM1/0.10

Interface type and number.

O PADO

Outgoing PPPoE Active Discovery Offer packet.

I PADR

Incoming PPPoE Active Discovery Request packet.

[3]

Unique user session ID. The same ID is used for identifying sessions across different applications such as PPPoE, PPP, Layer 2 Tunneling Protocol (L2TP), and Subscriber Service Switch (SSS). The same session ID appears in the output for the show pppoe session, show sss session, and show vpdn session commands.

PPPoE 3

PPPoE session ID.

Created

PPPoE session is created.

O PADS

Outgoing PPPoE Active Discovery Session-confirmation packet.

Connected PTA

PPPoE session is established.

Max session count(1) on mac(00b0.c2e9.c470) reached

PPPoE session is rejected because of per-MAC session limit.

Related Commands

Command

Description

encapsulation aal5autoppp virtual-template

Enables PPPoA/PPPoE autosense.

pppoe enable

Enables PPPoE sessions on an Ethernet interface or subinterface.

protocol pppoe (ATM VC)

Enables PPPoE sessions to be established on PVCs.

show pppoe session

Displays information about active PPPoE sessions.

show sss session

Displays Subscriber Service Switch session status.

show vpdn session

Displays session information about L2TP, L2F protocol, and PPPoE tunnels in a VPDN.

debug priority

To display priority queueing output, use the debug priority command in privileged EXEC mode. To disable debugging output, use the no form of this command.

debug priority
no debug priority
Syntax Description

This command has no arguments or keywords.

Command Modes

Privileged EXEC

Examples

The following example shows how to enable priority queueing output:
Router# debug priority
Priority output queueing debugging is on
The following is sample output from the debug priority command when the Frame Relay PVC Interface Priority Queueing (FR PIPQ) feature is configured on serial interface 0:
Router# debug priority
00:49:05:PQ:Serial0 dlci 100 -> high
00:49:05:PQ:Serial0 output (Pk size/Q 24/0)
00:49:05:PQ:Serial0 dlci 100 -> high
00:49:05:PQ:Serial0 output (Pk size/Q 24/0)
00:49:05:PQ:Serial0 dlci 100 -> high
00:49:05:PQ:Serial0 output (Pk size/Q 24/0)
00:49:05:PQ:Serial0 dlci 200 -> medium
00:49:05:PQ:Serial0 output (Pk size/Q 24/1)
00:49:05:PQ:Serial0 dlci 300 -> normal
00:49:05:PQ:Serial0 output (Pk size/Q 24/2)
00:49:05:PQ:Serial0 dlci 400 -> low
00:49:05:PQ:Serial0 output (Pk size/Q 24/3)
Related Commands

Command

Description

debug custom-queue

Displays custom queueing output.

debug proxy h323 statistics

To enable proxy RTP statistics, use the debug proxy h323 statistics command in privileged EXEC mode. To disable debugging output, use the no form of this command.

debug proxy h323 statistics
no debug proxy h323 statistics
Syntax Description

This command has no arguments or keywords.

Command Modes

Privileged EXEC

Command History

Release

Modification

11.3(2)NA

This command was introduced.

Usage Guidelines

Enter the show proxy h323 detail-call EXEC command to see the statistics.

debug pvcd

To display the permanent virtual circuit (PVC) Discovery events and Interim Local Management Interface (ILMI) MIB traffic used when discovering PVCs, use the debug pvcd command in privileged EXEC mode. To disable debugging output, use the no form of this command.

debug pvcd
no debug pvcd
Syntax Description

This command has no arguments or keywords.

Command Modes

Privileged EXEC

Usage Guidelines

This command is primarily used by Cisco technical support representatives.

Examples

The following is sample output from the debug pvcd command:
Router# debug pvcd
PVCD: PVCD enabled w/ Subif
PVCD(2/0): clearing event queue
PVCD: 2/0 Forgetting discovered PVCs...
PVCD: Removing all dynamic PVCs on 2/0 
PVCD: Restoring MIXED PVCs w/ default parms on 2/0
PVCD: Marking static PVCs as UNKNWN on 2/0
PVCD: Marking static PVC 0/50 as UNKNWN on 2/0 ...
PVCD: Trying to discover PVCs on 2/0...
PVCD: pvcd_discoverPVCs
PVCD: pvcd_ping
PVCD: fPortEntry.5.0 = 2
PVCD: pvcd_getPeerVccTableSize
PVCD: fLayerEntry.5.0 = 13
PVCD:end allocating VccTable size 13
PVCD:  pvcd_getPeerVccTable
PVCD:******* 2/0: getNext on fVccEntry = NULL TYPE/VALUE numFileds = 19 numVccs = 13
PVCD: Creating Dynamic PVC 0/33 on 2/0
PVCD(2/0): Before _update_inheritance() and _create_pvc() VC 0/33: DYNAMIC 
PVCD: After _create_pvc() VC 0/33: DYNAMIC0/33 on 2/0 :  UBR PCR = -1
PVCD: Creating Dynamic PVC 0/34 on 2/0
PVCD(2/0): Before _update_inheritance() and _create_pvc() VC 0/34: DYNAMIC
PVCD: After _create_pvc() VC 0/34: DYNAMIC0/34 on 2/0 :  UBR PCR -1
PVCD: Creating Dynamic PVC 0/44 on 2/0
PVCD(2/0): Before _update_inheritance() and _create_pvc() VC 0/44: DYNAMIC 
PVCD: After _create_pvc() VC 0/44: DYNAMIC0/44 on 2/0 :  UBR PCR = -1
PVCD: PVC 0/50 with INHERITED_QOSTYPE
PVCD: _oi_state_change ( 0/50, 1 = ILMI_VC_UP )
PVCD: Creating Dynamic PVC 0/60 on 2/0
PVCD(2/0): Before _update_inheritance() and _create_pvc() VC 0/60: DYNAMIC
PVCD: After _create_pvc() VC 0/60: DYNAMIC0/60 on 2/0 :  UBR PCR = -1
PVCD: Creating Dynamic PVC 0/80 on 2/0
PVCD(2/0): Before _update_inheritance() and _create_pvc() VC 0/80: DYNAMIC
PVCD: After _create_pvc() VC 0/80: DYNAMIC0/80 on 2/0 :  UBR PCR = -1
PVCD: Creating Dynamic PVC 0/99 on 2/0
debug pxf tbridge

To enable debugging of parallel express forwarding (PXF) transparent bridging, use the debug pxf tbridge command in privileged EXEC mode. To disable the debugging, use the no form of this command.

debug pxf tbridge
no debug pxf tbridge
Syntax Description

This command has no arguments or keywords.

Command Modes

Privileged EXEC

Command History

Release

Modification

12.3(14)T

This command was introduced.

Examples

The following example shows that BVI100 has been removed from the Software Mac-address Filter (SMF) table:
Router# debug pxf tbridge 
*Feb  8 18:39:04.710: rpmxf_tbridge_add_remove_bvi_from_smf: Deleting BVI entry 100 from 
SMF table.
*Feb  8 18:39:04.710: rpmxf_tbridge_add_remove_bvi_from_smf: BVI 100 ICM programming
*Feb  8 18:39:04.710: rpmxf_tbridge_add_remove_bvi_from_smf: Successfully removed SMF 
entry for bvi 100
*Feb  8 18:39:04.710: rpmxf_tbridge_add_remove_bvi_from_smf: Deleting BVI entry 100 from 
SMF table.
*Feb  8 18:39:04.710: rpmxf_tbridge_add_remove_bvi_from_smf: BVI 100 ICM programming
*Feb  8 18:39:04.710: rpmxf_tbridge_add_remove_bvi_from_smf: Successfully removed SMF 
entry for bvi 100
*Feb  8 18:39:05.178: %SYS-5-CONFIG_I: Configured from console by vty0
(CROI_MASTER_000A004B)
*Feb  8 18:39:06.710: %LINK-5-CHANGED: Interface BVI100, changed state to administratively 
down
*Feb  8 18:39:07.710:%LINEPROTO-5-UPDOWN: Line protocol on Interface BVI100, changed state 
to down
The following example shows that BVI is configured and that the SMF entry has been updated:
Router# debug pxf tbridge 
*Feb  8 18:39:16.398: 
Note: A random mac address of 0000.0ceb.c0f8 has been chosen for BVI in bridge group  100 
since there is no mac address associated with the selected interface.
*Feb  8 18:39:16.398: Ensure that this address is unique.
*Feb  8 18:39:16.398: rpmxf_tbridge_smf_update: SMF update for Switch1.1: BVI 100 Mac 
Address 0000.0ceb.c0f8
*Feb  8 18:39:16.398: rpmxf_tbridge_smf_update: BVI 100 ICM programming
*Feb  8 18:39:16.398: rpmxf_tbridge_smf_update: Successfully updated SMF entry for bvi 100
*Feb  8 18:39:16.398: rpmxf_tbridge_smf_update: SMF update for Switch1.1:
BVI 100 Mac Address 0000.0ceb.c0f8
*Feb  8 18:39:16.398: rpmxf_tbridge_smf_update: BVI 100 ICM programming
*Feb  8 18:39:16.398: rpmxf_tbridge_smf_update: Successfully updated SMF entry for bvi 100
*Feb  8 18:39:16.886: %SYS-5-CONFIG_I: Configured from console by vty0
(CROI_MASTER_000A004B)
*Feb  8 18:39:18.394: %LINK-3-UPDOWN: Interface BVI100, changed state to up
*Feb  8 18:39:19.394: %LINEPROTO-5-UPDOWN: Line protocol on Interface BVI100, changed 
state to up
Related Commands

Command

Description

show pxf cpu statistics

Displays PXF CPU statistics for a configured router.

show pxf cpu subblock

Displays PXF CPU subblocks for a bridged subinterface.

show pxf cpu tbridge

Displays PXF CPU statistics in a CPU for transparent bridging.

debug qllc error

To display quality link line control (QLLC) errors, use the debug qllc error command in privileged EXEC mode. To disable debugging output, use the no form of this command.

debug qllc error
no debug qllc error
Syntax Description

This command has no arguments or keywords.

Command Modes

Privileged EXEC

Usage Guidelines

This command helps you track down errors in the QLLC interactions with X.25 networks. Use the debug qllc error command in conjunction with the debug x25 all command to see the connection. The data shown by this command only flows through the router on the X.25 connection. Some forms of this command can generate a substantial amount of output and network traffic.

Examples

The following is sample output from the debug qllc error command:
Router# debug qllc error 
%QLLC-3-GENERRMSG: qllc_close - bad qllc pointer Caller 00407116 Caller 00400BD2 
QLLC 4000.1111.0002: NO X.25 connection. Discarding XID and calling out 
The following line indicates that the QLLC connection was closed:
%QLLC-3-GENERRMSG: qllc_close - bad qllc pointer Caller 00407116 Caller 00400BD2 
The following line shows the virtual MAC address of the failed connection:
QLLC 4000.1111.0002: NO X.25 connection. Discarding XID and calling out 
debug qllc event

To enable debugging of quality link line control (QLLC) events, use the debug qllc event command in privileged EXEC mode. To disable debugging output, use the no form of this command.

debug qllc event
no debug qllc event
Syntax Description

This command has no arguments or keywords.

Command Modes

Privileged EXEC

Usage Guidelines

Use the debug qllc event command to display primitives that might affect the state of a QLLC connection. An example of these events is the allocation of a QLLC structure for a logical channel indicator when an X.25 call has been accepted with the QLLC call user data. Other examples are the receipt and transmission of LAN explorer and exchange identification (XID) frames.

Examples

The following is sample output from the debug qllc event command:
Router# debug qllc event 
QLLC: allocating new qllc lci 9
QLLC: tx POLLING TEST, da 4001.3745.1088, sa 4000.1111.0001
QLLC: rx explorer response, da 4000.1111.0001, sa c001.3745.1088, rif 08B0.1A91.1901.A040
QLLC: gen NULL XID, da c001.3745.1088, sa 4000.1111.0001, rif 0830.1A91.1901.A040, dsap 4, 
ssap 4 
QLLC: rx XID response, da 4000.1111.0001, sa c001.3745.1088, rif 08B0.1A91.1901.A040
The following line indicates that a new QLLC data structure has been allocated:
QLLC: allocating new qllc lci 9
The following lines show transmission and receipt of LAN explorer or test frames:
QLLC: tx POLLING TEST, da 4001.3745.1088, sa 4000.1111.0001
QLLC: rx explorer response, da 4000.1111.0001, sa c001.3745.1088, rif 08B0.1A91.1901.A040
The following lines show XID events:
QLLC: gen NULL XID, da c001.3745.1088, sa 4000.1111.0001, rif 0830.1A91.1901.A040, dsap 4, 
ssap 4 
QLLC: rx XID response, da 4000.1111.0001, sa c001.3745.1088, rif 08B0.1A91.1901.A040 
debug qllc packet

To display quality link line control (QLLC) events and QLLC data packets, use the debug qllc packet command in privileged EXEC mode. To disable debugging output, use the no form of this command.

debug qllc packet
no debug qllc packet
Syntax Description

This command has no arguments or keywords.

Command Modes

Privileged EXEC

Usage Guidelines

This command helps you to track down errors in the QLLC interactions with X.25 networks. The data shown by this command only flows through the router on the X25 connection. Use the debug qllc packet command in conjunction with the debug x25 all command to see the connection and the data that flows through the router.

Examples

The following is sample output from the debug qllc packet command:
Router# debug qllc packet 
14:38:05: Serial2/5 QLLC I: Data Packet.-RSP    9 bytes. 
14:38:07: Serial2/6 QLLC I: Data Packet.-RSP 112 bytes. 
14:38:07: Serial2/6 QLLC O: Data Packet. 128 bytes. 
14:38:08: Serial2/6 QLLC I: Data Packet.-RSP    9 bytes. 
14:38:08: Serial2/6 QLLC I: Data Packet.-RSP 112 bytes. 
14:38:08: Serial2/6 QLLC O: Data Packet. 128 bytes. 
14:38:08: Serial2/6 QLLC I: Data Packet.-RSP    9 bytes. 
14:38:12: Serial2/5 QLLC I: Data Packet.-RSP 112 bytes. 
14:38:12: Serial2/5 QLLC O: Data Packet. 128 bytes. 
The following lines indicate that a packet was received on the interfaces:
14:38:05: Serial2/5 QLLC I: Data Packet.-RSP    9 bytes. 
14:38:07: Serial2/6 QLLC I: Data Packet.-RSP 112 bytes. 
The following lines show that a packet was sent on the interfaces:
14:38:07: Serial2/6 QLLC O: Data Packet. 128 bytes. 
14:38:12: Serial2/5 QLLC O: Data Packet. 128 bytes. 
debug qllc state

To enable debugging of quality link line control (QLLC) events, use the debug qllc state command in privileged EXEC mode. To disable debugging output, use the no form of this command.

debug qllc state
no debug qllc state
Syntax Description

This command has no arguments or keywords.

Command Modes

Privileged EXEC

Usage Guidelines

Use the debug qllc state command to show when the state of a QLLC connection has changed. The typical QLLC connection goes from states ADM to SETUP to NORMAL. The NORMAL state indicates that a QLLC connection exists and is ready for data transfer.

Examples

The following is sample output from the debug qllc state command:
Router# debug qllc state
Serial2 QLLC O: QSM-CMD
Serial2: X25 O D1 DATA (5) Q 8 lci 9 PS 4 PR 3
QLLC: state ADM -> SETUP
Serial2: X25 I D1 RR (3) 8 lci 9 PR 5
Serial2: X25 I D1 DATA (5) Q 8 lci 9 PS 3 PR 5
Serial2 QLLC I: QUA-RSPQLLC: addr 00, ctl 73
QLLC: qsetupstate: recvd qua rsp
QLLC: state SETUP -> NORMAL
The following line indicates that a QLLC connection attempt is changing state from ADM to SETUP:
QLLC: state ADM -> SETUP
The following line indicates that a QLLC connection attempt is changing state from SETUP to NORMAL:
QLLC: state SETUP -> NORMAL
debug qllc timer

To display quality link line control (QLLC) timer events, use the debug qllc timer command in privileged EXEC mode. To disable debugging output, use the no form of this command.

debug qllc timer
no debug qllc timer
Syntax Description

This command has no arguments or keywords.

Command Modes

Privileged EXEC

Usage Guidelines

The QLLC process periodically cycles and checks status of itself and its partner. If the partner is not found in the desired state, an LAPB primitive command is re-sent until the partner is in the desired state or the timer expires.

Examples

The following is sample output from the debug qllc timer command:
Router# debug qllc timer 
14:27:24: Qllc timer lci 257, state ADM retry count 0 Caller 00407116 Caller 00400BD2
14:27:34: Qllc timer lci 257, state NORMAL retry count 0 
14:27:44: Qllc timer lci 257, state NORMAL retry count 1 
14:27:54: Qllc timer lci 257, state NORMAL retry count 1 
The following line of output shows the state of a QLLC partner on a given X.25 logical channel identifier:
14:27:24: Qllc timer lci 257, state ADM retry count 0 Caller 00407116 Caller 00400BD2
Other messages are informational and appear every ten seconds.

debug qllc x25

To display X.25 packets that affect a quality link line control (QLLC) connection, use the debug qllc x25 command in privileged EXEC mode. To disable debugging output, use the no form of this command.

debug qllc x25
no debug qllc x25
Syntax Description

This command has no arguments or keywords.

Command Modes

Privileged EXEC

Usage Guidelines

This command is helpful to track down errors in the QLLC interactions with X.25 networks. Use the debug qllc x25 command in conjunction with the debug x25 events or debug x25 all commands to see the X.25 events between the router and its partner.

Examples

The following is sample output from the debug qllc x25 command:
Router# debug qllc x25 
15:07:23: QLLC X25 notify lci 257 event 1 
15:07:23: QLLC X25 notify lci 257 event 5 
15:07:34: QLLC X25 notify lci 257 event 3 Caller 00407116 Caller 00400BD2 
15:07:35: QLLC X25 notify lci 257 event 4 
Table 256 describes the significant fields shown in the display.

Table 256 debug qllc x25 Field Descriptions

Field

Description

15:07:23

Displays the time of day.

QLLC X25 notify 257

Indicates that this is a QLLC X25 message.

event <n>

Indicates the type of event, n. Values for n can be as follows:

•1—Circuit is cleared

•2—Circuit has been reset

•3—Circuit is connected

•4—Circuit congestion has cleared

•5—Circuit has been deleted

debug qos ha

To debug Quality of Service (QoS) information on the networking device, use the debug qos ha command in privileged EXEC mode. To disable the display of debugging output, use the no form of this command.

debug qos ha [detail]
no debug qos ha [detail]
Syntax Description

detail

(Optional) (Optional) Displays detailed debug messages related to specified QoS information.

Command Modes

Privileged EXEC

Command History

Release

Modification

12.2(25)S

This command was introduced.

Usage Guidelines

Use to determine that QoS in running properly on your networking device.

Examples

The following example enables QoS debugging:
debug qos ha
debug radius

To display information associated with RADIUS, use the debug radius command in privileged EXEC mode. To disable debugging output, use the no form of this command.

debug radius [brief | hex]
no debug radius [brief | hex]
Syntax Description

brief

(Optional) Displays abbreviated debug output.

hex

(Optional) Displays debugging output in hexadecimal notation.

Defaults

Debugging output in ASCII format is enabled.

Command Modes

Privileged EXEC

Command History

Release

Modification

11.2(1)T

This command was introduced.

12.2(11)T

The brief and hex keywords were added. The default output format became ASCII rather than hexadecimal.

Usage Guidelines

RADIUS is a distributed security system that secures networks against unauthorized access. Cisco supports RADIUS under the authentication, authorization, and accounting (AAA) security system. When RADIUS is used on the router, you can use the debug radius command to display detailed debugging and troubleshooting information in ASCII format. Use the debug radius brief command for abbreviated output displaying client/server interaction and minimum packet information. Use the debug radius hex command to display packet dump information that has not been truncated in hex format.

Examples

The following is sample output from the debug radius command:
Router# debug radius 
Radius protocol debugging is on
Radius packet hex dump debugging is off
Router#
00:02:50: RADIUS: ustruct sharecount=3
00:02:50: Radius: radius_port_info() success=0 radius_nas_port=1
00:02:50: RADIUS: Initial Transmit ISDN 0:D:23 id 0 10.0.0.1:1824, Accounting-Request, len 
358
00:02:50: RADIUS:  NAS-IP-Address      [4]   6   10.0.0.0
00:02:50: RADIUS:  Vendor, Cisco       [26]  19  VT=02 TL=13 ISDN 0:D:23
00:02:50: RADIUS:  NAS-Port-Type       [61]  6   Async
00:02:50: RADIUS:  User-Name           [1]   12  "4085554206"
00:02:50: RADIUS:  Called-Station-Id   [30]  7   "52981"
00:02:50: RADIUS:  Calling-Station-Id  [31]  12  "4085554206"
00:02:50: RADIUS:  Acct-Status-Type    [40]  6   Start
00:02:50: RADIUS:  Service-Type        [6]   6   Login
00:02:50: RADIUS:  Vendor, Cisco       [26]  27  VT=33 TL=21 h323-gw-id=5300_43.
00:02:50: RADIUS:  Vendor, Cisco       [26]  55  VT=01 TL=49 
h323-incoming-conf-id=8F3A3163 B4980003 0 29BD0
00:02:50: RADIUS:  Vendor, Cisco       [26]  31  VT=26 TL=25 h323-call-origin=answer
00:02:50: RADIUS:  Vendor, Cisco       [26]  32  VT=27 TL=26 h323-call-type=Telephony
00:02:50: RADIUS:  Vendor, Cisco       [26]  57  VT=25 TL=51 h323-setup-time=*16:02:48.681 
PST Fri Dec 31 1999
00:02:50: RADIUS:  Vendor, Cisco       [26]  46  VT=24 TL=40 h323-conf-id=8F3A3163 
B4980003 0 29BD0
00:02:50: RADIUS:  Acct-Session-Id     [44]  10  "00000002"
00:02:50: RADIUS:  Delay-Time          [41]  6   0
00:02:51: RADIUS: Received from id 0 1.7.157.1:1824, Accounting-response, len 20
00:02:51: %ISDN-6-CONNECT: Interface Serial0:22 is now connected to 4085274206 
00:03:01: RADIUS: ustruct sharecount=3
00:03:01: Radius: radius_port_info() success=0 radius_nas_port=1
00:03:01: RADIUS: Initial Transmit ISDN 0:D:23 id 1 1.7.157.1:1823, Access-Request, len 
171
00:03:01: RADIUS:  NAS-IP-Address      [4]   6   10.0.0.0
00:03:01: RADIUS:  Vendor, Cisco       [26]  19  VT=02 TL=13 ISDN 0:D:23
00:03:01: RADIUS:  NAS-Port-Type       [61]  6   Async
00:03:01: RADIUS:  User-Name           [1]   8   "123456"
00:03:01: RADIUS:  Vendor, Cisco       [26]  46  VT=24 TL=40 h323-conf-id=8F3A3163 
B4980003 0 29BD0
00:03:01: RADIUS:  Calling-Station-Id  [31]  12  "4085554206"
00:03:01: RADIUS:  User-Password       [2]   18  *
00:03:01: RADIUS:  Vendor, Cisco       [26]  36  VT=01 TL=30 h323-ivr-out=transactionID:0
00:03:01: RADIUS: Received from id 1 1.7.157.1:1823, Access-Accept, len 115
00:03:01: RADIUS:  Service-Type        [6]   6   Login
00:03:01: RADIUS:  Vendor, Cisco       [26]  29  VT=101 TL=23 h323-credit-amount=45
00:03:01: RADIUS:  Vendor, Cisco       [26]  27  VT=102 TL=21 h323-credit-time=33
00:03:01: RADIUS:  Vendor, Cisco       [26]  26  VT=103 TL=20 h323-return-code=0
00:03:01: RADIUS:  Class               [25]  7   6C6F63616C
00:03:01: RADIUS: saved authorization data for user 62321E14 at 6233D258
00:03:13: %ISDN-6-DISCONNECT: Interface Serial0:22  disconnected from 4085274206, call 
lasted 22 seconds
00:03:13: RADIUS: ustruct sharecount=2
00:03:13: Radius: radius_port_info() success=0 radius_nas_port=1
00:03:13: RADIUS: Sent class "local" at 6233D2C4 from user 62321E14
00:03:13: RADIUS: Initial Transmit ISDN 0:D:23 id 2 1.7.157.1:1824, Accounting-Request, 
len 775
00:03:13: RADIUS:  NAS-IP-Address      [4]   6   10.0.0.0
00:03:13: RADIUS:  Vendor, Cisco       [26]  19  VT=02 TL=13 ISDN 0:D:23
00:03:13: RADIUS:  NAS-Port-Type       [61]  6   Async
00:03:13: RADIUS:  User-Name           [1]   8   "123456"
00:03:13: RADIUS:  Called-Station-Id   [30]  7   "52981"
00:03:13: RADIUS:  Calling-Station-Id  [31]  12  "4085274206"
00:03:13: RADIUS:  Acct-Status-Type    [40]  6   Stop
00:03:13: RADIUS:  Class               [25]  7   6C6F63616C
00:03:13: RADIUS:  Undebuggable        [45]  6   00000001
00:03:13: RADIUS:  Service-Type        [6]   6   Login
00:03:13: RADIUS:  Vendor, Cisco       [26]  27  VT=33 TL=21 h323-gw-id=5300_43.
00:03:13: RADIUS:  Vendor, Cisco       [26]  55  VT=01 TL=49 
h323-incoming-conf-id=8F3A3163 B4980003 0 29BD0
00:03:13: RADIUS:  Vendor, Cisco       [26]  31  VT=26 TL=25 h323-call-origin=answer
00:03:13: RADIUS:  Vendor, Cisco       [26]  32  VT=27 TL=26 h323-call-type=Telephony
00:03:13: RADIUS:  Vendor, Cisco       [26]  57  VT=25 TL=51 h323-setup-time=*16:02:48.681 
PST Fri Dec 31 1999
00:03:13: RADIUS:  Vendor, Cisco       [26]  59  VT=28 TL=53 
h323-connect-time=*16:02:48.946 PST Fri Dec 31 1999
00:03:13: RADIUS:  Vendor, Cisco       [26]  62  VT=29 TL=56in=0
00:03:13: RADIUS:  Vendor, Cisco       [26]  23  VT=01 TL=17 pre-bytes-out=0
00:03:13: RADIUS:  Vendor, Cisco       [26]  21  VT=01 TL=15 pre-paks-in=0
00:03:13: RADIUS:  Vendor, Cisco       [26]  22  VT=01 TL=16 pre-paks-out=0
00:03:13: RADIUS:  Vendor, Cisco       [26]  22  VT=01 TL=16 nas-rx-speed=0
00:03:13: RADIUS:  Vendor, Cisco       [26]  22  VT=01 TL=16 nas-tx-speed=0
00:03:13: RADIUS:  Delay-Time          [41]  6   0
00:03:13: RADIUS: Received from id 2 1.7.157.1:1824, Accounting-response, len 20
h323-disconnect-time=*16:03:11.306 PST Fri Dec 31 1999
00:03:13: RADIUS:  Vendor, Cisco       [26]  32  VT=30 TL=26 h323-disconnect-cause=10
00:03:13: RADIUS:  Vendor, Cisco       [26]  28  VT=31 TL=22 h323-voice-quality=0
00:03:13: RADIUS:  Vendor, Cisco       [26]  46  VT=24 TL=40 h323-conf-id=8F3A3163 
B4980003 0 29BD0
00:03:13: RADIUS:  Acct-Session-Id     [44]  10  "00000002"
00:03:13: RADIUS:  Acct-Input-Octets   [42]  6   0
00:03:13: RADIUS:  Acct-Output-Octets  [43]  6   88000
00:03:13: RADIUS:  Acct-Input-Packets  [47]  6   0
00:03:13: RADIUS:  Acct-Output-Packets [48]  6   550
00:03:13: RADIUS:  Acct-Session-Time   [46]  6   22
00:03:13: RADIUS:  Vendor, Cisco       [26]  30  VT=01 TL=24 subscriber=RegularLine
00:03:13: RADIUS:  Vendor, Cisco       [26]  35  VT=01 TL=29 h323-ivr-out=Tariff:Unknown
00:03:13: RADIUS:  Vendor, Cisco       [26]  22  VT=01 TL=16 pre-bytes-
The following is sample output from the debug radius brief command:
Router# debug radius brief
Radius protocol debugging is on
Radius packet hex dump debugging is off
Radius protocol in brief format debugging is on
00:05:21: RADIUS: Initial Transmit ISDN 0:D:23 id 6 10.0.0.1:1824, Accounting-Request, len 
358
00:05:21: %ISDN-6-CONNECT: Interface Serial0:22 is now connected to 4085274206
00:05:26: RADIUS: Retransmit id 6
00:05:31: RADIUS: Tried all servers.
00:05:31: RADIUS: No valid server found. Trying any viable server
00:05:31: RADIUS: Tried all servers.
00:05:31: RADIUS: No response for id 7
00:05:31: RADIUS: Initial Transmit ISDN 0:D:23 id 8 10.0.0.0:1823, Access-Request, len 171
00:05:36: RADIUS: Retransmit id 8
00:05:36: RADIUS: Received from id 8 1.7.157.1:1823, Access-Accept, len 115
00:05:47: %ISDN-6-DISCONNECT: Interface Serial0:22 disconnected from 4085274206, call 
lasted 26 seconds
00:05:47: RADIUS: Initial Transmit ISDN 0:D:23 id 9 10.0.0.1:1824, Accounting-Request, len 
775
00:05:47: RADIUS: Received from id 9 1.7.157.1:1824, Accounting-response, len 20
The following example shows debug radius hex output:
Router# debug radius hex
Radius protocol debugging is on
Radius packet hex dump debugging is on
Router#
17:26:52: RADIUS: ustruct sharecount=3
17:26:52: Radius: radius_port_info() success=0 radius_nas_port=1
17:26:52: RADIUS: Initial Transmit ISDN 0:D:23 id 10 10.0.0.1:1824, Accounting-Request, 
len 361
17:26:52:         Attribute 4 6 01081D03
17:26:52:         Attribute 26 19 00000009020D4953444E20303A443A3233
17:26:52:         Attribute 61 6 00000000
17:26:52:         Attribute 1 12 34303835323734323036
17:26:52:         Attribute 30 7 3532393831
17:26:52:         Attribute 31 12 34303835323734323036
17:26:52:         Attribute 40 6 00000001
17:26:52:         Attribute 6 6 00000001
17:26:52:         Attribute 26 27 000000092115683332332D67772D69643D353330305F34332E
17:26:52:         Attribute 26 57 
000000090133683332332D696E636F6D696E672D636F6E662D69643D3846334133313633204234393830303046
20302033424537314238
17:26:52:         Attribute 26 31 
000000091A19683332332D63616C6C2D6F726967696E3D616E73776572
17:26:52:         Attribute 26 32 
000000091B1A683332332D63616C6C2D747970653D54656C6570686F6E79
17:26:52:         Attribute 26 56 
000000091932683332332D73657475702D74696D653D2A30393A32363A35322E3838302050535420536174204A
616E20312032303030
17:26:52:         Attribute 26 48 
00000009182A683332332D636F6E662D69643D3846334133313633204234393830303046203020334245373142
38
17:26:52:         Attribute 44 10 3030303030303035
17:26:52:         Attribute 41 6 00000000
17:26:52: %ISDN-6-CONNECT: Interface Serial0:22 is now connected to 4085274206
17:26:52: RADIUS: Received from id 10 10.0.0.1:1824, Accounting-response, len 20
17:27:01: RADIUS: ustruct sharecount=3
17:27:01: Radius: radius_port_info() success=0 radius_nas_port=1
17:27:01: RADIUS: Initial Transmit ISDN 0:D:23 id 11 10.0.0.0:1823, Access-Request, len 
173
17:27:01:         Attribute 4 6 01081D03
17:27:01:         Attribute 26 19 00000009020D4953444E20303A443A3233
17:27:01:         Attribute 61 6 00000000
17:27:01:         Attribute 1 8 313233343536
17:27:01:         Attribute 26 48 
00000009182A683332332D636F6E662D69643D3846334133313633204234393830303046203020334245373142
38
17:27:01:         Attribute 31 12 34303835323734323036
17:27:01:         Attribute 2 18 C980D8D0E9A061B3D783C61AA6F27214
17:27:01:         Attribute 26 36 
00000009011E683332332D6976722D6F75743D7472616E73616374696F6E49443A33
17:27:01: RADIUS: Received from id 11 1.7.157.1:1823, Access-Accept, len 115
17:27:01:         Attribute 6 6 00000001
17:27:01:         Attribute 26 29 000000096517683332332D6372656469742D616D6F756E743D3435
17:27:01:         Attribute 26 27 000000096615683332332D6372656469742D74696D653D3333
17:27:01:         Attribute 26 26 000000096714683332332D72657475726E2D636F64653D30
17:27:01:         Attribute 25 7 6C6F63616C
17:27:01: RADIUS: saved authorization data for user 61AA0698 at 6215087C
17:27:09: %ISDN-6-DISCONNECT: Interface Serial0:22  disconnected from 4085554206, call 
lasted 17 seconds
17:27:09: RADIUS: ustruct sharecount=2
17:27:09: Radius: radius_port_info() success=0 radius_nas_port=1
17:27:09: RADIUS: Sent class "local" at 621508E8 from user 61AA0698
17:27:09: RADIUS: Initial Transmit ISDN 0:D:23 id 12 1.7.157.1:1824, Accounting-Request, 
len 776
17:27:09:         Attribute 4 6 01081D03
17:27:09:         Attribute 26 19 00000009020D4953444E20303A443A3233
17:27:09:         Attribute 61 6 00000000
17:27:09:         Attribute 1 8 313233343536
17:27:09:         Attribute 30 7 3532393831
17:27:09:         Attribute 31 12 34303835323734323036
17:27:09:         Attribute 40 6 00000002
17:27:09:         Attribute 25 7 6C6F63616C
17:27:09:         Attribute 45 6 00000001
17:27:09:         Attribute 6 6 00000001
17:27:09:         Attribute 26 27 000000092115683332332D67772D69643D353330305F34332E
17:27:09:         Attribute 26 57 
000000090133683332332D696E636F6D696E672D636F6E662D69643D3846334133313633204234393830303046
20302033424537314238
17:27:09:         Attribute 26 31 
000000091A19683332332D63616C6C2D6F726967696E3D616E73776572
17:27:09:         Attribute 26 32 
000000091B1A683332332D63616C6C2D747970653D54656C6570686F6E79
17:27:09:         Attribute 26 56 
000000091932683332332D73657475702D74696D653D2A30393A32363A35322E3838302050535420536174204A
616E20312032303030
17:27:09:         Attribute 26 58 
000000091C34683332332D636F6E6E6563742D74696D653D2A30393A32363A35322E3930372050535420536174
204A616E20312032303030
17:27:09:         Attribute 26 61 
000000091D37683332332D646973636F6E6E6563742D74696D653D2A30393A32373A31302E3133372050535420
536174204A616E20312032303030
17:27:09:         Attribute 26 32 
000000091E1A683332332D646973636F6E6E6563742D63617573653D3130
17:27:09:         Attribute 26 28 000000091F16683332332D766F6963652D7175616C6974793D30
17:27:09:         Attribute 26 48 
00000009182A683332332D636F6E662D69643D3846334133313633204234393830303046203020334245373142
38
17:27:09:         Attribute 44 10 3030303030303035
17:27:09:         Attribute 42 6 00000000
17:27:09:         Attribute 43 6 00012CA0
17:27:09:         Attribute 47 6 00000000
17:27:09:         Attribute 48 6 000001E1
17:27:09:         Attribute 46 6 00000011
17:27:09:         Attribute 26 30 000000090118737562736372696265723D526567756C61724C696E65
17:27:09:         Attribute 26 35 
00000009011D683332332D6976722D6F75743D5461726966663A556E6B6E6F776E
17:27:09:         Attribute 26 22 0000000901107072652D62797465732D696E3D30
17:27:09:         Attribute 26 23 0000000901117072652D62797465732D6F75743D30
17:27:09:         Attribute 26 21 00000009010F7072652D70616B732D696E3D30
17:27:09:         Attribute 26 22 0000000901107072652D70616B732D6F75743D30
17:27:09:         Attribute 26 22 0000000901106E61732D72782D73706565643D30
17:27:09:         Attribute 26 22 0000000901106E61732D74782D73706565643D30
17:27:09:         Attribute 41 6 00000000
17:27:09: RADIUS: Received from id 12 10.0.0.1:1824, Accounting-response, len 20
Related Commands

Command

Description

debug aaa accounting

Displays information on accountable events as they occur.

debug aaa authentication

Displays information on AAA/TACACS+ authentication.

debug radius accounting

To enable debugging of RADIUS accounting collection, use the debug radius accounting command in privileged EXEC mode. To disable the debugging, use the no form of this command.

debug radius accounting
no debug radius accounting
Syntax Description

This command has no arguments or keywords.

Command Modes

Privileged EXEC

Command History

Release

Modification

12.3(4)T

This command was introduced.

Examples

The following example enables debugging of RADIUS accounting collection:
Router# debug radius accounting
Radius protocol debugging is on
Radius protocol brief debugging is off
Radius protocol verbose debugging is off
Radius packet hex dump debugging is off
Radius packet protocol (authentication) debugging is off
Radius packet protocol (accounting) debugging is on
Radius packet retransmission debugging is off
Radius server fail-over debugging is off
Radius elog debugging is off
Related Commands

Command

Description

debug event-manager

Enables debugging of the event manager.

debug voice statistics

Enables debugging of voice statistics.

debug radius local-server

To control the display of debug messages for the local authentication server, use the debug radius local-server command in privileged EXEC mode.

debug radius local-server {packets | error | client}
Syntax Description

packets

Displays the content of the RADIUS packets that are sent and received.

error

Displays error messages about the local authentication server.

client

Displays error messages about failed client authentications.

Defaults

No default behavior or values

Command Modes

Privileged EXEC

Command History

Release

Modification

12.2(11)JA

This command was introduced on Cisco Aironet Access Point 1200 and Cisco Aironet Access Point 1100.

12.3(11)T

This command was implemented on the following platforms: Cisco 2600XM, Cisco 2691, Cisco 2811, Cisco 2821, Cisco 2851, Cisco 3700, and Cisco 3800 series routers.
Related Commands

Command

Description

clear radius local-server

Clears the statistics display or unblocks a user.

group

Enters user group configuration mode and configures shared setting for a user group.

nas

Adds an access point or router to the list of devices that use the local authentication server.

radius-server host

Specifies the remote RADIUS server host.

radius-server local

Enables the access point or router to be a local authentication server and enters into configuration mode for the authenticator.

reauthentication time

Specifies the time (in seconds) after which access points or wireless-aware routers must reauthenticate the members of a group.

show radius local-server statistics

Displays statistics for a local network access server.

ssid

Specifies up to 20 SSIDs to be used by a user group.

user

Authorizes a user to authenticate using the local authentication server.

vlan

Specifies a VLAN to be used by members of a user group.

debug ras

To display the types and addressing of Registration, Admission and Status (RAS) messages sent and received, use the debug ras command in privileged EXEC mode. To disable debugging output, use the no form of this command.

debug ras
no debug ras
Syntax Description

This command has arguments or keywords.

Defaults

This command is disabled.

Command Modes

Privileged EXEC

Command History

Release

Modification

11.3(6)NA2

This command was introduced.

12.2(2)XB1

This command was implemented on the Cisco AS5850 universal access router.

12.2(11)T

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

Usage Guidelines

Use the debug ras command to display the types and addressing of RAS messages sent and received. The debug output lists the message type using mnemonics defined in International Telecommunications Union-Telecommunication (ITU-T) specification H.225.

Examples

In the following output, gateway GW13.cisco.com sends a RAS registration request (RRQ) message to gatekeeper GK15.cisco.com at IP address 10.9.53.15. GW13.cisco.com then receives a registration confirmation (RCF) message from the gatekeeper. If there is no response, it could mean that the gatekeeper is offline or improperly addressed. If you receive a reject (RRJ) message, it could mean that the gatekeeper is unable to handle another gateway or that the registration information is incorrect.
Router# debug ras 
*Mar 13 19:53:34.231:      RASlib::ras_sendto:msg length 105 from
                            10.9.53.13:8658 to 10.9.53.15:1719
*Mar 13 19:53:34.231:      RASLib::RASSendRRQ:RRQ (seq# 36939) sent
                            to 10.9.53.15
*Mar 13 19:53:34.247:      RASLib::RASRecvData:successfully rcvd
                            message of length 105 from 10.9.53.15:1719
*Mar 13 19:53:34.251:      RASLib::RASRecvData:RCF (seq# 36939) rcvd
                            from [10.9.53.15:1719] on sock [0x6168356C] 
debug redundancy

To enable the display of events for troubleshooting redundant dial shelf controllers (DSCs), use the debug redundancy command in privileged EXEC mode. To disable debugging output, use the no form of this command.

debug redundancy {all | ui | clk | hub}
no debug redundancy {all | ui | clk | hub}
Syntax Description

all

Displays all available information on redundant DSCs, including that specified by the following options in this table.

ui

Displays information on the user interface of the redundant DSCs.

clk

Displays information on the clocks of the redundant DSCs.

hub

Displays information on the BIC hub of the redundant DSCs. The hub is the Fast Ethernet link between the router and the DSC.

Defaults

The command is disabled.

Command Modes

Privileged EXEC

Command History

Release

Modification

11.3(6)AA

This command was introduced.

Usage Guidelines

This command is issued from the router shelf console.

Examples

The output from this command consists of event announcements that can be used by authorized troubleshooting personnel.