Hi Jesse,
Both VMware and HP has not been much of a help.
I've found two semi useful tools my self:
1: lsiprovider (CiM provider)
2: Sas2IRCU (cli program)
Both tools are available in on the lsi.com website.
The first one presents some information about the controller and its disks in the hardware status.
The second one is the most valuable. It provides information about the controller and the disks in the vmware cli:
~ # /opt/lsi/bin/sas2ircu LIST
LSI Corporation SAS2 IR Configuration Utility.
Version 20.00.00.00 (2014.09.18)
Copyright (c) 2008-2014 LSI Corporation. All rights reserved.
Adapter Vendor Device SubSys SubSys
Index Type ID ID Pci Address Ven ID Dev ID
----- ------------ ------ ------ ----------------- ------ ------
0 SAS2308_2 1000h 87h 00h:07h:00h:00h 1590h 0041h
SAS2IRCU: Utility Completed Successfully.
~ # /opt/lsi/bin/sas2ircu 0 DISPLAY
LSI Corporation SAS2 IR Configuration Utility.
Version 20.00.00.00 (2014.09.18)
Copyright (c) 2008-2014 LSI Corporation. All rights reserved.
Read configuration has been initiated for controller 0
------------------------------------------------------------------------
Controller information
------------------------------------------------------------------------
Controller type : SAS2308_2
BIOS version : 7.25.06.00
Firmware version : 15.10.07.00
Channel description : 1 Serial Attached SCSI
Initiator ID : 0
Maximum physical devices : 255
Concurrent commands supported : 8192
Slot : 2
Segment : 0
Bus : 7
Device : 0
Function : 0
RAID Support : No
------------------------------------------------------------------------
IR Volume information
------------------------------------------------------------------------
------------------------------------------------------------------------
Physical device information
------------------------------------------------------------------------
Initiator at ID #0
Device is a Enclosure services device
Enclosure # : 2
Slot # : 0
SAS Address : 5001438-0-314c-aad3
State : Standby (SBY)
Manufacturer : HP
Model Number : Gen8 ServBP 25+2
Firmware Revision : 3.30
Serial No : PC1L
GUID : N/A
Protocol : SAS
Device Type : Enclosure services device
Device is a Hard disk
Enclosure # : 2
Slot # : 1
SAS Address : 5000c50-0-7e13-c73d
State : Ready (RDY)
Size (in MB)/(in sectors) : 286102/585937499
Manufacturer : HP
Model Number : EH0300FBQDD
Firmware Revision : HPD3
Serial No :XXXXXXXXXXXXX
GUID : 5000c5007e13c73f
Protocol : SAS
Drive Type : SAS_HDD
Device is a Hard disk
Enclosure # : 2
Slot # : 2
SAS Address : 5000c50-0-7e13-17b9
State : Ready (RDY)
Size (in MB)/(in sectors) : 286102/585937499
Manufacturer : HP
Model Number : EH0300FBQDD
Firmware Revision : HPD3
Serial No : XXXXXXXXXXXXXL
GUID : 5000c5007e1317bb
Protocol : SAS
Drive Type : SAS_HDD
Even the locatorled function is working. That makes it possible to find a broken disk. (Although an error is printed turning on a led.)
I think the poor performance for the p420 is only in pass-through mode.The commando queue is much bigger than on the H220. And all the monitoring and cmd-line tools are working out off the box.
I remember some information from a HP consultant about the need for cache memory on the P420 to enable optimum bandwidth. Even if only used for single disk raid0 sets.