To migrate from previous database to the new database, you must perform the following steps:

Prerequisites

Note: Upgrade from 6.8u2 to 6.8u5 does not need event migration, as both of these have Elastic Search database. Also, running the event migration task throws an exception, which can be ignored.
  • Install and configure previous M&R version. For example, install and configure 6.7u1.
  • Configure 6.7u1 for Smarts SP CDR/CMR configurations. Verify CallOverview reports are present.
  • Download the latest M&R build. The Service Assurance Suite Installation and Configuration Guide for M&R provides more information.
  • Install the M&R, by invoking the following command: 
    sh EMC_MnR_7.3.0.5_Linux_64-bit_Setup_File.sh
  • To upgrade the platform, install the new packages in: 
    /opt/APG/Tools/Module-Repository [Y/n]? Y
/opt/APG/bin/manage-modules.sh update module-manager
/opt/APG/bin/manage-modules.sh service update all
/opt/APG/Tools/Module-Manager/1.16u3/bin/launch-update.sh
  • Configure the Elastic Search, see Configuring Elastic Search for more information.
  • Restart Elastic Search server. Ensure Elastic Search server is running.

Procedure

  1. Update the CUCM package.
  2. Update the CUCM versions from SolutionPacks.
  3. Ensure that CDR Processing block in the CUCM SP is updated with the Elastic Search host IP address instead of the localhost.
  4. Update the post install procedure.
  5. Manually create the schema for the CDR database, you have to create the following ES-TF-VOIP resource for the tomcat server to enable the connection to the CDR database.
    On Linux: 
    ./bin/manage-resources.sh create dba/ES-TF-VOIP '{ "type": "elasticsearch", "datasource": { "hosts": ["http://localhost:9200"],"prefix": "/cdr*"},"settings": {"mapping": "ES-CISCO-CDR.xml"},"disabled": false }'
    On Windows: 
    APG PATH\bin\manage-resources.cmd create dba/ES-TF-VOIP '{ "type": "elasticsearch", "datasource": { "hosts": ["http://localhost:9200"],"prefix": "/cdr*"},"settings": {"mapping": "ES-CISCO-CDR.xml"},"disabled": false }'
  6. Perform one of the following:
    • For migration from 6.6u1 or 6.7u1, delete the "dba/FLOW-TF-VOIP" table from manage-resources list.
    • For migration from 6.5u4, delete the resource link for FLOW-TF-VOIP from APG.xml and Server.xml.
  7. Restart the Tomcat service.
  8. Restart the Elastic Search server.
  9. Stop the event processing manager service for cisco-voip-cucm.
  10. Run the data-migration task which is enabled for run, see the Scheduling the Event-Processing Tasks for more information.
  11. Verify the Event Processing for cisco-cucm, CDR records are read and processed.
  12. Ensure from Elastic Search, that data is flowing.
    URL to check the data in Elastic Search are: 
    http://<Host IP of Elastic Search>:9200/_cat/indices
http://<Host IP of Elastic Search>:9200/_template?pretty
http://<Host IP of Elastic Search>:9200/cdr*/_search?pretty
---to get the total hits rows/records
  13. Add new CDR records and verify new CallOverview reports are also fetched.