Top
ETERNUS SF Storage Cruiser 14.0 User's Guide

4.1.3 Linux server node (host)

This software provides Linux server nodes with two management methods. In one method Agent is installed and in the other method Agent is not installed.

When Agent is installed, automatic import of the server node configuration from Manager, FC connection plot, and fault and status monitoring of the Fujitsu's multipath disk control mechanism become available. Without Agent installed, the host can still be registered manually but status reading/access path setting/fault monitoring is disabled.

See

For information about the products that can be observed by Agent, see "10.5 Server Node Middleware that can be Managed".


4.1.3.1 SNIA HBA API library settings

It is necessary to install the HBA API library that the HBA vender distributes to manage HBA installed in the Linux server node.


PG-FC105, PG-FC106, PG-FC107, PG-FC201, PG-FC202, PG-FCD201

Execute the next item of "Checking whether the HBA API library has been installed".

Checking whether the HBA API library has been installed

Check whether the following two conditions are met to determine the installation status. If both the conditions are met, the HBA API library has been installed.

  1. All of the following files exist.
    - /usr/lib/libHBAAPI.so
    - /usr/lib/libemulexhbaapi.so
    - /etc/hba.conf

  2. Executing the following command results in an integer that is 1 or larger. (The command is one line.)

    egrep -c [^[:blank:]]+[[:blank:]]+/usr/lib/libemulexhbaapi.so /etc/hba.conf

PG-FCD101, PG-FCD102

Execute the next item of "Checking whether the HBA API library has been installed". Install SNIA HBA API common library which corresponds to this software (corresponding to Common HBA API Version 2.18) as follows.

  1. If /usr/lib/libHBAAPI.so file exists, save it.

  2. Copy /opt/FJSVssagt/lib/libHBAAPI.so in /usr/lib/ or create the symbolic link as follows:

    # ln -s /opt/FJSVssage/lib/libHBAAPI.so /usr/lib/libHBAAPI.so
  3. As for libqlsdm.so (SNIA HBA API vendor library), contact your Fujitsu systems engineer (SE).

Checking whether the HBA API library has been installed

Check whether the following two conditions are met to determine the installation status. If both the conditions are met, the HBA API library has been installed.

  1. All of the following files exist.
    - /usr/lib/libHBAAPI.so
    - /usr/lib/libqlsdm.so
    - /etc/hba.conf

  2. Executing the following command results in an integer that is 1 or larger. (The command is one line.)

    egrep -c [^[:blank:]]+[[:blank:]]+/usr/lib/libqlsdm.so /etc/hba.conf

MC-08FC11, MC-08FC31, MC-08FC41, MC-08FC51, MC-08FC61, MC-08FC71

Install HBAnyware (SNIA HBA API) by referring to the operation manual of the HBA card or the driver manual.


4.1.3.2 Using the udev device

Information

  • The udev device is a Linux function that always assigns a fixed device name, even if the hardware configuration is changed.

    It assigns a device name that starts with "/dev/disk", unlike for existing device names, such as "/dev/sda".
    "/dev/disk/by-path/xxxxxxxx" xxxxxxxx is information generated from the disk location information
    "/dev/disk/by-id/yyyyyyyy" yyyyyyyy is information generated from the disk ID information

    In the following explanations, device names that start with "/dev/disk/by-path" are shown as "by-path", and device names that start with "/dev/disk/by-id" are shown as "by-id". Existing device names, such as "/dev/sda", are shown as compatible device names.

If the Linux udev function is used for devices monitored using ESC, use "by-id".
"by-id" is a symbolic link to "/dev/sd?name", therefore the relationship for "by-id" and the compatible device name displayed in this software can be checked by using the "ls -l /dev/disk/by-id" command.

Example

The method shown below checks "by-id" for "/dev/sdb"

# ls -l /dev/disk/by-id/
Total 0
lrwxrwxrwx 1 root root  9  April  3 21:28 scsi-1FUJITSU_300000690000 -> ../../sdb
lrwxrwxrwx 1 root root 10  April  3 21:28 scsi-1FUJITSU_300000690000-part1 -> ../../sdb1
lrwxrwxrwx 1 root root 10  April  3 21:28 scsi-1FUJITSU_300000690000-part2 -> ../../sdb2
lrwxrwxrwx 1 root root 10  April  3 21:28 scsi-1FUJITSU_300000690000-part3 -> ../../sdb3
lrwxrwxrwx 1 root root 10  April  3 21:28 scsi-1FUJITSU_300000690000-part7 -> ../../sdb7
lrwxrwxrwx 1 root root  9  April  3 21:28 scsi-1FUJITSU_300000690001 -> ../../sdc
lrwxrwxrwx 1 root root 10  April  3 21:28 scsi-1FUJITSU_300000690001-part1 -> ../../sdc1
lrwxrwxrwx 1 root root 10  April  3 21:28 scsi-1FUJITSU_300000690001-part2 -> ../../sdc2
lrwxrwxrwx 1 root root 10  April  3 21:28 scsi-1FUJITSU_300000690001-part3 -> ../../sdc3
lrwxrwxrwx 1 root root 10  April  3 21:28 scsi-1FUJITSU_300000690001-part7 -> ../../sdc7
lrwxrwxrwx 1 root root  9  April  3 21:28 scsi-1FUJITSU_300000690002 -> ../../sdd
lrwxrwxrwx 1 root root 10  April  3 21:28 scsi-1FUJITSU_300000690002-part1 -> ../../sdd1
lrwxrwxrwx 1 root root 10  April  3 21:28 scsi-1FUJITSU_300000690002-part2 -> ../../sdd2
lrwxrwxrwx 1 root root 10  April  3 21:28 scsi-1FUJITSU_300000690002-part3 -> ../../sdd3
lrwxrwxrwx 1 root root 10  April  3 21:28 scsi-1FUJITSU_300000690002-part7 -> ../../sdd7

Accordingly, it is possible to determine that "by-id" of "/dev/sdb" is "/dev/disk/by-id/scsi-1FUJITSU_300000690000".

Point

  • "by-path" for the device that is connected to the Fibre Channel switch may change, therefore specify "by-id".

  • Linux device nodes are displayed as compatible device name "sd?" in this software. The "by-id" and "by-path" are not displayed. Check the relationship using the command as shown above.


4.1.3.3 Database monitoring settings

To monitor databases, the following must have been executed:

Registering user information

Use the defusr command to register the user information that is required to monitor databases. Refer to 12.7.1.1 User information setting command (defusr) for details of the defusr command. For the contents to be specified in the defusr command, refer to the explanation for monitoring each database.

Monitoring Symfoware

Define in the sstorageagt.conf file the environment variables (such as LD_LIBRARY_PATH) that are required to access databases. Refer to "C.8 sstorageagt.conf Parameter". For the required environment variables, refer to the Symfoware manuals. For multiple-RDB operation, the Symfoware statement for the Correlation.ini parameter must be specified. Refer to "C.7 Correlation.ini Parameter". Note that user information registration by the defusr command is not required.

Monitoring Oracle

The JDBC driver is used to access Oracle. Use the sstorageagt.conf file to define the environment for using the JDBC driver and define the port number for accessing Oracle in the Oracle statement for the correlation.ini parameter.
Refer to "C.8 sstorageagt.conf Parameter" and "C.7 Correlation.ini Parameter" for details of the Oracle statement for the correlation.ini parameter. For the required JDBC driver environment definitions, refer to the Oracle manuals. As the defusr command key name, specify an instance name subject to configuration management.