How to Upgrade Cisco MeetingPlace
Now that MeetingPlace from Cisco is in a state of confusion due to its pending demise, it appears to be extremely hard to find information on how to upgrade it. Conflicting information prevails and Cisco SE's can't even find information or even the Product Manager!
Well, we did a successful upgrade today from 8.4 through multiple steps (so as to be careful since there is no clear information) and are finally at the current 8.6.2 SR1 version. We were already virtualized and started with 8.2 initially so we are fortunate for that. If you are upgrading from a physical version, you have a lot of reading to do...! This may not help too much.
Here are the several steps used to get there. It isn't totally detailed as to all the exact steps for each different version increment but I think you'll get the picture.
If you have questions or comments, please post them and I'll try to clear anything ambiguous up.
First of all, here are some links to the high level documentation;
- An upgrade keeps the database that holds the Hardware Media Server configuration information.
- We support using Integrated Lights-Out (iLO) to install/upgrade the Application Server software. This standard only applies to the Cisco MCS 7845-H2. For information about installing, configuring, and using iLO, see http://h18000.www1.hp.com/products/servers/management/ilo/.
- The upgrade program retains the same deployment that you currently have on your existing Cisco Unified MeetingPlace system.


- Do not uninstall the Application Server software before the upgrade.
- The Cisco Unified MeetingPlace system must be running when you perform an upgrade. Do not turn off the Cisco Unified MeetingPlace services.
- If you have automatic backups/archives enabled, then turn this off when you upgrade the Application Server software.
- Make sure your system is functional before starting the upgrade (the Operational Status of each node is green)
- If your Application Server is in a failover deployment and you want to continue MeetingPlace scheduling—follow the procedure in Upgrading a Failover Deployment in an Audio System or a System with MeetingPlace Scheduling (Cisco Unified MeetingPlace 8.5.5) or Upgrading a Failover Deployment in an Audio-Only System or a System with MeetingPlace Scheduling (Cisco Unified MeetingPlace 8.5.4 and Earlier). After the upgrade, reconfigure the system for database replication.
- Otherwise, follow the procedure in either the Upgrading the Application Server by Using the Console or the Upgrading the Application Server Remotely.
- Complete Determining Which Procedure to Follow.
- Take the Audio Blade offline.

- A. Login to SSH as mpxadmin, then change to 'root' user:
- A. Use 'chmod' command. For the use with MP hotfixes '755' permissions are used:
- A. Use 'mv' or 'cp' command:
- Backup MP File 8.5.2.8 which was the main upgrade at installation. First installation was a 7.x version and then was upgraded to this version.

============
=========================
a. Leaf nodes first
b. Secondary MBD
c. Primary MBD
1. Copy the patch file to the MP Application server
2. Put the patch in /mpx-record and gunzip it.
- A. Use 'gunzip' command:
If the the checksum value matches values above, you can proceed with running the patch
If the checksum value doesn't match, the file is corrupted, please, contact Cisco TAC to get the file republished.
4. Set the appropriate (755) permissions on the extracted .bin file and run it.
5. Answer the confirm/continue prompts if any.
6. The patch installer will install the files.
7. Repeat the steps for the standby server (failover deployment), or other nodes (multi-node deployment).


- Do not uninstall the Application Server software before the upgrade.
- The Cisco Unified MeetingPlace system must be running when you perform an upgrade. Do not turn off the Cisco Unified MeetingPlace services.
- If you have automatic backups/archives enabled, then turn this off when you upgrade the Application Server software.
- Make sure your system is functional before starting the upgrade (the Operational Status of each node is green)
- If your Application Server is in a failover deployment and you want to continue MeetingPlace scheduling—follow the procedure in Upgrading a Failover Deployment in an Audio System or a System with MeetingPlace Scheduling (Cisco Unified MeetingPlace 8.5.5) or Upgrading a Failover Deployment in an Audio-Only System or a System with MeetingPlace Scheduling (Cisco Unified MeetingPlace 8.5.4 and Earlier). After the upgrade, reconfigure the system for database replication.
- Otherwise, follow the procedure in either the Upgrading the Application Server by Using the Console or the Upgrading the Application Server Remotely.
- Complete Determining Which Procedure to Follow.
- Take the Audio Blade offline.


============
=========================
a. Leaf nodes first
b. Secondary MBD
c. Primary MBD
1. Login as mpxadmin. Escalate to root privilege user and then Copy the patch file to the MP Application server
2. Put the patch in /mpx-record and gunzip it.
3. Check cksum of gunzipped patch:
If the the checksum value matches values above, you can proceed with running the patch
If the checksum value doesn't match, the file is corrupted, please, contact Cisco TAC to get the file republished.
4. Set the appropriate (755) permissions on the extracted .bin file and run it.
6. The patch installer will install the files.
7. Repeat the steps for the standby server (failover deployment), or other nodes (multi-node deployment).

- Do not uninstall the Application Server software before the upgrade.
- The Cisco Unified MeetingPlace system must be running when you perform an upgrade. Do not turn off the Cisco Unified MeetingPlace services.
- If you have automatic backups/archives enabled, then turn this off when you upgrade the Application Server software.
- Make sure your system is functional before starting the upgrade (the Operational Status of each node is green)
- If your Application Server is in a failover deployment and you want to continue MeetingPlace scheduling—follow the procedure in Upgrading a Failover Deployment in an Audio System or a System with MeetingPlace Scheduling (Cisco Unified MeetingPlace 8.5.5) or Upgrading a Failover Deployment in an Audio-Only System or a System with MeetingPlace Scheduling (Cisco Unified MeetingPlace 8.5.4 and Earlier). After the upgrade, reconfigure the system for database replication.
- Otherwise, follow the procedure in either the Upgrading the Application Server by Using the Console or the Upgrading the Application Server Remotely.
- Complete Determining Which Procedure to Follow.
- Take the Audio Blade offline.


====
Version: 8.6.2.10 Patch 1
Filename: MP86MR1_PA1_Security_86210.bin.gz
Cksum: 3893645416 1142610 MP86MR1_PA1_Security_86210.bin
Released: Jul 10, 2015
=============
=============
[root@server ~]# openssl version
CiscoSSL 1.0.1p.4.13-fips
============
=========================
a. Leaf nodes first
b. Secondary MBD
c. Primary MBD
1. Copy the patch file to the MP Application server
2. Put the patch in /mpx-record and gunzip it.
3. Check cksum of gunzipped patch:
If the the checksum value matches values above, you can proceed with running the patch
If the checksum value doesn't match, the file is corrupted, please, contact Cisco TAC to get the file republished.
4. Set the appropriate (755) permissions on the extracted .bin file and run it.
5. Answer the confirm/continue prompts if any.
6. The patch installer will install the files.
7. Repeat the steps for the standby server (failover deployment), or other nodes (multi-node deployment).