[OCCAID] routing in atlanta (not related to current down time)

[James Jun]

We actually do peer with Host.net at Atlanta.  The problem however is,
OCCAID is a simultaneous peer and customer of Host.net (rare, but such cases
happen when bgp relationship between two parties is more than just a simple
'customer/business relationship').

The Host.net-OCCAID transfer network in Miami is used for transit/customer
relationship, where as transfer network in Atlanta is used for exchanging
customer routes for peering only.  It's a complicated setup that needs to be
corrected, and it is on our long list of to-do and we are aware of this
issue.

On a separate issue, I see that your traceroute is from gnax.net.  OCCAID
peers with GNAX last I checked over ATL-IX, so you may want to check with
GNAX to see what the story is there..  And yes, we peer with many ISPs over
IPv4, so they can access IPv6 tunnel points faster for their customers.
When we dual-stack our network soon with OCCAID2 project, we will be
announcing ipv6 service points all across our network at locations like
LINX, etc.

But... since enough users noticed it now, we'll work on getting this fixed
soon, but we'll need to find a new server for SixXS Atlanta first as current
sixxs server died this morning.

Regards,

James Jun
IP Infrastructure & Technology Services
TowardEX Technologies, Inc.
WWW: http://www.towardex.com
Email: james at towardex.com
Office: +1 (617) 459-4051 Ext. 179
Mobile: +1 (978) 394-2867

> -----Original Message-----
> From: occaid-bounces at cnacs.occaid.org [mailto:occaid-
> bounces at cnacs.occaid.org] On Behalf Of James Cloos
> Sent: Thursday, February 16, 2006 12:12 AM
> To: occaid at cnacs.occaid.org
> Subject: [OCCAID] routing in atlanta (not related to current down time)
> 
> Check out this traceroute from a box in Atlanta to the sixxs pop:
> 
> ,----
> | :; traceroute -I usatl01.sixxs.net
> | traceroute to usatl01.sixxs.net (216.10.93.2), 30 hops max, 40 byte
> packets
> |  1  169.254.1.1 (169.254.1.1)  0.163 ms  0.100 ms  0.046 ms
> |  2  207.210.96.1 (207.210.96.1)  0.459 ms  0.413 ms  0.213 ms
> |  3  gnax-atl-KalahariLimited-dsl-wan1-gnax.net (209.51.131.101)  0.742
> ms  7.689 ms  16.690 ms
> |  4  209.51.131.5 (209.51.131.5)  0.856 ms  0.729 ms  0.757 ms
> |  5  209.51.149.106 (209.51.149.106)  1.029 ms  16.333 ms  1.709 ms
> |  6  ge2-0.cr0.atl.ga.host.net (198.32.132.31)  0.812 ms  0.512 ms  0.632
> ms
> |  7  ge6-0.cr0.mia.fl.host.net (64.135.0.121)  12.083 ms  12.518 ms
> 12.880 ms
> |  8  ge5-0.cr1.mia.fl.host.net (64.135.0.106)  12.739 ms  12.479 ms
> 13.392 ms
> |  9  occaid-mia1.host.net (64.135.20.214)  12.988 ms  13.573 ms  12.614
> ms
> | 10  10.ge0-0.cr1.atl1.us.occaid.net (216.93.254.128)  12.992 ms  12.956
> ms  12.890 ms
> | 11  * 10.ge0-0.cr1.atl1.us.occaid.net (216.93.254.128)  13.987 ms !N
> 14.887 ms !N
> `----
> 
> I know the pop is down right now, but the traceroutes showed the same
> path before it went down.
> 
> As you can see, in hop 6 it gets to host.net in atlanta, but then goes
> to miami and back to get to occaid.
> 
> Is there any chance of a direct link between atl.ga.host.net (which
> looks to be at AtlantaIX, given the 198.32.0.0/16 address) and
> atl1.us.occaid.net?
> 
> The occaid network map shows a link to AtlantaIX.  Shouldn't this
> route there?  Or is it that you need to add a peering relationship
> at AtlIX with the AS my box is in?  (I believe that is gnax.net.)
> 
> Or that you only do v6 peering there?  (Iff so, v4 peering for the
> benefit of the tunnel pop would be "way cool". :)
> 
> -JimC
> --
> James H. Cloos, Jr. <cloos at jhcloos.com>
> _______________________________________________
> OCCAID Mailing List
> November 1, 2005: OCCAID 5th Year Anniversary!
> 
> http://www.occaid.org
> 
> Occaid at cnacs.occaid.org is the list posting address.
> db-admin at cnacs.occaid.org is the human contact address.
> See below URL for subscribe/unsubscribe and list options:
> http://mailman.twdx.net/mailman/listinfo/occaid