CUC (6) CUCM (28) Jabber (6) Python (2) Routing (3) Solarwinds Orion NPM (4) switching (1) Video (6) voice (3)

Wednesday, 7 January 2015

WebEx upgrade to 2.5

I have been working on this for a while, and recently I upgraded a webEx 1.5 system to 2.5. Cisco's documentation, although overwhelming, is somewhat sketchy in someways. This post will explain, step by step on what to do.  

So the assumption here is that you already have a fully functional CWMS deployment, with an admin server and a reverse proxy.

1-Obtain the upgrade software through Cisco PUT
First thing that you will need to do is obtain the 2.5 software. As this cannot be downloaded through software downloads with your cco account, you will need to go and order it though Cisco PUT. (which I experienced as a painful process to say at least. Sometimes Cisco is harder to deal with than the tax office). What you will get is an OVF template  (either the encrypted or unencrypted flavour, depending on what you ordered). I also found that you cannot order the CWMS 2.0 OVF.

2-Put your applicable ESXi hosts in VCentre
The upgrade will not work without vCentre, I found this out the hard way!
And remove all your existing 1.5 snaphots.

3-Deploy your OVFs
So the idea behind this whole update is to build a parallel 2.5 system that will be spun up after 1.5 is powered off. The 2.5 system will have the 1.5 vmdk copied to it, which will allow seamless migration. This is the part that I really like and that works as documented by Cisco.

Fig. 1 - Deploy CMWS  OVF template 

Give your virtual machine a name, please note that this is not the same as your host name

Fig 2. Choose the VM name

Choose your deployment option (Fig.3.),  for Reverse proxy (IRP) deployment obviously choose that option in Fig.3

Fig.3. Choose your deployment option.

After that, choose your ESXi host, and assign its storage. After that choose the VM Network mapping.

Next you will be presented a page where you populate the hostname, IP address, mask, default gateway, local domain name, and DNS servers  (this will only be available if you deploy through vCentre).  The settings here will have to be the same as in your 1.5 deployment. Remember we are upgrading an existing system. After you populated all this, a summary will be presented as the one below in Fig.4.

Fig.4. Deployment summary
After this it will deploy the OVF. please not that the power on after deployment is NOT ticked, leave it that way!

4-Power off your existing 1.5 admin server and reverse proxy
First go into the admin portal of your CWMS server, hit UPGRADE and then put it in maintenance mode. This will also put the reverse proxy in maintenance mode. After this power off the admin and reverse proxy guests through vCentre.

As of this moment there will be an outage, steps 1-3 are obviously non end-user impacting.

5-attach vmdk disk from 1.5 to 2.5
This is an important step, as it essentially copies all your 1.5 data across to 2.5 .

Just follow the table below, which is part of my change document, so I know for sure it works, and because this is how I roll. Please not that steps below will only need to be done for the CWMS admin server. the Reverse server? No, it is merely a dumb slave.

Step No.
Navigate to the Admin Virtual machine in VCentre, to existing 1.5 virtual machine.

Right click > EDIT settings

Select Hardware > Hard Disk 4
Check the VMDK location:
[cisco-webxadm_ds1] cisco-webxadm/cisco-webxadm_3-000001.vmdk
Folder name:
[au1cisco-webxadm_ds1] au1cisco-webxadm
(see picture 1)

Change the view:  VIEW>INVENTORY>DATA STORES AND Clusters

Browse to the Data store, obtained in Step 3.

Now also browse to the data store of the newly deployed 2.5 machine.

Copy the 1.5 vmdk  file obtained in Step 3 and paste into the 2.5 Datastore. (this only needs to be done on the Admin Virtual Machine).

Go to the upgraded 2.5 Admin Virtual Machine >EDIT SETTINGS  > Hardware > Hard Disk 4 > remove

Now add Hard Disk > NEXT > Use an existing virtual disk > Next

If you wanna go the highway check Cisco:

6-power on both admin and reverse proxy 2.5 servers.

Go to your VM console for the guest either admin, or reverse proxy, I powered admin on first and straight after that the IRP, no harm done.

One the console, you will see the following:

Fig.5. Deployment progress through Guest Console

You should see something similar through the console of your reverse Proxy. please note that I needs access through your firewall as the IRP is mostlikely deployed in some sort of DMZ. Make sure it can get to the DNS. Seeing that 1.5 was already deployed in a similar way, chances are that your firewall is already allowing traffic between admin and IRP.

After this you should see a screen like:

Fig.6. Obtain the deployment URL

Encircled is the deployment URL. Whack this in a browser, as it is your portal to the rest of the deployment.

Fig.7. Tracking Deployment progress through deployment URL

All this will probably take you 1 hour to migrate once CWMS 2.5 is spun up. After that, go into the admin portal of your 2.5 deployment and turn off maintenance mode.

And that is pretty much it. Now I have done the hard yard, go and take this recipe and do the upgrade.

Namaste! motherfuckers

1 comment:

  1. ok thanks for this post it's quite informative and I have learned new things.