I know that in our case, trying to use BGP for failover between two
providers, we
(a) were required to have a /24 <UUnet> ... no problem
(b) were required to have an AS# ... no
problem
(c) PSI *required* us to 'take posssession' of the maintainer object for our
/24 ... still working on that part
a. <<very few people appear to have ever heard of RADB ... very
frustrating>>
(d) once we finish (c) we *should* be all set .. unless PSInet finds another
way to delay us.
I only send this because the "RADB/ Maintainer Object" part has been a
really painful delay .. but, that should be resolved today :).
Thanks!
TJ
-----Original Message-----
From: John Neiberger [mailto:[EMAIL PROTECTED]]
Sent: Thursday, March 29, 2001 17:08
To: [EMAIL PROTECTED]
Cc: [EMAIL PROTECTED]
Subject: Re: BGP over two ISP links
At a minimum you're going to need a single /24, not two. You would
announce this prefix on both connections. You're also going to need to
apply for an autonomous system number from ARIN. Details can be found
at www.arin.net.
I'm wondering what you're really trying to accomplish. If this extra
link isn't for redundancy, just load sharing, then why not have two
connections to the same provider? This is FAR easier to implement, does
not require a public AS number, and does not require using up an entire
/24 prefix unnecessarily.
Even if the link is for redundancy, you could multihome to different
POPs of the same provider. Again, this is easier to implement, doesn't
require the AS number, and doesn't burn up so many addresses. If you
have a good provider this is an excellent solution.
I'd seriously consider these other options before you make a decision.
Regards,
John
>>> "Ruihai An" <[EMAIL PROTECTED]> 3/29/01 2:11:17 PM >>>
Hi, All,
Here is a quick question:
We are planning to run BGP over two ISP links to provide loading
balance.
But we were told that we will run into major problems if we do not have
full
class Cs on both ends.
Could somebody make comment on this?
Thanks
Ruihai
_________________________________
FAQ, list archives, and subscription info:
http://www.groupstudy.com/list/cisco.html
Report misconduct and Nondisclosure violations to [EMAIL PROTECTED]
_________________________________
FAQ, list archives, and subscription info:
http://www.groupstudy.com/list/cisco.html
Report misconduct and Nondisclosure violations to [EMAIL PROTECTED]
*****************************************************************************
The information in this email is confidential and may be legally privileged.
It is intended solely for the addressee. Access to this email by anyone else
is unauthorized.
If you are not the intended recipient, any disclosure, copying, distribution
or any action taken or omitted to be taken in reliance on it, is prohibited
and may be unlawful. When addressed to our clients any opinions or advice
contained in this email are subject to the terms and conditions expressed in
the governing KPMG client engagement letter.
*****************************************************************************
_________________________________
FAQ, list archives, and subscription info: http://www.groupstudy.com/list/cisco.html
Report misconduct and Nondisclosure violations to [EMAIL PROTECTED]
