Access Gateway Administrator's Guide (53-1001760-01, June 2010)

Access Gateway Administrator’s Guide 45
53-1001760-01
Failover
3
FIGURE 10 Example 1 and 2 Failover behavior
Adding a preferred secondary N_Port (optional)
F_Ports automatically fail over to any available N_Port. Alternatively, you can specify a preferred
secondary N_Port in case the primary N_Port fails. If the primary N_Port goes offline, the F_Ports
fail over to the preferred secondary N_Port (if it is online), then re-enable. If the secondary N_Port is
offline, the F_Ports will disable. Define the preferred secondary N_Ports per F_Port. For example, if
two F_Ports are mapped to a primary N_Port 1, you can define a secondary N_Port for one of those
F_Ports and not define a secondary N_Port for the other F_Port. F_Ports must have a primary
N_Port mapped before a secondary N_Port can be configured.
1. Connect to the switch and log in using an account assigned to the admin role.
2. Enter the ag --prefset command with the “F_Port1;F_Port2; ...” N_Port operands to add the
preferred secondary F_Ports to the specified N_Port.
The F_Ports must be enclosed in quotation marks and the port numbers must be separated by
a semicolon, for example:
switch:admin> ag --prefset "3;9" 4
Preferred N_Port is set successfully for the F_Port[s]
NOTE
Preferred mapping is not allowed when automatic login balancing mode is enabled for a port group.
All N_Ports are the same when automatic login balancing is enabled.
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