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.
There is a difference in functionality depending on whether the agent was installed or whether it was not installed (with registration performed by manual embedding).
To place a Storage Cluster Controller, agent must be installed.
See
Refer to "3.2 Server Node Middleware for Which Management Is Possible" for information about the products that can be observed by Agent.
Refer to "9.5 Storage Cluster Controller" for details about the Storage Cluster Controller and its operation method.
It is necessary to install the HBA API library that the HBA vender distributes to manage HBA installed in the Linux server node.
Refer to the SNIA HBA API Library Installation Guide at the following URL for details on how to install the HBA API library:
https://www.fujitsu.com/global/support/products/computing/storage/manuals-list.html
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 Storage Cruiser, 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
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.
For Red Hat Enterprise Linux 8, Red Hat Enterprise Linux 7, or Red Hat Enterprise Linux 6 environments
With a method to be managed by installing an agent, SNMP Traps from the server nodes are sent using SNMPv1 or SNMPv3. The default is SNMPv1. When using SNMPv3, perform an SNMPv3 configuration by using the setagtsnmp command on the server node.
For SUSE Linux Enterprise Server 15 or SUSE Linux Enterprise Server 12 environments
With a method to be managed by installing an agent, SNMP Traps from the server nodes are sent using only SNMPv1.
