nerdexam
Cisco

300-620 · Question #269

An engineer configures an L3Out between BLeaf1 and Core1. A Cisco Nexus 9000 Series Switch runs in NX-OS mode, and the two devices must peer using OSPF. The devices in the network are configured as…

The correct answer is B. Configure Area 1 on BLeaf1. To establish an OSPF adjacency between BLeaf1 and Core1, the OSPF area ID on BLeaf1 must be explicitly configured to match Area 1 on Core1.

External Network Connectivity

Question

An engineer configures an L3Out between BLeaf1 and Core1. A Cisco Nexus 9000 Series Switch runs in NX-OS mode, and the two devices must peer using OSPF. The devices in the network are configured as follows:

  • BLeaf1 has been configured with the IP address 10.1.0.2/31 and the

router ID 0.0.0.2.

  • Core1 has been configured with the IP address 10.1.0.3/31 and the

router ID 0.0.0.1.

  • On Cisco ACI, the engineer has enabled OSPF using the default OSPF

settings.

  • The engineer has configured OSPF on the NX-OS switch using the ip

router ospf ACI_peering area 1 command. Which action brings up the OSPF adjacency?

Options

  • ASet and Auth Key on Core1.
  • BConfigure Area 1 on BLeaf1.
  • CDisable Hello Timer on BLeaf1.
  • DChange the MTU on Core1.

How the community answered

(71 responses)
  • A
    4% (3)
  • B
    85% (60)
  • C
    3% (2)
  • D
    8% (6)

Why each option

To establish an OSPF adjacency between BLeaf1 and Core1, the OSPF area ID on BLeaf1 must be explicitly configured to match Area 1 on Core1.

ASet and Auth Key on Core1.

Setting an Auth Key on Core1 would only be necessary if OSPF authentication was enabled and mismatched, which is not indicated as the problem here.

BConfigure Area 1 on BLeaf1.Correct

OSPF adjacency requires several parameters to match between peering routers, and the OSPF Area ID is one of the most fundamental. Core1 is explicitly configured for OSPF Area 1, but BLeaf1's OSPF is enabled with default settings, which typically implies Area 0 (the backbone area). Therefore, configuring Area 1 on BLeaf1 is essential to resolve the area mismatch and allow OSPF adjacency to form.

CDisable Hello Timer on BLeaf1.

Disabling the Hello Timer on BLeaf1 would prevent OSPF from sending hello packets, which are necessary for neighbor discovery and maintaining adjacency, thus breaking it.

DChange the MTU on Core1.

While mismatched MTU can prevent OSPF adjacency, there is no information to suggest an MTU issue, and the explicit area ID mismatch is a more direct cause based on the provided configuration details.

Concept tested: OSPF adjacency requirements - Area ID

Source: https://www.cisco.com/c/en/us/td/docs/dcn/aci/apic/5x/sw/l3-configuration/b-cisco-aci-layer-3-configuration-guide-5x/m-ospf.html

Topics

#L3Out#OSPF#routing protocols#external routing

Community Discussion

No community discussion yet for this question.

Full 300-620 Practice