SNMP & its application in the

SRxxx I, V and L series product range

 TABLE OF CONTENTS

Introduction..3

Why use SNMP...3

SNMP Versions...3
Key Definitions.............4
How SNMP Works...5
Protocol Details.6
Management Information Base (MIB)...7
Implementation..7
Potential Challenges.8
SNMP in Perspective...8
Practical Use of SNMP8
Conclusion..9

Innovative Energies and its products...10

Innovative Energies 10
SNMP-capable Products.....10
Configuring SNMP on Srxxx PSU.............13

Using the MIB Browser...14

iReasoning MIB Browser.14
CastleRock snmpc example...19

Innovative Energies Ltd 1, Heremai Street, Auckland, NZ Ph: +64 98350700. www.innovative.co.nz 2
1. Introduction
SNMP, Simple Network Management Protocol, is an internet standard protocol for monitoring
and managing devices on IP networks. This white paper offers a general understanding of
how SNMP and its components work together to manage the network devices, its
advantages and the overview of SNMP enabled power supplies by Innovative Energies.

SNMP is a network management protocol which is used to exchange messages between

Network Management Systems (thereafter referred to as NMS) and agents that are
embedded in the operating system of manageable network devices.

The SNMP can be used in any environment where critical monitoring of network devices is
involved. The notifications are available from SNMP management system if certain user-
defined thresholds are exceeded.

Even though SNMP was developed in the 1980s, SNMP support is still a quality feature of
professional hardware to this date, and consequently has been integrated in Innovative
Energies I, V and L series PSUs.

Why use SNMP?

Before SNMP was developed, most network devices were managed individually - typically by
proprietary network management software. Unfortunately, only a single vendors devices
could be managed by such software and the lack of interoperability resulted in overly
complex management implementations.

As businesses became more and more dependent on connected computer systems,

monitoring and ensuring their reliability in performance also became a necessity. Because of
the huge amount of devices available from various manufacturers, it was imperative to
introduce a standard for such monitoring.

Defined by the Internet Engineering Task Force (IETF) in 1988, SNMP v1 was designed to
help monitor complex multi-vendor networks. Since then, two more SNMP versions have
been ratified by the IETF. Today, SNMP is still the standard for network management.

SNMP delivers management information in a common, non proprietary manner, making it

easy for an administrator to manage devises from different vendors using the same tools and
interface.

SNMP Versions

The first version of SNMP, SNMPv1, was the first implementation of SNMP. It provided the
basic structure and process required to define network management information, retrieve
information from network devices, control devices, and allow unsolicited messagescalled
Trapsto be sent to a NMS. It operates over protocols such as User Datagram Protocol
(UDP) and Internet Protocol (IP).

SNMPv1 was extended several times to incorporate new features and subsequently,
SNMPv2 included improvements in the areas of performance and security. It gave the

Innovative Energies Ltd 1, Heremai Street, Auckland, NZ Ph: +64 98350700. www.innovative.co.nz 3
capability to retrieve data in bulk rather than individually. and added the capability for the
NMS to acknowledge a trap message.

SNMPv3 added encryption both for the community strings that are used to access a network
device and the SNMP data transmitted between devices. It also included remote
configuration enhancements. Although the protocol was not otherwise changed, things look
quite different due to the introduction of textual conventions and terminology.

SNMPv1, which is very simple and does not contain encoding or similar mechanisms, is still
the most frequently used variant in private LANs behind a firewall. Use of this version is not
recommended for public nets due to the lack of security in this version. Nevertheless, many
simple devices still only offer SNMPv1.

The current version of SNMP is SNMPv3. However due to its relatively complex use, this
version has not really managed to establish itself for use in intranets since it was specified in
2002.

Key Definitions

Network Element(s): Network element is a monitored device. An element is often referred to

as a node or a managed node.

Network Management Systems (NMS): A server that runs the network management
application. It is the primary recipient that network elements communicate with to relay the
management and control information.

Management Information Base (MIB): The MIB is a database containing Object Identifier
(OID) information. MIB contains the information in the form of variable which would be useful
to manage the specific item. It is a hierarchical tree-based structure where the MIB is the
tree and each individual object is a leaf. Each object is identified by an OID.

SNMP MIBs must be loaded into the management system in order for it to be able to use the
OIDs defined by that MIB. Most management systems will have many standard MIBs already
loaded.

Object Identifier (OID): An object identifier is simply a unique id represented by a series of

numbers and dots that has a unique corresponding name. Object Identifiers identify
individual entries, or objects, within the MIB. OIDs are specified using an x,y naming
convention, defined by Abstract Syntax Notation One (ASN.1). In this naming convention, x
is a numeric value identifying an OIDs position within the MIB tree and y is a human-
readable OID name, also called a variable name.

The numerical OIDs make searching through the MIB and reporting human readable
information an easier process. Most OIDs start with .1.3.6.1 where 1 = iso, 3 = org, 6 = dod,
1 = internet. Once an OID is at the Internet identifier there are two branches, mgmt and
private. Private OIDs are developed by vendors for managing their specific products.

Traps: Traps are the method by which important, unsolicited information is reported. No trap
response is defined in SNMPv1. Each managed element must have one or more Trap
receivers defined in order for the Trap to be effective.

Innovative Energies Ltd 1, Heremai Street, Auckland, NZ Ph: +64 98350700. www.innovative.co.nz 4
In SNMPv2 and higher, the concept of a Trap was extended using another SNMP message
called Inform. Like a Trap, an Inform message is unsolicited. However, Inform enables an
NMS running SNMPv2 (or higher) to send a Trap to another NMS. It can also be used by a
SNMPv2 (or higher) managed node to send an SNMPv2 Trap. The receiving node sends a
response telling the sending NMS that the receiving NMS received the Inform message. Both
messages are sent on UDP Port 161.

Trap notifications are supported in SNMPv1 and later but are considered non-robust because
the SNMP manager doesnt send an acknowledgement in response to the Trap. The device
sending the Trap sends it only once. The sending device has no confirmation that the Trap
has been received so there is no guarantee that the alarm information has been successfully
sent to the SNMP manager.

Inform notifications, supported in some SNMPv2c implementations or SNMPv3, are designed

to allow confirmation of delivery. When an SNMP manager receives an Inform, it sends a
confirmation response back to the SNMP agent device. If a well-designed SNMP agent
device doesnt receive a response to its Inform, it resends it until the SNMP manager sends
the confirmation response or the specified number of retries is exhausted.

Community: SNMP specifies two groups, called communities, to enable access to the OIDs
on a managed element. SNMP community strings work as passwords to gain access to an
elements OIDs.

The read-community string, named public by default, allows read-only access. The write-
community string, named private by default, allows write access.

Both community strings must be defined for full management access to an element and
common community strings must be defined on all elements, probes, and NMSs for full
management in an SNMP domain.

Until SNMPv3, community strings were sent in clear text thus reducing SNMP security. All
security precautions should be exercised when using SNMP on a network to ensure
unauthorized personnel or system can not gain access to any network device. SNMPv3
specifies encrypted community strings and PDUs.

How SNMP Works

Basic communication
Through SNMP, client-server communication can take place via UDP. A monitoring (or
management) software sends as a client a UDP packet to the SNMP server (the agent,
which is normally a piece of software running within a device). This in turn reacts by sending
an SNMP packet as an answer.

Each single question-answer cycle enables the client to retrieve one measurement from the
device (for example network traffic, PSU-load, temperature etc). Depending on the enquiry
method, several measurements can be transferred at a time.

It is a prerequisite that the device must be available through a network connection and have
access to an SNMP server. It must also be a device which can react to requests.

Innovative Energies Ltd 1, Heremai Street, Auckland, NZ Ph: +64 98350700. www.innovative.co.nz 5
Control Commands and SNMP Traps
Control commands with which the client can set certain measurements and options within the
device and change its settings are transferred via SNMP.

While in classic communication the client always actively requests information from the
server, SNMP allows the additional use of data packages called traps. These are sent from
the SNMP server to the client without being explicitly requested. Management software can
therefore react immediately without delay to incidents.

The process is relatively simple and straightforward. Unfortunately the data packages are
created in a complex description language that is based on the Abstract Syntax Notation
One (ASN.1) and this complexity can lead to fault in the implementation.

Protocol Details

SNMP operates in the Application Layer of the Internet Protocol Suite (Layer 7 of the OSI
model). The manager may send requests from any available source port to port 161 by
default in the SNMP agent. The SNMP agent response will be sent back to the source port
on the manager. The manager receives notifications (Traps and InformRequests) on port 162
by default.

SNMPv1 specifies five core protocol data units (PDUs). Two other PDUs, GetBulkRequest
and InformRequest were added in SNMPv2 and carried over to SNMPv3.

All SNMP PDUs are constructed as follows:

IP header
UDP header
Version
Community
PDU-type
Request-id
Error-status
Error-index
Variable bindings

The seven SNMP protocol data units (PDUs) are:

GetRequest: A manager-to-agent request to retrieve the value of a variable or list of

variables.

SetRequest: A manager-to-agent request to change the value of a variable or list of

variables.

GetNextRequest: A manager-to-agent request to discover available variables and their

values. The entire MIB of an agent can be walked by iterative application of GetNextRequest
starting at OID 0.

GetBulkRequest: Optimized version of GetNextRequest introduced in SNMPv2. A manager-

to-agent request for multiple iterations of GetNextRequest.

Innovative Energies Ltd 1, Heremai Street, Auckland, NZ Ph: +64 98350700. www.innovative.co.nz 6
Response: Returns variable bindings and acknowledgement from agent to manager for
GetRequest, SetRequest, GetNextRequest, GetBulkRequest and InformRequest. Although it
was used as a response to both gets and sets, this PDU was called GetResponse in
SNMPv1.

Trap: Asynchronous notification from agent to manager. Destination addressing for traps is
determined in an application-specific manner typically through trap configuration variables in
the MIB.

InformRequest: Acknowledged asynchronous notification manager to manager or agent to

manager. InformRequest sends back an acknowledgement on receipt of a trap. This PDU
was introduced in SNMPv2.

Management Information Base (MIB)

A MIB is a virtual database used for managing the entities in a communications network.
While the term is used generically it is most often associated with SNMP.

Indeed, in order for SNMP clients and servers to exchange corresponding measurements,
the available SNMP objects must have addresses that are known to both sides. This is
necessary for a successful transfer of the measurements and network monitoring using
SNMP.

The Management Information Base (MIB) was created as an independent tree-structured

format for the storage of device information. It allows access to be gained regardless of the
manufacturer, as well as when different client-server combinations are used.

A MIB is a text-file in which all searchable SNMP objects of a device are listed in a
standardized tree hierarchy. Entries are addressed through object identifiers (OIDs) and a
MIB contains at least one OID that delivers not only the necessary unique address and
name, but also information on type, access rights and a description of the respective object.

Each knot in the tree structure of the MIB contains a unique ID and a name that identify the
underlying branch. To find out the address of a specific knot one has to move through the
tree structure from the root to the bottom. To obtain the address of an object, you must note
the number of every knot and string the numbers of all the knots together, separating them
by a dot. This string of numbers is called the OID of an SNMP object.

Implementation

In its simplest form, an SNMP agent is loaded on a host with the appropriate MIB
components. MIB components include the SNMP MIB, and may include extensions such as
RMON, SMON, private MIB, or a combination.

The agent is configured to communicate with one or more NMSs using specific SNMP
community strings. The NMS IP address is also configured to enable the agent to send traps
or notifications. The agent contains the SNMP MIB and typically, the manufacturers private
MIB extensions.

Innovative Energies Ltd 1, Heremai Street, Auckland, NZ Ph: +64 98350700. www.innovative.co.nz 7
The NMS is configured with the same community strings as the elements it manages. The
NMS is also configured with the appropriate combination of SNMP MIB and extensions
required to manage the agents for which it is responsible as well as with the IP addresses of
the agents it is to manage. SNMP communication requires network devices to open UDP
Ports 161 and 162 for polling and traps/notifications.

After initial configuration is complete, the SNMP agent collects information. The NMS
periodically polls the agent. When appropriate, the agent sends unsolicited traps to the NMS.
The NMS may be used to modify the agent configuration as appropriate.

Potential Challenges

Network monitoring with SNMP works very reliably in most cases. Suitable and well-
designed software can help to avoid many problems right from the start.

One of the challenges that can occur is load problems. These take place when the SNMP
client triggers too many enquiries within a very short time period because of a too optimistic
configuration. This can cause a temporary network disturbance. A good solution should
provide sensible default values.

The overall effort needed for setup is often underestimated and it can be especially time
consuming when MIBs are missing or faulty.

Also, some devices change their SNMP OIDs at every reboot. It is normal that fixed OIDs are
listed in the configuration when monitoring, but this can lead to obstacles. If the SNMP
objects cannot be found at their former OID address by the client software, no more data can
be requestedand the monitoring comes to a standstill. This problem can be avoided by
using software that automatically re-assigns OIDs.

SNMP in Perspective

Despite many problems and security risks, SNMPv1 is widely used. One reason for this is a
lack of mainstream alternatives. SNMP is used universally and a great number of devices
provide it as the sole standard to readout values.

Compared to previous monitoring and management methods, SNMP reduces the amount of
overhead on the network element while using a common platform. This allows SNMP to be
used on most IP networks often using a single, centralized NMS.

Practical Use of SNMP

A network monitoring solution deals with the request and evaluation of the data collected via
SNMP. In the case of the Innovative I, V & L series products, the results are displayed in a
website and can be viewed easily by the user. More details on how SNMP is applied to
Innovative Energies PSUs are provided in sections 2 and 3 of this document.

Innovative Energies Ltd 1, Heremai Street, Auckland, NZ Ph: +64 98350700. www.innovative.co.nz 8
Conclusion

IT system monitoring has grown considerably through the use of SNMP agents, probes and
NMSs and the requirement for administrators to manually monitor individual network
components was greatly reduced.

The ability to have systems inform an NMS, and ultimately humans, of error conditions has
led to increased up-time and availability. SNMP provides many of the tools necessary to
collect and analyze data to enable system-tuning for optimum performance. It can also help
identify when and where future growth in the network is required.

Innovative Energies Ltd 1, Heremai Street, Auckland, NZ Ph: +64 98350700. www.innovative.co.nz 9
 2. Innovative Energies & SNMP capable products

Innovative Energies

Innovative Energies is a specialist manufacturer of No-Break DC UPS (uninterruptible power

supplies) and complementary power electronic products and technologies, with over 20 years of
trading.

We are a leading ISO 9001:2000 registered manufacturer of:

DC Power Supplies
DC/DC Converters
Intelligent Battery Charging Systems & Solutions

Our vast range of products is produced and sold to established markets in New Zealand and
Australia, with plans to extend our offshore business already being implemented in Turkey,
Singapore, Thailand, Argentina, USA and the Pacific Islands.

Innovative Energies No-Break DC UPS technology is a unique and comprehensive approach to

providing uninterruptible and secure DC power when you need it.

SNMP Capable Products

SNMP is now being implemented in the Innovative Energies Power Supplies which enables
users to monitor and control the power supplies and batteries, and be notified with the status of
the system via email, pagers or mobile phones, etc.

This functionality comes with our new LAN+ range of No-Break DC UPS Power Supplies and
AC-DC Power Supplies. When SNMP features in power supplies it allows users to control and
monitor their power supplies remotely from any communication device connected to the
Internet

Features & Benefits

Even Low power (starting from 100 Watt) battery chargers can be managed remotely
Standardized protocol
Easy monitoring & management using web browser or SNMP manager
Remote Device Management
Configurable Software

The SNMP capable power supplies / battery chargers are available in three different versions.

SRxxx I
SRxxx L
SRxxx V

Innovative Energies Ltd 1, Heremai Street, Auckland, NZ Ph: +64 98350700. www.innovative.co.nz 1
0
The different power supplies connected in a network can be managed from a single location
using any of the SNMP manager as shown below.

Figure below explains the communication / SNMP delivery mechanism between managed device
(SRxxx I/L/V) and SNMP Manager (PC hosting MIB files).

Managed Device SNMP Manager

Innovative Energies Ltd 1, Heremai Street, Auckland, NZ Ph: +64 98350700. www.innovative.co.nz 1
1
The various parameters regarding power supply and battery system (for eg. voltage, current,
temperature etc) can be monitored remotely using the Get command.
The user can even set the high/low thresholds for temp, voltage etc and can receive the
trap/alarms when this threshold limits are crossed.

Battery Condition Test

The other important feature of no-break power supply with SNMP is its capability to remotely
start/stop a battery condition test.

The BCT feature is ideal for remote or automated sites and allows plant operators to

Minimize cost of maintenance

determine the condition of the back-up batteries and will provide an early warning of
potential failure

Innovative Energies Ltd 1, Heremai Street, Auckland, NZ Ph: +64 98350700. www.innovative.co.nz 1
2
Configuring SNMP on Srxxx PSU

It is recommended to view the SNMP setting page on the PSU website in order to check the
SNMP configuration before use with any SNMP network manager. For instance, the port
settings as well as the communities passwords need to match thnse configured in the SNMP
manager application.

The SNMP agent is always enabled but the trap sender can be disabled if necessary.

The SNMP Configuration page allows the user to enable or disable SNMP Trap, set the
Trap Destination IP, SNMP Trap Port and SNMP Agent Port among other things.

To be able to receive traps in the MIB Browser, SNMP Trap must be enabled and the Trap
Destination IP, SNMP Trap Port and SNMP Agent Port must be correctly set.

The Trap Destination IP must be the IP address of the PC on which MIB Browser is running.

Innovative Energies Ltd 1, Heremai Street, Auckland, NZ Ph: +64 98350700. www.innovative.co.nz 1
3
3. Using the MIB Browser
iReasoning MIB Browser

This section is based on version 7.5 of the iReasoning MIB Browser which can be
downloaded from http://ireasoning.com/mibbrowser.shtml.

Firstly, load the relevant MIB files into the MIB Browser. To do so, go to File -> Load MIBs in
the top menu:

Open the following files:

INNOVATIVE-ENERGIES-SRXXX-I-SERIES-MIB.mib
INNOVATIVE-ENERGIES-SRXXX-L-SERIES-MIB.mib
INNOVATIVE-ENERGIES-SRXXX-V-SERIES-MIB.mib

You will now see the following branches in the MIB tree:

By expanding those branches, you will be able to view all the variables that can be read
and/or set. For example if you expand the ieSRxxxiSeries branch, you will see the following:

Innovative Energies Ltd 1, Heremai Street, Auckland, NZ Ph: +64 98350700. www.innovative.co.nz 1
4
Innovative Energies Ltd 1, Heremai Street, Auckland, NZ Ph: +64 98350700. www.innovative.co.nz 1
5
The IP address shown at the top of the previous screenshot must be the IP address of the
unit used to perform the tests.

By clicking on the advanced button next to Address, you will see the following:

You will need to make sure that the address corresponds to that of the unit being used for
testing and that the port corresponds to the SNMP Agent Port shown on the SNMP
Configuration page of the website (see page 15 of this document). The Read Community and
Write Community should be the same as those shown on the SNMP Configuration page of
the website.

Innovative Energies Ltd 1, Heremai Street, Auckland, NZ Ph: +64 98350700. www.innovative.co.nz 1
6
From the top menu, click on Tools -> Trap Receiver

This will open a new tab Trap Receiver next to the Result Table. The Trap Receiver table
will allow you to verify that the relevant ON and OFF traps are sent appropriately depending
on the test being performed.

Clicking on the red circle will stop the trap receiver - to start it again, click on the circle to its
left (which will be green with a white triangle inside it when trap receiver is stopped).

Clicking on the button next to the red circle will clear the list of traps shown in Trap Receiver
(the same button on the Result Table will clear the results in that tab).

In the Trap Receiver tab, click on Tools -> Options

Innovative Energies Ltd 1, Heremai Street, Auckland, NZ Ph: +64 98350700. www.innovative.co.nz 1
7
The Trap Receiver Settings will be shown. Please check that the Trap Port is the same as
the SNMP Trap Port specified on the SNMP Configuration page of the website (see page 15
of this document).

Innovative Energies Ltd 1, Heremai Street, Auckland, NZ Ph: +64 98350700. www.innovative.co.nz 1
8
The Result Table tab will allow you to get or set the value of every SNMP variable that needs
to be checked.

To view the value of a variable, right-click on the variable that you wish to verify and select
Get. Alternatively, clicking on Walk will display the value of all the variables in the Result
Table.

Innovative Energies Ltd 1, Heremai Street, Auckland, NZ Ph: +64 98350700. www.innovative.co.nz 1
9
To set the value of a variable, for example the Overvoltage Threshold as in next screenshot,
right-click on the variable, select Set and fill in the Value field to desired value. Make sure
that the data type is correct for the variable you are setting a value for.

Innovative Energies Ltd 1, Heremai Street, Auckland, NZ Ph: +64 98350700. www.innovative.co.nz 2
0
CastleRock snmpc example

The following screenshot demonstrates the monitoring of a Srxxx I Serie with the CastleRock snmpc SNMP manager. The system
monitors the battery and load currents as well as the PSU output voltage during a mains fail situation.

2
Innovative Energies Ltd 1, Heremai Street, Auckland, NZ Ph: +64 98350700. www.innovative.co.nz
1