[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.