Professional Documents
Culture Documents
SRAN21A 2.0 Release Delivery Summary v1
SRAN21A 2.0 Release Delivery Summary v1
Approved: 30-Jun-2021
Contact
Contact your local Nokia support.
Summary of changes
1.1 Corrections
File SRAN21A_2.0_LGF.xlsx provides the list of Generic Faults fixed in this software delivery.
These files are provided with the load and available from Support Portal - Software Supply Tool (SwST).
The following corrections are delivered in SRAN21A 2.0 SW on top of SRAN21A 1.1 SW. Correction details can
be found under “Customer Communication forms” in the LGF document.
IMPORTANT:
Please note that the process of communicating the SW corrections in Delivery Documentation has changed
on 01.01.2021.
The List of Generic Faults (LGF) became a master document describing both: open and corrected faults.
For this purpose, the format of LGF document was redesigned. The document was extended with additional
fields describing the SW correction details (like root cause, correction description, test requirements).
*- already corrected in previous release for details refer to customer communication form (CCF)
1. Limitation in FDSW
Due to limitation in current FDSW (Factory Delivery SW) it is not possible to upgrade software build on top of
Classical BTS FDSW if size of target software build is bigger than 4GB.Current SRAN21A Classical BTS
software build size is bigger than 4GB. So, Upgrade on top of FDSW (for instance: new site installation or
after some recovery case where SBTS fallbacks to FDSW), steps are:
-Migration from FDSW to SRAN20A, SRAN20B or SRAN20C load (intermediate load)
-New Migration from this intermediate load to SRAN21A.
Note:
-Alternative way is to manually upgrade FDSW to the latest FDSW19A ->
LN_WN_FDSW19A_0000_000142_000000 (or newer FDSW product release when available) and perform then
an upgrade to the target SRAN package.
- FDSW release with correction for that issue was given already to the factories. If HW unit with the FDSW
version LN_WN_FDSW19A_0000_000142_000000(or newer) is installed, no need to perform this
intermediate upgrade.
- Limitations are related to manual SW installation only. PnP works correctly regardless package size.
- This limitation is valid for all the HW types.
3. Operator Hint for LTE5551: CA operation robustness for CBSD enbs(Intra enb)
When using LTE3663(CBRS standalone) and LTE5551(CA operation robustness for CBSD enbs(Intra enb)), the
sCellActivationMethod need to be set as nonGBRBufferBasedStepWise(1).
2. RELEASED OBJECTS
Following entities are part of the SRAN21A 2.0 SW delivery:
Entity ID
Flexi Multiradio BTS SingleRAN
SRAN21A 2.0
AirScale BTS Single RAN
PDL Validation Service nokia-pvs-1.1.20210617104210.6d4ee4-1
BTS Conversion Service BTS Conversion Service 0.1.35
* SBTS SW A5/0 CMCC load is a restricted package and can be used only after confirmation with
corresponding NPI Project Manager
* SBTS SW A5/4 CMCC load is a restricted package and can be used only after confirmation with
corresponding NPI Project Manager
The newly released software and corresponding release documentation can be downloaded from:
Support Portal >> Services >> Download: SwST >> Category: Radio Network >> Sub-Category: Radio Network
Solutions >> Single RAN >> SRAN 21A SW
The following are the new features delivered in SRAN21A 2.0 on top of SRAN21A 1.1 SW:
N/A
4. UPGRADE INSTRUCTIONS
Please refer to the Nokia documentation, the ‘SRAN system upgrade and migration section, available from
Nokia Discovery Center
4.1 Prerequisites
Before performing a SW upgrade in FSMF or AirScale System Module (later: Flexi System Module), please
ensure the following:
For 21A common SW packages are released (meaning that the package includes software for both FSMF and
AirScale).
Supported System
From release: From build/FDSW load:
Module/Hw type
LN_WN_FDSW19_ASIA_0000_000043_000000 FSMF
FDSW19A
LN_WN_FDSW19_ASIA_0000_000044_000000 ASIAA
LN_WN_FDSW19_FSIH_0000_000042_000000 FSIH
LN_WN_FDSW19_FSIH_0000_000043_000000 FSMF
LN_WN_FDSW21A_0000_000113_000000 ASIA / ASIAA
FDSW21A LN_WN_FDSW21A_0000_000115_000000 ASIB / ASIBA
LN_WN_FDSW21A_0000_000130_000000 ASIA/ ASIAA /ASIB / ASIBA
Supported HW items are defined in the "Single RAN Compatibility” document /2/.
Supported Network Elements are described in the "Single RAN Compatibility“ document /2/.
The upgrade order and SW levels for different network elements need to be checked from the corresponding
compatibility documentation.
4.8 SETUP
- IP settings for the PC network card (straight Ethernet cable is needed to connect to the LMP port):PC
IP address 192.168.255.126 ,
- Subnet mask 255.255.255.0 (with /24 mask),
- Gateway is not defined
WebEM will connect to the BTS via WebSocket connection remotely using the M-Plane IP or using the local
management port (LMP).
In case of SBTS17A and onwards, WebEM will connect to BTS on the port 443.
Authentication is always enabled either with the default username/password (Nemuadmin / nemuuser) or a
user defined username/password. Therefore, the correct username and password must be used to log in to
the BTS.
The purpose of this chapter is to describe the actions needed before and after the SBTS software upgrade
to ensure smooth troubleshooting if the upgrade fails for any reason.
Preventive actions need to be done to make troubleshooting possible afterwards, see steps below:
1. Collect and save BTS Snapshots from different configurations (for example, from one cluster).
2. Collect and save both active and passive SW versions information from the network.
3. Save the active SCFs (Site Configuration File) as back-up copies.
Following actions should be done after the SW download and activation if upgrade fails for any reason, see
steps below:
If there are problems with the upgraded MRBTS, you can rollback the original software
package using Software Manager. Note that to be able to restore the original situation,
there cannot be any configuration changes in MRBTS before the rollback.
Please, refer to the documents “SRAN System Upgrade and Migration” /4/ and BTS Upgrade and Migration /5/.
4.12 SW ROLLBACK
SW rollback is a SW fallback manually-initiated using the Web Element Manager. The operator can trigger SW
rollback when the key services are not activated successfully after the SW upgrade. Note that SW rollback is
only guaranteed if the source SW version has not been removed or overwritten in a non-volatile storage (NVS).
The SW rollback is done with the SW stored in the passive file system and no SW download from the server is
the part of the operation. If the passive SW has been overwritten with a different SW version, the rollback to
the former release is not possible.
A software rollback to the stored SW load restores the earlier configuration. If there has been a major network
reconfiguration after the upgrade, such as reconfiguring the eNB from IPv4 to IPv6 or updating the operator
certificates, then the network connectivity issues can occur after the rollback. Reconfigurations after the SW
upgrade must be evaluated before triggering the SW rollback to avoid a service outage.
You can rollback to the previous software and SBTS configuration data.
1. Launch WebEM / NetAct SWM.
2. Start SW rollback operation.
3. SBTS starts up with previous SW.
For more detailed instructions, refer to the document SRAN System Upgrade and Migration /4/.
Restore Factory Settings Tool (RFSTool) can be used to recover the System Module back to the factory
settings. The restore procedure with RFSTool should be used whenever the regular recovery procedures
(including resets, reconfiguration, SW download) are not possible or they do not recover the fault state.
RFSTool (including MS executable application and the user guide) is delivered with SBTS19A SW release. Please
read the tool instructions carefully before using it.
For more information about RFSTool, see also Technical Support Notes: TS-SRAN-HW-0080 /6/ and TS-SRAN-
HW-0108 /1/.
5. COMPATIBILITY
In line with global release compatibility (see the Compatibility Matrix from Nokia Discovery Center).
Unless otherwise stated, it is recommended to first upgrade the master technology (that is, LTE for GSM-LTE
configurations) as the SW management of Radio Modules in RF Sharing is done via the master System Module
only.
Note: For the newest information and restrictions regarding the RF-Sharing please see Classical RF Sharing
Compatibility Matrix in Discovery Center.
6. APPENDIXES/REFERENCES
This chapter presents the testing results for SRAN21A_2.0 SW delivery. Findings are included in LGF report.
The following table summarizes performed test cases in corresponding test phase.
Correction Testing
The target is to verify whether the introduced changes/corrections solve the reported issues.
Regression Testing
The target is to verify whether the introduced changes/corrections do not cause any unexpected side effects. The
aim of regression testing is also to ensure that all released functionalities work as expected in the E2E environment.
It covers also performance testing, which is executed to determine how the system performs in terms of
responsiveness and stability under a particular load/traffic. It serves to:
- collect KPI measurements that are compared against defined KPI targets and KPIs from the previous
releases,
- check whether the system can continuously function well in or above a defined period.
To ensure SRAN / TDD CA compatibility, both technologies must be upgraded to the compatible SW levels.
The target is to validate if the entity can be updated/upgraded from the old to the newly released SW version.
The upgrade was tested with the released upgrade paths which are listed in the Release Upgrade Instructions
documents.
The time highlights in the above table has been mentioned for the previous releases and it depends on actual system
load at the time of execution and may vary from the values listed above.
This chapter describes the summary of SRAN21A deliveries via Software Supply Tool and recommended SW versions.
The recommendation is based on SW versions used during SRAN System Verification and Integration Verification
testing phase.
Recommendation for the live networks is to upgrade to the latest released SW combination listed in below table
however it is supported to continue with existing software levels as long as the generic SRAN compatibility
requirements are fulfilled:
- Compatibility matrix (Discovery Center > Compatibility Matrix > Access Matrix)
- Compatibility document in Customer Documentation (Discovery Center > Radio Network > Radio
Network Solutions > Operating Documentation)
NetAct19
SP2008+FP764,
NetAct
WCDMA SP2011+FP746,
BSC AirScale RNC20 mcRNC AirScale
SRAN21A 0.1 SBTS21A 0.1 OMS NetAct19 SP2008,
FP21A BSC FP21A 1.0 FP21A RNC FP21A
FP21A NetAct19 SP2011,
NetAct20 SP2009,
NetAct20 SP2011,
NetAct20 SP2102
NetAct19
SP2008+FP764,
NetAct
WCDMA SP2011+FP746,
BSC AirScale RNC20 mcRNC AirScale
SRAN21A 0.1.1 SBTS21A 0.1.1 OMS NetAct19 SP2008,
FP21A BSC FP21A 1.0 FP21A RNC FP21A
FP21A NetAct19 SP2011,
NetAct20 SP2009,
NetAct20 SP2011,
NetAct20 SP2102
NetAct19
SP2008+FP764,
NetAct
WCDMA SP2011+FP746,
BSC AirScale RNC20 mcRNC AirScale
SRAN21A 0.2 SBTS21A 0.2 OMS NetAct19 SP2008,
FP21A BSC FP21A 1.0 FP21A RNC FP21A
FP21A NetAct19 SP2011,
NetAct20 SP2009,
NetAct20 SP2011,
NetAct20 SP2102
NetAct19
SP2008+FP764,
NetAct
AirScale WCDMA SP2011+FP746,
BSC AirScale RNC20 mcRNC
SRAN21A 1.0 SBTS21A 1.0 RNC FP21A OMS NetAct19 SP2008,
FP21A BSC FP21A 1.0 FP21A
0.0.1 FP21A NetAct19 SP2011,
NetAct20 SP2009,
NetAct20 SP2011,
NetAct20 SP2102
NetAct19
SP2008+FP764,
NetAct
AirScale WCDMA SP2011+FP746,
BSC AirScale RNC20 mcRNC
SRAN21A 1.1 SBTS21A 1.1 RNC FP21A OMS NetAct19 SP2008,
FP21A BSC FP21A 1.0 FP21A
0.0.1 FP21A NetAct19 SP2011,
NetAct20 SP2009,
NetAct20 SP2011,
NetAct20 SP2102
Legend:
SW package provided before the corresponding delivery (with previous delivery)
New SW package (provided in corresponding delivery)
Customer specific delivery
The following table describes the RF SW versions included in the SBTS21A 2.0 SW delivery.
SW item SW version
BTS SW SBTS21A_ENB_0000_001721_000000
RF MEDUSA MED28.02.R52A
RF VEGAS VEG21.06.R02
RF FRM FRM28.02.R20A
RF FRM3 FRM31.05.R03
RF FRM5 FRM51.02.R18S
This document is intended for use by Nokia's customers (“You”) only, and it may not be used except for the purposes defined in the
agreement between You and Nokia (“Agreement”) under which this document is distributed. No part of this document may be used,
copied, reproduced, modified or transmitted in any form or means without the prior written permission of Nokia. If You have not
entered into an Agreement applicable to the Product, or if that Agreement has expired or has been terminated, You may not use this
document in any manner and You are obliged to return it to Nokia and destroy or delete any copies thereof.
The document has been prepared to be used by professional and properly trained personnel, and You assume full responsibility
when using it. Nokia welcomes your comments as part of the process of continuous development and i mprovement of the
documentation.
This document and its contents are provided as a convenience to You. Any information or statements concerning the suitability,
capacity, fitness for purpose or performance of the Product are given solely on an “as is” and “as available” basis in this document,
and Nokia reserves the right to change any such information and statements without notice. Nokia has made all reasonable efforts
to ensure that the content of this document is adequate and free of material errors and omissions, and Nokia will correct errors that
You identify in this document. Nokia's total liability for any errors in the document is strictly limited to the correction of such error(s).
Nokia does not warrant that the use of the software in the Product will be uninterrupted or error-free.
NO WARRANTY OF ANY KIND, EITHER EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO ANY WARRANTY OF AVAILABILITY,
ACCURACY, RELIABILITY, TITLE, NON-INFRINGEMENT, MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE, IS MADE IN
RELATION TO THE CONTENT OF THIS DOCUMENT. IN NO EVENT WILL NOKIA BE LIABLE FOR ANY DAMAGES, INCLUDING BUT NOT
LIMITED TO SPECIAL, DIRECT, INDIRECT, INCIDENTAL OR CONSEQUENTIAL OR ANY LOSSES, SUCH AS BUT NOT LIMITED TO LOSS OF
PROFIT, REVENUE, BUSINESS INTERRUPTION, BUSINESS OPPORTUNITY OR DATA THAT MAY ARISE FROM THE USE OF THIS DOCUMENT
OR THE INFORMATION IN IT, EVEN IN THE CASE OF ERRORS IN OR OMISSIONS FROM THIS DOCUMENT OR ITS CONTENT.
This document is Nokia proprietary and confidential information, which may not be distributed or disclosed to any third parties
without the prior written consent of Nokia.
Nokia is a registered trademark of Nokia Corporation. Other product names mentioned in this document may be trademarks of their
respective owners.
This product may present safety risks due to laser, electricity, heat, and other sources of danger.
Only trained and qualified personnel may install, operate, maintain or otherwise handle this product and only after having
carefully read the safety information applicable to this product.
The safety information is provided in the Safety Information section in the “Legal, Safety and Environmental Information”
part of this document or documentation set.
Nokia is continually striving to reduce the adverse environmental effects of its products and services. We would like 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 for any additional information.