How to migrate HP-UX workloads between physical and virtual servers easily

16
Click on the Add Volume button; specify a Size (i.e., 31 GB) and the RAID level (i.e., RAID 5). Then, provide a
Storage Port WWN identifying the SAN controller that will provide storage capacity for this SPE. To keep this
example simple, we will supply only one SAN controller WWN.
In the LUN field, provide the LUN identifier that will be used by the SAN controller during the logical server activation.
Use the 16 hexadecimal digits Volume Set Addressing (VSA) format for this field. In this format, LUN Identifier 1 becomes
4001000000000000 and LUN Identifier 23 is represented by 4017000000000000.
Note: VSA is an HP proprietary format removing certain SCSI limitations when accessing devices over Fiber Channel. This format is used extensively
by the EFI.
In the Manage Server WWNs table, tick the Ready boxes corresponding to the WWNs provided by the Globally
Unique Identifier (GUID) Manager embedded in VCEM and corresponding to the 2 ports requested earlier (ATC_RACK
and ATC_RACK0). Those server WWNs will be assigned to the physical or virtual HBAs during logical server migration.
Figure 14 highlights the LUN identifier in VSA format and the ready boxes ticked. Save this configuration and hit
the Done button.
Figure 14. Creating a storage pool entry within an unlike portability group
SAN connectivity with unlike portability group storage pools
The deployment of an operating environment on logical servers activated in this unlike portability group will be
successful if an effective SAN connectivity exists between the disk arrays and the logical severs’ HBAs. With the help of
administrators from the storage department, adapt the zoning in the different SAN switches according to the WWNs
provided by the Storage Pool Entry, in the Manage Server WWNs table.
Verify that the information provided in the SPE match a host and a LUN in the ad hoc SAN controller.