[112601] in North American Network Operators' Group
RE: XO peering.
daemon@ATHENA.MIT.EDU (Kevin Oberman)
Tue Mar 10 15:41:18 2009
From: Kevin Oberman <oberman@es.net>
To: "Mort, Eric" <EMort@xo.com>
In-Reply-To: <2E209CF1536C0C42A260E215DA598E9606373D4B@TXPLANMAIL02.mail.inthosts.net>
Date: Tue, 10 Mar 2009 12:40:51 -0700
Cc: nanog@nanog.org
Errors-To: nanog-bounces@nanog.org
--=-jB9lQxDkJYwbiQXchpJ/
Content-Type: text/plain
Content-Transfer-Encoding: quoted-printable
On Tue, 2009-03-10 at 11:41 -0500, Mort, Eric wrote:
> We had some hardware issues in San Jose which triggered some other
> ugliness. We believe we have the issues mitigated at this time. Folks
> still seeing issues are encouraged to hit me up offline.
>=20
> Thanks,
>=20
> Eric J. Mort
> XO Communications
> Sr. Manager - IP Operations
> Desk - 314-787-7826
> Cell - 314.486-9057
> emort@xo.com
>=20
>=20
> -----Original Message-----
> From: Jake Mertel [mailto:jake@nobistech.net]=20
> Sent: Tuesday, March 10, 2009 11:34 AM
> To: John Martinez; nanog@nanog.org
> Subject: RE: XO peering.
>=20
> We had a number of issues in the Seattle area this morning, seemed to be
> isolated to traffic transiting via Level 3. We were forced to turn off
> the connection, and it's still disabled until we get an update from XO.=20
>=20
>=20
> --
> Regards,
>=20
> Jake Mertel
> Nobis Technology Group, L.L.C.
>=20
>=20
>=20
> Web: http://www.nobistech.net/
> Phone: (312) 281-5101 ext. 401
> Fax: (808) 356-0417
>=20
> Mail: 201 West Olive Street
> Second Floor, Suite 2B
> Bloomington, IL 61701
>=20
>=20
> -----Original Message-----
> From: John Martinez [mailto:jmartinez@zero11.com]=20
> Sent: Tuesday, March 10, 2009 11:23 AM
> To: nanog@nanog.org
> Subject: Re: XO peering.
>=20
> We saw an issue with Level 3 hand off to XO in Chicago.
>=20
> Stefan Molnar wrote:
> >
> > There was a peering issue in San Jose with XO, that impacted our
> > operations this morning. But looks like a side effect is after the
> hand
> > off to NTT.
> >
> > Anyone who has an XO link can reach areas insdie NTT?
> >
> > As an example our route to Salesforce /21 is via NTT and it is not
> happy
> > right now.
> >
> > Thanks,
> > Stefan
> >
>=20
>=20
>=20
>=20
>=20
>=20
>=20
No joy from our (AS293) perspective. I still see traffic to XO at SJ
black-holed.
eqx-sj-rt1-re1> traceroute 198.17.75.45=20
traceroute to 198.17.75.45 (198.17.75.45), 30 hops max, 40 byte packets
^C
Works fine from Ashburn, though. I've pref'ed XO down at SJ until it is
working again.
--=20
R. Kevin Oberman
Energy Sciences Network (ESnet)
Ernest Orlando Lawrence Berkeley National Laboratory (Berkeley Lab)
E-Mail: oberman@es.net Phone: +1 510-486-8634
--=-jB9lQxDkJYwbiQXchpJ/
Content-Type: application/pgp-signature; name="signature.asc"
Content-Description: This is a digitally signed message part
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2.0.11 (FreeBSD)
iEYEABECAAYFAkm2wkMACgkQkn3rs5h7N1HJwACff2ES1jvvPTtRNCijce7avUnd
RP0AmwW7WfwA29Xu8ssSPXZg6ltECHIb
=xRsI
-----END PGP SIGNATURE-----
--=-jB9lQxDkJYwbiQXchpJ/--
