|
North American Network Operators Group Date Prev | Date Next | Date Index | Thread Index | Author Index | Historical Re: Route Collector
### On Tue, 26 Mar 2002 09:14:11 -0500, "Chris Pace" <[email protected]> ### casually decided to expound upon "Jake Khuon" <[email protected]> the ### following thoughts about "Re: Route Collector ": CP> Yes, it is forwarding bgp routes. However, it has no serial lines connected. CP> Do you think it is causing unnecessary traffic ? I guess I'm just a little confused. You have your servers pointing default to it which means it's intended to pass traffic but it has no external connectivity and it's passing eBGP routes? How is that possible? I guess it would help me to understand if I knew what you're trying to achieve. CP> ----- Original Message ----- CP> From: "Jake Khuon" <[email protected]> CP> To: "Chris Pace" <[email protected]> CP> Cc: "Todd Suiter" <[email protected]>; <[email protected]> CP> Sent: Tuesday, March 26, 2002 9:02 AM CP> Subject: Re: Route Collector CP> CP> CP> > ### On Tue, 26 Mar 2002 08:50:44 -0500, "Chris Pace" <[email protected]> CP> > ### casually decided to expound upon "Todd Suiter" <[email protected]> the CP> > ### following thoughts about "Route Collector": CP> > CP> > CP> Is it common or a good idea to have a route collector in a CP> > CP> datacenter/enterprise environment ? We have 1 router that just CP> collects CP> > CP> routes using bgp and ospf, then set all servers to use it as the CP> default CP> > CP> gateway. Is this practical or am I making more work for myself ? CP> > CP> > So it's doing more than just collecting routes? It's also forwarding CP> > traffic? Is it carrying a full table of eBGP routes too? -- /*===================[ Jake Khuon <[email protected]> ]======================+ | Packet Plumber, Network Engineers /| / [~ [~ |) | | --------------- | | for Effective Bandwidth Utilisation / |/ [_ [_ |) |_| N E T W O R K S | +=========================================================================*/
|