> If a single device brings down your entire data center, you've got design problems and your architect should be fired or retrained.
Please: if your data center has the time, and skill, and is willing to take the service interruptions to make the whole setup properly immune to single points of failure, that's great. But very, very few live business environments have that kind of resource, time, and willingness to enable critical switches with robust failover.
As other posters have mentioned the level of switches discussed by op are not DC switches. SMB switches, sure, but enterprise datacenter, no.
blah blah blah
Reality is single device failures bring down large chunks of the net including valuable peers of your "enterprise datacenter"
Of course, sometimes identical cisco models used in redundant tuples also cause outages together after upgrade by common bug that didn't show up in test
so pontificate all you want, you're vulnerable to a lot of bad things
(1) I guarantee if you emailed that explanation to a DC manager you'd be shitcanned. I agree that we are all vulnerable to bad things, but avoidance of a single point of failure device in the DC like op highlights is network ops 101 stuff.
(2) Show me a datacenter that's an all cisco shop. Most are whitebox/greybox now. Welcome to the 21st century. Most "big-data" shops have firmware experts who know their hardware down to the MMU register level and order stuff directly from places like Taiwan with nary a CCIE to be found in corporate ranks.
Hackers have followed through on a threat to release online a huge cache of data, including customer information, that was stolen a month ago from cheating spouses website AshleyMadison.com, several tech websites reported on Tuesday.
Adding features does not necessarily increase functionality -- it just makes the manuals thicker.