OID reference

oammMjTable

1.3.6.1.4.1.629.10.14.1.2

Description

This table controls which entities the DC-OAM Management component should join to as master. Each join is represented by a row in this table. The status of each join is represented by a read-only object within each row. DC-MPLS OAM Manager requires a single join of type AMB_OAMM_MJ_I3 in order for it to go operStatusU…

Full description and source information

Identification

Identifier and names

Parent
1.3.6.1.4.1.629.10.14.1 (oammObjects)
Node code
2
Node name
oammMjTable
Category
SNMP management object
Numeric OID
1.3.6.1.4.1.629.10.14.1.2
URN notation
urn:oid:1.3.6.1.4.1.629.10.14.1.2
ASN.1, OID-IRI and named path variants
ASN.1 notation

{1 3 6 1 4 1 629 10 14 1 2}

  • {iso(1) identified-organization(3) dod(6) internet(1) private(4) enterprise(1) nbase(629) opx(10) oammMib(14) oammObjects(1) oammMjTable(2)}
  • {iso(1) identified-organization(3) dod(6) internet(1) private(4) enterprise(1) nbs(629) opx(10) oammMib(14) oammObjects(1) oammMjTable(2)}
  • {iso(1) identified-organization(3) dod(6) internet(1) private(4) enterprises(1) nbase(629) opx(10) oammMib(14) oammObjects(1) oammMjTable(2)}
  • {iso(1) identified-organization(3) dod(6) internet(1) private(4) enterprises(1) nbs(629) opx(10) oammMib(14) oammObjects(1) oammMjTable(2)}
  • {iso(1) identified-organization(3) dod(6) internet(1) private(4) ldap-enterprise(1) nbase(629) opx(10) oammMib(14) oammObjects(1) oammMjTable(2)}
  • {iso(1) identified-organization(3) dod(6) internet(1) private(4) ldap-enterprise(1) nbs(629) opx(10) oammMib(14) oammObjects(1) oammMjTable(2)}
  • {iso(1) identified-organization(3) dod(6) internet(1) private(4) vendor-objects(1) nbase(629) opx(10) oammMib(14) oammObjects(1) oammMjTable(2)}
  • {iso(1) identified-organization(3) dod(6) internet(1) private(4) vendor-objects(1) nbs(629) opx(10) oammMib(14) oammObjects(1) oammMjTable(2)}
  • {iso(1) org(3) dod(6) internet(1) private(4) enterprise(1) nbase(629) opx(10) oammMib(14) oammObjects(1) oammMjTable(2)}
  • {iso(1) org(3) dod(6) internet(1) private(4) enterprise(1) nbs(629) opx(10) oammMib(14) oammObjects(1) oammMjTable(2)}
  • {iso(1) org(3) dod(6) internet(1) private(4) enterprises(1) nbase(629) opx(10) oammMib(14) oammObjects(1) oammMjTable(2)}
  • {iso(1) org(3) dod(6) internet(1) private(4) enterprises(1) nbs(629) opx(10) oammMib(14) oammObjects(1) oammMjTable(2)}
  • {iso(1) org(3) dod(6) internet(1) private(4) ldap-enterprise(1) nbase(629) opx(10) oammMib(14) oammObjects(1) oammMjTable(2)}
  • {iso(1) org(3) dod(6) internet(1) private(4) ldap-enterprise(1) nbs(629) opx(10) oammMib(14) oammObjects(1) oammMjTable(2)}
  • {iso(1) org(3) dod(6) internet(1) private(4) vendor-objects(1) nbase(629) opx(10) oammMib(14) oammObjects(1) oammMjTable(2)}
  • {iso(1) org(3) dod(6) internet(1) private(4) vendor-objects(1) nbs(629) opx(10) oammMib(14) oammObjects(1) oammMjTable(2)}
  • Additional combinations skipped.
OID-IRI notation
  • /1/3/6/1/4/1/629/10/14/1/2
  • /ISO/Identified-Organization/6/1/4/1/629/10/14/1/2
  • /ISO/3/6/1/4/1/629/10/14/1/2
Named path variants
  • /iso/identified-organization/dod/internet/private/enterprise/nbase/opx/oammMib/oammObjects/oammMjTable
  • /iso/identified-organization/dod/internet/private/enterprise/nbs/opx/oammMib/oammObjects/oammMjTable
  • /iso/identified-organization/dod/internet/private/enterprises/nbase/opx/oammMib/oammObjects/oammMjTable
  • /iso/identified-organization/dod/internet/private/enterprises/nbs/opx/oammMib/oammObjects/oammMjTable
  • /iso/identified-organization/dod/internet/private/ldap-enterprise/nbase/opx/oammMib/oammObjects/oammMjTable
  • /iso/identified-organization/dod/internet/private/ldap-enterprise/nbs/opx/oammMib/oammObjects/oammMjTable
  • /iso/identified-organization/dod/internet/private/vendor-objects/nbase/opx/oammMib/oammObjects/oammMjTable
  • /iso/identified-organization/dod/internet/private/vendor-objects/nbs/opx/oammMib/oammObjects/oammMjTable
  • /iso/org/dod/internet/private/enterprise/nbase/opx/oammMib/oammObjects/oammMjTable
  • /iso/org/dod/internet/private/enterprise/nbs/opx/oammMib/oammObjects/oammMjTable
  • /iso/org/dod/internet/private/enterprises/nbase/opx/oammMib/oammObjects/oammMjTable
  • /iso/org/dod/internet/private/enterprises/nbs/opx/oammMib/oammObjects/oammMjTable
  • /iso/org/dod/internet/private/ldap-enterprise/nbase/opx/oammMib/oammObjects/oammMjTable
  • /iso/org/dod/internet/private/ldap-enterprise/nbs/opx/oammMib/oammObjects/oammMjTable
  • /iso/org/dod/internet/private/vendor-objects/nbase/opx/oammMib/oammObjects/oammMjTable
  • /iso/org/dod/internet/private/vendor-objects/nbs/opx/oammMib/oammObjects/oammMjTable
  • Additional combinations skipped.

SNMP properties

Value type
SEQUENCE OF OammMjEntry
Maximum access defined by MIB
not-accessible
Status in MIB
current

Properties come from available MIB definitions. Actual device support and access can differ. See source records below for original files and qualifications.

The displayed source records contain one distinct definition. Compare its source records.

oammMjTable OBJECT-TYPE
  -- FAMILY-SHORT-NAME OAMM_MJ
    SYNTAX      SEQUENCE OF OammMjEntry
    MAX-ACCESS  not-accessible
    STATUS      current
    DESCRIPTION "This table controls which entities the DC-OAM Management component should join to
                 as master.  Each join is represented by a row
                 in this table.  The status of each join is represented
                 by a read-only object within each row.

                 DC-MPLS OAM Manager requires a single join of type
                 AMB_OAMM_MJ_I3 in order for it to go operStatusUp.

                 Additional joins must be programmed in order to support
                 specific DC-MPLS OAM manager function.

                 - A single join of type AMB_OAMM_MJ_FRI is required if
                   DC-MPLS OAM Manager is to report faults status as
                   determined by OAM function.

                 - One or more joins of type AMB_OAMM_MJ_BFDI must be
                   programmed to enable DC-MPLS OAM Manager to intitiate BFD
                   sessions.

                 - One or more joins of type AMB_OAMM_MJ_LPI must be
                   programmed to enable DC-MPLS OAM Manager to intitiate LSP
                   Ping transactions.

                 - One or more joins of type AMB_OAMM_MJ_PMI must be
                   programmed to enable DC-MPLS OAM Manager to intitiate
                   Performance Monitoring sessions."
    ::= { oammObjects 2 }

Meaning

Descriptions

1 unique

Identical descriptions are grouped. Different wording and device-specific notes are retained.

This table controls which entities the DC-OAM Management component should join to as master. Each join is represented by a row in this table. The status of each join is represented by a read-only object within each row. DC-MPLS OAM Manager requires a single join of type AMB_OAMM_MJ_I3 in order for it to go operStatusUp. Additional joins must be programmed in order to support specific DC-MPLS OAM manager function. - A single join of type AMB_OAMM_MJ_FRI is required if DC-MPLS OAM Manager is to report faults status as determined by OAM function. - One or more joins of type AMB_OAMM_MJ_BFDI must be programmed to enable DC-MPLS OAM Manager to intitiate BFD sessions. - One or more joins of type AMB_OAMM_MJ_LPI must be programmed to enable DC-MPLS OAM Manager to intitiate LSP Ping transactions. - One or more joins of type AMB_OAMM_MJ_PMI must be programmed to enable DC-MPLS OAM Manager to intitiate Performance Monitoring sessions.

Sources for this description

Multiple manufacturers; see the original MIB MIB copies (LibreNMS/Observium Community)

See 1 matching source record

Evidence

Source records

1 records

Matching descriptions are grouped; open a group to compare definitions and supporting files.

Records for description 1Multiple manufacturers; see the original MIB MIB copies (LibreNMS/Observium Community)1 record · 1 source

Description 1

oammMjTable · currentMultiple manufacturers; see the original MIB MIB copies (LibreNMS/Observium Community)1 source

Status in source: current.

Names: oammMjTable

Technical details
{
  "smi_kind": "OBJECT-TYPE",
  "definition": [
    "oammMjTable",
    "OBJECT-TYPE",
    "SYNTAX",
    "SEQUENCE",
    "OF",
    "OammMjEntry",
    "MAX-ACCESS",
    "not-accessible",
    "STATUS",
    "current",
    "DESCRIPTION",
    "\"This table controls which entities the DC-OAM Management component should join to as master. Each join is represented by a row in this table. The status of each join is represented by a read-only object within each row. DC-MPLS OAM Manager requires a single join of type AMB_OAMM_MJ_I3 in order for it to go operStatusUp. Additional joins must be programmed in order to support specific DC-MPLS OAM manager function. - A single join of type AMB_OAMM_MJ_FRI is required if DC-MPLS OAM Manager is to report faults status as determined by OAM function. - One or more joins of type AMB_OAMM_MJ_BFDI must be programmed to enable DC-MPLS OAM Manager to intitiate BFD sessions. - One or more joins of type AMB_OAMM_MJ_LPI must be programmed to enable DC-MPLS OAM Manager to intitiate LSP Ping transactions. - One or more joins of type AMB_OAMM_MJ_PMI must be programmed to enable DC-MPLS OAM Manager to intitiate Performance Monitoring sessions.\"",
    "::=",
    "{",
    "oammObjects",
    "2",
    "}"
  ],
  "syntax_tree": [
    [
      "conceptualTable",
      [
        "row",
        "OammMjEntry"
      ]
    ],
    null,
    [
      "MaxAccessPart",
      "not-accessible"
    ],
    [
      "Status",
      "current"
    ],
    [
      "DESCRIPTION",
      "This table controls which entities the DC-OAM Management component should join to as master. Each join is represented by a row in this table. The status of each join is represented by a read-only object within each row. DC-MPLS OAM Manager requires a single join of type AMB_OAMM_MJ_I3 in order for it to go operStatusUp. Additional joins must be programmed in order to support specific DC-MPLS OAM manager function. - A single join of type AMB_OAMM_MJ_FRI is required if DC-MPLS OAM Manager is to report faults status as determined by OAM function. - One or more joins of type AMB_OAMM_MJ_BFDI must be programmed to enable DC-MPLS OAM Manager to intitiate BFD sessions. - One or more joins of type AMB_OAMM_MJ_LPI must be programmed to enable DC-MPLS OAM Manager to intitiate LSP Ping transactions. - One or more joins of type AMB_OAMM_MJ_PMI must be programmed to enable DC-MPLS OAM Manager to intitiate Performance Monitoring sessions."
    ],
    null,
    null,
    null,
    null
  ]
}

Registration

Registration authorities

First Registration Authority (inferred from ancestor 1.3.6.1.4.1.629)

Rotenstein Sergiu

Direct children (1)

OIDNameDirect childrenDescendantsDescription
1.3.6.1.4.1.629.10.14.1.2.1 oammMjEntry99

Siblings (1)

OIDNameDirect childrenDescendantsDescription
1.3.6.1.4.1.629.10.14.1.1 oammEntTable18