Why Network Management Is So Difficult?

 

At least once during a major network configuration or troubleshooting session, some viewers would look like a quiz, "Oh, that sounds too complicated. Is there a simpler way?"

This often happens when I kneel in a bunch of ssh or telnet sessions on various routers, switches or firewalls and keep dozens of variables in mind. "No," I answer, "no."

At this point, you might think that a weird person has a magical GUI interface and driver-driven components that can properly configure OSPF through the GRE, EIGRP redistribution, and BGP data exchange. It's been a long time - shouldn't it be much easier to manage now? The answer is obvious to network administrator salary. If all networks are the same, yes, it's okay. Reality says otherwise.

The validity of these protocols and tools lies within the scope and scope of the application. With Cisco IOS, you can do things that even Cisco people have never thought of. In terms of configuration, IOS is a programming language, not just a switching or routing platform. The reason why the Linux kernel is written in C instead of VPL (Visual Programming Language) is the same as why there is no stern GUI available for heavy routing and switching settings. Sure, there are SNMP-based tools that make it easy to switch switch-based VLAN assignments, translate firewalls, and add rules, but so far they can only do so. Inevitably, they hit the wall of what it was built to handle and what is really possible through the underlying operating system.

It is not just new configurations that these tools can handle. Troubleshooting and established networks tend to require more understanding and skill. There is no such thing as Clippy for heavy routing issues or simple issues like incorrect link configurations in LACP beams. In other words, there is no safety net in the network configuration. There is no convenient IDE that is somewhat aware that it transferred the two numbers to the OSPF network statement causing the remote routing protocol to fail.

This is not new to network administrators, but it is shocking for beginners. For some reason, many people think that configuring a 9-socket core switch or setting up an MPLS network works the same as configuring Wi-Fi on a Netgear home router. In some cases, we have even heard rumors that network administrators "make things seem more difficult than they really are" to keep things safe. Although this happens from time to time, the vast majority of network administrators run huge packet tracks to determine why WAN links are missing or why a particular subnet is not routing properly. I can do it. Remote grid VPN configuration does not overestimate the issue just to increase the situation.

Aside from the complexity (though still required) of the configuration interface and configuration elements as the same traffic safety allows the interface, these tools require a full understanding of the tool's capabilities arising from the lifelong learning process. there is. Also, unlike many other IT tasks, if you accidentally block access to a remote location and cannot return to the remote device to resolve the issue, there is no Undo button.

 

Yes, network management is difficult. It is perhaps the most demanding aspect of modern IT. That's the way it should be - at least until someone develops a network device that can read the mind.