< Base Stations ; Radio Controllers> < Flexi Multiradio BTS TD-LTE; LTE iOMS > < RL35 MP2>
Document name: Summary of corrections and enhancements Impact Document Release Notes Installation Instructions Verification Report
Contact Contact your local Nokia Solutions and Networks support
Summary of changes: 16-7-2014 21-7-2014
0.1 1.0
Creation date Approval date
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 recommendations for power use and proper disposal of our products and their components. If you should have questions regarding our Environmental Policy or any of the environmental services we offer, please contact us at Nokia Solutions and Networks for additional information.
Summary of Corrections and Enhancements Id: LNT3.0 2.0 Product Family: Base Stations Radio Controllers Product: Flexi Multiradio BTS TD-LTE LTE iOMS Release: RL35 MP2 Approval date: (21-7-2014)
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 recommendations for power use and proper disposal of our products and their components. If you should have questions regarding our Environmental Policy or any of the environmental services we offer, please contact us at Nokia Solutions and Networks for additional information. LNT3.0 2.0 - Version 1.0 Confidential
Table of Contents Purpose ......................................................................................................................................................... 3 CORRECTIONS............................................................................................................................................ 3 New / Changed functionality ......................................................................................................................... 5
1. 2. 3. 3.1 3.2 3.3
4.
Released Features ................................................................................................................................................... 5 Restricted Released Features .................................................................................................................................. 5 Not Released Features ............................................................................................................................................ 5
status legacy features ................................................................................................................................... 5 4.1 4.2 4.3
5. 6.
Released Legacy Features ...................................................................................................................................... 5 Restricted Released Legacy Features ................................................................................................................... 15 Not Released Legacy Features .............................................................................................................................. 17
Lack of TRS IP counter(Transport Ethernet interface AF)
140268ESPE02
[RL35 Main]PM counter DATA_RB_STP_COMP Bigger than DATA_RB_STP_ATT in 251_03
140445ESPE02
BTS site manager don't show alarm information when enter an incorrect usrname and password.
140728ESPE02
modify PCI failed even though enableAutoLock=enable
46894ESPE05
[LNT3.0] Counter should be clear when changed VLAN ID
48011ESPE05
[LNT3.0][FIVE]SRS receive signal imbalanced
51057ESPE05
[RL35 main] CC&S error with EU id : 441 (0x1B9) after delete config&trs file
81251ESPE03
[LNT3.0]TRS configuration missing after ENB upgrade from LNT3.0_ENB_1304_243_02 to LNT2.0_ENB_9308_345_00
NA05634595
RL50 - FSMF fast tune does not work for SyncE, no alarm displayed
NA05640471
NA05640471 (ENB)one NEW site of F band reported 0010 system module failure alarm(7651)
115808ESPE04
[RL35 Main] FATAL Error during Stability test
NA05644907
LTE939 - Usage Based PDCCH Adaption for RL35 TDD sites
NA05652597
(TDD LTE RL35 MP1.0)(LNT3.0_ENB_1304_251_02)SON,LTE eNB cannot process DHCP broadcast package with TTL=1
NA05656753
E NodeB fails to connect to DHCP using SON.
NA05664136
NA05664136 || VSWR Major alarm not reporting in RL35 LTE BTS
111434ESPE01 NA05670149
VSWR Major Alarm is not Auto Clear after return the jumper back. Degradation of main KPI's for neighbors sites after Power OFF/ON of one TD-LTE eNB, Looks the site went out of synch
NA05678532
L23 TDD eNodeB with FSMF locking up requiring local reset to restore service.
Note: Action of reconnecting the RF Antenna cable needs more than 3 minutes to cancel all VSWR related alarms after tuning VSWR Thresholds. This is expected result but not SW bug.
3.
NEW / CHANGED FUNCTIONALITY
3.1
Released Features NA
3.2
Restricted Released Features NA
3.3
Not Released Features NA
4.
STATUS LEGACY FEATURES
4.1
Released Legacy Features ID
Feature Name
1
S1/X2 Datapath Management
2
S1 Flex
3 4 5 7 9 10 11 13
Operator Hint
S1, X2 and RRC Common Signaling Multi-Operator Core Network Radio Bearer and S1 Bearer Establishment and Release Support of Multiple EPS Bearer Service Differentiation EPS Bearers for Conversational Voice Robust Header Compression Rate Capping (UL/DL)
2-way RX Diversity (MRC) Flexi AC/DC With Battery Power Module Flexi Indoor and outdoor Cabinets
80
GPS Synchronization
97
Cell Radius Max 77 km
118 119 129 131 132
Fast Ethernet (FE) Gigabit Ethernet (GE) Electrical Interface Gigabit Ethernet (GE) Optical Interface Traffic Prioritization on Ethernet Layer Traffic Prioritization on IP Layer (Diffserv) VLAN Based Traffic Differentiation
138
Traffic Shaping (UL)
147
LTE Hardware Management
150
LTE OAM Transport Layer Security (TLS) Support
153
LTE BTS Site Manager
154 158 160 187 423 430
SON LTE BTS Auto Connectivity NTP Clock Time Synchronization Flexi Multiradio BTS 3GPP Antenna Tilt Support Single TX Path Mode RRC Connection Release With Redirect DL power boosting for control channels
DNS Support for Certificate Examination management data FlexiPacket Radio Connectivity ANR Cell Outage Triggered Reset Support of Sounding Reference Signal in TDD UpPTS
518
Operator specific QCI
522
S1 Partial Reset
527 528
Distributed Resource Allocation Type 2 Idle Mode Inter-frequency Mobility Management
539
Central ANR
540
Sounding Reference Signal in Normal Frames
541
Dual Stream beamforming
550 559 562 570 571 593 602
Radio Parameter Online Changeable SW monitoring Module for LTE CSFB to UTRAN or GERAN via redirect Periodic UE measurements Controlled uplink packet segmentation Security for Ethernet Ports on FCT/FSM3 Performance Management Administration
LTE Transport Protocol Stack LTE Certificate Management LTE685: Infrastructures for Certification Authority (CA) and Registration Authority (RA) LTE User Account Management LTE User Event Log Management LTE Local User Account Management Windows 7 Support for Element Manager Client Software Infrastructures for Certification Authority (CA) and Registration Authority (RA)
689
LTE IPsec Support
692
LTE Firewall Support
703 720 724
Downlink Adaptive Closed Loop MIMO for Two Antennas SON LTE BTS Auto Configuration LTE Automatic Neighbor Cell Configuration
RRC Connection Reestablishment IP Based Filtering for BTS Site Support Equipment Support of UE Radio Capabilities Link Adaptation for PDCCH Advanced Target Cell Selection and Handover Retry for Intra-frequency Handover Support of Aperiodic CQI Reports Basic Performance Counter Collection II Optimization of Intra-LTE neighbor relations
TDD DwPTS, GP and UpPTS With SF Configuration 7 Different IP Addresses for U/C/M/S-plane TDD DwPTS, GP and UpPTS With SF Configuration 5 ACK/NACK Bundling TDD Support for Random Access Preamble Burst Format 4 Non GBR QCI 5, 6, 7, 8 and 9 TDD DL/UL Switching 3DL:1UL TDD Frame Synchronized Operation
Full SON Support for Distributed Sites LTE iOMS HW, HP Blade Gen8 Support of QCI 2, 3 and 4 FTIF Transport PDH / Ethernet Adjustable Performance Upload
736
CS Fallback to UTRAN
495
OTDOA
1014
X2 eNB Configuration Update
953 984 587 1019
Online change TAC or Cell add delete will not trigger X2 eNB configuration. Customer document need to be modified for this restriction.
MDT (Minimization of Drive Test) GSM Redirect with System Information Multiple GBR EPS Bearers per UE SON Reports Released as radio-only feature. It's only tested in radio part
provide respective results in eNB trace file. The feature can be activated/deactivated by R&D flag in swconfig file with BTS reset. Not be able to execute LTE140 since customer environment is not available
CRL0867 : Idle mode mobility from LTE TDD to CDMA/(eHRPD, 1xRTT) Done by LTE870-C (for RL35TD branch) CRL0867 : Idle mode mobility from LTE TDD to CDMA/(eHRPD, 1xRTT) Done by LTE870-C (for RL35TD branch) CRL0867 : Idle mode mobility from LTE TDD to CDMA/(eHRPD, 1xRTT) LTE426,LTE807,LTE870 (for RL35TD branch) Dynamic transmission mode switch for TM3 and TM8 System Upgrade (TDD Release) DL TM8 based Dual User Single Layer MU-MIMO Transport Separation for RAN Sharing Multi-layered Certificate Authorities Usage based PDCCH adaptation An alarm shall be raised (per active TWAMP session), if at least one of the following conditions is fulfilled: - The 1 minute average RTT threshold has been exceeded - The 15 minutes packet loss threshold has been exceeded.
or - the session becomes stopped by the operator - the RTT threshold has not been exceeded for 5 minutes (and the packet loss condition is not fulfilled at that time) 144
Transport admission control
866
Fast IP Rerouting (FSMr3)
931
Ethernet Jumbo Frames
1163
TD-LTE Dual carrier operation with one RFM/RRU
899
Antenna Line Supervision
490
Subscriber profile based mobility
581
PRACH management
1441
423-F
423-D
1383 1443-B 1650-B
1392 898 568 1036 507
Not be able to pilot LTE866 since customer environment is not available
Enhanced CS fallback to CDMA/1xRTT (e1xCSFB) CRL0868 : support RRC connection release with redirection to CDMA in LTE TDD (for RL35TD, LNT3.0) CN5178 CRL0719 RRC connection release with redirect to FDD-LTE (TDD LTE, LTE423 extension) (CRL0901) - RL35 Cell Specific neighbor relation UpPTS blanking - for RL35 Remove Wimax interference to TDLTE during UL subframe?#3/8, TDLTE conf.1:7 - for RL35 Extended TD-LTE Site Configuration for RL35TD TDD inter-RAT handover to TD-SCDMA DL adaptive closed loop MIMO (4x2) RSRQ based cell reselection InterRAT neighbor relation Optimization (LTE, UTRAN, GERAN)
Event-triggered symptom data collection and provisioning
1260
iOMS Certificate update and revocation support
Operator Hints 1. If CRL checking feature” is enabled in OMS, please be aware that the downloaded CRL lists must be in status “OK”. Otherwise the OMS may send a cert request and refuse the validation of the received certificates with an out-dated CRL list. Result is the rejection of a https connection. 2. Registration Authority (RA) support not tested, because missing functionality from 3rd party tool (INSTA5.2.3) 3. Starting from RL50 the certificates (CA cert or Entity cert) without the Key Usage "digitalsignature" and key-enciphment" are not accepted by OMS.
1454 1457 1687
Flexi RF Module 2600 8x15W FZHE Cell trace Configuration via Configuration Management Basic Layer3 Data Analyzer (L3DA) for LTE
1680
Active Queue Management
1405
Remote SW-management and data backup/restore support for iOMS
NG3.1. Plan is to verify in maintenance program when NG3.1 is available. eRAB modification contains dedicated bearer modification which is not supported in NG3.1. This feature needs NG3.1 (or even NG3.2) supporting.
519 Smart Admission Control
497
163
Subscriber and Equipment Trace
612
Synchronization Hub
It has not been verified by real NG3.1. Plan is to verify in maintenance program when NG3.1 is available. "Tested with NS2.2 (N2 2.26-0); 1. Some L3 message can’t be traced (e.g. HO related) because the mechanism in MME can’t support millisecond interval for S1 trace signaling. MME is planned in NS4.0 currently. 2. Sometimes eNB does not sent start trace message after establishing of TCP connection to iOMS (105298ESPE04, root cause is in MME). 3. TraceFailure is not displayed in Trace Viewer (NetAct 8). 4. eNB cannot automatically switch all ongoing trace sessions to new serving iOMS CN4542. " BBUHotelling is not used in RL35, so LTE612-b31, LTE612-
b32 and LTE612-b1 not tested in RL35. The performance is not achieved.
RL45
Not Released Legacy Features ID
Feature Name
424
Automatic interface alarm correlation
5.
Operator Hint/ Restriction
Pronto ID
No NAS monitor for OSS5.5 available. New function will come with NetAct 8.
3RD PARTY CORRECTIONS NA
6.
RELEASE OBJECTS
6.1
Flexi Multiradio BTS LTE and iOMS description Information about Flexi Multiradio BTS LTE and iOMS can be found in Long Term Evolution Information Center, System Documentation, Chapter: “BTS and iOMS Descriptions”
6.2
Released software versions Following software version is released with this delivery.
It is recommended that after downloading the SWs users should use CM_tools to double check the checksums are consistent with checksum showed in NOLS page.
6.2.2
iOMS Software file list
Software Item
Software File Name iOMS5.0 R_GOMS6_1.107.1.0.release_oms .corr38
Title: innofidei UE parameters setting Impact: UE’s access and throughput will be impacted Workaround: To do TM8 operations, it needs to make sure all of the following parameters changed to these values. In SCF files (for innofidei):
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 recommendations for power use and proper disposal of our products and their components. If you should have questions regarding our Environmental Policy or any of the environmental services we offer, please contact us at Nokia Solutions and Networks for additional information. LNT3.0 2.0 - Version 1.0 Confidential
PURPOSE The Purpose of this document is to describe the Release Delivery effects on the relevant parties and the new and changed functionalities that installing this Release Delivery bring to the customer’s network.
2.
RELEASE DELIVERY EFFECT
RL35 Main (LNT3.0) is a system release for Nokia Long Term Evolution (LTE), including the following network elements and SW releases • Flexi Multiradio BTS • Flexi iOMS • Flexi Network Server (NS) and Flexi Network Gateway (NG) • NetAct Management System
HIGHLIGHTS ON END-USER DL TM8 based Dual User Single Layer MU-MIMO It helps to increase the cell capacity via pairing two single layer users. Dynamic transmission mode switch The system performance is optimized for UEs under different channel conditions. Usage based PDCCH adaptation The subscribers may experience better downlink throughput in scenarios with high PDSCH usage. Support of QCI 2, 3 and 4 Support end use with GBR services like gaming or streaming. Multiple GBR EPS Bearers per UE Support end use with additional service combinations. DL adaptive closed loop MIMO (4x2) Provide multiple antenna precoding gain, Improve cell edge and cell mean throughput.
4.
HIGHLIGHTS ON OPERATOR RRU for network deployment: FZHA RRH 2600 8x10W FZNC RRH 2300 6x10W FZNI RRH 2300 4x30W Dual carrier operation with one RFM/RRU This feature allows customer to increase the cell capacity via dual carrier Subscriber profile based mobility This feature allows customer to assign subscriber profile IDs (SPID) to mobility profiles. Transport admission control The Transport admission control enhances the resource utilization of the Flexi Multiradio BTS Transport Graceful cell shut down This feature allows customer to gradually reduces the downlink power in several steps, thus achieve minor service impact :UEs in RRC connected to perform a handover or a redirect and UEs in RRC idle to perform cell reselection and UEs in RRC idle to perform cell reselection. Remote SW-management and data backup/restore support for iOMS OPEX-savings by introducing remote SW-management for iOMS Mobility Robustness
SON-features to enables adjustment of Handover-related thresholds like HO offsets and TimeToTrigger based on performance monitor Inter-frequency load balancing BTS supports load based inter-frequency handover between different eNode Bs connected via X2 or S1 Idle mode mobility load balancing BTS supports idle mode mobility load balancing between different LTE carrier frequencies as well as for IRAT scenarios. RACH Optimization BTS support optimization of PRACH / RACH parameters values by Resolution of Collisions and Inconsistencies MDT (Minimization of Drive Test) Operators invest considerable amount of money in drive test equipment and the execution of drive tests during delivering rollout, replacement, modernization and optimization projects where huge cost are incurred due the required resources to perform the drive test. The idea is to automate collecting of trace information from eNB in a preconfigured use case specific way, including UE measurements which would be post processed and analyzed quickly. This solution provides operator OPEX and CAPEX saving since not so many resources are needed to evaluate the performance of service and network thereby eliminating the need to perform an expensive drive test. Remove Wimax interference to TDLTE TD-LTE BTS supports co-existent with Wimax by specific SRS handling to remove interference. TDD - FDD handover Both handover directions FDD -> TDD and TDD -> FDD are supported. Cell Specific neighbor relation Introduce Cell specific PCI resolution to the existing ANR features to allow enhanced usage of ANR and HO related features even in difficult network setups Multi-layered Certificate Authorities Supports operator certificate management for multi-layer hierarchical PKI and crosscertified PKI structures by Flexi Multiradio BTS, The customer is able to integrate Nokia Identity Management System as sub-ordinate CA into its existing PKI and deploy an own/3rd party sub-ordinate CA to manage certificates for the Flexi Multiradio BTS iOMS Certificate update and revocation support The customer is able to use a usual Public Key Infrastructure with a Root certificate Authority on top and use case specific sub-ordinate Certificate Authorities in charge for signing the RAN nodes also now for iOMS nodes. 3GGP compliant life cycle management allows flexibility on PKI vendor selection and harmonized certificate management for iOMS in the same fashion as for BTS and Security Gateways which leads to severe OPEX reductions. X2 eNB Configuration Update LNT3.0 2.0 - Version 1.0 Confidential
Supports the configuration update to neighbor eNBs via X2AP:eNodeBConfigurationUpdate about served cell information, such as change of PCI or EARFCN, GU Group ID IP Transport Network Measurement This feature brings OPEX savings as the operator is able to monitor the network conditions and can react quickly to potential service degradations. The measurements provide an indication of possible violations against an SLA (Service Level Agreement). CAPEX savings are obtained, because the built-in measurement means obsoletes expensive measurement equipment that would be otherwise required to supervise and troubleshoot the network Event-triggered symptom data collection and provisioning The feature presents a centralized function of collecting BTS Techlogs (troubleshooting data) from Flexi Multiradio BTS when a predefined event occurs. The logs are available in the NetAct and can be accessed by operator and sent to technical service to identify problems.
5.
OTHER HIGHLIGHTS Secure management protocol between iOMS and NetAct Enhanced risk management due to improved system security. A secured transport interface can be used for management plane between iOMS and NetAct. OPEX and CAPEX savings are achieved because investments to external IPSec device co-sited to NetAct and manual IPSec configuration are not required to achieve system security.
Change Note Forms Id: LNT3.0 2.0 Product Family: Base Stations Radio Controllers Product: Flexi Multiradio BTS TD-LTE LTE iOMS Release: RL35 MP2 Approval date: (21-7-2014)
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 recommendations for power use and proper disposal of our products and their components. If you should have questions regarding our Environmental Policy or any of the environmental services we offer, please contact us at Nokia Solutions and Networks for additional information.
Title: Version of the SW-build: LNT3.0_ENB_1304_301_00 Valid for Product(s): Flexi LTE Base Station References:
Reason for the Change Note: Summary of the original problem: When working with iOMS after reaching max number of connections all following connections were rejected. When used connections decrease below maximum connections eNB which was previously rejected could not connect correctly despite of free connections in iOMS. How end user/operator could detect the problem: Operator should configure network with tracing feature. All sessions should be configured toward 3rd party tool. User can observe the problem when number of session exceed the number of connections supported by the iOMS and when some of the connections are released and previously rejected connection will try to connect again (without the eNB reconfiguration). Description of the fault: No start trace is send when eNB connects to iOMS after being previously rejected. What cause connection to be reset by iOMS. Related feature / functionality: LTE644 LTE163 Dependency on configuration: NA Workaround: NA Description of the correction (incl. risk analysis): eNB send start trace toward iOMS each time the connection is re-established. System effects: NA Faulty component and version: LOM: LNT3.1_LOM_1209_30956 Faulty component first delivered in (e.g. release, CD): Corrected Fault Reports: 109320ESPE01 Alarm flood of failure in connection between BTS and iOMS or 3rd party tool.
Modified components: Component Version *Net element LOM.30956 -
*SW-type
*Unit -
-
Change effects: Effects on end-user NA Effects on Operator NA Other effects NA New functionality NA Customer Impact No direct impact on customer. Additional messages are sent between eNB and IOMS.
Testing Instructions for the change Pre-requirements: Setup network with trace sessions towards 3rd party tool. Number of sessions have to be bigger than maximum number of connections supported by iOMS. Test execution: Remove session that is connected leaving sessions that were not connected because of max connections reach on iOMS side. Expected results: No alarm flood Unexpected results: Alarm flood of failure in connection between BTS and iOMS or 3rd party tool on eNB;
CN-id: LNT3.0_18280
Title: NA05664136 || VSWR Major alarm not reporting in RL35 LTE BTS Version of the SW-build: LNT3.0_ENB_1304_301_00 Valid for Product(s): LNT3.0 2.0 - Version 1.0 Confidential
Reason for the Change Note: Summary of the original problem: Antenna open state, alarm 1837 and 1957 reported simultaneously How end user/operator could detect the problem: alarm from site manager Description of the fault: antenna open state, alarm 1837 and 1957 reported simultaneously Related feature / functionality: N/A Dependency on configuration: N/A Workaround: N/A Description of the correction (incl. risk analysis): Add VSWR Major alarm in RL35. System effects: N/A Faulty component and version: N/A Corrected Fault Reports: NA05664136 NA05664136 || VSWR Major alarm not reporting in RL35 LTE BTS
Modified components: Component Version *Net element TDL24.03.R03D TDL24.03.R0 3D
*SW-type
*Unit -
-
Change effects: Effects on end-user NA Effects on Operator NA Other effects NA New functionality NA Customer Impact LNT3.0 2.0 - Version 1.0 Confidential
Testing Instructions for the change Pre-requirements: eNBs are installed with correction SW, up running, cells are configured, and On-Air state. Test execution: Trigger high VSWR environment (e.g. removing RF Antenna Cable) on the TRX port. Expected results: If the VSWR value higher than the VSWR Major Threshold, VSWR Major Alarm and Radio resources switched off should be raised Unexpected results: VSWR Major Alarm does not raised
CN-id: LNT3.0_18344
Title: LTE939 - Usage Based PDCCH Adaption for RL35 TDD sites Version of the SW-build: LNT3.0_ENB_1304_301_00 Valid for Product(s): Flexi LTE Base Station References:
Reason for the Change Note: 116050ESPE04: Summary of the original problem: scenario which triggered the issues (mandatory): Step1: Activated load adaptive PDCCH which allows adapt number of PDCCH symbol dynamic; Step2: Set maximum number of PDCCH symbols= 3, this would have number of PDCCH symbols from 1 to 3 in terms of setting; root cause for the fixed pronto (mandatory): EFS pronto, pdcch symbol need not add one when pdcchinnumOfSymChangeTime expired. correction solution for the fixed pronto (mandatory): EFS pronto, pdcch symbol need not add one when pdcchinnumOfSymChangeTime expired. Loc (mandatory): 16 fault category (mandatory): EFS design error feature which introduced this pronto (mandatory): LTE939 Fault category description: LNT3.0 2.0 - Version 1.0 Confidential
How end user/operator could detect the problem: System effects: NA Corrected Fault Reports: 116050ESPE04 LTE939 - Usage Based PDCCH Adaption for RL35 TDD sites NA05644907 LTE939 - Usage Based PDCCH Adaption for RL35 TDD sites
Modified components: Component Version fb1304.RRMT.5358 LTE_UP_9881.LTE_UP_8700.-
*Net element 128677 2.0.0 20.0 50.0 -
*SW-type
*Unit -
-
Change effects: Effects on end-user NA Effects on Operator NA Other effects NA New functionality NA Customer Impact 116050ESPE04: NA05644907: New feature/functionality PDDCH symbol number will increase unintentionally. This will be noticed only when the load is low. This has no significant negative impact on performance but the behavior is strange.
Testing Instructions for the change Pre-requirements: As pronto test description Test execution: As pronto test description Expected results: the PDCCH symbol will be stable 1 when stably no load Unexpected results: NA LNT3.0 2.0 - Version 1.0 Confidential
Title: SEM report error after commissioning file active successful Version of the SW-build: LNT3.0_ENB_1304_301_00 Valid for Product(s): Flexi LTE Base Station References:
Reason for the Change Note: From PDDB description if srsSubfrConf set to 'sc0', 'sc8', 'sc9', 'sc10' or 'sc11', srsOnTwoSymUpPts must be set to 'true', but when I set srsSubfrConf to 'sc0' and srsOnTwoSymUpPts set as empty SEM did not report any error. Corrected Fault Reports: 109576ESPE01 SEM report error after commissioning file active successful
Modified components: Component Version *Net element tdltebtsmanager.jar 646231 -
*SW-type
*Unit -
-
Change effects: Effects on end-user NA Effects on Operator NA Other effects NA New functionality NA Customer Impact Operation & Maintenance
Testing Instructions for the change LNT3.0 2.0 - Version 1.0 Confidential
Pre-requirements: set srsSubfrConf to 'sc0' and srsOnTwoSymUpPts set as empty Test execution: I set srsSubfrConf to 'sc0' and srsOnTwoSymUpPts set as empty Expected results: SEM report error Unexpected results: SEM did not report any error
CN-id: LNT3.0_28268
Title: BTS Crash with RRU status still OK to access normally, BTS could not reset itself except repower on. Version of the SW-build: LNT3.0_ENB_1304_301_00 Valid for Product(s): Flexi LTE Base Station References:
Reason for the Change Note: PR 113478ESPE04: BTS Crash with RRU status still OK to access normally, BTS could not reset itself except repower on. [PR 106711ESPE01][LNT3.0]BTS crash when UE attach and doing throughput Description of the fault: BTS is on air. UE attach/UE attach and doing T-put.BTS crash and only reset by power off/on can recover. Related feature / functionality: NA Description of the correction (incl. risk analysis): From the back trace we are able to confirm that crash took place while incrementing performance counter. Crash is happening while incrementing a performance counter and an invalid reference is used while incrementing that is causing the crash. This performance counter will get incremented when some unknown protocol packet with TTL=0 is received or if packet is received that is coming under TTL violation or some other error condition. For external communication, we have defined ports 8,9, and 10. If an invalid port is received while incrementing counter then it maps to an invalid memory reference and that handling is not done in the code. LNT3.0 2.0 - Version 1.0 Confidential
Corrected Fault Reports: 113478ESPE04 BTS Crash with RRU status still OK to access normally, BTS could not reset itself except repower on. 106711ESPE01 BTS crash when UE attach and doing throughput
Modified components: Component Version *Net element aricent_r3_pm_106 FTM_R3_LN5 711.0_LNT30_MP 1_323.00.01
*SW-type
*Unit -
-
Change effects: Effects on end-user NA Effects on Operator NA Other effects NA New functionality NA Customer Impact NA
Testing Instructions for the change Pre-requirements: eNB on air Test execution: UE PPOE attach for data traffic Expected results: No abnormal issue happen, such as eNB crash in this case. Unexpected results: eNB crash in this case, when UE PPOE attach
CN-id: LNT3.0_28269 LNT3.0 2.0 - Version 1.0 Confidential
Title: [RL35 P8] can't establish the SSL connection after upgrade from RL25 Version of the SW-build: LNT3.0_ENB_1304_301_00 Valid for Product(s): Flexi LTE Base Station References:
Reason for the Change Note: Summary of the original problem: On upgrading from RL25 to RL35 build, FTM webpage was not opening Description of the fault: In case when FTM is only containing BTS cert and no certificate chain then in that case lighthttpd.pem file is not generated. On upgrading from FTM ln20(non-MLCA) to ln50(MLCA), ln50 was not considering single certificate/key in certs directory and using bts certificate. Due to this lighthttpd.pem was not being created. Related feature / functionality: Certificate installation, lightHttpd.pem generation, lighttpd process startup Description of the correction (incl. risk analysis): In case when certificate chain is not present and bts cert is present then lighthttpd.pem is created using BTS cert.
Corrected Fault Reports: 112362ESPE04 [RL35 P8] can't establish the SSL connection after upgrade from RL25
Modified components: Component Version *Net element aricent_r3_ln50_11 FTM_R3_LN5 2362espe04_ssl_er 0_LNT30_MP ror_new.1_322.00.02
*SW-type
*Unit -
-
Change effects: Effects on end-user NA Effects on Operator NA Other effects NA New functionality NA LNT3.0 2.0 - Version 1.0 Confidential
Testing Instructions for the change Pre-requirements: The eNB running with RL25 SW, equipped with IPSec certificate, the status is OK.
Test execution: upgrade to RL35 P8 LNT3.0_ENB_1304_243_02
Expected results: the eNB is on air , but the SSL connection is OK Unexpected results: the SSL connection is impossible.
CN-id: LNT3.0_28270
Title: [LNT3.0]TRS configuration missing after ENB upgrade from LNT3.0_ENB_1304_243_02 to LNT2.0_ENB_9308_345_00 Version of the SW-build: LNT3.0_ENB_1304_301_00 Valid for Product(s): Flexi LTE Base Station References:
Reason for the Change Note: Summary of the original problem: [LNT3.0]TRS configuration missing after ENB upgrade from LNT3.0_ENB_1304_243_02 to LNT2.0_ENB_9308_345_00 Description of the correction (incl. risk analysis): issue mentioned in PR 81251ESPE03 arose because of mismatch in MOs supported in LNT3.0 vs. LNT2.0. Following MOs were supported in LNT 3.0 but not supported in LNT 2.0: 1. 2. 3. 4. 5.
But there was no provision to remove these MOs in the transformation function used for LNT2.0 adaptation. As a fix, transformation function has been enhanced to remove the above mentioned MOs while doing a downgrade from LNT3.0 to LNT2.0.
Corrected Fault Reports: 81251ESPE03 [LNT3.0]TRS configuration missing after ENB upgrade from LNT3.0_ENB_1304_243_02 to LNT2.0_ENB_9308_345_00
Modified components: Component Version *Net element aricent_r3_twamp.- FTM_R3_LN5 0_LNT30_MP 1_322.00.02
*SW-type
*Unit -
-
Change effects: Effects on end-user NA Effects on Operator NA Other effects NA New functionality NA Customer Impact NA
Testing Instructions for the change Pre-requirements: 1.BTS is On Air with LNT3.0 build, and with feature LTE574 enabled 2.prepare one LNT2.0 package Test execution: Upgrade from LNT3.0 to LNT2.0 Expected results: Upgrade successfully, BTS is On Air, TRS commissioned Unexpected results: BTS is not On-air, TRS is not commissioned
Title: BTS site manager don't show alarm information when enter an incorrect usrname and password. Version of the SW-build: LNT3.0_ENB_1304_301_00 Valid for Product(s): Flexi LTE Base Station References:
Reason for the Change Note: Summary of the original problem: Error being removed by ui update How end user/operator could detect the problem: the error disappearing after wrong credentials Description of the fault: The ui update removed the error from the launcher Related feature / functionality: the launcher connect Dependency on configuration: it is in all configurations Workaround: none Description of the correction (incl. risk analysis): The error message flash in a very short time. This problem have been fixed about 2 month ago Effects on end-user: The error message flash in a very short time. This problem have been fixed about 2 month ago Effects on operator: The error message flash in a very short time. This problem have been fixed about 2 month ago System effects: The error message flash in a very short time. This problem have been fixed about 2 month ago Other effects: N/A Interface Effects: The error message flash in a very short time. This problem have been fixed about 2 month ago Faulty component and version: launcher/trunk Faulty component first delivered in (e.g. release, CD):N/A Dependency on configuration: Workaround: none Description of the correction (incl. risk analysis): The error message flash in a very short time. This problem have been fixed about 2 month ago Effects on end-user: The error message flash in a very short time. This problem have been fixed about 2 month ago LNT3.0 2.0 - Version 1.0 Confidential
Effects on operator: The error message flash in a very short time. This problem have been fixed about 2 month ago System effects: N/A Other effects: N/A Interface Effects: The error message flash in a very short time. This problem have been fixed about 2 month ago Faulty component and version:LNT3.1_BTSSM_1209_085_00 Faulty component first delivered in (e.g. release, CD):N/A Corrected Fault Reports: 140445ESPE02 BTS site manager don't show alarm information when enter an incorrect usrname and password.
Modified components: Component Version cl.-
*Net element -
*SW-type
*Unit -
-
Change effects: Effects on end-user NA Effects on Operator NA Other effects NA New functionality NA Customer Impact Operation & Maintenance
Testing Instructions for the change Pre-requirements: BTSSM have installed normally Test execution: 1. Input correct username and error password, Or Input error username and correct password. 2. click "login" button Expected results: It should have related information if login failed. Unexpected results: There is not any information to show .
Title: Lack of TRS PM counter(IP counter: Transport Ethernet interface AF4) Version of the SW-build: LNT3.0_ENB_1304_301_00 Valid for Product(s): Flexi LTE Base Station References:
Reason for the Change Note: Summary of the original problem: Lack of TRS PM counter(IP counter: Transport Ethernet interface AF4) How end user/operator could detect the problem: Functional Description of the fault: while receiving packet from S1 interface with different dscp value, there is no PHB counter increment according to the DSCP value Related feature / functionality: NA Dependency on configuration: NA Workaround: NA Description of the correction (incl. risk analysis): while enabling QoS from EM, there is index used to maintain at device Adapter and FastPath for each dscp value. From Device adapter always index used to come with value 1. But FastPath used to calculate it wrongly and while increment PHB counter it value also get wrong . So at FastPath it also made 1.
Corrected Fault Reports: 138723ESPE02 Lack of TRS PM counter(IP counter: Transport Ethernet interface AF4)
Modified components: Component Version aricent_r3_rl50_mp in LNT3.0 2.0 - Version 1.0 Confidential
Change effects: Effects on end-user NA Effects on Operator NA Other effects NA New functionality NA Customer Impact Operation & Maintenance
Testing Instructions for the change Pre-requirements: all the packets show in the TRS PM counter should report the real state Test execution: 1. BTS is on air 2.Configure all the DSCP in one queue 3.Configure the egress shaper information to let upload traffic to fill full bandwidth 4.Do UL and DL throughput 5.Check the TRS PM counter Expected results: check TRS PM counter, the packets pass the Ethernet of eNB under vlan should as fast as you did Unexpected results: the ifInpackets counter of the TRS is zero, means no packets pass this port, unreasonable
CN-id: LNT3.0_31445
Title: [RL35 IR] System module fault (0010) or FBBA not detected after bts reset Version of the SW-build: LNT3.0_ENB_1304_301_00 Valid for Product(s): LNT3.0 2.0 - Version 1.0 Confidential
Reason for the Change Note: Summary of the original problem: One NEW site of F band reported 0010 system module failure alarms (7651) How end user/operator could detect the problem: FSP not starting Description of the fault: System module failure alarm (7651) on few (1/1000) A101, A102 or A103 (before w47 2013) FSMF. Related feature / functionality: NA Dependency on configuration: NA Workaround: power cycle Description of the correction (incl. risk analysis): make add events parallel in HPD Effects on end-user: out of service Effects on operator: our of service System effects: NA Other effects: NA Interface Effects: NA Faulty component and version: PS_REL_20M2_99_20 Faulty component first delivered in (e.g. release, CD): since mid of 2013 Corrected Fault Reports: 108122ESPE01 [RL35 IR] System module fault (0010) or FBBA not detected after bts reset 139978ESPE02 [R55 FSMF][Dual Carrier FZHA][routing table is not setup for one cell, another can be on-air] NA05640471 NA05640471 (TDLTE Fujian)(ENB)one NEW site of F band reported 0010 system module failure alarm(7651) 115623ESPE04 ][RL35 Main] Can’t detect FBBA2 and appeared 0010 alarm after Upgrade LNT3.0_ENB_1304_251_03 to LNT3.0_ENB_1304_273_00
Modified components: Component Version *Net element LFS.r70166 LNT3.0 2.0 - Version 1.0 Confidential
Change effects: Effects on end-user NA Effects on Operator NA Other effects NA New functionality NA Customer Impact 108122ESPE01: Stability NA05640471: Operation & Maintenance
Testing Instructions for the change Pre-requirements: NA Test execution: NA Expected results: NA Unexpected results: NA
CN-id: LNT3.0_31697
Title: Poster test scenarios not take effect after FSP2 external Memory test failure Version of the SW-build: LNT3.0_ENB_1304_301_00 Valid for Product(s): Flexi LTE Base Station References:
Reason for the Change Note: LNT3.0 2.0 - Version 1.0 Confidential
Summary of the original problem: when POST flag(427) isn't set in swconfig or set to 0, SPMAG doesn't verify the result of POST. Then, BTSOM doesn't know any errors of POST when power on reset. How end user/operator could detect the problem: test scenario described in this PR. Description of the fault: The fault FaultId_Post_test_failedAl isn't reported to SEM. Related feature / functionality: NA Dependency on configuration: NA Workaround: NA Description of the correction (incl. risk analysis): SPMAG will always validate the result of POST even if there is no POST flag System effects: NA Interface Effects: NA Corrected Fault Reports: 107858ESPE01 Poster test scenarios not take effect after FSP2 external Memory test failure
Modified components: Component Version *Net element FB_PS_REL_2013 128 _04_128.CSpmag_TaskPOS 263321 T.cls 48634.48634 -
*SW-type
*Unit -
-
-
-
-
-
Change effects: Effects on end-user NA Effects on Operator NA Other effects NA New functionality NA Customer Impact Operation & Maintenance LNT3.0 2.0 - Version 1.0 Confidential
Testing Instructions for the change Pre-requirements: n/a Test execution: Install the new eNB SW include correction for "Post test scenarios". If DSP fail post test, eNB will repot alarm of 69: EFaultId_Post_test_failedAl. Expected results: If DSP fail post test, eNB will repot alarm of 69: EFaultId_Post_test_failedAl.. Unexpected results: If DSP fail post test, FSP might be failure, then report other alarm, not report alarm of 69: EFaultId_Post_test_failedAl.
CN-id: LNT3.0_31701
Title: [RL35 Main] FATAL Error during Stability test Version of the SW-build: LNT3.0_ENB_1304_301_00 Valid for Product(s): Flexi LTE Base Station References:
Reason for the Change Note: Summary of the original problem: Random SRIO network congestion during high DIO bandwidth utilization causing spontaneous FATAL crashes How end user/operator could detect the problem: Execute high load test cases Description of the fault: Insufficient VBUS priority of SRIO transfers causing SRIO response timeouts and network congestion Related feature / functionality: None Dependency on configuration: None Workaround: LNT3.0 2.0 - Version 1.0 Confidential
None Description of the correction (incl. risk analysis): Increased SRIO device VBUS access priority : System effects: NA Interface Effects: none Faulty component and version: NA Faulty component first delivered in (e.g. release, CD): NA Corrected Fault Reports: 115808ESPE04 [RL35 Main] FATAL Error during Stability test
Modified components: Component Version PSDSP-3362.-
*Net element -
*SW-type
*Unit -
-
Change effects: Effects on end-user NA Effects on Operator NA Other effects NA New functionality NA Customer Impact Stability
Testing Instructions for the change Pre-requirements:
Test execution: 200 UE with full traffic on DL/UL, run for 3~12 hours. Check FATAL error log in Syslog Expected results: 1. Stable throughput 2. No fatal error happen
Title: Degradation of main KPI's for neighbors sites after Power OFF/ON of one TD-LTE eNB, Looks the site went out of synch Version of the SW-build: LNT3.0_ENB_1304_301_00 Valid for Product(s): Flexi LTE Base Station References:
Reason for the Change Note: Summary of the original problem: FYGB supply the wrong UTC time How end user/operator could detect the problem: Several times power reset GPS Description of the fault: NA Related feature / functionality: NA Dependency on configuration: FYGB was using Workaround: NA Description of the correction (incl. risk analysis): After EFS discuss with Tribbel person , the new msg 0x41 and 0x46 was new introduced to be checked to promise the correct UTC time . System effects: NA Faulty component and version: NA Faulty component first delivered in (e.g. release, CD): NA Corrected Fault Reports: NA05670149 Degradation of main KPI's for neighbors sites after Power OFF/ON of one TD-LTE eNB, Looks the site went out of synch
Modified components: Component Version LNT3.0 2.0 - Version 1.0 Confidential
Change effects: Effects on end-user NA Effects on Operator NA Other effects NA New functionality NA Customer Impact Capacity & Performance
Testing Instructions for the change Pre-requirements: Use FYGB The power supply lost for the whole shelter suddenly and there is no battery backup. Test execution: 1.eNB is on air on the RL35 MP2 2.The GPS receiver device is FYGB. 3. There is power break suddenly for all the shelter. 4. the eNB recovered after the power supply is normal. 5. Enable the following flag in the swconfig. 330 =1 428 =1 13=1
Expected results: The eNB is on air normally. Unexpected results: KPI degraded.
CN-id: LNT3.0_31709 LNT3.0 2.0 - Version 1.0 Confidential
Title: [LNT3.0] Counter should be clear when changed VLAN ID Version of the SW-build: LNT3.0_ENB_1304_301_00 Valid for Product(s): Flexi LTE Base Station References:
Reason for the Change Note: Summary of the original problem: Counter should be clear when changed VLAN ID Description of the fault: counters not cleared when vlan id is changed Related feature / functionality: Counters Description of the correction (incl. risk analysis): reset request is sent to the fast path from the adapter when vlan id is changed
Corrected Fault Reports: 46894ESPE05 [LNT3.0] Counter should be clear when changed VLAN ID
Modified components: Component Version aricent_r3_pr_5065 7_ln50_mp2.FTM_R3_LN50_LN T30_MP2_334.00.0 2
*Net element -
*SW-type
*Unit -
-
-
-
Change effects: Effects on end-user NA Effects on Operator NA Other effects NA New functionality NA Customer Impact LNT3.0 2.0 - Version 1.0 Confidential
Testing Instructions for the change Pre-requirements: eNB configured with VLAN. Test execution: Change the VLAN ID directly but not modify the IP address for this vlan. Expected results: The Ethernet counter for this vlan change to 0. The counter in this 15min period will lose. The history counter still keep. Unexpected results: Counter value too large or history counter lost.
CN-id: LN50_104
Title: E NodeB fails to connect to DHCP using SON. Version of the SW-build: LNT3.0_ENB_1304_301_00 Valid for Product(s): Flexi LTE Base Station References:
Reason for the Change Note: Summary of the original problem: E NodeB fails to connect to DHCP using SON. How end user/operator could detect the problem: please see detailed description Description of the fault:eNodeB fails to connect to DHCP DHCP server sends out the DHCP Offer message to the eNB via the Relay agent as unicast message which is transformed with TTL value as 1 (whatever you set at DHCP server, Relay Agent modifies it to TTL value-1) as broadcast towards the eNB as destination. eNB FSM ETH-1 port decrements the TTL value to 0 and before accepting the assigned IP, NSN eNB discard the packets which in terms that eNB never sends out the DHCP Request message and the process repeats after a while Related feature / functionality: IP Dependency on configuration: DHCP is received with ttl=1 LNT3.0 2.0 - Version 1.0 Confidential
Workaround: None Description of the correction (incl. risk analysis):added condition to check for broadcast packets with ttl value equal to 1 or 0 and accept them Corrected Fault Reports: NA05656753 E NodeB fails to connect to DHCP using SON.
Modified components: Component Version *Net element aricent_r3_na0565 FTM_R3_LN5 2597_rl50_mp1.0_LNT30_MP 1_333.00.02
*SW-type
*Unit -
-
Change effects: Effects on end-user NA Effects on Operator NA Other effects NA New functionality NA Customer Impact NA05656753: Capacity & Performance
Testing Instructions for the change Pre-requirements: FSMF and auto connection feature usage, with target HW being updated to RL50 MP1.1 first Test execution: Auto connection process is carried out, with a dhcp server being set up accordingly. Dhcp offer message from dhcp server even with TTL field being = 1 will be processed by eNB and thus auto connection process completes successfully. This can be seen in wireshark, as after dhcp offer message eNB sends out dhcp request message. Expected results: auto connection process completes successfully Unexpected results: auto connection process does not complete.
Title: L18 eNodeB with RL50 0.2 s/w locking requiring local reset to restore Version of the SW-build: LNT3.0_ENB_1304_301_00 Valid for Product(s): Flexi LTE Base Station References:
Reason for the Change Note: Summary of the original problem: System logger causes slowdowns. How end user/operator could detect the problem: Overall performance impact in particular for processes that do logging. Description of the fault: Logger causes backpressure under certain situations, which in turn leads to SW slowdown. This backpressure was caused by using a "compatibility mode" flag triggered the logger bug. Related feature / functionality: N/A Dependency on configuration: N/A Workaround: N/A Description of the correction (incl. risk analysis): Logger configuration has been updated not to use compatibility mode (which was not needed anyway anymore). Very low risk assumed. System effects: NA SW lockup due to logging should not happen anymore. Corrected Fault Reports: NA05668028 L18 eNodeB with RL50 0.2 s/w locking requiring local reset to restore
Modified components: Component Version *Net element LFS.r79315 -
*SW-type
*Unit -
-
Change effects: LNT3.0 2.0 - Version 1.0 Confidential
Effects on end-user NA Effects on Operator NA Other effects NA New functionality NA Customer Impact NA05668028: Operation & Maintenance
Testing Instructions for the change Pre-requirements: This was a platform problem, difficult to be reproduced in lab environment. The issue (site not working/IPSec not coming up) should not show up any more after correction installation. Test execution: NA Expected results: NA Unexpected results: NA
CN-id: LNT3.0_31699
Title: [RL35 Main]PM counter DATA_RB_STP_COMP Bigger than DATA_RB_STP_ATT in 251_03 Version of the SW-build: LNT3.0_ENB_1304_301_00 Valid for Product(s): Flexi LTE Base Station References:
Reason for the Change Note: Summary of the original problem: LNT3.0 2.0 - Version 1.0 Confidential
Completion Counter bigger than attempt counter, i.e. completion counter is wrongly incremented twice How end user/operator could detect the problem: See above. Description of the fault: In case of the occurrence of a reestablish request while still running in a handover target scenario in target configuration, the completion or failure counters are wrongly incremented by the reestablish procedure Related feature / functionality: NA Dependency on configuration: NA Workaround: NA Description of the correction (incl. risk analysis): - relegated counters are not counted for intracell HO cases or target configuration scenarios anymore, low risk System effects: NA Other effects: NA Faulty component and version: NA Corrected Fault Reports: 140268ESPE02 [RL35 Main]PM counter DATA_RB_STP_COMP Bigger than DATA_RB_STP_ATT in 251_03
Modified components: Component Version *Net element UEC.208644 -
*SW-type
*Unit -
-
Change effects: Effects on end-user NA Effects on Operator NA Other effects NA New functionality NA Customer Impact Operation & Maintenance LNT3.0 2.0 - Version 1.0 Confidential
Testing Instructions for the change Pre-requirements: BTS is in normal state, multi-ue attach in cell Test execution: Check PM counter DATA_RB_STP_COMP and DATA_RB_STP_ATT in SEM Expected results: DATA_RB_STP_ATT is bigger than or equal to DATA_RB_STP_COMP Unexpected results: DATA_RB_STP_ATT is smaller than DATA_RB_STP_COMP
CN-id: LNT3.0_29009
Title: Climate control profiling is auto enabled after enable and disable it by SEM Version of the SW-build: LNT3.0_ENB_1304_301_00 Valid for Product(s): Flexi LTE Base Station References:
Reason for the Change Note: Summary of the original problem: Climate control profiling is auto enabled after enable and disable it by SEM How end user/operator could detect the problem: NA Description of the fault: NA Related feature / functionality: NA Dependency on configuration: NA Workaround: NA Description of the correction (incl. risk analysis): NA System effects: NA Faulty component and version: NA LNT3.0 2.0 - Version 1.0 Confidential
Faulty component first delivered in (e.g. release, CD): NA Corrected Fault Reports: 108946ESPE01 Climate control profiling is auto enabled after enable and disable it by SEM
Modified components: Component Version laf.jar Change effects:
*Net element -
*SW-type
*Unit -
-
Effects on end-user NA Effects on Operator NA Other effects NA New functionality NA Customer Impact Operation & Maintenance
Testing Instructions for the change Pre-requirements: BTS is on air, all status is right. Test execution: step1: BTS is on air, all status is right. Go to Module Settings page from BTS commissioning. step2: Click the "In use" button to enable all modules. step3: Select any one of module and click the profile to open the pull-down list. step4: Don not choose any one, just click the profile button again and Click the "In use" button again to disable all modules. step5: Click the "next" button go to next page and click "back" button to see whether the module is enable. Expected results: The module of Climate control profiling is disabled. Unexpected results: The module of Climate control profiling is enabled.
CN-id: LNT3.0_31700 LNT3.0 2.0 - Version 1.0 Confidential
Title: [RL35 main] BTS OM crash after degrade BTS version from 275_00 to 273_99 Version of the SW-build: LNT3.0_ENB_1304_301_00 Valid for Product(s): Flexi LTE Base Station References:
Reason for the Change Note: 115838ESPE04: Summary of the original problem: Missing sync between send and SAaConfigSvcRegistry message leads send crash How end user/operator could detect the problem: It is an occasional issue, Run many times, maybe it will be appear. Description of the fault: BTS crash during BTS start up. Related feature / functionality: Ext-Connection removal Dependency on configuration: NA Workaround: NA Description of the correction (incl. risk analysis): Add a safe sender class to avoid crash. Effects on end-user: BTS crash Effects on operator: OAM crash Faulty component and version: NA Faulty component first delivered in (e.g. release, CD): NA Corrected Fault Reports: 115838ESPE04 [RL35 main] BTS OM crash after degrade BTS version from 275_00 to 273_99 51057ESPE05 [RL35 main] CC&S error with EU id : 441 (0x1B9) after delete config&trs file
Modified components: LNT3.0 2.0 - Version 1.0 Confidential
Component Version *Net element TECHREPAdapter. 263324 h
*SW-type
*Unit -
-
Change effects: Effects on end-user NA Effects on Operator NA Other effects NA New functionality NA Customer Impact 115838ESPE04: Capacity & Performance 51057ESPE05: Capacity & Performance
Testing Instructions for the change Pre-requirements: OAM crash when do auto-configure & auto-connect Test execution: 1. BTS work stable on build 280_00. 2. delete configure and FTM file
Expected results: ENB do auto-configure & auto-connect successfully, and ENB's status is on air Unexpected results: ENB cannot detect RRU, and OAM crash.
CN-id: LNT3.0_31698
Title: Lack of TRS IP counter (Transport Ethernet interface AF) Version of the SW-build: LNT3.0_ENB_1304_301_00 LNT3.0 2.0 - Version 1.0 Confidential
Valid for Product(s): Flexi LTE Base Station References:
Reason for the Change Note: Summary of the original problem: There is no PHB PM counter increment for each queue. How end user/operator could detect the problem: System verification Description of the fault: There is no PHB PM counter increment for each AF and BE queue. Related feature / functionality: QoS, PM counter Dependency on configuration: NA Workaround: NA Description of the correction (incl. risk analysis): while enabling QoS from EM, there is index used to maintain at device Adapter and FastPath for each dscp value. From Device adapter always index used to come with value 1. But FastPath used to calculate it wrongly and while increment PHB counter it value also get wrong . So at FastPath it also made 1. System effects: NA Faulty component and version: NA Corrected Fault Reports: 139164ESPE02 Lack of TRS IP counter (Transport Ethernet interface AF) Modified components: Component Version *Net element aricent_r3_rl50_mp FTM_R3_LN5 2_139164espe02.0_LNT30_MP 1_331.00
*SW-type
*Unit -
-
Change effects: Effects on end-user NA Effects on Operator NA Other effects NA LNT3.0 2.0 - Version 1.0 Confidential
New functionality NA Customer Impact Operation & Maintenance Testing Instructions for the change Pre-requirements: Check the AF counter is OK for operation Test execution: 1. BTS is on air 2. Configure all the DSCP in one queue 3. Configure the egress shaper information to let upload traffic to fill full bandwidth 4. Do UL and DL throughput Expected results: There are ifInPackets and ifOutPackets counters in SEM in one AF display Unexpected results: There is only ifOutPackets counter in SEM in one AF display, lacking of ifInPackets counter
CN-id: LNT3.0_18345
Title: Modify PCI failed even though enableAutoLock=enable Version of the SW-build: LNT3.0_ENB_1304_301_00 Valid for Product(s): Flexi LTE Base Station References:
Reason for the Change Note: Summary of the original problem: when modify pci, should check enableAutoLock in plan file How end user/operator could detect the problem: modify pci and enableAutoLock in plan file, then do commission Description of the fault: in code not check enableAutoLock, but check administrative State. Related feature / functionality: no Dependency on configuration: no Workaround: no Description of the correction (incl. risk analysis): in code check enableAutoLock in plan file LNT3.0 2.0 - Version 1.0 Confidential
Effects on end-user: no Effects on operator: no System effects: no Other effects: no Interface Effects: no Faulty component and version: no Faulty component first delivered in (e.g. release, CD): no Corrected Fault Reports: 140728ESPE02 modify PCI failed even though enableAutoLock=enable Modified components: Component Version *Net element CConf_validator.cls 263015 -
*SW-type
*Unit -
-
Change effects: Effects on end-user NA Effects on Operator NA Other effects NA New functionality NA Customer Impact Operation & Maintenance
Testing Instructions for the change Pre-requirements: 1. eNB is working normally on-air with LNT3.0 load (newer than LNT3.0_ENB_1304_279_00) 2. Keep LNBTS Enable automatic locking value as enable Test execution: Modify physical layer cell identity value for one or more cells via BTS Site manager commission page and send the commission file to eNB Expected results: New physical layer cell identity value was commissioned and activated successfully. Unexpected results: Commissioned and activation failed, and physical layer cell identity kept as old value. LNT3.0 2.0 - Version 1.0 Confidential
Title: RL50 - FSMF fast tune does not work for SyncE, no alarm displayed Version of the SW-build: xyz Valid for Product(s): Flexi LTE Base Station References:
Reason for the Change Note: Summary of the original problem: When using the BTS fast tune option for transmission synchronization when there is SyncE being delivered to the BTS, SSM flag ok, the BTS does not alarm when the fast tune fails. We have tried a number of times to fast tune, each time we click fast tune option, nothing happens, the BTS clocking does not update (BTS Clock Tuning history) but the BTS never alarms. SyncE is definitely configured on the trs, SSM is showing PRC. This fault is to track the lack of alarming, the BTS should alarm if it fails fast tune or even if fast tune is not used, when the BTS periodically tunes the clock every 20mins, if this fails, it should alarm How end user/operator could detect the problem: Reference clock with poor quality Description of the fault: no alarm of 1831 rose when tuning not success. Related feature / functionality: NA Dependency on configuration: NA Workaround: NA Description of the correction (incl. risk analysis): adding the FD rule for handling of fault 1831 System effects: N/A Faulty component and version: FlexiFDrules.txt/26411 Corrected Fault Reports: NA05634595 RL50 - FSMF fast tune does not work for SyncE, no alarm displayed Modified components: LNT3.0 2.0 - Version 1.0 Confidential
Component Version *Net element FlexiFDrules.txt 264115 -
*SW-type
*Unit -
-
Change effects: Effects on end-user NA Effects on Operator NA Other effects NA New functionality NA Customer Impact Operation & Maintenance
Testing Instructions for the change Pre-requirements: eNB on air and SyncE synchronization source available.
Test execution: Select SyncE as synchronization source for the eNB. Start the fast tune process for the eNB.
Expected results: Fast tune is successful and a DAC word calculated and displayed in the tuning history.
Unexpected results: No DAC word is written to the tuning history.
CN-id: LNT3.0_31720
Title: VSWR Major Alarm is not Auto Clear after return the jumper back. Version of the SW-build: LNT3.0_ENB_1304_301_00 Valid for Product(s): Flexi LTE Base Station LNT3.0 2.0 - Version 1.0 Confidential
Reason for the Change Note: Operation & Maintenance Fault Description: When VSWR Major alarm is triggered, the alarm itself cannot be automatically cleared Impact Statement: To Cancel this alarm, it's required eNB resetting. From customer perspective, alarm should be clear automatically when VSWR below the threshold value without resetting eNB Trigger: Trigger VSWR Major Alarm by removing Ant. Cable from the RRU port. After alarm generate, return the Ant Cable back to the port. (Alarm should be exist) Occurrence Rate: 10/10 Detection: VSWR Major Alarm Exist Recovery: In the previous version, it will require RRU resetting or eNB resetting. With new correction, Alarm can be cleared without eNB resetting by start VSWR tuning mode and run it until alarm is cleared. Corrected Fault Reports: 111434ESPE01 VSWR Major Alarm is not Auto Clear after return the jumper back.
Modified components: Component Version *Net element TDL24.03.R04D TDL24.03.R0 4D
*SW-type
*Unit -
-
Change effects: Effects on end-user NA Effects on Operator NA Other effects NA New functionality NA Customer Impact Operation & Maintenance Fault Description: When VSWR Major Alarm is triggered, the alarm itself cannot be automatically cleared Impact Statement: To cancel this alarm, it's required eNB resetting. From customer perspective, alarm should be clear automatically when VSWR below the threshold value without resetting eNB Trigger: Trigger VSWR Major Alarm by removing Ant. Cable from the RRU port. After alarm generate, return the Ant Cable back to the port. (Alarm should be exist) LNT3.0 2.0 - Version 1.0 Confidential
Occurrence Rate: 10/10 Detection: VSWR Major Alarm Exist Recovery: In the previous version, it will required RRU resetting or eNB resetting. With new correction, Alarm can be cleared without eNB resetting by start VSWR tuning mode and run it until alarm is cleared.
Testing Instructions for the change Pre-requirements: eNB is running on RL35 MP2 load, and cells are on air without any alarms. Test execution: 1. remove the jumper cables, and VSWR major alarms and Radio resource switched off alarm appear on the antenna line. 2. return the jumper cable back. 3. try to Tune VSWR threshold, and wait for about 3 minutes, and see that VSWR major alarm and Radio resource switched off are cancelled. 4. exit the VSWR threshold Tune mode. Expected results: VSWR alarm and Radio resource switched off alarm disappeared and never come back again. Unexpected results: VSWR major alarm still there.
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 recommendations for power use and proper disposal of our products and their components. If you should have questions regarding our Environmental Policy or any of the environmental services we offer, please contact us at Nokia Solutions and Networks for additional information. LNT3.0 2.0 - Version 1.0 Confidential
Flexi Multiradio BTS LTE eNB.................................................................................................................................. 5 Using Site Manager to upgrade SW ......................................................................................................................... 6 Using NetAct ............................................................................................................................................................ 7
First Installation ...................................................................................................................................................... 15 Upgrade from iOMS3.0 (R_GOMS6_1.27.1.1 Corr35) to iOMS5.0 ........................................................................ 15 Upgrade from iOMS4.0 (R_GOMS6_1.82.1.0 corr37) to iOMS5.0......................................................................... 19 Upgrade iOMS5.0 to corr24 ................................................................................................................................... 19 Upgrade iOMS5.0 corr24 to corr38 ........................................................................................................................ 20 SON ....................................................................................................................................................................... 21
Operational hints and recommendations .................................................................................................... 21 Checking of the package consistency ........................................................................................................ 22 9.1 9.2
1. PURPOSE The purpose of this document is to describe the actions needed for installing and or upgrading this Release Delivery into the customer’s network.
2. OVERVIEW This document covers Installation Instruction for 2 LTE entities: • Flexi Multiradio BTS LTE (eNB) • LTE iOMS And informs about preparations needed to use SON (Self Organizing Network) features. Standard installation instructions are available in the Customer Documentation library accessible through NOLS [1] at: • Nokia Long Term Evolution Information Center [3] It is required to carefully study content of the library and follow on detailed procedures described in the documents. It will be specified in this document which instruction should be used for installation of certain entity, all exceptions from base procedure will be listed in this document. During the execution of the procedure user will be asked to stop following the official Customer Documentation and execute steps mentioned here.
2.1 Other Relevant Installation Instructions All LTE Customer Documentation, including standard installation procedures, is accessible through NOLS [1] in the section “Product Information Center” Nokia Long Term Evolution Information Center [7] It is very important to check if new Change Deliveries are available – they may contain newer version of the documents
2.2 Supported Hardware and SFP The supported Hardware version as below: Hardware
Supported Hardware
FZHA
A101, A102, A103, A104
FZNC
A101, A102
FZNI
A101
FSMF
A101, A102, A103
FBBA
A101, A102, A103
Note: According to maintenance policy, X version proto type HW are not supported in maintenance phase.
3. PREPARATIONS 1. Hardware used for the installation should be integrated according to the hardware installation guide and all necessary cabling should be already done. Necessary documents can be found in the section “Install and commission” in the Customer Documentation library • For the Flexi Multiradio BTS LTE reference documents are named “Installing Flexi Multiradio BTS LTE…” [2] (Figure 1)
Figure 1
4. SW DOWNLOADING INSTRUCTIONS Software for the eNB and iOMS can be downloaded from NOLS: • Flexi Multiradio BTS LTE: https://online.portal.nsn.com/SWD/?access_key=MTA2OTY2 • LTE iOMS: RL50 1.0: LN5.0 RL50 1.0 SW https://online.portal.nsn.com/SWD/?access_key=MTA4NDQ1 RL50 1.1: LN5.0 RL50 1.1 SW https://online.portal.nsn.com/SWD/?access_key=MTA3Nzg1 RL50 1.2: LN5.0 RL50 1.2 SW https://online.portal.nsn.com/SWD/?access_key=MTA2OTI2 LNT3.0 2.0 - Version 1.0 Confidential
5. SPECIAL CONDITIONS 5.1 Flexi Multiradio BTS LTE eNB NA
5.2 LTE iOMS Before starting the iOMS installation the HW clock in the BIOS of the unit, where software is to be installed should be corrected to reflect current time in UTC/GMT time zone.
5.3 LTE NetAct LTE NetAct should to be upgrade to OSS5.5 in advance. Enable “swUpdateEvent” configuration flag in NetAct tool: Enable “swUpdateEvent” is used to trigger SW download again to LTE eNB when RF module SW doesn’t matched during eNB upgrade with NetAct. This will trigger eNB restart automatically. Notes: this function flag is controlled by NetAct server side.
5.4 Control PC configuration If Control PC is directly connected to the eNB by LMP interface, PC must be set up with IP address & subnet as follows: 1) IP address: 192.168.255.126 2) Network mask: 255.255.252.0 FZNI1
192.168.253.196
FZNI2
192.168.253.204
FZNI3
192.168.253.212
FZNI4
192.168.253.220
FZNI5
192.168.253.228
FZNI6
192.168.253.236
If Control PC is remote connected to the 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.
6. RELEASE DELIVERY UPGRADE INSTRUCTIONS 6.1 Flexi Multiradio BTS LTE eNB Following Upgrade Paths have been verified in lab: •
RL35 P8(LNT3.0_ENB_1304_243_02)MP2 site configurations are:
Click the Update button to do the upgrade. We can monitor the upgrade progress; the elapse time of downloading files is about 10 minutes. Then the eNB will restart. After the eNB startup, login BTSSM, the eNB should be at on air status.
6.3 Using NetAct Pre-checking before SW upgrade: LNT3.0 2.0 - Version 1.0 Confidential
In order to upgrade the target eNBs, a task shall be started manually
From task table, the SW DA task can be viewed and monitored:
10. Several minutes later(after OMS has downloaded the SW to its local folder, OMS will send a message to eNBs to initial SW update), check the local BTSSM connected to the eNB, the following message window shall pop out: LNT3.0 2.0 - Version 1.0 Confidential
11. About 20 minutes later, SW upgrade will finish, eNBs will reboot automatically and also BTSSM reconnected, following message window will be shown on BTSSM:
The following message window may be pop out to reminder the operator to update the BTSSEM version:
Then, normally the eNB will startup with new SW build. 12. After finishing upgrade, NetAct will automatically schedule an SW upload task, the purpose is to upload the latest eNBs’ SW build 20 minutes later after SW activation: LNT3.0 2.0 - Version 1.0 Confidential
7. IOMS Remark 1: If upgrade/update procedure is executed remotely it is recommended to have additional remote connection to Standard Integrated Lights-Out (iLO) management functions for HP ProLiant Blade via iLO management port. iLO allows additional access to blade server serial, text-based console. It gives possibility to monitor and restart blade even when standard access is not available. Please test the possibility of remote access to blade via iLO before starting of iOMS upgrade/update procedure. 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 system reset. If this happens during MSU (Major Software Upgrade) commit phase it will cause outage and continuous reset of iOMS. To prevent I/O buffer overload before MSU commit phase it is advised to change maximum available 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 iOMS SW upgrade commit phase LNT3.0 2.0 - Version 1.0 Confidential
7.1 First Installation For more detail information about iOMS, please refer to documents in NOLS Please access it from here: https://online.portal.nokiasiemensnetworks.com/pic/com/nsn/extranet/pic/controller/productinfoview/pivdo cumentation.do?productId=urn:nsn.com:mxpdm:134-004636&RId=urn:temp:iOMS5.0&CId=&FId=
HW Specification: - HPBlade G6 - HPBlade G8 - HDD 2x300GB Download USB_full_R_GOMS6_1.107.1.0.release_oms.corr16_2x300_G8_HPBlade Below files should be included. InstallGOMS_USB.sh restoretools.tgz USB_full_R_GOMS6_1.107.1.0.release_oms.corr16_2x300_G8_HPBlade.tar.gz USB_full_R_GOMS6_1.107.1.0.release_oms.corr16_2x300_G8_HPBlade.tar.gz.md5sum 1 Prepare USB installation stick by using iOMS4.0 FP_USBboot_v2.5.7, the file size is 765845KB in windows from NOLS. Copy the iOMS software to the USB stick. 2 Mount the USB stick, copy the installation script. Then start installation script by ./InstallGOMS_USB.sh 3 .Wait for script finished, and remove USB stick, and reboot iOMS. After iOMS is running, go to below folder and complete the installation. cd /opt/Nokia/SS_OMSINST/usb/ ./CompleteGOMS_USBInstallation.sh After this step you will be prompted to enter the necessary parameters. 4.Reboot again to finish installation.
7.2 Upgrade from iOMS3.0 (R_GOMS6_1.27.1.1 Corr35) to iOMS5.0 1 Transferring MSU file to OMS 1.1 MSU archive content MSU image is delivered as *.zip file containing: • MSU itself, • partitions description, • md5 sum file for MSU image, • amsurt_std installation scripts package • amsurt script Separate targetBD files for R_GOMS6_1.27.1.1 and R_GOMS6_1.82.1.0 delivered as .tgz file: R_GOMS6_1.27.1.1 • targetBD_R_GOMS6_1.27.1.1.c20_to_R_GOMS6_1.107.1.0.oms64.c16_G6_HPBlade.tgz • targetBD_R_GOMS6_1.27.1.1.c20_to_R_GOMS6_1.107.1.0.oms64.c16_G8_HPBlade.tgz R_GOMS6_1.82.1.0 • targetBD_R_GOMS6_1.82.1.0.c34_to_R_GOMS6_1.107.1.0.oms64.c16_G6_HPBlade.tgz • targetBD_R_GOMS6_1.82.1.0.c34_to_R_GOMS6_1.107.1.0.oms64.c16_G8_HPBlade.tgz LNT3.0 2.0 - Version 1.0 Confidential
1.2 Copying MSU file MSU may be transferred to OMS using SFTP, SCP FTP or USB stick. MSU packages should be copied to /var/mnt/local/backup/ as in this directory usually is a lot of free disk space. Note that proper for OMS release targetBD zip file need to be copied to amsurt_std directory and unpacked, example below. 1.3 Unpacking MSU file To unpack MSU file, simply execute: unzip To unpack targetBD file, simply execute: tar xvf Note that compressing with zip doesn’t save permissions so after unzipping you have to add execute permission to all amsurt scripts. 1.4 Checking amsurt_std content For R_GOMS6_1.82.1.0 and R_GOMS6_1.27.1.1 amsurt_std directory should contain: • MSU .tgz • MSU .md5 • data/ folder • omsswm_major script • partitionsSchema.tgz • proper targetBD .xml • proper targetBD .md5 2 Installing MSU Before you start check if you have technology licence installed on RL30. You should not have it installed and you can verify this using command lmcli listAllLicence. If you have technology licence you should delete it using lmcli deleteLicence before starting MSU procedure. 2.1 Performing pre installation check Go to directory with MSU file: cd /var/mnt/local/backup/amsurt_std/ To check if MSU can be installed on OMS, execute command: ./omsswm_major --check Results will be displayed on screen and stored in /var/log/msu.log 2.2 Installing in two steps: install – activate This scenario should be normally in use. Go to directory with MSU file: cd /var/mnt/local/backup/amsurt_std/ Execute MSU installation: ./omsswm_major Logs from operation will be stored in /var/log/ directory. Wait until installation is done. If it’s finished successfully you can activate new software set. WARNING – this will cause OMS reboot twice. ./omsswm_major --activate After OMS reboots postconfiguration is done automatically in silent mode. 2.3 Installing in single step There is an option to install MSU completely handsfree. In this scenario installer will not interact with operator and will not wait for activation command. OMS will reboot automatically, when installation is done. Go to directory with MSU file: cd /var/mnt/local/backup/amsurt_std/ To start upgrading OMS this way, execute: ./omssm_major --full LNT3.0 2.0 - Version 1.0 Confidential
After OMS reboots postconfiguration is done automatically in silent mode. 2.4 Installing step by step This gives you more control over installation process. Go to directory with MSU file: cd /var/mnt/local/backup/amsurt_std/ Break disk mirroring: ./omsswm_major --separate --disk Disk names are: /dev/cciss/c0d0/ /dev/cciss/c0d1/ By default /dev/cciss/c0d1/ is used. It is recommended to use default settings. Install MSU: ./omsswm_major --install Convert data: ./omsswm_major --convert Activate new software (WARNING – this will cause OMS reboot twice): ./omsswm_major --activate After OMS reboots postconfiguration is done automatically in silent mode.
3 Using execution switches 3.1 Error checking OMS checks for following errors after activation phase is executed: • Postconfiguration – OMS checks if postconfiguration is executed successfully. • Network settings – OMS checks its network settings. • RG’s and RU’s – Oms checks if all RG’s and RU’s are unlocked and enabled. • Network security – OMS checks if network security related information were converted successfully and imported to new software set • Licence files – OMS checks if licence files were imported to new software set • NWI3 connection – OMS checks if NetAct connection can be established • BTSOM connection – OMS checks if is able to accept requests from RNC If any of listed above fails, OMS will trigger automatic fallback to previous version. Automatic fallback requires Recovery Groups to be manually unlocked after fallback is done. You can do it by command: fshascli --unlock --noerror / You can verify MSU procedure in /var/log/msu.log and see if any errors occurred. When automatic postconfiguration starts in RU40 you log is in /var/log/postconfig*.log 3.2 Ignoring all errors It is possible to ignore all errors and disable automatic fallback. It is not recommended to do so. Ignoring errors in single step scenario: ./omsswm_major --full --noHLF In any other case: ./omsswm_major --activate --noHLF 3.3 Ignoring NetAct connection problems It is possible to ignore problems with NetAct connection. This option should be used, when there is no NetAct available for any reason. Ignoring NetAct problem in single step scenario: ./omsswm_major --full --noNetActchecking In any other case: ./omsswm_major --activate -- noNetActchecking 3.4 Locking non default disk It is possible to point, which disk will be locked during upgrade. In normal cases it is recommended to use default value. LNT3.0 2.0 - Version 1.0 Confidential
Using switch in single step scenario: ./omsswm_major --full --disk In step by step scenario: ./omsswm_major --separate --disk 4 Additional conversion scripts If some additional conversion scripts are needed, they are always delivered together with MSU. Scripts are stored in conversionScripts.zip file. Scripts are handled completely handsfree. There is no need for operator to take any action regarding these scripts. 5 Committing new software After MSU new software is not committed automatically. Commit has to be done by operator. Before committing, make sure, that new OMS is working properly. After commit rollback is not possible. To commit, execute: omsswm_major -c 6 Rollback Rollback can be performed manually with command: fsswcli --major --cutover Rollback requires Recovery Groups to be manually unlocked after rollback is done. You can do it by command: fshascli --unlock --noerror / OMS upgrade step by step example: 1. Download MSU image file to local from Tosco server via winSCP tool(set transfer mode as binary);
Figure 26: download file from server with tool 2. Upload MSU image file to OMS /var/mnt/local/users/home/Nemuadmin via winSCP tool(set transfer mode as binary);
Figure 27: set transfer mode as binary 3. SSH to OMS as root user; 4. mkdir /var/mnt/local/backup/amsurt_std; 5. cd /var/mnt/local/backup/amsurt_std/; 6. mv /home/Nemuadmin/MSU_image_file /var/mnt/local/backup/amsurt_std/; 7. tar xvf targetBD_***.tgz; 8. ./omsswm_major --check targetBD_***.xml; 9. ./omsswm_major --separate --disk ; 10. ./omsswm_major --install targetBD_***.xml; 11. ./omsswm_major --convert targetBD_***.xml; 12. ./omsswm_major --activate targetBD_***.xml; 13. After activate, some process will be startup within 20 minutes, please check whether new OMS software is working properly, 1) If yes, you need to commit new software with command “omsswm_major –c” 2) If no, rollback can be performed with command “fsswcli --major --cutover” and “fshascli --unlock -noerror /”;
7.3
Upgrade from iOMS4.0 (R_GOMS6_1.82.1.0 corr37) to iOMS5.0 As above
7.4
Upgrade iOMS5.0 to corr24
NOTICE: the correction can be upgrade after MSU upgrade with executed command“omsswm_major –c”.
1. Install 1 correction level. Files needed for the update are: targetBD_R_GOMS6_1.107.1.0.release_oms.corr17.xml R_GOMS6_1.107.1.0.release_oms.corr17.tar Install correction and create new SW Set (new SW Set will be passive): omsswm_install --full targetBD_R_GOMS6_1.107.1.0.release_oms.corr17.xml Activate SW Set: LNT3.0 2.0 - Version 1.0 Confidential
omsswm_activate --full targetBD_R_GOMS6_1.107.1.0.release_oms.corr17.xml 2. Install more that 1 correction level. For the following example R_GOMS6_1.107.1.0.release_oms.corr16 is installed and update is being done to R_GOMS6_1.107.debug_oms.corr24. Files needed for the update are: R_GOMS6_1.107.1.0.release_oms.corr17.tar R_GOMS6_1.107.1.0.release_oms.corr18.tar R_GOMS6_1.107.1.0.release_oms.corr19.tar R_GOMS6_1.107.1.0.release_oms.corr20.tar R_GOMS6_1.107.1.0.release_oms.corr21.tar R_GOMS6_1.107.1.0.release_oms.corr22.tar R_GOMS6_1.107.1.0.release_oms.corr23.tar R_GOMS6_1.107.1.0.release_oms.corr24.tar targetBD_R_GOMS6_1.107.1.0.release_oms.corr24.xml Install multiple corrections and create new SW Set (new SW Set will be passive): omsswm_install --full targetBD_R_GOMS6_1.107.1.0.release_oms.corr24.xml Activate SW Set: omsswm_activate --full targetBD_R_GOMS6_1.107.1.0.release_oms.corr24.xml * Note, in case of the correction is need to downgrade, then Files needed - only one xml file to correction level you want to downgrade, like: targetBD_R_GOMS6_1.107.1.0.release_oms.corr16.xml Uninstall corrections and create new SW Set (new SW Set will be passive): omsswm_install --full targetBD_R_GOMS6_1.107.1.0.release_oms.corr16.xml Activate SW Set: omsswm_activate --full targetBD_R_GOMS6_1.107.1.0.release_oms.corr16.xml
7.5 Upgrade iOMS5.0 corr24 to corr38 Download SW from following three links to get correction 25 to correction 38. RL50 1.0: LN5.0 RL50 1.0 SW https://online.portal.nsn.com/SWD/?access_key=MTA4NDQ1 RL50 1.1: LN5.0 RL50 1.1 SW https://online.portal.nsn.com/SWD/?access_key=MTA3Nzg1 RL50 1.2: LN5.0 RL50 1.2 SW https://online.portal.nsn.com/SWD/?access_key=MTA2OTI2 Check SH1 check sum of the downloaded files.. Unzip all archives R_GOMS6_1.107.1.0.release_oms.corrXX.zip and install the corrections Corr25 to Corr38: Files needed for update are: R_GOMS6_1.107.1.0.release_oms.corr25 R_GOMS6_1.107.1.0.release_oms.corr26 R_GOMS6_1.107.1.0.release_oms.corr27 R_GOMS6_1.107.1.0.release_oms.corr28 R_GOMS6_1.107.1.0.release_oms.corr29 R_GOMS6_1.107.1.0.release_oms.corr30 R_GOMS6_1.107.1.0.release_oms.corr31 R_GOMS6_1.107.1.0.release_oms.corr32 R_GOMS6_1.107.1.0.release_oms.corr33 R_GOMS6_1.107.1.0.release_oms.corr34 LNT3.0 2.0 - Version 1.0 Confidential
R_GOMS6_1.107.1.0.release_oms.corr35 R_GOMS6_1.107.1.0.release_oms.corr36 R_GOMS6_1.107.1.0.release_oms.corr37 R_GOMS6_1.107.1.0.release_oms.corr38 targetBD_ R_GOMS6_1.107.1.0.release__oms.corr38.xml For all needed files there must be a checksum file with the same file name but extension ‘md5’. Please do not change this file, it has to be in UNIX format and will be used by the installation procedure. Install multiple corrections and create new SW Set : omsswm_install --full targetBD_ R_GOMS6_1.107.1.0.release_oms.corr38.xml omsswm_activate --full targetBD_ R_GOMS6_1.107.1.0.release_oms.corr38.xml If during activation following error will appear: OMS will be restarted after successful activation... CRITICAL error: FlexiPlatform activation script returned error code: 1 Please use following workaround: Unpack corr tar files to obtain postupgrade scripts and copy it to iOMS Activate corr using fsswcli activation script fsswcli --set --activate R_GOMS6_1.107.1.0.release_oms.corr38 after reboot run Post-upgrade activation scripts one by one with approximately 30 sec interval. Important: Please carefully check name of script. It should be: R_GOMS6_1.107.1.0.release_oms.corrXXX_postsh_upgrade.sh • “R_GOMS6_1.107.1.0.release_oms.corr25_postsh_upgrade.sh” • “R_GOMS6_1.107.1.0.release_oms.corr26_postsh_upgrade.sh” • “R_GOMS6_1.107.1.0.release_oms.corr27_postsh_upgrade.sh” • “R_GOMS6_1.107.1.0.release_oms.corr28_postsh_upgrade.sh” • “R_GOMS6_1.107.1.0.release_oms.corr29_postsh_upgrade.sh” • “R_GOMS6_1.107.1.0.release_oms.corr30_postsh_upgrade.sh” • “R_GOMS6_1.107.1.0.release_oms.corr31_postsh_upgrade.sh” • “R_GOMS6_1.107.1.0.release_oms.corr32_postsh_upgrade.sh” • “R_GOMS6_1.107.1.0.release_oms.corr33_postsh_upgrade.sh” • “R_GOMS6_1.107.1.0.release_oms.corr34_postsh_upgrade.sh” • “R_GOMS6_1.107.1.0.release_oms.corr35_postsh_upgrade.sh” • “R_GOMS6_1.107.1.0.release_oms.corr36_postsh_upgrade.sh” • “R_GOMS6_1.107.1.0.release_oms.corr38_postsh_upgrade.sh”
7.6 SON SON is a set of features which enables operator to configure base station by connecting it to the network. To enable usage of SON facilities some preparation steps must be taken. It is described in Customer Documentation library in section “Functional Area DescriptionOperability-Configuration Management-SON management” chapter 4 “SON management” [5]. Main activities concern DHCP server configuration and certificates management. Descriptions and hints about SON feature usage can be found also in Customer Documentation for NetAct.
9. CHECKING OF THE PACKAGE CONSISTENCY 9.1 Flexi Multiradio BTS LTE eNB In order to check the package consistency after Flexi Multiradio BTS LTE SW update, please ensure that the procedure “Update SW to BTS site” is terminating successfully.
9.2 LTE iOMS Chapter 6 “Performing checks after installation and commissioning of iOMS” from “Installing and commissioning LTE iOMS” [6] document contains steps, which should be executed to double check if the installation of iOMS was finished successfully. Document is available in the Customer Documentation library.
10. FALLBACK N/A
11. APPENDICES / REFERENCES
[1] NOLS - Nokia Online Services log in link: https://online.portal.nsn.com [2] "Commissioning Flexi Multiradio BTS LTE", DN0972163, Issue 02 [3] Link to Nokia Long Term Evolution Information Center: https://online.portal.nsn.com/pic/com/nsn/extranet/pic/controller/productinfoview/pivdocumentation.do?productId=u rn:nsn.com:mxpdm:134-007609&RId=urn:temp:Flexi-TD-LBTS3.0&CId=urn:temp:Operating-documentation&FId= [4] "Upgrading from LTE OMS 3.0 or LTE OMS 4.0 to LTE OMS 5.0", DN0983101, Issue 01 [5] "LTE System Upgrade", DN09147545, Issue 01 [6] "Installing and Commissioning LTE iOMS", DN0956464, Issue 05A [7] Nokia Online Services TD-LTE LNT3.0 customer documentation: https://online.portal.nsn.com/pic/com/nsn/extranet/pic/controller/productinfoview/pivdocumentation.do?productId=u rn:nsn.com:mxpdm:134-007609
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 recommendations for power use and proper disposal of our products and their components. If you should have questions regarding our Environmental Policy or any of the environmental services we offer, please contact us at Nokia Solutions and Networks for additional information. LNT3.0 2.0 - Version 1.0 Confidential
Purpose ....................................................................................................................................... 3 Test phases and Amount of test cases ........................................................................................ 3 Test Environment ........................................................................................................................ 3 Description of test phase entities ................................................................................................. 3 Appendices / References............................................................................................................. 4
Contact: Contact your local Nokia Solutions and Networks support
1. PURPOSE This document presents the testing results for LTE RL35 MP2 release delivery. . 2. TEST PHASES AND AMOUNT OF TEST CASES The following table summarizes the amount of test cases.
Test Phase
Total
Passed
Passed Rate
Correction Testing
56
56
100%
Regression Testing
317
317
100%
Software Update Installation Testing
338
338
100%
Note: FiVe test cases are all passed and KPI performance is same as P8’s.
3. TEST ENVIRONMENT Test environment is build according to chapter “System Descriptions” [1] in Customer Documentation library 4. DESCRIPTION OF TEST PHASE ENTITIES Correction Testing All individual corrections have passed sub-system testing. All individual corrections have passed entity testing.
Regression Testing Regression test verifies the unchanged parts of a product after parts of the product have been changed. It is a way to ensure that the change did not affect anything else and that there are no unexpected side effects.
Software Update Installation Testing The target is to validate that the entity in an older version can be updated as expected to the version to be released. Update was tested from RL35 P8//MP1/PP1.1 to RL35 MP2.0.
