Re: XO Peering Question..

[Joshua McDonald]

I am seeing a MED of 3 from XO.

Josh


> On Jan 8, 2015, at 11:31 AM,  
>  wrote:
> 
> Hey All,
> Quick question for those of you who may be pulling a partial or full table 
> from XO..
> 
> Can you tell me your MED/Weight on the routes from them?
> 
> Please and Thank you.
> 
> 
> 
> 
> [cid:62CA825B-35AD-469A-B224-9BA199DC5662]GREGORY S CROFT Information 
> Security Engineer
> gcr...@unitedshore.com
> p 855.888.8737 ext.4999
> p 248.833.4999
> UNITEDSHORE.COM
> 
> 
> United to better serve you.
> Share your experience at 
> mymana...@unitedshore.com
> 
> The contents of this message may be confidential. If you are not the intended 
> recipient, do not disseminate, disclose, copy or use this message without the 
> permission of the author. Nothing contained in this message or in any 
> attachment shall satisfy the requirements for a writing, and nothing 
> contained herein shall constitute a contract or electronic signature. If this 
> message has been received in error, please delete it immediately.



signature.asc
Description: Message signed with OpenPGP using GPGMail

XO Peering Question..

[gcroft]

Hey All,
Quick question for those of you who may be pulling a partial or full table from 
XO..

Can you tell me your MED/Weight on the routes from them?

Please and Thank you.




[cid:62CA825B-35AD-469A-B224-9BA199DC5662]GREGORY S CROFT Information Security 
Engineer
gcr...@unitedshore.com
p 855.888.8737 ext.4999
p 248.833.4999
UNITEDSHORE.COM


United to better serve you.
Share your experience at 
mymana...@unitedshore.com

The contents of this message may be confidential. If you are not the intended 
recipient, do not disseminate, disclose, copy or use this message without the 
permission of the author. Nothing contained in this message or in any 
attachment shall satisfy the requirements for a writing, and nothing contained 
herein shall constitute a contract or electronic signature. If this message has 
been received in error, please delete it immediately.

AT&T - XO Peering (AS7018 and AS2828)

[Patrick Sumby]

Hi,

Please could someone from ATT and/or XO contact me off list to discuss 
some issues we've been seeing on a link between AS7018 and AS2828.


Thanks
Pat

--
---
Patrick Sumby
Director of Global Engineering
Sohonet

RE: XO peering.

[Jake Mertel]

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:ober...@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
> em...@xo.com
> 
> 
> -Original Message-
> From: Jake Mertel [mailto:j...@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:jmarti...@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: ober...@es.net   Phone: +1 510-486-8634

RE: XO peering.

[Kevin Oberman]

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
> em...@xo.com
> 
> 
> -Original Message-
> From: Jake Mertel [mailto:j...@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:jmarti...@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: ober...@es.net   Phone: +1 510-486-8634


signature.asc
Description: This is a digitally signed message part

Re: XO peering.

[ChrisSerafin]

Our office has XO, and sent an email out complainging about 
Salesforce.In Chicago.


--chris

Stefan Molnar wrote:


It just cleared up for me.  Nice to have a call center complain 
constantly.


Thanks

On Tue, 10 Mar 2009, Suresh Ramasubramanian wrote:

On Tue, Mar 10, 2009 at 9:35 PM, 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.


This is from a host in XO AS2828

I can reach, for example, www.verio.net 204.202.20.3 / AS2914
NTT-COMMUNICATIONS-2914 just fine.

www.salesforce.com is also reachable, through NTT

--
Suresh Ramasubramanian (ops.li...@gmail.com)






No virus found in this incoming message.
Checked by AVG - www.avg.com 
Version: 8.0.237 / Virus Database: 270.11.9/1993 - Release Date: 03/10/09 07:19:00


  

Re: XO peering.

[Stefan Molnar]

It just cleared up for me.  Nice to have a call center complain 
constantly.


Thanks

On Tue, 10 Mar 2009, Suresh Ramasubramanian wrote:


On Tue, Mar 10, 2009 at 9:35 PM, 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.


This is from a host in XO AS2828

I can reach, for example, www.verio.net 204.202.20.3 / AS2914
NTT-COMMUNICATIONS-2914 just fine.

www.salesforce.com is also reachable, through NTT

--
Suresh Ramasubramanian (ops.li...@gmail.com)

RE: XO peering.

[Mort, Eric]

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
em...@xo.com


-Original Message-
From: Jake Mertel [mailto:j...@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:jmarti...@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
>

Re: XO peering.

[John Martinez]

Do you have the XO ticket number?

Jake Mertel wrote:
> 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:jmarti...@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
>>
> 
> 
> 

RE: XO peering.

[Jake Mertel]

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:jmarti...@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
>

Re: XO peering.

[John Martinez]

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
> 

Re: XO peering.

[Suresh Ramasubramanian]

On Tue, Mar 10, 2009 at 9:35 PM, 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.

This is from a host in XO AS2828

I can reach, for example, www.verio.net 204.202.20.3 / AS2914
NTT-COMMUNICATIONS-2914 just fine.

www.salesforce.com is also reachable, through NTT

-- 
Suresh Ramasubramanian (ops.li...@gmail.com)

XO peering.

[Stefan Molnar]

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