X5000 G2 - NAS HP - Free user manual and instructions

Product Type	Network Attached Storage (NAS)
Model	HP X5000 G2
Form Factor	2U Rackmount
Supported Drives	Up to 12 LFF SATA/SAS drives
Processor	Intel Xeon E5-2600 v3/v4 series
Memory	32 GB up to 512 GB DDR4
Network Interfaces	4x 1GbE ports, optional 10GbE
Power Supply	Dual redundant 800W power supplies
Dimensions (H x W x D)	3.5 x 17.6 x 25.6 in (8.9 x 44.7 x 65.0 cm)
Weight	Approximately 55 lb (25 kg) fully loaded
Operating Voltage	100–240 VAC, 50/60 Hz
Power Consumption (Typical)	250 W
Operating Temperature	5°C to 35°C (41°F to 95°F)
Main Functions	File sharing, backup, virtualization, iSCSI, RAID 0/1/5/6/10
Operating System	HP StorageOS (based on Windows Storage Server)
RAID Support	Hardware RAID via HP Smart Array controller
Maintenance	Hot-swappable drives, redundant fans, predictive failure alerts
Safety	Overload protection, thermal monitoring, secure enclosure lock
Spare Parts	Power supplies, fans, hard drives, RAID controller, memory modules
Repairability	Field-replaceable units (FRUs) with tool-less access
Warranty	3-year limited warranty, 9x5 phone support
Certifications	CE, FCC, UL, RoHS

Frequently Asked Questions - X5000 G2 HP

How to initialize the HP X5000 G2?

Connect to the management port and use the HP StorageOS setup wizard. Default credentials are usually printed on the chassis.

What RAID levels are supported?

The X5000 G2 supports RAID 0, 1, 5, 6, 10, 50, 60 via the integrated HP Smart Array controller.

Can I upgrade the memory?

Yes, the system supports up to 512 GB DDR4 using registered ECC DIMMs. Refer to the manual for approved configurations.

How to replace a failed hard drive?

The drives are hot-swappable. Remove the failed drive by pressing the release lever, insert a new one, and the RAID will rebuild automatically.

How to reset the admin password?

Use the HP iLO remote management interface or connect a monitor and keyboard to the server. Boot into recovery mode to reset.

What network speeds does it support?

It has 4x 1GbE ports built-in, with optional 10GbE/25GbE add-on cards.

How to update firmware?

Download the latest firmware from the HP support site and use the HP Service Pack for ProLiant (SPP) via iLO.

Can the X5000 G2 be used for virtualization?

Yes, it supports Hyper-V and can serve as an iSCSI target for VMware or other hypervisors.

What backup software is compatible?

It works with HP Data Protector, Veeam, Acronis, and standard Windows Server backup tools.

How to access the web interface?

Open a browser and enter the IP address assigned to the management NIC. Default port is 443 with HTTPS.

USER MANUAL X5000 G2 HP

HP X5000 G2 Network Storage System Administrator Guide

Abstract

This document explains how to install, configure, and maintain all models of the HP X5000 G2 Network Storage System and is intended for system administrators. For the latest version of this guide, go to www.hp.com/support/manuals. Select NAS Systems in the storage group, and then select an X5000 G2 product.

© Copyright 2011, 2012 Hewlett-Packard Development Company, L.P.

Confidential computer software. Valid license from HP required for possession, use or copying. Consistent with FAR 12.211 and 12.212, Commercial Computer Software, Computer Software Documentation, and Technical Data for Commercial Items are licensed to the U.S. Government under vendor's standard commercial license.

The information contained herein is subject to change without notice. The only warranties for HP products and services are set forth in the express warranty statements accompanying such products and services. Nothing herein should be construed as constituting an additional warranty. HP shall not be liable for technical or editorial errors or omissions contained herein.

Acknowledgments

Microsoft®, Windows®, and Windows Server® are registered trademarks of Microsoft Corporation in the United States and other countries.

Revision History

	DateEdition	Version	DescriptionSoftware
			First release2.01.0aNovember 2011First
		Second 0aMarch 2011	Corrected network addresses for iLO connections; clarified network connections to both server blades are required during initial configuration; added details to the Known Issues section; corrected minimum supported Insight Remote Support software version; added details about the 1210m Online Volume Tool; revised content in the System recovery chapter; added SHOW CSR commands for EMU CLI and corrected instructions for using Enclosure Manager physical interface.
		Third 0aMay 2011	Added details to the Known issues section; documented new Storage Viewer feature; documented Alerts and Email enhancements; revised instructions for using the Enclosure Manager physical interface; corrected syntax for SHOW SERVER BOOT and POWEROFF SERVER Enclosure Manager commands.

Contents

1 HP X5000 G2 Network Storage System....7

Features....7
Hardware components....7
Software components....8

2 Installing the storage system....9

Verify the kit contents....9
Locate and record the product number, serial number, and SAID number....9
Unpack and rack the storage system hardware....9
Cable disk enclosures....10
Network connections....12
Power on the storage system....14
Configure the EMU and iLO management processors....15

3 Configuring the storage system....19

Accessing the storage system....19
Set up Windows and discover the second node....19
Completing initial configuration....20
Networking options....21

Network teaming....21
Multi-home....21
Dedicated networks....21
10 GbE versus 1 GbE....21

4 Monitoring and troubleshooting the storage system....22

Using notification alerts....22

Configuring Alerts and Email....22

HP System Management Homepage....26

Starting the System Management Homepage application....26
System Management Homepage main page....26

Using the System Manager....30
Component LEDs....34
EMU CLI SHOW commands....42
Known issues....43
Using Storage Viewer....47
HP Support websites....49
HP Insight Remote Support software....50
Microsoft Systems Center Operations Manager....51
Windows Recovery Environment 51

Startup Repair....51

Memory Diagnostic....53

HP 1210m Volume Online Tool....53
Obtaining the Service Agreement ID....54
Locating the storage system warranty entitlement label....54

5 Upgrading the storage system....55

Maintaining your storage system....55

Determining the current storage system software version....55

Upgrading X5000 G2 software....56

Upgrading a component's firmware....56

Resolving errors after the HP 1210m controller upgrade....59

Resolving errors after a disk drive firmware upgrade....59

Resolving an EMU upgrade issue....60

Upgrading hardware components....60

Powering the storage system off and on....60

6 Removing and replacing hardware components......61

Customer self repair....61

Best practices for replacing components....61

During replacement of the failed component....61

Accessing component replacement videos....61

Identifying the spare part....62

Replaceable parts....62

Hot, warm, and cold swap components....65

Preventing electrostatic discharge....65

Verifying component failure....66

Verifying proper operation....66

Wait times for hard disks....66

Removing the system enclosure from the rack....67

Inserting the system enclosure into the rack....68

Removing and replacing the server interposer board....68

Removing and replacing the midplane board....70

Removing and replacing a SAS cable 73

Removing and replacing the SAS I/O module....73

Removing and replacing the fan module....75

Removing and replacing the power UID button assembly....76

Removing and replacing the power supply....77

Removing and replacing the HP Ethernet I/O module....78

Removing and replacing the PCIe module (with card)....79

Removing and replacing the EMU module....81

Removing and replacing the server blade backplane....82

Removing and replacing the server airflow baffle....84

Removing and replacing the front bezel (standard)......85

Removing and replacing the front bezel (full)......87

Removing and replacing the front LED display board in the rack (standard)......88

Removing and replacing the front LED display board (full) 89

Removing and replacing a drive drawer....91

Removing and replacing the drive drawer hard drive....96

Removing and replacing the drive drawer rails (side or bottom)......98

Removing and replacing the enclosure rails....103

Removing and replacing the rack rails....108

Removing and replacing server blades....108

Removing and replacing the server blade hard drive....109

Removing and replacing the 1210m controller board components....111

Removing and replacing the 1210m cache module....113

Removing and replacing the capacitor pack....116

Removing and replacing the Mezzanine NIC....118

7 Storage system recovery....120

System Recovery DVD....120

Using a downloaded version of the System Recovery DVD....120

Drive letters are not assigned after a restore....121

Restoring the factory image with a DVD or USB flash device....121

Using a USB flash drive for storage system recovery....121

Recovering both servers....122

Recovering a single server....122

Restoring the system with Windows Recovery Environment....125

8 Support and other resources......128

Contacting HP....128

HP technical support....128

Subscription service....128

Related information....128

HP websites....128

Rack stability....129

9 Documentation feedback......130

A Managing the EMU....131

CLI reference....131

Command line conventions....131

Operational groups....131

Authentication....132

Time functions....135

Inventory and status....138

Internet control....143

Server management....146

Enclosure control....149

Forensic....153

Session....155

Using the Enclosure Manager physical interface....157

Activate Button Menu....158

Reboot EM (bE)....158

Restore Factory Defaults (Fd)....158

Recover Lost Password (Fp)....159

Set DHCP IP Address (dH)....159

Set Link Local IP Address (LL)....159

Display Current IP Address (IP)....159

Exit Button Menu....160

B Regulatory compliance notices....161

Regulatory compliance identification numbers....161

Federal Communications Commission notice....161

FCC rating label....161

Class A equipment....161

Class B equipment....161

Modification....162

Cables....162

Canadian notice (Avis Canadien)....162

Class A equipment....162

Class B equipment....162

European Union notice....162

Japanese notices....163

Japanese VCCI-A notice....163

Japanese VCCI-B notice....163

Japanese VCCI marking....163

Japanese power cord statement....163

Korean notices....163

Class A equipment....163

Class B equipment....163

Taiwanese notices....164

BSMI Class A notice....164

Taiwan battery recycle statement....164

Vietnamese notice....164

Laser compliance notices....165

English laser notice....165

Dutch laser notice....165

French laser notice....165

German laser notice....166

Italian laser notice....166

Japanese laser notice....166

Spanish laser notice....167

Recycling notices....167

English recycling notice....167

Bulgarian recycling notice....168

Czech recycling notice....168

Danish recycling notice....168

Dutch recycling notice....168

Estonian recycling notice....169

Finnish recycling notice....169

French recycling notice....169

German recycling notice....169

Greek recycling notice....170

Hungarian recycling notice....170

Italian recycling notice....170

Latvian recycling notice....170

Lithuanian recycling notice....171

Polish recycling notice....171

Portuguese recycling notice....171

Romanian recycling notice....171

Slovak recycling notice....172

Spanish recycling notice....172

Swedish recycling notice....172

Turkish recycling notice....172

Battery replacement notices....173

Dutch battery notice....173

French battery notice....173

German battery notice....174

Italian battery notice....174

Japanese battery notice....175

Spanish battery notice....175

Glossary....176

Index....177

1 HP X5000 G2 Network Storage System

The HP X5000 G2 Network Storage System ("storage system") is an integrated hardware-software solution that provides highly available file and block storage on a Windows failover cluster. E storage system features HP server blades and dense disk storage in a single 3U enclosure (Figure 1 (page 7)).

Features

The HP X5000 G2 Network Storage System provides the following advantages:

•Each system ships from the factory with preintegrated hardware and preloaded software, to significantly reduce the time and complexity of deploying clusters.
• Built on the HP converged application platform, which combines two server blades and dense storage drawer into a single enclosure
- Lower overall TCO with reduced footprint and lower energy consumption
- Specially developed setup tools (setup wizards) provide guided setup assistance, performing many of the complex and time-consuming tasks needed to configure and deploy a high availability storage system. The setup tools make it easy to get both Windows and a two-cluster configured and running quickly.
•HP and Microsoft management integration, including Microsoft Server Manager and System Center and HP System Insight Manager and Integrated Lights Out (iLO)

For more information about X5000 G2 Network Storage System features, go to:

http://www.hp.com/go/X5000-G2

Hardware components

Figure 1 (page 7) and Figure 2 (page 8) show front and rear views of the storage system.

Figure 1 Front view

1. Server blade 1, Bay 1

2. Server blade 2, Bay 21. Disk drawer

3. Server blade 2, OS drives2. Server blade 1, OS drives
4. Chassis fault LED

Figure 2 Rear view

1. System fan
2. HP 2-port 10 Gb I/O module (2). These modules connect to the NIC located on the server blade motherboard.
3. Intraconnect (internal switch connecting servers and EMU)
4. Drive fan
5. SAS I/O module (2)
6. Power button
7. Power supply (2)
8. HP 4-port, 1 Gb Ethernet I/O PCIe module (2)
9. HP 2-port, 1 Gb Ethernet I/O module (connects to the mezzanine NIC in each server blade)
10. Management port for iLO (servers 1 and 2), and Enclosure Manager Unit (EMU)

Software components

Windows Storage Server 2008 R2 SP1 comes preinstalled and activated on the HP X5000 G2 Network Storage System. The operating system software contains the Microsoft iSCSI Software Target and a Microsoft Cluster Service license. The storage system configuration also includes the HP Initial Configuration Tasks window and HP Server Manager, which are used to set up and manage your storage system.

The Initial Configuration Tasks window assists during the initial out of box setup by configuring the network, configuring two nodes from a single node, and deploying the cluster. Use HP Server Manager to further customize the storage system, such as managing volumes and spare drives.

To provide ongoing monitoring and facilitate management, the storage system includes the System Manager, which provides a snapshot view of the health and status of the storage system and too to manage firmware updates.

2 Installing the storage system

This chapter explains how to install the storage system hardware.

Verify the kit contents

Remove the contents, ensuring that you have all of the following components. If components are missing, contact HP technical support.

Hardware

•HP X5000 G2 Network Storage System

NOTE: External disk enclosures are not included with the storage system, but up to four D2600 or D2700 disk enclosures may be connected to the storage system.

• Rail kit

•Power cords

Media and documentation

•HP X5000 G2 Network Storage System Quick Start Guide
•HP ProLiant Essentials Integrated Lights-Out Advanced Pack
•End User License Agreement
•HP X5000 G2 System Recovery DVD
•Certificate of Authenticity Card
•Safety and Disposal Documentation CD

Locate and record the product number, serial number, and SAID number

Before you begin installation, locate and record the product number of the storage system, serial number, and support contract service agreement ID (SAID) number.

The product number of the storage system and serial number are located in three places:

•Top of the storage system
- Back of the storage system on a pull-out tab
• On the storage system shipping box

The SAID number is listed on your service contract agreement (see "Obtaining the Service Agreement ID" (page 54)).

Unpack and rack the storage system hardware

WARNING! The storage system enclosure is heavy. Always use at least two people to move t storage system into the rack.

1. If your storage system is delivered in a rack, proceed to Step 2. If you ordered the storage system without the rack, install the rail kit and enclosure in the rack using the installation instructions that are included with the rail kit.

IMPORTANT: Ensure that cabling in the back of the rack system does not interfere with system operation or maintenance. Bind cables loosely with cable ties and route the excess out of the way, along the side of the rack, to keep system components and indicators visible and accessible.

Figure 3 Storage system installed in a rack

1. Storage system enclosure
   2-5. Disk enclosures (optional)
   6-7. Cable connection, with no bend radius smaller than 5 cm

2. If you purchased disk enclosures, rack and cable the disk enclosures before moving to the next step.

3. Cable the storage system to your network and attach the power cords. See "Rear view" (page 8) for connecting the power cables.

Cable disk enclosures

The following figures show the correct cabling of disk enclosures to the storage system chassis. Numbers represent the order of attachment. Figure 4 (page 11) shows an HP X5000 G2 Network Storage System with two disk enclosures.

NOTE: Up to four HP D2600 or HP D2700 disk enclosures are supported. A mix of HP D2600 or HP D2700 disk enclosures is not supported.

Figure 4 X5000 G2 with two disk enclosures

1. X5000 G2
   2-3. Disk enclosures
2. SAS cable connecting disk enclosure 1 (green cable)
3. Green color code for upper SAS I/O module
4. Red color code for lower SAS I/O module
5. SAS cable connecting disk enclosure 2 (red cable)

Figure 5 (page 12) shows an X5000 G2 Network Storage System with four disk enclosures.

Figure 5 X5000 G2 with four disk enclosures

1. X5000 G2
   2-5. Disk enclosures
2. SAS cable connecting disk enclosure 1 (green cable)
3. Green color code for upper SAS I/O module
4. Red color code for lower SAS I/O module
5. SAS cable connecting disk enclosure 2 (red cable)

Network connections

Each of the two servers has eight network adapters. One of the adapters, Cluster Internal, is already connected to the corresponding adapter on the second node. This is done through an internal switch located in the Mezz B slot in the rear of the enclosure (5, Figure 6).

Figure 6 Network ports

1. 1 GbE Public 4 (Blade 1)1. 10 GbE Public 1 (Blade 1)
2. 1 GbE Public 3 (Blade 1)2. 10 GbE Public 1 (Blade 2)
3. 1 GbE Public 2 (Blade 1)3. 10 GbE Public 2 (Blade 1)
4. 1 GbE Public 1 (Blade 1)4. 10 GbE Public 2 (Blade 2)
5. 1 GbE Public 4 (Blade 2)5. Cluster Internal
6. 1 GbE Public 3 (Blade 2)6. Enclosure Manager, iLO (Bl
7. 1 GbE Public 2 (Blade 2)7. Server Management (Blade
8. 1 GbE Public 1 (Blade 2)8. Server Management (Blade

Because the two Cluster Internal adapters are connected, they are automatically assigned an IP link-local address from the address block 169.254.0.0/16. This network will be used in a late step for configuration of the second node from the first node, and it also is used as a private heartbeat network when the cluster is deployed. HP recommends that you do not make change to the configuration of the Cluster Internal network adapter.

The remaining network adapters are intended for use in your network infrastructure. Each adapter is labeled according to a suggested use (for example, 1 GbE Public 1), but you may rename adapters in later configuration steps and use them in a way best suited to your environment.

In the network infrastructure that connects the cluster nodes, avoid having single points of failure. One way to do this is to have at least two distinct networks. The HP X5000 G2 already pro one network between the nodes—the Cluster Internal network. You must add at least one more network. As you connect the HP X5000 G2 to your network infrastructure, consider the followi requirements:

• Since deploying the cluster requires that both servers be joined to an Active Directory domain, you must have a route to the domain controller from each server on the storage system.
• Servers in a cluster must use DNS for name resolution, so you must have a route to a DNS server from each server on the storage system.
• If you are adding more than one adapter per server to your network infrastructure, each adapter should be on a different subnet.

Figure 7 (page 14) shows two possibilities for adding network cables for an additional network

Figure 7 Cabling an additional network

1. Connect 10 GbE Public 1 (Blade 1) and 10 GbE Public 2 (Blade 2) to the same subnet in your network infrastructure. Note that adapters were chosen on different pass-through modules. This prevents the pass-through module from becoming a single point of failure for the connection between the two nodes.

or

1. Connect 1 GbE Public 4 (Blade 1) and 1 GbE Public 4 (Blade 2) to the same subnet in your network infrastructure.

In later configuration steps you can configure the adapters you have connected to your network. If you have connected to a DHCP-enabled network, no further configuration is necessary. Otherwise you must assign static addresses to the adapters. You may also want to rename the adapters to reflect their use in your environment. Also note that these are only two examples out of many networking possibilities. NIC teaming may also be used. It is not necessary to make all these decisions now, because you can always add more networks after the system has been deployed.

The Enclosure Manager and iLO port (6, Figure 6 (page 13)) provides for a connection from your network infrastructure to the Enclosure Manager Unit (EMU) and to the iLO on each blade. For ease of setup, the EMU and each iLO processor have been assigned static IP addresses in the factory. You use these addresses to make an initial connection, and then configure each to connet to your network. The factory configured addresses are as follows:

Table 1 Factory configured EMU and iLO addresses

		Subnet maskIP addressComponent
		255.255.255.010.0.0.10EMU
	Server 1 iLO	255.255.255.010.0.0.11
	Server 2 iLO	255.255.255.010.0.0.12

"Configure the EMU and iLO management processors" (page 15) describes how you can directly connect a laptop or other local system to reconfigure these addresses.

Power on the storage system

1. Power on disk enclosures, if any.
2. Power on the storage system by pushing the power button on the back of the chassis.
   Once the storage system power is on, power on the server blades if they do not automatically power on.

Configure the EMU and iLO management processors

Before configuring the management processors, verify the following:

- You have determined whether the network ports on the server are to use DHCP or static addresses. If the network ports are to use static addresses, you must provide the addresses:

- For this step, the EMU port should not be connected to a switch. You can connect the EMU port to a switch after the EMU and iLO NICs are configured.

Configure the EMU and iLO management processors for both servers as follows:

1. Connect a system (the configuration system) in the environment or a laptop to the EMU point (Figure 8 (page 15)). You can use either a crossover or a regular Ethernet cable.

Figure 8 EMU NIC port connection

1. Configure the networking properties for the local system:

a. Open Control Panel, select Network Sharing Center or Network Connections, and navigate to Local Area Connections.
b. Select Properties→Internet Protocol, and then select Properties.
c. If Use the following IP address: is selected, record values for the following items and restore them after completing the EMU and iLO setup:

•IP address
- Subnet mask
- Default gateway

d. Enter the following values:

•IP address: 10.0.0.20
- Subnet mask: 255.255.255.0

e. Before continuing, ping the following IP addresses to test connectivity to the EMU and the iLO located in each of the servers: 10.0.0.10, 10.0.0.11, and 10.0.0.12. The EM and iLO interfaces have been assigned IP addresses during factory setup. You must either update the factory values with site-specific static IP addresses or configure the management processors to use DHCP IP addressing.

1. Configure iLO on the server blades:

a. Open a web browser and log in to iLO using the address: http://10.0.0.11. You are prompted to enter the user name and password. The password for the Administrator account is located on a pull out tag on the front of the server blade. After you have logged into iLO, HP recommends that you change the administrator password. To do so, select User Administration under Administration in the iLO management interface.

b. Configure the network as required for your environment. Select Network under Administration in the iLO management interface. You can either enable DHCP or edit the IP address details and enter site-specific network settings. Click Apply to save your settings.

c. Repeat the process on the other server blade. Open a web browser and log in to iLO using the address: http://10.0.0.12.

4. Configure the EMU:

a. Connect to the Enclosure Manager software using an ssh compatible tool like PuTTY. In the PuTTY session basic options, enter the EMU IP address (10.0.0.10) and port (22), and select SSH for the connection type (Figure 9 (page 17)).

NOTE: See "Managing the EMU" (page 131) for information on using CLI commands.

Figure 9 Connecting to the Enclosure Manager software

b. After you have connected to the EMU port, set the following attributes:

• EMU (DNS) name
- Rack name
- EMU password (located on the tear-away label on the back of the server blade; see Figure 10 (page 17))
• IP addressing method

To change the static IP address, type the command set ipconfig static at the command line prompt and follow the instructions.

To change the EMU addressing to DHCP, type set ipconfig dhcp at the command line prompt.

Figure 10 Tear-away label location

Example 1 Setting attributes

CustomerEMU-dnsName> set em name CustomerEMU-dnsName

CSP Enclosure Manager name changed to CustomerEMU-dnsName.

CustomerEMU-dnsName> set rack name CustomerRackName

Changed rack name to "CustomerRackName".

CustomerEMU-dnsName> set password
New Password: *****
Confirm : *****
Changed password for the "Administrator" user account.
CustomerEMU-dnsName> 

NOTE: You will not be able to connect to iLO or the EMU from the configuration system until you change the network settings on the configuration system.

1. Complete the configuration:

a. Connect the EMU port to the appropriate switch/VLAN/subnet.
b. Log in to the EMU using ssh and the newly assigned EMU name and validate connectivity. It is assumed that the EMU name is in the DNS.

Example 2 Verifying connectivity

CustomerEMU-dnsName> show server list all
Bay	iLO Name	iLO IP Address	Status	Power	UID
1	ILOMXQ0110FJ9	16.78.90.51	OK	On	Off
2	ILOMXQ0110FHU	16.78.90.113	OK	On	Off
Totals: 2 server blades installed, 2 powered on.

3 Configuring the storage system

This chapter explains the out of box experience that occurs when you first power on the storage system. This includes setup tasks, such as the selection of language and regional settings for the OS, network configuration, time zone, provisioning storage required for the cluster, and deploy the two-node cluster. All configuration may be done from a single server. There is no need to on to the second server.

Accessing the storage system

For initial configuration of the storage system, you must have console access to one of the server blades. You can use either a local I/O diagnostic (SUV) cable or an iLO connection. The iLO connection is the preferred method because it allows for remote access. If you are using the c connect method, connect the supplied SUV cable to the front of the storage system server blade in the following sequence: keyboard, mouse, monitor cable, and monitor power cable. Regardless of which access method you use, perform the configuration from only one of the server blades. The server blade you choose for configuration will be designated the first node, and the other server blade will be designated the second node.

Figure 11 Keyboard, mouse, and monitor

1. Storage system enclosure
2. Monitor
3. Keyboard (USB)
4. Mouse (USB)

NOTE: The keyboard, mouse, and monitor are not provided with the storage system.

For remote access, open a web browser and enter the iLO name or IP address for a server I located in either bay. Log in using the iLO administrator name and newly created password fo that blade.

For instructions on using iLO, see the Integrated Lights Out user guide available from http://www.hp.com/go/ilo. On the iLO web page, select More iLO Documentation.

Set up Windows and discover the second node

When the storage system starts, the servers will begin a first time setup procedure that takes approximately 10 to 15 minutes, including the Set Up Windows wizard. Use only one node to complete the setup procedure.

In the Set Up Windows wizard, you are asked to choose a language, regional settings, and keyboard layout. After you accept the EULA, the server you are connected to attempts to discover the second server. This is done over the internal switch (5, Figure 6 (page 13)). If the second node is not ready, you may see a message stating Cannot establish communication with the second node. Click Retry to attempt discovery, and repeat the retry until the second node is discovered. After the second node is discovered, there will be a few more installation steps that occur automatically on each server, and then both servers will reboot.

NOTE: If you click Cancel instead of Retry, you must access the second node from iLO or a direct (SUV) connection and manually perform the Set Up Windows wizard on the second node. Because the discovery process has not completed, there will also be an extra step later to establish a connection between the two nodes. You will find instructions for this, if needed, in the online help of the Initial Configuration Tasks (ICT).

Completing initial configuration

After the servers reboot, continue the configuration using the first node. A default administrator password (HPinvent!) has been set and this is used to log on automatically. Leave this administrator password unchanged until you are prompted for a new password in a later configuration step. After logon, the HP ICT window is launched automatically.

Figure 12 ICT window

Use the HP ICT to perform setup tasks in the order they appear. See the provided online help for each group of tasks for more information about the task. After completing the "Provide cluster name and domain" task, both nodes will reboot. After allowing time for a reboot, log on once again to the first node. This time, rather than logging on as local Administrator, log on using the domain account that was specified in the "Provide cluster name and domain" task. You may now complet the remaining tasks, which includes creation of the two-node cluster. The final task is an optional

step to deploy one or more file servers on the cluster. You may also wait and create file server later using Server Manager.

The ICT is intended for initial setup, so once it is complete, you may select the Do not show this window at the next logon box. If you do want to launch the ICT at a later time, you mo from Server Manager or by typing oobe from a Windows command prompt.

When the HP ICT window is closed, Server Manager is launched automatically. Use Server Manager for further customization of the storage system, such as adding roles and features, and share a storage management. See the Getting Started node in the navigation tree of Server Manager for more help on using the storage system.

NOTE: Although BitLocker is supported by the Windows operating system, it is not supported on the X5000 G2 Network Storage System because BitLocker is not supported on clustered volume. For more information, see the following Microsoft article:

http://support.microsoft.com/kb/947302

If encryption is required, the Encrypting File System (EFS) is supported on clustered volumes. For more information on EFS, see the following Microsoft article:

http://support.microsoft.com/kb/223316

Networking options

The large number of network adapters on each server in the X5000 G2 provides a number of different options for networking. The network adapter named "Cluster Internal" is pre-configured as a private cluster heartbeat and should be left as is, but all other adapters are available for Use the guidelines below as an aid in making configuration choices.

Network teaming

Network teaming is a common use of multiple network adapters. Teaming is used to increase available network bandwidth and provide fault tolerance. Teaming can be across multiple ports in the same network adapter or across network adapters.

Multi-home

Distributing network workload across multiple network adapters is also commonly used. Placing each network interface on a different subnet allows the workload on each subnet to be service in parallel rather than through a single interface.

Dedicated networks

Implementing a unified storage solution requires that different protocols be used to access a state system. In one instance, a block protocol like iSCSI is used to present storage to a virtual master host. At the same time, a file protocol like SMB is used for sharing files for department or user home directories. A dedicated storage network for each protocol allows the network traffic to keep separate to maximize performance. Similarly, one network interface can be used for system management and monitoring while another interface can be used for data traffic.

10 GbE versus 1 GbE

Other than the obvious difference in speed, 10 GbE provides an order of magnitude difference in lower latency. Lower latency is ideal for transactional database applications and virtualization. Combining a 10 GbE dedicated storage network for a virtual machine infrastructure, and a 1 network for shared folder, takes the most advantage of the network offerings. A classic example is thin clients whose resources are hosted on virtual machines (for example, the Citrix model).

4 Monitoring and troubleshooting the storage system

The storage system provides several monitoring and troubleshooting options. You can access the following troubleshooting alerts and solutions to maintain the system health:

• Notification alerts
  •System Management Homepage (SMH)
  •System Manager

• Hardware component LEDs

• EMU CLI SHOW commands

•HP and Microsoft support websites

•HP Insight Remote Support software

• Microsoft Systems Center Operations Manager (SCOM) and Microsoft websites

- HP SIM 6.3 or later, which is required for proper storage system/HP SIM integration.

NOTE: Integration with HP SIM is only supported using the WBEM/WMI interfaces. Do not attempt to configure HP SIM to use the ProLiant SNMP agents, because the configuration is untested and unsupported. The ProLiant SNMP agents are enabled on the storage system by default and should not be disabled as they are used for internal management functions. If the are enabled for external client consumption, HP SIM must be configured so it does not attempt to communicate with these agents.

NOTE: WBEM events for storage are logged into Windows Application logs and WBEM events for Server and Enclosure are logged into Windows System logs.

If you are unable to resolve a storage system operation issue after using the various options, cont HP Support. You must provide your SAID and your warranty and entitlement labels. See "Obtaining the Service Agreement ID" (page 54) and "Locating the storage system warranty entitlement label" (page 54).

Using notification alerts

When you receive an alert, open the System Manager (described in "Using the System Manager" (page 30)) to view a high-level description of the issue. You may then choose to open the System Management Homepage or HP SIM to obtain more detailed information.

IMPORTANT: While the notification alerts report issues as they arise, it is still important to monitor the storage system regularly to ensure optimal operation.

Configuring Alerts and Email

Configure Alerts and Email in the System Manager to send email notification of system events.

IMPORTANT: HP recommends that you configure Alerts and Email (and also install HP Insight Remote Support) to ensure that you are proactively alerted to issues. Proactive notification enables you to address issues before they become serious problems.

To create an alert for a recipient:

1. Open the Server Manager by clicking the icon located to the right of the Start button on the Windows taskbar.
2. Expand the tree under System Manager.
3. In the tree, select Alerts and Email.

Figure 13 Configuring Alerts and Email

1. Do one of the following:

2. Select New to create a profile.

3. Select Copy or Edit to modify an existing profile.

The Alert Settings window appears.

Figure 14 Alert and Email settings

1. Complete the following fields:

- Name—Enter the name of a recipient (for example, John Doe).

- Recipient address—Enter the email address of the recipient (for example, [e-mail]).

- From address—Enter an email address that will display to the recipient indicating where the message originated. It can be the same as the recipient address, if desired.

- SMTP address—Enter a valid SMTP address (for example, SMTP.company.com).

- Alerts Severity—Select the severity for which you want to receive alerts. You will also receive alerts for any severity higher than the one you select. Select All to receive alerts for all severities.

- Components Alerts—Select the components for which you want to receive alerts, or select All to receive alerts for all components.

1. To test the ability for the recipient to receive email alerts, click Send Test Email. If the recipient receives the test email, no further action is required. If the test email is not received, check that the information entered for the recipient is correct.

Figure 15 Send test email

1. Click Save. The name of the recipient is displayed on the main Alerts and Email window.

To configure the SNMP settings:

1. In the Server Manager navigation pane, select System and Network Settings.
2. Select SNMP Settings in the lower-right pane.
3. Provide the contact and location information for the System Administrator, and then click OK.
4. To make SNMP visible externally:

a. Select Start→Administrative Tools→Services.
b. Select SNMP Service.
c. Right-click and select Properties to display the SNMP Service properties.
d. Select the Security tab and specify the following items:

•The external hosts that may use the SNMP protocol.

- The SNMP Community string. HP recommends that you use something other than the typical 'Public' string.

IMPORTANT: Configure HP SIM security to prevent the SIM management server from gaining access to SNMP.

The SNMP trap function in the storage system is enabled by default. Any SNMP client (on localhost) listening on default port number 171 can receive traps. You can configure the destination IP address using the snmp.xml configuration file in the directory \Program Files\HPWBEM\Tools\snmp.xml.

HP System Management Homepage

The HP System Management Homepage (SMH) is a web-based interface that consolidates and simplifies single system management for HP servers. The SMH is the primary tool for identifying and troubleshooting hardware issues in the storage system. You may choose this option to diagnose a suspected hardware problem. Go to the SMH main page and open the Overall System Health Status and the Component Status Summary sections to review the status of the storage system hardware.

By aggregating the data from HP web-based agents and management utilities, the SMH provides a common, easy-to-use interface for displaying the following information:

• Hardware fault and status monitoring
• System thresholds
• Diagnostics
- Software and firmware version control for an individual server
•HP Storage 1210m firmware information

The SMH Help menu provides documentation for using, maintaining, and troubleshooting the application. For more information about the SMH software, go to www.hp.com/support/manuals and enter System Management Homepage in the Search box. Select HP System Management Homepage Software. A list of documents and advisories is displayed. To view SMH user guides, select User Guide.

Starting the System Management Homepage application

To start the application, double-click the HP System Management Homepage desktop shortcut or enter https://hostname:2381/ in Internet Explorer. The hostname can be localhost or the IP address of the server you want to monitor. To log into SMH, enter the same username and password you use to log in to the server. Users who have administrative privileges on the server have the same privileges in the SMH application.

To view the SMH of one server from another server, you must modify the Windows firewall setting as follows:

1. Open the Control Panel and select System Security→Windows Firewall→Allowed Programs.
2. Select Allow another program and click Browse in the Add a Program dialog box.
3. Navigate to C:\hp\hpsmh\bin and select hpsmhd. Click Open and then click Add. HP System Management Homepage displays in the Allowed Programs and Features window.
4. Select Home/work (Private) and Public and click OK.
5. To access the SMH on another server, enter the following URL: https://:2381

System Management Homepage main page

Figure 16 (page 27) shows the SMH main page.

Figure 16 System Management Homepage main page

The page provides system, subsystem, and status views of the server and displays groupings of systems and their status.

NOTE:

- NICs will display with a failed status (red icon) if they are unplugged. To remove unused NICs from the system status, you can disable them by selecting Control Panel→Hardware→Device Manager, right-click on the specific NIC, and then select Disable.

- When you remove a disk or disconnect a cable, the SMH interface might not display alerts when you click the Refresh button. You can force a hard refresh by clicking the Home button or by navigating to the problem area. The default refresh interval is two minutes. To chan the interval in the Settings menu, select Autorefresh, and then Configure Page refresh settings. The minimum interval is five seconds and the maximum is 30 minutes.

Overall System Health Status

A webapp sets the value of the Overall System Health Status icon by using a predefined heuristic. If no webapp can determine the status, the worst possible status is displayed in the Component Status Summary section.

Component Status summary

The Component Status Summary section displays links to all subsystems that have a critical, major, minor, or warning status. If there are no critical, major, minor or warning items, the Component Status Summary section displays no items.

Enclosure

This section provides information about the enclosure cooling, IDs, power, Unit Identification LED PCIe devices, and I/O modules.

NOTE: A large number of disk errors may indicate that an I/O module has failed. Inspect the I/O module LEDs on the storage system and any disk enclosures, and replace any failed comp

- Because both a system and drive fan are required, the maximum and minimum number of fans required is two. If either fan becomes degraded, the system could shut down quickly. Because the fans are not mutually redundant, even if the status of a single fan has changed

the new status is reported immediately in the Components Status Summary section on the S main page.

- When the Enclosure Manager IP address is set incorrectly, the enclosure status displayed is Lost communication. Because the Enclosure Manager has lost communication with the external network, none of the other items in the Enclosure Information section can be displayed.

The enclosure I/O ports are numbered from 1 to 8 in the SMH.

Figure 17 I/O module

These numbers correspond to the I/O modules in the enclosure bays.

Figure 18 I/O module bays

1. PCIe module1. LOM module
2. PCIe module2. LOM module
3. SAS I/O module3. MEZZ module
4. SAS I/O module4. Intraconnect (internal switch)

Network

This section shows the status of the network connections.

Storage

This section displays information about the following components:

• Storage System—Links to the page that displays information about storage in the drive drawer and any external disk enclosures. This storage is managed by the 1210m controller.
• Smart array subsystem—Links to the page that displays information about operating system drives and smart array controllers.

NOTE: The SMH will display a total of four power supplies for each External Storage Enclosure. If there is more than one External Storage Enclosure connected, the SMH may not show the c number of power supplies for each of these enclosures.

The Storage System page is organized as a left panel and a main page:

Figure 19 Storage system

The left panel provides links to information about the following items:

- Controller

Select a storage controller to view its type, status, firmware version, and serial number.

•Logical Drives

A list of logical drives associated with the controller appears in the left panel tree view. S one of the logical drive entries to display the status of the drive, fault tolerance (RAID level and capacity (volume size). A link to the logical drive storage pool is also displayed.

•Storage Pools

A list of storage pools associated with the controller displays in the left panel tree view. S one of the pool entries to display its status, capacity, communication status with the control primordial state, and cache properties.

NOTE: If read or write cache is enabled the value displayed is 2; otherwise, the value is 3.

The Storage Pools page also displays a list of disk drives and storage volumes present in the pool.

Under the Physical Drives tree, the list of disk enclosures is displayed. Under each enclosure the list of disk drives present in each disk enclosures is displayed. When there is no drive

the enclosure, the display shows Bay Baynumber- Empty. Select one of the disk enclosures or disk drives to see information for that enclosure or drive.

•Physical Drives

This section provides an overview of all disk drives attached to the controller. Drives are identified and grouped as assigned, unassigned, and spare drives. Each physical drive is listed as a separate entry in the Storage System submenu. Select any of the physical drives to display more information about the drive.

NOTE: Spare drives are only used when a disk drive fails. Until a spare drive is used, it remains offline and its LEDs will remain off.

System

This section displays status for various system components.

Version Control

This section provides information about the Version Control Agent.

Software

This section provides information about system firmware and software.

Using the System Manager

The System Manager provides the status of each server blade that is configured in the storage system. Be sure to note the server blade that is being assessed when you open the System Mana Log in to each server blade to evaluate its status.

To use the System Manager, which has been preinstalled and configured, use Remote Desktop or

iLO to access the server blade. Click the Server Manager icon located in the taskbar to the right of the Start button or select Start→Administrative Tools→Server Manager. When Server Manager appears, select System Manger in the left navigation pane.

To troubleshoot using the System Manager:

1. Open the System Manager.
2. Open the System Summary tab to review the overall health of the storage system hardware, and firmware.
   If the status icon is green, the system is running properly. A yellow icon is a warning that the are conditions that might cause a problem. If the icon is red, a problem exists in the storage system.
3. Open each tab in the System Manager to assess the status of the storage system.
4. Follow the instructions provided on the System Manager tabs for any reported issue.

System Summary

The System Summary tab displays information such as the enclosure name, IP Address, firmware revision, and serial number. The lower part of the System Summary also shows the status of hardware, and whether your current firmware revision is up to date. If a green check mark does not appear beside the configuration status, go to the related tab for information about the issue.

Figure 20 System summary

Hardware Status

The Hardware Status tab provides the health status for each storage system component. The Sy section displays information for the server blade that you are logged in to. If a problem is re in the System section, you should check the Hardware Status tab on each server blade.

NOTE: If the System Manager shows that a LUN has an error, open the System Management Homepage and determine whether the LUN is degraded due to a disk failure. If so, also use System Management Homepage to determine which disk needs to be replaced.

Figure 21 Hardware status

Firmware

The Firmware tab indicates whether the firmware of a component is outdated. If the specific firmware requires that you reboot after installing the update, a message instructing you to reboot the storage system appears. Since the tool does not connect to the Internet to identify new firmware, you must periodically check the HP support web page and download new firmware when available. Be sure to check the Firmware tab on each server blade. Some firmware updates must be made on both server blades.

IMPORTANT: If a firmware update requires a reboot, you must reboot your storage system manually. For more information about firmware updates, see "Upgrading a component's firmware" (page 56).

Figure 22 Firmware

Reports

The Reports tab gathers logs for the hardware, software, Microsoft Windows system configuration and the Microsoft Exchange diagnostics in one place. These logs are used by HP support eng to help diagnose your system, if needed; you do not need to view and interpret the logs you To generate reports:

1. Consult with HP support to determine what type of report is required.

- If complete reports are required, go to step 2.

- If an abbreviated report can be used, select the Run Quick Report Only option. A quick report contains less information but is created in much less time. It may contain all the necessary information HP support needs.

1. Click Generate Support File. A license agreement window is displayed.
2. Select Yes to accept the license.

The report generation process begins. It may take up to 45 minutes to create the reports. When the process is complete, the lower portion of the screen indicates that HP System R have been generated.

1. Click Open Reports Folder to access the .cab file containing the report results.

This file is ready to forward to the HP support engineers.

Figure 23 Reports

Component LEDs

LEDs indicate the status of hardware components. This section provides images of the component LED locations and describes the status of LED behaviors. To obtain additional information on some status indicators, you can use the EMU CLI SHOW commands described in "Managing the EMU" (page 131).

Figure 24 Server blade LEDs

Table 2 Server blade LEDs status

		StatusDescriptionItem
		Blue = Needs service checkUID LED1Blue flashing = remote management (remote console in use via iLO)OFF = No remote management
		Green = NormalHealth LED2Flashing = Booting
		Amber = Degraded conditionRed = Critical condition
		Green = Network linkedNIC 1 LED*3Green flashing = Network activityOFF = No link or activity
		Green = Network linkedFlex-10 NIC 2 LED*4Green flashing = Network activityOFF = No link or activity
		—Reserved5
		Green = OnSystem power LED6Amber = Standby (auxiliary power available)OFF = OFF
*Actual NIC numbers depend on several factors, including the operating system installed on the server black

Figure 25 Front LED display board

Table 3 Front LED status

		StatusDescriptionItem
1	Hard drive LEDsNormal mode (UID LED is solid)Hard drive LEDs1Drive locate mode (UID LED flashing)	Green = The drive is online, but is not currently active.Flashing irregularly green = The drive is online and it is operating normally.Flashing green (1 Hz) = Do not remove the drive. Removing the drive may terminate the current operation and cause data loss. The drive is rebuilding, or it is part of an array that is undergoing expansion, logical drive extension, a stripe size migration, or RAID migration.Flashing amber/green = Drive is configured and indicating a predictive failure. The drive may also be undergoing a rebuild, expansion, extension, or migration.Flashing amber (1 Hz) = A predictive failure alert has been received for this drive. Replace the drive as soon as possible.Amber = Drive failure, link failure, or mismatched configuration.OFF = The drive is offline, a spare, or not configured as part of an array.Green = The drive has been selected by a management application and it is operating normally.Flashing amber (1 Hz) = The drive is not selected and is indicating a predictive failure.Flashing amber/green = The drive has been selected by a management application and is indicating a predictive failure.Amber = The drive might or might not be selected and is indicating drive failure, link failure, or mismatched configuration.OFF = The drive is not selected.
	Chassis fault LED2	Flashing amber if there is a failed component in the system.NOTE: The amber chassis fault LED flashes if any component fault is detected by the System Management Homepage. A fault can be as minor as a cable unplugged from a NIC port, and therefore may not be cause for concern.OFF if the system is in good health.
		Solid green if the system is in good health.Chassis health LED3OFF if there is a failed component in the system.
	Chassis UID LED4	This is either blue or off. When on it can be steady or blinking. Used only for unit identification. To set the LED, use the following CLI command: SET ENCLOSURE UID { ON | OFF | SLOW | FAST }OFF = Enclosure is functioning normally.

NOTE: All these LEDs are off if the enclosure has power but is turned off (see Table 11 (page 40)). Then only the equivalent Chassis LEDs (2,3,4) on the rear Power Pod show status.

Figure 26 Hard drive LEDs

1. Fault/UID LED (amber/blue)
2. Online LED (green)

Table 4 SAS hard drive LED combinations

Item	Description	Status
1	Activity/Online LED	OFF = Override drive activity output. Drive is not a member of any RAID volumesDrive is configured but in a replacement or failed state for at least one volume that is a member of a RAID volumeDrive is a spare drive that is or has been activated but has not been rebuilt.Drive is not rebuildingDrive is not a member of a volume undergoing capacity expansion or RAID migration.Solid green = Drive is a member of a RAID volumeDrive is not a spare driveDrive is not in a replacement or failed state for any volume that is a member of a RAID volumeDrive is not currently performing I/O activity.StatusDescriptionItem
		Blinking green (@ 4 Hz 50% of duty cycle) = Drive is currently performin I/O activityDrive is a member of a RAID volumeDrive is not in a replacement or failed state for any volumes that is a member of a RAID volume (drive is online)Drive is not rebuildingDrive is not a member of a volume undergoing capacity expansion or RAID migration.
		Blinking green (@1 Hz 50% duty cycle - override drive activity output) = Drive rebuildingmember of volume undergoing Capacity Expansion/RAID Migration.
2	- Bicolor amber/blue	OFF = Drive is not failedDrive is not selected (unit identification).f
		Solid blue = Drive is not failedDrive is selected (unit identification).
		Solid amber = Drive is failedDrive is not selected.
		Blinking amber (@ 1Hz 50% duty cycle) = Drive is in a predictive failure stateDrive is not failedDrive is not selected.
		Blinking alternate amber/blue (@ 1Hz 50% duty cycle) = Drive FailedDrive is in a predictive failure stateDrive is selected.

NOTE: Spare drives are only used when a disk drive fails. Until a spare drive is used, it remains offline and its LEDs will remain off.

Figure 27 1210m Cache module controller LEDs

Table 5 1210m Cache module controller LED status

		StatusDescriptionItem
Amber LED lower right		Green off, amber on = A bGain isED in upprogress of Controller LEDs
		Green flashing (1 Hz), amber on = A restore is in progress.
		Green flashing (1 Hz), amber off = The capacitor pack is charging.
		Green on, amber off = The capacitor pack has completed charging.
		Green flashing (2 Hz) alternating with amber; amber flashing (2 Hz) alternating with green LED = One of the following condition exists:- The charging process has timed out.- The capacitor pack is not connected.Green on, amber on = The flash code image failed to load.
		Green off, amber off = The flash code is corrupt.

Figure 28 Enclosure Manager unit LEDs

Table 6 Enclosure manager unit LEDs status

		StatusDescriptionItem
	EM display1	The LED blinks during power-up, but then the display changes only in response to commands from the Enclosure Manager Display.
	EM fault LED2	Amber flashing/green LED off = issue. Use the CLI commands SHOW ENCLOSURE STATUS and SHOW SYSLOG EM to determine possible fault causes.
	EM health LED3	The health LED is only green and is either on (Healthy) or off (Power off or Faulted).
LEDs are off when the enclosure is powered off.

Figure 29 HP 2-port 1 GB Ethernet I/O modules LEDs

Table 7 HP 2-port 1 GB Ethernet I/O modules LEDs status

		StatusDescriptionItem
		Solid green when module health is goodModule health OFF* when module has failed
		Solid amber when module2 has failedModule fault LED OFF* when module health is good
*LEDs are off when enclosure is powered off.

Figure 30 HP 2-port 1 GB Ethernet, Mezz A and B I/O modules LEDs

Table 8 HP 2-port 1 GB Ethernet, Mezz A and B I/O modules LEDs status

		StatusDescriptionItem
		Solid green when module health is goodModule healthOFF* when module has failed
		Solid amber when module has failedModule fault LED2OFF* when module health is good
*LEDs are off when enclosure is powered off.

Figure 31 HP 1 GB intraconnect module LEDs

Table 9 HP 1 GB intraconnect module LEDs status

		StatusDescriptionItem
		Solid green when module health is goodModule healthOFF* when module has failed
		Solid amber when module has failedModule fault LED2OFF* when module health is good
*LEDs are off when enclosure is powered off.

Figure 32 Power supply LEDs

Table 10 Power supply LED status

		StatusDescriptionItem
		Green = Power on and power supply functioning properly.Power supplyOFF = One or more of the following conditions exists:System powered off, AC power unavailable, Power supplyfailed, Power supply exceeded current limit. Use the CLI command SHOW ENCLOSURE POWERSUPLY STATUSALL for more details.

Figure 33 Chassis switches and indicator LEDs

Table 11 Chassis switches and indicator LEDs status

		StatusDescriptionItem
		Solid blue = Requires service check.UID1
		Solid green when system health is good.Chassis health2OFF if a module or component in the system has failed
3	Chassis fault	Flashing amber if a module or component in the system has failed.NOTE:The amber chassis fault LED flashes if any component fault is detected by the System Management Homepage. A fault can be as minor as a cable unplugged from a NIC port, and therefore may not be cause for concern.OFF if system health is good.
		Green when enclosure power is ON.Power button/LED4Amber when enclosure has AC power but is turned off.

Figure 34 SAS I/O modules LEDs

Table 12 SAS I/O module LEDs status

		StatusDescriptionItem
		Green* = HealthySAS Port 11, 2Amber = Issue
		Green* = HealthySAS Port 23, 4Amber = Issue
		Green = HealthyOverall I/O module status5, 6Amber = Issue
		Green* = HealthySAS Port 37, 8Amber = Issue
		Green* = HealthySAS Port 49, 10Amber = Issue
*If there is anything connected to a connector, the corresponding green LED is on and blinks off with activity. If there is nothing connected to a connector, both LEDs are off.

Figure 35 Fan LEDs

The two fan modules are physically identical, but their control is not. The Fault/health LED on FAI 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 EMU 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 fa 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 EMU cannot indicate Fan status in standby mode.

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 code 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 I/O Module. This LED cannot be lit unless enclosure power is on, and its state depends upon signals from one of the SAS I/O modules.

To troubleshoot a degraded fan, you can use the EMU CLI commands SHOW ENCLOSURE STATUS and SHOW ENCLOSURE FAN ALL described in "Managing the EMU" (page 131).

EMU CLI SHOW commands

Use the EMU CLI SHOW commands described in "Managing the EMU" (page 131) to obtain additional information about component status as indicated by the hardware LEDs described in "Component LEDs" (page 34). 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-away 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.

The following is a sample login session:

login as: Administrator

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 monitored and can result in criminal or civil prosecution under applicable law.

User: /src/bin/build@msaonyx Script: ./parbuild Directory: /src/quire/QUIRE-CSP-1-20/daily/2011102701/bld/QUIRE-CSP-1-20 FileTag: 102720111904 Date: 2011-10-27T19:04:57 Firmware Output: jsbach Firmware Version: 0x0120 SVN Version: 3414

Administrator@10.0.0.10's password:

HP CSP System Enclosure Manager

(C) Copyright 2006-2010 Hewlett-Packard Development Company, L.P.

Type 'HELP' to display a list of valid commands.

Type 'HELP' to display detailed information about a specific command.

Type 'HELP HELP' to display more detailed information about the help system.

EM-78E7D1C140F2>

After logging in, you can set the Administrator password using the Enclosure Manager Settings window. Go to the C:\Program Files\HP\HP Configuration Wizard directory and double-click HPEMConfig.exe.

Known issues

Table 13 identifies known issues with the storage system and provides workarounds to mitigate them.

Table 13 Known issues

	ResolutionIssue
HP System Insight Manager is not able to retrieve the OS and product name of the network storage system.	This occurs if the domain user or group does not have the proper security address to the WMI namespace. Access to the WMI namespace is not given by default. To permit access:Select Server Manager+Configuration.Right-click WMI Control and select Properties.On the Security tab, select Root and the HPQ namespace.Click Security, and give permission to the user or group.Restart WMI.
The cluster IP address on a cluster network resource cannot resolve the DNS service has not been set up to allow for updates from external clients. name or update the DNS name correctly fix this issue: causing the network resource to appear offline or with a warning message.	This occurs when a previous identifier is listed in the DNS entries and the DNS server has not been set up to allow for updates from external clients.Log in to the Active Directory Domain Services with your Domain Administrator, or Security Group access.Go to the DNS server, select the computer name, and then click Forward Lookup Tables.Select the domain to add the file server.Locate the DNS entries for the file server name. You can either update the information manually by double-clicking on the entry and entering the correct file server information, or by deleting the existing DNS entry.NOTE:Entering the correct file server information or deleting the DNS entry requires that you manually enable the network resource on the cluster. You can do this by manually right-clicking on the network resource on the file server and selecting theBring this resource onlineoption. When deleting the DNS entry, this option creates and updates a new DNS entry on the DNS server.
After joining a domain, the "Microsoft iSCSI Software Target" service may form with the error message: Windows could not start the Microsoft	During startup of the Microsoft iSCSI Software Target service, WinTarget makes a synchronous call to the Active Directory. If the Active Directory serve does not respond in a timely manner, the service fails to start after 30 seconds. To resolve this issue, type the following on the command line: reg add HKLM\System\CurrentControlSet\Control /vServicesPipeTimeout /t REG_DWORD /d 60000 /f shutdown /r /t 0
iSCSI Software Target service on MACHINE_NAME. Error 1053: The service did not respond to the start or control request in a timely manner.	The use of this registry key is documented at http://support.microsoft.com/kb/824344.
The Enclosure UID page that is part the HP System Management Homepage cannot be used to enable or disable UID status LED.	The UID LED cannot be enabled or disabled in the System Management Home page until the Enclosure Manager key has been generated. The Enclosure Manager key can be generated using the System Manager snap-in.
There is difficulty in setting up a storage system with clustering with insufficient administrative privileges.	When selectingProvide cluster name and domainin the ICT you need:An Active Directory domain where both nodes will be joined as member servers.A domain user account that has Create Computer Objects and Read All Properties permissions.
Length of network storage system reboot time	The reboot time for the network storage system is approximately six to seven minutes.
(from cluster net or cluster netint command or Failover Cluster Manager) as “network partitioned” when a cluster node is rebooted and rejoins the cluster. The network interface is still usable for communications to other nodes; it is only the communications between the cluster nodes that is affected. The cluster interface status will change after 12–24 hours. This issue is intermittent and takes approximately 30–50 reboots of a node to reproduce.	This issue can be resolved by doing one of the following:A cluster network interfAllow 12–24 hours to pass for the Microsoft Failover Cluster Manager to resolve the issue automatically.Manually restart the node that was restarted or affected.Manually disable or enable the NIC on the affected cluster node that is causing the issue, under Network Connections.
File Server Resource Manager (FSRM) displays the error message: File Server Resource Manager global configuration cannot be accessed since it is not installed yet.	FSRM only configures its config store in the cluster database when the FSRM service starts. To resolve this issue, reboot one node in the cluster, or you can start/stop the FSMR services by issuing the following commands on the command line using elevated privileges:net stop srmsvcnet stop srmreportsnet start srmreportsnet start srmsvcThis issue is documented by Microsoft at:http://technet.microsoft.com/en-us/library/gg214171(WS.10).aspx
Several utilities do not operate with the HP X5000 G2 Network Storage System	The HP X5000 G2 Network Storage System does not have a VDS Hardware Provider, so the following utilities do not work:The Microsoft Storage Manager for SAN (Server Manager+Storage+SMFS)Diskraid (command line utility)Provision Storage link from Share and Storage Management MMC (Server Manager+Roles+File Services+Share and Storage Management)
cluster validation wizard fails, indicating a failure in the storage tests from the Microsoft test report. The failure described is the inability to write to of the disk partitions.	HP recommends the following:When attempting to create a cluster, the HP one or more volumes were removed before running the validation wizard, they may be flagged with warnings during the cluster validation even though they do not exist. These warnings can be ignored. The network used for the cluster heartbeat uses APIPA (169.254.0.0/16) addresses which will be flagged with warnings during the cluster validation. These warnings can be ignored. The cluster validation may indicate that one or more disks are corrupted. When this happens the test terminates. You should run chkdsk.exe on the disk. It is not important to use any options on the chkdsk command line. For example, if the drive letter for the corrupted disk is Q: then you would run chkdsk q:.
The NFS user mapping should not use ADLDS.	HP strongly recommends using Active Directory or other RFC2307 compliant LDAP stores for NFS user name mapping. Using Active Directory Lightweight Data Services (ADLDS) is not recommended. Configuring ADLDS in a clustered environment is beyond the scope of this document.
The Onboard Administrator GUI cannot be launched from the Integrated Lights-Out 3 page. The Launch button in the Active Onboard Administration section under the BL c-Class node in Integrated Lights-Out 3 navigation tree.	the Onboard Administrator GUI Launch button only applies to systems with the C3000/C7000 chassis. You are not able to use this button with the X5000 G2 Network Storage System. the
On rare occasions, an update to the I/O module firmware may result in the following message: Flash failed for xxxx half of SAS I/O Module. Check log file yyyy for more information (where xxxx is internal or external and yyyy is the path and name of the log file).	Update the SAS I/O module firmware again. If the second update is unsuccessful, review the log file for more information.
If the System Management Homepage lists a fan module as unknown or dormant, it might not be a fan issue may mean that a SAS I/O module needs to be reseated.	Identify and reseat the SAS I/O module that is causing the issue. An I/O module may need to be replaced if there is less information available for the I/O module than the other.
If the cache on the 1210m controller either server blade of the X5000 G2 becomes disabled, it will greatly affected performance. As a protective measure to ensure the safety of data, if either 1210m controller experiences an issue requiring the cache to be disabled, the cache is disabled on both controllers. This results in the reduction of performance for both controllers until degraded part is repaired or replaced	An alert is generated for cache and supercapacitor (cache backup) issues, but you can also run the following command from a command prompt or PowerShell to determine the issue: ccu show controller all details If the output is similar to the following, replace the cache module or supercapacitor: controller 0: 500143800442D690 Manufacturer: HP Model: 1210m Part Number: 607190-001 SKU: None Serial Number: PBGJROXTAZ40FK Firmware Version: 0156 Firmware Build: 2011061702 Peer Controller: 500143800442E600 Operational Status: Degraded, Cache disabled: redundant controller battery issue Health Status: Degraded/Warning Cache Size: 1073741824 Read Cache Default: Enabled Write Cache Default: Enabled Battery 0 Status: fully charged Battery 0 Estimated Charge Remaining: 100%controller 1: 500143800442E600Manufacturer: HPModel: 1210mPart Number: 607190-001SKU: NoneSerial Number: PBGJROXTAZ407ZFirmware Version: 0156Firmware Build: 2011061702Peer Controller: 500143800442D690Operational Status: Degraded, Cache flash backuphardware failure, Cache disabled: low battery chargeHealth Status: Degraded/WarningCache Size: 1073741824Read Cache Default: EnabledWrite Cache Default: EnabledBattery 0 Status: chargingBattery 0 Estimated Charge Remaining: 0%
if there is no redundancy and the volumeis in a Bad state, the Create a Volumewizard will fail at the format andpartition step. The following errormessage will display:Failed to located LUN on host	Delete the volume that is in a Bad state and try again to create a volume.When
When configuring iLO settings in theInitial Configuration Tasks window,changing iLO settings on the secondnode may result in an error that thehas insufficient permissions. This canhappen even if the user is a domainadministrator and belongs to theadministrator group on each node. TheUser Access Control system prevents theapplication from running on the secondnode. No prompt is displayed to theto allow execution on the second node.	Log on to the second node using the local administrator account andconfigure the iLO settings using the iLO Configuration Utility in the HPSystem Tools program group.userConnect to iLO and change the settings using the iLO user interface.NOTE:Changing the iLO network settings may cause your iLO sessions todisconnect.user
You have installed the System Recoverimage on a storage system that hasexternal disk enclosure connected to thestorage system and the disk enclosuresither has existing LUNs or a degradeddisk. After installing the image, theHardware Status tab in the SystemManager and the System ManagementHomepage indicate the disk drives aredegraded and, if you use the Create aVolume wizard, the disk drives are onlydisplayed for one node.	Delete existing LUNs using either the Delete a Volume or Create a WitnessDisk wizard after installing the System Recovery image.
If you connect the storage system tothan one network or subnet and thenwizard may fail with the following errorStatic network xx.xx.xx.x /xxwas not configured. Pleaseuse -StaticAddress to usethis network or use-IgnoreNetwork to use it.	Three error message typically appears when the subnet mask is incorrectlyspecified for one or more network adapters. Verify that each network adapteris correctly configured to operate on the respective network by checking thatthe Cerror: the IP address, network mask, and gateway is applicable. You can alsoexecute the ping command to confirm connectivity on the network.
A drive letter is selected for a new volume in the Create a Volume wizard. letter.	This is a temporary condition that exists only until the volume has been added, the cluster as a cluster disk. Afterwards, the volume appears on the owner node with the desired drive letter. On the alternate node, the volume will not appear in Windows Explorer. The disk will appear in Disk Management once the alternate node, but it will have a status of Reserved and will not have a drive letter. If the cluster moves the disk resource to the alternate node, the desired drive letter will be used on the alternate node (provided the drive letter is still available). Drive letters can be changed using the Failover Cluster Manager after the disk has been added to the cluster.
The Test WBEM Events tool displays error when the tool is launched by a user other than Administrator.	dn Add the specific user name to the following namespaces:•root\HPQ•root\HPQ\default•root\HPQ\TestEvent•root\Interop•root\CIMv22. For each namespace, complete the following namespace security steps:a. Right-click My Computer→Manage→Services and Applications.b. Right-click WMI Control.c. Click Properties.d. Select the Security tab.e. Select the namespace.f. Click the Security button and enable the following permissions for the user:•Execute Methods•Full Write•Partial Write•Provider Write•Enable Account•Remote Enable•Read Security•Edit Security3. Click Apply and then click OK twice.

Using Storage Viewer

You can access the Storage Viewer under Manage storage in the Server Manager. The Storage Viewer enables you to view details about each LUN – name, size RAID level, pool assignment, spare drive indication, and cluster disk name (if applicable). In the lower part of the tool, select one of the following tabs to view additional information:

• Volumes: Displays any Windows volumes on the LUN, the volume label, and mount paths.
- Drives: Displays details about the physical drives that comprise the LUN (drive bay, size, RPM, disk name, and serial number).
- Spares: Displays details about any spares that are assigned to the LUN (drive bay, size, RPM, disk name, and serial number). If more information is available, when you hover over any part of the row, a tool tip opens with details.
- Jobs: Displays the status of any jobs running on the LUN (checking volume data integrity and rebuilding). For example, if a spare drive is in use as a failed drive replacement, a tool tip message will be shown.

Figure 36 Storage Viewer (LUNs view)

You can also view details about each drive - bay location, ID, serial number, size, health, and model number. In the lower part of the tool, you can view volume information related to the drive

Figure 37 Storage Viewer (Drives view)

HP Support websites

Use the "Support and troubleshooting" task at the HP Support & Drivers website (http://www.hp.com/go/support) to troubleshoot problems with the storage system. After entering the storage system name and designation (for example, X5000 G2 Network Storage System) or component information (for example, SAS I/O module), use the following links for troubleshooting information:

• Download drivers and software—Provides drivers and software for your operating system.
• Troubleshoot a problem—Provides a listing of customer notices, advisories, and bulletins applicable for the product or component.
• Manuals—Provides the latest user documentation applicable to the product or component. User guides can be a useful source for troubleshooting information. For most storage system hardware platforms, the following ProLiant server manuals may be useful for troubleshooting assistance:

HP ProLiant Server User Guide or HP ProLiant Server Maintenance and Service Guide

These guides contain specific troubleshooting information for the server.

° HP ProLiant Servers Troubleshooting Guide

The guide provides common procedures and solutions for many levels of troubleshooting with a ProLiant server.

IMPORTANT: Some troubleshooting procedures found in ProLiant server guides may not apply to the storage system. If necessary, check with your HP Support representative for full assistance.

For X5000 G2 guides, go to www.hp.com/support/manuals, select NAS Systems under storage, and select an X5000 G2 product.

For software-related components and issues, online help or user guide documentation may offer troubleshooting assistance. Known issues, workarounds and service releases are addressed in this guide or the release notes.

• Customer notices—Address informational topics about the HP X5000 G2 Storage System.
• Customer advisories—Address know issues and solutions or workarounds.

NOTE: You must register for Subscriber's Choice to receive customer advisories and notices. See "Subscription service" (page 128) for more information.

HP Insight Remote Support software

HP strongly recommends that you install HP Insight Remote Support software to complete the installation or upgrade of your product and to enable enhanced delivery of your HP Warranty, HP Care Pack Service, or HP contractual support agreement. HP Insight Remote Support supplements your monitoring, 24x7 to ensure maximum system availability by providing intelligent event diagnosis, and automatic, secure submission of hardware event notifications to HP, which initiates a fast and accurate resolution, based on the service level of your product. Notifications may be sent to your authorized HP Channel Partner for onsite service, if configured and available in your country. The software is available in two variants:

• HP Insight Remote Support Standard: This software supports server and storage devices and is optimized for environments with 1 to 50 servers. Ideal for customers who can benefit from pronotification, but do not need proservice delivery and integration with a management platform.
• HP Insight Remote Support Advanced: This software provides comprehensive remote monitoring and proservice support for HP servers, storage, network and SAN environments, plus selected non-HP servers than have a support obligation with HP. It is integrated with HP Systems Insight Manager. A dedicated server is recommended to host both HP Systems Insight Manager and HP Insight Remote Support Advanced.

Details for both versions are available at:

http://www.hp.com/go/insightremotesupport

To implement Insight Remote Support for HP X5000 G2 systems, follow the instructions in release A.05.70 or later of the following guides:

• HP Insight Remote Support Standard Hosting Device Configuration Guide (for standard support)
- HP Insight Remote Support Advanced CMS Configuration and Usage Guide (for advanced support)
- HP Insight Remote Support Standard Managed Systems Configuration Guide (for standard support).

To obtain these guides:

1. Go to the Insight Remote Software website (previously cited).
2. From the Product Information menu, select either Insight Remote Standard or Insight Remote Support Advanced software.
3. Select Support Documentation.

Be aware of the following specifics for HP X5000 G2 systems:

• The storage system is a "managed system" as described in Insight Remote Support guides.
• The X5460sb is equivalent to a ProLiant server and meets all the requirements for a managed system.

Follow guidelines and procedures for Windows Proliant servers in the Insight Remote Suppe documentation.

• The storage system hardware is preconfigured for Insight Remote Support and uses the WMI (WBEM) provider.
• Register the system using the X5000 G2 product number and serial number, instead of the blade serial number and part number.

Confirm and overwrite any prepopulated values with the serial number of the storage system. The product number and serial number are located on the pull-out tab located below the Enclosure Management module on the back of the enclosure, ((Figure 40 (page 54))).

- You must register WBEM access credentials in HP SIM for Insight Remote Support Advanced.

Microsoft Systems Center Operations Manager

Microsoft Systems Center Operations Manager (SCOM) provides comprehensive monitoring, performance management, and analysis tools to maintain Windows OS and application platform. This solution allows you to monitor Microsoft Windows environments and HP storage products through a common OpsMgr console. To download HP management packs for Microsoft System Center Operations Manager, including installation, configuration, and usage documentation, visit the HP Management Packs for Microsoft Systems Center site at:

www.hp.com/go/storageworks/scom2007

Windows Recovery Environment

You can use Windows Recovery Environment to help diagnose and recover from operating system errors which may prevent Windows from booting. To use Windows Recovery Environment to perform a system recovery, see "Restoring the system with Windows Recovery Environment" (page 125).

Startup Repair

1. Do one of the following:

a. For direct access, attach the SUV cable (supplied with the HP X5000 G2 Network Sto-System) to the port on the front of the server blade you want to recover. Connect a and USB mouse to the SUV cable. Using the remaining USB connector on the SUV can connect either a USB DVD drive (and insert the System Recovery DVD) or a bootable flash device (prepared with a System Recovery image).
b. For remote management access, connect to the server using iLO from a client PC. Insert the System Recovery DVD in the client PC or attach a bootable USB flash device that been prepared with a System Recovery image.

1. Reboot the server blade to either the USB flash device or USB DVD drive.

The system BIOS attempts to boot to the USB device first by default. Watch the monitor c during the boot as you may need to press a key to boot to the USB media

NOTE: If directly connected, you may have to change the BIOS settings to ensure proper boot sequence. If connected remotely, you may have to change some iLO settings to ensure proper boot sequence.

1. Select Windows Recovery Environment.

The recovery environment is loaded.

1. Once the recovery environment is loaded, the System Recovery Options wizard opens. On the first window, select the keyboard input method, which is based on your location (for example, select US for United States) and click Next.

2. Select either of the following options (it does not matter which option is selected) and click Next:

- Use recovery tools that can help fix problems starting Windows. Select an operating system to repair.

- Restore your computer using a system image that you created earlier.

1. Click Cancel until the Choose a recovery tool window opens.

Figure 38 System recovery options

1. Click Startup Repair.

The utility automatically attempts to repair the system image startup process. It also attempts to repair the errors. If the errors cannot be repaired, an alert window is displayed:

Figure 39 Startup repair alerts

1. Select Don't send.

2. When the utility has finished running, click Restart when prompted to restart the system.

Memory Diagnostic

1. Do one of the following:

a. For direct access, attach the SUV cable (supplied with the HP X5000 G2 Network Storage System) to the port on the front of the server blade you want to recover. Connect a and USB mouse to the SUV cable. Using the remaining USB connector on the SUV can connect either a USB DVD drive (and insert the System Recovery DVD) or a bootable flash device (prepared with a System Recovery image). b. For remote management access, connect to the server using iLO from a client PC. Insert the System Recovery DVD in the client PC or attach a bootable USB flash device that been prepared with a System Recovery image.

1. Reboot the server blade to either the USB flash device or USB DVD drive.

The system BIOS attempts to boot to the USB device first by default. Watch the monitor c during the boot as you may need to press a key to boot to the USB media

NOTE: If directly connected, you may have to change the BIOS settings to ensure proper boot sequence. If connected remotely, you may have to change some iLO settings to ensure proper boot sequence.

1. Select Windows Recovery Environment.

The recovery environment is loaded.

1. Once the recovery environment is loaded, the System Recovery Options wizard opens. On the first window, select the keyboard input method, which is based on your location (for example, select US for United States) and click Next.

2. Select either of the following options (it does not matter which option is selected) and click Next:

- Use recovery tools that can help fix problems starting Windows. Select an operating system to repair.

- Restore your computer using a system image that you created earlier.

1. Click Cancel until the Choose a recovery tool window opens.

2. Click Windows Memory Diagnostic.

3. Select one of the following options:

- Restart now and check for problems. Select this option to restart the system and scan for memory issues. Do not remove the attached USB DVD or USB flash drive.

- Check for problems the next time I start my computer. Select this option to schedule a memory diagnostic after you restart the system. Do not remove the attached USB DVD USB flash drive.

HP 1210m Volume Online Tool

Use the HP 1210m Volume Tool to manually set all volumes online. Manually setting volumes may be necessary if a disk enclosure is powered down before the server blades are powered down and the enclosure contains disks with LUNs on them.

IMPORTANT: You should only use this tool under the guidance of HP Support to avoid potential data loss.

The tool is included (but not installed) with HP X5000 G2 software version 2.02.0a or later.

To install the tool:

1. Navigte to the C:\hpnas\support directory on the server blade.

2. Double click Volume_Manager_Install.msi.

To use the tool:

1. Navigate to C:\Program Files (x86)\Hewlett-Packard\HP 1210m Volume Online Tool.

2. Double-click HPVolumeOnlineTool.exe to start the tool.

NOTE: Before the tool opens, a disclaimer about potential data loss is displayed. Read the disclaimer and accept the terms to continue. If you decline, the tool closes.

1. When the HP 1210m Volume Online Tool opens, the LUNs that are in an Enabled but Offline state are displayed.

2. Click Force Online.

When the operation is complete, the tool indicates that the LUNs are now in the Enabled state.

Obtaining the Service Agreement ID

Obtain the SAID from your service contract agreement and keep it in a secure location. You must provide it when you contact HP Support.

Locating the storage system warranty entitlement label

You must locate and identify the serial number and product number for the storage system components to obtain service under the warranty. The numbers are listed on the warranty entitlement label located on the pull-out tab below the Enclosure Management module on the back of the enclosure (Figure 40 (page 54)).

Figure 40 Warranty entitlement label location

5 Upgrading the storage system

The HP X5000 G2 Network Storage System is comprised of a common hardware platform containing two server blades. Each server runs Windows Storage Server 2008 R2 or later.

When HP determines that it is desirable to upgrade one or more of these components, a note is posted to the HP support website for the HP X5000 G2 Network Storage System with the notes and the updated code. HP recommends that you upgrade the storage system software as part of normal system maintenance for increased reliability and a better customer experience. Upgrades might also be necessary when replacing a server blade or other component.

Maintaining your storage system

HP recommends the following guidelines for maintaining your system, depending on your environment:

• You are not required to install any updates if your storage system is working properly.
• If security updates are important for your operating environment, you can:

Use Microsoft Windows Update to download updates.°

• Use Windows Update Server to update the server blades in the storage system.

• Download and install specific security updates as needed.

• If your maintenance policy is to only update servers to current and tested versions of drivers, firmware, and software, install the services releases when they are available.

• If your maintenance policy allows you to update servers to current versions of drivers, firmware, and software that have not been tested with the storage system, you can go to http://www.hp.com and download and install specific updates from the storage system product page or the platform product page (for example, the specific server model used for the st-system server blade).
• When updating the server blades, update the NIC drivers, firmware, and software in the same update window. HP recommends updating the RAID controller drivers, firmware, and software in the same update window to ensure proper operation of the storage system.

Determining the current storage system software version

You can find the version using the Server Manager or the registry.

From the Server Manager:

1. Expand the tree under System Manager.
2. Select System and Network Settings and locate the value for HP Quick Restore.
3. Read the value for HP Quick Restore in the System and Network Settings right pane.

Figure 41 System and network settings

From the registry:

1. Log in to the server blade.
2. Open a command window.
3. Enter the reg query command as shown in the following example:

C:> reg query HKLM\Software\Wow6432Node\Hewlett-Packard\StorageWorks /s

The version information that displays depends on the software version that you are currently running. The output format will look similar to the following:

HKEY_LOCAL_MACHINE\Software\Wow6432Node\Hewlett-Packard\StorageWorks\QuickRestore

The QRVersion field lists the version.

Upgrading X5000 G2 software

Software upgrades are typically distributed as service releases.

Download the service release file:

1. Go to http://www.hp.com/go/support.
2. Select Drivers and Software.
3. Enter X5000 G2 in the Enter a product name/number box and click Search.
4. Select your X5000 G2 product, select the operating system, and then select the service release
5. Follow the instructions included with the service release for installation.

Upgrading a component's firmware

To determine if a component requires a firmware upgrade:

IMPORTANT: Remember the following:

• You must complete these steps on each server.
- HP recommends that you complete any upgrade during a scheduled maintenance period and/or during periods of low user activity.

1. Install Hewlett-Packard CMP - Firmware Module from the latest X5000 G2 Service Release.
2. Select the System Manager in Server Manager. Click the System Summary tab, and inspect the Firmware update recommended icon status (Figure 42 (page 57)). If the icon is green, no firmware update is needed. If the icon is yellow, a firmware update is required. You can also check the Software component on the System Management Homepage to verify what

firmware versions are currently installed. See "HP System Management Homepage" (page 2 for more information.

Figure 42 System summary tab

1. If a firmware update is needed, select the Firmware tab to view a list of the components that can be upgraded (Figure 43 (page 58)).

The list of components can include:

• Integrated Lights-Out (iLO)
•HP 1210m controller
• System ROM (124) for the server blade
•Power Management controller firmware (c-Class blades)
•Smart Array HP P410i Blade HDD controller
•Enclosure Manager Unit (EMU)
• External half of the SAS I/O module
•Internal half of the SAS I/O module
• I/O module on an external disk enclosure
•Hard disk drives (various models)

Figure 43 Firmware tab

1. On the Firmware tab, select the box next to each component to be upgraded.
2. Click Apply Updates. The status reports that an upgrade is in progress.

CAUTION: When upgrading the controller firmware, you must complete the upgrade and power cycle one controller and then upgrade and power cycle the other controller. Otherwise, the firmware may synchronize with the controller running the previous version of code.

If, after upgrading the firmware on the controllers, the storage system does not see any storage or the controllers do not start, see "Resolving errors after the HP 1210m controller upgrade" (page 59).

NOTE: Each firmware upgrade takes a few minutes to complete. If you are upgrading multiple components, such as hard drives, the upgrade takes more time.

1. Reboot the server blade from the Start menu, if needed.

A message appears on the Firmware tab to alert you if a reboot is required after each component firmware upgrade. After the upgrade completes, the Firmware Status changes from "Firmware updates recommended" to "A reboot is required."

NOTE: If a reboot is not required after the component firmware upgrade completes, a green checkmark displays next to the component name.

1. Open the Firmware tab in the System Manager and verify that the upgrade was successful. You can also check the upgrade status on the System Summary tab.

If the firmware upgrade failed, the component is listed as an available upgrade in the Firmwc tab after the firmware upgrade and reboot. To determine the next steps for a successful firmwc upgrade, go to the Reports tab (see "Reports" (page 33)) and run a report.

Resolving errors after the HP 1210m controller upgrade

If the firmware upgrade for the HP 1210m controller does not complete successfully, the control could stop responding. As a result, the Controller Properties dialog box in Windows Device Manager displays "This device cannot start" and the storage system Configuration Wizard fails to detect storage.

To resolve this issue, first try the Simple method. If the issue persists, try the Advanced method: Simple method:

1. Upgrade the HP 1210m controller firmware on one server blade.
2. Upgrade the HP 1210m controller firmware on the other server blade.
3. Shut down both server blades.
4. Power on both server blades.

Advanced method:

1. Shut down both server blades and power off the entire HP X5000 G2 enclosure.
2. Power off and disconnect all disk enclosures.
3. Pull one of the server blades a quarter of the way out of the enclosure.
4. Power on the HP X5000 G2 enclosure.
5. If not already powered on, power on the server blade that remained in the enclosure.
6. Open System Manager.
7. Select the Firmware tab.
8. Select the 1210m controller and click Apply Updates.
9. Shut down the server blade that was powered on in Step 5.
10. Power off the HP X5000 G2 enclosure.
11. Push the other server blade back into the enclosure.
12. Reconnect the disk enclosures.
13. Power on the HP X5000 G2 enclosure and both server blades.
14. Verify that the 1210m controller firmware in both server blades is current.

Resolving errors after a disk drive firmware upgrade

If, after upgrading disk drive firmware on the storage system and rebooting the storage system the System Manager indicates an upgrade is needed, complete the following procedure:

1. Log in to the server in Bay 2.
2. Shut down the server in Bay 2 from the Windows Start menu.
3. Log in to the server in Bay 1 and open Server Manager.
4. Open the System Manager and select the Firmware tab.

5. In the Components Available for Upgrades window, select the drive firmware.

6. Click Apply Updates.

7. Once the update is complete, shut down Server Manager and any other running application

8. Shut down the server in Bay 1 from the Windows Start menu.

9. Power off any connected disk enclosures.

10. Power down the storage system chassis by pressing and holding the power button on the back of the enclosure.

11. Disconnect the power cables from the storage system and any connected disk enclosures.

12. Reconnect the power cables.

13. Power on any disk enclosures.

14. Power on the storage system chassis by pressing the power button on the back of the enclosure.

15. If necessary, manually power on the servers.

Resolving an EMU upgrade issue

When upgrading the EMU firmware, if the EMU and the server blade initiating the upgrade are not on the same subnet, the upgrade fails. The following message (an example) displays on the System Manager Firmware tab:

Flash failed for Enclosure Management Unit (EMU) using cpXXXXXX.exe. Check log files (C:\ProgramData\Hewlett-Packard\CMP\logs\firmware.log and C:\CPQSYSTEM\log\cpqsetup.log) for further information.

The C:\CPQSYSTEM\log\EmuFlash.log displays the following information (an example only):

Enclosure Manager information: Product Name : HP CSP EMUPart Number :

620022-001Serial Number : PBCYU0G9V0C01XUUID : 99PBCYU0G9V0C01XManufacturer

: HPFirmware Ver. : EM: 1.10 Jul 12 2011; HM: 1.3EMU Type : 1Hw Version

: Rev. BAux Info : SVN: 3221 branches/QUIRE-CSP-1-10

1.10 Jul 12 2011

Starting Flash Routine

Launching Http Server

Host IP Address:

Host IP not found

If this issue occurs, configure the EMU and server blade networking to be on the same subnet ar retry the firmware upgrade.

Upgrading hardware components

To replace a hardware component with an upgrade, follow the component removal and replacemer instructions in "Removing and replacing hardware components" (page 61). For example, to replace the HP 1 GB Ethernet I/O module with a 10 GB module, follow the instructions in "Removing and replacing the HP Ethernet I/O module" (page 78). If you need to shut down a server blade or the storage system to replace a component, follow the instructions in "Powering the storage system off and on" (page 60).

Powering the storage system off and on

Follow these steps to shut down a single server blade or to perform a storage system shutdown:

1. From the Windows desktop, select Start→Shut Down as follows:

a. While you are connected to blade 2, shut down blade 2 by clicking Start, and then Shut Down.
b. While you are connected to blade 1, shut down blade 1 by clicking Start, and then Shut Down.

NOTE: Let the Windows shutdown run to completion, which will power the blade off.

1. Power off any disks in disk enclosures by pressing and holding down the power button located on the back of each disk enclosure.
2. Power off the storage system enclosure by pressing and holding down the power button located on the back of the enclosure.
3. Disconnect the power cables (optional).
   To power on the server blades and storage system, reverse the shutdown procedure.

6 Removing and replacing hardware components

This chapter describes procedures for removing and replacing hardware components.

Customer self repair

HP customer self repair (CSR) programs allow you to repair your HP product. If a CSR part is replacing, HP ships the part directly to you so that you can install it at your convenience. So parts do not qualify for CSR. Your HP-authorized service provider determines whether a repair be accomplished by CSR.

For more information about CSR, contact your local service provider, or see the CSR website: http://www.hp.com/go/selfrepair

Best practices for replacing components

The following sections provide information to help you successfully replace the hardware component on your system.

WARNING! To reduce the risk of personal injury or damage to the equipment:

• Be sure that only one component is extended from a rack at a time. A rack may become unstable if more than one component is extended at the same time.
• Do not extend the hard drive drawers beyond the supporting surface when the unit is not installed in a rack.

CAUTION: Removing a component significantly changes the air flow within the enclosure. All components must be installed for the enclosure to cool properly. If a component fails, leave it place in the enclosure until a new component is available for installation.

IMPORTANT: Be sure to unpack the replacement part before you remove the existing compone

During replacement of the failed component

• HP recommends waiting until periods of low system activity to replace a component.
• For all hot/warm swappable components (SAS I/O module, fan module, Ethernet I/O module, PCIe module, server airflow baffle, server blades, and hard drives), be sure to unpack the replacement part before removing the existing part.

• When replacing components at the rear of the rack, cabling may obstruct access to the component. Carefully move any cables out of the way to avoid loosening any connections. In particular, avoid cable damage that may be caused by:

• Kinking or bending
  ° Disconnecting cables without capping. If uncapped, cable performance may be impaired by contact with dust, metal, or other surfaces.

• Placing removed cables on the floor or other surfaces where they may be walked on otherwise compressed.

Accessing component replacement videos

HP produced videos of the procedures to assist you in replacing components. To view the video go to the HP Customer Self Repair Services Media Library website and navigate to your product http://www.hp.com/go/sml

Identifying the spare part

Parts have a nine-character spare part number on their label. For some spare parts, the part num is available in the system. Alternatively, the HP call center can assist in identifying the correct spc part number.

Replaceable parts

This product contains replaceable parts. To identify the replaceable parts, see the individual component guides listed in Table 15 (page 65).

Parts that are available for CSR are indicated as follows:

• Mandatory CSR — You order the part directly from HP and repair the product yourself. On-site or return-to-depot repair is not provided under warranty.
• Optional CSR — You can order the part directly from HP and repair the product yourself, or you can request that HP repair the product. If you request repair from HP, you may be charged for the repair depending on the product warranty.
• No CSR — The replaceable part is not available for self repair. For assistance, contact an HP-authorized service provider.

For more information about CSR — contact your local service provider. For North America, see the CSR website:

http://www.hp.com/go/selfrepair

To determine the warranty service provided for this product, see the warranty information website: http://www.hp.com/go/storagewarranty

To order a replacement part, contact an HP-authorized service provider or see the HP Parts Store online:

http://www.hp.com/buy/parts

Figure 44 (page 63) shows an exploded view of the system.

Figure 44 Exploded view of the system

Table 14 (page 64) lists the CSR replaceable parts for the system.

Table 14 Storage system replaceable parts

				Replacement type (Cold, Warm, Hot)CSR availability
				ColdOptional631117-001Ser
				ColdNo631115-001Midplane
(Not shown)	.5 M mini SAS cable	408765-001	Mandatory	Hot
(Not shown)	Mini SAS cable 2 M	408767-001	Mandatory	Hot
(Not shown)	Mini SAS cable 4 M	408768-001	Mandatory	Hot
3	LFF SAS I/O module	631941-001	Mandatory	Hot
(Not shown)	SFF SAS I/O module	631940-001	Mandatory	Hot
4	Fan modules	631109-001	Mandatory	Hot
5	Power UID button assembly	399054-001	Optional	Cold
6	Power supplies	631942-001	Mandatory	Hot
7	2-port 10 Gb Ethernet module	631111-001	Mandatory	Hot
8	2-port 1 Gb Ethernet module	611378-001	Mandatory	Hot
(Not shown)	1 Gb intraconnect module	631114-001	Mandatory	Hot
9	NC365T 4-port Ethernet server adapter	593721-B21	Optional	Warm
10	Enclosure Manager module	631112-001	Mandatory	Hot
11	Server blade backplane	631116-001	No	Cold
12	Server airflow baffle	631129-001	No	Cold
13	Coil power assembly	631130-001	No	Cold
14	Drive drawer bezel LFF	631118-001	Optional	Cold
(Not shown)	Drive drawer bezel SFF	631124-001	Optional	Cold
15	LFF LED display board	631126-001	Optional	Cold
(Not shown)	SFF LED display board	631125-001	Optional	Cold
16	LFF drive drawer assembly	631128-001	Optional	Cold
(Not shown)	SFF drive drawer assembly	631127-001	Optional	Cold
(Not shown)	Hard drive drawer blanks	389015-001	Mandatory	Hot
(Not shown)	1 TB Hard drive	508011-001	Mandatory	Hot
(Not shown)	2 TB Hard drive	508010-001	Mandatory	Hot
17	Drawer rails bottom	631131-001	No	Cold
18	Drawer rails left	631132-001	No	Cold
(Not shown)	Mezzanine NIC	462748-001	Optional	Warm
(Not shown)	Right ear bezel on chassis (3629960-001, one for each model)	629960-002, 629960-003	Optional	Hot
19	1210m controller	615360-001	Optional	Warm
20	Cache module for 1210m	598414-001	Optional	Warm

Part numbe

ver interpose

board2

Table 14 Storage system replaceable parts (continued)

				Replacement type (Cold, Warm, Hot)CSR availability
21	Cache			WarmMandatory587225-001
(Not shown)	Rail kit assembly	631133-001	Optional	Cold
(Not shown)	HP 82B HBA (Brocade) PCI fibre HBA	AP770A	1	ColdOptional
(Not shown)	HP 82E HBA (Emulex)	AJ763A	1	WarmOptional
(Not shown)	HP 82Q HBA (Q-Logic)	AJ764A	1	WarmOptional

Part nu

Superca

¹ Used only for backup. See www.hp.com/go/ebs for information about tested backup applications.

For more information on removing and replacing components, see Table 15 (page 65) for a list of individual component documents.

Table 15 Related component documents

Component	Component name	Guide
Server blade	X5460sb blades	HP ProLiant BL460c G7 Server Blade Maintenance and Service Guide
Disks in disk enclosures	The large form factor (LFF) supports 12 3.5-inch disk drives and the small form factor (SFF) supports 25 2.5-inch disk drives.	HP D2600/D2700 Disk Enclosure User Guide

Hot, warm, and cold swap components

Hot or warm swapping a component means removing and replacing it while the main power is still on. Cold swapping means removing and replacing the component while the main power is off. Port (purple) colored handles on components like the fan module indicate the component is hot-swappable.

IMPORTANT: Remove and replace components quickly without interrupting the process.

Preventing electrostatic discharge

CAUTION: Components can be damaged by electrostatic discharge (ESD). Use proper antistatic protection.

• Always transport and store CSR replaceable parts in an ESD-protective enclosure.
- Do not remove CSR replaceable parts from the ESD-protective enclosure until you are ready to install it.
- Always use ESD precautions, such as a wrist strap, heel straps on conductive flooring, and an ESD-protective smock when handling ESD-sensitive equipment.
- Avoid touching all connector pins, leads, or circuitry.
- Do not place ESD-generating material such as paper or non-antistatic (pink) plastic in an ESD-protective with ESD-sensitive equipment.

Verifying component failure

Use the following methods to verify component failure:

• Analyze any failure messages received. Fault monitoring software from HP provides a recommended action.
• From the System Manager, select the System Summary tab to check the enclosure health status or select the Hardware Status tab to identify a failed component. See "Using the System Manager" (page 30) for more information.

- You can also use the System Management Homepage to identify hardware problems. For example, to identify the affected enclosure, select Unit Identification Device in the Enclosure pane and then on the Unit Identification Device window, click On. The blue UID indicator on the controller enclosure blinks. See "HP System Management Homepage" (page 26) for more information.

- Look for a blinking amber LED on the component. See "Component LEDs" (page 34) for LED information.

Verifying proper operation

After replacing a system component, check the following to verify that the component is operating properly:

• If applicable, verify that the green LED is lit continuously or blinking. If not, try reseating the component.
• From the System Manager, navigate to the Hardware Status and System Summary tabs to confirm the component failure alert no longer appears. The status should be (Good).

Wait times for hard disks

If the hard drive is part of a volume, the following wait times apply:

Removal: Less than three seconds for the LED to turn off

Insert:

•Less than one second for first disk activity
- Less than 15 seconds for the disk to be ready for REBUILD. The LED blinks at 1 Hz.

NOTE: The transition to solid green depends on how long the REBUILD takes (the LEDs indicate REBUILD).

If the hard drive is not part of a volume, the following wait times apply:

Removal: No indication appears because the LED is already off

Insert:

•Less than one second for the first disk activity to appear
•Less than 15 seconds for the disk to be ready to use

Removing the system enclosure from the rack

1. Extend the hard drive drawer (Figure 45 (page 67)):

a. Press upward on the release button on the hard drive drawer (1).

b. Pull the drawer handle down 90 degrees (2).

c. Extend the hard drive drawer (3).

Figure 45 Extending the hard drive drawer

1. Label the hard drives (Figure 46 (page 67)).

IMPORTANT: Use the drive labels provided with the replacement part when removing the drives to ensure you replace the drives in the correct order.

Figure 46 Hard drive labeling

1. Remove all hard drives.

WARNING! Carefully check the drive labels provided with the replacement board, and the install the hard drives in the same slots from which you removed them. If the drives are installed in the correct slots, the system might fail.

1. Push the hard drive drawer back into the system enclosure.

2. Label each server blade and then remove both server blades.

3. Label the cables and then unplug all cables from the back of the system enclosure.

4. Unscrew the retaining screws from the bezel ears, and then remove the enclosure from the rack.

WARNING! The system enclosure is heavy, even after removing the hard drives. Always use at least two people to remove the system from the rack.

Inserting the system enclosure into the rack

1. Place the enclosure into the rack, and secure the enclosure by tightening the two retaining screws.

WARNING! The system enclosure is heavy, even after removing the hard drives. Always use at least two people to replace the system in the rack.

1. Replace both server blades in their original bays.
2. Extend the hard drive drawer (Figure 47 (page 68)):

a. Press upward on the release button on the hard drive drawer (1).
b. Pull the drawer handle down 90 degrees (2).
c. Extend the hard drive drawer (3).

Figure 47 Extending the hard drive drawer

1. Replace all hard drives.

IMPORTANT: Install the hard drives in the same slots from which you removed them or the system might fail. Use the drive labels to ensure that you replace the drives in the correct order

1. Push the hard drive drawer back into the system enclosure.
2. Plug in all cables at the back of the system enclosure, and ensure that all cables are returned to their original locations.
3. Power on the system by pressing the power button ON.
4. Confirm that the system has resumed normal operations.

Removing and replacing the server interposer board

Removing the server interposer board

1. Verify the failed component as described in "Verifying component failure" (page 66).
2. Power off the system as described in "Powering the storage system off and on" (page 60).

3. Remove the enclosure from the rack as described in "Removing the system enclosure from the rack" (page 67).

4. Remove the top back panel by pressing the panel release button and lifting the latch to sli the top back panel off.

5. Open the release handle (1, Figure 48 (page 69)), and pull up to remove the server interposer board (2, Figure 48 (page 69)).

NOTE: You may need to use significant force to accomplish this task.

Figure 48 Removing the server interposer board

Replacing the server interposer board

1. With the release handle open, align the server interposer board with the alignment pins (1, Figure 49 (page 69)), and then close the server interposer release mechanism (2, Figure 49 (page 69)).

NOTE: Remember to move the server backplane power cable out of the way of the align pins.

Figure 49 Replacing the server interposer board

1. Reinstall the top back panel.

2. Replace the enclosure in the rack as described in "Inserting the system enclosure into the rack" (page 68).

Removing and replacing the midplane board

Removing the midplane board

1. Verify the failed component as described in "Verifying component failure" (page 66).
2. Power off the system as described in "Powering the storage system off and on" (page 60).
3. Remove the enclosure from the rack as described in "Removing the system enclosure from the rack" (page 67).
4. Remove the top back panel by pressing the panel release button and lifting the latch to slide the top back panel off.
5. Remove all modules from the back of the enclosure.

NOTE: Make a note of all module locations so they can be placed back into their original locations.

1. Open the release handle (1, Figure 50 (page 70)), and pull up to remove the server interposer board (2, Figure 50 (page 70)).

NOTE: This step may require significant force to accomplish.

Figure 50 Removing the server interposer board

1. Remove the plug bracket (2, Figure 51 (page 70)) from the coil power plug by removing the thumbscrew (1).

Figure 51 Removing the plug bracket from the coil power plug

1. Unplug the coil power assembly from the midplane board (Figure 52 (page 71)).

Figure 52 Unplugging the coil power assembly

1. Extend the server blades.
2. Remove the server blade airflow baffle from inside the enclosure (Figure 53 (page 71)).

Figure 53 Removing the server blade airflow baffle

1. Unplug the power cable from the server blade midplane (1, Figure 54 (page 71)), and then unplug the rear UID PCA from the midplane board (2).

Figure 54 Unplugging the power cable and the UID PCA

1. Complete the following (Figure 55 (page 72)):

a. Loosen the two thumbscrews holding midplane board in place (1).
b. Pull the captive locking pin out of the midplane board (2).
c. Lift the midplane board out of the enclosure (3).

Figure 55 Removing the midplane board

Replacing the midplane board

1. On the replacement midplane board, pull out the captive locking pin as you lower the board into the enclosure (1, Figure 56 (page 72)).
2. To complete the installation of the replacement midplane board:

a. Push the captive locking pin into the midplane board (2).

b. Tighten the two thumbscrews holding the midplane board in place (3).

Figure 56 Installing the midplane board

1. Plug the rear UID PCA into the midplane board.
2. Plug the power cable into the server blade midplane.
3. Partially insert the drive drawer.
4. Plug the coil power plug into the midplane board.
5. Reattach the coil power plug bracket.
6. Reinsert the server blade airflow baffles.
7. Reinstall the server interposer board, see "Replacing the server interposer board" (page 69).

8. Push the hard drive drawer back into the enclosure.

9. Replace the top back panel.

10. Reinsert all rear components in the enclosure.

11. Replace the enclosure in the rack as described in "Inserting the system enclosure into the rack" (page 68).

Removing and replacing a SAS cable

△ CAUTION: Remove only one cable at a time to prevent downtime.

IMPORTANT: Check the QuickSpecs for the device before you purchase and connect SAS cab to ensure that the cables do not exceed the maximum supported length. Only specific cable le were tested and approved for use with external disk enclosures.

Ensure that cabling in the back of the rack system does not interfere with system operation or maintenance. Bind cables loosely with cable ties and route the excess out of the way, along its side of the rack. When cables are tied together and routed down the side of the rack, system components and indicators are easily visible and accessible.

Removing a SAS cable

Remove the SAS cable that connects the system SAS I/O module to the disk enclosure.

Replacing a SAS cable

1. Connect the SAS cable between the system SAS I/O module and the disk enclosure.
2. Verify that the replacement SAS cable is working properly by checking the associated LED status on the SAS I/O module.
3. Confirm that the system has resumed normal operations.

Removing and replacing the SAS I/O module

Removing the SAS I/O module

1. Verify the failed component as described in "Verifying component failure" (page 66).
2. Label the cables so they can be returned to their original locations.
3. Unplug all cables from the SAS I/O module.
   IMPORTANT: The SAS I/O cables must be installed in the same slots from which they are removed or the system might fail.

4. Pull up on the SAS I/O module release button (1, Figure 57 (page 74)).

5. Push down on the SAS I/O module lever (2, Figure 57 (page 74)), and then remove the failed SAS I/O module (3, Figure 57 (page 74)).

NOTE: You may need to use significant force to accomplish this task.

Figure 57 Removing the SAS I/O module

Replacing the SAS I/O module

1. To install the replacement SAS I/O module (Figure 58 (page 74)):

a. Insert the SAS I/O module into the enclosure (1).

b. Push up on the SAS I/O module lever (2) until it locks into place.

NOTE: You may need to use significant force to accomplish this task.

Figure 58 Replacing the SAS I/O module

1. Plug in all cables to the SAS I/O module.

IMPORTANT: You must install the SAS I/O cables in the same slots from which they were removed or the system might fail.

1. Verify that the replacement SAS I/O module is working properly by checking the overall module status LED ("SAS I/O module LEDs status" (page 41)).

NOTE: The green overall module status LED should turn on within five seconds after the new module is inserted in the system, which reflects the necessary time to boot the firmware.

1. Confirm the firmware version.
2. Confirm that the system has resumed normal operations.

Removing and replacing the fan module

There are two fan modules: one server fan module, which cools the server half of the enclosure and one hard drive fan module, which cools the drive half of the enclosure. The two fan mod are not redundant for each other.

△ CAUTION: You must replace the server fan module within three minutes or a therm of the system may occur. The total time allowance is three minutes for replacing the fan module, which includes the removal of the original server fan module and installation of the replacement fan.

Removing a fan module significantly changes the air flow within the enclosure. Both fan modules must be installed for the enclosure to cool properly. The fan modules are not redundant to each other, and each module cools a different half of the enclosure. If a single fan module fails, let it in place in the enclosure until a new fan is available to install. The fan modules have some redundancy to keep operating until a replacement can be made. The remaining fan module sp up and allows operation for a limited time, based on operating and environmental conditions. a temperature threshold is exceeded, the enclosure automatically shuts down.

1. Verify the failed component as described in "Verifying component failure" (page 66).
2. Press up on the drive fan module release lever (1, Figure 59 (page 75)) and remove the fan module (2).

Figure 59 Removing the fan module

1. Verify that the replacement component is working properly by checking the associated LED status.

NOTE: It should take approximately 15 seconds for the LED status to appear.

1. Confirm that the system has resumed normal operations.

Removing and replacing the power UID button assembly

Removing the power UID button assembly

1. Power off the system as described in "Powering the storage system off and on" (page 60).
2. Remove the enclosure from the rack as described in "Removing the system enclosure from the rack" (page 67).
3. Remove the top back panel by pressing the panel release button and lifting the latch to slide the top back panel off.
4. Remove the hard drive fan module (Figure 61 (page 76)).

Figure 61 Removing the fan module

1. Complete the following (Figure 62 (page 77)):

a. Unplug the cable from the power UID button assembly (1).
b. Remove the screw from the power UID button assembly (2).
c. Remove the faulty power UID button assembly (3).

Figure 62 Removing the power UID button assembly

Replacing the power UID button assembly

1. Complete the following (Figure 63 (page 77)):

a. Insert the replacement power UID button assembly (1).
b. Replace the screw in the power UID button assembly (2).
c. Plug the cable into the power UID button assembly (3).

Figure 63 Replacing the power UID button assembly

1. Push the hard drive drawer back in the system enclosure.
2. Replace the hard drive fan module.
3. Replace the top back panel.
4. Replace the enclosure as described in "Inserting the system enclosure into the rack" (page 68).

Removing and replacing the power supply

Removing the power supply

1. Verify the failed component as described in "Verifying component failure" (page 66).
2. Remove the power cord from the power supply.
3. Press the power supply release lever to the left.
4. Remove the failed power supply.

Replacing the power supply

1. Insert the replacement power supply.
2. Plug the power cord into the power supply.
3. Verify that the replacement component is working properly by checking the associated LED status.
4. Confirm that the system has resumed normal operations.

Removing and replacing the HP Ethernet I/O module

Removing the HP Ethernet I/O module

1. Verify the failed component as described in "Verifying component failure" (page 66).
2. Label the cables, and then unplug all cables from the HP Ethernet I/O module.
3. Press the module release mechanism to the right (1, Figure 64 (page 78)), and then remove the failed module (2).

Figure 64 Removing the HP Ethernet I/O module

Replacing the HP Ethernet I/O module

1. Insert the replacement HP Ethernet I/O module (Figure 65 (page 78)).

Figure 65 Replacing the HP Ethernet I/O module

1. Plug in all cables to the replacement module to their original locations.

2. Verify that the replacement component is working properly by checking the associated LED status.

NOTE: It should take approximately 15 seconds for the LED status to display.

1. Confirm the firmware version.

2. Confirm that the system has resumed normal operations.

Removing and replacing the PCIe module (with card)

Removing the PCIe module

1. Verify the failed component as described in "Verifying component failure" (page 66).
2. Use the System Manager to identify which server needs to have the PCIe module removed. it is for both servers, then perform this operation for one server, then the other server, so both servers are not turned off at the same time.
3. Power off the appropriate server blade associated with the PCIe module that is being removed. Server 1 is the top server, and the PCIe module is on the left when looking from the back. Server 2 is the bottom server, and the PCIe module is on the right when looking from the back.

CAUTION: Be sure to power off the server before removing the PCIe module.

1. Label the cables so they can be returned to their original locations.
2. Unplug all cables from the PCIe module.
3. Press the PCIe module release mechanism to release the handle (1, Figure 66 (page 79)), and then pull the handle to remove the PCIe module from the system (2).

Figure 66 Removing the PCIe module

1. Complete the following (Figure 67 (page 80)):

a. Remove the two screws from the bracket of the failed PCIe module (1).
b. Remove the bracket (2).
c. Remove the PCIe card from the failed module (3).

Figure 67 Removing the PCIe card

Replacing the PCIe module

1. Install the PCIe card in the replacement module (1, Figure 68 (page 80)), replace the bracket (2), and then reinsert the two screws into the bracket of the replacement module (3).

Figure 68 Installing the PCIe card

1. Insert the replacement PCIe module into the system (1, Figure 69 (page 81)), and lock the release lever (2).

NOTE: The PCIe module should be inserted with the lever in the open position.

Figure 69 Installing the PCIe module

1. Plug in all cables to the PCIe module in their original locations.
2. Power on the server blade by pressing the power button ON.
3. Verify that the replacement component is working properly by checking the associated LED status.
4. Confirm that the system has resumed normal operations.

Removing and replacing the EMU module

Removing the EMU module

1. Verify the failed component as described in "Verifying component failure" (page 66).
2. Unplug any cables from the EMU module.
3. Press the EMU module release lever to the right (1, Figure 70 (page 81)), and then remove the EMU module (2).

Figure 70 Removing the EMU

Replacing the EMU module

1. Insert the replacement EMU module and ensure the release lever locks in place (Figure 71 (page 82)).

Figure 71 Installing the EMU

1. Plug the cables back into the EMU module.
2. Verify that the new component is working properly by checking the associated LED status.
3. Confirm the firmware version.
4. Obtain an IP address.

IMPORTANT: Some of the configuration information is automatically repopulated, but you must reconfigure the network settings and password.

1. Confirm that the system has resumed normal operations.

NOTE: This may take approximately one minute, or the time it takes for the Enclosure Manager to boot.

Removing and replacing the server blade backplane

Removing the server blade backplane

1. Verify the failed component as described in "Verifying component failure" (page 66).
2. Power off the system as described in "Powering the storage system off and on" (page 60).
3. Remove the enclosure from the rack as described in "Removing the system enclosure from the rack" (page 67).
4. Remove the top back panel by pressing the panel release button and lifting the latch to slide the top back panel off.
5. Remove the midplane board as described in "Removing the midplane board" (page 70).
6. Remove the small baffle from beside the server blade backplane by pinching the tabs and lifting the small baffle out of the enclosure.

7. Remove the large baffle from the bottom of the enclosure.

8. Complete the following (Figure 72 (page 83)):

a. Unplug the power cable from the server blade backplane by pinching the plug release mechanism (1).
b. Remove the screw (2).
c. Remove the server blade backplane from the enclosure (3).

Figure 72 Removing the server blade backplane

Replacing the server blade backplane

1. Complete the following (Figure 73 (page 83)):

a. Install the replacement server blade backplane (1).
b. Replace the screw (2).
c. Plug in the power cable (3).

Figure 73 Installing the server blade backplane

1. Replace the large baffle on the bottom of the enclosure.

2. Replace the small baffle beside the server blade backplane.

3. Replace the midplane board (Figure 74 (page 84)):

a. Pull out the captive locking pin as you lower the board into the enclosure (1).
b. Push the captive locking pin into the midplane board (2).
c. Tighten the two thumbscrews holding the midplane board in place (3).

Figure 74 Installing the midplane board

1. Plug the rear UID PCA into the midplane board.
2. Replace the midplane board as described in "Replacing the midplane board" (page 72).

Removing and replacing the server airflow baffle

Removing the server airflow baffle

1. Power off the system as described in "Powering the storage system off and on" (page 60).
2. Remove the enclosure from the rack as described in "Removing the system enclosure from the rack" (page 67).
3. Remove the top back panel by pressing the release button and lifting the latch to slide the top back panel off.
4. Remove the server blade airflow baffle from inside the enclosure (Figure 75 (page 84)).

Figure 75 Removing the server blade airflow baffle

Replacing the server airflow baffle

1. Install the replacement server blade airflow baffle (Figure 76 (page 85)).

Figure 76 Installing the server blade airflow baffle

1. Reinstall the top back panel.
2. Replace the enclosure as described in "Inserting the system enclosure into the rack" (page 68).

Removing and replacing the front bezel (standard)

NOTE: Use "Removing and replacing the front bezel (full)" (page 87) if you are not able to reach all of the screws due to the position of the system in the rack.

Removing the front bezel

1. Power off the system as described in "Powering the storage system off and on" (page 60).
2. Extend the hard drive drawer (Figure 77 (page 85)):

a. Press upward on the release button on the hard drive drawer (1).
b. Pull the drawer handle down 90 degrees (2).
c. Extend the hard drive drawer (3).

Figure 77 Extending the hard drive drawer

1. Remove all eight screws from the front bezel (1, Figure 78 (page 86)), and then lift the front bezel up and out to remove the front bezel (2).

NOTE: There are two screws on the bottom, four screws on the sides (two on each side), and two screws hidden behind the handle.

Figure 78 Removing the front bezel

Replacing the front bezel

1. Install the replacement front bezel with the handle at a 90 degree angle making sure the bottom pins are aligned with the bottom holes (1, Figure 79 (page 86)), and replace the screws into the front bezel (2).

NOTE: There are two screws on the bottom, four screws on the sides (two on each side), and two screws hidden behind the handle.

Figure 79 Replacing the front bezel

1. Push the drive drawer back into the system enclosure.

2. Power on the system by pressing the power button ON.

3. Verify that the replacement component is working properly by checking the associated LED status.

4. Confirm that the system has resumed normal operations.

Removing and replacing the front bezel (full)

NOTE: This full procedure is only required if all screws are not accessible due to the position of the system in the rack.

Removing the front bezel (full)

1. Power off the system as described in "Powering the storage system off and on" (page 60).
2. Remove the enclosure from the rack as described in "Removing the system enclosure from the rack" (page 67).
3. Pull the hard drive handle down 90 degrees, and slide out the hard drive drawer.
4. Remove all eight screws from the front bezel and pull the handle down 90 degrees (1, Figure 80 (page 87)). Then lift the front bezel up and out to remove the front bezel (2).

NOTE: There are two screws on the bottom, four screws on the sides (two on each side), and two screws hidden behind the handle.

Figure 80 Removing the front bezel

Replacing the front bezel (full)

1. Install the replacement front bezel with the handle at a 90 degree angle, making sure the bottom pins are aligned with the bottom holes (1, Figure 81 (page 88)), and replace the screws in the front bezel (2).

NOTE: There are two screws on the bottom, four screws on the sides (two on each side), and two screws hidden behind the handle.

Figure 81 Replacing the front bezel

1. Close the drive handle.
2. Push the drive drawer back into the system enclosure.
3. Replace the enclosure as described in "Inserting the system enclosure into the rack" (page 68).

Removing and replacing the front LED display board in the rack (standard

NOTE: If you are not able to access all of the screws due to the enclosure position in the rack, use the full procedure instructions.

Removing the front LED display board in the rack

1. Verify the failed component as described in "Verifying component failure" (page 66).
2. Power off the system as described in "Powering the storage system off and on" (page 60).

3. Remove the front bezel as described in "Replacing the front bezel" (page 86).

4. Complete the following (Figure 82 (page 89)):

a. Disconnect the LED display board from the drive backplane by pinching the ends of the LED display board cable together (1).
b. Remove the four screws from the LED display board (2).
c. Remove the LED display board from the drive drawer (3).

Figure 82 Removing the front LED display board

Replacing the front LED display board in the rack

1. Complete the following (Figure 83 (page 89)):

a. Install the replacement LED display board (1).
b. Replace the four LED display board screws (2).
c. Reconnect the LED display board to the drive drawer (3).

Figure 83 Installing the front LED display board

1. Replace the front bezel as described in "Replacing the front bezel" (page 86).

Removing and replacing the front LED display board (full)

Removing the front LED display board (full)

1. Verify the failed component as described in "Verifying component failure" (page 66).
2. Power off the system as described in "Powering the storage system off and on" (page 60).

3. Remove the enclosure as described in "Removing the system enclosure from the rack" (page 67).

4. Pull the hard drive drawer handle down 90 degrees, and slide out the hard drive drawer.

5. Remove all eight screws from front bezel (1, Figure 84 (page 90)). Then, lift the front bezel up and out to remove the front bezel (2).

NOTE: There are two screws on the bottom, four screws on the sides (two on each side), and two screws hidden behind the handle.

Figure 84 Removing the front bezel

1. Complete the following (Figure 85 (page 90)):

a. Disconnect the LED display board from the drive backplane by pinching the ends of the LED display board cable together (1).
b. Remove the four screws from the LED display board (2).
c. Remove the LED display board from the drive drawer (3).

Figure 85 Removing the front LED display board

Replacing the front LED display board (full)

1. Complete the following (Figure 86 (page 91)):

a. Install the replacement LED display board (1).
b. Replace the four LED display board screws (2).
c. Reconnect the LED display board to the drive drawer (3).

Figure 86 Installing the front LED display board

1. Replace the front bezel as described in "Replacing the front bezel (full)" (page 88).

Removing and replacing a drive drawer

Removing the drive drawer

1. Verify the failed component as described in "Verifying component failure" (page 66).
2. Power off the system as described in "Powering the storage system off and on" (page 60).
3. Remove the enclosure as described in "Removing the system enclosure from the rack" (page 67).
4. Remove the top back panel by pressing the panel release button and lifting the latch to slide the top back panel off.
5. Remove the hard drive fan module (Figure 87 (page 91)).

Figure 87 Removing the fan module

1. Push up on the SAS I/O module release button (1, Figure 88 (page 92)).
2. Push down on the SAS I/O module lever (2, Figure 88 (page 92)), and then remove the SAS I/O module (3).

NOTE: This step may require significant force to accomplish.

Figure 88 Removing the SAS I/O module

1. Extend the drive drawer (Figure 45 (page 67)):

a. Press upward on the release button on the hard drive drawer (1).
b. Pull the drawer handle down 90 degrees (2).
c. Extend the hard drive drawer (3).

Figure 89 Extending the hard drive drawer

NOTE: You must repeat Step 8 for the remaining SAS I/O module.

1. Remove the plug bracket (2, Figure 90 (page 93)) from the coil power plug by removing the thumbscrew (1).

Figure 90 Removing the plug bracket from the coil power plug

1. Unplug the coil power assembly from the midplane board (Figure 91 (page 93)).

Figure 91 Unplugging the coil power assembly

1. Press the release mechanism on the side rail (1, Figure 92 (page 93)), and then pull the hard drive drawer fully out of the enclosure (2).

WARNING! The hard drive drawer is heavy, even after removing the hard drives. Make sure the drawer is fully supported as you remove it from the enclosure.

Figure 92 Removing the drive drawer

Replacing the drive drawer

1. Unlock the side enclosure rail and push it into the back enclosure (Figure 93 (page 94)).

2. Align the bottom replacement drive drawer rails with the bottom enclosure rails.

Figure 93 Unlocking the enclosure rails

1. Align the side rails and then push the replacement drive drawer partially back into the system enclosure until approximately two inches of the drawer is still out of the enclosure (Figure 94 (page 94)).

CAUTION: Do not push the drive drawer completely into the enclosure. You must first connect the power coil assembly to prevent damaging the power coil assembly.

Figure 94 Partially installing the drive drawer

1. Pull the cable slightly out of the coil power plug and connect it to the midplane board (Figure 95 (page 95)).

Figure 95 Connecting the coil power assembly to the midplane board

1. Reattach the plug bracket (1, Figure 96 (page 95)) to the coil power plug and tighten the thumbscrew (2).

Figure 96 Reattaching the plug bracket to the coil power plug

1. Push the drive drawer fully back into the system enclosure (1, Figure 97 (page 96)) and the handle back into place (2).

Figure 97 Pushing the drive drawer into the system enclosure

1. Replace the top back panel.
2. Replace the drive fan module.
3. Replace both SAS I/O modules.
4. Replace the enclosure as described in "Inserting the system enclosure into the rack" (page 68).

Removing and replacing the drive drawer hard drive

△ CAUTION:

• Do not replace the hard drive with a SATA drive. Be sure to replace the hard drive only with an approved SAS drive.
• Do not replace the drive drawer hard drive during peak data transfer times. Make sure the hard drive LED is off before you remove the hard drive.
• Ensure that the capacity of the replacement drive is at least equal to the capacity of the original drive. The capacity of the replacement drive should not be smaller.

NOTE: After replacing the hard drives, the approximate wait times for viewable disk LED activity vary.

Removing the drive drawer hard drive

1. Verify the failed component as described in "Verifying component failure" (page 66).

2. Extend the hard drive drawer (Figure 98 (page 97)):

a. Press upward on the release button on the hard drive drawer (1).
b. Pull the drawer handle down 90 degrees (2).
c. Extend the hard drive drawer (3).

Figure 98 Extending the hard drive drawer

1. Locate the failed hard drive.

NOTE: Use the hard drive bay labels and the drive LED status (an amber LED or no LED to help identify the failed drive.

1. To remove the failed hard drive (Figure 99 (page 97)):

a. Press the release button (1).
b. Pull the release lever (2).
c. Remove the hard drive (3).

Figure 99 Remove the failed hard drive

Replacing the drive drawer hard drive

1. Install the hard drive (Figure 100 (page 98)):

a. Insert the replacement hard drive with the lever in the open position (1). b. Push the release lever into place (2).

Figure 100 Installing the hard drive

1. Push the drive drawer back into the system enclosure.

2. Verify that the replacement component is working properly by checking the associated LED status.

NOTE: This may require a wait time of less than 15 seconds for the LED status to appear.

1. Confirm that the system has resumed normal operations.

2. Confirm the hard drive firmware version.

IMPORTANT: You must reboot the storage solution after updating the drive drawer hard drive firmware.

Removing and replacing the drive drawer rails (side or bottom)

NOTE: Spare rail kits consist of rail pairs, one side rail, and two bottom drive drawer rails. See "Removing and replacing the enclosure rails" (page 103) for enclosure rail instructions.

Removing the drive drawer rails

1. Power off the system as described in "Powering the storage system off and on" (page 60).

2. Remove the enclosure as described in "Removing the system enclosure from the rack" (page 67).

3. Remove the top back panel by pressing the panel release button and lifting the latch to slide the top back off.

4. Extend the hard drive drawer (Figure 101 (page 99)):

a. Press upward on the release button on the hard drive drawer (1).
b. Pull the drawer handle down 90 degrees (2).
c. Extend the hard drive drawer (3).

Figure 101 Extending the hard drive drawer

1. Remove the plug bracket (2, Figure 102 (page 99)) from the coil power plug by removing the thumbscrew (1).

Figure 102 Removing the plug bracket from the coil power plug

1. Unplug the coil power assembly from the midplane board (Figure 103 (page 100)).

Figure 103 Unplugging the coil power assembly

1. Press the release mechanism on the side rail (1, Figure 104 (page 100)), and then pull the hard drive drawer fully out of the enclosure (2).

WARNING! The hard drive drawer is heavy, even after removing the hard drives. Make sure the drawer is fully supported as you remove it from the enclosure.

Figure 104 Removing the drive drawer

1. Lift the release tab on the side or bottom rail (1, Figure 105 (page 101)), and then slide the rail toward the front of the drive drawer to remove the rail (2).

NOTE: Repeat this step for all rails.

Figure 105 Removing the drive drawer rails

Replacing the drive drawer rails

1. Align the replacement rail with the tabs, and slide it toward the back of the drive drawer the rail locks into place (Figure 106 (page 101)).

Figure 106 Installing the drive drawer rails

1. Align the replacement drive drawer rail with the three enclosure rails and then push the dr drawer partially back into the system enclosure so that approximately two inches of the dr is still out of the enclosure (Figure 107 (page 102)).

CAUTION: Do not push the drive drawer completely into the enclosure. You must first con the power coil assembly to prevent damaging the power coil assembly.

Figure 107 Partially installing the drive drawer

1. Pull the cable slightly out of the coil power plug and connect it to the midplane board (Figure 108 (page 102)).

Figure 108 Connecting the coil power assembly to the midplane board

1. Reattach the plug bracket (1, Figure 109 (page 103)) to the coil power plug and tighten the thumbscrew (2).

Figure 109 Reattaching the plug bracket to the coil power plug

1. Push the drive drawer fully back into the system enclosure (1, Figure 110 (page 103)) and the handle back into place (2).

Figure 110 Pushing the drive drawer into the system enclosure

1. Replace the top back panel.

2. Replace the enclosure as described in "Inserting the system enclosure into the rack" (page 68).

Removing and replacing the enclosure rails

Removing the enclosure rails

1. Power off the system as described in "Powering the storage system off and on" (page 60).

2. Remove the enclosure as described in "Removing the system enclosure from the rack" (page 67).

3. Extend the hard drive drawer (Figure 111 (page 104)):

a. Press upward on the release button on the hard drive drawer (1).
b. Pull the drawer handle down 90 degrees (2).
c. Extend the hard drive drawer (3).

Figure 111 Extending the hard drive drawer

1. Remove the plug bracket (2, Figure 112 (page 104)) from the coil power plug by removing the thumbscrew (1).

Figure 112 Removing the plug bracket from the coil power plug

1. Unplug the coil power assembly from the midplane board (Figure 113 (page 105)).

Figure 113 Unplugging the coil power assembly

1. Press the release mechanism on the side rail (1, Figure 114 (page 105)), and then pull the hard drive drawer fully out of the enclosure (2).

Figure 114 Removing the drive drawer

1. Lift the release mechanism on the rail (side or bottom) (1, Figure 115 (page 105)), and then push the rail back and up to release and remove the rail (2).

Figure 115 Removing the enclosure rails

Replacing the enclosure rails

1. Align the replacement rail, and then attach it by sliding the rail toward the front of the enclosure (Figure 116 (page 106)).

Figure 116 Installing the enclosure rails

1. Align the replacement drive drawer rail with the three enclosure rails and then push the drive drawer partially back into the system enclosure so that approximately two inches of the drawer is still out of the enclosure (Figure 117 (page 106)).

CAUTION: Do not push the drive drawer completely into the enclosure. You must first connect the power coil assembly to prevent damaging the power coil assembly.

Figure 117 Partially installing the drive drawer

1. Pull the cable slightly out of the coil power plug and connect it to the midplane board (Figure 118 (page 107)).

Figure 118 Connecting the coil power assembly to the midplane board

1. Reattach the plug bracket (1, Figure 119 (page 107)) to the coil power plug and tighten the thumbscrew (2).

Figure 119 Reattaching the plug bracket to the coil power plug

1. Push the drive drawer fully back into the system enclosure (1, Figure 120 (page 108)) and the handle back into place (2).

Figure 120 Pushing the drive drawer into the system enclosure

1. Replace the enclosure as described in "Inserting the system enclosure into the rack" (page 68).

Removing and replacing the rack rails

For detailed instructions on installing the rack rails, see the HP 3U Storage System Rail Kit Installation Instructions.

Removing and replacing server blades

Removing the server blade

CAUTION: Do not use the server blade release lever to lift or carry the server blade. Always support the weight of the server blade by handling the chassis directly. Improper use can damage the release lever and the server blade.

1. Verify the failed component as described in "Verifying component failure" (page 66).
2. Power off the appropriate server blade by clicking Start and then select Shut Down.
3. Remove the server blade (Figure 121 (page 108)):

a. Push the button to release the handle (1).
b. Pull the handle toward you (2).
c. Remove the server blade (3).

Figure 121 Removing the server blade

1. Place the server blade on a flat, level work surface.

WARNING! To reduce the risk of personal injury from hot surfaces, allow the drives and the internal system components to cool before touching them.

CAUTION: To prevent damage to electrical components, properly ground the server blade before beginning any installation procedure. Improper grounding can cause ESD damage.

Replacing the server blade

1. Install the server blade (1, Figure 122 (page 109)), and then push the handle into place with the handle open (2).

Figure 122 Replacing the server blade

1. Power on the server blade.

2. Confirm that the system has resumed normal operations.

Removing and replacing the server blade hard drive

Removing the server blade hard drive

1. Verify the failed component as described in "Verifying component failure" (page 66).

2. Back up all data on the hard drive.

3. Remove the server blade hard drive (Figure 123 (page 110)):

a. Press the release button (1).
b. Pull the release lever (2).
c. Remove the hard drive (3).

CAUTION: To prevent improper cooling and thermal damage, replace the drive quickly. Do not operate the server unless all bays are populated.

Figure 123 Removing the server blade hard drive

Replacing the server blade hard drive

1. Install the hard drive (Figure 124 (page 110)):

a. Insert the replacement hard drive with the lever in the open position (1). b. Push the release lever into place (2).

Figure 124 Installing the hard drive

1. Verify that the server blade hard drive is working properly by checking the associated LED status.

NOTE: This may require a wait time of less than 15 seconds for the LED status to appear.

1. Confirm that the system has resumed normal operations.

2. Confirm the firmware version.

NOTE: You must reboot the system after updating a server blade hard drive.

Removing and replacing the 1210m controller board components

Removing the 1210m controller card

WARNING! Wear gloves or use care when removing the capacitor pack to avoid physical inj

1. Verify the failed component as described in "Verifying component failure" (page 66).
2. Back up all data.
3. Close all applications.
4. To power off the server blade, click Start, and then select Shut down.
5. Remove the server blade (Figure 125 (page 111)):

a. Push the button to release the handle (1).
b. Pull the handle toward you (2).
c. Remove the server blade from the enclosure (3).

Figure 125 Removing the server blade

1. Press the release button on the access panel and slide the access panel to the left to remove it.

2. The original cache module is connected to a capacitor pack, so observe the cache module LEDs:

3. If the amber LED is solid, data transfer to the flash device on the cache module is in progress. Do not remove the cache module until the amber LED is off, and then conti with the next step.
   • If the amber LED is not lit, proceed to the next step.

4. Open the ejector latches (1, Figure 126 (page 111)) on each side of the cache module slot.

Typically, opening the ejector latches ejects the cache module automatically. If the module does not eject automatically after you open the ejector latches, remove the cache module by grasping only the edges.

Figure 126 Removing the cache module

1. Remove the capacitor pack (2, Figure 127 (page 112)).

The 1210m cache module (1) and the 1210m controller card (3) are also shown.

Figure 127 Removing the capacitor pack

NOTE: Be sure to first remove the capacitor pack bracket.

1. Loosen the two captive screws and remove the 1210m controller card (Figure 128 (page 112)).

Figure 128 Removing the controller card

Replacing the 1210m controller card

1. Install the cache module and capacitor in the cache module slot of the replacement control
2. Close the ejector latches on the cache module slot.
3. Install the replacement controller card (1, Figure 129 (page 113)). Press down on the connector to seat the card (2).

CAUTION: Be sure not to press on the cache module when replacing the controller card. could damage the cache module and result in errors.

Figure 129 Replacing the 1210m controller card

1. Tighten the captive screws.
2. Replace the capacitor in its cradle.
3. Install the access panel.
4. Install the server blade in the enclosure.
5. Confirm that the replacement 1210m controller is running current firmware (see "Upgrading a component's firmware" (page 56)).

NOTE: You must reboot the storage solution after updating firmware on the 1210m control because both controllers must be updated at the same time.

Removing and replacing the 1210m cache module

Removing the 1210m cache module

WARNING! Wear gloves or use care when removing the capacitor pack to avoid physical inj

△ CAUTION:

• When replacing the cache module, ensure that the replacement is compatible with the 1210m controller. Otherwise, the controller could malfunction and you could lose data.

• ESD can damage electronic components. Be sure you are properly grounded before performing this procedure.

• Back up all data.

• Close all applications.

• Power off the server blade.

• Remove the server blade (Figure 130 (page 114)):

a. Push the button to release the handle (1).
b. Pull the handle toward you (2).
c. Remove the server blade (3).

Figure 130 Removing the server blade

1. Press the release button on the access panel and slide the access panel to the left to remove it.
2. The original 1210m cache module is connected to a capacitor pack, so observe the cache module LEDs:

- If the amber 1210m cache LED is solid, data transfer to the flash device on the cache is in progress. Do not remove the 1210m cache until the amber LED is off, and then continue with the next step.

- If the amber 1210m cache LED is not lit, proceed to the next step.

1. Open the ejector latches (1, Figure 131 (page 114)) on each side of the 1210m cache module slot.

Typically, opening the ejector latches ejects the cache module automatically. If the module does not eject automatically after you open the ejector latches, remove the cache module (2) by grasping only the edges.

Figure 131 Removing the cache module

1. Remove the capacitor pack (2, Figure 132 (page 115)).

The 1210m cache module (1), and the 1210m controller card (3) are also shown.

Figure 132 Removing the cache module and the capacitor pack

NOTE: Be sure to first remove the capacitor pack bracket.

1. Disconnect the capacitor pack cable from the connector on the top of the cache module (Figure 133 (page 115)).

Figure 133 Disconnecting the capacitor pack cable

Replacing the cache module

1. Connect the capacitor pack cable to the replacement cache module.

2. Complete the following (Figure 134 (page 116)):

a. Install the replacement cache module in the cache module slot (1). b. Close the ejector latches on the cache module slot (2).

Figure 134 Replacing the cache module

1. Install the capacitor pack bracket and insert the capacitor pack on the chassis wall.
2. Install the access panel.
3. Install the server blade into the enclosure.

Removing and replacing the capacitor pack

Removing the capacitor pack

WARNING! Wear gloves or use care when removing the capacitor pack to avoid physical injury.

CAUTION: ESD can damage electronic components. Be sure you are properly grounded before performing this procedure.

1. Back up all data.
2. Close all applications.
3. Power off the server blade.
4. Remove the server blade (Figure 135 (page 116)):
   a. Push the button to release the handle (1).
   b. Pull the handle toward you (2).
   c. Remove the server blade (3).

Figure 135 Removing the server blade

1. Press the release button on the access panel and slide the access panel to the left to remove it.

2. The original capacitor pack is connected to a cache module, so observe the cache module LEDs:

- If the amber cache LED is solid, data transfer to the flash device on the cache is in progress. Do not remove the cache until the amber LED is off, and then continue with the next - If the amber cache LED is not lit, proceed to the next step.

1. Open the ejector latches (1, Figure 136 (page 117)) on each side of the cache module slot.

Typically, opening the ejector latches ejects the cache module automatically. If the module does not eject automatically after you open the ejector latches, remove the cache module by grasping only the edges.

Figure 136 Removing the cache module

1. Remove the cache module (1, Figure 137 (page 117)) from the controller card (3) and the capacitor pack (2) from the server blade.

Figure 137 Removing the cache module and the capacitor pack

NOTE: Be sure to first remove the capacitor pack bracket.

1. Disconnect the capacitor pack cable on the top of the cache module (Figure 138 (page 118)).

Figure 138 Disconnecting the capacitor cable from the module

Replacing the capacitor pack

1. Connect the replacement capacitor pack to the cache module.
2. Install the cache module in the cache module slot.
3. Install the cache module on the controller, and then close the ejector latches on the cache module slot.
4. Install the capacitor pack bracket and insert the replacement capacitor pack on the chassis wall.
5. Install the access panel.
6. Install the server blade in the enclosure.

IMPORTANT: After installing a capacitor pack, you might see a POST message during reboot indicating that the array accelerator (cache) is disabled temporarily. This behavior is normal because the new capacitor pack is likely to have a low charge.

The controller operates properly while the capacitor pack is recharging, although the performance advantage of the array accelerator is absent. You do not need to take any action because the recharge process begins automatically when you install the capacitor pack. When the capacitor pack has been charged to a predetermined level, the array accelerator is enabled automatically.

Removing and replacing the Mezzanine NIC

Removing the Mezzanine NIC

1. Back up all data.
2. Close all applications.

3. To power off the server blade, click Start and then select Shut down. Verify the server blade is shut down before continuing.

4. Remove the server blade (Figure 139 (page 119)):

a. Push the button to release the handle (1).
b. Pull the handle toward you (2).
c. Remove the server blade (3).

Figure 139 Removing the server blade

1. Press the release button on the access panel and slide the access panel to the left to it. T Mezzanine NIC is under the controller card.
2. The 1210m cache module is connected to a capacitor pack, so observe the cache module LEDs (Figure 27 (page 37)):

- If the amber LED is solid, data transfer to the flash device on the cache module is in progress. Do not remove the controller card until the amber LED is off, and then cont with the next step.

- If the amber LED is not lit, proceed to the next step.

1. Loosen the three captive screws and remove the Mezzanine NIC.

Replacing the Mezzanine NIC

To replace the Mezzanine NIC:

1. Install the Mezzanine NIC, press down on the connector to seat the board (1, Figure 140 (page 119)), and then tighten the captive screws (2).

Figure 140 Installing the Mezzanine NIC

1. Reinstall the controller card, and then install the access panel.
2. Install the server blade in the enclosure. If necessary, power on the blade by pressing the power button on the front of the server blade.
3. Confirm the firmware version.

NOTE: You must reboot the storage solution after updating the Mezzanine NIC and server blade firmware.

7 Storage system recovery

This chapter describes how to perform a system recovery. To restore the X5000 G2 to the factory defaults, see "Restoring the factory image with a DVD or USB flash device" (page 121). To restore the X5000 G2 using Windows Recovery Environment, see "Restoring the system with Windows Recovery Environment" (page 125).

System Recovery DVD

The X5000 G2 System Recovery DVD enables you to install an image or recover from a catastrophe failure.

At any time, you may boot from the DVD and restore the server to the factory condition. This en you to recover the system if all other means to boot the server fail.

While the recovery process makes every attempt to preserve the existing data volumes, you should have a backup of your data before recovering the system.

IMPORTANT: All data on the original OS logical drive is erased during the recovery process.

During system recovery, you can replace the existing drives with drives of the same size or larger HP recommends that the replacement drives be the same type as the original drives, but it is not required. However, drives in the same RAID group must all be the same type (you cannot mix dr types in a RAID group).

If you replace any disk drives and then perform a system recovery, you must ensure that the replacement drives do not contain a logical drive. Use the Option ROM Configuration for Arrays (ORCA) utility to delete logical drives. For more information about ORCA, see the Configuring Arrays on HP Smart Array Controllers Reference Guide, which is available at:

http://www.hp.com/support/manuals

Under servers, select Server Management and then select HP Smart Array Advanced Pack Software under Server Management Software.

Using a downloaded version of the System Recovery DVD

If you have downloaded the System Recovery DVD image from the HP website and the version is newer than the DVD shipped with the product, you must verify that the firmware versions of all hardware components are current after completing the system recovery. The firmware for each hardware component is not automatically updated to the latest version after a system recovery.

IMPORTANT: Do not complete any tasks in the Initial Configuration Tasks window until you verify the firmware versions.

To verify the firmware versions, complete the following steps on each node:

1. Open Server Manager using one of the following methods:

- Click the Server Manager icon on the task bar.

- Select Start→Administrative Tools→Server Manager.

1. In the left navigation pane, select System Manager and then select the Firmware tab.

2. Review information on the Firmware tab to determine if any firmware upgrades are required. If so, follow the instructions on the Firmware tab to complete the firmware upgrades.

NOTE: For more information, see "Upgrading a component's firmware" (page 56).

1. Once the firmware upgrades are complete, open the Initial Configuration Tasks window to set up the cluster.

Drive letters are not assigned after a restore

When a system that has existing data volumes (non-operating system volumes) is restored using the System Recovery DVD, the data volumes will not have drive letters assigned to them. This design. The volume labels are retained and can be used to identify the data volumes.

You can assign drive letters to volumes using diskpart.exe or Disk Management.

To use Disk Management:

1. Click Start→Run.

The Run dialog box opens.

1. Enter diskmgmt.msc and click OK.

The Disk Management window opens.

1. Right-click the disk and partition the one for which you want to assign a drive letter and s Change Drive Letter and Paths.

Restoring the factory image with a DVD or USB flash device

1. Do one of the following:

a. For direct access, attach the SUV cable (supplied with the System) to the port on the f of the server blade you want to recover. Connect a monitor and USB mouse to the S cable. Using the remaining USB connector on the SUV cable, connect either a USB D drive (and insert the System Recovery DVD) or a bootable USB flash device (prepared with a System Recovery image).

b. For remote management access, connect to the server using iLO from a client PC. Insert the System Recovery DVD in the client PC or attach a bootable USB flash device that been prepared with a System Recovery image.

1. Reboot the server blade to either the USB flash device or USB DVD drive.

The system BIOS attempts to boot to the USB device first by default. Watch the monitor c during the boot as you may need to press a key to boot to the USB media.

NOTE: If directly connected, you may have to change the BIOS settings to ensure proper boot sequence. If connected remotely, you may have to change some iLO settings to ensure proper boot sequence.

1. Click Restore Factory Image.

The recovery process completes with minimal user intervention required. The server automatic reboots more than once.

IMPORTANT: Do not interrupt the recovery process.

When the recovery process completes, the Set Up Windows wizard appears. The next step depend on whether you are recovering both server blades (see "Recovering both servers" (page 122)) or recovering a single blade (see "Recovering a single server" (page 122)).

1. Remove the directly connected DVD or flash device (or remotely connected iLO virtual DVD or flash device) from the server.

Using a USB flash drive for storage system recovery

Creating a System Recovery USB flash drive is supported on Windows Vista, Windows 7, Wir Storage Server 2008, and Windows Storage Server 2008 R2 operating systems only.

If you create a backup copy of the System Recovery DVD using a USB flash drive, you can use it to restore the system.

To create a system recovery USB flash drive:

1. Obtain a blank 4 GB or larger USB flash drive.

2. Insert the USB flash device into your workstation or laptop.

3. Open an elevated command prompt with Administrator privileges.
4. At the command prompt, enter diskpart.
5. At the diskpart prompt, enter list disk.
6. Identify the disk number that corresponds to the flash drive. This is typically the last disk listed
7. Enter sel disk (for example, sel disk 4).
8. Enter clean. This deletes everything from the USB flash device, so ensure that you have the proper disk selected.
9. Enter create par primary.
10. Enter sel par 1.
11. Enter format fs=fat32 quick.

NOTE: If your USB flash drive does not support the FAT32 file system, format the drive as NTFS instead. Omitting the quick parameter lengthens the format time considerably.

1. Enter active to mark the partition as active.
2. Enter assign letter= to assign a drive letter to the USB drive (for example, assign letter=U).
3. Enter exit to quit diskpart context commands.
4. Insert the System Recovery DVD into the computer.
5. Using Windows Explorer or a comparable utility, open the DVD so that all contents are visible, including hidden and system files.
6. Select all of the files (including bootmgr) on the DVD.
7. Copy all of the selected files to the root of the USB flash drive.

Recovering both servers

If both server blades are being recovered, the process is similar to configuring a new HP X5000 G2 Network Storage System delivered from the factory.

NOTE: Although the recovery process restores the X5000 G2 to the factory version, it does not restore the EMU and iLO address configuration to the factory defaults. The EMU and iLO address configuration will be the same as it was prior to system recovery.

For each server, follow the steps in "Restoring the factory image with a DVD or USB flash device" (page 121). Once each server is displaying the Set Up Windows wizard, see "Set up Windows and discover the second node" (page 19), and follow the steps provided. When you run the Create Witness Disk wizard as part of the Initial Configuration Tasks, the wizard may indicate that a witness disk already exists and it may discover other LUNs on the shared storage as well. These LUNs will likely be from a previous cluster on the X5000 G2. Decide if you want to keep these LUNs and add them to the new cluster later. If you do not want to keep the existing LUNs, you may select them for deletion in the Create Witness Disk wizard.

Recovering a single server

If only one of the two server blades is being recovered, the process is slightly more involved because you want to join the recovered server to an existing Windows failover cluster. If you do not have a functional (containing at least one node) Windows failover cluster, follow the procedure for "Recovering both servers" (page 122).

The following procedure describes how to re-image one of the server blades of the X5000 G2, and then rejoin the server to the Windows failover cluster:

1. Follow the steps in "Restoring the factory image with a DVD or USB flash device" (page 121).

2. When the Set Up Windows wizard appears, select your desired language, regional settings keyboard layout, and accept the EULA. After completing the wizard, an attempt is made to discover the second node. The attempt fails and the following error message displays.

Figure 141 Error message during second node discovery

1. Click Cancel. A pop-up window displays with the following message:

Do you want to ignore the second node? If so, you must run the wizard manually later to configure the second node.

Click Yes.

The installation continues and eventually the server reboots. After the reboot, Windows automatically logs on as the local Administrator, and launches the Initial Configuration Task (ICT) window. However, you will not be using the ICT to configure the node.

1. Check the Do not show this window at next logon box in the lower left corner of the window, and close the ICT window. There will be messages warning about inconsistencies between the nodes. Confirm that you wish to close the ICT.

2. Change the password for the local administrator account by pressing CTRL+ALT+DELETE. (If you are using an iLO remote console, you must select the CTRL-ALT-DEL item from the Keyboard menu.) Select Change a password. Enter the old password, which is HPinvent!, then enter a new password.

3. Select the time and date shown in the lower right corner of the task bar. Click the Change date and time settings link. Set the time zone of the server to be the same time zone other X5520 server and the domain controller. Adjust the time of day, if needed.

4. Windows Server Manager opens when the ICT window is closed. If it is not open, launch from the shortcut on the task bar to the right of the Windows Start button.

As shown in Figure 142 (page 124), click Change System Properties, and then click Change on the Computer Name tab. Enter a new Computer name for the node, and select the Radio button to provide the Active Directory domain name to which the server will be joined. This must be the same domain that contains the existing one node cluster. You are prompt for the credentials of a domain account that has permissions to add a computer to the data. After the changes have been made, accept the prompt to restart the server.

Figure 142 Changing the computer name/domain

1. After the server has rebooted, log on as the local administrator. To manage the server as a cluster member in the future, use at least one domain user as a member of the local administrators group. In Server Manager, select Configuration→Local Users and Groups to add any domain users to the Administrators group.

2. In Server Manager, select System Manager. As shown in Figure 143 (page 125), select Generate keys to authenticate with the EM. When prompted, enter the Administrator password for the Enclosure Manager. In the X5520 Enclosure Settings window, click the Generate Keys... button to generate a key pair that will allow software on the server blade to communicate with the Enclosure Manager. After generating the key, close the window.

Figure 143 Generating keys

1. Remove the failed node from the cluster (also called evicting the node) before you add the newly recovered node to the cluster. See the following Microsoft article for more information http://technet.microsoft.com/en-us/library/cc784955(v=WS.10).aspx
2. To add the recovered server blade to the cluster, log on to the other server (the server the part of the existing one node cluster) as a domain user. Do not use the Initial Configurati Tasks (ICT) window. Follow the instructions at the following website to add the recovered server to the cluster:

http://technet.microsoft.com/en-us/library/cc730998.aspx

Restoring the system with Windows Recovery Environment

NOTE: To use Windows Recovery Environment, you must have created a system backup with the Windows Server Backup utility.

1. Do one of the following:

a. For direct access, attach the SUV cable (supplied with the HP X5000 G2 Network Storage System) to the port on the front of the server blade you want to recover. Connect a monitor and USB mouse to the SUV cable. Using the remaining USB connector on the SUV cable, connect either a USB DVD drive (and insert the System Recovery DVD) or a bootable USB flash device (prepared with a System Recovery image).
b. For remote management access, connect to the server using iLO from a client PC. Insert the System Recovery DVD in the client PC or attach a bootable USB flash device that been prepared with a System Recovery image.

1. Reboot the server blade to either the USB flash device or USB DVD drive.

The system BIOS attempts to boot to the USB device first by default. Watch the monitor output during the boot as you may need to press a key to boot to the USB media.

NOTE: If directly connected, you may have to change the BIOS settings to ensure proper boot sequence. If connected remotely, you may have to change some iLO settings to ensure proper boot sequence.

1. Select Windows Recovery Environment.

The recovery environment is loaded.

1. Once the recovery environment is loaded, the System Recovery Options wizard opens. On the first window, select the keyboard input method, which is based on your location (for example, select US for United States) and click Next.

2. Select one of the following options and click Next:

- Use recovery tools that can help fix problems starting Windows. Select an operating system to repair. If you select this option, then select the active partition from which to perform a scan and complete the recovery. Continue with step 8.

- Restore your computer using a system image that you created earlier. Select this option to completely delete the operating system drives from the RAID controller, reconfigure the storage, and recover using a backup image. Continue with step 6.

1. The System Recovery Options wizard scans the computer for a system image. If it is unable to locate a system image, the following message is displayed:

Figure 144 System image not found

Either attach an external drive or insert a DVD that contains the backup files and click Retry. If you want to recover from the network, click Cancel.

1. Select one of the following options and click Next:

- Use the latest available image. Select this option to use the backup image that was recently created. If you are restoring from the network, this option is grayed out.

- Select a system image. Select this option to choose a different image to restore from or will allow you to restore from the network.

1. Select the backup image from which you want to restore the system and click Next.

2. If you are restoring from the network, click Advanced and then select Search for a system image on the network:

a. The utility automatically connects to an existing network (DHCP enabled).

b. Once connected to the network, enter the directory where the system image is located on the network and click Next.

1. Select the disks to which you want to restore data and click Next.

2. The summary window opens. Verify the information is correct and click Next to start the recovery process.

IMPORTANT: Do not interrupt the recovery process.

1. Remove the directly connected DVD or flash device (or remotely connected iLO virtual DVD or flash device) from the server.

8 Support and other resources

Contacting HP

HP technical support

For worldwide technical support information, see the HP support website: http://www.hp.com/support

Before contacting HP, collect the following information:

•Product model names and numbers
•Technical support registration number (if applicable)
•Product serial numbers
- Error messages
- Operating system type and revision level
•Detailed questions

Subscription service

HP recommends that you register your product at the Subscriber's Choice for Business website: http://www.hp.com/go/e-updates

After registering, you receive email notification of product enhancements, new driver versions, firmware updates, and other product resources.

Related information

The following documents provide related information:

•HP X5000 G2 Network Storage System Quick Start Guide
•HP 3U Storage System Rail Kit Installation Instructions
•HP X5000 G2 Network Storage System Release Notes

To locate the storage system documents, go to http://www.hp.com/go/X5000-G2, and then click the support link.

You can also find these documents from the Manuals page of the HP Business Support Center website:

http://www.hp.com/support/manuals

HP websites

For additional HP information, see the following HP websites:

• http://www.hp.com
• http://www.hp.com/go/storage
• http://www.hp.com/go/hpsim
• http://www.hp.com/service_locator
• http://www.hp.com/support/manuals
• http://www.hp.com/support/downloads
• http://www.hp.com/storage/whitepapers

Rack stability

Rack stability protects personnel and equipment.

!

WARNING! To reduce the risk of personal injury or damage to equipment:

• Extend leveling jacks to the floor.
• Ensure that the full weight of the rack rests on the leveling jacks.
  • Install stabilizing feet on the rack.
• In multiple-rack installations, fasten racks together securely.
• Extend only one rack component at a time. Racks can become unstable if more than one component is extended.

9 Documentation feedback

HP is committed to providing documentation that meets your needs. To help us improve the documentation, send any errors, suggestions, or comments to Documentation Feedback ([e-mail]). Include the document title and part number, version number, or the URL when submitting your feedback.

A Managing the EMU

This chapter describes how to manage the EMU using the CLI or the Enclosure Manager physi interface.

CLI reference

The CLI is the primary interface for managing the Enclosure Manager and is accessed via sec shell protocol over the LAN. Using the CLI is necessary for functions not possible through any mechanism or interface. For example, creating and setting Enclosure Manager user accounts and passwords and remotely powering the enclosure ON or OFF can be done only with the CLI.

Command line conventions

CLI input is case-insensitive except when otherwise noted. Commands are organized into a tree with approximately 30 base commands. Each of these commands can have any number of subcommands. Subcommands can also have further subcommands. Each command used in this appendix follows the conventions listed in Table 16 (page 131).

Table 16 Command line conventions

	DescriptionSymbol
< >	Denotes a variable must be substituted with a value, such as a user name. Do not include the < > symbols when entering the variable.
	Used to separate input options. |
{}	Denotes a list of mandatory choices that must be made. For example, SET ENCLOSURE UID {ON | OFF} must be in one of the following forms:SET ENCLOSURE UID ONSET ENCLOSURE UID OFF
	Denotes an optional argument or set of characters.[ ]
	Used to enclose command arguments that contain spaces." "

NOTE: All users logged into the CLI have administrator privilege. When a user account is created, the account has administrator privilege.

Operational groups

Descriptions of the CLI commands are organized by operational group instead of the parser implementation which is a tree of commands, subcommands, and sub-subcommands. The operation groups are:

• Authentication—user identity and authentication
• Time functions—Real Time Clock/Calendar control
• Role definition—access control
• Inventory and status—self explanatory
- Internet control—internal and external LAN management
• Server management—iLO dependent control of server
• Enclosure control—global control of enclosure, excluding JBOD management zone
• Forensic—global diagnostic context functions (not directed validation tests)
• Session—CLI session control

Authentication

This section defines EM authentication CLI functions.

ADD USER

Syntax

ADD USER "" [""]

Description

Adds a user to the system. If you do not provide a password, you are prompted for one. If script mode is enabled and the password is not provided, the password is assigned an unmatched string. This unmatched string requires an enclosure administrator to change the password to allow the new user to access the system.

Restrictions

- You can add a maximum of 30 users, including the reserved accounts.

- The is case-sensitive and must be unique to all other user names and group names. The user name must be 1 to 40 characters long and can include all alphanumeric characters, the hyphen, and the underscore.

- The must begin with a letter.

- The must be 3 to 40 characters long. The character set includes all printable characters. If you do not enter a password, you are prompted to enter one.

Reserved user names are: ALL (case insensitive), ADMINISTRATOR (case insensitive), switch1, switch2, switch3, switch4, switch5, switch6, switch7, switch8, daemon, ldapuser, nobody, tbmuser_, vcmuser_, root, and quire.

CLEAR SSHKEY

Syntax

CLEAR SSHKEY

Description

Disables a user account. The system immediately logs out the user and prevents the user from logging in until the account is enabled.

This command is used in the factory to disable the 'root' user account. The root user account is required to perform certain factory-only configuration and diagnostic operations when logged into the Linux shell.

Restrictions

None

DOWNLOAD SSHKEY

Syntax

DOWNLOAD SSHKEY

Description

Downloads an authorized key file to use with Secure Shell 2, which can contain the public keys for the built-in Administrator user. Supported protocols are http, ftp, and tftp. The url should be formatted as protocol://host/path/file. If your ftp server does not support anonymous connections, then you can specify a username and password by replacing the host part in the

above format with username:password@host. The authorized keys file must contain only protocol version 2 public keys. Each line of the file represents one key (empty lines and lines with # represent comments). Each protocol version 2 key consists of the following fields, separately by spaces: keytype, base64 encoded key, comment. Keytype is either ssh-rsa or ssh-dss. Downloading an SSH key file replaces all currently installed SSH keys.

Restrictions

None

ENABLE USER

Syntax

ENABLE USER

Description

Enables a user account that was previously disabled by the DISABLE USER command.

Restrictions

is case-sensitive.

REMOVE USER

Syntax

REMOVE USER {ALL | "" | CERTIFICATE ""}

Description

Removes the existing user specified by and/or any certificate mapped to this user. If the user is currently logged on, their sessions are terminated. Specifying ALL removes all users from the system except the default Administrator account. The user is prompted for confirmation except in script mode.

Restrictions

•The is case-sensitive.
- You cannot remove the Administrator user.

SET PASSWORD

Syntax

SET PASSWORD [""]

Description

Sets the password of the user who entered the command. The parameter is optional, but failure to enter a password results in the system prompting you for a password.

• Passwords must be between 3 and 40 characters in length.
• Acceptable characters include any printable character.
• This command is not valid in script mode.

Restrictions

None

SET USER PASSWORD

Syntax

SET USER PASSWORD "" [ ""]

Description

Sets a user's password. If you do not supply a password on the command line, you are prompt to enter it.

Restrictions

• Only the Administrator account can modify the password of the Administrator account.
  •The is case-sensitive.
  •The must be 3 to 40 characters long.
  •The character set includes all printable characters.
• This command is not valid in script mode.

SHOW USER

Syntax

SHOW USER [ [LIST | ""] ]

Description

Displays general user information and user rights (which is always "Admin") for this firmware version.

Restrictions

• Does not show information for restricted user accounts—only shows information for Administrator and other end-user-created accounts.
• Since there are no bay or device access restrictions, no information about bays being assigned is given.

SHOW SSHFINGERPRINT

Syntax

SHOW SSHFINGERPRINT

Description

Displays the key fingerprint of the host public key of the Enclosure Manager.

Restrictions

None

SHOW SSHKEY

Syntax

SHOW SSKEY

Description

Displays the contents of the existing ssh authorized key files (stored in NAND Flash).

Restrictions

None

ADD SSHKEY

Syntax

ADD SSHKEY

Description

Adds an SSH key on the command line. Start with a string that does not appear within the code (end marker). Next, paste in the certificate. Terminate the command with the end marker. Failure to give a proper end marker before and after the certificate may cause the interface to wait the appropriate end marker indefinitely.

Restrictions

This command is only available in script mode.

SHOW PASSWORD SETTINGS

Syntax

SHOW PASSWORD SETTINGS

Description

Displays the current minimum password length and strong password settings.

Restrictions

Time functions

Because this small group of functions is used in conjunction with other groups, it is separated its own group.

SET DATE

Syntax

SET DATE MMDDhhmm

Description

Sets the enclosure date and time and, optionally, year and time zone. Time is in a 24-hour format. If the year or time zone parameters are omitted, the current values remain in effect. The definition of the date parameters are:

MM: Month

DD: Day

hh: Hour (24-hour format)

mm: Minute

CC: Century

YY: Year

TZ: Time Zone (chosen from strings in Table 17 (page 135))

Table 17 Universal time zone settings

				MSTEtcZGMT-13Etc/GMT+7
			Etc/ZSTKIDT4Etc/GMT+8	MSTGMDT2NavajoEtc/GreenwichEtc/GMT+
				PST8PDTEtc/UCTEtc/GMT-9Etc/
				UCTEtc/UniversalEtc/GMT+9Etc,
			Etc/GMT-4Etc/Etc/TUTCEtc/GMT-10
	Etc/GMT-5Etc/GMT0	Etc/GMT+10	Etc/Zulu	UTC
Etc/GMT-0	Etc/GMT+5	Etc/GMT-11	GMT	WET
Etc/GMT+0	Etc/GMT-6	Etc/GMT+11	Greenwich	WSU
	Etc/GMT+6Etc/GMT-1	Etc/GMT-12	HST	Zulu
	Etc/GMT-7Etc/GMT+1	Etc/GMT+12	MET

If you leave the time zone, century, or year blank, the current setting is reused.

Restrictions

• Date and time can only be set if NTP is disabled.
• MM is an integer from 01 to 12.
• DD is an integer from 01 to 31.
• hh is an integer from 00 to 23.
• mm is an integer from 00 to 59.
• CC is an integer from 00 to 99.
• YY is an integer from 00 to 99.

SET TIMEZONE

Syntax

SET TIMEZONE

Description

Sets the time zone.

Restrictions

Only the choices listed in Table 17 (page 135) can be used.

ENABLE NTP

Syntax

ENABLE NTP

Description

Enables NTP support for the Enclosure Manager.

Restrictions

None

DISABLE NTP

Syntax

DISABLE NTP

Description

Disables the synchronizing of time and date with a remote server using the NTP protocol. Does not clear any NTP servers that have been configured with SET NTP.

Restrictions

None

CLEAR NTP

Syntax

CLEAR NTP {PRIMARY | SECONDARY}

Description

Clears the Primary or Secondary NTP server IP address.

Restrictions

Clearing the Primary NTP address disables NTP.

SET NTP POLL

Syntax

SET NTP POLL

Description

Sets the polling interval for NTP servers. The factory default polling interval is 720 seconds (1: minutes).

Restrictions

The polling range is 60 - 86400 seconds (1 minute to 1 day).

NOTE: EM 1.10 or later does not support this command.

SET NTP PRIMARY

Syntax

SET NTP PRIMARY

Description

Sets the primary server used for synchronizing time/date using the Network Time Protocol (NTP can be either an IPv4 address, an IPv6 address, or a DNS name.

Restrictions

- IPv4 addresses must be in the form ####.###.###.###, where each ### ranges from 0 to 255.

- IPv6 addresses must be formed without the network prefix length.

SET NTP SECONDARY

Syntax

SET NTP SECONDARY

Description

Sets the secondary server used for synchronizing time/date using the Network Time Protocol (NTP) can be either an IPv4 address, and IPv6 address or a DNS name.

Restrictions

• IPv4 addresses must be in the form ####.###.###.###, where each ### ranges from 0 to 255.
• IPv6 addresses must be formed without the network prefix length.

Inventory and status

These commands display various inventory and global state data.

SET DISPLAY EVENTS

Syntax

SET DISPLAY EVENTS { ON | OFF }

Description

Turns on or off the displaying of events that are triggered by status changes in the system.

Restrictions

• This command is specific to the current CLI session and must be issued for each CLI session to display events in that session. (The setting is not persistent.)
• Upon boot of the EM, the event display is OFF.

SHOW ALL

Syntax

SHOW ALL

Description

Executes all SHOW commands in succession.

Restrictions

To save the output, you must configure your SSH software to log the session to a file or increase the history buffer size so that the output can be copied and pasted into another file.

SHOW CONFIG

Syntax

SHOW CONFIG

Description

Displays the script required to recreate the settings of the enclosure. Passwords are not included for any user.

Restrictions

None

SHOW CSR CSR-ID

Syntax

SHOW CSR CSR-

Description

Displays the CSR event messages captured in the Enclosure Manager system log (syslog) for the specified CSR ID. The output includes the cause and action for each event message.

Restrictions

A valid ID for CSR-must be used.

SHOW CSR ALL

Syntax

SHOW CSR ALL

Description

Displays all possible CSR events that can be captured in the Enclosure Manager system log (s) and includes the cause and action for each event.

Restrictions

None

SHOW CSR FAST

Syntax

SHOW CSR FAST

Description

Displays all possible CSR events that can be captured in the Enclosure Manager system log (s). The output does not include the cause and action for each event like SHOW CSR ALL.

Restrictions

None

SHOW DATE

Syntax

SHOW DATE

Description

Displays the current date, time, and time zone settings of the internal Real Time Clock of the Enclosure Manager.

Restrictions

None

SHOW DEVICE SERIAL_NUMBER BLADE

Syntax

SHOW DEVICE SERIAL_NUMBER BLADE

Description

Displays the serial number of the blade specified by the bay .

Restrictions

Can be used only when the enclosure power is on, the blade is present, and iLO is communicated with the EMU properly. If the enclosure power is off, the EMU has no signal from the blade to determine whether it is present, and iLO in the blade has no power to report its serial number. EM reports "[Unknown]" if this command is used with the enclosure power off.

SHOW DISPLAY EVENTS

Syntax

SHOW DISPLAY EVENTS

Description

Displays the current status of the display event setting.

Restrictions

None

SHOW EM

Syntax

SHOW EM INFO

Description

Displays information about the Enclosure Manager.

NOTE: Hardware versions are A, B, C, and so forth. Aux info includes the change management SVN number and the health monitor PSoC firmware version number. Both are needed occasionally in lab testing environments. In production environments, the HM version may sometimes be needed and this command is the only way to find it in EM firmware 1.0 or later.

Restrictions

None

SHOW ENCLOSURE FAN

Syntax

SHOW ENCLOSURE FAN { ALL | }

Description

Displays information about and current status of the specified enclosure fan.

Restrictions

•The must be 1 or 2.
- Fan information is not available if fan status is Dormant (meaning not powered).

- The EM is only directly controlling FAN 1. The JBOD IE expanders control FAN 2 so information on FAN 2 can only be reported if the enclosure power is on AND at least one SAS IO is present and functioning normally.

• Not all information (for example, part number and serial number) of FAN 2 are reported to the EM by the SAS IO module so it cannot be reported as with FAN 1.
• When the enclosure power is first turned on, FAN 2 status changes from Dormant to Absent and then to the actual status when this information is given to the EM.

SHOW ENCLOSURE INFO

Syntax

SHOW ENCLOSURE INFO

Description

Displays information about the enclosure and included options.

NOTE: Some information, such as Enclosure Name, is user supplied, and if never programmed has a default value. The Solution part number, serial number and name string are programmed the factory depending on the software SKU that is pre-installed. These numbers and strings are customer programmable but vary by solution SKU even if the hardware is the same type. The solution numbers, not the chassis numbers, are used for warranty obligation tracking.

Restrictions

None

SHOW ENCLOSURE POWERSUPPLY

Syntax

SHOW ENCLOSURE POWERSUPPLY { ALL | { , | - } }

Description

Displays the following general information and current status for the specified power supply or range of power supplies:

• Status (OK, Degraded, Dormant, Failed, Unknown)
• AC Input status
  •Capacity: (watts)
  • Current power output (watts)
• Serial Number
• Product name
  • Part number
• Spare part number
• Product version. Integer value, 01, 02, and so forth.

Restrictions

None

SHOW ENCLOSURE STATUS

Syntax

SHOW ENCLOSURE STATUS

Description

Displays the basic health and status of the enclosure and its subsystems. If the enclosure shows degraded, the subsystems causing the state change are detailed (for example, failed or missing redundant module).

Restrictions

None

SHOW ENCLOSURE TEMP

Syntax

SHOW ENCLOSURE TEMP

Description

Displays current status and reading of some of the thermal sensors in the enclosure. If the sensor is unreadable due to absence of power or failure, ? is displayed.

Restrictions

• Only integral measurements in Celsius are displayed (fraction, if any, is truncated).
• Not every sensor that is present in the enclosure is reported.
• For blades a virtual ambient (not a physical) sensor temperature is displayed that is computed by iLO based on its thermal model and measurements from several sensors. This model is transparent to the EM. Until this calculation normalizes, 0 is shown as the temperature for the blade, so that right after power on of the enclosure, it takes several seconds before a nonzero value is shown for the blades while other sensors are reported immediately.

SHOW FRU

Syntax

SHOW FRU

Description

Displays summary information on field replaceable units (FRUs) within the enclosure. Information provided in this section can quickly aid the administrator in contacting HP Customer Service for troubleshooting, repair, and ordering replacements.

Restrictions

• Only displays known/live data.
- Some FRU devices are not accessible by the EM when the enclosure power is off so their information is unavailable.

SHOW IOMODULES

Syntax

SHOW IOMODULES

Description

Shows information for the IO modules within the enclosure: SAS, LOM, MEZZ, and PCIe.

Restrictions

- Should be used only when enclosure power is on.

- If enclosure power has never been turned on, no information is available. If it was on but is now off, only the firmware version of the IO modules that have firmware is shown.

SHOW RACK

Syntax

SHOW RACK { NAME | ID }

Description

Displays user-defined rack name (string) or id (0...255) that is part of the persistent EMU configuration.

Restrictions

• If rack name has not been set, it is UnnamedRack.
• If rack id has not been set, it is 0.

SHOW SERVER TEMP

Syntax

SHOW SERVER TEMP { ALL | [ { , | - } ] }

Description

Displays temperature sensor information for the specified server or range of servers. This data provided by iLO to the EM, which has no direct sensor access.

Restrictions

The enclosure must be powered on, otherwise, iLO has no power and cannot sense temperature or send data to the EM.

Internet control

The following commands define the EM 1.0 or later CLI functions for Internet control.

ADD EBIPA

Syntax

ADD EBIPA { SERVER } DNS

Description

Adds an EBIPA DNS server IP address to the list of DNS servers for server bays.

Restrictions

• A maximum of three DNS servers can be added for EBIPA.
- must be in the form ####.###.###.###, where each ### ranges from 0 to 255.

REMOVE EBIPA

Syntax

REMOVE EBIPA { SERVER } DNS

Description

Removes an EBIPA (Enclosure Bay IP Addressing) DNS server IP address from the list of DNS serv for server bays.

Restrictions

must be in the form ####.###.###.###, where each ### ranges from 0 to 255.

SET EBIPA

Syntax

SET EBIPA { SERVER } { NETMASK <netmask> | GATEWAY <gateway> | DOMAIN "<domain name>" | <ip address> {<netmask> | [netmask] { ALL | <bay#> [{ , | - } <bay#>] } } 

Description

Sets EBIPA settings, including starting IP address, net mask, default gateway, and domain name for the specified bay. If a bay number is not specified when setting an IP address, then both ser bays are assigned an IP address in the range starting from the number entered for . The keyword NONE can be used in place of , , or to clear the IP address.

Restrictions

• and must be in the form ####.###.###.###, where each ### ranges from 0 to 255.
• is a string containing letters (a-z, A-Z), digits (0-9), or a hyphen (-).
  • must be 1 or 2.

SET EM GATEWAY

Syntax

SET EM GATEWAY []

Description

Sets the network default gateway. is optional because there is only one EMU bay.

Restrictions

• This gateway is used only if the system is currently configured to use a static IP address rather than the DHCP protocol.
• must be in the form ####.###.###.###, where each ### ranges from 0 to 255.
  • 1 is the only valid value for because there is no bay 2.

PING

Syntax

PING IPV6 [] { | ""}

Description

Sends ICMP echo messages to a remote IPv6 device. If you omit , or use a numbe larger than 9999 or one that is negative, then only four packets are sent. Packets are sent at one-second intervals to prevent congestion.

Restrictions

• must be between 1 and 9999.
  •IPv6 must be enabled.
• must be in the format #####:######:######::##.

SET IPCONFIG

Syntax

SET IPCONFIG { DHCP | STATIC | LOCAL }

Description

Configures EM addressing mode to be DHCP, static, or link local. The setting takes effect immediately. If mode chosen is static, other parameters are required (see below).

Restrictions

None

SET IPCONFIG STATIC

Syntax

SET IPCONFIG STATIC []

Description

Configures the IP settings for the EM to static mode. In selecting this mode, the IP address an netmask are be set to and , respectively. These settings take effect immediately. The gateway address will be cleared if it is omitted. Note that you can also set gateway address using the SET EM GATEWAY command.

Restrictions

None

SHOW NETWORK

Syntax

SHOW NETWORK

Description

Displays the network settings of the Enclosure Manager.

Restrictions

None

SHOW EBIPA

Syntax

SHOW EBIPA

Description

Displays EBIPA configuration information.

Restrictions

EM EBIPA control only functions for the two iLO processors in the server blades.

Server management

Use the commands in this section to perform server management operations.

POWEROFF SERVER

Syntax

POWEROFF SERVER { ALL | [{ , | - } ] } [FORCE]

Description

Sends an asynchronous request for a graceful shutdown to the server. This command returns the user to the CLI immediately but the shutdown command can take up to five minutes to complete. the FORCE option is specified, the server blade OS is not given the opportunity to perform a graceful shutdown before power is removed. This option can cause a server blade to lose data and possibly to become unstable.

Restrictions

• must be 1 or 2.
- Use of the FORCE option can cause a server blade to lose data and possibly to become unstable.

POWERON SERVER

Syntax

POWERON SERVER { ALL | [{ , | - } ] { {NORMAL | PXE | HDD | RBSU }]

Description

Power on the specified server. Adding an optional boot argument forces the blade to ignore the regular boot order and forces a boot using the specified method. If no blade is in the specified bay, you are notified that the bay is empty.

Restrictions

This command functions only if the enclosure power is already on.

NOTE: Because the EMU hardware cannot determine if a blade is physically present unless enclosure power is on, the EM reports the warning that the blade is not present if this command is used when enclosure power is off.

REBOOT SERVER

Syntax

REBOOT SERVER { ALL | <bay#> [ { , | - } <bay#>] } [FORCE] [ {NORMAL | PXE | HDD | RBSU }] 

Description

Sends an asynchronous request to the server to do a graceful shutdown of the OS. After the has had sufficient time to perform a graceful shutdown, the server blade is power cycled. If the FORCE option is specified, the server blade OS is not given the opportunity to perform a gradual shutdown before power is removed but is cleanly powered off and then immediately powered back on. The FORCE option can cause a server blade to lose data and possibly to become up

Restrictions

This command functions only if the enclosure power is already on. Because the EMU hardware cannot determine if a blade is physically present unless enclosure power is on, the EM reports warning that the blade is not present if this command is used when enclosure power is off.

SET SERVER UID

Syntax

SET SERVER UID { ALL | <bay#> [ { , | - } <bay#>] } { ON | OFF } 

Description

Turns on or off the UID LED on the specified servers.

Restrictions

This command functions only if the enclosure power is already on.

NOTE: Because the EMU hardware cannot determine if a blade is physically present unless enclosure power is on, the EM reports the warning that the blade is not present if this comma is used when enclosure power is off.

SET SERVER BOOT

Syntax

SET SERVER BOOT { FIRST | ONCE } { NORMAL | HDD | PXE | RBSU } { ALL |
<bay#> [{ , | - } <bay#>] 

Description

Persistently stores a setting for the IPL to be passed to the specified servers at the next reboot SET SERVER BOOT FIRST sets the boot order of the blade.

SET SERVER BOOT ONCE sets the boot device to be used on the next boot of the specified k. The RBSU option is only available for SET SERVER BOOT ONCE.

Restrictions

- This setting is only valid on present blades and is cleared if the blade is removed.

- This command functions only if the enclosure power is already on. Because the EMU hardware cannot determine if a blade is physically present unless enclosure power is on, the EM re the warning that the blade is not present if this command is used when enclosure power off.

SHOW SERVER NAMES

Syntax

SHOW SERVER NAMES

Description

Displays a brief description of all server blades.

Restrictions

This command functions only if the enclosure power is already on. If power is not on, the commands responds with the message: "enclosure power is off". If power is coming on but state exchange between iLO and EM have not normalized, some displayed information might display [Unknown] or ?.

SHOW SERVER BOOT

Syntax

SHOW SERVER BOOT { ALL | [ { - | , } ] }

Description

Displays the boot order and one-time boot device for the specified server or range of servers. The settings correspond to the server boot settings in the ROM-Based Setup Utility.

Restrictions

This command functions only if the enclosure power is already on. Because the EMU hardware cannot determine if a blade is physically present unless enclosure power is on, the EM reports the warning that the blade is not present if this command is used when enclosure power is off.

SHOW SERVER INFO

Syntax

SHOW SERVER INFO { ALL | [{ , | - } ] }

Description

Displays a description of the server blade hardware, including the embedded NICs, the Mezz HBAs, and the management processor, in the specified bays.

Restrictions

This command functions only if the enclosure power is already on.

SHOW SERVER LIST

Syntax

SHOW SERVER LIST

Description

Displays a brief iLO and status description of all server blades. For a longer description, use SHOW SERVER INFO.

Restrictions

This command functions only if the enclosure power is already on. Because the EMU hardware cannot determine if a blade is physically present unless enclosure power is on, the EM reports warning "enclosure power is off" if this command is issued when power is off.

SHOW SERVER STATUS

Syntax

SHOW SERVER STATUS { ALL | [ { , | - } ] }

Description

Displays current status of the server blade in the specified bay or both bays.

Restrictions

This command functions only if the enclosure power is already on. Because the EMU hardware cannot determine if a blade is physically present unless enclosure power is on, the EM reports warning “enclosure power is off” if this command is issued when power is off.

Enclosure control

The commands in the section provide various enclosure control functions.

DOWNLOAD CONFIG

Syntax

DOWNLOAD CONFIG

Description

Downloads a previously saved configuration script file from a specific IP host then executes it. command should be used to recover configuration after replacement of a failed EMU.

Supported protocols are HTTP, FTP, and TFTP. The URL should be formatted asprotocol://hc path/file. If your FTP server does not support anonymous connections, you can specify a username and password by replacing the host part in the above format with username:password@host.

Restrictions

Only IPv4 is supported in EM 1.0 or later.

RESTART EM

Syntax

RESTART EM

Description

This reboots the Linux OS and restarts the EM software. It is necessary to do this command for a firmware downgrade using UPGRADE IMAGE FORCE. Except when in script mode, the user is prompted for an explicit confirmation, which must be given or the command is terminated.

Restrictions

None

POWEROFF ENCLOSURE

Syntax

POWEROFF ENCLOSURE

Description

The EM removes main DC power from the enclosure (just as if the user had pressed the enclosure power-button. Servers are NOT automatically sent a graceful shutdown command; that should be done prior to issuing this command using POWEROFF SERVER. Except when in script mode, the user is prompted for an explicit confirmation, which must be given, or the command is terminated

Restrictions

None

POWERON ENCLOSURE

Syntax

POWERON ENCLOSURE

Description

The EM sends a command to the health monitor to enable main DC power (just as if the user has pressed the enclosure power button).

Restrictions

None

UPLOAD CONFIG

Syntax

UPLOAD CONFIG { }

Description

Uploads a script to the specified URL, which duplicates the current runtime configuration. Supported protocols are FTP and TFTP. The URL should be formatted as: protocol://host/path/filename. If your FTP server does not support anonymous logins, you can specify a username and password within the URL formatted as: ftp://username:password@host/path/filename

Restrictions

Only IPv4 is supported in EM version 1.0 or later.

SET EM NAME

Syntax

SET EM NAME ""

Description

Sets the user defined string reported with SHOW EM STATUS. The system responds with confirmation of the change. The default EM name is "EM-" where is the hardware Ethernet address for the iLO port on the EMU. For example, EM-78E7D1C12074.

Restrictions

must be 1 to 32 characters long and includes all alphanumeric, underscore (_), and hyphen (-) characters.

SET ENCLOSURE ASSET

Syntax

SET ENCLOSURE ASSET [TAG] ""

Description

Sets the enclosure asset tag that is stored persistently in the EM, displayed with SHOW ENCLOSURE INFO command.

Restrictions

must be 1 to 32 characters long and includes all alphanumeric, underscore (_) and hyphen (-) characters.

SET ENCLOSURE ID

Syntax

SET ENCLOSURE ID

Description

Sets the persistent enclosure ID in the EM. This ID is displayed on the 2-digit LED display on EMU module, displayed with SHOW ENCLOSURE INFO command and is provided to the StorageWorks 1200m HBA in the MEZZ2 slot of the server through the MEZZPOS CLP string. command takes effect immediately.

IMPORTANT: Do not change the enclosure ID. You will be unable to access the data volumes from the servers.

Restrictions

is a decimal integer from 0 to 99.

SET ENCLOSURE NAME

Syntax

SET ENCLOSURE NAME ""

Description

Sets the persistent enclosure name stored in the EM. This name is displayed with SHOW ENCLOSURE INFO command. The default (unset by user) value is 'UnnamedEnclosure'.

Restrictions

must be 1 to 32 characters long and includes all alphanumeric, underscore (_), and hyphen (-) characters.

SET ENCLOSURE UID

Syntax

SET ENCLOSURE UID { ON | OFF | SLOW | FAST }

Description

Sets the blue enclosure UID. The enclosure has a UID on both the front and rear of the enclosure. However, the front UID is only lit when enclosure power is on, while the rear UID is only lit when standby power is on. The Unit Identification LED displays as steady on, off, or one of two blinkin speeds. The system confirms the operation. There is no particular meaning to SLOW or FAST.

Restrictions

Blinking rates are not user definable. SLOW is 1 Hz; FAST is 2 Hz.

SET FACTORY

Syntax

SET FACTORY

Description

Restores configuration settings back to the factory defaults, including deleting any created user accounts, except for the Administrator password, which remains unmodified. The EM restarts after restoring the configuration settings. If the enclosure power is on, the iLOs are reset (to force a refresh of the enclosure information passed to iLO).

Restrictions

None

SET RACK NAME

Syntax

SET RACK NAME ""

Description

Sets the user-defined string reported with SHOW RACK NAME command. The system responds with confirmation of the change. The default (unset by user) rack name is 'UnnamedRack'.

Restrictions

must be 1 to 32 characters long and includes all alphanumeric, underscore (_), and hyphen (-) characters.

UPDATE IMAGE

Syntax

UPDATE IMAGE { [ FORCE ] }

Description

Downloads a new EM firmware image from the network and uses it to update the Enclosure Manager's firmware. Supported protocols are HTTP, FTP, and TFTP. The EM validates the image before performing the update. Unless the session is in script mode, the EM requests confirmation before performing the update.

After update, the EM is restarted unless the FORCE operation was used in which case a manual invocation of RESTART EM is necessary to reboot the new firmware.

Restrictions

• should be formatted as: protocol://host/path/filename.
• Host is a fully qualified domain name or an IPv4 address.
  •path/filename is the pathname of the file to download.
• Use FORCE to allow downgrading firmware even if settings/passwords may be lost.

Forensic

The following set of forensically useful functions is supported by the EM CLI.

CLEAR SYSLOG

Syntax

CLEAR SYSLOG [ EM | ENCLOSURE ]

Description

Completely erases the local syslog of the Enclosure Manager. The EM prompts the user for confirmation because once deleted, this information cannot be recovered.

Restrictions

Only deletes the syslog stored inside the EM itself; it does not delete the remote syslog, if ren logging is enabled.

SHOW SYSLOG SERVER

Syntax

SHOW SYSLOG SERVER

Description

Displays the syslog for the specified server. If the session is not in script mode, the EM page displays display of the output to throttle output and give the user time to view the data. iLO syslog dc formatted in XML.

Restrictions

• must be 1 or 2.
- This command can only function if enclosure power is on. Because the EMU hardware cannot determine if a blade is physically present unless enclosure power is on, the EM reports that warning "Could not determine the IP address of the management processor for blade" if the command is issued when power is off.

SHOW SYSLOG EM

Syntax

SHOW SYSLOG EM

Description

Displays the local syslog for the Enclosure Manager.

Restrictions

None

SHOW SYSLOG SETTINGS

Syntax

SHOW SYSLOG SETTINGS

Description

Displays the remote syslog settings (enabled/disabled status, IP address, Port#) for the Enclosure Manager.

Restrictions

None

TEST SYSLOG

Syntax

TEST SYSLOG

Description

Tests the remote system log settings by logging a test message to the remote syslog. The test mess also appears in the local EM system log.

Restrictions

Only functions if remote syslog is enabled.

SET REMOTE SYSLOG SERVER

Syntax

SET REMOTE SYSLOG SERVER { | }

Description

Sets the IP address of a remote system log server.

Restrictions

•EM 1.0 only supports IPv4.
- Settings are not used unless remote system logging is enabled.

SET REMOTE SYSLOG PORT

Syntax

SET REMOTE SYSLOG PORT

Description

Sets the UDP destination port for remote system logging.

Restrictions

•The default remote system logging port is 514.
- must be a number between 1 and 65535.
- Settings are not used unless remote system logging is enabled.

ENABLE SYSLOG REMOTE

Syntax

ENABLE SYSLOG REMOTE

Description

Enables remote system logging.

Restrictions

The remote system log server address must be configured before enabling remote system loggir

DISABLE SYSLOG REMOTE

Syntax

DISABLE SYSLOG REMOTE

Description

Disables remote system logging.

Restrictions

None

Session

Interacting with the EM via the CLI requires a login-initiated session. A session represents a tro context which has a state that can be explicitly controlled by the user. This section describes commands for managing session state and behavior.

CLEAR SCREEN

Syntax

CLEAR SCREEN

Description

Clears the terminal screen.

Restrictions

None

CONNECT SERVER

Syntax

CONNECT SERVER

Description

Opens a Text Console session to the iLO specified by the server bay number. Exit from the set with 'exit'.

Restrictions

This command can function only if enclosure power is on and a blade server is present. Because the EMU hardware cannot determine if a blade is physically present unless enclosure power is

the EM reports the warning "The blade is not present." if this command is issued when enclosure power is off.

EXIT

Syntax

EXIT | LOGOUT | QUIT

Description

Exit the Command Line Interpreter.

Restrictions

None

HELP

Syntax

HELP []

Description

Show Help messages for or list the top-level commands if no arguments are provided. Arguments listed in braces ( { } ) and separated by the pipe symbol ( | ) are mutually exclusive choices. Arguments listed in square brackets ( [ ] ) are optional arguments and can be omitted. Fields listed in angle brackets (< >) should be replaced with the value indicated.

Restrictions

None

SET SCRIPT

Syntax

SET SCRIPT [MODE] { ON | OFF }

Description

Sets script mode on or off. script mode prevents commands from prompting for input or confirmatic. All actions are performed without confirmation. Default values are used for any parameters that normally require user interaction. This setting is only effective for the current CLI session.

Restrictions

The ADD USER command must have a password argument if executed in script mode.

SHOW SESSION TIMEOUT

Syntax

SHOW SESSION TIMEOUT

Description

Displays the current Enclosure Manager user session timeout. The session timeout is the number of minutes before insessions are removed.

Restrictions

None

SET SESSION TIMEOUT

Syntax

SET SESSION TIMEOUT

Description

Sets the number of minutes before insessions are removed. Valid session timeout. Please note: the session timeout value is lowered, currently insessions may be removed. The default timeout 1,440 minutes.

Restrictions

must be in the range from 10 to 1,440 minutes (24 hours). The session timeout can be disabled by setting it to zero.

SLEEP

Syntax

SLEEP

Description

Pauses the session for a fixed period of time. Useful for adding delays to scripts. The parameter can be any whole number from 1 to 86400.

NOTE: Once the pause begins, there is no way to continue the session before time runs out, but you can always terminate the session (from the client end) and start another one.

Restrictions

The parameter can be any whole number from 1 to 86400.

HISTORY

Syntax

HISTORY

Description

Shows the history of commands for the current session.

Restrictions

None

Using the Enclosure Manager physical interface

The primary interface to the Enclosure Manager is the Ethernet LAN port, which is intended for remote management of the enclosure. AC power is applied to the enclosure so that auxiliary p is available to the EMU. The enclosure may or may not be powered on. Solution software mc may not be installed.

Manual button functions

IMPORTANT: Use the following manual button functions only with the assistance of HP Technical Support.

The two manual buttons and a two-digit LED display on the EM provide basic management function when the EM is not connected to the network. Figure 145 (page 158) illustrates the physical (touch/visual) interaction elements.

Figure 145 EM Physical Interface

Activate Button Menu

You cannot manage the EM using a remote management interface because the system is not connected to the LAN, the LAN interface is not functioning properly, or management software is not installed or available.

To activate the button menu:

1. Press and hold the UP (right) button until the two digits display “- -”.
2. Release the UP button. System displays two underscores “_ _”:

This display indicates context is at the bottom of the menu range and is awaiting menu selection which requires pressing the UP button one or more times.

Reboot EM (bE)

The EM LAN interface is not responding to the remote management software but is configured to do so, or the EM has just been reconfigured and needs to be rebooted for the configuration to take effect.

To reboot the EM:

1. Enter the menu mode using the "Activate Button Menu" (page 158).
2. Press the UP button one time.
   The EM changes the display from “_ _” to “bE” to indicate that menu choice 0 (Reboot) is selected.
3. Press and hold the UP button for three seconds.
   The system blinks (or flashes) the two "bE" for one second to acknowledge the selection.
4. Release the UP button.
   The system then reboots the EM. This event is logged in the system log. The display shows "-" during the reboot. The module fault LED flashes. When the reboot is complete, the EM gre health LED is lit steady, and the enclosure ID is displayed on the two digits.

Restore Factory Defaults (Fd)

You might be replacing an EM or reconfiguring a storage system. The action resets the EMU address to a link local IP address (not the factory default).

To restore factory defaults:

1. Enter the menu mode using the "Activate Button Menu" (page 158).

2. Press the UP button until the display changes from “_ _” to “Fd”.

3. Press and hold the UP button for three seconds.

The EM blinks (or flashes) "Fd" three times to acknowledge the selection.

1. Release the UP button.

The system stops flashing the pattern, internally restores all configurations to factory defaults and reboots the EM.

Recover Lost Password (Fp)

You changed the Administrator password from the default password set by the factory, and the lost or forgot the new password.

To recover a lost password:

1. Enter the menu mode using the "Activate Button Menu" (page 158).
2. Press the UP button until the display changes from “_ _” to “Fp”.
3. Press and hold the UP button for three seconds.

The EM blinks (or flashes) "Fp" to acknowledge the selection.

1. Release the UP button.

The system stops flashing "Fp". The system restores the Administrator password from hardw and logs the event in the syslog. The system displays the Enclosure ID to indicate that the operation is complete.

Set DHCP IP Address (dH)

Reconfigure the storage system for a different network where IP address assignment is handled dynamically.

To set a DHCP IP address:

1. Enter the menu mode using the "Activate Button Menu" (page 158).
2. Press the UP button until the display changes from “_ _” to “dH”.
3. Press and hold the UP button for three seconds.

The EM flashes "dH" to acknowledge the selection.

1. Release the UP button.

The system sets the EM to DHCP and exits the menu mode. This event is also logged in EM syslog and takes effect immediately. The system displays the Enclosure ID to indicate the operation is complete.

Set Link Local IP Address (LL)

Reconfigure the storage system for a network where IP address assignment is static.

To set a static IP address:

1. Enter the menu mode using the "Activate Button Menu" (page 158).
2. Press the UP button until the display changes from “_ _” to “LL”.
3. Press and hold the UP button for three seconds.

The EM flashes "LL" to acknowledge the selection.

1. Release the UP button.

The system sets the EM to Link local mode and exits the menu mode. This event is also in the EM syslog and takes effect immediately. The system displays the Enclosure ID to include that the operation is complete.

Display Current IP Address (IP)

Learn the IP address of the EM.

To find the current IP address:

1. Enter the menu mode using the "Activate Button Menu" (page 158).

2. Press the UP button until the display changes from “_ _” to “IP”.

3. Press and hold the UP button for three seconds.

The EM displays "IP" to acknowledge the selection.

1. Release the UP button.

The system enters the 'Display IP' subfunction and displays the first octet of the IPv4 address being used by the EM.

1. Press the UP button three times to scroll through the other three octets of the EM IP address. You can back up using the DOWN button.

2. Press and hold the DOWN button for three seconds.

The EM flashes "IP" to acknowledge the selection, and then exits the operation. The system displays the Enclosure ID to indicate that the operation is complete.

Exit Button Menu

Exit the main menu (or any subfunction).

To exit the button menu:

Press and hold the DOWN button for three seconds.

The system displays and flashes the two hyphens ("-") three times to indicate the menu was exit. The system then returns the LEDs to the original display state showing the Enclosure ID.

B Regulatory compliance notices

This section contains regulatory notices for the HP ____.

Regulatory compliance identification numbers

For the purpose of regulatory compliance certifications and identification, this product has been assigned a unique regulatory model number. The regulatory model number can be found on the product nameplate label, along with all required approval markings and information. When requesting compliance information for this product, always refer to this regulatory model number. The regulatory model number is not the marketing name or model number of the product.

Product specific information:

HP

Regulatory model number: ____

FCC and CISPR classification: ____

These products contain laser components. See Class 1 laser statement in the "Laser compliance notices" (page 165) section.

Federal Communications Commission notice

Part 15 of the Federal Communications Commission (FCC) Rules and Regulations has established Radio Frequency (RF) emission limits to provide an interference-free radio frequency spectrum. Many electronic devices, including computers, generate RF energy incidental to their intended function and are, therefore, covered by these rules. These rules place computers and related peripheral devices into two classes, A and B, depending upon their intended installation. Class devices are those that may reasonably be expected to be installed in a business or commercial environment. Class B devices are those that may reasonably be expected to be installed in a residential environment (for example, personal computers). The FCC requires devices in both class to bear a label indicating the interference potential of the device as well as additional operational instructions for the user.

FCC rating label

The FCC rating label on the device shows the classification (A or B) of the equipment. Class devices have an FCC logo or ID on the label. Class A devices do not have an FCC logo or the label. After you determine the class of the device, refer to the corresponding statement.

Class A equipment

This equipment has been tested and found to comply with the limits for a Class A digital dev pursuant to Part 15 of the FCC rules. These limits are designed to provide reasonable protection against harmful interference when the equipment is operated in a commercial environment. This equipment generates, uses, and can radiate radio frequency energy and, if not installed and u in accordance with the instructions, may cause harmful interference to radio communications. Operation of this equipment in a residential area is likely to cause harmful interference, in wh case the user must correct the interference at personal expense.

Class B equipment

This equipment has been tested and found to comply with the limits for a Class B digital devi pursuant to Part 15 of the FCC Rules. These limits are designed to provide reasonable protecti against harmful interference in a residential installation. This equipment generates, uses, and ca radiate radio frequency energy and, if not installed and used in accordance with the instructio may cause harmful interference to radio communications. However, there is no guarantee that interference does not occur in a particular installation. If this equipment does cause harmful interference to radio or television reception, which can be determined by turning the equipment

off and on, the user is encouraged to try to correct the interference by one or more of the follow measures:

•Reorient or relocate the receiving antenna.
- Increase the separation between the equipment and receiver.
- Connect the equipment into an outlet on a circuit that is different from that to which the receiver is connected.
- Consult the dealer or an experienced radio or television technician for help.

Modification

The FCC requires the user to be notified that any changes or modifications made to this device that are not expressly approved by Hewlett-Packard Company may void the user's authority to operate the equipment.

Cables

When provided, connections to this device must be made with shielded cables with metallic RFI/EN connector hoods in order to maintain compliance with FCC Rules and Regulations.

Canadian notice (Avis Canadien)

Class A equipment

This Class A digital apparatus meets all requirements of the Canadian Interference-Causing Equipment Regulations.

This Class B digital apparatus meets all requirements of the Canadian Interference-Causing Equipment Regulations.

This product complies with the following EU directives:

•Low Voltage Directive 2006/95/EC
• EMC Directive 2004/108/EC

Compliance with these directives implies conformity to applicable harmonized European standards (European Norms) which are listed on the EU Declaration of Conformity issued by Hewlett-Packard for this product or product family.

This compliance is indicated by the following conformity marking placed on the product:

This marking is valid for non-Telecom products and EU harmonized Telecom products (e.g., Bluetooth).

Certificates can be obtained from http://www.hp.com/go/certificates.

Hewlett-Packard GmbH, HQ-TRE, Herrenberger Strasse 140, 71034 Boeblingen, Germany

Japanese notices

Japanese VCCI-A notice

Japanese VCCI marking

Japanese power cord statement

Please use the attached power cord. The attached power cord is not allowed to use with other product.

Korean notices

Class A equipment

A급 기기 (업무용 정보통신기기)

Taiwan battery recycle statement

廢電池請回收

Vietnamese notice

Laser compliance notices

English laser notice

This device may contain a laser that is classified as a Class 1 Laser Product in accordance with U.S. FDA regulations and the IEC 60825-1. The product does not emit hazardous laser radiati

WARNING! Use of controls or adjustments or performance of procedures other than those specified herein or in the laser product's installation guide may result in hazardous radiation exposure. To reduce the risk of exposure to hazardous radiation:

• Do not try to open the module enclosure. There are no user-serviceable components inside.
• Do not operate controls, make adjustments, or perform procedures to the laser device other than those specified herein.
• Allow only HP Authorized Service technicians to repair the unit.

The Center for Devices and Radiological Health (CDRH) of the U.S. Food and Drug Administration implemented regulations for laser products on August 2, 1976. These regulations apply to laser products manufactured from August 1, 1976. Compliance is mandatory for products marketed in the United States.

Dutch laser notice

Italian laser notice

Japanese laser notice

Spanish laser notice

English recycling notice

Disposal of waste equipment by users in private household in the European Union

This symbol means do not dispose of your product with your other household waste. Instead, you should protect human health and the environment by handing over your waste equipment to a designated collection point for the recycling of waste electrical and electronic equipment. For more information, please contact your household waste disposal service

Bulgarian recycling notice

Czech recycling notice

Danish recycling notice

Dutch recycling notice

Estonian recycling notice

Finnish recycling notice

French recycling notice

German recycling notice

Greek recycling notice

Hungarian recycling notice

Italian recycling notice

Latvian recycling notice

Lithuanian recycling notice

Polish recycling notice

Portuguese recycling notice

Romanian recycling notice

Slovak recycling notice

Spanish recycling notice

Swedish recycling notice

Turkish recycling notice

Battery replacement notices

Dutch battery notice

French battery notice

Avis relatif aux piles

Italian battery notice

Spanish battery notice

CSR Customer self repair.

EBIPA Enclosure Bay IP Addressing

EM Enclosure Manager

EMU Enclosure Manager Unit

ESD Electrostatic discharge. The emission of a potentially harmful static electric voltage as a result of improper grounding.

FRU Field replaceable unit. An assembly component that is designed to be replaced on site, without the system having to be returned to the manufacturer for repair.

PSoC Programmable System-on-Chip

RBSU ROM-Based Setup Utility

SAID Service Agreement Identifier.

SCOM Systems Center Operations Manager

SIM Systems Insight Manager

SKU Stock-keeping unit

TCO Total cost of ownership. A financial estimate for determining economic value of an investment.

UID Unit identification

WBEM Web-Based Enterprise Management

Witness Server A server used for high availability in conjunction with database availability groups. For more information, see the Microsoft Technet article, Create a Database Availability Group at http://technet.microsoft.com/en-us/library/dd351172.aspx.

WMI Windows Management Instrumentation

Index

Symbols

1210m cache module

removing and replacing, 113

2-port 1GB Ethernet I/O module

LED behavior, 38

2-port 1GB Mezz A and B I/O module

LED behavior, 38

B

battery replacement notices, 173

best practices

for removing and replacing hardware components, 61

C

cache module controller

LED behavior, 37

Canadian notice, 162

capacitor pack

removing and replacing, 116

chassis switches

LED behavior, 40

completing initial configuration, 20

component replacement videos

accessing, 61

contacting HP, 128

controller and controller server blade components

removing and replacing, 111

customer self repair see removing and replacing hardware

components

D

Disposal of waste equipment, European Union, 167

documentation

providing feedback on, 130

drive drawer

removing and replacing, 91

drive drawer hard drive

removing and replacing, 96

drive drawer rails (side or bottom)

removing and replacing, 98

drive fan

LED behavior, 41

removing and replacing, 75

E

electrostatic discharge

avoiding, 65

EMU

CLI reference, 131

configuring management processor, 15

LED behavior, 37

logging in, 42

removing and replacing, 81

using CLI SHOW commands for troubleshooting, 42

enclosure rails

removing and replacing, 103

Ethernet I/O module

removing and replacing, 78

European Union notice, 162

Event Notifier

configuring for proemail (SMTP) event notification, 22

F

factory image

restoring the system, 121

failure of component

verifying, 66

Federal Communications Commission notice, 161

firmware

checking for version upgrade, 32, 58

updating component, 56

upgrading, 55

front bezel (full)

removing and replacing, 87

front bezel (standard)

removing and replacing, 85

front LED display board

LED behavior, 35

front LED display board (full)

removing and replacing, 89

front LED display board in the rack (standard)

removing and replacing, 88

hard drive

LED behavior, 36

wait time after replacement, 66

hardware

upgrading, 55

hardware components

removing and replacing, 61

upgrading, 60

|

I/O module

LED behavior, 41

iLO

configuring management processor, 15

Insight Remote Support, 50

implementing, 50

installing X5000 G2 hardware, 9

J

Japanese notices, 163

K

kit contents

X5000 G2 Network Storage System, 9

Korean notices, 163

L

laser compliance notices, 165

LED

2-port 1 GB Ethernet I/O module, 38

2-port 1 GB Ethernet, Mezz A and B I/O module, 38

cache module controller, 37

chassis switches and indicator, 40

EMU, 37

fan, 41

front LED display board, 35

hard drive, 36

I/O module, 41

power supply, 39

server blade, 34

M

maintenance

SAID, 54

warranty entitlement labels, 54

management processor

configuring EMU, 15

configuring iLO, 15

Mezzanine NIC

removing and replacing, 118

Microsoft Systems Center Operations Manager (SCOM)

using for monitoring and troubleshooting, 51

midplane board

removing and replacing, 70

monitoring tools, 22

component LEDs, 34

EMU CLI SHOW commands, 42

Event Notifer, 22

Microsoft Systems Center Operations Manager (SCOM), 51

notification alerts, 22

System Management Homepage, 26

System Manager, 30

N

network connections, 12

notification alerts, 22

sample error messages, 22

O

OpsMgr see Microsoft Systems Center Operations

Manager (SCOM)

P

PCIe module

removing and replacing, 79

power off procedure, 60

power on procedure, 14, 60

power supply

LED behavior, 39

removing and replacing, 77

power UID button assembly

removing and replacing, 76

product number

locating, 9

R

rack rails

removing and replacing, 108

Rack stability

HP, 129

recovering the system, 120

system recovery DVD, 120

USB flash drive, 121

recycling notices, 167

regulatory compliance

Canadian notice, 162

European Union notice, 162

identification numbers, 161

Japanese notices, 163

Korean notices, 163

laser, 165

recycling notices, 167

Taiwanese notices, 164

Vietnamese notice, 164

remote support see Insight Remote Support

removing and replacing hardware components, 61

1210m cache module, 113

best practices, 61

capacitor pack, 116

controller and controller server blade components, 111

drive drawer, 91

drive drawer hard drive, 96

drive drawer rails (side or bottom), 98

drive fan, 75

EMU, 81

enclosure rails, 103

Ethernet I/O module, 78

front bezel (full), 87

front bezel (standard), 85

front LED display board (full), 89

front LED display board in the rack (standard), 88

Mezzanine NIC, 118

midplane board, 70

PCIe module, 79

power supply, 77

power UID button assembly, 76

rack rails, 108

SAS cable, 73

SAS I/O module, 73

server airflow baffle, 84

server blade, 108

server blade backplane, 82

server blade hard drive, 109

server interposter board, 68

replaceable part

identifying, 62

restoring the system

factory image, 121

S

SAID

locating number, 9

obtaining, 54

SAS cable

removing and replacing, 73

SAS I/O module

removing and replacing, 73

serial number

locating, 9

server airflow baffle

removing and replacing, 84

server blade

LED behavior, 34

removing and replacing, 108

server blade backplane

removing and replacing, 82

server blade hard drive

removing and replacing, 109

server interposter board

removing and replacing, 68

Service Agreement ID see SAID

spare part

hot, warm, cold swap, 65

identifying, 62

verifying proper operation after replacement, 66

Subscriber's Choice for Business, 128

Support websites

contacting HP, 128

HP, 49, 128

Subscribers's Choice for Business, 128

Subscription service, 128

system fan

LED behavior, 41

USB flash drive, 121

system software

upgrading, 55

T

Taiwanese notices, 164

technical support see Support websites

troubleshooting tools, 22

component LEDs, 34

EMU CLI SHOW commands, 42

Event Notifer, 22

Insight Remote Support, 50

Microsoft Systems Center Operations Manager (SCOM), 51

notification alerts, 22

System Management Homepage, 26

System Manager, 30

U

unpacking the X5000 G2 Network Storage System, 9

updating

system software and firmware, 55

upgrading

system software and firmware, 55

upgrading hardware components, 60

USB flash drive

system recovery, 121

V

Vietnamese notice, 164

W

warranty entitlement labels

locations, 54

X

X5000 G2 Network Storage System

accessing, 19

Configuration Wizard, 19

configuring system, 19

exploded view, 62

features, 7

front view, 7

hardware models, 7

installing hardware, 9

kit contents, 9

locating product number, 9

locating SAID number, 9

locating serial number, 9

monitoring tools, 22

network connections, 12

powering off, 60

powering on, 14, 60

preparing to install, 7

rear view, 7

recovery, 120, 121

restoring factory image, 121

software components, 8

troubleshooting tools, 22

unpacking, 9

updating system software and firmware, 55

upgrading system software and firmware, 55