Kurhan - Fotolia
Cisco, Tail-F acquisition and its effect on competitors
The Cisco, Tail-F Systems acquisition has gone relatively unnoticed, writes Greg Ferro on his site Ethereal Mind. However, there are two products developed by Tail-F that could have an impact on Cisco competitors now that the company has been acquired. Tail-F's Network Control System provides a network configuration toolkit and management platform for vendor devices. That is now part of Cisco's Service Provider Unit and will most likely not be used in the enterprise.
By submitting your personal information, you agree that TechTarget and its partners may contact you regarding relevant content, products and special offers.
However, Tail-F also has a product called "Conf-D." It is an OEM product that acts as a software library purchased by networking companies, allowing their network operating system to provide management features. Now, Cisco owns these software libraries. Ferro writes that with this acquisition, Cisco can easily disrupt the product development "road maps" of its competitors and get a lead in the SDN market.
Read more on how Cisco's acquisition of Tail-F is going to impact competitors.
Content filtering: A use case for SDN
The Networking Nerd's Tom Hollingsworth looks at another use case for SDN on his blog site. As schools continue to look at online protection for students, Hollingsworth writes that SDN can be used for content filtering. He describes it as software-defined protection, where service chaining allows traffic to be directed to a device or virtual appliance before being passed through the network.
Carriers looking to provide the same type of protection to schools can use this concept as well. With SDN, they're able to configure the edge network to force traffic to a large central content filter cluster, ensuring delivery. It also allows the service provider network to operate without impact to non-filtered customers.
Check out Hollingsworth's post in its entirety and learn more about SDN and content filtering
SDN protocols to know: OpFlex and Declarative Networking
Matt Oswalt adds a fourth edition to his SDN protocol series on his Keeping It Classless site with a look at OpFlex and Declarative Networking. OpFlex is a protocol introduced by Cisco in OpenStack and OpenDaylight that addresses group based policy in an SDN environment. Oswalt writes that there has been a lot of confusion and inaccuracies around OpFlex, which is why he decided to break it down in detail.
Oswalt first explains the use of Opflex in the declarative programmability model. Then he shows how how OpFlex influences policy pushed into network elements, and how OpFlex works as both a system and an agent.
Learn more in Oswalt's post about OpFlex, Cisco and declarative networking.
What is the Software Defined Data center?
On his Hybrid Cloud Burst Blog, author Marty Hauville breaks down everything you need to know about the software-defined data center. In the SDDC, infrastructure control is abstracted from the underlying hardware, with all physical and virtual resources made visible via software programs. Hauville delves deeper into the origins of the SDDC, outlining specific cloud challenges that exist within the data center.
Hauville also looks at what he deems the future of the enterprise or hybrid cloud, and how the SDDC plays into it. Business challenges associated with the software-defined data center are outlined, as well as interoperability, security and control. Hauville also includes a section dedicated to openness, detailing protocols and organizations such as OpenFlow, Open vSwitch, and OpenDaylight.
Take a look at Hauville's post in its entirety, outlining the software-defined data center.