hp enterprise data warehouse appliance support pack user guide · csv format ... smp server...

HP Enterprise Data Warehouse Appliance Support Pack v1.44 User Guide

Abstract This document details the firmware and driver versions supported in HP EDW Support Pack v1.44 including MRA v1.41 for the Gen8 topologies and MRA v1.42 for the G7 topologies. Also included are details and best practices for keeping the appliance tuned for maximum performance. The Support Pack documentation audience includes data engineers, architects, BI users, and executives.

Part Number: 675165-008 August 2013 Edition: 8

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

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.

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.

Microsoft®, Windows®, and Windows Server® are U.S. registered trademarks of Microsoft Corporation. Intel® is a trademark of Intel Corporation in the U.S. and other countries. Java is a registered trademark of Oracle and/or its affiliates.

Contents 3

Contents

Introduction .................................................................................................................................. 6 Executive summary ....................................................................................................................................... 6

Parameter and password usage ..................................................................................................... 7 Parameters common to all scripts ................................................................................................................... 7

Password rules common to all devices .................................................................................................. 7 Entering domain and device type passwords ........................................................................................ 8 Entering individual device passwords ................................................................................................... 8 Prompt for individual passwords automatically ...................................................................................... 8 Getting interactive help on parameter availability .................................................................................. 9

EDW Password: Appliance password management ........................................................................ 10 Changing the common devices password ..................................................................................................... 10

EDW Update: Enterprise Data Warehouse update process .............................................................. 11 EDW_Password.ps1 script information ......................................................................................................... 11

Updating a single device type ........................................................................................................... 12 Updating the server using a separate CP file ....................................................................................... 12

Implementation options ............................................................................................................................... 12 Individual node update example .................................................................................................................. 13 Appliance update using the EDW update script............................................................................................. 13 Updating certain parts of the appliance only ................................................................................................. 17 Firmware ................................................................................................................................................... 19

Required firmware per node .............................................................................................................. 19 Firmware deployment options ............................................................................................................ 19 HP ProLiant G6 and G7 firmware by node ......................................................................................... 20 HP ProLiant Gen8 firmware by node .................................................................................................. 20 HP EDW v1.3 or prior firmware switches and MSA ............................................................................. 20 HP EDW v1.4 firmware switches and MSA ......................................................................................... 20

Drivers ...................................................................................................................................................... 22 HP ProLiant G6 and G7 drivers by node ............................................................................................ 22 HP ProLiant Gen8 drivers by node ..................................................................................................... 22

EDW Validation: Validating firmware and driver version compliance ............................................... 24 MRA_Check.ps1 script information .............................................................................................................. 24

EDW Reporting: Generating Appliance Reports ............................................................................. 26 EDW_Reporting.ps1 script information ......................................................................................................... 26

CSV Format ..................................................................................................................................... 27 HTML format .................................................................................................................................... 28

Physical Disk Properties Report excerpt ......................................................................................................... 29 CSV format ...................................................................................................................................... 29 HTML format .................................................................................................................................... 30

Serial Number Report excerpt...................................................................................................................... 31 CSV format ...................................................................................................................................... 31 HTML format .................................................................................................................................... 32

EDW Diagnostics: Appliance diagnostic ....................................................................................... 33 Appliance diagnostics ................................................................................................................................ 33

Contents 4

Default IP naming schema ............................................................................................................ 35 Device interface names ............................................................................................................................... 35 External device names ................................................................................................................................ 35 Storage device names ................................................................................................................................ 36 Switch device names .................................................................................................................................. 36 Node device names ................................................................................................................................... 36 Default IP address for G7 and Gen8 test or development racks ....................................................................... 37 Default IP addresses for single data racks (G7) .............................................................................................. 38

Control rack (HP EDW v1.3 or prior) ................................................................................................. 38 Data rack (HP EDW v1.3 or prior) ..................................................................................................... 39

Default IP address for single data racks (Gen8) ............................................................................................. 42 Gen8 control rack ............................................................................................................................ 42 Gen8 data rack ............................................................................................................................... 43

Custom IP: Using custom IP address ranges .................................................................................... 45 Using the Custom IP Range script to alter non-default IP ranges ....................................................................... 45

Troubleshooting .......................................................................................................................... 46 Redundancy property error (EDW diagnostics - G7) ...................................................................................... 46 Status 138, unknown error (all tools - Gen8 platform) .................................................................................... 47 Found string error (various tools – Gen8 platform) ......................................................................................... 47 Device timeout issue ................................................................................................................................... 48

How to change P2000 password using the SMU browser utility ............................................................ 48 Device timeout MRA Check example .................................................................................................. 50

MRA Check not returning version information when running TS240P004-02 P2000 firmware version ................ 50 Manual P2000 firmware downgrade workaround ......................................................................................... 51 P2000 single device update ........................................................................................................................ 51 Automated reboot locks up with forced update .............................................................................................. 51 HP SUM repository errors ............................................................................................................................ 51 HP SUM BroadComNIC update ................................................................................................................... 51 HP SUM manual downgrade to resolve update issues .................................................................................... 51 Manually updating the system BIOS ............................................................................................................. 52 Update process interrupted or stuck.............................................................................................................. 52 Fibre Channel Switch web interface stuck at 19% while initializing ................................................................. 52 Downgrading the ProCurve Ethernet switch ................................................................................................... 52 Downgrade System ROM on DL370 G6 (Landing Zone node) from version 5/5/2011 or newer ....................... 53 Node not accessible over the private network ............................................................................................... 53 Manual reboot required after ping all error ................................................................................................... 53

Updating the firmware ................................................................................................................ 55 HP Smart Update Manager ......................................................................................................................... 55

Firmware and driver updates using HP Smart Update Manager ............................................................ 55 Fibre Channel HBA firmware upgrade .......................................................................................................... 61 InfiniBand 4xDDR DP HCA firmware upgrade ............................................................................................... 64 InfiniBand FDR switch firmware upgrade ...................................................................................................... 65 HP P2000 G3 FC Controller firmware upgrade ............................................................................................. 66 QLogic IB 9040 and 9024 Switch firmware upgrade .................................................................................... 70 Voltaire IB 4036 Switch firmware upgrade ................................................................................................... 76 Fibre Channel SAN Switch firmware upgrade ............................................................................................... 78 Fibre Channel SAN Switch firmware downgrade .......................................................................................... 80 ProCurve 2810-24/48 G Switch firmware upgrade ...................................................................................... 80 HP Software Updates EDW Support Pack file ................................................................................................ 83 iLO reboot usage ....................................................................................................................................... 83

Support and other resources ........................................................................................................ 85

Contents 5

Contacting HP Enterprise Data Warehouse support ....................................................................................... 85 Before you contact HP ................................................................................................................................ 85 HP contact information ................................................................................................................................ 85 Other resources ......................................................................................................................................... 86

Acronyms and abbreviations ........................................................................................................ 87

Documentation feedback ............................................................................................................. 89

Index ......................................................................................................................................... 90

Introduction 6

Introduction

Executive summary HP EDW is a purpose-built solution developed through collaborative engineering efforts between HP and Microsoft. Designed to simplify the implementation and management of an enterprise data warehouse environment, HP EDW provides high-speed performance through MPP and is optimized for Microsoft SQL Server 2008 R2, Parallel Data Warehouse Edition.

Periodically updating firmware and drivers keeps the HP EDW Appliance running at maximum performance. These critical updates maintain the overall health of servers, storage arrays, switches, and all components included in the hardware stack.

Developing a methodology for maintaining firmware on a complex hardware stack like the multi-server, MPP appliance powered by SQL Server 2008, R2 Parallel Data Warehouse Edition, and HP EDW, requires a number of considerations. In addition to requiring a specific, tested firmware and driver software stack, the appliance requires consistent firmware and driver versions across all similar nodes and subsystems throughout the appliance. All maintenance procedures require careful coordination with Microsoft support.

HP EDW is a scale-out, shared-nothing appliance architecture that operates as a single entity, so the approach to servicing the unit, including hardware replacement or driver and firmware updates, contrasts with scale-up, SMP server architecture maintenance methodologies.

The HP Parallel Data Warehouse V2 upgrade requires no hardware update, so HP Technical Support involvement might not be necessary. Download the v1.44 Support Pack, upgrade your firmware, and coordinate directly with Microsoft for the PDW v2 software upgrade.

Parameter and password usage 7

Parameter and password usage

Parameters common to all scripts This section describes the set of parameters that are common across all scripts and the individual parameters found in each script.

The most common script usage calls the scripts without any parameters, and then the script prompts for required information.

Script parameter Description

-DomainPassword <password> Domain password used to access host devices.

-DevicesPassword <password> Common device password used to access individual/external devices.

-P2000Pw <password> P2000 password used when this password is different from the common device password.

-IbSwitchPw <password> InfiniBand switch password used when this password is different from the common device password.

-EthSwitchPw <password> Ethernet switch password used when this password is different from the common device password.

-FcSwitchPw <password> Fibre Channel switch password used when this password is different from the common device password.

-PromptForDevicePasswords Specify different passwords for individual devices; interactive mode only.

-IgnoreNodeCheck Execute scripts skipping unreachable nodes if applicable. -h Request help with parameter usage (alias of help). -help Request help with parameter usage (alias of h).

Password rules common to all devices The Support Pack Password Management script enforces password rules for all devices. Follow these rules for both individual password changes and when creating a common password.

Rule Description

Length The password length must be eight characters long.

Reusability The password can not be reused.

Spaces No spaces are allowed in the password.

Additional rules (3 of 4 must be followed) At least one uppercase alphabet character must be present.

Additional rules (3 of 4 must be followed) At least one lowercase alphabet character must be present.

Additional rules (3 of 4 must be followed) At least one numeric value must be present (0-9).


Rule Description

Additional rules (3 of 4 must be followed) Only the following non-alphanumeric character can be used (all other special characters are forbidden): ! * # + ? ~ =

Entering domain and device type passwords Provide the domain administrator and device passwords as follows (MRA_Check is used as an example):

powershell .\MRA_Check.ps1 <Domain administrator password> <External devices password>

You can use the domain and device passwords without a parameter name as long as they are sent in the correct order (position).

To specify the parameters by name, use this example: powershell .\MRA_Check.ps1 -DomainPassword <Domain administrator password> -DevicesPassword <External devices password>

Entering individual device passwords To specify different passwords for individual devices, add password parameters as needed from the available list. Use any combination of the following parameters:

• P2000Pw

• IbSwitchPw

• EthSwitchPw

• FcSwitchPw

If you include all of the parameters, you do not need to use the <External devices password>. Examples include the following:

• powershell .\MRA_Check.ps1 <Domain administrator password> <External devices password> -P2000pw <P2000 device password>

• powershell .\MRA_Check.ps1 <Domain administrator password> <External devices password> -EthSwitchPw <Ethernet switch device password> -FcSwitchPw <Fibre channel switch device password>

• powershell .\MRA_Check.ps1 <Domain administrator password> -P2000pw <P2000 device password> -IbSwitchPw <InfiniBand switch device password> -EthSwitchPw <Ethernet switch device password> -FcSwitchPw <Fibre channel switch device password>

Prompt for individual passwords automatically Use the PromptForDevicePasswords parameter o automatically prompt for individual device passwords. The following example uses MRA_Check.

powershell .\MRA_Check.ps1 -PromptForDevicePasswords


Getting interactive help on parameter availability To request that the script display a list of supported parameters, use h or help parameters as follows: (MRA_Check is used as an example)

powershell .\MRA_Check.ps1 -h

EDW Password: Appliance password management 10

EDW Password: Appliance password management

Changing the common devices password To change the common devices password:

1. Open a command window.

2. Change to c:\EDW Support Pack v1.44\EDW_Update\.

3. Run the following script: powershell .\EDW_Password.ps1

The script automatically prompts for credentials and new passwords.

You can provide passwords using parameters as follows: powershell .\EDW_Password.ps1 <Domain administrator password> <External devices password> <New external devices password> <New external devices password confirmed>

You can use all four parameters positionally. If you name the parameters individually, as shown in the following example, you can use them in any order:

powershell .\EDW_Password.ps1 -DomainPassword <Domain administrator password> -DevicesPassword <External devices password> -newpassword1 <New external devices password> -newpassword2 <New external devices password confirmed>

EDW Update: Enterprise Data Warehouse update process 11

EDW Update: Enterprise Data Warehouse update process

EDW_Password.ps1 script information In addition to the common parameters described in "Parameters common to all scripts (on page 7)," the EDW Password.ps1 script includes the following parameters. Parameter Description

-newpassword1 <password> ("Changing the common devices password" on page 10)

The new (common) devices password

-newpassword2 <password> ("Changing the common devices password" on page 10)

The new (common) devices password confirmation

-newP2000Pw1 <password> The new P2000 device password -newP2000Pw2 <password> The new P2000 password confirmation

-newIbSwitchPw1 <password> The new InfiniBand switch password -newIbSwitchPw2 <password> The new InfiniBand switch password

confirmation -newEthSwitchPw1 <password> The new Ethernet switch password

-newEthSwitchPw2 <password> The new Ethernet switch password confirmation

-newFcSwitchPw1 <password> The new Fibre Channel switch password -newFcSwitchPw2 <password> The new Fibre Channel switch password

confirmation -newiLoPw1 <password> The new iLO password -newiLoPw2 <password> The new iLO password confirmation -iLoPw <password> Current iLO password


Updating a single device type 1. Open a command window.

2. Change to the EDW Support Pack directory for your version: c:\EDW Support Pack <version>\EDW_Update\

3. Run the following script: powershell .\EDW_Update.ps1 –UpdateSingleDevice <device>

o Replace <device> with any available and supported individual updates.

o For a list of supported updates, see "EDW_Password.ps1 parameters (EDW_Update.ps1 script parameters "EDW_Password.ps1 script information" on page 11)."

The script automatically prompts for credentials. You can also use common parameters as described in "Parameters common to all scripts (on page 7)."

Updating the server using a separate CP file 1. Open a command window.


3. Run the following script: powershell .\EDW_Update.ps1 <Domain administrator password> –ApplyServerCP <filename>

o Replace <filename> with the CP filename.

o Do not provide path information. The script expects to find the CP file in the same folder as the script.

Implementation options The EDW Support Pack contains the firmware, drivers, and tools necessary to update the EDW topology to a given MRA Identifier. New Reference IDs for a given topology are released with the software updates as new driver and firmware combinations are tested and validated. All updates for the HP EDW v1.3 or earlier topologies can be implemented using the EDW_Update.ps1 utility. Specific updates can be performed


manually for the HP EDW v1.3 or earlier topology. All updates for the HP EDW v1.4 topology must be performed manually.

For more information about updating the firmware, see "Updating the firmware (on page 55)."

The following table includes scenarios that are supported from the EDW Support Pack.

Type Approach Script

Full appliance update

Use the EDW_update.ps1 script to update all of the firmware and drivers to comply with a given MRA. Use the script when updating to a new MRA Reference ID. This update requires taking the EDW appliance offline for servicing. Coordinate the update with Microsoft Support.

EDW_update.ps1

Individual node or component update

HP recommends using the EDW_update.ps1 script to update firmware and drivers on a single node or component. You can also use the appropriate individual scripts and/or smart components to perform a local update on the node or component. A common use-case requiring individual updates occurs when a customer replaces a single node within the appliance. Replacing a single node requires taking the node offline. The rest of the appliance is still operational. Coordinate the update with Microsoft Support.

EDW_update.ps1 (preferred method) The alternative, manual approach uses various individual files.

Individual node update example If a compute node fails, update the firmware and drivers before using the SQL Server PDW management console to run the node recovery process.

1. Download the appropriate EDW Support Pack from the HP Software Updates website (http://www.hp.com/go/hpsoftwareupdatesupport). For details on downloading the most current Support Pack, see the HP Enterprise Data Warehouse Appliance Support Pack Release Note for your version.

2. On a server configured separately and outside of the EDW appliance, log in to iLO.

3. Start the integrated remote console with a user account that has domain administrator privileges.

4. Mount the HP OEM version of Windows Server 2008 SP2 (included with the HP EDW appliance) to load the Windows operating system on the server.

5. Unzip the EDW Support Pack .zip file to c:\ to speed up the deployment.

6. Execute HP SUM from c:\EDW Support Pack v1.44\EDW_Update\HPSUM\hpsum.exe.

7. Set the local host as the default target, and then apply the HP Enterprise Data Warehouse Release Set to apply the HP SUM firmware and drivers to the node.

8. To upgrade the adapters, see "Fibre Channel HBA firmware upgrade (on page 61)" and "InfiniBand 4xDDR DP HCA firmware upgrade (on page 64)."

The server is now compliant with the existing MRA. To start the node replacement process, contact Microsoft Support.

Appliance update using the EDW update script Network drivers and firmware are updated as part of the upgrade process. Manage the update process while connected to MAD01 using the iLO connection.

http://www.hp.com/go/hpsoftwareupdatesupport�


IMPORTANT: HP has designed the update process to work on a functional appliance that has the EDW appliance services stopped. Be sure that the appliance is fully functional before using these scripts.

To update the EDW appliance to the latest MRA version:

1. Download the latest EDW Support Pack from the HP Software Updates website (http://www.hp.com/go/hpsoftwareupdatesupport). For details on downloading the most current Support Pack, see the HP Enterprise Data Warehouse Appliance Support Pack Release Note for your version.

2. Copy the EDW Support Pack to the management node <appliance name>-MAD01.

3. Unzip the EDW Support Pack to c:\.

4. Open a command window, change to c:\EDW Support Pack v1.44\EDW_Update\, and then run powershell .\EDW_update.ps1.

IMPORTANT: Perform this process while using the iLO connection to MAD01. Regular network connections are disabled during the update.

5. Enter the credentials needed to connect to the domain controller and the external devices, or provide credentials on the command line.

The script runs a quick check to make sure all appliance devices are responsive. If this check fails, an on-screen error message appears and the execution stops.

IMPORTANT: The -IgnoreNodeCheck parameter ignores this check, but it should be used only when advised by the support team.

IMPORTANT: The -force command syntax is used in v1.44 or later, while the force command syntax is used in versions prior to v1.44.

The script automatically cycles through all of the steps that are described in this section. To override or downgrade firmware/driver versions, use the -force parameter on the command line. The



deployment time varies based on the topology and number of data racks. The following illustration shows the timing for a one data rack topology.

After the update is complete, the script reboots the EDW appliance automatically with the MAD01 node first and then all other nodes.

6. After MAD01 restarts, open HPC Cluster Manger by selecting Start>Programs>Microsoft HPC Pack>HPC Cluster Manager.


7. Select Node Management, and then verify that all nodes are operational and that OK appears in the Node Health column.

8. After all nodes are operational, make sure you are in the c:\EDW Support Pack

v1.44\EDW_Update\tools directory.

9. Run powershell .\EDW_align.ps1 to verify that all cluster nodes have the correct primary host selected.

10. Use DwConfig to start PDW services.

HP provides additional script parameters for those customers choosing to implement separate passwords for each appliance device type (P2000, Ethernet switches, InfiniBand switches, and Fibre Channel switches).


Script parameter Description -P2000Pw <password> If the P2000 takes a password that is

different from the common device password, use this parameter to specify the P2000 password.

-IbSwitchPw <password> If the InfiniBand switch takes a password that is different from the common device password, use this parameter to specify the InfiniBand switch password.

-EthSwitchPw <password> If the Ethernet switch takes a password that is different from the common device password, use this parameter to specify the Ethernet switch password.

-FcSwitchPw <password> If the Fibre Channel switch takes a password that is different from the common device password, use this parameter to specify the Fibre Channel switch password.

-PromptForDevicePasswords Only used in interactive mode. Use this parameter if you want to be prompted to specify different passwords for individual device types.

The HP support team might instruct you to downgrade or rewrite firmware and drivers in some cases. Use the –force parameter to indicate a forced downgrade/rewrite.

By default, the script only upgrades the components that need to be upgraded. Do not use the –force parameter for a mass update. Mass force updates with HP SUM are not supported and could lead to unexpected results.

IMPORTANT: The -IgnoreNodeCheck parameter ignores this check, but it should be used only when advised by the support team.

IMPORTANT: The -force command syntax is used in v1.44 or later, while the force command syntax is used in versions prior to v1.44.

Updating certain parts of the appliance only The EDW_update.ps1 script only updates the components that are out of compliance with the latest MRA version. However, HP recognizes that in certain cases it is helpful to have a way to upgrade and downgrade only certain parts of the appliance due to time constraints. Additional EDW_update.ps1 parameters that enable you to upgrade and downgrade only certain parts of the appliance are provided.

IMPORTANT: These parameters offer the possibility to change the appliance firmware and drivers that are out of compliance with the MRA revision. These types of changes should only be performed when advised by the HP support team.



-UpdateSingleDevice <device type name> The name of a single device type to update. If this parameter is set, then only that device type is updated. Available device type names: • HPSUM • FC_HBA • IB_HCA • NC375i • P2000 • FC_Switch • IB_Switch • ETH_Switch To update more than one device, you must write a script to execute this script multiple times. Note that HPSUM applies upgrades to drivers and firmware. Other updates apply upgrades to firmware only.

-ApplyP2000CP <filename> Use this parameter to update P2000 devices with a specific P2000 CP file. Place the CP file in the same folder as the EDW_update.ps1 script. Pass the CP filename without path information. The P2000Pw parameter must be used to provide the P2000 password in this case. Obtain P2000 CP files by going to the HP Support & Drivers website (http://www.hp.com/go/support) and searching for updates for P2000 storage.

-ApplyServerCP <filename> Use this parameter to update servers with a specific CP file. Place the CP file in the same folder as the EDW_update.ps1 script. Pass the CP filename without path information. Obtain server CP files by going to the HP Support & Drivers website (http://www.hp.com/go/support) and looking for updates for individual servers. To force an update, use the -Force parameter.

http://www.hp.com/go/support�

http://www.hp.com/go/support�


Firmware

Required firmware per node The following tables list the required firmware components and the assigned nodes for the HP EDW appliance. HP Smart Update Manager is used to install most of the firmware and drivers required for devices in the server nodes as noted in the Installed using HP SUM column.

The table headings use the following abbreviations.

• MAD—Management nodes

• CTL—Control nodes

• CMP—Compute nodes

• LZ—Landing Zone node

• BU—Backup node

IMPORTANT: The EDW_Update.ps1 utility only supports updates for G7 and G6 firmware and drivers. The Gen8 firmware and drivers are listed for informational purposes only. The HP EDW v1.4 implementation ships from the HP factory with the current firmware and drivers.

Firmware deployment options Four key terms are used when describing a typical firmware update use case scenario.

• Local installation—Runs on the physical hardware being updated; for example, when you execute a utility on a server to update the system ROM.

• Remote installation—Runs on one system but updates other physical targets; for example, running the physical tool on a workstation or system like MAD01, that updates firmware remotely.

• Online installation—Installation occurs while the host processor is running in your normal environment; for example, when running Windows Server 2008, the update takes place under this environment and you do not need to boot to a special environment to update the firmware. An online installation does not mean that a reboot is not necessary for the firmware to be activated.

• Offline installation—Installation occurs while the server is booted to a special environment that prevents normal operations until the firmware updates are complete and the server reboots; for example, when you boot to the Firmware Maintenance CD to deploy Emulex, QLogic, and Brocade Fibre Channel HBA firmware updates. These updates require that I/O operations cease on the adapters during the update, which requires booting to a special environment.

Use these terms together to designate the type of environment required for firmware updates to occur, such as local-online or remote-online. HP specifically designed the EDW firmware update process as a remote-online process, driven by a number of scripts.


HP ProLiant G6 and G7 firmware by node

Driver MAD CTL CMP LZ BU Installed using HP SUM

SA 410i controller X X X X X X

NC382i X X X X X

NC375i — — — X — —

iLO3 X X X X X

iLO2 — — — X — X

SAS Expander card — X — X — X

DL360G7 BIOS X — X — — X

DL380G7 BIOS — X — — X X

DL370G6 BIOS — — — X X X

82E DP FC HBA — X X — X —

IB 4x DDR PCIe DP HCA X X X X X —

HP ProLiant Gen8 firmware by node


SA 420i controller X X X X X X

NC 331FLR FlexLOM X X X X X X

iLO4 X X X X X X

DL360Gen8 BIOS X — X — — X

DL380Gen8 BIOS — X — X X X

82E DP FC HBA — X X — X X

Mellanox IB FDR card X X X X X X

HP EDW v1.3 or prior firmware switches and MSA Device:

• HP P2000 G3 FC Controllers

• HP 8/8 16 port SAN Switch


• ProCurve Switch 2810-24 G

• Qlogic IB DDR 9040 Switch

• Qlogic IB DDR 9024 Switch

• Voltaire IB QDR 4036 Switch

HP EDW v1.4 firmware switches and MSA Device:


• HP P2000 G3 FC Controllers



• ProCurve Switch 2810-24 G

• Mellanox IB FDR 36p Switch


Drivers

HP ProLiant G6 and G7 drivers by node


iLO 3 management controller driver (all but LZ)

X X X — X X

Intel Chipset Driver (all servers)

X X X X X* X

Storport Driver for HP Emulex HBA (all fibre attached servers)

— X X — X X

Lights-Out Management Interface Driver

— — — X X* X

iLO 2 Management Controller Driver (LZ)

— — — X X* X

SAS Controller Driver X X X X X X

HP NC-Series QLogic nx3 Multifunction Driver

— — — X — X

NC-Series Broadcom 1Gb network driver

X X X — X X

Insight Management X X X X X X

Mellanox IB driver** X X X X X —

*The Test/Dev topology uses the DL370G6 server for the backup node with the HP EDW v1.3 and prior implementation, while the HP EDW v1.4 implementation uses the DL380Gen8 server. **The HP EDW Support Pack installation does not include this component. For more information, contact HP Support.

HP ProLiant Gen8 drivers by node


iLO 4 management controller driver

X X X X X X

iLO 4 Channel interface driver

X X X X X X

Storport Driver for HP Emulex HBA (all fibre attached servers)

— X X — X X

SAS Controller Driver X X X X X X

NC 331FLR FlexLOM driver

X X X X X X

Insight Management Agents

X X X X X X


Combined Chipset Driver X X X X X X

Matrox G200 Video Driver

X X X X X X

HP Online Diagnostics X X X X X X

Mellanox IB driver* X X X X X —

*The HP EDW Support Pack installation does not include this component. For more information, contact HP Support.

EDW Validation: Validating firmware and driver version compliance 24

EDW Validation: Validating firmware and driver version compliance

MRA_Check.ps1 script information To verify compliance with the latest MRA version:

1. Download the latest EDW Support Pack following the instructions in the Download and Installation section.

2. Open a command window and change to the c:\EDW Support Pack <version>\EDW_Update\ directory.

3. Run powershell .\MRA_check.ps1.

4. Enter the credentials needed to connect to the external switches and the domain controller, or provide credentials on the command line: Powershell .\MRA_check.ps1 <Domain administrator password> <External devices password>

For complete usage information, use the -help parameter.

EDW Validation: Validating firmware and driver version compliance 25

The script checks your configuration against all known MRA configurations. The following output shows an excerpt from MRA Check. The output displays all of the components that have the wrong version and provides information about the expected version. This output appears only for the closest MRA version.

The script runs a quick check to make sure that all appliance devices are responsive. If this check fails, an on-screen error message appears and the execution stops. The output displays all of the components that have the wrong version and provides information about the expected version. This output appears only for the closest MRA version.

HP provides the following, additional script parameters for those customers choosing to implement separate passwords for each appliance device type (P2000, Ethernet switches, InfiniBand switches, and Fibre Channel switches).


-P2000Pw <password> If the P2000 takes a password that is different from the common device password, use this parameter to specify the P2000 password.

-IbSwitchPw <password> If the InfiniBand switch takes a password that is different from the common device password, use this parameter to specify the InfiniBand switch password.

-EthSwitchPw <password> If the Ethernet switch takes a password that is different from the common device password, use this parameter to specify the Ethernet switch password.

-FcSwitchPw <password> If the Fibre Channel switch takes a password that is different from the common device password, use this parameter to specify the Fibre Channel switch password.

-PromptForDevicePasswords Only used in interactive mode. Use this parameter if you want to be prompted to specify different passwords for individual device types.

EDW Reporting: Generating Appliance Reports 26

EDW Reporting: Generating Appliance Reports

EDW_Reporting.ps1 script information The Support Pack includes the EDW_Reporting.ps1 script that generates all reporting for the EDW Support Pack in CSV and HTML formats.

To execute the script:


2. Change to c:\EDW Support Pack v1.40\EDW_Update\, and then run powershell .\EDW_Reporting.ps1.

The following parameters indicate the report type and format in addition to the common script parameters. Default parameters are used if parameters are not provided. For more information, see "Parameters common to all scripts (on page 7)." Script parameter Description

-ReportType The ReportType describes one of three reports: Serial (default), HDD or Version

-OutputType The OutputType describes the report format: CSV (default) or HTML

IMPORTANT: All reports generated by the tool are stored in the EDW Update root folder which also contains the five primary calling programs and folder structure.

Name (ReportType) Description File name extractions

Version Report (version) Reports the server, storage, switches, and related device firmware and driver versions information.

VerNumReport.csv and VerNumReport.html

Physical Disk Properties Report (HDD)

Reports physical disk properties including model, serial number, and firmware version.

PhysDiskPropsReport.csv and PhysDiskPropsReport.html

Serial Number Report (serial) Reports the serial numbers and rack location of servers, storage, switches, and related devices.

Serials.csv and Serials.html

Firmware and Driver Version Report excerpt


CSV Format


HTML format


Physical Disk Properties Report excerpt

CSV format


HTML format


Serial Number Report excerpt

CSV format


HTML format

EDW Diagnostics: Appliance diagnostic 33

EDW Diagnostics: Appliance diagnostic

Appliance diagnostics The Support Pack includes diagnostic checks that you can perform using the EDW_Diag.ps1 script. The script tests the following aspects of the appliance status:

• Node and device availability on all assigned IP addresses

• Wiring in accordance with specifications and at the correct speed for each of the following:

o Fibre Channel cabling

o InfiniBand cabling

o Ethernet cabling

• Appliance devices (servers, switches, and storage) to make sure they are in a healthy state

• Status and configuration of physical disk drives

• Server configuration and settings

• Time and time zone settings and synchronization

To perform a diagnostic check:


2. Change to the c:\EDW Support Pack v1.44\EDW_Update\ directory.

3. Run powershell .\EDW_Diag.ps1

o The script prompts for credentials.

o To have the script prompt for individual device passwords, add the –PromptForDevicePasswords parameter.

EDW Diagnostics: Appliance diagnostic 34

o For details of other available parameters see "Parameter and password usage (on page 7)."

Default IP naming schema 35

Default IP naming schema

Device interface names If the site survey indicates a conflict, change the first two octets.

Device Prefix (Appliance Name)

DNS Name IP Address/ Range

Netmask Example Name

Example IP Misc information

BMC IP <appliance name>

BMC[CTL,CMP, MAD,LZ,BU][num]

172.16.5.x 255.255.128.0

HPMTP-BMCCTL02

172.16.5.24

—

iLO IP <appliance name>

RAC[CTL,CMP, MAD,LZ,BU][num]

172.15.6.x 255.255.128.0

HPMTP-RACCTL01

172.16.6.0 —

External Ethernet Interface

N/A Not used DNS [site generated]

[site generated]

N/A TBD Eth 3 = External

Ethernet Interface 1 - Private

N/A Not used DNS 172.16.0.x 255.255.128.0

N/A 172.16.0.12

Eth 1 = Heartbeat Network 1

Ethernet Interface 2 - Private0

N/A Not used DNS 172.16.1.x 255.255.128.0

N/A 172.16.1.12

Eth 2 = Heartbeat Network 2

Infiniband Interface 1 - Application

<appliance name>

[CTL,CMP,LZ,BU, MAD][num]

172.16.128.x

255.255.128.0

HPMTP-CMP01 172.16.128.1

IB 1 = Application Network 1

Infiniband Interface 1 - Application0

<appliance name>

[CTL,CMP,LZ,BU, MAD][num]

172.16.129.x

255.255.128.0

HPMTP-CMP01 172.16.129.1

IB 2 = Application Network 2

Failover Cluster

<appliance name>

WFO[CTL,CMP] [num]

172.16.121.x

255.255.128.0

HPMTP-WFOCMP01

172.16.131.1

Cluster Virtual Network

Virtual Node <appliance name>

SQL[CTL,CMP,LZ, BU][num]

172.16.130.x

255.255.128.0

HPMTP-AQLCMP12

172.16.130.12

Virtual Application Network

SQL Instance (external Ethernet)

Not used DNS

Not used DNS [site generated]

[site generated]

N/A TBD Eth 3 = External

External device names The external IP naming schema is used temporarily for setup purposes.

Name IP address Netmask

<appliance name>MAD01 10.10.10.250 255.255.255.0

<appliance name>MAD02 10.10.10.251 255.255.255.0


<appliance name>BU01 10.10.10.220 255.255.255.0

<appliance name>LZ01 10.10.10.230 255.255.255.0

<appliance name>CTL01 10.10.10.240 255.255.255.0

<appliance name>CTL02 10.10.10.241 255.255.255.0

<appliance name>SQLCTL01 10.10.10.242 255.255.255.0

Storage device names

Device Prefix DNS name IP address Netmask Example name Example IP

Storage (HP or EMC) SP-A IP address

<appliance name>

SA1[CTL,CMP, BU][num]

172.16.2.x 255.255.128.0 HPMTP-SA1CTL01 172.16.2.x

Storage (HP or EMC) SP-B IP address

<appliance name>

SB1[CTL,CMP, BU][num]

172.16.3.x 255.255.128.0 HPMTP-SB1CTL01 172.16.3.x

Switch device names

Device Prefix DNS name IP address Netmask Example name Example IP

Ethernet IP <appliance name>

ETHSW[num] 172.16.4.1-50 255.255.128.0 HPMTP-ETHSW01 172.16.12.1

Fibre IP <appliance name>

FBRSW[num] 172.16.4.51-100 255.255.128.0 HPMTP-FBRSW02 172.16.12.52

IB IP <appliance name>

IBSW[num] 172.16.4.101-150

255.255.128.0 HPMTP-IBSW01 172.16.12.101

PDU IP <appliance name>

PDU[num] 172.16.4.151-200

255.255.128.0 HPMTP-PDU01 172.16.12.151

Node device names

Device Prefix DNS name IP address Misc information

Active Directory Server <appliance name> MAD01-04 x.x.x[250-253] For internal only devices

Control Node - All <appliance name> CTL01-10 x.x.x[240-249] gateway: 172.16.0.250

Compute Node —- Active <appliance name> CMP01-89 x.x.x[1-89] dns1: 172.16.0.250

Compute Node —- Passive

<appliance name> CMP91-99 x.x.x[91-99] dns2: 172.16.0.251

Landing zone Node <appliance name> LZ01-10 x.x.x[230-239] —

Backup Node <appliance name> BU01-10 x.x.x[220-229] —

DOMAIN: naming

<appliance name>.DWPU.LOCAL (example: HPMTP.DWPU.LOCAL)


Default IP address for G7 and Gen8 test or development racks

U loc Device name Port 1private Port 2 private0

Port 3 external

iLO port

U42 — — — — —

U41 — — — — —

U40-U26 — — — — —

U25 — — — — —

U24 — — — — —

U23 — — — — —

U22 <APPLIANCE-NAME>-SWI01 172.16.4.101 — — —

U21 <APPLIANCE-NAME>-MAD01 172.16.0.250 172.16.1.250 Customer assigned

172.16.6.250

U20 <APPLIANCE-NAME>-LZ01 172.16.0.230 172.16.1.230 Customer assigned

172.16.6.230


172.16.6.230


172.16.6.230


172.16.6.230

U16 <APPLIANCE-NAME>-BU01 172.16.0.220 172.16.1.220 Customer assigned

172.16.6.220


172.16.6.220


172.16.6.220


172.16.6.220

U12 <APPLIANCE-NAME>-CTL01 172.16.0.240 172.16.1.240 Customer assigned

172.16.6.240


172.16.6.240

U10 <APPLIANCE-NAME>-CMP01 172.16.0.1 172.16.1.1 — 172.16.6.1


U08 <APPLIANCE-NAME>-SWF01 172.16.4.51 — — —

U07 <APPLIANCE-NAME>-SWE01 172.16.4.1 — — —

U06 <APPLIANCE-NAME>-CTL01MSA01

172.16.2.240 172.16.3.240 — —


172.16.2.240 172.16.3.240 — —

U04 <APPLIANCE-NAME>-MSA01 172.16.2.1 172.16.3.1 — —




PDU A <APPLIANCE-NAME>-PDU01 172.16.4.151 — — —

PDU B <APPLIANCE-NAME>-PDU02 172.16.4.152 — — —


Default IP addresses for single data racks (G7)

Control rack (HP EDW v1.3 or prior)


Port 3 external

iLO port

U42 <APPLIANCE-NAME>-SWI01

172.16.4.101 — — —


172.16.4.102 — — —

U40 - U27 — — — — —

U26 <APPLIANCE-NAME>-BU01JBOD02

— — — —


— — — —


— — — —


— — — —

U22 <APPLIANCE-NAME>-BU01MSA02

172.16.2.221 172.16.3.221 — —


172.16.2.221 172.16.3.221 — —


172.16.2.220 172.16.3.220 — —


172.16.2.220 172.16.3.220 — —


172.16.6.220


172.16.6.220

U16 <APPLIANCE-NAME>-SWF01

172.16.4.51 — — —


172.16.4.52 — — —

U14 <APPLIANCE-NAME>-SWE01

172.16.4.1 — — —


172.16.4.2 — — —


172.16.6.240


172.16.6.240


172.16.6.241


172.16.6.241


172.16.2.240 172.16.3.240 — —



Port 3 external

iLO port


172.16.2.240 172.16.3.240 — —

U06 <APPLIANCE-NAME>-MAD01

172.16.0.250 172.16.1.250 Customer assigned

172.16.6.250



172.16.6.251


172.16.6.230


172.16.6.230


172.16.6.230


172.16.6.230

PDU A <APPLIANCE-NAME>-PDU01

172.16.4.151 — — —

PDU B <APPLIANCE-NAME>-PDU02

172.16.4.152 — — —

Data rack (HP EDW v1.3 or prior)


Port 3 external

iLO port

U42 <APPLIANCE-NAME>-SWIB01

172.16.4.103 — — —

U41 <APPLIANCE-NAME>-SWIB02

172.16.4.104 — — —

U40 — — — — —

U39 — — — — —

U38 — — — — —

U37 — — — — —

U36 — — — — —

U35 <APPLIANCE-NAME>-CMP01

172.16.0.1 172.16.1.1 — 172.16.6.1


172.16.0.2 172.16.1.2 — 172.16.6.2


172.16.0.3 172.16.1.3 — 172.16.6.3


172.16.0.4 172.16.1.4 — 172.16.6.4


172.16.0.5 172.16.1.5 — 172.16.6.5


172.16.0.6 172.16.1.6 — 172.16.6.6


172.16.0.7 172.16.1.7 — 172.16.6.7


172.16.0.8 172.16.1.8 — 172.16.6.8



Port 3 external

iLO port


172.16.0.9 172.16.1.9 — 172.16.6.9


172.16.0.10 172.16.1.10 — 172.16.6.10


172.16.0.91 172.16.1.91 — 172.16.6.91


172.16.4.53 — — —


172.16.4.54 — — —


172.16.4.3 — — —


172.16.4.4 — — —

U20 <APPLIANCE-NAME>-MSA01

172.16.2.1 172.16.3.1 — —


172.16.2.1 172.16.3.1 — —


172.16.2.2 172.16.3.2 — —


172.16.2.2 172.16.3.2 — —


172.16.2.3 172.16.3.3 — —


172.16.2.3 172.16.3.3 — —


172.16.2.4 172.16.3.4 — —


172.16.2.4 172.16.3.4 — —


172.16.2.5 172.16.3.5 — —


172.16.2.5 172.16.3.5 — —


172.16.2.6 172.16.3.6 — —


172.16.2.6 172.16.3.6 — —


172.16.2.7 172.16.3.7 — —


172.16.2.7 172.16.3.7 — —


172.16.2.8 172.16.3.8 — —


172.16.2.8 172.16.3.8 — —


172.16.2.9 172.16.3.9 — —


172.16.2.9 172.16.3.9 — —


172.16.2.10 172.16.3.10 — —



Port 3 external

iLO port


172.16.2.10 172.16.3.10 — —


172.16.4.153 — — —


172.16.4.154 — — —


Default IP address for single data racks (Gen8)

Gen8 control rack


Port 3 external

iLO port


172.16.4.101 — — —


172.16.4.102 — — —

U40-U27 — — — — —


— — — —


— — — —


— — — —


— — — —


172.16.2.221 172.16.3.221 — —


172.16.2.221 172.16.3.221 — —


172.16.2.220 172.16.3.220 — —


172.16.2.220 172.16.3.220 — —


172.16.6.220


172.16.6.220


172.16.4.51 — — —


172.16.4.52 — — —


172.16.4.1 — — —


172.16.4.2 — — —


172.16.6.240


172.16.6.240


172.16.6.241


172.16.6.241


172.16.2.240 172.16.3.240 — —



Port 3 external

iLO port


172.16.2.240 172.16.3.240 — —



172.16.6.250



172.16.6.251


172.16.6.230


172.16.6.230


172.16.6.230


172.16.6.230


172.16.4.151 — — —


172.16.4.152 — — —

Gen8 data rack

U Loc Device name Port 1private

Port 2 private0

Port 3 external

iLO port

U42 <APPLIANCE-NAME>-SWIB01 172.16.4.103

— — —

U41 <APPLIANCE-NAME>-SWIB02 172.16.4.104

— — —

U40 — — — — —

U39 — — — — —

U38 — — — — —

U37 — — — — —

U36 — — — — —










U26 <APPLIANCE-NAME>-CMP10 172.16.0.10

172.16.1.10 — 172.16.6.10

U25 <APPLIANCE-NAME>-CMP91 172.16.0.91

172.16.1.91 — 172.16.6.91

U24 <APPLIANCE-NAME>-SWF03 172.16.4.53

— — —


U Loc Device name Port 1private

Port 2 private0

Port 3 external

iLO port

U23 <APPLIANCE-NAME>-SWF04 172.16.4.54

— — —





















U02 <APPLIANCE-NAME>-MSA10 172.16.2.10

172.16.3.10 — —

U01 <APPLIANCE-NAME>-MSA10 172.16.2.10

172.16.3.10 — —

PDU A <APPLIANCE-NAME>-PDU03 172.16.4.153

— — —

PDU B <APPLIANCE-NAME>-PDU04 172.16.4.154

— — —

Custom IP: Using custom IP address ranges 45

Custom IP: Using custom IP address ranges

Using the Custom IP Range script to alter non-default IP ranges

If you have a conflict with the default 172.16.x.x IP networks, you can alter the scripts in the support pack for non-default IP ranges using the CustomIPrange.ps1 script, found in the Tools folder. Modify the following section to include specific IP networks:

### Please change the below section with custom IP networks based on ### ### your IP networks selection ### $CustomPrivateNetwork="172.17.248" $CustomPrivate0Network="172.17.249" $CustomP2000ANetwork="172.17.250" $CustomP2000BNetwork="172.17.251" $CustomSwitchNetwork="172.17.252" $CustomiLONetwork="172.17.254" $CustomApplicationNetwork="172.17.0" $CustomApplication0Network="172.18.0"

After you have updated this section, run the script from the Tools folder to update all of the EDW Support Pack tools with the provided, non-default IP ranges. You only need to do this once for each EDW Support Pack version that you use.

Verify that the correct IP address octet was changed with the custom numbering per the instructions above. Correcting the IP addresses after changing the wrong octet or using the wrong numbering can be complex and time consuming.

Troubleshooting 46

Troubleshooting

Redundancy property error (EDW diagnostics - G7) The following error occurs when running the G7 EDW Diagnostics (EDW_Diag.ps1) script. This is a known issue occurring after an ILO firmware update. This error does not effect the outcome of the diagnostics and you can ignore it.

Troubleshooting 47

Status 138, unknown error (all tools - Gen8 platform) The following error occurs when running the Gen8 Support Pack scripts. This is a known issue occurring after the required firmware has been updated. You can ignore this error. It has no effect on the outcome of the tool.

Found string error (various tools – Gen8 platform) The following error occurs when running the Gen8 Support Pack scripts. This is a known issue occurring after the required firmware has been updated. You can ignore this error. It has no effect on the outcome of the tool.

EDW Reporting log example

04/25/2013 16:09:36 INFO: Found time string: IL221903FY

04/25/2013 16:09:46 INFO: Found time string: IL221903G1

04/25/2013 16:09:56 INFO: Found time string: IL2217002Y

04/25/2013 16:10:06 INFO: Found time string: IL223100S7

EDW Diagnostics log example

04/25/2013 15:42:10 INFO: Checking all IB cables

04/25/2013 15:42:13 INFO: Found Version string: 00:02:C9:03:00:70:E8:D0

04/25/2013 15:42:15 INFO: Found Version string: 00:02:C9:03:00:70:EA:50

04/25/2013 15:42:18 INFO: Found Version string: 00:02:C9:03:00:6E:D3:70

04/25/2013 15:42:21 INFO: Found Version string: 00:02:C9:03:00:7C:32:00

Troubleshooting 48

Device timeout issue P2000s (MSAs) or other devices can time out during some routines, causing undesirable results. Use the information provided in the table below to resolve timeout issues.

Script name Routine Result

All scripts PINGALL Error message displays on the console and in the log, and then the routine continues. Resolution: Rerun the script.

MRA Check Version check Error message displays on the console and in the log, and then the routine continues. Resolution: Rerun the script.

Diagnostics Disk enclosure check Error message displays on the console and in the log, and then the routine continues. Resolution: Rerun the script.

Reporting Various Error message displays on the console, in the report, and in the log, and then the routine continues. Resolution: Rerun the script.

Password Change common or device type password

The specific P2000 (MSA) IP addresses that are not responding display on the console and in the log, and then the routine continues. All other device passwords, other than the passwords of the P2000 affected, are changed. Resolution: After the common password change routine completes, the user must log into each MSA that was affected and change the password manually using the IP address or addresses provided.

Update (HP EDW v1.3 or earlier)

Update P2000 firmware

Error message displays on the console, in the report, and in the log, and then routine continues. Resolution: Rerun the script.

How to change P2000 password using the SMU browser utility 1. Enter the P2000 (MSA) IP address into a browser. Log in with the user name manager and current

password.

Troubleshooting 49

2. Select Configuration > Users > Modify User.

3. Select the manage user, and then enter the new common password.

4. Click modify user at the bottom of the window.

5. Log out, and then log back in with the new password to verify access.

Troubleshooting 50

Device timeout MRA Check example The following screenshot shows an example of the timeout issue occurring when running MRA Check. In this example, the P2000 was not responding in the allocated time. If this happens, the routine needs to be executed again.

MRA Check not returning version information when running TS240P004-02 P2000 firmware version

This issue, shown in the following screen shot, is specific to running firmware version TS240P004-02 P2000 dated 11/2/2012 with CP filename cp018818.exe. After downgrading the firmware to the approved MRA version, the MRA check returns the approved version.

Troubleshooting 51

Manual P2000 firmware downgrade workaround To manually downgrade the P2000 firmware from TS240P004-02:

1. Download the following TS230P008 (cp017775.exe) firmware version to the Landing Zone server from this HP website (http://h20000.www2.hp.com/bizsupport/TechSupport/SoftwareDescription.jsp?lang=en&cc=US&swItem=MTX-21901f95515f48b794947a63f3&mode=5&prodTypeId=12169&prodSeriesId=4118559).

2. Click Download, and then enter the IP address.

3. Follow the remaining instructions on line.

P2000 single device update The P2000 single device update /EDW_update/ ApplyP2000cp might fail to update on P2000s. If this occurs, use one of the following options to complete the update:

• Run EDW Update using the -ApplyP2000cp option.

• Manually run the required cp file on the failed P2000s.

Automated reboot locks up with forced update When running an update with the –force option (downgrades/rewrites only), the appliance might not reboot properly using the automated script. The reboot process can hang because some nodes do not respond to any network commands or they do not timeout. In this case, the unreachable nodes must be manually rebooted to get the appliance operational again.

HP SUM repository errors If you encounter errors that are related to the HP SUM repository, be sure that all files and folders in the EDW Support Pack are not read-only. If errors persist, delete the %TEMP%\hp_sum folder.

HP SUM BroadComNIC update After successfully updating the BroadComNIC driver using HP SUM (without force) in a remote or local server implementation, HP SUM returns 3, while return code 1 is expected.

HP SUM manual downgrade to resolve update issues EDW Update might report a failure during an HP SUM downgrade. To diagnose and downgrade the individual component manually:

1. Run hpsum_update.cmd to review the failed component on the UI mode.

2. Review the HP SUM update table for the name of the failed component and the name of the cp file.

3. Run EDW update using the -applyservercp -force option to downgrade that individual component.

http://h20000.www2.hp.com/bizsupport/TechSupport/SoftwareDescription.jsp?lang=en&cc=US&swItem=MTX-21901f95515f48b794947a63f3&mode=5&prodTypeId=12169&prodSeriesId=4118559�



Troubleshooting 52

Manually updating the system BIOS If the EDW Update fails to update the system BIOS, use one of the following solutions:

• Run the EDW Update script in the default mode for all nodes.

• Run EDW Update with the -applyservercp option to update the BIOS.

Update process interrupted or stuck If the update process is interrupted or if it becomes stuck, use the EDW_reboot.ps1 script to reboot the appliance. If a node becomes unreachable, reboot the node in question. This can be done locally or remotely using HP iLO. If you are using HP iLO, HP recommends using the Cold Boot power option if the server is unresponsive.

Fibre Channel Switch web interface stuck at 19% while initializing

To resolve this issue, clear the Java cache. To clear the Java cache, open a command prompt and go to c:\Program Files (x86)\Java\jre6\bin and run "javaws –viewer.

In the interface that opens, delete the WebTools related to the FC switch (applications that contain "SWF" in the name). Delete the application by selecting it and then clicking the X icon.

Downgrading the ProCurve Ethernet switch When replacing a ProCurve Ethernet switch, downgrade the firmware to the approved MRA version for the G7 topologies. The approved version of firmware for the G7 appliance is N.11.15; the current version is N.11.52.

To downgrade the switch to the approved G7 version:


Troubleshooting 53


Be sure to include the two spaces and the period as shown at the end of the command line.

3. Run the following script: powershell .\EDW_Update.ps1 –UpdateSingleDevice ETH_Switch -force

The script automatically prompts for credentials. To use the common parameters, see "Parameters common to all scripts (on page 7)."

Downgrade System ROM on DL370 G6 (Landing Zone node) from version 5/5/2011 or newer

Enhancing the flash upgrade process requires modifications to both the System ROM and the flash update utility, the System ROM revision cannot be downgraded with the flash components available on the HP Support site after updating to this revision of the System ROM. A customer can downgrade the System ROM by creating a new flash component with the older System ROM revision as indicated in Advisory C02838375 available on the HP website (http://h20000.www2.hp.com/bizsupport/TechSupport/Document.jsp?locale=en_US&objectID=c02838375).

Node not accessible over the private network On rare occasions, not all network driver files are properly updated, thus the affected nodes cannot load the network drivers for the onboard network card. If this occurs, re-apply the network drivers to fix the issue. To expedite this, use the –ApplyServerCP parameter for the EDW_update.ps1 script. For example, to re-apply the NC382i driver, run:

Powershell .\edw_update.ps1 -DomainPassword <Domain administrator password> –ApplyServerCP cp014152.exe

Manual reboot required after ping all error Some hosts produce output showing that the script display errors are unavailable and refer you to the log file. The log file entry refers you to the HPC cluster manager application for additional status. However, the cluster manager uses multiple networks to derive host status and might show that all nodes are reachable.

http://h20000.www2.hp.com/bizsupport/TechSupport/Document.jsp?locale=en_US&objectID=c02838375�

http://h20000.www2.hp.com/bizsupport/TechSupport/Document.jsp?locale=en_US&objectID=c02838375�

Troubleshooting 54

The output console screen indicates which nodes are down. Manually reboot these nodes using an iLO cold boot to resolve this issue. For more information about rebooting the server from iLO, see "iLO reboot usage (on page 83)."

Updating the firmware 55

Updating the firmware

HP Smart Update Manager HP SUM is the primary deployment tool used to update firmware and drivers on most of the EDW components. HP SUM is designed for maximum flexibility and is shipped within the HP ProLiant Support Pack, HP BladeSystem Firmware Deployment Tool, and HP EDW Support Pack (downloadable from the HP Software Updates website (http://www.hp.com/go/hpsoftwareupdatesupport)). For details on downloading the most current Support Pack, see the HP Enterprise Data Warehouse Appliance Support Pack Release Note for your version.

HP SUM provides a GUI and a scriptable command line interface for the deployment of firmware for single or one-to-many servers and network-based targets such as iLOs, OAs, and Virtual Connect Ethernet and Fibre Channel modules. HP SUM has an integrated hardware and software discovery engine that discovers the installed hardware, the current versions of firmware in use on a target, and the software versions on target servers. This prevents extraneous network traffic by only sending the components that are needed to a target host. HP SUM also has logic to install updates in the correct order, ensure that all dependencies are met before deployment of a firmware update, and prevent version-based dependencies from derailing an installation, which minimizes any downtime required for the firmware update process.

HP SUM does not require an agent for remote installations, because it copies a small, secure SOAP server to the target server for the duration of the installation. After the installation is complete, the SOAP server and all remote files associated with the installation, except installation log files, are removed. HP SUM copies the log files from the remote targets back to the system where HP SUM is executed.

The key features of HP SUM include:

• Dependency checking, which ensures appropriate install order and dependency checking between components.

• Intelligent deployment deploys only required updates.

• Simultaneous firmware and software deployment.

• Improved deployment performance.

• Local or remote (one-to-many) online deployment.

• Local offline deployments with the HP Firmware Deployment Tool and Firmware Maintenance CD.

• Remote offline deployment when used with the SmartStart Scripting Toolkit or iLO Virtual Media.

• GUI or CLI/scriptable with extensive logging.

• Remote command-line deployment.

Firmware and driver updates using HP Smart Update Manager The EDW appliance firmware and drivers that are installed using HP SUM are upgraded through the HPSUM_update.cmd script.



IMPORTANT: This process must be performed while using the iLO connection to MAD01. Regular network connections will be broken during the update.

To update the firmware and driver using HP SUM on EDW:

1. Download the appropriate MRA EDW Support Pack from the HP Software Updates website (http://www.hp.com/go/hpsoftwareupdatesupport).



4. From the command line, execute c:\EDW Support Pack v1.44\EDW Update\HPSUM\HPSUM_update.cmd verbose. This starts the HP SUM graphical interface with the appropriate targets and bundle.

5. Click Start Inventory.



The list of remote nodes is preselected and the script proceeds to authenticate using the current credentials against all of the remote nodes. This might take a few minutes depending on the number of nodes in the appliance, as HP SUM has copied a temporary local version to each node.


The progress of the discovery process on all remote nodes appears. This process identifies firmware and driver versions on the system.

6. A list of all the remote nodes that were identified appears, as well as the updates that are preselected

to run on all of the nodes.

Clear the checkbox for the nodes you do not want to update. Select a node from the list, and then click View Host to view additional information about existing firmware/driver levels and the components that are preselected to be installed on the host.


Click Install to start installing the updates.


The update progress across remote nodes appears.


7. The upgrade status across all nodes appears. Select individual nodes, and then click View Host to see additional information about each update step.

8. Click Exit to finish HP SUM update for remote nodes.

HP SUM restarts automatically and repeats the upgrade on the local node.

9. If you encounter errors deploying on some nodes, re-run HPSUM update.cmd and the upgrade again on only the nodes and components that were not upgraded.

IMPORTANT: Do not click the HP SUM Reboot Now button. Instead, use the EDW_reboot.ps1 script that is described in this document. HP recommends rebooting the appliance with this script after making firmware/driver changes to make these changes active.

Fibre Channel HBA firmware upgrade The appliance uses the HP 82E DP FC HBA in the Control, Backup, and Compute nodes. Update these to FW v1.00A12 using the following instructions:




4. From the command prompt, execute c:\EDW Support Pack v1.44\EDW Update\FC_HBA.

5. Copy the EDW Support Pack to the Management node <appliance name>-MAD01.



6. Install HBAnyware on all Control, Backup, and Compute nodes (cp011160.exe).

7. Select All Programs>Emulex>HBAnywhere to start the HBAnywhere software from one of the Control nodes.

8. Select Batch>Download Firmware. The HBAnywhere Batch Firmware Download window appears.

9. Browse to the firmware file c:\EDW Support Pack v1.44\EDW

Update\FC_HBA\ud100a12.all.

10. Verify that all controllers and ports are selected.


11. Click Start Download.


The download progress appears.

12. Repeat these steps on the Backup node, Compute nodes, and the Control nodes.

InfiniBand 4xDDR DP HCA firmware upgrade Use the following steps to upgrade the InfiniBand HCA firmware on the EDW appliance:




4. Execute the following steps on all of the nodes you need to upgrade.



a. Install WinMFT firmware tools from c:\EDW Support Pack v1.44\EDW Update\IB_HCA\WinMFT_x64_2_6_0.msi.

b. Open a command prompt to c:\EDW Support Pack v1.44\EDW Update\IB_HCA\, and then run mst start to start the firmware upgrade service.

c. Run flint -no -d mt25218_pciconf0 -i fw-25218-5_3_000-483513-B21_A1.bin burn.

d. If you need to force a rewrite or downgrade, run flint -yes -d mt25218_pciconf0 -i fw-25218-5_3_000-483513-B21_A1.bin burn.

The following example shows the command prompt output.

InfiniBand FDR switch firmware upgrade To manually install the FDR switch firmware:

1. Download the current approved firmware version from the HP website (http://h20000.www2.hp.com/bizsupport/TechSupport/SoftwareDescription.jsp?lang=en&cc=us&prodTypeId=12883&prodSeriesId=5229311&prodNameId=5194984&swEnvOID=4103&swLang=8&mode=2&taskId=135&swItem=MTX-93f9ad4836824db99c8d873d67).

2. Launch a supported web browser, and then enter the IP address in the URL field.

3. Log on to the FDR switch using the user name: admin. The password is your current device password.

4. Extract the TGZ file into a local folder on the Landing Zone.

5. Select System, and then select MLNX-OS Upgrade.

6. Click Install from the local file.

7. Browse to the image-PPC_M460EX-SX_3.2.0100.img firmware image file.

8. Click Install image.

9. After image installation completes, click Reboot in the left panel of the System tab.

10. After the system reboots, log in to the switch.

11. Select System, and then select MLNX-OS Upgrade (used for both upgrades and downgrades).

http://h20000.www2.hp.com/bizsupport/TechSupport/SoftwareDescription.jsp?lang=en&cc=us&prodTypeId=12883&prodSeriesId=5229311&prodNameId=5194984&swEnvOID=4103&swLang=8&mode=2&taskId=135&swItem=MTX-93f9ad4836824db99c8d873d67�




12. Verify that the new image version was applied to the Active Image.

HP P2000 G3 FC Controller firmware upgrade The appliance uses the HP P2000 G3 FC arrays for the control, backup, and compute node storage. The update process takes about 30 minutes or up to 90 minutes depending on the firmware upgrade requirements.

IMPORTANT: After the HP P2000 G3 MSA Array System is upgraded to TS230 firmware or later, the controllers no longer support a firmware downgrade to an earlier firmware version. For more information, see HP Customer Advisory c02971504 on the HP website (http://h20000.www2.hp.com/bizsupport/TechSupport/Document.jsp?objectID=c02971504).

To update the controllers in the arrays:




4. Run the executable file in the c:\EDW Support Pack v1.44\EDW Update\P2000 folder.

http://h20000.www2.hp.com/bizsupport/TechSupport/Document.jsp?objectID=c02971504�

http://h20000.www2.hp.com/bizsupport/TechSupport/Document.jsp?objectID=c02971504�



5. Click Install.

6. Enter the IP Address, User Name, and Password for the P2000 G3 FC array. The storage array IP

addresses are 172.16.2.x.

o For Compute node storage arrays, x = 1, 2,…

o For Control node storage arrays, x = 240, 241,…

o For Backup node storage arrays, x = 220, 221, ….

For example, for Compute node CMP01, enter 172.16.2.1 for the IP Address, manage for the User Name, and HP*Msft1 for the password. HP*Msft1 is the default password. Your password might be different.


7. Click Continue.

8. To start discovery, click Continue.


The storage array discovery process begins.

9. The current version appears. If the firmware version is not up to date, click Install to continue.

Controller (B) firmware is flashed.

Controller (A) firmware is flashed.


10. Upon successful completion, click Close.

11. Repeat this process for all P2000 G3 FC storage arrays in the EDW appliance. For example, the HP

DL360G7 1 Data Rack High Performance EDW topology has the following storage arrays:

o 10 Compute node storage arrays (IP addresses 172.16.2.[1-10])

o 1 Control node storage array (IP address 172.16.2.240)

o 2 Backup storage arrays (IP addresses 172.16.2.[220-221])

QLogic IB 9040 and 9024 Switch firmware upgrade

IMPORTANT: The QLogic IB switch requires Java in order to properly display the web interface. The Landing Zone node (LZ01) is the node designated for third-party software installations. Install the latest JRE on the Landing Zone and use this node for the steps in this section.

The firmware version on all three switches should be 4.2.5.1.1. If the firmware needs to be updated, log on to each switch through the assigned IP address.

QLogic SilverStorm 9040 Switch

1. Launch a supported browser, and then enter 172.16.4.101 in the URL field.

2. Log on to the QLogic 9040 switch with the login information supplied by the customer. The factory default at the time of shipping is admin/HP*Msft1, and the manufacturer default user/password is admin/adminpass.


3. Click on the outer gray chassis to view the Chassis Details menu.

4. Click Maintenance, and then click Firmware Update.

5. Select the Spine 1 checkbox, and then select the Boot? checkbox.


6. Browse to the Firmware Update Package file: c:\EDW Support Pack v1.44\EDW Update\IB_Switch\InfiIO9000.t3.pkg.

7. Click Update.

8. After the Completion State is 100% complete, click Close.

QLogic SilverStorm 9024 Switches

1. Launch a supported browser, and then enter 172.16.4.[102,103...] in the URL field. The number of 9024 switches depends on the EDW topology. Update the firmware the 9024 switches.

2. Log on to the QLogic 9024 switch with the login information supplied by the customer. The factory default at time of shipping is admin/HP*Msft1, and the manufacturer default user/password is admin/adminpass.


3. Click Maintenance, and then click Update Firmware.

4. Browse to the Firmware Update Package file: c:\EDW Support Pack v1.44\EDW

Update\IB_Switch\InfiIO9000.t3.pkg.


5. Click Update Firmware.


The update progress bar appears.


6. After the update completes, click Close.

Voltaire IB 4036 Switch firmware upgrade The firmware version on all Voltaire IB switches should be the same. If the firmware needs to be updated, log on to each switch through the assigned IP address. The Voltaire IB switch does not provide a web interface. Management operations are performed through a CLI.

To upgrade the firmware:

1. Open a command prompt.

2. Change to the c:\EDW Support Pack v1.44\EDW Update\IB_Switch\IB_QDR_Switch directory.

3. Run the following command: ftpdmin.exe –g –ha 172.16.0.250 .

o The command must include the two spaces and the dot after the last number.

o Do not close the window until the firmware upgrade is complete.

4. Open a telnet connection to 172.16.4.101 using the login information provided by the customer. The

factory default user name/password combinations are as follows:


o At the time of shipping: admin/HP*Msft1

o Manufacturer default admin/123456

5. Run the following commands: a. config b. remote

c. server 172.16.0.250

d. username user

e. password f. pass

g. protocol set FTP

h. exit i. exit

j. update software chassis


The switch downloads the firmware image and closes the telnet connect upon completion.

6. Close the window using the ftpdmin.exe process.

Fibre Channel SAN Switch firmware upgrade

IMPORTANT: The Fibre Channel SAN switch requires Java in order to properly display the web interface. The Landing Zone node (LZ01) is the node designated for third-party software installations. Install the latest JRE on the Landing Zone and use this node for the steps in this section.

During a firmware download, the switch reboots and the browser temporarily loses connection with the switch. When the connection is restored, the version of the software running in the browser is different from the new software version that has been installed and activated on the switch. Close the Web Tools windows, and then log in again to avoid a firmware version mismatch. You might get pop-up messages that imply the loss of connection is temporary and will soon be resolved. You still need to close all windows and log in again.

IMPORTANT: Fibre Channel SAN Switch firmware can only be upgraded/downgraded in single version steps. For example, in order to upgrade from version 6.2.x to version 6.4.x, you must first upgrade to version 6.3.x, and then upgrade to version 6.4.x.

To update the firmware on each switch:

1. Open a command prompt to c:\EDW Support Pack v1.44\EDW Update\FC_Switch.


2. Run ftpdmin.exe –g –ha 172.16.0.230 <Firmware version number>. Do not close the window until the firmware upgrade is complete.

3. Launch a supported browser, and then enter 172.16.4.[51,52,…] in the URL field.

4. Log on to the switch with the login information supplied by the customer. The factory default at time of shipping is admin/HP*Msft1, and the manufacturer default user/password is admin/admin.

5. Open the Switch Administration window.

6. Click the Firmware Download tab.

7. Choose the option for downloading the firmware.

8. Select Network as the download source.

9. Enter the host name or IP address, user name, password, and fully qualified path to the file release.plist.

The path name should follow the structure: //<directory>/<fos_version_directory>/release.plist

where <directory> is the path up to the entry point of <fos_version_directory> and <fos_version_directory> is the location of the unzipped version of Fabric OS.

For example: //v6.2.2d/release.plist

Under v6.2.2d there is no release.plist file, but several SWBDXX folders for each switch type supported by this firmware upgrade.

10. Select the FTP protocol type in the Protocol Type field.

11. Click Download.


The firmware download begins. You can monitor the progress by looking at the Firmware Download progress bar. About halfway through the download process, after the firmware key is downloaded to the switch, connection to the switch is lost and Web Tools invalidates the current session. Web Tools invalidates all windows if upfront login is enabled.

Fibre Channel SAN Switch firmware downgrade The Fibre Channel HBA downgrade from 1.00a12 to the required version 2.00a4 using applyservercp can fail on some nodes. If this occurs, use one of the following updates:

• Run HPSUM update – the preferred method

• Run the complete EDW_Update

Use this specific downgrade, use-case example only when receiving a new hardware replacement, which requires downgrading from the latest firmware to the required MRA version, 1.00a12 for EDW Support Pack v1.41.

ProCurve 2810-24/48 G Switch firmware upgrade

IMPORTANT: The ProCurve 2810-24/48 switch requires Java in order to properly display the web interface. The Landing Zone node (LZ01) is the node designated for third-party software installations. Install the latest JRE on the Landing Zone and use this node for the steps in this section.


To update the firmware on a single switch:

1. Launch a supported browser, and then enter 172.16.4.[1,2…] in the URL field. The number of 2810-24/48 G switches depends on the EDW appliance topology. Update the firmware on the 2810 24/48 G switches to version N.11.15.

2. Log on to the ProCurve 2810-24/48 G switch with the login information supplied by the customer:

• The factory default user/password at the time of shipping is admin/HP*Msft1, and the manufacturer default user/password is blank/blank.

• Login information is cached in the browser on the computer that you regularly use (jump station). Depending on your browser settings, only one login is required.

1. Select the Configuration tab.

2. Click Upload/Download.

3. Select Upload a Software Image for Destination Primary.

4. Browse to the firmware image c:\EDW Support Pack v1.44\EDW Update\Eth_Switch\N_11_15.swi.


5. Click Upload.

Wait for the upload to complete. You might need to log on again during the upload, because the firmware has been reset.


HP Software Updates EDW Support Pack file Download the EDW Support Pack from the HP Software Updates website (http://www.hp.com/go/hpsoftwareupdatesupport). For details on downloading the most current Support Pack, see the HP Enterprise Data Warehouse Appliance Support Pack Release Note for your version.

The ZIP file contains the following:

• PDW Setup/Installation drivers—HP specific drivers installed during the factory PDW setup. These files are required on the management node in this directory structure in addition to the PDW installation files during the setup procedure for an initial PDW installation or a reconfiguration of the appliance at the customer site.

ZIP file location---\External\

• EDW Firmware and driver upgrade—Installation of the EDW appliance firmware and drivers as outlined in this document.

ZIP file location---\EDW update\

• Documentation—A copy of this document and additional material.

ZIP file location---\Documents

iLO reboot usage To log in to iLO and reboot a server:

1. Enter the iLO IP address in a browser. Enter Administrator for the default user ID and the appropriate device password.



2. Select Information > Overview > Monetary Press to reboot the server.

For more information, see "Troubleshooting (on page 46)."

Support and other resources 85

Support and other resources

Contacting HP Enterprise Data Warehouse support To contact HP Support for the HP AppSystem for SQL Server Parallel Data Warehouse, use the phone number provided with your HP service contract documentation. Your specific support phone number is tied to your service contract and the specific level of support purchased.

Be sure to have the following information available before you call HP Support:

• EDW Solution Identifier composed of EDW Control Rack SKU number + the Product Serial number

• Applicable error messages

• Operating system type and revision level

• EDW MRA version

Before you contact HP Be sure to have the following information available before you call HP:

• Active Health System log (HP ProLiant Gen8 or later products)

Download and have available an Active Health System log for 3 days before the failure was detected. For more information, see the HP iLO 4 User Guide or HP Intelligent Provisioning User Guide on the HP website (http://www.hp.com/go/ilo/docs).

• Onboard Administrator SHOW ALL report (for HP BladeSystem products only)

For more information on obtaining the Onboard Administrator SHOW ALL report, see the HP website (http://www.hp.com/go/OAlog).

• Technical support registration number (if applicable)

• Product serial number

• Product model name and number

• Product identification number

• Applicable error messages

• Add-on boards or hardware

• Third-party hardware or software

• Operating system type and revision level

HP contact information For United States and worldwide contact information, see the Contact HP website (http://www.hp.com/go/assistance).

In the United States:

http://www.hp.com/go/ilo/docs�

http://www.hp.com/go/OAlog�

http://www.hp.com/go/assistance�

Support and other resources 86

• To contact HP by phone, call 1-800-334-5144. For continuous quality improvement, calls may be recorded or monitored.

• If you have purchased a Care Pack (service upgrade), see the Support & Drivers website (http://www8.hp.com/us/en/support-drivers.html). If the problem cannot be resolved at the website, call 1-800-633-3600. For more information about Care Packs, see the HP website (http://pro-aq-sama.houston.hp.com/services/cache/10950-0-0-225-121.html).

Other resources For more detailed information about hardware and software features used on the HP Enterprise Data Warehouse Appliance, see the documents listed below.

To access the documents:

1. Go to the HP Business Support Center:

http://h20000.www2.hp.com/bizsupport/TechSupport/Home.jsp (http://h20000.www2.hp.com/bizsupport/TechSupport/Home.jsp)

2. In the Search box at the top of the page, type "Appliance Support Pack" with the quotations.

3. From the list that appears, click HP AppSystem for Microsoft SQL Server 2012 Parallel Data Warehouse v2 - Manuals - HP Business - (59829).

Documentation available from this location includes the latest available versions of the following:

o HP Enterprise Data Warehouse Appliance Getting Started Guides

o HP Enterprise Data Warehouse Appliance Release Notes

o HP Enterprise Data Warehouse Appliance User Guides

Other available documentation includes the following:

• Best Practices for HP Enterprise Data Warehouse Appliance (http://h20195.www2.hp.com/V2/GetPDF.aspx/4AA3-8477ENW.pdf)

• HP Enterprise Data Warehouse Appliance architecture overview and performance guide (http://h20195.www2.hp.com/v2/GetPDF.aspx/4AA3-5625ENW.pdf)

• High speed data export from an HP Enterprise Data Warehouse Appliance to an SMP Microsoft SQL Server (http://h20195.www2.hp.com/V2/GetPDF.aspx/4AA3-8382ENW.pdf)

• HP and Microsoft SQL Server Business Intelligence solutions (http://www.hp.com/solutions/microsoft/sqlbi)

• HP and Microsoft SQL Server Business Intelligence Configurations and SQL Server Fast Track Data Warehouse reference architectures (http://www.hp.com/solutions/microsoft/sqlbiconfigs)

• HP and Microsoft SQL Server solutions (http://www.hp.com/solutions/microsoft/sql)

• HP and Microsoft (http://www.hp.com/go/microsoft)

• SQL Server Fast Track Data Warehouse (http://msdn.microsoft.com/en-us/library/dd459178.aspx)

• SQL Server solutions on ActiveAnswers (http://www.hp.com/solutions/activeanswers/microsoft/sql)

http://www8.hp.com/us/en/support-drivers.html�

http://pro-aq-sama.houston.hp.com/services/cache/10950-0-0-225-121.html�

http://h20000.www2.hp.com/bizsupport/TechSupport/Home.jsp�

http://h20195.www2.hp.com/V2/GetPDF.aspx/4AA3-8477ENW.pdf�

http://h20195.www2.hp.com/v2/GetPDF.aspx/4AA3-5625ENW.pdf�

http://h20195.www2.hp.com/V2/GetPDF.aspx/4AA3-8382ENW.pdf�

http://www.hp.com/solutions/microsoft/sqlbi�

http://www.hp.com/solutions/microsoft/sqlbiconfigs�

http://www.hp.com/solutions/microsoft/sql�

http://www.hp.com/go/microsoft�

http://msdn.microsoft.com/en-us/library/dd459178.aspx�

http://www.hp.com/solutions/activeanswers/microsoft/sql�

Acronyms and abbreviations 87

Acronyms and abbreviations

CP CarePack

CSV comma-separated value

DDR double data rate

EDW enterprise data warehouse

ETH

Ethernet

FC

Fibre Channel

HBA

host bus adapter

HCA

Host Channel Adapter

HP SUM

HP Smart Update Manager

IB InfiniBand

iLO Integrated Lights-Out

iSCSI Internet Small Computer System Interface

Acronyms and abbreviations 88

ISO

International Organization for Standardization

MPP

massively parallel processing

MRA

master reference architecture

OA

Onboard Administrator

PDW parallel data warehouse

SA Smart Array

SAS serial attached SCSI

SATA serial ATA

SMP

Server Migration Pack

SOAP

Simple Object Access Protocol

Documentation feedback 89

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 (mailto:[email protected]). Include the document title and part number, version number, or the URL when submitting your feedback.

mailto:[email protected]�

Index 90

A

appliance diagnostics 24, 33

B

before you contact HP 85 BIOS upgrade 52

C

control rack 38, 42

D

data rack 39 device naming 35, 36 device, updating P2000 single 51 domain name 8 downgrades 51, 52, 53 driver version 24 drivers 22

E

enterprise data warehouse 6, 11

F

firmware 19, 20, 24, 80 firmware by node 19, 20 firmware deployment options 19 firmware requirements 19 firmware switches 20 firmware version 50 firmware, downgrading 51 firmware, troubleshooting 50, 51 firmware, updating 55, 61, 64, 65, 66, 70, 76, 78 firmware, validating 24

H

HP contact information 85 HP EDW 24, 26, 33 HP EDW v1.3 20 HP EDW v1.4 20

HP ProLiant Gen8 20 HP SUM, troubleshooting 51

I implementation options 12 InfiniBand 65 IP address 37, 38, 42, 43, 45 IP address naming schema 35

M

manual update, system BIOS 52 MRA 24, 50

N

node status, conflicts 47, 53

P

P2000 48, 51 parameters 7, 8, 9 password, changing 48 password, entering 8 password, prompt 8 passwords 7, 8, 10, 11

R

reports 26

S

single device update failure 51 software updates, tracking deployment 83 support and other resources 85, 86

T

troubleshooting 46, 47, 48, 50, 51, 53

U

update issues, HP SUM 51 update system BIOS manually 52 update, appliance 13, 17, 55 update, node 13

Index

Index 91

updating a single device 12 updating the server 12