Operating Environment Software User Manual

Suggested action 3
Modify the unusable WWNs, entering in new values in their place.
HP recommends that you do not use Unmanage Logical Server to unmanage a logical server that
has been previously activated. Unmanaging the logical server may result in an inconsistent state,
and may render the storage pool entries unusable. An exception to this recommendation is if you
plan to manage the profile using VCEM.
Storage pool entry status is “Presentation Completed with Errors –
Inoperable” or “Presentation Completed – Inoperable”
After creating a storage pool entry from an array imported into SPM, the status of the storage pool
entry on the Matrix OE visualization Storage Pool screen is “Presntation completed with Errors
Inoperable” or “Presentation Completed Inoperable”.
A possible cause can be when the array is imported into SPM, a security group other than the
Matrix Security Group is selected on the Array Properties screen
Suggested action
the storage administrator or an administrator with permissions to use SPM should perform the
following steps:
1. Start SPM by pointing a browser to https://localhost:8000 where “localhost” is the name of
the CMS.
2. Right click on an array and select Change Security Group.
3. Select the Matrix Security Group.
4. In Matrix OE, refresh storage pool entries on the Tools→Logical Servers→Refresh or
Modify→Logical Server Storage Pools screen.
The status of the inoperable storage pool entry will change to “Presentation Completed –
Available”.
Logical servers are inoperable if they are associated with guests that use
SLVM file-based storage
HP Integrity guests can use SLVM storage, referred to as file-based storage in Matrix OE logical
server management. These volumes are created in HP-UX LVM volume groups. By default, the
volume groups are not online when the HP-UX host starts up. This results in existing guests being
unable to access their storage, further causing any associated logical servers to become inoperable
Suggested action
Create a multi-node Serviceguard package for each of the SLVM volume groups to activate volume
groups after a host reboot. This will enable the SLVM volume groups to be started when Serviceguard
starts during HP Integrity VM host start up.
Follow the first two steps in section 10.5.2 (Creating and Configuring VMs as Serviceguard
Packages Having SLVM Backing Storage) in HP Integrity Virtual Machines 4.3: Installation,
Configuration, and Administration, available from www.hp.com/go/hpux-hpvm-docs..
To enable Serviceguard to start automatically during an HP Integrity VM host boot, set
AUTOSTART_CMCLD to 1 in /etc/rc.config.d/cmcluster.
Unmanaging a logical server leaves WWNs used by VC profile unavailable
After a logical server is unmanaged, any WWNs still being used by the underlying Virtual Connect
profile will become unavailable. This may make the storage pool entry unavailable.
Suggested actions
• If you want to reuse the storage pool entry but do not need to keep the original WWNs,
modify the storage pool entry to increase the Maximum Number of Sharers by 1. This assigns
86 Troubleshooting