Welcome!

SDN Journal Authors: Yeshim Deniz, Liz McMillan, Elizabeth White, Pat Romanski, TJ Randall

Related Topics: @CloudExpo, Java IoT, Linux Containers, Containers Expo Blog, Agile Computing, SDN Journal, @ThingsExpo

@CloudExpo: Article

Network Device Management | @CloudExpo #BigData #SDN #IoT #M2M #API

This list will help you employ a strategy that makes sense for organizations today and tomorrow

Network Device Management for Today and Tomorrow - a Do and Don't Guide

Today, "network device management" means different things to different people, and the reality is that IT organizations do it, or at least do what they consider network device management to be, to vastly varying degrees, including some who do none at all (hopefully this isn't you).

At least part of the reason network device management has become such an ambiguous thing is because what we consider to be a network device is constantly evolving. At one point, network devices were largely just routers and switches. Back then, even if one added end-user workstations into the mix, things were fairly simple.

Then things started to get interesting. Wireless introduced a few more devices and, when BYOD started springing up, all you-know-what seemed to break loose. Now the Internet of Things (IoT) and other trends and dangers such as software defined networking (SDN) and shadow IT, respectively, are only complicating things even further.

I previously went into greater detail on these trends and more, and how to create a sensible network roadmap that breaks down what network administrators should be focused on today, and what we should be preparing for tomorrow and beyond. The reality is that network device management, no matter how you currently define it, is a major part of all three phases - today, tomorrow and beyond. On the heels of that write-up, here I attempt to better define the scope of network device management and provide a list of network device management do's and don'ts that will help you employ a strategy that makes sense for organizations today and tomorrow.

I submit that network device management can be divided into three areas, applicable across almost all organizations: configuration management, device monitoring and automation. These are the most essential elements of effective network monitoring and have stood the test of time.

With this framework in mind, here are several key best practices for getting a handle on network device management.

Configuration Management

  • DO: Systematic backups. You should have ongoing, automatic backups of network device configurations - not when you remember to run them, or when you start to get worried, but always. That also includes a system that triggers ad hoc device configuration backups in response to any significant configuration change. This will not only help ensure your network performs well, but will also aid in ongoing configuration management and identifying security or compliance issues.
  • DON'T: Forget to save. Network devices typically have two different configurations: running and saved. It's all too common for network administrators to make a change to a device, which changes the running configuration, but then never save it, resulting in the configuration changes disappearing when the device reboots. Backing up both configurations and then triggering an alert when they don't match is another handy tip.

Device Monitoring

  • DO: Truly understand your network. This goes beyond understanding the architecture diagram. It includes making sure you understand what "normal" looks like on your network and what "healthy" is for the devices in your environment even if you have too many devices to count. It means knowing - or knowing how to find out - what the patterns of usage are day by day, hour by hour, and at different points in the month. Basically, it means treating monitoring - the regular, consistent, ongoing collection of data from devices - as its own discipline and not just "the thing that creates all those tickets" or an item on your to-do list.
  • DON'T: Just sit there. Ticketing is the happy bi-product of monitoring, but it's not the end of the story. Work with the people who receive and respond to those tickets to fine-tune the alerts for greater insight. Also understand all the monitoring, alerting and automation techniques at your disposal. From SNMP to syslog, and from traps to configuration comparison, look at each capability as the treasure trove it is and leverage it for all you are worth.

Automation

  • DO: Be lazy! Okay, don't actually be lazy, but find ways to let the computer respond at 2 a.m. and if the problem clears up, let sleeping humans lie. Ask the fine people who make up your IT team, "What will you do once you get this ticket?" If they tell you something that can be automated, then you automate it.
  • DON'T: Be lazy! Meaning being the kind of monitoring professional who has a "set it and forget it" mentality when it comes to monitoring and alerting.

While network device management can seem daunting, following these do's and don'ts can help you ensure that you've got a grasp on it, not only for today's networks and associated challenges, but those to come as well.

More Stories By Leon Adato

Leon Adato is a Head Geek and technical evangelist at SolarWinds and is a Cisco® Certified Network Associate (CCNA), MCSE and SolarWinds Certified Professional (he was once a customer, after all). His 25 years of network management experience spans financial, healthcare, food and beverage, and other industries.

Comments (0)

Share your thoughts on this story.

Add your comment
You must be signed in to add a comment. Sign-in | Register

In accordance with our Comment Policy, we encourage comments that are on topic, relevant and to-the-point. We will remove comments that include profanity, personal attacks, racial slurs, threats of violence, or other inappropriate material that violates our Terms and Conditions, and will block users who make repeated violations. We ask all readers to expect diversity of opinion and to treat one another with dignity and respect.


CloudEXPO Stories
René Bostic is the Technical VP of the IBM Cloud Unit in North America. Enjoying her career with IBM during the modern millennial technological era, she is an expert in cloud computing, DevOps and emerging cloud technologies such as Blockchain. Her strengths and core competencies include a proven record of accomplishments in consensus building at all levels to assess, plan, and implement enterprise and cloud computing solutions. René is a member of the Society of Women Engineers (SWE) and a member of the Society of Information Management (SIM) Atlanta Chapter. She received a Business and Economics degree with a minor in Computer Science from St. Andrews Presbyterian University (Laurinburg, North Carolina). She resides in metro-Atlanta (Georgia).
In his session at 20th Cloud Expo, Mike Johnston, an infrastructure engineer at Supergiant.io, discussed how to use Kubernetes to set up a SaaS infrastructure for your business. Mike Johnston is an infrastructure engineer at Supergiant.io with over 12 years of experience designing, deploying, and maintaining server and workstation infrastructure at all scales. He has experience with brick and mortar data centers as well as cloud providers like Digital Ocean, Amazon Web Services, and Rackspace. His expertise is in automating deployment, management, and problem resolution in these environments, allowing his teams to run large transactional applications with high availability and the speed the consumer demands.
The technologies behind big data and cloud computing are converging quickly, offering businesses new capabilities for fast, easy, wide-ranging access to data. However, to capitalize on the cost-efficiencies and time-to-value opportunities of analytics in the cloud, big data and cloud technologies must be integrated and managed properly. Pythian's Director of Big Data and Data Science, Danil Zburivsky will explore: The main technology components and best practices being deployed to take advantage of data and analytics in the cloud, Architecture, integration, governance and security scenarios and Key challenges and success factors of moving data and analytics to the cloud
SYS-CON Events announced today that DatacenterDynamics has been named “Media Sponsor” of SYS-CON's 18th International Cloud Expo, which will take place on June 7–9, 2016, at the Javits Center in New York City, NY. DatacenterDynamics is a brand of DCD Group, a global B2B media and publishing company that develops products to help senior professionals in the world's most ICT dependent organizations make risk-based infrastructure and capacity decisions.
Most DevOps journeys involve several phases of maturity. Research shows that the inflection point where organizations begin to see maximum value is when they implement tight integration deploying their code to their infrastructure. Success at this level is the last barrier to at-will deployment. Storage, for instance, is more capable than where we read and write data. In his session at @DevOpsSummit at 20th Cloud Expo, Josh Atwell, a Developer Advocate for NetApp, will discuss the role and value extensible storage infrastructure has in accelerating software development activities, improve code quality, reveal multiple deployment options through automated testing, and support continuous integration efforts. All this will be described using tools common in DevOps organizations.