HP 6400/8400 HP StorageWorks 6400/8400 Enterprise Virtual Array User Guide - Page 122

Risks, Limitations, Linux (32-bit) configuration, Requirements

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

Page 122 highlights

Risks • For nonclustered nodes with a single path HBA, a path failure from the HBA to the SAN switch will result in a loss of connection with storage devices. NOTE: For additional risks, see "OpenVMS and Tru64 UNIX failure scenarios" (page 129). Limitations • HP P6000 Continuous Access is not supported with single path configurations. Figure 36 OpenVMS 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 Linux (32-bit) configuration Requirements • Switch zoning or controller level SSP must be used to ensure each single path HBA has an exclusive path to its LUNs. • All nodes with direct connection to a disk must have the same access paths available to them. • Single path HBA server can be in the same fabric as servers with multiple 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. 122 Single Path Implementation

  • 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
Risks
•
For nonclustered nodes with a single path HBA, a path failure from the HBA to the SAN switch
will result in a loss of connection with storage devices.
NOTE:
For additional risks, see
“OpenVMS and Tru64 UNIX failure scenarios” (page 129)
.
Limitations
•
HP P6000 Continuous Access is not supported with single path configurations.
Figure 36 OpenVMS 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
Linux (32-bit) configuration
Requirements
•
Switch zoning or controller level SSP must be used to ensure each single path HBA has an
exclusive path to its LUNs.
•
All nodes with direct connection to a disk must have the same access paths available to them.
•
Single path HBA server can be in the same fabric as servers with multiple 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.
122
Single Path Implementation