logstash-integration-snmp 4.0.0-java

data/lib/mibs/ietf/URI-TC-MIB.dic

@@ -0,0 +1,193 @@
+# python version 1.0						DO NOT EDIT
+#
+# This python file has been generated by smidump version 0.5.0:
+#
+#   smidump -f python URI-TC-MIB
+
+FILENAME = "./libsmi-0.5.0/mibs/ietf/URI-TC-MIB"
+
+MIB = {
+    "moduleName" : "URI-TC-MIB",
+
+    "URI-TC-MIB" : {
+        "nodetype" : "module",
+        "language" : "SMIv2",
+        "organization" :    
+            """IETF Operations and Management (OPS) Area""",
+        "contact" : 
+            """EMail: ops-area@ietf.org
+Home page: http://www.ops.ietf.org/""",
+        "description" :
+            """This MIB module defines textual conventions for
+representing URIs, as defined by RFC 3986 STD 66.""",
+        "revisions" : (
+            {
+                "date" : "2007-09-10 00:00",
+                "description" :
+                    """Initial revision, published as RFC 5017.
+
+Copyright (C) The IETF Trust (2007).  This version of this
+MIB module is part of RFC 5017; see the RFC itself for full
+
+
+
+legal notices.""",
+            },
+        ),
+        "identity node" : "uriTcMIB",
+    },
+
+    "imports" : (
+        {"module" : "SNMPv2-SMI", "name" : "MODULE-IDENTITY"},
+        {"module" : "SNMPv2-SMI", "name" : "mib-2"},
+        {"module" : "SNMPv2-TC", "name" : "TEXTUAL-CONVENTION"},
+    ),
+
+    "typedefs" : {
+        "Uri" : {
+            "basetype" : "OctetString",
+            "status" : "current",
+            "format" : "1a",
+            "description" :
+                """A Uniform Resource Identifier (URI) as defined by STD 66.
+
+Objects using this TEXTUAL-CONVENTION MUST be in US-ASCII
+encoding, and MUST be normalized as described by RFC 3986
+Sections 6.2.1, 6.2.2.1, and 6.2.2.2.  All unnecessary
+percent-encoding is removed, and all case-insensitive
+characters are set to lowercase except for hexadecimal
+digits, which are normalized to uppercase as described in
+Section 6.2.2.1.
+
+The purpose of this normalization is to help provide unique
+URIs.  Note that this normalization is not sufficient to
+provide uniqueness.  Two URIs that are textually distinct
+after this normalization may still be equivalent.
+
+Objects using this TEXTUAL-CONVENTION MAY restrict the
+schemes that they permit.  For example, 'data:' and 'urn:'
+schemes might not be appropriate.
+
+A zero-length URI is not a valid URI.  This can be used to
+express 'URI absent' where required, for example when used
+as an index field.
+
+Where this TEXTUAL-CONVENTION is used for an index field,
+it MUST be subtyped to restrict its length.  There is an
+absolute limit of 128 subids for an OID, and it is not
+efficient to have OIDs whose length approaches this
+limit.""",
+            "reference" :
+                """RFC 3986 STD 66 and RFC 3305""",
+        },
+        "Uri255" : {
+            "basetype" : "OctetString",
+            "status" : "current",
+            "ranges" : [
+            {
+                "min" : "0",
+                "max" : "255"
+            },
+            ],
+            "range" : {
+                "min" : "0",
+                "max" : "255"
+            },
+            "format" : "255a",
+            "description" :
+                """A Uniform Resource Identifier (URI) as defined by STD 66.
+
+Objects using this TEXTUAL-CONVENTION MUST be in US-ASCII
+encoding, and MUST be normalized as described by RFC 3986
+Sections 6.2.1, 6.2.2.1, and 6.2.2.2.  All unnecessary
+percent-encoding is removed, and all case-insensitive
+
+
+
+characters are set to lowercase except for hexadecimal
+digits, which are normalized to uppercase as described in
+Section 6.2.2.1.
+
+The purpose of this normalization is to help provide unique
+URIs.  Note that this normalization is not sufficient to
+provide uniqueness.  Two URIs that are textually distinct
+after this normalization may still be equivalent.
+
+Objects using this TEXTUAL-CONVENTION MAY restrict the
+schemes that they permit.  For example, 'data:' and 'urn:'
+schemes might not be appropriate.
+
+A zero-length URI is not a valid URI.  This can be used to
+express 'URI absent' where required, for example when used
+as an index field.
+
+STD 66 URIs are of unlimited length.  Objects using this
+TEXTUAL-CONVENTION impose a length limit on the URIs that
+they can represent.  Where no length restriction is
+required, objects SHOULD use the 'Uri' TEXTUAL-CONVENTION
+instead.  Objects used as indices SHOULD subtype the 'Uri'
+TEXTUAL-CONVENTION.""",
+            "reference" :
+                """RFC 3986 STD 66 and RFC 3305""",
+        },
+        "Uri1024" : {
+            "basetype" : "OctetString",
+            "status" : "current",
+            "ranges" : [
+            {
+                "min" : "0",
+                "max" : "1024"
+            },
+            ],
+            "range" : {
+                "min" : "0",
+                "max" : "1024"
+            },
+            "format" : "1024a",
+            "description" :
+                """A Uniform Resource Identifier (URI) as defined by STD 66.
+
+Objects using this TEXTUAL-CONVENTION MUST be in US-ASCII
+encoding, and MUST be normalized as described by RFC 3986
+Sections 6.2.1, 6.2.2.1, and 6.2.2.2.  All unnecessary
+percent-encoding is removed, and all case-insensitive
+characters are set to lowercase except for hexadecimal
+digits, which are normalized to uppercase as described in
+Section 6.2.2.1.
+
+The purpose of this normalization is to help provide unique
+URIs.  Note that this normalization is not sufficient to
+provide uniqueness.  Two URIs that are textually distinct
+after this normalization may still be equivalent.
+
+Objects using this TEXTUAL-CONVENTION MAY restrict the
+schemes that they permit.  For example, 'data:' and 'urn:'
+schemes might not be appropriate.
+
+
+
+A zero-length URI is not a valid URI.  This can be used to
+express 'URI absent' where required, for example when used
+as an index field.
+
+STD 66 URIs are of unlimited length.  Objects using this
+TEXTUAL-CONVENTION impose a length limit on the URIs that
+they can represent.  Where no length restriction is
+required, objects SHOULD use the 'Uri' TEXTUAL-CONVENTION
+instead.  Objects used as indices SHOULD subtype the 'Uri'
+TEXTUAL-CONVENTION.""",
+            "reference" :
+                """RFC 3986 STD 66 and RFC 3305""",
+        },
+    }, # typedefs
+
+    "nodes" : {
+        "uriTcMIB" : {
+            "nodetype" : "node",
+            "moduleName" : "URI-TC-MIB",
+            "oid" : "1.3.6.1.2.1.164",
+            "status" : "current",
+        }, # node
+    }, # nodes
+
+}

data/lib/mibs/ietf/UUID-TC-MIB.dic

@@ -0,0 +1,135 @@
+# python version 1.0						DO NOT EDIT
+#
+# This python file has been generated by smidump version 0.5.0:
+#
+#   smidump -f python UUID-TC-MIB
+
+FILENAME = "./libsmi-0.5.0/mibs/ietf/UUID-TC-MIB"
+
+MIB = {
+    "moduleName" : "UUID-TC-MIB",
+
+    "UUID-TC-MIB" : {
+        "nodetype" : "module",
+        "language" : "SMIv2",
+        "organization" :    
+            """IETF Energy Management Working Group""",
+        "contact" : 
+            """WG Email: eman@ietf.org
+Mailing list subscription info:
+http://www.ietf.org/mailman/listinfo/eman
+
+Dan Romascanu
+Avaya
+Park Atidim, Bldg. #3
+Tel Aviv, 61581
+Israel
+Phone: +972-3-6458414
+Email: dromasca@avaya.com
+
+Juergen Quittek
+NEC Europe Ltd.
+Network Research Division
+Kurfuersten-Anlage 36
+Heidelberg  69115
+Germany
+Phone: +49 6221 4342-115
+Email: quittek@neclab.eu
+
+Mouli Chandramouli
+Cisco Systems, Inc.
+Sarjapur Outer Ring Road
+Bangalore 560103
+India
+Phone: +91 80 4429 2409
+Email: moulchan@cisco.com""",
+        "description" :
+            """This MIB module defines TEXTUAL-CONVENTIONs
+representing Universally Unique IDentifiers
+(UUIDs).
+
+Copyright (c) 2013 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, is permitted
+pursuant to, and subject to the license terms
+contained in, the Simplified BSD License set forth
+in Section 4.c of the IETF Trust's Legal
+Provisions Relating to IETF Documents
+(http://trustee.ietf.org/license-info).""",
+        "revisions" : (
+            {
+                "date" : "2013-04-05 00:00",
+                "description" :
+                    """Initial version of this MIB as published in
+RFC 6933.""",
+            },
+        ),
+        "identity node" : "uuidTCMIB",
+    },
+
+    "imports" : (
+        {"module" : "SNMPv2-SMI", "name" : "MODULE-IDENTITY"},
+        {"module" : "SNMPv2-SMI", "name" : "mib-2"},
+        {"module" : "SNMPv2-TC", "name" : "TEXTUAL-CONVENTION"},
+    ),
+
+    "typedefs" : {
+        "UUID" : {
+            "basetype" : "OctetString",
+            "status" : "current",
+            "ranges" : [
+            {
+                "min" : "16",
+                "max" : "16"
+            },
+            ],
+            "range" : {
+                "min" : "16",
+                "max" : "16"
+            },
+            "format" : "4x-2x-2x-1x1x-6x",
+            "description" :
+                """Universally Unique Identifier information.  The syntax must
+conform to RFC 4122, Section 4.1.""",
+        },
+        "UUIDorZero" : {
+            "basetype" : "OctetString",
+            "status" : "current",
+            "ranges" : [
+            {
+                "min" : "0",
+                "max" : "0"
+            },
+            {
+                "min" : "16",
+                "max" : "16"
+            },
+            ],
+            "range" : {
+                "min" : "0",
+                "max" : "16"
+            },
+            "format" : "4x-2x-2x-1x1x-6x",
+            "description" :
+                """Universally Unique Identifier information.  The syntax must
+conform to RFC 4122, Section 4.1.
+
+The semantics of the value zero-length OCTET STRING are
+object-specific and must therefore be defined as part of
+the description of any object that uses this syntax.""",
+        },
+    }, # typedefs
+
+    "nodes" : {
+        "uuidTCMIB" : {
+            "nodetype" : "node",
+            "moduleName" : "UUID-TC-MIB",
+            "oid" : "1.3.6.1.2.1.217",
+            "status" : "current",
+        }, # node
+    }, # nodes
+
+}