Availability:
This feature was introduced in M2000 V200R010. The original CME release is CME

V200R009.

Summary:
In certain data reconfiguration scenarios, the CME automatically generates rollback scripts
together with delivery scripts.  After reconfigured data is delivered to NEs and takes effect,
users can use the script executor to run the corresponding rollback script to roll the data back
to the previous state. Users can also select a BSC to roll back its configuration data.

Benefits:

With this feature, users can easily and quickly restore the network during routine maintenance
if the network quality deteriorates due to exceptions that occur during data delivery.

Description:

During data configuration, the CME generates a rollback directory that stores a rollback script
and a project file of the script executor based on the configuration information in the
generated reconfiguration script. It then stores the rollback directory in the directory of the
reconfiguration script. After the reconfiguration script is executed, users can use the script
executor to load the rollback project file and deliver the rollback script for it to take effect. In
this way, the configuration data is rolled back.

The CME allows users to roll back configurations for device, transport, and radio parameters.

For details about the scenarios where the CME does not support configuration rollback, see
CME Online Help.

Enhancement:

The following function is added to M2000 V200R012C00:
?  Rolling back configurations for device, transport, and radio parameters.

The following function is added to M2000 V200R011C00:

?  Rolling back transport parameters related to intra-GBSC GBTS reparenting and link
management.

Dependency:

None

No dependency for this procedure

It will help my job