Managing HP Serviceguard A.12.00.00 for Linux, June 2014

Table 12 Types of Changes to Packages (continued)
Required Package StateChange to the Package
Package can be running.
See “ip_subnet” (page 192) for important information. Serviceguard will reject
the change if you are trying to add an ip_subnet that is not configured on all
the nodes on the package's node_name list.
Add or remove an ip_subnet:
Package can be running.
See “ip_subnet” (page 192) and “ip_address” (page 193) for important
information. Serviceguard will reject the change if you are trying to add an
ip_address that cannot be configured on the specified ip_subnet, or is on
a subnet that is not configured on all the nodes on the package's node_name
list.
Add or remove an ip_address:
Package can be running.
Serviceguard will reject the change if you are trying to add a node on which the
specified ip_subnet is not configured.
Add or delete nodes from
package’s ip_subnet_node
list(page 192) in cross-subnet
configurations
Package can be running.
Serviceguard will not allow the change if the subnet being added is down, as
that would cause the running package to fail.
Add or remove monitoring for a
subnet: monitored_subnet for a
modular package
Package must not be running.
NOTE: pv (page 199) is for use by HP partners only.
Add, change, or delete a pv:
Package can be running.Add a volume group:
Package can be running.
CAUTION: Serviceguard ignores the change if the volume group is removed
and its associated logical volumes are in use by the same or different package
within the cluster.
Remove a volume group:
Package should not be running (unless you are only changing fs_umount_opt).
Changing file-system options other than fs_umount_opt may cause problems
because the file system must be unmounted (using the existing fs_umount_opt)
and remounted with the new options; the CAUTION under “Remove a file system:
modular package” applies in this case as well.
If only fs_umount_opt is being changed, the file system will not be unmounted;
the new option will take effect when the package is halted or the file system is
unmounted for some other reason.
Change a file system:
Package can be running.
During the package reconfiguration, if the fsck command on a file system fails,
the package does not start.
CAUTION: To avoid this issue, run the fsck command on the file system outside
the package, and then add the file system to the modular package.
Add a file system:
Package can be running.
CAUTION: Removing a file system may cause problems if the file system cannot
be unmounted because it's in use by a running process. In this case Serviceguard
kills the process; and keeps the package running with errors. For more information,
see “Handling Failures During Online Package Reconfiguration” (page 251).
Remove a file system:
Package can be running.
These changes in themselves will not cause any file system to be unmounted.
Change
concurrent_fsck_operations,
, fs_mount_retry_count,
fs_umount_retry_count:
248 Cluster and Package Maintenance