An engineer configured Layer 2 extension from the ACI fabric and changed the Layer 2 unknown unicast policy from Flood to Hardware Proxy.
How does this change affect the flooding of the L2 unknown unicast traffic?
Click on the arrows to vote for the correct answer
A. B. C. D.A.
https://www.cisco.com/c/en/us/td/docs/switches/datacenter/aci/apic/sw/2-x/L2_config/b_Cisco_APIC_Layer_2_Configuration_Guide/When an endpoint sends a unicast frame, the ACI fabric checks if the destination endpoint is present in the endpoint table. If the destination endpoint is not present in the table, the unicast frame is considered as unknown unicast traffic.
By default, the ACI fabric floods unknown unicast traffic within the bridge domain or VLAN. However, this can lead to a significant increase in network traffic, causing congestion and other performance issues. To address this problem, the ACI fabric provides a feature called Layer 2 unknown unicast policy, which allows the network administrator to control how the unknown unicast traffic is handled.
When the Layer 2 unknown unicast policy is set to "Flood," the unknown unicast traffic is flooded within the bridge domain or VLAN, which can result in a higher volume of network traffic.
On the other hand, when the Layer 2 unknown unicast policy is set to "Hardware Proxy," the ACI fabric forwards the unknown unicast traffic to one of the spine switches to perform as a spine proxy. The spine proxy then forwards the unknown unicast traffic only to the leaf switch where the destination endpoint is located, reducing the amount of network traffic.
Therefore, the answer to the question is A. When the Layer 2 unknown unicast policy is changed from "Flood" to "Hardware Proxy," the unknown unicast traffic is forwarded to one of the spine switches to perform as a spine proxy. The spine proxy forwards the traffic only to the leaf switch where the destination endpoint is located, reducing the amount of network traffic.