Policy_Parameters:
POLICY_NAME CONFIGURED_VALUE
Failover min_package_node
Failback automatic
Script_Parameters: |
|
| |
ITEM | STATUS | NODE_NAME | NAME |
Resource | up | manx | /resource/random |
Subnet | up | manx | 192.8.15.0 |
Resource | up | burmese | /resource/random |
Subnet | up | burmese | 192.8.15.0 |
Resource | up | tabby | /resource/random |
Subnet | up | tabby | 192.8.15.0 |
Resource | up | persian | /resource/random |
Subnet | up | persian | 192.8.15.0 |
Node_Switching_Parameters: |
|
| |
NODE_TYPE | STATUS | SWITCHING | NAME |
Primary | up | enabled | manx |
Alternate | up | enabled | burmese |
Alternate | up | enabled | tabby |
Alternate | up | enabled | persian |
Checking the Cluster Configuration and Components
Serviceguard provides tools that allow you to check the soundness of the cluster configuration, and the health of its components. In past releases, much of this was done by cmcheckconf (1m) and/or cmapplyconf (1m) and could be done only when you were changing the configuration of the cluster or packages.
As of Serviceguard A.11.20, these commands perform additional checks, and a new command, cmcompare (1m) allows you to compare the contents and characteristics of
Specifically, the following capabilities are new as of Serviceguard A.11.20.
122 Maintenance