12
Oracle® Communications LSMS Release Notes Release 13.0 E54202 Revision 2 October 2014

Oracle® Communications LSMS · Oracle® Communications LSMS Release Notes Release 13.0 E54202 Revision 2 October 2014

  • Upload
    others

  • View
    16

  • Download
    0

Embed Size (px)

Citation preview

Page 1: Oracle® Communications LSMS · Oracle® Communications LSMS Release Notes Release 13.0 E54202 Revision 2 October 2014

Oracle® Communications LSMS

Release Notes

Release 13.0

E54202 Revision 2

October 2014

Page 2: Oracle® Communications LSMS · Oracle® Communications LSMS Release Notes Release 13.0 E54202 Revision 2 October 2014

LSMS 13.0 Release Notes

E54202 Revision 2 2 October 2014

Oracle® Communications LSMS 13.0 Release Notes

Copyright © 1997, 2014 Oracle and/or its affiliates. All rights reserved.

This software and related documentation are provided under a license agreement containing restrictions on use and disclosure and are protected by intellectual property laws. Except as expressly permitted in your license agreement or allowed by law, you may not use, copy, reproduce, translate, broadcast, modify, license, transmit, distribute, exhibit, perform, publish, or display any part, in any form, or by any means. Reverse engineering, disassembly, or decompilation of this software, unless required by law for interoperability, is prohibited.

The information contained herein is subject to change without Notes and is not warranted to be error-free. If you find any errors, please report them to us in writing.

If this is software or related documentation that is delivered to the U.S. Government or anyone licensing it on behalf of the U.S. Government, the following notices are applicable:

U.S. GOVERNMENT RIGHTS Programs, software, databases, and related documentation and technical data delivered to U.S. Government customers are "commercial computer software" or "commercial technical data" pursuant to the applicable Federal Acquisition Regulation and agency-specific supplemental regulations. As such, the use, duplication, disclosure, modification, and adaptation shall be subject to the restrictions and license terms set forth in the applicable Government contract, and, to the extent applicable by the terms of the Government contract, the additional rights set forth in FAR 52.227-19, Commercial Computer Software License (December 2007). Oracle America, Inc., 500 Oracle Parkway, Redwood City, CA 94065.

This software or hardware is developed for general use in a variety of information management applications. It is not developed or intended for use in any inherently dangerous applications, including applications that may create a risk of personal injury. If you use this software or hardware in dangerous applications, then you shall be responsible to take all appropriate fail-safe, backup, redundancy, and other measures to ensure its safe use. Oracle Corporation and its affiliates disclaim any liability for any damages caused by use of this software or hardware in dangerous applications.

Oracle and Java are registered trademarks of Oracle and/or its affiliates. Other names may be trademarks of their respective owners.

Intel and Intel Xeon are trademarks or registered trademarks of Intel Corporation. All SPARC trademarks are used under license and are trademarks or registered trademarks of SPARC International, Inc. AMD, Opteron, the AMD logo, and the AMD Opteron logo are trademarks or registered trademarks of Advanced Micro Devices. UNIX is a registered trademark of The Open Group.

This software or hardware and documentation may provide access to or information on content, products, and services from third parties. Oracle Corporation and its affiliates are not responsible for and expressly disclaim all warranties of any kind with respect to third-party content, products, and services. Oracle Corporation and its affiliates will not be responsible for any loss, costs, or damages incurred due to your access to or use of third-party content, products, or services.

Page 3: Oracle® Communications LSMS · Oracle® Communications LSMS Release Notes Release 13.0 E54202 Revision 2 October 2014

LSMS 13.0 Release Notes

E54202 Revision 2 3 October 2014

Table of Contents

Contents INTRODUCTION .............................................................................................................................. 4

PR Severity Definitions........................................................................................................ 4

Locate Product Documentation on the Customer Support Site .......................................... 4

Procedure .......................................................................................................................................... 4

RESOLVED PRS ............................................................................................................................. 5

CUSTOMER KNOWN PRS.............................................................................................................. 7

PRODUCT COMPATIBILITY ......................................................................................................... 11

ORACLE REFERENCES AND SERVICES ................................................................................... 12

Customer Access Support (CAS) ...................................................................................... 12

Emergency Response ....................................................................................................... 12

Page 4: Oracle® Communications LSMS · Oracle® Communications LSMS Release Notes Release 13.0 E54202 Revision 2 October 2014

LSMS 13.0 Release Notes

E54202 Revision 2 4 October 2014

Introduction This Release Notes document lists the Resolved and Known PRs for LSMS Release 13.0.0, Build 130.17.0.

This Release Notes also includes:

Software Compatibility

Release Notes are distributed to customers with a new software release at the time of General Availability (GA). They are updated for each Maintenance release.

Release Notes are available only on the Oracle Technical Network (OTN) site. For each new publication to the OTN site, the revision level of the part number is incremented. See Locate Product Documentation below

PR Severity Definitions

The PR sections in this document refer to PR severity levels. Definitions of these levels can be found in the following publication:

TL 9000 Quality Management System Measurement Handbook.

Locate Product Documentation on the Customer Support Site

Oracle customer documentation is available on the web at the Oracle Technology Network (OTN)

site, http://docs.oracle.com. You do not have to register to access these documents. Viewing these files requires Adobe Acrobat Reader, which can be downloaded at www.adobe.com.

Procedure 1. Navigate to the OTN site at http://docs.oracle.com

2. Under Applications, click the link for Communications. The Oracle Communications Documentation window opens with Tekelec shown near the top.

3. Click Oracle Communications Documentation for Tekelec Products.

4. Navigate to your Product and then the Release Number, and click the View link (the Download link will retrieve the entire documentation set).

5. To download a file to your location, right-click the PDF link and select Save Target As.

Page 5: Oracle® Communications LSMS · Oracle® Communications LSMS Release Notes Release 13.0 E54202 Revision 2 October 2014

LSMS 13.0 Release Notes

E54202 Revision 2 5 October 2014

Resolved PRs

Table RN-1 lists Resolved PRs for LSMS 13.0.0-130.17.0.

NOTE: Resolved PRs are sorted in ascending order by Severity (Sev), and then by PR number.

Page 6: Oracle® Communications LSMS · Oracle® Communications LSMS Release Notes Release 13.0 E54202 Revision 2 October 2014

Table RN-1. Resolved PRs for LSMS Release 13.0 Build 130.17.0 (10/10/14)

PR# CSR? Sev Title Customer Impact

134561 2 Customer executable MySQL DataBase defragmentation Progressively slower LSMS/ELAP Audit performance as the MySQL DB fragmentation increases.

224680 2 ELAP10.0_ST IPSEC is not getting configured on ELAP10.0 IPSEC not enabled between ELAP and LSMS.

239528 2 LSMS - Update JRE to 7u55 LSMS 13.0 includes the most recent version of the Java Runtime Environment (JRE).

161382 Y 3 LSMS shows Query Server to be connected even when Query Server MySQL slave is not connected.

The active status of connected servers is not properly displayed when query servers are disconnected.

196004 3 Configuration manual does not have commands to create new user on QS.

204618 Y 3 Procedural errors in doc 909-1968-001 MySQL will not start if the configuration is overwritten during the upgrade.

228112 Y 3 Error ("Invalid report ID: -1") received when retrieving subscription TN range from LSMS.

Occasional misleading ("Invalid report ID: -1") received when retrieving subscription TN range and other reports from LSMS.

167961 5 LSMS12.0_SYSTEM_TEST:LSMS Backup using Advanced Options is getting failed .

206183 Y 5 Wrong path name to Modify Title Bar in LSMS Console Window

212417 5 LSMS on E5-APP-B

214137 Y 5 Configurable MySQL Port for LNP Query Server on LSMS

221465 5 E5-APP-B Based Open Systems Products will only support Internet Explorer 8.0 & 9.0

228416 5 LSMS - Support of latest Java Client version (1.7)

232876 5 Security updates related to OS (CentOS) and MySQL

233879 5 LSMS Query Server update after MySQL upgrade in Core LSMS software

234392 5 Oracle Re-branding: Copyright

234395 5 Oracle Re-branding: Logo

234396 5 Oracle Re-branding: Customer Doc

Page 7: Oracle® Communications LSMS · Oracle® Communications LSMS Release Notes Release 13.0 E54202 Revision 2 October 2014

LSMS 13.0 Release Notes

E54202 Revision 2 7 October 2014

Customer Known PRs

Table RN-2 lists known PRs for LSMS 13.0.

NOTE: Known PRs are sorted in ascending order by Severity (Sev), and then by PR number.

Table RN-2. Known PRs for LSMS 13.0 (10/10/14)

PR# CSR? Sev Status Disposition Title Customer Impact

224680 2 Resolved No-Fix ELAP10.0_ST IPSEC is not getting configured on ELAP10.0

IPSEC not enabled between ELAP and LSMS.

240134 2 Resolved Defer LSMS13.0_ST:On stopping mysql on active server the secondary server gets stuck in transaction phase.

The stopping of MySQL from Linux command is not part of LSMS operations. However if someone were to do this accidently then the node can restarted to recover the system.

168186 3 Resolved Defer Incorrect alarm was issued during startNode

Alarm could be misleading to the customer as system did not really switch over.

236005 3 Resolved No-Fix LSMS13.0: Drop down menu of create tab of Service Provider menu is not displaying anything.

LSMS GUI is designed this way for other menus as well.

236045 3 Resolved No-Fix LSMS13.0 :"Halt the MPS" & "Eject CDROM" tab is available in platcfg menu of NAS.

No impact to customers.

236110 3 Resolved No-Fix LSMS_13.0: ON NAS Platcfg menu , extra tabs are present.

No impact to customers.

236112 3 Resolved No-Fix LSMS_13.0 :Repository Field is empty for few backup options on LSMS.

No impact, user needs to specify repository.

236210 3 Resolved No-Fix Title : Error is getting logged into platcfg.err.log file on LSMS.

No real impact. Restore is to be done using the documented tools.

236232 3 Resolved No-Fix LSMS13.0 : Spelling of word "Exiting" is incorrect.

No impact. Spelling error visible in a very rare scenario.

236291 3 Resolved Defer LSMS_13.0: "npacagent" core file is generated on LSMS.

No impact to customer operation.

236380 3 Resolved No-Fix LSMS13.0 : "Tekelec" word is observed while validating media.

No impact - branding problem.

Page 8: Oracle® Communications LSMS · Oracle® Communications LSMS Release Notes Release 13.0 E54202 Revision 2 October 2014

LSMS 13.0 Release Notes

E54202 Revision 2 8 October 2014

PR# CSR? Sev Status Disposition Title Customer Impact

236501 3 Resolved No-Fix LSMS_13.0: Hostname of NAS needs to be modified.

No impact to customers.

236581 3 Resolved Defer LSMS 13.0 : On LSMS GUI Java pop of "Invalid Session ID" is observed

Invalid ID is observed after closing the LSMS Java GUI and the browser is still open. There is no negative system impact.

236678 3 Resolved No-Fix LSMS_13.0: Timestamp is missing in platcfg.log file on LSMS

The platcfg.log file no longer contains the timestamp for each entry.

236713 3 Resolved Defer LSMS 13.0 : LSMS server is showing high utilization when we start capturing save logs from GUI.

System speed during savelogs operation is reduced.

236716 3 Resolved No-Fix LSMS 13.0 : Incorrect messgage is observed on LSMS GUI.

No impact but misleading return message.

236723 3 Resolved Defer LSMS13.0 : LSMS Server is showing high CPU Utilization when Servdi process is initiated with delay.

While servdi is in progress, some process such as backup, bulkload and NPAC traffic might take longer time to complete.

236725 3 Resolved Defer LSMS13.0 : Audit for single TN is taking more than 1 second.

Apart from the performance, there is not any negative system impact.

236761 3 Resolved Defer LSMS13.0 : LSMS Server is showing high CPU Utilization when bulkload is initiated on system.

No impact to customer operation.

236840 3 Resolved No-Fix LSMS13.0 : Fragmentation on norepl DB has been observed on LSMS Server.

No performance impact in case of fragmentation of that table.

236923 3 Resolved Defer LSMS 13.0 : Manual Re-sync under LNP Database Synchronization is not required.

No negative system impact. An error message is already displayed that the operation is not supported with ELAP 10.

237007 3 Resolved Defer LSMS13.0 : dbSort logs are not getting updated in case of MOP termination.

At this time due to the implementation of Solid State devices for storage Oracle no longer believes there is any issue that would require DB sort to be run. So there should be no impact to the customers. Note; The DB sort should not be run without contacting Oracle.

237203 3 Resolved No-Fix LSMS13.0_ST : Performance table on LSMS have different values on lsms Active and Standby.

Expected behavior. Both LSMS servers and DB can have different performance tables.

237295 3 Resolved No-Fix LSMS_13.0: LSMS GUI needs to be resizable.

No impact; screen resolution needs to be increased.

Page 9: Oracle® Communications LSMS · Oracle® Communications LSMS Release Notes Release 13.0 E54202 Revision 2 October 2014

LSMS 13.0 Release Notes

E54202 Revision 2 9 October 2014

PR# CSR? Sev Status Disposition Title Customer Impact

237387 3 Resolved Defer MAX_USER feature should be applied to LSMS CLI users

No negative impact to customer operation.

237659 3 Resolved No-Fix LSMS13.0_STP : lock.db file is not getting clear on NAS even after backup is completed

Situation not expected in the field. Problem will only occur if server is rebooted or backup process killed "improperly". Moreover there is a workaround (a manual delete of the lock.db file is possible).

237733 3 Resolved Defer LSMS_13.0: LQL queries should only be run from Active server.

Customer should run the command on the active server.

237893 3 Resolved Defer LSMS13.0_ST:Data being printed on LSMS CLI while creating spid, GTT group and modifying EMS routing .

No negative impact to customer operation.

238042 3 Resolved Defer LSMS13.0_FT : Warning is observed in queryserver.err log file present on query server

No negative impact to customer operation.

238107 3 Resolved Defer LSMS13.0_ST:Response file is not being generated while importing data on LSMS.

Response files will not be created when the input exceeds 2GB.

238178 3 Resolved Defer LSMS13.0_ST : Unwanted lines observed while initiating Db snapshot on LSMS

No negative impact to customer operation.

238390 3 Resolved Defer LSMS13.0_ST : User is able to successfully reconcile using old reconcile files.

No negative impact to customer operation.

238437 3 Resolved Defer Pop-UP Windows doesn't close properly while modifying LNP Threshold Value

Customer will make the changes and click on OK to close the window. They will not be able to close the window however they will be able to close the window after clinking on CANCEL. They may think that the changes were not saved.

238488 3 Resolved Defer LSMS13.0_ST:Incorrect message displayed on importing SPID.

Incorrect response text generated. No impact to normal operations.

238492 3 Resolved Defer LSMS13.0_ST: Error message is ambigous on LSMS GUI for QS Mysql port

No impact to customer operations.

238880 3 Resolved Defer E5MS_46:Some alarms are not displayed on Network Events and Alarms GUI.

Batched Alarms will not be forwarded properly.

239512 3 Resolved Defer Customer needs to be able to replace TKLC/Oracle self-signed SSL cert with external

No impact to normal customer operations.

Page 10: Oracle® Communications LSMS · Oracle® Communications LSMS Release Notes Release 13.0 E54202 Revision 2 October 2014

LSMS 13.0 Release Notes

E54202 Revision 2 10 October 2014

PR# CSR? Sev Status Disposition Title Customer Impact

239733 3 Resolved Defer LSMS13.0_ST:Warnings are observed when LSMS terminal left idle.

Occasional undesired output present on idle terminal sessions.

239738 3 Resolved Defer LSMS13.0_ST : EMS status varies between ACTIVE and STANDBY LSMS Server.

Status not displayed on the standby server.

239740 3 Resolved Defer LSMS13.0_ST : Incorrect message displayed while modifying Default GTT and Override GTT.

Additional popup box displayed upon saving/updating.

239852 3 Resolved Defer LSMS13.0_ST :Message Box stating that Reconcile Later is not observed.

No real impact to customer operations.

239861 3 Resolved Defer LSMS_13.0: Field is missed in the generated report.

Province field is missing from report.

240084 3 Resolved Defer LSMS13.0_ST: After upgrading Platcfg menu displaying unwanted options .

Options not applicable to system will be available on the menu. These options will not function and should be ignored.

19765938 3 Resolved Defer LSMS13.0_ST:Incorrect LSMS version and release displayed after TPD and upgrade

There could be some confusion as to the specific LSMS release. This is due to an error in release 13.0.0-130.17.0. The incorrect LSMS version (13.0.0_130.16.0 ) is displayed in the output of command rpm -qi TKLClsms and also in the version file. The correct release is shown using the command appRev.

19773194 3 Resolved Defer LSMS_13.0: Incorrect spelling is displayed

No impact to the customer as the message is still clear with "Resynch Successful". The synchronization was successful.

19773240 3 Resolved Defer LSMS13.0_ST:Backup of plat and plat-app gets stored at incorrect location

If the customer is performing a manual back up from the plafcfg menu, it is possible to cause the backup to go to the wrong location by going through multiple menu options. To avoid this bug, if taking manual backup and selecting xml configs (lsmsdb.xml, lsmslogs.xml or plat.xml) other than the intended backup, exit the platcfg menu and select only the intended xml option.

Page 11: Oracle® Communications LSMS · Oracle® Communications LSMS Release Notes Release 13.0 E54202 Revision 2 October 2014

LSMS 13.0 Release Notes

E54202 Revision 2 11 October 2014

Product Compatibility

Table RN-3 shows LSMS 13.0 compatibility with EAGLE and ELAP.

Table RN-3. E5-MS 46.0 Compatibility with Other Related Products

Product Release Compatibility

EAGLE 43.0 FC*

44.0 FC*

45.0 FC*

ELAP 8.0 NC

9.0 NC

10.0 FC

Note: LSMS 13.0 customers should upgrade their other products to the Fully Compatible releases identified in the table above.

Legend:

FC - Fully Compatible

NC - Not Compatible

* EAGLE dependencies are inherited from ELAP 10.0 compatibility matrix

Page 12: Oracle® Communications LSMS · Oracle® Communications LSMS Release Notes Release 13.0 E54202 Revision 2 October 2014

LSMS 13.0 Release Notes

E54202 Revision 2 12 October 2014

Oracle References and Services

Customer Access Support (CAS)

The Oracle Customer Access Support (CAS) is your initial point of contact for all product support needs. A representative takes your call or email, creates a Customer Service Request (CSR) and directs your requests to the Tekelec Technical Assistance Center (TAC). Each CSR includes an individual tracking number. Together with TAC Engineers, the representative will help you resolve your request.

The CAS is available 24 hours a day, 7 days a week, 365 days a year, and is linked to Engineers around the globe.

Oracle Tekelec TAC Engineers are available to provide solutions to your technical questions and issues 7 days a week, 24 hours a day. The Engineer determines the classification of the trouble after issuing a ticket. If a critical problem exists, emergency procedures are initiated. If the problem is not critical, normal support procedures apply. A primary Technical Engineer is assigned to work on the ticket and provide a solution to the problem. The ticket is closed when the problem is resolved.

Contact CAS by:

Phone: 1-800-223-1711 (toll-free, within continental USA and Canada) or see http://www.oracle.com/us/support/contact/index.html for the phone number of your local country.

When calling, make the following selections on the Support telephone menu:

Select 2 for New Service Request

Select 3 for Hardware, Networking and Solaris Operating System Support

Select 2 for Non-technical issue

You will be connected to a live agent who can assist you; simply mention you are a Tekelec Customer new to MOS and they will be happy to assist you.

Emergency Response

In the event of a critical service situation, emergency response is offered by the Customer Access Support 24 hours a day, 7 days a week. The emergency response provides immediate coverage, automatic escalation, and other features to ensure that the critical situation is resolved as rapidly as possible.

A critical situation is defined as a problem with the installed equipment that severely affects service, traffic, or maintenance capabilities, and requires immediate corrective action. Critical situations affect service and/or system operation resulting in one or several of these situations:

A total system failure that results in loss of all transaction processing capability

Significant reduction in system capacity or traffic handling capability

Loss of the system’s ability to perform automatic system reconfiguration

Inability to restart a processor or the system

Corruption of system databases that requires service affecting corrective actions

Loss of access for maintenance or recovery operations

Loss of the system ability to provide any required critical or major trouble notification

Any other problem severely affecting service, capacity/traffic, billing, and maintenance capabilities may be defined as critical by prior discussion and agreement with the Customer Care Center.