17.3. Advanced storage options

Procedure

1. From the Installation Summary window, click Installation Destination. The Installation Destination window opens, listing all available drives.
2. Under the Specialized & Network Disks section, click Add a disk. The storage devices selection window opens.

3. Click Add iSCSI target. The Add iSCSI Storage Target window opens.

   重要

   You cannot place the /boot partition on iSCSI targets that you have manually added by using this method. An iSCSI target containing a /boot partition must be configured for use with iBFT. However, in instances where the installed system is expected to boot from iSCSI with iBFT configuration provided by a method other than firmware iBFT. For example, by using iPXE, you can remove the /boot partition restriction by using the inst.nonibftiscsiboot installer boot option.

4. Enter the IP address of the iSCSI target in the Target IP Address field.

5. Type a name in the iSCSI Initiator Name field for the iSCSI initiator in iSCSI qualified name (IQN) format. A valid IQN entry contains the following information:

   • The string iqn. (note the period).
   • A date code that specifies the year and month in which your organization’s Internet domain or subdomain name was registered, represented as four digits for the year, a dash, and two digits for the month, followed by a period. For example, represent September 2010 as 2010-09.
   • Your organization’s Internet domain or subdomain name, presented in reverse order with the top-level domain first. For example, represent the subdomain storage.example.com as com.example.storage.

   • A colon followed by a string that uniquely identifies this particular iSCSI initiator within your domain or subdomain. For example :diskarrays-sn-a8675309.

     A complete IQN is as follows: iqn.2010-09.storage.example.com:diskarrays-sn-a8675309. The installation program pre-populates the iSCSI Initiator Name field with a name in this format to help you with the structure. For more information about IQNs, see 3.2.6. iSCSI Names in RFC 3720 - Internet Small Computer Systems Interface (iSCSI) available from tools.ietf.org and 1. iSCSI Names and Addresses in RFC 3721 - Internet Small Computer Systems Interface (iSCSI) Naming and Discovery available from tools.ietf.org.

6. Select the Discovery Authentication Type drop-down menu to specify the type of authentication to use for iSCSI discovery. The following options are available:

   • No credentials
   • CHAP pair
   • CHAP pair and a reverse pair

7. Do one of the following:

   1. If you selected the CHAP pair as the authentication type, enter the user name and password for the iSCSI target in the CHAP Username and CHAP Password fields.
   2. If you selected the CHAP pair and a reverse pair as the authentication type, enter the user name and password for the iSCSI target in the CHAP Username and CHAP Password field, and the user name and password for the iSCSI initiator in the Reverse CHAP Username and Reverse CHAP Password fields.
8. Optional: Select the Bind targets to network interfaces check box.

9. Click Start Discovery.

   The installation program attempts to discover an iSCSI target based on the information provided. If discovery succeeds, the Add iSCSI Storage Target window displays a list of all iSCSI nodes discovered on the target.

10. Select the check boxes for the node that you want to use for installation.

    The Node login authentication type menu contains the same options as the Discovery Authentication Type menu. However, if you need credentials for discovery authentication, use the same credentials to log in to a discovered node.

11. Click the additional Use the credentials from discovery drop-down menu. When you provide the proper credentials, the Log In button becomes available.

12. Click Log In to initiate an iSCSI session.

    While the installer uses iscsiadm to find and log into iSCSI targets, iscsiadm automatically stores any information about these targets in the iscsiadm iSCSI database. The installer then copies this database to the installed system and marks any iSCSI targets that are not used for root partition, so that the system automatically logs in to them when it starts. If the root partition is placed on an iSCSI target, initrd logs into this target and the installer does not include this target in start up scripts to avoid multiple attempts to log into the same target.

Procedure

1. From the Installation Summary window, click Installation Destination. The Installation Destination window opens, listing all available drives.
2. Under the Specialized & Network Disks section, click Add a disk. The storage devices selection window opens.
3. Click Add FCoE SAN. A dialog box opens for you to configure network interfaces for discovering FCoE storage devices.
4. Select a network interface that is connected to an FCoE switch in the NIC drop-down menu.
5. Click Add FCoE disk(s) to scan the network for SAN devices.

6. Select the required check boxes:

   • Use DCB:Data Center Bridging (DCB) is a set of enhancements to the Ethernet protocols designed to increase the efficiency of Ethernet connections in storage networks and clusters. Select the check box to enable or disable the installation program’s awareness of DCB. Enable this option only for network interfaces that require a host-based DCBX client. For configurations on interfaces that use a hardware DCBX client, disable the check box.
   • Use auto vlan:Auto VLAN is enabled by default and indicates whether VLAN discovery should be performed. If this check box is enabled, then the FIP (FCoE Initiation Protocol) VLAN discovery protocol runs on the Ethernet interface when the link configuration has been validated. If they are not already configured, network interfaces for any discovered FCoE VLANs are automatically created and FCoE instances are created on the VLAN interfaces.
7. Discovered FCoE devices are displayed under the Other SAN Devices tab in the Installation Destination window.

Procedure

1. From the Installation Summary window, click Installation Destination. The Installation Destination window opens, listing all available drives.
2. Under the Specialized & Network Disks section, click Add a disk. The storage devices selection window opens.
3. Click Add DASD ECKD. The Add DASD Storage Target dialog box opens and prompts you to specify a device number, such as 0.0.0204, and attach additional DASDs that were not detected when the installation started.
4. Type the device number of the DASD that you want to attach in the Device number field.

5. Click Start Discovery.

   If a DASD with the specified device number is found and if it is not already attached, the dialog box closes and the newly-discovered drives appear in the list of drives. You can then select the check boxes for the required devices and click Done. The new DASDs are available for selection, marked as DASD device 0.0.xxxx in the Local Standard Disks section of the Installation Destination window.

   If you entered an invalid device number, or if the DASD with the specified device number is already attached to the system, an error message appears in the dialog box, explaining the error and prompting you to try again with a different device number.

Procedure

1. From the Installation Summary window, click Installation Destination. The Installation Destination window opens, listing all available drives.
2. Under the Specialized & Network Disks section, click Add a disk. The storage devices selection window opens.

3. Click Add ZFCP LUN. The Add zFCP Storage Target dialog box opens allowing you to add a FCP (Fibre Channel Protocol) storage device.

   64-bit IBM Z requires that you enter any FCP device manually so that the installation program can activate FCP LUNs. You can enter FCP devices either in the graphical installation, or as a unique parameter entry in the parameter or CMS configuration file. The values that you enter must be unique to each site that you configure.

4. Type the 4 digit hexadecimal device number in the Device number field.

5. Provide following details when the zFCP device is not configured in NPIV mode or auto LUN scanning is disabled by the zfcp.allow_lun_scan=0 kernel module parameter:

   1. Type the 16 digit hexadecimal World Wide Port Number (WWPN) in the WWPN field.
   2. Type the 16 digit hexadecimal FCP LUN identifier in the LUN field.

6. Click Start Discovery to connect to the FCP device.

   The newly-added devices are displayed in the IBM Z tab of the Installation Destination window.

   Use only lower-case letters in hex values. If you enter an incorrect value and click Start Discovery, the installation program displays a warning. You can edit the configuration information and retry the discovery attempt. For more information about these values, consult the hardware documentation and check with your system administrator.

Procedure

1. From the Installation Summary window, click Installation Destination.

   The Installation Destination window opens, listing all available devices. This includes local (PCI Express transport) NVMe™ devices.

2. Under the Specialized & Network Disks section, click Add a disk…​.

   The storage devices selection window opens.

3. Click the NVMe™ Fabrics Devices tab.
4. Optional: If the device list is too long, use the Filter by option to view specific devices.
5. Select the devices from the list by using check boxes.

6. Click Done to return to the Installation Destination window.

   The NVMe™ device that you reconfigured is displayed in the Specialized & Network Disks section.

7. Click Done to return to the Installation Summary window.