Authorized personnel can remotely initiate a soft reboot on a controller from the controller's details page. Click on the Hardware tab on the left hand side pane, and then click on the controller of your choice as shown below. Note that the steps detailed below were performed on a location level. The same workflow can be achieved in the Global Overview.
CAUTION: Reboots can go sour resulting in the controller staying offline perpetually. Personnel are urged to ensure that the fields under Network Settings and Primary Host Details have correct values before initiating a soft reboot.
When in the controller's details page, a soft reboot can be initiated by clicking the More button which will produce a dropdown as shown below. Click the option labelled Reboot to initiate a soft reboot on the controller:
A tag indicating that the reboot is in progress will now appear next to the controller's name as shown below. This tag will reflect the controller's reboot status in real time as the reboot progresses.
A few moments after initiating the reboot, the controller will go offline as expected. This is shown below.
If there were no errors, the controller will come back online in some time as shown below.
Shortly after coming back online, the status of the tag will change as shown below, indicating that the reboot was successful.
This tag will remain for close to 10 seconds after which it will disappear as shown:
At this point, it can be concluded that the soft reboot operation was successful.
Failed Reboot
There can be circumstances where a reboot fails. This can happen for a variety of reasons. For instance, a reboot will fail if the network settings have invalid values. In these situations, the controller goes offline, but fails to come back online. Our system keeps track of the duration for which a controller stays offline after having initiated a soft reboot. If the controller stays offline for more than 5 mins, we conclude that the reboot has failed. In such a situation, the reboot status will appear as shown below:
In the event of a failed reboot, the controller needs to be reset and reconfigured.
The first step is to revert the controller's configuration related parameters to their default states. This can be achieved by manually:
Moving Dipswitch 2 into the ON position
Moving Dipswitches 1, 3 and 4 into the OFF position
Pressing and releasing the RESET push button.
The next step is to log into the controller's web panel using a browser. Care must be taken that the browser's computer is in the same network as the default static IP address (192.168.0.251).
Type 192.168.0.251 in the browser's address bar and hit Enter.
Login credentials will be requested. Move Dipswitch 1 into the ON position. This will enable default credentials (username: admin , password: password) for 5 minutes.
(Shown below is the login page of an LP4502 controller.)
Log into the web panel.
Now that we have entered the web panel, we need to set the values for:
Network Settings:
Select the Network option from the panel to the left.
Select the "Use DHCP method to obtain IP address automatically" checkbox.
Under DNS Settings, select the "Obtain DNS server address automatically" checkbox.
(Shown below is the network settings page of an LP4502 controller. The values supplied in the inputs are to be ignored. Only the two radio buttons as mentioned above are to be selected.)
Click Accept to save the changes.
Host Communication Settings:
Select Host Comm from the panel to the left.
Set the inputs as follows:
Connection Type: IP Client
Data Security: TLS Required
Host IP: mercury-api.sequr.io
Port Number: 3001
Connection Mode: Continuous
Retry Interval: 20 seconds
Click Accept to save the changes.
As a last step:
Move Dipswitch 2 back to the OFF position.
Select Apply Settings option from the panel to the left.
Select Apply Settings, Reboot.
These steps will bring back a controller online with the default values for web configurations.