Cisco Meeting Server Cluster Upgrade to 2.3.6

[Steffen Wentzel]

Hi team,

currently I'm planning to upgrade a CMS cluster from 2.3.0 to 2.3.6. The cluster consists of three nodes, all are virtualized deployments. We have two callbridges and one dedicated DB node:

• CMS01: CallBridge + DB
• CMS02: CallBridge + DB
• CMS03: DB only

From the upgrade documentation I understand that I should issue a

database cluster status

command to check DB health and find out which nodes are slave/master. Then it says "Upgrade each database node, one by one, starting with the slave database nodes and finishing with the master node".

Q1: What are the database nodes in my case? I assume this includes all nodes in my case, b/c the DB service runs on all three nodes, correct? And the master/slave information is shown by above command, so it could be that (depending on current status) I'll upgrade even CMS03 first, is this also correct?

Then I should login to the DB master node and issue this command:

database cluster upgrade_schema

Q2: Is this command only required on the current master node? So this implies that it will upgrade the schema on the slave nodes automatically?

Thanks for your feedback!

BR

Steffen

[Jaime Valencia · Accepted solution]

Have you read this

https://kb.acano.com/content/5/250/en/how-do-i-upgrade-a-resilient-deployment.html#content

[Steffen Wentzel]

Thanks Jaime, actually I haven't :-) Very helpful information, will do the upgrade today in the evening.

All the best,

Steffen