Cisco Support Community
cancel
Showing results for 
Search instead for 
Did you mean: 
Announcements

Welcome to Cisco Support Community. We would love to have your feedback.

For an introduction to the new site, click here. And see here for current known issues.

New Member

Webex Meeting Server upgrade to 2.5

Hello,

we have CWMS and IRP versione: 2.0.1.2.B-AE

We want to upgrade to 2.5.1.29.B-AE, i have the ova file.

Somebody can please help me giving me the steps to follow to perform the task?

Is the upgrade of the Internet Reverse "automatic"?

Every information will be appreciated.

Giovanni

 

1 ACCEPTED SOLUTION

Accepted Solutions
Cisco Employee

Yes, Giovanni, you can go to

Yes, Giovanni, you can go to MR3 directly.

 

-Dejan

25 REPLIES
Cisco Employee

Hi Giovanni, Update from 2.0

Hi Giovanni,

 

Update from 2.0 to 2.5 is considered a minor update. Keep in mind that in documentation we recommend you update 2.0 to 2.0 MR3 or later first, and then update to 2.5. Minor updates are pretty straight forward and you don't use the OVA file for minor updates, but instead the ISO update image from Cisco.com (You would use OVA file if you were performing a MAJOR upgrade from 1.x to 2.x release).

Here you can find minor update instructions:

1. Use these for update to 2.0 MR3 or later first: http://www.cisco.com/c/en/us/td/docs/collaboration/CWMS/2_0/Administration_Guide/Administration_Guide_chapter_01001.html

2. Use these for updating from 2.0 MR3 or later to 2.5: http://www.cisco.com/c/en/us/td/docs/collaboration/CWMS/2_5/Administration_Guide/Administration_Guide/Administration_Guide_chapter_01001.html

 

 

Minor update updates all the components automatically as long as your system is deployed properly (NTP is running on ESXi hosts and the time is in sync on all hosts, you have enough disk space, needed ports and protocols are open/enabled on your firewall (if you have the firewall between Admin VM and IRP VM - ports requirements). 

Furthermore, if you have a 50 users system, there is currently a bug on 2.5 version that causes some issues with labels and button definitions in the GUI after the update (Bug ID: CSCur33905 ), so you may want to wait until that is resolved. If you have 250, 800, or 2000 user system, you can proceed with 2.5 version. 

 

Finally, here is my best practices when doing a minor update:

  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 ,you can skip this step)
  2. Upload the update ISO file 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 update 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.

 

I hope this will be of help.

-Dejan

New Member

Hello Dejan,thank you very

Hello Dejan,

thank you very much for your answer.

It's my first upgrade of a webex, so maybe it's a stupid question.

The IRP VM will be updated automatically launching the update on the Admin VM?

 

We have 50 users Admin/media and IRP deployment, so we are probably hitting the bug CSCur33905, so maybe better to wait until is solved.

Thank you

Giovanni

Cisco Employee

Hi Giovanni, Entire system

Hi Giovanni,

 

Entire system will be updated automatically when doing a Minor Update (even if you are doing a MAJOR UPGRADE, you can do that automatically or manually). Hence, all the VMs will be updated automatically, including the IRP.

 

As for the update, you can update to the latest Maintenance Release for 2.0. That way at least you protect your system from all the know issues, and have a stable system before moving to 2.5 later on when bugs are fixed.

 

-Dejan

New Member

Hello Dejan,i am upgrading to

Hello Dejan,

i am upgrading to 2.0 MR5 right now in a test environment CWMS/IRP VMs

I'll keep you updated about the result :)

Thank you for very usefull informations.

Giovanni

New Member

Update to 2.0 MR5 went fine

Update to 2.0 MR5 went fine.

Thank you for informations.

Now i'll wait for the resolution of the BUG and after that i'll update to 2.5

Question: same way? Minor update steps?

Thank you

Giovanni

 

Cisco Employee

Hi Giovanni, I am glad

Hi Giovanni,

 

I am glad everything went well. As for moving from 2.0 to 2.5 MRx (once it is released), you would follow the same process for Minor Update as you did for 2.0 MR5 update.

 

-Dejan

New Member

Hello Dejan,do you have an

Hello Dejan,

do you have an idea about when will be released the new version that contains the bug fix?

Thank you

Giovanni

Cisco Employee

Hi Giovanni, Maintenance

Hi Giovanni,

 

Maintenance Releases are usually released at 2 months periods (sometimes a little bit later). Based on that, we can expect these defects resolved in 2.5 MR1 (unofficial ETA second half of December 2014).

-Dejan

 

New Member

Hello,how are you? Do you

Hello,

how are you? Do you know if "cisco-webex-meetings-server-2.5.1.132.B.iso" solved the BUG?

Thanks

Giovanni

Cisco Employee

Hi Giovanni, Defect

Hi Giovanni,

 

Defect CSCur33905 has been resolved in CWMS 2.5 MR1. At this time, you can proceed with updating to 2.5, and then updating to 2.5 MR1.

 

-Dejan

New Member

Hello Dejan,in a test (demo)

Hello Dejan,

in a test (demo) environment i performed the 2 updates, but:

- the first one went fine

- the second one no, i am not able to access administration page or "user" page

it looks like the webserver is unreachable : (

I waited 1 hour, and the same. I go to sleep now and tomorrow morning i'll try to access again.

Any idea?

Thanks

Giovanni

New Member

Another strange thing is that

Another strange thing is that the IP address that should be reachable is very unstable. I can reach it for a while and after it becomes unreachable.

I am sure network is ok. It's like webex meeting server is unable to start the virtual ip address and bind all the "web-stuff" to it.

: (
 

Cisco Employee

Hi Giovanni,I would advise

Hi Giovanni,

I would advise you to open a ticket with TAC to look into that as soon as possible so your production environment doesn't get impacted for too long.

 

Dejan

New Member

Hello,a little update about

Hello,

a little update about my adventure with webex meeting server.

I opened the case and the unique solution was restoring the VM from the backup

After that actually i updated the system to 2.5 and i'll update again the system to MR1 in a second step next days

Bye!

Giovanni

 

New Member

Hello Dejan,a little question

Hello Dejan,

a little question. I would like to try upgrading webex meeting server from 2.5.1.29.B-AE to 2.5 MR3 hoping that it does not fail.

Can you tell me if i can go directly to MR3?

Thanks.

Giovanni

 

Cisco Employee

Yes, Giovanni, you can go to

Yes, Giovanni, you can go to MR3 directly.

 

-Dejan

New Member

It worked without a problem

It worked without a problem.

thank you a lot

Anonymous
N/A

Hi  Giovanni,

Hi  Giovanni,

Do you have any idea how much time will it take to update from 2.0  to 2.0 MR9?

We are planning for  this update.

Thanks

Sanket G

Cisco Employee

As it is a single Minor

As it is a single Minor Update process, without knowing your deployment size, I would say you should plan for 4h.

30min to put the system in Maintenance and gracefully shut down VMs.

5min to take VM snapshots

30min to bring all the VMs back up into Maintenance Mode

45min to run the update

30min to restart the system upon update completion

30min to bring the system out of Maintenance mode

1h to run all the tests and ensure the system works as expected and there is no need to revert to snapshots.

And then, you need to push the 2.0 MR9 client version to end users but that can be done outside of maintenance window.

-Dejan

Hi, I am trying to update my

Hi,

 

I am trying to update my CWMS system from version 2.0.1.107.B-AE to version 2.0.1.707.B but I keep on getting the error below. Any suggestions or ideas? I have tried 2.0.1.207 as well same error.

 

We are unable to prepare your system for the update. Restore the existing system using your backup. Confirm that your copy of the Cisco WebEx Meetings Server Release Update file is not corrupt, then try the Update again. Contact Cisco Technical Assistance Center (TAC) for further assistance.

Voice CCIE #37771
Cisco Employee

Hi Hermanus, Can you please

Hi Hermanus,

 

Can you please share a little bit more information about your setup?

1. What is the size of your deployment?

2. Do you have Internet Reverse Proxy - Public Access (IRP)?

3. Do you have High Availability (HA)?

4. Can you check if NTP client is running on all ESXi servers hosting CWMS VMs?

5. Ensure the time is in sync on all the hosts

6. Make sure that all the ports between Admin VM and IRP VMs (if you have them) are open: http://www.cisco.com/c/en/us/td/docs/collaboration/CWMS/2_0/Planning_Guide/Planning_Guide_chapter_011.html#reference_CB65D7FE4B3746DDAF1649884AD777CE

 

Without the logs, it is hard to say what might have caused this error, but let's first check all of the above and we'll see what can be done next.

-Dejan

Hi Dejan, Thank you for the

Hi Dejan,

 

Thank you for the response.

 

1. What is the size of your deployment? (50 users)

2. Do you have Internet Reverse Proxy - Public Access (IRP)? (yes I have IRP with Public IP)

3. Do you have High Availability (HA)? (No)

4. Can you check if NTP client is running on all ESXi servers hosting CWMS VMs? (yes)

5. Ensure the time is in sync on all the hosts (Yes)

6. Make sure that all the ports between Admin VM and IRP VMs (if you have them) are open: http://www.cisco.com/c/en/us/td/docs/collaboration/CWMS/2_0/Planning_Guide/Planning_Guide_chapter_011.html#reference_CB65D7FE4B3746DDAF1649884AD777CE

Yes

I have 1.13TB free space on my server as well.

I will gather some logs and have a look in that and check with my FW team if anything gets blocked.

Question though with my initial setup I had to open ports and those ports is still open do I need extra ports for the update? I have had a look a the ports and it seems like all the ports I have added with my initial setup.

Voice CCIE #37771
Cisco Employee

Hi Hermanus,If all the ports

Hi Hermanus,

If all the ports are open that were there for deployment and match the port requirement in the Planning Guide, you should be good. 

Can you please try to go to CWMS Administration > Support > Remote Support Account, and enable the account (give it a name and validity of just 1 day)?

Once the account is enabled, please see if you can SSH to the IRP server using Putty client or similar. If your firewall allows port 22 access to IRP, but your SSH connection gets rejected, your IRP VM server most likely has an issue with time sync (even though the ESXi host is fine). If that is the case, try disabling Remote Support Account and perform a graceful restart of IRP VM (in vCenter, right click IRP VM > Power > Restart Guest).

Once IRP VM is back up, try to enable Remote Support Account one more time, and see if SSH connection is accepted (you won't be able to log in, as you won't have the valid password, but we care just about the SSH connection). If yes, put the system in maintenance mode and try to update again. (make sure you take the VM snapshots before attempting the update - put the system in MM, gracefully power off the VMs - Shut Down Guest in vCenter, take the snapshot, power on the VMs, and then proceed with the update).

Let me know how that goes.

-Dejan

Hi Dejan, It seems like NTP

Hi Dejan,

 

It seems like NTP was the issue yes, I did a graceful restart of both the Admin server and the IRP and the update went through successful.

Thank you very much for the prompt assistance.

 

Herman

Voice CCIE #37771
Cisco Employee

Hi Hermanus, I am glad to

Hi Hermanus,

 

I am glad to hear you were able to resolve the problem and upgrade successfully. 

Thank you for letting me know.

-Dejan

1603
Views
50
Helpful
25
Replies
CreatePlease login to create content