HP StorageWorks 8/24 Brocade Access Gateway Administrator's Guide v6.3.0 (53-1 - Page 43

Automatic Port Configuration policy considerations

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

Page 43 highlights

Port Grouping policy 3 Automatic Port Configuration policy considerations Following are the considerations for the Automatic Port Configuration policy: • The APC and the PG policies cannot be enabled at the same time. • You cannot manually configure F_Port-to-N_Port mapping with this policy enabled. Upgrade and downgrade considerations for the APC policy The following are supported: • Downgrading to Fabric OS v6.2.0 or earlier. • Upgrading from Fabric OS v6.2.0 to Fabric OS v6.3.0. • Upgrading from Fabric OS v6.2.0 to Fabric OS v6.3.0 will maintain the policy that was enabled in Fabric OS 6.2.0. Port Grouping policy The Port Grouping (PG) policy is enabled by default for Access Gateway. Use the PG policy to partition the fabric and host ports within an AG-enabled module into independently operated groups. Use the PG policy in the following situations: • When connecting the AG module to multiple physical or virtual fabrics. • When you want to isolate specific hosts to specific fabric ports for performance, security, or other reasons. How port groups work Create port groups using the ag --pgcreate command. This command groups N_ports together as "port groups." Any F_ports mapped to the N_ports belonging to a port group will become members of that port group. Port grouping fundamentally restricts failover of F_ports to the N_ports that belong to that group. For this reason an N_port cannot be member of two port groups. The default PG0 group contains all N_ports that do not belong to any other port groups. Figure 6 on page 24 shows that.if you have created port groups and then an N_Port goes offline, the F_Ports being routed through that port will fail over to any of the N_Ports that are part of that port group and are currently active. For example, if N_Port 4 goes offline then F_Ports 7 and 8 are routed through to N_Port 3 as long as N_Port3 is online because both N_Ports 3 and 4 belong to the same port group, PG2. If no active N_Ports are available, the F_Ports are disabled. The F_Ports belonging to a port group do not fail over to N_Ports belonging to another port group. Access Gateway Administrator's Guide 23 53-1001345-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
Access Gateway Administrator’s Guide
23
53-1001345-01
Port Grouping policy
3
Automatic Port Configuration policy considerations
Following are the considerations for the Automatic Port Configuration policy:
•
The APC and the PG policies cannot be enabled at the same time.
•
You cannot manually configure F_Port-to-N_Port mapping with this policy enabled.
Upgrade and downgrade considerations for the APC policy
The following are supported:
•
Downgrading to Fabric OS v6.2.0 or earlier.
•
Upgrading from Fabric OS v6.2.0 to Fabric OS v6.3.0.
•
Upgrading from Fabric OS v6.2.0 to Fabric OS v6.3.0 will maintain the policy that was enabled
in Fabric OS 6.2.0.
Port Grouping policy
The Port Grouping (PG) policy is enabled by default for Access Gateway. Use the PG policy to
partition the fabric and host ports within an AG-enabled module into independently operated
groups. Use the PG policy in the following situations:
•
When connecting the AG module to multiple physical or virtual fabrics.
•
When you want to isolate specific hosts to specific fabric ports for performance, security, or
other reasons.
How port groups work
Create port groups using the
ag
--
pgcreate
command. This command groups N_ports together as
“port groups.” Any F_ports mapped to the N_ports belonging to a port group will become members
of that port group. Port grouping fundamentally restricts failover of F_ports to the N_ports that
belong to that group. For this reason an N_port cannot be member of two port groups. The default
PG0 group contains all N_ports that do not belong to any other port groups.
Figure 6
on page 24 shows that.if you have created port groups and then an N_Port goes offline,
the F_Ports being routed through that port will fail over to any of the N_Ports that are part of that
port group and are currently active. For example, if N_Port 4 goes offline then F_Ports 7 and 8 are
routed through to N_Port 3 as long as N_Port3 is online because both N_Ports 3 and 4 belong to
the same port group, PG2. If no active N_Ports are available, the F_Ports are disabled. The F_Ports
belonging to a port group do not fail over to N_Ports belonging to another port group.