BGP hardware spec suggestion

General questions
,
1

Hi, I am trying to use BGP with 1 million ipv4 and 20k ipv6 records.
Is there any suggestion about the hardware(cpu, memory) I should prepare for VyOS?

Thanks

2

Will this box just deal with the RIB aka the BGP routing database stuff (like a route server) or will this box also route packets so a FDB aka forwarding database must be utilized aswell (like a regular internet router)?

Also will you do just IPv4 or just IPv6 or both?

Also if you want to deal with graceful restarts and additional paths (which will like double the usage since entries will be at “hot standby” instead of exchange them when needed later on).

3

Hi Apachez,
I will build as a virtual machine, and work in iBGP with a cisco router.
The main goal is asking cisco router send the BGP information to VyOS, VyOS don’t need to forward any traffic.

Both the ipv4 and ipv6 working in the same time.

As the result, I think it don’t need to be at “hot standby”, just as a client to fetch routing table through BGP.

4

Regarding the last part its part of BGP if your BGP box would only learn and remember the routes it will use or if it will use some additional memory to also have additional paths already stored in the local db.

The difference is without the additional paths you will have some downtime while the BGP exchange info from its peers while with additional paths already learned it can instantly switch to alternative paths without having to wait for the BGP process to exchange info.

5

My BGP box will only keep learning and remember the routes. I’m not sure if it has to have additional path that stored in the local db.
What’s the hardware requirements in this case with or without the feature?

6

I use two VyOS virtual routers for full IPv4 BGP and OSPF.
I also use two additional VyOS virtual routers for full IPv6 BGP and OSPF.

It works well ( no problems ever … ).

I am running these virtual vm VyOS BGP routers on Proxmox.

  • qty-14 3.0-GHz Xeon CPUs hyper threading disabled ( per virtual VyOS BGP router )
  • 40-Gig network cards into my 100-Gig switches
  • 10-Gig network BGP peering.
  • In Proxmox configuration , I do assign MultiQueue - 2 per virtual interface on my VyOS routers.
  • 16-Gig RAM per VyOS BGP router.

Each BGP router can easily handle 5+ Gig sustained traffic.

North Idaho Tom Jones

3 Likes
7

Thanks for your information!

Could you share with me how many BGP records in your case?
I have to handle 1 million ipv4 and 20k ipv6 records together, but it don’t need to forward traffic.

8

reply to ; dickens

just moments ago , I performed a count of BGP routes on all four of my VyOS BGP routers.

BGP #1 ( IPv4 only ) :
$ show bgp ipv4 statistics
BGP IPv4 Unicast RIB statistics (VRF default)
Total Advertisements : 951885
Total Prefixes : 951884
Average prefix length : 22.89
Unaggregateable prefixes : 468409
Maximum aggregateable prefixes: 483475
BGP Aggregate advertisements : 55029
Address space advertised : 3.02675e+09
% announced : 70.47
/8 equivalent : 180.41
/24 equivalent : 11823251.00
Advertisements with paths : 951885
Longest AS-Path (hops) : 107
Average AS-Path length (hops) : 4.62
Largest AS-Path (bytes) : 430
Average AS-Path size (bytes) : 20.48
Highest public ASN : 650950004

BGP #2 ( IPv4 only ) :
$ show bgp ipv4 statistics
BGP IPv4 Unicast RIB statistics (VRF default)
Total Advertisements : 951872
Total Prefixes : 951872
Average prefix length : 22.89
Unaggregateable prefixes : 468416
Maximum aggregateable prefixes: 483456
BGP Aggregate advertisements : 55041
Address space advertised : 3.02675e+09
% announced : 70.47
/8 equivalent : 180.41
/24 equivalent : 11823255.00
Advertisements with paths : 951872
Longest AS-Path (hops) : 107
Average AS-Path length (hops) : 4.62
Largest AS-Path (bytes) : 430
Average AS-Path size (bytes) : 20.48
Highest public ASN : 650950004

BGP #3 ( IPv6 only ) :
~$ show bgp ipv6 statistics
BGP IPv6 Unicast RIB statistics (VRF default)
Total Advertisements : 202282
Total Prefixes : 202282
Average prefix length : 42.88
Unaggregateable prefixes : 91748
Maximum aggregateable prefixes: 110534
BGP Aggregate advertisements : 12923
Address space advertised : 1.77176e+34
/32 equivalent %s
: 223627
/48 equivalent %s
: 1.46556e+10
Advertisements with paths : 202282
Longest AS-Path (hops) : 30
Average AS-Path length (hops) : 4.92
Largest AS-Path (bytes) : 122
Average AS-Path size (bytes) : 21.69
Highest public ASN : 401416

BGP #4 ( IPv6 only ) :
$ show bgp ipv6 statistics
BGP IPv6 Unicast RIB statistics (VRF default)
Total Advertisements : 202283
Total Prefixes : 202282
Average prefix length : 42.88
Unaggregateable prefixes : 91750
Maximum aggregateable prefixes: 110532
BGP Aggregate advertisements : 12924
Address space advertised : 1.77175e+34
/32 equivalent %s
: 223626
/48 equivalent %s
: 1.46556e+10
Advertisements with paths : 202283
Longest AS-Path (hops) : 30
Average AS-Path length (hops) : 4.92
Largest AS-Path (bytes) : 122
Average AS-Path size (bytes) : 21.70
Highest public ASN : 401416

1 Like
9

Using show bgp memory will provide more useful information regarding memory usage, which seems something interesting for this post

10

This topic was automatically closed 2 days after the last reply. New replies are no longer allowed.