
Access Gateway Administrator’s Guide
11
53-1000605-01
Access Gateway policies
1
FIGURE 7
pg0 default setup
Figure 8
demonstrates that if you created port groups then, when an N_Port goes offline, the
F_Ports being routed through that port fails over to any of the N_Ports that are part of that port
group and are currently active. For example, if N_Port4 goes offline then F_Ports7 and 8 is routed
through to N_Port 3 as long as N_Port 3 is online because both N_Ports3 and 4 belong to the same
port group PG2. If no active N_Ports are available the F_Ports will be disabled. The F_Ports
belonging to a port group will not failover to N_Ports belonging to another port group.
FIGURE 8
Port grouping behavior
In Fabric OS 6.0.0, the PG policy is enabled by default. All N_Ports will be part of a default port
group with a special identifier 0. This port group is known as
pg0
.
When a dual redundant fabric configuration is used, F_Ports connected to an Access
Gateway-enabled switch can access some target devices from both the fabrics. In these cases, it is
recommended to have paths fail over to the redundant fabric when the primary fabric goes down.
This can be achieved by grouping N_Ports connected to the redundant fabrics into one single port
group.
Summary of Contents for Brocade BladeSystem 4/24
Page 1: ...53 1000605 01 19 Oct 2007 Access Gateway Administrator s Guide Supporting Fabric OS v6 0 0 ...
Page 24: ...14 Access Gateway Administrator s Guide 53 1000605 01 Access Gateway policies 1 ...
Page 30: ...20 Access Gateway Administrator s Guide 53 1000605 01 Enabling Access Gateway mode 2 ...
Page 48: ...38 Access Gateway Administrator s Guide 53 1000605 01 Default Port Mapping A ...
Page 62: ...52 Access Gateway Administrator s Guide 53 1000605 01 ...