Exodus/C&W Depeering

Tue Mar 26 17:35:13 UTC 2002

Chris,
You are right.

On Tue, 26 Mar 2002, Chris Woodfield wrote:

>
> I'm presuming that Exodus is planning to get the transit they need after this
> depeering via C&W's peering points? If so, this makes a certain amount of sense - no

Looking at Exodus Route Server you will see that they are now getting
transit from C&W.  Probably using as you state their current peering
circuits (it makes sense from an operational point of view, when you are
consolidating an AS into a single one).

route-server.exodus.net>sh ip bgp regexp _3561_
BGP table version is 15604957, local router ID is 209.1.220.234
Status codes: s suppressed, d damped, h history, * valid, > best, i -
internal
Origin codes: i - IGP, e - EGP, ? - incomplete

   Network          Next Hop            Metric LocPrf Weight Path
* i3.0.0.0          209.1.40.148                 1000      0 3561 1239 80
i
* i                 209.1.220.242                1000      0 3561 1239 80
i
* i                 209.1.220.102                1000      0 3561 1239 80
i
* i                 209.1.220.9                  1000      0 3561 1239 80
i
* i3.18.135.0/24    209.1.220.102                1000      0 3561 7018 ?
* i                 209.1.220.9                  1000      0 3561 7018 ?
* i4.0.0.0          209.1.40.148                 1000      0 3561 1 i
* i                 209.1.220.174                1000      0 3561 1 i
* i                 209.1.220.102                1000      0 3561 1 i
* i                 209.1.220.242                1000      0 3561 1 i
* i                 209.1.220.133                1000      0 3561 1 i
* i                 209.1.40.72                  1000      0 3561 1 i
* i                 209.1.40.141                 1000      0 3561 1 i
* i                 209.1.220.9                  1000      0 3561 1 i
* i                 209.1.220.102                1000      0 3561 1 i
* i                 209.1.220.9                  1000      0 3561 1 i
* i6.0.0.0/20       209.1.40.148                 1000      0 3561 3549 i
* i                 209.1.220.156                1000      0 3561 3549 i
* i                 209.1.220.242                1000      0 3561 3549 i
* i                 209.1.40.72                  1000      0 3561 3549 i
* i                 209.1.40.141                 1000      0 3561 3549 i
* i                 209.1.220.174                1000      0 3561 3549 i
* i9.2.0.0/16       209.1.40.148                 1000      0 3561 701 i
* i                 209.1.220.174                1000      0 3561 701 i

> need to maintain separate peering circuits; this is probably just a step in the
> eventual assimilation of Exodus' IP backbone into C&W's.
>
> -C

What I don't know is what they are going to do with their private peers ?
Does somebody has a clue on this ?

>