Select Preferred EBGP Peer with Weights

In the previous lab exercises, you configured EBGP sessions with two routers belonging to upstream ISPs and advertised your IPv4 prefixes to them.

Now, imagine that you want to use one of the uplinks just for backup purposes – it might be either too slow or too expensive for regular use.

Lab topology

In this lab, you’ll modify your BGP configuration to ensure your router always prefers routes advertised by X1 (ISP-1).

Existing BGP Configuration

The routers in your lab use the following BGP AS numbers. Each autonomous system advertises an IPv4 prefix. Upstream routers (x1, x2) also advertise the default route to your router (rtr).

Node/ASN Router ID Advertised prefixes

Your router has these EBGP neighbors. netlab configures them automatically; if you’re using some other lab infrastructure, you’ll have to manually configure EBGP neighbors and advertised prefixes.

Neighbor Neighbor IPv4 Neighbor AS
x1 65100
x2 65101

Start the Lab

Assuming you already set up your lab infrastructure:

  • Change directory to policy/1-weights
  • Execute netlab up (other options)
  • Log into your device (RTR) with netlab connect rtr and verify IP addresses and BGP configuration.

Note: netlab will configure IP addressing, EBGP sessions, and BGP prefix advertisements on your router. If you’re not using netlab, continue with the configuration you made during the previous exercise.

Configuration Tasks

You want your device to prefer routes advertised by X1 over those by X2. For example, the route for X2’s loopback interface should use X1 as the next hop.

Many BGP implementations use a mechanism called weight (usually applied per neighbor) to prefer routes advertised by one of the BGP peers.

If your device supports BGP weights, use them to prefer routes advertised by X1. Otherwise, you’ll have to use BGP local preference to achieve the same result.


Applying routing policy parameters to BGP neighbors doesn’t necessarily change the BGP table as the new parameters might be evaluated only on new incoming updates – you might have to use a command similar to clear ip bgp * soft in to tell your router to ask its neighbors to resend their BGP updates.


Examine the BGP table on your router to verify that the routes advertised by X1 (next hop: are the best (active) routes. This is a printout you should get on Arista EOS:

rtr#show ip bgp
BGP routing table information for VRF default
Router identifier, local AS number 65000
Route status codes: s - suppressed contributor, * - valid, > - active, E - ECMP head, e - ECMP
                    S - Stale, c - Contributing to ECMP, b - backup, L - labeled-unicast
                    % - Pending BGP convergence
Origin codes: i - IGP, e - EGP, ? - incomplete
RPKI Origin Validation codes: V - valid, I - invalid, U - unknown
AS Path Attributes: Or-ID - Originator ID, C-LST - Cluster List, LL Nexthop - Link Local Nexthop

          Network                Next Hop              Metric  AIGP       LocPref Weight  Path
 * >                  0       -          100     200     65100 i
 *                  0       -          100     100     65101 i
 * >        -                     -       -          -       0       ?
 * >              0       -          100     200     65100 i
 *              0       -          100     100     65101 65100 i
 * >              0       -          100     200     65100 65101 i
 *              0       -          100     100     65101 i

You could dig deeper and examine the details of an IPv4 prefix that originated in AS 65101 (X2), for example, Yet again, the next hop of the best path should be X1 (

rtr#show ip bgp
BGP routing table information for VRF default
Router identifier, local AS number 65000
BGP routing table entry for
 Paths: 2 available
  65100 65101 from (
      Origin IGP, metric 0, localpref 100, IGP metric 0, weight 200, tag 0
      Received 00:00:46 ago, valid, external, best
      Rx SAFI: Unicast
  65101 from (
      Origin IGP, metric 0, localpref 100, IGP metric 0, weight 100, tag 0
      Received 00:00:46 ago, valid, external
      Rx SAFI: Unicast


Reference Information

The following information might help you if you’re not using netlab to build the lab:

Lab Wiring

This lab uses a subset of the 4-router lab topology:

Origin Device Origin Port Destination Device Destination Port
rtr Ethernet1 x1 swp1
rtr Ethernet2 x2 swp1
x1 swp2 x2 swp2

Lab Addressing

Node/Interface IPv4 Address IPv6 Address Description
rtr Loopback
Ethernet1 rtr -> x1
Ethernet2 rtr -> x2
x1 Loopback
swp1 x1 -> rtr
swp2 x1 -> x2
x2 Loopback
swp1 x2 -> rtr
swp2 x2 -> x1