Preview Tool

Cisco Bug: CSCsz34118 - UNI: ASR shouldn't puts LNS into busy list during L2TP resync period

Last Modified

Jan 30, 2017

Products (1)

  • Cisco IOS

Known Affected Releases


Description (partial)


If a new L2TP session comes into the ASR LAC while it is still in the resync phase (just after switchover), the session is rejected as expected, but the LNS is put in the busy list. Hence even if the session tries to come up again after the resync phase is complete, if the LNS busy timer hasn't expired, the session can't be brought up. Sessions can be brought up only after the busy timer has expired. It is incorrect to put the LNS in the busy list in this scenario since the LNS isn't really busy. This behavior adds additional 60 sec delay in time it takes for ASR to bring up a new session after RP switchover in worst case scenario.
When a new L2TP session comes into the ASR LAC with L2TP HA enabled and LAC is still in resync phase just after a switchover.
Bug details contain sensitive information and therefore require a account to be viewed.

Bug Details Include

  • Full Description (including symptoms, conditions and workarounds)
  • Status
  • Severity
  • Known Fixed Releases
  • Related Community Discussions
  • Number of Related Support Cases
Bug information is viewable for customers and partners who have a service contract. Registered users can view up to 200 bugs per month without a service contract.