Tcc2/Tcc2P Card Database - Cisco ONS 15454 DWDM Installation And Operation Manual

Chapter 19 CTC Operation Reference

19.7 TCC2/TCC2P Card Database

When dual TCC2/TCC2P cards are installed in the ONS 15454, each TCC2/TCC2P card hosts a separate
database; therefore, the protect card database is available if the database on the working TCC2/TCC2P
fails. You can also store a backup version of the database on the workstation running CTC. This
operation should be part of a regular ONS 15454 maintenance program at approximately weekly
intervals, and should also be completed when preparing an ONS 15454 for a pending natural disaster,
such as a flood or fire.
The following parameters are not backed up and restored: node name, IP address, mask and gateway, and
Note
Internet Inter-ORB Protocol (IIOP) port. If you change the node name and then restore a backed up
database with a different node name, the circuits map to the new node name. Cisco recommends keeping
a record of the old and new node names.
19.8 Software Revert
When you click the Activate button after a software upgrade, the TCC2/TCC2P card copies the current
working database and saves it in a reserved location in the TCC2/TCC2P card flash memory. If later
during the upgrade you need to revert to the original working software load from the protect software
load, the saved database installs automatically. You do not need to restore the database manually or
recreate circuits.
The revert feature is useful if the maintenance window in which you were performing an upgrade closes
while you are still upgrading CTC software. You can revert to the protect software load without losing
traffic. During the next maintenance window, you can complete the upgrade and activate the new
software load.
Circuits created or provisioning done after you activate a new software load (upgrade to a higher release)
will be lost with a revert. The database configuration at the time of activation is reinstated after a revert.
(This does not apply to maintenance reverts, such as R5.0.1 to 5.0.2, because maintenance releases retain
the database during activation.)
Cisco does not recommend reverting after changing provisioning on the node. Depending upon the
Caution
particular provisioning, reverting in this case can be traffic affecting.
To perform a supported (non-service-affecting) revert from a software release you have just activated,
the release you revert to must have been working at the time you first activated the new software on that
node. Because a supported revert automatically restores the node configuration at the time of the
previous activation, any configuration changes made after activation will be lost when you revert the
software. Downloading the software release you are upgrading to a second time after you have activated
the new load ensures that no actual revert to a previous load can take place (the TCC2/TCC2P will reset,
but will not be traffic affecting and will not change your database).
To perform a supported software upgrade or revert you must consult the specific upgrade document and
Note
release notes for the release you are upgrading to (or reverting from).
August 2005
Cisco ONS 15454 DWDM Installation and Operations Guide, R6.0
19.7 TCC2/TCC2P Card Database
19-15