Daylight breaks: New consortium announced in SDN market
After last week's speculative post about a potential new open source consortium, SDNCentral's Matthew
Check out Palmer's breakdown of what Daylight will mean for customers, software vendors, startups and others.
SDN's potential in changing network industry
Predictions about how disruptive SDN will be in the coming year are anything but definitive. Over at Jason Edelman's blog, the networking engineer acknowledges there's no real answer to what will become news in the coming years. But one thing is clear: Data center networking is changing. Clouds are degrading brand power, bring your own device, or BYOD, is proliferating, and physical networks are becoming simpler and more automated. Together, this evolution of networking requires that networks be virtualized. Network managers and engineers might insist SDN is years away from having a noticeable impact, but the acquisitions likely to come in 2013 will change many perspectives on virtual networking.
Read Edelman's thoughts on how SDN will affect the networking industry in the near future.
More details about a Cisco SDN controller
Last week we got more details about the Cisco SDN controller. Currently in beta, the controller will support OpenFlow and One Platform Kit, or onePK. Key among Cisco's recent announcements was the introduction of the Nexus 6000 series switch, the first SDN controller Cisco has offered, and Nexus 1000v-based software. Brent Salisbury at Network Static broke down the key points of Cisco's news, including a dissection of the three applications announced: network tapping, custom forwarding and network slicing. He also offered some analysis outlining his views on the future of Cisco in networking, plus a coy review of the product itself, which he tested under a nondisclosure agreement.
Head over to Salisbury's blog to read his full opinion on Cisco's recent announcements.
Best practices for network documentation
A comprehensive Packet Pusher's blog lists the essential elements of network documentation, including the key numbers to record, important inventories to list and standard configurations to define. Network consultant Charles Galler outlines eight key areas that companies should be documenting, with details on how and why the records are essential.
Read Galler's article for step-by-step tips on network documentation.
Tips for packet sniffers in a virtual environment
Sniffing traffic in the virtual world can be tricky even in the simplest of environments. Networking expert Jim MacLeod offers advice for packet capture in different virtual machine scenarios, where a focus on simplicity rather than control makes monitoring a challenge. McLeod outlines straightforward solutions for environments with a single server, with encapsulated overlay traffic or in a cloud, plus their advantages and disadvantages.
Brush up on your sniffing choices in the virtual world with McLeod's post at LoveMyTool.