WCDMA RAN, Rel. WCDMA 17, Operating Documentation, Issue 02, Documentation Change Delivery 1 WCDMA RAN, Rel. WCDMA 17, System Upgrade DN0980322 Issue 03B Approval Date 2016-11-17
WCDMA RAN, Rel. WCDMA 17, System Upgrade
The information in this document applies solely to the hardware/software product (“Product”) specified herein, and only as specified herein. Reference to “Nokia” later in this document shall mean the respective company within Nokia Group of Companies with whom you have entered into the Agreement (as defined below). This document is intended for use by Nokia's customers (“You”) only, and it may not be used except for the purposes defined in the agreement between You and Nokia (“Agreement”) under which this document is distributed. No part of this document may be used, copied, reproduced, modified or transmitted in any form or means without the prior written permission of Nokia. If You have 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 improvement 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. Copyright © 2016 Nokia. All rights reserved.
f
Important Notice on Product Safety This product may present safety risks due to laser, electricity, heat, and other sources of danger. Only trained and qualified personnel may install, operate, maintain or otherwise handle this product and only after having carefully read the safety information applicable to this product. The safety information is provided in the Safety Information section in the “Legal, Safety and Environmental Information” part of this document or documentation set.
Nokia is continually striving to reduce the adverse environmental effects of its products and services. We would like 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.
2
© 2016 Nokia
DN0980322 Issue: 03B
WCDMA RAN, Rel. WCDMA 17, System Upgrade
Table of Contents This document has 18 pages Summary of changes..................................................................... 6 1
System upgrade overview..............................................................8
2
Instructions for upgrade............................................................... 13
3
Fallback/rollback to previous system release...............................17
DN0980322 Issue: 03B
© 2016 Nokia
3
WCDMA RAN, Rel. WCDMA 17, System Upgrade
List of Figures Figure 1
4
WCDMA RAN upgrade path.................................................................9
© 2016 Nokia
DN0980322 Issue: 03B
WCDMA RAN, Rel. WCDMA 17, System Upgrade
List of Tables Table 1
Nokia RU releases mapping to 3GPP................................................ 11
Table 2
Common terms................................................................................... 12
Table 3
Requirements and recommendations.................................................13
Table 4
Network elements paths and upgrade documentation....................... 15
Table 5
Reference documentation and technical notes.................................. 16
DN0980322 Issue: 03B
© 2016 Nokia
5
Summary of changes
WCDMA RAN, Rel. WCDMA 17, System Upgrade
Summary of changes Changes between document issues are cumulative. Therefore, the latest document issue contains all changes made to the previous issues.
g
Note: Please Note: Flexi Lite’s features are planned separately. Please consult your Nokia contact for further information. Changes between issues 03A (2016-09-09, WCDMA17) and 03B (2016-11-17, WCDMA17) Instructions for upgrade •
The Network elements paths and upgrade documentation table has been updated.
Changes between issues 03 (2016-0 7-14, WCDMA17) and 03A (2016-09-09, WCDMA17) System upgrade overview • •
Prerequisite information has been updated. The Overall WCDMA 16 to WCDMA 17 System Upgrade scenario section has been updated.
Instructions for upgrade • •
The Requirements and recommendations table has been updated. The Network elements paths and upgrade documentation table has been updated.
Fallback/rollback to previous system release •
A note has been added related to BTS software fallback.
Changes between issues 02A (2015-11-19, WCDMA16) and 03 (2016-07-14, WCDMA17) System upgrade overview •
The Nokia RU releases mapping to 3GPP table has been updated to include WCDMA 17.
Instructions for upgrade •
The Network elements paths and upgrade documentation table has been updated.
Fallback/rollback to previous system release • •
Rollback of mcRNC has been updated. BTS software fallback has been updated.
Changes between issues 02 (2015-07-15, WCDMA 16) and 02A (2015-11-19, WCDMA16) •
6
The Network elements paths and upgrade documentation table has been updated.
© 2016 Nokia
DN0980322 Issue: 03B
WCDMA RAN, Rel. WCDMA 17, System Upgrade
Summary of changes
Changes between issues 01C (2014-10-29, RU50 and RU50 EP1) and 02 (2015-0715, WCDMA 16)
•
In WCDMA 16 the Flexi Direct documents have been separated from RNC documentation due to different release cycle.
•
System upgrade overview has been updated.
•
Instructions for upgrade has been updated.
•
Fallback/rollback to previous system release has been updated.
DN0980322 Issue: 03B
© 2016 Nokia
7
System upgrade overview
WCDMA RAN, Rel. WCDMA 17, System Upgrade
1 System upgrade overview About upgrade procedure The upgrade procedure is a series of actions that must be performed in order to upgrade WCDMA RAN from a current release to a newer one. Prerequisites The prerequisite for WCDMA 17 system upgrade is that all network elements are at the WCDMA 16 level. Upgrading of core network elements should be performed beforehand. Note that, however, it is not in the scope of this document. The compatibility of core network elements towards the new WCDMA 17 release features must be verified before any WCDMA 17 system upgrade actions are started. System upgrade principles System upgrade refers to the software (SW) and hardware (HW) upgrade of the following WCDMA RAN network elements: • • • •
NetAct OMS RNC BTS
The upgrade procedure is conducted in a top-down approach. It starts with NetAct, followed by the OMS, RNC, and finally BTS upgrade. Note that RNC refers to two controller products: IPA-RNC and mcRNC. Each product is referred to with its own name wherever applicable. Apart from the software build upgrade, conversion of configuration data (for example: LDAP parameters, RNW configuration) is performed automatically for all the network elements. Upgrade path for WCDMA RAN network elements Top-down approach assumes that the upgrade is performed in the specific order. Yet, it is not necessary to upgrade all network elements of one hierarchy at once. It is because backward compatibility ensures that the network element at higher hierarchy level is capable of networking with the network element of lower hierarchy running at an earlier SW level.
8
© 2016 Nokia
DN0980322 Issue: 03B
WCDMA RAN, Rel. WCDMA 17, System Upgrade
Figure 1
System upgrade overview
WCDMA RAN upgrade path
tep Netact
release n Step 2
t o p d o w n
OMS
OMS
release n
release n-1
Step 3 RNC (1)
RNC (2)
RNC (3)
release n
release n-1
release n-1
Step 4 BTS (1)
BTS (2)
BTS (3)
release n
release n-1
release n-1
Overall WCDMA 16 to WCDMA 17 System Upgrade scenario Note that service degradation and partial service loss cannot be fully avoided during upgrade. Therefore, it is highly recommended to perform the upgrade steps during periods of low traffic. Actors: Operation and Maintenance Engineer Preconditions : The following conditions must be met before the upgrade can be carried out: • • • •
Network system is available and active with WCDMA 16. Interfaces NetAct <=> OMS <=> RNC <=> BTS are up and running. SW packages, including the SW files for the new WCDMA 17 release, are available. There are no HW outages that could prevent access to one or more Network Elements (NEs) to be upgraded.
Description 1.
Preparation of SW loads for the new release and storing in repository. New NetAct SW load as well as new OMS SW load are stored on the work station. The SW loads for the NEs that are controlled from NetAct SWM (Flexi BTS including TRS) are stored in NetAct repository. 2. Preparation of license files for new optional features and storing in NetAct LM (optional). License file preparation is not a mandatory prerequisite; instead licenses for new features can be added later after the SW upgrade is finished. 3. NetAct system SW upgrade to the version that supports the new Node element SW versions. The following preparation steps are executed: • •
checking available disk space backing-up Oracle database version n-1 and customer-specific configuration
Next, the following occurs: • • •
DN0980322 Issue: 03B
The NetAct system OSS n-1 is shut down. NetAct version OSS n SW is installed. OSS n is activated.
© 2016 Nokia
9
System upgrade overview
WCDMA RAN, Rel. WCDMA 17, System Upgrade
• •
Scripts support database migration from OSS n-1 to OSS n. Post-checks are performed to verify if NetAct applications work properly.
It is assumed that NetAct upgrade is performed at low traffic times to minimize impact on service. 4. OMS upgrade •
•
•
•
Either the Remote CLI solution via SSH or NetAct Software Manager is used for the OMS upgrade. OMSs are upgraded sequentially. Note that it is not mandatory to upgrade all OMSs of the system before upgrading RNCs and/or BTSs. Before upgrading an RNC, however, the associated OMS(s) should be upgraded using a top-down approach. The operator confirms that the OMS is ready to be upgraded to WCDMA 17. Health checks shall be executed from NetAct and can consist of verifying there are no outstanding alarms or failures and executing status checks indicate that the OMS is functioning normally on WCDMA 16. The OMS System Status View GUI (delivered by RAN2699: OMS System Status View , which is an optional feature) is used to check OMS status and alarms. It can be launched from OMS Element Manager web application which is accessible from NetAct. The operator can also view OMS alarms in NetAct alarm monitoring window. The operator can confirm that the OMS is on the expected SW version before upgrading from NetAct SWM by executing a SW upload operation or by checking the SW version at the OMS CLI.
5. RNC upgrade •
•
• •
•
•
It is assumed that operators lower the risk and minimize total outage times by performing RNC upgrade sequentially. Note that it is not mandatory to upgrade all RNCs of the system before upgrading BTSs. Before upgrading a BTS, however, the associated RNC should be upgraded using a top-down approach. mcRNC and IPA-RNC upgrade can only be triggered from the command line of a locally connected laptop. The command line terminal can be accessed remotely. NetAct Software Manager cannot be used to upgrade RNC to WCDMA 17. The operator can check RNC alarm status from NetAct Alarm Monitoring GUI, OMS FM GUI, RNC MML (IPA-RNC) or SCLI (mcRNC). The operator performs health checks locally to confirm that the RNC is ready to be upgraded to WCDMA 17. Health checks can consist of verifying there are no outstanding alarms or failures and executing status checks that the RNC is functioning normally on WCDMA 16. The operator performs prechecks locally to confirm that the RNC is ready to be upgraded to WCDMA 17. The prechecks are included in the RNC upgrade procedure. The operator can confirm that the RNC is on the expected SW version before the upgrade from NetAct SWM by executing a SW upload operation or by using RNC MML/SCLI.
6. BTS upgrade •
10
BTS SW upgrade is supported remotely using NetAct Software Manager (SWM) or from the integrated BTS Site Manager (SM). The BTS can also be locally upgraded from a locally connected BTS SM. Several BTSs can, but do not need
© 2016 Nokia
DN0980322 Issue: 03B
WCDMA RAN, Rel. WCDMA 17, System Upgrade
•
•
g
System upgrade overview
to, be upgraded in parallel. NetAct, OMS, and RNC are able to operate with a mixture of BTSs running in release n and n-1. After the upgrade, BTS configuration data is uploaded to stay in sync with data repository in NetAct. Prior to triggering a BTS upgrade the operator must confirm that all BTS are connected to the system, there are no critical alarms on any BTS and that all BTSs to be upgraded are running on the expected, compatible SW version prior to upgrade. The operator can view alarms for all BTSs managed by that NetAct in the NetAct alarm monitoring window. Individual BTS alarms can also be viewed at BTS Site Manager (either locally connected BTS Site Manager (SM) or NetAct Integrated BTS SM). Note: The BTS fault 61006 (BTS booted at $date due to $RCause) is raised during software upgrade from WCDMA16 to WCDMA17 or during rollback from WCDMA17 to WCDMA16 because of a change in the clock control system synchronization application (CCSSA) image. This requires an additional BTS restart and extends the software activation time.
•
The operator can confirm that all of the BTSs are on the expected SW version before and after the upgrade from NetAct SWM by executing a SW upload operation in bulk for all BTS. The SW version on individual BTS can also be checked from BTS Site Manager.
7. Cleanup (optional) •
NetAct and OMS repositories can be cleaned from old NE SW and old NE configuration data. The cleanup is not an automatic action, but it can be triggered by users explicitly (for example by overwriting old SW).
Relationship between Nokia RU releases and 3GPP releases Table 1
Nokia RU releases mapping to 3GPP RAS Release
3GPP Release
WCDMA 17
Rel11
WCDMA 16
Rel11
RU50 EP1
Rel11
RU50
Rel11
RU40
Rel9
RU30
Rel9
RU20
Rel8
Note that after the RNC has been upgraded to the new software release, the information on the neighboring RNC must be updated to ensure that Iur-based features work correctly. Adjust the NRncVersion parameter of the Iur object so that it matches with the 3GPP version of the RNC. The parameter can be changed online, without disturbing ongoing calls. Terminology Before the system upgrade is carried out, it is important to be familiar with the procedurerelated terminology.
DN0980322 Issue: 03B
© 2016 Nokia
11
System upgrade overview
WCDMA RAN, Rel. WCDMA 17, System Upgrade
Table 2
Common terms
Action
Definition
SW Update
It comprises software download, installation and activation of a software build to one or more network elements in WCDMA RAN. Software update to the new software version is of the same topology version as the active one. The configuration data is kept.
SW Upgrade
It is installation and activation of a software version which is of higher/newer topology version than the one currently active. Configuration database content is converted to a new topology format where needed.
SW Downgrade
It is installation and activation of a software version which is of lower/older topology version than the active one. Downgrade is not formally supported as it may cause the BTS to end up in a uncommissioned state.
SW Fallback
It is automatic/autonomous activation of an older software version that is stored on the network element and that was previously running. After fallback, the NE is providing service under control of the previous software version. Activation of a software version always goes together with activation of a configuration database fitting to the same topology version. This database is stored in the NE. No database conversion takes place in case of SW Fallback or SW Rollback.
SW Rollback
It is a manually-initiated operation on a node element that causes the node element to restart the SW that had been active before the SW upgrade was performed. Note that there is no uniform trigger operation for rollback of different node element types from NetAct software manager. Depending on the NE type it can be done by:
12
•
locally at the NE using CLI.
•
remotely, using NetAct Software Manager (SWM).
•
starting SW download with former SW version.
© 2016 Nokia
DN0980322 Issue: 03B
WCDMA RAN, Rel. WCDMA 17, System Upgrade
Instructions for upgrade
2 Instructions for upgrade All network elements must be at WCDMA 16 level before starting the system upgrade. Recommendations and requirements for the system upgrade are listed in Table 3: Requirements and recommendations For information on the upgrade documents for a given network element, see Table 4: Network elements paths and upgrade documentation . Additional information that is relevant from the upgrade procedure point of view is listed in Table 5: Reference documentation and technical notes . Table 3
Requirements and recommendations
Network element(s)
BTS, NetAct BTS
Requirements and recommendations
If the RAN1770/BSS21403:RF Sharing WCDMA - GSM feature is in use, both NetAct and BTSs software version must be compatible. If the RAN1770/BSS21403: RF Sharing WCDMA - GSM feature is in use, then the network elements upgrade must be performed in the following sequence:
1. Flexi Multiradio BTS WCDMA 2. Flexi Multiradio BTS GSM/EDGE Additionally, if the RAN2126/LTE435 RF Sharing WCDMA – LTE feature is in use, the network elements upgrade must be done in the following sequence:
1. Flexi Multiradio BTS WCDMA 2. Flexi Multiradio BTS LTE WCDMA-GSM RF sharing is supported in WCDMA 17 from GF16.0 onwards and from EX16 onwards. WCDMA-LTE RF sharing is supported in WCDMA 17 from FL16 onwards. BTS BTS
PC where BTS Site Manager SW is running should have at least 1 GB RAM memory. The recommendation is 2 GB. SW upgrade from WCDMA to LTE/SBTS is supported without a commission file. To ensure smooth troubleshooting if BTS software upgrade fails for any reason, the following preventative actions should be performed: Before BTS software upgrade:
BTS
1. Collect and save BTS snapshots from different configurations (for example, from one cluster).
2. Collect and save both active and passive SW version information from the network.
3. Save active system configuration files (SCFs) as backups.
DN0980322 Issue: 03B
© 2016 Nokia
13
Instructions for upgrade
WCDMA RAN, Rel. WCDMA 17, System Upgrade
Table 3
Requirements and recommendations (Cont.)
Network element(s)
Requirements and recommendations
After BTS software upgrade and activation:
1. Collect logs and BTS snapshots as soon as possible. A two-week BTS alarm history after software upgrade and activation should be collected in NetAct or the RNC.
To ensure smooth troubleshooting if RNC or mcRNC software upgrade fails for any reason, the following preventative actions should be performed: Before RNC or mcRNC software upgrade:
1. Collect RNC-level KPIs for the duration of one to two weeks before upgrade.
2. Collect message monitoring logs (30 minutes to 1 hour amount of data) using L3DC (Megamon) or Fishing macro. (See the instructions in Technical Support Note TS-RNC-SW-038 RNC Problem Report Instructions.)
3. Perform IPA-RNC symptom report or mcRNC symptom report.
g
Note: For IPA-RNC, see Technical Support Note TS-RNC-SW038 RNC Problem Report Instructions for more information on data collection. For mcRNC, see mcRNC17 SW Release Upgrade Installation Instructions and Technical Support Note TS-RNC-SW-038 R NC Problem Report Instructions for more information on symptom report and collection of logs.
4. Upload a valid RNW plan (*.xml file format) to NetAct and save a copy to an external storage for backup. RNC, mcRNC During RNC or mcRNC software upgrade: •
Collect and save terminal upgrade logs.
After RNC or mcRNC software upgrade:
1. Collect RNC-level KPIs after the upgrade to see deviations against the collected KPIs before upgrade.
2. Collect message monitoring logs (30 minutes to 1 hour amount of data) using L3DC (Megamon) or Fishing macro. (See the instructions in Technical Support Note TS-RNC-SW-038 RNC Problem Report Instructions.)
3. Perform IPA-RNC symptom report or mcRNC symptom report.
g
14
Note: For IPA-RNC, see Technical Support Note TS-RNC-SW038 RNC Problem Report Instructions for more information on data collection. For mcRNC, see mcRNC17 SW Release Upgrade Installation Instructions and Technical Support Note TS-RNC-SW-038 R NC Problem Report Instructions for more information on symptom report and collection of logs.
© 2016 Nokia
DN0980322 Issue: 03B
WCDMA RAN, Rel. WCDMA 17, System Upgrade
Table 3
Instructions for upgrade
Requirements and recommendations (Cont.)
Network element(s)
Requirements and recommendations
4. Upload the post-upgrade RNW plan (*.xml file format) to NetAct and save a copy to an external storage for backup.
Table 4
Network elements paths and upgrade documentation
Network element
Software level upgrade paths •
OMS
WCDMA OMS:
RNC
WCDMA OMS16 → WCDMA OMS17
IPA-RNC: •
RNC16 SW → RNC17 SW
mcRNC: •
BTS
Location
NetAct 16.2 → NetAct NetAct Upgrade Overview NetAct 16.81 or NetAct 16.81 or NetAct 16.5 16.5 + NetAct fast pass + NetAct fast pass documentation in PIC portal
NetAct
•
Reference
mcRNC16 1.0 → mcRNC17
Introduction to upgrading from WCDMA OMS16 to WCDMA OMS17
WCDMA RAN, Rel. WCDMA 17, Operating Documentation in PIC portal
RNC17 SW Release Upgrade Installation Instructions
In NOLS at the following path: Care → Software Supply Tool → Radio Network → Radio Controllers → WCDMA RNC → RNC17 (Package Type: Release)
mcRNC17 SW Release Upgrade Installation Instructions
In NOLS at the following path: Care → Software Supply Tool → Radio Network → Radio Controllers → Multicontroller RNC → mcRNC17 SW (Package Type: Release)
Release Upgrade In NOLS at the following Instructions document for path: Care → Software WBTS17 release Supply Tool → Radio Network → Base Stations WBTS16 → WBTS17 → Flexi Multiradio BTS WCDMA → WBTS17
Flexi Multiradio BTS WCDMA: •
1 The
NetAct SW version for WCDMA17 P8 SW is NetAct 16.8 + SP414 or newer version.
DN0980322 Issue: 03B
© 2016 Nokia
15
Instructions for upgrade
WCDMA RAN, Rel. WCDMA 17, System Upgrade
Table 5
Reference documentation and technical notes
Network element
16
Reference
Location
NetAct
N/A
N/A
OMS
N/A
N/A
RNC
TS-RNC-HW-0114 WCDMA17 Minimum Requirements for HW
Product Information Center → Radio Network → Radio Controllers → WCDMA RNC: Documentation (Content type: Technical Support Note)
BTS
N/A
N/A
© 2016 Nokia
DN0980322 Issue: 03B
WCDMA RAN, Rel. WCDMA 17, System Upgrade
Fallback/rollback to previous system release
3 Fallback/rollback to previous system release During the software upgrade process, network elements can fallback to the former software load in the case of critical exceptions. NetAct A prerequisite for the NetAct upgrade is to make a fallback copy of the running software package. The copy can be used for SW Rollback purposes to restore the system to the previous software level. OMS If the new software installation for the OMS does not work properly after the upgrade, the autonomous SW Fallback to the old software installation is performed based on the automatic checking. It is also possible to perform manual SW Rollback locally using CLI or remotely using either CLI or NetAct. After OMS rollback has been completed a topology upload should be executed to ensure the OMS software version is updated at Netact. RNC In general, the prerequisite for the RNC upgrade is to make a fallback copy of the running software package. The copy can be used for SW Rollback purposes to restore the system to the previous software level. The differences between the particular RNC type fallbacks have been described below. For IPA-RNC, manual SW rollback can be triggered using MML commands. For mcRNC, rollback from mcRNC17 to mcRNC16 needs to be performed manually with SCLI commands. The rollback to the SW build from a previous release is possible only if the SW build was previously installed and activated on mcRNC. Note that rollback/fallback to the previous eSW stored in the passive bank is possible only if normalization has not been triggered (normalization time is 24 hours by default). BTS The SW Fallback is performed by installing and activating the software build from the previous release.
g
Note: After any BTS SW Fallback the user needs to disconnect and connect SEM again in order to ensure that a proper version of the site manager is loaded. The BTS does not perform any data conversion from WBTS17 to WBTS16. Instead, the stored configuration data that fits to the older SW topology version is activated. As a result, any configuration changes made with the new SW version are lost and need to be re-entered if only they are applicable to the previous version.
DN0980322 Issue: 03B
© 2016 Nokia
17
Fallback/rollback to previous system release
g
WCDMA RAN, Rel. WCDMA 17, System Upgrade
Note: The BTS fault 61006 (BTS booted at $date due to $RCause) is raised during software upgrade from WCDMA16 to WCDMA17 or during rollback from WCDMA17 to WCDMA16 because of a change in the clock control system synchronization application (CCSSA) image. This requires an additional BTS restart and extends the software activation time. If the BTS, apart from the software upgrade, has also been upgraded with the new hardware items, the following should be considered: •
After the fallback, SCF file contains the site configuration parameters from the moment of BTS upgrade to WBTS17 level. Should there be any hardware changes done on the WBTS17 level that required the re-commissioning, the same recommissioning must also be performed after the fallback.
BTSOM connection that cannot be re-established after the upgrade does not trigger the SW Fallback for BTS.
g
18
Note: Software downgrade to a software version that is not in the passive file system is not supported.
© 2016 Nokia
DN0980322 Issue: 03B