1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
96
97
98
99
100
101
102
103
104
105
106
107
108
109
110
111
112
113
114
115
116
117
118
119
|
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
<!-- This document was generated using DocBuilder 3.3.3 -->
<HTML>
<HEAD>
<TITLE>Manager Functional Description</TITLE>
<SCRIPT type="text/javascript" src="../../../../doc/erlresolvelinks.js">
</SCRIPT>
</HEAD>
<BODY BGCOLOR="#FFFFFF" TEXT="#000000" LINK="#0000FF" VLINK="#FF00FF"
ALINK="#FF0000">
<CENTER>
<A HREF="http://www.erlang.se"><IMG BORDER=0 ALT="[Ericsson AB]" SRC="min_head.gif"></A>
</CENTER>
<A NAME="3"><!-- Empty --></A>
<H2>3 Manager Functional Description</H2>
<A NAME="3.1"><!-- Empty --></A>
<H3>3.1 Features</H3>
<A NAME="features"><!-- Empty --></A>
<P>The manager provided with the tool is a lightweight manager
that basically provides a means to communinicate with agents.
<P>It does not really implement any management capabillities by
itself. That is up to the <STRONG>user</STRONG>.
<P>A <STRONG>user</STRONG> in this context is basically a module implementing
the <A HREF="snmpm_user.html">snmpm_user</A> behaviour.
A <STRONG>user</STRONG> can issue snmp requests and receive
notification/traps.
<P>Agents to be accessed by the manager needs to be registered by
a user. Once registered, they can be accessed by all registered
users.
<P>Notifications/traps from an agent is delivered to the user that
did the registration.
<P>Any message from an agent that is not registered is delivered to
the <STRONG>default user</STRONG>.
<P>By default, the <STRONG>default user</STRONG> is set to the
<CODE>snmpm_user_default</CODE> module, which simply sends an info message
to the error_logger. It is however highly recommended that this
module be replaced by another that does something usefull
(see <A HREF="snmp_config.html#configuration_params"> configuration params</A> for more info).
<P>When using version 3, then (at least one) <STRONG>usm user</STRONG> has to
be registered.
<P>Requests can be issued in two different ways. Synchronous (see
<A HREF="snmpm.html#s">s</A>,
<A HREF="snmpm.html#g">g</A>,
<A HREF="snmpm.html#gn">gn</A> and
<A HREF="snmpm.html#gb">gb</A>)
and asynchronous (see
<A HREF="snmpm.html#as">as</A>,
<A HREF="snmpm.html#ag">ag</A> and
<A HREF="snmpm.html#agn">agn</A>). With synchronou
the snmp reply is returned by the function. With asynchronous,
the reply will instead be delivered through a call to one of the
<CODE>handle_pdu</CODE> callback function defined by the
<A HREF="snmpm_user.html#handle_pdu">handle_pdu</A>
behaviour.<A NAME="3.2"><!-- Empty --></A>
<H3>3.2 Operation</H3>
<A NAME="operation"><!-- Empty --></A>
<P>The following steps are needed to get the manager running:
<P>
<OL>
<LI>
[optional] Implement the default user.<BR>
</LI>
<LI>
Implement the user(s).<BR>
</LI>
<LI>
Configure the application (manager).<BR>
</LI>
<LI>
Start the application (manager).<BR>
</LI>
<LI>
Register the user(s).<BR>
</LI>
<LI>
The user(s) register their agents.<BR>
</LI>
</OL>
<A NAME="3.3"><!-- Empty --></A>
<H3>3.3 MIB loading</H3>
<A NAME="mib_loading"><!-- Empty --></A>
<P>It is possible to load mibs into the manager, but this is not
necessary for normal operation, and not recomended.<CENTER>
<HR>
<SMALL>
Copyright © 1991-2006
<A HREF="http://www.erlang.se">Ericsson AB</A><BR>
</SMALL>
</CENTER>
</BODY>
</HTML>
|
