FL16A 6.0 Installation Instruction.pdf

Installation Instruction

Product Family: Product: Release:

Base Stations Flexi Multiradio BTS LTE FL16A 6.0

Approval date:

26-Apr-2017

FL16A 6.0 Installation Instruction - Page 1/23 Version 1.0 Confidential

© Nokia 2017

Table of Contents 1. 2.

Purpose ................................................................. ................................................................................................................................... .................................................................................. ................5 Overview .............................................................. .............................................................................................................................. ................................................................................... ...................5 2.1 Other Relevant Installation Instructions ................................................................... .............................................................................................. ........................... 5 3. Preparations ......................................................... ......................................................................................................................... ................................................................................... ...................5 4. Making a safe copy cop y of the package ........................................................................................................ 5 5. SW downloading instruction ....................................................... .................................................................................................................... .............................................................5 6. Special conditions .......................................................... ............................................................................................................................. ......................................................................... ...... 6 6.1 FHCA A.103 operating conditions ...................................................................................................... ...................................................................................................... 6 6.2 FRGP Power Setting ............................................................ .......................................................................................................................... ..............................................................6 7. RF-Sharing ........................................................... ........................................................................................................................... ................................................................................... ...................6 7.1.1 LTE-GSM RF Sharing (EX) ................................................................... ........................................................................................................ ..................................... 6 7.1.2 LTE-GSM RF Sharing (GF) ............................................................... ....................................................................................................... ........................................ 7 7.1.3 WCDMA-LTE RF Sharing .......................................................................................................... .......................................................................................................... 7 8. Compatibility matrix ........................................................................................................................... ................................................................................................................................. ...... 8 8.1 OAM compatibility ............................................................................................................................... ...............................................................................................................................8 8.2 Inter eNB Carrier Aggregation features f eatures compatibility ......................................................................... ......................................................................... 9 9. Data migration ................................................................................................................................... ....................................................................................................................................... .... 10 10. Release delivery upgrade instruction .............................................................. .................................................................................................... ......................................10 10.1 First installation and commissioning ........................................................... ................................................................................................. ......................................10 10.2 Project upgrade ......................................................... ............................................................................................................................ ....................................................................... .... 10 10.3 Supported update/upgrade paths ..................................................................................................... .....................................................................................................10 10.4 General installation hints ....................................................... .................................................................................................................. ...........................................................11 10.4.1 Cases when SW update is not allowed ................................................................................... 11 10.4.2 Carrier Aggregation scenarios - range of scellActivationLevel parameter adapted ................11 10.4.3 No Configurations Conf igurations during SW upgrade .................................................................................... ....................................................................................11 10.4.4 CM Upload must be executed after eNB upgrade in case Automatic Synchronization with NetAct is not enabled .............................................................................................. ............................................................................................................... ................. 11 10.4.5 Invalid EARFCN values in LNCEL/IRFIM/dlCarFrqEut (EUTRA frequency value) leads to cell setup failure (fault 6253) .......................................................................................................... .......................................................................................................... 12 11. CRAN ........................................................ ......................................................................................................................... ............................................................................................ ...........................12 11.1 Project upgrade to FL16A 6.0 ........................................................... ........................................................................................................... ................................................12 11.2 CRAN operator hints ............................................................. ......................................................................................................................... ............................................................13 11.2.1 ToP-frequency vs GPS/ToP-phase G PS/ToP-phase as synchronization source for master ............................. 13 11.2.2 SFP needed in all FBBC’s port 3 ....................................................... ............................................................................................. ...................................... 13 11.2.3 cranId value range ....................................................... ................................................................................................................... ............................................................13 12. General operator hints .......................................................................................................................... ..........................................................................................................................13 12.1 Ping RTT requirement ...................................................................................................................... ...................................................................................................................... 13 12.2 Support for Combined OBSAI/CPRI ........................................................... ................................................................................................. ......................................13 12.3 Redirection to ultraFDD supported only ........................................................................................... 13 12.4 Juniper SEC-GW ....................................................... .......................................................................................................................... ....................................................................... .... 14 12.5 Checkpoint SEC-GW ........................................................................................................................ ........................................................................................................................14 12.6 TLS renegotiation between BTS and BTS Site Manager fail ........................................................... 14 12.7 Auto Connection and VLAN Scan Optimization .............................................................. ............................................................................... ................. 14 12.8 LTE497 Smart Admission Control: Avoid GBR admission in empty cells c ells fail .................................. 15 12.9 IPSec PROTECT / BYPASS Policies Definition ........................................................................... ............................................................................... .... 15 12.10 ICMP Rate Limiting .................................................................................................................. ..................................................................................................................15 12.11 LTE574 IP Transport Network Measurements: Configuration of the UDP Port number of the TWAMP Responder .......................................................................................................................... ..........................................................................................................................15 12.12 BTS Site Manager: Date/Time in Transmission Alarms is misleading .................................... 16 12.13 Import new MRBTS SW to NetAct ............................................................................. ........................................................................................... ..............16 12.14 Automatic Synchronization with NetAct after upgrade of eNB ................................................ ................................................ 17 FL16A 6.0 Installation Instruction - Page 2/23 Version 1.0 Confidential

© Nokia 2017

12.15 LTE523 Multi-layered Certificate Authorities: Manual key and certificate commissioning ...... 18 12.16 BTS booted due to TRS power on reset during FSMF upgrade ..............................................18 12.17 Supported PRACH Configuration index values .......................................................................18 12.18 RF Sharing: Upgrade ............................................................................................................... 18 12.19 LTE-LTE RF-Sharing update ................................................................................................... 18 12.20 RF Sharing WCDMA-LTE Synchronization without LTE1710 Sync Hub direct forward .........18 12.21 RF sharing W CDMA-LTE with FSMF used for the LTE side ...................................................18 12.22 Don’t configure WCDMA -LTE RF sharing in use if shared BTS site does not contain WCDMA system module .................................................................................................................................. 22 12.23 Hardware exchange fALU Radio Module or Base Band Unit ..................................................22 12.24 RTWP level below threshold (4333) ........................................................................................ 22 12.25 3CC Carrier Aggregation throughput ....................................................................................... 22 12.26 Cell block/unblock operations .................................................................................................. 22 12.27 External baseband module (FBBA/FBBC/FBIH/ABIA...) .........................................................23 12.28 Additional eNB reset needed in rare cases (faults 1868 or 4001) ...........................................23 13. Fallback .................................................................................................................................................23 13.1 No Configuration changes during SW upgrade ................................................................................ 23 13.2 APPENDICES / REFERENCES .......................................................................................................23

Contact: Contact your local Nokia support.

Summary of changes: 26-Apr-2017

1.0


Approved version

© Nokia 2017

Disclaimer The information in this document applies solely to the hardware/software product (“Product”) specified herein, and only as specified herein. Reference to “Nokia” later in this document shall mean the respective company within Nokia Group of Companies with wh om you have entered into the Agreement (as defined below). This document is intended for use by Nokia's customers (“You”) only, and it may not be used except for the purposes defined in the agreement between You and Nokia (“Agreement”) under which this document is distributed. No part of this document may be used, copied, reproduced, modified or transmitted in any form or means without the prior written permission of Nokia. If You have n ot entered into an Agreement applicable to the Product, or if that Agreement has expired or has been terminated, You may not use this document in any manner and You are obliged to return it to Nokia and destroy or delete any copies thereof. The document has been prepared t o be used by professional and properly trained personnel, and You assume full responsibility when using it. Nokia welcomes your comments as part of the process of continuous development and improvement of t he documentation. This document and its contents are provided as a convenience to You. Any information or statements concerning the suitability, capacity, fitness for purpose or performance of the Product are given solely on an “as is” and “as available” basis in this document, and Nokia reserves the right to change any such information and statements without notice. Nokia has made all reasonable efforts to ensure that the content of this document is adequate and free of material errors and omissions, and Nokia will correct errors that You identify in this document. Nokia's total liability for any errors in the document is strictly limited to the correction of such error(s). Nokia does not warrant that the use of the software in the Product will be uninterrupted or error -free. NO WARRANTY OF ANY KIND, EITHER EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO ANY WARRANTY OF AVAILABILITY, ACCURACY, RELIABILITY, TITLE, NON-INFRINGEMENT, MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE, IS MADE IN RELATION TO THE CONTENT OF THIS DOCUMENT. IN NO EVENT WILL NOKIA BE LIABLE 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, EVEN IN THE CASE OF ERRORS IN OR OMISSIONS FROM THIS DOCUMENT OR ITS CONTENT. This document is Nokia proprietary and confidential information, which may not be distributed or disclosed to any third parties without the prior written consent of Nokia. Nokia is a registered trademark of Nokia Corporation. Other product names mentioned in this document may be trademarks of their respective owners. Copyright © 2017 Nokia. All rights reserved.

Important Notice on Product Safety This product may present safety risks due to laser, electricity, heat, and other sources of danger. Only trained and qualified personnel may install, operate, maintain or otherwise handle this product and only after having carefully read the safety information applicable to this product. The safety information is provided in the Safety Information section in the “Legal, Safety and Environmental Information” part of this document or documentation set. Nokia is continually striving to reduce the adverse environmental effects of its products and services. We would like t o encourage you as our customers and users to join us in working towards a cleaner, safer environment. Please recycle product packaging and follow the recommendations for power use and proper disposal of our products and their components. If you should have questions regarding our Environmental Policy or any of the environmental services we offer, please contact us at Nokia for any additional information.


© Nokia 2017

1. PURPOSE The purpose of this document is to describe the actions needed for installing and or upgrading this Release Delivery into the customer’s network. It contains common Operator Hints that have to be taken in account during and after installation/upgrade.

2. OVERVIEW This document covers Installation Instruction Flexi Multiradio BTS LTE. Standard installation instructions are available in the Customer Documentation library [2], accessible through NOLS [1] at Nokia Long Term Evolution Information Center [3]. It is required to carefully study content of the library and follow on detailed procedures described in the documents. It will be specified in this document which instruction should be used for installation of certain entit y; all exceptions from base procedure will be listed in this document. During the execution of the procedure user will be asked to stop following the official Customer Documentation and execute steps mentioned here. H ow to access Customer Documentation is described in point 2.1. 2.1 Other Relevant Installation Instruct ions

All LTE Customer Documentation, including standard installation procedures, is accessible through NOLS [1] in the section “Product Information Center” Nokia Long Term Evolution Information Center [3] It is very important to check if new Change Deliveries are available – they may contain newer version of the documents.

3. PREPARATIONS Hardware used for the installation should be integrated according to the hardware installation guide and all necessary cabling should be already done. Necessary documents can be found in the section “Install and commission” in the Customer Documentation librar y For the Flexi Multiradio BTS LTE reference documents are named “Installing Flexi Multiradio BTS LTE…” available in the LTE Radio Access, Rel. FDD-LTE16A, Operating Documentation [2] •

4. MAKING A SAFE COPY OF THE PACKAGE N/A

5. SW DOWNLOADING INSTRUCTION The software for the released pro ducts is available in NOLS. •

Flexi Multiradio B TS LTE: https://online.networks.nokia.com/SWD/?access_key=MTI4NDQy


© Nokia 2017

Softw are Item BTS Site Manager FSME BTS Site Manager FSMF & Air Scale eNB Golden SCF/FSMF Golden SCF/FSME

Softw are File Name

SHA1 check sum

BTS Site Manager (ltesdkroot)_FL15A_BTSSM_0000_000167_0000 00.zip BTS Site Manager (ltesdkroot)_FL16A_BTSSM_0000_000270_0000 00.zip FL16A_ENB_0000_006051_000000_release_BT SSM_downloadable.zip GoldenConfig-FL16A-ENB-3050-onwards-201701-04.zip Golden Config FL15A_ENB_001030_28onwards_2015-09-02.zip

NetAct PPLTE16AMP4v5

netact-PPLTE16AMP4-5-disc1.iso

PPValidator106

netact-PPValidator106-1-disc1.iso

EBA42E2895E924049ABBB 4E300C264EDC79B8892 96C36ACDB6540C680EAF4 414451FA569EC25F0E6 3B29D7BBA25385B4105232 C2E40B2B65A0C27787 A5EAAB71EB0C45D5D8362 B112B1538C077B05A2A 8FD8FEB9EBA215CD24FB6 4B9DD3542307EEB65ED 52274F1040A0071E0ECF2F 6EDACFCA0D8D077175 8E8F7C85A00DC2EBDB807 C471176D6A2ACFBF087

6. SPECIAL CONDITIONS 6.1 FHCA A.103 operating cond ition s

FHCA 472169 A.103 product (FPGA) should be used in max. 2*20W DL power. This firmware must only be used under the following conditions: 20W mode -40 to +50 degrees. 6.2 FRGP Power Setti ng

Symmetrical power setting IN FRGP can be used for e xample: WCMDA 10W + LTE 10W Asymmetrical power setting in WCDMA-LTE (WCDMA power different than in LTE) is not supported by FRGP.A RF Module, except for: - WCDMA 15W + LTE 30W @ 10MHz - WCDMA 15W + LTE 45W @ 15MHz

7. RF-SHARING Unless otherwise stated, it is recommended to first upg rade the master technology (i.e. LTE f or GSM-LTE configurations) as the SW management of Radio Modules in RF sharing is done via the master System Module only. For the newest information and restrictions regarding the RF-Sharing please refer toClassical RF Sharing Compatibility Matrix. RF-Sharing is not supported for AirScale system module. 7.1.1 LTE-GSM RF Sharing (EX)

LTE-GSM RF-Sharin g GSM16


Status for FL16A 4.0

EX16 1.0

NC

EX16 2.0

Com.

© Nokia 2017

Rec. Com. Rel. NC

EX16 3.0

Com.

EX16 4.0

Com.

EX16 5.0

Com.

SW combination recommended SW combination compatible SW combination released (can be used as interim pair in SW update) not compatible

Following upgrade paths were tested: EX5_2 3.0 to EX16 3.2 with pair FL16A 4.0.1 FL15A 1.5.2 upgrade to FL16A 3.0.5 with pair EX16 3.4 FL15A 1.2 to FL16A 4.0.1 with pair EX5_2 3.0 EX5_2 3.0 to EX16 3.2 with pair FL16A 4.0.1 FL15A 1.3 to FL16A 5.0 with EX5_2 3.0 • • • • •

7.1.2 LTE-GSM RF Sharing (GF)

LTE-GSM RF-Sharin g

GSM16

GSM17 Rec. Com. Rel. NC

Status for FL16A 4.0

GF16.5

Com.

GF16.5 1.0

Com.

GF16.5 2.0

Com.

GF17

Com.

GF17 1.0

Com.


Following upgrade paths were tested: FL16A to FL16A 3.0 with pair GF16.5 2.0 GF16 upgrade to GF16.5 2.0 with pair FL16A 3.0.5 FL16 4.0 to FL16A 3.0 with pair GF16.5 2.0 FL16 6.0 to FL16A with pair GF16.5 2.0 FL15A 1.5.2 upgrade to FL16A 3.0.5 with pair GF16 GF16 upgrade to GF16.5 2.0 with pair FL16A 3.0.5 • • • • • •

7.1.3 WCDMA-LTE RF Sharing

WCDMA-LTE RF Sharing

WCDMA16

WCDMA17


Status f or FL16A 4.0

WBTS16 2.0

Com.

WBTS16 3.0

Com.

WBTS16 4.0

Com.

WBTS17

Com.

WBTS17 1.0

Com.

WBTS17 2.0

Com. © Nokia 2017

Rec. Com. Rel. NC


Following upgrade paths were tested: FL16A 1.0 to FL16A 2.0 with pair WBTS17 1.0 FL16A 2.0 to FL16A 3.0 with pair WBTS17 1.0 WBTS16 3.0 to WBTS17 1.0 with pair FL16A 1.0 WBTS16 3.0 to WBTS17 1.0 with pair FL16A 3.0 FL16A 1.0 to FL16A 4.0 with pair WBTS16 3.0 FL16A 2.0 to FL16A 4.0 with pair WBTS17 1.0 FL16A to FL16A 4.0 with pair WBTS17 WBTS16 3.0 to WBTS17 1.0 with pair FL16A 4.0 WBTS17 to WBTS17 1.0 with pair FL16A 4.0 WBTS16 3.0 to WBTS17 1.0 with pair FL16A FL16A 1.0 to FL16A 4.0 with pair WBTS17 • • • • • • • • • • •

8. COMPATIBILITY MATRIX 8.1 OAM compatibility

If there are two values in the given cell, the second one describes the compatibility of FSME system module. eNB SW package contains FSME, FSME and AirScale software so there is no need to download a dedicated SW package for FSME. For FSME the dedicated BTS Site Manager package should be used, such package is a part of this delivery. SW delivery

FL16A P8/C5

Flexi Mult iradi o BTS LTE

BTSSM

FL16A_ENB_0000_000833_000086

FL16A_BTSSM_0000_000237_0 00000

FL15A_ENB_0107_001667_000000 FL15A_BTSSM_0000_000164_0 00000 FL16A_ENB_0000_000860_000018

FL16A_BTSSM_0000_000237_0 00000

FL16A 0.1 FL15A_ENB_0107_001667_000000 FL15A_BTSSM_0000_000164_0 00000 FL16A_ENB_0000_000870_000009

FL16A_BTSSM_0000_000237_0 00000


FL16A_BTSSM_0000_000237_0 00000


FL16A_BTSSM_0000_000248_0 00000

FL16A 1.0 FL15A_ENB_0107_001754_000000 FL15A_BTSSM_0000_000166_0 00000


LTE OMS

R_GOMS7_1.10. 1.0 Corr14

R_GOMS7_1.10. 1.0 Corr14

R_GOMS7_1.10. 1.0 Corr14

R_GOMS7_1.10. 1.0 Corr14

R_GOMS7_1.10. 1.0 Corr17

NetAct

BTSSM in NetAct FL16A_BTSSM_0000_000 237_000000

NetAct 16.8 P8 FL15A_BTSSM_0000_000 164_000000 FL16A_BTSSM_0000_000 237_000000 NetAct 16.8 P8 FL15A_BTSSM_0000_000 164_000000 FL16A_BTSSM_0000_000 237_000000 NetAct 16.8 P8 FL15A_BTSSM_0000_000 164_000000 FL16A_BTSSM_0000_000 237_000000 NetAct 16.8 P8 FL15A_BTSSM_0000_000 164_000000 NetAct 16.8 P8+ PPLTE16AMP1 v.5

FL16A_BTSSM_0000_000 248_000000 FL15A_BTSSM_0000_000 164_000000

© Nokia 2017

SW delivery

Flexi Mult iradi o BTS LTE

BTSSM

FL16A_ENB_0000_000890_000007

FL16A_BTSSM_0000_000237_0 00000


FL16A_BTSSM_0000_000248_0 00000


FL16A_BTSSM_0000_000256_0 00000


FL16A_BTSSM_0000_000256_0 00000


FL16A_BTSSM_0000_000259_0 00000


FL16A_BTSSM_0000_000267_0 00000


FL16A_BTSSM_0000_000268_0 00000

FL16A 5.0 FL15A_ENB_0107_001818_000000

FL16A_ENB_0000_006051_000000

FL15A_BTSSM_0000_000167_0 00000 FL16A_BTSSM_0000_000270_0 00000

FL16A 6.0 FL15A_ENB_0107_001822_000000 FL15A_BTSSM_0000_000167_0 00000

LTE OMS

R_GOMS7_1.10. 1.0 Corr14

NetAct

BTSSM in NetAct FL16A_BTSSM_0000_000 237_000000

NetAct 16.8 P8 FL15A_BTSSM_0000_000 164_000000 FL16A_BTSSM_0000_000 248_000000

R_GOMS7_1.10. 1.0 Corr17

NetAct 16.8 P8+ PPLTE16AMP1 v.5

R_GOMS7_1.10. 1.0 Corr17

NetAct 16.8 P8+ PPLTE16AMP2v.2 or NetAct 16.8 P8+ PPLTE16AMP2v.3

FL16A_BTSSM_0000_000 256_000000

R_GOMS7_1.10. 1.0 Corr19

NetAct 16.8 P8+ PPLTE16AMP2v.2 or NetAct 16.8 P8+ PPLTE16AMP2v.3

FL16A_BTSSM_0000_000 256_000000

R_GOMS7_1.10. 1.0 Corr20

NetAct 16.8 P8+ PPLTE16AMP3v5

R_GOMS7_1.10. 1.0 Corr21

NetAct 16.8 P8+ PPLTE16AMP4v5

R_GOMS7_1.10. 1.0 Corr22

NetAct 16.8 P8+ PPLTE16AMP4v5 or NetAct 16.8 P8+ PPLTE16AMP4v5+ PPValidator099

R_GOMS7_1.10. 1.0 Corr23

NetAct 16.8 P8+ PPLTE16AMP4v5+ PPValidator106

FL15A_BTSSM_0000_000 164_000000

FL15A_BTSSM_0000_000 164_000000

FL15A_BTSSM_0000_000 164_000000 FL16A_BTSSM_0000_000 259_000000 FL15A_BTSSM_0000_000 164_000000 FL16A_BTSSM_0000_000 267_000000 FL15A_BTSSM_0000_000 164_000000 FL16A_BTSSM_0000_000 267_000000 FL15A_BTSSM_0000_000 164_000000 FL16A_BTSSM_0000_000 270_000000 FL15A_BTSSM_0000_000 164_000000

8.2 Inter eNB Carrier Aggregation features compatibi lity

Inter-eNB Carrier Aggregation features are supported for the listed below SW releases combination.


© Nokia 2017

TD-LTE SW deliv ery

FDD-LTE SW deliv ery

TL16A P8

FL16A P8

TL16A 0.1

FL16A 0.1

TL16A 0.2

FL16A 0.2

TL16A 0.3

FL16A 0.3

TL16A 1.0

FL16A 1.0

TL16A 0.4

FL16A 0.4

TL16A 2.0

FL16A 2.0

TL16A 2.1

FL16A 2.1

TL16A 3.0

FL16A 3.0

TL16A 4.0

FL16A 4.0

TL16A 5.0

FL16A 5.0

TL16A 6.0

FL16A 6.0

It is recommended to upgrade both technologies in the similar time to the compatible SW

9. DATA MIGRATION N/A

10. RELEASE DELIVERY UPGRADE INSTRUCTION 10.1 First installation and comm ission ing

The commissioning procedure of the Flexi Multiradio BTS LTE is described in the document “Commissioning Flexi Multiradio BTS LTE” [3]. Please be aware that BTS Site Manager shall be updated before the BTS SW. 10.2 Project upgrade

System upgrade is described in customer documentation "LTE System Upgrade" [7]. 10.3 Supported update/upgr ade paths

For the information about the installation of the SBTS SW please refer to the BTS SW compatibility chapter in the SBTS Release Upgrade Instruction document of given SBTS release. Upgrade to FL16A 6.0 (FL16A_ENB_0000_006051_000000) was tested from the following SW levels: Release

FDSW

SW delivery

SW version

FDSW 1.0

FDSW1.0_RP_FD1405_310_00

FDSW 1.1

FDSW1.0_RP_FD1405_317_00

FDSW 2.0

LN_WN_FDSW20_R4_TRUNK_38 5

FL15A 1.3

FL15A_ENB_0107_001667_000000


Comments This upgrade should be executed in following steps: FDSW 1.0 -> RL70 2.5 -> FL15A 1.5 -> FL16A 6.0

AirScale FSMF © Nokia 2017

Release

SW delivery

FDDLTE15A

FL15A 1.5

FL15A_ENB_0107_001788_000000

FSME/FSMF

FL16 1.0

FL16_ENB_0000_001169_000000

FSMF

FL16 5.0

FL16_ENB_0000_001566_000000

FSMF

FL16 7.0

FL16_ENB_0000_001809_000000

FSME/FSMF

FL16A P8

FL16A_ENB_0000_000833_000086

FSMF

FL16A 0.2

FL16A_ENB_0000_000870_000009

FSMF

FL16A 0.4

FL16A_ENB_0000_000890_000007

FSMF

FL16A 2.1

FL16A_ENB_0000_002227_000000

FSMF/AirScale*

FL16A 4.0

FL16A_ENB_0000_004115_000000

FSMF

FL16A 5.0

FL16A_ENB_0000_005049_000000

FSME/FSMF/AirScale

FDDLTE16

FDDLTE16A

SW version

Comments

*please refer to the chapter 10.4.6 Rollback from FL16A 4.0, FL16A 5.0 and FL16A 6.0 to FL16A 2.1

10.4 General installation hints

10.4.1 Cases when SW update is not allowed SW update is not allowed in case: there is ongoing Radio unit reset, there is ongoing BTS reset, RF unit is blocked or being blocked. • • •

10.4.2 Carrier Aggregation scenarios - range of scellActivationLevel parameter adapted In order to better cover typical carrier aggregation field scenarios, the value range of scellActivationLevel parameter has been optimized in FL16A. The high values 100TTI and 1000TTI have been replaced by more suitable values 5TTI and 20TTI. During upgrade to FL16A the eNB configuration is automatically adapted and scellActivationLevel values 100TTI or 1000TTI are converted to 20TTI (new maximum value of scellActivationLevel in FL16A). 10.4.3 No Configurations during SW upgrade HW configuration changes should not be done during SW upgrade as this may lead to inconsistencies in the internal configuration files. Changes in configurations should either be executed before SW upgrade or after SW upgrade. In case the changes have been executed before SW upgrade a SW fallback will keep the configuration changes. In case LTE_FL16A the configuration change will be done directly after SW upgrade and then a SW fallback will be initiated, the changed configuration may lead to start-up problems with former SW. Reason would be that the internal configuration file of pre-upgrade will be used and this may not match the changed configuration. 10.4.4 CM Upload must be executed after eNB upgrade in case Automatic Synchronization with NetAct is not enabled After the upgrade of an eNB is executed a CM Upload with CM Operation Manager must be executed to synchronize the eNB database with NetAct in case Automatic Synchronization with NetAct is not enabled.


© Nokia 2017

10.4.5 Invalid EARFCN values in LNCEL/IRFIM/dlCarFrqEut (EUTRA frequency value) leads to cell setup failure (fault 6253) Starting with FL16A, eNB SW is checking if the “EUTRA frequency value” parameter of the IRFIM object corresponds to a DL EARFCN value as defined b y 3GPP in specification 36.101. If this is not the case, ce ll setup will fail and the fau lt "Cell configuration data distribution failed (6253)" is reported for this cell. In order to avoid such cell setup problems, the “EUTRA frequency value” parameters of all IRFIM objects should be checked for validity against 3GPP before upgrading to FL16A. 10.4.6 Rollback from FL16A 4.0, FL16A 5.0 and FL16A 6.0 to FL16A 2.1 Rollback from FL16A 4.0, FL16A5.0 and FL16A 6.0 to FL16A 2.1 performed for the AirScale system module equipped with the CPRI radios can cause a fault: 7653 - Configuration error: BTS config error (Not enough HW for LCR) (1868) and 7653 - Failure in optical interface (10) on all cells and RM's connected to ABIA 1 module . Reset of the eNB should be performed as a recovery action.

11. CRAN 11.1 Project up grade to FL16A 6.0

Upgrade to FL16A 6.0 (FL16A_ENB_0000_006051_000000) with CRAN features activated is supported from the following SW levels: Release FDDLTE15A FDDLTE16

FDDLTE16A

SW deliv ery

SW versi on

BTS Site Manager

FL15A 1.5

FL15A_ENB_0107_001788_000000

FL15A_BTSSM_0000_000167_000000

FL16 1.0

FL16_ENB_0000_001169_000000

FL16_BTSSM_0000_000186_000000

FL16 5.0

FL16_ENB_0000_001566_000000

FL16_BTSSM_0000_000199_000000

FL16 7.0

FL16_ENB_0000_001809_000000

FL16_BTSSM_0000_000207_000000

FL16A 0.4

FL16A_ENB_0000_000890_000007

FL16A_BTSSM_0000_000237_000000

FL16A 2.1

FL16A_ENB_0000_002227_000000

FL16A_BTSSM_0000_000256_000000

FL16A 4.0

FL16A_ENB_0000_004115_000000

FL16A_BTSSM_0000_000267_000000

FL16A 5.0

FL16A_ENB_0000_006051_000000

FL16A_BTSSM_0000_000268_000000

1

All cells need to be consistent otherwise configuration error will be displayed: a. Band b. EARFCN c. Radio configuration type d. Same type of radios.

2

CRAN configured, enabled and operational on ALL FSMs. a. Backup SCFC and Commissioning files on each FSM. b. Existing cells should be “ On Air ”, no visible alarms.

3

SW update on ALL FSMs to FL16A SW eNB SW delivery a. eNB: with FL16A SW. b. BTS Site Manager: related BTS Site manager. c. All FSMs can be updated at the same time. d. Existing cells should be “ On Air ”, no visible alarms


© Nokia 2017

11.2 CRAN operato r hin ts

11.2.1 ToP-frequency vs GPS/ToP-phase as synchronization source for master Regardless of synchronization source of the master, the sync mode between SHDF master (SHM) and all SHDF slaves (SHS) is always phase sync mode. Phase sync mode is needed in order to establish RP3-01 interconnections between SHM-SHS and SHS-SHS. Phase sync between SHM and SHS means that also the BCN counters in these nodes are aligned, via 1PPS & ToD. With frequency sync mode (ToP-frequency) in the master, the BCN counter in the master is arbitrary after each startup as there is no precise external source like GPS or ToP-phase available. This means that 1PPS & ToD generated by the master will have significant offset after reset compared to the ‘tolerable window = + - 5us‘ in the SHSs and hence the SHS need to re-align their BCN counters, which requires a reset. The advantage of master phase sync mode (GPS or ToP-phase) is that the master, and hence the whole SHDF chain, is aligned with its BCN counters to an external source. After a SHM reset, the master will re-align its own BCN again to the external source before enabling 1PPS & ToD towards SHSs. As long as the outage of the master and he nce the holdover period in the slave is limited such that the phase deviation between master and slave is within the ‘tolerable window = + - 5us’, all SHS will continue with pha se tuning, otherwise they will re-align their BCN counters. The need for SHSs to re-align their BCN counters after a reset is more likely when frequency sync mode for SHM is used. 11.2.2 SFP needed in all FBBC’s port 3 Even if chain configuration would be used and there is no inter-connection between last helper and master, the last helper s till needs to have a SFP installed in FBBC2 port 3. If the SFP is missing, then startup issues can be expected. 11.2.3 cranId value range It is recommended to set the cranId parameter to the value from the range 1-34463. Values other than these will trigger a CRAN configuration alarm (4274) .

12. GENERAL OPERATOR HINTS 12.1 Ping RTT requi rement

Instead of 10ms ping RTT requirement, for AirScale is sufficient to reach 11ms in FL16A. 12.2 Suppo rt for Comb ined OBSAI/CPRI

Combined OBSAI/CPRI on same eNB is not supported in FL16A. 12.3 Redirection to ult raFDD supp orted only Redirection is only supported to utraFDD. There is no feature ‘Redirection to utraTDD’. Nevertheless, the value ‘utraTDD’ can be sele cted in instances of the managed object classes REDRT, MORED and MODRED. FL16A 6.0 Installation Instruction - Page 13/23 Version 1.0 Confidential

© Nokia 2017

Please do not set parameter redirRAT to ‘utraTDD’ in REDRT, MORED and MODRED otherwise the related cell will not provide service and the alarm ‘Cell configuration data distribution failed’ will be reported after upgrade. 12.4 Jun iper SEC-GW

If eNB trust chain has a different Root CA, it is necessary to install as Trust Anchor in the GW not only the eNB RootCA but a lso the complete eNB trust chain including all interm ediate CAs. 12.5 Checkpoint SEC-GW

Operation mode: Round robin for Ethernet interface on Checkpoint should be avoided as packet loss is observed with this setting in R&D Lab. Recommended setting for Ethernet interface operation mode configuration at Checkpoint to be set to LACP (802.3ad) . IKEv1: To work with IKEv1 one need to choose exclusively “IKEv1 only” mode in community level on CP. IKEv1: Multi tunnel configuration: Not released (Restriction for multi tunnel configurations due to CP offering of traffic selector of 0.0.0.0/0 0.0.0.0/0 (universal tunnel) and so no IPSec SA established.) Multi Layer Certificates: Multi Layer Certificates operation with Checkpoint is no t released by Nokia Security organization. 12.6 TLS renegotiati on between BTS and BTS Site Manager fail

Due to a known interoperability issue between OpenSSL and Java SSL stack s, TLS renegotiation on connection between BTS and BTS Site Manager may fail and result in abrupt termination of the connection. This problem may occur in t wo situations: 1. It may occur occasionally on the management connection (i.e. XoH interface) between BTS and BTS Site manager. The occurrence is expected to be rare (one or two times of connection loss in 24h when rene gotiation time is set as the minimum value: 300s). Since BTS Site Manager automatically reconnects with BTS two minutes later, the impact is minimum. 2. The problem may also occur on the file transfer connection between Flexi Zone Micro BTS and BTS Site Manager via Satellite Backhaul, in case the setting of TLS renegotiation interval is small. To avoid the issue, it is proposed to keep default setting of TLS renegotiation interval, i.e. 24 hour; or simply turn off time-based TLS renegotiation temporarily during software download. 12.7 Auto Connection and VLAN Scan Optimi zation

Cisco Interoperability for improved eNB AutoConnection Feature. The SON feature has been improved to be faster. In case of using VLANs at the transport configuration a VLAN scan functionality has been introduced. This feature will inspect all incoming packets to detect the VLAN IDs in use. Since this process speeds up the switching time between sending DHCP DISCOVER messages as plain frames and sending VLAN tagged messages, a change at the access router/switch has to be made if it is a Cisco device. By default, a physical interface on Cisco is set to support “DTP – Dynamic Trunking Protocol” which is a proprietary protocol. If this is enabled, it will try to detect configured trunks on the FL16A 6.0 Installation Instruction - Page 14/23 Version 1.0 Confidential

© Nokia 2017

next hop once the port is up. It will block the VLAN IF to be up for 30sec. This will cause the DHCP negotiation to fail. According to Cisco’s documentation this feature should be turned off if the next hop is not a Cisco product. Therefore, configuration of the physical interface at Cisco router/switches should be as following: ----- Example ----TT_Cisco#sh run int gi 3/11 Building configuration... Current configuration : 273 bytes ! interface GigabitEthernet3/11 description Gi 3/11 Temp AutoConnection switchport switchport trunk encapsulation dot1q switchport trunk allowed vlan 201 switchport mode trunk switchport nonegotiate logging event link-status spanning-tree portfast trunk end 12.8 LTE497 Smart Admissio n Control: Avo id GBR admission in empt y cells fail When 'Enhanced AC and GBR services' are activated, i.e. if ‘actEnhAcandGbrServices’ equals 'true', it is highly recommended to configure ‘gbrCongHandling’ to 'l2andl3'. If it not configured like this, GBR admission in empty cells may fail. 12.9 IPSec PROTECT / BYPASS Polic ies Definit ion

For the configuration of IPSec policies in the eNB, the following rule needs to be considered. In case of several matching IPsec policies, the polic y rule which shall be applied needs to have a lower number than the other m atching policy. The lowest number of several matching policies is applied first. For example, if a wide-ranging PROTECT policy is defined (e. g. ANY-TO-ANY) and a dedicated traffic type shall bypass the IPSec tunnel, than the BYPASS policy needs to be configured with a lower ‘Policy Order Number’ than the protect policy. 12.10 ICMP Rate Lim iti ng

In order to avoid a system outage due to DoS attacks (ICMP flood) the ingress and egress ICMP packet rates are limited. Only a burst of 8 ICMP_ECHO_REQUESTS / ICMP_ECHO_REPLY are allowed. If e.g. more than 8 ICMP_ECHO_REQUESTS are sent in a burst, eNB will only reply to the f irst 8. This is applicable for the eN B interface address(es) (Ethernet and VLAN). 12.11 LTE574 IP Transport Network Measurements: Configur ation of the UDP Port numb er of the TWAMP Responder

Currently, the UDP port of the TWAMP Reflector can be freely configured in the range from 0 to 65535, with a default value of 5000. Free configuration of this parameter requires special care, since the entries may conflict with p ort numbers which are already assigned to other applications. E.g. the port numbers 0 … 1023 and 5001 … 5010 are reserved and must not be FL16A 6.0 Installation Instruction - Page 15/23 Version 1.0 Confidential

© Nokia 2017

used for the TWAMP responder function. Currently, th e system does not support a complete check of the configured TWAMP responder port number aga inst all other port numbers used in the system. To avoid conflicts between the TWAMP UDP port number and other port numbers, it is recommended to always use the default value of 5000. It has been found that the flexibility in configuring the port number does not provide a real benefit, and using a fixed value eliminates the possibility of misconfigurations. 12.12 BTS Site Manager: Date/Time in Transmissio n Alarms i s misl eading

Date/time included in fault name of transmission alarms is misleading in BTS Site Manager. Same issue is correctly displayed in NetAct Alarm Monitor. 12.13 Impor t new MRBTS SW to NetAct

When a new MRBTS SW is imported to NetAct SW Archive the ‘Version ID’ and the ‘Package name’ should be set to the SW release version. By default the file name of the SW is entered. If the default name is used an automatic fallback via NE-triggered-SW-update wouldn’t work: Before import is executed, select ‘Details’

And enter in the fields ‘Version ID’ and ‘Package name’ the SW release version e.g. FL16A_ENB_0000_000231_000003 as shown as example in the picture above and below.


© Nokia 2017

12.14 Autom atic Synchronization wit h NetAct after upgrade of eNB By default the feature LTE954 ‘Intelligent Configuration Synchronization’ is disabled in NetAct.

If it is disabled data s ynchronization via CM Upload of NetAct must be execut ed manually after upgrade (the same way as it was in previous releases, e.g. after upgrade from FL16 to FL16A). If it is enabled the aut omatic upload of the configuration data is not started immediately after upgrade, it is started after a configurable time interval. Furthermore there are situations when it is necessary to perform manually the data synchronization after upgrade even the feature is enabled. This can happen when the establishment of the OAM connection takes a long time, but the startup of the eNB is very quick, e.g. when eNB is configured with only one cell and OAM connection with IPSEC. If af ter upgrade the configuration data synchronization state is empty the eNB must be manually synchronized with NetAct. For more information about the configuration of the feature LTE954 ‘Intelligent Configuration Synchronization’ please refer to the documentation of LTE954.


© Nokia 2017

12.15 LTE523 Multi-layered Certif icate Authoriti es: Manual key and certifi cate commissio ning

Manual key and certificate commissioning: BTS and eNB does not support slash ‘/’ as subject name element separator. 12.16 BTS booted due to TRS power on r eset during FSMF upgrade

When FSMF upgrade requires FPGA version upgrade, during activation of new software, an additional power on reset occur after FPGA firmware update. Because of this reset, after software upgrade, BTS booted alarm due to TRS power on reset alarm will observed. Alarm can be ignored in this case. 12.17 Supported PRACH Configur ation index values Cell band wid ths 5.0 MHz, 10 MHz, 15 MHz and 20 MHz (dlChBw ) Supported PRACH Configuration index values are: PRACH format 0: 3…8 PRACH format 1: 19…24 Cell bandwidths 1.4 MHz and 3 MHz (dlChBw) Supported PRACH Configuration index values are: PRACH format 0: 3, 4, 5 PRACH format 1: 19, 20, 21 12.18 RF Sharing : Upgr ade

Unless otherwise stated, it is recommended to first upg rade the master technology (i.e. LTE) as the SW management of Radio Modules in RF sharing is done via the master System Module only. 12.19 LTE-LTE RF-Sharing up date

During LTE-LTE RF-sharing configuration upgrade it m ight happen that after slave side is updated radios are not detected on both SMs after slave reset. Additional reset of both SMs is required in this situation to restore configuration to working state. 12.20 RF Sharing WCDMA-LTE Synchro nization wit hout L TE1710 Sync Hub direct fo rward •

•

•

Clock source switching from OCXO to clock received from RP3-01, when operating as an extension system module or as a synchronization slave system module. At slave system module, the setting about the sync is not necessary. Synchronization will be fixed to master system module. If system module is synchronized to master system module, Site manager will display the synchronization source as “Other BTS”.

12.21 RF shari ng WCDMA-LTE wit h FSMF used for the LTE side LTE side: Local Maintenance Terminal (LMT) of the LTE eNB: Set the IP address of the LMT PC to 192.168.255.126/24.


© Nokia 2017

LTE BTS Site Manager: It is possible to use local or remote IP addresses to login to th e LTE eNB with BTS Site Manager. In case of using the local IP address, for a standalone LTE eNB choose the option “Local”:


© Nokia 2017

For an LTE eNB running in RF sharing WCDMA-LTE configuration, choose “Local (192.168.255.127)”:

After enabling or disabling RF sharing for the LTE eNB, please restart the BTS Site Manager with the correct option. Alternatively the remote IP address of the LTE eNB can be used. WCDMA side: Local Maintenance Terminal (LMT) of the LTE eNB: Set the IP address of the LMT PC to 192.168.255.130/24.


© Nokia 2017

WCDMA BTS Site Manager: It is possible to login with local or remote IP addresses to the W CDMA BTS with BTS Site Manager. Use the option Local, or the remote IP address of the BTS. For example, using the option Local:


© Nokia 2017

12.22 Don’t configure WCDMA-LTE RF sharing in use if s hared BTS site does not c ontain WCDMA system module

If WCDMA system module does not exist AND if WCDMA-LTE RF sharing has been tak en into use then BTS remains in initializing state because WCDMA system module is fixedly synchronization master in WCDMA-LTE RF sharing and if it do es not exist then BTS remains in initializing state. Initializing state in BTS SW prevents reconfiguration commissioning from BTSSM Workaround: If this accidently happens it is possible to commission BTS to the synchronization master mode via NetAct, because Flexi Radio auto-detection is not required, when commissioned via NetAct. 12.23 Hardware exchange fALU Radio Module or Base Band Unit

When a fALU radio (i.e. UHID) is moved from one eNB to another eNB within 30 seconds, there is a possibility of an IP address conflict. If the reinserted radio’s IP address is the same IP address of an existing radio on the eNB, then the existing radio will go out of se rvice. The existing radio (cell) will go off air for around 2.5 minutes before automatically recovering and coming back on line. This issue exists on the fALU BBU as well, but only when moving across eNBs AND changing to a different port. To avoid this problem, wait 30 seconds after disconnecting a radio module or BBU before reinsert it when moving radios across eNBs. 12.24 RTWP level below th resho ld (4333)

After simultaneous unblocking of the RF-module and the supported cells (in MIMO configuration where a cell is served by 2 RF-modules), occasionally the fault "RTWP level below threshold (4333)" is reported for one cell. The cell is down. This problem can be avoided when cells are unblocked when the RF module is up again. In case the RTWP alarm is reported for a cell you can block / unblock the cell to clear the alarm. 12.25 3CC Carrier Aggregation thr ough put 3CC Carrier Aggregation throughput decreased compared to previous release if “User layer TCP MSS clamping" (LTE1240) is activated (parameter: “Activation of user layer TCP MSS clamping” / actUserLayerTcpMssClamping). This throughput degradation happens only with TCP traffic. UDP is not affected. 12.26 Cell block/unbloc k operation s

During cell block/unblock operations on a eNB with UL-ComP and SuperCell feature activated occasional UL-PHY DSP crash occurred, then FSP reset was triggered due to auto rec overy action. During cell block/unblock operations in rare cases it may occur, that Cells 13-18 remain in disabled state without any alarm. This does not happen in configurations up to 12 cells. The problem was found during automated tests with many block/unblock actions and occurr ed only once.


© Nokia 2017

12.27 External baseband modul e (FBBA/FBBC/FBIH/ABIA...)

During normal startup procedure, sometimes, FSP reconfiguration res et is necessary (reconfigure timing). Then the working state of external baseband module will be updated to “resetting”, and the LED indication is update to “Red” without any fault. BTS will get to operational status after this resetting. This issue will be fixed by LTERLCR-14856 in XL17A. 12.28 Add iti onal eNB reset needed in rare cases (faults 1868 or 4001)

In rare cases it has been observed that the startup of AirScale based eNBs (using ASIA/ABIA modules) fails and fault 1868 or 4001 is raised. An additional eNB reset is needed in such cases to recover the system. In case fault 1806 is raised, the eNB takes care about the recovery autonomously.

13. FALLBACK 13.1 No Config uration changes during SW upgr ade

HW configuration changes should not be done during SW upgrade as this may lead to inconsistencies in the internal configuration files. Changes in configurations should either be executed before SW upgrade or after SW upgrade. In case the changes have been executed before SW upgrade a SW fallback will keep the configuration changes. In case the configuration change will be done directly after SW upgrade and then a SW fallback will be initiated, the changed configuration may lead to start-up problems with former SW. Reason would be that the internal configuration file of pre-upgrade will be used and this may not match the changed configuration. For new HW that was not support ed by previous SW (i.e. FBBC extension board) the HW changes and configuration have to be done after SW upgrade. Those changes must be revoked before fallback otherwise the previous SW may not work. 13.2 APPENDICES / REFERENCES

[1] NOLS - Nokia Online Services log in link: https://online.networks.nokia.com [2] LTE Radio Access, Rel. FDD-LTE16A, Operating Documentation [3] Nokia Long Term Evolution Information Center


© Nokia 2017

FL16A 6.0 Installation Instruction.pdf

Recommend Documents