|
|
The uOne Corporate Edition 4.1E product structures the uOne platform of services on a separate system from CallManager 3.0 service, allowing up to 20 sessions of uOne and 500 users. If you are currently using uOne Entry Edition 4.1E on a single system (MCS-7830), you must migrate your current uOne platform to the new corporate system, utilizing an MCS-7835. Because the uOne Corporate Edition 4.1E installation includes the configuration of your system to use 20 sessions of uOne, the need to purchase an upgrade for additional sessions for your system is eliminated.
This chapter will includes the following topics in the migration process:
The migration of your existing uOne software to utilize the Corporate Edition is shown in Figure 4-1. The uOne Entry Edition 4.1E components were installed on the same server as CallManager. The Corporate Edition moves the uOne components onto a separate MCS-7835 system, with CallManager 2.4 remaining on the existing MCS-7830 system. The migration includes a manual process to transfer the information in your existing directory server and messaging server, as well as the underlying configuration files, to the new Corporate Edition platform. The uOne Corporate Edition 4.1E is then configured to communicate with the existing CallManager server.
To migrate your CallManager 2.4 system to CallManager 3.0, see the Installing Cisco CallManager Release 3.0 on the Cisco Media Convergence Server manual.
The following procedures will migrate your current uOne system to the two-box solution of uOne Corporate Edition 4.1E, using CallManager 3.0.
 |
Note It is highly recommended that you back up your existing uOne system prior to performing this migration. This prevents data loss and ensures you can recreate the system in an emergency. |
For the purpose of these instructions, the existing system using the single-box uOne platform is referred to as the Entry Server. The newly-configured system which will hold the upgraded uOne Corporate Edition 4.1E is referred to as the Corporate Server.
Please check that the following have been completed prior to the migration of uOne directory servers:
|
Note These instructions assume that both the Entry Server and Corporate Server have been properly set up and shared on the same network system. |
Follow these steps to export the LDIF information from the Entry Server.
Step 2 To log onto Netscape's Administrative Server on port 2500, using admin/admin, select Start from the Windows Taskbar, then select Programs.
Step 3 From the Programs menu, select Netscape SuiteSpot, then Administration.
Step 4 Open the Netscape Directory Server by clicking the <machine name> button (for example, uOne2).
Step 5 Click the Database Management button.
Step 6 Click the Export hyperlink to the left of the window.
Step 7 You will be prompted to shut down the services before proceeding. Click OK to shut down the services. Click on Go Back after the services have been shut down.
Step 8 When the Apply Changes prompt appears, click the Apply Manual Changes button at the bottom of the window.
Step 9 Enter the .ldif export filename necessary for transferring the information to the Corporate Server. (The system will automatically use the c:\Netscape\Suitespot\slapd-hostname\ldif\ path.) For example:
Step 10 After entering a name for the export file, click OK.
Follow these steps to copy the LDIF information to the Corporate Server.
Step 2 On the Corporate Server, select Start from the Windows Taskbar, then select Run.
Step 3 At the Run prompt, type in Wordpad. This will create a Wordpad session window which should allow you to edit the newly copied .ldif file.
Step 4 From within Wordpad, on the File menu, select Open and navigate to the path for the newly copied .ldif file: C:\Netscape\Suitespot\slapd-hostname\ldif\exportfile.ldif. Select Open.
Step 5 Using the Replace feature found under the Edit menu, perform a global search and replace. Replace all instances of the old hostname (the hostname of the Entry Server) with the new host name (the hostname for the Corporate Server). The domain name should not be edited.
Step 6 After replacing the hostname, from the Wordpad menu, select File, Save As and enter a new name for the document, such as exportfile1.ldif.
Step 7 Select File, Exit to close Wordpad.
Import the LDIF information by performing the following steps on the Corporate Server.
Step 2 From the Programs menu, select Netscape SuiteSpot, then Administration.
Step 3 Open the Netscape Directory Server by clicking the <machine name> button (for example, uOne1).
Step 4 Select Database Management button.
Step 5 Click the Import hyperlink.
Step 6 You will be prompted to shut down the services before proceeding. Click OK to shut down the services. Click Go Back after the services have been shut down.
Step 7 Select the new .ldif file :
Step 8 Click OK after selecting the filename.
Stop the services on the Entry Server as follows.
Step 2 Choose Start from the Windows Taskbar, then Control Panel, then Services.
Step 3 Select uTel and choose Stop from the buttons on the right side of the window. This process notifies you that it will stop not only uTel, but also uLite, uLogRemover, uOne and uPilot. Click OK.
Step 4 Select Apache Web Server, and click the Stop button.
Step 5 Select Netscape Messaging Server 3.6, and click the Stop button.
Step 6 Select Netscape Directory Server 3.1, and click the Stop button.
Step 7 Select Netscape Administration Server 3.5, and click the Stop button.
Step 8 Close the Services dialog box, then close Control Panel.
Stop the services on the Corporate Server as follows.
Step 2 Choose Start from the Windows Taskbar, then Control Panel, then Services.
Step 3 Select uTel and choose Stop from the buttons on the right side of the window. This process notifies you that it will stop not only uTel, but also uLite, uLogRemover, uOne and uPilot. Click OK.
Step 4 Select Netscape Administration Server 3.5, and click the Stop button.
Step 5 Select Netscape Directory Server 3.1, and click the Stop button.
Step 6 Select Netscape Messaging Server 3.6, and click the Stop button.
Step 7 Select Apache Web Server, and click the Stop button.
Step 8 Close the Services dialog box, then close Control Panel.
On the Corporate Server, set up the directory information using the following steps.
Step 2 Rename the Mailbox subdirectory to Mailbox_old.
Step 3 Rename the Spool subdirectory to Spool_old.
Step 4 Be sure that the Corporate Server is shared with the network system.
On the Entry Server, set up the directory information using the following steps.
Step 2 From the menu select Tools, then Map Network Drive...
Step 3 In the Path field, insert the Corporate Server address using \\ipaddress\C$ command, where ipaddress is the network location for the Corporate Server. If you are prompted for a password, enter the login and password information for the Corporate Server.
Step 4 Copy all files from the Entry Server c:\Netscape\Suitespot\Mailserver\ directory to the c:\Netscape\Suitespot\Mailserver directory on the Corporate Server.
|
Note If you are not logged into this system as admin, you will have difficulty accessing the Mailserver files. |
On the Corporate Server, perform the following steps.
Step 2 At the Run prompt, type in Wordpad.
Step 3 From within Wordpad, on the File menu select Open and navigate to the following file: C:\Netscape\Suitespot\Mailserver\Spool\sie.conf
Step 4 Select Open.
Step 5 Using the Replace feature found under the Edit menu, perform a global search and replace. Replace both instances of the old hostname (the hostname of the Entry Server) with the new host name (the hostname for the Corporate Server). The domain name should not be edited.
Step 6 Close and save the document, replacing the original.
Step 7 Close Wordpad.
The following procedures will copy the configuration files from the Entry Server to the Corporate Server:
On the Corporate Server, do the following.
Step 2 Back up the installation version of the C:\CiscoSystems\uOne\Parms\ directory files.
Step 3 Using Windows Explorer, map a network drive to the Entry Server.
Step 4 Copy all files from the Entry Server C:\CiscoSystems\uOne\Parms\ directory to the C:\CiscoSystems\uOne\Parms\ directory on the Corporate Server.
On the Corporate Server, do the following.
Step 2 At the Run prompt, type in Wordpad.
Step 3 From within Wordpad, on the File menu select Open and navigate to the parms path for the .ini files: C:\CiscoSystems\uOne\Parm\uOne.ini.
Step 4 Select Open.
Step 5 In the LDAPConfig section of the uOne.ini file, change the value of the LDAPhost to the fully qualified domain name of the Corporate Server.
Step 6 Save and close the document, replacing the original.
Step 7 Close Wordpad.
Before restarting either system, change the properties for the Netscape Services.
On the Entry Server, the services should be changed to manual start as follows.
Step 2 Double-click Netscape Administration Server 3.5, and set to Manual Start.
Step 3 Double-click Netscape Directory Server 3.1, and set to Manual Start.
Step 4 Double-click Netscape Messaging Server 3.6, and set to Manual Start.
Step 5 Double-click Apache Web Server, and set to Manual Start.
Step 6 Close the Services dialog box, then close Control Panel.
On the Corporate Server, the services should be changed to Autostart as follows.
Step 2 Double-click Netscape Administration Server 3.5, and set to AutoStart.
Step 3 Double-click Netscape Directory Server 3.1, and set to AutoStart.
Step 4 Double-click Netscape Messaging Server 3.6, and set to AutoStart.
Step 5 Double-click Apache Web Server, and set to AutoStart.
Step 6 Close the Services dialog box, then close Control Panel.
You can now restart the new Corporate Server to test the migration functionality.
After completing the migration, you can test the system by dialing the Cisco Voice messaging Pilot Number on any IP phone. If you hear the system voice greeting, then you have been successful. You can further test the system by dialing an individual voice mailbox and making sure that the number dialed has the correct personal greeting.
Posted: Mon Jul 10 13:09:53 PDT 2000
Copyright 1989-2000©Cisco Systems Inc.