8-15
Cisco ONS 15454 SDH Reference Manual, R5.0
April 2008
Chapter8 Cisco Transport Contro ller Operation
8.6 TCC2/TCC2P Card Reset
8.6 TCC2/TCC2P Card Reset
You can reset the ONS 15454 SDH TCC2/TCC2P card by using CTC (a soft reset) or by physically
reseating a TCC2/TCC2P card (a hard reset). A soft reset reboots the TCC2/TCC2P card and reloads the
operating system and the application software. Additionally, a hard reset temporarily removes power
from the TCC2/TCC2P card and clears all buffer memory.
You can apply a soft reset from CTC to either an active or standby TCC2/TCC2P card without affecting
traffic. If you need to perform a hard reset on an active TCC2/TCC2P card, p ut the TCC2/TCC2P card
into standby mode first by performing a soft reset.
Note When a CTC reset is performed on an active TCC2/TCC2P card, the AIC-I card goes through an
initialization process and also resets because the AIC-I card is controlled by the active TCC2/TCC2P.
8.7 TCC2/TCC2P Card Database
When dual TCC2/TCC2P cards are installed in the ONS 15454 SDH, each TCC2/TCC2P card hosts a
separate database; therefore, the protect card’s 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 SDH maintenance program at approximately
weekly intervals, and should also be completed when preparing an ONS 15454 SDH for a pending
natural disaster, such as a flood or fire.
Note The following parameters are not backed up and restored: node name, IP ad dress, mask and gateway, and
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 rec ommends keeping
a record of the old and new node names.
8.8 Software Revert
When you click the Activate button after a software upgrade, the TCC2/TCC2P copies the current
working database and saves it in a reserved location in the TCC2/TCC2P flash memory. If you later 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.
Note The TCC2/TCC2P card does not carry any software earlier than Software R4.0. You will not be able to
revert to a software release earlier than Software R4.0 with TCC2/TCC2P cards installed.
The revert feature is useful if a maintenance window closes while you are upgrading CTC software. You
can revert to the protect software load without losing traffic. When the next maintenance window opens,
complete the upgrade and activate the new software load.
Circuits created and provisioning done after a software load is activated (upgraded to a hi gher software
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 (for example, 4.6.2 to 4.6.1), because maintena nce
releases use the same database.