System information

221 02-FGB 101 544 Uen H – June 2009 43
When an update is initiated, the image file is downloaded using standard
TCP/IP protocol specified by the URL or path to a local file. Before the
update process is started, the file is checked for inconsistencies.
It is also possible to upgrade the software via the WUI from a locally stored
file. This feature can be configured from the CLI to be blocked (invisible) in
the WUI.
9.3.2 Remote Management using TR-069
The Ericsson W3x includes a remote management agent supporting the
CPE WAN Management Protocol (CWMP) as specified in DSL Forum TR-
069 (short for Technical Report 069) Amendment II.
CWMP defines an application layer protocol for remote management of
end-user devices and provides the communication between a CPE and a
TR-069 capable Auto Configuration Server (ACS).
The Ericsson W3x is configured with parameters relating to the association
with an ACS, credentials for an ACS when making a connection request to
the Ericsson W3x as well as time settings for when the Ericsson W3x
should send CPE information to the ACS.
The Ericsson W3x remote management agent supports remote software
image installation, shell script execution and a set of configuration and
status parameters.
9.3.3 Backup and Restore Configuration
To preserve the running configuration, a backup copy of all accessible
values can be stored in a local file. In case of a system failure or a
corrupted configuration, the system can be restored from a backup file.
9.3.4 Reset to Default Configuration
A reset to default configuration can be done either from the CLI, WUI or by
using the physical Reset button on the unit.
9.3.4.1 Create own Default Configuration File
It is possible to save the running configuration as a new default
configuration file which then can be imported to the CDB.
9.3.5 System Log
The Ericsson W3x includes a system log accessible both from the CLI and
WUI as a text file.
The system logging information is written to 5 files which are rotated in a
circular fashion. The files are limited to 200Kbytes each, which equals a
maximum of 1 MB total logging information. The files are not saved to flash
and will be lost when rebooting or when power is disconnected.
When persistent logging is enabled, the log files are written to flash
memory in two files alternately.
The syslog events can be saved to a local file or forwarded to a remote
syslog server.