| View status | cmviewcl -v |
| Stop a package | cmhaltpkg 'pkg_name' |
| Start a package | cmmodpkg -e 'pkg_name' |
| cmrunpkg -n 'node_name' 'pkg_name' | |
| Stop a node (make it leave the cluster) | cmhaltnode |
| Stop a node (and all packages) | cmhaltnode -f |
| Start a node (make it join the cluster) | cmrunnode |
| Stop a cluster | cmhaltcl |
| Stop a cluster (and all packages | cmhaltcl -f |
| Start a cluster | cmruncl |
| Query configuration | cmquerycl -v -C 'config_file' -n 'node_1' -n 'node_2' |
| Config file syntax check | cmcheckconf -v -C 'config_file' |
| Apply configuration | cmapplyconf -v -C 'config_file' |
Note: you'll need this procedure when installing apps on a cluster. Also it is essentially doing the same thing that SVG does when failing disks over from node to node. So it is good information to have from that perspective.
On first node: (assumes disk has already been setup: fdisk, LVM, mkfs, etc)
vgimport {VG_Name}
vgchange -ae {VG_Name} (the 'e' is for exclusive)
mount {VG_Name} {mount_point}
To move disk to second node: On node one: shutdown application (to remove locks from mountpoint)
umount -l {mount_point}
vgchange -an {VG_Name}
vgexport {VG_Name}
On node two:
sfdisk -R {dev_name} (this step is required only for the first time mounting on a new node)
vgimport {VG_Name}
vgchange -ae {VG_Name} (the 'e' is for exclusive)
mount {VG_Name} {mount_point}