Brocade Access Gateway Administrator's Guide - Supporting Fabric OS v5.3.0 (53-1000633-01, June 2007)

Access Gateway Administrator’s Guide 7
53-1000633-01
Failback policy
1
Example: Failover Policy
This example shows the failover behavior in a scenario where two fabric ports go offline, one after
the other.
• First the edge switch F_A1 port goes offline, as shown in Figure 5 on page 7 Example 1 (left),
causing the corresponding Access Gateway N_1 port to be disabled.
The ports mapped to N_1 fail over; F_1 fails over to N_2 and F_2 fails over to N_3.
• Next the F_A2 port goes offline, as shown in Figure 5 on page 7 Example 2 (right), causing the
corresponding Access Gateway N_2 port to be disabled.
The ports mapped to N_2 (F_1, F_3, and F_4) failover to N_3 and N_4. Note that the F_Ports
are evenly distributed to the remaining online N_Ports and that the F_2 did not participate in
the failover event.
FIGURE 5 Example 1 and 2 failover policy behavior
Failback policy
The Brocade Access Gateway failback policy automatically reroutes the F_Ports back to the
originally mapped N_Ports as those N_Ports come back online.
F_A2
Hosts
Access Gateway
Edge Switch
Fabric
(Switch_A)
enabled
NPIV
F_4
F_3
F_2
F_1
N_1
F_A1
enabled
NPIV
N_3
F_B1
enabled
NPIV
Host_1
Host_2
Host_3
Host_4
F_5
Host_5
F_6
Host_6
F_7
Host_7
F_8
Host_8
Edge Switch
(Switch_B)
N_4
F_B2
enabled
NPIV
N_2
Legend
Physical connection
Mapped online
Failover route online
Original mapped route
(offline)
Example 1
F_A2
Hosts
Access Gateway
Edge Switch
Fabric
(Switch_A)
enabled
NPIV
F_4
F_3
F_2
F_1
N_1
F_A1
enabled
NPIV
N_3
F_B1
enabled
NPIV
Host_1
Host_2
Host_3
Host_4
F_5
Host_5
F_6
Host_6
F_7
Host_7
F_8
Host_8
Edge Switch
(Switch_B)
N_4
F_B2
enabled
NPIV
Example 2
N_2