The standard backup and restore procedure works as expected, provided the configuration master key on the old gateway matches the new gateway.
On the old gateway, run the following command to verify the master key:
ADDITIONAL INFORMATION:
copy running-config startup-config
ADDITIONAL INFORMATION:
If the command prints the warning, the backup from the old gateway can be restored on the new gateway without any further action.
For example:Warning! It is a recommended policy to override default configuration master key with user defined secret - for details see user reference.
If the command does not print the warning, the user has configured a new master configuration key.
If you do not know the master configuration key, do the following:
Set a new passphrase. Run the following command:
ADDITIONAL INFORMATION:
key config-key password-encryption
Save the passphrase. Run the following command:
ADDITIONAL INFORMATION:
copy running-confg startup-config
After changing the key, record the new passphrase and perform the backup of the old board.
Insert the new board and enter the default username root and password root to log in.
Change the password and configure EASG.
ADDITIONAL INFORMATION:
The following are the options:
Enable
Disable
If you are restoring from a backup, you can skip the initial gateway configuration and disable DHCP.
ADDITIONAL INFORMATION:
For example:--- Gateway Configuration Script --- The script will provide you basic gateway connectivity configuration. Configuration Script - do you want to continue (Y/N)? n
Note: The PMI is currently configured with DHCP on VLAN 1 Do you want to remove it [Y]: y
If you configured a master configuration key password before the backup, you must set the same configuration password for the new gateway using the following commands:
key config-key password-encryption
copy running startup-config
To check the software load, run the following command:
ADDITIONAL INFORMATION:
show system
ADDITIONAL INFORMATION:
After the backup is done, if the software load is older than the one used in the previous gateway, then:
Update the software load manually. You can update the software using an image stored in the USB drive so you do not need to configure the networking parameters.
Allow the restore operation update the software load. If you manually add software downloadable files to the backup directories, the restore also updates the firmware of the gateway and media modules. The gateway software must be present in the backup folder, and the media module firmware must be present in the MM subfolder.
ADDITIONAL INFORMATION:
For example:
A backup directory that contains a G430v3 software image version 43.28.0.g430-???(super)# dir usbdevice0 g430-backup Date Type Size(Bytes) Filename ------- -------- ---------- ---------- 2026-01-15,11:17:48 file 728 audio8122.bin 2026-01-15,11:17:48 file 865 README.TXT 2026-01-15,15:09:38 file 16598907 g430v3_sw_43_28_0.bin 2026-01-15,11:17:46 <DIR> 4096 IPPHONE 2026-01-15,11:17:48 <DIR> 4096 GWANNC 2026-01-15,11:17:46 <DIR> 4096 MM 2026-01-15,11:17:48 <DIR> 4096 TRUST 2026-01-15,16:18:34 file 2038 startup_config.cfg
A software update during the restore operation, before the automatic reset.g430-???(super)# show restore status Restore operation in progress. Files restored: Type FileName Status ----------------------------------------------------- startup-config startup_config.cfg OK announcement annc1.wav OK announcement annc2.wav OK swComponent g430v3_sw_43_28_0.bin Copying...
Update the gateway serial number in Communication Manager using the value displayed in the show system command output. Run the following command:
