Cisco Bug: CSCul53613 - No Failover triggered in partial failover state.
Sep 19, 2016
- Cisco Unified Attendant Consoles
Known Affected Releases
10.0(1) 10.5 9.0 9.1
Symptom: Currently for fail-over to trigger in a CUAC cluster, we require all 4 services Attendant Server Service, LDAP, CUPS and the BLF plugin to be down along with telephony so as to render a successful failover from Primary to Seconday for DDI calls. For a stable architecture, this failover mechanism depends on too many preconditions to be met so as to declare the communication between the CUAC publisher/Primary and CUCM Publisher/Primary CTI Mgr. If the system is in a partial degradation, such as only Attendant Server service is down, and rest of the services are up, fail-over does not trigger. There should be a fewer dependent services to trigger failover from Primary to Secondary, like in other appliance models, such as CUCM where a single CM service triggers fail-over. Since a customer deployment can always run into a partial degraded state of the CUAC server, this requirement only makes the fail-over architecture more dependable. Conditions: CUAC 9 & CUAC 10
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