Installation and Administration Guide for the Cisco TelePresence Exchange System Release 1.1
Data Migration
Downloads: This chapterpdf (PDF - 92.0KB) The complete bookPDF (PDF - 3.66MB) | Feedback

Data Migration

Table Of Contents

Data Migration

About the Migration Behavior for Media Bridge Resources and Resource Groups

About the Migration Behavior for Meet-Me and Rendezvous Meetings

Administration Console Comparisons

Media Bridge Resources Comparisons

CTMS Resources Field Comparisons

TPS Resources Field Comparisons

MSE 8510 Resources Field Comparisons

Customers Comparisons

Endpoint Management Comparisons

Collaboration Services Comparisons


Data Migration


Revised July 3, 2012

This appendix describes how the Cisco TelePresence Exchange System migrates data from Release 1.0.(x) to Release 1.1, and how the administration console graphical user interface has changed between the two releases.

The following sections are included:

About the Migration Behavior for Media Bridge Resources and Resource Groups

About the Migration Behavior for Meet-Me and Rendezvous Meetings

Administration Console Comparisons

About the Migration Behavior for Media Bridge Resources and Resource Groups

When migrating media bridge resources (Cisco TelePresence Multipoint Switch [CTMS], Cisco TelePresence MCU MSE 8510 [MSE 8510], and Cisco TelePresence Server MSE 8710 [TPS]) from Release 1.0(x) to Release 1.1, the system automatically creates region-specific resource groups in the following manner:

All media bridge resources that are reserved for large meetings are contained within one resource group per region.

All media bridge resources that are not reserved for large meetings are contained within one resource group per region.

Up to two resource groups per region are created, where one of the resource groups contains only media bridge resources that are reserved for large meetings and the other resource group contains only media bridge resources that are not reserved for large meetings.

Names are assigned to the new resource groups based on the name of the associated region and whether or not the resource group contains resources that are reserved for large meetings. For example, if the resource group contains resources that are placed in the San Jose region and reserved for large meetings, then the system will name the resource group San Jose Large Resource Group.

Table E-1 provides examples of the system behavior for migrating media bridge resources to new resource groups.

Table E-1 Migration Behavior Examples for Media Bridge Resources and Resource Groups 

Before Data Migration
After Data Migration

CTMS resource that was not reserved for large meetings was placed in the San Jose region.

CTMS resource that was not reserved for large meetings is placed in a resource group named San Jose Resource Group.

TPS resource that was reserved for large meetings was placed in the San Jose region.

TPS resource that was reserved for large meetings is placed in a resource group named San Jose Large Resource Group.

MSE 8510 resource that was reserved for large meetings was placed in the San Francisco region.

MSE 8510 resource that was reserved for large meetings is placed in a resource group named San Francisco Large Resource Group.


By default, the system configures new resource groups with a guaranteed reservation type with the following dedication percentage and booking percentage settings:

For a resource group that contains resources that are reserved for large meetings, both the dedication percentage and booking percentage are set to 100%.

For a resource group that contains resources that are not reserved for large meetings, the dedication percentage is set to 80%, and the booking percentage is set to 100%.

About the Migration Behavior for Meet-Me and Rendezvous Meetings


Caution If you scheduled both Meet-Me and Rendezvous meetings, all the Rendezvous meetings will be deleted. Before you start the upgrade process, verify that all the Rendezvous meetings have been manually saved so that they can be created again.

When meetings are migrated during the upgrade to Release 1.1, the Host PINs and Automatic Meeting Extension meeting fields will be disabled.

For detailed information about the requirements and prerequisites to upgrade the software on the Cisco TelePresence Exchange System, see the "Upgrading the Software" chapter.

Administration Console Comparisons

The following sections describe the administration console user interface comparisons between Release 1.0.(x) to Release 1.1:

Media Bridge Resources Comparisons

Customers Comparisons

Endpoint Management Comparisons

Collaboration Services Comparisons

Media Bridge Resources Comparisons

The following sections describe the field comparisons for the media bridge resources:

CTMS Resources Field Comparisons

TPS Resources Field Comparisons

MSE 8510 Resources Field Comparisons

CTMS Resources Field Comparisons

Table E-2 describes the Cisco TelePresence Multipoint Switch (CTMS) resources field comparisons.

Table E-2 CTMS Resources Field Comparisons 

Release 1.0.(x) Field
Release 1.0.(x) Field Removed
Release 1.0.(x) Scenario
Replaced With...
Release 1.1 Scenario

Test CTMS

Yes

The Test check box allowed the CTMS to be available for test meetings only. A test system was not available for scheduling regular meetings.

The test resource concept is not supported.

Region

Yes

The resources were contained in the regions.

The Resource Group field.

The reservation type is configured by indicating a specific resource.

The resources are contained in the resource groups.

The resource groups are contained in the regions.


TPS Resources Field Comparisons

Table E-3 describes the Cisco TelePresence Server MSE 8710 (TPS) resources field comparisons.

Table E-3 TPS Resources Field Comparisons 

Release 1.0.(x) Field
Release 1.0.(x) Field Removed
Release 1.0.(x) Scenario
Replaced With...
Release 1.1 Scenario

Test TPS

Yes

The Test check box allowed you to reserve the TPS for test meetings only. When serving as a test system, the resource was not available as a resource for scheduling regular meetings.

The test resource concept is not supported.

Region

Yes

The resources were contained in the regions.

The Resource Group field.

The reservation type is configured by indicating a specific resource.

The resources are contained in the resource groups.

The resource groups are contained in the regions.


MSE 8510 Resources Field Comparisons

Table E-4 describes the Cisco TelePresence MCU MSE 8510 (MSE 8510) resources field comparisons.

Table E-4 MSE 8510 Resources Field Comparisons 

Release 1.0.(x) Field
Release 1.0.(x) Field Removed
Release 1.0.(x) Scenario
Replaced With...
Release 1.1 Scenario

Test MSE 8510

Yes

The Test check box allowed you to reserve the MSE 8510 for test meetings only. The system was not available as a resource for scheduling regular meetings.

The test resource concept is not supported.

Region

Yes

The resources were contained in the regions.

The Resource Group field.

The resources are contained in the resource groups.

The resource groups are contained in the regions.


Customers Comparisons

Table E-5 describes the region field comparisons.

Table E-5 Region Field Comparisons 

Release 1.0.(x) Field
Release 1.0.(x) Field Removed
Release 1.0.(x) Scenario
Replaced With...
Release 1.1 Scenario

Service Provider

Yes

The region was associated with any service provider.

The region is not associated with any service provider.


Table E-6 describes the organizations field comparisons.

Table E-6 Organizations Field Comparisons 

Release 1.0.(x) Field
Release 1.0.(x) Field Removed
Release 1.0.(x) Scenario
Replaced With...
Release 1.1 Scenario

Direct Dial Enabled

Yes

This check box enabled direct-dial for an organization.

The Enforce Whitelisting field.

Restrictions are enforced on direct-dial calls between this organization and other organizations under the same service provider (also known as intra-SP direct calls).


Endpoint Management Comparisons

Table E-7 describes the media profiles field comparisons.

Table E-7 Media Profiles Field Comparisons 

Release 1.0.(x) Field
Release 1.0.(x) Field Removed
Release 1.0.(x) Scenario
Replaced With...
Release 1.1 Scenario

Video Bandwidth

Yes

This optional field allowed you to specify the maximum video bandwidth for the endpoint type.

Audio Bandwidth

Yes

This optional field allowed you to set the maximum audio bandwidth available for the endpoint type.

Participant Type

Yes

This drop-down list allowed you to choose the value that corresponded to this endpoint type.

The Protocols check boxes.

You can choose one or more media protocols that are supported by this endpoint type.


Collaboration Services Comparisons

Table E-8 describes the meetings field comparisons under collaboration services.

Table E-8 Meetings Field Comparisons 

Release 1.0.(x) Field
Release 1.0.(x) Field Removed
Release 1.0.(x) Scenario
Replaced With...
Release 1.1 Scenario

Is Remote Meeting

Yes

The Is Remote Meeting field indicated a remote meeting. A yes or no value was displayed depending on the choice.

The Meeting Type field.

The Meeting Type field displays all four meeting types.

Test

Yes

The Test check box allowed the system to run test meetings. This check box was displayed only when scheduling a Meet-Me meeting.

The test resource concept is not supported.

Request Specific Resource

Yes

The Request Specific Resource check box allowed the system to display a drop-down list of available resources.

Additional Bridge Capabilities

Yes

The Additional Bridge Capabilities field allowed you to set the required bridge capabilities for unprovisioned endpoints in the meeting.

The Additional Media Profiles field.

All existing meetings, which specified additional bridge capabilities, are converted to the applicable additional media profiles.

This scenario occurs when you are modifying a future meeting that was originally scheduled before the data migration.