Websites.... Typographic conventions.... Customer self repair.... Rack stability....

123 124

A Regulatory notices... 125
Regulatory notices.... Federal Communications Commission (FCC) notice... FCC Class A certification.... Class A equipment.... Class B equipment.... Declaration of conformity for products marked with the FCC logo, United States only.. Modifications... Cables.... Laser device.... Laser safety warnings.... Compliance with CDRH regulations... Certification and classification information... Canadien notice (avis Canadien).... Class A equipment.... Class B equipment.... Notice for the European union... Notice for France.... WEEE Recycling Notices.... English notice... Dutch notice.... Czechoslovakian notice.... Estonian notice.... Finnish notice... French notice.... German notice.... Greek notice.... Hungarian notice... Italian notice.... Latvian notice... Lithuanian notice... Polish notice.... Portuguese notice... Slovakian notice.... Slovenian notice.... Spanish notice.... Swedish notice.... Germany noise declaration... Japanese notice.... Harmonics conformance (Japan).... Taiwanese notice.... Japanese power cord notice.... Country-specific certifications... 134 134
B Non-standard rack specifications.. 137
Internal component envelope.... EIA310-D standards.... EVA cabinet measures and tolerances.... Weights, dimensions and component CG measurements.. 137 138
Airflow and recirculation.... Component airflow requirements... Rack airflow requirements... Configuration standards.... UPS selection.... Shock and vibration specifications....

139 140

Glossary... 141 Index.... 155

Figures

1 Storage system hardware components (back view).. Disk drive bay numbering... Disk enclosure (front view without bezel ears)... Disk enclosure (rear view)... I/O module detail.... Fiber Optic Fibre Channel cable... Copper Fibre Channel cable... Disk status indicators.... Controller enclosure (front bezel)... Controller enclosure (front view with bezel removed).. HSV300 controller enclosure (back view).. HSV300-S controller enclosure (back view)... Controller status LEDs.... Power supply.... Fan module pulled out... Battery module pulled out... Dual PDUfront view.... Dual PDUrear view.... Rack PDM.... Rack AC power distribution... Single rack configuration floor space requirements.. Raising a leveler foot.... Management module.... WOCP Configure controller host ports page... Example of typical product label... Single path HBA server without OpenVMS... Single path HBA server with OpenVMS... HP-UX configuration... Windows Server 2008 (32-bit), Windows Server 2003 (32-bit), and Windows 2000 configuration.... Windows Server 2008 (64-bit) or Windows Server 2003 (64-bit) configuration. SUN Solaris configuration... 94

Repeat Step 1 for the other feet.
1. Hex nut 2. Leveler foot
Figure 22 Raising a leveler foot
Carefully move the rack to the installation area and position it to provide the necessary service areas (see Figure 21).
To stabilize the rack when it is in the final installation location: 1. 2. 3. Use a wrench to lower the foot by turning the leveler foot hex nut clockwise until the caster does not touch the floor. Repeat for the other feet. After lowering the feet, check the rack to ensure it is stable and level. Adjust the feet as necessary to ensure the rack is stable and level.

2 EVA4400 operation

Best practices
For useful information on managing and configuring your storage system, see the HP StorageWorks 4400/6400/8400 Enterprise Virtual Array configuration Best practices white paper available at: http://h18006.www1.hp.com/storage/arraywhitepapers.html
Operating tips and information
Reserving adequate free space
To ensure efficient storage system operation, reserve some unallocated capacity, or free space, in each disk group. The recommended amount of free space is influenced by your system configuration. For guidance on how much free space to reserve, see the HP StorageWorks 4400/6400/8400 Enterprise Virtual Array configuration Best practices white paper. See Best practices.

Using FATA disk drives

FATA drives are designed for lower duty cycle applications such as near online data replication for backup. Do not use these drives as a replacement for EVA's high performance, standard duty cycle, Fibre Channel drives. This practice could shorten the life of the drive. For more information on FATA drives, see the HP StorageWorks 4400/6400/8400 Enterprise Virtual Array configuration Best practices white paper. See Best practices.
Using solid state disk drives
Supported in the EVA4400 and EVA6400/8400 only, running a minimum controller software version of 09500000 for the 72 GB drive and 09534000 for the 200 GB and 400 GB drives SSD drives must be in a separate disk group The SSD disk group supports a minimum of 6 and a maximum of 8 drives per array SSD drives can only be configured with Vraid5 or Vraid1 (Vraid1 requires controller software version 09534000 Supported with HP Business Copy EVA Not supported with HP Continuous Access EVA Dynamic Capacity Management extend and shrink features are not supported Use of these devices in unsupported configurations can lead to unpredictable results, including unstable array operation or data loss.
EVA4400 port does not log in to the embedded switch
It has been observed that an EVA4400 host port will occasionally not log in to the embedded switch. If you encounter this issue, restart the controller to bring the port online.
Emulex HBAs require unique zoning
When multiple Emulex HBAs are connected to the same EVA4400, each HBA requires unique zoning.

Shutting down the storage system from HP Command View EVA
1. 2. Start HP Command View EVA. Select the appropriate storage system in the Navigation pane. The Initialized Storage System Properties window for the selected storage system opens. 3. Click Shut down. The Shutdown Options window opens. 4. Under System Shutdown, click Power Down. If you want to delay the initiation of the shutdown, enter the number of minutes in the Shutdown delay field. The controllers complete an orderly shutdown and then power off. The disk enclosures then power off. Wait for the shutdown to complete.
Shutting down the storage system from the array controller
1. 2. Push and hold the enclosure power button on the rear of the EVA4400 (see callout 9 in Figure 11 or Figure 12). Wait 4 seconds. The power button and the green LED start to blink. NOTE: You must press and hold the power switch button for a minimum of 4 seconds. Otherwise, nothing will happen. 3. 4. Between 4 and 10 seconds, release the button. The button continues to blink and the firmware starts the shutdown process (LED becomes solid amber, flushes the cache, disables the batteries). After 10 seconds, the power shuts down.
Starting the storage system
1. Verify that each Fibre Channel fabric switch connected to the HSV controllers is powered up and fully booted. The power indicator on each switch should be on. If you must power up the SAN switches, wait for them to complete their power-on boot process before proceeding. This can take several minutes. 2. 3. 4. 5. Power on the circuit breakers on both EVA rack PDUs. Verify that all disk enclosures are operating properly. The status indicator and the power indicator should be on (green). Power on the controller enclosure, which powers on both controllers. After allowing the EVA4400 to start, connect to the web-based Operator Control Panel (WOCP) to verify the display of the storage system name and WWN. Start HP Command View EVA and verify connection to the storage system. If the storage system is not visible, click HSV Storage Network in the Navigation pane, and then click Discover in the Content pane to allow HP Command View EVA to discover the array. NOTE: If the storage system is still not visible, check zoning and cabling, and verify correct configuration of server connectivity. If necessary, reboot the management server to re-establish the communication link. 6. Check the storage system status using HP Command View EVA to ensure everything is operating properly. If any status indicator is not normal, check the log files or contact your HP-authorized service provider for assistance.

Installing a Qlogic driver
NOTE: The HP Emulex driver kit performs in a similar manner; use./INSTALL -h to list all supported arguments. 1. 2. 3. 4. 5. Download the appropriate driver kit for your distribution. The driver kit file is in the format hp_qla2x00-yyyy-mm-dd.tar.gz. Copy the driver kit to the target system. Uncompress and untar the driver kit using the following command: # tar zxvf hp_qla2x00-yyyy-mm-dd.tar.gz Change directory to the hp_qla2x00-yyyy-mm-dd directory. Execute the INSTALL command. The INSTALL command syntax varies depending on your configuration. If a previous driver kit is installed, you can invoke the INSTALL command without any arguments. To use the currently loaded configuration: #./INSTALL To force the installation to failover mode, use the -f flag:
#./INSTALL -f To force the installation to single-path mode, use the -s flag: #./INSTALL -s To list all supported arguments, use the -h flag: #./INSTALL -h The INSTALL script installs the appropriate driver RPM for your configuration, as well as the appropriate fibreutils RPM. 6. Once the INSTALL script is finished, you will either have to reload the QLogic driver modules (qla2xxx, qla2300, qla2400, qla2xxx_conf) or reboot your server. To reload the driver use one or more of the following commands, as applicable: # /opt/hp/src/hp_qla2x00src/unload.sh # modprobe qla2xxx_conf # modprobe qla2xxx # modprobe qla2300 # modprobe qla2400 To reboot the server, enter the reboot command. CAUTION: If the boot device is attached to the SAN, you must reboot the host. 7. To verify which RPM versions are installed, use the rpm command with the -q option. For example: # rpm -q hp_qla2x00src # rpm q fibreutils
Upgrading Linux components
If you have any installed components from a previous solution kit or driver kit, such as the qla2x00 RPM, invoke the INSTALL script with no arguments, as shown in the following example: #./INSTALL To manually upgrade the components, select one of the following kernel distributions: For 2.4 kernel based distributions, use version 7.xx. For 2.6 kernel based distributions, use version 8.xx. Depending on the kernel version you are running, upgrade the driver RPM as follows: For the hp_qla2x00src RPM: # rpm -Uvh hp_qla2x00src- version-revision.linux.rpm For fibreutils RPM, you have two options: To upgrade the driver: # rpm -Uvh fibreutils-version-revision.linux.architecture.rpm To remove the existing driver, and install a new driver: # rpm -e fibreutils # rpm -ivh fibreutils-version-revision.linux.architecture.rpm

To verify the virtual disks, first verify that the LUN is recognized and then verify that the host can access the virtual disks. To ensure that the LUN is recognized after a virtual disk is presented to the host, do one of the following: Reboot the host.
Enter the /opt/hp/hp_fibreutils/hp_rescan -a command. To verify that the host can access the virtual disks, enter the # more /proc/scsi/scsi command. The output lists all SCSI devices detected by the server. An EVA4400 LUN entry looks similar to the following: Host: scsi3 Channel: 00 ID: 00 Lun: 01 Vendor: HP Model: HSV300 Rev: ANSI SCSI revision: 02 Type: Direct-Access
Updating the AlphaServer console code, Integrity Server console code, and Fibre Channel FCA firmware
The firmware update procedure varies for the different server types. To update firmware, follow the procedure described in the Installation instructions that accompany the firmware images.
Verifying the Fibre Channel adapter software installation
A supported FCA should already be installed in the host server. The procedure to verify that the console recognizes the installed FCA varies for the different server types. Follow the procedure described in the Installation instructions that accompany the firmware images.
Console LUN ID and OS unit ID
HP Command View EVA software contains a box for the Console LUN ID on the Initialized Storage System Properties window. It is important that you set the Console LUN ID to a number other than zero (0). If the Console LUN ID is not set or is set to zero (0), the OpenVMS host will not recognize the controller pair. The Console LUN ID for a controller pair must be unique within the SAN. Table 15 shows an example of the Console LUN ID. You can set the OS unit ID on the Virtual Disk Properties window. The default setting is 0, which disables the ID field. To enable the ID field, you must specify a value between 1 and 32767, ensuring that the number you enter is unique within the SAN. An OS Unit ID greater than 9999 is not capable of being served by MSCP. CAUTION: It is possible to enter a duplicate Console LUN ID or OS unit ID number. You must ensure that you enter a Console LUN ID and OS Unit ID that is not already in use. A duplicate Console LUN ID or OS Unit ID can allow the OpenVMS host to corrupt data due to confusion about LUN identity. It can also prevent the host from recognizing the controllers. Table 15 Comparing console LUN to OS unit ID

$ INIT $1$DGA1: data1 $ MOUNT/SYSTEM $1$DGA1: data1 $ SHOW DEV $1$DGA1: /FULL

Setting preferred paths

You can use one of the following options for setting, changing, or displaying preferred paths: To set or change the preferred path, use the following command: $ SET DEVICE $1$DGA83: /PATH=PGA0.5000-1FE1-0007-9772/SWITCH This allows you to control which path each virtual disk uses. To display the path identifiers, use the SHOW DEV/FULL command. For additional information on using OpenVMS commands, see the OpenVMS help file: $ HELP TOPIC
For example, the following command displays help information for the MOUNT command: $ HELP MOUNT
NOTE: The information in this section applies to both SPARC and x86 versions of the Sun Solaris operating system.
Loading the operating system and software
Follow the manufacturers instructions for loading the operating system (OS) and software onto the host. Load all OS patches and configuration utilities supported by HP and the FCA manufacturer.
Configuring FCAs with the Sun SAN driver stack
Sun-branded FCAs are supported only with the Sun SAN driver stack. The Sun SAN driver stack is also compatible with current Emulex FCAs and QLogic FCAs. Support information is available on the Sun website: http://www.sun.com/io_technologies/index.html To determine which non-Sun branded FCAs HP supports with the Sun SAN driver stack, see the latest MPxIO application notes or contact your HP representative. Update instructions depend on the version of your OS: For Solaris 9, install the latest Sun StorEdge SAN software with associated patches. To automate the installation, use the Sun-supplied install script available at: http://www.sun.com/download/ 1. Under Systems Administration, select Storage Management. 2. Under Browse Products, select StorageTek SAN 4.4. 3. Reboot the host after the required software/patches have been installed. No further activity is required after adding any new LUNs once the array ports have been configured with the cfgadm c command for Solaris 9. Examples for two FCAs: cfgadm -c configure c3 cfgadm -c configure c4 4. Increase retry counts and reduce I/O time by adding the following entries to the /etc/ system file: set ssd:ssd_retry_count=0xa set ssd:ssd_io_time=0x1e 5. Reboot the system to load the newly added parameters.
For Solaris 10, use the Sun Update Manager to install the latest patches (see http://www.sun.com/ service/sunupdate/). Reboot the host once the required software/patches have been installed. No further activity is required after adding any new LUNs, as the controller and LUN recognition are automatic for Solaris 10.

1. 2. 3.

For Solaris 10 x86/64, ensure patch 138889-03 or later is installed. For SPARC, ensure patch 138888-03 or later is installed. Increase the retry counts by adding the following line to the /kernel/drv/sd.conf file: sd-config-list="HP HSV","retries-timeout:10"; Reduce the I/O timeout value to 30 seconds by adding the following line to the /etc/system file: set sd:sd_io_time=0x1e Reboot the system to load the newly added parameters.

If the qla2300 driver is version 4.13.01 or earlier, for each LUN that users will access add an entry to the /kernel/drv/sd.conf file: name="sd" class="scsi" target=20 lun=1; name="sd" class="scsi" target=21 lun=1; name="sd" class="scsi" target=30 lun=1; name="sd" class="scsi" target=31 lun=1; If LUNs are preconfigured in the/kernel/drv/sd.conf file, after changing the configuration file. use the devfsadm command to perform LUN rediscovery.
If the qla2300 driver is version 4.15 or later, verify that the following or a similar entry is present in the /kernel/drv/sd.conf file: name="sd" parent="qla2300" target=2048; To perform LUN rediscovery after configuring the LUNs, use the following command: /opt/QLogic_Corporation/drvutil/qla2300/qlreconfig d qla2300 -s
Reboot the server to implement the changes to the configuration files.
NOTE: The qla2300 driver is not supported for Sun StorEdge Traffic Manager/Sun Storage Multipathing. To configure a QLogic FCA using the Sun SAN driver stack, see Configuring the FCAs with the Sun SAN driver stack on page 63.

Fabric setup and zoning

To set up the fabric and zoning: 1. 2. 3. 4. Verify that the Fibre Channel cable is connected and firmly inserted at the array ports, host ports, and SAN switch. Through the Telnet connection to the switch or Switch utilities, verify that the WWN of the EVA ports and FCAs are present and online. Create a zone consisting of the WWNs of the EVA ports and FCAs, and then add the zone to the active switch configuration. Enable and then save the new active switch configuration.
NOTE: There are variations in the steps required to configure the switch between different vendors. For more information, see the HP StorageWorks SAN design reference guide, available for downloading on the HP website: http://www.hp.com/go/sandesign.
Sun StorEdge Traffic Manager (MPxIO)/Sun Storage Multipathing
Sun StorEdge Traffic Manager (MPxIO)/Sun Storage Multipathing can be used for FCAs configured with the Sun SAN driver and depending on the operating system version, architecture (SPARC/x86), and patch level installed. For configuration details, see the HP StorageWorks MPxIO application notes, available on the HP support website: http://www.hp.com/support/manuals. NOTE: MPxIO is included in the SPARC and x86 Sun SAN driver. A separate installation of MPxIO is not required. In the Search products box, enter MPxIO, and then click the search symbol. Select the application notes from the search results.
Configuring with Veritas Volume Manager
The Dynamic Multipathing (DMP) feature of Veritas Volume Manager (VxVM) can be used for all FCAs and all drivers. EVA disk arrays are certified for VxVM support. When you install FCAs, ensure that the driver parameters are set correctly. Failure to do so can result in a loss of path failover in DMP. For information about setting FCA parameters, see Configuring the FCAs with the Sun SAN driver stack on page 63 and the FCA manufacturers instructions. The DMP feature requires an Array Support Library (ASL) and an Array Policy Module (APM). The ASL/APM enables Asymmetric Logical Unit Access (ALUA). LUNs are accessed through the primary controller. After enablement, use the vxdisk list <device> command to determine the primary and secondary paths. For VxVM 4.1 (MP1 or later), you must download the ASL/APM from the Symantec/Veritas support site for installation on the host. This download and installation is not required for VxVM 5.0 or later. To download and install the ASL/APM from the Symantec/Veritas support website:

1. 2. 3. 4. 5. 6. 7.

Go to http://support.veritas.com. Enter Storage Foundation for UNIX/Linux in the Product Lookup box. Enter EVA in the Enter keywords or phrase box, and then click the search symbol. To further narrow the search, select Solaris in the Platform box and search again. Read TechNotes and follow the instructions to download and install the ASL/APM. Run vxdctl enable to notify VxVM of the changes. Verify the configuration of VxVM as shown in Example 3 (the output may be slightly different depending on your VxVM version and the array configuration).
Example 3. Verifying the VxVM configuration
# vxddladm listsupport all | grep HP libvxhpevale.so HP HSV300, HSV400, HSV450 # vxddladm listsupport libname=libvxhpevale.so ATTR_NAME ATTR_VALUE ======================================================================= LIBNAME libvxhpevale.so VID HP PID HSV300, HSV400, HSV450 ARRAY_TYPE A/A-A-HP ARRAY_NAME EVA4400, EVA6400, EVA8400 # vxdmpadm listapm all | grep HP dmphpalua dmphpalua # vxdmpadm listapm dmphpalua Filename: dmphpalua APM name: dmphpalua APM version: 1 Feature: VxVM VxVM version: 41 Array Types Supported: A/A-A-HP Depending Array Types: A/A-A State: Active

A/A-A-HP

Active
# vxdmpadm listenclosure all ENCLR_NAME ENCLR_TYPE ENCLR_SNO STATUS ARRAY_TYPE ============================================================================ Disk Disk DISKS CONNECTED Disk EVA44000 EVA4400 50001FE1002709E0 CONNECTED A/A-A-HP
By default, the EVA I/O policy is set to Round-Robin. For VxVM 4.1 MP1, only one path is used for the I/Os with this policy. Therefore, HP recommends that you change the I/O policy to Adaptive in order to use all paths to the LUN on the primary controller. Example 4 shows the commands you can use to check and change the I/O policy.
Example 4. Setting the iopolicy
# vxdmpadm getattr arrayname EVA4400 iopolicy ENCLR_NAME DEFAULT CURRENT ============================================ EVA44000 Round-Robin Round-Robin # vxdmpadm setattr arrayname EVA4400 iopolicy=adaptive # vxdmpadm getattr arrayname EVA4400 iopolicy ENCLR_NAME DEFAULT CURRENT ============================================ EVA44000 Round-Robin Adaptive
The procedure used to configure the LUN path to the array depends on the FCA driver. For more information, see Installing Fibre Channel adapters. To identify the WWLUN ID assigned to the virtual disk and/or the LUN assigned by the storage administrator: Sun SAN driver, with MPxIO enabled: You can use the luxadm probe command to display the array/node WWN and associated array for the devices. The WWLUN ID is part of the device file name. For example:
/dev/rdsk/c5t600508B4001030E40000500000B20000d0s2
If you use luxadm display, the LUN is displayed after the device address. For example:

50001fe1002709e9,5

Sun SAN driver, without MPxIO: The EVA WWPN is part of the file name (which helps you to identify the controller). For example:
/dev/rdsk/c3t50001FE1002709E8d5s2 /dev/rdsk/c3t50001FE1002709ECd5s2 /dev/rdsk/c4t50001FE1002709E9d5s2 /dev/rdsk/c4t50001FE1002709EDd5s2
If you use luxadm probe, the array/node WWN and the associated device files are displayed. You can retrieve the WWLUN ID as part of the format -e (scsi, inquiry) output; however, it is cumbersome and hard to read. For example:
30 e00.50001F E1002709E050001F E1002709E8600508 B4001030E4000050 0000B20000
The assigned LUN is part of the device file name. For example:
/dev/rdsk/c3t50001FE1002709E8d5s2
You can also retrieve the LUN with luxadm display. The LUN is displayed after the device address. For example:
Emulex (lpfc)/QLogic (qla2300) drivers: You can retrieve the WWPN by checking the assignment in the driver configuration file (the easiest method, because you then know the assigned target) or by using HBAnyware/ SANSurfer. You can retrieve the WWLUN ID by using HBAnyware/SANSurfer. You can also retrieve the WWLUN ID as part of the format -e (scsi, inquiry) output; however, it is cumbersome and difficult to read. For example:
The assigned LUN is part of the device file name. For example: /dev/dsk/c4t20d5s2
Verify that the host can access virtual disks by using the format command. See Example 5.
Example 5. Format command
# format Searching for disks.done c2t50001FE1002709F8d1: configured c2t50001FE1002709F8d2: configured c2t50001FE1002709FCd1: configured c2t50001FE1002709FCd2: configured c3t50001FE1002709F9d1: configured c3t50001FE1002709F9d2: configured c3t50001FE1002709FDd1: configured c3t50001FE1002709FDd2: configured AVAILABLE DISK SELECTIONS: 0. c0t0d0 <SUN18G cyl 7506 alt 2 hd 19 sec 248> /pci@1f,4000/scsi@3/sd@0,0 1. c2t50001FE1002709F8d1 <HP-HSV400-0952 cyl 126 alt 2 hd 128 sec 128> /pci@1f,4000/QLGC,qla@4/fp@0,0/ssd@w50001fe1002709f8,1 2. c2t50001FE1002709F8d2 <HP-HSV400-0952 cyl 126 alt 2 hd 128 sec 128> /pci@1f,4000/QLGC,qla@4/fp@0,0/ssd@w50001fe1002709f8,2 3. c2t50001FE1002709FCd1 <HP-HSV400-0952 cyl 126 alt 2 hd 128 sec 128> /pci@1f,4000/QLGC,qla@4/fp@0,0/ssd@w50001fe1002709fc,1 4. c2t50001FE1002709FCd2 <HP-HSV400-0952 cyl 126 alt 2 hd 128 sec 128> /pci@1f,4000/QLGC,qla@4/fp@0,0/ssd@w50001fe1002709fc,2 5. c3t50001FE1002709F9d1 <HP-HSV400-0952 cyl 126 alt 2 hd 128 sec 128> /pci@1f,4000/lpfc@5/fp@0,0/ssd@w50001fe1002709f9,1 6. c3t50001FE1002709F9d2 <HP-HSV400-0952 cyl 126 alt 2 hd 128 sec 128> /pci@1f,4000/lpfc@5/fp@0,0/ssd@w50001fe1002709f9,2 7. c3t50001FE1002709FDd1 <HP-HSV400-0952 cyl 126 alt 2 hd 128 sec 128> /pci@1f,4000/lpfc@5/fp@0,0/ssd@w50001fe1002709fd,1 8. c3t50001FE1002709FDd2 <HP-HSV400-0952 cyl 126 alt 2 hd 128 sec 128> /pci@1f,4000/lpfc@5/fp@0,0/ssd@w50001fe1002709fd,2 Specify disk (enter its number):

From the service console, enter the wwpn.pl command. Output similar to the following is displayed: [root@gnome7 root]# wwpn.plvmhba0: 210000e08b09402b (QLogic) 6:1:0vmhba1: 210000e08b0ace2d (QLogic) 6:2:0[root@gnome7 root]# Check the SCSI device information section of the /proc/scsi/qla2300/X directory, where X is a bus instance number. Output similar to the following is displayed: SCSI Device Information: scsi-qla0-adapter-node=200000e08b0b0638; scsi-qla0-adapter-port=210000e08b0b0638; 6. Repeat this procedure for each ESX server.
Configuring an ESX server
This section provides information about configuring the ESX server.

Loading the FCA NVRAM

The FCA stores configuration information in the non-volatile RAM (NVRAM) cache. You must download the configuration for HP StorageWorks products. Perform one of the following procedures to load the NVRAM: If you have a ProLiant blade server: 1. Download the supported FCA BIOS update, available on http://www.hp.com/support/ downloads, to a virtual floppy. For instructions on creating and using a virtual floppy, see the HP Integrated Lights-Out user guide. 2. 3. Unzip the file. Follow the instructions in the readme file to load the NVRAM configuration onto each FCA.
If you have a blade server other than a ProLiant blade server: 1. Download the supported FCA BIOS update, available on http://www.hp.com/support/ downloads. 2. Unzip the file. 3. Follow the instructions in the readme file to load the NVRAM configuration onto each FCA.
Setting the multipathing policy
You can set the multipathing policy for each LUN or logical drive on the SAN to one of the following: Most recently used (MRU) Fixed Preferred ESX 2.5.x commands The # vmkmultipath s vmhba0:0:1 p mru command sets vmhba0:0:1 with an MRU multipathing policy for all LUNs on the SAN. The # vmkmultipath -s vmhba1:0:1 -p fixed command sets vmhba1:0:1 with a Fixed multipathing policy.
The # vmkmultipath -s vmhba1:0:1 -r vmhba2:0:1 -e vmhba2:0:1 command sets and enables vmhba2:0:1 with a Preferred multipathing policy. ESX 3.x commands The # esxcfg-mpath --policy=mru --lun=vmhba0:0:1 command sets vmhba0:0:1 with an MRU multipathing policy. The # esxcfg-mpath --policy=fixed --lun=vmhba0:0:1 command sets vmhba1:0:1 with a Fixed multipathing policy. The # esxcfg-mpath --preferred --path=vmhba2:0:1 --lun=vmhba2:0:1 command sets vmhba2:0:1 with a Preferred multipathing policy. ESX 4.x commands The # esxcli nmp device setpolicy --device naa.6001438002a56f220001100000710000 --psp VMW_PSP_MRU command sets device naa.6001438002a56f220001100000710000 with an MRU multipathing policy. The # esxcli nmp device setpolicy --device naa.6001438002a56f220001100000710000 --psp VMW_PSP_FIXED command sets device naa.6001438002a56f220001100000710000 with a Fixed multipathing policy. The # esxcli nmp fixed setpreferred --device naa.6001438002a56f220001100000710000 --path vmhba1:C0:T2:L1 command sets device naa.6001438002a56f220001100000710000 with a Preferred multipathing policy. NOTE: Each LUN can be accessed through both EVA storage controllers at the same time; however, each LUN path is optimized through one controller. To optimize performance, if the LUN multipathing policy is Fixed, all servers must use a path to the same controller. You can also set the multipathing policy from the VMware Management User Interface (MUI) by clicking the Failover Paths tab in the Storage Management section and then selecting Edit link for each LUN whose policy you want to modify.

25 Objects in your system are in use, and their state prevents the operation you wish to perform.
Case 7: Physical Store erase volume: The disk is a part of a disk group and cannot be erased. Case 8: Storage cell discard: The storage cell contains one or more virtual disks or LUN presentations. Case 9: Storage cell client discard: = The EVA host contains one or more LUN presentations. Case 10: SCVD discard: The virtual disk contains one or more derived units and cannot be discarded. This may indicate a programming error. Case 11: SCVD set capacity: The capacity cannot be modified because the virtual disk has a dependency on either a snapshot or snapclone. Case 12: SCVD set disk cache policy: The virtual disk cache policy cannot be modified while the virtual disk is presented and enabled. Case 13: SCVD set logical disk: The logical disk attribute is already set, or the supplied logical disk is already a member of another virtual disk. Case 14: VOLUME set requested usage: The disk volume is already a member of a disk group or is in the state of being removed from a disk group. Case 15: GROUP discard: The Continuous Access group cannot be discarded as one or more virtual disk members exist. The operation cannot be performed because the object does not exist. This can indicate a user or program error. VOLUME set requested usage: The disk volume set requested usage cannot be performed because the disk group does not exist. This can indicate a user or program error.
26 Parameter Object Does Not Exist
Case 1: The operation cannot be performed because the object does not exist. This can indicate a user or program error. Case 2: DERIVED UNIT discard: The operation cannot be performed because the virtual disk, snapshot, or snapclone does not exist or is still being created. Case 3: VOLUME set requested usage: The operation cannot be performed because the target disk volume does not exist. This can indicate a user or program error. Case 4: GROUP get name: The operation cannot be performed because the Continuous Access group does not exist. This can indicate a user or program error.
27 Target Object Does Not Exist
Case 1: Report the error to product support. Case 2: Retry the request at a later time. Case 3: Report the error to product support. Case 4: Report the error to product support.
28 Timeout 29 Unknown ID 30 Unknown Parameter Handle 31 Unrecoverable Media Error 32 Invalid State 33 Transport Error 34 Volume is Missing 35 Invalid Cursor 36 Invalid Target for the Operation 37 No More Events 38 Lock Busy 39 Time Not Set

EMI enclosure enclosure address bus
Enterprise Virtual Array rack
ESD event Event Information Packet Event Number Evt No. exabyte

fabric failover

Fault Management Code FC HBA
See FMC. Fibre Channel host bus adapter. An interchangeable term for Fibre Channel adapter. See also FCA. Fibre Channel adapter. An adapter used to connect the host server to the fabric. Also called a host bus adapter (HBA) or a Fibre Channel host bus adapter (FC HBA). See also FC HBA. Federal Communications Commission. The federal agency responsible for establishing standards and approving electronic devices within the United States. Fibre Channel Protocol. The mapping of SCSI-3 operations to Fibre Channel. The optical media used to implement Fibre Channel. The technology where light is transmitted through glass or plastic (optical) threads (fibers) for data communication or signaling purposes. A transmission medium designed to transmit digital signals in the form of pulses of light. Fiber optic cable is noted for its properties of electrical isolation and resistance to electrostatic contamination. The international spelling that refers to the Fibre Channel standards for optical media. A data transfer architecture designed for mass storage devices and other peripheral devices that require very high bandwidth. See FCA. Fibre Channel Arbitrated Loop. The American National Standards Institutes (ANSI) document that specifies arbitrated loop topology operation See FRU. The act of writing dirty data from cache to a storage media. Fault Management Code. The HP Command View EVA display of the Enterprise Storage System error condition information. A storage industry dimensional standard for 3.5 inch (89 mm) and 5.25 inch (133 mm) high storage devices. Device heights are specified as low-profile (1 inch or 25.4 mm), half-height (1.6 inch or 41 mm), and full-height (5.25 inch or 133 mm). Field Programmable Gate Array. A programmable device with an internal array of logic blocks surrounded by a ring of programmable I/O blocks connected together through a programmable interconnect. The number of cycles that occur in one second expressed in Hertz (Hz). Thus, 1 Hz is equivalent to one cycle per second.
FCC FCP fiber fiber optics fiber optic cable
fibre Fibre Channel Fibre Channel adapter Fibre Channel Loop field replaceable unit flush FMC form factor

frequency

Field Replaceable Unit. A hardware element that can be replaced in the field. This type of replacement can require special training, tools, or techniques. Therefore, FRU procedures are usually performed only by an Authorized Service Representative. The convention of applying an alloy or gray color to a CRU tab, lever or handle to identify the unit as warm-swappable. Host Bus Adapter. See also FCA. A computer that runs user applications and uses the information stored on an array. See FCA. See host. The HSV Controller display that indicates the status of the storage system Fibre Channel links. A connection point to one or more hosts through a Fibre Channel fabric. A host is a computer that runs user applications and that uses (or can potentially use) one or more of the virtual disks that are created and presented by the controller pair. See host ports. A method of element replacement whereby the complete system remains operational during element removal or insertion. Replacement does not interrupt data transfers to other elements. A communications infrastructure device to which nodes on a multi-point bus or loop are physically connected. It is used to improve the manageability of physical cables. Input/Output module. The enclosure element that is the Fibre Channel disk enclosure interface to the host or controller. A 2-digit decimal number portion of the HSV controller termination code display that defines one of 48 locations in the Termination Code array that contains information about a specific event. See also param and TC. A configuration step that binds the controllers together as an operational pair and establishes preliminary data structures on the disk array. Initialization also sets up the first disk group, called the default disk group. See I/O module. See ambient temperature. A set of protocols used between components such as cables, connectors, and signal levels. Just a Bunch of Disks. A number of disks connected to one or more controllers.

gray-color

HBA host Host Bus Adapter host computer host link indicator host ports
host-side ports hot-pluggable

I/O module IDX

initialization
input/output module intake temperature interface
laser Last Fault View Last Termination Error Array License Key link logon loop pair
A device that amplifies light waves and concentrates them in a narrow, very intense beam. An HSV Controller display defining the last reported fault condition. See LTEA. A WWN-encoded sequence that is obtained from the license key fulfillment website. A connection ports on Fibre Channel devices. The link is a full duplex connection to a fabric or a simplex connection loop devices. Also called login, it is a procedure whereby a user or network connection is identified as being an authorized network user or participant. A Fibre Channel attachment a controller and physical disk drives. Physical disk drives connect to controllers through paired Fibre Channel arbitrated loops. There are two loop pairs, designated loop pair 1 and loop pair 2. Each loop pair consists of two loops (called loop A and loop B) that operate independently during normal operation, but provide mutual backup in case one loop fails. Last Termination Event Array. A two-digit HSV Controller number that identifies a specific event that terminated an operation. Valid numbers range from 00 to 47. Logical Unit Number. A SCSI convention used to identify elements. The host sees a virtual disk as a LUN. The LUN address a user assigns to a virtual disk for a particular host will be the LUN at which that host will see the virtual disk. The HP Command View EVA software that controls and monitors the Enterprise storage system. The software can exist on more than one management server in a fabric. Each installation is a management agent. Significant occurrence to or within the management agent software, or an initialized storage cell controlled or monitored by the management agent. See MTBF. A notation denoting a multiplier of 1 million (1,000,000). Information that a controller pair writes on the disk array. This information is used to control and monitor the array and is not readable by the host. See m. A process in which half of each controllers write cache mirrors the companion controllers write cache. The total memory available for cached write data is reduced by half, but the level of protection is greater. The act of creating an exact copy or image of data. Mean Time Between Failures. The average time from start of use to first failure in a large population of identical systems, components, or devices.