Agility, protection and scalability needed for hybrid cloud adoption
While small businesses are increasingly using the public or hybrid cloud, enterprises are not so quick to jump on board. To make the move to the hybrid cloud, enterprises need to be guaranteed security and scalability, among a few other killer apps, said
Read Greg's rundown on the hybrid cloud's killer apps and why enterprises should shift the cloud adoption discussion in their direction.
How to use the normal forwarding action in hybrid OpenFlow
While many engineers don't consider OpenFlow ready for primetime (some even claim it has been prematurely productized), others will begin using the technology in hybrid SDN-traditional environments. Using hybrid OpenFlow, engineers would keep most of the network the same, while deploying OpenFlow at the edge of the network to direct specific traffic flows for a few applications, such as tapping. NetworkStatic blogger Brent Salisbury said that most vendors are supporting the OF Normal action to allow the redirection of certain "interesting" traffic to these applications.
Check out Salisbury's post for a debriefing on how to use the OpenFlow normal forwarding action.
Differentiating network virtualization and server virtualization
There is plenty of debate about where software-defined networking (SDN) and network virtualization overlap or intersect. Network engineer Jason Edelman takes a focused approach to the concept of virtualization in his latest posts on the subject, avoiding the subject of SDN in a discussion centered on the properties that define the virtualized network. He dives into the details of what distinguishes server virtualization from network virtualization, including the corresponding tools used for each approach.
Read Edelman's initial breakdown of the differences between network virtualization and server virtualization,and then view his follow-up post on the ways physical devices should adapt to enhance the virtual network.
How to pin down the source of network, application glitches
When it comes to identifying the root cause of a network snag, it's a good idea to keep your problem-solving simple. As network analyst Chris Greer explained in a series of blog posts, there are three top contributors to faulty network performance: packet loss, capacity issues and -- a side effect of the rise of BYOD -- wireless network problems. Diagnosing the cause of slow application performance requires looking at the start of the Transmission Control Protocol (TCP) sequence, analyzing server response time and filtering for TCP resets.
Meraki sheds light on infrastructure design process
Meraki faced plenty of skepticism when it introduced its cloud-based management system to the wireless market, but its cost-effective offerings and customer-oriented approach have propelled the company from a 15-employee startup to a branch of Cisco worth $1.2 billion. At Meraki's most recent showing at a Wireless Field Day, the company provided an in-depth look at its design process for cloud-based infrastructure. It was a daring move, Chris Lyttle wrote, and one that highlighted the steep standard Meraki has set for customer-driven management in the cloud.
Get all the technical details behind the Meraki Wi-Fi platform and the business practicesthat have oriented the company for success at Wi-fi Kiwi's Blog.