db2prereqcheck - Check installation prerequisites

Authorization

None

Command Syntax

>>-db2prereqcheck--+--------------------------+----------------->
                   +- -v--version-------------+   
                   '-+-----+--+-------------+-'   
                     '- -l-'  '-f--xml_file-'     

>--+--------------------------------+--+----------------+------->
   +-c------------------------------+  '-o--output-file-'   
   '- -p--| DB2-pureScale-options |-'                       

>--+---+--+---+--+---+-----------------------------------------><
   '-s-'  +-u-+  '-i-'   
          '-g-'          

DB2-pureScale-options

|--t--+--------------------------+------------------------------>
      +-SINGLE_IB_PORT_CLUSTER---+   
      +-MULT_IB_PORT_CLUSTER-----+   
      +-SINGLE_ROCE_PORT_CLUSTER-+   
      '-MULTI_ROCE_PORT_CLUSTER--'   

>--+-------------------------------------------------------------------------------------------------------+-->
   |     .-,---------.                                                                                     |   
   |     V           |                                                                                     |   
   '-hl----host-name-+--+----------------+--+-------------------+--+----------------+--+-----------------+-'   
                        |     .-,------. |  '-iu--instance_user-'  '-tb_dev--device-'  |     .-,-------. |     
                        |     V        | |                                             |     V         | |     
                        '-dl----device-+-'                                             '-nl----netname-+-'     

>--+---------------------------------------+--------------------|
   '- -adapter_list--adapter_list_filename-'   

Command Parameters

-v version

Checks the prerequisites for a specific DB2 version. The -i and -v parameters are mutually exclusive.

-l

Checks the prerequisites related to DB2 pureScale and unrelated to DB2 pureScale environments for the latest DB2 version that is defined in the XML resource file. The -l and -v parameters are mutually exclusive. The -l parameter will not output any screen output if all prerequisites are met.

-f xml-file

Specifies the name of the XML resource file. If you do not specify the -f parameter, the DB2 installation/cfg/DB2prereqs.xml file is used.

-c

Checks the prerequisites for thin client.

The -c, -u, -g, and -p parameters are mutually exclusive.

-p

Checks the prerequisites for the DB2 pureScale environment (Linux and AIX® operating systems only). This is the default option.

The -c, -u, -g, and -p parameters are mutually exclusive.

Important: To validate prerequisites requirement for a specific network configuration of a DB2 pureScale installation, the -t network configuration type option must be specified along with this option.

-o output-file

Specifies a name for the output file such as db2prereqcheck.rpt. If you do not specify a filename the output is displayed on the screen.

-s

Prints prerequisite validation summary on screen.

-u

Checks the uDAPL requirement for the DB2 pureScale environment (Linux and AIX operating systems only).

The -c, -u, -g, and -p parameters are mutually exclusive.

On RoCE networks, you must manually ensure that the AIX and uDAPL software prerequisites are satisfied. The db2prereqcheck command does not validate the levels of the AIX and uDAPL software.

-g

Checks the GPL compilation requirement (Linux operating systems only)

The -c, -u, -g, and -p parameters are mutually exclusive

-i

Checks the prerequisites that are unrelated to DB2 pureScale environments for the latest DB2 version that you defined in the XML resource file. The -i and -v parameters are mutually exclusive.

-t

Validates the prerequisites for a specific type of network configuration (Linux operating systems only)

The network configuration type must be a single InfiniBand port cluster, multiple InfiniBand port cluster, single RoCE port cluster, or multiple RoCE port cluster (SINGLE_IB_PORT_CLUSTER, MULTI_IB_PORT_CLUSTER, SINGLE_ROCE_PORT_CLUSTER or MULTI_ROCE_PORT_CLUSTER)

-hl host-name

Specifies a list of hosts that are checked for passwordless root SSH access between all hosts.

-dl device

Specifies one or more device paths of the shared disks that are verified in order to make sure that they are accessible by all hosts. If you specify this parameter, you must also specify the -hl parameter.

For example: /dev/hdisk2; /dev/dm-0

ex: /dev/hdisk2; /dev/dm-0

-adapter_list adapter_list_filename

Specifies the file name that contains the list of hostname(s), netname(s), adapter name(s), and mac address(es) for each of the host to verify the network connectivity between all the hosts are pingable using RDMA.

The input file must have the following format:

#Hostname    Netname         Interface-Adapter    Mac-Address
hostname1    netname1-ib0    deviceName-1         macAddress-1
hostname2    netname2-ib1    deviceName-2         macAddress-2
hostname3    netname3-ib2    deviceName-3         macAddress-3

For example, the input file format:

#Hostname      Netname            Interface-Adapter    
coralpib110    coralpib110-ib0    hca1         
coralpib111    coralpib111-ib0    hca1         
coralpib112    coralpib112-ib0    hca1         

Refer to /etc/dat.conf to find the Interface-Adapter name. For example:

from /etc/dat.conf: 
hca0 u1.2 nonthreadsafe default /usr/lib/libdapl/libdapl.a(shr_64.o) IBM.1.1 "/dev/iba0 1 ib0"

where hca1 is the device name of your adapter.

Note: In the input file, any line that is preceded by # is considered as comment and skipped.

-iu instance_user

Specifies the instance user name. The UID and GID of the instance user name are verified to make sure they are the same across all hosts. If you specify this parameter, you must also specify the -hl parameter.

-tb_dev device

Specifies the device name of the shared disk that is verified to make sure that it can be used as the "quorum tie-breaker" device for the pureScale cluster. If you specify this parameter, you must also specify the -hl parameter.

-nl netname

Specifies the list of netnames. These netnames are used to ping the RocE & IB networks to verify that they are pingable between all hosts.