HP Array Controller Utility CLI – Usage – 01

Background

Let us quickly cover a few commands that can be issued within the HP Array Controller Utility CLI.

Initiate

Let us initiate “HP Array Controller Utility CLI”.

Desktop

Start Menu

HPArrayConfigurationUtility.CLI.01.20190611.0355PM.PNG

CLI Properties

HPArrayConfigurationUtility.CLI.App.01.20190611.0357PM.PNG

Path & App Name

“C:\Program Files (x86)\Compaq\Hpacucli\Bin\hpacucli.exe”

 

Commands

Outline

  1. Controller
    • Show Controller Status
  2. Disks
    • Physical Disk
      • Show information for all Physical Disks
      • Show information for specific Physical Disk
    • Logical Disk
      • Show information for all Logical Disks
      • Show information for specific Logical disk

Tasks

Controller

Show Controller Status

Syntax

controller all show status

Output

Explanation
  1. Smart Array
    • Smart Array P410i
      • Slot 0

 

Disks

Physical Disks

Show Physical Disks Status for all Discs
Syntax

controller slot=0 pd all show

Output

Explanation
  1. Shows information for each physical disks
    • Port
    • Box
    • Bay
    • Drive Type
      • SAS
    • Drive Size
      • 900 GB
    • Status
      • OK

 

Show Physical Disks Status for Specific Disk
Sample

controller slot=0 pd 3C:1:5 show

Output

Explanation
  1. Shows information for targeted physical disks
    • Port
    • Box
    • Bay
    • Interface Type
      • SAS
    • Drive Size
      • 900 GB
    • Rotational Speed
      • 10000
    • Firmware Revision
    • Model
      • Model: HP EG000300JWFVB
    • Physical Count
      • 2
    • Physical Transfer Rate
      • 6.0Gbps, Unknown

 

Logical Disks

Show Logical Disks Status for all Discs
Syntax

controller slot=0 ld all show

Output

Explanation
  1. Shows information for each array
    • Array
      • Logical Drive
        • Size
        • RAID Level
          • RAID 5
          • RAID 1
        • Status
          • OK
Show Logical Disks Status for targeted Disc
Syntax

controller slot=0 ld 4 show

Output

Explanation
  1. Shows information for targeted Logical Drive
    • Size
    • Fault Tolerance
      • RAID 5
    • Status
      • OK
    • Caching
      • Enabled
    • Mount Points
      • Drive F:
    • Drive Type

References

  1. HP
    • Hewlett Packard Enterprise Support Center
      • Hpacucli Utility for Linux – All Commands Guide
        Link
  2. The Geek Stuff
    • hpacucli Command Examples for Linux on HP Servers
      Link
  3. PHUOCTAI HUYNH
    • HP SERVER DISK HEALTH CHECK
      Link

HP – Error Message – Array controller P410i [Embedded] was of an unknown or unrecognized class.

Background

About once a day, we started seeing the error posted below in our Event Viewer.

Error Message

Message Detail

  1. Source :- Cissesrv
  2. Event ID: 24607
  3. Error Message :- The event information received from array controller P410i [Embedded] was of an unknown or unrecognized class.
    An excerpt of the controller message is as follows: Surface Analysis Pass Information, LDrv=0 Number of passes=84.

 

Browse Errors

BrowseErrors

 

Diagnosis

Source

Where is the error coming from?

In the Source column we see Cissesrv

 

Registry

Did a quick search in MS Windows Registry for cissesrv

cissesrv

 

Services

We see that Cisserv is a service known as HP Smart Array SAS/SATA Event Notification Service.

 

HPSmartArraySAS-SATAEventNotificationService

Product and File Version

Checked the folder referenced for the file … C:\Program Files\HP\Cissesrv

Version

  1. File Version :- 6.18.0.64
  2. Product Version :- 6.18.0.64
  3. Copyright 2003, 2010

 

Device Manager

SmartArrayP410iController

 

  1. Driver version: 6.28.0.64
  2. Driver Date: 10/28/2013

 

HP Advisory

There is an HP Advisory titled “Advisory: HP Smart Array Controllers – Multiple Event ID 24607 Messages May be Generated By HP ProLiant Smart Array SAS/SATA Event Notification Service for Windows on Servers Configured With Smart Array Controllers Running Firmware Version 5.12 (or Later)” and available @ Link.

Description

Beginning with the Smart Array Controller Firmware Versions 5.12, a new Event Notification Class was added into the firmware and HP ProLiant Smart Array SAS/SATA Event Notification Service for Windows 6.22 (or earlier) does not have the support for this new Event Class. Therefore, it will log Event ID 24607 as an unknown Event.

SCOPE

Any HP ProLiant server configured with any HP Smart Array controller running firmware version 5.12 (or later) and running Windows Server 2003 or Windows Server 2008 with HP ProLiant Smart Array SAS/SATA Event Notification Service for Windows Server 2003/2008 Version 6.22 (or earlier) installed.

 

Resolution

Apply HP ProLiant Smart Array SAS/SATA Event Notification Service for Windows Server 2008 x64 or x86 Editions Version 6.24 (or later).

 

Applicability

Here is the applicability to our environment:

  1. Notification Service
    • We are running 6.18 and it seems we need to be at 6.24 or later
  2. Driver
    • HP Smart Array P410i Controller
      • We are running 6.28.0.64
      • The scope of the upgrade is for those running 5.12 or later

 

Identify & Download Patch

Direct Links

Here are the current links.

 

Name Type Version OS Filename Reboot Link
HP ProLiant Smart Array SAS/SATA Event Notification Service for Windows Server 2008 x64 Editions and Windows Server 2012  Software – Storage Controller  6.42.0.64 (15 Jun 2015)  v2012, v2008/R2, v2008  cp025886.exe (795 KB)  No  Link

 

 

Identify Missing Patches

You might want to explore any other missing patches.

  1. Launch Web Bowser
  2. Access “HP Customer Support – Software and Driver Downloads” by entering the URL http://support.hp.com/us-en/drivers
  3. Choose “Identify Now” button
  4. In the download Options tab, choose “Drivers, Software, and Firmware
  5. The HP Devices detected are
    • HP DL380z Gen9 Virtual Workstation
  6. In our case, the lone missing software is:
    • HP PC Hardware Diagnostics UEFI (International)
      5.9.1.0 Rev.A
      30 Oct 2015
      24.3 MB
  7. Download patch

Identify & Download Software

Devices Detected

DevicesDetected

 

Download Options

DownloadOptions

 

Missing Updates

DiagnosticSoftware

 

Apply Patch

Once download, apply patch, reboot box, and confirm that Notification Service has been updated.

File Properties

Here is the updated file’s property.

20160126

  1. File Version :- 6.44.0.64
  2. Product Version :- 6.44.0.64
  3. Copyright 2003, 2015

HP – Software – Driver \ Firmware Patches (2012)

HP – Software – Driver \ Firmware Patches (2012)

Science is all about being a busy body; some call it being curious.

If you lack interest, if you lack joy for it — Then you probably should not be in Technology; or at least in particular sub-domains of it.

So installed patches earlier in the week and occasionally one has the interest to go back and document the patch a bit; while doing so, you hopefully deepen your overall understanding.

So you Goggle until your wrist hurt — How I wish I was one of those with the gentle typist fingers … Wow must be nice.

So anyways I have this HP Patch that is geared towards MS Windows Installation.  And, thank Goodness it is pre-packaged as a MS Windows Executable (exe).

So no problem with installation … Just run and you have a nice GUI…

But, wanted to dig in a bit and see what is exactly being bundled.

To do so, launched the installer and chose the “Extract” option:

For this executable, got the following files:

  1. bcu.exe
  2. bfa_boot_fw
  3. boot.txt
  4. BootImageInfo.xml
  5. cp017397.xml
  6. cpqsetup.exe
  7. installer.dll
  8. reference.xml

Let us dig a bit deeper per each file:

bcu.exe

  • This file is the Brocade CLI Utility.  CLI means Command Line Utility.
  • As the name suggests to really use the utility launch a command shell and start digging around command line options

bfa_boot_fw

  • Not so sure when this file is used
  • It contains entries in old style item = value designation
#
# Template for the entries for a particular type of card
#
# <Field Name>   = <Value>    
# CARDTYPE(*)   = <Model type>
# DESCRIPTION= <Brief description of the card>
# FWCFG(M)     = <Firmware Configuration file name>

Sample Entries

CARDTYPE=415
DESCRIPTION=Brocade 4G FC HBA
FIRMWARE=cbfw.bin
OPTROM=bfa_option.rom
BOOTOVL=all.ovl

CARDTYPE=815
DESCRIPTION=Brocade 8G FC HBA
FIRMWARE=cbfw.bin
OPTROM=bfa_option.rom
BOOTOVL=all.ovl

boot.txt

Seem basis as bfa_boot_fw will suffice.

bootImageInfo.xml

  • As the file extension suggests this is a true XML file
  • It has the version#
  • The package’s release date
  • SupportedDrivers — That is which version# of the base Drivers are supported
  • And, a hash#

sample

<bootimage>
<version>3.0.3.4</version>
<releaseDate>04-20-2012</releaseDate>
<supportedDrivers>3.0+</supportedDrivers>
<hash>62a2ef7f32ead1f598033ca61fdbbd84</hash>
</bootimage>

cp017397.xml

  • This is also an XML file
  • It is much more detailed that other XML files (in the bundle)
  • It is probably the most revealing in terms of HP’s Engineering predigree
  • It has entries for Division — In this case Networking / Server
  • Lists the Operating Systems Supported – In this case Microsoft Windows Server 2003 x64 Edition, Microsoft Windows Server 2008 x64, Microsoft Windows Server 2008 R2
  • Version# – 2012.05.01
  • Language List – English / Japanese
  • Description – “This component upgrades the boot BIOS of Brocade fibre channel host bus adapters“.
  • Prerequisites – “Requires Brocade version 3.0.0.0 storport driver that can be obtained from the Service Pack for Proliant (SPP).”
  • Revisions / Enhancements
    – to resolve an issue when performing boot from san (bfs) with 3Par arrays.
    –  to resolve an HBA (Host Bus Adapter) disconnect issue seen on some configurations.
  • Supported OSes
  • Supported Devices
    – Vendor – 1657
    – Device – 0013

Areas that were a bit missing are:

  • Signature \ Fingerprint in terms of determining how to identify machines that have the software installed
  • Device Identification that might allow one to Identify\map the Hardware Device — This is useful in CMDB and also when one is looking for more KB over in the Internet (ie http://pcidatabase.com)

Conclusion:

Here is my takeaway:  HP puts in a lot of work into documenting these patches.  They carefully note which OSes it can be installed on.  The underlying software version that has to be currently installed.  And, the problems that are being addressed are listed.

References:

Microsoft – Windows \ SQL Server on HP Servers using Brocade\Mezzanine HBA Card – Error Source – bfad – Error Message – Heartbeat of IOC has failed

Microsoft – Windows \ SQL Server on HP Servers

When I first move to the Bay Area, I had the good fortune of working with one of the giant publishing companies.

I remember we had a Box that kept crashing.  Finally, the vendor owned up to it and sent us a replacement box.

What brings it to mind is that the in-house OS Administrator was literally crying that finally the vendor believed him.  And, shall we say he was able to sleep as the old server was a lemon.

Read more about California’s (CA) Motor Vehicle Warranty & Lemon Law
http://oag.ca.gov/consumers/general/lemon

These days you can sleep better.  You have the Internet and a community of techies writing down their experiences.

And, thank goodness for Google.  Just know what to look for and since it is so fast you have many gos at it.

Each is own, I do not read anymore – I just google it.  No wonder our bookstores are out of business; less to talk of community\city libraries.

Back to our discussions..

So on your Windows Box, if you start seeing errors such as:

1) In your Windows Event Viewer Log

– Branch : System
– Source : bfad
– Level : critical
– Message : Heartbeat of IOC has failed

2) And, on your Brocade\Mezzanine “Host Connectivity Manager” \ HCM Log will contain something close to this:

3) And, today is not the day you will go completely crazy nor start sobbing at work

Then look to your Brocade Mezzanie card that is quite common with HP Blade Servers.

HP Description states:

This occurs because the Brocade 804 mezzanine card BIOS incorrectly self-configures architecture internal to the ASIC, resulting in data throughput that can cause brief losses of the fabric connection. Occurrences may be more noticeable with an increased number of LUNs.

The error was fixed in BIOS revision 3.0.3.4. And, the post is dated June 5th, 2012.

So five months later it bit us.

To remediate:

  • Apply “HP Firmware Online Flash for Brocade Fibre Channel Host Bus Adapters” version 2012.05.01 or later

HP’s excellent and most useful write-up is available @

Advisory: Brocade 804 8Gb Fibre Channel HBA for HP BladeSystem c-Class- Adapter May Experience a Brief Loss of Fabric Connection on All Ports

http://h20000.www2.hp.com/bizsupport/TechSupport/Document.jsp?objectID=c03362107&lang=en&cc=us&taskId=135&prodSeriesId=3676868&prodTypeId=15351

As of election day 2012 the latest patch is

Type: Firmware – Storage Fibre Channel
Version: 2012.10.01 (26 Oct 2012)
File name: cp018011.exe (2.5 MB)

And, it is available @

http://h20000.www2.hp.com/bizsupport/TechSupport/SoftwareDescription.jsp?lang=en&cc=us&swLang=8&mode=2&taskId=135&swItem=MTX-98c4a6eb74a64a2c9e40489cff