Reference Guide

Version 1.0.1 19
9 Use Cases
9.1 SCSI HBA
HPSCSI_HBAComputerSystem:01
HP_ComputerSystem:88
HP Base Server
SystemComponent
HPSCSI_HBAPortController:01
CentralClass
LogicalIdentity
HPSCSI_HBAPhysicalPackage:01
Realizes
HPSCSI_HBAProduct:01
Name = “Ultra320 SCSI HBA”
ProductPhysicalComponent
HPSCSI_DAPort:01
HostedAccessPoint
HPSCSI_DASCSIProtocolEndpoint:01
HPSCSI_SCSIProtocolController:01
SystemDevice
HPSCSI_StorageVolume:002
OSName = “Disk 0”
SAPAvailableForElement
ProtocolControllerForUnit
SystemDevice
HPSCSI_Location:01
ElemInfoTagDesc = PCISlot
ElemInfoTag = “3”
HPSCSI_DiskDrive:005
SystemDevice
HPSCSI_StorageExtent:005
LogicalIdentity
MediaPresent
PhysicalElementLocation
ElementConformsToProfile
DeviceSAPImplementation
RegisteredProfile
RegisteredOrg = “Other”
OtherRegOrg = “HP WBEM TC”
RegisteredName = “HP SCSI HBA”
HPSCSI_HBASPIPort:01
HPSCSI_SCSIProtocolEndpoint:01
SAPAvailableForElement
DeviceSAPImplementation
Figure 7 – HP SCSI HBA profile: SCSI HBA
The example in Figure 7 shows a PCI based SCSI HBA in slot 3. The HPSCSI_HBAPortController central
class instance can be identified by following the CIM_ElementConformsToProfile association from
HP_RegisteredProfile instance in root\Interop namespace. This instance of RegisteredProfile is identified
as HP WBEM TC: HP SCSI HBA.
The ComputerSystem instance (used to scope devices managed by the array) is identified by following
CIM_LogicalIdentity association to HPSCSI_HBAComputerSystem class.
This example shows a single disk configuration. All disk drives can be found using the SystemDevice
association from the HPSCSI_HBAComputerSystem instance.
The marketing name for the controller can be found by first traversing the SystemPackaging association
from the HPSCSI_HBAComputerSystem instance to the PhysicalPackage that represents the HBA, then