Cisco ASR 5000 Series, Обзор продукта

Страница: 87 / 992

ASR 5000 Hardware Platform Overview
ASR 5000 Application Cards ▀
Cisco ASR 5000 Series Product Overview ▄
OL-22938-02
Item Description
4
System Level Status LEDs —Show the status of overall system health and/or maintenance requirements. (See Applying
Power and Verifying Installation for definitions).
5
PC-Card/PCMCIA Slot —Stores or moves software, diagnostics, and other information.
6
System Alarm Speaker —Sounds an audible alarm when specific system failures occur.
7
Alarm Cut-Off (ACO)— Press and release this recessed toggle switch to reset the system alarm speaker and other audible
or visual alarm indicators connected to the CO Alarm interface on the SPIO.
SMC RAID Support
Each SMC is equipped with a hard disk, commonly referred to as a Small Form Factor (SFF) disk.
Important:
The hard disk is not physically accessible. Disk failure constitutes SMC failure.
To access physical RAID details, such as disk manufacturer, serial number, number of partitions, disk size, and so on, in
the Executive Mode of the CLI, type the command
.
If there is a redundant SMC in the chassis, the standby disk works as a mirror to the disk in the active chassis, forming
an active Redundant Array of Inexpensive Disks (RAID).
Use the HD RAID commands in the Command Line Interface Reference to configure RAID. RAID control mechanisms
allow xDR charging data to be written to the hard disks on both the active and standby SMCs for later upload to a
suitable local or remote storage server. Configuring CDR, EDR, and UDR storage is described in the Command Line
Interface Reference.
Event logs related to disk and RAID include disk name, serial number and RAID UUID for reference. They are
generated at the Critical, Error, Warning, and Informational levels. For more information on configuring and viewing
log files, refer to Configuring and Viewing System Logs in the System Administration Guide.
Event logs at the Critical level are generated for service-affecting events such as:
RAID failure, including failures during runtime and various cases of initial RAID discovery and disk partition
failures
File system failure when the system fails to initialize or mount file systems
Network failure for NFS server-related errors
Event logs at the Error level are generated for important failures:
RAID disk failure, including failures during runtime
Internal errors, including forking process failures
Event logs at Warning level are generated for important abnormal cases:
Overwriting a valid or invalid disk partition, RAID image, and file system
RAID construction in progress and possible failure
Low disk space
Files deleted to free up disk space