I did some preliminary tests static-routing some prefixes that were not working earlier over our XO connection and everything seemed fine. I went ahead and turned the session back up, no reports of trouble yet. I'll update if we have any issues. -- Regards, Jake Mertel Nobis Technology Group, L.L.C. Web: http://www.nobistech.net/ Phone: (312) 281-5101 ext. 401 Fax: (808) 356-0417 Mail: 201 West Olive Street Second Floor, Suite 2B Bloomington, IL 61701 -----Original Message----- From: Kevin Oberman [mailto:oberman@es.net] Sent: Tuesday, March 10, 2009 2:41 PM To: Mort, Eric Cc: Jake Mertel; John Martinez; nanog@nanog.org Subject: RE: XO peering. 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.
Thanks,
Eric J. Mort XO Communications Sr. Manager - IP Operations Desk - 314-787-7826 Cell - 314.486-9057 emort@xo.com
-----Original Message----- From: Jake Mertel [mailto:jake@nobistech.net] Sent: Tuesday, March 10, 2009 11:34 AM To: John Martinez; nanog@nanog.org Subject: RE: XO peering.
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.
-- Regards,
Jake Mertel Nobis Technology Group, L.L.C.
Web: http://www.nobistech.net/ Phone: (312) 281-5101 ext. 401 Fax: (808) 356-0417
Mail: 201 West Olive Street Second Floor, Suite 2B Bloomington, IL 61701
-----Original Message----- From: John Martinez [mailto:jmartinez@zero11.com] Sent: Tuesday, March 10, 2009 11:23 AM To: nanog@nanog.org Subject: Re: XO peering.
We saw an issue with Level 3 hand off to XO in Chicago.
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
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 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. -- 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