We recently met with Huawei executives during the launch of its latest product in China, the S12700 switch. The product, which ships in limited quantity in Q1 2014 is designed for managing campus networks, and acts as a core and aggregation switch in the heart of campus networks. While wired/wireless convergence, policy control and management come as standard features, the draw is the Ethernet Network Processor (ENP). The ENP competes against merchant silicon in competitive switch products, and Huawei claims to be able to deliver new programmable services in six months, compared to one to three years for competitive application-specific integrated circuit (ASIC) chips. This helps IT managers respond quicker to the needs of campus network users, especially in the age of BYOD, Big Data, and cloud computing.
While it is a commendable product in its own right, Huawei will need to position its value more strategically against IT managers that have technology inertia, especially in ‘Cisco-heavy’ networks:
Tying the value of the switch to existing and future enterprise campus needs. In the age of cloud computing, big data, mobility, and social networking, IT managers need to solve network challenges like insufficient service processing capability and slow service responses. Huawei says the new switch is able to provide agile services and respond flexibly to changes in service requirements, on demand. For example, the switch has access control built in for wired/wireless access management. This is a good start. Enterprises will need to understand how the switch plays a central role in a campus network, and Huawei should continue to reinforce its agile network architecture’s storyline.
At the Cisco Live EMEAR 2013 event in London, Cisco brought a new down-to-earth dynamism to the table. The vision for how Cisco is intending to empower its clients in an evermore connected world is becoming clearer. In this blog, Forrester analysts Dan Bieler and Peter O’Neill discuss their take-home messages from the event:
Hosted Collaboration Solution is empowering its high-end channel partners.
Dan. HCS, Cisco’s hosted collaboration suite, allows carriers to offer cloud-based as-a-service solutions, comprising unified communications, telepresence, contact centre, as well as a range of communication features under the Jabber brand. In EMEAR, BT, Telefonica, and Vodafone are already selling HCS, primarily aiming it at MNC customers. It remains to be seen whether the HCS pitch is the right one for smaller carriers and SMBs, especially as Cisco remains committed to catering to SMBs.
Peter. They also need to think about being more attractive to the needs of midmarket system integrators and MSPs. That means they must provide different price configurations that are attractive to SMBs. Positioning themselves only to the national telcos is quite restrictive and doesn’t match the increasing demand we are seeing for these solutions across the market. But, of course, if they want to compete in the SMB segment, they’ll compete with Google and Microsoft and their pricing strategies. The best way to run two pricing strategies is to use two brands.
Is it me, or does the network industry remind you of Revenge of the Nerds? Networking was cast aside in the cloud revolution, but now companies are learning -- the painful way – what a mistakes that was. Don’t kid yourself one bit if you think that VMware’s acquisition of Nicirawas mostly about developing heterogeneous hypervisor data centers or reducing networking hardware costs. If you do think that, you’re probably an application developer, hypervisor administrator, or data center architect. You’ve been strutting your newly virtualized self through rows of server racks over the last five year, casually brushing aside the networking administrators. You definitely had some outside support for your views: Google, VMware, and even OpenFlow communities have messaged that networking organizations aren’t cool anymore and need to be circumvented by coding around the network, making it a Layer 2 network or taking over the control plane.
To be fair, though, networking vendors and networking teams helped to create this friction, too, since they built their networks on:
40 years of outdated networking reliability principles. The current state of networking can be in many ways traced back to ARPANET’s principle: a single method to reliably communicate a host of multiple sets of flows, traffic, and workloads. Basically, voice, video, and all applications traverse the same rigid and static set of links that only change when a failure occurs. The package didn’t matter.