Top
ETERNUS SF Storage Cruiser V16.9 Operation Guide
FUJITSU Storage

4.1.1 Solaris OS Server Node

Two methods are used for managing Solaris OS server nodes: one method installs Agent on the host, and the other does not.

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 products that can be monitored by Agent.

Refer to "9.5 Storage Cluster Controller" for details about the Storage Cluster Controller and its operation method.

Note

Limitations When Solaris OS Server Nodes Are Managed Using Agent:

  • If device files of more than one controller number are generated

    If more than one device driver type is used to access storage of a different type from a single HBA, device files for at least 2 controller numbers may be generated for the single HBA. This software does not support this status.

    If there is a problem with information gathering or display, manage the server nodes using the manual embedding function. Refer to "5.2.7 Registering Manually Embedded Device" for details on the manual embedding function.

4.1.1.1 SNIA HBA API Library Settings

To manage the HBAs that are installed at Solaris OS server nodes, the SNIA HBA API library that an HBA vendor distributes must be installed.

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

4.1.1.2 N-port Settings

N port setting is needed on the side of HBA when connecting with the Fibre Channel switch. The method of setting the port of HBA as N port depends on the HBA type. Each method for setting is shown below.

For Solaris OS Default emlxs Driver (Target HBA: XSEFC401AF, XSEFC402AF, SG-XPCIE2FC-EM4, SG-XPCIE2FC-EM8, and so on.)

Specify "2" for the emlxsX-topology parameter in the /kernel/drv/emlxs.conf file.

#
# +++ Fibre Channel specific parameters +++
#
# topology: link topology for initializing the Fibre Channel connection.
#
#          0 = attempt loop mode, if it fails attempt point-to-point mode
#          2 = attempt point-to-point mode only
#          4 = attempt loop mode only
#          6 = attempt point-to-point mode, if it fails attempt loop mode
#
# Set point-to-point mode if you want to run as an N_Port.
# Set loop mode if you want to run as an NL_Port.
#
# Range: Min:0 Max:6 Default:0
#
emlxs0-topology=2;
emlxs1-topology=2;

For Solaris OS Default qlc Driver (Target HBA: SE0X7F21F, SE0X7F22F, SG-XPCI1FC-QF4, SG-XPCIE2FC-QF8, and so on.)

N port settings are not required.

4.1.1.3 SNMP Trap Transmission Settings

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.