Revised October 13, 2006
June 19, 2001
THIS FIELD NOTICE HAS BEEN ARCHIVED 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.
The product affected is the ONS 15454 Software Release 3.0.0.
When you upgrade from ONS 15454 Software Release 2.2.x to 3.0.0, a condition may arise that can cause a reset of the node if a provisioning change is detected on the node. During testing this condition was experienced in less than 2 percent of the systems upgraded.
As the node activates the new software load, each card in the system is loaded with the new revision of code. If any one of the cards fails to load the software successfully, an alarm is generated indicating a card failure. If this card failure is ignored, the node enters a state whereby any provisioning changes detected by the TCC+ will cause the entire shelf to reload the new software image and potentially affect traffic.
The condition will not be seen on new or "greenfield" systems initialized with release 3.0.
Note: You may receive a series of Java exception errors when the software is activated. Disregard these messages; they are due to the changes instituted in the Java code base for 3.0.0 that 2.2.x is unable to interpret.
This issue was identified in verification testing of release 3.0.0 and was witnessed in less than 2 percent of our test cases.
If your system reports a failed card during activation of release 3.0.0, a condition can arise that may cause the node software to reload and may affect traffic.
If you upgraded to 3.0.0 and were informed of a failed card, you will need to revert to the previous load of software prior to making any provisioning changes on the network. You will then need to replace the card which reported the failure and repeat the upgrade procedure. Failure to follow this procedure can result in a loss of traffic as the node reboots.
The issue has been resolved in 3.0.1, which will be available shortly on CCO and CD. If you do not currently require the 3.0.x code base, we recommend that you wait to upgrade your existing nodes using release 3.0.1. This release is expected to be available by August 2001. If you need the 3.0.x code base now, you must follow the upgrade procedures (available on CCO) or consult with your account team for assistance.
To follow the bug ID link below and see detailed bug information, you must be a registered user and you must be logged in.
Activation of TCC+ causes Exception Error
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:
Receive Email Notification For New Field Notices
Product Alert Tool - Set up a profile to receive email updates about reliability, safety, network security, and end-of-sale issues for the Cisco products you specify.