-> Configuration data will be loaded from the backup server. This is normally the case after upgrade over HDLC or exchanging the physical board.

The gateway starts up using its default configuration data. No retry to reach the backup server is executed.

A retry to reach the backup server is executed.

The gateway starts up using its default configuration data. No retry to reach the backup server is executed.

Loadware Update via HDLC

Same procedures as normal restart. When upgrading via HDLC the board can’t have stored the current configuration data to the local flash (TFFS).

Configuration data is essentially no longer lost when a loadware update is performed via HDLC as a backup file is created on the local flash whenever data is saved in the WBM.

Loadware Update via OpenScape 4000 Assistant / WBM

After activating the new loadware the gateway will be automatically rebooted. The new gateway loadware is loaded. The new loadware image loads the previously stored configuration data. The data on the backup server can not be more up-to-date, therefore it is not taken into consideration.

For more information on the loadware update via OpenScape 4000 Assistant / WBM please refer to Chapter 5, “Load Concept for Gateway Boards”.

Loadware Update via OpenScape 4000 Assistant / WBM: backup server not configured

Same as „Loadware Update via OpenScape 4000 Assistant / WBM“.

Loadware Update via OpenScape 4000 Assistant / WBM: backup server configured but not reachable (via IP)

Same as „Loadware Update via OpenScape 4000 Assistant / WBM“.

Loadware Update via OpenScape 4000 Assistant / WBM: backup server configured and reachable, but no backup with configuration data is stored/found

Same as „Loadware Update via OpenScape 4000 Assistant / WBM“.

Loadware Update via OpenScape 4000 Assistant / WBM: backup server configured and reachable, but on the backup server an older configuration than the current one is found

Same as„Loadware Update via OpenScape 4000 Assistant / WBM“.