Failback policy configurations in Access Gateway
The following sequence describes how a failback event occurs:
• When an N_Port comes back online, with the Failback policy enabled, the F_Ports that were
originally mapped to it are temporarily disabled.
• The F_Port is rerouted to the primary mapped N_Port, and then re-enabled.
• The host establishes a new connection with the fabric.
NOTE
The failback period is quite fast and rarely causes an I/O error at the application level.

Failback example

In Example 3, described below, the Access Gateway N_1 remains disabled because the
corresponding F_A1 port is offline. However, N_2 comes back online. See Failover example on page
66 for the original failover scenario.
Ports F_1 and F_2 are mapped to N_1 and continue routing to N_3. Ports F_3 and F_4, which were
originally mapped to N_2, are disabled and rerouted to N_2, and then enabled.

Failback policy configurations in Access Gateway

72 Access Gateway Administrator's Guide
53-1003126-02