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
|
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
<!-- This document was generated using DocBuilder 3.3.3 -->
<HTML>
<HEAD>
<TITLE>Combining Mnesia with SNMP
</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="7"><!-- Empty --></A>
<H2>7 Combining Mnesia with SNMP
</H2>
<A NAME="7.1"><!-- Empty --></A>
<H3>7.1 Combining Mnesia and SNMP </H3>
<P>Many telecommunications applications must be controlled and
reconfigured remotely. It is sometimes an advantage to perform
this remote control with an open protocol such as the Simple
Network Management Protocol (SNMP). The alternatives to this would
be:
<P>
<UL>
<LI>
Not being able to control the application remotely at all.
</LI>
<LI>
Using a proprietary control protocol.
</LI>
<LI>
Using a bridge which maps control messages in a
proprietary protocol to a standardized management protocol and
vice versa.
</LI>
</UL>
<P>All of these approaches have different advantages and
disadvantages. Mnesia applications can easily be opened to the
SNMP protocol. It is possible to establish a direct one-to-one
mapping between Mnesia tables and SNMP tables. This
means that a Mnesia table can be configured to be <STRONG>both</STRONG>
a Mnesia table and an SNMP table. A number of functions to
control this behavior are described in the Mnesia reference
manual.
<CENTER>
<HR>
<SMALL>
Copyright © 1991-2006
<A HREF="http://www.erlang.se">Ericsson AB</A><BR>
</SMALL>
</CENTER>
</BODY>
</HTML>
|
