From: MADMAN (dmadlan@xxxxxxxxx)
Date: Mon Mar 18 2002 - 11:17:14 GMT-3
No sorry I do not. I don't work in that group but I do know a couple
of people that do who also read this list so maybe they can answer this
question...
Dave
Vincent Lee wrote:
>
> Do you know PacBell and Qwest BGP Policy?
> I got the Sprintlink's BGP Policy from their website.
> http://www.sprint.net/policy/bgp.html
>
> thanks
>
> --- MADMAN <dmadlan@qwest.com> wrote:
> >
> > I disagree. I have done several Internet
> > connections where one
> > provider announces /24's of another, no problem.
> > It's the primary factor
> > in the growth of the Internet routing table.
> >
> > Dave
> >
> > Wade Edwards wrote:
> > >
> > > To get a true backup you have to apply for your
> > own address space that
> > > you can announce to both PacBell and Qwest. If
> > you are using address
> > > space from both PacBell and Qwest then they will
> > not allow you to
> > > announce their addresses through a different
> > provider. You can ask if
> > > they will but this is usually against their
> > routing policy. So you
> > > don't need BGP. Just use static routing.
> > >
> > > L8r.
> > >
> > > -----Original Message-----
> > > From: Vincent Lee [mailto:mcne95@yahoo.com]
> > > Sent: Friday, March 15, 2002 11:49 AM
> > > To: Brian Lodwick; dmadlan@qwest.com
> > > Cc: ccielab@groupstudy.com
> > > Subject: Re: OT: Change primary ISP from
> > PacBell to Quest
> > >
> > > We are using the PacBell and already ordered the
> > Qwest
> > > Circuit.
> > > Two perimeter routers configed with HSRP and they
> > are
> > > only connect to Pacbell at this moment.
> > >
> > > We are going to keep PacBell as secondary with a
> > > smaller bandwidth. Qwest will be the primary
> > inbound
> > > Web traffic.
> > >
> > > My first step is asking PacBell and Qwest for AS
> > > peering info then I'll apply for our own AS from
> > ARIN.
> > >
> > > thanks
> > >
> > > --- Brian Lodwick <xpranax@hotmail.com> wrote:
> > > > I would suggest you replace the Qwest circuit
> > with
> > > > another provider so that
> > > > you get some support if it goes down.
> > > >
> > > > >>>Brian
> > > >
> > > >
> > > > >From: MADMAN <dmadlan@qwest.com>
> > > > >Reply-To: MADMAN <dmadlan@qwest.com>
> > > > >To: Vincent Lee <mcne95@yahoo.com>
> > > > >CC: ccielab@groupstudy.com
> > > > >Subject: Re: OT: Change primary ISP from
> > PacBell to
> > > > Quest
> > > > >Date: Fri, 15 Mar 2002 09:35:29 -0600
> > > > >
> > > > > You mean Qwest ;)
> > > > >
> > > > > Reading between the lines are you currently
> > > > connected to PacBell? If
> > > > >so I would set up the BGP connection with them
> > > > first, make sure they get
> > > > >rid of the static routing of your network.
> > Bring
> > > > up the Qwest
> > > > >connection. Then you could establish the IBGP
> > > > connection between the
> > > > >two. Are you doing HSRP between the two
> > routers
> > > > that you defaulting to
> > > > >internally?
> > > > >
> > > > > Just a couple of ideas based on limited
> > info.
> > > > >
> > > > > Dave
> > > > >
> > > > >Vincent Lee wrote:
> > > > > >
> > > > > > I am going to setup a redundancy multihomed
> > BGP
> > > > > > network with two separate ISPs - PacBell and
> > > > Quest.
> > > > > >
> > > > > > Here is my plan.
> > > > > >
> > > > > > 1. setup BGP in our company's perimeter
> > routers
> > > > > >
> > > > > > 2. connect to Pacbell and Quest autonomous
> > > > system
> > > > > >
> > > > > > 3. Change primary DNS server from PacBell to
> > > > Quest in
> > > > > > Network Solutions/VeriSign
> > > > > >
> > > > > > 4. Change our Web IP address in Network
> > > > > > Solutions/VeriSign and point smtp relay
> > > > servers to
> > > > > > Quest.
> > > > > >
> > > > > > Any suggestions are welcome and appreciated.
> > > > > >
> > > > > >
> > > >
This archive was generated by hypermail 2.1.4 : Thu Jun 13 2002 - 10:57:12 GMT-3