The other simplifying aspect is its reliance on an unsupervised or connectionless communication link. The small number of commands used is only one of the reasons SNMP is simple. This notifies the SNMP manager as soon as an alarm condition occurs, instead of waiting for the SNMP manager to ask. Because the Trap message is the only message capable of being initiated by an agent, it's the message that we use here for our RTUs to report alarms. SNMP Traps allow the agent to spontaneously inform the manager of an "important" event.Īs you can see, most of the messages (Get, GetNext, and Set) are only issued by the SNMP manager. The agent will then respond with a GetResponse message indicating the change has been made or an error indication as to why the change can't be made. The agent, upon receiving a Get or GetNext message, will issue a GetResponse message to the manager with either the information requested or an error indication as to why the request can't be processed.Ī Set message allows the manager to request a change be made to the value of a specific variable in the case of an alarm remote that will operate a relay. The Get and GetNext messages allow the manager to request information for a specific variable.
The SNMP protocol uses five basic message types to communicate between the manager and the agent: SNMP uses a manager/agent data structure. The agent provides the interface between the manager and the physical device(s) being managed. The manager provides the interface between the human network manager and the management system. SNMP is based on the manager/agent model that consists of a manager, agent, a database of management information, managed objects and the network protocol. While there are widely accepted standards, there's no governing body that controls how SNMP can and cannot be used, or declares and set rules for how messages are created and processed, making it extremely flexible and unable to be made obsolete by a singular vendor going out of business. This means that this protocol allows devices from different vendors to communicate with one another. Part of why SNMP has reached such wide adoption is due to the fact that it's an open standard. This long-term solution, however, never received the widespread of SNMP. SNMP was derived from its predecessor SGMP (Simple Gateway Management Protocol) and was intended to be replaced by a solution based on the CMIS/CMIP (Common Management Information Service/Protocol) architecture. Its advantage today is that a very large number of devices support it, enabling them to work together. Since its creation in 1988, as a short-term solution to manage elements in the growing Internet and other attached networks, SNMP has achieved widespread acceptance. SNMP can do a lot to make your network alarm monitoring more cost-effective and your network more reliable - if you clearly identify your network monitoring goals and have the right tools to achieve them.
0 kommentar(er)
