1. Home
    2. /
  2. Manuals
    3. /
  3. Allied-Telesis
    4. /
  4. AT-iMG624A
    5. /
  5. 9
Page 41 / 998 Scroll up to view Page 36 - 40
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
Page 42 / 998
System Management
Configuration Management
iMG/RG Software Reference Manual (System Configuration)
1-10
N ImGwaSips ImGwaSips
N ImGwaSip ImGwaSips.gwa
A ControlProtocol SIP
A Enable true
A Authentication proxy
A DefaultPort 5060
A KeepAlive disabled
A KeepAlive_Time 300
A NAT none
A NetInterface ip0
A RTT 500
A SE 1800
A Support none
A TimerB 32
To create a configuration that stores the current running system configuration, simply use the system config
create command. This command will create a file with the filename specified by the user in the Information
Model format and will save it permanently in the flash.
To extend configuration flexibility, it is possible at bootstrap time to force the gateway to execute a configura-
tion file written in standard CLI syntax. As it is not possible to save a running configuration directly into a file in
CLI syntax, a special set of commands has been provided that allow the loading of a configuration file (written
in CLI syntax) from a remote ftp or tftp server.
To set a configuration file as the bootstrap configuration file (irrespective of whether it has been written in
Information Model format or CLI syntax), use the
system config set
command.
To display the list of the existing configuration files use the
system config list
command.
To retrieve the bootstrap configuration filename or to display the content of a configuration file use the
sys-
tem config show command.
It is also possible set the gateway to a default factory configuration (see
Section 1.1.5.1.10
) using the
system
config set factory
command and then restarting the gateway.
It is possible set the gateway to a minimal configuration (see
Section 1.1.5.1.10
) using the
system config
set none
command, and then restart the device.
1.1.4.1 Configuration File Saving and Backup Process
On the units with 8 MBytes of FLASH configuration partitions are duplicated to support redundancy. Each con-
figuration partition includes the same files as its peer partition.
A special file named “version” is present within each configuration partition. This stores an incremental number
that differs between the two partitions by one. During the bootstrap phase the configuration partition having
the version file with the higher value is nominated to be the active configuration partition while the other is
assumed to be the backup partition.
Page 43 / 998
Configuration Management
System Management
1-11
iMG/RG Software Reference Manual (System Configuration)
Figure 1-3
details the backup process executed when a configuration file is created and set as bootstrap config-
uration.
FIGURE 1-3
Configuration files backup process - example
At the bootstrap phase the gateway activates the configuration stored in the active configuration partition,
based on the higher value stored in the “version” file available on both the two configuration partitions.
In
Figure 1-3
, when the configuration file “boot2” is generated via the
system config create
command
(phase A), the backup process first copies the content of the active configuration partition to the current
backup configuration partition. It then updates the backup configuration partition with the new configuration file
“boot2” and increments the content of file version in the backup configuration partition to be one value higher
than the active configuration partition.
At this point, if the gateway restarts the role of the two partitions is swapped. The second partition will be the
active configuration partition while the other will be the backup.
Note also that if during the
system config create
command the gateway restarts or power-cycles, only
the backup configuration partition (the second in the example) will be corrupted, leaving the first configuration
partition responsible for configuring the gateway.
im.conf, cm.boot,
version (10)
im.conf,
cm.boot,
version (9)
1st Configuration Partition
(256 KByte)
(active)
2nd Configuration Partition
(256 KByte)
(back-up)
> system config create
boot2
Phase A
Phase A
im.conf, cm.boot,
version (10)
im.conf, cm.boot,
cm.boot2
version (11)
1st Configuration Partition
(256 KByte)
(back-up)
2nd Configuration Partition
(256 KByte)
(active)
> system config create
boot2
Phase B
Phase B
im.conf,
cm.boot,
cm.boot2
version (12)
im.conf, cm.boot,
cm.boot2
version (11)
1st Configuration Partition
(256 KByte)
(active)
2nd Configuration Partition
(256 KByte)
(back-up)
Page 44 / 998
System Management
System command reference
iMG/RG Software Reference Manual (System Configuration)
1-12
Following the example in
Figure 1-4
; when the configuration file “boot2” is set to be the bootstrap configura-
tion file via the
system config set
command (phase B), the backup process first copies the content of
the active configuration partition (now the second partition) to the backup configuration partition (the first
partition). It then updates the im.conf file in the backup configuration partition to be a copy of the new config-
uration file “boot2” and increments the content of file version in the backup config partition to be one value
higher than the active configuration partition.
At this point, if the gateway restarts the rule of the two partitions are swapped yet again. The first partition will
be the active configuration partition while the second will be the backup.
If during the system config set command, the gateway restarts or power-cycles, only the backup configuration
partition (the first in the example) will be corrupted, leaving the second configuration partition responsible for
configuring the gateway and preserving the original bootstrap configuration file as well as the newly generated
(from Phase A) configuration file.
Note:
When a configuration partition is corrupted, the first system config create or set command will cause the
backup process to format and restore the invalid partition so it can receive a copy of the current active
configuration partition.
1.1.5
System command reference
This section describes the commands available on the gateway to configure and manage the
system
module.
1.1.5.1 System CLI commands
Table 1-1
lists all system
commands provided by the CLI:
Page 45 / 998
System command reference
System Management
1-13
iMG/RG Software Reference Manual (System Configuration)
TABLE 1-1
System Commands
Option
Fiber
A
Fiber
B
Fiber
C
Fiber
D
Fiber
E
Modular
ADSL
A
ADSL
B
ADSL
C
SYSTEM ADD USER
X
X
X
X
X
X
X
X
X
SYSTEM ADD LOGIN
X
X
X
X
X
X
X
X
X
SYSTEM CONFIG CREATE
X
X
X
X
X
X
X
X
X
SYSTEM CONFIG DELETE
X
X
X
X
X
X
X
X
X
SYSTEM CONFIG GET
X
X
X
X
X
X
X
X
X
SYSTEM CONFIG HELP
X
X
X
X
X
X
X
X
X
SYSTEM CONFIG LIST
X
X
X
X
X
X
X
X
X
SYSTEM CONFIG PUT
X
X
X
X
X
X
X
X
X
SYSTEM CONFIG RESTORE
X
X
X
X
X
X
X
X
X
SYSTEM CONFIG SET
X
X
X
X
X
X
X
X
X
SYSTEM CONFIG SHOW
X
X
X
X
X
X
X
X
X
SYSTEM CONTACT
X
X
X
X
X
X
X
X
X
SYSTEM CPULOAD
X
X
X
X
X
X
X
X
SYSTEM DELETE USER
X
X
X
X
X
X
X
X
X
SYSTEM INFO
X
X
X
X
X
X
X
X
X
SYSTEM LEGAL
X
X
X
X
X
X
X
X
X
SYSTEM LIST ERRORS
X
X
X
X
X
X
X
X
X
SYSTEM LIST OPENFILES
X
X
X
X
X
X
X
X
X
SYSTEM LIST USERS
X
X
X
X
X
X
X
X
X
SYSTEM LIST LOGINS
X
X
X
X
X
X
X
X
X
SYSTEM LOCATION
X
X
X
X
X
X
X
X
X
SYSTEM LOG
X
X
X
X
X
X
X
X
X
SYSTEM LOG ENABLE|DISABLE
X
X
X
X
X
X
X
X
X
SYSTEM LOG LIST
X
X
X
X
X
X
X
X
X

Rate

4 / 5 based on 3 votes.

Popular Allied-Telesis Models

Famous Router IPs
Famous Router Companies
Bookmark Our Site

Press Ctrl + D to add this site to your favorites!

Share
Top