Brocade Access Gateway Administrator's Guide - Supporting Fabric OS v5.2.1 (53-1000430-01)

1-8 Access Gateway Administrator’s Guide
Publication Number: 53-1000430-01
Failback policy
1
3. The host establishes a new connection with the fabric.
Example: Failback Policy
In Example 3, the Brocade Access Gateway N_1 remains disabled because the corresponding F_A1
port is offline. However N_2 comes back online. (See Figure 1-5 for the original failover scenario.)
The ports mapped to N_1 (F_1 and F_2) continue to be routed to N_3; the ports originally mapped to
N_2 (F_3 and F_4) are disabled, rerouted to N_2, and then enabled.
Figure 1-6 Failback policy behavior
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 3