This shows you the differences between two versions of the page.
| Next revision | Previous revision | ||
| virtualization:cloud:aci [2016/08/14 14:06] – created jotasandoku | virtualization:cloud:aci [2023/11/02 14:38] (current) – external edit 127.0.0.1 | ||
|---|---|---|---|
| Line 1: | Line 1: | ||
| **Cisco ACI**\\ | **Cisco ACI**\\ | ||
| + | VXLAN-EVPN explained: [[https:// | ||
| [[http:// | [[http:// | ||
| + | * VTEP: runs in the leaf swicthes. Distributed gateways (but same IP in all), all arp are in the leafs. | ||
| + | * | ||
| + | |||
| + | 2. It's automatically (I'd say randomly) chosen by the APIC | ||
| + | |||
| + | 3. The VTEP IP is automatically (again I'd say randomly) chosen from the pool of infrastructure addresses you have to define when setting up the fabric | ||
| \\ | \\ | ||
| VXLANs can use MCAST but most of the solutions are heading to point to point. ARP flooding between different hypervisors\\ | VXLANs can use MCAST but most of the solutions are heading to point to point. ARP flooding between different hypervisors\\ | ||
| Line 13: | Line 20: | ||
| Cisco APIC REST API User Guide: http:// | Cisco APIC REST API User Guide: http:// | ||
| \\ | \\ | ||
| - | * Unordered List ItemEPG | + | * EPG (End Distribution Point). They are like port-groups or port-profiles |
| - | * Unordered List ItemTenant: Within a tenant, you define one or more Layer 3 networks (VRF instances), one or more bridge domains per network, and EPGs to divide the bridge domains. | + | * Tenant: Within a tenant, you define one or more Layer 3 networks (VRF instances), one or more bridge domains per network, and EPGs to divide the bridge domains. |
| - | * Unordered List ItemTenant: Within a tenant, you define | + | * Contracts: The communication path between EPGs is managed using the concept of contracts. Contracts |
| + | |||
| + | |||
| + | ---- | ||
| + | **eVPN LEAF AND SPINE fabrics**\\ | ||
| + | * ToR router Has routing tables!! | ||
| + | * Even the end ‘host’ runs routing | ||