User guide

Configuration Management System Management
1-9
iMG/RG Software Reference Manual (System Configuration)
Note: Recovery Application Code uses the same configuration file used by Main Application Code.
Configuration parameters for modules not available on Recovery Application Code are simply ignored
when the CPE runs in recovery mode.
1.1.3.5 Main partition
The gateway operating system is named Main Application code and is stored in a third flashfs partition area (the
Main Partition) that provides permanent storage for the Main Application code and for files that are normally used
only during system bootstrap.
During the system bootstrap, the files stored in the main partition are copied into isfs in order to make them
available to all application processes. Processes typicallyuse the isfs to store temporary configuration data.
1.1.3.6 Configuration partitions
This gateway adopts a partition architecture based on two Configuration Partitions.
One configuration partition is used to backup the other one in case of flash corruption during configuration
update. Any time a configuration partition needs to be changed, an identical backup copy is created.
To increase system robustness and avoid loss of configuration when the CPE runs in recovery or is rebooted
during a configuration save process, configuration files are saved in separate partitions from the main application
code.
Note: The Command Line Interface doesn't allow access to the flashfs file system or to the isfs in store file
system because this is not typically required by user.
The Flash file system flashfs, in store file system isfs and special debug functions are available only
through the debug console command line.
1.1.4 Configuration Management
Each active gateway configuration can be saved as configuration file for future reference, or as bootstrap config-
uration file.
Up to two custom configuration files can be permanently stored in the system, with one of them marked as the
active configuration file to be executed during the bootstrap phase.
Configurations are not stored as a sequence of commands but in a proprietary format.
The format of the configuration files follows the Information Model used by the main application code where a
typical object tree representation is used to categorize and map system objects attributes.
The following example shows a snapshot of a generic configuration file.
# Information Model configuration file
version 4
N ImGwaAdmins ImGwaAdmins
N ImGwaAdmin ImGwaAdmins.gwa_admin
A Profile none