CWMS 2.0 - Adding IRP

[btmulgrew]

Hi, our customer currently has a single CWMS 2.0.1.107 server and is looking to install the IRP for public access.  The OVA provided is the 2.0.1.107; is it possible to upgrade the Admin / Media server to 2.0.2.507, then install the IRP as 2.0.1.107 then upgrade the IRP to 2.0.2.507?  Or do we need to build the IRP as the exact version as the existing Admin / Media server?

Thanks
Brian

[dpetrovi · Accepted solution]

Hi Brian,

If you have your internal CWMS VMs on a version level that is higher than the OVA available (e.g. in your case 2.0.2.507, and your OVA is 2.0.1.107), you can deploy IRP VM using 2.0.1.107 OVA, but then when you start adding the IRP to the topology, the system will recognize the discrepancy in version levels, and will ask you to attach the update ISO image to the Admin VM CD-rom in order to update the IRP server. Once it completes with the update, the IRP server will be successfully added to the topology.

I hope this clarifies expected behavior and the update process.

Kind regards,

-Dejan

[btmulgrew]

Thanks Dejan - hope you don't mind another quick question:

 It looks like we will be able to build the IRP on the existing version as the Admin server is actually-  2.0.1.507, so we should be ok there.

We are then looking to patch to cisco-webex-meetings-server-2.0.1.611.B.iso but from the readme we need Build 2.0.1.2.B,  I can’t see this version  on CCO – would you know if it is possible to upgrade direct from 2.0.1.507 to 2.0.1.611.B.iso?

Thanks

Brian

[dpetrovi · Accepted solution]

Hi Brian,

I assume you are talking about 2.0.1.107 version (2.0.1.507 is probably a typo). Update from 2.0.1.107 to 2.0 MR6 (2.0.1.611) is a direct update considered a minor update. Once you have your Admin and IRP VM built on 2.0.1.107 and in the same topology, then you can just perform a minor update of the entire solution to 2.0 MR6. Here is best practice approach to minor updates and below you will also find a link to the official documentation.

Download 2.0.1.611 iso (cisco-webex-meetings-server-2.0.1.611.B.iso) from cisco.com, and verify the MD5SUM based on the Readme file (62427cf5df7b1e409228052bc8524906 cisco-webex-meetings-server-2.0.1.611.B.iso). Once you have a file downloaded, proceed with these steps:

1. Ensure on your Dashboard that the daily backup is completed successfully (you have to have NFS storage configured on your system for backups and recordings to run. If not, and since this is a new install ,you can skip this step)
2. Upload the ISO file (cisco-webex-meetings-server-2.0.1.611.B.iso) to the Datastore that CWMS Admin VM has access to.
3. On the CWMS Dashboard, put the system into Maintenance Mode.
4. Power off the VMs (In vCenter for each VM select Power > Shut Down Guest).
5. Once the machines are down, take the snapshot of each VM (in vCenter for each VM create a VM snapshot).
6. After snapshots of CWMS VMs are taken, in vCenter, power ON all the VMs.
7. The system will boot into Maintenance Mode.
8. Mount the cisco-webex-meetings-server-2.0.1.611.B.iso​ image to the CD/DVD drive of the Admin VM.
9. Initiate the update process (Go to Dashboard Admin page, click on the System tab >  Upgrade > Update (minor update).  Click Continue, let the update proceed).
10. Once the update is completed, bring the system out of Maintenance Mode.
11. Verify everything is up and running and test basic functions like accessing the end user page, schedule a test meeting and join it.
12. After thorough testing and confirming everything is running as expected, proceed with removing the VM snapshots (in vCenter, for each VM ensure to remove the snapshots). This is a mandatory step as having snapshots on the system will cause serious performance degradation! Remove the snapshots within 24h after the update.

Official document: http://www.cisco.com/c/en/us/td/docs/collaboration/CWMS/2_0/Administration_Guide/Administration_Guide_chapter_01001.html

I hope this will help.

-Dejan

[btmulgrew]

Thanks very much indeed Dejan!

[Sanjay_555_07]

Hi Dpetrovi,

In my organization they are not feeling safe to connect the IRP with public server. Do cisco has any special solution for this security concern ?

Regards,

Sanjay