HP Matrix Operating Environment 7.3 Update 1 Release Notes

Suggested action
At the Integrity Virtual Machine EFI prompt, execute the following commands to see
LUN mappings. When these steps are complete, the user can select the required LUN
from the displayed device list to boot up or to install the operating system.
1. Check configurable controllers using the drvcfg command.
Shell> drvcfg
Configurable Components
Drv[2C] Ctrl[29] Lang[eng]
2. Enumerate all SCSI and FC LUNs using drvcfg -s <drvnum> <ctrlnum>.
(drvnum and ctrlnum are displayed as part of step 1.) Press Y for confirmation
on enumerating both SCSI and FC LUNs.
Shell> drvcfg -s 2C 29
Set Configuration Options
Drv[2C] Ctrl[29] Lang[eng]
HP AVIO Stor Driver Configuration
==================================
Warning: Enumerating all SCSI or FC LUNs increases initialization times.
Enumerate all SCSI LUNs (Y/N)? [current setting: Y]: Y
Enumerate all FC LUNs (Y/N)? [current setting: Y]: Y
Drv[2C] Ctrl[29] Lang[eng] - Options set. Action Required is None
3. Reconnect drivers, refresh mapped drives and display available boot options using
commands reconnect -r and map -r.
Shell> reconnect -r
ReconnectController(0,0,0) : Status = Success
Shell> map -r
Device mapping table
blk0 :
Acpi(PNP0A03,0)/Pci(1|0)/Fibre(WWN50001FE1501A1F39,Lun4068000000000000)
blk1 :
Acpi(PNP0A03,0)/Pci(1|0)/Fibre(WWN50001FE1501A1F3D,Lun4068000000000000)
Applications that depend on IO hardware paths or legacy storage DSFs are not supported
with Integrity cross-technology logical servers
HP-UX applications that have a dependency on I/O hardware paths or Legacy Storage
Device Special Files (DSFs) might fail if these applications are running on Integrity
cross-technology logical servers. This occurs because I/O hardware paths and Legacy
Storage DSFs may change during cross-technology move operations. After a
cross-technology logical server move operation, Networking I/O Instance Numbers
and Storage Agile DSFs will not cause application failure.
Major issues
Provisioning storage using SPM and automated zoning
Provisioning storage using SPM and automated zoning can fail because the principal
switch in the fabric used for this storage is offline.
Suggested action
Resynchronize the fabric in the SPM GUI, and then deactivate and reactivate the service
involved.
Provisioning storage after migrating from one CMS to another
SPM does not provision storage after migrating from one Central Management Server
to another because using the Data Migration Tool (DMT) changes the local user
identifiers that are communicated to SPM.
42