Common issue here is - you have to make static routing on all switches and point where is default-network (default-gateway) - so on switch that has mgmt0 interface down - use "ip default-gateway X.I.T.Y" where IP is the one from IPFC subnet of the switch that has connectivity to external network.
On the interconnecting switch - default-gateway should point to external router IP - and router has to know (static route on router - and redistributed to any routing protocol you use) that network X.I.T.0/24 is accessible thru interface that MDS is connected to (static route with MDS external IP as next-hop).
and don't forget to enable "ip routing" on all MDS switches - and all switches should have vsanX with IP assigned from this same subnet.
Thanks. I'll double check the gateway and IP forwarding settings.
Although, It is currently possible to ping the VSAN 1 interfaces from each of the switches, so I'd guess the proper routing should be correct.
When selecting 'Fabrics' from the Logical Domain panel and viewing the 'Switches' information tab only the mgmt0 interfaces are listed for each switch. It would seem logical that a switch would have to be multi-homed for this to work correctly.
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...