Frequently Asked Questions

How do I upgrade a resilient deployment to meeting server versions 3.5 and later?

Note: Cisco Meeting Server must be upgraded sequentially to each version of the software. If you are currently on CMS 3.4 and wish to upgrade to 3.6.x, you must upgrade to 3.5.x initially, and then go to CMS 3.6.x.
 
Procedure: 
 
  1. Before upgrading your Meeting Servers, take a backup of the current configuration on each of the servers. Use the backup snapshot <name> command. Save the backup safely to a local server. See the MMP Command Reference guide for full details. Do not rely on the automatic backup file generated by the upgrade/downgrade process as it may be inaccessible in the event of a failed upgrade/downgrade.

  2. Save the cms.lic and certificate files to the local drive. (From version 3.0 Smart Licensing is introduced and Cisco Meeting Management handles the licenses.) 

  3. Before upgrading, check the database cluster status and document who is the current primary server. Check that all calls (SIP and clients) are working and no fault conditions are listed on the Web Admin pages.

  4. Disband the servers from the database cluster before upgrading, starting with any connected CMS nodes, then Replica CMS nodes, and finally the primary node using database cluster remove command.

  5. Upgrade all Core servers. This can be performed simultaneously as the servers are not clustered. Wait until all servers have fully booted. Run the command version to ensure the servers have all upgraded to the desired version.

  6. If the previous upgrade was just a step upgrade and you plan to go to another version, repeat Step 5 until you are at the version you want.  If you are currently on the version you wanted to be on, proceed to step 7.

  7. Once all servers have upgraded, you need to now re-cluster the environment.  Starting with the node that WAS primary before starting the upgrade process, run  the database cluster initialize command.

  8. On the nodes that were Joined (showing up as replicas in step 4), run the database cluster join <IP of Primary node> command. 

  9. On the nodes that were Connected (Not seen in Step 4 as replicas), run the database cluster connect <IP of Primary node> command. 

  10. check that the database servers are connected and in sync (check this using database cluster status). Do not go onto the next step until the database servers are in sync. 

  11. Check that the Web Admin interface on each Call Bridge and confirm that the coSpaces and users are all there, on all nodes. 

  12. Upgrade all Edge servers.
Last update:
13-Oct-2022
FAQ ID:
1519