Cisco Bug: CSCuq84088 - Indefinite CUCM Callprocessing outage after LBM LINK OOS.
Jul 29, 2017
- Cisco Unified Communications Manager (CallManager)
Known Affected Releases
Symptom: CUCM Callprocessing went into indefinite halt state after LBM LINK OOS. Conditions: CUCM Version 10.5.1.98000-263 CUCM under traffic exhibited "%UC_Location Bandwidth Manager-1-LBMLinkOOS:", and this cause outage of call processing for an indefinite period of time. LBM LINK-OOS triggered due to some unknown reasons within 2 minutes of traffic start, and in another 10-15 minutes CCM call processing capability completely stopped in CUCM clusters interconnected via LBM network, even the clusters not taking part in traffic refused to process the calls. Traffic was stopped in ~30 minutes and the system was left idle for next 60 hours, but it never recovered itself. we need to STOP the LBM service manually to make call processing working. Symptoms: Alarms: %UC_Location Bandwidth Manager-1-LBMLinkOOS: LBM HUBS nodes showing high in CPU (~100%) in all clusters. When a call is made, no Ringback, definite silent, and the called party never ring. Few LBM core dumps. Total number of clusters 3. (2 LEAF and one SME) interconnected via LBM.
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