Reference record for OID 1.3.6.1.2.1.122.2.2.2


parent
1.3.6.1.2.1.122.2.2 (teModuleCompliance)
node code
2
node name
teModuleFullCompliance
dot oid
1.3.6.1.2.1.122.2.2.2
type
MODULE-COMPLIANCE
asn1 oid
  • {iso(1) identified-organization(3) dod(6) internet(1) mgmt(2) mib-2(1) teMIB(122) teMIBConformance(2) teModuleCompliance(2) teModuleFullCompliance(2)}
  • {iso(1) identified-organization(3) dod(6) internet(1) mgmt(2) mib-2(1) teMIB(122) teTunnelTable(2) teModuleCompliance(2) teModuleFullCompliance(2)}
  • ...skipped...
  • {iso(1) org(3) dod(6) internet(1) mgmt(2) mib-2(1) teMIB(122) teMIBConformance(2) teModuleCompliance(2) teModuleFullCompliance(2)}
  • {iso(1) org(3) dod(6) internet(1) mgmt(2) mib-2(1) teMIB(122) teTunnelTable(2) teModuleCompliance(2) teModuleFullCompliance(2)}
  • {iso(1) org(3) dod(6) internet(1) mgmt(2) mib(1) teMIB(122) teMIBConformance(2) teModuleCompliance(2) teModuleFullCompliance(2)}
  • {iso(1) org(3) dod(6) internet(1) mgmt(2) mib(1) teMIB(122) teTunnelTable(2) teModuleCompliance(2) teModuleFullCompliance(2)}
  • ...skipped...
  • {iso(1) iso-identified-organization(3) dod(6) internet(1) mgmt(2) mib(1) teMIB(122) teMIBConformance(2) teModuleCompliance(2) teModuleFullCompliance(2)}
  • {iso(1) iso-identified-organization(3) dod(6) internet(1) mgmt(2) mib(1) teMIB(122) teTunnelTable(2) teModuleCompliance(2) teModuleFullCompliance(2)}
  • iri oid
  • /iso/identified-organization/dod/internet/mgmt/mib-2/teMIB/teMIBConformance/teModuleCompliance/teModuleFullCompliance
  • /iso/identified-organization/dod/internet/mgmt/mib-2/teMIB/teTunnelTable/teModuleCompliance/teModuleFullCompliance
  • ...skipped...
  • /iso/org/dod/internet/mgmt/mib-2/teMIB/teMIBConformance/teModuleCompliance/teModuleFullCompliance
  • /iso/org/dod/internet/mgmt/mib-2/teMIB/teTunnelTable/teModuleCompliance/teModuleFullCompliance
  • /iso/org/dod/internet/mgmt/mib/teMIB/teMIBConformance/teModuleCompliance/teModuleFullCompliance
  • /iso/org/dod/internet/mgmt/mib/teMIB/teTunnelTable/teModuleCompliance/teModuleFullCompliance
  • ...skipped...
  • /iso/iso-identified-organization/dod/internet/mgmt/mib/teMIB/teMIBConformance/teModuleCompliance/teModuleFullCompliance
  • /iso/iso-identified-organization/dod/internet/mgmt/mib/teMIB/teTunnelTable/teModuleCompliance/teModuleFullCompliance
  • iri by oid_info
    /ISO/Identified-Organization/6/1/2/1/122/2/2/2

    Description by oid_info

    teModuleFullCompliance MODULE-COMPLIANCE
    STATUS current
    DESCRIPTION "When this MIB module is implemented with support for
    read-create, then the implementation can claim
    full compliance. Such devices can be both
    monitored and configured with this MIB module.
    "
    MODULE -- enclosing module, i.e., TE-MIB
    MANDATORY-GROUPS {
    teTrafficEngineeringGroup
    }
    GROUP teNotificationGroup
    DESCRIPTION "Implementation of this group is optional."
    OBJECT teAdminGroupRowStatus
    SYNTAX RowStatus { active(1) }
    WRITE-SYNTAX RowStatus { createAndGo(4), destroy(6) }
    DESCRIPTION "Support for notInService, createAndWait and
    notReady is not required.
    "
    OBJECT teTunnelRowStatus
    SYNTAX RowStatus { active(1), notInService(2) }
    WRITE-SYNTAX RowStatus { active(1), notInService(2),
    createAndGo(4), destroy(6)
    }
    DESCRIPTION "Support for createAndWait and notReady is not
    required.
    "
    OBJECT teTunnelSourceAddressType
    SYNTAX TeHopAddressType { ipv4(1), ipv6(2) }
    DESCRIPTION "Write access is required. An implementation is
    only required to support IPv4 and IPv6 host
    addresses.
    "
    OBJECT tePathRowStatus
    SYNTAX RowStatus { active(1), notInService(2) }
    WRITE-SYNTAX RowStatus { active(1), notInService(2),
    createAndGo(4), destroy(6)
    }
    DESCRIPTION "Support for createAndWait and notReady is not
    required.
    "
    OBJECT tePathHopRowStatus
    SYNTAX RowStatus { active(1), notInService(2) }
    WRITE-SYNTAX RowStatus { active(1), notInService(2),
    createAndGo(4), destroy(6)
    }
    DESCRIPTION "Support for createAndWait and notReady is not
    required.
    "

    View at oid-info.com

    Description by mibdepot

    When this MIB module is implemented with support for
    read-create, then the implementation can claim
    full compliance. Such devices can be both
    monitored and configured with this MIB module.

    Parsed from file rfc3970-Traffic-Engineering-TE.mib.txt
    Company: None
    Module: TE-MIB

    Description by circitor

    When this MIB module is implemented with support for
    read-create, then the implementation can claim
    full compliance. Such devices can be both



    monitored and configured with this MIB module.

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

    Information by oid_info

    Automatically extracted from RFC3970

    Information by mibdepot

    teModuleFullCompliance MODULE-COMPLIANCE STATUS current DESCRIPTION "When this MIB module is implemented with support for read-create, then the implementation can claim full compliance. Such devices can be both monitored and configured with this MIB module. " MODULE MANDATORY-GROUPS { teTrafficEngineeringGroup } GROUP teNotificationGroup DESCRIPTION "Implementation of this group is optional." OBJECT teAdminGroupRowStatus SYNTAX RowStatus { active(1) } WRITE-SYNTAX RowStatus { createAndGo(4), destroy(6) } DESCRIPTION "Support for notInService, createAndWait and notReady is not required. " OBJECT teTunnelRowStatus SYNTAX RowStatus { active(1), notInService(2) } WRITE-SYNTAX RowStatus { active(1), notInService(2), createAndGo(4), destroy(6) } DESCRIPTION "Support for createAndWait and notReady is not required. " OBJECT teTunnelSourceAddressType SYNTAX TeHopAddressType { ipv4(1), ipv6(2) } DESCRIPTION "Write access is required. An implementation is only required to support IPv4 and IPv6 host addresses. " OBJECT tePathRowStatus SYNTAX RowStatus { active(1), notInService(2) } WRITE-SYNTAX RowStatus { active(1), notInService(2), createAndGo(4), destroy(6) } DESCRIPTION "Support for createAndWait and notReady is not required. " OBJECT tePathHopRowStatus SYNTAX RowStatus { active(1), notInService(2) } WRITE-SYNTAX RowStatus { active(1), notInService(2), createAndGo(4), destroy(6) } DESCRIPTION "Support for createAndWait and notReady is not required. " ::= { teModuleCompliance 2 }

    Information by circitor

    teModuleFullCompliance MODULE-COMPLIANCE STATUS current DESCRIPTION "When this MIB module is implemented with support for read-create, then the implementation can claim full compliance. Such devices can be both monitored and configured with this MIB module. " MODULE MANDATORY-GROUPS { teTrafficEngineeringGroup } GROUP teNotificationGroup DESCRIPTION "Implementation of this group is optional." OBJECT teAdminGroupRowStatus SYNTAX RowStatus { active(1) } WRITE-SYNTAX RowStatus { createAndGo(4), destroy(6) } DESCRIPTION "Support for notInService, createAndWait and notReady is not required. " OBJECT teTunnelRowStatus SYNTAX RowStatus { active(1), notInService(2) } WRITE-SYNTAX RowStatus { active(1), notInService(2), createAndGo(4), destroy(6) } DESCRIPTION "Support for createAndWait and notReady is not required. " OBJECT teTunnelSourceAddressType SYNTAX TeHopAddressType { ipv4(1), ipv6(2) } DESCRIPTION "Write access is required. An implementation is only required to support IPv4 and IPv6 host addresses. " OBJECT tePathRowStatus SYNTAX RowStatus { active(1), notInService(2) } WRITE-SYNTAX RowStatus { active(1), notInService(2), createAndGo(4), destroy(6) } DESCRIPTION "Support for createAndWait and notReady is not required. " OBJECT tePathHopRowStatus SYNTAX RowStatus { active(1), notInService(2) } WRITE-SYNTAX RowStatus { active(1), notInService(2), createAndGo(4), destroy(6) } DESCRIPTION "Support for createAndWait and notReady is not required. " ::= { teModuleCompliance 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 (3)

    OIDNameSub childrenSub Nodes TotalDescription
    1.3.6.1.2.1.122.2.2.1 teModuleReadOnlyCompliance 0 0 When this MIB module is implemented without support
    for read-create (i.e., in read-only mode), then such
    an implementation can cl…
    1.3.6.1.2.1.122.2.2.3 teModuleServerReadOnlyCompliance 0 0 When this MIB module is implemented by a path
    computation server without support for read-create
    (i.e., in read-only mode), then …
    1.3.6.1.2.1.122.2.2.4 teModuleServerFullCompliance 0 0 When this MIB module is implemented by a path
    computation server with support for read-create,
    then the implementation can claim …