HP Matrix Operating Environment 7.3 Update 1 Release Notes

In the above example, for non-redundant storage, Matrix tries FabricA, FabricB, FabricC
and FabricD in that order. For redundant storage, Matrix tries the FabricC & FabricD
pairing.
NOTE: The fabrics listed in this property are used by all auto-generated storage pool
entries from Matrix infrastructure orchestration on that CMS. It cannot be set up to only
be used by some users or some organizations. If storage is not found after going through
the fabrics defined in this list, then all known fabrics are tried.
Define prefix used for host names on the storage array when provisioning
storage
When provisioning storage through Matrix IO or Matrix OE, using SPM, a prefix can
be defined for the host names that are created on the storage array. This can be defined
by adding or modifying the property SPM_HOSTNAME_PREFIX within the
lsa.properties file. This prefix can be 5 characters or less due to host name
limitations on the storage arrays. If not selected, the default prefix used is “LSM”. The
rest of the host name will be the initiator WWN defined within the host definition in
order to guarantee name uniqueness.
Deployment of HPUX 11iv3 1203 or HPUX 11iv3 1209 on any Integrity i2
or i4 server blade using Matrix infrastructure orchestration with Ignite-UX
may fail
When deploying HP-UX 11iv3 1203 or HP-UX 11iv3 1209 on a BL860c i2, BL870c
i2, BL860c i4, BL 870c i4, or BL890c i4 server blade using Matrix infrastructure
orchestration with Ignite-UX, the Create Service Request may fail and the server will not
be provisioned. The step in the request that deploys the HP-UX OS fails and the following
error displays:
Major,"Failed while deploying operating system for <your service
name>. Cause: Logical server job (ID = <your logical server
ID>) completed with a failure status. Failure: Deployment server
does not have a record of the target system(s)..”
Suggested action
1. Erase the disk used by the target server for deployment.
a. Make sure all hosts are in the same zone then perform a LUN clean-up: Log
in to the storage management server (HP P6000 Command View Software
or HP 3PAR StoreServ Management Console, etc.)
b. Unpresent the host associated with the vdisks and delete the vdisks.
c. Create the new vdisks with the required size and RAID level and present the
vdisks to the respective hosts.
2. Deactivate the logical server associated with the target server.
a. From the HP Matrix Operating Environment menu, click Tools→HP Matrix OE
Visualization.
b. Select Logical Server from the Perspective drop-down menu.
c. Select the logical server and click Tools→Logical Servers→Deactivate....
d. Monitor the status of the task by selecting Report→Logical Server Job Status.
e. Wait for the task to complete successfully before continuing to the next step.
3. Delete the logical server. Select the appropriate deactivated logical server and
click Delete→Delete Logical Server...
4. Move the target server from the IO maintenance pool to the desired server pool.
19