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

data/lib/mibs/ietf/TOKENRING-STATION-SR-MIB.dic

@@ -0,0 +1,292 @@
+# python version 1.0						DO NOT EDIT
+#
+# This python file has been generated by smidump version 0.5.0:
+#
+#   smidump -f python TOKENRING-STATION-SR-MIB
+
+FILENAME = "./libsmi-0.5.0/mibs/ietf/TOKENRING-STATION-SR-MIB"
+
+MIB = {
+    "moduleName" : "TOKENRING-STATION-SR-MIB",
+
+    "TOKENRING-STATION-SR-MIB" : {
+        "nodetype" : "module",
+        "language" : "SMIv2",
+        "organization" :    
+            """IETF Interfaces MIB Working Group""",
+        "contact" : 
+            """       Keith McCloghrie
+Postal: Cisco Systems, Inc.
+        170 West Tasman Drive
+        San Jose, CA  95134-1706
+        US
+
+ Phone: +1 408 526 5260
+ Email: kzm@cisco.com""",
+        "description" :
+            """The MIB module for managing source routes in
+end-stations on IEEE 802.5 Token Ring networks.""",
+        "revisions" : (
+            {
+                "date" : "1994-12-16 10:00",
+                "description" :
+                    """[Revision added by libsmi due to a LAST-UPDATED clause.]""",
+            },
+        ),
+        "identity node" : "dot5SrMIB",
+    },
+
+    "imports" : (
+        {"module" : "SNMPv2-SMI", "name" : "MODULE-IDENTITY"},
+        {"module" : "SNMPv2-SMI", "name" : "OBJECT-TYPE"},
+        {"module" : "SNMPv2-TC", "name" : "TEXTUAL-CONVENTION"},
+        {"module" : "SNMPv2-TC", "name" : "RowStatus"},
+        {"module" : "SNMPv2-TC", "name" : "MacAddress"},
+        {"module" : "SNMPv2-CONF", "name" : "MODULE-COMPLIANCE"},
+        {"module" : "SNMPv2-CONF", "name" : "OBJECT-GROUP"},
+        {"module" : "RFC1213-MIB", "name" : "mib-2"},
+        {"module" : "RFC1213-MIB", "name" : "ifIndex"},
+    ),
+
+    "typedefs" : {
+        "SourceRoute" : {
+            "basetype" : "OctetString",
+            "status" : "current",
+            "ranges" : [
+            {
+                "min" : "0",
+                "max" : "30"
+            },
+            ],
+            "range" : {
+                "min" : "0",
+                "max" : "30"
+            },
+            "format" : "1x:",
+            "description" :
+                """Represents a Source Route, containing an
+embedded sequence of bridge and ring ID's,
+as used by 802.5 Source Routing.""",
+            "reference" :
+                """Annex C of ISO/IEC 10038: 1993,
+[ANSI/IEEE Std 802.1D, 1993]""",
+        },
+    }, # typedefs
+
+    "nodes" : {
+        "dot5SrMIB" : {
+            "nodetype" : "node",
+            "moduleName" : "TOKENRING-STATION-SR-MIB",
+            "oid" : "1.3.6.1.2.1.42",
+            "status" : "current",
+        }, # node
+        "dot5SrMIBObjects" : {
+            "nodetype" : "node",
+            "moduleName" : "TOKENRING-STATION-SR-MIB",
+            "oid" : "1.3.6.1.2.1.42.1",
+        }, # node
+        "dot5SrRouteTable" : {
+            "nodetype" : "table",
+            "moduleName" : "TOKENRING-STATION-SR-MIB",
+            "oid" : "1.3.6.1.2.1.42.1.1",
+            "status" : "current",
+            "description" :
+                """The table of source-routing routes.
+This represents the 802.5 RIF database.""",
+        }, # table
+        "dot5SrRouteEntry" : {
+            "nodetype" : "row",
+            "moduleName" : "TOKENRING-STATION-SR-MIB",
+            "oid" : "1.3.6.1.2.1.42.1.1.1",
+            "create" : "true",
+            "status" : "current",
+            "linkage" : [
+                "ifIndex",
+                "dot5SrRouteDestination",
+            ],
+            "description" :
+                """Information on a specific route.
+
+An entry is created whenever a 'Single Path
+Explorer' or an 'All Paths Explorer' discovers
+a route to a neighbor not currently in the table,
+or whenever an 'All Paths Explorer' discovers a
+better (e.g., shorter) route than the route currently
+stored in the table.  This is done on behalf of
+any network layer client.
+
+The ifIndex value in the INDEX clause refers to
+the value of MIB-II's ifIndex object for the
+interface on which the route is in effect.""",
+        }, # row
+        "dot5SrRouteDestination" : {
+            "nodetype" : "column",
+            "moduleName" : "TOKENRING-STATION-SR-MIB",
+            "oid" : "1.3.6.1.2.1.42.1.1.1.2",
+            "status" : "current",
+            "syntax" : {
+                "type" : { "module" :"SNMPv2-TC", "name" : "MacAddress"},
+            },
+            "access" : "noaccess",
+            "description" :
+                """The destination of this route.""",
+        }, # column
+        "dot5SrRouteControl" : {
+            "nodetype" : "column",
+            "moduleName" : "TOKENRING-STATION-SR-MIB",
+            "oid" : "1.3.6.1.2.1.42.1.1.1.3",
+            "status" : "current",
+            "syntax" : {
+                "type" :                 {
+                    "basetype" : "OctetString",
+                    "ranges" : [
+                    {
+                        "min" : "2",
+                        "max" : "2"
+                    },
+                    ],
+                    "range" : {
+                        "min" : "2",
+                        "max" : "2"
+                    },
+                },
+            },
+            "access" : "readwrite",
+            "description" :
+                """The value of Routing Control field for this
+route.""",
+            "reference" :
+                """Annex C of ISO/IEC 10038: 1993,
+[ANSI/IEEE Std 802.1D, 1993]""",
+        }, # column
+        "dot5SrRouteDescr" : {
+            "nodetype" : "column",
+            "moduleName" : "TOKENRING-STATION-SR-MIB",
+            "oid" : "1.3.6.1.2.1.42.1.1.1.4",
+            "status" : "current",
+            "syntax" : {
+                "type" : { "module" :"TOKENRING-STATION-SR-MIB", "name" : "SourceRoute"},
+            },
+            "access" : "readwrite",
+            "description" :
+                """The embedded sequence of bridge and ring ID's
+for this route.  For destinations on the
+local ring, the value of this object is
+the zero-length string.""",
+            "reference" :
+                """Annex C of ISO/IEC 10038: 1993,
+[ANSI/IEEE Std 802.1D, 1993]""",
+        }, # column
+        "dot5SrRouteStatus" : {
+            "nodetype" : "column",
+            "moduleName" : "TOKENRING-STATION-SR-MIB",
+            "oid" : "1.3.6.1.2.1.42.1.1.1.5",
+            "status" : "current",
+            "syntax" : {
+                "type" : { "module" :"SNMPv2-TC", "name" : "RowStatus"},
+            },
+            "access" : "readwrite",
+            "description" :
+                """The status of this row.  Values of the instances
+of dot5SrRouteControl and dot5SrRouteDescr can be
+modified while the row's status is 'active.""",
+        }, # column
+        "dot5SrConformance" : {
+            "nodetype" : "node",
+            "moduleName" : "TOKENRING-STATION-SR-MIB",
+            "oid" : "1.3.6.1.2.1.42.2",
+        }, # node
+        "dot5SrGroups" : {
+            "nodetype" : "node",
+            "moduleName" : "TOKENRING-STATION-SR-MIB",
+            "oid" : "1.3.6.1.2.1.42.2.1",
+        }, # node
+        "dot5SrCompliances" : {
+            "nodetype" : "node",
+            "moduleName" : "TOKENRING-STATION-SR-MIB",
+            "oid" : "1.3.6.1.2.1.42.2.2",
+        }, # node
+    }, # nodes
+
+    "groups" : {
+        "dot5SrRouteGroup" : {
+            "nodetype" : "group",
+            "moduleName" : "TOKENRING-STATION-SR-MIB",
+            "oid" : "1.3.6.1.2.1.42.2.1.1",
+            "status" : "current",
+            "members" : {
+                "dot5SrRouteControl" : {
+                    "nodetype" : "member",
+                    "module" : "TOKENRING-STATION-SR-MIB"
+                },
+                "dot5SrRouteDescr" : {
+                    "nodetype" : "member",
+                    "module" : "TOKENRING-STATION-SR-MIB"
+                },
+                "dot5SrRouteStatus" : {
+                    "nodetype" : "member",
+                    "module" : "TOKENRING-STATION-SR-MIB"
+                },
+            }, # members
+            "description" :
+                """A collection of objects providing for the management of
+source routes in stations on IEEE 802.5 source-routing
+networks.""",
+        }, # group
+    }, # groups
+
+    "compliances" : {
+        "dot5SrCompliance" : {
+            "nodetype" : "compliance",
+            "moduleName" : "TOKENRING-STATION-SR-MIB",
+            "oid" : "1.3.6.1.2.1.42.2.2.1",
+            "status" : "current",
+            "description" :
+                """The compliance statement for SNMPv2 entities
+which implement the IEEE 802.5 Station Source Route
+MIB.""",
+            "requires" : {
+                "dot5SrRouteGroup" : {
+                    "nodetype" : "mandatory",
+                    "module" : "TOKENRING-STATION-SR-MIB"
+                },
+            }, # requires
+            "refinements" : {
+                "dot5SrRouteStatus" : {
+                    "module" : "TOKENRING-STATION-SR-MIB",
+                    "syntax" : {
+                        "type" :                         {
+                            "basetype" : "Enumeration",
+                            "parent module" : {
+                                "name" : "SNMPv2-TC",
+                                "type" : "RowStatus",
+                            },
+                            "active" : {
+                                "nodetype" : "namednumber",
+                                "number" : "1"
+                            },
+                        },
+                    }, # syntax
+                    "access" : "readonly",
+                    "description" :
+                        """Write access is not required, and only the 'active'
+value need be supported.""",
+                },
+                "dot5SrRouteControl" : {
+                    "module" : "TOKENRING-STATION-SR-MIB",
+                    "access" : "readonly",
+                    "description" :
+                        """Write access is not required.""",
+                },
+                "dot5SrRouteDescr" : {
+                    "module" : "TOKENRING-STATION-SR-MIB",
+                    "access" : "readonly",
+                    "description" :
+                        """Write access is not required.""",
+                },
+            }, # refinements
+
+        }, # compliance
+    }, # compliances
+
+}

data/lib/mibs/ietf/TRANSPORT-ADDRESS-MIB.dic

@@ -0,0 +1,610 @@
+# python version 1.0						DO NOT EDIT
+#
+# This python file has been generated by smidump version 0.5.0:
+#
+#   smidump -f python TRANSPORT-ADDRESS-MIB
+
+FILENAME = "./libsmi-0.5.0/mibs/ietf/TRANSPORT-ADDRESS-MIB"
+
+MIB = {
+    "moduleName" : "TRANSPORT-ADDRESS-MIB",
+
+    "TRANSPORT-ADDRESS-MIB" : {
+        "nodetype" : "module",
+        "language" : "SMIv2",
+        "organization" :    
+            """IETF Operations and Management Area""",
+        "contact" : 
+            """Juergen Schoenwaelder (Editor)
+TU Braunschweig
+Bueltenweg 74/75
+38106 Braunschweig, Germany
+
+
+
+Phone: +49 531 391-3289
+EMail: schoenw@ibr.cs.tu-bs.de
+
+Send comments to <mibs@ops.ietf.org>.""",
+        "description" :
+            """This MIB module provides commonly used transport
+address definitions.
+
+Copyright (C) The Internet Society (2002). This version of
+this MIB module is part of RFC 3419; see the RFC itself for
+full legal notices.""",
+        "revisions" : (
+            {
+                "date" : "2002-11-01 00:00",
+                "description" :
+                    """Initial version, published as RFC 3419.""",
+            },
+        ),
+        "identity node" : "transportAddressMIB",
+    },
+
+    "imports" : (
+        {"module" : "SNMPv2-SMI", "name" : "MODULE-IDENTITY"},
+        {"module" : "SNMPv2-SMI", "name" : "OBJECT-IDENTITY"},
+        {"module" : "SNMPv2-SMI", "name" : "mib-2"},
+        {"module" : "SNMPv2-TC", "name" : "TEXTUAL-CONVENTION"},
+    ),
+
+    "typedefs" : {
+        "TransportDomain" : {
+            "basetype" : "ObjectIdentifier",
+            "status" : "current",
+            "description" :
+                """A value that represents a transport domain.
+
+Some possible values, such as transportDomainUdpIpv4, are
+defined in this module.  Other possible values can be
+defined in other MIB modules.""",
+        },
+        "TransportAddressType" : {
+            "basetype" : "Enumeration",
+            "status" : "current",
+            "unknown" : {
+                "nodetype" : "namednumber",
+                "number" : "0"
+            },
+            "udpIpv4" : {
+                "nodetype" : "namednumber",
+                "number" : "1"
+            },
+            "udpIpv6" : {
+                "nodetype" : "namednumber",
+                "number" : "2"
+            },
+            "udpIpv4z" : {
+                "nodetype" : "namednumber",
+                "number" : "3"
+            },
+            "udpIpv6z" : {
+                "nodetype" : "namednumber",
+                "number" : "4"
+            },
+            "tcpIpv4" : {
+                "nodetype" : "namednumber",
+                "number" : "5"
+            },
+            "tcpIpv6" : {
+                "nodetype" : "namednumber",
+                "number" : "6"
+            },
+            "tcpIpv4z" : {
+                "nodetype" : "namednumber",
+                "number" : "7"
+            },
+            "tcpIpv6z" : {
+                "nodetype" : "namednumber",
+                "number" : "8"
+            },
+            "sctpIpv4" : {
+                "nodetype" : "namednumber",
+                "number" : "9"
+            },
+            "sctpIpv6" : {
+                "nodetype" : "namednumber",
+                "number" : "10"
+            },
+            "sctpIpv4z" : {
+                "nodetype" : "namednumber",
+                "number" : "11"
+            },
+            "sctpIpv6z" : {
+                "nodetype" : "namednumber",
+                "number" : "12"
+            },
+            "local" : {
+                "nodetype" : "namednumber",
+                "number" : "13"
+            },
+            "udpDns" : {
+                "nodetype" : "namednumber",
+                "number" : "14"
+            },
+            "tcpDns" : {
+                "nodetype" : "namednumber",
+                "number" : "15"
+            },
+            "sctpDns" : {
+                "nodetype" : "namednumber",
+                "number" : "16"
+            },
+            "description" :
+                """A value that represents a transport domain. This is the
+enumerated version of the transport domain registrations
+in this MIB module. The enumerated values have the
+following meaning:
+
+unknown(0)     unknown transport address type
+udpIpv4(1)     transportDomainUdpIpv4
+udpIpv6(2)     transportDomainUdpIpv6
+udpIpv4z(3)    transportDomainUdpIpv4z
+udpIpv6z(4)    transportDomainUdpIpv6z
+tcpIpv4(5)     transportDomainTcpIpv4
+tcpIpv6(6)     transportDomainTcpIpv6
+tcpIpv4z(7)    transportDomainTcpIpv4z
+
+
+
+tcpIpv6z(8)    transportDomainTcpIpv6z
+sctpIpv4(9)    transportDomainSctpIpv4
+sctpIpv6(10)   transportDomainSctpIpv6
+sctpIpv4z(11)  transportDomainSctpIpv4z
+sctpIpv6z(12)  transportDomainSctpIpv6z
+local(13)      transportDomainLocal
+udpDns(14)     transportDomainUdpDns
+tcpDns(15)     transportDomainTcpDns
+sctpDns(16)    transportDomainSctpDns
+
+This textual convention can be used to represent transport
+domains in situations where a syntax of TransportDomain is
+unwieldy (for example, when used as an index).
+
+The usage of this textual convention implies that additional
+transport domains can only be supported by updating this MIB
+module. This extensibility restriction does not apply for the
+TransportDomain textual convention which allows MIB authors
+to define additional transport domains independently in
+other MIB modules.""",
+        },
+        "TransportAddress" : {
+            "basetype" : "OctetString",
+            "status" : "current",
+            "ranges" : [
+            {
+                "min" : "0",
+                "max" : "255"
+            },
+            ],
+            "range" : {
+                "min" : "0",
+                "max" : "255"
+            },
+            "description" :
+                """Denotes a generic transport address.
+
+A TransportAddress value is always interpreted within the
+context of a TransportAddressType or TransportDomain value.
+Every usage of the TransportAddress textual convention MUST
+
+
+
+specify the TransportAddressType or TransportDomain object
+which provides the context. Furthermore, MIB authors SHOULD
+define a separate TransportAddressType or TransportDomain
+object for each TransportAddress object. It is suggested that
+the TransportAddressType or TransportDomain is logically
+registered before the object(s) which use the
+TransportAddress textual convention if they appear in the
+same logical row.
+
+The value of a TransportAddress object must always be
+consistent with the value of the associated
+TransportAddressType or TransportDomain object. Attempts
+to set a TransportAddress object to a value which is
+inconsistent with the associated TransportAddressType or
+TransportDomain must fail with an inconsistentValue error.
+
+When this textual convention is used as a syntax of an
+index object, there may be issues with the limit of 128
+sub-identifiers specified in SMIv2, STD 58. In this case,
+the OBJECT-TYPE declaration MUST include a 'SIZE' clause
+to limit the number of potential instance sub-identifiers.""",
+        },
+        "TransportAddressIPv4" : {
+            "basetype" : "OctetString",
+            "status" : "current",
+            "ranges" : [
+            {
+                "min" : "6",
+                "max" : "6"
+            },
+            ],
+            "range" : {
+                "min" : "6",
+                "max" : "6"
+            },
+            "format" : "1d.1d.1d.1d:2d",
+            "description" :
+                """Represents a transport address consisting of an IPv4
+address and a port number (as used for example by UDP,
+TCP and SCTP):
+
+ octets       contents         encoding
+  1-4         IPv4 address     network-byte order
+  5-6         port number      network-byte order
+
+This textual convention SHOULD NOT be used directly in object
+definitions since it restricts addresses to a specific format.
+However, if it is used, it MAY be used either on its own or
+in conjunction with TransportAddressType or TransportDomain
+as a pair.""",
+        },
+        "TransportAddressIPv6" : {
+            "basetype" : "OctetString",
+            "status" : "current",
+            "ranges" : [
+            {
+                "min" : "18",
+                "max" : "18"
+            },
+            ],
+            "range" : {
+                "min" : "18",
+                "max" : "18"
+            },
+            "format" : "0a[2x:2x:2x:2x:2x:2x:2x:2x]0a:2d",
+            "description" :
+                """Represents a transport address consisting of an IPv6
+address and a port number (as used for example by UDP,
+
+
+
+TCP and SCTP):
+
+ octets       contents         encoding
+  1-16        IPv6 address     network-byte order
+ 17-18        port number      network-byte order
+
+This textual convention SHOULD NOT be used directly in object
+definitions since it restricts addresses to a specific format.
+However, if it is used, it MAY be used either on its own or
+in conjunction with TransportAddressType or TransportDomain
+as a pair.""",
+        },
+        "TransportAddressIPv4z" : {
+            "basetype" : "OctetString",
+            "status" : "current",
+            "ranges" : [
+            {
+                "min" : "10",
+                "max" : "10"
+            },
+            ],
+            "range" : {
+                "min" : "10",
+                "max" : "10"
+            },
+            "format" : "1d.1d.1d.1d%4d:2d",
+            "description" :
+                """Represents a transport address consisting of an IPv4
+address, a zone index and a port number (as used for
+example by UDP, TCP and SCTP):
+
+ octets       contents         encoding
+  1-4         IPv4 address     network-byte order
+  5-8         zone index       network-byte order
+  9-10        port number      network-byte order
+
+This textual convention SHOULD NOT be used directly in object
+definitions since it restricts addresses to a specific format.
+However, if it is used, it MAY be used either on its own or
+in conjunction with TransportAddressType or TransportDomain
+as a pair.""",
+        },
+        "TransportAddressIPv6z" : {
+            "basetype" : "OctetString",
+            "status" : "current",
+            "ranges" : [
+            {
+                "min" : "22",
+                "max" : "22"
+            },
+            ],
+            "range" : {
+                "min" : "22",
+                "max" : "22"
+            },
+            "format" : "0a[2x:2x:2x:2x:2x:2x:2x:2x%4d]0a:2d",
+            "description" :
+                """Represents a transport address consisting of an IPv6
+address, a zone index and a port number (as used for
+example by UDP, TCP and SCTP):
+
+ octets       contents         encoding
+  1-16        IPv6 address     network-byte order
+ 17-20        zone index       network-byte order
+ 21-22        port number      network-byte order
+
+This textual convention SHOULD NOT be used directly in object
+definitions since it restricts addresses to a specific format.
+
+
+
+However, if it is used, it MAY be used either on its own or
+in conjunction with TransportAddressType or TransportDomain
+as a pair.""",
+        },
+        "TransportAddressLocal" : {
+            "basetype" : "OctetString",
+            "status" : "current",
+            "ranges" : [
+            {
+                "min" : "1",
+                "max" : "255"
+            },
+            ],
+            "range" : {
+                "min" : "1",
+                "max" : "255"
+            },
+            "format" : "1a",
+            "description" :
+                """Represents a POSIX Local IPC transport address:
+
+octets       contents                   encoding
+ all         POSIX Local IPC address    string
+
+The Posix Local IPC transport domain subsumes UNIX domain
+sockets.
+
+This textual convention SHOULD NOT be used directly in object
+definitions since it restricts addresses to a specific format.
+However, if it is used, it MAY be used either on its own or
+in conjunction with TransportAddressType or TransportDomain
+as a pair.
+
+When this textual convention is used as a syntax of an
+index object, there may be issues with the limit of 128
+sub-identifiers specified in SMIv2, STD 58. In this case,
+the OBJECT-TYPE declaration MUST include a 'SIZE' clause
+to limit the number of potential instance sub-identifiers.""",
+            "reference" :
+                """Protocol Independent Interfaces (IEEE POSIX 1003.1g)""",
+        },
+        "TransportAddressDns" : {
+            "basetype" : "OctetString",
+            "status" : "current",
+            "ranges" : [
+            {
+                "min" : "1",
+                "max" : "255"
+            },
+            ],
+            "range" : {
+                "min" : "1",
+                "max" : "255"
+            },
+            "format" : "1a",
+            "description" :
+                """Represents a DNS domain name followed by a colon ':'
+(ASCII character 0x3A) and a port number in ASCII.
+The name SHOULD be fully qualified whenever possible.
+
+Values of this textual convention are not directly useable as
+transport-layer addressing information, and require runtime
+resolution. As such, applications that write them must be
+prepared for handling errors if such values are not
+supported, or cannot be resolved (if resolution occurs at the
+time of the management operation).
+
+The DESCRIPTION clause of TransportAddress objects that may
+
+
+
+have TransportAddressDns values must fully describe how (and
+when) such names are to be resolved to IP addresses and vice
+versa.
+
+This textual convention SHOULD NOT be used directly in object
+definitions since it restricts addresses to a specific format.
+However, if it is used, it MAY be used either on its own or
+in conjunction with TransportAddressType or TransportDomain
+as a pair.
+
+When this textual convention is used as a syntax of an
+index object, there may be issues with the limit of 128
+sub-identifiers specified in SMIv2, STD 58. In this case,
+the OBJECT-TYPE declaration MUST include a 'SIZE' clause
+to limit the number of potential instance sub-identifiers.""",
+        },
+    }, # typedefs
+
+    "nodes" : {
+        "transportAddressMIB" : {
+            "nodetype" : "node",
+            "moduleName" : "TRANSPORT-ADDRESS-MIB",
+            "oid" : "1.3.6.1.2.1.100",
+            "status" : "current",
+        }, # node
+        "transportDomains" : {
+            "nodetype" : "node",
+            "moduleName" : "TRANSPORT-ADDRESS-MIB",
+            "oid" : "1.3.6.1.2.1.100.1",
+        }, # node
+        "transportDomainUdpIpv4" : {
+            "nodetype" : "node",
+            "moduleName" : "TRANSPORT-ADDRESS-MIB",
+            "oid" : "1.3.6.1.2.1.100.1.1",
+            "status" : "current",
+            "description" :
+                """The UDP over IPv4 transport domain.  The corresponding
+transport address is of type TransportAddressIPv4 for
+global IPv4 addresses.""",
+        }, # node
+        "transportDomainUdpIpv6" : {
+            "nodetype" : "node",
+            "moduleName" : "TRANSPORT-ADDRESS-MIB",
+            "oid" : "1.3.6.1.2.1.100.1.2",
+            "status" : "current",
+            "description" :
+                """The UDP over IPv6 transport domain.  The corresponding
+transport address is of type TransportAddressIPv6 for
+global IPv6 addresses.""",
+        }, # node
+        "transportDomainUdpIpv4z" : {
+            "nodetype" : "node",
+            "moduleName" : "TRANSPORT-ADDRESS-MIB",
+            "oid" : "1.3.6.1.2.1.100.1.3",
+            "status" : "current",
+            "description" :
+                """The UDP over IPv4 transport domain.  The corresponding
+transport address is of type TransportAddressIPv4z for
+scoped IPv4 addresses with a zone index.""",
+        }, # node
+        "transportDomainUdpIpv6z" : {
+            "nodetype" : "node",
+            "moduleName" : "TRANSPORT-ADDRESS-MIB",
+            "oid" : "1.3.6.1.2.1.100.1.4",
+            "status" : "current",
+            "description" :
+                """The UDP over IPv6 transport domain.  The corresponding
+transport address is of type TransportAddressIPv6z for
+scoped IPv6 addresses with a zone index.""",
+        }, # node
+        "transportDomainTcpIpv4" : {
+            "nodetype" : "node",
+            "moduleName" : "TRANSPORT-ADDRESS-MIB",
+            "oid" : "1.3.6.1.2.1.100.1.5",
+            "status" : "current",
+            "description" :
+                """The TCP over IPv4 transport domain.  The corresponding
+transport address is of type TransportAddressIPv4 for
+global IPv4 addresses.""",
+        }, # node
+        "transportDomainTcpIpv6" : {
+            "nodetype" : "node",
+            "moduleName" : "TRANSPORT-ADDRESS-MIB",
+            "oid" : "1.3.6.1.2.1.100.1.6",
+            "status" : "current",
+            "description" :
+                """The TCP over IPv6 transport domain.  The corresponding
+transport address is of type TransportAddressIPv6 for
+global IPv6 addresses.""",
+        }, # node
+        "transportDomainTcpIpv4z" : {
+            "nodetype" : "node",
+            "moduleName" : "TRANSPORT-ADDRESS-MIB",
+            "oid" : "1.3.6.1.2.1.100.1.7",
+            "status" : "current",
+            "description" :
+                """The TCP over IPv4 transport domain.  The corresponding
+transport address is of type TransportAddressIPv4z for
+scoped IPv4 addresses with a zone index.""",
+        }, # node
+        "transportDomainTcpIpv6z" : {
+            "nodetype" : "node",
+            "moduleName" : "TRANSPORT-ADDRESS-MIB",
+            "oid" : "1.3.6.1.2.1.100.1.8",
+            "status" : "current",
+            "description" :
+                """The TCP over IPv6 transport domain.  The corresponding
+transport address is of type TransportAddressIPv6z for
+scoped IPv6 addresses with a zone index.""",
+        }, # node
+        "transportDomainSctpIpv4" : {
+            "nodetype" : "node",
+            "moduleName" : "TRANSPORT-ADDRESS-MIB",
+            "oid" : "1.3.6.1.2.1.100.1.9",
+            "status" : "current",
+            "description" :
+                """The SCTP over IPv4 transport domain.  The corresponding
+transport address is of type TransportAddressIPv4 for
+global IPv4 addresses. This transport domain usually
+represents the primary address on multihomed SCTP
+endpoints.""",
+        }, # node
+        "transportDomainSctpIpv6" : {
+            "nodetype" : "node",
+            "moduleName" : "TRANSPORT-ADDRESS-MIB",
+            "oid" : "1.3.6.1.2.1.100.1.10",
+            "status" : "current",
+            "description" :
+                """The SCTP over IPv6 transport domain.  The corresponding
+transport address is of type TransportAddressIPv6 for
+global IPv6 addresses. This transport domain usually
+represents the primary address on multihomed SCTP
+endpoints.""",
+        }, # node
+        "transportDomainSctpIpv4z" : {
+            "nodetype" : "node",
+            "moduleName" : "TRANSPORT-ADDRESS-MIB",
+            "oid" : "1.3.6.1.2.1.100.1.11",
+            "status" : "current",
+            "description" :
+                """The SCTP over IPv4 transport domain.  The corresponding
+transport address is of type TransportAddressIPv4z for
+scoped IPv4 addresses with a zone index. This transport
+domain usually represents the primary address on
+multihomed SCTP endpoints.""",
+        }, # node
+        "transportDomainSctpIpv6z" : {
+            "nodetype" : "node",
+            "moduleName" : "TRANSPORT-ADDRESS-MIB",
+            "oid" : "1.3.6.1.2.1.100.1.12",
+            "status" : "current",
+            "description" :
+                """The SCTP over IPv6 transport domain.  The corresponding
+transport address is of type TransportAddressIPv6z for
+scoped IPv6 addresses with a zone index. This transport
+domain usually represents the primary address on
+multihomed SCTP endpoints.""",
+        }, # node
+        "transportDomainLocal" : {
+            "nodetype" : "node",
+            "moduleName" : "TRANSPORT-ADDRESS-MIB",
+            "oid" : "1.3.6.1.2.1.100.1.13",
+            "status" : "current",
+            "description" :
+                """The Posix Local IPC transport domain. The corresponding
+transport address is of type TransportAddressLocal.
+
+The Posix Local IPC transport domain incorporates the
+well-known UNIX domain sockets.""",
+        }, # node
+        "transportDomainUdpDns" : {
+            "nodetype" : "node",
+            "moduleName" : "TRANSPORT-ADDRESS-MIB",
+            "oid" : "1.3.6.1.2.1.100.1.14",
+            "status" : "current",
+            "description" :
+                """The UDP transport domain using fully qualified domain
+names. The corresponding transport address is of type
+TransportAddressDns.""",
+        }, # node
+        "transportDomainTcpDns" : {
+            "nodetype" : "node",
+            "moduleName" : "TRANSPORT-ADDRESS-MIB",
+            "oid" : "1.3.6.1.2.1.100.1.15",
+            "status" : "current",
+            "description" :
+                """The TCP transport domain using fully qualified domain
+names. The corresponding transport address is of type
+TransportAddressDns.""",
+        }, # node
+        "transportDomainSctpDns" : {
+            "nodetype" : "node",
+            "moduleName" : "TRANSPORT-ADDRESS-MIB",
+            "oid" : "1.3.6.1.2.1.100.1.16",
+            "status" : "current",
+            "description" :
+                """The SCTP transport domain using fully qualified domain
+names. The corresponding transport address is of type
+TransportAddressDns.""",
+        }, # node
+    }, # nodes
+
+}