Oracle Communications LSMS · • Media Pack.....10 Delivery Cloud (OSDC). Documentation is delivered • Documentation Pack.....10 electronically on the Oracle Technology Network

Oracle® CommunicationsLSMSRelease Notes

Release 13.1

E61926 Revision 6

April 2016

Oracle Communications LSMS Release Notes, Release 13.1Copyright © 1993, 2016, Oracle and/or its affiliates. All rights reserved.

This software and related documentation are provided under a license agreement containing restrictionson use and disclosure and are protected by intellectual property laws. Except as expressly permitted in yourlicense 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. Reverseengineering, disassembly, or decompilation of this software, unless required by law for interoperability, isprohibited.

The information contained herein is subject to change without notice 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 iton behalf of the U.S. Government, then the following notice is applicable:

U.S. GOVERNMENT END USERS: Oracle programs, including any operating system, integrated software,any programs installed on the hardware, and/or documentation, delivered to U.S. Government end usersare "commercial computer software" pursuant to the applicable Federal Acquisition Regulation andagency-specific supplemental regulations. As such, use, duplication, disclosure, modification, and adaptationof the programs, including any operating system, integrated software, any programs installed on thehardware, and/or documentation, shall be subject to license terms and license restrictions applicable to theprograms. No other rights are granted to the U.S. Government.

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 applicationsthat 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 toensure its safe use. Oracle Corporation and its affiliates disclaim any liability for any damages caused byuse of this software or hardware in dangerous applications.

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

Intel and Intel Xeon are trademarks or registered trademarks of Intel Corporation. All SPARC trademarksare 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 AdvancedMicro Devices. UNIX is a registered trademark of The Open Group.

This software or hardware and documentation may provide access to or information about content, products,and services from third parties. Oracle Corporation and its affiliates are not responsible for and expresslydisclaim all warranties of any kind with respect to third-party content, products, and services unless otherwiseset forth in an applicable agreement between you and Oracle. Oracle Corporation and its affiliates will notbe responsible for any loss, costs, or damages incurred due to your access to or use of third-party content,products, or services, except as set forth in an applicable agreement between you and Oracle.

Table of Contents

Chapter 1: Introduction.................................................................................6

Chapter 2: Feature Descriptions..................................................................7LSMS Segmented Network Configuration Support ........................................................................8

Hardware Requirements...........................................................................................................8Limitations..................................................................................................................................8

Enhancement Bugs.................................................................................................................................8

Chapter 3: Media and Documentation.......................................................9Media Pack............................................................................................................................................10

TPD and LSMS Application Installation...............................................................................10Documentation Pack............................................................................................................................10

Chapter 4: Upgrade Paths...........................................................................12Upgrade Path........................................................................................................................................13Migration Path......................................................................................................................................13

Chapter 5: Product Compatibility.............................................................14Product Compatibility.........................................................................................................................15LSMS Query Server Compatibility....................................................................................................15

Chapter 6: Resolved and Known Bugs...................................................17Severity Definitions..............................................................................................................................18Resolved Bug Listing...........................................................................................................................18Customer Known Bug Listing............................................................................................................20

Chapter 7: Oracle References and Services.............................................30My Oracle Support (MOS)..................................................................................................................31Emergency Response...........................................................................................................................31Customer Training...............................................................................................................................32

iiiE61926 Revision 6, April 2016

Locate Product Documentation on the Oracle Help Center Site...................................................32Locate Product Release Software on the Oracle Software Delivery Cloud Site..........................32

Appendix A: Firmware Components.......................................................34

ivE61926 Revision 6, April 2016

List of Tables

Table 1: LSMS 13.1 Enhancement Bugs...........................................................................................................8

Table 2: Media Pack Contents........................................................................................................................10

Table 3: Documentation Pack Contents........................................................................................................10

Table 4: LSMS 13.1 Upgrade Path..................................................................................................................13

Table 5: LSMS 13.1 Migration Path................................................................................................................13

Table 6: LSMS 13.1 Compatibility with Other Related Products..............................................................15

Table 7: LSMS 13.1 Compatibility with the LSMS Query Servers............................................................16

Table 8: LSMS Release 13.1.1 Resolved Bugs (12/18/15)...........................................................................19

Table 9: LSMS Release 13.1 Resolved Bugs (6/9/15)..................................................................................19

Table 10: LSMS Release 13.1 Customer Known Bugs (12/18/15)............................................................20

vE61926 Revision 6, April 2016

Chapter

1Introduction

This Release Notes includes Feature Descriptions,Media and Documentation pack contents, ProductCompatibility and identifies the supported UpgradePath and Migration Paths (if applicable). Thisdocument also includes listings of both the Resolvedand Known Bugs for this Release. Directions foraccessing key Oracle sites and Services are alsoidentified in the Oracle References and Serviceschapter.

Release Notes are included in the DocumentationPack made available with every Software Release.

6E61926 Revision 6, April 2016

Chapter

2Feature Descriptions

This Release delivers the following feature:Topics:

• LSMS Segmented Network Configuration Support• LSMS Segmented Network Configuration Support.....8

• Enhancement Bugs.....8


LSMS Segmented Network Configuration Support

The LSMS Segmented Network Configuration support feature allows customers to have segmentednetwork architecture with the LSMS running on E5-APP-B cards. This feature allows the use of asegmented network to separate the Northbound (NPAC) and Southbound (ELAP, GUI, NAS)connections, where the eth0 port is used to connect to the NPAC. The eth1 port is used to connect tothe EMS, Application and NAS. There is no functionality change of ports eth2 and eth3.

Hardware Requirements

There are more switch/router ports required to enable the segmented configuration. The customer isresponsible for providing the switch/switch ports for the segmented configuration.

Limitations

• In the segmented configuration, if the eth1 port goes down no functionality (NAS, GUI, EMS, etc.)dependent on this port will work.

Enhancement Bugs

LSMS 13.1 supports these enhancement Bugs:

Table 1: LSMS 13.1 Enhancement Bugs

DescriptionBug # and Title

LSMS 13.1 adds HTTPS support for the LSMSGUI.

20488952

Add HTTPS support for LSMS GUI

LSMS 13.1 removes X11 forwarding over SSH.20618240

Remove "local" SSH/X11 based GUI & JRE

LSMS Query Server 13.0 supports Solaris 10 andis fully compatible with LSMS 13.1. If you need

22836521

LSMS Query Server 13.1 Must Support Solaris 11Only to host your LSMS Query Server on Solaris 11 for

use with LSMS 13.1, use LSMS Query Server 13.1.


Feature DescriptionsRelease Notes

Chapter

3Media and Documentation

Oracle Communications software is available forelectronic download on the Oracle Software

Topics:

• Media Pack.....10 Delivery Cloud (OSDC). Documentation is delivered• Documentation Pack.....10 electronically on the Oracle Technology Network

(OTN). Both the software Media Pack and theDocumentation Pack are listed in this chapter.


Media Pack

All components available for download from the Oracle Software Delivery Cloud(https://edelivery.oracle.com/) are in Table 2: Media Pack Contents.

Note: This list is accurate at the time of release, but is subject to change. Please view the Oracle SoftwareDelivery Cloud site for the latest information.

Table 2: Media Pack Contents

Name

Oracle Communications LSMS Query Server (13.1.0-131.10.0)

Oracle Communications LSMS (13.1.1-131.9.0)

Oracle Communications LSMS (13.1.0-131.8.0)

Oracle Communications Tekelec Platform Distribution 5.5.1-75.20.0 - 32 bit

Oracle Communications Tekelec Platform Distribution 5.5.1-75.23.0 - 64 bit

TPD and LSMS Application Installation

When upgrading to LSMS 13.1, the LSMS Primary and Secondary servers' new installation is IPM'dto TPD 5.5.1-75.20.0 32-bit, then the LSMS application installation will include an incremental upgradeto TPD 5.5.1-75.23.0.

The NAS server's new installation is IPM'd to TPD 5.5.1-75.23.0 64-bit. There is no NAS application.

Once installation is complete, all servers will be running TPD version 5.5.1-75.23.0.

Documentation Pack

All documents available for download from the Oracle Technology Network (OTN) site(http://docs.oracle.com) are listed in Table 3: Documentation Pack Contents.

Note: This list is accurate at the time of release but is subject to change. See Oracle Help Center forthe latest information.

Table 3: Documentation Pack Contents

Core LSMS Documentation

Release Notes

Administration and LNP Feature Activation Guide

Software Upgrade/Installation Guide

Configuration Guide


Media and DocumentationRelease Notes

https://edelivery.oracle.com/

http://docs.oracle.com

Security Guide

LNP Database Synchronization User's Guide

Database Administrator's Guide

LSMS Query Server Documentation

LSMS Query Server Installation and Upgrade Guide

LSMS Query Server Security Guide

LSMS Query Server Licensing Information Reference

Hardware, Installation, and Maintenance Documentation

Alarms and Maintenance Guide

EAGLE Application B Card Hardware and Installation Guide

Reference Documentation

LSMS Licensing Information User's Guide


Media and DocumentationRelease Notes

Chapter

4Upgrade Paths

This release has been tested for upgrades fromspecific prior releases; this chapter contains the exact

Topics:

• Upgrade Path.....13 paths for upgrade. Please verify that your currentinstalled release is listed on a valid upgrade path.• Migration Path.....13


Upgrade Path

The possible upgrade path to LSMS 13.1 is listed below.

Table 4: LSMS 13.1 Upgrade Path

ToFrom

LSMS Release 13.1LSMS Release 13.0

Migration Path

The possible migration path to LSMS 13.1 is listed below.

Table 5: LSMS 13.1 Migration Path

ToFrom

LSMS Release 13.1.y (running on the E5-APP-BCard version 02)

LSMS Release 12.0.x (running on T1100 Servers)

Note: Migration from T1100 servers is for a Segmented Network only.


Upgrade PathsRelease Notes

Chapter

5Product Compatibility

This section shows release-specific compatibilitywith other related products.

Topics:

• Product Compatibility.....15• LSMS Query Server Compatibility.....15


Product Compatibility

Table 6: LSMS 13.1 Compatibility with Other Related Products shows LSMS 13.1 compatibility with otherproducts.

Table 6: LSMS 13.1 Compatibility with Other Related Products

CompatibilityReleaseProduct

N/A45.0EAGLE EMS

FC46.0

NC8.0ELAP

NC9.0

FC10.0

FC*43.0EAGLE

FC*44.0

FC*45.0

FC*46.0

NC**46.1

FC*46.2

Note: LSMS 13.2 customers should upgrade their other products to the Fully Compatible releasesidentified in the table above.

Legend:

• FC - Fully Compatible• PC - Partially Compatible - Product combinations are functional but have not undergone complete

regression testing. Some feature capabilities may not be fully functional or supported.• N/A - Not Applicable• NC - Not compatible• * EAGLE dependencies are inherited from ELAP 10.0 compatibility matrix• ** EAGLE 46.1 is excluded from the North American market

LSMS Query Server Compatibility

Table 7: LSMS 13.1 Compatibility with the LSMS Query Servers shows LSMS 13.1 compatibility with theLSMS Query Servers.


Product CompatibilityRelease Notes

Table 7: LSMS 13.1 Compatibility with the LSMS Query Servers

CompatibilityLSMS Query Server

NC12.0

FC13.0

FC13.1

Legend:

• FC - Fully Compatible• NC - Not Compatible


Product CompatibilityRelease Notes

Chapter

6Resolved and Known Bugs

This chapter lists the Resolved and Known Bugs forthis release.

Topics:

• Severity Definitions.....18These bug lists are distributed to customers with anew software release at the time of General• Resolved Bug Listing.....18

• Customer Known Bug Listing.....20 Availability (GA), and are updated for eachMaintenance release.


Severity Definitions

The problem report sections in this document refer to Bug severity levels. Definitions of these levelscan be found in the publication, TL 9000 Quality Management System Measurement Handbook.

Problem Report: A report from a customer or on behalf of the customer concerning a product or processdefect requesting an investigation of the issue and a resolution to remove the cause. The report maybe issued via any medium. Problem reports are systemic deficiencies with hardware, software,documentation, delivery, billing, invoicing, servicing or any other process involved with the acquisition,operation, or performance of a product. An incident reported simply to request help to bring back theservice or functionality to normal without the intent to investigate and provide a resolution to thecause of the incident is not a problem report.

• Critical: Conditions that severely affect the primary functionality of the product and because ofthe business impact to the customer requires non-stop immediate corrective action, regardless oftime of day or day of the week as viewed by a customer on discussion with the organization suchas

1. product inoperability (total or partial outage),2. a reduction in the capacity capability, that is, traffic/data handling capability, such that expected

loads cannot be handled,3. any loss of emergency capability (for example, emergency 911 calls), or4. safety hazard or risk of security breach

• Major: Product is usable, but a condition exists that seriously degrades the product operation,maintenance or administration, etc., and requires attention during pre-defined standard hours toresolve the situation. The urgency is less than in critical situations because of a lesser immediateor impending effect on product performance, customers and the customer's operation and revenuesuch as

1. reduction in product's capacity (but still able to handle the expected load),2. any loss of administrative or maintenance visibility of the product and/or diagnostic capability,3. repeated degradation of an essential component or function, or4. degradation of the product's ability to provide any required notification of malfunction

• Minor: Other problems of a lesser severity than 'critical' or 'major' such as conditions that havelittle or no impairment on the function of the system

• Minor, No Loss of Service: Oracle severity beyond what is defined by TL 9000.

The numbered severity levels in the tables below correspond to these definitions:

• 1 - Critical• 2 - Major• 3 - Minor• 4 - Minor, No Loss of Service

Resolved Bug Listing

The tables in this section list bugs that are resolved in the following builds:


Resolved and Known BugsRelease Notes

LSMS 13.1.1-131.9.0.

LSMS 13.1.0-131.8.0.

The Resolved Bugs table shows an impact statement for Severity 1 and 2 Bugs as well as for Severity3 Bugs that are associated with a SR.

Note: Resolved bugs are sorted in ascending order by severity, then bug number.

Table 8: LSMS Release 13.1.1 Resolved Bugs (12/18/15)

Customer ImpactTitleSevSRBug #

LSMS13.1_FT: Getting error messagein the upgrade.log after incrementalupgrade

421110720

Update TPD421911198

Table 9: LSMS Release 13.1 Resolved Bugs (6/9/15)


[238391] LSMS uses old version ofXerces-C.

319115400

[238392] LSMS uses old version ofXerces-J.

319115401

[238394] LSMS uses old version ofperl-DBD-MySQL.

319115403

[238395] LSMS uses old version ofxulrunner.

319115404

NAS initial configuration does notwork if the root password is changedon NAS.

320044726

LSMS support for TPD 75.21.320407021

LSMS_13.0: No error is displayedwhen system is upgraded to samerelease.

320429962

LSMS13.0_ST:Incorrect LSMS versionand release displayed after TPD andupgrade.

319765938

Remove "local" SSH/X11 based GUI& JRE.

320096107

POR: Add support for HTTPS.320146236

POR: LSMS Segmented NetworkConfiguration Support.

320654334

Support Java 1.8 client.320762198




IP_GUI feature can be removed.320854352

Customer Known Bug Listing

Table 10: LSMS Release 13.1 Customer Known Bugs (12/18/15) lists known bugs in this release:

Table 10: LSMS Release 13.1 Customer Known Bugs (12/18/15)

Customer ImpactTitleDispositionStatusSevSRBug#

No impact to customeroperation.

[236291]LSMS_13.0:"npacagent" core file isgenerated on LSMS

DeferResolved319112659

Invalid ID is observed afterclosing the LSMS Java GUI

[236581]LSMS 13.0 : OnLSMS GUI Java pop of


and the browser is still"Invalid Session ID" isobserved open. There is no negative

system impact.

System speed duringsavelogs operation isreduced.

[236713]LSMS 13.0 : LSMSserver is showing highutilization when we startcapturing save logs fromGUI


While servdi is in progress,some process such as

[236723]LSMS13.0 : LSMSServer is showing high CPU


backup, bulkload andUtilization when ServdiNPAC traffic might takelonger time to complete.

process is initiated withdelay

Apart from theperformance, there is not

[236725]LSMS13.0 : Auditfor single TN is taking morethan 1 second


any negative systemimpact.

No impact to customeroperation.

[236761]LSMS13.0 : LSMSServer is showing high CPUUtilization when bulkloadis initiated on system


No negative system impact.An error message is

[236923]LSMS 13.0 : ManualRe-syn under LNP Database


already displayed that theSynchronization is notrequired operation is not supported

with ELAP 10.




At this time due to theimplementation of Solid

[237007]LSMS13.0 : dbSortlogs are not getting updatedincase of MOP termination


State devices for storageOracle no longer believesthere is any issue thatwould require DB sort tobe run. So there should beno impact to the customers.Note: The DB sort shouldnot be run withoutcontacting Oracle.

No negative impact tocustomer operation.

[237387]MAX_USER featureshould be applied to LSMSCLI users


Customer should run thecommand on the activeserver.

[237733]LSMS_13.0: LQLqueries should only be runfrom Active server.



[237893]LSMS13.0_ST:Databeing printed on LSMS CLIwhile creating spid, GTT


group and modifying EMSrouting


[238042]LSMS13.0_FT :Warning is observed inqueryserver.err log filepresent on query server


Response files will not becreated when the inputexceeds 2GB.

[238107]LSMS13.0_ST:Responsefile is not being generatedwhile importing data onLSMS



[238178]LSMS13.0_ST :Unwanted lines observedwhile initiating Db snapshoton LSMS



[238390]LSMS13.0_ST : Useris able to successfullyreconcile using old reconcile


Incorrect response textgenerated. No impact tonormal operations.

[238488]LSMS13.0_ST:Incorrectmessage displayed onimporting SPID.


No impact to customeroperations.

[238492]LSMS13.0_ST: Errormessage is ambiguous onLSMS GUI for QS Mysqlport





Batched Alarms will not beforwarded properly.

[238880]E5MS_46:Somealarms are not displayed onNetwork Events and AlarmsGUI.


Occasional undesiredoutput present on idleterminal sessions.

[239733]LSMS13.0_ST:Warningsare observed when LSMSterminal left idle.


Status not displayed on thestandby server.

[239738]LSMS13.0_ST : EMSstatus varies betweenACTIVE and STANDBYLSMS Server.


Additional popup boxdisplayed uponsaving/updating.

[239740]LSMS13.0_ST :Incorrect message displayedwhile modifying DefaultGTT and Override GTT


No real impact to customeroperations.

[239852]LSMS13.0_ST:Message Box stating thatReconcile Later is notobserved.


Province field is missingfrom report.

[239861]LSMS_13.0: Field ismissed in the generatedreport.


Options not applicable tosystem will be available on

[240084]LSMS13.0_ST: Afterupgrading Platcfg menu


the menu. These optionsdisplaying unwantedoptions . will not function and

should be ignored.

An alarm is raised on GUIwithout any side effect.

[240919]LSMS13.0_ST:Switchover complete alarm isobserved on LSMS GUI.


Should not be of muchissue for the customer.

There is no additionalinformation provided for

Connection with NPACaborted by NPACAgent forinternal failure


the abort to be able totroubleshoot and fix whatis causing the connectionfailure.

If customer is performingmanual back up from the

LSMS13.0_ST:Backup of platand plat-app gets stored atincorrect location .


plafcfg menu it is possibleto cause the backup to goto the wrong location bygoing through multiplemenu option. To avoid this



Customer ImpactTitleDispositionStatusSevSRBug#bug, if taking manualbackup and selected xmlconfigs (lsmsdb.xml,lsmslogs.xml or plat.xml)other than the intendedbackup, exit the platcfgmenu and select only theintended xml option.

Incorrect error regardingswitch over may occurwhen standby server is lost.

LSMS13.1_FT: Unexpectedalarm observed on LSMSGUI


When the heartbeat cablesare removed from the

LSMS13.1_FT:Unstablebehavior shown on loss of


LSMS server, the activeconnectivity with heartbeatcable server goes into ACTIVE

"INHIBITED" and thestandby server goes intoSTANDBY "INHIBITED"which is the expectedbehavior. This can becorrected using thehafailover --noinhibitcommand.

At startNode the LSMS isjust started. No other

LSMS13.1_FT: High CPUutilization while startingnode on LSMS


operation can take place.So high cpu utilizationduring startNode is not abig issue to customer.

No impact. It is verydoubtful that a customer

LSMS13.1_FT:Statusdisplayed on active and


will try to run astandby server fornon-existing ELAP non-existing CLLI from the

command line. Runningthe command for anon-existing CLLI does notdo any harm. Moremeaningful error outputwould be helpful.

The switch over alarm isnot generated upon loss of

LSMS13.1_FT: Switch overalarm is not observed onLSMS GUI


network connectivity to theprimary server. Thecustomer may not noticethat switch over hasoccurred and thereforewould not have an



Customer ImpactTitleDispositionStatusSevSRBug#opportunity to address thenetwork issue that causedthe switch over. Note thatthe switch over itself issuccessful.

The HTTP/HTTPS bannermessage is not shown upon

LSMS13.1_FT:On freshLSMS setup ,banner


initial installation of themessage about http/https isnot observed LSMS software. When

there is a change to HTTPSoptions, the bannermessage will be shown.The command"httpConfig.pl status" canbe used to display theHTTP/HTTPS status.

The condition will arise ifa time-consuming

LSMS13.1_FT: Issue whileviewing logs when day ischanged


operation (e.g., bulkload,audit or servdi) is startedjust before midnight. Theuser will not be able toview the logs of theoperation that justcompleted from the currentGUI screen. The log file canbe viewed using a vi editorif the pathname is known.

The user should choose afile that is shown in the

LSMS13.1_FT: List of all filesdisappear if we try to deletenon-existing file


browser window. If anon-existing file isattempted to be opened,the file list that was shownearlier is removed. Theuser can close the currentwindow and reopen thesame window to see all theexisting files in thebrowsed path again, andthen choose an existing file.

This may cause the backupto take longer in somecases.

LSMS13.1_FT: Effect of HighCPU utilization on backup.


A wrong message is loggedonce. The process starts

LSMS13.1_FT:lsmsSNMPagent failure




Customer ImpactTitleDispositionStatusSevSRBug#properly. No impact tocustomer.

observed while startinglsmsSNMP agent

Some parts of the featuremay work without it beingenabled.

LSMS13.1_FT: Recoveryhappens without enablingCANADA_SPID_RECOVERYfeature


The network re-configconfirmation page might

LSMS13.1_ST:NetworkReconfiguration on singledisplaying segmented menu


be confusing as VIP isdisplayed as APP VIP. Butthere is no negative systemimpact, the networkconfiguration is successfulas expected.

Problem is simulated if aCPU-hogging process is

LSMS13.1_ST: Not able toperform Backup on LSMS


started when aCPU-hogging process isalready in progress.Customers should not starta SERVDI when a backupis in progress or vice versa.

When diagnostics are runusing lsmsmgr, an error is

LSMS13.1_ST: Getting errorlogs on


logged, although/var/TKLC/log/platcfg inLSMS 13.1 diagnostics are run

successfully. Using theplatcfg menu will rundiagnostics with no errors.

The Exit option is visible ina normal PuTTY window.

LSMS13.1_ST: "Exit" is notdisplaying properly forConfigure Hosts-->Edit path


It is also visible in a smallerwindow up to a limit. Theuser can open anormal-sizedPuTTY/xterm window andeverything works fine. Nocustomer impact.

If theENHANCED_FILTERS

LSMS13.1_ST: Enhance filteris not getting disabled


feature is turned OFF thenuser is not able to switch tocustom filter in EMSRouting, but they will notbe able to switch back tothe regional filter. If the



Customer ImpactTitleDispositionStatusSevSRBug#user wants to disable theregional filters by disablingthe ENHANCED_FILTERSfeature, they should firstmove to Custom Filterrouting.

The parameters for accountexpiration date and

LSMS13.1_ST: Command"lsmsdb -c adduser -u


maximum number of days<username>" is notappropriate between logins will result

in the user's account beingdeclared invalid at theearlier of the twoconditions specified by theparameters.

Extra lines are displayed.LSMS13.1_ST: Extra line isgetting pegged while


executing commandlsmsSNMP stop

The view tab is disabledwhen doing the following:

LSMS13.1_ST: View tab is indisable mode whileaccessing lsmsview user.


Login to LSMS GUI aslsmsadm user. Switch userto lsmsview, access the tabas LSMS->Default GTT. Allthe tabs including the"view" tab will be disabled.

If apply and cancel areused close together there

LSMS13.1_ST:-Reports GUIdisabled when apply and


will be an error for aninvalid report.

cancel operatedsimultaneously.

The audit logs are alwayson the active server.

LSMS13.1_ST:Issue inviewing audit logs onstandby server


User can create report onstandby server even

LSMS13.1_ST: Issue inviewing report from standbyserver.


though it cannot be used.Reports are supposed to becreated on active server.

Failure of manual backupmay not get logged.

LSMS13.1_ST: Surveillancealarm not getting generatedin case of manual backup


It would take longer to IPMthe system with the TPD

LSMS13.1: On LSMSApplication installation istaking longer time


version that is embedded



Customer ImpactTitleDispositionStatusSevSRBug#within LSMS. To avoid this,only the previous TPD isprovided for system IPM.

If a patch is applied to asystem, the system may

LSMS13.0:Incorrect LSMSrelease being displayed afterpatch installation.


display the wrong releaseversion.

No known impact at thistime.

LSMS13.1_ST: ProcessControl core is observed onlsms13.1


May have to do initialsetup again to get setup towork.

LSMS13.1:Error observedwhile doing networkreconfiguration on LSMS13.1


User should only restorethe backup on the same

LSMS13.1_ST:Mysqlreplication stops afterrestore.


server the backup wasdone from to avoid this.

The Customer will see the90% full alarm and

db partition in LSMS 13.1exceeds 90% very easily.


syscheck will report thesame. No operationalimpact unless the databasepartition reaches close to100%. This also effectsUpgrade as upgrade is notallowed due to thesyscheck error.

After a patch is appliedthere may be warning

LSMS_12.0: One module inclass "proc" under syscheckoutput is getting failed


messages in syscheckmodules. There is no otherknown impact.

This occurred whenimplementing a patch.

LSMS_12.0: Core files hasbeen generated on LSMSserver


Only known impact isalarm for core files.

CLLI tool tip is not beingdisplayed. The tool tip

LSMS13.1_FT: On LSMSGUI "show tool tip" optionis not working on EMS icon.


would show some help onthe purpose/status of theCLLI. It should be presentfor the ease of use for theend user.




If there is only one userdefined on the server and

LSMS13.1:Modify/Viewuser level password time out


the width of the dialog boxwindow is not workingproperly is decreased, the user is not

visible. Increase the size ofthe dialog box to view theuser.

User will have to cancel thedelete dialog box by

LSMS13.1_FT: Errormessage is displayed on


clicking on the "No" buttonin the dialog box.

clicking 'X' of delete dialogbox

The End user cannot useshortcut key to open the

LSMS13.1_FT: Usingshortcut key 'p' the control


Dialog Box. He has to useshifts from primary tosecondary the GUI and Mouse or GUI

and Arrow/Enter Key toopen the required DialogBox.

The error message isdisplayed after entering

LSMS13.1_FT: commandclass feature pop up is


data. Customer wasteddisplayed at a very laterstage time entering data that will

not be saved. No realimpact.

These messages do nothave any negative impact

LSMS13.1_FT: Unexpectedwarnings are received onLSMS console.


on the working of LSMS.These messages areobserved only on theConsole terminal if keptopen.

An extra line is loggedcreating a little confusionto the end user.

LSMS13.1_FT:Unexpectedlines pegged in backend.log


No known issue at thistime.

LSMS13.1_ST: mysql core isobserved on lsms13.1


When the SNMPAgent isstopped or started from

LSMS13.1_ST: SNMP logsare not getting update whileterminating SNMP agent


within the LSMSapplication, the activity islogged properly. When theSNMPAgent is killed by aUnix command, the activityis not logged. A Unixcommand can be used to



Customer ImpactTitleDispositionStatusSevSRBug#check if the SNMPAgentwas killed. No real impact.

This issue is currentlyhandled by the restore

LSMS does not come upafter restoring DB from NAS


procedure in theMaintenance Manual. Butto avoid the chance ofhuman error, this bug isopen to improve thesoftware to handle thisautomatically in a futurerelease.

Files are updated in spiteof the error message. There

LSMS13.1_FT: Getting errormessage in the upgrade.logafter incremental upgrade


is no impact on theupgrade or systemoperation.

Even for the single subnetconfiguration, the gateway

SR: Unnecessary duplicateentry needed in singlesubnet configuration


address must be enteredtwice. This is only doneduring installation.



Chapter

7Oracle References and Services

Topics:

• My Oracle Support (MOS).....31• Emergency Response.....31• Customer Training.....32• Locate Product Documentation on the Oracle Help

Center Site.....32• Locate Product Release Software on the Oracle

Software Delivery Cloud Site.....32


My Oracle Support (MOS)

MOS (https://support.oracle.com) is your initial point of contact for all product support and trainingneeds. A representative at Customer Access Support (CAS) can assist you with MOS registration.

Call the CAS main number at 1-800-223-1711 (toll-free in the US), or call the Oracle Support hotlinefor your local country from the list at http://www.oracle.com/us/support/contact/index.html. When calling,make the selections in the sequence shown below on the Support telephone menu:

1. Select 2 for New Service Request2. Select 3 for Hardware, Networking and Solaris Operating System Support3. Select one of the following options:

• For Technical issues such as creating a new Service Request (SR), Select 1• For Non-technical issues such as registration or assistance with MOS, Select 2

You will be connected to a live agent who can assist you with MOS registration and opening a supportticket.

MOS is available 24 hours a day, 7 days a week, 365 days a year.

Emergency Response

In the event of a critical service situation, emergency response is offered by the Customer AccessSupport (CAS) main number at 1-800-223-1711 (toll-free in the US), or by calling the Oracle Supporthotline for your local country from the list at http://www.oracle.com/us/support/contact/index.html. Theemergency response provides immediate coverage, automatic escalation, and other features to ensurethat 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 affectservice 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 capabilitiesmay be defined as critical by prior discussion and agreement with Oracle.


Oracle References and ServicesRelease Notes

https://support.oracle.com

http://www.oracle.com/us/support/contact/index.html

http://www.oracle.com/us/support/contact/index.html

Customer Training

Oracle University offers expert training on Oracle Communications solutions for service providersand enterprises. Make sure your staff has the skills to configure, customize, administer, and operateyour communications solutions, so that your business can realize all of the benefits that these richsolutions offer. Visit the Oracle University web site to view and register for Oracle Communicationstraining: education.oracle.com/communication. To reach Oracle University:

• In the US, please dial 800-529-0165.

• In Canada, please dial 866-825-9790.

• In Germany, please dial 0180 2000 526 (toll free) or +49 8914301200 (International).

• In Spain, please dial +34 91 6267 792.

• In the United Kingdom, please dial 0845 777 7 711 (toll free) or +44 11 89 726 500 (International).

For the appropriate country or region contact phone number for the rest of the world, please visitOracle University's web site at http://www.oracle.com/education/contacts.

Locate Product Documentation on the Oracle Help Center Site

Oracle Communications customer documentation is available on the web at the Oracle Help Center(OHC) site, http://docs.oracle.com. You do not have to register to access these documents. Viewing thesefiles requires Adobe Acrobat Reader, which can be downloaded at http://www.adobe.com.

1. Access the Oracle Help Center site at http://docs.oracle.com.2. Click Industries.3. Under the Oracle Communications subheading, click the Oracle Communications

documentation link.The Communications Documentation page appears. Most products covered by these documentationsets will appear under the headings “Network Session Delivery and Control Infrastructure” or“Platforms.”

4. Click on your Product and then the Release Number.A list of the entire documentation set for the selected product and release appears.

5. To download a file to your location, right-click the PDF link, select Save target as (or similarcommand based on your browser), and save to a local folder.

Locate Product Release Software on the Oracle Software Delivery CloudSite

Oracle Communications software is available for electronic download at the Oracle Software DeliveryCloud (OSDC) site, https://edelivery.oracle.com. Only authorized customers with a valid password maydownload software from the site.



http://education.oracle.com/pls/web_prod-plq-dad/ou_product_category.getFamilyPage?p_family_id=41&p_mode=Training&sc=WWOU14047594MPP002C005

http://www.oracle.com/education/contacts


http://www.adobe.com


https://edelivery.oracle.com

For directions on downloading the software and other information about using this site, click theFAQ button on the top right corner.



Appendix

AFirmware Components

This appendix is not applicable to EAGLE, ExAP orLSMS releases.


Documents

Oracle Communications LSMS · • Media Pack.....10 Delivery Cloud (OSDC). Documentation is delivered • Documentation Pack.....10 electronically on the Oracle Technology Network