Part 1: An Introduction to SNMP


Manager-Agent Relationship
SNMP uses a manager/agent architecture. Alarm messages (Traps) are sent by the agent to the manager.

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 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 the widespread acceptance of SNMP.

Part of why SNMP has reached such wide adoption is due to the fact that it is an open standard. While there are widely accepted standards, there is 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.

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 (see illustration).

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.


Reality Check: What Can SNMP Do For Me?

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.

The advantages of SNMP are:

  • It's LAN-based. Moving your alarm monitoring off
    dedicated copper lines and onto existing LAN/WAN infrastructure creates significant savings. LAN data transport reduces installation and operation costs and transports alarm data more reliably.
  • It's an open standard. SNMP is non-proprietary, fully documented, and supported by multiple vendors.
  • It can be easily extended. SNMP is simple, but it's also flexible enough to describe almost anything. Vendors and users of SNMP equipment can add to the Management Information Base (MIB) to include nearly any kind of device.
  • It provides a common management platform for many different devices. If it's supplied with the right MIB file, an SNMP manager can correctly interpret alarm data from any device that supports SNMP, creating greater interoperability between different parts of your network.

That's what's good about SNMP - but there's also some pitfalls that you have to watch out for. If you're not careful, it's easy to wind up with a system that costs too much and does too little.

You can avoid the risks (and guarantee the benefits) of your SNMP implementation by working with an experienced vendor who can help you accurately determine your network monitoring needs. To learn more, call 1-800-693-0351 and ask for your free Network Monitoring Needs Analysis.