Comments on: Outages at Paypal, Mozilla, DreamHost, MT http://www.datacenterknowledge.com/archives/2008/03/23/outages-at-paypal-mozilla-dreamhost-mt/ News and analysis about data centers, cloud computing, managed hosting and disaster recovery Mon, 13 Feb 2012 17:24:17 +0000 hourly 1 http://wordpress.org/?v= By: Mike Sullivan http://www.datacenterknowledge.com/archives/2008/03/23/outages-at-paypal-mozilla-dreamhost-mt/comment-page-1/#comment-288 Mike Sullivan Mon, 24 Mar 2008 14:30:15 +0000 http://dev.datacenterknowledge.com/archives/2008/03/23/outages-at-paypal-mozilla-dreamhost-mt/#comment-288 Netflix.com has been down for at least a few hours on Monday morning. First the site sent back "Service Unavailable" errors, and now it is resetting connections without loading any pages. Netflix.com has been down for at least a few hours on Monday morning. First the site sent back “Service Unavailable” errors, and now it is resetting connections without loading any pages.

]]> By: Douglas Gourlay http://www.datacenterknowledge.com/archives/2008/03/23/outages-at-paypal-mozilla-dreamhost-mt/comment-page-1/#comment-287 Douglas Gourlay Mon, 24 Mar 2008 07:44:43 +0000 http://dev.datacenterknowledge.com/archives/2008/03/23/outages-at-paypal-mozilla-dreamhost-mt/#comment-287 The blade-switch error is not uncommon. One of our best engineers was at a customer site where the customer was complaining that their network was performing slowly. A detailed look showed that one of the Blade Switches (vendor to remain nameless, but not from us) had decided it wanted to be the root bridge for the entire L2 domain. A few ways to solve this- 1) hard code the priority 2) set 'Root Guard' on in the aggregation switches 3) design Spanning-Tree out of the network as a topology bound protocol (getting harder because of server virtualization) Not an uncommon event though, so worth checking into in many infrastructures where blade switches may be rather 'haphazardly' deployed. dg The blade-switch error is not uncommon. One of our best engineers was at a customer site where the customer was complaining that their network was performing slowly. A detailed look showed that one of the Blade Switches (vendor to remain nameless, but not from us) had decided it wanted to be the root bridge for the entire L2 domain.

A few ways to solve this-

1) hard code the priority

2) set ‘Root Guard’ on in the aggregation switches

3) design Spanning-Tree out of the network as a topology bound protocol (getting harder because of server virtualization)

Not an uncommon event though, so worth checking into in many infrastructures where blade switches may be rather ‘haphazardly’ deployed.

dg

]]>