What's the reasoning for adding additional circuits?  Are you running
into bandwidth issues, or at least think you might in the near future?

If you add circuits, are you going to add connections to either AT&T or
UUNET or are you going to add additional providers?

If you have that much memory and a 3640, you could take full routes
from those two providers with no problem at all.  But if you start
adding circuits, I'd agree with Dave's suggestion which I think was to
accept customer-routes only and then use static defaults to handle the
rest.

The first question that must be answered is "Why?"   These other people
want to add additional circuits just because you can?  That's kinda
spooky.   You could add a DS3 if you wanted, why not just do that?  ;-)

John

>>> "brian kastor"  3/12/02 10:09:29 AM >>>
We have 1 router, 2 connections.  One goes to uunet, the other to at&t.

Equal bandwidth.  UUNET is where we are getting a /23, we are getting
nothing from at&t but connectivity and they have aggreed to advertise
the
/23.  The router is a 3640 with 256mb.  I have tried to explain that
this
router should only be used for this task, but others are wondering if
we
should bring in another couple of ds1's... hey we have the space on
the
router.  This got me to thinking we could take some of the load of by
only
getting customer routes or even just defaults.  John's first post made
me
rethink the defaults, so I was just wondering about what happens when
somethinng comes through for an as that isn't attached to the providers
if
we go with just customer routes.  I think I am going to take MADMAN's
suggestion and just weigh everything that doesn't get routed to uunet's
side.

I hope this helps clear it up... don't think I did a very good job of
explaining why I was asking




Message Posted at:
http://www.groupstudy.com/form/read.php?f=7&i=37974&t=37948
--------------------------------------------------
FAQ, list archives, and subscription info: http://www.groupstudy.com/list/cisco.html
Report misconduct and Nondisclosure violations to [EMAIL PROTECTED]

Reply via email to