It is probably best to zone based upon the pwwn of the devices that are attaching into the fabric. You can zone upon the FCID that is given to those devices but you better make sure that persistent FCID is enabled and the fcdomain is configured as static and is the same number as what is in the zoning info.
I'm not sure I'm following you here. The fcdomain is a number that is 1 byte long (1-239) and is the address of a vsan per switch. So, before vsans, it would have been the address of that switch. Zoning and zonesets are a different concept. You can think of zoning as access lists that permit devices access to each other. To zone, you use some designator to define those devices like pwwn, fcid, interface, etc. Between two switches with the same vsan, there must be a homogeneous zoneset whether that is acheived by merging or activating a zoneset in one switch to force it propogate to the other switch(s). Is it possible that you are referencing the CFS (Cisco Fabric Services) feature?
Introduction This article will help you understand the steps on how to
download the UCS licenses from the Cisco Systems website and then
installing it on the UCS. The redacted (blue lines) just covers up
certain numbers for privacy please do not take them...
Introduction This article will help you understand and educate the
customer on how to clear their "expired licenses"
(license-graceperiod-expired) from their UCS-M. If a customer just
purchased a license and needs a step by step guide on how to download
==================== VIC FNIC driver does not support Virtual Volumes (
second level LUN ID ) An enhancement request has been created to track
this feature - CSCux64473 UPDATE - 12-14-2016 We made some traction on
the enhancement request - The Fix is in t...