Cisco Bug: CSCut43885 - Clustering: inconsistent stop and start monitoring messages
Feb 15, 2018
- Cisco ASA 5500-X Series Firewalls
Known Affected Releases
Symptom: In the <CmdBold>show cluster info trace<noCmdBold> output, after a configuration is successfully sent to a slave, there are a series of "stop to monitor" and "start to monitor" messages for the interfaces. While there are "stop to monitor" messages for both physical and port-channel interfaces there are only "start to monitor" messages for port-channel interfaces. Conditions: Cisco ASA running release 18.104.22.168, configured for clustering and trying to join as a slave.
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