Table Of Contents

ARP Debug Commands on Cisco IOS XR Software

debug arp all

debug arp bulk

debug arp errors

debug arp events

debug arp packets

debug arp table

ARP Debug Commands on Cisco IOS XR Software

---

This chapter describes the commands used to debug the Address Resolution Protocol (ARP).

debug arp all

To enable all Address Resolution Protocol (ARP) debugging, use the debug arp all command in EXEC mode. To disable all ARP debugging, use the no form of this command.

debug arp all [location node-id]

no debug arp all [location node-id]

Syntax Description

location node-id

(Optional) Displays ARP debug information for a specified location. The node-id argument is entered in the rack/slot/module notation.

Defaults

No default behavior or values

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	No modification.
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.

Use the debug arp all command to turn on all ARP debugging which includes bulk, error, event, packet, and table debugging.

Task ID

Task ID	Operations
cef	read

Examples

The following example shows how to enable all ARP debug commands:

RP/0/RP0/CPU0:router# debug arp all 

Related Commands

Command	Description
debug arp bulk	Debugs ARP bulk notifications.
debug arp errors	Debugs ARP errors.
debug arp events	Debugs ARP events.
debug arp packets	Debugs packets sent and received by the ARP process.
debug arp table	Debugs changes made to the ARP table.

debug arp bulk

To enable the debugging of Address Resolution Protocol (ARP) bulk notifications received from the Interface Manager and bulk notifications built and sent to the Interface Manager, use the debug arp bulk command in EXEC mode. To disable ARP bulk notifications debugging, use the no form of this command.

debug arp bulk [location node-id]

no debug arp bulk [location node-id]

Syntax Description

location node-id

(Optional) Displays ARP bulk notification debug information for a specified location. The node-id argument is entered in the rack/slot/module notation.

Defaults

No default behavior or values

Command Modes

EXEC

Command History

Release	Modification
Release 3.2	This command was introduced on the Cisco CRS-1 and the Cisco XR 12000 Series Router.
Release 3.3.0	No modification.
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.

Use the debug arp bulk command to debug the handling of bulk notifications from the Interface Manager and the building and sending of bulk notifications to the Interface Manager.

Task ID

Task ID	Operations
cef	read

Examples

The following example shows how to enable debugging of ARP bulk notifications from the Interface Manager:

RP/0/RP0/CPU0:router# debug arp bulk 

debug arp errors

To enable Address Resolution Protocol (ARP) error debugging, use the debug arp errors command in EXEC mode. To disable ARP error debugging, use the no form of this command.

debug arp errors [location node-id]

no debug arp errors [location node-id]

Syntax Description

location node-id

(Optional) Displays ARP error debug information for a specified location. The node-id argument is entered in the rack/slot/module notation.

Defaults

No default behavior or values

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	No modification.
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.

Use the debug arp errors command to debug errors that have occurred, including the reason for the error.

Task ID

Task ID	Operations
cef	read

Examples

The following example shows how to enable ARP error debugging:

RP/0/RP0/CPU0:router# debug arp errors 

debug arp events

To enable the debugging of Address Resolution Protocol (ARP) events that are expected and have completed successfully, use the debug arp events command in EXEC mode. To disable ARP event debugging, use the no form of this command.

debug arp events [location node-id | interface-instance interface-type]

no debug arp events [location node-id | interface-instance interface-type]

Syntax Description

location node-id	(Optional) Displays ARP successful event debug information for a specified location. The node-id argument is entered in the rack/slot/module notation.
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

No default behavior or values

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	No modification.
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.

Use the debug arp events command to debug events that have occurred in ARP in the expected scenarios, that is, operations that have completed successfully. Any event that fails or is unexpected generates an error debug message.

Task ID

Task ID	Operations
cef	read

Examples

The following example shows how to enable successful ARP event debugging:

RP/0/RP0/CPU0:router# debug arp events 

debug arp packets

To enable the debugging of Address Resolution Protocol (ARP) packets that were sent and received by the ARP process, use the debug arp packets command in EXEC mode. To disable ARP packet debugging, use the no form of this command.

debug arp packets [location node-id | interface-instance interface-type]

no debug arp packets [location node-id | interface-instance interface-type]

Syntax Description

location node-id	(Optional) Displays ARP packet debug information for a specified location. The node-id argument is entered in the rack/slot/module notation.
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

No default behavior or values

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	No modification.
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.

Use the debug arp packets command to debug ARP packets sent and received by the ARP process.

Task ID

Task ID	Operations
cef	read

Examples

The following example shows how to enable debugging of ARP packets sent and received by the ARP process:

RP/0/RP0/CPU0:router# debug arp packets 

debug arp table

To enable the debugging of changes made to the Address Resolution Protocol (ARP) table, use the debug arp table command in EXEC mode. To disable the debugging of changes made to the ARP table, use the no form of this command.

debug arp table [location node-id | interface-instance interface-type]

no debug arp table [location node-id | interface-instance interface-type]

Syntax Description

location node-id	(Optional) Displays ARP table debug information for a specified location. The node-id argument is entered in the rack/slot/module notation.
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

No default behavior or values

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	No modification.
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.

Use the debug arp table command to debug changes made to the ARP table, that is, entries that are added, changed, or deleted from the table.

Task ID

Task ID	Operations
cef	read

Examples

The following example shows how to enable ARP table debugging:

RP/0/RP0/CPU0:router# debug arp table