Port Grouping Policy - Brocade Communications Systems A7533A - Brocade 4Gb SAN Switch Base Administrator's Manual

1
Access Gateway policies
In Example 3, the ports F_1 and F_2 are mapped to N_1 and continue routing to N_3. Ports F_3
and F_4 were originally mapped to N_2 are disabled and rerouted to N_2, and then enabled.
FIGURE 6

Port Grouping policy

When connecting an AG to multiple fabrics or isolating a subset of servers from other servers, you
might want to group a number of servers and their corresponding fabric ports. You can do this
using the N_Port grouping feature. Port groups cannot be overlapped. This means that an F_Port or
N_Port cannot belong to two different groups.
The Path Failover and Failback policies remain the same within each port group and the Preferred
Secondary N_Port can only specify the N_Ports from the same group. This is why it is
recommended to form groups before defining the preferred secondary path. In FOS v6.0.0 by
default, the Port group policy is enabled. When upgrading to FOS v6.0.0, all the ports on the switch
module belong to a default port group zero identified as pg0. If needed, additional port groups can
be defined.
For example,
F_Ports 1-2 are using N_Port1 and N_Port1 goes offline, then F_Ports1-2 are routed through
N_Port2 because N_Port2 is in the same port group, pg0.
10
Access Gateway
Hosts
Host_1
F_1
Host_2
F_2
Host_3
F_3
Host_4
F_4
Host_5
F_5
Host_6
F_6
Host_7
F_7
Host_8
F_8
Failback policy behavior
Figure 7 on page 11 shows an example of pg0. If N_Port1 and 2 are in pg0 and
Example 3
Edge Switch
(Switch_A)
F_A1
N_1
NPIV
enabled
F_A2
N_2
NPIV
enabled
Edge Switch
(Switch_B)
F_B1
N_3
NPIV
enabled
F_B2
N_4
NPIV
enabled
Access Gateway Administrator's Guide
Fabric
Legend
Physical connection
Mapped online
Failover route online
Original mapped route
(offline)
53-1000605-01