HP Surestore 64 Planning Guide - Page 91

Load balancing, Table 2

Page 91 highlights

Table 2 ISL Transfer Rate Versus Fabric Port Availability (Two-Director Fabric) Number of ISLs ISL Data Transfer Rate Available Fabric Ports 1 1.0625 Gbps 126 2 2.1250 Gbps 124 3 3.1875 Gbps 122 4 4.2500 Gbps 120 5 5.3125 Gbps 118 6 6.3750 Gbps 116 7 7.4375 Gbps 114 8 8.5000 Gbps 112 • Load balancing Planning consideration must be given to the amount of data traffic expected through the fabric. Because the fabric automatically determines and uses the least cost (shortest) data transfer path between source and destination ports, some ISL connections may provide insufficient bandwidth while the bandwidth of other connections is unused. Fibre Channel frames are routed through fabric paths that implement the minimum possible hop count. For example, in Figure 19, all traffic between devices connected to director S1 and director S2 communicate directly through ISLs that connect the directors (one hop). No traffic is routed through director S3 (two hops). If heavy traffic between the devices is expected, multiple ISL connections should be configured to create multiple minimum-hop paths. With multiple paths, the directors balance the load by assigning traffic from different ports to different minimum-hop paths (ISLs). When balancing a load across multiple ISLs, the director attempts to avoid assigning multiple ports attached to a device to the same ISL. This minimizes the probability that failure of a single ISL will affect all paths to the device. However, because port assignments are made incrementally as devices log into the fabric and ISLs become available, optimal results are not guaranteed. Planning Considerations Multiswitch Fabric Support 77

  • 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

Multiswitch Fabric Support
77
Planning Considerations
Load balancing
Planning consideration must be given to the amount of data traffic expected through
the fabric. Because the fabric automatically determines and uses the least cost
(shortest) data transfer path between source and destination ports, some ISL
connections may provide insufficient bandwidth while the bandwidth of other
connections is unused.
Fibre Channel frames are routed through fabric paths that implement the minimum
possible hop count. For example, in Figure 19, all traffic between devices connected to
director
S
1
and director
S
2
communicate directly through ISLs that connect the
directors (one hop). No traffic is routed through director
S
3
(two hops). If heavy traffic
between the devices is expected, multiple ISL connections should be configured to
create multiple minimum-hop paths. With multiple paths, the directors balance the
load by assigning traffic from different ports to different minimum-hop paths (ISLs).
When balancing a load across multiple ISLs, the director attempts to avoid assigning
multiple ports attached to a device to the same ISL. This minimizes the probability that
failure of a single ISL will affect all paths to the device. However, because port
assignments are made incrementally as devices log into the fabric and ISLs become
available, optimal results are not guaranteed.
Table 2
ISL Transfer Rate Versus Fabric Port Availability (Two-Director Fabric)
Number of ISLs
ISL Data Transfer Rate
Available Fabric Ports
1
1.0625 Gbps
126
2
2.1250 Gbps
124
3
3.1875 Gbps
122
4
4.2500 Gbps
120
5
5.3125 Gbps
118
6
6.3750 Gbps
116
7
7.4375 Gbps
114
8
8.5000 Gbps
112