As we (ATG) are about to move into PAIX, SIX, and MAE-East ATM, I wanted to ask what the members of Nanog used to manage their peering with others (software wise). Currently we are all Cisco based, but Juniper and others are also eventualities. I've looked at the RtConfig program and it seems like a place to start, but I get the feeling that this is not the method most use. So, my question to you all is: Do you? a> Use RtConfig b> Use other publicly available code c> Use "in-house" code that's not public d> Do it by hand. Thanks in advance for any responses. -Scott -- ------------------------------------------------------------------------ Scott Call | Perhaps the best way to keep kids from turning on Router Geek | their classmates is to protect them in the first Advanced Telcom Group| place, -jonkatz
So, my question to you all is:
Do you?
a> Use RtConfig
We don't. IMHO, it's bloated and way more that I need. NAC has written some tools, but they are part of our entire billing package, and it will read the RA for routing updates.
b> Use other publicly available code
See a>.
c> Use "in-house" code that's not public
See a>.
d> Do it by hand.
We used to, and it will scale somewhat if you use peer-groups extensively. However, once you start to do 'special cases' more and more, it does get cumbersome.
On Fri, Apr 07, 2000 at 11:49:03AM -0700, Scott Call wrote:
As we (ATG) are about to move into PAIX, SIX, and MAE-East ATM, I wanted to ask what the members of Nanog used to manage their peering with others (software wise).
Route Server service is available at the PAIX exchange. You can get a sense of what type of routes are available from the PAIR pages for the exchange: http://www.rsng.net/rs-views/paix/ Information about peering with the route servers is available at: http://www.rsng.net/newpeer.html
I've looked at the RtConfig program and it seems like a place to start, but I get the feeling that this is not the method most use.
RtConfig is very nice for the RSng route servers, but can be problematic for your typical ISP-ISP peering sessions. However, if you are very serious about filtering routes on your peering sessions, agreeing to register your routes in one of the routing databases and programatically building your filters can be a big advantage.
a> Use RtConfig b> Use other publicly available code c> Use "in-house" code that's not public d> Do it by hand.
e> Use a route server and leave the filtering to us. :-) (N.B. The route servers only solve part of the problem, so YMMV.) -- Jeffrey Haas - Merit RSng project - jeffhaas@merit.edu
participants (3)
-
Alex Rubenstein -
Jeff Haas -
Scott Call