creating new vsan and assigning switch to multiple vsans, segmented

Hi Ericlam,

looks like you have that VSAN ID alredy assigned in fabric B.
I would try to give some different VSAN name and see if it works.

Here is what I found from Cisco Web.

Autonomous Fabric ID
The autonomous fabric ID (AFID) distinguishes segmented VSANS (that is, two VSANs that are logically and physically separate but have the same VSAN number). Cisco MDS SAN-OS supports AFIDs from 1 through 64. AFIDs are used in conjunction with auto mode to allow segmented VSANS in the IVR VSAN topology database. You can configure up to 64 AFIDs.

The AFID can be configured individually for each switch and list of VSANs, or the default AFID can be configured for each switch

You don't add a whole switch to a certain VSAN. Only ports can be assigned to a VSAN.

Segmented VSAN's are shown when for example VSAN2 in switch 1 cannot communicate with VSAN2 in switch 2. If you create an ISL or portchannel between the switches and allow VSAN2 over that link (by default all VSAN's are allowed), the segmentation will be gone and both fabrics (VSAN's) will merge.

RRR-
You don't add a whole switch to a certain VSAN. Only ports can be assigned to a VSAN

Correct me if I'm wrong but Initially we add switches to VSAN and then divert ports to specific VSANs, right?
Even when you create New VSAN from FM it asks for switches participating in that VSAN.

The problem is because there's a domain ids conflict. Manually reassigning the domain ids fix the segment issue.

Yes, when you create a new VSAN, it will ask you what switch to assign the VSAN to. You can also assign the port to the new VSAN or leave it empty during the initial VSAN creation.