Cisco ACI Overview 

Thank you !

I appreciate that!

Glad it helped!

Glad to hear that!

Thanks !

Thanks !

Thank you !

Thank you sir !

You're welcome!

thank you !

Glad it was helpful!

you are welcome

Thanks!

Glad you liked it

Thank you sir !

Not exactly. APIC must be connected to 2 different leafs for redundancy and performance. You don't have to connect it to every leaf in your fabric

Nope, in case with ACI vPC control plane goes via spines hence even if you pair leaf101 and leaf102 into vPC domain you don't need to connect them physically

The whole point of vxlan evpn aci is to boot out peerlinks

If we are talking about APIC controllers than we are doing it for both redundancy and performance. If we are talking about regular servers than we can attach them with just a single cable to one leaf, with a portchannel or with a vPC.

Well, let's at least define some boundaries. Setting up vSphere (ESXi and vCenter) has nothing to do with ACI. The same is with OpenStack and all its components. But you don't have to be an expert in virtualization to configure integration between ACI and VMware or OpenStack or Hyper-V

Correct, thank you

I'm not sure about your particular example, but if you have 2 spines with all ports occupied and you add third spine it DOES help you to scale your fabric and add more leaves which implies more host-facing ports.

@@SneakySubnet In this very video when you run out of ports on the two existing spines, you add a third one and then add a new leaf and connect it to first two spines (that are supposedly out of ports). If you want more host-facing ports you need more leaves. More leaves -> more ports taken on existing spines. No more ports on spines -> add another new spines (that the existing leaves won't connect to) and connect them to the existing spines by adding another layer to the fabric.

@@metallicat20 Example in this video is more abstract. In heavily populated fabrics there are more than 1 connection between each spine and each leaf. So you either do re-cabling (redistribute physical links between 3 spines instead of 2) or plan for growth wisely and add new spine before you run out of ports.

You should use PBR www.cisco.com/c/en/us/solutions/collateral/data-center-virtualization/application-centric-infrastructure/white-paper-c11-739971.html

@@SneakySubnet no pbr is for specify a route to be used specifically instead of default routing table...

@@SneakySubnet the only way you can prevent 2 devices to communication in the same subnet with traditional network is using private vlan there is no need of firewall..

You can find scalability limits here www.cisco.com/c/en/us/td/docs/switches/datacenter/aci/apic/sw/5-x/verified-scalability/cisco-aci-verified-scalability-guide-501.html I don't think that there is a limit in terms of number of bare-metal servers connected to leafs.

Thank you for quick reply. I. Your demonstration you had L1 with up address 10.10.10.10/24 and L2 was 10.10.10.20/24 That is why I asked with subnet being the same only 8-9 servers would be capable to connecting to L1 not sure for L2 being their are only 256 up addresses per subnet or router.

ACI uses Anycast Gateway (or Pervasive Gateway). Basically it means that every leaf in your fabric may deploy SVI with the same IP address hence you can stretch your broadcast domain throughout the whole fabric. Servers in the same subnet (e.g. 10.10.10.0/24) may reside behind any leaf and every leaf will serve as Default Gateway for them.

Sorry, but I can't do that

Hello ! Of course you can, check out L2 Out functionality. And you can connect FEXes to ACI as well

yes you can