You are deploying an IP fabric using EBGP and notice that your leaf devices are advertising and receiving all the routes. However, the routes are not installed in the routing table and are marked as…

Question

Options

• AYou need to configure as-override.
• BYou need to configure a next-hop self policy.
• CYou need to configure loops 2.
• DYou need to configure multipath multiple-as.

• A
  5% (2)
• B
  79% (33)
• D
  17% (7)

Explanation

You need to configure a next-hop self policy: When using EBGP, the next-hop IP address in the routing advertisements might not be reachable from the receiving device, causing the routes to be marked as hidden. By configuring the next-hop-self policy, the leaf devices will change the next-hop IP to their own IP address for the routes they advertise, making them reachable within the fabric and allowing the routes to be installed in the routing table. You need to configure loops 2: When all leaves share the same AS (common-AS design), BGP loop prevention drops routes learned from the same AS. Configuring loops 2 allows the leaf to accept routes with its own AS in the path twice, which is needed in an eBGP IP fabric with repeated AS numbers.

No community discussion yet for this question.