SHARE



ABOUT THE AUTHOR


Terry Slattery
Terry Slattery, is a senior network engineer with decades of experience in the internetworking industry. Prior to joining Chesapeake NetCraftsmen as...
Read Full Bio >>
SHARE



Terry Slattery | February 11, 2014 |

 
   

Monitoring a Software Defined Network, Part 3

Monitoring a Software Defined Network, Part 3 Should the SDN monitoring system be integrated with the controller, or should it be a separate system?

Should the SDN monitoring system be integrated with the controller, or should it be a separate system?

Note: My discussion of SDN monitoring covers several topics. Here are two prior posts:
1. Monitoring the SDN data plane
2. What parameters to monitor in an SDN control system

Monitoring Requirements
Defining the requirements for monitoring a software-defined network (SDN) is an interesting challenge, considering the fact that the definition of an SDN itself is still under debate. However, there are several things that we know about SDNs, and we can use them to help us begin to construct a management architecture.

We know that an SDN will contain a control system. The control system could be a single controller or it could be a multi-controller system, depending on the complexity and resilience requirements. A larger network may need multiple controllers in order to distribute the load. A highly resilient system will likewise need multiple controllers in case one controller fails or loses connectivity. So let's start with a requirement to monitor multiple controllers.

SDNs are very agile. One of the benefits is to be able to adapt to the application's needs very quickly. The monitoring system will need to be just as adaptable. It will need to track which network interfaces are active. It should be able to display a map of how an application uses the network. If overlays are in use, show the overlay and how it maps to the physical underlay network.

We explored monitoring of the data plane components in the first blog of this series--the monitoring requirements there are no different than those of a traditional network management system. Since much of the data plane monitoring is based on periodic performance measurements, it makes sense to use a time-series database to store the data. Note: I've never seen a relational database handle the volumes of data produced by a network performance monitoring system; a time-series database is the proper tool for this job.

Data will need to be collected from all the interfaces in the data plane (that's the only way to detect certain classes of errors) and store it. This requirement dictates the use of high-throughput disk I/O. We will also need to gather the data from physical switches, so we'll need network connectivity to those switches.

Non-performance data, such as hardware and software inventory, device configurations, policy definitions, and functional data are much lower volume, and change much less frequently, making them suitable for storage in a relational database.

The network administrators will need to use the monitoring system to turn the raw data into actionable information that can be presented through a graphical user interface. Most network management systems now use a web-based GUI that is accessible from almost anywhere. Data warehouse technology and big-data technology can be used to transform raw data into actionable information, reducing the volume of information and making the GUI very responsive.

The Architecture
What should the architecture of the monitoring system be? Should it be based on a distributed system, a centralized system, or something else? Should it be built into the SDN control system? Or should it be a separate system?

There is a temptation to embed the monitoring system within the controller, since that is where all the data about the state of the system resides. This approach will work as long as the monitoring system can merge data from multiple controllers. However, in the past, the network monitoring development staff has been separate from the network equipment development staff within vendor organizations. Decoupling the two groups allows each group to ship products independently of each other, which is an advantage to companies that are attempting to get to market quickly.

Separating the controller and the monitoring system also means that a different company can develop each product. Each company can then focus on what it does best. I also expect to see existing network management products incorporate an SDN monitoring and management function, alongside their existing functionality.

Another argument in favor of building the monitoring system into the SDN controller is that the architecture could result in lower disk I/O requirements on each controller's monitoring system. But a distributed monitoring system architecture could provide the same benefit without being integrated into the SDN controller.

A distributed monitoring system architecture has a lot of benefits. Since the system is distributed, this architecture could result in lower disk I/O requirements on each monitoring component, which is an advantage. Local processing of the collected data may also be an advantage in this architecture, although moving the data to a data warehouse solution may be a better alternative. A monitoring system using this approach will need to make sure that it provides a view of the overall network.

Now let's examine the contrary point of view. Integrating an SDN management system within the controller creates a software update problem. As we've historically seen, network management software gets released on a different schedule than network control software. Decoupling the SDN controller from the management system makes it easy to perform software upgrades on both components.

It also makes a lot of sense to take advantage of x86-based server virtualization to run the management software, just as other network functions are being virtualized. This makes it much easier to perform software maintenance and upgrades. And when the hardware needs to be upgraded, simply migrate the management VM to a new platform.

The only problem with this approach is that network management systems tend to need high performance I/O subsystems for storing and processing the collected data. However, by creating a distributed architecture that partitions the data-handling task into enough pieces, the performance problem disappears.

Summary
I predict that future network management systems (NMSs) will start to look like many of the big data applications that we see enterprises using today. There is no compelling reason to integrate the SDN NMS into the controller. While we need to collect data from the SDN controllers, that can be done through some north-bound APIs that provide a clean interface. One SDN NMS collector can then monitor multiple SDN controllers.

With a distributed architecture, the NMS can handle large-scale SDN monitoring, multiple SDN domains, and non-SDN networking infrastructure, providing a view of the entire network. With the right internal architecture and components, the NMS can adapt to changes in the network, starting and stopping monitoring VMs as needed. In this way the NMS becomes as flexible and as agile as the underlying network.

Want a deep dive into SDN and its impact on communications? Attend Terry Slattery's workshop on the topic at Enterprise Connect Orlando 2014!





COMMENTS



Enterprise Connect Orlando 2018
March 12-15 | Orlando, FL

Connect with the Entire Enterprise Communications & Collaboration Ecosystem


Stay Up-to-Date: Hear industry visionaries in Keynotes and General Sessions delivering the latest insight on UC, mobility, collaboration and cloud

Grow Your Network: Connect with the largest gathering of enterprise IT and business leaders and influencers

Learn From Industry Leaders: Attend a full range of Conference Sessions, Free Programs and Special Events

Evaluate All Your Options: Engage with 190+ of the leading equipment, software and service providers

Have Fun! Mingle with sponsors, exhibitors, attendees, guest speakers and industry players during evening receptions

Register now with code NOJITTEREB to save $200 Off Advance Rates or get a FREE Expo Pass!

December 13, 2017

The two major vendors in the Unified Communications space, Cisco and Microsoft, are both strongly promoting their cloud UC deployments. If cloud UC is on your enterprises roadmap, but you dont want

November 29, 2017

As video conferencing use rises in the enterprise, businesses are looking for ways to bring this technology out of traditional conference room and make it more broadly accessible. That's made the h

November 1, 2017

Your customers (internal and external) demand that you offer them the ability to connect by any means. With the adoption of cloud communications tools you now have access to an expanded portfolio o

November 30, 2017
With a ruling on the FCC's proposed order to dismantle the Open Internet Order expected this month, communications technology attorney Martha Buyer walks us through what's at stake.
October 23, 2017
Wondering which Office 365 collaboration tool to use when? Get quick pointers from CBT Nuggets instructor Simona Millham.
September 22, 2017
In this podcast, we explore the future of work with Robert Brown, AVP of the Cognizant Center for the Future of Work, who helps us answer the question, "What do we do when machines do everything?"
September 8, 2017
Greg Collins, a technology analyst and strategist with Exact Ventures, delivers a status report on 5G implementation plans and tells enterprises why they shouldn't wait to move ahead on potential use ....
August 25, 2017
Find out what business considerations are driving the SIP trunking market today, and learn a bit about how satisfied enterprises are with their providers. We talk with John Malone, president of The Ea....
August 16, 2017
World Vision U.S. is finding lots of goodness in RingCentral's cloud communications service, but as Randy Boyd, infrastructure architect at the global humanitarian nonprofit, tells us, he and his team....
August 11, 2017
Alicia Gee, director of unified communications at Sutter Physician Services, oversees the technical team supporting a 1,000-agent contact center running on Genesys PureConnect. She catches us up on th....
August 4, 2017
Andrew Prokop, communications evangelist with Arrow Systems Integration, has lately been working on integrating enterprise communications into Internet of Things ecosystems. He shares examples and off....
July 27, 2017
Industry watcher Elka Popova, a Frost & Sullivan program director, shares her perspective on this acquisition, discussing Mitel's market positioning, why the move makes sense, and more.
July 14, 2017
Lantre Barr, founder and CEO of Blacc Spot Media, urges any enterprise that's been on the fence about integrating real-time communications into business workflows to jump off and get started. Tune and....
June 28, 2017
Communications expert Tsahi Levent-Levi, author of the popular BlogGeek.me blog, keeps a running tally and comprehensive overview of communications platform-as-a-service offerings in his "Choosing a W....
June 9, 2017
If you think telecom expense management applies to nothing more than business phone lines, think again. Hyoun Park, founder and principal investigator with technology advisory Amalgam Insights, tells ....
June 2, 2017
Enterprises strategizing on mobility today, including for internal collaboration, don't have the luxury of learning as they go. Tony Rizzo, enterprise mobility specialist with Blue Hill Research, expl....
May 24, 2017
Mark Winther, head of IDC's global telecom consulting practice, gives us his take on how CPaaS providers evolve beyond the basic building blocks and address maturing enterprise needs.
May 18, 2017
Diane Myers, senior research director at IHS Markit, walks us through her 2017 UC-as-a-service report... and shares what might be to come in 2018.
April 28, 2017
Change isn't easy, but it is necessary. Tune in for advice and perspective from Zeus Kerravala, co-author of a "Digital Transformation for Dummies" special edition.
April 20, 2017
Robin Gareiss, president of Nemertes Research, shares insight gleaned from the firm's 12th annual UCC Total Cost of Operations study.
March 23, 2017
Tim Banting, of Current Analysis, gives us a peek into what the next three years will bring in advance of his Enterprise Connect session exploring the question: Will there be a new model for enterpris....
March 15, 2017
Andrew Prokop, communications evangelist with Arrow Systems Integration, discusses the evolving role of the all-important session border controller.
March 9, 2017
Organizer Alan Quayle gives us the lowdown on programmable communications and all you need to know about participating in this pre-Enterprise Connect hackathon.
March 3, 2017
From protecting against new vulnerabilities to keeping security assessments up to date, security consultant Mark Collier shares tips on how best to protect your UC systems.
February 24, 2017
UC analyst Blair Pleasant sorts through the myriad cloud architectural models underlying UCaaS and CCaaS offerings, and explains why knowing the differences matter.
February 17, 2017
From the most basics of basics to the hidden gotchas, UC consultant Melissa Swartz helps demystify the complex world of SIP trunking.
February 7, 2017
UC&C consultant Kevin Kieller, a partner at enableUC, shares pointers for making the right architectural choices for your Skype for Business deployment.
February 1, 2017
Elka Popova, a Frost & Sullivan program director, shares a status report on the UCaaS market today and offers her perspective on what large enterprises need before committing to UC in the cloud.
January 26, 2017
Andrew Davis, co-founder of Wainhouse Research and chair of the Video track at Enterprise Connect 2017, sorts through the myriad cloud video service options and shares how to tell if your choice is en....
January 23, 2017
Sheila McGee-Smith, Contact Center/Customer Experience track chair for Enterprise Connect 2017, tells us what we need to know about the role cloud software is playing in contact centers today.