【正文】 et them, * * consult the MC/ServiceGuard ServiceGuard Extension for RAC manuals. ********************************************************************** Enter a name for this package. This name will be used to identify the package when viewing or manipulating it. It must be different from the other configured package names. PACKAGE_NAME pkg_db Enter the package type for this package. PACKAGE_TYPE indicates whether this package is to run as a FAILOVER or SYSTEM_MULTI_NODE package. FAILOVER package runs on one node at a time and if a failure occurs it can switch to an alternate node. SYSTEM_MULTI_NODE package runs on multiple nodes at the same time. It can not be started and halted on individual nodes. Both NODE_FAIL_FAST_ENABLED and AUTO_RUN must be set to YES for this type of package. All SERVICES must have SERVICE_FAIL_FAST_ENABLED set to YES. NOTE: Packages which have a PACKAGE_TYPE of SYSTEM_MULTI_NODE are not failover packages and should only be used for applications provided by HewlettPackard. Since SYSTEM_MULTI_NODE packages run on multiple nodes at one time, following parameters are ignored: FAILOVER_POLICY FAILBACK_POLICY Since an IP address can not be assigned to more than node at a time, relocatable IP addresses can not be assigned in the package control script for multiple node packages. If volume groups are assigned to multiple node packages they must activated in a shared mode and data integrity is left to the application. Shared access requires a shared volume manager. Examples : PACKAGE_TYPE FAILOVER (default) PACKAGE_TYPE SYSTEM_MULTI_NODE PACKAGE_TYPE FAILOVER Enter the failover policy for this package. This policy will be used to select an adoptive node whenever the package needs to be started. The default policy unless otherwise specified is CONFIGURED_NODE. This policy will select nodes in priority order from the list of NODE_NAME entries specified below. The alternative policy is MIN_PACKAGE_NODE. This policy will select the node, from the list of NODE_NAME entries below, which is running the least number of packages at the time this package needs to start. FAILOVER_POLICY CONFIGURED_NODE Enter the failback policy for this package. This policy will be used to determine what action to take when a package is not running on its primary node and its primary node is capable of running the package. The default policy unless otherwise specified is MANUAL. The MANUAL policy means no attempt will be made to move the package back to its primary node when it is running on an adoptive node. The alternative policy is AUTOMATIC. This policy will attempt to move the package back to its primary node whenever the primary node is capable of running the package. FAILBACK_POLICY MANUAL Enter the names of the nodes configured for this package. Repeat this line as necessary for additional adoptive nodes. NOTE: The order is relevant. Put the second Adoptive Node after the first one. Example : NODE_NAME original_node NODE_NAME adoptive_node If all nodes in the cluster are to be specified and order is not important, NODE_NAME * may be specified. Example : NODE_NAME * NODE_NAME chnyt08 NODE_NAME chnap07 Enter the value for AUTO_RUN. Possible values are YES and NO. The default for AUTO_RUN is YES. When the cluster is started the package will be automatically started. In the event of a failure the package will be started on an adoptive node. Adjust as necessary. AUTO_RUN replaces obsolete PKG_SWITCHING_ENABLED. AUTO_RUN YES Enter the value for LOCAL_LAN_FAILOVER_ALLOWED. Possible values are YES and NO. The default for LOCAL_LAN_FAILOVER_ALLOWED is YES. In the event of a failure, this permits the cluster software to switch LANs locally (transfer to a standby LAN card). Adjust as necessary. LOCAL_LAN_FAILOVER_ALLOWED replaces obsolete NET_SWITCHING_ENABLED. LOCAL_LAN_FAILOVER_ALLOWED YES Enter the value for NODE_FAIL_FAST_ENABLED. Possible values are YES and NO. The default for NODE_FAIL_FAST_ENABLED is NO. If set to YES, in the event of a failure, the cluster software will halt the node on which the package is running. All SYSTEM_MULTI_NODE packages must have NODE_FAIL_FAST_ENABLED set to YES. Adjust as necessary. NODE_FAIL_FAST_ENABLED NO Enter the plete path for the run and halt scripts. In most cases the run script and halt script specified here will be the same script, the package control script generated by the cmmakepkg mand. This control script handles the run(ning) and halt(ing) of the package. Enter the timeout, specified in seconds, for the run and halt scripts. If the script has not pleted by the specified timeout value, it will be terminated. The default for each script timeout is NO_TIMEOUT. Adjust the timeouts as necessary to permit full execution of each script. Note: The HALT_SCRIPT_TIMEOUT should be greater than the sum of all SERVICE_HALT_TIMEOUT values specified for all services. RUN_SCRIPT /etc/cmcluster/pkg_bcvdbs/ RUN_SCRIPT_TIMEOUT NO_TIMEOUT HALT_SCRIPT /etc/cmcluster/pkg_bcvdbs/ HALT_SCRIPT_TIMEOUT NO_TIMEOUT Enter the names of the storage groups configured for this package. Repeat this line as necessary for additional storage groups. Storage groups are only used with CVM d