nerdexam
Cisco

400-007 · Question #339

Refer to the exhibit, Company XYZ is a large enterprise network where the WAN traffic utilizes most of the link. The IT team in the company often reports Stuck-In-Active problems. The company is set…

The correct answer is D. Deploy the EIGRP stub capability on R5 and R6 with the connected and summary options. Deploying EIGRP stub on R5 and R6 restricts query propagation scope, which is the root cause of Stuck-In-Active conditions in EIGRP networks.

Designing Network Infrastructure

Question

Refer to the exhibit, Company XYZ is a large enterprise network where the WAN traffic utilizes most of the link. The IT team in the company often reports Stuck-In-Active problems. The company is set to acquire another company that will also be running EIGRP and which will connect to the Company XYZ R3 and R4 routers. This acquisition could make the issue worse. Which design solution solves this problem?

Exhibit

400-007 question #339 exhibit

Options

  • AImplement EIGRP Route Rap Dampening
  • BUtilize the EIGRP unequal cost load-balancing feature on R5 and R6 to provide an interim
  • CAdvertise only the default route to R5 and R6 filtering all other routes
  • DDeploy the EIGRP stub capability on R5 and R6 with the connected and summary options

How the community answered

(18 responses)
  • A
    11% (2)
  • B
    28% (5)
  • C
    6% (1)
  • D
    56% (10)

Why each option

Deploying EIGRP stub on R5 and R6 restricts query propagation scope, which is the root cause of Stuck-In-Active conditions in EIGRP networks.

AImplement EIGRP Route Rap Dampening

EIGRP Route Flap Dampening is not a native Cisco IOS EIGRP feature comparable to BGP dampening and would not address the query propagation scope that causes SIA.

BUtilize the EIGRP unequal cost load-balancing feature on R5 and R6 to provide an interim

Unequal cost load-balancing using the variance command addresses traffic distribution across unequal-cost paths but does not reduce EIGRP query scope or resolve SIA conditions.

CAdvertise only the default route to R5 and R6 filtering all other routes

Advertising only a default route to R5 and R6 would severely restrict routing functionality and does not address the underlying EIGRP query propagation mechanism that causes Stuck-In-Active.

DDeploy the EIGRP stub capability on R5 and R6 with the connected and summary optionsCorrect

EIGRP Stuck-In-Active occurs when a router does not receive replies to all outstanding queries within the active timer; configuring stub with the 'connected and summary' options causes R5 and R6 to advertise their stub status to neighbors, instructing EIGRP not to send queries to those routers during topology changes, which dramatically reduces query scope and prevents SIA from worsening as new EIGRP routers are added after the acquisition.

Concept tested: EIGRP stub routing to prevent Stuck-In-Active

Source: https://www.cisco.com/c/en/us/support/docs/ip/enhanced-interior-gateway-routing-protocol-eigrp/13673-14.html

Topics

#EIGRP#Stuck-In-Active#stub routing#WAN scalability

Community Discussion

No community discussion yet for this question.

Full 400-007 Practice