Revised June 2, 2008
April 24, 2003
THIS FIELD NOTICE HAS BEEN EXPIRED AND IS NO LONGER MAINTAINED OR UPDATED BY CISCO.
THIS FIELD NOTICE IS PROVIDED ON AN "AS IS" BASIS AND DOES NOT IMPLY ANY KIND OF GUARANTEE, WARRANTY OR SUPPORT. USE OF THE INFORMATION ON THIS FIELD NOTICE OR MATERIALS LINKED FROM THIS FIELD NOTICE IS AT YOUR OWN RISK. CISCO RESERVES THE RIGHT TO CHANGE OR UPDATE THIS FIELD NOTICE AT ANY TIME.
TCC+ cards with release 2.2.0 originally on the card
An active TCC+ reset occurs when attempting to download software from 3.1, 3.2, or 3.2.1. This happens when the TCC+ is loaded with 2.2.0 at the time of the download.
The problem was discovered when trying to download a newer version of software from 3.1, 3.2, or 3.2.1 when the TCC+ had version 2.2.0 installed.
When downloading software to the active TCC+, there would be a TCC+ reset causing outages on Ethernet traffic.
Equipment Failure alarms and TCC+ resets are present on the active TCC+ during software downloads. A loss of Ethernet traffic also occurs at the time of upgrade.
One or more retries may result in success.
A utility is available, ptfix2, which can be run prior to software downloads that will prevent TCC+ cards from resetting. The utility should always be run prior to an upgrade when a TCC+ is running 3.1, 3.2, or 3.21 and the current version of software is 2.2.0.
The utility will run on a win32 based PC and requires IP connectivity from the PC or workstation to the 15454 that will receive the software upgrade. The ptfix2.exe utility can be run from a command prompt or using the Start -> Run interface.
Usage: ptfix2 [--user [--pass ]] address
Where address is the hostname or IP address of the 15454, --user is a superuser login (3.21 only), and --pass is the superuser password (3.21 only).
Note:?If a TCC+ card is manually reset after running this utility, but before software download, the utility will need to be run again prior to software download.
Note:?Use the available script file "ptfix2" that can be found in the Software Center (registered customers only) .
This issue is fixed in version 3.3 and later. This issue does not occur when the interim software version is after 2.2.0 and prior to 3.1.0.
To follow the bug ID link below and see detailed bug information, you must be a registered user and you must be logged in.
For More Information
If you require further assistance, or if you have any further questions regarding this field notice, please contact the Cisco Systems Technical Assistance Center (TAC) by one of the following methods: