Cisco Bug: CSCur99152 - fips enabled cucm migration failed from 8.6.1 to 10.5.2
Sep 15, 2016
- Cisco Unified Communications Manager (CallManager)
Known Affected Releases
Symptom: M1 migration: Tomcat services are not up after installation, See below for the services list. This is specifically for a scenario when the IP or hostname is not changed for the source and the destination is in FIPS mode. Conditions: M1 migration i.e simple migration where source node network settings is being used by the destination node.
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