RE: Heads-Up: GoDaddy Broke the Interwebs...
Looks like this may be a DDoS attack from Anonymous: http://techcrunch.com/2012/09/10/godaddy-outage-takes-down-millions-of-sites/ -Original Message- From: Aaron C. de Bruyn [mailto:aa...@heyaaron.com] Sent: Monday, September 10, 2012 1:07 PM To: NANOG mailing list Subject: Heads-Up: GoDaddy Broke the Interwebs... For the last ~15 minutes I've been receiving complaints about DNS issues. GoDaddy DNS is apparently b0rked. I'm also seeing a lot of tweets about their hosting and VPS being down. I'm unable to access the control panel for one of my customer accounts. -A
RE: Redundant Routes, BGP with MPLS provider
I think having a GRE tunnel for the internal routing protocol is unnecessary. Can you explain the reasoning behind this? I understand the technical issue whereby GRE will allow multicast for EIGRP, OSPF, etc, but why not just redistribute into BGP? I work on a lot of MPLS CE routers, and in general you can accomplish anything you need by redistributing your internal routing protocol into BGP, and adjusting LP, MED and AS Prepend as needed. Thanks, Bill -Original Message- From: Lee [mailto:ler...@gmail.com] Sent: Friday, August 31, 2012 11:15 AM To: Tribble, Wesley Cc: nanog@nanog.org Subject: Re: Redundant Routes, BGP with MPLS provider On 8/30/12, Tribble, Wesley wtrib...@sterneagee.com wrote: Hello all, I am an Network Operator working in an Enterprise environment with offices all over the country(mostly connected via MPLS). We are currently working towards building a Disaster Recovery Site that will host some of our vendor routers and provide the capability to access these vendors from both our primary and backup data center locations. The routes(as advertised by the vendor's routers) will be the same at both locations. I would like to advertise the routes from multiple locations at the same time, rather than suppress the routes and advertise conditionally. At work, we have our internal routing protocol running on GRE over IPSec tunnels keep the BGP sessions with the MPLS provider limited to just the MPLS network. And have an ACL on the MPLS network interface that allows only what's expected in... some providers are better than others at not having anything hit the 'deny any any log' line Regards, Lee What is the best method to Instruct the provider's network to prefer the Primary Data Center routes over the DR site? Keep in mind that I am only peering with the provider over BGP and I have no visibility to the underlying MPLS architecture or configuration. Although if you have specific questions about their architecture, I can work to get answers. Discussing in house, we have gone over a few different options: -Advertise specific routes from primary site and summary routes from the DR site. Most specific will always be chosen. -Prepend the routes from the DR site so that they will have a longer AS-path than the Primary location -Use Community Strings to influence local preference.(Still working to find out if Provider will pass our community strings) Just looking for some ideas and best practices. Any thoughts or insight would be much welcomed and appreciated. This is my first message on NANOG, so please be gentle. I apologize in advance if I have done something incorrectly. Wes ** Sterne Agee Group, Inc. and its subsidiaries request that you do not transmit orders and instructions regarding your Sterne Agee account by e-mail. Transactional details do not supersede normal trade confirmations or statements. The information contained in this transmission is privileged and confidential. It is intended for the use of the individual or entity named above. The information contained herein is based on sources we believe reliable but is not considered all-inclusive. Opinions are our current opinions only and are subject to change without notice. Offerings are subject to prior sale and/or change in price. Prices, quotes, rates and yields are subject to change without notice. Sterne Agee Leach, Inc. member FINRA and SIPC, is a registered broker-dealer subsidiary of Sterne Agee Group, Inc. Generally, investments are NOT FDIC INSURED, NOT BANK GUARANTEED, and MAY LOSE VALUE. Please contact your Financial Advisor with information regarding specific investments. Sterne Agee reserves the right to monitor all electronic correspondence. **
RE: Redundant Routes, BGP with MPLS provider
I work for an MPLS provider, so I guess I tend to trust them ;) Bill -Original Message- From: Lee [mailto:ler...@gmail.com] Sent: Friday, August 31, 2012 11:28 AM To: Ingrum, Bill Cc: wtrib...@sterneagee.com; nanog@nanog.org Subject: Re: Redundant Routes, BGP with MPLS provider On 8/31/12, bill.ing...@t-systems.com bill.ing...@t-systems.com wrote: I think having a GRE tunnel for the internal routing protocol is unnecessary. It might be, but we have a requirement for multicast over the wan so the GRE tunnels had to be there. Can you explain the reasoning behind this? I understand the technical issue whereby GRE will allow multicast for EIGRP, OSPF, etc, but why not just redistribute into BGP? I see no reason to trust the provider that much. I work on a lot of MPLS CE routers, and in general you can accomplish anything you need by redistributing your internal routing protocol into BGP, and adjusting LP, MED and AS Prepend as needed. Sure.. but how do you *know* you're not getting anything added/removed by the provider? Lee Thanks, Bill -Original Message- From: Lee [mailto:ler...@gmail.com] Sent: Friday, August 31, 2012 11:15 AM To: Tribble, Wesley Cc: nanog@nanog.org Subject: Re: Redundant Routes, BGP with MPLS provider On 8/30/12, Tribble, Wesley wtrib...@sterneagee.com wrote: Hello all, I am an Network Operator working in an Enterprise environment with offices all over the country(mostly connected via MPLS). We are currently working towards building a Disaster Recovery Site that will host some of our vendor routers and provide the capability to access these vendors from both our primary and backup data center locations. The routes(as advertised by the vendor's routers) will be the same at both locations. I would like to advertise the routes from multiple locations at the same time, rather than suppress the routes and advertise conditionally. At work, we have our internal routing protocol running on GRE over IPSec tunnels keep the BGP sessions with the MPLS provider limited to just the MPLS network. And have an ACL on the MPLS network interface that allows only what's expected in... some providers are better than others at not having anything hit the 'deny any any log' line Regards, Lee What is the best method to Instruct the provider's network to prefer the Primary Data Center routes over the DR site? Keep in mind that I am only peering with the provider over BGP and I have no visibility to the underlying MPLS architecture or configuration. Although if you have specific questions about their architecture, I can work to get answers. Discussing in house, we have gone over a few different options: -Advertise specific routes from primary site and summary routes from the DR site. Most specific will always be chosen. -Prepend the routes from the DR site so that they will have a longer AS-path than the Primary location -Use Community Strings to influence local preference.(Still working to find out if Provider will pass our community strings) Just looking for some ideas and best practices. Any thoughts or insight would be much welcomed and appreciated. This is my first message on NANOG, so please be gentle. I apologize in advance if I have done something incorrectly. Wes * * Sterne Agee Group, Inc. and its subsidiaries request that you do not transmit orders and instructions regarding your Sterne Agee account by e-mail. Transactional details do not supersede normal trade confirmations or statements. The information contained in this transmission is privileged and confidential. It is intended for the use of the individual or entity named above. The information contained herein is based on sources we believe reliable but is not considered all-inclusive. Opinions are our current opinions only and are subject to change without notice. Offerings are subject to prior sale and/or change in price. Prices, quotes, rates and yields are subject to change without notice. Sterne Agee Leach, Inc. member FINRA and SIPC, is a registered broker-dealer subsidiary of Sterne Agee Group, Inc. Generally, investments are NOT FDIC INSURED, NOT BANK GUARANTEED, and MAY LOSE VALUE. Please contact your Financial Advisor with information regarding specific investments. Sterne Agee reserves the right to monitor all electronic correspondence. ** ** **
RE: Colocation in New York for a POP
+1 for 60 Hudson -Original Message- From: Andrew Mulholland [mailto:andy-na...@bash.sh] Sent: Thursday, April 19, 2012 4:03 PM To: Paul WALL Cc: nanog@nanog.org Subject: Re: Colocation in New York for a POP at $JOB-2 we had a couple of racks in 60 Hudson St, which worked well On Thu, Apr 19, 2012 at 10:50 PM, Paul WALL pauldotw...@gmail.com wrote: Stay away from the NYIIX. It goes down every month or two, and its current management is not competent. There are plenty of competitive options, including Equinix and Telx/TIE (which is free or close to it). Drive Slow, Paul Wall On 4/19/12, Abdelkader Chikh Daho achikhd...@iweb.com wrote: Hi everyone, Can some one please tell us what is the best Colo in New york to set up a POP (one cabinet) in order to get bandwidth, peering (NIIX, etc). Best regards, -- Abdelkader Chikh Daho Network Architect iWeb Technologies Email : achikhd...@iweb.com Web : www.iweb.com Tel : 514-286-4242 ext 2309
RE: fiber cut in California?
https://puck.nether.net/pipermail/outages/2012-April/003852.html -Original Message- From: Greg Olson [mailto:gol...@markettools.com] Sent: Thursday, April 19, 2012 4:49 PM To: nanog@nanog.org Subject: fiber cut in California? Anyone hear of a fiber cut in California today?
