Cisco Cisco ONS 15454 SONET Multiservice Provisioning Platform (MSPP) Installation Guide
Corporate Headquarters:
Copyright © 2003 Cisco Systems, Inc. All rights reserved.
Cisco Systems, Inc., 170 West Tasman Drive, San Jose, CA 95134-1706 USA
Upgrading Cisco ONS 15454 Release 2.2.x to 3.0.0
Using the TCC+ Card
Using the TCC+ Card
Introduction
This document explains how to upgrade Cisco ONS 15454's Cisco Transport Controller (CTC) software
from Release 2.2.x to Release 3.0.0 using the Timing, Communications, and Control + (TCC+) card.
from Release 2.2.x to Release 3.0.0 using the Timing, Communications, and Control + (TCC+) card.
Before beginning, write down the following information about your site; the data will be useful during
and after the upgrade: Date, Street Address, Site Phone Number, and Dial Up Number.
and after the upgrade: Date, Street Address, Site Phone Number, and Dial Up Number.
Caution
Read each procedure before you begin the upgrade.
Caution
This procedure is only supported for Releases 2.2.0 and foward. If you wish to upgrade from a release
prior to Release 2.2.0, you must call the Technical Assistance Center (TAC) at 877 323-7368 for
assistance.
prior to Release 2.2.0, you must call the Technical Assistance Center (TAC) at 877 323-7368 for
assistance.
Caution
Cisco recommends Release 3.0.0 for new system installations (or what is commonly termed "Greenfield
applications") only. When you upgrade from ONS 15454 Release 2.2.x to 3.0.0, a condition may arise
that can cause a reset of the node at the point after the upgrade process after a provisioning change is
performed on the node. During testing, this condition was experienced in less than 2% of the systems
upgraded. If the node falls into this condition, traffic may be affected on provisioned circuits. If you
choose to upgrade nodes to Release 3.0.0, perform the upgrade within a maintenance window and follow
the procedure described in the caution after Step 9 of the
applications") only. When you upgrade from ONS 15454 Release 2.2.x to 3.0.0, a condition may arise
that can cause a reset of the node at the point after the upgrade process after a provisioning change is
performed on the node. During testing, this condition was experienced in less than 2% of the systems
upgraded. If the node falls into this condition, traffic may be affected on provisioned circuits. If you
choose to upgrade nodes to Release 3.0.0, perform the upgrade within a maintenance window and follow
the procedure described in the caution after Step 9 of the
.