HP 8/8 Access Gateway Administrator's Guide (53-1001760-01, June 2010) - Page 42

Considerations for Access Gateway mapping, Pre-provisioning, VMware configuration, Mapping priority

Get HP 8/8 PDF manuals and user guides View all HP 8/8 manuals
Add to My Manuals
Save this manual to your list of manuals

Page 42 highlights

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 correct port group (or N_Port). Map all VWWPNs to N_Ports to avoid confusion. 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 correct, traffic will flow from VN PID. 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: • 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 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 Access Gateway Administrator's Guide 53-1001760-01

  • 1
  • 2
  • 3
  • 4
  • 5
  • 6
  • 7
  • 8
  • 9
  • 10
  • 11
  • 12
  • 13
  • 14
  • 15
  • 16
  • 17
  • 18
  • 19
  • 20
  • 21
  • 22
  • 23
  • 24
  • 25
  • 26
  • 27
  • 28
  • 29
  • 30
  • 31
  • 32
  • 33
  • 34
  • 35
  • 36
  • 37
  • 38
  • 39
  • 40
  • 41
  • 42
  • 43
  • 44
  • 45
  • 46
  • 47
  • 48
  • 49
  • 50
  • 51
  • 52
  • 53
  • 54
  • 55
  • 56
  • 57
  • 58
  • 59
  • 60
  • 61
  • 62
  • 63
  • 64
  • 65
  • 66
  • 67
  • 68
  • 69
  • 70
  • 71
  • 72
  • 73
  • 74
  • 75
  • 76
  • 77
  • 78
  • 79
  • 80
  • 81
  • 82
  • 83
  • 84
  • 85
  • 86
  • 87
  • 88
  • 89
  • 90
  • 91
  • 92
  • 93
  • 94
  • 95
  • 96
22
Access Gateway Administrator’s Guide
53-1001760-01
Access Gateway mapping
2
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:
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
correct port group (or N_Port). Map all VWWPNs to N_Ports to avoid confusion.
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
correct, traffic will flow from VN PID.
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:
•
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
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.