-
Cisco IOS XR IP Addresses and Services Debug Command Reference, Release 3.3
-
Preface
-
Access List Debug Commands on Cisco IOS XR Software
-
ARP Debug Commands on Cisco IOS XR Software
-
Cisco Express Forwarding Debug Commands on Cisco IOS XR Software
-
DHCP Debug Commands on CIsco IOS XR Software
-
HSRP Debug Commands on Cisco IOS XR Software
-
LPTS Debug Commands on Cisco IOS XR Software
-
Network Stack IPv4 and IPv6 Debug Commands on Cisco IOS XR Software
-
VRRP Debug Commands on Cisco IOS XR Software
-
Index
-
Feedback
Table Of Contents
Network Stack Debug Commands on Cisco IOS XR Software
Network Stack Debug Commands on Cisco IOS XR Software
This chapter describes the commands used to debug Network Stack problems.
debug arm api
To enable Internet Protocol Address Repository Manager (IPARM) application program interface (API) debugging, use the debug arm api command in EXEC mode. To disable IPARM API debugging, use the no form of this command.
debug arm api {all | callbacks | calls | database | db-access | errors | ipc}
no debug arm api {all | callbacks | calls | database | db-access | errors | ipc}
Syntax Description
Defaults
No default behavior or values
Command Modes
EXEC
Command History
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
Examples
The following example shows how to enable IPARM local server debugging:
RP/0/RP0/CPU0:router# debug arm apidebug arm ipv4
To enable IPv4 ARM server events debugging, use the debug arm ipv4 command in EXEC mode. To disableIPv4 ARM server events debugging, use the no form of this command.
debug arm ipv4 {conflict {override | policy} | error interface type instance | events [internal | external] [global | interface type instance] | redundancy [global | interface type instance]}
no debug arm ipv4 {conflict {override | policy} | error interface type instance | events [internal | external] [global | interface type instance] | redundancy [global | interface type instance]}
Syntax Description
Defaults
No default behavior or values
Command Modes
EXEC
Command History
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 this command to display IPv4 ARM server events related to address conflict checking and conflict overrides.
Task ID
Examples
The following example shows how to enable IPv4 ARM server event debugging:
RP/0/RP0/CPU0:router# debug arm ipv4 conflict overridedebug arm ipv6
To enable IPv6 ARM server events debugging, use the debug arm ipv6 command in EXEC mode. To disable Pv6 ARM server events debugging, use the no form of this command.
debug arm ipv6 {conflict {override | policy} | events [internal | external] [global | interface type instance] | redundancy [global | interface type instance]}
no debug arm ipv6 {conflict {override | policy} | events [internal | external] [global | interface type instance] | redundancy [global | interface type instance]}
Syntax Description
Defaults
No default behavior or values
Command Modes
EXEC
Command History
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 this command to display IPv6 ARM server events related to address conflict checking and conflict overrides.
Task ID
Examples
The following example shows how to enable IPv6 ARM server event debugging:
RP/0/RP0/CPU0:router# debug arm ipv6 conflict overridedebug arm local server
To enable Internet Protocol Address Repository Manager (IPARM) local server debugging, use the debug arm local server command in EXEC mode. To disable IPARM local server debugging, use the no form of this command.
debug arm local server {all | callbacks | calls | errors | ipc}
no debug arm local server {all | callbacks | calls | errors | ipc}
Syntax Description
Defaults
No default behavior or values
Command Modes
EXEC
Command History
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
Examples
The following example shows how to enable IPARM local server debugging:
RP/0/RP0/CPU0:router# debug arm local server alldebug ipv4 att-api
To enable IPv4 application programming interface (API) attribute debugging, use the debug ipv4 att-api command in EXEC mode. To disable IPv4 API attribute debugging, use the no form of this command.
debug ipv4 attr-api [callbacks | errors | events] [job job-id | process process-id] [location node-id]
no debug ipv4 attr-api [callbacks | errors | events] [job job-id | process process-id] [location node-id]
Syntax Description
Defaults
No default behavior or values
Command Modes
EXEC
Command History
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
Examples
The following example shows how to enable IPv4 API attribute error debugging:
RP/0/RP0/CPU0:router# debug ipv4 attr-api errorsdebug ipv4 error
To enable IPv4 event error debugging, use the debug ipv4 errors command in EXEC mode. To disable IPv4 event error debugging, use the no form of this command.
debug ipv4 error [detail] [location node-id]
no debug ipv4 error [detail] [location node-id]
Syntax Description
Defaults
No default behavior or values
Command Modes
EXEC
Command History
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
Examples
The following example shows how to enable IPv4 event error debugging:
RP/0/RP0/CPU0:router# debug ipv4 errordebug ipv4 events
To enable IPv4 event debugging, use the debug ipv4 events command in EXEC mode. To disable IPv4 event debugging, use the no form of this command.
debug ipv4 events [bulk | init] [location node-id]
no debug ipv4 events [bulk | init] [location node-id]
Syntax Description
Defaults
No default behavior or values
Command Modes
EXEC
Command History
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
Examples
The following example shows how to enable IPv4 event debugging:
RP/0/RP0/CPU0:router# debug ipv4 eventsdebug ipv4 ma error
To enable IPv4 management agent error debugging, use the debug ipv4 ma error command in EXEC mode. To disable IPv4 management agent error debugging, use the no form of this command.
debug ipv4 ma error [detail] [location node-id]
no debug ipv4 ma error [detail] [location node-id]
Syntax Description
Defaults
No default behavior or values
Command Modes
EXEC
Command History
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
Examples
The following example shows how to enable IPv4 management agent error debugging:
RP/0/RP0/CPU0:router# debug ipv4 ma errordebug ipv4 options
To enable IPv4 options-related error, event, and packet debugging, use the debug ipv4 options command in EXEC mode. To disable IPv4 options-related error, event, and packet debugging, use the no form of this command.
debug ipv4 options {all | events | errors | packets} [location node-id]
no debug ipv4 options {all | events | errors | packets} [location node-id]
Syntax Description
Defaults
No default behavior or values
Command Modes
EXEC
Command History
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
Examples
The following example shows how to enable all IPv4 processing option debugging:
RP/0/RP0/CPU0:router# debug ipv4 options alldebug ipv4 packet
To enable IPv4 input and output packet debugging, use the debug ipv4 packet command in EXEC mode. To disable IPv4 input and output packet debugging, use the no form of this command.
debug ipv4 packet [access-list] [dump {ingress | egress} | error | detail] [location node-id]
no debug ipv4 packet [access-list] [dump {ingress | egress} | error | detail] [location node-id]
Syntax Description
Defaults
No default behavior or values
Command Modes
EXEC
Command History
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
Examples
The following example shows how to enable IPv4 input and output packet error debugging:
RP/0/RP0/CPU0:router# debug ipv4 packet errordebug ipv4 smiap
To enable IPv4 Single Management IP Address Process (SMIAP) debugging, use the debug ipv4 smiap command in EXEC mode. To disable IPv4 SMIAP debugging, use the no form of this command.
debug ipv4 smiap {error | event} location node-id
no debug ipv4 smiap {error | event} location node-id
Syntax Description
Defaults
No default behavior or values
Command Modes
EXEC
Command History
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
Examples
The following example shows how to enable IPv4 SMIAP error debugging:
RP/0/RP0/CPU0:router# debug ipv4 smiap error location 0/2/cp0debug ipv6 assembler
To enable IPv6 fragmented packet assembler debugging, use the debug ipv6 assembler command in EXEC mode. To disable IPv6 fragmented packet assembler debugging, use the no form of this command.
debug ipv6 assembler {all | errors | events | packet} [location node-id]
no debug ipv6 assembler {all | errors | events | packet} [location node-id]
Syntax Description
Defaults
No default behavior or values
Command Modes
EXEC
Command History
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
Examples
The following example shows how to enable IPv6 fragmented packet assembler debugging:
RP/0/RP0/CPU0:router# debug ipv6 assembler all location 0/2/cp0debug ipv6 fib
To enable IPv6 forwarding information base debugging, use the debug ipv6 fib command in EXEC mode. To disable IPv4 forwarding information base debugging, use the no form of this command.
debug ipv6 fib {adjacency | download | errors | lookup | messages | nsf | route | timing} [location node-id]
no debug ipv6 fib {adjacency | download | errors | lookup | messages | nsf | route | timing} [location node-id]
Syntax Description
Defaults
No default behavior or values
Command Modes
EXEC
Command History
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
Examples
The following example shows how to enable ipv6 fib debugging:
RP/0/RP0/CPU0:router# debug ipv6 fib adjacencydebug ipv6 icmp
To enable IPv6 Internet Control Message Protocol (ICMP) debugging, use the debug ipv6 icmp command in EXEC mode. To disable ICMP debugging, use the no form of this command.
debug ipv6 icmp [location node-id]
no debug ipv6 icmp [location node-id]
Syntax Description
location node-id
(Optional) Displays IPv6 ICMP 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
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
Examples
The following example shows how to enable IPv6 ICMP debugging:
RP/0/RP0/CPU0:router# debug ipv6 icmp location 0/2/cp0debug ipv6 io
To enable IPv6 inbound and outbound debugging, use the debug ipv6 io command in EXEC mode. To disable IPv6 inbound and outbound debugging, use the no form of this command.
debug ipv6 io {all | api {calls | errors} [job job-id | process process-id] | errors | events | packets [incoming | outgoing] [detail]} [location node-id]
no debug ipv6 io {all | api {calls | errors} [job job-id | process process-id] | errors | events | packets [incoming | outgoing] [detail]} [location node-id]
Syntax Description
Defaults
No default behavior or values
Command Modes
EXEC
Command History
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
Examples
The following example shows how to enable IPv6 inbound and outbound debugging:
RP/0/RP0/CPU0:router# debug ipv6 io all location 0/2/cp0debug ipv6 ma
To enable IPv6 management agent debugging, use the debug ipv6 ma command in EXEC mode. To disable IPv6 management agent debugging, use the no form of this command.
debug ipv6 ma {errors | events | mhost} [location node-id]
no debug ipv6 ma {errors | events | mhost} [location node-id]
Syntax Description
Defaults
No default behavior or values
Command Modes
EXEC
Command History
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
Examples
The following example shows how to enable IPv6 management agent event debugging:
RP/0/RP0/CPU0:router# debug ipv6 ma events location 0/2/cp0debug ipv6 nd
To enable IPv6 neighbor discovery debugging, use the debug ipv6 nd command in EXEC mode. To disable IPv6 neighbor discovery debugging, use the no form of this command.
debug ipv6 nd {api errors | events | packet [interface | incoming | outgoing] [detail] | timers} [location node-id]
no debug ipv6 nd {api errors | errors | events | packet [interface | incoming | outgoing] [detail] | timers} [location node-id]
Syntax Description
Defaults
No default behavior or values
Command Modes
EXEC
Command History
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 api keyword to track the communication channel between IPV6_ND and IPV6_MA components.
Use the errors keyword when the neighbor is not functioning normally. Error messages are printed when error conditions are detected. Error messages include lost connections, failed memory allocations, failed API function calls, and so on.
Use the events keyword to collect data for further debugging or analysis. Event messages are printed from internal and external sources. Neighbor events include sending a NS packet, notification from the interface manager, installing a neighbor adjacency to the adjacency information base (AIB), and so on.
Use the packet keyword to debug neighbor- related protocol problems such that failed to resolve a MAC address, and so on.
Use the timers keyword to debug protocol related problems. Timer-related events such as `RA timer expires' are printed.
Task ID
Examples
The following example shows how to enable IPv6 neighbor event debugging:
RP/0/RP0/CPU0:router# debug ipv6 nd events location 0/2/cp0debug ipv6 netio
To enable IPv6 network input and output debugging, use the debug ipv6 netio command in EXEC mode. To disable IPv6 network input and output debugging, use the no form of this command.
debug ipv6 netio {cap | proto} [location node-id | interface-type interface-instance]
no debug ipv6 netio {cap | proto} [location node-id | interface-type interface-instance]
Syntax Description
Defaults
No default behavior or values
Command Modes
EXEC
Command History
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
Examples
The following example shows how to enable IPv6 network input and output netio protocol debugging:
RP/0/RP0/CPU0:router# debug ipv6 netio proto location 0/2/cp0debug ipv6 packet
To enable IPv6 packet data debugging, use the debug ipv6 packet command in EXEC mode. To disable IPv6 packet data debugging, use the no form of this command.
debug ipv6 packet [input | output | detail] [location node-id | interface-type interface-instance]
no debug ipv6 packet [input | output | detail] [location node-id | interface-type interface-instance]
Syntax Description
Defaults
No default behavior or values
Command Modes
EXEC
Command History
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
Examples
The following example shows how to enable IPv6 packet data debugging for incoming packets:
RP/0/RP0/CPU0:router# debug ipv6 packet input POS 0/3/0/0
Physical interface instance. Naming notation is rack/slot/module/port and a slash between values is required as part of the notation.