HP StorageWorks 2/16V Brocade Web Tools Administrator's Guide (53-0000194-01, - Page 130

User-Defined Admin Domains, System-Defined Admin Domains

Page 130 highlights

8 User-Defined Admin Domains AD1 through AD254 are user-defined Admin Domains. These user-defined Admin Domains can be created only by a physical fabric administrator in AD255. System-Defined Admin Domains AD0 and AD255 are special Admin Domains and are present in every AD-capable fabric. AD0 AD0 is a system-defined Admin Domain that, in addition to containing members you explicitly added (similar to user-defined Admin Domains), it contains all online devices, switches, and switch ports that have not been assigned to any user-defined Admin Domain. AD0 also implicitly contains all devices from switches running Fabric OS versions earlier than 5.2.0, as they can never be part of an Admin Domain unless and until they are upgraded to v5.2.0. Unlike user-defined Admin Domains, AD0 has an automatic and a fixed membership list. User-defined Admin Domains have only fixed members. • Automatic membership list-Contains all devices and switches that have not been assigned to any other Admin Domain. • Fixed membership list-Contains all devices and switches that you explicitly add to AD0 and can be used to force device and switch sharing between AD0 and other Admin Domains. The Switch Admin module displays the fixed members and not the automatic members, you can use the View menu to display a list of the automatic members. AD0 can be managed like any user-defined Admin Domain. The only difference between AD0 and user-defined Admin Domains is the automatic membership list. In filtered views, the automatic members of AD0 are considered direct members. The automatic members of AD0 change dynamically as the membership of other Admin Domains changes. The fixed members of AD0 are not deleted unless you explicitly remove them. For example, if you explicitly add DeviceA to AD0 and it is not a member of any other Admin Domain, then DeviceA is both an automatic and a fixed member of AD0. If you add DeviceA to AD2, then DeviceA is deleted from the AD0 automatic membership list, but is not deleted from the AD0 fixed membership list. If you then remove DeviceA from AD2, DeviceA is added back to the AD0 automatic membership list (assuming DeviceA is not in any other Admin Domains). AD0 is useful if you want to share its zone database (called "root zone database") with a legacy fabric. 8-2 Web Tools Administrator's Guide Publication Number: 53-0000194-01

  • 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
  • 249
  • 250
  • 251
  • 252
  • 253
  • 254
  • 255
  • 256
  • 257
  • 258
  • 259
  • 260
  • 261
  • 262
  • 263
  • 264
  • 265
  • 266
  • 267
  • 268
  • 269
  • 270
  • 271
  • 272
  • 273
  • 274
  • 275
  • 276
  • 277
  • 278
  • 279
  • 280
  • 281
  • 282
  • 283
  • 284
  • 285
  • 286
  • 287
  • 288
  • 289
  • 290
  • 291
  • 292
  • 293
  • 294
  • 295
  • 296
  • 297
  • 298
  • 299
  • 300
  • 301
  • 302
  • 303
  • 304
  • 305
  • 306
  • 307
  • 308

8-2
Web Tools Administrator’s Guide
Publication Number: 53-0000194-01
8
User-Defined Admin Domains
AD1 through AD254 are user-defined Admin Domains. These user-defined Admin Domains can be
created only by a physical fabric administrator in AD255.
System-Defined Admin Domains
AD0 and AD255 are special Admin Domains and are present in every AD-capable fabric.
AD0
AD0 is a system-defined Admin Domain that, in addition to containing members you explicitly added
(similar to user-defined Admin Domains), it contains all online devices, switches, and switch ports that
have not been assigned to any user-defined Admin Domain.
AD0 also implicitly contains all devices from switches running Fabric OS versions earlier than 5.2.0, as
they can never be part of an Admin Domain unless and until they are upgraded to v5.2.0.
Unlike user-defined Admin Domains, AD0 has an automatic and a fixed membership list. User-defined
Admin Domains have only fixed members.
Automatic membership list—Contains all devices and switches that have not been assigned to any
other Admin Domain.
Fixed membership list—Contains all devices and switches that you explicitly add to AD0 and can
be used to force device and switch sharing between AD0 and other Admin Domains.
The Switch Admin module displays the fixed members and not the automatic members, you can use the
View menu to display a list of the automatic members.
AD0 can be managed like any user-defined Admin Domain. The only difference between AD0 and
user-defined Admin Domains is the automatic membership list.
In filtered views, the automatic members of AD0 are considered direct members.
The automatic members of AD0 change dynamically as the membership of other Admin Domains
changes. The fixed members of AD0 are not deleted unless you explicitly remove them.
For example, if you explicitly add DeviceA to AD0 and it is not a member of any other Admin Domain,
then DeviceA is both an automatic and a fixed member of AD0. If you add DeviceA to AD2, then
DeviceA is deleted from the AD0 automatic membership list, but is
not
deleted from the AD0 fixed
membership list. If you then remove DeviceA from AD2, DeviceA is added back to the AD0 automatic
membership list (assuming DeviceA is not in any other Admin Domains).
AD0 is useful if you want to share its zone database (called “root zone database”) with a legacy fabric.