Está en la página 1de 103

All rights reserved.

Passing on and copying of this


document, use and communication of its contents not
permitted without written authorization from Alcatel-Lucent

Site
VELIZY

Mobile Access Division

Originator

BSS RESTRICTIONS LIST


BSSSAX01C Ed07 QD5

C. Clep

RELEASE B10

System
Sub-system
Document Category

:
:
:

ALCATEL 900/1800/BSS
SYS
PRODUCT DELIVERY

ABSTRACT
This document provides the complete restriction list of the BSSSAX01C Ed07 QD5 delivery (MR2
Ed07).

Approvals
Name
App.

B10 BSS TPL


R. Mauger

B10 Quality
Manager
T. Herment-Tan

NPI
N. Maleyrie / D.
Guidot

FOA
Franois Berjon

Name
App.

REVIEW
HISTORY
Ed.01 Proposal 01

09/10/16

Based on BSS RESTRICTION LIST BSSSAX01C Ed07


QD2.
Updated updated with the following:

ED

01

Removal of CLOSE FRs and adition of new FRs, listed


in the two following tables

Released

11/25/2009

BSS RESTRICTIONS LIST


BSSSAX01C Ed07 QD5
RELEASE B10
3BK 13016 1261 TQZZA
1/103

All rights reserved. Passing on and copying of this


document, use and communication of its contents not
permitted without written authorization from Alcatel-Lucent

New FRs introduced


from BSSSAX01C
Ed07QD5

Failed to add BSC (BKC08) to OAD via SECusm

New

3BKA20FBR261698

Toggling alarm VOLTAGE_MINOR [16] for both TCIF


boards

New

3BKA20FBR278558

Wrong values of counters family P531_b (DL LLC


throughput distribution per user)
MT120-TCIF connection lost after HSI cable unplug/plug, or
after TCIF take over

New
New

3BKA20FBR285887

TP takeover refused after an MLU session

New

3BKA20FBR285134

TWIN module replacement issue

New

3BKA20FBR285136

ANC module replacement issue

New

3BKA20FBR270350
3BKA20FBR280001
3BKA20FBR281083
3BKA20FAG285316
3BKA20FBR276494
3BKA20FBR280476
3BKA20FBR280282
3BKA20FAG284753
3BKA20FBR273540
3BKA20FBR274598
3BKA20FBR273709
3BKA20FBR287743

FRs removed since


BSSSAX01C Ed07
QD5

When performing the MT120 board replacement, the wizard


provided by TC NEM never ends
Sporadically, MT20 boards are missing in TC NEM, after
TCIF new SW activation
MT120 boards misaligned with cause File list report failure
after rejecting the activated SW.
Old OBSYNT directories are not deleted when the files
inside these directories are removed.
MUX contact error on MFS Evolution during MFS SW
Migration
Telecom outage on BSC Evolution due to unsuccessful TP
takeover
Wrong status displayed in OMC for stm1-ttp1, in case of
lock action.
ENVIR [5] SUBRACK-POWER [24] alarm not enough
accurate in case of TWIN TRE
Wrong display of TS allocation in USD Cell Overview
Window in case of satellite communications
Re-init and resynchronize GPRS fails due to error during file
transfer
Even if one TCIF board is power-off, the TCIF board
appears OK at TCNEM
Only one way voice is heard in case of A_PCM_TP48 is
used

Short Description

New
New
New
New
New
New
New
New
New
New
New
New

Status

3BKA20FBR257549

In certain conditions, TREs cannot be added on BTS due to


max-tre-exceeded
List of all SW present on each supervised MT120 should be
accessible from TCIF TCNEM

3BKA20FBR262484

Alarm INT-BUS-FLT-G25 on MT120 board after swith to HSI

CLOSE REL

3BKA20FBR272686

After unlock TCIF, the status of TCIF board displayed in TCNEM or OMC-R is not aligned with the real state (rebooting)
of the TCIF, for a few minutes

CLOSE REL

3BKA20FBR274034

DCNUSM: TCIF - SDH Occupancy is empty

CLOSE REL

3BKA20FBR273495

Not possible to declare the TCIF at OMCR

CLOSE REL

3BKA20FBR227643

3BKA20FBR273587
3BKA20FBR274697
3BKA20FBR272452
3BKA20FBR273827

01

Status

3BKA20FBR276963

3BKA20FBR248190

ED

Short Description

When performing change_bssim supervision from Master,


HMI is not updating (and vice versa)
Sometimes OMC-MXMFS connection is lost after
performing actions as 'reset MXMFS' or 'Switchover Control
Station'
BSC-HW-RESYNCH message is sent by BSC, but OMC-R
does not trigger an automatic HW Audit
TC Remote Inventory Request is sometimes not successful

Released

11/25/2009

CLOSE REL
CLOSE REL

CLOSE REL
CLOSE REL
CLOSE REL
CLOSE REL

BSS RESTRICTIONS LIST


BSSSAX01C Ed07 QD5
RELEASE B10
3BK 13016 1261 TQZZA
2/103

FRs removed since


BSSSAX01C Ed07
QD5
All rights reserved. Passing on and copying of this
document, use and communication of its contents not
permitted without written authorization from Alcatel-Lucent

3BKA20FBR275006
3BKA20FBR275259
3BKA20FBR273831
3BKA20FAG276116

BSSIM crash during the TC Remote Inventory request


During a TCIF power-off test, the only STM1_TTP available
becomes protected, instead of working
OMC-BSC connection is down after performing scenario
"change MXBSC IP in case of MXBSC with mlppp"
BSC Evolution with TELECOM [42] OVERLOAD-BSC [9]
alarm, observed on TP boards.

CLOSE REL
CLOSE REL
CLOSE REL
CLOSE REL

GP Reset if JBXSSW shelf4 active is reseted

CLOSE REL

3BKA20FBR275257

Both TCIFs seen as stand-by on OMC, after unlock stm1_ttp

CLOSE REL

3BKA20FBR273098
3BKA20FBR275852

No response from the OMC to the M-GET requests sent by


the TTI
BSSIM process hanging during network element link
creation due to SCOMM crash. TCIF is declared.
Hanging GPU: After a loss of connection with GPU, GEM is
sometimes not reseting the board.

CLOSE REL
CLOSE REL
CLOSE REL

3BKA20FAg276124

GPRS traffic lost on several cells from one BSC

CLOSE REL

3BKA20FBR261379

Legacy MT120 not seen in TCNEM after TCIF takeover

CLOSE REL

3BKA20FBR258208

Sometimes BTS-NEM crashes/closes autonomously

CLOSE REL

3BKA20FBR274532

TC Call Drop for some sites, on MxBSC

CLOSE REL

Frequent OMC-BSC Evolution disconnections

CLOSE REL

After CCP takeover, many VCE report Reset alarm that


aren't cleared automatically

CLOSE REL

3BKA20FBR232033
3BKA20FBR274313

New FRs introduced


from BSSSAX01C
Ed07QD2

Short Description

Status

3BKA20FBR274194

No response from the OMC to the M-GET requests sent by


the TTI

New

3BKA20FBR274466

GP Reset if JBXSSW shelf4 active is reseted

New

3BKA20FBR274532

TC Call Drop for some sites, on MxBSC

New

3BKA20FBR274579

Sleeping Q3 interface observed several times

New

3BKA20FBR275086

OMCP reset/takeover after BSC Evolution reduction

New

3BKA20FBR275257

Both TCIFs seen as stand-by on OMC, after unlock stm1_ttp

New

3BKA20FBR275852
3BKA20FAG276116

01

Status

3BKA20FBR274466

3BKA20FBR274194

ED

Short Description

Hanging GPU: After a loss of connection with GPU, GEM is


sometimes not reseting the board.
BSC Evolution with TELECOM [42] OVERLOAD-BSC [9]
alarm, observed on TP boards.

New
New

3BKA20FAG276122

"Loss of contact with GPU" MFS alarms

New

3BKA20FAg276124

GPRS traffic lost on several cells from one BSC

New

3BKA20FBR264586

Strident whistling noise after a while during a communication

New

3BKA20FBR266341

No alarm for both active/stand-by TPs, in case of driversfailure problem

New

3BKA20FBR267980

Total GPRS Outage during 15 min on MFS Evolution

New

3BKA20FBR270721

No JBXTP takeover done, leads to outage on BSC Evolution

New

3BKA20FBR271489

TC Power supply alarm not recognized by MX BSC

New

Released

11/25/2009

BSS RESTRICTIONS LIST


BSSSAX01C Ed07 QD5
RELEASE B10
3BK 13016 1261 TQZZA
3/103

New FRs introduced


from BSSSAX01C
Ed07QD2
All rights reserved. Passing on and copying of this
document, use and communication of its contents not
permitted without written authorization from Alcatel-Lucent

3BKA20FBR272054
3BKA20FBR273007
3BKA20FBR273029
3BKA20FBR227643

TS15 and TS16 on not usable on A-Interface : TS16 cannot


be used for PS traffic
After PRC activation the GPRS Status at RNUSM for BSC
and all Cells are disable
Alarm alignment action from TTI NMC to OMC-R fails all the
time
In certain conditions, TREs cannot be added on BTS due to
max-tre-exceeded

New
New
New
New

TCNEM sometimes remains hanging

New

3BKA20FBR258208

Sometimes BTS-NEM crashes/closes autonomously

New

3BKA20FBR272452
3BKA20FBR272686
3BKA20FBR273098

All GPUs rebooted twice after performing RESET MFS from


IMT in GboIP and MXMFS in 2 shelfs
BSC-HW-RESYNCH message is sent by BSC, but OMC-R
does not trigger an automatic HW Audit
After unlock TCIF, the status of TCIF board displayed in TCNEM or OMC-R is not aligned with the real state (rebooting)
of the TCIF, for a few minutes
BSSIM process hanging during network element link
creation due to SCOMM crash. TCIF is declared.

New
New
New
New

3BKA20FBR273827

TC Remote Inventory Request is sometimes not successful

New

3BKA20FBR273831

OMC-BSC connection is down after performing scenario


"change MXBSC IP in case of MXBSC with mlppp"

New

3BKA20FBR274034

DCNUSM: TCIF - SDH Occupancy is empty

New

3BKA20FBR274313
3BKA20FBR274697
3BKA20FBR275006
3BKA20FBR275259
3BKA20FBR270108

After CCP takeover, many VCE report Reset alarm that


aren't cleared automatically
Sometimes OMC-MXMFS connection is lost after
performing actions as 'reset MXMFS' or 'Switchover Control
Station'
BSSIM crash during the TC Remote Inventory request
During a TCIF power-off test, the only STM1_TTP available
becomes protected, instead of working
PV_PEM alarms raised and not cleared from IMT and
OMCR after MFS power off/on

New
New
New
New
New

3BKA20FBR270214

Values in CCP Resources Report are not OK

New

3BKA20FBR270216

Missing removal of Remote Inventory data after reallocation


of Network Element

New

3BKA20FBR271005

GOM crash due to watchdog expiry

New

3BKA20FBR271475

The alarm "Hard disk problem" is present on every machine


(Master, Agent, and HMI)

New

3BKA20FBR272959

CCP-Resource-report has displayed strange values

New

3BKA20FBR273495

Not possible to declare the TCIF at OMCR

New

3BKA20FBR273587
3BKA20FBR276240

FRs removed since


BSSSAX01C Ed07
QD2

01

Status

3BKA20FBR254920

3BKA20FBR272345

ED

Short Description

When performing change_bssim supervision from Master,


HMI is not updating (and vice versa)
GP reset in loop, for multi GP configuration, if reshuffle is
performed

Short Description

New
New

Status

3BKA20FBR263321

Cells are stopped and started frequently during GPU


endurance test in GboIP configuration

CLOSE REL

3BKA20FBR264025

Sporadic GOM crashes

CLOSE REL

3BKA20FBR264331

BSC predownload may fail during MLU

CLOSE REL

3BKA20FBR264351

Sometimes GPMRES files are not trasnferred to OMC

CLOSE REL

Released

11/25/2009

BSS RESTRICTIONS LIST


BSSSAX01C Ed07 QD5
RELEASE B10
3BK 13016 1261 TQZZA
4/103

All rights reserved. Passing on and copying of this


document, use and communication of its contents not
permitted without written authorization from Alcatel-Lucent

FRs removed since


BSSSAX01C Ed07
QD2

No alarm reported by the BSC toward OMC-R after FAN


removal.

CLOSE REL

3BKA20FBR265104

JBXPS alarms not cleared in OMC-R after JBXPS recovery.

CLOSE REL

3BKA20FBR268123
3BKA20FBR267840
3BKA20FBR268303
3BKA20FBR264234
3BKA20FBR265726
3BKA20FBR268512

Decrease of GPRS quality indicator after CCP extension on


a BSC Evolution
GPMRES files belonging to the interval [00:00,00:00+GMT
OFFSET] are not processed by OMC
After a BSC extension from conf 3 to 4, the BSSIM restarts
in loop if the AterMux 3 is a mixed one, with granularity
greater than 25%

CLOSE REL
CLOSE REL
CLOSE REL

MF-cleanup.pl script is not always working properly

CLOSE REL

OMCR/DSM "acoservice" process cannot be restarted

CLOSE NRE

Wrong population of R_CNFSMAT.D_QAD after TC


extension above Atermux 60
HW/Alarm audit does not work after a short BSC-OMC
disconnection

CLOSE REL
CLOSE REL

3BKA20FBR268523

Traffic failure after OMCP takeover

CLOSE REL

3BKA20FBR268510

Programming transmission not ended sometimes

CLOSE REL

3BKA20FBR263230

Connection interruption between OMC and BSC Evolution

CLOSE REL

3BKA20FBR264053

BSSIM crash due to Assertion Failure

CLOSE NRE

3BKA20FBR266131

CCP takeover not successful

CLOSE REL

3BKA45FBR258768

It happened once that after an MLU activation, GPRS


service was lost in one cell redefined with capacity
extension and parameter changes

CLOSE NRE

3BKA20FBR248886

Replacement Wizard is not accessible in HSI mode

CLOSE REL

3BKA20FBR266328

After N7 link cut, sometimes BSC does not respond during


link recovery

CLOSE NRE

3BKA20FBR268286

MT120-xB boards blocked during SW activation

CLOSE REL

3BKA20FBR266336

Both TP with access failed after OMCP takeover

CLOSE NRE

3BKA20FBR268514

Not possible to change TC config from 6 to 7 with BSC-LMT

CLOSE REL

3BKA20FBR267564

Sometimes the DCNUSM cannot be opened

CLOSE REL

3BKA20FBR253718

In the particular case where the SW upgrade has to be done


for a great number of MT120 boards, the preload fails for
some boards but without reporting which ones

CLOSE REL

3BKA20FBR268750

Sometimes the DCNUSM cannot be opened

CLOSE REL

3BKA20FBR264158

OMCP reboot in loop after OMCP board replacement

CLOSE REL

3BKA20FBR268890

Remote inventory of 9125 TC not always works

CLOSE REL

3BKA20FBR268974

During 9125 TC remote inventory, BSSIM may crash

CLOSE REL

3BKA20FBR269175

Cannot perform MxBSC extension to conf 5 when having


TC_conf>30

CLOSE REL

3BKA20FBR269292

Active OMCP reset when removal standby OMCP board

CLOSE REL

3BKA20FBR269306
3BKA20FBR269113
3BKA20FBR257105
3BKA20FBR268578

01

Status

3BKA20FBR265087

3BKA20FBR267745

ED

Short Description

Sporadic call drop, after MT120 SW migrated from B9 to


B10, on cells belonging to BTSs which have Abis link over
satellite
APS and EPS mechanism on TCIF linked to G2 BSC is not
always working
DTM and EDA modes cannot be used in Gb over IP
configuration
BSSIM process crash in loop during TC HW audit

Released

11/25/2009

CLOSE REL
CLOSE NRE
CLOSE REL
CLOSE REL

BSS RESTRICTIONS LIST


BSSSAX01C Ed07 QD5
RELEASE B10
3BK 13016 1261 TQZZA
5/103

FRs removed since


BSSSAX01C Ed07
QD2

CLOSE OUT

3BKA20FBR264234

OMCR/DSM "acoservice" process cannot be restarted

CLOSE NRE

3BKA20FBR264509

Wrong status reported in BSC terminal and OMC for JBXPS

CLOSE REL

3BKA20FBR264555

Very sporadic CU restart

CLOSE REL

3BKA20FBR265866

Autonomous TP Takeover due to E1-SL-FAILURE

CLOSE REL

3BKA20FBR269258

Reset action is still allowed on active TCIF, while standby


TCIF is unavailable

CLOSE REL

3BKA20FBR266850

Errors generated by script mx_checkSanity

CLOSE REL

3BKA20FBR266984

Short periodic HSI link disconnection for XB boards that are


Qmux master

CLOSE REL

3BKA20FBR267386

Loss of all traffic on MX BSC

CLOSE REL

3BKA20FBR267898

Autonomous TP Takeover due to TP1 ERROR

CLOSE REL

All rights reserved. Passing on and copying of this


document, use and communication of its contents not
permitted without written authorization from Alcatel-Lucent

3BKA20FBR268190
3BKA20FBR260036

3BKA20FBR267944
3BKA20FBR267683
3BKA20FBR268310

TC NEM didnt autonomously reconnect to TCIF boards,


after both TCIF boards were reseted
OMCP board replacement: after clean-disk-before-reuse the
board is not powered Off
SDH links View occupancy not updated to new STM1
configuration

CLOSE REL

CLOSE REL

CLOSE REL
CLOSE REL
CLOSE REL

3BKA20FBR268444

After MUX takeover, both MUX are displayed as standby

CLOSE REL

3BKA20FBR268656

Overload from PQ2 alarm during MLU Activation

CLOSE REL

3BKA20FBR268790

MT120 board displayed in red in TC NEM, after TCIF


takeover

CLOSE REL

3BKA20FBR269115

BER-6 alarms on MT120 boards configured in HSI2b

CLOSE REL

3BKA20FBR259527

It may happen that a GPU switch-over does not work.

CLOSE REL

3BKA20FBR237435

Incorrect informations regarding SDH characteristics, in the


TC rack view
Connection between OMC-R and TC on IP is lost from time
to time
It is not possible to perform a System Restore on the
STATION B of an MFS with DS10 server

3BKA20FBR268361

TC declaration on OMC is partially successful

3BKA20FBR265694
3BKA20FBR269114

New FRs introduced


from BSSSAX01C
Ed07

01

Status

The TCIF is not supervised by another OMC considered as


Spare after applying "OMC Disaster/Recovery" scenario
The call only establish on main TRX when concentric cell
maped on 2 BTS
Sporadic loss of ongoing call, during a TCIF takeover, in
HSI2b

3BKA20FBR243912

ED

Short Description

Short Description

CLOSE REL
CLOSE REL
CLOSE REL
CLOSE DUP

Status

3BKA20FBR263321

Cells are stopped and started frequently during GPU


endurance test in GboIP configuration

New

3BKA20FBR264025

Sporadic GOM crashes

New

3BKA20FBR264331

BSC predownload may fail during MLU

New

3BKA20FBR264351

Sometimes GPMRES files are not trasnferred to OMC

New

3BKA20FBR265087

No alarm reported by the BSC toward OMC-R after FAN


removal.

New

Released

11/25/2009

BSS RESTRICTIONS LIST


BSSSAX01C Ed07 QD5
RELEASE B10
3BK 13016 1261 TQZZA
6/103

Short Description

Status

3BKA20FBR265104

JBXPS alarms not cleared in OMC-R after JBXPS recovery.

New

All rights reserved. Passing on and copying of this


document, use and communication of its contents not
permitted without written authorization from Alcatel-Lucent

New FRs introduced


from BSSSAX01C
Ed07

3BKA20FBR267745
3BKA20FBR268123
3BKA20FBR267840
3BKA20FBR268303
3BKA20FBR265726
3BKA20FBR268512

Wrong population of R_CNFSMAT.D_QAD after TC


extension above Atermux 60
HW/Alarm audit does not work after a short BSC-OMC
disconnection

New
New
New
New
New

TC declaration on OMC is partially successful

New

3BKA20FBR268523

Traffic failure after OMCP takeover

New

3BKA20FBR268510

Programming transmission not ended sometimes

New

3BKA20FBR261517

Wrong reporting of several sensors from JBXPS board

New

3BKA20FBR263230

Connection interruption between OMC and BSC Evolution

New

3BKA20FBR264053

BSSIM crash due to Assertion Failure

New

3BKA20FBR266131

CCP takeover not successful

New

3BKA20FBR266328

After N7 link cut, sometimes BSC does not respond during


link recovery

New

3BKA20FBR266336

Both TP with access failed after OMCP takeover

New

3BKA20FBR267980

15 minutes GPRS outage due to reboot MFS stations

New

3BKA20FBR268286

MT120-xB boards blocked during SW activation

New

3BKA20FBR268514

Not possible to change TC config from 6 to 7 with BSC-LMT

New

3BKA20FBR267564

Sometimes the DCNUSM cannot be opened

New

3BKA20FBR268750

Sometimes the DCNUSM cannot be opened

New

3BKA20FBR264158

OMCP reboot in loop after OMCP board replacement

New

3BKA20FBR268890

Remote inventory of 9125 TC not always works

New

3BKA20FBR268974

During 9125 TC remote inventory, BSSIM may crash

New

3BKA20FBR269114
3BKA20FBR269292
3BKA20FBR269306
3BKA20FBR269113

01

MF-cleanup.pl script is not always working properly

New

3BKA20FBR268361

3BKA20FBR269175

ED

Decrease of GPRS quality indicator after CCP extension on


a BSC Evolution
GPMRES files belonging to the interval [00:00,00:00+GMT
OFFSET] are not processed by OMC
After a BSC extension from conf 3 to 4, the BSSIM restarts
in loop if the AterMux 3 is a mixed one, with granularity
greater than 25%

Cannot perform MxBSC extension to conf 5 when having


TC_conf>30
Connection between OMC-R and TC on IP is lost from time
to time
Active OMCP reset when removal standby OMCP board
Sporadic call drop, after MT120 SW migrated from B9 to
B10, on cells belonging to BTSs which have Abis link over
satellite
APS and EPS mechanism on TCIF linked to G2 BSC is not
always working

New
New
New
New
New

3BKA20FBR268578

BSSIM process crash in loop during TC HW audit

New

3BKA20FBR268190

The call only establish on main TRX when concentric cell


maped on 2 BTS

New

3BKA20FBR259871

Incorrect alarm dictionary extract after selecting an alarm

New

3BKA20FBR268643

Sometimes, in TCIL mode, the activation of the new MT120


SW is not always successful

New

Released

11/25/2009

BSS RESTRICTIONS LIST


BSSSAX01C Ed07 QD5
RELEASE B10
3BK 13016 1261 TQZZA
7/103

All rights reserved. Passing on and copying of this


document, use and communication of its contents not
permitted without written authorization from Alcatel-Lucent

New FRs introduced


from BSSSAX01C
Ed07

Sporadic loss of ongoing call, during a TCIF takeover, in


HSI2b

New

3BKA20FBR260051

Sporadic reboot of MT120 board, during TCIF takeover

New

3BKA20FBR261257

Very long link redundancy (arp timer) at SSW level in one


LAN configuration, for MFS evolution.

New

3BKA20FBR262484

Alarm INT-BUS-FLT-G25 on MT120 board after swith to HSI

New

3BKA20FBR261379

Legacy MT120 not seen in TCNEM after TCIF takeover

New

3BKA20FBR263050

MFS reservation status busy on 5 MFSs after close MLU


session

New

3BKA20FBR263228

Sometimes, the BSS declaration in OMC is not possible

New

3BKA20FBR263849

BSSIM crash due to Assertion Failure

New

3BKA20FBR264234

OMCR/DSM "acoservice" process cannot be restarted

New

3BKA20FBR264509

Wrong status reported in BSC terminal and OMC for JBXPS

New

3BKA20FBR264555

Very sporadic CU restart

New

3BKA20FBR265694

Incorrect informations regarding SDH characteristics, in the


TC rack view

New

3BKA20FBR265866

Autonomous TP Takeover due to E1-SL-FAILURE

New

3BKA20FBR266169

Errors during move a BSS from Master to Agent

New

3BKA20FBR269258

Reset action is still allowed on active TCIF, while standby


TCIF is unavailable

New

3BKA20FBR266850

Errors generated by script mx_checkSanity

New

3BKA20FBR266752

Wrong information in Alarm Dictionary for a QoS alarm

New

3BKA20FBR266984

Short periodic HSI link disconnection for XB boards that are


Qmux master

New

3BKA20FBR267386

Loss of all traffic on MX BSC

New

3BKA20FBR267898

Autonomous TP Takeover due to TP1 ERROR

New

3BKA20FBR267690
3BKA20FBR267683
3BKA20FBR268310

TC NEM didnt autonomously reconnect to TCIF boards,


after both TCIF boards were reseted
Wrong incrementation of repetition counter for the alarm
CELL [43] LOSS-OF-TCH [2]
OMCP board replacement: after clean-disk-before-reuse the
board is not powered Off
SDH links View occupancy not updated to new STM1
configuration

New
New
New
New

3BKA20FBR268444

After MUX takeover, both MUX are displayed as standby

New

3BKA20FBR268875

Date and time not correctly updated for TCIF takeover alarm

New

3BKA20FBR268656

Overload from PQ2 alarm during MLU Activation

New

3BKA20FBR268790

MT120 board displayed in red in TC NEM, after TCIF


takeover

New

3BKA20FBR269115

BER-6 alarms on MT120 boards configured in HSI2b

New

3BKA20FBR264021
3BKA20FBR259966
3BKA20FBR261064
3BKA20FBR261522

01

Status

3BKA20FBR260036

3BKA20FBR267944

ED

Short Description

Very spoardic, the GPMRES files have all GP counters


equal to 0
Secured (SSL) ICA connections are not properly configured
for HMI
After Gb IP base address and gateway creation from IMT
PC , IP endpoint creation window of OMC Gb configuration
window is not updated
Short circuit alarm for AGC9E with TMA

Released

11/25/2009

New
New
New
New

BSS RESTRICTIONS LIST


BSSSAX01C Ed07 QD5
RELEASE B10
3BK 13016 1261 TQZZA
8/103

New FRs introduced


from BSSSAX01C
Ed07
All rights reserved. Passing on and copying of this
document, use and communication of its contents not
permitted without written authorization from Alcatel-Lucent

3BKA20FBR261476

FRs removed since


BSSSAX01C Ed07

Status

Sometimes, during MLU session, the download may fail

Short Description

New

Status

3BKA20FBR260025

TC Remote Inventory fails for MT120-WB and MT120-NB

CLOSE REL

3BKA20FBR255898

Loss of MFS supervision after a BTS creation

CLOSE REL

3BKA17FBR240648

GPRS operational state are disabled for several cells after a


re-initialization in case of Multi-GP configuration
"REDUNDANCY-48V-LOSS" alarm for LIU PEM does not
allow to conclude which board is faulty
A faulty board disturbing the IPMI bus can let thinking
through an alarm to a failure of all fans and power supply of
a chassis.
In most of cases, during the Software Replacement of the
MT120 boards, the download operation seems starting but
never ends.
Sometimes, some cells have HO, assignment failure and
call drop problems.
During busy hours, it has been noted a degradation of
performance for services using uplink
On-line help is not working for most of the applications run
from the OMC-R Administration Facilities
TCIF board naming is not the same from the OMC-R and
TC Terminal
Active/Standby Status for TCIF boards is not updated at
OMC side during Reset TCIF for transition TCIF2 -> TCIF1
OMC - NMC supervision is lost in case of major operations
on a BSC
After extensive use by maximum number of users, no other
new user connection can be established with the HMI server
due to Citrix instability
Sometimes during parameter loading, one request may last
more than 1 hour

3BKA17FBR243914

Origin list filter is not working in NUART web page

3BKA20FBR258078
3BKA20FBR231296
3BKA20FBR258072

3BKA20FBR259429
3BKA20FBR256355
3BKA20FBR239429
3BKA20FBR241268
3BKA20FBR250248
3BKA20FBR259315
3BKA20FBR261265
3BKA17FBR219447

CLOSE REL
CLOSE REL
CLOSE REL

CLOSE REL
CLOSE REL
CLOSE REL
CLOSE REL
CLOSE REL
CLOSE REL
CLOSE REL
CLOSE REL
CLOSE REL
CLOSE REL

3BKA20FBR251592

It may happen that from time to time the OMCP crashes with
'HWM_HWCPI_RD_STARTING' information
Secure Single Gb feature is not compatible with multi-GPU
configuration and leads to O&M outage
No OMC-R online help available when using documentation
Server
The E1 over STM-1 transmission alarms are not correctly
reported after TCIF takeover
The replacement of an OMCP board loaded with a different
software leads to a decreasing of the nominal traffic and to
the loss of connection with the OMC-R and the BSC
Evolution terminal
If MPM is stopped for any reason, there is no easy way to
restart it
Sometimes it may happen that it is not possible to open the
AS Current USM window

CLOSE NRE

3BKA20FBR256725

It is not possible to perform a TCIF unlock from the OMC-R

CLOSE NRE

3BKA20FBR259118

No information displayed and no more operation possible


when trying to connect the TC-NEM via IP

CLOSE NRE

3BKA20FBR212839

Spare GP is rebooting in loop

CLOSE NRE

3BKA20FBR259524
3BKA20FBR232169
3BKA20FBR214662
3BKA20FBR259353

3BKA20FBR228309

3BKA20FBR252362

New FRs introduced


from BSSSAX01C
Ed06 QD02

ED

Short Description

01

Short Description

Released

11/25/2009

CLOSE REL
CLOSE REL
CLOSE REL
CLOSE REL

CLOSE REL

CLOSE REL

Status

BSS RESTRICTIONS LIST


BSSSAX01C Ed07 QD5
RELEASE B10
3BK 13016 1261 TQZZA
9/103

All rights reserved. Passing on and copying of this


document, use and communication of its contents not
permitted without written authorization from Alcatel-Lucent

New FRs introduced


from BSSSAX01C
Ed06 QD02
3BKA20FBR229768
3BKA20FBR239429
3BKA20FBR253718
3BKA20FBR256725

Short Description

Status

Sometimes, Objectstore crash occurs during Legato backup

New

During busy hours, it has been noted a degradation of


performance for services using uplink
In the particular case where the SW upgrade has to be done
for a great number of MT120 boards, the preload fails for
some boards but without reporting which ones
It is not possible to perform a TCIF unlock from the OMC-R

New
New

New

3BKA20FBR259524

DTM and EDA modes cannot be used in Gb over IP


configuration
Some information are missing for the MT120 boards when
the TC-NEM is connected via TCIF
List of all SW present on each supervised MT120 should be
accessible from TCIF TCNEM
It may happen that GPRS operational state are disabled for
several cells after a re-initialization in case of Multi-GP
configuration
No information displayed and no more operation possible
when trying to connect the TC-NEM via IP
Active/Standby Status for TCIF boards is not updated at
OMC side during Reset TCIF for transition TCIF2 -> TCIF1
The E1 over STM-1 transmission alarms are not correctly
reported after TCIF takeover
In most of cases, during the Software Replacement of the
MT120 boards, the download operation seems starting but
never ends.
It may happen that from time to time the OMCP crashes with
'HWM_HWCPI_RD_STARTING' information

3BKA20FBR260025

TC Remote Inventory fails for MT120-WB and MT120-NB

New

3BKA20FBR261265

OMC - NMC supervision is lost in case of major operations


on a BSC

New

3BKA20FBR257105
3BKA20FBR257277
3BKA20FBR257549
3BKA20FBR258078
3BKA20FBR259118
3BKA20FBR259315
3BKA20FBR259353
3BKA20FBR259429

FRs removed since


BSSSAX01C Ed06
QD02

Short Description

New
New
New
New

New
New
New
New

Status

A lot of messages DTM assignment failure cause TS in


inconsistent state with DTM traffic
Daylight saving time changes are not properly handled by
NPO

CLOSE REL

DPCK tool generates too many alarms

CLOSE REL

3BKA20FBR249922

Inactive objects not reported by NPO Administration

CLOSE REL

3BKA20FBR250509

Online help is not working from DSMUSM window

CLOSE REL

3BKA20FBR231044
3BKA20FBR238038
3BKA20FBR244156
3BKA20FBR244780

3BKA20FBR250882
3BKA20FBR251023
3BKA20FBR255910

New FRs introduced


from BSSSAX01C
Ed06 QD01
3BKA20FBR255471
3BKA20FBR255898
3BKA20FBR255910

ED

New

01

CLOSE REL

Error reported in DPCK after the MT120-WB board


introduction
The A9130 BSC Evolution extension systematically fails in
the particular case where this operation has been preceded
by an A9130 BSC Evolution reduction
It has been seen once a loss of PS traffic on the whole MFS
during a BTS creation through a Move BTS

CLOSE REL

Short Description

Status

It is not possible to configure a PS dedicated link below


Ater-Mux 31
It has been seen once a loss of MFS supervision after a
BTS creation
It has been seen once a loss of PS traffic on the whole MFS
during a BTS creation through a Move BTS

Released

11/25/2009

CLOSE REL
CLOSE REL

New
New
New

BSS RESTRICTIONS LIST


BSSSAX01C Ed07 QD5
RELEASE B10
3BK 13016 1261 TQZZA
10/103

All rights reserved. Passing on and copying of this


document, use and communication of its contents not
permitted without written authorization from Alcatel-Lucent

New FRs introduced


from BSSSAX01C
Ed06 QD01
3BKA20FBR256355
3BKA20FBR258072

Status

Sometimes, some cells have HO, assignment failure and


call drop problems.
It may happen that a faulty board disturbing the IPMI bus
can let thinking through an alarm to a failure of all fans and
power supply of a chassis.

New
New

3BKA20FBR259527

It may happen that a GPU switch-over does not work.

New

3BKA45FBR258768

It happened once that after an MLU activation, GPRS


service was lost in one cell redefined with capacity
extension and parameter changes

New

FRs removed since


BSSSAX01C Ed06
QD01

Short Description

Status

3BKA20FBR204709

Some indicators are missing in AD graphical display of


views or reports
It may happen that an A9130 MFS Evolution crashes during
a port security scan

3BKA20FBR231664

No-Q1-connection to TC boards

CLOSE OUT

3BKA20FBR235232

The opening of the IMT from the HMI takes a very long time

CLOSE REL

3BKA17FBR253015

CLOSE REL
CLOSE REL

3BKA20FBR238351

AXADMIN account gets lost as only SEC Database or LDAP


Database may be corrupted after a spontaneous reboot of
the OMC-R
In some cases, MFS Evolution auto backup does not work
anymore after migration to B10
No GPRS available when NH/RH is set on mixed
GSM/EGSM cells
A lock of the active SWW board leads to an outage of the
related MUX and OMCP boards

CLOSE NRE

3BKA20FBR238654

TCIF supervision is lost at OMC side

CLOSE REL

3BKA20FBR237652
3BKA20FBR238271
3BKA20FBR238302

3BKA20FBR241588
3BKA20FBR247623
3BKA20FBR252763
3BKA32FBR244317
3BKA36FBR253452

New FRs introduced


from BSSSAX01C
Ed06

CLOSE REL
CLOSE REL
CLOSE REL

An MT120 board in HSI mode cannot be configured from


TC-NEM
Number indicators (i.e. not % indicators) have values
multiplied or divided by 10
When using a PRC for the creation of HO and Reselection
relations on a large number of BSSs, for some cells only the
HO creation request is sent to the BSC
The addition of a new HMI is partially successful since the
Iconbox can not be then opened.
Three commands offering some facilities in case of remote
inventory and BTS/BSS reconfiguration are temporarily
missing in the BSC Terminal

CLOSE NRE

Short Description

Status

CLOSE REL
CLOSE REL

CLOSE REL
CLOSE REL

3BKA17FBR253015

Some indicators are missing in AD graphical display of


views or reports

New

3BKA20FBR249922

Inactive objects not reported by NPO Administration

New

3BKA20FBR250509

Online help is not working from DSMUSM window

New

3BKA20FBR251234
3BKA20FBR252362
3BKA20FBR252763
3BKA20FBR252795

ED

Short Description

01

Sometimes, the GPRS traffic is lost after the switchover of


an ATCA-F300 switch.
If MPM is stopped for any reason, there is no easy way to
restart it
When using a PRC for the creation of HO and Reselection
relations on a large number of BSSs, for some cells only the
HO creation request is sent to the BSC
In some cases, it is not possible to open the AD of MPM on
an HMI

Released

11/25/2009

New
New
New
New

BSS RESTRICTIONS LIST


BSSSAX01C Ed07 QD5
RELEASE B10
3BK 13016 1261 TQZZA
11/103

All rights reserved. Passing on and copying of this


document, use and communication of its contents not
permitted without written authorization from Alcatel-Lucent

New FRs introduced


from BSSSAX01C
Ed06
3BKA36FBR253452

FRs removed since


BSSSAX01C Ed06

Status

Three commands offering some facilities in case of remote


inventory and BTS/BSS reconfiguration are temporarily
missing in the BSC Terminal

Short Description

New

Status

3BKA20FBR224949

Cursor synchronization can not be used when the x-axis


scale contains a considerable number of values
Loss of some GPU boards when Full Intra RA feature is
activated

CLOSE REL

3BKA20FBR225553

SSW fault after unplug/plug standby SSW

CLOSE REL

3BKA20FBR227711

TP fatal termination leads to loss of traffic on the whole BSS

CLOSE REL

3BKA17FBR245355

CLOSE REL

3BKA20FBR243808

AGCH resources unusable after BSC legacy to BSC


Evolium replacement
Standby MUX disabled after changing the MxMFS
synchronization
The Lock / Unlock of the MT120-xB boards is not possible
from the OMC-R
The export can take a very long time even be blocked after
the execution of a report for more than 14 cells
After an HMI reboot or the OMC-R alarms directly visible in
OMC ASUSM feature activation, repeated OMC-R alarms
appear without any reason

3BKA20FBR243054

Frequent crash of BSSUSM after TC declaration or removal

CLOSE REL

3BKA20FBR243803

After an OMC reboot, some USM applications cannot be


launched from the HMI

CLOSE REL

3BKA20FBR244136

SSW boards become fault after lock-unlock action

CLOSE REL

3BKA20FBR244533

Router redundancy is not working in One-LAN configuration

CLOSE REL

3BKA20FBR231781
3BKA20FBR232211
3BKA20FBR237215
3BKA20FBR247775
3BKA20FBR242832
3BKA20FBR242867

3BKA20FBR245253
3BKA20FBR245397

New FRs introduced


from BSSSAX01C
Ed03 QD03A
3BKA20FBR229678
3BKA20FBR229821
3BKA20FBR237215
3BKA20FBR247775

Wrong aggregation method used in Availability indicator


calculation for Cell 2G
After an A9130 BSC Evolution configuration from 2lan to
1lan, "link fail" errors occurred inducing a BSC terminal
unavailability after a while

Short Description

3BKA20FBR251592

01

CLOSE REL
CLOSE REL

CLOSE REL
CLOSE REL

The Lock / Unlock of the MT120-xB boards is not possible


from the OMC-R

New

Replacement Wizard is not accessible in HSI mode

3BKA20FBR251023

CLOSE REL

New

3BKA20FBR248886

3BKA20FBR250248

CLOSE NRE

FTP transfer is stopped after cell reselection source cell in


GBR to target cell in BE or in case of RT resources
preemption

3BKA20FBR241268

3BKA20FBR247623

CLOSE REL

Status

Error reported in DPCK after the MT120-WB board


introduction
On-line help is not working for most of the applications run
from the OMC-R Administration Facilities

3BKA20FBR238566

ED

Short Description

Number indicators (i.e. not % indicators) have values


multiplied or divided by 10
TCIF board naming is not the same from the OMC-R and
TC Terminal
The A9130 BSC Evolution extension systematically fails in
the particular case where this operation has been preceded
by an A9130 BSC Evolution reduction
Sometimes it may happen that it is not possible to open the
AS Current USM window

Released

11/25/2009

New
New
New
New
New
New
New

BSS RESTRICTIONS LIST


BSSSAX01C Ed07 QD5
RELEASE B10
3BK 13016 1261 TQZZA
12/103

FRs removed since


BSSSAX01C Ed03
QD03A
All rights reserved. Passing on and copying of this
document, use and communication of its contents not
permitted without written authorization from Alcatel-Lucent

3BKA20FBR227001
3BKA20FBR228393
3BKA20FBR235516
3BKA20FBR238566
3BKA20FBR241154
3BKA20FBR241366
3BKA20FBR241937

FRs removed since


BSSSAX01C Ed03
QD3
3BKA20FBR244132
3BKA20FBR244139
3BKA20FBR237384
3BKA20FBR235582
3BKA20FBR239711
3BKA20FBR226065
3BKA20FBR236279
3BKA20FBR217431
3BKA20FBR236693

New FRs introduced


from BSSSAX01C
Ed03 QD2

Status

Sporadic MT120 Restart raised on the same board during


Nominal CS+PS Traffic
After new alerter definition, Id can be displayed instead of
specific problem field in AS
No more handovers between some cells after the Move
BTS
MT120-xB capability is not correctly reported for HW1 and
HW2 boards
Increase of drop remote TC failure with MT120 NB and WB
in HSI mode
Bad OMC-R performances due to lss process using 12% of
CPU

Short Description

CLOSE REL
CLOSE REL
CLOSE NRE
CLOSE REL
CLOSE REL
CLOSE NRE

Status

The A9130 BSC Evolution reduction cannot be performed


successfully
A lock of the active CCP induces a loss of traffic on some
cells
Wrong configuration alarm when AGC in secondary of a
Shared Cell BTS while ANC in the primary
Cell recovery impossible when locking TRE carrying
BCCCH on a cell configured as BBH
In case of Ater satellite configuration, the GSL stays
disabled after the BSC stops to answer to the MFS during
around 10 seconds
After few hours of GSL congestion, BSC is silent during
around 30 seconds
Autonomous TP takeover occurred during Nominal CS + PS
Traffic
Flooding of ARP messages from A9130 BSC Evolution in
direct IP configuration

CLOSE REL
CLOSE REL
CLOSE REL
CLOSE REL
CLOSE REL
CLOSE REL
CLOSE REL
CLOSE REL

Short Description

Status

3BKA17FBR240648

Sometimes during parameter loading, one request may last


more than 1 hour

New

3BKA17FBR243914

Origin list filter is not working in NUART web page

New

3BKA17FBR245355
3BKA20FBR237435
3BKA20FBR238038

Cursor synchronization can not be used when the x-axis


scale contains a considerable number of values
It is not possible to perform a System Restore on the
STATION B of an MFS with DS10 server
Daylight saving time changes are not properly handled by
NPO

New
New
New

3BKA20FBR241366

Increase of drop remote TC failure with MT120 NB and WB


in HSI mode

New

3BKA20FBR241178

No more voice traffic in case of unavailability of both TCIF

New

3BKA20FBR241154

3BKA20FBR241588
3BKA20FBR241937
3BKA20FBR242832
3BKA20FBR242867
3BKA20FBR243808

ED

Short Description

01

An MT120 board in HSI mode cannot be configured from


TC-NEM
Bad OMC-R performances due to lss process using 12% of
CPU
The export can take a very long time even be blocked after
the execution of a report for more than 14 cells
After an HMI reboot or the OMC-R alarms directly visible in
OMC ASUSM feature activation, repeated OMC-R alarms
appear without any reason

Released

11/25/2009

New
New
New
New

BSS RESTRICTIONS LIST


BSSSAX01C Ed07 QD5
RELEASE B10
3BK 13016 1261 TQZZA
13/103

All rights reserved. Passing on and copying of this


document, use and communication of its contents not
permitted without written authorization from Alcatel-Lucent

New FRs introduced


from BSSSAX01C
Ed03 QD2

Short Description

Status

3BKA20FBR242898

After a reset data of all GP from IMT, some alarms appear


on other NEs

New

3BKA20FBR242962

Fake counters after OMC-BSC communication problems

New

3BKA20FBR243054

Frequent crash of BSSUSM after TC declaration or removal

New

3BKA20FBR243803
3BKA20FBR243912

After an OMC reboot, some USM applications cannot be


launched from the HMI
The TCIF is not supervised by another OMC considered as
Spare after applying "OMC Disaster/Recovery" scenario

New

3BKA20FBR244139

The A9130 BSC Evolution reduction cannot be performed


successfully

New

3BKA20FBR244136

SSW boards become fault after lock-unlock action

New

DPCK tool generates too many alarms

New

Router redundancy is not working in One-LAN configuration

New

3BKA20FBR244132

3BKA20FBR244156
3BKA20FBR244780
3BKA20FBR244533
3BKA20FBR245253
3BKA20FBR245397
3BKA32FBR244317

FRs removed since


BSSSAX01C Ed03
QD2
3BKA17FBR237710
3BKA20FBR233317
3BKA20FBR237019
3BKA20FBR237002
3BKA20FBR236567
3BKA20FBR231754
3BKA20FBR237507
3BKA20FBR239990
3BKA20FBR225400
3BKA20FBR237224

ED

New

Wrong aggregation method used in Availability indicator


calculation for Cell 2G
After an A9130 BSC Evolution configuration from 2lan to
1lan, "link fail" errors occurred inducing a BSC terminal
unavailability after a while
The addition of a new HMI is partially successful since the
Iconbox can not be then opened.

Short Description

New
New
New

Status

Main jobs are set to disabled after a Stop/Start NPO


Re-create SGSN_IPendpoint operation fails when the GPU
is locked
A RESET of the SSW active provokes a RESET of the
ACTIVE OMCP & hence a takeover
A lot of DTCs reset after MLU activation

CLOSE REL
CLOSE REL
CLOSE REL
CLOSE REL

A lock of the active TP board induces a start/reset that leads


to a loss of the nominal traffic
It is not possible to declare more than 31 BCCH for
neighbor cells in case of 2G-3G reselection
New call can not be established after BCCH recovery in
BBH cell
In Gb over IP configuration (dynamic addressing), downlink
traffic does not resume after a control station switchover
BSSUSM fails when performing Display of VCE during an
Alarm Audit
Alc_Mono_LLC_Distribution can not be generated per cell
zone

CLOSE REL
CLOSE REL
CLOSE REL
CLOSE REL
CLOSE REL
CLOSE REL

3BKA20FBR237906

Diagnosis scheduling is not working

CLOSE REL

3BKA20FBR237907

Not possible to open diagnosis editor

CLOSE REL

3BKA20FBR237225

Detailed mode execution of diagnosis fails in AD

CLOSE REL

3BKA20FBR229704

Some incorrect BSC level parameters on NPO compared to


RNO

CLOSE REL

3BKA20FBR229394

No information displayed in TopN cell unavailability report

CLOSE REL

3BKA20FBR236850

Secure Single Gb feature: loss of GPRS after re-initialization


of a secured cell

CLOSE REL

3BKA20FBR238182

TC-NEM cannot be launched on PC with windows 2000

CLOSE REL

3BKA20FBR239200

Sometimes, MT120_WB board does not appear in TC_NEM


terminal after replacing an MT120 legacy

CLOSE REL

01

Released

11/25/2009

BSS RESTRICTIONS LIST


BSSSAX01C Ed07 QD5
RELEASE B10
3BK 13016 1261 TQZZA
14/103

FRs removed since


BSSSAX01C Ed03
QD2
All rights reserved. Passing on and copying of this
document, use and communication of its contents not
permitted without written authorization from Alcatel-Lucent

3BKA20FBR228455
3BKA20FBR228759
3BKA20FBR228929
3BKA20FBR229370
3BKA20FBR229309

Short Description

Status

Reshuffling never terminates when one GPU has a secured


Gb
In overload conditions, some failures remain in a pure EDA
environment
There has been observed differences between NPO reports
and raw data available in NUART
RMS Start/Stop time wrong after summer to winter time
change
Some inconsistencies between the TopN basic unavailability
report and the results provided by NUART

CLOSE REL
CLOSE REL
CLOSE REL
CLOSE REL

3BKA20FBR229311

Incomplete information for management alarm reports

CLOSE REL

3BKA20FBR230420

N7 names and objects are not correctly present in topology

CLOSE REL

3BKA20FBR230439
3BKA20FBR237764

Reverse MLU procedure leads to adjacencies


inconsistencies
OBSAL process stops when reaching a PMRES corrupted
file generated during a Move BTS from a G2 BSC to an
A9130 BSC Evolution

CLOSE REL
CLOSE REL

3BKA20FBR240666

Data from removed equipment are still stored in the OMC-R

CLOSE REL

3BKA20FBR228937
3BKA20FBR229298

Duplicated information present in AD

CLOSE REL

3BKA20FBR229395

Duplicate information provided by TopN unavailability and


TopN basic unavailability reports

CLOSE REL

The timer 1200 Sec expired when doing the query Inefficient
LOG/ALARM_COUNT_REC

CLOSE REL

3BKA20FBR239257
3BKA20FBR239786

3BKA20FBR238448

Incorrect Global Transmission report Data compared to


NUART
BSC may have no traffic during a long time due to telecom
overload on one DTC
After delete the MFS links for an Atermux changed from
mixed to direct the align MFS links action fails
In seldom cases, after launching manual consolidation, the
actions result is successful in the Follow up, but Daily data
and Hourly data are partially OK
Cell reselection not possible from one cell towards another
having a BCCH frequency 124 (GSM 900 band limit)

CLOSE NRE

3BKA20FBR237255

External NE not manageable from UFM (menus missing)

CLOSE NRE

3BKA20FBR228940

Some indicators have wrong values in alarm synthesis


reports

CLOSE REL

3BKA20FBR233824
3BKA20FBR233948
3BKA20FBR229372
3BKA20FBR232429

New FRs introduced


from BSSSAX01C
Ed03
3BKA17FBR237710
3BKA20FBR224338
3BKA20FBR237453
3BKA20FBR228929
3BKA20FBR228937

Short Description

CLOSE REL
CLOSE REL
CLOSE REL
CLOSE REL

Status

Main jobs are set to disabled after a Stop/Start NPO


In case of synthetic mode, after launching a query with 10
cells and one diagnosis scenario, an error message is
received
There has been observed differences between NPO reports
and raw data available in NUART
Duplicated information present in AD

New
New
New
New

3BKA20FBR229298

3BKA20FBR229309

Some indicators have wrong values in alarm synthesis


reports
Some inconsistencies between the TopN basic unavailability
report and the results provided by NUART

3BKA20FBR229311

Incomplete information for management alarm reports

New

3BKA20FBR229394

No information displayed in TopN cell unavailability report

New

3BKA20FBR228940

ED

CLOSE REL

01

Released

11/25/2009

New
New

BSS RESTRICTIONS LIST


BSSSAX01C Ed07 QD5
RELEASE B10
3BK 13016 1261 TQZZA
15/103

All rights reserved. Passing on and copying of this


document, use and communication of its contents not
permitted without written authorization from Alcatel-Lucent

New FRs introduced


from BSSSAX01C
Ed03

Status

3BKA20FBR229704

Duplicate information provided by TopN unavailability and


TopN basic unavailability reports
Some incorrect BSC level parameters on NPO compared to
RNO

3BKA20FBR230414

Incorrect display of RIDM statistics

New

3BKA20FBR230420

N7 names and objects are not correctly present in topology

New

3BKA20FBR229395

3BKA20FBR233948

Reverse MLU procedure leads to adjacencies


inconsistencies
"REDUNDANCY-48V-LOSS" alarm for LIU PEM does not
allow to conclude which board is faulty
In seldom cases, after launching manual consolidation, the
actions result is successful in the Follow up, but Daily data
and Hourly data are partially OK
Incorrect Global Transmission report Data compared to
NUART
BSC may have no traffic during a long time due to telecom
overload on one DTC

3BKA20FBR235232

The opening of the IMT from the HMI takes a very long time

3BKA20FBR230439
3BKA20FBR231296
3BKA20FBR232429
3BKA20FBR233824

3BKA20FBR236850

After new alerter definition, Id can be displayed instead of


specific problem field in AS
No more handovers between some cells after the Move
BTS
Wrong configuration alarm when AGC in secondary of a
Shared Cell BTS while ANC in the primary
After few hours of GSL congestion, BSC is silent during
around 30 seconds
A lock of the active TP board induces a start/reset that leads
to a loss of the nominal traffic
Flooding of ARP messages from A9130 BSC Evolution in
direct IP configuration
Secure Single Gb feature: loss of GPRS after re-initialization
of a secured cell

3BKA20FBR237002

A lot of DTCs reset after MLU activation

3BKA20FBR235439
3BKA20FBR235516
3BKA20FBR235582
3BKA20FBR236279
3BKA20FBR236567
3BKA20FBR236693

3BKA20FBR237507
3BKA20FBR237255

External NE not manageable from UFM (menus missing)

3BKA20FBR237224
3BKA20FBR237384

3BKA20FBR237652

3BKA20FBR237764

New
New

New
New
New
New
New
New
New
New
New
New
New
New
New
New

A RESET of the SSW active provokes a RESET of the


ACTIVE OMCP & hence a takeover
Alc_Mono_LLC_Distribution can not be generated per cell
zone
A lock of the active CCP induces a loss of traffic on some
cells
New call can not be established after BCCH recovery in
BBH cell

3BKA20FBR237019

AXADMIN account gets lost as only SEC Database or LDAP


Database may be corrupted after a spontaneous reboot of
the OMC-R
OBSAL process stops when reaching a PMRES corrupted
file generated during a Move BTS from a G2 BSC to an
A9130 BSC Evolution

New
New
New
New
New
New

New

3BKA20FBR237906

Diagnosis scheduling is not working

New

3BKA20FBR237907

Not possible to open diagnosis editor

New

3BKA20FBR237225

Detailed mode execution of diagnosis fails in AD

New

3BKA20FBR238182

TC-NEM cannot be launched on PC with windows 2000

New

3BKA20FBR238271
3BKA20FBR238351
3BKA20FBR238448

ED

Short Description

01

In some cases, MFS Evolution auto backup does not work


anymore after migration to B10
A lock of the active SWW board leads to an outage of the
related MUX and OMCP boards
Cell reselection not possible from one cell towards another
having a BCCH frequency 124 (GSM 900 band limit)

Released

11/25/2009

New
New
New

BSS RESTRICTIONS LIST


BSSSAX01C Ed07 QD5
RELEASE B10
3BK 13016 1261 TQZZA
16/103

All rights reserved. Passing on and copying of this


document, use and communication of its contents not
permitted without written authorization from Alcatel-Lucent

New FRs introduced


from BSSSAX01C
Ed03

Status

3BKA20FBR238566

MT120-xB capability is not correctly reported for HW1 and


HW2 boards

New

3BKA20FBR238654

TCIF supervision is lost at OMC side

New

3BKA20FBR239200
3BKA20FBR239248
3BKA20FBR239257
3BKA20FBR239786

Sometimes, MT120_WB board does not appear in TC_NEM


terminal after replacing an MT120 legacy
In BSSusmMAIN view, it may happen that TC boards are
not displayed correctly

New

The timer 1200 Sec expired when doing the query Inefficient
LOG/ALARM_COUNT_REC

New

New

3BKA20FBR239990

Not possible to open tuning browser on HMI with other user


than axadmin
Cell recovery impossible when locking TRE carrying
BCCCH on a cell configured as BBH
In Gb over IP configuration (dynamic addressing), downlink
traffic does not resume after a control station switchover

3BKA20FBR240666

Data from removed equipment are still stored in the OMC-R

New

Short Description

Status

3BKA20FBR239669
3BKA20FBR239711

FRs removed since


BSSSAX01C Ed03
3BKA20FBR187568
3BKA20FBR209551
3BKA20FBR211063

3BKA20FBR212685

3BKA20FBR214151
3BKA20FBR220025
3BKA20FBR223130
3BKA20FBR223810
3BKA20FBR225006
3BKA20FBR225666
3BKA20FBR226586
3BKA20FBR227108
3BKA20FBR227193
3BKA20FBR228426
3BKA32FBR229185
3BKA20FBR229377
3BKA20FBR230000
3BKA20FBR230372
3BKA20FBR230703

ED

Short Description

01

From trace viewer application, it is impossible to export the


results of an ODMC campaign with files related to type 11
counters
BSSIM process is frozen when switching from N7 LSL to
N7 HSL
Cases of cell alarms not automatically cleared in RNUSM
despite the alarm was actually cleared in the
An Atermux granularity modification change from 100%
Mixed GPRS to 100% or 0% Dedicated GPRS or reverse is
declared failed by the OMC-R because of a missing HWRESYNCH from the BSC Evolution
A Reset all on all the GPUs of a Multi-GPU configuration
leads to GPU reboot in loop when one GPU is secured
(Secured Single Gb feature active)
Incorrect averaging in some NPO Views

New
New
New

CLOSE REL
CLOSE REL
CLOSE NRE

CLOSE REL

CLOSE REL
CLOSE REL

Cannot access the MRTG data for a BSC Evolution after


Add BSS
Instabilities on the LAPD lead to several GP reset when
EDA is activated
The A9120 BSC move between a master and an agent fails
except if manually done
Sometimes, when EDA is activated, some instabilities on the
GSLs lead to GP reset
Lock Active TP may lead to the no triggering of a TP
takeover
The usage of the new generation of OSI-CPR board leads to
a faulty X25 link every few days
Wrong encoding of IE "Inter-System Transparent
Information"

CLOSE NRE
CLOSE OUT
CLOSE REL
CLOSE NRE
CLOSE REL
CLOSE REL
CLOSE REL

GPRS outage for the cell during the reshuffling period

CLOSE REL

The Export BSS process fails for A9130 BSC Evolution

CLOSE REL

After OMCP replacement, the replaced board is displayed


disabled in OMCR, but enabled at BSC side
A Lock of the active CCP board leads to a loss of Nominal
Traffic
[3,14] WRONG-CONFIGURATION (RA) alarm periodically
appears on BTSs having different output power for the
same sector
A lot of DTC restart cause OBCI_RESET are raised with
DTM traffic

Released

11/25/2009

CLOSE REL
CLOSE REL
CLOSE OUT
CLOSE REL

BSS RESTRICTIONS LIST


BSSSAX01C Ed07 QD5
RELEASE B10
3BK 13016 1261 TQZZA
17/103

FRs removed since


BSSSAX01C Ed03
All rights reserved. Passing on and copying of this
document, use and communication of its contents not
permitted without written authorization from Alcatel-Lucent

3BKA20FBR230924
3BKA20FBR231511
3BKA20FBR231512
3BKA20FBR231583

Status

HMI removal is not possible

CLOSE REL

The OBSYNT and PMTAR files are not generated for the
B10 A9130 MFS Evolution GP boards
Unitary report is not generated when performing a DLS
backup from the OMC-R
It may happen that no TC is displayed in ENSUSM

CLOSE REL
CLOSE REL
CLOSE NRE

It is not possible to modify the OMC-R secondary address


from the DCN window
In a general way, the MFS does not generate the PM report
after 10:00 am
In case of HO cause 28, RAM does not give information how
the channel rate from 'Fast Traffic HO Request' message is
established.

CLOSE NRE

3BKA20FBR232121

GPs blocked after performing a RESET DATA

CLOSE REL

3BKA20FBR233135

The search function for INSPAW is not working properly

CLOSE OUT

3BKA20FBR233137

MPM not automatically restarted when Legato backup is not


successful

CLOSE NRE

Short Description

Status

3BKA20FBR204709

It may happen that an A9130 MFS Evolution crashes during


a port security scan

New

3BKA20FBR212839

Spare GP is rebooting in loop

New

3BKA20FBR231778
3BKA20FBR231845
3BKA20FBR232084

New FRs introduced


from BSSSAX01C
Ed02

CLOSE REL

CLOSE REL

3BKA20FBR227193

The insecure FTP and Telnet services for A9130 MFS and
BSC Evolution should be disabled, because SSH is
available
BSSUSM fails when performing Display of VCE during an
Alarm Audit
Lock Active TP may lead to the no triggering of a TP
takeover
Sporadic MT120 Restart raised on the same board during
Nominal CS+PS Traffic
The usage of the new generation of OSI-CPR board leads to
a faulty X25 link every few days
Wrong encoding of IE "Inter-System Transparent
Information"

3BKA20FBR227711

TP fatal termination leads to loss of traffic on the whole BSS

New

3BKA20FBR228426

GPRS outage for the cell during the reshuffling period

New

3BKA20FBR219689
3BKA20FBR225400
3BKA20FBR226586
3BKA20FBR227001
3BKA20FBR227108

3BKA20FBR228759

Reshuffling never terminates when one GPU has a secured


Gb
In overload conditions, some failures remain in a pure EDA
environment

3BKA20FBR229377

After OMCP replacement, the replaced board is displayed


disabled in OMCR, but enabled at BSC side

3BKA20FBR228455

New
New
New
New
New
New

New
New
New

3BKA20FBR230703

A Lock of the active CCP board leads to a loss of Nominal


Traffic
[3,14] WRONG-CONFIGURATION (RA) alarm periodically
appears on BTSs having different output power for the
same sector
The violation of the rule Maximum 64 HOs per BSC can
lead to corruptions
A lot of DTC restart cause OBCI_RESET are raised with
DTM traffic

3BKA20FBR230924

HMI removal is not possible

New

3BKA20FBR231044

A lot of messages DTM assignment failure cause TS in


inconsistent state with DTM traffic

New

3BKA20FBR230000
3BKA20FBR230372
3BKA20FBR230654

ED

Short Description

01

Released

11/25/2009

New
New
New
New

BSS RESTRICTIONS LIST


BSSSAX01C Ed07 QD5
RELEASE B10
3BK 13016 1261 TQZZA
18/103

All rights reserved. Passing on and copying of this


document, use and communication of its contents not
permitted without written authorization from Alcatel-Lucent

New FRs introduced


from BSSSAX01C
Ed02
3BKA20FBR231204

Status

The network_info.pl script contains many errors

New

3BKA20FBR231512

The OBSYNT and PMTAR files are not generated for the
B10 A9130 MFS Evolution GP boards
Unitary report is not generated when performing a DLS
backup from the OMC-R

3BKA20FBR231583

It may happen that no TC is displayed in ENSUSM

New

3BKA20FBR231664

No-Q1-connection to TC boards

New

3BKA20FBR231511

New
New

3BKA20FBR231845

It is not possible to declare more than 31 BCCH for


neighbor cells in case of 2G-3G reselection
It is not possible to modify the OMC-R secondary address
from the DCN window
AGCH resources unusable after BSC legacy to BSC
Evolium replacement
In a general way, the MFS does not generate the PM report
after 10:00 am

3BKA20FBR232033

Frequent OMC-BSC Evolution disconnections

New

3BKA20FBR232121

GPs blocked after performing a RESET DATA

New

3BKA20FBR231754
3BKA20FBR231778
3BKA20FBR231781

3BKA20FBR233317

Secure Single Gb feature is not compatible with multi-GPU


configuration and leads to O&M outage
Re-create SGSN_IPendpoint operation fails when the GPU
is locked

3BKA32FBR229185

The Export BSS process fails for A9130 BSC Evolution

3BKA20FBR232169

FRs removed since


BSSSAX01C Ed02
3BKA17FBR225284
3BKA20FBR214845
3BKA20FBR215301
3BKA20FBR220893

Short Description

New
New
New
New

New
New
New

Status

Search function is unavailable in AD On-Line Help


Sporadic loss of calls when a lock of the active TP is done
on an A9130 BSC Evolution
Very sporadically a Reset of the Active TP fails with the
alarm ATCA-PROCESSOR [97] ACCESS FAIL [3].

CLOSE REL
CLOSE NRE
CLOSE REL

Sporadic CU Restart cause 22 during Nominal Traffic

CLOSE REL

3BKA20FBR222388

Hourly data per cell zone are not available

CLOSE REL

3BKA20FBR226257

Re-creation of NSCV/SGSN IP Endpoints objects after a


switching from FR mode to IP mode leads to a GOM crash

CLOSE REL

New FRs introduced


from BSSSAX01C
Ed01 QD02
3BKA20FBR232084

FRs removed since


BSSSAX01C Ed01
QD02

ED

Short Description

Short Description

Status

In case of HO cause 28, RAM does not give information how


the channel rate from 'Fast Traffic HO Request' message is
established.

New

Short Description

Status

3BKA20FBR221422

Sporadic CU Restart cause 10 during Nominal CS+PS


Traffic

CLOSE NRE

3BKA20FBR224871

TCU restart Error Type:Illegal_CALL FMMID:15

CLOSE REL

3BKA20FBR224952

Unplug/plug FAN unsuccessful with FAN RPM alarm

CLOSE REL

3BKA20FBR226096

Impacted SW version (B10 MR1/Ed2 with G2 BSC ELS)


crashed after BSC reset to active ELS.

CLOSE REL

01

Released

11/25/2009

BSS RESTRICTIONS LIST


BSSSAX01C Ed07 QD5
RELEASE B10
3BK 13016 1261 TQZZA
19/103

FRs removed since


BSSSAX01C Ed01
QD02
All rights reserved. Passing on and copying of this
document, use and communication of its contents not
permitted without written authorization from Alcatel-Lucent

3BKA20FBR226129

New FRs introduced


from BSSSAX01C
Ed01 QD01
3BKA20FBR228309

FRs removed since


BSSSAX01C Ed01
QD01

Status

GPRS Atermux declaration changes the impact on other


Atermux

Short Description

CLOSE REL

Status

The replacement of an OMCP board loaded with a different


software leads to a decreasing of the nominal traffic and to
the loss of connection with the OMC-R and the BSC
Evolution terminal

New

Short Description

Status

3BKA17FBR219704

Empty values for hourly data on vectors mapped on Array of


scalar counters

CLOSE REL

3BKA17FBR222280

Weekly consolidation fails on some machine

CLOSE REL

3BKA20FBR225210

There are big differences for many GPRS indicators


between NPO and RNO

CLOSE REL

New FRs introduced


from BSSSAX01C
Ed01

Short Description

Status

3BKA17FBR222280

Weekly consolidation fails on some machine

New

3BKA17FBR225284

Search function is unavailable in AD On-Line Help

New

3BKA20FBR217431

There is no alarm displayed on the IMT when the standby


MUX board is extracted
Sporadic loss of calls when a lock of the active TP is done
on an A9130 BSC Evolution
Very sporadically a Reset of the Active TP fails with the
alarm ATCA-PROCESSOR [97] ACCESS FAIL [3].
Autonomous TP takeover occurred during Nominal CS + PS
Traffic

3BKA20FBR220025

Incorrect averaging in some NPO Views

New

3BKA20FBR220893

Sporadic CU Restart cause 22 during Nominal Traffic

New

3BKA20FBR221422

Sporadic CU Restart cause 10 during Nominal CS+PS


Traffic

New

3BKA20FBR221793

In case of fans failure, the A9130 BSC Evolution is not


automatically powered off.

Moved from
SM

3BKA20FBR222388

Hourly data per cell zone are not available

3BKA20FBR210268
3BKA20FBR214845
3BKA20FBR215301

3BKA20FBR223810
3BKA20FBR224483
3BKA20FBR225006
3BKA20FBR225210
3BKA20FBR225666
3BKA20FBR226065
3BKA20FBR226096
3BKA20FBR226257

ED

Short Description

01

Instabilities on the LAPD lead to several GP reset when


EDA is activated
Alc_Mono_Call report maybe unsuccessful if created for a
great number of cells with a large covered period
The A9120 BSC move between a master and an agent fails
except if manually done
There are big differences for many GPRS indicators
between NPO and RNO
Sometimes, when EDA is activated, some instabilities on the
GSLs lead to GP reset
In case of Ater satellite configuration, the GSL stays
disabled after the BSC stops to answer to the MFS during
around 10 seconds
Impacted SW version (B10 MR1/Ed2 with G2 BSC ELS)
crashed after BSC reset to active ELS.
Re-creation of NSCV/SGSN IP Endpoints objects after a
switching from FR mode to IP mode leads to a GOM crash

Released

11/25/2009

New
New
New
New

New
New
New
New
New
New
New
New
New

BSS RESTRICTIONS LIST


BSSSAX01C Ed07 QD5
RELEASE B10
3BK 13016 1261 TQZZA
20/103

All rights reserved. Passing on and copying of this


document, use and communication of its contents not
permitted without written authorization from Alcatel-Lucent

FRs removed since


BSSSAX01C Ed01

Short Description

Status
CLOSE NIP

3BKA17FBR197501

Selecting the same frequency for two different TRX during


one frequency tuning operation is allowed but should not

3BKA17FBR197758

Setting the BCCH frequency on 2 ARFCNs is allowed but it


should not be

Updated in
Customer
Documentation
CLOSE NIP

BH Indicators needed to compute DAV Indicators are not


generated automatically by NPO
Memory used by AD increases quickly for tuning operations
done in a Working Zone with a great number of cells.

CLOSE REL

3BKA17FBR209279

AD is not opened because MAAT TOPO process is hanging

CLOSE REL

3BKA17FBR210098

Thematic layer execution for adjacencies is not working

CLOSE REL

3BKA17FBR210578

SEC sporadically becomes blocked when updating user


profile

CLOSE REL

3BKA17FBR210682

Basic indicator with one step interpolation cannot be created

CLOSE REL

3BKA17FBR203725
3BKA17FBR208586

3BKA17FBR211360
3BKA17FBR211508
3BKA17FBR211967
3BKA17FBR213087
3BKA17FBR213989
3BKA17FBR215145
3BKA17FBR215871
3BKA17FBR218294
3BKA17FBR216567
3BKA17FBR217462
3BKA17FBR217586
3BKA17FBR218000
3BKA17FBR218312
3BKA17FBR218434
3BKA17FBR218445
3BKA17FBR218481
3BKA17FBR218690
3BKA17FBR219427
3BKA17FBR219519
3BKA17FBR219692
3BKA17FBR209842
3BKA17FBR210445
3BKA17FBR210633
3BKA17FBR220015

ED

Updated in
Customer
Documentation

01

CLOSE REL

In case of NPO embedded in OMC-R, Analysis Desktop on


Solaris may sometimes exit unexpectedly
OSB Backup/Restore mechanism does not support multiple
tapes
The parameters are not updated anymore after a network
element is moved to/reported by a different OMC
ASM (Automatic Storage Management) can not be used on
a server which hostname contains capital letters

Moved in SM

It is not possible to drill drown from traffic zone to TRX

CLOSE REL

Bad xml result for EQL requests on vector with hourly


periodicity
The no deletion of B9/B10 PM files leads to the blocking of
NPO machine
Parameter values are not correct when choosing a date
where the object was soft-deleted
Four design parameters from B9 RNO are not found in NPO
parameters dictionary
NPO cannot load B10 BSCs containing a "-" in their name
Query with stored customer indicator AND stored system
indicator provides no value
Data may appear as missing in reports executed for certain
period within one day
Strange behavior in trends for the first two hours of the day
Whatever the time zone used for NPO installation, the PM
file import follow-up always displays the data in
Europe/Paris time zone.
Admin web does take correctly into account the Time Zone
to retrieve the recovered data.
View execution on current day can lead to incorrect values
due to time shift not correctly taken into account
Field "Support Dynamic interpolation" in the indicator editor
is not correctly managed
Iconbox may not start after a longer period of extensive
usage of the NPO machine
NPO partitioning creation does not handle correctly the DST
(hour change)
Conflicting network level values when NPO is not empty
when data is imported
Some HO indicators will not be migrated at TRX level from
B9 MR1 NPA
Empty values for views executed on Adjacencies for hourly

Released

11/25/2009

CLOSE REL
CLOSE REL
CLOSE REL

CLOSE REL
CLOSE REL
CLOSE REL
CLOSE REL
CLOSE REL
CLOSE REL
CLOSE REL
CLOSE REL
CLOSE REL
CLOSE REL
CLOSE REL
CLOSE REL
CLOSE REL
CLOSE REL
CLOSE OUT
CLOSE REL
CLOSE REL

BSS RESTRICTIONS LIST


BSSSAX01C Ed07 QD5
RELEASE B10
3BK 13016 1261 TQZZA
21/103

FRs removed since


BSSSAX01C Ed01

Short Description

Status

All rights reserved. Passing on and copying of this


document, use and communication of its contents not
permitted without written authorization from Alcatel-Lucent

values
3BKA17FBR220036
3BKA17FBR221054
3BKA17FBR224588
3BKA20FBR203134
3BKA20FBR203489
3BKA20FBR203884

3BKA20FBR205579

3BKA20FBR209350
3BKA20FBR209413
3BKA20FBR211016

3BKA20FBR211413

3BKA20FBR211766
3BKA20FBR212604
3BKA20FBR213188
3BKA20FBR213583
3BKA20FBR212094

3BKA20FBR214039

3BKA20FBR215422

3BKA20FBR215694
3BKA20FBR216651
3BKA20FBR216926
3BKA20FBR217672
3BKA20FBR219046
3BKA20FBR219569
3BKA20FBR219570
3BKA20FBR219601
3BKA20FBR219666

ED

01

Bad consolidation performed for indicators having


interpolation in two steps
Busy Hour production takes a long time when the statistics
are not activated in Oracle database
NPO shows value of the parameter after the purge date
When performing an A9130 BSC Evolution extension from
Type 1 to Type 2, the new CCP board seems to stay in the
standby status.
When a view contains values with different units (non
numerical data), the sorting does not work properly.
The reference name (RefName) for counters and indicators
is missing in the "drag&drop" area of Analysis Desktop
window.
Whatever the A9130 MFS Evolution configuration, when the
Remote Inventory is performed from the IMT through the
Site View path, the rack and the shelf number are wrong
for all the GP boards
It is not possible to create a G1 MKII BTS on a B9 G2 BSC
A double takeover of the MUX boards takes place when the
standby MUX board is removed from the LIU shelf
TMO MR4 PILOT:Show Counters from cell level not
working
When locking the JAXSSW and then unlocking the
corresponding JBXSSW, JAXSSW remains MSD in OMC-R
if OMC-BSC connection is lost and then recovered before
the JBXSSW initialization is finished.
The MFS is not able to manage more than 255 cells for one
BSC
When we change the Synchronization Mode for A9130 MFS
as described in 3DF 00300 0112 UAZZA Ed.07, there is a
problem to change the synchronizing PCM TTP
Fake N7 SBL created during consecutive Modify Atermux
granularity from mixed to dedicated 100% GPRS actions
The OMC-R alarms from the Master are not raised in AS
In case of MLPPP, the second TPGSM board is not booting
if it is plugged after a BSC reset or after an A9130 BSC
Evolution software installation
After modify GPRS Granularity from Dedicated to Mixed
(100%, 50%, 12%, 0%), the new ADAPT SBLs are not
reported immediately towards the OMC-R in the HW-Audit
BSC Reset, OMCP takeover, Reset standby OMCP, Reset
Shelf-Managers should not be performed when an SSW is
in the state FLT or OPR in the OMC-R BSSUSM Equipment
view
Replace JBXOMCP: the forced boot doesn't work using PC
in Windows 2000
Script "multiple_lan_setup.pl" isn't functioning due to wrong
ldap password.
Quite often a control station switchover appears after a
'RESET data of all GPUs' performed from the IMT
The creation of adjacencies via MLU fails during the predownload phase
A Lock Active OMCP can take more than 7 minutes to be
completed.
Consolidation failed during the Daily Spatial Aggregation for
RMS vector indicators.
Generic Loader is unable to load PM files when a low speed
connection is present between NPO and OMC servers
Radio parameters not loaded when huge number of
changes are present
Legato client configuration fails for long hostnames of NPO
server

Released

11/25/2009

CLOSE REL
CLOSE REL
Moved to OH
CLOSE REL
CLOSE REL
CLOSE REL

CLOSE REL

CLOSE REL
CLOSE REL
CLOSE REL

CLOSE REL

CLOSE REL
CLOSE REL
CLOSE REL
CLOSE REL
CLOSE REL

CLOSE OUT

CLOSE REL

CLOSE OUT
CLOSE REL
CLOSE NRE
CLOSE REL
CLOSE REL
CLOSE REL
CLOSE REL
CLOSE REL
CLOSE REL

BSS RESTRICTIONS LIST


BSSSAX01C Ed07 QD5
RELEASE B10
3BK 13016 1261 TQZZA
22/103

FRs removed since


BSSSAX01C Ed01
All rights reserved. Passing on and copying of this
document, use and communication of its contents not
permitted without written authorization from Alcatel-Lucent

3BKA20FBR219707
3BKA20FBR219985
3BKA20FBR220380
3BKA20FBR220381
3BKA20FBR220382
3BKA20FBR220383
3BKA20FBR220647

Status

Manual consolidation is not working in both recovery and


complete modes
NPO Server is unavailable after the launching of a manual
recovery consolidation

CLOSE REL
CLOSE REL

Failed GPMRES files are not deleted from NPO server

CLOSE REL

Missing values for some GPRS counters

CLOSE REL

For PVC and Bearer Channel tabs, the result of a


classification by MFS is an empty list
Error messages raised during the usage of Analysis
Desktop may lead to its blocking
Parameters can not be reloaded for current day in case of
ftp transfer failure.

CLOSE REL
CLOSE REL
CLOSE REL

3BKA20FBR220650

Wrong objects are present in the list of inactive objects

CLOSE REL

3BKA20FBR224521

Degradation of QOS for UL TBF release with internal cause


Reject_MS UL Access

CLOSE OUT

3BKA32FBR189303

It is not possible to create a G1 MKII BTS on a B9 G2 BSC

No more
relevant in
B10 scope

3BKA32FBR211470

SNMP alarms are cleared but raised back without any


reason

Moved in SM

3BKA36FBR212511

Standby CCP spontaneously resets several times per day

CLOSE REL

New FRs introduced


from BSSSAX01B
Ed02

Short Description

Status

3BKA17CBR208557

A manual consolidation unexpectedly interrupted in a


specific step cannot be resumed

New

3BKA17CBR211154

Only one RMS file can be loaded per day

New

3BKA17FBR208586

Memory used by AD increases quickly for tuning operations


done in a Working Zone with a great number of cells.

New

3BKA17FBR210098

Thematic layer execution for adjacencies is not working

New

3BKA17FBR213087

OSB Backup/Restore mechanism does not support multiple


tapes
The parameters are not updated anymore after a network
element is moved to/reported by a different OMC
ASM (Automatic Storage Management) can not be used on
a server which hostname contains capital letters

3BKA17FBR213989

It is not possible to drill drown from traffic zone to TRX

New

3BKA17FBR215145

Bad xml result for EQL requests on vector with hourly


periodicity

New

The no deletion of B9/B10 PM files leads to the blocking of


NPO machine

New

3BKA17FBR211508
3BKA17FBR211967

3BKA17FBR215871
3BKA17FBR218294

3BKA17FBR217462

Parameter values are not correct when choosing a date


where the object was soft-deleted
Four design parameters from B9 RNO are not found in NPO
parameters dictionary

3BKA17FBR217586

NPO cannot load B10 BSCs containing a "-" in their name

3BKA17FBR216567

New
New
New

New
New
New

3BKA17FBR218427

Query with stored customer indicator AND stored system


indicator provides no value
Data may appear as missing in reports executed for certain
period within one day
After a daylight saving, all hourly reports have data shifted
with one hour

3BKA17FBR218434

Strange behavior in trends for the first two hours of the day

New

3BKA17FBR218445

Whatever the time zone used for NPO installation, the PM


file import follow-up always displays the data in
Europe/Paris time zone.

New

3BKA17FBR218000
3BKA17FBR218312

ED

Short Description

01

Released

11/25/2009

New
New
New

BSS RESTRICTIONS LIST


BSSSAX01C Ed07 QD5
RELEASE B10
3BK 13016 1261 TQZZA
23/103

All rights reserved. Passing on and copying of this


document, use and communication of its contents not
permitted without written authorization from Alcatel-Lucent

New FRs introduced


from BSSSAX01B
Ed02
3BKA17FBR218481
3BKA17FBR218690
3BKA17FBR218778
3BKA17FBR219427
3BKA17FBR219447

3BKA17FBR219530
3BKA17FBR219519
3BKA17FBR219574
3BKA17FBR219692
3BKA17FBR209842

Status

Admin web does take correctly into account the Time Zone
to retrieve the recovered data.
View execution on current day can lead to incorrect values
due to time shift not correctly taken into account
It is impossible to get results for , periodicity in a view
for an user defined object zone and using a calculated
indicator
Field "Support Dynamic interpolation" in the indicator editor
is not correctly managed
After extensive use by maximum number of users, no other
new user connection can be established with the HMI server
due to Citrix instability
It is impossible to change a working zone from Global to 500
cells because the processes remaining hanged, the CPU
usage increases significantly
Iconbox may not start after a longer period of extensive
usage of the NPO machine
PM files cannot be loaded when a low speed connection is
present between NPO and OMC servers
NPO partitioning creation does not handle correctly the DST
(hour change)

New
New
New
New
New

New
New
New
New

3BKA20FBR219985

Empty values for hourly data on vectors mapped on Array of


scalar counters
Empty values for views executed on Adjacencies for hourly
values
Bad consolidation performed for indicators having
interpolation in two steps
Busy Hour production takes a long time when the statistics
are not activated in Oracle database
In case of MLPPP, the second TPGSM board is not booting
if it is plugged after a BSC reset or after an A9130 BSC
Evolution software installation
Quite often a control station switchover appears after a
'RESET data of all GPUs' performed from the IMT
The creation of adjacencies via MLU fails during the predownload phase
A Lock Active OMCP can take more than 7 minutes to be
completed.
Consolidation failed during the Daily Spatial Aggregation for
RMS vector indicators.
Generic Loader is unable to load PM files when a low speed
connection is present between NPO and OMC servers
Radio parameters not loaded when huge number of
changes are present
Legato client configuration fails for long hostnames of NPO
server
Manual consolidation is not working in both recovery and
complete modes
NPO Server is unavailable after the launching of a manual
recovery consolidation

3BKA20FBR220380

Failed GPMRES files are not deleted from NPO server

New

3BKA20FBR220381

Missing values for some GPRS counters

New

3BKA17FBR219704
3BKA17FBR220015
3BKA17FBR220036
3BKA17FBR221054
3BKA20FBR212094
3BKA20FBR216926
3BKA20FBR217672
3BKA20FBR219046
3BKA20FBR219569
3BKA20FBR219570
3BKA20FBR219601
3BKA20FBR219666
3BKA20FBR219707

New
New
New
New
New
New
New
New
New
New
New
New
New
New

3BKA20FBR220383

For PVC and Bearer Channel tabs, the result of a


classification by MFS is an empty list
Error messages raised during the usage of Analysis
Desktop may lead to its blocking

3BKA20FBR220405

No value loaded in NPO for EN_DTM parameter

New

3BKA20FBR220647

Parameters can not be reloaded for current day in case of


ftp transfer failure.

New

3BKA20FBR220650

Wrong objects are present in the list of inactive objects

New

3BKA20FBR220382

ED

Short Description

01

Released

11/25/2009

New
New

BSS RESTRICTIONS LIST


BSSSAX01C Ed07 QD5
RELEASE B10
3BK 13016 1261 TQZZA
24/103

FRs removed since


BSSSAX01B Ed02
All rights reserved. Passing on and copying of this
document, use and communication of its contents not
permitted without written authorization from Alcatel-Lucent

3BKA17FBR209572
3BKA17FBR210659
3BKA17FBR209785
3BKA17FBR209907
3BKA17FBR211083
3BKA17FBR213955
3BKA17FBR214144
3BKA17FBR214217
3BKA17FBR214448
3BKA17FBR214476
3BKA17FBR215635
3BKA17FBR216179
3BKA17FBR216188
3BKA20FBR199501
3BKA20FBR210784
3BKA20FBR211268

Short Description

Status

RMS indicators with boundary-type axis with fixed first/last


values not displayed
NPO Administration not usable after scheduled backup with
Legato

CLOSE REL

Only one RMS file can be loaded per day

CLOSE REL

Cannot edit an Object Zone when 'Absolute' field is not


checked
Computed vector indicators involving MIDDLE functions do
not work
The time from data available on the OMC-R till it is available
in NPO database is longer than expected on V880 hardware
configuration with 8000 cells
After creating an indicator the indicator tree is not directly
accessible
RNP data source cannot be updated from NPO
Administration menu
"Recovered data" operation fails from NPO Administration
window
The occupancy of /alcatel partition is too big for a 5000 cells
configuration on V880 machine
The disk activity is particularly high for a 5000 cells
configuration on V880 machine
Sometimes, BSCs and cells parameters are stored in NPO
with a wrong date
Sometimes, Analysis Desktop starting takes a long time
and induces an error message
OSB Restore failed due to SEGMENTATION FAULT error

3BKA20FBR214684
3BKA20FBR216318

MFS version is not correctly displayed in B9 GPMRES files

3BKA20FBR213976

3BKA20FBR216450
3BKA36FBR212100

New FRs introduced


from BSSSAX01B
Ed01

CLOSE REL
CLOSE REL
CLOSE REL
CLOSE REL
CLOSE REL
CLOSE REL
CLOSE REL
CLOSE REL
CLOSE REL
CLOSE REL
CLOSE NRE
CLOSE NRE
CLOSE REL
CLOSE REL
CLOSE REL

B9 GPMRES files are not sent to the B10 OMC-R on which


are declared both B9 MFSs and B10 MFSs with and without
security
Sometimes, the TP board stays in FLT status after its
removal/insertion

CLOSE REL

Short Description

Status

CLOSE REL

3BKA17FBR197758

Selecting the same frequency for two different TRX during


one frequency tuning operation is allowed but should not
Setting the BCCH frequency on 2 ARFCNs is allowed but it
should not be

New

3BKA17FBR202164

Some counters not migrated from B9 to B10

New

3BKA17FBR209279

AD is not opened because MAAT TOPO process is hanging

New

RMS data is loaded partially on NPO standalone

New

Basic indicator with one step interpolation cannot be created

New

3BKA17FBR197501

3BKA17FBR210491
3BKA17FBR213587
3BKA17FBR210682
3BKA17FBR211360
3BKA17FBR213142
3BKA17FBR213955

ED

CLOSE REL

Properties window on Tuning job cannot be opened

After a Logical Audit, the number of pure reselection


adjacencies doubles
Incorrect handling of pure reselection adjacency in OMC-R
after a BSS discover
NPO Stand alone: Server error MAAT common exception
message apperas at Analysis Desktop startup.

3BKA20FBR213803

CLOSE REL

01

In case of NPO embedded in OMC-R, Analysis Desktop on


Solaris may sometimes exit unexpectedly
Some computed indicators will not have historical values
after migration from B9 MR1 NPA
Cannot edit an Object Zone when 'Absolute' field is not
checked

Released

11/25/2009

New

New
New
New

BSS RESTRICTIONS LIST


BSSSAX01C Ed07 QD5
RELEASE B10
3BK 13016 1261 TQZZA
25/103

All rights reserved. Passing on and copying of this


document, use and communication of its contents not
permitted without written authorization from Alcatel-Lucent

New FRs introduced


from BSSSAX01B
Ed01
3BKA17FBR214144
3BKA17FBR214217
3BKA17FBR214448
3BKA17FBR214476
3BKA17FBR215635
3BKA17FBR216179
3BKA17FBR216188
3BKA20FBR203134
3BKA20FBR209413
3BKA20FBR209551
3BKA20FBR211268
3BKA20FBR211766
3BKA20FBR213803
3BKA20FBR213583

Status

Computed vector indicators involving MIDDLE functions do


not work
The time from data available on the OMC-R till it is available
in NPO database is longer than expected on V880 hardware
configuration with 8000 cells
After creating an indicator the indicator tree is not directly
accessible
RNP data source cannot be updated from NPO
Administration menu
"Recovered data" operation fails from NPO Administration
window
The occupancy of /alcatel partition is too big for a 5000 cells
configuration on V880 machine
The disk activity is particularly high for a 5000 cells
configuration on V880 machine
When performing an A9130 BSC Evolution extension from
Type 1 to Type 2, the new CCP board seems to stay in the
standby status.
A double takeover of the MUX boards takes place when the
standby MUX board is removed from the LIU shelf
BSSIM process is frozen when switching from N7 LSL to
N7 HSL
OSB Restore failed due to SEGMENTATION FAULT error
The MFS is not able to manage more than 255 cells for one
BSC
After a Logical Audit, the number of pure reselection
adjacencies doubles
The OMC-R alarms from the Master are not raised in AS

New
New
New
New
New
New
New
New
New
New
New
New
New
New

3BKA20FBR216317

Incorrect handling of pure reselection adjacency in OMC-R


after a BSS discover
Sometimes, Analysis Desktop is remaining at 75% and not
starting.
NPO Stand alone: Server error MAAT common exception
message apperas at Analysis Desktop startup.
B9 GPMRES files are generated after a B9 to B10 migration
of an MFS with its attached BSCs but should not

New

3BKA20FBR216318

MFS version is not correctly displayed in B9 GPMRES files

New

3BKA20FBR213976
3BKA20FBR214683
3BKA20FBR214684

3BKA20FBR216450
3BKA32FBR211470
3BKA36FBR196911
3BKA36FBR212100
3BKA36FBR212511

FRs removed since


BSSSAX01B Ed01
3BKA17FBR207361
3BKA17FBR208401
3BKA17FBR208463
3BKA17FBR208572
3BKA17FBR208946
3BKA17FBR209487

ED

Short Description

01

New
New
New

B9 GPMRES files are not sent to the B10 OMC-R on which


are declared both B9 MFSs and B10 MFSs with and without
security
SNMP alarms are cleared but raised back without any
reason
Ethernet link failure alarm is not seen from the A9130 BSC
Evolution Terminal
Sometimes, the TP board stays in FLT status after its
removal/insertion

New

Standby CCP spontaneously resets several times per day

New

Short Description

New
New
New

Status

The CellsInCircle primitive available for Diagnosis does not


work
All results of a Diagnosis Scheduled on an entire Working
Zone are not available.

CLOSE NRE

Impossible to load customer indicators dictionary

CLOSE REL

CLOSE OUT

Background maps loaded are not saved correctly when


exiting AD
Tuning session file is exported to both target and source
OMCs in case of inter-OMC adjacencies creation

CLOSE REL

Viewport centering works only for a complete layer and not

CLOSE REL

Released

11/25/2009

CLOSE REL

BSS RESTRICTIONS LIST


BSSSAX01C Ed07 QD5
RELEASE B10
3BK 13016 1261 TQZZA
26/103

FRs removed since


BSSSAX01B Ed01

Short Description

Status

All rights reserved. Passing on and copying of this


document, use and communication of its contents not
permitted without written authorization from Alcatel-Lucent

for a sub-selection
3BKA17FBR209500

Radio parameters of external 3G cells not accessible in AD

CLOSE REL

3BKA17FBR209851

Administrator could wrongly force the operator to change his


password

CLOSE REL

3BKA17FBR209947

Sometimes Log visualization GUI is not usable

CLOSE REL

3BKA17FBR209963

Database may be corrupted during creation or modification


of an indicator

CLOSE REL

3BKA17FBR210574

There are no busy hour monthly values calculated

CLOSE REL

3BKA17FBR210627

It is not possible to define filters in log visualization GUI

CLOSE REL

3BKA17FBR210810
3BKA17FBR211186
3BKA17FBR211271
3BKA17FBR211357
3BKA17FBR211380
3BKA17FBR212245
3BKA17FBR211488
3BKA17FBR211494

CLOSE REL
CLOSE REL
CLOSE REL
CLOSE REL
CLOSE REL
CLOSE REL
CLOSE REL

3BKA17FBR211754

Cannot create adjacency to an external cell

CLOSE REL

3BKA17FBR211792

Errors for parameter merge during move BSC inter NPO

CLOSE REL

3BKA20FBR202780

Some operators can not be used when creating a working


zone

CLOSE REL

3BKA20FBR206098

Sometimes, FTP transfer between OMC-R and NPO fails

CLOSE REL

3BKA17FBR210632

RMS36 does not have a corresponding indicator in NPO

CLOSE REL

3BKA17FBR213748

Indicator QSTRN is not mapped on the corresponding


GATRMHT
NPA computed indicators are not imported in NPO even if
they are stored in NPO
Some indicators display different values in NPO due to
wrong normalization
Some GPRS indicators should use spatial consolidation on
secondary BTS
Some GPDIST indicators do not have the AVG aggregation
in NPO
After an A9130 BSC Evolution Extension, it may sometimes
appear that the OMC-BSC connection is lost inducing a
reboot of all the OMCPs boards.
The recovery of the second N7 HSL signaling link takes
more than 5 minutes after a Reset of the Active TP
Export in xls format of a report containing a view with events
does not work

3BKA17FBR203213

Incomplete legend

3BKA17FBR211304
3BKA17FBR211399
3BKA17FBR212306
3BKA17FBR203916
3BKA20FBR204474
3BKA20FBR213697
3BKA20FBR212333

New FRs introduced


from BSSSAX01A
Ed01
3BKA17FBR203724

ED

Online help cannot be used unless some specific on-line


help windows are opened
First hours of the day is not interpolated (when the data are
missing) when executing a view using AD.
Execution of indicators, view and reports with sampling or
reliability option are not performed
Cannot create a new calculated indicator when the "formula"
field contains a parameter
Execution of view on base object with periodicity BH is not
displaying values
Only the first recovery consolidation will be performed
correctly by NPO
Spatial aggregation of RMS is not performed correctly for
timezone west from GMT

01

CLOSE REL
CLOSE REL
CLOSE REL
CLOSE REL
CLOSE REL
CLOSE NRE
CLOSE OUT
CLOSE REL
CLOSE REL

Short Description

Status

DAV3 and DAV5 aggregation methods are not working

Released

11/25/2009

New

BSS RESTRICTIONS LIST


BSSSAX01C Ed07 QD5
RELEASE B10
3BK 13016 1261 TQZZA
27/103

New FRs introduced


from BSSSAX01A
Ed01
All rights reserved. Passing on and copying of this
document, use and communication of its contents not
permitted without written authorization from Alcatel-Lucent

3BKA17FBR203725
3BKA20FBR204474
3BKA17FBR207361

Status

BH Indicators needed to compute DAV Indicators are not


generated automatically by NPO
Some GPDIST indicators do not have the AVG aggregation
in NPO
The CellsInCircle primitive available for Diagnosis does not
work

New
New
New

3BKA17FBR207606

Bad performance while migrating matrix indicators

New

3BKA17FBR208401

All results of a Diagnosis Scheduled on an entire Working


Zone are not available.

New

3BKA17FBR208463

Impossible to load customer indicators dictionary

New

Background maps loaded are not saved correctly when


exiting AD
Tuning session file is exported to both target and source
OMCs in case of inter-OMC adjacencies creation

New

3BKA17FBR209205

OSB Restore failed due to SEGMENTATION FAULT error

New

3BKA17FBR209487

Viewport centering works only for a complete layer and not


for a sub-selection

New

3BKA17FBR209500

Radio parameters of external 3G cells not accessible in AD

New

3BKA17FBR209572
3BKA17FBR210659

RMS indicators with boundary-type axis with fixed first/last


values not displayed
NPO Administration not usable after scheduled backup with
Legato
Administrator could wrongly force the operator to change his
password

3BKA17FBR208572
3BKA17FBR208946

3BKA17FBR209785
3BKA17FBR209851

New

New
New
New

3BKA17FBR209907

Properties window on Tuning job cannot be opened

New

3BKA17FBR209947

Sometimes Log visualization GUI is not usable

New

3BKA17FBR209963
3BKA17FBR210445
3BKA17FBR210574
3BKA17FBR210578
3BKA17FBR210585
3BKA17FBR210627
3BKA17FBR210632
3BKA17FBR210633
3BKA17FBR210810
3BKA17FBR211083
3BKA17FBR211186
3BKA17FBR211271
3BKA17FBR211304
3BKA17FBR211357
3BKA17FBR211380
3BKA17FBR212245
3BKA17FBR211399
3BKA17FBR211488

ED

Short Description

01

Database may be corrupted during creation or modification


of an indicator
Conflicting network level values when NPO is not empty
when data is imported
There are no busy hour monthly values calculated
SEC sporadically becomes blocked when updating user
profile
NPO Administration can become unusable after a significant
amount of operations

New
New
New
New
New

It is not possible to define filters in log visualization GUI

New

RMS36 does not have a corresponding indicator in NPO

New

Some HO indicators will not be migrated at TRX level from


B9 MR1 NPA
Online help cannot be used unless some specific on-line
help windows are opened
Only one RMS file can be loaded per day
First hours of the day is not interpolated (when the data are
missing) when executing a view using AD.
Execution of indicators, view and reports with sampling or
reliability option are not performed
Indicator QSTRN is not mapped on the corresponding
GATRMHT
Cannot create a new calculated indicator when the "formula"
field contains a parameter
Execution of view on base object with periodicity BH is not
displaying values
NPA computed indicators are not imported in NPO even if
they are stored in NPO
Only the first recovery consolidation will be performed
correctly by NPO

Released

11/25/2009

New
New
New
New
New
New
New
New
New
New

BSS RESTRICTIONS LIST


BSSSAX01C Ed07 QD5
RELEASE B10
3BK 13016 1261 TQZZA
28/103

All rights reserved. Passing on and copying of this


document, use and communication of its contents not
permitted without written authorization from Alcatel-Lucent

New FRs introduced


from BSSSAX01A
Ed01

Status

3BKA17FBR211494

Spatial aggregation of RMS is not performed correctly for


timezone west from GMT

New

3BKA17FBR211754

Cannot create adjacency to an external cell

New

3BKA17FBR211792

Errors for parameter merge during move BSC inter NPO

New

3BKA17FBR212306
3BKA20FBR199501
3BKA20FBR202780
3BKA20FBR203489
3BKA20FBR203884

ED

Short Description

Some indicators display different values in NPO due to


wrong normalization
Sometimes, BSCs and cells parameters are stored in NPO
with a wrong date
Some operators can not be used when creating a working
zone
When a view contains values with different units (non
numerical data), the sorting does not work properly.
The reference name (RefName) for counters and indicators
is missing in the "drag&drop" area of Analysis Desktop
window.

New
New
New
New
New

3BKA20FBR206098

Sometimes, FTP transfer between OMC-R and NPO fails

New

3BKA20FBR210784

Sometimes, Analysis Desktop starting takes a long time


and induces an error message

New

01

Released

11/25/2009

BSS RESTRICTIONS LIST


BSSSAX01C Ed07 QD5
RELEASE B10
3BK 13016 1261 TQZZA
29/103

All rights reserved. Passing on and copying of this


document, use and communication of its contents not
permitted without written authorization from Alcatel-Lucent

TABLE OF CONTENTS
1 NEW RESTRICTIONS IN B10 .......................................................................................................... 34
1.1 BSS O&M CONFIGURATION MANAGEMENT........................................................................ 34
1.1.1 BSS Hardware Configuration Management.................................................................. 34
1.1.1.1 On-line Hardware Configuration Management ............................................................ 34
1.1.1.2 TRX/RSL re-mapping .................................................................................................. 35
1.1.1.3 On-line BTS Extension/Reduction ............................................................................... 35
1.1.1.4 GPRS/EDGE Hardware Configuration Management .................................................. 36
1.1.2 BSS Logical Configuration Management ...................................................................... 37
1.1.2.1 Force Configuration ..................................................................................................... 39
1.1.2.2 GPRS/EDGE Logical Configuration Management ...................................................... 39
1.1.2.3 Extensive Logical Configuration Update...................................................................... 39
1.1.2.4 Remote Inventory from the OMC-R............................................................................. 41
1.1.2.5 BSS Audits................................................................................................................... 41
1.1.2.6 Usage state on demand............................................................................................... 41
1.1.3 TC software upgrade / MT120-xB usage ...................................................................... 42
1.1.4 TC supervision .............................................................................................................. 43
1.1.5 Back-up / Restore.......................................................................................................... 44
1.1.6 MFS O&M...................................................................................................................... 44
1.1.7 BSC/TC Extension ........................................................................................................ 47
1.1.8 Remote Inventory .......................................................................................................... 47
1.1.9 BSC OMCR link.......................................................................................................... 48
1.2 BSS FAULT MANAGEMENT.................................................................................................... 48
1.2.1 GSM Fault management ............................................................................................... 48
1.2.2 GPRS/EDGE Fault Management.................................................................................. 51
1.2.3 TC fault management.................................................................................................... 52
BSS PERFORMANCE MANAGEMENT ......................................................................................... 54
1.2.4 GSM Performance Management .................................................................................. 54
1.2.5 GPRS Performance Management ................................................................................ 54
1.2.6 Radio measurements Statistics (RMS) Counters on Electro-Magnetic Emmissions. 55
1.2.7 IMSI Trace..................................................................................................................... 55
1.3 GSM Telecom............................................................................................................................ 56
1.3.1 GSM Telecom ............................................................................................................... 56
1.3.2 GSM Quality of Service ................................................................................................. 56
1.3.3 GSM Adaptive Multi Rate Codec .................................................................................. 57
1.3.4 SMSCB.......................................................................................................................... 57
1.4 GPRS/EDGE Telecom .............................................................................................................. 58
1.5 A1353-OMC-R SYSTEM ........................................................................................................... 58
1.5.1 OMC-R Man machine interface..................................................................................... 58
1.5.2 OMC-R Configuration Modification ............................................................................... 58
1.5.3 OMC-R Software Management / Backup-Restore........................................................ 60
1.5.4 OMC-R Administration .................................................................................................. 60
1.5.5 OMC-R Supervision ...................................................................................................... 62
1.5.6 OMC-R Alarm Management.......................................................................................... 62
1.5.7 OMC-R Performance Management .............................................................................. 64
1.5.8 OSI Q3 interface to the NMC ........................................................................................ 64
1.5.9 Alarm call out function ................................................................................................... 65
1.5.10 OMCR Stability.............................................................................................................. 65
1.6 STABILITY AND PERFORMANCE........................................................................................... 65
1.6.1 Sub-system OMC-R ...................................................................................................... 65
1.6.2 Sub-system BSC Legacy .............................................................................................. 66
1.6.3 Sub-system BSC Evolution ........................................................................................... 66
1.6.3.1 BSC OMC-R link....................................................................................................... 68
1.6.4 Sub-system BTS ........................................................................................................... 68
ED

01

Released

11/25/2009

BSS RESTRICTIONS LIST


BSSSAX01C Ed07 QD5
RELEASE B10
3BK 13016 1261 TQZZA
30/103

All rights reserved. Passing on and copying of this


document, use and communication of its contents not
permitted without written authorization from Alcatel-Lucent

1.6.5 Sub-system TC.............................................................................................................. 68


1.6.6 Sub-system MFS Legacy .............................................................................................. 68
1.6.7 Sub-system MFS Evolution ........................................................................................... 68
1.7 LOCAL TERMINALS ................................................................................................................. 70
1.8 ADMINISTRATION SERVICES................................................................................................. 72
2 . RESTRICTIONS FROM PREVIOUS RELEASES.......................................................................... 73
2.1 BSS O&M CONFIGURATION MANAGEMENT........................................................................ 73
2.1.1 BSS Hardware Configuration Management.................................................................. 73
2.1.2 On-line Hardware Configuration Management ............................................................. 74
2.1.3 TCU/RSL re-mapping.................................................................................................... 74
2.1.4 On-line BTS extension/reduction .................................................................................. 74
2.1.5 GPRS/EDGE Hardware Configuration Management.................................................... 74
2.1.6 BSS Logical Configuration Management ...................................................................... 75
2.1.6.1 Force Configuration ..................................................................................................... 77
2.1.6.2 GPRS/EDGE Logical Configuration Management ...................................................... 77
2.1.7 Extensive Logical Configuration update........................................................................ 78
2.1.8 TC software upgrade..................................................................................................... 79
2.1.9 MFS O&M...................................................................................................................... 79
2.2 BSS FAULT MANAGEMENT.................................................................................................... 81
2.2.1 GSM Fault management ............................................................................................... 81
2.2.2 GPRS/EDGE fault management ................................................................................... 84
2.3 BSS O&M PERFORMANCE MANAGEMENT.......................................................................... 86
2.3.1 GSM Performance Management .................................................................................. 86
2.3.2 GPRS Performance Management ................................................................................ 86
2.3.3 Radio measurement Statistics (RMS) ........................................................................... 87
2.3.4 IMSI Trace..................................................................................................................... 88
2.3.5 Network performance analyzer ..................................................................................... 88
2.4 GSM Telecom............................................................................................................................ 89
2.4.1 GSM QoS ...................................................................................................................... 89
2.4.2 Adaptative MultiRate Codec.......................................................................................... 89
2.4.3 SMSCB.......................................................................................................................... 89
2.5 GPRS/EDGE Telecom .............................................................................................................. 90
2.6 A1353-OMC-R SYSTEM ........................................................................................................... 91
2.6.1 OMC-R Man-machine interface .................................................................................... 91
2.6.2 OMC-R Configuration Modification ............................................................................... 91
2.6.3 OMC-R Administration .................................................................................................. 91
2.6.4 OMC-R Software Management / Backup-Restore........................................................ 92
2.6.5 OMC-R Alarm Management.......................................................................................... 92
2.6.6 OSI Q3 Interface to NMC .............................................................................................. 92
2.6.7 Alarm Call Out Function ................................................................................................ 92
2.7 STABILITY AND PERFORMANCE........................................................................................... 94
2.7.1 Sub-system OMC-R ...................................................................................................... 94
2.7.2 Sub-system BSC ........................................................................................................... 94
2.7.2.1 BSC OMC-R link....................................................................................................... 95
2.7.3 Sub-system BTS ........................................................................................................... 95
2.7.4 Sub-system MFS........................................................................................................... 95
2.8 LOCAL TERMINALS ................................................................................................................. 97
2.9 ADMINISTRATION SERVICES................................................................................................. 98
3 IMPACT ON METHODS ................................................................................................................... 99
4 APPENDIX A: KEYWORDS ........................................................................................................... 101
5 APPENDIX B: ABBREVIATIONS .................................................................................................. 103

ED

01

Released

11/25/2009

BSS RESTRICTIONS LIST


BSSSAX01C Ed07 QD5
RELEASE B10
3BK 13016 1261 TQZZA
31/103

INTERNAL REFERENCED DOCUMENTS


All rights reserved. Passing on and copying of this
document, use and communication of its contents not
permitted without written authorization from Alcatel-Lucent

Not applicable

REFERENCED DOCUMENTS
[1] BSS SOFTWARE LIST BSSSAX01C Ed 07 RELEASE B10
3BK 13016 1225 TQZZA
[2] COUNTER STATUS BSSSAX01C Ed 03 RELEASE B10
3BK 13016 1127 TQZZA
[3] MFS TROUBLE SHOOTING GUIDE RELEASE B10
3BK 29042 LAAA PWZZA
[4] OMC-R TROUBLE SHOOTING GUIDE RELEASE B10
3BK 29007 LAAA PWZZA

RELATED DOCUMENTS
Not applicable

PREFACE
This document is in accordance with the document referenced in [1].
The B10 MR2 Ed07 delivery is aligned with B9 MR4 ED08.
Starting from B10 MR2 ED7, the NPO FRs are not added anymore into BSS RL document, and a
separate document (NPO RL) is issued in order to track the NPO FRs.
This document is divided into two parts:
-

New restrictions found in B10.


Known restrictions since previous releases.

Symbols are used to indicate visually the gravity of the fault report linked to a restriction:
 for FR with gravity G0/G1

for FR with gravity G2

for FR with gravity G3/G4

Notes:
1. In order to help readers of this document to find quicker all restrictions that are related to a
specific feature or domain, keywords have been introduced, plus a table. For each
restriction, a list of keywords gives the feature or domains to which the restriction is
related. At the end of this document, the exhaustive list of the keywords is provided.
2. Note that "Existed before current delivery" field is applicable only compared to previous
B10 maintenance release (B10 MR1).

ED

01

Released

11/25/2009

BSS RESTRICTIONS LIST


BSSSAX01C Ed07 QD5
RELEASE B10
3BK 13016 1261 TQZZA
32/103

All rights reserved. Passing on and copying of this


document, use and communication of its contents not
permitted without written authorization from Alcatel-Lucent

3. For a common understanding of the date when the restriction may be removed, the
following rules have been defined for the filling-in of the Planned Delivery field:
-

ED

01

Under study in B10: SW delivery not yet planned for the related FR
Planned for MR2 Edx: Correction planned in B10 MR2 Edx for the related FR
No solution planned: the FR will never be implemented

Released

11/25/2009

BSS RESTRICTIONS LIST


BSSSAX01C Ed07 QD5
RELEASE B10
3BK 13016 1261 TQZZA
33/103

All rights reserved. Passing on and copying of this


document, use and communication of its contents not
permitted without written authorization from Alcatel-Lucent

1 NEW RESTRICTIONS IN B10

1.1 BSS O&M CONFIGURATION MANAGEMENT


1.1.1
1.1.1.1

BSS Hardware Configuration Management

On-line Hardware Configuration Management

 OMCP reset/takeover after BSC Evolution reduction

RESTRICTION

On a BSC Evolution were performed several extension/reduction actions. After one of the reduction, it
was noticed several spontaneous OMCP reset/takeover events, until on one OMCP was noticed the
blue LED on.
Preventive actions: none
Corrective actions: none
Unusable
Usable with WA
Usable with limitation



Spontaneously OMCP takeover will be done after BSC reduction.

Workaround
Impacts

Occurrence
Existed before
Current delivery?

Very Sporadic

Likely

Sporadic

Yes


FR

3BKA20FBR275086

B10

Sub-System
Planned Delivery
Keywords

BSC Evolution
Severity
Under study in B10
On-line Hardware Configuration Management.

Errors during move a BSS from Master to Agent

Systematic

No

G1

RESTRICTION

On an OMC configuration with Master and Agent, a move BSS from Master to Agent was performed
using the method Move BSS with/without MFS between Servers of the Same OMC-R. All was OK
until the following script was launched: ./MoveBSS_InterHosts_SameOMC.pl -exportDir <X> -host
<hostname>, which was not finished successfully because of the following errors:
removed ok from omcr07
declaring BSS5 ...ERROR
Error code: oam-0
Error description: A creation of object failed in SECIM.
The created BSS identified by 5 should be deleted.
Preventive actions: none
Corrective actions: perform stop/start of lss and sec processes
Unusable
Usable with WA
Usable with limitation



Move BSS action form Master to Agent is blocked

Workaround
Impacts

ED

01

Released

11/25/2009

BSS RESTRICTIONS LIST


BSSSAX01C Ed07 QD5
RELEASE B10
3BK 13016 1261 TQZZA
34/103

All rights reserved. Passing on and copying of this


document, use and communication of its contents not
permitted without written authorization from Alcatel-Lucent

Occurrence

Very Sporadic

Likely


Sporadic

Yes

FR

3BKA20FBR266169
3BKA20FBR276396

B10
B11

Sub-System
Planned Delivery
Keywords

OMC-SW
Severity
Under study in B11
On-line Hardware Configuration Management.

Existed before
Current delivery?

1.1.1.2

TRX/RSL re-mapping

1.1.1.3

On-line BTS Extension/Reduction

Systematic

No


G2

TWIN module replacement issue

RESTRICTION

It was noticed that in case of BTS equipped with SUMx, in case of TWIN replacement procedure it
might happen at the end of procedure, when End of HW modification is applied, that the BTS
monitoring window from BTS NEM terminal to show only one TWIN TRE instead of two TWIN TREs, or
in some cases no TWIN TRE at all. The solution to display correctly the TWIN TRE is to not accept the
configuration and apply again the End of HW modification until the correct configuration will be
displayed.
Preventive actions: none
Corrective actions: do not accept the configuration and perform again
End of HW modification until the TWIN configuration is correct.
Unusable
Usable with WA
Usable with limitation



TWIN TRE replacement procedure does not work correctly.

Workaround

Impacts

Occurrence
Existed before
Current delivery?

Very Sporadic

Likely


Sporadic

Yes


FR

3BKA20FBR285134

B10

Sub-System
Planned Delivery
Keywords

BTS SW
Severity
Under study in B10
On-line BTS Extension/Reduction

ED

ANC module replacement issue

01

Systematic

No

G2

RESTRICTION

Released

11/25/2009

BSS RESTRICTIONS LIST


BSSSAX01C Ed07 QD5
RELEASE B10
3BK 13016 1261 TQZZA
35/103

All rights reserved. Passing on and copying of this


document, use and communication of its contents not
permitted without written authorization from Alcatel-Lucent

In case of BTS equipped with SUMx, the ANX replacement was performed as follows:
-Disable BTS_TEL for sector 3,
-Disable RA3,
-Unplug ANCG,
-Plug ANCG,
-Init RA3,
-Init BTS_TEL for sector 3,
After the Init RA3, the action was not successful, and the initialization of BTS was not done correct. In
order to overpass this problem, the Init RA action has to be performed several times until ended
successfully.
Preventive actions: none
Corrective actions: perform again Init RA until the initialization is
correct.
Unusable
Usable with WA
Usable with limitation



ANC replacement procedure does not work correctly.

Workaround

Impacts

Occurrence
Existed before
Current delivery?

Very Sporadic

Likely


Sporadic

Yes


FR

3BKA20FBR285136

B10

Sub-System
Planned Delivery
Keywords

BTS SW
Severity
Under study in B10
On-line BTS Extension/Reduction

1.1.1.4

Systematic

No

G2

GPRS/EDGE Hardware Configuration Management

Sometimes, the GPRS traffic is lost after the switchover of an ATCA-F300


switch.

RESTRICTION

In the following A9130 MFS Evolution configuration where 2 GPs are used (2 NSE) and SSW2 (ATCAF300) is active with MUX2, GPRS traffic is running.
After an SSW2 switchover, the GPRS traffic is lost.
The GPs then reboot and the following alarms appear at OMC-R:
GP loss of contact GP (for 2 GP)
Ne1oe supervision error on GP board
Rack1Shelf1Mux12 MUX supervision error
After around 8 minutes the GPs become operational meaning a GPRS traffic back.
This problem is not systematic and occurs once over 5 times. Investigation are for the moment NE1oE
block oriented
Preventive actions: Not applicable
Corrective actions: None

Workaround

Unusable
Usable with WA


Loss of GPRS traffic on the whole MFS

Impacts

ED

01

Released

11/25/2009

Usable with limitation

BSS RESTRICTIONS LIST


BSSSAX01C Ed07 QD5
RELEASE B10
3BK 13016 1261 TQZZA
36/103

All rights reserved. Passing on and copying of this


document, use and communication of its contents not
permitted without written authorization from Alcatel-Lucent

Occurrence

Very Sporadic

Likely


Sporadic

Yes

FR

3BKA20FBR251234
3BKA20FBR274942

B10
B11

Sub-System
Planned Delivery
Keywords

MFS Evolution HW
G2
Severity
Under study in B11
GPRS/EDGE Hardware Configuration Management

Existed before
Current delivery?

Systematic

No


 It is not possible to configure a PS dedicated link below Ater-Mux 31

RESTRICTION

The design of the A9130 BSC Evolution requires to have dedicated GPRS links to start with Ater-Mux
31 in order to separate CS Ater-Mux (pure CS or mixed) from GPRS (pure PS) Ater-Mux. The only
exception is an A9130 BSC Evolution which has replaced a G2 BSC by an HardSwap scenario.
Preventive actions: None
Corrective actions: As an example for the creation of Atermux 9 for a BSEV-200 configuration, the following extension/reduction procedure has to be
followed:
- Link MFS GPU-x TP-z with ATER-MUX 9
- Align Links
- Extend TC config from 3 to 10.
- Configure GPRS 100% dedicated link w/o GSL for ATER-MUX 9
- Align GPRS Configuration
- Connect the E1 links between BSC and MFS
- Allow alarm reporting for Atermux 9
- Unlock ATER-TPs at BSC side
- Reduce TC config from 10 to 3

Workaround

Timing
The operation needs less than 30 minutes
Impacts

Occurrence
Existed before
Current delivery?

Unusable
Usable with WA
Usable with limitation



Only Atermux that do not carry Qmux can be changed. For BSC-EV-200,
Atermux CS are in the range 1..10. The Atermux 1,2, 7 and 8 cannot be
used.
Very Sporadic
Sporadic
Systematic



Likely
Yes
No


FR

3BKA20FBR255471
3BKA20FBR261039

Sub-System
Planned Delivery
Keywords

OMC SW
G1
Severity
Under study in B11
GPRS/EDGE Hardware Configuration Management

1.1.2

ED

01

B10
B11

BSS Logical Configuration Management

Released

11/25/2009

BSS RESTRICTIONS LIST


BSSSAX01C Ed07 QD5
RELEASE B10
3BK 13016 1261 TQZZA
37/103

All rights reserved. Passing on and copying of this


document, use and communication of its contents not
permitted without written authorization from Alcatel-Lucent

The violation of the rule Maximum 64 HOs per cell can lead to
corruptions

RESTRICTION

When a cell becomes more than 64 times the neighbor of a cell (by PRC usage) then the OMC-R
allows the operation (a check would impact OMC-R performances at PRC activation) but since the
BSC does not allow it, this induces the cells to be misaligned between OMC-R and BSC databases
and can lead to corruptions.
To note that the BSC has also a limitation concerning the total number of outgoing HO links, which is
5400 for a B9 G2 BSC/A9130 BSC Evolution and 10300 for a B10 A9130 BSC Evolution.
Preventive actions: avoid that a cell be the neighbor to more than 64 cells
Corrective actions: perform a logical audit in order to recover the
configuration misalignment linked to the BSC check

Workaround

Unusable
Usable with WA
Usable with limitation



The operator is amazed by this misalignment because the OMC-R does not
check the rule at PRC activation

Impacts

Occurrence
Existed before
Current delivery?

Very Sporadic

Likely


FR

3BKA20FBR230654

Sub-System
Planned Delivery
Keywords

BSC-SW
Severity
No solution planned
BSS Logical Reconfiguration

Sporadic

Yes

Systematic

No

G2

It is not possible to open tuning browser on HMI with other user than
axadmin

RESTRICTION

On HMI, only axadmin user can open tuning browser. This action will fail with another user, with
axadmin profile.
This problem does not appear on master.
Preventive actions: Open tuning browser either from master, or by using
axadmin from HMI
Corrective actions: None

Workaround

Unusable
Usable with WA
Usable with limitation



The operator must use axadmin from HMI to open tuning browser.

Impacts
Occurrence

Very Sporadic

Likely


Sporadic

Yes

FR

3BKA20FBR239669
3BKA20FBR252990

B10
B11

Sub-System

OMC3

Severity

Existed before
Current delivery?

ED

01

Released

11/25/2009

Systematic

No


G2
BSS RESTRICTIONS LIST
BSSSAX01C Ed07 QD5
RELEASE B10
3BK 13016 1261 TQZZA
38/103

All rights reserved. Passing on and copying of this


document, use and communication of its contents not
permitted without written authorization from Alcatel-Lucent

Planned Delivery
Keywords

Under study in B11


BSS Logical Reconfiguration

1.1.2.1

Force Configuration

1.1.2.2

GPRS/EDGE Logical Configuration Management

 After PRC activation the GPRS Status at RNUSM for BSC and all Cells are
disable

RESTRICTION

It may happen sometimes that after a PRC application, the GPRS status on BSC and all the cells to
remain disabled on GPRS part. The operational State for all GSL is also disabled. First analysis shows
that there was no telecom impact on GPRS traffic.
The status at OMC side was not in line with the status at MFS side (Cells and GB link were not in state
"disabled" at MFS side). With USD it was possible to check as well the availability of GPRS traffic. The
problem could be solved with GP switchover.
Preventive actions: none
Corrective actions: Perform a GP switch over
Unusable
Usable with WA
Usable with limitation



GPRS Status at RNUSM for the BSC and all Cells is disabled.
The operational State for all GSL is disabled. GPRS traffic as not impacted.

Workaround
Impacts

Occurrence

Very Sporadic

Likely

Sporadic

Yes


FR

3BKA20FBR273007
3BKA20FBR274949

B10
B11

Sub-System
Planned Delivery
Keywords

MFS-SW
Severity
Under study in B11
GPRS Logical Configuration Management

Existed before
Current delivery?

1.1.2.3

Systematic

No


G1

Extensive Logical Configuration Update

MFS reservation status busy on 5 MFSs after close MLU session

RESTRICTION

During an MLU session, after the Close sessionwas applied, it was seen that the status on 5 MFSs
remained busy, making impossible the parameter updates and operators actions.
Preventive actions: none
Corrective actions: stop/start MFSIM process
Unusable
Usable with WA
Usable with limitation



Operator actions/parameter updates not possible.

Workaround
Impacts

ED

01

Released

11/25/2009

BSS RESTRICTIONS LIST


BSSSAX01C Ed07 QD5
RELEASE B10
3BK 13016 1261 TQZZA
39/103

All rights reserved. Passing on and copying of this


document, use and communication of its contents not
permitted without written authorization from Alcatel-Lucent

Occurrence

Very Sporadic

Likely

Sporadic

Yes


FR

3BKA20FBR263050
3BKA20FBR274399

B10
B11

Sub-System
Planned Delivery
Keywords

OMC-SW
Under study in B11
MLU

Severity

Existed before
Current delivery?

Systematic

No


G2

Sometimes, during MLU session, the download may fail

RESTRICTION

Sometimes, the MLU process may be stopped during downloand process. The download fails due to
following errors:
A message with jobUnsuccessful has been received from the BSS:
bsc_disk_problems (13) for the action %s or
A message with jobUnsuccessful has been received from the BSS: installation_problem (19) for the
action %s.
Preventive actions: none
Corrective actions: retry download process untill successfull
Unusable
Usable with WA
Usable with limitation



Pre-download cannot be done, and MLU is stopped

Workaround
Impacts

Occurrence

Very Sporadic

Likely


Sporadic

Yes

FR

3BKA20FBR261476
3BKA20FBR271676

B10
B11

Sub-System
Planned Delivery
Keywords

BSC Evolution
Under study in B11
MLU

Severity

Existed before
Current delivery?

 TP takeover refused after an MLU session

Systematic

No


G2

RESTRICTION

After an MLU session successfully finished, it was noticed that the TP takeover is refused causing the
lost of N7 and also the lost of GPRS. The issue was solved after a manual TP reset. Investigations
revealed the fact that a TP takeover occurred durin MLU session, between sw_preload and
sw_activate actions. This TP takeover leaded to an unsinchronized DLS scenario, causing the
refused TP takeover after MLU session was finished.
Preventive actions: avoid TP takeover during MLU session
Corrective actions: manual reset of the TP
Unusable
Usable with WA
Usable with limitation



N7 and GPRS traffic lost until manual reset of impacted TP

Workaround
Impacts

Occurrence
ED

01

Very Sporadic


Sporadic


Released

11/25/2009

Systematic

BSS RESTRICTIONS LIST


BSSSAX01C Ed07 QD5
RELEASE B10
3BK 13016 1261 TQZZA
40/103

All rights reserved. Passing on and copying of this


document, use and communication of its contents not
permitted without written authorization from Alcatel-Lucent

Existed before
Current delivery?

Likely


Yes

FR

3BKA20FBR285887

B10

Sub-System
Planned Delivery
Keywords

BSC SW
Under study in B10
MLU

Severity

1.1.2.4

Remote Inventory from the OMC-R

1.1.2.5

BSS Audits

No

G1

CCP-Resource-report has displayed strange values

RESTRICTION

The parameter-value EN_DR_TRE_PER-TCU is inconsistent between OMC and BSC.


In OMC the value is static, in BSC the value is dynamic. There is no apparent way to distinguish if the
value is wrongly set or wrongly displayed.
The way to force the display of the right value is:
1) Change the value on OMCR.
2) Commands->BSS Operations->Display N7 network address on BSC terminal.
Preventive actions: none
Corrective actions: none

Workaround
Impacts

Unusable
Usable with WA


CCP-resource report is not usable.

Usable with limitation




Occurrence

Very Sporadic

Likely


Sporadic

Yes

Systematic

No


FR

3BKA20FBR272959
3BKA20FBR274414

B10
B11

Sub-System
Planned Delivery
Keywords

BSC Evolution
Under study in B11
BSS Audits

Severity

Existed before
Current delivery?

1.1.2.6

G2

Usage state on demand

Wrong display of TS allocation in USD Cell Overview Window in case of


RESTRICTION
satellite communications
In case of Abis over satellite link is used, in USD Cell Overview window, there are few time slots which
are displayed as unallocated instead of busy. The impacted time slots are sent wrongly by BSC to
OMC. When the problem was seen, out of 8 TSs used for Traffic channel, 3 of them were wrongly sent
by BSC as unallocated instead of busy.
Workaround

ED

01

Preventive actions : none


Corrective actions : none
Released

11/25/2009

BSS RESTRICTIONS LIST


BSSSAX01C Ed07 QD5
RELEASE B10
3BK 13016 1261 TQZZA
41/103

Unusable
Usable with WA
Usable with limitation



Wrong information displayed in OMC about the radio TSs in USD window.

All rights reserved. Passing on and copying of this


document, use and communication of its contents not
permitted without written authorization from Alcatel-Lucent

Impacts
Occurrence

Very Sporadic

Likely

Sporadic

Yes


FR

3BKA20FBR273540
3BKA20FBR274364

B10
B11

Sub-System
Planned Delivery
Keywords

BSC SW
Severity
Under study in B11
Usage state on demand

Existed before
Current delivery?

1.1.3

Systematic

No


G3

TC software upgrade / MT120-xB usage

Sometimes, in TCIL mode, the activation of the new MT120 SW is not


always successful

RESTRICTION

On a TC with 10 MT120 boards, all in TCIL mode, an MT120 SW upgrade was started. The connection
was done between TC NEM and one of the MT board. All was OK until activation step. After activation
it was noted that all the MT boards except the one where the connection was done, were activated
very fast (turned to green), but the MT which had the connection did not activate even after 10 minutes
when the submit button was available again. After a disconnect/connect action from the TC NEM
terminal was done, it was noted that the board where the connection was made is in the old version.
So, the software upgrade was started again on this board only, and this time was going very fast,
finally activation being OK.
Preventive actions: none
Corrective actions: reperform software upgrade for the impacted boards
Unusable
Usable with WA
Usable with limitation



MT120 software upgrade not successful from the first trial

Workaround
Impacts

Occurrence
Existed before
Current delivery?

Very Sporadic

Likely


FR

3BKA20FBR268643

Sub-System
Planned Delivery
Keywords

MT120 SW
Severity
Under study in B10
MT120 SW Management

Sporadic

Yes


Systematic

No

G2

Sporadically, MT20 boards are missing in TC NEM, after TCIF new SW


activation

RESTRICTION

Very sporadic, it may happen that in case of TCIF software replacement, after the new software is
activated, all the MT120 boards are missing from TC NEM. All the MT120 boards are configured either
in HIS2a or HSI2b. There is no telecom impact.
ED

01

Released

11/25/2009

BSS RESTRICTIONS LIST


BSSSAX01C Ed07 QD5
RELEASE B10
3BK 13016 1261 TQZZA
42/103

Preventive actions: none


Corrective actions: perform TCIF takeover
Unusable
Usable with WA
Usable with limitation



Supervision lost in TC NEM for all MT120 boards.

All rights reserved. Passing on and copying of this


document, use and communication of its contents not
permitted without written authorization from Alcatel-Lucent

Workaround
Impacts

Occurrence
Existed before
Current delivery?

Very Sporadic

Likely

Sporadic

Yes


FR

3BKA20FBR280001

B10

Sub-System
Planned Delivery
Keywords

TCIF SW
Under study in B10
TCIF SW upgrade

Severity

Systematic

No

G2

MT120 boards misaligned with cause File list report failure after
rejecting the activated SW.

RESTRICTION

On a TC equipped with TCIF boards, and MT120 boards running in HSI2a, while performing a MT120
software replacement, it was noticed that after a SW reject action performed after a SW activate, it
could happen that some MT120 boards to remain misaligned, with the reason File list report failure.
Preventive actions: none
Corrective actions: restart each MT120 board, or write config on each
MT120.
Unusable
Usable with WA
Usable with limitation



MT120 reject software action not successful

Workaround

Impacts

Occurrence
Existed before
Current delivery?

Very Sporadic

Likely

Sporadic

Yes


FR

3BKA20FBR281083

B10

Sub-System
Planned Delivery
Keywords

MT120 SW
Under study in B10
MT120 SW upgrade

Severity

1.1.4

Systematic

No

G2

TC supervision

Wrong status displayed in OMC for stm1-ttp1, in case of lock action.

RESTRICTION

The TC equipment having TCIF boards is declared at OMC, and the supervision is working correctly.
In BSSUSM window all stm-1 ttps are IT. stm1-ttp1 from active TCIF is locked by operator. The action
is successfully completed (smile face in follow up) and also checking the TC-NEM it can be seen that
the TTP is locked, but the lock sign is never displayed on BSSUSM view, and according with this, it is
not possible to unlock the impacted TTP (no "unlock" option available).
Preventive actions: none
Corrective actions: perform unlock stm-ttp1 from TC NEM

Workaround

ED

01

Released

11/25/2009

BSS RESTRICTIONS LIST


BSSSAX01C Ed07 QD5
RELEASE B10
3BK 13016 1261 TQZZA
43/103

All rights reserved. Passing on and copying of this


document, use and communication of its contents not
permitted without written authorization from Alcatel-Lucent

Impacts

Unusable
Usable with WA
Usable with limitation



The stm-ttp1 SBL cannot be unlocked from OMC, after it has been locked by
operator.

Occurrence

Very Sporadic

Likely


Sporadic

Yes

FR

3BKA20FBR280282
3BKA20FBR284432

B10
B11

Sub-System
Planned Delivery
Keywords

OMC SW
Under study in B11
TC Supervision

Severity

Existed before
Current delivery?

1.1.5

Systematic

No


G2

Back-up / Restore

Sometimes, Objectstore crash occurs during Legato backup

RESTRICTION

Sporadically and randomly Objectstore crash occurs during Legato Backup in the network depending
on the actions performed on the related OMC and on the time when Legato backup is started.
First investigation shows that the database got corrupted because of the opened PRCs during backup
action. So, in order to make sure this issue will not happen anymore, preventive action is to close all
the opened PRCs before the backup.
Preventive actions: All PRCs should be closed before Legato backup
Corrective actions: None

Workaround
Impacts

Unusable
Usable with WA
Usable with limitation



No operational impact on the system but this leads to an inconsistent backup
of the data

Occurrence

Very Sporadic

Likely


Sporadic

Yes

FR

3BKA20FBR229768
3BKA20FBR274373

B10
B11

Sub-System
Planned Delivery
Keywords

OMC SW
Under study in B11
Backup / Restore

Severity

Existed before
Current delivery?

ED

1.1.6

MFS O&M

01

Released

11/25/2009

Systematic

No


G2

BSS RESTRICTIONS LIST


BSSSAX01C Ed07 QD5
RELEASE B10
3BK 13016 1261 TQZZA
44/103

All rights reserved. Passing on and copying of this


document, use and communication of its contents not
permitted without written authorization from Alcatel-Lucent

After Gb IP base address and gateway creation from IMT PC , IP


endpoint creation window of OMC Gb configuration window is not
updated

RESTRICTION

BSC and MFS are running under GB over IP mode.


- At OMC side, creation link between MFS - SGSN by "link and connections" menu of MFSUSM
window. All TP becomes green
- At IMT PC side, "IP view --> GPU --> set" . Creation of Gb base address ok ( seen by view)
- At IMT PC side, "IP view --> gateway --> set" . Creation of gateway
address OK ( seen by view). index = 1.
Problem
- At OMC Gb configuration, creation of NSE in IP dynamic mode.
- At OMC IP endpoint creation window, the address associated to GPU
stays always at initial value (0.0.0.1).
It must be updated with new values from MFS.
Preventive actions: none
Workaround
Corrective actions: perform control station switch-over
Unusable
Usable with WA
Usable with limitation
Impacts



As Gb IP address is not updated at OMC side, it is not possible to
create SGSN IP endpoint and there is no possibilities to communicate
with SGSN.
Occurrence

Very Sporadic

Likely

Sporadic

Yes


FR

3BKA20FBR261064
3BKA20FBR262266

B10
B11

Sub-System
Planned Delivery
Keywords

MFS-SW
Under study in B11
MFS O&M

Severity

Existed before
Current delivery?

Systematic

No


G2

All GPUs rebooted twice after performing RESET MFS from IMT in GboIP
and MXMFS in 2 shelfs

RESTRICTION

MXMFS with 2 shelves, 12 E1 in centralized mode and Gb over IP is configured for 1 GPU. When
performing RESET MFS, all GPUs rebooted - this is a normal. But after some minutes, when CS+PS
traffic became available, all GPUs rebooted again.
Preventive actions: none
Corrective actions: none

Workaround
Impacts

Unusable

Longer PS outage

Usable with WA


Usable with limitation

Occurrence

Very Sporadic

Likely


Sporadic

Yes

Systematic

No


3BKA20FBR272345
3BKA20FBR286674

B10
B11

Existed before
Current delivery?
FR

ED

01

Released

11/25/2009

BSS RESTRICTIONS LIST


BSSSAX01C Ed07 QD5
RELEASE B10
3BK 13016 1261 TQZZA
45/103

All rights reserved. Passing on and copying of this


document, use and communication of its contents not
permitted without written authorization from Alcatel-Lucent

Sub-System
Planned Delivery
Keywords

MFS Evolution
Under study in B11
MFS O&M

G2

Severity

GOM crash due to watchdog expiry

RESTRICTION

GOM didn't succeed to reset the watchdog, so NECTAR considered it faulty and killed it (GOM crash).
Preventive actions: none
Corrective actions: none

Workaround
Impacts

Unusable

none

Usable with WA


Usable with limitation




Occurrence

Very Sporadic

Likely


Sporadic

Yes

Systematic

No


FR

3BKA20FBR271005
3BKA20FBR274179

B10
B11

Sub-System
Planned Delivery
Keywords

MFS
Corrected in B11
MFS O&M

Severity

Existed before
Current delivery?

G2

 GP reset in loop, for multi GP configuration, if reshuffle is performed

RESTRICTION

After step 7 during Software Replacement from B10 MR1ED3 to B10MR2ED7QD2 and in case of Multi
GP BSS, it might happen that all cells will end up mapped on only one GP so it would be normal to
perform reshuffle cells, but this actions lead to all GP reset in loop. The analysis showed that the
problem is due to GP which is not answering in time to GOM, then as defence mechanism, reset is
performed. After the reset, GOM loads the configuration, but cells of same BTS are loaded on 2
different GP's leading to continuous reset's. The solution is to perform a re-init GPRS instead of
reshuffle. It's adviced to check that all GPs of the BSC are in operational state before applying the reinit. If by mistake the reshuffle was applied, the workaround is also to perform re-init, but needs to be
verified that all cells are balanced over the GP's of the BSC. If aren't balanced then should be applied
a reset_data on each GP whithout cells mapped.
Preventive actions: perform a re-init GPRS instead of reshuffle.
Corrective actions: also perform re-init, and in case the cells are not
balanced over the GPs, a reset data should be done on each GP without
cells mapped.

Workaround

Impacts

Unusable


Usable with WA

Usable with limitation




Occurrence

Very Sporadic

Likely

Sporadic

Yes


Systematic

No


3BKA20FBR276240
3BKA20FBR286673

B10
B11

Existed before
Current delivery?
FR

ED

01

Released

11/25/2009

BSS RESTRICTIONS LIST


BSSSAX01C Ed07 QD5
RELEASE B10
3BK 13016 1261 TQZZA
46/103

All rights reserved. Passing on and copying of this


document, use and communication of its contents not
permitted without written authorization from Alcatel-Lucent

Sub-System
Planned Delivery
Keywords

MFS Evolution
Under study in B11
MFS O&M

G1

Severity

 MUX contact error on MFS Evolution during MFS SW Migration

RESTRICTION

During a software replacement of the MFS Evolution, it may happen that the alarm MUX contact error;
Rack 1 Shelf 1 MUX XYZ will appear. The software replacement cannot continue due to blocked MUX
board. In order to go on it is needed to perform a unplug/plug action on the impacted MUX.
Preventive actions: none
Corrective actions: Unplug/plug the impacted MUX board.
Unusable
Usable with WA
Usable with limitation



Software replacement cannot be finished successfully, and intervention on
site is needed.

Workaround
Impacts

Occurrence

Very Sporadic

Likely

Sporadic

Yes


FR

3BKA20FBR276494
3BKA20FBR279751

B10
B11

Sub-System
Planned Delivery
Keywords

MFS Evolution
Under study in B11
MFS O&M

Severity

Existed before
Current delivery?

1.1.7

BSC/TC Extension

1.1.8

Remote Inventory

Systematic

No


G1

Missing removal of Remote Inventory data after reallocation of Network


Element

RESTRICTION

The remote inventory data are not all cleaned when the NE was moved to another OMC or removed.
Preventive actions: none
Corrective actions: none

Workaround
Impacts

Unusable

none

Usable with WA


Usable with limitation




Occurrence

Very Sporadic

Likely


Sporadic

Yes

Systematic

No


3BKA20FBR270216
3BKA20FBR274389

B10
B11

Existed before
Current delivery?
FR
ED

01

Released

11/25/2009

BSS RESTRICTIONS LIST


BSSSAX01C Ed07 QD5
RELEASE B10
3BK 13016 1261 TQZZA
47/103

All rights reserved. Passing on and copying of this


document, use and communication of its contents not
permitted without written authorization from Alcatel-Lucent

Sub-System
Planned Delivery
Keywords

1.1.9

OMC
Under study in B11
Remote Inventory

G2

Severity

BSC OMCR link

1.2 BSS FAULT MANAGEMENT


1.2.1

GSM Fault management

 In case of fans failure, the A9130 BSC Evolution is not automatically


powered off.

RESTRICTION

The four fans have been unplugged in order to check the defense mechanism for temperature
management which is centrally managed in the A9130 BSC Evolution.
Some minor and major alarms were seen only on SSWs boards that were automatically powered off
(none on OMCP and CCPs and TPs boards).
This confirm the today principle which is to power off the boards with too high temperature, but,
depending on the sequence of the temperature issue in the different boards (in particular in case the
switch board is powered-off first), this can lead to loose the BSC HW supervision possibilities, with
BSC boards becoming autonomous.
Even if there are few chances that at least two fans may fail in a short time (MTBF being 65 years) in
the field, A9130 BSC Evolution boards have to be able to autonomously defend themselves against a
temperature issue.
Workaround

Preventive actions: In case major alarms related to temperature events are


raised, be prepared to perform the required actions (boards then entire BSC
Evolution powering-off) in order not to have hardware damages.
Corrective actions: None
Unusable


Impacts

Usable with WA


Usable with limitation




Risk of severe hardware damage up to fire of boards


Occurrence

Sub-System

Very Sporadic

Likely

3BKA20FBR221793
3BKA20FBR234418
BSC Evolution

Planned Delivery
Keywords

Under study in B11


Fault management

Existed before
Current delivery?
FR

ED

01

Sporadic

Yes

B10
B11

Systematic

No


Severity

G1

Released

11/25/2009

BSS RESTRICTIONS LIST


BSSSAX01C Ed07 QD5
RELEASE B10
3BK 13016 1261 TQZZA
48/103

All rights reserved. Passing on and copying of this


document, use and communication of its contents not
permitted without written authorization from Alcatel-Lucent

PV_PEM alarms raised and not cleared from IMT and OMCR after MFS
power off/on

RESTRICTION

The ATCA specification requires a board to continue operating despite loosing power for up to 5ms.
This is true for the node blades installed in the ATCA chassis, but also for the Shelf Managers.
So, when the chassis is powered off, the active shelf manager and OMCP boards are still running
during 5ms, which is enough to send a power alarm towards the OMC-R (Respectively to the IMT)
The shelf managers are powering the IPMI signal board of the PEMs, so they detect the power off
(missing DC power), and generate an alarm.
When the system recovers (after a power on), the shelf manager will not see any alarm on the PEM,
so it will not send a de-assertion event at hpi level, and consequently the alarm at the OMC-R will not
be cleared.
Preventive actions: none
Corrective actions: A Switch over to the other JBXSSW was successful that
alarms disappeared from IMT. In order to eliminate the alarm from OMCR, it
is necessary to perform "Audit Alarm" from MFSUSM.

Workaround

Impacts

Unusable

Unnecessary alarms.

Usable with WA


Usable with limitation




Occurrence

Very Sporadic

Likely


Sporadic

Yes

Systematic

No


FR

3BKA20FBR270108
3BKA20FBR275434

B10
B11

Sub-System
Planned Delivery
Keywords

MFS Evolution
Severity
Under study in B11
BSS fault management

Existed before
Current delivery?

G2

 Wrong reporting of several sensors from JBXPS board

RESTRICTION

It was seen on BSC Evolution that the output of the hpi-sensor-output command is wrongly reported
as e0. The values are reported wrongly for the followings: Breaker open, Output Current, Output
Voltage, Input Voltage.
Preventive actions: none
Corrective actions: none
Unusable
Usable with WA
Usable with limitation


Unreliable information which could mislead the operator that the redundancy
of power is lost

Workaround
Impacts

Occurrence

Very Sporadic

Likely


Sporadic

Yes

FR

3BKA20FBR261517
3BKA20FBR274405

B10
B11

Sub-System
Planned Delivery
Keywords

BSC Evolution
Under study in B11
Fault management

Severity

Existed before
Current delivery?

ED

01

Released

11/25/2009

Systematic

No


G1

BSS RESTRICTIONS LIST


BSSSAX01C Ed07 QD5
RELEASE B10
3BK 13016 1261 TQZZA
49/103

All rights reserved. Passing on and copying of this


document, use and communication of its contents not
permitted without written authorization from Alcatel-Lucent

Short circuit alarm for AGC9E with TMA

RESTRICTION

A BTS with three sectors was installed, using TMA. For power supply and supervision of the three
TMA modules AGC9E are used. Immediately we get the following alarm on each of the three installed
AGCs:
- ENVIR[5] HW-DEGRADED[237] alarm number 14 and 17.
With external power supply the TMAs work without any problem.
Preventive actions: use external power supply
Corrective actions: use external power supply
Unusable
Usable with WA
Usable with limitation



Permanent alarm HW-Degraded

Workaround
Impacts

Occurrence

Very Sporadic

Likely


Sporadic

Yes

FR

3BKA20FBR261522
3BKA20FBR263018

B10
B11

Sub-System
Planned Delivery
Keywords

BTS-SW
Severity
Under study in B11
GSM Fault Management

Existed before
Current delivery?

Systematic

No


G2

 TC Power supply alarm not recognized by MX BSC

RESTRICTION

If the "Power supply " alarm is generated at TC side, it is sent by MT120 boards via Qmux to BSC, but
it is never seen in BSC terminal or OMC terminal if the BSC is an Evolution one.
If the used BSC is an G2 one, the alarm is correct displyed on both sides BSC terminal and OMC .
According with alarm directory the [TSC-ENVIRON, POWER-SUPPLY] [71,0]is only in 9120 BSC, not
on Evolution BSC.
Preventive actions: none
Corrective actions: none
Unusable
Usable with WA
Usable with limitation



Not possible for operator to know if a power supply problem appeares on TC
side

Workaround
Impacts

Occurrence

Very Sporadic

Likely

Sporadic

Yes


FR

3BKA20FBR271489
3BKA20FBR274978

B10
B11

Sub-System
Planned Delivery
Keywords

BSC Evolution
Severity
Under study in B11
GSM Fault Management

Existed before
Current delivery?

ED

01

Released

11/25/2009

Systematic

No


G1

BSS RESTRICTIONS LIST


BSSSAX01C Ed07 QD5
RELEASE B10
3BK 13016 1261 TQZZA
50/103

All rights reserved. Passing on and copying of this


document, use and communication of its contents not
permitted without written authorization from Alcatel-Lucent

ENVIR [5] SUBRACK-POWER [24] alarm not enough accurate in case of


RESTRICTION
TWIN TRE
In case of BTS equipped with TWIN TRE modules, if the alarm ENVIR [5] SUBRACK-POWER [24]
occurs, it could mean that the 2 TRE modules have power issues, but also could mean that all the
subrack module is impacted, and this can mislead the operator because the alarm is not accurate
enough for each case.
Workaround

Preventive actions : none


Corrective actions : none
Unusable
Usable with WA
Usable with limitation



The alarm is not very accurate, and could mislead the operator.

Impacts
Occurrence

Very Sporadic

Likely


Sporadic

Yes

FR

3BKA20FAG284753
3BKA20FAG284755

B10
B11

Sub-System
Planned Delivery
Keywords

BTS SW
Severity
Under study in B11
GSM Fault Management

Existed before
Current delivery?

1.2.2

Systematic

No


G3

GPRS/EDGE Fault Management

After a reset data of all GP from IMT, some alarms appear on other NEs

RESTRICTION

After a reset data of all GP from IMT, there are some alarms such as Fatal Ethernet switch error and
Card failure in addition with those linked to the reset GP.
Further investigation shows that after the reset_data of all GPs, as GPs are not supervised by TOMIX,
TOMIX considers during some seconds, that either Fatal Ethernet switch error and Card failure are
faulty. So, in this case, some alarms are temporarily generated by TOMIX. The GPRS traffic is
recovered after few minutes, when the GPs are recovered after reset.
Preventive actions: Not applicable
Corrective actions: None

Workaround
Impacts

Unusable
Usable with WA
Usable with limitation



GPRS outage only if switch in error is in the same plan as active MUX (case
of switch-over)

Occurrence

Very Sporadic

Likely


Sporadic

Yes

FR

3BKA20FBR242898
3BKA20FBR247628

B10
B11

Sub-System
Planned Delivery

MFS Evolution SW
Under study in B11

Severity

Existed before
Current delivery?

ED

01

Released

11/25/2009

Systematic

No


G2

BSS RESTRICTIONS LIST


BSSSAX01C Ed07 QD5
RELEASE B10
3BK 13016 1261 TQZZA
51/103

GPRS Fault Management

All rights reserved. Passing on and copying of this


document, use and communication of its contents not
permitted without written authorization from Alcatel-Lucent

Keywords

Very long link redundancy (arp timer) at SSW level in one LAN
configuration, for MFS evolution.

RESTRICTION

During the tests with Gb over IP, it was noticed that if one link from MFS Evolution SSW is
disconnected, the MFS supervision from OMC is lost. It was seen that the @MAC link to the floating IP
of the MFS is still the old one. Until the router is updating the arp cache, the link is down.
Preventive actions: none
Corrective actions: not aplicable
Unusable
Usable with WA


MFS supervision from OMC is lost

Workaround
Impacts

Occurrence

Very Sporadic

Likely

Sporadic

Yes


FR

3BKA20FBR261257
3BKA20FBR283606

B10
B11

Sub-System
Planned Delivery
Keywords

MFS Evolution
Severity
Under study in B10
GPRS Fault Management

Existed before
Current delivery?

1.2.3

Usable with limitation

Systematic

No


G2

TC fault management

MT120-TCIF connection lost after HSI cable unplug/plug, or after TCIF take
RESTRICTION
over
Sporadically, it was noticed that after a HSI cable disconnection or after a TCIF takeover, the
connection between some MT120 boards and TCIF board is not re-established, and the impactes
MT120 boards are not visible anymore in TC NEM terminal. The following errors can be seen in the
MT120 traces:
INF 10.06.2009 19:29:37:65 MHS3 PPP 0 is under negociation.
INF 10.06.2009 19:29:37:65 MHS3 PPP 1 is DOWN.
or:
INF 06.01.00 00:39:09:74 MHS3 PPP 0 is under negociation.
INF 06.01.00 00:39:09:74 MHS3 PPP 1 is UP, connected_on: 0.
SEV 06.01.00 00:39:09:74 MHS3 ioctl (SIOCGIFDSTADDR) returned 0xC0A80282
Workaround

Preventive actions : none


Corrective actions : Perform a TCIF take over or MT120 unplug/plug
Unusable


Impacts

Usable with WA

Usable with limitation

The impacted MT120 boards are not visible anymore in TC NEM


Occurrence

ED

01

Very Sporadic


Sporadic

Released

11/25/2009

Systematic


BSS RESTRICTIONS LIST


BSSSAX01C Ed07 QD5
RELEASE B10
3BK 13016 1261 TQZZA
52/103

All rights reserved. Passing on and copying of this


document, use and communication of its contents not
permitted without written authorization from Alcatel-Lucent

Existed before
Current delivery?

Likely


Yes

FR

3BKA20FBR278558
3BKA20FBR284974

B10
B11

Sub-System
Planned Delivery
Keywords

TCIF SW
Under study in B11
TC fault management

Severity

ED

01

Released

11/25/2009

No


G3

BSS RESTRICTIONS LIST


BSSSAX01C Ed07 QD5
RELEASE B10
3BK 13016 1261 TQZZA
53/103

All rights reserved. Passing on and copying of this


document, use and communication of its contents not
permitted without written authorization from Alcatel-Lucent

BSS PERFORMANCE MANAGEMENT

1.2.4

GSM Performance Management

1.2.5

GPRS Performance Management

FTP transfer is stopped after cell reselection source cell in GBR to target
cell in BE or in case of RT resources preemption

RESTRICTION

In case of cell reselection from source cell where GBR (Guaranteed Bit Rate) is possible to target cell
where GBR is not possible, the cell reselection successfully ends but the transfer initially well resumed
in BE (Best Effort) in target cell is suddenly stopped some seconds later. Also, in the case where an
external event preempts RT (Real Time) resources so that GBR is no more possible, the transfer
immediately stops.
Preventive actions: None
Corrective actions: None

Workaround
Impacts

Unusable
Usable with WA
Usable with limitation



The operator must avoid to use the QoS function, the bit rate being not
guaranteed since the transfer is stopped in some cases.

Occurrence

Very Sporadic

Likely


Sporadic

Yes

FR

3BKA20FBR229678
3BKA20FBR229821
3BKA20FBR252028
3BKA20FBR252029

B10
B10
B11
B11

Sub-System
Planned Delivery
Keywords

MFS
Severity
Under study in B11
GPRS Performance Management

Existed before
Current delivery?

Systematic

No


G3

 Wrong values of counters family P531_b (DL LLC throughput distribution


per user)

RESTRICTION

It has been observed that the DL distribution of average LLC throughput per user shows quite bad
throughput, and it doesnt make sense. Most users have LLC throughput in range [0 - 20] Kbps, which
is wrong. Drive tests confirmed that throughput measured at mobile level is not the same as the one
reported by MFS at cell level, due to wrong computation of these counters at MFS level.
Preventive actions: None
Corrective actions: None
Unusable
Usable with WA
Usable with limitation



Wrong and unreliable values for counters belonging to family P531_b.

Workaround
Impacts

Occurrence

ED

01

Very Sporadic


Sporadic


Released

11/25/2009

Systematic

BSS RESTRICTIONS LIST


BSSSAX01C Ed07 QD5
RELEASE B10
3BK 13016 1261 TQZZA
54/103

All rights reserved. Passing on and copying of this


document, use and communication of its contents not
permitted without written authorization from Alcatel-Lucent

Existed before
Current delivery?

Likely


Yes

FR

3BKA20FBR248190
3BKA20FBR284974

B10
B11

Sub-System
Planned Delivery
Keywords

MFS-SW
Under study in B11
GPRS/EDGE telecom

Severity

ED

No


G1

1.2.6

Radio measurements Statistics (RMS) Counters on Electro-Magnetic Emmissions

1.2.7

IMSI Trace

01

Released

11/25/2009

BSS RESTRICTIONS LIST


BSSSAX01C Ed07 QD5
RELEASE B10
3BK 13016 1261 TQZZA
55/103

All rights reserved. Passing on and copying of this


document, use and communication of its contents not
permitted without written authorization from Alcatel-Lucent

1.3 GSM Telecom

1.3.1

GSM Telecom

1.3.2

GSM Quality of Service

Sporadic reboot of MT120 board, during TCIF takeover

RESTRICTION

It was seen once on a configuration with 45 Atermux, where first 6 are in HSI2b and the rest in HSI2a,
that after a TCIF takeover, an AIS alarm appeared on Atermuxes which belongs to MT120 with TEI 51.
It was noticed that the alarms were a consequence of the MT120 board reboot. CS and PS traffic was
interrupted on that board during the reboot action.
Preventive actions: none
Corrective actions: none
Unusable
Usable with WA
Usable with limitation



CS and PS traffic handled by this board was affected

Workaround
Impacts

Occurrence
Existed before
Current delivery?

Very Sporadic

Likely


Sporadic

Yes


FR

3BKA20FBR260051

Sub-System
Planned Delivery
Keywords

TC-SW
Severity
Under study in B10
GSM Quality of Service

Systematic

No

G2

 Only one way voice is heard in case of A_PCM_TP48 is used

RESTRICTION

On a BSC connected to a TC which is equipped with TCIF boards, it was found that in case the CS call
is performed on the A_PCM_TP48, the voice path using this A interface is not functional, and the voice
is heard only on one side. It is happening only in case of TC equipped with TCIF, and only on
A_PCM_TP48, which corresponds to A no. 4 from MT120 board no 48.
Preventive actions: lock A no.4 from MT120 48
Corrective actions: none
Unusable
Usable with WA
Usable with limitation



Voice path works only in one way

Workaround
Impacts

Occurrence
Existed before
Current delivery?

Very Sporadic

Likely


Sporadic

Yes

FR

3BKA20FBR287743

B10

Sub-System
Planned Delivery

TCIF SW
Under study in B10

Severity

ED

01

Released

11/25/2009

Systematic

No

G1

BSS RESTRICTIONS LIST


BSSSAX01C Ed07 QD5
RELEASE B10
3BK 13016 1261 TQZZA
56/103

All rights reserved. Passing on and copying of this


document, use and communication of its contents not
permitted without written authorization from Alcatel-Lucent

Keywords

ED
1.3.3
GSM Adaptive Multi Rate Codec

1.3.4
SMSCB

01

Released

11/25/2009

BSS RESTRICTIONS LIST


BSSSAX01C Ed07 QD5
RELEASE B10
3BK 13016 1261 TQZZA

57/103

All rights reserved. Passing on and copying of this


document, use and communication of its contents not
permitted without written authorization from Alcatel-Lucent

1.4 GPRS/EDGE Telecom

1.5 A1353-OMC-R SYSTEM


1.5.1

OMC-R Man machine interface

1.5.2

OMC-R Configuration Modification

 The network_info.pl script contains many errors

RESTRICTION

The launching of the network_info.pl scriptgives the following wrong results:


1) Wrong values only for OMC B10 versions : Release and Sub-Release fields are wrong in
network_info.csv
Problem: With an OMC B10 MR1 and BSS B9, there were no results given by the script, but it should
give the following values (Release= B10 and Sub-Release= MR1).
While With an OMC B9 and BSS B9, the script gives good result which are (Release= B9 and SubRelease= MR4).
With an OMC B10 MR2 and BSS B10, the result of the script was wrong (Release= B9 and SubRelease= MR4 instead of Release= B10 and Sub-Release= MR2).
2) Wrong values only for OMC B10 MR 2 :
With an OMC and BSS on B10 MR2, the script cant count the MT120 boards. The "CircuitPackType" in
"ACIE_BSS1export_Dir1/AlcatelCircuitPack.csv" for the MT120 boards has changed to "jbmte2" ( it
was "mt120" for the previous versions).
The script returns 0 instead of 12.
3) Wrong values common to every OMC-R release (B9, B10MR1, B10MR2) :
1.
2.
3.
4.
5.
6.
7.
8.
9.
10.

BTS-G4-MBI-3, BTS-G4-MBI-5 .
GP-Boards
Total-TRE-edge.
Total-TRE-HP.
BSC-evolution-ATCA-1.
MFS-DS10RC23 and MFS-DS10RC40
AMR.
TFO.
Multiband-BTS
Total-Two-TRX-Twin

Workaround
Impacts

Preventive actions : Not Applicable


Corrective actions: None.
Unusable
Usable with WA
Usable with limitation



The results related to topology information about customers networks in the
world are not reliable.

Occurrence

ED

01

Very Sporadic


Sporadic


Released

11/25/2009

Systematic

BSS RESTRICTIONS LIST


BSSSAX01C Ed07 QD5
RELEASE B10
3BK 13016 1261 TQZZA
58/103

All rights reserved. Passing on and copying of this


document, use and communication of its contents not
permitted without written authorization from Alcatel-Lucent

Existed before
Current delivery?

Likely

Yes


FR

3BKA20FBR231204
3BKA20FBR274973

Sub-System
Planned Delivery
Keywords

OMC-SW
Severity
Under study in B11
OMC Configuration Modification

No

B10
B11
G2

Sometimes, the BSS declaration in OMC is not possible

RESTRICTION

Sometimes, when the operator wants to perform a BSS declaration in OMC, the following error
message may appear: cannot declare BSS due to SEC service, making the declaration not possible.
It was possible to declare it only after the svc and lss processess were restarted.
Workaround

Impacts

Occurrence

Preventive actions: none


Corrective actions: restart the svc and lss processes:
- svcadm disable svc:/network/ldap/sec7:default svcadm enable
svc:/network/ldap/sec7:default (on Master only, using root user)
- svcadm disable svc:/network/lss/lss:default svcadm enable
svc:/network/lss/lss:default (on Master and HMI)
Unusable
Usable with WA
Usable with limitation



BSS declaration in OMC not always posible
Very Sporadic

Likely

Sporadic

Yes


FR

3BKA20FBR263228
3BKA20FBR273995

B10
B11

Sub-System
Planned Delivery
Keywords

OMC-SW
Severity
Under study in B10
OMCR Configuration Management

Existed before
Current delivery?

Systematic

No


G2

 TS15 and TS16 on not usable on A-Interface : TS16 cannot be used for PS
traffic

RESTRICTION

It was observed that in the current implementation it is not possible to use TS15 and 16 for PS traffic if
the Ater-Mux is 100% dedicated, with BSC Evolution in fron of MFS. For PS A-Interface TS15 and
TS16 is not available at MFS and at the GPU the TS15 and TS16 are not usable for GCH while they
should be.
Workaround
Impacts

Occurrence

Preventive actions: none


Corrective actions: none
Unusable
Usable with WA
Usable with limitation



For PS A-Interface TS15 and TS16 is not available at MFS.
Very Sporadic


Existed before
Likely

Current delivery?
ED
01
Released

Sporadic
Yes

11/25/2009

Systematic

No

BSS RESTRICTIONS LIST
BSSSAX01C Ed07 QD5
RELEASE B10
3BK 13016 1261 TQZZA
59/103

All rights reserved. Passing on and copying of this


document, use and communication of its contents not
permitted without written authorization from Alcatel-Lucent

FR

3BKA20FBR272054
3BKA20FBR274371

B10
B11

Sub-System
Planned Delivery
Keywords

OMC-SW
Under study in B11
OMC Administration

Severity

1.5.3

G1

OMC-R Software Management / Backup-Restore

Old OBSYNT directories are not deleted when the files inside these
RESTRICTION
directories are removed.
It was noticed that after OMC migration from B9 to B10 the daily OBSYNT directories are no more
deleted, even if the content of these directories are deleted. For each OMC in B10, there are empty
OBSYNT directories in the following path /alcatel/var/share/AFTR/APME/OBSYNT/<NEname>/*
which are never deleted by OMC scripts.
Workaround

Preventive actions : none


Corrective actions : manually remove the empty OBSYNT directories.
Unusable
Usable with WA
Usable with limitation



Risk of filling /alcatel partition with unnecessary data.

Impacts
Occurrence

Very Sporadic

Likely


Sporadic

Yes

FR

3BKA20FAG285316
3BKA20FAG287364

B10
B11

Sub-System
Planned Delivery
Keywords

OMC
Under study in B11
OMC Administration

Severity

Existed before
Current delivery?

1.5.4

Systematic

No


G3

OMC-R Administration

Secured (SSL) ICA connections are not properly configured for HMI

RESTRICTION

Sssl ica connections is working properly only in case Citrix is installed on Master. For the HMI part,
there is a bug in install_citrix.sh script which is forwarding the ssl requests to Master IP address and
not to HMI IP address. Due to this issue, SSL ica connections cannot be configured on HMI machines.

ED

01

Released

11/25/2009

BSS RESTRICTIONS LIST


BSSSAX01C Ed07 QD5
RELEASE B10
3BK 13016 1261 TQZZA
60/103

Preventive actions: Edit (as root) on HMI the script


/install/script/install_citrix.sh before launching it as follows:
- in the following line: "FULL_COMMAND2="spawn /usr/local/bin/sudo -u
ctxssl /opt/CTXSmf/sbin/ctxsslcfg -add 443 -certificate $HOST.evolium.com forward add $MASTERIP:1494 -forward add $MASTERIP
:20000"
replace:
MASTERIP with the IP of the HMI (for ex: 192.168.14.23).
- save the file and launch the script.
Corrective actions:
- uninstall Citrix configured unssuccessfuly
- reinstall Citrix taking into account the WA from preventive actio

All rights reserved. Passing on and copying of this


document, use and communication of its contents not
permitted without written authorization from Alcatel-Lucent

Workaround

Impacts

Unusable
Usable with WA
Usable with limitation



SSL ICA connections cannot be configured for HMI unless WA is not applied.
The data transfer between HMIs (as citrix server) and Citrix Clients is not
secured.

Occurrence

Very Sporadic

Likely


Sporadic

Yes

FR

3BKA20FBR259966
3BKA20FBR265034

B10
B11

Sub-System
Planned Delivery
Keywords

OMC-SW
Under study in B11
OMC Administration

Severity

Existed before
Current delivery?

Systematic

No


G2

The alarm "Hard disk problem" is present on every machine (Master,


Agent, and HMI)

RESTRICTION

The alarm for Hard disk problem is raised though there were some hard errors in DVD/CD drive.
Preventive actions: none
Corrective actions: none

Workaround
Impacts

Unusable

Not useful alarm.

Usable with WA


Usable with limitation




Occurrence

Very Sporadic

Likely


Sporadic

Yes

Systematic

No


FR

3BKA20FBR3BKA20F
BR277878
3BKA20FBR274977

B10
B11

Sub-System
Planned Delivery
Keywords

OMC
Severity
Planned in B11
Administration Services

Existed before
Current delivery?

ED

01

Released

11/25/2009

G2

BSS RESTRICTIONS LIST


BSSSAX01C Ed07 QD5
RELEASE B10
3BK 13016 1261 TQZZA
61/103

All rights reserved. Passing on and copying of this


document, use and communication of its contents not
permitted without written authorization from Alcatel-Lucent

1.5.5

OMC-R Supervision

Values in CCP Resources Report are not OK

RESTRICTION

In the CCP Resource Usage Report, the values for the Column RSL without TRE and RSL without
TRX are incorrect.
Preventive actions: none
Corrective actions: none

Workaround
Impacts

Unusable
Usable with WA
Usable with limitation



At the CCP Resource Usage Report same values are incorrect

Occurrence

Very Sporadic

Likely


Sporadic

Yes

FR

3BKA20FBR270214
3BKA20FBR273992

B10
B11

Sub-System
Planned Delivery
Keywords

OMC
Severity
Under study in B11
Administration Services

Existed before
Current delivery?

1.5.6

Systematic

No


G2

OMC-R Alarm Management

Incorrect alarm dictionary extract after selecting an alarm

RESTRICTION

It was found that in case of alarm Loss of Packet Service, if the navigation to Alarm Dictionary is
performed, the informations displayed are not consistent with the alarm. Instead, it is displayed the
informations for another alarm NGISL3 auto test error.
Preventive actions: none
Corrective actions: none
Unusable
Usable with WA
Usable with limitation



Detailed informations concerning the alarm are wrong

Workaround
Impacts

Occurrence

Very Sporadic

Likely

Sporadic

Yes


FR

3BKA20FBR259871
3BKA20FBR274383

B10
B11

Sub-System
Planned Delivery
Keywords

OMC-SW
Severity
Under study in B10
OMC-R Alarm Management

Existed before
Current delivery?

ED

Systematic

No


G2

Wrong information in Alarm Dictionary for a QoS alarm


01

Released

11/25/2009

RESTRICTION

BSS RESTRICTIONS LIST


BSSSAX01C Ed07 QD5
RELEASE B10
3BK 13016 1261 TQZZA
62/103

All rights reserved. Passing on and copying of this


document, use and communication of its contents not
permitted without written authorization from Alcatel-Lucent

In ASUSM window, the QoS alarm RTCH_AVAILABLE_RATE is present for a BTS. When trying to
navigate to External Application -> Alarm Dictionary the informations are wrongly displayed for BTSExternal Alarm instead of expected QoS alarm. Also, the corective actions presented are not for QoS
alarm, but for BTS-External Alarm.
Preventive actions: none
Corrective actions: none
Unusable
Usable with WA
Usable with limitation



Wrong alarm information displayed in Alarm Dictionary

Workaround
Impacts

Occurrence

Very Sporadic

Likely


Sporadic

Yes

FR

3BKA20FBR266752
3BKA20FBR274388

B10
B11

Sub-System
Planned Delivery
Keywords

OMC-SW
Severity
Under study in B10
OMC-R Alarm Management

Existed before
Current delivery?

Systematic

No


G2

Wrong incrementation of repetition counter for the alarm CELL [43]


LOSS-OF-TCH [2]

RESTRICTION

It was observed on OMC that for one cell, the repetition counter corresponding to alarm CELL [43]
LOSS-OF-TCH [2] was having an abnormal high value. The value of this repetition counter was
wrongly incremented each time a BSC alarm/state audit was performed.
Preventive actions: none
Corrective actions: none
Unusable
Usable with WA
Usable with limitation



Unreliable information provided to operator for the repetition counter

Workaround
Impacts

Occurrence

Very Sporadic

Likely

Sporadic

Yes


FR

3BKA20FBR267690
3BKA20FBR274361

B10
B11

Sub-System
Planned Delivery
Keywords

BSC Evolution
Severity
Under study in B10
OMC-R Alarm Management

Existed before
Current delivery?

Systematic

No


G2

Date and time not correctly updated for TCIF takeover alarm

RESTRICTION

When performing several successive TCIF RESET actions on active TCIF, alarm is raised with correct
repetitive counter but the date and time never updated. The date and time coresponds always to the
date and time of the first occurence.
Preventive actions: none
Corrective actions: none

Workaround

ED

01

Released

11/25/2009

BSS RESTRICTIONS LIST


BSSSAX01C Ed07 QD5
RELEASE B10
3BK 13016 1261 TQZZA
63/103

All rights reserved. Passing on and copying of this


document, use and communication of its contents not
permitted without written authorization from Alcatel-Lucent

Impacts

Unusable
Usable with WA


Incorrect Date and time of the event

Usable with limitation




Occurrence

Very Sporadic

Likely


Sporadic

Yes


Systematic

No

FR

3BKA20FBR268875
3BKA20FBR283244

B10
B11

Sub-System
Planned Delivery
Keywords

OMC-SW
Severity
Under study in B10
OMC-R Alarm Management

Existed before
Current delivery?

1.5.7

G2

OMC-R Performance Management

If MPM is stopped for any reason, there is no easy way to restart it

RESTRICTION

For an unknown reason, MPM was not running even though Oracle processes were correct.
As MPM is not managed by DSM, it is not possible to restart it except by stopping completely the OMC
and running again MF-START.
Preventive actions: Not applicable
Corrective actions: Manually run the following Muse starting sequence:

Workaround

$ /alcatel/muse/OMC_SM/scripts/start.sh
$ /alcatel/muse/OMC_LOCAL/scripts/runLogim.sh
$ /alcatel/muse/MUSE_MAAT/server/scripts/startNPO.sh 0
Impacts

Unusable
Usable with WA
Usable with limitation



The operator can not take advantage of MPM for managing the alerters on a
daily basis.

Occurrence
Existed before
Current delivery?

Very Sporadic

Likely


FR

3BKA20FBR252362

Sub-System
Planned Delivery
Keywords

OMC
Severity
Under study in B10
OMC-R Performance Management

1.5.8

Sporadic

Yes

01

G2

OSI Q3 interface to the NMC

 Sleeping Q3 interface observed several times


ED

Systematic

No


Released

11/25/2009

RESTRICTION

BSS RESTRICTIONS LIST


BSSSAX01C Ed07 QD5
RELEASE B10
3BK 13016 1261 TQZZA
64/103

All rights reserved. Passing on and copying of this


document, use and communication of its contents not
permitted without written authorization from Alcatel-Lucent

Sporadically, it was noticed that the interface between OMC and NMC is frozen. The behavior noticed
was that no record was inserted anymore in the LOG and no alarm is received at NMC. The interface
was operational again after the osimcs and q3im processess were stopped and restarted.
Preventive actions: none
Corrective actions: Stop/start osimcs ans q3im processes
Unusable
Usable with WA
Usable with limitation



No network supervision via Q3 possible.

Workaround
Impacts

Occurrence

Very Sporadic

Likely

Sporadic

Yes


FR

3BKA20FBR274579
3BKA20FBR282405

B10
B11

Sub-System
Planned Delivery
Keywords

OMC
Severity
Under study in B11
Q3 interface to the NMC

Existed before
Current delivery?

1.5.9

Systematic

No


G1

Alarm call out function

1.5.10 OMCR Stability

1.6 STABILITY AND PERFORMANCE


1.6.1

Sub-system OMC-R

 Failed to add BSC to OAD via SECusm

RESTRICTION

BSC process restart in loop after reboot master and agent, workaround applied was "How to remove
BSSIM database without losing data" so recreated BSC successfully.This BSC belonged to a specific
OAD that operators using OAD access to this BSC .Opening OAD via SECusm and select specific
OAD fails. It show messages windows "Operation aborted: processing failure exception" Impact :Can
not add BSC to OAD
Preventive actions: none
Corrective actions: stop/atart BSSIM process, and restart BSSUSM
Unusable
Usable with WA
Usable with limitation



Perform the BSSIM database remove/recreate as described in the TSG

Workaround
Impacts

Occurrence
Existed before
Current delivery?

Very Sporadic

Likely


Sporadic

Yes

FR

3BKA20FBR276963

B10 impacted version


B11 Fixed version

Sub-System
Planned Delivery
Keywords

OMC-SW
Fixed in B11
OMC Stability

Severity

ED

01

Released

11/25/2009

Systematic

No


G1

BSS RESTRICTIONS LIST


BSSSAX01C Ed07 QD5
RELEASE B10
3BK 13016 1261 TQZZA
65/103

All rights reserved. Passing on and copying of this


document, use and communication of its contents not
permitted without written authorization from Alcatel-Lucent

 BSSIM crash due to Assertion Failure

RESTRICTION

While running a nominal tests capmaign, suddenly it was noted that BSSIM crashed and the following
error was reported: (src/agentkernel/mocore/MoCore.cc: 444). After a STOP/START of BSSIM
process, the BSSUSM was running normal again.
Preventive actions: none
Corrective actions: stop/atart BSSIM process, and restart BSSUSM
Unusable
Usable with WA
Usable with limitation



BSSUSM not available until workaround is applied

Workaround
Impacts

Occurrence

Very Sporadic

Likely


Sporadic

Yes

FR

3BKA20FBR263849
3BKA20FBR274384

B10
B11

Sub-System
Planned Delivery
Keywords

OMC-SW
Under study in B10
OMC Stability

Severity

Existed before
Current delivery?

Systematic

No


G2

 Re-init and resynchronize GPRS fails due to error during file transfer

RESTRICTION

It may happen very sporadic that the actions Re-init or resynchronize GPRS performed from OMCR
are failing with the following misalignment cause: The file transfer between RNIM and the MFS is not
possible. Investigations showed that the error is due to a bug on SUN machine, for which SUN has
provided a workaround: reboot the SUN machine. There is no planned solution for this problem, only
the WA provided.
Preventive actions: none
Corrective actions: reboot the SUN machine
Unusable
Usable with WA
Usable with limitation



Re-init and resynchronize GPRS cannot be performed

Workaround
Impacts

Occurrence
Existed before
Current delivery?

Very Sporadic

Likely


Sporadic

Yes

FR

3BKA20FBR274598

B10

Sub-System
Planned Delivery
Keywords

OMC SW
No solution planned
OMC Stability

Severity

ED

1.6.2

Sub-system BSC Legacy

1.6.3

Sub-system BSC Evolution

01

Released

11/25/2009

Systematic

No

G1

BSS RESTRICTIONS LIST


BSSSAX01C Ed07 QD5
RELEASE B10
3BK 13016 1261 TQZZA
66/103

All rights reserved. Passing on and copying of this


document, use and communication of its contents not
permitted without written authorization from Alcatel-Lucent

The insecure FTP for A9130 BSC Evolution should be disabled, because
SSH is available

RESTRICTION

The insecure FTP for A9130 BSC Evolution should be disabled, because SSH is available.
Till now, FTP is used as a 'telecom operational' protocol in a very defined way for distribution of public
files, as read only (very similar to an usual read only public FTP server which is allowed too in the
internet)
For information, current view in B11, following security workshop is:
- Only IP-sec with BTS
- OMC-MxBSC : plan is to switch from FTP to SFTP
- OMC-MxMFS : plan is to switch from FTP/SSH to SFTP
So, the plan is not to have IP-sec everywhere in B11
Workaround

Preventive actions : None


Corrective actions : None

Impacts

Unusable
Usable with WA


FTP access is somehow uncontrolled

Usable with limitation

Existed before
Current delivery?

Very Sporadic

Likely


Systematic

No


FR

3BKA20FBR219689

Sub-System
Planned Delivery
Keywords

BSC Evolution
Severity
No solution planned
BSC Evolution Performance

Occurrence

Sporadic

Yes

G2

 Telecom outage on BSC Evolution due to unsuccessful TP takeover

RESTRICTION

On BSC Evolution it was noticed a problem on all Ater channels, causing a complete telecom outage.
Investigations showed that this issue was caused by an unsuccessful TP takeover which was triggered
internally by the BSC, due to some HDLC channels blocked inside BSC. Issue was solved after TP
board was plugged out/in.
Preventive actions: none
Corrective actions: Plug out/in the impacted TP board.
Unusable
Usable with WA
Usable with limitation



Telecom outage on entire BSC until TP boards is plugged out/in.

Workaround
Impacts

Occurrence

Very Sporadic

Likely

Sporadic

Yes


FR

3BKA20FBR280476
3BKA20FAG285928

B10
B11

Sub-System
Planned Delivery
Keywords

BSC Evolution
Severity
Under study in B11
BSC Evolution Performance

Existed before
Current delivery?

ED

01

Released

11/25/2009

Systematic

No


G1

BSS RESTRICTIONS LIST


BSSSAX01C Ed07 QD5
RELEASE B10
3BK 13016 1261 TQZZA
67/103

All rights reserved. Passing on and copying of this


document, use and communication of its contents not
permitted without written authorization from Alcatel-Lucent

1.6.3.1

BSC OMC-R link

1.6.4

Sub-system BTS

1.6.5

Sub-system TC

Toggling alarm VOLTAGE_MINOR [16] for both TCIF boards

RESTRICTION

Sporadically it was observed that alarm VOLTAGE_MINOR[16] is raised on OMCR for a TC rack
equipped with TCIF boards. The alarm is generated by TCIF because the voltage measurement is
done by using an AD converter and the precision of the converter is : -10%, +5%.
So a 1.3 V can be measured between 1.218 V and 1.441 V, and, due to this inaccuracy, the minor
alarm threshold, set at 1.25V, is not really significant.
Preventive actions: None
Corrective actions: None
Unusable
Usable with WA


Toggling alarms on OMC for TCIF boards.

Workaround
Impacts

Occurrence

Very Sporadic

Likely


Sporadic

Yes

FR

3BKA20FBR261698
3BKA20FBR286768

B10
B11

Sub-System
Planned Delivery
Keywords

TCIF SW
Severity
Under study in B11
TC Stability and Performance

Existed before
Current delivery?

1.6.6

Sub-system MFS Legacy

1.6.7

Sub-system MFS Evolution

 "Loss of contact with GPU" MFS alarms

Usable with limitation

Systematic

No


G2

RESTRICTION

It was noticed on different MFS Evolutions an increased number of loss of contact with GPU alarms,
which leads to loss of GPRS traffic on those GPs.
Preventive actions: none
Corrective actions: perform reset all action on the impacted GPs

Workaround

ED

01

Released

11/25/2009

BSS RESTRICTIONS LIST


BSSSAX01C Ed07 QD5
RELEASE B10
3BK 13016 1261 TQZZA
68/103

All rights reserved. Passing on and copying of this


document, use and communication of its contents not
permitted without written authorization from Alcatel-Lucent

Impacts

Unusable
Usable with WA


Loss of GPRS traffic on the impacted GPs.

Usable with limitation




Occurrence
Existed before
Current delivery?

Very Sporadic

Likely

Sporadic

Yes


Systematic

No


FR

3BKA20FAG276122

B10

Sub-System
Planned Delivery
Keywords

MFS Evolution
Severity
Under study in B10
MFS Evolution Stability and Performance

G1

 Total GPRS Outage during 15 min on MFS Evolution

RESTRICTION

It was noticed on one MFS Evolution that during 15 minutes there was a total GPRS traffic outage
because Station A and Station B rebooted both in the same time. This behavior was caused by a Linux
crash. The traffic was recovered autonomously without any intervention.
Preventive actions: none
Corrective actions: none
Unusable
Usable with WA
Usable with limitation



Total GPRS outage on entire MFS Evolution for about 15 minutes

Workaround
Impacts

Occurrence

Very Sporadic

Likely

Sporadic

Yes


FR

3BKA20FBR267980
3BKA20FBR274824

B10
B11

Sub-System
Planned Delivery
Keywords

MFS Evolution
Severity
Under study in B11
MFS Evolution Stability and Performance

Existed before
Current delivery?

ED

01

Released

11/25/2009

Systematic

No


G1

BSS RESTRICTIONS LIST


BSSSAX01C Ed07 QD5
RELEASE B10
3BK 13016 1261 TQZZA
69/103

All rights reserved. Passing on and copying of this


document, use and communication of its contents not
permitted without written authorization from Alcatel-Lucent

1.7 LOCAL TERMINALS

There is no alarm displayed on the IMT when the standby Switch board is
extracted

RESTRICTION

When pulling the extractor bracket in order to extract the standby switch board, no alarm notifying the
extraction of the switch is displayed on the IMT.
When the switch is physically extracted, the physical view shows always 2 switches in operational
state.
On the shelf manager, the "hpievent" command shows that the extraction event is triggered.
Preventive actions: None
Corrective actions: Perform an "hpievent" command in order to show that
the extraction event is triggered

Workaround

Unusable
Usable with WA
Usable with limitation



The operator is mislead by the IMT physical view which shows the 2 switches
in operational state.

Impacts

Occurrence

Very Sporadic

Likely

Sporadic

Yes


FR

3BKA20FBR210268
3BKA20FBR251781

B10
B11

Sub-System
Planned Delivery
Keywords

MFS-SW
Under study in B11
Local Terminals

Severity

Existed before
Current delivery?

Systematic

No


G2

Some information are missing for the MT120 boards when the TC-NEM is
connected via TCIF

RESTRICTION

When a TC-NEM is directly connected to an MT 120 board, there is a panel called "Config. (readonly)"
containing some information about:
1- LAPD configuration
2- CRC4
3- Sync Config
4- SMHWAY
5- Alarm octet TS
These information are missing in the panel MT120 Config with TC NEM on TCIF but it was a decision
to do not put them on remote connection (via TCIF) in order to do not load MMI relay mechanism with
not useful (or redundant) information.
Preventive actions: Not applicable
Corrective actions: to directly connect the TC-NEM to the MT120 board to
get the listed transmission parameters

Workaround

Unusable


Impacts

ED

01

Usable with WA

Released

11/25/2009

Usable with limitation




BSS RESTRICTIONS LIST


BSSSAX01C Ed07 QD5
RELEASE B10
3BK 13016 1261 TQZZA
70/103

All rights reserved. Passing on and copying of this


document, use and communication of its contents not
permitted without written authorization from Alcatel-Lucent

Not a real impact since all these parameters related to transmissions are not
changeable by TC-NEM (only readable for local connection) and are all taken
from the BSC.
Occurrence

Very Sporadic

Likely


Sporadic

Yes


FR

3BKA20FBR257277
3BKA20FBR284966

B10
B11

Sub-System
Planned Delivery
Keywords

TC-NEM
No solution planned
MT120 usage

Severity

Existed before
Current delivery?

Systematic

No

G2

TCNEM sometimes remains hanging

RESTRICTION

It may sometimes happen that TC-NEM freezes. Seen sometimes during MT120 SW preload.
Preventive actions: none
Corrective actions: kill the application from task manager and re-open it.

Workaround
Impacts

Unusable
Usable with WA


Terminal freezes, needs to be re-opened.

Usable with limitation




Occurrence
Existed before
Current delivery?

Very Sporadic

Likely


Sporadic

Yes


Systematic

No

FR

3BKA20FBR254920

Sub-System
Planned Delivery
Keywords

TC-NEM
No solution planned
Local Terminals

Severity

G2

When performing the MT120 board replacement, the wizard provided by


TC NEM never ends

RESTRICTION

In case an MT120 board need to be replaced, the wizard provided by TC NEM is never ending, even if
the replacement action is finally successful. The following operation were performed:
- replacement of a HSI board by a board previously in TCIL
- replacement of a TCIL board by a board previously in TCIL
- replacement of a TCIL board by a board previously in HSI
In all cases, the wizard provided by TC-NEM never ends and keep open the window saying "Waiting till
file info from new board received".
Preventive actions: none
Corrective actions: Select another board in TC-NEM
Unusable
Usable with WA
Usable with limitation



The message could mislead the operator about the replacement operation.

Workaround
Impacts

ED

01

Released

11/25/2009

BSS RESTRICTIONS LIST


BSSSAX01C Ed07 QD5
RELEASE B10
3BK 13016 1261 TQZZA
71/103

All rights reserved. Passing on and copying of this


document, use and communication of its contents not
permitted without written authorization from Alcatel-Lucent

Occurrence
Existed before
Current delivery?

Very Sporadic

Likely


Sporadic

Yes

FR

3BKA20FBR270350

B10

Sub-System
Planned Delivery
Keywords

TC NEM SW
Under study in B10
Local terminals

Severity

Systematic

No

G2

 Even if one TCIF board is power-off, the TCIF board appears OK at TCNEM

RESTRICTION

On a TC rack equipped with TCIF boards, it was noticed that in case one of the TCIF boards is
removed, or if the handler is moved until the blue led is seen, there is no feedback on TC NEM. The
TC NEM shows the TCIF boards as if they are OK, which is not the case. Still, the alarm appear at
OMC side, only TC NEM is not showing this action. Still, as the board cannot be unplugged by itself,
the operator is aware of this action, and there the fact that this is not shown on TC NEM side is not
critical.
Preventive actions: none
Corrective actions: check the alarm on OMC side
Unusable
Usable with WA
Usable with limitation



The unplugged TCIF board is displayed as IT at TC NEM terminal.

Workaround
Impacts

Occurrence
Existed before
Current delivery?

Very Sporadic

Likely


Sporadic

Yes

FR

3BKA20FBR273709

B10

Sub-System
Planned Delivery
Keywords

TC NEM SW
No solution planned
Local terminals

Severity

Systematic

No

G1

1.8 ADMINISTRATION SERVICES

ED

01

Released

11/25/2009

BSS RESTRICTIONS LIST


BSSSAX01C Ed07 QD5
RELEASE B10
3BK 13016 1261 TQZZA
72/103

All rights reserved. Passing on and copying of this


document, use and communication of its contents not
permitted without written authorization from Alcatel-Lucent

2. RESTRICTIONS FROM PREVIOUS RELEASES


The IP addresses for a BSC Evolution must follow the following rules :
BSC Evolution external addresses must not belong to the following networks : 172.16/16,
172.17/16, 172.18/16
OMC or any other equipment that interacts with the BSC Evolution must not belong to the
following networks : 172.16/16, 172.17/16, 172.18/16
In the case of an O&M link on MLPPP, the BSC Evolution external addresses must not belong to the
network : 1.1.1.0/29

2.1 BSS O&M CONFIGURATION MANAGEMENT


2.1.1

BSS Hardware Configuration Management

Wrong TRE and RSL number after create BTS and unlock BTS O&M

RESTRICTION

In specific case when creating BTS, it may happen that some additional unequipped TREs are created
in the OMC-R/BSC. The specific case applies only if :
- The new BTS is one which has been previously deleted (and not commissioned again before the
creation)
-

The BTS was moved from one BSC to another.

For those cases, if the BTS contains at least one equipped TRE which has the TRE id greater than the
total number of the equipped TREs, then, after unlock BTS O&M, a wrong TRE/RSL numbering can be
seen.
Preventive actions: Avoid creating TRE sequence with gaps.
Corrective actions: Delete the not equipped TREs from the OMC-R by using
View BTS/Modify BTS characteristics window and reduce the number of TRE
to the number of the equipped one and apply.

Workaround

Unusable
Usable with WA


Useless TRE displayed in OMC-R.

Usable with limitation




Existed before
Current delivery?

Very Sporadic

Likely


Systematic

No


FR

3BKA20FBR131871

Sub-System
Planned Delivery
Keywords

BTS
G2
Severity
No solution planned
Hardware Configuration /Network modification BTS

Impacts
Occurrence

ED

Sporadic

Yes

Rate allocation not as requested by the operator when creating a BTS

01

Released

11/25/2009

RESTRICTION

BSS RESTRICTIONS LIST


BSSSAX01C Ed07 QD5
RELEASE B10
3BK 13016 1261 TQZZA
73/103

All rights reserved. Passing on and copying of this


document, use and communication of its contents not
permitted without written authorization from Alcatel-Lucent

In some specific situation the Create BTS action does not lead to the configuration declared and
expected by the operator.
The problem is seen in case of multi-band sector with GSM/DCS TRE(A) declared and mixed
allocation of FR/DR configuration per sector. When the BTS is created, the allocation of FR/DR on
TREs might be different than the one requested from the OMC-R
If the created BTS is not as declared, then open Modify BTS Characteristic window, set-up the correct
FR/DR allocation configuration and apply.
Workaround

Impacts

Occurrence
Existed before
Current delivery?
FR
Sub-System
Planned Delivery
Keywords

Preventive actions : Not applicable


Corrective actions: After creation of BTS, if the configuration is not the
desired one, open the Modify-BTS-Characteristics window from OMC-R, on
impacted BTS and modify the number of FR and DR GSM and DCS TRE.
Unusable
Usable with WA
Usable with limitation



Ratio of FR/DR TREs on each of the 2 frequency bands will be different from
the one requested by the operator
Very Sporadic
Sporadic
Systematic



Likely
Yes
No



3BKA20FBR139372
BSC
G2
Severity
No solution planned
Hardware Configuration / Network modification BTS

2.1.2

On-line Hardware Configuration Management

2.1.3

TCU/RSL re-mapping

2.1.4

On-line BTS extension/reduction

2.1.5

GPRS/EDGE Hardware Configuration Management

The OMC-R allows wrongly to change an Atermux carrying MLPPP from


mixed CS/GPRS to dedicated GPRS

RESTRICTION

It is currently possible to change an Atermux carrying MLPPP from mixed CS/GPRS to dedicated
GPRS. This should be refused unless an MLPPP reduction is first performed
Preventive actions:
Reduce the MLPPP link from the BSC-Terminal before the Atermux
Granularity change
Corrective actions:
Reduce the MLPPP link from the BSC-Terminal

Workaround

Unusable
Usable with WA
Usable with limitation



The MLPPP link carried by the involved Atermux is lost and no warning is
issued to the operator during the reconfiguration action. However, an
MLPPP-PARTIAL-FAILURE is active until MLPPP reduction is performed

Impacts

ED

01

Released

11/25/2009

BSS RESTRICTIONS LIST


BSSSAX01C Ed07 QD5
RELEASE B10
3BK 13016 1261 TQZZA
74/103

All rights reserved. Passing on and copying of this


document, use and communication of its contents not
permitted without written authorization from Alcatel-Lucent

Occurrence

Very Sporadic

Likely


Sporadic

Yes

FR

3BKA20FBR214905
3BKA20FBR218329
3BKA20FBR219740

B9
B10
B11

Sub-System
Planned Delivery
Keywords

OMC-R
G2
Severity
Under study in B11
GPRS/EDGE Hardware Configuration Management

Existed before
Current delivery?

2.1.6

Systematic

No


BSS Logical Configuration Management

Starting from B9, the current memory pool size for an A9210 BSC cannot
support the required maximum number of 3500 adjacent cells for the
Display Adjacent Cell ID.

RESTRICTION

Starting from B9, the A9120 BSC can have a maximum of 3500 adjacencies stored in the DLS through
R_PAR_ADJ. When the BSC receives the command Display Adjacent Cell ID, it goes through the
3500 tuples of R_PAR_ADJ. The memory pool in the A9120 BSC is then used up, that leads to an
OSI-CPR restart and consequently the report to display at the OMC-R is lost.
This restriction is not applicable for A9130 BSC Evolution.
Preventive actions: Do not create more than 2170 adjacent cells with an
A9120 BSC
Corrective actions: remove adjacent cells in order not to go over 2170

Workaround

Impacts

Unusable
Usable with WA
Usable with limitation



For a number greater than 2170 cell adjacencies in an A9120 BSC, the report
related to the list of adjacent cell IDs cannot be displayed at the OMC-R

Occurrence
Existed before
Current delivery?

Very Sporadic

Likely


FR

3BKA36FBR198184

Sub-System
Planned Delivery
Keywords

BSC Legacy
Severity
No solution planned
BSS Logical Configuration Management

ED

Sporadic

Yes

Systematic

No

G3

Change cell type: Lock/unlock BTS-O&M on former "inner zone" is necessary


after changing an extended enlarged cell into two single cells

01

Released

11/25/2009

RESTRICTION

BSS RESTRICTIONS LIST


BSSSAX01C Ed07 QD5
RELEASE B10
3BK 13016 1261 TQZZA
75/103

All rights reserved. Passing on and copying of this


document, use and communication of its contents not
permitted without written authorization from Alcatel-Lucent

After cell reconfiguration from extended enlarged cell (with inner/outer zone mapped over two sectors)
into two normal cells (one on each BTS sector), calls cannot be performed anymore on "former inner
cell" because the TRE carrying the BCCH timeslot of this cell is not well configured from telecom point
of view.
This wrong telecom configuration appear because an earlier unlock of BTS O&M was made (part of
the reconfiguration scenario triggered automatically by OMC-R), before the cell is reconfigured in BSC
database, which will trigger BSC to reconfigure the BTS in an inadequate moment.
Preventive actions : Not applicable
Corrective actions: At the end of extended enlarged cell reconfiguration
scenario (triggered by apply PRC), to force a good BTS reconfiguration, a
manual lock/unlock of BTS O&M action must be made from OMC-R BSSUSM.

Workaround

Impacts

Unusable
Usable with WA
Usable with limitation



Telecom outage on "former inner cell" after extended enlarged cell
reconfiguration is slightly increased until the corrective action is applied.
Note that the 2nd cell telecom configuration is well made and at the end calls
are possible on "former outer cell".

Occurrence

Very Sporadic
Sporadic
Systematic



Whenever extended cell is reconfigured to two normal cells.

Existed before
current delivery?

Likely


Yes

FR

3BKA20FBR110716
3BKA20FBR110857

B7.2
B7.2

Sub-System
Planned Delivery
Keywords

OMC-R
No solution planned
Logical Configuration

Severity

No


G2

In case of BSS/OMC-R inconsistency due to restoring an old DLS: LAC - CI


conflict warning during upload

RESTRICTION

If during an upload the OMC-R displays the following warning " the uploaded cell LAC/CI xxx,yyy can
not be created due to LAC+CI conflict" whereas this cell already exists in the OMC-R (and can be seen
in RNUSM), it means that the mapping LAC/CI versus BTS reported by the BSC during the audit is
different than the mapping known at OMC-R side (i.e. BSC is reporting cell A on BTS X and cell B on
BTS Y and for the OMC-R the cell A is mapped on BTS Y, cell B being mapped on BTS X).
Preventive actions: If A1353-RA Configuration Handbook (the chapter
Restore BSC database) is followed this problem will not occur.
Corrective actions : In this case the operator must do the following :
- in a PRC rename the cell A into a dummy LAC /CI
- re-perform the logical audit
In a second PRC rename the cell with a dummy LAC/CI into cell A.

Workaround

Impacts

Occurrence

ED

01

Unusable


Usable with WA

Very Sporadic


Sporadic

Released

11/25/2009

Usable with
limitation

Systematic


BSS RESTRICTIONS LIST


BSSSAX01C Ed07 QD5
RELEASE B10
3BK 13016 1261 TQZZA
76/103

All rights reserved. Passing on and copying of this


document, use and communication of its contents not
permitted without written authorization from Alcatel-Lucent

It may happen only when an old DLS is restored and an upload radio is
performed and is therefore a very seldom case.
Existed before
current delivery?

Likely


Yes

FR

3BKA20FBR102458
3BKA20FBR101188
3BKA20FBR102457
3BKA20FBR101189

B7
B6.2
B7
B6.2

Sub-System
Planned Delivery

OMC-R
No solution planned

Severity

Keywords

Logical configuration

2.1.6.1

Force Configuration

2.1.6.2

GPRS/EDGE Logical Configuration Management

No


G2

 In case of an E-GSM cell set up with mixed TREs (TRGM & TRAGE), EGPRS
is degraded

RESTRICTION

An E-GSM cell mapped on a BTS sector set up with a mix of G3 and G4 TREs is working fine as long
as EGPRS is not introduced on this cell.
However, at EGPRS activation, in case the preferred TRX is mapped on a G3 TRE, the MFS is not
able to provide a good Edge service because, due to RAE4 mechanism, the only available TS for
packet is given on this first TRX.
Note: the problem is only affecting sites with mix of TREs (TRGM & TRAGE).
Preventive actions :
HW configuration in case of mixed TREs being to have at least 2 G4 TREs
- set BCCH not preferred as PS (PS_PREF_BCCH_TRX = No preference)
- set 2 to N TRX as PS TRX (TRX_PREF_MARK = 0 on as many TRX as
N, N being the number of G4 TRE with 2 as a minimum)
Corrective actions : None

Workaround

Unusable
Usable with WA
Usable with limitation



An alarm appears meaning that EGPRS status is degraded.

Impacts
Occurrence
Existed before
Current delivery?

Very Sporadic

Likely


Sporadic

Yes

FR

3BKA20FBR184427

B8

Sub-System
Planned Delivery
Keywords

BSC-SW
Severity
No solution planned
GPRS Logical Configuration Management

ED

01

Released

11/25/2009

Systematic

No

G1

BSS RESTRICTIONS LIST


BSSSAX01C Ed07 QD5
RELEASE B10
3BK 13016 1261 TQZZA
77/103

All rights reserved. Passing on and copying of this


document, use and communication of its contents not
permitted without written authorization from Alcatel-Lucent

2.1.7

Extensive Logical Configuration update

Abort command sent from OMC-R is not taken into account by BSC during
MLU pre-loading

RESTRICTION

During a MLU pre-loading phase the BSC does not take into account the Abort command received
from the OMC-R, the pre-load being done up to the end by the BSC.
Preventive actions : Wait for BSC to be in preloaded state before triggering
MLU Abort
Corrective actions : Not applicable

Workaround

Unusable
Usable with WA
Usable with limitation



Errors are displayed in Follow-up and there is a loss of supervision for few
minutes.

Impacts

Occurrence

Very Sporadic

Likely


Sporadic

Yes

FR

3BKA20FBR138789
3BKA20FBR139735

B8
B9

Sub-System
Planned Delivery
Keywords

BSC
No solution planned.
MLU

Severity

Existed before
Current delivery?

Systematic

No


G2

If cell re-mapping operations are applied via MLU, the impacted cell needs
to be manually unlocked at the end of reconfiguration

RESTRICTION

If cell re-mapping operation, un-map and re-map cell, are applied via MLU mode, the impacted cell will
remain locked at the end of reconfiguration.
It is recommended to apply such simple re-mapping operations via PRC message mode. In this case,
the cell will not remain locked at the end.
Preventive actions : Not Applicable.
Corrective actions : Unlock manually the cell from RNUSM in case the
modification was applied via MLU mode.
It is recommended to perform re-mapping operations via PRC message
mode.

Workaround

Impacts

Unusable
Usable with WA
Usable with limitation



If re-mapping cell is done in MLU mode, the cell will remain locked after
"Apply MLU". Corrective actions need to be applied to have it operational.
The normal outage time caused by un-map/re-map operation is extended
with few seconds due to the need of applying the workaround.

Occurrence

ED

01

Very Sporadic


Sporadic


Released

11/25/2009

Systematic

BSS RESTRICTIONS LIST


BSSSAX01C Ed07 QD5
RELEASE B10
3BK 13016 1261 TQZZA
78/103

All rights reserved. Passing on and copying of this


document, use and communication of its contents not
permitted without written authorization from Alcatel-Lucent

Systematic only when the operation is applied in MLU mode.


Existed before
current delivery?

Likely


Yes

FR

3BKA20FBR115518

Sub-System
Planned Delivery
Keywords

OMC-R
Severity
No solution planned
Logical Configuration / MLU.

No

G2

In case of BSS / OMC-R inconsistency due to restoring an old DLS: Pure


reselections are lost if BCCH frequency of the target cell is changed by
upload radio parameters

RESTRICTION

If, for any reason (e.g. backup of an old DLS), there is a discrepancy between the DLS running in the
BSS and the OMC-R for the BCCH frequency of a cell A and if cell A is the target of a pure reselection
link (both at OMC-R and BSS side), then this reselection link will be lost at OMC-R side if a logical
audit (or upload radio) is performed. The OMC-R will indicate a warning in RNUSM follow up "there is
a reselection found in the BSC for cell A and not created in the OMC-R for frequency YYY".
Preventive actions : Not Applicable
Corrective actions: Reselection from cell A to cell B must be recreated
manually again from OMC-R.

Workaround

Impacts

Unusable
Usable with WA
Usable with limitation



Pure reselections are lost in OMC-R RNIM database if the BCCH frequency
of the target cell is changed.
Note that this occurs ONLY in case of PURE reselection links. This is a pure
local OMC-R problem without impact on the telecom behavior of the BSS.

Occurrence

Very Sporadic
Sporadic
Systematic



It may happen only when an old DLS is restored which leads to a BCCH
ARFCN mismatch between OMC-R and BSC and an upload radio is
performed and is therefore a very seldom case.

Existed before
current delivery?

Likely
Yes
No



In B7 problem is less frequently encountered compared to B6.2 due to other
bug fixes

FR

3BKA20FBR102456
3BKA20FBR100349

B7
B6.2

Sub-System
Planned Delivery
Keywords

OMC-R
No solution planned
Logical configuration

Severity

ED

2.1.8

TC software upgrade

2.1.9

MFS O&M

01

Released

11/25/2009

G2

BSS RESTRICTIONS LIST


BSSSAX01C Ed07 QD5
RELEASE B10
3BK 13016 1261 TQZZA
79/103

ED

01

Released

11/25/2009

BSS RESTRICTIONS LIST


BSSSAX01C Ed07 QD5
RELEASE B10
3BK 13016 1261 TQZZA

80/103

All rights reserved. Passing on and copying of this


document, use and communication of its contents not
permitted without written authorization from Alcatel-Lucent

All rights reserved. Passing on and copying of this


document, use and communication of its contents not
permitted without written authorization from Alcatel-Lucent

2.2 BSS FAULT MANAGEMENT


2.2.1

GSM Fault management

DTC faulty when lock/unlock is done on several DTCs

RESTRICTION

When applying a lock/unlock on 4 DTCs, 1 of them (never the same) is faulty at the end.
No operation can be done on this DTC. 4 or 5 minutes are needed to note that the barred circle
disappears. Then, applying a lock/unlock on the faulty DTC allows to go up afterwards
Preventive actions: Space out the lock/unlock on the 4 DTCs
Corrective actions: Lock/unlock DTC when the barred circle disappears

Workaround

Unusable
Usable with WA


No possible operation on the faulty DTC

Usable with limitation




Existed before
Current delivery?

Very Sporadic

Likely


Systematic

No


FR

3BKA20FBR169959

Sub-System
Planned Delivery
Keywords

BSC Legacy
Severity
No solution planned
BSS Fault management

Impacts
Occurrence

Sporadic

Yes

G2

Wrong alarm reported when Abis is cut in downlink between BSC and BTS

RESTRICTION

When an Abis link is cut on the downlink direction between a BSC Evolution and a BTS, the alarm
reported by the system is an AIS instead of a RAI.
There is no further impact than the wrong alarm type.
Note that the same misbehavior is observed with a BSC G2.
Preventive actions : Not applicable
Workaround
Corrective actions : None.
Unusable
Usable with WA
Usable with limitation



Incorrect alarm reported in case of transmission problems.

Impacts
Occurrence
Existed before
Current delivery?

Very Sporadic

Likely


FR

3BKA20FBR186110

Sub-System
Planned Delivery
Keywords

BSC
Severity
No solution planned
BSS Fault Management

ED

01

Sporadic

Yes

Released

11/25/2009

Systematic

No

G2

BSS RESTRICTIONS LIST


BSSSAX01C Ed07 QD5
RELEASE B10
3BK 13016 1261 TQZZA
81/103

All rights reserved. Passing on and copying of this


document, use and communication of its contents not
permitted without written authorization from Alcatel-Lucent

 A Trunks SBL's displayed IT when associated A_PCM_TP detect AIS

RESTRICTION

Due to alarm detection mechanism in the MT120 board, if there is no connection on some A interfaces,
the corresponding A Trunk SBL remains with IT status, but the associated A_PCM_TP detects LIS
(Loss of Incoming Signal). The supervision of all transmission alarms on Atermux must be done with
Ater window at OMC-R level
Preventive actions : Not Applicable
Corrective actions: Check the status of associated A_PCM_TP's in BSSUSM.
Check the alarms in A/Ater window (which gives A_PCM_TP) instead of the
Circuit Group Synthesis (which gives ATR status).

Workaround

Impacts

Unusable
Usable with WA
Usable with limitation



ATR specific alarms are not shown in BSSUSM - Ater supervision window.

Occurrence

Very Sporadic
Sporadic
Systematic



Whenever at least one of the A interfaces connected to MT120 board is cut.

Existed before
Current delivery?

Likely


Yes

CR

3BKA20CBR081009

Sub-System
Planned Delivery
Keywords

TC
Severity
No solution planned
TC G2.5/ BSS Fault management

No

G1

After unplug/ plug an ATBX board, a lock / unlock ATBX is required from
OMC-R to ensure availability of all resources

RESTRICTION

When an ATBX board is unplugged and plugged back (for instance in order to upgrade the ATBX
firmware) it may happen that some CIC remain BLOCKED after the ATBX has been plugged back.
Preventive actions: Not Applicable.
Corrective actions: Perform an ATBX lock / unlock from OMC-R BSSUSM to
unblock the CIC's.

Workaround
Impacts

Unusable
Usable with WA
Usable with limitation



Mismatching between BSC and TC. Increase of calls drop rate because the BSC
will allocate channels considered as available internally but blocked at TC level.

Occurrence

Very Sporadic
Sporadic


More probably after ATBX and DT16 power off/on.

Existed before
current delivery?

Likely


Yes

FR

3BKA20FBR082147
3BKA20FBR082085

B7
B6.2

Sub-System
Planned Delivery

BSC Legacy
No solution planned

Severity

ED

01

Systematic


Released

11/25/2009

No


G2

BSS RESTRICTIONS LIST


BSSSAX01C Ed07 QD5
RELEASE B10
3BK 13016 1261 TQZZA
82/103

BSS fault management - alarms handling

All rights reserved. Passing on and copying of this


document, use and communication of its contents not
permitted without written authorization from Alcatel-Lucent

Keywords

Access failed alarm for SYS-CPR cleared after BSC power off / on

RESTRICTION

If a BSC power up is performed on a BSC running in Simplex because the second system CPRA is in
fault (i.e. there is an active alarm "access fail" reported on this CPRA), then the alarm will not be
visible anymore at the OMC-R after the BSC power up. In the equipment view the impacted CPRA will
be marked as FAILED but will remain green. The associated disc and X25 link (in the functional view)
are also indicated as failed. In this case if a restart is attempted on this CPRA, the restart will fail
(normal because the CPRA is not running) and the alarm will appear again at the OMC-R.
Preventive actions: All BSC boards must be plugged if power off/on is
performed.
Corrective actions :
1. Perform a BSC alarm/state audit from OMC-R -> the alarm will be displayed
again in ASUSM.
2. Restart from BSSUSM the faulty CPR -> alarm is re-sent to ASUSM

Workaround

Impacts

Unusable
Usable with WA


One alarm is cleared at OMC-R level.

Occurrence

Very Sporadic
Sporadic
Systematic



It happens only in very special situations when a 2nd SYS-CPR is fault.

Existed before
current delivery?

Likely


Usable with limitation




Yes

FR

3BKA20FBR099492
3BKA20FBR099212

Sub-System
Planned Delivery
Keywords

BSC Legacy
Severity
No solution planned
BSS fault management - alarms handling

No


B7
B6.2
G2

 No alarm for both active/stand-by TPs, in case of drivers-failure problem

RESTRICTION

One BSC Evolution was detected with the N7 broken and with telecom outage. The TP1 board was
having one blue led, so the board was replaced, then a TP takeover (TP2->TP1) was triggered but
even if transmission was OK, the telecom was still down. After the TP2 board was replaced also, and
BSC was restarted the telecom was OK. Both TPs were having driver failures problems, but there was
no alarm for this.
Preventive actions: none
Corrective actions: none
Unusable
Usable with WA


N7 and traffic is lost until TP is replaced

Workaround
Impacts

Occurrence
Existed before
Current delivery?

ED

01

Very Sporadic

Likely


Sporadic

Yes


Released

11/25/2009

Usable with limitation



Systematic

No

BSS RESTRICTIONS LIST


BSSSAX01C Ed07 QD5
RELEASE B10
3BK 13016 1261 TQZZA
83/103

All rights reserved. Passing on and copying of this


document, use and communication of its contents not
permitted without written authorization from Alcatel-Lucent

FR

3BKA20FBR266341
3BKA20CBR267797

Sub-System
Planned Delivery
Keywords

BSC Evolution
Severity
Under study in B11
BSS fault management

2.2.2

B10
B11
G1

GPRS/EDGE fault management

Unexpected alarms No Q1 connection reported from TC when performing


RESTRICTION
a MUX switchover
When performing a MUX switchover on a MFS Evolution, it may happen that one alarm No Q1
connection is reported for some objects of the class TCSM-ADAPT. The alarm is cleared
autonomously after 20 seconds. There is no further impact.
Preventive actions : None
Workaround
Corrective actions : Not applicable
Unusable
Usable with WA


Unexpected alarms reported to the operator

Usable with limitation

Very Sporadic

Likely


Sporadic

Yes

Systematic

No


FR

3BKA20FBR185907
3BKA20FBR188461

B8
B9

Sub-System
Planned Delivery
Keywords

MFS Evolution
Severity
No solution planned
EDGE/GPRS Fault Management

Impacts
Occurrence
Existed before
Current delivery?

G3

 No alarm reporting for the JAXPC board of the MFS Evolution

RESTRICTION

The JAXPC board alarm reporting is not supported starting from B9


Preventive actions:
Check the board LEDs
Corrective actions:
Check the board LEDs

Workaround

Unusable
Usable with WA
Usable with limitation



JAXPC board fault detection has to be done locally based on LEDs


observation
If ever a JAXPC board is faulty, it will block a correct MFS Evolution Power
on. It has then to be checked visually before to Power Off an MFS Evolution.

Impacts

Occurrence

ED

01

Very Sporadic


Sporadic


Released

11/25/2009

Systematic

BSS RESTRICTIONS LIST


BSSSAX01C Ed07 QD5
RELEASE B10
3BK 13016 1261 TQZZA
84/103

All rights reserved. Passing on and copying of this


document, use and communication of its contents not
permitted without written authorization from Alcatel-Lucent

Existed before
Current delivery?
FR

Sub-System
Planned Delivery
Keywords

Likely

3BKA20FBR215008
3BKA20FBR215011
3BKA20FBR215827

Yes

B9
B9
B10

No


MFS Evolution
Severity
No solution planned
BSS Fault management

G2

During OMCP Replacement, the OMCP is wrongly powered off

RESTRICTION

While doing OMCP HOT INSTALL, the installed OMCP is wrongly powered off if the initialization of the
board takes more than 15 minutes
Preventive actions:
None.
Corrective actions:
Unlock / initialize the OMCP from OMC-R or BSC-TE.

Workaround

Impacts

Unusable
Usable with WA
Usable with limitation



The OMCP board is switched off without any telecom disturbances.

Occurrence

Very Sporadic

Likely


Sporadic

Yes

FR

3BKA20FBR216549
3BKA20FBR218820

B9
B10

Sub-System
Planned Delivery
Keywords

BSC Evolution
Severity
No solution planned
GPRS/EDGE Fault Management

Existed before
Current delivery?

ED

01

Released

11/25/2009

Systematic

No


G2

BSS RESTRICTIONS LIST


BSSSAX01C Ed07 QD5
RELEASE B10
3BK 13016 1261 TQZZA
85/103

All rights reserved. Passing on and copying of this


document, use and communication of its contents not
permitted without written authorization from Alcatel-Lucent

2.3 BSS O&M PERFORMANCE MANAGEMENT


2.3.1

GSM Performance Management

Fake counters after OMC-BSC communication problems

RESTRICTION

This problem can be observed with G2 BSC. In case of any communication problem between the OMC
and the BSC and if the timedate_modify action is triggered by the OMC, this timedate_modify action is
buffered and resent when the OMC-BSC link is back (few minutes later). It leads to a wrong BSC time
adjustment.
This disturbs the computation of TCH occupancy duration counters (C380a & C380b), which are
calculated through a start/stop time mechanism.
Preventive actions:
Inside /Alcatel/omc3/bss/im/10/conf/actions.cfg, change the retransmission
allowed flag from 1 to 0.
Then timedate_modify message will not be resent.
Corrective actions:
Same a preventive action

Workaround

Impacts

Unusable
Usable with WA


Some counters give unrealistic values

Usable with limitation




Occurrence

Very Sporadic

Likely


Sporadic

Yes

Systematic

No


FR

3BKA45FBR238230
3BKA20FBR242962
3BKA20FBR252966

B9
B10
B11

Sub-System
Planned Delivery
Keywords

OMC-R
Severity
Under study for B11
Performance measurements

Existed before
Current delivery?

2.3.2

G1

GPRS Performance Management

 Very spoardic, the GPMRES files have all GP counters equal to 0

RESTRICTION

Very sporadic it was observed that in the GPMRES files received from MFS, the values are 0 for all
counters. It was seen from the GPMRES files that the issue is due to the fact that the cell blocks for
this BSC appears with a LAC/CI and BSC value equal to zero. When the problem is present, the GP
didnt create any cell counters, even if the cells are mapped on this BSC. It seems that from time to
time and for an unknown reason, the GP is not processing correctly the GP counters.
Preventive actions: none
Corrective actions: none
Unusable
Usable with WA


No GPRS statistics available for some periods

Workaround
Impacts

ED

01

Released

11/25/2009

Usable with limitation




BSS RESTRICTIONS LIST


BSSSAX01C Ed07 QD5
RELEASE B10
3BK 13016 1261 TQZZA
86/103

All rights reserved. Passing on and copying of this


document, use and communication of its contents not
permitted without written authorization from Alcatel-Lucent

Occurrence
Existed before
Current delivery?

Very Sporadic

Likely

FR

3BKA20FBR264021

Sub-System
Planned Delivery
Keywords

MFS-SW
Severity
No solution planned
GPRS Performance Management

2.3.3

Sporadic

Yes


Systematic

No

G1

Radio measurement Statistics (RMS)

Wrong RMS-results after second Start RMS Request (STARMREQ) message

RESTRICTION

After receiving a second STARMREQ message due to new EMO frequencies or new neighbor cell
information (SYS INFO 5x frequencies), the BTS stops the RMS vector collection.
RMS results (PM type 31) are not reliable if HO relations or Mafa frequencies are changed on cells on
which a RMS job is currently active.
RMS jobs that are started after previously mentioned configuration changes are not impacted. They
are producing correct results.
Problem is only occurring when operator is changing the conditions for a measurement while it is
ongoing.
Preventive actions:
Workaround
Advice 1: Do not change HO relations or MAFA frequencies on cells for
which a RMS job is ongoing.
Advice 2: Stop active RMS job before HO relations or MAFA frequencies
are changed on these cells.
Corrective actions: None
Impacts

Unusable
Usable with WA


Wrong reporting of RMS-values

Occurrence

Existed before
current delivery?

Very Sporadic


Sporadic


Systematic

Likely


Yes

No


FR

3BKA20FBR170928

Sub-System
Planned Delivery
Keywords

BTS
No solution planned
EME

Usable with limitation




Severity

G3

RMS counters are missing for a new added TRX until the RMS job is
restarted

RESTRICTION

When a new TRX is added in a cell, the BSC sends a START-RMS-REQUEST message to the TRE
that does not answer to this message as it did not receive yet the CONF-COMPLETE message from
the OMU meaning that the BTS is well configured. As a consequence, that leads to the missing of the
RMS counter for the new added TRX.
ED

01

Released

11/25/2009

BSS RESTRICTIONS LIST


BSSSAX01C Ed07 QD5
RELEASE B10
3BK 13016 1261 TQZZA
87/103

All rights reserved. Passing on and copying of this


document, use and communication of its contents not
permitted without written authorization from Alcatel-Lucent

Workaround

Preventive actions: Not applicable


Corrective actions: Restart the RMS job

Impacts

Unusable
Usable with WA
Usable with limitation



In case of cell extension, RMS job results are not complete

Occurrence

Existed before
current delivery?

Very Sporadic


Sporadic


Systematic

Likely


Yes

No


FR

3BKA20FBR175986

Sub-System
Planned Delivery
Keywords

BSC
No solution planned
RMS

ED

2.3.4

IMSI Trace

2.3.5

Network performance analyzer

01

Severity

Released

11/25/2009

G2

BSS RESTRICTIONS LIST


BSSSAX01C Ed07 QD5
RELEASE B10
3BK 13016 1261 TQZZA
88/103

All rights reserved. Passing on and copying of this


document, use and communication of its contents not
permitted without written authorization from Alcatel-Lucent

2.4 GSM Telecom

2.4.1

GSM QoS

 Strident whistling noise after a while during a communication

RESTRICTION

It was observed that in case AMR is enabled, and the BSC is connected to a G2 transcoder, during a
normal call connection, if one of the mobiles is a Nokia, the user that is not using a Nokia handset may
experience some disturbing whistling noises. This is generated by the DT16 board from TC G2.
Preventive actions: none
Corrective actions: none
Unusable
Usable with WA
Usable with limitation



Whistling noises are heard on non Nokia mobiles users, which is disturbing.

Workaround
Impacts

Occurrence
Existed before
Current delivery?

Very Sporadic

Likely


Sporadic

Yes


FR

3BKA20FBR264586

B10

Sub-System
Planned Delivery
Keywords

DT16 SW
No solution planned
GSM QoS

Severity

ED

2.4.2

Adaptative MultiRate Codec

2.4.3

SMSCB

01

Released

11/25/2009

Systematic

No

G1

BSS RESTRICTIONS LIST


BSSSAX01C Ed07 QD5
RELEASE B10
3BK 13016 1261 TQZZA
89/103

All rights reserved. Passing on and copying of this


document, use and communication of its contents not
permitted without written authorization from Alcatel-Lucent

2.5 GPRS/EDGE Telecom


 Loss of periodic MS flow control in case of cell reselection

RESTRICTION

When a lot of data are transferred, sometimes it may occur that a flow control MS message is sent with
leak rate set to 0 (MS bucket full). This means that, during this period, no more DL frames are sent by
the SGSN.
Very sporadically, the problem may occur, if the bucket MS becomes full in one cell at a given moment
(no more DL frames sent by SGSN), and if at this time the MS performs a cell reselection. When the
MS will be on the new cell the SGSN waits for the new flow control message for this MS, but this
message will arrive in average of 10 sec after the cell reselection is done.
The impact is that during this period, the SGSN will not send DL frames and the performances are
reduced for this period of time.
After this period, the traffic comes back to normal
Preventive actions: Not applicable.
Corrective actions : Not applicable

Workaround

Unusable
Usable with WA
Usable with limitation



Decrease of throughput for a short period of time, when performing cell


reselection

Impacts

Occurrence
Existed before
Current delivery?

Very Sporadic

Likely


Sporadic

Yes

FR

3BKA20FBR132353

B8

Sub-System
Planned Delivery
Keywords

MFS
No solution planned
GPRS Telecom

Severity

ED

01

Released

11/25/2009

Systematic

No

G1

BSS RESTRICTIONS LIST


BSSSAX01C Ed07 QD5
RELEASE B10
3BK 13016 1261 TQZZA
90/103

All rights reserved. Passing on and copying of this


document, use and communication of its contents not
permitted without written authorization from Alcatel-Lucent

2.6 A1353-OMC-R SYSTEM


2.6.1

OMC-R Man-machine interface

Customer Documentation can not be displayed in a PDF File at the


workstation using CITRIX Software Version 1.2.

RESTRICTION

An error-message "Could not allocate enough colors, using grey scale." appears when trying to display
the B9 Customer Documentation in Acrobat Reader.
Preventive actions: Using the appropriate CD-ROM, access to Customer
Documentation is possible either from Master / HMI or from any Personal
Computer
Corrective actions: Same as preventive action

Workaround

Unusable
Usable with WA


Acrobat-Reader window is black.

Usable with limitation




Existed before
Current delivery?

Very Sporadic

Likely


Sporadic

Yes


Systematic

No

FR

3BKA20FBR179034

B9

Sub-System
Planned Delivery
Keywords

OMC-R
No solution planned
OMC-R MMI

Severity

Impacts
Occurrence

2.6.2

OMC-R Configuration Modification

2.6.3

OMC-R Administration

G3

The control on OAD is not done in command mode for all commands
containing BSC

RESTRICTION

On the OMC, there are 3 BSS (BSSID 1, 2 and 3) but in the operator profile, only the BSC ID 1 and 2
are present.
In DCN and RNUSM , the BSC ID3 is not displayed as it is not present in the operator profile.
But using the command mode, it is still possible to launch a command for the BSSID3: For instance:
"omcdo -cmd 'BSC_display(3)'".
This behavior is valid for all commands containing BSC ID. So the control on OAD is not done in
command mode for all commands containing BSC.
Preventive actions: Not applicable
Corrective actions: None

Workaround
Impacts

Unusable
Usable with WA


No control on OAD for commands with BSCID

Occurrence

Very Sporadic


ED

01

Sporadic


Released

11/25/2009

Usable with limitation

Systematic

BSS RESTRICTIONS LIST


BSSSAX01C Ed07 QD5
RELEASE B10
3BK 13016 1261 TQZZA
91/103

All rights reserved. Passing on and copying of this


document, use and communication of its contents not
permitted without written authorization from Alcatel-Lucent

Existed before
Current delivery?

Likely

FR

3BKA20FBR172326

Sub-System
Planned Delivery
Keywords

OMC-R
No solution planned
OMC-R Administration

Yes


No


Severity

G3

2.6.4

OMC-R Software Management / Backup-Restore

2.6.5

OMC-R Alarm Management

2.6.6

OSI Q3 Interface to NMC

 Alarm alignment action from TTI NMC to OMC-R fails all the time

RESTRICTION

It was observed that the communication breakdown has happened at the Q3IM while sending the MAction response. The communication between Q3IM and CMIP has been broken while sending the
response. It seems that the break was due to high amount of data sent from Q3 as part of the M-Action
response.
The issue appears to be with the CMIP library shared memory.
The following error is seen when the communication is broken down, and is returned by the CMIP
library to the Q3IM.
2008/06/26 14:19:54:q3im:comm:(1):mp_action_rsp failed (
Communication-Error: Broken Session.
)
Preventive actions: none
Corrective actions: none
Unusable
Usable with WA
Usable with limitation



Communication problems between OMC and NMC

Workaround
Impacts

Occurrence

Very Sporadic

Likely

Sporadic

Yes


FR

3BKA20FBR273029
3BKA20FBR274175

B10
B11

Sub-System
Planned Delivery
Keywords

OMC-SW
Under study in B11
Q3 Interface to NMC

Severity

Existed before
Current delivery?

2.6.7

ED

01

Systematic

No


G1

Alarm Call Out Function

Released

11/25/2009

BSS RESTRICTIONS LIST


BSSSAX01C Ed07 QD5
RELEASE B10
3BK 13016 1261 TQZZA
92/103

ED

01

Released

11/25/2009

BSS RESTRICTIONS LIST


BSSSAX01C Ed07 QD5
RELEASE B10
3BK 13016 1261 TQZZA

93/103

All rights reserved. Passing on and copying of this


document, use and communication of its contents not
permitted without written authorization from Alcatel-Lucent

All rights reserved. Passing on and copying of this


document, use and communication of its contents not
permitted without written authorization from Alcatel-Lucent

2.7 STABILITY AND PERFORMANCE

2.7.1

Sub-system OMC-R

2.7.2

Sub-system BSC

DRFU restarts under load

RESTRICTION

During GSM load tests (TCH + SDCCH load) some cases of DRFU restarts are observed on MKII
DRFU and G2 DRFU. The occurrence is roughly once a day. FU restart with alarm number 10 and
alarm number 13 are observed.
Workaround

Preventive actions : Not applicable


Corrective actions : Not applicable

Impacts

Unusable
Usable with WA


Decrease of performances

Usable with limitation

Existed before
Current delivery?

Very Sporadic

Likely

Systematic

No


FR

3BKA20FBR132875

Sub-System
Planned Delivery
Keywords

BTS-SW
Severity
No solution planned
BSC Stability/ Performance Management

Occurrence

Sporadic

Yes


G2

Equipment failure rate increased after BSC restart

RESTRICTION

Sporadically, it has been observed in the field on the migrated BSCs, as a side effect of BSC restart
under load conditions, that the equipment failure rate increases on one DTC. Autonomously the DTC is
restarted. Once the DTC is restarted, the failure rate comes back to normal.
Workaround

Preventive actions : Not applicable


Corrective actions : Not applicable

Impacts

Unusable
Usable with WA
Usable with limitation



Slightly degradation of Quality of Service after BSC restart (about 15 min)

Occurrence
Existed before
Current delivery?

Very Sporadic

Likely


FR

3BKA20FBR134081

Sub-System
Planned Delivery
Keywords

BSC Legacy
Severity
No solution planned
Performance Management/ BSC stability

ED

01

Sporadic

Yes

Released

11/25/2009

Systematic

No

G2

BSS RESTRICTIONS LIST


BSSSAX01C Ed07 QD5
RELEASE B10
3BK 13016 1261 TQZZA
94/103

All rights reserved. Passing on and copying of this


document, use and communication of its contents not
permitted without written authorization from Alcatel-Lucent

 No JBXTP takeover done, leads to outage on BSC Evolution

RESTRICTION

On an BSC Evolution is was noted that a TPGSM became faulty by seing the blue led on, but there
was no alarm at OMC, and there was no takover performed on the stand-by TPGSM, resulting in loss
of traffic on that BSC. Trying to perform a reset from OMC, did not have the good results, only after
unplug/plug the board, the problem was solved.
Preventive actions: none
Corrective actions: plug/unplug the faulty JBXTP
Unusable
Usable with WA
Usable with limitation



Traffic lost on impacted BSC, until the JBXTP is unplugged/plugged.

Workaround
Impacts

Occurrence

Very Sporadic

Likely

Sporadic

Yes


FR

3BKA20FBR270721
3BKA20FBR274410

B10
B11

Sub-System
Planned Delivery
Keywords

BSC Evolution
Severity
Under study in B11
BSC Evolution Stability and Performance

Existed before
Current delivery?

2.7.2.1

Systematic

No


G1

BSC OMC-R link

2.7.3

Sub-system BTS

2.7.4

Sub-system MFS

In case of A9135 MFS configured in cascading GPU synchronization mode


with two telecom sub-racks, a switch-over of the synchronizing GPU may
lead to an auto reset of all the other GPUs

RESTRICTION

When a switch-over is performed on the synchronizing GPU, a reset is requested and can lead to
disable the synchronizing PCM link. Consequently, subsequent GPUs are no longer synchronized and
GSL state changes are detected on several BSS. A lot of GPUs are then reset due to these GSL state
changes.
Preventive actions: None
Corrective actions: None

Workaround
Impacts

Unusable
Usable with WA
Usable with limitation



Loss of all PS calls on the cells mapped onto the rebooted GPU

Occurrence
Existed before
Current delivery?

Very Sporadic

Likely


FR

3BKA20FBR186104

Sub-System

MFS Legacy

ED

01

Sporadic

Yes

Systematic

No


Severity

G2

Released

11/25/2009

BSS RESTRICTIONS LIST


BSSSAX01C Ed07 QD5
RELEASE B10
3BK 13016 1261 TQZZA
95/103

All rights reserved. Passing on and copying of this


document, use and communication of its contents not
permitted without written authorization from Alcatel-Lucent

Planned Delivery
Keywords

ED

01

No solution planned
MFS Stability

Released

11/25/2009

BSS RESTRICTIONS LIST


BSSSAX01C Ed07 QD5
RELEASE B10
3BK 13016 1261 TQZZA

96/103

All rights reserved. Passing on and copying of this


document, use and communication of its contents not
permitted without written authorization from Alcatel-Lucent

2.8 LOCAL TERMINALS

ED

01

Released

11/25/2009

BSS RESTRICTIONS LIST


BSSSAX01C Ed07 QD5
RELEASE B10
3BK 13016 1261 TQZZA

97/103

All rights reserved. Passing on and copying of this


document, use and communication of its contents not
permitted without written authorization from Alcatel-Lucent

2.9 ADMINISTRATION SERVICES

ED

01

Released

11/25/2009

BSS RESTRICTIONS LIST


BSSSAX01C Ed07 QD5
RELEASE B10
3BK 13016 1261 TQZZA

98/103

During the method execution, the problems described in the FRs can appear.
They are marked as follows:
- o Restrictions already included in the method
- x Restrictions impacting but not included in the methods

Note:

Method Title

ANV Number

A9130 BSC Evolution


Maintenance Handbook

3BK 21281 AAAA PCZZA

Reduce 9130 BSC


Evolution

3BK 17430 0684 RJZZA

BSS Configuration
Handbook

3BK21201AAAAPCZZA

Replace X BTS with Y


BTS, Free Abis Port
Replace X BTS with Y
BTS, Same Abis Port
Replace Non-Alcatel BTS
with Alcatel BTS
Reconfigure TRE/Sectors,
A9100 BTS
Merge 900 and 1800 Cells
into Multiband Cells on
A9100 BTS

3BK174300741RJZZA

3BK174300742RJZZA

3BK174300743RJZZA

3BK174300801RJZZA

3BK174300804RJZZA

Add BTS, New Cell(s)

3BK174300841RJZZA

Create Extended Cells

3BK174300845RJZZA

3BK174300922RJZZA

3BK174300923RJZZA

3BK174301171RJZZA

Reconfigure TRE/Sectors
on A9110 E-BTS
Extend/Replace an A9110
Micro-BTS with an A9110
E-BTS
Modify Logical Parameter
with OMC-R Using MLU
Add a New BSS on OMCR
Move BSS with/without
MFS between Servers of
the Same OMC-R
Move A9130 BSC
Evolution Without MFS,
Same MSC, Different
OMC-R
Move A9130 BSC
Evolution, Different MFS,
Same MSC, Different
OMC-R
Move A9130 BSC
Evolution, Different MFS,
Different MSC, Different
OMC-R

ED

A20/230654

All rights reserved. Passing on and copying of this


document, use and communication of its contents not
permitted without written authorization from Alcatel-Lucent

3 IMPACT ON METHODS

01

3BK174301151RJZZA
3BK174301231RJZZA

3BK174300425RJZZA

3BK174300426RJZZA

3BK174300943RJZZA

Released

11/25/2009

BSS RESTRICTIONS LIST


BSSSAX01C Ed07 QD5
RELEASE B10
3BK 13016 1261 TQZZA
99/103

Move A9120 BSC, Without


MFS, Same MSC,
Different OMC-R
Move A9120 BSC,
Different MFS, Same
MSC, Different OMC-R
Move A9135 MFS with
Associated BSS, Different
OMC-R
Move A9130 MFS
Evolution with Associated
BSS, Different OMC-R
Move A9120 BSC,
Different MFS, Different
MSC, Different OMC-R

ED

01

ANV Number

A20/230654

All rights reserved. Passing on and copying of this


document, use and communication of its contents not
permitted without written authorization from Alcatel-Lucent

Method Title

3BK 17430 0421 RJZZA

3BK 17430 0422 RJZZA

3BK 17430 0423 RJZZA

3BK 17430 0424 RJZZA

3BK 17430 0942 RJZZA

Released

11/25/2009

BSS RESTRICTIONS LIST


BSSSAX01C Ed07 QD5
RELEASE B10
3BK 13016 1261 TQZZA
100/103

All rights reserved. Passing on and copying of this


document, use and communication of its contents not
permitted without written authorization from Alcatel-Lucent

4 APPENDIX A: KEYWORDS
Here is the list of keywords used in this document and their meaning sorted alphabetically.
Administration Services
This keyword is used for all restrictions linked to Administration Services for
BSC or OMC
AMR
This keyword is used for all restrictions linked to Adaptive Multirate Codec
feature
Back-up / Restore
This keyword is used for all restrictions linked to Back-up / Restore operations
BCCH recovery
This keyword is used for all restrictions linked to BCCH recovery
BSC Stability
This keyword is used for all restrictions linked to stability of BSC
BSC/TC Extension
This keyword is used for all restrictions linked to BSC or TC extension from
BSC Terminal
BSC OMC-R link
This keyword is used for all restrictions linked to stability of BSC- OMC-R link
BSS Audits
BSS fault management
BSS logical configuration
BTS Stability
BTS M4M
Logical Configuration
Circuit_group_blocking
EDGE
EME
GPRS Hardware
Configuration
GPRS/EDGE Fault
Management
GPRS/EDGE Logical
Configuration
GPRS/EDGE Telecom
GPRS QoS
GSM QoS
IMSI Trace
Half rate (HR)
Full rate (FR)
Laser
LCS
Local Terminals
MAFA
MFS O&M

ED

01

This keyword is used for all restrictions linked to BSS Audits


This keyword is used for all restrictions related to fault management : alarm
handling, operator actions
This keyword is used for all restrictions related to logical configuration
modification on BSS (BSC/BSS parameters only)
This keyword is used for all restrictions linked to stability of BTS
This keyword is used for all restrictions specific to BTS M4M
This keyword is used for all restrictions related to logical configuration
modification on a GSM cell (adjacency, radio configuration, )
This keyword is linked to the feature circuit group blocking
This keyword is used for all restrictions linked to Enhanced Data rates for
GSM Evolution (HW, Logical, Telecom)
This keyword is used for all restrictions linked Counters on Electro-Magnetic
Emissions
This keyword is used for all restrictions related to GPRS Hardware
Configuration Management.
This keyword is used for all restrictions related to GPRS/EDGE Fault
management
This keyword is used for all restrictions related to GPRS/EDGE Logical
Configuration Management.
This keyword is used for all restrictions related to GPRS/EDGE Telecom
This keyword is used for all restrictions related to GPRS QoS
This keyword is used for all restrictions related to GSM QoS
This keyword is used for all restrictions linked to the feature IMSI Trace
This keyword is used for all restrictions linked half rate
This keyword is used for all restrictions linked full rate
This keyword is used for all restrictions linked to the feature LASER
This keyword is used for all restrictions linked to the feature LCS
This keyword is used for all restrictions linked to Local terminals BTS, BSC,
LMCT, IMT
This keyword is used for all restrictions linked to the feature Mobile Assisted
Frequency Allocation
This keyword is used for all restrictions linked MFS O&M functionalities (MFS

Released

11/25/2009

BSS RESTRICTIONS LIST


BSSSAX01C Ed07 QD5
RELEASE B10
3BK 13016 1261 TQZZA
101/103

MFS Stability
All rights reserved. Passing on and copying of this
document, use and communication of its contents not
permitted without written authorization from Alcatel-Lucent

MLU
Network modification BSS

Network modification BTS

OMCR Stability
Remote Inventory
TCU/RSL re-mapping
Static sub-multiplexing
TC supervision
Statistical sub-multiplexing
TFO
TC G2.5
USOD
VGCS

ED

01

Security, MFS Administration)


This keyword is used for all restrictions linked to stability of MFS
This keyword is used for all restrictions specific to Extensive Logical
Configuration update feature
This keyword is used for all restrictions linked to the following scenarios :
Create BSS
Delete BSS
Move BSS
Rename BSS
This keyword is used for all restrictions linked to the following scenarios :
add BTS
delete BTS
extend/reduce BTS (add/delete sector)
move BTS
Change BTS hardware configuration
This keyword is used for all restrictions linked to stability of OMCR
This keyword is used for all restrictions linked to remote inventory of network
elements
This keyword is used for all restrictions linked to TCU/RSL re-mapping feature
This keyword is used for all restrictions linked to static sub-multiplexing feature
This keyword is used for all restrictions linked to TCIF supervision
This keyword is used for all restrictions linked to statistical sub-multiplexing
feature
This keyword is used for all restrictions linked to Tandem free operation
feature
This keyword is used for all restrictions linked to the usage of a TC G2.5
This keyword is used for all restrictions linked to the feature Usage state on
demand
This keyword is used for all restrictions linked to the feature VGCS (Voice
Group Call Service)

Released

11/25/2009

BSS RESTRICTIONS LIST


BSSSAX01C Ed07 QD5
RELEASE B10
3BK 13016 1261 TQZZA
102/103

All rights reserved. Passing on and copying of this


document, use and communication of its contents not
permitted without written authorization from Alcatel-Lucent

5 APPENDIX B: ABBREVIATIONS
Here is the list of abbreviations used in this document and their meaning sorted alphabetically
BBH
BIUA
CS
CSn
DR
DTC
EDGE
EGPRS
ExTS
FHS
FR
GPM
GPRS
HP
HR
HSDS
HSN

Base-Band Hopping
Base Station Interface Unit, variant A
Circuit switched: circuit traffic
Coding Scheme for GPRS: n=1 to 4
Dual rate
Digital Trunk Controller
Enhanced Data rates for GSM evolution
Enhanced GPRS
Extra Abis Timeslots
Frequency Hopping Sequence which is constituted by the couple (MA, HSN)
Full rate
GPRS Preference Mark
General Packet Radio Service
High Power
Half rate
High Speed Data Service
Hopping Sequence Number wich identifies the hopping sequence. The OMC-R takes
as hypothesis that there is one HSN per FHS in a cell.
Mobile Allocation which defines a list of frequencies to be used in a hopping sequence
Multiple Control Block (Group of TRE's on a TCU grouped to multiplex RSL/OML)
Modulation and Coding Scheme for EGPRS: n=1 to 9
Multi-Function Server
Medium Power
Non Hopping/Radio Hopping
Operation and Maintenance
On Board Controller Interface
Operation and Maintenance Center
O&M link between the BSC and the OMU
O&M Unit of the BTS
Pulse Coded Modulation: 2 Mbit/s link divided into 32 TS's
Provisioning Radio Configuration
Packet Switched: data traffic
Radio Link Control
Radio Signaling Link
Radio timeslot
Traffic Channel
TRX Control Unit
TRX Preference Mark
Timeslot: 64 kbit/s on a PCM
Terminal SubUnit (a group of Control Elements sharing one pair of access switches in
BSC)

MA
MCB
MCSn
MFS
MP
NH/RH
O&M
OBCI
OMC-R
OML
OMU
PCM
PRC
PS
RLC
RSL
RTS
TCH
TCU
TPM
TS
TSU

END OF DOCUMENT

ED

01

Released

11/25/2009

BSS RESTRICTIONS LIST


BSSSAX01C Ed07 QD5
RELEASE B10
3BK 13016 1261 TQZZA
103/103