HP Matrix Operating Environment Automated Storage Provisioning: "Static"SAN volume automation via multi-initiator NPIV

Insight Orchestration – Storage Automation via NPIV
20
LogicalServer and ‘wwnr2’ is assigned to the yellow LogicalServer). Now, only the boot
disks are attached to the servers. The shared disk is left unattached.
6. HPIO powers the servers up and each server initiates the standard FC login sequence and is
granted access to ‘Lun1’ and ‘Lun2’ on the disk array respectively.
7. The servers continue to boot. When the servers find no OS on their boot disk, they fall
through to network boots which attaches each of the servers to the OS deployment server.
8. HPIO then instructs the OS deployment server to install the selected OS to each of the servers.
The OS install process is monitored to completion.
9. HPIO instructs the servers to power off.
This leads to the second phase of the server provisioning process which is outlined in the next figure.
Figure 14: Add shared data disk
After HPIO successfully deploys the OS to each of the servers, they are powered-off and HPIO begins
the process of “attaching” the servers to their data disk(s).
1. In this example, the LogicalServers have requested a single shared 20GB data disk. Since
data disk has been defined as a “shared data disk”, the same disk is intended to be visible to
both LogicalServers.
Array
Lun1 10GB
Lun2 10GB
Lun3 20GB
Lun4 20GB
Blade Enclosure
VC-FC
Blade
Fc-hba
Storage
Admin
wwnr1
wwnr4
wwnr5
wwnr6
Storage
Mgmt
HPIO, LSM
VCEM
HPIO, LSM
VCEM
wwnr2
wwnr3
wwnr1
wwnr4
wwnr1, Lun1, …
wwnr2, Lun2, …
wwnr3, Lun3, …
wwnr4, wwnr5, wwnr6, Lun4, …
Storage Pool
LogicalServerLogicalServer
10GB
20GB
LogicalServer
10GB
Blade
Fc-hba
wwnr2
wwnr5