Migrating from Interchange 5.4 to Message Networking Release 2.0

This topic provides information on upgrading an Interchange 5.4 system to Message Networking Release 2.0. It is strongly recommended that you plan to do the upgrade during low usage hours. See Upgrading to Message Networking Release 2.0 for an estimate of system down time and time required to complete the migration.

Important! The following data is not migrated from the Interchange system to the Message Networking system:

• DCP and RS232 remote machines are not migrated as they are not supported on Message Networking.
• Traffic data (CDR records, log, messages in queue, etc.) and directory update data (delta records) are not migrated. Also, AMIS traffic data is now included in the system traffic reports.
• Voice channel assignments are not migrated.
• Alarm management information is not migrated. It is recommended that you record the Interchange system alarm management information for use when you register the new Message Networking system. Note that a new Alarm ID will be assigned to the Message Networking system.
• Switch selection is not migrated.

Note: In Message Networking Release 2, Enterprise Lists can be a maximum of two levels. This means that only one level of embedded lists is supported. If you are migrating an Interchange 5.4 system that includes Enterprise Lists with more than one level of embedding, you must modify the lists to have only level of embedding. For example, if List A includes List B as a member and List B includes List C as a member, you must remove List C as a member of List B and add List C as a member of List A.

Preparing for the migration

Complete the following steps before you begin the migration from Interchange 5.4 to Message Networking Release 2.0:

1. If the system is currently running a release of Interchange prior to Release 5.4, you must first upgrade your Interchange system to Release 5.4 before you can upgrade to Message Networking Release 2.0. Contact your technical representative for information on upgrading to Interchange 5.4.
2. A minimum network rate of 5 Mbps is recommended for the migration to support the large number of files that must be transferred to and from the Interchange system. A maximum rate of 10 Mbps is supported. You can test the transfer rate by using FTP to transfer a large file from the Interchange system to another system on your network.

   The time required to transfer the files depends on the size of the Interchange system and the transfer speed of the network. For example, for a system with 85,000 subscribers (65,000 with voice names), this process takes approximately 1.25 hours at 10 Mbps. For a very large system (250,000 subscribers with 120,000 voice names), the process can take up to 3 hours. If your network's transfer rate is lower than 5 Mpbs, you can proceed with the migration. However, the time required for the file transfers might be considerably longer than the example provided.

3. Obtain a temporary IP address and a DNS registered host name for the Message Networking system, and enter them on the Interchange 5.4 migration information form in the Message Networking Release 2.0 planning forms. You will enter this information on the Network Addressing page on the Message Networking system to enable you to connect to the network and transfer the necessary information to and from the Interchange 5.4 system. The Message Networking planning forms are included on the documentation CD-ROM under Reference.
4. On the Interchange 5.4 system:
   1. Record the IP Address from the TCP/IP Administration screen (Interchange Main Menu > Networking Administration > Local Machine Administration > TCP/IP Administration).
   2. Record the Domain Name from the General Parameters screen (Interchange Main Menu > Interchange Administration > System Parameters > General Parameters ).
   3. Record the alarm management settings for the system.

   Note: If there is currently no entry in the Domain Name field on the General Parameters page, obtain the domain name and enter it in the Domain Name field before proceeding. If you do not enter the Domain Name on the Interchange system, you will encounter an error during the migration because the domain name is required for Message Networking.

5. Perform a full system backup of the Interchange 5.4 system. See the Interchange 5.4 documentation for the steps you must follow to perform a system backup. The time required to complete the backup depends on the size of the Interchange system database and can range from 30 minutes to 2 hours.
6. As noted earlier, DCP and RS232 remote machines are not migrated as they are not supported on Message Networking. If there are DCP or RS232 remote machine that you want to be converted for use with Message Networking, convert them to AMIS Analog or TCP/IP machines before you begin the migration. If you do not want the DCP and RS232 remote machines to be converted for use with Message Networking, delete them before you perform the migration. Deleting remote machines that you do not want to use with Message Networking decreases the amount of time required to FTP system information from Interchange to Message Networking.

Performing the migration

To migrate from Interchange 5.4 to Message Networking Release 2.0, you must complete the following steps:

1. Complete the preinstallation requirements.
2. Unpack the system.
3. Identify the server components.
4. Install the system hardware.
5. Power up the system.
6. Log into the system from the console.
7. Set the time and date.
8. On the Network Addressing page, complete the IP Address, Host Name, and Primary Name + Domain fields, using the temporary information you obtained for the Message Networking system.
9. To verify that the Message Networking system is available through the network, logging into the system as craft from another PC on the network. When you verify that the system is available through the network, log off and then exit the browser.
10. Install additional language software (if needed).
11. Install the switch connection software (required for analog systems).
12. Check the system status.
13. Activate the modem/terminal.
14. Transfer data from the Interchange system to the Message Networking system:
    1. On the Message Networking Release 2.0 system, log in as tsc from the console, but do not start the web administration interface.
    2. From the command prompt, type /ichg/IC_upgrade/trans_MN_script_to_IC <Interchange IP address> <Interchange tsc password> and then press Enter. For example: /ichg/IC_upgrade/trans_MN_script_to_IC 135.9.54.123 mytscpw.

       This command transfers the necessary scripts to the Interchange system.

    3. Log out of the Message Networking system.
    4. On the Interchange system, log in as tsc.
    5. From the Interchange command prompt, type ksh trans_IC_data_to_MN <temporary MN system IP address> <Message Networking tsc password> and then press Enter. For example: ksh trans_IC_data_to_MN 135.9.54.124 mytscpw

       This command stops the Interchange voice system, collects the necessary Interchange data, and transfers it to the Message Networking system. The time it takes to transfer the files depends on the size of the Interchange system and the transfer speed of the network. For example, for a system with 85,000 subscribers (65,000 with voice names), this process takes approximately 1.25 hours. For a very large system (250,000 subscribers with 120,000 voice names), the process can take up to 3 hours.

       The output of the transfer is logged in a file called migration.log, which is stored in the /voice2 directory on the Interchange system. If the /voice2 directory is full, the system displays a message indicating where the log file is stored. This log file is useful if you encounter issues during this step.

    6. After you see the message on the Interchange system that the transfer was successful, log out of the Interchange system.
    7. If you want to bring the Interchange system back into service while you complete the upgrade on the Message Networking system, do so now by typing start_vs from the Interchange system command prompt.
    8. On the Message Networking system, log in as tsc from the console, but do not start the web administration interface.
    9. From the command prompt, type /ichg/IC_upgrade/load_IC_data and then press Enter.

       This command stops the Message Networking voice system, converts all of the Interchange data that you transferred for use with Message Networking, and imports all of the data into the Message Networking system database. The time to complete this process depends on the amount of data that was transferred from the Interchange system, but it should take no more than 1 hour.

       The output of the transfer is logged in a file called load_IC_data.log, which is stored in the /voice2 directory on the Message Networking system.

    10. If there was no domain name administered on the Interchange system, the following error message displays:

        .set_na_parms: ERROR -- Five arguments are required!!
USAGE:.set_na_params: interface ip_name ip_address netmask speed_duplex_flag

        If this message displays, press q to quit and continue with Step k. You will need to enter the host and domain name and the IP address of the original Interchange system on the Networking Addressing page of the Message Networking system later.

    11. When you see a message on the Message Networking system that the process is complete, shut down the Interchange system and disconnect it from the network.
    12. Reboot the Message Networking system.
15. Perform voice system administration.
16. Perform switch selection (analog systems).
17. If you encountered the error message described in Step 14j:
    1. Modify the /etc/hosts file to remove the IP address of the Interchange system. If you do not remove the IP address, you will encounter an error when you administer Networking Addressing that the IP address is already assigned.
    2. Administer Network Addressing to enter the Host, Primary Name + Domain, and the IP Address.
18. Check the following pages on the Message Networking system to verify that the information was successfully migrated from the Interchange system:

    Note: Fields on Message Networking pages that were not supported for Interchange are set to the system defaults.
    

    • Customer Options: Verify that the settings were correctly transferred from the Interchange system.

      Note: If you migrate to Message Networking on an S3400-H server, all features are activated.

    • General Parameters:
      • Verify that the settings were correctly transferred from the Interchange system.
      • Specify a password in the LDAP Password field. An LDAP Password is required for the local Message Networking system and LDAP remote machines (Modular Messaging and Message Networking systems) to secure the connection when performing LDAP queries.
      • Set the Block MM to MM Updates field to the appropriate setting for your network. This field indicates whether you want block subscriber updates between Modular Messaging remote machines through Message Networking. If the Modular Messaging systems in the network are configured for point-to-point networking, set this field to Yes.
    • Remote Machines List: Verify that the remote machines previously administered on the Interchange system are resident on the Message Networking system.
    • Remote Machine Dial Plan List: Verify that the remote machine dial plans previously administered on the Interchange system are resident on the Message Networking system.
    • Subscriber Count: Verify that the correct number of subscribers were transferred to the Message Networking system.
    • Voice system status: Verify that all ports are in service.
19. Prior to the migration, any Message Networking systems administered on the Interchange system were administered as Interchange remote machines. You must now convert those Interchange remote machines administered on the newly migrated systems to Message Networking remote machines.
20. You must also convert the newly migrated Interchange remote machine to a Message Networking remote machine on any Message Networking systems in the network on which the Interchange system is administered.
21. Perform LDAP and SMTP connectivity between both systems after they are converted.
22. Complete the following acceptance testing:
    • Testing voice ports
    • Calling Message Networking ports
    • Testing remote machine connectivity for other systems (non LDAP and SMTP) between the Message Networking system and remote machines
    • Sending a test message to a remote subscriber
23. Unregister the Interchange 5.4 system.
24. Register the Message Networking system as a new system.
25. On the migrated Message Networking system, perform a demand remote update for the Message Networking systems that you converted from an Interchange remote machine type to a Message Networking remote machine type in Step 19.

    The system begins transcoding subscriber voice names into .wav format as part of the migration to Message Networking. This process can take several hours depending on the number of voice names on the system. For example, on a system with 65,000 voice names, the process takes approximately four hours.

26. If you migrated an Interchange system in a network with no existing Message Networking systems, the new Message Networking system is ready for service. Note that the transcoding of subscriber voice names might still be ongoing.

    Caution! If there was at least one Message Networking system already in the network before the migration, it is important that you only pull other MN LDAP updates into the migrated Message Networking system. Do not yet request an LDAP update from the migrated Message Networking system.) Also, do not perform any remote machine administration, such as adding new remote machines or performing remote updates until the transcoding of subscriber voice names in .wav format is complete.

27. If you migrated an Interchange system in a network with other existing Message Networking systems, after the transcoding completes, perform a demand remote update from the other Message Networking systems in the network to pull an LDAP update from the newly migrated Message Networking system.

Top of page