What to configure in BGP so that other BGP neighbours cannot influence the path of a route.

What to configure in BGP so that other BGP neighbours cannot influence the path of a route.
A . Lower MED
B . Higher Local pref
C . Higher weight
D . Lower router ID

View Answer

Answer: C

Explanation:

The list of the selection criteria is presented below in the same order in which BGP uses them to select the optimal routes to be injected into the IP Routing table:

https://www.noction.com/blog/bgp_bestpath_selection_algorithm

1) Weight ― weight is the first criterion used by the router and it is set locally on the user’s router. The Weight is not passed to the following router updates. In case there are multiple paths to a certain IP address, BGP always selects the path with the highest weight. The weight parameter can be set either through neighbour command, route maps or via the AS-path access list.

2) Local Preference ― this criterion indicates which route has local preference and BGP selects the one with the highest preference. Local Preference default is 100.

3) Network or Aggregate ― this criterion chooses the path that was originated locally via an aggregate or a network, as the aggregation of certain routes in one is quite effective and helps to save a lot of space on the network.

4) Shortest AS_PATH ― this criterion is used by BGP only in case it detects two similar paths with nearly the same local preference, weight and locally originated or aggregate addresses.

5) Lowest origin type ― this criterion assigns higher preference to Exterior Gateway Protocol (EGP) and lower preference to Interior Gateway Protocol (IGP).

6) Lowest multi-exit discriminator (MED) ― this criterion, representing the external metric of a route, gives preference to the lower MED value.

7) eBGP over iBGP ― just like the “Lowest origin type” criterion, this criterion prefers eBGP rather than iBGP.

8) Lowest IGP metric ― this criterion selects the path with the lowest IGP metric to the BGP next hop.

9) Multiple paths ― this criterion serves as indication whether multiple routes need to be installed in the routing table.

10) External paths ― out of several external paths, this criterion selects the first received path.

11) Lowest router ID ― this criterion selects the path which connects to the BGP router that has the lowest router ID.

12) Minimum cluster list ― in case multiple paths have the same router ID or originator, this criterion selects the path with the minimum length of the cluster list.

13) Lowest neighbour address ― this criterion selects the path, which originates from the lowest neighbour address.

On eBGP router with single-homed (connected to single ISP with single router and multiple links) or dual-homed (connected to single ISP with dual router) topology, the route could be influenced by ISP by tuning the MED attribute (as we know MED is the attribute which is exchanged between eBGP peers), also we could influence the route advertised to our ISP by tuning the same metric – MED.

On eBGP router with multi-homed (connected to multiple ISPs) topology the MED attribute won’t work anymore.

On iBGP router with single-homed, dual-homed or multi-homed (doesn’t really matter as we are talking about iBGP peer) the route can be influenced by tuning the Local Preference attribute (as we know Local Preference is the attribute which is exchanged between iBGP peers).

Now, no matter what router we are on (eBGP or iBGP) and no matter what topology we are using (single-homed, dual-homed, multi-homed) if we don’t want to our BGP neighbors to influence the route choice, we can configure higher Weight attribute (for that route) locally on the router and no matter what the other routers do, they can not change it.