-
Cisco IOS XR Interface and Hardware Component Debug Command Reference, Release 3.4
-
Book-level PDF: Cisco IOS XR Interface and Hardware Component Debug Command Reference
-
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
-
ATM 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
-
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
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 [server] [job jobid | process string] [location node-id]
no debug cctl [server] [job jobid | process string] [location node-id]
Syntax Description
Defaults
No default behavior or values
Command Modes
Admin 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 debugging information for the complete functionality of Chassis Control Driver:
RP/0/RP0/CPU0:router(admin)# debug cctl serverdebug cetftp
To display debugging information about the CE-TFTP server, use the debug cetftp command in administrative 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
Administrative 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 debugging information for the CE-TFTP server:
RP/0/RP0/CPU0:router# adminRP/0/RP0/CPU0:router(admin)# debug cetftp allThe following example shows how to enable debugging information for CE-TFTP errors from internal functions.
RP/0/RP0/CPU0:router# adminRP/0/RP0/CPU0:router(admin)# 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
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
Release 3.3.0
This command was introduced on the Cisco CRS-1.
Release 3.4.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 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
Release 3.3.0
This command was introduced on the Cisco CRS-1.
Release 3.4.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 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
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
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
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
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
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
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 [api [errors | fatal | info] [job jobid | process word] | cdma | detail | eio | entryexit | error | fatal | info | interrupt | periodic] [location node-id]
no debug egressq [api [errors | fatal | info] [job jobid | process word] | cdma | detail | eio | entryexit | error | fatal | info | interrupt | periodic] [location node-id]
Syntax Description
Defaults
Enter the debug egressq command without including any of the optional syntax to turn on all messages from the egress queue manager for the entire router.
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 turn all messages from the egress queue manager:
RP/0/RP0/CPU0:router# debug egressqRelated 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.
debug ether {all | errors | im | info | trace} [location node-id]
no debug ether {all | errors | im | info | trace} [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 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
To turn on debugging messages from the fabric queue, use the debug fabricq command in EXEC mode. To disable debugging messages from the fabric queue, use the no form of this command.
debug fabricq [asic [eio | entryexit | errors | fabric | fatal | fbp | info | init | interrupt | noreset | periodic | register | show] | api | detail | entryexit | error | fabric | fatal | fbp | info | init | periodic] [job jobid | process string] [location node-id]
no debug fabricq [asic [eio | entryexit | errors | fabric | fatal | fbp | info | init | interrupt | noreset | periodic | register | show] | api | detail | entryexit | error | fabric | fatal | fbp | info | init | periodic] [job jobid | process string] [location node-id]
Syntax Description
Defaults
Enter the debug fabricq command without including any of the optional syntax to turn on all turn on debugging messages from the fabric queue for the entire router.
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 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 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
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
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
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
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
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
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
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
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
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
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
Release 3.3.0
This command was introduced on the Cisco CRS-1.
Release 3.4.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 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
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 fabric
To turn on fabric messages from the ingress queue, use the debug ingressq fabric command in EXEC mode. To disable fabric messages from the ingress queue, use the no form of this command.
debug ingressq fabric [location node-id]
no debug ingressq fabric [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 fabric messages from the ingress queue on all nodes installed in the router:
RP/0/RP0/CPU0:router# debug ingressq fabricThe following example shows how to enable fabric messages from the ingress queue on a specific node (the CPU in Slot 2):
RP/0/RP0/CPU0:router# debug ingressq fabric 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 info
To turn on informational messages from the ingress queue, use the debug ingressq info command in EXEC mode. To disable informational messages from the ingress queue, use the no form of this command.
debug ingressq info [location node-id]
no debug ingressq info [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 informational messages from the ingress queue on all nodes installed in the router:
RP/0/RP0/CPU0:router# debug ingressq infoThe following example shows how to enable informational messages from the ingress queue on a specific node (the CPU in Slot 2):
RP/0/RP0/CPU0:router# debug ingressq info 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 location
To display debugging information related to the ingress queue manager on a specific node, use the debug ingressq location command in EXEC mode. To disable debugging information related to the ingress queue manager on a specific node, use the no form of this command.
debug ingressq location node-id
no debug ingressq 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 display information related to the ingress queue manager for a specific node (the CPU0 node installed in Slot 2):
RP/0/RP0/CPU0:router# debug ingressq 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 pfilter-ea
To turn on debugging messages related to the pfilter electrical absorption (EA), use the debug pfilter-ea command in EXEC mode. To turn off debugging messages that are related to the pfilter EA, use the no form of this command.
On the Cisco CRS-1:
debug pfilter-ea {all | errors | info | rlb} [location node-id]
no debug pfilter-ea {all | errors | info | rlb} [location node-id]
On the Cisco XR 12000 Series Router:
debug pfilter-ea {all | detail | errors | info}
no debug pfilter-ea {all | detail | errors | info}
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 turn on error messages related to the pfilter EA for all nodes installed in the router:
RP/0/RP0/CPU0:router# debug pfilter-ea allThe following example shows how to turn on all error messages related to the pfilter EA for a specific node (the CPU in Slot 2):
RP/0/RP0/CPU0:router# debug pfilter-ea all location 0/2/CPU0Related Commands
Turns on detailed pfilter EA debug messages for a specific node, or for all nodes installed in the router.
debug pladrv
To enable physical layer interface module (PLIM) link ASIC debugging on a router, use the debug pladrv command in EXEC mode. To disable PLIM link ASIC debugging on a router, use the no form of this command.
debug pladrv [api [error | info [job jobid | process string] | job jobid | process string| trace [job jobid | process string]] | eio | error | info | int | memory | periodic | trace] [location node-id]
no debug pladrv api [api [error | info [job jobid | process string] | job jobid | process string| trace [job jobid | process string]] | eio | error | info | int | memory | periodic | trace] [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 display information related to platform client API calls on the PLIM link ASIC for all nodes installed in a router:
RP/0/RP0/CPU0:router# debug pladrv apiLC/0/2/CPU0:Jun 28 19:16:07 : pla_server[188]: --> pla_update_rmnLC/0/2/CPU0:Jun 28 19:16:07 : pla_server[188]: -->pla_read_rmnLC/0/2/CPU0:Jun 28 19:16:07 : pla_server[188]: --> pla_update_rmnLC/0/2/CPU0:Jun 28 19:16:07 : pla_server[188]: -->pla_read_rmnLC/0/2/CPU0:Jun 28 19:16:07 : pla_server[188]: --> pla_update_rmnLC/0/2/CPU0:Jun 28 19:16:07 : pla_server[188]: -->pla_read_rmnLC/0/2/CPU0:Jun 28 19:16:07 : pla_server[188]: --> pla_update_rmnLC/0/2/CPU0:Jun 28 19:16:07 : pla_server[188]: -->pla_read_rmnLC/0/2/CPU0:Jun 28 19:16:17 : pla_server[188]: entering pla_periodic_handlerLC/0/2/CPU0:Jun 28 19:16:17 : pla_server[188]: pla_periodic_handler: pla peiodictimerLC/0/2/CPU0:Jun 28 19:16:17 : pla_server[188]: -->pla_update_gb_statsLC/0/2/CPU0:Jun 28 19:16:17 : pla_server[188]: --> pla_update_rmnLC/0/2/CPU0:Jun 28 19:16:17 : pla_server[188]: -->pla_read_rmnThe following example shows how to display information related to PLA client API calls on the PLIM link ASIC for a specific node (the CPU in Slot 2):
RP/0/RP0/CPU0:router# debug pladrv api trace location 0/2/CPU0debug plim
To enable physical layer interface module (PLIM) debugging operations, use the debug plim command in EXEC mode. To disable PLIM debugging operations, use the no form of this command.
On the Cisco CRS-1:
debug plim {all | eio | errors | events | gaspp | im | info | mapping | operations | periodic | pio | trace} [job jobid | process string} [location node-id]
no debug plim {all | eio | errors | events | gaspp | im | info | mapping | operations | periodic | pio | trace} [job jobid | process string] [location node-id]
On the Cisco XR 12000 Series Router:
debug plim {all | eio | errors | events | gaspp | ge-4p-vlan {all |errors | info | periodic} | im | info | jdam {all | rxtx-buf | sram | tcam | tx-port-map | vlan} | mapping | operations | periodic | pio | trace} [location node-id]
no debug plim {all | eio | errors | events | gaspp | ge-4p-vlan {all |errors | info | periodic} | im | info | jdam {all | rxtx-buf | sram | tcam | tx-port-map | vlan} | mapping | operations | periodic | pio | trace} [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 PLIM debugging options on all nodes installed in a router:
RP/0/RP0/CPU0:router# debug plim allThe following example shows how to enable verbose PLIM tracing on a specific job (the job with the
ID 205):RP/0/RP0/CPU0:router# debug plim trace job 205debug tcam-mgr cam entry update
To turn on TCAM manager cam entry update debug messages for all nodes installed in the router, or for a specific node, use the debug tcam-mgr errors command in EXEC mode. To disable TCAM manager error condition debug messages for all nodes installed in the router, use the no form of this command.
debug tcam-mgr cam entry update [location node-id]
no debug tcam-mgr cam entry update [location node-id]
Syntax Description
Defaults
No default behavior or values
Command Modes
EXEC
Command History
Release 3.3.0
This command was introduced on the Cisco CRS-1.
Release 3.4.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 cam entry upate debug messages for all nodes installed in a router:
RP/0/RP0/CPU0:router# debug tcam-mgr cam entry updateThe following example shows how to enable cam entry update debug messages for a specific node (the CPU0 node in Slot 2):
RP/0/RP0/CPU0:router# debug tcam-mgr cam entry update location 0/2/CPU0debug tcam-mgr chkpt
To turn on TCAM manager checkpointing operations debug messages, use the debug tcam-mgr chkpt command in EXEC mode. To disable TCAM manager checkpointing operations content or error debug messages, use the no form of this command.
debug tcam-mgr chkpt {content | errors} [location node-id]
no debug tcam-mgr chkpt {content | errors} [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 TCAM manager checkpointing operations content messages for all nodes installed in a router:
RP/0/RP0/CPU0:router# debug tcam-mgr chkpt contentThe following example shows how to enable TCAM manager checkpointing operations error messages for a specific node (the CPU0 node in Slot 2):
RP/0/RP0/CPU0:router# debug tcam-mgr chkpt error location 0/2/CPU0debug tcam-mgr client
To turn on TCAM manager client dynamic link library (DLL) debug messages, use the debug tcam-mgr client command in EXEC mode. To disable TCAM manager client DLL debug messages, use the no form of this command.
debug tcam-mgr client {errors | info | ipc | notif |persistent-errors} [location node-id]
no debug tcam-mgr client {errors | info | ipc | notif |persistent-errors} [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 informational messages from the TCAM manager client DLL for all nodes installed in a router:
RP/0/RP0/CPU0:router# debug tcam-mgr client infoThe following example shows how to enable persistent TCAM manager error messages for a specific node (the CPU0 node in Slot 2):
RP/0/RP0/CPU0:router# debug tcam-mgr client persistent-errors location 0/2/CPU0debug tcam-mgr errors
To turn on TCAM manager error condition debug messages for all nodes installed in the router, or for a specific node, use the debug tcam-mgr errors command in EXEC mode. To disable TCAM manager error condition debug messages for all nodes installed in the router, use the no form of this command.
debug tcam-mgr errors [location node-id]
no debug tcam-mgr errors [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 error condition debug messages for all nodes installed in a router:
RP/0/RP0/CPU0:router# debug tcam-mgr errorsThe following example shows how to enable error condition debug messages for a specific node (the CPU0 node in Slot 2):
RP/0/RP0/CPU0:router# debug tcam-mgr errors location 0/2/CPU0debug tcam-mgr events
To turn on TCAM manager non-resource allocation event messages, use the debug tcam-mgr events command in EXEC mode. To disable TCAM manager non-resource allocation event messages, use the no form of this command.
debug tcam-mgr events [location node-id]
no debug tcam-mgr events [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 TCAM manager non-resource allocation event messages for all nodes installed in a router:
RP/0/RP0/CPU0:router# debug tcam-mgr eventsThe following example shows how to enable TCAM manager non-resource allocation event messages for a specific node (the CPU0 node in Slot 2):
RP/0/RP0/CPU0:router# debug tcam-mgr events location 0/2/CPU0debug tcam-mgr prefix-compress
To turn on TCAM manager IPv6 prefix compression debug messages, use the debug tcam-mgr prefix-compress command in EXEC mode. To disable TCAM manager IPv6 prefix compression debug messages, use the no form of this command.
debug tcam-mgr prefix-compress {errors | incremental-update-table | processing | profiling | result | trace} [location node-id]
no debug tcam-mgr prefix-compress {errors | incremental-update-table | processing | profiling | result | trace} [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 TCAM IPv6 prefix compression error messages for all nodes installed in a router:
RP/0/RP0/CPU0:router# debug tcam-mgr prefix-compress errorsThe following example shows how to enable detailed TCAM IPv6 prefix compression trace messages for a specific node (the CPU0 node in Slot 2):
RP/0/RP0/CPU0:router# debug tcam-mgr prefix-compress trace location 0/2/CPU0debug tcam-mgr processing
To turn on detailed TCAM manager event processing debug messages, use the debug tcam-mgr processing command in EXEC mode. To disable detailed TCAM manager event processing debug messages, use the no form of this command.
debug tcam-mgr processing [location node-id]
no debug tcam-mgr processing [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 detailed TCAM manager event processing debug messages for all nodes installed in a router:
RP/0/RP0/CPU0:router# debug tcam-mgr processing errorsThe following example shows how to enable detailed TCAM manager event processing debug messages for a specific node (the CPU0 node in Slot 2):
RP/0/RP0/CPU0:router# debug tcam-mgr processing location 0/2/CPU0debug tcam-mgr resalloc
To turn on TCAM manager resource allocation event messages, use the debug tcam-mgr resalloc command in EXEC mode. To disable TCAM manager resource allocation event messages, use the no form of this command.
debug tcam-mgr resalloc [location node-id]
no debug tcam-mgr resalloc [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 TCAM manager resource allocation event messages for all nodes installed in a router:
RP/0/RP0/CPU0:router# debug tcam-mgr resallocThe following example shows how to enable TCAM manager resource allocation event messages for a specific node (the CPU0 node in Slot 2):
RP/0/RP0/CPU0:router# debug tcam-mgr resalloc location 0/2/CPU0debug tcam-mgr rlb
To turn on TCAM manager Range Logic Block (RLB) debug messages, use the debug tcam-mgr rlb command in EXEC mode. To disable TCAM manager RLB debug messages, use the no form of this command.
debug tcam-mgr rlb {errors | events | trace} [location node-id]
no debug tcam-mgr rlb {errors | events | trace} [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 TCAM RLB debug error condition messages for all nodes installed in a router:
RP/0/RP0/CPU0:router# debug tcam-mgr processing errorsThe following example shows how to enable TCAM RLB debug error condition messages for a specific node (the CPU0 node in Slot 2):
RP/0/RP0/CPU0:router# debug tcam-mgr processing location 0/2/CPU0debug tcam-mgr scrub
To scrub TCAM manager debug messages, use the debug tcam-mgr scrub command in EXEC mode. To disable detailed TCAM manager function level traces, use the no form of this command.
debug tcam-mgr scrub [location node-id]
no debug tcam-mgr scrub [location node-id]
Syntax Description
Defaults
No default behavior or values
Command Modes
EXEC
Command History
Release 3.3.0
This command was introduced on the Cisco CRS-1.
Release 3.4.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 scrub TCAM manager debug messages for all nodes installed in a router:
RP/0/RP0/CPU0:router# debug tcam-mgr scrubThe following example shows how toscrub TCAM manager debug messages for a specific node (the CPU0 node in Slot 2):
RP/0/RP0/CPU0:router# debug tcam-mgr scrub location 0/2/CPU0debug tcam-mgr trace
To turn on detailed TCAM manager function level traces, use the debug tcam-mgr trace command in EXEC mode. To disable detailed TCAM manager function level traces, use the no form of this command.
debug tcam-mgr trace [location node-id]
no debug tcam-mgr trace [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 detailed TCAM manager function level traces for all nodes installed in a router:
RP/0/RP0/CPU0:router# debug tcam-mgr traceThe following example shows how to enable detailed TCAM manager function level traces for a specific node (the CPU0 node in Slot 2):
RP/0/RP0/CPU0:router# debug tcam-mgr trace location 0/2/CPU0
Enter the show platform command to see the location of all nodes installed in the router.