SDN (Software Defined Networking) promises some real benefits for those who use the network, but for the engineers who manage it, it may represent the end of an era.
Since Cisco created its first router in the 1980s, most network engineer have used a CLI (command line interface) to configure, manage, and troubleshoot everything from small office LANs to wide area operator networks. Dependents Cisco is not the only CLI, but its strength in networking has made it the de facto standard in the industry and is imitated by other vendors.
As a result, it is a ticket to career advancement for countless network professionals, especially those certified as CCNA (Cisco Certified Network Associates). According to the company, these network management professionals, along with the highest levels of Cisco Certified Network Experts (CCIE) and other official Cisco qualifications, make up more than two million trained workforces.
CLI is a way to simply enter a command line and interact with software, just like PC users did in DOS days. Using the Cisco CLI and its trace, engineers generally configure and manage networks by issuing commands to individual devices such as routers and switches.
A wide range of network and SDN workstations use a higher layer of software in a more abstract way. The new system is OpenFlow, Cisco ONE architecture (Open Network Environment) or Through the other framework, push the control plane of the so-called network job and push the packet. It is separated from the transfer plane that is formed by the team. The engine that manages the network is not a port but an application.
The network is the CLI or the command line. It was programmed through a so-called controller interface, which is currently being programmed by the program. -Modify to create a face.
Will SDN Ruin The Tools That Network Engineers Have Used Throughout Their Careers?
"If done correctly, it should stop the CLI, which can scare the bright sunlight from most CCIEs," said Gartner analyst Joe Skorpa. “Sure, about the fact that everyone who defines their value at work understands the more ambiguous Cisco CLI commands to configure some BGP4 (Border Gateway Protocol 4) parameters.
Not everyone thinks that CLI days are counted. SDN is not deep enough to analyze and correct all network flaws.
The compared SDN to driving a car and used the CLI to work on the car. For example, he said, with certain sets of ACLs (access control lists), some applications almost always have problems with some applications that only arise after the ACL has been built and used. Network engineers must use the CLI to diagnose and resolve these problems.
However, SDM reduces the use of the CLI for more routine tasks, says Mims. A network engineer who only knows the CLI looks like a manual worker whose job has been replaced by automation. He also said that some network jobs are likely to be removed.
A Canadian service provider, is not the first time that an alternative has emerged to challenge the CLI. Graphical user interfaces for managing networks have been around for many years, but they are not always welcome. "Engineers are always attracted to CLI as it becomes available.
The new network companies must provide a Cisco CLI to help customer engineers understand how to manage their products. Since 2005, Tail-F is one of the companies that opposes common orders.
The first introduced ConfD, a graphical tool for configuring network devices. After that, the company added NCS (Network Control System), which is a software platform to manage the entire network. To maintain interoperability, NCS interfaces with the Cisco CLI and third-party management systems.
CLI has its roots at the very foundation of the Internet. The focus of the Internet Engineering Working Group to monitor Internet Protocol (IP) was always to find a solution that works for a defined problem, he said. This detail-oriented "bottom-up" direction was different from how cellular networks were designed. He said he created the entire architecture at once with 3GPP, which developed the GSM standard used by most cell phone operators.
The IETF approach helped with manual device-by-device management, Moberg said. But as networks became more complex, that approach reached its limits. He said network changes would be more frequent and complex, leaving more room for human error and increasing the cost of error.
"Even the most experienced Cisco engineer is tired of typing the same command over and over and fails every 50 times," said Moberg. Although CLI will continue to exist, he said it will be a specialized tool for debugging in extreme situations.
"There will always be a certain level of CLI," With Nuage Networks' SDN system called Virtualized Services Platform launched earlier this year, Hanna said she wanted SDN to replace CLI. The number of lines of code contained in a system like VSP is "terrifying," he said.
Microsoft CEO Vijay Gill said in a panel discussion at the GigaOm Structure conference earlier this year that with a network fabric of 100,000 ports, scrolling through the list of ports would take an entire day.
"The system has gotten so big that you can't really do anything by hand," said Gil. Instead, the administrator would have to manipulate the software code and extend that code to provide commands to those ports, he said.
The most network administrators fall into two groups.
The first group "understands" and appreciates the need to fix the router at midnight. We would prefer to work with other IT and business managers to address a broader range of corporate problems. The second group, although initially unprepared, improves his skills and finally finds his place in a new landscape.
The secound group will never get one. They said they would face the same fate as telecommunications managers who relied on their work to learn the ambiguous commands of TDM (time division multiplexing) telephone systems. These engineers went offline when the circuit-switched voice was moved to VoIP (Voice over Internet Protocol) and connected to the LAN.
No comments:
Post a Comment