Dell PowerConnect Brocade M6505 Brocade 7.1.0 Access Gateway Administrator's G - Page 42

Device mapping

Get Dell PowerConnect Brocade M6505 PDF manuals and user guides View all Dell PowerConnect Brocade M6505 manuals
Add to My Manuals
Save this manual to your list of manuals

Page 42 highlights

2 Access Gateway mapping Device mapping Device mapping allows you to map individual N_Port ID Virtualization (NPIV) devices to N_Ports. By mapping device WWNs directly to an N_Port group (recommended) or specific N_Ports, traffic from the device will always go to the same N_Port or N_Port group, regardless of the F_Port where the device logs in. When the Port Grouping and Device Load Balancing policies are enabled for a port group, WWNs mapped to that port group are automatically balanced among the online N_Ports in that group (refer to "Port Grouping policy modes" on page 43). NOTE Port Grouping policy is not supported when both Automatic Login Balancing and Device Load Balancing are enabled. Device mapping does not affect or replace the traditional port mapping. Device mapping is an optional mapping that will exist on top of existing port mapping. In general, mapping devices to N_Port groups is recommended over mapping devices to individual N_Ports within a port group. This ensures maximum device "up-time," especially during failover conditions and system power up. This is especially true when a reasonably large number of devices must connect to the same fabric through a single port group. The following aspects of device mapping are important to note: • Logins from a device mapped to a specific N_Port or N_Port group (device mapping) always have priority over unmapped devices that log in to an F_Port that has been mapped to the same N_Port or N_Port group (port mapping). • Current device routing (dynamic mapping) may turn out different than your intended mapping (static mapping), depending on which N_Ports are online and which policies are enabled (for example, Automatic Port Configuration, Device Load Balancing, Failover, or Failback). Therefore, it is recommended to map devices to N_Port groups instead of specific N_Ports within a port group when using device mapping. NOTE Automatic Port Configuration and Device Load Balancing cannot be enabled at the same time. Figure 6 illustrates an example of device mapping to port groups. In the example, WWNs 1, 2, and 3 can connect to any N_Port in Port Group 1 (PG1), while WWNs 4 and 5 can connect with any N_Port in Port Group 2 (PG2). 22 Access Gateway Administrator's Guide 53-1002743-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
  • 97
  • 98
  • 99
  • 100
  • 101
  • 102
  • 103
  • 104
  • 105
  • 106
  • 107
  • 108
22
Access Gateway Administrator’s Guide
53-1002743-01
Access Gateway mapping
2
Device mapping
Device mapping allows you to map individual N_Port ID Virtualization (NPIV) devices to N_Ports. By
mapping device WWNs directly to an N_Port group (recommended) or specific N_Ports, traffic from
the device will always go to the same N_Port or N_Port group, regardless of the F_Port where the
device logs in. When the Port Grouping and Device Load Balancing policies are enabled for a port
group, WWNs mapped to that port group are automatically balanced among the online N_Ports in
that group (refer to
“Port Grouping policy modes”
on page 43).
NOTE
Port Grouping policy is not supported when both Automatic Login Balancing and Device Load
Balancing are enabled.
Device mapping does not affect or replace the traditional port mapping. Device mapping is an
optional mapping that will exist on top of existing port mapping. In general, mapping devices to
N_Port groups is recommended over mapping devices to individual N_Ports within a port group.
This ensures maximum device “up-time,” especially during failover conditions and system power
up. This is especially true when a reasonably large number of devices must connect to the same
fabric through a single port group.
The following aspects of device mapping are important to note:
•
Logins from a device mapped to a specific N_Port or N_Port group (device mapping) always
have priority over unmapped devices that log in to an F_Port that has been mapped to the
same N_Port or N_Port group (port mapping).
•
Current device routing (dynamic mapping) may turn out different than your intended mapping
(static mapping), depending on which N_Ports are online and which policies are enabled (for
example, Automatic Port Configuration, Device Load Balancing, Failover, or Failback).
Therefore, it is recommended to map devices to N_Port groups instead of specific N_Ports
within a port group when using device mapping.
NOTE
Automatic Port Configuration and Device Load Balancing cannot be enabled at the same time.
Figure 6
illustrates an example of device mapping to port groups. In the example, WWNs 1, 2, and
3 can connect to any N_Port in Port Group 1 (PG1), while WWNs 4 and 5 can connect with any
N_Port in Port Group 2 (PG2).