Software Increment Release Notes ================================ Increment ID: I08A2000 Release: AN2000 Date created: 10-15-2007 Increment Type: OPC Title: OPC: NMA secu, Prov Mgr, Ring delete, INM ConnMgr, VTBM facility ---------------------------------------------------------------------- This Increment addresses the following issues. See below for more details. 1. tl1shell NMA ent-user-secu not working 2. Connection and Provisioning Managers not opening. 3. Deleting a node from a ring without OPC association fails. 4. INM Connection Manager fails to open - large number of connections. 5. INM fails to display all connections in Connection Manager. 6. ANXs do not show consistently in the same place in INM display. 7. Allow TL1CI CTAG strings to start with a digit 8. Editing VTBM Facility Assignment fails. ---------------------------------------------------------------------- 1. tl1shell NMA ent-user-secu not working * Description: Adding a user via TL1 using the tl1shell nma ent-user-secu command fails to properly add the password and keyboard idle timeout period values to the newly created ID. This results in the inability to use the newly created ID. * Pre-Increment Impact and work-around: The OPC Central User Admin tool is required to fix the password and keyboard idle timeout period values. ---------------------------------------------------------------------- 2. Connection and Provisioning Managers not opening. * Description: The Provisioning Manager fails to open at times. This increment fixes all the known causes for the tools not opening properly. * Pre-Increment Impact and work-around: Prior to this increment, the Provisioning Manager may fail to open. Direct TL1 commands can be used to provision facilities, DS0 services and manage cross-connects in AN2000. Refer to document 830-00381-02 for the TL1 users guide. ---------------------------------------------------------------------- 3. Deleting a node from a ring without OPC association fails. * Description: Customers who desire to delete a node from a ring and who do not follow the procedures described in CAP 98-9 will encounter problems if the node is physically removed from the ring (and thereby dropping association) before it is deleted from the ring configuration manager. Should this occur, the user will not be able to delete the node from the OPC span of control. This increment introduces a new tool that will allow for node deletion from a ring when the node in question does not have association with the OPC. * Pre-Increment Impact and work-around: Follow CAP 98-9 when removing a node from a ring. ---------------------------------------------------------------------- 4. INM Connection Manager fails to open - large number of connections. * Description: The INM Connection Manager would fail to open once a significant number of connections were added. This change allows the INM Connection Manager to open with more connections. Contact GSS for fine tuning these changes if problems are still encountered after applying this increment. * Pre-Increment Impact and work-around: Connections would not be able to be queried, deleted, or added from the INM Connection Manager. OPC Connection Manager can be used to perform these actions on the local OPC. ---------------------------------------------------------------------- 5. INM fails to display all connections in Connection Manager. Description: This increment resolves an issue where Preside (INM, ONM) would not display all of the connections in the Connection Manager on ring nodes. For the first STS assigned, any traffic routed through the group/channel assignments of 2,4 3,1 3,2 3,3 3,4 would not display. If a connection was attempted to be made on these ports, Preside would validate the connections, but then fails to write them and reports the following error: "The connection was unable to be provisioned because of unavailable trib, channel, route, connection service or unsupported configuration or the OPC connection service has been disabled" * Pre-Increment Impact and work-around: Do not use the group/channel assignments noted above. ---------------------------------------------------------------------- 6. ANXs do not show consistently in the same place in INM display. * Description: INM view of ANXs change each time the OPC is rebooted. In AN1960, ANX voice modules will be renumbered on every OPC restart, Or any action which would cause the "TFED MSR" to restart. INM saves these numbers and re-uses them for each OPC session. This increment changes the OPC to also keep the ANX numbers constant over OPC restarts. The previously assigned numbers are no longer available at the OPC. After the application of this increment, one of two actions will be required by the customer to synchronize the OPC and INM: a. Re-arrange the INM ANX view by rebuilding the window, or b. Use a new tool at the OPC to reassign the ANX numbers. Care must be taken to reassign these numbers correctly. The customer must determine these numbers from his INM view. The OPC tool is located at /iws/tfe/tfetst. To obtain help on the tool: /iws/tfe/tfetst -h To renumber the ANXs: /iws/tfe/tfetst -r Contact Zhone GSS for questions/issues when running this tool. * Pre-Increment Impact and work-around: Rearrange INM ANXs within the view to the proper place. ---------------------------------------------------------------------- 7. Allow TL1CI CTAG strings to start with a digit. * Description: Customers using TL1CI to access their network elements discovered that otherwise valid commands would fail if a CTAG string began with a digit, and then included any alphabetical character. For example, a CTAG of 111111 would be accepted, but a CTAG of 111A11 would not. Any CTAG beginning with an alphabetic character would be accepted, as long as the rest of the characters were valid. Valid alphanumeric characters accepted for a CTAG are a through z, A through Z, and digits 0 through 9. This increment also requires APU patch I07A2000 be applied before the installation of this increment. * Pre-Increment Impact and work-around: Use a CTAG that has either all digits, or that begin with an alphabetical character. ---------------------------------------------------------------------- 8. Editing VTBM Facility Assignment fails. Description: Users trying to edit the Facility Assignments on VTBM rings would find the option unavailable from the edit vt1.5 connection screen, as well as from the edit sts1 connection screen. This update resolves this issue. * Pre-Increment Impact and work-around: Users could still use the Facility Assignment window and TL1 commands to edit the facilities. ---------------------------------------------------------------------- Increments Needed: ---------------------------------------------------------------------- Increments I01A2000 through I07A2000 need to be successfully applied prior to application of this increment. ---------------------------------------------------------------------- Loads Affected: ---------------------------------------------------------------------- After successful application of this increment, the OPC load will be: ACNL20AI ---------------------------------------------------------------------- Special Instructions: ---------------------------------------------------------------------- None. ---------------------------------------------------------------------- Installation Instructions: ---------------------------------------------------------------------- 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/cgi-bin/isd_main.cgi?product=Accessnode 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).