Configuration Transactions

A transaction is an operation, in this case for configuration, that either succeeds completely or not at all. It is explicitly opened by an administrator and then committed or rolled back. Technical problems such as a power loss counts as an implicit rollback.

When your device powers up, it loads and uses the last-committed configuration. The power cycle therefore rolls back any configuration changes that took place before the power was taken down.

When you press the RESET button for a few seconds, the same thing is done. In addition to the power cycle procedure, a web interface over which you can make configuration changes is opened. You have thus begun a new transaction.

When you make configuration changes over the web interface, then these are set immediately, in test mode. This means that you should do whatever you can to assure that it works properly. If all works as expected, you can press the COMMIT button to commit changes. When the RESET button is pressed or when the power is cycled, this committed state will be loaded.

Note that pressing RESET while configuration settings are under test will erase those test settings, and revert to the last-committed settings. This means that you can always use a hardware button if you would ever lock yourself out.

It is not possible to commit a configuration that locks you out of the administrator's web interface, simply because you would not be able to configure your own device if you would do that.

The web-interface also presents a facility to return the device to factory settings. If you cannot access the web interface anymore, you can also remove the power and plug it back in while you keep the RESET button pressed. Do not release the RESET button until you see the ACTIVE light flashing fast.

Note that administrator's passwords are treated separately; when it is changed, it is immediately stored. There is no way of resetting the administrator's password to factory defaults. Be sure to remember your administrator password.