HTTPS Networking Guide for Cisco Unity Connection Release 10.x - Migration from Legacy network to HTTPS network [Cisco Unity Connection]

Table Of Contents

Migration from Legacy network (i.e. Intrasite or Intersite) to HTTPS network

Prerequisites for migration from legacy to HTTPS network

Task list to migrate from Legacy network to HTTPS network using Flash Cut Approach

Migration from Legacy network (i.e. Intrasite or Intersite) to HTTPS network

From Unity Connection release 10.x onwards, two or more Unity Connection servers or clusters can be connected through HTTPS links in a hub-spoke topology to form a single site network, referred to as an HTTPS Unity Connection network.

Migration from legacy network to HTTPS network can be done using a flash-cut approach which includes unjoining the existing network and then joining the locations in a pre-decided network topology.

A downtime window is required for the migration activity, which varies depending on the number of locations and the directory size; hence it should be planned during off-hours or over the weekend. Since legacy links are not supported in HTTPS networking, the entire network should collectively be migrated to the HTTPS network.

Prerequisites for migration from legacy to HTTPS network

Before proceeding with the migration activity, ensure the following prerequisites have been met on each server that will join in the HTTPS network (for clusters, verify these prerequisites for the publisher server):

• For a Unity Connection site, the directory replication is working fine and none of the locations have stalled replication. Unity Connection SMTP server and Connection Digital Networking Replication Agent services are up and running. Visit http://www.cisco.com/en/US/docs/voice_ip_comm/connection/10x/serv_administration/guide/10xcucservag040.html for more details on description and management of Cisco Unity Connection Services.

•All locations in the network are in synchronization with each other.

•For Intrasite links, this can be determined as mentioned in section "Checking Replication Status Within a Site" of http://www.cisco.com/en/US/docs/voice_ip_comm/connection/10x/networking/guide/10xcucnet020.html .

•For Intersite links, see section "Checking the Status of Synchronization Between Cisco Unity Connection Sites And Configuring Task Schedules" of http://www.cisco.com/en/US/docs/voice_ip_comm/connection/10x/networking/guide/10xcucnet020.html . Verify that the latest synchronization task has completed without any errors.

• Upgrade all the locations to connection release 10.x. The HTTPS networking feature is available only from release 10.x onwards. See http://www.cisco.com/en/US/docs/voice_ip_comm/connection/10x/upgrade/guide/10xcucrug010.html for upgrading a network location to 10.x version.

•After upgrade, take a data backup for all locations in the legacy network. See http://www.cisco.com/en/US/docs/voice_ip_comm/connection/10x/drs_administration/guide/10xcucdrsag.html which provides an overview of the Disaster Recovery System, describes how to use the Disaster Recovery System, and provides procedures for completing various backup-related tasks and restore-related tasks.

• The network administrator needs to decide the HTTPS network topology and arrangement of Unity Connection servers prior to the migration of the network. See section "Deciding the Network Topology" at Setting up an HTTPS Network Between Cisco Unity Connection 10.0(1) Servers.

Task list to migrate from Legacy network to HTTPS network using Flash Cut Approach

After ensuring that the conditions specified in Prerequisites for migration from legacy to HTTPS network section are met, proceed with the following steps to migrate the network:

Step 1 On each Unity Connection location in the network, take a backup of distribution lists, both public and private, and distribution list members that are homed at that location. The Distribution List Syncher tool can be used for this purpose. For more information on the tool visit: http://www.ciscounitytools.com/Applications/CxN/DistributionListBuilderCsv/DistributionListBuilderCsv.html.

Step 2 Schedule the task "Update Database Statistics" to run every 2 hours. Visit http://www.cisco.com/en/US/docs/voice_ip_comm/connection/10x/gui_reference/guide/10xcucgrg130.html for details regarding task definitions, task definition basics and task schedules.

Step 3 Unjoin the locations in the network. It is recommended to unjoin only two locations at a time from the network, since unjoining more locations increases the SMTP traffic during replication and can halt replication.

See section Removing a Location From a Cisco Unity Connection 10.x site of http://www.cisco.com/en/US/docs/voice_ip_comm/connection/10x/networking/guide/10xcucnet040.html for steps to unjoin an Intrasite network. It is also recommended that the Intrasite links be removed using Remove Self from Site option as mentioned in section Search Intrasite Links section of Interface Reference Guide of Cisco Unity Connection Administration at http://www.cisco.com/en/US/docs/voice_ip_comm/connection/10x/gui_reference/guide/10xcucgrg080.html.

Also see section Removing an Intersite Link Between Two Cisco Unity Connection 10.x Sites at http://www.cisco.com/en/US/docs/voice_ip_comm/connection/10x/networking/guide/10xcucnet040.html for steps to unjoin an Intersite network.

Step 4 Schedule the "Update Database Statistics" task to run at its default time. See http://www.cisco.com/en/US/docs/voice_ip_comm/connection/10x/gui_reference/guide/10xcucgrg130.html for details regarding task definitions, task definition basics and task schedules.

Step 5 Take a DRS backup of all the locations. See http://www.cisco.com/en/US/docs/voice_ip_comm/connection/10x/drs_administration/guide/10xcucdrsag.html which provides an overview of the Disaster Recovery System, describes how to use the Disaster Recovery System, and provides procedures for completing various backup-related tasks and restore-related tasks.

Step 6 Join the locations in HTTPS network as per the topology decided by the network administrator and allow the directory replication to complete. See Setting Up an HTTPS Network Between Cisco Unity Connection 10.0(1) Servers for details regarding joining locations in HTTPS network and verifying the synchronization status.

Step 7 In an HTTPS network, by default the system distribution lists and its members are not synchronized between the locations in the network. To enable the synchronization of distribution lists and its members, of a particular Unity Connection location, you need to check the Include distribution lists and membership when synchronizing directory data check box on the Edit HTTPS Link page of the corresponding location. For more information, see the section "Edit HTTPS Link" of Interface Reference Guide Release 10.x at http://www.cisco.com/en/US/docs/voice_ip_comm/connection/10x/gui_reference/guide/10xcucgrgx.html.

It is recommended that synchronization of distribution list should be initiated after the completion of first directory synchronization cycle.

If you enable the Include distribution lists and membership when synchronizing directory data check box on one location in the network, it is recommended to check the check box on all the locations in the network.

Caution When you enable system distribution list synchronization, you cannot disable it afterwards, except by removing and recreating the HTTPS link.

Allow the directory synchronization to complete after enabling the checkbox on the locations.

Step 8 Once the directory replication is complete, start restoring the public and private distribution lists from the backup taken in step 1. The Distribution List Syncher tool can be used for this purpose. For more information on the tool see: http://www.ciscounitytools.com/Applications/CxN/DistributionListBuilderCsv/DistributionListBuilderCsv.html .

Step 9 After restoring distribution lists and distribution list members from the backup, allow the directory replication to complete between the locations.

	HTTPS Networking Guide for Cisco Unity Connection Release 10.x
	Migration from Legacy network to HTTPS network
HTTPS Networking Guide for Cisco Unity Connection Release 10.x Index Preface Overview of HTTPS Networking in Cisco Unity Connection 10.x Setting Up an HTTPS Network Between Cisco Unity Connection 10.x Servers Migration from Legacy network to HTTPS network Making Changes to the HTTPS Networking Configuration in Cisco Unity Connection 10.x Cross-Server Sign-In, Transfers, and Live Reply in HTTPS Networking 10.x	Download this chapter Migration from Legacy network to HTTPS network Download the complete book PDF version of the Entire Guide (PDF - 1 MB) Feedback Table Of Contents Migration from Legacy network (i.e. Intrasite or Intersite) to HTTPS network Prerequisites for migration from legacy to HTTPS network Task list to migrate from Legacy network to HTTPS network using Flash Cut Approach Migration from Legacy network (i.e. Intrasite or Intersite) to HTTPS network From Unity Connection release 10.x onwards, two or more Unity Connection servers or clusters can be connected through HTTPS links in a hub-spoke topology to form a single site network, referred to as an HTTPS Unity Connection network. Migration from legacy network to HTTPS network can be done using a flash-cut approach which includes unjoining the existing network and then joining the locations in a pre-decided network topology. A downtime window is required for the migration activity, which varies depending on the number of locations and the directory size; hence it should be planned during off-hours or over the weekend. Since legacy links are not supported in HTTPS networking, the entire network should collectively be migrated to the HTTPS network. Prerequisites for migration from legacy to HTTPS network Before proceeding with the migration activity, ensure the following prerequisites have been met on each server that will join in the HTTPS network (for clusters, verify these prerequisites for the publisher server): • For a Unity Connection site, the directory replication is working fine and none of the locations have stalled replication. Unity Connection SMTP server and Connection Digital Networking Replication Agent services are up and running. Visit http://www.cisco.com/en/US/docs/voice_ip_comm/connection/10x/serv_administration/guide/10xcucservag040.html for more details on description and management of Cisco Unity Connection Services. •All locations in the network are in synchronization with each other. •For Intrasite links, this can be determined as mentioned in section "Checking Replication Status Within a Site" of http://www.cisco.com/en/US/docs/voice_ip_comm/connection/10x/networking/guide/10xcucnet020.html . •For Intersite links, see section "Checking the Status of Synchronization Between Cisco Unity Connection Sites And Configuring Task Schedules" of http://www.cisco.com/en/US/docs/voice_ip_comm/connection/10x/networking/guide/10xcucnet020.html . Verify that the latest synchronization task has completed without any errors. • Upgrade all the locations to connection release 10.x. The HTTPS networking feature is available only from release 10.x onwards. See http://www.cisco.com/en/US/docs/voice_ip_comm/connection/10x/upgrade/guide/10xcucrug010.html for upgrading a network location to 10.x version. •After upgrade, take a data backup for all locations in the legacy network. See http://www.cisco.com/en/US/docs/voice_ip_comm/connection/10x/drs_administration/guide/10xcucdrsag.html which provides an overview of the Disaster Recovery System, describes how to use the Disaster Recovery System, and provides procedures for completing various backup-related tasks and restore-related tasks. • The network administrator needs to decide the HTTPS network topology and arrangement of Unity Connection servers prior to the migration of the network. See section "Deciding the Network Topology" at Setting up an HTTPS Network Between Cisco Unity Connection 10.0(1) Servers. Task list to migrate from Legacy network to HTTPS network using Flash Cut Approach After ensuring that the conditions specified in Prerequisites for migration from legacy to HTTPS network section are met, proceed with the following steps to migrate the network: Step 1 On each Unity Connection location in the network, take a backup of distribution lists, both public and private, and distribution list members that are homed at that location. The Distribution List Syncher tool can be used for this purpose. For more information on the tool visit: http://www.ciscounitytools.com/Applications/CxN/DistributionListBuilderCsv/DistributionListBuilderCsv.html. Step 2 Schedule the task "Update Database Statistics" to run every 2 hours. Visit http://www.cisco.com/en/US/docs/voice_ip_comm/connection/10x/gui_reference/guide/10xcucgrg130.html for details regarding task definitions, task definition basics and task schedules. Step 3 Unjoin the locations in the network. It is recommended to unjoin only two locations at a time from the network, since unjoining more locations increases the SMTP traffic during replication and can halt replication. See section Removing a Location From a Cisco Unity Connection 10.x site of http://www.cisco.com/en/US/docs/voice_ip_comm/connection/10x/networking/guide/10xcucnet040.html for steps to unjoin an Intrasite network. It is also recommended that the Intrasite links be removed using Remove Self from Site option as mentioned in section Search Intrasite Links section of Interface Reference Guide of Cisco Unity Connection Administration at http://www.cisco.com/en/US/docs/voice_ip_comm/connection/10x/gui_reference/guide/10xcucgrg080.html. Also see section Removing an Intersite Link Between Two Cisco Unity Connection 10.x Sites at http://www.cisco.com/en/US/docs/voice_ip_comm/connection/10x/networking/guide/10xcucnet040.html for steps to unjoin an Intersite network. Step 4 Schedule the "Update Database Statistics" task to run at its default time. See http://www.cisco.com/en/US/docs/voice_ip_comm/connection/10x/gui_reference/guide/10xcucgrg130.html for details regarding task definitions, task definition basics and task schedules. Step 5 Take a DRS backup of all the locations. See http://www.cisco.com/en/US/docs/voice_ip_comm/connection/10x/drs_administration/guide/10xcucdrsag.html which provides an overview of the Disaster Recovery System, describes how to use the Disaster Recovery System, and provides procedures for completing various backup-related tasks and restore-related tasks. Step 6 Join the locations in HTTPS network as per the topology decided by the network administrator and allow the directory replication to complete. See Setting Up an HTTPS Network Between Cisco Unity Connection 10.0(1) Servers for details regarding joining locations in HTTPS network and verifying the synchronization status. Step 7 In an HTTPS network, by default the system distribution lists and its members are not synchronized between the locations in the network. To enable the synchronization of distribution lists and its members, of a particular Unity Connection location, you need to check the Include distribution lists and membership when synchronizing directory data check box on the Edit HTTPS Link page of the corresponding location. For more information, see the section "Edit HTTPS Link" of Interface Reference Guide Release 10.x at http://www.cisco.com/en/US/docs/voice_ip_comm/connection/10x/gui_reference/guide/10xcucgrgx.html. It is recommended that synchronization of distribution list should be initiated after the completion of first directory synchronization cycle. If you enable the Include distribution lists and membership when synchronizing directory data check box on one location in the network, it is recommended to check the check box on all the locations in the network. Caution When you enable system distribution list synchronization, you cannot disable it afterwards, except by removing and recreating the HTTPS link. Allow the directory synchronization to complete after enabling the checkbox on the locations. Step 8 Once the directory replication is complete, start restoring the public and private distribution lists from the backup taken in step 1. The Distribution List Syncher tool can be used for this purpose. For more information on the tool see: http://www.ciscounitytools.com/Applications/CxN/DistributionListBuilderCsv/DistributionListBuilderCsv.html . Step 9 After restoring distribution lists and distribution list members from the backup, allow the directory replication to complete between the locations.
	Terms & Conditions \| Privacy Statement \| Cookie Policy \| Trademarks