Polisy stuck on 3.1.21

[SHM]

Can't seem to upgrade my Polisy to 3.1.29.  Running IoX 5.6.2.  Have only tried upgrade via Admin Console.

[kzboray]

@SHM If you have been unsuccessful in updating you Polisy via AC, you can try the front panel button. Keep in mind the update process can take quit a while if it's been a bit since your last update. During the update all three front panel lights will flash green. At the end of the update you will hear 5 beeps then a pause and finally a single beep.

That last beep is the notification that the system has restarted. I generally wait another 5 minutes giving IoX time to update all it's link tables, but you can log onto PG3 to verify the update before you start AC.

Here are the instructions for the front panel update process.

Multi Function Button

There's a little multi function button behind the very small hole on the front of the unit. This button has multiple purposes outlined below. Every click on the button will cause the unit to beep.

If the button does not behave as described below, please update Polisy.

Update and Upgrade All the Packages

Click the button once. Please consult support before updating this route. See link below for suggested update/upgrade process.

Please see this important update (July 2022)

[tlightne]

If you are not running PG3X there will not be an update path for Polisy to 3.1.29.

PG3 3.1.21 is the latest version.

[SHM]

So how does one upgrade to PG3X?

[tlightne]

• Enable PG3x: https://polisy.local:8443/rest/pg3x.enable
• Reboot and wait for a beep + 1. Migrating node servers from PG3 to PG3x might take up to 2 minutes per node server. So, please be patient
• Once all node servers show connected, reboot again.

[brians]

Note that the enable web page doesn't provide any visual feedback. After that you just let it sit and hope it completes the upgrade.

I did this a week or so ago, I just updated from 3.1.27 to 3.1.29 with no issues.

 

[SHM]

thanks

[SHM]

Tried 

• Enable PG3x: https://polisy.local:8443/rest/pg3x.enable

nothing happens after manual reboot

[bpwwer]

The reboot is supposed to:

1) install PG3x, overwriting PG3.  (There is no visual indication this is happening)

2) start PG3x, which detects that it needs to migrate from PG3 and starts migrating node servers

   - If you connect to PG3x via the WebUI during this process, you'll see pop-up message as each node server is migrated

 

Note, that you do have to close the WebUI to PG3 and open a new browser window for PG3x.

Note2, PG3x uses the same login credentials as the Admin Console, it has no default nor does it use whatever you changed PG3 login credentials too.