300-620 · Question #305
A network engineer configures a Cisco ACI fabric with this configuration: - Endpoint-1 with an IP address 10.1.0.1/24 is attached to Leaf-101. - Endpoint-2 with an IP address 10.1.0.2/24 is attached…
The correct answer is B. Configure a contract between the endpoints. If two endpoints in the same EPG cannot communicate despite being in the same EPG and bridge domain, the most likely cause is a policy enforcement issue. By default, endpoints in the same EPG can communicate without explicit contracts, but if security policies are preventing…
Question
A network engineer configures a Cisco ACI fabric with this configuration:
- Endpoint-1 with an IP address 10.1.0.1/24 is attached to Leaf-101.
- Endpoint-2 with an IP address 10.1.0.2/24 is attached to Leaf-102.
- Both endpoints are in EPG-A.
- The bridge domain for EPG-A is called BD-A and contains a single
subnet 10.1.0.254/24.
- Endpoint-1 cannot reach Endpoint-2.
Which action allows Endpoint-1 to communicate with Endpoint-2?
Options
- ASet L2 Unknown Unicast to Hardware Proxy.
- BConfigure a contract between the endpoints.
- CCreate a contract with a preferred group.
- DEnable silent host detection.
How the community answered
(34 responses)- A6% (2)
- B82% (28)
- C3% (1)
- D9% (3)
Explanation
If two endpoints in the same EPG cannot communicate despite being in the same EPG and bridge domain, the most likely cause is a policy enforcement issue. By default, endpoints in the same EPG can communicate without explicit contracts, but if security policies are preventing communication, configuring a contract between them would resolve the issue. Setting "L2 Unknown Unicast to Hardware Proxy" affects how unknown unicast traffic is handled but doesn't address policy enforcement between known endpoints. If the endpoints are in different EPGs, a contract is definitely required for communication.
Topics
Community Discussion
No community discussion yet for this question.