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

Device mapping considerations, Access Gateway configuration.

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 49 highlights

Access Gateway mapping 2 1. Static device mapping to N_Port (if defined) 2. Device mapping to N_Port group (if defined) For more information, refer to "Port Grouping policy" on page 41. 3. Automatic Device Load Balancing within a port group (if enabled) For more information, refer to "Port Grouping policy" on page 41. 4. Port mapping to an N_Port 5. Port mapping to an N_Port in a port group (if defined) For more information, refer to "Port Grouping policy" on page 41. Device mapping considerations Consider the following points when using device mapping: • If the N_Port is disabled, all devices that are mapped to it will be disabled. Depending on the effective failover policy, the devices will be enabled on other N_Ports. • Similar to port mappings, device mappings are affected by changes to underlying F_Ports. In other words, if an F_Port needs to be taken offline, both the physical device and all virtual nodes behind it will momentarily go offline. • Once devices are mapped to an N_Port rather than an N_Port group, they cannot be automatically rebalanced to another N_Port if an additional N_Port comes online. • There can be cases where two NPIV devices logging in through the same F_Port are mapped to two different N_Ports that are connected to two different fabrics. In this case, both NPIV devices may be allocated the same PID by their respective fabrics. Once Access Gateway detects this condition, it will disable that F_Port, and the event will be logged. NOTE Access Gateway algorithms reduce the chances of PID collisions, but they cannot be totally eliminated. In some cases, you may be able to configure your virtual or physical fabrics to further reduce PID collisions. • Device mapping is not supported when firmware is downgraded to Fabric OS v6.3.x or earlier. You must delete device mappings before downgrading or disable Device Load Balancing. • Static and dynamic device mapping are only supported on the edge module in a cascaded Access Gateway configuration. • When mapping devices to a port group, make sure that all ports in the group have the same NPIV login limit. If some ports have a lower login limit than the other ports, and there are many logins to the group, some devices will repeatedly attempt to connect to the device with the lower limit (because it has the fewest logins) and fail to connect. Access Gateway Administrator's Guide 29 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
Access Gateway Administrator’s Guide
29
53-1002743-01
Access Gateway mapping
2
1.
Static device mapping to N_Port (if defined)
2.
Device mapping to N_Port group (if defined)
For more information, refer to
“Port Grouping policy”
on page 41.
3.
Automatic Device Load Balancing within a port group (if enabled)
For more information, refer to
“Port Grouping policy”
on page 41.
4.
Port mapping to an N_Port
5.
Port mapping to an N_Port in a port group (if defined)
For more information, refer to
“Port Grouping policy”
on page 41.
Device mapping considerations
Consider the following points when using device mapping:
•
If the N_Port is disabled, all devices that are mapped to it will be disabled. Depending on the
effective failover policy, the devices will be enabled on other N_Ports.
•
Similar to port mappings, device mappings are affected by changes to underlying F_Ports. In
other words, if an F_Port needs to be taken offline, both the physical device and all virtual
nodes behind it will momentarily go offline.
•
Once devices are mapped to an N_Port rather than an N_Port group, they cannot be
automatically rebalanced to another N_Port if an additional N_Port comes online.
•
There can be cases where two NPIV devices logging in through the same F_Port are mapped to
two different N_Ports that are connected to two different fabrics. In this case, both NPIV
devices may be allocated the same PID by their respective fabrics. Once Access Gateway
detects this condition, it will disable that F_Port, and the event will be logged.
NOTE
Access Gateway algorithms reduce the chances of PID collisions, but they cannot be totally
eliminated. In some cases, you may be able to configure your virtual or physical fabrics to
further reduce PID collisions.
•
Device mapping is not supported when firmware is downgraded to Fabric OS v6.3.x or earlier.
You must delete device mappings before downgrading or disable Device Load Balancing.
•
Static and dynamic device mapping are only supported on the edge module in a cascaded
Access Gateway configuration.
•
When mapping devices to a port group, make sure that all ports in the group have the same
NPIV login limit. If some ports have a lower login limit than the other ports, and there are many
logins to the group, some devices will repeatedly attempt to connect to the device with the
lower limit (because it has the fewest logins) and fail to connect.