HP Surestore 64 HP Enterprise Connectivity Fabric Manager User's Guide - Page 82

Merging Zoned Fabrics, Rules for Merging Zoned Fabrics

Page 82 highlights

Merging Zoned Fabrics Managed products are linked through ISLs to form multiswitch fabrics. In a multiswitch fabric, the active zoning configuration applies to the entire fabric. Any change to the configuration applies to all switches in the fabric. When fabrics join through an ISL, adjacent managed products exchange active zone configurations and determine if the configurations are compatible and can merge. If the configurations can merge, the fabrics join. The resulting configuration will be a single zone set containing zone definitions from each fabric. If configurations cannot merge, the expansion ports (E_Ports) on each product become segmented. Segmented E_Ports cannot carry traffic from attached devices (class 2 or 3 traffic), but can carry management and control traffic (class F traffic) between managed products. Zoning configurations are compatible if the active zone names in each fabric are unique. If there are identical zone names in each fabric, then the zones must have identical members for the fabrics to join. Rules for Merging Zoned Fabrics Certain rules are enforced to ensure that zoning is consistent across the fabric. Table 2 on page 65 summarizes rules for joining two fabrics through an ISL. The the following terms are used in the table: • Not zoned No zone set is active in the fabric and the default zone is enabled. In other words, all devices in the fabric are visible to all other devices in the fabric. • Zoned A zone set is active in the fabric and/or the default zone is disabled. In this case, devices can discover other devices that are members of the same zone. 64 Merging Zoned Fabrics

  • 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

64
Merging Zoned Fabrics
Merging Zoned Fabrics
Managed products are linked through ISLs to form multiswitch fabrics. In a multiswitch
fabric, the active zoning configuration applies to the entire fabric. Any change to the
configuration applies to all switches in the fabric.
When fabrics join through an ISL, adjacent managed products exchange active zone
configurations and determine if the configurations are compatible and can merge. If the
configurations can merge, the fabrics join. The resulting configuration will be a single zone
set containing zone definitions from each fabric.
If configurations cannot merge, the expansion ports (E_Ports) on each product become
segmented. Segmented E_Ports cannot carry traffic from attached devices (class 2 or 3
traffic), but can carry management and control traffic (class F traffic) between managed
products.
Zoning configurations are compatible if the active zone names in each fabric are unique. If
there are identical zone names in each fabric, then the zones must have identical members
for the fabrics to join.
Rules for Merging Zoned Fabrics
Certain rules are enforced to ensure that zoning is consistent across the fabric. Table 2 on
page 65 summarizes rules for joining two fabrics through an ISL. The the following terms
are used in the table:
Not zoned
No zone set is active in the fabric and the default zone is enabled. In other words, all
devices in the fabric are visible to all other devices in the fabric.
Zoned
A zone set is active in the fabric and/or the default zone is disabled. In this case,
devices can discover other devices that are members of the same zone.