[86058] in North American Network Operators' Group
RE: multi homing pressure
daemon@ATHENA.MIT.EDU (Ejay Hire)
Fri Oct 21 12:31:04 2005
From: "Ejay Hire" <ejay.hire@isdn.net>
To: <nanog@merit.edu>
Date: Fri, 21 Oct 2005 11:30:21 -0500
In-Reply-To: <43569F09.4030605@amplex.net>
Errors-To: owner-nanog@merit.edu
If only I'd had the foresight to configure the all of the
customers I've setup on BGP with Bogon filters, and more
complex routing policies than defaults + provider customer
routes, then I would have made mountains of recurring
revenue from this "maintenance", and I would be reading this
thread in my mountain cabin with beleaguered amusement.
Alas, I met the customers requirement, it has to "just
work"... And it does.
(and yes, on the network I administer at my day job, I
bogon/rpf filter and aggressively traffic engineer.)
-ejay
> -----Original Message-----
> From: owner-nanog@merit.edu [mailto:owner-nanog@merit.edu]
On
> Behalf Of Mark Radabaugh
> Sent: Wednesday, October 19, 2005 2:31 PM
> To: nanog@merit.edu
> Subject: Re: multi homing pressure
>
>
> John Payne wrote:
>
> >
> > Hrm, people keep saying that BGP is hard and takes time.
> >
> > As well as my end-user-facing network responsibilities,
I also have
> > corporate network responsibilities here. All of our
corporate hub
> > locations are multi-homed (or soon will be)... and I
honestly can't
> > remember the last time I made any changes (besides IOS
upgrades) to
> > BGP configs for the 2 hubs in the US. (We're moving
physical
> > locations in the "international" hubs and taking new
providers, so
> > I'm discounting those changes as you'd have similar
changes in a
> > single homed statically routed move).
> >
> > If you don't have multihoming requirements other than
availability
> > then it really can be fire and forget.
>
> Except for those pesky bogon filters.... which
corporations
> seem to like
> to "fire and forget".
>
> --
> Mark Radabaugh
>
> Amplex
> mark@amplex.net
> 419.837.5015
>
