Add License Key - Smart Array P410i In Embedded Slot

Smart array p410i in embedded slot had valid data stored in its battery/capacitor backed write cache the last time the array controller has automatically written, or has attempted to writ this data to the drives. This message will continue to be displayed until the next reset power-cycle of the array controller. For this procedure, first we are going check the status of the Smart Array. Connect trough ssh to storage server with faulty HDD and using HP utility hpacucli, execute the following: # hpacucli ctrl all show config Smart Array P410i in Slot 0 (Embedded) (sn: 500xxxxxxxxxxxxx). Boards for I/O flexibility. The embedded modular smart array controllers deliver superior performance with the flexibility to seamlessly add cache and battery-backed write cache (BBWC) or flash-backed write cache (FBWC). As always, you can rely on ProLiant for the best in industry-standard management, including HP Insight Control.

From Bicom Systems Wiki

  • 2Hardware Requirements
  • 3Deployment Guide
  • 4Installation wizard steps
  • 5Setup wizard steps

Introduction

The following guide describes minimal and recommended hardware requirements as well as procedures for a successful deployment and maintenance of HP ProLiant DL360 G7 in the SERVERware 3 environment.

Hardware Requirements

Server requirements

HP ProLiant DL360 G7 with the following:

HARDWARE MINIMUM SYSTEM REQUIREMENTS RECOMMENDED SYSTEM REQUIREMENTS
CPU 2.4 GHz Quad-Core Intel Xeon Processor with 12MB Cache - E5620 2.93 GHz Hex-Core Intel Xeon Processor with 12MB Cache - X5670
RAM 16GB Memory (4x4GB) PC3-10600R 32GB Memory (4x8GB) PC3-10600R
Ethernet 2 network interfaces ( for SERVERware Mirror edition ), 3 network interfaces ( for SERVERware Cluster edition ) 4 network interfaces ( for SERVERware Mirror edition ), 6 network interfaces ( for SERVERware Cluster edition )
Controller Smart Array P410i 512MB BBWC 0-60 RAID Smart Array P410i 512MB BBWC 0-60 RAID
Disk 2 x 100GB 15K RPM SAS 2.5' HP Hard Disk Drive ( for system ), 2 x 300GB 10K RPM SAS 2.5' HP Hard Disk Drive ( for storage ) 2 x 100GB 15K RPM SAS 2.5' HP Hard Disk Drive ( for system ), 4 x 600GB 10K RPM SAS 2.5' HP Hard Disk Drive ( for storage )
PSU Redundant HP 460 Watt PSU Redundant HP 750 Watt PSU


IMPORTANT NOTE: Software RAID (including motherboard) implementations are not supported and could cause potential problems that Bicom Systems would not be able to support.

KVMoIP (Keyboard, Video, Mouse over IP) remote access to each server

  • Remote power management support (remote reset/power off/on)
  • Remote access to BIOS
  • Remote SSH console access
  • A public IP assigned to KVMoIP
  • If KVMoIP is behind firewall/NAT, the following ports must be opened: TCP (80, 443, 5100, 5900-5999)

SERVERware installation media is required in one of the following forms

  • DVD image burned on to a DVD and inserted into DVD drive
  • USB image burned onto 2GB USB drive and inserted into operational USB port

Deployment Guide

Network setup


How-to instructions regarding network setup are available on the following page:

RAID Controller setup

- Press F8 during POST to enter RAID setup configuration utility
- Create logical drive (RAID 1) for 2 100GB drives (for system)
- Create logical drive (RAID 0) for each still available drive (for storage)
- Exit RAID setup configuration utility

Creation of USB installation media


USB images and instructions are available on the following how-to page:



Boot target machine from the USB installation media. The following welcome screen appears.

If the live system was able to pickup IP address from DHCP server, it will show so on this screen. You can then access the system remotely via ssh on port 2020 with username 'root' and password 'bicomsystems' and continue installation. There are several options offered on the welcome screen:

  • Exit - Choose this option to exit installation wizard. This option will open live system command line shell.
  • Verify Media - This option will go trough the installation media files, match them against previous stored checksum and check for corruption.
  • Next - Proceed to the next step.
  • Network - Configure IP address for the remote access to the installation wizard.

Step 1:

Select the type of installation you want to install, Storage/Controller or Host (Processing or Backup).

Storage/Controller is the network storage for VPSs on the SERVERware network. In order to use mirrored setup, you will have to install two physical machines as Storage/Controller. Processing Host is computation resource that will attach and execute VPSs from storage via SAN (Storage Area Network).

Step 2:

Installation wizard will proceed to check for available disks.

Step 3:

Select physical disk for system installation. Volume for storage will be automatically created from disks that are not selected in this step.

Step 4:

Confirmation dialog appears.

Step 5:

Installation wizard will now proceed with installation of SERVERware operating system.

Step 6:

After OS is installed, configure network dialog appears.

Select Create virtual bonding network interface to proceed to network interface creation.

From the list of available network interfaces, select two interfaces for bonding interface creation.

From the list of available modes, (select agregattion to suit your network configuration eg. 802.3ad), for bonding interface creation.

Enter a name for a new bonding interface.

Click Next to continue and then chose one of the options to configure new bonding interface.

After finishing network configuration, click next to finish installation. Wizard will initiate reboot.

Step 7:


Redo installation steps for the second (mirrored) machine.


Open your browser and enter bondLAN IP you configured upon installation. After confirming self signed certificate, SERVERware setup wizard login screen appears. Enter administration password which is by default 'serverware'.

Step 1:

After successful login, SERVERware EULA appears.

Acceptance of the EULA leads to the next step.

Step 2:

Enter your license number, administrator's email, set new administrator's SERVERware GUI password. This password will also apply to shell root account. Select your time zone and click next to continue.

Step 3:

Depending on the license you acquired, this step will offer you to configure LAN, SAN and mirror RAN network. LAN is a local network for SERVERware management and service provision. SAN is a network dedicated to connecting SERVERware storage with processing hosts. RAN is a network dedicated to real time mirroring of two servers.

Before proceeding with the network configuration, use command line interface utility netsetup to create virtual bonding network interfaces bondRAN and bondSAN. Also, before proceeding to the next step, use command line interface utility netsetup to create and setup virtual bonding network interfaces bondRAN and bondSAN on the second (mirrored) machine.

Setup wizard will suggest default configuration for the network interfaces. The machines must be on same LAN network and the same SAN and RAN network. Modify network configuration if needed and click Next to proceed to the next step.

Step 4:

Choose the name for the cluster if you don't like the one generated by the SERVERware (it must be valid per hostname constrains).

Select from the list or enter the LAN IP address of the second (mirrored) machine. Purpose of mirrored setup is to provide storage redundancy, so it will need a few more configuration parameters. LAN Virtual IP is a floating IP address for accessing mirrored storage server. SAN Virtual IP is floating IP address used for access to the storage. Administration UI IP address will be used for CONTROLLER VPS (GUI).

CONTROLLER VPS is setup automatically on the storage server, and its purpose is to provide administrative managing web console as well as to control and monitor SERVERware hosts and VPSs.

Once you click Finish button, wizard will initialise and setup the network storage. When complete, setup will present the summary info.

Wait a few seconds for CONTROLLER to start and click on the Controller Web Console link to start using SERVERware and creating VPSs.

Storage Expansion and Replacement


Replacing one damaged HDD from RAID 1 on secondary server HP ProLiant DL360 G7 while system is running


When one of the HDD's from mirror is damaged, next procedure should be followed:

Setup :We have 2 mirrored storage servers, each server have 2 HDD‘s in RAID 1 (Mirror) for storage.

For this procedure, first we are going check the status of the Smart Array.

Connect trough ssh to storage server with faulty HDD and using HP utility hpacucli, execute the following:


As we can see from output one of the HDD’s have 'Failed' status.

Our next step is to remove the faulty HDD from the bay-6 and insert new HDD in bay-6.

After replacement we can use the same hpacucli command to check the status of the newly installed HDD.


Now we can see that HP Raid controller is rebuilding data on the replaced HDD,

and the status of logicaldrive 3 (931.5 GB, RAID 1, Recovering, 0% complete).

This can take a while to complete depending on a storage size.

After completion, HDD should have status 'OK'.

This is the end of our replacement procedure.

Replacing one damaged HDD from RAID 0 on secondary server HP ProLiant DL360 G7 while system is running


When one of the HDD's from mirror is damaged, next procedure should be followed:

Setup :We have 2 mirrored storage servers.Each server have 2 HDD‘s, each of them setup as RAID 0.

For this procedure, first we are going check the status of the Smart Array.

Connect trough ssh to storage server with faulty HDD and using HP utility hpacucli, execute the following:


This is output of the hpacucli command when everything is ok.

If one of the drives fail, the output would be:


If HDD fails, zpool will be in the state: DEGRADED on the primary server.

Next, we should physically replace the damaged HDD in the server bay 5 and run hpacucli again.


From output we can see that the status of the physicaldrive is OK but status of logicaldrive 3 is Failed.

We need to delete failed logical drive from smart array (in this case logicaldrive 3) and recreate it again with new drive.

We can do this using hpacucli command.

Checking the status again.

New physicaldrive is now unassigned.Create logicaldrive 3 in RAID 0 using new drive in bay 5.To create logical drive use hpacucli command:

Command explaination:

We have created logicaldrive 3 in RAID 0 configuration, using disk 2I:1:5 in bay 5.
Checking the status again.

To find out more detailed info on logicaldrive 3 and which block device name system has assigned to the logicaldrive 3, use the following hpacucli command:

When we have block device name (Disk Name: /dev/sdd), we need to make a partition table for the newly installed disk.

To make a partition table use parted:

Create the partition with the name to match our faulty partition on the primary server. We have this name from above:

SW3-NETSTOR-SRV2-1 FAULTED 3 0 0 too many errors

Our command in this case will be:

We have now added a new partition and a label. Now we need to edit mirror configuration file: /etc/tgt/mirror/SW3-NETSTOR-SRV2.conf


IMPORTANT:Before we can edit configuration file, we need to logout iSCSI session on the primary server.

Connect trough ssh to the primary server and use iscsiadm command to logout:

Example:

Now we can proceed editing configuration file on the secondary server.


Source of the file looks like this:

We need to replace iscsi-id to match the ID of the changed HDD.

To see the new ID use this command:

Now edit configuration file.

Replace ID with the new one and save file.


Next, we need to update the target from the configuration file we have just created.

To update tgt-admin info from configuration file, we will use following command:

This ends our procedure on the secondary server.

Next, on the primary server, add newly created virtual disk to the zfs pool.


First we need to login to the iscsi session we have exported before:

Example:

After this we can see zpool status:


From the output we can see:

SW3-NETSTOR-SRV2-1 FAULTED status of secondary HDD


Now we need to change guid of old HDD to guid of new HDD, so that zpool can identify new HDD.

To change guid from old to new in zpool, first we need to find out new guid.

We can use zdb command to find out:

The important line for from zdb output:

The guid part need to be updated to zpool.

We can update guid with the command:

Add


Example:


Now check zpool status:

You need to wait for zpool to finish resilvering.

This ends our replacement procedure.


Expanding storage with 2 new HDD’s in RAID 1 on HP ProLiant DL360 G7 while system is running


Insert 2 new HDD’s in storage server empty bays.

Connect trough ssh to the server and using hpacucli create new logical drive and add new HDD’s to logical drive.

Use the following command to view configuration:

We can see from the output that new HDD’s appear under unassigned.

We need to create logical drive in RAID 1 from unassigned HDD’s.

To create logicaldrive use this command:

And again check the status:


Now we have new logical drive logicaldrive 4 (931.5 GB, RAID 1, OK).

After creating new logical drive we need to make a partition table on a new drive.

We need to find out which block device name system has assigned to the logicaldrive 4.

To find out type:


Use parted to make partition table for new a logical drive.

And create a new label.

IMPORTANT: label must be formated as before SW3-NETSTOR-SRV2-2
Name of the label “SRV2” comes from the server number and “-2” is the second virtual drive:

1. SW3-NETSTOR-SRV2 - this means virtual disk on SERVER 2
2. -2 - this is the number of the virtual disk (virtual disk 2)

Now add a label to a new drive.

We have to update configuration file for SERVERware to know what block device to use.

We can get this informations by listing devices by-id:

Now copy disk ID scsi-3600508b1001cad552daf39b1039ea46a and edit configuration file:

Our case:

File should look like this:


Add one more <target> to a configuration file, to include new <target>:

<target SW3-NETSTOR-SRV2-2>

and ID:

<direct-store /dev/disk/by-id/scsi-3600508b1001cad552daf39b1039ea46a>

After editing, the configuration file should look like this:

Save file and exit.

We need to edit one more configuration file to add a location of the secondary HDD:

Add a new storage name comma separated after existing storage name.

Edit file and apply the change to look like this:

Save file and exit.


Now repeat all these steps on another server.


After all these steps are done on both servers, we need to link storage from the secondary server to the zpool on the primary server.

Connect trough ssh to the secondary server and export target to iSCSI using tgt-admin tool:


This ends our procedure on the secondary server.

Connect trough ssh to the primary server and use iscsiadm discovery to find new logical disk we have exported on the secondary server.

First, find out network address of the secondary storage server:

In output we will get information we need for the discovery command,192.168.1.46:3259 (IP address and port).

Now using iscsiadm discovery, find new logical drive:

Now login to the exported iSCSI session.Use this command:

To see newly added logical drive use:

Now we need to expand our pool with new logical drives.You need to be careful with this command. Check names of logical drives to make sure you got the right name.

Add License Key - Smart Array P410i In Embedded Slots

Now in the zpool, we should see newly added logical volume:

This is the end of our storage expansion procedure.

Retrieved from 'http://wiki.bicomsystems.com/index.php?title=SERVERware_3_Deployment_Guide_for_HP_ProLiant_DL360_G7&oldid=38170'
Printable version

Add License Key - Smart Array P410i In Embedded Slot Software

* RECOMMENDED * Online ROM Flash Component for VMware ESXi - Smart Array P212, P410, P410i, P411, P711m, P712m, and P812

By downloading, you agree to the terms and conditions of the Hewlett Packard Enterprise Software License Agreement.
Note: Some software requires a valid warranty, current Hewlett Packard Enterprise support contract, or a license fee.

Type:Firmware - Storage Controller
Version:6.62(6 Apr 2015)
Operating System(s):
VMware vSphere 5.1
VMware vSphere 5.5
VMware vSphere 6.0
VMware ESXi 5.0
Multi-part download
File name:CP025733.scexe (7.2 MB)
File name:CP025733.md5 (49 Bytes)
This Smart Component provides firmware for the following storage controllers: Smart Array P212, P410, P410i, P411, P711m, P712m, and P812

Enhancements/New Features:

  • Performance enhancement when a drive starts to degrade due to excessive recovered media errors.

To ensure the integrity of your download, HP recommends verifying your results with the following MD5 Checksum values:

27660a8a865d40cf281955449521f862CP025733.md5
ecfb82c5eeb4d8dbb189b334befee7b3CP025733.scexe

Reboot Requirement:
Reboot is required after installation for updates to take effect and hardware stability to be maintained.

Installation:
To use HP Smart Update Manager from the HP Service Pack for ProLiant:
Offline (The SPP Offline mode boots a special Linux OS environment, thus the Linux Smart Components are used, not the VMware Smart Components):

  • Place the HP Service Pack for ProLiant on a USB key using the HP USB Key Creator Utility.
  • Place the desired Linux firmware component to be updated in the directory, /hp/swpackages on the USB key.
  • Boot from the newly created HP Service Pack for ProLiant USB key.
  • Follow HP Smart Update Manager steps to complete firmware update.
Remote Online:
  • Download the appropriate SPP.
  • Add the component to the SPP.
  • Mount the SPP on a remote server running Windows or Linux that has a network connection to the ESXi host to be updated.
  • Run HP SUM.
  • Add the ESXi host to be updated as a remote target/node.
  • Enter IP or DNS address of the ESXi host to be updated Enter the ESXi host credentials (root or administrator username and password).
  • For HP SUM 6.0 and newer, select both the Additional Package with the added component and the SPP Baseline on the node Inventory page.
  • Follow HP Smart Update Manager Steps and complete the firmware update.
Refer to the SPP documentation for detailed instructions at: http://www.hp.com/go/spp
To use HP Insight Control for vCenter :
  • Log in to the vSphere Client.
  • Select a server or cluster in the inventory tree.
  • Click the HP Insight Management tab.
  • Follow Insight Control for vCenter steps to update firmware using a Smart Component
To update firmware from VMware ESXi operating system on target server:
  • Enable Tech Support Mode on the ESXi host.
  • Login as root. (You must be root in order to apply the ROM update.)
  • Place the Smart Component in a temporary directory.
  • From the same directory, execute the Smart Component. For example: ./CPXXXXXX.scexe
  • Follow the directions given by the Smart Component.
  • Logout
  • Disable Tech Support Mode on the ESXi host.
  • Reboot your system, if required, for the firmware update to take effect.

End User License Agreements:
Hewlett-Packard End User License Agreement

Upgrade Requirement:
Recommended - HP recommends users update to this version at their earliest convenience.

Important:
Important Notes:

  • Reference Customer Advisory c03793656 - Windows Server 2012 - HP ProLiant Server May Blue Screen if Configured With an HP Smart Array Controller and the Windows Server 2012 HPCISSS2.SYS Driver Version 62.26.0.64

Notes:
Deliverable Name:

Online ROM Flash Component for VMware ESXi - Smart Array P212, P410, P410i, P411, P711m, P712m, and P812
Release Version and/or Date:
6.62
Last Recommended or Critical Version:
6.60
Previous Version of Firmware:
6.60
Firmware Dependency:
None
Enhancements/New Features:

  • Performance enhancement when a drive starts to degrade due to excessive recovered media errors.
Problems Fixed:
  • On systems configured with HP Smart Array P711m controllers connected to logical volumes on HP P2000 G3 SAS storage arrays, the Smart Array device driver ‘hpsa’ would cease to function during installation of VMware vSphere 5.5 Update 2.
  • After the Smart Array device driver 'hpsa' was upgraded to version 3.4.6-165 on Red Hat Enterprise Linux 6 Update 4 or Update 5 on a server configured with logical volumes on HP P2000 G3 Storage Systems or HP MSA 2040 SAS Storage Arrays, the system would cease to function and an HP Smart Array P712m controller lockup would be reported after reboot. (POST Error: 1719 - A controller failure event occurred prior to this power-up. (Previous lock up code = 0x13))

Known Issues:
None

Upgrade Requirement:
Recommended - HP recommends users update to this version at their earliest convenience.

Problems Fixed:

  • On systems configured with HP Smart Array P711m controllers connected to logical volumes on HP P2000 G3 SAS storage arrays, the Smart Array device driver ‘hpsa’ would cease to function during installation of VMware vSphere 5.5 Update 2.
  • After the Smart Array device driver 'hpsa' was upgraded to version 3.4.6-165 on Red Hat Enterprise Linux 6 Update 4 or Update 5 on a server configured with logical volumes on HP P2000 G3 Storage Systems or HP MSA 2040 SAS Storage Arrays, the system would cease to function and an HP Smart Array P712m controller lockup would be reported after reboot. (POST Error: 1719 - A controller failure event occurred prior to this power-up. (Previous lock up code = 0x13))
Important Notes:
  • Reference Customer Advisory c03793656 - Windows Server 2012 - HP ProLiant Server May Blue Screen if Configured With an HP Smart Array Controller and the Windows Server 2012 HPCISSS2.SYS Driver Version 62.26.0.64
Version:6.64 (B) (1 Oct 2015)

Upgrade Requirement:
Recommended - HP recommends users update to this version at their earliest convenience.

  • Running SMARTCTL (smartmontools) on HP Proliant G6/G7 (Px1x) Smart Array controllers that have firmware version 5.70 to 6.62 installed with SATA drives attached may result in system not responding or reboot. When reboot occurred, a reboot 1719 POST error message with lockup 0x15 displayed.

Version:6.64 (15 Jun 2015)

Upgrade Requirement:
Recommended - HP recommends users update to this version at their earliest convenience.

  • Running SMARTCTL (smartmontools) on HP Proliant G6/G7 (Px1x) Smart Array controllers that have firmware version 5.70 to 6.62 installed with SATA drives attached may result in system not responding or reboot. When reboot occurred, a reboot 1719 POST error message with lockup 0x15 displayed.

Version:6.62 (6 Apr 2015)

Upgrade Requirement:
Recommended - HP recommends users update to this version at their earliest convenience.

Problems Fixed:

  • On systems configured with HP Smart Array P711m controllers connected to logical volumes on HP P2000 G3 SAS storage arrays, the Smart Array device driver ‘hpsa’ would cease to function during installation of VMware vSphere 5.5 Update 2.
  • After the Smart Array device driver 'hpsa' was upgraded to version 3.4.6-165 on Red Hat Enterprise Linux 6 Update 4 or Update 5 on a server configured with logical volumes on HP P2000 G3 Storage Systems or HP MSA 2040 SAS Storage Arrays, the system would cease to function and an HP Smart Array P712m controller lockup would be reported after reboot. (POST Error: 1719 - A controller failure event occurred prior to this power-up. (Previous lock up code = 0x13))

Enhancements/New Features:

  • Performance enhancement when a drive starts to degrade due to excessive recovered media errors.

Version:6.60 (B) (30 Mar 2015)

Upgrade Requirement:
Recommended - HP recommends users update to this version at their earliest convenience.

  • Customers who already installed firmware version 6.60 do not need to update to 6.60 (B).

Problems Fixed in version 6.60:
This firmware release resolved the following issues:

  • After a mode toggle at EFI ORCA was performed, the controller name would not be displayed when running the command: “reconnect –r”.
  • Controller displayed a POST error message 1805 “Cache Module Super–Cap is not installed” when the controller was configured to work without super-capacitors.
  • Corrected thermal behavior with HDDs.
  • Controllers configured with one or more SATA spare drives and firmware version 6.40 (or earlier) may halt with 'Lockup Code = 0xAB' after 64, 128, or 256 days.
  • HP Smart Array P812 controller onboard expander firmware was updated to version 3.12 to enforce 3Gbps SATA connection speeds which is the maximum supported SATA data rate on HP Smart Array P212, P410, P410i, P411, P711m, P712m, and P812 controllers.

Enhancements/New Features:

  • Enhanced the controller SAS discovery logic to tolerate devices that may be resetting.
  • Added a new POST message 1813 to indicate bad or failed battery charge circuit.
Enhancements/New Features for 6.60 (B):
  • Added support for VMware vSphere 6.0

Version:6.6 (9 Sep 2014)

Upgrade Requirement:
Recommended - HP recommends users update to this version at their earliest convenience.

Problems Fixed in version 6.60:
This firmware release resolved the following issues:

  • After a mode toggle at EFI ORCA was performed, the controller name would not be displayed when running the command: “reconnect –r”.
  • Controller displayed a POST error message 1805 “Cache Module Super–Cap is not installed” when the controller was configured to work without super-capacitors.
  • Corrected thermal behavior with HDDs.
  • Controllers configured with one or more SATA spare drives and firmware version 6.40 (or earlier) may halt with 'Lockup Code = 0xAB' after 64, 128, or 256 days.
  • HP Smart Array P812 controller onboard expander firmware was updated to version 3.12 to enforce 3Gbps SATA connection speeds which is the maximum supported SATA data rate on HP Smart Array P212, P410, P410i, P411, P711m, P712m, and P812 controllers.

Enhancements/New Features:

  • Enhanced the controller SAS discovery logic to tolerate devices that may be resetting.
  • Added a new POST message 1813 to indicate bad or failed battery charge circuit.

Version:6.40(B) (18 Oct 2013)

Upgrade Requirement:
Recommended - HPE recommends users update to this version at their earliest convenience.

  • Customers who already installed firmware version 6.40 do not need to update to 6.40 (B).

Problems Fixed in version 6.40(B):

  • Fixed an installation issue where version 6.40 of the Online Smart Array firmware smart components for the Smart Array P410i Controller would in some cases update the SAS expander in the HP D2200sb Storage Blade with incorrect firmware causing the Smart Array P410i Controller to be unable to communicate with the hard drives installed in the HP D2200sb Storage Blade. Reference Customer Advisory c03964262 for additional important information about this issue.
Problems Fixed in version 6.40:
  • False POST 1705 messages were being posted on the HP BL465c G7 or HP BL685c G7 Blade systems that used HP Smart Array P410i controller firmware version 5.76 or greater. The POST was indicateding a bad Super-Cap, which in turn disabled write caching.
  • On rare occasions the controller would become unresponsive during POST.
  • On intermittent occasions, SATA spare drives in a JBOD were being marked as hot removed and then rediscovered.
  • Customers could not invoke ORCA via command line interface, by pressing the escape key-strokes “Esc+6” or 'F6' or “Esc+8” or 'F8' via the BIOS Serial Console.
Note: Version 6.40 is no longer available for download from HP Support Center, but the following fixes are also provided in version 6.40(B).

Enhancements/New Features:

  • Allow Windows Server 2012 drivers to utilize command addressing above the lower 4GB memory region when requested by the storage driver.
  • Version 6.40(B) added support for VMware vSphere 5.5.

Version:6.00 (19 Feb 2013)

Upgrade Requirement:
Recommended - HPE recommends users update to this version at their earliest convenience.
Important Note:

  • Do not upgrade HP ProLiant BL465c G7 or ProLiant BL685c G7 Server Blades with embedded P410i Smart Array Controllers to Smart Array Firmware Version 6.00. Some servers may experience an Array Accelerator Super-Capacitor charging failure and subsequent failure of the embedded P410i Smart Array Controller on specified servers.

Problems Fixed:
The following problems are addressed in version 6.00 of Online ROM Flash Component for VMware ESXi - Smart Array P212, P410, P410i, P411, P711m, P712m, and P812:

  • On rare occasions during power-up of an HP D2200sb the expander backplane would be unresponsive. When the expander backplane was unresponsive, the attached Smart Array Controller was not allowed to discover drives that were attached.
  • On an HP P812 controller, executing several sequential Write operations to more than 75 hard drives would result in a controller lockup.
  • Modified the FBWC module code to improve the training of the DDR2 DIMMs in order to prevent the rare occasions when 1783 POST error messages displays followed by an unresponsive controller.
  • Protection has been added to prevent potential Smart Array controller hangs under rare conditions when hot-adding hard drives.
  • When running in a Solaris environment, Smart Array firmware version 6.00 works around an issue where the driver would not handle asynchronous events from the Smart Array controller properly.
  • An interaction issue occurred between the Smart Array Controller and HP SAS Expander card in which the Hard Drives attached to the HP SAS Expander were not being discovered occasionally upon boot up or hot plug.
  • On rare occasions, the Smart Array controller would reset the same SATA drive several times when a PHY is stuck longer than four seconds.
  • The Smart Array P711m and P712m would report false link errors.
  • The Open Connection timeout was reduced to 900 microseconds so that SAS connections terminate gracefully and data transfer stalls are prevented.
  • The Smart Array controller would not connect to hard drives within 20ms under heavy stress.
  • Upon power up, a Post message will now be displayed to the user to indicate that a cache module is needed for the P711m controller.
  • When running heavy I/O in RAID 5, while an HP P410 controller was connected to more than 17 SAS drives in an HP DL180 G6 server with a 25SFF backplane, a lockup issue (error code 0xAB or 0xEA) could occur.
  • During heavy I/O when the HP P711m controller is connected to a HP P2000sa G3 MSA Array System via a HP 6Gb SAS Switch, a lockup issue (error code 0x15) could occur.
  • After a system with (2) or more empty SAS storage boxes, Box 1, 2, 3 …, attached to an HP SAS Expander card is powered up and then a drive is hot plugged into Box 2 or above, ACU and ORCA would incorrectly display the drive in Box 1.

Version:5.70(B) (17 Jan 2013)

Upgrade Requirement:
Recommended - HPE recommends users update to this version at their earliest convenience.
Customers who already installed firmware version 5.70 do not need to update to 5.70(B).

Problems Fixed:

  • Fixed an issue with the HP P812 controller in which a rare lockup (code 0xD4) could occur upon reboot.
  • Fixed an issue where disk location information was reported incorrectly in the HP DL580 G5 with the HP SAS Expander card
  • Fixed an issue where a RAID 6 volume could have inconsistent parity data in the last stripe in certain configurations after a volume transformation operation had occurred.
  • Fixed an issue where removal of a HP P2000saG3 controller module could cause a controller lockup (code 0xAB).
  • Fixed an issue where the hot-add of a 3TB drive to HP DL180G6 12 drive backplane could cause the controller to lock up (code 0x15).
  • Fixed an issue where the controller would lock up (code 0xBC) due to incorrectly placing host data into a write-cache line that had a memory error.
  • Fixed an issue where a controller configured for 100% read cache could cause a false 'A cache error was detected. Run a diagnostic report for more information' error to be displayed in the 'Cache Status Details' column in ACU.
  • Fixed an issue where after hot-adding a SATA disk to an MSA-60, MSA-70, or HP DL180-G6 12-drive backplane, the storage controller could become unresponsive. Reference Customer Advisory c03011608.
  • Fixed an issue where the controller could become unresponsive while handling a hot-removal event when experiencing heavy I/O.
  • Fixed an issue that could be experienced during a volume transformation operation. If a logical Unrecovered Read Error occurred, it could cause the bad block(s) to be moved to the incorrect location in the transformed volume if the original volume was configured at an offset in the array.
  • Fixed an issue where simultaneous handling of many Unrecoverable Read Errors on SATA disks supporting Native Command Queuing could result in a lockup (code 0x15).
  • Fixed an issue where a disk of size >2TB could be incorrectly marked as failed.
  • Fixed an issue that caused a lockup (code 0x13) with a SSD RAID 10 array under heavy I/O load.
  • Fixed an issue where SATA disks could occasionally be marked as failed or missing during boot when no cache module is installed on the controller.
  • Fixed an issue where a controller running with no cache module, attached to SATA disks, could encounter a lockup (code 0x15) when running HP Insight Diagnostics software or offline HDD firmware flash utility.
  • Fixed an issue with cable pull between the controller and an enclosure IO module that would cause a lockup (code 0x13) in Open VMS / Solaris systems.
  • Fixed several issues that caused the controller to become unresponsive at boot up time. Reference CA C03161926.
  • Fixed the controller firmware to properly process F1 and F2 keys at startup. Reference CA c03127437.
  • Fixed an issue in which 3TB drives were not managed as spares.
  • Fixed an issue in which the Server Serial Number, Product ID, and Other Configurations were cleared or set to default. Reference Customer Advisory c03083515
  • FW version 5.70(B) - Fixed an issue where installation of the component would not complete under HP Insight Control for vCenter.

Type:Firmware - Storage Controller
Version:6.62(6 Apr 2015)
Operating System(s):
VMware ESXi 5.0
VMware vSphere 5.1
VMware vSphere 5.5
VMware vSphere 6.0

Description

This Smart Component provides firmware for the following storage controllers: Smart Array P212, P410, P410i, P411, P711m, P712m, and P812

Enhancements

Enhancements/New Features:

  • Performance enhancement when a drive starts to degrade due to excessive recovered media errors.

Installation Instructions

To ensure the integrity of your download, HP recommends verifying your results with the following MD5 Checksum values:

27660a8a865d40cf281955449521f862CP025733.md5
ecfb82c5eeb4d8dbb189b334befee7b3CP025733.scexe

Reboot Requirement:
Reboot is required after installation for updates to take effect and hardware stability to be maintained.

Installation:
To use HP Smart Update Manager from the HP Service Pack for ProLiant:
Offline (The SPP Offline mode boots a special Linux OS environment, thus the Linux Smart Components are used, not the VMware Smart Components):

  • Place the HP Service Pack for ProLiant on a USB key using the HP USB Key Creator Utility.
  • Place the desired Linux firmware component to be updated in the directory, /hp/swpackages on the USB key.
  • Boot from the newly created HP Service Pack for ProLiant USB key.
  • Follow HP Smart Update Manager steps to complete firmware update.
Remote Online:
  • Download the appropriate SPP.
  • Add the component to the SPP.
  • Mount the SPP on a remote server running Windows or Linux that has a network connection to the ESXi host to be updated.
  • Run HP SUM.
  • Add the ESXi host to be updated as a remote target/node.
  • Enter IP or DNS address of the ESXi host to be updated Enter the ESXi host credentials (root or administrator username and password).
  • For HP SUM 6.0 and newer, select both the Additional Package with the added component and the SPP Baseline on the node Inventory page.
  • Follow HP Smart Update Manager Steps and complete the firmware update.
Refer to the SPP documentation for detailed instructions at: http://www.hp.com/go/spp
To use HP Insight Control for vCenter :
  • Log in to the vSphere Client.
  • Select a server or cluster in the inventory tree.
  • Click the HP Insight Management tab.
  • Follow Insight Control for vCenter steps to update firmware using a Smart Component
To update firmware from VMware ESXi operating system on target server:
  • Enable Tech Support Mode on the ESXi host.
  • Login as root. (You must be root in order to apply the ROM update.)
  • Place the Smart Component in a temporary directory.
  • From the same directory, execute the Smart Component. For example: ./CPXXXXXX.scexe
  • Follow the directions given by the Smart Component.
  • Logout
  • Disable Tech Support Mode on the ESXi host.
  • Reboot your system, if required, for the firmware update to take effect.

Release Notes

End User License Agreements:
Hewlett-Packard End User License Agreement

Upgrade Requirement:
Recommended - HP recommends users update to this version at their earliest convenience.

Important:
Important Notes:

  • Reference Customer Advisory c03793656 - Windows Server 2012 - HP ProLiant Server May Blue Screen if Configured With an HP Smart Array Controller and the Windows Server 2012 HPCISSS2.SYS Driver Version 62.26.0.64

Notes:
Deliverable Name:

Online ROM Flash Component for VMware ESXi - Smart Array P212, P410, P410i, P411, P711m, P712m, and P812
Release Version and/or Date:
6.62
Last Recommended or Critical Version:
6.60
Previous Version of Firmware:
6.60
Firmware Dependency:
None
Enhancements/New Features:

  • Performance enhancement when a drive starts to degrade due to excessive recovered media errors.
Problems Fixed:
  • On systems configured with HP Smart Array P711m controllers connected to logical volumes on HP P2000 G3 SAS storage arrays, the Smart Array device driver ‘hpsa’ would cease to function during installation of VMware vSphere 5.5 Update 2.
  • After the Smart Array device driver 'hpsa' was upgraded to version 3.4.6-165 on Red Hat Enterprise Linux 6 Update 4 or Update 5 on a server configured with logical volumes on HP P2000 G3 Storage Systems or HP MSA 2040 SAS Storage Arrays, the system would cease to function and an HP Smart Array P712m controller lockup would be reported after reboot. (POST Error: 1719 - A controller failure event occurred prior to this power-up. (Previous lock up code = 0x13))

Known Issues:
None

Fixes

Upgrade Requirement:
Recommended - HP recommends users update to this version at their earliest convenience.

Problems Fixed:

  • On systems configured with HP Smart Array P711m controllers connected to logical volumes on HP P2000 G3 SAS storage arrays, the Smart Array device driver ‘hpsa’ would cease to function during installation of VMware vSphere 5.5 Update 2.
  • After the Smart Array device driver 'hpsa' was upgraded to version 3.4.6-165 on Red Hat Enterprise Linux 6 Update 4 or Update 5 on a server configured with logical volumes on HP P2000 G3 Storage Systems or HP MSA 2040 SAS Storage Arrays, the system would cease to function and an HP Smart Array P712m controller lockup would be reported after reboot. (POST Error: 1719 - A controller failure event occurred prior to this power-up. (Previous lock up code = 0x13))

Important

Important Notes:
  • Reference Customer Advisory c03793656 - Windows Server 2012 - HP ProLiant Server May Blue Screen if Configured With an HP Smart Array Controller and the Windows Server 2012 HPCISSS2.SYS Driver Version 62.26.0.64

Revision History

Version:6.64 (B) (1 Oct 2015)

Upgrade Requirement:
Recommended - HP recommends users update to this version at their earliest convenience.

  • Running SMARTCTL (smartmontools) on HP Proliant G6/G7 (Px1x) Smart Array controllers that have firmware version 5.70 to 6.62 installed with SATA drives attached may result in system not responding or reboot. When reboot occurred, a reboot 1719 POST error message with lockup 0x15 displayed.

Version:6.64 (15 Jun 2015)

Upgrade Requirement:
Recommended - HP recommends users update to this version at their earliest convenience.

  • Running SMARTCTL (smartmontools) on HP Proliant G6/G7 (Px1x) Smart Array controllers that have firmware version 5.70 to 6.62 installed with SATA drives attached may result in system not responding or reboot. When reboot occurred, a reboot 1719 POST error message with lockup 0x15 displayed.

Version:6.62 (6 Apr 2015)

Upgrade Requirement:
Recommended - HP recommends users update to this version at their earliest convenience.

Problems Fixed:

  • On systems configured with HP Smart Array P711m controllers connected to logical volumes on HP P2000 G3 SAS storage arrays, the Smart Array device driver ‘hpsa’ would cease to function during installation of VMware vSphere 5.5 Update 2.
  • After the Smart Array device driver 'hpsa' was upgraded to version 3.4.6-165 on Red Hat Enterprise Linux 6 Update 4 or Update 5 on a server configured with logical volumes on HP P2000 G3 Storage Systems or HP MSA 2040 SAS Storage Arrays, the system would cease to function and an HP Smart Array P712m controller lockup would be reported after reboot. (POST Error: 1719 - A controller failure event occurred prior to this power-up. (Previous lock up code = 0x13))

Enhancements/New Features:

  • Performance enhancement when a drive starts to degrade due to excessive recovered media errors.

Version:6.60 (B) (30 Mar 2015)

Upgrade Requirement:
Recommended - HP recommends users update to this version at their earliest convenience.

  • Customers who already installed firmware version 6.60 do not need to update to 6.60 (B).

Problems Fixed in version 6.60:
This firmware release resolved the following issues:

  • After a mode toggle at EFI ORCA was performed, the controller name would not be displayed when running the command: “reconnect –r”.
  • Controller displayed a POST error message 1805 “Cache Module Super–Cap is not installed” when the controller was configured to work without super-capacitors.
  • Corrected thermal behavior with HDDs.
  • Controllers configured with one or more SATA spare drives and firmware version 6.40 (or earlier) may halt with 'Lockup Code = 0xAB' after 64, 128, or 256 days.
  • HP Smart Array P812 controller onboard expander firmware was updated to version 3.12 to enforce 3Gbps SATA connection speeds which is the maximum supported SATA data rate on HP Smart Array P212, P410, P410i, P411, P711m, P712m, and P812 controllers.

Enhancements/New Features:

  • Enhanced the controller SAS discovery logic to tolerate devices that may be resetting.
  • Added a new POST message 1813 to indicate bad or failed battery charge circuit.
Enhancements/New Features for 6.60 (B):
  • Added support for VMware vSphere 6.0

Version:6.6 (9 Sep 2014)

Upgrade Requirement:
Recommended - HP recommends users update to this version at their earliest convenience.

Problems Fixed in version 6.60:
This firmware release resolved the following issues:

  • After a mode toggle at EFI ORCA was performed, the controller name would not be displayed when running the command: “reconnect –r”.
  • Controller displayed a POST error message 1805 “Cache Module Super–Cap is not installed” when the controller was configured to work without super-capacitors.
  • Corrected thermal behavior with HDDs.
  • Controllers configured with one or more SATA spare drives and firmware version 6.40 (or earlier) may halt with 'Lockup Code = 0xAB' after 64, 128, or 256 days.
  • HP Smart Array P812 controller onboard expander firmware was updated to version 3.12 to enforce 3Gbps SATA connection speeds which is the maximum supported SATA data rate on HP Smart Array P212, P410, P410i, P411, P711m, P712m, and P812 controllers.

Enhancements/New Features:

  • Enhanced the controller SAS discovery logic to tolerate devices that may be resetting.
  • Added a new POST message 1813 to indicate bad or failed battery charge circuit.

Version:6.40(B) (18 Oct 2013)

Upgrade Requirement:
Recommended - HPE recommends users update to this version at their earliest convenience.

  • Customers who already installed firmware version 6.40 do not need to update to 6.40 (B).

Problems Fixed in version 6.40(B):

  • Fixed an installation issue where version 6.40 of the Online Smart Array firmware smart components for the Smart Array P410i Controller would in some cases update the SAS expander in the HP D2200sb Storage Blade with incorrect firmware causing the Smart Array P410i Controller to be unable to communicate with the hard drives installed in the HP D2200sb Storage Blade. Reference Customer Advisory c03964262 for additional important information about this issue.
Problems Fixed in version 6.40:
  • False POST 1705 messages were being posted on the HP BL465c G7 or HP BL685c G7 Blade systems that used HP Smart Array P410i controller firmware version 5.76 or greater. The POST was indicateding a bad Super-Cap, which in turn disabled write caching.
  • On rare occasions the controller would become unresponsive during POST.
  • On intermittent occasions, SATA spare drives in a JBOD were being marked as hot removed and then rediscovered.
  • Customers could not invoke ORCA via command line interface, by pressing the escape key-strokes “Esc+6” or 'F6' or “Esc+8” or 'F8' via the BIOS Serial Console.
Note: Version 6.40 is no longer available for download from HP Support Center, but the following fixes are also provided in version 6.40(B).

Enhancements/New Features:

  • Allow Windows Server 2012 drivers to utilize command addressing above the lower 4GB memory region when requested by the storage driver.
  • Version 6.40(B) added support for VMware vSphere 5.5.

Version:6.00 (19 Feb 2013)

Upgrade Requirement:
Recommended - HPE recommends users update to this version at their earliest convenience.
Important Note:

  • Do not upgrade HP ProLiant BL465c G7 or ProLiant BL685c G7 Server Blades with embedded P410i Smart Array Controllers to Smart Array Firmware Version 6.00. Some servers may experience an Array Accelerator Super-Capacitor charging failure and subsequent failure of the embedded P410i Smart Array Controller on specified servers.

Problems Fixed:
The following problems are addressed in version 6.00 of Online ROM Flash Component for VMware ESXi - Smart Array P212, P410, P410i, P411, P711m, P712m, and P812:

  • On rare occasions during power-up of an HP D2200sb the expander backplane would be unresponsive. When the expander backplane was unresponsive, the attached Smart Array Controller was not allowed to discover drives that were attached.
  • On an HP P812 controller, executing several sequential Write operations to more than 75 hard drives would result in a controller lockup.
  • Modified the FBWC module code to improve the training of the DDR2 DIMMs in order to prevent the rare occasions when 1783 POST error messages displays followed by an unresponsive controller.
  • Protection has been added to prevent potential Smart Array controller hangs under rare conditions when hot-adding hard drives.
  • When running in a Solaris environment, Smart Array firmware version 6.00 works around an issue where the driver would not handle asynchronous events from the Smart Array controller properly.
  • An interaction issue occurred between the Smart Array Controller and HP SAS Expander card in which the Hard Drives attached to the HP SAS Expander were not being discovered occasionally upon boot up or hot plug.
  • On rare occasions, the Smart Array controller would reset the same SATA drive several times when a PHY is stuck longer than four seconds.
  • The Smart Array P711m and P712m would report false link errors.
  • The Open Connection timeout was reduced to 900 microseconds so that SAS connections terminate gracefully and data transfer stalls are prevented.
  • The Smart Array controller would not connect to hard drives within 20ms under heavy stress.
  • Upon power up, a Post message will now be displayed to the user to indicate that a cache module is needed for the P711m controller.
  • When running heavy I/O in RAID 5, while an HP P410 controller was connected to more than 17 SAS drives in an HP DL180 G6 server with a 25SFF backplane, a lockup issue (error code 0xAB or 0xEA) could occur.
  • During heavy I/O when the HP P711m controller is connected to a HP P2000sa G3 MSA Array System via a HP 6Gb SAS Switch, a lockup issue (error code 0x15) could occur.
  • After a system with (2) or more empty SAS storage boxes, Box 1, 2, 3 …, attached to an HP SAS Expander card is powered up and then a drive is hot plugged into Box 2 or above, ACU and ORCA would incorrectly display the drive in Box 1.

Version:5.70(B) (17 Jan 2013)

Upgrade Requirement:
Recommended - HPE recommends users update to this version at their earliest convenience.
Customers who already installed firmware version 5.70 do not need to update to 5.70(B).

Problems Fixed:

  • Fixed an issue with the HP P812 controller in which a rare lockup (code 0xD4) could occur upon reboot.
  • Fixed an issue where disk location information was reported incorrectly in the HP DL580 G5 with the HP SAS Expander card
  • Fixed an issue where a RAID 6 volume could have inconsistent parity data in the last stripe in certain configurations after a volume transformation operation had occurred.
  • Fixed an issue where removal of a HP P2000saG3 controller module could cause a controller lockup (code 0xAB).
  • Fixed an issue where the hot-add of a 3TB drive to HP DL180G6 12 drive backplane could cause the controller to lock up (code 0x15).
  • Fixed an issue where the controller would lock up (code 0xBC) due to incorrectly placing host data into a write-cache line that had a memory error.
  • Fixed an issue where a controller configured for 100% read cache could cause a false 'A cache error was detected. Run a diagnostic report for more information' error to be displayed in the 'Cache Status Details' column in ACU.
  • Fixed an issue where after hot-adding a SATA disk to an MSA-60, MSA-70, or HP DL180-G6 12-drive backplane, the storage controller could become unresponsive. Reference Customer Advisory c03011608.
  • Fixed an issue where the controller could become unresponsive while handling a hot-removal event when experiencing heavy I/O.
  • Fixed an issue that could be experienced during a volume transformation operation. If a logical Unrecovered Read Error occurred, it could cause the bad block(s) to be moved to the incorrect location in the transformed volume if the original volume was configured at an offset in the array.
  • Fixed an issue where simultaneous handling of many Unrecoverable Read Errors on SATA disks supporting Native Command Queuing could result in a lockup (code 0x15).
  • Fixed an issue where a disk of size >2TB could be incorrectly marked as failed.
  • Fixed an issue that caused a lockup (code 0x13) with a SSD RAID 10 array under heavy I/O load.
  • Fixed an issue where SATA disks could occasionally be marked as failed or missing during boot when no cache module is installed on the controller.
  • Fixed an issue where a controller running with no cache module, attached to SATA disks, could encounter a lockup (code 0x15) when running HP Insight Diagnostics software or offline HDD firmware flash utility.
  • Fixed an issue with cable pull between the controller and an enclosure IO module that would cause a lockup (code 0x13) in Open VMS / Solaris systems.
  • Fixed several issues that caused the controller to become unresponsive at boot up time. Reference CA C03161926.
  • Fixed the controller firmware to properly process F1 and F2 keys at startup. Reference CA c03127437.
  • Fixed an issue in which 3TB drives were not managed as spares.
  • Fixed an issue in which the Server Serial Number, Product ID, and Other Configurations were cleared or set to default. Reference Customer Advisory c03083515
  • FW version 5.70(B) - Fixed an issue where installation of the component would not complete under HP Insight Control for vCenter.

Add License Key - Smart Array P410i In Embedded Slot Machine

Legal Disclaimer: Products sold prior to the November 1, 2015 separation of Hewlett-Packard Company into Hewlett Packard Enterprise Company and HP Inc. may have older product names and model numbers that differ from current models.