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. If you'd prefer to explore, try our test area to get started. And see here for current known issues.

Bronze

Callmanager bridged upgrade from 7.1.3 to 8.6

I'm planning a bridged upgrade from version 7.1.3 on MCS7845 hardware to 8.6.2 on UCS hardware (esxi 5). My MCS7845 hardware is supported for bridged upgrade to 8.6 version. Currently, all of my mgcp gateways and tftp services are pointed to the ip address of my subscribers.

After applying the upgrade to the MCS hardware and rebooting cluster to new version, I understand I take a drs backup of the publisher and restore it to the UCS hardware (and new licensing). Can I expect the subscribers to replicate to the new publisher or should I expect a complete outage until db replication takes place.

Also, after the publisher is running and relicensed, can I leave the old MCS hardware in place temporarily until I get my mgcp gateways and dhcp tftp options reconfigured (3-5 days). I plan on building new subscribers on UCS hardware. After the gatways and dhcp are changed, the old subscribers will be removed from the cluster and retired.

Any thoughts will be appreciated!

4 REPLIES
Cisco Employee

Callmanager bridged upgrade from 7.1.3 to 8.6

I assume you're going to upgrade all the servers, right??

If so, yes, once you switch them all you'll have replication.

If you're going to upgrade only the PUB, the moment you switch partitions and start running 8.6 there won't be any replication.

On above scenario you can lease SUBs running but obviously there won't be able to perform any management tasks and only UFF will be available

HTH

java

if this helps, please rate

www.cisco.com/go/pdihelpdesk

HTH

java

if this helps, please rate

www.cisco.com/go/pdi
Cisco Employee

Callmanager bridged upgrade from 7.1.3 to 8.6

Procedure


Step 1 Perform an upgrade to the new Cisco Unified Communications Manager version on your discontinued first node (publisher) server. Refer to the preceding sections in this chapter that describe the kind of upgrade you want to do. Observe the warning on the console that tells you that the only thing you can do with the new Cisco Unified Communications Manager version is to perform a DRS backup ("This hardware has limited functionality. Backup and Restore is the only supported functionality.").

Step 2 Perform an upgrade to the new Cisco Unified Communications Manager version on your subsequent node (subscriber) servers. Refer to the preceding sections in this chapter that describe the kind of upgrade you want to do.

Step 3 Verify database synchronization between all nodes. You can use the CLI commands utils dbreplication runtime state and utils dbreplication status. For more information, refer to the Command Line Interface Reference Guide for Cisco Unifed Communications Solutions.

Step 4 Using the new Cisco Unified Communications Manager version on your discontinued first node server, perform a DRS backup. The DRS backups are encrypted using the cluster security password provided at install time. You must remember this security password as the "old" password, because you may be prompted to enter this "old" password at the time of restore. Refer to the Disaster Recovery System Administration Guide.

Step 5 Disconnect your discontinued server from the network.

Step 6 Install the new Cisco Unified Communications Manager version on your new supported first node server. You must obtain and install a new license on this server. Refer to the guide Installing Cisco Unified Communications Manager. You will be prompted to enter a "new" security password, a password that is different from the "old" password you noted in Step 4. The guide Installing Cisco Unified Communications Manager describes the requirements of a "new" security password that Cisco Unified Communications Manager will accept. You must remember this "new" security password.

Step 7 Using the new Cisco Unified Communications Manager version on your new supported first node server, perform the Disaster Recovery System Administration Guide procedure "Restoring the First Node only (Rebuilding the Publisher Alone)". First, select only select the first node for restore. You can only select the subsequent nodes for restore after the completion of first node restore. Use the discontinued server's backup file that you created in Step 4. You will be prompted for the "old" security password that you noted in Step 4. For further details, refer to the Disaster Recovery System Administration Guide.

Step 8 On your new supported first node server, reactivate all services that used to be active on your discontinued first node server before the bridge upgrade. Refer to the Administration Guide for Cisco Unity Connection Serviceability.

Step 9 Verify database synchronization between all nodes. You can use the CLI commands utils dbreplication runtime state and utils dbreplication status. For more information, refer to the Command Line Interface Reference Guide for Cisco Unifed Communications Solutions.

So, you can expect an outage until you perform the bridge upgrade on the whole cluster.  Backup and Restore is the only supported functionality of the bridge upgrade, so no you can not leave the old hardware in place.  You should migrate the cluster to the UCS asap and at one time to have a shorter down time.

Regards,

Anthony

Bronze

Callmanager bridged upgrade from 7.1.3 to 8.6

Sorry for the 1 star. I meant to hit 5 and hit 1 accidently and it won't let me change it. Very helpful. Thanks!

Cisco Employee

Callmanager bridged upgrade from 7.1.3 to 8.6

Hi Brad,

No worries, as long as I could help you out.  Thats all that really matters. 

Thanks,

Anthony

748
Views
16
Helpful
4
Replies