HP 1606 Access Gateway Administrator's Guide (53-1001760-01, June 2010) - Page 36

Port Grouping Policy is not supported when both Automatic Login Balancing and Device Load

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

Page 36 highlights

2 Access Gateway mapping NOTE Port Grouping Policy is not supported when both Automatic Login Balancing and Device Load Balancing are enabled. Device-based 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 fail-over 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. These 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 into 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 5 on page 17 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). 16 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
16
Access Gateway Administrator’s Guide
53-1001760-01
Access Gateway mapping
2
NOTE
Port Grouping Policy is not supported when both Automatic Login Balancing and Device Load
Balancing are enabled.
Device-based 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 fail-over 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.
These 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 into 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 5
on page 17 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).