This document is posted to help you gain knowledge. Please leave a comment to let me know what you think about it! Share it to your friends and learn new things together.
ID: RL55_LNT5.0_P8Release Delivery: RL55Produ ct Family: Base Stations, Radio ControllersProduct: Flexi Mult iradio BTS TD-LTE, LTE iOMS7.0, Flexi Zone BTS
Release: LNT5.0 LTE iOMS7.0, LNZ5.0
Document name:
LTE_RL55_LNT5.0_P8 Summary of Corrections and Enhancements
LTE_RL55_LNT5.0_P8 LGF
LTE_RL55_LNT5.0_P8 Release Upgrade Instructions
LTE_RL55_LNT5.0_P8 Release Compatibility Report
LTE_RL55_LNT5.0_P8 Supplementary document
LTE_RL55_LNT5.0_P8 Impact document
Nokia Solutions and Networks is continually striving to reduce the adverse environmental effects of itsproducts and services. We would like to encourage you as our customers and users to join us inworking towards a cleaner, safer environment. Please recycle product packaging and follow therecommendations 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 serviceswe offer, please contact us at Nokia Solutions and Networks for additional information.
Nokia Solutions and Networks is continually striving to reduce the adverse environmental effects of its
products and services. We would like to encourage you as our customers and users to join us in working
towards a cleaner, safer environment. Please recycle product packaging and follow the recommendationsfor 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 Solutions and Networks for additional information.
3. New / Changed functionality .................................................................................................................... 3
3.1 Released Features ................................................................................................................................................... 3
3.1.1 Flexi Multi-radio Released Features ......................................................................................................................... 3
3.1.2 Flexi Zone Released Features ................................................................................................................................. 5
3.2 Restricted Released Features .................................................................................................................................. 6
3.2.1 Flexi Multi-radio Restricted Released Features ........................................................................................................ 6
3.2.2 Flexi Zone Restricted Released Features ................................................................................................................ 7
3.3 Legacy Released Features ...................................................................................................................................... 8
3.3.1
Flexi Multi-radio Legacy Released Features ............................................................................................................ 8
3.3.2 Flexi Zone Legacy Released Features ................................................................................................................... 15
4. 3RD party corrections ............................................................................................................................ 20
5. Released objects ................................................................................................................................... 20
5.1 Released software versions ................................................................................................................................... 20
5.1.1 eNB Software file list .............................................................................................................................................. 20
5.1.1.1 Flexi Multi-radio eNB Software file list ................................................................................................ 20
5.1.1.2 Flexi Zone eNB Software file list ........................................................................................................ 21
5.1.2 iOMS Software file list ............................................................................................................................................ 21
5.1.3 EPC Software file list (R&D Lab Environment) ....................................................................................................... 21
5.1.4 NetAct Software file list .......................................................................................................................................... 21
5.1.5
Tested UE Software file list .................................................................................................................................... 21
5.1.5.1 Flexi Multi-radio Tested UE Software file list ...................................................................................... 21
5.1.5.2
Flexi Zone UE Software file list .......................................................................................................... 22
6.1 TDS Version ........................................................................................................................................................... 24
The purpose of this document is to give a brief summary on the RL55 P8 Release Deliverycorrections content.
2. CORRECTIONS
Refer to LGF file.
3. NEW / CHANGED FUNCTIONALITY
3.1 Released Features
3.1.1 Flexi Multi-radio Released Features
ID Feature Name Correc tion Plan
1481 OMS LDAP web GUI Released
1053 Real-time KPI-monitoring with Traffica Released1685 Neighbor Relation Robustness Released
CRL1439 SBM Active UE & UE Throughput Counters Released
CRL1976 Frame configuration for single mode- RL55 Released
CRL1910 Complete sub-configuration support in super cell Released
1779 Triple carrier operation ReleasedCRL2703 Introduce enhanced hardware version FZFF-e Released
1636 Extended site configuration with FSIH ReleasedCRL2702 Support 10MHz in RL55 configurations Released
CRL3428 Updates in RL55 OBSAI site configurations Released1335 9.8Gbps Ir Interface for FSIH Released
1780 FZHJ-b Flexi RRH 8TX 2600 BD41 for China Released
CRL2601 Site configurations with FZHJ-b Released908 ANR Inter-RAT WCDMA - Fully UE based Released
CRL1553 Configuration with FZNK FZNL FZNN mixed - R55 parent ReleasedCRL1890 Support different super cell topology between TDS and TDL - RL55 Released
CRL2493 Add 12x1 star configuration with FZHO/FZHG and FSIH Released
CRL1580 Support of dual mode FZNN sub-configurations - RL55 parent ReleasedCRL5994 Advance dual carrier chaining configurations from TL15A to RL55 Released
ID Feature Name Correc tion Plan2054 Measurement Report addition with PDCP KPI counter subset Released1914 Support Received Interference Power (RIP) alarm ( CRL2091 scope
clarification)Released
648 SCTP Multi-homing Released
1042 Nominal Bitrate for non-GBR bearers ReleasedCRL3314 Updates in RL55 site configuration Released
CRL1911 Support more than one super cell Released
1266 BTS and BTS Site Reset Support Released
907 TTI bundling Released1740 PM Counters enhancement for RAB-modification/context/TM7
(CRL2608)Released
CRL1636 Cell alarm should be initiated when FSP is out of work - parent Released
1935 PM counters for HO incoming ReleasedCRL2038 Extend 1T1R FZND configuration with super cell - RL55 Released
1664 TD-SCDMA redirect with multiple frequencies Released1240 User Layer TCP MSS clamping Released
1731 Serving PLMN ID change during X2 based handover Released
1467 TDD Special Subframe Configuration 9 ReleasedCRL1703 Adding CMAS/ETWS PM-counters (unsuccessful case) Released
1127 Service based mobility trigger Released
1617 RLF triggered handover Released
CRL3441 Dedicated mobility thresholds for SRVCC ReleasedCRL1951 DL CAC counter histogram per resource area Released
1545 UL MU MIMO 8RX Released
1800 Downlink interference shaping Released
1388 TDD Special Subframe Configuration 3 and 4 Released
CRL3086 Improved alarm for optical link failure in TD- Radio Modules Released1954 FZHP Flexi RRH 2TX 2600 Released
1442 Open access home eNode B mobility Released
CRL1970 Adding PM-Counters for E-RAB performance monitoring for non-GBR-specific QCI
Released
1841 load balance with Equalization Released1721 X2 IP address exchange Released
1845 eNB SW support for FYGE Released
2050 Load triggered Idle Mode Load Balancing ReleasedCRL2124 Site configurations with FZHI Released
CRL3414 sub-counters for ENB initiated UE context release request per cause
value
Released
CRL3378 Add Commscope antenna types in the antenna weight configurationprofile - parent
Released
CRL3043 CA support with PCell and SCell reserved for operator use Released
CRL2989 VLAN Scan Optimization ReleasedCRL2500 Support up to 64 cells of neighbor eNBs Released
CRL4559 FZHG 2T2R chain without super cell config in RL55 ReleasedCRL5005 SW adapatation for CMCC 1.9G 3rd party RRU frequency change Released
ID Feature Name Correc tion PlanCRL2494 Configuration of FSMF with single mode RRU ReleasedCRL5980 B38 and B41 carrier support within same HW - RL55 Released
3.1.2 Flexi Zone Released Features
ID Feature Name Correc tion Plan
1481 OMS LDAP web GUI Released
1053 Real-time KPI-monitoring with Traffica Released1685 Neighbor Relation Robustness Released
1703 3GPP baseline R11 09/2013 Released908 ANR Inter-RAT WCDMA - Fully UE based Released
DisclaimerThe information in this document is subject to change without notice and describes only theproduct defined in the introduction of this documentation. This documentation is intended for theuse of Nokia customers only for the purposes of the agreement under which the document issubmitted, and no part of it may be used, reproduced, modified or transmitted in any form ormeans without the prior written permission of Nokia. The documentation has been prepared tobe used by professional and properly trained personnel, and the customer assumes fullresponsibility when using it. Nokia welcomes customer comments as part of the process ofcontinuous 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 liabilityarising in connection with such hardware or software products shall be defined conclusively andfinally in a separate agreement between Nokia and the customer. However, Nokia has made allreasonable efforts to ensure that the instructions contained in the document are adequate andfree of material errors and omissions Nokia will, if deemed necessary by Nokia, explain issueswhich may not be covered by the document.
Nokia will correct errors in this documentation as soon as possible. IN NO EVENT WILL NOKIABE LIABLE FOR ERRORS IN THIS DOCUMENTATION OR FOR ANY DAMAGES,INCLUDING BUT NOT LIMITED TO SPECIAL, DIRECT, INDIRECT, INCIDENTAL ORCONSEQUENTIAL 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 andother intellectual property rights according to the applicable laws.
The wave logo is a trademark of Nokia. Nokia is a registered trademark of Nokia Corporation.Other product names mentioned in this document may be trademarks of their respectiveowners, and they are mentioned for identification purposes only.
Nokia Solutions and Networks is continually striving to reduce the adverse environmental effects of itsproducts and services. We would like to encourage you as our customers and users to join us in workingtowards a cleaner, safer environment. Please recycle product packaging and follow the recommendationsfor 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 weoffer, please contact us at Nokia Solutions and Networks for additional information.
Table of Contents1 OVERVIEW ............................................................................................................................................ 4
A description of what will be the most likely phenomena seen in the network because of the problem................ 4
2 Generic open faults (tOP Priority) ............................................................................................................ 5
2.1 [RL55 FSMF]Incorrect parameter configuration for actDrx and riPerM after parameter conversion fromRL45 to RL55 ........................................................................................................................... ............................................ 5
2.2 [RL55_FSMF]: In Super cell the CNT_Counter updates incorrectly during paging ................................................. 5
2.3 [RL55] upgrade fallback due to srsSubfrConf migation issue from RL45 to RL55.................................................... 5
2.4 [RL55 FSIH][OBSAI FZHA] 1911 is reported when BTS is connected with 20KM fiber ........................................... 6
2.12 [RL55 FISH]Angle value update to 0 after do calibration triggered via commissioning wizard ................................. 9
2.13 [RL55 FSIH]DHCP server for SSE is not working .................................................................... ................................ 9
2.14
[RL55 FSIH]:activation failed when try to delete non existed RRU using recommission. ....................................... 10
2.15
[RL55 FSIH][LTE 1812]FYGB need do 2 times self-survey then self-survey can be completed ............................ 10
2.16 [RL55 FSIH][CPRI][9.8G]STA_After site reset, 4011 and 0010 alarm arise, RRU can't be detected. ................... 10
[RL55 FSIH] The eNB cannot enter handover mode if it used FYGH (FSIH Built-in) ............................................. 12
2.22 [RL55 FSIH][LTE891]Multicast is unstable, fault 61058 and 61631 reported and canceled repeatedly ................. 13
2.23
[RL55 FISH] Cell3 keeps in notCalculated state ................................................................................. ................... 13 2.24 [RL55 FSIH][FZHJ] OAM crashed due to Bus error (reason: 128 'unknown') ........................................................ 13
2.25 [RL55 FSMF FZFE][Single mode] Fault 1868(Not enough HW for LCR) occurred after unplug the fiberbetween BBU and RRU...................................................................................................................................................... 14
2.26 [RL55] LNT5.0_ENB_1407_555_00 Activating parameters failed under special scenario .................................... 14
2.27 [RL55 FSIH] There is no error notification when deleting 'antCablingMappingConfig' under a cell ........................ 15
2.28 [RL55 FSIH] BTS cann't on air with alarm failure in optical RP3 interface ............................................................. 15
2.30 [RL55TD FSIH+FZHJ][Sprint] DC voltage administratively disabled (4141) alarm after SW upgrade toLNT5.0_ENB_1407_555_00 .................................................................. ..................................................................... ....... 16
2.31 [RL55 FSMF]LTE_5143A RRC Connection Re-establishment Success Ratio is low in KPI test ........................... 16
2.32 [RL55 FSIH][Stability] Fault0010&fault1806 active/cancel on RRUs and some of cells not on air onLNT5.0_ENB_1407_523_03 .................................................................. ..................................................................... ....... 17
2.33
[RL55 FSIH] [stability]BTS cann't be on air with warning "failure in optical RP3 interfae" ...................................... 17
2.34
[RL55 FSIH]: FSIH+FZNN RMOD report 0010 and 2001 alarm after upgrade RL45LNT4.0_ENB_1311_657_01 to RL55 build LNT5.0_ENB_1407_555_03 ................................................................... ....... 17
3 Flexi ZONE Generic open faults ............................................................................................................ 18
3.1 BTS site manager: Unexpected Error .................................................................................................................... 18
3.2 Poor UL performance with FULLA when compared to EULLA ............................................................ ................... 18
3.3 TRS ETH IF Ethernet statistics counter showing wrong values ...................................................................... ....... 19
3.4 CLPC doesn't work with VoLTE traffic...................................................................................... .............................. 19
3.5 eNB SM could enable eICIC without btssyncmode .................................................................. .............................. 19
List of Generic Faults describes the current unsolved problemsaffecting the functionality of the Flexi LTE Base Station, as well as the corrections made tothe existing problems.
Chapter 2 lists the newly opened problems in this releaseChapter 3 lists the open problems in all previous releasesChapter 4 lists the newly solved problems in this releaseChapter 5 lists the solved problems in all previous releases
The problem descriptions are structured as follows:
Problem title: Title of the problemProblem report: Problem ID numberExists in: Product and software release in which the problem existsCorrected in / Correction Target: Product/software release in which the problem is
A short description of the problem and in the corrected cases also a description of thecorrection.
Attached PR:
Related Fault reports attached with same root cause. This field is optional.
Probability: • Rare: 1-2 cases during an observation period• Seldom: few times during an observation period• Occasional: seen several times (5-10) during an observation period• Permanent: will occur always when a configuration or a feature is used
Workaround:
Describes method to avoid the problem or minimize the defect impact before the actualcorrection is available
Impact to Operator:
A description of what will be the most likely phenomena seen in the network because ofthe problem
2.1 [RL55 FSMF]Incorrect parameter configuration for actDrx and riPerM after parameterconversion from RL45 to RL55
Problem Report: 122529ESPE01Exists in: LNT5.0_ENB_1407_523_00Correction Target: RL55_MP1Severity: B - MajorDescription:[1 testing steps]Offline converted commissioning file from RL45 to RL55.[2. Fault Description]Incorrect parameter of ‘actDrx’ is shown on BTSSM.Configuration (parameters):
RL45 version: riPerM !=1; riEnable=false; actDrx=trueSummary of the original problem:There is inconsistency in PDDB between related parameters and descriptionThe configuration of actDrx= true in RL45 is meaningless because riEnable=false.conversion from RL45 to RL55Customer Impact: Operation & MaintenanceProbability: PermanentSolution / Workaround: Configure the parameter ‘actDrx’ as false before upgrade SW andthen reconfigure actDrx and riPerM manullay after SW upgradeImpact to Operator: The convert of ‘actDrx’ will occur error.
2.2 [RL55_FSMF]: In Super cell the CNT_Counter updates incorrectly during paging
Problem Report: 122558ESPE01Exists in: LNT5.0_ENB_1407_523_04Correction Target: RL55_PP0.1Severity: C - MinorDescription:[1 testing steps]1. BTS is on air2. UE connects to BTS[2. Fault Description]In snapshot,M8008C3 (RRC_PAGING_MESSAGES) is much bigger than M8001C220(RLC_SDU_PCCH) and M8001C9 (TRANSMIT_TB_ON_PCH).Currently investigationshows paging messages from CELLC to MAC PS are discarded.
[2. Fault Description]BTS will fallback due to srsSubfrConf is not set any value.
Customer Impact: Operation & MaintenanceProbability: PermanentSolution / Workaround: Configure srsSubfrConf to a proper value in RL45, and then dosystem upgrade to RL55.Impact to Operator: Upgrade failure.
2.4 [RL55 FSIH][OBSAI FZHA] 1911 is reported when BTS is connected with 20KM fiber
Problem Report: 126552ESPE04Exists in: LNT5.0_ENB_1407_500_08Correction Target: RL55_MP1Severity: C - MinorDescription:
[1 testing steps]Power on BTS (BBU and RRU is connected with 20KM fiber links).[2. Fault Description] Alarm 1911 is reported after BTS is on air.Configuration:Test line HW info: FSIH (085570A.Y32) + 1*FZHA(085283A.102) + FYGAConfiguration: T1-L-137-8TX-8RXSummary of the original problem: Alarm 1911 is reported after BTS is on air when BTS is connected with 20KM fiberCustomer Impact: New feature/functionalityProbability: PermanentSolution / Workaround: NAImpact to Operator: RRU will continue to reset, only impact FZHA
2.5 [RL55 FSIH T333][stabi li ty]FYGH GPS device read timeout during BTS startup
Problem Report: 126921ESPE04Exists in: LNT5.0_ENB_1407_501_05Correction Target: RL55_PP0.1Severity: C - MinorDescription:[1 testing steps]BTS reset[2. Fault Description]FYGH will trigger self-survey or will detect failed during BTS startupConfiguration:
FSIH (A101) + 3*FZHJ-b (3A101) + 2*FBIH (A101) + FYGHBTS GPS type is FYGHSummary of the original problem:FYGH will trigger self-survey or will detect failed during BTS startupCustomer Impact: StabilityProbability: OccasionalSolution / Workaround: Reset eNB by BTSSMImpact to Operator: The startup success rate, only impact FYGH
2.6 [RL55 FSIH CPRI 9.8G][FiVe] 544_19_Reference clock missing in star tup 4153
Problem Report: 127856ESPE04Exists in: LNT5.0_ENB_1407_554_19
[1 testing steps]1. reset BTS.[2. Fault Description] After reset BTS from site manager, Reference clock missing in startup 4153, RF cannot bedetected and cell can’t be on Air.Configuration:T11-8TX-8RXSummary of the original problem: After reset BTS from site manager, Reference clock missing in startup 4153, RF cannot bedetected and cell can’t be onAir..Customer Impact: StabilityProbability: OccasionalSolution / Workaround: Reset eNB by BTSSM.
Impact to Operator: The eNB is not available to put in service,only impact CPRI mode
2.7 [RL55 FSMF CPRI] Fault 10 visible in SEM after unblock ing RRU
Problem Report: 127863ESPE04Exists in: LNT5.0_ENB_1407_554_12Correction Target: RL55_MP1Severity: C - MinorDescription:[1. Test Scenario Steps]1. SW active build is LNT5.0_ENB_1407_554_122. Block RRU_3, fault 48 visible as expected3.Unlock RRU_3, fault 48 cancel and fault 0010 raise on it.
4. Fault 10 cancel after RRU come back.[2. Fault Description]Fault 10 visible in SEM after unblock RRU.Configuration:HW configuration: FSIH+2FZHO+FZHG+FYGBCustomer Impact: Operation & MaintenanceProbability: PermanentSolution / Workaround: No recovery. Alarm is cancelled after RRU come back.Impact to Operator: No impact, fault 10 visible due to RRU reset, fault 10 is cancelled afterRRU come back. only impact CPRI mode.
2.8 [RL55 FSIH] FSI5 disconnected after BTS reset
Problem Report: 127882ESPE04Exists in: LNT5.0_ENB_1407_554_29Correction Target: RL55_MP1Severity: C - MinorDescription:[1 testing steps]1. Connect the BTS FSI5/EIF5 interface with Cisco3560 via fiber and 1000BaseZX SFP.2. Restart the BTS and check again the connection on FSI5 interface.[2. Fault Description] After BTS restart, the connection via FSI5 is broken.Configuration:FSIH+FYGB+FZHA T1-L-30-8TX-8RXCustomer Impact: Operation & Maintenance
Solution / Workaround: Use FSI1/EIF1~FSI4/EIF4 as S1 intherface or disable the FSI5 andthen enable it again when this issue occur
Impact to Operator: S1 is disconnected if customer uses FSI5/EIF5, all cells of eNB areoffline, only impact FSIH
2.9 [RL55 FSIH]alarm 4176 raised on 1407_555_00
Problem Report: 128002ESPE04Exists in: LNT5.0_ENB_1407_555_00Correction Target: RL55_PP0.1Severity: C - MinorDescription:[1 testing steps]Save snapshot on SEM.[2. Fault Description]
During save snapshot, Alarm 4176 raised. After alarm 4176 raised, save snapshot again, the save snapshot operation is OK.Configuration:DM FSIH (A101)+2*FZFA+1FZFD T111-L-545-8TX-8RXCustomer Impact: Operation & MaintenanceProbability: OccasionalSolution / Workaround: Save snapshot again and the log can be collected, but the alarmcan’t be cancelled, except reset the BTS.Impact to Operator: The RRU log can’t be uploaded into the snapshot at the first time, onlyimpact CRPI dual mode
2.10 [RL55 FSIH][CPRI FZNN]BTS synchronization is missing dur ing star tup (4160) is repor tedafter SWDL
Problem Report: 128048ESPE04Exists in: LNT5.0_ENB_1407_556_04Correction Target: RL55_PP0.1Severity: C - MinorDescription:[1 testing steps]1. BTS on air on LNT5.0_ENB_1407_556_012. Update SW to LNT5.0_ENB_1407_556_043. check BTS[2. Fault Description] Alarm 4160 (BTS synchronization is missing during startup) is reported after SWDLConfiguration:
DM T2222-1TX-1RXSummary of the original problem:Synchronization signal is unavailable.Customer Impact: StabilityProbability: OccasionalSolution / Workaround: Reset eNB by BTSSMImpact to Operator: BTS can’t be on air with alarm 4160, only impact CPRI mode.
[1 testing steps]1. BTS is on air[2. Fault Description]Many DENOM* counters update incorrectly, such as counters M8018C9, M8001C265 duringone period.Configuration:FSIH+FZFF (T11/DM) or FSMF+FZNN(T1/DM)Summary of the original problem: Counters with name DENOM* updates bigger or shorterthan expected values in 15 minutes. Investigation shows the update time has extended orcut short.Customer Impact: Operation & MaintenanceProbability: OccasionalSolution / Workaround: NA
Impact to Operator: The incorrect counting of DENOM_ACTIVE_UE_ENB will bring somemisunderstanding of active corrected UE KPI
2.12 [RL55 FISH]Angle value update to 0 after do calibration triggered via commissioningwizard
Problem Report: 153567ESPE02Exists in: LNT5.0_ENB_1407_495_29Correction Target: RL55_PP0.1Severity: C - MinorDescription:[1 testing steps]1. Modify the value of Mechanical Angle from 1 to 3 via RET Setting window
2. Do RET calibration triggered via commissioning wizard3. Check the operation process from RET Setting Dialog.[2. Fault Description]The value of RET angle all change to 0.Configuration:HW: FSIH (101) + FZHJ*3 + single/multi RETSummary of the original problem:Tilt angle will be set to 0 after RET calibrationCustomer Impact: Operation & MaintenanceProbability: PermanentSolution / Workaround: Re-set the tilt angle value.Impact to Operator: After RET calibration, the tilt angle will be cleared
2.13 [RL55 FSIH]DHCP server for SSE is not working
Problem Report: 154465ESPE02Exists in: LNT5.0_ENB_1407_510_00Correction Target: RL55_MP1Severity: B - MajorDescription:[1 testing steps]1. Enable the DHCP server with IP rang 192.168.19.2~192.168.19.2002. Connect the PC to LMP port and enable the DHCP[2. Fault Description]The PC retrieved the IP address 192.168.253.197 from BTS.Configuration:
Solution / Workaround: Restart dhcpd in FTC via SSH connection.Impact to Operator: SSE(site support equipment) node cannot get ip address in theconfigured scope.
2.14 [RL55 FSIH]:activation failed when try to delete non existed RRU using recommission.
Problem Report: 155039ESPE02Exists in: LNT5.0_ENB_1407_537_00Correction Target: RL55_MP1Severity: C - MinorDescription:[1 testing steps]1. RRU is not connected to eNB and 0010 alarm is reported in BTSSM,
2. Do recommission using BTSSM, after all commission steps finished, activation alwaysfailed.[2. Fault Description]If RMOD lost and 0010 alarm reported in BTSSM, activation failed when do recommissionConfiguration:Common configurationCustomer Impact: Operation & MaintenanceProbability: PermanentSolution / Workaround: Upload new SCFC to eNB manuallyImpact to Operator: To delete non-connected RRU by using recommission will fail, onlyimpact CPRI mode
2.15 [RL55 FSIH][LTE 1812]FYGB need do 2 times self -survey then self-survey can be
completed
Problem Report: 155497ESPE02Exists in: LNT5.0_ENB_1407_554_29Correction Target: RL55_PP0.1Severity: C - MinorDescription:[1 testing steps]1. Deleted FYGB store position info2. FYGB start self survey[2. Fault Description]FYGB need do self-survey twice then self-survey can be completedConfiguration:
FSIH+FZND+FYGBCustomer Impact: Operation & MaintenanceProbability: PermanentSolution / Workaround: Wait second self-survey progress finishImpact to Operator: Need do self-survey twice. Only impact FYGB
2.16 [RL55 FSIH][CPRI][9.8G]STA_After si te reset, 4011 and 0010 alarm arise, RRU can' t bedetected.
Problem Report: 155528ESPE02Exists in: LNT5.0_ENB_1407_542_00Correction Target: RL55_PP0.1Severity: B - Major
[2. Fault Description] After site reset, alarm 4011 and 0010 raise, RRU can't be detected.Configuration:SM T75-1TX-1RX1 (FSIH+12*FZNN+FYGH)Summary of the original problem:GPS can’t be detected after site reset or cold resetCustomer Impact: StabilityProbability: OccasionalSolution / Workaround: Reset BTS one more timeImpact to Operator: eNB can’t be on air, only impact CPRI mode
2.17 [RL55] eNB stays commissioned
Problem Report: 155676ESPE02Exists in: LNT5.0_ENB_1407_555_00Correction Target: RL55_MP1Severity: B - MajorDescription:[1 testing steps]eNB on-air with RL45 MP2LNT5.0_ENB_1407_555_00 SW downloaded and activated.[2. Fault Description]
After startup eNB stays commissioned state, no active alarms.Configuration:T111-M-44-4TX-4RX, FSMF A.102, FBBA A.101, 2xFZHA A.102, 1xFZHA A.103, 3 Cells4x2 CLMIMO, FYGA HW 3001
Summary of the original problem: After startup eNB stays commissioned state, no activealarms.Customer Impact: StabilityProbability: OccasionalSolution / Workaround: Reset the eNB manuallyImpact to Operator: eNB can’t be on air.
2.18 [RL55 FSIH]'Read only' error code for RET occured after upgrade eNB from RL45MP2 toRL55 P8
Problem Report: 155711ESPE02Exists in: LNT5.0_ENB_1407_555_00Correction Target: RL55_RL55_PP0.1
Severity: C - MinorDescription[1 testing steps]Upgrade the eNB from RL45 MP2 to LNT5.0_ENB_1407_555_00[2. Fault Description]The error code ‘Read only’ for RETS reported.Configuration:HW: FSIH + 3*FZHJ + RET (Tong you)Summary of the original problem:Min/max angle value updated on RL45 SCF when the value is read onlyCustomer Impact: Operation & MaintenanceProbability: PermanentSolution / Workaround: Do RET calibration or reset eNB
Once in a while。Customer Impact: New feature/functionality
Probability: Permanent
Solution / Workaround: NAImpact to Operator: The eNB will not enter handover mode
2.22 [RL55 FSIH][LTE891]Mul ticast is unstable, fault 61058 and 61631 reported and canceledrepeatedly
Problem Report: 59981ESPE05Exists in: LNT5.0_ENB_1407_510_00Correction Target: RL55_RL55_MP1Severity: B - MajorDescription:[1. Test Scenario Steps]
1. eNB is selected ToP as sync source and on air. Just wait.
[2. Fault Description]Multicast is unstable with sync message rate 128.Fault Synchronization lost(61058) and ToP master service unusable(61631) reported andcanceled repeat on SEM.Customer Impact: New feature/functionalityProbability: PermanentSolution / Workaround: It will reocver by itself if the TOP sync source was availableImpact to Operator: It will affect multicast holdover function
2.23 [RL55 FISH] Cell3 keeps in notCalculated state
Problem Report: 60449ESPE05Exists in: LNT5.0_ENB_1407_537_00
Correction Target: RL55_RL55_PP0.1Severity: C - MinorDescription:[1 testing steps]1. reset BTS.[2. Fault Description]One of the cells cannot be onair, and no alarm reported for the disabled cellConfiguration:T222-8TX-8RXSummary of the original problem: After BTS reset, one of cells cannot turn to enable state, and no alarm reported for thedisable cell.Customer Impact: Stability
Probability: OccasionalSolution / Workaround: Reset eNBImpact to Operator: Cell cannot be onair and it is without any alarm. Only OBSAI mode wasimpacted
2.24 [RL55 FSIH][FZHJ] OAM crashed due to Bus error (reason: 128 'unknown' )
Problem Report: 60635ESPE05Exists in: LNT5.0_ENB_1407_554_29Correction Target: RL55_PP0.1Severity: B - MajorDescription:[1 testing steps]
1: eNB is running well on version LNT5.0_ENB_1407_553_14
2: Do SW upgrade from LNT5.0_ENB_1407_553_14 to LNT5.0_ENB_1407_554_02.3: eNB cannot be on air on LNT5.0_ENB_1407_554_02
4: The issue was also found on LNT5.0_ENB_1407_554_29[2. Fault Description]OAM crashed due to Bus error (reason: 128 'unknown') during eNB startup processeNB keep in configured state and alarm 4019 was reportedConfiguration:* HW: FSIH +1*3FZHJ* T222-8TX-8RXSummary of the original problem:OAM crashed due to Bus error during BTS startup process.Customer Impact: StabilityProbability: OccasionalSolution / Workaround: Reset eNBImpact to Operator: BTS crash sometimes and can’t go into onair status. Only impact OBSAI
mode
2.25 [RL55 FSMF FZFE][Single mode] Fault 1868(Not enough HW for LCR) occurred afterunplug the fiber between BBU and RRU
Problem Report: 60741ESPE05Exists in: LNT5.0_ENB_1407_554_29Correction Target: RL55_RL55_MP1Severity: C - MinorDescription: Fault 1868(Not enough HW for LCR) occoured after unplug the fiber betweenBBU and RRU while it is supposed to be fault 0010(Failure in optical RP3 interface).Customer Impact: Operation & MaintenanceProbability: Permanent
Solution / Workaround: Insert the fiberImpact to Operator: The affected cell cannot be onair while the fault ID was wrong. OnlyCPRI mode was impacted
2.26 [RL55] LNT5.0_ENB_1407_555_00 Ac tivating parameters failed under specialscenario
Problem Report: 60761ESPE05Exists in: LNT5.0_ENB_1407_555_00Correction Target: RL55_RL55_PP0.1Severity: B - MajorDescription[1. Testing Steps]
1. Change TAC with SEM.[2. Fault Description]If HWF does not match with SCFC file, activating parameters failed.Configuration:T111-8TX-8RXSummary of the original problem:Change parameters which need reset eNB, activating parameters failed.Customer Impact: Operation & MaintenanceProbability: PermanentSolution / Workaround: Delete HWF file manually and reset eNBImpact to Operator: Cannot change parameters with BTSSM, only impact CPRI single mode8T8R configuration
2.27 [RL55 FSIH] There is no error notif ication when deleting 'antCablingMappingConfig'under a cell
Problem Report: 60773ESPE05Exists in: LNT5.0_ENB_1407_555_00Correction Target: RL55_MP1Severity: C - MinorDescription:[1 testing steps]1. Configure the BTS and make it in on air state.2. In BTS commission, delete the "antCablingMappingConfig" and send parameters.[2. Fault Description]There is no error notification when deleting "antCablingMappingConfig" under a cell. And thesending of parameter is successful.Configuration:
FSIH+FYGB+FZHA T1-L-30-8TX-8RXCustomer Impact: Operation & MaintenanceProbability: PermanentSolution / Workaround: “antCablingMappingConfig” is mandatory and should not be deletedImpact to Operator: 6253: EFaultId_CellSetupFailed will be raised on the faulty cell after eNBreseting
2.28 [RL55 FSIH] BTS cann't on air with alarm failure in opt ical RP3 interface
Problem Report: 90989ESPE03Exists in: LNT5.0_ENB_1407_553_14Correction Target: RL55_PP0.1Severity: C - Minor
TDDCPRI didn't switch protocol to OBSAI and 2 BBC set the wrong detectedprotocol onBBSIWTCHConfiguration:1FSIH+1FZHJ +2FBIH+FYGE, 3Cells + 2 piper, T111-I-123-2TX-2RX configurationSW version: LNT5.0_ENB_1407_555_00Summary of the original problem:GS Bts cann't on air with warnning "failure in optical RP3 interfaceCustomer Impact: Stability
Probability: OccasionalSolution / Workaround: Reset eNB by BTSSMImpact to Operator: BTS can’t be on air, There is a risk for SW upgrade in large scale. Onlyimpact OBSAI mode
[1. Test Scenario Steps]1. BTS on air with load LNT5.0_ENB_1407_554_32
2. 150 CPEs with traffic doing HO under Cell1 and Cell33. 400 UEs (TM500) with traffic under cell 3[2. Fault Description]Test had run for about 34 hours then DSP 0x1232 fatal error happened.Customer Impact: StabilityProbability: OccasionalSolution / Workaround: Reset eNB by BTSSMImpact to Operator: eNB crashed and traffic is interrupted
2.30 [RL55TD FSIH+FZHJ][Spr int] DC voltage admini strati vely disabled (4141) alarm after SWupgrade to LNT5.0_ENB_1407_555_00
Problem Report: 155723ESPE02
Exists in: LNT5.0_ENB_1407_555_00Correction Target: RL55_PP0.1Severity: B - MajorDescription:[1 Testing steps]1. eNB with RETs running LNT4.0_ENB_1311_657_06 or LNT5.0_ENB_1407_444_12 – noalarms2. Upgrade SW to LNT5.0_ENB_1407_555_003. Upon completion of upgrade observe 4141 alarm4. Clear alarms by resetting eNB – no parameter changes required[2. Fault Description]In some instances the fiber on the first optical interface is detected later than the fiber onsecond interface. When the RRU doesn’t match configuration it is considered un-
commissioned for a short period of time. For un-commissioned RRU, ALMAG is required toapply defaults to RRU, including enabling ALD power feed and scan. Since the RRU wasconsidered un-commissioned for a short time, the 4141 alarm was triggered even though ALD DC power had been disabled in the eNB configuration.Customer Impact: Operation & MaintenanceProbability: PermanentSolution / Workaround: Re-commissionImpact to Operator: User observes fault 4141 is reported, but no impact on functionality.Only impact OBSAI mode
2.31 [RL55 FSMF]LTE_5143A RRC Connect ion Re-establishment Success Ratio is low in KPItest
Problem Report: NA05777873Exists in: LNT5.0_ENB_1407_555_02Correction Target: RL55_PP0.1Severity: B - MajorDescription:[1. Test Scenario Steps]1. Upgrade from RL45 to RL55 (pre-P8).2. All the sites are running more than one week.[2. Fault Description] After upgraded, RRC Connection Re-establishment Success Ratio is lower than the target(99.5%) in KPI testConfigurationFSMF+FBBA+3*FZHA
Impact to Operator: Impact customer network performance indicator of LTE_5143A
2.32 [RL55 FSIH][Stability] Fault0010&fault1806 active/cancel on RRUs and some of cells noton air on LNT5.0_ENB_1407_523_03
Problem Report: 127350ESPE04Exists in: LNT5.0_ENB_1407_523_03Correction Target: RL55_PP0.1Severity: B - MajorDescription:[1. Test Scenario Steps]1. SW active build is LNT5.0_ENB_1407_523_032. Did a cold site reset.
[2. Fault Description] Alarm 1806 (Unit autonomous reset as recovery action) and 0010 (Failure in optical RP3interface) occurred and then cancelled automatically.Finally, all cells were on air except cell2 which was disabled (grey). In the meantime eNBreported1806 on cell5.HW configuration: FSIH+3FZHJ +FYGB+2FBIHCustomer Impact: StabilityProbability: OccasionalSolution / Workaround: Reset eNB by BTSSMImpact to Operator: eNB reset success rate is low. Only impact OBSAI mode.
2.33 [RL55 FSIH] [stabi li ty]BTS cann't be on air with warning " failure in optical RP3 interfae"
Problem Report: 91250ESPE03Exists in: LNT5.0_ENB_1407_555_02Correction Target: RL55_PP0.1Severity: C - MinorDescription:[1 testing steps]1.1 Cell on air1.2 cold reset waiting cell on air[2. Fault Description]
Even though the BBU / bbsiwtch protocol is OBSAI. But there are failure in optical RP3interface (0010)on the process of startup , the probability is occasionalConfiguration:1FSIH+1FZHJ +2FBIH+FYGE, 3Cells + 2 piper, T111-I-123-2TX-2RX configuration
SW version: LNT5.0_ENB_1407_555_00Summary of the original problem:GS BTS can’t be on air with warning "failure in optical RP3 interfaceCustomer Impact: StabilityProbability: OccasionalSolution / Workaround: Reset eNB by BTSSMImpact to Operator: FSIH+FZHJ test line reset success rate is low. Only impact OBSAI mode
2.34 [RL55 FSIH]: FSIH+FZNN RMOD repor t 0010 and 2001 alarm after upgrade RL45LNT4.0_ENB_1311_657_01 to RL55 build LNT5.0_ENB_1407_555_03
Problem Report: 123544ESPE01Exists in: LNT5.0_ENB_1407_555_03
There are fault 0010 and 2001 in BTSSM, and BTS can reach on air state due to the fault2001 can’t be cleared.Configuration:FSIH+FZNN T111Customer Impact: StabilityProbability: PermanentSolution / Workaround: Reset BTS by BTSSMImpact to Operator: BTS SW upgrading BTS SW build from RL45 to RL55, BTS can’t reachon air state
3 FLEXI ZONE GENERIC OPEN FAULTS
3.1 BTS site manager: Unexpected Error
Problem report: 60531ESPE05Exists in: LNF7.0_ENB_1407_133_00Correction Target: MPSeverity: C-MinorCustomer Impact: BTS Site manager gives Unexpected Error if user tries to accesscertain commissioning parameter details.Description:[1. Test Scenario Steps]Open BTS site manager and go to BTS commissioning. Open lncel parameters. Hover
mouse pointer over 'Cell Scheduling request periodicity' and select 'show more details' onpop-up window. An 'Unexpected problem' will pop instead of more details.[2. Fault Description]Unexpected Error' seenProbability: PermanentWorkaround: NAImpact to operator: Unable to access parameter detail description.
3.2 Poor UL performance wi th FULLA when compared to EULLA
Problem report: 149066ESPE02Exists in: LNT5.0_ENB_1407_176_00
Correction Target: MPSeverity: C-MinorCustomer Impact: Throughput performance will be lower with FULLA vs. EULLADescription:[1. Test Scenario Steps]High uplink interference[2. Fault Description]LTE1495 (Fast Uplink Link Adaptation) might perform worse than EULLA (EnhancedUplink link adaptation) in scenarios where:- The level of uplink interference is very high- Effective uplink combining algorithm (IRC) is used to cancel the UL intererence.Probability: PermanentWorkaround: Workaround is to not use FULLA in eNB's which have very high level of
Impact to operator: In certain scenarios Fast Uplink Link Adaptation may provide worseperformance than Enhanced Uplink Link Adaptation
3.3 TRS ETH IF Ethernet statistics counter showing wrong values
Problem report: 153992ESPE02Exists in: LNZ5.0_ENB_1407_096_00Correction Target: MPSeverity: B-MajorCustomer Impact: Statistics counter shows random valuesDescription:[1. Test Scenario Steps] Analysis of TRS ETH IF Ethernet statistics[2. Fault Description]TRS ETH IF Ethernet statistics counter shows randomly looking values (in hex they are
FFFFFFFF or FFFFFFFE). There is also mismatch between counting octets and ethpackets. Whole traffic goes through VLAN1001 in the given example.Probability: PermanentWorkaround: NAImpact to operator: Inability to collect and analyze these statistics
3.4 CLPC doesn' t work with VoLTE traff ic
Problem report: 154681ESPE02Exists in: LN7.0_ENB_1407_548_07Correction Target: MPSeverity: B-MajorCustomer Impact: CLPC does not work for intermittent traffic, e.g. VoLTE traffic
Description:[1. Test Scenario Steps]VoLTE traffic[2. Fault Description]The CLPC algorithm has a discontinuous filtering specified which is applied in TTIs inwhich the UE was not scheduled. If the UE is scheduled very seldom, then thediscontinuous update of the averaged power values prevents the filter from measuring thereal power. This will prevent the CLPC from working, no TPCs will be sent to the UE.Probability: PermanentWorkaround: Utilize open loop power controlImpact to operator: If UE VoLTE call is scheduled very seldom then it will prevent CLPCfrom working.
3.5 eNB SM could enable eICIC wi thout btssyncmode
Problem report: 155333ESPE02Exists in: LN7.0_ENB_1407_554_12Correction Target: MPSeverity: C-MinorCustomer Impact: Incorrect enabling of eICIC when not plannedDescription:[1. Test Scenario Steps]eNB had disabled eICIC and wasn't configured in Network synchroniaztion mode. There isno parameter btssyncmod under object BTSSCL.[2. Fault Description]On the commission start page, select BTS and reconfiguration, then click the link "Go to
Radio Network Configuration page" to go to the Radio Network Configuration.
Enabled the eICIC flag under LNCEL object, BTS SM didn't show any error to indicate wehave to configure the BTS Sync mode.
Probability: PermanentWorkaround: Ensure Network synchronization mode is set prior to enabling eICICImpact to operator: Improper/incorrect enabling of Eicic
4 CLOSED PRONTO
Problem ID Title
117746ESPE01[RL55 FSIH CPRI]RRU can't be detected due to BBC receivedevAPI_CPRI_GET_LINK_PARAM_RESP_MSG message status is 0 when flag 275=100 isdisabled
121337ESPE01 [RL55 FSIH][DualMode][BTS auto reset when delete hwf file]
NA05760993 [LNT5.0] [CMCC]Auto reset happens when eNB keeps running on RL55 PT3.2
121703ESPE01 [RL55 FSIH][DualMode][Calibration is NOK after RRU fiber hot remove and insert]
117429ESPE01 [RL55 FSIH]: Parameters sending failed with plan operation failed.
117746ESPE01[RL55 FSIH CPRI]RRU can't be detected due to BBC receivedevAPI_CPRI_GET_LINK_PARAM_RESP_MSG message status is 0 when flag 275=100 isdisabled
119721ESPE01 [RL55 FSIH ][CPRI]BTS can not startup due to FYGH PPS output not generated
119746ESPE01 [RL55_FSMF_CPRI]:There is a ?zombie process? HWRTDLTECpriSExe after BTS reset
119837ESPE01 [RL55][FSMF CPRI][LTE1266]BTS reset didn't triggered after unblocked BTS
120152ESPE01[RL55 FSIH ]:[stability CPRI]:FSIH+FZND dual carrier RRU lost its connection to BBU afterBTS site onair , and fault 0010 happened
121337ESPE01 [RL55 FSIH][DualMode][BTS auto reset when delete hwf file]
121701ESPE01 [RL55 FSIH][DualMode][HWF is not updated after RRU order is changed]
122302ESPE01 [RL55 FSIH+6FZND,S111111]fault1903 can't appear in the SEM after trig it
124760ESPE04 [RL55 FSIH T333][stability]FYGH will occasionally start to do self-survey after BTS reset
126573ESPE04[RL55 FSIH][DualMode][CPRI FZNN/K/L]Occasional Fault 1868, 0010 and BTS auto reset
after do site reset.127032ESPE04 [RL55FSIH CPRI][LBT2766-A]Cannot setup dual carrier or three carrier for FZHP.
151479ESPE02[RL55 FSIH]FYGH GPS pps output can not be generated after self-survey finished/swupgrade/running time
152387ESPE02[RL55 FSIH][LTE1231]Sending parameter failed after configure the object for QCI translationtable operator specific QCIs
152643ESPE02 [RL55 FSIH][LTE1845]Alarm 1868 and 0010 rise after plug in FYGE and BTS auto reset
152662ESPE02 [RL55 FSIH][DualMode][Calibration is NOK Occasionally when remove 190030]
152709ESPE02[RL55 FSIH]Item with beamformingType(SRS beamforming type) is missing whendlMimoMode value is Dual Stream Beamforming while SW upgrade from RL45 to RL55
152798ESPE02[LNT5.0 FSIHI+FZHJ] optical l ink sync to 8X failure after RRU block/unblock onLNT5.0_ENB_1407_444_11
152818ESPE02 [RL55 FSIH CPRI][LTE 1257]BTS auto reset after FYGH module reset
90410ESPE03 [RL55 FSIH CPRI]Fail to block RRU after triggering fault 1925.
60100ESPE05[RL55 FSIH][DM]:T2_11111 dual carrier cell2 can?t onair and proceduralState istimingsUpdated
Disclaimer
The information in this document is subject to change without notice and describes only theproduct defined in the introduction of this documentation. This documentation is intended forthe use of Nokia customers only for the purposes of the agreement under which thedocument is submitted, and no part of it may be used, reproduced, modified or transmitted inany form or means without the prior written permission of Nokia. The documentation hasbeen prepared to be used by professional and properly trained personnel, and the customerassumes full responsibility when using it. Nokia welcomes customer comments as part of theprocess 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 bedefined conclusively and finally in a separate agreement between Nokia and the customer.However, Nokia has made all reasonable efforts to ensure that the instructions contained in
the document are adequate and free of material errors and omissions Nokia will, if deemednecessary by Nokia, explain issues which may not be covered by the document.
Nokia will correct errors in this documentation as soon as possible. IN NO EVENT WILLNOKIA BE LIABLE FOR ERRORS IN THIS DOCUMENTATION OR FOR ANY DAMAGES,INCLUDING BUT NOT LIMITED TO SPECIAL, DIRECT, INDIRECT, INCIDENTAL ORCONSEQUENTIAL OR ANY LOSSES, SUCH AS BUT NOT LIMITED TO LOSS OFPROFIT, REVENUE, BUSINESS INTERRUPTION, BUSINESS OPPORTUNITY ORDATA,THAT MAY ARISE FROM THE USE OF THIS DOCUMENT OR THE INFORMATIONIN IT.
This documentation and the product it describes are considered protected by copyrights andother intellectual property rights according to the applicable laws.
Release Delivery: RL55Product Family: Base Stations / Radio Controllers
Product: Flexi Multiradio BTS TD-LTE
LTE iOMS7.0, Flexi Zone BTSRelease: LNT5.0, iOMS7.0, LNZ5.0
Approval Date: 31-March-2015
Nokia Solutions and Networks is continually striving to reduce the adverse environmental effects of itsproducts and services. We would like to encourage you as our customers and users to join us in workingtowards a cleaner, safer environment. Please recycle product packaging and fo llow the recommendations forpower 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 weoffer, please contact us at Nokia Solutions and Networks for additional information.
Table of ContentsTable of Contents...............................................................................................................................................2 1 Purpose ...................................................................................................................................................1 2 Overview..................................................................................................................................................1
2.1 Other Relevant Installation Instructions.................................................................................................................... 1 3 Preparations ............................................................................................................................................1
3.1 Previous deliveries for the release ................................................................ ........................................................... 2 4 Making a safe copy of the active package ................................................................................................2 5 SW downloading instructions ...................................................................................................................2 6 Special conditions ....................................................................................................................................3
6.3.1 Verified upgrade path in the Lab ........................................................................................................................ 4 6.3.2 Upgrade path list ................................................................................................................................................ 4
6.4 Control PC configuration .................................................................... ..................................................................... . 5 6.5 Flexi Zone Operator tips........................................................................................................................................... 5
6.5.1 S1 link workaround ........................................................... ..................................................................... ............. 5 7 FLEXI Multi-radio special notice while upgrading ......................................................................................5
7.1 Hardware accessories operation notice .................................................................................................................. . 5 7.1.1 FYGH effective identification and scene description........................................................................................... 5 7.1.2 FYGH self survey completed but no pps generated ................................................................... ........................ 7 7.1.3 FYGH self survey process abnormal ................................................................... ............................................... 7 7.1.4 When can replace FYGH with FYGD ............................................................................. .................................... 7
7.1.5 When use GPS antenna combiner .......................................................... ........................................................... 9 7.1.6 FYGH module lost during eNB is running ............................................................ ............................................. 10 7.1.7 FYGH GPS device read timeout during BTS reset ..................................................................... ...................... 10 7.1.8 RL45 and RL55 GPS module name showing ................................................................. .................................. 10 7.1.9 FYGB need do 2times self-survey that self-survey can be complete................................................................ 10 7.1.10 How to verify whether FYGD support TOD....................................................................................................... 10 7.1.11 Distribution site fiber installation suggestion ................................................................... .................................. 11 7.1.12 Delay upgrade chain connection site ................................................................... ............................................. 11
7.2 Special swconfig flag operation.............................................................................................................................. 11 7.2.1 Different site solution whether need necessary flag ......................................................................................... 11 7.2.2 Remove force 8x speed setting before upgrade ............................................................. .................................. 12
7.3 Special compatibility configuration for upgrade .................................................................... .................................. 13 7.3.1 Mitigation configuration need update for F band RRU ................................................................ ...................... 13 7.3.2 Some DRX related parameters need update before upgrade .......................................................................... 14
7.3.3 Add parameter of srsSubfrConf on RL45 before upgrade ..................................................................... ........... 14 7.4 Site startup and RRU detect issue notice............................................................................................................... 14 7.4.1 Site auto reset after upgrade ................................................................... ......................................................... 14 7.4.2 RMOD report 0010 and 2001 alarm while first running on RL55 ........................................................... ........... 15 7.4.3 Reference clock missing in startup 4153 ............................................................. ............................................. 15 7.4.4 BTS synchronization is missing (4160) is reported during startup after SWDL ................................................ 15 7.4.5 RRU can’t be detected ..................................................................................................................................... 15 7.4.6 Occasional 0010 issue on OBSAI factory load upgrade ............................................................. ...................... 15 7.4.7 eNB stays commissioned ................................................................................................................................. 15 7.4.8 MOAM crashed due to Bus error during BTS startup process.......................................................................... 16
7.5 Abnormal running fault and issue notice ................................................................... ............................................. 16 7.5.1 FSI5 disconnected after BTS restart................................................................................................................. 16 7.5.2 EIF6 disconnected after upgrade ..................................................................................................................... 16 7.5.3 Site should not show FYG module ................................................................................................................... 16 7.5.4 System reply activationError when full plan active during auto-configuration ................................................... 17 7.5.5 Snpashot can’t be saved after BTS block with triple carrier configuration ........................................................ 18 7.5.6 Fault 1911 is reported when BTS is connected with 20KM fiber ...................................................................... 18
7.5.7 Fault 4176 maybe rise while first save snapshot ............................................................ .................................. 18 7.5.8 Activation failed when try to delete non-connected RRU using recommission ................................................. 18 7.5.9 'Read only' error code for RET occurred after upgrade .............................................................. ...................... 18 7.5.10 Cell-x stucked in the preparationDone status after site reset ........................................................................... 18 7.5.11 Cell-x in not calculated state............................................................................................................................. 18 7.5.12 Activating parameters failed .................................................................... ......................................................... 18
8.1.1 Special matters stated .................................................................. .................................................................... 19 8.1.2 Factory load to RL55_P8 by NetAct with FSIH+FZFD........................................................................... ........... 19 8.1.3 Factory load to RL55_P8 by BTSSM with FSIH+FZFF-e ...................................................................... ........... 33
8.2 Last big release to target version .................................................................. ......................................................... 37 8.2.1 Special matters stated .................................................................. .................................................................... 37 8.2.2 RL45_MP2.0 Upgrade to RL55_P8 by BTSSM with FSMF+FZFE DM ............................................................ 37
8.2.3 RL45_MP1.0 Upgrade to RL55_P8 by NetAct with FSIH+FZHA...................................................................... 42 8.3 Early release to target version ............................................................................................................................... 45 8.3.1 Special matters stated .................................................................. .................................................................... 45 8.3.2 RL55_PCD2.0 Upgrade to RL55_P8 by NetAct with FSMF+FZHA .................................................................. 45 8.3.3 RL55_PCD2.0 Upgrade to RL55_P8 by BTSSM with FSIH+FZFF-e ............................................................... 50
8.4 Flexi Zone Micro BTS TD-LTE ........................................................... .................................................................... 52 8.4.1 First installation and commissioning .................................................................... ............................................. 52 8.4.2 Build information ............................................................... ..................................................................... ........... 52 8.4.3 Project upgrade ................................................................ ..................................................................... ........... 52
8.5 iOMS ............................................................... ..................................................................... .................................. 54 8.5.1 Upgrade from iOMS6.0 (R_GOMS6_1.113.1.0 Corr34) to iOMS7.0 (R_GOMS7_1.3.2.0 corr13)Error! Bookmark not d8.5.2 Upgrade from iOMS7.0 (R_GOMS7_1.3.2.0 corr13) to iOMS7.0 (R_GOMS7_1.3.2.0 corr25)Error! Bookmark not defi
9 Checking of the package consistency .....................................................................................................63 9.1 Flexi Multi-radio ........................................................... ..................................................................... ...................... 63 9.2 Flexi Zone .............................................................................................................................................................. 64
10.1.1 Rollback to old release ..................................................................................................................................... 64 10.2 Fallback.................................................................................................................................................................. 65
10.2.1 Fallback to old release...................................................................................................................................... 65 10.3 Flexi Zone Rollback/Fallback ................................................................................................................................. 65
Please study the content of the library carefully and follow on detailed procedures described inthe document. The instruction for installation and upgrade of certain entities will be specified inthis document. During the execution of the procedure user will be asked to stop following theofficial Customer Documentation and execute steps mentioned here.
2.1 Other Relevant Installation Instructions
All LTE Customer Documentation, including standard installation procedures, is accessiblethrough NOLS
[1] in the section “Long Term Evolution Information”
https://online.portal.nsn.com
Nokia Solutions and Networks Long Term Evolution Information Center[2]
https://online.portal.nsn.com
It is very important to check if new Change Deliveries are available – they may contain newerversion of the documents
3 PREPARATIONS
Hardware used for the installation should be integrated according to the hardware installationguide and all necessary cabling should be already done. Necessary documents can be found inthe section “Install and commission” in the Customer Documentation library
[2].
Operator should check and verify these following steps:
Step1 verify whether all hardware is in this version support scope, see thesection<Chapter 6.1 Supported Hardware >;
Step2 check current eNB’s site configuration and SW configuration are supported bynew SW release , refer to release notes file;
Step3 check current eNB’s alarm;
Step4 backup the commissioning file.
Step5 check control PC disk space which BTSSM is installed, at least more than 260MB;
Step6 check new eNB version number;
Step7 There is no swconfig.txt in eNB flash by default, need add special flag in caseneed capture logs.Only for CMCC CPRI configuration, please read detail of c hapter7.2.1.
To enable usage of SON features, some preparation steps must be taken. They are described in
Customer Documentation library in section “Functional Area Description-Operability-
1. Factory load UpgradeIt doesn’t need copy the environment data in the factory load uploading, there is no SCFfile in the factory HW, and the active and passive version are both factory package.
2. By SiteManager UpgradeBTS is in fallback status when software download is failure and the SW upgrade is neededto again. If it must backup then configuration file is enough.
3. By NetAct UpgradeIf meet any errors during system upgrade, then fallback/rollback to original version will besupported, if it must backup then backup commission file is enough.
5 SW DOWNLOADING INSTRUCTIONS
Software for the ENB can be downloaded from NOLS server:
As example, the detail steps for 3 typical upgrade paths are described in chapter 8.1 , 8.2 and8.3 , following upgrade paths are supported “Factory load package” /“RL45_LNT4.0_P8/PP0.0.1/MP1.0/MP2.0” / “RL55_LNT5.0_PCD1.0/PT3.2/P7.2/PCD2.0”Upgrade to “RL55_LNT5.0_P8”
6.4 Control PC conf iguration
If Control PC is directly connected to eNB by LMP interface, PC must be set up with ip address &subnet as follows:IP address: 192.168.255.126Network mask: 255.255.252.0
If Control PC is remote connected to eNB, you just make sure that it can access the M-plane
application IP address of the eNB.
If you use BTSSM to do SWDL, please make sure the matching BTSSM has been installed well.
Any failure about download file, we suggest to disable the firewall and anti-virus software on thecontrol PC.
6.5 Flexi Zone Operator tips
6.5.1 S1 link workaround
An issue might occur where “S1 link failure” alarm will be visible after upgrade.In order to prevent that, both FZM and switch/router to which FZM is connected have to have thesame link speed configured, i.e. both must be set to negotiate, or both must be set to a specific value.
Previously only forced mode was supported. Issue is seen because there is a mismatch between theFZM and the media converter/switch/router. The FZM will be defaulted to auto detect, however it mustbe changed to forced mode if auto detect is not supported by the other side (Media converter, switchetc.)
Workaround: Site Manager -> TRS Hardware -> EIF1: Speed and Duplex: set to "1000 Mbit/s fullduplex" instead of Autodetect.
7 FLEXI MULTI-RADIO SPECIAL NOTICE WHILE UPGRADING
7.1 Hardware accessories operation notice
If operator uses “internal GPS FYGH” on FSIH, please read this sub chapter carefully foroperation and trouble shooting. And other related hardware installation and configuration notice also should be pay attention to.
7.1.1 FYGH effect ive identi ficati on and scene description
Usually in the field, the GPS signal is worse than lab and cable is longer than 5m. Operator shouldset manually commission to set some necessary parameters of FYGH.
Method-1: online
• After RRU has been detected, run manully commission by “planed commission type” baseon your “exsited BTS commission file”;
• At last, save BTS commission file as SCFC_xx.xml;
• Upload to site and power off/on;
• After site reset, FYGH shoulde begin to do self survey process.
If operator make configuration of FYGH as above, but it still can’t begin to do self survey process,you can refer chapter7.1.4 to check your current environment of GPS signal quality whether it isapplicable for using FYGH.
# =========================antenna status=======================================# 1 DDAL_POWER_GPS_ANT_INIT, /*!< antenna is still in init state*/# 2 DDAL_POWER_GPS_ANT_ACTIVE, /*!< antenna power on successfully */# 3 DDAL_POWER_GPS_ANT_OPEN, /*!< antenna circuitry open detected */
# 4 DDAL_POWER_GPS_ANT_SHORT, /*!< antenna ci rcu itry short detected */
So that please makes sure there is only one site that set parameter of “internal GPS antenna LNA
power supply” to true.
7.1.6 FYGH module lost during eNB is runn ing
If issue happen, cell will disable and service interrupt when eNB is running.
Operator can do “reset site” for recover.
7.1.7 FYGH GPS devic e read timeout during BTS reset
While you cold/hot reset site, maybe all the cells can’t reach on air status with fault 4153 & 4011 & 4072.Please reset by SEM again for recover.
If reset not ok after 3 times, do as following steps:
• Backup the commission file SCF
• Rollback to previously SW build
• update SW to make the P8 SW is overwritten by RL55_PCD2.0
• Update to P8 SW again
• Commission the BTS with backup SCF if commission error in found
7.1.8 RL45 and RL55 GPS module name show ing
While customers have used FYGB/FYGD in RL45, it is all showing as FYGA.Once you upgrade to RL55 later, they will be displayed correctly.
7.1.9 FYGB need do 2times self-survey that self-survey can be complete
After deleted FYGB store position information, FYGB will start to do self-survey. When the first self-surveyprogress to 100% it will be re-do self-survey again. This abnormal issue only needs more time to complete; it’s about 2* 2000 seconds.The generally one round of self-survey time is 2000 seconds under the condition of good signal.
If FYGA/FYGB/FYGD can offer TOD info to eNB, it’s best condition. But if it does not have this capabili ty,RL55 software will try to get TOD from NTP function.
But in field site setup, some FYGD can’t support TOD offer, so that please check this issue and then replacethem.
We usually via a button label serial number and product characteristics to distinguish between the things,please according to the identification guide to complete the further confirmation.
If you have this requirement, please contact with your related GS/NPI interface man for detail technicaldocument.
7.1.11 Distribution site fiber installation suggestion
If field setup site with distribution connection topology, please notice the fiber length between BBU and firstRRU, second RRU…etc, it’s suggestion that operator install the first step fiber length to max.
If not, it maybe causes some strange fiber fault or alarm.
7.1.12 Delay upgrade chain connection site
For FSMF+FSMF chain connection topology, please don’t upgrade to this version until RL55_MP1.0.We will release feature “LTE1710/CRL6621” by using “SYNC IN and SYNC OUT” to offer ToD.
7.2 Special swconfig flag operation
By default, the swconfig.txt of customer sites should have empty content, but if we hand out this chapter, youmust follow guide operation as we description to avoid some strange fault or issues.
7.2.1 Different site solut ion whether need necessary flag
Open swconfig.txt and disable “0x19000c”, then ftp upload back to fs
RRU telnet every RRU;
set command “rad -pw 0xED 0” / “rad -pw 0xEE 0”;
set command “rad -r 0” again and verify result.
Step3: after above setting, do site reset, and eNB should be on air. Then you can begin to do SWDL to target
RL55_P8 version.
7.3 Special compatibility configuration for upgrade
These following issues and operation notices are so important for operator while upgrade from RL45 to RL55.Please attach importance to them.
7.3.1 Mitigation configuration need update for F band RRU
In particular for CMCC project, as roadmap,"tddSpecSubfConf=7" is not supported in RL55, however it'ssupported in RL45. So for this BTS configured with 2:7 needs to perform some action before upgradeoperation.
Just take SEM for example, operation also can change thought to the NetAct for multi BTS.
These two parameters should be update as following snapshot showing:
• tddSpecSubfConf: change it from “7” to “5”;
• maxNumUeDlDwPTS need also to been changed due to change of tddSpecSubfConf.
7.3.3 Add parameter of srsSubfrConf on RL45 before upgrade
Because it’s mandatory in RL55 while optional in RL45.So if not configured in RL45, then after upgrade to RL55, BTS will report invalid parameter.It’s suggested that operator add this parameter in RL45 SCF before upgrade to RL55.
These following issues and operation notices are so important while site startup on RL55_P8.If you met some abnormal fault issues, please refer to it and try to recover site.
7.4.1 Site auto reset after upgrade
If you meet some times site auto reset 2 times issue after eNB is first running new version, please waitpatiently, it will recover.
It is because that FPGA or Firmware do upgrade then restart.
7.4.2 RMOD repor t 0010 and 2001 alarm while first running on RL55
If you upgrade site from RL45 to RL55, while first running on RL55 version, RMOD maybe report 0010 and2001 fault especially site with large capacity and complex configuration.Operator can do “reset site again” for recover.
7.4.3 Reference clock missing in startup 4153
After reset BTS from site manager, Reference clock missing in startup 4153, RF cannot be detected and cellcannot on Air.Operator can do “reset site” for recover.
7.4.4 BTS synchronization is missing (4160) is reported during startup after SWDL
After SWDL to target RL55_P8, BTS synchronization is missing during startup (4160) maybe reported. Operators can do “reset site” for recover.
7.4.5 RRU can’ t be detected
It maybe some condition while issue happen on site startup:
• After site reset, 4011 and 0010 alarm arise, and RRU can’t be detected.Operators can do “reset site” for recover.
7.4.6 Occasional 0010 issue on OBSAI facto ry load upgrade
For OBSAI site solution (FZHA,FZHJ,FZHJ-B), if meet occasional 0010 issue and if reset more than 3 timesstill not able to recover.Try to delete “hwf.bin.giz” in, eg /ffs/fs2/config or /ffs/fs1/config , (Depending on which is active partition)
7.4.7 eNB stays comm issioned
After startup eNB stays commissioned state for long time, no active alarms.Operators can do “reset site” for recover.
7.4.8 MOAM crashed due to Bus error during BTS startup process
MOAM crashed due to Bus error (reason: 128 'unknown').Operators can do “reset site” for recover.
7.5 Abnormal runn ing fault and issue notice
These following issues and operation notices are so important while site running on RL55_P8.If you met some abnormal fault issues, please refer to it and try to recover site.
7.5.1 FSI5 disconnected after BTS restart
If using FSI5 for transport connection, it maybe link fail after BTS restart, as result site S1 link lost.Please change to “use FSI1~FSI4 as S1 interface” or “disable the FSI5 and then enable it again” when this
issue occur.
7.5.2 EIF6 disconnected after upgrade
While operator set EIF6 of FSMF force 1000Mbit/s full duplex mode, after upgrade to target version, it maybedisconnected.Operators can do “local reset site” for recover.
7.5.3 Site should not show FYG modu le
For DM site, when it startup with RL55 SW version, although site can on air, but operator still seeFYG module in SEM.
It does not affect site on air and normal traffic and will be fix later.
7.5.4 System reply activationError when full plan active during auto-configuration
While operators do auto-configuration process, if you met this warning as following snapshot, please ignoreas it does not affect that BTS get commission file from NetAct.
7.5.5 Snpashot can’t be saved after BTS block with triple carrier configuration
While operators use triple carrier configuration of FSIH+FZHJ, after you block cell, then snapshot saveoperation maybe fail.
7.5.6 Fault 1911 is reported when BTS is connected wi th 20KM fiber
For OBSAI+FZHA, fault 1911 is reported while under this condition.The length of the fiber between BBU and RRU are limited to be less than 20 KM.15KM is the recommended.
7.5.7 Fault 4176 maybe rise while first save snapshot
Please ignore the fault 4176 when do first save snapshot operation and save it again.
7.5.8 Activation failed when try to delete non-connected RRU using recommission
RRU is not connected to eNB and 0010 alarm is reported in BTSSM, delete non-connected RRU usingrecommission failed.Operator can “upload new SCFC to eNB manually” for recover.
7.5.9 'Read only ' error code for RET occurred after upgrade
For FSIH using, while after upgrade eNB from RL45MP2 to RL55 P8, one error message will be displayedon BTSSM GUI. Operators can do “Do RET calibration or reset eNB” for recover.
7.5.10 Cell-x stucked in the preparationDone status after site reset
After reset BTS from site manager, there are 2 cells which are not OnAir and can’t be used.Operators can do “reset site” for recover.Notice: it need confirm in IMviewer log tool, please contract with support engineer for help.
7.5.11 Cell-x in not calculated state
One of cell can't onair without any alarm reported, from tool “IMCommander log” we can see cell in notcalculated state.Operators can do “reset site” for recover.Notice: it need confirm in IMviewer log tool, please contract with support engineer for help.
7.5.12 Activating parameters failed
Change parameters which need reset eNB, activating parameters failed.Operators can “delete hwf file manually and reset eNB” for recover.
8 RELEASE DELIVERY UPGRADE INSTRUCTIONS
Notice:Please ignore the eNB sw version in the picture below. Although it’s not “LNT5.0_ENB_1407_555_03”. All upgrade operation steps are all the same as generally operation.So that you should pay more attention to the last chapter (7.SPECIAL NOTICE WHILEUPGRADING), there are some known issues and workarounds for you refer to.For every topical upgrade paths and methods, we only take 2~3 scenes for example.
For OBSAI site solution, may be met issue as chapter7.4.6 description.For CPRI site solution, operators maybe have a lot of chance to meet FYGH issues, please refer tochapter7.1.x.
8.1.2 Factory load to RL55_P8 by NetAct wi th FSIH+FZFD
8.1.2.1 Test environment
Factory load upgrade to LNT5.0 P8 will use NetAct Auto-Con Procedure. This is main work flow using auto-connection and auto-configuration to upgrade FSIH from factory load to LNT5.0 P8 version. The workflow
covers system upgrade procedure from factory load startup to FSIH upgrade to LNT5.0.
FSIH.A101+FZFD.A101The FSIH.A101 factory load version is LNT4.0_ENB_1311_512_00.
8.1.2.2 Preparation
OMS version R_GOMS7_1.3.2.0.release_oms.corr26
DHCP server preparation:Since the Auto Connection trusts the use of standard DHCP (Dynamic Host Configuration Protocol) services,the DHCP servers are pre configured with suitable options and Nokia-eNB specific data (vendor-specificattributes) such as:
• IP address of the Certificate Server that is the operators' Registration Authority or Certificate Authorityproviding the operators' public key infrastructure (PKI) services. (Optional)
• IP address of the VPN/Security Gateway protecting the responsible NetAct Operations, Administrations andMaintenance (OAM) system (Optional)
• IP address of Dedicated OMS (Mandatory)The definition of the vendor specific extension is vendor (Nokia) specific. The Nokia vendor parameterdefinition is based on the TLV (Type-Length-Value) approach.
43 10 0 1 4 A B C D
Option Total TLV OMS OMS OMS IP
Type Option length identifier param type param length <-------------------------------------->
Note: DHCP shall not bind MAC address during factory load upgrade procedure.
Plan preparationHere is an example for prepare the BTS configuration file from NetAct.Note: How many eNBs you choose during export plan files depends how many eNBs you want to plug intogether at one time. Below example will upgrade three eNBs together, so it chooses three eNBs from currentNetAct, and you can choose any eNBs from your current networks, which HW info is match with pluggedones.
Step1: Export eNB configuration file from NetAct for new eNB file plan.
Step 2: Create new plan file for eNBsCreate new plan file with exported plan depending on the new side dedicated configurations, At least MRBTSID, LNBTS ID, MCC, MNC, IP, Site ID, PCI… All the parameters related BTS configuration depends on yourrequirement.
iOMS preparation: A dedicated OMS should be defined in NetAct, the OMS should be same as defined in DHCPserver.
Step 1: Create a CM plan via CM Editor, and select the dedicated OMS, change parameter “Auto
Step 2: Upload LNT5.0_ENB_1407_555_03_release_BTSSM_downloadable_wo_images by using “Add
NetAct Files…”.
Note: If uploaded using local directory, you may need to copy the BTSSW to NetAct local server
Step 3: When the software package is ready for import, click the “Details” to edit the software packageversion id. Use the name like “LNT5.0_ENB_1407_555_03”.
Individual PREBTS plan:If using higher PREBTS configuration from CM editor tool to download OMS PREBTS configuration, pleasesee the the plan as bellow:
Step 1: Provision this plan via CM Operations Manager.
Step 2: Add below parameter into site plan under MRBTS MO as customer required (following value forparameter just for reference)Mandatory Need:<p name="autoConSiteId">TDLTE807</p>
Note: The parameter can be added via CM Editor also if using manual import way for eNB plan.Common site
configurations for each site configuration with specific transmission parameter for each eNB need to beprepared offline for NetAct. Backup commissioning file by BTS Site Manager cannot be used for the
Step 2: Open workflow engine in CM Operations Manager, and select “Auto configuration – eNB - planning”.
Step 3: Press start for “eNB - Create configuration plan”, and fill plan name, and correct directory for eNBplan. If eNB plan is using UI values, then change “UI values” to Yes. If eNB plan is using internalvalues, then keep “UI values” to No.
Step 4: Press “Start” button, and wait for plan import finished.
Note: If auto-connection parameter or target SW package build is not in eNB plan, they can be manually filledvia CM Editor. Go to CM Editor, and open the created plan in step 2, find the created MR-BTS object,
and fill "autoConfSWPackage", “AutoConnSiteID”, and “AutoConnHWID” manually.
Step 5: Press start for “eNB - Validation configuration plan”, and press “Start” button, and wait for validation
finished.
Note: if validation fails, go to operation history of CM Operations Manager, and view feedback of the failedplan to check if any parameter is set wrong. Go to CM Editor, and open the created plan in step 2, find
and correct the wrong parameter. Then re-do the step again until it’s finished with success.
Step 6: Set Polling mechanism for auto-configuration auto-triggerIf auto-configuration need to be auto-triggered, a scheduled polling can be set, so that NetAct willautomatically trigger auto-configuration continuously in a defined interval.
Step7: Open SON Scheduler in Configuration page, and click setting under Auto Configuration menu.
Step 8: Go to polling mechanism tab, and select “Alive” option, and set the interval, and save theconfiguration.
8.1.2.3 eNB auto-connection and configuration
Step 1: Power on FSIH, and wait for startup. eNB will come up with Uncommissioned status. Auto-connection
is triggered automatically. eNB will send CCN message when auto-connection is done and it’s readyfor auto-configuration.
Step 2: Open CM Editor and open the created plan, and check parameters “Auto configuration blocked” and“Autoconfiguration required by multiradio flexi BTS” under MRBTS. If “Auto configuration blocked” is set false,
and “Autoconfiguration required by multiradio flexi BTS” is set true. It means eNB is ready for auto-configuration.
Step 3: Open workflow engine in CM Operations Manager, and select “Auto configuration – eNB – additionaloperation”. Press start of “eNB – Auto configuration trigger”, and press “Start” button to trigger auto-configuration procedure.
Note: If polling mechanism is set, this step can be skipped.
Step 4: NetAct will automatically download required SW package to eNB. eNB will activate the SW packageautomatically when download is finished, and reset.
Step 5: eNB startup with LNT5.0SW.
Note: Due to no configuration convert from factory build LNT4.0 SW to LNT5.0 SW, TRS parameter which
Any abnormal of internal GPS issue, please refer to chapter7.1.x.
8.2 Last big release to target version
8.2.1 Special matters stated
For all RL45 site, please read carefully about chapter7.3.For OBSAI site solution, please extra notice “remove force 8X speed setting” issue as chapter7.2.2.For CPRI site solution, no special statement.
8.2.2 RL45_MP2.0 Upgrade to RL55_P8 by BTSSM with FSMF+FZFE DM
Active partition: RL45_MP2.0Passive partition: any version below RL45_MP2.0LTE eNB is on air.
For F band site solution, please refer to chapter7.3.1 while operators start to upgrade from RL45 to RL55.For DRX enable site, please refer to chapter7.3.2 while operators start to upgrade from RL45 to RL55.For BTS report invalid parameter issue of srsSubfrConf, please add this parameter in RL45 SCF beforeupgrade to RL55.
Step1: Pre-install the corresponding BTSSM version for these eNB packets on your local computer.
Step2: Check current eNB SW version, and eNB status is on air without alarm. And check TDS carrier and local cell status are all ok.
Remark: if need of TDS upgrade, please refer to TDS documents and TDL corresponding release notes.
For F band site solution, please refer to chapter7.3.1 while operators start to upgrade from RL45 to
RL55.For DRX enable site, please refer to chapter7.3.2 while operators start to upgrade from RL45 toRL55.For BTS report invalid parameter issue of srsSubfrConf, please add this parameter in RL45 SCFbefore upgrade to RL55.No special flag for CPRI configuration, some detail info you can refer to chapter7.2.1. Any site error show FYG module, please refer to chapter7.5.1.
8.2.3 RL45_MP1.0 Upgrade to RL55_P8 by NetAct with FSIH+FZHA
8.2.3.1 Test environment
FSIH.A101 + FZHA + FYGASite solution configuration: S1 OBSAI SM
8.2.3.2 Preparation
For DRX enable site, please refer to chapter7.3.2 while operators start to upgrade from RL45 to RL55.For BTS report invalid parameter issue of srsSubfrConf, please add this parameter in RL45 SCF beforeupgrade to RL55.
Step1: Check current eNB SW version, and eNB status is on air without alarm.
For DRX enable site, please refer to chapter7.3.2 while operators start to upgrade from RL45 to RL55.For BTS report invalid parameter issue of srsSubfrConf, please add this parameter in RL45 SCF before
upgrade to RL55.
8.3 Early release to target version
8.3.1 Special matters stated
For all versions before RL55_P8, please notice “swconfig should be empty content” issue as chapter7.2.1.
8.3.2 RL55_PCD2.0 Upgrade to RL55_P8 by NetAct wi th FSMF+FZHA
NetAct side preparation check:Step 1: Open Software Manager, and select “Software Archive”. Select “MRBTS” as the MO type, then click“Add software package …”
Step 2: Upload target eNB software packet by using “Add NetAct Files…”or “Add Local Files”.
No special flag for CPRI configuration, some detail info you can refer to chapter7.2.1.
8.4 Flexi Zone Micro BTS TD-LTE
8.4.1 First installation and commissioning
The commissioning procedure of the Flexi Zone Micro BTS TD-LTE is described in the document“Commissioning Flexi Zone Micro BTS LTE” [3].Please be aware that BTS Site Manager shall be updated before the BTS SW.
System upgrade is described in customer documentation "LTE System Upgrade" [7].
IMPORTANT NOTE:
This document does not include upgrade paths for FWND hardware. Please refer to NPI MOPValidated document available from CT.
Upgrade path from older loads (RL55FZ PT1 & PT2) to newer loads (RL55 PT2.5 and above),contains an interim step which requires RL55FZ_PT3 (LNZ5.0_ENB_1407_103_00) installation.More information you can find in related RL55FZ PT3 Release Upgrade instruction document.
In RL55FZ release, there are introduced incompatibilities that make post PT2.5 laodsunloadable by older software releases (RL55FZ PT1 and PT2). There is a HIGH RISK ofrendering the unit unusable after SW Rollback/Fallback. To avoid this issue intermediate stepneeds to be taken. The intention is to clear the incompatible passive partition and install acompatible release.
Flexi Zone BTS may reset additional one or two times after upgrade to intermediate load andalso after Rollback. This may lengthen the time necessary for eNB to come into service. This isknown issue. Additional workarounds not needed.
Uncomissioned upgrade path from factory load LNZ50_ENB_1407_005_00 contains twointerim steps which require LNZ5.0_ENB_1407_022_01 and LNZ5.0_ENB_1407_103_00installation.
Background:
• LNZ50_ENB_1407_005_00 factory load had a Bug (FZBTSOM-251) which was fixed inthe LNZ5.0_ENB_1407_022_01 load. It was causing upgrades to fail to the new loadswhich contain new RL55 content.
• LNZ5.0_ENB_1407_103_00 is required because of release incompatibilities describedalready above.
When a site is in uncommissioned state and a user tries to upgrade using BTS Site Managerwhile connected via the LMP, there is a small chance that site manager connectivity drops andthe user has to attempt the upgrade again. Plug and Play procedure is not impacted. OnceTransport is commissioned (auto-connection and/or auto-configuration triggered by NetAct),that problem goes away and the user can use the LMP for upgrades w/o issues.
NOTE: The issue is not visible while connected via Bluetooth.
Checking active/passive SW version:Net Act: Software Manager Network Status MO type:”MRBTS” -> Select your MRBTS ->
Synchronize
8.4.3.1 Supported upgrade paths for FWHE (FZM is in commissioned state)
Upgrade paths described in this section are related only to FWHE HW.
Following upgrade paths to LNZ5.0 1.2 PD are suppor ted (FZM is commissioned/onAIR):
Please access it from here:https://online.portal.nsn.com/SWD/?access_key=MTEzODM1
Note: For iOMS upgrade path is from iOMS6.0 (R_GOMS6_1.113.1.0 Corr41) to iOMS7.0
(R_GOMS7_1.3.2.0 corr22), then from iOMS7.0 (R_GOMS7_1.3.2.0 corr22) toiOMS7.0(R_GOMS7_1.3.2.0 corr28).
Remark 1:
If upgrade/update procedure is executed remotely it is recommended to have additional remoteconnection to Standard Integrated Lights-Out (iLO) management functions for HP ProLiantBlade via iLO management port.iLO allows additional access to blade server serial, text-based console. It gives possibility tomonitor and restart blade even when standard access is not available.
Remark 2:
Possible system crash and continuous reset during major LTE iOMS SW upgrade commit phase
iOMS system may be affected by I/O buffer overload which results in kernel crash and systemreset. If this happens during MSU (Major Software Upgrade) commit phase it will cause outageand continuous reset of iOMS.
To prevent I/O buffer overload before MSU commit phase it is advised to change maximumavailable speed for synchronization to 15000.
To reduce RAID synchronization speed please execute following command from root account:# echo “15000” > /proc/sys/dev/raid/speed_limit_max
To check if change was successful please execute:cat /proc/sys/dev/raid/speed_limit_max
More details will be provided in Technical Support Note:TS-LTE_iOMS-SW-0017: Possible system crash and continuous reset during major LTE iOMSSW upgrade commit phase
8.5.1 Upgrade from iOMS6.0 (R_GOMS6_1.113.1.0 Corr41) to iOMS7.0 (R_GOMS7_1.3.2.0 corr22)
8.5.1.1 Software requirements for upgrade procedureDownload the following MSU file from NOLS upgrading from R_GOMS6_1.113.1.0 software levelto the R_GOMS7_1.3.2.0 software level:
MSU_GOMS6_1.113.1.0.c29_42orGOMS6_1.107.1.0.c24_45_to_GOMS7_1.3.2.0.c22_HW.BLG6Gen8.zipThe contents of the <MSU image> file is the asmurt_std directory containing:MSU_GOMS6_1.113.1.0.c29_42orGOMS6_1.107.1.0.c24_45_to_GOMS7_1.3.2.0.c22_HW.BLG6Gen8.tgz;targetBD_GOMS6_1.113.1.0.c29_42orGOMS6_1.107.1.0.c24_45_to_GOMS7_1.3.2.0.c22_HW.BLG6Gen8.xml;targetBD_GOMS6_1.113.1.0.c29_42orGOMS6_1.107.1.0.c24_45_to_GOMS7_1.3.2.0.c22_HW.BLG6Gen8.xml.md5;omsswm_major;data.tgz;partitionsSchema.tgz;
8.5.1.2 Upgrade OMS MSU image with the use of AMSURT from CLI via SSH
8.5.1.2.1 Installing upgrade images
8.5.1.2.1.1 Transferring upgrade image to OMS
1. Remove all unnecessary files from the /var/mnt/local/backup and check the/var/mnt/local/backup directory size with df -h commandMSU may be transferred to OMS using SFTP, SCP FTP or USB stick.
2. MSU packages should be copied to /var/mnt/local/backup/ as in this directory usually is alot of free disk space.
3. Go to the MSU_GOMS6_1.113.1.0.c29_42orGOMS6_1.107.1.0.c24_45_to_GOMS7_1.
3.2.0.c22_HW.BLG6Gen8 directory.
4. Unpack the MSU package file with unzip command.
And execute the following command to verify readiness for the upgrade procedure (for example,targetBD xml conditions and md5 sums),
# ./omsswm_major --check targetBD_*.xml
* In case if the BIOS version is incorrect, proceed to “Upgrading OMS BIOS” in iOMS upgrade
instructions from NOLS.
8.5.1.2.1.2 Installing MSU image in one step (Full Mode)
In the Full Mode, the MSU image file installation is performed totally hands-free, and there is nointerraction with the user. The activation is done automatically, and the OMS reboots
automatically when the installation is done.Execute the following command to start the installationin the Full Mode:# ./omsswm_major --full --noNetActchecking targetBD_*.xmlUse the --noNetActchecking switch to ignore all errors related to connection with NetAct
8.5.1.2.1.3 Installing MSU image in two steps (MSU Installation Mode)
In the MSU Installation Mode, the MSU image file installation is performed in two steps. The userinterraction is needed to start the conversion and activation.Execute the following command tostart the installation in the MSU Installation Mode:# ./omsswm_major targetBD_*.xmlNote that # ./omsswm_major targetBD_*.xml is equivalent to#./omsswm_major --msu_installation targetBD_*.xml
Execute the following command to convert and activate the new software installation:# ./omsswm_major --conversion_activation --noHLF targetBD_*.xmlUse the --noHLF switch to ignore all High Level Fallback errors.
8.5.1.2.1.4 Installing MSU image in multiple steps (Manual Mode)
Execute the following command to check targetBD xml, md5 sums, and so on# ./omsswm_major --check targetBD_*.xmlExecute the following command to break the disk mirroring:# ./omsswm_major --separate --disk <disk name>Execute the following command to start the installation:# ./omsswm_major --install targetBD_*.xmlExecute the following command to convert the data:
Execute the following command to activate the new software installation:# ./omsswm_major --activate --noHLF targetBD_*.xmlUse the --noHLF switch to ignore all High Level Fallback errors.
8.5.1.2.2 Verifying Major Software Upgrade
If the new software installation has been activated, then check if the Major Software Upgradeprocess has finished successfully.
1. check if the MSU process ended successfully.Execute the command:# omsswm_helper –e
2. Check if any elements are connected through the southbound interface.Execute the command:# ztopocli -lc
3. Check the status of recovery groups, recovery units, processes, and coredumps.Execute the command:# zstatus -d –c
4. Check the last successful registration to NetAct.Execute the command:# fsnwi3ctl -iResult
Example printout:# fsnwi3ctl -iGLB_SYSTEM_ID=NE-OMS-341NAR_LAST_REG_ACCOUNT_TYPE=MAINNAR_LAST_REG_OUTCOME=SUCCESSNAR_LAST_REG_TIMESTAMP=2014-03-05T08:57:28+0100NAR_ACCOUNT_NAME_MAIN=nwi3systemNAR_ACCOUNT_NAME_FALLBACK=
8.5.1.2.3 Committing system to new installation
Execute the following command to commit the system to the new installation,# omsswm_major --commit
NOTICE: The rollback is no longer possible after the commit step.
8.5.1.2.4 Performing Major Software Upgrade rollback
1. Execute the installation cutoverThe current live disk is the upgrade disk. Executing the installation cutover for the secondtime means restarting the system with the old installation; that is, separating the upgradedisk from the system and cancelling the separation of the other disk that contains the oldinstallation.Use the following command to execute the installation cutover:# omsswm_major --rollback
This command automatically initiates the OMS restart. Note that the OMS can restart twice.
Check OMS status via command: # fshascli -s /,If the administrative state is locked, thenexecute the following command:# fshascli -un /
2. Commit system to old installation.To make the system run again with a full redundancy, you must finalize the rollbackprocedure and commit the system back to the old installation.Execute the command:# omsswm_major –commit
8.5.1.3 Upgrade MSU image with the software manager of NetAct
8.5.1.3.1 Transferring upgrade image to NetAct
1. Open Software Manager, and click the “Add software package” from “software Archive” item
8.5.2 Upgrade from iOMS7.0 (R_GOMS7_1.3.2.0 corr22) to iOMS7.0 (R_GOMS7_1.3.2.0 corr29)
NOTICE: the correction can be upgrade after MSU upgrade with executed
command“omsswm_major –commit”
1. Install 1 correction level.
Files needed for the update are:targetBD_R_GOMS7_1.3.2.0.release_oms.corr23.xmlR_GOMS7_1.3.2.0.release_oms.corr23.tar
Install correction and create new SW Set (new SW Set will be passive):omsswm_install --full targetBD_R_GOMS7_1.3.2.0.release_oms.corr23.xml
Activate SW Set:omsswm_activate --full targetBD_R_GOMS7_1.3.2.0.release_oms.corr23.xml After installing of corr23, then do the same for corr24/25/26/27/28/29.
2. Install more that 1 correction level.For the following example R_GOMS7_1.3.2.0.release_oms.corr22 is installedand update is being done to R_GOMS7_1.3.2.0.release_oms.corr29. Files needed for theupdate are:
Install multiple corrections and create new SW Set (new SW Set will be passive):omsswm_install --full targetBD_R_GOMS7_1.3.2.0.release_oms.corr29.xml Activate SW Set:
Step 1 whether eNB startup is normal and cell on airStep 2 whether eNB has abnormal or new alarms
Step 3 whether all LEDs of eNB are normal
Step 4 whether the traffic of eNB and PM counter are normal
9.2 Flexi Zone
After downloading the software it is important to generate SH1 checksum for files and compare it withthe one provided in the Summary of Corrections and Enhancements document, this will ensure thatthe files were not corrupted during downloading. In order to check the package consistency after FlexiZone Micro BTS TD-LTE SW update, please ensure that the procedure “Update SW to BTS site” isterminating successfully.
10 DEGRADE OPERATION NOTICE
Rollback is the operation by which operator performs a software update with a software package olderthan the one currently active on the eNB.
Fallback is defined as the procedure by which eNB takes into use the SW on the backup/passivepartition. This occurs due to an error condition on the eNB and is not triggered by an operator.
Example below is for Rollback and Fallback.
10.1 Flexi Multi-radio Rollback/Fallback
10.1.1 Rollback to old release
If you want to rollback to RL45 or RL55 old release, operator can do this operation by twomethods:
• Do SWDL again with RL45 packet as generally step;
• Do it by “Rollback to passive SW and configuration” button.
If any fatal error happened, the eNB will return to old release automatic. And RFM could not been found by eNB due to RFSW incompatible.Perform a software download to target old release version again.
10.3 Flexi Zone Rollback/Fallback
Addit ional reset after roll back/fal lback
Flexi Zone BTS may reset additional one or two times after rollback/fallback to the older loads. Thismay lengthen the time necessary for eNB to come into service. This is known issue. Additionalworkarounds not needed.
SH1 checksum check
After downloading the software it is important to generate SH1 checksum for files and compare it withthe one provided in the Summary of Corrections and Enhancements document, this will ensure thatthe files were not corrupted during downloading.
Release incompatibil it ies between post RL55FZ PT2.5 loads and older RL55FZ (PT1 or PT2)
In RL55FZ release, there are introduced incompatibilities that make post PT2.5 loads unloadable byolder software releases (RL55FZ PT1 and PT2). There is a HIGH RISK of rendering the unitunusable after SW Rollback/Fallback. To avoid this issue additional step to load RL55FZ PT3(LNZ5.0_ENB_1407_103_00) needs to be taken. The intention is to clear the incompatible passivepartition and install a compatible release. Therefore each upgrade from older loads (RL55FZ PT1 orPT2) to the post RL55FZ PT2.5 loads and vice versa needs to be executed twice to install acompatible releases on both partitions.
Rollback/fallback between post RL55FZ PT2.5 and older RL55FZ (PT1 or PT2) loads i s notpossible w hen doing upgrade with intermediate load.
Due to the release incompatibilities and the intermediate load, direct rollback from post RL55FZ PT2.5to older RL55FZ (PT1 or PT2) loads is not possible, because rollback/fallback will be to intermediateload (RL55FZ PT3).
10.3.1 Rollback inst ruc tion
From Site Manager:
• Site Manager select Software Update SW to BTS site Rollback to Passive SW
From NetAct:
• NetAct Software Manager select MRBTS New Task Rollback
10.3.2 Fallback
If any fatal error happens, the eNB will automatically return to the version from passive partition.
[1] NOLS - Nokia Online Services log in link: https://online.portal.nsn.com[2]- "Installing Flexi Multiradio 10 Base Station for Stack, Wall, and Pole Configurations", DN09107819,Issue 08- "Installing Flexi Multiradio BTS LTE Modules for Stack, Wall, and Pole Configurations",DN0951987, Issue 07- "Installing Flexi Multiradio Base Station and Flexi Multiradio 10 Base Station Modules in Cabinets",DN09147506, Issue 02- "Installing Flexi Multiradio Base Station and Flexi Multiradio 10 Base Station Optional Items",DN09142359, Issue 02- "Installing Flexi Cabinet for Outdoor (FCOA)", DN09144084, Issue 01A
- "Installing Flexi Cabinet for Indoor (FCIA)", DN09144096, Issue 01- "Cabling Flexi Multiradio 10 Base Station", DN09107822, Issue 08- "Cabling Flexi Multiradio BTS LTE", DN0951881, Issue 05[3] "Commissioning Flexi Zone Micro BTS LTE", DN09176301, Issue 05 DRAFT[4] Long Term Evolution Information Center(LTE Radio Access, Rel. RL55, Operating Documentation, Pre-release, Issue 01)[6] "Upgrading from LTE iOMS 5.0 to LTE iOMS 6.0", DN0983101, Issue 01[7] "LTE System Upgrade", DN09183899, Issue 01[8] "Installing and Commissioning LTE iOMS", DN0956464, Issue 07A[9] “Upgrading from LTE OMS 5.0 or LTE OMS 6.0 to LTE OMS 7.0”, DN0983101, Issue 01
The information in this document applies solely to the hardware/software product (“Product”)specified herein, and only as specified herein.
This document is intended for use by Nokia Solutions and Networks' customers (“You”) only, andit may not be used except for the purposes defined in the agreement between You and NokiaSolutions and Networks (“Agreement”) under which this document is distributed. No part of thisdocument may be used, copied, reproduced, modified or transmitted in any form or meanswithout the prior written permission of Nokia Solutions and Networks. If you have not entered intoan Agreement applicable to the Product, or if that Agreement has expired or has beenterminated, You may not use this document in any manner and You are obliged to return it toNokia Solutions and Networks and destroy or delete any copies thereof.
The document has been prepared to be used by professional and properly trained personnel, andYou assume full responsibility when using it. Nokia Solutions and Networks welcome Yourcomments as part of the process of continuous development and improvement of thedocumentation.
This document and its contents are provided as a convenience to You. Any information orstatements concerning the suitability, capacity, fitness for purpose or performance of the Productare given solely on an “as is” and “as available” basis in this document, and Nokia Solutions andNetworks reserves the right to change any such information and statements without notice. NokiaSolutions and Networks has made all reasonable efforts to ensure that the content of thisdocument is adequate and free of material errors and omissions, and Nokia Solutions andNetworks will correct errors that You identify in this document. But, Nokia Solutions andNetworks' total liability for any errors in the document is strictly limited to the correction of sucherror(s). Nokia Solutions and Networks 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 NOTLIMITED TO ANY WARRANTY OF AVAILABILITY, ACCURACY, RELIABILITY, TITLE, NON-INFRINGEMENT, MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE, ISMADE IN RELATION TO THE CONTENT OF THIS DOCUMENT. IN NO EVENT WILL NOKIASOLUTIONS AND NETWORKS BE LIABLE FOR ANY DAMAGES, INCLUDING BUT NOTLIMITED TO SPECIAL, DIRECT, INDIRECT, INCIDENTAL OR CONSEQUENTIAL OR ANYLOSSES, SUCH AS BUT NOT LIMITED TO LOSS OF PROFIT, REVENUE, BUSINESSINTERRUPTION, BUSINESS OPPORTUNITY OR DATA THAT MAY ARISE FROM THE USEOF THIS DOCUMENT OR THE INFORMATION IN IT, EVEN IN THE CASE OF ERRORS IN OROMISSIONS FROM THIS DOCUMENT OR ITS CONTENT.
This document is Nokia Solutions and Networks’ proprietary and confidential information, which
may not be distributed or disclosed to any third parties without the prior written consent of NokiaSolutions and Networks.
Nokia is a registered trademark of Nokia Corporation. Other product names mentioned in thisdocument may be trademarks of their respective owners, and they are mentioned foridentification purposes only.
Nokia Solutions and Networks is continually striving to reduce the adverse environmental effects of itsproducts and services. We would like to encourage you as our customers and users to join us in workingtowards a cleaner, safer environment. Please recycle product packaging and fo llow the recommendationsfor 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 weoffer, please contact us at Nokia Solutions and Networks for additional information.
The information in this document is subject to change without notice and describes only theproduct defined in the introduction of this documentation. This documentation is intended forthe use of Nokia customers only for the purposes of the agreement under which thedocument is submitted, and no part of it may be used, reproduced, modified or transmitted inany form or means without the prior written permission of Nokia. The documentation hasbeen prepared to be used by professional and properly trained personnel, and the customerassumes full responsibility when using it. Nokia welcomes customer comments as part of theprocess 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 bedefined conclusively and finally in a separate agreement between Nokia and the customer.However, Nokia has made all reasonable efforts to ensure that the instructions contained in
the document are adequate and free of material errors and omissions Nokia will, if deemednecessary by Nokia, explain issues which may not be covered by the document.
Nokia will correct errors in this documentation as soon as possible. IN NO EVENT WILLNOKIA BE LIABLE FOR ERRORS IN THIS DOCUMENTATION OR FOR ANY DAMAGES,INCLUDING BUT NOT LIMITED TO SPECIAL, DIRECT, INDIRECT, INCIDENTAL ORCONSEQUENTIAL OR ANY LOSSES, SUCH AS BUT NOT LIMITED TO LOSS OFPROFIT, REVENUE, BUSINESS INTERRUPTION, BUSINESS OPPORTUNITY ORDATA,THAT MAY ARISE FROM THE USE OF THIS DOCUMENT OR THE INFORMATIONIN IT.
This documentation and the product it describes are considered protected by copyrights andother intellectual property rights according to the applicable laws.
The wave logo is a trademark of Nokia. Nokia is a registered trademark of NokiaCorporation.
Other product names mentioned in this document may be trademarks of their respectiveowners, and they are mentioned for identification purposes only.
Nokia Solutions and Networks is continually striving to reduce the adverse environmental effects of itsproducts and services. We would like to encourage you as our customers and users to join us in workingtowards a cleaner, safer environment. Please recycle product packaging and follow the recommendationsfor 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 weoffer, please contact us at Nokia Solutions and Networks for additional information.
Links and references to related documentation, which will supplement Release deliverydocumentation.
2 OTHER RELEVANT CUSTOMER DOCUMENTATION
Other relevant documentation can be found in Product Information Center. Links are given inchapter 4.
• For Flexi Base Station these documents are located in RL55 Documentation tabof Flexi Multiradio BTS Information Center.
• For iOMS these documents are located in RL55 Documentation tab of LTE iOMSInformation Center.
3 TS NOTE AND LIST OF GENERIC FAULTS
List of Generic Faults is part of the Release Documentation Set.
4 PRODUCT INFORMATION CENTER
Product Information Center (PIC) introduces the Nokia Solutions and Networks productportfolio as well as provides technical documentation for operating and maintaining NokiaSolutions and Networks products.
• Long Term Evolution Information Center
• LTE iOMS Information Center
• NetAct Information Center • Flexi NG Information Center
• Flexi NS – MME Information Center
5 HINT
The parameter information provided in LTE Radio Access Operation Documentation will bedelivered only in Excel format and not anymore as PDF or HTML.
The information in this document is subject to change without notice and describes only theproduct defined in the introduction of this documentation. This documentation is intended forthe use of Nokia customers only for the purposes of the agreement under which thedocument is submitted, and no part of it may be used, reproduced, modified or transmitted inany form or means without the prior written permission of Nokia. The documentation hasbeen prepared to be used by professional and properly trained personnel, and the customerassumes full responsibility when using it. Nokia welcomes customer comments as part of theprocess 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 bedefined conclusively and finally in a separate agreement between Nokia and the customer.However, Nokia has made all reasonable efforts to ensure that the instructions contained in
the document are adequate and free of material errors and omissions Nokia will, if deemednecessary by Nokia, explain issues which may not be covered by the document.
Nokia will correct errors in this documentation as soon as possible. IN NO EVENT WILLNOKIA BE LIABLE FOR ERRORS IN THIS DOCUMENTATION OR FOR ANY DAMAGES,INCLUDING BUT NOT LIMITED TO SPECIAL, DIRECT, INDIRECT, INCIDENTAL ORCONSEQUENTIAL OR ANY LOSSES, SUCH AS BUT NOT LIMITED TO LOSS OFPROFIT, REVENUE, BUSINESS INTERRUPTION, BUSINESS OPPORTUNITY ORDATA,THAT MAY ARISE FROM THE USE OF THIS DOCUMENT OR THE INFORMATIONIN IT.
This documentation and the product it describes are considered protected by copyrights andother intellectual property rights according to the applicable laws.
The wave logo is a trademark of Nokia. Nokia is a registered trademark of NokiaCorporation.
Other product names mentioned in this document may be trademarks of their respectiveowners, and they are mentioned for identification purposes only.
Nokia Solutions and Networks is continually striving to reduce the adverse environmental effects
of its products and services. We would like to encourage you as our customers and users to joinus in working towards a cleaner, safer environment. Please recycle product packaging andfollow the recommendations for power use and proper disposal of our products and theircomponents.
If you should have questions regarding our Environmental Policy or any of the environmentalservices we offer, please contact us at Nokia Solutions and Networks for additional information.
3 Effects on end-user ................................................................................................................................. 3
4 Effects on operator .................................................................................................................................. 4
5 Other effects ........................................................................................................................................... 6
6 New / Changed functionality .................................................................................................................... 6
The Purpose of this document is to describe the Release Delivery effects on the relevantparties and the new and changed functionalities that installing this Release Delivery bring tothe customer’s network.
2 RELEASE DELIVERY EFFECT
RL55 TD (LNT5.0) is a system release for Nokia Solutions and Networks Long TermEvolution (LTE), including the following network elements and SW releases
• Flexi Multiradio BTS
• Flexi iOMS
• Flexi Network Server (NS) and Flexi Network Gateway (NG)
Extended VoLTE talk time The UE power consumption during VoLTE calls is reduced.
Service based mobility trigger
VoLTE traffic steering schemes can be deployed with this feature
SCTP Mult i-homing
High reliability of C-plane by using different transport path for the associations or by usingmulti-homed associations between eNB and MME (using two IP addresses in each endpoint and so e.g. different transport path).
Intra-frequency load balancing
Avoiding of overload situations for specific cells by steering the traffic into less loaded cells
at same frequency layer.
RLF triggered handoverThe RRC connection re-establishment success rate is improved which leads to a reducedVoLTE call drop rate.
UL MU MIMO 8RX
The higher spectral efficiency may lead to an improved end-customer satisfaction.
Load tr iggered Idle Mode Load Balancing
Avoid frequent cell reselections at low load.
Suppor t of High Speed Users
LTE deployment at railways and motorways.
TTI bundling
Bundling of TTIs enhances the uplink coverage. One transport block is allocated to fourTTIs instead of one TTI, i.e. the energy per transmitted bit is increased.
OMS LDAP web GUI
Easier to use and lower risk to mess up with OMS parameters.
4 EFFECTS ON OPERATOR
Real-time KPI-monitoring with Traffica
Real-time KPI-monitoring with Traffica helps the operators to improve revenue due toreduced problems in the network and provide consequently more effective networks; anOPEX saving is also expected considering the expensive alternative solution based on 3rdparties probes tools available for the same use case.
TD-SCDMA redirect with multiple frequencies
The average service interruption time is reduced by providing multiple frequency targetsinstead of a single frequency target.
TDD Special Subframe Configuration 9
Customer can have co-existing TD-SCDMA network deployment in the sameband withmarginally higher throughput compared TDD Special subframeconfiguration 5.
Remote Syslog for continous log storageThis feature allows an increased number of BTS syslog messages to be logged withoutsuffering from the constraint of the local syslog file-size. This reduces outage times, errorcorrection times and service effort from customer and NSN.
Triple carrier operation
This allows operator to increase the LTE capacity by having three carriers.
Open access home eNode B mobility
This feature enables higher density of femto cells to be deployed.
Measurement Report addi tion with UE Uplink SINR
The measurement report will be used for radio coverage optimization purposes
SM (SiteManager) supports limited CLI function
- Operator can use CLI access the eNB by urgent case (e.g. when O&M system (e.g.NetAct) is out of service)- With pre-defined batch CLI commnd list, operator can get information from manyeNBs with script manner
Neighbor Relation Robustness
Neighbor relations learned autonomously in the network might not be valid anymore aftersome time, as they were at the time of new learning. The network setup might havechanged, so that other relations are used more often.With the enhancements in this feature the neighbor relations are maintained autonomouslywithout the need of manual operator intervention.
9.8Gbps Ir Interface for FSIH
Increase RP3-01 link speed and capacity which allows the use of less number of opticalfibersUtilize 1x9.8Gbps link per 8 pipe radio vs 2x6GbpsSavings 3 fiber links for 8 pipe/20Mhz/3sector site Also enables daisy chaining of more RRH to BBU site
Clock Slave mode for TD-SCDMA and TD-LTE dual mode on FSIH
-CMCC: FSIH will be utilized to support S222/S333 8T8R configuration. We are behind theother competitors on BBU performance before FSIH is introduced.-In most site on band 39/40, NSN has install base for TD-SCDMA, so TD-SCDMA and TD-LTE dual mode are required, and help to acquire our market share
Backup IPsec Tunnel
Service continuation w/o BTS site visit after SEG site disaster, while in normal operationmaximum security is applied, i.e. M-plane is protected by IPsec as well. By this retaincustomers, manage risks and differentiate in the market.
BTS and BTS Site Reset Support
-Customer requires highest availability of each RAT on a single RAN site. Only whenabsolutely required aggregated traffic e.g. of GSM BTS shall be impacted by reset of theaggregation master.-Instead of using BTS integrated aggregation, customer would need to buy (CAPEX)expensive cell site gateway (e.g. Cisco MWR)-Customer can remove one additional single point of failure (cell site gateway)
-Customer can reduce OPEX when using integrated transport, e.g. no additional HW, SWmaintenance, lower footprint, less cabinets etc.
User Layer TCP MSS clamping
IP fragmentation AND reassembly in the transport IP layer will be avoided which wouldhave a negative impact on throughput performance otherwise.
Serving PLMN ID change during X2 based handover
Inter PLMN mobility with HRL in X2 handover
TDD Special Subframe Conf iguration 3 and 4higher downlink share and flexible TDD LTE special SF configuration
FZHP Flexi RRH 2TX 2600
Remote RF Head is able to support 2TX MIMO with high output power. It enables easy
installation outdoors close to antennas thus maximising BTS site capacity and coverage.
X2 IP address exchange
The operator is able to increase the overall networks security. Provided that an eNBsupports the automated access control list configuration (ACL) for its firewall then thefirewall will be only opened for neighbor sites authorized by the MME. Thus these eNBaccept only X2 connections from neighbor eNB which are already known in advance.
5 OTHER EFFECTS
Secure management protocol between iOMS and NetAct
Enhanced risk management due to improved system security. A secured transportinterface can be used for management plane between iOMS and NetAct. OPEX andCAPEX savings are achieved because investments to external IPSec device co-sited toNetAct and manual IPSec configuration are not required to achieve system security.
The information in this document is subject to change without notice and describes only theproduct defined in the introduction of this documentation. This documentation is intended forthe use of Nokia Solutions and Networks customers only for the purposes of the agreementunder which the document is submitted, and no part of it may be used, reproduced, modifiedor transmitted in any form or means without the prior written permission of Nokia Solutionsand Networks. The documentation has been prepared to be used by professional andproperly trained personnel, and the customer assumes full responsibility when using it. NokiaSolutions and Networks welcomes customer comments as part of the process of continuousdevelopment 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 bedefined conclusively and finally in a separate agreement between Nokia Solutions and
Networks and the customer. However, Nokia Solutions and Networks has made allreasonable efforts to ensure that the instructions contained in the document are adequateand free of material errors and omissions. Nokia Solutions and Networks will, if deemednecessary by Nokia Solutions and Networks, explain issues which may not be covered bythe document.
Nokia Solutions and Networks will correct errors in this documentation as soon as possible.IN NO EVENT WILL NOKIA SOLUTIONS AND NETWORKS BE LIABLE FOR ERRORS INTHIS DOCUMENTATION OR FOR ANY DAMAGES, INCLUDING BUT NOT LIMITED TOSPECIAL, DIRECT, INDIRECT, INCIDENTAL OR CONSEQUENTIAL OR ANY LOSSES,SUCH AS BUT NOT LIMITED TO LOSS OF PROFIT, REVENUE, BUSINESSINTERRUPTION, BUSINESS OPPORTUNITY OR DATA,THAT MAY ARISE FROM THEUSE OF THIS DOCUMENT OR THE INFORMATION IN IT.
This documentation and the product it describes are considered protected by copyrights andother intellectual property rights according to the applicable laws.
NSN is a trademark of Nokia Solutions and Networks. Nokia is a registered trademark ofNokia Corporation Other product names mentioned in this document may be trademarks of