tree.
Activating and Committing Changes
If any changes are made to the current configuration through the CLI, those changes will not be
uploaded to NetDefendOS until the command:
gw-world:/> activate
is issued. Immediately following the activate command, the command:
gw-world:/> commit
should be issued to make those changes permanent.
If a commit command is not issued within a default time period of 30 seconds then the changes are
automatically undone and the old configuration restored.
A possible side effect of committing changes though the CLI is that any Web Interface browser
session that is logged in at the time of the commit will require that the user logs in again. This is
because the Web Interface view of the configuration may no longer be valid.
Restarting NetDefendOS with the CLI
The CLI can be used to restart NetDefendOS using the command:
gw-world:/> shutdown
This command performs a graceful shutdown of all connections and VPN tunnels before the restart
and is sufficient for most situations that require a system restart. In includes a reloading of the
configuration (in other words, reconfiguration).
To shutdown and restart both NetDefendOS and completely reinitialize the hardware, including the
NetDefendOS loader (equivalent to switching the hardware off then on), use the command:
gw-world:/> shutdown -reboot
The -reboot option is rarely needed in normal circumstances and because it requires more time for
the restart it is best not to use it. When NetDefendOS is upgraded the -reboot option is executed
automatically during the upgrade process.
The same restart functions can be performed with the Web Interface by selecting the menu bar
option Maintenance > Reset.
Reconfiguring NetDefendOS with the CLI
NetDefendOS can be forced to reread and reload the current configuration with the command:
gw-world:/> reconf
Apart from reloading the configuration, many of NetDefendOS's internal data structures related to
rules and traffic processing are reinitialized. It is not usual to execute a reconfigure during normal
operation but it can sometimes be a way to solve transient problems related to NetDefendOS
memory management.
Unlike the system restart described above, a reconfiguration does not usually affect current
2.1.4. The CLI Chapter 2. Management and Maintenance
43
To Next Page
Loading...
