nerdexam
Cisco

300-620 · Question #162

Refer to the exhibit. An engineer configured subnets on the external EPG called L3OUT_CORE. The external endpoints in the 10.1.0.0/24 subnet can reach internal endpoints, but the external endpoints in

The correct answer is B. Delete the external EPG subnet 0.0.0.128/1.. To resolve reachability issues for specific external endpoints, it is necessary to identify and remove overly broad or conflicting external EPG subnet configurations.

External Network Connectivity

Question

Refer to the exhibit. An engineer configured subnets on the external EPG called L3OUT_CORE. The external endpoints in the 10.1.0.0/24 subnet can reach internal endpoints, but the external endpoints in the 172.16.1.0/24 subnet are unreachable. Which set of actions enables the connectivity?

Options

  • ADelete both external EPG subnets.
  • BDelete the external EPG subnet 0.0.0.128/1.
  • CDelete both external EPG subnets.
  • DDelete the external EPG subnet 0.0.0.0/0.

How the community answered

(20 responses)
  • A
    10% (2)
  • B
    65% (13)
  • C
    20% (4)
  • D
    5% (1)

Why each option

To resolve reachability issues for specific external endpoints, it is necessary to identify and remove overly broad or conflicting external EPG subnet configurations.

ADelete both external EPG subnets.

Deleting both subnets is too aggressive and would likely break connectivity for 10.1.0.0/24, which is currently working.

BDelete the external EPG subnet 0.0.0.128/1.Correct

Deleting the external EPG subnet 0.0.0.128/1 (likely representing 128.0.0.0/1) resolves the issue for 172.16.1.0/24. This broad subnet definition can misclassify specific external endpoints or interfere with their proper policy application and contract matching, particularly for subnets falling within its range like 172.16.1.0/24.

CDelete both external EPG subnets.

Deleting both subnets is too aggressive and would likely break connectivity for 10.1.0.0/24, which is currently working.

DDelete the external EPG subnet 0.0.0.0/0.

Deleting 0.0.0.0/0 would likely affect connectivity for 10.1.0.0/24 as well, and the problem is specific to 172.16.1.0/24, suggesting a more targeted issue.

Concept tested: ACI L3Out external EPG subnet policy

Source: https://www.cisco.com/c/en/us/td/docs/dcn/aci/apic/5x/config-guide/cisco-aci-layer3-configuration-guide-5x/m-external-epg-subnets.html

Topics

#L3Out#external EPG#subnet configuration#connectivity troubleshooting

Community Discussion

No community discussion yet for this question.

Full 300-620 Practice