[CAUSE] A vRtrLdpSessMaxFecThresChanged notification is generated when the number of FECs accepted from the peer has exceeded or drops below vRtrLdpPeerMaxFecThreshold percent of the value specified by vRtrLdpPeerMaxFec. New notification will not be generated if multiple internal event change occurs for the same level indicated by vRtrLdpSessOperThresLevel during a 2 minute interval. If any parameter in FEC limit configuration changes then we would always raise this trap if current number of FECs are above the configured threshold or has crossed the threshold downwards. If we remain on or below the configured threshold before and after the configuration changes then no trap would be generated. [EFFECT] No direct effect but if the peer LSR continues to send further Label Mapping Message, then the number of FECs may exceed the configured maximum (vRtrLdpPeerMaxFec) resulting in the generation of vRtrLdpSessMaxFecLimitReached notification. [RECOVERY] Appropriate Configuration changes in local or peer LSR will be required. This notification was obsoleted in release 13.0.