HP StorageWorks 8/80 Brocade Access Gateway Administrator's Guide v6.2.0 (53-1 - Page 34

Disabling the Failover policy, Failback policy

Page 34 highlights

2 Failback policy Disabling the Failover policy 1. Connect to the switch and log in as admin. 2. Enter the ag command with the --failovershow operand to display the failover setting. switch:admin> ag --failovershow 13 Failover on N_Port 13 is supported 3. Enter the ag --failoverdisable operand to disable failover. switch:admin> ag --failoverdisable 13 Failover policy is disabled for port 13 Failback policy The Failback policy automatically reroutes the F_Ports back to the primary mapped N_Ports as those N_Ports come back online, if the Failback policy is enabled for the N_Port. Only the originally mapped F_Ports fail back. In the case of multiple N_Port failures, only F_Ports that were mapped to the recovered N_Port experience failback. The remaining F_Ports are not redistributed among the online N_Ports during the failback. If the APC policy is enabled, by default, the failback policy is disabled. NOTE The Failback policy is an N_Port parameter. By default, the Failback policy is enabled. 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 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. Example: Failback Policy In Example 3, described in Figure 5 on page 17, the Access Gateway N_1 remains disabled because the corresponding F_A1 port is offline. However, N_2 comes back online. See Figure 4 on page 15 for the original fail over scenario. The 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. 16 Access Gateway Administrator's Guide 53-1001189-01

  • 1
  • 2
  • 3
  • 4
  • 5
  • 6
  • 7
  • 8
  • 9
  • 10
  • 11
  • 12
  • 13
  • 14
  • 15
  • 16
  • 17
  • 18
  • 19
  • 20
  • 21
  • 22
  • 23
  • 24
  • 25
  • 26
  • 27
  • 28
  • 29
  • 30
  • 31
  • 32
  • 33
  • 34
  • 35
  • 36
  • 37
  • 38
  • 39
  • 40
  • 41
  • 42
  • 43
  • 44
  • 45
  • 46
  • 47
  • 48
  • 49
  • 50
  • 51
  • 52
  • 53
  • 54
  • 55
  • 56
  • 57
  • 58
  • 59
  • 60
  • 61
  • 62
  • 63
  • 64
  • 65
  • 66
  • 67
  • 68
  • 69
  • 70
  • 71
  • 72
  • 73
  • 74
  • 75
  • 76
  • 77
  • 78
  • 79
  • 80

16
Access Gateway Administrator’s Guide
53-1001189-01
Failback policy
2
Disabling the Failover policy
1.
Connect to the switch and log in as admin.
2.
Enter the
ag
command with the
--
failovershow
<n_portnumber>
operand to display the
failover setting.
switch:admin>
ag --failovershow 13
Failover on N_Port 13 is supported
3.
Enter the
ag
--
failoverdisable
<n_portnumber>
operand to disable failover.
switch:admin>
ag --failoverdisable 13
Failover policy is disabled for port 13
Failback policy
The Failback policy automatically reroutes the F_Ports back to the primary mapped N_Ports as
those N_Ports come back online, if the Failback policy is enabled for the N_Port.
Only the originally mapped F_Ports fail back. In the case of multiple N_Port failures, only F_Ports
that were mapped to the recovered N_Port experience failback. The remaining F_Ports are not
redistributed among the online N_Ports during the failback. If the APC policy is enabled, by default,
the failback policy is disabled.
NOTE
The Failback policy is an N_Port parameter. By default, the Failback policy is enabled.
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 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.
Example: Failback Policy
In Example 3, described in
Figure 5
on page 17, the Access Gateway N_1 remains disabled
because the corresponding F_A1 port is offline. However, N_2 comes back online. See
Figure 4
on
page 15 for the original fail over scenario.
The 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.