Cisco Bug: CSCte56532 - Manifest failure alarm present even after SE deregistered
Nov 25, 2010
- Cisco Content Delivery Engine Series
Known Affected Releases
Symptom: In a corner case, a minor alarm manifestUpdateFail can be raised after an acquirer is deactivated, the alarm can't be cleared after activating the device again. Conditions: The following operation series can cause the issue, (1) Stop the cms service of an acquirer, or reload the acquirer, (2) Designate another SE as acquirer, and deactivate the previous acquirer, (3) Restart the cms service of previous acquirer, or the previous acquirer becomes online after it's reloaded. Then the manifestUpdateFail alarm will be raised.
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