docs.netapp.com · ONTAP SAN Host Configuration This content provides distribution-specific...

ONTAP SAN Host ConfigurationONTAP SAN HostNetAppJune 26, 2020

This PDF was generated from https://docs.netapp.com/us-en/ontap-sanhost/index.html on June 26, 2020. Alwayscheck docs.netapp.com for the latest.

Table of ContentsONTAP SAN Host Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1

More information. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1

NVMe/FC Host Configurations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2

RHEL . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2

SUSE. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7

Oracle Linux . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12

FC/iSCSI Host Configurations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19

RHEL . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19

SUSE. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 146

Oracle Linux . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 198

ONTAP SAN Host ConfigurationThis content provides distribution-specific guidance about how to configureONTAP SAN hosts for the NVMe, iSCSI, and FC protocols.

For best performance and to ensure successful failover, it is important to correctly configure SAN hostsusing ONTAP storage. These documents show how to quickly set up a best practice configuration.

For iSCSI and FC, this documentation replaces the traditional Linux Unified Host Utilities guides. Eachdocument is specific to one distribution and version of Linux, so you see only the information for yourexact version. If your distribution and version of Linux is not yet listed, please check back soon.

More informationYou can find additional information on SAN configurations in the following documentation:

All SAN Array Software Configuration GuideSAN Administration GuideSAN Configuration Guide

https://docs.netapp.com/ontap-9/topic/com.netapp.doc.dot-asa-config/home.html

https://docs.netapp.com/ontap-9/topic/com.netapp.doc.dot-cm-sanag/home.html

https://docs.netapp.com/ontap-9/topic/com.netapp.doc.dot-cm-sanconf/home.html

NVMe/FC Host Configurations

RHEL

NVMe/FC Host Configuration for RHEL 8.1 with ONTAP

Supportability

NVMe/FC is supported on ONTAP 9.6 or later for the following versions of RHEL:

• RHEL 8.1

RHEL 8.1 host can run both NVMe & SCSI traffic through the same fibre channel initiator adapter ports.See the Hardware Universe for a list of supported FC adapters and controllers.For the most current list of supported configurations see the NetApp Interoperability Matrix.

Known limitations

• Native NVMe/FC auto-connect scripts are not available in the nvme-cli package.You can use the HBA vendor provided external auto-connect script.

• By default, NVMe multipath is disabled.It must be manually enabled. Steps are provided in the section on Enabling NVMe/FC on RHEL 8.1.

• By default, round-robin load balancing is not enabled.You must write a udev rule to enable this functionality. Steps are provided in the section onEnabling NVMe/FC on RHEL 8.1.

Enabling NVMe/FC on RHEL 8.1

1. Install Red Hat Enterprise Linux 8.1 on the server.

2. After the installation is complete, verify that you are running the specified Red Hat EnterpriseLinux kernel. See the NetApp Interoperability Matrix for the most current list of supportedversions.

# uname -r4.18.0-147.el8.x86_64

3. Install the nvme-cli-1.8.1-3.el8 package.

# rpm -qa|grep nvme-clinvme-cli-1.8.1-3.el8.x86_64

4. Enable in-kernel NVMe multipath.

https://hwu.netapp.com/Home/Index

https://mysupport.netapp.com/matrix/


# grubby –args=nvme_core.multipath=Y –update-kernel /boot/vmlinuz-4.18.0-147.el8.x86_64

5. Add the string below as a separate udev rule at /lib/udev/rules.d/71-nvme-iopolicy-netapp-ONTAP.rules. This enables round-robin load balancing for NVMe multipath.

# Enable round-robin for NetApp ONTAPACTION==”add”, SUBSYSTEM==”nvme-subsystem”, ATTR{model}==”NetApp ONTAP Controller”,ATTR{iopolicy}=”round-robin

6. On the RHEL 8.1 host, check the hostnqn string at /etc/nvme/hostnqn and verify that it matches thehostnqn string for the corresponding subsystem on the ONTAP array.

# cat /etc/nvme/hostnqnnqn.2014-08.org.nvmexpress:uuid:75953f3b-77fe-4e03-bf3c-09d5a156fbcd

*> vserver nvme subsystem host show -vserver vs_nvme_10Vserver Subsystem Host NQN------- --------- -------------------------------------- -----------rhel_141_nvme_ss_10_0nqn.2014-08.org.nvmexpress:uuid:75953f3b-77fe-4e03-bf3c-09d5a156fbcd

Note:

If the hostnqn strings do not match, you should use the vserver modify command to update thehostnqn string on your corresponding ONTAP array subsystem to match to hostnqn string from/etc/nvme/hostnqn on the host.

7. Reboot the host.

Configuring the Broadcom FC Adapter for NVMe/FC

1. Verify that you are using the supported adapter. For the most current list of supported adapters seethe NetApp Interoperability Matrix.

# cat /sys/class/scsi_host/host*/modelnameLPe32002-M2LPe32002-M2

# cat /sys/class/scsi_host/host*/modeldescEmulex LightPulse LPe32002-M2 2-Port 32Gb Fibre Channel AdapterEmulex LightPulse LPe32002-M2 2-Port 32Gb Fibre Channel Adapter

2. Copy and install the Broadcom lpfc outbox driver and auto-connect scripts.

# tar -xvzf elx-lpfc-dd-rhel8-12.4.243.20-ds-1.tar.gz# cd elx-lpfc-dd-rhel8-12.4.2453.20-ds-1# ./elx_lpfc_install-sh -i -n

Note:

The native drivers that come bundled with the OS are called inbox drivers. If you download theoutbox drivers (drivers that are not included with the OS release), an auto-connect script isincluded in the download and should be installed as part of the driver installation process.

3. Reboot the host.

4. Verify that you are using the recommended Broadcom lpfc firmware, outbox driver & auto-connectpackage versions.

# cat /sys/class/scsi_host/host*/fwrev12.4.243.20, sil-4.2.c12.4.243.20, sil-4.2.c

# cat /sys/module/lpfc/version0:12.4.243.20

# rpm -qa | grep nvmefcnvmefc-connect-12.6.61.0-1.noarch

5. Verify that lpfc_enable_fc4_type is set to 3.

# cat /sys/module/lpfc/parameters/lpfc_enable_fc4_type3

6. Verify that the initiator ports are up and running.

# cat /sys/class/fc_host/host*/port_name0x10000090fae0ec610x10000090fae0ec62

# cat /sys/class/fc_host/host*/port_stateOnlineOnline

7. Verify that the NVMe/FC initiator ports are enabled, running and able to see the target LIFs.

# cat /sys/class/scsi_host/host*/nvme_infoNVME Initiator EnabledXRI Dist lpfc0 Total 6144 NVME 2947 SCSI 2977 ELS 250NVME LPORT lpfc0 WWPN x10000090fae0ec61 WWNN x20000090fae0ec61 DID x012000 ONLINENVME RPORT WWPN x202d00a098c80f09 WWNN x202c00a098c80f09 DID x010201 TARGET DISCSRVCONLINENVME RPORT WWPN x203100a098c80f09 WWNN x202c00a098c80f09 DID x010601 TARGET DISCSRVCONLINENVME Statistics…

Validating NVMe/FC

1. Verify the following NVMe/FC settings.

# cat /sys/module/nvme_core/parameters/multipathY

# cat /sys/class/nvme-subsystem/nvme-subsys*/modelNetApp ONTAP ControllerNetApp ONTAP Controller

# cat /sys/class/nvme-subsystem/nvme-subsys*/iopolicyround-robinround-robin

2. Verify that the namespaces are created.

# nvme listNode SN Model Namespace Usage Format FW Rev---------------- -------------------- -----------------------/dev/nvme0n1 80BADBKnB/JvAAAAAAAC NetApp ONTAP Controller 1 53.69 GB / 53.69 GB 4 KiB+ 0 B FFFFFFFF

3. Verify the status of the ANA paths.

# nvme list-subsys/dev/nvme0n1Nvme-subsysf0 – NQN=nqn.1992-08.com.netapp:sn.341541339b9511e8a9b500a098c80f09:subsystem.rhel_141_nvme_ss_10_0\+- nvme0 fc traddr=nn-0x202c00a098c80f09:pn-0x202d00a098c80f09 host_traddr=nn-0x20000090fae0ec61:pn-0x10000090fae0ec61 live optimized+- nvme1 fc traddr=nn-0x207300a098dfdd91:pn-0x207600a098dfdd91 host_traddr=nn-0x200000109b1c1204:pn-0x100000109b1c1204 live inaccessible+- nvme2 fc traddr=nn-0x207300a098dfdd91:pn-0x207500a098dfdd91 host_traddr=nn-0x200000109b1c1205:pn-0x100000109b1c1205 live optimized+- nvme3 fc traddr=nn-0x207300a098dfdd91:pn-0x207700a098dfdd91 host traddr=nn-0x200000109b1c1205:pn-0x100000109b1c1205 live inaccessible

4. Verify the NetApp plug-in for ONTAP devices.

# nvme netapp ontapdevices -o columnDevice Vserver Namespace Path NSID UUID Size------- -------- ------------------------- ------ ----- -----/dev/nvme0n1 vs_nvme_10 /vol/rhel_141_vol_10_0/rhel_141_ns_10_0 155baf453-f629-4a18-9364-b6aee3f50dad 53.69GB

# nvme netapp ontapdevices -o json{ "ONTAPdevices" : [ { Device" : "/dev/nvme0n1", "Vserver" : "vs_nvme_10", "Namespace_Path" : "/vol/rhel_141_vol_10_0/rhel_141_ns_10_0", "NSID" : 1, "UUID" : "55baf453-f629-4a18-9364-b6aee3f50dad", "Size" : "53.69GB", "LBA_Data_Size" : 4096, "Namespace_Size" : 13107200 }]

Enabling 1MB I/O Size for Broadcom NVMe/FC

The lpfc_sg_seg_cnt parameter must be set to 256 in order for the host to issue 1MB size I/O.

1. Set the lpfc_sg_seg_cnt parameter to 256.

# cat /etc/modprobe.d/lpfc.confoptions lpfc lpfc_sg_seg_cnt=256

2. Run a dracut -f command, and reboot the host.

3. Verify that lpfc_sg_seg_cnt is 256.

# cat /sys/module/lpfc/parameters/lpfc_sg_seg_cnt256

LPFC Verbose Logging

1. You can set the lpfc_log_verbose driver setting to any of the following values to log NVMe/FC events.

#define LOG_NVME 0x00100000 /* NVME general events. */#define LOG_NVME_DISC 0x00200000 /* NVME Discovery/Connect events. */#define LOG_NVME_ABTS 0x00400000 /* NVME ABTS events. */#define LOG_NVME_IOERR 0x00800000 /* NVME IO Error events. */

2. After setting any of these values, run dracut-f and reboot host.

3. After rebooting, verify the settings.

# cat /etc/modprobe.d/lpfc.conflpfc_enable_fc4_type=3 lpfc_log_verbose=0xf00083# cat /sys/module/lpfc/parameters/lpfc_log_verbose15728771

SUSE

NVMe/FC Host Configuration for SUSE Linux Enterprise Server 15 SP1 withONTAP

Supportability

NVMe/FC is supported on ONTAP 9.6 or later for the following versions of SLES:

• SLES15 SP1

SLES15 SP1 host can run both NVMe/FC, & FCP (FC-SCSI) traffic through the same fibre channelinitiator adapter ports. See the Hardware Universe for a list of supported FC adapters andcontrollers.

For the most current list of supported configurations & versions, see the NetApp InteroperabilityMatrix.

Known limitations

None. Native NVMe/FC auto-connect scripts are included in the nvme-cli package. You can use thenative inbox lpfc driver on SLES15 SP1.

Enabling NVMe/FC on SLES15 SP1

1. Upgrade to SLES15 SP1 MU kernel-default-4.12.14-197.40.1. See the NetApp Interoperability Matrixfor the most current list of supported versions.

# uname -r4.12.14-197.40-default

2. Upgrade to nvme-cli-1.8.1-6.9.1 MU package.

This nvme-cli package contains the native NVMe/FC auto-connect scripts, so you do not need toinstall the external NVMe/FC auto-connect scripts provided by Broadcom on the SLES15 SP1 host.This package also includes the ONTAP udev rule which enables round-robin load balancing forNVMe multipath, and the NetApp plug-in for ONTAP devices.

# rpm -qa | grep nvme-clinvme-cli-1.8.1-6.9.1.x86_64

3. On the SLES15 SP1 host, check the hostnqn string at /etc/nvme/hostnqn and verify that it matchesthe hostnqn string for the corresponding subsystem on the ONTAP array.






*> vserver nvme subsystem host show -vserver vs_nvme_10Vserver Subsystem Host NQN------- --------- -------------------------------------- -----------sles_117_nvme_ss_10_0nqn.2014-08.org.nvmexpress:uuid:75953f3b-77fe-4e03-bf3c-09d5a156fbcd

4. Reboot the host.





2. Verify that you are using the recommended Broadcom lpfc firmware and native inbox driverversions.











Validating NVMe/FC








# nvme list-subsys/dev/nvme0n1Nvme-subsysf0 – NQN=nqn.1992-08.com.netapp:sn.341541339b9511e8a9b500a098c80f09:subsystem.sles_117_nvme_ss_10_0\+- nvme0 fc traddr=nn-0x202c00a098c80f09:pn-0x202d00a098c80f09 host_traddr=nn-0x20000090fae0ec61:pn-0x10000090fae0ec61 live optimized+- nvme1 fc traddr=nn-0x207300a098dfdd91:pn-0x207600a098dfdd91 host_traddr=nn-0x200000109b1c1204:pn-0x100000109b1c1204 live inaccessible+- nvme2 fc traddr=nn-0x207300a098dfdd91:pn-0x207500a098dfdd91 host_traddr=nn-0x200000109b1c1205:pn-0x100000109b1c1205 live optimized+- nvme3 fc traddr=nn-0x207300a098dfdd91:pn-0x207700a098dfdd91 host traddr=nn-0x200000109b1c1205:pn-0x100000109b1c1205 live inaccessible


# nvme netapp ontapdevices -o columnDevice Vserver Namespace Path NSID UUID Size------- -------- ------------------------- ------ ----- -----/dev/nvme0n1 vs_nvme_10 /vol/sles_117_vol_10_0/sles_117_ns_10_0 155baf453-f629-4a18-9364-b6aee3f50dad 53.69GB

# nvme netapp ontapdevices -o json{ "ONTAPdevices" : [ { Device" : "/dev/nvme0n1", "Vserver" : "vs_nvme_10", "Namespace_Path" : "/vol/sles_117_vol_10_0/sles_117_ns_10_0", "NSID" : 1, "UUID" : "55baf453-f629-4a18-9364-b6aee3f50dad", "Size" : "53.69GB", "LBA_Data_Size" : 4096, "Namespace_Size" : 13107200 }]














Oracle Linux

NVMe/FC Host Configuration for Oracle Linux 7.7 with ONTAP

Supportability

NVMe/FC is supported on ONTAP 9.6 or later for the following versions of Oracle Linux

• OL 7.7

OL 7.7 host can run both NVMe & SCSI traffic through the same fibre channel initiator adapterports. See the Hardware Universe for a list of supported FC adapters and controllers.

For the most current list of supported configurations see the NetApp Interoperability Matrix.

Known limitations

• Native NVMe/FC auto-connect scripts are not available in the nvme-cli package.You can use the HBA vendor provided external auto-connect scripts.

• By default, round-robin load balancing is not enabled.You must write a udev rule to enable this functionality. Steps are provided in the section onEnabling NVMe/FC on OL 7.7.

Enabling NVMe on OL 7.7

1. Ensure the default Oracle Linux 7.7 kernel is installed.

2. Reboot the host and verify that it boots into specified OL 7.7 kernel.

# uname -r4.14.35-1902.9.2.el7uek

3. Upgrade to the nvme-cli-1.8.1-3.el7 package.

# rpm -qa|grep nvme-clinvme-cli-1.8.1-3.el7.x86_64

4. Add the string below as a separate udev rule at /lib/udev/rules.d/71-nvme-iopolicy-netapp-ONTAP.rules. This enables round-robin load balancing for NVMe multipath.

# Enable round-robin for NetApp ONTAPACTION==”add”, SUBSYSTEM==”nvme-subsystem”, ATTR{model}==”NetApp ONTAP Controller”,ATTR{iopolicy}=”round-robin

5. On the OL 7.7 host, check the hostnqn string at /etc/nvme/hostnqn and verify that it matches thehostnqn string for the corresponding subsystem on the ONTAP array.




*> vserver nvme subsystem host show -vserver vs_nvme_10Vserver Subsystem Host NQN------- --------- -------------------------------------- -----------ol_157_nvme_ss_10_0nqn.2014-08.org.nvmexpress:uuid:75953f3b-77fe-4e03-bf3c-09d5a156fbcd

Note:

If the hostnqn strings do not match, you should use the vserver modify command to update thehostnqn string on your corresponding ONTAP array subsystem to match to hostnqn string from/etc/nvme/hostnqn on the host.

1. Reboot the host.





2. Copy and install the Broadcom outbox auto-connect scripts package.

# rpm -ivh nvmefc-connect-12.4.65.0-1.noarch.rpm

3. Reboot the host.

4. Verify that you are using the recommended Broadcom lpfc firmware, native inbox driver & outboxauto-connect package versions. For a list of supported versions, see the NetApp InteroperabilityMatrix.






# rpm -qa | grep nvmefcnvmefc-connect-12.4.65.0-1.noarch








Validating NVMe/FC








# nvme list-subsys/dev/nvme0n1Nvme-subsysf0 – NQN=nqn.1992-08.com.netapp:sn.341541339b9511e8a9b500a098c80f09:subsystem.ol_157_nvme_ss_10_0\+- nvme0 fc traddr=nn-0x202c00a098c80f09:pn-0x202d00a098c80f09 host_traddr=nn-0x20000090fae0ec61:pn-0x10000090fae0ec61 live optimized+- nvme1 fc traddr=nn-0x207300a098dfdd91:pn-0x207600a098dfdd91 host_traddr=nn-0x200000109b1c1204:pn-0x100000109b1c1204 live inaccessible+- nvme2 fc traddr=nn-0x207300a098dfdd91:pn-0x207500a098dfdd91 host_traddr=nn-0x200000109b1c1205:pn-0x100000109b1c1205 live optimized+- nvme3 fc traddr=nn-0x207300a098dfdd91:pn-0x207700a098dfdd91 host traddr=nn-0x200000109b1c1205:pn-0x100000109b1c1205 live inaccessible


# nvme netapp ontapdevices -o columnDevice Vserver Namespace Path NSID UUID Size------- -------- ------------------------- ------ ----- -----/dev/nvme0n1 vs_nvme_10 /vol/rhel_141_vol_10_0/ol_157_ns_10_0 155baf453-f629-4a18-9364-b6aee3f50dad 53.69GB

# nvme netapp ontapdevices -o json{ "ONTAPdevices" : [ { Device" : "/dev/nvme0n1", "Vserver" : "vs_nvme_10", "Namespace_Path" : "/vol/rhel_141_vol_10_0/ol_157_ns_10_0", "NSID" : 1, "UUID" : "55baf453-f629-4a18-9364-b6aee3f50dad", "Size" : "53.69GB", "LBA_Data_Size" : 4096, "Namespace_Size" : 13107200 }]










FC/iSCSI Host Configurations

RHEL

RHEL 8

Using Red Hat Enterprise Linux 8.2 with NetApp ONTAP

Installing the Linux Unified Host Utilities

The NetApp Linux Unified Host Utilities software package is available on the NetApp Support Site in a64-bit .rpm file.

Installing the Linux Unified Host Utilities is strongly recommended, but not mandatory. The utilities donot change any settings on your Linux host. The utilities improve management and assist NetAppcustomer support in gathering information about your configuration.

Before you begin

If you have a version of Linux Unified Host Utilities currently installed you should upgrade it or, youshould remove it and use the following steps to install the latest version.

1. Download the 64-bit Linux Unified Host Utilities software package from the NetApp Support Site toyour host.

2. Use the following command to install the software package:

rpm -ivh netapp_linux_unified_host_utilities-7-1.x86_64

SAN Toolkit

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

Example

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

https://mysupport.netapp.com/NOW/cgi-bin/software/?product=Host+Utilities+-+SAN&platform=Linux


# sanlun lun show allcontroller(7mode/E-Series)/ device host lunvserver(cDOT/FlashRay) lun-pathname filename adapter protocol size Product-------------------------------------------------------------------------data_vserver /vol/vol1/lun1 /dev/sdb host16 FCP 120.0g cDOTdata_vserver /vol/vol1/lun1 /dev/sdc host15 FCP 120.0g cDOTdata_vserver /vol/vol2/lun2 /dev/sdd host16 FCP 120.0g cDOTdata_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 NetAppInteroperability Matrix Tool to verify that your OS, HBA, HBA firmware and the HBA boot BIOS, andONTAP version are supported.

1. Map the SAN boot LUN to the host.

2. Verify multiple paths are available.

Remember, multiple paths will only be 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 the boot is successful.

Multipathing

For Red Hat Enterprise Linux (RHEL) 8.2 the /etc/multipath.conf file must exist, but you do not need tomake specific changes to the file. RHEL 8.2 is compiled with all settings required to recognize andcorrectly manage ONTAP LUNs.

You can use the multipath -ll command to verify the settings for your ONTAP LUNs.There should be two groups of paths with different priorities. The paths with the higher priorities areActive/Optimized, meaning they are serviced by the controller where the aggregate is located. Thepaths with the lower priorities are active but are non-optimized because they are served from adifferent controller. The non-optimized paths are only used when no optimized paths are available.

Example

The following example displays the correct output for an ONTAP LUN with two Active/Optimized pathsand two Active/non-Optimized paths:

https://mysupport.netapp.com/matrix/imt.jsp?components=96167;&solution=236&isHWU&src=IMT


# multipath -ll3600a098038303634722b4d59646c4436 dm-28 NETAPP,LUN C-Modesize=80G features='3 queue_if_no_path pg_init_retries 50' hwhandler='1 alua' wp=rw|-+- policy='service-time 0' prio=50 status=active| |- 16:0:6:35 sdwb 69:624 active ready running| |- 16:0:5:35 sdun 66:752 active ready running`-+- policy='service-time 0' prio=10 status=enabled|- 15:0:0:35 sdaj 66:48 active ready running|- 15:0:1:35 sdbx 68:176 active ready running

Note

Do not use an excessive number of paths to a single LUN. No more than 4 paths should be required.More than 8 paths might cause path issues during storage failures.

Recommended Settings

The RHEL 8.2 OS is compiled to recognize ONTAP LUNs and automatically set all configurationparameters correctly.The multipath.conf file must exist for the multipath daemon to start, but you can create an empty, zero-byte file using the command:touch /etc/multipath.confThe first time you create this file, you might need to enable and start the multipath services.

[root@jfs0 ~]#systemctl enable multipathd[root@jfs0 ~]# systemctl start multipathd

There is no requirement to add anything directly to multipath.conf, unless you have devices that youdo not want to be managed by multipath or you have existing settings that override defaults.You can add the following syntax to the multipath.conf file to exclude the unwanted devices.

Note

Replace the <DevId> with the WWID string of the device you want to exclude. Use the followingcommand to determine the WWID:

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

Example

In this example, sda is the local SCSI disk that we need to blacklist.

1. Run the following command to determine the WWID:

# /lib/udev/scsi_id -gud /dev/sda360030057024d0730239134810c0cb833

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

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

You should always check your /etc/multipath.conf file for legacy settings, especially in the defaultssection, that may be overriding default settings.The table below shows the critical multipathd parameters for ONTAP LUNs and the required values. If ahost is connected to LUNs from other vendors and any of these parameters are overridden, they willneed to be corrected by later stanzas in multipath.conf that apply specifically to ONTAP LUNs. If this isnot done, the ONTAP LUNs may not work as expected. These defaults should only be overridden inconsultation with NetApp and/or OS vendor 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 "2 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 "service-time 0"

polling_interval 5

prio "ontap"

product LUN.*

Parameter Setting

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 filedefines values for path_checker and no_path_retry that are not compatible with ONTAP LUNs. If theycannot be removed because of other SAN arrays still attached to the host, these parameters can becorrected 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 }}

Known Problems and Limitations

There are no known issues for RHEL 8.2.

Release Notes

ASM Mirroring

ASM mirroring might require changes to the Linux multipath settings to allow ASM to recognize aproblem and switch over to an alternate fail group. Most ASM configurations on ONTAP use externalredundancy, which means that data protection is provided by the external array and ASM does notmirror data. Some sites use ASM with normal redundancy to provide two-way mirroring, normallyacross different sites. See Oracle Databases on ONTAP for further information.


https://www.netapp.com/us/media/tr-3633.pdf




Before you begin





SAN Toolkit


Example



SAN Booting

Before you begin












Multipathing


You can use the multipath -ll command to verify the settings for your ONTAP LUNs.The following sections provide sample multipath output for a LUN mapped to ASA and non-ASApersonas.

All SAN Array Configuration

For All SAN Array (ASA) configuration there should be one group of paths with single priorities. All thepaths are Active/Optimized, meaning they are serviced by the controller and I/O is sent on all the activepaths.

Example

The following example displays the correct output for an ONTAP LUN with four Active/Optimizedpaths:

# multipath -ll3600a09803831347657244e527766394e dm-5 NETAPP,LUN C-Modesize=80G features='4 queue_if_no_path pg_init_retries 50 retain_attached_hw_handle'hwhandler='1 alua' wp=rw`-+- policy='service-time 0' prio=50 status=active |- 11:0:7:1 sdfi 130:64 active ready running |- 11:0:9:1 sdiy 8:288 active ready running |- 11:0:10:1 sdml 69:464 active ready running |- 11:0:11:1 sdpt 131:304 active ready running

Note


Non-ASA Configuration

For non-ASA configuration there should be two groups of paths with different priorities. The pathswith the higher priorities are Active/Optimized, meaning they are serviced by the controller where theaggregate is located. The paths with the lower priorities are active but are non-optimized because theyare served from a different controller. The non-optimized paths are only used when no optimizedpaths are available.

Example


# multipath -ll3600a098038303634722b4d59646c4436 dm-28 NETAPP,LUN C-Modesize=10G features='3 queue_if_no_path pg_init_retries 50' hwhandler='1 alua' wp=rw|-+- policy='service-time 0' prio=50 status=active| |- 16:0:6:35 sdwb 69:624 active ready running| |- 16:0:5:35 sdun 66:752 active ready running`-+- policy='service-time 0' prio=10 status=enabled |- 15:0:0:35 sdaj 66:48 active ready running |- 15:0:1:35 sdbx 68:176 active ready running

Note



The RHEL 8.1 OS is compiled to recognize ONTAP LUNs and automatically set all configurationparameters correctly for both ASA and non-ASA configuration.The multipath.conf file must exist for the multipath daemon to start, but you can create an empty, zero-byte file using the command:touch /etc/multipath.confThe first time you create this file, you might need to enable and start the multipath services.



Note

Replace the <DevId> with the WWID string of the device you want to exclude. Use the following

command to determine the WWID:


Example







Parameter Setting

detect_prio yes


failback immediate

fast_io_fail_tmo 5


Parameter Setting



no_path_retry queue

path_checker "tur"



polling_interval 5

prio "ontap"

product LUN.*


rr_weight "uniform"


vendor NETAPP

Example





NetApp Bug ID Title Description Bugzilla ID

1275843 Kernel disruption mightoccur on Red HatEnterprise Linux 8.1with QLogic QLE267216GB FC HBA duringstorage failoveroperation

Kernel disruption mightoccur during storagefailover operations onthe Red Hat EnterpriseLinux 8.1 kernel with aQLogic QLE2672 FibreChannel (FC) host busadapter (HBA). Thekernel disruption causesRed Hat EnterpriseLinux 8.1 to reboot,leading to applicationdisruption. If the kdumpmechanism is enabled,the kernel disruptiongenerates a vmcore filelocated in the/var/crash/directory. You can checkthe vmcore file todetermine the cause ofthe disruption.A storagefailover with the QLogicQLE2672 HBA eventaffects the"kmem_cache_alloc+131" module. You can locatethe event in the vmcorefile by finding thefollowing string: "[exception RIP:kmem_cache_alloc+131]"After the kerneldisruption, reboot theHost OS and recover theoperating system. Thenrestart the applications

1760819

https://mysupport.netapp.com/NOW/cgi-bin/bol?Type=Detail&Display=1275843

https://bugzilla.redhat.com/show_bug.cgi?id=1760819


1275838 Kernel disruptionoccurs on Red HatEnterprise Linux 8.1with QLogic QLE274232GB FC HBA duringstorage failoveroperations

Kernel disruptionoccurs during storagefailover operations onthe Red Hat EnterpriseLinux 8.1 kernel with aQLogic QLE2742 FibreChannel (FC) host busadapter (HBA). Thekernel disruption causesRed Hat EnterpriseLinux 8.1 to reboot,leading to applicationdisruption. If the kdumpmechanism is enabled,the kernel disruptiongenerates a vmcore filelocated in the/var/crash/directory. You can checkthe vmcore file todetermine the cause ofthe disruption. A storagefailover with the QLogicQLE2742 HBA eventaffects the"kmem_cache_alloc+131"module. You can locatethe event in the vmcorefile by finding thefollowing string: "[exception RIP:kmem_cache_alloc+131]"After the kerneldisruption, reboot theHost OS and recover theoperating system. Thenrestart the applications.

1744082




1266250 Login to multiple pathsfails during the Red HatEnterprise Linux 8.1installation on iSCSI SANLUN

You cannot login tomultiple paths duringthe Red Hat EnterpriseLinux 8.1 installation oniSCSI SAN LUNmultipath devices.Installation is notpossible on multipathiSCSI device and themultipath service is notenabled on the SAN bootdevice.

1758504

Release Notes

ASM Mirroring






Before you begin










SAN Toolkit


Example



SAN Booting

Before you begin








Multipathing







Example



Note




Example


# multipath -ll3600a098038303634722b4d59646c4436 dm-28 NETAPP,LUN C-Modesize=10G features='3 queue_if_no_path pg_init_retries 50' hwhandler='1 alua' wp=rw|-+- policy='service-time 0' prio=50 status=active| |- 16:0:6:35 sdwb 69:624 active ready running| |- 16:0:5:35 sdun 66:752 active ready running`-+- policy='service-time 0' prio=10 status=enabled |- 15:0:0:35 sdaj 66:48 active ready running |- 15:0:1:35 sdbx 68:176 active ready running

Note






Note



Example







Parameter Setting

detect_prio yes


failback immediate

fast_io_fail_tmo 5




no_path_retry queue

path_checker "tur"



polling_interval 5

prio "ontap"

product LUN.*

Parameter Setting


rr_weight "uniform"


vendor NETAPP

Example






1238719 Kernel disruption onRHEL8 with QLogicQLE2672 16GB FCduring storage failoveroperations

Kernel disruption mightoccur during storagefailover operations on aRed Hat EnterpriseLinux (RHEL) 8 kernelwith a QLogic QLE2672host bus adapter (HBA).The kernel disruptioncauses the operatingsystem to reboot. Thereboot causesapplication disruptionand generates thevmcore file under the/var/crash/directory ifkdump is configured.Use the vmcore file toidentify the cause of thefailure. In this case, thedisruption is in the“kmem_cache_alloc+160” module. It is logged inthe vmcore file with thefollowing string:"[exception RIP:kmem_cache_alloc+160]". Reboot the host OS torecover the operatingsystem and then restartthe application.

1710009

1226783 RHEL8 OS boots up to"emergency mode"when more than 204SCSI devices aremapped on all FibreChannel (FC) host busadapters (HBA)

If a host is mapped withmore than 204 SCSIdevices during anoperating systemrebootprocess, the RHEL8 OSfails to boot up to"normal mode" andenters "emergencymode". This results inmost of the host servicesbecoming unavailable.

1690356






1230882 Creating a partition onan iSCSI multipathdevice during theRHEL8 installation is notfeasible.

iSCSI SAN LUNmultipath devices arenot listed in diskselection during RHEL 8installation.Consequently, themultipath service is notenabled on the SAN bootdevice.

1709995

1235998 The "rescan-scsi-bus.sh-a" command does notscan more than 328devices

If a Red Hat EnterpriseLinux 8 host maps withmore than 328 SCSIdevices, the host OScommand "rescan-scsi-bus.sh -a" only scans 328devices. The host doesnot discover anyremaining mappeddevices.

1709995

1231087 Remote ports transit to ablocked state on RHEL8with Emulex LPe1600216GB FC during storagefailover operations

Remote ports transit to ablocked state on RHEL8with Emulex LPe1600216GB Fibre Channel (FC)during storage failoveroperations. When thestorage node returns toan optimal state, theLIFs also come up andthe remote port stateshould read "online".Occasionally, the remoteport state mightcontinue to read as"blocked” or "notpresent". This state canlead to a "failed faulty"path to LUNs at themultipath layer

1702005








1231098 Remote ports transit toblocked state on RHEL8with Emulex LPe3200232GB FC during storagefailover operations

Remote ports transit to ablocked state on RHEL8with Emulex LPe3200232GBFibre Channel (FC)during storage failoveroperations. When thestorage node returns toan optimal state, theLIFs also come up andthe remote port stateshould read "online".Occasionally, the remoteport state mightcontinue to read as"blocked” or "notpresent". This state canlead to a "failed faulty"path to LUNs at themultipath layer.

1705573

Release Notes

ASM Mirroring


RHEL 7



The NetApp Linux Unified Host Utilities software package is available on the NetApp Support Site in a32-bit and 64-bit .rpm file. If you do not know which file is right for your configuration, use the NetAppInteroperability Matrix Tool to verify which one you need.






https://mysupport.netapp.com/matrix/#welcome


Before you begin


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



SAN Toolkit


Example



SAN Booting

Before you begin












Multipathing





Example



Note




Example


# multipath -ll3600a09803831347657244e527766394e dm-5 NETAPP,LUN C-Modesize=80G features='4 queue_if_no_path pg_init_retries 50 retain_attached_hw_handle'hwhandler='1 alua' wp=rw|-+- policy='service-time 0' prio=50 status=active| |- 11:0:1:0 sdj 8:144 active ready running| |- 11:0:2:0 sdr 65:16 active ready running`-+- policy='service-time 0' prio=10 status=enabled|- 11:0:0:0 sdb 8:i6 active ready running|- 12:0:0:0 sdz 65:144 active ready running

Note






Note



Example







Parameter Setting

detect_prio yes


failback immediate

fast_io_fail_tmo 5

features "3 queue_if_no_path pg_init_retries 50"


Parameter Setting


no_path_retry queue

path_checker "tur"



polling_interval 5

prio "ontap"

product LUN.*


rr_weight "uniform"


vendor NETAPP

Example






Release Notes

ASM Mirroring






Before you begin





SAN Toolkit


Example









SAN Booting

Before you begin








Multipathing





Example





Note




Example


# multipath -ll3600a09803831347657244e527766394e dm-5 NETAPP,LUN C-Modesize=80G features='4 queue_if_no_path pg_init_retries 50 retain_attached_hw_handle’hwhandler='1 alua' wp=rw|-+- policy='service-time 0' prio=50 status=active| |- 11:0:1:0 sdj 8:144 active ready running| |- 11:0:2:0 sdr 65:16 active ready running`-+- policy='service-time 0' prio=10 status=enabled |- 11:0:0:0 sdb 8:i6 active ready running |- 12:0:0:0 sdz 65:144 active ready running

Note



The RHEL 7.7 OS is compiled to recognize ONTAP LUNs and automatically set all configuration

parameters correctly.The multipath.conf file must exist for the multipath daemon to start, but you can create an empty, zero-byte file using the command:touch /etc/multipath.confThe first time you create this file, you might need to enable and start the multipath services.



Note



Example






You should always check your /etc/multipath.conf file for legacy settings, especially in the defaults

section, that may be overriding default settings.The table below shows the critical multipathd parameters for ONTAP LUNs and the required values. If ahost is connected to LUNs from other vendors and any of these parameters are overridden, they willneed to be corrected by later stanzas in multipath.conf that apply specifically to ONTAP LUNs. If this isnot done, the ONTAP LUNs may not work as expected. These defaults should only be overridden inconsultation with NetApp and/or OS vendor and only when the impact is fully understood.

Parameter Setting

detect_prio yes


failback immediate

fast_io_fail_tmo 5




no_path_retry queue

path_checker "tur"



polling_interval 5

prio "ontap"

product LUN.*


rr_weight "uniform"


vendor NETAPP

Example






1258856 Remote ports transit to ablocked state onRHEL7U7 with EmulexLPe16002 16GB FCduring storage failoveroperations

Remote ports mighttransit to a blocked stateon a RHEL 7.7 host witha LPe16002 16GB FCadapter during storagefailover operations.When the storage nodereturns to an optimalstate, the LIFs also comeup and the remote portstate should read"online". Occasionally,the remote port statemight continue to readas "blocked” or "notpresent". This state canlead to a "failed faulty"path to LUNs at themultipath layer.

1743667




1261474 Remote ports transit toblocked state onRHEL7U7 with EmulexLPe32002 32GB FC

Remote ports mighttransit to a blocked stateon a RHEL 7.7 host withLPe32002 32GB FCadapter during storagefailover operations.When the storage nodereturns to an optimalstate, the LIFs also comeup and the remote portstate should read"online". Occasionally,the remote port statemight continue to readas "blocked” or "notpresent". This state canlead to a "failed faulty"path to LUNs at themultipath layer.

1745995

Release Notes

ASM Mirroring






Before you begin

If you have a version of Linux Unified Host Utilities currently installed you should upgrade it or, you







should remove it and use the following steps to install the latest version.




SAN Toolkit


Example



SAN Booting

Before you begin





Example







Note




Example



Note






Note



Example







Parameter Setting

detect_prio yes


failback immediate

fast_io_fail_tmo 5




no_path_retry queue

path_checker "tur"



polling_interval 5

prio "ontap"

product LUN.*


rr_weight "uniform"


vendor NETAPP

Example






1186754 Remote ports status onRHEL7U6 with QLogicQLE2742 host might bein blocked during hostdiscovery

During host discovery,FC remote port status onRHEL7U6 host with aQLogic QLE2742 adaptermight enter a blockedstate. These blockedremote ports mightresult in the paths toLUNs becomingunavailable. Duringstorage failover, thepath redundancy mightbe reduced and result inI/O outage. You cancheck the remote portstatus by entering thefollowing command:#cat/sys/class/fc_remote_ports/rport-*/port_state

1628039




1190698 Remote port status onRHEL7U6 with QLogicQLE2672 host might bein blocked duringstorage failoveroperations

FC remote ports mightbe blocked on Red HatEnterprise Linux (RHEL)7U6 with the QLogicQLE2672 host duringstorage failoveroperations. Because thelogical interfaces godown when a storagenode is down, theremote ports set thestorage node status toblocked. When thestorage node returns toits optimal state, thelogical interfaces alsocome up and the remoteports should be online.However, the remoteportsmight still beblocked. This blockedstate registers as failedfaulty to LUNS at themultipath layer. You canverify the remote portsstate with the followingcommand:# cat/sys/class/fc_remote_ports/rport-*/port_state

1643459

Release Notes

ASM Mirroring









Before you begin





SAN Toolkit


Example



SAN Booting

Before you begin















Multipathing





Example



Note




Example



Note






Note



Example







Parameter Setting

detect_prio yes


failback immediate

fast_io_fail_tmo 5

Parameter Setting




no_path_retry queue

path_checker "tur"



polling_interval 5

prio "ontap"

product LUN.*


rr_weight "uniform"


vendor NETAPP

Example






1139053 Kernel disruptionoccurs on RHEL7.5 withQLogic QLE2672 16GBFC during storagefailover operations

During storage failoveroperations on theRHEL7U5 kernel withQLogic QLE2672 16GBfibre channel host busadapter, the kerneldisruption occurs due toa panic in the kernel.The kernel panic causesRHEL 7.5 to reboot,which leads to anapplication disruption.The kernel panicgenerates the vmcorefile under the/var/crash/directory ifkdump is configured.The vmcore file is usedto understand the causeof the failure. In thiscase, the panic wasobserved in the“get_next_timer_interrupt+440” module which islogged in the vmcore filewith the followingstring: " [exception RIP:get_next_timer_interrupt+440]" After the kerneldisruption, you canrecover the operatingsystem by rebooting thehost operating systemand restarting theapplication as required.

1542564




1138536 Kernel disruptionoccurs on RHEL7U5with QLogic QLE274232GB FC during storagefailover operations

During storage failoveroperations on the RedHat Enterprise Linux(RHEL) RHEL7U5 kernelwith QLogic QLE2742HBA, kernel disruptionoccurs due to a panic inthe kernel. The kernelpanic leads to a rebootof the operating system,causing an applicationdisruption. The kernelpanic generates thevmcore file under the/var/crash/ directory ifkdump is configured.When the kernel panics,you can use the vmcorefile to investigate thereason for the failure.The following exampleshows a panic in thebget_next_timer_interrupt+440b module. Thepanic is logged in thevmcore file with thefollowing string: "[exception RIP:get_next_timer_interrupt+440]" You can recoverthe operating system byrebooting the host OSand restarting theapplication as required.

1541972




1148090 Kernel disruptionoccurs on RHEL 7.5 withQLogic QLE2742 32GBFC HBA during storagefailover operations

During storage failoveroperations on the RedHat Enterprise Linux(RHEL) 7.5 kernel with aQLogic QLE2742 FibreChannel (FC) host busadapter (HBA), a kerneldisruption occurs due toa panic in the kernel.The kernel panic causesRHEL 7.5 to reboot,which leads to anapplication disruption.If the kdumpmechanism is enabled,the kernel panicgenerates a vmcore filelocated in the /var/crash/directory. You cananalyze the vmcore fileto determine the causeof the panic. In thisinstance, when storagefailover with the QLogicQLE2742 HBA eventoccurs, the"native_queued_spin_lock_slowpath+464"module is affected. Youcan locate the event inthe vmcore file byfinding the followingstring: " [exception RIP:native_queued_spin_lock_slowpath+464]" Afterthe kernel disruption,you can reboot the HostOS and recover theoperating system, andthen you can restart theapplications as required.

1559050




1146898 Kernel disruptionoccurs on RHEL 7.5 withEmulex HBAs duringstorage failoveroperations

During storage failoveroperations on a Red HatEnterprise Linux (RHEL)7.5 system with EmulexLPe32002-M2 32-GB FChost bus adapters(HBAs), a disruption inthe kernel occurs. Thekernel disruption causesa reboot of the operatingsystem, which in turncauses an applicationdisruption. If youconfigure kdump, thekernel disruptiongenerates the vmcorefile under the /var/crash/directory. You can usethe vmcore file todetermine the cause ofthe failure. In thefollowing example, youcan see the disruption inthe"lpfc_hba_clean_txcmplq+368" module. Thisdisruption is logged inthe vmcore file with thefollowing string: "[exception RIP:lpfc_hba_clean_txcmplq+368]" After the kerneldisruption, reboot thehost OS to recover theoperating system.Restart the applicationas required.

1554777

Release Notes

ASM Mirroring

ASM mirroring might require changes to the Linux multipath settings to allow ASM to recognize a



problem and switch over to an alternate fail group. Most ASM configurations on ONTAP use externalredundancy, which means that data protection is provided by the external array and ASM does notmirror data. Some sites use ASM with normal redundancy to provide two-way mirroring, normallyacross different sites. See Oracle Databases on ONTAP for further information.





Before you begin





SAN Toolkit


Example









SAN Booting

Before you begin








Multipathing





Example





Note




Example



Note







Note



Example








Parameter Setting

detect_prio yes


failback immediate

fast_io_fail_tmo 5




no_path_retry queue

path_checker "tur"



polling_interval 5

prio "ontap"

product LUN.*


rr_weight "uniform"


vendor NETAPP

Example






Release Notes

ASM Mirroring






Before you begin











SAN Toolkit


Example



SAN Booting

Before you begin








Multipathing







Example



Note




Example



Note






Note



Example







Parameter Setting

detect_prio yes


failback immediate

fast_io_fail_tmo 5




no_path_retry queue

path_checker "tur"



polling_interval 5

prio "ontap"

Parameter Setting

product LUN.*


rr_weight "uniform"


vendor NETAPP

Example






Release Notes

ASM Mirroring







Before you begin





SAN Toolkit


Example



SAN Booting

Before you begin

If you decide to use SAN booting, it must be supported by your configuration. You can use the NetApp







Interoperability Matrix Tool to verify that your OS, HBA, HBA firmware and the HBA boot BIOS, andONTAP version are supported.







Multipathing





Example



Note

Do not use an excessive number of paths to a single LUN. No more than 4 paths should be required.


More than 8 paths might cause path issues during storage failures.



Example



Note






Note



Example







Parameter Setting

detect_prio yes


failback immediate

Parameter Setting

fast_io_fail_tmo 5




no_path_retry queue

path_checker "tur"



polling_interval 5

prio "ontap"

product LUN.*


rr_weight "uniform"


vendor NETAPP

Example






Release Notes

ASM Mirroring






Before you begin





SAN Toolkit


Example









SAN Booting

Before you begin








Multipathing





Example





Note




Example



Note







Note



Example








Parameter Setting

detect_prio yes


failback immediate

fast_io_fail_tmo 5




no_path_retry queue

path_checker "tur"



polling_interval 5

prio "ontap"

product LUN.*


rr_weight "uniform"


vendor NETAPP

Example






799323 Emulex FCoE(OCe10102-FX-D) hosthang or path failuresobserved during I/Owith storage failoveroperations

You might observe ahost hang or pathfailures on Emulex 10GFCoE host (OCe10102-FX-D) during I/O withstorage failoveroperations. In suchscenarios, you might seethe following message:"driver’s buffer pool isempty, IO busied andSCSI Layer I/O AbortRequest Status"

1061755




836875 IP addresses are notalways assigned duringthe boot of a RHEL 7.0OS installed on an iSCSImultipath’d LUN

When you install theroot(/) on a iSCSImultipath’d LUN, the IPaddress for the Ethernetinterfaces are specifiedin the kernel commandline so that the IPaddresses are assignedbefore the iSCSI servicestarts. However, dracutcannot assign IPaddresses to all theEthernet ports duringthe boot, before theiSCSI service starts. Thiscauses the iSCSI login tofail on interfaceswithout IP addresses.You will see the iSCSIservice attempt to loginnumerous times, whichwill cause a delay in theOS boot time.

1114966

Release Notes

ASM Mirroring





Installing the Linux Unified Host Utilities is strongly recommended, but not mandatory. The utilities donot change any settings on your Linux host. The utilities improve management and assist NetApp







customer support in gathering information about your configuration.

Before you begin





SAN Toolkit


Example



SAN Booting

Before you begin












Multipathing





Example



Note




Example



Note






Note



Example







Parameter Setting

detect_prio yes


failback immediate

fast_io_fail_tmo 5



Parameter Setting


no_path_retry queue

path_checker "tur"



polling_interval 5

prio "ontap"

product LUN.*


rr_weight "uniform"


vendor NETAPP

Example






844417 Emulex 16G FC(LPe16002B-M6) hostcrashes during I/O withstorage failoveroperations

You might observe a 16GFC Emulex (LPe16002B-M6) host crash duringI/O with storage failoveroperations.

1131393



1079735



1067895

820163 QLogic host hang orpath failures observedduring I/O with storagefailover operations

You might observe ahost hang or pathfailures on QLogic hostduring I/O with storagefailover operations. Insuch scenarios, youmight see the followingmessage: "Mailbox cmdtimeout occurred,cmd=0x54, mb[0]=0x54and Firmware dumpsaved to temp buffer"messages which leads tohost hung/path failure.

1090378










799323 Emulex FCoE(OCe10102-FX-D) hosthang or path failuresobserved during I/Owith storage failoveroperations

You might observe ahost hang or pathfailures on Emulex 10GFCoE host (OCe10102-FX-D) during I/O withstorage failoveroperations. In suchscenarios, you might seethe following message:"driver’s buffer pool isempty, IO busied andSCSI Layer I/O AbortRequest Status"messages which leads tohost hung/path failures.

1061755

849212 Emulex 16G FC(LPe16002B-M6) hosthang or path failuresare observed during I/Owith storage failoveroperations

You might observe ahost hang or pathfailures on Emulex 16GFC (LPe16002B-M6) hostduring I/O with storagefailover operations. Insuch scenarios, youmight see the followingmessage: "RSCN timeoutData and iotag x1301 isout of range: max iotag"messages which leads tohost hung/path failures.

1109274






836800 Anaconda displays aniSCSI login failuremessage although loginsare successful duringRHEL 7.0 OS installation

When you install theroot(/) on a iSCSImultipath’d LUN, the IPaddress for the Ethernetinterfaces are specifiedin the kernel commandline so that the IPaddresses are assignedbefore the iSCSI servicestarts. However, dracutcannot assign IPaddresses to all theEthernet ports duringthe boot, before theiSCSI service starts. Thiscauses the iSCSI login tofail on interfaceswithout IP addresses.You will see the iSCSIservice attempt to loginnumerous times, whichwill cause a delay in theOS boot time.

1114966




836875 IP addresses are notalways assigned duringthe boot of a RHEL 7.0OS installed on an iSCSImultipath’d LUN

When you are installingRHEL 7.0, the anacondainstallation screendisplays that iSCSI loginto multiple target IPshave failed though theiSCSI logins aresuccessful. Anacondadisplays following errormessage: “Node LoginFailed” You will observethis error only whenyou select multipletarget IPs for iSCSI login.You can continue the OSinstallation by clickingthe "ok" button. This bugdoes not hamper eitherthe iSCSI or the RHEL7.0 OS installation.

1114820

836657 Anaconda does not addbootdev argument inkernel cmd line to set IPaddress for RHEL 7.0 OSinstalled on iSCSImultipath’d LUN

Anaconda does not adda bootdev argument inthe kernel commandline where you set theIPv4 address during theRHEL 7.0 OS installationon an iSCSI multipath’dLUN. This preventsassigning of IPaddresses to any of theEthernet interfaces thatwere configured toestablish iSCSI sessionswith the storagesubsystem during theRHEL 7.0 boot. SinceiSCSI sessions are notestablished, the rootLUN is not discoveredwhen the OS boots andhence the OS boot fails.

1114464





Release Notes

ASM Mirroring


RHEL 6





Before you begin





SAN Toolkit


Example









SAN Booting

Before you begin








Multipathing

For Red Hat Enterprise Linux (RHEL) 6.10 the /etc/multipath.conf file must exist, but you do not need tomake specific changes to the file. RHEL 6.10 is compiled with all settings required to recognize andcorrectly manage ONTAP LUNs.To Enable ALUA Handler, perform the following 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-8rd_LVM_LV=vg_ibmx355021082/lv_swap rd_NO_MD SYSFONT=latarcyrheb-sun16 crashkernel=autoKEYBOARDTYPE=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 -rOrThe command: dracut -f

4. Reboot the host.

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




Example



Note




Example


# multipath -ll3600a0980383034466b2b4a3775474859 dm-3 NETAPP,LUN C-Modesize=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






Note



Example







Parameter Setting

detect_prio yes


failback immediate

fast_io_fail_tmo 5



Parameter Setting


no_path_retry queue

path_checker "tur"


path_selector "round-robin 0"

polling_interval 5

prio "ontap"

product LUN.*


rr_weight "uniform"


vendor NETAPP

Example






Release Notes

ASM Mirroring






Before you begin





SAN Toolkit


Example









SAN Booting

Before you begin








Multipathing




Example





4. Reboot the host.





Example



Note




Example



Note






Note



Example







Parameter Setting

detect_prio yes


failback immediate

fast_io_fail_tmo 5



Parameter Setting


no_path_retry queue

path_checker "tur"



polling_interval 5

prio "ontap"

product LUN.*


rr_weight "uniform"


vendor NETAPP

Example






1067272 Remote port status onEMULEX LPe32002 hostmight be in 'Blocked'state during storagefailover operations

During storage failoveroperations, certainremote port status onRHEL 6.9 host withLPe32002 adapter mightget into 'Blocked' state.Because the logicalinterfaces go downwhen a storage node isdown, the remote portsets the storage nodestatus to "Blocked" state.However, when thestorage node comesback to optimal state,the logical interfacesalso comes up and theremote port state isexpected to be 'Online'.But, on certain occasionthe remote portcontinues to be in'Blocked' state. This statemanifests as 'failedfaulty' to LUNS atmultipath layer.

427496




1076584 Firmware dumps occuron Red Hat EnterpriseLinux 6.9 QLogicQE8362 HBA duringstorage failoveroperations

Firmware dumps canoccur during storagefailover operations onRed Hat EnterpriseLinux (RHEL) 6.9 hostswith QLogic QLE8362host bus adapters (HBA),firmware dumps areobserved occasionally.The firmware dumpsmight manifest as an I/Ooutage on the host thatcan last as long as 1200seconds. After theadapter completesdumping the firmwarecores, the I/O operationresumes normally. Nofurther recoveryprocedure is requiredon the host. To indicatethe firmware dump, thefollowing message isdisplayed in /var/log/message file: kernel:qla2xxx [0000:0c:00.3]-d001:3: Firmware dumpsaved to temp buffer(3/ffffc90018b01000),dump status flags (0x3f)

1438711

Release Notes

ASM Mirroring









Before you begin





SAN Toolkit


Example



SAN Booting

Before you begin















Multipathing




Example



4. Reboot the host.






Example



Note




Example



Note






Note



Example







Parameter Setting

detect_prio yes


failback immediate

fast_io_fail_tmo 5




no_path_retry queue

path_checker "tur"



polling_interval 5

prio "ontap"

Parameter Setting

product LUN.*


rr_weight "uniform"


vendor NETAPP

Example






Release Notes

ASM Mirroring







Before you begin





SAN Toolkit


Example



SAN Booting

Before you begin















Multipathing




Example



4. Reboot the host.






Example



Note




Example



Note






Note



Example







Parameter Setting

detect_prio yes


failback immediate

fast_io_fail_tmo 5




no_path_retry queue

path_checker "tur"



polling_interval 5

prio "ontap"

Parameter Setting

product LUN.*


rr_weight "uniform"


vendor NETAPP

Example






Release Notes

ASM Mirroring







Before you begin





SAN Toolkit


Example



SAN Booting

Before you begin















Multipathing




Example



4. Reboot the host.






Example



Note




Example



Note






Note



Example







Parameter Setting

detect_prio yes


failback immediate

fast_io_fail_tmo 5




no_path_retry queue

path_checker "tur"



polling_interval 5

prio "ontap"

Parameter Setting

product LUN.*


rr_weight "uniform"


vendor NETAPP

Example






863878 Kernel crash occurswith RHEL 6U6 hostduring storage failures

You might observekernel crash on RHEL6U6 host duringstorage/fabric.

1158363

1076584 IO stall up to 300 secseen with QLogic 16G FC(QLE2672) host duringstorage failures in RHEL6U4

You might observe an IOstall up to 300 sec onQLogic 16G FC(QLE2672) host duringstorage/fabric failures.

1135962






795684 RHEL6 U5 multipathdincorrectly groupmultipath maps duringMoD and storagefailover fault operations

You might observe anincorrect path groupingon LUNs during LUNmove on demandoperation along withstorage faults. DuringLUN move operationmultipath pathpriorities will changeand multipath is unableto reloads the devicetable due to devicefailure caused bystorage fault. This leadsto incorrect pathgrouping.

1151020

Release Notes

ASM Mirroring






Before you begin


1. Download the 32-bit or 64-bit Linux Unified Host Utilities software package from the NetApp








Support Site Site to your host.



SAN Toolkit


Example



SAN Booting

Before you begin








Multipathing

For Red Hat Enterprise Linux (RHEL) 6.5 the /etc/multipath.conf file must exist, but you do not need tomake specific changes to the file. RHEL 6.5 is compiled with all settings required to recognize and




correctly manage ONTAP LUNs.To Enable ALUA Handler, perform the following steps:



Example



4. Reboot the host.





Example



Note




Example



Note






Note



Example







Parameter Setting

detect_prio yes


failback immediate

fast_io_fail_tmo 5




no_path_retry queue

path_checker "tur"



polling_interval 5

prio "ontap"

product LUN.*


rr_weight "uniform"


vendor NETAPP

Example






760515 Path failures or hosthangs were observed inRHEL 6.5 8G Qlogic FCSAN host during storagefailover operations

Path failures or hosthangs were observed inRHEL 6.5 8G Qlogic FCSAN host during storagefailover operations.

1033136

758271 bnx2 firmware fails toload when booting withcustom initrd (dracut -f)

Broadcom NetXtreme IIGigabit controller portswill not ping due tobnx2 firmware fails toload during boot withcustom initrd.

1007463

799394 RHEL 6U5: Emulex 16GFC (LPe16002B-M6) hostcrash is seen during I/Owith storage failoveroperations

16G FC Emulex(LPe16002B-M6) hostcrash is seen during I/Owith storage failoveroperations.

1063699








786571 QLogic FCoE hosthangs/path failuresobserved in RHEL 6.5during I/O with storagefailover operations

QLogic FCoE (QLE8242)host hangs/path failuresare observed in RHEL6.5 during I/O withstorage failoveroperations. In suchscenarios, you might seethe following message:"Mailbox cmd timeoutoccurred, cmd=0x54,mb[0]=0x54. SchedulingISP abort" messageswhich leads to hosthung/path failures.

1068619

801580 QLogic 16G FC hosthangs or path failuresobserved in RHEL 6.5during I/O with storagefailover operations

The I/O delays of morethan 600 seconds areobserved with QLogic16G FC host (QLE2672)during storage failoveroperations. In suchscenarios, the followingmessage is displayed:"Failed mbx[0]=54,mb[1]=0, mb[2]=76b9,mb[3]=5200, cmd=54"

1068622

Release Notes

ASM Mirroring














Before you begin





SAN Toolkit


Example



SAN Booting

Before you begin












Multipathing




Example



4. Reboot the host.





Example



Note




Example



Note






Note



Example







Parameter Setting

detect_prio yes


failback immediate

fast_io_fail_tmo 5




no_path_retry queue

path_checker "tur"



polling_interval 5

prio "ontap"

product LUN.*


rr_weight "uniform"


vendor NETAPP

Example


673009 Creating ext4 file systemon LV striped across 15or more discard-enabled, thinlyprovisioned multipathdevices triggers "requestbotched" kernel errors

"Request blotched"kernel errors have beenseen when usersattempt to create anext4 file system ondiscard-enabled, thinlyprovisioned multipathdevices. As a result,creating the ext4 filesystem might takelonger to complete andoccasional disruptionoccurs. This issue hasoccurred only whenusers attempt to createthe ext4 file system on aLV striped across 15 ormore discard-enabledmultipath devices onsystems running RedHat Enterprise Linux 6.xand Data ONTAP 8.1.3and later operating in 7-Mode. The issuehappens because thekernel erroneouslyattempts to mergediscard requests, whichis not supported on RedHat Enterprise Linux 6.xat this time. When thisissue occurs, multipleinstances of thefollowing message arewritten to syslog(/var/log/messages):kernel: blk: requestbotched. As a result, filesystem creation mighttake longer time tocomplete than expected.

907844



Release Notes

ASM Mirroring


SUSE

SUSE 15

Using SUSE Linux Enterprise Server 15 with NetApp ONTAP




Before you begin





SAN Toolkit


Example









SAN Booting

Before you begin








Multipathing

For SUSE Linux Enterprise Server 15 the /etc/multipath.conf file must exist, but you do not need tomake specific changes to the file. SUSE Linux Enterprise Server 15 is compiled with all settingsrequired to recognize and correctly manage ONTAP LUNs.




Example





Note




Example


# multipath -ll3600a09803831347657244e527766394e dm-5 NETAPP,LUN C-Modesize=80G features='3 queue_if_no_path pg_init_retries 50' hwhandler='1 alua' wp=rw|-+- policy='service-time 0' prio=50 status=enabled| |- 11:0:1:0 sdj 8:144 active ready running| |- 11:0:2:0 sdr 65:16 active ready running`-+- policy='service-time 0' prio=10 status=enabled |- 11:0:0:0 sdb 8:i6 active ready running |- 12:0:0:0 sdz 65:144 active ready running

Note



SUSE Linux Enterprise Server 15 OS is compiled to recognize ONTAP LUNs and automatically set all

configuration parameters correctly.The multipath.conf file must exist for the multipath daemon to start, but you can create an empty, zero-byte file using the command:touch /etc/multipath.confThe first time you create this file, you might need to enable and start the multipath services.



Note



Example








Parameter Setting

detect_prio yes


failback immediate

fast_io_fail_tmo 5




no_path_retry queue

path_checker "tur"



polling_interval 5

prio "ontap"

product LUN.*


rr_weight "uniform"


vendor NETAPP

Example






1154309 SLES 15 host with morethan 20 mapped LUNsmight go intomaintenance mode aftera reboot

SLES 15 host with morethan 20 mapped LUNsmight go intomaintenance mode aftera reboot. Themaintenance modebecomes single usermode following themessage:Give root password formaintenance (or pressControl-D to continue)

1104173

Release Notes

ASM Mirroring


Using SUSE Linux Enterprise Server 15 SP1 with NetApp ONTAP


The NetApp Linux Unified Host Utilities software package is available on the NetApp Support Site in a


https://bugzilla.suse.com/show_bug.cgi?id=1104173



32-bit and 64-bit .rpm file. If you do not know which file is right for your configuration, use the NetAppInteroperability Matrix Tool to verify which one you need.


Before you begin





SAN Toolkit


Example



SAN Booting

Before you begin














Multipathing

For SUSE Linux Enterprise Server 15 SP1 the /etc/multipath.conf file must exist, but you do not need tomake specific changes to the file. SUSE Linux Enterprise Server 15 SP1 is compiled with all settingsrequired to recognize and correctly manage ONTAP LUNs.




Example



Note



For non-ASA configuration there should be two groups of paths with different priorities. The paths

with the higher priorities are Active/Optimized, meaning they are serviced by the controller where theaggregate is located. The paths with the lower priorities are active but are non-optimized because theyare served from a different controller. The non-optimized paths are only used when no optimizedpaths are available.

Example


# multipath -ll3600a09803831347657244e527766394e dm-5 NETAPP,LUN C-Modesize=80G features='3 queue_if_no_path pg_init_retries 50' hwhandler='1 alua' wp=rw|-+- policy='service-time 0' prio=50 status=active| |- 11:0:1:0 sdj 8:144 active ready running| |- 11:0:2:0 sdr 65:16 active ready running`-+- policy='service-time 0' prio=10 status=enabled |- 11:0:0:0 sdb 8:i6 active ready running |- 12:0:0:0 sdz 65:144 active ready running

Note



SUSE Linux Enterprise Server 15 SP1 OS is compiled to recognize ONTAP LUNs and automatically setall configuration parameters correctly.The multipath.conf file must exist for the multipath daemon to start, but you can create an empty, zero-byte file using the command:touch /etc/multipath.confThe first time you create this file, you might need to enable and start the multipath services.



Note



Example







Parameter Setting

detect_prio yes


failback immediate

fast_io_fail_tmo 5



Parameter Setting


no_path_retry queue

path_checker "tur"



polling_interval 5

prio "ontap"

product LUN.*


rr_weight "uniform"


vendor NETAPP

Example






1246622 Remote portstransit to a blockedstate on SLES15SP1with EmulexLPe12002 8GB FCduring storagefailover operations.

Remote portstransit to a blockedstate on SLES15SP1with EmulexLPe12002 8GBFibre Channel (FC)during storagefailover operations.When the storagenode returns to anoptimal state, theLIFs also come upand the remoteport state shouldread "online."Occasionally, theremote port statemight continue toread as "blocked”or "not present."This state can leadto a "failed faulty"path to LUNs at themultipath layer aswell as an I/Ooutage for thoseLUNs. You cancheck theremoteport’sdetails against thefollowing samplecommands:

----cat/sys/class/fc_host/host*/device/rport*/fc_remote_ports/rport*/port_name

cat/sys/class/fc_host/host*/device/rport*/fc_remote_ports/rport*/port_state----

1139137



Release Notes

ASM Mirroring


SUSE 12





Before you begin





SAN Toolkit


Example









SAN Booting

Before you begin








Multipathing





Example





Note




Example


#multipath -ll3600a09803831347657244e527766394e dm-5 NETAPP,LUN C-Modesize=80G features='3 queue_if_no_path pg_init_retries 50' hwhandler='1 alua' wp=rw|-+- policy='service-time 0' prio=50 status=active| |- 11:0:1:0 sdj 8:144 active ready running| |- 11:0:2:0 sdr 65:16 active ready running`-+- policy='service-time 0' prio=10 status=enabled|- 11:0:0:0 sdb 8:i6 active ready running|- 12:0:0:0 sdz 65:144 active ready running

Note



SUSE Linux Enterprise Server 12 SP5 OS is compiled to recognize ONTAP LUNs and automatically set

all configuration parameters correctly.The multipath.conf file must exist for the multipath daemon to start, but you can create an empty, zero-byte file using the command:touch /etc/multipath.confThe first time you create this file, you might need to enable and start the multipath services.



Note



Example








Parameter Setting

detect_prio yes


failback immediate

fast_io_fail_tmo 5




no_path_retry queue

path_checker "tur"



polling_interval 5

prio "ontap"

product LUN.*


rr_weight "uniform"


vendor NETAPP

Example


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



1284293 Kernel disruptionoccurs on SLES12 SP5with QLogic QLE25628GB FC HBA duringstorage failoveroperations

Kernel disruptionoccurs during storagefailover operations onthe SLES12 SP5 kernelwith a QLogic QLE2562Fibre Channel (FC) hostbus adapter (HBA). Thekernel disruption causesSLES12 SP5 to reboot,leading to applicationdisruption. If the kdumpmechanism is enabled,the kernel disruptiongenerates a vmcore filelocated in the /var/crash/directory. Check thevmcore file to determinethe cause of thedisruption. A storagefailover with a QLogicQLE2562 HBA eventaffects the"THREAD_INFO:ffff8aedf723c2c0"module. Locate thisevent in the vmcore fileby finding the followingstring: " [THREAD_INFO:ffff8aedf723c2c0]".After the kerneldisruption, reboot thehost OS to enable it torecover. Then restartthe applications.

1157966

Release Notes

ASM Mirroring

ASM mirroring might require changes to the Linux multipath settings to allow ASM to recognize aproblem and switch over to an alternate fail group. Most ASM configurations on ONTAP use externalredundancy, which means that data protection is provided by the external array and ASM does notmirror data. Some sites use ASM with normal redundancy to provide two-way mirroring, normally


http://bugzilla.suse.com/show_bug.cgi?id=1157966

across different sites. See Oracle Databases on ONTAP for further information.





Before you begin





SAN Toolkit


Example









SAN Booting

Before you begin








Multipathing





Example





Note




Example


#multipath -ll3600a09803831347657244e527766394e dm-5 NETAPP,LUN C-Modesize=80G features='3 queue_if_no_path pg_init_retries 50' hwhandler='1 alua' wp=rw|-+- policy='service-time 0' prio=50 status=active| |- 11:0:1:0 sdj 8:144 active ready running| |- 11:0:2:0 sdr 65:16 active ready running`-+- policy='service-time 0' prio=10 status=enabled|- 11:0:0:0 sdb 8:i6 active ready running|- 12:0:0:0 sdz 65:144 active ready running

Note



SUSE Linux Enterprise Server 12 SP4 OS is compiled to recognize ONTAP LUNs and automatically set

all configuration parameters correctly.The multipath.conf file must exist for the multipath daemon to start, but you can create an empty, zero-byte file using the command:touch /etc/multipath.confThe first time you create this file, you might need to enable and start the multipath services.



Note



Example








Parameter Setting

detect_prio yes


failback immediate

fast_io_fail_tmo 5




no_path_retry queue

path_checker "tur"



polling_interval 5

prio "ontap"

product LUN.*


rr_weight "uniform"


vendor NETAPP

Example




There are no known issues for SUSE Linux Enterprise Server 12 SP4.

Release Notes

ASM Mirroring






Before you begin











SAN Toolkit


Example



SAN Booting

Before you begin








Multipathing


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



The following sections provide sample multipath output for a LUN mapped to ASA and non-ASApersonas.



Example



Note




Example


# multipath -ll3600a09803831347657244e527766394e dm-5 NETAPP,LUN C-Modesize=80G features='4 queue_if_no_path pg_init_retries 50 retain_attached_hw_handler'hwhandler='1 alua' wp=rw|-+- policy='service-time 0' prio=50 status=active| |- 11:0:1:0 sdj 8:144 active ready running| |- 11:0:2:0 sdr 65:16 active ready running`-+- policy='service-time 0' prio=10 status=enabled|- 11:0:0:0 sdb 8:i6 active ready running|- 12:0:0:0 sdz 65:144 active ready running

Note






Note



Example







Parameter Setting

detect_prio yes


failback immediate

fast_io_fail_tmo 5




no_path_retry queue

path_checker "tur"



polling_interval 5

prio "ontap"

Parameter Setting

product LUN.*


rr_weight "uniform"


vendor NETAPP

Example





1089555 Kernel disruptionobserved on kernelversion SLES12 SP3 withEmulex LPe16002 16GBFC during storagefailover operation

A kernel disruptionmight occur duringstorage failoveroperations on kernelversion SLES12 SP3 withEmulex LPe16002 HBA.The kernel disruptionprompts a reboot of theoperating system, whichin turn causes anapplication disruption.If the kdump isconfigured, the kerneldisruption generates avmcore file under/var/crash/directory. Youcan investigate thecause of the failure inthe vmcore file.Example:In the observed case, thekernel disruption wasobserved in the module“lpfc_sli_ringtxcmpl_put+51” and is logged in thevmcore file– exception RIP:lpfc_sli_ringtxcmpl_put+51.

Recover the operatingsystem after the kerneldisruption by rebootingthe host operatingsystem and restartingthe application.

1042847

https://https://mysupport.netapp.com/NOW/cgi-bin/bol?Type=Detail&Display=1089555



1089561 Kernel disruptionobserved on kernelversion SLES12 SP3 withEmulex LPe32002 32GBFC during storagefailover operations

A kernel disruptionmight occur duringstorage failoveroperations on kernelversion SLES12 SP3 withEmulex LPe32002 HBA.The kernel disruptionprompts a reboot of theoperating system, whichin turn causes anapplication disruption.If the kdump isconfigured, the kerneldisruption generates avmcore file under/var/crash/directory. Youcan investigate thecause of the failure inthe vmcore file.Example:In the observed case, thekernel disruption wasobserved in the module“lpfc_sli_free_hbq+76”and is logged in thevmcore file– exception RIP:lpfc_sli_free_hbq+76.

Recover the operatingsystem after the kerneldisruption by rebootingthe host operatingsystem and restartingthe application.

1042807




1117248 Kernel disruptionobserved on SLES12SP3with QLogic QLE25628GB FC during storagefailover operations

During storage failoveroperations on theSles12sp3 kernel(kernel-default-4.4.82-6.3.1) with QLogicQLE2562 HBA, thekernel disruption wasobserved due to a panicin the kernel. The kernelpanic leads to a rebootof the operating system,causing an applicationdisruption. The kernelpanic generates thevmcore file under the/var/crash/ directory ifkdump is configured.Upon the kernel panic,the vmcore file can beused to understand thecause of the failure.Example:In this case, the panicwas observed in the“blk_finish_request+289” module.It is logged in thevmcore file with thefollowing string:"exception RIP:blk_finish_request+289"

After the kerneldisruption, you canrecover the operatingsystem by rebooting theHost OS. You can restartthe application asrequired.

1062496




1117261 Kernel disruptionobserved on SLES12SP3with Qlogic QLE266216GB FC during storagefailover operations

During storage failoveroperations on Sles12sp3kernel (kernel-default-4.4.82-6.3.1) with QlogicQLE2662 HBA, youmight observe kerneldisruption. Thisprompts a reboot of theoperating systemcausing applicationdisruption. The kerneldisruption generates avmcore file under/var/crash/ directory ifkdump is configured.The vmcore file can beused to understand thecause of the failure.Example:In this case the Kerneldisruption was observedin the module"unknown or invalidaddress" and is loggedin vmcore file with thefollowing string -exception RIP: unknownor invalid address.

After kernel disruption,the operating systemcan be recovered byrebooting the hostoperating system andrestarting theapplication as required.

1062508




1117274 Kernel disruptionobserved on SLES12SP3with Emulex LPe1600216GB FC during storagefailover operations

During storage failoveroperations on Sles12sp3kernel (kernel-default-4.4.87-3.1) with EmulexLPe16002 HBA, youmight observe kerneldisruption. Thisprompts a reboot of theoperating systemcausing applicationdisruption. The kerneldisruptiongenerates a vmcore fileunder the /var/crash/directory if kdump isconfigured. The vmcorefile can be used tounderstand the causeof the failure.Example:In this case kerneldisruption was observedin the module“raw_spin_lock_irqsave+30” and is logged in thevmcore file with thefollowing string:– exception RIP:_raw_spin_lock_irqsave+30.

After kernel disruption,the operating systemcan be recovered byrebooting the hostoperating system andrestarting theapplication as required.

1062514

Release Notes



ASM Mirroring






Before you begin





SAN Toolkit


Example









SAN Booting

Before you begin








Multipathing





Example





Note




Example



Note






Note



Example







Parameter Setting

detect_prio yes


failback immediate

fast_io_fail_tmo 5




path_checker "tur"



polling_interval 5

prio "ontap"

product LUN.*


rr_weight "uniform"


vendor NETAPP

Example

The following example shows how to correct an overridden default. In this case, the multipath.conf filedefines values for path_checker and detect_prio 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 becorrected specifically for ONTAP LUNs with a device stanza.

defaults { path_checker readsector0 detect_prio no }devices { device { vendor "NETAPP " product "LUN.*" path_checker tur detect_prio yes }}



Release Notes

ASM Mirroring






Before you begin









SAN Toolkit


Example



SAN Booting

Before you begin












Multipathing





Example



Note




Example

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

and two Active/non-Optimized paths:


Note






Note



Example







Parameter Setting

detect_prio yes


failback immediate

fast_io_fail_tmo 5




path_checker "tur"



polling_interval 5

prio "ontap"

Parameter Setting

product LUN.*


rr_weight "uniform"


vendor NETAPP

Example

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




Release Notes

ASM Mirroring


Using SUSE Linux Enterprise Server 12 with NetApp ONTAP





Before you begin





SAN Toolkit


Example



SAN Booting

Before you begin















Multipathing

For SUSE Linux Enterprise Server 12 the /etc/multipath.conf file must exist, but you do not need tomake specific changes to the file. SUSE Linux Enterprise Server 12 is compiled with all settingsrequired to recognize and correctly manage ONTAP LUNs.




Example



Note




Example



Note



SUSE Linux Enterprise Server 12 OS is compiled to recognize ONTAP LUNs and automatically set allconfiguration parameters correctly.The multipath.conf file must exist for the multipath daemon to start, but you can create an empty, zero-byte file using the command:touch /etc/multipath.confThe first time you create this file, you might need to enable and start the multipath services.



Note



Example







Parameter Setting

detect_prio yes


failback immediate

fast_io_fail_tmo 5

Parameter Setting




path_checker "tur"



polling_interval 5

prio "ontap"

product LUN.*


rr_weight "uniform"


vendor NETAPP

Example





873555 scsi_dh_alua module isnot loaded duringmultipathd startup onlocal boot

scsi_dh_alua is a LinuxALUA device handlermodule. This is is notloaded duringmultipathd startup onlocal boot. Due to thisdevice handler will notbe loaded though ALUAis enabled on targetside.

908529

863584 The message "conflictingdevice node'/dev/mapper/360xx'found" appears on thescreen when you createa DM device on SLES12

You might observe afailure in creating a linkto DM devices under/dev/mapper dir in SLES12 and see the messages"conflicting device node'/dev/mapper/360xx'found".

903001

847490 Multipath daemonshows path failures onSLES 12

You might observe pathfailures on the SLES12multipath daemonduring I/O with storageor fabric faults.

890854

Release Notes

ASM Mirroring


Oracle Linux

OL 8

Using Oracle Linux 8.1 with NetApp ONTAP






https://bugzilla.novell.com/show_bug.cgi?id=890854





Before you begin





SAN Toolkit


Example



SAN Booting

Before you begin












Multipathing

For Oracle Linux 8.1 the /etc/multipath.conf file must exist, but you do not need to make specificchanges to the file. Oracle Linux 8.1 is compiled with all settings required to recognize and correctlymanage ONTAP LUNs.


Example



Note



The Oracle Linux 8.1 OS is compiled to recognize ONTAP LUNs and automatically set all configurationparameters correctly.The multipath.conf file must exist for the multipath daemon to start, but you can create an empty, zero-byte file using the command:

touch /etc/multipath.confThe first time you create this file, you might need to enable and start the multipath services.



Note



Example






You should always check your /etc/multipath.conf file for legacy settings, especially in the defaultssection, that may be overriding default settings.The table below shows the critical multipathd parameters for ONTAP LUNs and the required values. If ahost is connected to LUNs from other vendors and any of these parameters are overridden, they will

need to be corrected by later stanzas in multipath.conf that apply specifically to ONTAP LUNs. If this isnot done, the ONTAP LUNs may not work as expected. These defaults should only be overridden inconsultation with NetApp and/or OS vendor and only when the impact is fully understood.

Parameter Setting

detect_prio yes


failback immediate

fast_io_fail_tmo 5




no_path_retry queue

path_checker "tur"



polling_interval 5

prio "ontap"

product LUN.*


rr_weight "uniform"


vendor NETAPP

Example


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


There are no known issues for Oracle Linux 8.1.

Note

For Oracle Linux (Red Hat compatible kernel) known issues, see the Known Issues section in thecorresponding Red Hat Enterprise Linux release documentation.

Release Notes

ASM Mirroring






Before you begin


https://mysupport.netapp.com/documentation/productlibrary/index.html?productID=63146






SAN Toolkit


Example



SAN Booting

Before you begin











Multipathing



Example



Note



The Oracle Linux 8.0 OS is compiled to recognize ONTAP LUNs and automatically set all configurationparameters correctly.The multipath.conf file must exist for the multipath daemon to start, but you can create an empty, zero-byte file using the command:touch /etc/multipath.confThe first time you create this file, you might need to enable and start the multipath services.


There is no requirement to add anything directly to multipath.conf, unless you have devices that youdo not want to be managed by multipath or you have existing settings that override defaults.

You can add the following syntax to the multipath.conf file to exclude the unwanted devices.

Note



Example







Parameter Setting

detect_prio yes


Parameter Setting

failback immediate

fast_io_fail_tmo 5




no_path_retry queue

path_checker "tur"



polling_interval 5

prio "ontap"

product LUN.*


rr_weight "uniform"


vendor NETAPP

Example


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



Note


Release Notes

ASM Mirroring


OL 7





Before you begin





SAN Toolkit

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








initiator groups.

Example



SAN Booting

Before you begin








Multipathing



Example

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



and two Active/non-Optimized paths:


Note






Note



Example







Parameter Setting

detect_prio yes


failback immediate

fast_io_fail_tmo 5




path_checker "tur"



polling_interval 5

prio "ontap"

Parameter Setting

product LUN.*


rr_weight "uniform"


vendor NETAPP

Example





Note


Release Notes

ASM Mirroring








Before you begin





SAN Toolkit


Example



SAN Booting

Before you begin















Multipathing



Example



Note







Note



Example







Parameter Setting

detect_prio yes


failback immediate

fast_io_fail_tmo 5




path_checker "tur"



polling_interval 5

prio "ontap"

product LUN.*


rr_weight "uniform"


vendor NETAPP

Example



1202736 LUNs might not beavailable during hostdiscovery due to "NotPresent" state of remoteports on a OL7U6 hostwith QLogic QLE2742adapter

During host discovery,the status of FibreChannel (FC) remoteports on a OL7U6 hostwith a QLogic QLE2742adapter might enter into"Not Present" state.Remote ports with a"Not Present" statemight cause paths toLUNs to becomeunavailable. Duringstorage failover, thepath redundancy mightbe reduced and result inan I/O outage.You can check theremote port status byentering the followingcommand:# cat/sys/class/fc_remote_ports/rport-*/port_stateThe following is anexample of the outputthat is displayed:OnlineOnlineNot PresentOnlineOnline

16613


https://bugzilla.oracle.com/bugzilla/show_bug.cgi?id=16613


1204078 Kernel disruptionoccurs on Oracle Linux7.6 running withQlogic(QLE2672) 16GBFC HBA during storagefailover operations

During storage failoveroperations on the OracleLinux 7.6 with a QlogicQLE2672 Fibre Channel(FC) host bus adapter(HBA), a kerneldisruption occurs due toa panic in the kernel.The kernel panic causesOracle Linux 7.6 toreboot, which leads toan applicationdisruption. If the kdumpmechanism is enabled,the kernel panicgenerates a vmcore filelocated in the /var/crash/directory. You cananalyze the vmcore fileto determine the causeof the panic. After thekernel disruption, youcan reboot the host OSand recover theoperating system, andthen you can restart anyapplications as required.

16606




1204351 Kernel disruption mightoccur on Oracle Linux7.6 running withQlogic(QLE2742) 32GBFC HBA during storagefailover operations

During storage failoveroperations on the OracleLinux 7.6 with a QlogicQLE2742 Fibre Channel(FC) host bus adapter(HBA), a kerneldisruption might occurdue to a panic in thekernel. The kernel paniccauses Oracle Linux 7.6to reboot, which leads toan applicationdisruption. If the kdumpmechanism is enabled,the kernel panicgenerates a vmcore filelocated in the /var/crash/directory. You cananalyze the vmcore fileto determine the causeof the panic.After the kerneldisruption, you canreboot the host OS andrecover the operatingsystem, and then youcan restart anyapplications as required.

16605




1204352 Kernel disruption mightoccur on Oracle Linux7.6 running withEmulex (LPe32002-M2)32GB FC HBA duringstorage failoveroperations

During storage failoveroperations on the OracleLinux 7.6 with anEmulex LPe32002-M2Fibre Channel (FC) hostbus adapter (HBA), akernel disruption mightoccur due to a panic inthe kernel. The kernelpanic causes OracleLinux 7.6 to reboot,which leads to anapplication disruption.If the kdumpmechanism is enabled,the kernel panicgenerates a vmcore filelocated in the /var/crash/directory. You cananalyze the vmcore fileto determine the causeof the panic.After the kerneldisruption, you canreboot the host OS andrecover the operatingsystem, and then youcan restart anyapplications as required.

16607




11246134 No I/O progress onOracle Linux 7.6 withUEK5U2 kernel, runningwith an EmulexLPe16002B-M6 16G FCHBA during storagefailover operations

During storage failoveroperations on the OracleLinux 7.6 with theUEK5U2 kernel runningwith an EmulexLPe16002B-M6 16GFibre Channel (FC) hostbus adapter (HBA), I/Oprogress might stop dueto reports gettingblocked. The storagefailover operationreports change from an"online" state to a"blocked" state, causinga delay in read andwrite operations. Afterthe operation hascompleted successfully,the reports fail to moveback to an "online" stateand continue to remainin a "blocked" state.

16852




1246327 Remote port status onQLogic QLE2672 16Ghost blocked duringstorage failoveroperations

Fibre Channel (FC)remote ports might beblocked on Red HatEnterprise Linux (RHEL)7.6 with the QLogicQLE2672 16G hostduring storage failoveroperations. Because thelogical interfaces godown when a storagenode is down, theremote ports set thestorage node status toblocked. IO progressmight stop due to theblocked ports if you arerunning both a QLogicQLE2672 16G host and aQLE2742 32GB FibreChannel (FC) host busadapter (HBA).When the storage nodereturns to its optimalstate, the logicalinterfaces also come upand the remote portsshould be online.However, the remoteports might still beblocked. This blockedstate registers as failedfaulty to LUNS at themultipath layer. You canverify the state of theremote ports with thefollowing command:# cat/sys/class/fc_remote_ports/rport-*/port_statYou should see thefollowing output:BlockedBlockedBlocked

16853



Note


Release Notes

ASM Mirroring






Before you begin





SAN Toolkit


Example










SAN Booting

Before you begin








Multipathing



Example





Note






Note



Example







Parameter Setting

detect_prio yes


failback immediate

fast_io_fail_tmo 5




path_checker "tur"



polling_interval 5

prio "ontap"

product LUN.*

Parameter Setting


rr_weight "uniform"


vendor NETAPP

Example

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




1177239 Kernel disruptionobserved on OL7.5 withQlogic QLE2672 16G FCduring storage failoveroperations

During storage failoveroperations on OracleLinux 7 (OL7.5) withkernel 4.1.12-112.16.4.el7uek.x86_64and the Qlogic QLE2672HBA, you might observekernel disruption. Thisprompts a reboot of theoperating system whichcauses an applicationdisruption.If kdump is configured,the kernel disruptioncreates a vmcore file inthe /var/crash/ directory.This disruption can beobserved in the module“kmem_cache_alloc+118,” which is logged in thevmcore file andidentified with thestring "exception RIP:kmem_cache_alloc+118."After a kerneldisruption, you canrecover by rebooting thehost operating systemand restarting theapplication.

Note


Release Notes

ASM Mirroring









Before you begin





SAN Toolkit


Example









SAN Booting

Before you begin








Multipathing



Example



Note








Note



Example







Parameter Setting

detect_prio yes


failback immediate

fast_io_fail_tmo 5




path_checker "tur"



polling_interval 5

prio "ontap"

product LUN.*


rr_weight "uniform"


vendor NETAPP

Example



1109468 Firmware dumpsobserved on an OL7.4Hypervisor withQLE8362 card

During storage failoveroperations on an OL7.4Hypervisor withQLE8362 card, thefirmware dumps areobserved occasionally.The firmware dumpsmight result in an I/Ooutage on the host,which might go up to500 seconds. After theadapter completes thefirmware dump, the I/Ooperation resumes inthe normal manner. Nofurther recoveryprocedure is requiredon the host. To indicatethe firmware dump, thefollowing message isdisplayed in the/var/log/message file:qla2xxx [0000:0c:00.3]-d001:8: Firmware dumpsaved to temp buffer(8/ffffc90008901000),dump status flags (0x3f)

16039

Note


Release Notes

ASM Mirroring










Before you begin





SAN Toolkit


Example



SAN Booting

Before you begin















Multipathing



Example



Note







Note



Example







Parameter Setting

detect_prio yes


failback immediate

fast_io_fail_tmo 5




path_checker "tur"



polling_interval 5

prio "ontap"

product LUN.*


rr_weight "uniform"


vendor NETAPP

Example

The following example shows how to correct an overridden default. In this case, the multipath.conf filedefines values for path_checker and detect_prio that are not compatible with ONTAP LUNs.

If they cannot be removed because of other SAN arrays still attached to the host, these parameters canbe corrected specifically for ONTAP LUNs with a device stanza.




Note


Release Notes

ASM Mirroring











Before you begin





SAN Toolkit


Example



SAN Booting

Before you begin









https://mysupport.netapp.com/matrix/imt.jsp?components=72764;72763;&solution=1&isHWU&src=IMT



Multipathing

Oracle Linux 7.2 supports Unbreakable Enterprise Kernel (UEK) R3 and UEK R4. The OS boots with UEKR3 kernel by default.

Oracle Linux 7.2 UEK R3 Configuration

For Oracle Linux 7.2 UEK R3, create an empty multipath.conf file. The settings for Oracle Linux 7.2 UEKwith and without ALUA update automatically by default. To Enable ALUA Handler, perform thefollowing steps:



Example

kernel /vmlinuz-3.8.13-68.1.2.el6uek.x86_64 ro root=/dev/mapper/vg_ibmx3550m421096-lv_root rd_NO_LUKSrd_LVM_LV=vg_ibmx3550m421096/lv_root LANG=en_US.UTF-8rd_NO_MDSYSFONT=latarcyrheb-sun16 crashkernel=256M KEYBOARDTYPE=pc KEYTABLE=usrd_LVM_LV=vg_ibmx3550m421096/lv_swap rd_NO_DM rhgb quiet rdloaddriver=scsi_dh_alua

3. Use the dracut -f command to recreate the initrd-image.

4. Reboot the host.



For Oracle Linux 7.2 UEK R4 the /etc/multipath.conf file must exist, but you do not need to makespecific changes to the file. Oracle Linux 7.2 is compiled with all settings required to recognize andcorrectly manage ONTAP LUNs.


Example



Note






Note



Example







Parameter Setting

detect_prio yes


failback immediate

fast_io_fail_tmo 5




path_checker "tur"



polling_interval 5

prio "ontap"

product LUN.*

Parameter Setting


rr_weight "uniform"


vendor NETAPP

Example





Note


Release Notes

ASM Mirroring








Before you begin





SAN Toolkit


Example



SAN Booting

Before you begin















Multipathing

Oracle Linux 7.1 supports Unbreakable Enterprise Kernel (UEK) R3 and UEK R4. The OS boots with UEKR3 kernel by default.


For Oracle Linux 7.1 UEK R3, create an empty multipath.conf file. The settings for Oracle Linux 7.1 UEKwith and without ALUA update automatically by default. To Enable ALUA Handler, perform thefollowing steps:



Example


3. Use the dracut -f command to recreate the initrd-image.

4. Reboot the host.



For Oracle Linux 7.1 UEK R4 the /etc/multipath.conf file must exist, but you do not need to makespecific changes to the file. Oracle Linux 7.1 is compiled with all settings required to recognize andcorrectly manage ONTAP LUNs.You can use the multipath -ll command to verify the settings for your ONTAP LUNs.There should be two groups of paths with different priorities. The paths with the higher priorities are


Active/Optimized, meaning they are serviced by the controller where the aggregate is located. Thepaths with the lower priorities are active but are non-optimized because they are served from adifferent controller. The non-optimized paths are only used when no optimized paths are available.

Example



Note



The Oracle Linux 7.1 OS is compiled to recognize ONTAP LUNs and automatically set all configurationparameters correctly.

The multipath.conf file must exist for the multipath daemon to start, but you can create an empty, zero-byte file using the command:touch /etc/multipath.confThe first time you create this file, you might need to enable and start the multipath services.



Note



Example







Parameter Setting

detect_prio yes


failback immediate

fast_io_fail_tmo 5



Parameter Setting


path_checker "tur"



polling_interval 5

prio "ontap"

product LUN.*


rr_weight "uniform"


vendor NETAPP

Example




There are no known issues for Oracle Linux 7.1..NoteFor Oracle Linux (Red Hat compatible kernel) known issues, see the Known Issues section in thecorresponding Red Hat Enterprise Linux release documentation.


Release Notes

ASM Mirroring






Before you begin





SAN Toolkit


Example









SAN Booting

Before you begin








Multipathing

For Oracle Linux 7.0 the /etc/multipath.conf file must exist, but you do not need to make specificchanges to the file. Oracle Linux 7.0 is compiled with all settings required to recognize and correctlymanage ONTAP LUNs. To Enable ALUA Handler, perform the following steps:



Example


3. Recreate the initrd-image with the dracut -f command.



4. Reboot the host.



Example



Note







Note



Example







Parameter Setting

detect_prio yes


failback immediate

Parameter Setting

fast_io_fail_tmo 5




path_checker "tur"



polling_interval 5

prio "ontap"

product LUN.*


rr_weight "uniform"


vendor NETAPP

Example





901558 OL7.0 : Host loses allpaths to the lun andhangs due to "RSCNtimeout" error on OL 7.0UEK r3U5 Beta onEmulex 8G(LPe12002)host

You might observe thatthe Emulex8G(LPe12002) hosthangs and there is ahigh I/O outage duringstorage failoveroperations with I/O. Youmight observe paths notrecovering, which is aresult of the RSCNtimeout, due to whichthe host loses all thepaths and hangs.Probability of hittingthis issue is high.

14898

901557 OL 7.0: High IO outageobserved on QLogic 8GFC (QLE2562) SAN hostduring storage failoveroperations with IO

You might observe highIO outage on QLogic 8GFC (QLE2562) hostduring storage failoveroperations with IO.Aborts and Device resetsmanifests as IO outageon the host. Probabilityof hitting this IO outageis high.

14894

894766 OL7.0: Dracut fails toinclude scsi_dh_alua.komodule in initramfs onUEKR3U5 alpha

The scsi_dh_aluamodule might not loadeven after adding theparameter"rdloaddriver=scsi_dh_alua" in the kernelcommand line andcreating Dracut. As aresult, ALUA is notenabled for NetAppLUNs as recommended.

14860








894796 Anaconda displays aniSCSI login failuremessage although loginsare successful during OL7.0 OS installation

When you are installingOL 7.0, the anacondainstallation screendisplays that iSCSI loginto multiple target IPshave failed though theiSCSI logins aresuccessful. Anacondadisplays following errormessage:"Node Login Failed"You will observe thiserror only when youselect multiple target IPsfor iSCSI login.You can continue the OSinstallation by clickingthe "ok" button. This bugdoes not hamper eitherthe iSCSI or the OL 7.0OS installation.

14870

894771 OL7.0 : Anaconda doesnot add bootdevargument in kernel cmdline to set IP address foriSCSI SANboot OS install

Anaconda does not adda bootdev argument inthe kernel commandline where you set theIPv4 address during theOL 7.0 OS installation onan iSCSI multipath’dLUN. Owing to this, youcannot assign IPaddresses to any of theEthernet interfaces thatwere configured toestablish iSCSI sessionswith the storagesubsystem during theOL 7.0 boot. Since iSCSIsessions are notestablished, the rootLUN is not discoveredwhen the OS boots andhence the OS boot fails.

14871






916501 Qlogic 10G FCoE(QLE8152) host kernelcrash observed duringstorage failoveroperations with IO

You may observe akernel crash in Qlogicdriver module on 10GFCoE Qlogic (QLE8152)host. The crash occursduring storage failoveroperations with IO.Probability of hittingthis crash is high whichleads to longer IOoutage on the host.

15019

Note


Release Notes

ASM Mirroring


OL 6





Before you begin












SAN Toolkit


Example



SAN Booting

Before you begin












Multipathing

For Oracle Linux 6.10 the /etc/multipath.conf file must exist, but you do not need to make specificchanges to the file. Oracle Linux 6.10 is compiled with all settings required to recognize and correctlymanage ONTAP LUNs.To Enable ALUA Handler, perform the following steps:



Example


3. Use the mkinitrd command to recreate the initrd-image.Oracle 6x and later versions use either:The command: mkinitrd -f /boot/ initrd-"uname -r".img uname -rOrThe 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.There should be two groups of paths with different priorities. The paths with the higher prioritiesare Active/Optimized, meaning they are serviced by the controller where the aggregate is located.The paths with the lower priorities are active but are non-optimized because they are served froma different controller. The non-optimized paths are only used when no optimized paths areavailable.

Example


# multipath -ll3600a09803831347657244e527766394e dm-5 NETAPP,LUN C-Modesize=80G 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| |- 0:0:26:37 sdje 8:384 active ready running| |- 0:0:25:37 sdik 135:64 active ready running`-+- policy='round-robin 0' prio=10 status=enabled |- 0:0:18:37 sdda 70:128 active ready running |- 0:0:19:37 sddu 71:192 active ready running

Note





[root@jfs0 ~]# chkconfig multipathd on[root@jfs0 ~]#/etc/init.d/multipathd start


Note



Example







Parameter Setting

detect_prio yes


failback immediate

fast_io_fail_tmo 5




no_path_retry queue

path_checker "tur"



polling_interval 5

Parameter Setting

prio "ontap"

product LUN.*


rr_weight "uniform"


vendor NETAPP

Example




There are no known issues for Oracle 6.10.

Note


Release Notes

ASM Mirroring








Before you begin





SAN Toolkit


Example









SAN Booting

Before you begin








Multipathing




Example



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.There should be two groups of paths with different priorities. The paths with the higher priorities



are Active/Optimized, meaning they are serviced by the controller where the aggregate is located.The paths with the lower priorities are active but are non-optimized because they are served froma different controller. The non-optimized paths are only used when no optimized paths areavailable.

Example



Note







Note



Example







Parameter Setting

detect_prio yes


failback immediate

fast_io_fail_tmo 5



Parameter Setting


no_path_retry queue

path_checker "tur"



polling_interval 5

prio "ontap"

product LUN.*


rr_weight "uniform"


vendor NETAPP

Example





1082780 Firmware dumps areobserved occasionallyon OL6.9 hypervisorwith the QLE8362 card

During storage failoveroperations on OL6.9hypervisor withQLE8362 card, thefirmware dumps areobserved occasionally.The firmware dumpsmight result in an I/Ooutage on the hostwhich might go up to athousand seconds. Afterthe adapter completesthe firmware dump, theI/O operation resumes inthe normal manner. Nofurther recoveryprocedure is requiredon the host. To indicatethe firmware dump, thefollowing message isdisplayed in the/var/log/message file:qla2xxx [0000:0c:00.3]-d001:3: Firmware dumpsaved to temp buffer(3/ffffc90008901000),dump status flags (0x3f).

16039

Note


Release Notes

ASM Mirroring










Before you begin





SAN Toolkit


Example



SAN Booting

Before you begin















Multipathing




Example



4. Reboot the host.



Example



Note







Note



Example







Parameter Setting

detect_prio yes


failback immediate

fast_io_fail_tmo 5



Parameter Setting


no_path_retry queue

path_checker "tur"



polling_interval 5

prio "ontap"

product LUN.*


rr_weight "uniform"


vendor NETAPP

Example





Note



Release Notes

ASM Mirroring






Before you begin





SAN Toolkit


Example









SAN Booting

Before you begin








Multipathing




Example


https://mysupport.netapp.com/matrix/imt.jsp?components=74908;74907;71545;71546;&solution=1&isHWU&src=IMT

https://mysupport.netapp.com/matrix/imt.jsp?components=74908;74907;71545;71546;&solution=1&isHWU&src=IMT


4. Reboot the host.


Example



Note







Note



Example






You should always check your /etc/multipath.conf file for legacy settings, especially in the defaultssection, that may be overriding default settings.The table below shows the critical multipathd parameters for ONTAP LUNs and the required values. If ahost is connected to LUNs from other vendors and any of these parameters are overridden, they willneed to be corrected by later stanzas in multipath.conf that apply specifically to ONTAP LUNs. If this isnot done, the ONTAP LUNs may not work as expected. These defaults should only be overridden in

consultation with NetApp and/or OS vendor and only when the impact is fully understood.

Parameter Setting

detect_prio yes


failback immediate

fast_io_fail_tmo 5




no_path_retry queue

path_checker "tur"



polling_interval 5

prio "ontap"

product LUN.*


rr_weight "uniform"


vendor NETAPP

Example





Note


Release Notes

ASM Mirroring






Before you begin










SAN Toolkit


Example



SAN Booting

Before you begin










https://mysupport.netapp.com/matrix/imt.jsp?components=74908;74907;71545;71546;69941;69939;69940;&solution=1&isHWU&src=IMT

https://mysupport.netapp.com/matrix/imt.jsp?components=74908;74907;71545;71546;69941;69939;69940;&solution=1&isHWU&src=IMT

Multipathing




Example



4. Reboot the host.


Example



Note







Note



Example







Parameter Setting

detect_prio yes


failback immediate

fast_io_fail_tmo 5




no_path_retry queue

path_checker "tur"



polling_interval 5

Parameter Setting

prio "ontap"

product LUN.*


rr_weight "uniform"


vendor NETAPP

Example





Note


Release Notes

ASM Mirroring








Before you begin





SAN Toolkit


Example









SAN Booting

Before you begin








Multipathing




Example



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.There should be two groups of paths with different priorities. The paths with the higher priorities

https://mysupport.netapp.com/matrix/imt.jsp?components=68083;67438;67437;&solution=1&isHWU&src=IMT

https://mysupport.netapp.com/matrix/imt.jsp?components=68083;67438;67437;&solution=1&isHWU&src=IMT

are Active/Optimized, meaning they are serviced by the controller where the aggregate is located.The paths with the lower priorities are active but are non-optimized because they are served froma different controller. The non-optimized paths are only used when no optimized paths areavailable.

Example



Note







Note



Example







Parameter Setting

detect_prio yes


failback immediate

fast_io_fail_tmo 5



Parameter Setting


no_path_retry queue

path_checker "tur"



polling_interval 5

prio "ontap"

product LUN.*


rr_weight "uniform"


vendor NETAPP

Example





Note



Release Notes

ASM Mirroring






Before you begin





SAN Toolkit


Example









SAN Booting

Before you begin








Multipathing




Example





4. Reboot the host.


Example



Note







Note



Example






You should always check your /etc/multipath.conf file for legacy settings, especially in the defaultssection, that may be overriding default settings.The table below shows the critical multipathd parameters for ONTAP LUNs and the required values. If ahost is connected to LUNs from other vendors and any of these parameters are overridden, they willneed to be corrected by later stanzas in multipath.conf that apply specifically to ONTAP LUNs. If this isnot done, the ONTAP LUNs may not work as expected. These defaults should only be overridden in

consultation with NetApp and/or OS vendor and only when the impact is fully understood.

Parameter Setting

detect_prio yes


failback immediate

fast_io_fail_tmo 5




no_path_retry queue

path_checker "tur"



polling_interval 5

prio "ontap"

product LUN.*


rr_weight "uniform"


vendor NETAPP

Example



713555 QLogic adapter resetsare seen on OL6.4 andOL5.9 with UEK2 oncontroller faults such astakeover/giveback, andreboot

QLogic adapter resetsare seen on OL6.4 hostswith UEK2 (kernel-uek-2.6.39-400.17.1.el6uek)or OL5.9 hosts withUEK2 (kernel-uek-2.6.39400.17.1.el5uek) whencontroller faults happen(such as takeover,giveback, and reboots).These resets areintermittent. Whenthese adapter resetshappen, a prolonged I/Ooutage (sometimes,more than 10 minutes)might occur until theadapter resets succeedand the paths' status areupdated by dm-multipath.

In /var/log/messages,messages similar to thefollowing are seen whenthis bugis hit:kernel: qla2xxx[0000:11:00.0]-8018:0:ADAPTER RESET ISSUEDnexus=0:2:13.

This is observed withthe kernel version:On OL6.4: kernel-uek-2.6.39-400.17.1.el6uekOn OL5.9: kernel-uek-2.6.39-400.17.1.el5uek

13999




715217 Delay in path recoveryon OL6.4 or OL5.9 hostswith UEK2 may result indelayed I/O resumptionon controller or fabricfaults

When a controller fault(storage failover orgiveback, reboots and soon) or a fabric fault (FCport disable or enable)occurs with I/O onOracle Linux 6.4 orOracle Linux 5.9 hostswith UEK2 Kernel, thepath recovery by DM-Multipath takes a longtime (4mins. to 10 mins).Sometimes, during thepaths recovering toactive state, thefollowing lpfc drivererrors are also seen:kernel: sd 0:0:8:3: [sdlt]Result:hostbyte=DID_ERRORdriverbyte=DRIVER_OK

Due to this delay in pathrecovery during faultevents, the I/Oresumption also delays.

OL 6.4 Versions:device-mapper-1.02.77-9.el6device-mapper-multipath-0.4.9-64.0.1.el6kernel-uek-2.6.39-400.17.1.el6uek

OL 5.9 Versions:device-mapper-1.02.77-9.el5device-mapper-multipath-0.4.9-64.0.1.el5kernel-uek-2.6.39-400.17.1.el5uek

14001



709911 DM Multipath on OL6.4& OL5.9 iSCSI with UEK2kernel takes long time toupdate LUN path statusafter storage faults

On systems runningOracle Linux 6 Update4and Oracle Linux 5Update9 iSCSI withUnbreakable EnterpriseKernel Release 2 (UEK2),a problem has beenseen during storagefault events where DMMultipath (DMMP) takesaround 15 minutes toupdate the path status ofDevice Mapper (DM)devices (LUNs).If you run the"multipath -ll" commandduring this interval, thepath status is shown as"failed ready running"for that DM device(LUN). The path status iseventually updated as"active ready running."This issue is seen withfollowing version:Oracle Linux 6 Update 4:UEK2 Kernel: 2.6.39-400.17.1.el6uek.x86_64Multipath: device-mapper-multipath-0.4.9-64.0.1.el6.x86_64iSCSI: iscsi-initiator-utils-6.2.0.873-2.0.1.el6.x86_64

Oracle Linux 5 Update 9:UEK2 Kernel: 2.6.39-400.17.1.el5uekMultipath: device-mapper-multipath-0.4.9-64.0.1.el5.x86_64iSCSI: iscsi-initiator-utils-6.2.0.872-16.0.1.el5.x86_64

13984


http://bugzilla.oracle.com/bugzilla/show_bug.cgi?id=13984


739909 The SG_IO ioctl systemcall fails on dm-multipath devices afteran FC fault on OL6.x andOL5.x hosts with UEK2

A problem is seen onOracle Linux 6.x hostswith UEK2 kernel andOracle Linux 5.x hostswith UEK2 kernel. Thesg_* commands on amultipath device failwith EAGAIN error code(errno) after a fabricfault that makes all thepaths in the active pathgroup go down. Thisproblem is seen onlywhen there is no I/Ooccurring to themultipath devices.The following is anexample:

# sg_inq -v/dev/mapper/3600a098041764937303f436c75324370inquiry cdb: 12 00 00 0024 00ioctl(SG_IO v3) failedwith os_err (errno) = 11inquiry: pass through oserror: Resourcetemporarily unavailableHDIO_GET_IDENTITYioctl failed:Resource temporarilyunavailable [11]Both SCSI INQUIRY andfetching ATAinformation failed on/dev/mapper/3600a098041764937303f436c75324370#

This problem occursbecause the path group

14082



Note


Release Notes

ASM Mirroring




Copyright Information

Copyright © 2020 NetApp, Inc. All rights reserved. Printed in the U.S. No part of this documentcovered by copyright may be reproduced in any form or by any means-graphic, electronic, ormechanical, including photocopying, recording, taping, or storage in an electronic retrieval system-without prior written permission of the copyright owner.

Software derived from copyrighted NetApp material is subject to the following license and disclaimer:

THIS SOFTWARE IS PROVIDED BY NETAPP “AS IS” AND WITHOUT ANY EXPRESS OR IMPLIEDWARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES OFMERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE, WHICH ARE HEREBYDISCLAIMED. IN NO EVENT SHALL NETAPP BE LIABLE FOR ANY DIRECT, INDIRECT,INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES (INCLUDING, BUT NOTLIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES; LOSS OF USE, DATA, ORPROFITS; OR BUSINESS INTERRUPTION) HOWEVER CAUSED AND ON ANY THEORY OFLIABILITY, WHETHER IN CONTRACT, STRICT LIABILITY, OR TORT (INCLUDING NEGLIGENCE OROTHERWISE) ARISING IN ANY WAY OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OFTHE POSSIBILITY OF SUCH DAMAGE.

NetApp reserves the right to change any products described herein at any time, and without notice.NetApp assumes no responsibility or liability arising from the use of products described herein,except as expressly agreed to in writing by NetApp. The use or purchase of this product does notconvey a license under any patent rights, trademark rights, or any other intellectual propertyrights of NetApp.

The product described in this manual may be protected by one or more U.S. patents,foreign patents, or pending applications.

RESTRICTED RIGHTS LEGEND: Use, duplication, or disclosure by the government is subject torestrictions as set forth in subparagraph (c)(1)(ii) of the Rights in Technical Data andComputer Software clause at DFARS 252.277-7103 (October 1988) and FAR 52-227-19 (June 1987).

Trademark Information

NETAPP, the NETAPP logo, and the marks listed at http://www.netapp.com/TM are trademarks ofNetApp, Inc. Other company and product names may be trademarks of their respective owners.

http://www.netapp.com/TM

docs.netapp.com · ONTAP SAN Host Configuration This content provides distribution-specific...

Documents

Transcript of docs.netapp.com · ONTAP SAN Host Configuration This content provides distribution-specific...