Migrating ShoreTel HQ to new Server Hardware and New IP Address

This an application note on how to migrate an existing HQ server to a new hardware platform with a new IP address change

Pre migration Tasks

• Make sure the customer understands and updates their Option 156 in the DHCP scope to point to the new server.
  
• Have the customer put the new server online with the new IP address.
  
• Verify that you have remote access to the new server
  
• Make sure or verify that the operating system and hardware meets the specifications of the version of software you are going to install.
  
• With remote access ensure that all the features and roles have been turned on and installed on the new system
  
  • Ensure that you have Telnet client installed on the new server for remote Telnet access to the switches.
    
• Ensure that you have setup the SMTP relay on the new server
  
• Create a shared folder on the new server with read/write access. You are going to use this share from the old platform to copy the old information over.
  
• Create a local administrator account on the system to match our company wide logins
  
• Download the exact same version of software as on the old server. You can copy the install folder over to the new server using the shared drive you just created.
  
  • Since this is an HQ IP address change you will need to make sure that you have pre-downloaded all the Remote Server software on all their DVS locations.
    
  • The customer has bodies available for the remote sites so that they can provide a serial connection into any remote switches that need to be reconfigured
    
• Copy or download the Install folder off our FTP site and put it on the new server
  
• Once the new system has all the previous steps completed, You can install a fresh install of the Shoreware Server software on the system.
  
• Once the software has been installed, remote int and make sure that the Shoreware Director is running with no configuration.
  
• Stop all the ShoreTel services on the new server. This can be accomplished by running quickinstall –stopall in the C:program files (x86)Shoreline CommunicationsShoreware Server directory.
  
  • You can also navigate to the C:program files (x86)Shoreline CommunicationsShoreware Server directoryScripts> and run the hq_shoretel-stop-svcs.bat
    

Pre Migration backup

Allow yourself about 1 hour prior to the migration to run a backup. This will accommodate for large systems and will prevent you from missing the start time of the maintenance window.

Run the Lantelligence Backup Scripts for the appropriate version of software they are running. This will create a C;Shoreware Backup folder on the older server.

Once you have the MySql ShoreTel config file, open this file up in a text editor. Search for SOFTSWITCH and change the old IP address to the new server IP address and save the file.

Once completed copy over the folders via the shared folder you create or upload to LANtelligence FTP site. This may take some time so allow yourself the time for the backup and for the moving of the files.

Start of Migration

Since we are migration the HQ server and changing the IP address the following will have to occur:

• All the DVS servers will have to be re-pointed to the new HQ server. This is most effectively achieved from uninstalling, rebooting, reinstalling and rebooting the remote server software.
  
• All switches will have to be re-pointed to the new HQ server. This may auto update for some switches but in the case that is does not you will have to Telnet or SSH into the remote switches.
  
  • You will need to have server online to be able to telnet to the older switches.
    
  • You may also have to initiate the Telnet from the previous Servers Shoreline CommunicationsShoreware Server directory if the switches won’t authenticate your telnet session from the new server IP address
    
• The customer will have to change their DHCP options Scope 156 to update the phones to point to the new FTP server address. Therefore when you reboot the phones they all come back up and point to the new server address
  
• Stop all the ShoreTel services on the old server. This can be accomplished by running quickinstall –stopall in the C:program files (x86)Shoreline CommunicationsShoreware Server directory.
  
  • You can also navigate to the C:program files (x86)Shoreline CommunicationsShoreware Server directory Scripts> and run the hq_shoretel-stop-svcs.bat
    
• Using SQLyog connect to the new Shoreware DB on the new server (root/shorewaredba port 4308)
  
  • Import the ConfigSQL.sql into the ShoreTel DB
    
  • Import the ShorewareBridge.sql into the ShoreTel DB
    
• Using SQLyog connect to the ShorewareCDR db an import the ShorewareCDR.sql dump file into the db
  
• Then in the Shoreware Backup folder copy and paste the following directories over the existing ones in the C:Shoreware Data folder
  
  • Prompts
    
  • User Data
    
  • VMS
    
• Once all the folders have been copied over and the DB has been imported, restart the ShoreTel services
  
  • Start all the ShoreTel services on the new server. This can be accomplished by running quickinstall –startall in the C:program files (x86)Shoreline CommunicationsShoreware Server directory.
    
    • You can also navigate to the C:program files (x86)Shoreline CommunicationsShoreware Server directory Scripts> and run the hq_shoretel-start-svcs.bat
      
• You may be able to start services and be okay, but you may have to reboot the server to ensure that the services do come back up.
  
• Login to the system and verify that the new servers Shoreware Director appears to have the configuration of the old server.
  

DVS locations

Remote into the remote locations and uninstall the Remote Sever Software on all their DVS systems. You can run all the uninstalls concurrently.

To avoid later reboots, if possible you should leave the switches with their new server address saved on the switch but do not reboot until the DVS servers are back online. If you do because the customer needs some functionality, you will eventually have to reboot the switches and the DVS’ later on in the process to ensure they are communicating.

Once the DVS servers have finished their unistalls, reboot the machines.

When the DVS servers have come back online, run the installation of the remote software on the server. You will be prompted to enter the new HQ server IP address.

Once the software finishes, reboot the DVS one last time.

ShoreTel Switches

Once all the DVS servers have come back online it is time to reboot any switches that have the new server address and update the remaining switches with the new server address.

ShoreTel phones

Once the switches have reconnected, you will need to remotely reboot all the IP phones on the new system. The phones will not come up unless they grab the new DHCP scope with the new server address.

Post Migration tasks

As with any upgrade or migration we need to test to ensure that all the settings have taken and that the system is fully operational as it was prior to the migration:

• Have customer test voice mail on their phones, can they login
  
• Dial into the main numbers at each site to ensure that the local Auto Attendants and greetings play
  
• Check the Quick Look and Connectivity screens to ensure that everything is green and has reconnected
  
• Make sure the SMTP relay address have been added to the server
  
• Using the Trunk Test tool make outbound calls out of each set of customer trunks to verify that both outbound and inbound (calling the AA’s step from above) is working.
  
• Call a few DID numbers to ensure they are going to the correct person and that person’s voice mail