Carrier Access BROADway System 770-0125-AB, Installation Manual

Page: 71 / 96

BROADway - Release 4.00 3-23
Configuration
Managing the BROADway Configuration Database
Managing the BROADway Configuration Database
BROAD way stores all configuration information in a database located in the non-volatile (flash)
memory-based file system in both the primary and backup (if installed) NSP101 cards. Changes made
to the database on the primary (in-service) NSP101 card are automatically copied and synchronized
with the database on the backup (out-of-service) NSP101 card.
BROAD way’s flash file system has approximately 30 MB available for system and user data, including
databases and code images. You can have as many database configurations stored as allowed up to the
limit of the
BROAD way file system storage space. If you use up all the available flash file system
memory, then when you attempt to save or copy a database the operation will fail.
NOTE:
If your flash file system begins to run out of space, the ALARM SUM LED on the
NSP101 will light. To recover from the alarm condition, delete any unneeded files. If you
ignore the alarm, the
BROAD way system will degrade in management access
performance.
Each of the configuration databases stored in the BROAD way system will fall into one of the following
three categories:
RUNNING —The “running” database is the one that the BROAD way system is currently executing
and running. Only one database can be “running” at any one time in the BROAD way system.
SAVED —The “saved” database is the one that will come into effect when you reboot the
BROAD way system. Only one database can be a “saved” database.
OFFLINE —All other databases that were ever named and stored but are not either RUNNING or
SAVED are off-line databases. You can have as many off-line databases as your BROAD way
system’s memory allows. If you use up all memory then when you attempt to store or copy a new
database, the operation will fail.
NOTE:
It is important to note that configuration changes made in the course of normal
operation to the RUNNING database will not be automatically saved unless a command is
performed to save the current configuration to the SAVED or other offline database. If you
reboot the BROAD way system without saving any configuration changes made to the
RUNNING configuration then BROAD way will revert to the previously SAVED database.
The BROAD way management interface will enable you to:
!
Load and execute a different database than the one currently running
!
Make a backup copy of a database
!
Delete a database
!
Rename a database