Cisco Bug: CSCtb30286 - SRM should auto-failback if publisher/primary rebooted
Nov 21, 2014
- Cisco Unity Connection
Known Affected Releases
Symptom: In a Cisco Unity Connection 7.X cluster, when a publisher has the Primary cluster state and is rebooted gracefully, then the subscriber becomes the Primary and no failback occurs after the Publisher comes back online. When the subscriber has the primary role, a failure to the subscriber server will not result in the publisher taking over the primary role. The current design calls for when a publisher is rebooted and comes back, an automatic failback should occur. In all other cases (e.g. a critical service fails on the publisher/primary) the failback must be manual. Conditions: Only applicable to a Cisco Unity Connection 7.X cluster.
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