You need to see DPS gear in action. Get a live demo with our engineers.
Finding and solving problems in your SNMP implementation can be tough.
This guide helps you identify and solve SNMP issues.
Have a specific question? Ask our team of expert engineers and get a specific answer!
Sign up for the next DPS Factory Training!
Whether you're new to our equipment or you've used it for years, DPS factory training is the best way to get more from your monitoring.Reserve Your Seat Today
This is a brief overview of several core SNMP concepts.
The Simple Network Management Protocol (SNMP) was created in 1988 as a short-term solution to manage elements in the growing Internet and other attached networks. Since then, this protocol has achieved widespread acceptance.
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. This long-term solution, however, never received a widespread acceptance.
SNMP is based on the manager/agent model, consisting of a manager, an agent, a database of management information, managed objects, and the network protocol. The manager provides the interface between the human network manager and the management system. The agent provides the interface between the manager and the physical device(s) being managed.
The manager and agent use a Management Information Base (MIB) and a relatively small set of commands to exchange information. The MIB is organized in a tree structure with individual variables, such as point status or description, being represented as leaves on the branches. A long numeric tag or object identifier (OID) is used to distinguish each variable uniquely in the MIB and in SNMP messages.
The manager/agent model is very simple on the surface, but it takes many different forms. You have many different devices, each with their own MIB. Sometimes, manufacturers who claim, "Our device is SNMP compatible" will not provide a MIB. That makes it incredibly difficult to actually use this protocol for that device.
Since the original introduction of SNMPv1, architecture has been complicated by the arrival of new SNMP versions. V2c and V3 managers are generally backward-compatible with earlier versions, but security can become a concern. You may not WANT to use versions earlier than SNMPv3 to make sure that your remote-management traffic is always encrypted.
The different generations of SNMP have created a definite fracturing of what was once a simple architecture. Now, you have to consider the multi-generational devices you have in play and consider mediation devices to convert older versions to SNMPv3.