Previous Topic

Next Topic

Book Contents

Book Index

Configuration management

The user interface provides options for configuration backup and storing it on a selected server. The easiest way to save node configuration is to use back up configuration. In back up configuration, the existing snapshot of the configuration is copied and stored to the server mentioned using the FTP protocol. In case of backup config failure- “Database Save Failed” alarm is raised. In this process, NE obtains the configuration using the FTP protocol from a remote server, checks and accepts the configuration if applicable to the node. In case of failure, a restore failure alarm is raised.

You can restore the configuration by restoring from remote machine through FTP or from the local machine using HTTP. The node gives an error message for the cause of the failure. The cause of the failure may be one of the following:

The node can recover from restoration operation failures due to network unavailability by using FTP timeout of 15 seconds.

The node verifies the validity of the restored configuration. The activation of restored configuration shall be non-service affecting for the unaffected configuration. If the verification fails, the restored configuration is rejected and configuration restore failure alarm is raised.

The node raises an alarm on detecting configuration corruption or version mismatch without affecting traffic.

In This Section

Backing up configuration data

Restoring Configuration

Restoring Factory Default settings

Bringing up the node from SLAT

See Also

Maintenance

Viewing and Editing System settings

Viewing System Changes

Rebooting Cards

System Restart options

Adding System Notes

Viewing List of Monitored Tasks

Performing Loop-backs

Diagnostics

Upgrade Operations