Highlighted
Regular Member
Posts: 544
Registered: ‎07-21-2010
Kudos: 95
Solutions: 8
Accepted Solution

ER-Pro8 | BGP routing mistakes on v.1.10.0

Hey Guys,

 

why will i ever step into the strangest issues first? :-P

 

 

root@at-sbg-itz-tz-k10-r10-bgp01:/home/rack# show ip bgp 185.202.7.240
BGP routing table entry for 185.202.7.0/24
Paths: (3 available, best #1, table Default-IP-Routing-Table)
  Advertised to non peer-group peers:
  185.58.30.254
  42871
    185.1.43.34 from 185.1.43.200 (185.1.43.200)
      Origin IGP, metric 20, localpref 200, valid, external, best
      Community: 1962:19640 1962:19641
      Last update: Fri Feb 16 01:41:50 2018

  33891 42871
    81.95.2.13 from 81.95.2.13 (81.95.15.237)
      Origin IGP, metric 0, localpref 100, valid, external
      Community: 1962:19623 33891:33892
      Last update: Fri Feb 16 01:45:47 2018

  1299 33891 42871
    62.115.150.201 from 62.115.150.201 (80.91.242.51)
      Origin IGP, metric 0, localpref 100, valid, external
      Community: 1299:30000 1962:19623
      Last update: Fri Feb 16 01:45:22 2018
root@at-sbg-itz-tz-k10-r10-bgp01:/home/rack# ip route show 185.202.7.0/24
185.202.7.0/24 via 62.115.150.201 dev eth4.102  proto zebraroot@at-sbg-itz-tz-k10-r10-bgp01:/home/rack#

That lines say everything that needs no comment ^^

 

 

Why is the route installated via AS1299 to the FIB instead of AS42871.

 

AS42871 is the origin of 185.202.7.0/24. We have a direct interconnection to that network.

Why EdgeOS will use an IP-Transit-Provider instead of direct interface?

 


Accepted Solutions
Regular Member
Posts: 544
Registered: ‎07-21-2010
Kudos: 95
Solutions: 8

Re: ER-Pro8 | BGP routing mistakes on v.1.10.0

Ahhhh, after 30 Minutes, FIB was correct.

So BGP is not immediately in sync with FIB.

View solution in original post


All Replies
Regular Member
Posts: 544
Registered: ‎07-21-2010
Kudos: 95
Solutions: 8

Re: ER-Pro8 | BGP routing mistakes on v.1.10.0

Ahhhh, after 30 Minutes, FIB was correct.

So BGP is not immediately in sync with FIB.