pe-omc-app-018438_0112_en

8/3/2019 pe-omc-app-018438_0112_en

http://slidepdf.com/reader/full/pe-omc-app-0184380112en 1/121

OMC-R FIXES V15.1/V15.1R2 PostChR

Document number: PE/OMC/APP/018438Document issue: 01.12 / ENDocument status: StandardDate: 20/Jul/2007

External document

Copyright© 2006 Nortel Networks, All Rights Reserved

Printed in France

NORTEL CONFIDENTIAL

The information contained in this document is the property of Nortel Networks. Except as specifically authorized in

writing by Nortel Networks, the holder of this document shall keep the information contained herein confidential

and shall protect same in whole or in part from disclosure and dissemination to third parties and use same for

evaluation, operation and maintenance purposes only.

The content of this document is provided for information purposes only and is subject to modification. It does not

constitute any representation or warranty from Nortel Networks as to the content or accuracy of the information

contained herein, including but not limited to the suitability and performances of the product or its intended

application.

The following are trademarks of Nortel Networks: *NORTEL NETWORKS, the NORTEL NETWORKS corporate

logo, the NORTEL Globemark, UNIFIED NETWORKS. The information in this document is subject to change

without notice. Nortel Networks assumes no responsibility for errors that might appear in this document.

All other brand and product names are trademarks or registered trademarks of their respective holders.

8/3/2019 pe-omc-app-018438_0112_en



Nortel Networks confidential

PE/OMC/APP/018438 01.12 / EN Standard 20/Jul/2007 Page 2/121

PUBLICATION HISTORY

03/Mar/2006

Issue 01.01/ EN

Creation for V15.1 CL2 / V15.1R2 CL1 delivery

AVL 24032 OMC_APPLI V15_01.FR

AVL 21904 DS_OMC_CIUS V15_01.BV

AVL 23265 PE_UPGPRECHECK V15_01.E0Hd

AVL 23264 PE_VERSUPGPRECHECK V15_01.EH9g

28/Mar/2006

Issue 01.02/ EN

Update with the following deliveries:

AVL 22492 PE_UPG_FW_T3 V02_00.E01

AVL 21099 PE_OSILOGD_PATCH V15_01.E01

AVL 23687 PE_HSI-P V03_01.E00

30/Mar/2006

Issue 01.03/ EN

Installation/fallback of the AVL 23687 described.

Added chapter “Known issues”.

17/May/2006

Issue 01.04/ EN

The document was updated with soak period report for V15.1 CL2 load.

19/June/2006

Issue 01.05/ EN

The document was updated with the following deliveries:

AVL 25000 OMC_APPLI V15_01.HR

AVL 24750 PE_EMERGENCY_PATCH V15_01.E06

24/July/2006

Issue 01.06/ EN

The document was updated with the following deliveries:


8/3/2019 pe-omc-app-018438_0112_en





30/Aug/2006

Issue 01.07/ EN

The document was updated with soak period report for AVL 25129.

16/Oct/2006

Issue 01.08/ EN

The document was updated with soak period report for V15.1R2 CL1 load.

27/Oct/2006

Issue 01.09/ EN

The document was updated for V15.1R2 CL2 delivery:

AVL 25757 OMC_APPLI V15_01.IR


20/Dec/2006

Issue 01.10/ EN

The document was updated for V15.1R2 EP delivery:

AVL 26237 OMC_APPLI V15_01.JR

27/Feb/2007

Issue 01.11/ EN


AVL 26597 OMC_APPLI V15_01.KR

20/Jul/2007

Issue 01.12/ EN


AVL 27450 OMC_APPLI V15_01.LR

8/3/2019 pe-omc-app-018438_0112_en





CONTENTS

1. INTRODUCTION ............................................................................................................................ 8 1.1. OBJECT.................................................................................................................................... 8 1.2. SCOPE OF THIS DOCUMENT .......................................................................................................8 1.3. AUDIENCE FOR THIS DOCUMENT ................................................................................................8

2. RELATED DOCUMENTS .............................................................................................................. 8 2.1. APPLICABLE DOCUMENTS ..........................................................................................................8 2.2. REFERENCE DOCUMENTS ..........................................................................................................8

3. V15.1 CL2 / V15.1R2 CL1 CONTENTS ........................................................................................9 3.1. DEFINITION............................................................................................................................... 9 3.2. CORRECTIVE LOAD : AVL 24032 – OMC_APPLI V15_01.FR ..................................................10

3.2.1 CR fixed for GSM and GSM-R customers .................................................................10 Q01245876-01 : TMOCHIC:V15.1: CT/CPT insert record was failed to trace_db database ....... 10 Q01252014 : TMOBELV:V15.1: When cf_save_tool.x is stuck, the MMI is not functional .......... 13 Q01252014-03 : TMOBELV:V15.1: When cf_save_tool.x is stuck, the MMI is not functional ..... 15 Q01252718 : TMOCHIC:V15.1: system() used in multithread tasks is unstable. .......................17 Q01280824-01 : PREINT160: Configref M/N13: incorrect BTS configuration ............................. 19 Q01243900-03 : GSM : V15.0.1 : OSK : Configref M/N24 missing in CT2K ...............................21 Q01287440 : CM:Variance between documentation and OMC-R behavior ................................23 Q01135458-01 : PREINT 154: CFG creates incorrect command files ........................................25 Q01186607-02 : Cyclic OMC-R restart ........................................................................................26 3.2.2 CR fixed only for GSM-R customers .........................................................................29 3.2.3 Regression Tests ........................................................................................................29

3.3. CORRECTIVE LOAD : AVL 21904 – DS_OMC_CIUS V15_01.BV .............................................30 3.3.1 CR fixed for GSM and GSM-R customers .................................................................30 Q01289182 : GSM:V15.1:DOC:DS/OMC/APP/013888 Add step for mirroring root disks viareboot ........................................................................................................................................... 30 Q01265544 : TMOCHIC:V15.1:Reconfigure Disaster Plan backup when cfInitOMCName ischanged ........................................................................................................................................ 32 Q01258365 : Disks array restoration failure ................................................................................34 Q01301782 : Procedure DS/OMC/APP/0017 should not contain script for MB-configuration. ... 36 Q01301200 : Login-step is missing at the document DS/OMC/APP/0017 .................................. 37 Q01308084 : Command should be added to list the content of the dat .......................................39 Q01308089 : Parameter 'spesificDay' is not needed for execution of the PCUOAM backup ...... 41 Q01310197 : Parameter 'spesificDay' is not needed for execution of the backup BDE ..............43 3.3.2 CR fixed only for GSM-R customers .........................................................................45 3.3.3 Regression Tests ........................................................................................................45

3.4. CORRECTIVE LOAD : AVL 23265 – PE_UPGPRECHECK V15_01.E0HD................................46 3.4.1 CR fixed for GSM and GSM-R customers .................................................................46 Q01245035 : TMOCHIC:V15.1: bad throughput for WS calculated by precheck tool ................. 46 Q01245035-03 : TMOCHIC:V15.1: bad throughput for WS calculated by precheck tool ............ 48 3.4.2 CR fixed only for GSM-R customers .........................................................................50 3.4.3 Regression Tests ........................................................................................................50

3.5. CORRECTIVE LOAD : AVL 23264 – PE_VERSUPGPRECHECK V15_01.EH9G......................51 3.5.1 CR fixed for GSM and GSM-R customers .................................................................51 Q01245035-02 : TMOCHIC:V15.1: bad throughput for WS calculated by precheck tool ............ 51

8/3/2019 pe-omc-app-018438_0112_en





Q01245035-04 : TMOCHIC:V15.1: bad throughput for WS calculated by precheck tool ............ 53 3.5.2 CR fixed only for GSM-R customers .........................................................................55 3.5.3 Regression Tests ........................................................................................................55

3.6. CORRECTIVE LOAD : AVL 22492 – PE_UPG_FW_T3 V02_00.E01 ......................................... 56 3.6.1 CR fixed for GSM and GSM-R customers .................................................................56 Q01202531-01 : HB_OMC:HD OMC-R Two T3 diskarray can not reachable throughethernet links ................................................................................................................................ 56 3.6.2 CR fixed only for GSM-R customers .........................................................................58 3.6.3 Regression Tests ........................................................................................................58

3.7. CORRECTIVE LOAD : AVL 21099 – PE_OSILOGD_PATCH V15_01.E01 ................................ 59 3.7.1 CR fixed for GSM and GSM-R customers .................................................................59 Q01103886-01 : BYTEL VO V15.1: osilogd core generated after restart of the SF880 ..............59 3.7.2 CR fixed only for GSM-R customers .........................................................................61 3.7.3 Regression Tests ........................................................................................................61

3.8. CORRECTIVE LOAD : AVL 23687 – PE_HSI-P V03_01.E00 .....................................................62 3.8.1 Features delivered for GSM and GSM-R customers ...............................................63 RFF 30156 – OMC-R Server RoHS Compliant ...........................................................................63

3.8.2 Features delivered only for GSM-R customers........................................................65 3.8.3 Regression Tests ........................................................................................................65

4. V15.1 CL2/V15.1R2 CL1 POST CHR CORRECTIONS HISTORY .............................................66 4.1. CORRECTIVE LOAD : AVL 25000 – OMC_APPLI V15_01.HR ..................................................66

4.1.1 CR fixed for GSM and GSM-R customers .................................................................66 Q01365703-04 : SUNDAY: Missing filed in CT2000 ....................................................................66 Q01355526-01 : PREINT153: Wrong TEI values for some BTS models. ...................................68 Q01328644-03 : CT2000: Incorrect TEI value in Internal View for some BTS models. .............. 70 Q01336165-01 : Some Outdoor BTS Models are declared as Indoor .........................................72 4.1.2 CR fixed only for GSM-R customers .........................................................................75 4.1.3 Features delivered for GSM and GSM-R customers ...............................................75 RFF 27899: BTS 18000 Dual Mode (BTS Combo) ......................................................................75 4.1.4 Features delivered only for GSM-R customers........................................................77 4.1.5 Regression Tests ........................................................................................................77

4.2. CORRECTIVE LOAD : AVL 24750 – PE_EMERGENCY_PATCH V15_01.E06 ......................... 78 4.2.1 CR fixed for GSM and GSM-R customers .................................................................78 Q01291382-01 : TMUK:GSM:OMC-R:V14.3.2: OMC-R Swap - Problem on PSUS -SFV880 ........................................................................................................................................ 78 Q01330639 : E3:GSM:OMC-R:V15_01.BR: Sybase not responding ..........................................80 4.2.2 CR fixed only for GSM-R customers .........................................................................82 4.2.3 Regression Tests ........................................................................................................82

4.3. CORRECTIVE LOAD : AVL 25129 – PE_EMERGENCY_PATCH V15_01.E07 ......................... 83 4.3.1 CR fixed for GSM and GSM-R customers .................................................................83 Q01387113-01 : OMCR1 server’s service LEDs are on ..............................................................83 4.3.2 CR fixed only for GSM-R customers .........................................................................85 4.3.3 Regression Tests ........................................................................................................85

5. V15.1R2 CL2 CONTENTS ........................................................................................................... 86 5.1. DEFINITION.............................................................................................................................86 5.2. CORRECTIVE LOAD : AVL 25757 – OMC_APPLI V15_01.IR ...................................................87

5.2.1 CR fixed for GSM and GSM-R customers .................................................................87 Q01408131 : OMC-R:BDA audit has to show all differences between BDE and BDA ................ 87 Q01423174 : OMC-R:BDA audit has to show all differences between BDE and BDA ................ 89 Q00863131-05 : Counter connectionDurationTcHCum (1600/0) ................................................92

5.2.2 CR fixed only for GSM-R customers .........................................................................94 5.2.3 Regression Tests ........................................................................................................94

8/3/2019 pe-omc-app-018438_0112_en





5.3. CORRECTIVE LOAD : AVL 24270 – PE_EMERGENCY_PATCH V15_01.E05 .................. 95 5.3.1 CR fixed for GSM and GSM-R customers .................................................................95 Q01338121-01 : Preventive Update of the Solaris patches for the Daylight Saving TimeChange ......................................................................................................................................... 95 Q01338136-01 : Preventive Update of the Solaris patch for QGE cards ....................................97 5.3.2 CR fixed only for GSM-R customers .........................................................................98 5.3.3 Regression Tests ........................................................................................................98

6. V15.1R2 CL2 POST CHR CORRECTIONS HISTORY ...............................................................99 6.1. CORRECTIVE LOAD : AVL 26237 – OMC_APPLI V15_01.JR ...................................................99

6.1.1 CR fixed for GSM and GSM-R customers .................................................................99 Q01479255-03 : OMC-R restarts after V16ChRCL2 patches application ................................... 99 6.1.2 CR fixed only for GSM-R customers .......................................................................101 6.1.3 Regression Tests ......................................................................................................101

6.2. CORRECTIVE LOAD: AVL 26597 – OMC_APPLI V15_01.KR .................................................101 6.2.1 CR fixed for GSM and GSM-R customers ...............................................................101 Q01542131-01: GSMR: BSS: Kein korrektes Abarbeitung von "Globel Commandfiles" ........101 Problem Description : .................................................................................................................101 6.2.2 CR fixed only for GSM-R customers .......................................................................103 6.2.3 Regression Tests ......................................................................................................103

6.3. CORRECTIVE LOAD: AVL 27450 – OMC_APPLI V15_01.LR .................................................103 6.3.1 CR fixed for GSM and GSM-R customers ...............................................................103 Q01681763-03: GSMR: BSS: V15.1R2: S8000 - O4 Configuration not possible ......................103 Problem Description : .................................................................................................................103 6.3.2 CR fixed only for GSM-R customers .......................................................................106 6.3.3 Regression Tests ......................................................................................................106

7. UPGRADE .................................................................................................................................107 7.1. CORRECTIVE LOAD : AVL 24032 – OMC_APPLI V15_01.FR .........................................107 7.2. CORRECTIVE LOAD : AVL 21904 – DS_OMC_CIUS V15_01.BV ....................................107 7.3. CORRECTIVE LOAD : AVL 23265 – PE_UPGPRECHECK V15_01.E0HD.......................107 7.4. CORRECTIVE LOAD : AVL 23264 – PE_VERSUPGPRECHECK V15_01.EH9G ............107 7.5. CORRECTIVE LOAD : AVL 22492 – PE_UPG_FW_T3 V02_00.E01 ................................107 7.6. CORRECTIVE LOAD : AVL 21099 – PE_OSILOGD_PATCH V15_01.E01 .......................107 7.7. CORRECTIVE LOAD : AVL 23687 – PE_HSI-P V03_01.E00 ............................................107 7.8. CORRECTIVE LOAD : AVL 25000 – OMC_APPLI V15_01.HR .........................................108 7.9.

CORRECTIVE LOAD : AVL 24750 – PE_EMERGENCY_PATCH V15_01.E06 ................108

7.10. CORRECTIVE LOAD : AVL 25129 – PE_EMERGENCY_PATCH V15_01.E07 ................108 7.11. CORRECTIVE LOAD : AVL 25757 – OMC_APPLI V15_01.IR ...........................................108 7.12. CORRECTIVE LOAD : AVL 24270 – PE_EMERGENCY_PATCH V15_01.E05 ................108 7.13. CORRECTIVE LOAD : AVL 26237 – OMC_APPLI V15_01.JR ..........................................108 7.14. CORRECTIVE LOAD: AVL 26597 – OMC_APPLI V15_01.KR ..........................................108 7.15. CORRECTIVE LOAD: AVL 26597 – OMC_APPLI V15_01.KR ..........................................108

8. KNOWN ISSUES .......................................................................................................................109 Q01341049 : ID: gzip has wrong rights ......................................................................................109 Q01416533 : During patch avl24750&avl24826 application, abnormal message occured .......110

8/3/2019 pe-omc-app-018438_0112_en





9. ON-SITE SOAK PERIOD RESULTS.........................................................................................111 9.1. FIXES OF V15.1 CL2 LOAD....................................................................................................111 9.2. CORRECTIVE LOAD : AVL 25129 – PE_EMERGENCY_PATCH V15_01.E07 ................112 9.3.

F

IXES OFV15.1R2

CL1

LOAD...............................................................................................113

10. ABBREVIATIONS AND DEFINITIONS .....................................................................................116

10.1. ABBREVIATIONS ....................................................................................................................116 10.2. DEFINITIONS .........................................................................................................................116

11. ANNEXES ..................................................................................................................................117 ANNEX A: V15.1 POST-CHR PRODUCT VERSIONS ...........................................................................117

A.1 Initial delivery for GSM ....................................................................................................117 A.2 Initial delivery for GSM-R ................................................................................................117 A.3 Delivery for V15.1 CL2 / V15.1R2 CL1 ...........................................................................118 A.4 Patch history for V15.1 CL2 / V15.1R2 CL1 ...................................................................118 A.5 Delivery for V15.1R2 CL2 ...............................................................................................119 A.6 Patch history for V15.1R2 CL2 .......................................................................................119

ANNEX B: V15.1 POST-CHR CR – CUSTOMER CASE MATRIX...........................................................120

8/3/2019 pe-omc-app-018438_0112_en





1. INTRODUCTION

1.1. OBJECT

This document describes OMC-R fixes: fault description, fix, tests,installation/upgrade paths and product versions.Unless explicit remark, each delivery includes fixes added to thecontent of the previous one.

1.2. SCOPE OF THIS DOCUMENT

Scope of the present document is:

• V15.1 PostChR, applicable for all GSM and GSM-R customers.

• V15.1R2 PostChR, applicable only for GSM-R customers

1.3. AUDIENCE FOR THIS DOCUMENT

All people concerned with V15.1/V15.1R2 PostChR OMC-RSoftware.

2. RELATED DOCUMENTS

2.1. APPLICABLE DOCUMENTS

[A1] PE/OMC/APP/016762 V15.1 Post ChR OMC-R fixes

[A2] PE/OMC/APP/016384 V15.1R2 ChR OMC-R fixes

2.2. REFERENCE DOCUMENTS

[R1] PE/BSS/APP/000109 Patch and plug-in installation guide

8/3/2019 pe-omc-app-018438_0112_en





3. V15.1 CL2 / V15.1R2 CL1 CONTENTS

3.1. DEFINITION

This OMC-R software version is known as:

• V15.1 CL2 for GSM customer,

• V15.1R2 CL1 for GSM-R customers,

and is defined by:

- contents of last CL applied on previous V15.1 version

V15.1 Post ChR OMC-R fixes [A1];

- new fixes GSM and GSM-R detailed in this chapter.

Corresponding loads are defined in chapter:

ANNEX A: V15.1 Post-ChR Product Versions

(V15.1 CL2/V15.1R2 CL1 delivery).

8/3/2019 pe-omc-app-018438_0112_en





3.2. CORRECTIVE LOAD : AVL 24032 – OMC_APPLIV15_01.FR

3.2.1 CR FIXED FOR GSM AND GSM-R CUSTOMERS

Q01245876-01 : TMOCHIC:V15.1: CT/CPT INSERT RECORD WASFAILED TO TRACE_DB DATABASE

Problem Description :

If insertion of CT/CPT data into database fails because of fault of Sybaseserver, corresponding message explaining the error is printed to diagnosticfile and an internal flag is raised denoting that the database is locked.When this flag is raised, all subsequent trace files coming for processingare rejected without even making an attempt to insert them to thedatabase, and an error message is printed to the diagnostic files. Thiserror message contains no useful information, but it is repeated every timea CT/CPT file arrives, which can happen several times per second on areally loaded OMC-R. Therefore, diagnostic file quickly becomes filled upwith such messages, and the error message for initial problem which led tothe internal lock flag being raised is scrolled out (because diagnostic file iscircular).So lots of useless messages printed to diagnostics will hide the originalerror message, which could be needed to clarify the actual initial problem.

Another trouble is that currently restart of the OMC-R is mandatory torestore normal insertion of CT/CPT data in the database in such cases asdescribed above. Because single failure blocks all subsequent insertionsin the database. Although, in some certain situations it could be possible tocontinue working with Sybase even without restart (for example, if database is saturated, then defense purge can free some space in it, andthen normal operation could be resumed).

Impact:

If an error occurs during insertion of CT/CPT data into Sybase, then theroot cause cannot be investigated (no information about the reasons of

failure available in diagnostics); no subsequent CT/CPT data insertions inthe database possible, and OMC-R restart is mandatory to restore normaloperation.

Occurrence: Reproducible

Workaround: Restart of the OMC-R is necessary to restore normal operation.

8/3/2019 pe-omc-app-018438_0112_en





Fix:Modifications were introduced to change the behavior in the following way:error message for rejected CT/CPT data files mentioned above is printedto the diagnostic file only once, but not every time a data file is rejected.

A timeout was introduced (30 minutes after internal lock flag has beenraised), upon which the lock flag is cleared and insertion of CT/CPT data isre-enabled.

Modified files: /OMC/base/exe/pm_cpu_trace.x

Fix verification:

The fix can be tested only by Nortel R&D

The fix can also be tested on Customer side following the test description

Test configuration:

System Test SubSystem Test

Tests:Test Description: 1) Simulate Sybase error in order to test this fix.2) Generate call trace data:

chrserv03:/MD/base/debug/pm <50> (omc) % SIMU_TRACE.x 89 15 -

LogId 6 -CTRACE -PRIO -amrFR -btsV15 -maxField -Day 0and check that insertion of CT data to database has failed.

3) Generate call trace data:chrserv03:/MD/base/debug/pm <50> (omc) % SIMU_TRACE.x 89 15 -LogId 6 -CTRACE -PRIO -amrFR -btsV15 -maxField -Day 0and check /OMC/diagnostic/diag_pmcputra.

4) Restore normal functioning of the database.5) Check /OMC/diagnostic/diag_pmcputra after 30 min.6) Check that generated CT data appeared in the database within 5

minutes after timeout was finished

Test Result: 1) OK. Actions to simulate Sybase error were performed.2) OK. Insertion of CT data to database has failed.

/OMC/diagnostic/diag_pmcputra:

Applicative mirroring OFF.NORMAL initialisation of PM_CPU_TRACE taskVERSION:V14_00.00

Tue Feb 7 10:51:15 2006 Performance management(source:pmos_dbop.c - line:3938) Thread Number : 56Pb to bcp_init on TCLmeasureRp_06_20060207

8/3/2019 pe-omc-app-018438_0112_en





Tue Feb 7 10:51:15 2006 Performance management(source:pmos_dbop.c - line:4045) Thread Number : 56CUR server disabled

Tue Feb 7 10:51:15 2006 Performance management(source:pmos_dbop.c - line:1520) Thread Number : 1Pb on insertion trace at Tue Feb 7 10:51:15 2006

3) OK. Expected results are present in diagnostic file/OMC/diagnostic/diag_pmcputra:

Tue Feb 7 10:52:42 2006 Performance management(source:pmos_cputrace_msg.c - line:562) Thread Number : 1trace_db is locked, 30 min timer activated, timer id: 326

4) OK. Normal functioning of the database is restored.5) OK. Expected results are present in diagnostic file

/OMC/diagnostic/diag_pmcputra:

Tue Feb 7 11:25:47 2006 Performance management(source:pmos_cputrace_msg.c - line:488) Thread Number : 1trace_db is unlocked, the timer is deactivated, timer id: 326

6) OK. All generated CT data appeared in the database within 5 minutesafter timeout was finished.

8/3/2019 pe-omc-app-018438_0112_en





Q01252014 : TMOBELV:V15.1: WHEN CF_SAVE_TOOL.X ISSTUCK, THE MMI IS NOT FUNCTIONAL

Problem Description :During BDE backup operation the following mechanism is used: after operation has been started intended tool sends lock requests to COMtasks, and waits for responses before performing BDE backup itself. After reception of acknowledgements from all concerned COM tasks operationis continued: BDE dumping and archiving is performed. When alloperations which require BDE locked are finished unlock requests are sentto the same COM tasks.But if no lock response received from one of these COM tasks, theprocess is stuck. There is no possibility to interrupt BDE backup operationin such case. And since COM tasks have received the lock request but

haven’t received the unlock request after, any actions on BDE performedvia MMI are prohibited and a message saying that the BDE backup isrunning is displayed.

Impact:

No operations can be performed via MMI. Backup cannot be cancelled.

Occurrence: Rare – difficult to reproduce.

Workaround: The problem can be solved by OMC-R restart.

Fix:Modifications in the cf_save_mgr.x were made in order to activate a newtimer before sending a lock request to each of COM tasks and delete itafter each successful reception of acknowledgement. If during 40 minutesfrom the timer activation no acknowledgement is received – the backupoperation is canceled.

Modified files:

/OMC/base/exe/cf_save_mgr.x

Fix verification:



Test configuration:


8/3/2019 pe-omc-app-018438_0112_en





Tests:Test Description: OMC-R is operational.1) Configure com-tasks to work in a non-nominal way (to make them not

to send responses to lock requests).2) Launch /CMN/base/exe/cf_save_tool.x -o archive -y backup -l label143) Wait 40 min and see backup results.

Test Result: 1) OK. com-tasks are configured.2) OK. The backup of the BDE is launched.3) OK. After 40 min backup exits with NOK-status:- 16:03:23 OMC backup/restore : - Lock com omnet has been canceled.- 16:03:26 OMC backup/restore : >> Backup failed !!, error 1

8/3/2019 pe-omc-app-018438_0112_en





Q01252014-03 : TMOBELV:V15.1: WHEN CF_SAVE_TOOL.X ISSTUCK, THE MMI IS NOT FUNCTIONAL

Problem Description :During BDE backup operation the following mechanism is used: after operation has been started intended tool sends lock requests to COMtasks, and waits for responses before performing BDE backup itself. After reception of acknowledgements from all concerned COM tasks operationis continued: BDE dumping and archiving is performed. When alloperations which require BDE locked are finished unlock requests are sentto the same COM tasks.But if no lock response received from one of these COM tasks, theprocess is stuck. There is no possibility to interrupt BDE backup operationin such case. And since COM tasks have received the lock request but

haven’t received the unlock request after, any actions on BDE performedvia MMI are prohibited and a message saying that the BDE backup isrunning is displayed.

Impact:

No operations can be performed via MMI. Backup cannot be cancelled.

Occurrence: Rare – difficult to reproduce.

Workaround: The problem can be solved by OMC-R restart.

Fix:A new alarm was added (notification with codano 32100“ARCHIVE/RESTORE PROBLEM” was introduced, cause 32101 "Answer for lock request was not received from COM task" was defined). It is raisedif an answer from a concerned COM task is not received in time andcleared if BDE backup ends successfully. In other cases alarm must becleared manually.

Modified files: /OMC/base/config/locale/en/MmiCodano.cfg/OMC/base/config/locale/en/MmiCause.cfg/CMN/base/config/fm_alaSem.cfg

Fix verification:



8/3/2019 pe-omc-app-018438_0112_en





Test configuration:


Tests:Test Description: OMC-R is operational. Notification Monitor is opened.1) Configure com-tasks to work in a non-nominal way (to make them not

to send responses to lock requests).2) Launch /CMN/base/exe/cf_save_tool.x -o archive -y backup -l label143) Check Notification Monitor.4) Wait 40 minutes.

Test Result:

1) OK. com-tasks are configured.2) OK. The backup of the BDE is launched.3) OK. Expected notification is present in the Notification Monitor:

**** Notification : 641281 *********** SEVERITY : major ******************occurred on 02/03/06 10:49:14 received on 02/03/06 10:49:14Type : processingErrorAlarmInstance : omcDescription : omcTaskId : 1420- Information on fault -------------------------

Probable cause : (46) softwareError Fault number : (32100) “ARCHIVE/RESTORE PROBLEM”Source : (32101) Answer for lock request was

not received from COM task**************************************************************************4) OK. After 40 minutes backup exits with NOK-status.

8/3/2019 pe-omc-app-018438_0112_en





Q01252718 : TMOCHIC:V15.1: SYSTEM() USED INMULTITHREAD TASKS IS UNSTABLE.

Problem Description :system() function call is not safe when used in multithread applications.Since all tasks/tools providing backup/restore of OMC-R data aremultithread (execution of an operation is done in a separate thread) use of system() function in them should be avoided.

Impact:

Backup/restore of OMC-R data can hang and block execution of other operations in MMI.

Occurrence: Intermittent

Workaround: Only OMC-R restart can solve the problem.

Fix:A new function which uses multithread-safe commands was implementedin the library intended for OMC-R backup/restore tasks/tools.

Modified files:

/CMN/base/exe/cf_save_tool.x/OMC/base/exe/cf_backupPCUOAM_mgr.x/OMC/base/exe/cf_save_mgr.x/MD/base/exe/cf_save_md.x

Fix verification:



Test configuration:


Tests:Test Description: 1) Backup/Restore BDE on/from file system and on/from DAT.2) Backup/Restore Daily Data on/from file system and on/from DAT.3) Backup/Restore PCUOAM data on/from file system and on/from DAT.

Test Result:

1) OK. Backup/Restore BDE successfully completed.2) OK. Backup/Restore Daily Data successfully completed.

8/3/2019 pe-omc-app-018438_0112_en





3) OK. Backup/Restore PCUOAM data successfully completed.

8/3/2019 pe-omc-app-018438_0112_en





Q01280824-01 : PREINT160: CONFIGREF M/N13: INCORRECTBTS CONFIGURATION

Problem Description :Six models are not recognized by Sdo2CT plug-in:M13_S18181_2644M13_S18182_2644M13_S18183_2644N13_S18181_2644N13_S18182_2644N13_S18183_2644The TEI distribution for these models is incorrect.

Impact:

Six models have incorrect TEI distribution (between cells). The user is notable to create the correct models. These models will not be recognized bySdo2CT plug-in.

Occurrence: Reproducible.

Workaround: Use M/N13 S181818 (with 0 TRX in the third sector) instead of M/N13S1818.

Fix:Two-sectorial M/N13 were deleted from the models list. Instead of themuser should use tri-sectorial M/N13 S181818. Necessary modificationswere done in Sdo2CT plug-in.

Modified files: /CMN/base/plugins/Sdo2CT/plugin.cfg/CMN/base/plugins/Sdo2CT/DrfInputModel/models.cts

Fix verification:



Test configuration:


Tests:Test Description:

CT2000 - OMC-R - CT2000 loop was performed for the following models:M13_S1818181_2644

8/3/2019 pe-omc-app-018438_0112_en





M13_S1818182_2644M13_S1818183_2644N13_S1818181_2644N13_S1818182_2644

N13_S1818183_2644(bts configurations with 0 TRXs in the third sector)

Test Result: All tested models have been recognized correctly after CT2000 - OMC-R -CT2000 loop. All the concerned models have the right TEI distribution.

8/3/2019 pe-omc-app-018438_0112_en





Q01243900-03 : GSM : V15.0.1 : OSK : CONFIGREF M/N24MISSING IN CT2K

Problem Description :CT2000 internal tables do not contain the description of the dual-bandmodels with DLU M24/N24.The earlier implementation was done according to documentation whichcontained only the mono-band configurations with DLU M24/N24 and noinformation were present about the dual-band. The new specificationdocument contains such information.

Impact:

The user can not create some BTS configurations using CT2000. They

are: bi- and tri- dual band configurations RM with DDM H2 and TXF H2with DLU M24/N24.


Workaround: It is possible to use M21/N21 instead of M24/N24.NOTE: in M/N21 the S111 RM modules are in the shelf one and the O3RM modules in the shelf two and for the M/N24 it’s the opposite, O3 inshelf one and S111 in shelf two.

None: For other missed configurations.

Fix:The missed configurations were included in Sdo2CT plug-in.


Fix verification:

The fix can be tested only by Nortel R&DThe fix can also be tested on Customer side following the test description

Test configuration:


Tests:Test Description: CT2000 - OMC-R - CT2000 loop was performed for the concerned

models.

8/3/2019 pe-omc-app-018438_0112_en





Test Result: M/N24 models requested by customer are available in CT2000. NewBTS18000 configurations have been recognized correctly after loopCT2000 - OMC-R - CT2000.

8/3/2019 pe-omc-app-018438_0112_en





Q01287440 : CM:VARIANCE BETWEEN DOCUMENTATION ANDOMC-R BEHAVIOR

Problem Description :While creating BTS18000 with maximum number of TRXes under BSC2G,the creation process has failed because the rule 203CO02 was broken:when related to a 'transceiverEquipment' object instance, the attribute 'tei'is located between 14 and 55 for a s12000 bts, between 14 and 79 (3G);14 and 65 (2G) for a BTS18000 bts and between 16 and 63 for the others.There is the assertion in PE/MD/DD/0008 V13.02/EN: ‘203CO02 - Whenrelated to a'transceiverEquipment' object instance, the attribute 'tei' is locatedbetween 14 and 55 for a s12000 bts, between 14 and 79 for a BTS18000bts and between 16 and 63 for the others.’

Corresponding check implemented in OMC-R is correct, but thedocumentation is not consistent. There is inconsistency betweendocument and OMC-R behavior.

Impact:

Inconsistency between document and OMC-R behavior is present.Operator can meet problems during objects creation following thedocumentation.

Occurrence:

Reproducible.

Workaround: None.

Fix:The document PE/MD/DD/0008 V13.03/EN was updated, description for the concerned semantic check was corrected to correspond to OMC-Rbehavior.

Modified documents:

PE/MD/DD/0008 V13.03/EN

Fix verification:



Test configuration:


8/3/2019 pe-omc-app-018438_0112_en





Tests:Test Description: Procedure: PE/MD/DD/0008 V13.03/EN

Open PE/MD/DD/0008 V13.03/EN document on the page 448 and makesure that there is an assertion:"203CO02 - When related to a 'transceiverEquipment' object instance, theattribute 'tei' is located between 14 and 55 for a s12000 bts, between 14and 79 (3G); 14 and 65 (2G) for a BTS18000 bts and between 16 and 63for the others."

Test Result: OK. The documentation is consistent.

8/3/2019 pe-omc-app-018438_0112_en





Q01135458-01 : PREINT 154: CFG CREATES INCORRECTCOMMAND FILES

Problem Description :In create mode, CmdFilegeneration plugin reverses file for TCU creation, if destination path contains "del" substring.

Impact:

It’s not possible to perform generated command files if result directoryname contains substring “del”.


Workaround: Do not use name of result directory that contains substring “del”.

Fix:CmdFilegeneration plugin was modified. The condition to reverse a filewas changed: regular expression which is matched with result commandfile directory was corrected.

Modified files: /CMN/base/plugins/CmdFileGeneration/plugin.cfg

/CMN/base/plugins/CmdFileGeneration/CmdFileGeneration.x

Fix verification:



Test configuration:


Tests:Test Description: Launch CmdFileGeneration plugin on SDO set in create mode. As a resultdirectory, specify name that contains “del” as substring. Check thatgenerated command file for tcu creation isn't reversed.

Test Result: OK. The plugin’s behavior is as expected: generated command file is notreversed.

8/3/2019 pe-omc-app-018438_0112_en





Q01186607-02 : CYCLIC OMC-R RESTART


During network instability the task com_scse.x is blocked and unable toprocess surveillance messages from OMC-R, thus it leads to OMC-Rrestart. Blocking is caused by current mechanism of receiving data fromBSC: while getting packets of the same datagram from BSC, com_scse.xwill not process the data and will not stop waiting for the next subsequentpackets until the last packet of the datagram is received. In case of network instability the last packet of datagram can be lost or delayed for along time. During this time com_scse.x is stuck.

Impact:

com_scse.x task is blocked and unable to process surveillance messagesfrom OMC-R. This leads to OMC-R restart.

Occurrence: Intermittent

Workaround: Eliminate the network instability.

Fix:New algorithm of data receiving was introduced: the task com_scse.x first

checks for the data availability, then appends received packet to databuffer where the whole datagram from BSC is being collected. The datafrom the buffer will be processed if the last packet of the datagram isreceived, then the buffer will be flushed. If disconnection happens anddetected, then all not completed datagrams are flushed. In suchimplementation com_scse.x is not blocked while receiving subsequentpackets of the same datagram, thus in case of network instability it will notbe stuck.

Modified files: /MD/base/exe/com_scse.x

Fix verification:



Test configuration:


Tests: Test Description:

8/3/2019 pe-omc-app-018438_0112_en





The following tests were executed with bsc e3 V15 and bsc 2g V15.

Test 1:1) Perform the Online Reset on BSC.

2) Perform the BuildBDA.3) Verify that OMC-R is not restarted.

Test 2:1) Create command file to perform Get/Set/Delete/Display operations on

different objects of BSS and Audit BDA on BSC.2) Perform the following actions in parallel:

- download the new BSC, BTS, TRX and TCU software on BSC;

- execute the created command file.3) Verify that the OMC-R is not restarted.

Test 3:1) Perform the Online Reset on BSC.2) Perform the BuildBDA, during this operation disconnect/connect the

OMN link from BSC side several times.3) Verify that OMC-R is not restarted.

Test 4:1) Create command file to perform Get/Set/Delete/Display operations on

different objects of BSS and Audit BDA on BSC.2) Perform the following actions in parallel and also during these

operations disconnect/connect OMN link from BSC side several times.

- download the new BSC, BTS, TRX and TCU software on BSC;

- execute the created command file.3) Verify that the OMC-R is not restarted.

Test Result: Test 1:1) OK.2) OK.3) OK. OMC-R is not restarted.

Test 2:1) OK.2) OK.3) OK. OMC-R is not restarted.

Test 3:1) OK.2) OK.3) OK. OMC-R is not restarted.

Test 4:

1) OK.2) OK.

8/3/2019 pe-omc-app-018438_0112_en





3) OK. OMC-R is not restarted.

8/3/2019 pe-omc-app-018438_0112_en





3.2.2 CR FIXED ONLY FOR GSM-R CUSTOMERS

None.

3.2.3 REGRESSION TESTS

Regression Tests performed:

• Backup/Restoration tests

Upgrade Tests performed:

Unless explicit remark, upgrade is done by patch installation/application

with install_data tool.

Nominal patch installation/application with install_data tool was performed.

See chapter 7 UPGRADE for details.

Soak Tests performed:

None.

8/3/2019 pe-omc-app-018438_0112_en





3.3. CORRECTIVE LOAD : AVL 21904 – DS_OMC_CIUSV15_01.BV


Q01289182 : GSM:V15.1:DOC:DS/OMC/APP/013888 ADD STEPFOR MIRRORING ROOT DISKS VIA REBOOT


During SF global restoration, after Disk array restoration, script ends withthe message: "Reboot the server to take into account mirroring of bootdisk". But in this particular case there is no need to reboot the server, asreboot will be performed several steps later according to thedocumentation. However, the message can confuse operator.

Impact:

None, even if operator decides to reboot the server at this time, therestoration procedure can be continued after it.


Workaround:

To ignore this message. Even if reboot has been performed it will notimpact anything, restoration procedure could be continued.

Fix:DS/OMC/APP/000044, DS/OMC/APP 013888: sheet "DISKS ARRAYRESTORATION" - in the sample of script’s output the string which asks for reboot was added, a note was inserted that reboot is not needed here.

Modified documents: DS/OMC/APP/000044 V04.09/ENDS/OMC/APP/013888 V01.12/EN

Fix verification:



Test configuration:


8/3/2019 pe-omc-app-018438_0112_en





Tests:Test Description: DS/OMC/APP/000044 V04.09/ENDS/OMC/APP/013888 V01.12/EN

Validate the procedures (step S7 in chapter 6.2.2 - DISKS ARRAY ANDENVIRONMENT DATA RESTORATION).

Test Result: OK. There is a note claiming to ignore request for server reboot after executing ds_restore_MB.sh (step S7).

8/3/2019 pe-omc-app-018438_0112_en





Q01265544 : TMOCHIC:V15.1:RECONFIGURE DISASTER PLANBACKUP WHEN CFINITOMCNAME IS CHANGED

Problem Description :1) After cfInitOMCName had been changed for the server, the nextdisaster plan automatic daily backup was failed. The reason for the failureis the absent signature file on the defined NFS path, which wasconsequently changed after modification of cfInitOMCName parameter.Automatic backup process should be reconfigured after changingcfInitOMCName, but this is not descried in the corresponding procedureDS/OMC/APP/08020.

2) During configuration of the disaster plan procedure according to thedocument DS/OMC/APP/08020 OMC-R application is stopped on all the

machines on step S5, but there is no step in the document asking torestart OMC-R application after configuration has been performed.

Impact:

Auto backup failed, operator should reconfigure automatic backupprocess, and start OMC-R.


Workaround: 1) After changing cfInitOMCName in omc_configure.cfg (note: the value of his parameter should be unique!) operator has to perform the followingsteps of DS/OMC/APP/08020 procedure:S3 Ensure that the OMC-R can access NFS server shared directoryS5 Stop the OMC-R application on all OMC-R machinesS6 Configure the OMC-R application on OMC-R machinesS9 Configure the system to perform automatic daily backup

2) Start OMC-R application on all the machines after configuration of thedisaster plan procedure has been performed.

Fix:1) A note describing which steps to perform in case of changingcfInitOMCName and in case if it is needed to change only the executiontime was added to the document DS/OMC/APP/08020.

2) Step of starting OMC-R was added to the chapter 6 “Configuration” of DS/OMC/APP/08020 procedure.

Modified documents: DS/OMC/APP/008020 V04.05/EN

8/3/2019 pe-omc-app-018438_0112_en





Fix verification:



Test configuration:


Tests:Test Description: Procedure DS/OMC/APP/008020 V04.05/EN

1) S2 - Change cfInitOMCName.

2) S3 - Ensure that the OMC-R can access NFS server shared directory.3) S4 - Specify backup server on the OMC-R server.4) S5 - Stop the OMC-R application on the OMC-R server.5) S6 - Configure the OMC-R application on OMC-R server.6) S7 - Start the OMC-R application on OMC-R server.7) S9 - Configure the system to perform automatic daily backup.

Test Result: 1) OK. OMC-R has a new name.2) OK. NFS directory is accessible.3) OK. Backup server is specified.

4) OK. The OMC-R is stopped on the OMC-R server.5) OK. The OMC-R software configuration is complete.6) OK. OMC-R is running on the OMC-R server.7) OK. The system is configured to perform automatic daily backup for

disaster plan.Automatic backup successfully works.

8/3/2019 pe-omc-app-018438_0112_en





Q01258365 : DISKS ARRAY RESTORATION FAILURE


System global restoration operation fails on disk array restoration step: atthis time it is supposed that there is no DISKSET defined, although itexists.The file mddb.cf contains information about SDS database replicalocations and must be cleared after "system" restoration step before thereboot. But it is not deleted, because script incorrectly determines itslocation: the location is determined by having a look at Solaris version,which is not correct, as machine could be booted from not nominal for thishardware Solaris CD-ROM and there is no note in the documentationwhich version of Solaris CD-ROM should be used for booting.The following nominal cases for file system restoration are supposed:

E4XXX – boot from CD-ROM Solaris 2.6 (in the documentDS/OMC/APP/000017 there is no information about Solaris version)SFV880 – boot from CD-ROM Solaris 8 02/02 (in the documentDS/OMC/APP/000044 Solaris version is defined)SFV890 – boot from CD-ROM Solaris 8 02/04 (in the documentDS/OMC/APP/013888 Solaris version is defined)So, only document DS/OMC/APP/000017 does not mention which versionof Solaris CD-ROM to boot from.

Impact:

In case an operator uses CD-ROM Solaris 8 for E4XXX (instead of Solaris2.6): it’s not possible to perform disks array restoration without theworkaround.


Workaround: 1) Clear metadevices, metaset. On the active server, under croot login:# metaclear -sDISKSET1 -a -f # metaset -s DISKSET1 -d -f -h <active_server_hostname>

# metaset -s DISKSET1 -d -f -h <passive_server_hostname>2) Retry the action. Under croot login:# /usr/local/oam/bin/ds_restore.sh -Y -MdisksArrayDb

Fix:Version of Solaris CD-ROM which should be used for booting was addedinto the DS/OMC/APP/000017 document. Mentioned that for server andstation different Solaris CD-ROMs should be used.


8/3/2019 pe-omc-app-018438_0112_en





Fix verification:



Test configuration:


Tests:Test Description: Procedure: DS/OMC/APP/000017 V09.09/EN

Backups of the file system for the server and for the station are available

at the DATs.1) Perform File System restoration of the server using procedureDS/OMC/APP/0017 V09.09 (S9 at p. 17).

2) Perform File System restoration of the workstation using procedureDS/OMC/APP/0017 V09.09 (S41 at p. 21).

Test Result: 1) OK. The reboot of the server from CD-ROM with Solaris 2.6 is OK (at

the S9). File system restoration is OK.2) OK. The reboot of the station from CD-ROM with Solaris 8 is OK (at

the S41). File system restoration is OK.

8/3/2019 pe-omc-app-018438_0112_en





Q01301782 : PROCEDURE DS/OMC/APP/0017 SHOULD NOTCONTAIN SCRIPT FOR MB-CONFIGURATION.

Problem Description :Procedure DS/OMC/APP/0017 “OMC-R system global restoration”intended for standard configuration at sheet "End Restoration" mentions touse “MB" script (designed for MONOBOX configuration)/usr/local/oam/bin/ds_restoreMaj_MB.sh, that is not correct.

Impact:

Wrong script could be used because of documentation mistake.

Occurrence:

Reproducible

Workaround: To use /usr/local/oam/bin/ds_restoreMaj.sh script instead of /usr/local/oam/bin/ds_restoreMaj_MB.sh on this step.

Fix:Mentioned script was changed to "non-MB" one.


Fix verification:



Test configuration:


Tests: Test Description: Procedure: DS/OMC/APP/000017 V09.09/EN

Backup of the server’s disk array device is available on the DAT.Perform disk array device restoration for the standard configuration usingthe procedure DS/OMC/APP/0017 V09.09

Test Result: OK. According to the procedure, at the step S17 script/usr/local/oam/bin/ds_restoreMaj.sh was launched.

The disk array device restoration was successfully completed.

8/3/2019 pe-omc-app-018438_0112_en





Q01301200 : LOGIN-STEP IS MISSING AT THE DOCUMENTDS/OMC/APP/0017

Problem Description :During the file system restoration performed according to the documentDS/OMC/APP/0017 “OMC-R system global restoration”, after step S9,operator should login to the system. This step is not described in thedocumentation.

Impact:

Operator could be confused, as action that should be performed is notmentioned in the documentation.


Workaround: To login to the system at this step and to continue operations according tothe documentation.

Fix:A step was added to DS/OMC/APP/0017 procedure to perform login to thesystem.


Fix verification:



Test configuration:


Tests:Test Description: Procedure: DS/OMC/APP/000017 V09.09/EN

Backup of the server’s file system is available on the DAT.Perform server file system restoration using procedureDS/OMC/APP/0017 V09.09.

8/3/2019 pe-omc-app-018438_0112_en





Test Result: OK. After execution of the S9 the system demanded that the operator enter login and password (to login to the operating system). The procedurecontains S10 describing how user can login to the operating system.

The server file system restoration finished successfully.

8/3/2019 pe-omc-app-018438_0112_en





Q01308084 : COMMAND SHOULD BE ADDED TO LIST THECONTENT OF THE DAT

Problem Description :Procedure DS/OMC/APP/0016 “OMC-R preventive maintenance backup”,MDM configuration backup: tar command which is proposed to belaunched on the sheet “PCUOAM CONFIGURATIONBACKUP/RESTORING VIA COMMAND LINE” to list data contained onthe DAT after backup is not efficient, as the tape is not rewound. The tapeshould be rewound first.

Impact:

The result of the proposed command could be not informative.


Workaround: Rewind the tape with the command "mt -f /dev/rmt/0n rewind", beforeexecuting the proposed tar command.

Fix:Documentation was updated: before execution of tar command, command“mt -f /dev/rmt/0n rewind” was added.

Modified documents: DS/OMC/APP/000016 V09.07/ENDS/OMC/APP/000043 V04.07/ENDS/OMC/APP/013888 V01.12/EN

Fix verification:



Test configuration:


Tests:Test Description: Procedures: DS/OMC/APP/000016 V09.07/EN

DS/OMC/APP/000043 V04.07/ENDS/OMC/APP/013888 V01.12/EN

Validate the updated documentation.

8/3/2019 pe-omc-app-018438_0112_en





Test Result: OK. Mentioned command has been added. The documentation isconsistent.

8/3/2019 pe-omc-app-018438_0112_en





Q01308089 : PARAMETER 'SPESIFICDAY' IS NOT NEEDED FOREXECUTION OF THE PCUOAM BACKUP

Problem Description :During PCUOAM backup there is no need to define the parameter 'spesificDay' as the backup is performed for the current day anyway,although this parameter is mentioned in the documentation as required.

Impact:

There is no actual impact, if the parameter is specified in the commandline it will not affect anything.

Occurrence:

Reproducible

Workaround: No need, as there is no actual impact.

Fix:The documentation was updated: mentioned that 'spesificDay' is notneeded for PCUOAM backup. Parameter was removed from theconcerned step.

Modified documents:

DS/OMC/APP/000016 V09.07/ENDS/OMC/APP/000043 V04.07/ENDS/OMC/APP/013888 V01.12/EN

Fix verification:



Test configuration:





8/3/2019 pe-omc-app-018438_0112_en





Test Result: OK. Mentioned parameter has been removed from concerned step. Thedocumentation is consistent.

8/3/2019 pe-omc-app-018438_0112_en





Q01310197 : PARAMETER 'SPESIFICDAY' IS NOT NEEDED FOREXECUTION OF THE BACKUP BDE

Problem Description :During OMC-R Environment Data (BDE) backup there is no need to definethe parameter 'spesificDay' as the backup is performed for the current dayanyway, although this parameter is mentioned in the documentation asrequired.

Impact:

There is no actual impact, if the parameter is specified in the commandline it will not affect anything.


Workaround: No need, as there is no actual impact.

Fix:The documentation was updated: parameter 'spesificDay' was removedfrom the concerned step and sheet.

Modified documents:

DS/OMC/APP/000016 V09.07/ENDS/OMC/APP/000043 V04.07/ENDS/OMC/APP/013888 V01.12/EN

Fix verification:



Test configuration:





8/3/2019 pe-omc-app-018438_0112_en





Test Result: OK. Mentioned parameter has been removed from concerned step andsheet. The documentation is consistent.

8/3/2019 pe-omc-app-018438_0112_en






None.



None.






None.

8/3/2019 pe-omc-app-018438_0112_en





3.4. CORRECTIVE LOAD : AVL 23265 – PE_UPGPRECHECKV15_01.E0HD


Q01245035 : TMOCHIC:V15.1: BAD THROUGHPUT FOR WSCALCULATED BY PRECHECK TOOL


Throughput measurement precheck step of Version/Hardware UpgradePrechecks tools shows incorrect information for the station. It shows thevery low throughput although it is not the case. Network throughput valueis calculated in the wrong way for workstation. This is because of wrongpacket size for ping command, which is used for calculation of thethroughput value.

Impact:

Throughput value measured for WS is not correct.


Workaround:

None.

Fix:Hardware Upgrade Prechecks tool was modified: for both server andstation the packet size for the ping command (which is used for calculationof the throughput value) was taken with value 30000 bytes. So thethroughput value obtained will be the correct one.

Modified files: /home/CIUS/gui/precheck/pre-checks.tcl/home/CIUS/gui/precheck/precheck_lib.tcl

Fix verification:



Test configuration:


8/3/2019 pe-omc-app-018438_0112_en





Tests:Test Description: Hardware Upgrade Prechecks tool: PE_UPGPRECHECK V15_01.E0Hd

1) Run hardware upgrade precheck tool. Proceed to the ‘Check networkthroughput’ step.

2) Validate that during calculation of the network throughput pingcommand is used with 30000 bytes for packet size for both: server andworkstation.

3) Perform the same check manually as it’s described in thedocumentation. Validate that result is the same as declared by theprecheck tool for the server and workstations.

Test Result: 1) OK. The step ‘Check network throughput’ is being executed.

2) OK. During calculation of the network throughput ping command isused with 30000 bytes for packet size for both: server and workstation.

3) OK. The check was performed manually as it’s described in thedocumentation. The result is the same as declared by the prechecktool for the server and workstations.

8/3/2019 pe-omc-app-018438_0112_en





Q01245035-03 : TMOCHIC:V15.1: BAD THROUGHPUT FOR WSCALCULATED BY PRECHECK TOOL

Problem Description :Throughput measurement precheck step of Version/Hardware UpgradePrechecks tools shows incorrect information for the station. It shows thevery low throughput although it is not the case. Network throughput valueis calculated in the wrong way for workstation. This is because of wrongpacket size for ping command, which is used for calculation of thethroughput value.

Impact:



Workaround: None.

Fix:Hardware Upgrade Prechecks tool’s documentation was updated: it wasdescribed that for both server and station the packet size for the pingcommand (which is used for calculation of the throughput value) is taken

with value 30000 bytes.


Fix verification:



Test configuration:


Tests:Test Description: Hardware Upgrade Prechecks tool: PE_UPGPRECHECK V15_01.E0HdProcedure: DS/OMC/APP/014865 V01.10/EN

Verify that in the step "C19: Check network throughput" of procedure, for both server and workstation the packet size for the ping command is

specified to be 30000 bytes.

8/3/2019 pe-omc-app-018438_0112_en






8/3/2019 pe-omc-app-018438_0112_en






None.



None.


Unless explicit remark, upgrade is done by patch installation/applicationwith install_data tool.




None.

8/3/2019 pe-omc-app-018438_0112_en





3.5. CORRECTIVE LOAD : AVL 23264 –PE_VERSUPGPRECHECK V15_01.EH9G




Throughput measurement precheck step of Version/Hardware UpgradePrechecks tools shows incorrect information for the station. It shows thevery low throughput although it is not the case. Network throughput valueis calculated in the wrong way for workstation. This is because of wrongpacket size for ping command, which is used for calculation of thethroughput value.

Impact:



Workaround:

None.

Fix:Version Upgrade Prechecks tool was modified: for both server and stationthe packet size for the ping command (which is used for calculation of thethroughput value) was taken with value 30000 bytes. So the throughputvalue obtained will be the correct one.

Modified files: /home/CIUS/gui/precheck/pre-checks.tcl/home/CIUS/gui/precheck/precheck_lib.tcl

Fix verification:



Test configuration:


8/3/2019 pe-omc-app-018438_0112_en





Tests:Test Description: Version Upgrade Prechecks tool: PE_VERSUPGPRECHECKV15_01.EH9g

1) Run version upgrade precheck tool. Proceed to the ‘Check networkthroughput’ step.

2) Validate that during calculation of the network throughput pingcommand is used with 30000 bytes for packet size for both: server andworkstation.

3) Perform the same check manually as it’s described in thedocumentation. Validate that result is the same as declared by theprecheck tool for the server and workstations.

Test Result:

1) OK. The step ‘Check network throughput’ is being executed.2) OK. During calculation of the network throughput ping command is

used with 30000 bytes for packet size for both: server and workstation.3) OK. The check was performed manually as it’s described in the

documentation. The result is the same as declared by the prechecktool for the server and workstations.

8/3/2019 pe-omc-app-018438_0112_en






Problem Description :Throughput measurement precheck step of Version/Hardware UpgradePrechecks tools shows incorrect information for the station. It shows thevery low throughput although it is not the case. Network throughput valueis calculated in the wrong way for workstation. This is because of wrongpacket size for ping command, which is used for calculation of thethroughput value.

Impact:



Workaround: None.

Fix:Version Upgrade Prechecks tool’s documentation was updated: it wasdescribed that for both server and station the packet size for the pingcommand (which is used for calculation of the throughput value) is taken

with value 30000 bytes.


Fix verification:



Test configuration:


Tests:Test Description: Version Upgrade Prechecks tool: PE_VERSUPGPRECHECKV15_01.EH9gProcedure: DS/OMC/APP/013929 V01.15/EN

Verify that in the step "C20: Check network throughput" of procedure, for

both server and workstation the packet size for the ping command isspecified to be 30000 bytes.

8/3/2019 pe-omc-app-018438_0112_en






8/3/2019 pe-omc-app-018438_0112_en






None.



None.







None.

8/3/2019 pe-omc-app-018438_0112_en





3.6. CORRECTIVE LOAD : AVL 22492 – PE_UPG_FW_T3V02_00.E01


Q01202531-01 : HB_OMC:HD OMC-R TWO T3 DISKARRAY CANNOT REACHABLE THROUGH ETHERNET LINKS


Both T3 disk arrays became unreachable through Ethernet links. Noactions had been done on T3 or Ethernet hub/switch and server before.Tries to reach T3 disk arrays with ping command have not succeeded.The root cause of the problem is that firmware version 2.01.03 installed onthe T3 disks arrays has a bug; here is SUN’s bug notification:4857833 “T3B: T3B's Running F/W 2.01.03 Network Connection Failsafter n weeks”.

Impact:

T3 disk arrays are unreachable through Ethernet links.On the OMC-R a notification is received:faultNumber: (30532) T3 DEVICE UNREACHABLE

Occurrence:

Intermittent.

Workaround: Update T3 firmware version from 2.01.03 to 2.01.06.

Fix:T3B FW 2.01.06 SUN patch 112276-13 was delivered.

Modified files: N/A

Fix verification:



Test configuration:


8/3/2019 pe-omc-app-018438_0112_en





Tests:Test Description: 1) Install FW 2.01.06 (SUN patch 112276-13) on two T3 disk arrays.2) Using telnet connect to T3 disk arrays and execute command ver .

3) Check the stability of OMC-R configuration functioning.

Test Result: 1) OK, firmware installed.2) OK, installed firmware version displayed:storedge1:/:<1>ver

T3B Release 2.01.06 2003/11/06 14:59:41 (192.168.11.134)Copyright (C) 1997-2001 Sun Microsystems, Inc.All Rights Reserved.

storedge2:/:<1>ver

T3B Release 2.01.06 2003/11/06 14:59:41 (192.168.11.135)Copyright (C) 1997-2001 Sun Microsystems, Inc.All Rights Reserved.3) OK. OMC-R is stable.

8/3/2019 pe-omc-app-018438_0112_en






None.



None.


Unless explicit remark, upgrade is done by patch installation/application.

Nominal patch installation/application was performed.



None.

8/3/2019 pe-omc-app-018438_0112_en





3.7. CORRECTIVE LOAD : AVL 21099 – PE_OSILOGD_PATCHV15_01.E01


Q01103886-01 : BYTEL VO V15.1: OSILOGD CORE GENERATEDAFTER RESTART OF THE SF880


A core-file of osilogd process is generated in the root directory after SFV880 reboot.The root cause of the problem is SUN product defect identified under BugId 6177563 “OSI 9.0 : osilogd cores when FTAM or CMIP is started”and introduced in 111344-07 patch.

Impact:

The problem is not a functional one (osilogd utility daemon is not used inOMC-R application). The only impact is that the generated file is diskspace consuming in the / partition.


Workaround: None.

Fix:osilogd executable coming with OSI patch is to be replaced with correctone from PE_FTAMPATCH V08_03.E04 (105738-10 SUN patch).

Modified files: N/A

Fix verification:



Test configuration:



1) Reboot SFV880 OMC-R server.2) Check core file.

8/3/2019 pe-omc-app-018438_0112_en





3) Install PE_OSILOGD_PATCH.4) Remove core file and reboot OMC-R server again.5) Check core file.

Test Result: 1) OK.2) OK, core file is present in the root (/) directory:sunstorm:/ <58> (root) # file corecore: ELF 32-bit MSB core file SPARC Version 1, from 'osilogd'3) OK. The patch was installed.4) OK.5) OK, core file is absent in the root (/) directory.

8/3/2019 pe-omc-app-018438_0112_en






None.



None.







None.

8/3/2019 pe-omc-app-018438_0112_en





3.8. CORRECTIVE LOAD : AVL 23687 – PE_HSI-P V03_01.E00

Installation :

The product is install_data compatible.Install package PE_HSI-P with the help of install_data tool (refer to [R1]).

Fallback :

No automatic fallback with the help of install_data tool possible.The following steps should be done to perform the fallback.

OMC-R application is stopped on the target OMC-R server.Patch CD-ROM is available and inserted in the target OMC-R server.Under croot login:1. Download from the patch CD-ROM HSI-P related products used in

V15.1 (PE_HSI-P V03_00.E00 AVL 13343 and PE_HSI-PPATCHV03_00.E03 AVL 18087) and unpack them in a temporary folder (/var/tmp, for example):

# ls /var/tmp/PE_HSI-P/V03_00.E00PE_HSI-P.V03_00.E00.cfg SUNWhsipmSUNWhsip SUNWhsipu…

# ls /var/tmp/PE_HSI-PPATCH/V03_00.E03

109715-14 apply.sh install_data.cfg...

2. Remove installed new RoHS HSI-P packages:

# pkgrm SUNWhsip# pkgrm SUNWhsipm# pkgrm SUNWhsipu

3. Install previous version of HSI-P packages and patches:

# cd /var/tmp/PE_HSI-P/V03_00.E00# pkgadd -d . SUNWhsip SUNWhsipm SUNWhsipu(Answer “Y” on all questions if needed)

# cd /var/tmp/PE_HSI-PPATCH/V03_00.E03# ./apply.sh

4. Launch install_data tool in the line mode:

# cd /cdrom/cdrom0

#./install_data.sh –c lineMode –u user_name -s active_server_IP_address -r root_password -n MMI_user -x MMI_user_password [-v]

8/3/2019 pe-omc-app-018438_0112_en





For example:(root) # ./install_data.sh -c lineMode -u ira -s 47.237.72.52 -r nortel -nadministrator -x nmc_nmc -v

5. Perform ‘markAsUnapplied’ operation for avl23687:# ./install_data.sh –c markAsUnapplied –p avl23687 [-m machine_list ] [-v]For example:(root) # ./install_data.sh -c markAsUnapplied -p avl23687 -v

6. Finish install_data session:# ./install_data.sh –c exit

3.8.1 FEATURES DELIVERED FOR GSM AND GSM-RCUSTOMERS

RFF 30156 – OMC-R SERVER ROHS COMPLIANT

Feature Description :

OMC-R server should be compliant with the Restriction of HazardousSubstances (RoHS) directive. The server based on a SFV890 will beRoHS compliant. Compliancy is required for PCI boards: HSI/U, QGE,XVR100, Dual SCSI 320 (for DAT72) and DAT72.In scope of this delivery software kit for new RoHS compliant boards isprovided.

Feature verification:



Test configuration:


Tests:

Note: all the tests were executed with delivered software installed onOMC-R configurations equipped with old (non-RoHS) cards (SFV880 andSFV890).

Test Description 1: 1) Perform nominal patch installation/application.2) Perform patch fallback.

Test Result 1:

1) OK. The patch has been installed successfully.2) OK. The patch has been fallen back.

8/3/2019 pe-omc-app-018438_0112_en





Test Description 2: Execute tests with a real BSC2G: build, audit, set on-line, get on-line, reseton-line, software downloading.

Test Result 2: OK. The results are as expected.

8/3/2019 pe-omc-app-018438_0112_en





3.8.2 FEATURES DELIVERED ONLY FOR GSM-R CUSTOMERS

None.



Executed tests with a real BSC2G: build, audit, set on-line, get on-line,reset on-line, software downloading.






None.

8/3/2019 pe-omc-app-018438_0112_en





4. V15.1 CL2/V15.1R2 CL1 POST CHRCORRECTIONS HISTORY

4.1. CORRECTIVE LOAD : AVL 25000 – OMC_APPLIV15_01.HR


Q01365703-04 : SUNDAY: MISSING FILED IN CT2000


The model with id J83_S8442_3044 has incorrect declaration in theCT2000 application. Tei assignation is incorrect for BTS models.

Impact:

Sdo2CT plug-in can not recognize the model.


Workaround:

None

Fix:Declaration of J83_S8442_3044 model has been changed. Necessarymodifications were done in Sdo2CT plug-in.


Fix verification:



Test configuration:



1) Create a network and an alternative in CT2000, load templates andsome configuration;

8/3/2019 pe-omc-app-018438_0112_en





2) Create 4 new sites J83_S8442_3044 with different TRXNumber;3) Execute Check for export SDO;4) Export SDO and execute CmdFileGeneration plug-in in create mode;5) Execute Sdo2CT plug-in;

6) Load CT files into CT2000 application;7) Make sure that the models have been recognized correctly and that

they have correct TEI assignation.

Test Result: 1) OK.2) OK.3) OK. 0 warnings, 0 errors.4) OK.5) OK.6) OK.

7) OK.

8/3/2019 pe-omc-app-018438_0112_en





Q01355526-01 : PREINT153: WRONG TEI VALUES FOR SOMEBTS MODELS.

Problem Description :It was found that several models in CT2000 application contain incorrectTEI values, they are:M03_S999_9992_1044,M03_S999_9992_244,M0D_S999_9992_1044,M0D_S999_9992_244,N03_S999_9992_1044,N03_S999_9992_244,N0D_S999_9992_1044,N0D_S999_9992_244.

All models are two cabinets configurations but contain the TEI from thethird cabinet, in other words we have 74, 75, 76 consequence instead of 71, 72, 73 in the Sector 3. That is why after creation of these models someTEIs for TRXs are not filled and BTS18000 check raises error messages.

Impact:

In case of creation of impacted models in OMC-R with correct TEIs theywill not be recognized by Sdo2Ct plug-in.

Occurrence:

Reproducible

Workaround: None

Fix:TEI values for the erroneous models have been corrected. Necessarymodifications were done in Sdo2CT plug-in.

Modified files: /CMN/base/plugins/Sdo2CT/plugin.cfg

/CMN/base/plugins/Sdo2CT/DrfInputModel/models.cts

Fix verification:



Test configuration:


8/3/2019 pe-omc-app-018438_0112_en





Tests:Test Description: Perform CT2000 - OMC-R - CT2000 loop for the following models:M03_S999_9992_1044,

M03_S999_9992_244,M0D_S999_9992_1044,M0D_S999_9992_244,N03_S999_9992_1044,N03_S999_9992_244,N0D_S999_9992_1044,N0D_S999_9992_244.Validate that all the models have been recognized correctly.

Test Result: OK. All impacted models were recognized correctly after CT2000 - OMC-R

- CT2000 loop.

8/3/2019 pe-omc-app-018438_0112_en





Q01328644-03 : CT2000: INCORRECT TEI VALUE IN INTERNALVIEW FOR SOME BTS MODELS.

Problem Description :In CT2000 application for BTS models M27_O12_122_244,N27_O12_122_244, M2H_O12_122_244 and N2H_O12_122_244 inInternal View there is incorrect value '0' for TEI for secondary band: 0, 40,41, 42, etc. Definition of these models in the database is incorrect.

Impact:

Operator is misinformed while viewing TEI in Internal View in CT2000 for impacted BTS models.


Workaround None

Fix:Impacted models definitions have been corrected. Necessarymodifications were done in Sdo2CT plug-in.

Modified files:

/CMN/base/plugins/Sdo2CT/plugin.cfg/CMN/base/plugins/Sdo2CT/DrfInputModel/models.cts

Fix verification:



Test configuration:


Tests:Test Description: Perform CT2000 - OMC-R - CT2000 loop for the following models:M27_O12_122_244;N27_O12_122_244,M2H_O12_122_244,N2H_O12_122_244Validate that all the models have been recognized correctly.

8/3/2019 pe-omc-app-018438_0112_en





Test Result: OK. All impacted models were recognized correctly after CT2000 - OMC-R- CT2000 loop.

8/3/2019 pe-omc-app-018438_0112_en





Q01336165-01 : SOME OUTDOOR BTS MODELS ARE DECLAREDAS INDOOR

Problem Description :Some Outdoor BTS models in CT2000 application are declared as Indoor -they have values of ProductLine and BCFHWRef fields as correspondingIndoor BTS Models. DLUs, which are impacted: N01, N02, N03, N17, NL7.

Impact:

In CT2000, in BSM, if user tries to find one of impacted models by filtratingon ProductLine field, he couldn’t find it.

Occurrence:

Reproducible

Workaround: None.

Fix:Definitions of Outdoor BTS Models, which were declared as Indoor models, were corrected. DLUs, which have been corrected: N01, N02,N03, N17, NL7. Necessary modifications were done in Sdo2CT plug-in.

Modified files:

/CMN/base/plugins/Sdo2CT/plugin.cfg/CMN/base/plugins/Sdo2CT/DrfInputModel/models.cts

Fix verification:



Test configuration:


Tests:Test Description: 1) Create a configuration under OMC-R with following models:

N01_S1818181_2644N01_S1818182_2644N01_S1818183_2644N01_S12181_2644N01_S12182_2644N01_S666_1212122_1044

N01_S666_1212123_1044N01_S666_1212122_244

8/3/2019 pe-omc-app-018438_0112_en





N01_S666_1212123_244N02_S1818181_2644N02_S1818182_2644N02_S1818183_2644

N02_S18181_2644N02_S18182_2644N02_S99182_2644N02_S999_9991_1044N02_S999_9992_1044N02_S999_9993_1044N02_S999_9991_244N02_S999_9992_244N02_S999_9993_244N02_O18_182_1044N02_O18_182_244

N02_S99_18182_1044N02_S99_18183_1044N02_S99_18182_244N02_S99_18183_244N03_O151_2644N03_S3691_2644N03_S9631_2644N03_S3961_2644N03_S33121_2644N03_S315151_2644N03_S315152_2644N03_S612151_2644N03_S612152_2644N17_S1818181_2644N17_S1818182_2644N17_S1818183_2644N17_S121212_6661_1044N17_S121212_6662_1044N17_S121212_6663_1044N17_S121212_6661_244N17_S121212_6662_244

N17_S121212_6663_244NL7_S2221_2644NL7_S3331_2644NL7_S999_6661_1044NL7_S999_6662_1044NL7_S999_6663_1044NL7_S999_6661_244NL7_S999_6662_244NL7_S999_6663_244

2) Execute Sdo2CT plug-in and load CT files into CT2000 application.3) Make sure that value of Bts Product parameter is correct for all sites.

8/3/2019 pe-omc-app-018438_0112_en





Test Result: 1) OK.2) OK.3) OK. The value of Bts Product parameter is correct for all sites.

8/3/2019 pe-omc-app-018438_0112_en






None.

4.1.3 FEATURES DELIVERED FOR GSM AND GSM-RCUSTOMERS

RFF 27899: BTS 18000 DUAL MODE (BTS COMBO)

Feature Description :

The GSM/UMTS combo BTS is based on the existing BTS18000 NortelGSM BTS.The new combo BTS addresses the future convergence of GSM with

UMTS (the 3G wireless standard), which utilizes an air interface based onCDMA. It is also an important part of the Nortel convergence effort todevelop common designs for different systems and thus reduce costs.The combo BTS is available for all GSM frequency bands supported byGSM BTS18000 and for the 1900 or 2100 MHz bands for UMTS. Mixedconfigurations supported so far are, GSM 900 or GSM 1800/UMTS 2100.The combo BTS supports the same GSM dual band configurations as theBTS18000 taking into account the restriction that one GSM shelf is filledwith UMTS equipment (constraints on number of available RF combiner equipment for the different bands). The support for concentric cellconfigurations using either RM or HPRM modules (no mix allowed) is alsothe same as for BTS18000 for a given software version and GSMconfiguration.

Feature verification:



Test configuration:


Tests:

The following tests were performed in scope of the feature validation: Creation of sites with new DLU Presentation of new sites in CT2000 GUI SDO2CT plugin CommandFileGeneration plugin Site Assistant Site Internal view Loop Delta command files with a new BSS and modifications on an

existing BSS

8/3/2019 pe-omc-app-018438_0112_en





Delta DRF Delta SDO Delta command files without modifications Creation command files generation

Get parameter from BTSSMModel Rule Recovermodel Rule

Tests results were as expected.

8/3/2019 pe-omc-app-018438_0112_en





4.1.4 FEATURES DELIVERED ONLY FOR GSM-R CUSTOMERS

None.



None.







None.

8/3/2019 pe-omc-app-018438_0112_en





4.2. CORRECTIVE LOAD : AVL 24750 –PE_EMERGENCY_PATCH V15_01.E06


Q01291382-01 : TMUK:GSM:OMC-R:V14.3.2: OMC-R SWAP -PROBLEM ON PSUS - SFV880


When PSU 0 (first PSU on the right hand side) of SFV880 is unpluggedthere is no alarm on MMI level, prtdiag doesn't report the alarm too, butalarm is present on the console.The Platform Information and Control Library (PICL) provides amechanism to publish platform-specific information for clients to access ina platform-independent way. PICLD maintains and controls the PICLinformation from clients and plug-in modules. Latest patches for PICLDplug-in modules must be applied.

Impact:

When PSU 0 (first PSU on the right hand side) of SFV880 is unpluggedthere is no alarm on MMI level, prtdiag doesn't report the alarm too, butalarm is present on the console.


Workaround: None

Fix:The following SUN patches have been delivered withPE_EMERGENCY_PATCH V15_01.E06 product and should be applied tothe system:108528-29

111792-13117005-01

Fix verification:



8/3/2019 pe-omc-app-018438_0112_en





Test configuration:


Tests:Test Description: 1) Install the patch on SFV880 server by means of install_data.2) Simulate the power supply failure (for each power supply of the server)

by pulling out the power cord.3) Validate that the fault is detected and reported by prtdiag tool.4) Validate that the fault is reported on MMI: corresponding alarm is

risen.5) Eliminate the power supply malfunction: pull back the power cord.6) Validate that prtdiag tool reports normal state of PS.

7) Validate that corresponding alarm on MMI is cleared.

Test Result: 1) OK. Installation is successful.2) OK. Power supply failure is simulated. All 3 power supplies were

verified following the sequence.3) OK. prtdiag tool reports failure.4) OK. An alarm is risen on MMI.5) OK.6) OK. prtdiag tool reports normal state of PS.

7) OK. The alarm on MMI is cleared.

8/3/2019 pe-omc-app-018438_0112_en





Q01330639 : E3:GSM:OMC-R:V15_01.BR: SYBASE NOTRESPONDING

Problem Description :The OMC-R is in hang state as no commands implying Sybase access arepossible. Sybase connection is not possible.The problem was observed particularly during execution of FPCprocedure.Investigations of the problem showed that it is known by SUN. Theproblem was introduced with the fix of the bug 4924525 ‘timod racecondition when ioctl is interrupted under flow control’ included in the patch110955-05 (installed with OMC-R only on SFV890) and its correction isincluded into the patch 110955-06.According to SUN:

“The fix for bug 4924525 introduced a problem whereby rapidly interruptedioctls can cause the timod write queue to remain unscheduled andunserviced. This most often results in the application hanging waiting onan outstanding reply to some ioctl or other message queued on theunserviced timod write queue.”

Impact:

The OMC-R is in hang state as no commands implying Sybase access arepossible. Sybase connection is not possible.

Occurrence: Could be reproduced in specific conditions.

Workaround: None

Fix:The patch 110955-06 for SFV890 has been delivered withPE_EMERGENCY_PATCH V15_01.E06 product and should be applied tothe system.

Fix verification:



Test configuration:


8/3/2019 pe-omc-app-018438_0112_en





Tests:Configuration:

server SFV890 (OMCRCORESERV)station SB150 (STATDATAEXP)

MaxBDE for FPC configuration contains:15 BSC, 2880 Bts and Sites, 12960 TDMA,12960 TRX, 3600 FHS, 103680 channels.

Original problem was reproduced on this configuration in OMC-R V15.1.

4 BSS simulators (NEOS).

OMC-R is started. All BSC are built.

A lot of SMS broadcast are activated.Several jobs on audit launching are activated.

Test Description: 1) Run FPC plugin on modifications of all TDMA objects.2) During the plugin work perform some MMI commands: Display, Audit.3) When plugin finishes its work, check that OMC-R is operational: MMI

commands can be successfully performed.4) Connect to sybase and check that it's operational.

Test Result: 1) OK. FPC plugin is launched with configuration file, which contains

about 10800 lines.2) OK. During FPC plugin work MMI commands can be processed.3) OK. The plugin finishes after 1 hour and 20 minutes. FPC Command

files are created. MMI commands can be performed.4) OK. Data select from sybase is successfully performed.

8/3/2019 pe-omc-app-018438_0112_en






None.



None.







None.

8/3/2019 pe-omc-app-018438_0112_en







Q01387113-01 : OMCR1 SERVER’S SERVICE LEDS ARE ON


Under some circumstances picld daemon begins generating ERRORmessages in /var/adm/messages.This problem leads to impossibility to get environmental status with prtdiagand service LED is switched on.

After consulting with sun technicians it was found that this is known issueof picld daemon tracked by note "FIELD INFORMATION NOTICE" number 102279. Root cause is in ‘noisy’ I2C bus which causes picld to report falseenvironmental FRU failures. This problem is fixed by the patch 111792-15.

Currently in V15.x the following releases of 111792-xx are used:On SFV880: 111792-03On SFV890: 111792-11

Impact:

False environmental FRU failures are reported, service LED is switchedon; it’s impossible to get correct environmental status with prtdiag.

Occurrence: Rare

Workaround: None

Fix:The latest patch 111792-16 for PICL daemon with the latest Solaris 2.8

kernel patch 108528-29 have been delivered with the productPE_EMERGENCY_PATCH V15_01.E07 and should be applied to thesystem.

Fix verification:



8/3/2019 pe-omc-app-018438_0112_en





Test configuration:


Tests:Test Description: 1) Install PE_EMERGENCY_PATCH V15_01.E07 on V15.1

(V15_01.HR) SFV880 or SFV890 OMC-R server with install_data.2) Check environmental status with prtdiag tool.

Test Result: 1) OK. Installation has succeeded; server has been restarted without

errors.

2) OK. No errors reported by prtdiag tool.

8/3/2019 pe-omc-app-018438_0112_en






None.



None.







None.

8/3/2019 pe-omc-app-018438_0112_en





5. V15.1R2 CL2 CONTENTS

5.1. DEFINITION

This OMC-R software version is known as:

• V15.1R2 CL2 for GSM-R customers,

and is defined by:

- contents of last CL applied on previous V15.1 version;

- new fixes GSM and GSM-R detailed in this chapter.

Corresponding loads are defined in chapter:

ANNEX A: V15.1 Post-ChR Product Versions

(V15.1R2 CL2 delivery).

8/3/2019 pe-omc-app-018438_0112_en





5.2. CORRECTIVE LOAD : AVL 25757 – OMC_APPLI V15_01.IR


Q01408131 : OMC-R:BDA AUDIT HAS TO SHOW ALLDIFFERENCES BETWEEN BDE AND BDA


Unclear results during Audit if inconsistency found on baseColourCodeand/or networkColourCode attributes of bts and adjCHO objects: thedifference is reported but <no value available> is displayed instead of parameters’ values.The root cause of the problem is incorrect mediation of these attributes in

audit2G tasks.

Impact:

Unclear results of the Audit action.


Workaround: None

Fix:The mediation of baseColourCode and networkColourCode attributes inaudit2G tasks has been fixed.

Fix verification:



Test configuration:


Tests:Test Description: 1) BSC 2GV15 and BSC 2GV12 are created and built.2) Perform "Audit BDA" action on BSC2GV12 and BSC2GV15.3) Launch backup operation:

ds_restoreBsc.sh -B89 -Obackupds_restoreBsc.sh -B100 -Obackup

4) Create inconsistencies on some parameters:

8/3/2019 pe-omc-app-018438_0112_en





Change baseColourCode from 4 to 3 onBSC89;btsSiteManager45;bts0Change baseColourCode from 4 to 0 onBSC100;btsSiteManager2;bts0

5) Launch restore operation:ds_restoreBsc.sh -B89 -Orestoreds_restoreBsc.sh -B100 -Orestore

6) Perform "Audit BDA" action on BSC2GV12 and BSC2GV15.

Test Result: 1) OK.2) OK. No BDE/BDA differences exist.3) OK. BSC database backup has been performed.

4) OK.5) OK. BSC database restoration has been performed.6) OK. BDA Audit found inconsistencies between BDE and BDA on the

impacted parameters:

09/28/06 08:04:44 1921687550000025 iss 10.10.2.38Audit BDA-bsc: object = (bsc = 89);

09/28/06 08:04:44 1921687550000025 iss 10.10.2.38 SUCCEEDED (other answers follow)object bsc 89 (bsc2Gv15)

09/28/06 08:04:56 1921687550000025 iss 10.10.2.38 SUCCEEDED (completed)inconsistencies

object class: btsobject instance: (bsc 89 (bsc2Gv15) | btsSiteManager 45 (B89-S45_S12000Ind gsm U11) | bts 0 (B89-S45_S12000 Ind gsm U11_0))----------------------------------------------------------------------------------------------parameter | value in BDA | value in BDE-----------------------------------+-----------------------------+----------------------------baseColourCode | 3 | 4networkColourCode | 4 | 4

**************************************************************************


09/29/06 05:16:12 1921687550000140 iss 10.10.2.38 SUCCEEDED (other answers follow)

object bsc 100 (bsc2Gv12)


object class: btsobject instance: (bsc 100 (bsc2Gv12) | btsSiteManager 2 (B100-

S02_S2000) | bts 0 (B100-S02_S2000_0))----------------------------------------------------------------------------------------------parameter | value in BDA | value in BDE-----------------------------------+-----------------------------+----------------------------baseColourCode | 0 | 4networkColourCode | 4 | 4

8/3/2019 pe-omc-app-018438_0112_en





Q01423174 : OMC-R:BDA AUDIT HAS TO SHOW ALLDIFFERENCES BETWEEN BDE AND BDA

Problem Description :Unclear results during Audit if inconsistency found onabsoluteRFChannelNo / fhsRef / maio attributes of channel object, cic of xtp object and averagingPeriod of handOverControlMatra object: theinstances on which inconsistencies were found are reported, but nodifferences in values are shown for them.The root cause of the problem is incorrect mediation of these attributes inaudit2G tasks.

Impact:

Unclear results of the Audit action.


Workaround: None

Fix:The mediation of impacted attributes in audit2G tasks has been fixed.

Fix verification:



Test configuration:


Tests:

Test Description: 1) BSC 2GV15 and BSC 2GV12 are created and built.2) Perform "Audit BDA" action on BSC2GV12 and BSC2GV15.3) Launch backup operation:

ds_restoreBsc.sh -B89 -Obackupds_restoreBsc.sh -B100 -Obackup

4) Create inconsistencies on some parameters:Parameters averagingPeriod and absoluteRFChannelNol have beenchanged.

5) Launch restore operation:ds_restoreBsc.sh -B89 -Orestore

ds_restoreBsc.sh -B100 -Orestore

8/3/2019 pe-omc-app-018438_0112_en





6) Perform "Audit BDA" action on BSC2GV12 and BSC2GV15.

Test Result: 1) OK.

2) OK. No BDE/BDA differences exist.3) OK. BSC database backup has been performed.4) OK.

averagingPeriod and absoluteRFChannelNol have been changed:a) BSC2GV15averagingPeriod from 20 to 19absoluteRFChannelNol from 3 to 11b) BSC2GV12averagingPeriod from 20 to 100absoluteRFChannelNol from 15 to 30

5) OK. BSC database restoration has been performed.

6) OK. BDA Audit found inconsistencies between BDE and BDA on theimpacted parameters:




object class: handOverControlobject instance: (bsc 89 (bsc2Gv15) | btsSiteManager 45 (B89-S45_S12000

Ind gsm U11) | bts 0 (B89-S45_S12000 Ind gsm U11_0) | handOverControl 0)----------------------------------------------------------------------------------------------parameter | value in BDA | value in BDE-----------------------------------+-----------------------------+----------------------------averagingPeriod | 19 | 20

thresholdInterference | boundary 0 -107 dBm | boundary 0 -107 dBm| boundary 1 -109 dBm | boundary 1 -109 dBm| boundary 2 -111 dBm | boundary 2 -111 dBm| boundary 3 -113 dBm | boundary 3 -113 dBm

object class: channelobject instance: (bsc 89 (bsc2Gv15) | btsSiteManager 45 (B89-S45_S12000

Ind gsm U11) | bts 0 (B89-S45_S12000 Ind gsm U11_0) | transceiver 1 | channel 0)----------------------------------------------------------------------------------------------

parameter | value in BDA |value in BDE-----------------------------------+-----------------------------+----------------------------absoluteRFChannelNo | 11 | 3

fhsRef | <no value available> | <no value available>maio | <no value available> | <no value available>

**************************************************************************



8/3/2019 pe-omc-app-018438_0112_en






object class: handOverControlobject instance: (bsc 100 (bsc2Gv12) | btsSiteManager 7 (B100-S07_S8002

Outdoor) | bts 0 (B100-S07_S8002 Outdoor_0) | handOverControl 0)----------------------------------------------------------------------------------------------parameter | value in BDA | value in BDE-----------------------------------+-----------------------------+----------------------------averagingPeriod | 100 | 20

thresholdInterference | boundary 0 -107 dBm | boundary 0 -107 dBm| boundary 1 -109 dBm | boundary 1 -109 dBm| boundary 2 -111 dBm | boundary 2 -111 dBm| boundary 3 -113 dBm | boundary 3 -113 dBm

object class: channelobject instance: (bsc 100 (bsc2Gv12) | btsSiteManager 7 (B100-S07_S8002

Outdoor) | bts 0 (B100-S07_S8002 Outdoor_0) | transceiver 1 | channel 1)----------------------------------------------------------------------------------------------

parameter | value in BDA | value in BDE-----------------------------------+-----------------------------+----------------------------absoluteRFChannelNo | 30 | 15fhsRef | <no value available> | <no value available>maio | <no value available> | <no value available>

8/3/2019 pe-omc-app-018438_0112_en





Q00863131-05 : COUNTER CONNECTIONDURATIONTCHCUM(1600/0)

Problem Description :The following modifications should be done to synthetic counters 8623(averageDLRxLev), 8624 (averageULRxLev), 8625 (averageDLRxQual)and 8626 (averageULRxQual):

(C1600/480) has to be replaced by ((C1600/480) -1)(C1603/470) has to be replaced by ((C1603/470) -1)

Impact:

Impacted synthetic counters are calculated in the wrong way.


Workaround None

Fix:Formulas of corresponding synthetic counters have been corrected.

Fix verification:



Test configuration:



1) BSC e3V15 is created and built.2) Create mdScanner and simulate OFS observations.3) In MMI open Performance->Open Performance Monitor. Create new

report on object bts for every synthetic counter (C8623(averageDLRxLev), C8624 (averageULRxLev), C8625(averageDLRxQual), C8626 (averageULRxQual)) including thesynthetic counter itself and raw counters contained in its formula(according to the file bss_nmc_formulas.dat).

4) Make sure that synthetic counters 8623, 8624, 8625 and 8626 arecalculated according to the correct formulas.

8/3/2019 pe-omc-app-018438_0112_en





Test Result: 1) OK.2) OK. OFS observations have been generated.3) OK. Reports were created for every counter (C8623

(averageDLRxLev), C8624 (averageULRxLev), C8625(averageDLRxQual), C8626 (averageULRxQual))

4) OK. Synthetic counters are calculated correctly.

8/3/2019 pe-omc-app-018438_0112_en






None.



OMC-R sanity tests have been performed.







None.

8/3/2019 pe-omc-app-018438_0112_en







Q01338121-01 : PREVENTIVE UPDATE OF THE SOLARISPATCHES FOR THE DAYLIGHT SAVING TIME CHANGE


According to Energy Policy Act of 2005 , signed on August 8, 2005, timechange dates for Daylight Saving Time in the U.S. will be changed:beginning in 2007, DST will begin on the second Sunday of March andend the first Sunday of November.Following this change the next preventive actions should be done:

- deliver Sun patches for Solaris 8 dedicated to DST in U.S.;

- there are no patches for Solaris 2.6 expected due to End-Of-Supportfor Solaris 2.6 (23/07/2006). Possible solution for the problem shouldbe investigated.

Impact:

DST time change on OMC-R configurations installed in U.S. time zoneswill be performed according to the old schedule, if no changes will beapplied intended for the new time change dates introduced.

Occurrence: N/A

Workaround: None.

Fix:The next SUN patches for Solaris 8 dedicated to DST in U.S. weredelivered:108993-53109809-02Following additional SUN patches which have to be installed on machinesbefore applying DST patches were delivered:108528-29111023-03111317-05113648-03115827-01116602-01

8/3/2019 pe-omc-app-018438_0112_en





Fix verification:



Test configuration:


Tests:Test Description: On an OMC-R configuration change the system date and wait for the DSTtime changing. Validate that it is performed according to the new schedule.

Test Result: OK. DST time change is performed according to the new schedule.

8/3/2019 pe-omc-app-018438_0112_en





Q01338136-01 : PREVENTIVE UPDATE OF THE SOLARIS PATCHFOR QGE CARDS

Problem Description :According to SUN recommendations patch 111883-31 (or higher) for QGEcards (introducing a variety of different fixes) should be installed on OMC-R configurations. Thus this patch should be delivered.

Impact:

None – preventive action.

Occurrence: N/A.

Workaround: None.

Fix:SUN patch 111883-34 for Solaris 8 was delivered.

Modified files: N/A

Fix verification:



Test configuration:


Tests:

Test Description: 1) Execute OMC-R upgrade post-checks (steps to validate sanity of anOMC-R system) according to the procedure DS/OMC/APP/013889.

2) Validate huge files transferring between OMC-R server and stations vianetwork.

3) Validate basic operations on OMC-R.

Test Result: 1) OK. The result is as expected.2) OK.3) OK.

8/3/2019 pe-omc-app-018438_0112_en






None.



None.







None.

8/3/2019 pe-omc-app-018438_0112_en





6. V15.1R2 CL2 POST CHR CORRECTIONSHISTORY

6.1. CORRECTIVE LOAD : AVL 26237 – OMC_APPLI V15_01.JR


Q01479255-03 : OMC-R RESTARTS AFTER V16CHRCL2PATCHES APPLICATION


Customer has one configured External Manager. This manager is sendingsimple GET request to OMC-R each 30 seconds all the time. At the sametime OMC-R is sending events to External Manager.There is only one opened association between External Manager andOMC for both events and commands.Normally there should be 2 associations: one for events, it is opened byOMC, and one for commands, opened by External Manager.In the current case there is only one association and it is openedconcurrently by OMC or External Manager and then used by both entities.On customer site it is done by External Manager.

Association in CMIP has parameter "Inactivity timer".This parameter defines how long an association can remain idle before itis closed automatically by the CMIP daemon. If the inactivity timer is set to0, the association remains open until it is explicitly closed. This parameter can be set in the range of 0 to 255. The default value is 12.Local Manager and OMC Agent connect to CMIP with configuredparameter "Inactivity timer" set to value 720 seconds.Local Manager works with OMC Agent via CMIP loopback, thus there is noassociation for this connection and "Inactivity timeout" parameter for it isnot used in normal cases.

The problem is reproduced under the following conditions:1. There is only one association between External Manager and OMC.2. External Manager sends periodically its GET request to OMC.3. Commands from Local Manager are working fine for some time.4. OMC-R generates some events, they are sent to External Manager butthen there are no more events sent for several minutes (more than 12).EFD object remains unlocked all the time.5. Upon expiration of inactivity timeout of 720 seconds after last event,CMIP tried to close association not between External Manager and OMCbut between Local Manager and OMC. And this attempt has failed.6. After that operation commands from Local Manager sometimes ends

with "Communication Error". This means that "Inactivity timeout"

8/3/2019 pe-omc-app-018438_0112_en





mechanism inside CMIP spoiled connection between Local Manager andOMC.The possible reason of problem can be the "Inactivity Timeout"mechanism inside CMIP implemented incorrectly for case of single

association for both commands and events.

Impact:

As a result of the described problem occurrence commands from LocalManager can finish with "Communication Error".

Occurrence: Rare, can be reproduced under certain circumstances only.

Workaround: Lock all EFD objects in OMC-R.

Fix:Inactivity timeout is set to 0, so CMIP "Inactivity Timeout" mechanism isnever activated.In such case opened associations will remain open until they are explicitlyclosed by applications or by network problems.

Fix verification:



Test configuration:


Tests:Test Description1: Non-regression tests for Local Manager operations have been done.

Test Result1:

OK. The results are as expected.

Test Description2: Non-regression tests for External Manager operations have been done.

Test Result2: OK. The results are as expected.

8/3/2019 pe-omc-app-018438_0112_en






None.



OMC-R sanity tests have been performed.Non-regression tests for Local Manager operations have been done.Non-regression tests for External Manager operations have been done.






None.

6.2. CORRECTIVE LOAD: AVL 26597 – OMC_APPLI V15_01.KR


Q01542131-01: GSMR: BSS: KEIN KORREKTES ABARBEITUNGVON "GLOBEL COMMANDFILES"

PROBLEM DESCRIPTION :

Customer has tried to estimate command files execution time by means of Command file estimator plugin, but estimation has failed as the plugincould deal only with command file enclosed by double quotes (") in theRun-commandFile command sequence. But actually these quotes weremissed, and this behavior is supposed to be normal, so command filename extraction mechanism must be improved.

Impact:

As a result of the described problem command file time estimation can failif command file is not enclosed by double quotes.

8/3/2019 pe-omc-app-018438_0112_en





Occurrence:

Every time if command file estimator is supplied with command file not

enclosed by double quotes.

Workaround:

Fix command file manually to enclose file names with double quotes.

Fix:

Processing of the Run-commandFile command has been improved inorder to allow command file execution with or without double quotesenclosure.

Fix verification:



Test configuration:


Tests:Test Description1: Non-regression tests for command file estimator have been done.

Test Result1: OK. The results are as expected.

8/3/2019 pe-omc-app-018438_0112_en






None.



OMC-R sanity tests have been performed.Non-regression tests for command file estimator have been done.






None.

6.3. CORRECTIVE LOAD: AVL 27450 – OMC_APPLI V15_01.LR


Q01681763-03: GSMR: BSS: V15.1R2: S8000 - O4CONFIGURATION NOT POSSIBLE

PROBLEM DESCRIPTION :

In accordance with document PE/BTS/DD/0866, depopulation algorithm of O6 model is different from standard one, implemented in CT2000.As displayed on picture below, in order to create O4 configuration fromO6, one by one DRX should be deleted from each radio modules.

8/3/2019 pe-omc-app-018438_0112_en





Depopulated configuration

But CT2000 provide deleting only from last radio module. In this case, TEIin CT2000 would be different from right model.So, since CT2000 does not provide creating right O4 configuration bydepopulation from O6, model O4 with right TEIs should be implementedinto CT2000.

Impact:

User can not create necessary model O4 by depopulation from O6 withright TEIs.

Occurrence:

Reproducible

Workaround:

Create O4 model by depopulation from O6 via CT2000, export SDO filesand then correct TEIs manually via SDO files.

Fix:

Update SDO to CT plugin to be compliant with CR Q01681763.

Fix verification:



Test configuration:


Tests:Test Description1:

8/3/2019 pe-omc-app-018438_0112_en





1. Create some configuration under OMC-R with S05_O41_2611 andT05_O41_2611 models.2. Export CT files and load it to CT2000.3. Make sure that the models are recognized correctly.

Test Result1: 1. Configuration has been created.2. CT files successfully loaded.3. Models are recognized correctly.

8/3/2019 pe-omc-app-018438_0112_en






None.



OMC-R sanity tests have been performed.







None.

8/3/2019 pe-omc-app-018438_0112_en





7. UPGRADE


7.1. CORRECTIVE LOAD : AVL 24032 – OMC_APPLIV15_01.FR

Validated upgrade paths:

• OMC-R version V15_01.BR→ OMC-R version V15_01.FR

7.2. CORRECTIVE LOAD : AVL 21904 – DS_OMC_CIUSV15_01.BV

N/A

7.3. CORRECTIVE LOAD : AVL 23265 – PE_UPGPRECHECKV15_01.E0HD

N/A

7.4. CORRECTIVE LOAD : AVL 23264 –PE_VERSUPGPRECHECK V15_01.EH9G

N/A

7.5. CORRECTIVE LOAD : AVL 22492 – PE_UPG_FW_T3V02_00.E01

N/A

7.6. CORRECTIVE LOAD : AVL 21099 – PE_OSILOGD_PATCHV15_01.E01

N/A

7.7. CORRECTIVE LOAD : AVL 23687 – PE_HSI-P V03_01.E00

N/A

8/3/2019 pe-omc-app-018438_0112_en





7.8. CORRECTIVE LOAD : AVL 25000 – OMC_APPLIV15_01.HR


• OMC-R version V15_01.GP→ OMC-R version V15_01.HR


N/A


N/A

7.11. CORRECTIVE LOAD : AVL 25757 – OMC_APPLI V15_01.IR


• OMC-R version V15_01.BR→ OMC-R version V15_01.IR

7.12. CORRECTIVE LOAD : AVL 24270 –

PE_EMERGENCY_PATCH V15_01.E05N/A

7.13. CORRECTIVE LOAD : AVL 26237 – OMC_APPLI V15_01.JR


• OMC-R version V15_01.BR→ OMC-R version V15_01.JR



• OMC-R version V15_01.BR→ OMC-R version V15_01.KR



• OMC-R version V15_01.BR→ OMC-R version V15_01.LR

8/3/2019 pe-omc-app-018438_0112_en





8. KNOWN ISSUES

Q01341049 : ID: GZIP HAS WRONG RIGHTS


Installation of a patch with install_data tool finishes with error “Internalerror occurred during patch size definition”. The problem is thatinstall_data can not uncompress the patch package with gzip (copied byinstall_data to the /tmp directory of the machine during sessioninitialization), because /tmp/gzip has not rights for execution.

Impact:

Installation of some products by means of install_data is not possible.

Occurrence: Intermittent.

Workaround: After install_data session initialization and establishment of the connectionto OMC-R configuration (before any patches installation) change the filerights for the /tmp/gzip.Under croot login:# chmod 777 /tmp/gzip

Target for fix:V17

8/3/2019 pe-omc-app-018438_0112_en





Q01416533 : DURING PATCH AVL24750&AVL24826APPLICATION, ABNORMAL MESSAGE OCCURED

Problem Description :SFV880 system running Solaris 8 contains warnings in/var/adm/messages similar to the following:krtld: [ID 995402 kern.notice] /platform/sun4u/kernel/misc/sparcv9/sbd:undefined symbol 'sbdp_portid_to_cpu_unit'krtld: [ID 995402 kern.notice] /platform/sun4u/kernel/misc/sparcv9/sbd:undefined symbol 'plat_max_cmp_units_per_board'krtld: [ID 472681 kern.notice] WARNING: mod_load: cannot load module'sbd'gptwo: [ID 450795 kern.warning] WARNING: cannot load sbdkrtld: /platform/SUNW,Sun-Fire-880/kernel/misc/sparcv9/sbdp: undefined

symbol 'gptwocfg_unconfigure'krtld: /platform/SUNW,Sun-Fire-880/kernel/misc/sparcv9/sbdp: undefinedsymbol 'gptwocfg_configure'

This is a known Sun problem (SRDB 77717) and may be fixed with Solaris8 patch 116970-02 or later.

Impact:

/var/adm/messages is filling up with persistent warnings.


Workaround: Add the following to /etc/system and reboot:

exclude: sbdpexclude: gptwoexclude: sbd

Target for fix:

Target release for the fix is not defined yet.As one of potential solutions a bulletin could be introduced to describe theworkaround that should be applied to eliminate the problem.

8/3/2019 pe-omc-app-018438_0112_en





9. ON-SITE SOAK PERIOD RESULTS

9.1. FIXES OF V15.1 CL2 LOAD

Description of the soak period:

During the soak period no functional regression or instability has beenobserved.No specific tests were carried out during the soak period.

Equipment Information:

TYPE VERSION / PATCH

OMC-R SF V890V15.1 CL2

BSC e3v15.1 CL2

TCU 2G / e3v15.1 CL2

BTSS4000

S8000 BCF / CBCFS12000

S18000

v15.1 CL2

PCUSN PCUSN 24v15.1 CL2

Operation Performed on load in soaked test:

• OMC load

Operations / Configuration Yes/NoOMC-R BSC Link (A interface or SLS) IP

External Q3 Manager YesFrequency Plan change thennotifications check and BDA audit

No

BSC Reparenting then notificationscheck and BDA audit

Yes

Command files executed Yes

BDE Backup / Restore Yes

Check SYBASE database: executeds_check_db.sh

No

Check consistency of HW configuration:execute ds_checkGlobal.sh

No

Manual switchover performed No (monobox configuration)

Observation and Counters Check onSDO Yes

CallTrace performed Yes

8/3/2019 pe-omc-app-018438_0112_en





CallPathTrace performed Yes

Real Time Observation Yes

Fast Statistic Observation Yes

General Statistic Observation Yes

Notifications and Counters Check Yes

• DS_OAM load

Shell Shell usedds_checkMdBscLink.sh Yes

ds_check_MB.sh

ds_startOmc_MB.sh

ds_autoSelectDelivery.sh Yes

PCU SN upgrade plugin Yes

BSC e3 upgrade shells Yes

TCU e3 upgrade shells Yes

BTS upgrade shells Yes

NORTEL TAS has approved the load (V15.1 CL2) rollout.



During the soak period no functional regression or instability has beenobserver.

The following comments about the application procedure have beenpointed out:1) SUN documentation recommends Solaris patches application in

single-user mode, whereas the application with install_data isexecuted in multi-user environment.

SUN almost always recommends installing patches in single-user mode. This is done

- to guarantee that no other users are logged to the system;

-to minimize impact of software running.

Patches can be also installed in multi-user mode. In this case beforeSolaris patches installation the following prerequisites should berespected:

- ensure that no users are logged in and perform any activities;

- to minimize impact of software running stop OMC-R application.

2) The SBD module generated huge message flow into/var/adm/messages. Problem is described by SUN notice 77717 andClarify case 060814-42604.

The same problem is tracked by CR Q01416533. See chapter 8KNOWN ISSUES for details.

8/3/2019 pe-omc-app-018438_0112_en







OMC-R SF880/T3V15.1

BSC 3GV15.1

TCU 2G/3GV15.1

BTSV15.1

PCUSN 6 / 12 / 24V15.1


As written in the patch application document – the prtdiag command wasissued after patch installation with success.

NORTEL TAS has approved the load rollout.

9.3. FIXES OF V15.1R2 CL1 LOAD


During the soak period no functional regression or instability has beenobserved.No specific tests were carried out during the soak period.



OMC-R SF880 + T3Avl23086Avl24032Avl22492Avl21099Avl23687

Avl21904Avl23264Avl23265

8/3/2019 pe-omc-app-018438_0112_en





BSC 3000 B3G15100319D

TCU 3000 TC315100210

BTS S8000 CBC15C160CDR15C225

PCUSN N/A N/A


• OMC load

Operations / Configuration Yes/NoOMC-R BSC Link (A interface or SLS) No

External Q3 Manager No

Frequency Plan change thennotifications check and BDA audit

No

BSC Reparenting then notificationscheck and BDA audit

No

Command files excuted Yes

BDE Backup / Restore No

Check SYBASE database : executeds_check_db.sh

No

Check consistency of HW configuration :execute a dscheckglobal.sh

No

Manual switchover performed No

Observation and Counters Check onSDO

No

CallTrace performed No

CallPathTrace performed No

Real Time Observation No

Fast Statistic Observation No

General Statistic Observation No

Notifications and Counters Check Yes

•

DS_OAM loadShell Shell used

./bin/ds_softwareSwitch.sh No

./bin/ds_auditBDA.sh Yes

./bin/ds_reduceTraffic.sh No

./bin/ds_restoreTraffic.sh No

./bin/ds_checkMdBscLink.sh No

./bin/ds_getNotif.sh No

./bin/CheckCusto.x No

./bin/ds_makeMirror.sh No

./bin/ds_startOmc.sh No

./bin/ds_buildBDAOnLine.sh No

./bin/ds_transbsc.sh No

./bin/ds_activateNewBDA.sh No

8/3/2019 pe-omc-app-018438_0112_en





./bin/ds_bssUpgrade.sh Yes

./bin/ds_transbts.sh No

./bin/ds_check.sh No

./bin/ds_check_db.sh No

./bin/ds_checkGlobal.sh No

./bin/ds_backup.sh Yes

./bin/ds_restore.sh No

./bin/ds_restoreAll.sh No

./bin/ds_restoreBDE.sh No

./bin/ds_restoreMaj.sh No

./lib/ds_downloadTools.sh No

./lib/ds_configDisks.sh No

NORTEL TAS has approved the load (V15.1R2 CL1) rollout.

8/3/2019 pe-omc-app-018438_0112_en





10. ABBREVIATIONS AND DEFINITIONS

10.1. ABBREVIATIONS

CL Corrective Load

EP Emergency Patch

AVL Avis de Livraison / Delivery Notice

BSC Base Station Controller

BSS Base Station Sub-system

BTS Base Transceiver Sub-system

TCU TransCoder Unit

OMC Operations and Maintenance Centre

10.2. DEFINITIONSFix Any software supplied outside a complete system delivery (“version” or

“edition”). The word “fix” is used to cover deliveries of partial sub-system

loads, complete sub-system loads or even new products.

8/3/2019 pe-omc-app-018438_0112_en





11. ANNEXES

ANNEX A: V15.1 POST-CHR PRODUCT VERSIONS

A.1 INITIAL DELIVERY FOR GSM

Line-up: V15.1_postChr_CoL_1

Product Version

OMC_APPLI V15_01.BR (AVL 23086)

DS_OMC_CIUS V15_01.BV (AVL 21904)

PE_UPGPRECHECK V15_01.E0Hc (AVL 20919)

PE_VERSUPGPRECHECK V15_01.EH9f (AVL 20918)PE_HSI-P V03_00.E00 (AVL 13343)

A.2 INITIAL DELIVERY FOR GSM-R

Line-up: V15.1R2_ChR

Product Version

OMC_APPLI V15_01.BR (AVL 23086)


PE_UPGPRECHECK V15_01.E0Hc (AVL 20919)

PE_VERSUPGPRECHECK V15_01.EH9f (AVL 20918)

PE_HSI-P V03_00.E00 (AVL 13343)

8/3/2019 pe-omc-app-018438_0112_en





A.3 DELIVERY FOR V15.1 CL2 / V15.1R2 CL1

Product Version Patch doc. issue Corrected CRs/ Deliveredfeatures

OMC_APPLI V15_01.FR (AVL 24032)

PE/OMC/APP/018438 V01.01

Q01245876-01Q01252014Q01252014-03Q01252718Q01280824-01Q01243900-03Q01287440Q01135458-01Q01186607-02


PE/OMC/APP/018438 V01.01

Q01289182Q01265544Q01258365Q01301782Q01301200Q01308084Q01308089Q01310197

PE_UPGPRECHECK V15_01.E0Hd (AVL 23265)PE/OMC/APP/018438 V01.01

Q01245035Q01245035-03

PE_VERSUPGPRECHECK V15_01.EH9g (AVL 23264)PE/OMC/APP/018438 V01.01

Q01245035-02Q01245035-04

PE_UPG_FW_T3 V02_00.E01 (AVL 22492)PE/OMC/APP/018438 V01.02

Q01202531-01

PE_OSILOGD_PATCH V15_01.E01 (AVL 21099)PE/OMC/APP/018438 V01.02

Q01103886-01

PE_HSI-P V03_01.E00 (AVL 23687)PE/OMC/APP/018438 V01.02

RFF 30156

A.4 PATCH HISTORY FOR V15.1 CL2 / V15.1R2 CL1

Product Version Patch doc. issue Corrected CRs

/ Deliveredfeatures

OMC_APPLI V15_01.HR (AVL 25000)

PE/OMC/APP/018438 V01.05

Q01365703-04Q01355526-01Q01328644-03Q01336165-01RFF 27899

PE_EMERGENCY_PATCH V15_01.E06 (AVL 24750)PE/OMC/APP/018438 V01.05

Q01291382-02Q01330639-02


Q01387113-01

8/3/2019 pe-omc-app-018438_0112_en





A.5 DELIVERY FOR V15.1R2 CL2

Product Version Patch doc. issue Corrected CRs/ Deliveredfeatures

OMC_APPLI V15_01.IR (AVL 25757)PE/OMC/APP/018438 V01.09

Q01408131Q01423174Q00863131-05


Q01338121-01Q01338136-01

A.6 PATCH HISTORY FOR V15.1R2 CL2

Product Version Patch doc. issue Corrected CRs/ Delivered

features

OMC_APPLI V15_01.JR (AVL 26237) PE/OMC/APP/018438 V01.10 Q01479255-03

OMC_APPLI V15_01.KR (AVL 26597) PE/OMC/APP/018438 V01.11 Q01542131-01

OMC_APPLI V15_01.LR (AVL 27450) PE/OMC/APP/018438 V01.12 Q01681763-03

8/3/2019 pe-omc-app-018438_0112_en





ANNEX B: V15.1 POST-CHR CR – CUSTOMER CASE MATRIX

Corrected CRs Customer cases Product GSM/GSM-R

applicableQ01245876-01 051101-38843 OMC_APPLI V15_01.FR (AVL 24032) both

Q01252014 051018-24067 OMC_APPLI V15_01.FR (AVL 24032) both

Q01252014-03 051018-24067 OMC_APPLI V15_01.FR (AVL 24032) both

Q01252718 051108-46152 OMC_APPLI V15_01.FR (AVL 24032) both

Q01280824-01 Not Applicable – Internal CR OMC_APPLI V15_01.FR (AVL 24032) both


Q01287440 Not Applicable – Internal CR OMC_APPLI V15_01.FR (AVL 24032) both

Q01135458-01 Not Applicable – Internal CR OMC_APPLI V15_01.FR (AVL 24032) both


Q01289182 060112-07726 DS_OMC_CIUS V15_01.BV (AVL 21904) both

Q01265544 051129-68066 DS_OMC_CIUS V15_01.BV (AVL 21904) both

Q01258365 Not Applicable – Internal CR DS_OMC_CIUS V15_01.BV (AVL 21904) both






Q01245035 051024-29314 PE_UPGPRECHECK V15_01.E0Hd

(AVL 23265)

both

Q01245035-03 051024-29314 PE_UPGPRECHECK V15_01.E0Hd

(AVL 23265)

both

Q01245035-02 051024-29314 PE_VERSUPGPRECHECK V15_01.EH9g

(AVL 23264)

both

Q01245035-04 051024-29314 PE_VERSUPGPRECHECK V15_01.EH9g

(AVL 23264)

both

Q01202531-01 050817-57875 PE_UPG_FW_T3 V02_00.E01 (AVL 22492) both

8/3/2019 pe-omc-app-018438_0112_en



Q01103886-01 050316-88842 PE_OSILOGD_PATCH V15_01.E01

(AVL 21099)

both

Q01365703-04 060412-05387 OMC_APPLI V15_01.HR (AVL 25000) both

Q01355526-01 Not Applicable – Internal CR OMC_APPLI V15_01.HR (AVL 25000) both



Q01291382-02 051117-56827 PE_EMERGENCY_PATCH V15_01.E06

(AVL 24750)

both

Q01330639-02 060308-67309

060526-52936

PE_EMERGENCY_PATCH V15_01.E06

(AVL 24750)

both

Q01387113-01 060530-55305 PE_EMERGENCY_PATCH V15_01.E07

(AVL 25129)

both

Q01408131 060703-92509 OMC_APPLI V15_01.IR (AVL 25757) both

Q01423174 060703-92509 OMC_APPLI V15_01.IR (AVL 25757) both

Q00863131-05 040310-75408 OMC_APPLI V15_01.IR (AVL 25757) both

Q01338121-01 Not Applicable – Internal CR PE_EMERGENCY_PATCH V15_01.E05

(AVL 24270)

both

Q01338136-01 Not Applicable – Internal CR PE_EMERGENCY_PATCH V15_01.E05

(AVL 24270)

both

Q01479255-03 061017-14372 OMC_APPLI V15_01.JR (AVL 26237) both

Q01542131-01 061130-63099 OMC_APPLI V15_01.KR (AVL 26597) both

Date post:	06-Apr-2018
Category:	Documents
Upload:	rv-anand-kumar
View:	217 times
Download:	0 times

pe-omc-app-018438_0112_en

Documents