FC Aliases Zoning passed on pWWN/WWPN is error-prone Zoning errors can be catastrophic to the fabric FC Aliases five user-friendly names to WWN's, FCID's etc. Similar to DNS in IP Locally significant Configured as fcalias name Can be advertised through Zoneset distribution zoneset distribute vsan 1 Configuration conf t fcalias name JBOD2_PORT2_DISK0 vsan 30 member pwwn 22:00:00:11:c6:58:83:2c or fcalias name SERVER3 vsan 30 member pwwn 21:00:00:1b:32:0b:2f:61 then issue the "show fcalias"  So now when you create a zone and zoneset it would look like this conf t zone name SERVER3_TO_JBOD2_PORT2_DISKS_0_1_2 vsan 30 (config-zone) member fcalias SERVER3 member fcalias JBOD2_PORT2_DISK0 member fcalias JBOD2_PORT2_DISK1 member fcalias JBOD2_PORT2_DISK2 zoneset name VSAN30 vsan 30 member SERVER3_TO_JBOD2_PORT2_DISKS_0_1_2 zoneset activate name VSAN30 vsan 30 If you configured the fcalias on MDS1 it will only be locally significant unless you zoneset distribute vsan 30 Basic vs. Enhanced Zoning By default the Full Zoneset is local and the active Zoneset is local and the Active Zoneset is fabric wide Order of of operations errors can corrupt the Active Zoneset Similar to VTRP deleting all Ethernet VLAN's Enhanced Zoning prevents this by LOCKING the fabric Ensures that no one accidentally overwrites each other changes to the fabric Using Enhanced Zoning Admin logs into any switch in the Fabric and starts to configure Zoning Lock is advertised to all switches in the Fabric Other admins cannot edit Zoneset until lock is released Lock is released by committing the Zoneset Can clear the lock form another switch with: clear zone lock vsan # Configured with: zone mode enhanced vsan # system default zone mode enhanced This is configured per vsan, so if you have an legacy device that cannot support enhanced zoning you can leave it on basic for the particular VSAN FC Aliases Can be distributed through manual Zoneset distribution Still prone to becoming unsynchronized through the fabric Device Aliases Solve the issue with the FC aliases not being manually distributed Server the same purpose as the FC Aliases Bind pWWN/WWPN to a user-friendly name Binding is advertised out to the Fabric Using Device Aliases Device Aliases are advertised like Enhanced Zoning Device Alias session is created and "lock" is advertised to the fabric Changes are made and "committed" Aliases are advertised through CFS (Cisco Fabric Services) and lock is removed Configured with: device-alias database Topology  Conf t zone mode enhanced vsan 10 ( it will ask you if you want to do this yes/no) zone mode enhanced vsan 20 device-alias database (config-device-alias-db) device-alias name SERVER2_SANA pwwn 21:00:00:1b:32:07:32:23 you would know do this for all other device alias's device-alias commit You can go to any other switch and look at the "show device-alias database"  show cfs applications  You wold now have to do this for the SAN B on MDS2 N5K2 conf tzone mode enhanced vsan 20 device-alias database (config-device-alias-db) device-alias name SERVER2_SANA 21:00:00:1b:32:07:32:23 device-alias name SERVER2_SANB 21:01:00:1b:32:27:32:23  show fcns database vsan 20  create the zone and zoneset zone name SERVER2 vsan 20 member device_alias SERVER2_SANB member device_alias JBOD_PORT1_DISK13 member device_alias JBOD_PORT1_DISK14 member device_alias JBOD_PORT1_DISK15 exit zoneset name VSAN20 vsan 20 member SERVER2 exit zoneset activate name VSAN20 vsan 20 zone commit vsan 20 Before you commit you can also do the "show zone pending" or "show zoneset pending" to see what changes will move from the full to the active zoneset and advertised via CFS through the Fabric. Steps
|
Blog >