Managing Serviceguard A.11.20, March 2013

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
Control-script entries for nodeC and nodeD
IP[0] = 15.244.56.100
SUBNET[0] = 15.244.56.0
IP[1] = 15.244.56.101
SUBNET[1] = 15.244.56.0
Reconfiguring a Package
You reconfigure a package in much the same way as you originally configured it; for modular
packages, see Chapter 6: “Configuring Packages and Their Services ” (page 232); for legacy
packages, see “Configuring a Legacy Package” (page 307).
The cluster, and the package itself, can be either halted or running during package reconfiguration;
see “Reconfiguring a Package on a Running Cluster ” (page 316). The types of changes that can
be made and the times when they take effect depend on whether the package is running or not;
see “Allowable Package States During Reconfiguration ” (page 319). For information on changes
Reconfiguring a Package 315