No relevant resource is found in the selected language.

This site uses cookies. By continuing to browse the site you are agreeing to our use of cookies. Read our privacy policy>Search


To have a better experience, please upgrade your IE browser.

Knowledge Base

eAPP610 configuration file restore annex

Publication Date:  2018-01-31  |   Views:  739  |   Downloads:  0  |   Author:  v84085639  |   Document ID:  EKB1001272587


Issue Description

This document is intended to add supplementary actions to the standard "Configuration data restoration" procedure in order to attain complete configuration data restore.

If the standard procedure is followed, only eUDC data will be entirely loaded from the configuration, exception will be for the DNS setting of the eMDC server and for the maintenance IP addresses of both eMDC and eUDC servers.

Example of incomplete data restore:

Please note that the eMDC IP address configured In eUDC is initially, also eSCN IP is

The “Configuration data restoration” is used to load an older config, where eMDC IP adress was and eSCN IP was


The process is successful but the eMDC IP address doesn’t change, it’s still instead of


On the other hand, although the eUDC main IP address is not changed the eMDC and eSCN IP address were restored to the ones in the configuration file:


Also DNS configuration on the eUDC remained the same


The solution is to update first the maintenance IP addresses of eMDC and eUDC from eMDC OAM Business > System Configuration > IP Address Configuration

Step 2 is to follow standard "Configuration Data restoration " procedure in eMDC OAM Business > Configuration Data Batch Operations > Configuration Data Restoration