You can assign a WWN to a new virtual machine with an RDM disk when you create this virtual machine, or to an existing virtual machine you can temporarily power off.

1

From the vSphere Client, click Inventory in the navigation bar, and expand the inventory as needed.

2

In the inventory list, select the managed host to which you want to add a new virtual machine.

3

Select File > New > Virtual Machine.

The New Virtual Machine wizard appears.

4

Select Custom, and click Next.

5

Type a virtual machine name, and click Next.

6

Select a folder or the root of a datacenter, and click Next.

7

If the resource pool option is available, expand the tree until you locate the resource pool in which you want to run the virtual machine, highlight it, and click Next.

8

Select a datastore in which to store the virtual machine files, and click Next.

9

Under Guest operating system, select the operating system family (Microsoft Windows, Linux, Novell NetWare, Solaris, or Other).

10

Select the version from the pull-down menu, and click Next.

11

Select the number of virtual processors in the virtual machine from the pull-down list, and click Next.

12

Configure the virtual machine’s memory size by selecting the number of megabytes, and click Next.

13

Configure network connections, and click Next.

14

Choose the type of SCSI adapter you want to use with the virtual machine.

15

Select Raw Device Mapping, and click Next.

16

From a list of SAN disks or LUNs, select a raw LUN you want your virtual machine to access directly.

17

Select a datastore for the RDM mapping file.

You can place the RDM file on the same datastore where your virtual machine files reside, or select a different datastore.

Note

If you want to use VMotion for a virtual machine with enabled NPIV, make sure that the RDM file is located on the same datastore where the virtual machine configuration file resides. You cannot perform Storage VMotion, or VMotion between datastores, when NPIV is enabled.

18

Select a compatibility mode, either physical or virtual.

Depending on your choice, subsequent screens offer different options.

Physical compatibility mode allows the guest operating system to access the hardware directly. Physical compatibility is useful if you are using SAN-aware applications in the virtual machine. However, powered on virtual machines that use RDMs configured for physical compatibility cannot be migrated if the migration involves copying the disk. Such virtual machines cannot be cloned or cloned to a template either.

Virtual compatibility allows the RDM to behave as if it were a virtual disk, so you can use such features as snapshotting, cloning, and so on.

19

On the Specify Advanced Options page, you can change the virtual device node and click Next.

20

Assign WWNs to the virtual machine.

21

On the Ready to Complete New Virtual Machine page, select the Edit the virtual machine settings before completion check box and click Next.