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

HBA configuration, Risks, Limitations, Failure scenarios, HP-UX

Page 163 highlights

HBA configuration • Host 1 is a single path HBA. • Host 2 is a dual HBA host with multi-pathing software. See Figure 59 (page 163). Risks • Single path failure may result in data loss or disk corruption. NOTE: For additional risks, see Table 63 (page 166). Limitations • HP Continuous Access EVA is not supported with single path configurations. • Single path HBA server is not part of a cluster. • Booting from the SAN is supported on single path HBA servers. Figure 59 VMware configuration 1 Network interconnection 2 Single HBA server 3 Dual HBA server 4 Management server Failure scenarios HP-UX Table 57 HP-UX failure scenarios Fault stimulus Server failure (host power-cycled) Switch failure (SAN switch disabled) Controller failure 5 SAN switch 1 6 SAN switch 2 7 Controller A 8 Controller B Failure effect Extremely critical event on UNIX. Can cause loss of system disk. Short term: Data transfer stops. Possible I/O errors. Long term: Job hangs, cannot umount disk, fsck failed, disk corrupted, need mkfs disk. Short term: Data transfer stops. Possible I/O errors. Long term: Job hangs, cannot umount disk, fsck failed, disk corrupted, need mkfs disk. Failure scenarios 163

  • 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

HBA configuration
Host 1 is a single path HBA.
Host 2 is a dual HBA host with multi-pathing software.
See
Figure 59 (page 163)
.
Risks
Single path failure may result in data loss or disk corruption.
NOTE:
For additional risks, see
Table 63 (page 166)
.
Limitations
HP Continuous Access EVA is not supported with single path configurations.
Single path HBA server is not part of a cluster.
Booting from the SAN is supported on single path HBA servers.
Figure 59 VMware configuration
5 SAN switch 1
1 Network interconnection
6 SAN switch 2
2 Single HBA server
7 Controller A
3 Dual HBA server
8 Controller B
4 Management server
Failure scenarios
HP-UX
Table 57 HP-UX failure scenarios
Failure effect
Fault stimulus
Extremely critical event on UNIX. Can cause loss of system disk.
Server failure (host power-cycled)
Short term: Data transfer stops. Possible I/O errors.
Long term: Job hangs, cannot umount disk, fsck failed, disk corrupted,
need mkfs disk.
Switch failure (SAN switch disabled)
Short term: Data transfer stops. Possible I/O errors.
Long term: Job hangs, cannot umount disk, fsck failed, disk corrupted,
need mkfs disk.
Controller failure
Failure scenarios
163