Skip to content

Latest commit

 

History

History
140 lines (108 loc) · 5.39 KB

hu_rhel_71.adoc

File metadata and controls

140 lines (108 loc) · 5.39 KB
sidebar permalink keywords summary
sidebar
hu_rhel_71.html
host utilities, red hat, rhel, linux, 7.1, netapp, ontap
Describes how to use Red Hat Enterprise Linux 7.1 with ONTAP

Use Red Hat Enterprise Linux 7.1 with ONTAP

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

SAN Booting

What you’ll need

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, and ONTAP version are supported.

Multipathing

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

# multipath -ll
3600a09803831347657244e527766394e dm-5 NETAPP,LUN C-Mode
size=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
# multipath -ll
3600a09803831347657244e527766394e dm-5 NETAPP,LUN C-Mode
size=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

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

Parameter Setting

detect_prio

yes

dev_loss_tmo

"infinity"

failback

immediate

fast_io_fail_tmo

5

features

"3 queue_if_no_path pg_init_retries 50"

flush_on_last_del

"yes"

hardware_handler

"0"

no_path_retry

queue

path_checker

"tur"

path_grouping_policy

"group_by_prio"

path_selector

"service-time 0"

polling_interval

5

prio

"ontap"

product

LUN.*

retain_attached_hw_handler

yes

rr_weight

"uniform"

user_friendly_names

no

vendor

NETAPP

Example

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

defaults {
   path_checker      readsector0
   no_path_retry      fail
}

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

Known issues

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

NetApp Bug ID Title Description Bugzilla ID

799323

Emulex FCoE (OCe10102-FX-D) host hang or path failures observed during I/O with storage failover operations

You might observe a host hang or path failures on Emulex 10G FCoE host (OCe10102-FX-D) during I/O with storage failover operations. In such scenarios, you might see the following message:
"driver’s buffer pool is empty, IO busied and SCSI Layer I/O Abort Request Status"

1061755

836875

IP addresses are not always assigned during the boot of a RHEL 7.0 OS installed on an iSCSI multipath’d LUN

When you install the root(/) on a iSCSI multipath’d LUN, the IP address for the Ethernet interfaces are specified in the kernel command line so that the IP addresses are assigned before the iSCSI service starts. However, dracut cannot assign IP addresses to all the Ethernet ports during the boot, before the iSCSI service starts. This causes the iSCSI login to fail on interfaces without IP addresses. You will see the iSCSI service attempt to login numerous times, which will cause a delay in the OS boot time.

1114966