What’s your SDN story? This is a question that I hear more and more recently. Here’s the short version of my answer:
Net Optics NPB devices are located between the network elements and the different monitoring / security tools. As such, they are typically not involved in switching or forwarding decisions. However, we felt that there is a need to change the static nature of configuration and provide a method to respond to networking changes in a better way, by providing SDN integration. That’s the main reason that we added support for NETCONF management protocol in a native way.
Some technical details:
Software-defined networking (SDN) is an approach to computer networking which abstracts the hardware of the system, the control plane and the data plane.
The Open Networking Foundation (ONF) was founded to promote SDN standards and engineering. ONF defines the different protocols and standards that are shared among all vendors and open community/open source projects.
The OpenFlow configuration protocol is defined by OF-CONIFG specification. OF-CONFIG requires that devices supporting OF-CONFIG MUST implement NETCONF protocol as the transport.
NETCONF is protocol for exchanging configuration information from a management platform. YANG is the data modeling language for the format of data used by NETCONF to exchange data. Both NETCONF and YANG are defined by several RFC. Just to list few RFC and standards that we support:
- RFC 4741 NETCONF Configuration Protocol
- RFC 4742 Using the NETCONF Configuration Protocol over Secure Shell
- RFC 6020 YANG – A Data Modeling Language for the Network Configuration Protocol (NETCONF)
- RFC 6021 Common YANG Data Types
- RFC 6022 YANG Module for NETCONF Monitoring
- RFC 6244 An Architecture for Network Management Using NETCONF and YANG
Net Optics xStream products (xStream 10, xStream 40 ) support the NETCONF protocol natively. This is very important, since it means that all future actions and activities that are managed by any SDN enabled management platform can fully manage xStream.
Due to our openness and standard protocol support one can use 3rd party or even community-developed tools to access and manage our devices. We can provide links to simple tools that can be used by any 3rd party to fully access the device.
Thanks to Net Optics for the article.