Академический Документы
Профессиональный Документы
Культура Документы
Share:
Detailed Information
What is Zone?
Zone Types:
1.
This zone allows the devices connected to the ports to communicate with each other. The
change of the device will not affect the zoning configuration. So you do not need to make
any change to the zone configuration after replacing the host HBA card.
2.
WWPN/WWNN zone
This zone allows the devices who have the specified WWN to communicate with each other.
It does not care the devices connect to which ports. Once the device moves to another port,
there is no need to change the zone configuration. If the switch is connected NPIV devices,
WWN zone is required.
3.
When a device uses D, P and WWN zones in two or more zones, the device will
get into the mixed zone mode. In a mixed zone mode, the commutation relies on
switch CPUs software validation.
4.
LSAN zone
LSAN zone is only used when enabled FCR (Fibre Channel Routing). It allows the devices
in different fabrics to communicate via the FC router. You must install Integrated Routing
license to enable this feature.
5.
TI zone can specify one or more ISL (Inter Switch Link) dedicated for a zone, without any
license.
6.
QoS zone indicates the priority of the traffic flow between a given host/target pair. You must
install Adaptive Networking license to enable this feature.
Zoneset is a collection of zones. You can only enable one zoneset on a switch. All the active
zonesets in one fabric must be consistent, or it would lead to a fabric segment problem.
Alias is to simplify the zoning configuration. For each device, you can setup the alias in
advance, then use these alias to replace the D, P and WWN during the setup.
Both Cisco and Brocade switches have the default zones. It allows all the connected device
to communicate with each other if there is no zone configured.
1.
Brocade CLI:
First create the alias for each zone, then create the zone and add the alias, create cfg
(zoneset) and add the zones, finally enable the cfg.
Help manual:
zonehelp
Displays the current configuration:
cfgshow
Create/add, remove members/delete alias:
alicreate "aliName","member[; member...]"
aliadd "aliName","member[; member...]"
aliremove "aliName","member[; member...]"
alidelete "aliName"
Create/add, remove members/delete zone:
2.
Brocade GUI:
Open WebTools and click Zone Admin, then go to the Zone Admin page.
For V6.x.x version:
Create alias:
3.
Cisco CLI:
The biggest difference between Cisco and Brocade switches is VSAN. Each VSAN can
have its own zone and zoneset. Another one is enhanced zone and basic zone.
The enhanced zone will create a session once the user tries to change the zone
configuration, to prevent other users from changing the same configuration. Once enabled
enhanced zone, you must commit the changes and close the session before the new
configuration takes effect.
The enhanced zone will automatically turn on the broadcasting zone. For MDS 9500
series, you must disable the broadcasting zone before enable the fourth-generation network
interface module.
show commands:
# show fcalias vsan x
# show zoneset vsan x
# show active zoneset vsan x
# show zone status vsan x
Enable enhanced zone:
# configure terminal
4.
Open GUI then click Edit Local Full Zone Database in the zone menu.
Edit zone:
Look for the corresponding WWN or device alias, click Add to Zone to add them to the zone
1)
Port zone ensures the security by physical isolation, but WWN zone can allow the
specify device to access the zone.
2)
3)
Only WWN zone can be used in IVR/FCR and tape acceleration products.
2.
Zoning takes effect in SAN switches while LUN masking does the job in storage.
3.
4.
There is a bug in v6.4.3 version which could make the host automatically logged out from
the storage.
5.
This can prevent losing the zone configuration when multiple users change it.
6.
For MDS switches running in NX-OS post 5.2(6), we recommend to use smart zoning. Smart
Zoning combines the benefits of both approaches above:
Simplicity of operational management with a Single Zone for all initiators and targets of an
application or cluster.
No wasted switch resources as with two member zones.
Translator Roger
using fcalias is not the best practices, device aliases is. Also please consider talking about
SmartZoning as that negates some of the best practices your provided above.
Hi dynamox,
Thanks for reading the blog carefully and raising your opinion.
We are aware that device alias is a fabric wide feature and more convenient than fcalias.
However, considering multiple bugs for device alias found in NX-OS v5.x working with
DCNM, we still recommend our customer to use fcalias.
Smart zoning is a new feature introduced in 5.2(6) which saves a lot of time for SAN
administrators to configure zoning.
We encourage customer to use this feature and have added some recommend into this
article.
can you please point me to Cisco bug reports about device-aliases. We have been using
devices aliases for at least 3 years and i have yet to find any issues.
Thanks
Hi Dynamox,
CSCtt20652 - DCNM SAN: Device Alias CFS Regions column does not sort
Affecting: 5.2.1
Fixed in: 6.2(0.18)S0
CSCuc04839 - Device-alias instead of fcalias in the document under DCNM control panel
Affecting: 5.2(7.9)
Fixed in: Release Pending
majority of those are bugs in really old 5.2.x branch of NX-OS. Folks should be on the latest
5.2.8 if only for the reason to address ShellShock vulnerabilities on NX-OS. These should
not be a deterrent from using device aliases. Being able to see server name when you
create IVR zones, when you run sh flogi database and others is just too great of an feature
to be not considered.