HP Surestore 64 FW 05.01.00 and SW 07.01.00 HP StorageWorks SAN High Availabil - Page 100

Device Locality, Real-world SANs are

Page 100 highlights

Planning Considerations for Fibre Channel Topologies Depending on fabric performance requirements and cost, there are several options to solve ISL oversubscription problems, including: ■ Employ device locality - NT server 1 and its associated storage device can be connected through one director. NT server 2 and its associated storage device can be connected through the other director. As a result, minimal traffic flows across the ISL between directors and the congestion problem is mitigated. For additional information, refer to "Device Locality." ■ Install an additional ISL - A second ISL can be installed to balance the traffic load between fabric elements. Two ISLs are sufficient to support the bandwidth of both NT servers operating at peak load. ■ Upgrade the existing ISL - Fabric element software, firmware, and hardware can be upgraded to support a 2.125 Gbps bandwidth traffic load between fabric elements. A 2.125 Gbps ISL is sufficient to support the bandwidth of both NT servers operating at peak load. ■ Deliberately employ ISL oversubscription - Real-world SANs are expected to function well, even with oversubscribed ISLs. Device I/O is typically bursty; few devices operate at peak load for a significant length of time, and device loads seldom peak simultaneously. As a result, ISL bandwidth is usually not fully allocated, even for an oversubscribed link. An enterprise can realize significant cost savings by deliberately designing a SAN with oversubscribed ISLs that provide connectivity for noncritical applications. Device Locality Devices that communicate with each other through the same director or switch have high locality. Devices that must communicate with each other through one or more ISLs have low locality. Part (A) of Figure 42 illustrates high device locality with little ISL traffic. Part (B) of Figure 42 illustrates low device locality. 100 SAN High Availability Planning Guide

  • 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

Planning Considerations for Fibre Channel Topologies
100
SAN High Availability Planning Guide
Depending on fabric performance requirements and cost, there are several options
to solve ISL oversubscription problems, including:
Employ device locality —
NT server 1 and its associated storage device can
be connected through one director. NT server 2 and its associated storage
device can be connected through the other director. As a result, minimal traffic
flows across the ISL between directors and the congestion problem is
mitigated. For additional information, refer to “
Device Locality
.”
Install an additional ISL —
A second ISL can be installed to balance the
traffic load between fabric elements. Two ISLs are sufficient to support the
bandwidth of both NT servers operating at peak load.
Upgrade the existing ISL —
Fabric element software, firmware, and
hardware can be upgraded to support a 2.125 Gbps bandwidth traffic load
between fabric elements. A 2.125 Gbps ISL is sufficient to support the
bandwidth of both NT servers operating at peak load.
Deliberately employ ISL oversubscription —
Real-world SANs are
expected to function well, even with oversubscribed ISLs. Device I/O is
typically bursty; few devices operate at peak load for a significant length of
time, and device loads seldom peak simultaneously. As a result, ISL
bandwidth is usually not fully allocated, even for an oversubscribed link. An
enterprise can realize significant cost savings by deliberately designing a SAN
with oversubscribed ISLs that provide connectivity for noncritical
applications.
Device Locality
Devices that communicate with each other through the same director or switch
have
high locality
. Devices that must communicate with each other through one or
more ISLs have
low localit
y. Part (A) of
Figure 42
illustrates high device locality
with little ISL traffic. Part (B) of
Figure 42
illustrates low device locality.