The
ping
command is a convenient way to test the ability of an interface to send and receive packets over the
network. The
ping
command sends ICMP echo request packets to a specified destination address, which
should send an equal number of ICMP echo reply packets in reply. By measuring the numbering of packets
that are successfully returned, as well as how long each packet takes to be returned, you can quickly obtain a
rough idea of the Layer 3 to Layer 3 connectivity between two interfaces.
The IP
ping
command has the following syntax:
ping
or
ping ip-address
[
repeat count
] [
data hex
] [
size datagram-size
]
If you enter just
ping
, the command interactively prompts you for all other parameters. Otherwise, you must
specify at least a specific IP address as the destination for the ping. You can also optionally specify the
following parameters:
•
repeat count
—
Number of ICMP echo request packets to send. The default is five packets.
•
data hex
—
The data pattern, in hexadecimal, to be sent in the ICMP echo request packets.
•
size datagram-size
—
Specifies the size, in bytes, of the ICMP echo request packets to be sent. The range
is 40 to 18024 bytes, with a default of 100 bytes.
Using the Cisco IOS Event Tracer to Troubleshoot Problems
This feature is intended for use as a software diagnostic tool and should be configured only under the
direction of a Cisco Technical Assistance Center (TAC) representative.
Note
The Event Tracer feature provides a binary trace facility for troubleshooting Cisco IOS software. This feature
gives Cisco service representatives additional insight into the operation of the Cisco IOS software and can be
useful in helping to diagnose problems in the unlikely event of an operating system malfunction or, in the
case of redundant systems, route processor switchover.
Event tracing works by reading informational messages from specific Cisco IOS software subsystem
components that have been preprogrammed to work with event tracing, and by logging messages from those
components into system memory. Trace messages stored in memory can be displayed on the screen or saved
to a file for later analysis.
The SPAs currently support the
“
spa
”
component to trace SPA OIR-related events.
For more information about using the Event Tracer feature, refer to the following URL:
en/US/docs/ios/12_0s/feature/guide/evnttrcr.html
Preparing for Online Insertion and Removal of a SPA
The Cisco ASR 1000 Series Aggregation Services Routers support online insertion and removal (OIR) of the
SIP, in addition to each of the SPAs. Therefore, you can remove a SIP with its SPAs still intact, or you can
remove a SPA independently from the SIP, leaving the SIP installed in the router.
This means that a SIP can remain installed in the router with one SPA remaining active, while you remove
another SPA from one of the SIP subslots. If you are not planning to immediately replace a SPA into the SIP,
Cisco ASR 1000 Series Aggregation Services Routers SIP and SPA Software Configuration Guide, Cisco IOS XE
Everest 16.5
OL-14127-17
395
Troubleshooting the Cisco WebEx Node for the ASR 1000 Series Aggregation Services Routers
Using the Cisco IOS Event Tracer to Troubleshoot Problems