Managing HP Serviceguard for Linux, Eighth Edition, March 2008

Cluster and Package Maintenance
Configuring a Legacy Package
Chapter 7 287
Configuring monitored_subnet_access
In order to monitor subnet 15.244.65.0 or 15.244.56.0, you would
configure monitored_subnet and monitored_subnet_access in pkg1’s
package configuration file as follows:
monitored_subnet 15.244.65.0
monitored_subnet_access PARTIAL
monitored_subnet 15.244.56.0
monitored_subnet_access PARTIAL
NOTE Configuring monitored_subnet_access as FULL (or not configuring
monitored_subnet_access) for either of these subnets will cause the
package configuration to fail, because neither subnet is available on all
the nodes.
Creating Subnet-Specific Package Control Scripts
Now you need to create control scripts to run the package on the four
nodes.
IMPORTANT In a cross-subnet configuration, you cannot share a single package
control script among nodes on different subnets if you are using
relocatable IP addresses. In this case you will need to create a separate
control script to be used by the nodes on each subnet.
In our example, you would create two copies of pkg1’s package control
script, add entries to customize it for subnet 15.244.65.0 or
15.244.56.0, and copy one of the resulting scripts to each node, as
follows.
Control-script entries for nodeA and nodeB
IP[0] = 15.244.65.82
SUBNET[0] 15.244.65.0
IP[1] = 15.244.65.83
SUBNET[1] 15.244.65.0