Brocade Access Gateway Administrator's Guide Supporting Fabric OS v7.0.0 (53-1002156-01, April 2011)

46 Access Gateway Administrator’s Guide
53-1002156-01
Failover
3
Failover example
The following example shows the failover sequence of events in a scenario where two fabric ports
go offline, one after the other. Note that this example assumes that no preferred secondary N_Port
is set for any of the F_Ports.
• First, the Edge switch F_A1 port goes offline, as shown in Figure 10 on page 46 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 10 on page 46 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) fail over 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 port did not participate
in the failover event.
FIGURE 10 Failover behavior
F_A2
Hosts
Access Gateway
Edge Switch
Fabric
(Switch_A)
F_4
F_3
F_2
F_1
N_1
F_A1
N_3
F_B1
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
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)
F_4
F_3
F_2
F_1
N_1
F_A1
N_3
F_B1
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
Example 2
N_2