Manualshelf

HP Integrity Virtual Machines Installation, Configuration, and Administration Version A.03.50

ManualsBrandsHP ManualsSoftwareHP-UX 11i v3 Integrity Virtual Machines Host Per Core License LTU
161162163164165166167168169170
STANDBY up 0/2/1/0/4/0 lan2
STANDBY up 0/2/1/0/6/0 lan8
STANDBY up LinkAgg0 lan900
STANDBY up 0/0/3/0 lan0
PACKAGE STATUS STATE AUTO_RUN NODE
compass1 up running disabled host1
Policy_Parameters:
POLICY_NAME CONFIGURED_VALUE
Failover configured_node
Failback manual
Script_Parameters:
ITEM STATUS MAX_RESTARTS RESTARTS NAME
Service up 0 0 host1
Node_Switching_Parameters:
NODE_TYPE STATUS SWITCHING NAME
Primary up enabled host1 (current)
Alternate up enabled host2
NODE STATUS STATE
host 2 up running
Network_Parameters:
INTERFACE STATUS PATH NAME
PRIMARY up 0/2/1/0/4/1 lan7
STANDBY up 0/1/2/0 lan1
STANDBY up 0/2/1/0/4/0 lan2
STANDBY up 0/2/1/0/6/0 lan8
STANDBY up LinkAgg0 lan900
PRIMARY up 0/5/1/0/7/0 lan6
PRIMARY up 0/2/1/0/6/1 lan9
STANDBY up 0/0/3/0 lan0
If desired, enter the cmmodpkg command to enable autorun and failover.
11.3.5 Starting the Vswitch Monitor
The vswitch monitor is responsible for monitoring the activities of the Serviceguard network
monitor and for moving the vswitch configuration, when appropriate, between primary and
standby network interfaces. The vswitch monitor requires no user configuration and is installed
as part of the Integrity VM product. If Serviceguard is running and any distributed guests are
configured, the vswitch monitor is automatically started on the VM Host system when the VM
Host system boots. To start the vswitch monitor manually, use the following command:
# /sbin/init.d/vswitchmon start
To verify that the vswitch monitor is running, enter the following command:
# ps -ef | grep vswitchmon
11.3.6 Verifying That Distributed Guests Can Fail Over
To verify that the guests configured as Serviceguard packages and the multiserver environment
are working properly, use the following commands to perform a manual failover:
1. On the original node (host1), verify that the package named compass1 is running:
host1# cmviewcl -v -p compass1
2. Halt the compass1 package on host1:
host1# cmhaltpkg compass1
Halting package compass1.
3. Start the package on the other VM Host system (host2):
162 Using HP Serviceguard with Integrity VM