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

Zone aliases, Zone configurations, 00:00:80:33:3f:aa:11, SRV_MAILSERVER_SLT5, BACKUP_A, RECOVERY_2

Page 180 highlights

WWNs are specified as 8-byte (16-digit) hexadecimal numbers, separated by colons, for example, 10:00:00:90:69:00:00:8a. When a node name specifies a zone object, all ports on such a device are in the zone. When a port name specifies a zone object, only the single port is in the zone. The types of zone objects used to define a zone can be mixed and matched. For example, a zone defined with the zone objects 2,12; 2,14; 10:00:00:80:33:3f:aa:11 contains the devices connected to domain 2, ports 12 and 14, and a device with the WWN (either node name or port name) 10:00:00:80:33:3f:aa:11 that is connected on the fabric. Zone aliases A zone alias is a name assigned to a device or a group of devices. By creating an alias, you can assign a familiar name to a device or group multiple devices into a single name. This simplifies cumbersome data entry and allows an intuitive naming structure (such as using NT_Hosts to define all NT hosts in the fabric). Zone aliases also simplify repetitive entry of zone objects, such as port numbers or a WWN. For example, you can use the name Eng as an alias for 10:00:00:80:33:3f:aa:11. A useful convention is to name zones for the initiator they contain. For example, if you use the alias SRV_MAILSERVER_SLT5 to designate a mail server in PCI slot 5, the alias for the associated zone is ZNE_MAILSERVER_SLT5. This clearly identifies the server HBA associated with the zone. Zone configuration naming is more flexible. One configuration should be named PROD_fabricname, where fabricname is the name that the fabric has been designated. The purpose of the PROD configuration is to easily identify the configuration that can be implemented and provide the most generic services. If other configurations are used for specialized purposes, names such as BACKUP_A, RECOVERY_2, and TEST_18jun02 can be used. Zone configurations A zone configuration is a group of one or more zones. A zone can be included in more than one zone configuration. When a zone configuration is in effect, all zones that are members of that configuration are in effect. The different types of zone configurations are: • Defined configuration: The complete set of all zone objects defined in the fabric. • Effective configuration: A single zone configuration that is currently in effect. The effective configuration is built when an administrator enables a specified zone configuration. • Saved configuration: A copy of the defined configuration plus the name of the effective configuration, which is saved in flash memory by the cfgSave command. (You can also use the configUpload command to provide a backup of the zoning configuration and the configDownload command to restore the zoning configuration.) There might be differences between the saved configuration and the defined configuration if the system administrator has modified any of the zone definitions and has not saved the configuration. • Disabled configuration: The effective configuration is removed from flash memory. On power-up, the switch reloads the saved configuration. If a configuration was active when it was saved, the same configuration is reinstated on the local switch with an autorun of the cfgEnable command. You can establish a zone by identifying zone objects using one or more of the following zoning schemes: • Domain, port number level: All members are specified by domain ID, port number, or domain, area number pair or aliases, described in "Zone aliases" on page 180. • WWN level: All members are specified only by WWNs or aliases of WWNs. They can be node or port versions of the WWN. • Mixed zoning: A zone containing members specified by a combination of domain, port number, and/or domain, area number and WWN. 180 Administering advanced zoning

  • 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

180
Administering advanced zoning
WWNs are specified as 8-byte (16-digit) hexadecimal numbers, separated by colons, for example,
10:00:00:90:69:00:00:8a. When a node name specifies a zone object, all ports on such a device are
in the zone. When a port name specifies a zone object, only the single port is in the zone.
The types of zone objects used to define a zone can be mixed and matched. For example, a zone defined
with the zone objects 2,12; 2,14; 10:00:00:80:33:3f:aa:11 contains the devices connected to domain
2, ports 12 and 14, and a device with the WWN (either node name or port name)
10:00:00:80:33:3f:aa:11 that is connected on the fabric.
Zone aliases
A
zone alias
is a name assigned to a device or a group of devices. By creating an alias, you can assign
a familiar name to a device or group multiple devices into a single name. This simplifies cumbersome
data entry and allows an intuitive naming structure (such as using NT_Hosts to define all NT hosts in the
fabric).
Zone aliases also simplify repetitive entry of zone objects, such as port numbers or a WWN. For
example, you can use the name
Eng
as an alias for
10:00:00:80:33:3f:aa:11
.
A useful convention is to name zones for the initiator they contain. For example, if you use the alias
SRV_MAILSERVER_SLT5
to designate a mail server in PCI slot 5, the alias for the associated zone is
ZNE_MAILSERVER_SLT5
. This clearly identifies the server HBA associated with the zone.
Zone configuration naming is more flexible. One configuration should be named
PROD_
fabricname
,
where
fabricname
is the name that the fabric has been designated. The purpose of the PROD
configuration is to easily identify the configuration that can be implemented and provide the most generic
services. If other configurations are used for specialized purposes, names such as
BACKUP_A
,
RECOVERY_2
, and
TEST_18jun02
can be used.
Zone configurations
A
zone configuration
is a group of one or more zones. A zone can be included in more than one zone
configuration. When a zone configuration is in effect, all zones that are members of that configuration
are in effect.
The different types of zone configurations are:
Defined configuration:
The complete set of all zone objects defined in the fabric.
Effective configuration:
A single zone configuration that is currently in effect. The effective
configuration is built when an administrator enables a specified zone configuration.
Saved configuration:
A copy of the defined configuration plus the name of the effective configuration,
which is saved in flash memory by the
cfgSave
command. (You can also use the
configUpload
command to provide a backup of the zoning configuration and the
configDownload
command to
restore the zoning configuration.) There might be differences between the saved configuration and the
defined configuration if the system administrator has modified any of the zone definitions and has not
saved the configuration.
Disabled configuration:
The effective configuration is removed from flash memory.
On power-up, the switch reloads the saved configuration. If a configuration was active when it was
saved, the same configuration is reinstated on the local switch with an autorun of the
cfgEnable
command.
You can establish a zone by identifying zone objects using one or more of the following zoning schemes:
Domain, port number level:
All members are specified by domain ID, port number, or domain, area
number pair or aliases, described in ”
Zone aliases
” on page 180.
WWN level:
All members are specified only by WWNs or aliases of WWNs. They can be node or
port versions of the WWN.
Mixed zoning:
A zone containing members specified by a combination of
domain
,
port number
,
and/or
domain
,
area number
and
WWN
.