Monthly Archives: July 2011

Mazzola’s Next Move

I’ve written previously about Mario Mazzola, Luca Cafiero, and Prem Jain, Cisco’s triumvirate of engineering maestros. My last post in which they figured prominently dealt with Cisco’s seeming retirement of its spin-in move.

Explaining the Spin-In

For those not familiar with the spin-in concept, I will now quote from my earlier post:

 “Such deals typically involve a parent company, such as Cisco, allowing a team of engineers and business managers to leave the corporate nest to create breakthrough products and technologies. These arm’s-length ventures are funded by the parent company exclusively or sometimes by the parent company and other investors, such as VCs. The parent company’s ownership ratio of the venture increases as technology milestones and business objectives are reached, until eventually the venture is spun, in its entirely, back into the mothership. Hence, the term “spin in.”

Cisco executed a number of spin-in arrangements, but its best-known examples involved storage-networking startup Andiamo Systems, which Cisco officially acquired in the summer of 2002, and Nuova Systems, which Cisco finally acquired in full in the spring of 2008.

The companies had more than their spin-in natures in common. Both were led by Mario Mazzola, Cisco’s on-again-off-again chief development officer (CDO). What’s more, the teams at both companies included many of the same players, namely Luca Cafiero, Prem Jain, and Soni Jiandani.”

Startup Rumor

I wrote that post last summer, and, while Soni Jiandani remains in a prominent executive position at Cisco, serving as senior vice president for server access and virtualization, the other three — Mazzola, Cafiero, and Jain — are the subject of rumors.

According to unconfirmed reports, Mazzola is leading another startup effort. Cafiero and Jain might be joining him. I don’t know what this alleged startup might do, but some say it initially might function as an incubator/VC operation, on its own or perhaps in league with another Silicon Valley VC outfit.

Spin-In Unlikely

It is not thought to be another Cisco spin-in. Given the substantial layoffs John Chambers is overseeing currently at Cisco, it would be difficult for him to sell investors, analysts, and — last but not least — employees on the merits of a high-priced spin-in maneuver that would make a few people richer than Croesus while  others are being escorted to the door and entire business operations within Cisco are facing extinction.

That’s not to say it won’t happen — Cisco and Chambers could argue that a particular spin-in initiative is absolutely essential to the company’s renovated strategic vision — but the odds are not in its favor.

Regardless of whether Mazzola is fronting a standalone startup or yet another Cisco spin-in venture, it will be interesting to see what he does next.

ONF Board Members Call OpenFlow Tune

The concept of software-defined networking (SDN) has generated considerable interest during the last several months.  Although SDNs can be realized in more than one way, the OpenFlow protocol seems to have drawn a critical mass of prospective customers (mainly cloud-service providers with vast data centers) and solicitous vendors.

If you aren’t up to speed with the basics of software-defined networking and OpenFlow, I suggest you visit the Open Networking Foundation (ONF) and OpenFlow websites to familiarize yourself the underlying ideas.  Others have written some excellent articles on the technology, its perceived value, and its potential implications.

In a recent piece he wrote originally for GigaOm, Kyle Forster of Big Switch Networks offers this concise definition:

Concisely Defined

“At its most basic level, OpenFlow is a protocol for server software (a “controller”) to send instructions to OpenFlow-enabled switches, where these instructions give direct control over how those switches forward traffic through the network.

I think of OpenFlow like an x86 instruction set for the network – it’s low-level, but it’s very powerful. Continuing that analogy, if you read the x86 instruction set for the first time, you might walk away thinking it could be useful if you need to build a fancy calculator, but using it to build Linux, Apache, Microsoft Word or World of Warcraft wouldn’t exactly be obvious. Ditto for OpenFlow. It isn’t the protocol that is interesting by itself, but rather all of the layers of software that are starting to emerge on top of it, similar to the emergence of operating systems, development environments, middleware and applications on top of x86.”

Increased Network Functionality, Lower Network Operating Costs

The Open Networking Foundation’s charter summarizes its objectives and the value proposition that advocates of SDN and OpenFlow believe they can deliver:

 “The Open Networking Foundation is a nonprofit organization dedicated to promoting a new approach to networking called Software-Defined Networking (SDN). SDN allows owners and operators of networks to control and manage their networks to best serve their users’ needs. ONF’s first priority is to develop and use the OpenFlow protocol. Through simplified hardware and network management, OpenFlow seeks to increase network functionality while lowering the cost associated with operating networks.”

That last part is the key to understanding the composition of ONF’s board of directors, which includes Deutsche Telecom, Facebook, Google, Microsoft, Verizon, and Yahoo. All of these companies are major cloud-service providers with multiple, sizable data centers. (Yes, Microsoft also is a cloud-technology purveyor, but what it has in common with the other board members is its status as a cloud-service provider that owns and runs data centers.)

Underneath the board of directors are member companies. Most of these are vendors seeking to serve the needs of the ONF board members and similar cloud-service providers that share their business objective: boosting network functionality while reducing the costs associated with network operations.

Who’s Who of Networking

Among the vendor members are a veritable who’s who of the networking industry: Cisco, HP, Juniper, Brocade, Dell/Force10, IBM, Huawei, Nokia Siemens Networks, Riverbed, Extreme, and others. Also members, not surprisingly, are virtualization vendors such as VMware and Citrix, as well as the aforementioned Microsoft. There’s a smattering of SDN/OpenFlow startups, too, such as Big Switch Networks and Nicira Networks.

Of course, membership does not necessarily entail avid participation. Some vendors, including Cisco, likley would not be thrilled at any near-term prospect of OpenFlow’s widespread market adoption. Cisco would be pleased to see the networking status quo persist for as long as possible, and its involvement in ONF probably is more that of vigilant observer than of fervent proponent. In fact, many vendors are taking a wait-and-see approach to OpenFlow. Some members, including Force10, are bearish and have suggested that the protocol is a long way from delivering the maturity and scalability that would satisfy enterprise customers.

Vendors Not In Charge

Still, the board members are steering the ONF ship, not the vendors. Regardless of when OpenFlow or something like it comes of age, the rise of software-defined networking seems inevitable. Servers and storage gear have been virtualized and have become more application-driven, but networks haven’t changed much in the last several years. They’re faster, yes, but they’re still provisioned in the traditional manner, configured rather than programmed. That takes time, consumes resources, and costs money.

Major cloud-service providers, such as those on the ONF board, want network infrastructure to become more elastic, flexible, and dynamic. Vendors will have to respond accordingly, whether with OpenFlow or with some other approach that delivers similar operational outcomes and business benefits.

I’ll be following these developments closely, watching to see how the business concerns of the cloud providers and the business interests of the networking-vendor community ultimately reconcile.

Cisco and RIM: Hard Times, Different Situations

A morbid debate has ensued as to whether Cisco or RIM is in worse shape. It’s an unseemly discourse, but it seems obvious to me that Cisco, regardless of its current woes, remains in a better, stronger position than RIM, both today and well into the future.

That said, let me be absolutely clear that I believe Cisco has entered a period of decline, perhaps of the irrevocable sort. The broad industry trends — commoditized wiring-closet switches, stiff competition in the data center and the network core, the rise of cloud computing, and so forth — are not its friends. To make matters worse, Cisco is suffering from its own imperial overstretch, and from a cultural malaise that afflicts and challenges all big corporations that reach a certain stage of maturity.

Not the Same

This Cisco, the one you see today, is not the one that ruled the networking industry late in the last century and early in this one. That beast, which seemed so unstoppable on its path to dominance — capturing and keeping customers, charming partners,  drawing prospective suppliers, and dazzling industry analysts — seems to have left the building. It has the same head, figuratively and literally, but it’s uncoordinated now and tends to get in its own way at least as often as it bulldozes the competition.

Even so, Cisco is a long way from dead. It has a prodigious installed base of customers, some major partnerships that still matter, and a chance to step back, reflect on what’s happening in the market, and alter course accordingly. It won’t be easy — some believe Cisco’s leadership is better at building than fixing  – but Cisco need not slide into an industry abyss.

RIM, too, has an opportunity for renewal, but its situation is far more daunting. As with Cisco, the trends — an app-driven market dynamic; consumerization of IT and “bring your own device” (BYOD) to work; the strength of Apple at the high end of the smartphone market, Google Android nearly everywhere else, and low-cost competitors in the developing world; the rise of mobile-device-management (MDM) suites that can support heterogeneous mobile platforms — are not in its favor. Also like Cisco, RIM has lost its way, failing to recognize foreboding trends and lethal competitors until serious damage had been done.

Bigger Challenges, Fewer Resources

Still, RIM is worse off in many respects. First, it’s no longer an industry leader. It’s been usurped by Google’s Android and by Apple in smartphones, and there’s a danger that Microsoft, and perhaps even HP, could knock it further down the charts. Cisco, notwithstanding its current hardships, doesn’t have that problem; it’s still number one in enterprise networking (switching and routing), though competitors are chipping away at its market share and it has lost ground in other important, faster-growing markets, such as the application delivery controller (ADC) space, where F5 leads.

Furthermore, Cisco still has customers that will buy into the brand and the higher prices that accompany it. That could change — nearly everything can change — but Cisco retains that benefit today. There might fewer of those customers than there were a couple years ago, but the population of Ciscotown remains considerable. Unfortunately for RIM, the brand-equity die has been cast, and it has suffered a decline not only in the eyes of consumers but in many enterprises as well. Apple iPhones and iPads are proliferating in enterprise settings and vertical markets, often supplanting BlackBerry devices, at a rate few predicted.

RIM also has fewer resources than Cisco. True, it’s fighting competitive battles on fewer fronts than the networking giant, but Cisco has the option of reining in its aspirations and allocating its ample resources with greater strategic focus. RIM can only do so much.

Mitigate Risk or Roll Dice?

It’s ironic that, just a short time ago, some analysts and pundits were suggesting that Cisco buy RIM. My point is not to mock them — this industry will humble anybody who tries to predict its course — but to illustrate just how much a combination of strategic missteps and the vagaries of fate can change the game in relatively short order.

The best anybody out there can do is to find a balance between risk mitigation and success probability, which often (but not always) are closely interrelated. Sometimes, though, you need to take a big risk to qualify for a big reward.

Cisco can still play some risk-mitigation cards, while RIM needs to roll the dice.

Muglia’s Move to Juniper

Juniper Networks announced yesterday that Bob Muglia, who spent 23 years at Microsoft and was president of that company’s Server and Tools Business (STB) until January, will be joining the networking vendor to oversee its end-to-end software strategy and lead its just-created Software Solutions Division.

Back at Microsoft, Muglia and CEO Steve Ballmer appeared to hold diverging views on strategy for the STB. Those views apparently were not reconciled, so Ballmer ousted Muglia and sought “new leadership” — but only for the STB, not for the company as a whole.

Big Mandates

Until he left Microsoft, Muglia’s group was responsible for a remit that encompassed infrastructure software, developer tools, and cloud-computing platforms, including products such as Windows Server, SQL Server, Visual Studio, System Center, and the Windows Azure Platform. It was a big mandate, and Muglia will have a similarly ambitious charge at Juniper. As Jim Duffy notes at NetworkWorld:

“Juniper is centralizing its software business to further position it as a company differentiator and growth engine. Included in it will be software for Juniper’s SRX Series and vGW Series security platforms, MobileNext packet core offering for mobile operators, Junos Pulse mobile security suite for managing devices, and the Junos Space platform for developing and deploying network applications.”

Muglia, quoted below, seems eager for the challenge:

 “The emergence of cloud, heterogeneous devices connecting, and applications (executing) in a much more automated state creates an opportunity to bring software into the network and connect to all devices. Networks are configured and managed by manual processes, people with mice and keyboards, and separate from the application infrastructure. There is no way to deal with the scale of the amount of configuration changes in the network to ensure the reliability and consistency of the environment. Networks will be applications driven; applications are at the center of intelligence and business value. The infrastructure as a whole is being driven by the applications. Juniper is very well positioned to take this on with QFabric for cloud, and a single operating system platform. There’s not a lot of legacy mess to clean up.”

Raising the Software Quotient

Except for the last sentence, where Muglia offers an enthusiastic plug for QFabric, those words could have come from an executive at F5 Networks, or from those at other networking vendors trying to adjust to an application-centric data-center overhaul that already has virtualized and transmogrified the server and storage spheres, and is beginning to do likewise to the realm of network infrastructure.

From what I have seen, Juniper needed a further infusion of software bloodlines. Muglia could be an excellent addition to the leadership team, able to bring a heightened software sensibility to what remains a hardware-centric corporate culture. In some ways, though they are radically different companies in many respects, Juniper and Dell are both struggling to get away from a hardware-oriented culture. Yes, there’s a lot of software that goes Juniper networking equipment, but some within the company still are struggling, quite literally, to think “outside the box.”

The effort is there, though, and the spirit is willing, which is why I think Muglia was brought aboard. There’s tremendous potential in the entire Junos-based strategy and its software portfolio, including Pulse for mobile security and device management and the Space platform.

That’s why I see the Muglia move as a potentially significant and positive development for Juniper.

New Place, Familiar Faces

Muglia shouldn’t take long to acclimate to his new corporate home. As Mary Jo Foley wrote, it is well populated with former Microsoft executives. Heading that list is Juniper CEO Kevin Johnson, but he’s joined by a number of others, including Gerri Elliott, chief sales Officer; Brad Brooks, VP of worldwide enterprise marketing; Eddie Amos, VP of developer marketing; and Lauren Cooney, director of developer evangelism.

Reporting directly to Johnson and starting at Juniper after he leaves Microsoft in September, Muglia should have immediate rapport with his new boss.

Wondering About HP Networking’s Dualism

At Network Computing, Greg Ferro writes an intriguing piece about HP Networking’s split personality.

After HP acquired 3Com (H3C), the conventional wisdom, with which I concurred, was that the ProCurve product line was living on borrowed time. I didn’t expect ProCurve to disappear overnight — there was an installed base of customers to take into account, after all — but I did think the development pendulum would swing overwhelmingly to China and the 3Com/H3C team.

To a large extent, that has happened, but the ProCurve product portfolio is proving surprisingly tenacious. As Ferro notes, HP’s E Series switches continue to sport ProCurve’s in-house ASICs and ProCurve software. Meanwhile, HP  Networking’s A Series switches feature merchant silicon and 3Com/H3C’s Comware network OS. Finally, HP has the S Series, which also sports merchant silicon.

HP’s Rationale

So, what’s with the continuing split in HP Networking’s product portfolio? In his article at Network Computing, Ferro quotes Dan Montesanto, an HP switch product manager, who asserts that custom ASICs “make a lot of sense in the ‘middle of the market,’” but apparently not as much sense at the low end or the high end of the market. You can read the rationalization over at Network Computing, and you can decide whether you buy it.

I must admit, I’m skeptical of the official reasoning. I don’t want to go all “conspiracy theory” on you — in fact, I don’t have a conspiracy theory to proffer on this matter — but I just question whether HP is giving us the whole truth and nothing but the truth.

Something just doesn’t ring true about it. Yes, I note HP’s claims that it can make cheaper and better chips than merchant-silicon purveyors for certain product price points in the market. Perhaps those claims are true. I can’t disprove them.

Still, why continue to offer the different network operating systems? Wouldn’t it make sense to run the same software across all HP’s switches? Silicon issues notwithstanding, why wouldn’t HP unify its networking portfolio under Comware?

Market Expects Comware Migration

The market thinks that will happen eventually. Ferro writes:

 “One thing seems clear: HP Networking hasn’t convinced the wider market that both Comware and ProCurve operating systems are necessary, and most network architects expect HP to migrate its product line to Comware.”

Again, I’m not trying to sell you an extraterrestrial in the desert or persuade you that I saw Elvis outside a Burger King, but I wonder what’s happening behind the scenes at HP. It’s almost as if HP Networking is keeping the ProCurve ASICs and software going as an insurance policy.

But, if that’s true, why?

F5 Bids to Strengthen Data-Center Grip

Acquisitions always qualify as big news because they’re dramatic transactions. They are sudden, sometimes surprising, and they can have significant commercial, financial, industrial, and technological implications. They roil industry waters, ultimately leaving some vendors capsized and others navigating toward bold horizons.

Product announcements can be overshadowed amid periods of M&A ferment, so it’s important that we pay sufficient attention to product launches that have potentially far-reaching consequences.

Toward the Dynamic Data Center

One such announcement occurred today as F5 Networks, the leader in the application delivery controller (ADC) space, announced its BIG-IP v11 software release, scheduled to reach market in the third quarter. F5 is emphasizing two major aspects of the release: the realization of its vision of a “dynamic data center,” in which service provisioning is expedited through an application-centric view of network infrastructure and resource availability; and enhanced, dynamic security services that are intended to prevent attacks on networks, applications, and data.

Over at F5’s DevCentral, Lori MacVittie has been setting the stage for today’s announcement for a while, discussing various intractable operational and technological challenges — all of which, perhaps not surprisingly, can be addressed by the new release of BIG-IP. No wonder, then, that she was eager to provide her perspective on what today’s announcement means.

Piecing IT Together

In her view, the “game changing” pieces of the new BIG-IP are iApp, which moves the focus of BIG-IP configuration from network-oriented objects to application-centric views; ScaleN, which introduces the concept of “Device Service Clusters” and facilitates targeted fail-over of application instances, allowing customers to scale out across CPUs or devices, managing them as one pool; and Virtual Clustered Multiprocessing (vCMP), which makes ScaleN possible.

When you consider those three components together, she contends, “you now have capabilities in the application delivery infrastructure with similar benefits and abilities as those found previously only in the server / application virtualization infrastructure: automated, repeatable, manageable, scalable infrastructure services.”

Strengthening Data-Center Claims

What it means from a business standpoint for customers is increased cost savings from greater IT efficiency, improved application-centric resource utilization, and automated (thus faster and less costly) application provisioning.

From an industry and vendor perspective, what is means is that F5 bolsters its case for BIG-IP as an essential element in data-center management. If this release of BIG-IP and its underlying strategy are successful, F5 not only takes greater command of the ADC space, but also will strengthen its claims on some critical real estate in enterprise and service-provider data centers.

Reviewing Dell’s Acquisition of Force10

Now seems a good time to review Dell’s announcement last week regarding its acquisition of Force10 Networks. We knew a deal was coming, and now that the move finally has been made, we can can consider the implications.

It was big news on a couple fronts. First, it showcased Dell’s continued metamorphosis from being a PC vendor and box pusher into becoming a comprehensive provider of enterprise and cloud solutions. At the same time, and in a related vein, it gave Dell the sort of converged infrastructure that allows it to compete more effectively against Cisco, HP, and IBM.

The transaction price of Dell’s Force10 acquisition was not disclosed, but “people familiar with the matter” allege that Dell paid about $700 million to seal the deal. Another person apparently privy to what happened behind the scenes says that Dell considered buying Brocade before opting for Force10. That seems about right.

Rationale for Acquisition

As you’ll recall (or perhaps not), I listed Force10 as the second favorite, at 7-2, in my Dell Networking Derby, my attempt to forecast which networking company Dell would buy. Here’s what I said about the rationale for a Dell acquisition of Force10:

 “Dell partners with Force10 for Layer 3 backbone switches and for Layer 2 aggregation switches. Customers that have deployed Dell/Force10 networks include eHarmony, Salesforce.com, Yahoo, and F5 Networks.

Again, Michael Dell has expressed an interest in 10GbE and Force10 fits the bill. The company has struggled to break out of its relatively narrow HPC niche, placing increasing emphasis on its horizontal enterprise and data-center capabilities. Dell and Force10 have a history together and have deployed networks in real-word accounts. That could set the stage for a deepening of the relationship, presuming Force10 is realistic about its market valuation.”

While not a cheap buy, Force10 went for a lot less than an acquisition of Brocade, at a market capitalization of $2.83 billion, would have entailed. Of course, bigger acquisitions always are harder to integrate and assimilate than smaller ones. Dell has found a targeted acquisition model that seems to work, and a buy the size of Brocade would have been difficult for the company to digest culturally and operationally. In hindsight, which usually gives one a chance to be 100% correct, Dell made a safer play in opting for Force10.

IPO Plans Shelved

Although Force10 operates nominally in 60 countries worldwide, it derived 80 percent of its $200 million in revenue last year from US customers, primarily data-center implementations. Initially, at least, Dell will focus its sales efforts on cross-pollination between its and Force10’s customers in North America. It will expand from there.

Force10 has about 750 employees, most of whom work at its company headquarters in San Jose, California, and at a research facility in Chennai, India. Force10 doesn’t turn Dell into an overnight networking giant; the acquired vendor had just two percent market share in data-center networking during the first half of 2011, according to IDC. Numbers from Dell’Oro suggest that Force10 owned less than one percent of the overall Ethernet switch market.

Once upon a time, Force10 had wanted to fulfill its exit strategy via an IPO. Those plans obviously were not realized. The scuttlebutt on the street is that, prior to being acquired by Dell, Force10 had been slashing prices aggressively to maintain market share against bigger players.

Channel Considerations

Force10 has about 1,400 customers, getting half its revenue and the other half from channel sales. Dell doesn’t see an immediate change in the sales mix.

Dell will work to avoid channel conflict, but I foresee an increasing shift toward direct sales, not only with the Force10’s data-center networking gear, but also with any converged data-center-in-a-box offerings Dell might assemble.

Converged Infrastructure (AKA Integrated Solution Stack) 

Strategically, Dell and its major rivals are increasingly concerned with provision of converged infrastructure, otherwise known as as an integrated technology stack (servers, storage, networking, associated management and services) for data centers. The ultimate goal is to offer comprehensive automation of tightly integrated data-center infrastructure. These things probably will never run themselves — though one never knows — but there’s customer value (and vendor revenue) in pushing them as far along that continuum as possible.

For some time,  Dell has been on a targeted acquisition trail, assembling all the requisite pieces of the converged-infrastructure puzzle. Key acquisitions included Perot Systems for services, EqualLogic and Compellent for storage, Kace for systems management, and SecureWorks for security capabilities. At the same time, Dell has been constructing data centers worldwide to host cloud applications.

Dell’s converged-infrastructure strategy is called Virtual Network Services Architecture (VNSI), and the company claims Force10’s Open Cloud Networking (OCN) strategy, which stresses automation and virtualization based on open standards, is perfectly aligned with its plans. Dario Zamarian, VP and GM of Dell Networking, said last week that VNSI is predicated on three pillars: “managing from the edge,” where servers and storage are attached to the network; “flattening the network,” which is all the rage these days; and “scaling virtualization.”

For its part, Force10 has been promoting the concept of flatter and more scalable networks comprising its interconnected Z9000 switches in distributed data-center cores.

 The Network OS Question

I don’t really see Dell worrying unduly about gaining greater direct involvement in wiring-closet switches. It has its own PowerConnect switches already, and it could probably equip those to run Force10’s FTOS on those boxes. It seems FTOS, which Dell is positioning as an open networking OS, could play a prominent role in Dell’s competitive positioning against Cisco, HP, Juniper, IBM, and perhaps even Huawei Symantec.

Then again, Dell’s customers might have a say in the matter. At least two big Dell customers, Facebook and Yahoo, are on the board of directors of the Open Networking Foundation (ONF), a nonprofit organization dedicated to promoting software-defined networking (SDN) using the OpenFlow protocol. Dell and Force10 are members of ONF.

It’s possible that Dell and Force10 might look to keep those big customers, and pursue others within the ONF’s orbit, by fully embracing OpenFlow. The ONF’s current customer membership is skewed toward high-performance computing and massive cloud environments, both of which seem destined to be aggressive early adopters of SDN and, by extension, the OpenFlow protocol.  (I won’t go into my thoughts on OpenFlow here — I’ve already written a veritable tome in this missive — but I will cover it in a forthcoming post.)

Notwithstanding its membership in the Open Networking Foundation, Force10 is perceived as relatively bearish on OpenFlow. Earlier this year, Arpit Joshipura, Force10’s chief marketing officer, indicated his company would wait for OpenFlow to mature and become more scalable before offering it on its switches. He said “big network users” — presumably including major cloud providers — are more interested in OpenFlow today than are enterprise customers. Then again, the cloud ultimately is one of the destinations where Dell wants to go.

Still, Dell and Force10 might see whether FTOS can fit the bill, at least for now. As Cindy Borovick, research vice president for IDC’s enterprise communications and data center networks, has suggested, Dell could see Force10‘s FTOS as something that can be easily customized for a wide range of deployment environments. Dell could adapt FTOS to deliver prepackaged products to customers, which then could further customize the network OS depending on their particular requirements.

It’ll be interesting to see how Dell proceeds with FTOS and with OpenFlow.

 Implications for Others

You can be sure that Dell’s acquisition of Force10 will have significant implications for its OEM partners, namely Juniper Networks and Brocade Communications. From what I have heard, not much has developed commercially from Dell’s rebranding of Juniper switches, so any damage to Juniper figures to be relatively modest.

It’s Brocade that appears destined to suffer a more meaningful hit. Sure, Dell will continue to carry and sell its Fiber Channel SAN switches, but it won’t be offering Brocade’s Foundry-derived Ethernet switches, and one would have to think that the relationship, even on the Fiber Channel front, has seen its best days.

As for whether Dell will pursue other networking acquisitions in the near team, I seriously doubt it. Zeus Kerravala advises Dell to buy Extreme Networks, but I don’t see the point. As mentioned earlier, Dell already has its PowerConnect line, and the margins are in the data-center, not out in the wiring closets. Besides, as Dario Zamarian has noted, data-center networking is expected to grow at a compound annual growth rate of 21 percent through 2015, much faster than the three-percent growth forecast for the rest of the industry.

The old Dell would have single-mindedly chased the network box volumes, but the new Dell aspires to something grander.