clmgr command: Quick reference
Use the following information to quickly find the most common syntax and examples for the PowerHA® SystemMirror® clmgr command.
Basic usage
Command usage | Command syntax |
---|---|
Basic command format | clmgr <ACTION> <CLASS> [<OBJECT>] [COMMAND-SPECIFIC
INPUTS] |
Flexible output from data retrieval commands |
|
Intention Recognition: Aliases |
Note: You can display available aliases by running the
clmgr <ACTION> <CLASS>
-h command. |
Intention Recognition: Case sensitivity | The case sensitivity is ignored for all actions, classes, and input labels. For example,
the following command syntax is
valid:
Note: The
case sensitivity does not apply to labels used within the PowerHA SystemMirror product. For example, you can
create a node that is labeled MyNode.
|
Intention Recognition: Abbreviations | You can enter enough letters to be unambiguous when you are typing syntax. The following
examples have the exact syntax first, and then followed by the abbreviated syntax. Both of the
following commands provide the same results.
clmgr add tape
SHARED_TAPE_RESOURCE=/dev/rmt0 == clmgr add tape SH=/dev/rmt0 Note: Abbreviations are
intended for ease-of-use while you are typing from the command line. Do not use abbreviations in
scripts. Abbreviations might change over time, and are not documented.
|
Log file | /var/hacmp/log/clutils.log |
Defining basic topology
Command usage | Command syntax |
---|---|
Define a cluster with no sites |
|
Define a stretched cluster Note: Sites are defined, but only one repository disk is required
for a stretched cluster because the repository disk is shared by all sites.
|
|
Define a linked cluster Note: Sites are defined and each site has its own repository
disk.
|
|
Create the newly defined objects on all the defined nodes | clmgr sync cluster The alias for a Note: You must verify and synchronize the cluster after any configuration
changes to replicate the change to other nodes in the cluster.
|
Defining resource groups
Command usage | Command syntax |
---|---|
Define a resource group |
The alias for a Note: A resource group is a set of cluster resources that you configure and manage as a single unit.
|
Modify a resource group |
The alias for a |
Defining application resources
Command usage | Command syntax |
---|---|
Define an application controller Note: You can use this command to automatically start and
stop an application.
|
The aliases for an Note: You must specify the scripts for an application. The scripts must exist on every node the
application might run on.
|
Define an application monitor: Process-based |
The aliases for an You can use the ps -e command to determine the correct process names to use an application. Do not use the ps -ef command. For example, you can use the ps -e | awk '{print $4}' | sort –u command. Note: This type of monitoring detects the termination of one or more application processes.
|
Define an application monitor: Custom |
The aliases for an Note: This type of monitoring checks the health of an application by running the specified monitor
method file at configurable intervals and checking the monitors exit code. The monitor method file
must exist on every node the application might run on.
|
Creating LVM resources
Command usage | Command syntax |
---|---|
Create a volume group |
The alias for a |
Create a logical volume |
The alias for a |
Create a file system: Create logical volume |
The alias for a Note: You must specify the size of the file system to create this type of a file system.
|
Create a file system: Use logical volume |
The alias for a Note: You must specify the size of the specific logical volume to create this style of a file
system.
|
Create a mirror pool: All disks |
The aliases for a |
Create a mirror pool: Specified disks |
The aliases for a |
Managing volume groups
Command usage | Command syntax |
---|---|
Volume Group: Add a physical volume |
The alias for a |
Volume Group: Add a mirror pool |
The alias for a |
Volume Group: Remove a physical volume |
The alias for a |
Managing resource groups
Command usage | Command syntax |
---|---|
Move a resource group: New node |
The alias for a Note: All resources that are managed by the resource group are brought offline on the
current node, and brought online on the specified new node.
|
Move a resource group: New site |
The alias for a Note: All resources that are managed by the resource group are brought offline on the
current node, and brought online on the specified new node.
|
Start a resource group |
The alias for a Note: All resources that are managed by the resource group are brought offline on the current
node, and brought online on a node within the specified site. If you do not specify the
To bring the resource group simultaneously in ONLINE and ONLINE SECONDARY state in a
multi-site cluster environment, you must specify following additional
attributes:node input, the resource group is brought online on a default node for the current
policy.
To bring the resource group in
ONLINE SECONDARY state on a node, run the following
command:
|
Stop a resource group |
Note: Resources that are managed by the resource group
are brought offline on the current node.
To bring the resource group simultaneously on both
sites from ONLINE and ONLINE SECONDARY state to OFFLINE state, you must specify following additional
attributes:
To bring down the resource group
from ONLINE SECONDARY to OFFLINE state on a node, run the following
command:
|
Suspend application monitoring |
Note: This command suspends application monitoring for the specified application. You can specify
ALL instead of an application controller to suspend all
application monitoring. |
Resume application monitoring |
Note: This command resumes application monitoring for the specified application. You can specify
ALL instead of an application controller to suspend all
application monitoring. |
Move service IP |
Note: The
<NEW_INTERFACE> variable refers to a logical interface. For
example, en3 . |
Cluster services
Command usage | Command syntax |
---|---|
Start cluster services: Entire cluster |
Note: All resources that are managed by the cluster are brought online unless the Manage
Resouce Group option in SMIT is set to Manually.
|
Start cluster services: Site |
Note: All resources that are managed by the nodes within the site are brought online, unless the
current policy setting forbids it or in the SMIT interface the field is set to Manually.
|
Start cluster services: Node |
Note: All resources that are managed by the node are brought online, unless current policy setting
forbids it or in the SMIT interface the field is set to Manually.
|
Stop cluster services: Entire cluster |
Note: All resources that are managed by the cluster are brought offline. If you want to suspend
cluster services without bringing applications and other resources offline, you must set the
manage option to unmanage . |
Stop cluster services: Site |
Note: All resources that are managed by the nodes within the site are brought offline, unless the
manage option is set to unmanage or move . |
Stop cluster services: Node |
Note: All resources that are managed by the node are brought offline, unless the
manage option is set to unmanage or move . |