-
Cisco IOS XR Interface and Hardware Component Debug Command Reference, Release 3.3
-
Preface
-
Hardware Redundancy and Node Administration Debug Commands on Cisco IOS XR Software
-
Packet-over-SONET User Interface and SONET Layer 1 Debug Commands on Cisco IOS XR Software
-
cHDLC Debug Commands on Cisco IOS XR Software
-
PPP Debug Commands on Cisco IOS XR Software
-
SPA Interface Processor and Shared Port Adapter Debug Commands on Cisco IOS XR Software
-
Link Bundling Debug Commands on Cisco IOS XR Software
-
Bidirectional Forwarding Detection Debug Commands on Cisco IOS XR Software
-
Platform and Driver Debug Commands on Cisco IOS XR Software
-
Fabric Management Debug Commands on Cisco IOS XR Software
-
Index
-
Table Of Contents
Platform and Driver Debug Commands on
Cisco IOS XR Softwaredebug tcam-mgr cam entry update
debug tcam-mgr prefix-compress
Platform and Driver Debug Commands on
Cisco IOS XR Software
This module describes the commands that provide useful information for debugging the platform and driver components of the Cisco CRS-1 and the Cisco XR 12000 Series Router.
debug asic-scan
To display debugging information about the ASIC scan, use the debug asic-scan command in EXEC mode. To disable debugging, use the no form of this command.
debug asic-scan [level [level | error [level level] | trace [level level] | xsvf [level level]] | lib [error [level level] | level level| trace [level level]] [location node-id]
no debug asic-scan [level [level | error [level level] | trace [level level] | xsvf [level level]] | lib [error [level level] | level level| trace [level level]] [location node-id]
Syntax Description
Defaults
No default behavior or values
Command Modes
EXEC
Command History
Release 2.0
This command was introduced on the Cisco CRS-1.
Release 3.0
No modification.
Release 3.2
No modification.
Release 3.3.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
Examples
The following example shows how to enable debugging information for the ASIC scan for all nodes installed in a router:
RP/0/RP0/CPU0:router# debug asic-scanThe following example shows how to enable debugging information about the ASIC scan with the API library debugging flags turned on for all nodes installed in a router:
RP/0/RP0/CPU0:router# debug asic-scan level 2The following example shows how to enable debugging information about the ASIC scan with the API library debugging flags turned on for the CPU node installed in Slot 0:
RP/0/RP0/CPU0:router# debug asic-scan lib location 0/0/CPU0debug cctl
To display debugging information about chassis control driver functionality, use the debug cctl command in Admin EXEC mode. To disable debugging, use the no form of this command.
debug cctl [alarm | all | api | edm | errors | helperfunc | ideeprom | internalapi | monitor | obfl | reset | server | trap] [job jobid | process string] [location node-id]
no debug cctl [alarm | all | api | edm | errors | helperfunc | ideeprom | internalapi | monitor | obfl | reset | server | trap] [job jobid | process string] [location node-id]
Syntax Description
Defaults
No default behavior or values
Command Modes
Admin EXEC
Command History
Release 2.0
This command was introduced on the Cisco CRS-1.
Release 3.0
No modification.
Release 3.2
No modification.
Release 3.3.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
Examples
The following example shows how to enable debugging information for the complete functionality of Chassis Control Driver:
RP/0/RP0/CPU0:router(admin)# debug cctl allThe following example shows how to enable debugging information for the read ID EEPROM protocol implementation of Chassis Control Driver:
RP/0/RP0/CPU0:router(admin)# debug cctl ideepromThe following example shows how to enable debugging information for the reset functionality of job ID 3 for the CPU node in Slot 2:
RP/0/RP0/CPU0:router(admin)# debug cctl reset job 3 location 0/2/CPU0debug cetftp
To display debugging information about the CE-TFTP server, use the debug cetftp command in EXEC mode. To disable debugging, use the no form of this command.
debug cetftp {all | arp | brief | cfg | detail | enet | error | ip | server | timer}
no debug cetftp {all | arp | brief | cfg | detail | enet | error | ip | server | timer}
Syntax Description
Defaults
No default behavior or values
Command Modes
EXEC
Command History
Release 2.0
This command was introduced on the Cisco CRS-1.
Release 3.0
No modification.
Release 3.2
No modification.
Release 3.3.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
Examples
The following example shows how to enable debugging information for the CE-TFTP server:
RP/0/RP0/CPU0:router# debug cetftp allThe following example shows how to enable debugging information for CE-TFTP errors from internal functions.
RP/0/RP0/CPU0:router# debug cetftp errorRelated Commands
ce tftp server enable
Enables or disables Trivial File Transfer Protocol (TFTP) on a specific directory, or to enable files to be written to the TFTP server.
debug cpuctrl api
To turn on all debugging messages for the CPU controller driver API DLL, use the debug cpuctrl api command in EXEC mode. To disable debugging messages, use the no form of this command.
debug cpuctrl api [cdma | connect | errors | fatal | info | pdma | pio] [job jobid | process string] [location node-id]
no debug cpuctrl api [cdma | connect | errors | fatal | info | pdma | pio] [job jobid | process string] [location node-id]
Syntax Description
Defaults
No default behavior or values
Command Modes
EXEC
Command History
Release 2.0
This command was introduced on the Cisco CRS-1.
Release 3.0
No modification.
Release 3.2
No modification.
Release 3.3.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
Examples
The following example shows how to enable debugging information for the CPU controller driver API DLL:
RP/0/RP0/CPU0:router# debug cpuctrl apiThe following example shows how to enable debugging information for the CPU controller driver API DLL for the job with the ID 200:
RP/0/RP0/CPU0:router# debug cpuctrl api info job 200Related Commands
debug cpuctrl asic-error
To turn on error messages from the CPU controller driver asic errors, use the debug cpuctrl asic-error command in EXEC mode. To disable debugging messages, use the no form of this command.
debug cpuctrl asic-error [job jobid | process string] [location node-id]
no debug cpuctrl asic-error [job jobid | process string] [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 asic error messages for the CPU controller driver:
RP/0/RP0/CPU0:router# debug cpuctrl asic-errorRelated Commands
debug cpuctrl asic-info
To turn on informational messages from the CPU controller driver asic errors, use the debug cpuctrl asic-error command in EXEC mode. To disable debugging messages, use the no form of this command.
debug cpuctrl asic-info [job jobid | process string] [location node-id]
no debug cpuctrl asic-info [job jobid | process string] [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 asic error messages for the CPU controller driver:
RP/0/RP0/CPU0:router# debug cpuctrl asic-errorRelated Commands
debug cpuctrl detail
To turn on all debugging messages from the CPU controller driver, use the debug cpuctrl detail command in EXEC mode. To disable debugging messages, use the no form of this command.
debug cpuctrl detail [job jobid | process string] [location node-id]
no debug cpuctrl detail [job jobid | process string] [location node-id]
Syntax Description
Defaults
No default behavior or values
Command Modes
EXEC
Command History
Release 2.0
This command was introduced on the Cisco CRS-1.
Release 3.0
No modification.
Release 3.2
No modification.
Release 3.3.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
Examples
The following example shows how to enable debugging information for the CPU controller driver:
RP/0/RP0/CPU0:router# debug cpuctrl detailThe following example shows how to enable debugging information for the CPU controller driver on a specific node (in this example, the CPU node in Slot 2):
RP/0/RP0/CPU0:router# debug cpuctrl detail 0/2/CPU0Related Commands
debug cpuctrl entryexit
To turn on all entry and exit debugging messages from CPU controller driver, use the debug cpuctrl entryexit command in EXEC mode. To disable debugging messages, use the no form of this command.
debug cpuctrl entryexit [job jobid | process string] [location node-id]
no debug cpuctrl entryexit [job jobid | process string] [location node-id]
Syntax Description
Defaults
No default behavior or values
Command Modes
EXEC
Command History
Release 2.0
This command was introduced on the Cisco CRS-1.
Release 3.0
No modification.
Release 3.2
No modification.
Release 3.3.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
Examples
The following example shows how to turn on all entry and exit messages from CPU controller driver:
RP/0/RP0/CPU0:router# debug cpuctrl enteryexitThe following example shows how to turn on all entry and exit messages from CPU controller driver for the job with the ID 400:
RP/0/RP0/CPU0:router# debug cpuctrl enteryexit job 400Related Commands
debug cpuctrl error
To turn on debugging error messages from the CPU controller, use the debug cpuctrl error command in exec mode. To disable debugging messages, use the no form of this command.
debug cpuctrl error [job jobid | process string] [location node-id]
no debug cpuctrl error [job jobid | process string] [location node-id]
Syntax Description
Defaults
No default behavior or values
Command Modes
EXEC
Command History
Release 2.0
This command was introduced on the Cisco CRS-1.
Release 3.0
No modification.
Release 3.2
No modification.
Release 3.3.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
Examples
The following example shows how to turn on all error messages from the CPU controller:
RP/0/RP0/CPU0:router# debug cpuctrl errorThe following example shows how to turn on error messages from the CPU controller on a specific node (the CPU0 node in Slot 2):
RP/0/RP0/CPU0:router# debug cpuctrl error location 0/2/CPU0Related Commands
debug cpuctrl fatal
To turn on fatal messages from CPU controller driver, use the debug cpuctrl fatal command in EXEC mode. To disable fatal messages, use the no form of this command.
debug cpuctrl fatal [job jobid | process string] [location node-id]
no debug cpuctrl fatal [job jobid | process string] [location node-id]
Syntax Description
Defaults
No default behavior or values
Command Modes
EXEC
Command History
Release 2.0
This command was introduced on the Cisco CRS-1.
Release 3.0
No modification.
Release 3.2
No modification.
Release 3.3.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
Examples
The following example shows how to turn on fatal messages from CPU controller driver on all nodes in the router:
RP/0/RP0/CPU0:router# debug cpuctrl fatalThe following example shows how to turn on fatal messages from CPU controller driver on the a specific job (the job with the ID 332):
RP/0/RP0/CPU0:router# debug cpuctrl fatal job 332Related Commands
debug cpuctrl info
To turn on informational messages from the CPU controller, use the debug cpuctrl info command in EXEC mode. To disable informational messages, use the no form of this command.
debug cpuctrl info [job jobid | process string] [location node-id]
no debug cpuctrl info [job jobid | process string] [location node-id]
Syntax Description
Defaults
No default behavior or values
Command Modes
EXEC
Command History
Release 2.0
This command was introduced on the Cisco CRS-1.
Release 3.0
No modification.
Release 3.2
No modification.
Release 3.3.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
Examples
The following example shows how to turn on informational messages from the CPU controller:
RP/0/RP0/CPU0:router# debug cpuctrl infoThe following example shows how to turn on informational messages from the CPU controller on the process with the ID name:
RP/0/RP0/CPU0:router# debug cpuctrl info process nameRelated Commands
debug cpuctrl location
To turn on all debugging messages from the CPU controller driver on a specific node, use the debug cpuctrl location command in EXEC mode. To disable debugging messages, use the no form of this command.
debug cpuctrl location node-id
no debug cpuctrl location node-id
Syntax Description
Defaults
No default behavior or values
Command Modes
EXEC
Command History
Release 2.0
This command was introduced on the Cisco CRS-1.
Release 3.0
No modification.
Release 3.2
No modification.
Release 3.3.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
Examples
The following example shows how to turn on all debugging messages from the CPU controller driver on a specific node (the CPU controller in Slot 2):
RP/0/RP0/CPU0:router# debug cpuctrl location 0/2/CPU0Related Commands
debug egressq
To turn on all messages from the egress queue manager, use the debug egressq command in EXEC mode. To disable messages from the egress queue manager, use the no form of this command.
debug egressq
no debug egressq
Syntax Description
This command has no arguments or keywords.
Defaults
No default behavior or values
Command Modes
EXEC
Command History
Release 2.0
This command was introduced on the Cisco CRS-1.
Release 3.0
No modification.
Release 3.2
No modification.
Release 3.3.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
Examples
The following example shows how to turn all messages from the egress queue manager:
RP/0/RP0/CPU0:router# debug egressqRelated Commands
debug egressq api errors
To turn on all debug error messages from the egress queue manager API DLL, use the
debug egressq api errors command in EXEC mode. To disable error messages from the egress queue manager, use the no form of this command.debug egressq api errors [job jobid | process word] [location node-id]
no debug egressq api errors [job jobid | process word] [location node-id]
Syntax Description
Defaults
No default behavior or values
Command Modes
EXEC
Command History
Release 2.0
This command was introduced on the Cisco CRS-1.
Release 3.0
No modification.
Release 3.2
No modification.
Release 3.3.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
Examples
The following example shows how to turn on all debug error messages from the egress queue manager API DLL:
RP/0/RP0/CPU0:router# debug egressq api errorsThe following example shows how to turn on all debug error messages from the egress queue manager API DLL on a specific node (the CPU node in Slot 2):
RP/0/RP0/CPU0:router# debug egressq api errors location 0/2/CPU0Related Commands
debug egressq api fatal
To turn on all fatal messages from the egress queue manager API DLL, use the debug egressq api fatal command in EXEC mode. To disable fatal messages from the egress queue manager API DLL, use the no form of this command.
debug egressq api fatal [job jobid | process word] [location node-id]
no debug egressq api fatal [job jobid | process word] [location node-id]
Syntax Description
Defaults
No default behavior or values
Command Modes
EXEC
Command History
Release 2.0
This command was introduced on the Cisco CRS-1.
Release 3.0
No modification.
Release 3.2
No modification.
Release 3.3.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
Examples
The following example shows how to enable all fatal messages from the egress queue manager API DLL for the entire router:
RP/0/RP0/CPU0:router# debug egressq api fatalThe following example shows how to enable all fatal messages from the egress queue manager API DLL for a specific job (the job with the ID 323):RP/0/RP0/CPU0:router# debug egressq api fatal job 323Related Commands
debug egressq api info
To turn on informational messages from the egress queue manager API DLL, use the debug egressq api info command in EXEC mode. To disable informational messages from the egress queue manager API DLL, use the no form of this command.
debug egressq api info [location node-id]
no debug egressq api info [location node-id]
Syntax Description
Defaults
No default behavior or values
Command Modes
EXEC
Command History
Release 2.0
This command was introduced on the Cisco CRS-1.
Release 3.0
No modification.
Release 3.2
No modification.
Release 3.3.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
Examples
The following example shows how to enable informational messages from the egress queue manager API DLL:
RP/0/RP0/CPU0:router# debug egressq api infoThe following example shows how to enable informational messages from the egress queue manager API DLL on a specific node (the CPU node in Slot 2):
RP/0/RP0/CPU0:router# debug egressq api info location 0/0/CPU0Related Commands
debug egressq api job
To turn on all error messages from the egress queue manager API DLL on a specific job, use the debug egressq api job command in EXEC mode. To disable error messages from the egress queue manager API DLL, use the no form of this command.
debug egressq api job jobid [location node-id]
no debug egressq api job jobid [location node-id]
Syntax Description
Defaults
No default behavior or values
Command Modes
EXEC
Command History
Release 2.0
This command was introduced on the Cisco CRS-1.
Release 3.0
No modification.
Release 3.2
No modification.
Release 3.3.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
Examples
The following example shows how to enable all error messages from the egress queue manager API DLL on a specific job (the job with the ID 40):
RP/0/RP0/CPU0:router# debug egressq api job 40The following example shows how to enable all error messages from the egress queue manager API DLL for a job on a specific node. In this example, the job ID is 40, and the node is the CPU node in Slot 2:
RP/0/RP0/CPU0:router# debug egressq api job 40 location 0/0/CPU0Related Commands
debug egressq api location
To turn on all error messages from the egress queue manager API DLL on a specific node, use the debug egressq api location command in EXEC mode. To disable all error messages from the egress queue manager API DLL, use the no form of this command.
debug egressq api location node-id [job jobid | process word]
no debug egressq api location node-id [job jobid | process word]
Syntax Description
Defaults
No default behavior or values
Command Modes
EXEC
Command History
Release 2.0
This command was introduced on the Cisco CRS-1.
Release 3.0
No modification.
Release 3.2
No modification.
Release 3.3.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
Examples
The following example shows how to enable all error messages from the egress queue manager API DLL on a specific node (the CPU node in Slot 0):
RP/0/RP0/CPU0:router# debug egressq api location 0/0/CPU0The following example shows how to enable all error messages from the egress queue manager API DLL on for a specific job on a node. In this example, the job has the ID of 300, and it is located on the CPU node is Slot 0:
RP/0/RP0/CPU0:router# debug egressq api location 0/0/CPU0 job 300Related Commands
debug egressq api process
To turn on all error messages from the egress queue manager API DLL for a specific process, use the debug egressq api process command in EXEC mode. To disable error messages from the egress queue manager API DLL for a specific process, use the no form of this command.
debug egressq api process word [location node-id]
no debug egressq api process word [location node-id]
Syntax Description
Defaults
No default behavior or values
Command Modes
EXEC
Command History
Release 2.0
This command was introduced on the Cisco CRS-1.
Release 3.0
No modification.
Release 3.2
No modification.
Release 3.3.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
Examples
The following example shows how to enable all error messages from the egress queue manager API DLL for a specific process. In this example, the process ID is name.
RP/0/RP0/CPU0:router# debug egressq api process nameThe following example shows how to enable all error messages from the egress queue manager API DLL for a specific process on a specific node. In this example, the process ID is name, and it is located on the CPU node in Slot 0.
RP/0/RP0/CPU0:router# debug egressq api process name location 0/0/CPU0Related Commands
debug egressq cdma
To turn on all CDMA messages from the egress queue manager, use the debug egressq cdma command in EXEC mode. To disable CDMA messages from the egress queue manager, use the no form of this command.
debug egressq cdma [location node-id]
no debug egressq cdma [location node-id]
Syntax Description
Defaults
No default behavior or values
Command Modes
EXEC
Command History
Release 2.0
This command was introduced on the Cisco CRS-1.
Release 3.0
No modification.
Release 3.2
No modification.
Release 3.3.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
Examples
The following example shows how to enable all egress queue CDMA messages for the entire router:
RP/0/RP0/CPU0:router# debug egressq cdmaThe following example shows how to enable all egress queue CDMA messages on a specific node (the CPU node in Slot 2):
RP/0/RP0/CPU0:router# debug egressq cdma location 0/2/CPU0Related Commands
debug egressq detailed
To turn on detailed messages from the egress queue manager, use the debug egressq detailed command in EXEC mode. To disable detailed messages from the egress queue manager, use the no form of this command.
debug egressq detailed [location node-id]
no debug egressq detailed [location node-id]
Syntax Description
Defaults
No default behavior or values
Command Modes
EXEC
Command History
Release 2.0
This command was introduced on the Cisco CRS-1.
Release 3.0
No modification.
Release 3.2
No modification.
Release 3.3.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
Examples
The following example shows how to enable detailed messages for the entire router:
RP/0/RP0/CPU0:router# debug egressq detailedThe following example shows how to enable detailed messages on a specific node (the CPU node in Slot 2):
RP/0/RP0/CPU0:router# debug egressq detailed location 0/2/CPU0Related Commands
debug egressq eio
To turn on EIO messages from the egress queue manager, use the debug egressq eio command in EXEC mode. To disable EIO messages from the egress queue manager, use the no form of this command.
debug egressq eio [location node-id]
no debug egressq eio [location node-id]
Syntax Description
Defaults
No default behavior or values
Command Modes
EXEC
Command History
Release 2.0
This command was introduced on the Cisco CRS-1.
Release 3.0
No modification.
Release 3.2
No modification.
Release 3.3.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
Examples
The following example shows how to enable EIO messages for the entire router:
RP/0/RP0/CPU0:router# debug egressq eioThe following example shows how to enable EIO messages on a specific node (the CPU node in Slot 2):
RP/0/RP0/CPU0:router# debug egressq eio location 0/2/CPU0Related Commands
debug egressq entryexit
To turn on entry and exit messages from the egress queue manager, use the debug egressq entryexit command in EXEC mode. To disable entry and exit messages from the egress queue manager, use the no form of this command.
debug egressq entryexit [location node-id]
no debug egressq entryexit [location node-id]
Syntax Description
Defaults
No default behavior or values
Command Modes
EXEC
Command History
Release 2.0
This command was introduced on the Cisco CRS-1.
Release 3.0
No modification.
Release 3.2
No modification.
Release 3.3.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
Examples
The following example shows how to enable entry and exit messages for the entire router:
RP/0/RP0/CPU0:router# debug egressq entryexitThe following example shows how to enable entry and exit messages on a specific node (the CPU node in Slot 2):
RP/0/RP0/CPU0:router# debug egressq eio location 0/2/CPU0Related Commands
debug egressq error
To turn on error messages from the egress queue manager, use the debug egressq error command in EXEC mode. To disable error messages from the egress queue manager, use the no form of this command.
debug egressq error [location node-id]
no debug egressq error [location node-id]
Syntax Description
Defaults
No default behavior or values
Command Modes
EXEC
Command History
Release 2.0
This command was introduced on the Cisco CRS-1.
Release 3.0
No modification.
Release 3.2
No modification.
Release 3.3.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
Examples
The following example shows how to enable error messages from the egress queue manager for the entire router:
RP/0/RP0/CPU0:router# debug egressq errorThe following example shows how to enable error messages from the egress queue manager on a specific node (the CPU node in Slot 2):
RP/0/RP0/CPU0:router# debug egressq error location 0/2/CPU0Related Commands
debug egressq fatal
To turn on fatal messages from the egress queue manager, use the debug egressq fatal command in EXEC mode. To disable fatal messages from the egress queue manager, use the no form of this command.
debug egressq fatal [location node-id]
no debug egressq fatal [location node-id]
Syntax Description
Defaults
No default behavior or values
Command Modes
EXEC
Command History
Release 2.0
This command was introduced on the Cisco CRS-1.
Release 3.0
No modification.
Release 3.2
No modification.
Release 3.3.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
Examples
The following example shows how to enable fatal messages from the egress queue manager for the entire router:
RP/0/RP0/CPU0:router# debug egressq fatalThe following example shows how to enable fatal messages from the egress queue manager on a specific node (the CPU node in Slot 2):
RP/0/RP0/CPU0:router# debug egressq fatal location 0/2/CPU0Related Commands
debug egressq info
To turn on informational messages from the egress queue manager, use the debug egressq info command in EXEC mode. To disable informational messages from the egress queue manager, use the no form of this command.
debug egressq info [location node-id]
no debug egressq info [location node-id]
Syntax Description
Defaults
No default behavior or values
Command Modes
EXEC
Command History
Release 2.0
This command was introduced on the Cisco CRS-1.
Release 3.0
No modification.
Release 3.2
No modification.
Release 3.3.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
Examples
The following example shows how to enable informational messages from the egress queue manager for the entire router:
RP/0/RP0/CPU0:router# debug egressq infoThe following example shows how to enable informational messages from the egress queue manager on a specific node (the CPU node in Slot 2):
RP/0/RP0/CPU0:router# debug egressq info location 0/2/CPU0Related Commands
debug egressq interrupt
To turn on interrupt messages from the egress queue manager, use the debug egressq interrupt command in EXEC mode. To disable interrupt messages from the egress queue manager, use the no form of this command.
debug egressq interrupt [location node-id]
no debug egressq interrupt [location node-id]
Syntax Description
Defaults
No default behavior or values
Command Modes
EXEC
Command History
Release 2.0
This command was introduced on the Cisco CRS-1.
Release 3.0
No modification.
Release 3.2
No modification.
Release 3.3.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
Examples
The following example shows how to enable interrupt messages from the egress queue manager for the entire router:
RP/0/RP0/CPU0:router# debug egressq interruptThe following example shows how to enable interrupt messages from the egress queue manager on a specific node (the CPU node in Slot 2):
RP/0/RP0/CPU0:router# debug egressq interrupt location 0/2/CPU0Related Commands
debug egressq location
To turn on all messages from the egress queue manager on a specific node, use the debug egressq location command in EXEC mode. To disable all messages from the egress queue manager on a specific node, use the no form of this command.
debug egressq location node-id
no debug egressq location node-id
Syntax Description
Defaults
No default behavior or values
Command Modes
EXEC
Command History
Release 2.0
This command was introduced on the Cisco CRS-1.
Release 3.0
No modification.
Release 3.2
No modification.
Release 3.3.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
Examples
The following example shows how to enable all messages from the egress queue manager on a specific node (the CPU node in Slot 2):
RP/0/RP0/CPU0:router# debug egressq location 0/2/CPU0Related Commands
debug egressq periodic
To turn on periodic messages from the egress queue manager, use the debug egressq periodic command in EXEC mode. To disable periodic messages from the egress queue manager, use the no form of this command.
debug egressq periodic [location node-id]
no debug egressq periodic [location node-id]
Syntax Description
Defaults
No default behavior or values
Command Modes
EXEC
Command History
Release 2.0
This command was introduced on the Cisco CRS-1.
Release 3.0
No modification.
Release 3.2
No modification.
Release 3.3.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
Examples
The following example shows how to enable periodic messages from the egress queue manager for the entire router:
RP/0/RP0/CPU0:router# debug egressq periodicThe following example shows how to enable periodic messages from the egress queue manager on a specific node (the CPU node in Slot 2):
RP/0/RP0/CPU0:router# debug egressq periodic location 0/2/CPU0Related Commands
debug ether
To display debugging information about Ethernet management, use the debug ether command in EXEC mode. To disable debugging information about Ethernet management, use the no form of this command.
On the Cisco CRS-1:
debug ether {all | errors | im | info | trace} [location node-id]
no debug ether {all | errors | im | info | trace} [location node-id]
On the Cisco XR 12000 Series Router:
debug ether {trace}
no debug ether {trace}
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 Ethernet management debugging options for the entire router:
RP/0/RP0/CPU0:router# debug ether allThe following example shows how to enable Ethernet management driver informative messages on a specific node (the CPU node in Slot 2:
RP/0/RP0/CPU0:router# debug ether imRelated Commands
show controllers GigabitEthernet
Displays Gigabit Ethernet port information.
show controllers tengige
Displays 10-Gigabit Ethernet (TenGigE) port information.
debug fabricq api
To turn on debugging messages from the fabric queue API DLL, use the debug fabricq api command in EXEC mode. To disable debugging messages from the fabric queue API DLL, use the no form of this command.
debug fabricq api [errors | fatal | info] [job jobid | process word] [location node-id]
no debug fabricq api [errors | fatal | info] [job jobid | process word] [location node-id]
Syntax Description
Defaults
No default behavior or values
Command Modes
EXEC
Command History
Release 2.0
This command was introduced on the Cisco CRS-1.
Release 3.0
No modification.
Release 3.2
No modification.
Release 3.3.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
Examples
The following example shows how to enable all messages from the fabric queue API DLL for the entire router:
RP/0/RP0/CPU0:router# debug fabricq apiThe following example shows how to enable error messages from the fabric queue API DLL for a specific node (the CPU node in Slot 2):
RP/0/RP0/CPU0:router# debug fabricq api error location 0/2/CPU0Related Commands
debug fabricq asic
To turn on debugging messages from the fabric queue ASIC DLL, use the debug fabricq asic command in EXEC mode. To disable debugging messages from the fabric queue ASIC DLL, use the no form of this command.
debug fabricq asic [eio | entryexit | errors | fabric | fatal | fbp | info | init | interrupt | noreset | periodic | register | show] {job jobid | process string] [location node-id]
no debug fabricq asic [eio | entryexit | errors | fabric | fatal | fbp | info | init | interrupt | noreset | periodic | register | show] {job jobid | process string] [location node-id]
Syntax Description
Defaults
No default behavior or values
Command Modes
EXEC
Command History
Release 2.0
This command was introduced on the Cisco CRS-1.
Release 3.0
No modification.
Release 3.2
No modification.
Release 3.3.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
Examples
The following example shows how to enable all messages from the fabric queue ASIC DLL for the entire router:
RP/0/RP0/CPU0:router# debug fabricq asicThe following example shows how to enable EIO library debugging for the fabric queue ASIC EIO on for a specific node (the CPU node in Slot 2):
RP/0/RP0/CPU0:router# debug fabricq asic eio location 0/2/CPU0Related Commands
debug fabricq detail
To turn on detail debugging messages from the fabric queue, use the debug fabricq detail command in EXEC mode. To disable detail debugging messages from the fabric queue, use the no form of this command.
debug fabricq detail [job jobid | process string] [location node-id]
no debug fabricq detail [job jobid | process string] [location node-id]
Syntax Description
Defaults
No default behavior or values
Command Modes
EXEC
Command History
Release 2.0
This command was introduced on the Cisco CRS-1.
Release 3.0
No modification.
Release 3.2
No modification.
Release 3.3.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
Examples
The following example shows how to enable detail messages from the fabric queue for all nodes installed in the router:
RP/0/RP0/CPU0:router# debug fabricq detailThe following example shows how to enable detail messages from the fabric queue for a specific job (the job with the ID 234):
RP/0/RP0/CPU0:router# debug fabricq detail job 234Related Commands
debug fabricq entryexit
To turn on entry and exit messages from the fabric queue, use the debug fabricq entryexit command in EXEC mode. To disable entry and exit messages from the fabric queue, use the no form of this command.
debug fabricq entryexit [job jobid | process string] [location node-id]
no debug fabricq entryexit [job jobid | process string] [location node-id]
Syntax Description
Defaults
No default behavior or values
Command Modes
EXEC
Command History
Release 2.0
This command was introduced on the Cisco CRS-1.
Release 3.0
No modification.
Release 3.2
No modification.
Release 3.3.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
Examples
The following example shows how to enable entry and exit messages from the fabric queue for all nodes installed in the router:
RP/0/RP0/CPU0:router# debug fabricq entryexitThe following example shows how to enable entry and exit messages from the fabric queue for a specific process (the process with the ID "name"):
RP/0/RP0/CPU0:router# debug fabricq entryexit process nameRelated Commands
debug fabricq error
To turn on error messages from the fabric queue, use the debug fabricq error command in EXEC mode. To disable error messages from the fabric queue, use the no form of this command.
debug fabricq error [job jobid | process string] [location node-id]
no debug fabricq error [job jobid | process string] [location node-id]
Syntax Description
Defaults
No default behavior or values
Command Modes
EXEC
Command History
Release 2.0
This command was introduced on the Cisco CRS-1.
Release 3.0
No modification.
Release 3.2
No modification.
Release 3.3.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
Examples
The following example shows how to enable error messages from the fabric queue for all nodes installed in the router:
RP/0/RP0/CPU0:router# debug fabricq errorThe following example shows how to enable error messages from the fabric queue for a specific node (the CPU node in Slot 2):
RP/0/RP0/CPU0:router# debug fabricq error location 0/2/CPU0Related Commands
debug fabricq fabric
To turn on fabric activity messages from the fabric queue, use the debug fabricq fabric command in EXEC mode. To disable fabric activity messages from the fabric queue, use the no form of this command.
debug fabricq fabric [job jobid | process string] [location node-id]
no debug fabricq fabric [job jobid | process string] [location node-id]
Syntax Description
Defaults
No default behavior or values
Command Modes
EXEC
Command History
Release 2.0
This command was introduced on the Cisco CRS-1.
Release 3.0
No modification.
Release 3.2
No modification.
Release 3.3.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
Examples
The following example shows how to enable fabric activity messages for all nodes installed in the router:
RP/0/RP0/CPU0:router# debug fabricq fabricThe following example shows how to enable fabric activity messages from the fabric queue for a specific process (the process with the name "pid3"):
RP/0/RP0/CPU0:router# debug fabricq fabric process pid3Related Commands
debug fabricq fatal
To turn on fatal messages from the fabric queue, use the debug fabricq fatal command in EXEC mode. To disable fatal messages from the fabric queue, use the no form of this command.
debug fabricq fatal [job jobid | process string] [location node-id]
no debug fabricq fatal [job jobid | process string] [location node-id]
Syntax Description
Defaults
No default behavior or values
Command Modes
EXEC
Command History
Release 2.0
This command was introduced on the Cisco CRS-1.
Release 3.0
No modification.
Release 3.2
No modification.
Release 3.3.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
Examples
The following example shows how to enable fatal messages from the fabric queue for all nodes installed in the router:
RP/0/RP0/CPU0:router# debug fabricq fatalThe following example shows how to enable fatal messages from the fabric queue for a specific job (the job with the ID 900000):
RP/0/RP0/CPU0:router# debug fabricq fatal job 900000Related Commands
debug fabricq fbp
To turn on backpressure messages from the fabric queue, use the debug fabricq fbp command in EXEC mode. To disable backpressure messages from the fabric queue, use the no form of this command.
debug fabricq fbp [job jobid | process string] [location node-id]
no debug fabricq fbp [job jobid | process string] [location node-id]
Syntax Description
Defaults
No default behavior or values
Command Modes
EXEC
Command History
Release 2.0
This command was introduced on the Cisco CRS-1.
Release 3.0
No modification.
Release 3.2
No modification.
Release 3.3.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
Examples
The following example shows how to enable backpressure messages for all nodes installed in the router:
RP/0/RP0/CPU0:router# debug fabricq fbpThe following example shows how to enable backpressure messages from the fabric queue for a specific node (the CPU node in Slot 2):
RP/0/RP0/CPU0:router# debug fabricq fbp location 0/0/CPU0Related Commands
debug fabricq info
To display informational messages from the fabric queue, use the debug fabricq info command in EXEC mode. To disable informational messages from the fabric queue, use the no form of this command.
debug fabricq info [job jobid | process string] [location node-id]
no debug fabricq info [job jobid | process string] [location node-id]
Syntax Description
Defaults
No default behavior or values
Command Modes
EXEC
Command History
Release 2.0
This command was introduced on the Cisco CRS-1.
Release 3.0
No modification.
Release 3.2
No modification.
Release 3.3.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
Examples
The following example shows how to enable informational messages for all nodes installed in the router:
RP/0/RP0/CPU0:router# debug fabricq infoThe following example shows how to enable informational messages from the fabric queue for a specific process (the process with the name "pid8"):
RP/0/RP0/CPU0:router# debug fabricq info process pid8Related Commands
debug fabricq init
To turn on initialization messages from the fabric queue, use the debug fabricq init command in EXEC mode. To disable initialization messages from the fabric queue, use the no form of this command.
debug fabricq init [job jobid | process string] [location node-id]
no debug fabricq init [job jobid | process string] [location node-id]
Syntax Description
Defaults
No default behavior or values
Command Modes
EXEC
Command History
Release 2.0
This command was introduced on the Cisco CRS-1.
Release 3.0
No modification.
Release 3.2
No modification.
Release 3.3.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
Examples
The following example shows how to enable initialization messages for all nodes installed in the router:
RP/0/RP0/CPU0:router# debug fabricq initThe following example shows how to enable initialization messages from the fabric queue for a specific job (the job with the ID 85768):
RP/0/RP0/CPU0:router# debug fabricq init job 85768Related Commands
debug fabricq location
To turn on all messages from the fabric queue for a specific node, use the debug fabricq location command in EXEC mode. To disable all messages from the fabric queue for a specific node, use the no form of this command.
debug fabricq location node-id
no debug fabricq location node-id
Syntax Description
Defaults
No default behavior or values
Command Modes
EXEC
Command History
Release 2.0
This command was introduced on the Cisco CRS-1.
Release 3.0
No modification.
Release 3.2
No modification.
Release 3.3.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
Examples
The following example shows how to enable all messages from the fabric queue for a specific node (the CPU node in Slot 0):
RP/0/RP0/CPU0:router# debug fabricq location 0/0/CPU0Related Commands
debug fabricq periodic
To turn on periodic activity messages from the fabric queue, use the debug fabricq periodic command in EXEC mode. To disable all periodic activity messages from the fabric queue, use the no form of this command.
debug fabricq periodic [job jobid | process string] [location node-id]
no debug fabricq periodic [job jobid | process string] [location node-id]
Syntax Description
Defaults
No default behavior or values
Command Modes
EXEC
Command History
Release 2.0
This command was introduced on the Cisco CRS-1.
Release 3.0
No modification.
Release 3.2
No modification.
Release 3.3.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
Examples
The following example shows how to enable periodic activity messages for all nodes installed in the router:
RP/0/RP0/CPU0:router# debug fabricq periodicThe following example shows how to enable periodic activity messages from the fabric queue for a specific process (the process with the name "pid25"):
RP/0/RP0/CPU0:router# debug fabricq periodic process pid25Related Commands
debug fcram
To enable debugging information about the Fast Cycle Random Access Memory (FCRAM) in ASICs, use the debug fcram command in EXEC mode. To disable debugging information about the FCRAM in ASICs, use the no form of this command.
debug fcram {chkpt | entryexit | errors | events | fatal | info}
no debug fcram {chkpt | entryexit | errors | events | fatal | info}
Syntax Description
Defaults
No default behavior or values
Command Modes
EXEC
Command History
Release 2.0
This command was introduced on the Cisco CRS-1.
Release 3.0
No modification.
Release 3.2
No modification.
Release 3.3.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
Examples
The following example shows how to enable checkpointing messages from the FCRAM in ASICs:
RP/0/RP0/CPU0:router# debug fcram chkptThe following example shows how to enable fatal messages from the FCRAM in ASICs:
RP/0/RP0/CPU0:router# debug fcram fataldebug generic
To enable generic debugging for the entire router, use the debug generic command in EXEC mode. To disable generic debugging for the entire router, use the no form of this command.
debug generic
no debug generic
Syntax Description
This command has no arguments or keywords.
Defaults
No default behavior or values
Command Modes
EXEC
Command History
Release 2.0
This command was introduced on the Cisco CRS-1.
Release 3.0
No modification.
Release 3.2
This command was first supported on the Cisco XR 12000 Series Router.
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 generic debugging for the entire router:
RP/0/RP0/CPU0:router# debug genericdebug gsp-em
To display debugging information about Gigabit Switch Platform (GSP) Ethernet support, use the debug gsp-em command in EXEC mode. To disable debugging information about GSP Ethernet support, use the no form of this command.
debug gsp-em {enet-addr | enet-error | enet-replay | enet-rx | enet-rx-hi | enet-rx-lo | enet-states | enet-tx | enet-tx-hi | enet-tx-lo} [location node-id]
no debug gsp-em {enet-addr | enet-error | enet-replay | enet-rx | enet-rx-hi | enet-rx-lo | enet-states | enet-tx | enet-tx-hi | enet-tx-lo} [location node-id]
Syntax Description
Defaults
No default behavior or values
Command Modes
EXEC
Command History
Release 2.0
This command was introduced on the Cisco CRS-1.
Release 3.0
No modification.
Release 3.2
No modification.
Release 3.3.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
Examples
The following example shows how display information pertaining to the setting and unsetting of the Ethernet address for all nodes installed in the router:
RP/0/RP0/CPU0:router# debug gsp-em enet-addrThe following example shows how to display information pertaining to low Ethernet receive streams for a specific node (the CPU node in Slot 2):
RP/0/RP0/CPU0:router# debug gsp-em enet-rx-lo location 0/2/CPU0debug gsp-fab
To display debugging information related to Gigabit Switch Platform (GSP) fabric support, use the debug gsp-em command in EXEC mode. To disable debugging information related to GSP fabric support, use the no form of this command.
debug gsp-fab {fab-addr | fab-error | fab-replay | fab-rx | fab-rx-frr | fab-rx-hi | fab-rx-lo | fab-states | fab-tx | fab-tx-frr | fab-tx-hi | fab-tx-lo} [location node-id]
no debug gsp-fab {fab-addr | fab-error | fab-replay | fab-rx | fab-rx-frr | fab-rx-hi | fab-rx-lo | fab-states | fab-tx | fab-tx-frr | fab-tx-hi | fab-tx-lo} [location node-id]
Syntax Description
Defaults
No default behavior or values
Command Modes
EXEC
Command History
Release 2.0
This command was introduced on the Cisco CRS-1.
Release 3.0
No modification.
Release 3.2
No modification.
Release 3.3.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
Examples
The following example shows how to display information related to the setting and unsetting of the fabric address for all nodes installed in the router:
RP/0/RP0/CPU0:router# debug gsp-fab fab-addrThe following example shows how to enable the tracking of fabric DLL errors on a specific node (the CPU node in Slot 2):
RP/0/RP0/CPU0:router# debug gsp-fab fab-error location 0/2/CPU0debug ingressq
To display debugging information related to the ingress queue manager for all nodes installed in the router, use the debug ingressq command in EXEC mode. To disable debugging information related to the ingress queue manager for all nodes installed in the router, use the no form of this command.
debug ingressq
no debug ingressq
Syntax Description
This command has no arguments or keywords.
Defaults
No default behavior or values
Command Modes
EXEC
Command History
Release 2.0
This command was introduced on the Cisco CRS-1.
Release 3.0
No modification.
Release 3.2
No modification.
Release 3.3.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
Examples
The following example shows how to display information related to the ingress queue manager for all nodes installed in the router:
RP/0/RP0/CPU0:router# debug ingressqRelated Commands
debug ingressq api
To turn on debugging messages from the ingress queue API DLL, use the debug ingressq api command in EXEC mode. To disable debugging messages from the ingress queue API DLL, use the no form of this command.
debug ingressq api [errors | fatal | info] [location node-id]
no debug ingressq api [errors | fatal | info] [location node-id]
Syntax Description
Defaults
No default behavior or values
Command Modes
EXEC
Command History
Release 2.0
This command was introduced on the Cisco CRS-1.
Release 3.0
No modification.
Release 3.2
No modification.
Release 3.3.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
Examples
The following example shows how to enable all messages from the ingress queue API DLL on all nodes installed in the router:
RP/0/RP0/CPU0:router# debug ingressq apiThe following example shows how to enable error messages from the ingress queue API DLL on a specific node (the CPU in Slot 0):
RP/0/RP0/CPU0:router# debug ingressq api location 0/0/CPU0Related Commands
Displays information related to the ingress queue manager for all nodes installed in the router.
show controllers ingressq statistics
Displays ingress queue manager statistics.
debug ingressq asic
To enable debugging messages from the ingress queue ASIC DLL, use the debug ingressq asic command in EXEC mode. To disable debugging messages from the ingress queue ASIC DLL, use the no form of this command.
debug ingressq asic [cdma | detail | eio | error | fatal | gaspp | info | intr | pio] [location node-id]
no debug ingressq asic [cdma | detail | eio | error | fatal | gaspp | info | intr | pio] [location node-id]
Syntax Description
Defaults
No default behavior or values
Command Modes
EXEC
Command History
Release 2.0
This command was introduced on the Cisco CRS-1.
Release 3.0
No modification.
Release 3.2
No modification.
Release 3.3.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
Examples
The following example shows how to enable all messages from the ingress queue ASIC DLL on all nodes installed in the router:
RP/0/RP0/CPU0:router# debug ingressq asicThe following example shows how to enable messages from the ingress queue ASIC DLL on a specific node (the CPU in Slot 2):
RP/0/RP0/CPU0:router# debug ingressq asic location 0/2/CPU0Related Commands
Displays information related to the ingress queue manager for all nodes installed in the router.
show controllers ingressq statistics
Displays ingress queue manager statistics.
debug ingressq detail
To turn on detailed debug messages from the ingress queue, use the debug ingressq detail command in EXEC mode. To disable detailed debug messages from the ingress queue, use the no form of this command.
debug ingressq detail [location node-id]
no debug ingressq detail [location node-id]
Syntax Description
Defaults
No default behavior or values
Command Modes
EXEC
Command History
Release 2.0
This command was introduced on the Cisco CRS-1.
Release 3.0
No modification.
Release 3.2
No modification.
Release 3.3.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
Examples
The following example shows how to enable detailed debug messages from the ingress queue on all nodes installed in the router:
RP/0/RP0/CPU0:router# debug ingressq detailThe following example shows how to enable detailed debug messages from the ingress queue on a specific node (the CPU in Slot 0):
RP/0/RP0/CPU0:router# debug ingressq detail location 0/0/CPU0Related Commands
Displays information related to the ingress queue manager for all nodes installed in the router.
show controllers ingressq statistics
Displays ingress queue manager statistics.
debug ingressq entryexit
To turn on entry and exit messages from the ingress queue, use the debug ingressq entryexit command in EXEC mode. To disable entry and exit messages from the ingress queue, use the no form of this command.
debug ingressq entryexit [location node-id]
no debug ingressq entryexit [location node-id]
Syntax Description
Defaults
No default behavior or values
Command Modes
EXEC
Command History
Release 2.0
This command was introduced on the Cisco CRS-1.
Release 3.0
No modification.
Release 3.2
No modification.
Release 3.3.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
Examples
The following example shows how to enable entry and exit messages from the ingress queue on all nodes installed in the router:
RP/0/RP0/CPU0:router# debug ingressq entryexitThe following example shows how to enable entry and exit messages from the ingress queue on a specific node (the CPU in Slot 2):
RP/0/RP0/CPU0:router# debug ingressq entryexit location 0/2/CPU0Related Commands
Displays information related to the ingress queue manager for all nodes installed in the router.
show controllers ingressq statistics
Displays ingress queue manager statistics.
debug ingressq error
To turn on error messages from the ingress queue, use the debug ingressq error command in EXEC mode. To disable error messages from the ingress queue, use the no form of this command.
debug ingressq error [location node-id]
no debug ingressq error [location node-id]
Syntax Description
Defaults
No default behavior or values
Command Modes
EXEC
Command History
Release 2.0
This command was introduced on the Cisco CRS-1.
Release 3.0
No modification.
Release 3.2
No modification.
Release 3.3.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
Examples
The following example shows how to enable error messages from the ingress queue on all nodes installed in the router:
RP/0/RP0/CPU0:router# debug ingressq errorThe following example shows how to enable error messages from the ingress queue on a specific node (the CPU in Slot 2):
RP/0/RP0/CPU0:router# debug ingressq error location 0/2/CPU0Related Commands
Displays information related to the ingress queue manager for all nodes installed in the router.
show controllers ingressq statistics
Displays ingress queue manager statistics.
debug ingressq fatal
To turn on fatal messages from the ingress queue, use the debug ingressq fatal command in EXEC mode. To disable fabric messages from the ingress queue, use the no form of this command.
debug ingressq fatal [location node-id]
no debug ingressq fatal [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 fatal messages from the ingress queue on all nodes installed in the router:
RP/0/RP0/CPU0:router# debug ingressq fatalThe following example shows how to enable fatal messages from the ingress queue on a specific node (the CPU in Slot 2):
RP/0/RP0/CPU0:router# debug ingressq fatal location 0/2/CPU0Related Commands
Enter the show platform command to see the location of all nodes installed in the router.