Table Of Contents

cHDLC Debug Commands on Cisco IOS XR Software

debug chdlc ma slarp

cHDLC Debug Commands on Cisco IOS XR Software

---

This chapter describes the Cisco High-Level Data Link Control (cHDLC) and Serial Line Address Resolution Protocol (SLARP) debug commands on Cisco IOS XR software.

debug chdlc ma slarp

To debug the SLARP protocol, use the debug chdlc ma slarp command in EXEC mode. To disable debugging, use the no form of this command.

debug chdlc ma slarp {packets | state} [location node-id] [interface interface-type interface-instance]

no debug chdlc ma slarp {packets | state} [location node-id] [interface interface-type interface-instance]

Syntax Description

packets	Specifies the debug information for sent and received SLARP packets.
state	Specifies the debug information for the state of the SLARP finite state machine.
location node-id	(Optional) Specifies the location on the router, for example, 0/0/CPU0. The node-id argument is entered in the rack/slot/module notation.
interface interface-type	(Optional) Interface type. For more information, use the question mark (?) online help function.
interface-instance	(Optional) Either a physical interface instance or a virtual interface instance as follows: •Physical interface instance. Naming notation is rack/slot/module/port and a slash between values is required as part of the notation. –rack: Chassis number of the rack. –slot: Physical slot number of the modular services card or line card. –module: Module number. A physical layer interface module (PLIM) is always 0. –port: Physical port number of the interface. Note In references to a Management Ethernet interface located on a route processor card, the physical slot number is alphanumeric (RP0 or RP1) and the module is CPU0. Example: interface MgmtEth0/RP1/CPU0/0. •Virtual interface instance. Number range varies depending on interface type. For more information about the syntax for the router, use the question mark (?) online help function.

Defaults

If no location is specified, the default is all locations.

Command Modes

EXEC

Command History

Release	Modification
Release 2.0	This command was introduced on the Cisco CRS-1.
Release 3.0	No modification.
Release 3.2	This command was supported on the Cisco XR 12000 Series Router.
Release 3.3.0	Command name changed to include the ma keyword. Added the interface keyword.
Release 3.4.0	No modification.
Release 3.5.0	No modification.
Release 3.6.0	No modification.

Usage Guidelines

To use this command, you must be in a user group associated with a task group that includes the proper task IDs. For detailed information about user groups and task IDs, see the Configuring AAA Services on Cisco IOS XR Software module of the Cisco IOS XR System Security Configuration Guide.

Debugging output is assigned high priority in the CPU process and, therefore, can affect system performance. For more information about the impact on system performance when using debug commands, refer to Using Debug Commands on Cisco IOS XR Software.

Task ID

Task ID	Operations
hdlc	read

Examples

The following example shows the sample output for the packet keyword with the debug chdlc ma slarp command:

RP/0/RP0/CPU0:router# debug chdlc ma slarp packet location 0/4/CPU0

LC/0/4/CPU0:Mar 29 12:31:01.038 : chdlc_ma[113]: POS0/4/0/1: SLARP REQUEST Sent (length 
14): [IP-Addr 0.0.0.0, IP-Mask 0.0.0.0]  
LC/0/4/CPU0:Mar 29 12:31:01.054 : chdlc_ma[113]: POS0/4/0/1: SLARP REPLY Received (length 
14): [IP-Addr 0.0.0.0, IP-Mask 0.0.0.0]  
LC/0/4/CPU0:Mar 29 12:31:08.924 : chdlc_ma[113]: POS0/4/0/1: SLARP KEEPALIVE Received 
(length 18): [My-Seq 2, Your-Seq 0, Unique 17650] Line UP  
LC/0/4/CPU0:Mar 29 12:31:11.203 : chdlc_ma[113]: POS0/4/0/1: SLARP KEEPALIVE Sent (length 
18): [My-Seq 1, Your-Seq 2, Unique 32549] Line UP  
LC/0/4/CPU0:Mar 29 12:31:18.964 : chdlc_ma[113]: POS0/4/0/1: SLARP KEEPALIVE Received 
(length 18): [My-Seq 3, Your-Seq 1, Unique 17650] Line UP  
LC/0/4/CPU0:Mar 29 12:31:21.244 : chdlc_ma[113]: POS0/4/0/1: SLARP KEEPALIVE Sent (length 
18): [My-Seq 2, Your-Seq 3, Unique 32549] Line UP  
LC/0/4/CPU0:Mar 29 12:31:29.004 : chdlc_ma[113]: POS0/4/0/1: SLARP KEEPALIVE Received 
(length 18): [My-Seq 4, Your-Seq 2, Unique 17650] Line UP  
LC/0/4/CPU0:Mar 29 12:31:31.285 : chdlc_ma[113]: POS0/4/0/1: SLARP KEEPALIVE Sent (length 
18): [My-Seq 3, Your-Seq 4, Unique 32549] Line UP  
LC/0/4/CPU0:Mar 29 12:31:39.044 : chdlc_ma[113]: POS0/4/0/1: SLARP KEEPALIVE Received 
(length 18): [My-Seq 5, Your-Seq 3, Unique 17650] Line UP  
LC/0/4/CPU0:Mar 29 12:31:41.326 : chdlc_ma[113]: POS0/4/0/1: SLARP KEEPALIVE Sent (length 
18): [My-Seq 4, Your-Seq 5, Unique 32549] Line UP  

The following example shows the sample output for the statechange keyword from the debug chdlc ma slarp command:

RP/0/RP0/CPU0:router# debug chdlc ma slarp statechange location 0/4/CPU0

LLC/0/4/CPU0:Mar 29 12:31:01.040 : chdlc_ma[113]: POS0/4/0/1: SLARP FSM State Change: 
[DOWN, Keepalives enabled] -> [LINECHECK]  
LC/0/4/CPU0:Mar 29 12:31:01.067 : chdlc_ma[113]: POS0/4/0/1: SLARP FSM State Change: 
[LINECHECK] -> [UP, Keepalives enabled]  
LC/0/4/CPU0:Mar 29 12:33:18.013 : chdlc_ma[113]: POS0/4/0/1: SLARP FSM State Change: [UP, 
Keepalives enabled] -> [UP, Keepalives disabled]  
LC/0/4/CPU0:Mar 29 12:33:22.522 : chdlc_ma[113]: POS0/4/0/1: SLARP FSM State Change: [UP, 
Keepalives disabled] -> [DOWN, Keepalives disabled]