| sidebar | permalink | keywords | summary |
|---|---|---|---|
sidebar |
hu_suse_12SP3.html |
host utilities, suse linux enterprise server 12 SP3, suse, linux, 12 SP3, netapp, ontap |
Describes how to use SUSE Linux Enterprise Server 12 SP3 with ONTAP |
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.
For SUSE Linux Enterprise Server 12 SP3 the /etc/multipath.conf file must exist, but you do not need to make specific changes to the file. SUSE Linux Enterprise Server 12 SP3 is compiled with all settings required to recognize and correctly manage ONTAP LUNs.
# multipath -ll 3600a0980383034466b2b4a3775474859 dm-3 NETAPP,LUN C-Mode size=20G features='4 queue_if_no_path pg_init_retries 50 retain_attached_hw_handle' hwhandler='1 alua' wp=rw |-+- policy='round-robin 0' prio=50 status=active | |- 1:0:8:1 sdb 8:16 active ready running | `- 2:0:8:1 sdd 8:48 active ready running `-+- policy='round-robin 0' prio=10 status=enabled |- 1:0:9:1 sdc 8:32 active ready running `- 2:0:9:1 sde 8:64 active ready running
# multipath -ll 3600a09803831347657244e527766394e dm-5 NETAPP,LUN C-Mode size=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
SUSE Linux Enterprise Server 12 SP3 OS is compiled to recognize ONTAP LUNs and automatically set all configuration parameters correctly.
_include/hu/reuse_hu_recommended_settings.adoc
| 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.* |
retain_attached_hw_handler |
yes |
rr_weight |
"uniform" |
user_friendly_names |
no |
vendor |
NETAPP |
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
}
}
| NetApp Bug ID | Title | Description | Bugzilla ID |
|---|---|---|---|
Kernel disruption observed on kernel version SLES12 SP3 with Emulex LPe16002 16GB FC during storage failover operation |
A kernel disruption might occur during storage failover operations on kernel version SLES12 SP3 with Emulex LPe16002 HBA. The kernel disruption prompts a reboot of the operating system, which in turn causes an application disruption. If the kdump is configured, the kernel disruption generates a vmcore file under /var/crash/directory. You can investigate the cause of the failure in the vmcore file. |
||
Kernel disruption observed on kernel version SLES12 SP3 with Emulex LPe32002 32GB FC during storage failover operations |
A kernel disruption might occur during storage failover operations on kernel version SLES12 SP3 with Emulex LPe32002 HBA. The kernel disruption prompts a reboot of the operating system, which in turn causes an application disruption. If the kdump is configured, the kernel disruption generates a vmcore file under /var/crash/directory. You can investigate the cause of the failure in the vmcore file. |
||
Kernel disruption observed on SLES12SP3 with QLogic QLE2562 8GB FC during storage failover operations |
During storage failover operations on the Sles12sp3 kernel (kernel-default-4.4.82-6.3.1) with QLogic QLE2562 HBA, the kernel disruption was observed due to a panic in the kernel. The kernel panic leads to a reboot of the operating system, causing an application disruption. The kernel panic generates the vmcore file under the /var/crash/ directory if kdump is configured. Upon the kernel panic, the vmcore file can be used to understand the cause of the failure. |
||
Kernel disruption observed on SLES12SP3 with Qlogic QLE2662 16GB FC during storage failover operations |
During storage failover operations on Sles12sp3 kernel (kernel-default-4.4.82-6.3.1) with Qlogic QLE2662 HBA, you might observe kernel disruption. This prompts a reboot of the operating system causing application disruption. The kernel disruption generates a vmcore file under /var/crash/ directory if kdump is configured. The vmcore file can be used to understand the cause of the failure. |
||
Kernel disruption observed on SLES12SP3 with Emulex LPe16002 16GB FC during storage failover operations |
During storage failover operations on Sles12sp3 kernel (kernel-default-4.4.87-3.1) with Emulex LPe16002 HBA, you might observe kernel disruption. This prompts a reboot of the operating system causing application disruption. The kernel disruption |