Upgrade and Migration Strategy

Transcription

1 Cisco HCS Architecture, page 2 Solution Upgrade and Migration Phases, page 5 Understanding Subsystem Upgrades, page 6 1

2 Cisco HCS Architecture Cisco HCS Architecture The following figure provides a high-level view of the Cisco Hosted Collaboration Solution (HCS). Depicted are the component groups such as data center, telephony aggregation, virtualization, management, and various Unified Communications (UC) application deployment models. Figure 1: Cisco HCS Architecture - Network View The Cisco HCS Data Center is depicted (at a high level) as the chassis that houses the blades on which virtualized HCS applications are deployed. Management System and Telephony applications are deployed in the service provider's data center. Cisco UC applications can be deployed in the service provider's data center, or at a customer's data center (CPE). When deployed at a CPE, UC applications support the components deployed at the CPE. Note The private cloud model has all layers deployed, but still connects back to the service provider's Telephony Aggregation function. As shown in the figure, Management System is a collection of Service Fulfillment and Service Assurance applications. Telephony Aggregation comprises applications and components used for call and connection routing between the UC applications and the PSTN and WebEx clouds. The Cisco HCS Model is a Service Fulfillment data set that defines the Cisco HCS Dial Plan that is provisioned by Cisco Unified Communications Domain Manager. 2

3 Data Center Data Center The end-to-end data center architecture for Cisco HCS includes the data center connectivity, deployment models, addressing scheme, and security. It also includes the deployment of a Session Border Controller for Cisco HCS, as part of the telephony aggregation function. It is recommended that Service Providers remain current within their data center releases. If the system is running a release earlier than the latest recommended release, Cisco advises upgrading to the recommended release as soon as possible. Cisco recommends continual data center upgrades, regardless of management and application upgrades, as long as a compatible configuration is maintained. For information on the data center upgrade strategy, see Phase 1 - Cisco HCS Data Center Infrastructure Upgrades. HCS Management Applications Cisco Hosted Collaboration Solution Release 10.6(1)Service Fulfillment applications consist of the Cisco Hosted Collaboration Mediation Fulfillment (HCM-F) application and the associated Service Fulfillment Domain Managers: Cisco Unified Communications Domain Manager (Unified CDM) 10.x Cisco Unified Communications Domain Manager 8.1(x) Contact Center Domain Manager Prime License Manager Cisco Hosted Collaboration Solution Release 10.6(1) Service Assurance Domain Managers consist of Prime Collaboration Assurance for Unified Communications. Management applications are typically deployed as one instance of the product that manages or monitors multiple instances of other Cisco HCS applications and components. This scenario is true of Service Fulfillment for Cisco HCM-F. Unified CDM 10.x is deployed in a multinode or single node configuration. Unified CDM 8.1(x) is deployed in primary and secondary pairs. As the number of customers in your Cisco HCS deployment increases beyond the scale of a Domain Manager, deploy multiple instances of that Domain Manager. In Service Fulfillment, the single instance of Cisco HCM-F can manage one Unified CDM 10.x and one Unified CDM 8.1(x). For information on the Management Applications upgrade strategy, see Phase 2 - Management Upgrades. Cisco Unified CDM Dial Plan Models Cisco HCS supports Cisco Unified Communications Domain Manager (Unified CDM) versions 8.1(x) and 10.x. Each version has a distinct Dial Plan model design. For descriptions, see Cisco Unified CDM 8.1(x) Dial Plan Model Assessment and Cisco Unified CDM 10.x Dial Plan Model Assessment. 3

4 HCS Management Applications Telephony Aggregation The Cisco HCS Telephony Aggregation components provide a centralized interconnect to the Service Provider cloud. The Telephony Aggregation is a demarcation for Cisco HCS. It is also a central point for all off-net calling capabilities to Unified Communications (UC) applications at the UC infrastructure layer. The Telephony Aggregation components can be deployed in various combinations depending on the type of services. The demarcation line denotes the logical and administrative separation between the service provider network and the Cisco HCS solution for the purposes of network interconnect. The following figure shows the different deployment models and the demarcation in each case. Figure 2: Deployment Models and Cisco HCS Demarcation This document recommends the order in which to upgrade Telephony Aggregation components relative to the other component groups. Upgrade details are provided only for Cisco HCS products that are deployed in the aggregation layer as listed in the Cisco Hosted Collaboration Solution Compatibility Matrix. Note Upgrading a session border controller (SBC) is discussed in Upgrade Network Infrastructure Components, as part of the Data Center upgrade. The upgrade strategy for the Aggregation components is discussed in Phase 4 - Aggregation and Unified Communications Applications Upgrade. Unified Communications Applications Cisco HCS partners deploy Unified Communications (UC) applications to offer voice, video, voice mail messaging, instant messaging and presence, and mobility. The Cisco Hosted Collaboration Solution Compatibility Matrix identifies the supported UC applications, which include the following: Cisco Unified Communications Manager Cisco Unified Communications Manager IM and Presence Service Cisco Unity Connection Cisco Unified Attendant Console Cisco TelePresence Cisco Unified Contact Center Enterprise Cisco Emergency Responder 4

5 Solution Upgrade and Migration Phases Cisco Paging Server Expressway Jabber Guest Server The upgrade strategy for UC applications is discussed in Phase 4 - Aggregation and Unified Communications Applications Upgrade. Solution Upgrade and Migration Phases The strategy for upgrading and migrating Cisco Unified Communications Domain Manager (Unified CDM) involves five phases: 1 Phase 1: Data Center Infrastructure Upgrade 2 Phase 2: Management Component Upgrade 3 Phase 3: Dial Plan Model Migration or Upgrade. This phase migrates the model and dial plan using Unified CDM 8.1(x) or upgrades the dial plan model using Unified CDM 10.x. 4 Phase 4: Aggregation and Unified Communications Applications Upgrade 5 Phase 5: Optional Component Introduction and Migration Each phase has the following characteristics: Comprises one or more Cisco HCS application and component groups Completed in a single or multiple maintenance windows Completed in a specific order Includes preupgrade and postupgrade phase conditions and activities Includes upgrade maintenance window conditions and activities Scheduled to be completed as soon as possible You can operate your Cisco HCS deployment between upgrade phases because the application and component groups of any phase are compatible with the subsequent upgrade phases. However, before you upgrade to the next phase, the previous phases must be upgraded to the minimum version. You can upgrade the required Cisco HCS Data Center components (based on the minimum versioning analysis) significantly before upgrading the subsequent phases. Each phase is described in more detail in the following topics. Phase 1 - Cisco HCS Data Center Infrastructure Upgrades Phase 2 - Management Upgrades Phase 3 - Dial Plan Migration Phase 4 - Aggregation and Unified Communications Applications Upgrade Phase 5 - Optional Components 5

6 Understanding Subsystem Upgrades Understanding Subsystem Upgrades Cisco Hosted Collaboration Solutions (HCS) consists of subsystems, or groupings of similar functionality, such as the following examples: Management fulfillment and management assurance products, such as Cisco Hosted Collaboration Mediation Fulfillment and Cisco Prime Collaboration Assurance Collaboration applications, such as Cisco Unified Communications Manager and Cisco Unity Connection Aggregation and Edge products, such as the Metaswitch Perimeta session border controller and Cisco Expressway For Cisco HCS Release 10.6(1) and later, you can upgrade one or more subsystems without upgrading the entire solution. The following rules apply: Subsystem upgrades are valid for maintenance releases of components, products, and applications introduced between major releases of Cisco HCS. The Cisco HCS Compatibility Matrix identifies the subsystems that are compatible with Cisco HCS Release 10.6(1): hosted-collaboration-solution-hcs/products-device-support-tables-list.html. Sample Subsystem Upgrade Scenario You deployed Cisco HCS Release 10.6(1). Between Cisco HCS Release 10.6(1) and the next major release of Cisco HCS, you can upgrade the following subsystem components: Cisco Unified Communications Domain Manager 10.6(1) to release 10.6(2) Cisco Unified Communications Domain Manager 8.1(7) to release 8.1(7)ER1 Prime Collaboration Deployment to release 10.6 Note You may have to upgrade two or more components within a subsystem at the same time. Refer to the component release notes for dependency information. 6