Nokia LTE Integrating and Configuring

Nokia Networks

LTE Radio Access, Rel. FDD-LTE 15A, Operating Documentation, Issue 02 Integrating LTE/EPC System DN0966493 Issue 07 Approval Date 2015-06-23

Integrating LTE/EPC System

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 © 2015 Nokia Solutions and Networks. All rights reserved.

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 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 any additional information.

2

DN0966493

Issue: 07


Table of Contents This document has 13 pages Summary of changes..................................................................... 5

Issue: 07

1

Integrating LTE/EPC System Overview..........................................6

2 2.1

Integrating EPS elements.............................................................. 7 Evolved Packet System Interfaces.................................................7

3

Integrating eNB to EPS.................................................................. 9

4

Integrating Flexi Network Server-MME to EPS............................ 11

5

Integrating Flexi NG to EPS......................................................... 12

6

Verify the integration.................................................................... 13

DN0966493

3


List of Figures

4

Figure 1

Evolved Packet System interfaces....................................................... 8

Figure 2

Commissioning and integration of eNB.............................................. 10

DN0966493

Issue: 07


Summary of changes

Summary of changes Changes between document issues are cumulative. Therefore, the latest document issue contains all changes made to previous issues. Changes between issues 06 (2014-11-30, RL70) and 07 (2015-06-23, FDD-LTE15A)

•

Integrating eNB to EPS -

Added details about Flexi Zone Controller.

Changes between issues 05 (2013-09-25, RL50) and 06 (2014-11-30, RL70)

• • • •

Added Flexi Zone Micro BTS in EPS integration overview. Added Flexi Zone Micro BTS in Figure 1: Evolved Packet System interfaces. Updated Figure 2: Evolved Packet System integration flow. • Updated Figure 4: Flexi Network Server - MME interfaces. Updated Figure 5: Flexi NG interfaces.

Changes between issues 04 (2012-10-26, RL40) and 05 (2013-09-25, RL50)

•

Section 3 Related documents updated

Changes between issues 04 DRAFT(2012-07-13, RL40 and 04 (2012-10-26, RL40)

•

Editorial changes in section 1.2 Flexi network server - MME

The document has been rewritten to improve usability.

Issue: 07

DN0966493

5

Integrating LTE/EPC System Overview


1 Integrating LTE/EPC System Overview Evolved packet system (EPS) is high speed, low latency radio access technology, and service architecture for packet switched data via pure IP service domain. The core network is referred as evolved packet core (EPC) and the radio network as evolved UTRAN (E-UTRAN). Integrating EPS is a procedure to connect E-UTRAN and EPC elements to each other. This is achieved by cabling and configuring the interfaces of the following network elements:

•

evolved node B (eNB) These are variants of eNB: -

Flexi Multiradio BTS LTE

-

Flexi Zone Micro BTS

-

Flexi Zone Pico BTS Flexi Zone Controller

-

• •

mobility management entity (MME) - Flexi Network Server (Flexi NS) serving gateway (S-GW) and packet data network gateway (P-GW) - Flexi Network Gateway (Flexi NG)

Operation and management server (OMS) and NetAct are also configured during the integration. For more information about network elements, see Network elements in LTE system. For more information about Nokia LTE/EPC product portfolio, see LTE/EPC product portfolio.

6

DN0966493

Issue: 07


Integrating EPS elements

2 Integrating EPS elements Before you start Complete the following tasks before integrating the EPS elements: 1. Plan the network.

•

Follow the Planning process as described in the LTE Radio Network Planning Guideline.

2. Install and configure the hardware and software. 3. Commission the network elements. During the commissioning phase, the network elements are configured and tested as stand-alone entities.

g

1

Integrate the eNB to EPS.

2

Integrate the Flexi NS to EPS.

3

Integrate the Flexi NG to EPS.

4

Verify the integration.

2.1 Evolved Packet System Interfaces Figure 1: Evolved Packet System interfaces illustrates the network elements and interfaces that are configured during EPS integration.

Issue: 07

DN0966493

7

Integrating EPS elements

Figure 1


Evolved Packet System interfaces

Gn

SGs

SGSN

E-UTRAN

MSC/VLR

EPC

S4

S1-MME

S6a MME

HSS

S11 X2 S1-U

S5/S8

SGi

PDN eNB

S-GW

P-GW

NE3S/SNMP BTSOM

NWI3

OMS

C-PLANE U-PLANE M-PLANE

NetAct

8

DN0966493

Issue: 07


Integrating eNB to EPS

3 Integrating eNB to EPS Before you start Complete the following tasks before integrating eNB to EPS: 1. Install and commission the eNB (see installing and commissioning eNB). 2. Install and commission the LTE OMS (see installing and commissioning of LTE OMS). 3. Integrate eNB to NetAct.

g

For detailed procedure, see Integrating Flexi Multiradio BTS LTE to NetAct.

g

Integrating Flexi Controller to NetAct has two parts, these are: a) Integrate the Flexi Controller Platform to NetAct. For detailed proceduce, see Integrating Flexi Controller to NetAct. b) Integrate the Flexi Controller LTE to NetAct. To integrate the Flexi Zone Controller LTE to NetAct, refer to Integrating Flexi Multiradio BTS LTE to NetAct.

Figure 2: Commissioning and integration of eNB illustrates the process of commissioning and integrating eNB.

Issue: 07

DN0966493

9

Integrating eNB to EPS


Figure 2

10

Commissioning and integration of eNB

DN0966493

Issue: 07


Integrating Flexi Network Server-MME to EPS

4 Integrating Flexi Network Server-MME to EPS Before you start Complete the following tasks before integrating the Flexi NS-MME element:

g

Issue: 07

• • •

Plan the network.

1

Set up the cables.

2

Configure the external interfaces.

3

Configure the system parameters.

4

Activate the configuration.

5

Test the connections.

Install and configure hardware and software. Commission the network element. Commissioning comprises the software installation tasks and tests that are performed after the hardware of the network element has been installed on the site, but before the network element is connected to the operator's network.

For detailed procedure, see Flexi Network Server Operating Documentation, under section Integrate and Configure on NOLS.

DN0966493

11

Integrating Flexi NG to EPS


5 Integrating Flexi NG to EPS Before you start Complete the following tasks before integrating the Flexi NG element:

• • •

Plan the application interfaces. Plan the needed Flexi NG nodes to provide the services. Plan the applicable site solution.

1

Set up the cables.

2

Configure the external network.

3

Configure the IP addresses.

4

Configure the routing.

5

Configure the Flexi NG services.

6

Configure access control lists.

For detailed procedure, see Flexi Network Gateway Operating Documentation, under section Commission, subsection Commissioning and Integrating Flexi NG on NOLS.

12

DN0966493

Issue: 07


Verify the integration

6 Verify the integration This procedure is intended to verify the integration of EPS elements.

1

Verify the eNB integration to NetAct.

2

Verify the Flexi NS integration to NetAct.

3

Verify the Flexi NG integration to NetAct.

4

Verify the RAN interfaces.

• • •

5

Make a test call using the UE. Send an SMS message to 2G/3G UE to ensure MME delivers it to MSC/VLR. Send an SMS message from 2G/3G UE to ensure MME receives it from MSC/VLR.

Ensure the network elements are fully integrated. Use the integration checklists and integration verification instructions delivered with the network elements.

Issue: 07

DN0966493

13

NetAct™ 15 Integrating Flexi Multiradio BTS LTE to NetAct DN09118114 Issue: 1-2

The information in this document is subject to change without notice and describes only the product defined in the introduction of this documentation. This documentation is intended for the use of Nokia Solutions and Networks customers only for the purposes of the agreement under which the document is submitted, and no part of it may be used, reproduced, modified or transmitted in any form or means without the prior written permission of Nokia Solutions and Networks. The documentation has been prepared to be used by professional and properly trained personnel, and the customer assumes full responsibility when using it. Nokia Solutions and Networks welcomes customer comments as part of the process of continuous development and improvement of the documentation. The information or statements given in this documentation concerning the suitability, capacity, or performance of the mentioned hardware or software products are given "as is" and all liability arising in connection with such hardware or software products shall be defined conclusively and finally in a separate agreement between Nokia Solutions and Networks and the customer. However, Nokia Solutions and Networks has made all reasonable efforts to ensure that the instructions contained in the document are adequate and free of material errors and omissions. Nokia Solutions and Networks will, if deemed necessary by Nokia Solutions and Networks, explain issues which may not be covered by the document. Nokia Solutions and Networks will correct errors in this documentation as soon as possible. I N N O E V EN T WI LL N OKI A S O L UT I ON S A N D N E T W O R K S B E L I A B L E F O R E R R O R S I N T H IS DO CU M EN TAT IO N OR F O R A N Y D A M A G E S , I N C L U D I N G B U T N O T L IM I T ED TO SPEC IAL, D IR E C T, IN D I R E C T, I N C I D E N TA L O R C O N S E Q U E N T I A L O R AN Y LOSSES, SU CH A S B U T N O T L I M I T E D TO L O S S O F P R O F I T, R E V E N U E, B USI NESS IN T ER RU P T I ON , B U S I N E S S O P P O RT U N I T Y O R D ATA , T H AT M AY A RI SE F RO M T H E USE OF T HI S D O C U M E N T O R T H E I N F O R M AT I O N I N I T. NSN is a trademark 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 © Nokia Solutions and Networks 2014/11/27. All rights reserved.

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.

Integrating Flexi Multiradio BTS LTE to NetAct

Contents 1 Overview of Flexi Multiradio BTS LTE integration.......................................................................................6 1.1 Brief introduction to Flexi Multiradio BTS LTE..........................................................................................6 1.2 Brief introduction to LTE iOMS................................................................................................................. 6 1.3 Management interfaces and protocols......................................................................................................6 1.4 Compatibility information........................................................................................................................... 7 1.5 Network connection after integration........................................................................................................ 9 1.6 First time integration............................................................................................................................... 10

2 Preparation before integration..................................................................................................................... 12 2.1 Prerequisites for NetAct.......................................................................................................................... 12 2.1.1 Managing integration users............................................................................................................ 15 2.1.2 Checking virtual machine address and service status................................................................... 16 2.1.2.1 Checking the virtual machine for services............................................................................. 16 2.1.2.2 Checking NetAct Virtual Machine IP address........................................................................ 17 2.1.2.3 Checking LB WAS Virtual IP and LB JBI Virtual IP............................................................... 18 2.1.3 Checking the service status in NetAct........................................................................................... 18 2.1.3.1 Checking the status of Database service.............................................................................. 18 2.1.3.2 Checking the status of NWI3 mediation................................................................................ 19 2.1.3.3 Checking the status of WAS service..................................................................................... 19 2.1.3.4 Checking the status of FM Pipe service................................................................................ 20 2.1.3.5 Checking the status of PM Pipe service................................................................................20 2.1.3.6 Checking the status of LDAP service.................................................................................... 20 2.1.4 Checking NetAct licenses required for LTE software..................................................................... 21 2.1.4.1 LTE Standard software license.............................................................................................. 21 2.1.4.2 Checking installed licenses in NetAct.................................................................................... 21 2.1.5 Checking the adaptation packages................................................................................................ 22 2.1.5.1 Checking the adaptation packages in Adaptation Manager...................................................22 2.1.5.2 Checking the PM adaptation packages in Virtual Machines.................................................. 23 2.1.6 Checking connection from NetAct to Flexi Multiradio BTS LTE..................................................... 24 2.1.7 Checking NetAct time synchronization........................................................................................... 25 2.1.8 Prerequisites for Element Management......................................................................................... 26 2.1.8.1 Installing Application Launcher in Node Manager Server...................................................... 27 2.1.8.1.1 Downloading LTE iOMS Application Launcher installer.................................................27 2.1.8.1.2 Installing and configuring Application Launcher............................................................ 28 2.1.8.2 Installing BTS Site Manager in Node Manager Server.......................................................... 28 2.2 Prerequisites for LTE iOMS.................................................................................................................... 29 2.2.1 Checking IP connectivity between LTE iOMS and NetAct............................................................. 34 2.2.2 Configuring a heartbeat interval for Flexi Multiradio BTS LTE....................................................... 35 2.2.3 Configuring LTE iOMS TLS modes................................................................................................ 35 2.2.3.1 TLS operation mode in Flexi Multiradio BTS LTE..................................................................36 2.2.3.2 BTS and O&M Protocol (OM) security mode in LTE iOMS................................................... 36 2.2.3.3 File Transfer (FT) security mode in LTE iOMS...................................................................... 36 2.2.3.4 Allowed TLS mode combinations...........................................................................................37

3


2.2.3.5 Configuring File Transfer modes in LTE iOMS...................................................................... 37 2.2.3.6 Mandatory certificates for TLS configuration in LTE iOMS.................................................... 38 2.2.3.7 Installing certificates for secure communication.................................................................... 38 2.2.4 Configuring DNS service on LTE iOMS......................................................................................... 39 2.2.5 Configuring time synchronization in LTE iOMS..............................................................................40 2.3 Prerequisites for Flexi Multiradio BTS LTE.............................................................................................41 2.3.1 Commissioning Flexi Multiradio BTS LTE...................................................................................... 44 2.3.2 Checking the instance identifier of Flexi Multiradio BTS LTE........................................................ 44 2.3.3 Checking IP connectivity between Flexi Multiradio BTS LTE and LTE iOMS.................................44 2.3.4 Configuring Flexi Multiradio BTS LTE time synchronization with NetAct........................................45 2.3.5 Activating measurements configuration through BTS Site Manager.............................................. 46 2.4 Prerequisites for intermediate system.................................................................................................... 47 2.4.1 Setting up firewall rules.................................................................................................................. 47 2.4.2 Routing configuration...................................................................................................................... 52 2.4.3 Network Time Protocol configuration..............................................................................................53 2.5 Adding Flexi Multiradio BTS LTE and LTE iOMS to DNS in NetAct.......................................................53 2.5.1 Checking the name server status.................................................................................................. 53 2.5.2 Configuring the DNS in NetAct...................................................................................................... 54 2.5.3 Verifying the availability of a zone..................................................................................................55 2.6 Other configurations................................................................................................................................ 55 2.6.1 Configuring SOCKS proxy service................................................................................................. 56 2.6.1.1 Checking the status of SOCKS proxy service....................................................................... 56 2.6.2 Adding the trusted sites..................................................................................................................56 3 Integrating Flexi Multiradio BTS LTE to NetAct manually........................................................................ 57 3.1 Checking and creating the root object in NetAct....................................................................................57 3.2 Checking and creating maintenance region........................................................................................... 58 3.3 Creating service users required for LTE iOMS Integration.....................................................................58 3.4 Creating managed objects for LTE iOMS in NetAct............................................................................... 61 3.4.1 Creating LTE iOMS managed object..............................................................................................62 3.4.2 Creating the HTTP interface object................................................................................................63 3.5 Associating maintenance region with LTE iOMS....................................................................................65 3.6 Executing integration data upload.......................................................................................................... 66 3.7 Associating maintenance region with MRBTS and LNBTS.................................................................... 66 3.7.1 Manual association using NetAct Monitor...................................................................................... 66 3.7.2 Automatic association using Integration Data Upload....................................................................68 3.7.3 Automatic association using the MR association Tool................................................................... 68 3.8 Provisioning Flexi Multiradio BTS LTE credentials in Network Element Access Control........................ 69 3.9 Collecting SSH public keys.....................................................................................................................70 3.9.1 Collecting the SSH public keys of LTE iOMS in NetAct.................................................................71 3.9.2 Collecting the SSH public keys of the Flexi Multiradio BTS LTE in NetAct.................................... 71 3.10 Executing CM upload............................................................................................................................72 3.11 Executing Alarm Upload........................................................................................................................74 4 Integrating Flexi Multiradio BTS LTE to NetAct with NE Integration Wizard...........................................76 4.1 Integration operations in NEIW...............................................................................................................76

4


5 Verifying the integration............................................................................................................................... 78 5.1 Verifying Integration Data Upload........................................................................................................... 78 5.2 Verifying alarm upload............................................................................................................................ 78 5.3 Verifying CM upload................................................................................................................................79 5.3.1 Verifying in NetAct Monitor............................................................................................................. 79 5.3.2 Verifying in CM Editor.....................................................................................................................81 5.4 Verifying element management connectivity...........................................................................................82 5.4.1 Verifying LTE iOMS EM Launch through NetAct Monitor...............................................................82 5.4.2 Verifying LTE BTS Site Manager EM launch through NetAct Monitor............................................83 5.5 Verifying fault management connectivity................................................................................................ 84 5.6 Verifying performance management connectivity................................................................................... 85 5.6.1 Verifying performance management data flow by checking database........................................... 85 5.6.2 Checking measurements data on Performance Manager..............................................................86 5.7 Verifying configuration management operation.......................................................................................87 5.8 Verifying state management operation................................................................................................... 88 5.8.1 Changing the administrative state of a network element to Lock...................................................88 5.8.2 Changing the administrative state of a network element to Unlock............................................... 89 5.8.3 Changing the administrative state of a network element to Shutdown.......................................... 90 5.8.4 Resetting the LNCEL or LNBTS.................................................................................................... 90 6 Other management functions for Flexi Multiradio BTS LTE..................................................................... 92 6.1 Administering Centralized Network Element User Management............................................................ 92 7 Disabling integration................................................................................................................................... 100 7.1 Disabling Flexi Multiradio BTS LTE integration.................................................................................... 100 7.2 Disabling LTE iOMS integration............................................................................................................102 8 Troubleshooting integration problems......................................................................................................106 8.1 Integration data upload fails..................................................................................................................106 8.2 Alarm upload fails................................................................................................................................. 110 8.3 Element management launch fails........................................................................................................110 8.4 No fault management data received.....................................................................................................111 8.5 State management operation................................................................................................................112 8.5.1 State management operation fails................................................................................................112 8.5.2 Error message "Existing operation is still running, please try again later." appears..................... 113 8.6 No performance management data received in database....................................................................114

5


Overview of Flexi Multiradio BTS LTE integration

1 Overview of Flexi Multiradio BTS LTE integration Before performing integration, you must have basic knowledge of the following:

• network protocols used • NetAct • Flexi Multiradio BTS LTE • network topology • interfaces involved • user management plan • network management plan You must have copies of the following documents on hand as reference for the integration procedure:

• Flexi Multiradio BTS LTE Operating Documentation • LTE iOMS Operating Document of the NE to be integrated to NetAct

1.1 Brief introduction to Flexi Multiradio BTS LTE Flexi Multiradio BTS with LTE software is a 3GPP LTE eNodeB BTS site solution. Flexi Multiradio BTS LTE introduces a new way to build BTS sites using modules without a specific BTS cabinet. Flexi Multiradio BTS LTE modules can be used with different BTS configurations for an integrated site solution. The existing site support and auxiliary cabinets can be used to house Flexi Multiradio BTS modules, or modules can be installed, for example, on a wall. Flexi Multiradio BTS LTE provides high radio downlink output power when using Flexi 3-sector RF Module with the total of 210 W power amplifiers, or Remote Radio Heads. The LTE or WCDMA/HSPA RF frequency division duplex frequency band is selected by using the desired RF Module hardware variant. A Flexi Multiradio BTS consists of one RF Module per frequency band and one System Module with a transmission submodule. The same Multiradio modules are used in both WCDMA/HSPA and LTE indoor and outdoor sites.

1.2 Brief introduction to LTE iOMS LTE iOMS is a necessary network element in the operability architecture of NSN LTE Solution. It concentrates operation and management traffic, and performs operation and management activities towards the Flexi Multiradio BTS LTE. In addition, it provides mediator and aggregation functionalities between eNodeB elements and NetAct. LTE iOMS participates as a centralizing node to all key management tasks, such as fault, performance, configuration, topology, and software management.

Issue: 1-2

DN09118114

6



1.3 Management interfaces and protocols The network management interface between NetAct and LTE iOMS is NWI3. The interface between LTE iOMS and Flexi Multiradio BTS LTE is BTSOM. LTE iOMS connects to Flexi Multiradio BTS LTE through the NSN BTSOM management interface. All fault management, performance management, configuration, and software management transactions between Flexi Multiradio BTS LTE and LTE iOMS are transferred over the BTSOM interface. The NWI3 interface is a specific management interface for carrying management information between LTE iOMS and the NetAct network management system and external Element Manager. The NWI3 interface acts as a mediator for applications sending data between the NE and external O&M tools (such as GUIs) located in the NetAct and external EM. The NWI3 and BTSOM management interfaces used in NSN LTE and WCDMA systems provide functional capabilities, reliability and efficiency. Note: NWI3 and BTSOM are NSN proprietary interfaces.

1.4 Compatibility information The following tables show information on the compatibility between NetAct and network element releases. Supported network element

Adaptation package identifier in

version

NetAct

RL40

LN4.0

NOKLTE-LN4.0

RL50

LN5.0

NOKLTE-LN5.0

RL50 FZM

LNFZ5.0

NOKLTE-LNFZ5.0

RL35TD

LNT3.0

NOKLTE-LNT3.0

RL35IR

LNT3.1

NOKLTE-LNT3.1

RL60

LN6.0

NOKLTE-LN6.0

RL45

LNT4.0

NOKLTE-LNT4.0

RL70

LN7.0

NOKLTE-LN7.0

RL70 FZM

LNF7.0

NOKLTE-LNF7.0

RL55

LNT5.0

NOKLTE-LNT5.0

RL55 FZM

LNZ5.0

NOKLTE-LNZ5.0

FL15A

FL15A

NOKLTE-FL15A

Radio network release

Issue: 1-2

DN09118114

7


Radio network release TL15A


Supported network element


version

NetAct

TL15A

NOKLTE-TL15A

Table 1: NetAct and Flexi Multiradio LTE BTS compatibility information

Supported network element


version

NetAct

RL40

LTO4.0

NOKGOMS-LTO4.0

RL50

LTO5.0

NOKGOMS-LTO5.0

RL50 FZM

LTO5.0

NOKGOMS-LTO5.0

LTO6.0

NOKGOMS-LTO6.0

RL35TD

LTO5.0

NOKGOMS-LTO5.0

RL35IR

LTO5.0

NOKGOMS-LTO5.0

RL60

LTO6.0

NOKGOMS-LTO6.0

RL45

LTO6.0

NOKGOMS-LTO6.0

RL70

LTO7.0

NOKGOMS-LTO7.0

RL70 FZM

LTO7.0

NOKGOMS-LTO7.0

RL55

LTO7.0

NOKGOMS-LTO7.0

RL55 FZM

LTO7.0

NOKGOMS-LTO7.0

FL15A

LTO15A

NOKGOMS-LTO15A

TL15A

LTO15A

NOKGOMS-LTO15A

Radio network release

Table 2: NetAct and LTE iOMS compatibility information Compatibility information of Flexi Multiradio BTS LTE releases and NetAct The supported network element versions and corresponding supported management functions are listed in the table below. After the integration, NetAct can perform supported management functions for the network element from a central location, and the Flexi Multiradio BTS LTE management applications can be launched from the NetAct user interface. Supported network element version Management functions

NE Integration Wizard (NEIW)*

Issue: 1-2

LN4.0, LN5.0, LN6.0, LN7.0,

LNT3.0, LNT3.1, LNT4.0,

LNFZ5.0, LNF7.0, FL15A

LNT5.0, LNZ5.0, TL15A

Supported (NWI3)

Supported (NWI3)

DN09118114

8



Supported network element version Management functions

LN4.0, LN5.0, LN6.0, LN7.0,

LNT3.0, LNT3.1, LNT4.0,

LNFZ5.0, LNF7.0, FL15A

LNT5.0, LNZ5.0, TL15A

Supported (HTTP/HTTPS)

Supported (HTTP/HTTPS)

Fault management

Supported (NWI3)

Supported (NWI3)

Performance management

Supported (NWI3)

Supported (NWI3)

Configuration management

Supported (NWI3)

Supported (NWI3)

License management

Not Supported

Not Supported

Software management

Supported (NWI3)

Supported (NWI3)

Not Supported

Not Supported

Supported (NWI3)

Supported (NWI3)

Audit Trail

Supported (NWI3)

Supported (NWI3)

TraceViewer

Supported (NWI3)

Supported (NWI3)

Network Element Backup and

Supported (NWI3)

Supported (NWI3)

Not Supported

Not Supported

Supported (NWI3)

Supported (NWI3)

Element management launch

(including Hardware Management)

Administration of Measurement Network Element Access Control

Restore Dynamic Adaptation Centralized Network User Management

Table 3: Supported network element versions, management functions and used southbound interfaces Note: * Automated integration is done through LTE iOMS.

1.5 Network connection after integration The following figure shows how Flexi Multiradio BTS LTE is connected to NetAct through DCN backbone after integration.

Issue: 1-2

DN09118114

9



Figure 1: Managing Flexi Multiradio BTS LTE

1.6 First time integration The following flowchart shows the basic order of steps needed for integrating Flexi Multiradio BTS LTE to NetAct. The steps can be divided into preparation, integration, and verification phases. Note: Follow the order of the steps presented in this document to prevent any unwanted delays in integration.

Issue: 1-2

DN09118114

10



Figure 2: The steps needed for integrating Flexi Multiradio BTS LTE to NetAct

Issue: 1-2

DN09118114

11


Preparation before integration

2 Preparation before integration Prerequisites for the Flexi Multiradio BTS LTE, LTE iOMS, and NetAct must be met before you can proceed with the integration procedure. The following sections list the required information and configuration details, and provide information on how to meet the requirements.

2.1 Prerequisites for NetAct Before starting integration, ensure that NetAct meets the following requirements. Follow the instructions given in this chapter to ensure all the requirements listed below are met. NetAct requirements

Additional information

NetAct

Running

NetAct serves both as a network management system and as

environment

NetAct system

an element management system. NetAct offers a wide range of

environment

unified operation and maintenance capabilities for network

(hardware

elements in core, radio and transport networks. It consists of

configuration)

many tools for handling a number of network elements and expanding networks. It is designed for handling an increase in both complexity of the network and the amount of traffic and data. For more details, refer to NetAct deployment and configurations.

Hardening of

RC4 Ciphers are disabled by default. You need to enable

WebSphere

RC4 Ciphers to perform the integration procedure. For more

application

information, refer to Handling RC4 Ciphers.

server (WAS) Licenses

NetAct Radio

Check if the required licenses, which authorize the support in

LTE FD TD FZ

NetAct for the network element to be integrated, are installed in

standard SW

NetAct using License Manager. This license integrates the fault management, performance management, and configuration management data of LTE radio network elements (eNodeB, iOMS) into the NetAct database. It is required for the functions of NetAct Monitor, NetAct Reporter, and NetAct Configurator applications for the LTE network elements. NetAct Reporter includes Report Editor, Report Viewer and Administration of Measurements. NetAct Configurator includes CM Editor and CM Operations For detailed instructions, refer to Checking NetAct licenses required for LTE software.

Software

The NetAct system is delivered with all the functionality/

licenses for

features, called NetAct Sales Features, which are implemented

NetAct

in a particular release of NetAct. On the other hand, not all functionality/features are available for use. These functionality/

Issue: 1-2

DN09118114

12


NetAct requirements


Additional information features need to be unlocked using license key files which need to be ordered from NSN. A license-based application, service, solution, feature, or functionality can only be used with a valid software license. For details, refer to Software licenses for NetAct.

Adaptation

LTE adaptation

Adaptations are metadata that are used to configure the software

packages

to handle new network elements. To check the supported Adaptation Packages for LTE iOMS and Flexi Multiradio BTS LTE, refer to Required adaptation packages table. For instructions on checking adaptation packages, refer to Checking the adaptation packages in Adaptation Manager and Checking the PM adaptation packages in Virtual Machines.

Required

CM certificates

information, refer to Adding certificates for CM upload.

Certification Authority (CA) Certificates

Services and

Check if the required certificates are available. For more

NWI3

For more information, refer to Adding a network element certificate

Certificates

to the NWI3 mediation's truststore.

NWI3-HTTP

For more information, refer to Configuring the Tomcat NWI3-HTTP

Certificate

server.

LDAP

For more information on installing certificates in NetAct LDAP

Certificate

server, refer to Managing certificates

NWI3 Service

For more information, refer to Checking the status of NWI3

Interfaces

mediation. WAS Service

For more information, refer to Checking the status of WAS service.

FM Pipe

For more information, refer to Checking the status of FM Pipe

Service

service.

PM Pipe

For more information, refer to Checking the status of PM Pipe

Service

service.

LDAP Service

For more information, refer to Checking the status of LDAP service.

Interfaces and ports Default object

Root object

For more information, refer to Setting up firewall rules. Check whether the default root object is created. If not, create the root object. For more information, refer to Checking and creating the root object in NetAct.

Issue: 1-2

Maintenance

This is the Maintenance Region into which the Flexi Multiradio BTS

Region

LTE and LTE iOMS will be associated and managed.

DN09118114

13


NetAct requirements


Additional information Refer to the network management plan. For more information, refer to Checking and creating maintenance region.

Table 4: Preparation checklist in NetAct Ensure that all required information is available before starting the integration process. Follow the instructions listed below to find all the required information. NetAct information


User accounts

NetAct user

It is recommended that the NetAct User Administrator create the

account which

dedicated integration user for the integration engineer to perform

is used for

the operation in Netact start page.

integration operations in NetAct Start

The omc user can be used for integration. For detailed instructions, refer to Managing integration users.

Page Default

The user group in which the created integration user belongs must

roles and

have the default roles.

permissions required for the

For more information, refer to Permission management overview.

integration of Flexi Multiradio BTS LTE and LTE iOMS NetAct user

This account will be used when you will log in to any NetAct VM

account which

to conduct verification operations and others. Use omc user for

is used for

operations in NetAct VMs. When a certain operation needs higher

operations in

user privileges, you may opt to use root user access and switch

NetAct Virtual

back to omc user after the operation.

Machines (VMs) NetAct user

Different user accounts might be needed for accessing the

account

different NetAct applications. For the user accounts and

for function

permissions, contact your network element administrator.

management operations

The user name should contain 4-8 characters and must be in accordance with the login name policy in user management. For information on NetAct User Management, refer to User management overview.

NetAct basic

NetAct is

Refer to Running Preventive Health Check in Troubleshooting

information

installed

section.

successfully. NetAct VM types

Issue: 1-2

In NetAct, there are normally three main types of VMs:

• NetAct VMs • Node Manager VMs DN09118114

14


NetAct information



• PM platform VMs For more information, refer to Node structure overview. FQDN and

IP address

The IP address and FQDN of NetAct integration point is the NetAct

Address

and FQDN

reference point for a network element connection.

of the NetAct

Refer to the network configuration plan. For detailed instructions,

integration point refer to Checking virtual machine address and service status. IP address of

This is the IP address of the NetAct VM on which the socks

proxy service

service is running. For detailed instructions, refer to Checking the status of SOCKS proxy service.

NTP Server

IP address

Check and confirm which server is used as the time source(s) for

of the time

the network element.

source(s)

The time source(s) could be any of the following:

• an external time source • NetAct WAS VM • NetAct DB VM For more information, refer to Checking NetAct time synchronization. Domain

NetAct domain

This is the domain into which the NetAct servers are included, for example, netact.example.com.

Table 5: Information checklist in NetAct

2.1.1 Managing integration users User for integration operations in NetAct Start Page For integration operations in NetAct, it is recommended that the administrator create a dedicated integration user for the integration engineer and assign required default roles to the user group which the integration user belongs to. The following default roles are required for the integration:

• CM-Configuration Management Administration • CM-Network Planning and Engineering • CM-Provisioning • FM-Fault Management Admin • PM-Performance Analysis • PM-Performance Management Control • PM-Performance Monitoring • PM-Performance Quality Assurance • SM-Security Administration Issue: 1-2

DN09118114

15



This Node manager group is required for the integration:

• ApplicationLaunchOnly For detailed instructions on how to create users and user groups, see User Management Help. For detailed instructions on how to add users to a user group, assign roles to a user group, and add scope to group-role combinations, see Permission Management Help. User for integration operations in NetAct VMs Use omc user for integration operations in NetAct VMs. When root access is needed, switch to root user and switch back to omc after the operation. Customizing the user plan The roles with permissions can be customized in NetAct. For detailed instructions on how to add users to a user group, assign roles to a user group, and add scope to group-role combinations, see Permission Management Help. If you have your own user plan, you can manage users following the instructions given in User Management Help.

2.1.2 Checking virtual machine address and service status 2.1.2.1 Checking the virtual machine for services In several integration procedures, you are required to log in to a NetAct virtual machine (VM) where a specific service is running. Perform the succeeding procedure to determine the right NetAct VM on which the service is running. 1. Log in to any NetAct VM as the omc user. 2. Find the VM where a specific service is running by entering: [omc]$ /opt/cpf/sbin/netact_status.sh status service For example: [omc]$ /opt/cpf/sbin/netact_status.sh status service osscore Expected outcome :: For example: Executing NetAct cluster status script osscore:netactvm08:started

3. To generate a list of service names, enter the following command:

Issue: 1-2

DN09118114

16



[omc]$ /opt/cpf/sbin/netact_status.sh status Expected outcome Below is part of an example output. It displays a list of services and NetAct VMs. Executing NetAct cluster status script Status of NetAct Node Service netactvm01 cpfnx2s-netactvm01 OMAgentAF-netactvm01 DNS-Master db nfs dirsrv tomcat_vcentplg socks netactvm02 netfs-netactvm02 cpfnx2s-netactvm02 OMAgentAF-netactvm02 lb-unify-backup netactvm03 netfs-netactvm03 cpfnx2s-netactvm03 OMAgentAF-netactvm03 lb-unify-primary

Status started started started started started started started started started started started started started started started started

The first column shows NetAct VM names, the second column shows the available services in each NetAct VM, and the third column shows the current status of the services.

2.1.2.2 Checking NetAct Virtual Machine IP address Prerequisites Ensure that you have done the steps in Checking the virtual machine for services, and that you have the name of the virtual machine. To extract the IP address, perform the following steps: 1. Log in to any NetAct VM as the omc user. 2. To check the FQDN and IP address of the located NetAct VM, enter the following command: [omc]$ host

Issue: 1-2

DN09118114

17



Expected outcome has address

2.1.2.3 Checking LB WAS Virtual IP and LB JBI Virtual IP Prerequisites Ensure that you have done the steps in Checking the virtual machine for services, and that you have the name of the virtual machine. To extract the IP address, perform the following steps: 1. Log in to the NetAct VM wherein the cpfnx2s service is running as the omc user. 2. To determine the FQDN for NetAct LB WAS Virtual IP, enter the following command: [omc]$ /opt/cpf/bin/cpf_list_lb_address.sh --lb was Expected outcome

3. To determine the FQDN for NetAct LB JBI, enter the following command: [omc]$ /opt/cpf/bin/cpf_list_lb_address.sh --lb jbi Expected outcome

4. To check the IP address of the FQDN, enter the following command: [omc]$ host Expected outcome has address

2.1.3 Checking the service status in NetAct Before you start the integration process, it is recommended to check if all NetAct services are running. To do this, you can follow the general instructions under Checking the virtual machine for services. The instructions below show how to check the status of specific services.

Issue: 1-2

DN09118114

18



2.1.3.1 Checking the status of Database service 1. Using an SSH client, log in to a NetAct node as omc user. 2. To check the status of the Database service, enter: [omc]$ /opt/cpf/sbin/netact_status.sh status service db Expected outcome An output like the one below appears. Executing NetAct cluster status script db::started Note: Possible states include stopped, failed, and config error.

For more information on the service status, check the Service Manager.

2.1.3.2 Checking the status of NWI3 mediation 1. Using an SSH client, log in to any NetAct node as omc user. 2. To check the status of the NWI3 service, enter the following command: [omc]$ /opt/cpf/sbin/netact_status.sh status service nwi3 Expected outcome An output like the one below appears: Executing NetAct cluster status script nwi3::started Note: Possible states include stopped, failed, and config error.

2.1.3.3 Checking the status of WAS service

1. Using an SSH client, log in to any NetAct node as omc user. 2. To check the status of the WAS service, enter the following command: [omc]$ /opt/cpf/sbin/netact_status.sh status service was

Issue: 1-2

DN09118114

19



Expected outcome An output like the one below appears: Executing NetAct cluster status script was-::started

2.1.3.4 Checking the status of FM Pipe service

1. Using an SSH client, log in to any NetAct node as omc user. 2. To check the status of the FM pipe service, enter the following command: [omc]$ /opt/cpf/sbin/netact_status.sh status service fm_pipe Expected outcome An output like the one below appears: Executing NetAct cluster status script fm_pipe-::started

2.1.3.5 Checking the status of PM Pipe service

1. Using an SSH client, log in to any NetAct node as omc user. 2. To check the status of the PM pipe service, enter the following command: [omc]$ /opt/cpf/sbin/netact_status.sh status service rep Expected outcome An output like the one below appears: Executing NetAct cluster status script rep-::started

Issue: 1-2

DN09118114

20



2.1.3.6 Checking the status of LDAP service

1. Using an SSH client, log in to any NetAct node as omc user. 2. To check the status of the LDAP service, enter the following command: [omc]$ /opt/cpf/sbin/netact_status.sh status service dirsrv Expected outcome An output like the one below appears: Executing NetAct cluster status script dirsrv::started

2.1.4 Checking NetAct licenses required for LTE software 2.1.4.1 LTE Standard software license Ensure the following licenses are installed. Application

Feature Code

License Key Name

NetAct Radio

0000003599

LTE standard SW

Table 6: Required licenses Note: For more information on software licenses for NetAct, see Software licenses for NetAct

2.1.4.2 Checking installed licenses in NetAct You can check your NetAct licenses by using the License Manager. 1. Log in to NetAct Start Page as the integration user. 2. In NetAct Start Page, open License Manager by clicking Configuration → License Manager. 3. If the License Browser view is not opened, click Licenses → License Browser to open it.

Issue: 1-2

DN09118114

21



Expected outcome The License Browser view appears. 4. In License Browser, click NetAct™ Software Licenses tab if it is not already selected. 5. Check if the license code or license name of the required license is displayed. For more instructions on license operations, see License Manager Help.

2.1.5 Checking the adaptation packages 2.1.5.1 Checking the adaptation packages in Adaptation Manager Ensure all necessary adaptation packages in NetAct are successfully deployed. 1. Log in to NetAct Start Page as the user whose group has been granted the Adaptation Manager permission. 2. Select Administration → Adaptation Manager. Expected outcome The Adaptation Manager application opens.

3. In the List of deployed Adaptations table, find the following required adaptation packages in the Identification column:

Issue: 1-2

Adaptation package

Alarm Manual Page

NOKLTE-LN4.0

NOKLTE.man-LN4.0

NOKLTE-LN5.0

NOKLTE.man-LN5.0

NOKLTE-LNFZ5.0

NOKLTE.man-LNFZ5.0

NOKLTE-LNT3.0

NOKLTE.man-LNT3.0

NOKLTE-LNT3.1

NOKLTE.man-LNT3.1

NOKLTE-LN6.0

NOKLTE.man-LN6.0

NOKLTE-LNT4.0

NOKLTE.man-LNT4.0

NOKLTE-LN7.0

NOKLTE.man-LN7.0

NOKLTE-LNF7.0

NOKLTE.man-LNF7.0

NOKLTE-LNT5.0

NOKLTE.man-LNT5.0

NOKLTE-LNZ5.0

NOKLTE.man-LNZ5.0

DN09118114

22



Adaptation package

Alarm Manual Page

NOKLTE-FL15A

NOKLTE.man-FL15A

NOKLTE-TL15A

NOKLTE.man-TL15A

NOKGOMS-LTO4.0

NOKGOMS.man-LTO4.0

NOKGOMS-LTO5.0

NOKGOMS.man-LTO5.0

NOKGOMS-LTO6.0

NOKGOMS.man-LTO6.0

NOKGOMS-LTO7.0

NOKGOMS.man-LTO7.0

NOKGOMS-LTO15A

NOKGOMS.man-LTO15A

NOKLTE-base

N/A

NOKGOMS-base

N/A

com.nsn.app.adaputil-1.

N/A

0 com.nsn.app.adaputil-2.

N/A

0

Table 7: Required adaptation packages

4. If the Status field for each adaptation shows DEPLOYED, then the required adaptations have been deployed for integration. 5. If the required adaptations are missing from the list or if any of them is in the FAILED state, then deploy them using the Deploy Adaptation tab.

2.1.5.2 Checking the PM adaptation packages in Virtual Machines Before integration, ensure that all necessary PM packages in NetAct are successfully installed. Note: If the outcome of the procedures detailed below is not as expected, please consult your System Administrator for proper deployment of the Adaptation Packages. 1. Log in to the NetAct VM on which the db_crons service is running as the omc user. 2. To check the PM adaptation database packages , enter the following command: [omc]$ /usr/bin/nokia/ManageSS.pl --list umalte noklte-db

Issue: 1-2

DN09118114

23



Expected outcome An output like the one below appears: UMALTE-5.0-NOKLTE-DB-7.2.27 (CONFIGURED) (ACTIVATED) (ACTIVE)

3. Log in to the NetAct VM on which the osscore2 service is running as the omc user. 4. To check the installed PM adaptation packages , enter the following command: [omc]$ /usr/bin/nokia/ManageSS.pl --list umalte noklte Expected outcome An output like the one below appears: UMALTE-5.0-NOKLTE-7.2.27 (CONFIGURED) (ACTIVATED) (ACTIVE)

5. To check the Adaptation Support Metadata , enter the following command: [omc]$ /usr/bin/nokia/ManageSS.pl --list content3 rslte_adapsup Expected outcome An output like the one below appears: CONTENT3-5.0-RSLTE_ADAPSUP-7.3.0.251 (CONFIGURED) (ACTIVATED) (ACTIVE)

6. To check the installed LTEMEI packages, enter the following command: [omc]$ /usr/bin/nokia/ManageSS.pl --list umalte LTEMEI Expected outcome An output like the one below appears: UMALTE-5.0-LTEMEI-7.1.28 (CONFIGURED) (ACTIVATED) (ACTIVE)

2.1.6 Checking connection from NetAct to Flexi Multiradio BTS LTE Prerequisites Ensure that Internet Control Message Protocol (ICMP) communication is allowed between the WAS VM and Flexi Multiradio BTS LTE before performing this procedure. 1. Log in to the VM running the was service as omc user.

Issue: 1-2

DN09118114

24



Note: To determine the address of the VM running the was service, refer to Checking the status of WAS service.

2. Ping Flexi Multiradio BTS LTE by entering the following command: ping Expected outcome An output like the one below appears: 64 bytes from : icmp_seq=1 ttl=252 time=0.611 ms 64 bytes from : icmp_seq=2 ttl=252 time=0.424 ms 64 bytes from : icmp_seq=3 ttl=252 time=2.39 ms --- ping statistics --6 packets transmitted, 6 received, 0% packet loss, time 5117ms .......

2.1.7 Checking NetAct time synchronization Network Time Protocol (NTP) service is used to ensure that all the nodes are synchronized. An external NTP service can be used as the time reference for NetAct. Network elements can be configured to get the NTP service from NetAct or from the external NTP server. 1. Log in to any NetAct VM as the omc user. 2. Check the NTP application status by entering: [omc]$ service ntpd status Expected outcome Below is an example output: ntpd (pid

12345) is running...

Note:

• To stop the NTP application, switch to the

root user and use the service ntpd

stop command.

• To start the NTP application, switch to the

root user and use the service ntpd

start command.

3. Check whether NetAct time is synchronized and accurate by entering: [omc]$ ntpq -p

Issue: 1-2

DN09118114

25



Expected outcome An output like the one below appears. remote refid st t when poll reach delay offset jitter ================================================================= *10.0.0.1 .PPS. 2 u 480 1024 377 0.461 0.221 0.517 netactvm01.neta 1.1.1.1 2 u 599 1024 376 0.142 -0.063 0.091 netactvm02.neta 1.1.1.1 2 u 129 1024 377 0.504 0.026 0.630 netactvm03.neta 1.1.1.1 2 u 876 1024 376 0.106 0.046 0.068 netactvm04.neta 1.1.1.1 2 u 605 1024 377 0.202 0.550 0.668 netactvm05.neta 1.1.1.1 2 u 40 1024 377 0.242 0.132 0.029 netactvm06.neta 1.1.1.1 2 u 518 1024 376 0.155 -0.289 0.035 There should be at least one entry in the output with an asterisk (*), indicating that the NTP server is synchronized to that source. The asterisk is a tally code character. For more information, see Tally Codes in http://doc.ntp.org/4.2.0/ntpq.html. For more instructions on the NTP configuration, see Administering NTP Service.

2.1.8 Prerequisites for Element Management Ensure that Node Managers are installed and configured correctly. For more information, refer to Installing Node Managers and related software. To access the Element Manager application, the following must be installed on the Node Manager server:

• Application Launcher for LTE iOMS • BTS Site Manager for eNodeB To configure and manage the ApplicationLaunchOnly group, see the following procedures under Managing Node Manager users and user groups:

• Set user account control • Check NetAct User Group information and permissions • Set permissions and roles for the user group Supported applications

Supported application versions

LTE iOMS Application Launcher

Automatically updated; install latest version

• BTSSiteEM-LTE50- • BTSSiteEM-LTE40- • BTSSiteEM-LTE60- • BTSSiteEM-LTE70- • BTSSiteEM-TD_LTE30-

BTS Site Manager

Issue: 1-2

DN09118114

26



Supported applications

Supported application versions

• BTSSiteEM-TD_LTE31-< application version>

• BTSSiteEM-TD_LTE40- • BTSSiteEM-TD_LTE50- • BTSSiteEM-LNFZ50- • BTSSiteEM-LNF70- • BTSSiteEM-LNZ50- Table 8: Supported applications and network element versions

2.1.8.1 Installing Application Launcher in Node Manager Server Note:

• If LTE iOMS Application Launcher is already installed, then you may proceed to Installing the BTS Site Manager.

• The following steps apply to supported network element versions indicated in Supported applications and network element versions.

• If you have the Disaster Recovery Solution in your NetAct system, perform this procedure in the Disaster Recovery Site (SITE-B).

2.1.8.1.1 Downloading LTE iOMS Application Launcher installer 1. Using Remote Desktop, log in to the Node Manager Server (Domain Member) as administrator. 2. Open a web browser and enter the northbound IP address of LTE iOMS. Note:

• The LTE iOMS northbound IP address must be added to the list of trusted sites in the web browser. Refer to the browser manual for more information.

• A secure connection (HTTPS) is required when browsing the LTE iOMS website. 3. To log in, enter the proper credentials used in accessing LTE iOMS. 4. For release version RL70, click Download AL. For release version RL60 or older, do the following: 1. Click the OMS Management drop-down menu and select Download Application Launcher. 2. Click Download Application Launcher Client 2.

Issue: 1-2

DN09118114

27



Note: For more detailed information, refer to the OMS Operating Documentation for the specific release version you are using.

5. Select the appropriate installer for your operating system, and then save the setupwin32.exe file in a designated drive.

2.1.8.1.2 Installing and configuring Application Launcher 1. Using Remote Desktop, log in to Node Manager Server (Domain Member) as administrator. 2. Run the setupwin32.exe file and follow the instructions provided by the Installation Wizard. Note:

• The Application Launcher requires 32bit Java version JRE 1.6.0 update 45 or higher to be installed. For more information, contact your NetAct administrator.

• Tick the Desktop Shortcuts option when prompted to create an application shortcut. Expected outcome The Application Launcher Client 2 is successfully installed and an application shortcut appears on the desktop.

3. Create a folder for the supported network element version in Node Manager Server (Domain Member). C:\Apps\Nokia\NokiaOss\config\EM\NOKGOMS\\ For example, C:\Apps\Nokia\NokiaOss\config\EM\NOKGOMS\LTO4.0\ Note: For the release version information, refer to Compatibility information.

4. From the Desktop, copy the Application Launcher Client 2 and paste it in the newly created folder. 5. Right-click the Application Launcher Client 2 shortcut. Click Rename and enter ApplicationLauncher.

2.1.8.2 Installing BTS Site Manager in Node Manager Server Note: The following steps apply to supported network element versions indicated in NetAct and Flexi Multiradio LTE BTS compatibility information and NetAct and LTE iOMS compatibility information.

Issue: 1-2

DN09118114

28



If you have the Disaster Recovery Solution in your NetAct system, perform this procedure in the Disaster Recovery Site (SITE-B). 1. Using a remote desktop, log in to Node Manager Server (Domain Member) as administrator. 2. Run the BTSSiteEM-.exe file. For example, BTSSiteEM-LTE50-1234_123_12.exe. Follow the instructions provided by the Installation Wizard. Note: Contact your network element administrator for the location of this file. There are two options for installation, Normal Installation and Clean Installation.

• Select Normal Installation to add the new BTS Site Manager version to the system. • Select Clean Installation to install the latest version of the BTS Site Manager and remove old versions from the system. Expected outcome The BTS Site Manager is successfully installed and an application shortcut appears on the desktop.

3. Create a folder for the supported network element version in Node Manager Server (Domain Server). C:\Apps\Nokia\NokiaOss\config\EM\NOKLTE\\ For example, C:\Apps\Nokia\NokiaOss\config\EM\NOKLTE\LN4.0\ Note: For the release version information, please refer to Compatibility information.

4. From the Desktop, copy the BTS Site Manager shortcut and paste it in the newly created folder. 5. Right-click the BTS Site Manager shortcut. Click Rename and enter wbtssitemanager.

2.2 Prerequisites for LTE iOMS This chapter describes the required tasks to be completed before integration, and the information required to perform the integration procedure. LTE iOMS requirements


LTE iOMS release version

Ensure that the current LTE iOMS release version is supported by NetAct. For the list of supported LTE iOMS release versions, refer to Compatibility information.

Issue: 1-2

DN09118114

29


LTE iOMS requirements


Additional information To check the LTE iOMS software versions using the web interface of Software Version Viewer: 1. Log in to the OMS web page (https://) using the LTE iOMS local user name. The default user, Nemuadmin, may be used; however, please coordinate with your Network Administrator for proper NE User Accounts. 2. Select OMS Management → SW Version Viewer → View Current SW Sets. Note: For version RL70 or newer, select OMS SW Version Viewer. For more information, refer to the OMS Operating Documentation for the specific release version you are using. 3. The Current Sets pane displays the software version of LTE iOMS. The instructions on how to check the software version level are also available in the LTE Radio Access Operating Documentation in the NSN online library. Open LTE Radio Access Operating Documentation and navigate to Installing and Commissioning LTE iOMS → Managing incremental software deliveries (minor software upgrade) → Verifying software level. Note that this document has several versions depending on the software release. As an example, you may refer to LTE Radio Access Documentation (DN0956464).

LTE iOMS is installed and commissioned

Installation and commissioning refers to the installation

successfully

of the Blade server into the rack, the installation of LTE iOMS software (only if the iOMS is not preinstalled), postinstallation, the inspections, and internal configurations required before the Integrated Operation Mediation Subsystem (iOMS) is taken into use. The installation can be performed using a portable storage device. To know more details about pre-installation, installation, and post-installation of LTE iOMS, refer to the LTE Radio Access Operating Documentation in the NSN online library. Open LTE Radio Access Operating Documentation and navigate to Installing and Commissioning LTE iOMS. Note that this document has several versions, depending on the software release. As an example, you may refer to LTE Radio Access Operating Documentation (DN0956464).

Issue: 1-2

DN09118114

30




Additional information To perform checks after installation and commissioning of iOMS, refer to the LTE Radio Access Operating Documentation in the NSN online library. Open LTE Radio Access Operating Documentation and navigate to Installing and Commissioning LTE iOMS → Integrating LTE iOMS to the network → Performing checks after installation and commissioning of iOMS. Note that this document has several versions depending on the software release. As an example, you may refer to LTE Radio Access Operating Documentation (DN0956464).

LTE iOMS Element Manager

LTE iOMS Element Manager (EM) is a tool for performing operation tasks in the Network Element using graphical user interface applications. EM consists of an application launcher (AL) and EM application that are downloaded and installed from iOMS located in the network element to the client computer (EM workstation). For requirements and installation procedures, refer to the LTE Radio Access Operating Documentation in the NSN online library. Open LTE Radio Access Operating Documentation and navigate to Installing and Commissioning LTE iOMS → LTE iOMS Element Manager configuration. Note that this document has several versions depending on the software release. As an example, you may refer to LTE Radio Access Operating Documentation (DN0956464).

LTE iOMS Parameter Tool

For version RL70 or onwards, the Parameter Tool is no longer visible in the Application Launcher by default. To make the Parameter Tool visible: 1. Using an SSH client, log in to LTE iOMS as Nemuadmin user, and then switch to root user. 2. To assign user to group _nokfsuiparametertool, enter the following command: # fsgpasswd -a USER _ nokfsuiparametertool 3. To force NWI3Adapter to update its cached authorization information, enter the following command: # fscorbaseccli -c updatetoken 4. Restart the Application Launcher. Expected outcome

Issue: 1-2

DN09118114

31




Additional information The Parameter Tool is visible in the Application Launcher. For more information, refer to the OMS Operating Documentation for the specific release version you are using.

Table 9: Preparation checklist for LTE iOMS The table below shows the information required for integrating LTE iOMS and NetAct. LTE iOMS information


LTE iOMS

Southbound IP

BTSOM protocol, network element uses this IP address for

Basic

Address

connecting LTE iOMS. LTE iOMS NTP (Network Time Protocol)

Information

server. Vsftpd, sshd, and httpd are configured to listen to both southbound and northbound IP addresses. Northbound IP

This IP is used mainly toward NetAct. EM, NWI3, DNS Vsftpd,

Address

sshd, and httpd are configured to listen to both southbound and northbound IP addresses.

NWI3 User in

If a user account other than the default username and password

LTE iOMS

(Nemuadmin / nemuuser) is needed for NWI3 services, it can be created. The username can be freely selected, but an identical user needs to be present in NetAct. 1. Log in to LTE iOMS as Nemuadmin user, and then switch to root user. 2. To create a new NWI3 user, enter the following command: # fsuseradd -g 557 -G Example: # fsuseradd -g 557 testuser2 -G pmgRoot,_ nokOMSCommonmanage,_nokFaultManagementmanage,_ nokRNWCMManagementmanage,_ nokfsuiexternalldaplogin,_ nokActiveSessionsmanage 3. To set a password for the created user, enter the following command: passwd Example: passwd testuser2 4. To restart the NWI3 Adapter, enter the following command: fshascli -r /NWI3Adapter The following prompt appears: The request will terminate all the processes running in /NWI3Adapter.

Issue: 1-2

DN09118114

32


LTE iOMS information


Additional information Are you sure you want to proceed? [y/n] Enter Y to restart NWI3Adapter. Information is also available in LTE Radio Access Operating Documentation in the NSN online library. Open LTE Radio Access Operating Documentation and navigate to Installing and Commissioning LTE iOMS → Integrating LTE iOMS to the network → Creating NWI3 user in LTE iOMS. Note that this document has several versions depending on the software release. As an example, you may refer to LTE Radio Access Operating Documentation (DN0956464).

LTE iOMS ID or

Ensure that the system ID of OMS is configured correctly,

System ID

otherwise problems will be encountered when sending notifications to NetAct. Note: The system Id must be unique in the whole network. Please check your Network Element Management Plan or Network Administrator for correct values. 1. Log in to LTE iOMS as Nemuadmin user, and then switch to root user. 2. To change the OMS system ID, start the zchangecluster-id script by entering the following command: zchangecluster-id 3. Specify the OMS ID. For example, OMS id number <1-65535>: Any number falling within the 1-65535 range can be used for the OMS ID number. See the Network Element Operating Documentation for the specific network element version you are using for more information. 4. To restart NWI3Adapter, enter the following command: fshascli -r /NWI3Adapter The following prompt appears: The request will terminate all the processes running in /NWI3Adapter. Are you sure you want to proceed? [y/n] Enter Y to restart NWI3Adapter. Note: The cluster id is unchanged during the default or current session. It is valid from new sessions onward.

Issue: 1-2

DN09118114

33



LTE iOMS information


LTE iOMS

The default user details are:

User Account

Element

• Username: Nemuadmin • Password: nemuuser

Manager

It is recommended to change the password after first login to prevent unauthorized access. To know more about LTE iOMS User Management, refer to LTE Radio Access Operating Documentation in the NSN online library. Open LTE Radio Access Operating Documentation and navigate to Administering and Security in the LTE iOMS → User security → User authorization. Note that this document has several versions depending on the software release. As an example, you may refer to LTE Radio Access Operating Documentation (DN0962925). LTE iOMS DNS

DNS zone of

Please check your Network Element Management Plan or Network

Domain

the LTE iOMS

Administrator for correct values.

LTE iOMS

Please check your Network Element Management Plan or Network

Hostname

Administrator for correct values.

LTE iOMS

For the list of ports, refer to Setting up firewall rules

communication matrix

Table 10: Interface and ports information required for integrating LTE iOMS

2.2.1 Checking IP connectivity between LTE iOMS and NetAct Prerequisites Ensure that Internet Control Message Protocol (ICMP) communication is allowed between the WAS VM and Flexi Multiradio BTS LTE before performing this procedure. 1. Log in to the NetAct VM running the WAS service as omc user. 2. Ping LTE iOMS by entering the following command: ping Expected outcome An output like the one below appears: 64 bytes from : icmp_seq=1 ttl=252 time=0.611 ms 64 bytes from : icmp_seq=2 ttl=252 time=0.424 ms 64 bytes from : icmp_seq=3 ttl=252 time=2.39 ms

Issue: 1-2

DN09118114

34



--- ping statistics --6 packets transmitted, 6 received, 0% packet loss, time 5117ms .......

2.2.2 Configuring a heartbeat interval for Flexi Multiradio BTS LTE This parameter defines the time after which the alarm 70246 ALARM SYSTEM HEARTBEAT is raised or cancelled. The alarm system is interchangeably raising and clearing this alarm after the expiration of each heartbeat interval. If the refreshing of the alarm does not occur, it signals that the alarm system is faulty. Note: Following below steps requires AlarmSystem restart.

1. Log in to the Application Launcher and provide required credentials. You can use the default user account, Nemuadmin. 2. Double-click Parameter Tool. Note: If the Parameter Tool is not visible in the Application Launcher, follow the procedure under the LTE iOMS Parameter Tool entry in the Preparation checklist for LTE iOMS table to make the Parameter Tool visible. 3. In the left application pane, select fsClusterId=ClusterRoot → fsFragmentId=AlarmMgmt → fsFragmentId=AlarmProcessors → fsAlarmProcessorId=AlarmProcessor1> → fsAlarmProcessorConfigurationId=Default. In the right application pane, find the fsHeartbeatInterval attribute. 4. Set the fsHeartbeatInterval parameter value according to needs.

• 300s = default • 0s = disable heartbeat Note: Check the operating documentation of the specific release version of the LTE iOMS you are configuring for more details on fsnwi3heartbeatPeriod .

5. To restart the AlarmSystem, enter the following command: fshascli -rn /AlarmSystem Expected outcome The AlarmSystem restarts and the updated value of the parameter is applied.

Issue: 1-2

DN09118114

35



2.2.3 Configuring LTE iOMS TLS modes Different Transport Layer Security Protocol (TLS) mode parameters are being supported by LTE iOMS. The below information describes the parameters and the possible values, as well as the meaning of each value.

2.2.3.1 TLS operation mode in Flexi Multiradio BTS LTE Transport Layer Security in the eNB (omsTLS parameter) can be configured as:

• Probing (Secure/Unsecure): Both secure and unsecure O&M connections are allowed between the LTE iOMS and the eNodeB. If the connection setup to both secure and unsecure ports fails, the eNodeB starts the connection procedure from the beginning, that is, it tries to establish secure connection first. This setting should be used for only for transition from unsecure to secure BTS O&M interface without limiting the connectivity. From the security point of view, it is recommended not to use this setting permanently.

• Forced: Only secure O&M connections are established between LTE iOMS and eNB. • Off : Only unsecure O&M connections are established between LTE iOMS and eNB. This is the default setting. Note: Ensure that the configuration of the operation mode settings is the same for eNodeB and LTE iOMS. If the settings differ, the eNodeB might not be able to connect, but will continue trying to connect even though the LTE iOMS connection port is closed.

2.2.3.2 BTS and O&M Protocol (OM) security mode in LTE iOMS The TLSModeOM parameter in LTE iOMS can be configured as any of the following:

• Probing (Secure/Unsecure): Both secure and unsecure O&M protocol connections are allowed. Both secure and unsecure ports are open. When the parameter value is changed from Off to Probing, the LTE iOMS resets the port 8002 to trigger the eNodeB change from unsecure to secure connection.

• Forced: Only secure O&M protocol connections are established. The LTE iOMS and the eNodeB use the TLS_RSA_WITH_AES_128_CBC_SHA cipher suite. The unsecure port (8002) is closed.

• Off: Only unsecure O&M protocol connections are allowed. The secure port (8003) is closed. 2.2.3.3 File Transfer (FT) security mode in LTE iOMS For file transfer between LTE iOMS and eNodeB there is a separate parameter (TLSModeFT) which can be configured as any of the following:

• Forced: Only secure file transfers are allowed. - The LTE iOMS and the eNodeB use the TLS_RSA_WITH_RC4_128_SHA cipher suite. - The secure port (443) is open. Insecure ports are closed (FTP 20, HTTP 80). This is the default value.

Issue: 1-2

DN09118114

36



• Probing: Both secure and unsecure file transfers are allowed between LTE iOMS and eNodeB. Secure file transfer is tried first. File transfers between LTE iOMS and NetAct are in secure mode only. Both secure and unsecure ports are open.

• Off: Only unsecure file transfers are allowed. Both secure and unsecure ports are open. The file transfers between eNodeB and LTE iOMS depend on the BTS O&M interface state. If the interface state is secure, then the file transfer is also secure. If the negotiated file transfer protocols allow both unsecure and secure file transfers, and the file transfer attempts from both secure and unsecure ports fails, the client does not retry, but aborts the procedure.

2.2.3.4 Allowed TLS mode combinations The allowed combinations of TLS modes are listed in the table below. Only these combinations are allowed because of dependencies between O&M connection and file transfer secure state in some network elements. TSLModeFT

TSLModeOM

Forced

Forced

Forced *

Probing

Probing

Forced

Probing

Probing

Probing

Off

Off

Probing

Off

Off

Table 11: Allowed TLS mode combinations *

This combination can be introduced provided that the eNodeB has successfully established the

secure BTSOM connection.

2.2.3.5 Configuring File Transfer modes in LTE iOMS 1. From the Application Launcher, open the LTE iOMS Parameter Tool. Note: If the Parameter Tool is not visible in the Application Launcher, follow the procedure under the LTE iOMS Parameter Tool entry in the Preparation checklist for LTE iOMS table to make the Parameter Tool visible.

2. To find the TLSModeFT and TLSModeOM parameters in OMS, use the following:

Issue: 1-2

DN09118114

37



fsClusterId=ClusterRoot → fsFragmentId=OMS → omsFragmentId=System → omsFragmentId=Network → omsFragmentId=TLS 3. Set the value of the TLSModeFT or TLSModeOM parameter according to possible values indicated in BTS and O&M Protocol (OM) security mode in LTE iOMS and File Transfer (FT) security mode in LTE iOMS.

2.2.3.6 Mandatory certificates for TLS configuration in LTE iOMS Attribute

Forced

Probing

Off

TLSModeFT

Mandatory

Mandatory for file

None

transfers between NetAct and LTE iOMS. Options for network elements. TLSModeOM

Mandatory

Optional

None

Table 12: Mandatory certificates

Attribute

HTTP server certificate

HTTP client trusted CA

BTSOM server certificate

certificate TLSModeFT

x

BTSOM server trusted CA certificate

x x

TLSModeOM

x

Table 13: Certificates required for secure connections

2.2.3.7 Installing certificates for secure communication To completely enable the TLS for Secure File Transfer, ensure the certificates are installed on the network element. For more information, refer to Certificate lifecycle management in the LTE RAN O&M Security chapter of the LTE Radio Access Operating Documentation in the NSN online library. Note that this document has several versions, depending on the software release. As an example, you may refer to LTE Radio Access Operating Documentation ( DN0958798) Certificates must be installed in NetAct to complete the Trust cycle and enable the Secure Communication:

• CM certificates - For more information, refer to Adding certificates for CM upload. • NE certificates - For more information, refer to Adding a network element certificate to the NWI3 mediation's truststore.

• NWI3 certificates - For more information, refer to Configuring the Tomcat NWI3-HTTP server.

Issue: 1-2

DN09118114

38



2.2.4 Configuring DNS service on LTE iOMS OMS DNS can be configured to connect to an external DNS server. Restarting the ClusterDNS service activates the new configuration. Note:

• DNS can also be reconfigured by executing the zmodifyNetworkSettings script. Using zmodifyNetworkSettings, however, requires the following data besides the DNS IP address: - OMS IP address - subnet mask - gateway address - NTP IP address Executing zmodifyNetworkSettings resets the system in order to apply new settings.

• LTE iOMS can be configured for several DNS servers. You need root access in order to modify DNS settings and restart the DNS service. 1. Using an SSH client, log in to LTE iOMS. 2. To check the current DNS server IP address, enter the following command: # fsipnet get service ClusterDNS This shows the DNS IP configuration stored in LDAP. Note: Another option is to show the current external DNS IP configuration. To do this, enter the following command: # cat /etc/ClusterDNS.conf | grep forwarders Expected outcome fsipnet service add ClusterDNS forwarder 192.0.2.1 forwarder 192.0.2.2 forwarder 192.0.2.3

3. Modify the DNS server address. To do this, you can do any of the following:

• Add the DNS server IP address by entering the following command: fsipnet service modify ClusterDNS addforwarder

• Remove the DNS server IP address by entering the following command: fsipnet service modify ClusterDNS delforwarder

• Remove the whole ClusterDNS by entering the following command: Issue: 1-2

DN09118114

39



fsipnet service delete ClusterDNS

• Recreate the ClusterDNS after it has been deleted by entering the following command: fsipnet service add ClusterDNS

• Add service by entering the following command: fsipnet service add ClusterDNS forwarder [forwarder <2nd_dns_ip_address>][forwarder <3rd_dns_ip_address>] For example, to configure LTE iOMS to use a DNS server with IP address 10.0.0.1, enter the following command: fsipnet service modify ClusterDNS addforwarder 10.0.0.1 4. To save the changes made, enter the following command: fsipreconfigure commit 5. To update HAS parameters and restart the ClusterDNS service, enter following command: fshascli -r /ClusterDNS Expected outcome The changes to the configuration are saved and applied. 6. To check if the primary DNS server is configured correctly, enter the following command: # ping

2.2.5 Configuring time synchronization in LTE iOMS Flexi Multiradio BTS LTE can get NTP service and keep time synchronization from LTE iOMS. LTE iOMS can get NTP service from NetAct or an external NTP server. To configure NetAct as the time source, do the following steps: Note: To ensure high availability, it is recommended to configure at least one external NTP server for LTE iOMS. The minimum configuration is one NetAct server and one external NTP server. 1. Using an SSH client, log in to OMS as Nemuadmin user and then switch to root user. 2. To check the NTP settings, enter the following command: fsipnet service get ClusterNTP

Issue: 1-2

DN09118114

40



Expected outcome An output like the one below appears: fsipnet service add ClusterNTP forwarder

3. If an unwanted NTP service host IP address is displayed, remove the NTP service by entering the following command: fsipnet service delete ClusterNTP If no output is displayed, add an NTP service with request forwarders by entering the following command: fsipnet service add ClusterNTP forwarder forwarder forwarder [forwarder <4th_ntp_ip_address>] Note:

• For high availability purposes, it is recommended to add all possible NetAct VM IP addresses which host the NTP service as the NTP reference for LTE iOMS.

• For LTE iOMS integration, at least more than one NetAct VM IP address should be added as forwarders, and the NetAct VM which hosts NWI3 service should be the first forwarder. If only one forwarder IP address is shown and it is the NetAct VM which hosts the NTP service, then add at least one additional NTP VM IP address which also hosts the NTP service by entering the following command: fsipnet service modify ClusterNTP addforwarder 4. Restart the NTP service to activate the newly added NTP forwarders by entering the following command: fshascli -rn /ClusterNTP Expected outcome The NTP service is restarted successfully. 5. Log out of OMS.

Issue: 1-2

DN09118114

41



2.3 Prerequisites for Flexi Multiradio BTS LTE This chapter describes the required tasks to be completed before integration, and the information required during the integration procedure. Before you start the integration, ensure that the Flexi Multiradio BTS LTE meets the following requirements in the table below. Flexi Multiradio BTS LTE requirements


Flexi Multiradio BTS LTE software version

Ensure that the current Flexi Multiradio LTE BTS release version is supported by NetAct. For the list of supported Flexi Multiradio LTE BTS software versions, refer to Compatibility information of Flexi Multiradio BTS LTE releases and NetAct. If the current Flexi Multiradio BTS LTE release version is not supported by NetAct, the software must be upgraded. For eNodeB software update, refer to NE Operating Documentation chapter of the Commissioning Flexi Multiradio BTS LTE Updating BTS Site software document in the NSN online library. Note that this document may have several versions, depending on the software release. As an example, you may refer to Commissioning Flexi Multiradio BTS LTE Updating BTS Site software (DN0951893). To check the current Flexi Multiradio BTS LTE release version, refer to BTS LTE operational documentation.

BTS Site Manager is installed successfully.

The BTS Site Manager must be installed in order to configure, commission, and manage Flexi Multiradio BTS LTE. For BTS Site Manager prerequisites and installation information, refer to LTE Radio Access Operating Documentation in the NSN online library. Open LTE Radio Access Operating Documentation and navigate to Commissioning Flexi Multiradio BTS LTE → Installing BTS Site Manager. Note that this document may have several versions depending on the software release. As an example, you may refer to LTE Radio Access Operating Documentation (DN0956464).

O&M agent is commissioned successfully.

To perform checks after installation and commissioning of iOMS, refer to the LTE Radio Access Operating Documentation in the NSN online library. Open LTE Radio Access Operating Documentation and navigate to Installing and Commissioning LTE iOMS → Performing checks after installation and commissioning of iOMS. Note that this document may

Issue: 1-2

DN09118114

42



Flexi Multiradio BTS LTE requirements

Additional information have several versions depending on the software release. As an example, you may refer to LTE Radio Access Operating Documentation (DN0956464).

Table 14: Preparation checklist for Flexi Multiradio BTS LTE The table below shows the information required for integrating eNodeB to LTE iOMS and NetAct. Flexi Multiradio BTS LTE information


Flexi

Instance

When LTE BTS is commissioned for the first time, ensure

Multiradio

identifier

that its base ID is unique in NetAct scope. The instance

BTS LTE

of the Flexi

identifier is used when creating the LTE BTS managed

basic

Multiradio

object in NetAct.

information

BTS LTE To check the Instance Identifier of the LTE BTS, connect or log in to LTE BTS using BTSSM and check the properties window. For detailed instructions, refer to Checking the instance identifier of Flexi Multiradio BTS LTE. Service Users For more information, refer to Creating service users required for Flexi Multiradio BTS LTE Integration Flexi

For more information, refer to Setting up firewall rules

Multiradio BTS LTE Firewall Ports IP address

The connections between NetAct, LTE iOMS, and Flexi Multiradio BTS LTE are based on IP Protocols. There are several ways to establish WAN connections between NetAct and remote network elements. Just ensure that the Flexi Multiradio BTS LTE are integrated into the IP network. Refer to the network management plan or contact your network element administrator for more information.

Element Manager

User Accounts User name and password for connecting BTSSM to Flexi Multiradio BTS LTE. The default user name is Nemuadmin and the default password is nemuuser.

Issue: 1-2

DN09118114

43


Flexi Multiradio BTS LTE information


Additional information Note: The defaults may not apply in your current environment. For more information, contact your network element administrator.

Table 15: Required information for integrating Flexi Multiradio BTS LTE

2.3.1 Commissioning Flexi Multiradio BTS LTE For information on integrating and configuring Flexi Multiradio BTS LTE to LTE iOMS, see Autoconnection and Autoconfiguration phases in Configuring LTE eNB using Autoconnection and Autoconfiguration. You may also refer to NE Operating Documentation chapter for Commissioning Flexi Multiradio BTS LTE Updating BTS Site software. Note that this document may have several versions, depending on the software release. As an example, you may refer to Commissioning Flexi Multiradio BTS LTE Updating BTS Site software (DN0951893).

2.3.2 Checking the instance identifier of Flexi Multiradio BTS LTE 1. Launch the BTS Site Manager. 2. In the BTS Site Manager log in window, enter the following information:

• IP address of Flexi Multiradio BTS LTE • username • password Note: To determine the IP address and Element Manager user accounts of Flexi Multiradio BTS LTE, refer to Required information for integrating Flexi Multiradio BTS LTE.

3. Click Connect. 4. In the left side of the BTS Site Manager window, click BTS Hardware. 5. In BTS Equipment View, click the BTS object. Expected outcome The BTS Properties View window displays the object properties. 6. For the instance identifier of the BTS LTE, refer to the BTS ID field.

Issue: 1-2

DN09118114

44



2.3.3 Checking IP connectivity between Flexi Multiradio BTS LTE and LTE iOMS Prerequisites Ensure that ICMP is enabled between Flexi Multiradio BTS LTE and LTE iOMS before performing this procedure. 1. Log in to LTE iOMS using an SSH client. You may use the default user, Nemuadmin. 2. Ping Flexi Multiradio BTS LTE by entering the following command: ping Expected outcome A message like the one below appears: xx bytes from : icmp_seq=1 ttl=252 time=x.xxx ms xx bytes from : icmp_seq=2 ttl=252 time=x.xxx ms xx bytes from : icmp_seq=3 ttl=252 time=x.xxx ms --- ping statistics --x packets transmitted, x received, x% packet loss, time xxxxms

2.3.4 Configuring Flexi Multiradio BTS LTE time synchronization with NetAct This section describes how to configure NetAct as the time source for Flexi Multiradio BTS LTE.

Accurate time synchronization is the key element to ensure the capability of providing reliable mobile network services. Nokia recommends that you consider the time synchronization as part of the IP network planning: what the time source for NetAct and Flexi Multiradio BTS LTE is, and what the time sharing topology is. NetAct and Flexi Multiradio BTS LTE must synchronize the time, but the scenarios varies as the following:

• NetAct and Flexi Multiradio BTS LTE use the same time source (external NTP server). • NetAct and Flexi Multiradio BTS LTE use different time sources (external NTP servers). • Flexi Multiradio BTS LTE uses NetAct as the secondary or tertiary time source. Note: There must be more than one time sources with synchronized time. It is not recommended to use NetAct as the primary time source for Flexi Multiradio BTS LTE. To ensure high availability, configure at least one external NTP server for Flexi Multiradio BTS LTE. Therefore, the minimum configuration is one NetAct server and one external NTP server.

Issue: 1-2

DN09118114

45



If you need to configure NetAct as the time source for the Flexi Multiradio BTS LTE, perform the following steps. Otherwise, skip this section. 1. Launch the BTS Site Manager. 2. In the BTS Site Manager log in window, enter the following information:

• IP address of Flexi Multiradio BTS LTE • username • password Note: To determine the IP address and Element Manager user accounts of Flexi Multiradio BTS LTE, refer to Required information for integrating Flexi Multiradio BTS LTE.

3. Click Connect. 4. In the left side of the BTS Site Manager window, click IP. 5. In the IP View, click System Time. 6. In the System Time dialog, add the NTP server IP address in the table. 7. Click Send to save the changes.

2.3.5 Activating measurements configuration through BTS Site Manager Prerequisites Ensure that the BTS Site Manager is installed before performing this procedure. 1. Log in to BTS Site Manager. 2. Select the BTS PM tab. 3. Select Measurement Configuration. Expected outcome The BTS Performance Monitoring window displays all measurements. 4. Refer to your KPI measurement and set measurement types to In Use and specify the corresponding Interval. Expected outcome All measurement types are set.

Issue: 1-2

DN09118114

46



Figure 3: BTS Site Manager Measurement Configuration

5. Click Send. Expected outcome The measurement configuration is activated.

2.4 Prerequisites for intermediate system Ensure that the following configurations are set correctly in the intermediate systems in the DCN backbone.

• Firewall rules settings • Routing configuration • Network Time Protocol (NTP) configuration

Issue: 1-2

DN09118114

47



2.4.1 Setting up firewall rules Before creating connections between NetAct and Flexi Multiradio BTS LTE, open the ports that are allowed in the network element. If the network element uses an external NTP server or an external DNS server, ensure that appropriate firewall ports (123 for NTP and 53 for DNS) are open for these services. The default firewall rules for connecting Flexi Multiradio BTS LTE to NetAct are listed in the table below. FTP service is disabled by default in NetAct. Enable FTP service manually. For detailed instructions on how to enable FTP service, see Starting FTP. Source

Source Port

Dest.

Dest. Port

AL1

TL2

Service Object

Description

OMS

ephemeral3

NWI3

80

HTTP

TCP

http

HTTP port used by OMS file download (hardcoded in OMS). There is a port forwarding rule set to forward all traps coming to port 80 to port 9294.

OMS

ephemeral3

NWI3

443

HTTPS

TCP

https

HTTPS port used by OMS file download (hardcoded in OMS). There is a port forwarding rule set to forward all traps coming to port 443 to port 9295.

OMS

ephemeral3

NWI3

9294

HTTP

TCP

http-oms-file-

HTTP forward port

download

used by OMS file download

OMS

ephemeral3

NWI3

9295

HTTPS

TCP

https-oms-file-

HTTPS forward port

download

used by OMS file download

OMS

OMS

OMS

ephemeral3

ephemeral3

ephemeral3

NWI3

NWI3

NWI3

49152

49164

49177

IIOP

IIOP

IIOP

TCP

TCP

TCP

nwi3-reg-

NWI3 registration

service

service

nwi3-notific-

NWI3 notification

service

service

nwi3-topology-

NWI3 topology event

event-consumer consumer OMS

ephemeral3

NWI3

49179

IIOP

TCP

nwi3-alarm-

NWI3 alarm event


ephemeral3

NWI3

49192

IIOP

TCP

nwi3-trace-

NWI3 trace event

event-consumer consumer

Issue: 1-2

DN09118114

48



Source

Source Port

Dest.

Dest. Port

AL1

TL2

Service Object

Description

OMS

ephemeral3

NWI3

49300

IIOP

TCP

nwi3-cm-event-

NWI3 CM event

notification

notification

nwi3-topology-

NWI3 topology service

OMS

ephemeral3

NWI3

49311

IIOP

TCP

service-callback OMS

ephemeral3

NWI3

49312

IIOP

TCP

nwi3-topology-

NWI3 topology delete

delete-callback OMS

ephemeral3

NWI3

49350

IIOP

TCP

nwi3-hw-agent

NWI3 HW event consumer

OMS

ephemeral3

NWI3

49354

IIOP

TCP

nwi3-audit-trail-

NWI3 audit trail

callback OMS

ephemeral3

NWI3

49509

IIOP

TCP

nwi3-license-

NWI3 licence event


ephemeral3

NWI3

49510

IIOP

TCP

nwi3-cert-agent

NWI3 certificate management

OMS

ephemeral3

NWI3

49530

IIOP

TCP

nwi3-pm-event-

NWI3 pm event

consumer

consumer

OMS

ephemeral3

NWI3

49557

IIOP

TCP

nwi3-sw-upload

NWI3 Software Upload

OMS

ephemeral3

NWI3

49558

IIOP

TCP

nwi3-sw-

NWI3 Software

download

Download

nwi3-sw-

NWI3 Software change

change-event-

event consumer

OMS

ephemeral3

NWI3

49559

IIOP

TCP

consumer OMS

ephemeral3

NWI3

49560

IIOP

TCP

nwi3-sw-

NWI3 Software update

update-event-

event consumer

consumer OMS

ephemeral3

NWI3

49600

IIOP

TCP

nwi3-audit-trail-

NWI3 audit trail event


ephemeral3

NWI3

49619

IIOP

TCP

tcp-49619

NWI3 CNUM mediator management

OMS

OMS

ephemeral3

ephemeral3

NWI3

NWI3

49620

49622

IIOP

IIOP

TCP

TCP

nwi3-mediator-

NWI3 integration

callback

mediator management

nwi3-local-

NWI3 user

security-

management

callback OMS

OMS

OMS

ephemeral3

ephemeral3

ephemeral3

NWI3

NWI3

NWI3

49333

49344

49561

IIOP

IIOP

IIOP

TCP

TCP

TCP

nwi3-swm-

NEBR download

nodebackup

callback agent

nwi3-swm-

NEBR upload callback

nodebackup

agent

nwi3-sw-commit NWI3 Software Commit/Rollback

OMS

ephemeral3

NWI3

123

NTP

UDP

ntp

NetAct server clock time set to actual time

Issue: 1-2

DN09118114

49


Source

Source Port


Dest.

Dest. Port

AL1

TL2

Service Object

Description from external NTP server

OMS

Any

OMS

ephemeral3

NWI3

33749

HTTPS

TCP

SBI-

443

HTTP/S

TCP

https

CM NWI3 data file

CommonMediation OMS

ephemeral3

SBI-

transfer 80

HTTP

TCP

http

CommonMediation OMS

ephemeral3

SBI-

ephemeral3

49400 -

WebSphere

CM NWI3 data file transfer

CommonMediation 49499 OMS

For software backup

CORBA/

TCP

IIOP

49400-49499 CORBA/

tcp-49400 -

CM NWI3

49499 TCP

https

For CM upload

IIOP OMS

Any

LB WAS virtual IP

80

HTTP

TCP

http

HTTP

OMS

Any

LB WAS virtual IP

443

HTTPS

TCP

https

HTTPS

NWI3

ephemeral3

OMS

49341

IIOP

TCP

nwi3-security-

NWI3 Security

fragment

fragment

nwi3-swm-

NWI3 SWM NEBR

NWI3

ephemeral3

OMS

49348

IIOP

TCP

nodebackup NWI3

ephemeral3

OMS

49342

IIOP

TCP

nwi3-license-

NWI3 LM Agent

mgr-agent NWI3

NWI3

ephemeral3

ephemeral3

OMS

OMS

49351

49361

IIOP

IIOP

TCP

TCP

nwi3-topology-

NWI3 Topology

service

Service

nwi3-pm-

NWI3 PM Service

service NWI3

ephemeral3

OMS

49363

IIOP

TCP

nwi3-sw-agent

NWI3 SW Agent

NWI3

ephemeral3

OMS

49566

IIOP

TCP

nwi3-adapter

NWI3 Adapter

NWI3

ephemeral3

OMS

80

HTTP

TCP

http

HTTP file transfers from OMS

NWI3

ephemeral3

OMS

443

HTTPS

TCP

https

HTTPS file transfers from OMS

NWI3

ephemeral3

OMS

22

SSH/SFTP TCP

ssh

Secured shell and secured file transfer from OMS

NWI3

ephemeral3

OMS

23

TELNET

TCP

telnet

Telnet session to OMS

NWI3

ephemeral3

MRBTS

80

HTTP

TCP

http

HTTP file transfers from MRBTS

NWI3

ephemeral3

MRBTS

443

HTTPS

TCP

https

HTTPS file transfers from MRBTS

Issue: 1-2

WebSphere

ephemeral3

OMS

49350

IIOP

TCP

nwi3-hw-agent

NWI3 HW Agent

WebSphere

ephemeral3

OMS

49357

IIOP

TCP

nwi3-cm-plan-

NWI3 CM Plan

mgmt

Management

DN09118114

50



Source

Source Port

Dest.

Dest. Port

AL1

TL2

Service Object

Description

WebSphere

ephemeral3

OMS

49367

IIOP

TCP

nwi3-

NWI3 Measurement

measurement-

Handler

hndlr WebSphere

ephemeral3

OMS

49566

IIOP

TCP

nwi3-adapter

NWI3 Adapter

WebSphere

ephemeral3

OMS

49363

IIOP

TCP

nwi3-sw-agent

NWI3 SW Agent

WebSphere

ephemeral3

OMS

443

HTTPS

TCP

https

HTTPS

WebSphere

ephemeral3

OMS

80

HTTP

TCP

http

HTTP

WebSphere

ephemeral3

OMS

22

SSH

TCP

ssh

SSH

WebSphere

ephemeral3

OMS

23

TELNET

TCP

telnet

TELNET

WebSphere

Any

MRBTS

33400-33600 traceroute

UDP

udp-36400-33600 Used for displaying the route and measuring transit delays of

WebSphere

Any

MRBTS

7-8

ICMP

UDP

icmp

packet Test host reachability and measure the round-trip time for messages sent from host to destination

NodeMgr

Any

OMS

49568

IIOP

TCP

tcp-49568

OMS connection needed for EM Launch

NodeMgr

any

OMS

636

LDAPS

TCP

ldaps

Application Launcher launch

NodeMgr

any

OMS

49152-49999 IIOP

TCP

ne-

Ephemeral ports used

applauncher-

by OMS Application

oms

launcher internal applications, i.e. : Measurement management, Fault management.

NodeMgr

Any

OMS

80

HTTP

TCP

http

OMS HTTP Web

NodeMgr

Any

OMS

443

HTTPS

TCP

https

OMS HTTP Web

NodeMgr

Any

OMS

500

UDP

UDP

NodeMgr

Any

MRBTS

6000-6001

X-Window

TCP

IPsec IKE negotiation x-window

For btssitemanager launch

NodeMgr

Any

MRBTS

443

HTTPS

TCP

https

Secured HTTP collection to MRBTS

NodeMgr

Any

MRBTS

12000

IIOP

TCP

entextxid

SEM-FTM connection

ALL_NE

ephemeral3

LB WAS virtual IP

636

LDAPS

TCP

ldap

This port needs to be open for any NE that is being configured for CNUM.

Issue: 1-2

DN09118114

51



Source

Source Port

Dest.

Dest. Port

AL1

TL2

Service Object

Description

ALL_NE

ephemeral3

LB WAS virtual IP

389

LDAP

TCP

ldap

LDAP port used by any NE that is configured for CNUM.

ALL_NE

Any

DNS and LDAP

22

SSH

TCP

ssh

SSH Daemon used for NE to NetAct communications

ALL_NE

Any

DNS and LDAP

53

DNS

TCP/UDP

dns

DNS Server used for NE to NetAct communications

LB WAS virtual IP

Any

OMS

80

HTTP

TCP

http

HTTP

LB WAS virtual IP

Any

OMS

443

HTTPS

TCP

https

HTTPS

SBI-

ephemeral3

OMS

443

HTTP/S

TCP

https

CM NWI3 data file

CommonMediation SBI-

transfer ephemeral3

OMS

80

HTTP

TCP

http

CommonMediation

CM NWI3 data file transfer

Table 16: Firewall rules for Flexi Multiradio BTS LTE 1

Application Layer

2

Transport Layer

3

If the source port is ephemeral, select a port from the NetAct port pool of the IP stack. To determine

which range of ports can be used, contact your system administrator. Node object name

Description

OMS

Host address of OMS North Bound Interface for LTE

MRBTS

Host address of Base Transceiver Station (BTS) for LTE

SBI-CommonMediation

Virtual address of the node where the common_mediations service is running in NetAct

NWI3

Virtual address of the node where the NWI3 service is running in NetAct

NodeMgr

Virtual address of the Node Manager Server in NetAct

WebSphere, WAS VM

Virtual address of the node where the WAS service is running in NetAct

DNS and LDAP

Virtual address of the node where DNS and LDAP dirsrv services are running in NetAct

LB WAS virtual IP

Virtual IP address of the WAS load balancer component

ALL_NE

All NE types

Table 17: Node descriptions

Issue: 1-2

DN09118114

52



2.4.2 Routing configuration If network elements are integrated to NetAct through the DCN backbone, ensure that the related configuration has been done correctly in the intermediate system (for example, routers and switches).

2.4.3 Network Time Protocol configuration If an external Network Time Protocol (NTP) server is used, ensure that the NTP service is started up and that the IP address of the NTP server is known.

2.5 Adding Flexi Multiradio BTS LTE and LTE iOMS to DNS in NetAct The Domain Name System (DNS) is a distributed database containing naming information of network elements. DNS converts host names into IP addresses and IP addresses into host names. Before integrating the network element to NetAct, you need to add the IP address and host name of the element to the DNS zone using BIND.

2.5.1 Checking the name server status 1. Log in to a VM hosting a DNS-Master or a DNS-Slave service as omc user, and switch to the root user. 2. To check the DNS server status, choose one of the following methods:

• As a

root user, enter:

[root]# service named status Expected outcome An output like the one below appears. WARNING: key file (/etc/rndc.key) exists, but using default configuration file (/etc/rndc.conf) version: 9.8.2rc1-RedHat-9.8.2-0.17.rc1.el6_4.5 CPUs found: 1 worker threads: 1 number of zones: 22 debug level: 0 xfers running: 0 xfers deferred: 0 soa queries in progress: 0 query logging is OFF recursive clients: 0/0/1000 tcp clients: 0/100 server is up and running

Issue: 1-2

DN09118114

53


named (pid

• As a


12345) is running...

root user using the smanager.pl command, enter:

[root]# smanager.pl status service DNS Expected outcome An output like the one below appears. DNS-Master:node01:started DNS-Slave:node02:started dns-namesurfer:node25:started

• As an

omc user, enter the following command:

[username@hostname]$ /opt/cpf/sbin/netact_status.sh status Expected outcome The outcome displays a list of the active service names and virtual machines. Executing NetAct cluster status script Status of NetAct Node Service custvm10 netfs-custvm10 ftp-custvm10 omagentaf-custvm10 osi pingserver-custvm10 tnameserver-custvm10 DNS-Master

Status started started started started started started started

custvm11 netfs-custvm11 omagentaf-custvm11 lb-unify-primary DNS-Slave socks

started started started started started

2.5.2 Configuring the DNS in NetAct Prerequisites The following information must be available:

• host name • IP address • DNS domain name

Issue: 1-2

DN09118114

54



• zone file name • reverse zone domain name • reverse zone file name Note:

• You can define the domain name structure and host names of Flexi Multiradio BTS LTE or Flexi Multiradio BTS LTE management interfaces, but ensure that these values are in line with the DNS specifications.

• To make zone file management easy, it is recommended that you consider the zone management as part of IP-network planning - how many zones are needed and how many entries are inserted into one zone. You must have the following information available: Based on the DNS domain of Flexi Multiradio BTS LTE, you need to perform the following: 1. If the network element is in the same domain as NetAct , then configure a zone and reverse zones in the NetAct DNS for the network element. 2. If the network element is in a different domain than NetAct, then you must decide whether the NetAct DNS is configured as a master or a slave for the network element's domain. If the NetAct DNS is configured as the master, then you need to create a zone file. If the NetAct DNS is configured as a slave, then you must configure the domain to point to the DNS of the separate domain. For instructions on DNS configuration, refer to Administering the DNS in NetAct.

2.5.3 Verifying the availability of a zone 1. Log in to the VM hosting a DNS service, and switch to the omc user. 2. To check that the zone is available, enter: [omc]$ dig @ soa +noall +answer where is the IP address of the VM where DNS-Master or DNS-Slave service is running, and is the domain name configured in the zone file. Below is an example output of the command: ;; <<>> DiG 9.8.2rc1-RedHat-9.8.2-0.10.rc1.el6_3.6 <<>> @192.0.2.2 netact.example.com soa +noall +answer ; (1 server found) ;; global options: +cmd netact.example.com. 3600 IN SOA ns1.netact.example.com. root.ns1.netact.example.com. 2013031801 28800 1200 604800 3600

Issue: 1-2

DN09118114

55



2.6 Other configurations 2.6.1 Configuring SOCKS proxy service If you want to launch the applications in NetAct from a workstation, you need to configure the SOCKS proxy service in NetAct as a prerequisite. For more information on how to configure the SOCKS proxy service, see Administering the SOCKS proxy.

2.6.1.1 Checking the status of SOCKS proxy service

1. Using an SSH client, log in to any NetAct node as omc user. 2. To check status of the SOCKS proxy service, enter the following command: [omc]$ /opt/cpf/sbin/netact_status.sh status service socks Expected outcome An output like the one below appears: Executing NetAct cluster status script socks::started

2.6.2 Adding the trusted sites Before enabling SSO function on NetAct, you need to add the IP address of the network element as Trusted sites of Internet browser. This section takes Internet Explorer as an example. 1. On the menu bar of Internet Explorer, select Tools → Internet Options. 2. On the opened dialog, click Security and select Trusted sites as the zone. 3. Click Sites. Expected outcome The Trusted sites dialog opens.

4. In Add this website to the zone, fill in https:// or http:// based on the network element version and click Add. 5. Click Close. 6. Click OK.

Issue: 1-2

DN09118114

56


Integrating Flexi Multiradio BTS LTE to NetAct manually

3 Integrating Flexi Multiradio BTS LTE to NetAct manually

3.1 Checking and creating the root object in NetAct Before NetAct can receive and store network element data, ensure that the managed objects are created under one root object for the network elements in NetAct Monitor.Ensure that the required root object is in NetAct. If it is not, then create the root object. Note: The root object for Flexi Multiradio BTS LTE has the distinguished name PLMN-PLMN and the instance ID PLMN. 1. Log in to NetAct Start Page as the integration user. 2. In NetAct Start Page, click Monitoring → Monitor. 3. In Monitor, open the Object Explorer panel by selecting Tools → Managed Objects → Object Explorer. Expected outcome The Object Explorer panel appears in the left side of the Monitor window with the existing root object instances displayed in it. If the root object instance already exists, skip steps 4 to 6. 4. In the Objects panel, right-click a blank area and select New → Object.... 5. From the Object Class drop-down list, select PLMN(PLMN) and click Next. 6. In the Instance field, fill in the instance ID and click Finish.

Issue: 1-2

DN09118114

57



Figure 4: Creating the PLMN-PLMN root object

Expected outcome The PLMN-PLMN root object is created and shown in the Objects panel. The default Object State for the created root object is Operational in the Properties panel. To open the Properties panel, right-click the PLMN-PLMN root object and select Properties.

3.2 Checking and creating maintenance region A NetAct Maintenance Region (MR) is used to maintain a group of network elements which share the credentials for accessing the network element. Consider your network layout and the location of Flexi Multiradio BTS LTE in the network layout. Based on the location, place the Flexi Multiradio BTS LTE network element in an existing MR. Create a new MR if there is none representing the new area. For instructions on checking or creating maintenance region, refer to Creating Maintenance Region.

3.3 Creating service users required for LTE iOMS Integration To connect and integrate Flexi Multiradio BTS LTE to NetAct and then manage Flexi Multiradio BTS LTE using NetAct tools, a number of mandatory service users have to be created in NetAct. At the same time, the corresponding service users have to exist in Flexi Multiradio BTS LTE. The credentials of the service user in NetAct must match the credentials of the service user on the network element.

Issue: 1-2

DN09118114

58



You can manage network element credentials (create and modify service users) with Network Element Access Control. The following table lists the service users needed during the Flexi Multiradio BTS LTE integration to NetAct. Username Interface

Service type

Profile

type

NWI3 Access

NWI3

Service user's username example

Default

Nemuadmin

and password dependencies

Connected to

Needed for

Application Group

You can define

End-user group which

HW Manager and

any username and

needs an access

connection between

password, but an

to NE (sysop,

NetAct and NE.

identical username

cmauto, and cmwsapi)

Application group

and password must

cmwsapi is part of

exist in every LTE

HW Manager feature

iOMS in the same

in NetAct8 and next

MR.

releases. Application group cmauto is part of "autoconnection and autoconfiguration" and "Intelligent configuration synchronization for LTE" features in NetAct 8 EP1 and next releases.

EM Access

EM

Default

The username can

Nemuadmin Note that Nemuadmin

be freely selected,

sysop

Connection between NetAct and LTE

is the default user and but a matching user must exist in GUI and may have changed during provisioning.

the user in GUI must belong to the domain Adminstrator`s group.

Table 18: Service users required for LTE integration Service users required for Flexi Multiradio BTS LTE integration and management have to be granted to the sysop user group, so that the system administrator can verify the integration (for example FM and PM data flow). Once the Flexi Multiradio BTS LTE has been integrated and verified, other user groups which need access to the Flexi Multiradio BTS LTE have to be connected to required service users as well. To create service users using Network Element Access Control: 1. Log in to the NetAct Start Page as user with Network Element Access Control permission, for example, as user of system administrator group sysop. 2. Select Security → Network Element Access Control.

Issue: 1-2

DN09118114

59



Expected outcome The Network Element Access Control application opens.

3. Create the required service users given in Service users required for LTE integration. a) Click the New button. b) Select the desired Service Type, and specify mandatory service user properties (profile, username, password, network element type or maintenance region). c) Click Save. Repeat step 3 for all mandatory service users. Note: NWI3 access is needed only on LTE iOMS so the NWI3 account must be manually created on LTE iOMS only, and not in Flexi Multiradio BTS LTE. On the other hand, EM access is supported on LTE iOMS and LNBTS so the account must be created on LTE iOMS and LNBTS. Ensure that the accounts have the same user ID and password, which are defined in Network Element Access Control.

Issue: 1-2

DN09118114

60



Figure 5: Example for Creating new Service user in Network Element Access Control

To assign service users to user group: 1. Select the service type, and then click Grant/Revoke. 2. Select sysop, cmauto, and cmwsapi in the Application Group section, and then click Save. Note:

• Grant the given service users to sysop, cmauto, and cmwsapi to enable the hardware change notifications between the network element and NetAct.

• Given service type must be granted to all MRs to which LNBTS are integrated. • Granting of this service type must be done for all end-user groups which must have access to a given MR and its associated LNBTS. Expected outcome: The name Several Groups appears under Group in the Credentials tab. To view the list of groups to which the service user belongs, click Several Groups.

Issue: 1-2

DN09118114

61



3.4 Creating managed objects for LTE iOMS in NetAct Before NetAct can receive and store network element data, use NetAct Monitor to create the managed objects for the network element. For Flexi Multiradio BTS LTE, create the managed objects under PLMN root object. Under the network element managed object, create the interface objects. You must create the following objects manually in NetAct: |-PLMN-PLMN |-OMS- |-HTTP-1

3.4.1 Creating LTE iOMS managed object 1. Log in to NetAct Start Page as integration user. 2. In NetAct Start Page, click Monitoring → Monitor. 3. In Monitor, open Object Explorer by selecting Tools → Managed Objects → Object Explorer. 4. Right-click the PLMN-PLMN object and select New → Object… …. 5. In the New Object dialog, from the Object Class drop-down list select OMS, select Assign as self agent and then click Next.

Figure 6: Example of new object configuration

Issue: 1-2

DN09118114

62



Note:

• The default value for Agent Direct Integration to this NetAct is true. • If Assign as self agent is not selected in this step, the managed object can be associated after it is created. To do this, right-click the object, select Agent Association, and then select the managed object.

6. In the Fill Mandatory Values dialog, enter the LTE iOMS instance ID, select the version for the object and click Finish.

Figure 7: Example of LTE iOMS object configuration

Note:

• The LTE iOMS instance ID must be an exact match of what is set in the network element. For information on the instance number of LTE iOMS, contact your network administrator.

• The value for Version is the appropriate LTE iOMS element version.

3.4.2 Creating the HTTP interface object 1. Log in to NetAct Start Page as omc user. 2. Select Monitoring → Monitor. 3. In the Objects pane, right-click the LTE iOMS object, and then select New → Object.

Issue: 1-2

DN09118114

63



Figure 8: Example of HTTP object creation

4. In the Object Class drop-down menu of the New Object dialog, select HTTP(HTTP) → Next. Expected outcome Note: Select HTTP(HTTP) only. Other objects, including NWI3, will be created automatically during integration data upload.

5. Enter the appropriate instance number and the northbound LTE iOMS IP address or Fully Qualified Domain Name (FQDN) in the Host name field, and then click Finish.

Issue: 1-2

DN09118114

64



Figure 9: Example of HTTP object creation

Note:

• Enter 1 as the instance number. • The Security Mode must be HTTPS.

3.5 Associating maintenance region with LTE iOMS 1. Log in to NetAct Start Page as omc user. 2. Select Monitoring → Monitor. Expected outcome The NetAct Monitor application window opens. 3. To start Object Explorer, select Tools → Managed Objects → Object Explorer. 4. In the Objects pane, right-click the managed object (OMS) that you want to associate with the maintenance region, and select Maintenance Region Association. 5. From the list of available maintenance regions, select the preferred one, and then click OK.

Issue: 1-2

DN09118114

65



Expected outcome The selected maintenance region is associated with the managed object.

3.6 Executing integration data upload Note: For instructions on how to troubleshoot integration data upload, refer to Integration data upload fails. 1. Log in to NetAct Start Page as omc user. 2. Select Monitoring → Monitor. Expected outcome The NetAct Monitor application window opens. 3. To start Object Explorer, select Tools → Managed Objects → Object Explorer. 4. Right-click OMS object, and then select Element Management → Integration Data Upload.

Figure 10: Starting integration data upload for OMS

5. To verify Integration Data Upload, refer to Verifying Integration Data Upload.

3.7 Associating maintenance region with MRBTS and LNBTS There are two ways to associate the Maintenance Region with MRBTS and LNBTS:

• Manual association using NetAct Monitor • Automatic association using the MR association Tool

Issue: 1-2

DN09118114

66



3.7.1 Manual association using NetAct Monitor 1. Log in to NetAct Start Page as omc user. 2. Select Monitoring → Monitor. Expected outcome The NetAct Monitor application window opens.

3. To start Object Explorer, select Tools → Managed Objects → Object Explorer. 4. In the Objects pane, expand the PLMN object, right-click the MRBTS that you want to associate with the maintenance region, and select Maintenance Region Association. 5. In the Associate Maintenance Region dialog, select the Maintenance Region to which you want to associate the MRBTS object. Note:

• To associate the child LNBTS objects, select the Propagate selected Maintenance Region to the sub tree checkbox.

• To deselect the Maintenance Region, select the No Maintenance Region Selected checkbox.

• To disassociate the MRBTS and child LNBTS objects, select the Propagate selected Maintenance Region to the sub tree and No Maintenance Regions selected checkboxes.

• The Confirm Maintenance Region Propagation dialog appears whenever Propagate selected Maintenance Region to the sub tree is selected or cleared. To confirm selection, click Yes.

6. Click OK. Expected outcome The selected maintenance region is associated with MRBTS and LNBTS. 7. To verify if the manual association procedure succeeded, right-click the Maintenance Region and select Show Associated Objects. Expected outcome The Object List window displays the managed objects associated with the Maintenance Region. By default, the following information is available:

• Distinguished Name • Instance

Issue: 1-2

DN09118114

67



• Adaptation ID • Release Note: The Show Associated Objects option is disabled if:

• multiple Maintenance Regions are selected. • objects other than the Maintenance Region are selected. For more information, refer to Associating a managed object to Maintenance Region.

3.7.2 Automatic association using Integration Data Upload After Integration Data Upload, the MRBTS and LNBTS objects, which are mediated by this OMS and still not yet associated with any Maintenance Region, will be automatically associated with the Maintenance Region that the LTE iOMS has. This information can be identified in the Show Log window of the Integration Data Upload operation on Monitor.

Figure 11: Integration Data Upload logs

Note: Real Time update of MR association in Monitor is not supported.

3.7.3 Automatic association using the MR association Tool This script automatically associates the Maintenance Region with all the NASDA Managed Objects (MO) it mediates, that is, MOs that have agent relationships with the mediator. This tool can be used after migration and Integration Data Upload, and can only be executed by an omc user.

Issue: 1-2

DN09118114

68



Note: If an object is already associated with the Maintenance Region, the script/tool will ignore it. The tool will only associate objects that are not yet associated with the Maintenance Region. 1. Log in to the node where NWI3 service is running as omc user. 2. To start the script, enter the following command: [omc]$ python /opt/oss/NSN-nwi3/bin/mrAssociation.zip -a Note: refers to the distinguished Fully Qualified Domain Name (FQDN) of the agent object, such as PLMN-PLMN/OMS-1234. Expected outcome An output like the one below appears: INFO | Starting MR association for all the objects that mediates INFO | MR of agent is MRC-/MR- INFO | 4 object(s) are mediated by INFO | 1 object(s) already have MR, ignore them INFO | 3 object(s) have no MR, associating them to MRC-/MR INFO | MR association succeeded for 3 object(s), failed for 0 object(s) INFO | MR association finished. Details info see: /var/opt/oss/log/nwi3/mr_association_result.log.2014-05-04_12:34:32

3. Log out from the node. Note: If the Properties panel was opened before the script/tool was executed, the Maintenance Region information will not be immediately visible in Monitor. To view changes to the Maintenance Region, re-open Monitor.

3.8 Provisioning Flexi Multiradio BTS LTE credentials in Network Element Access Control You can manage network element credentials with Network Element Access Control (NEAC) application. This application allows you to manage and administer the service users of a network element.

Issue: 1-2

DN09118114

69



Provisioning is supported only for the service user for the Maintenance Region created in Network Element Access Control (NEAC). Ensure that the network element objects are associated to the maintenance region before provisioning. Do this only if user and password is intended to be provisioned to Network Element. Note: Provisioning is supported only for LNBTS objects.

Provisioning NE Type LNBTS

Provisioning Service

Authentication NE

Authentication

Type

Type

Service Type

EM Access

OMS

NWI3 Access

Table 19: Required service types for provisioning For information on how to create the service type, see Creating service users required for Flexi Multiradio BTS LTE Integration. 1. Log in to NetAct Start Page as the integration user. 2. Click Security → Network Element Access Control. 3. Click the Provisioning tab. 4. In the Provisioning tab, select the following created Maintenance Region credentials and click Provision.

• EM Access

Figure 12: Provisioning tab

Expected outcome If completed appears in the Status column, then the credentials are provisioned to the network element in the Maintenance Region.

Issue: 1-2

DN09118114

70



3.9 Collecting SSH public keys 3.9.1 Collecting the SSH public keys of LTE iOMS in NetAct Note: The network administrator must keep the public host keys up-to-date in the user's home directories. 1. Log in to the NetAct virtual machine (VM) where the nwi3 service is running as the root user. To locate the correct VM, see Checking NetAct addresses in Prerequisites for NetAct 2. To gather SSH public keys, enter the following command: /opt/oss/bin/gather_ssh_public_keys.pl -e OMS Expected outcome An output like the one below appears: Querying 'OMS' addresses from NASDA DB: 3 addresses found! Gathering rsa ssh public keys: -----------------------------------------------------------# 10.0.1.1 SSH-2.0-OpenSSH_4.3 # 10.0.1.2 SSH-2.0-OpenSSH_4.3 # 10.0.1.3 SSH-2.0-OpenSSH_4.3 -----------------------------------------------------------A new ssh known hosts file generated: 'known_hosts.new' As a result, the known_hosts.new file is generated in your home directory. The file contains the public keys of all the network element types for which the gather_ssh_public_keys.pl script was run, in that case, of the LTE iOMS.

3. Verify that each collected public host key in the known_hosts.new file matches the public host key of the LTE iOMS. If a public host key does not match the key in the network element, then a man-in-the-middle attack might be taking place. 4. Make a backup copy of the $CPF_CERT_PATH/smx/nwi3/known_hosts. 5. Copy the gathered public host keys from the known_hosts.new file to the end of the $CPF_CERT_PATH/smx/nwi3/known_hosts with the following command: cat known_hosts.new >> $CPF_CERT_PATH/smx/nwi3/known_hosts 6. To log out of the node, enter logout

Issue: 1-2

DN09118114

71



3.9.2 Collecting the SSH public keys of the Flexi Multiradio BTS LTE in NetAct Note: The network administrator must keep the public host keys up-to-date in the user's home directories. 1. Log in to the NetAct virtual machine (VM) where the nwi3 service is running as the root user. To locate the correct VM, see Checking NetAct addresses in Prerequisites for NetAct 2. To gather SSH public keys, enter the following command: /opt/oss/bin/gather_ssh_public_keys.pl -e MRBTS Expected outcome An output like the one below appears: Querying 'MRBTS' addresses from NASDA DB: 3 addresses found! Gathering rsa ssh public keys: -----------------------------------------------------------# 10.0.1.1 SSH-2.0-OpenSSH_5.8 # 10.0.1.2 SSH-2.0-OpenSSH_5.8 # 10.0.1.3 SSH-2.0-OpenSSH_5.8 -----------------------------------------------------------A new ssh known hosts file generated: 'known_hosts.new' As a result, the known_hosts.new file is generated in your home directory. The file contains the public keys of all the network element types for which the gather_ssh_public_keys.pl script was run, in that case, of the MRBTS.

3. Verify that each collected public host key in the known_hosts.new file matches the public host key of the MRBTS. If a public host key does not match the key in the network element, then a man-in-the-middle attack might be taking place. 4. Make a backup copy of the $CPF_CERT_PATH/smx/nwi3/known_hosts. 5. Copy the gathered public host keys from the known_hosts.new file to the end of the $CPF_CERT_PATH/smx/nwi3/known_hosts with the following command: cat known_hosts.new >> $CPF_CERT_PATH/smx/nwi3/known_hosts 6. To log out of the node, enter logout

Issue: 1-2

DN09118114

72



3.10 Executing CM upload Note: For optimal database performance, it is recommended to execute the statistics gathering from 30 minutes to 1 hour after triggering the initial CM Upload. To do so, run the following command: /opt/oss/NSN-doctor/bin/doctormx.sh -case --run D3BOracleStatisticsGathering For more information on how to gather statistics, refer to NetAct Doctor usage and available maintenance cases. To verify Configurator data flow: 1. Log in to the NetAct virtual machine where the WAS service is running as the integration user. 2. On the NetAct Start Page, open CM Operations Manager by selecting Configuration → CM Operations Manager. Expected outcome The CM Operations Manager application window opens. 3. Select Upload → New Upload. Expected outcome The Upload dialog opens.

4. In the Upload dialog, click the LTE tab, and then select the MRBTS object that you want to upload.

Issue: 1-2

DN09118114

73



Figure 13: Example of LTE Upload

5. Enter a name of the upload operation and select the level of information. 6. To start the upload, click Start. 7. In the confirmation dialog, click Yes. Expected outcome The upload operations starts. The operation is done if Upload: Finished appears in the upper left corner of the dialog.

3.11 Executing Alarm Upload Prerequisites Before doing this task, ensure that you have successfully integrated the network element to NetAct. 1. Log in to NetAct Start Page as omc user. 2. Select Monitoring → Monitor.

Issue: 1-2

DN09118114

74



Expected outcome The NetAct Monitor application window opens. 3. Select Tools → Managed Objects → Object Explorer. 4. Right-click the OMS object and click Alarm Upload.

Figure 14: Executing Alarm Upload

Expected outcome The alarms are uploaded to NetAct and are displayed in the Alarm List of NetAct Monitor.

Issue: 1-2

DN09118114

75


Integrating Flexi Multiradio BTS LTE to NetAct with NE Integration Wizard

4 Integrating Flexi Multiradio BTS LTE to NetAct with NE Integration Wizard Automated integration is supported for integrating Flexi Multiradio BTS LTE to NetAct by using NE Integration Wizard (NEIW). For other releases, go to Integrating Flexi Multiradio BTS LTE to NetAct manually. For more information on which Flexi Multiradio BTS LTE releases support automated integration, see Supported network element versions, management functions and used southbound interfaces.

4.1 Integration operations in NEIW 1. Log in to NetAct Start Page as the integration user. 2. In NetAct Start Page, click Administration → NE Integration Wizard. Expected outcome The NE Integration Wizard application runs. 3. Click New. Expected outcome The NE Configuration window opens. 4. In NE type and Adaptation release, select OMS and its version from the drop-down lists. Expected outcome Corresponding attributes are displayed.

5. Fill in the mandatory values. Attribute

Value

MR

The MR FQDN used for integration, for example, MRC-1/MR-1

OMS O&M agent address

The fully qualified domain name (FQDN) or IP address of the OMS O&M Agent

NEUM admin user name

The user name used to log in to OMS. This is the user created in Creating service users required for LTE iOMS integration

NEUM admin password

The password used to log in along with the NEUM admin user name

Issue: 1-2

DN09118114

76


Integrating Flexi Multiradio BTS LTE to NetAct with NE Integration Wizard

Attribute

Value

Confirm NEUM admin password

The password used to log in along with the NEUM admin user name

NEUM admin root password

The password used to log in as root in OMS

Confirm NEUM admin root

The password used to log in as root in OMS

password OMS FQDN

The distinguished name of OMS, for example, PLMN-PLMN/ OMS-123

Table 20: Configuration parameters for Flexi Multiradio BTS LTE

6. Click Save. Expected outcome The NE Configuration window is closed. The integration plan is created and shown in the list. 7. Select the added plan and click Integrate. Note: If multiple plans are triggered, the network elements are integrated one by one. So for those network elements whose integration is in queue, the Integration status shows In queue. Expected outcome After the integration, in Integration status, the status changes to Completed. If the integration fails, in Integration status, click Failed to check the log and see the troubleshooting section.

8. Perform the CM upload procedure.

Issue: 1-2

DN09118114

77


Verifying the integration

5 Verifying the integration

5.1 Verifying Integration Data Upload Before performing this task, ensure that you have successfully integrated the network element to NetAct. For more information, see Executing integration data upload. 1. Log in to NetAct Start Page as omc user. 2. Select Monitoring → Monitor. Expected outcome NetAct Monitor application window opens. 3. To start Object Explorer, select Tools → Managed Objects → Object Explorer. Expected outcome

• PLMN-PLMN is visible in the Objects pane. • MRBTS and LTE iOMS are visible under PLMN-PLMN. • EM-1 and LNBTS are visible under MRBTS, with EM-1 as the child object of LNBTS. • EM-1, HTTP-1, and NWI3-1 appear under the LTE iOMS object.

Figure 15: Objects pane

Issue: 1-2

DN09118114

78



5.2 Verifying alarm upload Prerequisites Before doing this task, ensure that you have successfully executed Alarm upload. For more information, see Executing Alarm Upload. 1. Log in to NetAct Start Page as omc user. 2. Select Monitoring → Monitor. Expected outcome The NetAct Monitor application window opens. 3. Select Tools → Monitoring Desktop → Alarm List. Expected outcome All LTE iOMS and eNodeB alarms are displayed in the Alarm List.

Figure 16: Alarm List

5.3 Verifying CM upload 5.3.1 Verifying in NetAct Monitor 1. Log in to NetAct Start Page as omc user. 2. Select Monitoring → Monitor. Expected outcome The NetAct Monitor application window opens. 3. To start Object Explorer, select Tools → Managed Objects → Object Explorer.

Issue: 1-2

DN09118114

79



Expected outcome FTM and LNCELs are displayed as child objects of LNBTS.

Figure 17: Child object hierarchy

4. Check the icons of each object:

• MRBTS • LNBTS • FTM • LNCELs Expected outcome NetAct monitor displays the correct icons. The table below shows the possible icons in NetAct monitor. LN4.0, LN5.0, LNT3.0,

Issue: 1-2

LTO4.0, LTO5.0, LTO6.0,

LNT3.1, LN6.0, LNT4.0,

LTO7.0, LTO15A

LN7.0, LNT5.0, FL15A, TL15A

DN09118114

LNFZ5.0, LNF7.0, LNZ5.0

80


LTO4.0, LTO5.0, LTO6.0, LTO7.0, LTO15A


LN4.0, LN5.0, LNT3.0, LNT3.1, LN6.0, LNT4.0,

LNFZ5.0, LNF7.0, LNZ5.0

LN7.0, LNT5.0, FL15A, TL15A

Table 21: NetAct Monitor icons

5.3.2 Verifying in CM Editor 1. Log in to NetAct Start Page as omc user. 2. Select Configurator → CM Editor. Expected outcome The NetAct CM Editor application window opens. 3. Select All Parameters View from the drop-down list. 4. Expand Actual Configuration and check if all LTE managed objects are present. You may use the Object Information Browser to get the list of LTE managed objects. Expected outcome If the MRBTS, LNBTS, and child object hierarchy are visible under Actual Configuration, then the configuration management data flow from LTE iOMS and Flexi Multiradio BTS LTE to NetAct for the newly integrated network element is verified.

Issue: 1-2

DN09118114

81



Figure 18: Child object hierarchy under Actual Configuration

5.4 Verifying element management connectivity Before launching Element Manager, ensure that the related NEAC Service User has been created.

5.4.1 Verifying LTE iOMS EM Launch through NetAct Monitor Ensure that the following are installed and configured correctly:

• Node Manager Server. For more information, refer to Installing Node Managers and related software.

• Application Launcher. For more information, refer to Installing Application Launcher in Node Manager Server. 1. Log in to the NetAct Start Page as omc user. 2. Select Monitoring → Monitor.

Issue: 1-2

DN09118114

82



Expected outcome The NetAct Monitor application window opens. 3. Select Tools → Managed Objects → Object Explorer and then expand the PLMN-PLMN object. 4. Right-click the LTE iOMS object representing the target NE, and select Element Management → Element Manager → OMS EM. Expected outcome The Application Launcher window opens. Note: If the Parameter Tool is not visible in the Application Launcher, follow the procedure under the LTE iOMS Parameter Tool entry in the Preparation checklist for LTE iOMS table to make the Parameter Tool visible.

5. Right-click the LTE iOMS object representing the target NE, and select Element Management → Element Manager → OMS GUI EM. Expected outcome The LTE iOMS Element Manager webpage window opens.

5.4.2 Verifying LTE BTS Site Manager EM launch through NetAct Monitor 1. Log in to the NetAct Start Page as omc user. 2. Select Monitoring → Monitor. Expected outcome The NetAct Monitor application window opens. 3. Right-click the LNBTS object representing eNodeB target, and select Element Management → Element Manager. Note: Element Manager can also be launched from MRBTS, FTM, or LNCEL objects.

Expected outcome The site manager launches.

Issue: 1-2

DN09118114

83



Figure 19: Site Manager window

5.5 Verifying fault management connectivity This section provides information on how to check if alarms are received and properly displayed in NetAct Monitoring Desktop. 1. Log in to the integrated LTE iOMS element as Nemuadmin user. 2. Raise the test alarm by entering the following command: flexalarm --raise --sp=70255 --ap=/WAS/FSAlarmDBServer/ SolidWDforAlarmType --mo=/WAS/FSAlarmDBServer/SolidWDforAlarmType --se=3 Expected outcome The generated LTE iOMS test alarm appears in the NetAct Monitor Alarm list. To view this, open NetAct Monitor and then select Tools → Monitoring Desktop → Alarm List.

3. Cancel the test alarm by entering: flexalarm --clear --sp=70255 --ap=/WAS/FSAlarmDBServer/ SolidWDforAlarmType --mo=/WAS/FSAlarmDBServer/SolidWDforAlarmType --se=3

Issue: 1-2

DN09118114

84



Expected outcome The generated LTE iOMS test alarm is not in the NetAct Monitor Alarm list.

5.6 Verifying performance management connectivity This section describes the tasks that you need to perform to verify that the performance management data is arriving from the Flexi Multiradio BTS LTE to NetAct. There are two ways to verify performance management data flow:

• checking database • using NetAct Performance Manager 5.6.1 Verifying performance management data flow by checking database Note: Raw PM data might take some time to arrive in NetAct DB after integration. This operation is only valid when you integrate Flexi Multiradio BTS LTE to NetAct for the first time. For the integration of other network elements after the initial integration, you can skip the steps below. 1. Log in to the NetAct VM on which the rep service is running as the omc user. 2. Verify that performance management data is inserted to database by entering the following command: [omc]$ etlcolDBInfo.pl -t NOKLTE%RAW Expected outcome The screen displays the raw measurement table. ======================================================================= CONNECTING TO DATABASE ======================================================================= Get connection to database ... ok ----------------------------------------------------------------------NOKLTE%RAW - Checking database tables NOKLTE%RAW% --------------------------------------------------------------------------------------------------------------------------------------- Number of rows in NOKLTE%RAW measurement tables Yesterday Today Last entry Name of the table ----------------------------------------------------------------NOKLTE_PS_LCELAV_MNC1_RAW 1014 1478 2014/07/21 05:45:00 NOKLTE_PS_LCELLD_MNC1_RAW 383 560 2014/07/21 04:45:00 NOKLTE_PS_LCELLR_MNC1_RAW 383 560 2014/07/21 04:45:00

Issue: 1-2

DN09118114

85


NOKLTE_PS_LCELLT_MNC1_RAW NOKLTE_PS_LENBLD_LNBTS_RAW NOKLTE_PS_LEPSB_MNC1_RAW NOKLTE_PS_LETHIF_IEIF_RAW NOKLTE_PS_LETHL_ETHLK_RAW NOKLTE_PS_LHOBC_HBC1_RAW NOKLTE_PS_LHORLF_MNC1_RAW NOKLTE_PS_LHO_MNC1_RAW NOKLTE_PS_LIANBHO_MNC1_RAW NOKLTE_PS_LIENBHO_MNC1_RAW NOKLTE_PS_LIPF_IPRM_RAW NOKLTE_PS_LIPSEC_IPSECC_RAW NOKLTE_PS_LIP_IPPM_RAW NOKLTE_PS_LISHOG_DMNC3_RAW NOKLTE_PS_LISHOU_DMNC2_RAW NOKLTE_PS_LISHO_MNC1_RAW

Issue: 1-2


383 403 383 201 402 0 0 377 377 377 201 201 201 0 0 377

DN09118114

560 589 560 294 588 0 0 552 552 552 294 294 294 0 0 552

2014/07/21 2014/07/21 2014/07/21 2014/07/21 2014/07/21

04:45:00 05:45:00 04:45:00 05:45:00 05:45:00

2014/07/21 2014/07/21 2014/07/21 2014/07/21 2014/07/21 2014/07/21

04:45:00 04:45:00 04:45:00 05:45:00 05:45:00 05:45:00

2014/07/21 04:45:00

86



5.6.2 Checking measurements data on Performance Manager 1. Log in to the NetAct Start page as omc user. 2. Select Reporting → Performance Manager. 3. On the Performance Manager page, click Reporting Tools and then select Report Creator from the drop-down menu. 4. In the Object Selection area, select NSN Adaptation Support / LNBTS-NSN LTE Base Transceiver Station from the Technology pane. 5. In Hierarchy, select PLMN/MRBTS. 6. In the Object level, select MRBTS. 7. In the Object Filtering area, enter ** in the search box. 8. Select the instance number of the dedicated MRBTS that was integrated to NetAct. 9. Click Edit Time Selection. 10. In the Time Level pane, select RAW. 11. Select Relative as Time type. Specify the number of days and select Now in the Back from dropdown list. 12. Click Edit KPI/Counter Selection. 13. In the KPI/Counter Selection area, select Counters tab and the measurement from the drop-down list. For example, LS1AP. 14. Select less than 50 counters. Click Preview Report. Expected outcome The raw data for the measurement selected in Step 13 appears in the Preview area.

5.7 Verifying configuration management operation 1. Log in to NetAct Start Page as omc user. 2. Select Configuration → CM Editor.

Issue: 1-2

DN09118114

87



Expected outcome The CM Editor application window opens. 3. Select Target Configuration → Actual Configuration. 4. Expand the Actual Configuration node in the navigation tree. Expected outcome A list of root objects is shown. They are sorted alphabetically and in ascending order based on class and object instance.

5. Expand the PLMN-PLMN root object. Expected outcome Objects uploaded using the Integration Data Upload operation are visible.

6. Select the objects that you want to view. Expected outcome The Parameters by Actual Managed Object view opens. It shows the values for the actual managed objects in the network.

5.8 Verifying state management operation To perform a state management function, do any of the following:

• Change the administrative state of a network element to Lock. • Change the administrative state of a network element to Unlock. • Change the administrative state of a network element to Shutdown. • Reset the LNCEL or LNBTS. 5.8.1 Changing the administrative state of a network element to Lock To lock one or more LNCELs: 1. In NetAct Monitor, select Tools → Managed Objects → Object Explorer. 2. Select the LNCEL object or objects. 3. Right-click the selected objects, and then select Element Management → Lock LNCEL. Expected outcome

Issue: 1-2

DN09118114

88



The Confirmation Operation dialog appears. 4. To confirm state change operation, click Yes. Otherwise, click No. 5. In NetAct Monitor, select Tools → Properties. In the Properties panel, the Administrative state value under Configuration Management is set to Locked. To lock all LNCELs under LNBTS: 1. In NetAct Monitor, select Tools → Managed Objects → Object Explorer. 2. Select the LNBTS object. 3. Right-click the selected object, and then select Element Management → Administrative State Management → Lock LNCELs. Expected outcome The Confirmation Operation dialog appears. 4. To confirm state change operation, click Yes. Otherwise, click No. 5. In NetAct Monitor, select Tools → Properties. In the Configuration Management section of the Properties panel, the Administrative state value of all LNCELs is set to Locked. Note: The Lock LNCEL operation is not executed on objects with the initial Administrative state value of Locked.

5.8.2 Changing the administrative state of a network element to Unlock To unlock one or more LNCELs: 1. In NetAct Monitor, select Tools → Managed Objects → Object Explorer. 2. Select the LNCEL object or objects. 3. Right-click the selected objects, and then select Element Management → Unlock LNCEL. Expected outcome The Confirmation Operation dialog appears. 4. To confirm state change operation, click Yes. Otherwise, click No. 5. In NetAct Monitor, select Tools → Properties. In the Properties panel, the Administrative state value under Configuration Management is set to Unlocked. To unlock all LNCELs under LNBTS: 1. In NetAct Monitor, select Tools → Managed Objects → Object Explorer. 2. Select the LNBTS object. 3. Right-click the selected object, and then select Element Management → Administrative State Management → Unlock LNCELs.

Issue: 1-2

DN09118114

89



Expected outcome The Confirmation Operation dialog appears. 4. To confirm state change operation, click Yes. Otherwise, click No. 5. In NetAct Monitor, select Tools → Properties. In the Configuration Management section of the Properties panel, the Administrative state value of all LNCELs is set to Unlocked. Note: The Unlock LNCEL operation is not executed on objects with the initial Administrative state value of Unlocked.

5.8.3 Changing the administrative state of a network element to Shutdown To shut down one or more LNCELs: 1. In NetAct Monitor, select Tools → Managed Objects → Object Explorer. 2. Select the LNCEL object or objects. 3. Right-click the selected objects, and then select Element Management → Shutdown LNCEL. Expected outcome The Confirmation Operation dialog appears. 4. To confirm state change operation, click Yes. Otherwise, click No. 5. In NetAct Monitor, select Tools → Properties. In the Properties panel, the Administrative state value under Configuration Management is set to shutting down. The value changes to locked once the operation is completed. To shut down all LNCELs under LNBTS: 1. In NetAct Monitor, select Tools → Managed Objects → Object Explorer. 2. Select the LNBTS object. 3. Right-click the selected object, and then select Element Management → Administrative State Management → Shutdown LNCELs. Expected outcome The Confirmation Operation dialog appears. 4. To confirm state change operation, click Yes. Otherwise, click No. 5. In NetAct Monitor, select Tools → Properties. In the Configuration Management section of the Properties panel, the Administrative state value of all LNCELs is set to shutting down. The value changes to locked once the operation is completed. Note: If the Administrative state value of the object is set to Locked, the Shutdown LNCEL operation will fail.

Issue: 1-2

DN09118114

90



5.8.4 Resetting the LNCEL or LNBTS To reset LNCEL: 1. In NetAct Monitor, select Tools → Managed Objects → Object Explorer. 2. Select the LNCEL object or objects. 3. Right-click the selected objects, and then select Element Management → Reset LNCEL. Expected outcome The Confirmation Operation dialog appears. 4. To confirm state change operation, click Yes. Otherwise, click No. To reset LNBTS: 1. In NetAct Monitor, select Tools → Managed Objects → Object Explorer. 2. Select the LNBTS object. 3. Right-click the selected object, and then select Element Management → Reset LNBTS. Expected outcome The Confirmation Operation dialog appears. 4. To confirm state change operation, click Yes. Otherwise, click No. Note:

• If the state of an object does not change after executing any of the above operations (except Reset), it is recommended to use either of the following: - Reset LNBTS or Reset LNCEL. The Reset operation may take between 2-8 minutes to complete, depending on hardware performance. - Reset Site via BTS Site Manager application. Retry the failed operation once the Reset operation is completed.

• For more information, refer to State management operation fails under Troubleshooting integration problems.

Issue: 1-2

DN09118114

91


Other management functions for Flexi Multiradio BTS LTE

6 Other management functions for Flexi Multiradio BTS LTE After Flexi Multiradio BTS LTE is integrated to NetAct, basic network element management functions such as fault management and performance management are functional. For the operation instructions, see the specific instructions: Note: Do each kind of management function with minimum relevant user permission.

• For user management, see User Management Help. • For permission management, see Permission Management Help. • For configuration management or hardware management, see CM Editor Help and CM Operations Manager Help.

• For license management, see License Manager Help. • For software management, see Software Manager Help. • For performance management, see Performance Manager Help. • For administration of measurement, see Administration of Measurements Help.

6.1 Administering Centralized Network Element User Management The Centralized Network Element User Management (CNUM) feature enables network elements to authenticate and authorize users against the CNUM repository (LDAP) in NetAct. When using CNUM, users with sufficient access rights can log in to a network element with their own user account instead of using the local network element-specific user accounts. CNUM is also known as Centralized User Authentication and Authorization (CUAA) and Remote User Identification Management (RUIM). CNUM is based on user accounts that are created in the NetAct system using the User Management application and stored in the LDAP repository in NetAct. Access to network elements and allowed operations are controlled by permissions that are granted using the Permission Management application. For more information, refer to About Centralized Network Element User Management. Before LTE iOMS can be used with NetAct for CNUM, some configuration changes need to be applied. For the list of preconditions, refer to Network element specific requirements for LTE iOMS under Administering Users and Permissions. CNUM-supported network elements LTE iOMS

eNodeB

LTO6.0

Issue: 1-2

LNT3.0

DN09118114

92



LTE iOMS

eNodeB LNT3.1 LNT4.0 LN4.0 LN5.0 LN6.0 LNFZ5.0

LTO7.0

LNT3.0 LNT3.1 LNT4.0 LNT5.0 LN4.0 LN5.0 LN6.0 LN7.0 LNFZ5.0 LNF7.0 LNZ5.0

LTO15A

LNT3.0 LNT3.1 LNT4.0 LNT5.0 TL15A LN4.0 LN5.0 LN6.0 LN7.0 FL15A LNFZ5.0 LNF7.0 LNZ5.0

Table 22: Network element mapping

To use CNUM, the following conditions must be met:

• The network element must support CNUM feature. For a list of the CNUM-supported network elements, refer to Network element mapping.

Issue: 1-2

DN09118114

93



Note: Ensure that LTE iOMS software version R_GOMS6_1.xxxxx, or newer, is installed.

• The CNUM license (Centralized NE User Management for LTE, Feature Code 0000004670) must be installed in NetAct. For more information, refer to the following sections:

• To activate CNUM on Network Elements, see Activating Centralized Network Element User Management.

• To deactivate CNUM on Network Elements, see Deactivating Centralized Network Element User Management.

• To change the password of the accounts for CNUM on Network Elements, see Changing password of the network element accounts.

• For information on LTE iOMS commands, see LTE Radio Access Operating Documentation in the NSN online library. Open LTE Radio Access Operating Documentation and navigate to Checking functional correctness of OMS. Note that this document has several versions depending on the software release. As an example, you may refer to LTE Radio Access Documentation (DN0983101). Below are the supported LTE iOMS roles and permissions: Adaptation Permission Name Operation

Description

Action Log Error

This permission enables read access to Ready

Monitor

Support

ActionLogError. EMI, not used in OMS. Manage

This permission enables manage

Ready

access to ActionLogError. EMI, not used in OMS. Action Log

Monitor

Operation

This permission enables read access to Supported ActionLogOperation. EMI, not used in OMS.

Manage


Supported

access to ActionLogOperation. WebUI server-side service. Action Log

Monitor

Security

This permission enables read access

Ready

to ActionLogSecurity. EMI, not used in OMS server-side service. Manage


Ready

access to ActionLogSecurity. EMI, not used in OMS server-side service.

Issue: 1-2

DN09118114

94



Permission Name Operation

Description

Action Log Setting


Monitor

Adaptation Support Ready

to ActionLogSetting. EMI, not used in OMS server-side service. Manage


Ready

access to ActionLogSetting. EMI, not used in OMS server-side service. CM Plan

Monitor

Management

This permission enables read access to Ready CMPlanManagement. NWI3, not used in OMS server-side service.

Manage


Ready

access to CMPlanManagement. NWI3 and WebUI server-side service, not used in OMS. Diagnostics

Monitor

Management


Ready

to Diagnostics. EMI, not used in OMS server-side service. Manage


Ready

access to Diagnostics. EMI, not used in OMS server-side service. Fault Management

Monitor

This permission enables read access to Supported Fault Management.

Manage


Supported

access to Fault Management. fsui

Monitor

This permission is typically assigned

Supported

to an operator that monitors the network element, but does not take any management actions. This also includes access to log files (managed using ACL). Log

This permission is for files generated by Supported syslog.

Manage

This permission is typically used

Supported

for management actions such as attempting recovery, managing IP addresses, hardware, and licenses. This does not include access to

Issue: 1-2

DN09118114

95




Description

Adaptation Support

data stored in databases, backup functionality, or passwords stored in LDAP. This role is targeted for daily management functions, such as reacting to alarms. Root privileges are required for operations that cannot be performed using this group. Exceptions are log files (_nokfsuilog, _nokfsuiseclog), and backup (_nokfsuibackup). wheel

This permission allows a user to use

Supported

the su command to switch to the root account; it is used only for LDAP users. The normal wheel group (/etc/group) is used for accounts stored in /etc/ passwd. seclog

This permission is for files generated by syslog. Syslog only uses numeric IDs when creating the file so as not to depend on LDAP. Users should be assigned to this group when they need to read security log files. The syslog daemon creates files with this group owner and grants read access to this group. It is stored in /etc/passwd since it is required when starting syslog.

fsuicli

generalloginshell

This permission allows a CNUM user to Supported connect to OMS via SSH.

ownhomedir

This permission allows a CNUM user

Supported

to log in to the home directory (/home/ ) via SSH. hassharedreadonlyhomeThis permission allows a user to log in

Supported

to a read-only shared home directory (/ usr/bin) via SSH.

Issue: 1-2

DN09118114

96




Description

fsuiexternalldap

This permission is required for clients

login

Adaptation Support Supported

to access the LDAP server using the external LDAPS interface. fsuifault

man

This permission is required for Fault

Supported

Management. view

This permission is required for Fault

Supported

Monitoring. fsuilic

man

This permission is assigned to users

Supported

that need to manage the licensing of a FlexiServer-based network element. fsuiom

Manage

This permission allows access

Supported

to collect statistics and modify the performance management configuration and alarm system configuration, for example, alarm correlation. This permission is required for fsuiperformance

man

Performance Management.

Supported

This permission is required for view

Mmi Login

Monitor

Performance Monitoring.

Supported

This permission enables read access to Supported MMILogin.

Manage


Supported

access to MMILogin. OMS Common

Monitor

This OMSCommonmonitor permission

Supported

enables the user to launch the Active Sessions and Fault Management application. Manage

This OMSCommonmanage permission

Supported

enables the user to launch the Active Sessions and Fault Management application. OMS

Issue: 1-2

Monitor


Configuration

to OMS parameters using Parameter

Management

Viewer.

DN09118114

Supported

97




Description

Adaptation Support

Manage

This permission enables the user to

Supported

launch the Parameter Editor and allows the user to change values for certain parameters. Performance

Monitor

Management

This permission enables read access to Supported Performance Management operations.

Manage


Supported

access to Performance Management operations. pmg

Manage

This permission allows for read/write

Supported

access to all data in LDAP. Monitor

This permission allows read access

Supported

to the HA and hardware fragment in LDAP. Configure

This permission allows read/write

Supported

access to LDAP fragments that are typically used when changing configuration data in LDAP. RNW CM

Monitor

Management

This permission enables read access to Ready RNW CM Management operations.

Manage


Ready

access to RNW CM Management operations. S3part Server

Monitor

Access

This permission enables read access to Ready S3part Server Access operations.

Manage


Ready

access to S3part Server Access operations. State Handling

Monitor

This permission enables read access to Ready State Handling operations.

Manage


Ready

access to State Handling operations. SW Version

Monitor

This permission enables read access to Supported SW Version operations.

Issue: 1-2

DN09118114

98




Description

Adaptation Support

Manage

This SWVersionmanage security

Supported

permission enables the user to launch the SW Version Viewer application and perform operations such as View Current SW Sets and View Current Delivery. User Authority

Monitor

Manager

This permission enables read access to Ready User Authority Manager operations.

Manage


Ready

access to User Authority Manager operations. Active Sessions

Monitor


Supported

to Active Sessions operations in the Application Launcher, such as View Active Sessions. Manage


Supported

access to Active Sessions operations in the Application Launcher, such as Terminate Active Sessions.

Table 23: Supported LTE iOMS roles and permissions Note:

• Supported - The role and its corresponding permissions are supported in adaptation and LTE iOMS.

• Ready - The role and its corresponding permissions are provided in the adaptation only. This list of roles and permissions is applicable only to LTEGOMS root context.

Issue: 1-2

DN09118114

99


Disabling integration

7 Disabling integration You must undo the network element integration in the following cases:

• When there are big changes in the Flexi Multiradio BTS LTE after an upgrade • When a rollback to a previous release (Flexi Multiradio BTS LTE or NetAct) is required • When it is necessary to undo the current integration • When Flexi Multiradio BTS LTE must be removed from NetAct • When Flexi Multiradio BTS LTE is moved to another NetAct or NMS; for this case, steps 3-11 are not required This procedure disables integration of NetAct and LTE iOMS. If LTE iOMS is integrated to another NetAct, then it will unregister from the previous NetAct but leave topology, alarms, and measurements behind. Before disabling Flexi Multiradio BTS LTE, ensure that a backup of the configuration is available. For more information, see Deleting eNB from NetAct.

7.1 Disabling Flexi Multiradio BTS LTE integration 1. Log in to NetAct Start Page as the user who has the permission to disable integration. Note: For more information, refer to Managing integration users.

2. Select Monitoring → Monitor. Expected outcome The NetAct Monitor application window appears. 3. Select Tools → Managed Objects → Object Explorer. 4. Expand the PLMN-PLMN object. 5. In NetAct Monitor, right-click the MRBTS object. 6. Select Maintenance → Set under maintenance. 7. Select Delete All Alarms from Database → Delete Alarms For Object And Its Subnetwork. 8. When prompted, select Yes, and then wait until the process is completed.

Issue: 1-2

DN09118114

100



Note: Repeat steps 6 to 8 for all MRBTS objects.

9. Log in to NetAct Start Page as the user who has the permission to disable integration. 10. Select Configuration → CM Operations Manager. Expected outcome The CM Operations Manager application opens. 11. To open the Workflow Engine dialog box, perform either of the following:

• From the Tools menu, select Workflow Engine.... • In the Plans tab, select the plan name, and then from the Tools menu, select Workflow Engine for Plan. Expected outcome The Workflow Engine dialog box appears. 12. In the MO(s) area, you can perform either of the following:

• Drag and drop the network elements from CM Editor. • Copy and paste the network elements from CM Editor. • Select working sets from the Working Set field. Note: CM Editor and Workflow Engine must be open to drag and drop, or copy and paste, the network elements from CM Editor. To locate the managed objects: 1. In the NetAct Start Page, select Configuration → CM Editor. 2. From the left pane, select Actual Configuration → PLMN-PLMN → .

13. From the Operation List drop-down list, select NE data deletion from Configurator. 14. In the Start column, click Start to begin the operation. 15. In the Name field, enter a name for the operation. This step is optional. 16. In the Description field, enter a description for the operation. This step is optional. 17. In the Scope area, select the managed objects for which the operation needs to be done. 18. Click Start. 19. When prompted, select Yes, and then wait until the process is completed.

Issue: 1-2

DN09118114

101



Expected outcome The NE data deletion from Configuration: Finished dialog box appears displaying the results of the operation. 20. In NetAct Monitor, right-click the MRBTS object. 21. When prompted, select Delete → Yes, and then wait until the process is completed. Note: Repeat steps 20 to 21 for all MRBTS objects. For more information, see Deleting managed object.

7.2 Disabling LTE iOMS integration 1. Log in to the NetAct Start Page as the user who has the permission to disable integration. Note: For more information, refer to Managing integration users.

2. Select Monitoring → Monitor. Expected outcome The NetAct Monitor application window appears. 3. In the NetAct Monitor, right-click the LTE iOMS object. 4. Select Maintenance → Set under Maintenance. 5. Select Delete All Alarms from Database → Delete Alarms For Object And Its Subnetwork. 6. When prompted, select Yes, and then wait until the process is completed. 7. From the NetAct Start Page, select Configuration → CM Operations Manager. Expected outcome The CM Operations Manager application opens. 8. To open the Workflow Engine dialog box, perform either of the following:

• From the Tools menu, select Workflow Engine.... • In the Plans tab, select the plan name, and then from the Tools menu, select Workflow Engine for Plan.

Issue: 1-2

DN09118114

102



Expected outcome The Workflow Engine dialog box appears. 9. In the MO(s) area, you can perform either of the following:

• Drag and drop the network elements from CM Editor. • Copy and paste the network elements from CM Editor. • Select working sets from the Working Set field. Note: CM Editor and Workflow Engine must be open to drag and drop, or copy and paste, the network elements from CM Editor. To locate the managed objects: 1. In the NetAct Start Page, select Configuration → CM Editor. 2. From the left pane, select Actual Configuration → PLMN-PLMN → .

10. From the Operation List drop-down list, select NE data deletion from Configurator. 11. In the Start column, click Start to begin the operation. 12. In the Name field, enter a name for the operation. This step is optional. 13. In the Description field, enter a description for the operation. This step is optional. 14. In the Scope area, select the managed objects for which the operation needs to be done. 15. Click Start. 16. When prompted, select Yes, and then wait until the process is completed. Expected outcome The NE data deletion from Configuration: Finished dialog box appears displaying the results of the operation. 17. In NetAct Monitor, select Tools → Managed Objects → Object Explorer. 18. Expand the PLMN-PLMN object. 19. Right-click the LTE iOMS object, and then select Element Management → Element Manager → OMS EM. Expected outcome The Application Launcher window appears.

Issue: 1-2

DN09118114

103



Note: If the message JAVA VIRTUAL MACHINE VERSION IS NOT SUPPORTED appears, then you may ignore it by pressing I on the keyboard.

20. Double-click Parameter Tool. Note: If the Parameter Tool is not visible in the Application Launcher, follow the procedure under the LTE iOMS Parameter Tool entry in the Preparation checklist for LTE iOMS table to make the Parameter Tool visible. Expected outcome The Parameter Tool window appears. 21. Select fsClusterId=ClusterRoot → fsFragmentId=NWI3 → fsFragmentId=mediator. If there are multiple items under fsFragmentId=mediator, then select the item that has an Active Value of true for fsnwi3configurationActive. 22. On the right-hand pane, remove value designated for fsnwi3registrationServiceIOR. To remove the value from the Active Value column of fsnwi3registrationServiceIOR, doubleclick the figure, clear the IOR entry, and then click OK. Expected outcome The Active Value of fsnwi3registrationServiceIOR is updated to IOR. 23. Close the Parameter Tool window and the Application Launcher window. 24. Using SSH, log in to LTE iOMS as Nemuadmin user. 25. Using the su - command, switch to root user and restart NWI3Adapter by entering the following command: fshascli -rn /NWI3Adapter Expected outcome The NWI3Adapter restarts and the changes are saved. 26. From the NetAct Start Page, select Monitoring → Monitor.

Issue: 1-2

DN09118114

104



Expected outcome The NetAct Monitor application window appears. 27. In the NetAct Monitor, right-click the LTE iOMS object. 28. When prompted, select Delete → Yes, and then wait until the process is completed. Note: For more information, refer to Deleting managed object.

29. Close NetAct Monitor.

Issue: 1-2

DN09118114

105


Troubleshooting integration problems

8 Troubleshooting integration problems

8.1 Integration data upload fails Problem The integration process is not successful. Possible causes

• NWI3 Access is not created in NEAC. • Username or password of NWI3 Access is not configured correctly in NEAC. • The NWI3 service of NetAct is not active. • NWI3Adapter of LTE iOMS was locked. 1. Create or recreate NWI3 access. a) If NWI3 Access for LTE iOMS has not yet been created, then create it. For more information, refer to Creating service users required for Flexi Multiradio BTS LTE Integration. b) If NWI3 Access has already been created but the problem still happens, then recreate the NWI3 Access. 1. Log in to the NetAct Start Page as omc user. 2. Select Security → Network Element Access Control. 3. Check if NWI3 Access has the proper credential. If the credential is not correct, then proceed to the next step. 4. Select NWI3 Access and then click Delete. 5. To recreate NWI3 Access for LTE iOMS, refer to Creating service users required for Flexi Multiradio BTS LTE Integration. c) Check the password of NWI3 Access. 1. Log in to the NetAct Start Page as omc user. 2. Select Security → Network Element Access Control. 3. Check if NWI3 Access credential for Network Element is correct. If the username is not correct, then remove NWI3 Access for LTE iOMS, and then create a new NWI3 Access for LTE iOMS. 4. If the password is not correct, then select NWI3 Access for LTE iOMS. 5. Click Modify, and then enter the correct password. 6. Launch Integration Data Upload. d) Start the NWI3 service.

Issue: 1-2

DN09118114

106



Note: These steps are intended only for the system administrator with root privileges.

1. Log in to the NetAct NWI3 node as root user. 2. To start the NWI3 service, enter the following command: smanager.pl start service nwi3 Expected outcome NWI3 service starts successfully. An output like the one below appears: Service nwi3 started on node 3. Launch Integration Data Upload. e) Check the status of NWI3Adapter. 1. Log in to the LTE iOMS NE with a valid account. 2. To check the NWI3Adapter status, enter the following command: fshascli -s /NWI3Adapter Expected outcome An output like the one below appears:

Figure 20: Example of output

3. If NWI3Adapter is locked, unlock it by entering the following command: fshascli -u /NWI3Adapter Expected outcome NWI3Adapter is unlocked. You may also refer to Unlock LTE iOMS NWI3 Adapter. 4. To restart NWI3Adapter, enter the following command: fshascli -rn /NWI3Adapter Expected outcome NWI3Adapter restarts successfully.

Issue: 1-2

DN09118114

107



5. Launch Integration Data Upload again. 2. Update Parameter Tool attributes and restart NWI3 Adapter. a) Using an SSH client, log in to the node where NWI3 service is running. b) Get the IOR information by entering the following command: cat /var/opt/oss/global/nwi3/RegistrationService..ior For example, cat /var/opt/oss/global/nwi3/ RegistrationService.clab123node01.netact.nsn-rdnet.net.ior Expected outcome An output like the one below appears: IOR:010000002400000049444c3a4e5749332f526567697374726174696f6e53657276 6963655f56313a312e300001000000000000008c000000010102000d00000031302e34 342e3234362e3134000006c03900000014010f004e5550000000190000000001000000 526f6f74504f41006e77336e33632e31006e77336e33632e315f526567536572766963 655f3000000002000000000000000800000001ec8900004f4154010000001800000001 ec89000100010001000000010001050901010000000000 Take note of the IOR information. c) Get the password of the nwi3system user by entering the following command: /opt/nokia/oss/bin/syscredacc.sh -user nwi3system -type APPSERV instance APPSERV Expected outcome The password of the nwi3system user is displayed. d) Close the SSH session. e) Open the Application Launcher. Note: The IP address of LTE iOMS must be determined prior to launching the tool. If the Application Launcher is not yet installed, then install it locally. For more information, refer to Installing Application Launcher in Node Manager Server. f) Run the Parameter Tool. Note: If the Parameter Tool is not visible in the Application Launcher, follow the procedure under the LTE iOMS Parameter Tool entry in the Preparation checklist for LTE iOMS table to make the Parameter Tool visible.

Issue: 1-2

DN09118114

108



g) Check the value of fsnwi3ActiveN3CF. Navigate to fsFragmentID = NWI3 → fsFragmentID = security. Take note of the fsnwi3ActiveN3CF value. h) Navigate to fsFragmentID=NWI3 → fsFragmentID=mediator → fsnwi3N3CFId=X. Note: X must be equal to the value of fsnwi3ActiveN3CF determined in the previous step.

i) Modify the following attributes: Parameter Tool attribute

New Value

fsnwi3initialRegistrationUsername

nwi3system

fsnwi3initialRegistrationPassword

The password derived from Step 3

fsnwi3registrationServiceIOR

The IOR value derived from Step 2

fsnwi3takeIntoUseNext

true

Table 24: Values for Parameter Tool attributes j) Close Parameter Tool and Application Launcher. k) Log in to LTE iOMS using an SSH client. l) Restart NWI3Adapter by entering the following command: fshascli -r /NWI3Adapter Expected outcome NWI3Adapter restarts successfully. m) To check the status of LTE iOMS services, enter the following command: # zstatus -d Expected outcome An output like the one below appears: Monitoring cluster CLA-0 R_GOMS6_1.113.1.0.release_oms.corr4 RecoveryGroups(@OMS, disabled): RecoveryUnits(@/, disabled): Processes(@/, disabled): Monitoring cluster FINISHED

Issue: 1-2

DN09118114

109



n) Execute Integration Data Upload again. For more information, refer to Executing integration data upload. 3. Unlock LTE iOMS NWI3 Adapter. a) Log in to LTE iOMS using an SSH client. b) Unlock NWI3Adapter by entering the following command: fshascli -u /NWI3Adapter Expected outcome NWI3Adapter is successfully unlocked. c) Launch Integration Data Upload again.

8.2 Alarm upload fails Problem HTTPS operation failure in CM upload. Possible causes

• The required certificates are not installed. Solution Make sure the required licenses are installed. For more information, refer to Configuring certifications on network element.

8.3 Element management launch fails Problem

• The element manager can not be launched. Possible Causes

• Node manager is not installed or configured properly. • Element manager is not configured properly.

Issue: 1-2

DN09118114

110



Solution 1. Check Node Manager installation and configuration. For more information, contact your NetAct administrator. 2. Check if the related service user is created. For more information, refer to Creating service users required for Flexi Multiradio BTS LTE Integration. 3. Check if the element manager is configured properly. For more information, refer to Prerequisites for Element Management

8.4 No fault management data received Problem

• There is no alarm displayed in NetAct Monitor. Possible causes

• User permission is incorrect. • Firewall is not properly set up. For more information, refer to Setting up firewall rules. • Integration data upload failed. For more fault management troubleshooting information, refer to the Troubleshooting section of the NetAct Operating Documentation and navigate to Troubleshooting NetAct → Fault Management. Solution 1. Check connectivity and required NetAct components. a) Check if the NWI3 mediation is running.

• For instructions on starting the service, refer to Starting the NWI3 service in Administering NWI3.

• For more information, refer to Checking the status of NWI3 mediation in Administering NWI3. b) Check the IP connectivity between Flexi LTE BTS and NetAct. For more information, refer to Checking connection from NetAct to Flexi Multiradio BTS LTE. c) Check the deployed adaptation packages. For more information, refer to Checking the adaptation packages in Adaptation Manager. 2. Check required permissions. Verify if the appropriate user permission is granted. For more information, refer to Creating service users required for Flexi Multiradio BTS LTE Integration. 3. Check the status of the Fault Management process.

Issue: 1-2

DN09118114

111



Verify if the Fault Management process is running. For more information, refer to Administering Fault Management.

8.5 State management operation 8.5.1 State management operation fails The basic feature of the State Management functionality is the ability to change the Administrative State of network elements, such as LNCELs. The Administrative State on an object describes the permission for, or prohibition against, using the resource imposed through management services. This function is triggered using a dedicated state management option in the NetAct Monitor. Problem

• Failed appears as the status of State Management. Possible Causes

• PLMN hierarchy is incorrect. • The required licenses are missing. • The Enable Graceful Cell Shutdown parameter is disabled 1. Check connectivity and required NetAct components. a) Check if the NWI3 mediation is running.

• For instructions on starting the service, refer to Starting the NWI3 service in Administering NWI3.

• For more information, refer to Checking the status of NWI3 mediation in Administering NWI3. b) Check the IP connectivity between Flexi LTE BTS and NetAct. For more information, refer to Checking connection from NetAct to Flexi Multiradio BTS LTE. c) Check the deployed adaptation packages. For more information, refer to Checking the adaptation packages in Adaptation Manager. 2. Check root object of NE. Make sure the network element is under PLMN-PLMN hierarchy in NetAct Monitor. For more information, refer to Checking and creating the root object in NetAct. 3. Check required licenses. Make sure the required licenses are installed. For more information, refer to Checking NetAct licenses required for LTE software. 4. Update CM parameter.

Issue: 1-2

DN09118114

112



In the CM Editor, set the value of the LNBTS parameter Enable Graceful Cell Shutdown (enableGrflShdn) to Enabled. For more information, refer to Changing the administrative state of managed objects under NetAct Administration.

8.5.2 Error message "Existing operation is still running, please try again later." appears Every State Management operation is locked according to the network element being processed. Simultaneous execution of State Management operations is not possible on the same network element. The preceding operation must be completed before another state management operation can proceed. Problem Unable to proceed with the state management operation even if no other operation is currently running. Possible Cause Forced or premature termination of the previous state management operation. Solution Note: Note down the BTS instance number of the unresponsive network element.

1. From the NetAct Start Page, open the CM Operations Manager application. 2. In CM Operations Manager, click the Operation History tab. 3. Check the status of the provision operation of the affected network element. If the status is Started, wait for the provision operation to be completed before executing another State Management operation on the network element. If the status is either Finished, Failed, or Interrupted, or if the provision operation of the affected network element is not found, then do the following: a) Using an SSH client, log in to the NetAct node running the WAS service as omc user. b) Navigate to /var/opt/nokia/oss/global/adaptations/statemgmt by entering the following command: cd /var/opt/nokia/oss/global/adaptations/statemgmt c) Locate the LCK files related to the unresponsive network element object. d) Remove the LCK file by entering the following command: rm

MRBTS-.LCK

For example:

Issue: 1-2

DN09118114

113


rm


MRBTS-1728.LCK

4. Retry the failed state management operation.

8.6 No performance management data received in database Problem Performance Management (PM) data is not reflected in the database. Possible Cause

• PM pipe is not running. • Some ETLOAD processes stopped working. • Invalid OMeS files are received. • OMeS file is inaccessible. 1. Check PM pipe status. a) To check the status of the PM pipe, refer to Checking the status of PM Pipe service. b) If the PM pipe service is not started, restart the service by following the succeeding steps: Note: These steps are intended only for the system administrator with root privileges.

1. Log in to the VM where the rep service is running as root user. 2. To restart the rep service, enter the following command: $ smanager.pl start service rep- Expected outcome An output like the one below appears: Service rep-

started on node

2. For ETLOAD-related issues, refer to ETLOAD processes failures. 3. For invalid OMeS, refer to Invalid semantic error in etlpslmx. 4. For OMeS accessibility problems, refer to Troubleshooting "Cannot access file. Can't gunzip" error in etlpslmx.

Issue: 1-2

DN09118114

114

Nokia Networks

LTE Radio Access, Rel. FDDLTE 15A, Operating Documentation, Issue 02 Configuring RF Sharing DN09172017 Issue 06 Approval Date 2015-09-23

Configuring RF Sharing

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 © 2015 Nokia Solutions and Networks. All rights reserved.

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 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 any additional information.

2

DN09172017

Issue: 06


Table of Contents This document has 62 pages Summary of changes..................................................................... 7 1

Concepts of RF sharing and RX diversity sharing....................... 10

2 2.1 2.2

RF Sharing deployment scenarios............................................... 11 Installing a new RF sharing site....................................................11 Adding RF Sharing to existing site and activating locally.............13

2.3

Adding RF Sharing with locked WCDMA cells.............................16

3 3.1 3.2

Commissioning RF sharing.......................................................... 22 Commissioning WCDMA for 2-RAT RF Sharing.......................... 22

3.3

Commissioning GSM for 2-RAT RF Sharing................................ 32

3.3.1

Sync Hub related BSC MML commands to set right Sync Mode for GSM BTS..................................................................................... 37 Recommissioning RF Sharing to change particular settings in Master technology........................................................................38

3.4

4 4.1

Reverting RF sharing site to dedicated site................................. 41 Reverting RF sharing site to dedicated GSM site........................ 41

5 5.1

Rx diversity sharing......................................................................43 Rx diversity sharing requirements................................................43

5.2

Commissioning WCDMA or LTE to RX diversity sharing............. 46 Commissioning GSM to RX diversity sharing.............................. 51

5.3 5.4 5.4.1 5.4.2

Issue: 06

Commissioning LTE for 2-RAT RF Sharing..................................27

LTE-GSM RF sharing with Rx diversity sharing (P-type configuration)............................................................................... 53 Commissioning type P configuration in LTE.................................55 Commissioning type P configuration in GSM...............................59

DN09172017

3


List of Figures

4

Figure 1

Main differences between RF sharing and RX diversity sharing concepts............................................................................................. 10

Figure 2

RF Sharing with locked WCDMA cells concept..................................16

Figure 3

Commissioning - reconfiguration, target: BTS....................................18

Figure 4

GSM BTS - alarms at startup............................................................. 19

Figure 5

GSM BTS - selecting shared/dedicated modules...............................20

Figure 6

WCDMA - Enable EIF2 as RP3-01 interface......................................23

Figure 7

BTS Synchronization settings.............................................................24

Figure 8

WCDMA - Concurrent Mode Settings.................................................25

Figure 9

WCDMA - Local Cell Resources........................................................ 26

Figure 10

WCDMA - Send Parameters.............................................................. 27

Figure 11

LTE - Enable EIF2 as RP3-01 interface............................................. 28

Figure 12

BTS Synchronization settings.............................................................30

Figure 13

LTE - Concurrent Mode Settings for LTE-2G......................................31

Figure 14

LTE - Concurrent Mode Settings for LTE-3G......................................31

Figure 15

GSM - Site Specific Information......................................................... 35

Figure 16

GSM - Module Configuration for Sync Hub Master............................ 36

Figure 17

GSM - Module Configuration for Sync Hub Slave.............................. 36

Figure 18

GSM - Local Sector Settings.............................................................. 37

Figure 19

Rx diversity sharing requirements...................................................... 43

Figure 20

Carrier-TRX spacing rules (pictures not in scale)...............................44

Figure 21

Additional Rx diversity cables connection.......................................... 45

Figure 22

Rx diversity signal paths.....................................................................46

Figure 23

RX diversity sharing: WCDMA - Local Cell Resources...................... 47

Figure 24

RX diversity sharing: WCDMA - Carrier settings................................ 48

Figure 25

RX diversity sharing: WCDMA - Antenna Line Management............. 48

Figure 26

RX diversity sharing: WCDMA - AISG MHA Settings: LNA1..............49

Figure 27

RX diversity sharing: WCDMA - AISG MHA Settings: LNA2..............49

Figure 28

RX diversity sharing: WCDMA - Antenna Line Settings - RX antenna modifications.......................................................................................50

Figure 29

WCDMA - Send Parameters.............................................................. 50

Figure 30

RX diversity sharing: GSM - Antenna Line Settings - TX (example)...... 52

Figure 31

RX diversity sharing: GSM - Antenna Line Settings - RX...................52

Figure 32

RX diversity sharing: GSM - Antenna Line Settings - RX - for Flexi Compact............................................................................................. 53

Figure 33

P-type configuration for LTE FSME with resource allocation............. 54 P-

Figure 34

type configuration for LTE FSMF with resource allocation..............55 P-

Figure 35

type LTE - LTE Concurrent Mode Settings......................................56 P-

Figure 36

type LTE - Cell Resources.............................................................. 57

DN09172017

Issue: 06


Issue: 06

Figure 37

P-type LTE - LTE Carriers...................................................................58

Figure 38

P-type LTE - Antenna Line Settings................................................... 58 P-

Figure 39

type GSM - Local sector 1.............................................................. 60 P-

Figure 40


Figure 41


Figure 42

type GSM - Antenna line settings................................................... 62

DN09172017

5


List of Tables

6

Table 1

RAT releases covered by the document...............................................7

Table 2

Clock source (CS) parameter values..................................................38

Table 3

SENA parameter values..................................................................... 38

Table 4

WCDMA/LTE settings forcing the GSM recommissioning.................. 39

Table 5

Example of manual filter tuning (FXDA)............................................. 48

DN09172017

Issue: 06


Summary of changes

Summary of changes Changes between document issues are cumulative. Therefore, the latest document issue contains all changes made to previous issues. This document is common for Radio Access Technologies (RATs) listed in Table 1: RAT releases covered by the document. Table 1

RAT releases covered by the document

Radio Access Technology (RAT)

Product release

GSM/EDGE (BSS)

RG30 (BSS), RG40 (BSS), GSM16 (BSS)

WCDMA RAN

RU40, RU50, RU50 EP1, WCDMA16

Long Term Evolution

RL50, RL60, RL70, FDD-LTE 15A

Changes between issues 05 (2015-06-16) and 06 (2015-09-23) Installing a new RF sharing site

• • • •

Information on WCDMA licenses has been removed. Information on storage of SCF files in NetAct has been added. Steps 3, 6, 7 and 9 have been updated. Information of FDSW has been removed.

Adding RF Sharing to existing site and activating locally

• • •

Information on licenses has been updated. Information on storage of SCF files in NetAct has been added. Steps 3, 5 and 12 have been updated.

Adding RF Sharing with locked WCDMA cells

• •

Information on licenses has been updated. Steps 4, 6 and 8 have been updated.

Commissioning WCDMA for 2-RAT RF Sharing

• • •

Information on licenses has been removed. Information on Enable FSM EIF2 as RP3-01 interface option has been added to step 1. Note about secondary sync source for SyncHyb Slaves has been added.

Commissioning LTE for 2-RAT RF Sharing

• • •

Information on licenses has been removed. Note about secondary sync source for SyncHyb Slaves has been added. Note about the power sums has been removed.

Commissioning GSM for 2-RAT RF Sharing

•

Step Proceed to Site Specific Information has been updated.

Sync Hub related BSC MML commands to set right Sync Mode for GSM BTS

•

Section has been added.

Recommissioning RF Sharing to change particular settings in Master technology

Issue: 06

DN09172017

7

Summary of changes


•

Section has been updated.

Reverting RF sharing site to dedicated GSM site

•


LTE-GSM RF sharing with Rx diversity sharing (P-type configuration)

• •

Note about MHA restriction has been added. Figure P-type configuration for LTE FSMF with resource allocation has been added.

Concept of RP3-blocking SW

•

Section has been removed.

Adding RF Sharing with RP3-blocking SW case 1

•


Adding RF Sharing with RP3-blocking SW case 2

•


Changes between issues 04 (2015-05-25) and 05 (2015-06-16) Commissioning WCDMA for 2-RAT RF Sharing

• • •

Step Proceed to BTS Synchronization settings has been added. Step Proceed to Concurrent Mode Settings has been updated. Post requisite has been added.


• • •

Step Proceed to BTS Synchronization settings has been added. Step Proceed to Concurrent Mode Settings has been updated. Post requisite has been added.


• • •

Note regarding GSM as Sync Hub Master has been added. Step Proceed to Site Specific Information has been added. Step Proceed to Module Configuration has been updated.

Troubleshooting RF sharing

•

Section has been moved to Troubleshooting RF Sharing document.

Changes between issues 03 (2015-02-27) and 04 (2015-05-25) Commissioning WCDMA for 2-RAT RF Sharing

•

Note regarding GSM recommission has been removed.


•



8

DN09172017

Issue: 06


Summary of changes

•


Recommissioning RF Sharing to change particular settings in Master technology

•


Commissioning WCDMA or LTE to RX diversity sharing

•

Minor changes in center frequency tuning have been made.

Commissioning GSM to RX diversity sharing

•

Issue: 06

Minor changes in manual filter tuning have been made.

DN09172017

9

Concepts of RF sharing and RX diversity sharing


1 Concepts of RF sharing and RX diversity sharing A description and a picture showing the basic differences between RF sharing and RX diversity sharing. There are two ways of deploying two technologies at one site with shared resources: RF sharing and RX diversity sharing (also called antenna sharing). The main difference is that in RF sharing the technologies work in Master-Slave mode and the same RFMs/RRHs are used by both technologies, while in RX diversity sharing both technologies are transmitting independently, using dedicated RFMs. Figure 1: Main differences between RF sharing and RX diversity sharing concepts presents the main differences between those deployment cases. Note that the figure is only an example. Figure 1

Main differences between RF sharing and RX diversity sharing concepts

RF Sharing Sync Mas

Radio Master Technology 1 System Module

Shared RFM/RRH

ALD

Antennas

s

Technology 2 System Module

RX diversity sharing Radio Master Technology 1 System Module

Technology 1 dedicated RFM

Antennas

Radio Master Technology 2 dedicated RFM

Technology 2 System Module

10

DN09172017

ALD s

Issue: 06


RF Sharing deployment scenarios

2 RF Sharing deployment scenarios A list the most typical RF sharing deployment scenarios. For the supported and recommended HW combinations, the latest SW release combinations, and the recommended SW upgrade paths, see the following documents:

• •

•

RF-Sharing Regular Maintenance Newsletter This RF Sharing Newsletter is published internally and updated monthly. For details, contact Technical Support. Flexi Multiradio BTS RF Sharing Released Configurations Available in NOLS at the following directory: NOLS ► Product Information Center ► Documentation finder ► Radio Network ► Base Stations ► Flexi Multiradio 10 BTS EDGE / Flexi Multiradio BTS EDGE / Flexi Multiradio BTS WCDMA / Flexi Multiradio BTS LTE ► Operating documentation ► Flexi Multiradio BTS RF Sharing Released Configurations (XLS format) Compatibility Matrix Available in NOLS at the following directory: NOLS ► Product Information Center ► Compatibility Matrix ► Compatibility Matrix - Access Networks

2.1 Installing a new RF sharing site Steps to install a new site with RF sharing: WCDMA-GSM, LTE-GSM, or WCDMA-LTE. Purpose The purpose of this scenario is to prepare a new RF sharing site. Both technologies' HW is installed and activated locally during the site visit. After the site visit both technologies are on air. Ensure that you have all the respective instructions to prepare the desired site.

Before the site visit 1

Prepare the configurations, depending on which technologies are used: a) For GSM: create the site on BSC. b) For WCDMA: create the site on RNC. Optional: Prepare Site Configuration Files (SCFs) for both technologies to save the site visiting time. It is recommended that you store the backup of SCFs for both technologies in NetAct as soon as the RF Sharing site is accepted. This would serve as a reference in the future troubleshooting and help in faster recovery of sites in HW replacement scenarios.

Issue: 06

DN09172017

11


2

g


Install the correct GSM/WCDMA/LTE BTS Site Manager version on your computer(s). It is recommended that you have two computers, which allows simultaneous connection to both technologies' Site Managers.

3

Check the supported SW for both technologies in Compatibility Matrix, in Flexi Multiradio BTS RF Sharing Released Configurations, or in RF-sharing Regular Maintenance Newsletter. For details on these documents, see RF Sharing deployment scenarios section.

4

Optional: Update the System Module SW. It is recommended that you update the new System Module SW before the site visit (if possible) to reduce the site visit time.

During the site visit 5

Install the HW, do the cabling, and connect your computer(s) to System Modules via Local Management Ports (LMPs). To connect the modules for RF sharing configurations, see Flexi Multiradio BTS RF Sharing Released Configurations. For details, see the respective Installing and Cabling Flexi Multiradio documentation. Ensure that the RFM/RRH has the same SFP type as the System Module - 3 Gbps or 6 Gbps. In case of LTE, always use 6 Gbps SFPs and optical links, when supported by the used HW.

6

Power up the Master technology's System Module (WCDMA or LTE).

7

If not done before, update the System Module SW to the desired version. If Incompatible SW version detected (0023) alarm is raised, update the SW again. Ensure that all the installed RFMs/RRHs and ALDs are detected and shown properly in the BTS Site Manager. Result The HW is now ready for commissioning.

8

Commission the Master technology for RF sharing.

9

Power up the Slave technology's System Module and update the System Module SW to the desired version, if not done before.

10 Commission the Slave technology for RF sharing. In case GSM is the Slave technology, select "Manual commissioning", then fetch the SCF from the Master technology's BTS (as a Backup Commissioning File) and use it as a template in Hardware Configuration.

12

DN09172017

Issue: 06



Result The site is ready and both technologies are on air. Post requisites Before leaving the site ensure that:

• • •

Both technologies are working properly without any unexpected alarms. Test calls (both voice and data) are successful in each cell/sector. All unused ports (for example LMP) are secured with IP caps.

2.2 Adding RF Sharing to existing site and activating locally Steps to add one technology HW to an already existing site and create an RF sharing site: WCDMA-GSM, LTE-GSM, or WCDMA-LTE. Purpose Typical initial status:

• •

GSM is already on air, WCDMA or LTE is now added as a Master technology. WCDMA is already on air, LTE is now added as a Slave technology.

The purpose of this scenario is to add RF Sharing to the site. The other technology's HW is installed and RF Sharing is activated locally during the site visit. After the site visit both technologies are on air. Ensure that you have all the respective instructions to prepare the desired site.

Before the site visit 1

If possible, prepare the shared configurations, depending on which technologies are used: a) For GSM: create the site on BSC. b) For WCDMA: create the site on RNC. Optional: Prepare Site Configuration Files (SCFs) for both technologies to save the site visiting time. It is recommended that you store the backup of SCFs for both technologies in NetAct as soon as the RF Sharing site is accepted. This would serve as a reference in the future troubleshooting and help in faster recovery of sites in HW replacement scenarios.

2

Install the correct GSM/WCDMA/LTE BTS Site Manager version on your computer(s). When activating RF Sharing in an existing WCDMA site, ensure you have the new required licences downloaded to your computer.

Issue: 06

DN09172017

13



It is recommended that you have two computers, which allows simultaneous connection to both technologies' Site Managers.

g 3

Check the supported SW for both technologies in Compatibility Matrix, in Flexi Multiradio BTS RF Sharing Released Configurations, or in RF-sharing Regular Maintenance Newsletter. For details on these documents, see RF Sharing deployment scenarios section.

4

Optional: Update and activate the already deployed technology's System Module SW. If the SW update is needed for the already deployed technology, update it remotely to save the site visit time.

5

Optional: Update the new technology's System Module SW. It is recommended that you update the new technology's System Module SW before the site visit (if possible). This reduces the site visit time and the eventual downtime of the already deployed technology's transmission. FSMF is delivered with Factory Delivered SW (FDSW). Site Manager does not detect any RFMs/RRHs and ALDs until the System Module is updated with appropriate technology SW. For details, see the Technical Support Note: TS-SRAN-HW-0108.

g


Install the new HW. Do not connect the new System Module to the already deployed System Module and RFMs/RRHs. This way does not disturb the already deployed technology transmission.

7

Power up the new technology's System Module. Update and activate the SW, if not done before. This ensures that the new System Module is running the correct SW before proceeding.

8

Power off the already deployed and the new System Modules and finalize the HW installation for RF Sharing. To connect the modules for RF Sharing configurations, see Flexi Multiradio BTS RF Sharing Released Configurations. For details, see the respective Installing and Cabling Flexi Multiradio documentation. Ensure that the RFM/RRH has the same SFP type as the System Module - 3 Gbps or 6 Gbps. In case of LTE, always use 6 Gbps SFPs and optical links, when supported by the used HW. Result The already deployed technology's traffic goes down.

14

DN09172017

Issue: 06



9

Recommended (Optional): Switch the RFM/RRH power cables to the Master System Module. The Shared RFMs/RRHs can be powered from either Master System Module, Slave System Module, or an external power supply, depending on the site environment. If the RFMs/RRHs are powered from the Slave System Module and the Slave System Module gets a HW reset or a failure occurs, both technologies' traffic goes down. Exception: in WCDMA-LTE case, if the Slave (LTE) System Module is FSMF with Power Distribution Sub-module (FPFD), then the System Module reset does not affect the power supply provided by FPFD. If the RFMs/RRHs are powered from the Master System Module (as recommended) and the Slave System Module gets reset or failure occurs, only the Slave technology traffic goes down.

10 Power up the Master technology's System Module and ensure all the RFMs/RRHs and ALDs are detected and shown properly. If Incompatible SW version detected (0023) alarm is raised, update the SW again. Result The HW is now ready for commissioning. 11 Commission the Master technology (WCDMA or LTE) for RF Sharing. If the SCF was not created before the site visit, save the Master technology's SCF for later use in the GSM (Slave) technology commissioning. Save the SCF as a Backup Commissioning File. Result The Master technology cells go on air (in both shared and dedicated RFMs/RRHs). 12 Power up the Slave technology (LTE or GSM) and commission it for RF Sharing. In case of GSM, the commissioning can be conducted with Undo Commissioning (removes both Hardware Configuration and Transmission Parameters) procedure. Before performing Undo Commissioning in GSM save the current SCF. It contains the transmission settings and can be used as a back-up. To commission GSM, fetch the SCF from the Master technology's BTS (as a Backup Commissioning File in case of LTE SCF) and use it as a template in Hardware Configuration. Result The site is ready and both technologies are on air. Post requisites Before leaving the site ensure that:

• •

Issue: 06

Neither of the technologies' Site Managers shows any unexpected alarms. Both technologies are transmitting properly (make test calls).

DN09172017

15


• • •


All unused ports (for example LMP) are secured with IP caps. All cables are routed, connected and tied correctly. Front and back covers are properly installed, if provided with the module.

2.3 Adding RF Sharing with locked WCDMA cells Steps to reuse a GSM band for WCDMA-GSM RF sharing in an already existing site with dedicated WCDMA and GSM. Purpose Initial status: WCDMA (on Band A, for example 2100 MHz) and GSM (on Band B, for example 900 MHz) are already on air, both in dedicated mode. WCDMA Band B WCEL(s) are created in RNC and kept in locked state. Figure 2

RF Sharing with locked WCDMA cells concept

Dedicated RFM

Band

WCDMA S M

Radio Master Shared RFM transmitting only GSM

GSM S M

Band

Sync Mas

Radio Master

Remote RF Sharing activation

WCDMA SM

Band

Dedicated RFM Radio Master

GSM SM

Band

Sync Mas

Radio Master

Shared RFM transmitting WCDMA + GSM

The purpose of this scenario is to add RF Sharing, in which WCDMA and GSM share the Band B (currently used by GSM). The new optical cabling is done, RF Sharing is prepared locally during the site visit. In a typical scenario, the shared RFMs/RRHs transmit only the GSM traffic with limited power budget (due to RF Sharing), overlapping the planned WCDMA carrier bandwidth (BW). Later, the overlapping GSM TRXs are removed and WCDMA cells for RF Sharing are activated remotely. Figure 2: RF Sharing with locked WCDMA cells concept presents the deployment case. Ensure that you have all the respective instructions to prepare the desired site. Use case

16

DN09172017

Issue: 06



This scenario is deployed in cases where the user, for example, has not yet got a legal license to transmit WCDMA on Band B. The scenario is used when WCDMA transmission in dedicated mode (on Band A) is needed.

Prerequisites 1

Install the correct GSM/WCDMA BTS Site Manager version on your computer(s). Ensure you have the new required WCDMA licenses downloaded to your computer. It is recommended that you have two computers, which allows simultaneous connection to both technologies' Site Managers.

2

Optional: Update and activate the System Module SW. If the SW update is needed for the WCDMA and GSM System Modules, update them remotely to save the site visit time.

3

Back up the GSM commissioning file.


Switch off the WCDMA and GSM System Modules. Consider blocking/locking the BTS (sector) objects to hand over the ongoing traffic before powering off the GSM BTS. Result The WCDMA and GSM traffic goes down.

5

Install the new optical cables for RF Sharing. To connect the modules for RF Sharing configurations, see Flexi Multiradio BTS RF Sharing Released Configurations. For details, see the respective Installing and Cabling Flexi Multiradio documentation. Ensure that the RFM/RRH has the same SFP type as the System Module - 3 Gbps or 6 Gbps. In case of LTE, always use 6 Gbps SFPs and optical links, when supported by the used HW.

6

Commission WCDMA to RF Sharing. a) Switch on the WCDMA System Module. Connect to the System Module using the LMP cable and establish local connection via BTS Site Manager. If Incompatible SW version detected (0023) alarm is raised, download the SW again. Result Band B RFM/RRH is detected.

Issue: 06

DN09172017

17



b) In BTS Site Manager, select reconfiguration, as shown in Figure 3: Commissioning - reconfiguration, target: BTS, and update the information regarding the shared Band B RFM(s)/RRH. Figure 3

Commissioning - reconfiguration, target: BTS

c) Save the commissioning parameters and send them to BTS. Save the WCDMA BTS SCF for later use in the GSM technology commissioning. BTS gets reset and is recommissioned to RF Sharing mode. Result Band A cells are active, Band B cells are inactive (locked in RNC). 7

Commission GSM to RF Sharing. a) Power up the GSM System Module. Connect to the System Module locally and run the BTS Site Manager. Two alarms are activated:

• •

18

BCF NOTIFICATION: Shared RF module detected two synchronization master sources. TRX FAULTY: TRX object allocation failed in RF module.

DN09172017

Issue: 06



Figure 4

GSM BTS - alarms at startup

b) In BTS Site Manager select "Commissioning/Change settings manually". Proceed to Hardware Configuration page, select Specify from file and use the WCDMA BTS SCF. Choose RFMs to be shared/dedicated in a pop-up window, as in Figure 5: GSM BTS - selecting shared/dedicated modules. If the shared RFMs'/RRHs' climate-control has not been set in WCDMA commissioning, a window pops up, press Close to ignore it.

Issue: 06

DN09172017

19


Figure 5


GSM BTS - selecting shared/dedicated modules

c) Proceed to Local Sector Settings page and create the GSM configurations again. Important: make sure that BCCH is outside the planned WCDMA carrier BW. The other TRXs can overlap the WCDMA carrier BW. d) Proceed to Transmission Parameters and select "Do not change settings". e) On the last page, press Send SCF. Result All TRXs are in working state. At this point, non-blocking alarms for the TRXs which overlap with WCDMA carrier BW: "TRX OPERATION DEGRADED: TRX object allocation failed in RF module" (7607) are expected. Before leaving the site ensure that:

• • •

Neither of the technologies' Site Managers shows any unexpected alarms. Both technologies transmit properly (make test calls). All unused ports (for example LMP) are secured with IP caps.

After the site visit Perform the steps only when the legal license to transmit WCDMA on band B is acquired.

20

DN09172017

Issue: 06



8

Connect to the BSC and perform the TRX removal procedure: a) Lock the BCF - command ZEFS b) Lock the BTSs (sectors) on BSC - command ZEQS c) Lock all the TCH-TRXs overlapping the WCDMA carrier BW - command ZERS Note that TCH-TRXs have to be allocated at least 2 MHz away from the WCDMA cell's center frequency. Thus overlapping the edges of WCDMA cell bandwidth is allowed. d) Delete the locked TCH-TRXs (command ZERD) or modify their ARFCN (command ZERM) e) Unlock the GSM BTS (sector) - command ZEQS f)

Unlock the BCF - command ZEFS

Result The GSM TRXs go on air. 9

Unlock the WCDMA Band B WCELs on RNC. Result The WCDMA Band B cells go on air.

Issue: 06

DN09172017

21

Commissioning RF sharing


3 Commissioning RF sharing List of instructions on how to commission RF sharing.

3.1 Commissioning WCDMA for 2-RAT RF Sharing Steps to commission WCDMA for RF sharing WCDMA-GSM or WCDMA-LTE. Purpose Follow these steps to commission WCDMA (the Master technology) for:

• •

RF Sharing WCDMA-GSM RF Sharing WCDMA-LTE

Make sure that all the appropriate steps in RF Sharing deployment scenarios section have been completed. The RF Sharing is a part of the commissioning procedure. Commissioning procedures are described in detail in the technology-specific documents. The RF Sharing commissioning steps have to be taken in addition to the technology-specific steps. In RF Sharing configurations, only certain Master-Slave BTS SW combinations, SW upgrade paths and configurations are tested, recommended and officially supported. Using any other SW combinations, upgrade path or configuration might cause unexpected problems. Preconditions:

•

• •

The BTS Site Manager is running and connection to the BTS is established. Always use the matching BTS Site Manager version, considering the running BTS SW version. The running BTS SW in the System Module is the correct version before commissioning. Upgrade the BTS SW if required. The RFMs/RRHs and ALDs are correctly detected. There are no unexpected alarms.

1

Start commissioning.

•

In case of FSMF go through the TRS commissioning first and tick the Enable FSM EIF2 as RP3-01 interface check box.

22

DN09172017

Issue: 06



Figure 6

WCDMA - Enable EIF2 as RP3-01 interface

Select Commissioning, Target: BTS, Commissioning type:

• •

if the WCDMA BTS has not been commissioned at all: Template/Planned/Manual if the WCDMA BTS has already been commissioned: Reconfiguration

Result The BTS Settings page appears. Note that the Slave technology (GSM or LTE) System Module is not detected yet. 2

Proceed to BTS Synchronization settings. In order to use RG602339/RAN3001/LTE1710: Sync Hub Direct Forward, apply the following settings:

•

for Sync Hub Master: -

-

•

for Sync Hub Slave: -

-

-

-

Issue: 06

Configure synchronization settings as related to the synchronization source to be used (no special impact on synchronization settings due to RF sharing and Sync Hub Direct Forward). Synchronization output settings Select the Forward synchronization in co-siting and the PPS synchronization output in use in HO mode check boxes.

Network synchronization mode Select the Phase synchronization from the network synchronization mode dropdown list. Synchronization input settings Select the Sync Hub Master BTS as reference source from the 1PPS synchronization input source in use drop-down list. Tick the 1PPS source line delay and enter the value; 1PPS source line delay is calculated based on the following formula: 1PPS source line delay = 5.4 ns per meter cable (which connects the Synch Hub Master to the Synch Hub Slave) + 8 ns for Sync Out in case of LTE/WCDMA (30 ns in case of GSM) + 12 ns for Sync In in case of LTE/WCDMA (30 ns in case of GSM) If there are further elements connected to a synchronization chain after a Sync Hub Slave, then select the Forward synchronization in co-siting and the PPS synchronization output in use in HO mode check boxes.

DN09172017

23



Note that the 1PPS source line delay is applied from the Sync Hub Slave to be configured up to the Sync Hub Master, which can span over one or more other Sync Hub Slaves in case they are connected in between. The 1PPS source line delay to be compensated needs in this case the accumulative value (i.e. accumulated Cable Length and adding all Sync Out, Sync In connections in between). Do not define a secondary sync source for SyncHub Slaves. Otherwise, SyncHub Slave might not be able to maintain its local phase relationship to the SyncHub Master anymore, when the SyncHub Master is losing its reference clock. In this case the radio slave might discontinue services allocated to the shared RF module. Figure 7: BTS Synchronization settings shows exemplary settings for Sync Hub Slave. Figure 7

3

BTS Synchronization settings

Proceed to Concurrent Mode Settings. Tick the RF sharing enabled check box, choose the shared technologies (3G-2G or 3G-LTE), enter the product code and serial number of the Slave System Module, and choose the shared RFMs/RRHs. The parameter Synchronization master is configurable from RU50 EP1 onwards. When Sync Hub Direct Forward is in use, select Synchronization Hub from the Synchronization master dropdown list. When Sync Hub Direct Forward is not in use, select FSMx 1. Figure 8: WCDMA - Concurrent Mode Settings shows exemplary settings for 3G-2G RF Sharing without using Sync Hub Direct Forward. At least one RFM/RRH must be selected as shared.

24

DN09172017

Issue: 06



Figure 8

4

WCDMA - Concurrent Mode Settings

Proceed to Local Cell Resources. Remember the settings on this page, as they affect the later Slave technology settings. Figure 9: WCDMA - Local Cell Resources shows exemplary settings for 3G2G RF Sharing. Make sure that the power sums of both WCDMA carriers and LTE carriers/GSM TRXs does not exceed the RFM's/RRHs' maximum output power. (Except when BSS21507: Flexible MCPA TX Power Pooling is activated in GSM.)

Issue: 06

DN09172017

25



Figure 9

5

WCDMA - Local Cell Resources

Proceed to WCDMA Carrier Candidates and Local Cell Group Settings. Enter the UARFCN channel value for each Local Cell (use the same value as defined in the RNC). These UARFCN values are stored in the SCF and are later used for the Slave technology commissioning. Thus incorrect values may cause TRX object allocation issues in GSM. Make sure that all WCDMA carriers along with GSM TRXs/LTE carriers are within the RFMs'/RRHs' bandwidths. Note that TCH-TRXs have to be allocated at least 2 MHz away from the WCDMA cell's center frequency. Thus overlapping the edges of WCDMA cell bandwidth is allowed.

26

DN09172017

Issue: 06



6

Proceed to Radio Module External Fault and Control Settings. Every Radio Module external alarm can be commissioned for either or both of the two technologies. For example, if an alarm is commissioned for WCDMA, it is visible from the WCDMA side only.

7

Proceed to the last page - Send Parameters. Select the appropriate Send option:

• •

if the WCDMA BTS has not been commissioned, select: All parameters if the WCDMA BTS has been already commissioned, select: Only changes

Click Send Parameters. Figure 10

WCDMA - Send Parameters

Result The WCDMA System Module resets and the RF Sharing is activated. Post requisites Check the applied settings carefully. If there is an error with the synchronization settings, a BTS might be unable to synchronize and cause RF Modules to be undetectable. Recommissioning is in this case only possible either remotely via NetAct or by uncommission a BTS first.

3.2 Commissioning LTE for 2-RAT RF Sharing Steps to commission LTE for RF sharing WCDMA-LTE or LTE-GSM. Purpose Follow these steps to commission LTE for:

• •

RF Sharing LTE-GSM RF Sharing WCDMA-LTE

Make sure that all the appropriate steps in the RF Sharing deployment scenarios section have been completed. The RF Sharing is a part of the commissioning procedure. Commissioning procedures are described in detail in the technology-specific documents. The RF Sharing commissioning steps have to be taken in addition to the technology-specific steps.

Issue: 06

DN09172017

27



Note that from RL70 onwards, when RF sharing WCDMA-LTE is activated, LTE System Module resets itself and changes its IP addresses (local M-plane IP address is changed from 192.168.255.129 to 192.168.255.127). After the reset the BTS Site Manager reconnects to the same IP address of the previous session (.129) used prior to the reset. However, after the reset LTE (Slave technology) is not at the .129 address anymore, and the connection is actually established to the WCDMA (Master) System Module . Therefore, the disconnection and the reconnection need to be done again either using the local connection probing option, which gives the user a selection of available System Modules, or using the correct local M-plane IP address of LTE System Module directly. When RF Sharing WCDMA-LTE is setup, the same IP address cannot be shared by multiple computers. In RF Sharing configurations, only certain Master-Slave BTS SW combinations, SW upgrade paths and configurations are tested, recommended and officially supported. Using any other SW combinations, upgrade path or configuration might cause unexpected problems. Preconditions:

•

• •

The BTS Site Manager is running and connection to the BTS is established. Always use the matching BTS Site Manager version, considering the running BTS SW version. The running BTS SW in the System Module is the correct version before commissioning. Upgrade the BTS SW if required. The RFMs/RRHs and ALDs are correctly detected. There are no unexpected alarms.

1


•

In case of FSMF go through the TRS commissioning first and check the "Enable EIF2 as RP3-01 interface". Figure 11

LTE - Enable EIF2 as RP3-01 interface

Select Commissioning, Target: BTS, Commissioning type:

• •

when the SCF has been prepared before: Template when there is no SCF file: Manual

Result The BTS Settings page appears. Note that the other technology (GSM or WCDMA) System Module is not detected yet.

28

DN09172017

Issue: 06



2

Proceed to BTS Synchronization settings. In order to use RG602339/RAN3001/LTE1710: Sync Hub Direct Forward, apply the following settings:

•

for Sync Hub Master: -

-

•

Configure synchronization settings as related to the synchronization source to be used (no special impact on synchronization settings due to RF sharing and Sync Hub Direct Forward). Synchronization output settings Select the Forward synchronization in co-siting and the PPS synchronization output in use in HO mode check boxes.

for Sync Hub Slave: -

-

-

-

Network synchronization mode Select the Phase synchronization from the network synchronization mode dropdown list. Synchronization input settings Select the Sync Hub Master BTS as reference source from the 1PPS synchronization input source in use drop-down list. Tick the 1PPS source line delay and enter the value; 1PPS source line delay is calculated based on the following formula: 1PPS source line delay = 5.4 ns per meter cable (which connects the Synch Hub Master to the Synch Hub Slave) + 8 ns for Sync Out in case of LTE/WCDMA (30 ns in case of GSM) + 12 ns for Sync In in case of LTE/WCDMA (30 ns in case of GSM) If there are further elements connected to a synchronization chain after a Sync Hub Slave, then select the Forward synchronization in co-siting and the PPS synchronization output in use in HO mode check boxes.

Note that the 1PPS source line delay is applied from the Sync Hub Slave to be configured up to the Sync Hub Master, which can span over one or more other Sync Hub Slaves in case they are connected in between. The 1PPS source line delay to be compensated needs in this case the accumulative value (i.e. accumulated Cable Length and adding all Sync Out, Sync In connections in between). Do not define a secondary sync source for SyncHub Slaves. Otherwise, SyncHub Slave might not be able to maintain its local phase relationship to the SyncHub Master anymore, when the SyncHub Master is losing its reference clock. In this case the radio slave might discontinue services allocated to the shared RF module. Figure 12: BTS Synchronization settings shows exemplary settings for Sync Hub Slave.

Issue: 06

DN09172017

29



Figure 12

3

BTS Synchronization settings

Proceed to Concurrent Mode Settings. Tick the RF sharing enabled check box, choose the shared technologies (LTE-2G or LTE-3G), enter the product code and serial number of the other technology System Module, and choose the shared RFMs/RRHs. The parameter Synchronization master is configurable from RL70 onwards. When Sync Hub Direct Forward is in use, select Synchronization Hub from the Synchronization master dropdown list. When Sync Hub Direct Forward is not in use, select FSMx 1 for LTE-2G and 3G system module for LTE-3G. In LTE-3G RF Sharing configuration select Optical IF for 3G system module from RL70 onwards. Figure 13: LTE - Concurrent Mode Settings for LTE-2G shows exemplary settings for LTE2G RF Sharing without using Sync Hub Direct Forward. Figure 14: LTE - Concurrent Mode Settings for LTE-3G shows exemplary settings for LTE-3G RF Sharing without using Sync Hub Direct Forward. At least one RFM/RRH must be selected as shared.

30

DN09172017

Issue: 06



4

Figure 13

LTE - Concurrent Mode Settings for LTE-2G

Figure 14

LTE - Concurrent Mode Settings for LTE-3G

Proceed to Cell Resources. In case of RF Sharing LTE-GSM, remember the settings on this page, as they affect the later settings in GSM. In case of RF Sharing WCDMA-LTE, calculate the available power, taking into account the values already commissioned to WCDMA.

Issue: 06

DN09172017

31


5


Proceed to LTE Carriers. Enter the EARFCN channel value for each Local Cell. These EARFCN values are stored in the SCF and is later used for the GSM commissioning. Select the appropriate Bandwidth. Ensure the Bandwidth is supported by the used HW configuration. For details see Flexi Multiradio BTS RF Sharing Released Configurations. Make sure that all LTE carriers along with GSM TRXs/WCDMA carriers are within the RFM's/RRH's UL/DL instantaneous bandwidth, and that they are not overlapping.

g 6

Proceed to Radio Module External Fault and Control Settings. Every Radio Module alarm can be commissioned for either or both of the two technologies. For example, if an alarm is commissioned for LTE, it is visible from the LTE side only.

7

Proceed to the last page - Send Parameters. Select Send: All parameters. Save Parameters, if the SCF is needed for later GSM commissioning, then Send Parameters. Result The LTE System Module resets and the RF Sharing is activated.

Post requisites Check the applied settings carefully. If there is an error with the synchronization settings, a BTS might be unable to synchronize and cause RF Modules to be undetectable. Recommissioning is in this case only possible either remotely via NetAct or by uncommission a BTS first.

3.3 Commissioning GSM for 2-RAT RF Sharing Steps to commission GSM for RF sharing WCDMA-GSM or LTE-GSM. Purpose Follow these steps to commission GSM (the Slave technology) to:

• •

RF Sharing WCDMA-GSM RF Sharing LTE-GSM

Make sure that all the appropriate steps in the RF Sharing deployment scenarios section have been completed.

32

g

GSM as Sync Hub Master is only supported with WCDMA-GSM RF sharing.

g

The RF Sharing is a part of the commissioning procedure. Commissioning procedures are described in detail in the technology-specific documents. The RF Sharing commissioning steps have to be taken in addition to the technology-specific steps.

g

In RF Sharing configurations, only certain Master-Slave BTS SW combinations, SW upgrade paths and configurations are tested, recommended and officially supported. Using any other SW combinations, upgrade path or configuration might cause unexpected problems.

DN09172017

Issue: 06



Preconditions:

•

•

The BTS Site Manager is running and connection to the BTS is established. Always use the matching BTS Site Manager version, considering the running BTS SW version. Appropriate SW is downloaded. The running BTS SW in the System Module is the correct version before commissioning. Upgrade the BTS SW if required. The RFMs/RRHs and ALDs are correctly detected (if the GSM has been commissioned earlier). There are no unexpected alarms.

1


• • •

Select Commissioning Wizard, Change settings manually. 2

Proceed to Site Specific Information. When Sync Hub Direct Forward is in use, apply the following settings:

•

•

for Sync Hub Master: Configure synchronization settings as related to the synchronization source to be used (no special impact due to RF sharing and Sync Hub Direct Forward). Only Timing over Packet with phase synchronization or a GPS receiver is supported as synchronization source, when GSM operates as Sync Hub Master. for Sync Hub Slave:

a) Select the 1PPS+ToD TSIP format from the BTS Sync Source drop-down list. b) Enter the Cable propagation delay value. This value is calculated based on the following formula: Cable propagation delay = 5.4 ns per meter cable (which connects the Synch Hub Master to the Synch Hub Slave) + 8 ns for Sync Out in case of LTE/WCDMA (30 ns in case of GSM) + 12 ns for Sync In in case of LTE/WCDMA (30 ns in case of GSM). c) Apply the following configurations at BSC:

•

Do not active the feature BSS101563: 2G Temp Sync Master role if the Packet Abis is in use, otherwise the BSC resets if 1PPS+ToD loss happens.

g • • •

Issue: 06

Use command ZEFM:BCF ID:CS,:; to configure a GSM BTS as Sync Hub Slave. For CS configure either LMU with Packet Abis or LAB with Legacy Abis.

Use command ZEXI:LMUA=ID:TRE65535,BCF ID:FNO=0,LTO=0,FMU=T,LTD=0; to configure phase offsets to 0 and TRE ID to not applicable. Use command ZEFM:BCF ID:SENA=T,:; to configure Sync Hub Slave to apply phase synchronization. Use command ZEFO to check correct settings.

DN09172017

33



Example commands for BCF = 167 after entering BCF control command line with ZEFO command: BASE CONTROL FUNCTION HANDLING COMMAND < BCF .... MASTER CLOCK BCF LMU .... LOCATION MEASUREMENT UNIT BWLMU... WIDEBAND CODE DIVISION MULTIPLE ACESS LOCATION MEASUREMENT UNIT IWLMU... INDEPENDENT WCDMA LMU LAB .... LMU-ABIS BSSTOP . BSS TOP PHASE PCM .... INDEPENDENT MODE BCF NONE ... REMOVE CLOCK SOURCE */ EFM:167:CS=LMU /*

IDENTIFY BCF PARAMETERS PARAMETER NAMES: … */ EFM:167:CS=LMU,:; EXI:LMUA=167: TRE65535,BCF167:FNO=0,LTO=0,FMU=T,LTD=0; FlexiBSC XYZ LMU AREA PARAMETERS:

2015-01-27

13:51:15

LMU AREA IDENTIFICATION................(LMUA)... 167 TRANSMISSION EQUIPMENT..................(TRE)... 65535 (NOT USED) 167 BASE CONTROL FUNCTION ID................(BCF)... FRAME NUMBER OFFSET.....................(FNO)... 00 LMU TSL FRAME NUMBER OFFSET.............(LTO)... T0 LMU FNO 26-MULTIPLIER USAGE.............(FMU)... LMU TSL FN DELAY........................(LTD)... COMMAND EXECUTED EFO:167:; BASE CONTROL FUNCTION BCF-0167 DATA … CLOCK SOURCE .................(CS).... LMU or LAB SYNCHRONIZATION ENABLED ......(SENA).. T SYNCHRONIZATION MODE .........(SM).... BSSSYNCH …

For more details, see Sync Hub related BSC MML commands to set right Sync Mode for GSM BTS section. Example Exemplary settings for Sync Hub Slave.

34

DN09172017

Issue: 06



Figure 15

3

GSM - Site Specific Information

Proceed to Hardware Configuration. Select Specify from file and browse for WCDMA/LTE SCF. If the shared RFMs'/RRHs' climate-control has not been set in WCDMA or LTE commissioning, a window appears, press Close to ignore it.

4

Proceed to Module Configuration. The shared modules are shown (taken from the Master technology's SCF). If necessary, add the GSM-dedicated RFMs/RRHs. When Sync Hub Direct Forward is in use, select the Sync hub direct forward check box and tick the 1PPS clock output in holdover check box. In case of a Sync Hub Slave and further connected elements to the Sync Chain, also select Forward 1PPS clock. Figure 16: GSM - Module Configuration for Sync Hub Master shows exemplary settings for Sync Hub Master. Figure 17: GSM - Module Configuration for Sync Hub Slave shows exemplary settings for Sync Hub Slave.

Issue: 06

DN09172017

35


5

g

36


Figure 16

GSM - Module Configuration for Sync Hub Master

Figure 17

GSM - Module Configuration for Sync Hub Slave

Proceed to Local Sectors Settings. Note that the "Total max. Capacity" shows a value for both shared technologies. Figure 18: GSM - Local Sector Settings shows exemplary settings for LTE-2G RF Sharing. In the example, LTE uses 8 W per pipe out of available 60 W - the power left for GSM is 52 W, which allows for five TRXs with 10 W each.

DN09172017

Issue: 06



Figure 18

6

GSM - Local Sector Settings

Proceed to FRM External Alarm and Control Settings. Every Radio Module alarm can be commissioned for either or both of the two technologies. For example, if an alarm is commissioned for GSM, it is visible from the GSM side only.

7

Proceed to the last page - Site Commissioning File. Select Send SCF. Result The GSM System Module resets and the RF Sharing is activated.

3.3.1 Sync Hub related BSC MML commands to set right Sync Mode for GSM BTS Appendix for Sync Hub Slave configurations at BSC.

g

From the BSC perspective the synchronization to a SyncHub Master is seen as a kind of GPS sync source. The following Sync Hub related BSC MML commands can be executed to configure the right Sync Mode for a GSM BTS: For the GPS Sync, LMUA must be configured for GSM BTS with the recommended parameters listed in this section. ZEXA:LMUA=xxx:TRE65535,BCFXX:FNO=0,LTO=0,FMU=T,LTD=0;

BSC MML command ZEFM (MODIFY BASE CONTROL FUNCTION PARAMETERS):

ZEFM:XXX:CS=

Issue: 06

(XXX = BCF ID)

DN09172017

37


Table 2


Clock source (CS) parameter values

Parameter Value

Explanation , Usage

CS=

Location Measurement Unit,

LMU

select this if GPS Sync Source used in GSM with Packet Abis LAB

Location Measurement Unit with Abis recovery (LMU-ABIS), select this if GPS Sync Source and legacy Abis transport used in GSM

BSSTOP

Timing over Package Phase Synchronisation, select this if ToP Phase is used as Sync Source

NONE

Remove clock source, select this if TOPFREQ is used as Sync Source

Use SENA command to set right setting for Sync: ZEFM:XXX:SENA=

Table 3

(XXX = BCF ID)

SENA parameter values

Parameter Value

Explanation , Usage

SENA=

Synchronisation enabled,

T

select this if GPS using phase as Sync Source F

Synchronisation disabled, select this if GPS using frequency as Sync Source

Use ZEFO command to check right settings. Example: VALID SETTINGS FOR GPS PHASE CLOCK SOURCE .................(CS).... SYNCHRONIZATION ENABLED ......(SENA).. SYNCHRONIZATION MODE .........(SM).... EXTERNAL 1PPS SYNC SOURCE ....(EPPS).. VALID SETTINGS FOR TOP FREQUENCY CLOCK SOURCE .................(CS).... SYNCHRONIZATION ENABLED ......(SENA).. SYNCHRONIZATION MODE .........(SM).... EXTERNAL 1PPS SYNC SOURCE ....(EPPS)..

LMU T BSSSYNCH 3 (GPS RECEIVER) -F UNSYNCH 0 (DISABLED)

3.4 Recommissioning RF Sharing to change particular settings in Master technology Steps to recommission RF Sharing WCDMA-GSM or LTE-GSM to change particular Master technology BTS settings affecting Slave technology BTS. Purpose

38

DN09172017

Issue: 06



This section describes the procedure that must be followed when changing any of the following settings in RF Sharing WCDMA-GSM and LTE-GSM of the Master technology of already commissioned site. Changes in some of the WCDMA/LTE settings in Table 4: WCDMA/LTE settings forcing the GSM recommissioning must always be applied in GSM via (re)commissioning to ensure correct system level operation. The changes in some other settings are only needed for maintenance purposes that make it easier to troubleshoot any problems later on (the corresponding views are grayed out in GSM BTS Site Manager). Table 4

WCDMA/LTE settings forcing the GSM recommissioning WCDMA

LTE Concurrent Mode Settings Local Cell Resources - Antenna settings

Local Cell Resources - Carrier Power settings Local Cell Resources - MIMO settings WCDMA Carrier Candidates and Local Cell Group Settings - WCDMA carrier frequency (UARFCN)

LTE Carriers - Downlink (Tx) Carriers and LTE Bandwidth

Antenna Line Management* Antenna Line Settings* MHA settings* RET settings* * The corresponding views in GSM BTS Site Manager are grayed out.

1

Recommission WCDMA/LTE to change the settings. Select the target BTS and use the Reconfiguration option in WCMDA/LTE BTS Site Manager.

2

Click Send Parameters. Result WCDMA/LTE site resets.

3

Save the new WCDMA/LTE BTS SCF file to be used in GSM. Select File in the menu bar in WCDMA/LTE BTS Site Manager, choose Backup Commissioning Files... and save the BTS SCF file.

4

Recommission GSM using the WCDMA/LTE SCF. Use Change settings manually, go to Hardware Configuration view and browse the WCDMA/LTE SCF file. Check the settings in each window and click Send SCF button to complete the procedure. Result GSM BTS resets.

Issue: 06

DN09172017

39


5


Reset WCDMA/LTE BTS. Result WCDMA/LTE site, GSM site, and all RF Modules reset.

Result RF Sharing operates again using the new settings.

40

DN09172017

Issue: 06


Reverting RF sharing site to dedicated site

4 Reverting RF sharing site to dedicated site 4.1 Reverting RF sharing site to dedicated GSM site Steps to revert an existing GSM-WCDMA or GSM-LTE RF sharing site to a dedicated GSM site. Purpose Typical initial status:

•

GSM-WCDMA or GSM-LTE RF sharing site is working and both technologies are on air.

The purpose of this scenario is to convert the RF sharing site into a dedicated GSM site. This action must be done locally during the site visit. On completion GSM technology is on air and WCDMA/LTE is deactivated completely. Before starting, ensure that you have all the respective instructions to prepare the desired site.


Lock/block GSM and WCDMA/LTE and then turn off the power.

2

Physically remove the RP3-01 synchronization optical cable between the GSM System Module and the WCDMA/LTE System Module.

3

Physically remove the optical cables between the shared RFM and GSM System Module.

4

If RFM PWR cables are connected to the WCDMA/LTE System Module switch them to the GSM System Module.

5

Perform Undo commissioning in 2G BTS Site Manager.

6

Connect the optical cables for the new GSM-dedicated configuration.

7

Commission GSM with the new SCF. Optional: If the site was GSM-dedicated before the RF sharing deployment and, if you revert it to the original configuration (that is: the same RFMs/RRHs are used) you can use the old SCF. Result GSM is on air as a dedicated site. WCDMA or LTE is inactive

Post requisites

Issue: 06

DN09172017

41

Reverting RF sharing site to dedicated site


Before leaving the site, ensure that GSM technology is working properly without any unexpected alarms.

42

DN09172017

Issue: 06


Rx diversity sharing

5 Rx diversity sharing List of instructions and descriptions of RX diversity sharing.

5.1 Rx diversity sharing requirements Requirements and detailed information regarding Rx diversity sharing. The following RF Module (RFM) requirements have to be fulfilled to configure RX diversity sharing:

• • •

Only RFMs with "Rx Out" port can be used. Both RFMs operate in the same frequency band. Both GSM and WCDMA/LTE carriers are within the RFM's instantaneous BW.

Figure 19

Rx diversity sharing requirements 3GP

WCDMA/ LTE BTS

RFM instantaneous DL BW

P DL B W

DL filter center frequency

WCDMA/LTE

RFM 1

carrier

Frequency

2G BTS RFM 2 GSM TRXs

Frequency

Filter Tuning In case the RFM's instantaneous BW is narrower than the 3GPP band BW, the RF Module's filter may need a manual shift to meet the Rx diversity sharing requirements. In WCDMA and LTE BTS Site Manager it is possible to shift the DL filter and in 2G BTS Site Manager it is possible to shift the UL filter. The DL and UL band filters are coupled, so they are both shifted simultaneously.

Calculating GSM frequencies In a typical scenario, a GSM-dedicated BTS already exists on a site. WCDMA or LTE, with predefined carrier frequencies, is brought to the same site and existing antenna lines are used for both technologies with Rx diversity sharing. The GSM TRX frequencies are usually changed to accommodate the WCDMA/LTE carriers in the same band. Thus the available GSM ARFCNs have to be calculated. Example: calculating available ARFCNs, when FXDA RF Module (20 MHz Rx filter pass band BW) is used and the WCDMA uplink (Rx) center frequency is set to 905 MHz. 1. Calculate the lower and the higher Rx filter cutoff frequencies: [Rx center frequency] -/+ [Rx filter pass band BW]/2

Issue: 06

DN09172017

43



• •

lower frequency [MHz]: 905 - 20/2 = 895 higher frequency [MHz]: 905 + 20/2 = 915

2. The available ARFCN channel frequencies have to be greater than 895 MHz and lower than 915 MHz:

• •

the lowest ARFCN: 26 (895.2 MHz) the highest ARFCN: 124 (914.8 MHz)

In case of WCDMA, the GSM TRXs can overlap the edges of the WCDMA carrier BW the carrier frequencies have to be allocated at least 2 MHz away from the WCDMA carrier's center frequency. In case of LTE, the GSM TRXs have to be allocated outside the LTE carrier BW. For example, when LTE carrier BW is 10 MHZ, the GSM carrier frequencies have to be allocated at least 5.1 MHz away from the LTE carrier's center frequency. Figure 20

Carrier-TRX spacing rules (pictures not in scale) ≥ 2.0 MHz

≥ 2.0 MHz

GSM TRX center frequency


Frequency WCDMA carrier

WCDMA carrier center frequency

LTE carrier ≥ 0.5*BW + 0.1 MHz

GSM TRX

≥ 0.5*BW + 0.1 MHz



Frequency LTE carrier center frequency

Rx diversity cabling Rx diversity sharing requires two additional RF cables for each sector. Those cables connect the Rx Out port of the first RFM and Ant2/4/6 (Rx) port of the second RFM. A set of six cables (allowing for three sectors) is delivered in "RDSA Rx Diversity Sharing Kit 2m", sales code 472454A.

44

DN09172017

Issue: 06



Figure 21

Additional Rx diversity cables connection PWR NI Rx

ANT 6 Tx/Rx

ANT 5 Rx

ANT 5

ANT 4 Tx/Rx

ANT 3 Rx

ANT 2 Tx/Rx

ANT 3

ANT 1

ANT 1 Rx Out

EAC

OPT 1

Rx Out

Rx Out

Rx Out

Rx Out

OPT 2 OPT 3

Additional RX diversity cables Sector 3

PWR NI Rx

ANT 6 Tx/Rx

ANT 5 Rx

ANT 5

Sector 2

ANT 4 Tx/Rx

ANT 3 Rx

ANT 2 Tx/Rx

ANT 3 EAC

Sector 1

ANT 1

ANT 1 Rx Out OPT 1

OPT 2 OPT 3

Total uplink gain The BTS receiver expects a certain fixed total gain in the uplink (UL) path, regardless the configuration. The total gain at RX Diversity and RX Main have to be approximately equal (the difference have to be less than few dB). The internal LNA gain at both RX Main and RX Diversity paths is adjusted by the BTS, depending on the parameters set during the commissioning. In Rx diversity sharing, both paths have to be commissioned separately.

•

LNA in the Rx Main path: -

•

When there is no MHA nor other additional gain in the feeder lines: the LNA gain is set to high, to optimize the Rx sensitivity. When there is an MHA or other additional gain in the feeder lines: the LNA gain is adjusted by the BTS SW according to the values set during the commissioning.

LNA in the Rx Diversity path: The LNA gain is set to low as the signal is already amplified by the other RFM. The eventual gain of an MHA is also taken into account by the other RFM.

The additional gain seen by the receiving RFM equals +28 dB (+29 dB from Rx Out port - 1 dB for Rx diversity cable loss).

Issue: 06

DN09172017

45



Figure 22

Rx diversity signal paths Antenna

Low gain set by BTS

Total gain at RX Diversity and RX Main is approximately the same

Bias-T

LNA

ANT2 Rx

RX filter

RX Diversity

Optional MHA MHA

RF block

LNA

RX filter

RX Main

ANT1 Rx Out Bias-T

VSWR Det

TX RX

ANT1 Tx/Rx

TX filter

P A

MHA

LNA1 LNA2

RFM 1 Rx diversity cables 1 dB cable loss No MHA: High gain set by BTS MHA: gain adjusted by BTS

Gain at Rx Out is +29 dB

Bias-T

LNA

ANT2 Rx

RX filter

RX Diversity

ANT1 Rx Out

LNA

RF block

RX filter

RX Main

Bias-T

VSWR Det

TX

TX RX

P A

ANT1 Tx/Rx

filter

RFM 2

5.2 Commissioning WCDMA or LTE to RX diversity sharing Steps to commission WCDMA or LTE to RX diversity sharing Initial status The site is prepared for RX diversity sharing - the cabling is done and BTS Site Manager connection to the SMs is established. The commissioning procedure is the same as in the dedicated mode, except for the additional steps described in this section. The pictures in this section show the WCDMA Site Manager, but the same steps are applicable for LTE as well.

1

Start the commissioning. Select Commissioning, Target: BTS, Commissioning type:

46

DN09172017

Issue: 06



• • 2

if the BTS has not been commissioned: Template/Manual if the BTS has been already commissioned: Reconfiguration

Proceed to Local Cell Resources (WCDMA) or Cell Resources (LTE). Set three 1TX/2RX sectors. Figure 23

3

RX diversity sharing: WCDMA - Local Cell Resources

Proceed to WCDMA Carrier Candidates and Local Cell Group Settings (WCDMA) or LTE Carriers (LTE). Select the appropriate UARFCN/EARFCN value and Bandwidth (for LTE). The RNC automatically sets the RFM's filter position during cell setup process. If the RFM's instantaneous bandwidth (BW) is narrower than the 3GPP BW, it is recommended to tick the Override nominal frequency check box and set the center frequency.

Issue: 06

DN09172017

47



The allowed values are calculated (in MHz) as follows:

g

• •

The lowest value: 3GPP Band start frequency + 1/2*RFM's UL filter BW The highest value: 3GPP Band stop frequency - 1/2*RFM's UL filter BW

Example: FXDA (900 MHz) RFM has 20 MHz UL filter BW, the center frequency tuning range is shown in Table 5: Example of manual filter tuning (FXDA). Table 5 Example of manual filter tuning (FXDA) DL start UL start DL stop UL stop frequency [MHz] frequency [MHz] frequency [MHz] frequency [MHz] 900 MHz band frequency range

92 5

880

960

915

Manual tuning range of FXDA UL filter center frequency

935 (925 + 10)

890 (880 + 10)

950 (960 - 10)

905 (915 - 10)

Figure 24

g

RX diversity sharing: WCDMA - Carrier settings

Steps Proceed to Antenna Line Management. and Proceed to AISG MHA Settings. are required only when WCDMA or LTE provides power to MHAs and controls them. 4

Proceed to Antenna Line Management. Tick the DC voltage check box for the antenna ports in which the MHAs are used. Figure 25

48

RX diversity sharing: WCDMA - Antenna Line Management

DN09172017

Issue: 06



5

Proceed to AISG MHA Settings. Assign the first LNA to This BTS and the second LNA to Other BTS as it is used by GSM.

Issue: 06

Figure 26

RX diversity sharing: WCDMA - AISG MHA Settings: LNA1

Figure 27

RX diversity sharing: WCDMA - AISG MHA Settings: LNA2

DN09172017

49



6

Proceed to Antenna Line Settings. Use regular, site-specific values and settings on TX antenna ports (ANT1, ANT3, and ANT 5). For RX antenna ports (ANT2, ANT4, and ANT6) use the following modifications when using Nokia RDSA cables:

• • • •

Set Feeder loss to "0" Set Additional RX gain to "28" Set Uplink delay to "10" RTT measurements are done as usual, based on the site-specific conditions. There are no special requirements because of RX diversity sharing.

Figure 28

7

RX diversity sharing: WCDMA - Antenna Line Settings - RX antenna modifications

Proceed to the last page - Send Parameters. Select the appropriate Send option:

• •

if the WCDMA/LTE BTS has not been commissioned: All parameters if the WCDMA/LTE BTS has been already commissioned: Only changes

Click Save Parameters, if needed, then Send Parameters. Figure 29

WCDMA - Send Parameters

In the commissioning report check if the parameters are set correctly. This can also be checked in Site Information, after the commissioning. Result

50

DN09172017

Issue: 06



The SM gets reset and the RX diversity sharing is ready from WCDMA/LTE side. 8

Check the BTS Hardware view (the main Site Manager view) Ensure there are no unexpected alarms.

Post requisites If WCELs must be kept locked after commissioning due to, for example, missing operating license (or WCELs are not yet created in RNC), the RFM filters will not tune into expected positions. This can cause RSSI problems in GSM as it receives Rx Div signal via WCDMA RFMs. To avoid this problem, select Tests -> Enter BTS Test State menu item and select test model 2 temporarily to enable RFM filter tuning. This can also be done remotely provided the O&M link is up and running.

5.3 Commissioning GSM to RX diversity sharing Steps to commission GSM to RX diversity sharing Initial status The site is prepared for RX diversity sharing - the cabling is done and BTS Site Manager connection to the SMs is established. The commissioning procedure is the same as in the dedicated mode, except for the additional steps described in this section.

1

Start the commissioning. Select Commissioning Wizard, Change settings manually

2

Proceed to Antenna Settings. a) For TX antenna ports (ANT1, ANT3, and ANT5) Use regular, site-specific values and settings. If the UL (Rx) bandwidth (BW) of the used RF Module is narrower than 3GPP BW, it is recommended to tune the filter manually. The filter tuning is done by setting the "Distance of beginning of filter band from lower frequency" parameter (in MHz, granularity 0.1) as in Figure 30: RX diversity sharing: GSM - Antenna Line Settings - TX (example).

g

The UL and DL filters are coupled, thus setting UL filter also shifts the DL filter. The allowed values (in MHz) are calculated as follows:

• •

The lowest value: "0.0" The highest value: 3GPP band UL BW - RFM UL filter BW

Example: FXDA (900 MHz) RFM has 20 MHz UL filter BW, the 900 MHz EGSM band's BW is 35 MHz. The highest allowed parameter value: 15 MHz (35 MHz 20 MHz). If an MHA is used (and controlled by the other technology), set the parameters as listed:

Issue: 06

DN09172017

51



• • • • • •

Feeder voltage - set to "0". Feeder loss - use site-specific value. MHA type - select "Non-AISG 2.0 MHA". Product type - select the correct MHA type, or choose "Other" if your MHA is not on the list. Serial number - optional field for entering the MHA's serial number manually. Alarm threshold - enter the MHA's alarm threshold manually.

Figure 30

RX diversity sharing: GSM - Antenna Line Settings - TX (example)

b) For RX antenna ports (ANT2, ANT4, and ANT6) Tick the Additional Rx Gain check box and set the value to "28", when using Nokia RDSA cables. Figure 31

RX diversity sharing: GSM - Antenna Line Settings - RX

c) For Flexi Compact

g

52

This step is valid for GFC until GFC1 EP2.

DN09172017

Issue: 06



Additional RX gain has to be set as a virtual MHA. When using RDSA cables, set the parameters as listed:

• • • • • •

Feeder voltage - set to "0". Feeder loss - set to "0". MHA type - select "AISG 2.0 MHA". Product type - select Other". Gain - set to "28". Product code - mandatory field, though you can fill in any value.

Figure 32

3

RX diversity sharing: GSM - Antenna Line Settings - RX - for Flexi Compact

Proceed to the last page - Site Commissioning File. Click Send SCF. Result The SM gets reset and the RX diversity sharing is ready from GSM side.

5.4 LTE-GSM RF sharing with Rx diversity sharing (Ptype configuration) Description of a special configuration (type P) for LTE-GSM.

Issue: 06

g

This section is valid for EX5.1 3.1.0 onwards. This SW release allows to commission either one, two or three cells, the previous SW releases allow to configure only three cells.

g

If P-type configuration is used with MHA, it requires LN7.0 1.2 (or later).

DN09172017

53



The configuration allows for up to 1+1+1 LTE 20 MHz MIMO and up to 4+4+4 GSM with FXEA variant A.203 RF Module. As FXEA RF Module (RFM) can allocate a total of 20 MHz uplink (UL) LTE signal in each pipe, it cannot transmit the GSM signal simultaneously. That is why the LTE and GSM resources have to be assigned to separate pipes. In such case the additional Rx diversity sharing cables have to be connected, to provide Rx Div signal to the other technology-dedicated pipes. The configuration with resources allocation is shown in Figure 33: P-type configuration for LTE FSME with resource allocation. In the downlink (DL), full 25 MHz BW can be used to transmit both LTE and GSM simultaneously in the same pipe.

g

Note that when type P configuration is commissioned:

• •

GSM cannot support additional GSM-dedicated RFMs. TRX Tests in 2G cannot be run.

Figure 33

P-type configuration for LTE FSME with resource allocation Pipes Pipes commissioned commissioned to LTE to GSM

GSM SM PWR NI Rx

Tx/Rx

Rx

In

EAC

Q1

Tx/Rx

Rx

ANT 6 ANT 5 Tx/Rx FPA OPT OPT

ANT 5

ANT 4

ANT 3

ANT 2

OPT OPT LMP

PWR

PWR

PWR

PWR

PWR

ANT 1 Rx Out

EAC

OPT 1

Sector 3

ANT 1

Sync-Out Sync-

ANT 3 Rx Out

Sector 2

Rx Out

OPT 2 OPT 3

Sector 1

LTE FSME SM PWR NI Rx

ANT 6 Tx/Rx

ANT 5

ANT 5 Rx

ANT 4 Tx/Rx

ANT 3 Rx

ANT 2 Tx/Rx

ANT 3 Rx Out EAC

54

DN09172017

ANT 1

ANT 1 Rx Out OPT 1

Rx Out

OPT 2 OPT 3

Issue: 06



Figure 34

P-type configuration for LTE FSMF with resource allocation Pipes Pipes commissioned commissioned to GSM to LTE

GSM SM PWR NI Rx

Tx/Rx

Sync-In

Rx

EAC

Tx/Rx

Q1

Rx

ANT 6 ANT 5 Tx/Rx FPA OPT

OPT

ANT 5

ANT 4

ANT 3

ANT 2

OPT OPT LMP

PWR

PWR

PWR

PWR

PWR

ANT 1 Rx OutRx Out

EAC

OPT 1

Sector 3

ANT 1

Sync-Out

ANT 3

Sector 2

Rx Out

OPT 2 OPT 3

Sector 1

LTE FSMF SM PWR NI Rx

ANT 6 Tx/Rx

ANT 5 Rx

ANT 5

ANT 4 Tx/Rx

ANT 3 Rx

ANT 2 Tx/Rx

ANT 3 EAC

ANT 1

ANT 1 Rx OutRx Out OPT 1

Rx Out

OPT 2 OPT 3

5.4.1 Commissioning type P configuration in LTE Steps to commission configuration type P in LTE. Purpose

g

If P-type configuration is used with MHA, it requires LN7.0 1.2 (or later). Initial status The site is prepared for RX diversity sharing - the cabling is done and BTS Site Manager connection to the System Modules (SM) is established. The commissioning procedure is the same as in the dedicated mode, except for the additional steps described in this section.

1

Start the commissioning. Select Commissioning, Target: BTS, Commissioning type:

• • 2

if the BTS has not been commissioned: Template/Manual if the BTS has been already commissioned: Reconfiguration

Proceed to Concurrent Mode Settings. Tick the "RF sharing enabled" check box, choose "LTE-2G" as the shared technologies, enter the product code and serial number of the GSM SM, and tick both FXEA RF Modules (RFMs) as shared.

Issue: 06

DN09172017

55



Figure 35

3

P-type LTE - LTE Concurrent Mode Settings

Proceed to Cell Resources. Configure one, two or three cells and assign the TXs and RXs as shown in Figure 36: P-type LTE - Cell Resources, select "Dynamic Open Loop MIMO" and the appropriate Carrier power.

56

DN09172017

Issue: 06



Figure 36

4

P-type LTE - Cell Resources

Proceed to LTE Carriers Select 20 MHz Bandwidth for each cell.

Issue: 06

DN09172017

57



Figure 37

5

P-type LTE - LTE Carriers

(Optional) Configure the MHAs appropriately, if they are used a) Proceed to Antenna Line Management Ensure that 3GPP/AISG communication and DC Voltage are enabled for all antenna ports having the MHAs. b) Proceed to AISG MHA Settings Select the appropriate Antenna from the pull-down menu.

6

Proceed to Antenna Line Settings Use regular, site-specific values and settings on TX antenna ports (ANT1, ANT3, and ANT 5 on both FXEAs). For the used RX antenna ports (FXEA 1.1.1: ANT2 and ANT6, FXEA 1.2.1: ANT4) use the following modifications when using Nokia RDSA cables:

• • •

Set Total loss to "0" Set Additional RX gain to "28" Set Uplink delay to "0"

Figure 38

58

P-type LTE - Antenna Line Settings

DN09172017

Issue: 06



7

Proceed to Send Parameters a) Press Send Parameters to finish the commissioning. b) After commissioning is complete, choose File -> Backup Commissioning Files menu item and store the BTS SCF on your computer. The SCF is necessary for later GSM commissioning. Result All the commissioned LTE Cells go On Air with no unexpected alarms.

5.4.2 Commissioning type P configuration in GSM Steps to commission configuration type P in GSM. Purpose

g

This section is valid for EX5.1 3.1.0 onwards. Initial status The site is prepared for RX diversity sharing - the cabling is done and BTS Site Manager connection to the System Modules (SM) is established. The commissioning procedure is the same as in the dedicated mode, except for the additional steps described in this section.

1

Start the commissioning. Select Commissioning Wizard, Change settings manually

2

Proceed to Hardware Configuration. Select "Specify from file" and choose the LTE SCF, previously saved after the LTE commissioning.

3

Proceed to Local Sector Settings. Configure the sectors as shown in figures.

Issue: 06

DN09172017

59


60


Figure 39

P-type GSM - Local sector 1

Figure 40


DN09172017

Issue: 06



Figure 41

4


Proceed to Antenna line settings. Tick the check boxes as in figure.

g

Issue: 06

In this configuration the 29 dB Rx gain is taken into account automatically.

DN09172017

61

Rx diversity sharing Configu ring RF Sharing

Figure 42 Ptype GSM - Antenna line settings

5 Proceed to the last commissioning page and click Send SCF.Result Both LTE and GSM are On Air with no unexpect ed alarms.

62

DN09172017 Issue: 06

Appendix: I.

LTE Base Stations LTE Base Stations Supported Configurations Supported Configurations.zip

LTE Base Stations Supported Configurations.xls

Nokia LTE Integrating and Configuring

Recommend Documents