Table of ContentsView in Frames

Sample configuration file for Oracle Linux Unbreakable Enterprise Kernel and Red Hat Compatible Kernel

All versions of Oracle Linux use a DM-Multipath configuration file, but there might be slight variations in the file based on which Oracle update you have installed. You can replace your current file with the sample file, and then change the values to ones that are appropriate for your system.

Sample configuration file for Oracle Linux Unbreakable Enterprise Kernel

All versions of Oracle Linux Unbreakable Enterprise Kernel (UEK) 5 series use a DM-Multipath configuration file, but there might be slight variations in the file based on which UEK update you have installed. You can replace your current file with the sample file, and then change the values to ones that are appropriate for your system.

You can use the sample Oracle Linux (UEK) 5 series configuration files to create your own multipath.conf file. When you create your file, keep the following in mind:

Oracle Linux Unbreakable Enterprise Kernel Series notes Explanation
Blacklist section You must provide information that is specific to your system in the blacklist section. Any names shown in the sample files are examples and will not work with your system.

SAN boot LUNs and the user_friendly_names parameter

NetApp recommends that you set the user_friendly_names to no. There have been reports of problems when this parameter is set to yes

SAN boot LUNs on Oracle Linux 5 series and the user_friendly_names parameter

  1. Change the user_friendly_names parameter to no.
  2. Make a backup of initrd-image.
  3. Re-create the initrd-image by using the mkinitrd command: mkinitrd -f /boot/initrd-"`uname -r`".img `uname -r`
  4. Change the root dm-multipath device name to the WWID-based device name in all of the locations that refer to the device, such as /etc/fstab and /boot/grub/device.map.

    For example, suppose the name of the root device is /dev/mapper/mpatha and the WWID of the device is 360a98000486e2f66426f583133796572. You must re-create the initrd-image and then change the device name to /dev/mapper/360a98000486e2f66426f583133796572 in /etc/fstab and /boot/grub/device.map, as well as any other place that refers to device /dev/mapper/mpatha.

  5. Reboot the host.

Oracle Linux 5 (UEK) update 11, 10, 9, and 8 with ALUA enabled sample configuration file

The following screen illustration shows sample values supplied when your host is running Oracle Linux 5 (UEK) with update 11, 10, 9, or 8 and has ALUA enabled. For Oracle Linux 5 (UEK) update 11, 10, 9, and 8, use the same values in the DM-Multipath configuration file, so that this file can apply to all versions.

Note: If you use the blacklist section, you must replace the sample information with information for your system.
defaults {
    queue_without_daemon     no
    flush_on_last_del     yes
    max_fds     max
    user_friendly_names     no
}
blacklist {
    wwid (35000c50072648313)
    devnode "^cciss.*"
    devnode "^hd[a-z]"
    devnode "^(ram|raw|loop|fd|md|dm-|sr|scd|st)[0-9]*"
}
devices {
device {
    hardware_handler     "1 alua"
    prio     "alua"
    product     "LUN.*"
    vendor     "NETAPP"
}
}

Oracle Linux 5 (UEK) update 11, 10, 9, and 8 without ALUA enabled sample configuration file

The following file provides an example of the values you need to supply when your host is running Oracle Linux 5 (UEK) with update 11, 10, 9, and 8 and does not have ALUA enabled.

Note: Unless you are running the iSCSI protocol and Data ONTAP operating in 7-Mode, you should have ALUA enabled.

Remember: If you use the blacklist section, you must replace the sample information with information for your system.

defaults {
    queue_without_daemon     no
    flush_on_last_del     yes
    max_fds     max
    user_friendly_names     no
}
blacklist {
    wwid (35000c50072648313)
    devnode "^cciss.*"
    devnode "^hd[a-z]"
    devnode "^(ram|raw|loop|fd|md|dm-|sr|scd|st)[0-9]*"
}
devices {
device {
    hardware_handler     "0"
    prio     "ontap"
    product     "LUN.*"
    vendor     "NETAPP"
}
}

Oracle Linux 6 series (Unbreakable Enterprise Kernel) with and without ALUA enabled sample configuration file

For Oracle Linux 6 series Unbreakable Enterprise Kernel, follow Red Hat 6 series sample DM Multipath configuration file.

Oracle Linux 7 series (Unbreakable Enterprise Kernel) with and without ALUA enabled sample configuration file

Remember: When you use a blacklist section, you must replace the sample information with information for your system.
# All data under blacklist must be specific to your system.
blacklist {
wwid < wwid_of_the_local_disk>
}

If you create a SAN boot LUN, you must perform the following steps:

  1. For Oracle Linux 7 series (Unbreakable Enterprise Kernel), create an empty multipath.conf file; all the settings for Oracle Linux 7 series (Unbreakable Enterprise Kernel) with and without ALUA are automatically updated by default
  2. Make a backup of initrd-image.
  3. Re-create the initrd-image using the command dracut -f
  4. Change the root dm-multipath device name to the WWID-based device name in all of the

    locations that refer to the device, such as /etc/fstab and /boot/grub/device.map.For example, suppose the name of the root device is /dev/mapper/mpatha and the WWID of the device is 360a98000486e2f66426f583133796572. You must re-create the initrd-image, and then change the device name to /dev/mapper/360a98000486e2f66426f583133796572 in /etc/fstab, /boot/grub/device.map,

    and any other place that that refers to device /dev/mapper/mpatha.

  5. Append the following parameter value to the kernel for ALUA and non-ALUA to work: rdloaddriver=scsi_dh_alua
    Example:
    kernel /vmlinuz-3.8.13-68.1.2.el6uek.x86_64 ro root=/dev/mapper/vg_ibmx3550m421096-lv_root rd_NO_LUKS
    rd_LVM_LV=vg_ibmx3550m421096/lv_root LANG=en_US.UTF-8 rd_NO_MD SYSFONT=latarcyrheb-sun16
    crashkernel=256M  KEYBOARDTYPE=pc KEYTABLE=us rd_LVM_LV=vg_ibmx3550m421096/lv_swap rd_NO_DM
    rhgb quiet rdloaddriver=scsi_dh_alua
  6. Reboot the host.

Sample configuration file for Oracle Linux Red Hat Compatible Kernel

All versions of Oracle Linux Red Hat Compatible Kernel (RHCK) 5 series use a DM-Multipath configuration file, but there might be slight variations in the file based on which RHCK update you have installed. You can replace your current file with the sample file, and then change the values to ones that are appropriate for your system.

You can use the sample Oracle Linux 5 series (RHCK) series configuration files shown here to create your own multipath.conf file. When you create your file, keep the following in mind:

Oracle Linux Red Hat Compatible Kernel 5 series notes Explanation
Blacklist Section You must provide information of your system in the blacklist section. Any names shown in the sample files are examples and will not work with your system.

SAN boot LUNs and the user_friendly_names parameter

NetApp recommends that you set the user_friendly_names parameter to no. There have been reports of problems when this parameter is set to yes.
Oracle Linux 5 prior to Update 6 If you are using a version of Oracle Linux 5 series prior to update 6, check the Recommended Host Settings for Linux Host Utilities to see whether there are any parameter values specific to that version.

SAN boot LUNs on Oracle Linux 5 series (RHCK) and user_friendly_names parameter

If you create a SAN boot LUN and the installer sets the user_friendly_names parameter to yes, you must perform the following steps:

  1. Change the user_friendly_names parameter to no.
  2. Make a backup of initrd-image.
  3. Re-create the initrd-image by using the mkinitrd command: mkinitrd -f /boot/initrd-"`uname -r`".img `uname -r`
  4. Change the root dm-multipath device name to the WWID-based device name in all of the locations that refer to the device, such as /etc/fstab and /boot/grub/device.map.

    For example, suppose the name of the root device is /dev/mapper/mpatha and the WWID of the device is 360a98000486e2f66426f583133796572. You must re-create the initrd-image, and then change the device name to /dev/mapper/360a98000486e2f66426f583133796572 in /etc/fstab and /boot/grub/device.map, as well as any other place that refers to device /dev/mapper/mpatha.

  5. Reboot the host.

Oracle Linux Red Hat Compatible Kernel 5 update 11, 10, 9, 8 and 7 with ALUA enabled sample configuration file

The following file provides an example of the values you need to supply when your host is running Oracle Linux 5 with update 11, 10, 9, 8 and 7 and has ALUA enabled.

Note: For Oracle Linux 5 (Red Hat Compatible Kernel) update 11, 10, 9, 8 and 7 use the same values in the DM- Multipath configuration file, so this file can apply to all versions.
Remember: If you use the blacklist section, you must replace the sample information with information for your system.
defaults {
user_friendly_names no
queue_without_daemon no
flush_on_last_del yes
max_fds max
pg_prio_calc avg
}
# All data under blacklist must be specific to your system.
blacklist {
devnode "^hd[a-z]"
devnode "^(ram|raw|loop|fd|md|dm-|sr|scd|st)[0-9]*"
devnode "^cciss.*"
}
devices {
device {
vendor "NETAPP"
product "LUN"
path_grouping_policy group_by_prio
features "3 queue_if_no_path pg_init_retries 50"
prio_callout "/sbin/mpath_prio_alua /dev/%n"
path_checker tur
path_selector "round-robin 0"
failback immediate
hardware_handler "1 alua"
rr_weight uniform
rr_min_io 128
getuid_callout "/sbin/scsi_id -g -u -s /block/%n"
}
}

Oracle Linux 5 (RHCK) update 11, 10, 9, 8, and 7 without ALUA enabled sample configuration file

The following file provides an example of the values you need to supply when your host is running Oracle Linux 5 (RHCK) with update 11,10, 9, 8, and 7 and does not have ALUA enabled.

Note: For Oracle Linux 5 (RHCK) update 11, 10, 9, 8 and 7 use the same values in the DM-Multipath configuration file, so this file can apply to all version.
Remember: If you use the blacklist section, you must replace the sample information with information for your system.
defaults {
user_friendly_names no
queue_without_daemon no
flush_on_last_del yes
max_fds max
pg_prio_calc avg
}
# All data under blacklist must be specific to your system.
blacklist {
devnode "^hd[a-z]"
devnode "^(ram|raw|loop|fd|md|dm-|sr|scd|st)[0-9]*"
devnode "^cciss.*"
}
devices {
device {
vendor "NETAPP"
product "LUN"
path_grouping_policy group_by_prio
features "3 queue_if_no_path pg_init_retries 50"
prio_callout "/sbin/mpath_prio_ontap /dev/%n"
path_checker tur
path_selector "round-robin 0"
failback immediate
hardware_handler "0"
rr_weight uniform
rr_min_io 128
getuid_callout "/sbin/scsi_id -g -u -s /block/%n"
}
}

Oracle Linux 5 update 6 (RHCK) with ALUA enabled sample configuration file

The following file provides an example of the values you need to supply when your host is running Oracle Linux 5 update 6 (RHCK) and has ALUA enabled:

Remember: If you use the blacklist section, you must replace the sample information with information for your system.

Oracle Linux 5 update 6 (RHCK) without ALUA enabled sample configuration file

The following file provides an example of the values you need to supply when your host is running Oracle Linux 5 update 6 (RHCK) with update 6 and does not have ALUA enabled.

Note: Unless you are running the iSCSI protocol and Data ONTAP operating in 7-Mode, you should have ALUA enabled.

Remember: If you use the blacklist section, you must replace the sample information with information for your system

defaults {
user_friendly_names no
queue_without_daemon no
flush_on_last_del yes
max_fds max
pg_prio_calc avg
}
# All data under blacklist must be specific to your system.
blacklist {
devnode "^hd[a-z]"
devnode "^(ram|raw|loop|fd|md|dm-|sr|scd|st)[0-9]*"
devnode "^cciss.*"
}
devices {
device {
vendor "NETAPP"
product "LUN"
path_grouping_policy group_by_prio
features "3 queue_if_no_path pg_init_retries 50"
prio_callout "/sbin/mpath_prio_alua /dev/%n"
path_checker tur
path_selector "round-robin 0"
failback immediate
hardware_handler "1 alua"
rr_weight uniform
rr_min_io 128
getuid_callout "/sbin/scsi_id -g -u -s /block/%n"
}
}

Oracle Linux 6 series (RHCK) with and without ALUA enabled sample configuration file

For Oracle Linux 6 series (RHCK), Please follow Red Hat 6 series sample DM-Multipath configuration file.

Oracle Linux 7 series (RHCK) with and without ALUA enabled sample configuration file

For Oracle Linux 7 series (RHCK), Please follow Red Hat 7 series sample DM-Multipath configuration file.