Skip to main content
ONTAP SAN Host Utilities

Use Red Hat Enterprise Linux 6.6 with ONTAP

Contributors netapp-pcarriga netapp-ranuk netapp-reenu netapp-sdaffy netapp-sarajane
PDFs

You can use the ONTAP SAN host configuration settings to configure Red Hat Enterprise Linux 6.6 with ONTAP as the target.

Install the Linux Host Utilities

The NetApp Linux Host Utilities software package is available on the NetApp Support Site in a 32-bit and 64-bit .rpm file. If you don't know which file is right for your configuration, use the Interoperability Matrix Tool to verify which one you need.

NetApp strongly recommends installing the Linux Host Utilities, but it's not mandatory. The utilities don't change any settings on your Linux host. The utilities improve management and assist NetApp customer support in gathering information about your configuration.

If you have Linux Host Utilities currently installed, you should either upgrade it to the latest version, or remove it and follow these steps to install the latest version.

Steps

  1. Download the 32-bit or 64-bit Linux Host Utilities software package from the NetApp Support Site to your host.

  2. Install the software package:

    rpm -ivh netapp_linux_unified_host_utilities-7-1.x86_64

Note You can use the configuration settings provided in this procedure to configure cloud clients connected to Cloud Volumes ONTAP and Amazon FSx for ONTAP.

SAN Toolkit

The toolkit is installed automatically when you install the NetApp Host Utilities package. This kit provides the sanlun utility, which helps you manage LUNs and HBAs. The sanlun command returns information about the LUNs mapped to your host, multipathing, and information necessary to create initiator groups.

Example

In the following example, the sanlun lun show command returns LUN information.

# sanlun lun show all

Example output:

controller(7mode/E-Series)/            device     host               lun
vserver(cDOT/FlashRay)   lun-pathname  filename   adapter  protocol  size    Product
------------------------------------------------------------------------------------
data_vserver          /vol/vol1/lun1   /dev/sdb   host16   FCP       120.0g  cDOT
data_vserver          /vol/vol1/lun1   /dev/sdc   host15   FCP       120.0g  cDOT
data_vserver          /vol/vol2/lun2   /dev/sdd   host16   FCP       120.0g  cDOT
data_vserver          /vol/vol2/lun2   /dev/sde   host15   FCP       120.0g  cDOT

SAN Booting

Before you begin

If you decide to use SAN booting, it must be supported by your configuration. You can use the Interoperability Matrix Tool to verify that your OS, HBA, HBA firmware and the HBA boot BIOS, and ONTAP version are supported.

Steps

  1. Map the SAN boot LUN to the host.

  2. Verify that multiple paths are available.

    Note Multiple paths become available after the host OS is up and running on the paths.

  3. Enable SAN booting in the server BIOS for the ports to which the SAN boot LUN is mapped.

    For information on how to enable the HBA BIOS, see your vendor-specific documentation.

  4. Reboot the host to verify that the boot was successful.

Multipathing

For Red Hat Enterprise Linux (RHEL) 6.6 the /etc/multipath.conf file must exist, but you do not need to make specific changes to the file. RHEL 6.6 is compiled with all settings required to recognize and correctly manage ONTAP LUNs.
To Enable ALUA Handler, perform the following steps:

Steps

  1. Create a backup of the initrd-image.

  2. Append the following parameter value to the kernel for ALUA and non-ALUA to work:
    rdloaddriver=scsi_dh_alua

    Example
    kernel /vmlinuz-2.6.32-358.6.1.el6.x86_64 ro root=/dev/mapper/ vg_ibmx355021082-lv_root rd_NO_LUKS rd_LVM_LV=vg_ibmx355021082/ lv_root LANG=en_US.UTF-8 rd_LVM_LV=vg_ibmx355021082/lv_swap rd_NO_MD SYSFONT=latarcyrheb-sun16 crashkernel=auto KEYBOARDTYPE=pc KEYTABLE=us rd_NO_DM rhgb quiet rdloaddriver=scsi_dh_alua

  3. Use the mkinitrd command to recreate the initrd-image.
    RHEL 6x and later versions use either:
    The command: mkinitrd -f /boot/ initrd-"uname -r".img uname -r
    Or
    The command: dracut -f

  4. Reboot the host.

  5. Verify the output of the cat /proc/cmdline command to ensure that the setting is complete.

You can use the multipath -ll command to verify the settings for your ONTAP LUNs.

The following sections provide example multipath outputs for a LUN mapped to ASA and non-ASA personas.

All SAN Array configurations

All SAN Array (ASA) configurations optimize all paths to a given LUN, keeping them active. This improves performance by serving I/O operations through all paths at the same time.

Example

The following example displays the correct output for an ONTAP LUN.

# multipath -ll
3600a0980383034466b2b4a3775474859 dm-3 NETAPP,LUN C-Mode
size=20G features='4 queue_if_no_path pg_init_retries 50 retain_attached_hw_handle' hwhandler='1 alua' wp=rw
|-+- policy='round-robin 0' prio=50 status=active
|- 1:0:8:1  sdb 8:16 active ready running
|- 2:0:8:1  sdd 8:48 active ready running
|- 1:0:9:1  sdc 8:32 active ready running
|- 2:0:9:1  sde 8:64 active ready running
Note A single LUN shouldn't require more than four paths. Having more than four paths might cause path issues during storage failures.

Non-ASA configurations

For non-ASA configurations, there should be two groups of paths with different priorities. The paths with higher priorities are Active/Optimized. This means they are serviced by the controller where the aggregate is located. The paths with lower priorities are active but non-optimized because they are served from a different controller. The non-optimized paths are only used when optimized paths are not available.

Example

The following example displays the correct output for an ONTAP LUN with two Active/Optimized paths and two Active/Non-Optimized paths.

# multipath -ll
3600a0980383034466b2b4a3775474859 dm-3 NETAPP,LUN C-Mode
size=20G features='4 queue_if_no_path pg_init_retries 50 retain_attached_hw_handle' hwhandler='1 alua' wp=rw
|-+- policy='round-robin 0' prio=50 status=active
| |- 1:0:8:1  sdb 8:16 active ready running
| `- 2:0:8:1  sdd 8:48 active ready running
`-+- policy='round-robin 0' prio=10 status=enabled
  |- 1:0:9:1  sdc 8:32 active ready running
  `- 2:0:9:1  sde 8:64 active ready running
Note A single LUN shouldn't require more than four paths. Having more than four paths might cause path issues during storage failures.

The RHEL 6.6 OS is compiled to recognize ONTAP LUNs and automatically set all configuration parameters correctly for both ASA and non-ASA configuration.

The multipath.conf file must exist for the multipath daemon to start. If this file doesn't exist, you can create an empty, zero-byte file by using the touch /etc/multipath.conf command.

The first time you create the multipath.conf file, you might need to enable and start the multipath services by using the following commands:

chkconfig multipathd on
/etc/init.d/multipathd start

You don't need to add anything directly to the multipath.conf file unless you have devices that you don't want multipath to manage or you have existing settings that override defaults. To exclude unwanted devices, add the following syntax to the multipath.conf file, replacing <DevId> with the worldwide identifier (WWID) string of the device you want to exclude:

blacklist {
        wwid <DevId>
        devnode "^(ram|raw|loop|fd|md|dm-|sr|scd|st)[0-9]*"
        devnode "^hd[a-z]"
        devnode "^cciss.*"
}

The following example determines the WWID of a device and adds it to the multipath.conf file.

Steps

  1. Determine the WWID:

    /lib/udev/scsi_id -gud /dev/sda
    3600a098038314c4a433f5774717a3046

    sda is the local SCSI disk that you want to add to the blacklist.

  2. Add the WWID to the blacklist stanza in /etc/multipath.conf:

    blacklist {
     wwid   3600a098038314c4a433f5774717a3046
     devnode "^(ram|raw|loop|fd|md|dm-|sr|scd|st)[0-9]*"
     devnode "^hd[a-z]"
     devnode "^cciss.*"
}

Always check your /etc/multipath.conf file, especially in the defaults section, for legacy settings that might be overriding default settings.

The following table demonstrates the critical multipathd parameters for ONTAP LUNs and the required values. If a host is connected to LUNs from other vendors and any of these parameters are overridden, they must be corrected by later stanzas in the multipath.conf file that apply specifically to ONTAP LUNs. Without this correction, the ONTAP LUNs might not work as expected. You should only override these defaults in consultation with NetApp, the OS vendor, or both, and only when the impact is fully understood.

Parameter Setting

detect_prio

yes

dev_loss_tmo

"infinity"

failback

immediate

fast_io_fail_tmo

5

features

"3 queue_if_no_path pg_init_retries 50"

flush_on_last_del

"yes"

hardware_handler

"0"

no_path_retry

queue

path_checker

"tur"

path_grouping_policy

"group_by_prio"

path_selector

"round-robin 0"

polling_interval

5

prio

"ontap"

product

LUN.*

retain_attached_hw_handler

yes

rr_weight

"uniform"

user_friendly_names

no

vendor

NETAPP
Example

The following example shows how to correct an overridden default. In this case, the multipath.conf file defines values for path_checker and no_path_retry that are not compatible with ONTAP LUNs. If they cannot be removed because of other SAN arrays still attached to the host, these parameters can be corrected specifically for ONTAP LUNs with a device stanza.

defaults {
   path_checker      readsector0
   no_path_retry      fail
}

devices {
   device {
      vendor         "NETAPP  "
      product         "LUN.*"
      no_path_retry     queue
      path_checker      tur
   }
}

Configure KVM settings

You don't need to configure settings for a Kernel-based Virtual Machine because the LUN is mapped to the hypervisor.

ASM mirroring

Automatic Storage Management (ASM) mirroring might require changes to the Linux multipath settings to allow ASM to recognize a problem and switch over to an alternate failure group. Most ASM configurations on ONTAP use external redundancy, which means that data protection is provided by the external array and ASM doesn't mirror data. Some sites use ASM with normal redundancy to provide two-way mirroring, normally across different sites. See Oracle databases on ONTAP for further information.

Known issues

The RHEL 6.6 with ONTAP release has the following known issues:

NetApp Bug ID Title Description

863878

Kernel crash occurs with RHEL 6U6 host during storage failures

You might observe kernel crash on RHEL 6U6 host during storage/fabric.

1076584

I/O stall up to 300 sec seen with QLogic 16G FC (QLE2672) host during storage failures in RHEL 6U4

You might observe an I/O stall up to 300 sec on QLogic 16G FC (QLE2672) host during storage/fabric failures.

795684

RHEL6 U5 multipathd incorrectly group multipath maps during MoD and storage failover fault operations

You might observe an incorrect path grouping on LUNs during LUN move on demand operation along with storage faults. During LUN move operation multipath path priorities will change and multipath is unable to reloads the device table due to device failure caused by storage fault. This leads to incorrect path grouping.