EtherHaul™ 8000 Installation, Operation and Maintenance Manual
Page 40
Apply
, all parameters are sent in bulk to the system and then executed locally in order
to avoid losing management connection.
3.5.2
Save Configuration
Any configuration change applied should be saved using the
Save Configuration
button.
The system has two configuration banks:
1.
Running Configuration – the currently active configuration. Every time
Apply
is
clicked, the Running Configuration is updated.
2.
Startup Configuration – the configuration the system will come up with after the
next reboot. This configuration may be different than the currently active
configuration (Running Configuration).
In order to save the applied configuration changes, click
Save Configuration
so
changes will be saved to the startup configuration. If changes are not saved to the
startup configuration, they will be lost the next time the system reboots.
Save Configuration
buttons are available for local and remote systems.
A
Save
icon is displayed on the all Web-Management pages, as a reminder, in case
configuration changes were made and not saved.
3.5.3
Rollback
A safety measure that allows recovering from system configuration changes that caused
loss of communication.
When Rollback is used, a timer runs (and restarts) whenever a management (or CLI)
command is entered. In the event that no command is entered within the timeout
period, the system automatically reboots and comes up with the saved startup
configuration.
A Rollback timeout is especially recommended when configuring remote elements that
are being managed over the link.
Rollback is activated for both local and remote systems.
3.5.4
Reboot
Separate buttons for local and remote reboot. The system will power off and then on
and come up after initialization (~90 seconds).
Note that any unsaved changes will be lost.
