BGP Confederation deployment
My company has a small network that is now expanding somewhat. We have
3 data centers in total 2 of which provide eBGP connections to our
customers who have local Ethernet/Metro-E circuit handoffs to each data
center... We currently use eBGP to the client with a public AS.
Between the 2 data centers another engineer decided to run IBGP, which
was then removed and now spanning tree is being used between the 2 data
centers (Over high capacity circuits), Not my idea!
One of my fellow engineers insists running BGP confederation is optimal
My plan is revert to private AS for each data center and run eBGP to the
clients and also between the data centers for faster convergence along
with BFD protocol.. I do not want to use confederation as I dont see it
being needed and i dont have an experience with any routing anomalies
associate with it.
I plan on weighing routes using MED's between the private AS in our networks to control routing.
I have argued that BGP confederation is used to solve the issue of larger
networks iBGP mesh and typically ISP use confederations only..
Is there a need to use confederations ? Does it make sense to use it
here ??? If we plan on using eBGP between data center I dont see a need
In summary this is how the network will look:
Client ---eBGP---> DC#1 <----eBGP----> DC#2 -----eBGP----> Client
we really dont have any need to run IBGP except maybe between the 2 egress (eBGP) switches that connect to the clients