HP Serviceguard manual Locallanfailoverallowed

Table 15 Types of Changes to Packages (continued)

Change to the Package

Add or remove monitoring for a subnet: monitored_subnet for a modular package or SUBNET (in the package configuration file) for a legacy package

Change

local_lan_failover_allowed

Add or remove a resource: modular package

Change

resource_polling_interval, resource_start, resource_up_value: modular package

Add or remove a resource: legacy package

Change

RESOURCE_POLLING_INTERVAL RESOURCE_UP_VALUE: legacy package

Change RESOURCE_START: legacy package

Add a volume group: modular package

Add a volume group: legacy package

Remove a volume group: modular package

Required Package State

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.

Package can be running.

Serviceguard will not allow the change if it would cause the package to fail.

Package can be running.

Serviceguard will not allow the change if it would cause the package to fail. In addition, Serviceguard will reject the change if the resource is not UP within about 30 seconds. Multiple changes that take longer than this should be done incrementally; resources that are very slow to come up may need to be configured offline.

Serviceguard treats a change to resource_name as deleting the existing resource and adding a new one, meaning that the existing resource is stopped.

Package can be running.

Serviceguard will not allow a change to resource_up_value if it would cause the package to fail.

For AUTOMATIC resources, package can be running. See the entry for “Add or remove a resource: modular package” for more information.

For DEFERRED resources, package must not be running.

For AUTOMATIC resources, package can be running.

For DEFERRED resources, package must not be running.

Serviceguard will not allow a change to RESOURCE_UP_VALUE if it would cause the package to fail.

Package must not be running.

Package can be running.

(Remember that a volume group must already be configured into the cluster, via the VOLUME_GROUP parameter, before you can configure it into to a package.)

Package must not be running.

Package should not be running.

CAUTION: Removing a volume group may cause problems if file systems, applications or other resources are using it. In particular, if the volume group cannot be deactivated and kill_processes_accessing_raw_devices is set to yes, processes accessing the volume group as a raw device will be killed; in addition the CAUTION under “Remove a file system: modular package” applies to any file systems using the volume group.

Remove a volume group: legacy package

Change a file system: modular package

Package must not be running.

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.

316 Cluster and Package Maintenance