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

HP-UX configuration, Requirements, Risks, Limitations

Page 153 highlights

HP-UX configuration Requirements • Proper switch zoning must be used to ensure each single path HBA has an exclusive path to its LUNs. • Single path HBA server can be in the same fabric as servers with multiple HBAs. • Single path HBA server cannot share LUNs with any other HBAs. • In the use of snapshots and snapclones, the source virtual disk and all associated snapshots and snapclones must be presented to the single path hosts that are zoned with the same controller. In the case of snapclones, after the cloning process has completed and the clone becomes an ordinary virtual disk, you may present that virtual disk as you would any other ordinary virtual disk. HBA configuration • Host 1 is a single path HBA host. • Host 2 is a multiple HBA host with multi-pathing software. See Figure 50 (page 153). Risks • Disabled jobs hang and cannot umount disks. • Path or controller failure may results in loss of data accessibility and loss of host data that has not been written to storage. NOTE: For additional risks, see Table 57 (page 163). 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 not supported. Figure 50 HP-UX configuration 1 Network interconnection 2 Host 1 3 Host 2 4 Management server 5 SAN switch 1 6 SAN switch 2 7 Controller A 8 Controller B Supported configurations 153

  • 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

HP-UX configuration
Requirements
Proper switch zoning must be used to ensure each single path HBA has an exclusive path to
its LUNs.
Single path HBA server can be in the same fabric as servers with multiple HBAs.
Single path HBA server cannot share LUNs with any other HBAs.
In the use of snapshots and snapclones, the source virtual disk and all associated snapshots
and snapclones must be presented to the single path hosts that are zoned with the same
controller. In the case of snapclones, after the cloning process has completed and the clone
becomes an ordinary virtual disk, you may present that virtual disk as you would any other
ordinary virtual disk.
HBA configuration
Host 1 is a single path HBA host.
Host 2 is a multiple HBA host with multi-pathing software.
See
Figure 50 (page 153)
.
Risks
Disabled jobs hang and cannot umount disks.
Path or controller failure may results in loss of data accessibility and loss of host data that has
not been written to storage.
NOTE:
For additional risks, see
Table 57 (page 163)
.
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 not supported.
Figure 50 HP-UX configuration
5 SAN switch 1
1 Network interconnection
6 SAN switch 2
2 Host 1
7 Controller A
3 Host 2
8 Controller B
4 Management server
Supported configurations
153