OID reference

ospfPmEntVpnRouteTag

1.3.6.1.4.1.629.10.3.1.1.1.51

Description

The VPN route tag used for loop detection as part of OSPF PE-CE protocol function. This field is only used if ospfPmEntVpnPeCeSupport is true. If this field is set to zero then VPN route tag function is disabled. VPN route tag function is specified in RFC 4577, and VPN route tag configuration is described in sections …

Full description and source information

Identification

Identifier and names

Parent
1.3.6.1.4.1.629.10.3.1.1.1 (ospfPmEntEntry)
Node code
51
Node name
ospfPmEntVpnRouteTag
Category
SNMP management object
Numeric OID
1.3.6.1.4.1.629.10.3.1.1.1.51
URN notation
urn:oid:1.3.6.1.4.1.629.10.3.1.1.1.51
ASN.1, OID-IRI and named path variants
ASN.1 notation

{1 3 6 1 4 1 629 10 3 1 1 1 51}

  • {iso(1) identified-organization(3) dod(6) internet(1) private(4) enterprise(1) nbase(629) opx(10) ospfMib(3) ospfObjects(1) ospfPmEntTable(1) ospfPmEntEntry(1) ospfPmEntVpnRouteTag(51)}
  • {iso(1) identified-organization(3) dod(6) internet(1) private(4) enterprise(1) nbs(629) opx(10) ospfMib(3) ospfObjects(1) ospfPmEntTable(1) ospfPmEntEntry(1) ospfPmEntVpnRouteTag(51)}
  • {iso(1) identified-organization(3) dod(6) internet(1) private(4) enterprises(1) nbase(629) opx(10) ospfMib(3) ospfObjects(1) ospfPmEntTable(1) ospfPmEntEntry(1) ospfPmEntVpnRouteTag(51)}
  • {iso(1) identified-organization(3) dod(6) internet(1) private(4) enterprises(1) nbs(629) opx(10) ospfMib(3) ospfObjects(1) ospfPmEntTable(1) ospfPmEntEntry(1) ospfPmEntVpnRouteTag(51)}
  • {iso(1) identified-organization(3) dod(6) internet(1) private(4) ldap-enterprise(1) nbase(629) opx(10) ospfMib(3) ospfObjects(1) ospfPmEntTable(1) ospfPmEntEntry(1) ospfPmEntVpnRouteTag(51)}
  • {iso(1) identified-organization(3) dod(6) internet(1) private(4) ldap-enterprise(1) nbs(629) opx(10) ospfMib(3) ospfObjects(1) ospfPmEntTable(1) ospfPmEntEntry(1) ospfPmEntVpnRouteTag(51)}
  • {iso(1) identified-organization(3) dod(6) internet(1) private(4) vendor-objects(1) nbase(629) opx(10) ospfMib(3) ospfObjects(1) ospfPmEntTable(1) ospfPmEntEntry(1) ospfPmEntVpnRouteTag(51)}
  • {iso(1) identified-organization(3) dod(6) internet(1) private(4) vendor-objects(1) nbs(629) opx(10) ospfMib(3) ospfObjects(1) ospfPmEntTable(1) ospfPmEntEntry(1) ospfPmEntVpnRouteTag(51)}
  • {iso(1) org(3) dod(6) internet(1) private(4) enterprise(1) nbase(629) opx(10) ospfMib(3) ospfObjects(1) ospfPmEntTable(1) ospfPmEntEntry(1) ospfPmEntVpnRouteTag(51)}
  • {iso(1) org(3) dod(6) internet(1) private(4) enterprise(1) nbs(629) opx(10) ospfMib(3) ospfObjects(1) ospfPmEntTable(1) ospfPmEntEntry(1) ospfPmEntVpnRouteTag(51)}
  • {iso(1) org(3) dod(6) internet(1) private(4) enterprises(1) nbase(629) opx(10) ospfMib(3) ospfObjects(1) ospfPmEntTable(1) ospfPmEntEntry(1) ospfPmEntVpnRouteTag(51)}
  • {iso(1) org(3) dod(6) internet(1) private(4) enterprises(1) nbs(629) opx(10) ospfMib(3) ospfObjects(1) ospfPmEntTable(1) ospfPmEntEntry(1) ospfPmEntVpnRouteTag(51)}
  • {iso(1) org(3) dod(6) internet(1) private(4) ldap-enterprise(1) nbase(629) opx(10) ospfMib(3) ospfObjects(1) ospfPmEntTable(1) ospfPmEntEntry(1) ospfPmEntVpnRouteTag(51)}
  • {iso(1) org(3) dod(6) internet(1) private(4) ldap-enterprise(1) nbs(629) opx(10) ospfMib(3) ospfObjects(1) ospfPmEntTable(1) ospfPmEntEntry(1) ospfPmEntVpnRouteTag(51)}
  • {iso(1) org(3) dod(6) internet(1) private(4) vendor-objects(1) nbase(629) opx(10) ospfMib(3) ospfObjects(1) ospfPmEntTable(1) ospfPmEntEntry(1) ospfPmEntVpnRouteTag(51)}
  • {iso(1) org(3) dod(6) internet(1) private(4) vendor-objects(1) nbs(629) opx(10) ospfMib(3) ospfObjects(1) ospfPmEntTable(1) ospfPmEntEntry(1) ospfPmEntVpnRouteTag(51)}
  • Additional combinations skipped.
OID-IRI notation
  • /1/3/6/1/4/1/629/10/3/1/1/1/51
  • /ISO/Identified-Organization/6/1/4/1/629/10/3/1/1/1/51
  • /ISO/3/6/1/4/1/629/10/3/1/1/1/51
Named path variants
  • /iso/identified-organization/dod/internet/private/enterprise/nbase/opx/ospfMib/ospfObjects/ospfPmEntTable/ospfPmEntEntry/ospfPmEntVpnRouteTag
  • /iso/identified-organization/dod/internet/private/enterprise/nbs/opx/ospfMib/ospfObjects/ospfPmEntTable/ospfPmEntEntry/ospfPmEntVpnRouteTag
  • /iso/identified-organization/dod/internet/private/enterprises/nbase/opx/ospfMib/ospfObjects/ospfPmEntTable/ospfPmEntEntry/ospfPmEntVpnRouteTag
  • /iso/identified-organization/dod/internet/private/enterprises/nbs/opx/ospfMib/ospfObjects/ospfPmEntTable/ospfPmEntEntry/ospfPmEntVpnRouteTag
  • /iso/identified-organization/dod/internet/private/ldap-enterprise/nbase/opx/ospfMib/ospfObjects/ospfPmEntTable/ospfPmEntEntry/ospfPmEntVpnRouteTag
  • /iso/identified-organization/dod/internet/private/ldap-enterprise/nbs/opx/ospfMib/ospfObjects/ospfPmEntTable/ospfPmEntEntry/ospfPmEntVpnRouteTag
  • /iso/identified-organization/dod/internet/private/vendor-objects/nbase/opx/ospfMib/ospfObjects/ospfPmEntTable/ospfPmEntEntry/ospfPmEntVpnRouteTag
  • /iso/identified-organization/dod/internet/private/vendor-objects/nbs/opx/ospfMib/ospfObjects/ospfPmEntTable/ospfPmEntEntry/ospfPmEntVpnRouteTag
  • /iso/org/dod/internet/private/enterprise/nbase/opx/ospfMib/ospfObjects/ospfPmEntTable/ospfPmEntEntry/ospfPmEntVpnRouteTag
  • /iso/org/dod/internet/private/enterprise/nbs/opx/ospfMib/ospfObjects/ospfPmEntTable/ospfPmEntEntry/ospfPmEntVpnRouteTag
  • /iso/org/dod/internet/private/enterprises/nbase/opx/ospfMib/ospfObjects/ospfPmEntTable/ospfPmEntEntry/ospfPmEntVpnRouteTag
  • /iso/org/dod/internet/private/enterprises/nbs/opx/ospfMib/ospfObjects/ospfPmEntTable/ospfPmEntEntry/ospfPmEntVpnRouteTag
  • /iso/org/dod/internet/private/ldap-enterprise/nbase/opx/ospfMib/ospfObjects/ospfPmEntTable/ospfPmEntEntry/ospfPmEntVpnRouteTag
  • /iso/org/dod/internet/private/ldap-enterprise/nbs/opx/ospfMib/ospfObjects/ospfPmEntTable/ospfPmEntEntry/ospfPmEntVpnRouteTag
  • /iso/org/dod/internet/private/vendor-objects/nbase/opx/ospfMib/ospfObjects/ospfPmEntTable/ospfPmEntEntry/ospfPmEntVpnRouteTag
  • /iso/org/dod/internet/private/vendor-objects/nbs/opx/ospfMib/ospfObjects/ospfPmEntTable/ospfPmEntEntry/ospfPmEntVpnRouteTag
  • Additional combinations skipped.

SNMP properties

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

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: ospfPmEntIndex.

snmpwalk [connection options] DEVICE .1.3.6.1.4.1.629.10.3.1.1.1.51

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.

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

ospfPmEntVpnRouteTag OBJECT-TYPE
       SYNTAX       Unsigned32
       MAX-ACCESS   read-create
       STATUS       current
       DESCRIPTION
          "The VPN route tag used for loop detection as part of OSPF
           PE-CE protocol function.

           This field is only used if ospfPmEntVpnPeCeSupport is
           true.

           If this field is set to zero then VPN route tag function
           is disabled.

           VPN route tag function is specified in RFC 4577, and
           VPN route tag configuration is described in sections
           4.2.5.1 and 4.2.5.2.

           In particular RFC 4577 sectios 4.2.5.1 and 4.2.5.2 state
           the following.

           - If OSPF PE-CE protocol function is enabled then by
             default a VPN route tag MUST be configured.

           - If the Autonomous System number of the VPN backbone is
             two bytes long, the VPN route tag SHOULD be set to
             0xD000nnnn where nnnn is the AS number of the VPN
             backbone.

           - When it is no longer necessary to use the VPN Route Tag
             in a particular deployment, its use (both sending and
             receiving) may be disabled by configuration.

           If ospfPmEntVpnRouteTag is non-zero then it overrides any
           OSPF tag supplied with a redistributed route.
           In particular, it overrides any OSPF tag specified by
           rtmRedistNwOspfTag in the rtmRedistTable MIB for this OSPF
           instance."
       DEFVAL { 0 }
       ::= { ospfPmEntEntry 51 }

Meaning

Descriptions

1 unique

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

The VPN route tag used for loop detection as part of OSPF PE-CE protocol function. This field is only used if ospfPmEntVpnPeCeSupport is true. If this field is set to zero then VPN route tag function is disabled. VPN route tag function is specified in RFC 4577, and VPN route tag configuration is described in sections 4.2.5.1 and 4.2.5.2. In particular RFC 4577 sectios 4.2.5.1 and 4.2.5.2 state the following. - If OSPF PE-CE protocol function is enabled then by default a VPN route tag MUST be configured. - If the Autonomous System number of the VPN backbone is two bytes long, the VPN route tag SHOULD be set to 0xD000nnnn where nnnn is the AS number of the VPN backbone. - When it is no longer necessary to use the VPN Route Tag in a particular deployment, its use (both sending and receiving) may be disabled by configuration. If ospfPmEntVpnRouteTag is non-zero then it overrides any OSPF tag supplied with a redistributed route. In particular, it overrides any OSPF tag specified by rtmRedistNwOspfTag in the rtmRedistTable MIB for this OSPF instance.

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

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

Status in source: current.

Names: ospfPmEntVpnRouteTag

Technical details
{
  "smi_kind": "OBJECT-TYPE",
  "definition": [
    "ospfPmEntVpnRouteTag",
    "OBJECT-TYPE",
    "SYNTAX",
    "Unsigned32",
    "MAX-ACCESS",
    "read-create",
    "STATUS",
    "current",
    "DESCRIPTION",
    "\"The VPN route tag used for loop detection as part of OSPF PE-CE protocol function. This field is only used if ospfPmEntVpnPeCeSupport is true. If this field is set to zero then VPN route tag function is disabled. VPN route tag function is specified in RFC 4577, and VPN route tag configuration is described in sections 4.2.5.1 and 4.2.5.2. In particular RFC 4577 sectios 4.2.5.1 and 4.2.5.2 state the following. - If OSPF PE-CE protocol function is enabled then by default a VPN route tag MUST be configured. - If the Autonomous System number of the VPN backbone is two bytes long, the VPN route tag SHOULD be set to 0xD000nnnn where nnnn is the AS number of the VPN backbone. - When it is no longer necessary to use the VPN Route Tag in a particular deployment, its use (both sending and receiving) may be disabled by configuration. If ospfPmEntVpnRouteTag is non-zero then it overrides any OSPF tag supplied with a redistributed route. In particular, it overrides any OSPF tag specified by rtmRedistNwOspfTag in the rtmRedistTable MIB for this OSPF instance.\"",
    "DEFVAL",
    "{",
    "0",
    "}",
    "::=",
    "{",
    "ospfPmEntEntry",
    "51",
    "}"
  ],
  "syntax_tree": [
    [
      "ApplicationSyntax",
      "Unsigned32"
    ],
    null,
    [
      "MaxAccessPart",
      "read-create"
    ],
    [
      "Status",
      "current"
    ],
    [
      "DESCRIPTION",
      "The VPN route tag used for loop detection as part of OSPF PE-CE protocol function. This field is only used if ospfPmEntVpnPeCeSupport is true. If this field is set to zero then VPN route tag function is disabled. VPN route tag function is specified in RFC 4577, and VPN route tag configuration is described in sections 4.2.5.1 and 4.2.5.2. In particular RFC 4577 sectios 4.2.5.1 and 4.2.5.2 state the following. - If OSPF PE-CE protocol function is enabled then by default a VPN route tag MUST be configured. - If the Autonomous System number of the VPN backbone is two bytes long, the VPN route tag SHOULD be set to 0xD000nnnn where nnnn is the AS number of the VPN backbone. - When it is no longer necessary to use the VPN Route Tag in a particular deployment, its use (both sending and receiving) may be disabled by configuration. If ospfPmEntVpnRouteTag is non-zero then it overrides any OSPF tag supplied with a redistributed route. In particular, it overrides any OSPF tag specified by rtmRedistNwOspfTag in the rtmRedistTable MIB for this OSPF instance."
    ],
    null,
    null,
    null,
    [
      "DEFVAL",
      0
    ]
  ]
}

Registration

Registration authorities

First Registration Authority (inferred from ancestor 1.3.6.1.4.1.629)

Rotenstein Sergiu

Siblings (60)

OIDNameDirect childrenDescendantsDescription
1.3.6.1.4.1.629.10.3.1.1.1.52 ospfPmEntVpnRouterIdAttr00
1.3.6.1.4.1.629.10.3.1.1.1.53 ospfPmEntDfltExtType1Metric00
1.3.6.1.4.1.629.10.3.1.1.1.54 ospfPmEntDfltExtType2Metric00
1.3.6.1.4.1.629.10.3.1.1.1.55 ospfPmEntRtmPurgeTime00
1.3.6.1.4.1.629.10.3.1.1.1.56 ospfPmEntMinLsInterval00
1.3.6.1.4.1.629.10.3.1.1.1.57 ospfPmEntMinLsArrival00
1.3.6.1.4.1.629.10.3.1.1.1.58 ospfPmEntVpnDfltShamLinkMetric00
1.3.6.1.4.1.629.10.3.1.1.1.59 ospfPmEntInstanceId00
1.3.6.1.4.1.629.10.3.1.1.1.60 ospfPmEntStatsReset00
1.3.6.1.4.1.629.10.3.1.1.1.61 ospfPmEntEnableTrapSupport00