The information in this document pertains to AIX 4. This function will also be available in the base of AIX 5. This capability is added through mainly a new flag, -e, although a -m flag was also added to allow for the gathering of information from only those nodes specified rather than from all nodes of the cluster. The snap -e command gathers all HACMP related data from all nodes in the cluster configuration unless the -m flag is included and specifies which nodes to collect data from. The -e flag may not be used with any other flags except -d data collection directory , and -m, because, unlike all other snap command flags, the -e flag gathers data from multiple nodes.

Author:Yozshuzahn Sarg
Language:English (Spanish)
Genre:Personal Growth
Published (Last):8 September 2019
PDF File Size:20.17 Mb
ePub File Size:20.26 Mb
Price:Free* [*Free Regsitration Required]

Gathers X. The ADD keyword allows external products to register their debug data collection script with the snap framework. When a class name is specified as parameter to the class attribute, registered debug command of all the products in that class are executed. To collect data for more than one class specify the required class names in the class attribute. When ALL is specified as parameter, registered debug data collection command of all the products in all classes is executed.

Parameters Arguments Names of third-party scripts to be executed are specified as parameters to snap. A parameter can be a single word or a list of words enclosed in quotes. When parameters are enclosed in quotes, the first parameter in the list represents the name of the script and the subsequent words represent the arguments to pass to the script.

When All is specified as a parameter, all the scripts in the script repository are executed. No script parameters may be passed in this case. If the file: keyword is used and is immediately followed by a path to a file, that file is read to get the scripts to execute. Each line in the file represents a script and optional parameters to the script. When called during pass 1, a script must return its size estimation to snap.

In pass 2, it collects the data and saves it as specified by snap. This variable has comma separated name of the products for which the snap command collects the data during execution. This is the directory where the script should be saving its output.

During the first pass, the script should calculate a size estimation for the data it will write during the second pass. The value saved to the file should be in decimal. The following example shows a snap script:! The script is registered with the snap framework before it can be used to collect user defined debug data. These scripts can be de-registered as per user discretion. Following is the ODM class defined in the system. The same name is used for deregistration of the product debug data collection script.

You can choose appropriate class based on the product or define your own class. Class helps in the classification of the products. Users can contact IBM service personnel to add any other class in the snap documentation. Registration of Third Party Debug Script with Snap framework Registration can be done in two ways: You can explicitly run odmadd command to add the entry.

You can continue running the snap command. So, the odmdelete command must be executed before the odmadd command is invoked. Use the ADD keyword with the —z flag. Note: 1. If the debug binary is changed or updated, the user must re-register the component to update the snap repository with the latest binary. Deregistration of Third party debug scripts from Snap framework Deregistration can be done in two ways: Use the odmdelete command to deregister the product. This command also writes the system information to a removable diskette.

To run the scripts foo1, foo2 and foo3. To specify the All parameter to run all the scripts, type: snap All Note: No parameters are passed in this case.


The PowerHA for AIX (formerly HACMP) cheat sheet

PowerHA manages disk, network, and application resources logically, passing control to individual machines based on availability and preference. From a systems administration point of view, the main concept behind PowerHA is to keep everything as redundant as possible to ensure that there is high availability at all levels. Figure 1 below illustrates a simple PowerHA configuration. Figure 1. Figure 2. Active and idle servers When a problem occurs with the availability of some of the physical resources, such as some wires being accidentally unplugged, PowerHA senses the errors and makes the other server take over.


Understanding the hacmp.out log file



IBM High Availability Cluster Multiprocessing


Related Articles