Sample configuration file for Oracle VM 3 series

All versions of Oracle VM 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.

Oracle VM, SAN boot LUNs, and user_friendly_names parameter

You can use the sample Oracle VM configuration files to create your own multipath.conf file.

When you create your file, keep the following in mind:

Oracle VM 3.0.1, 3.1.1, and 3.2 series	Parameter notes
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.
wwid <Dev ID>	Use the actual device ID. Run the /lib/udev/scsi_id -gus /block/%n command on the SCSI drive to be blacklisted.
Multipath settings and heartbeat settings	Multipath settings and heartbeat settings must be the same on all hypervisors in a server pool.
SAN boot support	SAN booting is supported only with Oracle VM 3.1.1 and the FC protocol.
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.

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

Change the user_friendly_names parameter to no.
Make a backup of initrd-image.
Re-create the initrd-image by using the mkinitrd command.
You could use the following command line: mkinitrd -f /boot/initrd-"`uname -r`".img `uname -r`
Change the root dm-multipath device name to the WWID-based device name in all 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 the /dev/mapper/mpatha device.
Reboot the host.

The following file provides an example of the values you need to supply when your host is running Oracle VM 3.0.1 with 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
        max_fds               max       
        flush_on_last_del     no
        queue_without_daemon  no
}
# All data under blacklist must be specific to your system.
blacklist {
devnode "^hd[a-z]"
wwid "<wwid_of_the_local_disk>"
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                "1 queue_if_no_path"
       prio                    "alua"
       path_checker            directio
       no_path_retry           "queue"
       failback                immediate
       hardware_handler        "1 alua"
       rr_weight               uniform
       rr_min_io               128          
       getuid_callout          "/lib/udev/scsi_id -gus /block/%n"
            }
}

The following file provides an example of the values you need to supply when your host is running Oracle VM 3.0.1 and ALUA is not enabled.

Note: In addition to providing a DM-Multipath configuration file, you must also set the O2CB_HEARTBEAT_THRESHOLD timeout. For more information, see (Oracle VM) Configuring the O2CB_HEARTBEAT_THRESHOLD. Also, 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
        max_fds               max       
        flush_on_last_del     no
        queue_without_daemon  no
}
# All data under blacklist must be specific to your system.
blacklist {
devnode "^hd[a-z]"
wwid "<wwid_of_the_local_disk>"
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                "1 queue_if_no_path"
       prio                    "ontap"
       path_checker            directio
       no_path_retry           "queue"
       failback                immediate
       hardware_handler        "0"
       rr_weight               uniform
       rr_min_io               128          
       getuid_callout          "/lib/udev/scsi_id -gus /block/%n"
            }
}

The following file provides an example of the values you need to supply when your host is running Oracle VM 3.1.1 with ALUA enabled.

defaults {
        user_friendly_names   no
        max_fds               max       
        flush_on_last_del     no
        queue_without_daemon  yes
}
# All data under blacklist must be specific to your system.
blacklist {
devnode "^hd[a-z]"
wwid "<wwid_of_the_local_disk>"
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                    "alua"
       path_checker            tur
       no_path_retry           "queue"
       failback                immediate
       hardware_handler        "1 alua"
       rr_weight               uniform
       rr_min_io               128          
       getuid_callout          "/lib/udev/scsi_id -gus /block/%n"
            }
}

The following file provides an example of the values you need to supply when your host is running Oracle VM and ALUA is not enabled.

defaults {
        user_friendly_names   no
        max_fds               max       
        flush_on_last_del     no
        queue_without_daemon  yes
}
# All data under blacklist must be specific to your system.
blacklist {
devnode "^hd[a-z]"
wwid "<wwid_of_the_local_disk>"
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                    "ontap"
       path_checker            tur
       no_path_retry           "queue"
       failback                immediate
       hardware_handler        "0"
       rr_weight               uniform
       rr_min_io               128          
       getuid_callout          "/lib/udev/scsi_id -gus /block/%n"
            }
}

Oracle VM 3.2 series 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 VM and ALUA is enabled.

defaults {
        user_friendly_names   no
        max_fds               max       
        flush_on_last_del     no
        queue_without_daemon  no
}
# All data under blacklist must be specific to your system.
blacklist {
devnode "^hd[a-z]"
wwid "<wwid_of_the_local_disk>"
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                    "alua"
       path_checker            tur
       no_path_retry           "queue"
       failback                immediate
       hardware_handler        "1 alua"
       rr_weight               uniform
       rr_min_io               128          
       getuid_callout          "/lib/udev/scsi_id -gus /block/%n"
            }
}

Oracle VM 3.2 series 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 VM and ALUA is not enabled.

Note: In addition to providing a DM-Multipath configuration file, you must also set the O2CB_HEARTBEAT_THRESHOLD timeout. For more information see, (Oracle VM) Configuring the O2CB_HEARTBEAT_THRESHOLD. Also, unless you are running the iSCSI protocol and Data ONTAP operating in 7-Mode, you should have ALUA enabled.

defaults {
        user_friendly_names   no
        max_fds               max       
        flush_on_last_del     no
        queue_without_daemon  no
}
# All data under blacklist must be specific to your system.
blacklist {
devnode "^hd[a-z]"
wwid "<wwid_of_the_local_disk>"
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                    "ontap"
       path_checker            tur
       no_path_retry           "queue"
       failback                immediate
       hardware_handler        "0"
       rr_weight               uniform
       rr_min_io               128          
       getuid_callout          "/lib/udev/scsi_id -gus /block/%n"
            }
}