Ok. I would also suggest taking a step back and learn more about the ACI objects and their use. This document can also help get you started with how to design and use the ACI objects together.  https://www.cisco.com/c/en/us/solutions/collateral/data-center-virtualization/application-centric-infrastructure/white-paper-c11-737909.html   Typically, with any technology, VLANs from the Campus are not extended into the Datacenter, and that is no different here.    I would also suggest taking a look at these Cisco Live presentations: Introduction to ACI - BRKACI-1000 How to Setup an ACI Fabric from Scratch - BRKACI-2004 Your First 7 Days of ACI - BRKACI-1001   ... View more

At this point I'll have to take a step back and ask what is the goal of attaching the campus VLANs/subnets directly to ACI BDs/EPGs? Are you going to move the Campus Gateway into ACI? Is it simple for reachability to ACI subnets?   If it's just so the Campus can reach ACI subnets, you should just use the routed L3 External to exchange reachability with the routers/switches between campus and DC.    If you really want to connect the Campus VLANs into ACI, which I don't recommend unless you are migrating the Campus VLANs to ACI, you can map those VLANs over the same Trunk as the L3 external. They get mapped into the BD/EPG with a static path binding.    I recommend reading this doc: https://www.cisco.com/c/en/us/td/docs/switches/datacenter/aci/apic/sw/4-x/basic-configuration/Cisco-APIC-Basic-Configuration-Guide-411/Cisco-APIC-Basic-Configuration-Guide-411_chapter_0110.html ... View more

Hello! You have mostly the right Idea. What you should do is create 1 L3 External toward your DIL layer w/ OSPF. For the L3 out you would likely configure an SVI with the subnet you mention below this configures the fabric to start a routing protocol on the specified interfaces and exchange routes. You would then configure each VLAN you want to extend into ACI as separate EPGs/BDs. You would configure a static path under the EPG with the VLAN encapsulation of the VLAN on the external Switch.    Hopefully that helps point you in the right direction.  ... View more

I'm not sure if there is any publicly available document that details this kind of testing, usually it is pretty specific to the implementation and focuses on the Endpoints and applications that are deployed in the environment.    This document might help you check into if best practices are being used: https://unofficialaciguide.com/2018/11/29/aci-best-practice-configurations/   Checking Faults is a great to ensure that everything has deployed ok.   And if you mean after a change or upgrade, the ACI Appcenter App StateChangeChecker is a great tool to check the state of objects in the fabric before and after the change.    https://dcappcenter.cisco.com/statechangechecker-2-2-1n.html     ... View more

You could enable GARP based detection on the BD under the L3 Configurations, like the other poster mentioned. You did mention that the EPs GARP when they failover. Is it possible to test with a single ESX host prior to the upgrade? I would also say to use the ACI App Enhanced Endpoint Tracker to get a better idea of what's happening with the EPs during the failover and when they time out, etc.  ... View more

Hello!  Firstly, if this was an urgent issue or if it was due to a bug that it's best to open a TAC case to determine root cause so that we can track the reason in our system and possibly fix if needed.   Secondly, can you show all the settings on the BD? A screenshot of both the Policy > General, and Policy > L3 Configurations tabs.    You are right, in Non ACI, these packets should be flooded. In ACI, with the correct bridge domain settings, ACI will also flood, end to end with no proxying, across all ports that are up and in the BD, essentially removing any special behavior.   Are both of these hosts configured in the same EPG? If so, can you please post the configuration of the EPG(s) as well. What was the hosts behavior at this point? Were you able to still access the ESX host or NetApp host through an OOB to see their failover was working properly? What is the configuration of the host failover configuration since you mention that they are not in a vPC. Did you see any faults or anything for the IP or MAC associated with the EP? Did you see if the EPs still showed up in their expected EPG(s)? ... View more

Hello! Can you please check that your multicast configuration is correct on the IPN? This is a typical reason for being unable to ping. Please verify you see the correct groups on the IPN. You can also try to use the troubleshooting wizard between these two EPs.      ... View more

Hello!    No CIMC connected on the other APICs is not the end of the world, although we would recommend having them connected long term, console should be enough for bringing them up, same with Ethernet.   The only thing I can see might be that the difference between APIC version and Switch version may be too great to bring them up and bootstrap them? Are all of the Leaf/Spine switches running the same version of software?    The APIC is running 4.0(2c)? 14. is not a valid APIC version. Can you put the whole version string from the switch? ... View more

If this is the case I would suggest opening a TAC case. ... View more

This is normal, You have to add policies for Nodes 1, 2, and 3 manually to the mgmt tenant. You can also change the addresses by adding a policy with a different IP address.  ... View more