[isp-routing] Re: How common is multi-homing?

["Mike Hammett" <isplist@...]

Can't say that I have.

I did mean to call you yesterday, but I ran out of time.  Let's see if that
happens today...


Mike Hammett
CAM Internetworking


----- Original Message -----
From: "Dan Harrison" <dan.76@...>
To: <isp-routing@isp-routing.com>
Sent: Wednesday, January 22, 2003 8:06 AM
Subject: [isp-routing] Re: How common is multi-homing?


> Mike, the load balancing will need to be determined in order to
> optimize the inbound and outbound traffic for your network.
> Have you heard of MARO?
> DH3
>
>
>
> ----- Original Message -----
> From: Mike Hammett <isplist@...>
> Date: Tuesday, January 21, 2003 11:45 pm
> Subject: [isp-routing] Re: How common is multi-homing?
>
> > From what Logisense says, it supports BGP4, I dunno about Load
> > Balancing.
> >
> > Mike Hammett
> > CAM Internetworking
> >
> >
> > ----- Original Message -----
> > From: "Dan Harrison" <dan.76@...>
> > To: <isp-routing@isp-routing.com>
> > Sent: Tuesday, January 21, 2003 8:10 AM
> > Subject: [isp-routing] Re: How common is multi-homing?
> >
> >
> > > Either buy it or determine if Logisense supports BGP4 and load
> > > balancing.
> > >
> > > DH3
> > >
> > >
> > >
> > > ----- Original Message -----
> > > From: Mike Hammett <isplist@...>
> > > Date: Monday, January 20, 2003 6:48 pm
> > > Subject: [isp-routing] Re: How common is multi-homing?
> > >
> > > > What if you don't have Cisco equipment?  I am looking at between
> > > > Cisco and
> > > > Logisense.
> > > >
> > > >
> > > > Mike Hammett
> > > > CAM Internetworking
> > > > ----- Original Message -----
> > > > From: "Adam "Tauvix" Debus" <adam@...>
> > > > To: <isp-routing@isp-routing.com>
> > > > Cc: <isplist@...>
> > > > Sent: Wednesday, January 08, 2003 1:24 PM
> > > > Subject: [isp-routing] Re: How common is multi-homing?
> > > >
> > > >
> > > > > There are a couple of ways to figure this out, depending on what
> > > > equipment> you are using and/or what your budget looks like.
> > > > >
> > > > > If you are using Cisco equipment you can enable NetFlow and
> > > > export version
> > > > 5
> > > > > information to an external collector (Cisco sells one, there are
> > > > a couple
> > > > of
> > > > > Open Source ones that you'll have to do a little bit of work on
> > > > to get up
> > > > > and running). This will tell you the AS Number of the
> > > > destination network
> > > > > for outgoing traffic, and the origination network for incoming
> > > > traffic.> However, I think this will only work if you are
> > > > recieving a BGP feed from
> > > > > your upstream.
> > > > >
> > > > > Another option is to mirror the port your router is on, sniff
> > > > the traffic
> > > > > and log the domains/ip addresses. The major downside to this
> > > > will be the
> > > > > sifting through all the data and coming out with something
> > > > useful. Perl
> > > > will
> > > > > become your friend quickly.
> > > > >
> > > > > If you use a proxy server or firewall for your clients, you can
> > > > keep logs
> > > > > there, and write scripts to sift through and determine where
> > > > destination> networks are.
> > > > >
> > > > > Your last option is to guess. You can safely figure that roughly
> > > > 60% of
> > > > your
> > > > > traffic (in my experience anyway) ends up on the Big Networks
> > > > (UUNet, C&W,
> > > > > Sprint, Qwest). Your milage may vary. Generally, these 4
> > > > networks are in
> > > > > every area with a decent population, however, I wouldn't
> > > > recommed Qwest
> > > > > until such time as they get through all this relief stuff and
> > > > become a
> > > > Tier
> > > > > 1 network again. Another thing to consider when guessing is
> > how much
> > > > traffic
> > > > > is regional. Sometimes you'll find that a large portion of your
> > > > traffic is
> > > > > going to local ISPs and companies. In that case you might want
> > > > to find out
> > > > > what transit they buy, and sign up with the same. That will keep
> > > > transit> times really low for your regional traffic, as well as
> > > > get you the extra
> > > > > bandwidth and redundancy you need.
> > > > >
> > > > > Ultimately, however, it's not where you multihome, it's IF you
> > > > multihome.If
> > > > > it gets down to the question of cost and if you go with Provider
> > > > A your
> > > > > traffic will be better but it will put you right into
> > > > bankruptacy, or
> > > > > Provider B ping times might be a little higher, but you can
> > > > afford it; go
> > > > > with Provider B. Any multihoming is better then none.
> > > > >
> > > > > Thanks,
> > > > >
> > > > > Adam "Tauvix" Debus
> > > > > Linux Certified Professional, Linux Certified Administrator
> > #447641> > > Network Administrator, ReachONE Internet
> > > > > adam@...
> > > > > ----- Original Message -----
> > > > > From: "Mike Hammett" <isplist@...>
> > > > > To: <isp-routing@isp-routing.com>
> > > > > Sent: Tuesday, January 07, 2003 9:54 PM
> > > > > Subject: [isp-routing] Re: How common is multi-homing?
> > > > >
> > > > >
> > > > > > How would you figure out where your traffic goes?
> > > > > >
> > > > > >
> > > > > > Mike Hammett
> > > > > > CAM Internetworking
> > > > > > ----- Original Message -----
> > > > > > From: "Adam "Tauvix" Debus" <adam@...>
> > > > > > To: <isp-routing@isp-routing.com>
> > > > > > Sent: Monday, January 06, 2003 6:31 PM
> > > > > > Subject: [isp-routing] Re: How common is multi-homing?
> > > > > >
> > > > > >
> > > > > > > Extremely. Virtually any ISP with more then a handful of
> > > > customers> > generally
> > > > > > > will multihome. Extremely large orginizations will also
> > > > multihome.> > >
> > > > > > > The largest benifit comes, not from the extra bandwidth,
> > but the
> > > > > > > non-reliance on a single provider. If you have a
> > connection from
> > > > > Provider
> > > > > > A
> > > > > > > and a connection from Provider B then if one of them
> > > > experiences a
> > > > > router
> > > > > > > failure, power failure, employee going postal, etc, then you
> > > > are still
> > > > > > > online.
> > > > > > >
> > > > > > > The trick to good multihoming is to know where your traffic
> > > > is going.
> > > > If
> > > > > > you
> > > > > > > have a connection with, for example, Verio, and you find
> > > > most of your
> > > > > > > traffic goes from Verio to the UUNet peering, you could
> > > > probably cut
> > > > > > 10-25ms
> > > > > > > by buying transit from UUNet directly as well as from Verio.
> > > > > > >
> > > > > > > You would, of course, use BGP to peer with each provider,
> > > > probably> > > downloading full router tables (Make sure you have
> > > > at least 256MB of
> > > > RAM
> > > > > > in
> > > > > > > your router!), and then apply route-maps and so forth to
> > > > adjust your
> > > > > > traffic
> > > > > > > patterns from there.
> > > > > > >
> > > > > > > Thanks,
> > > > > > >
> > > > > > > Adam "Tauvix" Debus
> > > > > > > Linux Certified Professional, Linux Certified Administrator
> > > > #447641> > > Network Administrator, ReachONE Internet
> > > > > > > adam@...
> > > > > > > ----- Original Message -----
> > > > > > > From: "Michael Loftis" <mloftis@...>
> > > > > > > To: <isp-routing@isp-routing.com>
> > > > > > > Sent: Monday, January 06, 2003 4:10 PM
> > > > > > > Subject: [isp-routing] How common is multi-homing?
> > > > > > >
> > > > > > >
> > > > > > > > Was just quietly wondering, as far as the people on this
> > > > list have
> > > > had
> > > > > > > > contact with, how common is multi-homing?  (If you're not
> > > > sure what
> > > > > this
> > > > > > > > question means it probably doesn't apply to you! :))
> > > > > > > >
> > > > > > > > TIA!
> > > > > > > >
> > > > > > > > Michael Loftis
> > > > > > > >




> > > > routing/archives/> > > >
> > > > > > >
> > > > > > >




> > routing/archives/> > > >
> > > > > >




> > routing/archives/> > > >
> > > > >
> > > > >




> > > >
> > > >




> > > >
> > >
> > >




> >
> >




> >
>
>