kJ0i70i7by nameby nameBUILDd kHA./AA kd@E/H 0h/Pѿ (X@o ?(Ӯ3Irޙxı%Hid > }.3D jQ? 0 ``@`(h X#>3O\HAngY>oS +$(FވnhJ0`Fi n4A27r+q Ą±-RD @d9X>4G!0  + ,h 7BŋƔW ioLphbnhG+K i@8ȀYKGq XT xPd#EG, >)zB[p:>n Ax`P1Y B0@8SsDdzQ` 3Ot8m^q qۑXi.$ !ll,u7 (` 6$y͜8,(Ԡ`_E4o 0iBƂ~,XOiE@ƝqK%l}2 YKGq XT xPd#EG, >)zB[p:>n Ax`P1Y B0@8SsDdzQ` 3Ot8m^q qۑXi.$ !ll,u7 (` 6$y͜8,(Ԡ?$cF P,X'ui.[/4)/[.  i%@ F䂒W# 4cAE,XO ioLphbXzӇytjӮ3Jrަ4pI QJi:4-cH<H:uҚicN)z$"bIBSM5Li9oQ1qI QJi:4- AfAУMSuiN[A4E$G])4Ҝ)$ :M41\fTı\fH:uҚicN)x: A$c (XQ ,}:4-闎 MHiz-!qcN& @RA  ,g 0iBƂX` 7Ӯ3Irޙx\Vp"УMSuiN[ƴH:uҚicN)zAУMSuiN[pt=$G])4ҜI QJi:4-c[dCH:uҚicN)zAУMSuiN[Ƭx"AУMSuiN[Ƭx"AУMSuiN[ƬxI QJi:4-cXdI QJi:4-cYIBSM5Li9oS<ÒH:uҚicN)zܑI QJi:4-c[u6AУMSuiN[Ӫm$G])4Ҝ !Si$ :M41\fLmB2E$G])4ҜyytjӮ3Jrަ5kdIBSM5Li9oS.hIBSM5Li9oS>[$RH:uҚicN)zMt(4TƝqS1t(4TƝqS1"AУMSuiN[ƛHt(4TƝqS1"AУMSuiN[ِ"AУMSuiN[Ƒ =$G])4Ҝ:=$G])4Ҝt(4TƝqS1 jIBSM5Li9oSn8=$G])4ҜƤt(4TƝqS1pu$t(4TƝqS1Ǥt(4TƝqS1RH:uҚicN)zی I QJi:4-cV<{qtjӮ3Jrަ5cǾ$G])4ҜamƒH:uҚicN)ztjӮ3Jrަ5IBSM5Li9oScn4AУMSuiN[ƶH:uҚicN)z>RH:uҚicN)zH:uҚicN)zs>RH:uҚicN)z@$G])4Ҝ˥H:uҚicN)z-$G])4Ҝˢ!tjӮ3Jrާ.hIBSM5Li9o@_ 7a (XQ ,Q_7Ȑt1\f2@0X 3h _ Qc? (X@? ?(Ӯ3Irޙxı%Hi 2@:uҬԩz4pI >k/B(}\t^4k/B(}\t^4k/B(}\t^4k/B(}\t^4k/B(}\t^4k/B(}\t^4k/B(}\t^4r^cWwZx#/(LioLphbnhG+G2Xg;/H8!G]*]J*l|I >k/B(}\t^4k/B(}\t^4k/B(}\t^4v^$XaJf.N[ĕ1!$eEP8ܾϸˑƔR?'9xHPXB?]^Mi<01\f23Idg/$T ċ0f%QJR-bJA|_PQiE#y#4֞( .G/QHl!Aa5wyz5 2ƝqK&$z2Xg;/,hрġ :VbTL\ISے)$eEP8ܾϸˑƔR?'9xHPXB?]^Mi<01\f23Idg/H"?Ke@X!G]*]J*c[u6A|_PQiE#y#4֞( r^cWwZx#/(LioLphbnhG+G%%s cF7ġ :VbTL\IS.hIGAY}BGT7/2>r^cWwZx#/(LioLphbnhG+G$%s @bPt1u*rަ.$-)$eEP8ܾϸˑƔR?'9xHPXB?]^Mi<01\f23Idg/$ j?KeEO3(YS1q%Lkli$eEP8ܾϸˑƔR?'9xHPXB?]^Mi<01\f23Idg/$d āQ#!G]*]J*c[w4E$ êr?9xҊGg/ Giv^$i 1(BU9oSTӮhIGAY}BGT7/2>r^cWwZx#/(LioLphbnhG+Ga9x P`"!G]*]J*cl]I >k/B(}\t^4r^cWwZx#/(LioLphbnhG+GG`}IC@BuҬԩz4svAI >k/B(}\t^4k/B(}\t^4.G/QHl!Aa5wyz5 2ƝqK&$za% G`}HҀX!G]*]J*cXcq"n_ge@|J)͜$(,!Ʈ/YDF_QӮ3Irޙx\V30`*?Ke@$a?Jf.N[ĕ11)$eEP8ܾϸˑƔR?'9xHPXB?]^Mi<01\f23Idg/ R?Ke@'ġ :VbTL\IS` $ êr?9xҊGg/ Gik/B(}\t^4v^$Y% bPt1u*rަ.$m$ êr?9xҊGg/ Gir^cWwZx#/(LioLphbnhG+G(` ĒPҁ?!G]*]J*cXaW"n_ge@|J)͜$(,!Ʈ/YDF_QӮ3Irޙx\V35%s",Jf.N[ĕ9tBIGAY}BGT7/2>r)͜$(,!Ʈ/YDF_QӮ3Irޙx\V3H$ ċ$P_f%QJR-bJ-$ êr?9yE^cWwZx#/(LioLphbnhG+GP*?KeJġ :VbTL\ISDB)$eEP8ܾϸˑ(O6r𐠰fy|aGcN%zeCsDf=qZ?^H%#d>v^$b!G]*]J*r戤t5!u@r>.G/(v^$X3(YS1q%LhtĀ $ êr?9yE^cWwZx#/(LioLphbnhG+G a9xJf.N[ĕ1<:I >k/B(}\t^QE#y#4֞( r)͜$(,!Ʈ/YDF_QӮ3Irޙx\V3(j?KeJ(ġ :VbTL\ISoYd"A8$t5!u@r>.G/(r)͜$(,!Ʈ/YDF_QӮ3Irޙx\V3IH,(h0/3(YS1q%@$űƹ$ êr?9yE^cWwZx#/(LioLphbnhG+G %%s$3ġ :VbTL\IS=u)$eEP8ܾϸˑ(O6r𐠰fy|aGcN%zeCsDf=qZ?^4`4 Č,ġ :VbTL\IS1["@H:??:q}q#QHl!Aa5wyz5 2ƝqK&$z01, O3(YS1q%Lhtq$eEP8ܾϸˑ(O6r𐠰fy|aGcN%zeCsDf=qZ?^Hb2Xg;/IBA?!G]*]J*cijIGAY}BGT7/2>r)͜$(,!Ʈ/YDF_QӮ3Irޙx\V30,$h f%QJR-bJ+!$eEP8ܾϸˑ(O6r𐠰fy|aGcN%zeCsDf=qZ?^-%s# BuҬԩz4rΌ] $ êr?9yE^cWwZx#/(LioLphbnhG+G-%s cI7BuҬԩz4Am$ êr?9yE^cWwZx#/(LioLphbnhG+G 1%s# +ġ :VbTL\IS:\sWI >k/B(}\t^QE#y#4֞( t%G]*]J*c[o 䒄YS1q%Lk>^JIBTuҬԩz6i$*:VbTL\IS"Pt1u*rަ.$m!a% QJR-bJՏ$RJf.N[ĕ1=Pt1u*rަ.$X4E$*:VbTL\ISm$*:VbTL\IS$IBTuҬԩz4y$%G]*]J*c[rE$*:VbTL\IS۩YS1q%Lm:Jf.N[ĕ1d*m$*:VbTL\ISgI(JU9oST<0IBTuҬԩz4Am$*:VbTL\IS:\sWI(JU9oSTƎdFj)% QJR-bJAf:޳lE$*:VbTL\IS:'8>hMBJf.N[ĕMPq\e$@P2`("P (X@_ ?(cN%zeCsDf=qZlt(YS1q'0(YSH@^1( 0h0a 7!błOJ+4\^841,`ď\V#/(t1u*rަ.$"n_ge@|R?'9xHPXB?]^Mi<01\f2e$z2G`}HF Pt1u*rަ.$vA|_PQGg/ Gi.G/(v^$ J(BU9oSTƎa"A|_PQGg/ Giv^$`?k/B(}\t^QE#y#4֞( r)͜$(,!Ʈ/YDF_QӮ3IrޙxIJ̓=qZ?^Q#IG`}Hx!G]*]J*cG6E$ êr?9yE^cWwZx#/(LioLphbYfdg/a9xFġ :VbTL\IS9u$t5!u@r>.G/(v^$ `bk/B(}\t^QE#y#4֞( k/B(}\t^QE#y#4֞( .G/(k/B(}\t^QE#y#4֞( r)͜$(,!Ʈ/YDF_QӮ3IrޙxIJ̓=qZ?^ , %s#ƌq(BU9oSTƎpxA|_PQGg/ Gi Image location. Suggested Reading HACMP for AIX Concepts and Facilities HACMP for AIX Installation Guide Prerequisite Information Related Information The imserv, imcreate, and imconvert commands. /P k"AB0i7]7P`7!EB./usr/share/man/cat1/imconvert.1 imconvert Command ***************** Purpose This command lets you convert an Ximage to or from a RAW or FILE access format. You must use this command to store images on a RAW logical volume, or to remove them from a RAW logical volume to a filesystem. Syntax imconvert [-d LEVEL][-i LEVEL] [-p] -t image_location -f image_location To convert images from one format to another (RAW and FILE). imconvert [-d LEVEL][-i LEVEL] [-l] [-p] [-a image_name] [-r image_name] image_location To operate on a set of images (RAW and FILE). Description The imconvert command is used to convert cluster image server images in a number of ways. The two basic formats are FILE and RAW. In FILE mode, each image is represented by three files (.args, .data, and .txt) and the directory list of images is stored in a file called image.dir. These files are in the directory named by the environment variable IMSERV_IMAGE_LOCATION. If the file named in the environment variable IMSERV_IMAGE_LOCATION is a logical volume (raw drive), it is understood that the images are stored in RAW format. This is usually the case when the image server is being used in concurrent mode and when the images are stored directly on a raw disk that allows concurrent access. The images are all stored in one file with an internal directory prepended. The imconvert command lets you list, add, and delete these directories, as well as convert between the different types of image directories. Flags -d The level of debug output the user wishes to see. The higher the number, the more output printed. -i The level of informational output to be shown. The higher the level, the more information. -f The source image location from which the conversion utility takes original images to operate on. It can be either a RAW or FILE location. -t The target image location from which the conversion utility should put the converted images. It can be either a RAW or FILE location. -l List all the images in the images directory. -a Add an image to the images directory. If the image location is in FILE mode, the imconvert utility tries to find the .args, .data, and .txt files. Once found, the utility adds an entry to the images.dir file. If the image location is in RAW mode, it will search the directory for a deleted entry that matches and clear its deleted status. -r Remove an image from the images directory. If the image location is a RAW file, this option marks the image as deleted, creating a hole in the directory that can be filled in with using the Pack option. -p Pack the images directory; this removes holes in the RAW images directory, thus removing "deleted" images from the RAW image file. Deleted images can't be recovered after a pack operation. Examples 1. To convert images in the default images directory to RAW format and store them on the raw logical volume /dev/rawlv1, enter: imconvert -f /usr/lpp/cluster/samples/demos/image/images -t /dev/rawlv1 Note: Be very careful that a filesystem is not mounted on /dev/rawlv1. 2. To list images in the images.dir file in the given directory, enter: imconvert -l /usr/lpp/cluster/samples/demos/image/images Implementation Specifics This command is part of High Availability Cluster Multi-Processing for AIX (HACMP for AIX). Files /usr/lpp/cluster/samples/demos/image/images Default image home directory. /usr/lpp/cluster/samples/demos/image/images/images.dir The image directory file. An imagename.args, imagename.txt, and imagename.data file exists for each image_name listed. /usr/lpp/cluster/samples/demos/image/images/.args Binary image description. /usr/lpp/cluster/samples/demos/image/images/.txt Text associated with image. /usr/lpp/cluster/samples/demos/image/images/.data Actual image data. /usr/sbin/cluster/demos/image/imconvert The imconvert command executable file. Suggested Reading HACMP for AIX Concepts and Facilities HACMP for AIX Installation Guide Prerequisite Information Related Information The imcat, imserv, and imcreate commands. ion k꼷@ 0i7]7P`7!AD ./usr/share/man/cat1/imserv.1.1 imserv Command ************** Purpose The imserv program responds to image requests from imcat clients. Syntax imserv [image_directory] [service_address] Description The imserv program runs on HACMP for AIX server nodes. It responds to image requests from client imcat programs and in turn requests locks on images from the Cluster Lock Manager daemon (cllockd) so that no two clients can access images simultaneously. The imserv program returns the requested image to the imcat program once an image lock is granted. The imserv program loads images, (the names of which appear in a file named images.dir in the same location), from a location specified either on the command line or in the environment variable IMSERV_IMAGE_LOCATION. If a location is not given, the images will be loaded from the following default location: /usr/lpp/cluster/samples/demos/image/images. Imserv then transmits images over a UDP connection to imcat (1) in response to requests. Flags image_directory Directory containing images. The default directory is /usr/lpp/cluster/samples/demos/image/images. service_address Creates a listen socket using the IP address specified. The default is localhost. Examples 1. If you want the image server to listen on the IP address of the localhost, enter: imserv 2. If you want the image server to connect to IP address 123.123.123.123, enter: imserv 123.123.123.123 3. If you want the image server to listen on the IP address of host clamhost, enter: imserv clamhost Implementation Specifics This command is part of High Availability Cluster Multi-Processing for AIX (HACMP for AIX). Files /usr/lpp/cluster/samples/demos/image/images The default image home directory. /usr/lpp/cluster/samples/demos/image/images/images.dir The image directory file. An imagename.args, imagename.txt, and imagename.data file exists for each image_name listed. /usr/lpp/cluster/samples/demos/image/images/.args Binary image description. /usr/lpp/cluster/samples/demos/image/images/.txt Text associated with image. /usr/lpp/cluster/samples/demos/image/images/.data Actual image data. /usr/sbin/cluster/demos/image/imcat The imcat command executable file. Environmental Variables IMSERV_IMAGE_LOCATION Image home directory override. Suggested Reading HACMP for AIX Concepts and Facilities HACMP for AIX Installation Guide Prerequisite Information Related Information The imcat, imcreate, and imconvert commands. 4 k@0i7]7P`7!E./usr/share/man/cat1/clstat.1.1 clstat Command ************** Purpose Monitors the status of an HACMP cluster. Syntax (ASCII mode) clstat [-a] [-c ID] [-i] [-r seconds] (X mode) xclstat [-c ID | -n name] [-r #] [-D debug_level] Description The clstat utility uses the clinfo library routines to display all node and interface information about a selected cluster. Clstat can be run on any type of terminal, ASCII or xterm. Two modes are supported: ASCII mode and X Window mode. ASCII mode can run on terminals running X Windows by specifying the -a flag when issuing the clstat command. The clstat utility runs in either single-cluster or multi-cluster mode. Single-cluster mode run only on the cluster specified. If the -c flag is not used, clstat searches for the first accessible cluster on the system. If more than one cluster is available, clstat will not run in single-cluster mode. Specifying the -c flag and the cluster ID will circumvent this situation. Multi-cluster mode allows the monitoring of a number of clusters accessible to the local system. If more than one cluster is active, multi-cluster mode allows you to toggle back and forth between cluster status displays. Multi-cluster mode is more interactive. The clstat X Window display is automatically run on any terminal running X. Up nodes are shown in green, down nodes are shown in red. Nodes that are either joining or leaving the cluster (topology changes) are shown in yellow, and undefined nodes are shown in the background color. Pressing the left mouse button on a particular node causes a popup window with interface information to appear. Flags -c ID Display information about the cluster with the specified Id, if cluster is active. -r interval Specifies the refresh interval; that is, the frequency with which clstat queries clinfo for new cluster information. In ASCII mode, interprets the value of interval in seconds. The default interval is 1 second. In X display mode, clstat interprets the value of interval in tenths of seconds. The default interval is .1 of a second. -a Run clstat in ASCII mode on an X Window display. (ASCII mode only flag) -i Run clstat in interactive mode. Initially displays a list of all clusters accessible to the system. The user must select the cluster for which to display the detailed information. From the display, a number of functions are available: # - Specify the cluster ID to select and monitor that cluster. [ENTER] - Update the display imediately. q - Return to the cluster list display. Note: May not be specified if the -c ID option is used. (X mode only flag) -n name Display information about cluster with specified cluster name, if the cluster is active. -D debug_level The debug level applies to using clstat in X Window display mode. This flag determines the level of debugging to be performed. The levels range from 1 to 9 in increasing amounts of information. The default (0) turns degugging off. Buttons Prev Display previous cluster. Next Display next cluster. Cluster:Id Refresh bar, pressing bar causes xclstat to refresh immediately. quit Exit clstat utility. help Popup help window with this manual page. Examples 1. To display the cluster information about the cluster with the cluster ID of `10', refreshing the display every three seconds, in ASCII mode, enter: clstat -c 10 -r 3 2. To run clstat (ASCII mode) in interactive mode, allowing multi-cluster monitoring, enter: clstat -i 3. To display the cluster information about the first cluster to be identified to the local system, refreshing the display every five seconds, in ASCII mode, enter: clstat -a -r 5 Implementation Specifics This command is part of High Availability Cluster Multi-Processing for AIX (HACMP for AIX). Files /usr/sbin/cluster/clstat The clstat command executable file. /usr/sbin/cluster/xclstat The xclstat command executable file. Suggested Reading HACMP for AIX Concepts and Facilities HACMP for AIX Administration Guide HACMP for AIX Programming Client Applications Prerequisite Information Related Information The clinfo command. kr@0i7]7P`7!?D./usr/share/man/cat1/clstop.1.1clstop Command ************** Purpose Stops the Cluster daemons. Syntax clstop { -f | -g | -gr } [-s] [-y] [ -N | -R | -B ] Description The clstop command stops the cluster daemons using the System Resource Controller utility. The daemons can be stopped either gracefully or forcefully. The command optionally removes automatic start on reboot via its inittab entry. Flags -f Forced shutdown. Cluster daemons should terminate without running any local procedures. -g Graceful shutdown with no takeover. -gr Graceful shutdown with the resources being released by this node and taken over by another node, if completed. The daemons should terminate gracefully, and the node should release its resources, which will then be taken over. -s Silent shutdown, specifies not to broadcast a shutdown message via /usr/sbin/wall. The default is to broadcast. -y Confirms the shutdown of the specified node. This flag is the default. -N Shutdown now. -R Removes automatic start of cluster daemons on subsequent system restart (removes the inittab entry). -B Stop now and remove automatic start on subsequent system restart. Examples 1. To shut down the cluster node gracefully, releasing the resources, with no warning broadcasted to users before the cluster processes are stopped and resources are released, enter: clstop -gr -s -y 2. To forcefully and immediately shut down the Cluster node, resources not released, with warning broadcasted to users before the Cluster processes are stopped, enter: clstop -f -y 3. To shut down the Cluster node gracefully, releasing resources to be taken over and with broadcasting a warning to users before the Cluster processes are stopped, enter: clstop -gr -y Implementation Specifics This command is part of High Availability Cluster Multi-Processing for AIX (HACMP for AIX). Files /usr/sbin/cluster/utilities/clstop The clstop command executable file. Suggested Reading HACMP for AIX Concepts and Facilities HACMP for AIX Administration Guide Prerequisite Information Related Information The clstart, stopsrc, startsrc, clstrmgr, clinfo, and cllockd commands. X k:A}0i7]7P`7!D}./usr/share/man/cat1/imcreate.1 imcreate Command **************** Purpose Creates images for HACMP for AIX image server (imserv). Syntax imcreate filename.xbm Description The imcreate command creates three imserv image files (data, text, and description) from the X bitmap file specified on the command line. It puts this new image file in the current directory. The new files must then be placed into the directory in which the Image Server retrieves its images. Also, the images.dir file, in the same directory, must be updated with the base name of the new image in order for the Image Server to display the new image. Flags/Arguments filename.xbm Name of a valid X bitmap file. The file must end with the .xbm extension. Example To create a mailfull.args, mailfull.data and mailfull.txt file in the current working directory, enter: imcreate /usr/include/X11/bitmaps/mypicture Implementation Specifics This command is part of High Availability Cluster Multi-Processing for AIX (HACMP for AIX). Files /usr/lpp/cluster/samples/demos/image/imcreate The imcreate executable file. /usr/lpp/cluster/samples/demos/image/images/.args Binary image description. /usr/lpp/cluster/samples/demos/image/images/.data Actual image data. /usr/lpp/cluster/samples/demos/image/images/.txt Text associated with image. Suggested Reading HACMP for AIX Concepts and Facilities HACMP for AIX Installation Guide Prerequisite Information Related Information The imcat, imconvert, imserv commands. kBA?0i7]7P`7!D?./usr/share/man/cat1/marxclient.1 marxclient Command ****************** Purpose Initializes the CLMarket X Window client process. Syntax marxclient Description Starts the CLMarket X Window process on a client to display the Checkout Client graphical user interface. Flags/Arguments None Example To display the CLMarket Checkout Client, enter: marxclient Implementation Specifics This command is part of Highly Available Cluster Multi-Processing for AIX (HACMP for AIX). The CLMarket server process must be enabled on a node before the Checkout Client can be run. Files /usr/sbin/cluster/demos/clmarket/marxclient The CLMarket X Window client executable file. /usr/sbin/cluster/cllockd The Cluster Lock Manager daemon that coordinates requests for shared data in concurrent access environments. Suggested Reading HACMP for AIX Concepts and Facilities HACMP for AIX Installation Guide Prerequisite Information Related Information The marinit, mara2db, and mardb2a commands. s ki@0i7]7P`7!WD./usr/share/man/cat1/rc.cluster.1 rc.cluster Command ****************** Purpose Sets up the operating system environment and starts the cluster daemons: clstrmgr, clinfo, cllockd, and clsmuxpd. Syntax rc.cluster [-boot] [-l] [-i] [-b] [-N | -R | -B] Description The rc.cluster command first sets the operating system environment by making any necessary changes to the inittab file. Then it runs /etc/rc.net, if applicable, to set up the network configuration and verifies that the System Resource Controller (SRC), System Logger, portmapper and inetd daemons are started and are active -- i.e. it invokes harc.net. After setting network options, it uses the SRC to start the cluster and lock group daemons. By default, the cluster group daemons (clsmuxpd, and clstrmgr) are started on servers, and clinfo is started on clients. Flags -boot Configures the service adapter to be on its boot address if IPAT is enabled. -l Starts the Cluster Lock Manager daemon (cllockd) with its default options. -i Starts the Cluster Information (clinfo) daemon with its default options. -b Broadcasts the startup message. -N Starts the daemons Now (no inittab change). -R Starts the HACMP daemons on system restart only (the HACMP start-up command is added to inittab file). -B Starts the daemons Now and adds the HACMP entry to the inittab file. Example To start the cluster with lock services, and to broadcast the event, enter: rc.cluster -boot -l -b Note: The Cluster Manager (clstrmgr) and Cluster SMUX Peer (clsmuxpd) daemons are automatically started when this command is executed. The command ensures that the service adapter is configured to use its boot address if IPAT is enabled. Implementation Specifics This command is part of High Availability Cluster Multi-Processing for AIX (HACMP for AIX). Files /usr/sbin/cluster/etc/rc.cluster The rc.cluster command script file. /etc/inittab The cluster initialization script. Suggested Reading HACMP for AIX Concepts and Facilities HACMP for AIX Administration Guide Prerequisite Information Related Information The rc.net script and clstart command. , stops kj@&0i7]7P`7!BD&./usr/share/man/cat1/clruncmd.1 clruncmd Command **************** Purpose Executes Cluster Manager command. Syntax clruncmd hostname [command] Description The clruncmd command instructs the Cluster Manager on the specified host to restore the cluster to normal operation. For instance, if the cluster has been in reconfiguration too long, perhaps due to a script failure, the clruncmd command allows the Cluster Manager to behave as though the script completed successfully. This command should be run only after the reasons for the failure have been manually corrected and the actions which the scripts would have taken have been performed. Note: When running the clruncmd on a remote host, the IP Label of the local host must be defined in the /.rhosts file on the remote host. Flags hostname [command] Connects to Cluster Manager on the specified host. Example To instruct the Cluster Manager on the host "node1" to return to normal operation, enter: clruncmd node1 This is a useful way to restart the Cluster Manager after script failures have been corrected. Implementation Specifics This command is part of High Availability Cluster Multi-Processing for AIX (HACMP for AIX). Files /usr/sbin/cluster/utlities/clruncmd The clruncmd command executable file. .rhosts Specifies remote users allowed to use a local user account. Suggested Reading HACMP for AIX Concepts and Facilities HACMP for AIX Administration Guide Prerequisite Information Related information The clstrmgr command. on k 2A}0i7]7P`7!D}./usr/share/man/cat1/clgetaddr.1clgetaddr Command ***************** Purpose Returns a PINGable address for the specified node name. Syntax clgetaddr [-o odmdir] nodename Description Returns a PINGable address for any node name you specify. Flags -o odmdir Specifies the path to the ODM directory to retrieve the specified node address. Example To get a PINGable address for the node seaweed, enter: clgetaddr [-o odmdir] seaweed The following address is returned: 2361059035 Implementation Specifics This command is part of High Availability Cluster Multi-Processing for AIX (HACMP for AIX). Files /usr/sbin/cluster/utilities/clgetaddr The clgetaddr command executable file. Suggested Reading HACMP for AIX Concepts and Facilities HACMP for AIX Administration Guide Prerequisite Reading Related Information The cllscf and cllsnode commands. ruc k`4Ax0i7]7P`7!Dx./usr/share/man/cat1/clgodmget.1 clgodmget Command ************ Purpose List ODM class remotely. Syntax clgodmget [-c] [-q criteria] -n nodename class Description Shows ODM class information for the specified node and HACMPclass. Flags -c Specifies the colon output format. -q criteria Specifies ODM search criteria. See the odmget man page for information on search criteria. If no criteria are entered, all objects in the class are retrieved. -n Searches the ODM from the specified node. class ODM object class. Examples To print adapter information for the node foo, enter: clgodmget -n foo HACMPadapter Implementation Specifics This command is part of High Availability Cluster Multi-Processing for AIX (HACMP for AIX). Files /usr/sbin/cluster/utilities/clgodmget The command executable file /etc/objrepos/HACMPclass Specific ODM object class Suggested Reading HACMP for AIX Concepts and Facilities HACMP for AIX Administration Guide AIX Version 4.1 General Programming Concepts Prerequisite Information Related Information odmget command k5A0i7]7P`7!D./usr/share/man/cat1/cllsgrp.11 cllsgrp Command *************** Purpose Lists all resource groups configured for a cluster. Syntax cllsgrp Description Displays the names of all resource groups in the cluster. Example To show resource group information for a cluster, enter: cllsgrp Shows the following (for example): grp1 grp2 grp3 grp4 Implementation Specifics This command is part of High Availability Cluster Multi-Processing for AIX (HACMP for AIX). Files /usr/sbin/cluster/utilities/cllsgrp The cllsgrp command executable file Suggested Reading HACMP for AIX Concepts and Facilities HACMP for AIX Administration Guide Prerequisite Information Related Information The clshowres command. lti- k7A0i7]7P`7!D./usr/share/man/cat1/cllsparam.1 cllsparam Command ***************** Purpose Lists run-time parameters configured for a node. Syntax cllsparam -n nodename [-c] [-s] [-d odmdir] Description Shows run-time parameters for the specified node. Flags -n nodename Specifies the node for which to list parameters. -c Specifies a colon output format. -s Used with the -c flag, specifies native language instead of English. -d Specifies an alternate ODM directory. Example cllsparam -n node1 Shows the following run-time parameters for the node node1: NODE_NAME=node1 VERBOSE_LOGGING=high NAME_SERVER=false Implementation Specifics This command is part of High Availability Cluster Multi-Processing for AIX (HACMP for AIX). Files /usr/sbin/cluster/utilities/cllsparam The command executable file Suggested Reading HACMP for AIX Concepts and Facilities HACMP for AIX Administration Guide Prerequisite Information Related Information f k>9Ao0i7]7P`7!Do./usr/share/man/cat1/get_local_nodename.1 get_local_nodename Command ************************** Purpose Retrieves the name of the local node. Syntax get_local_nodename Description Returns the name of the local node. Flags none Implementation Specifics This command is part of High Availability Cluster Multi-Processing for AIX (HACMP for AIX). Files /usr/sbin/cluster/utilities/get_local_nodename The command executable file. Suggested Reading HACMP for AIX Concepts and Facilities HACMP for AIX Administration Guide Prerequisite Reading Related Information The cllscf and cllsnode commands. kDA0i7]7P`7!D./usr/share/man/cat1/cllsnim.1n cllsnim Command *************** Purpose Lists contents of the HACMPnetwork interface module ODM object class. Syntax cllsnim [-d odmdir] [-c] [-n name] Description Shows network interface module information for all avaialble network modules. Flags -d odmdir Specifies an alternate ODM directory to /etc/objrepos. -c Specifies a colon output format. -n name Specifies the name of a specific network interface module. Examples cllsnim Shows information for all available network modules (see ether example below for type of information shown). cllsnim -n ether Shows information for all available Ethernet network modules: Name Add-Type Param G-Period HT-Rate F-Cycle Path ether Address 30 50 12 /usr/sbin/cluster/nims/nim_ether Implementation Specifics This command is part of High Availability Cluster Multi-Processing for AIX (HACMP for AIX). Files /usr/sbin/cluster/utilities/cllsinim The cllsnim command executable file Suggested Reading HACMP for AIX Concepts and Facilities HACMP for AIX Administration Guide HACMP for AIX Installation Guide Prerequisite Information Related Information The cllscf, cllsnode, and cllsnw commands. k.FA0i7]7P`7!D./usr/share/man/cat1/clnodename.1ename. clnodename Command ****************** Purpose Lists, adds, changes, or removes the cluster node name. Syntax clnodename [-d odmdir] -o oldname -n newname clnodename [-d odmdir] -a `name(s)' clnodename [-d odmdir] -r name clnodename [-d odmdir] Description The clnodename command manipulates the HACMPnode ODM object class. The command lets you list configured cluster node names, add multiple node names to a cluster in one operation, change an existing node name, and remove an existing node name from the cluster. Flags -d odmdir Specifies an alternate ODM directory other than /etc/objrepos. -o oldname Specifies the old node name when changing a node name. -n newname Specifies the new node name when changing a node name. -a name(s) Specifies the node name(s) to be added to the cluster. -r name Specifies the node name to be removed. Example To list all the nodenames configured for a cluster, enter: clnodename The command returns the list, for example: clam oyster seaweed Implementation Specifics This command is part of High Availability Cluster Multi-Processing (HACMP for AIX). Files /usr/sbin/cluster/utilities/clnodename The clnodename executable file. Suggested Reading HACMP for AIX Concepts and Facilities HACMP for AIX Administration Guide Prerequisite Reading Related Information H kHA0i7]7P`7!D./usr/share/man/cat1/clrmclstr.1ename. clrmclstr Command ***************** Purpose Removes the cluster configuration (cluster, node, network, adapter, group, resource HACMP ODM object classes) and undoes any changes that were made to the /etc/rc.net and /etc/inittab files due to the configuration. Syntax clrmclstr Description The clrmclstr command deletes the cluster configuration. Use this command with caution. If you are sure that you DON'T want the current cluster configuration, this command deletes it quickly. Flags None Implementation Specifics This command is part of High Availability Cluster Multi-Processing for AIX (HACMP for AIX). Do not execute this command from the command line. Use the SMIT interface as explained in the documentation. Files /usr/sbin/cluster/utilities/clrmclstr The clrmclstr executable file. Suggested Reading HACMP for AIX Concepts and Facilities HACMP for AIX Administration Guide Prerequisite Reading Related Information The claddclstr command. ist, k$'A80i7]7P`7!fD8./usr/share/man/cat1/cllsvg.1.1 cllsvg Command ************** Purpose Lists the shared volume group(s), i.e. the volume groups which are accessible by all participating nodes in a resource group. If no resource group is given, then for each configured resource group the command lists the resource group name along with their shared volume groups. Syntax cllsvg [ -g resource_group ] [ -n ] [-v] Description The cllsvg command retrieves a list of volume groups shared by nodes in a resource group and prints information on these volumes groups. A volume group is considered shared if it is accessible by all participating nodes in a configured resource group. Note that the volume groups listed may or may not be configured as a resource in the resource group. Flags -g resource_group Specifies the name of the resource group for which to list volume groups that are shared amongst participating nodes. -n Shows the names of the participating nodes in each resource group. -v Shows only volume groups that are varied on. Examples 1. To list all the volume groups accessible by all nodes participating in a resource group named grp1, enter: cllsvg -g grp1 2. To list all the volume groups accessible by all the configured resource groups, along with the names of the participating nodes in each configured resource group, enter: cllsvg -n Implementation Specifics This command is part of High Availability Cluster Multi-Processing for AIX (HACMP for AIX). Files /usr/sbin/cluster/utilities/cllsvg The cllsvg command executable file. Suggested Reading HACMP for AIX Concepts and Facilities HACMP for AIX Administration Guide Prerequisite Information Related Information The cllsfs command, cllslv command and cllsdisk command. k3 Aw0i7]7P`7!cDw./usr/share/man/cat1/cllsdisk.1 cllsdisk Command **************** Purpose Lists PVIDs of disk(s) shared between or among configured nodes. Syntax cllsdisk -g resource_group Description The cllsdisk command retrieves disk information from cluster nodes and prints physical volume IDs for each disk. Flags -g resource_group Specifies a resource group in which nodes participate. Example To list the PVIDs of disks configured for a resource group named grp1, enter: cllsdisk -g grp1 Implementation Specifics This command is part of High Availability Cluster Multi-Processing for AIX (HACMP for AIX). Files /usr/sbin/cluster/utilities/cllsdisk The cllsdisk command executable file. Suggested Reading HACMP for AIX Concepts and Facilities HACMP for AIX Administration Guide Prerequisite Information Related Information The cllsfs and cllsvg commands. kHA~ 0i7]7P`7!sD~ ./usr/share/man/cat1/claddev.1 claddev Command *************** Purpose Adds an event to the event ODM object class HACMPevent. Syntax claddev [-i nodeName] -e Eventname -d Description [-f NLSCatalogfile] [-m CatalogMessageNo] [-t CatalogSetNo] -s script [-n script] [-b script] [-a script] [-r script] [-c count] [-o odmdir] Description The claddev command adds an event name, event description, NLS description Catalog file, Catalog Id, event handler script, event notify script, pre-event and post-event scripts, recovery script and failure retry times to the HACMPevent object class, either locally or remotely. Note: Eventname, Description, and command scripts are required options. You may not add duplicated event names. Note: CatalogMessageNo, CatalogSetNo, and count are defined as short integers internally. The command uses atoi() to convert command arguments to integer; no validation check is performed on these numbers. Flags -i nodeName Specifies the destination node name. If not specified, adds to local node. -e Eventname Specifies the name of the event. -d Description Default description of the event. Spaces are allowed. -f NLSCatalogfile Specifies the NLS Catalog file where the event description is held. If this file doesn't exist, the default description is used. -m CatalogMessageNo Specifies the NLS Catalog message number of the description, if a CatalogFile entry exists. -t CatalogSetNo Specifies the NLS Catalog message set number of the description, if a CatalogFile entry exists. -s script Specifies the event handler script (command) to execute when the event happens. -n script Specifies the notify script (command) to execute both before and after the event handler script is executed. -b script Specifies the pre-event script (command) to run before the event handler scripts are executed. -a script Specifies the post-event script (command) to run after the event handler script is executed. -r script Specifies the recovery script (command) to execute to recover from a failed event handler execution. If the retry count is greater than zero and this script succeeds, the event handler script is rerun. -c count Specifies the number of times to run the recovery command. Default value is zero if no recovery command is specified, or 1 (one) if a recovery command is specified. -o odmdir Specifies an ODM directory other than the default /etc/objrepos. Implementation Specifics This command is part of High Availability Cluster Multi-Processing for AIX (HACMP for AIX). Do not run this command from the command line. Use the SMIT interface as explained in the documentation. Files /usr/sbin/cluster/events/cmd/claddev The claddev command executable file. /etc/objrepos/HACMPevent The event ODM object class. Suggested Reading HACMP for AIX Concepts and Facilities HACMP for AIX Administration Guide HACMP for AIX Installation Guide Prerequisite Information Related Information The cllsev, cldelev, clchev, and clcallev commands, and the clsubmitev and clpollev scripts. 43 k6@X 0i7]7P`7!DDX ./usr/share/man/cat1/claddnim.1 claddnim Command **************** Purpose Add or change an entry in the HACMPnim ODM class. Syntax claddnim [-d odmdir] -o oldname -n name -D 'description' -f {'0' | '1'} -p path [-g grace_period] [-r heart_beat_rate] [-c cycle_to_fail] [-l parameter] Description Each supported cluster network in a configured HACMP cluster has a corresponding network interface module (NIM). Each network module maintains a connection to other network modules in the cluster. The periodic heartbeat traffic across these networks is used to verify connectivity to cluster peers. Use the claddnim command to add a NIM or change the characteristics of an existing NIM. (Typically, only change the failure detection rate is changed.) Flags/Arguments -d Specifies an alternative ODM directory. -D Specifies a text string that describes the NIM. This is typically the type of network; for example, ethernet. -n name Specifies the name of a NIM. When the -o flag is also specified, this flag represents the new name. -o oldname Specifies name of an existing NIM. -f Specifies type of NIM. Use the value zero (0) if the NIM controls a TCP/IP network, such as an ethernet network. Use the value one (1) to indicate the NIM controls a raw device file such as the target mode SCSI NIM. -p path Specifies the path to the NIM executable. -g grace_period Specifies the NIM failure grace period. -l parameter Specifies any arguments that get passed to the NIM executable. -r heart_beat_rate Specifies the heartbeat rate which determines the failure detection rate. -c cycle_to_fail Specifies the cycle to fail. Implementation Specifics This command is part of High Availability Cluster Multi-Processing for AIX (HACMP for AIX). To reset the NIM heartbeat rates for several NIMs, use the SMIT. Files /usr/sbin/cluster/utilities/claddnim The command executable file /etc/objrepos/HACMPnim NIM ODM object class Suggested Reading HACMP for AIX Concepts and Facilities HACMP for AIX Installation Guide HACMP for AIX Administration Guide Prerequisite Information Related Information kVA0i7]7P`7!jD./usr/share/man/cat1/claddserv.1ename. claddserv Command ***************** Purpose Adds an application server to the server ODM database HACMPserver. Syntax claddserv -s server-name -b start-script -e stop-script [-d odmdir] Description The claddserv command adds an application server (identified by server-name, start- and stop-script) to the server ODM object class on the local node. This ODM object class, like all other node-environment related object classes (HACMPresource, HACMPgroup, and HACMPfence) must be synchronized through the Synchronize Cluster Resources SMIT screen. The cluster-related ODM classes must be synchronized through the Synchronize Cluster Topology SMIT screen. Flags -d odmdir Specifies an alternative directory in which to search for the file containing the object class. The default is /etc/objrepos. -s server-name Specifies the name of the application server. -b start-script Specifies the full path to the command that starts the application server. -e stop-script Specifies the full path to the command that stops the application server. Implementation Specifics This command is part of High Availability Cluster Multi-Processing for AIX (HACMP for AIX). Do not run this command from the command line. Use the SMIT interface as explained in the documentation. Files /usr/sbin/cluster/utilities/claddserv The claddserv executable file. /etc/objrepos/HACMPserver The application server ODM object class. Suggested Reading HACMP for AIX Concepts and Facilities HACMP for AIX Administration Guide HACMP for AIX Installation Guide Prerequisite Information Related Information The cllsserv, clchserv,and clrmserv commands. /@ k( A-0i7]7P`7!`D-./usr/share/man/cat1/claddres.1 claddres Command **************** Purpose Writes resource variables to the node environment ODM object class HACMPresource. Syntax claddres -g group [-d odmdir] NAME=VALUE [NAME=VALUE ...] Description The claddres command first removes any existing resource variable for a particular Resource Group, and then adds the new variables to the HACMPresource object class. It accepts as arguments variable declarations much in the style of UNIX shell variable assignments. This utility does minimal error checking. Syntax must be followed strictly; otherwise results are unpredictable. The following are valid variables: DISK, VOLUME_GROUP, CONCURRENT_VOLUME_GROUP, FILESYSTEM, EXPORT_FILESYSTEM, MOUNT_FILESYSTEM, APPLICATIONS, MISC_DATA, INACTIVE_TAKEOVER, DISK_FENCING, SERVICE_LABEL SSA_DISK_FENCING, AIX_CONNECTIONS_SERVICE, SNA_CONNECTIONS, AIX_FAST_CONNECT_SERVICES If names other than the ones listed above are specified, no error message is printed. The length of a variable name must not exceed 31 characters. The length of a variable value depends on the field size. Excess characters will be discarded. Flags -d odmdir (Optional) Specifies an alternative directory to search for the file containing the object class. The default is /etc/objrepos. -g group Specifies the name of the resource group. Implementation Specifics This command is part of High Availability Cluster Multi-Processing for AIX (HACMP for AIX). Do not run this command from the command line. Use the SMIT interface as explained in the documentation. Files /usr/sbin/cluster/utilities/claddres The claddres command executable file. /etc/objrepos/HACMPresource The HACMP for AIX node environment ODM object class. Suggested Reading HACMP for AIX Concepts and Facilities HACMP for AIX Administration Guide HACMP for AIX Installation Guide Prerequisite Information Related Information The cllsres, clrmres, and clshowres commands. ies k$A0i7]7P`7!~D./usr/share/man/cat1/clchev.11 clchev Command ************** Purpose Modifies an event in the event ODM object class HACMPevent. NOTE: It is recommended that you run this command via the SMIT interface as explained in the HACMP for AIX documentation. The SMIT interface controls the information passed to this command in a way that is consistent with the use of the event information by HACMP and also ensures that the HACMPevent ODM files are kept in sync on all cluster nodes. Primarily for historical reasons, other clchev flags are still supported, but they should be used with caution, as outlined below. Syntax As shown below, the event name can be passed to clchev either using the -O flag or without a flag as the last parameter: clchev [-i nodeName] -O Eventname [-e new-eventname] [-d description] [-f NLSCatalogfile] [-m CatalogMessageNo] [-t CatalogSetNo] [-s script] [-n script] [-b script] [-a script] [-r script] [-c count] [-o odmdir] OR: clchev [-i nodeName] [-e new-eventname] [-d description] [-f NLSCatalogfile] [-m CatalogMessageNo] [-t CatalogSetNo] [-s script] [-n script] [-b script] [-a script] [-r script] [-c count] [-o odmdir] Eventname Description The clchev command modifies an event's information in the event ODM object class (either locally or remotely). If the event name specified in the command line has no match in the event ODM, the command takes no action. Only the field specified in the command line is changed in the event ODM, with the exception of the Notify, Pre-Event, Post-Event, and Recovery script fields. If they are not supplied when invoking the clchev command, any existing values will be removed from the HACMPevent ODM file. Note: CatalogMessageNo, CatalogSetNo, and count are defined as short integers internally. The command uses atoi() to convert command arguments to integer, no validation check is performed on these numbers. Flags Flags exist for every field found in the HACMPevent ODM file. However, some of these flags will rarely, if ever, need to be used. The flag descriptions are grouped below according to their intended use: Flags Available When Invoking clchev via the SMIT Interface: -O Eventname Specifies the event name to look up from event ODM. -s script Specifies the new event handler script(command). -n script Specifies the new notify script(command). -b script Specifies the new pre-event script(command). -a script Specifies the new post-event script(command). -r script Specifies the new recovery script(command). -c count Specifies the new count (times to retry event). Flags Maintained for Historical Reasons: -i nodeName Specifies the node name. If not specified, changes are made to the local node. NOTE: The -i flag was used in earlier versions of HACMP when the HACMPevent ODM file was managed on a node-by-node basis. Since the HACMPevent ODM file is now synchronized across all nodes, this flag is no longer necessary. As a convenience to users who still want to perform HACMP event customization on a node-by-node basis, however, this flag is still supported. However, those who use it should be aware that synchronizing the cluster will propagate the HACMPevent file to all cluster nodes from the one where the synchronization is initiated, thereby wiping out any differences that may have been introduced by using the clchev command with the -i flag. Flags Used to Manage Fields that Rarely, if Ever, Need to be Changed: -e eventname Specifies the new event name. -d description Specifies the new modified description. Spaces are allowed. -f NLSCatalogfile Specifies the new NLS Catalog file. -m CatalogMessageNo Specifies the new Catalog message number. -t CatalogSetNo Specifies the new Catalog message set number. -o odmdir Specifies an ODM object repository directory other than the ODMDIR environment value. NOTE: The above fields should never need to be used, but are supported by clchev only to provide the means to update all HACMPevent ODM file fields. Examples clchev -O'acquire_service_addr' -n '/usr/local/scripts/notify_script' The above command will add notify script /usr/local/scripts/notify_script to the acquire_service_addr event. It will also wipe out any existing pre,post, or recovery event scripts for the acquire_service_addr event because of the absence of the corresponding flags for those event scripts. Implementation Specifics This command is part of High Availability Cluster Multi-Processing for AIX (HACMP for AIX). Files /usr/sbin/cluster/events/cmd/clchev The clchev command executable file. /etc/objrepos/HACMPevent The event ODM object class. Suggested Reading HACMP for AIX Concepts and Facilities HACMP for AIX Administration Guide Prerequisite Information Related Information The cllsev, claddev, cldelev, and clcallev commands, and the clsubmitev and clpollev scripts. am kR+A$0i7]7P`7!E$./usr/share/man/cat1/cldiag.11 cldiag Command ************** Purpose Top level command to aid in diagnosing HACMP for AIX cluster hardware and software problems. Syntax cldiag [debug] [logs] [vgs] [error] [trace] Description The cldiag command gives the user access to the top level menu which contains options to several AIX RAS facilities, as well as to HACMP-specific debug and lock-dumping facilities. The following options are available: debug, logs, vgs, error, and trace. Each option can be specified from the command line. When an option is chosen, other options more specific to the task are made available. Note: For cldiag to run successfully, the PATH environment variable for root must include /usr/sbin/cluster/utilities/diag/. It is also recommended that /usr/sbin/cluster be added to root's PATH. cldiag debug Subcommand *********************** Purpose Allows real-time Cluster Manager (clstrmgr) process debug information about be viewed, or allows the Lock Resource Table of the Cluster Lock Manager (cllockd) to be dumped. Syntax cldiag debug clstrmgr [-l level] | cllockd [-R file] Description The cldiag debug option is used to obtain more detailed information on the clstrmgr and cllockd processes. The following options are available: clstrmgr and cllockd. Each option can be specified from the command line. Flags clstrmgr Allow clstrmgr debug information to be viewed. Options: -l Level The level of debugging to be performed. The levels range from 1 to 9 in increasing amounts of information. The default (0) turns debugging off. See the clstrmgr man page for a description of debug levels. -R file The output file to which the output is saved. cllockd Obtain a dump of the Lock Resource table Options: -R file The name of the file in which to save the data. Examples 1. To enable clstrmgr debugging at debug level 2 and save output to a file, enter: cldiag debug clstrmgr -l2 -Rfoo 2. To save a dump of the lock resource table, enter: cldiag debug cllockd -Rfoo cldiag logs Subcommand ********************** Purpose Allows the viewing and parsing of HACMP process and script output files. Syntax cldiag logs scripts [-s | -f | event...] | syslog [-e | -w | -h hostname] | [-d#_of_days | -R file] Description cldiag logs is used to view, filter, and save the output from the HACMP script and process output files. These files contain event execution and error/failure/warning codes. Flags scripts Allows parsing of the script output files, hacmp.outXXX [default location: /tmp] Options: -hHostname Hostname of the system from which to gather data. -s Captures all "Start" and "Complete" events -f Captures all "Fail" events -d#_of_days The number of days preceeding the present day from which information will be gathered. The hacmp.outXXX file is saved in a rotation manner. The present day file is named hacmp.out, the previous day's file is named hacmp.out1, and so on. Up to seven days' worth of files are saved. -R file The name of the file in which to save the data. event... Captures all lines containing the cluster event (such as "node_up_local"). This can be a list of events. syslog Allows parsing of the HACMP daemon output file, cluster.log [default location: /usr/adm] Options: -h hostname The hostname of the system from which to gather data. -e Captures all "Error" events -w Captures all "Warning" events -d#_of_days The number of days preceeding the present day from which information will be gathered, up to seven days' worth of data. The default (0) will use all data in the file, which is arbitrarily long. Note: This option returns information for all days within the cluster.log file. -R file The name of the file in which to save the data. Examples 1. To capture all failed script events in the last three days, enter: cldiag logs scripts -f -d3 2. To capture all errors and any cllockd events from the HACMP syslog, enter: cldiag logs syslog -e cllockd cldiag vgs Subcommand ********************* Purpose Allows the user to check for inconsistencies among Volume Groups. Syntax cldiag vgs -h host [-v volume_groups] Description The cldiag vgs command is used to check for inconsistencies among the node's ODM and the VGDA on the disks. It compares the ODM information of the hosts entered for each volume group entered. It also compares the ODM of each host with the VGDA. Every inconsistency found is sent to standard output. If no volume groups are entered, cldiag vgs uses all the shared volume groups among the nodes. Flags -h hostnames The current list of host names. Enter each name separated by commas. Spaces between characters are not allowed. -v volume_groups volume_groups represent a list of volume group names. They must be entered separated by commas and spaces aren't allowed in between. This flag is optional. Examples 1. To check volume group vgck1 in hosts limpet and cowrie, enter: cldiag vgs -h limpet,cowrie -v vgck1 2. To check all common volume groups in hosts jaws and kelp, enter: cldiag vgs -h jaws,kelp cldiag error Subcommand *********************** Purpose The cldiag error command produces a report showing all system errors that occurred in a particular cluster. Syntax cldiag error type short | long | cluster [-h host | -R file] Description The cldiag error command generates a report based on the report type entered. This error report can also be generated for a particular host and sent to a user-specified file instead of standard output. The default is to generate a short report for the local host and send it to standard output. Flags type Specifies the type of report. It can be short, long, or cluster. A short report generates only one line of data for each error logged. A long report generates a detailed report for each error. A cluster report generates a report for "clstrmgr" and "hacmp". -h host Specifies the name of the host for which to generate the error report. -R file File name representing the file where trace information is to be sent, instead of to standard output. Examples 1. To display a short error report for the local host, enter: cldiag error short 2. To generate a long error report for host steamer and send it to file err_rep, enter: cldiag error long -h steamer -R err_rep 3. To display a cluster error report for host chowder, enter: cldiag error cluster -h chowder cldiag trace Subcommand *********************** Purpose cldiag trace facility helps isolate a problem within an HACMP for AIX system by allowing the user to monitor selected events. Syntax cldiag trace [-t time] [-R file] [-l] daemon ... Description The cldiag trace command captures a sequential flow of timestamped system events that provide a fine level of detail on the activity within an HACMP for AIX cluster daemon. The user is able to choose the tracing time, whether to send the trace information to a file or to standard output, and whether to execute a short trace or a long trace. Flags -t time Specifies the tracing time in seconds. The default is set to 30 seconds. -R file File name representing the file to which to send the trace information, instead of to standard output. -l Specifies a long trace. If this flag is entered, a long trace will be executed. The default is for a short trace. daemon Represents a list of HACMP for AIX cluster daemons for which to execute the trace. clstrmgr Cluster Manager daemon clinfo Cluster Information daemon cllockd Cluster Lock Manager daemon clsmuxpd Cluster SMUX Peer daemon Examples 1. To display trace information for clstrmgr, enter: cldiag trace clstrmgr 2. To execute a long trace during the time period of 15 seconds for clinfo and send it to standard output, enter: cldiag trace -t 15 -l clinfo 3. To execute a short trace for cllockd and send it to file trc_rpt instead of standard output, enter: cldiag trace -R trc_rpt cllockd Implementation Specifics These commands are part of High Availability Cluster Multi-Processing for AIX (HACMP for AIX) Files /usr/sbin/cluster/diag/cl_diag /usr/sbin/cluster/diag/clmenu /usr/sbin/cluster/diag/cld_logfiles /usr/sbin/cluster/diag/cld_debug /usr/sbin/cluster/diag/cld_vgs /usr/sbin/cluster/diag/cld_error /usr/sbin/cluster/diag/cld_trace /usr/sbin/cluster/diag/cl_src_cmd /usr/sbin/cluster/diag/cld_getdate /usr/sbin/cluster/diag/cld_lockdump Sugested Reading HACMP for AIX Concepts and Facilities HACMP for AIX Administration Guide HACMP for AIX Troubleshooting Guide fl k6A 0i7]7P`7!vD ./usr/share/man/cat1/cllsev.11 cllsev Command ************** Purpose Lists the contents of the event ODM object class. Syntax cllsev [-i nodeName] [-h] [-o odmdir] [-f 'field..'] [-c] eventname.. Description The cllsev command lists the contents kept in the event ODM. If an event name is specified, only the contents of the event name entry will be displayed. Otherwise, the contents of all events are listed. By default, only name, event command and description fields are displayed as contents. To list other fields, specify the -f option and the field name list. Flags -i nodeName Specifies to list the event(s) from the node whose name is specified by nodeName. If not specified, list the local node. -h Prints the header first. No header is printed by default. -o odmdir Specifies the odm directly. The environment value of the ODMDIR is used by default. -f field(s) Prints the specified field(s) only. The order of printing is determined by the corresponding position(s) in the command line. If not specified, only default fields are listed. Note: only "name", "desc", "msgno", "setno", "catalog", "cmd", "notify", "pre", "post", "recv" and "count" are recognized field names. -c Requests using a colon instead of a space as field separator. eventname.. Specifies the event name(s) to look up from the event ODM. If no name is given, all events are listed. Examples: 1. To list the command field and notify field of the node_up event, to print a header as well, and to use a colon as a field separator, enter: cllsev -ch -f 'cmd notify' node_up 2. To list the description field of all events, and use the ODM in /usr/odm directory, enter: cllsev -f "desc" -o /usr/odm Implementation Specifics This command is part of High Availability Cluster Multi-Processing for AIX (HACMP for AIX). Files /usr/sbin/cluster/events/cmd/cllsev The cllsev command executable file. /etc/objrepos/HACMPevent The event ODM object class. Suggested Reading HACMP for AIX Concepts and Facilities HACMP for AIX Administration Guide Prerequisite Information Related Information The claddev, cldelev, clchev, and clcallev commands, and the clsubmitev and clpollev scripts. kDAy0i7]7P`7!eDy./usr/share/man/cat1/cllsres.1 cllsres Command *************** Purpose Retrieves node environment resources. Syntax cllsres [-g group] [-c] [-s] [-f field] [-d odmdir] [-q query] Description The cllsres command retrieves variables from the HACMP for AIX node resource ODM object class. The variables are output in UNIX shell format suitable for input to the shell. If multiple records are retrieved that specify the same variable, the values will be concatenated. For example if the ODM contains the following variables: DISK=A DISK=B DISK=C cllsres will output: DISK="A B C" The cllsres command is used by the HACMP for AIX software to retrieve variables from the ODM. It normally is not required by the user. Flags -g group Specifies the name of the resource group to list. -c Specifies that the output should be in colon format. -s When used with -c flag, specifies that the colon format will be displayed in the native language instead of English. -f field Specifies the field to retrieve from the node resource ODM object class. -d odmdir Specifies an ODM object repository directory other than the default /etc/objrepos. -q query Specifies the search criteria used to select objects from the HACMP object class. If no criteria are specified, all objects are retrieved. Example To retrieve all HACMP for AIX ODM "Node Environment" variables, enter: cllsres Information similar to the following is returned: APPLICATIONS="App3 App1 App2" DISK_FENCING="false false" INACTIVE_TAKEOVER="false false" SERVICE_LABEL="nodeA_en0 nodeB_en0" Implementation Specifics This command is part of AIX High Availability Cluster Multi-Processing for AIX (HACMP for AIX). Files /usr/sbin/cluster/utilities/cllsres The cllsres command executable file. /etc/objrepos/HACMPresource The HACMP for AIX node resource ODM object class. Suggested Reading HACMP for AIX Concepts and Facilities HACMP for AIX Administration Guide Prerequisite Information Related Information The clshowres, clrmres, and claddres commands. Prerequ k6AA90i7]7P`7!oD9./usr/share/man/cat1/clrmres.1 clrmres Command *************** Purpose Deletes resources from a resource group. Syntax clrmres [-d odmdir] [-g group] Description The clrmres command removes all resources from a resource group in the HACMP for AIX ODM node environment resource object class. Flags -d odmdir (Optional) Specifies the alternate ODM directory. -g group Specifies the resource group from which resources should be deleted. Implementation Specifics This command is part of High Availability Cluster Multi-Processing for AIX (HACMP for AIX). Do not execute this command from the command line. Use the SMIT interface as explained in the documentation. Files /usr/sbin/cluster/utilities/clrmres The clrmres command executable file. /etc/objrepos/HACMPresource The HACMP node environment ODM resource group object class. Suggested Reading HACMP for AIX Concepts and Facilities HACMP for AIX Administration Guide Prerequisite Information Related Information The cllsres, claddres, and clshowres commands. ce ODM kxA0i7]7P`7!qD./usr/share/man/cat1/clshowres.1ename. clshowres Command ***************** Purpose Shows resource group information defined for a node, group, or all groups. Syntax clshowres [-g group] [-n nodename] [-d odmdir] Description The clshowres command retrieves information from the HACMP resource ODM object class and lists the resources defined for all groups or for a given group or node. Flags -d odmdir Specifies an alternate ODM object repository directory other than the default /etc/objrepos directory. -n nodename Lists all resources related to a given node. -g groupname Specifies the name of the resource group to show. Examples 1. To list the node environment resource defined for nodeA, enter: clshowres -n nodeA 2. To list all resources defined for all groups, enter: clshowres 3. To list all resources defined for resource group grp1, enter: clshowres -g grp1 Implementation Specifics This command is part of High Availability Cluster Multi-Processing for AIX (HACMP for AIX). Files /usr/sbin/cluster/utilities/clshowres The clshowres command executable file. /etc/objrepos/HACMPresource The HACMP node resource ODM object class. Suggested Reading HACMP for AIX Concepts and Facilities HACMP for AIX Administration Guide Prerequisite Information Related Information The cllsres, clrmres, and claddres commands. ronment kLP&AD 0i7]7P`7!zDD ./usr/share/man/cat1/clsubmitev.1ename. clsubmitev Shell Script *********************** Purpose Executes (in background) the event scripts defined in event ODM object class. Syntax clsubmitev [-o odmdir] Eventname [argument..] Description The clsubmitev command takes an event name and executes all the scripts associated with the Eventname found in the event ODM. Any arguments after the Eventname are passed to all the event scripts as input (trailing arguments). This command does no argument validation check. This script works very much the same way as clcallev command, except clsubmitev executes all scripts in background. The clsubmitev command outputs the background process id and exits immediately. Upon the finishing of the background process, a file named /tmp/ps., where PID is the return background process id, will be created, and the exit status of the event handler script (command) is saved into the file. All associated scripts (commands) will be executed in the following order, if they exist: 1. notify script. It uses Eventname, `start', and is passed in trailing arguments as its own arguments. 2. pre script. It uses Eventname and is passed in trailing arguments as its own arguments. 3. event handler script. It uses Eventname and is passed in trailing arguments as its own arguments. 4. recovery script (executed only if recovery count is greater than 0, and event handler script failed). It uses Eventname and is passed in trailing arguments as its own arguments. 5. post script. It uses Eventname, exit status of event handler script, and is passed in trailing arguments as its own arguments. 6. notify script. It uses Eventname, `complete', exit status of event handler script, and is passed in trailing arguments as its own arguments. Flags -o odmdir Specifies an ODM directory other than the system default. Eventname Specifies the event name to look up in the event ODM object class. arguments Specifies the arguments which will be passed to event handler script, notify script, recovery script, and pre- and post-event scripts. Return The clsubmitev script returns 0 if it runs successfully. The clsubmitev script returns 2 if there is a bad argument. Implementation Specifics This command is part of AIX High Availability Cluster Multi-Processing for AIX (HACMP for AIX). Do not run this script from the command line. Use the SMIT interface as explained in the documentation. Files /usr/sbin/cluster/events/cmd/clsubmitev The clsubmitev script file. /etc/objrepos/HACMPevent The event ODM object class. Suggested Reading Prerequisite Information Related Information The cllsev command, claddev command, clchev command, cldelev command, clcallev command, and clpollev script. Z k-A0i7]7P`7!D./usr/share/man/cat1/convaryonvg.1name. convaryonvg Command ******************* Purpose Varies on an IBM Disk Array device volume group, permitting concurrent access in a concurrent access HACMP configuration. Syntax convaryonvg volume_group Description The convaryonvg command performs the equivalent function of varyonvg(1), but permits concurrent (shared) access to the volume group by other cluster nodes. This command is used by a concurrent access shared data-base environment. Each node should perform convaryonvg, rather than varyonvg. Disk device reservations are not made as they normally are; instead, data integrity of a volume group(s) exposed by shared access is the responsibility of the application environment. Volume groups made available by using this command can be made unavailable by using the standard varyoffvg(1) command. Flags The flags, return codes, and messages are those of the varyonvg command. Implementation Specifics This command is part of High Availability Cluster Multi-Processing for AIX (HACMP for AIX). Files /usr/sbin/cluster/events/utils/convaryonvg executable shell script /usr/sbin/cluster/events/utils/scdiskutil disk utility program to hold disks open /usr/sbin/varyonvg standard system command Suggested Reading HACMP for AIX Concepts and Facilities HACMP for AIX Administration Guide Prerequisite Information Related Information The varyonvg command, varyoffvg command traili k!A 0i7]7P`7!wD ./usr/share/man/cat1/clcallev.1 clcallev Command **************** Purpose Executes (in the foreground) the scripts associated with the event defined in event ODM object class. Syntax clcallev [-i nodeName] [-o odmdir] Eventname [argument..] Description The clcallev command takes an event name from the command line and executes all scripts associated with the Eventname found in the HACMPevent ODM object class. Any arguments after the Eventname are passed to event scripts as input (trailing arguments). This command does no argument validation check. All associated scripts (commands) will be executed in the following order: 1. notify script. The first argument is the Eventname, 'start', followed by all arguments passed to that event. The script is executed in background. 2. pre-script. The first argument is the Eventname, 'start', followed by all arguments passed to that event. 3. event handler script. The first argument is the Eventname, 'start', followed by all arguments passed to that event. 4. recovery script (executed only if recovery count is greater than 0, and event handler script fails). The first argument is the Eventname, 'start', followed by all arguments passed to that event. If the recovery script fails, see step 5, else go to step 3. 5. post-script. The first argument is the Eventname, exit status of event handler script, followed by all arguments passed to that event. 6. notify script. The first argument is the Eventname, 'complete', exit status of event handler script, followed by all arguments passed to that event. The script is executed in the background. If the -i option is specified and if nodeName is not equal to the local node name, then all event scripts associated with Eventname (found on the remote node) must also exist on the local node and must be accessible using the same path name used to access the event scripts on the remote node. Flags -i nodeName Specifies to look up event ODM object class from remote node, whose name is specified by nodeName. If not specified, look up from local node. -o odmdir Specifies an odm directory other than the default environment value of ODMDIR. Eventname Specifies the event name to look up in the event ODM object class. arguments Specifies the arguments to be passed to event, notify, recovery, and pre- and post-event scripts. Implementation Specifics This command is part of High Availability Cluster Multi-Processing for AIX (HACMP for AIX). Files /usr/sbin/cluster/events/cmd/clcallev The clcallev command executable file. /etc/objrepos/HACMPevent The event ODM object class. Suggested Reading HACMP for AIX Concepts and Facilities HACMP for AIX Administration Guide Prerequisite Information Related Information The cllsev, claddev, clchev, and cldelev commands, and the clsubmitev and clpollev scripts. / kN A0i7]7P`7!bD./usr/share/man/cat1/clchserv.1 clchserv Command **************** Purpose Changes the existing application server in the ODM object class HACMPserver. Syntax clchserv -o old-server_name [-s server_name] [-b start_script] [-e stop_script] [-d odmdir] Description The clchserv command changes an existing application server. If server-name or start-script or stop-script is not specified, the old value is preserved. clchserv changes the local server ODM object class HACMPserver. So you need to re-sync the cluster via the Synchronize Cluster Resources SMIT screen to propogate the change to remote nodes. Flags -d odmdir Specifies an alternative directory in which to search for the file containing the object class. The default is /etc/objrepos. -o old_server_name Specifies the old application server name. -s server_name Specifies the new name of the application server. -b start_script Specifies the new script to start the application server. -e stop_script Specifies the new script to stop the application server. Implementation Specifics This command is part of AIX High Availability Cluster Multi-Processing for AIX (HACMP for AIX). Do not run this command from the command line. Use the SMIT interface as explained in the documentation. Files /usr/sbin/cluster/utilities/clchserv The clchserv executable file. /etc/objrepos/HACMPserver The application server ODM object class. Suggested Reading HACMP for AIX Concepts and Facilities HACMP for AIX Administration Guide Prerequisite Information Related Information The cllsserv, claddserv,and clrmserv commands. t kA0i7]7P`7!tD./usr/share/man/cat1/cldelev.1 cldelev Command *************** Purpose Deletes event information from the event ODM object class. Syntax cldelev [-i nodename] [-o odmdir] Eventname [Eventname...] OR: cldelev [-i nodename] -a [-o odmdir] Description The cldelev command deletes the event entry in the event ODM. If an event name is given, only the entry associated with the specified event name will be deleted. To delete all the events from the event ODM, specify the -a option. WARNING: Use the -a option with caution. Flags -i nodename Specifies the name of the node from which to remove event. If not specified, only removes from local node. -a Deletes all entries from the event object class. -o odmdir Specifies an ODM directory other than the default environment value of ODMDIR. Eventname Deletes the Eventname entry from the event object class. Implementation Specifics This command is part of High Availability Cluster Multi-Processing for AIX (HACMP for AIX). Do not run this command from the command line. Use the SMIT interface as explained in the documentation. Files /usr/sbin/cluster/cldelev The cldelev command executable file. /etc/objrepos/HACMPevent The event ODM object class. Suggested Reading HACMP for AIX Administration Guide Prerequisite Information Related Information The cllsev command, claddev command, clchev command, clcallev command, clsubmitev script, and clpollev script. k1A0i7]7P`7!lD./usr/share/man/cat1/cllsfs.1 cllsfs Command ************** Purpose Lists the shared file system(s), i.e. the file systems which are accessible by all participating nodes in a resource group. If no resource group is given, then for each configured resource group the command lists the resource group name along with their shared file systems. Syntax cllsfs [-g resource group] [-n] Description The cllsfs command retrieves a list of file systems shared by nodes in a resource group and prints information on these file systems. A file system is considered shared if it is accessible by all participating nodes in a configured resource group. Note that the file systems listed may or may not be configured as a resource in the resource group. Flags -g resource group Specifies the name of the resource group for which to list file systems that are shared amongst participating nodes. -n Lists the nodes that share the file system in resource group. Examples 1. To list all the file systems accessible by all nodes participating in a resource group named grp1, enter: cllsfs -g grp1 2. To list all the file systems accessible by all the configured resource groups, along with the names of the participating nodes in each configured resource group, enter: cllsfs -n Implementation Specifics This command is part of High Availability Cluster Multi-Processing for AIX (HACMP for AIX). Files /usr/sbin/cluster/utilities/cllsfs The cllsfs command executable file. Suggested Reading HACMP for AIX Concepts and Facilities HACMP for AIX Administration Guide Prerequisite Information Related Information The cllslv command, cllsvg command and cllsdisk command.  kHVAT0i7]7P`7!nDT./usr/share/man/cat1/cllsserv.1 cllsserv Command **************** Purpose Lists application servers. Syntax cllsserv [-c] [-h] [-n name] [-d odmdir] Description The cllsserv command lists application servers defined in the HACMP server ODM object class. The output can be printed in a colon format suitable for SMIT. Flags -c Specifies to print the output in colon format. -h Specifies to print the header first in the output. -n name Specifies to only search for the application server with the specified name. -d odmdir Specifies an alternative ODM object repository instead of the default /etc/objrepos directory. Examples 1. To list all the servers defined in the server ODM object class, enter: cllserv 2. To show the definition of a server called foo and format the with colon separators, enter: cllsserv -c -n foo Implementation Specifics This command is part of High Availability Cluster Multi-Processing for AIX (HACMP for AIX). Files /usr/sbin/cluster/utilities/cllsserv The cllsserv command executable file. /etc/objrepos/HACMPserver The application server ODM object class file. Suggested Reading HACMP for AIX Concepts and Facilities HACMP for AIX Administration Guide Prerequisite Information Related Information The claddserv, clchserv, and clrmserv commands. is c k #A0i7]7P`7!yD./usr/share/man/cat1/clpollev.1 clpollev Shell Script ********************* Purpose Polls the outstanding event(s) submitted by the clsubmitev script. Syntax clpollev pid Description The clpollev script takes a process id returned from the clsubmitev script and checks the file's (/tmp/ps.PID) existence. The file contains the return status of an event handler script (command) submitted by clsubmitev. Flags pid Specifies the process id returned from clsubmitev script. Returns The clpollev script exits with a status of 0, outputs the exit status of the event handler script from /tmp/ps.PID, and removes /tmp/ps.PID file. The clpollev script exits with a status of 1 if the event handler script has not yet finished (/tmp/ps.PID does not exist). The clpollev script exits with a status of 2 if the argument count is not 1. Example To poll the event submitted by clsubmitev, first get the return process id from clsubmitev script, then enter: clpollev pid Implementation Specifics This command is part of High Availability Cluster Multi-Processing for AIX (HACMP for AIX). Files /usr/sbin/cluster/events/cmd/clpollev The clpollev script file. /etc/objrepos/HACMPevent The event ODM object class. Suggested Reading HACMP for AIX Concepts and Facilities Prerequisite Information Related Information The cllsev, claddev, clchev, cldelev, and clcallev commands, and the clsubmitev script. . Su k@9Af0i7]7P`7!hDf./usr/share/man/cat1/clrmserv.1 clrmserv Command **************** Purpose Removes an application server from the server ODM database. Syntax clrmserv [-d odmdir] { server-name | All } Description The clrmserv command removes an application server from the HACMP ODM server object class. The command removes the server from both the local ODM and from defined remote nodes in the cluster. The local node's hostname must be added to the /.rhosts and /etc/hosts files on the local node, as well as on remote nodes in the cluster. The godm server must be running in order for this command to run correctly. Flags server-name Specifies the server name to remove. All Specifies to remove all application servers. -d odmdir Specifies the alternate ODM directory. Implementation Specifics This command is part of High Availability Cluster Multi-Processing for AIX (HACMP for AIX). This program should not be run from the command line. Use the SMIT interface as explained in the documentation. Files /usr/sbin/cluster/utilities/clrmserv The clrmserv executable command file. /etc/objrepos/HACMPserver The application server ODM object class. Suggested Reading HACMP for AIX Concepts and Facilities HACMP for AIX Administration Guide Prerequisite Information Related Information The cllsserv, claddserv, and clchserv commands. es kDAf0i7]7P`7!ZDf./usr/share/man/cat1/clshowsrv.11name. clshowsrv Command ***************** Purpose Shows status of HACMP subsystems. Syntax clshowsrv { -a | subsystem [subsystem2...] } Description The clshowsrv command displays the status of HACMP subsystems. Status includes subsystem name, group name, process ID, and status. The status of a daemon is either active or inoperative. Process IDs are only displayed for active daemons. Flags -a Displays all HACMP daemons. subsystem Shows the status of the given HACMP subsystem. Valid values are clstrmgr, clinfo, cllockd, and clsmuxpd. When more then one is entered, separate them by a space. Examples 1. To display the status of all HACMP for AIX subsystems, enter: clshowsrv -a 2. To display the status of the clstrmgr subsystem, enter: clshowsrv clstrmgr 3. To display the status of the clstrmgr and cllockd subsystems, enter: clshowsrv clstrmgr cllockd Implementation Specifics This command is part of High Availability Cluster Multi-Processing for AIX (HACMP for AIX). Files /usr/sbin/cluster/utilities/clshowsrv The clshowsrv command executable file. Suggested Reading HACMP for AIX Concepts and Facilities HACMP for AIX Administration Guide HACMP for AIX Troubleshooting Guide Prerequisite Information Related Information The lssrc and mkssys commands. es k 'A0i7]7P`7!|D./usr/share/man/cat1/clverify.1 clverify Command **************** Purpose Top level command to verify that the necessary HACMP-specific modifications to AIX system files exist and are correct, and that the cluster configuration is correct and consistent. Syntax clverify [software] [cluster] Description clverify gives the user access to the top level menu for verifying that an HACMP for AIX cluster is properly configured. A list of options are presented to the user. These options are: software and cluster. The options can also be specified on the command line. These options then give the user access to more menu picks that verify different parts of the HACMP for AIX system. clverify software Subcommand Purpose Verify that all necessary HACMP-specific modifications to AIX system files exist and are correct. Syntax clverify software [lpp] Description clverify software is used to verify that all of the HACMP-specific modifications to AIX system files exist and are correct for running HACMP for AIX. Flags lpp Verify that the HACMP-specific modifications to AIX system files exist and are correct. -R Redirects output to a log file. clverify cluster Subcommand Purpose Verify that a cluster has been properly configured. Syntax clverify cluster [config] [topology] Description clverify cluster is used to verify that the cluster environment has been properly configured. This means that all cluster nodes agree on the topology of the cluster, and configured resources are reachable by the proper nodes in the cluster. A list of options are presented to the user. These options are: config and topology. The options can be specified on the command line. Flags config Verifies that the network devices and shared resources are properly configured. Options: resources Verifies resource ownership and takeover distribution amongst cluster nodes. networks Verifies that network resources are properly configured throughout the cluster. all Verifies the cluster's network topology, resources, and custom methods. Note: All clverify cluster config options support an -e error_count flag. This flag allows the user to specify the maximum number of errors to display before exiting. (The topology option does not support the -e flag.) topology Verifies that all cluster nodes agree on the cluster topology. Options: check Check to see if all nodes are in agreement on the cluster's topology. sync Force all nodes in the cluster to agree with topology on local node. Note: All clverify options support an -R file_name flag to generate error reports to the named file. Examples 1. To verify that all cluster nodes agree on cluster topology enter: clverify cluster topology check 2. To verify that the proper HACMP-specific modifications to AIX system files are correct and place the results in a file called HACMP_INST, enter: clverify software lpp -R HACMP_INST Implementation Specifics These commands are part of High Availability Cluster Multi-Processing for AIX (HACMP for AIX). Files /usr/sbin/cluster/diag/clmenu executable for the menu driver /usr/sbin/cluster/diag/clver executable for verifying cluster resources. /usr/sbin/cluster/diag/configchk executable for verifying cluster topology /usr/sbin/cluster/diag/clvhacmp executable for verifying HACMP LPP /usr/sbin/cluster/diag/clvbos executable for verifying AIX level /usr/sbin/cluster/diag/clvreq executable for verifying required PTF installation /usr/sbin/cluster/diag/clvinval executable for verifying installation of invalid PTFs Suggested Reading HACMP for AIX Concepts and Facilities HACMP for AIX Administration Guide HACMP for AIX Installation Guide For HACMP/ES: HACMP for AIX Enhanced Scalability Installation and Administration Guide k.)A0i7]7P`7!D./usr/share/man/cat1/godmd.1.1 godmd Command ************* Purpose Daemon responsible for handling global ODM cluster information requests. Syntax godmd Description This command is started by the inetd script when a GODM client requests a session. It is configured in the /etc/inetd.conf file and should never be started from the command line. It retrieves information from the local RISC System/6000's ODM and passes it back to authorized clients. Implementation Specifics This command is part of AIX High Availability Cluster Multi-Processing for AIX (HACMP for AIX). Files /usr/sbin/cluster/godmd Executable for the godmd daemon /etc/inetd.conf inetd configuration file Prerequisite Information inetd Manual kꚢA0i7]7P`7!_D./usr/share/man/cat1/cl_nfskill.1name.cl_nfskill Command ****************** Purpose Identifies processes using an NFS directory. Syntax cl_nfskill [-k] [-u] [-t] Directory ... Description The cl_nfskill command lets only the root user list the process numbers of local processes that use the NFS directory specified by the Directory parameter. Each process number is followed by a letter indicating how the process uses the file: c Uses the directory as the current directory. f Has a file open in the directory. r The process' root directory is on the filesystem. e The process is executed on the filesystem. t The process uses a library on the filesystem. o The process has an open in progress on the filesystem. The process numbers are written to the standard output, in a line with spaces between process numbers. The line ends with a single new line character. All other output is written to the standard error. Flags -k Sends the SIGKILL signal to each local process. Only the root user can kill a process of another user. -u Provides the login name for local processes in parentheses after the process number. -t Finds and kills processes which are just opening an NFS filesystem. If you specify the -t flag, all processes that have certain NFS module names within their stack will be killed. CAUTION: When using the -t flag it is not possible to tell which NFS filesystem the process is related to. This could result in killing processes which belong to NFS mounted filesystems other than those which are cross-mounted from another HACMP node and under HACMP control. Also, the processes found could be related to filesystems under HACMP control but not part of the current resources being taken. The -t flag, therefore, should be used with caution and only if you know you have a specific problem with unmounting the NFS filesystems. The cl_deactivate_nfs script contains the normal calls to cl_nfskill with the -k and -u flags, as well as commented calls using the -t flag. If you choose to use the -t flag, you should uncomment these calls and comment the original calls. Examples 1. To list the process numbers of local processes using the /home NFS directory, enter: cl_nfskill /home 2. To list the process numbers and user login names of processes using the /home NFS directory, enter: cl_nfskill -u /home 3. To stop (send SIGKILL) all of the processes using the /home NFS directory, enter: cl_nfskill -k -u /home 4. To stop (send SIGKILL) all of the processes using the /home NFS directory, and including all processes with NFS filesystem opens in progress, enter: cl_nfskill -k -u -t /home This command lists the process number and user name; then it stops each process using the /home directory. As root, you can stop processes that belong to another user. Use this command if you are trying to unmount the /home directory and one or more processes using the /home directory is preventing you from doing so. Implementation Specifics This command is part of High Availability Cluster Multi-Processing for AIX (HACMP for AIX). Files /usr/sbin/cluster/events/utils/cl_nfskill The cl_nfskill command executable. /dev/mem Used for the system image. Suggested Reading HACMP for AIX Concepts and Facilities HACMP for AIX Administration Guide Prerequisite Information Related Information The fuser, kill, killall, mount, and ps commands. @ kA 0i7]7P`7!]D ./usr/share/man/cat1/clsmuxpd.1clsmuxpd Command **************** Purpose Cluster SNMP peer agent Syntax clsmuxpd [-s uSecs] [-e MaxEventCount] [-T] Description The clsmuxpd daemon provides enterprise specific MIB-II information for HACMP for AIX. It allows any SNMP browsers with access to the cluster node to obtain cluster topology information. The clsmuxpd daemon communicates directly with the clstrmgr to track cluster, node, network, and adapter information; it also communicates with the System Resource Controller to track all cluster daemon process status information. Flags -s uSecs Specifies the amount of time to wait, in microseconds, for the System Resource Controller to return process status information for the cluster daemons under its control. Default is 1,000,000 uSecs or 1 second. -e MaxEventCount Specifies the maximum number of topology events saved in a buffer for retrieval via SNMP. Default is 1000. -T Enables tracing of the daemon without having to use the System Resource Controller. Examples Do not run this command from the command line, Use the SMIT interface as explained in the documentation (use the clstart and clstop commands). Implementation Specifics This command is part of High Availability Cluster Multi-Processing for AIX (HACMP for AIX). Files /usr/sbin/cluster/clsmuxpd The clsmuxpd command executable file. /usr/sbin/cluster/hacmp.defs The HACMP for AIX SNMP object definitions. Suggested Reading HACMP for AIX Concepts and Facilities HACMP for AIX Administration Guide HACMP for AIX Installation Guide HACMP for AIX Programming Client Applications Prerequisite Information Familiarity with SNMP Related Information The clinfo, clstart, and clstop commands, and the clhosts file. k([@D0i7]7P`7!ED./usr/share/man/cat1/clstrmgr.1 clstrmgr Command **************** Purpose Starts Cluster Manager daemon. Syntax clstrmgr [-d] Description The clstrmgr command invokes the Cluster Manager process. The clstrmgr provides a facility through which applications and different network nodes can participate in a distributed system. The clstrmgr command is normally started automatically as part of system initialization through the file /usr/sbin/cluster/etc/rc.cluster, or manually through the SMIT interface via "smit clstart". The clstrmgr controls resources that are considered "cluster resources". This includes any network adapters, shared disks, High Availability servers, and software sub-systems. The clstrmgr uses a set of network adapters to communicate, while at the same time monitoring the health of these adapters. If a node has two or more adapters connected to the same physical network, one of these adapters will be chosen (at configuration time by the user) as the service interface with an optional boot interface; the rest will be standby. If a service interface has 1 or more standby interfaces, the clstrmgr is able to swap the IP addresses between the adapters should the service interface fail. The result is that users will be unaware of a network adapter failure. There can be only one clstrmgr process on each machine. A clstrmgr process will attempt to communicate with clstrmgr processes on other machines described in the cluster configuration. This communication is done over UDP sockets. The clstrmgr processes on each participating node send "keep-alive" messages to each other. The Cluster Manager protocol uses these messages to determine all node and network failures. All active Cluster Managers must agree on an event, such as a node failing, before any action can be taken. Whenever an event happens, the Cluster Managers respond by running a configuration script. There are a number of these scripts, one for each event that the clstrmgr generates. These scripts in turn call other scripts, which perform specific tasks like releasing shared disk resources. These scripts are completely user configurable; sample scripts are included in the HACMP for AIX distribution. If the stdin for the clstrmgr is a terminal, it forks and enters daemon mode. Otherwise, the clstrmgr operates in the foreground. Foreground operations facilitate control by the System Resource Controller. Cluster Configuration The clstrmgr command depends on the cluster configuration for information regarding nodes that are potential cluster members. This information is stored in the ODM in HACMP-defined classes. Various SMIT screens are used to enter this information. Since HACMP has a facility for accessing a node's ODM remotely, the configuration for the entire cluster can be entered from a single node and then sync'd to all other names in the cluster. Flags -d Debug option. This feature is used by system developers and is not supported for normal operation. Failsafe Protection The clstrmgr makes use of an HACMP-supplied kernel extension which causes the system to panic if the clstrmgr is somehow kept from running for more than five seconds at a time. This 'failsafe' is enabled when the clstrmgr first starts, and is disabled when the clstrmgr exits normally. Thus it is important not to terminate the cluster manager in an abnormal way, for example via a 'kill -9' command or the system may panic. Example The clstrmgr command is normally executed through SMIT using the SMIT clstart command. Implementation Specifics This command is part of AIX High Availability Cluster Multi-Processing for AIX (HACMP for AIX). Files /usr/sbin/cluster/clstrmgr The clstrmgr command executable file. /usr/sbin/cluster/events The directory containing predefined scripts. /tmp/hacmp.out Log file for scripts run by the clstrmgr. [default location listed] /usr/adm/cluster.log Syslog file for errors from cluster daemons. [default location listed] /usr/sbin/cluster/history/cluster.mmdd Log files containing a list of the events generated by the cluster manager on mm/dd (month/day). [default location listed] /usr/sbin/cluster/clruncmd The clruncmd executable file used to force the clstrmgr to continue after a configuration script has failed. Suggested Reading HACMP for AIX Concepts and Facilities HACMP for AIX Installation Guide Prerequisite Information Related Information The clinfo command, cllockd command, clsmuxpd command and clruncmd command. lust k@0i7]7P`7!=D./usr/share/man/cat1/cllockd.1cllockd Command *************** Purpose Cluster Lock Manager daemon Syntax cllockd [-F dumpfilename] [-M heap_percentage] [-D decay_rate] [-r recalculation_rate] Description The cllockd daemon provides a cluster-wide locking facility to client programs. An instance of cllockd runs on each participating node in a cluster. The cllockd daemon will terminate if a Cluster Manager daemon (clstrmgr) is not running on the local node. If the local clstrmgr terminates, the cllockd daemon will exit. If the stdin to the cllockd is a terminal, it will fork and enter daemon mode. Otherwise, the cllockd will operate in the foreground. This facilitates control by the System Resource Controller. Flags -F dumpfilename Specifies the file to be used if the lock manager is instructed to dump its resource state table. The default filename is /tmp/lockdump. -M heap_percentage Specifies the maximum percentage of the kernel heap that the Cluster Lock Manager will use before clearing lock requests. -D decay_rate Specifies the migration decay rate as described in Chapter 1 of the HACMP for AIX Programming Locking Applications manual. -r recalculation_rate Specifies the migration evaluation frequency as described in Chapter 6 of the HACMP for AIX Programming Locking Applications manual. Examples Do not run this command from the command line. Use the SMIT interface as explained in the documentation. Implementation Specifics This command is part of High Availability Cluster Multi-Processing for AIX (HACMP for AIX). Files /usr/sbin/cluster/cllockd The cllockd command executable file. /usr/sbin/cluster/cllockd.x The cllockd kernel extension. /usr/sbin/cluster/clm_loader The cllockd loader program. /usr/sbin/cluster/clm_stop The executable that stops the Lock Manager. /usr/lib/libclm.a The lock manager API library. /usr/lib/libclm_r.a The lock manager threadsafe API library. Suggested Reading HACMP for AIX Concepts and Facilities HACMP for AIX Administration Guide HACMP for AIX Programming Locking Applications Related Information The clstrmgr, clstart, and clstop commands. k@T 0i7]7P`7!>DT ./usr/share/man/cat1/clstart.1 clstart Command *************** Purpose Starts Cluster Manager, Cluster Information, Cluster Lock Manager, Cluster Resource Manager (HACMP/ES only),and Cluster SMUX Peer daemons. Syntax clstart [-m | -ml] [-s] [-b] -i -l -r Description The clstart command starts the cluster daemons by using the System Resource Controller facility. Caution should be applied if using this command directly instead of going through the SMIT screen to start cluster services on a cluster node. There is preprocessing done in the rc.cluster script which, if not done, could cause the cluster to function unpredictably. Note: Although the cluster daemons can run standalone, the cllockd daemon will eventually time out unless all the other daemons are active. Thus, start the cllockd with the clstrmgr. Flags -m starts the cluster manager (clstrmgr) daemon. -s starts the cluster SMUX peer (clsmuxpd) daemon. -b broadcasts startup messages. The default is not to broadcast. -i starts the cluster information (clinfo) daemon. -l starts the lock manager (cllockd) daemon. -r starts the cluster resource manager (HACMP/ES only) Examples 1. To start the Cluster Manager, enter: clstart -m 2. To start the Cluster Manager with a broadcast message telling users that the Cluster Manager processes have been started, enter: clstart -m -b 3. To start the Cluster Manager and the Cluster Lock Manager, enter: clstart -ml Note: The clstrmgr, clsmuxpd, and clinfo daemons must be started for the cllockd daemon to run. 4. To start all the daemons with a broadcast message telling users what has been started, enter: clstart -b -i -l -m -s Implementation Specifics This command is part of High Availability Cluster Multi-Processing for AIX (HACMP for AIX). Files /usr/sbin/cluster/utilities/clstart The clstart command executable script. /usr/sbin/cluster/etc/rc.cluster The cluster startup script. Suggested Reading HACMP for AIX Concepts and Facilities HACMP for AIX Administration Guide HACMP for AIX Enhanced Scalability Installation and Administration Guide Prerequisite Information Related Information The rc.cluster, clstop, clstrmgr, clinfo, cllockd, clRMupdate, clRGinfo, and clsmuxpd commands. for k@P0i7]7P`7!CDP./usr/share/man/cat1/claddclstr.1name. claddclstr Command ****************** Purpose Adds a cluster stanza to the cluster configuration ODM object class HACMPcluster. Syntax claddclstr -i id -n name Description The claddclstr command sets up the cluster stanza (definition) in the HACMPcluster ODM object class. Flags -i id A unique integer from 1 to 999,999,999. -n name An alphanumeric string of up to 31 characters that uniquely identifies the cluster. Implementation Specifics This command is part of High Availability Cluster Multi-Processing for AIX (HACMP for AIX). Do not run this command from the command line. Use the SMIT interface as explained in the documentation. Files /usr/sbin/cluster/utilities/claddclstr The claddclstr command executable file. /etc/objrepos/HACMPcluster HACMPcluster ODM object class. Suggested Reading HACMP for AIX Concepts and Facilities HACMP for AIX Administration Guide Prerequisite Information Related Information The clchclstr, cllsclstr, and cllscf commands. kX@b0i7]7P`7!EDb./usr/share/man/cat1/claddnode.1name. claddnode Command ***************** Purpose Adds adapter entry to the adapter ODM object class HACMPadapter. Syntax claddnode [-n name] -a adapter:net-type:net-name:attr:func: [ipaddr|device-file]:[hwaddr] Description Adds an adapter stanza to the HACMPadapter ODM object class. Flags -n name Specifies the name of the node that will acquire the address (associated with the adapter) on its service adapter. -a adapter:net-type:net-name:attr:func:[ipaddr|device-file]:[hwaddr] Specifies an adapter to be included in the node stanza as well as the values needed in the associated adapter stanza(s). Only one -a clause can be entered on the command line per adapter on the node. adapter The IP label of the adapter being added to the node. net-type The type of network to which an adapter is being added. (ethernet or RS232) net-name The network name of the network connected to the adapter. This is a user-defined field. attr The network attribute. Valid values are public, private (point-to-point), or serial. func The adapter function. Valid values are service, standby, and boot. ipaddr|device-file The adapter IP address or device file for a specified host. This is only required if the adapter name cannot be resolved into an address. hwaddr The hardware address of the adapter being added. Implementation Specifics This command is part of High Availability Cluster Multi-Processing for AIX (HACMP for AIX). Do not run this command from the command line. Use the SMIT interface as explained in the documentation. Files /usr/sbin/cluster/utilities/claddnode The claddnode command executable file. /etc/objrepos/HACMPadapter The adapter configuration ODM object class. Suggested Reading HACMP for AIX Concepts and Facilities HACMP for AIX Administration Guide HACMP for AIX Installation Guide Prerequisite Information Related Information The clchnode, clrmnode, cllsnode, and cllscf commands. strati kQ@0i7]7P`7!FD./usr/share/man/cat1/clchclstr.1name. clchclstr Command ***************** Purpose Changes cluster stanza in the cluster configuration ODM object class. Syntax clchclstr -i Id -n ClusterName Description Changes the cluster definition in the cluster configuration ODM /etc/objrepos/HACMPcluster. Unless specified as an argument, the current values (id and cluster name) remain unchanged. Flags -i id A unique integer from 1 to 999,999,999. -n ClusterName An alphanumeric string of up to 31 characters that uniquely identifies the cluster. Implementation Specifics This command is part of High Availability Cluster Multi-Processing for AIX (HACMP for AIX). Do not run this command from the command line. Use the SMIT interface as explained in the documentation. Files /usr/sbin/cluster/utilities/clchclstr The clchclstr command executable file. /etc/objrepos/HACMPcluster The cluster configuration ODM object class. Suggested Reading HACMP for AIX Concepts and Facilities HACMP for AIX Administration Guide HACMP for AIX Installation Guide Prerequisite Information Related Information The claddclstr, cllsclstr, and cllscf commands. ip k`@Z 0i7]7P`7!GDZ ./usr/share/man/cat1/clchnode.1 clchnode Command **************** Purpose Changes adapter stanzas in the ODM object class HACMPadapter. Syntax clchnode [-n name] -a adapter:[newadapter]:[net-type]:[net-name]: [attr]:[func]:ipaddr|device-file:[hwaddr] Description The clchnode command changes attributes defined in a node stanza in the adapter configuration ODM (/etc/objrepos/HACMPadapter); if specified, it also changes associated adapter stanza values. Only values entered are changed. Flags -n name Specifies the name of the node that will acquire the address (associated with the adapter) on its service adapter. -a adapter:[newadapter]:[net-type]:[net-name]:[attr]:[func]: ipaddr|device-file:[hwaddr] Specifies the changes to an adapter to be included in the node stanza as well as the values needed in the associated adapter stanza(s). Only one -a clause can be entered on the command line per adapter on the node. Note: All fields are optional except ipaddr. newadapter The new IP label of an adapter. net-type The network type (ethernet or RS232). net-name The network name of the network connected to the adapter. This is a user-defined field. attr The network attribute. Valid values are public, private (point-to-point), or serial. func The adapter function. Valid values are service, standby, and boot. ipaddr|device-file The new adapter internet address. This address is only required if the new adapter label cannot be resolved into an address. You can also specify the device-file in this file. hwaddr The hardware address for the new node. Implementation Specifics This command is part of AIX High Availability Cluster Multi-Processing for AIX (HACMP for AIX). Do not run this command from the command line. Use the SMIT interface as explained in the documentation. Files /usr/sbin/cluster/utilities/clchnode The clchnode command executable file. /etc/objrepos/HACMPadapter The adapter configuration ODM object class. Suggested Reading HACMP for AIX Concepts and Facilities HACMP for AIX Administration Guide Prerequisite Information Related Information The claddnode, clrmnode, cllsnode, and cllscf commands. round. kt9@0i7]7P`7!HD./usr/share/man/cat1/cllscf.11 cllscf Command ************** Purpose List cluster topology information. Syntax cllscf Description The cllscf command lists the cluster topology information as defined in the cluster, network, and adapter configuration ODM object classes. This command summarizes information stored in the /etc/objrepos/HACMPcluster, /etc/objrepos/HACMPnetwork, and /etc/objrepos/HACMPadapter object classes. Example To show the cluster information defined in the default or active cluster configuration, enter: cllscf Implementation Specifics This command is part of High Availability Cluster Multi-Processing for AIX (HACMP for AIX). Files /usr/sbin/cluster/utilites/cllscf The cllscf command executable file. /etc/objrepos/HACMPcluster The cluster configuration ODM class. /etc/objrepos/HACMPnetwork The network configuration ODM class. /etc/objrepos/HACMPadapter The adapter configuration ODM class. Suggested Reading HACMP for AIX Concepts and Facilities HACMP for AIX Administration Guide Prerequisite Information Related Information The cllscf command, cllsclstr command, cllsif command, cllsnode command, and cllsnw command. ef th kʘ@{0i7]7P`7!ID{./usr/share/man/cat1/cllsclstr.1name. cllsclstr Command ***************** Purpose Shows cluster name, id, and security mode in the cluster configuration ODM object class, given either the cluster id or no arguments. Syntax cllsclstr [-i Id] Description Shows cluster definition (name, id, security mode) in the cluster configuration ODM (/etc/objrepos/HACMPcluster). Flags -i Id Specifies cluster id to show. If no id is specified, the cluster name and id will be the cluster of which the node is a member. Example To show the cluster definition as configured for cluster 2, enter: cllsclstr -i 2 Implementation Specifics This command is part of High Availability Cluster Multi-Processing for AIX (HACMP for AIX). Files /usr/sbin/cluster/utilities/cllsclstr The cllsclstr command executable file. /etc/objrepos/HACMPcluster The cluster configuration ODM object class. Suggested Reading HACMP for AIX Concepts and Facilities HACMP for AIX Administration Guide Prerequisite Information Related Information The cllsnw command, cllsnode command, cllsif command, cllscf command. mand, kJ@G0i7]7P`7!JDG./usr/share/man/cat1/cllsif.1.1 cllsif Command ************** Purpose Shows adapter information. Syntax cllsif [-n IPlabel] [-i nodename] [-x] Description Shows adapter information from the adapter configuration ODM object class (/etc/objrepos/HACMPadapter) for either all defined adapters in the file or for a specified adapter. Flags -n IPlabel Specifies the IP label of the adapter to show. -i nodename Specifies the node name - all adapters defined for this node are shown. -x Lists only adapter labels defined for the node. No additional adapter attributes are listed. Examples 1. To show information about the adapter labeled foo, enter: cllsif -n foo 2. To show information about all the adapters on nodeA, enter: cllsif -i nodeA 3. To list the labels of adapters on nodeA, enter: cllsif -i nodeA -x Implementation Specifics This command is part of High Availability Cluster Multi-Processing for AIX (HACMP for AIX). Files /usr/sbin/cluster/utilities/cllsif cllsif command executable file /etc/objrepos/HACMPadapter adapter configuration ODM object class Suggested Reading HACMP for AIX Concepts and Facilities HACMP for AIX Administration Guide Prerequisite Information Related Information The cllscf, cllsclstr, cllsnode, and cllsnw commands. c ky@0i7]7P`7!MD./usr/share/man/cat1/cllsnode.1 cllsnode Command **************** Purpose Shows node information. Syntax cllsnode [-i nodename] Description Shows all information from adapter and network configuration ODM classes. Flags -i nodename Specifies name of node for which to show information. Examples 1. To show information for all configured nodes, enter: cllsnode 2. To show information for node1, enter: cllsnode -i node1 NODE Node1: Interfaces to network Ethernet1 Boot Interface: Name node1_boot, Attribute public, IP address 192.168.0.65 Service Interface: Name node1_svc, Attribute public, IP address 192.168.0.1 Standby Interface: Name node1_standby, Attribute public, IP address 192.168.1.1 Interfaces to network Serial1 Service Interface: Name node1_rs232, Attribute serial, IP address /dev/tty0 Implementation Specifics This command is part of High Availability Cluster Multi-Processing for AIX (HACMP for AIX). Files /usr/sbin/cluster/utilities/cllsnode The cllsnode command executable file. /etc/objrepos/HACMPadapter The adapter configuration ODM object class. /etc/objrepos/HACMPnetwork The network configuration ODM object class. Suggested Reading HACMP for AIX Concepts and Facilities HACMP for AIX Administration Guide Prerequisite Information Related Information The cllscf, cllsif, cllsclstr, cllsnw, claddnode commands. ues a k@0i7]7P`7!PD./usr/share/man/cat1/cllsnw.11 cllsnw Command ************** Purpose Shows network information for a cluster. Syntax cllsnw [-n network name] Description Shows network information defined in the adapter and network configuration ODM object classes (HACMPadapter and HACMPnetwork) for either all defined networks or for a specified network. Flags -n network name Specifies which network's information should be displayed, name is the user-defined network name. Examples 1. To show all networks, enter: cllsnw Sample output: Network Attribute Node Adapter(s) Ethernet1 public Node1 (node1_boot) node1_svc node1_standby Node2 (node2_boot) node2_svc node2_standby Serial1 serial Node1 node1_rs232 Node2 node2_rs232 2. To show the network ether1, enter: cllsnw -n ether1 Implementation Specifics This command is part of High Availability Cluster Multi-Processing for AIX (HACMP for AIX). Files /usr/sbin/cluster/utilities/cllsnw cllsnw command executable file. /etc/objrepos/HACMPadapter Adapter configuration ODM object class. /etc/objrepos/HACMPnetwork Network configuration ODM object class. Suggested Reading HACMP for AIX Concepts and Facilities HACMP for AIX Administration Guide Prerequisite Reading Related Information The cllscf, cllsnode, cllsif, and cllsclstr commands. ess. Th k^@0i7]7P`7!RD./usr/share/man/cat1/clrmnode.1 clrmnode Command **************** Purpose Removes node or adapter from configuration. Syntax clrmnode [-n nodename] [-a adapter] Description The clrmnode command removes a specified node stanza (and associated adapter stanza(s)) or removes a specified adapter stanza (and an associated entry in a node stanza) from the adapter configuration ODM object class. Flags -n nodename Specifies the node name to be removed from the adapter configuration. -a adapter Specifies the hostname of an adapter to be removed from the adapter configuration. Note: This command only removes the adapter information from the local node's adapter ODM object class. Use SMIT "Synchronize all Cluster Nodes" to update the adapter information on other nodes. Implementation Specifics This command is part of High Availability Cluster Multi-Processing for AIX (HACMP for AIX). Do not execute this command from the command line. Use the SMIT interface as explained in the documentation. Files /usr/sbin/cluster/utilities/clrmnode The clrmnode command executable file. /etc/objrepos/HACMPadapter The adapter configuration ODM object class. Suggested Reading HACMP for AIX Concepts and Facilities HACMP for AIX Administration Guide Prerequisite Information Related Information The cllscf, cllsnode, and clchnode commands. ti kr@0i7]7P`7!UD./usr/share/man/cat1/clchipat.1 clchipat Command **************** Purpose Enables or disables IP address takeover mode at startup. Syntax clchipat 'true|false' Description The clchipat command performs processing on AIX startup commands (see files below) and on other files so the cluster can function in an IP address takeover environment. The command is used either to enable or disable the special processing. If an HACMP for AIX server is configured for IP address takeover, an entry to execute /usr/sbin/cluster/etc/harc.net is added to the /etc/inittab script and a -boot flag is added to /etc/rc.net so that the start of TCP/IP subsystems is delayed until after the node is configured on its service address. The entries in the /etc/inittab file corresponding to these subsystems are moved from run-level "2" to run-level "a" and are invoked by the HACMP for AIX event scripts. The entries modified are rctcpip, rcnfs, writesrv, qdaemon. The harc.net script does start all network and inet daemons required to configure HACMP, however. Flags true Enable IP address takeover. Move entries to run-level "a" and modify /etc/rc.net. false Disable IP address takeover. Reverse above changes. Implementation Specifics This command is part of AIX High Availability Cluster Multi-Processing for AIX (HACMP for AIX). Do not run this command from the command line. Use the SMIT interface as explained in the documentation. Files /usr/sbin/cluster/utilities/clchipat The clchipat command script file. /usr/sbin/cluster/etc/harc.net The HACMP for AIX network configuration file. /usr/sbin/cluster/etc/rc.cluster The HACMP for AIX system start-up file. /etc/inittab The system initialization control file. /etc/rc.net The host network configuration file. Suggested Reading HACMP for AIX Concepts and Facilities HACMP for AIX Administration Guide HACMP for AIX Installation Guide Prerequisite Information Related Information 1/cl k ascii_file Description The mardb2a command reads all product information from the Product Database raw logical volume and writes it to stdout. The output can also be redirected to an ASCII file. Flags/Arguments source_rlv_db Specifies the full pathname to the logical volume representing the Product Database file. ascii_file Specifies the output ascii file. Example To copy all the products from the Product Database /dev/rtestdb_lv into the ASCII file named "products.ascii", enter: mardb2a /dev/rtestdb_lv > products.ascii Implementation Specifics This command is part of Highly Available Cluster Multi-Processing for AIX (HACMP for AIX). Files /usr/sbin/cluster/demos/clmarket/mardb2a The mardb2a executable file. Suggested Reading HACMP for AIX Concepts and Facilities HACMP for AIX Instatllation Guide Prerequisite Information Related Information The marserv, marinit, mara2db, and marxclient commands. k< ?A$"0i7]7P`7!D"./usr/share/man/cat1/marinit.1$$ marinit Command *************** Purpose Initializes CLMarket's Product Database and Logfile. Syntax marinit database logfile Description The marinit command initializes the specified Product Database and Logfile's raw logical volumes. Both the Product Database and the Logfile are logical volumes stored on a disk subsystem that can be concurrently accessed. Flags/Arguments database Specifies the full path to the raw logical volume containing the Product Database. logfile Specifies the full path to the raw logical volume used as the Logfile. The Logfile maintains transaction information insuring the integrity of the Product Database. Example To initialize the Product Database logical volume, testdb_lv, and the Logfile logical volume, testlog_lv, enter: marinit /dev/rtestdb_lv /dev/rtestlog_lv Implementation Specifics This command is part of Highly Available Cluster Multi-Processing for AIX (HACMP for AIX). Files /usr/sbin/cluster/demos/clmarket/marinit The marinit executable file. Suggested Reading HACMP for AIX Concepts and Facilities HACMP for AIX Installation Guide Prerequisite Information Related Information The marserv, mara2db, marxclient, and mardb2a commands. labili k*=AA$-0i7]7P`7!D-./usr/share/man/cat1/marserv.1$$ marserv Command *************** Purpose HACMP for AIX CLMarket server. Syntax marserv [-d #] database logfile Description The market server (marserv) opens a Product Database and a Logfile specified on the command line. The -d flag specifies the debug level under which marserv should run. Both the Product Database and the Logfile are logical volumes and their raw logical volume names should be specified. Flags -d Debug Level to use (0 by default). 0 - Print Errors only. 1 - Print Warnings and Errors. 2 - Print Status, Warnings, and Errors. 3 - Print everthing. database Full pathname to the Product Database. logfile Full pathname to the Logfile. Example To run the marserv server with the logical volume db_lv as the Product Database and log_lv as the Logfile at the debug level set to 3, enter: marserv -d 3 /dev/rdb_lv /dev/rlog_lv To run marserv with the raw logical volume /dev/rtestdb_lv as the Product Database and /dev/rtestdb_lv as the Logfile at the default debug level, enter: marserv /dev/rtestdb_lv /dev/rtestlog_lv Implementation Specifics This command is part of Highly Available Cluster Multi-Processing for AIX (HACMP for AIX). Files /usr/sbin/cluster/demos/clmarket/marserv The executable file. Suggested Reading HACMP for AIX Concepts and Facilities HACMP for AIX Installation Guide Prerequisite Information Related Information The marinit, mara2db, and mardb2a commands, and the cllockd daemon. lus kA$0i7]7P`7![D./usr/share/man/cat1/clgetif.1$$ clgetif Command *************** Purpose Prints the interface name, interface device name, and/or netmask associated with a specified IP label or address on the local node. Syntax clgetif [-n] [-a] [-d] IPlabel | IPaddress Description Shows interface or netmask information for the specified IP label/address. Flags -a Prints the interface name (for example, en0) for a given IP label or IP address. -n Prints the interface netmask (in dotted decimal format) for a given IP label or IP address. -d Prints the interface adapter name for a given IP label or IP address. IPlabel Specifies the name of the adapter to show. IPaddress Specifies the address of the adapter to show. Examples 1. To print the interface name for the adapter with the IP label of clam, enter: clgetif -a clam This returns en0. 2. To print the netmask for the adapter with IP address 1.1.1.22, enter: clgetif -n 1.1.1.22 This returns 255.255.255.0 3. To print the interface names and netmasks for adapters with the IP labels clam_svc and clam_stby, enter: clgetif -an clam_svc clam_stby This returns en0 255.255.255.0 and en1 255.255.255.1, where the en0 specifies the service interface clam_svc. Implementation Specifics This command is part of High Availability Cluster Multi-Processing for AIX (HACMP for AIX). Files /usr/sbin/cluster/utilities/clgetif The command executable file. Suggested Reading HACMP for AIX Concepts and Facilities HACMP for AIX Administration Guide HACMP for AIX Troubleshooting Guide Prerequisite Information Related Information kJJA$0i7]7P`7!D./usr/share/man/cat1/claddgrp.1$$ claddgrp Command **************** Purpose Adds an entry to the HACMPgroup ODM class. Syntax claddgrp -g group -r relationship [-o odmdir] -n nodes ... Description The claddgrp command adds a resource group name to the HACMPgroup ODM class. The command specifies the type of resource group and establishes the takeover chain for the group if it is cascading or rotating. The command checks for duplicate entries. Flags -o odmdir (Optional) Specifies an alternative directory to the default /etc/objrepos. -g group Specifies the name of the resource group. -r relationship Specifies the resource group/node relationship: Cascading, concurrent, or rotating. -n nodes Specifies a list of node names (chain for this resource group). The maximum list is eight nodes. Takeover priority is assigned with highest priority going to the leftmost node name in descending order to the lowest priority on the right. For example, the list: -n node1 node3 node2 assigns the priority order node1=1, node3=2, node2=3. Implementation Specifics This command is part of High Availability Cluster Multi-Processing for AIX (HACMP for AIX). Do not run this command from the command line. Use the SMIT interface as explained in the documentation. Files /usr/sbin/cluster/utilities/claddgrp The claddgrp command executable file. /etc/objrepos/HACMPgroup The HACMP for AIX node environment ODM object class. Suggested Reading HACMP for AIX Concepts and Facilities HACMP for AIX Administration Guide HACMP for AIX Installation Guide Prerequisite Information Related Information The clgetgrp, clchgrp, clrmgrp, cllsgrp, cllsres, and clshowres commands. c k(=KA$0i7]7P`7!D./usr/share/man/cat1/clgetgrp.1$$ clgetgrp Command **************** Purpose Gets an entry from the HACMPgroup ODM class. Syntax clgetgrp [-g resource_group] [-o odmdir] [-c ] [ -h] [-f field] [-n node] Description The clgetgrp command retrieves the specified object from the HACMPgroup Class and displays it in the format specified. Flags -o odmdir (Optional) Specifies an alternative directory to the default /etc/objrepos. -g group Specifies the resource group name. -c Specifies output in colon format. -f Specifies the field in object to list. Fields are: group, type, nodes. -h Specifies to print a header. -n Specifies participating node name. Note: All resource groups are listed if no arguments are specified. Example 1. To see the information about resource group grpA presented in colon format, enter: clgetgrp -g grpA -c Information similar to the following will be returned: #group:type:nodes grpA:cascading:nodeA nodeB nodeC 2. To see what nodes participate in the resource chain for resource group grpA, enter: clgetgrp -g grpA -h -f nodes Information similar to the following will be returned: Participating Nodes grpA nodeA nodeB nodeC Implementation Specifics This command is part of High Availability Cluster Multi-Processing for AIX (HACMP for AIX). Files /usr/sbin/cluster/utilities/clgetgrp The clgetgrp command executable file. /etc/objrepos/HACMPgroup The HACMP for AIX resource group ODM object class. /etc/objrepos/HACMPresource The HACMP for AIX resource ODM database. Suggested Reading HACMP for AIX Concepts and Facilities HACMP for AIX Administration Guide HACMP for AIX Installation Guide Prerequisite Information Related Information The clchgrp, claddgrp, clrmgrp, cllsgrp, cllsres, and clshowres commands. tratio k&MA$^0i7]7P`7!D^./usr/share/man/cat1/clchgrp.1$$ clchgrp Command **************** Purpose Changes entry to the HACMPgroup ODM class. Syntax clchgrp -g group [-o odmdir] [-G new_name] [-r relationship] [-n nodes...] Description The clchgrp command changes a resource group name and/or node relationship. If a new name is specified, then all instances of the previous name in the HACMPgroup and HACMPresource databases are changed. If a node relationship and/or list of node names is supplied, they are written over the old. If resources have been defined for the group,they must be deleted before changing the resource group/node relationship. Flags -o odmdir (Optional) Specifies an alternative directory to the default /etc/objrepos. -g group Specifies the resource group name to change. -G new_name Specifies the new resource group name. -r relationship Specifies the resource group/node relationship: Cascading, concurrent, or rotating. -n nodes Specifies a list of node names (chain for this resource group).The maximum list is eight nodes. Takeover priority is assigned with highest priority going to the leftmost node name in descending order to the lowest priority on the right. For example, the list: -n clam mussel seaweed assigns the priority order clam=1,mussel=2,seaweed=3. Implementation Specifics This command is part of High Availability Cluster Multi-Processing for AIX (HACMP for AIX). Do not run this command from the command line. Use the SMIT interface as explained in the documentation. Files /usr/sbin/cluster/utilities/clchgrp The clchgrp command executable file. /etc/objrepos/HACMPgroup The HACMP for AIX resource group ODM object class. /etc/objrepos/HACMPresource The HACMP for AIX resource ODM object class. Suggested Reading HACMP for AIX Concepts and Facilities HACMP for AIX Administration Guide HACMP for AIX Installation Guide Prerequisite Information Related Information The clgetgrp, claddgrp, clrmgrp, cllsgrp, cllsres, and clshowres commands. r k.PA$ 0i7]7P`7!D ./usr/share/man/cat1/clsnapshot.1name.$$ clsnapshot ********** Purpose Generates ASCII files which store HACMP for AIX Cluster Configuration data and state information. Syntax clsnapshot [-a] [-c] [-C] [-f true|false] [g] [h] [i] [-l] [-o odmdir] [-r] [-R] [s] [-N filename] -n filename [-m methodlist] [-d description] Description The clsnapshot command creates, modifies or removes two files: One file, identified by the file extension ".odm" contains the current HACMP for AIX ODM class objects. An optional brief description may be written to the file. A second file with an extension of ".info" contains information useful for problem determination in an HACMP cluster. The clsnapshotinfo command is run on every configured node to obtain node-specific information. The clsnapshot command can also be used to apply a snapshot to the current cluster hardware. A verification utility is run, and must pass before the configuration information is synchronized to the cluster nodes. A "force" flag option forces a snapshot to be applied even if the verification routine fails. Note: The environment variable "SNAPSHOTPATH" contains the path leading to the snapshot file. By default, this path is /usr/sbin/cluster/snapshots. Flags -a Apply a cluster snapshot -c Create a cluster snapshot -C Do not refresh active cluster resource when applied -f true|false Force the apply if verification fails -g Generate a temporary ODM holding the snapshot -h Usage -i Generate info file -l List snapshot files -m methodlist Execute each custom snapshot method listed in methodlist -n file Name of the cluster snapshot -N file New name of the cluster snapshot -o odmdir ODMDIR for HACMP ODM classes location may be specified -r Remove a cluster snapshot -R Replace a cluster snapshot -s Show a cluster snapshot -d text Description Implementation Specifics This command is part of High Availability Cluster Multi-Processing for AIX (HACMP for AIX). Use the SMIT or Xhacmpm interface to run this command as explained in the documentation. Files /usr/sbin/cluster/utilities/clsnapshot The clsnapshot command file. Suggested Reading HACMP for AIX Concepts and Facilities HACMP for AIX Administration Guide Prerequisite Information Related information The clsnapshotinfo command. "# kRA$0i7]7P`7!D./usr/share/man/cat1/clsnapshotinfo.1e.$$ clsnapshotinfo ************** Purpose Executable that retrieves and outputs to stdout certain HACMP for AIX cluster configuration information. Syntax clsnapshotinfo Description The clsnapshotinfo command will run HACMP for AIX and AIX commands and utilities which are required for gathering information pertaining to an HACMP for AIX cluster. A clsnapshot command is run on one node in a cluster, and executes the clsnapshotinfo command on all defined cluster nodes and concatenates the information into a user-defined file with an extension of ".info". In an HACMP/ES cluster, the clsnapshotinfo command runs the clgetesdbginfo file in usr/es/sbin/cluster/utilities. Examples Use the SMIT interface to run the clsnapshot command as explained in the documentation. Implementation Specifics This command is part of AIX Highly Available Cluster Multi-Processing for AIX (HACMP for AIX). Files /usr/sbin/cluster/utilities/clsnapshotinfo The clsnapshot command file. Suggested Reading HACMP for AIX Concepts and Facilities HACMP for AIX Administration Guide HACMP for AIX Enhanced Scalability Installation and Administration Guide Prerequisite Information Related information The clsnapshot command. k"NSA$0i7]7P`7!D./usr/share/man/cat1/xclconfig.1fo.1e.$$ xclconfig Command ***************** Purpose Invokes the HACMP for AIX Quick Configuration utility Syntax xclconfig Description The xclconfig command creates an X/Motif-based Graphical User Interface which allows the user to configure certain HACMP clusters with the minimal amount of user configuration. One of four pre-defined configurations may be chosen, and the user may make certain modifications to each to match any site-specific requirements. The cluster administrator can apply the configuration from a central location (one of the cluster nodes, to be referred to as the configurator), once the following requirements are met: 1. AIX and HACMP for AIX must be installed on the cluster nodes. 2. The required hardware is available and configured: a. The physical disk subsystem must be properly installed. b. TCP/IP must be configured on the nodes and at least one communication path must be available and working between the configurator and the other nodes in the cluster being configured. c. The tty serial connection must exist between the two nodes, and the tty devices must be configured and available. 3. Appropriate entries must exist in the /.rhosts file on the nodes for the configurator node to be able to make use of the standard AIX rsh utility. The xclconfig utility includes a "Guidance Facility" that provides a step-by-step instructions about choosing a configuration, defining connectivity between the configurator and the nodes to be configured, performing optional customizations and verifying and applying the configuration. Implementation Specifics This command is part of High Availability Cluster Multi-Processing for AIX (HACMP for AIX). Files /usr/sbin/cluster/xclconfig The xclconfig command executable file. Suggested Reading HACMP for AIX: System Overview HACMP for AIX: Installation Guide Prerequisite Information a k*UA$+0i7]7P`7!D+./usr/share/man/cat1/xhacmpm.11$$ xhacmpm Command **************** Purpose Starts the Visual System Management (VSM) application used to help configure a cluster under High Availability Cluster Multi-Processing Version 4.2 for AIX (HACMP for AIX). Syntax xhacmpm [-N snapshot_name] Description Xhacmpm is a VSM application used to conveniently configure and view an HACMP cluster. Xhacmpm is a graphical interface that enables you to configure a cluster through direct manipulation of objects (icons). Xhamcpm provides system-defined and user-customized templates for cluster objects (i.e. adapter, resource). To add an object to a cluster configuration, objects are simply dragged-and-dropped from the Templates Area onto a cluster Work Area (Cluster Topology or Cluster Resource). Flags All of the standard command line options parsed by XtDisplayInitialize() (e.g. -bg color, -fn font) and VSM's GuiInitialize() (e.g. -cool True) are supported by xhacmpm. -N snapshot name Snapshot file name to load. Examples 1. To start up xhacmpm with the snapshot file Configuration1 xhacmpm -N Configuration1 Note: xhacmpm will look for snapshot files in the directory stored in the SNAPSHOTPATH environment variable which if left unset defaults to /usr/sbin/cluster/snapshots 2. To start up xhacmpm with the snapshot file My_Config in /home/me SNAPSHOTPATH=/home/me xhacmpm -N My_Config 3. To run xhacmpm with aquamarine as the background color xhacmpm -bg aquamarine Implementation Specifics This command is part of High Availability Cluster Multi-Processing Version 4.2 for AIX. Files /usr/sbin/cluster/xhacmpm The xhacmpm command executable file. /usr/dt/appconfig/help/%L/Xhacmpm.sdl The xhacmpm dthelp file. Suggested Reading High Availability Cluster Multi-Processing Version 4.2 for AIX System Overview High Availability Cluster Multi-Processing Version 4.2 for AIX Administration Guide Prerequisite Information X11, VSM and CDE. Related Information o.1 k(yA$y0i77]7P`7!Ey./usr/share/man/cat1/cldare.11$$ cldare Command ************** Purpose Updates the HACMP Cluster Manager and associated daemons with new configuration information. Syntax cldare [ -u ] cldare [ -n ] [ -i ] [ -r ] [ -t ] [ -v ] [ -f ] [-h] [ -N ] [ -M resgroup [:location | [ stop | default] [:sticky]] ... (Note that the -u flag cannot be run with any other flag or command.) Description The cldare command allows an HACMP Cluster Administrator to synchronize and verify a change to an HACMP cluster configuration, and if the cluster is active, make the cluster daemons and event scripts aware of the new configuration. The latter process is known as a "Dynamic Automatic Reconfiguration Event" (DARE). In order to execute the DARE, the cldare command will request the local Cluster Manager process to execute the DARE. The cldare command will automatically save a copy of the current HACMP configuration as a Cluster Snapshot which may be manually reapplied if the DARE fails. The last seven such snapshots are saved in the default snapshot directory, /usr/sbin/cluster/snapshots. The Cluster Name and/or Cluster ID cannot change as part of a DARE. The Cluster Topology and Cluster Resources cannot both be changed as part of a single DARE. This utility requires that the cluster daemons (clstrmgr, cllockd, clsmuxpd, and clinfo) be shutdown on a node which is to be removed from the configuration. Similarly, when a node is added to the configuration, the daemons must remain shutdown on that node until the DARE has succeeded. After the DARE has succeeded, the cluster administrator may manually start the cluster daemons on the new node. The Cluster Configuration will be verified before the DARE request is passed along to the cluster daemons. Once received, the Cluster Manager will process the DARE. If the Cluster Topology has changed, two Cluster Events will be run to process the DARE. They are: reconfig_topology_start and reconfig_topology_complete. If Cluster Resources have changed, three Cluster Events will be run to process the DARE. They are: reconfig_resource_release, reconfig_resource_acquire, and reconfig_resource_complete. These events handle the acquisition or release of cluster resources. The cldare command provides an emulation feature to emulate cluster resource and cluster topology dynamic reconfiguration. When run in emulation mode, cldare makes no changes to the Cluster Manager. Flags -u If this flag is set, the DARE will remove the stage ODM lock on all nodes. This may be used in case of a failure to remove the lock. This flag is exclusive--it cannot be run with any other flags or commands in cldare. -i If this flag is specified, the DARE event will be performed whether or not the cluster verification finds configuration errors. -n If this flag is specified, cluster resources which are removed from the configuration will not be unconfigured as part of the DARE event. The default behavior is to unconfigure the resources. -r If this flag is specified, Cluster Resources will be synchronized across cluster nodes. -t If this flag is specified, the Cluster Topology will be synchronized across cluster nodes. -v Do not run verification. -f If this flag is specified, the cldare command will run as an emulation only and no changes will be made to the Cluster Manager. You must specify either the -r flag to indicate the emulation of Synchronizing Cluster Resources, or the -t flag to indicate the emulation of Synchronizing Cluster Topology. The -u flag and the -v flag cannot be used if you specify emulation mode. -h shows usage statement -N Requests non-blocking behavior that prevents the cldare command from performing the final resource group location check. Normally, the cldare command waits until all requested group migrations have completed. It then finishes by running the clfindres command to check if the group's migrations have completed properly. This blocking behavior, however, would prevent the use of DARE group migration in pre- or post-event scripts. Thus, when using DARE resource group migration in pre- or post-event scripts, include the -N flag. -M resgroup [:location | [stop | default] [:sticky] Permits one or more pairs of resource groups and nodes to be specified on the command line to perform a dynamic resource group migration to another node. The stop keyword in place of a node location causes the utility to attempt to stop the resource group, taking down any service label, unmounting file systems, etc. A sticky stopped resource will be restarted at the time of the next migration request. A non-sticky stopped resource will likely be restarted at the next cluster event. Non-sticky stop requests should be used with caution. The use of the default keyword instead of a location will cause the resource group to be started/moved to a cluster node based on the node priority listed provided in the resource group definition. For more information on the cldare command and the location, stop, and default keywords, see the chapter on "Changing Resources and Resource Groups" in the HACMP for AIX Administration Guide. Implementation Specifics This command is part of High Availability Cluster Multi-Processing for AIX (HACMP for AIX). Do not run this command from the command line. Use the SMIT or VSM interface as explained in the documentation. Files /usr/sbin/cluster/utilities/cldare The cldare command executable file. /usr/sbin/cluster/snapshots/active.X.odm The generated cluster snapshot. Suggested Reading HACMP for AIX Concepts and Facilities HACMP for AIX Administration Guide HACMP for AIX Installation Guide Prerequisite Information Related Information The reconfig_topology_start, reconfig_topology_complete, reconfig_resource_release, reconfig_resource_acquire, reconfig_resource_complete, clsnapshot, and xhacmp commands. se, r k"d~A$0i77]7P`7!D./usr/share/man/cat1/clgetactivenodes.1$$ clgetactivenodes **************** Purpose Prints a list of nodes which have a running Cluster Manager process. Syntax clgetactivenodes -n nodename -o odmdir -t timeout -v verbose Description The clgetactivenodes command makes an RPC call to the Cluster Manager on the given node requesting a list of all nodes the Cluster Manager considers active (running the Cluster Manager). This routine will print the list of such nodes to stdout. If there is no response from the node within timeout seconds, the call returns. The return code will be the number of active nodes in the list, which can be displayed using print $?. Flags -n nodename The name of a node running a Cluster Manager process. -o odmdir The directory containing the HACMP ODM information. By default, this is /etc/objrepos. -t timeout The length of time in seconds for the command to retrieve the list. The default is 10 seconds. -v verbose If this flag is set, debug information will be printed. Example To retrieve a list of nodes with active Cluster Manager processes from the Cluster Manager on node "clam", enter: clgetactivenodes -n clam Implementation Specifics This command is part of AIX High Availability Cluster Multi-Processing for AIX (HACMP for AIX). Files /usr/sbin/cluster/utilities/clgetactivenodes The clgetactivenodes executable file. Suggested Reading Prerequisite Information Related Information The "cldare" command. kA$0i77]7P`7!D./usr/share/man/cat1/clgodmcomp.1des.1$$ clgodmcomp ********** Purpose Compares ODM Class Objects in different directories Syntax clgodmcomp -n nodename -c classname -s odmdir -t odmdir -q criteria -f field1 field2 ... Description The clgodmcomp command compares, on node nodename, the specified ODM class in directory odmdir1 with that in directory odmdir2, excluding comparing any specified fields. Flags -n nodename The name of an HACMP node. -c classname The name of the ODM Class -s odmdir A directory containing the HACMP ODM information. -t odmdir A second directory containing the HACMP ODM information. -q criteria The field to search for on a comparison -f field1 ... A list of ODM Class object fields to exclude from the comparison. Example clgodmcomp -n clam -c HACMPadapter -s /etc/objrepos -t \ /usr/sbin/cluster/etc/objrepos/active -f nodename Implementation Specifics This command is part of AIX High Availability Cluster Multi-Processing for AIX (HACMP for AIX). Files /usr/sbin/cluster/utilities/clgodmcomp The clgodmcomp executable file. Suggested Reading Prerequisite Information Related Information The "cldare" command. kxOA$0i7]7P`7!D./usr/share/man/cat1/clrmgrp.1.$$clrmgrp Command **************** Purpose Removes a resource group and all related resources Syntax clrmgrp -g group [-o odmdir] Description The clrmgrp command removes a resource group and all related resources from HACMPgroup and HACMPresource ODM object classes. Flags -o odmdir (Optional) Specifies an alternative directory to the default /etc/objrepos. -g group Specifies the name of the resource group to remove. Implementation Specifics This command is part of High Availability Cluster Multi-Processing for AIX (HACMP for AIX). Do not execute this command from the command line. Use the SMIT interface as explained in the documentation. Files /usr/sbin/cluster/utilities/clrmgrp The clrmgrp command executable file. /etc/objrepos/HACMPgroup The HACMP resource group ODM object class. /etc/objrepos/HACMPresource The HACMP resource ODM object class. Suggested Reading HACMP for AIX Concepts and Facilities HACMP for AIX Administration Guide HACMP for AIX Installation Guide Prerequisite Information Related Information The clgetgrp, clchgrp, claddgrp, cllsgrp, cllsres, and clshowres commands. hi kA$ 0i77]7P`7!D ./usr/share/man/cat1/clvaryonvg.1des.1$$ clvaryonvg Command ****************** Purpose Varies on a volume group. Syntax clvaryonvg [-F] [-f] [-n] [-p Number] [-s] [-o] Description The clvaryonvg utility is meant as a replacement for the standard AIX varyonvg command. It performs some checks on the volume group to determine if there have been any changes made to it prior to calling the standard AIX varyonvg command. If any changes have been made since the last time the volume group was varyied on locally, the volume group is exported and then imported prior to being varied on, thus ensuring that all nodes have a consistent view of the the volume group's content. If a system failure occurs during a VG update, the volume group can become invisible to the node. Two mechanisms are implemented to safeguard against this. Prior to executing the exportvg of a volume group a file is created in /usr/sbin/cluster/etc called .replay, where VG is the name of the volume group we are acting on. This file is a shell script which contains a set of commands meant to re-establish the volume group in the worst case scenario. The commands in this file are automatically executed at the next invocation of clvaryonvg if the volume group does not exist. Should the replay fail to clear the problem, messages are logged into hacmp.out [default location: /tmp], directing the operator to information needed to manually restore the volume group. This information can also be found in the file /usr/sbin/cluster/etc/vg/.desc. Additionally, a copy of the failed replay file is placed in the directory /var/tmp. Flags -F Forces an update (exportvg/importvg) on the volume group, ignoring the timestamp. -f The flag is passed on to importvg (if it is run) as well as to varyonvg. See the importvg and varyonvg manpages for more details. -n Disables the synchronization of the stale physical partitions within the volume group. This flag is simply passed on to varyonvg. -p Number Specifies that all physical volumes must be available to use the clvaryonvg command. -s Makes the volume group available in system management mode only. -o Leaves the volume group varied off upon completion, having performed all the integrity checks and performed the importvg/exportvg, if needed. Examples 1. To activage volume group vg03, enter: clvaryonvg vg03 2. To force the update of a node's information on volume group vg03, enter: clvaryonvg -F vg03 Implementation Specifics This command is part of High Availability Cluster Multi-Processing for AIX (HACMP for AIX). Files /usr/sbin/cluster/utilities/clvaryonvg The clvaryonvg executable file. /usr/sbin/cluster/etc/vg/ The timestamp for the volume group. /usr/sbin/cluster/etc/vg/.desc File which contains the major number and the names of the physical volumes which comprise a volume group. This information is usefull when manual intervention is needed. /usr/sbin/cluster/etc/vg/.replay File which contains code to restore a volume group in case of a system crash during clvaryonvg's execution. /etc/objrepos/HACMPresource The HACMP node environment ODM resource group object class. Suggested Reading HACMP for AIX Concepts and Facilities HACMP for AIX Administration Guide Prerequisite Information Related Information The cllsres, claddres, and clshowres commands. m klkA$0i7b]7P`7!D./usr/share/man/cat1/cl_auto_varyoff.1$$ cl_auto_varyoff Command Purpose Change the auto varyon attribute of an imported volume group to no. Syntax cl_auto_varyoff vg_name nodename Description The Quick Configuration utility uses this command to change the auto varyon attribute of an imported volume group to "no." Flags vg_name Name of the volume group to vary off. nodename Name of the volume group's node. Implementation Specifics This command is part of the Quick Configuration utility. Exit Codes The following exit codes are returned by cl_auto_varyoff. 0 Success. Else any positive number. Files Directory containing the cl_auto_varyoff command executable /usr/sbin/cluster/utilities HACMP /usr/es/sbin/cluster/utilities HACMP/ES Suggested Reading HACMP for AIX Installation Guide, Part 2, "Installing HACMP Cluster Configurations: Quick Method" Related Information /usr/sbin/chvg, /usr/sbin/cluster/utilities/setup_vg_fs which kTuA$0i7d]7P`7!D./usr/share/man/cat1/clfindres.1off.1$$clfindres Command ************** Purpose Finds a given resource group in a cluster configuration. This command is intended for use when trying to locate migrated resource groups. Syntax clfindres [-s] [resgroup1] [resgroup2] ... Description The clfindres command attempts to find a given resource group in the cluster using the same methods as the Cluster Manager uses in determining where a resource is configured. In addition, the clfindres command will indicate whether the current location is "sticky." This is done by checking for a sticky location in the ODM. The sticky location will not exist unless the topology would permit a migration to occur. Flags -s Requests abbreviated (location only) output. Example clfindres -s myres themoney ourres Produces the following abbreviated output: myres:crusty themoney:[crusty oyster] ourres:**down** If no arguments are specified, the clfindres command lists all resources. As shown in the following, the output lists resource groups and defines the resource group type, state, location, and migration type/location. The output lists all resource groups in the order of cascading, rotating, and concurrent. GroupName Type State Location (Sticky:location) --------- ---- ----- -------- ----------------- myres cascading UP crusty crusty ourres cascading DOWN N/A STOP yourres rotating UP oyster themoney concurrent UP [crusty oyster] zztop concurrent DOWN N/A Implementation Specifics This command is part of High Availability Cluster Multi-Processing for AIX (HACMP for AIX). Files /usr/sbin/cluster/utilities/clfindres clfindres command executable file Suggested Reading HACMP for AIX Concepts and Facilities HACMP for AIX Administration Guide Prerequisite Information Related Information The cldare command. /s k40A$ 0i7d]7P`7!D ./usr/share/man/cat1/cl_emulate.1ff.1$$ cl_emulate Command ***************** Purpose Emulates a specific cluster event and outputs the results of the emulation. Syntax cl_emulate -e node_up -n nodename cl_emulate -e node_down -n nodename {f | g | t} cl_emulate -e network_up -w networkname [-n nodename] cl_emulate -e network_down -w networkname [-n nodename] cl_emulate -e join_standby -n nodename -a ip_label cl_emulate -e fail_standby -n nodename -a ip_label cl_emulate -e swap_adapter -n nodename -w networkname -a ip_label -d ip_label Description Emulates specific cluster events by running event scripts that produce output but that do not affect the cluster configuration or status. Emulation allows you to predict a cluster's reaction to a particular event as though the event actually occurred. The cl_emulate command runs the events scripts on every active node of a stable cluster. Output from each node is stored on an output file on the node from which you invoked the emulation. You can specify the location of the output file using log redirection, or use the default output file, /tmp/emuhacmp.out. You can only run one instance of the event emulator at a time. If you attempt to start a new emulation in a cluster while an emulation is already running, the integrity of the results cannot be guaranteed. Each emulation is a stand-alone process; one emulation cannot be based on the results of a previous emulation. The cl_emulate command runs customized event scripts (pre- and post-event scripts) associated with an event, but does not execute commands within these scripts. Therefore, if these customized scripts change the cluster configuration when actually run, the outcome may differ from the outcome of the emulation. When emulating an event which contains a customized script, cl_emulate uses the ksh flags -n and -v. The -n flag reads commands and checks them for syntax errors, but does not execute them. The -v flag indicates verbose mode. When writing customized scripts that may be accessed during an emulation, be aware that the other ksh flags may not be compatible with the -n flag and may cause unpredictable results during the emulation. See the ksh man page for flag descriptions. Flags -e eventname The name of the event to emulate: node_up, node_down, network_up, network_down, join_standby, fail_standby, swap_adapter. -n nodename The node name used in the emulation. When emulating a network_up or network_down event, this field is optional. -f Forced shut down emulation. -g Graceful shut down with no takeover emulation. -t Graceful shutdown with takeover emulation. -w networkname The network name used in the emulation. -a ip_label The standby adapter address with which to switch. -d ip_label The service adapter to fail. Implementation Specifics This command is part of High Availability Cluster Multi-Processing for AIX (HACMP for AIX). The cl_emulate command requires that both the Cluster SMUX peer daemon (clsmuxpd) and the Cluster Information Program (Clinfo) be running on your cluster. Files /usr/sbin/cluster/events/emulate/driver/cl_emulate The cl_emulate command executable file. Suggested Reading HACMP for AIX Concepts and Facilities HACMP for AIX Administration Guide HACMP for AIX Troubleshooting Guide Related Information The cldare and ksh commands. e - kh/A$ 0i7g]7P`7!D ./usr/share/man/cat1/cl_convert.1ff.1$$ cl_convert Command ****************** Purpose Converts cluster configurations from earlier versions of HACMP for AIX to HACMP for AIX, Version 4.3.1. Syntax cl_convert -v [version] [-F] Description The cl_convert command is executed automatically during the installation of HACMP 4.3.1 to upgrade from most earlier versions of HACMP (4.1.1, 4.2, 4.2.1, 4.2.2, 4.3.0) to Version 4.3.1. ( Note that when upgrading from version 4.1.0, you must run cl_convert manually.) The command creates new ODM data structures and objects, redefines field names and values within data structures, and ensures data integrity between HACMP versions. Depending on the HACMP upgrade version, the command calls the appropriate program to update the ODMs to the current level. cl_convert is located in the /usr/sbin/cluster/conversion directory. Upgrading from Version 4.1.1, 4.2, 4.2.1, 4.2.2, or 4.3.0 to Version 4.3.1 Before the current version of HACMP for AIX is installed over the old version, the install script changes the HACMP ODM classes by adding the suffix OLD to those classes stored in the /etc/objrepos directory and then creates the new version of the HACMP ODM classes in the same directory. After most of the installation completes, the cl_convert command is issued to read the configuration data in the HACMPxxxOLD classes, convert it to the new format and then populate the new HACMP ODM classes. The cl_convert command will be run on all nodes in the cluster as they are upgraded to the current version. There is no requirement to synchronize the cluster after it has been fully upgraded. However if an error occurs during the conversion of one of the nodes in the cluster, a synchronization can be done from a node in the cluster which successfully converted the previous configuration once ALL the nodes in the cluster have been upgraded. Flags -v Specifies the version number from which the conversion is to be performed (the previous HACMP version number). Warning: Do not use the cl_convert command unless you are sure about which version you are converting. -F The force option unconditionally deletes the contents of the new ODM classes, therefore all previous data is overwritten. If this option is not specified, the cl_convert command checks for configured data in new ODM classes and if data is present, the conversion is aborted. The installation script uses the force option. This option does not affect the data in the HACMPxxxOLD classes. Examples If a cluster is already configured for HACMP/6000 4.2, and you wish to overwrite configuration data in this earlier version, enter: cl_convert -v 4.2 -F Implementation Specifics This command is part of High Availability Cluster Multi-Processing Version for AIX (HACMP for AIX). Files /usr/sbin/cluster/conversion/cl_convert Command clconvert executable file. /etc/objrepos The directory which contains the HACMP ODM classes. Suggested Reading HACMP for AIX Concepts and Facilities HACMP for AIX Installation Guide Prerequisite Information Related Information clconvert_snapshot command.  k&1A$ 0i7g]7P`7!D ./usr/share/man/cat1/clconvert_snapshot.1$$ clconvert_snapshot Command ************************** Purpose Converts cluster snapshot file from earlier versions of HACMP for AIX to snapshot file of HACMP for AIX, Version 4.3.1. Syntax clconvert_snapshot [-C] -v [release] -s [snapshot file] Description The clconvert_snapshot command is used to upgrade snapshot files from an earlier version of HACMP (4.2, 4.2.1 4.2.2, 4.3.0 or 4.3.1 [if performing migrating from HACMP to HACMP/ES]) to Version 4.3.1. The command adds new ODM data objects and redefines field values within data structures in the snapshot file. Once a snapshot file has been upgraded, it can not be reverted back to the previous version. Therefore if a copy of the old version of the snapshot file must be preserved, it must be saved prior to executing this command. You must be in the /usr/sbin/cluster/conversion directory on the same node that took the snapshot to run the clconvert_snapshot command. Once the snapshot file has been upgraded and all of the nodes in the cluster have the current level installed, the upgraded snapshot can be applied and then the cluster can be brought up. The script clconvert_snapshot creates an old version of the ODMs and populates those ODMs with the values from the user supplied snapshot file. It then calls the same commands that cl_convert uses to convert those ODMs to the current version. A new snapshot is taken from the upgraded ODMs and copied to the user supplied snapshot file. Flags -C This option is only available with HACMP/ES. Converts a HACMP for AIX snapshot file to a HACMP/ES snapshot file. Do not use this option when the specified snapshot file is already a HACMP/ES snapshot file. -v Specifies the release number from which the conversion is to be performed WARNING: Do not use the clconvert_snapshot command unless you know the version from which you are converting. -s Specifies the snapshot file. If you do not specify a path for the snapshot file, the command uses the path specified in the $SNAPSHOTPATH variable. The default is /usr/sbin/cluster/snapshots. The suffix .odm can optionally be added to the snapshot file name. Examples If you want to convert the snapshot file "TestSnapshot" from HACMP for AIX, Version 4.2.2 to the snapshot file of HACMP for AIX, Version 4.3.1, enter: clconvert_snapshot -v 4.2.2 -s TestSnapshot or enter: clconvert_snapshot -v 4.2.2 -s TestSnapshot.odm If you want to convert the snapshot file "OldSnapshot" from HACMP for AIX, Version 4.2.2 to the snapshot file of HACMP/ES, Version 4.3.1, enter: clconvert_snapshot -C -v 4.2.2 -s OldSnapshot Implementation Specifics This command is part of High Availability Cluster Multi-Processing for AIX (HACMP for AIX). Files /usr/sbin/cluster/conversion/clconvert_snapshot The clconvert command executable file. Suggested Reading HACMP for AIX Concepts and Facilities HACMP for AIX Installation Guide HACMP for AIX Enhanced Scalability Installation and Administration Guide Prerequisite Information Related Information clsnapshot command. cl_convert command. hot com k|A$*0i7r]7P`7!D*./usr/share/man/cat1/cl_setup_kerberos.1$$ cl_setup_kerberos ***************** Purpose Creates the Kerberos service principals and /.klogin entries necessary for running HACMP, HACMP/ES, or HANFS with the cluster security mode set to Enhanced. Syntax cl_setup_kerberos Description The cl_setup_kerberos utility creates the proper Kerberos service principals, and the /.klogin entries, and updates the /etc/krb-srvtab file and /.klogin file on all nodes in the HA cluster with the new Kerberos service principal information. For the command to execute properly the user must first enter the cluster topology configuration on at least one of the cluster nodes. The cl_setup_kerberos utility extracts the adapter IP labels stored in the HACMPadapter odm and adds both a rcmd and a godm service principal for each adapter IP label listed in the odm to the Kerberos Authentication Database. The utility also extracts these principals from the primary Kerberos Authentication Database and copies each of the principals to each cluster node's /etc/krb-srvtab file. cl_setup_kerberos then adds the name of each new service principal to each node's /.klogin file. After successful completion, all nodes in the current cluster configuration will be properly configured to use Kerberized cluster commands. To provide the cl_setup_kerberos utility with a secure means to execute commands on other nodes in the cluster and on the control workstation, users must add SP reliable Ethernet adapter labels associated with each cluster node into the cluster topology configuration. Also, the Kerberos Authentication Database administrative password must be known by the user, and the user executing the utility must have root privileges. The cl_setup_kerberos utility should be run after the following events: - initial cluster configuration - each time a new adapter IP label has been added to the cluster topology - each time that setup_server or setup_authent is run and any of the cluster nodes are customized to receive new krb-srvtab files. Related Information kerberos, add_principal, ext_srvtab, kstash beros. kFA$0i7]7P`7!D./usr/share/man/cat1/err_emulate.1ros.1$$ err_emulate Command ******************* Purpose Logs an error to the AIX error device /dev/error. Syntax err_emulate where ID is a hexadecimal error identifier. Description The err_emulate command is used to log an error to the AIX error device /dev/error. This is useful for testing user-defined error notification methods. The user needs to select error labels and define error notification methods before using this command. Running the err_emulate command inserts an error into the AIX error device. The error deamon then picks up the error and runs the appropriate notification method that the user may have defined for the error label. The err_emulate command uses the resource name EMULATOR to distinguish between actual and emulated errors. Example To insert an error with label OPMSG to the error device, use errpt -t -J OPMSG to get the error identifier for the error label OPMSG. Then, use the error identifier ( AA8AB241 ) to run the err_emulate command as shown below. err_emulate AA8AB241 Related Information The diag command, errclear command, errinstall command, errupdate command, errpt command. The errlog subroutine. Files /usr/sbin/cluster/utilities/err_emulate /usr/es/sbin/cluster/utilities/err_emulate Suggested Reading HACMP for AIX Enhanced Scalability Install and Admin Guide HACMP for AIX Concepts and Facilities Guide HACMP for AIX Installation Guide th ea kFWA$0i7*]7P`7!D./usr/share/man/cat1/cl_chuser.11ros.1$$ cl_chuser Command ***************** Purpose Changes user attributes for a user on all nodes in an HACMP cluster. Syntax cl_chuser [-cspoc "[-f] [-g ResourceGroup | -n NodeList]"] Attribute=Value ... Name Description Warning: Do not use the cl_chuser command if you have a Network Information Service (NIS) database installed on any cluster node; using the command in this environment can cause database inconsistencies. The cl_chuser command changes attributes on all cluster nodes for the user identified by the Name parameter. The user name is an alphanumeric string of eight bytes or less. To change an attribute, specify the attribute name and the new value with the Attribute=Value parameter. Refer to the chuser command for valid attributes and values. If you specify a single incorrect attribute or attribute value with the cl_chuser command, the command does not change attributes on any cluster node. By default, cl_chuser requires that all cluster nodes be powered up and accessible over the network; otherwise, cl_chuser fails. Additionally, by default, cl_chuser requires that a user with the given user name exist on every cluster node. Note: if any node in the cluster is a member of an SP with the usermgmt_config option set to 'true', this operation will not be allowed. This command uses the AIX rsh facility to propagate commands to other nodes and requires the proper rsh access to all nodes. Thus each node must have a /.rhosts file which includes references to all interfaces for each cluster node. The /.rhosts file must reside in the root directory, and its mode must be 0600. You can use the System Management Interface Tool (SMIT) to run this command. To use SMIT, enter: smit cl_chuser Flags -cspoc Argument used to specify the use of one of the following C-SPOC options: -f Forces cl_chuser command to skip default verification. If this flag is set and a cluster node is not accessible, cl_chuser reports a warning and continues execution on the other cluster nodes. If the flag is set and the user does not exist on a node, cl_chuser reports a warning and continues execution on the other cluster nodes. -g ResourceGroup Generates a list of nodes participating in the resource group on which the cl_chuser command will be executed. -n NodeList Specifies the node(s) on which the C-SPOC command will be executed. You can specify more than one node by separating each node in the list with a comma. Examples 1. To change the expiration date for the davis user account to 8 a.m., 1 May, 1995 on every cluster node, enter: cl_chuser expires=0501080095 davis 2. To add davis to the groups finance and accounting on every cluster node, enter: cl_chuser -cspoc "-g resgrp1" groups=finance,accounting davis 3. To specify one or more cluster nodes on which to execute the cl_chuser command, enter: cl_chuser -cspoc "-n node1,node2, ... " groups=adm albert Note: If you do not specify either the -g or -n options, the default action occurs on all cluster nodes. Implementation Specifics This command is part of High Availability Cluster Multi-Processing for AIX (HACMP for AIX). You must be a root user to execute C-SPOC commands. Files /tmp/cspoc.log File contains a log of all distributed commands run, along with status, error messages, and timestamps. /usr/bin/chuser Contains the path to the chuser command. /etc/passwd Contains the basic attributes of users. /etc/group Contains the basic attributes of groups. /etc/security/group Contains the extended attributes of groups. /etc/security/user Contains the extended attributes of users. /etc/security/lastlog Contains the last login attributes of users. /etc/security/limits Defines resource quotas and limits for each user. /etc/security/audit/config Contains audit configuration information. /etc/security/environ Contains the environment attributes of users. Suggested Reading HACMP for AIX Administration Guide HACMP for AIX Troubleshooting Guide Related Information The chuser and rsh commands. cie kX XA$`0i7*]7P`7!D`./usr/share/man/cat1/cl_chfs.11$$ cl_chfs Command *************** Purpose Changes attributes of a shared file system. Syntax cl_chfs [-cspoc "[-f] [-g ResourceGroup | -n NodeList]"] [-m newmtpt] [-u mtgrp] [-A {yes | no}] [-p {ro | rw}] [-a attr1=val1] [-d attr] [-t {yes | no}] FileSystem Description Attention: This command is not supported for concurrent volume groups. The cl_chfs command changes the attributes of a shared file system on the node which currently has the file systems' underlying shared volume group varied on. The file system must reside on a volume group that is shared by all participating nodes in the specified resource group. The new mount point, automatic mounts, permissions, and file system size can be set or changed. The FileSystem parameter specifies the name of the file system, expressed as a mount point. If cl_chfs is unable to change the shared file system -- the underlying AIX chfs command fails -- cl_chfs also fails. The definition of the volume group will be updated on all nodes in the resource group immediately. By default, cl_chfs requires that all nodes in an HACMP cluster be accessible over the network and powered up; otherwise, cl_chfs fails. Also the file system's volume group must be varied on. The cl_chfs command also requires the proper rsh access to all cluster nodes because it uses the AIX rsh facility to propagate commands to other nodes. Thus each node must have a /.rhosts file which includes references to all interfaces for each cluster node. The /.rhosts file must reside in the root directory, and its mode must be 0600. You can use the System Management Interface Tool (SMIT) to run this command. To use SMIT, enter: smit cl_chfs Flags -cspoc Argument used to specify the use of one of the following C-SPOC options: -f The command will not fail if at least one node which has access to the underlying volume group is accessible. A warning is issued for nodes that cannot be reached. If no node has the volume group varied on, and it is a shared non-concurrent volume group, an appropriate node is chosen, the volume group on that node is varied on, and the command executes there. The volume group is varied off upon successful completion. -g ResourceGroup Generates a list of nodes participating in the resource group on which the cl_chfs command will be executed. -n NodeList Specifies the node(s) on which to execute the C-SPOC command. You can specify more than one node by separating each node in the list with a comma. Note: When using the cl_chfs command to change a file system's mount point, be aware that the mount point must also be changed in the resource group to avoid errors generated during resynchronization or failover. -a attr1=val1 Specifies the attribute/value pairs; dependent on virtual file system type. Specific to the journaled file system, the size=Value parameter specifies the size of the journaled file system in 512-byte blocks. If Value begins with a + it is interpreted as a request to increase the file system size by the specified amount. If the specified size is not evenly divisible by the physical partition size, it is rounded up to the closest evenly divisible number. Also specific to the journaled file system is the logname=LVName parameter, which specifies the logical volume name of the existing log to be used. -A Specifies the attributes for auto-mount. yes File system is automatically mounted at system restart. no File system is not mounted at system restart. -m newmtpt Specifies the new mount point. -p Sets the permissions for the file system. ro Specifies read only permissions. rw Specifies read-write permissions. -t Sets accounting entry in the /etc/filesystems file. yes The accounting= entry is set to true. no The accounting= entry is set to false. -u mtgrp Specifies the mount group. Mount groups are used to group related mounts, so that they can be mounted as one instead of mounting each individually. For example, if several scratch file systems always need to be mounted together when performing certain tests, they can each be placed in the test mount group. They can then all be mounted with a single command, such as the mount -t test command. Examples 1. To change the file system size of the /test shared file system, enter: cl_chfs -cspoc "-g resource_grp1" -a size=24576 /test This changes the size of the /test journaled file system to 24576 512-byte blocks, or 12 MB (provided it was previously no larger than this). 2. To change the mount point of a file system, enter: cl_chfs -cspoc "-g resource_grp1" -m /test2 /test This changes the mount point of a file system /test to file system /test2. 3. To specify one or more cluster nodes on which to execute the cl_chfs command, enter: cl_chfs -cspoc "-n node1,node2, ... " -s=+4 /test2 Implementation Specifics This command is part of High Availability Cluster Multi-Processing for AIX (HACMP for AIX). You must be a root user to execute C-SPOC commands. Files /tmp/cspoc.log File contains a log of all distributed commands run, along with status, error messages, and timestamps. /etc/filesystems Lists the known file systems and defines their characteristics. Suggested Reading HACMP for AIX Administration Guide HACMP for AIX Troubleshooting Guide Related Information The chfs, clvaryonvg, cl_chlv, chlv, and rsh commands. k_A$0i7*]7P`7!E./usr/share/man/cat1/cl_chgroup.1ros.1$$ cl_chgroup Command ****************** Purpose Changes group attributes on all nodes in an HACMP cluster. Syntax cl_chgroup [-cspoc "[-f] [-g ResourceGroup | -n NodeList]"] Attribute=Value ... Group Description Warning: Do not use the cl_chgroup command if you have a Network Information Service (NIS) database installed on any cluster node; using the command in this environment can cause database inconsistencies. The cl_chgroup command changes attributes for the group specified by the Group parameter on all cluster nodes. The group name is a string of eight bytes or less. To change an attribute, specify the attribute name and the value you want to change it to in the Attribute=Value parameter. Refer to the manpage for the underlying AIX chgroup command for valid attributes and values. By default, cl_chgroup requires that all nodes in the HACMP cluster must be accessible. Each cluster node must be powered up and accessible over the network; otherwise, cl_chgroup fails. By default, cl_chgroup requires that a group (with the given group name) exist on every cluster node; otherwise, cl_chgroup fails. Note: if any node in the cluster is a member of an SP with the usermgmt_config option set to 'true', this operation will not be allowed. This command uses the AIX rsh facility to propagate commands to other nodes and requires the proper rsh access to all nodes. Thus each node must have a /.rhosts file, which includes references to all interfaces for each node. The /.rhosts file must reside in the root directory, and its mode must be 0600. You can use the System Management Interface Tool (SMIT) to run this command. To use SMIT, enter: smit cl_chgroup Flags -cspoc Argument used to specify the use of one of the following C-SPOC options: -f Forces cl_chgroup command to skip default verification. If this flag is set and a cluster node is not accessible, cl_chgroup prints a warning and continues execution on the other cluster nodes. If the flag is set and the group does not exist on a node, cl_chgroup prints a warning and continues execution on the accessible cluster nodes. -g ResourceGroup Generates a list of nodes participating in the resource group on which the cl_chgroup command will be executed. -n NodeList Specifies the node(s) on which the C-SPOC command will be executed. You can specify more than one node by separating each node in the list with a comma. Examples 1. To add Sam and Carol to the finance group on all cluster nodes that currently have Frank as a member, enter: cl_chgroup users=sam,carol,frank finance Note: This command executes on all cluster nodes and completes only on nodes that contain the group and all specified user IDs. 2. To remove Frank from the finance group on all cluster nodes, but to retain Sam and Carol and to remove the administrators of the finance group on all cluster nodes, enter: cl_chgroup users=sam,carol adms=finance staff 3. To specify one or more cluster nodes on which to execute the cl_chgroup command, enter: cl_chgroup -cspoc "-n node1,node2, ... " adms=finance staff 4. To change a group that is located on nodes participating in a resource group, enter: cl_chgroup -cspoc "-g rsgrp1 ... " adms=finance staff Implementation Specifics This command is part of High Availability Cluster Multi-Processing for AIX (HACMP for AIX). You must be a root user to execute C-SPOC commands. Files /tmp/cspoc.log File contains a log of all distributed commands run, along with status, error messages, and timestamps. /etc/group Contains the basic attributes of groups. /etc/security/group Contains the extended attributes of groups. /etc/passwd Contains the basic attributes of users. Suggested Reading HACMP for AIX Administration Guide HACMP for AIX Installation Guide HACMP for AIX Troubleshooting Guide Related Information The chgroup and rsh commands. you ha kZ`A$)0i7*]7P`7!E)./usr/share/man/cat1/cl_chlv.1.$$ cl_chlv Command *************** Purpose Changes the characteristics of a shared logical volume. Syntax cl_chlv [-cspoc "[-f] [-g ResourceGroup | -n NodeList]"] [-a Position] [-b BadBlocks] [-d Schedule] [-e Range] [-L label] [-p Permission] [-r Relocate] [-s Strict] [-t Type] [-u Upperbound] [-v Verify] [-w MirrorWriteConsistency] [-x Maximum] LogicalVolume ... Changes the name of a shared logical volume: cl_chlv [-cspoc "[-f] [-g ResourceGroup | -n NodeList]"] -n NewLogicalVolume LogicalVolume Description The cl_chlv command changes the attributes of a shared logical volume on the node that currently has the logical volume's underlying shared volume group varied on. Note that the information changed is in memory on the local node and in the VGDA on the physical disk associated with the logical volume. The definition of the volume group will be updated on all nodes in the resource group immediately. The LogicalVolume parameter can be a logical volume name or logical volume ID. Each current characteristic for a logical volume remains in effect unless explicitly changed with the corresponding flag. The changes you make with the -a, -e, -s, and -u flags take effect only when new partitions are allocated or when partitions are deleted. The other flags take effect immediately. To change the name of a logical volume, use the -n flag and the NewLogicalVolume parameter to represent the new logical volume name. The -n flag should not be used simultaneously with other option flags. The cl_chlv command causes the definition of the underlying shared volume group to be updated upon failover on a participating node in the resource group. By default, cl_chlv requires that all nodes in the HACMP cluster be accessible over the network and powered up; otherwise, cl_chlv fails. Note: Changes you make to the logical volume are not reflected in the file systems. To change file system characteristics, use the cl_chfs command. This command uses the AIX rsh facility to propagate commands to other nodes and requires the proper rsh access to all nodes. Thus each node must have a /.rhosts file which includes references to all interfaces for each cluster node. The /.rhosts file must reside in the root directory, and its mode must be 0600. You can use the System Management Interface Tool (SMIT) to run this command. To use SMIT, enter: smit cl_chlv Flags -cspoc Argument used to specify the use of one of the following C-SPOC options: -f The cl_chlv command will not fail if at least one node which has access to the underlying volume group is accessible. A warning is issued for nodes that cannot be reached. If no node has the volume group varied on, and it is a shared non-concurrent volume group, an appropriate node is chosen, the volume group on that node is varied on, and the command executes there. The volume group is varied off upon successfull completion. -g ResourceGroup Generates a list of nodes participating in the resource group on which the cl_chlv command will be executed. -n NodeList Specifies the node(s) on which the C-SPOC command will be executed. You can specify more than one node by separating each node in the list with a comma. -a Position Sets the intra-physical volume allocation policy (the position of the logical partitions on the physical volume). The Position variable is represented by one of the following: m Allocates logical partitions in the outer middle section of each physical volume. This is the default position. c Allocates logical partitions in the center section of each physical volume. -e Allocates logical partitions in the outer edge section of each physical volume. ie Allocates logical partitions in the inner edge section of each physical volume. im Allocates logical partitions in the inner middle section of each physical volume. -b BadBlocks Sets the bad-block relocation policy. The BadBlocks variable is represented by one of the following: y Causes bad-block relocation to occur. n Prevents bad block relocation from occurring. -d Schedule Sets the scheduling policy when more than one logical partition is written. The Schedule variable is represented by one of the following: p Establishes a parallel scheduling policy. s Establishes a sequential scheduling policy. -e Range Sets the inter-physical volume allocation policy (the number of physical volumes to extend across, using the volumes that provide the best allocation). The value of the Range variable is limited by the Upperbound variable, set with the -u flag, and is represented by one of the following: -x Allocates logical partitions across the maximum number of physical volumes. -m Allocates logical partitions across the minimum number of physical volumes. -L label Sets the logical volume label. The maximum size of the Label variable is 127 characters. -n NewLogicalVolume Changes the name of the logical volume to that specified by the NewLogicalVolume variable. Logical volume names must be unique systemwide and can range from 1 to 15 characters. -p Permission Sets the access permission to read-write or read-only. The Permission variable is represented by one of the following: w Sets the access permission to read-write. r Sets the access permission to read-only. -r Relocate Sets the reorganization flag to allow or prevent the relocation of the logical volume during reorganization. The Relocate variable is represented by one of the following: y Allows the logical volume to be relocated during reorganization. n Prevents the logical volume from being relocated during reorganization. -s Strict Determines the strict allocation policy. Copies of a logical partition can be allocated to share or not to share the same physical volume. The Strict variable is represented by one of the following: y Sets a strict allocation policy, so copies of a logical partition cannot share the same physical volume. n Does not set a strict allocation policy, so copies of a logical partition can share the same physical volume. -t Type Sets the logical volume type. The maximum size is 31 characters. -u Upperbound Sets the maximum number of physical volumes for new allocation. The value of the Upperbound variable should be between one and the total number of physical volumes. -v Verify Sets the write-verify state for the logical volume. Causes all writes to the logical volume either to be verified with a follow-up read or not to be verified with a follow-up read. The Verify variable is represented by one of the following: y Causes all writes to the logical volume to be verified with a follow-up read. n Causes all writes to the logical volume not to be verified with a follow-up read. -w MirrorWriteConsistency y Turns on mirror write consistency which insures data consistency among mirrored copies of a logical volume during normal I/O processing. n No mirror write consistency. See the -f flag of the syncvg command. -x Maximum Sets the maximum number of logical partitions that can be allocated to the logical volume. Examples 1. To change the inter-physical volume allocation policy of logical volume lv01, enter: cl_chlv -cspoc "-g resource_grp1" -e m lv01 The inter-physical volume allocation policy is set to minimum. 2. To change the type of logical volume lv03, enter: cl_chlv -cspoc "-g resource_grp1" -t copy lv03 3. To change the permission of logical volume lv03 to read-only, enter: cl_chlv -cspoc "-g resource_grp1" -p r lv03 Logical volume lv03 now has read-only permission. 4. To change the type to paging and the maximum number of physical volumes for logical volume lv03, enter: cl_chlv -cspoc "-g resource_grp1" -t paging -u 10 lv03 The change in the type of logical volume takes effect immediately, but the change in the maximum number of physical volumes does not take effect until a new allocation is made. 5. To change the allocation characteristics of logical volume lv07, enter: cl_chlv -cspoc "-g resource_grp1" -a e -e x -r y -s n -u 5 lv07 6. To specify one or more cluster nodes on which to execute the cl_chlv command, enter: cl_chlv -cspoc "-n node1,node2, ... " -n newlv oldlv Note: When using the cl_chfs command to change a file system's mount point, be aware that the mount point must also be changed in the resource group to avoid errors generated during resynchronization or failover. Implementation Specifics This command is part of High Availability Cluster Multi-Processing for AIX (HACMP for AIX). You must be a root user to execute C-SPOC commands. Files /tmp/cspoc.log File contains a log of all distributed commands run, along with status, error messages, and timestamps. Suggested Reading HACMP for AIX Administration Guide HACMP for AIX Installation Guide Related Information The chlv, clvaryonvg and rsh commands. ca kcA$0i7*]7P`7!D./usr/share/man/cat1/cl_clstop.1ros.1$$ cl_clstop Command ***************** Purpose Stops cluster daemons using the System Resource Controller (SRC) facility. Syntax cl_clstop [-cspoc "[-f] [-n NodeList | -g ResourceGroup]"] -f cl_clstop [-cspoc "[-f] [-n NodeList | -g ResourceGroup]"] -g [-s] [-y] [-N | -R | -B] cl_clstop {-cspoc "[-f] {-n NodeList | -g ResourceGroup}"} -gr [-s] [-y] [-N | -R | -B] Description The cl_clstop command shuts down cluster services across cluster nodes. By default, the cl_clstop command stops cluster services across all cluster nodes; however, the system administrator can specify the list of nodes on which to stop cluster services. The cl_clstop command stops the cluster daemons using the SRC facility. The daemon can be stopped either gracefully or forcefully. The command optionally removes automatic start on reboot through its inittab entry. A node list must be specified if the cluster daemons are being shut down gracefully with takeover. By default, cl_clstop requires that all nodes cluster or all nodes in a given node list be accessible over the network and powered up; otherwise, cl_clstop fails. This command uses the AIX rsh facility to propagate commands to other nodes and requires the proper rsh access to all nodes. Thus each node must have a /.rhosts file which includes references to all interfaces for each cluster node. The /.rhosts file must reside in the root directory, and its mode must be 0600. Flags -cspoc Argument used to specify the use of one of the following C-SPOC options: -f Forces C-SPOC command to skip default verification. If this flag is set and a cluster node is not accessible, cl_clstop reports a warning and continues execution on the other nodes. -n NodeList Shuts down cluster services on the nodes specified in the node list. -g ResourceGroup Generates a list of nodes participating in the resource group on which the cl_clstop command will be executed. -f Forced shutdown. Cluster daemons should terminate without running any local procedures. -g Graceful shutdown with no takeover. -gr Graceful shutdown with the resources being released by this node and taken over by another node. The daemons should terminate gracefully, and the node should release its resources, which will then be taken over. A node list must be specified for graceful shutdown with takeover. -s Silent shutdown, specifies not to broadcast a shutdown message via /usr/sbin/wall. The default is to broadcast. -y Asks operator for confirmation before shutting down. This flag is the default. -N Shutdown now. -R Stops on susbequent system restart (removes the inittab entry). -B Stop now and on subsequent system restart. Examples 1. To shut down the cluster node gracefully with takeover on node1 (releasing the resources) without sending a warning message to users before the cluster processes are stopped and resources are released, enter: cl_clstop -cspoc "-n node1" -ysNgr 2. To forcefully and immediately shut down the Cluster on all cluster nodes (resources not released) with warning broadcasted to users before the Cluster processes are stopped, enter: cl_clstop -yNf 3. To shut down the Cluster node gracefully on all cluster nodes, and broadcasting a warning to users before the Cluster processes are stopped, enter: cl_clstop -yg Note: If you do not specify either the -g or -n options, the default action occurs on all cluster nodes. Implementation Specifics This command is part of High Availability Cluster Multi-Processing for AIX (HACMP for AIX). You must be a root user to execute C-SPOC commands. Files /usr/sbin/cluster/utilities/clstop The clstop command executable file. Suggested Reading HACMP for AIX Concepts and Facilities HACMP for AIX Administration Guide HACMP for AIX Troubleshooting Guide Related Information The clstop and rsh commands. kdA$R0i7*]7P`7!DR./usr/share/man/cat1/cl_lsfs.11$$ cl_lsfs Command *************** Purpose Displays the characteristics of shared file systems. Syntax cl_lsfs -cspoc "[-f] [-g ResourceGroup | -n NodeList]" [-q] [-c | -l] FileSystem ... cl_lsfs [FileSystem] ... Description The cl_lsfs command displays characteristics of shared file systems. The characteristics include mount points, automatic mounts, permissions, and file system size. The FileSystem parameter reports on a specific shared file system. The following subsets can be queried for a listing of the following characteristics: * All shared file systems in the cluster * All file systems shared by the participating nodes in a specified resource group * One or more individual shared file systems This command uses the AIX rsh facility to propagate commands to other nodes and requires the proper rsh access to all nodes. Thus each node must have a /.rhosts file that includes references to interfaces for all cluster nodes. The /.rhosts file must reside in the root directory, and its mode must be 0600. You can use the System Management Interface Tool (SMIT) to run this command. To use SMIT, enter: smit cl_lsfs Flags -cspoc Argument used to specify the use of one of the following C-SPOC options: -f The cl_lsfs command is run on all nodes that have access to the volume group containing the filesystem. The output from each node is displayed versus only the output from nodes with the volume group varied on. -g ResourceGroup Generates a list of nodes participating in the resource group on which the ch_lsfs command will be executed. -n NodeList Specifies the node(s) on which the C-SPOC command will be executed. You can specify more than one node by separating each node in the list with a comma. -c Specifies that the output should be in colon format. -l Specifies that the output should be in list format. -q Queries the logical volume manager (LVM) for the logical volume size (in 512-byte blocks) and queries the JFS superblock for the file system size, the fragment size, the compression algorithm (if any), and the number of bytes per i-node (nbpi). This information is displayed in addition to other file system characteristics reported by the lsfs command. Example 1. To display characteristics about all shared file systems in the cluster, enter: cl_lsfs 2. Display (in colon format) characteristics of the file systems shared amongst the participating nodes in resource_grp1. cl_lsfs -cspoc "-g resource_grp1" -c /jupiterfs 3. To specify one or more cluster nodes on which to execute the cl_lsfs command, enter: cl_lsfs -cspoc "-n node1,node2, ... " /jupiterfs Note: If you do not specify either the -g or -n options, the default action occurs on all cluster nodes. Implementation Specifics This command is part of High Availability Cluster Multi-Processing for AIX (HACMP for AIX). You must be a root user to execute C-SPOC commands. Files /etc/filesystems Lists the known file systems and defines their characteristics. /tmp/cspoc.log File contains a log of all distributed commands run, along with status, error messages, and timestamps. Suggested Reading HACMP for AIX Administration Guide HACMP for AIX Troubleshooting Guide Related Information The cllsfs, lsfs and rsh commands. c kꖶfA$A0i7*]7P`7!DA./usr/share/man/cat1/cl_lsgroup.1ros.1$$ cl_lsgroup Command ****************** Purpose Displays attributes of groups that exist on an HACMP cluster. Syntax cl_lsgroup [-cspoc "[-f] [-g ResourceGroup | -n NodeList]"] [-c | -f] [-a attr attr .. ] {"ALL" | group1,group2 ... } Description The cl_lsgroup command displays group attributes for groups that exist on the cluster nodes. Since no default parameter exists, you must enter the ALL keyword to list all the groups in the cluster and their attributes. Given a group name, cl_lsgroup displays information about groups with the defined name that exist in the cluster. All attributes described in the underlying AIX chgroup command appear. If the cl_lsgroup command cannot read one or more attributes, it lists as much information as is possible. To view a selected attribute, use the -a List flag. Note: If you have a Network Information Service (NIS) database installed on any cluster node, some user information may not appear when you use the cl_lsgroup command. If a group name is given and a group with that name does not exist on a node, cl_lsgroup reports the warning and continues to execute on the other cluster nodes. This command uses the AIX rsh facility to propagate commands to other nodes and requires the proper rsh access to all nodes. Thus each node must have a /.rhosts file which includes interfaces references for each node. The /.rhosts file must reside in the root directory, and its mode must be 0600. You can use the System Management Interface Tool (SMIT) to run this command. To use SMIT, enter: smit cl_lsgroup Flags -cspoc Argument used to specify the use of one of the following C-SPOC options: -f This option has no effect when used with the cl_lsgroup command. -g ResourceGroup Specifies the name of the resource group whose participating nodes share the defined group. -n NodeList Specifies the node(s) on which the C-SPOC command will be executed. You can specify more than one node by separating each node in the list with a comma. -a attribute_list Specifies the attributes to display. The List parameter can include any attribute defined in the chgroup command, and requires a blank space between attributes. If you specify an empty list using only the -a flag, only the group names are listed. -c Displays the attributes for each group in colon-separated records, as follows: # name: attribute1: attribute2: ... Group: value1: value2: ... -f Displays the group attributes in stanzas. Each stanza is identified by a group name. Each Attribute=Value pair is listed on a separate line: group: attribute1=value attribute2=value attribute3=value Examples 1. To display the attributes of the finance group from all cluster nodes enter: cl_lsgroup finance 2. To display in stanza format the id, members (users), and administrators (adms) of the finance group from all cluster nodes, enter: cl_lsgroup -f -a id users adms finance 3. To display the attributes of all the groups from all the cluster nodes in colon-separated format, enter: cl_lsgroup -c ALL All the attribute information appears, with each attribute separated by a blank space. Implementation Specifics This command is part of High Availability Cluster Multi-Processing for AIX (HACMP for AIX). You must be a root user to execute C-SPOC commands. Files /tmp/cspoc.log File contains a log of all distributed commands run, along with status, error messages, and timestamps. /etc/group Contains the basic attributes of groups. /etc/security/group Contains the extended attributes of groups. Suggested Reading HACMP for AIX Administration Guide HACMP for AIX Troubleshooting Guide Related Information The chgroup, lsgroup and rsh commands. tribute khA$0i7*]7P`7!D./usr/share/man/cat1/cl_lslv.1.$$ cl_lslv Command *************** Purpose Displays shared logical volume attributes. Syntax cl_lslv [-cspoc "[-f] [-g ResourceGroup | -n NodeList]"] [-l | -m] LogicalVolume Description The cl_lslv command displays the characteristics and status of a shared logical volume from the cluster node that currently has the logical volume's underlying shared volume group varied on. If none of the cluster nodes has the shared volume group varied on, cl_lslv fails. The LogicalVolume parameter can be a logical volume name or logical volume ID. The logical volume must reside on a volume group shared by all participating nodes in the specified resource group. Note: If the cl_lslv command cannot find information for a field in the Device Configuration Database, it inserts a question mark (?) in the value field. For example, if no information for the LABEL field exists, the following is displayed: LABEL: ? The command attempts to obtain as much information as possible from the description area when it is given a logical volume identifier. This command uses the AIX rsh facility to propagate commands to other nodes and requires the proper rsh access to all nodes. Thus each node must have a /.rhosts file which includes references to all interfaces for each cluster node. The /.rhosts file must reside in the root directory, and its mode must be 0600. You can use the System Management Interface Tool (SMIT) to run this command. To use SMIT, enter: smit cl_lslv Flags -cspoc Argument used to specify the use of one of the following C-SPOC options: -f This command will not fail if at least one node which has access to the underlying volume group is accessible. A warning is issued for nodes that can't be reached. -g ResourceGroup Generates a list of nodes participating in the resource group on which the cl_lslv command will be executed. -n NodeList Specifies the node(s) on which the C-SPOC command will be executed. You can specify more than one node by separating each node in the list with a comma. -l Lists information for each physical volume in the shared logical volume. Refer to the lslv command for information about the fields displayed. -m Lists information for each logical partition. Refer to the lslv command for information about the fields displayed. If no flags are specified, information about the shared logical volume and its underlying shared volume group is displayed. Refer to the lslv command for information about the fields displayed. Examples 1. To display information about the shared logical volume lv03, enter: cl_lslv -cspoc "-g resource_grp1" lv03 Information about logical volume lv03, its logical and physical partitions, and the volume group to which it belongs is displayed. 2. To display information about all logical volumes, using the identifier, enter: cl_lslv -cspoc "-n node1,node2" -l 00000256a81634bc.2 All available characteristics and status of this logical volume are displayed. Implementation Specifics This command is part of High Availability Cluster Multi-Processing for AIX (HACMP for AIX). You must be a root user to execute C-SPOC commands. Files /tmp/cspoc.log File contains a log of all distributed commands run, along with status, error messages, and timestamps. Suggested Reading HACMP for AIX Administration Guide HACMP for AIX Troubleshooting Guide Related Information The cllslv, lslv and rsh commands. ands k:"iA$0i7*]7P`7!D./usr/share/man/cat1/cl_lsuser.1ros.1$$ cl_lsuser Command ***************** Purpose Displays user account attributes for users that exist on an HACMP cluster. Syntax cl_lsuser [-cspoc "-f [-g ResourceGroup | -n NodeList]"] [-c | -f] [-a List] {ALL | Name [,Name] ...} Description The cl_lsuser command displays user attributes for users that exist on cluster nodes. You can use this command to list all attributes for all users on all nodes, or to list attributes of specific users. By default, the cl_lsuser command displays all user attributes. To view selected attributes, use the -a List flag. Refer to the underlying AIX chuser command for the list of user attributes. If one or more attributes cannot be read, the cl_lsuser command lists as much information as possible. Given a user name, cl_lsuser displays information about all users with that specific on all cluster nodes. To see the attributes of all users in the cluster, you must enter the ALL keyword in place of a user name. Note: If you have a Network Information Service (NIS) database installed on any node, some user information may not appear when you use the cl_lsuser command. If a user name is given and the user does not exist on a node, cl_lsuser reports a warning and continues execution on the other cluster nodes. This command uses the AIX rsh facility to propagate commands to other nodes and requires the proper rsh access to all nodes. Thus each node must have a /.rhosts file which includes references to all interfaces for each cluster node. The /.rhosts file must reside in the root directory, and its mode must be 0600. You can use the System Management Interface Tool (SMIT) to run this command. To use SMIT, enter: smit cl_lsuser Flags -cspoc Argument used to specify the use of one of the following C-SPOC options: -f This option has no effect when used with the cl_lsuser command. -g ResourceGroup Generates a list of nodes participating in the resource group on which the cl_lsuser command will be executed. -n NodeList Specifies the node(s) on which the C-SPOC command will be executed. You can specify more than one node by separating each node in the list with a comma. Note: If you do not specify either the -g or -n options, the default action occurs on all cluster nodes. -a attribute_list Specifies the attributes to display. The List variable can include any attribute defined in the chuser command and requires a blank space between attributes. If you specify an empty list, only the user names are displayed. -c Displays the user attributes in colon-separated records, as follows: # name: attribute1: attribute2: ... User: value1: value2: ... -f Displays the output in stanzas, with each stanza identified by an user name. Each Attribute=Value pair is listed on a separate line: user: attribute1=value attribute2=value attribute3=value Examples 1. To display the user id and group-related information about the smith account in stanza form from all cluster nodes, enter: cl_lsuser -f -a id pgrp groups admgroups smith 2. To display all attributes of user smith in the default format on specific cluster nodes, enter: cl_lsuser -cspoc "-n node1,node2" smith All attribute information appears, with each attribute separated by a blank space. 3. To display all attributes of all the users on the cluster, enter: cl_lsuser ALL All attribute information appears, with each attribute separated by a blank space. 4. To list users on nodes associated with a specific resource group, enter: cl_lsuser -cspoc "-g res_grp1" joe,mary,robert Implementation Specifics This command is part of High Availability Cluster Multi-Processing for AIX (HACMP for AIX). You must be a root user to execute C-SPOC commands. Files /tmp/cspoc.log File contains a log of all distributed commands run, along with status, error messages, and timestamps. /etc/passwd Contains basic user information. /etc/security/limits Defines resource quotas and limits for each user. /etc/security/user Contains the extended attributes of users. /etc/security/environ Contains the environment attributes of users. /etc/group Contains basic group attributes. /etc/security/audit/config Contains the audit configuration files. Suggested Reading HACMP for AIX Administration Guide HACMP for AIX Troubleshooting Guide Related Information The chuser, lsuser and rsh commands. use k kA$,0i7*]7P`7!E,./usr/share/man/cat1/cl_lsvg.11$$ cl_lsvg Command *************** Purpose Displays information about shared volume groups. Syntax cl_lsvg [-cspoc "[-f] [-g ResourceGroup | -n NodeList]"] [-o] -n VolumeGroup ... cl_lsvg [-cspoc "[-f] [-g ResourceGroup | -n NodeList]"] [-i] [-M | -l | -p] VolumeGroup ... Description The cl_lsvg command displays information about shared volume groups. If no volume group name is given, a list of all shared volume groups is displayed. If a resource group is given, a list of volume groups shared by the participating nodes in the resource group is displayed. If the volume group name is given, the cl_lsvg command displays information from the cluster node that currently has the shared volume group varied on. If none of the cluster nodes has the volume group varied on, cl_lsvg fails. When information from the Device Configuration database is unavailable, some fields will contain a question mark (?) in place of the missing data. This command uses the AIX rsh facility to propagate commands to other nodes and requires the proper rsh access to all nodes. Thus each node must have a /.rhosts file which includes references to all interfaces for each cluster node. The /.rhosts file must reside in the root directory, and its mode must be 0600. You can use the System Management Interface Tool (SMIT) to run the cl_lsvg command. To use SMIT, enter: smit cl_lsvg Flags -cspoc Argument used to specify the use of one of the following C-SPOC options: -f This option has no effect when used with the cl_lsvg command. -g ResourceGroup Generates a list of nodes participating in the resource group on which the cl_lsvg command will be executed. -n NodeList Specifies the node(s) on which the C-SPOC command will be executed. You can specify more than one node by separating each node in the list with a comma. Note: If you do not specify either the -g or -n options, the default action occurs on all cluster nodes. -p Lists the following information for each physical volume within the group specified by the VolumeGroup parameter: Physical volume: A physical volume within the group. PVstate: State of the physical volume. Total PPs: Total number of physical partitions on the physical volume. Free PPs Number of free physical partitions on the physical volume. Distribution The number of physical partitions allocated within each section of the physical volume: outer edge, outer middle, center, inner middle, and inner edge of the physical volume. -l Lists the following information for each logical volume within the group specified by the VolumeGroup parameter: LV: A logical volume within the volume group. Type: Logical volume type. LPs: Number of logical partitions in the logical volume. PPs: Number of physical partitions used by the logical volume. PVs: Number of physical volumes used by the logical volume. -M Lists the following fields for each logical volume on the physical volume: PVname: PPnum [LVname: LPnum [:Copynum] [PPstate]] PVname: Name of the physical volume as specified by the system. PPnum: Physical partition number. Physical partition numbers can range from 1 to 1016. -o Lists only the active volume groups (those that are varied on). An active volume group is one that is available for use. -i Reads volume group names from standard input. Refer to the lsvg command for the information displayed if no flags are specified. Examples 1. To display the names of all active shared volume groups in the cluster, enter: cl_lsvg -o 2. To display the names of all shared volume groups in the cluster, enter: cl_lsvg 3. To display information about the shared volume group vg02, enter: cl_lsvg -cspoc "-g resource_grp1" vg02 4. To display physical information about volume groups on specific nodes, enter: cl_lsvg -cspoc "-n node1,node2" -M vg02 The characteristics and status of both the logical and physical partitions of volume groups with the name vg02 are displayed. Implementation Specifics This command is part of High Availability Cluster Multi-Processing for AIX (HACMP for AIX). You must be a root user to execute C-SPOC commands. Files /tmp/cspoc.log File contains a log of all distributed commands run, along with status, error messages, and timestamps. Suggested Reading HACMP for AIX Administration Guide HACMP for AIX Troubleshooting Guide Related Information The cllsvg, lsvg and rsh commands. ther kȶlA$0i7*]7P`7!D./usr/share/man/cat1/cl_mkgroup.1ros.1$$ cl_mkgroup Command ****************** Purpose Creates a new group on all nodes in an HACMP cluster. Syntax cl_mkgroup [-cspoc "[-f] [-g ResourceGroup | -n NodeList]"] [-a] [-A] [Attribute=Value ...] Group Description Given the group name and a list of attributes, the cl_mkgroup command creates a new group on all cluster nodes. The Group parameter must be a unique string of eight bytes or less and cannot be the ALL or default keywords. By default, the cl_mkgroup command creates a standard group on all the nodes. To create an administrative group, specify the -a flag. But you must be a root user to create an administrative group. By default, the cl_mkgroup command checks if a group with the given name already exists in the cluster. If so, the command fails. The cl_mkgroup command also ensures that the group id, if provided, is available on all nodes. If the id is in use, the command fails. If no id is provided, cl_mkgroup will choose an id that is available on all nodes. Note that a ceiling of 250,000 is enforced; group id's above this value are not supported. By default, cl_mkgroup requires that all nodes in the HACMP cluster must be accessible over the network and powered up; otherwise, cl_mkgroup fails. Note: if any node in the cluster is a member of an SP with the usermgmt_config option set to 'true', this operation will not be allowed. This command uses the AIX rsh facility to propagate commands to other nodes and requires the proper rsh access to all nodes. Thus each node must have a /.rhosts file which includes references to all interfaces for each cluster node. The /.rhosts file must reside in the root directory, and its mode must be 0600. You can use the System Management Interface Tool (SMIT) to run this command. To use SMIT, enter: smit cl_mkgroup Flags -cspoc Argument used to specify the use of one of the following C-SPOC options: -f If this flag is specified and a cluster node is not accessible, cl_mkgroup reports a warning and continues execution on the other cluster nodes. If the flag is specified and the group already exists on a node, cl_mkgroup reports a warning and continues execution on the other cluster nodes. -g ResourceGroup Generates a list of nodes participating in the resource group on which the cl_mkgroup command will be executed. -n NodeList Specifies the node(s) on which the C-SPOC command will be executed. You can specify more than one node by separating each node in the list with a comma. Note: If you do not specify either the -g or -n options, the default action occurs on all cluster nodes. -a Creates an administrative group. -A Sets the group administrator to the person who invoked the cl_mkgroup command. Attribute=Value Initializes a group with a specific attribute. See the chgroup command for more information about the group attributes. Examples 1. To create a new group account called finance on all cluster nodes, enter: cl_mkgroup -cspoc "-n node1,node2" finance 2. To create a new administrative group account called payroll on all cluster nodes, enter: cl_mkgroup -cspoc "-g resgrp1" -a payroll Implementation Specifics This command is part of High Availability Cluster Multi-Processing for AIX (HACMP for AIX). You must be a root user to execute C-SPOC commands. Files /tmp/cspoc.log File contains a log of all distributed commands run, along with status, error messages, and timestamps. /etc/group Contains the basic attributes of groups. /etc/security/group Contains the extended attributes of groups. /etc/passwd Contains basic user information. /etc/security/passwd Contains password information. Suggested Reading HACMP for AIX Administration Guide HACMP for AIX Troubleshooting Guide Related Information The chgroup, mkgroup and rsh commands. rceGr kBnA$0i7*]7P`7!E./usr/share/man/cat1/cl_mkuser.1ros.1$$ cl_mkuser Command ***************** Purpose Creates a new user account on all nodes in an HACMP cluster. Syntax cl_mkuser [-cspoc "[-f] [-g ResourceGroup | -n NodeList]"] [-a] [Attribute=Value ...] Name Description Given the user name and a list of attributes, the cl_mkuser command creates a new user on all cluster nodes. By default, the cl_mkuser command checks if a user with the given user name already exists in the cluster. If so, cl_mkuser command fails. Also cl_mkgroup requires that all nodes in the HACMP cluster be accessible over the network and powered up; otherwise, it fails. The Name parameter must be a unique string of eight-bytes or less. The cl_mkuser command creates a standard user account. To create an administrative user account, specify the -a flag. The cl_mkuser command creates a standard user account. To create an administrative user account, specify the -a flag. The cl_mkuser command does not create password information for the user. Until the initial password is set using the passwd command or the pwdadm command, the password field in the /etc/passwd file is set to * (an asterisk) to indicate that no valid password exists. The new user account is disabled until authentication information is added to the /etc/security/passwd file. The cl_mkuser command also ensures that the user id, if provided, is available on all nodes. If the id is in use, the command fails. If no id is provided, cl_mkuser will choose an id that is available on all nodes. Note that a ceiling of 250,000 is enforced; user id's above this value are not supported. Note: if any node in the cluster is a member of an SP with the usermgmt_config option set to 'true', this operation will not be allowed. This command uses the AIX rsh facility to propagate commands to other nodes, and requires the proper rsh access to all nodes. Thus each node must have a /.rhosts file which includes references to all interfaces for each cluster node. The /.rhosts file must reside in the root directory, and its mode must be 0600. You can use the System Management Interface Tool (SMIT) to run this command. To use SMIT, enter: smit cl_mkuser Flags -cspoc Argument used to specify the use of one of the following C-SPOC options: -f If this flag is specified and a cluster node is not accessible, cl_mkuser reports a warning and continues execution on the other cluster nodes. Or, if the flag is specified and the user already exists on a node, cl_mkuser reports a warning and continues execution on the other cluster nodes. -g ResourceGroup Generates a list of nodes participating in the resource group on which the cl_mkuser command will be executed. -n NodeList Specifies the node(s) on which the C-SPOC command will be executed. You can specify more than one node by separating each node in the list with a comma. Note: If you do not specify either the -g or -n options, the default action occurs on all cluster nodes. -a Specifies that the user is an administrator. Attribute=Value Initializes an user attribute. Refer to the chuser command for the valid attributes and values. Examples 1. To create the davis user account with the default values in the /usr/lib/security/mkuser.default file on all cluster nodes, enter: cl_mkuser davis 2. To create davis as an administrator on nodes participating in resgrp1, enter: cl_mkuser -cspoc "-g resgrp1" -a davis 3. To create the davis user account on node1 and node2 and to set the su attribute to a value of false, enter: cl_mkuser -cspoc "-n node1,node2" su=false davis Implementation Specifics This command is part of High Availability Cluster Multi-Processing for AIX (HACMP for AIX). You must be a root user to execute C-SPOC commands. Files /tmp/cspoc.log File contains a log of all distributed commands run, along with status, error messages, and timestamps. /usr/lib/security/mkuser.default Contains the default values for new users. /etc/passwd Contains basic user attributes. /etc/security/user Contains the extended user attributes. /etc/security/passwd Contains password information. /etc/security/limits Defines resource quotas and limits for each user. /etc/security/environ Contains the environment attributes of users. /etc/group Contains basic group attributes. /etc/security/group Contains the extended group attributes. /etc/security/.ids Contains standard and administrative user IDs and group IDs. Suggested Reading HACMP for AIX Administration Guide HACMP for AIX Installation Guide HACMP for AIX Troubleshooting Guide Related Information The chuser, mkuser and rsh commands. kjA$S0i7d]7P`7!DS./usr/share/man/cat1/cl_nodecmd.1ros.1$$cl_nodecmd Command ***************** Purpose Runs a given command in parallel on a given set of nodes. Syntax cl_nodecmd [-cspoc "[-f] [-q] [-n nodelist] | [-g resource group]" ] command args Description The cl_nodecmd command provides a Cluster Administrator with the ability to remotely execute a given command on a list of cluster nodes. The command is run in parallel on all nodes in the list. The cl_nodecmd command returns 0 if the execution of "command" on all specified nodes is successful, otherwise it returns 1. The default nodelist is the list of all nodes in the cluster. Flags -cspoc Argument used to specify the following C-SPOC options: -f Forces cl_nodecmd to skip HACMP version compatibility checks and node accessibility verification. -q Quiet mode. All standard output is suppressed. -n nodelist Execute underlying command across nodes in nodelist. Node names should be separated by a comma and have no spaces between them. -g resource group The nodelist is determined from the list of nodes participating in the resource group. command The command to be run on all nodes in the nodelist. args Any arguments necessary with the user_command. Examples 1. To run the "lspv" command on all cluster nodes, enter: cl_nodecmd lspv 2. To run the "lsvg rootvg" command on nodes "node1" and "node2", suppressing standard output, enter: cl_nodecmd -cspoc "-n node1,node2" lsvg rootvg Implementation Specifics This command is part of High Availability Cluster Multi-Processing for AIX (HACMP for AIX). Files /usr/sbin/cluster/utilities/cl_nodecmd cl_nodecmd command executable file Suggested Reading HACMP for AIX Concepts and Facilities HACMP for AIX Administration Guide Prerequisite Information Related Information The clverify command. Y k `pA$0i7*]7P`7!D./usr/share/man/cat1/cl_rc.cluster.1s.1$$ cl_rc.cluster Command ********************* Purpose Sets up the operating system environment and starts the cluster daemons on cluster nodes. Syntax cl_rc.cluster [-cspoc "[-f] [-n NodeList | -g ResourceGroup]"] [-boot] [-l] [-i] [-b] [-N | -R | -B] Description The cl_rc.cluster command starts cluster services on all cluster nodes in an HAMCP environment, and it sets the operating system environment. The system administrator can, however, specify the list of nodes on which to start cluster services. The cl_rc.cluster command first sets the operating system environment by making necessary changes to the inittab file. Then it runs /etc/rc.net, if applicable, to set up the network configuration and to verify that the System Resource Controller (SRC), System Logger, portmapper, and inetd daemons are started and active (for example, it invokes harc.net). After setting network options, it uses the SRC to start the cluster and lock group daemons. By default, the cluster group daemons (clinfo, clsmuxpd, and clstrmgr) are started on servers, and clinfo is started on clients. The cl_rc.cluster command requires that all nodes in the HACMP cluster or in a given node list be accessible over the network and powered on; otherwise cl_clstop. This command uses the AIX rsh facility to propagate commands to other nodes and requires the proper rsh access to all nodes. Thus each node must have a /.rhosts file which includes references to all interfaces for each cluster node. The /.rhosts file must reside in the root directory, and its mode must be 0600. Flags -cspoc Argument used to specify the use of one of the following C-SPOC options: -f Specifies that if a cluster node is not accessible, cl_rc.cluster reports a warning and continues execution on the other cluster nodes. -n NodeList Specifies the nodes on which to start the cluster daemons. You can specify more than one node by separating each node in the list with a comma. -g ResourceGroup Generates a list of nodes participating in the resource group on which the cl_rc.cluster command will be executed. Note: If you do not specify either the -g or -n options, the default action occurs on all cluster nodes. -boot Configures the service adapter to be on its boot address if IPAT is enabled. -l Starts the Cluster Lock Manager daemon (cllockd) with its default option. -i Starts the Cluster Information (clinfo) daemon with its default options. -b Broadcasts the startup. -N Starts the daemons Now (no inittab change). -R Starts the HACMP daemons on system restart only (the HACMP start-up command is added to inittab file). -B Starts the daemons Now and adds the HACMP entry to the inittab file. -f Forced startup. Cluster daemons should initialize running local procedures. Examples 1. To start the cluster with cluster lock services and to broadcast the event, enter: cl_rc.cluster -cspoc "-n node1,node2" -boot -l -b 2. To start the cluster with clinfo running on all the cluster nodes, enter: cl_rc.cluster -boot -i 3. To start the cluster with clinfo running on all the cluster nodes, enter: cl_rc.cluster -cspoc "-g resgrp1" -boot -i -N Implementation Specifics This command is part of High Availability Cluster Multi-Processing for AIX (HACMP for AIX). You must be a root user to execute C-SPOC commands. Files /usr/sbin/cluster/etc/rc.cluster The rc.cluster command script file. /etc/inittab The cluster initialization script. Suggested Reading HACMP for AIX Administration Guide HACMP for AIX Troubleshooting Guide Related Information The rc.cluster script and rsh command. H kqA$0i7*]7P`7!D./usr/share/man/cat1/cl_rmfs.1t$$ cl_rmfs Command *************** Purpose Removes a shared file system. Syntax cl_rmfs [-cspoc "[-f] [-g ResourceGroup | -n NodeList]"] [-r] FileSystem Description Attention: This command is not supported for concurrent volume groups. The cl_rmfs command removes a shared file system on the node which has the file systems's underlying shared volume group varied on. The file system must reside on a volume group that is shared by all participating nodes in the specified resource group. The definition of the volume group will be updated on all nodes in the resource group immediately. The cl_rmfs command removes both the shared logical volume, the underlying file system indicated, and the associated stanza in the /etc/filesystems file only on the node with the volume group varied on. It also removes the metadata from the VGDA on the physical volume. The FileSystem parameter specifies the file system to be removed. The shared file system must be removed as a resource from the resource group configuration before issuing the cl_rmfs command; otherwise, errors can occur during resynchronization or failover. If the command is unable to remove the shared file system--if the underlying AIX rmfs command fails-- cl_rmfs also fails. As long as the underlying volume group, or another file system on the volume group is configured as a resource in a resource group, the cl_rmfs command causes the definition of the underlying shared volume group to be updated upon takeover. If the underlying volume group is no longer under HACMP control, the clvaryonvg command must be run on the other cluster nodes to synchronize the volume group definition, that is to reflect the removal of the file system. By default, cl_rmfs requires that all nodes in the HACMP cluster be accessible over the network and powered up; otherwise, cl_rmfs fails. This command uses the AIX rsh facility to propagate commands to other nodes and requires the proper rsh access to all nodes. Thus each node must have a /.rhosts file which includes references to all interfaces for each cluster node. The /.rhosts file must reside in the root directory, and its mode must be 0600. You can use the System Management Interface Tool (SMIT) to run this command. To use SMIT, enter: smit cl_rmfs Flags -cspoc Argument used to specify the use of one of the following C-SPOC options: -f The command will not fail if at least one node which has access to the underlying volume group is accessible. A warning is issued for nodes that cannot be reached. If no node has the volume group varied on, and it is a shared non-concurrent volume group, an appropriate node is chosen, the volume group on that node is varied on, and the command executes there. The volume group is varied off upon successfull completion. -g ResourceGroup Generates a list of nodes participating in the resource group on which the cl_rmfs command will be executed. -n NodeList Specifies the node(s) on which the C-SPOC command will be executed. You can specify more than one node by separating each node in the list with a comma. Note: If you do not specify either the -g or -n options, the default action occurs on all cluster nodes. FileSystem Specifies the shared file system to be removed. Examples 1. To remove the /test file system, enter: cl_rmfs -cspoc "-g resource_grp1" /test This removes the /test file system, its entry in the /etc/filesystems file, and the underlying logical volume from the cluster node in resource_grp1 that currently has the /test file system's volume group varied on. 2. To remove remove a file system on a specific node, enter: cl_rmfs -cspoc "-n node1,node2" /test Implementation Specifics This command is part of High Availability Cluster Multi-Processing for AIX (HACMP for AIX). You must be a root user to execute C-SPOC commands. Files /tmp/cspoc.log File contains a log of all distributed commands run, along with status, error messages, and timestamps. Suggested Reading HACMP for AIX Administration Guide HACMP for AIX Troubleshooting Guide Related Information The clvaryonvg, rmfs and rsh commands. k2sA$# 0i7+]7P`7!D# ./usr/share/man/cat1/cl_rmgroup.1.1s.1$$ cl_rmgroup Command ****************** Purpose Removes a group from all cluster nodes. Syntax cl_rmgroup [-cspoc "[-f] [-g ResourceGroup | -n NodeList]"] Name Description The cl_rmgroup command removes a group specified by the Name parameter from all cluster nodes. The group name is a string of eight bytes or less. Users who are group members are not removed from the system. If the group is the primary group for any user, you cannot remove it unless you redefine the user's primary group with the underlying AIX chuser command, which alters the /etc/passwd file. If a group with the given name does not exist on a node, the cl_rmgroup command reports a warning and continues execution on the other cluster nodes. By default, cl_rmgroup requires that all nodes in the HACMP cluster be accessible over the network and powered up; otherwise, cl_rmgroup fails. Note: if any node in the cluster is a member of an SP with the usermgmt_config option set to 'true', this operation will not be allowed. This command uses the AIX rsh facility to propagate commands to other nodes and requires the proper rsh access to all nodes. Thus each node must have a /.rhosts file which includes references to all interfaces for each cluster node. The /.rhosts file must reside in the root directory, and its mode must be 0600. You can use the System Management Interface Tool (SMIT) to run this command. To use SMIT, enter: smit cl_rmgroup Flags -cspoc Argument used to specify the use of one of the following C-SPOC options: -f Specifies that if a cluster node is not accessible, cl_rmgroup reports a warning and continues execution on the other cluster nodes. -g ResourceGroup Generates a list of nodes participating in the resource group on which the cl_rmgroup command will be executed. -n NodeList Specifies the node(s) on which the C-SPOC command will be executed. You can specify more than one node by separating each node in the list with a comma. Note: If you do not specify either the -g or -n options, the default action occurs on all cluster nodes. Example 1. To remove the finance group from all cluster nodes, enter: cl_rmgroup finance 2. To remove the finance group a specific nodes, enter: cl_rmgroup -cspoc "node1,node2" finance Implementation Specifics This command is part of High Availability Cluster Multi-Processing for AIX (HACMP for AIX). Files /tmp/cspoc.log File contains a log of all distributed commands run, along with status, error messages, and timestamps. /etc/group Contains the basic attributes of groups. /etc/security/group Contains the extended attributes of groups. Suggested Reading HACMP for AIX Administration Guide HACMP for AIX Troubleshooting Guide Related Information The rmgroup and rsh commands. re/ma kBuA$0i7+]7P`7!E./usr/share/man/cat1/cl_rmlv.1.$$ cl_rmlv Command *************** Purpose Removes a shared logical volume from a volume group. Syntax cl_rmlv [-cspoc "[-f] [-g ResourceGroup | -n NodeList]"] [-f] LogicalVolume Description The cl_rmlv command removes a shared logical volume on the node which currently has the logical volume's underlying shared volume group varied on. The logical volume must reside on a volume group that is shared by all participating nodes in the specified resource group. The definition of the volume group will be updated on all nodes in the resource group immediately. The LogicalVolume parameter can be a logical volume name or logical volume ID, and the logical volume first must be closed. If the logical volume contains a file system, the file system must be unmounted. However, removing the logical volume does not notify the operating system that the file system residing on it has been destroyed. The underlying rmfs command updates the /etc/filesystems file. Warning: This command destroys all data in the specified logical volumes. This command uses the AIX rsh facility to propagate commands to other nodes and requires the proper rsh access to all nodes. Thus each node must have a /.rhosts file which includes references to all interfaces for each cluster node. The /.rhosts file must reside in the root directory, and its mode must be 0600. If the command is unable to remove the shared logical volume, the command fails. As long as the underlying volume group (or another file system on the volume group) is configured as a resource in a resource group, the cl_rmfs command causes the definition of the underlying shared volume group to be updated upon takeover. If the underlying volume group is no longer under HACMP control, the clvaryonvg command must be run on the other cluster nodes to synchronize the volume group definition, that is to reflect the removal of the logical volume. By default, cl_rmlv requires that all nodes in the HACMP cluster must be accessible over the network and powered up; otherwise, cl_rmlv fails. You can use the System Management Interface Tool (SMIT) to run this command. To use SMIT, enter: smit cl_rmlv Flags -cspoc Argument used to specify the use of one of the following C-SPOC options: -f The command will not fail if at least one node which has access to the underlying volume group is accessible. A warning is issued for nodes that cannot be reached. If no node has the volume group varied on, and it is a shared non-concurrent volume group, an appropriate node is chosen, the volume group on that node is varied on, and the command executes there. The volume group is varied off upon successfull completion. -g ResourceGroup Generates a list of nodes participating in the resource group on which the cl_rmlv command will be executed. -n NodeList Specifies the node(s) on which the C-SPOC command will be executed. You can specify more than one node by separating each node in the list with a comma. Note: If you do not specify either the -g or -n options, the default action occurs on all cluster nodes. -f Removes the logical volumes without requesting confirmation. Examples 1. To remove logical volume lv05 without requiring user confirmation, enter: cl_rmlv -cspoc "-g resource_grp1" -f lv05 Warning: This command destroys all data in the logical volumes, and the logical volume is removed from the volume group. 2. To remove a logical volume from a specific node list, enter: cl_rmlv -cspoc "-n node1,node2" lv05 Implementation Specifics This command is part of High Availability Cluster Multi-Processing for AIX (HACMP for AIX). You must be a root user to execute C-SPOC commands. Files /tmp/cspoc.log File contains a log of all distributed commands run, along with status, error messages, and timestamps. /etc/filesystems Lists the known file systems and defines their characteristics. Suggested Reading HACMP for AIX Administration Guide HACMP for AIX Troubleshooting Guide Related Information The clvaryonvg, rmfs, rmlv and rsh commands. g knvA$i0i7+]7P`7!Di./usr/share/man/cat1/cl_rmuser.1.1s.1$$ cl_rmuser Command ***************** Purpose Removes a user account from all HACMP cluster nodes. Syntax cl_rmuser [-cspoc "[-f] [-g ResourceGroup | -n NodeList]"] [-p] Name Description Given the user name, the cl_rmuser command removes a user account from all cluster nodes. The user name must already exist as a string of eight bytes or less. The user is identified by the Name parameter. This command removes a user's attributes without removing the user's home directory and files. If the -p flag is specified, the cl_rmuser command also removes passwords and other user authentication information from the /etc/security/passwd file. If a user with the given user name does not exist on a node, the cl_rmuser command reports a warning and continues execution on the other cluster nodes. By default, cl_rmuser requires that all nodes in the HACMP cluster be accessible over the network and powered up; otherwise, cl_rmuser fails. Note: if any node in the cluster is a member of an SP with the usermgmt_config option set to 'true', this operation will not be allowed. This command uses the AIX rsh facility to propagate commands to other nodes and requires the proper rsh access to all nodes. Thus each node must have a /.rhosts file which includes references to all interfaces for each cluster node. The /.rhosts file must reside in the root directory, and its mode must be 0600. You can use the System Management Interface Tool (SMIT) to run this command. To use SMIT, enter: smit cl_rmuser Flags -cspoc Argument used to specify the use of one of the following C-SPOC options: -f Specifies that if a cluster node is not accessible, cl_rmuser reports a warning and continues execution on the other cluster nodes. -g ResourceGroup Generates a list of nodes participating in the resource group on which the cl_rmuser command will be executed. -n NodeList Specifies the node(s) on which the C-SPOC command will be executed. You can specify more than one node by separating each node in the list with a comma. Note: If you do not specify either the -g or -n options, the default action occurs on all cluster nodes. -p Removes user password information from the /etc/security/passwd file. Name The specified user name. Examples 1. To remove the user davis account and its attributes from all cluster nodes, enter: cl_rmuser davis 2. To remove the user davis account and all its attributes, including passwords and other user authentication information in the /etc/security/passwd file from all cluster nodes, enter: cl_rmuser -p davis 3. To remove the user davis account from all nodes participation in a specific resource group, enter: cl_rmuser -cspoc "-g resgrp1" davis 4. To remove the user davis from a given list of nodes, enter: cl_rmuser -cspoc "-n node1,node2" davis Implementation Specifics This command is part of High Availability Cluster Multi-Processing for AIX (HACMP for AIX). You must be a root user to execute C-SPOC commands. Files /tmp/cspoc.log File contains a log of all distributed commands run, along with status, error messages, and timestamps. /etc/passwd Contains the basic attributes of users. /etc/security/passwd Contains password information. /etc/security/limits Defines resource quotas and limits for each user. /etc/security/user Contains the extended attributes of users. /etc/security/environ Contains environment attributes of users. /etc/security/audit/config Contains audit configuration information. /etc/group Contains the basic attributes of groups. /etc/security/group Contains the extended attributes of groups. Suggested Reading HACMP for AIX Administration Guide HACMP for AIX Troubleshooting Guide Related Information The rmuser and rsh commands. Synt kTnA$ 0i7=]7P`7!D ./usr/share/man/cat1/clm_stats.1.1s.1$$ clm_stats Command ***************** Purpose Queries the HACMP Cluster Lock Manager (cllockd) for current information about the numbers of locks, resources, and memory usage. Syntax clm_stats [-t Seconds] Description The clm_stats utility queries the HACMP cluster lock manager for up-to-date status information concerning the numbers of locks, resources, and memory usage on the cluster node where the command is executed. The utility then displays this information. Note: The HACMP cluster lock manager must be active for clm_stats to report accurate information. The clm_stat only functions with the current level of HACMP. The utility queries the lock manager kernel extension and reports the following status information: * the number of locks in use * the number of locks allocated * the number of requests refused * the number of resources in use * the number of resources allocated * the available lock manager memory * the lock manager memory used * the percentage of lock manager memory used * the percent at which requests will be denied. The clm_stats utility should be run on each node in the cluster as soon as cllockd starts. Executing the command at this point lets you view the lock manager allocation as the associated database initializes. The utility, however, will not run until the kernel extension is loaded. If the clm_stats command is executed with no arguments, it returns a snapshot of current lock manager information. The -t flag can be used with the clm_stats command to specify that the utility run continuously, displaying information every specified number of seconds. Flags -t Seconds Specifies the interval in seconds between each line of output. Example: To specify that the clm_stats utility runs continuously, producing output every five seconds, enter: clm_stats -t 5 The following is output you may see: locks locks locks W res res W mem mem % % in use alloc refused in use alloc maxMB usedMB used limit 23209 32767 0 23209 24576 255 15 5 50 24263 32767 0 24263 24576 255 15 5 50 25297 32767 0 25297 32768 255 17 6 50 26350 32767 0 26350 32768 255 17 6 50 27403 32767 0 27403 32768 255 17 6 50 28457 32767 0 28457 32768 255 17 6 50 29506 32767 0 29506 32768 255 17 6 50 30554 32767 0 30554 32768 255 17 6 50 CTRL-C causes the utility to exit. Note: An asterisk appears in the W (Warning) columns if the cluster lock manager has denied locks (CLM_DENIED_NOLOCKS return code) to a client application because of memory contraints. Implementation Specifics This command is part of High Availability Cluster Multi-Processing for AIX (HACMP for AIX). Suggested Reading HACMP for AIX Troubleshooting Guide HACMP for AIX Programming Locking Applications Related Information None ot use k'xA$ 0i7+]7P`7!D ./usr/share/man/cat1/cl_updatevg.11s.1$$ cl_updatevg *********** Purpose Forces the update of each node's view of a volume group's contents. Syntax cl_updatevg -cspoc "[-f] -g ResourceGroup" VolumeGroup Description Note: The volume group must be varied off on all nodes for the cl_updatevg command to execute; otherwise, it fails. The cl_updatevg command forces each node participating in the given resource group to export and then import the volume group. The command preempts the HACMP "lazy update" feature implemented by forcing each node to update its view of the volume group at a pre-planned time, minimizing the duration of HACMP's fallover time. This command uses the AIX rsh facility to propagate commands to other nodes and requires the proper rsh access to all nodes. Thus each node must have a /.rhosts file which includes references to all interfaces for each cluster node. The /.rhosts file must reside in the root directory, and its mode must be 0600. Flags -cspoc Argument used to specify the use of one of the following C-SPOC options: -f The command will procede with only a warning if nodes that access the volume group are inaccessible. The update occurs on all nodes that are accessible. -g ResourceGroup Generates a list of nodes participating in the resource group on which the cl_updatevg command will be executed. -n NodeList Specifies the node(s) on which the C-SPOC command will be executed. You can specify more than one node by separating each node in the list with a comma. Note: If you do not specify either the -g or -n options, the default action occurs on all cluster nodes. VolumeGroup Name of the shared volume group. Example 1. To update all nodes' view of volume group vg03, enter: cl_updatevg -cspoc "-g res_grp3" vg03 2. To update all nodes' view of volume group vg03, even though one or more nodes participating in "res_grp3" are not accessible, enter: cl_updatevg -cspoc "-f -g res_grp3" vg03 Note that any nodes not currently accessible will need to be updated at some future time. Implementation Specifics This command is part of High Availability Cluster Multi-Processing for AIX (HACMP for AIX). You must be a root user to execute C-SPOC commands. Files /tmp/cspoc.log File contains a log of all distributed commands run, along with status, error messages, and timestamps. Suggested Reading HACMP for AIX Administration Guide HACMP for AIX Troubleshooting Guide Related Information The clvaryonvg, varyonvg, importvg, exportvg, and rsh commands. kK]A$ 0i7]7P`7!D ./usr/share/man/cat1/cl_rmdisk.111s.1$$ cl_rmdisk Command *************** Purpose Removes a disk definition from the selected nodes. Syntax cl_rmdisk [-cspoc "[-f] [-g ResourceGroup | -n NodeList]"] -l PVID [-d] Description The cl_rmdisk command unconfigures or both unconfigures and undefines a disk on the selected nodes. This disk is specifed as a PVID by the -l paramter. The cl_rmdisk command takes the PVID and converts it to a disk device on each of the selected nodes. Then it runs the rmdev command on each node to do the actual unconfiguration. If you specify the -d flag, the rmdev command deletes the device definition from the Customized Devices object class (undefines). If you do not specify the -d flag, the rmdev command sets the device to the Defined state (unconfigures). This command uses the AIX rsh facility to propagate commands to other nodes and requires the proper rsh access to all nodes. Thus each node must have a /.rhosts file which includes references to all interfaces for each cluster node. The /.rhosts file must reside in the root directory, and its mode must be 0600. Flags -cspoc Argument used to specify the use of one of the following C-SPOC options: -f This command will not fail if at least one node which has access to the underlying volume group is accessible. A warning is issued for nodes that can't be reached. -g ResourceGroup Generates a list of nodes participating in the resource group on which the cl_lslv command will be executed. -n NodeList Specifies the node(s) on which the C-SPOC command will be executed. You can specify more than one node by separating each node in the list with a comma. -l PVID This is a mandatory parameter. The PVID is the pysical volume identifier for the disk definition you want to remove. -d Removes the device definition from the Customized Devices object class. This flag cannot be used with the -S flag. Examples 1. To make the disk with PVID 00003367ccd3fcd9 unavailable (but defined) to all nodes in resource_grp1: cl_rmdisk -cspoc "-g resource_grp1" -l 00003367ccd3fcd9 This will make the disk unavailable on any node in resource_grp1 that has a disk device with PVID 00003367ccd3fcd9. 2. To remove the disk definition with PVID 00003367ccd3fcd9 on node1, node2 and node3: cl_rmdisk -cspoc "-n node1,node2,node3" -l 00003367ccd3fcd9 -d This will remove the disk definition on node1, node2 and node3 if the node has a disk device with PVID 00003367ccd3fcd9. Implementation Specifics This command is part of High Availability Cluster Multi-Processing for AIX (HACMP for AIX). You must be a root user to execute C-SPOC commands. Files /tmp/cspoc.log File contains a log of all distributed commands run, along with status, error messages, and timestamps. Suggested Reading HACMP for AIX Administration Guide HACMP for AIX Troubleshooting Guide Related Information The lspv, rmdev and rsh commands. ing Lo koZA$7$0i7]7P`7!E7$./usr/share/man/cat1/cl_crfs.11$$cl_crfs Command Purpose Adds a shared file system on specified nodes in the cluster. Syntax cl_crfs [-cspoc "[-f] [ -n NodeList]"] -v VfsType { -d Device } [ -l LogPartitions ] -m MountPoint [ -n NodeName ] [ -u MountGroup ] [ -A { yes | no } ] [ -p {ro | rw } ] [ -a Attribute=Value ... ] [ -t { yes | no } ] Description The cl_crfs command creates a file system on a logical volume within a previously created volume group. The volume group is then updated on the specified nodes in the cluster. Note: When creating a shared file system on a shared logical volume, at least one node in the cluster must have the parent volume group varied on. This command uses the AIX rsh facility to propagate commands to other nodes and requires the proper rsh access to all nodes. Thus each node must have a /.rhosts file which includes references to all interfaces for each cluster node. The /.rhosts file must reside in the root directory, and its mode must be 0600. You can use the System Management Interface Tool (SMIT) to run this command. To use SMIT, enter: smit cl_admin Then, select "Cluster Logical Volume Manager" and then "Shared File Systems" and "Create a Shared File System". Flags -cspoc Argument used to specify the use of one of the following C-SPOC options: -f The cl_crfs command will not fail if at least one node which has access to the underlying volume group is accessible. A warning is issued for nodes that cannot be reached. -n NodeList Specifies the node(s) on which the C-SPOC command will be executed. You can specify more than one node by separating each node in the list with a comma. -a Attribute=Value Specifies a virtual file system-dependent attribute/value pair. To specify more than one attribute/value pair, provide multiple -a Attribute=Value parameters (see example). The following attribute/value pairs are specific to the Journaled File System (JFS): -a ag={ 8 | 16 | 32 | 64 } Specifies the allocation group size in megabytes. An allocation group is a grouping of inodes and disk blocks similar to BSD cylinder groups. The default ag value is 8. This attribute only applies to AIX Version 4.2 or later. -a bf={ true | false } Specifies a large file enabled file system. See "Understanding Large File Enabled File Systems" for more information. If you do not need a large file enabled file system, set this option to false; this is the default. Specifying bf=true requires a fragment size of 4096 and compress=no. This attribute only applies to AIX Version 4.2 or later. -a compress={ no | LZ } Specifies data compression. If you do not want data to be compressed, set this option to no. The default compress value is no. Selecting compression requires a fragment size of 2048 or less. -a frag={ 512 | 1024 | 2048 | 4096 } Specifies the JFS fragment size in bytes. A file system fragment is the smallest unit of disk storage that can be allocated to a file. The default fragment size is 4096 bytes. -a logname=LVName Specifies the log logical volume name. The specified logical volume will be the logging device for the new JFS. The LVName logical volume must already exist. The default action is to use an existing logging device in the target volume group. -a nbpi={ 512 | 1024 | 2048 | 4096 | 8192 | 16384 | 32768 | 65536 | 131072 } Specifies the number of bytes per i-node (nbpi). The nbpi affects the total number of i-nodes on the file system. The nbpi value is inversely proportional to the number of i-nodes on the file system. The default nbpi value is 4096 bytes. The values 32768, 65536, and 131072 only apply to AIX Version 4.2 or later. -a size=Value Specifies the size of the JFS in 512-byte blocks. If the specified size is not evenly divisible by the physical partition size, it is rounded up to the closest number that is evenly divisible. This attribute is required when creating a JFS file system. See "Understanding JFS Size Limitations" for more information. Notes: 1.Only JFS file systems created with the default ag, bf, compress, frag, and nbpi values and a size of less than 2 gigabytes are recognized on an AIX Version 3.2 system. Furthermore, file systems created with an ag value greater than 8 is not recognized on an AIX Version 4 system much less an AIX Version 3.2 system. 2.The ag, bf, compress, frag, and nbpi attributes are set at file system creation and cannot be changed after the file system is successfully created. The size attribute defines the minimum file system size, and you cannot decrease it once the file system is created. 3.The root filesystem ( / ) cannot be compressed. 4.Some nbpi values and allocation group sizes are mutually exclusive. See "Understanding JFS Size Limitations" for information. -A Specifies whether the file system is mounted at each system restart: yes File system is automatically mounted at system restart. no File system is not mounted at system restart. -d Device Specifies the device name of a device or logical volume on which to make the file system. This is used to create a file system on an already existing logical volume. -l LogPartitions Specifies the size of the log logical volume, expressed as a number of logical partitions. This flag applies only to JFS file systems that do not already have a log device. -m MountPoint Specifies the mount point, which is the directory where the file system will be made available. Note: If you specify a relative path name, it is converted to an absolute path name before being inserted into the /etc/filesystems file. -n NodeName Specifies the remote host name where the file system resides. This flag is only valid with remote virtual file systems such as the Network File System (NFS). -p Sets the permissions for the file system. ro Read-only permissions rw Read-write permissions -t Specifies whether the file system is to be processed by the accounting subsystem: yes Accounting is enabled on the file system. no Accounting is not enabled on the file system (default value). -u MountGroup Specifies the mount group. -v VfsType Specifies the virtual file system type. Examples To make a JFS on the rootvg volume group with nondefault fragment size and nondefault nbpi, enter: cl_crfs -cspoc "-n alpha,beta" -v jfs -d shared_lv1 -m /test -a \ size=32768 -a frag=512 -a nbpi=1024 This command creates the /test file system on the shared_lv1 logical volume on nodes alpha and beta with a fragment size of 512 bytes, a number of bytes per i-node (nbpi) ratio of 1024, and an initial size of 16MB (512 * 32768). Implementation Specifics This command is part of High Availability Cluster Multi-Processing for AIX (HACMP for AIX). You must be a root user to execute C-SPOC commands. Files /tmp/cspoc.log File contains a log of all distributed commands run, along with status, error messages, and timestamps. /etc/filesystems Lists the known file systems and defines their characteristics. Suggested Reading HACMP for AIX Administration Guide HACMP for AIX Troubleshooting Guide Related Information The crfs, chfs, clvaryonvg, cl_chfs, cl_chlv, chlv, and rsh commands. g k|[A$a0i7]7P`7!Da./usr/share/man/cat1/cl_mkvg.11$$cl_mkvg Command Purpose Creates a shared volume group. Syntax cl_mkvg [-cspoc "[-f] [-g ResourceGroup | -n NodeList]"] [ -d MaximumPhysicalVolumes ] [ -i ] [ -c ] [ -x ] [ -m MaxPvSize ] [ -n ] [ -s Size ] [ -V MajorNumber ] -f -y VolumeGroup PhysicalVolumes... Description The cl_mkvg command creates a new volume group, using the physical volumes represented by the PhysicalVolume parameter. The volume group is created on the first node in the specified nodelist. It is then imported on all the other nodes in the nodelist. This command can be used to create concurrent and non-concurrent capable volume groups. This command uses the AIX rsh facility to propagate commands to other nodes and requires the proper rsh access to all nodes. Thus each node must have a /.rhosts file which includes references to all interfaces for each cluster node. The /.rhosts file must reside in the root directory, and its mode must be 0600. Notes : 1.Before you attempt to add a new volume group, check the root file system (with the df command) to ensure that 1 to 2MB of free space exists. If you run the cl_mkvg command on a full rootvg file system, the underlying mkvg command fails if it tries to vary on the newly created volume group. If this occurs, create or free 2MB of space in the /etc directory. 2.To use this command, you must either have root user authority or be a member of the system group. 3.For disks greater that 4GB, make sure that the Physical Partion Size (-s) is set to a large enough value to utilize the entire disk. The default value, 4MB, along with the maximum number of physical partions (1016), will only utilize 4GB. 4.After AIX Version 4.1, whenever you create a volume group, the operating system automatically does a varyon. However if you create a volume group with the -c flag, the system will not autovaryon the volume group at the end of the Concurrent Capable volume group creation. Instead, the mkvg command notifies you to manually varyonvg the volume group in either non-concurrent or concurrent mode. You could also use the System Management Interface Tool (SMIT) to create a shared volume group. Use smit cl_admin and then "Logical Volume Manager" or 'Concurrent Logical Volume Manager", then "Shared Volume Groups" and "Create a Shared Volume Group". Flags -cspoc Argument used to specify the use of one of the following C-SPOC options: -f The cl_mkvg command will not fail if at least one node which has access to the underlying volume group is accessible. A warning is issued for nodes that cannot be reached. -g ResourceGroup Generates a list of nodes participating in the resource group on which the cl_mkvg command will be executed. -n NodeList Specifies the node(s) on which the C-SPOC command will be executed. You can specify more than one node by separating each node in the list with a comma. -c Creates a Concurrent Capable volume group. Only use the -c flag with the HACMP. It has no effect on volume groups and systems not using the HACMP product. This flag only applies to AIX Version 4.2 or later. -d MaximumPhysicalVolumes Estimates the maximum number of physical volumes contained in the volume group. The default is 32; a smaller number reduces physical volume space overhead. -f Forces the volume group to be created on the specified physical volume unless the physical volume is part of another volume group in the Device Configuration Database or a volume group that is active. -i Reads the PhysicalVolume parameter from standard input. -m MaxPvSize Specifies the maximum size of the physical volume. When this flag is used, the number of physical partitions is calculated based on the size of the physical volume. If this flag is not specified, then 1016 physical partitions are assumed. -n Specifies that the volume group is not automatically available during a system restart. The default value activates the volume group automatically. -s Size Sets the number of megabytes in each physical partition, where the Size variable is expressed in units of megabytes from 1 through 256. The Size variable must be equal to a power of 2 (example 1, 2, 4, 8). The default value is 4 megabytes. -V MajorNumber Specifies the major number of the volume group that is created. -x Specifies to varyon automatically in Concurrent mode a Concurrent Capable volume group set to varyon automatically during a system restart. This flag has no meaning on systems which do not have the HACMP product installed. This flag only applies to AIX Version 4.2 or later. In order for this auto-varyon into concurrency of the volume group to take effect, you must enter the following line into the /etc/inittab file: rc_clvmv:2:wait:/usr/sbin/clvm_cfg 2>&1 Attention: This entry must be added after the entry used to initiate srcmstr. -y VolumeGroup Specifies the volume group name rather than having the name generated automatically. Volume group names must be unique clusterwide and can range from 1 to 15 characters. The name cannot begin with a prefix already defined in the PdDv class in the Device Configuration database for other devices. The volume group name created is sent to standard output. The volume group name can only contain the following characters: "A" through "Z," "a" through "z," "0" through "9," or "_" (the underscore), "-" (the minus sign), or "." (the period). All other characters are considered invalid. Examples To create a volume group with name test_vg that contains two physical volumes with partition size set to 1 megabyte on nodes alpha, beta and gamma, enter: cl_mkvg -cspoc "-n alpha,beta,gamma" -f -y test_vg -s 1 000033674acf1ed2 00003275d91789e8 Implementation Specifics This command is part of High Availability Cluster Multi-Processing for AIX (HACMP for AIX). You must be a root user to execute C-SPOC commands. Files /tmp Directory where the temporary files are stored while the command is running. /dev Directory where the character device entry for the volume group is created. /tmp/cspoc.log File contains a log of all distributed commands run, along with status, error messages, and timestamps. Suggested Reading HACMP for AIX Administration Guide HACMP for AIX Troubleshooting Guide Related Information The mkvg command, lsvg command, varyonvg command, clvaryonvg command and rsh command. kUA$0i7r[7P`7!D./usr/share/man/cat1/cl_mkdisk.111s.1$$cl_mkdisk Command Purpose Adds a disk to a given set of cluster nodes. This command uses the AIX rsh facility to propagate commands to other nodes and requires the proper rsh access to all nodes. Thus each node must have a /.rhosts file which includes references to all interfaces for each cluster node. The /.rhosts file must reside in the root directory, and its mode must be 0600. You could also use the System Management Interface Tool (SMIT) to add a disk to the system. Use smit cl_admin and then "Physical Volume Manager", then "Add a Disk". Syntax The syntax is different for SCSI disks and SSA disks. For SCSI, the syntax is cl_mkdisk -cspoc "[-f] [-n nodelist]" -c disk -t DiskType -s Subclass -p -w [-aAttribute=Value] For SSA, the syntax is cl_mkdisk -cspoc "[-f] [-n nodelist]" -c disk -t DiskType -s Subclass -p -w [-aAttribute=Value] Description The cl_mkdisk command defines and makes available a disk with the given device class (-c Class flag), type (-tType flag), subclass (-s Subclass flag), connection location (-w ConnectionLocation flag), and the device logical name of the parent (-p ParentName flag) on the nodes specified. ( the -n nodelist flag ). Flags -cspoc Argument used to specify the use of one of the following C-SPOC options: -f The cl_mkdisk command will not fail if a cluster node is not reachable. A warning is issued for nodes that cannot be reached. -n NodeList Specifies the node(s) on which the C-SPOC command will be executed. You can specify more than one node by separating each node in the list with a comma. -a Attribute=Value Specifies the device attribute value pairsto be used instead of the defaults. The Attribute=Value variable can be used to specify one attribute value pair or multiple attribute value pairs for one -a flag. If you use an -a flag with multiple attribute value pairs, the list of pairs must be enclosed in quotation marks with a blank space between the pairs. For example, entering -a Attribute=Value lists one attribute value pair per flag, while entering -a 'Attribute1=Value1 Attribute2=Value2' lists more than one attribute value pair. -c Class Specifies the device class. -p ParentName Specifies the device name, indicated by the ParentName variable, that you want assigned to the device when used with the -c, -s, and -t flags. This flag is used for SSA devices. For SCSI disks, the -p flag is used. This is because the parent device names can be different for each node in the cluster. -s Subclass Specifies the subclass, indicated by the Subclass variable, of the device. -t Type Specifies the device type from the Predefined Devices object class. -w ConnectionLocation Specifies the connection location, indicated by the ConnectionLocation variable, on the parent. Examples To add a 1000mb SCSI disk on nodes alpha and beta with connection address 5,0 and with parent adapter on alpha being vscsi0, parent adapter on beta being scsi0, use cl_mkdisk -cspoc "-n alpha,beta" -c disk -t 1000mb -s scsi -p alpha,vscsi0 beta,scsi0 -w 5,0 To add a SSA disk on nodes alpha and beta with connection address 5,0 enter cl_mkdisk -cspoc "-n alpha,beta" -c disk -t hdisk -s ssar -p ssar -w 5,0 Implementation Specifics This command is part of High Availability Cluster Multi-Processing for AIX (HACMP for AIX). You must be a root user to execute C-SPOC commands. Files /tmp Directory where the temporary files are stored while the command is running. /tmp/cspoc.log File contains a log of all distributed commands run, along with status, error messages, and timestamps. Suggested Reading HACMP for AIX Administration Guide HACMP for AIX Troubleshooting Guide Related Information The chdev command, lsattr command, lsconn command, lsdev command, lsparent command, rmdev command, cl_rsh command. @kjFwhibutes of groups. /etc/security/group Contains the extended attributes of groups. Suggested Reading HACMP for AIX Administration Guide HACMP for AIX Troubleshooting Guide Related Information The rmuser and rsh commands. Synt kTnA$ 0i7=]7P`7!D ./usr/share/man/cat1/clm_stats.1.1s.1$$ clm_stats Command ***************** Purpose Queries the HACMP Cluster Lock Manager (cllockd) for current information about the numbers of locks, resources, and memory usage. Syntax clm_stats [-t Seconds] Description The clm_stats utility queries the HACMP cluster lock manager for up-to-date status information concerning the numbers of locks, resources, and memory usage on the cluster node where the command is executed. The utility then displays this information. Note: The HACMP cluster lock manager must be active for clm_stats to report accurate information. The clm_stat only functions with the current level of HACMP. The utility queries the lock manager kernel extension and reports the following status information: * the number of locks in use * the number of locks allocated * the number of requests refused * the number of resources in use * the number of resources allocated * the available lock manager memory * the lock manager memory used * the percentage of lock manager memory used * the percent at which requests will be denied. The clm_stats utility should be run on each node in the cluster as soon as cllockd starts. Executing the command at this point lets you view the lock manager allocation as the associated database initializes. The utility, however, will not run until the kernel extension is loaded. If the clm_stats command is executed with no arguments, it returns a snapshot of current lock manager information. The -t flag can be used with the clm_stats command to specify that the utility run continuously, displaying information every specified number of seconds. Flags -t Seconds Specifies the interval in seconds between each line of output. Example: To specify that the clm_stats utility runs continuously, producing output every five seconds, enter: clm_stats -t 5 The following is output you may see: locks locks locks W res res W mem mem % % in use alloc refused in use alloc maxMB usedMB used limit 23209 32767 0 23209 24576 255 15 5 50 24263 32767 0 24263 24576 255 15 5 50 25297 32767 0 25297 32768 255 17 6 50 26350 32767 0 26350 32768 255 17 6 50 27403 32767 0 27403 32768 255 17 6 50 28457 32767 0 28457 32768 255 17 6 50 29506 32767 0 29506 32768 255 17 6 50 30554 32767 0 30554 32768 255 17 6 50 CTRL-C causes the utility to exit. Note: An asterisk appears in the W (Warning) columns if the cluster lock manager has denied locks (CLM_DENIED_NOLOCKS return code) to a client application because of memory contraints. Implementation Specifics This command is part of High Availability Cluster Multi-Processing for AIX (HACMP for AIX). Suggested Reading HACMP for AIX Troubleshooting Guide HACMP for AIX Programming Locking Applications Related Information None ot use k'xA$ 0i7+]7P`7!D ./usr/share/man/cat1/cl_updatevg.11s.1$$ cl_updatevg *********** Purpose Forces the update of each node's view of a volume group's contents. Syntax cl_updatevg -cspoc "[-f] -g ResourceGroup" VolumeGroup Description Note: The volume group must be varied off on all nodes for the cl_updatevg command to execute; otherwise, it fails. The cl_updatevg command forces each node participating in the given resource group to export and then import the volume group. The command preempts the HACMP "lazy update" feature implemented by forcing each node to update its view of the volume group at a pre-planned time, minimizing the duration of HACMP's fallover time. This command uses the AIX rsh facility to propagate commands to other nodes and requires the proper rsh access to all nodes. Thus each node must have a /.rhosts file which includes references to all interfaces for each cluster node. The /.rhosts file must reside in the root directory, and its mode must be 0600. Flags -cspoc Argument used to specify the use of one of the following C-SPOC options: -f The command will procede with only a warning if nodes that access the volume group are inaccessible. The update occurs on all nodes that are accessible. -g ResourceGroup Generates a list of nodes participating in the resource group on which the cl_updatevg command will be executed. -n NodeList Specifies the node(s) on which the C-SPOC command will be executed. You can specify more than one node by separating each node in the list with a comma. Note: If you do not specify either the -g or -n options, the default action occurs on all cluster nodes. VolumeGroup Name of the shared volume group. Example 1. To update all nodes' view of volume group vg03, enter: cl_updatevg -cspoc "-g res_grp3" vg03 2. To update all nodes' view of volume group vg03, even though one or more nodes participating in "res_grp3" are not accessible, enter: cl_updatevg -cspoc "-f -g res_grp3" vg03 Note that any nodes not currently accessible will need to be updated at some future time. Implementation Specifics This command is part of High Availability Cluster Multi-Processing for AIX (HACMP for AIX). You must be a root user to execute C-SPOC commands. Files /tmp/cspoc.log File contains a log of all distributed commands run, along with status, error messages, and timestamps. Suggested Reading HACMP for AIX Administration Guide HACMP for AIX Troubleshooting Guide Related Information The clvaryonvg, varyonvg, importvg, exportvg, and rsh commands. kK]A$ 0i7]7P`7!D ./usr/share/man/cat1/cl_rmdisk.111s.1$$ cl_rmdisk Command *************** Purpose Removes a disk definition from the selected nodes. Syntax cl_rmdisk [-cspoc "[-f] [-g ResourceGroup | -n NodeList]"] -l PVID [-d] Description The cl_rmdisk command unconfigures or both unconfigures and undefines a disk on the selected nodes. This disk is specifed as a PVID by the -l paramter. The cl_rmdisk command takes the PVID and converts it to a disk device on each of the selected nodes. Then it runs the rmdev command on each node to do the actual unconfiguration. If you specify the -d flag, the rmdev command deletes the device definition from the Customized Devices object class (undefines). If you do not specify the -d flag, the rmdev command sets the device to the Defined state (unconfigures). This command uses the AIX rsh facility to propagate commands to other nodes and requires the proper rsh access to all nodes. Thus each node must have a /.rhosts file which includes references to all interfaces for each cluster node. The /.rhosts file must reside in the root directory, and its mode must be 0600. Flags -cspoc Argument used to specify the use of one of the following C-SPOC options: -f This command will not fail if at least one node which has access to the underlying volume group is accessible. A warning is issued for nodes that can't be reached. -g ResourceGroup Generates a list of nodes participating in the resource group on which the cl_lslv command will be executed. -n NodeList Specifies the node(s) on which the C-SPOC command will be executed. You can specify more than one node by separating each node in the list with a comma. -l PVID This is a mandatory parameter. The PVID is the pysical volume identifier for the disk definition you want to remove. -d Removes the device definition from the Customized Devices object class. This flag cannot be used with the -S flag. Examples 1. To make the disk with PVID 00003367ccd3fcd9 unavailable (but defined) to all nodes in resource_grp1: cl_rmdisk -cspoc "-g resource_grp1" -l 00003367ccd3fcd9 This will make the disk unavailable on any node in resource_grp1 that has a disk device with PVID 00003367ccd3fcd9. 2. To remove the disk definition with PVID 00003367ccd3fcd9 on node1, node2 and node3: cl_rmdisk -cspoc "-n node1,node2,node3" -l 00003367ccd3fcd9 -d This will remove the disk definition on node1, node2 and node3 if the node has a disk device with PVID 00003367ccd3fcd9. Implementation Specifics This command is part of High Availability Cluster Multi-Processing for AIX (HACMP for AIX). You must be a root user to execute C-SPOC commands. Files /tmp/cspoc.log File contains a log of all distributed commands run, along with status, error messages, and timestamps. Suggested Reading HACMP for AIX Administration Guide HACMP for AIX Troubleshooting Guide Related Information The lspv, rmdev and rsh commands. ing Lo koZA$7$0i7]7P`7!E7$./usr/share/man/cat1/cl_crfs.11$$cl_crfs Command Purpose Adds a shared file system on specified nodes in the cluster. Syntax cl_crfs [-cspoc "[-f] [ -n NodeList]"] -v VfsType { -d Device } [ -l LogPartitions ] -m MountPoint [ -n NodeName ] [ -u MountGroup ] [ -A { yes | no } ] [ -p {ro | rw } ] [ -a Attribute=Value ... ] [ -t { yes | no } ] Description The cl_crfs command creates a file system on a logical volume within a previously created volume group. The volume group is then updated on the specified nodes in the cluster. Note: When creating a shared file system on a shared logical volume, at least one node in the cluster must have the parent volume group varied on. This command uses the AIX rsh facility to propagate commands to other nodes and requires the proper rsh access to all nodes. Thus each node must have a /.rhosts file which includes references to all interfaces for each cluster node. The /.rhosts file must reside in the root directory, and its mode must be 0600. You can use the System Management Interface Tool (SMIT) to run this command. To use SMIT, enter: smit cl_admin Then, select "Cluster Logical Volume Manager" and then "Shared File Systems" and "Create a Shared File System". Flags -cspoc Argument used to specify the use of one of the following C-SPOC options: -f The cl_crfs command will not fail if at least one node which has access to the underlying volume group is accessible. A warning is issued for nodes that cannot be reached. -n NodeList Specifies the node(s) on which the C-SPOC command will be executed. You can specify more than one node by separating each node in the list with a comma. -a Attribute=Value Specifies a virtual file system-dependent attribute/value pair. To specify more than one attribute/value pair, provide multiple -a Attribute=Value parameters (see example). The following attribute/value pairs are specific to the Journaled File System (JFS): -a ag={ 8 | 16 | 32 | 64 } Specifies the allocation group size in megabytes. An allocation group is a grouping of inodes and disk blocks similar to BSD cylinder groups. The default ag value is 8. This attribute only applies to AIX Version 4.2 or later. -a bf={ true | false } Specifies a large file enabled file system. See "Understanding Large File Enabled File Systems" for more information. If you do not need a large file enabled file system, set this option to false; this is the default. Specifying bf=true requires a fragment size of 4096 and compress=no. This attribute only applies to AIX Version 4.2 or later. -a compress={ no | LZ } Specifies data compression. If you do not want data to be compressed, set this option to no. The default compress value is no. Selecting compression requires a fragment size of 2048 or less. -a frag={ 512 | 1024 | 2048 | 4096 } Specifies the JFS fragment size in bytes. A file system fragment is the smallest unit of disk storage that can be allocated to a file. The default fragment size is 4096 bytes. -a logname=LVName Specifies the log logical volume name. The specified logical volume will be the logging device for the new JFS. The LVName logical volume must already exist. The default action is to use an existing logging device in the target volume group. -a nbpi={ 512 | 1024 | 2048 | 4096 | 8192 | 16384 | 32768 | 65536 | 131072 } Specifies the number of bytes per i-node (nbpi). The nbpi affects the total number of i-nodes on the file system. The nbpi value is inversely proportional to the number of i-nodes on the file system. The default nbpi value is 4096 bytes. The values 32768, 65536, and 131072 only apply to AIX Version 4.2 or later. -a size=Value Specifies the size of the JFS in 512-byte blocks. If the specified size is not evenly divisible by the physical partition size, it is rounded up to the closest number that is evenly divisible. This attribute is required when creating a JFS file system. See "Understanding JFS Size Limitations" for more information. Notes: 1.Only JFS file systems created with the default ag, bf, compress, frag, and nbpi values and a size of less than 2 gigabytes are recognized on an AIX Version 3.2 system. Furthermore, file systems created with an ag value greater than 8 is not recognized on an AIX Version 4 system much less an AIX Version 3.2 system. 2.The ag, bf, compress, frag, and nbpi attributes are set at file system creation and cannot be changed after the file system is successfully created. The size attribute defines the minimum file system size, and you cannot decrease it once the file system is created. 3.The root filesystem ( / ) cannot be compressed. 4.Some nbpi values and allocation group sizes are mutually exclusive. See "Understanding JFS Size Limitations" for information. -A Specifies whether the file system is mounted at each system restart: yes File system is automatically mounted at system restart. no File system is not mounted at system restart. -d Device Specifies the device name of a device or logical volume on which to make the file system. This is used to create a file system on an already existing logical volume. -l LogPartitions Specifies the size of the log logical volume, expressed as a number of logical partitions. This flag applies only to JFS file systems that do not already have a log device. -m MountPoint Specifies the mount point, which is the directory where the file system will be made available. Note: If you specify a relative path name, it is converted to an absolute path name before being inserted into the /etc/filesystems file. -n NodeName Specifies the remote host name where the file system resides. This flag is only valid with remote virtual file systems such as the Network File System (NFS). -p Sets the permissions for the file system. ro Read-only permissions rw Read-write permissions -t Specifies whether the file system is to be processed by the accounting subsystem: yes Accounting is enabled on the file system. no Accounting is not enabled on the file system (default value). -u MountGroup Specifies the mount group. -v VfsType Specifies the virtual file system type. Examples To make a JFS on the rootvg volume group with nondefault fragment size and nondefault nbpi, enter: cl_crfs -cspoc "-n alpha,beta" -v jfs -d shared_lv1 -m /test -a \ size=32768 -a frag=512 -a nbpi=1024 This command creates the /test file system on the shared_lv1 logical volume on nodes alpha and beta with a fragment size of 512 bytes, a number of bytes per i-node (nbpi) ratio of 1024, and an initial size of 16MB (512 * 32768). Implementation Specifics This command is part of High Availability Cluster Multi-Processing for AIX (HACMP for AIX). You must be a root user to execute C-SPOC commands. Files /tmp/cspoc.log File contains a log of all distributed commands run, along with status, error messages, and timestamps. /etc/filesystems Lists the known file systems and defines their characteristics. Suggested Reading HACMP for AIX Administration Guide HACMP for AIX Troubleshooting Guide Related Information The crfs, chfs, clvaryonvg, cl_chfs, cl_chlv, chlv, and rsh commands. g k|[A$a0i7]7P`7!Da./usr/share/man/cat1/cl_mkvg.11$$cl_mkvg Command Purpose Creates a shared volume group. Syntax cl_mkvg [-cspoc "[-f] [-g ResourceGroup | -n NodeList]"] [ -d MaximumPhysicalVolumes ] [ -i ] [ -c ] [ -x ] [ -m MaxPvSize ] [ -n ] [ -s Size ] [ -V MajorNumber ] -f -y VolumeGroup PhysicalVolumes... Description The cl_mkvg command creates a new volume group, using the physical volumes represented by the PhysicalVolume parameter. The volume group is created on the first node in the