OID reference

vRtrLdpNgAddrFecCommMismatch

1.3.6.1.4.1.6527.3.1.3.91.0.11

Description

[CAUSE] A vRtrLdpNgAddrFecCommMismatch notification is generated when two or more peer routers advertising labels for the given address FEC have been assigned differing communities, or some have been assigned communities and some have not. It will also be generated if multiple LDP peer routers have been configured to …

Full description and source information

Identification

Identifier and names

Parent
1.3.6.1.4.1.6527.3.1.3.91.0 (tmnxLdpNgNotifications)
Node code
11
Node name
vRtrLdpNgAddrFecCommMismatch
Category
SNMP notification
Numeric OID
1.3.6.1.4.1.6527.3.1.3.91.0.11
URN notation
urn:oid:1.3.6.1.4.1.6527.3.1.3.91.0.11
ASN.1, OID-IRI and named path variants
ASN.1 notation

{1 3 6 1 4 1 6527 3 1 3 91 0 11}

  • {iso(1) identified-organization(3) dod(6) internet(1) private(4) enterprise(1) timetra(6527) timetraProducts(3) tmnxSRMIB(1) tmnxSRNotifyPrefix(3) tmnxLdpNgNotifyPrefix(91) tmnxLdpNgNotifications(0) vRtrLdpNgAddrFecCommMismatch(11)}
  • {iso(1) identified-organization(3) dod(6) internet(1) private(4) enterprises(1) timetra(6527) timetraProducts(3) tmnxSRMIB(1) tmnxSRNotifyPrefix(3) tmnxLdpNgNotifyPrefix(91) tmnxLdpNgNotifications(0) vRtrLdpNgAddrFecCommMismatch(11)}
  • {iso(1) identified-organization(3) dod(6) internet(1) private(4) ldap-enterprise(1) timetra(6527) timetraProducts(3) tmnxSRMIB(1) tmnxSRNotifyPrefix(3) tmnxLdpNgNotifyPrefix(91) tmnxLdpNgNotifications(0) vRtrLdpNgAddrFecCommMismatch(11)}
  • {iso(1) identified-organization(3) dod(6) internet(1) private(4) vendor-objects(1) timetra(6527) timetraProducts(3) tmnxSRMIB(1) tmnxSRNotifyPrefix(3) tmnxLdpNgNotifyPrefix(91) tmnxLdpNgNotifications(0) vRtrLdpNgAddrFecCommMismatch(11)}
  • {iso(1) org(3) dod(6) internet(1) private(4) enterprise(1) timetra(6527) timetraProducts(3) tmnxSRMIB(1) tmnxSRNotifyPrefix(3) tmnxLdpNgNotifyPrefix(91) tmnxLdpNgNotifications(0) vRtrLdpNgAddrFecCommMismatch(11)}
  • {iso(1) org(3) dod(6) internet(1) private(4) enterprises(1) timetra(6527) timetraProducts(3) tmnxSRMIB(1) tmnxSRNotifyPrefix(3) tmnxLdpNgNotifyPrefix(91) tmnxLdpNgNotifications(0) vRtrLdpNgAddrFecCommMismatch(11)}
  • {iso(1) org(3) dod(6) internet(1) private(4) ldap-enterprise(1) timetra(6527) timetraProducts(3) tmnxSRMIB(1) tmnxSRNotifyPrefix(3) tmnxLdpNgNotifyPrefix(91) tmnxLdpNgNotifications(0) vRtrLdpNgAddrFecCommMismatch(11)}
  • {iso(1) org(3) dod(6) internet(1) private(4) vendor-objects(1) timetra(6527) timetraProducts(3) tmnxSRMIB(1) tmnxSRNotifyPrefix(3) tmnxLdpNgNotifyPrefix(91) tmnxLdpNgNotifications(0) vRtrLdpNgAddrFecCommMismatch(11)}
  • {iso(1) iso-identified-organization(3) dod(6) internet(1) private(4) enterprise(1) timetra(6527) timetraProducts(3) tmnxSRMIB(1) tmnxSRNotifyPrefix(3) tmnxLdpNgNotifyPrefix(91) tmnxLdpNgNotifications(0) vRtrLdpNgAddrFecCommMismatch(11)}
  • {iso(1) iso-identified-organization(3) dod(6) internet(1) private(4) enterprises(1) timetra(6527) timetraProducts(3) tmnxSRMIB(1) tmnxSRNotifyPrefix(3) tmnxLdpNgNotifyPrefix(91) tmnxLdpNgNotifications(0) vRtrLdpNgAddrFecCommMismatch(11)}
  • {iso(1) iso-identified-organization(3) dod(6) internet(1) private(4) ldap-enterprise(1) timetra(6527) timetraProducts(3) tmnxSRMIB(1) tmnxSRNotifyPrefix(3) tmnxLdpNgNotifyPrefix(91) tmnxLdpNgNotifications(0) vRtrLdpNgAddrFecCommMismatch(11)}
  • {iso(1) iso-identified-organization(3) dod(6) internet(1) private(4) vendor-objects(1) timetra(6527) timetraProducts(3) tmnxSRMIB(1) tmnxSRNotifyPrefix(3) tmnxLdpNgNotifyPrefix(91) tmnxLdpNgNotifications(0) vRtrLdpNgAddrFecCommMismatch(11)}
  • {iso(1) iso-organization(3) dod(6) internet(1) private(4) enterprise(1) timetra(6527) timetraProducts(3) tmnxSRMIB(1) tmnxSRNotifyPrefix(3) tmnxLdpNgNotifyPrefix(91) tmnxLdpNgNotifications(0) vRtrLdpNgAddrFecCommMismatch(11)}
  • {iso(1) iso-organization(3) dod(6) internet(1) private(4) enterprises(1) timetra(6527) timetraProducts(3) tmnxSRMIB(1) tmnxSRNotifyPrefix(3) tmnxLdpNgNotifyPrefix(91) tmnxLdpNgNotifications(0) vRtrLdpNgAddrFecCommMismatch(11)}
  • {iso(1) iso-organization(3) dod(6) internet(1) private(4) ldap-enterprise(1) timetra(6527) timetraProducts(3) tmnxSRMIB(1) tmnxSRNotifyPrefix(3) tmnxLdpNgNotifyPrefix(91) tmnxLdpNgNotifications(0) vRtrLdpNgAddrFecCommMismatch(11)}
  • {iso(1) iso-organization(3) dod(6) internet(1) private(4) vendor-objects(1) timetra(6527) timetraProducts(3) tmnxSRMIB(1) tmnxSRNotifyPrefix(3) tmnxLdpNgNotifyPrefix(91) tmnxLdpNgNotifications(0) vRtrLdpNgAddrFecCommMismatch(11)}
OID-IRI notation
  • /1/3/6/1/4/1/6527/3/1/3/91/0/11
  • /ISO/Identified-Organization/6/1/4/1/6527/3/1/3/91/0/11
  • /ISO/3/6/1/4/1/6527/3/1/3/91/0/11
Named path variants
  • /iso/identified-organization/dod/internet/private/enterprise/timetra/timetraProducts/tmnxSRMIB/tmnxSRNotifyPrefix/tmnxLdpNgNotifyPrefix/tmnxLdpNgNotifications/vRtrLdpNgAddrFecCommMismatch
  • /iso/identified-organization/dod/internet/private/enterprises/timetra/timetraProducts/tmnxSRMIB/tmnxSRNotifyPrefix/tmnxLdpNgNotifyPrefix/tmnxLdpNgNotifications/vRtrLdpNgAddrFecCommMismatch
  • /iso/identified-organization/dod/internet/private/ldap-enterprise/timetra/timetraProducts/tmnxSRMIB/tmnxSRNotifyPrefix/tmnxLdpNgNotifyPrefix/tmnxLdpNgNotifications/vRtrLdpNgAddrFecCommMismatch
  • /iso/identified-organization/dod/internet/private/vendor-objects/timetra/timetraProducts/tmnxSRMIB/tmnxSRNotifyPrefix/tmnxLdpNgNotifyPrefix/tmnxLdpNgNotifications/vRtrLdpNgAddrFecCommMismatch
  • /iso/org/dod/internet/private/enterprise/timetra/timetraProducts/tmnxSRMIB/tmnxSRNotifyPrefix/tmnxLdpNgNotifyPrefix/tmnxLdpNgNotifications/vRtrLdpNgAddrFecCommMismatch
  • /iso/org/dod/internet/private/enterprises/timetra/timetraProducts/tmnxSRMIB/tmnxSRNotifyPrefix/tmnxLdpNgNotifyPrefix/tmnxLdpNgNotifications/vRtrLdpNgAddrFecCommMismatch
  • /iso/org/dod/internet/private/ldap-enterprise/timetra/timetraProducts/tmnxSRMIB/tmnxSRNotifyPrefix/tmnxLdpNgNotifyPrefix/tmnxLdpNgNotifications/vRtrLdpNgAddrFecCommMismatch
  • /iso/org/dod/internet/private/vendor-objects/timetra/timetraProducts/tmnxSRMIB/tmnxSRNotifyPrefix/tmnxLdpNgNotifyPrefix/tmnxLdpNgNotifications/vRtrLdpNgAddrFecCommMismatch
  • /iso/iso-identified-organization/dod/internet/private/enterprise/timetra/timetraProducts/tmnxSRMIB/tmnxSRNotifyPrefix/tmnxLdpNgNotifyPrefix/tmnxLdpNgNotifications/vRtrLdpNgAddrFecCommMismatch
  • /iso/iso-identified-organization/dod/internet/private/enterprises/timetra/timetraProducts/tmnxSRMIB/tmnxSRNotifyPrefix/tmnxLdpNgNotifyPrefix/tmnxLdpNgNotifications/vRtrLdpNgAddrFecCommMismatch
  • /iso/iso-identified-organization/dod/internet/private/ldap-enterprise/timetra/timetraProducts/tmnxSRMIB/tmnxSRNotifyPrefix/tmnxLdpNgNotifyPrefix/tmnxLdpNgNotifications/vRtrLdpNgAddrFecCommMismatch
  • /iso/iso-identified-organization/dod/internet/private/vendor-objects/timetra/timetraProducts/tmnxSRMIB/tmnxSRNotifyPrefix/tmnxLdpNgNotifyPrefix/tmnxLdpNgNotifications/vRtrLdpNgAddrFecCommMismatch
  • /iso/iso-organization/dod/internet/private/enterprise/timetra/timetraProducts/tmnxSRMIB/tmnxSRNotifyPrefix/tmnxLdpNgNotifyPrefix/tmnxLdpNgNotifications/vRtrLdpNgAddrFecCommMismatch
  • /iso/iso-organization/dod/internet/private/enterprises/timetra/timetraProducts/tmnxSRMIB/tmnxSRNotifyPrefix/tmnxLdpNgNotifyPrefix/tmnxLdpNgNotifications/vRtrLdpNgAddrFecCommMismatch
  • /iso/iso-organization/dod/internet/private/ldap-enterprise/timetra/timetraProducts/tmnxSRMIB/tmnxSRNotifyPrefix/tmnxLdpNgNotifyPrefix/tmnxLdpNgNotifications/vRtrLdpNgAddrFecCommMismatch
  • /iso/iso-organization/dod/internet/private/vendor-objects/timetra/timetraProducts/tmnxSRMIB/tmnxSRNotifyPrefix/tmnxLdpNgNotifyPrefix/tmnxLdpNgNotifications/vRtrLdpNgAddrFecCommMismatch

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

vRtrLdpNgAddrFecCommMismatch     NOTIFICATION-TYPE
    OBJECTS     {
        vRtrID,
        vRtrLdpNgAddrFecCommunity
    }
    STATUS      current
    DESCRIPTION
        "[CAUSE] A vRtrLdpNgAddrFecCommMismatch notification is generated when
         two or more peer routers advertising labels for the given address FEC
         have been assigned differing communities, or some have been assigned
         communities and some have not.  It will also be generated if multiple
         LDP peer routers have been configured to advertise their local LSR-ID
         as a FEC, and those peer routers have been assigned differing communities.
         This notification is rate-limited to at most one notification every 60 seconds.

         [EFFECT] This condition indicates that the network is misconfigured,
         and it is likely that the affected address FEC is not being advertised
         to the routers which the operator intends.

         [RECOVERY] Analyze, check and fix the community configuration for all
         LDP session-parameters and LDP targeted-session peer-templates in the
         network to find the error.  Start with the configuration on the router
         generating the notification, and if this is correct, look next at the
         routers advertising the labels to see if their configuration is correct."
    ::= { tmnxLdpNgNotifications 11 }

Meaning

Descriptions

1 unique

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

[CAUSE] A vRtrLdpNgAddrFecCommMismatch notification is generated when two or more peer routers advertising labels for the given address FEC have been assigned differing communities, or some have been assigned communities and some have not. It will also be generated if multiple LDP peer routers have been configured to advertise their local LSR-ID as a FEC, and those peer routers have been assigned differing communities. This notification is rate-limited to at most one notification every 60 seconds. [EFFECT] This condition indicates that the network is misconfigured, and it is likely that the affected address FEC is not being advertised to the routers which the operator intends. [RECOVERY] Analyze, check and fix the community configuration for all LDP session-parameters and LDP targeted-session peer-templates in the network to find the error. Start with the configuration on the router generating the notification, and if this is correct, look next at the routers advertising the labels to see if their configuration is correct.

Sources for this description

Nokia networking 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 1Nokia networking MIB copies (LibreNMS/Observium Community)1 record · 1 source

Description 1

vRtrLdpNgAddrFecCommMismatch · currentNokia networking MIB copies (LibreNMS/Observium Community)1 source

Status in source: current.

Names: vRtrLdpNgAddrFecCommMismatch

Technical details
{
  "smi_kind": "NOTIFICATION-TYPE",
  "definition": [
    "vRtrLdpNgAddrFecCommMismatch",
    "NOTIFICATION-TYPE",
    "OBJECTS",
    "{",
    "vRtrID",
    ",",
    "vRtrLdpNgAddrFecCommunity",
    "}",
    "STATUS",
    "current",
    "DESCRIPTION",
    "\"[CAUSE] A vRtrLdpNgAddrFecCommMismatch notification is generated when two or more peer routers advertising labels for the given address FEC have been assigned differing communities, or some have been assigned communities and some have not. It will also be generated if multiple LDP peer routers have been configured to advertise their local LSR-ID as a FEC, and those peer routers have been assigned differing communities. This notification is rate-limited to at most one notification every 60 seconds. [EFFECT] This condition indicates that the network is misconfigured, and it is likely that the affected address FEC is not being advertised to the routers which the operator intends. [RECOVERY] Analyze, check and fix the community configuration for all LDP session-parameters and LDP targeted-session peer-templates in the network to find the error. Start with the configuration on the router generating the notification, and if this is correct, look next at the routers advertising the labels to see if their configuration is correct.\"",
    "::=",
    "{",
    "tmnxLdpNgNotifications",
    "11",
    "}"
  ],
  "syntax_tree": [
    [
      "Objects",
      [
        "vRtrID",
        "vRtrLdpNgAddrFecCommunity"
      ]
    ],
    [
      "Status",
      "current"
    ],
    [
      "DESCRIPTION",
      "[CAUSE] A vRtrLdpNgAddrFecCommMismatch notification is generated when two or more peer routers advertising labels for the given address FEC have been assigned differing communities, or some have been assigned communities and some have not. It will also be generated if multiple LDP peer routers have been configured to advertise their local LSR-ID as a FEC, and those peer routers have been assigned differing communities. This notification is rate-limited to at most one notification every 60 seconds. [EFFECT] This condition indicates that the network is misconfigured, and it is likely that the affected address FEC is not being advertised to the routers which the operator intends. [RECOVERY] Analyze, check and fix the community configuration for all LDP session-parameters and LDP targeted-session peer-templates in the network to find the error. Start with the configuration on the router generating the notification, and if this is correct, look next at the routers advertising the labels to see if their configuration is correct."
    ],
    null
  ]
}
  • Nokia networking MIB copies (LibreNMS/Observium Community) · Publisher's source file: Source package: observium-community-latest.tar.gz

    Vendor MIB copy from the Observium Community archive. Nokia support.

    Module: TIMETRA-LDP-NG-MIB

    See published definition above

    Module imports
    {'IF-MIB': ['InterfaceIndexOrZero'], 'SNMPv2-TC': ['DisplayString', 'RowStatus', 'TimeInterval', 'TimeStamp', 'TruthValue'], 'SNMPv2-SMI': ['Counter32', 'Gauge32', 'Integer32', 'MODULE-IDENTITY', 'NOTIFICATION-TYPE', 'OBJECT-TYPE', 'Unsigned32'], 'SNMPv2-CONF': ['MODULE-COMPLIANCE', 'NOTIFICATION-GROUP', 'OBJECT-GROUP'], 'MPLS-LDP-MIB': ['MplsLsrIdentifier'], 'TIMETRA-TC-MIB': ['TNamedItem', 'TNamedItemOrEmpty', 'TPolicyStatementNameOrEmpty', 'TmnxAddressAndPrefixAddress', 'TmnxAddressAndPrefixPrefix', 'TmnxAddressAndPrefixType', 'TmnxAdminState', 'TmnxCBFClasses', 'TmnxEnabledDisabled', 'TmnxLdpFECType', 'TmnxMplsLdpNgIdType', 'TmnxMplsLdpNgIdentifier', 'TmnxMplsLsrNgIdentifier', 'TmnxOperState', 'TmnxServId', 'TmnxVRtrMplsLspID', 'TmnxVcId', 'TmnxVcIdOrNone', 'TmnxVcType'], 'TIMETRA-LDP-MIB': ['TmnxLabelSigStatus', 'TmnxLabelStatus', 'TmnxLdpAdjacencyType', 'TmnxLdpBackoffTime', 'TmnxLdpFECFlags', 'TmnxLdpFECPolicy', 'TmnxLdpGenOperDownReasonCode', 'TmnxLdpHelloFactor', 'TmnxLdpHelloTimeout', 'TmnxLdpInLblWdrawalReasonCode', 'TmnxLdpIntTargOperDownReasonCode', 'TmnxLdpKeepAliveFactor', 'TmnxLdpLabelDistMethod', 'TmnxLdpNewHelloTimeout', 'TmnxLdpNewKeepAliveTimeout', 'TmnxVpnId'], 'INET-ADDRESS-MIB': ['InetAddress', 'InetAddressPrefixLength', 'InetAddressType', 'InetVersion'], 'TIMETRA-SERV-MIB': ['SdpId', 'ServType', 'TdmOptionsCasTrunkFraming', 'TdmOptionsSigPkts'], 'TIMETRA-VRTR-MIB': ['vRtrID'], 'TIMETRA-GLOBAL-MIB': ['timetraSRMIBModules', 'tmnxSRConfs', 'tmnxSRNotifyPrefix', 'tmnxSRObjs']}
    · Download TIMETRA-LDP-NG-MIB

    Related source files and packages:

Registration

Registration authorities

First Registration Authority (inferred from ancestor 1.3.6.1.4.1.6527)

Marcelo Mourier

Current Registration Authority (inferred from ancestor 1.3.6.1.4.1.6527)

Jason Sterne

Siblings (9)

OIDNameDirect childrenDescendantsDescription
1.3.6.1.4.1.6527.3.1.3.91.0.1 vRtrLdpNgIpv4InstStateChange00
1.3.6.1.4.1.6527.3.1.3.91.0.2 vRtrLdpNgIpv6InstStateChange00
1.3.6.1.4.1.6527.3.1.3.91.0.3 vRtrLdpNgIfStateChange00
1.3.6.1.4.1.6527.3.1.3.91.0.4 vRtrLdpNgInetIfStateChange00
1.3.6.1.4.1.6527.3.1.3.91.0.5 vRtrLdpNgTargPeerStateChange00
1.3.6.1.4.1.6527.3.1.3.91.0.6 vRtrLdpNgSessionStateChange00
1.3.6.1.4.1.6527.3.1.3.91.0.7 vRtrLdpNgSessMaxFecThresChanged00
1.3.6.1.4.1.6527.3.1.3.91.0.8 vRtrLdpNgSessMaxFecLimitReached00
1.3.6.1.4.1.6527.3.1.3.91.0.9 vRtrLdpNgResourceExhaustion00