HP Matrix Operating Environment Software - Manual (Page 195)

Logical servers are inoperable if they are associated with guests that use SLVM file-based storage
After starting an HP Integrity VM Host, logical servers are inoperable if they are associated with
guests that use SLVM file-based storage. Issue
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 Possible cause
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.
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. Action
To enable Serviceguard to start automatically during an HP Integrity VM Host boot, set
AUTOSTART_CMCLD to 1 in /etc/rc.config.d/cmcluster.
Could not find server serial number or task for logical server failed
Failure message • Could not find server with serial number <serial_number>.
• Task for logical server <logical_server_id> has failed. Logical server
job <job_id> completed with a failure status. Failure: Exception
creating connection to: 15.2.50.138; nested exception is:
java.net.NoRouteToHostException: No route to host: connect.
• Task for logical server <logical_server_id> has failed. Logical server
job <job_id> completed with a failure status. Failure: no such object
in table.
A server blade that was allocated has suffered hardware or firmware problems during the
provisioning process, for example, insufficient power alert or power outage. Possible cause
Action 1. Use Onboard Administrator to verify the status of the server blade.
2. Verify that the server blade has the latest firmware installed.
3. Perform a manual clean-up process for any affected logical servers. See
“Manual clean-up
process (physical)” (page 234) .
Manual storage provisioning email states that more data LUNs than are required should be added
Manual Storage Provisioning email states that more data LUNs than are required should be added. Issue
This email is sent when adding a new server to an existing service and one or more of the following
applies: Possible cause
• A server is added to a deployed server group using the Add Server feature.
• The servers in the selected group are connected to a shared data disk.
• A manual storage provisioning action is required for the data disk.
If you receive this email, add the LUN information to both the new server and the existing servers.
You only need to add the LUN information to the Matrix OE storage pool entry for the new server. Action
Cannot add servers to an existing service using a static IP address
Cannot add servers to an existing service using a static IP address. Issue
Static IP allocation limitation.
When a service contains multiple servers and the network is configured with static IP addresses,
additional servers cannot be added to the provisioned service, even though the infrastructure Possible cause
orchestration interface enables you to create the request without a warning. When this type of
request is processed, it fails.
Service creation 195