Which two solutions require Raw Device Mapping using physical compatibility mode?

Which two solutions require Raw Device Mapping using physical compatibility mode? (Choose two.)

A.
Array-based snapshots

B.
MSCS clustering across ESX/ESXi hosts

C.
N_Port ID virtualization

D.
SAN management agents

4 Comments on “Which two solutions require Raw Device Mapping using physical compatibility mode?

  1. Pavel says:

    It should be B and C, shouldn’t it?

    In this article:
    http://kb.vmware.com/selfservice/microsites/search.do?language=en_US&cmd=displayKC&externalId=1037959
    There are:
    RDM: Configuration using shared storage for Quorum and/or Data must be on Fibre Channel (FC) based RDMs (physical mode for cluster across boxes “CAB”, virtual mode for cluster in a box “CIB”). RDMs on other than FC are not currently supported.

    I understand “across boxes” as “across ESX/ESXi hosts”

    1. Tony says:

      The asnwers are C and D

      D:
      http://pubs.vmware.com/vsphere-50/index.jsp?topic=%2Fcom.vmware.vsphere.storage.doc_50%2FGUID-4B2479B1-541D-4FF4-865E-2EE711294478.html

      Physical mode specifies minimal SCSI virtualization of the mapped device, allowing the greatest flexibility for SAN management software. Physical mode is useful to run SAN management agents or other SCSI target-based software in the virtual machine

      If you are using a raw disk in virtual mode, you can realize the benefits of VMFS such as advanced file locking for data protection
      ~~~~~~~
      C:
      http://blogs.vmware.com/vsphere/2011/11/npiv-n-port-id-virtualization.html

      Next, we need to map an RDM to the VM in order to enable NPIV. With the RDM mapped in Physical Compatability Mode (PassThru), return to the VM Properties Options tab and Fiber Channel NPIV & select the option to Generate new WWNs


Leave a Reply

Your email address will not be published. Required fields are marked *