6.0

Procedure
1 Open the New Virtual Machine wizard.
2 Select Custom, and click Next.
3 Follow all steps required to create a custom virtual machine.
4 On the Select a Disk page, select Raw Device Mapping, and click Next.
5 From a list of SAN disks or LUNs, select a raw LUN you want your virtual machine to access directly.
6 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.
7 Follow the steps required to create a virtual machine with the RDM.
8 On the Ready to Complete page, select the Edit the virtual machine settings before completion check
box and click Continue.
The Virtual Machine Properties dialog box opens.
9 Assign WWNs to the virtual machine.
a Click the Options tab, and select Fibre Channel NPIV.
b Select Generate new WWNs.
c Specify the number of WWNNs and WWPNs.
A minimum of 2 WWPNs are needed to support failover with NPIV. Typically only 1 WWNN is
created for each virtual machine.
10 Click Finish.
The host creates WWN assignments for the virtual machine.
What to do next
Register newly created WWNs in the fabric so that the virtual machine is able to log in to the switch, and
assign storage LUNs to the WWNs.
Modify WWN Assignments
You can modify WWN assignments for a virtual machine with an RDM.
Typically, you do not need to change existing WWN assignments on your virtual machine. In certain
circumstances, for example, when manually assigned WWNs are causing conflicts on the SAN, you might
need to change or remove WWNs.
Prerequisites
Launch the vSphere Client and log in to a vCenter Server system or an ESXi host.
Make sure to power off the virtual machine if you want to edit the existing WWNs.
Before you begin, ensure that your SAN administrator has provisioned the storage LUN ACL to allow the
virtual machine’s ESXi host to access it.
vSphere Administration with the vSphere Client
302 VMware, Inc.