You are on page 1of 20

Nokia UltraSite EDGE Base Station

Open and Corrected Problems in


BTS SW CX5 CD2.0

DN0756836 Nokia Siemens Networks 1 (20)


Issue 1-0
Open and Corrected Problems in BTS SW CX5 CD2.0

The information in this document is subject to change without notice and describes only the
product defined in the introduction of this documentation. This documentation is intended for
the use of Nokia Siemens Networks customers only for the purposes of the agreement under
which the document is submitted, and no part of it may be used, reproduced, modified or
transmitted in any form or means without the prior written permission of Nokia Siemens
Networks. The documentation has been prepared to be used by professional and properly
trained personnel, and the customer assumes full responsibility when using it. Nokia Siemens
Networks welcomes customer comments as part of the process of continuous development
and improvement of the documentation.
The information or statements given in this documentation concerning the suitability, capacity,
or performance of the mentioned hardware or software products are given as is and all
liability arising in connection with such hardware or software products shall be defined
conclusively and finally in a separate agreement between Nokia Siemens Networks and the
customer. However, Nokia Siemens Networks has made all reasonable efforts to ensure that
the instructions contained in the document are adequate and free of material errors and
omissions. Nokia Siemens Networks will, if deemed necessary by Nokia Siemens Networks,
explain issues which may not be covered by the document.
Nokia Siemens Networks will correct errors in this documentation as soon as possible. IN NO
EVENT WILL NOKIA SIEMENS NETWORKS BE LIABLE FOR ERRORS IN THIS
DOCUMENTATION OR FOR ANY DAMAGES, INCLUDING BUT NOT LIMITED TO
SPECIAL, DIRECT, INDIRECT, INCIDENTAL OR CONSEQUENTIAL OR ANY LOSSES,
SUCH AS BUT NOT LIMITED TO LOSS OF PROFIT, REVENUE, BUSINESS
INTERRUPTION, BUSINESS OPPORTUNITY OR DATA,THAT MAY ARISE FROM THE
USE OF THIS DOCUMENT OR THE INFORMATION IN IT.
This documentation and the product it describes are considered protected by copyrights and
other intellectual property rights according to the applicable laws.
The wave logo is a trademark of Nokia Siemens Networks Oy. Nokia is a registered trademark
of Nokia Corporation. Siemens is a registered trademark of Siemens AG.
Other product names mentioned in this document may be trademarks of their respective
owners, and they are mentioned for identification purposes only.
Copyright Nokia Siemens Networks 2007. All rights reserved.

2 (20) Nokia Siemens Networks DN0756836


Issue 1-0
Contents

Contents

1 About this document .............................................................................5


1.1 Problem description..................................................................................5

2 Corrected problems in CX5 CD2.0........................................................7


2.1 Locally blocked BTS can still handle traffic ..............................................7
2.2 Problem with WCxT TX cabling figure in HW Configurator ......................8
2.3 Calls are dropped in the 2nd sector when the 1st or 3rd sector is
restarted or unblocked locally in IDD/4UD configuration..........................8
2.4 Fault in a sector during RTC Configure with wrong frequencies
after a sector block from BTS Manager....................................................9
2.5 BTS SW file corruption not detected ......................................................10
2.6 Disabling STIRC from a non-EDGE sector where one TRX is
set to preferred BCCH............................................................................10
2.7 Cancellation of the 3rd sector alarm 7606 TRX FAULTY
Antenna Connection Faulty causes restart of other sectors in
IDD configuration ...................................................................................11
2.8 BTS Manager displays an error message when RSSI
comparison values are fetched ..............................................................12

3 Corrected problems in customer specific CX5 CD1.1/CD2.0 ...........13


3.1 GSM TRX TSxA with BB2F does not carry traffic in BB hopping...........13
3.2 Alarm 7606 TRX FAULTY FBUS HW Failure with BB hopping............14

4 Open problems in CX5 CD2.0..............................................................15


4.1 Open problems targeted for CX5 CD3.0 ................................................15
4.1.1 MNTB cannot be added to UltraSite HW Configuration using
HW Configurator 5 CD2.0 ......................................................................15
4.1.2 Codec first and codec last values are wrongly reported in some
scenarios with BB2A ..............................................................................16
4.1.3 Mini UltraSite view changes to UltraSite view after Abis is
disabled from BTS Manager...................................................................16
4.1.4 Long delay in reconfiguration if RTC and DVxx units are
configured in the same sector ................................................................17
4.1.5 EAC generated MAINS alarm is not sent from master to slave
cabinets ..................................................................................................17
4.1.6 Alarm 8048 LOSS OF INCOMING SIGNAL is lost during a BCF
reset .......................................................................................................18
4.1.7 Enabling/disabling STIRC for sector with non-EDGE capable
preferred BCCH TRX .............................................................................19
4.1.8 OMU reset during intelligent shutdown ..................................................19

DN0756836 Nokia Siemens Networks 3 (20)


Issue 1-0
Open and Corrected Problems in BTS SW CX5 CD2.0

4 (20) Nokia Siemens Networks DN0756836


Issue 1-0
About this document

1 About this document


This document describes the problem corrections included in the Nokia
UltraSite EDGE BTS SW CX5 CD2.0. It also lists the open, customer-
visible problems in this SW which were known at the time of the BTS
SW release, that is, the 31st of October, 2007.

The corrections included in the previous UltraSite EDGE BTS SW


releases as well as an updated list of open problems can be found from
the Generic Failure Report document. An updated GFR is published
every couple of months in NOLS/Documentation/Product: Nokia
UltraSite EDGE Base Station, Document type: Generic Failure Reports.

1.1 Problem description


In the problem report cases below, the following information is displayed:

Heading row
The title of the problem.

Problem report
The reference number of the problem. It is provided to help to identify
any particular problem.

Reported in
The BTS SW version in which the problem has been reported.

Correction target
The latest estimation of the BTS SW release in which the problem will be
corrected.

DN0756836 Nokia Siemens Networks 5 (20)


Issue 1-0
Open and Corrected Problems in BTS SW CX5 CD2.0

Note
The correction may be delivered with or it might also require new
Element Manager SW. Element managers are delivered with the
SiteWizard.

If the field is marked with TBD, the schedule for correcting the problem
is still open.

Problem description
A brief description of the problem and its symptoms, including more
detailed information if the problem is related to certain configurations,
HW types, or features.

Workaround
Brief instructions on how to avoid or clear the problem.

Note
The workaround must be used before the normal troubleshooting
instructions are applied.

System impact
The impact of the problem on end-users and BTS maintenance services.

6 (20) Nokia Siemens Networks DN0756836


Issue 1-0
Corrected problems in CX5 CD2.0

2 Corrected problems in CX5 CD2.0


This section lists all the problems corrected in CX5 CD2.0.

2.1 Locally blocked BTS can still handle traffic


Problem report: 1-262455362
Reported in: CX4.1 CD3.0
Correction target: CX5 CD2.0
Description:
The problem occurs only when all TRXs under the BTS are first locally
blocked and then the BTS is locally blocked. Finally all the TRXs are
locally unblocked.
The BTS starts to transmit and BTS Manager shows green light on
BCCH TRX in the equipment view. Telecom working is displayed at the
bottom of the window. The sector is still in a blocked state in BTS
manager and in the BSC, but calls are possible.
Workaround:
BCCH transmission is stopped correctly, when the BTS is locally
blocked first, or BCCH TRX/BTS is locked from the BSC.
System impact:
The BTS starts to transmit even when it is in a locally blocked state.
Calls can be made when the BTS is in the BL-BTS state at the BSC.

DN0756836 Nokia Siemens Networks 7 (20)


Issue 1-0
Open and Corrected Problems in BTS SW CX5 CD2.0

2.2 Problem with WCxT TX cabling figure in HW


Configurator
Problem report: 1-256542665
Reported in: Hardware Configurator 5
Correction target: Hardware Configurator 5 CD2.0,
SiteWizard 5 CD2.0
Description:
When setting up TX cabling from TRXs to DVxx via the WCxT, a
problem is seen in the figure of Configuration Candidate in Hardware
Configurator (HWC) when connecting up TRX4, TRX8, or TRX12. The
HWC displays the TX cabling in an incorrect position between WCxT
and DVxx units. The problem is only in the figure and the correct cabling
path is listed in the TX cabling window. Thus the problem does not affect
the performance of the BTS.
Workaround:
-
System impact:
This problem does not affect the performance of the BTS.

2.3 Calls are dropped in the 2nd sector when the 1st or
3rd sector is restarted or unblocked locally in
IDD/4UD configuration
Problem report: 4026C02, 5126C01
Reported in: CX4.1 CD3.0
Correction target: CX5 CD2.0
Description:
A local BTS reset is done to the third sector in 2+2+2 IDD/4UD
configuration. The transmission of the second sector stops for a moment
and then comes back to normal. The problem is also observed when the
local block/unblock command is given to the third sector from BTS
Manager.
When a local block/unblock is done in the first sector, all calls are
dropped in the second sector. When BB2F is used for Aux TRXs of the
second sector, alarms 7607 TRX OPERATION DEGRADED: FBUS HW

8 (20) Nokia Siemens Networks DN0756836


Issue 1-0
Corrected problems in CX5 CD2.0

failure and 7604 BTS OPERATION DEGRADED: FBUS HW failure are


seen in the second sector.
Workaround:
Use BTS lock/unlock from the BSC instead of a local restart in IDD
configuration.
System impact:
Calls are dropped from the second sector when the first or third sector is
locally unblocked or restarted.

2.4 Fault in a sector during RTC Configure with


wrong frequencies after a sector block from BTS
Manager
Problem report: 4636C01, 4953C01
Reported in: CX4.1
Correction target: CX5 CD2.0
Description:
A sector with RTC is blocked locally with BTS Manager. The RTC
Configure option is selected from BTS Manager with different
frequencies than those given by the BSC for each TRX. The sector is
unblocked with BTS Manager.
Two possible scenarios have been observed after the BTS unblock:
x The TRXs are tuned to the frequencies which were given
manually. BCCH transmission is started with the wrong frequency
and the sector is in the working state (WO) at the BSC, as well as
at BTS Manager, with no alarms.
x The sector stays in the BL-RST state with all the TRXs in the
configuring state.
While testing the correction for this problem, a new issue was found:
x In two sector BB hopping configuration, the first sector is blocked
with BTS Manager. The RTC is configured using the RTC
Configure command with BTS Manager. Immediately after the
RTC Configure command is sent to the RTC, the other sector goes
down with alarm 7606 TRX FAULTY: There is disturbance in the
serial DL bus or bus is broken for all TRXs in the sector, which
then correlates with alarm 7603 BTS FAULTY. TRXs in the first
sector stay in the configuring state.

DN0756836 Nokia Siemens Networks 9 (20)


Issue 1-0
Open and Corrected Problems in BTS SW CX5 CD2.0

When the second sector is unblocked with BTS Manager, alarm


7208 LOCAL BLOCK is cancelled. Both sectors take multiple
resets and the second sector stays in the BL-BTS state at BSC
even though alarm 7208 is cancelled.
Workaround:
Do not unblock the sector with wrong RTC frequencies. BCF lock/unlock
will clear the situation.
System impact:
Calls are not possible for the sector with wrong frequencies.

2.5 BTS SW file corruption not detected


Problem report: 31468ES08P
Reported in: CX4.0
Correction target: CX5 CD2.0
Description:
When new BTS software is downloaded to the base station, it might
happen that the CRC checking included in the application files does not
detect corruption in the files. In this case the SW activation may result in
malfunction of the BTS.
This is extremely rare (in fact seen on one occasion only).
The CRC checking is further enhanced to include a more secure CRC
calculation.
Workaround:
Run a binary comparison between the BTS SW files downloaded from
NOLS and the files stored on the BSC disk before downloading the BTS
SW to the base stations.
System impact:
In extremely rare occasions, it may happen that corruption in the BTS
SW is not detected, resulting in malfunction of the base station.

2.6 Disabling STIRC from a non-EDGE sector where


one TRX is set to preferred BCCH
Problem report: 3196C01

10 (20) Nokia Siemens Networks DN0756836


Issue 1-0
Corrected problems in CX5 CD2.0

Reported in: CX5


Correction target: CX5 CD2.0
Description:
The Space-Time Interference Rejection Combining (STIRC) feature is
enabled for the non-EDGE sector where BB2A boards are used. Alarm
7606 TRX FAULTY Non EDGE TRX device type used accidentally in
Edge Capable Mode is reported for all TRXs, and alarm 7603 BTS
FAULTY Non EDGE TRX device type used accidentally in Edge
Capable Mode is reported. The STIRC feature is disabled. Alarm 7603
for BTS and alarm 7606 for non-BCCH TRXs are cancelled.
Alarm 7606 for the preferred BCCH TRX is not cancelled from the BSC
or BTS Manager. The sector moves into working state (WO) and calls
are possible. The LED colour of BB2A for BCCH TRX is red.
Workaround:
Restart the sector.
System impact:
Alarm 7606 TRX FAULTY EDGE TRX device type used accidentally in
Edge Capable Mode is not cancelled correctly. BB2A LED is incorrectly
red, which indicates a failure.

2.7 Cancellation of the 3rd sector alarm 7606 TRX


FAULTY Antenna Connection Faulty causes
restart of other sectors in IDD configuration
Problem report: 3820C01
Reported in: CX5
Correction target: CX5 CD2.0
Description:
A site is configured as 2+2+2 IDD. Sector 3 has an active TSxx unit
alarm 7606 TRX FAULTY Antenna Connection Faulty for the main TCH
TRX.
The alarm is cancelled by locking/unlocking the sector from the BSC.
After the unlock, other sectors under the same BCF will restart and all
calls are dropped.
A similar problem occurs if RF hopping is applied to the third sector.
This problem is seen only in the third sector and in an IDD configuration.
The problem does not occur if the sector is restarted with BTS Manager.

DN0756836 Nokia Siemens Networks 11 (20)


Issue 1-0
Open and Corrected Problems in BTS SW CX5 CD2.0

Workaround:
After a failed unit has been changed, restart the third sector with a local
or remote BTS Manager.
System impact:
All calls are dropped when the alarm is cancelled.

2.8 BTS Manager displays an error message when


RSSI comparison values are fetched
Problem report: 3943C01
Reported in: CX5 and SiteWizard 5 (BTS Manager 5)
Correction target: CX5 CD2.0 and SiteWizard 5 CD2.0
(BTS Manager 5 CD2.0)
Description:
The RX Difference Limit (RXDL) parameter value is set to 64 at the BSC
(64dB indicates that no RSSI measurement is done). The site is
restarted. After the site is up and running, the RSSI comparison values
are fetched using BTS Manager.
BTS Manager prompts error message Requesting RSSI comparison
values failed. Cannot get response from BTS SW three times for the
newest, reliable, and raw values respectively. Thereafter, the RSSI
window opens with message Failed to get response in all three sub-
windows.
The correct message should be Requesting RSSI comparison values
failed. Feature is not activated and it will be shown for the newest,
reliable, and raw values. After selecting OK in each of the conditions
stated above, the data comparison window will appear. RSSI Sections of
each RSSI value will be opened with the message Failed to get X RSSI
values, where X = newest/reliable/raw.
Workaround:
The RSSI value fetching is working correctly when the RXDL value is not
64.
System impact:
A wrong error message is seen at BTS Manager.

12 (20) Nokia Siemens Networks DN0756836


Issue 1-0
Corrected problems in customer specific CX5 CD1.1/CD2.0

3 Corrected problems in customer


specific CX5 CD1.1/CD2.0
This section includes the problem corrections in customer specific CD
CX5 CD1.1.
The corrections in CX5 CD1.1 are merged into CX5 CD2.0.

3.1 GSM TRX TSxA with BB2F does not carry traffic
in BB hopping
Problem report: 1-264900231
Reported in: CX4.1 CD2.0
Correction target: CX5 CD1.1
Description:
When baseband hopping is in use, the GSM TRX units connected to
BB2F baseband units may not be able to carry any traffic.
The problem results in dropped calls during the SDCCH call setup.
Workaround:
If possible, switch off BB hopping in the affected sectors.
System impact:
A cell configured with GSM TRX units connected to EDGE capable
baseband units maybe unable to carry traffic in BB hopping.

DN0756836 Nokia Siemens Networks 13 (20)


Issue 1-0
Open and Corrected Problems in BTS SW CX5 CD2.0

3.2 Alarm 7606 TRX FAULTY FBUS HW Failure with


BB hopping
Problem report: 4307C02
Reported in: CX4.1 CD2.0
Correction target: CX5 CD1.1
Description:
7606 TRX FAULTY FBUS HW Failure alarms are still rarely reported
even when the correction delivered with CX4.1 CD2.0 is in use. The
alarms are seen only with BB hopping configurations. The previously
delivered correction in CX4.1 CD2.0 did not correct these cases as
during further investigation another root cause has been found which is
caused by an unexplained TRX restart in a BB hopping sector. The reset
was caused by a problem in internal message queue whose memory
allocation was exceeding the TRX OS limits.
Workaround:
BTS lock/unlock will clear the problem.
System impact:
Unwanted TRX alarms are seen with a BB hopping sector. Calls are
dropped when the problem occurs.

14 (20) Nokia Siemens Networks DN0756836


Issue 1-0
Open problems in CX5 CD2.0

4 Open problems in CX5 CD2.0

4.1 Open problems targeted for CX5 CD3.0


This section lists all the problems targeted for correction in CX5 CD3.0.

4.1.1 MNTB cannot be added to UltraSite HW Configuration using HW


Configurator 5 CD2.0

Problem report: 5286C02


Reported in: SiteWizard 5 CD2.0 (HW Configurator 5 CD2.0)
Correction target: SiteWizard 5 CD3.0 (HW Configurator 5 CD3.0)
Description:
MNTB unit (800 band MHA co-sited with WCDMA) is being configured
using HW Configurator 5 CD2.0.
When MNTB units are configured to the HWC file, it can be seen that the
units are correctly shown in the Cabinet Units view.
When the antenna settings are set in the Antenna Settings view, no
MHA is seen in the windows.
The problem means that MNTB unit configurations cannot be set and
sent to the BTS when configured with HW Configurator 5 CD2.0.
The problem is specific to 800 band only.
Workaround:
Use HW Configurator 5 CD1.0 to set up the MNTBs. Select high gain in
the Antenna Properties dialog box.
System impact:
It is not possible to set up the MNTB unit to UltraSite configuration using
HW Configurator 5 CD2.0.

DN0756836 Nokia Siemens Networks 15 (20)


Issue 1-0
Open and Corrected Problems in BTS SW CX5 CD2.0

4.1.2 Codec first and codec last values are wrongly reported in some
scenarios with BB2A

Problem report: 8704ES05X


Reported in: CX4.1
Correction target: CX5 CD3.0
Description:
GSM baseband unit BB2A is used.
During an AMR call setup or bad uplink RF interference conditions, AMR
UL CODEC FIRST and AMR UL CODEC LAST values always show 3
instead of the codec used and irrespective of the number of codecs
defined.
AMR UL CODEC FIRST indicates the used codec of the first block in the
multiframe.
AMR UL CODEC LAST indicates the used codec of the last block in the
multiframe.
AMR UL CODEC FIRST is used in DL FER calculation (BSC DL FER
estimation algorithm).
AMR UL CODEC LAST is used to map the uplink FER counts on BSC
according to the codec.

Workaround:
-
System impact:
When BB2A boards are used, the KPI statistics of the DL FER and Used
AMR Codec report marginally wrong values.

4.1.3 Mini UltraSite view changes to UltraSite view after Abis is disabled
from BTS Manager

Problem report: 5200C01


Reported in: CX5 CD1.0
Correction target: CX5 CD3.0
Description:
UltraSite EDGE Mini Outdoor site is in the supervisory state and BTS
Manager is connected to the BTS. BTS Manager shows UltraSite Mini
cabinet as expected.
If the Abis is disabled from BTS Manager, the site resets and the BTS

16 (20) Nokia Siemens Networks DN0756836


Issue 1-0
Open problems in CX5 CD2.0

Manager view is changed from Mini UltraSite to a standard UltraSite


cabinet view.
Workaround:
Enable the Abis with BTS Manager to get the view back to Mini
UltraSite.
System impact:
The fault has no effect on the operation of the BTS.

4.1.4 Long delay in reconfiguration if RTC and DVxx units are


configured in the same sector

Problem report: 1-275540244


Reported in: CX4.1
Correction target: CX5 CD3.0
Description:
A BTS is configured to have an RTC unit and a DVxx unit in the same
sector.
When BCCH is active in a TRX connected to the RTC unit, a failure
occurs in the RTC. Alarm 7606 TRX FAULTY is raised on each TRX
connected to the RTC.
The reconfiguration starts going through every TRX connected to the
RTC, but it will take approximately 5-10 minutes per TRX. It may take up
to one hour until the BCCH is reconfigured to a TRX connected to the
DVxx unit.
Workaround:
Lock/unlock the sector to speed up the reconfiguration.
System impact:
During the reconfiguration the sector is out of service.

4.1.5 EAC generated MAINS alarm is not sent from master to slave
cabinets

Problem report: 22280ES11P


Reported in: CX4.1
Correction target: CX5 CD3.0

DN0756836 Nokia Siemens Networks 17 (20)


Issue 1-0
Open and Corrected Problems in BTS SW CX5 CD2.0

Description:
Site Support System (SSS) supplies power to UltraSite master and slave
cabinets in a chained configuration.
The Mains Breakdown indication is sent to the UltraSite master cabinet
from the SSS using the External Input lines (EAC).
The Mains Breakdown indication is not delivered to UltraSite slave
cabinets.
The behaviour is correct if Site Support alarms are delivered to UltraSite
via Q1 instead of EAC.
Workaround:
-
System impact:
Intelligent shutdown does not work in the UltraSite Slave cabinets if EAC
lines are used to get a Mains Breakdown indication to the UltraSite
system.

4.1.6 Alarm 8048 LOSS OF INCOMING SIGNAL is lost during a BCF reset

Problem report: 33787ES08P


Reported in: CX4.1 CD4.0
Correction target: CX5 CD3.0
Description:
LMU is feeding clock signal to the BCF. The LMU is reset from LMU
Manager or following LMU SW activation. Alarm 8048 is raised.
If the BSS11073 Recovery for BSS and Site Synchronisation feature is
not in use, this will cause a BCF reset as well and during the BCF start-
up alarm 8048 is not cancelled.
The site will stay in UNSYNC mode and will never recover to LMU
SYNC.
Workaround:
Lock/unlock the BCF.
System impact:
No synchronisation to the BCF when alarm 8048 stays active.

18 (20) Nokia Siemens Networks DN0756836


Issue 1-0
Open problems in CX5 CD2.0

4.1.7 Enabling/disabling STIRC for sector with non-EDGE capable


preferred BCCH TRX

Problem report: 3182C02


Reported in: CX5
Correction target: CX5 CD3.0
Description:
A non-EDGE TRX with BB2A is the preferred BCCH TRX (PREF=P) and
the Space-Time Interference Rejection Combining (STIRC) feature is
enabled for the sector. A TRX alarm 7606 TRX FAULTY Non EDGE
TRX device type used accidentally in Edge Capable Mode is raised, and
the TRX state is disabled (BL-TRX). The BCCH is reconfigured to an
EDGE TRX. This is expected behaviour as STIRC is not supporting non-
EDGE TRx with BB2A.
When STIRC is disabled, alarm 7606 is cancelled but the TRX stays in
BL-RSL state with alarm 7705 LAPD FAILURE. When the TRX is reset,
it will clear the alarm.
When BCCH reconfiguration occurs for the preferred TRX, the EDGE
TRXs in the sector may restart and stay in BL-SYS state with alarm
Failure in sending system info. The EDGE TRXs need to be restarted to
clear the fault.
Workaround:
Do not activate the STIRC feature in a sector with BB2A units. If STIRC
needs to be enabled, change the HW to EDGE capable units and restart
the sector/TRX. If it is accidentally enabled, disable STIRC and restart
the TRXs or the sector.
System impact:
Non-EDGE capable units are out of service until the STIRC feature is
disabled and the unit/sector is restarted.

4.1.8 OMU reset during intelligent shutdown

Problem report: 3252C01


Reported in: CX5.0
Correction target: CX5 CD3.0
Description:
In a multi-BCF configuration the master BCF OMU is reset during
intelligent shutdown. This will cause differences in alarm and shutdown
states between the master and slave BCFs on both BTS and BSC level.

DN0756836 Nokia Siemens Networks 19 (20)


Issue 1-0
Open and Corrected Problems in BTS SW CX5 CD2.0

This will lead to a situation where the intelligent shutdown does not work
properly and the capacity of Site Support System batteries is
unnecessarily used.
As there is no real need for OMU reset during intelligent shutdown and
the problem is more in system design, Nokia has decided not to support
the OMU reset during intelligent shutdown.
Workaround:
Use BCF lock/unlock or site restart instead of OMU reset during
intelligent shutdown.
System impact:
-

20 (20) Nokia Siemens Networks DN0756836


Issue 1-0