Table Of Contents
ASIC Driver Commands on Cisco IOS XR Software
asic-scan egressq (block number)
asic-scan pse egress (block number)
asic-scan pse egress quick-scan
asic-scan pse ingress (block number)
asic-scan pse ingress location
asic-scan pse ingress quick-scan
clear controller egressq queue
clear controller egressq queue all
clear controller egressq statistics
clear controller ingressq statistics
clear controller pse statistics
show controllers cpuctrl cdma channel
show controllers cpuctrl clients
show controllers cpuctrl devices
show controllers cpuctrl internal
show controllers cpuctrl ports
show controllers cpuctrl summary
show controllers egressq eio links
show controllers egressq group
show controllers egressq interface
show controllers egressq queue
show controllers egressq statistics
show controllers ingressq statistics
show controllers plim asic egress-channel bay
show controllers plim asic ingress-channel bay
show controllers plim asic spa bay
show controllers plim asic statistics
show controllers plim asic summary
show controllers pse eio links
show controllers pse statistics
ASIC Driver Commands on Cisco IOS XR Software
This module describes the commands used to configure and monitor the ASICs on a router running Cisco IOS XR software.
asic-scan egressq (block number)
To run, enable, or disable a generic ASIC scan on a specific egress queue ASIC block ID or error cause, use the asic-scan egressq command in EXEC mode.
asic-scan egressq block_number [[error_cause] [disable | enable] | help-cause] 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.
Task ID
Examples
The following example shows how to display a list of all error causes in the specified block:
RP/0/RP0/CPU0:router# asic-scan egressq 10 help-cause location 0/6/CPU0Total 6 cause(s)Cause Number Cause Name0 lbm_owl_ovl1 scr_m4_ovl2 scr_m3_ovl3 scr_m2_ovl4 scr_m1_ovl5 scr_m0_ovlThe following example shows how to run a scan on the egress queue ASIC block ID 30 located on the CPU node in slot 1:
RP/0/RP0/CPU0:router# asic-scan egressq 30 location 0/6/CPU0asic-scan egressq disable
To disable an ASIC scan on all causes in all blocks on the specified node, use the asic-scan egressq disable command in EXEC mode.
asic-scan egressq disable 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.
Task ID
Examples
The following example shows how to disable an ASIC scan on all causes in all blocks on the egress queue that is located on the CPU node in slot 6:
RP/0/RP0/CPU0:router# asic-scan egressq disable location 0/6/CPU0asic-scan egressq enable
To enable an ASIC scan on all causes in all blocks on the specified node, use the asic-scan egressq enable command in EXEC mode.
asic-scan egressq enable 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.
Task ID
Examples
The following example shows how to enable an ASIC scan on all causes in all blocks on the egress queue that is located on the CPU node in slot 6:
RP/0/RP0/CPU0:router# asic-scan egressq enable location 0/6/CPU0asic-scan egressq location
To run an ASIC scan on all the egress queues on a specific node, use the asic-scan egressq location command in EXEC mode.
asic-scan egressq 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.
Task ID
Examples
The following example shows how to run an ASIC scan on all egress queues located on the CPU node in slot 1:
RP/0/RP0/CPU0:router# asic-scan egressq location 0/1/CPU0asic-scan egressq quick-scan
To run a quick ASIC scan on a specific file or on all bits of the chip, use the asic-scan egressq quick-scan command in EXEC mode.
asic-scan egressq quick-scan {filename | allscan} 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.
Task ID
Examples
The following example shows how to run a quick ASIC scan on all bits of the chip on the egress queue that is located on the CPU node in slot 1:
RP/0/RP0/CPU0:router# asic-scan egressq quick-scan allscan location 0/1/CPU0asic-scan pse egress (block number)
To run, enable, or disable a generic ASIC scan on a specific egress Packet Switching Engine (PSE) device block or error cause, use the asic-scan pse egress command in EXEC mode.
asic-scan pse egress block_number [[error_cause] [disable | enable] | help-cause] 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.
Task ID
Examples
The following example shows how to display a list of all error causes in the specified block of a PSE device:
RP/0/RP0/CPU0:router# asic-scan pse egress 10 help-cause location 0/6/CPU0Total 6 cause(s)Cause Number Cause Name0 lbm_owl_ovl1 scr_m4_ovl2 scr_m3_ovl3 scr_m2_ovl4 scr_m1_ovl5 scr_m0_ovlThe following example shows how to run a scan on the PSE ASIC block ID 30 located on the CPU node in slot 1:
RP/0/RP0/CPU0:router# asic-scan pse egress 30 location 0/6/CPU0asic-scan pse egress disable
To disable an ASIC scan on all causes in all blocks of a specific Packet Switching Engine (PSE) device, use the asic-scan pse egress disable command in EXEC mode.
asic-scan pse egress disable 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.
Task ID
Examples
The following example shows how to disable an ASIC scan on all causes in all blocks of the egress PSE device that is located on the CPU node in slot 6:
RP/0/RP0/CPU0:router# asic-scan pse egress disable location 0/6/CPU0asic-scan pse egress enable
To enable an ASIC scan on all causes in all blocks of a specific egress Packet Switching Engine (PSE) device, use the asic-scan pse egress enable command in EXEC mode.
asic-scan pse egress enable 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.
Task ID
Examples
The following example shows how to enable an ASIC scan on all causes in all blocks on the egress PSE that is located on the CPU node in slot 6:
RP/0/RP0/CPU0:router# asic-scan pse egress enable location 0/6/CPU0asic-scan pse egress location
To run an ASIC scan on a specific Packet Switching Engine (PSE) device, use the asic-scan pse egress location command in EXEC mode.
asic-scan pse egress 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.
Task ID
Examples
The following example shows how to run an ASIC scan on all egress PSE located on the CPU node in slot 1:
RP/0/RP0/CPU0:router# asic-scan pse egress location 0/1/CPU0asic-scan pse egress quick-scan
To run a quick ASIC scan on a specific file or on all bits of the chip located on a specific Packet Switching Engine (PSE) device, use the asic-scan pse egress quick-scan command in EXEC mode.
asic-scan pse egress quick-scan {filename | allscan} 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.
Task ID
Examples
The following example shows how to run a quick ASIC scan on all bits of the chip on the egress PSE device that is located on the CPU node in slot 1:
RP/0/RP0/CPU0:router# asic-scan pse egress quick-scan allscan location 0/1/CPU0asic-scan pse ingress (block number)
To run, enable, or disable a generic ASIC scan on a specific ingress Packet Switching Engine (PSE) device block or error cause, use the asic-scan pse ingress command in EXEC mode.
asic-scan pse ingress block_number [[error_cause] [disable | enable] | help-cause] 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.
Task ID
Examples
The following example shows how to display a list of all error causes in the specified block of a PSE device:
RP/0/RP0/CPU0:router# asic-scan pse ingress 10 help-cause location 0/6/CPU0Total 6 cause(s)Cause Number Cause Name0 lbm_owl_ovl1 scr_m4_ovl2 scr_m3_ovl3 scr_m2_ovl4 scr_m1_ovl5 scr_m0_ovlThe following example shows how to run a scan on the PSE ASIC block ID 30 located on the CPU node in slot 1:
RP/0/RP0/CPU0:router# asic-scan pse ingress 30 location 0/6/CPU0asic-scan pse ingress disable
To disable an ASIC scan on all causes in all blocks of a specific Packet Switching Engine (PSE) device, use the asic-scan pse ingress disable command in EXEC mode.
asic-scan pse ingress disable 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.
Task ID
Examples
The following example shows how to disable an ASIC scan on all causes in all blocks of the ingress PSE device that is located on the CPU node in slot 6:
RP/0/RP0/CPU0:router# asic-scan pse ingress disable location 0/6/CPU0asic-scan pse ingress enable
To enable an ASIC scan on all causes in all blocks of a specific ingress Packet Switching Engine (PSE) device, use the asic-scan pse ingress enable command in EXEC mode.
asic-scan pse ingress enable 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.
Task ID
Examples
The following example shows how to enable an ASIC scan on all causes in all blocks on the ingress PSE that is located on the CPU node in slot 6:
RP/0/RP0/CPU0:router# asic-scan pse ingress enable location 0/6/CPU0asic-scan pse ingress location
To run an ASIC scan on a specific Packet Switching Engine (PSE) device, use the asic-scan pse ingress location command in EXEC mode.
asic-scan pse ingress 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.
Task ID
Examples
The following example shows how to run an ASIC scan on all ingress PSE located on the CPU node in slot 1:
RP/0/RP0/CPU0:router# asic-scan pse ingress location 0/1/CPU0asic-scan pse ingress quick-scan
To run a quick ASIC scan on a specific file or on all bits of the chip located on a specific Packet Switching Engine (PSE) device, use the asic-scan pse ingress quick-scan command in EXEC mode.
asic-scan pse ingress quick-scan {filename | allscan} 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.
Task ID
Examples
The following example shows how to run a quick ASIC scan on all bits of the chip on the ingress PSE device that is located on the CPU node in slot 1:
RP/0/RP0/CPU0:router# asic-scan pse ingress quick-scan allscan location 0/1/CPU0clear controller egressq queue
To clear a specific controller egress queue, use the clear controller egressq queue command in EXEC mode.
clear controller egressq queue queue-id1 [queue-id2] 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.
Note
If you enter the optional [queue-id2] argument after you enter the queue-id1 argument, then the queue-id1 argument specifies the first queue in a range of queues to be cleared. If you enter the queue-id1 argument without specifying the queue-id2 argument, then only the queue specified for queue-id1 is cleared.
Task ID
Examples
The following example shows how to clear a specific controller egress queue:
RP/0/RP0/CPU0:router# clear controller egress queue 1 location 0/1/CPU0Related Commands
clear controller egressq queue all
To clear all controller egress queues on a specific node, use the clear controller egressq queue all command in EXEC mode.
clear controller egressq queue all 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.
Task ID
Examples
The following example shows how to clear all controller egress queues on a specific node:
RP/0/RP0/CPU0:router# clear controller egress queue all location 0/1/CPU0Related Commands
clear controller egressq statistics
To clear the egress queue statistics in a specific location, use the clear controller egressq statistics command in EXEC mode.
clear controller egressq statistics 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.
Task ID
Examples
The following example shows how to clear all controller egress queue statistics on a specific node:
RP/0/RP0/CPU0:router# clear controller egressq statistics location 0/1/CPU0Related Commands
clear controller ingressq statistics
To clear application-specific integrated circuit (ASIC) statics from the ingress fabric queue on a specific node, or on all nodes installed in the router, use the clear controller ingressq statistics command in EXEC mode.
clear controller ingressq statistics [location node-id]
Syntax Description
location node-id
(Optional) Identifies the node whose ASIC statistics you want to clear from the ingress fabric queue. The node-id argument is entered in the rack/slot/module notation.
Defaults
Enter the clear controller ingressq statistics command without the optional location node-id keyword argument to clear the ASIC statistics from the ingress queues on all nodes that are installed in the 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.
Only locations that contain a fabric queue ASIC can be specified for the location node-id.
The clear controller ingressq statistics command is intended for use while performing special maintenance, test, or debugging procedures. You do not need to use this command when fabric connectivity is performing normally.
Task ID
Examples
The following example shows how to use the clear controller ingressq statistics command to clear all ASIC statistics in the ingress fabric queue from the location 0/1/CPU0:
RP/0/RP0/CPU0:router# clear controller ingressq statistics location 0/1/CPU0Related Commands
clear controller pse statistics
To clear statistics maintained by the packet switching engine (PSE) on a specific node, use the clear controller pse statistics command in EXEC mode.
clear controller pse statistics [egress | ingress] location node-id
Syntax Description
Defaults
If the egress or ingress keywords are not specified, the clear controller pse statistics command takes effect on both device instances.
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.
Task ID
Examples
The following example shows how to clear all PSE statistics on a specific node (0/1/CPU0):
RP/0/RP0/CPU0:router# clear controller pse statistics location 0/1/CPU0The following example shows how to clear all egress PSE statistics on a specific node (0/6/CPU0):
RP/0/RP0/CPU0:router# clear controller pse statistics egress location 0/6/CPU0Related Commands
show controllers cpuctrl cdma channel
To display information about the CPU controller Code Division Multiplex Access (CDMA) engine, use the show controllers cpuctrl cdma channel command in EXEC mode.
show controllers cpuctrl cdma channel {0 | 1} queue {queue-id | all} {active | 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.
Task ID
Examples
The following example shows partial output from the show controllers cpuctrl cdma channel command with the detail keyword.
RP/0/RP0/CPU0:router# show controllers cpuctrl cdma channel 1 queue 1 detail location 0/6/CPU0-------------------------------------------------------DMA queue:Channel: 1 queue: 1 state: ActiveOS Interrupt Level = 108 Cpuctrl Int Level = 12OS Run Priority = 45 client handle = 1ISR context = 0x780cff84 Pakman/Bufman Inst = bufman/miscclient callback function = 0x482038e4 cleanup function = 0x48203a90Pakmode = 0x00000002 Pollflags = 0x00000000Total DMA transactions = 3 Queue create count = 1DMA transactions = 3 Bytes transferred = 67584DMA Out of Desc errs = 0 DMA IWA = 0DMA transaction errs = 0Descriptor list base addr = 0xec0370f0 Physical address = 0x0510f0f0list_size = 32 Active descriptors = 0current_index = 3 tx_enqueue_index = 3Index 0, Shadow: Hdr 0x00000000 Flags 0x00000000Descriptor: 0x40200060 |...|DIR|...|...| Width 0x00200x0000fff8 Bufsize 0x0000 | Xfersize 0xfff80x00120000 Memaddr 0x0001200000x6fb4d000 Squidaddr 0x606fb4d000Index 1, Shadow: Hdr 0x00000000 Flags 0x00000000Descriptor: 0x40200060 |...|DIR|...|...| Width 0x00200x00000008 Bufsize 0x0000 | Xfersize 0x00080x0012fff8 Memaddr 0x00012fff80x6fb4d000 Squidaddr 0x606fb4d000Index 2, Shadow: Hdr 0x00000000 Flags 0x00000000Descriptor: 0x40100060 |...|DIR|...|...| Width 0x00100x00000800 Bufsize 0x0000 | Xfersize 0x08000x00041000 Memaddr 0x0000410000x6fb42000 Squidaddr 0x606fb42000Index 3, Shadow: Hdr 0x00000000 Flags 0x00000000Descriptor: 0x00000000 |...|...|...|...| Width 0x00000x00000000 Bufsize 0x0000 | Xfersize 0x00000x00000000 Memaddr 0x0000000000x00000000 Squidaddr 0x0000000000Index 4, Shadow: Hdr 0x00000000 Flags 0x00000000--More--Table 2 describes the significant fields shown in the display.
1. Division Multiple Access
Related Commands
Displays information about all CPU controller clients on the router, or for specific CPU controller clients.
show controllers cpuctrl clients
To display information about all CPU controller clients on the router, or for specific CPU controller clients, use the show controllers cpuctrl clients command in EXEC mode.
show controllers cpuctrl clients {all | cdma clients | pdma clients} {active | 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.
Task ID
Examples
The following example shows how to display information about the active queues on the CPU controller client called "plimasic":
RP/0/RP0/CPU0:router# show controllers cpuctrl clients plimasic active-------------------------------------------------------------client_name: plimasic client_handle: 10isr_count: 0 queue_count: 0client_pid: 0-------------------------------------------------------------client_name: plimasic client_handle: 10isr_count: 0 queue_count: 0client_pid: 0-------------------------------------------------------------client_name: plim asic client_handle: 10isr_count: 0 queue_count: 0client_pid: 0-------------------------------------------------------------client_name: plim asic client_handle: 10isr_count: 0 queue_count: 0client_pid: 0Table 3 describes the significant fields shown in the display.
1. Division Multiplex Access
2. Integrated SONET/SDH
3. packet identification
Related Commands
Displays information about the CPU controller CDMA engine.
Displays summarized information about all CPU controller ASICs on the router or on a specific node
show controllers cpuctrl devices
To display information about the CPU controller devices on the router, use the show controllers cpuctrl devices command in EXEC mode.
show controllers cpuctrl devices device-name {pdma queue {all | tx | rx} {active | detail} | 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.
Task ID
Examples
The following example shows how to display transmit and receive PDMA information for all active queues on the egressq ASIC instance 0:
RP/0/RP0/CPU0:router# show controllers cpuctrl devices egressq pdma all active---------------------------------------------------------------TX PKT queue:cpuctrl net Port: 7 queue: 0client handle: 6 queue state: ActiveOS Interrupt Level:127 Cpuctrl Interrupt Level:31OS Run Priority:20 Queue Created 1 timesPakmode = 0x1Tx out_of_desc failures = 0Packets transmitted = 0, Byte transmitted = 0Tx IWA = 0ISR pointer is at 0x7804372c Descriptor List at 0xec27b060Pakman/Bufman Instance: /dev/pakman/serverclient callback function pointer 0x00000000client cleanup function pointer 0x00000000Queue descriptor list info:list_size=1024 current_index=0 tx_index=0active descriptors number:0---------------------------------------------------------------TX PKT queue:cpuctrl net Port: 0 queue: 1client handle: 6 queue state: Inactive---------------------------------------------------------------TX PKT queue:cpuctrl net Port: 0 queue: 2client handle: 6 queue state: Inactive---------------------------------------------------------------TX PKT queue:cpuctrl net Port: 0 queue: 3client handle: 6 queue state: Inactive---------------------------------------------------------------TX PKT queue:cpuctrl net Port: 0 queue: 4client handle: 6 queue state: Inactive---------------------------------------------------------------TX PKT queue:cpuctrl net Port: 0 queue: 5client handle: 6 queue state: Inactive---------------------------------------------------------------TX PKT queue:cpuctrl net Port: 0 queue: 6client handle: 6 queue state: Inactive---------------------------------------------------------------TX PKT queue:cpuctrl net Port: 0 queue: 7client handle: 6 queue state: Inactive---------------------------------------------------------------RX PKT queue:cpuctrl net Port: 7 queue: 0client handle: 3 queue state: Active--More--Table 4 describes the significant fields shown in the display.
1. transmit
2. receive
Related Commands
Displays summarized information about all CPU controller ASICs on the router or on a specific node.
show controllers cpuctrl internal
To display information about the internal CPU controller, use the show controllers cpuctrl internal command in EXEC mode.
show controllers cpuctrl internal location node-id
Syntax Description
location node-id
Identifies the location of the node whose internal CPU controller information you want to display. The node-id is expressed in the rack/slot/module notation.
Defaults
No default behavior or values
Command Modes
EXEC
Command History
Usage Guidelines
To use this command, you must be in a user group associated with a task group that includes the proper task IDs. For detailed information about user groups and task IDs, see the Configuring AAA Services on Cisco IOS XR Software module of the Cisco IOS XR System Security Configuration Guide.
Task ID
Examples
The following example shows how to display information about the internal CPU controller:
RP/0/RP0/CPU0:router# show controllers cpuctrl internalCpuctrl Internal Info for node 0/0/CPU0:Error Interrupts = 0 Spurious Error Interrupts = 0PCI Error Overflows = 0 PCI PM Error Overflows = 0PCIX Error Overflows = 0 Internal Access PCI Overflows = 0Port Error Overflows = 0 Error Log Overflows = 0cpuctrl Config Reg = 0x8357ffff cpuctrl Physical Offset = 0x80000000cpuctrl Window Size = 0x40000000 cpuctrl Port Window Size = 0x04000000cpuctrl SHMem Size = 0x00800000 cpuctrl SHMem Used = 0x00223ee8cpuctrl version info: Squid FPGA v2.07 Fri Jan 23 16:21:01 2004 ykorenCpuctrl Internal Info for node 0/3/CPU0:Error Interrupts = 0 Spurious Error Interrupts = 0PCI Error Overflows = 0 PCI PM Error Overflows = 0PCIX Error Overflows = 0 Internal Access PCI Overflows = 0Port Error Overflows = 0 Error Log Overflows = 0cpuctrl Config Reg = 0x8357ffff cpuctrl Physical Offset = 0x80000000cpuctrl Window Size = 0x40000000 cpuctrl Port Window Size = 0x04000000cpuctrl SHMem Size = 0x00800000 cpuctrl SHMem Used = 0x00223ee8cpuctrl version info: Squid FPGA v2.07 Fri Jan 23 16:21:01 2004 ykorenCpuctrl Internal Info for node 0/RP0/CPU0:Error Interrupts = 0 Spurious Error Interrupts = 0PCI Error Overflows = 0 PCI PM Error Overflows = 0PCIX Error Overflows = 0 Internal Access PCI Overflows = 0Port Error Overflows = 0 Error Log Overflows = 0cpuctrl Config Reg = 0x803f007f cpuctrl Physical Offset = 0x80000000cpuctrl Window Size = 0x40000000 cpuctrl Port Window Size = 0x04000000cpuctrl SHMem Size = 0x00800000 cpuctrl SHMem Used = 0x00223ee8cpuctrl version info: Squid FPGA v2.07 Fri Feb 6 17:49:22 2004 ykorenCpuctrl Internal Info for node 0/RP1/CPU0:Error Interrupts = 0 Spurious Error Interrupts = 0PCI Error Overflows = 0 PCI PM Error Overflows = 0PCIX Error Overflows = 0 Internal Access PCI Overflows = 0Port Error Overflows = 0 Error Log Overflows = 0cpuctrl Config Reg = 0x003f007f cpuctrl Physical Offset = 0x80000000cpuctrl Window Size = 0x40000000 cpuctrl Port Window Size = 0x04000000cpuctrl SHMem Size = 0x00800000 cpuctrl SHMem Used = 0x00223ee8cpuctrl version info: Squid FPGA v2.05 Wed Sep 3 17:37:47 2003 ykorenTable 5 describes the significant fields shown in the display.
1. Peripheral Component Interconnect
2. port manager
Related Commands
Displays summarized information about all CPU controller ASICs on the router or on a specific node
show controllers cpuctrl ports
To display port information for the specified CPU controller ASIC, use the show controllers cpuctrl ports command in EXEC mode.
show controllers cpuctrl ports {asic_id} {pdma queue {queue-id | all} direction {all | rx | tx} {active | detail} | 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.
Task ID
Examples
The following example shows how to display port information for the transmit and receive PIO queues on the EPSE ASIC:
RP/0/RP0/CPU0:router# show controllers cpuctrl ports epse pioclient name: PSE device instance: 1cpuctrl net port: 6 pci base: 0x98000000map reg: 0x6076a12c OS interrupt level: 102Cpuctrl interrupt level: 6 OS Run priority: 6config reg: 0x00000000 channels reg: 0x00000000int_cause_asic_mask: 0x00000010 int_cause_error_mask: 0x00000020int_cause_link_error_mask: 0x00000040crc_errors: 0 sync_errors: 0 reframe_events: 0client name: PSE device instance: 1cpuctrl net port: 6 pci base: 0x98000000map reg: 0x6076a12c OS interrupt level: 102Cpuctrl interrupt level: 6 OS Run prority: 6config reg: 0x00000000 channels reg: 0x00000000int_cause_asic_mask: 0x00000010 int_cause_error_mask: 0x00000020int_cause_link_error_mask: 0x00000040crc_errors: 0 sync_errors: 0 reframe_events: 0device PSE instance 1 is not detected on node 201/Table 6 describes the significant fields shown in the display.
1. Peripheral Component Interconnect
2. cyclic redundancy check
Related Commands
Displays summarized information about all CPU controller ASICs on the router or on a specific node.
show controllers cpuctrl summary
To display summarized information about all CPU controller ASICs on the router or on a specific node, use the show controllers cpuctrl summary command in EXEC mode.
show controllers cpuctrl summary [location node-id]
Syntax Description
location node-id
(Optional) Identifies the location of the node whose CPU controller ASIC information you want to display. The node-id is expressed in the rack/slot/module notation.
Defaults
No default behavior or values
Command Modes
EXEC
Command History
Usage Guidelines
To use this command, you must be in a user group associated with a task group that includes the proper task IDs. For detailed information about user groups and task IDs, see the Configuring AAA Services on Cisco IOS XR Software module of the Cisco IOS XR System Security Configuration Guide.
Task ID
Examples
The following example shows how to display summarized information about all CPU controller ASICs on a specific node:
RP/0/RP0/CPU0:router# show controllers cpuctrl summary location 0/0/CPU0Cpuctrl discovered 11 device on node 0/0/CPU0:Cpuctrl HW version string for this node is:Squid FPGA v2.07 Fri Jan 23 16:21:01 2004 ykoren-----------------------------------------------------------device_name: Fabricq device instance: 0Cpuctrl net port: 3 pci_base: 0x8c000000-----------------------------------------------------------device_name: Fabricq device instance: 1Cpuctrl net port: 4 pci_base: 0x90000000-----------------------------------------------------------device_name: Ingressq device instance: 0Cpuctrl net port: 8 pci_base: 0xa0000000-----------------------------------------------------------device_name: Egressq device instance: 0Cpuctrl net port: 7 pci_base: 0x9c000000-----------------------------------------------------------device_name: FIA device instance: 0Cpuctrl net port: 1 pci_base: 0x84000000-----------------------------------------------------------device_name: FIA device instance: 1Cpuctrl net port: 2 pci_base: 0x88000000-----------------------------------------------------------device_name: Cpuctrl device instance: 0Cpuctrl net port: 0 pci_base: 0x80000000-----------------------------------------------------------device_name: PSE device instance: 1Cpuctrl net port: 6 pci_base: 0x98000000--More--Table 7 describes the significant fields shown in the display.
1. Peripheral Component Interconnect
Related Commands
show controllers egressq eio links
To display Elastic I/O (EIO) information for the egress queueing ASIC, use the show controllers egressq eio links command in EXEC mode.
show controllers egressq eio links {link-id | all} location node-id
Syntax Description
Defaults
No default behavior or values
Command Modes
EXEC
Command History
Release 3.2
This command was introduced on the Cisco CRS-1.
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.
Task ID
Examples
The following example shows how to display information for all EIO links on a node's egress queueing ASIC:
RP/0/RP0/CPU0:router# show controllers egressq eio links all location 0/2/CPU0Node: 0/2/CPU0:----------------------------------------EIO links:-------------------------------------------------------------------ASIC Id Peer Id Type Link-Id Attempts Accept Failed State-------------------------------------------------------------------EGRESSQ_0 PSE_1 RX 11 1 1 0 EIO_LINK_TRAINEDEGRESSQ_0 PSE_1 TX 64 0 0 0 EIO_LINK_TRAINEDEGRESSQ_0 PLIM-ASIC_0 TX 60 0 0 0 EIO_LINK_TRAINEDEGRESSQ_0 PLIM-ASIC_1 TX 61 0 0 0 EIO_ADD_LINKEGRESSQ_0 PLIM-ASIC_2 TX 62 0 0 0 EIO_ADD_LINKEGRESSQ_0 PLIM-ASIC_3 TX 63 0 0 0 EIO_ADD_LINKTable 8 describes the significant fields shown in the display.
Related Commands
show controllers egressq group
To display information about egress queue groups, use the show controllers egressq group command in EXEC mode.
show controllers egressq group {group1 [group2] | all | limits {max | min}} location node-id
Syntax Description
Defaults
No default behavior or values
Command Modes
EXEC
Command History
Release 3.2
This command was introduced on the Cisco CRS-1.
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.
If you do not specify a group number for the group2 argument, information is displayed only for the egress queue you specified for the group1 argument. If you specify group1 and group2, information is displayed for all groups within the range from group1 through group2.
Task ID
Examples
The following example shows how to display information for a specific range of egress queue groups on the CPU node in slot 2:
RP/0/RP0/CPU0:router# show controllers egressq group 1 3 location 0/2/CPU0----------------------------------Group 1----------------------------------Port : 0Priority : LowMax LB Tokens : 7812Max LB Limit Index : 38Min LB Tokens : 0Min LB Limit Index : 0Quantum : 27Default Queue : 1High Priority Queue : N/ALow Priority Queue : 1--------------------------------------------------------------------Group 2----------------------------------Port : 1Priority : LowMax LB Tokens : 7812Max LB Limit Index : 38Min LB Tokens : 0Min LB Limit Index : 0Quantum : 27Default Queue : 2High Priority Queue : N/ALow Priority Queue : 2--------------------------------------------------------------------Group 3----------------------------------Port : 256Priority : LowMax LB Tokens : 7812Max LB Limit Index : 38Min LB Tokens : 0Min LB Limit Index : 0Quantum : 27Default Queue : 3High Priority Queue : N/ALow Priority Queue : 3----------------------------------Table 9 describes the significant fields shown in the display.
Related Commands
show controllers egressq interface
To display information about interfaces associated with an egress queue, use the show controllers egressq interface command in EXEC mode.
show controllers egressq interface [type instance | all] location location
Syntax Description
Defaults
No default behavior or values
Command Modes
EXEC
Command History
Release 3.2
This command was introduced on the Cisco CRS-1.
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.
Task ID
Examples
The following example shows how to display egress queue information for all configured interfaces on the router:
RP/0/RP0/CPU0:router# show controllers egressq interface all/CPU0----------------------------------Interface POS0/0/0/15----------------------------------Port 776----------------------------------Max LB Tokens : 18720Max LB Limit Index : 41Quantum : 27Default Group : 24High Priority Group : N/ALow Priority Group : 24--------------------------------------------------------------------Interface POS0/0/0/14----------------------------------Port 780----------------------------------Max LB Tokens : 18720Max LB Limit Index : 41Quantum : 27Default Group : 23High Priority Group : N/ALow Priority Group : 23--------------------------------------------------------------------Interface POS0/0/0/13----------------------------------Port 778----------------------------------Max LB Tokens : 18720Max LB Limit Index : 41Quantum : 27Default Group : 22High Priority Group : N/ALow Priority Group : 22--------------------------------------------------------------------Interface POS0/0/0/12----------------------------------Port 782----------------------------------Max LB Tokens : 18720Max LB Limit Index : 41Quantum : 27Default Group : 21High Priority Group : N/ALow Priority Group : 21--------------------------------------------------------------------Interface POS0/0/0/11----------------------------------Port 520----------------------------------Max LB Tokens : 18720Max LB Limit Index : 41Quantum : 27Default Group : 20High Priority Group : N/ALow Priority Group : 20--------------------------------------------------------------------Interface POS0/0/0/10----------------------------------Port 524----------------------------------Max LB Tokens : 18720Max LB Limit Index : 41Quantum : 27Default Group : 19High Priority Group : N/ALow Priority Group : 19--------------------------------------------------------------------Interface POS0/0/0/9----------------------------------Port 522----------------------------------Max LB Tokens : 18720Max LB Limit Index : 41Quantum : 27Default Group : 18High Priority Group : N/ALow Priority Group : 18--------------------------------------------------------------------Interface POS0/0/0/8----------------------------------Port 526----------------------------------Max LB Tokens : 18720Max LB Limit Index : 41Quantum : 27Default Group : 17High Priority Group : N/ALow Priority Group : 17--------------------------------------------------------------------Table 10 describes the significant fields shown in the display.
Related Commands
show controllers egressq port
To display egress queue information for a port, or for several ports, use the show controllers egressq port command in EXEC mode.
show controllers egressq port {port1 [port2] | all | limits max] 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.
Task ID
Examples
The following example shows how to display egress queue information for ports 1, 2, and 3 on the CPU node in slot 2:
RP/0/RP0/CPU0:router# show controllers egressq port 1 3 location 0/2/CPU0----------------------------------Port 1----------------------------------Max LB Tokens : 7812Max LB Limit Index : 38Quantum : 27Default Group : 2High Priority Group : N/ALow Priority Group : 2--------------------------------------------------------------------Port 2----------------------------------Port is not allocated----------------------------------Port 3----------------------------------Port is not allocatedTable 11 describes the significant fields shown in the display.
Related Commands
show controllers egressq queue
To display information about a specific egress queue, or a range of egress queues, use the show controllers egressq queue command in EXEC mode.
show controllers egressq queue {queue1 [queue2 | from-group {group-id | all} | from-interface {type instance | all} | from-port {port-id | all} | limits {max | min} | all] 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.
Task ID
Examples
The following example shows how to display information about egress queues 1 and 2 on the CPU node in slot 2:
RP/0/RP0/CPU0:router# show controllers egressq queue 1 2 location 0/2/CPU0----------------------------------Queue 1----------------------------------Group : 1Priority : LowMax LB Tokens : 7812Max LB Limit Index : 38Min LB Tokens : 0Min LB Limit Index : 0Quantum : 27Instantaneous length : 0Length high watermark : 0--------------------------------------------------------------------Queue 2----------------------------------Group : 2Priority : LowMax LB Tokens : 7812Max LB Limit Index : 38Min LB Tokens : 0Min LB Limit Index : 0Quantum : 27Instantaneous length : 0Length high watermark : 0Table 12 describes the significant fields shown in the display.
Related Commands
show controllers egressq statistics
To display egress queue manager statistics, use the show controllers egressq statistics command in EXEC mode.
show controllers egressq statistics location node-id
Syntax Description
location node-id
Identifies the location of the egress queue whose statistics you want to display. The node-id is expressed in the rack/slot/module notation.
Defaults
No default behavior or values
Command Modes
EXEC
Command History
Release 3.2
This command was introduced on the Cisco CRS-1.
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.
Task ID
Examples
The following example shows how to display egress queue manager statistics:
RP/0/RP0/CPU0:router# show controllers egressq statistics location 0/2/CPU0--------------------------------------------------Egressq Statistics--------------------------------------------------egressq ASIC version: 1egressq ASIC state: Normalplimasic link0 output packets: 0plimasic link0 output bytes: 0plimasic link1 output packets: 0plimasic link1 output bytes: 0plimasic link2 output packets: 0plimasic link2 output bytes: 0plimasic link3 output packets: 0plimasic link3 output bytes: 0cpuctrl input packets: 0cpuctrl output bytes: 1433250pse input packets: 29250pse dropped packets: 0cpuctrl dropped packets: 0--------------------------------------------------Table 13 describes the significant fields shown in the display.
Related Commands
show controllers ingressq statistics
To display ingress queue manager statistics, use the show controllers ingressq statistics command in EXEC mode.
show controllers ingressq statistics location node-id
Syntax Description
Defaults
No default behavior or values
Command Modes
EXEC
Command History
Release 3.2
This command was introduced on the Cisco CRS-1.
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.
Note
Task ID
Examples
The following example shows how to display ingress queue manager statistics:
RP/0/RP0/CPU0:router# show controllers ingressq statistics location 0/2/CPU0Ingressq Rx Statistics.------------------------------------------------------------------------rx pkts : 131827 ( 33509182 bytes)rx pkts from cpu : 102509 ( 16422606 bytes)rx control pkts from cpu : 102509 ( 16422606 bytes)rx data pkts from cpu : 0 ( 0 bytes)Ingressq Tx Statistics.------------------------------------------------------------------------tx pkts : 131826 ( 35086366 bytes)tx pkts to cpu : 29318 ( 17086576 bytes)tx control pkts to cpu : 29318 ( 17086576 bytes)tx data pkts to cpu : 0 ( 0 bytes)tx pkts shaped : 102508 ( 17999790 bytes)tx cells to fabric : 223190Ingressq Drops.------------------------------------------------------------------------length error drops - PSE : 0length error drops - Cpuctrl : 0crc error drops - PSE : 0crc error drops - Cpuctrl : 0OOR error drops - PSE : 0OOR error drops - Cpuctrl : 0discard drops : 0tail drops : 0tail drops - no QE : 0cell drops : 0Table 14 describes the significant fields shown in the display.
Related Commands
show controllers plim asic egress-channel bay
To display statistical information for the SPI4.2 transmit channel on a physical layer interface module (PLIM) ASIC, use the show controllers plim asic egress-channel bay command in EXEC mode.
show controllers plim asic egress-channel bay {0 | 1} channel channel_number [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.
Task ID
Examples
The following example shows sample output from the show controllers plim asic egress-channel bay command:
RP/0/0/CPU0:router# show controllers plim asic egress-channel bay 0 channel 0 location 0/4/CPU0Host bay 0 Tx SPI4.2 channel 0 :=============================================Ifname : DATA_PORT_0SPI4.2 Channel state : provisionedBay number : 0Tx SPI4.2 channel number : 0Internal Buffer number : 0SPI4.2 calendar entries : 1Buffer Almost Full Threshold : 0x2c00Tx Queuing ASIC port number : 0Table 15 describes the significant fields shown in the display.
1. System Packet Level Interface 4.2
show controllers plim asic ingress-channel bay
To display statistical information for the SPI4.2 receive channel on a physical layer interface module (PLIM) ASIC, use the show controllers plim asic ingress-channel bay command in EXEC mode.
show controllers plim asic ingress-channel bay {0 | 1} channel channel_number [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.
Task ID
Examples
The following example shows sample output from the show controllers plim asic ingress-channel bay command:
RP/0/0/CPU0:router# show controllers plim asic ingress-channel bay 0 channel 0 location 0/4/CPU0Host bay 0 Rx SPI4.2 channel 0 :============================================Ifname : DATA_PORT_0SPI4.2 Channel state : provisionedBay number : 0Rx SPI4.2 channel number : 0Internal Buffer number : 0Rx edram buffer start address : 0x0Rx edram buffer end address : 0x31fffRx edram buffer size : 0x32000Rx length buffer start address : 0x0Rx length buffer end address : 0x63ffRx length buffer size : 0x6400Number of calendar entries : 1Quantum : 209714RxEDRAM buffer threshold settings:==================================------------------ <-- Buffer Start (0x0)| ||------------------|<-- SPI4 AEmpty0 (0x6400)| || ||------------------|<-- SPI4 AEmpty1 (0xc800)| || || || || || ||------------------|<-- SPI4 AFull 0 (0x1f400)| || ||------------------|<-- SPI4 AFull 1 (0x25800)| || ||------------------|<-- Buffer Full (0x2bc00)| |------------------ <-- Buffer End (0x31fff)RxLen EDRAM buffer threshold settings:======================================------------------ <-- Buffer Start (0x0)| ||------------------|<-- SPI4 AEmpty0 (0xc80)| || ||------------------|<-- SPI4 AEmpty1 (0x1900)| || || || || || ||------------------|<-- SPI4 AFull 0 (0x3e80)| || ||------------------|<-- SPI4 AFull 1 (0x4b00)| || ||------------------|<-- Buffer Full (0x5780)| |------------------ <-- Buffer End (0x63ff)Table 16 describes the significant fields shown in the display.
1. System Packet Level Interface 4.2
show controllers plim asic spa bay
To display statistical information for the SPA ASIC, use the show controllers plim asic spa command in EXEC mode.
show controllers plim asic spa bay {bay-number} channel channel_number} [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.
Task ID
Examples
The following example shows sample output from the show controllers plim asic spa bay command:
RP/0/0/CPU0:router# show controllers plim asic spa bay 0 location 0/4/CPU0SPA 0 table:=======================================SPA OIR state : presentSPA state : enabledSPA allocated Rx buffer size : 4MBSPA available Rx buffer size : 0x20c000RxSPI PLL reset : inactiveHeader Format type : Format APad bytes : 0L2LA : 0Strict priority mode : activeEFC Manager : disabledSPA dual wide mode : inactiveMax SPA channels : 10PLIM loopback : inactiveSPI loopback : inactiveDatamaxT : 4096Training M : 16DIP2 Match : 3DIP2 Error : 3Tx SClk edge : fallingDIP4 Match : 15DIP4 Error : 2Rx SClk edge : risingSPI bus speed : 350MHzTx Burst size : 64 BytesRx Burst size sysdb : 80 BytesRx SPI state : enabledRx SPI sync state : inframeRx calendar mode : singleMaximun RxSPI channels : 10Tx SPI state : enabledTx SPI sync state : inframeTx calendar mode : singleMaximun Tx SPI4.2 channels : 5Table 17 describes the significant fields shown in the display.
1. Online Insertion and Removal
2. Extended Flow Control
3. 2-bit Diagonal Interleaved Parity
4. Security policy index
5. Megahertz
show controllers plim asic statistics
To display physical layer interface module (PLIM) ASIC statistics for a specific node or interface, use the show controllers plim asic statistics command in EXEC mode.
show controllers plim asic statistics {interface type instance | summary} [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.
Task ID
Examples
The following example shows how to display PLIM ASIC statistics information for a POS interface on a Cisco CRS-1:
RP/0/RP0/CPU0router# show controllers plim asic statistics interface POS 0/2/0/0Node: 0/2/CPU0-------------------------------------------------------------------------------POS0/2/0/0 Tx Statistics-------------------------------------------------------------------------------TotalOctets : 78904040 TotalPkts : 1622308Unicastpkts : 1622308 MulticastPkts : 0BroadcastPkts : 0 <64Octets : 161043364Octets : 0 65to127Octets : 11875128to255Octets : 0 256to511Octets : 0512to1023Octets : 0 1024to1518Octets : 01519to1548Octets : 0 1549to9216Octets : 0>9216Octet : 0 BadCRCPkts : 0802.1QPkts : 0 Underrun : 0Runt : 0 Giant : 0PausePkts : 0 Jabbers : 0DeferralAbort : 0 LateCollision : 0CollisionAbort : 0 OneCollision : 0MultiCollision : 0 TotalCollisions : 0TotalDefer : 0 LateCollisionAbort: 0LengthAbort : 0 TxBP count : 0POS0/2/0/0 Rx Statistics---------------------------------------------------------------------------------More-- failed to get statsTotalOctets : 91010808TotalPkts : 1815571 UnicastPkts : 1815571MulticastPkts : 0 BroadcastPkts : 064Octets : 63846 65to127Octets : 11844128to255Octets : 7 256to511Octets : 0512to1023Octets : 0 1024to1518Octets : 01519to1548Octets : 0 1549to9216Octets : 0>9216Octets : 0 BadCRCPkts : 0BadCodedPkts : 0 Runt : 0ShortPkts : 1739874 802.1QPkts : 0Drop : 0 PausePkts : 0ControlPkts : 0 Jabbers : 0BadPreamble : 0POS0/2/0/0 Drop-------------------------------------------------------------------------------RxFiFO Drop : 0 PAR Tail Drop : 0TxFIFO Drop : 0Table 18 describes the significant fields shown in the display.
show controllers plim asic summary
To display summarized physical layer interface module (PLIM) ASIC information for a specific node or interface, use the show controllers plim asic command in EXEC mode.
show controllers plim asic summary [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.
Task ID
Examples
The following example shows how to display summarized PLIM ASIC information for all locations:
RP/0/RP0/CPU0router# show controllers plim asic summaryNode: 0/1/CPU0--------------------------------------Instance# 0 Summary info:--------------------------------------Name : PLASPA Version : 2Port 0Jacket slot: 1 SPA type : SPA_NAME_UNKNOWNPort 1Jacket slot: 3 SPA type : SPA_NAME_UNKNOWNPort 2Jacket slot: 0 SPA type : 4xOC3 POS SPAInstance# 1 Summary info:--------------------------------------Name : PLASPA Version : 2Port 0Jacket slot: 2 SPA type : SPA_NAME_UNKNOWNPort 1Jacket slot: 4 SPA type : 4xOC48 POS/RPR HHSPAPort 2Jacket slot: 5 SPA type : 8xGE SPAIFName : POS0/1/0/0Inst# : 0 Port : 2RxLPORT : 0x80 TxLPORT : 0x48Uidb : 0x2 Key : 0x80Hkey : 209 Hkey idx : 0IFName : POS0/1/0/1Inst# : 0 Port : 2RxLPORT : 0x81 TxLPORT : 0x49Uidb : 0x4 Key : 0x81Hkey : 28 Hkey idx : 0IFName : POS0/1/0/2Inst# : 0 Port : 2RxLPORT : 0x82 TxLPORT : 0x4aUidb : 0x6 Key : 0x82Hkey : 183 Hkey idx : 0--More--Table 19 describes the significant fields shown in the display.
1. Universal interface descriptor block
show controllers pse eio links
To display packet switching engine (PSE) information for Elastic I/O (EIO) links, use the show controllers pse eio links command in EXEC mode.
show controllers pse eio links {link_number | all} [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.
Task ID
Examples
The following is sample output from the show controllers pse eio links command for a specific EIO link:
RP/0/RP0/CPU0:router# show controllers pse eio links 50 location 0/0/CPU0Node: 0/0/CPU0:----------------------------------------EIO link: 50-------------------------------------------------------------------ASIC Id Peer Id Type Link-Id Attempts Accept Failed State-------------------------------------------------------------------PSE_1 FABRICQ_0 RX 50 1 1 0 EIO_LINK_TRAINED-------------------------------------------------------------------Macro-id Windage Diag status-------------------------------------------------------------------0 4 0x00001 4 0x00002 4 0x00003 4 0x0000-------------------------------------------------------------------Table 20 describes the significant fields shown in the display.
Related Commands
show controllers pse ipc
To display packet switching engine (PSE) device information for interprocess communication (IPC) connections, or for a specific IPC controller, use the show controllers pse ipc command in EXEC mode.
show controllers pse ipc {client-connection {connID | all} | cpuctrlif} [egress | ingress]
[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.
To display client connection IPC information for a specific device instance, include the egress or ingress argument with the command, as shown in the following examples:
show controllers pse ipc client-connection connId egressshow controllers pse ipc client-connection connId ingressTo display client connection IPC information for a specific node location, include the location node-id argument with the command, as shown in the following example:
show controllers pse ipc client-connection connId location node-idTask ID
Examples
The following command shows how to display PSE information for a specific IPC client-connection:
RP/0/RP0/CPU0:router# show controllers pse ipc client-connection 13Node: 0/0/CPU0:----------------------------------------PSE IPC Conn Info:-------------------------------------------------ConnId: 13 (Backdoor)ConnOptions: 0Clinfos: 0x482bf9f8 (Notif) 0 (Reply)ConnStateFlags: 0ConnNotifFlags: 0SendReqs: 0 (iHP) 4 (iNP) 0 (eHP) 0 (eNP)SendFiltered: 0 (iHP) 0 (iNP) 0 (eHP) 0 (eNP)SendFailed: 0 (iHP) 0 (iNP) 0 (eHP) 0 (eNP)RecvReqs: 0RecvReqTouts: 0RecvDatTouts: 0RecvQState: 0/16Node: 0/3/CPU0:----------------------------------------PSE IPC Conn Info:-------------------------------------------------ConnId: 13 (Backdoor)ConnOptions: 0Clinfos: 0x482bf9f8 (Notif) 0 (Reply)ConnStateFlags: 0ConnNotifFlags: 0SendReqs: 0 (iHP) 4 (iNP) 0 (eHP) 0 (eNP)SendFiltered: 0 (iHP) 0 (iNP) 0 (eHP) 0 (eNP)SendFailed: 0 (iHP) 0 (iNP) 0 (eHP) 0 (eNP)RecvReqs: 0RecvReqTouts: 0RecvDatTouts: 0RecvQState: 0/16Table 21 describes the significant fields shown in the display.
The following command shows how to display PSE information for a specific IPC controller connection:
RP/0/RP0/CPU0:router# show controllers pse ipc cpuctrlifNode: 0/0/CPU0:----------------------------------------Pse IPC cpuctrl if Information-------------------------------------------------Cpuctrl interface is upNormal Priority Tx I/F:BufBase 0x112190 BufSize 32768 PadBufp 0xec0af118 Seqnum 854RORegNum 10 RORegVal 0x49f0 WORegNum 2 WORegVal 0x49f0CDMACh 0 CDMAQ 3HoldQ 0/512 CDMAPendQ 0/128 UnackQ 0/256NumEnqs 854 NumRejs 0 NumDmaReqFails 0NumDmaPendFails 0 NumMbxSpcFails 0 NumHldqOvflows 0Normal Priority Rx I/F:NumPDMAEntries 64 NumEnqs 15 NumRejs 0Pse IPC cpuctrl if Information-------------------------------------------------Cpuctrl interface is upNormal Priority Tx I/F:BufBase 0x112190 BufSize 32768 PadBufp 0xec0af14c Seqnum 424RORegNum 10 RORegVal 0x1c60 WORegNum 2 WORegVal 0x1c60CDMACh 1 CDMAQ 3HoldQ 0/512 CDMAPendQ 0/128 UnackQ 0/256NumEnqs 424 NumRejs 0 NumDmaReqFails 0NumDmaPendFails 0 NumMbxSpcFails 0 NumHldqOvflows 0Normal Priority Rx I/F:NumPDMAEntries 64 NumEnqs 2 NumRejs 0Node: 0/3/CPU0:----------------------------------------Pse IPC cpuctrl if Information-------------------------------------------------Cpuctrl interface is upNormal Priority Tx I/F:BufBase 0x112190 BufSize 32768 PadBufp 0xec0af118 Seqnum 833RORegNum 10 RORegVal 0xdb8 WORegNum 2 WORegVal 0xdb8CDMACh 0 CDMAQ 3HoldQ 0/512 CDMAPendQ 0/128 UnackQ 0/256NumEnqs 833 NumRejs 0 NumDmaReqFails 0NumDmaPendFails 0 NumMbxSpcFails 0 NumHldqOvflows 0Normal Priority Rx I/F:NumPDMAEntries 64 NumEnqs 9 NumRejs 0Pse IPC cpuctrl if Information-------------------------------------------------Cpuctrl interface is upNormal Priority Tx I/F:BufBase 0x112190 BufSize 32768 PadBufp 0xec0af14c Seqnum 409RORegNum 10 RORegVal 0x5f70 WORegNum 2 WORegVal 0x5f70CDMACh 1 CDMAQ 3HoldQ 0/512 CDMAPendQ 0/128 UnackQ 0/256NumEnqs 409 NumRejs 0 NumDmaReqFails 0NumDmaPendFails 0 NumMbxSpcFails 0 NumHldqOvflows 0Normal Priority Rx I/F:NumPDMAEntries 64 NumEnqs 2 NumRejs 0Table 22 describes the significant fields shown in the display.
Related Commands
show controllers pse mp
To display packet switching engine (PSE) information for the maintenance processor on a specific controller or node, use the show controllers pse mp command in EXEC mode.
show controllers pse mp [egress | ingress] [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.
The instance and location optional keywords are not mutually exclusive. The instance keyword directs the command to a specific PSE device, and the location keyword directs the command to that device or devices on the specified modular services card. You can specify the instance and location options together in the same command. If you do not specify the instance {0 | 1} and location node-id arguments, the show controllers pse mp command takes effect on both device instances on all modular services cards.
Task ID
