To connect two nonsilient servers in active/standby mode to two ACI leaves, you should implement a virtual PortChannel (vPC) on the ACI leaves. vPC provides high availability and load balancing for server connections.

References  :=  Cisco APIC Layer 2 Networking Configuration Guide, Release 5.2(x)

Removing pre-existing Fibre Channel over Ethernet (FCoE) configurations from Nexus devices is necessary to ensure compatibility with Cisco ACI mode.  FCoE configurations are not supported in ACI mode, and their presence can hinder the migration process 2 .

When Server A is connected to the Cisco ACI fabric using teamed interfaces with one active and one standby interface, enabling ARP flooding ensures that the ACI fabric can learn about the new active interface after a failover. This allows for seamless communication continuity even when the standby interface becomes active and starts sending traffic with its built-in MAC address.

Table Description automatically generated

To address resource overconsumption on a border leaf switch, migrating L3Outs to another switch can help distribute the load and reduce strain on the affected switch.

References  := Implementing Cisco Application Centric Infrastructure Official Cert Guide

An application-centric design in Cisco ACI focuses on the application requirements and interactions between different application components. In this design, EPGs (Endpoint Groups) represent different application tiers, such as web, application, and database tiers. This approach allows for a more flexible and scalable network configuration that aligns with the application architecture, enabling policies to be applied based on the application’s needs rather than the network topology.  References  := Implementing Cisco Application Centric Infrastructure Official Cert Guide

To prevent MAC flapping on Cisco UCS Fabric Interconnects and ACI leaf switches, MAC Pinning should be selected for the VMM vSwitch Port Channel policy. This ensures consistent uplink usage for each virtual machine’s traffic, avoiding MAC address movement across multiple uplinks.

References  := Implementing Cisco Application Centric Infrastructure Official Cert Guide

 In a stretched bridge domain solution between Cisco ACI sites with Layer 2 flood enabled, spine head-end replication is utilized to forward Broadcast, Unknown unicast, and Multicast (BUM) traffic between the sites. This method leverages the spine switches at each site to replicate BUM traffic to other sites, ensuring that all endpoints within the stretched bridge domain can receive such traffic. This approach is chosen over ISN multicast replication because it simplifies the overall design and reduces bandwidth consumption on inter-site links by avoiding unnecessary duplication of BUM traffic.  References  := ( Implementing Cisco Application Centric Infrastructure Official Cert Guide )

To enable SSH communication between Web_EPG (Web Endpoint Group) and App_EPG (Application Endpoint Group), it’s necessary to apply a configuration that allows bidirectional communication while not restricting ports based on their directionality. By enabling “Apply Both Directions” and disabling “Reverse Filter Ports,” this ensures that the filter allows SSH packets to flow from Web_EPG to App_EPG and vice versa without any restrictions based on the port’s direction, which is essential for establishing an SSH session.  References  := ( Implementing Cisco Application Centric Infrastructure Official Cert Guide )

 To address loops detected from endpoints in a Cisco ACI fabric, the engineer should  enable the rogue endpoint  feature and  set the Error Disabled Recovery Policy .  This will allow the system to detect rogue endpoints causing loops and automatically recover the port if it was disabled due to the loop detection 2 .

References  := ( Implementing Cisco Application Centric Infrastructure Official Cert Guide )