FUJITSU P3AM-4042-23ENZ0 Eternus Af

Product Information

The Fujitsu Storage ETERNUS AF and ETERNUS DX Configuration Guide provides detailed instructions for setting up server connections using iSCSI for Oracle Solaris. The manual covers various chapters including workflow, checking server environment, setting up the storage system, installing iSCSI software initiator, checking connections, setting multipath, and setting up a file system.

Specifications

• Product: Fujitsu Storage ETERNUS AF, ETERNUS DX
• Model: P3AM-4042-23ENZ0
• Edition: 23rd Edition July 2024

Product Usage Instructions

Workflow
The Workflow section guides users through the configuration settings required to connect the ETERNUS AF/DX storage system.

Checking the Server Environment
Before proceeding with the setup, ensure the following server environment conditions are met:

• Hardware compatibility as per Server Support Matrix
• Operating System compatibility as per Server Support Matrix
• Network Interface Card compatibility as per Server Support Matrix
• Multipath configuration as per Server Support Matrix

Installing the iSCSI Software Initiator and Setting Up the Server
Follow these steps to install the iSCSI software initiator and set up the server:

1. Install the iSCSI Software Initiator as detailed in the manual.
2. Proceed with setting up the server as described in the manual.

Checking Connections
To ensure proper connectivity, follow these steps:

1. Turn on the devices as instructed.
2. Configure the server to recognize the logical units following the steps.

Setting the Multipaths
For setting multi-paths, follow these guidelines:

1. Enable MPxIO according.
2. Edit /kernel/drv/scsi_vhci.conf as specified.
3. Reconfigure and restart the server following the steps.

Chapter 9: Setting a File System
To set up a file system, refer to Chapter 9 of the manual for detailed instructions.

FAQ (Frequently Asked Questions)

• Q: What should I do if my server environment does not meet the requirements specified in the manual?
  A: If your server environment does not meet the specified requirements, it is recommended to consult with your IT department or Fujitsu support for further assistance.

• Q: Can I use this configuration guide for systems other than Oracle Solaris?
  A: This configuration guide is specifically tailored for Oracle Solaris systems. For other operating systems, please refer to the respective configuration guides provided by Fujitsu.

This manual briefly explains the operations that need to be performed by the user to connect an ETERNUS AF/DX to a server running Solaris OS via an iSCSI interface. This manual should be used in conjunction with any other applicable user manuals, such as those for the ETERNUS AF/DX, server, OS, LAN cards, and drivers. Refer to “Configuration Guide -Server Connection- Notations” for the notations used in this manual such as product trademarks and product names. For storage systems that are supported by the OS, refer to the Server Support Matrix of the ETERNUS AF/DX.

Workflow

Exactly which documents are required depends on the connection environment, see the “Work-flow” section that follows for details. IPv4 is used for IP address examples in this manual.

Required Documents

• “Server Support Matrix”
• “Configuration Guide -Server Connection- Storage System Settings” that corresponds to the ETERNUS AF/DX to be connected
• “ETERNUS Web GUI User’s Guide”

1. Setting Up the ETERNUS AF/DX
   Set the various parameters required to operate the ETERNUS AF/DX.

   • “Chapter 4 Checking the Server Information” (page 13)
   • “Chapter 5 Setting Up the ETERNUS AF/DX” (page 14)
   • Checking the setup and maintenance operations
   • “ETERNUS Web GUI User’s Guide”
   • Setting up the ETERNUS AF/DX
   • “Configuration Guide -Server Connection- Storage System Settings” that corresponds to the ETERNUS AF/DX to be connected

2. Installing the iSCSI Software Initiator and Setting Up the Server
   Set up the OS to connect to the ETERNUS AF/DX.

   • “Chapter 6 Installing the iSCSI Software Initiator and Setting Up the Server” (page 15)

3. Setting Up the Server to Recognize the Logical Units
   Set up the server so that it can recognize the LUNs (logical unit numbers) of the ETERNUS AF/DX.

4. “7.2 Setting Up the Server to Recognize the Logical Units” (page 22)

5. Configuring the System
   Set up the server as required by the system configuration.

   • Setting the multipath
   • “8.1 Enabling MPxIO” (page 23)
   • Setting a file system
   • “Chapter 9 Setting a File System” (page 26)

Checking the Server Environment

Connection to servers is possible in the following environments. Check the “Server Support Matrix” for server environment conditions.

1. Hardware
   Refer to the “Server Support Matrix”.

2. Operating System (OS)
   Refer to the “Server Support Matrix”.

3. Network Interface Card
   Refer to the “Server Support Matrix”.

4. Multipath Configuration
   Refer to the “Server Support Matrix”.

Notes

Note the following issues when connecting the ETERNUS AF/DX to a server.

LAN Environment Notes

• For the iSCSI LAN (used to transfer data), do not set multipath configuration with IP Network Multipathing (IPMP).

• Configure the iSCSI LAN as a dedicated LAN that is separate from the business LAN or the management LAN by segmenting the IP address.
  Example:

  • IP address of the LAN for iSCSI: 192.168.10.x/24

  • IP address of the business/management LAN: 192.168.70.y/24
    The iSCSI LAN and the business/management LAN must be configured with different network addresses (up to the value “192.168.10.”) as shown in the above example.

  • If it is not a dedicated LAN, the following may occur.

  • Processes may be delayed in the LANs due to traffic conflicts.

  • In terms of security, SAN data may leak or the iSCSI port may hang due to DoS attacks.

• iSCSI LAN redundancy is achieved by the use of multipaths. The LAN must be configured as a dedicated LAN for each path from a server to the ETERNUS AF/DX.

Example of a LAN switch connection configuration

1. In this system configuration, multipaths provide redundant connections between the servers and the storage system. LAN switches #1 and #2 provide physical separation of the network paths.
2. A separate LAN segment is provided in the LAN switch (using the switch VLAN function) for each grouping of business servers and storage systems (equivalent to the FC zones).

Example of a network address configuration
The following example shows a configuration in which multiple servers are connected to multiple CAs.

The following example shows a configuration in which a single server is connected to multiple CAs.

Server Startup and Power Supply Control Notes

• Before turning the server on, check that the ETERNUS AF/DX storage systems and LAN switches are all “Ready”. If the server is turned on and they are not “Ready”, the server will not be able to recognize the ETERNUS AF/DX storage systems.
• Also, when the ETERNUS AF/DX power supply is being controlled by a connected server, make sure that the ETERNUS AF/DX does not shut down before the connected servers. Similarly, the LAN switches must also be turned off after the connected servers have been shut down.
• If turned off, data writes from the running server cannot be saved to the ETERNUS AF/DX storage systems, and already saved data may also be affected.

Jumbo Frame Setting Notes

• To enable Jumbo Frame, all the connected devices must support Jumbo Frame. Set the appro-priate values for various parameters (such as the MTU size) on each connected device.
• For details about how to set Jumbo Frame for a LAN card and LAN switch, refer to the OS and each device’s manuals. Rebooting the server may be required to apply the new settings.
• The MTU size that is supported by the ETERNUS AF/DX is 9,000 bytes.

Notes on Configuring an iSCSI Boot Environment

• When configuring an iSCSI Boot environment, use the path of the assigned CM (Primary) for the LUN where the OS is to be installed as the path for the configuration (or OS installation).
• During operation, use the path of the assigned CM (Primary) for the LUN where the OS is installed as the boot path.
• Use the path of the unassigned CM (Secondary) as the standby path that is only used for maintaining redundancy when a failure occurs.
• After the failure is recovered, perform a boot again using the path of the assigned CM (Primary).

Checking the Server Information

The server information registered in the ETERNUS AF/DX should be checked. A variety of commands are used to check the following server information.

• iSCSI Software Initiator
  Since iSCSI Software Initiator is provided with the OS, installation is not required. Check the SUNWiscsiu and SUNWiscsir packages using the “pkginfo” command.

• iSCSI Initiator name

  • The iSCSI Initiator name is required for the ETERNUS AF/DX settings.
  • Execute the following command to check the iSCSI Initiator name:
    The iSCSI Initiator name is displayed in the “Initiator node name” column.

• Server-side LAN card IP address for connecting to the ETERNUS AF/DX
  Execute the following command:

  • ifconfig -a

    Set the IP address if it is not already set.

• Initiator CHAP Name

  • The Initiator CHAP Name is the user name for unidirectional CHAP authentication. Execute the following command:

  • This is not required if CHAP authentication is not used.

    iscsiadm list initiator-node

  • The Initiator CHAP Name is displayed in the “CHAP Name” column of the applicable target information.

Setting Up the ETERNUS AF/DX

Set up the ETERNUS AF/DX storage systems using ETERNUS Web GUI.
ETERNUS AF/DX setup can be performed independently of server setup. For details on how to perform these settings, refer to the following manuals.

• “Configuration Guide -Server Connection- Storage System Settings” that corresponds to the ETERNUS AF/DX to be connected
• “ETERNUS Web GUI User’s Guide”

Installing the iSCSI Software Initiator and Setting Up the Server

Installing the iSCSI Software Initiator
Since iSCSI Software Initiator is provided with the OS, installation is not required.

Setting Up the Server
iSCSI connection settings depend on the CHAP authentication method. Perform the settings to match the CHAP authentication to be used.

Settings” (page 17)
Unidirectional CHAP authentication| “6.2.1 Setting Up the Command Queue Depth” (page 15) “6.2.2 iSCSI Basic Settings” (page 17)

“6.2.3 Server Settings when CHAP Authentication is Used” (page 18)

Bidirectional CHAP authentication| “6.2.1 Setting Up the Command Queue Depth” (page 15) “6.2.2 iSCSI Basic Settings” (page 17)

“6.2.3 Server Settings when CHAP Authentication is Used” (page 18)

“6.2.4 Server Settings when Bidirectional CHAP Authentication is Used” (page 20)

Setting Up the Command Queue Depth
Set the number of commands allowed to be queued (command queue depth) on each LUN in the ETERNUS AF/DX storage systems from the LAN card. This setting optimizes the connection between the ETERNUS AF/DX storage systems and the server.

Procedure

1. Edit the configuration file.
   Edit the configuration file (/etc/system) and specify the command queue depth.

Model

| Setting value
---|---
Command queue depth
ETERNUS AF/DX| Arbitrary (*1)

1. Recommended value = (maximum number of simultaneous command processes per CA port) ¸ (number of iSCSI ports connected to a single CA port) ¸ (number of LUNs)(Round the result down to the nearest whole number)

  * The maximum number of simultaneous command processes per CA port is as follows:  

The value is used by multiple servers that share the CA port. The commands are processed until the limit is reached. Model| Maximum number of simultaneous command processes
---|---
ETERNUS AF S3 series, ETERNUS DX S6 series, ETERNUS DX S5 series, ETERNUS DX8900 S4| 2048
Models other than the above| 1024

• Use the value of “8” if the actual result is lower.

• To achieve maximum system performance, this value can be changed according to the server load and the peak operating times.
  The parameter to be specified is determined by the disk driver currently operating in the server to be connected.

• For ssd drivers
  Specify the command queue depth for the “ssd_max_throttle” parameter. Add this parameter if it does not exist.
  Example:
  set ssd:ssd_max_throttle = 20

• For sd drivers
  Specify the command queue depth for the “sd_max_throttle” parameter. Add this parameter if it does not exist.
  Example:
  set sd:sd_max_throttle = 20

2. After editing the configuration file, save it.
3. After the setting is complete, check the configuration file for incorrect settings.
4. Reboot the server.

   /usr/sbin/shutdown -y -g0 -i6

iSCSI Basic Settings
The following items are required for the iSCSI connection and must be set:

• Checking the iSCSI Initiator
• Checking the iSCSI Initiator Node Name
• Setting the iSCSI Target IP addresses
• Enabling the iSCSI Target connection
• Creating an iSCSI device link
• Checking the ETERNUS AF/DX

Procedure

1. Check that the iSCSI Initiator service (iscsid) is enabled.
   If the iSCSI Initiator service is “disabled” (the default setting), use the “svcadm” command to change it to the “online” state.

2. Check the iSCSI Initiator Node Name.
   Refer to “iSCSI Initiator name” in “Chapter 4 Checking the Server Information” (page 13).

3. Set the iSCSI Target IP address(es).
   To connect the iSCSI Target, specify the IP address of each iSCSI CA port of the ETERNUS
   AF/DX is to be an iSCSI Target, as a “discovery address”.

   iscsiadm add discovery-address———–

   Enter the IP address for the underlined portion.
   Example: CM0Port0: 192.1.1.120, CM1Port0: 192.1.1.121

   iscsiadm add discovery-address 192.1.1.120

   iscsiadm add discovery-address 192.1.1.121

4. Enable the connection to the iSCSI Target.
   Enable the connection to the ETERNUS AF/DX that is to be the iSCSI Target.

   iscsiadm modify discovery -t enable

5. Create an iSCSI device link.

   devfsadm -i iscsi

6. Check the ETERNUS AF/DX.
   Check the state of the ETERNUS AF/DX disks using the “format” command.
   Example: ETERNUS DX200 S4

Server Settings when CHAP Authentication is Used
The following operations are required for CHAP authentication.

• Setting the Initiator secret (password setting to connect to the ETERNUS AF/DX)
• Setting the Initiator CHAP Name (CHAP name setting to connect to the ETERNUS AF/DX)
• Enabling CHAP

Procedure

1. Set the Initiator secret.
   This is a password that must be set so that the Initiator can connect to the target ETERNUS AF/DX. The CHAP secret set here must match that set in Target information.
   Example:
   To set the password “initiator000”

   iscsiadm modify initiator-node –CHAP-secret

   Enter secret:initiator000
   Re-enter secret:initiator000
   Caution
   Passwords are restricted to a maximum of 16 characters by the Solaris operating system. For 17 or more characters, the following message is output:

   • Iscsiadm: secret too long, maximum length is 16
   • Iscsiadm: Unable to complete operation

2. Set the Initiator CHAP Name.

   • The Initiator Node Name is the default Initiator CHAP Name. Use the “iscsiadm” command to set a new Initiator CHAP Name.
   • The Initiator CHAP Name set here must match that set in the Target information.
     iscsiadm modify initiator-node –CHAP-name———
     Enter the CHAP name for the underlined portion.
     Example:
     To set “initiator” as the CHAP Name

     iscsiadm modify initiator-node –CHAP-name initiator

3. Enable CHAP authentication.
   Enable CHAP authentication on the Initiator.

   iscsiadm modify initiator-node –authentication CHAP

4. Check that CHAP is enabled on the Initiator. Use the “initiator-node” option.

5. Check that CHAP is enabled on the Target. Use the “target-param” option.

If CHAP is disabled, use the “iscsiadm” command to enable it.

iscsiadm modify target-param -a———

Enter the CHAP target name for the underlined portion.

Example:
To set “iqn.2000-09.com.fujitsu:storage-system.dxl:00001001-cm0” and “iqn.2000- 09.com.fujitsu:storage-system.dxl:00001001-cm1” as the target names.

• iscsiadm modify target-param -a CHAP iqn.2000-09.com.fujitsu:storage-system.dxl:00001001-cm0

• iscsiadm modify target-param -a CHAP iqn.2000-09.com.fujitsu:storage-system.dxl:00001001-cm1

Server Settings when Bidirectional CHAP Authentication is Used
The following items are required for bidirectional CHAP authentication and must be set:

• Enabling the bidirectional authentication parameters

Procedure

1. Enable the bidirectional authentication parameters on the Target.

   iscsiadm modify target-param -B enable

   Enter the target name for the underlined portion.
   Example:
   To set “iqn.2000-09.com.fujitsu:storage-system.dxl:00001001-cm0” and “iqn.2000- 09.com.fujitsu:storage-system.dxl:00001001-cm1” as the target names.

   • iscsiadm modify target-param -B enable iqn.2000-09.com.fujitsu:storage-system.dxl:00001001-cm0

   • iscsiadm modify target-param -B enable iqn.2000-09.com.fujitsu:storage-system.dxl:00001001-cm1

2. Set the authentication method to CHAP on the Initiator.

   iscsiadm modify target-param –authentication

   Enter the CHAP target name for the underlined portion.
   Example:
   To set “iqn.2000-09.com.fujitsu:storage-system.dxl:00001001-cm0” and “iqn.2000- 09.com.fujitsu:storage-system.dxl:00001001-cm1” as the target names.

   • iscsiadm modify target-param –authentication CHAP iqn.2000-09.com.fujitsu:storage-system.dxl:00001001-cm0

   • iscsiadm modify target-param –authentication CHAP iqn.2000-09.com.fujitsu:storage-system.dxl:00001001-cm1

3. Set a password for the target device on the Initiator.

   iscsiadm modify target-param –CHAP-secret

   Enter the target name for the underlined portion.
   Example:
   To set “testtarget00” and “testtarget10” as the passwords

4. Set a CHAP name on the Initiator.

   iscsiadm modify target-param –CHAP-name (1) (2)

   Enter the CHAP name for the target in (1) and the target name in (2).
   Example:
   To set “iqn.1986-03.com.sun:01:00144f565a49.47677520” as the CHAP name, and “iqn. 2000-09.com.fujitsu:storage-system.dxl:00001001-cm0” and “iqn.2000-09.com.fujitsu:storage- system.dxl:00001001-cm1” as the target names

Checking Connections

Turning on the Devices

To turn on the connected devices, use the following procedure:

Procedure

1. Turn on any devices (such as LAN switches) on the LAN path between the ETERNUS AF/DX and server.
2. After checking that the Ready (or equivalent) LED of the LAN switch is lit, turn on the ETERNUS AF/DX storage systems.
3. After checking that the ETERNUS AF/DX’s Ready LED is lit, turn on the server.

Setting Up the Server to Recognize the Logical Units

Check the state of the ETERNUS AF/DX LUNs (logical units) using the “format” command.

Example: ETERNUS DX200 S4

Setting the Multipaths

CAUTION

• For the iSCSI LAN (used to transfer data), do not set multipath configuration with IP Network Multipathing (IPMP).
• When configuring the multipath, use MPxIO in the same way as FC-SAN is used for configuration.

Enabling MPxIO

• Enable MPxIO.
• Check the [mpxio-disable=”no”] line in the “/kernel/drv/iscsi.conf” file.
• Change the parameter to “no” when “yes” is set.
• Example for changing the “/kernel/drv/iscsi.conf” file:

Check whether “no” is set for the underlined portion.

Editing “/kernel/drv/scsi_vhci.conf”
Edit the “/kernel/drv/scsi_vhci.conf” file.

Procedure

1. Specify the multipath control method.
   • Check that a “load-balance=”round-robin”;” line exists.
   • Otherwise, add this line or change its value to “enable”.
2. Enable the auto-failback function.
   • Check that an “auto-failback=” enable”;” line exists.
   • Otherwise, add this line or change its value to “enable”.
   • Check that “round-robin” is set for (1).
   • Check that “enable” is set for (2).

Reconfiguring and Restarting the Server

Reconfigure and restart the server to effect the new settings.

• touch /reconfigure

• /usr/sbin/shutdown -y -g0 -i6

Use the “format” command to check the MPxIO multipath status after multipathing is set up.

Example: ETERNUS DX200 S4

Setting a File System

The file system is created using the same procedure as when creating a file system on a regular disk.

• For single-path connection
  Example command:

  newfs /dev/rdsk/c2t16d0s6

• For multipath connection
  Example command:

  newfs /dev/rdsk/c7t600E000000A800000067902400000000d0s6

Fujitsu Storage ETERNUS AF, ETERNUS DX Configuration Guide -Server Connection- (iSCSI) for Oracle Solaris

• P3AM-4042-23ENZ0
• Date of issuance: July 2024
• Issuance responsibility: Fujitsu Limited

1. The content of this manual is subject to change without notice.
2. This manual was prepared with the utmost attention to detail.
3. However, Fujitsu shall assume no responsibility for any operational problems as the result of errors, omissions, or the use of information in this manual.
4. Fujitsu assumes no liability for damages to third-party copyrights or other rights arising from the use of any information in this manual.
5. The content of this manual may not be reproduced or distributed in part or its entirety without prior permission from Fujitsu.

References

• 09.com

Read User Manual Online (PDF format)

Download This Manual (PDF format)

Download this manual  >>