Considerations For Access Gateway Mapping; Vmware Configuration - Brocade Communications Systems 8 Administrator's Manual

2
Access Gateway mapping
Pre-provisioning
You can use Fabric OS commands, Web Tools, and Fabric Manager to map devices that do not yet
exist. This allows applicable management programs to push configuration changes with out
worrying about the order in which they are received. For example, if system administrators need to
push a set of port group changes and a set of device mapping changes, they could push them in
either order with out error. This also applies to using Fabric OS commands for device mapping. You
could map several devices to a new port group then create the group without error. Removing a
device twice can also be accomplished without error.

VMware configuration

To use the device mapping feature for connecting VMware systems, refer to the Technical Brief:
How to Configure NPIV on VMware ESX Server 3.5 at following link:
http://www.brocade.com/downloads/documents/brocade_vmware_technical_briefs/Brocade_NP
IV_ESX3.5_WP.pdf
The following is a summary of the steps involved.
1. Make sure that virtual port names (VWWPN) of virtual machines (VM) are mapped to the
2. Make sure all VWWPNs are mapped for LUN access for array-based targets.
3. Make sure to include all VWWPNs in the zone configuration.
4. Zone the server's physical port to the storage device.
5. Finally check the traffic that originates from virtual node PID (VN PID). if configuration is
Failover and Failback considerations
When using device mapping with VMware, the base device initiates PLOGI and PRLI to the target,
and then discovers the LUN. The virtual device also initiates a PLOGI and PRLI to the target, but
LUN discovery does not occur. Therefore, when the device-mapped port is toggled and failover or
failback takes place, traffic will resume from the base device. We recommend one of the following
when using device mapping with VMware:
•
•

Considerations for Access Gateway mapping

This section outlines considerations and limitations for Access Gateway mapping types.
Mapping priority
To avoid potential problems when both port-based and device-based mapping are implemented, AG
uses the following priority system when verifying policies to select the N_Port where a FLOGI is
routed. Access Gateway considers all available mappings in the following order until one can be
used.
22
correct port group (or N_Port). Map all VWWPNs to N_Ports to avoid confusion.
correct, traffic will flow from VN PID.
Targets should also be reachable by the base device so that I/Os can resume if the mapped
device fails over and I/Os will move over to the base PID.
Reboot the server so that it initializes and uses device mapping
Access Gateway Administrator's Guide
53-1001760-01