HP StorageWorks 2/16V HP StorageWorks Fabric OS 5.X Procedures User Guide (AA- - Page 189

Table 36 Resulting database size: 0 to 96K, Table 36

Page 189 highlights

Symmetrical segmentation occurs when both ends of an ISL are shut down. Subsequently, no frames are exchanged between the two switches. Asymemetrical segmentation not only prevents frames from being exchanged between switches, but also causes routing inconsistencies. The best way to avoid either type of segmentation is to know the zone database size limit of adjacent switches. Table 36 through Table 39 provide the expected behavior based on different database sizes after a zone merge is specified. Table 36 Resulting database size: 0 to 96K Receiver J Initiator L FOS 2.6 FOS 3.1 FOS 3.2 FOS 4.0, 4.1, 4.2 FOS 2.6, 3.1 Join Join Join Join FOS 3.2 Join Join Join Join FOS 4.0, 4.1, Join Join Join Join 4.1 FOS 4.3, 4.4.0 Join Join Join Join FOS 5.5.0, 5.0.1 Join Join Join Join Fibre Channel Join Join Join Join Router XPath 7.3 Join Join Join Join FOS 4.3, FOS 5.5.0, 4.4.0 5.0.1 Join Join Join Join Join Join Fibre Channel Router Join Join Join XPath 7.3 Join Join Join Join Join Join Join Join Join Join Join Join Join Join Join Join Join Join Join Table 37 Resulting database size: 96K to 128K Receiver J FOS 2.6 FOS 3.1 FOS 3.2 Initiator L FOS 4.0, 4.1, 4.2 FOS 2.6, 3.1 Segment FOS 3.2 Segment FOS 4.0, 4.1, 4.1 Segment FOS 4.3, 4.4.0 Segment FOS 5.5.0, 5.0.1 Segment Fibre Channel Join Router XPath 7.3 Segment Segment Segment Segment Segment Segment Join Segment Segment Join Segment Join Join Join Segment Segment Join Join Join Join Join Join FOS 4.3, FOS 5.5.0, 4.4.0 5.0.1 Segment Join Join Segment Join Join Fibre Channel Router Join Join Join XPath 7.3 Segment Join Join Join Join Join Join Join Join Join Join Join Join Join Join Join Join Join Join Fabric OS 5.x administrator guide 189

  • 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
  • 186
  • 187
  • 188
  • 189
  • 190
  • 191
  • 192
  • 193
  • 194
  • 195
  • 196
  • 197
  • 198
  • 199
  • 200
  • 201
  • 202
  • 203
  • 204
  • 205
  • 206
  • 207
  • 208
  • 209
  • 210
  • 211
  • 212
  • 213
  • 214
  • 215
  • 216
  • 217
  • 218
  • 219
  • 220
  • 221
  • 222
  • 223
  • 224
  • 225
  • 226
  • 227
  • 228
  • 229
  • 230
  • 231
  • 232
  • 233
  • 234
  • 235
  • 236
  • 237
  • 238
  • 239
  • 240
  • 241
  • 242
  • 243
  • 244
  • 245
  • 246
  • 247
  • 248

Fabric OS 5.x administrator guide
189
Symmetrical segmentation occurs when both ends of an ISL are shut down. Subsequently, no frames are
exchanged between the two switches.
Asymemetrical segmentation not only prevents frames from being exchanged between switches, but also
causes routing inconsistencies.
The best way to avoid either type of segmentation is to know the zone database size limit of adjacent
switches.
Table 36
through
Table 39
provide the expected behavior based on different database sizes
after a zone merge is specified.
Table 37
Resulting database size: 96K to 128K
Table 36
Resulting database size: 0 to 96K
Receiver
FOS 2.6
FOS 3.1
FOS 3.2
FOS 4.0,
4.1, 4.2
FOS 4.3,
4.4.0
FOS 5.5.0,
5.0.1
Fibre
Channel
Router
XPath
7.3
Initiator
FOS 2.6, 3.1
Join
Join
Join
Join
Join
Join
Join
Join
FOS 3.2
Join
Join
Join
Join
Join
Join
Join
Join
FOS 4.0, 4.1,
4.1
Join
Join
Join
Join
Join
Join
Join
Join
FOS 4.3, 4.4.0
Join
Join
Join
Join
Join
Join
Join
Join
FOS 5.5.0, 5.0.1
Join
Join
Join
Join
Join
Join
Join
Join
Fibre Channel
Router
Join
Join
Join
Join
Join
Join
Join
Join
XPath 7.3
Join
Join
Join
Join
Join
Join
Join
Join
Receiver
FOS 2.6
FOS 3.1
FOS 3.2
FOS 4.0,
4.1, 4.2
FOS 4.3,
4.4.0
FOS 5.5.0,
5.0.1
Fibre
Channel
Router
XPath
7.3
Initiator
FOS 2.6, 3.1
Segment
Segment
Segment
Segment
Segment
Segment
Join
Segment
FOS 3.2
Segment
Segment
Join
Join
Join
Join
Join
Join
FOS 4.0, 4.1,
4.1
Segment
Segment
Segment
Join
Join
Join
Join
Join
FOS 4.3, 4.4.0
Segment
Segment
Join
Join
Join
Join
Join
Join
FOS 5.5.0, 5.0.1
Segment
Segment
Join
Join
Join
Join
Join
Join
Fibre Channel
Router
Join
Join
Join
Join
Join
Join
Join
Join
XPath 7.3
Segment
Segment
Segment
Join
Join
Join
Join
Join