1
<?xml version="1.0" encoding="latin1" ?>
2
<!DOCTYPE chapter SYSTEM "chapter.dtd">
7
<year>2004</year><year>2009</year>
8
<holder>Ericsson AB. All Rights Reserved.</holder>
11
The contents of this file are subject to the Erlang Public License,
12
Version 1.1, (the "License"); you may not use this file except in
13
compliance with the License. You should have received a copy of the
14
Erlang Public License along with this software. If not, it can be
15
retrieved online at http://www.erlang.org/.
17
Software distributed under the License is distributed on an "AS IS"
18
basis, WITHOUT WARRANTY OF ANY KIND, either express or implied. See
19
the License for the specific language governing rights and limitations
24
<title>Manager Functional Description</title>
26
<responsible></responsible>
32
<file>snmp_manager_funct_descr.xml</file>
36
<title>Features</title>
37
<marker id="features"></marker>
38
<p>The manager provided with the tool is a lightweight manager
39
that basically provides a means to communicate with agents.</p>
40
<p>It does not really implement any management capabilities by
41
itself. That is up to the <em>user</em>.
43
<p>A <em>user</em> in this context is basically a module implementing
44
the <seealso marker="snmpm_user">snmpm_user</seealso> behaviour.
45
A <em>user</em> can issue snmp requests and receive
46
notification/traps.</p>
47
<p>Agents to be accessed by the manager needs to be registered by
48
a user. Once registered, they can be accessed by all registered
50
<p>Notifications/traps from an agent is delivered to the user that
51
did the registration.</p>
52
<p>Any message from an agent that is not registered is delivered to
53
the <em>default user</em>.</p>
54
<p>By default, the <em>default user</em> is set to the
55
<c>snmpm_user_default</c> module, which simply sends an info message
56
to the error_logger. It is however highly recommended that this
57
module be replaced by another that does something useful
58
(see <seealso marker="snmp_config#configuration_params">configuration params</seealso> for more info).</p>
59
<p>When using version 3, then (at least one) <em>usm user</em> has to
61
<p>Requests can be issued in two different ways. Synchronous (see
62
<seealso marker="snmpm#sync_set">sync_set</seealso>,
63
<seealso marker="snmpm#sync_get">sync_get</seealso>,
64
<seealso marker="snmpm#sync_get_next">sync_get_next</seealso> and
65
<seealso marker="snmpm#sync_get_bulk">sync_get_bulk</seealso>)
67
<seealso marker="snmpm#async_set">async_set</seealso>,
68
<seealso marker="snmpm#async_get">async_get</seealso>,
69
<seealso marker="snmpm#async_get_next">async_get_next</seealso> and
70
<seealso marker="snmpm#async_get_bulk">async_get_bulk</seealso>).
72
the snmp reply is returned by the function. With asynchronous,
73
the reply will instead be delivered through a call to one of the
74
<c>handle_pdu</c> callback function defined by the
75
<seealso marker="snmpm_user#handle_pdu">handle_pdu</seealso>
80
<title>Operation</title>
81
<marker id="operation"></marker>
82
<p>The following steps are needed to get the manager running:</p>
85
<p>[optional] Implement the default user.</p>
88
<p>Implement the user(s).</p>
91
<p>Configure the application (manager).</p>
94
<p>Start the application (manager).</p>
97
<p>Register the user(s).</p>
100
<p>The user(s) register their agents.</p>
106
<title>MIB loading</title>
107
<marker id="mib_loading"></marker>
108
<p>It is possible to load mibs into the manager, but this is not
109
necessary for normal operation, and not recomended.</p>