HP BL860c HP Integrity Virtual Machines Release Notes - Page 40
Do not Use Integrity VM Commands to Manage Distributed Guests
View all HP BL860c manuals
Add to My Manuals
Save this manual to your list of manuals |
Page 40 highlights
6.11.1 Required HP Serviceguard Patches To use Serviceguard to manage HP-UX guests, make sure the required patches are installed. For more information, see Section 2.1.6 (page 18). 6.11.2 Reenter Command to Start Packages The procedure for configuring and starting guest packages includes the cmrunpkg command. This command does not always work the first time you enter it. If the command does not start the package, re-enter the command. 6.11.3 Do not Use Integrity VM Commands to Manage Distributed Guests Guests configured as Serviceguard packages should only be stopped and started using Serviceguard package control commands. Do not use the Integrity VM commands (hpvmstart, hpvmstop, and hpvmconsole) to start and stop these types of guests. For more information about using Serviceguard to manage virtual machines, see the Integrity Virtual Machines Installation, Configuration, and Administration manual. 6.11.4 Different Cluster Nodes Report Virtual Machine Status Differently Integrity VM commands can receive different warnings and errors from guests running on different Serviceguard nodes. For example, the Serviceguard node that is starting a guest as part of a package knows that the guest is running before any other nodes know. (The delay is usually less than 10 seconds.) Commands that are run on different servers report different errors or warnings depending on whether the guest is running or not. 6.11.5 Syslog Entries for cmcld Can Be Ignored With Serviceguard and Integrity VM running, you may see the following types of message in the syslog file: Syslog entries - cmcld[XXXX]: Warning: cmcld process was unable to run for the last X.XX seconds These messages can be ignored. 6.11.6 Using Virtual Machines Manager (VM Manager) to Manage Distributed Guests The following situations might occur when you are using VSE to manage distributed guests (guests that are configured as Serviceguard packages): • There is a guest configuration file for each guest on each VM Host. Therefore, when you modify a distributed guest you must modify the guest on each VM Host that is a cluster node. • Do not start and stop distributed guests using VM Manager menu items. Use Serviceguard commands to start and stop distributed virtual machines. For more information, see the HP Integrity Virtual Machines Installation, Configuration, and Administration manual. • The VM Hosts field on the VM Properties page sometimes shows an incorrect list of hosts in the cluster. If VM Manager is running on the VM Host that is actively managing the virtual machine that is being viewed, the list is correct. In all other cases, the list is incorrect. 6.11.7 Polling Interval for Virtual Machine Serviceguard Nodes Serviceguard failover in Integrity VM can take longer than expected with the default 5-second network polling interval. To reduce the failover time, reduce the value of the HPVMNETINTVL tunable to 2. If your system has Serviceguard installed and you want to make sure that failover of their vswitches used for Serviceguard fail over in less than 5 seconds, use a text editor to add or change the following line in the /etc/rc.config.d/hpvmconf file: 40 Guest Administration