HP Surestore 64 Planning Guide - Page 94

Path selection, Frame delivery order, connected to an ISL. For example

Page 94 highlights

• Path selection Directors are not manually configured with data transmission paths to each other. Participating directors automatically exchange information to determine the fabric topology and resulting minimum-hop data transfer paths through the fabric. These paths route Fibre Channel frames between devices attached to the fabric and enable operation of the fabric services firmware on each director. Paths are determined when the fabric topology is determined, and remain static as long as the fabric does not change. If the fabric topology changes (directors are added or removed or ISLs are added or removed), directors detect the change and define new data transfer paths as required. The algorithm that determines data transfer paths is distributive and does not rely on the principal switch to operate. Each director calculates its own optimal paths in relation to other directors. Only minimum-hop data transfer paths route frames between devices. If an ISL in a minimum-hop path fails, directors calculate a new least-cost path (which may include more hops) and route Fibre Channel frames over that new path. Conversely, if the failed ISL is restored, directors detect the original minimum-hop path and route Fibre Channel frames over that path. When multiple minimum-hop paths (ISLs) between directors are detected, the switch firmware balances the data transfer load and assigns ISL as follows: - The director assigns an equal number of device entry ports (F_Ports) to each E_Port connected to an ISL. For example, if a director has two ISLs and six attached devices, the load from three devices is transferred through each ISL. - If a single device has multiple F_Port connections to a director, the switch assigns the data transfer load across multiple ISLs to maximize device availability. • Frame delivery order When directors calculate a new least-cost data transfer path through a fabric, routing tables immediately implement that path. This may result in Fibre Channel frames being delivered to a destination device out of order, because frames transmitted over the new (shorter) path may arrive ahead of previously-transmitted frames that traverse the old (longer) path. This can cause problems because many Fibre Channel devices cannot receive frames in the incorrect order. 80 Multiswitch Fabric Support

  • 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

80
Multiswitch Fabric Support
Path selection
Directors are not manually configured with data transmission paths to each other.
Participating directors automatically exchange information to determine the fabric
topology and resulting minimum-hop data transfer paths through the fabric. These
paths route Fibre Channel frames between devices attached to the fabric and enable
operation of the fabric services firmware on each director.
Paths are determined when the fabric topology is determined, and remain static as long
as the fabric does not change. If the fabric topology changes (directors are added or
removed or ISLs are added or removed), directors detect the change and define new
data transfer paths as required. The algorithm that determines data transfer paths is
distributive and does not rely on the principal switch to operate. Each director
calculates its own optimal paths in relation to other directors.
Only minimum-hop data transfer paths route frames between devices. If an ISL in a
minimum-hop path fails, directors calculate a new least-cost path (which may include
more hops) and route Fibre Channel frames over that new path. Conversely, if the
failed ISL is restored, directors detect the original minimum-hop path and route Fibre
Channel frames over that path.
When multiple minimum-hop paths (ISLs) between directors are detected, the switch
firmware balances the data transfer load and assigns ISL as follows:
The director assigns an equal number of device entry ports (F_Ports) to each E_Port
connected to an ISL. For example, if a director has two ISLs and six attached
devices, the load from three devices is transferred through each ISL.
If a single device has multiple F_Port connections to a director, the switch assigns
the data transfer load across multiple ISLs to maximize device availability.
Frame delivery order
When directors calculate a new least-cost data transfer path through a fabric, routing
tables immediately implement that path. This may result in Fibre Channel frames being
delivered to a destination device out of order, because frames transmitted over the new
(shorter) path may arrive ahead of previously-transmitted frames that traverse the old
(longer) path. This can cause problems because many Fibre Channel devices cannot
receive frames in the incorrect order.