Agent prerequisite checker
You can perform prerequisite checking before starting the agent installation process.
The prerequisite checker is located on the OMEGAMON® XE on z/VM® and Linux™ agent installation media. Platform-specific scripts are used by the prerequisite checker, so you must select the prerequisite checker that is appropriate for the platform where you are executing the prerequisite scan.
The prerequisite checker for Linux and UNIX platforms is
located in the following directory:
<installation_media>/unix/prereqcheckerThe prerequisite checker for Windows platforms is located
in the following directory:
<installation_media>/WINDOWS/prereqcheckerComplete
the following steps to run the stand-alone Prerequisite Checker:
- Open a command-line interface on the target computer:
- On Windows™ systems, open a Command Prompt.
- On Linux and UNIX™ systems, open a shell environment.
- Change the directory to the folder where you located the prerequisite
checker (on the installation media) and run the
following command:
- On Windows systems, run the prereq_checker.bat command.
- On Linux and UNIX systems, run the prereq_checker.sh command.
prereq_checker.bat "<Product code> [product version], <Product code> [product version]..." [PATH=<Agent install path>] [detail] [-p <Product Code>.SECTION.NAME=VALUE pairs]Windows example:prereq_checker.bat "KVL" detail PATH=d:\ibm\itm -p SERVER=IP.PIPE://mytems:1234Linux and UNIX example:./prereq_checker.sh "KVL" detail PATH=/opt/IBM/ITM -p SERVER=mytems:1918
The following paragraphs provide a detailed description
of the input parameters:
- Product code and version pairs
- At least one product code is required. For IBM® Tivoli® Monitoring, the code is the three-letter product code for the component or agent. Optionally, you can specify a version for the agent. If you do not specify a version, the prerequisite checker checks the latest version available.
- You must enter the product codes in capital letters. For the z/VM agent, for example, you must enter KVL. If you enter lowercase kvl, an error message is displayed.
- You can specify multiple product codes separated by commas.
- The product codes and versions must be enclosed in quotation marks, for example "KVL 04300000". In this example, the prerequisite check is made on the KVL agent version 04300000.
- Each component or agent has a config file with the naming convention *.cfg, for example, KVL_0430000.cfg. If you specify a product code that does not have a corresponding *.cfg file, that product code is ignored.
- [PATH=<product install path>]
- The PATH parameter is optional. An example PATH is
PATH=D:\IBM\ITM. If you do not specify a PATH parameter, the prerequisite checker checks the following default IBM Tivoli Monitoring installation paths:- On Windows systems, the default path is: C:\IBM\ITM
- On Linux and UNIX systems, the default path is: /opt/IBM/ITM
- The PATH parameter is optional. An example PATH is
- [detail]
- The detail parameter is optional. This flag indicates that you want to see detailed results on the screen when you run the prerequisite checker.
- Do not enclose the word detail in quotation marks.
- If you do not specify detail, then only PASS or FAIL is displayed on the screen. Omitting the parameter is a simple way to see if your system meets the prerequisites.
- See the following example output when the detail parameter
is specified:
OMEGAMON XE on z/VM and Linux Agent [version 04300000] : Evaluation PASS/FAIL Expected Result Result CPU Number PASS 1 1 Available Memory PASS 35MB 1.02GB Available Disk PASS 70MB 1.09GB ALL COMPONENTS : Evaluation PASS/FAIL Expected Result Result Available Memory PASS 35MB 1.02GB Available Disk PASS 70MB 1.09GB - The detailed output is written to a file called precheck.log, regardless of whether you specify detail or not. You can view this file to see the results of the prerequisite checker. In addition, you can view the result.txt file to see the detailed steps taken by the prerequisite checker.
- You can specify optional parameters by using a -p flag. The parameters
are formatted as follows:
See the following example to check the ports:[-p <Product Code>.<instance>.<parameter>=<value>, <Product Code>.<instance>.<parameter>=<value>,]-p SERVER=IP.PIPE://mymachine:1918
Note: This script accepts the -p connection
parameter in the same way as the tacmd createNode command,
you can specify SERVER, PROTOCOL, PORT, BACKUP, BSERVER,
and so on. All parameters are case sensitive, therefore you must use
capital letters.
For additional information on the prerequisite checker, see the IBM Tivoli Monitoring Installation and Setup Guide.