Using Sdrs To Diagnose Problems; Sdr Cli Commands - Cisco ASR 5000 Administration Manual
Staros release 21.1
Hide thumbs
Also See for ASR 5000:
- Installation manual (294 pages) ,
- Administration manual (159 pages) ,
- Installation procedure (8 pages)
Table of Contents
Advertisement
Support Data Collector
Important
The Exec Mode show support collection command displays useful information about the Support Data
Collector. The output includes information about when the collector last ran, how long it took to run, when
it is scheduled to run again, as well as the number of SDRs currently stored, where they are stored, and how
much storage space is being used. Refer to
command.
Using SDRs to Diagnose Problems
The user can compare the SDRs by examining two or more in sequence. These SDRs are dumped out in their
CLI-formatted output display. Comparing the display outputs reveals trends and performance or configuration
differences that indicate problem areas.
Once specific record sections have been identified as having problematic characteristics, only the CLI show
commands associated with those sections need be monitored and compared to further isolate the problem
areas. In addition, individual SDRs may be transferred via system-supported protocols to remote system, or
the current collection may be transferred as a set for later analysis.
SDR CLI Commands
You may use the collected support data records to view support data chronologically. If the default list and
sequence of sections is inadequate for system monitoring, you can configure your own set of record section
commands that make up a particular support record.
Important
Important
After configuring the SDR you then configure the sleep-duration interval between record collections and the
number of historical records to be retained before being overwritten. By default, configuring this collection
information makes the collector mechanism active (if not already active).
After one or more collection intervals have passed, the SDR data becomes available for analysis. The
administrator can then use CLI commands to examine the SDR information to perform root cause analysis
and trend analysis based on how the data has changed over time. The administrator may decide to transfer the
SDRs off the system to be analyzed remotely, for example, by Cisco TAC.
Using a shorter interval to compensate for this behavior is not recommended, since it will only add to the
overhead incurred by the collection process and will ultimately impact the overall system performance.
The sleep-duration (idle-time) between scheduled collections is an important component of the
"self-throttling" mechanism that should not be circumvented by the user.
Refer to the SDR CLI Command Strings appendix for a listing of supported CLI strings (show commands)
for record sections. The listing also identifies the CLI strings supported as default record sections. You
can obtain the same listing by running the show support collection definitions command.
You may enter up to 200 SDR CLI strings in a single record section command. If you attempt to add more
than 200 CLI strings, an error message appears. You may also receive an error message if the system is
unable to parse all of the requested CLI strings because they are too complicated to parse.
Exec Mode Commands, on page 363
ASR 5000 System Administration Guide, StarOS Release 21.1
Using SDRs to Diagnose Problems
for more detail about this
361
Advertisement
Table of Contents
Troubleshooting
