IBM SAN768B-2, Руководство пользователя

Страница: 37 / 228

v
Nondisruptive "hot" software code loads and activation
v
Easy configuration, save, and restore
The high-availability software architecture of the SAN768B-2 provides a common
framework for all applications that reside on the system, allowing global and local
status to be maintained through any component failure. High-availability elements
consist of the High Availability Manager, the heartbeat, the fault/health
framework, the replicated database, initialization, and software upgrade.
The High Availability Manager controls access to the standby control processor,
facilitates software upgrades, prevents extraneous CP failover activity, closes and
flushes streams as needed, provides flow control and message buffering, and
supports a centralized active and standby state.
Reliability
The SAN768B-2 uses the following error detection and correction mechanisms to
ensure reliability of data:
v
Error Detection and Correction over main control processor memory
v
Error Detection and Correction mechanism, which checks for encoder errors and
fault isolation (EDFI), such as cyclic redundancy checking (CRC), parity
checking, checksum, and illegal address checking
v
Power-on self test (POST)
v
Dual control processors that enable hot, nondisruptive fast firmware upgrades
v
One serial port and two Ethernet ports on each control processor for
management and for service. Offline control processor diagnostics and remote
diagnostics simplify troubleshooting. The standby control processor monitors
diagnostics to ensure the system is operational should a failover be necessary.
v
Bus monitoring and control of blades and other field-replaceable units (FRUs).
Serviceability
The SAN768B-2 provides the following features to enhance and ensure
serviceability:
v
Modular design with hot-swappable components
v
Flash memory that stores two firmware images per control processor
v
USB port on control processor blades for most tasks that formerly required an
FTP/SCP server, including software and firmware upgrades
v
Nonvolatile random-access memory (NVRAM), containing the OEM serial
number, IBM serial number, revision information, and part number information
v
Background health-check daemon
v Memory scrubber, self test, and bus ping to determine if a bus is not functioning
v
RASlog messages
v SMI-S compliant
v
Hardware and software watchdog timers
v
Status LEDs
v
Predictive diagnostics analysis through Fabric Watch
v
SNMP (including version 3) integration with higher-layer managers
Chapter 1. Introduction
9