The documentation set for this product strives to use bias-free language. For the purposes of this documentation set, bias-free is defined as language that does not imply discrimination based on age, disability, gender, racial identity, ethnic identity, sexual orientation, socioeconomic status, and intersectionality. Exceptions may be present in the documentation due to language that is hardcoded in the user interfaces of the product software, language used based on RFP documentation, or language that is used by a referenced third-party product. Learn more about how Cisco is using Inclusive Language.
The following commands, listed in alphabetical order, are introduced or modified for the Cisco SAMI Cisco IOS PPCs and are supported at the SAMI Cisco IOS PPC console:
•clear sami ixp statistics egress
•clear sami pci ipc statistics
•confreg (ROM monitor command)
•show sami mac-resolver dest-addr-list
•show sami mac-resolver next-hop list
Note This section does not contain commands specific to the Cisco software application image bundled with the SAMI software. For a description of the commands supported by the Cisco software application image on your SAMI, see the documentation for the Cisco software application you are using.
To clear the statistics corresponding to number of packets forwarded to IXP in the egress path, use the clear sami ixp statistics egress privileged EXEC command.
clear sami ixp statistics egress
This command has no keywords or arguments.
No default behavior or values exist.
Privileged EXEC
|
|
---|---|
SAMI Release 3.4 |
This command was introduced in the Cisco CSG2 Release 5.0. |
Use this command to clear the statistics corresponding to number of packets forwarded to IXP in the egress path.
This example shows how to clear the statistics forwarded to IXP in the egress path:
Router# clear sami ixp statistics egress
To clear the statistics corresponding to PCI-based IXP IPC, use the clear sami pci ipc statistics privileged EXEC command.
clear sami pci ipc statistics
This command has no keywords or arguments.
No default behavior or values exist.
Privileged EXEC
|
|
---|---|
SAMI Release 3.4 |
This command was introduced in conjunction with the CSG2 Release 5.0. |
This example shows how to clear the PCI statistics for IPC with IXP:
Router#clear sami pci ipc statistics
To change the configuration register settings, use the config-register command in global configuration mode.
config-register value
The default is 0x2102, which causes the processor to boot from flash memory and the Break key to be ignored.
Global configuration
|
|
---|---|
Release 1.0 |
This command was integrated into Cisco SAMI Release 1.0. |
Use the config-register command to change the configuration register settings for a PPC.
The following bits of the configuration register are supported:
In the following example, the configuration register is set to boot the system image from flash memory:
Router(config)# config-register 0x2102
To change the configuration register settings from ROM monitor, use the config-register command.
confreg value
The default is 0x2102, which causes the processor to boot from flash memory and the Break key to be ignored.
ROM monitor
|
|
---|---|
Release 1.0 |
This command was integrated into Cisco SAMI Release 1.0. |
The following bits of the configuration register are supported:
In the following example, the configuration register is set to boot the system image from flash memory:
rommon 1> confreg 0x2102
To debug Ethernet interface events, use the debug ethernet-interface command in privileged EXEC mode. Use the no form of this command to disable debugging output.
debug ethernet-interface
no debug ethernet-interface
This command has no keywords or arguments.
No default behavior or values exist.
Privileged EXEC
|
|
---|---|
Release 1.0 |
This command was integrated into Cisco SAMI Release 1.0. |
Use this command to provide non-IP control protocol (IPCP) packet level debugs at the First In First Out (FIFO) interface.
This example shows how to enable debugging of Ethernet interface events and provides a sample of the output:
Router# debug ethernet-interface
Ethernet network interface debugging is on
Router# RX:(D)b000.0000.0ffc (S)0000.0000.0000 (T)0x4000 (L)92 (IP)0.0.0.80 (TL)6
RX:(D)b800.0000.0ffc (S)0000.0000.0000 (T)0x4000 (L)92 (IP)0.0.255.255 (TL)57344
RX:(D)c800.0008.0000 (S)0000.0000.0000 (T)0x6000 (L)124 (IP)0.0.255.255 (TL)3225
<... output truncated ...>
Router#
To display information health-monitoring processing (from the PPC to IXP path or all paths from the PPC to the supervisor), use the debug sami health-monitoring command in privileged EXEC mode. To remove this configuration, use the no form of the command.
debug sami health-monitoring [probe | IXP]
no debug sami health-monitoring [probe | IXP]
Disabled.
Privileged EXEC
|
|
---|---|
Release 1.0 |
This command was introduced. |
Use this command to enable debugging related to data path sanity monitoring sent to probe the path to an IXP or to probe all paths between the PPC and the supervisor.
The following example illustrates how to use the debug sami health-monitoring command.
Router# debug sami health-monitoring IXP
To display message-level debugging related to health-monitoring processing (from the PPC to IXP path or all paths from the PPC to the supervisor), use the debug sami health-monitoring command in privileged EXEC mode. To remove this configuration, use the no form of the command.
debug sami health-monitoring [probe | IXP] message
no debug sami health-monitoring [probe | IXP] message
Disabled.
Privileged EXEC
|
|
---|---|
Release 1.0 |
This command was introduced. |
Use this command to enable message-level debugging related to data path sanity monitoring sent to probe the path to an IXP or to probe all paths between the PPC and the supervisor.
The following example illustrates how to use the debug sami health-monitoring command.
Router# debug sami health-monitoring probe message
To information about IP control protocol (IPCP) communication used for Ethernet Out of Band Channel (EOBC) and inter-processor traffic, use the debug sami ipcp command in privileged EXEC mode. To disable debugging, use the no form of this command.
debug sami ipcp {errors | events | packet} [src 0x1-0x3f | ixp | ppc# | bcm >] [dstn 0x1-0x3f | ixp | ppc# | bcm>] [ssap 0-255] [dsap 0-255]
No default behavior or values exist.
Privileged EXEC
|
|
---|---|
Release 1.0 |
This command was introduced. |
Use this command to enable debugging for IPCP communication used for EOBC and inter processor traffic
The following example illustrates how to use the debug sami ipcp command.
Router# debug sami ipcp
To enabling debugging for traffic processing to/from the 127.0.0.0 network use the debug sami ip hidden command in privileged EXEC mode. To turn off the debug function, use the no form of this command.
debug sami ip hidden
no debug sami ip hidden
This command has no keywords or arguments.
No default behavior or values exist.
Privileged EXEC
|
|
---|---|
Release 1.0 |
This command was introduced. |
Use this command to enable the RCAL feature debugging for the127.0.0.0 network.
The following example illustrates how to use the debug sami ip hidden command.
Router# debug sami ip hidden
To enable debugging for MAC-resolver feature, use the debug sami mac-resolver privileged EXEC command.
debug sami mac-resolver {errors | events}
errors |
Enable error level logs for mac resolver. |
events |
Enable logs corresponding to mac-resolver processing. |
If no keyword is provided, both error and events logs are enabled.
Privileged EXEC
|
|
---|---|
SAMI Release 3.4 |
This command was introduced in conjunction with the Cisco LTE Release 1.0. |
This command enables debugging capabilities of MAC resolver feature. MAC resolver is an important feature that facilitates datapath forwarding capabilities in IXP.
Here is an example of the debug sami mac-resolver command:
Router#debug sami mac-resolver errors
Router#debug sami mac-resolver events
Router#debug sami mac-resolver
To enable logging for the PCI-based IPC with IXP, use the debug sami pci ipc privileged EXEC command.
debug sami pci ipc {errors | events | msgs}
errors |
Enables error level logs for PCI based IXP IPC. |
events |
Enables logs corresponding to PCI based IXP IPC processing. |
msgs |
Enable logs to dump messages received over PCI for IXP IPC. |
If no keyword is provided, both error and events logs are enabled.
Privileged EXEC
|
|
---|---|
SAMI Release 3.4 |
This command was introduced in conjunction with the CSG2 Release 5.0, and the Cisco LTE Release 1.0. |
Here is an example of the debug sami pci ipc command:
Router#debug sami pci ipc errors
Router#debug sami pci ipc events
Router#debug sami pci ipc msgs
To enable debugging capabilities in packet trailer processing, use the debug sami pkttrailer privilieged EXEC command.
debug sami pkttrailer {errors | events | cr }
errors |
Enables error logs in packet trailer processing. |
events |
Enables logs corresponding to packet trailer processing in platform driver. |
If no keyword is provided, logs for both error and events are enabled.
Privileged EXEC
|
|
---|---|
SAMI Release 3.4 |
This command was introduced in conjunction with the CSG2 Release 5.0. |
This command enables debugging capabilities in packet trailer processing. Packet trailer is an integral part of CSG2 Release 5.0, where additional data is send to the IXP at the end of the packet to configure acceleration parameters for a flow.
This command would have an impact on the datapath performance of the SAMI processors. You should only use the command when directed to do so by Cisco Technical Assistance Center (TAC) engineers.
Here is an example of the debug sami pkttrailer command:
Router#debug sami pkttrailer errors
Router#debug sami pkttrailer events
Router#debug sami pkttrailer
To dump packet trailer data in the ingress and egress directions for IXP, use the debug sami pkttrailer dump privileged EXEC command.
debug sami pkttrailer dump [{ingress | egress | cr }]
ingress |
Dumps packet trailer data received in ingress. |
events |
Dumps packet trailer data received in egress. |
If no keyword is provided, packet trailer dump is enabled in both egress and ingress directions.
Privileged Exec
|
|
---|---|
SAMI Release 3.4 |
This command was introduced in conjunction with the CSG2 Release 5.0. |
This command impacts the datapath performance of the SAMI processors. You should only use this command when directed to do so by Cisco Technical Assistance Center (TAC) engineers.
Here is an example of the debug sami pkttrailer dump command:
Router#debug sami pkttrailer dump
Router#debug sami pkttrailer dump ingress
Router#debug sami pkttrailer dump egress
To enable client-related remote console and logging (RCAL) debugging, use the debug sami rcal-client command in privileged EXEC mode.
debug sami rcal-client
no debug sami rcal-client
This command has no keywords or arguments.
No default behavior or values exist.
Privileged EXEC
|
|
---|---|
Release 1.0 |
This command was introduced. |
Use this command to enable/disable server-related RCAL debugging.
The following example illustrates how to use the debug sami rcal-client command.
Router# debug sami rcal-client
To enable logs to be generated and sent to the supervisor for all events at and above the specified log-level, use the logging-main-cpu command in privileged EXEC mode. To turn off log generation, use the no form of this command.
logging-main-cpu udp-port log-level [ip-addr]
no logging-main-cpu udp-port log-level [ip-addr]
The RCAL feature is enabled on a processor and the processor sends messages for level 3 and above.
Privileged EXEC
|
|
---|---|
Release 1.0 |
This command was integrated into Cisco SAMI Release 1.0. |
This command enables log generation to the supervisor for all events at and above the log-level value.
The UDP port specified must match the port specified on the supervisor. By default, port 4000 is used. This is the recommended port. Optionally, a vlan IP address can be specified for transporting this traffic from PPCs 3-8.
The following table defines the severity levels:
The following example illustrates how to use the logging main-cpu command.
Router# logging main-cpu 4000
To enables health monitoring on the paths between the PPC and IXP1 and IXP2 (future), use the sami health-monitoring command in privilege EXEC mode. To remove the configuration, use the no form of this command.
sami health-monitoring {ixp1 | ixp2}
no sami health-monitoring {ixp1 | ixp2}
ixp1 |
Specifies to monitor the health of the path to IXP1. |
ixp2 |
Specifies to monitor the health of the path to IXP1. Note This keyword option is intended for future use. |
By default, health monitoring is enabled for IXP1 and disabled for IXP2.
Global configuration
|
|
---|---|
Release 1.0 |
This command was introduced. |
Use this command to enable sanity monitoring on the path from the PPC to IXP1.
Health monitoring is configured on the SAMI PPC. The PPC tracks the health of a path by sending probes to a destination and waiting for a response. If the PPC does not receive a response to a probe, it determines that the path is not healthy and sends a notification to the SAMI LCP, which then initiates a module reload.
The PPC identifies the health of a path in the following categories:
•Passed—The PPC returns a valid response.
•Failed—The PPC did not receive a valid response to a probe or was unable to reach a destination for a specified number of retries.
When a PPC is configured for health monitoring, it sends active probes periodically to determine the state of a path.
The following example illustrates how to use the sami health-monitoring command.
Router(config)# sami health-monitoring ipx1
To enable health monitoring on all paths between the PPC and the supervisor, use the sami health-monitoring probe command. To remove the configuration, use the no form of the command.
sami health-monitoring probe ip address [interval seconds] [retries number}
No default behavior or values exist.
Global Configuration
|
|
---|---|
Release 1.0 |
This command was introduced. |
Use this command to enable health monitoring on all the paths between the PPC and the supervisor.
Health monitoring is configured on the SAMI PPC. The PPC tracks the health of a path by sending probes to a destination and waiting for a response. If the PPC does not receive a response to a probe, it determines that the path is not healthy and sends a notification to the SAMI LCP, which then initiates a module reload.
The PPC identifies the health of a path in the following categories:
•Passed—The PPC returns a valid response.
•Failed—The PPC did not receive a valid response to a probe or was unable to reach a destination for a specified number of retries.
When a PPC is configured for health monitoring, it sends active probes periodically to determine the state of a path.
The following example illustrates how to use the sami health-monitoring probe command.
Router(config)# sami health-monitoring probe 10.1.1.14 interval 250 retries 25
To configure the module to be reset when a path failure has occurred, use the sami health-monitoring probe reset command in privileged EXEC mode. To remove this configuration, use the no form of the command.
sami health-monitoring {ipx1 | ixp2 | probe} reset
No default behavior or values exist.
Global configuration
|
|
---|---|
Release 1.0 |
This command was introduced. |
Use this command to configure the module to be reset when a path failure has occurred.
Health monitoring is configured on the SAMI PPC. The PPC tracks the health of a path by sending probes to a destination and waiting for a response. If the PPC does not receive a response to a probe, it determines that the path is not healthy and sends a notification to the SAMI LCP, which then initiates a module reload.
The PPC identifies the health of a path in the following categories:
•Passed—The PPC returns a valid response.
•Failed—The PPC did not receive a valid response to a probe or was unable to reach a destination for a specified number of retries.
When a PPC is configured for health monitoring, it sends active probes periodically to determine the state of a path.
The following example illustrates how to use the sami health-monitoring reset command.
Router(config)# sami health-monitoring probe reset
To display the statistics of the two IXP interface on the SAMI, use the show interface command in privileged EXEC mode.
show interface
This command has no keywords or arguments.
No default behavior or values exist.
Privileged EXEC
|
|
---|---|
CSG2 Release 6.0 and LTE Release 2.0 |
This command was introduced. |
show interface will also show the IXP interaface's packet count, byte count , packet rate, and data rate.
The following example displays the output for the show interface command:
Router#show interfaces
Interface-IXP1 is up, line protocol is up
Hardware is Bouncer IXP1, address is 0023.5e25.9a32 (bia 0023.5e25.9a32)
MTU 0 bytes, BW 10000000 Kbit/sec, DLY 0 usec,
reliability 255/255, txload 1/255, rxload 1/255
Encapsulation ARPA, loopback not set
Last input never, output never, output hang never
Last clearing of "show interface" counters never
Input queue: 0/75/0/0 (size/max/drops/flushes); Total output drops: 0
5 minute input rate 0 bits/sec, 19 packets/sec
5 minute output rate 0 bits/sec, 19 packets/sec
346569 packets input, 0 bytes, 0 no buffer
Received 0 broadcasts, 0 runts, 0 giants, 0 throttles
0 input errors, 0 CRC, 0 frame, 0 overrun, 0 ignored
0 input packets with dribble condition detected
345883 packets output, 0 bytes, 0 underruns
0 output errors, 0 collisions, 0 interface resets
0 unknown protocol drops
0 unknown protocol drops
0 babbles, 0 late collision, 0 deferred
0 lost carrier, 0 no carrier
0 output buffer failures, 0 output buffers swapped out
Interface-IXP2 is up, line protocol is up
Hardware is Bouncer IXP2, address is 0023.5e25.9a32 (bia 0023.5e25.9a32)
MTU 0 bytes, BW 10000000 Kbit/sec, DLY 0 usec,
reliability 255/255, txload 1/255, rxload 1/255
Encapsulation ARPA, loopback not set
Last input never, output never, output hang never
Last clearing of "show interface" counters never
Input queue: 0/75/0/0 (size/max/drops/flushes); Total output drops: 0
5 minute input rate 0 bits/sec, 11 packets/sec
5 minute output rate 0 bits/sec, 11 packets/sec
200341 packets input, 0 bytes, 0 no buffer
Received 0 broadcasts, 0 runts, 0 giants, 0 throttles
0 input errors, 0 CRC, 0 frame, 0 overrun, 0 ignored
0 input packets with dribble condition detected
200341 packets output, 0 bytes, 0 underruns
0 output errors, 0 collisions, 0 interface resets
0 unknown protocol drops
0 unknown protocol drops
0 babbles, 0 late collision, 0 deferred
0 lost carrier, 0 no carrier
0 output buffer failures, 0 output buffers swapped out
GigabitEthernet0/0 is up, line protocol is up
Hardware is MPC8500_FIFO_ETSEC, address is 0023.5e25.9a32 (bia 0023.5e25.9a32)
MTU 1500 bytes, BW 2000000 Kbit/sec, DLY 10 usec,
To display platform information, use the show platform command.
show platform [cookie | fpga | cpld]
cookie |
Displays information provided by the dump. |
fpga |
Displays field programmable gate array (FPGA)-related registers. |
cpld |
Displays complex programmable logic device (CPLD)-related registers. |
No default behavior or values exist.
Privileged EXEC
|
|
---|---|
Release 1.0 |
This command was introduced. |
Use this command to provide a dump of various registers and other platform specific information.
The following example illustrates how to use the initial part of the show platform command.
Router# show platform
Interrupt Throttling:
Throttle Count = 00000000 Timer Count = 00000000
Netint usec = 00001000 Netint Mask usec = 00000200
Active = 0 Configured = 1
Longest IRQ = 00000367
The following example illustrates how to use the IXP0 part of the show platform command.
CDE IXP0 INTERFACE
======================
Packets received 0
Packets transmitted 0
Num bad pkts recvd on fast spi channel0 0
Num bad pkts recvd on slow spi channel8 0
Num bad pkts recvd on fast spi channel2 0
Num bad pkts recvd on slow spi channel4 0
IXP0 Fast VOQ status [empty] [not full]
IXP0 BRCM VOQ status [empty] [not full]
IXP0 pull status [pulling]
IXP0 spi src status [healthy]
IXP0 spi snk status [healthy]
To display the configuration mode of a PowerPC (PPC), use the show sami config-mode command.
show sami config-mode
This command has no keywords or arguments.
No default behavior or values exist.
Privileged EXEC
|
|
---|---|
Release 1.0 |
This command was introduced. |
Use the show sami config-mode command to display the configuration mode of the PPC.
Supervisor is currently the only supported configuration mode.
The following example illustrates how to use the show sami config-mode command.
Router# show sami config-mode
sami config-mode supervisor
===========================================================
To display health monitoring status and counters for the path to IXP1, IXP2 (future), and the supervisor, use the show sami health-monitoring command.
show sami health-monitoring [ixp | processor]
ixp |
Displays health monitoring status and counters for the path to IXP1 or IXP2 (future). |
processor |
Displays health monitoring status and counters for the path to the supervisor. |
No default behavior or values exist.
Privileged EXEC
|
|
---|---|
Release 1.0 |
This command was introduced. |
Use this command to display counters specific to health monitoring for the path to the IXPs or the path to the supervisor.
The following example shows how to display health monitoring-related counters and status:
Router#show sami health-monitoring
IXP1: DISABLED
0/0 Missed/Rcvd consecutive responses
0/0 Missed/Rcvd cumulative responses
0 Failed to send
IXP2: DISABLED
0/0 Missed/Rcvd consecutive responses
0/0 Missed/Rcvd cumulative responses
0 Failed to send
ICMP PROBE: PROBING
0/0 Missed/Rcvd consecutive responses
10/8 Missed/Rcvd cumulative responses
40 Failed to send
Table 2 describes the fields shown in the display.
To display detailed information about the SAMI, use the show sami info command.
show sami info
This command has no keywords or arguments.
No default behavior or values exist.
Privileged EXEC
|
|
---|---|
Release 1.0 |
This command was introduced. |
Use the show sami info command to display information about the SAMI.
The following examples illustrates how to use the show sami info command.
Router# show sami info
Slot Number: 4
Daughtercard Number: 1
Processor/Session Number: 3
PPC Number: 1
Active Supervisor EOBC address: 127.0.0.71
Active PPC EOBC address: 127.0.0.43
Daughter Board Identifier: P3 (2GB)
Daughter Board Hardware Version:10000
To display the counters for IP control protocol (IPCP) packets processed to and from IPCP peers, use the show sami ipcp statistics command.
show sami ipcp statistics
This command has no keywords or arguments.
No default behavior or values exist.
Privileged EXEC
|
|
---|---|
Release 1.0 |
This command was introduced. |
Use the show sami ipcp statistics command to display counters of IPCP packets received and sent to IPCP peers.
The following examples illustrate the show sami ipcp statistics command.
Router# show sami ipcp statistics
IPCP Statistics Summary: Tx Tx-ERR Rx Rx-ERR
===========================================================
303681 0 452316 0
===========================================================
Router#
To display the counters of IP control protocol (IPCP) packets processed to and from a SAMI daughter card, use the show sami ixp command in privileged EXEC mode.
show sami ixp {1 | 2}
ixp |
Displays IPC counters for the IXP. |
processor |
Displays IPC counters for the PPC. |
No default behavior or values exist.
Privileged EXEC
|
|
---|---|
Release 1.0 |
This command was introduced. |
This command is enhanced to display inband packets forwarded and received to and from IXP1 and IXP2 with trailer. |
Use the show sami ixp command to display counters of IXP packets received and sent to the IXP.
The following examples illustrate the show sami ipcp statistics command.
Router# show sami ixp 1
IPCP Statistics Summary: Tx Tx-ERR Rx Rx-ERR
===========================================================
303681 0 452316 0
===========================================================
Router#
To display IPC statistics for IXP, and also display important tables of the IXPs, use the show sami ixp statistics privileged EXEC command.
show sami ixp statistics
There are no keywords or arguments for this command.
No default behavior or values exist.
Privileged EXEC
This command displays IPC statistics for IXP and also displays important tables of the IXPs.
The following example illustrates the show sami ixp statistics command.
SAMI-PPC3#show sami ixp statistics
------------------------------
IPC IXP 1 Stats
------------------------------
SAMI-PPC3#show sami ixp statistics
------------------------------
Interface - IXP1
------------------------------
Pkts rx = 733325
Pkts tx0 = 83087
Pkts tx1 = 0
Bytes rx = 0
Bytes tx0 = 0
Bytes tx1 = 0
------------------------------
Interface - IXP2
------------------------------
Pkts rx = 650249
Pkts tx0 = 0
Pkts tx1 = 0
Bytes rx = 0
Bytes tx0 = 0
Bytes tx1 = 0
------------------------------
IPC IXP 1 Stats
------------------------------
ixp communications
ixp sends = 73, retries = 0 send failures = 0
ixp info sem fail = 0
get buffer fail = 0, timeout = 0
ixp packets received = 73
out of sequence = 0
with unknown error id = 0
ixp response code:
no error = 56
unknown command = 0
no resource = 0
bad parameter = 0
already existed = 1
not found for deletion = 1
unknown error = 0
ixp input trace messages = 0
pkts egress through ixp = 20
async messages from ixp = 100
queued to nets = 60
queued to process = 40
------------------------------
IPC IXP 2 Stats
------------------------------
ixp communications
ixp sends = 73, retries = 0 send failures = 0
ixp info sem fail = 0
get buffer fail = 0, timeout = 0
ixp packets received = 73
out of sequence = 0
with unknown error id = 0
ixp response code:
no error = 56
unknown command = 0
no resource = 0
bad parameter = 0
already existed = 1
not found for deletion = 1
unknown error = 0
ixp input trace messages = 0
pkts egress through ixp = 0
async messages from ixp = 100
queued to nets = 70
queued to process = 30
------------------------------
IXP Stats Update Counters
To show statistics corresponding to the packet trailers (these statistics are cumulative of IXP1 and IXP2), use the show sami ixp trailerstats command in Privileged EXEC mode.
show sami ixp trailerstats
There are no keywords or arguments for this command.
No default behavior or values exist.
Privileged EXEC
|
|
---|---|
This command was introduced. |
Use the show sami ixp trailersets command to display statistics corresponding to the packet trailers. These statistics are cumulative of IXP1 and IXP2. The following list identifies the statistics that are displayed:
•Number of packet received with trailer.
•Number of packet on which trailer was written by application.
•Number of packets transmitted with trailer.
•Number of packets for which trailer write failed due to space not available in data buffer.
•Number of packets for which trailer write failed due to trailer size > MAX_BOUNCER_TRAILER_BYTES.
•Number of packets for which trailer write failed due to insufficient pak subblock resources.
The following example illustrates the show sami ixp trailersets command.
To display all the address(es) registered by the application along with the VRF tableid, callback functions address, callback parameters address, next hop IP and ref count, use the show sami mac-resolver dest-addr-list command in privileged EXEC mode.
show sami mac-resolver dest-addr-list [ip]
ip |
(optional) IPv4/IPv6 address for which data is required. |
If no keyword is provided, the mac resolver entries for all the registered IP's are dumped.
Privileged EXEC
|
|
---|---|
SAMI Release 3.4 |
This command was introduced in conjunction with the Cisco LTE 1.0 Release. |
If given, the ip keyword displays only those entries whose destination IP matches with the given IP.
Here is an example of the
SAMI#show sami mac-resolver dest-addr-list
Table Id Ref-Count Dest IP
via Nexthop IP
0 1 20.20.20.51
via 20.20.20.51
0 1 2001::10
via 2001::10
0 1 100.0.0.1
via 20.20.20.51
There are 3 elements in the list
show sami mac-resolver dest-addr-list 2001::10
Table Id Ref-Count Dest IP
via Nexthop IP
0 1 2001::10
via 2001::10
There are 1 elements in the list with IP 2001::10
show sami mac-resolver dest-addr-list 20.20.20.51
Table Id Ref-Count Dest IP
via Nexthop IP
0 1 20.20.20.51
via 20.20.20.51
There are 1 elements in the list with IP 20.20.20.51
To display the next-hop IP, ref count, mac address, table ID and the encapsulation type, use the show sami mac-resolver next-hop list in privileged EXEC mode.
show sami mac-resolver next-hop list [ip]
ip |
(optional) IPv4/IPv6 address for which data is required. |
If no keyword is provided, the mac resolver entries for all the registered IP's are dumped.
Privileged EXEC
|
|
---|---|
Release 3.4 |
This command was introduced in conjunction with the Cisco LTE 1.0 Release. |
If given, displays the entries whose next-hop IP matches to the given IP.
Here is an example of the show sami mac-resolver next-hop list command:
SAMI#show sami mac-resolver next-hop-list
TableId IP Address MAC Addr Enctype Ref-count
0 20.20.20.51 0200.0200.0200 1 2
0 2001::10 0200.0200.0200 1 1
There are 2 elements in the list
show sami mac-resolver next-hop-list 2001::10
TableId IP Address MAC Addr Enctype Ref-count
0 2001::10 0200.0200.0200 1 1
There are 1 elements in the list with IP 2001::10
To display statistics corresponding to IPC with IXP using PCI, use the show sami pci ipc statistics privileged EXEC command.
show sami pci ipc statistics
There are no keywords or arguments for this command.
There are no default values.
Privileged EXEC
Here is an example of the show sami pci ipc statistics command:
SAMI#show sami pci ipc statistics
----------- Slot 2/CPU 3, show sami pci ipc statistics -------------
From PROC 3 To IXP1:
Tx-fn = 132 Rx-fn = 132
Msgs sent = 132 Msgs received = 140
Msgs over I2R = 132 Msgs over I2P = 8
DMA Attempts = 10 DMA Success = 10
Tx-ring full = 0 Rx-ring empty = 0
DMA ctx failures = 0 Invalid data = 0
No Rx Buffers = 0
Backpressure triggered= 0 Backpressure state = INACTIVE
Num of msgs requeued for backpressure = 0
From PROC 3 To IXP2:
Tx-fn = 132 Rx-fn = 132
Msgs sent = 132 Msgs received = 132
Msgs over I2R = 132 Msgs over I2P = 0
DMA Attempts = 0 DMA Success = 0
Tx-ring full = 0 Rx-ring empty = 0
DMA ctx failures = 0 Invalid data = 0
No Rx Buffers = 0
Backpressure triggered= 0 Backpressure state = INACTIVE
Num of msgs requeued for backpressure = 0
----------- Slot 2/CPU 4, show sami pci ipc statistics -------------
From PROC 4 To IXP1:
Tx-fn = 132 Rx-fn = 132
Msgs sent = 132 Msgs received = 140
Msgs over I2R = 132 Msgs over I2P = 8
DMA Attempts = 10 DMA Success = 10
Tx-ring full = 0 Rx-ring empty = 0
DMA ctx failures = 0 Invalid data = 0
No Rx Buffers = 0
Backpressure triggered= 0 Backpressure state = INACTIVE
Num of msgs requeued for backpressure = 0
From PROC 4 To IXP2:
Tx-fn = 132 Rx-fn = 132
Msgs sent = 132 Msgs received = 132
Msgs over I2R = 132 Msgs over I2P = 0
DMA Attempts = 0 DMA Success = 0
Tx-ring full = 0 Rx-ring empty = 0
DMA ctx failures = 0 Invalid data = 0
No Rx Buffers = 0
Backpressure triggered= 0 Backpressure state = INACTIVE
Num of msgs requeued for backpressure = 0
----------- Slot 2/CPU 5, show sami pci ipc statistics -------------
From PROC 5 To IXP1:
Tx-fn = 132 Rx-fn = 132
Msgs sent = 132 Msgs received = 140
Msgs over I2R = 132 Msgs over I2P = 8
DMA Attempts = 10 DMA Success = 10
Tx-ring full = 0 Rx-ring empty = 0
DMA ctx failures = 0 Invalid data = 0
No Rx Buffers = 0
Backpressure triggered= 0 Backpressure state = INACTIVE
Num of msgs requeued for backpressure = 0
From PROC 5 To IXP2:
Tx-fn = 132 Rx-fn = 132
Msgs sent = 132 Msgs received = 132
Msgs over I2R = 132 Msgs over I2P = 0
DMA Attempts = 0 DMA Success = 0
Tx-ring full = 0 Rx-ring empty = 0
DMA ctx failures = 0 Invalid data = 0
No Rx Buffers = 0
Backpressure triggered= 0 Backpressure state = INACTIVE
Num of msgs requeued for backpressure = 0
----------- Slot 2/CPU 6, show sami pci ipc statistics -------------
From PROC 6 To IXP1:
Tx-fn = 132 Rx-fn = 132
Msgs sent = 132 Msgs received = 140
Msgs over I2R = 132 Msgs over I2P = 8
DMA Attempts = 10 DMA Success = 10
Tx-ring full = 0 Rx-ring empty = 0
DMA ctx failures = 0 Invalid data = 0
No Rx Buffers = 0
Backpressure triggered= 0 Backpressure state = INACTIVE
Num of msgs requeued for backpressure = 0
From PROC 6 To IXP2:
Tx-fn = 132 Rx-fn = 132
Msgs sent = 132 Msgs received = 132
Msgs over I2R = 132 Msgs over I2P = 0
DMA Attempts = 0 DMA Success = 0
Tx-ring full = 0 Rx-ring empty = 0
DMA ctx failures = 0 Invalid data = 0
No Rx Buffers = 0
Backpressure triggered= 0 Backpressure state = INACTIVE
Num of msgs requeued for backpressure = 0
----------- Slot 2/CPU 7, show sami pci ipc statistics -------------
From PROC 7 To IXP1:
Tx-fn = 132 Rx-fn = 132
Msgs sent = 132 Msgs received = 140
Msgs over I2R = 132 Msgs over I2P = 8
DMA Attempts = 10 DMA Success = 10
Tx-ring full = 0 Rx-ring empty = 0
DMA ctx failures = 0 Invalid data = 0
No Rx Buffers = 0
Backpressure triggered= 0 Backpressure state = INACTIVE
Num of msgs requeued for backpressure = 0
From PROC 7 To IXP2:
Tx-fn = 132 Rx-fn = 132
Msgs sent = 132 Msgs received = 132
Msgs over I2R = 132 Msgs over I2P = 0
DMA Attempts = 0 DMA Success = 0
Tx-ring full = 0 Rx-ring empty = 0
DMA ctx failures = 0 Invalid data = 0
No Rx Buffers = 0
Backpressure triggered= 0 Backpressure state = INACTIVE
Num of msgs requeued for backpressure = 0
----------- Slot 2/CPU 8, show sami pci ipc statistics -------------
From PROC 8 To IXP1:
Tx-fn = 132 Rx-fn = 132
Msgs sent = 132 Msgs received = 140
Msgs over I2R = 132 Msgs over I2P = 8
DMA Attempts = 10 DMA Success = 10
Tx-ring full = 0 Rx-ring empty = 0
DMA ctx failures = 0 Invalid data = 0
No Rx Buffers = 0
Backpressure triggered= 0 Backpressure state = INACTIVE
Num of msgs requeued for backpressure = 0
From PROC 8 To IXP2:
Tx-fn = 132 Rx-fn = 132
Msgs sent = 132 Msgs received = 132
Msgs over I2R = 132 Msgs over I2P = 0
DMA Attempts = 0 DMA Success = 0
Tx-ring full = 0 Rx-ring empty = 0
DMA ctx failures = 0 Invalid data = 0
No Rx Buffers = 0
Backpressure triggered= 0 Backpressure state = INACTIVE
Num of msgs requeued for backpressure = 0