apic

The video covers installing ACI Multi-Cloud infrastructure in AWS, deploying a Cisco Cloud Network Controller (CNC), and provisioning the infra VPC using Catalyst 8000V (CCR) cloud routers. NDO is used to register the CNC and automate site-to-site connectivity configuration. Our focus for the lab is to bring up Inter-Site Network connectivity between on-prem DC and AWS cloud in preparation to support user tenant workload deployment.

The video covers installing ACI Multi-Cloud infrastructure in AWS, deploying a Cisco Cloud Network Controller (CNC), and provisioning the infra VPC using Catalyst 8000V (CCR) cloud routers. NDO is used to register the CNC and automate site-to-site connectivity configuration. Our focus for the lab is to bring up Inter-Site Network connectivity between on-prem DC and AWS cloud in preparation to support user tenant workload deployment.

The video covers installing ACI Multi-Cloud infrastructure in AWS, deploying a Cisco Cloud Network Controller (CNC), and provisioning the infra VPC using Catalyst 8000V (CCR) cloud routers. NDO is used to register the CNC and automate site-to-site connectivity configuration. Our focus for the lab is to bring up Inter-Site Network connectivity between on-prem DC and AWS cloud in preparation to support user tenant workload deployment.

The video covers installing ACI Multi-Cloud infrastructure in AWS, deploying a Cisco Cloud Network Controller (CNC), and provisioning the infra VPC using Catalyst 8000V (CCR) cloud routers. NDO is used to register the CNC and automate site-to-site connectivity configuration. Our focus for the lab is to bring up Inter-Site Network connectivity between on-prem DC and AWS cloud in preparation to support user tenant workload deployment.

The video demonstrates Service Graph configuration in a ACI Multi-Site setup using L3 Policy-Based Redirect (PBR) to Cisco Secure Firewall Virtual (FTDv). Two traffic scenarios are validated: North-South (N-S) and East-West (E-W). We will try to understand traffic processing behavior by the Service Graph in each scenario. We will perform L3Out failover and see how traffic rerouting between sites is handled.

The video demonstrates Service Graph configuration in a ACI Multi-Site setup using L3 Policy-Based Redirect (PBR) to Cisco Secure Firewall Virtual (FTDv). Two traffic scenarios are validated: North-South (N-S) and East-West (E-W). We will try to understand traffic processing behavior by the Service Graph in each scenario. We will perform L3Out failover and see how traffic rerouting between sites is handled.

The video covers L3OUT design in ACI Multi-Site in three scenarios: shared L3Out, dedicated L3Out, and active/active DC design. Each scenario presents different design options and we will highlight key differences and benefits of each one. The lab will look at host route advertisement to ensures that external traffic is always routed optimally to a destination workload.

The video covers L3OUT design in ACI Multi-Site in three scenarios: shared L3Out, dedicated L3Out, and active/active DC design. Each scenario presents different design options and we will highlight key differences and benefits of each one. The lab will look at host route advertisement to ensures that external traffic is always routed optimally to a destination workload.

The video covers L3OUT design in ACI Multi-Site in three scenarios: shared L3Out, dedicated L3Out, and active/active DC design. Each scenario presents different design options and we will highlight key differences and benefits of each one. The lab will look at host route advertisement to ensures that external traffic is always routed optimally to a destination workload.

The video demonstrates how to replicate an existing tenant from a primary ACI site to a second site using object import. The lab then configures VMM integration at the second site using a single vCenter that manages ESXi clusters at both sites. We will create a new per-site VDS and VMM domain on the DC2 APIC. The lab concludes with successful inter-cluster vMotion of VMs across sites over the stretched L2 subnet.