Table Of Contents
ASIC Driver Debug Commands on
Cisco IOS XR Software
debug asic-scan
debug cctl
debug cetftp
debug cpuctrl api
debug cpuctrl asic-error
debug cpuctrl asic-info
debug cpuctrl detail
debug cpuctrl entryexit
debug cpuctrl error
debug cpuctrl fatal
debug cpuctrl info
debug cpuctrl location
debug egressq
debug ether
debug fabricq
debug fcram
debug generic
debug gsp-em
debug gsp-fab
debug ingressq
debug ingressq api
debug ingressq asic
debug ingressq detail
debug ingressq entryexit
debug ingressq error
debug ingressq fatal
debug ingressq fabric
debug ingressq info
debug ingressq location
debug pfilter-ea
debug pladrv
debug plim
debug tcam-mgr cam entry update
debug tcam-mgr chkpt
debug tcam-mgr client
debug tcam-mgr errors
debug tcam-mgr events
debug tcam-mgr prefix-compress
debug tcam-mgr processing
debug tcam-mgr resalloc
debug tcam-mgr rlb
debug tcam-mgr scrub
debug tcam-mgr trace
ASIC Driver Debug Commands on
Cisco IOS XR Software
This module describes the commands that provide useful information for debugging the ASIC 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
level level
|
(Optional) Specifies the level of output to display. Range is from 1 through 3, where level 3 provides the most detail.
|
error
|
(Optional) Displays information about ASIC scan errors.
|
trace
|
(Optional) Displays information about ASIC scan trace.
|
xsvf
|
(Optional) Displays information about the ASIC scan XSVF.
|
lib
|
(Optional) Displays application programming interface (API) library debugging flags.
|
location node-id
|
(Optional) Displays ASIC scan information for a specific node.
The node-id argument is expressed in the rack/slot/module notation.
Note  Enter the show platform command to see the location of all nodes installed in the router.
|
Defaults
No default behavior or values
Command Modes
EXEC
Command History
Release
|
Modification
|
Release 2.0
|
This command was introduced on the Cisco CRS-1.
|
Release 3.0
|
No modification.
|
Release 3.2
|
No modification.
|
Release 3.3.0
|
No modification.
|
Release 3.4.0
|
No modification.
|
Release 3.5.0
|
No modification.
|
Usage Guidelines
To use this command, you must be in a user group associated with a task group that includes the proper task IDs. For detailed information about user groups and task IDs, see the Configuring AAA Services on Cisco IOS XR Software module of the Cisco IOS XR System Security Configuration Guide.
Debugging output is assigned high priority in the CPU process and, therefore, can affect system performance. For more information about the impact on system performance when using debug commands, refer to Using Debug Commands on Cisco IOS XR Software.
Task ID
Task ID
|
Operations
|
drivers
|
read
|
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-scan
The 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 2
The 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/CPU0
debug 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
server
|
(Optional) Displays information about the cBus controller (CCTL) low water mark (LWM) server.
|
job jobid
|
(Optional) Displays chassis control driver functionality for a specific job. Range is from 0 through 4294967295.
|
process string
|
(Optional) Displays chassis control driver functionality for a specific process. Replace the string argument with a process ID or name.
|
location node-id
|
(Optional) Displays chassis control driver functionality for a specific node.
The node-id argument is expressed in the rack/slot/module notation.
Note Enter the show platform command to see the location of all nodes installed in the router.
|
Defaults
No default behavior or values
Command Modes
Admin EXEC
Command History
Release
|
Modification
|
Release 2.0
|
This command was introduced on the Cisco CRS-1.
|
Release 3.0
|
No modification.
|
Release 3.2
|
No modification.
|
Release 3.3.0
|
No modification.
|
Release 3.4.0
|
The following keywords were removed from the debug cctl command syntax:
•alarm
•all
•api
•edm
•errors
•helperfunc
•ideeprom
•internalapi
•monitor
•obfl
•reset
•trap
|
Release 3.5.0
|
No modification.
|
Usage Guidelines
To use this command, you must be in a user group associated with a task group that includes the proper task IDs. For detailed information about user groups and task IDs, see the Configuring AAA Services on Cisco IOS XR Software module of the Cisco IOS XR System Security Configuration Guide.
Debugging output is assigned high priority in the CPU process and, therefore, can affect system performance. For more information about the impact on system performance when using debug commands, refer to Using Debug Commands on Cisco IOS XR Software.
Task ID
Task ID
|
Operations
|
system
|
read
|
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 server
debug 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
all
|
Turns on all the debug options for the CE-TFTP server.
|
arp
|
Displays information about the CE-TFTP ARP interface.
|
brief
|
Displays brief CE-TFTP information. This is equivalent to logging.
|
cfg
|
Displays information about the CE-TFTP CFG interface.
|
detail
|
Displays information about the CE-TFTP. This is equivalent to tracing.
|
enet
|
Displays information about the control Ethernet and IP layer of the CE-TFTP interface.
|
error
|
Displays information about CE-TFTP errors from internal functions.
|
ip
|
Displays information about the CE-TFTP IP interface.
|
server
|
Displays information about the CE-TFTP server interface.
|
timer
|
Displays information about the CE-TFTP TIMER interface.
|
Defaults
No default behavior or values
Command Modes
Administrative EXEC
Command History
Release
|
Modification
|
Release 2.0
|
This command was introduced on the Cisco CRS-1.
|
Release 3.0
|
No modification.
|
Release 3.2
|
No modification.
|
Release 3.3.0
|
No modification.
|
Release 3.4.0
|
The debug cetftp command was moved from EXEC mode to administrative EXEC mode.
|
Release 3.5.0
|
No modification.
|
Usage Guidelines
To use this command, you must be in a user group associated with a task group that includes the proper task IDs. For detailed information about user groups and task IDs, see the Configuring AAA Services on Cisco IOS XR Software module of the Cisco IOS XR System Security Configuration Guide.
Debugging output is assigned high priority in the CPU process and, therefore, can affect system performance. For more information about the impact on system performance when using debug commands, refer to Using Debug Commands on Cisco IOS XR Software.
Task ID
Task ID
|
Operations
|
root-system
|
read
|
Examples
The following example shows how to enable debugging information for the CE-TFTP server:
RP/0/RP0/CPU0:router# admin
RP/0/RP0/CPU0:router(admin)# debug cetftp all
The following example shows how to enable debugging information for CE-TFTP errors from internal functions.
RP/0/RP0/CPU0:router# admin
RP/0/RP0/CPU0:router(admin)# debug cetftp error
Related Commands
Command
|
Description
|
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
cdma
|
(Optional) Turns on CDMA debugging messages from the Cpuctrl driver API DLL.
|
connect
|
(Optional) Turns on connect debugging messages from the Cpuctrl driver API DLL.
|
errors
|
(Optional) Turns on error debugging messages from the Cpuctrl driver API DLL.
|
fatal
|
(Optional) Turns on fatal debugging messages from the Cpuctrl driver API DLL.
|
info
|
(Optional) Turns on info debugging messages from the Cpuctrl driver API DLL.
|
pdma
|
(Optional) Turns on PDMA debugging messages from the Cpuctrl Driver API DLL.
|
pio
|
(Optional) Turns on PIO debugging messages from the Cpuctrl Driver API DLL.
|
job jobid
|
(Optional) Specifies a job. Range is from 0 through 4294967295.
|
process string
|
(Optional) Specifies a process name or ID.
|
location node-id
|
(Optional) Specifies a node on which to turn on all debugging messages for the CPU driver API DLL.
The node-id argument is expressed in the rack/slot/module notation.
Note Enter the show platform command to see the location of all nodes installed in the router.
|
Defaults
No default behavior or values
Command Modes
EXEC
Command History
Release
|
Modification
|
Release 2.0
|
This command was introduced on the Cisco CRS-1.
|
Release 3.0
|
No modification.
|
Release 3.2
|
No modification.
|
Release 3.3.0
|
No modification.
|
Release 3.4.0
|
No modification.
|
Release 3.5.0
|
No modification.
|
Usage Guidelines
To use this command, you must be in a user group associated with a task group that includes the proper task IDs. For detailed information about user groups and task IDs, see the Configuring AAA Services on Cisco IOS XR Software module of the Cisco IOS XR System Security Configuration Guide.
Debugging output is assigned high priority in the CPU process and, therefore, can affect system performance. For more information about the impact on system performance when using debug commands, refer to Using Debug Commands on Cisco IOS XR Software.
Task ID
Task ID
|
Operations
|
drivers
|
read, write
|
Examples
The following example shows how to enable debugging information for the CPU controller driver API DLL:
RP/0/RP0/CPU0:router# debug cpuctrl api
The 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 200
Related Commands
Command
|
Description
|
debug cpuctrl asic-error
|
Turns on asic error debugging messages for the CPU driver.
|
debug cpuctrl asic-info
|
Turns on asic info debugging messages for the CPU driver.
|
debug cpuctrl asic-error
|
Turns on all debugging messages from the CPU controller driver.
|
debug cpuctrl entryexit
|
Turns on all entry and exit messages from CPU controller driver.
|
debug cpuctrl error
|
Turns on error messages from the CPU controller.
|
debug cpuctrl fatal
|
Turns on fatal messages from CPU controller driver.
|
debug cpuctrl info
|
Turns on informational messages from the CPU controller.
|
debug cpuctrl location
|
Turns on all debugging messages from the CPU controller driver on a specific node.
|
show controllers cpuctrl cdma
|
Displays information about the CPU controller Code Division Multiplex Access (CDMA) engine.
|
show controllers cpuctrl clients
|
Displays information about all CPU controller clients on the router, or for specific CPU controller clients.
|
show controllers cpuctrl devices
|
Displays information about the CPU controller devices on the router.
|
show controllers cpuctrl internal
|
Displays information about the internal CPU controller.
|
show controllers cpuctrl ports
|
Displays port information for the specified CPU controller ASIC.
|
show controllers cpuctrl summary
|
Displays summarized information about all CPU controller ASICs on the router or on a specific node.
|
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
job jobid
|
(Optional) Specifies a job. Range is from 0 through 4294967295.
|
process string
|
(Optional) Specifies a process name or ID.
|
location node-id
|
(Optional) Specifies a node on which to turn on all debugging messages for the CPU driver.
The node-id argument is expressed in the rack/slot/module notation.
Note Enter the show platform command to see the location of all nodes installed in the router.
|
Defaults
No default behavior or values
Command Modes
EXEC
Command History
Release
|
Modification
|
Release 3.3.0
|
This command was introduced on the Cisco CRS-1.
|
Release 3.4.0
|
No modification.
|
Release 3.5.0
|
No modification.
|
Usage Guidelines
To use this command, you must be in a user group associated with a task group that includes the proper task IDs. For detailed information about user groups and task IDs, see the Configuring AAA Services on Cisco IOS XR Software module of the Cisco IOS XR System Security Configuration Guide.
Debugging output is assigned high priority in the CPU process and, therefore, can affect system performance. For more information about the impact on system performance when using debug commands, refer to Using Debug Commands on Cisco IOS XR Software.
Task ID
Task ID
|
Operations
|
drivers
|
read, write
|
Examples
The following example shows how to enable asic error messages for the CPU controller driver:
RP/0/RP0/CPU0:router# debug cpuctrl asic-error
Related Commands
Command
|
Description
|
debug cpuctrl api
|
Turns on all debugging messages for the CPU driver API DLL.
|
debug cpuctrl asic-error
|
Turns on asic error debugging messages for the CPU driver.
|
debug cpuctrl asic-info
|
Turns on all debugging messages from the CPU controller driver.
|
debug cpuctrl entryexit
|
Turns on all entry and exit messages from CPU controller driver.
|
debug cpuctrl error
|
Turns on error messages from the CPU controller.
|
debug cpuctrl fatal
|
Turns on fatal messages from CPU controller driver.
|
debug cpuctrl info
|
Turns on informational messages from the CPU controller.
|
debug cpuctrl location
|
Turns on all debugging messages from the CPU controller driver on a specific node.
|
show controllers cpuctrl cdma
|
Displays information about the CPU controller Code Division Multiplex Access (CDMA) engine.
|
show controllers cpuctrl clients
|
Displays information about all CPU controller clients on the router, or for specific CPU controller clients.
|
show controllers cpuctrl devices
|
Displays information about the CPU controller devices on the router.
|
show controllers cpuctrl internal
|
Displays information about the internal CPU controller.
|
show controllers cpuctrl ports
|
Displays port information for the specified CPU controller ASIC.
|
show controllers cpuctrl summary
|
Displays summarized information about all CPU controller ASICs on the router or on a specific node.
|
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
job jobid
|
(Optional) Specifies a job. Range is from 0 through 4294967295.
|
process string
|
(Optional) Specifies a process name or ID.
|
location node-id
|
(Optional) Specifies a node on which to turn on all debugging messages for the CPU driver.
The node-id argument is expressed in the rack/slot/module notation.
Note Enter the show platform command to see the location of all nodes installed in the router.
|
Defaults
No default behavior or values
Command Modes
EXEC
Command History
Release
|
Modification
|
Release 3.3.0
|
This command was introduced on the Cisco CRS-1.
|
Release 3.4.0
|
No modification.
|
Release 3.5.0
|
No modification.
|
Usage Guidelines
To use this command, you must be in a user group associated with a task group that includes the proper task IDs. For detailed information about user groups and task IDs, see the Configuring AAA Services on Cisco IOS XR Software module of the Cisco IOS XR System Security Configuration Guide.
Debugging output is assigned high priority in the CPU process and, therefore, can affect system performance. For more information about the impact on system performance when using debug commands, refer to Using Debug Commands on Cisco IOS XR Software.
Task ID
Task ID
|
Operations
|
drivers
|
read, write
|
Examples
The following example shows how to enable asic error messages for the CPU controller driver:
RP/0/RP0/CPU0:router# debug cpuctrl asic-error
Related Commands
Command
|
Description
|
debug cpuctrl api
|
Turns on all debugging messages for the CPU driver API DLL.
|
debug cpuctrl asic-error
|
Turns on asic error debugging messages for the CPU driver.
|
debug cpuctrl asic-info
|
Turns on all debugging messages from the CPU controller driver.
|
debug cpuctrl entryexit
|
Turns on all entry and exit messages from CPU controller driver.
|
debug cpuctrl error
|
Turns on error messages from the CPU controller.
|
debug cpuctrl fatal
|
Turns on fatal messages from CPU controller driver.
|
debug cpuctrl info
|
Turns on informational messages from the CPU controller.
|
debug cpuctrl location
|
Turns on all debugging messages from the CPU controller driver on a specific node.
|
show controllers cpuctrl cdma
|
Displays information about the CPU controller Code Division Multiplex Access (CDMA) engine.
|
show controllers cpuctrl clients
|
Displays information about all CPU controller clients on the router, or for specific CPU controller clients.
|
show controllers cpuctrl devices
|
Displays information about the CPU controller devices on the router.
|
show controllers cpuctrl internal
|
Displays information about the internal CPU controller.
|
show controllers cpuctrl ports
|
Displays port information for the specified CPU controller ASIC.
|
show controllers cpuctrl summary
|
Displays summarized information about all CPU controller ASICs on the router or on a specific node.
|
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
job jobid
|
(Optional) Specifies a job. Range is from 0 through 4294967295.
|
process string
|
(Optional) Specifies a process name or ID.
|
location node-id
|
(Optional) Specifies a node on which to turn on all debugging messages for the CPU driver.
The node-id argument is expressed in the rack/slot/module notation.
Note Enter the show platform command to see the location of all nodes installed in the router.
|
Defaults
No default behavior or values
Command Modes
EXEC
Command History
Release
|
Modification
|
Release 2.0
|
This command was introduced on the Cisco CRS-1.
|
Release 3.0
|
No modification.
|
Release 3.2
|
No modification.
|
Release 3.3.0
|
No modification.
|
Release 3.4.0
|
No modification.
|
Release 3.5.0
|
No modification.
|
Usage Guidelines
To use this command, you must be in a user group associated with a task group that includes the proper task IDs. For detailed information about user groups and task IDs, see the Configuring AAA Services on Cisco IOS XR Software module of the Cisco IOS XR System Security Configuration Guide.
Debugging output is assigned high priority in the CPU process and, therefore, can affect system performance. For more information about the impact on system performance when using debug commands, refer to Using Debug Commands on Cisco IOS XR Software.
Task ID
Task ID
|
Operations
|
drivers
|
read, write
|
Examples
The following example shows how to enable debugging information for the CPU controller driver:
RP/0/RP0/CPU0:router# debug cpuctrl detail
The 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/CPU0
Related Commands
Command
|
Description
|
debug cpuctrl api
|
Turns on all debugging messages for the CPU driver API DLL.
|
debug cpuctrl asic-error
|
Turns on asic error debugging messages for the CPU driver.
|
debug cpuctrl asic-info
|
Turns on asic info debugging messages for the CPU driver.
|
debug cpuctrl entryexit
|
Turns on all entry and exit messages from CPU controller driver.
|
debug cpuctrl error
|
Turns on error messages from the CPU controller.
|
debug cpuctrl fatal
|
Turns on fatal messages from CPU controller driver.
|
debug cpuctrl info
|
Turns on informational messages from the CPU controller.
|
debug cpuctrl location
|
Turns on all debugging messages from the CPU controller driver on a specific node.
|
show controllers cpuctrl cdma
|
Displays information about the CPU controller Code Division Multiplex Access (CDMA) engine.
|
show controllers cpuctrl clients
|
Displays information about all CPU controller clients on the router, or for specific CPU controller clients.
|
show controllers cpuctrl devices
|
Displays information about the CPU controller devices on the router.
|
show controllers cpuctrl internal
|
Displays information about the internal CPU controller.
|
show controllers cpuctrl ports
|
Displays port information for the specified CPU controller ASIC.
|
show controllers cpuctrl summary
|
Displays summarized information about all CPU controller ASICs on the router or on a specific node.
|
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
job jobid
|
(Optional) Specifies a job. Range is from 0 through 4294967295.
|
process string
|
(Optional) Specifies a process name or ID.
|
location node-id
|
(Optional) Specifies a node on which to turn on all entry and exit messages from the CPU driver.
The node-id argument is expressed in the rack/slot/module notation.
Note Enter the show platform command to see the location of all nodes installed in the router.
|
Defaults
No default behavior or values
Command Modes
EXEC
Command History
Release
|
Modification
|
Release 2.0
|
This command was introduced on the Cisco CRS-1.
|
Release 3.0
|
No modification.
|
Release 3.2
|
No modification.
|
Release 3.3.0
|
No modification.
|
Release 3.4.0
|
No modification.
|
Release 3.5.0
|
No modification.
|
Usage Guidelines
To use this command, you must be in a user group associated with a task group that includes the proper task IDs. For detailed information about user groups and task IDs, see the Configuring AAA Services on Cisco IOS XR Software module of the Cisco IOS XR System Security Configuration Guide.
Debugging output is assigned high priority in the CPU process and, therefore, can affect system performance. For more information about the impact on system performance when using debug commands, refer to Using Debug Commands on Cisco IOS XR Software.
Task ID
Task ID
|
Operations
|
drivers
|
read, write
|
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 enteryexit
The 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 400
Related Commands
Command
|
Description
|
debug cpuctrl api
|
Turns on all debugging messages for the CPU driver API DLL.
|
debug cpuctrl asic-error
|
Turns on asic error debugging messages for the CPU driver.
|
debug cpuctrl asic-info
|
Turns on asic info debugging messages for the CPU driver.
|
debug cpuctrl asic-error
|
Turns on all debugging messages from the CPU controller driver.
|
debug cpuctrl error
|
Turns on error messages from the CPU controller.
|
debug cpuctrl fatal
|
Turns on fatal messages from CPU controller driver.
|
debug cpuctrl info
|
Turns on informational messages from the CPU controller.
|
debug cpuctrl location
|
Turns on all debugging messages from the CPU controller driver on a specific node.
|
show controllers cpuctrl cdma
|
Displays information about the CPU controller Code Division Multiplex Access (CDMA) engine.
|
show controllers cpuctrl clients
|
Displays information about all CPU controller clients on the router, or for specific CPU controller clients.
|
show controllers cpuctrl devices
|
Displays information about the CPU controller devices on the router.
|
show controllers cpuctrl internal
|
Displays information about the internal CPU controller.
|
show controllers cpuctrl ports
|
Displays port information for the specified CPU controller ASIC.
|
show controllers cpuctrl summary
|
Displays summarized information about all CPU controller ASICs on the router or on a specific node.
|
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
job jobid
|
(Optional) Specifies a job. Range is from 0 through 4294967295.
|
process string
|
(Optional) Specifies a process name or ID.
|
location node-id
|
(Optional) Specifies a node on which to turn on all error messages from the CPU driver.
The node-id argument is expressed in the rack/slot/module notation.
Note Enter the show platform command to see the location of all nodes installed in the router.
|
Defaults
No default behavior or values
Command Modes
EXEC
Command History
Release
|
Modification
|
Release 2.0
|
This command was introduced on the Cisco CRS-1.
|
Release 3.0
|
No modification.
|
Release 3.2
|
No modification.
|
Release 3.3.0
|
No modification.
|
Release 3.4.0
|
No modification.
|
Release 3.5.0
|
No modification.
|
Usage Guidelines
To use this command, you must be in a user group associated with a task group that includes the proper task IDs. For detailed information about user groups and task IDs, see the Configuring AAA Services on Cisco IOS XR Software module of the Cisco IOS XR System Security Configuration Guide.
Debugging output is assigned high priority in the CPU process and, therefore, can affect system performance. For more information about the impact on system performance when using debug commands, refer to Using Debug Commands on Cisco IOS XR Software.
Task ID
Task ID
|
Operations
|
drivers
|
read, write
|
Examples
The following example shows how to turn on all error messages from the CPU controller:
RP/0/RP0/CPU0:router# debug cpuctrl error
The 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/CPU0
Related Commands
Command
|
Description
|
debug cpuctrl api
|
Turns on all debugging messages for the CPU driver API DLL.
|
debug cpuctrl asic-error
|
Turns on asic error debugging messages for the CPU driver.
|
debug cpuctrl asic-info
|
Turns on asic info debugging messages for the CPU driver.
|
debug cpuctrl asic-error
|
Turns on all debugging messages from the CPU controller driver.
|
debug cpuctrl entryexit
|
Turns on all entry and exit messages from CPU controller driver.
|
debug cpuctrl fatal
|
Turns on fatal messages from CPU controller driver.
|
debug cpuctrl info
|
Turns on informational messages from the CPU controller.
|
debug cpuctrl location
|
Turns on all debugging messages from the CPU controller driver on a specific node.
|
show controllers cpuctrl cdma
|
Displays information about the CPU controller Code Division Multiplex Access (CDMA) engine.
|
show controllers cpuctrl clients
|
Displays information about all CPU controller clients on the router, or for specific CPU controller clients.
|
show controllers cpuctrl devices
|
Displays information about the CPU controller devices on the router.
|
show controllers cpuctrl internal
|
Displays information about the internal CPU controller.
|
show controllers cpuctrl ports
|
Displays port information for the specified CPU controller ASIC.
|
show controllers cpuctrl summary
|
Displays summarized information about all CPU controller ASICs on the router or on a specific node.
|
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
job jobid
|
(Optional) Specifies a job. Range is from 0 through 4294967295.
|
process string
|
(Optional) Specifies a process name or ID.
|
location node-id
|
(Optional) Specifies a node on which to turn on all fatal messages from the CPU driver.
The node-id argument is expressed in the rack/slot/module notation.
Note Enter the show platform command to see the location of all nodes installed in the router.
|
Defaults
No default behavior or values
Command Modes
EXEC
Command History
Release
|
Modification
|
Release 2.0
|
This command was introduced on the Cisco CRS-1.
|
Release 3.0
|
No modification.
|
Release 3.2
|
No modification.
|
Release 3.3.0
|
No modification.
|
Release 3.4.0
|
No modification.
|
Release 3.5.0
|
No modification.
|
Usage Guidelines
To use this command, you must be in a user group associated with a task group that includes the proper task IDs. For detailed information about user groups and task IDs, see the Configuring AAA Services on Cisco IOS XR Software module of the Cisco IOS XR System Security Configuration Guide.
Debugging output is assigned high priority in the CPU process and, therefore, can affect system performance. For more information about the impact on system performance when using debug commands, refer to Using Debug Commands on Cisco IOS XR Software.
Task ID
Task ID
|
Operations
|
drivers
|
read, write
|
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 fatal
The 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 332
Related Commands
Command
|
Description
|
debug cpuctrl api
|
Turns on all debugging messages for the CPU driver API DLL.
|
debug cpuctrl asic-error
|
Turns on asic error debugging messages for the CPU driver.
|
debug cpuctrl asic-info
|
Turns on asic info debugging messages for the CPU driver.
|
debug cpuctrl asic-error
|
Turns on all debugging messages from the CPU controller driver.
|
debug cpuctrl entryexit
|
Turns on all entry and exit messages from CPU controller driver.
|
debug cpuctrl error
|
Turns on error messages from the CPU controller.
|
debug cpuctrl info
|
Turns on informational messages from the CPU controller.
|
debug cpuctrl location
|
Turns on all debugging messages from the CPU controller driver on a specific node.
|
show controllers cpuctrl cdma
|
Displays information about the CPU controller Code Division Multiplex Access (CDMA) engine.
|
show controllers cpuctrl clients
|
Displays information about all CPU controller clients on the router, or for specific CPU controller clients.
|
show controllers cpuctrl devices
|
Displays information about the CPU controller devices on the router.
|
show controllers cpuctrl internal
|
Displays information about the internal CPU controller.
|
show controllers cpuctrl ports
|
Displays port information for the specified CPU controller ASIC.
|
show controllers cpuctrl summary
|
Displays summarized information about all CPU controller ASICs on the router or on a specific node.
|
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
job jobid
|
(Optional) Specifies a job. Range is from 0 through 4294967295.
|
process string
|
(Optional) Specifies a process name or ID.
|
location node-id
|
(Optional) Specifies a node on which to turn on all informational debugging messages from the CPU driver.
The node-id argument is expressed in the rack/slot/module notation.
Note Enter the show platform command to see the location of all nodes installed in the router.
|
