OID reference

fsMplsTpNodeIdentifier

1.3.6.1.4.1.2076.13.8.1.2.1.5

Description

This object allows the operator or service provider to assign a unique MPLS-TP Node Identifier. The Node Identifier is assigned within the scope of the Global Identifier or Operator Identifier. The value 0 (or 0.0.0.0 in dotted decimal notation) is reserved and MUST NOT be used. When IPv4 addresses are in use, the val…

Full description and source information

Identification

Identifier and names

Parent
1.3.6.1.4.1.2076.13.8.1.2.1 (fsMplsTpGlobalConfigEntry)
Node code
5
Node name
fsMplsTpNodeIdentifier
Category
SNMP management object
Numeric OID
1.3.6.1.4.1.2076.13.8.1.2.1.5
URN notation
urn:oid:1.3.6.1.4.1.2076.13.8.1.2.1.5
ASN.1, OID-IRI and named path variants
ASN.1 notation

{1 3 6 1 4 1 2076 13 8 1 2 1 5}

  • {iso(1) identified-organization(3) dod(6) internet(1) private(4) enterprise(1) 2076 13 fsMplsTpMIB(8) fsMplsTpObjects(1) fsMplsTpGlobalConfigTable(2) fsMplsTpGlobalConfigEntry(1) fsMplsTpNodeIdentifier(5)}
  • {iso(1) identified-organization(3) dod(6) internet(1) private(4) enterprises(1) 2076 13 fsMplsTpMIB(8) fsMplsTpObjects(1) fsMplsTpGlobalConfigTable(2) fsMplsTpGlobalConfigEntry(1) fsMplsTpNodeIdentifier(5)}
  • {iso(1) identified-organization(3) dod(6) internet(1) private(4) ldap-enterprise(1) 2076 13 fsMplsTpMIB(8) fsMplsTpObjects(1) fsMplsTpGlobalConfigTable(2) fsMplsTpGlobalConfigEntry(1) fsMplsTpNodeIdentifier(5)}
  • {iso(1) identified-organization(3) dod(6) internet(1) private(4) vendor-objects(1) 2076 13 fsMplsTpMIB(8) fsMplsTpObjects(1) fsMplsTpGlobalConfigTable(2) fsMplsTpGlobalConfigEntry(1) fsMplsTpNodeIdentifier(5)}
  • {iso(1) org(3) dod(6) internet(1) private(4) enterprise(1) 2076 13 fsMplsTpMIB(8) fsMplsTpObjects(1) fsMplsTpGlobalConfigTable(2) fsMplsTpGlobalConfigEntry(1) fsMplsTpNodeIdentifier(5)}
  • {iso(1) org(3) dod(6) internet(1) private(4) enterprises(1) 2076 13 fsMplsTpMIB(8) fsMplsTpObjects(1) fsMplsTpGlobalConfigTable(2) fsMplsTpGlobalConfigEntry(1) fsMplsTpNodeIdentifier(5)}
  • {iso(1) org(3) dod(6) internet(1) private(4) ldap-enterprise(1) 2076 13 fsMplsTpMIB(8) fsMplsTpObjects(1) fsMplsTpGlobalConfigTable(2) fsMplsTpGlobalConfigEntry(1) fsMplsTpNodeIdentifier(5)}
  • {iso(1) org(3) dod(6) internet(1) private(4) vendor-objects(1) 2076 13 fsMplsTpMIB(8) fsMplsTpObjects(1) fsMplsTpGlobalConfigTable(2) fsMplsTpGlobalConfigEntry(1) fsMplsTpNodeIdentifier(5)}
  • {iso(1) iso-identified-organization(3) dod(6) internet(1) private(4) enterprise(1) 2076 13 fsMplsTpMIB(8) fsMplsTpObjects(1) fsMplsTpGlobalConfigTable(2) fsMplsTpGlobalConfigEntry(1) fsMplsTpNodeIdentifier(5)}
  • {iso(1) iso-identified-organization(3) dod(6) internet(1) private(4) enterprises(1) 2076 13 fsMplsTpMIB(8) fsMplsTpObjects(1) fsMplsTpGlobalConfigTable(2) fsMplsTpGlobalConfigEntry(1) fsMplsTpNodeIdentifier(5)}
  • {iso(1) iso-identified-organization(3) dod(6) internet(1) private(4) ldap-enterprise(1) 2076 13 fsMplsTpMIB(8) fsMplsTpObjects(1) fsMplsTpGlobalConfigTable(2) fsMplsTpGlobalConfigEntry(1) fsMplsTpNodeIdentifier(5)}
  • {iso(1) iso-identified-organization(3) dod(6) internet(1) private(4) vendor-objects(1) 2076 13 fsMplsTpMIB(8) fsMplsTpObjects(1) fsMplsTpGlobalConfigTable(2) fsMplsTpGlobalConfigEntry(1) fsMplsTpNodeIdentifier(5)}
  • {iso(1) iso-organization(3) dod(6) internet(1) private(4) enterprise(1) 2076 13 fsMplsTpMIB(8) fsMplsTpObjects(1) fsMplsTpGlobalConfigTable(2) fsMplsTpGlobalConfigEntry(1) fsMplsTpNodeIdentifier(5)}
  • {iso(1) iso-organization(3) dod(6) internet(1) private(4) enterprises(1) 2076 13 fsMplsTpMIB(8) fsMplsTpObjects(1) fsMplsTpGlobalConfigTable(2) fsMplsTpGlobalConfigEntry(1) fsMplsTpNodeIdentifier(5)}
  • {iso(1) iso-organization(3) dod(6) internet(1) private(4) ldap-enterprise(1) 2076 13 fsMplsTpMIB(8) fsMplsTpObjects(1) fsMplsTpGlobalConfigTable(2) fsMplsTpGlobalConfigEntry(1) fsMplsTpNodeIdentifier(5)}
  • {iso(1) iso-organization(3) dod(6) internet(1) private(4) vendor-objects(1) 2076 13 fsMplsTpMIB(8) fsMplsTpObjects(1) fsMplsTpGlobalConfigTable(2) fsMplsTpGlobalConfigEntry(1) fsMplsTpNodeIdentifier(5)}
OID-IRI notation
  • /1/3/6/1/4/1/2076/13/8/1/2/1/5
  • /ISO/Identified-Organization/6/1/4/1/2076/13/8/1/2/1/5
  • /ISO/3/6/1/4/1/2076/13/8/1/2/1/5
Named path variants
  • /iso/identified-organization/dod/internet/private/enterprise/2076/13/fsMplsTpMIB/fsMplsTpObjects/fsMplsTpGlobalConfigTable/fsMplsTpGlobalConfigEntry/fsMplsTpNodeIdentifier
  • /iso/identified-organization/dod/internet/private/enterprises/2076/13/fsMplsTpMIB/fsMplsTpObjects/fsMplsTpGlobalConfigTable/fsMplsTpGlobalConfigEntry/fsMplsTpNodeIdentifier
  • /iso/identified-organization/dod/internet/private/ldap-enterprise/2076/13/fsMplsTpMIB/fsMplsTpObjects/fsMplsTpGlobalConfigTable/fsMplsTpGlobalConfigEntry/fsMplsTpNodeIdentifier
  • /iso/identified-organization/dod/internet/private/vendor-objects/2076/13/fsMplsTpMIB/fsMplsTpObjects/fsMplsTpGlobalConfigTable/fsMplsTpGlobalConfigEntry/fsMplsTpNodeIdentifier
  • /iso/org/dod/internet/private/enterprise/2076/13/fsMplsTpMIB/fsMplsTpObjects/fsMplsTpGlobalConfigTable/fsMplsTpGlobalConfigEntry/fsMplsTpNodeIdentifier
  • /iso/org/dod/internet/private/enterprises/2076/13/fsMplsTpMIB/fsMplsTpObjects/fsMplsTpGlobalConfigTable/fsMplsTpGlobalConfigEntry/fsMplsTpNodeIdentifier
  • /iso/org/dod/internet/private/ldap-enterprise/2076/13/fsMplsTpMIB/fsMplsTpObjects/fsMplsTpGlobalConfigTable/fsMplsTpGlobalConfigEntry/fsMplsTpNodeIdentifier
  • /iso/org/dod/internet/private/vendor-objects/2076/13/fsMplsTpMIB/fsMplsTpObjects/fsMplsTpGlobalConfigTable/fsMplsTpGlobalConfigEntry/fsMplsTpNodeIdentifier
  • /iso/iso-identified-organization/dod/internet/private/enterprise/2076/13/fsMplsTpMIB/fsMplsTpObjects/fsMplsTpGlobalConfigTable/fsMplsTpGlobalConfigEntry/fsMplsTpNodeIdentifier
  • /iso/iso-identified-organization/dod/internet/private/enterprises/2076/13/fsMplsTpMIB/fsMplsTpObjects/fsMplsTpGlobalConfigTable/fsMplsTpGlobalConfigEntry/fsMplsTpNodeIdentifier
  • /iso/iso-identified-organization/dod/internet/private/ldap-enterprise/2076/13/fsMplsTpMIB/fsMplsTpObjects/fsMplsTpGlobalConfigTable/fsMplsTpGlobalConfigEntry/fsMplsTpNodeIdentifier
  • /iso/iso-identified-organization/dod/internet/private/vendor-objects/2076/13/fsMplsTpMIB/fsMplsTpObjects/fsMplsTpGlobalConfigTable/fsMplsTpGlobalConfigEntry/fsMplsTpNodeIdentifier
  • /iso/iso-organization/dod/internet/private/enterprise/2076/13/fsMplsTpMIB/fsMplsTpObjects/fsMplsTpGlobalConfigTable/fsMplsTpGlobalConfigEntry/fsMplsTpNodeIdentifier
  • /iso/iso-organization/dod/internet/private/enterprises/2076/13/fsMplsTpMIB/fsMplsTpObjects/fsMplsTpGlobalConfigTable/fsMplsTpGlobalConfigEntry/fsMplsTpNodeIdentifier
  • /iso/iso-organization/dod/internet/private/ldap-enterprise/2076/13/fsMplsTpMIB/fsMplsTpObjects/fsMplsTpGlobalConfigTable/fsMplsTpGlobalConfigEntry/fsMplsTpNodeIdentifier
  • /iso/iso-organization/dod/internet/private/vendor-objects/2076/13/fsMplsTpMIB/fsMplsTpObjects/fsMplsTpGlobalConfigTable/fsMplsTpGlobalConfigEntry/fsMplsTpNodeIdentifier

SNMP properties

Value type
Unsigned32
Maximum access defined by MIB
read-write
Status in MIB
current
Default value
0

Definitions may combine these properties differently.

Compare 2 source variants

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

Value type
Unsigned32
Maximum access defined by MIB
read-write
Status in MIB
current
Default value
0

Variant 2 — Belden, GarrettCom and Hirschmann IT official standalone MIBs

Value type
Unsigned32
Maximum access defined by MIB
read-write
Status in MIB
current

Using this OID with SNMP

At least one MIB declaration places this object in a table row. A value belongs to a row instance; its suffix depends on the row's INDEX or AUGMENTS definition. The index encoding is not inferred here.

Published row index: fsMplsTpContextId.

snmpwalk [connection options] DEVICE .1.3.6.1.4.1.2076.13.8.1.2.1.5

Replace the placeholders with your connection and authentication options. Available permissions and device support can differ from the MIB.

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

Available source records contain 2 distinct definitions; some records may not include a definition.

Show 2 published definitions

fsMplsTpNodeIdentifier · current

fsMplsTpNodeIdentifier OBJECT-TYPE
         SYNTAX      Unsigned32
         MAX-ACCESS  read-write
         STATUS      current
         DESCRIPTION
             "This object allows the operator or service provider to assign a
              unique MPLS-TP Node Identifier.

              The Node Identifier is assigned within the scope of the Global
              Identifier or Operator Identifier. 

              The value 0 (or 0.0.0.0 in dotted decimal notation) is reserved
              and MUST NOT be used.

              When IPv4 addresses are in use, the value of this object can be
              derived from the LSR's /32 IPv4 loopback address.

              Note that, when IP reachability is not needed, the 32-bit Node
              Identifier is not required to have any association with the IPv4
              address space.
              
              Note: The value of this object has to be explicitly configured 
              by the user in both cases.A Node Id with 0 is the default 
              value and is not a valid configuration for a operationally 
              active node."
         REFERENCE
             "MPLS-TP Identifiers draft version 02, Section 4"
         DEFVAL { 0 }
        ::= { fsMplsTpGlobalConfigEntry 5 }

fsMplsTpNodeIdentifier · current

fsMplsTpNodeIdentifier OBJECT-TYPE
         SYNTAX      Unsigned32
         MAX-ACCESS  read-write
         STATUS      current
         DESCRIPTION
             "This object allows the operator or service provider to assign a
              unique MPLS-TP Node Identifier.

              The Node Identifier is assigned within the scope of the Global
              Identifier or Operator Identifier. 

              The value 0 (or 0.0.0.0 in dotted decimal notation) is reserved
              and MUST NOT be used.

              When IPv4 addresses are in use, the value of this object can be
              derived from the LSR's /32 IPv4 loopback address.

              Note that, when IP reachability is not needed, the 32-bit Node
              Identifier is not required to have any association with the IPv4
              address space.
              
              Note: The value of this object has to be explicitly configured 
              by the user in both cases."
         REFERENCE
             "MPLS-TP Identifiers draft version 02, Section 4"
        ::= { fsMplsTpGlobalConfigEntry 5 }

Meaning

Descriptions

2 unique

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

Description 1

This object allows the operator or service provider to assign a unique MPLS-TP Node Identifier. The Node Identifier is assigned within the scope of the Global Identifier or Operator Identifier. The value 0 (or 0.0.0.0 in dotted decimal notation) is reserved and MUST NOT be used. When IPv4 addresses are in use, the value of this object can be derived from the LSR's /32 IPv4 loopback address. Note that, when IP reachability is not needed, the 32-bit Node Identifier is not required to have any association with the IPv4 address space. Note: The value of this object has to be explicitly configured by the user in both cases.A Node Id with 0 is the default value and is not a valid configuration for a operationally active node.

Sources for this description

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

See 1 matching source record

Description 2

This object allows the operator or service provider to assign a unique MPLS-TP Node Identifier. The Node Identifier is assigned within the scope of the Global Identifier or Operator Identifier. The value 0 (or 0.0.0.0 in dotted decimal notation) is reserved and MUST NOT be used. When IPv4 addresses are in use, the value of this object can be derived from the LSR's /32 IPv4 loopback address. Note that, when IP reachability is not needed, the 32-bit Node Identifier is not required to have any association with the IPv4 address space. Note: The value of this object has to be explicitly configured by the user in both cases.

Sources for this description

Belden, GarrettCom and Hirschmann IT official standalone MIBs

See 1 matching source record

Evidence

Source records

2 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

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

Status in source: current.

Names: fsMplsTpNodeIdentifier

Technical details
{
  "smi_kind": "OBJECT-TYPE",
  "definition": [
    "fsMplsTpNodeIdentifier",
    "OBJECT-TYPE",
    "SYNTAX",
    "Unsigned32",
    "MAX-ACCESS",
    "read-write",
    "STATUS",
    "current",
    "DESCRIPTION",
    "\"This object allows the operator or service provider to assign a unique MPLS-TP Node Identifier. The Node Identifier is assigned within the scope of the Global Identifier or Operator Identifier. The value 0 (or 0.0.0.0 in dotted decimal notation) is reserved and MUST NOT be used. When IPv4 addresses are in use, the value of this object can be derived from the LSR's /32 IPv4 loopback address. Note that, when IP reachability is not needed, the 32-bit Node Identifier is not required to have any association with the IPv4 address space. Note: The value of this object has to be explicitly configured by the user in both cases.A Node Id with 0 is the default value and is not a valid configuration for a operationally active node.\"",
    "REFERENCE",
    "\"MPLS-TP Identifiers draft version 02, Section 4\"",
    "DEFVAL",
    "{",
    "0",
    "}",
    "::=",
    "{",
    "fsMplsTpGlobalConfigEntry",
    "5",
    "}"
  ],
  "syntax_tree": [
    [
      "ApplicationSyntax",
      "Unsigned32"
    ],
    null,
    [
      "MaxAccessPart",
      "read-write"
    ],
    [
      "Status",
      "current"
    ],
    [
      "DESCRIPTION",
      "This object allows the operator or service provider to assign a unique MPLS-TP Node Identifier. The Node Identifier is assigned within the scope of the Global Identifier or Operator Identifier. The value 0 (or 0.0.0.0 in dotted decimal notation) is reserved and MUST NOT be used. When IPv4 addresses are in use, the value of this object can be derived from the LSR's /32 IPv4 loopback address. Note that, when IP reachability is not needed, the 32-bit Node Identifier is not required to have any association with the IPv4 address space. Note: The value of this object has to be explicitly configured by the user in both cases.A Node Id with 0 is the default value and is not a valid configuration for a operationally active node."
    ],
    [
      "REFERENCE",
      "MPLS-TP Identifiers draft version 02, Section 4"
    ],
    null,
    null,
    [
      "DEFVAL",
      0
    ]
  ]
}
Records for description 2Belden, GarrettCom and Hirschmann IT official standalone MIBs1 record · 1 source

Description 2

fsMplsTpNodeIdentifier · currentBelden, GarrettCom and Hirschmann IT official standalone MIBs1 source

Status in source: current.

Names: fsMplsTpNodeIdentifier

Technical details
{
  "smi_kind": "OBJECT-TYPE",
  "definition": [
    "fsMplsTpNodeIdentifier",
    "OBJECT-TYPE",
    "SYNTAX",
    "Unsigned32",
    "MAX-ACCESS",
    "read-write",
    "STATUS",
    "current",
    "DESCRIPTION",
    "\"This object allows the operator or service provider to assign a unique MPLS-TP Node Identifier. The Node Identifier is assigned within the scope of the Global Identifier or Operator Identifier. The value 0 (or 0.0.0.0 in dotted decimal notation) is reserved and MUST NOT be used. When IPv4 addresses are in use, the value of this object can be derived from the LSR's /32 IPv4 loopback address. Note that, when IP reachability is not needed, the 32-bit Node Identifier is not required to have any association with the IPv4 address space. Note: The value of this object has to be explicitly configured by the user in both cases.\"",
    "REFERENCE",
    "\"MPLS-TP Identifiers draft version 02, Section 4\"",
    "::=",
    "{",
    "fsMplsTpGlobalConfigEntry",
    "5",
    "}"
  ],
  "syntax_tree": [
    [
      "ApplicationSyntax",
      "Unsigned32"
    ],
    null,
    [
      "MaxAccessPart",
      "read-write"
    ],
    [
      "Status",
      "current"
    ],
    [
      "DESCRIPTION",
      "This object allows the operator or service provider to assign a unique MPLS-TP Node Identifier. The Node Identifier is assigned within the scope of the Global Identifier or Operator Identifier. The value 0 (or 0.0.0.0 in dotted decimal notation) is reserved and MUST NOT be used. When IPv4 addresses are in use, the value of this object can be derived from the LSR's /32 IPv4 loopback address. Note that, when IP reachability is not needed, the 32-bit Node Identifier is not required to have any association with the IPv4 address space. Note: The value of this object has to be explicitly configured by the user in both cases."
    ],
    [
      "REFERENCE",
      "MPLS-TP Identifiers draft version 02, Section 4"
    ],
    null,
    null,
    null
  ]
}

Registration

Registration authorities

First Registration Authority (inferred from ancestor 1.3.6.1.4.1.2076)

Division Products

Siblings (7)

OIDNameDirect childrenDescendantsDescription
1.3.6.1.4.1.2076.13.8.1.2.1.1 fsMplsTpContextId00
1.3.6.1.4.1.2076.13.8.1.2.1.2 fsMplsTpOamModuleStatus00
1.3.6.1.4.1.2076.13.8.1.2.1.3 fsMplsTpGlobalId00
1.3.6.1.4.1.2076.13.8.1.2.1.4 fsMplsTpIcc00
1.3.6.1.4.1.2076.13.8.1.2.1.6 fsMplsTpErrorCode00
1.3.6.1.4.1.2076.13.8.1.2.1.7 fsMplsTpTraceLevel00
1.3.6.1.4.1.2076.13.8.1.2.1.8 fsMplsTpNotificationEnable00