This procedure allows the replacement of the first generation AIM servers with the next generation 1U-19inch rack-mounted servers. A technology refresh has been carried out with new higher-spec server components used and as such, the software on the unit is substantially different from the older system.
This process describes how to upgrade your system from the older generation to the newer generation with minimal downtime. There are two methods of migrating from the 1st to 2nd Generation AIM, method 1 is recommended for installations where you have large numbers of Transmitters and Receivers (endpoints), which are spread across a large area.
If you are looking to replace a 2nd or 3rd AIM Manager, please see Replacing an AIM Manager instead.
Using the built-in migration tool in the AIM v4.0 firmware release. If you have a large number of transmitters and receivers, using the migration tool allows you to replace the AIM without the need to manually factory reset all the endpoints (transmitters and receivers). For the migration process to be successful, all the endpoints in the Transmitters and Receivers must be Online, otherwise, the process will fail. If there are any endpoints offline that can not be put back online again for the migration process, then they must be removed from the AIM Manager first.
Exporting a backup file from the original AIM Manager (minimum firmware version 3.3) and importing it to the latest AIM Manager. After which the transmitters and receivers are manually factory reset and their firmware is upgraded. All the endpoints known to the AIM will automatically be configured as per the imported backuip after they are factory reset.
Using Method 1
- The 1st Generation AIM must be upgraded to or be running at v3.3 or above and the AdderLink Infinity endpoints must be at v3.3 or above.
- The upgrade only works if the first generation AIM is running an “Unlimited License”. If it does not – an upgrade will have to be acquired. – Contact firstname.lastname@example.org if you need an unlimited license with your unique product id code.
- Until told to do so, do not connect the new AIM to the same network as the existing AIM.
- All the Transmitters and Receivers listed in the AIM must be online.
- Your new AIM server must be installed with V4.0 firmware and be fully factory reset.
- Make sure that your new AIM's license covers the number of endpoints (Transmitters and Receivers) on your system.
Step 1 - Preparation on the Existing AIM
- Ensure your first generation AIM server version 3.5 or above is on the network.
- All AdderLink Infinity Endpoints must be online.
- Make a backup of the database. Navigate to Dashboard -> Settings -> Backups. In the Backup section at the top of the page, click the Backup Now button to download a copy of the database.
- If there is only one AIM server and is running as a solo machine, it must be promoted to be a Primary. Navigate to the Servers and click on the Manage icon. In the Configure Server page, change the role from Solo to Primary. Press Save.
- Navigate to Dashboard -> Settings -> Servers. Set a Require Authentication to Yes, enter a Cluster Password and press Save.
- Connect your new AIM server version 4.0 to the network. (Powered off)
Step 2 - Migration
- Add the new AIM server version 4.0 to the network with the original server and power it on.
- Navigate to 169.254.1.3 and Login as ‘admin’ (no password required)
- Click on the Servers tab. Click on the blue ‘configured’ link (circled in red). NOTE: This link will not appear if the new AIM does detect the original AIM on the network.
- You are taken to the Servers > Configure Servers page. Press the migrate the 3.3 system button.
- The System Migration page will be displayed.
- Enter an IP Address that you wish to assign the new AIM.
- Ensure your chosen IP Address is different to your existing original AIM's IP Address and does not end with .254, as additonal backup AIM's will not be able to acquire the next IP address after this.
- Enter the cluster password that you entered into the original AIM. Note: The software does not validate the password before continuing. Make sure you enter the password correctly.
- Depending on the size of the original AIM's database, it can take anywhere from 2-5 minutes for the database to be synchronised.
- Flashing information Migration complete in green is displayed; process completed.
- This will result in the old AIM server automatically shutting itself down and the new AIM taking over.
- The old AIM server may still appear to be powered up but does not respond, power down the old AIM hardware.
- Sometimes the page times out before the migration is complete, if this happens - just reload the page.
- If at any stage you wish to revert to the old system - simply shut down the NEW AIM server, place the old system onto the network and power up.
- Once you set the new server to Primary or upgrade the firmware/software – the old server cannot be returned to the system without factory resetting all the endpoints.
- Click Servers tab. You may have to Login again as ‘admin’ (no password required)
- The new AIM must be promoted to be a Primary. Navigate to the Servers and click on the Manage icon. In the Configure Server page, change the role from Solo to Primary. Press Save.
Upgrading the AIM and Endpoints
You should now have the AIM and Endpoints working together. If you have the original ALIF1000's endpoints then you will not be able to upgrade the AIM beyond v4.0 since the firmware versions after this are not compatible. If you do not have ALIF1000's then you can upgrade the endpoints and AIM to the latest firmware version (see Compatibility Matrix). If the endpoints are not running v3.7 (or above) firmware then you will need to upgrade them to v4.4 first, see our Longevity Update page for more information. It is recommended that you upgrade the AIM to v4.9 first and then upgrade the endpoints to 4.4, and then to the latest endpoint firmware.
Using Method 2
- The AIM must be running 3.3 or 3.5. If you are running an older firmware version, please see the Original AIM Upgrade page.
- The Transmitters and Receivers must be running firmware version 3.3 or higher.
- Make a note of the firmware version installed on the Endpoints.
- Download the firmware version 4.4 and latest version for the Endpoints.
- You know the physical location for each transmitter and receiver, and they can be physically reached to manually factory reset them.
- The 2nd or 3rd Generation AIM should be running the latest firmware release and configured, but without any endpoints.
- Do not add a Backup AIM Manager until this procedure has been completed.
- Take a Backup file from the 1st Gen AIM and store the file somewhere safe.
- Power down the 1st Gen AIM Manager and remove it from the network.
- Install the 2nd Gen AIM Manager in its place, and connect it to the network.
- Power up the replacement AIM and log into its web interface.
- Navigate to Dashboard -> Backups
- In the Downloaded Backups section, click on Choose File.
- Choose the backup file taken from the 1st Gen AIM.
- Click the Upload button. It may take a minute or two to complete.
- After the AIM has imported the backup file you may notice that the Receivers and Transmitters tabs are empty and that there is a message informing you that there are receivers and transmitters that need to be firmware updated.
- You will need to manually factory reset all the Transmitters and Receivers.
- It will take approximately 3 minutes for each of the endpoints to reboot and communicate with the new AIM Manager.
- To check that the Receivers and Transmitters are online, go to the Receivers tab for example and click on the link showing the number of Receivers that need to be updated.
- In the list, there should be a green tick against each Receiver/Transmitter to confirm that it's online. Wait about 1 minute for the page to automatically refresh to ensure that the green tick remains before proceeding. If the tick changes to a red cross and 5 minutes have elapsed and it doesn't change, try factory resetting any endpoints that are not showing as being Online.
- The final stage is to upgrade the firmware on the endpoints. If any of the transmitters and receivers were running firmware older than 3,7 then they will need to be upgraded to firmware version 4.4 first, before upgrading to the latest version.