Software Increment Release Notes ================================ Increment ID: I41A1730 Release: AN1730 Date created: 5-1-2004 Increment Type: APU Title: ANX Robustness, Linecard Enhancements, MVI Call Rejections ---------------------------------------------------------------------- *** WARNING: Please refer to the following Pre-installation and *** *** Post-installation special instructions before applying this *** *** Increment. *** ---------------------------------------------------------------------- Following is a list of issues addressed in this Increment. See below for more details. 1. ANX recovery robustness 2. UE9000 MLC circuit failures after TDM SWACT. 3. Line cards stuck in over-current protection state. 4. MVI incoming call rejections. 5. Autonomous reset of Omega Linecards. ---------------------------------------------------------------------- *** Pre-installation Special Instructions: ---------------------------------------------------------------------- Some customers may have had special debug increments I98A1730 and I99A1730 applied to their systems. In order for this increment to apply properly, these increments must first be removed. To determine if this is applicable to your OPC span of control, use the 'Display Increments' option in the ISD tool to display all increments. If I98A1730 or I99A1730 (or both) exist, you must use the 'Remove An Increment' option to remove these changes prior to applying this increment. Failure to remove increments I98A1730 and I99A1730 will result in a patching error and I41A1730 will not apply. Should patch I98A1730 and I99A1730 be removed or not present, and the application of this patch results in the following error when applying: "Active APU apply error : Patcher error", then restart warm the active processor on the ABM shelf that the increment fails to apply on. After sync between the two ABM processors has been achieved, use the Rebuild the ISD database (entire), and apply APU patches I40A1730 (if needed) and I41A1730. If this does not resolve the application of this increment, then contact Zhone's GSS group referenced at the end of this increment document. ---------------------------------------------------------------------- *** Post installation Special Instructions: ---------------------------------------------------------------------- This increment provides the ability to adjust ANX recovery parameters. To ensure any changes to these parameter survive a ABM boot, an image must be taken following any changes to the ANX recovery parameters. Please note, these changes will not survive a system software upgrade. Removal of this increment will require a warm restart or a double switch of activity of the APUs. Failure to do so may impact the communications recovery time of ANX shelves. ---------------------------------------------------------------------- 1. ANX recovery robustness * Description: Large ANX deployments (20 VM's per HDT and higher) have had issues where the LAIC's would both fail during different system actions. Such actions include the switching of processors at the ABM shelf, committing ANX increments from ISD as well as an event that causes the total loss of transport from the ABM shelf to the ANX systems. This increment improves ANX robustness by: - Providing CI commands which allow adjusting the number of ANX shelves recovered simultaneously following a ABM switch of activity, ABM restart or ANX loss of communication condition. Go to ANXRECOVERY command increment on the NE after applying this patch, and type "HELP" for more details. - Changing the default number of ANXs recovered at a time after a ABM switch of activity to 2. This value can also be changed from the ANXRECOVERY CI tool. - Introducing a 5 second delay between the commit of each ANX on the HDT during ANX patching. In order to set the newly introduced recovery mechanisms, please refer to the Special Instructions section. * Pre-Increment Impact and work-around: Both LAIC packs could fail, causing a total system outage. Should both LAIC packs fail during a swact, the loss of transport or the application of an ANX increment, remove the LAIC packs and place the DS1 interfaces OOS at the fwpui. Place the LAIC packs back in the system, and place the DS1 facilities back IS one at a time. * Note: Please refer to the special instructions below. ---------------------------------------------------------------------- 2. UE9000 MLC circuit failures after TDM SWACT. * Description: If a UE9000 TDM has an autonomous switch-of-activity (SWACT) during an APU intensive situation, like during an optical switch of activity, several MLC circuits may be failed. * Pre-Increment Impact and work-around: Multiple circuits on each TDM shelf that has an autonomous SWACT may experience the problem. Avoid optical switches of activity until this patch is applied. ---------------------------------------------------------------------- 3. Line cards stuck in over-current protection state. * Description: Lightning voltage or other abnormal voltage surges can cause certain types of circuits to go into an over-current state. These circuits may not automatically recover from this state and need to be manually recovered. These pack types include all vintages of the NT4K65 CDS Epsilon, NTN502 ANX Epsilon II, UE9000 NTNP40 POTS-24, NTNP44 4+4, and NTNP42 UVG-24 line cards. * Pre-Increment Impact and work-around: The circuit is unavailable for call processing until it is manually reset at the craft level of the AccessNode Human Machine Interface (HMI). ---------------------------------------------------------------------- 4. MVI incoming call rejections * Description: If a MVI subscriber goes on-hook between 1.1 and 1.3 seconds before an incoming call is received, there is a chance that the incoming call would be rejected. * Pre-Increment Impact and work-around: When this occurs, the MVI subscriber is not aware of the incoming call rejection and the originator gets call failure treatment. Subsequent call attempts to the MVI subscriber are successful. ---------------------------------------------------------------------- 5. Autonomous reset of Omega Linecards. * Description: A condition exists whereby the AccessNode processor could convict the Omega linecard as needing a reboot. This would result in an LC602 log with the text "Auto Recovery Initiated" and a momentary loss of dial tone or a call cutoff. This change will reduce the chance of an Omega linecard (NT4K67 and NTNP41 series) resetting autonomously. * Pre-Increment Impact and work-around: During a linecard reset, the card is not available for call processing. A typical reset on the Omega card takes under 30 seconds to complete. ---------------------------------------------------------------------- Increments Needed: ---------------------------------------------------------------------- Increment I01A1730 through I40A1730 needs to be successfully applied prior to application of this increment. ---------------------------------------------------------------------- Loads Affected: ---------------------------------------------------------------------- ABM: ACCL17AS TBM: ATBL17AS ---------------------------------------------------------------------- Installation Assistance: ---------------------------------------------------------------------- Please refer to the Incremental Software Delivery Users Guide for general installation instructions. This document may be obtained from either the AccessWeb ISD web site located on the Zhone web page at (http://www.zhone.com/support/patches/index.html), or you may request document 830-00374-01 from your Zhone Technologies Account Manager or Order Manager. Issues with this increment should be directed to Zhone Global Services and Support at 1-877-ZHONE-20 (1-877-946-6320).