•
From the console port:
By default, the system automatically displays events over the console interface
to a terminal provided that there is no CLI session active.
This section provides instructions for viewing event logs using the CLI. These instructions assume that you
are at the root prompt for the Exec mode.
Step 1
Copy the active log memory buffer to the inactive log memory buffer.
When the active log memory buffer is copied to the inactive log memory buffer existing information in the inactive log
memory buffer is deleted.
Both active and inactive event log memory buffers can be viewed using the CLI in Exec mode. However, it is preferable
to view the inactive log in order to prevent any data from being over-written. The information from the active log buffer
can be copied to the inactive log buffer by entering the following command:
[local]
host_name
#
logs checkpoint
Step 2
View the logs by entering the following command:
[local]
host_name
#
show logs
A number of optional keywords/variables are available for the
show logs
command. Refer to the
Exec Mode Show
Commands
chapter in the
Command Line Interface Reference
for more information.
Configuring and Viewing Crash Logs
In the unlikely even of a software crash, the system stores information that could be useful in determining the
reason for the crash. This information can be maintained in system memory or it can be transferred and stored
on a network server.
The system supports the generation of the following two types of logs:
•
Crash log:
Crash logs record all possible information pertaining to a software crash (full core dump).
Due to their size, they can not be stored in system memory. Therefore, these logs are only generated if
the system is configured with a Universal Resource Locator (URL) pointing to a local device or a network
server where the log can be stored.
•
Abridged crash log:
Crash event records are automatically generated when a software crash occurs and
are stored in flash memory on management cards. The abridged crash log contains a list crash event
records along with associated dump files. This log allows you to view event records and dump files via
CLI commands.
Crash Logging Architecture
The crash log is a persistent repository of crash event information. Each event is numbered and contains text
associated with a CPU (minicore), NPU or kernel crash. The logged events are recorded into fixed length
records and stored in /flash/crashlog2.
Whenever a crash occurs, the following crash information is stored:
1
The event record is stored in /flash/crashlog2 file (the crash log).
ASR 5500 System Administration Guide, StarOS Release 21.5
143
System Logs
Configuring and Viewing Crash Logs