Configured domain ID: 0x00(0) (preferred) <<--- is this normal for a principal switch
I recently extended a VSAN using an EISL by adding an new cisco MDS 9222i switch to an existing production MDS 9222i switch.
Before extending the VSAN , i configured the VSAN on the new switch with a higher priority (160) value and different static domain ID (160) to avoid any issues when connecting the two switches together and to ensure the production MDS switch was still the principal switch. Note that the production principal switch had a "preferred" domain id of 120, not a static one.
After the successful extesion of the VSAN across the EISL , i noticed that the domain id for the principal switch had changed to 0 (preferred) for the VSAN, The running config stil showed that the Current domain ID was 0x78(120).
IS THE "Configured domain ID: 0x00(0) (preferred) " THE NORMAL THING TO SEE ON A PRINCIPAL SWITCH after two switches have been connected together?
I expected the Configured domain ID ID = 0x78(120) ] to remain unchanged and the same valuefor both the running and startup config ?
Can some one please shed some light if this is normal or is there an issue
Thanks in advance
**************** below is the output of show fcdomain vsan x *************
Configured domain ID: 0x00(0) (preferred) <<<<<<<------ This domain id changed to 0x00(0) (preferred) from 0x78(120)(preferred) after i successfully extended the VSAN onto another identical switch. Is this normal??? I did not in any way manually change this domain ID. Can i change the configured domain id back to 120 (preferred) without an impact?
Configured domain ID: 0x00(0) (preferred) <<--- is this nor
I didnt change the domain ID on the principal switch. It changed it self to 0 (preferred) from a value of 120 (preferred), after i added an indentical switch switch into the fabric.
This is why i am puzzled with this value and i dont know fi this is a normal thing to change the Domain ID value to 0 (preferred) on all the principal switches in NX-OS once you have a VSAN which extends over multiple switches (core-edge switch configuration) ?
The running value of the ID is still 120, so i want to change the configured value back to 120 as well, but i dont know if this is a correct thing to do or not.
Topology & Design:
Two ACI fabrics
Stretching VLANs using OTV
Both fabrics are advertising BD subnets into same routing domain
Some BDs(or say VLANs) are stretched, but some are not.
Endpoints can move betwee...
VMware Trunk Port Group is supported from ACI version 2.1
VMM integration must be configured properly
ASA device package must be uploaded to APIC
ASAv version must be compatible with ACI and device package version
Topology &Design:Traffic flow within same fabric:Endpoint moves to Fabric-2Bounce Entry Times OutTraffic Black-holedSummarySolutionAppendix:
In the Previous articles of ACI Automation, we are using Postman/Newman a...