Cisco Bug: CSCuq83703 - LBM Link OOS may cause stale connections
Oct 27, 2017
- Cisco Unified Communications Manager (CallManager)
Known Affected Releases
Symptom: LBM LINK OSS can cause stale connections. Conditions: Call is up between two endpoints registered to same UCM cluster. On the local node where call got originated, had only one local LBM service, no backup configured. CCM process will update LBM on local node, which in turn will update the other LBM nodes about the current call. At this point, if the LBM service on the local node is cored, stopped, or OOS with the local ccm service. And call is released before the LBM process comes up. CCM service will not be able to update the local LBM service now, and it wont update other LBM services as well, as no backup is configured. On an ideal situation, if LBM service doesnt hear about the call transaction, then it will clear the connections once the timer elapses which is 15 or 20 mins. But before the timer gets elapsed, if there is a network flap or other lBM service incurred LBM link OOS, then it will send all its transactions to the other nodes once the link is in service. And this process can go on a loop, if they receive an update even before the timer gets elapsed, which will lead the way to stale connections.
Bug details contain sensitive information and therefore require a Cisco.com account to be viewed.
Bug Details Include
- Full Description (including symptoms, conditions and workarounds)
- Known Fixed Releases
- Related Community Discussions
- Number of Related Support Cases