HP Serviceguard A.11.20- Managing Serviceguard Twentieth Edition, August 2011

Table 15 Types of Changes to Packages (continued)
Required Package StateChange to the Package
Package can be running.Add or remove monitoring for a
subnet: monitored_subnet for a
Serviceguard will not allow the change if the subnet being added is down, as
that would cause the running package to fail.
modular package or SUBNET (in
the package configuration file) for
a legacy package
Package can be running.Change
local_lan_failover_allowed
Serviceguard will not allow the change if it would cause the package to fail.
Package can be running.Add or remove a resource: modular
package
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.Change
resource_polling_interval,
Serviceguard will not allow a change to resource_up_value if it would cause
the package to fail.
resource_start,
resource_up_value: modular
package
For AUTOMATIC resources, package can be running. See the entry for “Add or
remove a resource: modular package” for more information.
Add or remove a resource: legacy
package
For DEFERRED resources, package must not be running.
For AUTOMATIC resources, package can be running.Change
RESOURCE_POLLING_INTERVAL
For DEFERRED resources, package must not be running.
RESOURCE_UP_VALUE: legacy
package
Serviceguard will not allow a change to RESOURCE_UP_VALUE if it would cause
the package to fail.
Package must not be running.Change RESOURCE_START: legacy
package
Package can be running.Add a volume group: modular
package
(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.Add a volume group: legacy
package
Package should not be running.Remove a volume group: modular
package
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.
Package must not be running.Remove a volume group: legacy
package
Package should not be running (unless you are only changing fs_umount_opt).Change a file system: modular
package
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