Table of Contents
Advertisement
Example: Failover Policy
This example shows the failover behavior in a scenario where two fabric ports go offline, one after
the other.
•
•
Example 1
Hosts
Host_1
Host_2
Host_3
Host_4
Host_5
Host_6
Host_7
Host_8
FIGURE 5
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.
Access Gateway Administrator's Guide
53-1000633-01
First the edge switch F_A1 port goes offline, as shown in
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
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.
Access Gateway
F_1
F_2
N_1
F_3
N_2
F_4
F_5
N_3
F_6
N_4
F_7
F_8
Example 1 and 2 failover policy behavior
Figure 5
on page 7 Example 2 (right), causing the
Example 2
Hosts
Host_1
Fabric
Edge Switch
(Switch_A)
Host_2
F_A1
NPIV
enabled
Host_3
F_A2
NPIV
enabled
Host_4
Edge Switch
(Switch_B)
Host_5
F_B1
NPIV
enabled
Host_6
F_B2
NPIV
enabled
Host_7
Host_8
Failback policy
Figure 5
on page 7 Example 1 (left),
Access Gateway
F_1
Edge Switch
(Switch_A)
F_2
F_A1
N_1
NPIV
enabled
F_3
F_A2
N_2
NPIV
enabled
F_4
Edge Switch
(Switch_B)
F_5
F_B1
N_3
NPIV
enabled
F_6
F_B2
N_4
NPIV
enabled
F_7
F_8
Legend
Physical connection
Mapped online
Failover route online
Original mapped route
(offline)
1
Fabric
7
Advertisement
Table of Contents
