Table Of Contents
ASIC Driver Commands on Cisco IOS XR Software
asic-scan pse
clear controller egressq queue
clear controller egressq queue all
clear controller egressq statistics
clear controller pse statistics
show controllers cpuctrl cdma
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 port
show controllers egressq queue
show controllers egressq statistics
show controllers ingressq statistics
show controllers plim asic
show controllers pse eio links
show controllers pse ipc
show controllers pse mp
show controllers pse statistics
show controllers pse summary
show packet-memory
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 pse
To run a generic ASIC scan on the Packet Switching Engine (PSE), use the asic-scan pse command in EXEC mode.
asic-scan pse {egress | ingress} [disable | enable | help-subblock | subblock_number [error_cause
[disable | enable] | disable | enable | help_cause] | quick-scan [filename [filename] | allscan}
location node-id
Syntax Description
egress
|
Runs the ASIC scan on the egress PSE device.
|
ingress
|
Runs the ASIC scan on the ingress PSE device.
|
disable
|
(Optional) Disables the ASIC scan on all sub-blocks.
|
enable
|
(Optional) Enables the ASIC scan on all sub-blocks.
|
help-subblock
|
(Optional) Lists all sub-block numbers.
|
subblock_number error_cause [disable | enable]
|
(Optional) Enables or disables the ASIC scan on a specific error cause in the specified sub-block.
Replace subblock_number with the number that identifies the sub-block on which to enable of disable the ASIC scan. Replace error_cause with the number that identifies an error cause in the specified sub-block.
|
subblock_number disable
|
(Optional) Disables the ASIC scan on the specified sub-block
|
subblock_number enable
|
(Optional) Enables the ASIC scan on the specified sub-block
|
subblock_number help_cause
|
(Optional) Lists all block numbers in the specified sub-block.
|
quick-scan filename
|
(Optional) Performs a quick ASIC scan on a specific file. Replace filename with the name of the .xsvf file on which to run the quick ASIC scan
|
filename
|
Name of the file on which to write the ASIC scan output.
|
quick-scan allscan
|
(Optional) Performs a quick ASIC scan on all bits of the chip, including the preread for Metro.
|
location node-id
|
Identifies the location of the node hosting the PSE on which to run the ASIC scan. The node-id is expressed in the rack/slot/module notation.
Note Use 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.
|
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
Task ID
|
Operations
|
drivers
|
read, write
|
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/CPU0
quick_scan: {'sysdb' detected the 'warning' condition 'An EDM took too long to process a
request and was timed out'} Scan in progress... Please wait for completion mesaage
The following command shows how to run an ASIC scan on the ingress PSE device that is located on the CPU node in slot 1:
RP/0/RP0/CPU0:P2_CRS-8# asic-scan pse ingress location 0/1/CPU0
clear 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
queue-id1
|
Queue you want to clear. Replace queue-id1 with a queue number. Range is from 1 through 8191.
|
queue-id2
|
(Optional) Last queue in a range of queues to clear. Replace queue-id2 with a queue number. Range is from 1 through 8191.
|
location node-id
|
Identifies the location of the node whose egress queue you want to clear. The node-id is expressed in the rack/slot/module notation.
Note Use 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.
|
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
Task ID
|
Operations
|
root-system
|
read
|
basic-services
|
read, write
|
drivers
|
read, write
|
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/CPU0
Related 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
all
|
Clears all egress queues in the specified location.
|
location node-id
|
Identifies the location of the egressq queue you want to clear. The node-id is expressed in the rack/slot/module notation.
Note Use 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.
|
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
Task ID
|
Operations
|
root-system
|
read
|
basic-services
|
read, write
|
drivers
|
read, write
|
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/CPU0
Related 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
location node-id
|
Identifies the location of the egressq queue whose statistics you want to clear. The node-id is expressed in the rack/slot/module notation.
Note Use 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.
|
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
Task ID
|
Operations
|
drivers
|
read, write
|
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/CPU0
Related Commands
clear controller pse statistics
To clear statistics maintained by the packet switching engine (PSE) on a specific PSE device instance, or on a specific node, use the clear controller pse statistics command in EXEC mode.
clear controller pse statistics [instance {0 | 1}] [location node-id]
Syntax Description
instance {0 | 1}
|
(Optional) Identifies the PSE device whose statistics you want to clear.
Enter 0 to specify the ingress PSE device, or enter 1 to specify the egress PSE device.
Note Follow the instance {0 | 1} argument with the location node-id argument to restrict the command to specific node containing the specified device instance.
|
location node-id
|
(Optional) Identifies the location of the node whose PSE device statistics you want to clear. The node-id is expressed in the rack/slot/module notation.
Note Use the show platform command to see the location of all nodes installed in the router.
Note Include the instance {0 | 1} argument before the location node-id argument to restrict the command to a specific device instance on the specified node.
|
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.
|
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 keyword directs the clear controller pse statistics command to a specific PSE device, and the location keyword directs the clear controller pse statistics command to that device or devices on the specified modular services card. You can specify the instance and location keywords together in the same command. If the instance and location keywords are not specified, the
clear controller pse statistics command takes effect on both device instances on all modular services cards.
Task ID
Task ID
|
Operations
|
root-system
|
execute
|
drivers
|
read, write
|
Examples
The following example shows how to clear PSE statistics on a specific instance of the controller (instance 1):
RP/0/RP0/CPU0:router# clear controller pse statistics instance 1
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/CPU0
Related Commands
show controllers cpuctrl cdma
To display information about the CPU controller Code Division Multiplex Access (CDMA) engine, use the show controllers cpuctrl cdma command in EXEC mode.
show controllers cpuctrl cdma {all | cdma0 {queue | all} | cdma1 {queue | all} {active | detail}
[location node-id]
Syntax Description
all
|
Displays CDMA information for channel 0 and channel 1.
|
cdma0 queue
|
Displays CDMA information for a specific Division Multiplex Access (DMA) queue on channel 0. Replace queue with a number. Range is from 1 through 7.
|
cdma0 all
|
Displays CDMA engine information for all DMA queues on channel 0.
|
cdma1 queue
|
Displays CDMA information for a specific Division Multiplex Access (DMA) queue on channel 1. Replace queue with a number. Range is from 1 through 7.
|
cdma1 all
|
Displays CDMA engine information for all DMA queues on channel 1.
|
active
|
Displays descriptions for active DMA queues only.
|
detail
|
Displays descriptions for any DMA queues, regardless of whether they are active.
|
location node-id
|
(Optional) Identifies the location of the node whose CPU controller CDMA 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
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.
|
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
Task ID
|
Operations
|
drivers
|
read
|
Examples
The following example shows how to display CPU controller CDMA information from the active DMA queues on channel 1:
RP/0/RP0/CPU0:router# show controllers cpuctrl cdma cdma0 1 active
---------------------------------------------------------------
client handle: 1 queue state: Active
OS Interrupt Level:108 Cpuctrl Interrupt Level:12
OS Run Priority:45 Queue Created 1 times
CDMA out_of_desc failures = 0
CDMA transactions = 3, Bytes DMA'd = 67584
ISR pointer is at 0x78043224 Descriptor List at 0xec032300
Pakman/Bufman Instance: /dev/bufman/misc
client callback function pointer 0x48203424
client cleanup function pointer 0x48203424
Queue descriptor list info:
list_size=32 current_index=3 tx_index=3
active descriptors number:0
---------------------------------------------------------------
client handle: 1 queue state: Active
OS Interrupt Level:108 Cpuctrl Interrupt Level:12
OS Run Priority:45 Queue Created 1 times
CDMA out_of_desc failures = 0
CDMA transactions = 3, Bytes DMA'd = 67584
ISR pointer is at 0x7804316c Descriptor List at 0xec032300
Pakman/Bufman Instance: /dev/bufman/misc
client callback function pointer 0x48203424
client cleanup function pointer 0x48203424
Queue descriptor list info:
list_size=32 current_index=3 tx_index=3
active descriptors number:0
---------------------------------------------------------------
client handle: 1 queue state: Inactive
---------------------------------------------------------------
client handle: 1 queue state: Inactive
Table 36 describes the significant fields shown in the display.
Table 36 show controllers cpuctrl cdma Field Descriptions
Field
|
Description
|
DMA queue
|
Identifies the DMA queue.
|
Channel
|
Identifies the channel whose DMA queue is displayed. 0 is the ingress channel, and 1 is the egress channel
|
queue
|
Identifies the queue.
|
client handle
|
Internal identifier for the Cisco client.
|
queue state
|
Current state of the queue.
|
OS Interrupt Level
|
Current interrupt level for the queue.
|
Cpuctrl Interrupt Level
|
Current interrupt level for the CPU controller.
|
OS Run Priority
|
Run priority level for this queue.
|
Queue Created 1 times
|
Number of times this queue was regenerated.
|
Pakmode
|
Information about internal data structures and parameters.
|
CDMA out_of_desc failures
|
Number of CDMA1 failures in the queue.
|
CDMA transactions
|
Number of CDMA transactions in the queue.
|
Bytes DMA'd
|
Number of bytes that have been processed by the Division Multiplex Access engine.
|
DMA IWA
|
Number of IWA bytes that have been processed by the Division Multiplex Access engine.
|
ISR pointer is at
|
Internal information about the location of the ISR2 pointer.
|
Descriptor List at
|
Internal information about the location of the descriptor list.
|
Pakman/Bufman Instance
|
Internal information about the location of the Pakman and Bufman Instance.
|
client callback function pointer
|
Internal information about the client callback function pointer.
|
client cleanup function pointer
|
Internal information about the client cleanup function pointer.
|
Queue descriptor list info
|
Internal information about the queue descriptor list.
|
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 {plim asic | dcc | egressq | fabricq | fia | ingressq |
jacketcard | mipc | plim | plimasic | pse | reindeer} | pdma {diag | fia | frr | gsp| mipc | mstats
| netflow | netio}} {active | detail} [location node-id]
Syntax Description
all
|
Displays a summary information for all clients on the router.
|
cdma
|
Displays information about Code Division Multiplex Access (CDMA) clients only.
|
dcc
|
Displays information for the dcc client.
|
egressq
|
Displays information for the egressq client.
|
fabricq
|
Displays information for the Fabricq ASIC client.
|
fia
|
Displays information for the Fabric Interface ASIC (FIA) client.
|
ingressq
|
Displays information for the ingressq ASIC client.
|
jacketcard
|
Displays information for the jacketcard client.
|
mipc
|
Displays information for the Marvel interprocess communication (MIPC) client.
|
plim
|
Displays information for the plim client.
|
plimasic
|
Displays information for the plim ASIC client.
|
pse
|
Displays information for the pse client.
|
reindeer
|
Displays information for the reindeer client.
|
pdma
|
Displays information for Provisioning-Driven Memory Administration (PDMA) clients only.
|
diag
|
Displays information for the PDMA client called DIAG packet.
|
fia
|
Displays information for the Fabric Interface ASIC packet PDMA client.
|
frr
|
Displays information for the Fast Reroute (FRR) packet PDMA client.
|
gsp
|
Displays information for the Global Support Partner (GSP) packet PDMA client.
|
mipc
|
Displays information for the MIPC packet PDMA client.
|
mstats
|
Displays information for the MSTATS packet PDMA client.
|
netflow
|
Displays information for the NETFLOW packet PDMA client.
|
netio
|
Displays information for the NETIO packet PDMA client.
|
active
|
Displays descriptions for active queues only.
|
detail
|
Displays descriptions for any queues, regardless of whether they are active.
|
location node-id
|
(Optional) Identifies the location of the node whose 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
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.
|
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
Task ID
|
Operations
|
drivers
|
read
|
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: 10
isr_count: 0 queue_count: 0
-------------------------------------------------------------
client_name: plimasic client_handle: 10
isr_count: 0 queue_count: 0
-------------------------------------------------------------
client_name: plim asic client_handle: 10
isr_count: 0 queue_count: 0
-------------------------------------------------------------
client_name: plim asic client_handle: 10
isr_count: 0 queue_count: 0
Table 37 describes the significant fields shown in the display.
Table 37 show controllers cpuctrl clients Field Descriptions
Field
|
Description
|
client
|
Client type that whose information is displayed. Can be DMA1 or PKT.
|
client_name
|
Identifies the client whose information is displayed.
|
client_handle
|
Internal client identifier.
|
isr_count
|
ISR2 counters.
|
queue_count
|
Queue counters.
|
client_pid
|
Client PID3.
|
Related Commands
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 {egressq | epse | fabricq0| fabricq1 | fabricq2 | fabricq3 |
fia0 | fia1 | ingressq | ipse | jacketcard0 | jacketcard1 | jacketcard2 | plimasic0 | plimasic1 |
plimasic2 | plimasic3 | plimfpga} {pdma queue {all | tx | rx} {active | detail} | pio}
[location node-id]
Syntax Description
egressq
|
Displays information about the egressq ASIC instance 0.
|
epse
|
Displays information about the egress packet switching engine (PSE) ASIC.
|
fabricq0
|
Displays information about the fabricq ASIC instance 0.
|
fabricq1
|
Displays information about the fabricq ASIC instance 1.
|
fabricq2
|
Displays information about the fabricq ASIC instance 2.
|
fabricq3
|
Displays information about the fabricq ASIC instance 3.
|
fia0
|
Displays information about the Fabric Interface ASIC (FIA) instance 0.
|
fia1
|
Displays information about the FIA instance 1.
|
ingressq
|
Displays information about the ingressq ASIC.
|
ipse
|
Displays information about the ingress packet switching engine (PSE) ASIC.
|
jacketcard0
|
Displays information about the jacketcard0 ASIC.
|
jacketcard1
|
Displays information about the jacketcard1 ASIC.
|
jacketcard2
|
Displays information about the jacketcard2 ASIC.
|
plimasic0
|
Displays information about the PLIM ASIC instance 0.
|
plimasic1
|
Displays information about the PLIM ASIC instance 1.
|
plimasic2
|
Displays information about the PLIM ASIC instance 2.
|
plimasic3
|
Displays information about the PLIM ASIC instance 3.
|
plimfpga
|
Displays information about the field-programmable gate array (FPGA) PLIM.
|
pdma queue all
|
Displays transmit and receive Provisioning-Driven Memory Administration (PDMA) information for the specified queue. Replace queue with a queue number. The range is from 1 through 7.
|
pdma queue tx
|
Displays transmit PDMA information only for the specified queue. Replace queue with a queue number. The range is from 1 through 7.
|
pdma queue rx
|
Displays receive PDMA information only for the specified queue. Replace queue with a queue number. The range is from 1 through 7.
|
pdma all
|
Displays transmit and receive PDMA information for all queues.
|
active
|
Displays descriptions for active queues only.
|
detail
|
Displays detailed descriptions for any queues, regardless of whether they are active.
|
pio
|
Displays transmit and receive Polled I/O (PIO) information for the specified queue.
|
location node-id
|
(Optional) Identifies the location of the node whose 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
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.
|
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
Task ID
|
Operations
|
drivers
|
read
|
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
---------------------------------------------------------------
cpuctrl net Port: 7 queue: 0
client handle: 6 queue state: Active
OS Interrupt Level:127 Cpuctrl Interrupt Level:31
OS Run Priority:20 Queue Created 1 times
Tx out_of_desc failures = 0
Packets transmitted = 0, Byte transmitted = 0
ISR pointer is at 0x7804372c Descriptor List at 0xec27b060
Pakman/Bufman Instance: /dev/pakman/server
client callback function pointer 0x00000000
client cleanup function pointer 0x00000000
Queue descriptor list info:
list_size=1024 current_index=0 tx_index=0
active descriptors number:0
---------------------------------------------------------------
cpuctrl net Port: 0 queue: 1
client handle: 6 queue state: Inactive
---------------------------------------------------------------
cpuctrl net Port: 0 queue: 2
client handle: 6 queue state: Inactive
---------------------------------------------------------------
cpuctrl net Port: 0 queue: 3
client handle: 6 queue state: Inactive
---------------------------------------------------------------
cpuctrl net Port: 0 queue: 4
client handle: 6 queue state: Inactive
---------------------------------------------------------------
cpuctrl net Port: 0 queue: 5
client handle: 6 queue state: Inactive
---------------------------------------------------------------
cpuctrl net Port: 0 queue: 6
client handle: 6 queue state: Inactive
---------------------------------------------------------------
cpuctrl net Port: 0 queue: 7
client handle: 6 queue state: Inactive
---------------------------------------------------------------
cpuctrl net Port: 7 queue: 0
client handle: 3 queue state: Active
Table 38 describes the significant fields shown in the display.
Table 38 show controllers cpuctrl devices Field Descriptions
Field
|
Description
|
PKT queue:
|
Displays whether the packet queue is TX1 or RX2.
|
cpuctrl net Port
|
Identifies the CPU controller port.
|
queue
|
Identifies the queue whose CPU controller device information is displayed.
|
client handle
|
Internal Cisco client identifier.
|
queue state
|
Current state of the queue. The queue can be Active or Inactive.
|
Related Commands
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
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.
|
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
Task ID
|
Operations
|
drivers
|
read
|
Examples
The following example shows how to display information about the internal CPU controller:
RP/0/RP0/CPU0:router# show controllers cpuctrl internal
Cpuctrl Internal Info for node 0/0/CPU0:
Error Interrupts = 0 Spurious Error Interrupts = 0
PCI Error Overflows = 0 PCI PM Error Overflows = 0
PCIX Error Overflows = 0 Internal Access PCI Overflows = 0
Port Error Overflows = 0 Error Log Overflows = 0
cpuctrl Config Reg = 0x8357ffff cpuctrl Physical Offset = 0x80000000
cpuctrl Window Size = 0x40000000 cpuctrl Port Window Size = 0x04000000
cpuctrl SHMem Size = 0x00800000 cpuctrl SHMem Used = 0x00223ee8
cpuctrl version info: Squid FPGA v2.07 Fri Jan 23 16:21:01 2004 ykoren
Cpuctrl Internal Info for node 0/3/CPU0:
Error Interrupts = 0 Spurious Error Interrupts = 0
PCI Error Overflows = 0 PCI PM Error Overflows = 0
PCIX Error Overflows = 0 Internal Access PCI Overflows = 0
Port Error Overflows = 0 Error Log Overflows = 0
cpuctrl Config Reg = 0x8357ffff cpuctrl Physical Offset = 0x80000000
cpuctrl Window Size = 0x40000000 cpuctrl Port Window Size = 0x04000000
cpuctrl SHMem Size = 0x00800000 cpuctrl SHMem Used = 0x00223ee8
cpuctrl version info: Squid FPGA v2.07 Fri Jan 23 16:21:01 2004 ykoren
Cpuctrl Internal Info for node 0/RP0/CPU0:
Error Interrupts = 0 Spurious Error Interrupts = 0
PCI Error Overflows = 0 PCI PM Error Overflows = 0
PCIX Error Overflows = 0 Internal Access PCI Overflows = 0
Port Error Overflows = 0 Error Log Overflows = 0
cpuctrl Config Reg = 0x803f007f cpuctrl Physical Offset = 0x80000000
cpuctrl Window Size = 0x40000000 cpuctrl Port Window Size = 0x04000000
cpuctrl SHMem Size = 0x00800000 cpuctrl SHMem Used = 0x00223ee8
cpuctrl version info: Squid FPGA v2.07 Fri Feb 6 17:49:22 2004 ykoren
Cpuctrl Internal Info for node 0/RP1/CPU0:
Error Interrupts = 0 Spurious Error Interrupts = 0
PCI Error Overflows = 0 PCI PM Error Overflows = 0
PCIX Error Overflows = 0 Internal Access PCI Overflows = 0
Port Error Overflows = 0 Error Log Overflows = 0
cpuctrl Config Reg = 0x003f007f cpuctrl Physical Offset = 0x80000000
cpuctrl Window Size = 0x40000000 cpuctrl Port Window Size = 0x04000000
cpuctrl SHMem Size = 0x00800000 cpuctrl SHMem Used = 0x00223ee8
cpuctrl version info: Squid FPGA v2.05 Wed Sep 3 17:37:47 2003 ykoren
Table 39 describes the significant fields shown in the display.
Table 39 show controllers cpuctrl internal Field Descriptions
Field
|
Description
|
Error Interrupts
|
Total of error interrupts that have occurred on this node.
|
Spurious Error Interrupts
|
Current number interrupts that have occurred on this node due to spurious errors.
|
PCI Error Overflows
|
Number of times the PCI1 error buffer overflowed on the node.
Note When an overflow occurs, packets may be dropped.
|
PCI PM Error Overflows
|
Number of times PCI PM2 errors buffer overflowed on this node.
Note When an overflow occurs, packets may be dropped.
|
PCIX Error Overflows
|
Number of times the PCI IX error buffer overflowed on this node.
Note When an overflow occurs, packets may be dropped.
|
Internal Access PCI Overflows
|
Number of times the Internal Access PCI buffer overflowed on this node.
Note When an overflow occurs, packets may be dropped.
|
Port Error Overflows
|
Number of times the port error buffer overflowed on this node.
Note When an overflow occurs, packets may be dropped.
|
Error Log Overflows
|
Number of times the error log buffer overflowed on this node.
Note When an overflow occurs, packets may be dropped.
|
cpuctrl Config Reg
|
CPU controller configuration register, expressed in hexadecimal format.
|
cpuctrl Physical Offset
|
CPU controller physical offset, expressed in hexadecimal format.
|
cpuctrl Window Size
|
CPU controller window size, expressed in hexadecimal format. CPU controller performance improves as window size increases.
|
cpuctrl Port Window Size
|
CPU controller port window size, expressed in hexadecimal format. CPU controller port performance improves as window size increases.
|
cpuctrl SHMem Size
|
CPU controller SH memory size, expressed in hexadecimal format.
|
cpuctrl SHMem Used
|
CPU controller SH memory that has been used already, expressed in hexadecimal format.
|
cpuctrl version info
|
Provides version information for the CPU controller. The information displayed is:
• Squid version
• Date of the last version install or upgrade
• ID of the user who performed the install or upgrade.
|
Related Commands
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 {cpuctrl | egressq| epse | fabricq0 | fabricq1 | fabricq2 |
fabricq3 | fia0 | fia1 | ingressq | ipse | jacketcard0 | jacketcard1 | jacketcard2 | plimasic0 |
plimasic1 | plimasic2 | plimasic3 | reindeer} {pdma queue-id {all | rx | tx} {active | detail}
| pio} [location node-id]
Syntax Description
cpuctrl
|
Displays port information for the CPU controller ASIC instance 0.
|
egressq
|
Displays port information for the egressq ASIC instance 0.
|
epse
|
Displays port information for the egress packet switching engine (EPSE) ASIC.
|
fabricq0
|
Displays port information for the fabricq ASIC instance 0.
|
fabricq1
|
Displays port information for the fabricq ASIC instance 1.
|
fabricq2
|
Displays port information for the fabricq ASIC instance 2.
|
fabricq3
|
Displays port information for the fabricq ASIC instance 3.
|
fia0
|
Displays port information for the fabric Interface ASIC (FIA) instance 0.
|
fia1
|
Displays port information for the fabric Interface ASIC (FIA) instance 1.
|
ingressq
|
Displays port information for the ingressq ASIC.
|
ipse
|
Displays port information for the ingress packet switching engine (PSE) ASIC.
|
jacketcard0
|
Displays port information for the jacketcard0 ASIC.
|
jacketcard1
|
Displays port information for the jacketcard1 ASIC.
|
jacketcard2
|
Displays port information for the jacketcard2 ASIC.
|
plimasic0
|
Displays port information for instance 0 of the plim ASIC.
|
plimasic1
|
Displays port information for instance 1 of the plim ASIC.
|
plimasic2
|
Displays port information for instance 2 of the plim ASIC.
|
plimasic3
|
Displays port information for instance 3 of the plim ASIC.
|
reindeer
|
Displays port information for the reindeer ASIC.
|
pdma queue-id all
|
Displays transmit and receive Provisioning-Driven Memory Administration (PDMA) information for the specified queue.
|
pdma queue-id tx
|
Displays transmit PDMA information only for the specified queue. The information displayed pertains to the ASIC indicated in the show controllers cpuctrl ports command.
|
pdma queue-id rx
|
Displays receive PDMA information only for the specified queue. The information displayed pertains to the ASIC indicated in the show controllers cpuctrl ports command.
|
pdma all
|
Displays transmit and receive PDMA information for all queues. The information displayed pertains to the ASIC indicated in the show controllers cpuctrl ports command.
|
active
|
Displays descriptions for active queues only.
|
detail
|
Displays descriptions for any queues, regardless of whether they are active.
|
pio
|
Displays transmit and receive Polled I/O (PIO) information for the specified queue.
|
location node-id
|
(Optional) Identifies the location of the node whose CPU controller port 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
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.
|
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
Task ID
|
Operations
|
drivers
|
read
|
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 pio
client name: PSE device instance: 1
cpuctrl net port: 6 pci base: 0x98000000
map reg: 0x6076a12c OS interrupt level: 102
Cpuctrl interrupt level: 6 OS Run priority: 6
config reg: 0x00000000 channels reg: 0x00000000
int_cause_asic_mask: 0x00000010 int_cause_error_mask: 0x00000020
int_cause_link_error_mask: 0x00000040
crc_errors: 0 sync_errors: 0 reframe_events: 0
client name: PSE device instance: 1
cpuctrl net port: 6 pci base: 0x98000000
map reg: 0x6076a12c OS interrupt level: 102
Cpuctrl interrupt level: 6 OS Run prority: 6
config reg: 0x00000000 channels reg: 0x00000000
int_cause_asic_mask: 0x00000010 int_cause_error_mask: 0x00000020
int_cause_link_error_mask: 0x00000040
crc_errors: 0 sync_errors: 0 reframe_events: 0
device PSE instance 1 is not detected on node 201/
Table 40 describes the significant fields shown in the display.
Table 40 show controllers cpuctrl ports Field Descriptions
Field
|
Description
|
client name
|
Identifies the client whose port CPU controller information is displayed.
|
device instance
|
The client's device instance for which the port CPU controller information is displayed.
|
cpuctrl net port
|
Identifies the CPU controller net port.
|
pci base
|
PCI1 base.
|
map reg
|
Client map register.
|
OS interrupt level
|
Level of Cisco IOS XR interrupt configured for the port. Interrupts are triggered by arrival of a packet that causes the CPU to postpone other tasks and handle the packet.
|
Cpuctrl interrupt level
|
Level of CPU controller interrupt configured for the port.
|
OS Run priority
|
Cisco IOS XR priority.
|
config reg
|
Configuration register, expressed in hexadecimal format.
|
channels reg
|
Channel register, expressed in hexadecimal format.
|
int_cause_asic_mask
|
Internal ASIC masking information.
|
int_cause_error_mask
|
Internal error masking information.
|
int_cause_link_error_mask
|
Internal link error masking information.
|
crc_errors
|
Number of CRC2 errors that have occurred on this port.
|
sync_errors
|
Number of synchronization errors that have occurred on this port.
|
reframe_events
|
Number of reframe events that have occurred on this port.
|
Related Commands
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
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.
|
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
Task ID
|
Operations
|
drivers
|
read
|
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/CPU0
Cpuctrl 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: 0
Cpuctrl net port: 3 pci_base: 0x8c000000
-----------------------------------------------------------
device_name: Fabricq device instance: 1
Cpuctrl net port: 4 pci_base: 0x90000000
-----------------------------------------------------------
device_name: Ingressq device instance: 0
Cpuctrl net port: 8 pci_base: 0xa0000000
-----------------------------------------------------------
device_name: Egressq device instance: 0
Cpuctrl net port: 7 pci_base: 0x9c000000
-----------------------------------------------------------
device_name: FIA device instance: 0
Cpuctrl net port: 1 pci_base: 0x84000000
-----------------------------------------------------------
device_name: FIA device instance: 1
Cpuctrl net port: 2 pci_base: 0x88000000
-----------------------------------------------------------
device_name: Cpuctrl device instance: 0
Cpuctrl net port: 0 pci_base: 0x80000000
-----------------------------------------------------------
device_name: PSE device instance: 1
Cpuctrl net port: 6 pci_base: 0x98000000
Table 41 describes the significant fields shown in the display.
Table 41 show controllers cpuctrl summary Field Descriptions
Field
|
Description
|
device_name
|
Identifies the device whose CPU controller information is displayed.
|
device instance
|
Identifies the CPU device whose information is displayed. Can be 0 or 1.
|
Cpuctrl net port
|
Identifies the CPU controller network port.
|
pci_base
|
PCI1 base, in hexadecimal format.
|
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
link-id
|
Identifies the EIO link whose egress queueing ASIC information you want to display. Replace link-id with a link identifier. Range is from 0 through 4294967295.
|
all
|
Displays egress queueing ASIC information for all links on the specified node.
|
location node-id
|
Identifies the location of the egress queue manager whose EIO link 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
Release
|
Modification
|
Release 3.2
|
This command was introduced on the Cisco CRS-1.
|
Release 3.3.0
|
No modification.
|
Usage Guidelines
To use this command, you must be in a user group associated with a task group that includes the proper task IDs. For detailed information about user groups and task IDs, see the Configuring AAA Services on Cisco IOS XR Software module of the Cisco IOS XR System Security Configuration Guide.
Task ID
Task ID
|
Operations
|
interface
|
read
|
drivers
|
read
|
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/CPU0
----------------------------------------
-------------------------------------------------------------------
ASIC Id Peer Id Type Link-Id Attempts Accept Failed State
-------------------------------------------------------------------
EGRESSQ_0 PSE_1 RX 11 1 1 0 EIO_LINK_TRAINED
EGRESSQ_0 PSE_1 TX 64 0 0 0 EIO_LINK_TRAINED
EGRESSQ_0 PLIM-ASIC_0 TX 60 0 0 0 EIO_LINK_TRAINED
EGRESSQ_0 PLIM-ASIC_1 TX 61 0 0 0 EIO_ADD_LINK
EGRESSQ_0 PLIM-ASIC_2 TX 62 0 0 0 EIO_ADD_LINK
EGRESSQ_0 PLIM-ASIC_3 TX 63 0 0 0 EIO_ADD_LINK
Table 42 describes the significant fields shown in the display.
Table 42 show controllers egressq eio links Field Descriptions
Field
|
Description
|
ASIC Id
|
Identifies the ASIC that is associated with the link whose information is displayed.
|
Peer Id
|
Identifies the ASIC peer.
|
Type
|
Indicates whether the AISC is receiving (RX) or transmitting (TX).
|
Link-Id
|
Link identifier.
|
Attempts
|
Number of attempts made to send or receive information on the specified link.
|
Accept
|
Number of consecutive EIO requests for the link made by the PSE driver to the peer that were accepted.
|
Failed
|
Number of consecutive EIO requests for the link that failed.
|
State
|
Current link state.
|
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
group1
|
First group whose information you want to display.
|
group2
|
(Optional) Last group whose information you want to display.
|
all
|
Indicates that you want to display information about all egress queue groups on a specific node.
|
limits
|
Indicates that you want to display the limits table. Follow the keyword with max to display the maximum limits table, or min to display the minimum limits table.
|
max
|
Display the maximum limits table.
|
min
|
Display the minimum limits table.
|
location node-id
|
Identifies the location of the egress queue whose group information you want to display.
|
Defaults
No default behavior or values
Command Modes
EXEC
Command History
Release
|
Modification
|
Release 3.2
|
This command was introduced on the Cisco CRS-1.
|
Release 3.3.0
|
No modification.
|
Usage Guidelines
To use this command, you must be in a user group associated with a task group that includes the proper task IDs. For detailed information about user groups and task IDs, see the Configuring AAA Services on Cisco IOS XR Software module of the Cisco IOS XR System Security Configuration Guide.
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
Task ID
|
Operations
|
interface
|
read
|
drivers
|
read
|
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
----------------------------------
----------------------------------
High Priority Queue : N/A
----------------------------------
----------------------------------
----------------------------------
High Priority Queue : N/A
----------------------------------
----------------------------------
----------------------------------
High Priority Queue : N/A
----------------------------------
Table 43 describes the significant fields shown in the display.
Table 43 show controllers egressq group Field Descriptions
Field
|
Description
|
Port
|
Port identifier.
|
Priority
|
Group priority.
|
Max LB Tokens
|
Maximum number of port LB tokens.
|
Max LB Limit Index
|
Maximum LB limit.
|
Min LB Tokens
|
Minimum number of port LB tokens.
|
Min LB Limit Index
|
Minimum LB limit.
|
Quantum
|
Quantum value for this group.
|
Default Queue
|
Default queue for this group.
|
High Priority Queue
|
High priority queue identifier.
|
Low Priority Queue
|
Low priority queue identifier.
|
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 [Bundle-Ether bundle-id | Bundle-POS bundle-id |
GigabitEthernet interface_instance | Loopback interface | MgmtEth interface_instance |
Null 0 | POS interface_instance | all] location location
Syntax Description
Bundle-Ether bundle-id
|
Identifies the aggregated Ethernet interfaces whose egress queue information you want to display. Replace bundle-id with the bundle identifier. Range is from 1 through 65535.
|
Bundle-POS bundle-id
|
Identifies the aggregated POS interfaces whose egress queue information you want to display. Replace bundle-id with the bundle identifier. Range is from 1 through 65535.
|
GigabitEthernet interface_instance
|
Identifies the Gigabit Ethernet or IEEE 802.3 interfaces whose egress queue information you want to display.
|
Loopback interface
|
Identifies the loopback interfaces whose egress queue information you want to display. Replace interface with the loopback interface identifier. Range is from 1 through 65535.
|
MgmtEth interface_instance
|
Identifies the Ethernet or IEEE 802.3 interfaces whose egress queue information you want to display.
|
Null 0
|
Identifies the Null interface.
|
POS interface_instance
|
Identifies the POS interfaces whose egress queue information you want to display.
|
all
|
Indicates that you want to display egress queue information for all interfaces in the specified location.
|
location location
|
Identifies the location of the interface whose egress queue information you want to display.
|
Defaults
No default behavior or values
Command Modes
EXEC
Command History
Release
|
Modification
|
Release 3.2
|
This command was introduced on the Cisco CRS-1.
|
Release 3.3.0
|
No modification.
|
Usage Guidelines
To use this command, you must be in a user group associated with a task group that includes the proper task IDs. For detailed information about user groups and task IDs, see the Configuring AAA Services on Cisco IOS XR Software module of the Cisco IOS XR System Security Configuration Guide.
Task ID
Task ID
|
Operations
|
interface
|
read
|
drivers
|
read
|
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
----------------------------------
----------------------------------
----------------------------------
High Priority Group : N/A
----------------------------------
----------------------------------
----------------------------------
----------------------------------
High Priority Group : N/A
----------------------------------
----------------------------------
----------------------------------
----------------------------------
High Priority Group : N/A
----------------------------------
----------------------------------
----------------------------------
----------------------------------
High Priority Group : N/A
----------------------------------
----------------------------------
----------------------------------
----------------------------------
High Priority Group : N/A
----------------------------------
----------------------------------
----------------------------------
----------------------------------
High Priority Group : N/A
----------------------------------
----------------------------------
----------------------------------
----------------------------------
High Priority Group : N/A
----------------------------------
----------------------------------
----------------------------------
----------------------------------
High Priority Group : N/A
----------------------------------
----------------------------------
Table 44 describes the significant fields shown in the display.
Table 44 show controllers egressq interface Field Descriptions
Field
|
Description
|
Interface
|
Interface identifier, in the <type>rack/slot/module/port format.
|
Port
|
Port to which the specified interface belongs.
|
Max LB Tokens
|
Maximum number of port LB tokens.
|
Max LB Limit Index
|
Maximum LB limit.
|
Quantum
|
Quantum value for this interface.
|
Default Group
|
Default group.
|
High Priority Group
|
High priority group identifier.
|
Low Priority Group
|
Low priority group identifier.
|
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
port1
|
Identifies the port whose egress queue information you want to display. Replace port1 with a port identifier. Range is from 1 through 1023.
|
port2
|
Identifies the last port whose egress queue information you want to display. Replace port2 with a port identifier. Range is from 1 through 1023.
|
all
|
Indicates that you want to display egress queue information for all ports on the node in the specified location.
|
limits max
|
Indicates that you want to display the maximum limits table.
|
location node-id
|
Identifies the location of the egress queue whose group 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
Release
|
Modification
|
Release 3.2
|
This command was introduced on the Cisco CRS-1.
|
Release 3.3.0
|
This command was first supported on the Cisco XR 12000 Series Router.
|
Usage Guidelines
To use this command, you must be in a user group associated with a task group that includes the proper task IDs. For detailed information about user groups and task IDs, see the Configuring AAA Services on Cisco IOS XR Software module of the Cisco IOS XR System Security Configuration Guide.
Task ID
Task ID
|
Operations
|
interface
|
read
|
drivers
|
read
|
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
----------------------------------
----------------------------------
High Priority Group : N/A
----------------------------------
----------------------------------
----------------------------------
----------------------------------
----------------------------------
Table 45 describes the significant fields shown in the display.
Table 45 show controllers egressq port Field Descriptions
Field
|
Description
|
Port
|
Port identifier.
|
Max LB Tokens
|
Maximum number of port LB tokens.
|
Max LB Limit Index
|
Maximum LB limit.
|
Quantum
|
Quantum value for this interface.
|
Default Group
|
Default group.
|
High Priority Group
|
High priority group identifier.
|
Low Priority Group
|
Low priority group identifier.
|
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 | context [max_elements] | all | limits]
location node-id
Syntax Description
queue1
|
Identifies the first port whose egress queue information you want to display. Replace queue1 with a queue identifier. Range is from 1 through 8191.
|
queue2
|
(Optional) Identifies the last port whose egress queue information you want to display. Replace queue2 with a queue identifier. Range is from 1 through 8191.
|
context
|
Specifies the context in which to display the information.
|
max_elements
|
(Optional) Maximum number of queue elements to show. Replace max_elements with a maximum number of elements. Range is from 1 through 4096000.
|
all
|
Indicates that you want to display egress queue information for all ports on the node in the specified location.
|
limits
|
Indicates that you want to display the limits table. Follow the limits keyword with max to display the maximum limits table, or min to display the minimum limits table.
|
max
|
Display the maximum limits table.
|
min
|
Display the minimum limits table.
|
location node-id
|
Identifies the location of the egress queue whose egress queue 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
Release
|
Modification
|
Release 3.2
|
This command was introduced on the Cisco CRS-1.
|
Release 3.3.0
|
This command was first supported on the Cisco XR 12000 Series Router.
|
Usage Guidelines
To use this command, you must be in a user group associated with a task group that includes the proper task IDs. For detailed information about user groups and task IDs, see the Configuring AAA Services on Cisco IOS XR Software module of the Cisco IOS XR System Security Configuration Guide.
Task ID
Task ID
|
Operations
|
interface
|
read
|
drivers
|
read
|
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
----------------------------------
----------------------------------
Length high watermark : 0
----------------------------------
----------------------------------
----------------------------------
Length high watermark : 0
----------------------------------
Table 46 describes the significant fields shown in the display.
Table 46 show controllers egressq queue Field Descriptions
Field
|
Description
|
Group
|
Group identifier.
|
Priority
|
Group priority.
|
Max LB Tokens
|
Maximum number of port LB tokens.
|
Max LB Limit Index
|
Maximum LB limit.
|
Min LB Tokens
|
Minimum number of port LB tokens.
|
Min LB Limit Index
|
Minimum LB limit.
|
Quantum
|
Quantum value for this queue.
|
Instantaneous length
|
Egress queue instantaneous length.
|
Length high watermark
|
Length high watermark register.
|
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
|
Modification
|
Release 3.2
|
This command was introduced on the Cisco CRS-1.
|
Release 3.3.0
|
No modification.
|
Usage Guidelines
To use this command, you must be in a user group associated with a task group that includes the proper task IDs. For detailed information about user groups and task IDs, see the Configuring AAA Services on Cisco IOS XR Software module of the Cisco IOS XR System Security Configuration Guide.
Task ID
Task ID
|
Operations
|
interface
|
read
|
drivers
|
read
|
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 ASIC state: Normal
plimasic link0 output packets: 0
plimasic link0 output bytes: 0
plimasic link1 output packets: 0
plimasic link1 output bytes: 0
plimasic link2 output packets: 0
plimasic link2 output bytes: 0
plimasic link3 output packets: 0
plimasic link3 output bytes: 0
cpuctrl output bytes: 1433250
cpuctrl dropped packets: 0
--------------------------------------------------
Table 47 describes the significant fields shown in the display.
Table 47 show controllers egressq statistics Field Descriptions
Field
|
Description
|
egressq ASIC version
|
Version identifier for the egress queue ASIC.
|
egressq ASIC state
|
Current state of the egress queue ASIC.
|
plimasic link0 output packets
|
Number of output packets on link 0 of the ASIC.
|
plimasic link0 output bytes
|
Output bytes on link 0 of the ASIC.
|
plimasic link1 output packets
|
Number of output packets on link 1 of the ASIC.
|
plimasic link1 output bytes
|
Number of output packets on link 1 of the ASIC.
|
plimasic link2 output packets
|
Number of output packets on link 2 of the ASIC
|
plimasic link2 output bytes
|
Number of output packets on link 2 of the ASIC.
|
plimasic link3 output packets
|
Number of output packets on link 3 of the ASIC.
|
plimasic link3 output bytes
|
Number of output packets on link 3 of the ASIC.
|
cpuctrl input packets
|
Number of CPU controller input packets received on this ASIC.
|
cpuctrl output bytes
|
CPU controller output bytes transmitted on this ASIC.
|
pse input packets
|
Number of PSE input packets received on this ASIC.
|
pse dropped packets
|
Number of PSE packets that were dropped by this ASIC due to errors.
|
cpuctrl dropped packets
|
Number of CPU controller packets that were dropped by this ASIC due to errors.
|
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
location node-id
|
Identifies the location of the ingress queue whose statistics you want to display. The node-id is expressed in the rack/slot/module notation.
Note Use 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.2
|
This command was introduced on the Cisco CRS-1.
|
Release 3.3.0
|
No modification.
|
Usage Guidelines
To use this command, you must be in a user group associated with a task group that includes the proper task IDs. For detailed information about user groups and task IDs, see the Configuring AAA Services on Cisco IOS XR Software module of the Cisco IOS XR System Security Configuration Guide.
Note
In the show controllers ingressq statistics command display, the rx pkts counter field may wrap if it is calculating line rate traffic.
Task ID
Task ID
|
Operations
|
interface
|
read
|
drivers
|
read
|
Examples
The following example shows how to display ingress queue manager statistics:
RP/0/RP0/CPU0:router# show controllers ingressq statistics location 0/2/CPU0
------------------------------------------------------------------------
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)
------------------------------------------------------------------------
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 : 223190
------------------------------------------------------------------------
length error drops - PSE : 0
length error drops - Cpuctrl : 0
crc error drops - PSE : 0
crc error drops - Cpuctrl : 0
OOR error drops - PSE : 0
OOR error drops - Cpuctrl : 0
Related Commands
show controllers plim asic
To display physical layer interface module (PLIM) ASIC information for a specific node or interface, use the show controllers plim asic command in EXEC mode.
Use the following syntax on a Cisco CRS-1:
show controllers plim asic {statistics {interface {POS interface_instance |
TenGigE interface_instance}| summary} | summary} [location node-id]
Use the following syntax on a Cisco XR 12000 Series Router:
show controllers plim asic {rx-channel bay {0 | 1} channel channel_number | spa {0 | 1} |
tx-channel bay {0 | 1} channel channel_number} [location node-id]
Syntax Description
statistics
|
Displays PLIM ASIC statistics for a specific interface, or summarized statistics information for all PLIM ASICS on a specific node.
|
interface POS interface_instance
|
Displays statistical information for POS interfaces only. The interface argument is expressed in the rack/slot/module/port notation.
Note Use the show interfaces command in EXEC mode to see a list of all interfaces the router.
|
interface TenGigE interface_instance
|
Displays statistical information for TenGigE interfaces only. The interface argument is expressed in the rack/slot/module/port notation.
Note Use the show interfaces command in EXEC mode to see a list of all interfaces the router.
|
summary
|
Displays a summarized information for PLIM ASICs on a specified node, or for all interfaces on the router.
|
location node-id
|
Identifies the location of the node whose PLIM ASIC information you want to display. The node-id is expressed in the rack/slot/module notation.
Note Use the show platform command to see the location of all nodes installed in the router.
|
rx-channel bay {0 | 1}
|
Displays statistical information for the SPI4.2 receive channel that is specified with the channel channel_number argument. Use 0 to indicate the bottom bay, or 1 to indicate the top bay.
|
spa {0 | 1}
|
Displays statistical information for the SPA that is specified with the channel channel argument. Use 0 to indicate the bottom bay, or 1 to indicate the top bay.
|
tx-channel bay {0 | 1}
|
Displays statistical information for the SPI4.2 transmit channel. Use 0 to indicate the bottom bay, or 1 to indicate the top bay.
|
channel channel_number
|
Identifies the channel whose statistics you want to display. Replace channel_number with the number of the channel whose statistics you want to display. Range is from 1 through 255.
|
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
|
This command was first supported on the Cisco XR 12000 Series Router.
|
Release 3.3.0
|
No modification.
|
Usage Guidelines
To use this command, you must be in a user group associated with a task group that includes the proper task IDs. For detailed information about user groups and task IDs, see the Configuring AAA Services on Cisco IOS XR Software module of the Cisco IOS XR System Security Configuration Guide.
To display statistics for a specific PLIM ASIC on a Cisco CRS-1, include the interface interface option in the command, as shown in the following example:
show controllers plim asic statistics interface interface
To display summarized statistics information for all PLIM ASICs on a specific node in a Cisco CRS-1, include the summary option in the command, as shown in the following example:
show controllers plim asic statistics summary
To display summarized PLIM ASIC port information on a Cisco CRS-1, use the show controllers plim asic summary location node-id command.
To display a summary of PLIM ASIC statistics on a Cisco CRS-1, use the show controllers plim asic statistics summary location node-id command.
Task ID
Task ID
|
Operations
|
interface
|
read
|
root-system
|
read
|
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/0
-------------------------------------------------------------------------------
-------------------------------------------------------------------------------
TotalOctets : 78904040 TotalPkts : 1622308
Unicastpkts : 1622308 MulticastPkts : 0
BroadcastPkts : 0 <64Octets : 1610433
64Octets : 0 65to127Octets : 11875
128to255Octets : 0 256to511Octets : 0
512to1023Octets : 0 1024to1518Octets : 0
1519to1548Octets : 0 1549to9216Octets : 0
>9216Octet : 0 BadCRCPkts : 0
802.1QPkts : 0 Underrun : 0
PausePkts : 0 Jabbers : 0
DeferralAbort : 0 LateCollision : 0
CollisionAbort : 0 OneCollision : 0
MultiCollision : 0 TotalCollisions : 0
TotalDefer : 0 LateCollisionAbort: 0
LengthAbort : 0 TxBP count : 0
-------------------------------------------------------------------------------
--More-- failed to get stats
TotalPkts : 1815571 UnicastPkts : 1815571
MulticastPkts : 0 BroadcastPkts : 0
64Octets : 63846 65to127Octets : 11844
128to255Octets : 7 256to511Octets : 0
512to1023Octets : 0 1024to1518Octets : 0
1519to1548Octets : 0 1549to9216Octets : 0
>9216Octets : 0 BadCRCPkts : 0
BadCodedPkts : 0 Runt : 0
ShortPkts : 1739874 802.1QPkts : 0
ControlPkts : 0 Jabbers : 0
-------------------------------------------------------------------------------
RxFiFO Drop : 0 PAR Tail Drop : 0
Table 48 describes the significant fields shown in the display.
Table 48 show controllers plim asic Field Descriptions
Field
|
Description
|
TotalOctets
|
Number of octets received or transmitted on the interface.
|
TotalPkts
|
Number of Total packets received or transmitted on the interface.
|
Unicastpkts
|
Number of unicast packets received or transmitted on the interface.
|
MulticastPkts
|
Number of multicast packets received or transmitted on the interface. Received packets were directed to the multicast address.
|
BroadcastPkts
|
Number of good broadcast packets received or transmitted. Received packets were directed to the broadcast address.
|
64Octets
|
Number of packets (including bad packets) received or transmitted that were less than 64 octets in length (excluding framing bits but including FCS octets).
|
64Octets
|
Number of packets (including bad packets) received or transmitted that were 64 octets in length (excluding framing bits but including FCS octets).
|
65to127Octets
|
Number of packets (including bad packets) received or transmitted that were between 65 and 127 octets in length inclusive (excluding framing bits but including FCS octets).
|
128to255Octets
|
Number of packets (including bad packets) received or transmitted that were between 128 and 255 octets in length inclusive (excluding framing bits but including FCS octets).
|
256to511Octets
|
Number of packets (including bad packets) received or transmitted that were between 256 and 511 octets in length inclusive (excluding framing bits but including FCS octets).
|
512to1023Octets
|
Number of packets (including bad packets) received or transmitted that were between 512 and 1023 octets in length inclusive (excluding framing bits but including FCS octets).
|
1024to1518Octets
|
Number of packets (including bad packets) received or transmitted that were between 1024 and 1518 octets in length inclusive (excluding framing bits but including FCS octets).
|
1519to1548Octets
|
Number of packets (including bad packets) received or transmitted that were between 1519 and 1548 octets in length inclusive (excluding framing bits but including FCS octets).
|
1549to9216Octets
|
Number of packets (including bad packets) received or transmitted that were between 1549 and 9216 octets in length inclusive (excluding framing bits but including FCS octets).
|
>9216Octet
|
Number of packets (including bad packets) received or transmitted that were greater than 9216 octets in length (excluding framing bits but including FCS octets).
|
BadCRCPkts
|
Number of packets received or transmitted that had a length (excluding framing bits, but including FCS octets) of between 64 and 1518 octets, inclusive, but had either a bad Frame Check Sequence (FCS) with an integral number of octets (FCS error) or a bad FCS with a nonintegral number of octets (alignment error).
|
802.1QPkts
|
Number of 802.1QPkts received or transmitted on the interface.
|
Underrun
|
Number of packets that were not retrieved quickly enough from shared memory to be transmitted/received.
|
Runt
|
Number of packets received or transmitted that were less than 64 octets long (excluding framing bits, but including FCS octets) and were otherwise well formed.
|
Giant
|
Number of packets received or transmitted that were longer than 1518 octets (excluding framing bits, but including FCS octets) and were otherwise well formed.
|
PausePkts
|
Number of pause packets transmitted/received on the interface. Pause packets that tell remote devices to delay sending more packets for a specified period of time.
|
Jabbers
|
Number of packets received or transmitted that were longer than 1518 octets (excluding framing bits but including FCS octets) and had either a bad Frame Check Sequence (FCS) with an integral number of octets (FCS error) or a bad FCS with a nonintegral number of octets (assigned error).
|
DeferralAbort
|
Number of deferral aborts that occurred on this segment.
|
LateCollision
|
Number of late collisions on this segment
|
CollisionAbort
|
Number of collisions that were aborted.
|
OneCollision
|
Number of single collisions that occurred on this segment.
|
MultiCollision
|
Number multiple collisions that occurred on this segment.
|
TotalCollisions
|
Number of collisions on this segment.
|
TotalDefer
|
Number of deferrals on this segment.
|
LateCollisionAbort
|
Number of late collision aborts that occurred on this segment.
|
LengthAbort
|
Number of length aborts that occurred on this segment.
|
TxBP count
|
Number of transmit BP on this segment.
|
Rx Statistics
|
Indicates the statistics that follow were received by the interface.
|
TX statistics
|
Indicates the statistics that follow were transmitted by the interface.
|
RxFiFO Drop
|
Displays the receive FIFO drop information.
|
PAR Tail Drop
|
Displays PAR tail drop information.
|
TxFIFO Drop
|
Displays transmitted FIFO drop information.
|
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
links link_number
|
Displays PSE information for the specified link. Replace link_number with a link number in the range from 1 through 4294967295.
Note Use the show controllers pse eio links all location node-id command to display all available EIO link IDs on a node.
|
links all
|
Displays PSE information for all links on the specified node.
|
location node-id
|
(Optional) Displays all EIO links on a specific node only. The node-id is expressed in the rack/slot/module notation.
Note Use 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.
|
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
Task ID
|
Operations
|
interface
|
read
|
drivers
|
read
|
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/CPU0
----------------------------------------
-------------------------------------------------------------------
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
-------------------------------------------------------------------
-------------------------------------------------------------------
Table 49 describes the significant fields shown in the display.
Table 49 show controllers pse eio links Field Descriptions
Field
|
Description
|
Node
|
Node whose PSE information is displayed.
|
EIO link
|
EIO link whose information is displayed.
|
ASIC Id
|
ASIC associated with this EIO link.
|
Peer Id
|
ASIC of the remote peer of this EIO link.
|
Type
|
Indicates whether this link is receiving or transmitting (re)training requests.
|
Link-Id
|
Unique ID assigned by the system to the EIO link.
|
Attempts
|
Number of consecutive EIO training requests for the link made by the PSE driver to the peer.
Note Typically, the PSE driver at the receive end of a link initiates the training of that EIO link. Therefore, the EIO links whose PSE driver is at the transmit end show a value of 0 for the Attempts field, even though those links are in the EIO_LINK_TRAINED state.
|
Accept
|
Number of PSE driver requests for training that were accepted by the peer. When a PSE driver request is accepted, training is started.
Note Typically, the PSE driver at the receive end of a link initiates the training of that EIO link. Therefore, the EIO links whose PSE driver is at the transmit end show a value of 0 for the Accept field, even though those links are in the EIO_LINK_TRAINED state.
|
Failed
|
Number of times the training for this link failed for any reason.
|
State
|
Current state of the EIO link.
|
Macro-id Windage Diag status
|
Windage value used for the training, and the final status of the training for that windage.
Note The Macro-id Windage Diag status field is displayed only when you ask EIO info for specific link.
|
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} [instance {0 | 1}]
[location node-id]
Syntax Description
client-connection connID
|
Displays IPC information about the specified client connection. Replace connID with the client connection ID. Range is from 1 through 255.
|
client-connection all
|
Displays IPC information about the all client connection.
|
cpuctrlif
|
Displays IPC information about the specified PSE IPC CPU controller instance.
|
instance {0 | 1}
|
(Optional) Identifies the PSE device whose information you want to display. Enter 0 to specify the ingress PSE device, or 1 to specify the egress PSE device.
Note Follow the instance {0 | 1} argument with the location node-id argument to restrict the command to a specific node containing the specified device instance.
|
location node-id
|
(Optional) Identifies the location of the node whose PSE device information you want to display. The node-id is expressed in the rack/slot/module notation.
Note Use the show platform command to see the location of all nodes installed in the router.
Note Include the instance {0 | 1} argument before the location node-id argument to restrict the command to a specific device instance on the specified node.
|
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.
|
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 instance {0 | 1} argument with the command, as shown in the following example:
show controllers pse ipc client-connection connId instance instance
To 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-id
Task ID
Task ID
|
Operations
|
interface
|
read
|
drivers
|
read
|
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 13
----------------------------------------
-------------------------------------------------
Clinfos: 0x482bf9f8 (Notif) 0 (Reply)
SendReqs: 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)
----------------------------------------
-------------------------------------------------
Clinfos: 0x482bf9f8 (Notif) 0 (Reply)
SendReqs: 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)
Table 50 describes the significant fields shown in the display.
Table 50 show controllers pse ipc client-connection Field Descriptions
Field
|
Description
|
ConnId
|
Connection identifier.
|
ConnOptions
|
Connection bind time options requested by the client creating this connection.
|
Clinfos
|
Client information (clinfo) index number. The memory database is organized as a table of clinfos, which are indexed by the region id and maintained in shared memory.
|
ConnStateFlags
|
Bitmask containing the current state of the connection.
|
ConnNotifFlags
|
Bitmask of the types of notifications that the client creating this connection has registered for.
|
SendReqs
|
Number of PSE IPC send requests that client has made on this connection.
|
SendFiltered
|
Number of send requests that were filtered out (dropped) from the PSE driver due to any internal filter policy.
|
SendFailed
|
Number of send requests that could not be handled by the PSE driver due to error conditions such as hardware I/O failures, lack of buffering space, and so forth.
|
RecvReqs
|
Number of data receive requests that the client has made on this connection.
|
RecvReqTouts
|
Number of data receive requests from the client that timed out because no data was received from PSE device.
|
RecvDatTouts
|
Number of times data was received from PSE device, but timed out because there was no receive request from client to pick up that data from the connection.
|
RecvQState
|
Current state of the internal data receive FIFO queue. The internal data receive FIFO queue buffers data arriving from the PSE device for the connection, until the client sends a receive request for that data. The RecvQState is expressed in the X/Y notation, where X is current depth of the queue, and Y is the maximum depth allowed for the queue.
|
The following command shows how to display PSE information for a specific IPC controller connection:
RP/0/RP0/CPU0:router# show controllers pse ipc cpuctrlif
----------------------------------------
Pse IPC cpuctrl if Information
-------------------------------------------------
BufBase 0x112190 BufSize 32768 PadBufp 0xec0af118 Seqnum 854
RORegNum 10 RORegVal 0x49f0 WORegNum 2 WORegVal 0x49f0
HoldQ 0/512 CDMAPendQ 0/128 UnackQ 0/256
NumEnqs 854 NumRejs 0 NumDmaReqFails 0
NumDmaPendFails 0 NumMbxSpcFails 0 NumHldqOvflows 0
NumPDMAEntries 64 NumEnqs 15 NumRejs 0
Pse IPC cpuctrl if Information
-------------------------------------------------
BufBase 0x112190 BufSize 32768 PadBufp 0xec0af14c Seqnum 424
RORegNum 10 RORegVal 0x1c60 WORegNum 2 WORegVal 0x1c60
HoldQ 0/512 CDMAPendQ 0/128 UnackQ 0/256
NumEnqs 424 NumRejs 0 NumDmaReqFails 0
NumDmaPendFails 0 NumMbxSpcFails 0 NumHldqOvflows 0
NumPDMAEntries 64 NumEnqs 2 NumRejs 0
----------------------------------------
Pse IPC cpuctrl if Information
-------------------------------------------------
BufBase 0x112190 BufSize 32768 PadBufp 0xec0af118 Seqnum 833
RORegNum 10 RORegVal 0xdb8 WORegNum 2 WORegVal 0xdb8
HoldQ 0/512 CDMAPendQ 0/128 UnackQ 0/256
NumEnqs 833 NumRejs 0 NumDmaReqFails 0
NumDmaPendFails 0 NumMbxSpcFails 0 NumHldqOvflows 0
NumPDMAEntries 64 NumEnqs 9 NumRejs 0
Pse IPC cpuctrl if Information
-------------------------------------------------
BufBase 0x112190 BufSize 32768 PadBufp 0xec0af14c Seqnum 409
RORegNum 10 RORegVal 0x5f70 WORegNum 2 WORegVal 0x5f70
HoldQ 0/512 CDMAPendQ 0/128 UnackQ 0/256
NumEnqs 409 NumRejs 0 NumDmaReqFails 0
NumDmaPendFails 0 NumMbxSpcFails 0 NumHldqOvflows 0
NumPDMAEntries 64 NumEnqs 2 NumRejs 0
Table 51 describes the significant fields shown in the display.
Table 51 show controllers pse ipc cpuctrlif Field Descriptions
Field
|
Description
|
Cpuctrl interface is up
Cpuctrl interface is down
|
Whether the connection is currently up or down.
|
Normal Priority Tx I/F
|
Displays the following transmit buffer information for the connection:
• BufBase
• BufSize
• PadBufp
• Seqnum
• RORegNum
• RORegVal
• WORegNum
• WORegVal
• CDMACh
• CDMAQ
• HoldQ
• CDMAPendQ
• UnackQ
• NumEnqs
• NumRejs
• NumDmaReqFails
• NumDmaPendFails
• NumMbxSpcFails
• NumHldqOvflows
|
Normal Priority Rx I/F:
|
Displays the following receive buffer information for the connection:
• NumPDMAEntries
• NumEnqs
• NumRejs
|
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
egress
|
(Optional) Displays information for the ingress PSE device only.
Note Follow the egress argument with the location node-id argument to restrict the command to a specific node.
|
ingress
|
(Optional) Displays information for the ingress PSE device only.
Note Follow the ingress argument with the location node-id argument to restrict the command to a specific node.
|
location node-id
|
(Optional) Identifies the location of the node whose PSE device information you want to display. The node-id is expressed in the rack/slot/module notation.
Note Use the show platform command to see the location of all nodes installed in the router.
Note Include the instance {0 | 1} argument before the location node-id argument to restrict the command to a specific device instance on the specified node.
|
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.
|
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
Task ID
|
Operations
|
interface
|
read
|
drivers
|
read
|
Examples
The following command shows how to display PSE maintenance processor information for a specific controller instance:
RP/0/RP0/CPU0:router# show controllers pse mp instance 1
----------------------------------------
-------------------------------------------------
MIPC Subtask Context Information
High Priority MIPC Mbox Info
Norm Priority MIPC Mbox Info
NumMsgsGtred 93 NumDMAErrDrops 5 NumGtrDisDrops 2
MSTAT Subtask Context Information
NumSegs 9 CntrsPerBrst 93 MinCycleMsecs 4000
--------- Seg[0] config -----------------
SegId 0 SegBeg 0 SegEnd 3071
ExpBeg 0 ExpEnd 0 ExpRate 0 CycBefExp 0
--------- Seg[1] config -----------------
SegId 1 SegBeg 3072 SegEnd 74239
ExpBeg 3072 ExpEnd 3072 ExpRate 0 CycBefExp 0
--------- Seg[2] config -----------------
SegId 2 SegBeg 74240 SegEnd 107007
ExpBeg 74240 ExpEnd 74240 ExpRate 0 CycBefExp 0
--------- Seg[3] config -----------------
SegId 3 SegBeg 107008 SegEnd 262143
ExpBeg 107008 ExpEnd 107008 ExpRate 0 CycBefExp 0
--------- Seg[4] config -----------------
SegId 4 SegBeg 262144 SegEnd 265215
ExpBeg 262144 ExpEnd 262144 ExpRate 0 CycBefExp 0
--------- Seg[5] config -----------------
SegId 5 SegBeg 265216 SegEnd 336383
ExpBeg 265216 ExpEnd 265216 ExpRate 0 CycBefExp 0
--------- Seg[6] config -----------------
SegId 6 SegBeg 336384 SegEnd 442367
ExpBeg 336384 ExpEnd 336385 ExpRate 1 CycBefExp 1
--------- Seg[7] config -----------------
SegId 7 SegBeg 442368 SegEnd 458751
ExpBeg 442368 ExpEnd 442368 ExpRate 0 CycBefExp 0
--------- Seg[8] config -----------------
SegId 8 SegBeg 458752 SegEnd 491519
ExpBeg 458752 ExpEnd 458752 ExpRate 0 CycBefExp 0
CurrTokens 9 MaxTokens 44 MinTokens 11
CurrSeg 5 CurrCntr 289954 CntrsExp 66532
PktsExp 33266 DMAErrDrops 0 REDDrops 0
REDDelays 0 GtrDisDelays 0
CfgUpdsApp 1 SegUpdsApp 10 UpdsRej 0
----------------------------------------
-------------------------------------------------
MIPC Subtask Context Information
High Priority MIPC Mbox Info
Norm Priority MIPC Mbox Info
NumMsgsGtred 71 NumDMAErrDrops 4 NumGtrDisDrops 3
MSTAT Subtask Context Information
NumSegs 9 CntrsPerBrst 93 MinCycleMsecs 4000
--------- Seg[0] config -----------------
SegId 0 SegBeg 0 SegEnd 3071
ExpBeg 0 ExpEnd 0 ExpRate 0 CycBefExp 0
--------- Seg[1] config -----------------
SegId 1 SegBeg 3072 SegEnd 74239
ExpBeg 3072 ExpEnd 3072 ExpRate 0 CycBefExp 0
--------- Seg[2] config -----------------
SegId 2 SegBeg 74240 SegEnd 107007
ExpBeg 74240 ExpEnd 74240 ExpRate 0 CycBefExp 0
--------- Seg[3] config -----------------
SegId 3 SegBeg 107008 SegEnd 262143
ExpBeg 107008 ExpEnd 107008 ExpRate 0 CycBefExp 0
--------- Seg[4] config -----------------
SegId 4 SegBeg 262144 SegEnd 265215
ExpBeg 262144 ExpEnd 262144 ExpRate 0 CycBefExp 0
--------- Seg[5] config -----------------
SegId 5 SegBeg 265216 SegEnd 336383
ExpBeg 265216 ExpEnd 265216 ExpRate 0 CycBefExp 0
--------- Seg[6] config -----------------
SegId 6 SegBeg 336384 SegEnd 442367
ExpBeg 336384 ExpEnd 336415 ExpRate 1 CycBefExp 0
--------- Seg[7] config -----------------
SegId 7 SegBeg 442368 SegEnd 458751
ExpBeg 442368 ExpEnd 442368 ExpRate 0 CycBefExp 0
--------- Seg[8] config -----------------
SegId 8 SegBeg 458752 SegEnd 491519
ExpBeg 458752 ExpEnd 458752 ExpRate 0 CycBefExp 0
CurrTokens 5 MaxTokens 44 MinTokens 11
CurrSeg 6 CurrCntr 398633 CntrsExp 1064256
PktsExp 33258 DMAErrDrops 0 REDDrops 0
REDDelays 0 GtrDisDelays 0
CfgUpdsApp 1 SegUpdsApp 10 UpdsRej 0
Table 52 describes the significant fields shown in the display.
Table 52 show controllers pse mp Field Descriptions
Field
|
Description
|
MIPC Subtask Context Information
|
MIPC subtask information from the following mailboxes (queues):
• High Priority MIPC Mbox
• Norm Priority MIPC Mbox
Note The MIPC MBox is a chunk of the MP DMEM that receives MIPC messages. The Norm Priority mailbox has buffer of 32 KB, while the High Priority Mbox has an 8 KB buffer.
|
High Priority MIPC Mbox Info
|
Mailbox (or queue) that receives high-priority MIPC messages. The following information is displayed for the High Priority MIPC Mbox:
• NumProc—Number of MIPC messages that have been processed.
• NumUnsupp—Number of unsupported MIPC messages.
• NxtSeqNum—Sequence number of the message with respect to other messages sent on the same MIPC channel.
• NumOOSeq—Number of MIPC messages that were received out of sequence.
|
Norm Priority MIPC Mbox info
|
Mailbox (or queue) that receives normal-priority MIPC messages. The following information is displayed for the High Priority MIPC Mbox:
• NumProc—Number of MIPC messages that have been processed.
• NumUnsupp—Number of unsupported MIPC messages.
• NxtSeqNum—Identifies the sequence number of the message with respect to other messages sent on the same MIPC channel.
• NumOOSeq—Number of MIPC messages that were received out of sequence.
|
NumMsgsGtred
|
Number of MIPC gather messages that have been processed.
|
NumDMAErrDrops
|
Number of MIPC gather messages that were dropped due to DMA errors.
|
NumGtrDisDrops
|
Number of MIPC gather messages that were dropped due to distribution errors.
|
MSTAT Subtask Context Information
|
MSTAT subtask information from the following queues:
• High Priority MIPC Mbox
• Norm Priority MIPC Mbox
The MIPC MBox is a chunk of the MP DMEM that receives MIPC messages. The Norm Priority mailbox has buffer of 32 KB, while the High Priority Mbox has an 8 KB buffer.
|
Related Commands
show controllers pse statistics
To display packet switching engine (PSE) statistics for a specific controller instance, or for a specific node, use the show controllers pse statistics command in EXEC mode.
show controllers pse statistics [instance {0 | 1}] [location node-id]
Syntax Description
instance {0 | 1}
|
(Optional) Identifies the PSE device whose statistics you want to display.
Enter 0 to specify the ingress PSE device, or 1 to specify the egress PSE device.
Note Follow the instance {0 | 1} argument with the location node-id argument to restrict the command to specific node containing the specified device instance.
|
location node-id
|
(Optional) Identifies the location of the node whose PSE device information you want to display. The node-id is expressed in the rack/slot/module notation.
Note Use the show platform command to see the location of all nodes installed in the router.
Note Include the instance {0 | 1} argument before the location node-id argument to restrict the command to a specific device instance on the specified node.
|
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.
|
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 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 statistics command takes effect on both device instances on all modular services cards.
Task ID
Task ID
|
Operations
|
interface
|
read
|
drivers
|
read
|
Examples
The following command shows how to display PSE statistics for a specific controller instance:
RP/0/RP0/CPU0:router# show controllers pse statistics instance 0
----------------------------------------
-------------------------------------------------
MPLS_FWD_STATS_MEM_OOR : 0
DROP_IPV4_LENGTH_ERROR : 0
DROP_IPV4_CHECKSUM_ERROR : 0
IPV4_UNKNOWN_PLU_TYPE : 0
IPV4_DF_SET_FRAG_NEEDED_PUNT : 0
IPV4_MCAST_EMPTY_OLIST_COUNTER : 0
IPV4_MCAST_MAX_COPIES_EXCEEDED_COUNTER : 0
IPV4_MCAST_LAST_PACKET_TIME_WASTED_COUNTER : 0
DROP_BAD_RESOURCE_ERROR : 0
DROP_IPV4_LINE_STATUS : 0
DROP_PUNT_EXCEED_Q_THRESH : 0
DROP_IPV6_LINE_STATUS : 0
PLU_LEAF_UNTERMINATED : 0
DROP_IPV6_UNKNOWN_PLU_TYPE : 0
DROP_IPV6_LENGTH_ERROR : 0
PUNT_IPV6_MISS_SRC_COMP : 0
IPV4_MCAST_DROP_DF_PACKET : 0
IPV4_MCAST_DO_ALL_BUT_FWD : 0
IPV4_TUNNEL_NOT_CONFIGD : 0
GLOBAL_IFHANDLE_TCAM_MISS : 0
RECIRCULATE_UIDB_INDEX : 0
DUMMY_COUNTER : 2622348240762
MPLS_LINE_STATUS_DN_DROP : 0
MPLS_NOT_ENABLED_DROP : 0
MPLS_UNSUPP_PLU_LABEL_TYPE : 0
IPV4_TUNNEL_UNEXP_PHYSINTF_ADJ : 0
IPV4_TUNNEL_UNEXP_TUNINTF_ADJ : 0
DROP_IPV4_L4HDR_LENGTH_ERROR : 0
MPLS_TTL_EXP_GEN_ICMP : 0
MPLS_NON_IP_PKT_GT_MTU : 0
DROP_L2TP_TOO_SHORT_ERROR : 0
DROP_L2TP_TOO_LONG_ERROR : 0
DROP_GRE_LENGTH_ERROR : 0
DROP_IPIP_LENGTH_ERROR : 0
IPV4_FRAG_TUNNEL_PUNT : 0
MPLS_IPV4_PKT_WITH_OPT_NEEDS_FRAG : 0
IPV4_NULL_RTE_DROP_PKT : 0
IPV6_NULL_RTE_DROP_PKT : 0
PKT_LARGE_PADDING_PUNT : 0
----------------------------------------
-------------------------------------------------
MPLS_FWD_STATS_MEM_OOR : 0
DROP_IPV4_LENGTH_ERROR : 0
DROP_IPV4_CHECKSUM_ERROR : 0
IPV4_UNKNOWN_PLU_TYPE : 0
IPV4_DF_SET_FRAG_NEEDED_PUNT : 0
IPV4_MCAST_EMPTY_OLIST_COUNTER : 0
IPV4_MCAST_MAX_COPIES_EXCEEDED_COUNTER : 0
IPV4_MCAST_LAST_PACKET_TIME_WASTED_COUNTER : 0
DROP_BAD_RESOURCE_ERROR : 0
DROP_IPV4_LINE_STATUS : 0
DROP_PUNT_EXCEED_Q_THRESH : 0
DROP_IPV6_LINE_STATUS : 0
PLU_LEAF_UNTERMINATED : 0
DROP_IPV6_UNKNOWN_PLU_TYPE : 0
DROP_IPV6_LENGTH_ERROR : 0
PUNT_IPV6_MISS_SRC_COMP : 0
IPV4_MCAST_DROP_DF_PACKET : 0
IPV4_MCAST_DO_ALL_BUT_FWD : 0
IPV4_TUNNEL_NOT_CONFIGD : 0
GLOBAL_IFHANDLE_TCAM_MISS : 0
RECIRCULATE_UIDB_INDEX : 0
DUMMY_COUNTER : 2668152738279
MPLS_LINE_STATUS_DN_DROP : 0
MPLS_NOT_ENABLED_DROP : 0
MPLS_UNSUPP_PLU_LABEL_TYPE : 0
IPV4_TUNNEL_UNEXP_PHYSINTF_ADJ : 0
IPV4_TUNNEL_UNEXP_TUNINTF_ADJ : 0
DROP_IPV4_L4HDR_LENGTH_ERROR : 0
MPLS_TTL_EXP_GEN_ICMP : 0
MPLS_NON_IP_PKT_GT_MTU : 0
DROP_L2TP_TOO_SHORT_ERROR : 0
DROP_L2TP_TOO_LONG_ERROR : 0
DROP_GRE_LENGTH_ERROR : 0
DROP_IPIP_LENGTH_ERROR : 0
IPV4_FRAG_TUNNEL_PUNT : 0
MPLS_IPV4_PKT_WITH_OPT_NEEDS_FRAG : 0
IPV4_NULL_RTE_DROP_PKT : 0
IPV6_NULL_RTE_DROP_PKT : 0
PKT_LARGE_PADDING_PUNT : 0
Table 53 describes the significant fields shown in the display.
Table 53 show controllers pse statistics Field Descriptions
Field
|
Description
|
Node
|
Identifies the node whose PSE statistics are displayed. The node ID is expressed in the rack/slot/module notation.
|
PSE 0, Statistics Info
|
Displays all statistics maintained by the PSE.
|
Related Commands
show controllers pse summary
To display a summary of packet switching engine (PSE) information for a specific controller or node, use the show controllers pse summary command in EXEC mode.
show controllers pse summary [instance {0 | 1}] [location node-id]
Syntax Description
instance {0 | 1}
|
(Optional) Identifies the PSE device whose information you want to display.
Enter 0 to specify the ingress PSE device, or 1 to specify the egress PSE device.
Note Follow the instance {0 | 1} argument with the location node-id argument to restrict the command to specific node containing the specified device instance.
|
location node-id
|
(Optional) Identifies the location of the node whose PSE device information you want to display. The node-id is expressed in the rack/slot/module notation.
Note Use the show platform command to see the location of all nodes installed in the router.
Note Include the instance {0 | 1} argument before the location node-id argument to restrict the command to a specific device instance on the specified node.
|
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.
|
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 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 summary command takes effect on both device instances on all modular services cards.
Task ID
Task ID
|
Operations
|
interface
|
read
|
drivers
|
read
|
Examples
The following command shows how to display a summary of PSE information for a specific controller instance:
RP/0/RP0/CPU0:router# show controllers pse summary instance 1
----------------------------------------
-------------------------------------------------
IBM P/N : 47P0595 LotNum : D2300123
SerialNum : 0x00001c BadPPECls : 0000
Version : 1 CpuctrlPort : 6
StartupOpts : 00000000 MmappedBase : 0x60669000
ClsDisMask : 0000 NFusedPPEs : 0 (0 hwf, 0 swf)
MPUcodeName : /pkg/ucode/egress_mp_v1.mucode
PPEUcodeName: /pkg/ucode/egress_turbo_pos_v1.mucode
INTR-Status : 00000000 INTR-Enable : 0x7ffffe
NColdResets : 1 NWarmResets : 0
NPPEUcDlds : 1 NResetRetry : 0
NIntrtps : 1 NIntrptThrot: 0
----------------------------------------
-------------------------------------------------
SerialNum : 0xffffff BadPPECls : 0000
Version : 3 CpuctrlPort : 6
StartupOpts : 00000000 MmappedBase : 0x60669000
ClsDisMask : 0000 NFusedPPEs : 4 (0 hwf, 4 swf)
MPUcodeName : /pkg/gsr/ucode/egress_mp_v3.mucode
PPEUcodeName: /pkg/gsr/ucode/egress_turbo_pos_v3.mucode
INTR-Status : 00000000 INTR-Enable : 0x7ffffe
NColdResets : 1 NWarmResets : 0
NPPEUcDlds : 1 NResetRetry : 0
NIntrtps : 1 NIntrptThrot: 0
Table 54 describes the significant fields shown in the display.
Table 54 show controllers pse summary Field Descriptions
Field
|
Description
|
Node
|
Node whose PSE information is displayed.
|
IBM P/N
|
IBM part number.
|
SerialNum
|
Serial number of the node.
|
BadPPECls
|
Number of bad PPECIs on the PSE.
|
Version
|
PSE version.
|
CpuctrlPort
|
Cpuctrl port associated with the PSE instance.
|
DeviceState
|
Whether the node is up (active) or down (inactive).
|
StartupOpts
|
Internal information about the PSE startup options.
|
MmappedBase
|
Internal mapping information.
|
ClsDisMask
|
Internal masking information,
|
NFusedPPEs
|
Internal PPE information.
|
MPUcodeName
|
Information about the MPU code.
|
PPEUcodeName
|
Information about the PPEU code.
|
INTR-Status
|
Internal status information.
|
INTR-Enable
|
Internal enable information.
|
NColdResets
|
Number of cold resets experienced by the router.
|
NWarmResets
|
Number of warm resets experienced by the router.
|
NPPEUcDlds
|
Internal information about the PSE.
|
NResetRetry
|
Number of times the router attempted to reset itself.
|
NIntrtps
|
Internal information about interrupts on the PSE.
|
NIntrptThrot
|
Internal throttling information for the PSE.
|
Related Commands
show packet-memory
To display information for packet memory, use the show packet-memory command in EXEC mode.
show packet-memory [location node-id]
Syntax Description
location node-id
|
(Optional) Displays detailed packet memory information for the designated node. The node-id argument is entered in the rack/slot/module notation.
|
Defaults
Displays information about all packet memory.
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.
|
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 show packet-memory command can be used to display the total number of packet and particle headers, along with the packet memory that is currently allocated in the system.
Task ID
Task ID
|
Operations
|
basic-services
|
read
|
Examples
The following example shows how to display packet memory information:
RP/0/RP0/CPU0:router# show packet-memory
Packet memory statistics :
==========================
total: 32000, free: 32000, size: 448
Pool(0):total: 8000, free: 8000, size: 256
Pool(1):total: 4000, free: 3968, size: 512
Pool(2):total: 16, free: 16, size: 512
Pool(3):total: 8000, free: 7936, size: 768
Pool(4):total: 12800, free: 9172, size: 1648
Pool(5):total: 320, free: 320, size: 2560
Pool(6):total: 1600, free: 1088, size: 4608
Pool(7):total: 640, free: 640, size: 6240
total: 8000, free: 8000, size: 256
Packet Feature Specific Variable (FSV)
total: 16000, free: 16000, size: 88
total: 16384, free: 16384, size: 40
Table 55 describes the significant fields shown in the display.
Table 55 show packet memory Field Descriptions
Field
|
Description
|
Packet headers
|
Data structure that defines and controls an aggregation of data structures, collectively known as a packet. Includes information about every packet in the system.
|
Particle Pools
|
Data structure that describes a particle and may be chained to other particles in a linked list. Includes information about the actual data of the packet and other particle headers in this packet if present in this packet.
|
Particle clone
|
Duplicate particle header that points to a previously allocated particle. Differs from a particle header in that a particle clone shares the particle with another particle header.
|
Packet Feature Specific Variable (FSV)
|
Scratch pad shared among the features in the packet path, listing hangs of the packet header.
|
Packet trace
|
Data associated with the packet header to help tracing a packet in the system.
|