Administrator's Guide
The two fan modules are physically identical, but their control is not. The Fault/health LED on FAN
1 is a single bi-color LED controlled by the EMU via the Health Monitor – it is either off, steady
green, or flashing amber. The lens of the fan LED is colorless and looks grayish-white when off.
System Fan — Fan 1
Fan 1 LED is driven by the Health Monitor PSoC under direction of the EMP firmware. The fan
microprocessor inside the Fan module cannot sense or control this LED. If the EMU fails, or if the
connection between the EMU and the fan fails, the LED cannot be controlled and thus may not
reflect actual state. Also, because Fan 1 LED has no power unless enclosure power is on, the EMP
cannot indicate Fan status in standby mode.
Unlike the EMU health LED circuit, there is no autonomic hardware circuit controlling the FAN Fault
LED. Assuming the LED is working, it flashes Amber by the EMU if one or two of the 3 fan rotors
is not functioning, or if the microprocessor on the fan module is unresponsive, or if MFG NVRAM
on the module is unreadable.
Drive Fan — Fan 2
The Fault/health LED on FAN 2 is not controlled at all by the EMU – but is controlled by one of
the management processors inside the SAS IO Module. This LED cannot be lit without enclosure
power ON, and its state depends upon signals from one of the SAS IO modules.
To troubleshoot a degraded fan, you can use the EMU CLI commands SHOW ENCLOSURE STATUS
and SHOW ENCLOSURE FAN ALL described in “EMU reference” (page 153).
EMU CLI SHOW commands
Use the EMU CLI SHOW commands described in “EMU reference” (page 153) to obtain additional
information about component status as indicated by the hardware LEDs described in “Component
LEDs” (page 51). To access the CLI, log in to the EMU as Administrator.
The system is shipped with a single enabled user account: Administrator. The password of the
Administrator account is unique, programmed at the factory, and printed on the tear-off label on
the back of the unit and the label on top of the EMU. Logging in to the system requires the Secure
Shell protocol (SSH). Windows systems can use ssh clients such as PuTTy, which can be freely
downloaded.
To log in to the EMU:
1. Note the IP address of the EMU.
2. ssh to the EMU.
3. Log in as Administrator.
Following is a sample login session.
[user@host ~]$ ssh Administrator@10.0.0.10
-----------------------------------------------------------------------------
WARNING: This is a private system. Do not attempt to login unless you are an
authorized user. Any authorized or unauthorized access and use may be moni-
tored and can result in criminal or civil prosecution under applicable law.
-----------------------------------------------------------------------------
User: /src/bin/build@msaonyx
Script: ./parbuild
Directory: /src/quire/QUIRE-IDP-1-0/daily/2010110801/bld/QUIRE-IDP-1-0
FileTag: 110820102003
Date: 2010-11-08T20:03:55
Firmware Output: jsbach
Firmware Version: 0x0100
SVN Version: 2452
Administrator@10.0.0.10's password:
HP IDP System Enclosure Manager
(C) Copyright 2006-2009 Hewlett-Packard Development Company, L.P.
EMU CLI SHOW commands 59