logstash-input-snmp 0.1.0.beta4 → 0.1.0.beta5

data/lib/mibs/ietf/SNMP-TSM-MIB.dic

@@ -0,0 +1,315 @@
+# python version 1.0						DO NOT EDIT
+#
+# This python file has been generated by smidump version 0.5.0:
+#
+#   smidump -f python SNMP-TSM-MIB
+
+FILENAME = "./libsmi-0.5.0/mibs/ietf/SNMP-TSM-MIB"
+
+MIB = {
+    "moduleName" : "SNMP-TSM-MIB",
+
+    "SNMP-TSM-MIB" : {
+        "nodetype" : "module",
+        "language" : "SMIv2",
+        "organization" :    
+            """ISMS Working Group""",
+        "contact" : 
+            """WG-EMail:   isms@lists.ietf.org
+Subscribe:  isms-request@lists.ietf.org
+
+Chairs:
+  Juergen Quittek
+  NEC Europe Ltd.
+  Network Laboratories
+  Kurfuersten-Anlage 36
+  69115 Heidelberg
+  Germany
+  +49 6221 90511-15
+  quittek@netlab.nec.de
+
+  Juergen Schoenwaelder
+  Jacobs University Bremen
+  Campus Ring 1
+  28725 Bremen
+  Germany
+  +49 421 200-3587
+  j.schoenwaelder@jacobs-university.de
+
+
+
+
+
+Editor:
+  David Harrington
+  Huawei Technologies USA
+  1700 Alma Dr.
+  Plano TX 75075
+  USA
+  +1 603-436-8634
+  ietfdbh@comcast.net
+
+  Wes Hardaker
+  Cobham Analytic Solutions
+  P.O. Box 382
+  Davis, CA  95617
+  USA
+  +1 530 792 1913
+  ietf@hardakers.net""",
+        "description" :
+            """The Transport Security Model MIB.
+
+In keeping with the RFC 3411 design decisions to use
+self-contained documents, the RFC that contains the definition
+of this MIB module also includes the elements of procedure
+that are needed for processing the Transport Security Model
+for SNMP.  These MIB objects SHOULD NOT be modified via other
+subsystems or models defined in other documents.  This allows
+the Transport Security Model for SNMP to be designed and
+documented as independent and self-contained, having no direct
+impact on other modules, and this allows this module to be
+upgraded and supplemented as the need arises, and to move
+along the standards track on different time-lines from other
+modules.
+
+Copyright (c) 2009 IETF Trust and the persons
+identified as authors of the code.  All rights reserved.
+
+Redistribution and use in source and binary forms, with or
+without modification, are permitted provided that the
+following conditions are met:
+
+- Redistributions of source code must retain the above copyright
+  notice, this list of conditions and the following disclaimer.
+
+- Redistributions in binary form must reproduce the above
+  copyright notice, this list of conditions and the following
+  disclaimer in the documentation and/or other materials
+  provided with the distribution.
+
+
+
+
+- Neither the name of Internet Society, IETF or IETF Trust,
+  nor the names of specific contributors, may be used to endorse
+  or promote products derived from this software without
+  specific prior written permission.
+
+THIS SOFTWARE IS PROVIDED BY THE COPYRIGHT HOLDERS AND
+CONTRIBUTORS 'AS IS' AND ANY EXPRESS OR IMPLIED WARRANTIES,
+INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES OF
+MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE ARE
+DISCLAIMED.  IN NO EVENT SHALL THE COPYRIGHT OWNER OR
+CONTRIBUTORS BE LIABLE FOR ANY DIRECT, INDIRECT, INCIDENTAL,
+SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES (INCLUDING, BUT
+NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES;
+LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION)
+HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN
+CONTRACT, STRICT LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR
+OTHERWISE) ARISING IN ANY WAY OUT OF THE USE OF THIS SOFTWARE,
+EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE.
+
+This version of this MIB module is part of RFC 5591;
+see the RFC itself for full legal notices.""",
+        "revisions" : (
+            {
+                "date" : "2009-06-09 00:00",
+                "description" :
+                    """The initial version, published in RFC 5591.""",
+            },
+        ),
+        "identity node" : "snmpTsmMIB",
+    },
+
+    "imports" : (
+        {"module" : "SNMPv2-SMI", "name" : "MODULE-IDENTITY"},
+        {"module" : "SNMPv2-SMI", "name" : "OBJECT-TYPE"},
+        {"module" : "SNMPv2-SMI", "name" : "mib-2"},
+        {"module" : "SNMPv2-SMI", "name" : "Counter32"},
+        {"module" : "SNMPv2-CONF", "name" : "MODULE-COMPLIANCE"},
+        {"module" : "SNMPv2-CONF", "name" : "OBJECT-GROUP"},
+        {"module" : "SNMPv2-TC", "name" : "TruthValue"},
+    ),
+
+    "nodes" : {
+        "snmpTsmMIB" : {
+            "nodetype" : "node",
+            "moduleName" : "SNMP-TSM-MIB",
+            "oid" : "1.3.6.1.2.1.190",
+            "status" : "current",
+        }, # node
+        "snmpTsmNotifications" : {
+            "nodetype" : "node",
+            "moduleName" : "SNMP-TSM-MIB",
+            "oid" : "1.3.6.1.2.1.190.0",
+        }, # node
+        "snmpTsmMIBObjects" : {
+            "nodetype" : "node",
+            "moduleName" : "SNMP-TSM-MIB",
+            "oid" : "1.3.6.1.2.1.190.1",
+        }, # node
+        "snmpTsmStats" : {
+            "nodetype" : "node",
+            "moduleName" : "SNMP-TSM-MIB",
+            "oid" : "1.3.6.1.2.1.190.1.1",
+        }, # node
+        "snmpTsmInvalidCaches" : {
+            "nodetype" : "scalar",
+            "moduleName" : "SNMP-TSM-MIB",
+            "oid" : "1.3.6.1.2.1.190.1.1.1",
+            "status" : "current",
+            "syntax" : {
+                "type" : { "module" :"SNMPv2-SMI", "name" : "Counter32"},
+            },
+            "access" : "readonly",
+            "description" :
+                """The number of incoming messages dropped because the
+
+
+
+tmStateReference referred to an invalid cache.""",
+        }, # scalar
+        "snmpTsmInadequateSecurityLevels" : {
+            "nodetype" : "scalar",
+            "moduleName" : "SNMP-TSM-MIB",
+            "oid" : "1.3.6.1.2.1.190.1.1.2",
+            "status" : "current",
+            "syntax" : {
+                "type" : { "module" :"SNMPv2-SMI", "name" : "Counter32"},
+            },
+            "access" : "readonly",
+            "description" :
+                """The number of incoming messages dropped because
+the securityLevel asserted by the Transport Model was
+less than the securityLevel requested by the
+application.""",
+        }, # scalar
+        "snmpTsmUnknownPrefixes" : {
+            "nodetype" : "scalar",
+            "moduleName" : "SNMP-TSM-MIB",
+            "oid" : "1.3.6.1.2.1.190.1.1.3",
+            "status" : "current",
+            "syntax" : {
+                "type" : { "module" :"SNMPv2-SMI", "name" : "Counter32"},
+            },
+            "access" : "readonly",
+            "description" :
+                """The number of messages dropped because
+snmpTsmConfigurationUsePrefix was set to true and
+there is no known prefix for the specified transport
+domain.""",
+        }, # scalar
+        "snmpTsmInvalidPrefixes" : {
+            "nodetype" : "scalar",
+            "moduleName" : "SNMP-TSM-MIB",
+            "oid" : "1.3.6.1.2.1.190.1.1.4",
+            "status" : "current",
+            "syntax" : {
+                "type" : { "module" :"SNMPv2-SMI", "name" : "Counter32"},
+            },
+            "access" : "readonly",
+            "description" :
+                """The number of messages dropped because
+the securityName associated with an outgoing message
+did not contain a valid transport domain prefix.""",
+        }, # scalar
+        "snmpTsmConfiguration" : {
+            "nodetype" : "node",
+            "moduleName" : "SNMP-TSM-MIB",
+            "oid" : "1.3.6.1.2.1.190.1.2",
+        }, # node
+        "snmpTsmConfigurationUsePrefix" : {
+            "nodetype" : "scalar",
+            "moduleName" : "SNMP-TSM-MIB",
+            "oid" : "1.3.6.1.2.1.190.1.2.1",
+            "status" : "current",
+            "syntax" : {
+                "type" : { "module" :"SNMPv2-TC", "name" : "TruthValue"},
+            },
+            "access" : "readwrite",
+            "default" : "false",
+            "description" :
+                """If this object is set to true, then securityNames
+passing to and from the application are expected to
+contain a transport-domain-specific prefix.  If this
+object is set to true, then a domain-specific prefix
+will be added by the TSM to the securityName for
+incoming messages and removed from the securityName
+when processing outgoing messages.  Transport domains
+and prefixes are maintained in a registry by IANA.
+This object SHOULD persist across system reboots.""",
+        }, # scalar
+        "snmpTsmConformance" : {
+            "nodetype" : "node",
+            "moduleName" : "SNMP-TSM-MIB",
+            "oid" : "1.3.6.1.2.1.190.2",
+        }, # node
+        "snmpTsmCompliances" : {
+            "nodetype" : "node",
+            "moduleName" : "SNMP-TSM-MIB",
+            "oid" : "1.3.6.1.2.1.190.2.1",
+        }, # node
+        "snmpTsmGroups" : {
+            "nodetype" : "node",
+            "moduleName" : "SNMP-TSM-MIB",
+            "oid" : "1.3.6.1.2.1.190.2.2",
+        }, # node
+    }, # nodes
+
+    "groups" : {
+        "snmpTsmGroup" : {
+            "nodetype" : "group",
+            "moduleName" : "SNMP-TSM-MIB",
+            "oid" : "1.3.6.1.2.1.190.2.2.2",
+            "status" : "current",
+            "members" : {
+                "snmpTsmInvalidCaches" : {
+                    "nodetype" : "member",
+                    "module" : "SNMP-TSM-MIB"
+                },
+                "snmpTsmInadequateSecurityLevels" : {
+                    "nodetype" : "member",
+                    "module" : "SNMP-TSM-MIB"
+                },
+                "snmpTsmUnknownPrefixes" : {
+                    "nodetype" : "member",
+                    "module" : "SNMP-TSM-MIB"
+                },
+                "snmpTsmInvalidPrefixes" : {
+                    "nodetype" : "member",
+                    "module" : "SNMP-TSM-MIB"
+                },
+                "snmpTsmConfigurationUsePrefix" : {
+                    "nodetype" : "member",
+                    "module" : "SNMP-TSM-MIB"
+                },
+            }, # members
+            "description" :
+                """A collection of objects for maintaining
+information of an SNMP engine that implements
+
+
+
+the SNMP Transport Security Model.""",
+        }, # group
+    }, # groups
+
+    "compliances" : {
+        "snmpTsmCompliance" : {
+            "nodetype" : "compliance",
+            "moduleName" : "SNMP-TSM-MIB",
+            "oid" : "1.3.6.1.2.1.190.2.1.1",
+            "status" : "current",
+            "description" :
+                """The compliance statement for SNMP engines that support
+the SNMP-TSM-MIB.""",
+            "requires" : {
+                "snmpTsmGroup" : {
+                    "nodetype" : "mandatory",
+                    "module" : "SNMP-TSM-MIB"
+                },
+            }, # requires
+        }, # compliance
+    }, # compliances
+
+}

data/lib/mibs/ietf/SNMP-USER-BASED-SM-MIB.dic

@@ -0,0 +1,1164 @@
+# python version 1.0						DO NOT EDIT
+#
+# This python file has been generated by smidump version 0.5.0:
+#
+#   smidump -f python SNMP-USER-BASED-SM-MIB
+
+FILENAME = "./libsmi-0.5.0/mibs/ietf/SNMP-USER-BASED-SM-MIB"
+
+MIB = {
+    "moduleName" : "SNMP-USER-BASED-SM-MIB",
+
+    "SNMP-USER-BASED-SM-MIB" : {
+        "nodetype" : "module",
+        "language" : "SMIv2",
+        "organization" :    
+            """SNMPv3 Working Group""",
+        "contact" : 
+            """WG-email:   snmpv3@lists.tislabs.com
+Subscribe:  majordomo@lists.tislabs.com
+            In msg body:  subscribe snmpv3
+
+Chair:      Russ Mundy
+            Network Associates Laboratories
+postal:     15204 Omega Drive, Suite 300
+            Rockville, MD 20850-4601
+            USA
+email:      mundy@tislabs.com
+
+
+
+phone:      +1 301-947-7107
+
+Co-Chair:   David Harrington
+            Enterasys Networks
+Postal:     35 Industrial Way
+            P. O. Box 5004
+            Rochester, New Hampshire 03866-5005
+            USA
+EMail:      dbh@enterasys.com
+Phone:      +1 603-337-2614
+
+Co-editor   Uri Blumenthal
+            Lucent Technologies
+postal:     67 Whippany Rd.
+            Whippany, NJ 07981
+            USA
+email:      uri@lucent.com
+phone:      +1-973-386-2163
+
+Co-editor:  Bert Wijnen
+            Lucent Technologies
+postal:     Schagen 33
+            3461 GL Linschoten
+            Netherlands
+email:      bwijnen@lucent.com
+phone:      +31-348-480-685""",
+        "description" :
+            """The management information definitions for the
+SNMP User-based Security Model.
+
+Copyright (C) The Internet Society (2002). This
+version of this MIB module is part of RFC 3414;
+see the RFC itself for full legal notices.""",
+        "revisions" : (
+            {
+                "date" : "2002-10-16 00:00",
+                "description" :
+                    """Changes in this revision:
+- Updated references and contact info.
+- Clarification to usmUserCloneFrom DESCRIPTION
+  clause
+- Fixed 'command responder' into 'command generator'
+  in last para of DESCRIPTION clause of
+  usmUserTable.
+This revision published as RFC3414.""",
+            },
+            {
+                "date" : "1999-01-20 00:00",
+                "description" :
+                    """Clarifications, published as RFC2574""",
+            },
+            {
+                "date" : "1997-11-20 00:00",
+                "description" :
+                    """Initial version, published as RFC2274""",
+            },
+        ),
+        "identity node" : "snmpUsmMIB",
+    },
+
+    "imports" : (
+        {"module" : "SNMPv2-SMI", "name" : "MODULE-IDENTITY"},
+        {"module" : "SNMPv2-SMI", "name" : "OBJECT-TYPE"},
+        {"module" : "SNMPv2-SMI", "name" : "OBJECT-IDENTITY"},
+        {"module" : "SNMPv2-SMI", "name" : "snmpModules"},
+        {"module" : "SNMPv2-SMI", "name" : "Counter32"},
+        {"module" : "SNMPv2-TC", "name" : "TEXTUAL-CONVENTION"},
+        {"module" : "SNMPv2-TC", "name" : "TestAndIncr"},
+        {"module" : "SNMPv2-TC", "name" : "RowStatus"},
+        {"module" : "SNMPv2-TC", "name" : "RowPointer"},
+        {"module" : "SNMPv2-TC", "name" : "StorageType"},
+        {"module" : "SNMPv2-TC", "name" : "AutonomousType"},
+        {"module" : "SNMPv2-CONF", "name" : "MODULE-COMPLIANCE"},
+        {"module" : "SNMPv2-CONF", "name" : "OBJECT-GROUP"},
+        {"module" : "SNMP-FRAMEWORK-MIB", "name" : "SnmpAdminString"},
+        {"module" : "SNMP-FRAMEWORK-MIB", "name" : "SnmpEngineID"},
+        {"module" : "SNMP-FRAMEWORK-MIB", "name" : "snmpAuthProtocols"},
+        {"module" : "SNMP-FRAMEWORK-MIB", "name" : "snmpPrivProtocols"},
+    ),
+
+    "typedefs" : {
+        "KeyChange" : {
+            "basetype" : "OctetString",
+            "status" : "current",
+            "description" :
+                """Every definition of an object with this syntax must identify
+a protocol P, a secret key K, and a hash algorithm H
+that produces output of L octets.
+
+The object's value is a manager-generated, partially-random
+value which, when modified, causes the value of the secret
+key K, to be modified via a one-way function.
+
+The value of an instance of this object is the concatenation
+of two components: first a 'random' component and then a
+'delta' component.
+
+The lengths of the random and delta components
+are given by the corresponding value of the protocol P;
+if P requires K to be a fixed length, the length of both the
+random and delta components is that fixed length; if P
+allows the length of K to be variable up to a particular
+maximum length, the length of the random component is that
+maximum length and the length of the delta component is any
+length less than or equal to that maximum length.
+For example, usmHMACMD5AuthProtocol requires K to be a fixed
+length of 16 octets and L - of 16 octets.
+usmHMACSHAAuthProtocol requires K to be a fixed length of
+20 octets and L - of 20 octets. Other protocols may define
+other sizes, as deemed appropriate.
+
+
+
+When a requester wants to change the old key K to a new
+key keyNew on a remote entity, the 'random' component is
+obtained from either a true random generator, or from a
+pseudorandom generator, and the 'delta' component is
+computed as follows:
+
+ - a temporary variable is initialized to the existing value
+   of K;
+ - if the length of the keyNew is greater than L octets,
+   then:
+    - the random component is appended to the value of the
+      temporary variable, and the result is input to the
+      the hash algorithm H to produce a digest value, and
+      the temporary variable is set to this digest value;
+    - the value of the temporary variable is XOR-ed with
+      the first (next) L-octets (16 octets in case of MD5)
+      of the keyNew to produce the first (next) L-octets
+      (16 octets in case of MD5) of the 'delta' component.
+    - the above two steps are repeated until the unused
+      portion of the keyNew component is L octets or less,
+ - the random component is appended to the value of the
+   temporary variable, and the result is input to the
+   hash algorithm H to produce a digest value;
+ - this digest value, truncated if necessary to be the same
+   length as the unused portion of the keyNew, is XOR-ed
+   with the unused portion of the keyNew to produce the
+   (final portion of the) 'delta' component.
+
+ For example, using MD5 as the hash algorithm H:
+
+    iterations = (lenOfDelta - 1)/16; /* integer division */
+    temp = keyOld;
+    for (i = 0; i < iterations; i++) {
+        temp = MD5 (temp || random);
+        delta[i*16 .. (i*16)+15] =
+               temp XOR keyNew[i*16 .. (i*16)+15];
+    }
+    temp = MD5 (temp || random);
+    delta[i*16 .. lenOfDelta-1] =
+           temp XOR keyNew[i*16 .. lenOfDelta-1];
+
+The 'random' and 'delta' components are then concatenated as
+described above, and the resulting octet string is sent to
+the recipient as the new value of an instance of this object.
+
+At the receiver side, when an instance of this object is set
+to a new value, then a new value of K is computed as follows:
+
+
+
+
+ - a temporary variable is initialized to the existing value
+   of K;
+ - if the length of the delta component is greater than L
+   octets, then:
+    - the random component is appended to the value of the
+      temporary variable, and the result is input to the
+      hash algorithm H to produce a digest value, and the
+      temporary variable is set to this digest value;
+    - the value of the temporary variable is XOR-ed with
+      the first (next) L-octets (16 octets in case of MD5)
+      of the delta component to produce the first (next)
+      L-octets (16 octets in case of MD5) of the new value
+      of K.
+    - the above two steps are repeated until the unused
+      portion of the delta component is L octets or less,
+ - the random component is appended to the value of the
+   temporary variable, and the result is input to the
+   hash algorithm H to produce a digest value;
+ - this digest value, truncated if necessary to be the same
+   length as the unused portion of the delta component, is
+   XOR-ed with the unused portion of the delta component to
+   produce the (final portion of the) new value of K.
+
+ For example, using MD5 as the hash algorithm H:
+
+    iterations = (lenOfDelta - 1)/16; /* integer division */
+    temp = keyOld;
+    for (i = 0; i < iterations; i++) {
+        temp = MD5 (temp || random);
+        keyNew[i*16 .. (i*16)+15] =
+               temp XOR delta[i*16 .. (i*16)+15];
+    }
+    temp = MD5 (temp || random);
+    keyNew[i*16 .. lenOfDelta-1] =
+           temp XOR delta[i*16 .. lenOfDelta-1];
+
+The value of an object with this syntax, whenever it is
+retrieved by the management protocol, is always the zero
+length string.
+
+Note that the keyOld and keyNew are the localized keys.
+
+Note that it is probably wise that when an SNMP entity sends
+a SetRequest to change a key, that it keeps a copy of the old
+key until it has confirmed that the key change actually
+succeeded.""",
+        },
+    }, # typedefs
+
+    "nodes" : {
+        "usmNoAuthProtocol" : {
+            "nodetype" : "node",
+            "moduleName" : "SNMP-USER-BASED-SM-MIB",
+            "oid" : "1.3.6.1.6.3.10.1.1.1",
+            "status" : "current",
+            "description" :
+                """No Authentication Protocol.""",
+        }, # node
+        "usmHMACMD5AuthProtocol" : {
+            "nodetype" : "node",
+            "moduleName" : "SNMP-USER-BASED-SM-MIB",
+            "oid" : "1.3.6.1.6.3.10.1.1.2",
+            "status" : "current",
+            "description" :
+                """The HMAC-MD5-96 Digest Authentication Protocol.""",
+            "reference" :
+                """- H. Krawczyk, M. Bellare, R. Canetti HMAC:
+Keyed-Hashing for Message Authentication,
+RFC2104, Feb 1997.
+- Rivest, R., Message Digest Algorithm MD5, RFC1321.""",
+        }, # node
+        "usmHMACSHAAuthProtocol" : {
+            "nodetype" : "node",
+            "moduleName" : "SNMP-USER-BASED-SM-MIB",
+            "oid" : "1.3.6.1.6.3.10.1.1.3",
+            "status" : "current",
+            "description" :
+                """The HMAC-SHA-96 Digest Authentication Protocol.""",
+            "reference" :
+                """- H. Krawczyk, M. Bellare, R. Canetti, HMAC:
+Keyed-Hashing for Message Authentication,
+RFC2104, Feb 1997.
+- Secure Hash Algorithm. NIST FIPS 180-1.""",
+        }, # node
+        "usmNoPrivProtocol" : {
+            "nodetype" : "node",
+            "moduleName" : "SNMP-USER-BASED-SM-MIB",
+            "oid" : "1.3.6.1.6.3.10.1.2.1",
+            "status" : "current",
+            "description" :
+                """No Privacy Protocol.""",
+        }, # node
+        "usmDESPrivProtocol" : {
+            "nodetype" : "node",
+            "moduleName" : "SNMP-USER-BASED-SM-MIB",
+            "oid" : "1.3.6.1.6.3.10.1.2.2",
+            "status" : "current",
+            "description" :
+                """The CBC-DES Symmetric Encryption Protocol.""",
+            "reference" :
+                """- Data Encryption Standard, National Institute of
+Standards and Technology.  Federal Information
+Processing Standard (FIPS) Publication 46-1.
+
+
+
+Supersedes FIPS Publication 46,
+(January, 1977; reaffirmed January, 1988).
+
+- Data Encryption Algorithm, American National
+Standards Institute.  ANSI X3.92-1981,
+(December, 1980).
+
+- DES Modes of Operation, National Institute of
+Standards and Technology.  Federal Information
+Processing Standard (FIPS) Publication 81,
+(December, 1980).
+
+- Data Encryption Algorithm - Modes of Operation,
+American National Standards Institute.
+ANSI X3.106-1983, (May 1983).""",
+        }, # node
+        "snmpUsmMIB" : {
+            "nodetype" : "node",
+            "moduleName" : "SNMP-USER-BASED-SM-MIB",
+            "oid" : "1.3.6.1.6.3.15",
+            "status" : "current",
+        }, # node
+        "usmMIBObjects" : {
+            "nodetype" : "node",
+            "moduleName" : "SNMP-USER-BASED-SM-MIB",
+            "oid" : "1.3.6.1.6.3.15.1",
+        }, # node
+        "usmStats" : {
+            "nodetype" : "node",
+            "moduleName" : "SNMP-USER-BASED-SM-MIB",
+            "oid" : "1.3.6.1.6.3.15.1.1",
+        }, # node
+        "usmStatsUnsupportedSecLevels" : {
+            "nodetype" : "scalar",
+            "moduleName" : "SNMP-USER-BASED-SM-MIB",
+            "oid" : "1.3.6.1.6.3.15.1.1.1",
+            "status" : "current",
+            "syntax" : {
+                "type" : { "module" :"SNMPv2-SMI", "name" : "Counter32"},
+            },
+            "access" : "readonly",
+            "description" :
+                """The total number of packets received by the SNMP
+engine which were dropped because they requested a
+securityLevel that was unknown to the SNMP engine
+or otherwise unavailable.""",
+        }, # scalar
+        "usmStatsNotInTimeWindows" : {
+            "nodetype" : "scalar",
+            "moduleName" : "SNMP-USER-BASED-SM-MIB",
+            "oid" : "1.3.6.1.6.3.15.1.1.2",
+            "status" : "current",
+            "syntax" : {
+                "type" : { "module" :"SNMPv2-SMI", "name" : "Counter32"},
+            },
+            "access" : "readonly",
+            "description" :
+                """The total number of packets received by the SNMP
+engine which were dropped because they appeared
+outside of the authoritative SNMP engine's window.""",
+        }, # scalar
+        "usmStatsUnknownUserNames" : {
+            "nodetype" : "scalar",
+            "moduleName" : "SNMP-USER-BASED-SM-MIB",
+            "oid" : "1.3.6.1.6.3.15.1.1.3",
+            "status" : "current",
+            "syntax" : {
+                "type" : { "module" :"SNMPv2-SMI", "name" : "Counter32"},
+            },
+            "access" : "readonly",
+            "description" :
+                """The total number of packets received by the SNMP
+engine which were dropped because they referenced a
+user that was not known to the SNMP engine.""",
+        }, # scalar
+        "usmStatsUnknownEngineIDs" : {
+            "nodetype" : "scalar",
+            "moduleName" : "SNMP-USER-BASED-SM-MIB",
+            "oid" : "1.3.6.1.6.3.15.1.1.4",
+            "status" : "current",
+            "syntax" : {
+                "type" : { "module" :"SNMPv2-SMI", "name" : "Counter32"},
+            },
+            "access" : "readonly",
+            "description" :
+                """The total number of packets received by the SNMP
+engine which were dropped because they referenced an
+snmpEngineID that was not known to the SNMP engine.""",
+        }, # scalar
+        "usmStatsWrongDigests" : {
+            "nodetype" : "scalar",
+            "moduleName" : "SNMP-USER-BASED-SM-MIB",
+            "oid" : "1.3.6.1.6.3.15.1.1.5",
+            "status" : "current",
+            "syntax" : {
+                "type" : { "module" :"SNMPv2-SMI", "name" : "Counter32"},
+            },
+            "access" : "readonly",
+            "description" :
+                """The total number of packets received by the SNMP
+engine which were dropped because they didn't
+contain the expected digest value.""",
+        }, # scalar
+        "usmStatsDecryptionErrors" : {
+            "nodetype" : "scalar",
+            "moduleName" : "SNMP-USER-BASED-SM-MIB",
+            "oid" : "1.3.6.1.6.3.15.1.1.6",
+            "status" : "current",
+            "syntax" : {
+                "type" : { "module" :"SNMPv2-SMI", "name" : "Counter32"},
+            },
+            "access" : "readonly",
+            "description" :
+                """The total number of packets received by the SNMP
+engine which were dropped because they could not be
+decrypted.""",
+        }, # scalar
+        "usmUser" : {
+            "nodetype" : "node",
+            "moduleName" : "SNMP-USER-BASED-SM-MIB",
+            "oid" : "1.3.6.1.6.3.15.1.2",
+        }, # node
+        "usmUserSpinLock" : {
+            "nodetype" : "scalar",
+            "moduleName" : "SNMP-USER-BASED-SM-MIB",
+            "oid" : "1.3.6.1.6.3.15.1.2.1",
+            "status" : "current",
+            "syntax" : {
+                "type" : { "module" :"SNMPv2-TC", "name" : "TestAndIncr"},
+            },
+            "access" : "readwrite",
+            "description" :
+                """An advisory lock used to allow several cooperating
+Command Generator Applications to coordinate their
+use of facilities to alter secrets in the
+usmUserTable.""",
+        }, # scalar
+        "usmUserTable" : {
+            "nodetype" : "table",
+            "moduleName" : "SNMP-USER-BASED-SM-MIB",
+            "oid" : "1.3.6.1.6.3.15.1.2.2",
+            "status" : "current",
+            "description" :
+                """The table of users configured in the SNMP engine's
+Local Configuration Datastore (LCD).
+
+To create a new user (i.e., to instantiate a new
+conceptual row in this table), it is recommended to
+follow this procedure:
+
+  1)  GET(usmUserSpinLock.0) and save in sValue.
+
+
+
+  2)  SET(usmUserSpinLock.0=sValue,
+          usmUserCloneFrom=templateUser,
+          usmUserStatus=createAndWait)
+      You should use a template user to clone from
+      which has the proper auth/priv protocol defined.
+
+If the new user is to use privacy:
+
+  3)  generate the keyChange value based on the secret
+      privKey of the clone-from user and the secret key
+      to be used for the new user. Let us call this
+      pkcValue.
+  4)  GET(usmUserSpinLock.0) and save in sValue.
+  5)  SET(usmUserSpinLock.0=sValue,
+          usmUserPrivKeyChange=pkcValue
+          usmUserPublic=randomValue1)
+  6)  GET(usmUserPulic) and check it has randomValue1.
+      If not, repeat steps 4-6.
+
+If the new user will never use privacy:
+
+  7)  SET(usmUserPrivProtocol=usmNoPrivProtocol)
+
+If the new user is to use authentication:
+
+  8)  generate the keyChange value based on the secret
+      authKey of the clone-from user and the secret key
+      to be used for the new user. Let us call this
+      akcValue.
+  9)  GET(usmUserSpinLock.0) and save in sValue.
+  10) SET(usmUserSpinLock.0=sValue,
+          usmUserAuthKeyChange=akcValue
+          usmUserPublic=randomValue2)
+  11) GET(usmUserPulic) and check it has randomValue2.
+      If not, repeat steps 9-11.
+
+If the new user will never use authentication:
+
+  12) SET(usmUserAuthProtocol=usmNoAuthProtocol)
+
+Finally, activate the new user:
+
+  13) SET(usmUserStatus=active)
+
+The new user should now be available and ready to be
+used for SNMPv3 communication. Note however that access
+to MIB data must be provided via configuration of the
+SNMP-VIEW-BASED-ACM-MIB.
+
+
+
+The use of usmUserSpinlock is to avoid conflicts with
+another SNMP command generator application which may
+also be acting on the usmUserTable.""",
+        }, # table
+        "usmUserEntry" : {
+            "nodetype" : "row",
+            "moduleName" : "SNMP-USER-BASED-SM-MIB",
+            "oid" : "1.3.6.1.6.3.15.1.2.2.1",
+            "create" : "true",
+            "status" : "current",
+            "linkage" : [
+                "usmUserEngineID",
+                "usmUserName",
+            ],
+            "description" :
+                """A user configured in the SNMP engine's Local
+Configuration Datastore (LCD) for the User-based
+Security Model.""",
+        }, # row
+        "usmUserEngineID" : {
+            "nodetype" : "column",
+            "moduleName" : "SNMP-USER-BASED-SM-MIB",
+            "oid" : "1.3.6.1.6.3.15.1.2.2.1.1",
+            "status" : "current",
+            "syntax" : {
+                "type" : { "module" :"SNMP-FRAMEWORK-MIB", "name" : "SnmpEngineID"},
+            },
+            "access" : "noaccess",
+            "description" :
+                """An SNMP engine's administratively-unique identifier.
+
+In a simple agent, this value is always that agent's
+own snmpEngineID value.
+
+The value can also take the value of the snmpEngineID
+of a remote SNMP engine with which this user can
+communicate.""",
+        }, # column
+        "usmUserName" : {
+            "nodetype" : "column",
+            "moduleName" : "SNMP-USER-BASED-SM-MIB",
+            "oid" : "1.3.6.1.6.3.15.1.2.2.1.2",
+            "status" : "current",
+            "syntax" : {
+                "type" :                 {
+                    "basetype" : "OctetString",
+                    "parent module" : {
+                        "name" : "SNMP-FRAMEWORK-MIB",
+                        "type" : "SnmpAdminString",
+                    },
+                    "ranges" : [
+                    {
+                        "min" : "1",
+                        "max" : "32"
+                    },
+                    ],
+                    "range" : {
+                        "min" : "1",
+                        "max" : "32"
+                    },
+                },
+            },
+            "access" : "noaccess",
+            "description" :
+                """A human readable string representing the name of
+the user.
+
+This is the (User-based Security) Model dependent
+security ID.""",
+        }, # column
+        "usmUserSecurityName" : {
+            "nodetype" : "column",
+            "moduleName" : "SNMP-USER-BASED-SM-MIB",
+            "oid" : "1.3.6.1.6.3.15.1.2.2.1.3",
+            "status" : "current",
+            "syntax" : {
+                "type" : { "module" :"SNMP-FRAMEWORK-MIB", "name" : "SnmpAdminString"},
+            },
+            "access" : "readonly",
+            "description" :
+                """A human readable string representing the user in
+Security Model independent format.
+
+The default transformation of the User-based Security
+Model dependent security ID to the securityName and
+vice versa is the identity function so that the
+securityName is the same as the userName.""",
+        }, # column
+        "usmUserCloneFrom" : {
+            "nodetype" : "column",
+            "moduleName" : "SNMP-USER-BASED-SM-MIB",
+            "oid" : "1.3.6.1.6.3.15.1.2.2.1.4",
+            "status" : "current",
+            "syntax" : {
+                "type" : { "module" :"SNMPv2-TC", "name" : "RowPointer"},
+            },
+            "access" : "readwrite",
+            "description" :
+                """A pointer to another conceptual row in this
+usmUserTable.  The user in this other conceptual
+row is called the clone-from user.
+
+When a new user is created (i.e., a new conceptual
+row is instantiated in this table), the privacy and
+authentication parameters of the new user must be
+cloned from its clone-from user. These parameters are:
+  - authentication protocol (usmUserAuthProtocol)
+  - privacy protocol (usmUserPrivProtocol)
+They will be copied regardless of what the current
+value is.
+
+Cloning also causes the initial values of the secret
+authentication key (authKey) and the secret encryption
+
+
+
+key (privKey) of the new user to be set to the same
+values as the corresponding secrets of the clone-from
+user to allow the KeyChange process to occur as
+required during user creation.
+
+The first time an instance of this object is set by
+a management operation (either at or after its
+instantiation), the cloning process is invoked.
+Subsequent writes are successful but invoke no
+action to be taken by the receiver.
+The cloning process fails with an 'inconsistentName'
+error if the conceptual row representing the
+clone-from user does not exist or is not in an active
+state when the cloning process is invoked.
+
+When this object is read, the ZeroDotZero OID
+is returned.""",
+        }, # column
+        "usmUserAuthProtocol" : {
+            "nodetype" : "column",
+            "moduleName" : "SNMP-USER-BASED-SM-MIB",
+            "oid" : "1.3.6.1.6.3.15.1.2.2.1.5",
+            "status" : "current",
+            "syntax" : {
+                "type" : { "module" :"SNMPv2-TC", "name" : "AutonomousType"},
+            },
+            "access" : "readwrite",
+            "default" : "1.3.6.1.6.3.10.1.1.1",
+            "description" :
+                """An indication of whether messages sent on behalf of
+this user to/from the SNMP engine identified by
+usmUserEngineID, can be authenticated, and if so,
+the type of authentication protocol which is used.
+
+An instance of this object is created concurrently
+with the creation of any other object instance for
+the same user (i.e., as part of the processing of
+the set operation which creates the first object
+instance in the same conceptual row).
+
+If an initial set operation (i.e. at row creation time)
+tries to set a value for an unknown or unsupported
+protocol, then a 'wrongValue' error must be returned.
+
+The value will be overwritten/set when a set operation
+is performed on the corresponding instance of
+usmUserCloneFrom.
+
+Once instantiated, the value of such an instance of
+this object can only be changed via a set operation to
+the value of the usmNoAuthProtocol.
+
+If a set operation tries to change the value of an
+
+
+
+existing instance of this object to any value other
+than usmNoAuthProtocol, then an 'inconsistentValue'
+error must be returned.
+
+If a set operation tries to set the value to the
+usmNoAuthProtocol while the usmUserPrivProtocol value
+in the same row is not equal to usmNoPrivProtocol,
+then an 'inconsistentValue' error must be returned.
+That means that an SNMP command generator application
+must first ensure that the usmUserPrivProtocol is set
+to the usmNoPrivProtocol value before it can set
+the usmUserAuthProtocol value to usmNoAuthProtocol.""",
+        }, # column
+        "usmUserAuthKeyChange" : {
+            "nodetype" : "column",
+            "moduleName" : "SNMP-USER-BASED-SM-MIB",
+            "oid" : "1.3.6.1.6.3.15.1.2.2.1.6",
+            "status" : "current",
+            "syntax" : {
+                "type" : { "module" :"SNMP-USER-BASED-SM-MIB", "name" : "KeyChange"},
+            },
+            "access" : "readwrite",
+            "default" : "",
+            "description" :
+                """An object, which when modified, causes the secret
+authentication key used for messages sent on behalf
+of this user to/from the SNMP engine identified by
+usmUserEngineID, to be modified via a one-way
+function.
+
+The associated protocol is the usmUserAuthProtocol.
+The associated secret key is the user's secret
+authentication key (authKey). The associated hash
+algorithm is the algorithm used by the user's
+usmUserAuthProtocol.
+
+When creating a new user, it is an 'inconsistentName'
+error for a set operation to refer to this object
+unless it is previously or concurrently initialized
+through a set operation on the corresponding instance
+of usmUserCloneFrom.
+
+When the value of the corresponding usmUserAuthProtocol
+is usmNoAuthProtocol, then a set is successful, but
+effectively is a no-op.
+
+When this object is read, the zero-length (empty)
+string is returned.
+
+The recommended way to do a key change is as follows:
+
+
+
+
+  1) GET(usmUserSpinLock.0) and save in sValue.
+  2) generate the keyChange value based on the old
+     (existing) secret key and the new secret key,
+     let us call this kcValue.
+
+If you do the key change on behalf of another user:
+
+  3) SET(usmUserSpinLock.0=sValue,
+         usmUserAuthKeyChange=kcValue
+         usmUserPublic=randomValue)
+
+If you do the key change for yourself:
+
+  4) SET(usmUserSpinLock.0=sValue,
+         usmUserOwnAuthKeyChange=kcValue
+         usmUserPublic=randomValue)
+
+If you get a response with error-status of noError,
+then the SET succeeded and the new key is active.
+If you do not get a response, then you can issue a
+GET(usmUserPublic) and check if the value is equal
+to the randomValue you did send in the SET. If so, then
+the key change succeeded and the new key is active
+(probably the response got lost). If not, then the SET
+request probably never reached the target and so you
+can start over with the procedure above.""",
+        }, # column
+        "usmUserOwnAuthKeyChange" : {
+            "nodetype" : "column",
+            "moduleName" : "SNMP-USER-BASED-SM-MIB",
+            "oid" : "1.3.6.1.6.3.15.1.2.2.1.7",
+            "status" : "current",
+            "syntax" : {
+                "type" : { "module" :"SNMP-USER-BASED-SM-MIB", "name" : "KeyChange"},
+            },
+            "access" : "readwrite",
+            "default" : "",
+            "description" :
+                """Behaves exactly as usmUserAuthKeyChange, with one
+notable difference: in order for the set operation
+to succeed, the usmUserName of the operation
+requester must match the usmUserName that
+indexes the row which is targeted by this
+operation.
+In addition, the USM security model must be
+used for this operation.
+
+The idea here is that access to this column can be
+public, since it will only allow a user to change
+his own secret authentication key (authKey).
+Note that this can only be done once the row is active.
+
+
+
+When a set is received and the usmUserName of the
+requester is not the same as the umsUserName that
+indexes the row which is targeted by this operation,
+then a 'noAccess' error must be returned.
+
+When a set is received and the security model in use
+is not USM, then a 'noAccess' error must be returned.""",
+        }, # column
+        "usmUserPrivProtocol" : {
+            "nodetype" : "column",
+            "moduleName" : "SNMP-USER-BASED-SM-MIB",
+            "oid" : "1.3.6.1.6.3.15.1.2.2.1.8",
+            "status" : "current",
+            "syntax" : {
+                "type" : { "module" :"SNMPv2-TC", "name" : "AutonomousType"},
+            },
+            "access" : "readwrite",
+            "default" : "1.3.6.1.6.3.10.1.2.1",
+            "description" :
+                """An indication of whether messages sent on behalf of
+this user to/from the SNMP engine identified by
+usmUserEngineID, can be protected from disclosure,
+and if so, the type of privacy protocol which is used.
+
+An instance of this object is created concurrently
+with the creation of any other object instance for
+the same user (i.e., as part of the processing of
+the set operation which creates the first object
+instance in the same conceptual row).
+
+If an initial set operation (i.e. at row creation time)
+tries to set a value for an unknown or unsupported
+protocol, then a 'wrongValue' error must be returned.
+
+The value will be overwritten/set when a set operation
+is performed on the corresponding instance of
+usmUserCloneFrom.
+
+Once instantiated, the value of such an instance of
+this object can only be changed via a set operation to
+the value of the usmNoPrivProtocol.
+
+If a set operation tries to change the value of an
+existing instance of this object to any value other
+than usmNoPrivProtocol, then an 'inconsistentValue'
+error must be returned.
+
+Note that if any privacy protocol is used, then you
+must also use an authentication protocol. In other
+words, if usmUserPrivProtocol is set to anything else
+than usmNoPrivProtocol, then the corresponding instance
+of usmUserAuthProtocol cannot have a value of
+
+
+
+usmNoAuthProtocol. If it does, then an
+'inconsistentValue' error must be returned.""",
+        }, # column
+        "usmUserPrivKeyChange" : {
+            "nodetype" : "column",
+            "moduleName" : "SNMP-USER-BASED-SM-MIB",
+            "oid" : "1.3.6.1.6.3.15.1.2.2.1.9",
+            "status" : "current",
+            "syntax" : {
+                "type" : { "module" :"SNMP-USER-BASED-SM-MIB", "name" : "KeyChange"},
+            },
+            "access" : "readwrite",
+            "default" : "",
+            "description" :
+                """An object, which when modified, causes the secret
+encryption key used for messages sent on behalf
+of this user to/from the SNMP engine identified by
+usmUserEngineID, to be modified via a one-way
+function.
+
+The associated protocol is the usmUserPrivProtocol.
+The associated secret key is the user's secret
+privacy key (privKey). The associated hash
+algorithm is the algorithm used by the user's
+usmUserAuthProtocol.
+
+When creating a new user, it is an 'inconsistentName'
+error for a set operation to refer to this object
+unless it is previously or concurrently initialized
+through a set operation on the corresponding instance
+of usmUserCloneFrom.
+
+When the value of the corresponding usmUserPrivProtocol
+is usmNoPrivProtocol, then a set is successful, but
+effectively is a no-op.
+
+When this object is read, the zero-length (empty)
+string is returned.
+See the description clause of usmUserAuthKeyChange for
+a recommended procedure to do a key change.""",
+        }, # column
+        "usmUserOwnPrivKeyChange" : {
+            "nodetype" : "column",
+            "moduleName" : "SNMP-USER-BASED-SM-MIB",
+            "oid" : "1.3.6.1.6.3.15.1.2.2.1.10",
+            "status" : "current",
+            "syntax" : {
+                "type" : { "module" :"SNMP-USER-BASED-SM-MIB", "name" : "KeyChange"},
+            },
+            "access" : "readwrite",
+            "default" : "",
+            "description" :
+                """Behaves exactly as usmUserPrivKeyChange, with one
+notable difference: in order for the Set operation
+to succeed, the usmUserName of the operation
+requester must match the usmUserName that indexes
+
+
+
+the row which is targeted by this operation.
+In addition, the USM security model must be
+used for this operation.
+
+The idea here is that access to this column can be
+public, since it will only allow a user to change
+his own secret privacy key (privKey).
+Note that this can only be done once the row is active.
+
+When a set is received and the usmUserName of the
+requester is not the same as the umsUserName that
+indexes the row which is targeted by this operation,
+then a 'noAccess' error must be returned.
+
+When a set is received and the security model in use
+is not USM, then a 'noAccess' error must be returned.""",
+        }, # column
+        "usmUserPublic" : {
+            "nodetype" : "column",
+            "moduleName" : "SNMP-USER-BASED-SM-MIB",
+            "oid" : "1.3.6.1.6.3.15.1.2.2.1.11",
+            "status" : "current",
+            "syntax" : {
+                "type" :                 {
+                    "basetype" : "OctetString",
+                    "ranges" : [
+                    {
+                        "min" : "0",
+                        "max" : "32"
+                    },
+                    ],
+                    "range" : {
+                        "min" : "0",
+                        "max" : "32"
+                    },
+                },
+            },
+            "access" : "readwrite",
+            "default" : "",
+            "description" :
+                """A publicly-readable value which can be written as part
+of the procedure for changing a user's secret
+authentication and/or privacy key, and later read to
+determine whether the change of the secret was
+effected.""",
+        }, # column
+        "usmUserStorageType" : {
+            "nodetype" : "column",
+            "moduleName" : "SNMP-USER-BASED-SM-MIB",
+            "oid" : "1.3.6.1.6.3.15.1.2.2.1.12",
+            "status" : "current",
+            "syntax" : {
+                "type" : { "module" :"SNMPv2-TC", "name" : "StorageType"},
+            },
+            "access" : "readwrite",
+            "default" : "nonVolatile",
+            "description" :
+                """The storage type for this conceptual row.
+
+Conceptual rows having the value 'permanent' must
+allow write-access at a minimum to:
+
+- usmUserAuthKeyChange, usmUserOwnAuthKeyChange
+  and usmUserPublic for a user who employs
+  authentication, and
+- usmUserPrivKeyChange, usmUserOwnPrivKeyChange
+  and usmUserPublic for a user who employs
+  privacy.
+
+
+
+Note that any user who employs authentication or
+privacy must allow its secret(s) to be updated and
+thus cannot be 'readOnly'.
+
+If an initial set operation tries to set the value to
+'readOnly' for a user who employs authentication or
+privacy, then an 'inconsistentValue' error must be
+returned.  Note that if the value has been previously
+set (implicit or explicit) to any value, then the rules
+as defined in the StorageType Textual Convention apply.
+
+It is an implementation issue to decide if a SET for
+a readOnly or permanent row is accepted at all. In some
+contexts this may make sense, in others it may not. If
+a SET for a readOnly or permanent row is not accepted
+at all, then a 'wrongValue' error must be returned.""",
+        }, # column
+        "usmUserStatus" : {
+            "nodetype" : "column",
+            "moduleName" : "SNMP-USER-BASED-SM-MIB",
+            "oid" : "1.3.6.1.6.3.15.1.2.2.1.13",
+            "status" : "current",
+            "syntax" : {
+                "type" : { "module" :"SNMPv2-TC", "name" : "RowStatus"},
+            },
+            "access" : "readwrite",
+            "description" :
+                """The status of this conceptual row.
+
+Until instances of all corresponding columns are
+appropriately configured, the value of the
+corresponding instance of the usmUserStatus column
+is 'notReady'.
+
+In particular, a newly created row for a user who
+employs authentication, cannot be made active until the
+corresponding usmUserCloneFrom and usmUserAuthKeyChange
+have been set.
+
+Further, a newly created row for a user who also
+employs privacy, cannot be made active until the
+usmUserPrivKeyChange has been set.
+
+The RowStatus TC [RFC2579] requires that this
+DESCRIPTION clause states under which circumstances
+other objects in this row can be modified:
+
+The value of this object has no effect on whether
+other objects in this conceptual row can be modified,
+except for usmUserOwnAuthKeyChange and
+usmUserOwnPrivKeyChange. For these 2 objects, the
+
+
+
+value of usmUserStatus MUST be active.""",
+        }, # column
+        "usmMIBConformance" : {
+            "nodetype" : "node",
+            "moduleName" : "SNMP-USER-BASED-SM-MIB",
+            "oid" : "1.3.6.1.6.3.15.2",
+        }, # node
+        "usmMIBCompliances" : {
+            "nodetype" : "node",
+            "moduleName" : "SNMP-USER-BASED-SM-MIB",
+            "oid" : "1.3.6.1.6.3.15.2.1",
+        }, # node
+        "usmMIBGroups" : {
+            "nodetype" : "node",
+            "moduleName" : "SNMP-USER-BASED-SM-MIB",
+            "oid" : "1.3.6.1.6.3.15.2.2",
+        }, # node
+    }, # nodes
+
+    "groups" : {
+        "usmMIBBasicGroup" : {
+            "nodetype" : "group",
+            "moduleName" : "SNMP-USER-BASED-SM-MIB",
+            "oid" : "1.3.6.1.6.3.15.2.2.1",
+            "status" : "current",
+            "members" : {
+                "usmStatsUnsupportedSecLevels" : {
+                    "nodetype" : "member",
+                    "module" : "SNMP-USER-BASED-SM-MIB"
+                },
+                "usmStatsNotInTimeWindows" : {
+                    "nodetype" : "member",
+                    "module" : "SNMP-USER-BASED-SM-MIB"
+                },
+                "usmStatsUnknownUserNames" : {
+                    "nodetype" : "member",
+                    "module" : "SNMP-USER-BASED-SM-MIB"
+                },
+                "usmStatsUnknownEngineIDs" : {
+                    "nodetype" : "member",
+                    "module" : "SNMP-USER-BASED-SM-MIB"
+                },
+                "usmStatsWrongDigests" : {
+                    "nodetype" : "member",
+                    "module" : "SNMP-USER-BASED-SM-MIB"
+                },
+                "usmStatsDecryptionErrors" : {
+                    "nodetype" : "member",
+                    "module" : "SNMP-USER-BASED-SM-MIB"
+                },
+                "usmUserSpinLock" : {
+                    "nodetype" : "member",
+                    "module" : "SNMP-USER-BASED-SM-MIB"
+                },
+                "usmUserSecurityName" : {
+                    "nodetype" : "member",
+                    "module" : "SNMP-USER-BASED-SM-MIB"
+                },
+                "usmUserCloneFrom" : {
+                    "nodetype" : "member",
+                    "module" : "SNMP-USER-BASED-SM-MIB"
+                },
+                "usmUserAuthProtocol" : {
+                    "nodetype" : "member",
+                    "module" : "SNMP-USER-BASED-SM-MIB"
+                },
+                "usmUserAuthKeyChange" : {
+                    "nodetype" : "member",
+                    "module" : "SNMP-USER-BASED-SM-MIB"
+                },
+                "usmUserOwnAuthKeyChange" : {
+                    "nodetype" : "member",
+                    "module" : "SNMP-USER-BASED-SM-MIB"
+                },
+                "usmUserPrivProtocol" : {
+                    "nodetype" : "member",
+                    "module" : "SNMP-USER-BASED-SM-MIB"
+                },
+                "usmUserPrivKeyChange" : {
+                    "nodetype" : "member",
+                    "module" : "SNMP-USER-BASED-SM-MIB"
+                },
+                "usmUserOwnPrivKeyChange" : {
+                    "nodetype" : "member",
+                    "module" : "SNMP-USER-BASED-SM-MIB"
+                },
+                "usmUserPublic" : {
+                    "nodetype" : "member",
+                    "module" : "SNMP-USER-BASED-SM-MIB"
+                },
+                "usmUserStorageType" : {
+                    "nodetype" : "member",
+                    "module" : "SNMP-USER-BASED-SM-MIB"
+                },
+                "usmUserStatus" : {
+                    "nodetype" : "member",
+                    "module" : "SNMP-USER-BASED-SM-MIB"
+                },
+            }, # members
+            "description" :
+                """A collection of objects providing for configuration
+of an SNMP engine which implements the SNMP
+User-based Security Model.""",
+        }, # group
+    }, # groups
+
+    "compliances" : {
+        "usmMIBCompliance" : {
+            "nodetype" : "compliance",
+            "moduleName" : "SNMP-USER-BASED-SM-MIB",
+            "oid" : "1.3.6.1.6.3.15.2.1.1",
+            "status" : "current",
+            "description" :
+                """The compliance statement for SNMP engines which
+implement the SNMP-USER-BASED-SM-MIB.""",
+            "requires" : {
+                "usmMIBBasicGroup" : {
+                    "nodetype" : "mandatory",
+                    "module" : "SNMP-USER-BASED-SM-MIB"
+                },
+            }, # requires
+            "refinements" : {
+                "usmUserAuthProtocol" : {
+                    "module" : "SNMP-USER-BASED-SM-MIB",
+                    "access" : "readonly",
+                    "description" :
+                        """Write access is not required.""",
+                },
+                "usmUserPrivProtocol" : {
+                    "module" : "SNMP-USER-BASED-SM-MIB",
+                    "access" : "readonly",
+                    "description" :
+                        """Write access is not required.""",
+                },
+            }, # refinements
+
+        }, # compliance
+    }, # compliances
+
+}