HP 8/40 Brocade Access Gateway Administrator's Guide v6.3.0 (53-1001345-01, Ju - Page 55

Failback, Failback configurations in Access Gateway

Get HP 8/40 PDF manuals and user guides View all HP 8/40 manuals
Add to My Manuals
Save this manual to your list of manuals

Page 55 highlights

Failback 3 The list of F_Ports must be enclosed in quotation marks. Port numbers must be separated by a semicolon. In the following example, F_Ports 3 and 9 are deleted from preferred secondary N_Port 4. switch:admin> ag --prefdel "3;9" 4 Preferred N_Port is deleted successfully for the F_Port[s] Failback Failback policy provides a means for hosts that have failed over to move back to their intended N_ports when these N_ports come back online. When Failback is enabled, all F_Ports automatically reroute back to these primary-mapped N_Ports. Failback is an N_Port parameter and is enabled by default. 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. Failback configurations in Access Gateway The following sequence describes how a failback event occurs: • When an N_Port comes back online, with Failback 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 configuration In Example 3, described in Figure 9 on page 36, the Access Gateway N_1 remains disabled because the corresponding F_A1 port is offline. However, N_2 comes back online. See Figure 8 on page 33 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. Access Gateway Administrator's Guide 35 53-1001345-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
  • 81
  • 82
Access Gateway Administrator’s Guide
35
53-1001345-01
Failback
3
The list of F_Ports must be enclosed in quotation marks. Port numbers must be separated by a
semicolon. In the following example, F_Ports 3 and 9 are deleted from preferred secondary
N_Port 4.
switch:admin>
ag --prefdel
"3;9" 4
Preferred N_Port is deleted successfully for the F_Port[s]
Failback
Failback policy provides a means for hosts that have failed over to move back to their intended
N_ports when these N_ports come back online. When Failback is enabled, all F_Ports
automatically reroute back to these primary-mapped N_Ports. Failback is an N_Port parameter and
is enabled by default.
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.
Failback configurations in Access Gateway
The following sequence describes how a failback event occurs:
•
When an N_Port comes back online, with Failback 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 configuration
In Example 3, described in
Figure 9
on page 36, the Access Gateway N_1 remains disabled
because the corresponding F_A1 port is offline. However, N_2 comes back online. See
Figure 8
on
page 33 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.