User guide

Emergency Save and activate emergency configuration.
iMG/RG Software Reference Manual (System Configuration)
1-48
When Ethernet connection is used, the intelligent Multiservice Gateway Ethernet ports are set to belong to
the default vlan as untagged port. When running in recovery mode, there is no support to tagged VLANs on
the Ethernet interfaces.
When ADSL connection is used, the intelligent Multiservice Gateway tries to connect to the remote NOC via
an RFC1483 LLC/SNAP Bridged connection type with VPI/VCI = 0/35 without any tagging scheme.
It’s possible configure the IP address used to connect remotely to the intelligent Multiservice Gateway when
recovery application is running.
To set a static IP address use the EMERGENCY SET IPINTERFACE IPADDRESS NETMASK command
and to set the default gateway use the EMERGENCY SET IPINTERFACE GATEWAY command.
To set a dynamic IP address uses the EMERGENCY SET DHCP ENABLE command. The intelligent Multi-
service Gateway will get the IP address from any external DHCP server as well as the interface subnet and the
default gateway.
Note: Note that if no DHCP server is discovered, the intelligent Multiservice Gateway will use the autoip
feature to autonomously assign a random IP address in the range 169.254.0.0/16. If a DHCP server
becoms available later, the IP interface will then change the IP address to the value offered by the DHCP
server.
1.3.3 Save and activate emergency configuration.
The emergency configuration data set in the previous section is not active until saved permanently in the intel-
ligent Multiservice Gateway e2prom. Emergency configuration data are saved in an e2prom instead in the
flashfs filesystem to increase the system robustness to any flashfs failure.
To save emergency configuration data in e2prom use the EMERGENCY UPDATE command.
Emergency configuration data is also saved in the system configuration any time the command SYSTEM CON-
FIG CREATE or SYSTEM CONFIG SET are entered. In this way the information is stored in two differ-
ent areas: the e2prom and the file bootstrap configuration file in the main partition.
In the case where the system starts in recovery mode because the main application partition is considered cor-
rupted, only the information stored in the e2prom will be used to configure the recovery application.
During normal system bootstrap initialization the recovery configuration data stored in the bootstrap configu-
ration file is considered the current emergency settings. This information is also stored automatically in the
e2prom to be immediately active.
To display the active recovery configuration data use the EMERGENCY SHOW command.
To avoid any misalignment between the configuration stored in the E2PROM and the configuration reported in
the bootstrap configuration file, the following situations are managed during the system bootstrap: