How to update iProtect to 10.3
- Arnout van Wanrooij
- MB
- Lennert
How To Article | HTA-20230623-AVW-01 iProtect Access / Security | How To Articles | How to update iProtect to 10.3  |
|
- 1 How to update the iProtect™ Application.
- 2 Some points to check at the end of the update:
How to update the iProtect™ Application.
Introduction
This how-to guide provides you with instructions on how to update your iProtect system to the latest 10.03 version, allowing you to take advantage of the latest improvements and features.
Software
The required operating system version for iProtect:
Version | O.S./ Firmware | Internet connection required |
iProtect 10.3 | Ubuntu 20.04 LTS | Yes, for installation and updates |
Update workflow
The workflow described above specifies that the iProtect system can only be upgraded from version 10.01.x to version 10.03. If your current iProtect version is below 10.01.37, please consult the documentation available at *How to update iProtect™ to 10.1 before proceeding.
To upgrade from version 10.01 to 10.03, you need to first set up a new Ubuntu 20.04 server with the latest version 10.03 installed (follow the instructions provided below). Once this step is complete, you can upload the backup file from your 10.01 installation, which will restore your data. For detailed information on restoring a backup, please refer to *How to Restore an iProtect backup.
If you are currently running version 10.02, you can simply upload the latest 10.03 package to complete the upgrade; please see the instructions below.
Download files
Download the latest files on our download section of the knowledge base:
iProtect Serverbox
IProtect Database
*iProtect™ - Software Downloads | Version 10.3
Pre-checks
Before the update it is required that the state of the system is known. Not functioning readers, nodes and lines must be noted. If possible, restore the connections first, if this is not possible, then put the relevant lines inactive. Check and test database couplings and other custom intergrations, it's best to test them on a 10.3 test-system first to see if they work or still need adjustments first.
Compatibility and discontinued hardware/software is noted in the release notes:
Minimal requirements / tested versions:
Firmware intrusion detection (UNii 2.4.0 / Alpha XL 3.11 / Alpha XL ML is EOL)
Rootfs Pluto's (5.68a)
Firmware Polyx (UBIFS)
Diva/VDG-Sense (2.6.13)
iProtect version 10.1.37
IPROTECT 10.3 - INTEGRATIONS - SOFTWARE & FIRMWARE
Network requirements
Since iProtect version 10.03 the network communication between the server and the Pluto devices has changed. Previously, we were only using our own communication protocol. When updating to iProtect 10.3, secure WebSockets are used.
It is necessary to set up certain network ports to switch to using Websockets. Please read the page carefully! IPROTECT Access - Network sockets
Firewall settings
The firewall on the iProtect server is set by default to allow network traffic with TKH access control controllers. When connecting a third-party system to iProtect, the necessary network port settings must be added to the firewall.
These firewall rules can be adjusted via the system's Cockpit Panel, which is accessible at the following URL: https://{ipaddress/hostname}/cockpitpanel
Getting the necessary files
Creating a new Backup of the iProtect system and download the Backup from the maintenance page.
Updating the iProtect version.
First, it is important to bring the server fully up-to-date, you can do this by going to the “Software updates” tab in CockpitPanel and then running a scan to see if any updates are available.
Cockpitpanel is reachable by the url https://{ipadress/hostname}/cockpitpanel
Install the new serverbox at the maintenance page.
Go to the iProtect™ maintenance page (Click on the iProtect maintenance tab in cockpitpanel)
Activate the maintenance functions by clicking on the activating button at the top left.
Go to file upload section at the maintenance page (Install > Upgrade > Configuration)
Click on the “...” button below Upload iProtect™ (1) and select the new maintenance page version and click on the “Post” button.
Refresh your browser webpage.
Install the new iProtect™ version at the maintenance page.
Install > Upload iProtect (1)
Click on the “...” button and select the new iProtect™ package and click on the “Post” button.
When the “Check requirements” button appears, press it and a check will be done. Check the log and see what is needed to continue.
if the check is passed you get a “Start Upgrade” button and can start the upgrade by a click on this button.
You can follow the installation at the User interface logging, if you see the messages “system is ready” the Gui is ready and you can login in iProtect™ again (only the root user can login at this point)
Installing the new license:
*How to import an iProtect™ license (>=10.1)
If a new license is needed, please contact our orderdesk.
Activating lines
To be sure all lines and nodes gets the latest software, select the system default Provisioner group.
Go to iProtect™ menu option Installation > Hardware > Line
Select System default at the Provisioner group options.
The components under the line config will automatically be provided with the latest firmware version.
Activate the line’s now, the ‘door controllers’ will get the new software and start with the installation automatically. The doors will be non-functional for 5-10 minutes. Open doors beforehand if they are critical.
When updating iProtect to version 10.03, all network controllers will be updated automatically to a new Rootfs version. This update will be processed in the background and will take aprox 20 - minutes (depending on network speed).
During the preparation of the Pluto Rootfs update, the customer will not experience any inconvenience.
When the update is complete, the system administrator must reboot the controller. Booting up the controller will take approximately 2-5 minutes (depending on network speed). During this time, the customer may experience problems opening the door.
IPROTECT - Release notes 10.3 | 4.1.3 Update of rootFS by privisoner
Finishing the update
When all lines are updated and the re-index message is gone, you can finish the update with the button in the menu:
Installation > Database restore > Activate line
Some points to check at the end of the update:
Readers
Database couplings
Client login (remove browser cache)
Import / Export
iNVR
Printing badges/cards
Intercom
browser certificate