Solution: Proof-of-concept mindset
Smaller companies and deep network engineering teams can often succeed with a homegrown or open-source NSoT solution, at least at in the early stages of a network automation strategy. As complexity, scale, and diversity of use cases grow, many network teams will need to partner with a NSoT vendor. Thus, network teams should approach these projects with a NSoT mindset. They should document the value of such a tool as much as possible and prepare a business case for how a vendor could amplify this success.
Challenge: Data pain
NSoT isn’t a magic bullet for solving the problems IT organizations have with poor network documentation and scattered operational data. Network engineering teams will need to discover, validate, reconcile, and import data from multiple repositories. This process can be challenging and time-consuming. Some of this data will difficult to find. Once the data is found, engineers need to validate the data is good. For instance, is the spreadsheet for a network’s IP address plan accurate?
“In brownfield networks, IP addresses are in one IPAM, VLANs are in another system. Some people have spreadsheet and some use MongoDB,” said a network automation engineer at a Fortune 500 bank. “The sources of data are everywhere, and everyone is doing their own thing.”
“There was so much information for the operational team,” said network engineer with a large energy company. “From circuits to IPs to devices, all that was in so many different Excel sheets and different spaces, and each team had its own version.”
Solution: Discovery tools, cooperation
There is no quick fix for solving data problems during NSoT projects, but network discovery tools can help. Network observability solutions can typically discovery a wide variety of relevant data on the network. IP address management tools also offer discovery. NSoT specialist vendors have also recently introduced discovery features. There will still be some manual data gathering and validation required, since not all NSoT data is online. Rack locations, patch panels, customer service contacts for WAN circuits may all require manual fact-finding, for instance.
Another key element of success is management buy-in. In this case, it’s not about budget. It’s about a getting support from mid- and -upper management. These authority figures can issue directives that require various engineering teams to cooperate with the NSoT project team. This is especially important if there are certain people in the organization who refuse to share or relinquish control of data.
