Generating An Ssd - Cisco ASR 5000 Administration Manual

Staros release 21.1
Hide thumbs Also See for ASR 5000:
Table of Contents

Advertisement

Troubleshooting
INBOUND>>>>> 10:02:35:518 Eventid:25000(0)
PPP Rx PDU (12)
IPCP 12: Conf-Req(2), IP-Addr=0.0.0.0
<<<<OUTBOUND 10:02:35:518 Eventid:25001(0)
PPP Tx PDU (14)
IPCP 14: Conf-Nak(2), IP-Addr=192.168.250.87
INBOUND>>>>> 10:02:35:519 Eventid:25000(0)
PPP Rx PDU (12)
IPCP 12: Conf-Req(3), IP-Addr=192.168.250.87
The monitor remains active until disabled. To quit the protocol monitor and return to the prompt, press q.

Generating an SSD

An SSD is an instance of the output when the Exec mode show support details command is run. It displays
a comprehensive list of system information that is useful for troubleshooting purposes. In most cases, the
output of this command is requested by the Technical Assistance Center (TAC).
An SSD output .tar file can redirected to a local or remote location (URL).
The .tar file includes:
• support_summary - An ASCII text file that contains the support detail information.
• information.minicores.tar - A .tar file that contains any minicore files found on the system. Minicore
The show support details command includes information that is not otherwise accessible to users but that is
helpful in the swift resolution of issues by TAC.
Important
For releases prior to 20.0, an operator could initiate another SSD while an SSD was already running. In a
large configuration, the SSD request often timed out while waiting for the first one to complete. The operator
was not aware of the failure until the entire timeout expired. An operator could have more than one SSD
running simultaneously.
For release 20.0 and higher, if an SSD is in progress when the operator enters the show support details
command, StarOS responds with a warning message stating that an SSD is already in progress and the user
should try again later. The operator is restricted to running only one SSD instance at a time.
There are optional keywords to the show support details command that can target the SSD to only report
specific type of information. These keywords can reduce the amount of time required to generate the SSD/
files contain memory core dumps that are captured during some events. These core dumps provide
specific memory locations and other information about the event. This information is useful to the
technical support team in identifying where and when an event occurred along with its probably cause.
Platforms with large configuration files can take up to 30 minutes to complete an SSD. Executing the
show support details command consumes system resources and may reduce traffic throughput.
ASR 5000 System Administration Guide, StarOS Release 21.1
Generating an SSD
227

Advertisement

Table of Contents
loading

Table of Contents