Полезная информация

cc/td/doc/product/software/ios120/12supdoc
hometocprevnextglossaryfeedbacksearchhelp
PDF

Table of Contents

debug ppp bap
debug ppp multilink fragments
debug ppp multilink events
debug ppp multilink negotiation
debug qllc error
debug qllc event
debug qllc packet
debug qllc state
debug qllc timer
debug qllc x25
debug radius
debug rif
debug rtr error
debug rtr trace
debug sdlc
debug sdlc local-ack
debug sdlc packet
debug sdllc

debug ppp bap

To display general BACP transactions, use the debug ppp bap EXEC command. The no form of this command disables debugging output.

[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.

Usage Guidelines

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

Sample Displays

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

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 104 describes some basic information about the group, the events, and the sent-message details.


Table 104: 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, 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 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 when the event keyword is used:

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 when the event keyword is used:

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 105 describes the reasons for a BACP Negotiation Action.


Table 105: Explanation of Reasons for BACP Negotiation Action
Reason Explanation

`Outgoing add request has precedence"

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

"Outgoing remove request has precedence"

We received a LinkDropQueryRequest while we are waiting on a LinkDropQueryResponse to a transmitted 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"

We received a CallRequest, CallbackRequest or LinkDropQueryRequest while we were waiting on a LinkDropQueryResponse to a transmitted 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"

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

"Attempting to add link"

We received a LinkDropQueryRequest while we were attempting to add a link; a NAK is issued.

"Link addition is pending"

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

"Attempting to remove link"

We received a CallRequest or CallbackRequest while we were attempting to remove a link; a NAK is issued.

"Link removal is pending"

We received a CallRequest, CallbackRequest or LinkDropQueryRequest while we were 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"

We 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"

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

"Call request rejected due to configuration"

We 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 there are no links of the specified type and speed available; a NAK is issued.

"Drop request disallowed due to configuration"

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

"Discriminator is invalid"

We 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 are not going to 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"

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

"Load has not exceeded threshold"

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

"Load is above threshold"

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

"Currently attempting to dial destination"

We received a CallbackRequest which is a retransmission of one which we previously ACK'd and are currently in the process of 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 fragments

Use the debug ppp multilink fragments EXEC command to display information about individual multilink fragments and important multilink events. The no form of this command disables debugging output.

[no] debug ppp multilink fragments

Usage Guidelines

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.

Sample Display

The following is sample output from the debug ppp multilink fragments command when used with the ping 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 events

To display information about events affecting multilink groups established for BACP, use the debug ppp multilink events EXEC command. The no form of this command disables debugging output.

[no] debug ppp multilink events

Usage Guidelines

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

Sample Display

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 106 describes the significant fields.


Table 106: 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 negotiation

To display information about events affecting multilink groups established controlled by BACP, use the debug ppp multilink negotiation EXEC command. The no form of this command disables debugging output.

[no] debug ppp multilink negotiation

Usage Guidelines

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

Sample Displays

The following sample output shows LCP and 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 107 describes the negotiation actions shown in the output.


Table 107: 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:

The 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 qllc error

Use the debug qllc error EXEC command to display quality link line control (QLLC) errors. The no form of this command disables debugging output.

[no] debug qllc error

Usage Guidelines

This command helps you track down errors in the QLLC interactions with X.25 networks. Use debug qllc error in conjunction with debug x25 all 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 lots of output and network traffic.

Sample Display

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

Use the debug qllc event EXEC command to enable debugging of QLLC events. The no form of this command disables debugging output.

[no] debug qllc event

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 XID frames.

Sample Display

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 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

Use the debug qllc packet EXEC command to display QLLC events and QLLC data packets. The no form of this command disables debugging output.

[no] debug qllc packet

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 debug qllc packet in conjunction with debug x25 all to see the connection and the data that flows through the router.

Sample Display

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 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 transmitted 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

Use the debug qllc state EXEC command to enable debugging of the QLLC events. The no form of this command disables debugging output.

[no] debug qllc state

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.

Sample Display

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 a QLLC connection attempt is changing state from ADM to SETUP:

QLLC: state ADM -> SETUP

The following line indicates a QLLC connection attempt is changing state from SETUP to NORMAL:

QLLC: state SETUP -> NORMAL

debug qllc timer

Use the debug qllc timer EXEC command to display QLLC timer events. The no form of this command disables debugging output.

[no] debug qllc timer

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, a LAPB primitive command is resent until the partner is in the desired state or the timer expires.

Sample Display

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

Use the debug qllc x25 EXEC command to display X.25 packets that affect a QLLC connection. The no form of this command disables debugging output.

[no] debug qllc x25

Usage Guidelines

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

Sample Display

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 108 describes fields of output.


Table 108: Debug QLLC X.25 Field Descriptions
Field Description

15:07:23

Shows the time of day.

QLLC X25 notify 257

Indicates 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 radius

Use the debug radius EXEC command to display information associated with the Remote Authentication Dial-In User Server (RADIUS). The no form of this command disables debugging output.

[no] debug radius

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.

Use the debug aaa authentication command to get a high-level view of login activity. When RADIUS is used on the router, you can use the debug radius command for more detailed debugging information.

Sample Displays

The following is sample output from the debug aaa authentication command for a RADIUS login attempt that failed. The information indicates that RADIUS is the authentication method used.

Router# debug aaa authentication
14:02:55: AAA/AUTHEN (164826761): Method=RADIUS
14:02:55: AAA/AUTHEN (164826761): status = GETPASS
14:03:01: AAA/AUTHEN/CONT (164826761): continue_login
14:03:01: AAA/AUTHEN (164826761): status = GETPASS
14:03:01: AAA/AUTHEN (164826761): Method=RADIUS
14:03:04: AAA/AUTHEN (164826761): status = FAIL

The following is partial sample output from the debug radius command that shows a login attempt that failed because of a key mismatch (that is, a configuration problem):

Router# debug radius
13:55:19: Radius: IPC Send 0.0.0.0:1645, Access-Request, id 0x7, len 57
13:55:19:         Attribute 4 6 AC150E5A
13:55:19:         Attribute 5 6 0000000A
13:55:19:         Attribute 1 7 62696C6C
13:55:19:         Attribute 2 18 19D66483
13:55:22: Radius: Received from 171.69.1.152:1645, Access-Reject, id 0x7, len 20
13:55:22: Radius: Reply for 7 fails decrypt

The following is partial sample output from the debug radius command that shows a successful login attempt as indicated by an Access-Accept message:

Router# debug radius
13:59:02: Radius: IPC Send 0.0.0.0:1645, Access-Request, id 0xB, len 56
13:59:02:         Attribute 4 6 AC150E5A
13:59:02:         Attribute 5 6 0000000A
13:59:02:         Attribute 1 6 62696C6C
13:59:02:         Attribute 2 18 0531FEA3
13:59:04: Radius: Received from 171.69.1.152:1645, Access-Accept, id 0xB, len 26
13:59:04:         Attribute 6 6 00000001

The following is partial sample output from the debug radius command that shows an unsuccessful login attempt as indicated by the Access-Reject message:

Router# debug radius
13:57:56: Radius: IPC Send 0.0.0.0:1645, Access-Request, id 0xA, len 57
13:57:56:         Attribute 4 6 AC150E5A
13:57:56:         Attribute 5 6 0000000A
13:57:56:         Attribute 1 7 62696C6C
13:57:56:         Attribute 2 18 49C28F6C
13:57:59: Radius: Received from 171.69.1.152:1645, Access-Reject, id 0xA, len 20

Related Commands

debug aaa accounting
debug aaa authentication

debug rif

Use the debug rif EXEC command to display information on entries entering and leaving the routing information field (RIF) cache. The no form of this command disables debugging output.

[no] debug rif

Usage Guidelines

In order to use the debug rif command to display traffic source-routed through an interface, fast switching of source route bridging (SRB) frames must first be disabled with the no source-bridge route-cache interface configuration command.

Sample Display

The following is sample output from the debug rif command:


The first line of output is an example of a RIF entry for an interface configured for SDLLC or Local-Ack. Table 109 describes significant fields shown in this line of debug rif output.


Table 109: Debug RIF Field Descriptions---Part 1
Field Description

RIF:

This message describes RIF debugging output.

U chk

Update checking. The entry is being updated; the timer is set to zero (0).

da = 9000.5a59.04f9

Destination MAC address.

sa = 0110.2222.33c1

Source MAC address. This field contains values of zero (0000.0000.0000) in a non-SDLLC or non-Local-ack entry.

[4880.3201.00A1.0050]

RIF string. This field is blank (null RIF) in a non-SDLLC or non-Local-Ack entry.

type 8

Possible values follow:

  • 0---Null entry

  • 1---This entry was learned from a particular Token Ring port (interface)

  • 2---Statically configured

  • 4---Statically configured for a remote interface

  • 8---This entry is to be aged

  • 16---This entry (which has been learned from a remote interface) is to be aged

  • 32---This entry is not to be aged

  • 64 ---This interface is to be used by LAN Network Manager (and is not to be aged)

on static/remote/0

This route was learned from a real Token Ring port, in contrast to a virtual ring.

The following line of output is an example of a RIF entry for an interface that is not configured for SDLLC or Local-Ack:

RIF: U chk da=0000.3080.4aed,sa=0000.0000.0000 [] type 8 on TokenRing0/0

Notice that the source address contains only zero values (0000.0000.0000), and that the RIF string is null ([  ]). The last element in the entry indicates that this route was learned from a virtual ring, rather than a real Token Ring port.

The following line shows that a new entry has been added to the RIF cache:

RIF: U add 1000.5a59.04f9 [4880.3201.00A1.0050] type 8

The following line shows that a RIF cache lookup operation has taken place:

RIF: L checking da=0000.3080.4aed, sa=0000.0000.0000

The following line shows that a TEST response from address 9000.5a59.04f9 was inserted into the RIF cache:

RIF: rcvd TEST response from 9000.5a59.04f9

The following line shows that the RIF entry for this route has been found and updated:

RIF: U upd da=1000.5a59.04f9,sa=0110.2222.33c1 [4880.3201.00A1.0050]

The following line shows that an XID response from this address was inserted into the RIF cache:

RIF: rcvd XID response from 9000.5a59.04f9

The following line shows that the router sent an XID response to this address:

SR1: sent XID response to 9000.5a59.04f9

Table 110 explains the other possible lines of debug rif output.


Table 110: Debug RIF Field Descriptions---Part 2
Field Description

RIF: L Sending XID for address

The router/bridge wanted to send a packet to address but did not find it in the RIF cache. It sent an XID explorer packet to determine which RIF it should use. The attempted packet is dropped.

RIF: L No buffer for XID to address

Similar to the previous description; however, a buffer in which to build the XID packet could not be obtained.

RIF: U remote rif too small [rif]

A packet's RIF was too short to be valid.

RIF: U rej address too big [rif]

A packet's RIF exceeded the maximum size allowed and was rejected. The maximum size is 18  bytes.

RIF: U upd interface address

The RIF entry for this router/bridge's interface has been updated.

RIF: U ign address interface update

A RIF entry that would have updated an interface corresponding to one of this router's interfaces.

RIF: U add address [rif]

The RIF entry for address has been added to the RIF cache.

RIF: U no memory to add rif for address

No memory to add a RIF entry for address.

RIF: removing rif entry for address, type code

The RIF entry for address has been forcibly removed.

RIF: flushed address

The RIF entry for address has been removed because of a RIF cache flush.

RIF: expired address

The RIF entry for address has been aged out of the RIF cache.

Related Command

debug list

debug rtr error

Use the debug rtr error EXEC command to enable logging of response time reporter runtime errors. The no form of this command disables debugging output---including the debug rtr trace command.

[no] debug rtr error [probe]

Syntax Description:

probe

(Optional) Number of the probe in the range 0 to 31.

Usage Guidelines

The response time reporter feature allows you to monitor network performance and network resources by measuring response times and availability. With this feature you can perform troubleshooting, problem notifications, and preproblem analysis based on response time reporter statistics.

The debug rtr error command displays runtime errors. When a probe number other than 0 is specified, all runtime errors for that probe are displayed when the probe is active. When the probe number is 0, all runtime errors relating to the response time reporter scheduler process are displayed. When no probe number is specified, all runtime errors for all active probes configured on the router and probe control are displayed. The response time reporter scheduler process is responsible for starting and stopping probes and managing the database.


Note Use the debug rtr error command before using the debug rtr trace command because the debug  rtr error command generates a smaller amount of traffic.

Because the trace output generated by the debug rtr trace command uses the same control mechanism as debug  rtr  error, the no debug rtr error command disables both logging and tracing.

Sample Display

The following is sample output from the debug rtr error command. All debug output for the response time reporter (including debug rtr trace) has the format shown.

Router# debug rtr error 1
RTR 1: Error Return Code - LU0 RTR Probe 1
                    in echoTarget on call luReceive
                    LuApiReturnCode of InvalidHandle - invalid host name or API handle

Table 111 describes the fields in the output.


Table 111: Debug RTR Error Field Descriptions
Field Description

RTR 1

Number of the probe generating the message.

Error Return Code

Message identifier indicating the error type (or error itself).

LU0 RTR Probe 1

Name of the process generating the message.

in echoTarget on call luReceive

LuApiReturnCode of InvalidHandle - invalid host name or API handle

Supplemental messages that pertain to the message identifier.

Related Command

debug rtr trace

debug rtr trace

Use the debug rtr trace EXEC command to trace the execution of a response time reporter probe. The no form of this command disables trace debugging output (but not debug rtr error output).

[no] debug rtr trace [probe]

Syntax Description:

probe

(Optional) Number of the probe in the range 0 to 31.

Usage Guidelines


Note The debug rtr trace command can generate a large number of debug messages. First use the debug  rtr error command, and then use the debug rtr trace on a per probe basis.

When a probe number other than 0 is specified, execution for that probe is traced. When the probe number is 0, the response time reporter scheduler process is traced. When no probe number is specified, all active probes and every probe control is traced. The response time reporter scheduler process is responsible for starting and stopping probes and managing the database.

The debug rtr trace command also enables debug rtr error for the specified probe. However, the no debug rtr trace command does not disable the debug rtr error command. You must manually disable the command by using the no debug rtr error command.

All debug output (including debug rtr error) has the format shown in the debug rtr error output example.

Sample Display

The following is sample output from the debug rtr trace command. In this example, a probe is traced through a single operation attempt: the setup of a connection to the target (LU0), the attempt at an echo, and the closing of the connection on the echo attempt.

Router# debug rtr trace 
RTR 1: Calling getRttMonOperState (check pending) - LU0 RTR Probe 1 
RTR 1: Calling getRttMonOperState (check death) - LU0 RTR Probe 1 
RTR 1: Starting An Echo Operation - LU0 RTR Probe 1 
RTR 1: setting receiveFinished to FALSE - LU0 RTR Probe 1 
                  in dependLuEchoApplication
RTR 1: openConnection called - LU0 RTR Probe 1 
                  Calling rttMonHopConnected
RTR 1: calling luT0orT2Open - LU0 RTR Probe 1 
RTR 1: Dumping luT0orT2Open Result - LU0 RTR Probe 1 
                  applicationHandle: inRttMonCtrlAdminQItem = 13920808
                  receiveFinished = FALSE currentLUHandle = 14199576
                  maxRespBufferLen = 52 receivedBufferLen = 0
                  aHostName = CWBC02 locAddr = 1 eApplNameLen = 7 
                  ApplName = D5E2D7C5C3C8D60 eModeName = 4040404040404040 userDataLen = 14
                  userData = D5E2D7C5C3C8D61 sysSense = 0 userSense = 0 bindDataLen = 64
                  bindData = D5E2D7C5C3C8D61 bindDataCount = 14
RTR 1: Calling rttMonSetConnectionHandle - LU0 RTR Probe 1 
RTR 1: Calling rttMonSetHopConnectedState to TRUE - LU0 RTR Probe 1 
RTR 1: Calling rttMonSetDiagText - LU0 RTR Probe 1 
RTR 1: setupPathInfo called - LU0 RTR Probe 1 
                  Calling rttMonStartUpdatePath
RTR 1: Calling rttMonUpdatePath - LU0 RTR Probe 1 
                  for Target CWBC02 NSPECHO         
RTR 1: Calling rttMonEndUpdatePath - LU0 RTR Probe 1 
RTR 1: Calling rttMonUpdateNumberOfEchosAttempted - LU0 RTR Probe 1 
RTR 1: performEcho called - LU0 RTR Probe 1 
                  applicationHandle: inRttMonCtrlAdminQItem = 13920808
                  receiveFinished = FALSE currentLUHandle = 14199576
                  maxRespBufferLen = 52 receivedBufferLen = 0
                  echoTimeout (milliseconds) = 5000 sequenceNum = 886
                  rttMonEchoAdminTargetAddress is CWBC02 NSPECHO
                  verifyDataFlag = False
RTR 1: Calling rttMonGetFirstStoredHopAddress - LU0 RTR Probe 1 
RTR 1: echoTarget called - LU0 RTR Probe 1 
                  applicationHandle: inRttMonCtrlAdminQItem = 13920808
                  receiveFinished = FALSE currentLUHandle = 14199576
                  maxRespBufferLen = 52 receivedBufferLen = 0
                  echoTimeout (milliseconds) = 5000
                  Data: 
                   E6 A7 E8 A9 01 02 03 77   00 00 00 00 C1 
                  calling luReceive...
RTR 1: calling luSend - LU0 RTR Probe 1 
RTR 1: receiveFinished is FALSE - LU0 RTR Probe 1 
                  in echoTarget calling
                  process_wait_for_event_timed(5000 milliseconds)
RTR 1: rtt_closeIndication called - DSPU Msg Proc 
                  applicationHandle: inRttMonCtrlAdminQItem = 13920808
                  receiveFinished = FALSE currentLUHandle = 14199576
                  maxRespBufferLen = 52 receivedBufferLen = 0
RTR 1: setting receiveFinished to TRUE - DSPU Msg Proc 
                  in rtt_closeIndication
RTR 1: Woke on receive event - LU0 RTR Probe 1 
RTR 1: returned from echoTarget - LU0 RTR Probe 1 
                  with D_echoTarget_connectionLost return_code
                  and responseTime (milliseconds) = 196
...
RTR 1: Calling getRttMonOperState (check active) - LU0 RTR Probe 1 
RTR 1: Going to Sleep - LU0 RTR Probe 1 
                  until next frequency time (delta milliseconds 60000)

Related Command

debug rtr error

debug sdlc

Use the debug sdlc EXEC command to display information on Synchronous Data Link Control (SDLC) frames received and sent by any router serial interface involved in supporting SDLC end station functions. The no form of this command disables debugging output.

[no] debug sdlc

Usage Guidelines


Note Because the debug sdlc command can generate many messages and alter timing in the network node, use it only when instructed by authorized support personnel.

Sample Display

The following is sample output from the debug sdlc command:

Router# debug sdlc
SDLC: Sending RR at location 4
Serial3: SDLC O (12495952) C2 CONNECT (2) RR P/F 6
Serial3: SDLC I (12495964) [C2] CONNECT (2) RR P/F 0 (R) [VR: 6 VS: 0]
Serial3: SDLC T [C2] 12496064 CONNECT 12496064 0
SDLC: Sending RR at location 4
Serial3: SDLC O (12496064) C2 CONNECT (2) RR P/F 6
Serial3: SDLC I (12496076) [C2] CONNECT (2) RR P/F 0 (R) [VR: 6 VS: 0]
Serial3: SDLC T [C2] 12496176 CONNECT 12496176 0

The following line of output indicates that the router is sending a Receiver Ready packet at location  4 in the code:

SDLC: Sending RR at location 4

The following line of output describes a frame input event:

Serial3: SDLC O (12495952) C2 CONNECT (2) RR P/F 6

Table 112 describes the fields in this line of output.


Table 112: Debug SDLC Field Descriptions for a Frame Output Event
Field Description

SDLC

Protocol providing the information.

Serial3

Interface type and unit number reporting the frame event.

O

Command mode of frame event. Possible values follow:

  • I---Frame input

  • O---Frame output

  • T---T1 timer expired

(12495952)

Current timer value.

C2

SDLC address of the SDLC connection.

CONNECT

State of the protocol when the frame event occurred. Possible values follow:

  • CONNECT

  • DISCONNECT

  • DISCSENT (disconnect sent)

  • ERROR (FRMR frame sent)

  • REJSENT (reject frame sent)

  • SNRMSENT (SNRM frame sent)

  • USBUSY

  • THEMBUSY

  • BOTHBUSY

(2)

Size of the frame (in bytes).

RR

Frame type name. Possible values follow:

  • DISC---Disconnect

  • DM---Disconnect mode

  • FRMR---Frame reject

  • IFRAME---Information frame

  • REJ---Reject

  • RNR---Receiver not ready

  • RR---Receiver ready

  • SIM---Set Initialization mode command

  • SNRM---Set Normal Response Mode

  • TEST---Test frame

  • UA---Unnumbered acknowledgment

  • XID---EXchange ID

P/F

Poll/Final bit indicator. Possible values follow:

  • F---Final (printed for Response frames)

  • P---Poll (printed for Command frames)

  • P/F---Poll/Final (printed for RR, RNR and REJ frames, which can be either Command or Response frames)

6

Receive count; range: 0-7.

The following line of output describes a frame input event:

Serial3: SDLC I (12495964) [C2] CONNECT (2) RR P/F 0 (R) [VR: 6 VS: 0] rfp: P

In addition to the fields described in Table 112, output for a frame input event also includes the additional fields described in Table 113.


Table 113: Debug SDLC Field Descriptions Unique to a Frame Input Event
Field Description

(R)

Frame Type:

  • C---Command

  • R---Response

VR: 6

Receive count; range: 0-7.

VS: 0

Send count; range: 0-7.

rfp: P

Ready for poll;

  • P ---Idle poll (keepalive) timer is on.

  • T---Data acknowledgment timer is on.

These timers are based on the T1 timer.

VS: 0

Send count; range: 0-7.

The following line of output describes a frame timer event:

Serial3: SDLC T [C2] 12496064 CONNECT 12496064 0

Table 114 describes the fields in this line of output.


Table 114: Debug SDLC Field Descriptions for a Timer Event
Field Description

Serial3:

Interface type and unit number reporting the frame event.

SDLC

Protocol providing the information.

T

The timer has expired.

[C2]

SDLC address of this SDLC connection.

12496064

System clock.

CONNECT

State of the protocol when the frame event occurred. Possible values follow:

  • BOTHBUSY

  • CONNECT

  • DISCONNECT

  • DISCSENT (disconnect sent)

  • ERROR (FRMR frame sent)

  • REJSENT (reject frame sent)

  • SNRMSENT (SNRM frame sent)

  • THEMBUSY

  • BOTHBUSY

12496064

Top timer.

0

Retry count; default: 0.

Related Command

debug list

debug sdlc local-ack

Use the debug sdlc local-ack EXEC command to display information on the local acknowledgment feature. The no form of this command disables debugging output.

[no] debug sdlc local-ack [number]

Syntax Description

number

(Optional) Frame type that you want to monitor. Refer to the Usage Guidelines section.

Usage Guidelines

You can select the frame types you want to monitor; the frame types correspond to bit flags. You can select 1, 2, 4, or 7, which is the decimal value of the bit flag settings. If you select 1, the octet is set to 00000001. If you select 2, the octet is set to 0000010. If you select 4, the octet is set to 00000100. If you want to select all frame types, select 7; the octet is 00000111. The default is 7 for all events. Table 115 defines these bit flags.


Table 115: Debug SDLC Local-Ack Debugging Levels
Debug Command Meaning

debug sdlc local-ack 1

Only U-Frame events

debug sdlc local-ack 2

Only I-Frame events

debug sdlc local-ack 4

Only S-Frame events

debug sdlc local-ack 7

All SDLC Local-Ack events (default setting)

Caution Because using this command is processor intensive, it is best to use it after hours, rather than in a production environment. It is also best to use this command by itself, rather than in conjunction with other debugging commands.

Sample Display

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


The first line shows the input to the SDLC local acknowledgment state machine:

SLACK (Serial3): Input     = Network, LinkupRequest

Table 116 describes the fields in this line of output.


Table 116: Debug SDLC Local-Ack Field Descriptions
Field Description

SLACK

The SDLC local acknowledgment feature is providing the information.

(Serial3):

Interface type and unit number reporting the event.

Input = Network

The source of the input.

LinkupRequest

The op code. A LinkupRequest is an example of possible values.

The second line shows the change in the SDLC local acknowledgment state machine. In this case the AwaitSdlcOpen state is an internal state that has not changed while this display was captured.

SLACK (Serial3): Old State = AwaitSdlcOpen            New State = AwaitSdlcOpen

The third line shows the output from the SDLC local acknowledgment state machine:

SLACK (Serial3): Output     = SDLC, SNRM

debug sdlc packet

Use the debug sdlc packet EXEC command to display packet information on Synchronous Data Link Control (SDLC) frames received and sent by any router serial interface involved in supporting SDLC end station functions. The no form of this command disables debugging output.

[no] debug sdlc packet [max-bytes]

Syntax Description

max-byte

(Optional) Limits the number of bytes of data that are printed to the display.

Usage Guidelines

This command requires intensive CPU processing; therefore, we recommend not using it when the router is expected to handle normal network loads, such as in a production environment. Instead, use this command when network response is non-critical. We also recommend that you use this command by itself, rather than in conjunction with other debug commands.

Sample Display

The following is sample output from the debug sdlc packet command with the packet display limited to 20 bytes of data.

Router# debug sdlc packet 20
 Serial3 SDLC Output
00000 C3842C00 02010010 019000C5 C5C5C5C5 Cd.........EEEEE
00010 C5C5C5C5                            EEEE
 Serial3 SDLC Output
00000 C3962C00 02010011 039020F2          Co.........2
 Serial3 SDLC Output
00000 C4962C00 0201000C 039020F2          Do.........2
 Serial3 SDLC Input
00000     C491                              Dj

debug sdllc

Use the debug sdllc EXEC command to display information about data link layer frames transferred between a device on a Token Ring and a device on a serial line via a router configured with the SDLLC feature. The no form of this command disables debugging output.

[no] debug sdllc

Usage Guidelines

The SDLLC feature translates between the SDLC link layer protocol used to communicate with devices on a serial line and the LLC2 link layer protocol used to communicate with devices on a Token Ring.

The router configured with the SDLLC feature must be attached to the serial line. The router sends and receives frames on behalf of the serial device on the attached serial line but acts as an SDLC station.

The topology between the router configured with the SDLLC feature and the Token Ring is network dependent and is not limited by the SDLLC feature.

Sample Display

The following is sample output from the debug sdllc command between link layer peers from the perspective of the SDLLC-configured router.

Router# debug sdllc
SDLLC: rx explorer rsp, da 4000.2000.1001, sa C000.1020.1000, rif
 8840.0011.00A1.0050
SDLLC: tx short xid, sa 4000.2000.1001, da C000.1020.1000, rif
 88C0.0011.00A1.0050, dsap 4 ssap 4
SDLLC: tx long xid, sa 4000.2000.1001, da C000.1020.1000, rif
 88C0.0011.00A1.0050, dsap 4 ssap 4
Rcvd SABME/LINKUP_REQ pak from TR host
SDLLCERR: not from our partner, pak dropped, da 4000.2000.1001,
sa C000.1020.1000, rif 8840.0011.00A1.0050, partner = 5000.1040.1003

Table 117 describes the significant fields.


Table 117: Debug SDLLC Field Descriptions
Field Description

rx

Router receives message from the FEP.

explorer rsp

Response to an explorer (TEST) frame previously sent by the router to FEP.

da

Destination address. This is the address of the router receiving the response.

sa

Source address. This is the address of the FEP sending the response to the router.

rif

Routing information field.

tx

Router sent message to the FEP.

short xid

Router sent the null XID to the FEP.

dsap

Destination service access point

ssap

Source service access point.

tx long xid

Router sent the XID type 2 to the FEP.

Rcvd

Router received Layer 2 message from the FEP.

SABME/LINKUP_REQ

Set asynchronous Balanced Mode Extended command.

partner =

Partner address.

The following line indicates that an explorer frame response was received by the router at address 4000.2000.1001 from the FEP at address C000.1020.1000 with the specified RIF. The original explorer sent to the FEP from the router is not monitored as part of the debug sdllc command.

SDLLC: rx explorer rsp, da 4000.2000.1001, sa C000.1020.1000, rif
 8840.0011.00A1.0050

The following line indicates that the router sent the null XID (Type 0) to the FEP. The debugging information does not include the response to the XID message sent by the FEP to the router.

SDLLC: tx short xid, sa 4000.2000.1001, da C000.1020.1000, rif
 88C0.0011.00A1.0050, dsap 4 ssap 4

The following line indicates that the router sent the XID command (Format 0 Type 2) to the FEP:

SDLLC: tx long xid, sa 4000.2000.1001, da C000.1020.1000, rif
 88C0.0011.00A1.0050, dsap 4 ssap 4

The following line is the SABME response to the XID command previously sent by the router to the FEP:

Rcvd SABME/LINKUP_REQ pak from TR host


hometocprevnextglossaryfeedbacksearchhelp
Copyright 1989-1998 © Cisco Systems Inc.