Reference record for OID 1.3.6.1.2.1.50.2.1.2


parent
1.3.6.1.2.1.50.2.1 (udpMIBCompliances)
node code
2
node name
udpMIBCompliance2
dot oid
1.3.6.1.2.1.50.2.1.2
type
OBJECT IDENTIFIER
asn1 oid
  • {iso(1) identified-organization(3) dod(6) internet(1) mgmt(2) mib-2(1) udpMIB(50) udpMIBConformance(2) udpMIBCompliances(1) udpMIBCompliance2(2)}
  • {iso(1) identified-organization(3) dod(6) internet(1) mgmt(2) mib(1) udpMIB(50) udpMIBConformance(2) udpMIBCompliances(1) udpMIBCompliance2(2)}
  • {iso(1) org(3) dod(6) internet(1) mgmt(2) mib-2(1) udpMIB(50) udpMIBConformance(2) udpMIBCompliances(1) udpMIBCompliance2(2)}
  • {iso(1) org(3) dod(6) internet(1) mgmt(2) mib(1) udpMIB(50) udpMIBConformance(2) udpMIBCompliances(1) udpMIBCompliance2(2)}
  • {iso(1) iso-identified-organization(3) dod(6) internet(1) mgmt(2) mib-2(1) udpMIB(50) udpMIBConformance(2) udpMIBCompliances(1) udpMIBCompliance2(2)}
  • {iso(1) iso-identified-organization(3) dod(6) internet(1) mgmt(2) mib(1) udpMIB(50) udpMIBConformance(2) udpMIBCompliances(1) udpMIBCompliance2(2)}
  • iri oid
  • /iso/identified-organization/dod/internet/mgmt/mib-2/udpMIB/udpMIBConformance/udpMIBCompliances/udpMIBCompliance2
  • /iso/identified-organization/dod/internet/mgmt/mib/udpMIB/udpMIBConformance/udpMIBCompliances/udpMIBCompliance2
  • /iso/org/dod/internet/mgmt/mib-2/udpMIB/udpMIBConformance/udpMIBCompliances/udpMIBCompliance2
  • /iso/org/dod/internet/mgmt/mib/udpMIB/udpMIBConformance/udpMIBCompliances/udpMIBCompliance2
  • /iso/iso-identified-organization/dod/internet/mgmt/mib-2/udpMIB/udpMIBConformance/udpMIBCompliances/udpMIBCompliance2
  • /iso/iso-identified-organization/dod/internet/mgmt/mib/udpMIB/udpMIBConformance/udpMIBCompliances/udpMIBCompliance2
  • iri by oid_info
    /ISO/Identified-Organization/6/1/2/1/50/2/1/2

    Description by circitor

    The compliance statement for systems that implement
    UDP.

    There are a number of INDEX objects that cannot be
    represented in the form of OBJECT clauses in SMIv2, but
    for which we have the following compliance
    requirements, expressed in OBJECT clause form in this
    description clause:

    Parsed from file UDP-MIB.mib
    Module: UDP-MIB

    Description by oid_info

    udpMIBCompliance2 MODULE-COMPLIANCE
    STATUS current
    DESCRIPTION
    "The compliance statement for systems that implement
    UDP.
    There are a number of INDEX objects that cannot be
    represented in the form of OBJECT clauses in SMIv2, but
    for which we have the following compliance
    requirements, expressed in OBJECT clause form in this
    description clause:
    -- OBJECT udpEndpointLocalAddressType
    -- SYNTAX InetAddressType { unknown(0), ipv4(1),
    -- ipv6(2), ipv4z(3),
    -- ipv6z(4) }
    -- DESCRIPTION
    -- Support for dns(5) is not required.
    -- OBJECT udpEndpointLocalAddress
    -- SYNTAX InetAddress (SIZE(0|4|8|16|20))
    -- DESCRIPTION
    -- Support is only required for zero-length
    -- octet-strings, and for scoped and unscoped
    -- IPv4 and IPv6 addresses.
    -- OBJECT udpEndpointRemoteAddressType
    -- SYNTAX InetAddressType { unknown(0), ipv4(1),
    -- ipv6(2), ipv4z(3),
    -- ipv6z(4) }
    -- DESCRIPTION
    -- Support for dns(5) is not required.
    -- OBJECT udpEndpointRemoteAddress
    -- SYNTAX InetAddress (SIZE(0|4|8|16|20))
    -- DESCRIPTION
    -- Support is only required for zero-length
    -- octet-strings, and for scoped and unscoped
    -- IPv4 and IPv6 addresses.
    "
    MODULE -- this module
    MANDATORY-GROUPS { udpBaseGroup, udpEndpointGroup }
    GROUP udpHCGroup
    DESCRIPTION
    "This group is mandatory for systems that
    are capable of receiving or transmitting more than
    1 million UDP datagrams per second. 1 million
    datagrams per second will cause a Counter32 to
    wrap in just over an hour."

    View at oid-info.com

    Description by mibdepot

    The compliance statement for systems that implement
    UDP.

    There are a number of INDEX objects that cannot be
    represented in the form of OBJECT clauses in SMIv2, but
    for which we have the following compliance
    requirements, expressed in OBJECT clause form in this
    description clause:

    Parsed from file UDP-MIB.mib.txt
    Company: None
    Module: UDP-MIB

    Description by cisco

    The compliance statement for systems that implement
    UDP.

    There are a number of INDEX objects that cannot be
    represented in the form of OBJECT clauses in SMIv2, but
    for which we have the following compliance
    requirements, expressed in OBJECT clause form in this
    description clause:

    Information by circitor

    udpMIBCompliance2 MODULE-COMPLIANCE STATUS current DESCRIPTION "The compliance statement for systems that implement UDP. There are a number of INDEX objects that cannot be represented in the form of OBJECT clauses in SMIv2, but for which we have the following compliance requirements, expressed in OBJECT clause form in this description clause: " MODULE MANDATORY-GROUPS { udpBaseGroup, udpEndpointGroup } GROUP udpHCGroup DESCRIPTION "This group is mandatory for systems that are capable of receiving or transmitting more than 1 million UDP datagrams per second. 1 million datagrams per second will cause a Counter32 to wrap in just over an hour." ::= { udpMIBCompliances 2 }

    Information by cisco_v1

    udpMIBCompliance2 OBJECT IDENTIFIER ::= { udpMIBCompliances 2 }

    Information by oid_info

    Automatically extracted from RFC4113

    Information by mibdepot

    udpMIBCompliance2 MODULE-COMPLIANCE STATUS current DESCRIPTION "The compliance statement for systems that implement UDP. There are a number of INDEX objects that cannot be represented in the form of OBJECT clauses in SMIv2, but for which we have the following compliance requirements, expressed in OBJECT clause form in this description clause: " MODULE MANDATORY-GROUPS { udpBaseGroup, udpEndpointGroup } GROUP udpHCGroup DESCRIPTION "This group is mandatory for systems that are capable of receiving or transmitting more than 1 million UDP datagrams per second. 1 million datagrams per second will cause a Counter32 to wrap in just over an hour." ::= { udpMIBCompliances 2 }

    Information by cisco

    udpMIBCompliance2 MODULE-COMPLIANCE STATUS current DESCRIPTION "The compliance statement for systems that implement UDP. There are a number of INDEX objects that cannot be represented in the form of OBJECT clauses in SMIv2, but for which we have the following compliance requirements, expressed in OBJECT clause form in this description clause: " MODULE MANDATORY-GROUPS { udpBaseGroup, udpEndpointGroup } GROUP udpHCGroup DESCRIPTION "This group is mandatory for systems that are capable of receiving or transmitting more than 1 million UDP datagrams per second. 1 million datagrams per second will cause a Counter32 to wrap in just over an hour." ::= { udpMIBCompliances 2 }

    First Registration Authority (recovered by parent 1.3.6)

    Defense Communication Agency

    Current Registration Authority (recovered by parent 1.3.6.1.2)

    Internet Assigned Numbers Authority

    Brothers (1)

    OIDNameSub childrenSub Nodes TotalDescription
    1.3.6.1.2.1.50.2.1.1 udpMIBCompliance 0 0 udpMIBCompliance MODULE-COMPLIANCE
    STATUS current
    DESCRIPTION
    "The compliance statement for SNMPv2 entities which
    implement UDP…