S161_OnTop_032

S161_OnTop_032 - Page 1/11 © Nokia Solutions and Networks 2014 Version 1.0 Confidential

Installation Instructions Id: S161_OnTop_032 Product Family: Radio Controllers Product: BSC Release: S16.1

Approval date: 10-Sep-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.


Table of Contents 1.Overview .......................................................................................................................................... 3 2.OnTop process implementation ........................................................................................................ 3

2.1 OnTop files installation together with a CD ............................................................................ 3 2.2 Downloading OnTop software files from NOLS ...................................................................... 3

3.Automated installation with macro .................................................................................................... 4 4.Manual installation............................................................................................................................ 6

4.1 OnTop directory creation ....................................................................................................... 6 4.2 Checking OnTop file checksum ............................................................................................. 6 4.3 Safecopying original versions of OnTop files ......................................................................... 6 4.4 Copying OnTop files to running package ............................................................................... 6 4.5 Activating the new software ................................................................................................... 7

5.Cancelling OnTop files in BSC ......................................................................................................... 7 5.1 OnTop cancelling with macro................................................................................................. 7 5.2 OnTop cancelling manually ................................................................................................... 8

5.2.1 Copying original version of the file from OnTop fallback directory ..................................... 8 5.2.2 Swapping the default version of the file in running package .............................................. 8

5.3 Activating the new software after cancelling OnTop files ....................................................... 9 6.Description of Correction ................................................................................................................ 10

6.1 External HO success rate decreased after SW upgrade from S15 to S16.1 on AoIP BSC ....10 Contact:

Contact your local Nokia Solutions and Networks support

Summary of changes:

09-Sep-2014 0.1 Creation Date 10-Sep-2014 1.0 Approval date


1. OVERVIEW

This document is to describe the actions needed for installing (and cancelling) this OnTop Delivery SW to the Nokia Base Station Controller (BSC) using OnTop Installation macro. Note: After installing this OnTop delivery, the SW package is no longer according to version control file (MAFILE) and the Software Verification Command ZWQB will fail with these modules. Despite of this, adding new CD to this package is possible and you can ignore that SW package verifying is failing during CD installation. The following corrections are provided in this OnTop Delivery:

Title Modified Components

PRs Impact Delivery Target

External HO success rate decreased after SW upgrade from S15 to S16.1 on AoIP BSC

AIV_BFSX.PAC 28.75-0 NA05706456 Capacity & Performance S16.1 1.1.0

The following table describes pre-requisites on different network elements.

Network Element

Pre-requisite

BSC S16.1 1.0.1 and S16.1 OnTop 027 TCSM No special requirements BTS No special requirements SGSN No special requirements MSC No special requirements OSS No special requirements

2. ONTOP PROCESS IMPLEMENTATION

The BSC OnTop files can be implemented to BSC running package either manually or using custom-built macro.

2.1 OnTop files installation together with a CD

If the OnTop installation is done in together with a CD installation, only one BSC restart is required. In this case the manual OnTop installation should be performed according to the OnTop documentation immediately after the CD installation, prior to the restart. It is recommended to verify that the default version of the installed module is the correct version prior to the BSC restart.

2.2 Downloading OnTop software files from NOLS

Operators with a NOLS contract can download the OnTop files from NOLS. The OnTop delivery is in *.ZIP format. Copy the OnTop delivery to a computer and unzip OnTop ZIP file.


3. AUTOMATED INSTALLATION WITH MACRO

The BSC_OnTop_file_implementation Macro is a custom-built macro, using Holistic Integration Tester (HIT) SW tool. It is recommended to go through the HIT User’s Manual before starting the program. The BSC_OnTop_file_Implementation Macro executes all needed steps and checks during OnTop installation. There is no need for manual checking before installation. The following table describes the HIT macro name and the main tasks of the macro.

HIT macro file name Main tasks of the macro BSC_OnTop_file_implementation.tel Activates and cancels BSC OnTop files.

Supports files which defined in MAFILE file. (XML files are not supported)

Picture of options you need to choose when performing the installation with macro.

Steps to perform the installation with macro:

1. First, check the OnTop module status of currently active package.

2. Install OnTop modules: After a while there is window which asks to copy unzipped OnTop file(s).

Start an FTP session between a computer and a BSC, check that the transfer mode is set to binary. Transfer OnTop files to running package’s ONTOP directory.


3. System restart is needed to activate the correction(s) to the working SW package.

If Yes is selected, the BSC executes system restart with options STMU, ETPE, ETPA, ETPT, ETPC, ETME and ETMA depending on unit configuration of the BSC. ETP-units are restarted only if OnTop delivery includes GGN* -files or MET*- files for ETM-units.

4. After this, macro is ready and OnTop SW module installation has been completed.

If needed, the un-installation can be also performed automatically, macro checks and returns the old version of the module(s).


4. MANUAL INSTALLATION

By following this procedure OnTop modules can be installed manually.

4.1 OnTop directory creation

If the ONTOP directory does not exist in active package directory, create it with the following MML command:

ZIWL:,:WSB,::ONTOP,FF,02,OT:; Start an FTP session between a computer and a BSC, check that the transfer mode is set to binary. Transfer OnTop files to running package ONTOP directory.

4.2 Checking OnTop file checksum

Checksum of OnTop file is checked in the ONTOP directory: ZDDE:OMU:"ZLP:M,MAS";

ZDDE:OMU:"ZMXV:W0-/<current_SW_directory>/ONTOP/<filename>;";

ZDDE:OMU:"ZMXV:W1-/<current_SW_directory>/ONTOP/<filename>;";

4.3 Safecopying original versions of OnTop files

Original versions of the files to be replaced by OnTop modules in active SW package with current CD level are saved to fallback directory. Create directory to save original file version of OnTop files. FB directory for this purpose is created to active package directory:

ZIWL::WSB,:ONTOP:ONTOPFB,FF,02,OT:;

Copy original file versions to the fallback directory with the following MML command:

ZIWY:S:UNIT=OMU,PATH=/<current_SW_directory>/<source_dir>,DRIVE=WDU-S,;

ZIWY:D:UNIT=OMU,PATH=/<current_SW_directory>/ONTOP/ONTOPFB,DRIVE=WDU-SB,;

ZIBC:,,<file_name>,IMG,;

Note If there are several versions of some OnTop file, only the original version of OnTop file is saved to fallback directory.

4.4 Copying OnTop files to running package

Copy OnTop file to correct directory of the running package with the following MML command: ZIWY:S:UNIT=OMU,PATH=/<current_SW_directory>/ONTOP,DRIVE=WDU-S,;

ZIWY:D:UNIT=OMU,PATH=/<current_SW_directory>/<sub_dir>,DRIVE=WDU-SB,;



4.5 Activating the new software

Activate the software package with the following command: ZUSS:SYM:C=DSK:<Note>;

Note! By default, interface units are not restarted when their gateway computer is restarted. If BSC has STMU, include parameter “:STMU” at the end of ZUSS- command so that all interface computers of the STMU type are also restarted. In the same way all configured ETPE-, ETPT-, ETPA-, ETPC, ETME, ETMA units must be restarted when their gateway computer is restarted.

5. CANCELLING ONTOP FILES IN BSC

The cancelling can be made by using macro (chapter 6.1) or following manual un-installation procedure (chapter 6.2).

5.1 OnTop cancelling with macro

The un-installation can be also performed automatically; macro checks and returns the old version of module. Steps how to perform un-installation with the macro:

1. Select uninstall OnTop modules

2. Next select un-installation method


• 1st option assumes currently running SW build has both versions available, the original version belonging to official CD and the OnTop module which is currently active. This option swaps back the original CD version active.

• 2nd option assumes that under running package there exists an ONTOP directory and under that ONTOPFB directory where the official version to recover are stored.

3. Macro informs when the un-installation is ready.

5.2 OnTop cancelling manually

If OnTop file has to be cancelled, there are two possible ways to return to older version of the file: 1. Original version of the file will be copied from fallback directory ONTOPFB to running

package. (follow step 6.2.1) 2. Previous version of the file will be taken into use by swapping default version of the file in

running package. (follow step 6.2.2)

5.2.1 Copying original version of the file from OnTop fallback directory

Original version of the file will be copied from fallback directory to running package:

ZIWY:S:UNIT=OMU,PATH=/<current_SW_directory>/ONTOP/ONTOPFB,DRIVE=WDU-S,;

ZIWY:D:UNIT=OMU,PATH=/<current_SW_directory>/<sub_dir>,DRIVE=WDU-SB,;


5.2.2 Swapping the default version of the file in running package

Previous version of the file will be taken into use by swapping default version of the file in running package. In the below printout D defines the current default version.


Note! Default version must be changed on both disks (W0&W1). Example from W0:

00-MAN> ZMXP:W0-BLCODE/RRM*.*:*

VOLUME NSN .DIR

INITIALIZED BY XY 09-01-13 LAST WRITE 14-05-26

DIRECTORY OF /S161PP01/BLCODE/

INITIALIZED BY JJ 2014-01-16 09:43:51.09 LAST WRITE 14-04-11

NAME EXT VER CHECKSUM ID STRING ( D = DEFAULT VERSION )

RRM_BXSX .IMG :02 D: 475F70E2: 27.71-0 14/02/12 BXXENVSG.PAC 3.11-0

RRM_BXSX .IMG :01 : A1E16E00: 28.67-0 14/02/28 BXXENVSG.PAC 4.10-0

00-MAS> ZMNV:W0-BLCODE/RRM_BXSX.IMG,1

CHANGING DEFAULT VERSION: W0-BLCODE/RRM_BXSX.IMG:01

EXECUTED

5.3 Activating the new software after cancelling OnTop files

Activate the software package with the following command: ZUSS:SYM:C=DSK:<Note>;

Note! By default, interface units are not restarted when their gateway computer is restarted. If BSC has STMU, include parameter “:STMU” at the end of ZUSS- command so that all interface computers of the STMU type are also restarted. In the same way all configured ETPE-, ETPT-, ETPA-, ETPC, ETME, ETMA units must be restarted when their gateway computer is restarted.


6. DESCRIPTION OF CORRECTION

6.1 External HO success rate decreased after SW upgrade from S15 to S16.1 on AoIP BSC

Title Modified Components

PRs Impact Delivery Target

External HO success rate decreased after SW upgrade from S15 to S16.1 on AoIP BSC

AIV_BFSX.PAC 28.75-0 NA05706456 Capacity & Performance S16.1 1.1.0

1. Description of the fault? After S16.1 upgrade, increase in HO counter 4037 MSC O HO NOT ALLOWED is observed. 2. How to observe the fault from the real network? Configure mixed RNW (Packet Abis + Legacy Abis) and Legacy Abis sites should have both EDGE and non-EDGE TRXs. Only A-interface type supported should be AoIP TC in MGW. When AMR preferred HOs are performed between EDGE and non-EDGE TRXs, this issue can be observed. 3. What triggers the fault to be active? Since AMR with AoIP TC in MGW is not allowed on non-EDGE TRXs, AIVPRB fails the HO and counter 4037 is updated in the process. 4. How the fault has been corrected in this implementation? AIVPRB now selects a secondary non-AMR codec and proceeds with the HO only for those HO cases where AMR packing/unpacking is not performed. 5. How to recover from the fault without this correction? Remove non-EDGE TRXs from the network.


Disclaimer The information in this document applies solely to the hardware/software product (“Product”) specified herein, and only as specified herein.

This document is intended for use by Nokia Solutions and Networks' customers (“You”) only, and it may not be used except for the purposes defined in the agreement between You and Nokia Solutions and Networks (“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 Solutions and Networks. 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 Solutions and Networks 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 Solutions and Networks welcome 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 Solutions and Networks reserves the right to change any such information and statements without notice. Nokia Solutions and Networks has made all reasonable efforts to ensure that the content of this document is adequate and free of material errors and omissions, and Nokia Solutions and Networks will correct errors that You identify in this document. But, Nokia Solutions and Networks' total liability for any errors in the document is strictly limited to the correction of such error(s). Nokia Solutions and Networks does not warrant that the use of the software in the Product will be uninterrupted or error-free.

NO WARRANTY OF ANY KIND, EITHER EXPRESS OR IMPLIED, INCLUDING BUT 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 SOLUTIONS AND NETWORKS 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 Solutions and Networks’ proprietary and confidential information, which may not be distributed or disclosed to any third parties without the prior written consent of Nokia Solutions and Networks.

Nokia is a registered trademark of Nokia Corporation. Other product names mentioned in this document may be trademarks of their respective owners, and they are mentioned for identification purposes only.

Copyright © 2014 Nokia Solutions and Networks. All rights reserved.

Documents

S161_OnTop_032