Merge branch 'bmk/20180927/remove_otp_mibs2/OTP-14984'

1 files changed, 16 insertions, 39 deletions

diff --git a/system/doc/oam/oam_intro.xml b/system/doc/oam/oam_intro.xml
index ead8c026b9..3d08a5f3b1 100644
--- a/system/doc/oam/oam_intro.xml
+++ b/system/doc/oam/oam_intro.xml
@@ -4,7 +4,7 @@
 <chapter>
   <header>
     <copyright>
-      <year>1997</year><year>2017</year>
+      <year>1997</year><year>2018</year>
       <holder>Ericsson AB. All Rights Reserved.</holder>
     </copyright>
     <legalnotice>
@@ -178,7 +178,7 @@
     <section>
       <title>MIB Structure</title>
       <p>The top-level OTP MIB is called <c>OTP-REG</c> and it is
-      included in the SASL application. All other OTP MIBs
+      included in the SNMP application. All other OTP MIBs
       import some objects from this MIB.</p>
 
       <p>Each MIB is contained in one application. The MIB text
@@ -186,67 +186,44 @@
       the application directory. The generated <c>.hrl</c> files
       with constant declarations are stored under
       <c><![CDATA[include/<MIB>.hrl]]></c>, and the compiled MIBs
-      are stored under <c><![CDATA[priv/mibs/<MIB>.bin]]></c>.
-      For example, the <c>OTP-MIB</c> is included in the
-      SASL application:</p>
+      are stored under <c><![CDATA[priv/mibs/<MIB>.bin]]></c>. </p>
 
-      <code type="none">
-sasl-1.3/mibs/OTP-MIB.mib
-include/OTP-MIB.hrl
-priv/mibs/OTP-MIB.bin</code>
-
-      <p>An application that needs to import this MIB into another
+      <p>An application that needs to import an MIB into another
       MIB is to use the <c>il</c> option to the SNMP MIB compiler:</p>
 
       <code type="none">
-snmp:c("MY-MIB", [{il, ["sasl/priv/mibs"]}]).</code>
+snmp:c("MY-MIB", [{il, ["snmp/priv/mibs"]}]).</code>
 
-      <p>If the application needs to include the generated
+      <p>If the application needs to include a generated
       <c>.hrl</c> file, it is to use the <c>-include_lib</c>
       directive to the Erlang compiler:</p>
 
       <code type="none">
 -module(my_mib).
--include_lib("sasl/include/OTP-MIB.hrl").</code>
+-include_lib("snmp/include/OTP-REG.hrl").</code>
 
-      <p>The following MIBs are defined in the OTP system:</p>
+      <p>Here is a list of some of the MIBs defined in the OTP system:</p>
       <list type="bulleted">
-	<item><p><c>OTP-REG</c> (in SASL) contains the top-level
+	<item><p><c>OTP-REG</c> (in SNMP) contains the top-level
 	OTP registration objects, used by all other MIBs.</p></item>
-	<item><p><c>OTP-TC</c> (in SASL) contains the general
+	<item><p><c>OTP-TC</c> (in SNMP) contains the general
 	Textual Conventions, which can be used by any other MIB.</p></item>
-	<item><p><c>OTP-MIB</c> (in SASL) contains objects for
-	instrumentation of the Erlang nodes, the Erlang machines,
-	and the applications in the system.</p></item>
-	<item><p><c>OTP-OS-MON-MIB</c> (in <c>oc_mon</c>) contains
-	objects for instrumentation of disk, memory, and CPU use
-	of the nodes in the system.</p></item>
 	<item><p><c>OTP-SNMPEA-MIB</c> (in <c>snmp</c>)
 	contains objects for instrumentation and control of the extensible
 	SNMP agent itself. The agent also implements the standard SNMPv2-MIB
 	(or v1 part of MIB-II, if SNMPv1 is used).</p></item>
-	<item><p><c>OTP-EVA-MIB</c> (in <c>eva</c>) contains objects
-	for instrumentation and control of the events and alarms in
-	the system.</p></item>
-	<item><p><c>OTP-LOG-MIB</c> (in <c>eva</c>) contains objects
-	for instrumentation and control of the logs and FTP transfer of
-	logs.</p></item>
-	<item><p><c>OTP-EVA-LOG-MIB</c> (in <c>eva</c>) contains objects
-	for instrumentation and control of the events and alarm logs
-	in the system.</p></item>
-	<item><p><c>OTP-SNMPEA-LOG-MIB</c> (in <c>eva</c>) contains
-	objects for instrumentation and control of the SNMP audit
-	trail log in the system.</p></item>
       </list>
 
       <p>The different applications use different strategies for
       loading the MIBs into the agent. Some MIB implementations are
       code-only, while others need a server. One way, used by the
       code-only MIB implementations, is for the user to call a
-      function such as <c>otp_mib:load(Agent)</c> to load the MIB,
-      and <c>otp_mib:unload(Agent)</c> to unload the MIB. See the
-      manual page for each application for a description of how
-      to load each MIB.</p>
+      function such as
+      <c>snmpa:unload_mibs(Agent, [Mib])</c>
+      to load the MIB, and
+      <c>snmpa:unload_mibs(Agent, [Mib])</c>
+      to unload the MIB. See the manual page for each application for
+      a description of how to load each MIB.</p>
     </section>
   </section>
 </chapter>