OMC Trouble Shooting Guide B9 ed05.pdf

ED05RELEASED CONFIDENTIAL OMC3 B9 Troubleshooting Guidetsg_b9ed5released.doc 3BK 29007 JAAA PWZZA 1/99

All

right

s re

serv

ed. P

assi

ng o

n an

d co

pyin

g of

this

docu

men

t, us

e an

d co

mm

unic

atio

n of

its

cont

ents

notp

erm

itted

with

outw

ritte

nau

thor

izat

ion

from

Evo

lium

Site

TIMIOARAEVOLIUM SAS

Originator

Calin Rusu

OMC B9

TROUBLE SHOOTING GUIDE

System : ALCATEL 900/BSS

Sub-system : OMC

Document Category : TROUBLE SHOOTING GUIDE

PREDISTRIBUTION:

O&M B9 DPM : B. Csillag

VAL : G. Acbard, E. Bruth, A. Alves

OMC : IST, L3Support

ABSTRACT

This document provides the operational workarounds, which can be applied by the Alcatel teams on OMC B9from the first version.

Approvals

Name

App.

Lucian Florin Muntean B. Csillag


All

right

s re

serv

ed. P

assi

ng o

n an

d co

pyin

g of

this

docu

men

t, us

e an

d co

mm

unic

atio

n of

its

cont

ents

notp

erm

itted

with

outw

ritte

nau

thor

izat

ion

from

Evo

lium

REVIEWEd. 01 Proposal 01 29/09/2004 TD/O&M/SYSTEM/2004.232

Ed. 01 Proposal 02 22/10/2004 TD/O&M/SYSTEM/2004.257

Ed. 02 Proposal 01 30/06/2005 TD/MRC/OMT/2005.453



HISTORYEd. 01 Proposal 01 29/09/2004 First proposal

Ed. 01 Proposal 02 22/10/2004 Proposal 02

Ed. 01 Released 11/04/2005 Released







CHANGES SINCE THE LAST EDITION RELEASED

Remained actions pending in the BSSUSM follow-up .....................................................................................46No more free virtual memory (98% used) on HMI due to lss process .............................................................46Full partition due to generation of lss core file under "/" ...................................................................................47ObjectStore cache manager could not be started............................................................................................47Not possible to navigate between USMs from Iconbox 48

B9/B9 OMC-R software upgrade: after CD3 install, Master reboot no possible by "init 6" command .75

Aggregation crash 78


All

right

s re

serv

ed. P

assi

ng o

n an

d co

pyin

g of

this

docu

men

t, us

e an

d co

mm

unic

atio

n of

its

cont

ents

notp

erm

itted

with

outw

ritte

nau

thor

izat

ion

from

Evo

lium

TABLE OF CONTENT1. SCOPE .......................................................................................................................................................7

2. BASIC PROCEDURES..............................................................................................................................82.1 What to do in case of message "NML not available or RNIM not responding".....................................82.2 How to remove BSSIM database without losing data ...........................................................................82.3 How to remove and recreate manually BSSIM database (resolve specific FRs) ...............................122.4 How to stop a systematically crash of RNIM or crash of RNIMPRC ..................................................142.5 How to remove and recreate the RNIM database...............................................................................152.6 Problem occurred on a BSC iN reserved Mutual Exclusion ...............................................................192.7 How to proceed when a BSC stays abnormally busy .........................................................................202.8 Impossible to launch RNUSM: "the user is unknown to the security manager" .................................212.9 Cases of blocked BSSIM/RNIM initialization process........................................................................22

3. OMC3 ADMINISTRATION.......................................................................................................................233.1 How to unlock a locked axadmin user ................................................................................................233.2 Cases of blocked OMC initialization process.....................................................................................243.3 The IconBox starts with NO FAD ........................................................................................................253.4 How to reduce the size of txn.log ........................................................................................................273.5 ObjectStore doesn't start after a reboot or an OMC start ...................................................................283.6 Objecstore is freezed ..........................................................................................................................293.7 Impossible to open SEC for a user different of axadmin ....................................................................313.8 DSMUSM is empty because DSMIM is not running ...........................................................................323.9 DEC ALPHA `Num Lock` selected: Only the mouse is working. ........................................................333.10 It is not possible to do an expoRt from SEC or the SEC import does not work..................................343.11 SECIM DATAbase partially corrupted BUT import/EXPORT is WORKING .....................................353.12 ERROR: Print file failed! When user note field not correctly formatted ..............................................363.13 ALERTERS: formatted alarm export from AS-cuR and AS-HIST not possible ..................................373.14 Solaris 10: problem of colors..............................................................................................................383.15 "The DT messaging system could not be starting, axadmin iconbox cannot be launched.", .............393.18 It's not possible to give a name to a PRC when Verr Num (Num lock) key is activated..........................403.19 Legato backup cannot be re-started in case of failure of "save_pre_legato" script............................413.20 Launch of CRAFT terminal from OMC3 causes several Mozzila error messages ............................423.21 Ports blocked due to repetitive incorrectly terminated actions............................................................433.22 RNUSM freeze on HMI during normal usage .....................................................................................433.23 No error message if the NavServer is down .......................................................................................443.24 STOP/START SEC service.................................................................................................................453.25 False message appears when OMC is started from OSM. ................................................................453.26 Remained actions pending in the BSSUSM follow-up........................................................................463.27 No more free virtual memory (98% used) on HMI due to lss process ................................................463.28 Full partition due to generation of lss core file under "/"......................................................................473.29 ObjectStore cache manager could not be started ..............................................................................473.30 Not possible to navigate between USMs from Iconbox ......................................................................48

4. OMC/BSC COMMUNICATION................................................................................................................49


All

right

s re

serv

ed. P

assi

ng o

n an

d co

pyin

g of

this

docu

men

t, us

e an

d co

mm

unic

atio

n of

its

cont

ents

notp

erm

itted

with

outw

ritte

nau

thor

izat

ion

from

Evo

lium

4.1 Communication to all BSS lost-Nothing happens on the field whereas an action was triggered .......494.2 OMC3 X25 configuration problem.......................................................................................................504.3 How to recover an X25 link when invalid licence number was applied ..............................................51

5. RADIO ......................................................................................................................................................535.1 The "wrong BCCH/BSIC" error appears during a check PRC............................................................535.2 A Cell goes misaligned after an audit..................................................................................................545.3 The Cell/BSC goes misaligned after an activation or modification of the SC .....................................555.4 The Alignment Status of a Cell stays inConfig....................................................................................575.5 Processing Error - ERROR - bssim-5513 : For the cell (lac xxx, ci yyy),there is a reselection found onBSC but not created on omc, with BCCH frequency bbb.................................................................................585.6 WARNING bssim-5529 "For the cell (lac xxx,ci yyy), there is a reselection......................................595.7 ERROR - rnim-1005 : Stubbed activation mode: PRC activation will not be downloaded to any NE.615.8 Wrong license number: crash rnimsc..................................................................................................625.9 Duplication of handovers after Radio upload (RNIM case).................................................................635.10 ERROR RNIM 238 "Warning: the uploaded cell (LAC/CI) cannot be created due to LAC+CI conflict. (Toupload successfully the new cell, the existing cell must bemodified using change LAC-CI).".........................655.11 HOW TO CREATE A BACKUP PRC IF THE BSC TO BE COPIED ARE RESERVED.....................675.12 How to correct inconsistencies for more than 5000 adjacencies........................................................67

6. MLU..........................................................................................................................................................696.1 Several BSS impacted by a MLU session should not be impacted....................................................69

7. OMC3/OMC3 MIGRATION......................................................................................................................707.1 How to manually activate a SC during a migration .............................................................................707.2 How to run installMig.pl again if something goes wrong during the first installMig.pl or MF-start ......717.3 Timer T_i and T9110 equal 0 in the OMC...........................................................................................737.4 During migration B8->B9 same HW/OS the remove of the MFS fails (script removeNMC_MFS.pl) .747.5 During migration B8 to B9 the script HW_declare_BSC_MFS.pl didn't work .....................................747.6 B9/B9 OMC-R software upgrade: after CD3 install, Master reboot no possible by "init 6" command75

8. PERFORMANCE MANAGEMENT..........................................................................................................768.1 Loss of GPRS counters.......................................................................................................................768.2 QoS Analyser:(Line 162 in mdmain.tsl) Caught SIGSEGV signal (#183) error..................................778.3 No more data available for MPM Browser when reboot OMC occurs during PM file transfer............778.4 Aggregation crash ...............................................................................................................................78

9. SUPERVISION.........................................................................................................................................799.1 All the alarms are automatically purged..............................................................................................799.2 Export BSS from BSSusm doesn't work .............................................................................................809.3 Alarm filter not loadable.......................................................................................................................81

10. X-LARGE SPECIFIC..............................................................................................................................8210.1 The procedure of X-Large OMC-R backup doesn`t work ...................................................................8210.2 With a Xlarge, impossible to perform a backup with external and internal tape driver.......................83

11. APPENDIX I : TIMEOUT TABLES ........................................................................................................8411.1 Timeout during a software replacement..............................................................................................84

12. APPENDIX II : SEEK PROBLEMS OF " SLOWNESS OMC ".............................................................85


All

right

s re

serv

ed. P

assi

ng o

n an

d co

pyin

g of

this

docu

men

t, us

e an

d co

mm

unic

atio

n of

its

cont

ents

notp

erm

itted

with

outw

ritte

nau

thor

izat

ion

from

Evo

lium

12.1 Analyse of the problem:.......................................................................................................................8512.2 Analyse of the actions in progress: .....................................................................................................8512.3 check if RNIM is not in automatic situation of restarting: ....................................................................8512.4 Seek of the ' orphans processes' ........................................................................................................8512.5 Control of the number of sessions / users on the HMI / HOST:..........................................................8512.6 Detection of the input of the processes bssim / rnim in flow control: ..................................................8612.7 Check if the level of the traces ' + ' is activated: .................................................................................8612.8 Check if Objecstore is freezed ............................................................................................................86

13. APPENDIX III : OMC3 TOOLS..............................................................................................................8713.1 How to save Cell and BTS names/GPRS configuration .....................................................................87

14. APPENDIX IV : EXPLANATION ABOUT NEW SUBLISTS/FILTERS INSTALLATION (RESTRICTED TOADMINISTRATOR USE OR ALCATEL SUPPORT) ........................................................................................89

15. APPENDIX V : HOW TO HAVE A COMPLETE INFORMATION ABOUT AN ALARM.......................9115.1 Historical alarms information...............................................................................................................9115.2 Current alarms information..................................................................................................................92

16. APPENDIX VI : OMC TRACES .............................................................................................................9316.1 BSSCOMM traces ...............................................................................................................................9416.2 How to look after a flow of IMSI traces?..............................................................................................9616.3 informations needed to analyse a problem of a cell in GSM misaligned state : .................................9616.4 Import/Export traces ............................................................................................................................9716.5 = PRC number same as used for rnimpr traceObjectore traces ..................................................9716.6 How to get ASCII file information about the EML bssim HW audit .....................................................97


All

right

s re

serv

ed. P

assi

ng o

n an

d co

pyin

g of

this

docu

men

t, us

e an

d co

mm

unic

atio

n of

its

cont

ents

notp

erm

itted

with

outw

ritte

nau

thor

izat

ion

from

Evo

lium

ASSOCIATED DOCUMENTS:

[1] OMC3 BSC COMMUNICATION PROTOCOL INVESTIGATION

3BK 29087 GAA FPWZZA

RELATED DOCUMENTS:

[2] OMC3 B8 Troubleshooting guide

3BK 09928 FCAA RJZZA

[3] BSC BASIC TROUBLESHOOTING

8BL146200018PCZZA

[4] MFS B8 TROUBLE SHOOTING GUIDE

3BK 29042 FCAE PWZZA

[5] B8.2-KEY GENERATOR USER MANUAL

3BK174160007RJZZA

[6] MPI75-7/MDR2 B8 A1353-RA SW UPGRADE WITH DATABASE FORMAT CHANGE

3BK174080752RJZZA

[7] MPI75-7/MDR2 B8 A1353-RA SW UPGRADE WITH DATABASE FORMAT CHANGE

3BK174080752RJZZA


All

right

s re

serv

ed. P

assi

ng o

n an

d co

pyin

g of

this

docu

men

t, us

e an

d co

mm

unic

atio

n of

its

cont

ents

notp

erm

itted

with

outw

ritte

nau

thor

izat

ion

from

Evo

lium

1. SCOPE

The aim of this document is to provide hints and workarounds to operator using the B9 OMC3; it is issued fromthe OMC B8 Trouble Shooting Guide

This document is restricted for ALCATEL intern usage, notably for ALCATEL personnel providing onsite supportat customer premises.

The chapters BASIC PROCEDURES and the OMC3 ADMNISTRATION are the stable basic first aids, the otherchapters are supposed to be updated each time new problems will occur.


All

right

s re

serv

ed. P

assi

ng o

n an

d co

pyin

g of

this

docu

men

t, us

e an

d co

mm

unic

atio

n of

its

cont

ents

notp

erm

itted

with

outw

ritte

nau

thor

izat

ion

from

Evo

lium

2. BASIC PROCEDURES

2.1 WHAT TO DO IN CASE OF MESSAGE "NML NOT AVAILABLE ORRNIM NOT RESPONDING"

2.1.1 Reference FR

None

2.1.2 Problem description

DCN, RNUSM or an action in BSSUSM was launched, and there is in the DCN, BSSUM or RNUSM follow up, awarning message indicating NML not available or RNIM not responding

2.1.3 Corrective action

If you have error messages indicating a problem of communication with RNIM or NML when you launch DCN orRNUSM or an action which asks the reservation status of bss and no logical action which could slow down theRNIM process, you can Stop/Start RNIM in DSMUSM.

2.1.4 Problem solved

Not Applicable

2.2 HOW TO REMOVE BSSIM DATABASE WITHOUT LOSING DATA WARNING: This method should be applied by ALCATEL TD or under ALCATEL TD direct control.

ALCATEL-TDpreferred

BE CARREFULL: if you do not use the PRC backup, all the pureGPRS radio parameters will be lost (replaced by the defaultvalue)!

2.2.1 Reference FR

3BKA20FBR079298, 3BKA32CBR102358, 3BKA20FBR121702, 3BKA20FBR122635


The BSC database has been corrupted and the administrator must remove the BSSIM database to recover. Theproblem is that after removing the BSS, the BTS, cells names and ATER GPRS configuration are lost and mustbe reentered manually.


All

right

s re

serv

ed. P

assi

ng o

n an

d co

pyin

g of

this

docu

men

t, us

e an

d co

mm

unic

atio

n of

its

cont

ents

notp

erm

itted

with

outw

ritte

nau

thor

izat

ion

from

Evo

lium


NOTICE: In all the future cases where is mentioned to copy Network Elements (BSCs/Cells) in a PRC, and theseelement cannot be copied because are reserved please see also in this document the points 2.7 How toproceed when a BSC stays abnormally busy (cells aligningUp, aligningDown, misaligned ) to correct thealignment status

The principle is to simulate a move BSC for the corrupted BSS, as following:1) Create a PRC (BSCinitial)including all the cells and the MFS for that BSS and export it to idle export directory number x (where x is aninteger value). That will serve as a backup of the original configuration

2) Copy the exported files to empty import directory y (where y is an integer value):

axadmin@masterHost cd /alcatel/var/share/AFTR/ACIE

axadmin@masterHost cp ACIE_NLexport_Dirx/* ACIE_NLimport_Diry

From the IconBox, launch the Command Mode by using the axadmin user on the master

If BSSIM is crashing at each restart it won't be possible to use this script, see Appendix III: OMC3 How tosave Cell and BTS names/GPRSconfiguration chapter

COMMAND_MODE>omcdo -start EML

3) Type the following command:

COMMAND_MODE>omcdo -cmd 'BSS_moveBSC(bssid,"bssid")'

Where bssid is the id of the BSS whose names should be kept

For example, if the BSC is the BSC 27:

COMMAND_MODE>omcdo -cmd 'BSS_moveBSC(27,"27")'

4) Stop the EML command mode, and close the command window

COMMAND_MODE> omcdo -stop EML

COMMAND_MODE> exit

5) Verify in /alcatel/var/share/AFTR/MISC, that a file bssid.apd.bsc has been created. If not, look in theparam.cfg file of Bssim the value of MoveBscExchangePath, where this file should be created. Forexample:

axadmin@masterHost cd /alcatel/var/share/AFTR/MISC

axadmin@masterHost ls

27.apd.bsc

This file will be taken into account during next discover.

Note: if the error message "errorCode 1507: SS Migration: cannot retrieve MasterFile name. Cannot receiveactivateIntermediateReport until SW audit completed!" appears don't worry, it is a normal message thatmeans that no SW Replacement session is running.

6) Note the following parameters from the DCN window: (the BSCID bssid should be greater or equal to BSC_LOWER_ID in the/alcatel/omc3/rn/im/conf/param.cfg. If it not the case, then update this file and stop/start rnimsc),


All

right

s re

serv

ed. P

assi

ng o

n an

d co

pyin

g of

this

docu

men

t, us

e an

d co

mm

unic

atio

n of

its

cont

ents

notp

erm

itted

with

outw

ritte

nau

thor

izat

ion

from

Evo

lium

, , , , , , , ,, , ,

7) Stop the BSS measurements

8) Force Remove the BSS (in DCN). If MFSUSM is open, it enters in LIMITED MODE! It is better to closed it, oneach workstation.

9) Re-declare BSS:

From the IconBox, launch the Command Mode by using the axadmin user

COMMAND_MODE>omcdo -start OAM

COMMAND_MODE>omcdo -cmd 'OMC_declareBSSWithTsapSsapBscId( , "","","",,"","","","","","",,,None,"no")'

Example: for the "bss_13" on the host "jenlain" with 2 links:

COMMAND_MODE> omcdo -cmd'OMC_declareBSSWithTsapSsapBscId(13,"bss_13","jenlain","B8",0,"4254","4253","366963","4254","4253"," 366950 ",0,1,None,"no")'

COMMAND_MODE>omcdo -stop OAM

COMMAND_MODE>exit

Example: for the "bss_13" on the host "jenlain" with 1 link:

COMMAND_MODE> omcdo -cmd'OMC_declareBSSWithTsapSsapBscId(13,"bss_13","jenlain","B8",0,"4254","4253","366963","","","",0,1,None,"no")'

COMMAND_MODE>omcdo -stop OAM

COMMAND_MODE>exit

10) If needed, restart BSSUSM for that BSC and open the Discover window (Audit menu). Wait until the Statusis Reporting .

11) Create a new PRC (BSCfinal) including the MFS and all cells for the BSS that will serve as a reference forthe new configuration and export it to idle export directory number x. x may be the same number like the onefrom step 1.

12) Run the script to merge the BSCinitial and BSCfinal PRCs (mfsId must be replaced with the numerical valuefor the MFS Id, y with the number from step 2):

axadmin@host /alcatel/omc3/ei/script/moveBscInterOmc.pl x y mfsId

Only if the SMSCB is activated, in order to avoid disabling the SMSCB

Create the following file call for example f.txt which contains only the 2 following lines withoutblank spaces but with tab spaces:

rnlAlcatelBSC->CBC_PASSWORD

rnlAlcatelBSC->CBC_OPERATOR

where -> means tabulation


All

right

s re

serv

ed. P

assi

ng o

n an

d co

pyin

g of

this

docu

men

t, us

e an

d co

mm

unic

atio

n of

its

cont

ents

notp

erm

itted

with

outw

ritte

nau

thor

izat

ion

from

Evo

lium

Launch the following command from the /alcatel/var/share/AFTR/ACIE/ directory

/alcatel/omc3/ei/script/processCsv.pl f.txt /alcatel/var/share/AFTR/ACIE/ACIE_NLimport_Diry

Endif

13) Import the result (Population/Import menu) from directory y into the BSCfinal PRC.

14) Activate the PRC (GPRS is locked on the BSC as a result).

15) perform a Resynchronize GPRS on the BSC, then MFSUSM can be opened again in normal mode.

16) In order to allow GPRS traffic on this BSC, trigger on BSC "Unlock_GPRS" from RNUSM .

17) Start the BSS measurements which has been stopped in 6)

18) Trigger the RNUSM query adjacencies inconsistencies

WARNING: the PRCs previously created that contain cells of the removed BSC and/or incoming oroutcoming adjacencies are no longer usable, except applying the script moveBscInterOmc (See point 8of this paragraph)

WARNING: If the re-declared BSC belonged to a specific OAD, this information is lost and operators using thisOAD cannot access to the BSC anymore, so the BSCid has to be add again in the OAD via SECusm

2.2.4 Correction

Not Applicable.


All

right

s re

serv

ed. P

assi

ng o

n an

d co

pyin

g of

this

docu

men

t, us

e an

d co

mm

unic

atio

n of

its

cont

ents

notp

erm

itted

with

outw

ritte

nau

thor

izat

ion

from

Evo

lium

2.3 HOW TO REMOVE AND RECREATE MANUALLY BSSIMDATABASE (RESOLVE SPECIFIC FRS)

2.3.1 Reference FR

3BKA25FBR127388


The procedure to remove and recreate BSSIM database is used to solve specific problems:

- FR A25/118879 : not valide alarm at OMC

- FR A25/106991 : Abis TP locked

Note that this procedure does not modify the RNIM database part, which is done by using the "how to removeBSSIM database without loosing any data" procedure.


Prerequisite:

Cells of the concerning BSC must be aligned or misaligned.

No on-going action at equipment level for that BSC, and not at all at radio level.

Method:

Generate the apd and odmc files for this bss,The script must be launched on the host where the corresponding bssim process is running: master or agent (for

example if you have a bssim runnning on an agent host, run the script on that agent and you will also

find the output files in the agent host).

The script receives as input a list of BSC Id (ex : 1, 5, 8), or a range of BSC Ids (1-20).

root@host$ cd /alcatel/omc3/bss/im/9/script

root@host$ ./remove_db.pl

The log of the script execution could be found in /alcatel/var/maintenance/log/remove_db.log. The apd and odmc files are archived for each bss in /alcatel/var/maintenance/hist/.apd.yymmdd.hhmmss.tar.gz

Stop BSSIM by using DSM. Remove the database:axadmin@host /opt/ODI/OS6.2/ostore/bin/osrm /alcatel/base/bss/im/data/db/DB_BSS_"bscid"_*.db

Restart BSSIM and perform a BSS Discover When the discover is finish run the scripts:axadmin@host /alcatel/omc3/migration/script/createOdmc.pl "bscid"

Clean up, command from master hostroot@master /alcatel/omc3/migration/script/cleanUp.pl


All

right

s re

serv

ed. P

assi

ng o

n an

d co

pyin

g of

this

docu

men

t, us

e an

d co

mm

unic

atio

n of

its

cont

ents

notp

erm

itted

with

outw

ritte

nau

thor

izat

ion

from

Evo

lium

- Trigger a BSS logical Audit from RNUSM.

WARNING: the PRCs previously created that contain cells of the removed BSC and/or incoming oroutcoming adjacencies are no longer usable, except applying the script moveBscInterOmc as describedin the "How to remove BSSIM database without losing data chapter).


Not applicable.


All

right

s re

serv

ed. P

assi

ng o

n an

d co

pyin

g of

this

docu

men

t, us

e an

d co

mm

unic

atio

n of

its

cont

ents

notp

erm

itted

with

outw

ritte

nau

thor

izat

ion

from

Evo

lium

2.4 HOW TO STOP A SYSTEMATICALLY CRASH OF RNIM OR CRASHOF RNIMPRC

2.4.1 Reference FR

None


Symptom: the RNIM crashes systematically at the restart or there is a crash of RNIMPRC forexample during a copy of cells in PRC (example there is some target HO unsolved).

The RNIMSC database is probably corrupted.


1) Go to /alcatel/base/rn/im/data/ and type command

axadmin@host echo > FIXDATABASE

Verify that the file FIXDATABASE is created.

2) Start the RNIM process.

If RNIM crashes again, you must delete the database of RNIM see the following section How to remove andrecreate the RNIM database.

If RNIM is restarted usually do:

axadmin@host cat /alcatel/var/maintenance/trace/FIXDATABASE.report

In the FIXDATABASE.report you will see the troubles encountered and the way the rnim fixed them (e.g.Duplicate cells with the same LAC/CI found. Corrective actions: to correct the situations we will delete one cell).This is only informative and is not requested an action from you.

2.4.4 Correction

Not Applicable


All

right

s re

serv

ed. P

assi

ng o

n an

d co

pyin

g of

this

docu

men

t, us

e an

d co

mm

unic

atio

n of

its

cont

ents

notp

erm

itted

with

outw

ritte

nau

thor

izat

ion

from

Evo

lium

2.5 HOW TO REMOVE AND RECREATE THE RNIM DATABASEWARNING: This action should be done by ALCATEL TD or under ALCATEL TD direct control.

ALCATEL-TD preferred

2.5.1 Reference FR

3BKA32FBR106330, 3BKA20FBR118323

Each case is addressed and corrected. This section is used to address the "not yet encountered cases".


The rnim database can become corrupted and the administrator should then remove the RNIM database. Suchaction is done as a "last resort". The sections which implies the rnusm window (e.g. create a backup PRC) canbe perform only if the rnim process is stable.

If for any reasons it is necessary to remove a nameserver database: remove also the rnimsc + EVERY PRCdatabase.

WARNING: all the external cells not involved in the adjacencies will be lost; all the internal cells where an uploadhas not been performed before will be misaligned, and with parameters RACH_BUSY_THRES,THR_CCCH_LOAD, CCCH_LOAD_MEAS_PERIOD empty. The workaround for the second problem is toperform an Upload radio parameters from RNUSM.


The remove action must follow a specific procedure to save the BSS and to allow a resynchronization from rnimto the databases of bssim.

Save NAMESERVER and RNIM traces for further analysis. To do so, proceed as follows:

Use the message retrieval tool from the Log Viewer (Full Log) and perform a "Logs Merge on demand".

axadmin@host$ cd ~ (so you go to your home directory)

axadmin@host$ mkdir trace_dir (for example)

axadmin@host$ cd trace_dir

axadmin@host$ cp /alcatel/var/maintenance/trace/rnim* .

axadmin@host$ cp /alcatel/var/maintenance/trace/nameserver* .

axadmin@host$ cp /alcatel/var/maintenance/log/* .

axadmin@host$ cp R /alcatel/var/maintenance/log/SAVEDLOG/ .

axadmin@host$ cp /alcatel/var/maintenance/hist/rnim* .

axadmin@host$ cp /alcatel/var/maintenance/hist/nameserver* .

Introduce a DAT tape in the streamer of the host in order to backup the logs retrieved above.

axadmin@host$ tar -cv *.*


All

right

s re

serv

ed. P

assi

ng o

n an

d co

pyin

g of

this

docu

men

t, us

e an

d co

mm

unic

atio

n of

its

cont

ents

notp

erm

itted

with

outw

ritte

nau

thor

izat

ion

from

Evo

lium

First of all, create a backup PRC and copy in it all MFS/BSC/Cells (internal and external)

0) Export all the SC, in the directory number x

Run the script buildAlignStatus (in the directory /alcatel/omc3/migration/script/).

axadmin@host$ ./ buildAlignStatus.pl d x

where x is the export directory number

1) Under /alcatel/omc3/rn/im/conf create 3 files called omc3_list_of_bss, omc3_list_of_mfs and the empty fileomc3_local_activate.

2) Edit the file omc3_list_of_bss and complete it as follows:

One line for each bss. Each line following the model

bssId -> bssName -> bssRelease.

where -> means tabulation,

bssId is the id of the BSS under DCN (id present in the left part of the window different from the Node Id)

bss1name is the name given by the operator under DCN,

bssRelease is the mib version of the BSC (B8 or B9).

The file is built in the increasing order of bssId. As an example:

1 -> bss1name -> B8

2 -> bss2name -> B9

If you choose to remove also the nameserver database, then respect exactly the bssId and the bssname asdefined in /alcatel/var/share/dsm/programs.cfg with and

Endif

3) Edit the file omc3_list_of_mfs and complete it as follows:

one line for each mfs. Each line following the model

mfsId -> mfsName.

where -> means tabulation,

mfsid is the id of the mfs under DCN (MFS Identifier, different from the Node Identifier).

mfsname is the name given by the operator under DCN.

The file is built in the increasing order of mfsId. As an example:

15 -> mfs15name

22 -> mfs22name

Check that all the mfsId are in the range [MFS_LOWER_ID, MFS_UPPER_ID] (these 2 values are defined in/alcatel/omc3/rn/im/conf/param.cfg)

4) Under DSM, stop the RNIM process.

If you choose to remove also nameserver database, stop also the nameserver process

End If

5) Go to /alcatel/base/rn/im/data/ and type command


All

right

s re

serv

ed. P

assi

ng o

n an

d co

pyin

g of

this

docu

men

t, us

e an

d co

mm

unic

atio

n of

its

cont

ents

notp

erm

itted

with

outw

ritte

nau

thor

izat

ion

from

Evo

lium

If you choose to remove only the rnim database, then

axadmin@host$ /opt/ODI/OS6.2/ostore/bin/osrm rnim.db1

Verify that the file rnim.db1 has disappeared.

Else (you have chosen to remove the rnim database and the nameserver database)

axadmin@host$ /opt/ODI/OS6.2/ostore/bin/osrm rnim.db*

Verify that all the rnim.db* have disappeared.

axadmin@host$ cd /alcatel/base/nameserver/data/

axadmin@host$ /opt/ODI/OS6.2/ostore/bin/osrm nameserver.db

End If

6) Under DSM,If you have chosen to remove also nameserver database, start the nameserver process

End If

Start the RNIM process and then launch RNUSM through the ICONBOX.

The resynchronization happens then (the launch is slower than usually) and the radio configuration is uploaded.

WARNING: the information mfsi is associated with bssj is lost during the resynchronization so:

Move the exported files to empty import directory y (where y is an integer value):

axadmin@host$ cd /alcatel/var/share/AFTR/ACIE

axadmin@host$ cp ACIE_NLexport_Dirx/* ACIE_NLimport_Diry/

Under /alcatel/var/maintenance/trace/ create the file called neIdMappingEdit this file and complete it as follows:

BSC -> bssId -> bssId

The file is built in the increasing order of bssId. As an example:

BSC -> 1 -> 1

BSC -> 100-> 100


Export again the SC that will serve as a reference for the new configuration and export it to idle exportdirectory number z.

Run the script to merge the BSC/MFS associations, GPRS values... stored in ACIE_NLimport_Diry andthe new PRC value:

axadmin@host$ /alcatel/omc3/ei/script/mergeRadioInXLconcentration.pl z y/alcatel/var/maintenance/trace/neIdMapping

The External Cell will not be created in the PRC

If for one BSC the SMSCB is activated (in order to avoid disabling the SMSCB)


All

right

s re

serv

ed. P

assi

ng o

n an

d co

pyin

g of

this

docu

men

t, us

e an

d co

mm

unic

atio

n of

its

cont

ents

notp

erm

itted

with

outw

ritte

nau

thor

izat

ion

from

Evo

lium

Create the following third file call for example f.txt which contains only the 2 following lines withoutblank characters but tab characters:

rnlAlcatelBSC->CBC_PASSWORD

rnlAlcatelBSC->CBC_OPERATOR


Launch the following command

/alcatel/omc3/ei/script/processCsv.pl f.txt /alcatel/var/share/AFTR/ACIE/ACIE_NLimport_Diry

End of case of SMSCB activated

7) Run the script mergeGPRS (in the directory /alcatel/omc3/ei/script/).

axadmin@host$ ./ mergeGPRS.pl y

where y is the final import directory number

8) Create and open backup PRC

Import the result (Population/Import menu) from directory y into the final backup PRC.

9) then activate the PRC and resynchronize the MFS(s).

10) remove files omc3_list_of_bss, omc3_list_of_mfs and omc3_local_activate

1) launch as root the cleanUp script (in directory /alcatel/omc3migration/script)

root@host# cd /alcatel/omc3/migration/script/cleanUp.pl

root@host# ./cleanUp.pl


Not Applicable


All

right

s re

serv

ed. P

assi

ng o

n an

d co

pyin

g of

this

docu

men

t, us

e an

d co

mm

unic

atio

n of

its

cont

ents

notp

erm

itted

with

outw

ritte

nau

thor

izat

ion

from

Evo

lium

2.6 PROBLEM OCCURRED ON A BSC IN RESERVED MUTUALEXCLUSION

2.6.1 Reference FR

None


Symptom: the discover is refused with an error message (this problem can also happen for othersactions).

Analysis: The customer wants to do an action on a BSC but the reservation Status of this BSC staysbusy even if nothing happens.


The workaround depends of what is displayed in BSSUSM follow up when trying to trigger a discover; followingcases have been noticed:

1) "BSC is already reserved by RNL. Please try again later.:

In this case, wait 1 minute, then just try to trigger the discover once again. It should be unlocked the second time.If not please report to the "3)" and apply the described workaround.

2) "BSC is already reserved by [message]." where message is like "discover on going, sw activate on going":

In this case, if your SW replacement status is idle, just STOP/START BSSIM. It will be unlocked.

3) "SC is already reserved by RNL. Please try again later.:

In such a case there are three possibilities:

- remove the BSS, which will cause a loss of Supervision Outage during approximately 15 minutes(to do, please report to "How remove BSSIM database without losing data " chapter).

- remove the RNIM database, which will cause a partial loss of the GPRS Configuration and a lossof the Radio Supervision for up to 1 hour depending of the amount of cells in the OMC(to do, pleasereport to "How remove and recreate the RNIM database" chapter).

-

2.6.4 Correction

Not Applicable


All

right

s re

serv

ed. P

assi

ng o

n an

d co

pyin

g of

this

docu

men

t, us

e an

d co

mm

unic

atio

n of

its

cont

ents

notp

erm

itted

with

outw

ritte

nau

thor

izat

ion

from

Evo

lium

2.7 HOW TO PROCEED WHEN A BSC STAYS ABNORMALLY BUSY

2.7.1 Reference FR

None


Symptom: In the RNUSM window, one or several BSC stay busy: the reservationStatus of theBSC(s) stays at the state busy.

Analysis: Depends of the alignmentStatus of the BSC(s), in the same RNSUM window.


There are three cases, depending of the alignmentStatus of the BSC:

1) If it is aligningDown:

stop/start the rnim process in the DSM window (be sure before stopping the process that no otherBSS are working, i.e. the reservationStatus should be Idle). The alignmentStatus should change afterthe defenceAligneDownTimeout defined in /alcatel/omc3/rn/im/conf/param.cfg (default value = 1hour) Ifit doesn't succeed, stop/start the impacted bssim process in the DSM window.

If it doesn't succeed, please report How to remove BSSIM database without losing data section toremove the BSSIM database.

2) If it is aligningUp:

- check the time-out logicalparm_display has expired (default value 3 minutes - See Appendix 1),stop/start the impacted bssim process in the DSM window.

If it doesn't succeed, please report to How to remove BSSIM database without losing data sections toremove the BSSIM database.

3) If it is aligned or misaligned: remove the BSSIM database: to do, please report to How to remove BSSIMdatabase without losing data section.

2.7.4 Correction

Not Applicable


All

right

s re

serv

ed. P

assi

ng o

n an

d co

pyin

g of

this

docu

men

t, us

e an

d co

mm

unic

atio

n of

its

cont

ents

notp

erm

itted

with

outw

ritte

nau

thor

izat

ion

from

Evo

lium

2.8 IMPOSSIBLE TO LAUNCH RNUSM: "THE USER IS UNKNOWN TOTHE SECURITY MANAGER"

2.8.1 Reference FR

None


Symptom: the Iconbox seems ok, but RNUSM does not start. The following message is displayed: "the user isunknown to the security manager".

2.8.3 Workaround

1) Edit the $LANG variable ("echo $LANG"). If there is something else than "C" or , thenthere is a problem of language configuration. The OMC application automatically replaces all thestring by blank.

- If the host was just installed, it is because the language parameter was badly set. In this casereinstall with special attention to the language. Reinstall beginning with CD 1. All is explained in themethod.

- If the host worked before, but does not work anymore the problem comes from the login panel. Onthis panel there is a menu option/language. C_____Posix must be selected.

If not, select it and log on again.

2) If none of the above workarounds are operational, add two variables in all param.cfg of the host(rnusm,bssusm,DCN,rnim bssim(7 and 8), bsscomm ) : CO_USE_UTF8 CO_USE_I18N. Thisvariable is boolean and must be set to False. For instance:

axadmin@host cd /alcatel/omc3/bss/im/9/conf

axadmin@host vi param.cfg

In the file, this parameter will be added at the end of the COMMON VARIABLES

/COMMON VARIABLES

o (to add a line and to be in insert mode)

CO_USE_UTF8 CO_USE_I18N -> "TRUE"

Where -> means tabulation

2.8.4 Correction

Not Applicable.


All

right

s re

serv

ed. P

assi

ng o

n an

d co

pyin

g of

this

docu

men

t, us

e an

d co

mm

unic

atio

n of

its

cont

ents

notp

erm

itted

with

outw

ritte

nau

thor

izat

ion

from

Evo

lium

2.9 CASES OF BLOCKED BSSIM/RNIM INITIALIZATION PROCESS

2.9.1 Reference FR

None


The BSSIM/RNIM initialization process stays blocked because there is a problem with Objectstore.

Symptom: After a start of the OMC3 application, via DSM, we launch RNUSM (or DCN) but RNUSM (or DCN)can t contact RNIM.

In the files /alcatel/var/maintenance/trace/rnim.err and /alcatel/var/maintenance/trace/bssim.err it can be seen thereference to the Objectstore problem.


1) Stop the part application via DSMUSM

2) Stop Objectstore in the part Platform

3) Do the command as axadmin

#axadmin@host$ ps ef | grep ODI

If you find a process, log as root and kill 9 this process

4) Restart Objectstore via DSMUSM

5) Restart the part Application vi a DSMUSM


Not applicable.


All

right

s re

serv

ed. P

assi

ng o

n an

d co

pyin

g of

this

docu

men

t, us

e an

d co

mm

unic

atio

n of

its

cont

ents

notp

erm

itted

with

outw

ritte

nau

thor

izat

ion

from

Evo

lium

3. OMC3 ADMINISTRATION

3.1 HOW TO UNLOCK A LOCKED AXADMIN USER

3.1.2 Reference FR

3BKA20FBR164745


This problem occurs in the 2 following cases:

After three attempts to log with a wrong password

Aiming of an outdated account (in such a case, the user is not seen "locked").


A user axadmin can be unlocked by the following command:

Log in as root on the station.

# /alcatel/omc3/bin/ unlockaccount -l axadmin

WARNING: this action should be done only on Master


Not Applicable


All

right

s re

serv

ed. P

assi

ng o

n an

d co

pyin

g of

this

docu

men

t, us

e an

d co

mm

unic

atio

n of

its

cont

ents

notp

erm

itted

with

outw

ritte

nau

thor

izat

ion

from

Evo

lium

3.2 CASES OF BLOCKED OMC INITIALIZATION PROCESS

3.2.1 Reference FR

3BKA32FBR088945


The OMC initialization process stays blocked on the script /etc/rc2.d/S72inetsvc.

Symptom: in boot sequence, the master station is not able to resolve its own address from its hostname, thus theboot sequence is blocked.


Check the /etc/ nsswitch.conf file.

axadmin@host$vi nsswitch.conf

In nsswitch.conf a line "hosts: nis files" must be present, in this line invert order of resolutions, as following:replace the line "hosts: nis files [dns] " by the line "hosts: files nis [dns] . In case the customer has introducedDNS, at the same line, complete the DNS configuration by adding dns in nsswitch.conf

- Reboot the OMC (logged as root):

# init 6


Not Applicable (FR CLOSE REJECT)


All

right

s re

serv

ed. P

assi

ng o

n an

d co

pyin

g of

this

docu

men

t, us

e an

d co

mm

unic

atio

n of

its

cont

ents

notp

erm

itted

with

outw

ritte

nau

thor

izat

ion

from

Evo

lium

3.3 THE ICONBOX STARTS WITH NO FAD

3.3.1 Reference FR

3BKA20FBR108030


Symptom: When the Iconbox is launched, it contains only a grayed ICON called NO FAD Declared.

3.3.3 Workaround

Try the following workarounds, in that order.

1) If the problem occurs just after an OMC reboot, it can be that the OMC has not finished its restartprocedure. Close the Iconbox, wait a few minutes, and retry.

2) There are 2 cases:

- If the user whose iconbox is empty is axadmin: launch the script restore-sec.pl (in the directory/alcatel/omc3/sec/script/).

axadmin@host$ cd /alcatel/omc3/sec/script/

axadmin@host$ ./restore-sec.pl

This script will give back to axadmin its own profile under SEC (axadmin_special_profile).It will alsorecreate the user axadmin, if it has been destroyed (by a delete user).

- If the user whose iconbox is empty is not axadmin: Check (as axadmin) in SECUSM, that the user hasa profile assigned.

- You can see this under the Operator tab in SECUSM window.Click on the concrete operator, on theright side, you can see the profiles of this operator

WARNING: If only the profile of axadmin has been destroyed (and not the user), some errormessages will appear (it tries to re-create the user). It doesn't matter.

The specified identifier already exist

If there is no way to launch the script as axadmin (no window available) log in as a new user. Then:

User1@host$ su axadmin

axadmin@host$ cd /alcatel/omc3/sec/script/

axadmin@host$./restore-sec.pl

3) Check osmd is running (under UNIX)

axadmin@host ps -aef | grep osmd

Check if lss is running (in DSMUSM). (process must be green)

Check sec service is running

Su


All

right

s re

serv

ed. P

assi

ng o

n an

d co

pyin

g of

this

docu

men

t, us

e an

d co

mm

unic

atio

n of

its

cont

ents

notp

erm

itted

with

outw

ritte

nau

thor

izat

ion

from

Evo

lium

#svcs | grep sec7

You should see: online date-of-start svc:/network/ldap/sec7:default

Note: The lss and osmd must be running on the HMI, the slave and the master. The sec servermust be running on the master only.

4) Check the name of the user with Unix command "whoami" or "id". (We encountered some casewhere "axadmin" was seen as "#axadmin).

If this is the case and if you are on a HMI check if the "wrong" user has an entry to the file /etc/passwd. If sodelete the concerned line (but on the HMI only) as root.

# vi /etc/passwd

3.3.4 Correction

Not Applicable.


All

right

s re

serv

ed. P

assi

ng o

n an

d co

pyin

g of

this

docu

men

t, us

e an

d co

mm

unic

atio

n of

its

cont

ents

notp

erm

itted

with

outw

ritte

nau

thor

izat

ion

from

Evo

lium

3.4 HOW TO REDUCE THE SIZE OF TXN.LOG

3.4.1 Reference FR

None


Symptom:

/alcatel/var is saturated (95% of the disk space is full)

To see the load of your fileset, type the command df k


1) You stop the part Application in DSMUSM2) As root, launch the command :

/opt/ODI/OS6.2/ostore/bin/ossvrchkpt

3) Stop Objectstore in the part Platform in DSMUSM4) As root, launch the command :# /opt/ODI/OS6.2/ostore/lib/osserver i p /etc/opt/ODI/OS6.2/server_parameters

5) Start Objectsore via DSMUSM6) Restart the part Application via DSMUSM


Not applicable


All

right

s re

serv

ed. P

assi

ng o

n an

d co

pyin

g of

this

docu

men

t, us

e an

d co

mm

unic

atio

n of

its

cont

ents

notp

erm

itted

with

outw

ritte

nau

thor

izat

ion

from

Evo

lium

3.5 OBJECTSTORE DOESN'T START AFTER A REBOOT OR AN OMCSTART

3.5.1 Reference FR

None


Symptom: After a reboot of the station or after a Stop/Start of the OMC3, Objectstore cannot restart (the processstays red in DSMUSM).

Analysis: Those are problems with the cache Manager.


Type the following commands (as axadmin) on the master (is the OMC is XLARGE this command can betriggered, on the agent stations):

axadmin@host$ cd /opt/ODI/OS6.2/ostore/bin/

axadmin@host$ ./oscmrf


Not applicable.


All

right

s re

serv

ed. P

assi

ng o

n an

d co

pyin

g of

this

docu

men

t, us

e an

d co

mm

unic

atio

n of

its

cont

ents

notp

erm

itted

with

outw

ritte

nau

thor

izat

ion

from

Evo

lium

3.6 OBJECSTORE IS FREEZED

3.6.1 Reference FR

Not applicable


Symptom:

Bssim and rnim are blocked, impossible to create new PRC

This kind of problem could occur just after or during an OMC backup or just after a crash disk.


You can trigger the following command:

axadmin@host$ ps -ealf | grep store

8 S root 1613 1516 0 41 20 6214a8e0 1735 ef30de84 Aug 31 ? 1:01/opt/ODI/OS6.2/ostore/lib/oscmgr6 daemon 10

8 S root 1277 1 0 41 20 6214b660 49810 ef30de84 Aug 31 ? 30:33/opt/ODI/OS6.2/ostore/lib/osserver

When there is the 'T' on the second colon instead of S, you have to kill the process osserver with the option -CONT

root@host$ kill - CONT


Not applicable


All

right

s re

serv

ed. P

assi

ng o

n an

d co

pyin

g of

this

docu

men

t, us

e an

d co

mm

unic

atio

n of

its

cont

ents

notp

erm

itted

with

outw

ritte

nau

thor

izat

ion

from

Evo

lium


All

right

s re

serv

ed. P

assi

ng o

n an

d co

pyin

g of

this

docu

men

t, us

e an

d co

mm

unic

atio

n of

its

cont

ents

notp

erm

itted

with

outw

ritte

nau

thor

izat

ion

from

Evo

lium

3.7 IMPOSSIBLE TO OPEN SEC FOR A USER DIFFERENT OFAXADMIN

3.7.1 Reference FR

3BKA20FBR084310


Symptom: a user which just has been created with the right on SEC is not able, in remote login, to open theAccess Rights Definition (SEC) window in the ICONBOX

Analysis: after a user creation files .dtprofile and .profile are only created at the first CDE login.


Both files .dtprofile and .profile are to be copied from /alcatel/var/home/axadmin to the new user home directoryfor using this user on ssh as soon as the normal CDE login has never been performed.


Not applicable


All

right

s re

serv

ed. P

assi

ng o

n an

d co

pyin

g of

this

docu

men

t, us

e an

d co

mm

unic

atio

n of

its

cont

ents

notp

erm

itted

with

outw

ritte

nau

thor

izat

ion

from

Evo

lium

3.8 DSMUSM IS EMPTY BECAUSE DSMIM IS NOT RUNNING

3.8.1 Reference FR

None


Symptom: DSMUSM stays empty.

Analysis: dsmim is not running on the master.


If dsmim is not running on the master:

-look in the trace (dsmim.out) why it does not start.

axadmin@host$ cd /alcatel/var/maintenance/trace

axadmin@host$ vi dsmim.out

Note: dsmim should be automatically started by the inittab. Probably there is a syntax problem in the DSMconfiguration files. The reason is explained in the trace

- check if some definitions are not duplicated in hosts.cfg or imsecurity.cfg.

axadmin@host$ cd /alcatel/var/share/dsm/

axadmin@host$ vi hosts.cfg

axadmin@host$ vi imsecurity.cfg.

- Once the files are ok, log in as root

# init q

The init q launches the inittab, which launch dsmim.


Not applicable.


All

right

s re

serv

ed. P

assi

ng o

n an

d co

pyin

g of

this

docu

men

t, us

e an

d co

mm

unic

atio

n of

its

cont

ents

notp

erm

itted

with

outw

ritte

nau

thor

izat

ion

from

Evo

lium

3.9 DEC ALPHA `NUM LOCK` SELECTED: ONLY THE MOUSE ISWORKING.

3.9.1 Reference FR

3BKA32FBR114088


DEC ALPHA SPECIFIC PROBLEM :

When setting the `Num Lock` function on the keyboard (to have access to numbers) the keyboard doesnt workin most of the OMC Window. Only the mouse is working.

For example :

1)In SECUSM window : impossible to set the "OAD elementary" name and the "profile"

name during the "elementary OAD" and "profile" creation.

2)In DCN window : impossible to set the name of the BSS (or MFS) during the 'BSS

creation' (or MFS creation).

All the characters typed on the keyboard are not displayed in the textField when setting

the name.

3) In BSS view window : impossible to set the name of the ODMC campaign and the

start/end date and the start/end time.


unset the `Num Lock`.


Not applicable.


All

right

s re

serv

ed. P

assi

ng o

n an

d co

pyin

g of

this

docu

men

t, us

e an

d co

mm

unic

atio

n of

its

cont

ents

notp

erm

itted

with

outw

ritte

nau

thor

izat

ion

from

Evo

lium

3.10 IT IS NOT POSSIBLE TO DO AN EXPORT FROM SEC OR THE SECIMPORT DOES NOT WORK

3.10.1 Reference FR

Not applicable


The SEC database is corrupted


BE CARREFULL: by using this method, all operator's information will be lost. It is initialized the default and initialconfiguration i.e. the OMC-R users defined in OSM, will be no more accessible from SEC-USM.

remove all SEC database as root user: su

#/alcatel/omc3/sec/script/clean_secldap.pl

Stop SEC service #svcadm disable svc:/network/ldap/sec7:default

Start SEC service #svcadm enable svc:/network/ldap/sec7:default

Perform:#/alcatel/omc3/sec/script/restore_sec.pl


Not applicable


All

right

s re

serv

ed. P

assi

ng o

n an

d co

pyin

g of

this

docu

men

t, us

e an

d co

mm

unic

atio

n of

its

cont

ents

notp

erm

itted

with

outw

ritte

nau

thor

izat

ion

from

Evo

lium

3.11 SECIM DATABASE PARTIALLY CORRUPTED BUTIMPORT/EXPORT IS WORKING

3.11.1 Reference FR

Not applicable


The base is partially corrupted (export secim database works), so we will modified the export, remove the baseand import in order to have a clean configuration.


1)Uncomment (remove all the "#" characters) the 2 following lines in /alcatel/omc3/sec/data/secim/param.cfg :

### EXPORT_PATH_TOP "/alcatel/omc3/sec/data/repository/secim-exports"

### POPULATION_PATH "/alcatel/omc3/sec/data/repository/population"

1) Stop/Start SECIM from DSM-USM

2) /alcatel/omc3/sec/script/acdbm -export fileExport

3) remove all SEC database : /alcatel/omc3/sec/data/repository/secim-database/*.db

4) Check the /alcatel/omc3/sec/data/repository/secim-exports perform/fileExport file, there should be norepetition string

5) /alcatel/omc3/sec/script/acdbm -from /alcatel/omc3/sec/data/repository/secim-exports/fileExport

6) Comment it back (add the "#" characters at the beginning of the lines) the 2 following lines:

### EXPORT_PATH_TOP "/alcatel/omc3/sec/data/repository/secim-exports"

### POPULATION_PATH "/alcatel/omc3/sec/data/repository/population"

6) restart icon box to update the new re-added FAD

6) Stop/Start SECIM from DSM-USM


All

right

s re

serv

ed. P

assi

ng o

n an

d co

pyin

g of

this

docu

men

t, us

e an

d co

mm

unic

atio

n of

its

cont

ents

notp

erm

itted

with

outw

ritte

nau

thor

izat

ion

from

Evo

lium

3.12 ERROR: PRINT FILE FAILED! WHEN USER NOTE FIELD NOTCORRECTLY FORMATTED

3.12.1 Reference FR

3BKA20FBR109992


From the AS current USM, More information window, on the "output" button and print menu, the operator is ableto request the print of an alarm in HTML format.

The message "Print file failed!" is displayed with the following characters:

Characters @ (without character \ before) is present in the user note field (except at the end of this field)

Characters \ (without character \ before) is present at the end of the User Note field

There is the following specific behavior with the 2 following characters:

If the characters $ is present, the next word will be not present in the html file

If the characters \ is present, the next character will be not present in the html file.


Remove or move the special characters @ \ $ in user note field, in order to get correct html file:

If you need to print these 3 characters do the following actions in the User Note field:

Replace @ by \@

Replace $ by \$

Replace \ by \\


Not applicable


All

right

s re

serv

ed. P

assi

ng o

n an

d co

pyin

g of

this

docu

men

t, us

e an

d co

mm

unic

atio

n of

its

cont

ents

notp

erm

itted

with

outw

ritte

nau

thor

izat

ion

from

Evo

lium

3.13 ALERTERS: FORMATTED ALARM EXPORT FROM AS-CUR ANDAS-HIST NOT POSSIBLE

3.13.1 Reference FR

3BKA45FBR120556


This problem occurs when the operator has enabled the alerter in the A1353-RA-MPM administration/BasicAlerter and restarted the loader or defined an alerter

When the alerter in raised, in the alarm-lists (current and history) the text in the field SpecificProblems has gotthe "-character at the beginning and the end

If an alerter alarm (e.g. SDCCH_cong_rate) is selected to output via print (formattedHtml) the export is notpossible.


Remove the characters by editing the /alcatel/var/share/as/specificProblems file

Example :

alerters in the initial specificProblems file Adaptation performed in the final initialspecificProblems file

200001 "Out_succ_rate"200002 "In_succ_rate"200003 "RTCH_AVAIL_AH_rate"200004 "RTCH_Erlang_per_TCH"200005 "RTCH_cong_rate"200006 "RTCH_fail_rate"200007 "SDCCH_cong_rate"200008 "SDCCH_drop_rate"200009 "call_drop_rate"200031 "specific_alerter"/

200001 Out_succ_rate200002 In_succ_rate200003 RTCH_AVAIL_AH_rate200004 RTCH_Erlang_per_TCH200005 RTCH_cong_rate200006 RTCH_fail_rate200007 SDCCH_cong_rate200008 SDCCH_drop_rate200009 call_drop_rate200031 specific_alerter/

BE CARREFULL

Before removing the alerter, put back the 2 characters on the involved alerter in the/alcatel/var/share/as/specificProblems file.

If you did not put back the 2 characters, on the involved alerter before removing the alerter, you have to deletethe corresponding line in the /alcatel/var/share/as/specificProblems file.


Not applicable


All

right

s re

serv

ed. P

assi

ng o

n an

d co

pyin

g of

this

docu

men

t, us

e an

d co

mm

unic

atio

n of

its

cont

ents

notp

erm

itted

with

outw

ritte

nau

thor

izat

ion

from

Evo

lium

3.14 SOLARIS 10: PROBLEM OF COLORS

3.14.1 Reference FR

3BKA32FBR163876


If you have problems with the colors displayed on your monitor (the icon in DCN is black, the color of the iconinside BSSUSM is lost, and the border of RNUSMSC is grayed...)


A possible solution is to switch your workstation graphics mode to a color depth deeper than 8 bits (such as 16bits, 24 bits, or 32 bits, depending on the video memory of your workstation).

1) Execute the Solaris command on the target workstation (HMI, Master,)

/usr/sbin/m64config -prconf

This command prints a list of the possible card resolutions, possible monitor resolutions, possible depths, currentresolution setting, and current depth.

2) Find another resolution setting and depth setting that are possible on your monitor and then using theparameters

-res to change the monitor resolution and refresh rate

-depth to change the color depth (for example to 16 bit, 24 bit, ...),

execute the command

->> /usr/sbin/m64config

For example, to change to 1152x900 resolution with 76Hz refresh rate and 24 bit color depth, the commandwould be:

/usr/sbin/m64config -res 1152x900x76 -depth 24

You must restart the X11 server to activate the changes. If you use the CDE dtlogin window, logging out andthen logging in again activates the changes.


Not applicable


All

right

s re

serv

ed. P

assi

ng o

n an

d co

pyin

g of

this

docu

men

t, us

e an

d co

mm

unic

atio

n of

its

cont

ents

notp

erm

itted

with

outw

ritte

nau

thor

izat

ion

from

Evo

lium

3.15 "THE DT MESSAGING SYSTEM COULD NOT BE STARTING,AXADMIN ICONBOX CANNOT BE LAUNCHED.",

3.15.1 Reference FR

FR3BKA32FBR127023


After an OMC reboot, we try to log in OMC3 with axadmin user. This loggin failed with the following message:

"The DT messaging system could not be started

To correct the problem:

1 Choose [OK] to return to the login screen

2 Select Failsafe Session from the login screen's option menu and log in

3 Check to see that the hostname is correct in these locations

/etc/src.sh

/etc/hosts

/usr/adm/inetd.sec " .


Log in root and launch the following command:

rm /alcatel/var/home/axadmin/.TTauthority


Not applicable


All

right

s re

serv

ed. P

assi

ng o

n an

d co

pyin

g of

this

docu

men

t, us

e an

d co

mm

unic

atio

n of

its

cont

ents

notp

erm

itted

with

outw

ritte

nau

thor

izat

ion

from

Evo

lium

3.18 IT'S NOT POSSIBLE TO GIVE A NAME TO A PRC WHEN VERRNUM (NUM LOCK) KEY IS ACTIVATED.

3.15.5 Reference FR

3BKA20FBR126064


It's not possible to give a name to a PRC when Verr Num (Num lock) key is activated. The problem itsreproducible only on specific environments: NCD X-Terminals, Terminals with french keyboards, etc.

X-Windows defines the concept of modifiers. Modifiers are special keys on a keyboard that

can be "combined" with standard keys (examples are Shift, Caps Lock, Num Lock, ALT, ...).

Five different categories of modifiers are defined, named mod1, mod2, ..., mod5.

The OMC uses ILOG Views which considers that this categories must be :

mod1 = Meta Modifier

mod2 = AltG Modifier

mod3 = Num Modifier

mod4 = Alt Modifier

But, on some environment (especially on NCD X-Terminals) this standard definition of

categories is not implemented ! In fact, mod3 contains Alt modifiers and mod4 contains Num

modifier !


WARNING: After applying the corrective action described here its possible to have another problem: when VerrNum (Num lock) key is activated the windows can not be moved and the right click on the mouse will not work.

So, to fix the PRC name problem, you only have to reconfigure correctly your keyboard using the dedicated X11utility called xmodmap.

Here are the commands necessary to swap mod 3 and mod4 :

axadmin@host xmodmap -e "clear mod3"

axadmin@host xmodmap -e "clear mod4"

axadmin@host xmodmap -e "add mod3 = Num_Lock"

axadmin@host xmodmap -e "add mod4 = Meta_L Meta_R"


Not applicable


All

right

s re

serv

ed. P

assi

ng o

n an

d co

pyin

g of

this

docu

men

t, us

e an

d co

mm

unic

atio

n of

its

cont

ents

notp

erm

itted

with

outw

ritte

nau

thor

izat

ion

from

Evo

lium

3.19 LEGATO BACKUP CANNOT BE RE-STARTED IN CASE OFFAILURE OF "SAVE_PRE_LEGATO" SCRIPT

3.19.1 Reference FR

3BKA32FBR137456


LRG B9 old HW (1 Master and 2 Agents):

- Backup is launched from Legato Networker

- save_pre_legato script fails on Master during snapshots

- Stop Backup on Legato Networker

- Re-launch the Backup from Legato Networker

==> Legato Backup cannot be restarted


a) When the Legato Networker Backup cannot be started on XLRG old/new HW : the status of

group Control is "Running" but nothing is saved on Media Device. It is recommended to abort

the Backup on Legato Networker Server and to launch as root the cleanup script

"/usr/bin/clean_legato.sh" on OMC-R Master to retrieve a normal behavior.

or

b) Master and Agents ==>

Kill "save_pre_legato.sh"

Launch "save_post_legato.sh"

rm /var/tmp/pre_save_log.*

rm /var/tmp/post_save_log.*

Master ==>

rm /alcatel/var/share/traces/sshlog.*

rm /alcatel/var/share/traces/rshlog.*

rm -rf /alcatel/var/share/traces/legato

rm -rf /alcatel/var/share/traces/


A notice has been added in Legato method, that if the script hangs to press Ctrl-C and start

clean_legato.sh script.


All

right

s re

serv

ed. P

assi

ng o

n an

d co

pyin

g of

this

docu

men

t, us

e an

d co

mm

unic

atio

n of

its

cont

ents

notp

erm

itted

with

outw

ritte

nau

thor

izat

ion

from

Evo

lium

3.20 LAUNCH OF CRAFT TERMINAL FROM OMC3 CAUSES SEVERALMOZZILA ERROR MESSAGES

3.20.1 Reference FR

3BKA20FBR137530


Pressing the "Navigate to IMT" button from the MFSUSM (before Mozzila window appears), the following errorpops up:

"Mozzila has detected a /alcatel/var/home/axadmin/.mozzila /lock file. ...."

This can be due to the fact another Mozzila window is already open. In this case it is a normal behavior.

If no other Mozzila window is already open, delete the /alcatel/var/home/axadmin/. mozzila /lock file.

If above error has been confirmed with the "Ok" button, Mozzila can open two windows with the followingmessages:

1. The certificate issuer for this server is not recognized by Mozzila . .... Mozzila refuses to connect to thisserver...."

2."Java reported the following error on startup: java.lang.securityException: system classes were notsigned"

Those errors can be due to the http server configuration, but the Craft terminal can normally be used.


Confirm all the error messages.


Not Applicable


All

right

s re

serv

ed. P

assi

ng o

n an

d co

pyin

g of

this

docu

men

t, us

e an

d co

mm

unic

atio

n of

its

cont

ents

notp

erm

itted

with

outw

ritte

nau

thor

izat

ion

from

Evo

lium

3.21 PORTS BLOCKED DUE TO REPETITIVE INCORRECTLYTERMINATED ACTIONS

3.21.1 Reference FR

3BKA20FBR145032


Symptom:

Ports are blocked, impossible to perform other actions

This kind of problem could occur due to repetitive incorrectly terminated actions.


The workaround is to kill at least one process blocking the port using the following commands:

axadmin@host$ ps -ef | grep cmd

root@host$ kill -9 PID


Not applicable

3.22 RNUSM FREEZE ON HMI DURING NORMAL USAGE

3.22.1 Reference FR

3BKA20FBR148563

3BKA45FBR148519


Symptom:

During normal usage sporadically the CPU load oscillates between 80-100% and sometimes reaches 100%

The epim process was in FlowControl, which is normal taking into account the huge amount of informationexchanged between processes just after migration


All

right

s re

serv

ed. P

assi

ng o

n an

d co

pyin

g of

this

docu

men

t, us

e an

d co

mm

unic

atio

n of

its

cont

ents

notp

erm

itted

with

outw

ritte

nau

thor

izat

ion

from

Evo

lium

As a consequence all the operations are slow down, RNUSM freeze for few minutes, no action possiblemeanwhile.

After a while, 1-2 min it goes down again to 5-10% and the RNUSM windows can be normally used.


WARNING: before applying the workaround, please be sure that no radio modification is on going

If any RNUSM window is opened during applying this workaround a normal warning message is raised:Communication problem with rnimsc. Close all windows immediately

After pushing the OK button the RNUSM window will be closed.

The workaround is to stop/start from DSM the epim process.

You will need to reopen RNUSM window


Not applicable

3.23 NO ERROR MESSAGE IF THE NAVSERVER IS DOWN

3.23.1 Reference FR

3BKA32FBR171546


When a OMC application is opened from Icon-Box (Muse) and the Navserver is down no error message isdisplayed to the user.


The workaround is to restart Iconbox and then the application (to restart NavServer process from DSMUSMwindow)


Not applicable


All

right

s re

serv

ed. P

assi

ng o

n an

d co

pyin

g of

this

docu

men

t, us

e an

d co

mm

unic

atio

n of

its

cont

ents

notp

erm

itted

with

outw

ritte

nau

thor

izat

ion

from

Evo

lium

3.24 STOP/START SEC SERVICE

3.24.1 Reference FR

3BKA32FBR164347


The sec server process is now managed as a service; it will not be visible in DSMUSM anymore.


As root is necessary to launch following scripts:

STOP SEC service

svcadm disables /network/ldap/sec7

START SEC service

svcadm enable s /network/ldap/sec7


Not applicable

3.25 FALSE MESSAGE APPEARS WHEN OMC IS STARTED FROMOSM.

3.25.1 Reference FR

3BKA32FBR172736, 3BKA32FBR164347


When OMC is started from OSM the following message is displayed:

"Starting OMC3 ...

The security daemon could not be started within expected time

Starting processes via DSM

Please open the DSM window and WAIT until all processes became green!"


None.

Because the sec server process is now managed as a service ignore the message:

The security daemon could not be started within expected time


All

right

s re

serv

ed. P

assi

ng o

n an

d co

pyin

g of

this

docu

men

t, us

e an

d co

mm

unic

atio

n of

its

cont

ents

notp

erm

itted

with

outw

ritte

nau

thor

izat

ion

from

Evo

lium


Not applicable

3.26 REMAINED ACTIONS PENDING IN THE BSSUSM FOLLOW-UP

3.26.1 Reference FR

3BKA32FBR168333


After BSS B8->B9 Migration, the BSS Discover is frozen in the BSSUSM follow-upwindow. Several actionsremain at


All

right

s re

serv

ed. P

assi

ng o

n an

d co

pyin

g of

this

docu

men

t, us

e an

d co

mm

unic

atio

n of

its

cont

ents

notp

erm

itted

with

outw

ritte

nau

thor

izat

ion

from

Evo

lium


Not applicable

3.28 FULL PARTITION DUE TO GENERATION OF LSS CORE FILEUNDER "/"

3.28.1 Reference FR

3BKA32FBR178478


On the HMI, lss was crashing but the core file was not put on the "normal" location

(/alcatel/var/maintenance/core) but under /opt/almap/lss/data (so under the "/" partition).

The root partition is small in terms of available space (i.e. on the E450 machine - only 160,5 Mb available).

So after the generation of the ls core file (160Mb core file) the "/" partition was full.


Delete the core file under /opt/almap/lss/data

Restart the lss process from DSM


Documents

OMC Trouble Shooting Guide B9 ed05.pdf