OID reference

vRtrLdpNgSessMaxFecLimitReached

1.3.6.1.4.1.6527.3.1.3.91.0.8

Description

[CAUSE] A vRtrLdpNgSessMaxFecLimitReached notification is generated when the number of FECs accepted from the peer has reached the value specified by vRtrLdpNgSessParamMaxFec. 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 secon…

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
8
Node name
vRtrLdpNgSessMaxFecLimitReached
Category
SNMP notification
Numeric OID
1.3.6.1.4.1.6527.3.1.3.91.0.8
URN notation
urn:oid:1.3.6.1.4.1.6527.3.1.3.91.0.8
ASN.1, OID-IRI and named path variants
ASN.1 notation

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

  • {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) vRtrLdpNgSessMaxFecLimitReached(8)}
  • {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) vRtrLdpNgSessMaxFecLimitReached(8)}
  • {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) vRtrLdpNgSessMaxFecLimitReached(8)}
  • {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) vRtrLdpNgSessMaxFecLimitReached(8)}
  • {iso(1) org(3) dod(6) internet(1) private(4) enterprise(1) timetra(6527) timetraProducts(3) tmnxSRMIB(1) tmnxSRNotifyPrefix(3) tmnxLdpNgNotifyPrefix(91) tmnxLdpNgNotifications(0) vRtrLdpNgSessMaxFecLimitReached(8)}
  • {iso(1) org(3) dod(6) internet(1) private(4) enterprises(1) timetra(6527) timetraProducts(3) tmnxSRMIB(1) tmnxSRNotifyPrefix(3) tmnxLdpNgNotifyPrefix(91) tmnxLdpNgNotifications(0) vRtrLdpNgSessMaxFecLimitReached(8)}
  • {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) vRtrLdpNgSessMaxFecLimitReached(8)}
  • {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) vRtrLdpNgSessMaxFecLimitReached(8)}
  • {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) vRtrLdpNgSessMaxFecLimitReached(8)}
  • {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) vRtrLdpNgSessMaxFecLimitReached(8)}
  • {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) vRtrLdpNgSessMaxFecLimitReached(8)}
  • {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) vRtrLdpNgSessMaxFecLimitReached(8)}
  • {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) vRtrLdpNgSessMaxFecLimitReached(8)}
  • {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) vRtrLdpNgSessMaxFecLimitReached(8)}
  • {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) vRtrLdpNgSessMaxFecLimitReached(8)}
  • {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) vRtrLdpNgSessMaxFecLimitReached(8)}
OID-IRI notation
  • /1/3/6/1/4/1/6527/3/1/3/91/0/8
  • /ISO/Identified-Organization/6/1/4/1/6527/3/1/3/91/0/8
  • /ISO/3/6/1/4/1/6527/3/1/3/91/0/8
Named path variants
  • /iso/identified-organization/dod/internet/private/enterprise/timetra/timetraProducts/tmnxSRMIB/tmnxSRNotifyPrefix/tmnxLdpNgNotifyPrefix/tmnxLdpNgNotifications/vRtrLdpNgSessMaxFecLimitReached
  • /iso/identified-organization/dod/internet/private/enterprises/timetra/timetraProducts/tmnxSRMIB/tmnxSRNotifyPrefix/tmnxLdpNgNotifyPrefix/tmnxLdpNgNotifications/vRtrLdpNgSessMaxFecLimitReached
  • /iso/identified-organization/dod/internet/private/ldap-enterprise/timetra/timetraProducts/tmnxSRMIB/tmnxSRNotifyPrefix/tmnxLdpNgNotifyPrefix/tmnxLdpNgNotifications/vRtrLdpNgSessMaxFecLimitReached
  • /iso/identified-organization/dod/internet/private/vendor-objects/timetra/timetraProducts/tmnxSRMIB/tmnxSRNotifyPrefix/tmnxLdpNgNotifyPrefix/tmnxLdpNgNotifications/vRtrLdpNgSessMaxFecLimitReached
  • /iso/org/dod/internet/private/enterprise/timetra/timetraProducts/tmnxSRMIB/tmnxSRNotifyPrefix/tmnxLdpNgNotifyPrefix/tmnxLdpNgNotifications/vRtrLdpNgSessMaxFecLimitReached
  • /iso/org/dod/internet/private/enterprises/timetra/timetraProducts/tmnxSRMIB/tmnxSRNotifyPrefix/tmnxLdpNgNotifyPrefix/tmnxLdpNgNotifications/vRtrLdpNgSessMaxFecLimitReached
  • /iso/org/dod/internet/private/ldap-enterprise/timetra/timetraProducts/tmnxSRMIB/tmnxSRNotifyPrefix/tmnxLdpNgNotifyPrefix/tmnxLdpNgNotifications/vRtrLdpNgSessMaxFecLimitReached
  • /iso/org/dod/internet/private/vendor-objects/timetra/timetraProducts/tmnxSRMIB/tmnxSRNotifyPrefix/tmnxLdpNgNotifyPrefix/tmnxLdpNgNotifications/vRtrLdpNgSessMaxFecLimitReached
  • /iso/iso-identified-organization/dod/internet/private/enterprise/timetra/timetraProducts/tmnxSRMIB/tmnxSRNotifyPrefix/tmnxLdpNgNotifyPrefix/tmnxLdpNgNotifications/vRtrLdpNgSessMaxFecLimitReached
  • /iso/iso-identified-organization/dod/internet/private/enterprises/timetra/timetraProducts/tmnxSRMIB/tmnxSRNotifyPrefix/tmnxLdpNgNotifyPrefix/tmnxLdpNgNotifications/vRtrLdpNgSessMaxFecLimitReached
  • /iso/iso-identified-organization/dod/internet/private/ldap-enterprise/timetra/timetraProducts/tmnxSRMIB/tmnxSRNotifyPrefix/tmnxLdpNgNotifyPrefix/tmnxLdpNgNotifications/vRtrLdpNgSessMaxFecLimitReached
  • /iso/iso-identified-organization/dod/internet/private/vendor-objects/timetra/timetraProducts/tmnxSRMIB/tmnxSRNotifyPrefix/tmnxLdpNgNotifyPrefix/tmnxLdpNgNotifications/vRtrLdpNgSessMaxFecLimitReached
  • /iso/iso-organization/dod/internet/private/enterprise/timetra/timetraProducts/tmnxSRMIB/tmnxSRNotifyPrefix/tmnxLdpNgNotifyPrefix/tmnxLdpNgNotifications/vRtrLdpNgSessMaxFecLimitReached
  • /iso/iso-organization/dod/internet/private/enterprises/timetra/timetraProducts/tmnxSRMIB/tmnxSRNotifyPrefix/tmnxLdpNgNotifyPrefix/tmnxLdpNgNotifications/vRtrLdpNgSessMaxFecLimitReached
  • /iso/iso-organization/dod/internet/private/ldap-enterprise/timetra/timetraProducts/tmnxSRMIB/tmnxSRNotifyPrefix/tmnxLdpNgNotifyPrefix/tmnxLdpNgNotifications/vRtrLdpNgSessMaxFecLimitReached
  • /iso/iso-organization/dod/internet/private/vendor-objects/timetra/timetraProducts/tmnxSRMIB/tmnxSRNotifyPrefix/tmnxLdpNgNotifyPrefix/tmnxLdpNgNotifications/vRtrLdpNgSessMaxFecLimitReached

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

Show 2 published definitions

vRtrLdpNgSessMaxFecLimitReached · current

vRtrLdpNgSessMaxFecLimitReached  NOTIFICATION-TYPE
    OBJECTS     {
        vRtrLdpNgSessParamMaxFec,
        vRtrLdpNgSessOperMaxFecThreshold
    }
    STATUS      current
    DESCRIPTION
        "[CAUSE] A vRtrLdpNgSessMaxFecLimitReached notification is generated
         when the number of FECs accepted from the peer has reached the value
         specified by vRtrLdpNgSessParamMaxFec.

         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 vRtrLdpNgSessMaxFecLimitReached 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
         vRtrLdpNgSessMaxFecLimitReached trap.

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

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

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

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

         [RECOVERY] Appropriate Configuration changes in local or peer LSR will
         be required."
    ::= { tmnxLdpNgNotifications 8 }

vRtrLdpNgSessMaxFecLimitReached · current

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

         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 vRtrLdpNgSessMaxFecLimitReached 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 
         vRtrLdpNgSessMaxFecLimitReached trap.         

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

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

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

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

         [RECOVERY] Appropriate Configuration changes in local or peer
         LSR will be required."
    ::= { tmnxLdpNgNotifications 8 }

Meaning

Descriptions

2 unique

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

Description 1

[CAUSE] A vRtrLdpNgSessMaxFecLimitReached notification is generated when the number of FECs accepted from the peer has reached the value specified by vRtrLdpNgSessParamMaxFec. 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 vRtrLdpNgSessMaxFecLimitReached 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 vRtrLdpNgSessMaxFecLimitReached trap. [EFFECT] When the number of FECs exceed the configured maximum (vRtrLdpNgSessParamMaxFec) it results in any of the following: (1) If vRtrLdpNgSessParamMaxFecLogOnly is set to 'false' and LSR Overload Capability is supported, then Overload procedure will take place. (2) If vRtrLdpNgSessParamMaxFecLogOnly is set to 'false' and LSR Overload Capability is not supported, Label Mapping Message will be returned with Label Release Message. (3) If vRtrLdpNgSessParamMaxFecLogOnly is set to 'true', no action will be taken. [RECOVERY] Appropriate Configuration changes in local or peer LSR will be required.

Sources for this description

Nokia networking MIB copies (LibreNMS/Observium Community)

See 1 matching source record

Description 2

[CAUSE] A vRtrLdpNgSessMaxFecLimitReached notification is generated when the number of FEC's accepted from the peer has reached the value specified by vRtrLdpNgSessParamMaxFec. 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 vRtrLdpNgSessMaxFecLimitReached 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 vRtrLdpNgSessMaxFecLimitReached trap. [EFFECT] When the number of FECs exceed the configured maximum (vRtrLdpNgSessParamMaxFec) it results in any of the following: (1) If vRtrLdpNgSessParamMaxFecLogOnly is set to 'false' and LSR Overload Capability is supported, then Overload procedure will take place. (2) If vRtrLdpNgSessParamMaxFecLogOnly is set to 'false' and LSR Overload Capability is not supported, Label Mapping Message will be returned with Label Release Message. (3) If vRtrLdpNgSessParamMaxFecLogOnly is set to 'true', no action will be taken. [RECOVERY] Appropriate Configuration changes in local or peer LSR will be required.

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

Description 1

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

Status in source: current.

Names: vRtrLdpNgSessMaxFecLimitReached

Technical details
{
  "smi_kind": "NOTIFICATION-TYPE",
  "definition": [
    "vRtrLdpNgSessMaxFecLimitReached",
    "NOTIFICATION-TYPE",
    "OBJECTS",
    "{",
    "vRtrLdpNgSessParamMaxFec",
    ",",
    "vRtrLdpNgSessOperMaxFecThreshold",
    "}",
    "STATUS",
    "current",
    "DESCRIPTION",
    "\"[CAUSE] A vRtrLdpNgSessMaxFecLimitReached notification is generated when the number of FECs accepted from the peer has reached the value specified by vRtrLdpNgSessParamMaxFec. 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 vRtrLdpNgSessMaxFecLimitReached 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 vRtrLdpNgSessMaxFecLimitReached trap. [EFFECT] When the number of FECs exceed the configured maximum (vRtrLdpNgSessParamMaxFec) it results in any of the following: (1) If vRtrLdpNgSessParamMaxFecLogOnly is set to 'false' and LSR Overload Capability is supported, then Overload procedure will take place. (2) If vRtrLdpNgSessParamMaxFecLogOnly is set to 'false' and LSR Overload Capability is not supported, Label Mapping Message will be returned with Label Release Message. (3) If vRtrLdpNgSessParamMaxFecLogOnly is set to 'true', no action will be taken. [RECOVERY] Appropriate Configuration changes in local or peer LSR will be required.\"",
    "::=",
    "{",
    "tmnxLdpNgNotifications",
    "8",
    "}"
  ],
  "syntax_tree": [
    [
      "Objects",
      [
        "vRtrLdpNgSessParamMaxFec",
        "vRtrLdpNgSessOperMaxFecThreshold"
      ]
    ],
    [
      "Status",
      "current"
    ],
    [
      "DESCRIPTION",
      "[CAUSE] A vRtrLdpNgSessMaxFecLimitReached notification is generated when the number of FECs accepted from the peer has reached the value specified by vRtrLdpNgSessParamMaxFec. 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 vRtrLdpNgSessMaxFecLimitReached 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 vRtrLdpNgSessMaxFecLimitReached trap. [EFFECT] When the number of FECs exceed the configured maximum (vRtrLdpNgSessParamMaxFec) it results in any of the following: (1) If vRtrLdpNgSessParamMaxFecLogOnly is set to 'false' and LSR Overload Capability is supported, then Overload procedure will take place. (2) If vRtrLdpNgSessParamMaxFecLogOnly is set to 'false' and LSR Overload Capability is not supported, Label Mapping Message will be returned with Label Release Message. (3) If vRtrLdpNgSessParamMaxFecLogOnly is set to 'true', no action will be taken. [RECOVERY] Appropriate Configuration changes in local or peer LSR will be required."
    ],
    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:

Records for description 2Netdisco MIB archive copies1 record · 1 source

Description 2

vRtrLdpNgSessMaxFecLimitReached · currentNetdisco MIB archive copies1 source

Status in source: current.

Names: vRtrLdpNgSessMaxFecLimitReached

Technical details
{
  "smi_kind": "NOTIFICATION-TYPE",
  "definition": [
    "vRtrLdpNgSessMaxFecLimitReached",
    "NOTIFICATION-TYPE",
    "OBJECTS",
    "{",
    "vRtrLdpNgSessParamMaxFec",
    ",",
    "vRtrLdpNgSessOperMaxFecThreshold",
    "}",
    "STATUS",
    "current",
    "DESCRIPTION",
    "\"[CAUSE] A vRtrLdpNgSessMaxFecLimitReached notification is generated when the number of FEC's accepted from the peer has reached the value specified by vRtrLdpNgSessParamMaxFec. 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 vRtrLdpNgSessMaxFecLimitReached 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 vRtrLdpNgSessMaxFecLimitReached trap. [EFFECT] When the number of FECs exceed the configured maximum (vRtrLdpNgSessParamMaxFec) it results in any of the following: (1) If vRtrLdpNgSessParamMaxFecLogOnly is set to 'false' and LSR Overload Capability is supported, then Overload procedure will take place. (2) If vRtrLdpNgSessParamMaxFecLogOnly is set to 'false' and LSR Overload Capability is not supported, Label Mapping Message will be returned with Label Release Message. (3) If vRtrLdpNgSessParamMaxFecLogOnly is set to 'true', no action will be taken. [RECOVERY] Appropriate Configuration changes in local or peer LSR will be required.\"",
    "::=",
    "{",
    "tmnxLdpNgNotifications",
    "8",
    "}"
  ],
  "syntax_tree": [
    [
      "Objects",
      [
        "vRtrLdpNgSessParamMaxFec",
        "vRtrLdpNgSessOperMaxFecThreshold"
      ]
    ],
    [
      "Status",
      "current"
    ],
    [
      "DESCRIPTION",
      "[CAUSE] A vRtrLdpNgSessMaxFecLimitReached notification is generated when the number of FEC's accepted from the peer has reached the value specified by vRtrLdpNgSessParamMaxFec. 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 vRtrLdpNgSessMaxFecLimitReached 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 vRtrLdpNgSessMaxFecLimitReached trap. [EFFECT] When the number of FECs exceed the configured maximum (vRtrLdpNgSessParamMaxFec) it results in any of the following: (1) If vRtrLdpNgSessParamMaxFecLogOnly is set to 'false' and LSR Overload Capability is supported, then Overload procedure will take place. (2) If vRtrLdpNgSessParamMaxFecLogOnly is set to 'false' and LSR Overload Capability is not supported, Label Mapping Message will be returned with Label Release Message. (3) If vRtrLdpNgSessParamMaxFecLogOnly is set to 'true', no action will be taken. [RECOVERY] Appropriate Configuration changes in local or peer LSR will be required."
    ],
    null
  ]
}
  • Netdisco MIB archive copies · Publisher's source file: timetra-ldp-ng-mib.mib

    Vendor MIB copy from the Netdisco archive.

    Module: TIMETRA-LDP-NG-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': ['MplsLsrIdentifier'], 'TIMETRA-TC-MIB': ['TmnxAdminState', 'TmnxOperState', 'TPolicyStatementNameOrEmpty', 'TmnxServId', 'TmnxVcType', 'TmnxVcId', 'TmnxEnabledDisabled', 'TmnxCBFClasses', 'TmnxVcIdOrNone', 'TNamedItemOrEmpty', 'TmnxVRtrMplsLspID', 'TmnxLdpFECType', 'TNamedItem', 'TmnxMplsLdpNgIdType', 'TmnxMplsLdpNgIdentifier', 'TmnxMplsLsrNgIdentifier'], 'TIMETRA-LDP-MIB': ['TmnxLdpKeepAliveFactor', 'TmnxLdpNewKeepAliveTimeout', 'TmnxLdpHelloFactor', 'TmnxLdpNewHelloTimeout', 'TmnxLdpBackoffTime', 'TmnxLdpAdjacencyType', 'TmnxLdpIntTargOperDownReasonCode', 'TmnxLdpLabelDistMethod', 'TmnxLdpHelloTimeout', 'TmnxLdpFECFlags', 'TmnxLabelStatus', 'TmnxVpnId', 'TmnxLabelSigStatus', 'TmnxLdpInLblWdrawalReasonCode', 'TmnxLdpFec129Tlv', 'vRtrLdpSessOverloadState', 'vRtrLdpSessOverloadDirection', 'vRtrLdpSessOverloadFecType', 'TmnxLdpGenOperDownReasonCode', 'TmnxLdpFECPolicy'], '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-ng-mib.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.9 vRtrLdpNgResourceExhaustion00
1.3.6.1.4.1.6527.3.1.3.91.0.11 vRtrLdpNgAddrFecCommMismatch00