There are number of reasons that a VSAN will become segmented. From what you have reported, I would venture to guess that you have a 'zone merge failure'. When a VSAN tries to activate over an ISL or a trunk port, it will try to merge the zonesets active on each segment of the VSAN, into one single zoneset for the merged VSAN. One reason that would cause a zone merge failure is that the same zone name is in use in each segment, but not containing the exact same members. IE: zone name HOST-A-DISK-B has pwwn 111 and 222 in one segment, while the zone name HOST-A-DISK-B has pwwn 111 and 333 in the other segment.
If you issue the command 'show port x/y internal info' for the ISL or TE port that is isolated, it should tell you the cause of the VSAN segmentation.
Why do you need native HA: The native HA feature allows two Cisco DCNM
appliances to run as active and standby applications, with their
embedded databases synchronized in real time. Therefore, when the active
DCNM is not functioning, the standby DCNM will...
This document will provide screenshots to outline the steps to setup
TACACS+ configuration to ACI and also the configuration required on
Cisco ACS server. Please find the official Cisco guide for configuring
TACACS+ Authentication to ACI:
Is it supported or NOT supported? It's a frequently asked question.
Before APIC, release 2.3(1f), transit routing was not supported within a
single L3Out profile. In APIC, release 2.3(1f) and later, you can
configure transit routing with a single L3Out pr...