OID reference

vRtrLdpSessMaxFecLimitReached

1.3.6.1.4.1.6527.3.1.3.8.0.8

Description

[CAUSE] A vRtrLdpSessMaxFecLimitReached notification is generated when the number of FECs accepted from the peer has reached the value specified by vRtrLdpPeerMaxFec. If the current number of FECs go below the limit but higher than the configured threshold and again start to increase and hit the limit a second time, w…

Full description and source information

Identification

Identifier and names

Parent
1.3.6.1.4.1.6527.3.1.3.8.0 (tmnxLdpNotifications)
Node code
8
Node name
vRtrLdpSessMaxFecLimitReached
Category
SNMP notification
Numeric OID
1.3.6.1.4.1.6527.3.1.3.8.0.8
URN notation
urn:oid:1.3.6.1.4.1.6527.3.1.3.8.0.8
ASN.1, OID-IRI and named path variants
ASN.1 notation

{1 3 6 1 4 1 6527 3 1 3 8 0 8}

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

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

Show 2 published definitions

vRtrLdpSessMaxFecLimitReached · obsolete

vRtrLdpSessMaxFecLimitReached    NOTIFICATION-TYPE
    OBJECTS     {
        vRtrLdpPeerMaxFec,
        vRtrLdpSessOperMaxFecThreshold
    }
    STATUS      obsolete
    DESCRIPTION
        "[CAUSE] A vRtrLdpSessMaxFecLimitReached notification is generated when
         the number of FECs accepted from the peer has reached the value
         specified by vRtrLdpPeerMaxFec.

         If the current number of FECs go below the limit but higher than the
         configured threshold and again start to increase and hit the limit a
         second time, we will raise a trap if 2 or more minutes have elapsed
         since the first vRtrLdpSessMaxFecLimitReached trap was sent.

         If any parameter in FEC limit configuration changes and the current
         number of FECs are equal to or higher than the limit specified by
         vRtrLdpPeerMaxFec, then we would always raise the
         vRtrLdpSessMaxFecLimitReached trap.

         [EFFECT] When the number of FECs exceed the configured maximum
         (vRtrLdpPeerMaxFec) it results in any of the following:

         (1) If vRtrLdpPeerMaxFecLogOnly is set to 'false' and LSR Overload
         Capability is supported, then Overload procedure will take place.

         (2) If vRtrLdpPeerMaxFecLogOnly is set to 'false' and LSR Overload
         Capability is not supported, Label Mapping Message will be returned
         with Label Release Message.

         (3) If vRtrLdpPeerMaxFecLogOnly is set to 'true', no action will be
         taken.

         [RECOVERY] Appropriate Configuration changes in local or peer LSR will
         be required.

         This notification was obsoleted in release 13.0."
    ::= { tmnxLdpNotifications 8 }

vRtrLdpSessMaxFecLimitReached · obsolete

vRtrLdpSessMaxFecLimitReached   NOTIFICATION-TYPE
    OBJECTS {
              vRtrLdpPeerMaxFec,
              vRtrLdpSessOperMaxFecThreshold }
    STATUS obsolete 
    DESCRIPTION
        "[CAUSE] A vRtrLdpSessMaxFecLimitReached notification is generated when
         the number of FEC's accepted from the peer has reached the value
         specified by vRtrLdpPeerMaxFec.

         If the current number of FEC's go below the limit but higher than the 
         configured threshold and again start to increase and hit the limit a 
         second time, we will raise a trap if 2 or more minutes have elapsed 
         since the first vRtrLdpSessMaxFecLimitReached trap was sent.

         If any parameter in FEC limit configuration changes and the current
         number of FEC's are equal to or higher than the limit specified by
         vRtrLdpPeerMaxFec, then we would always raise the 
         vRtrLdpSessMaxFecLimitReached trap.         

         [EFFECT] When the number of FECs exceed the configured maximum 
         (vRtrLdpPeerMaxFec) it results in any of the following:

         (1) If vRtrLdpPeerMaxFecLogOnly is set to 'false' and LSR Overload
         Capability is supported, then Overload procedure will take place.

         (2) If vRtrLdpPeerMaxFecLogOnly is set to 'false' and LSR Overload
         Capability is not supported, Label Mapping Message will be returned
         with Label Release Message.

         (3) If vRtrLdpPeerMaxFecLogOnly is set to 'true', no action will be
         taken.

         [RECOVERY] Appropriate Configuration changes in local or peer
         LSR will be required.
         
         This notification was obsoleted in release 13.0."
    ::= { tmnxLdpNotifications 8 }

Meaning

Descriptions

2 unique

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

Description 1

[CAUSE] A vRtrLdpSessMaxFecLimitReached notification is generated when the number of FECs accepted from the peer has reached the value specified by vRtrLdpPeerMaxFec. If the current number of FECs go below the limit but higher than the configured threshold and again start to increase and hit the limit a second time, we will raise a trap if 2 or more minutes have elapsed since the first vRtrLdpSessMaxFecLimitReached trap was sent. If any parameter in FEC limit configuration changes and the current number of FECs are equal to or higher than the limit specified by vRtrLdpPeerMaxFec, then we would always raise the vRtrLdpSessMaxFecLimitReached trap. [EFFECT] When the number of FECs exceed the configured maximum (vRtrLdpPeerMaxFec) it results in any of the following: (1) If vRtrLdpPeerMaxFecLogOnly is set to 'false' and LSR Overload Capability is supported, then Overload procedure will take place. (2) If vRtrLdpPeerMaxFecLogOnly is set to 'false' and LSR Overload Capability is not supported, Label Mapping Message will be returned with Label Release Message. (3) If vRtrLdpPeerMaxFecLogOnly is set to 'true', no action will be taken. [RECOVERY] Appropriate Configuration changes in local or peer LSR will be required. This notification was obsoleted in release 13.0.

Sources for this description

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

See 1 matching source record

Description 2

[CAUSE] A vRtrLdpSessMaxFecLimitReached notification is generated when the number of FEC's accepted from the peer has reached the value specified by vRtrLdpPeerMaxFec. If the current number of FEC's go below the limit but higher than the configured threshold and again start to increase and hit the limit a second time, we will raise a trap if 2 or more minutes have elapsed since the first vRtrLdpSessMaxFecLimitReached trap was sent. If any parameter in FEC limit configuration changes and the current number of FEC's are equal to or higher than the limit specified by vRtrLdpPeerMaxFec, then we would always raise the vRtrLdpSessMaxFecLimitReached trap. [EFFECT] When the number of FECs exceed the configured maximum (vRtrLdpPeerMaxFec) it results in any of the following: (1) If vRtrLdpPeerMaxFecLogOnly is set to 'false' and LSR Overload Capability is supported, then Overload procedure will take place. (2) If vRtrLdpPeerMaxFecLogOnly is set to 'false' and LSR Overload Capability is not supported, Label Mapping Message will be returned with Label Release Message. (3) If vRtrLdpPeerMaxFecLogOnly is set to 'true', no action will be taken. [RECOVERY] Appropriate Configuration changes in local or peer LSR will be required. This notification was obsoleted in release 13.0.

Sources for this description

Netdisco MIB archive copies

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

Description 1

vRtrLdpSessMaxFecLimitReached · obsoleteMultiple manufacturers; see the original MIB MIB copies (LibreNMS/Observium Community), Nokia networking MIB copies (LibreNMS/Observium Community)3 sources

Status in source: obsolete.

Names: vRtrLdpSessMaxFecLimitReached

Technical details
{
  "smi_kind": "NOTIFICATION-TYPE",
  "definition": [
    "vRtrLdpSessMaxFecLimitReached",
    "NOTIFICATION-TYPE",
    "OBJECTS",
    "{",
    "vRtrLdpPeerMaxFec",
    ",",
    "vRtrLdpSessOperMaxFecThreshold",
    "}",
    "STATUS",
    "obsolete",
    "DESCRIPTION",
    "\"[CAUSE] A vRtrLdpSessMaxFecLimitReached notification is generated when the number of FECs accepted from the peer has reached the value specified by vRtrLdpPeerMaxFec. If the current number of FECs go below the limit but higher than the configured threshold and again start to increase and hit the limit a second time, we will raise a trap if 2 or more minutes have elapsed since the first vRtrLdpSessMaxFecLimitReached trap was sent. If any parameter in FEC limit configuration changes and the current number of FECs are equal to or higher than the limit specified by vRtrLdpPeerMaxFec, then we would always raise the vRtrLdpSessMaxFecLimitReached trap. [EFFECT] When the number of FECs exceed the configured maximum (vRtrLdpPeerMaxFec) it results in any of the following: (1) If vRtrLdpPeerMaxFecLogOnly is set to 'false' and LSR Overload Capability is supported, then Overload procedure will take place. (2) If vRtrLdpPeerMaxFecLogOnly is set to 'false' and LSR Overload Capability is not supported, Label Mapping Message will be returned with Label Release Message. (3) If vRtrLdpPeerMaxFecLogOnly is set to 'true', no action will be taken. [RECOVERY] Appropriate Configuration changes in local or peer LSR will be required. This notification was obsoleted in release 13.0.\"",
    "::=",
    "{",
    "tmnxLdpNotifications",
    "8",
    "}"
  ],
  "syntax_tree": [
    [
      "Objects",
      [
        "vRtrLdpPeerMaxFec",
        "vRtrLdpSessOperMaxFecThreshold"
      ]
    ],
    [
      "Status",
      "obsolete"
    ],
    [
      "DESCRIPTION",
      "[CAUSE] A vRtrLdpSessMaxFecLimitReached notification is generated when the number of FECs accepted from the peer has reached the value specified by vRtrLdpPeerMaxFec. If the current number of FECs go below the limit but higher than the configured threshold and again start to increase and hit the limit a second time, we will raise a trap if 2 or more minutes have elapsed since the first vRtrLdpSessMaxFecLimitReached trap was sent. If any parameter in FEC limit configuration changes and the current number of FECs are equal to or higher than the limit specified by vRtrLdpPeerMaxFec, then we would always raise the vRtrLdpSessMaxFecLimitReached trap. [EFFECT] When the number of FECs exceed the configured maximum (vRtrLdpPeerMaxFec) it results in any of the following: (1) If vRtrLdpPeerMaxFecLogOnly is set to 'false' and LSR Overload Capability is supported, then Overload procedure will take place. (2) If vRtrLdpPeerMaxFecLogOnly is set to 'false' and LSR Overload Capability is not supported, Label Mapping Message will be returned with Label Release Message. (3) If vRtrLdpPeerMaxFecLogOnly is set to 'true', no action will be taken. [RECOVERY] Appropriate Configuration changes in local or peer LSR will be required. This notification was obsoleted in release 13.0."
    ],
    null
  ]
}
  • Nokia networking MIB copies (LibreNMS/Observium Community) · Publisher's source file: TIMETRA-LDP-MIB

    Vendor MIB copy from the LibreNMS archive. Nokia support.

    Module: TIMETRA-LDP-MIB

    See published definition above

    Module imports
    {'IF-MIB': ['InterfaceIndexOrZero'], 'SNMPv2-TC': ['DisplayString', 'RowStatus', 'TEXTUAL-CONVENTION', 'TestAndIncr', 'TimeInterval', 'TimeStamp', 'TruthValue'], 'SNMPv2-SMI': ['Counter32', 'Counter64', 'Gauge32', 'IpAddress', 'MODULE-IDENTITY', 'NOTIFICATION-TYPE', 'OBJECT-TYPE', 'Unsigned32'], 'SNMPv2-CONF': ['MODULE-COMPLIANCE', 'NOTIFICATION-GROUP', 'OBJECT-GROUP'], 'MPLS-LDP-MIB': ['MplsLdpIdentifier', 'MplsLsrIdentifier'], 'TIMETRA-TC-MIB': ['TNamedItem', 'TNamedItemOrEmpty', 'TPolicyStatementNameOrEmpty', 'TmnxAddressAndPrefixAddress', 'TmnxAddressAndPrefixPrefix', 'TmnxAddressAndPrefixType', 'TmnxAdminState', 'TmnxEnabledDisabled', 'TmnxLdpFECType', 'TmnxOperState', 'TmnxServId', 'TmnxVRtrMplsLspID', 'TmnxVcId', 'TmnxVcType'], 'INET-ADDRESS-MIB': ['InetAddress', 'InetAddressPrefixLength', 'InetAddressType'], 'TIMETRA-SERV-MIB': ['SdpId', 'ServType', 'TdmOptionsCasTrunkFraming', 'TdmOptionsSigPkts'], 'TIMETRA-VRTR-MIB': ['vRtrID', 'vRtrLdpStatus'], 'TIMETRA-FILTER-MIB': ['TFilterID', 'TFilterLogId'], 'TIMETRA-GLOBAL-MIB': ['timetraSRMIBModules', 'tmnxSRConfs', 'tmnxSRNotifyPrefix', 'tmnxSRObjs']}
    · Download TIMETRA-LDP-MIB
  • 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-MIB

    Same published definition

    Module imports
    {'IF-MIB': ['InterfaceIndexOrZero'], 'SNMPv2-TC': ['DisplayString', 'RowStatus', 'TEXTUAL-CONVENTION', 'TestAndIncr', 'TimeInterval', 'TimeStamp', 'TruthValue'], 'SNMPv2-SMI': ['Counter32', 'Counter64', 'Gauge32', 'IpAddress', 'MODULE-IDENTITY', 'NOTIFICATION-TYPE', 'OBJECT-TYPE', 'Unsigned32'], 'SNMPv2-CONF': ['MODULE-COMPLIANCE', 'NOTIFICATION-GROUP', 'OBJECT-GROUP'], 'MPLS-LDP-MIB': ['MplsLdpIdentifier', 'MplsLsrIdentifier'], 'TIMETRA-TC-MIB': ['TNamedItem', 'TNamedItemOrEmpty', 'TPolicyStatementNameOrEmpty', 'TmnxAddressAndPrefixAddress', 'TmnxAddressAndPrefixPrefix', 'TmnxAddressAndPrefixType', 'TmnxAdminState', 'TmnxEnabledDisabled', 'TmnxLdpFECType', 'TmnxOperState', 'TmnxServId', 'TmnxVRtrMplsLspID', 'TmnxVcId', 'TmnxVcType'], 'INET-ADDRESS-MIB': ['InetAddress', 'InetAddressPrefixLength', 'InetAddressType'], 'TIMETRA-SERV-MIB': ['SdpId', 'ServType', 'TdmOptionsCasTrunkFraming', 'TdmOptionsSigPkts'], 'TIMETRA-VRTR-MIB': ['vRtrID', 'vRtrLdpStatus'], 'TIMETRA-FILTER-MIB': ['TFilterID', 'TFilterLogId'], 'TIMETRA-GLOBAL-MIB': ['timetraSRMIBModules', 'tmnxSRConfs', 'tmnxSRNotifyPrefix', 'tmnxSRObjs']}
    · Download TIMETRA-LDP-MIB

    Related source files and packages:

  • Multiple manufacturers; see the original MIB MIB copies (LibreNMS/Observium Community) · Publisher's source file: TIMETRA-LDP-MIB

    Vendor MIB copy from the LibreNMS archive.

    Module: TIMETRA-LDP-MIB

    Same published definition

    Module imports
    {'IF-MIB': ['InterfaceIndexOrZero'], 'SNMPv2-TC': ['DisplayString', 'RowStatus', 'TEXTUAL-CONVENTION', 'TestAndIncr', 'TimeInterval', 'TimeStamp', 'TruthValue'], 'SNMPv2-SMI': ['Counter32', 'Counter64', 'Gauge32', 'IpAddress', 'MODULE-IDENTITY', 'NOTIFICATION-TYPE', 'OBJECT-TYPE', 'Unsigned32'], 'SNMPv2-CONF': ['MODULE-COMPLIANCE', 'NOTIFICATION-GROUP', 'OBJECT-GROUP'], 'MPLS-LDP-MIB': ['MplsLdpIdentifier', 'MplsLsrIdentifier'], 'TIMETRA-TC-MIB': ['TNamedItem', 'TNamedItemOrEmpty', 'TPolicyStatementNameOrEmpty', 'TmnxAddressAndPrefixAddress', 'TmnxAddressAndPrefixPrefix', 'TmnxAddressAndPrefixType', 'TmnxAdminState', 'TmnxEnabledDisabled', 'TmnxLdpFECType', 'TmnxOperState', 'TmnxServId', 'TmnxVRtrMplsLspID', 'TmnxVcId', 'TmnxVcType'], 'INET-ADDRESS-MIB': ['InetAddress', 'InetAddressPrefixLength', 'InetAddressType'], 'TIMETRA-SERV-MIB': ['SdpId', 'ServType', 'TdmOptionsCasTrunkFraming', 'TdmOptionsSigPkts'], 'TIMETRA-VRTR-MIB': ['vRtrID', 'vRtrLdpStatus'], 'TIMETRA-FILTER-MIB': ['TFilterID', 'TFilterLogId'], 'TIMETRA-GLOBAL-MIB': ['timetraSRMIBModules', 'tmnxSRConfs', 'tmnxSRNotifyPrefix', 'tmnxSRObjs']}
    · Download TIMETRA-LDP-MIB
Records for description 2Netdisco MIB archive copies1 record · 1 source

Description 2

vRtrLdpSessMaxFecLimitReached · obsoleteNetdisco MIB archive copies1 source

Status in source: obsolete.

Names: vRtrLdpSessMaxFecLimitReached

Technical details
{
  "smi_kind": "NOTIFICATION-TYPE",
  "definition": [
    "vRtrLdpSessMaxFecLimitReached",
    "NOTIFICATION-TYPE",
    "OBJECTS",
    "{",
    "vRtrLdpPeerMaxFec",
    ",",
    "vRtrLdpSessOperMaxFecThreshold",
    "}",
    "STATUS",
    "obsolete",
    "DESCRIPTION",
    "\"[CAUSE] A vRtrLdpSessMaxFecLimitReached notification is generated when the number of FEC's accepted from the peer has reached the value specified by vRtrLdpPeerMaxFec. If the current number of FEC's go below the limit but higher than the configured threshold and again start to increase and hit the limit a second time, we will raise a trap if 2 or more minutes have elapsed since the first vRtrLdpSessMaxFecLimitReached trap was sent. If any parameter in FEC limit configuration changes and the current number of FEC's are equal to or higher than the limit specified by vRtrLdpPeerMaxFec, then we would always raise the vRtrLdpSessMaxFecLimitReached trap. [EFFECT] When the number of FECs exceed the configured maximum (vRtrLdpPeerMaxFec) it results in any of the following: (1) If vRtrLdpPeerMaxFecLogOnly is set to 'false' and LSR Overload Capability is supported, then Overload procedure will take place. (2) If vRtrLdpPeerMaxFecLogOnly is set to 'false' and LSR Overload Capability is not supported, Label Mapping Message will be returned with Label Release Message. (3) If vRtrLdpPeerMaxFecLogOnly is set to 'true', no action will be taken. [RECOVERY] Appropriate Configuration changes in local or peer LSR will be required. This notification was obsoleted in release 13.0.\"",
    "::=",
    "{",
    "tmnxLdpNotifications",
    "8",
    "}"
  ],
  "syntax_tree": [
    [
      "Objects",
      [
        "vRtrLdpPeerMaxFec",
        "vRtrLdpSessOperMaxFecThreshold"
      ]
    ],
    [
      "Status",
      "obsolete"
    ],
    [
      "DESCRIPTION",
      "[CAUSE] A vRtrLdpSessMaxFecLimitReached notification is generated when the number of FEC's accepted from the peer has reached the value specified by vRtrLdpPeerMaxFec. If the current number of FEC's go below the limit but higher than the configured threshold and again start to increase and hit the limit a second time, we will raise a trap if 2 or more minutes have elapsed since the first vRtrLdpSessMaxFecLimitReached trap was sent. If any parameter in FEC limit configuration changes and the current number of FEC's are equal to or higher than the limit specified by vRtrLdpPeerMaxFec, then we would always raise the vRtrLdpSessMaxFecLimitReached trap. [EFFECT] When the number of FECs exceed the configured maximum (vRtrLdpPeerMaxFec) it results in any of the following: (1) If vRtrLdpPeerMaxFecLogOnly is set to 'false' and LSR Overload Capability is supported, then Overload procedure will take place. (2) If vRtrLdpPeerMaxFecLogOnly is set to 'false' and LSR Overload Capability is not supported, Label Mapping Message will be returned with Label Release Message. (3) If vRtrLdpPeerMaxFecLogOnly is set to 'true', no action will be taken. [RECOVERY] Appropriate Configuration changes in local or peer LSR will be required. This notification was obsoleted in release 13.0."
    ],
    null
  ]
}
  • Netdisco MIB archive copies · Publisher's source file: timetra-ldp-mib.mib

    Vendor MIB copy from the Netdisco archive.

    Module: TIMETRA-LDP-MIB

    See published definition above

    Module imports
    {'IF-MIB': ['InterfaceIndexOrZero'], 'SNMPv2-TC': ['RowStatus', 'TruthValue', 'TestAndIncr', 'TimeStamp', 'TimeInterval', 'DisplayString', 'TEXTUAL-CONVENTION'], 'SNMPv2-SMI': ['MODULE-IDENTITY', 'OBJECT-TYPE', 'NOTIFICATION-TYPE', 'Unsigned32', 'Counter32', 'Gauge32', 'Counter64', 'IpAddress'], 'SNMPv2-CONF': ['MODULE-COMPLIANCE', 'OBJECT-GROUP', 'NOTIFICATION-GROUP'], 'MPLS-LDP-MIB': ['MplsLdpIdentifier', 'MplsLsrIdentifier'], 'TIMETRA-TC-MIB': ['TmnxAdminState', 'TmnxOperState', 'TPolicyStatementNameOrEmpty', 'TmnxServId', 'TmnxVcType', 'TmnxVcId', 'TmnxEnabledDisabled', 'TNamedItemOrEmpty', 'TmnxVRtrMplsLspID', 'TmnxLdpFECType', 'TNamedItem', 'TmnxMplsLsrNgIdentifier'], 'INET-ADDRESS-MIB': ['InetAddress', 'InetAddressType', 'InetAddressPrefixLength'], 'TIMETRA-SERV-MIB': ['ServType', 'SdpId', 'TdmOptionsSigPkts', 'TdmOptionsCasTrunkFraming'], 'TIMETRA-VRTR-MIB': ['vRtrID', 'vRtrLdpStatus'], 'TIMETRA-FILTER-MIB': ['TFilterLogId', 'TFilterID'], 'TIMETRA-GLOBAL-MIB': ['timetraSRMIBModules', 'tmnxSRObjs', 'tmnxSRNotifyPrefix', 'tmnxSRConfs']}
    · Download timetra-ldp-mib.mib

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 (7)

OIDNameDirect childrenDescendantsDescription
1.3.6.1.4.1.6527.3.1.3.8.0.1 vRtrLdpStateChange00 The vRtrLdpStateChange notification is generated when the LDP
protocol is created or deleted in the router.
1.3.6.1.4.1.6527.3.1.3.8.0.2 vRtrLdpInstanceStateChange00 The vRtrLdpInstanceStateChange notification is generated when the LDP
module changes state either administratively or operationa…
1.3.6.1.4.1.6527.3.1.3.8.0.3 vRtrLdpIfStateChange00 The vRtrLdpIfStateChange notification is generated when the LDP
interface changes state either administratively or operationally.
1.3.6.1.4.1.6527.3.1.3.8.0.4 vRtrLdpSvcIdMismatch00 The vRtrLdpSvcIdMismatch notification is generated when there is
a mismatch of local and remote service IDs.
1.3.6.1.4.1.6527.3.1.3.8.0.5 vRtrLdpGroupIdMismatch00 The vRtrLdpGroupIdMismatch notification is generated when there is
a mismatch of local and remote group IDs.
1.3.6.1.4.1.6527.3.1.3.8.0.6 vRtrLdpSessionStateChange00
1.3.6.1.4.1.6527.3.1.3.8.0.7 vRtrLdpSessMaxFecThresChanged00