hai, What is the difference between Route Server and Route Reflector in terms of complecity of TCP connections. Is it that Route Reflectors are for IBGP and Route Server for both EBGP and IBGP. Thanks in advance
On Sat, 20 Dec 2003, pramod babu G wrote:
What is the difference between Route Server and Route Reflector in terms of complecity of TCP connections. Is it that Route Reflectors are for IBGP and Route Server for both EBGP and IBGP.
Googling for those words gives this document... http://www.cs.ualberta.ca/~macg/Pubs/sci00.pdf
On 20 Dec 2003, at 10:11, Stephen J. Wilcox wrote:
On Sat, 20 Dec 2003, pramod babu G wrote:
What is the difference between Route Server and Route Reflector in terms of complecity of TCP connections. Is it that Route Reflectors are for IBGP and Route Server for both EBGP and IBGP.
Googling for those words gives this document...
I don't believe that route servers in the RFC 1863 sense have ever seen any real deployment. Joe
Stephen J. Wilcox wrote, On 21.12.2003 01:23:
I don't believe that route servers in the RFC 1863 sense have ever seen any real deployment.
I know at least one big global backbone who uses that deployment... i also know it causes them headaches!
To work properly rfc1863 requires also modified clients. Would be interestung to know what this big global backbone is using. We considered to implement rfc1863 in quagga (www.quagga.net) but stopped when we saw that clients have to support rfc1863 as well. And afaik no one of the big vendors does (or is even considering) Arnold
On 20 Dec 2003, at 05:26, pramod babu G wrote:
What is the difference between Route Server and Route Reflector in terms of complecity of TCP connections. Is it that Route Reflectors are for IBGP and Route Server for both EBGP and IBGP.
The term "route reflector" appears in the standards documents in RFC 1996 and later in RFC2796, both of which are concerned with IBGP things. "Route server" is (in my experience) almost always used to describe an EBGP thing, usually a means of implementing a multi-lateral peering infrastructure at an exchange point. "Looking glass" was the term used by Ed Kern in the cgi-script he ran on nitrous which allowed the world at large to execute particular commands on Digex routers. I don't know if other people used the term before Ed did, but that's the first time I saw it. Some route servers allow public telnet access, and provide looking glass functionality as well as route server functionality. These days, "route server" is frequently used to describe routers which provide looking glass functionality, regardless of whether they propagate routes between peers. In practice "route reflector" and "route server" are frequently interchanged, and if you are too pedantic in complaining about their misuse people start to hate you (again, in my experience :-) Joe
participants (4)
-
Arnold Nipper -
Joe Abley -
pramod babu G -
Stephen J. Wilcox