|
|
@@ -11,9 +11,8 @@
|
|
|
The purpose of a Route Server is to centralize the peerings between BGP
|
|
|
speakers. For example if we have an exchange point scenario with four BGP
|
|
|
speakers, each of which maintaining a BGP peering with the other three
|
|
|
-(@pxref{fig:full-mesh}), we can convert it into a centralized scenario where
|
|
|
-each of the four establishes a single BGP peering against the Route Server
|
|
|
-(@pxref{fig:route-server}).
|
|
|
+we can convert it into a centralized scenario where
|
|
|
+each of the four establishes a single BGP peering against the Route Server.
|
|
|
|
|
|
We will first describe briefly the Route Server model implemented by Quagga.
|
|
|
We will explain the commands that have been added for configuring that
|
