HP 6100 HP 4x00/6x00/8x00 Enterprise Virtual Array User Guide (5697-0733, Marc - Page 68

Table 25 Failback preference behavior, Table 26 Failback Settings by operating system

Page 68 highlights

Table 25 Failback preference behavior (continued) Setting Path B Failover/Failback Point in time At initial presentation On dual boot or controller resynch On controller failover On controller failback Behavior The units are brought online to Controller B. If cache data for a LUN exists on a particular controller, the unit will be brought online there. Otherwise, the units are brought online to Controller B. All LUNs are brought online to the surviving controller. All LUNs remain on the surviving controller. After controller restoration, the units that are online to Controller A and set to Path B are brought online to Controller B. This is a one time occurrence. If the host then moves the LUN using SCSI commands, the LUN will remain where moved. Table 26 (page 68) describes the failback default behavior and supported settings when AULA-compliant multipath software is running with each operating system. Recommended settings may vary depending on your configuration or environment. Table 26 Failback Settings by operating system Operating system HP-UX IBM AIX Linux Default behavior Host follows the unit1 Host follows the unit1 Host follows the unit 1 Supported settings No Preference Path A/B - Failover Only Path A/B - Failover/Failback No Preference Path A/B - Failover Only Path A/B - Failover/Failback No Preference Path A/B - Failover Only Path A/B - Failover/Failback OpenVMS Sun Solaris VMware Host follows the unit Host follows the unit1 Host follows the unit1 No Preference Path A/B - Failover Only Path A/B - Failover/Failback (recommended) No Preference Path A/B - Failover Only Path A/B - Failover/Failback No Preference Path A/B - Failover Only Path A/B - Failover/Failback Windows Failback performed on the host No Preference Path A/B - Failover Only Path A/B - Failover/Failback 1 If preference has been configured to ensure a more balanced controller configuration, the Path A/B - Failover/Failback setting is required to maintain the configuration after a single controller reboot. 68 Enterprise Virtual Array operation

  • 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
  • 83
  • 84
  • 85
  • 86
  • 87
  • 88
  • 89
  • 90
  • 91
  • 92
  • 93
  • 94
  • 95
  • 96
  • 97
  • 98
  • 99
  • 100
  • 101
  • 102
  • 103
  • 104
  • 105
  • 106
  • 107
  • 108
  • 109
  • 110
  • 111
  • 112
  • 113
  • 114
  • 115
  • 116
  • 117
  • 118
  • 119
  • 120
  • 121
  • 122
  • 123
  • 124
  • 125
  • 126
  • 127
  • 128
  • 129
  • 130
  • 131
  • 132
  • 133
  • 134
  • 135
  • 136
  • 137
  • 138
  • 139
  • 140
  • 141
  • 142
  • 143
  • 144
  • 145
  • 146
  • 147
  • 148
  • 149
  • 150
  • 151
  • 152
  • 153
  • 154
  • 155
  • 156
  • 157
  • 158
  • 159
  • 160
  • 161
  • 162
  • 163
  • 164
  • 165
  • 166
  • 167
  • 168
  • 169
  • 170
  • 171
  • 172
  • 173
  • 174
  • 175
  • 176
  • 177
  • 178
  • 179
  • 180
  • 181
  • 182
  • 183
  • 184
  • 185

Table 25 Failback preference behavior
(continued)
Behavior
Point in time
Setting
The units are brought online to Controller B.
At initial presentation
Path B -
Failover/Failback
If cache data for a LUN exists on a particular
controller, the unit will be brought online there.
Otherwise, the units are brought online to
Controller B.
On dual boot or controller resynch
All LUNs are brought online to the surviving
controller.
On controller failover
All LUNs remain on the surviving controller.
After controller restoration, the units that are
online to Controller A and set to Path B are
brought online to Controller B. This is a one
time occurrence. If the host then moves the LUN
using SCSI commands, the LUN will remain
where moved.
On controller failback
Table 26 (page 68)
describes the failback default behavior and supported settings when
AULA-compliant multipath software is running with each operating system. Recommended settings
may vary depending on your configuration or environment.
Table 26 Failback Settings by operating system
Supported settings
Default behavior
Operating system
No Preference
Path A/B – Failover Only
Path A/B – Failover/Failback
Host follows the unit
1
HP-UX
No Preference
Path A/B – Failover Only
Path A/B – Failover/Failback
Host follows the unit
1
IBM AIX
No Preference
Path A/B – Failover Only
Path A/B – Failover/Failback
Host follows the unit
1
Linux
No Preference
Path A/B – Failover Only
Path A/B – Failover/Failback
(recommended)
Host follows the unit
OpenVMS
No Preference
Path A/B – Failover Only
Path A/B – Failover/Failback
Host follows the unit
1
Sun Solaris
No Preference
Path A/B – Failover Only
Path A/B – Failover/Failback
Host follows the unit
1
VMware
No Preference
Path A/B – Failover Only
Path A/B – Failover/Failback
Failback performed on the host
Windows
1
If preference has been configured to ensure a more balanced controller configuration, the Path A/B – Failover/Failback setting
is required to maintain the configuration after a single controller reboot.
68
Enterprise Virtual Array operation