SNMP is considered today the most widely-used supervision standard protocol. But which are the alternative protocols, and why decide on SNMP? Are there known situations when different protocols really should be utilized or perhaps are even now being used? These are basic questions that many people try to ask every so often. This is the reason I'll make an attempt to provide answers to them currently, based around my personal 21 years experience with Element, Network and also Service Management. Be aware that the next few paragraphs should be used as something to think about when researching today's protocol alternatives.
The Internet Engineering Task Force (IETF) released the SNMP protocol around the 1980s and it was quickly identified as a good network management protocol. From the beginning of the 21st century it became visible the fact despite that was originally designed, SNMP was not used to set up network equipment, but rather had been principally used for the purpose of network monitoring, i.e. Fault and Performance Management.
Around two thousand and two, the Internet Architecture Board and vital members of IETF's network management network met up with network operators to go over the problem. The outcome of this discussion are really registered on RFC 3535. It seems operators were mainly utilizing proprietary Command Line Interfaces (CLI) to configure their equipment. This specific contained a variety of functions the operators favored, such as the undeniable fact that it was actually text-based, rather than the BER-encoded SNMP. On top of that, many equipment manufacturers didn't present the way to completely configure their devices by means of SNMP.
Now regarding CLI, it became apparent that although operators sometimes liked to write scripts to assist manage their particular devices, they did find the CLI problematic. Most notable was the unforeseen nature of the end result. The information together with formatting of output was susceptible to alternation in unknown ways. Concurrently, Juniper Networks was in fact utilizing an XML-based network management process. That was shown the IETF and shared with a broader circle. These activities made IETF develop NetConf that's expected to be better aligned with all the desires of service providers and their suppliers.
Finally, specifically for routers/switches and IP networks, CISCO quickly understood that an increasingly compact protocol than SNMP seemed to be essential to scale significantly better for collection of performance counters on IP networks. Netflow, designed by CISCO is a standard nowadays (termed IPfix) that's been integrated by a lot of routers/switches Vendors.
The Internet Engineering Task Force (IETF) released the SNMP protocol around the 1980s and it was quickly identified as a good network management protocol. From the beginning of the 21st century it became visible the fact despite that was originally designed, SNMP was not used to set up network equipment, but rather had been principally used for the purpose of network monitoring, i.e. Fault and Performance Management.
Around two thousand and two, the Internet Architecture Board and vital members of IETF's network management network met up with network operators to go over the problem. The outcome of this discussion are really registered on RFC 3535. It seems operators were mainly utilizing proprietary Command Line Interfaces (CLI) to configure their equipment. This specific contained a variety of functions the operators favored, such as the undeniable fact that it was actually text-based, rather than the BER-encoded SNMP. On top of that, many equipment manufacturers didn't present the way to completely configure their devices by means of SNMP.
Now regarding CLI, it became apparent that although operators sometimes liked to write scripts to assist manage their particular devices, they did find the CLI problematic. Most notable was the unforeseen nature of the end result. The information together with formatting of output was susceptible to alternation in unknown ways. Concurrently, Juniper Networks was in fact utilizing an XML-based network management process. That was shown the IETF and shared with a broader circle. These activities made IETF develop NetConf that's expected to be better aligned with all the desires of service providers and their suppliers.
Finally, specifically for routers/switches and IP networks, CISCO quickly understood that an increasingly compact protocol than SNMP seemed to be essential to scale significantly better for collection of performance counters on IP networks. Netflow, designed by CISCO is a standard nowadays (termed IPfix) that's been integrated by a lot of routers/switches Vendors.
About the Author:
So, if you like to read some more, please check the following interesting articles: A History of SNMP and comparison with other protocols and What is the TMN Network Management model
0 comments:
Post a Comment