I just worked on this a couple of weeks ago - and got mine running.
I am assuming you are BGP peering to something where both BGP servers ( yours and theirs ) are using private AS numbers.
What you can do to split the load on a /24 BGP network between two remote BGP peers is configure as prepend on your /24 - where - you divide your /24 into two /25 networks. On your first /25 configure it as somewhat normal BGP peering , then on the other /25 half of your /24 , configure the /25 to ap prepend twice. Then repeat the process on your other BGP peering - but this time , configure your AS prepend so that it is on the other /25 network.
The result is on a /24 network ( two /25s ) the lower half of the /24 comes in over one BGP peer and the upper half of the /24 comes in over the other BGP peering sessiong. If one BGP peer session goes down , then the remaining BGP peering session will pickup everything until the failed BGP session starts talking again.
if you have a 3\rd BGP peer for your network - lets say a very slow network , you can add both of your /25s to it and prepend 6 times , so that the result is when both of your normal BGP peers are running , the 3'rd bgp peer does nothing, And when both of your normal BGP peering sessions go down , then your last fall-back slow BGP peering session will then bring up everything until at least one of your two primary BGP peering sessions starts talking again.
As a rule of thumb - slow is better than dead ( thus a 3'rd alternate fall back BGP peer might be considered )
I am assuming you are BGP peering to something where both BGP servers ( yours and theirs ) are using private AS numbers.
What you can do to split the load on a /24 BGP network between two remote BGP peers is configure as prepend on your /24 - where - you divide your /24 into two /25 networks. On your first /25 configure it as somewhat normal BGP peering , then on the other /25 half of your /24 , configure the /25 to ap prepend twice. Then repeat the process on your other BGP peering - but this time , configure your AS prepend so that it is on the other /25 network.
The result is on a /24 network ( two /25s ) the lower half of the /24 comes in over one BGP peer and the upper half of the /24 comes in over the other BGP peering sessiong. If one BGP peer session goes down , then the remaining BGP peering session will pickup everything until the failed BGP session starts talking again.
if you have a 3\rd BGP peer for your network - lets say a very slow network , you can add both of your /25s to it and prepend 6 times , so that the result is when both of your normal BGP peers are running , the 3'rd bgp peer does nothing, And when both of your normal BGP peering sessions go down , then your last fall-back slow BGP peering session will then bring up everything until at least one of your two primary BGP peering sessions starts talking again.
As a rule of thumb - slow is better than dead ( thus a 3'rd alternate fall back BGP peer might be considered )
Statistics: Posted by TomjNorthIdaho — Tue Jan 30, 2024 4:41 am