Nokia 7302 Basics, Management And Oam Manual page 24

System Management
The command saves the current configuration file into the special protected
database. If the special protected database file already exists, it is overwritten. On a
default-database activation, the configuration present in this special protected
database will be restored. During shelf restart, if there is a corruption in configuration
database, then ISAM will try to restore it with the configuration saved in this special
protected database.
The protected interface configurations can be saved in a minimum protected
database directory using the command admin software-mngt ihub database
oam-save-protected. Use this command to save only the configuration of those
interfaces chosen to be protected [see
saves all the associated interface configurations through which management OAM
traffic can be passed. This command stores those OAM protected interfaces
configuration in a special OAM protected database file. If this file exists already, it
is overwritten. If the user did not protect any interfaces and issues this command, the
OAM protected database configuration file is not created. On a default-database
activation, this file is checked first, and if present, the OAM protected configuration is
restored. During shelf restart, if there is a corruption in configuration, ISAM tries to
restore the OAM protected configuration file, if the file exists.
Table
default-database activation. The OAM protected database has preference over
special protected database
24
If the user did not use this command, the OAM
Note 1 —
protected database is not stored. In this case, on
default-database activation, ISAM is restored with a
default/empty database configuration. Table
priority between special protected and OAM protected
databases on default-db activation
Unless the user issues this command, previously
Note 2 —
stored OAM protected database are not removed. For instance,
if the user restores a new database, this OAM protected
database is not overwritten based upon new database. The
user must explicitly give the above command to overwrite the
latest OAM protected database configuration based on the
newly restored database.
The OAM protected database can be removed by:
Note 3 —
•
removing protection from all interfaces, then issuing this
command. The OAM protected database is cleared
•
issuing the default-database activation with
"factory-defaults". See
3 shows the priority between the special and OAM protected databases during
3HH-11982-AAAA-TQZZA
"FD 100/320Gbps NT and FX NT IHub System
Basics, Management and OAM Guide"
"Saving Configurations"]. The command
3
"Saving Configurations"
shows the
Issue: 10