It was more or less a question about an unattended reboot.
The main reason for the reboot itself that the synchronization within a cluster after a software update does not work properly.
Example, you update your cluster. master and slave do have then the same software version.
Webadmin | Management | High Availibility
While 1 device appears as master, the second device stuck in the state SYNCING. Even after 24 hours.
I simply assume that synchronizing 2 devices ASG320 via Gigabit does not take so long. With webadmin , you can't boot the slave. A message appears that the synchonizing is on progress. After a reboot, the slave appears porperly as slave/active.
It was more or less a question about an unattended reboot.
The main reason for the reboot itself that the synchronization within a cluster after a software update does not work properly.
Example, you update your cluster. master and slave do have then the same software version.
Webadmin | Management | High Availibility
While 1 device appears as master, the second device stuck in the state SYNCING. Even after 24 hours.
I simply assume that synchronizing 2 devices ASG320 via Gigabit does not take so long. With webadmin , you can't boot the slave. A message appears that the synchonizing is on progress. After a reboot, the slave appears porperly as slave/active.
