All configuration data configured via the WBM of the board must be
backed up using the backup server. Otherwise all configuration data will
be lost after a board replacement, a reset of the board or loadware upgrade
and the native SIP-/SIP-Q trunking connection cannot be automatically
reestablished. This is done with the OpenScape 4000 Assistant > Backup
& Restore.
It is important to ensure that the backup server can be reached. If
the backup server is not available, the configuration data can also be
saved in the flash memory of the board and then can be retrieved from
there.
OpenScape 4000 Assistant > Backup & Restore
Configuration of a connection to backup server and OpenScape 4000
Assistant.
CHANGE-CGWB:MTYPE=CGW,LTU=1,SLOT=37,TYPE=MGNTDATA,
MGNTIP=<ip_address_assistant>,MGNTPN=<port_no_assistant>,
BUSIP=<ip_address_backup_server>,BUSPN=<port_no_backup_server>};
Note: The values for MGNTPN and BUSPN
will not be restored after a reset of the board. They have to be configured
again manually.
Local Flash
IMPORTANT:
It is recommended to additionally use the local
flash as a backup media. If the connection to the backup server is broken
the configuration data will be automatically restored from the local
flash.
WBM > Maintenance > Actions > (double-click) Automatic
Actions > Saving Local Configuration for Upgrade
IMPORTANT:
If the restore is necessary (e.g. after an upgrade
of the loadware) and the backup server cannot be reached during the startup
phase, the board is loaded and put into operation with the default configuration.
If the HBR server is then reachable, the restore is carried out afterwards
and a reboot with the new configuration is triggered! An additional
reboot is also triggered during the startup phase if configurations/data
required for operation are restored (e.g. SPE certificates).
IMPORTANT:
To avoid problems during upgrading/loadware swapping,
a backup should be initialized after exchanging the board because the
backup is associated with the MAC address.