Red Hat Summit Red Hat SummitSupportoConsoleSviluppatoriInizia una provaContatti

Questo contenuto non è disponibile nella lingua selezionata.

Chapter 7. Configuring an iSCSI initiator

An iSCSI initiator forms a session to connect to the iSCSI target. By default, an iSCSI service is lazily started and the service starts after running the iscsiadm command. If root is not on an iSCSI device or there are no nodes marked with node.startup = automatic then the iSCSI service will not start until an iscsiadm command is executed that requires iscsid or the iscsi kernel modules to be started.

Run the systemctl start iscsid command as root to force the iscsid service to run and iSCSI kernel modules to load.

7.1. Creating an iSCSI initiator
Copia collegamento

Create an iSCSI initiator to connect to the iSCSI target to access the storage devices on the server. For more information, see the targetcli(8) and iscsiadm(8) man pages on your system.

Prerequisites

  • You have an iSCSI target’s hostname and IP address:

    • If you are connecting to a storage target that the external software created, find the target’s hostname and IP address from the storage administrator.
    • If you are creating an iSCSI target, see Creating an iSCSI target.

Procedure

  1. Install iscsi-initiator-utils on client machine: 

    # dnf install iscsi-initiator-utils
    Copy to Clipboard Toggle word wrap

  2. Start the iscsid service: 

    # systemctl start iscsid
    Copy to Clipboard Toggle word wrap

  3. Check the initiator name: 

    # cat /etc/iscsi/initiatorname.iscsi

InitiatorName=iqn.2006-04.com.example:888
    Copy to Clipboard Toggle word wrap

  4. If the ACL was given a custom name in Creating an iSCI ACL, update the initiator name to match the ACL:

    1. Open the /etc/iscsi/initiatorname.iscsi file and modify the initiator name: 

      # vi /etc/iscsi/initiatorname.iscsi

InitiatorName=custom-name
      Copy to Clipboard Toggle word wrap

    2. Restart the iscsid service: 

      # systemctl restart iscsid
      Copy to Clipboard Toggle word wrap

  5. Discover the target and log in to the target with the displayed target IQN: 

    # iscsiadm -m discovery -t st -p 10.64.24.179
    10.64.24.179:3260,1 iqn.2006-04.com.example:444

# iscsiadm -m node -T iqn.2006-04.com.example:444 -l
    Logging in to [iface: default, target: iqn.2006-04.com.example:444, portal: 10.64.24.179,3260] (multiple)
    Login to [iface: default, target: iqn.2006-04.com.example:444, portal: 10.64.24.179,3260] successful.
    Copy to Clipboard Toggle word wrap

    Replace 10.64.24.179 with the target-ip-address.

    You can use this procedure for any number of initiators connected to the same target if their respective initiator names are added to the ACL as described in the Creating an iSCSI ACL.

  6. Find the iSCSI disk name and create a file system on this iSCSI disk: 

    # grep "Attached SCSI" /var/log/messages

# mkfs.ext4 /dev/disk_name
    Copy to Clipboard Toggle word wrap

    Replace disk_name with the iSCSI disk name displayed in the /var/log/messages file.

  7. Mount the file system: 

    # mkdir /mount/point

# mount /dev/disk_name /mount/point
    Copy to Clipboard Toggle word wrap

    Replace /mount/point with the mount point of the partition.

  8. Edit the /etc/fstab file to mount the file system automatically when the system boots: 

    # vi /etc/fstab

/dev/disk_name /mount/point ext4 _netdev 0 0
    Copy to Clipboard Toggle word wrap

    Replace disk_name with the iSCSI disk name and /mount/point with the mount point of the partition.

By using the Challenge-Handshake Authentication Protocol (CHAP), users can protect the target with a password. The initiator must be aware of this password to be able to connect to the target. For more information, see the iscsiadm(8) man page on your system.

Prerequisites

Procedure

  1. Enable CHAP authentication in the iscsid.conf file: 

    # vi /etc/iscsi/iscsid.conf

node.session.auth.authmethod = CHAP
    Copy to Clipboard Toggle word wrap

    By default, the node.session.auth.authmethod is set to None

  2. Add target username and password in the iscsid.conf file: 

    node.session.auth.username = redhat
node.session.auth.password = redhat_passwd
    Copy to Clipboard Toggle word wrap

  3. Restart the iscsid service: 

    # systemctl restart iscsid
    Copy to Clipboard Toggle word wrap

7.3. Monitoring an iSCSI session by using the iscsiadm utility
Copia collegamento

You can monitor the iscsi session by using the iscsiadm utility.

By default, an iSCSI service is lazily started and the service starts after running the iscsiadm command. If root is not on an iSCSI device or there are no nodes marked with node.startup = automatic then the iSCSI service will not start until an iscsiadm command is executed that requires iscsid or the iscsi kernel modules to be started.

Use the systemctl start iscsid command as root to force the iscsid service to run and iSCSI kernel modules to load.

For more information, see:

  • /usr/share/doc/iscsi-initiator-utils/README file
  • iscsiadm(8) man page on your system

Procedure

  1. Install the iscsi-initiator-utils on client machine: 

    # dnf install iscsi-initiator-utils
    Copy to Clipboard Toggle word wrap

  2. Find information about the running sessions: 

    # iscsiadm -m session -P 3
    Copy to Clipboard Toggle word wrap

    This command displays the session or device state, session ID (sid), some negotiated parameters, and the SCSI devices accessible through the session.

    • For shorter output, for example, to display only the sid-to-node mapping, run: 

      # iscsiadm -m session -P 0
        or
# iscsiadm -m session

tcp [2] 10.15.84.19:3260,2 iqn.1992-08.com.netapp:sn.33615311
tcp [3] 10.15.85.19:3260,3 iqn.1992-08.com.netapp:sn.33615311
      Copy to Clipboard Toggle word wrap

      These commands print the list of running sessions in the following format: driver [sid] target_ip:port,target_portal_group_tag proper_target_name.

7.4. DM Multipath overrides of the device timeout
Copia collegamento

The recovery_tmo sysfs option controls the timeout for a particular iSCSI device. The following options globally override the recovery_tmo values:

  • The replacement_timeout configuration option globally overrides the recovery_tmo value for all iSCSI devices.

  • For all iSCSI devices that are managed by DM Multipath, the fast_io_fail_tmo option in DM Multipath globally overrides the recovery_tmo value.

    The fast_io_fail_tmo option in DM Multipath also overrides the fast_io_fail_tmo option in Fibre Channel devices.

The DM Multipath fast_io_fail_tmo option takes precedence over replacement_timeout. Every time the multipathd service is reloaded, it resets recovery_tmo to the value of the fast_io_fail_tmo configuration option. Use the DM multipath fast_io_fail_tmo configuration option to override recovery_tmo in devices managed by DM Multipath.

Torna in cima
Red Hat logoGithubredditYoutubeTwitter

Formazione

Prova, acquista e vendi

Community

Informazioni sulla documentazione di Red Hat

Aiutiamo gli utenti Red Hat a innovarsi e raggiungere i propri obiettivi con i nostri prodotti e servizi grazie a contenuti di cui possono fidarsi. Esplora i nostri ultimi aggiornamenti.

Rendiamo l’open source più inclusivo

Red Hat si impegna a sostituire il linguaggio problematico nel codice, nella documentazione e nelle proprietà web. Per maggiori dettagli, visita il Blog di Red Hat.

Informazioni su Red Hat

Forniamo soluzioni consolidate che rendono più semplice per le aziende lavorare su piattaforme e ambienti diversi, dal datacenter centrale all'edge della rete.

Theme

© 2025 Red Hat