logstash-integration-snmp 4.0.0-java

data/lib/mibs/ietf/GMPLS-TC-STD-MIB.dic

@@ -0,0 +1,180 @@
+# python version 1.0						DO NOT EDIT
+#
+# This python file has been generated by smidump version 0.5.0:
+#
+#   smidump -f python GMPLS-TC-STD-MIB
+
+FILENAME = "./libsmi-0.5.0/mibs/ietf/GMPLS-TC-STD-MIB"
+
+MIB = {
+    "moduleName" : "GMPLS-TC-STD-MIB",
+
+    "GMPLS-TC-STD-MIB" : {
+        "nodetype" : "module",
+        "language" : "SMIv2",
+        "organization" :    
+            """IETF Common Control and Measurement Plane (CCAMP) Working Group""",
+        "contact" : 
+            """       Thomas D. Nadeau
+Cisco Systems, Inc.
+Email: tnadeau@cisco.com
+
+Adrian Farrel
+Old Dog Consulting
+Email: adrian@olddog.co.uk
+
+Comments about this document should be emailed directly to the
+CCAMP working group mailing list at ccamp@ops.ietf.org""",
+        "description" :
+            """Copyright (C) The IETF Trust (2007).  This version of
+this MIB module is part of RFC 4801; see the RFC itself for
+full legal notices.
+
+This MIB module defines TEXTUAL-CONVENTIONs for concepts used in
+Generalized Multiprotocol Label Switching (GMPLS) networks.""",
+        "revisions" : (
+            {
+                "date" : "2007-02-28 00:00",
+                "description" :
+                    """Initial version published as part of RFC 4801.""",
+            },
+        ),
+        "identity node" : "gmplsTCStdMIB",
+    },
+
+    "imports" : (
+        {"module" : "SNMPv2-SMI", "name" : "MODULE-IDENTITY"},
+        {"module" : "SNMPv2-TC", "name" : "TEXTUAL-CONVENTION"},
+        {"module" : "MPLS-TC-STD-MIB", "name" : "mplsStdMIB"},
+    ),
+
+    "typedefs" : {
+        "GmplsFreeformLabelTC" : {
+            "basetype" : "OctetString",
+            "status" : "current",
+            "ranges" : [
+            {
+                "min" : "0",
+                "max" : "64"
+            },
+            ],
+            "range" : {
+                "min" : "0",
+                "max" : "64"
+            },
+            "description" :
+                """This TEXTUAL-CONVENTION can be used as the syntax of an object
+that contains any GMPLS Label.  Objects with this syntax can be
+used to represent labels that have label types that are not
+defined in any RFCs.  The freeform GMPLS Label may also be used
+by systems that do not wish to represent labels that have
+label types defined in RFCs using type-specific syntaxes.""",
+            "reference" :
+                """1. Generalized Multi-Protocol Label Switching (GMPLS) Signaling
+Functional Description, RFC 3471, section 3.2.""",
+        },
+        "GmplsLabelTypeTC" : {
+            "basetype" : "Enumeration",
+            "status" : "current",
+            "gmplsMplsLabel" : {
+                "nodetype" : "namednumber",
+                "number" : "1"
+            },
+            "gmplsPortWavelengthLabel" : {
+                "nodetype" : "namednumber",
+                "number" : "2"
+            },
+            "gmplsFreeformGeneralizedLabel" : {
+                "nodetype" : "namednumber",
+                "number" : "3"
+            },
+            "gmplsSonetLabel" : {
+                "nodetype" : "namednumber",
+                "number" : "4"
+            },
+            "gmplsSdhLabel" : {
+                "nodetype" : "namednumber",
+                "number" : "5"
+            },
+            "gmplsWavebandLabel" : {
+                "nodetype" : "namednumber",
+                "number" : "6"
+            },
+            "description" :
+                """Determines the interpretation that should be applied to an
+object that encodes a label.  The possible types are:
+
+gmplsMplsLabel(1)           - The label is an MPLS Packet, Cell,
+                              or Frame Label and is encoded as
+                              described for the TEXTUAL-
+                              CONVENTION MplsLabel defined in
+                              RFC 3811.
+
+gmplsPortWavelengthLabel(2) - The label is a Port or Wavelength
+                              Label as defined in RFC 3471.
+
+gmplsFreeformLabel(3)       - The label is any form of label
+                              encoded as an OCTET STRING using
+                              the TEXTUAL-CONVENTION
+                              GmplsFreeformLabel.
+
+gmplsSonetLabel(4)          - The label is a Synchronous Optical
+                              Network (SONET) Label as
+                              defined in RFC 4606.
+
+gmplsSdhLabel(5)            - The label is a Synchronous Digital
+                              Hierarchy (SDH) Label as defined
+                              in RFC 4606.
+
+gmplsWavebandLabel(6)       - The label is a Waveband Label as
+                              defined in RFC 3471.""",
+            "reference" :
+                """1. Generalized Multi-Protocol Label Switching (GMPLS) Signaling
+Functional Description, RFC 3471, section 3.
+2. Definition of Textual Conventions and for Multiprotocol Label
+Switching (MPLS) Management, RFC 3811, section 3.
+3. Generalized Multi-Protocol Label Switching (GMPLS) Extensions
+for Synchronous Optical Network (SONET) and Synchronous
+
+
+
+Digital Hierarchy (SDH) Control, RFC 4606.""",
+        },
+        "GmplsSegmentDirectionTC" : {
+            "basetype" : "Enumeration",
+            "status" : "current",
+            "forward" : {
+                "nodetype" : "namednumber",
+                "number" : "1"
+            },
+            "reverse" : {
+                "nodetype" : "namednumber",
+                "number" : "2"
+            },
+            "description" :
+                """The direction of data flow on an Label Switched Path (LSP)
+segment with respect to the head of the LSP.
+
+Where an LSP is signaled using a conventional signaling
+protocol, the 'head' of the LSP is the source of the signaling
+(also known as the ingress) and the 'tail' is the destination
+(also known as the egress).  For unidirectional LSPs, this
+usually matches the direction of flow of data.
+
+For manually configured unidirectional LSPs, the direction of
+the LSP segment matches the direction of flow of data.  For
+manually configured bidirectional LSPs, an arbitrary decision
+must be made about which LER is the 'head'.""",
+        },
+    }, # typedefs
+
+    "nodes" : {
+        "gmplsTCStdMIB" : {
+            "nodetype" : "node",
+            "moduleName" : "GMPLS-TC-STD-MIB",
+            "oid" : "1.3.6.1.2.1.10.166.12",
+            "status" : "current",
+        }, # node
+    }, # nodes
+
+}