Use these questions to navigate to the sections that pertain to your own situation.
#MIGRATE FROM 5 TO TOWEB 6 UPGRADE#
Do not upgrade to CMS 3.4 or newer unless you have set up Smart Licensing. You can not upgrade to CMS 3.4 or newer and still use traditional licenses. If you do not perform a stepped upgrade, and are experiencing unusual behavior, TAC could request you downgrade and start over.Īlso, as of CMS 3.4, CMS MUST use Smart Licensing. If you are on CMS 2.9, you must upgrade in a stepped fashion (2.9 -> 3.0 -> 3.1 -> 3.2 -> 3.3 -> 3.4 -> 3.5 (Note upgrade process has changes as of CMS 3.5, so read the release notes carefully!!) At the time of writing this, CMS 3.5 has been released. The only supported method for upgrading CMS is a stepped upgrade. You need to plan to replace your X-series servers as soon as possible. Note: X-series cannot be upgraded to CMS 3.0. The information in this document pertains to all models of CMS. This document is intended as guidance in case you already have a CMS 2.9.x (or earlier) deployment, regardless if single combined, or resilient, and when you plan to upgrade to CMS 3.0.
If your network is live, ensure that you understand the potential impact of any command. All of the devices used in this document started with a cleared (default) configuration. The information in this document was created from the devices in a specific lab environment. The information in this document is based on Cisco Meeting Server. It is always advisable to read the product release notes and refer to our programming guides and deployment guides if you need any further clarification on features: CMS Installation and Configuration Guides and CMS Product Release notes. Prerequisites RequirementsĬisco recommends that you have knowledge of these topics:Įverything mentioned here is outlined in various documents. It does not cover all of the new features available in 3.X. This document only covers topics you need to consider before upgrading.
#MIGRATE FROM 5 TO TOWEB 6 HOW TO#
This document describes the challenges of upgrading a Cisco Meeting Server deployment running version 2.9 (or earlier) to 3.0 (or later) and how to handle those for a smooth upgrade process.įeatures removed: XMPP was removed (which affects WebRTC), trunks/load balancers, webbridgeįeatures changed: Recorders and streamers are now SIP, and webbridge is replaced with webbridge3
0 kommentar(er)
