I am fairly new to the world of FibreChannel, and recently discovered a gotcha when making changes to zoning configuration for one or more zones which are part of the active zoneset, which I will share with you now.
Updating the zone configuration
Below is a sample zone configuration for a Nexus switch, and we can see that we have two WWN’s in a zone, the zone is part of a zoneset, and that that zoneset has been activated.
1 2 3 4 5 6 7 8
Now, suppose that you make a change to that zone, or add another zone to the same zoneset; although the zoneset is already ‘active’, your changes wont be applied.
In order for our changes to be applied, we must re-activate the zoneset which, at first glance sounds like a disruptive operation. The
zoneset activate command is part of the running configuration, and to disable and re-apply such config items we typically negate the command (
no zoneset activate…) first and then re-apply it.
In this situation simply re-issuing the same command which is already in your running configuration will update the active zoneset in a non disruptive fashion. In my case I needed to configure zoning for a new server (Running ESXi) which needed access to VMWare datastores on the SAN.
I hope this helps somebody out as although I thought it must be possible to add new zones without causing downtime it was unclear at first.