DEV 5072, Руководство пользователя

Страница: 48 / 71

User Manual DEV 5072
48

Copyright DEV Systemtechnik GmbH 2016-2017
5.5 Control via Remote Interface: SNMP
5.5.1 SNMP Overview
The "Simple Network Management Protocol" (SNMP) essentially is a request-reply
protocol running over UDP (usually ports
161 and 162 ). SNMP is an asymmetric
protocol operating between two types of management units: managers and agents.
A manager is called "Network Management Station" (NMS), which is usually a
computer on which one or more management systems are running. On small NMS,
command line tools can be used. On larger NMS normally third-party software, also
called a "network management suite" collects the data and provides a graphical
user interface.
An agent or SNMP-agent is software, which runs on a "Network Element" (NE).
NEs in a SNMP environment are called "nodes". An agent collects and stores infor-
mation from the system, translates the information in SNMP-compatible form, and
makes this information available to the manager. The agents manage the "objects"
of the node. Each object has an own individual management "Object ID" (OID).
In the system, the objects are the variables, which can be simple values or tables.
The object information is stored in the "Management Information Base" (MIB).
Note:

The iReasoning MIB Browser Personal Edition (including Trap Receiver) by
iReasoning Inc. is recommended to test the communication via SNMP.
5.5.2 Private Enterprise Number, Device Index Number
The Private Enterprise Number of DEV Systemtechnik GmbH is 21035.
This MIB is designed in SNMP v2 compliant format starting with the object sections
.sysDevModules and .devSysMibConformance, which are not described in this
context.
The actual MIB content for DEV Systemtechnik power systems starts with the
object section .dev-5071, which has the Device Index Number 34.
This concatenates to the string (i.e. the numerical OID: .1.3.6.1.4.1.21035.34):
iso.org.dod.internet.private.enterprises.dev-systemtechnik.dev-5071
1 . 3 . 6 . 1 . 4 . 1 . 21035 . 34
Note:

The intention for this MIB design was to keep the structure compatible with the
predecessor MIB, which was designed for the DEV 5071 (thus, the name of the
above mentioned object section). To support the extended functionality of the
DEV 5072 the MIB was supplemented with a few OIDs.