Avoiding iBGP Full Mesh Configuration: Options and Techniques

Configure iBGP Full Mesh: Avoidance Methods

Prev Question Next Question

Question

Which of the following two options can you configure to avoid iBGP full mesh? (Choose two.)

Answers

Explanations

Click on the arrows to vote for the correct answer

A. B. C. D. E.

AB.

The two options that can be configured to avoid iBGP full mesh are:

  1. Route Reflectors: Route Reflectors (RRs) are BGP routers that are configured to provide a more scalable alternative to the iBGP full mesh design. In this design, all iBGP speakers establish a full mesh of iBGP peer relationships with all other iBGP speakers within the same AS. As the number of iBGP speakers grows, the number of iBGP peer relationships increases exponentially, which can cause issues with scalability, stability, and convergence. Route Reflectors can be configured to act as a centralized point of reflection, allowing iBGP speakers to send updates to the RR, which then reflects the updates to other iBGP speakers that have established a peer relationship with the RR. This avoids the need for a full mesh of iBGP peers.

  2. Confederations: Confederations is another design option to avoid iBGP full mesh. In this design, the AS is divided into multiple sub-ASes, each of which has its own iBGP full mesh. The sub-ASes are then connected to each other using eBGP peer relationships, allowing them to exchange routing information. By using Confederations, the number of iBGP peers is limited within each sub-AS, which reduces the number of iBGP peer relationships that need to be established, and thus reduces the complexity of the iBGP network.

The other options provided in the question are not directly related to avoiding iBGP full mesh:

  1. BGP NHT: BGP Next-Hop Tracking (NHT) is a feature that allows the BGP router to track the reachability of the next-hop address for a particular route. This feature is useful for detecting and reacting to changes in the underlying network topology, but it does not address the scalability issues associated with iBGP full mesh.

  2. Local Preference: Local Preference is a BGP attribute that is used to influence the path selection process within the same AS. It is used to indicate to the BGP routers within the same AS which path is preferred to reach a particular destination. While it can be used to influence the path selection within the same AS, it does not address the scalability issues associated with iBGP full mesh.

  3. Virtual Peering: Virtual Peering is a technique used to connect two or more networks using a virtual private network ( VPN) rather than a physical network. While it can be used to connect two or more networks, it does not address the scalability issues associated with iBGP full mesh.