Two methods are used for managing Solaris OS server nodes: one method installs Agent on the host, and the other does not.
When Agent is installed, the following functions are available: the configuration data is automatically loaded from the server node; the system fault and status is monitored for Fujitsu's multipath disk control mechanism, mirror disks, and file systems; the line drawing for FC connection is performed; the access path settings are configured including server node HBA binding (storage affinity). Without Agent installed, the host can still be registered manually but status reading/access path setting/fault monitoring is disabled.
See
For information about products that can be monitored by Agent, see "10.5 Server Node Middleware that can be Managed".
Note
The limitations when Solaris OS server nodes are managed using the Agent:
HBA WWNN (World Wide Node Name) and PID binding (storage affinity) settings are not supported.
The access path is managed automatically in this software using WWPN (World Wide Port Name). Accordingly, if WWNN, PID, or TID binding has already been set in the server node HBA (host bus adapter), the settings must be changed to WWPN binding before the device is registered in this software. Server nodes that are used to perform WWNN, PID, or TID binding cannot be registered in this software.
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. For details on the manual embedding function, refer to "5.2.6 Registering a Manually Embedded Device".)
The methods used to manage Solaris OS server nodes installed in SUN-made HBAs and Fujitsu-made HBAs using Agents are different. These differences are shown in the table below.
Function | Fujitsu-made HBAs | SUN-made HBAs |
|---|---|---|
Access path settings | Specify the target number and LUN when the access path is set. | Settings are not configured in the settings file, so enter the default values for the target number and LUN when the access path is set. The command for enabling recognition of the LUN must also be entered. The dialog for entering target number is not displayed. |
Access path color | If the LUN is recognized, the color changes from Blue to Green. | This is always blue in the normal status. |
Side view HBAs | This is displayed as the logic HBA number before recognition of the LUN, and in Cx format after recognition of the LUN. | The logical HBA number is always displayed. |
Beacon blinking | Possible. | Not possible (the menu cannot be selected). |
Server Node view server multipath display | This is displayed when there is a multipath environment. The path can also be displayed by selecting the multipath instance name. | Information on the multipath driver device is not displayed. Therefore, multipath driver's path information cannot be displayed. |
Resource view server property multipath information | This is displayed when there is a multipath environment. | This is not displayed (only the option name is displayed). |
Resource view HBA property connection admission WWPN, target number, and LUN information | This is displayed. | The connection admission WWPN and LUN information are displayed. The target number is not displayed. |
Resource view access path property connection admission WWPN, target number, and LUN information | The connection admission WWPN, target number, and LUN information are displayed. | The connection admission WWPN and LUN information are displayed. The target number is not displayed. |
Element display except for Relationship Management window HBA nodes and HBA ports | Raw devices, multipath devices, and file systems (ufs, zfs) are displayed. | A file system (ufs,zfs,QFS/SAM-QFS/SAM-FS) will be displayed. A multipath device (MPxIO) is displayed. The raw device is displayed. |
Relationship Management window HBA port property connection admission WWPN, target number, and LUN information | This is displayed. | The connection admission WWPN and LUN information are displayed. The target number is not displayed. |
Relationship Management window access path property connection admission WWPN, target number, and LUN information | The connection admission WWPN, target number, and LUN information are displayed. | The connection admission WWPN and LUN information are displayed. The target number is not displayed. |
Multipath path display | It is possible to show a light blue color on the information of the access path and the storage information area, by selecting and clicking a multipath device file name on the server icon in the resource control window. In the relationship management window, path and correlated device icon can be displayed in color by Route Search. | In the relationship management window, the path from a multipath device to the HBA port can be displayed. Additionally, in the relationship management window, correlated device icon can be displayed in color by Route Search. |
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.
Install the SNIA HBA API library by installing the driver (FUJITSU PCI Fibre Channel 2.2.1 or 3.0).
When FUJITSU PCI Fibre Channel 2.2.1 is installed, it must be patched (by 912069-17 or later).
Note that FUJITSU PCI Fibre Channel 2.2 cannot be used any more.
Install HBAnyware (SNIA HBA API) according to the instructions in the driver's handbook.
After installing the driver (FUJITSU PCI Fibre Channel 4.0 or higher), the SNIA HBA API library must be changed according to the following procedure.
Change the link from "/usr/lib/libfchba.so" to "/opt/FJSVpfca/sbin/libfchba.so" to "/opt/FJSVpfca/sbin/libfchba1.so".
# rm /usr/lib/libfchba.so # ln -s /opt/FJSVpfca/lib/libfchba1.so /usr/lib/libfchba.so
Reboot.
# /usr/sbin/shutdown -y -i6 -g0
The SNIA HBA API library is included in the driver that is handled in the OS, therefore it has no settings.
There is no need to set up SNIA HBA API library, as it is included in the driver which is bundled with the operating system.
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.
Describe the following port type in the /kernel/drv/fjpfca.conf file in each instance name of fjpfca(Adapter).
port= "fjpfca0:nport", "fjpfca1:nport";
The topology parameter of /kernel/drv/lpfc.conf or lpfs.conf file is set to 2 as follows:
# 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. topology=2;
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;
N port settings are not required.
Note that database monitoring requires the following actions to be taken in advance:
Execute the defusr command, and register the user information necessary for database monitoring. For information about the defusr command, see "12.5.1.1 User information setting command (defusr)".
For information about particulars specified in the defusr command, see descriptions of monitoring each database.
Define the environment variables necessary for database access (e.g., LD_LIBRARY_PATH) in the sstorageagt.conf file. For information about the sstorageagt.conf file, see "C.8 sstorageagt.conf Parameter". For information about the necessary environment variables, refer to the appropriate Symfoware manual. In order to use multiple RDBs, a Symfoware statement must be defined in the Correlation.ini parameter. For information about the Correlation.ini parameter, see "C.7 Correlation.ini Parameter". The registration of the user information by the defusr command is unnecessary.
The JDBC driver is used to access Oracle. In the sstorageagt.conf file, define an environment for using the JDBC driver; and, using an Oracle statement in the Correlation.ini parameter, specify the number of the port used for access. For information about the sstorageagt.conf file, see "C.8 sstorageagt.conf Parameter". For information about the Oracle statement in the Correlation.ini parameter, see "C.7 Correlation.ini Parameter". For information about definitions necessary for the JDBC driver environment, refer to the appropriate Oracle manual.
The key name of the defusr command must be assigned the instance name subject to configuration management.
