NetAct™ 16.8
Integrating Flexi Multiradio BTS LTE to
NetAct
DN09118114
Issue: 2-0
Integrating Flexi Multiradio BTS LTE to NetAct
Disclaimer
The information in this document applies solely to the hardware/software product (“Product”) specified herein, and only as
specified herein.
This document is intended for use by Nokia Solutions and Networks' customers (“You”) only, and it may not be used except
for the purposes defined in the agreement between You and Nokia Solutions and Networks (“Agreement”) under which this
document is distributed. No part of this document may be used, copied, reproduced, modified or transmitted in any form
or means without the prior written permission of Nokia Solutions and Networks. If you have not entered into an Agreement
applicable to the Product, or if that Agreement has expired or has been terminated, You may not use this document in any
manner and You are obliged to return it to Nokia Solutions and Networks and destroy or delete any copies thereof.
The document has been prepared to be used by professional and properly trained personnel, and You assume full
responsibility when using it. Nokia Solutions and Networks welcome Your comments as part of the process of continuous
development and improvement of the documentation.
This document and its contents are provided as a convenience to You. Any information or statements concerning the
suitability, capacity, fitness for purpose or performance of the Product are given solely on an “as is” and “as available” basis
in this document, and Nokia Solutions and Networks reserves the right to change any such information and statements
without notice. Nokia Solutions and Networks has made all reasonable efforts to ensure that the content of this document is
adequate and free of material errors and omissions, and Nokia Solutions and Networks will correct errors that You identify
in this document. But, Nokia Solutions and Networks' total liability for any errors in the document is strictly limited to the
correction of such error(s). Nokia Solutions and Networks does not warrant that the use of the software in the Product will be
uninterrupted or error-free.
N O WA RRAN T Y OF AN Y KI ND , EI T HER E X P R E S S OR I M P L I E D , I N C L U D I N G B U T N O T L I M I T E D
TO A NY WAR RA NT Y OF AVAI LABI LIT Y, AC CU RA C Y, R E L I A B I L I T Y, T I T L E , N O N - I N F R I N G E M E N T,
M ER C HANTA BI LI T Y OR F IT N ESS F OR A PA RT IC UL A R P U R P O S E , I S M A D E I N R E L AT I O N TO T H E
C ONT ENT O F TH IS DO CU M EN T. IN N O E V E N T W I L L N O K I A S O L U T I O N S A N D N E T W O R K S B E
L IA BLE F O R AN Y DA M A GES, I NC LUD IN G B U T N OT L I M I T E D TO S P E C I A L , D I R E C T, I N D I R E C T,
I NC I DENTAL OR CO NS EQ UEN T IAL OR AN Y L OS S E S , S U C H A S B U T N O T L I M I T E D TO L O S S O F
PRO FI T, RE VEN UE , BU SI 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
ARI SE FRO M T H E US E O F T H IS DO CU M E N T O R T HE I N F O R M AT I O N I N I T, E V E N I N T H E C A S E O F
ERR O RS I N OR OM I SSI ON S F RO M T H IS DO CU M E N T O R I T S C O N T E N T.
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 © 2016 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.
Integrating Flexi Multiradio BTS LTE to NetAct
Table of Contents
Contents
1 Overview of Flexi Multiradio BTS LTE integration.......................................................................................5
1.1
1.2
1.3
1.4
1.5
Integration solution.................................................................................................................................... 5
Relationship between Flexi Multiradio BTS LTE and other network elements......................................... 5
Compatibility information........................................................................................................................... 6
Integration process..................................................................................................................................10
Network connection.................................................................................................................................11
2 Preparing LTE iOMS and Flexi Multiradio BTS LTE.................................................................................. 13
2.1 Preparing LTE iOMS............................................................................................................................... 13
2.1.1 Configuring heartbeat interval for LTE iOMS................................................................................. 14
2.1.2 Configuring LTE iOMS TLS modes................................................................................................ 15
2.1.3 Checking system ID of LTE iOMS................................................................................................. 16
2.1.4 Adding LB WAS entry to LTE iOMS host file................................................................................. 16
2.2 Preparing Flexi Multiradio BTS LTE....................................................................................................... 18
2.2.1 Checking IP connectivity between Flexi Multiradio BTS LTE and LTE iOMS.................................18
3 Preparing NetAct........................................................................................................................................... 20
3.1 Managing NetAct user for Flexi Multiradio BTS LTE integration engineer............................................. 21
3.2 Checking NetAct licenses....................................................................................................................... 22
3.3 Deploying NetAct fast pass (formerly INES) compatible metadata........................................................ 23
3.4 Enabling pre-aggregation........................................................................................................................ 25
3.5 Managing the Maintenance Region........................................................................................................ 25
3.6 Adding Flexi Multiradio BTS LTE and LTE iOMS to Domain Name Service in NetAct........................... 26
3.7 Checking NetAct connectivity towards LTE iOMS.................................................................................. 26
3.8 Checking NetAct connectivity towards Flexi Multiradio BTS LTE...........................................................27
3.9 Managing Flexi Multiradio BTS LTE credentials.....................................................................................28
3.9.1 Checking Flexi Multiradio BTS LTE credentials............................................................................. 29
3.9.2 Creating Flexi Multiradio BTS LTE credentials...............................................................................30
3.10 Preparing applications for Element Management.................................................................................31
3.10.1 Installing Application Launcher in Node Manager Citrix Virtual Delivery Agent (VDA) server..... 32
3.10.1.1 Downloading LTE iOMS Application Launcher installer....................................................... 32
3.10.1.2 Installing and configuring Application Launcher...................................................................33
3.10.2 Configuring Parameter Tool in Application Launcher................................................................... 35
3.10.3 Installing BTS Site Manager in Node Manager Citrix Virtual Delivery Agent (VDA) server.......... 36
3.10.4 Downloading Element Management Launch scripts.................................................................... 37
3.10.5 Preparing for ADMIN of LTE BTS................................................................................................ 37
3.10.6 Configuring OMS Element Manager............................................................................................ 39
4 Preparing the intermediate system............................................................................................................. 40
4.1 Setting up firewall rules.......................................................................................................................... 40
4.2 Configuring SOCKS proxy service..........................................................................................................46
5 Integrating Flexi Multiradio BTS LTE to NetAct with NEIW...................................................................... 47
3
Integrating Flexi Multiradio BTS LTE to NetAct
Table of Contents
5.1 Integration operations in NEIW...............................................................................................................47
6 Integrating Flexi Multiradio BTS LTE to NetAct manually........................................................................ 50
6.1 Integration operations on OMS...............................................................................................................50
6.1.1 Configuring DNS forwarder on LTE iOMS..................................................................................... 50
6.1.2 Configuring LTE iOMS time synchronization with NetAct...............................................................50
6.2 Integration operations on NetAct............................................................................................................ 51
6.2.1 Creating managed objects for LTE iOMS in NetAct.......................................................................51
6.2.2 Associating managed objects to a Maintenance Region............................................................... 53
6.2.3 Executing integration data upload.................................................................................................. 53
6.2.4 Uploading Flexi Multiradio BTS LTE alarms...................................................................................54
7 Operations on NetAct after integration.......................................................................................................56
7.1 Associating maintenance region with MRBTS and LNBTS.................................................................... 56
7.2 Provisioning Flexi Multiradio BTS LTE credentials in Network Element Access Control........................ 57
7.3 Executing Configuration Management upload........................................................................................ 58
8 Verifying Flexi Multiradio BTS LTE integration.......................................................................................... 60
8.1 Verifying Element Management connectivity.......................................................................................... 60
8.1.1 Verifying Element Management connectivity of LTE iOMS............................................................ 60
8.1.2 Verifying Element Management connectivity of Flexi Multiradio BTS LTE..................................... 61
8.2 Verifying Fault Management connectivity............................................................................................... 63
8.3 Verifying Performance Management connectivity...................................................................................64
8.4 Verifying Configuration Management connectivity.................................................................................. 66
9 Using management functions for Flexi Multiradio BTS LTE.....................................................................67
10 Removing integration of LTE network elements from NetAct................................................................ 68
10.1 Removing Flexi Multiradio BTS LTE integration from NetAct............................................................... 68
10.2 Removing integration of both LTE iOMS and Flexi Multiradio BTS LTE from NetAct........................... 70
11 Troubleshooting integration problems......................................................................................................74
11.1
11.2
11.3
11.4
11.5
11.6
NEIW execution errors.......................................................................................................................... 74
Integration data upload failure.............................................................................................................. 74
Element Managements of Flexi Multiradio BTS LTE not launched.......................................................76
Alarms from Flexi Multiradio BTS LTE not received............................................................................. 76
Performance data of Flexi Multiradio BTS LTE not found.................................................................... 77
Configuration Management upload failure............................................................................................ 78
12 Upgrading integration for LTE network elements....................................................................................79
13 Migrating AoM plans and templates......................................................................................................... 81
13.1 Migrating AoM plans............................................................................................................................. 81
13.2 Migrating AoM templates...................................................................................................................... 82
4
Integrating Flexi Multiradio BTS LTE to NetAct
Overview of Flexi Multiradio BTS LTE integration
1 Overview of Flexi Multiradio BTS LTE integration
This section describes the compatibility information between Flexi Multiradio BTS LTE and NetAct,
integration work flow, and network connection.
Before integration, you must have basic knowledge of:
• Flexi Multiradio BTS LTE
• LTE iOMS
• Nokia NetAct™
• User Management plan
• Network Management plan
• network topology
• network protocols used
• interfaces involved
1.1 Integration solution
Before integration, ensure that Flexi Multiradio BTS LTE is commissioned and integrated to LTE iOMS.
By integrating LTE iOMS to NetAct, Flexi Multiradio BTS LTE is integrated to NetAct automatically.
Note: For information on integrating and configuring Flexi Multiradio BTS LTE to LTE
iOMS, see the Commissioning Flexi Multiradio BTS LTE document (DN0951893) in Nokia
Networks Online Services (NOLS). Accessing NOLS requires authentication. This document
has several versions depending on the network element release. Refer to the version
corresponding to the network element release.
1.2 Relationship between Flexi Multiradio BTS LTE and other network
elements
Relationship between Flexi Multiradio BTS LTE and SBTS
SBTS shares some LTE performance management measurements.
• For the introduced impact on Performance Manager, see Performance management.
• For the introduced impact on Object Information Browser, see Searching Single RAN data in
Object Information Browser.
DN09118114 2-0
© 2016 Nokia Solutions and Networks
5
Integrating Flexi Multiradio BTS LTE to NetAct
Overview of Flexi Multiradio BTS LTE integration
Relationship between Flexi Multiradio BTS LTE and Cloud BTS
Cloud BTS shares some LTE performance management measurements. For those shared
measurements and their corresponding objects and counters, the supported CBTS release information
is contained in the Note column of the NOKLTE adaptation in Object Information Browser.
1.3 Compatibility information
The following tables show information on the compatibility between NetAct and network element
releases and also show the corresponding adaptation versions. Adaptation identifier is in the format of
<Adaptation name>-<Adaptation version>.
Radio network release
RL60
Supported network element
version
LN6.0
Adaptation identifier in NetAct
NOKLTE-LN6.0
NOKLTE-LN6.0.man
RL45
LNT4.0
NOKLTE-LNT4.0
NOKLTE-LNT4.0.man
RL70
LN7.0
NOKLTE-LN7.0
NOKLTE-LN7.0.man
RL70 FZM
LNF7.0
NOKLTE-LNF7.0
NOKLTE-LNF7.0.man
RL55
LNT5.0
NOKLTE-LNT5.0
NOKLTE-LNT5.0.man
RL55 FZM
LNZ5.0
NOKLTE-LNZ5.0
NOKLTE-LNZ5.0.man
FDD-LTE 15A
FL15A
NOKLTE-FL15A
NOKLTE-FL15A.man
FLF15A
NOKLTE-FLF15A
NOKLTE-FLF15A.man
TD-LTE 15A
TL15A
NOKLTE-TL15A
NOKLTE-TL15A.man
TLF15A
DN09118114 2-0
© 2016 Nokia Solutions and Networks
NOKLTE-TLF15A
6
Integrating Flexi Multiradio BTS LTE to NetAct
Radio network release
Overview of Flexi Multiradio BTS LTE integration
Supported network element
version
Adaptation identifier in NetAct
NOKLTE-TLF15A.man
FDD-LTE 16
FL16
NOKLTE-FL16
NOKLTE-FL16.man
FLF16
NOKLTE-FLF16
NOKLTE-FLF16.man
TD-LTE 16
TL16
NOKLTE-TL16
NOKLTE-TL16.man
TLF16
NOKLTE-TLF16
NOKLTE-TLF16.man
FDD-LTE 16A
FL16A
NOKLTE-FL16A
NOKLTE-FL16A.man
FLF16A
NOKLTE-FLF16A
NOKLTE-FLF16A.man
TD-LTE 16A
TL16A
NOKLTE-TL16A
NOKLTE-TL16A.man
TLF16A
NOKLTE-TLF16A
NOKLTE-TLF16A.man
Table 1: NetAct and Flexi Multiradio BTS LTE compatibility information
Note: From LTE 16A onwards, the adaptations of Flexi Multiradio BTS LTE are visible after
deploying NetAct fast pass (formerly INES) compatible metadata. For more information, see
Deploying NetAct fast pass (formerly INES) compatible metadata on page 23.
Radio network release
RL60
Supported network element
version
LTO6.0
Adaptation identifier in NetAct
NOKGOMS-LTO6.0
NOKGOMS-LTO6.0.man
RL45
LTO6.0
NOKGOMS-LTO6.0
NOKGOMS-LTO6.0.man
DN09118114 2-0
© 2016 Nokia Solutions and Networks
7
Integrating Flexi Multiradio BTS LTE to NetAct
Radio network release
RL70
Overview of Flexi Multiradio BTS LTE integration
Supported network element
version
LTO7.0
Adaptation identifier in NetAct
NOKGOMS-LTO7.0
NOKGOMS-LTO7.0.man
RL70 FZM
LTO7.0
NOKGOMS-LTO7.0
NOKGOMS-LTO7.0.man
RL55
LTO7.0
NOKGOMS-LTO7.0
NOKGOMS-LTO7.0.man
RL55 FZM
LTO7.0
NOKGOMS-LTO7.0
NOKGOMS-LTO7.0.man
FDD-LTE 15A
LTO15A
NOKGOMS-LTO15A
NOKGOMS-LTO15A.man
TD-LTE 15A
LTO15A
NOKGOMS-LTO15A
NOKGOMS-LTO15A.man
FDD-LTE 16
LOMS16
NOKGOMS-LOMS16
NOKGOMS-LOMS16.man
TD-LTE 16
LOMS16
NOKGOMS-LOMS16
NOKGOMS-LOMS16.man
FDD-LTE 16A
LOMS16A
NOKGOMS-LOMS16A
NOKGOMS-LOMS16A.man
TD-LTE 16A
LOMS16A
NOKGOMS-LOMS16A
NOKGOMS-LOMS16A.man
Table 2: NetAct and LTE iOMS compatibility information
Compatibility information of Flexi Multiradio BTS LTE releases and NetAct
The supported network element releases and their corresponding supported management functions
and applications of NetAct are listed in the following table.
DN09118114 2-0
© 2016 Nokia Solutions and Networks
8
Integrating Flexi Multiradio BTS LTE to NetAct
Overview of Flexi Multiradio BTS LTE integration
LTE iOMS
Management functions and applications
BTS
TL16,
LN6.0, LN7.0,
LTO6.0,
LOMS16,
LTO7.0,
LTO15A
LOMS16A
LNT4.0, LNT5.0,
FL15A, TL15A,
LNF7.0, LNZ5.0,
TLF16,
FL16,
FLF16,
FL16A
TL16A,
TLF16A,
TLF15A, FLF15A
FLF16A
Management functions
Fault Management
Yes (NWI3)
Yes (NWI3)
Yes (NWI3)
Yes (NWI3)
Yes (NWI3)
Yes (NWI3)
Yes (NWI3)
Yes (NWI3)
Yes (NWI3)
Yes (NWI3)
No
No
Yes (NWI3)
Yes (NWI3)
Yes (NWI3)
Yes (NWI3)
Yes (NWI3)
Yes (NWI3)
Yes (NWI3)
Yes (NWI3)
Yes (NWI3)
Yes (NWI3)
Yes (NWI3)
Yes (NWI3)
Yes (NWI3)
Element Manage-
Yes (HTTP/
Yes (HTTP/
Yes (HTTP/HTTPS) Yes (HTTP/
Yes (HTTP/
ment launch (EM
HTTPS)
HTTPS)
Yes (NWI3)
Yes (NWI3)
No
No
(FM)
Configuration Management (CM)
Performance Management (PM)
Software Management (SWM)
Hardware Management (HWM)
HTTPS)
HTTPS)
Yes (NWI3)
Yes (NWI3)
Yes (NWI3)
No
Yes (NWI3)
Yes (NWI3)
Yes (NWI3)
No
No
No
No
launch)
Centralized Network Element
User Management
(CNUM)
Credential Provisioning
License Management (LIM)
Applications
Dynamic Adaptation No
No
No
No
No
Yes (NWI3)
Yes (NWI3)*
Yes (NWI3)*
Yes (NWI3)*
(DA)
NE Integration Wiz-
Yes (NWI3)
ard (NEIW)
DN09118114 2-0
© 2016 Nokia Solutions and Networks
9
Integrating Flexi Multiradio BTS LTE to NetAct
Overview of Flexi Multiradio BTS LTE integration
LTE iOMS
Management functions and applications
BTS
TL16,
LN6.0, LN7.0,
LTO6.0,
LNT4.0, LNT5.0,
LOMS16,
LTO7.0,
LTO15A
FL15A, TL15A,
LOMS16A
LNF7.0, LNZ5.0,
TLF16,
FL16,
FLF16,
FL16A
TL16A,
TLF16A,
TLF15A, FLF15A
Administration
No
No
No
FLF16A
Yes
Yes
IPv4 or IPv6
IPv4
of Measurement
(AoM)
Other
IP version
IPv4
IPv4 or IPv6
IPv4
Table 3: Supported network element versions, management functions and used southbound interfaces
Note: * NE Integration Wizard (NEIW) is done through LTE iOMS.
1.4 Integration process
The following flowchart shows the integration process.
Note:
Follow the order of the steps in this document to prevent any unwanted delays in integration.
DN09118114 2-0
© 2016 Nokia Solutions and Networks
10
Integrating Flexi Multiradio BTS LTE to NetAct
Overview of Flexi Multiradio BTS LTE integration
Figure 1: Integration process
1.5 Network connection
The following figure shows how Flexi Multiradio BTS LTE is connected to NetAct through DCN backbone after integration.
DN09118114 2-0
© 2016 Nokia Solutions and Networks
11
Integrating Flexi Multiradio BTS LTE to NetAct
Overview of Flexi Multiradio BTS LTE integration
Figure 2: Network connection
DN09118114 2-0
© 2016 Nokia Solutions and Networks
12
Integrating Flexi Multiradio BTS LTE to NetAct
Preparing LTE iOMS and Flexi Multiradio BTS LTE
2 Preparing LTE iOMS and Flexi Multiradio BTS LTE
This section describes how to prepare LTE iOMS and Flexi Multiradio BTS LTE for NetAct integration.
2.1 Preparing LTE iOMS
This section describes how to prepare LTE iOMS for NetAct integration.
The prerequisites for integrating LTE iOMS to NetAct are listed in the following table.
LTE iOMS requirements
Additional information
LTE iOMS is installed and commis-
Refer to the Installing and Commissioning LTE OMS document
sioned successfully
(DN0956464) in Nokia Networks Online Services (NOLS). Accessing
Services on LTE iOMS are started.
NOLS requires authentication. This document has several versions depending on the network element release. Refer to the version corresponding to the network element release. To perform checks after installation
and commissioning of iOMS, in the Installing and Commissioning LTE
OMS document, go to Integrating LTE OMS to the network → Performing checks after installation and commissioning of OMS.
The LTE iOMS release is supported See NetAct and LTE iOMS compatibility information.
by the current NetAct release.
IP address of LTE iOMS north-
Refer to the network management plan or contact your network element
bound interface
administrator.
The credentials on LTE iOMS need- The following credentials on LTE iOMS must be obtained.
ed for NetAct integration
• root
• Nemuadmin
Note: Nemuadmin is a default NWI3 credential that is
used when integrating network elements for the first time.
It is also used for accessing LTE iOMS using SSH, Webbased administration GUI, and Application Launcher. If
you want to create a new NWI3 credential, see Installing
and Commissioning LTE OMS document (DN0956464)
in Nokia Networks Online Services (NOLS). Accessing
NOLS requires authentication. This document has several
versions depending on the network element release. Refer to the version corresponding to the network element
release. The user name can be freely selected, but an
identical user name needs to be available in NetAct.
DN09118114 2-0
© 2016 Nokia Solutions and Networks
13
Integrating Flexi Multiradio BTS LTE to NetAct
Preparing LTE iOMS and Flexi Multiradio BTS LTE
Table 4: Preparation checklist for LTE iOMS
2.1.1 Configuring heartbeat interval for LTE iOMS
This section describes how to configure heartbeat interval for LTE iOMS.
The alarm system interchangeably raises and clears alarm 70246 ALARM SYSTEM HEARTBEAT after the expiration of each heartbeat interval. If the refreshing of the alarm does not occur, it indicates
that the alarm system is not working properly.
1. Using remote desktop connection, log in to the Node Manager Citrix Virtual Delivery Agent (VDA)
server as the <Domain name>\<Administrator account>.
2. Launch Application Launcher and provide the following information. You can use the default
Nemuadmin credential.
• Network Element: IP address of LTE iOMS northbound interface
• Login name: user name of the NWI3 credential
• Password: password of the NWI3 credential
For more information about Application Launcher, see Installing Application Launcher in Node
Manager Citrix Virtual Delivery Agent (VDA) server on page 32.
3. Double-click Parameter Tool.
Note: If the Parameter Tool is not visible in the Application Launcher, follow the
procedure in Configuring Parameter Tool in Application Launcher on page 35 to make
the Parameter Tool visible.
4. In the left application pane, under fsClusterId=ClusterRoot, expand fsFragmentId=AlarmMgmt
→ fsFragmentId=AlarmProcessors → fsAlarmProcessorId=AlarmProcessor1, and click
fsAlarmProcessorConfigurationId=Default.
5. In the right application pane, find the fsHeartbeatInterval attribute, and set the value of the
fsHeartbeatInterval attribute according to your needs. If there is no need to change the default
value, skip the next step.
• 300s = default
• 0s = disable heartbeat
Note: To ensure the heartbeat can be received normally from LTE iOMS to NetAct, the
value of the fsHeartbeatInterval attribute must be no more than 1200s.
6. Log in to LTE iOMS through SSH as the Nemuadmin user, and restart the alarm system by
entering:
fshascli -rn /AlarmSystem
DN09118114 2-0
© 2016 Nokia Solutions and Networks
14
Integrating Flexi Multiradio BTS LTE to NetAct
Preparing LTE iOMS and Flexi Multiradio BTS LTE
Expected outcome
/AlarmSystem is restarted successfully
2.1.2 Configuring LTE iOMS TLS modes
The section describes how to configure the TLS modes of LTE iOMS.
Prerequisites
To completely enable the TLS for secure file transfer, ensure the following:
• Certificates are installed on the network element.
For more information, see the Certificate management chapter of the LTE RAN O&M Security
document (DN0958798) in Nokia Networks Online Services (NOLS). Accessing NOLS requires
authentication. This document has several versions depending on the network element release.
Refer to the version corresponding to the network element release.
• Certificates are installed in NetAct to complete the Trust cycle and enable the Secure
Communication.
– NWI3 CM certificates
For more information, see Adding certificates for CM upload.
– NWI3 network element certificates
For more information, see Adding a network element certificate to the NWI3 mediation's truststore.
– NWI3-HTTP certificates
For more information, see Configuring the Tomcat NWI3-HTTP server.
To configure LTE iOMS TLS mode
1. Using remote desktop connection, log in to the Node Manager Citrix Virtual Delivery Agent (VDA)
server as the <Domain name>\<Administrator account>.
2. Launch Application Launcher and provide the following information. You can use the default
Nemuadmin credential.
• Network Element: IP address of LTE iOMS northbound interface
• Login name: user name of the NWI3 credential
• Password: password of the NWI3 credential
For more information about Application Launcher, see Installing Application Launcher in Node
Manager Citrix Virtual Delivery Agent (VDA) server on page 32.
3. Double-click Parameter Tool.
DN09118114 2-0
© 2016 Nokia Solutions and Networks
15
Integrating Flexi Multiradio BTS LTE to NetAct
Preparing LTE iOMS and Flexi Multiradio BTS LTE
Note: If the Parameter Tool is not visible in the Application Launcher, follow the
procedure in Configuring Parameter Tool in Application Launcher on page 35 to make
the Parameter Tool visible.
4. To find the TLSModeFT and TLSModeOM parameters in OMS, under fsClusterId=ClusterRoot,
expand fsFragmentId=OMS → omsFragmentId=System → omsFragmentId=Network →
omsFragmentId=TLS.
5. Set the value of the TLSModeFT or TLSModeOM parameter.
For more information about the possible values of the TLSModeFT or TLSModeOM parameter,
see the the LTE RAN O&M Security document (DN0958798) in Nokia Networks Online Services
(NOLS). Accessing NOLS requires authentication. This document has several versions depending on the network element release. Refer to the version corresponding to the network element release. In the document, go to Transport Layer Security (TLS) protocol.
2.1.3 Checking system ID of LTE iOMS
The system ID of LTE iOMS is used as the instance ID of the OMS object in NetAct.
Do the following to check the LTE iOMS system ID.
1. Log in to LTE iOMS through SSH as the Nemuadmin user, and then switch to the root user.
2. Check the OMS system ID by entering:
fsnwi3ctl -i | grep SYSTEM_ID
Expected outcome
GLB_SYSTEM_ID=NE-OMS-<OMS system ID>
An example output:
GLB_SYSTEM_ID=NE-OMS-2058
In the example output, NE-OMS-2058 indicates that the LTE iOMS system ID is 2058. In this case,
using 2058 as the instance ID of the OMS object in NetAct.
2.1.4 Adding LB WAS entry to LTE iOMS host file
This section describes how to add NetAct LB WAS entry to LTE iOMS host file.
DN09118114 2-0
© 2016 Nokia Solutions and Networks
16
Integrating Flexi Multiradio BTS LTE to NetAct
Preparing LTE iOMS and Flexi Multiradio BTS LTE
Note: This section is only needed for LTE iOMS whose IP address is IPv6. If the IP address
of the LTE iOMS to be integrated is IPv4, skip this section.
1. Log in to any NetAct VM as the omc user.
2. Get the FQDN of NetAct LB WAS Virtual IP by entering:
/opt/cpf/bin/cpf_list_lb_address.sh --lb was
Expected outcome
<FQDN of NetAct LB WAS Virtual IP>
3. Log in to one of the VMs on which the lb service is running as the omc user.
For information about how to locate the VM where a specific service is running, see Locating the
right virtual machine for a service.
4. Get the IP address of NetAct LB WAS Virtual IP by entering:
/opt/cpf/bin/cpf_host6.sh <FQDN of NetAct LB WAS Virtual IP>
Expected outcome
<FQDN of NetAct LB WAS Virtual IP> has IPv6 address <IP address of
NetAct LB WAS Virtual IP>
5. Log in to LTE iOMS as the Nemuadmin user, and then switch to the root user.
6. Open the /etc/hosts file, and add the IP address and FQDN of NetAct LB WAS Virtual IP in the
following format to the file. Then save the file.
<IP address of NetAct LB WAS Virtual IP> <FQDN of NetAct LB WAS Virtual
IP>
7. To ensure LTE iOMS host file contains the NetAct LB WAS entry even if LTE iOMS is restarted,
enter the following command:
fsdistribute –v /etc/hosts
Note:
• For more information, see the Command Line Interface Tools and Management
Scripts in LTE iOMS document (DN0962949) in Nokia Networks Online
Services (NOLS). Accessing NOLS requires authentication. This document
has several versions depending on the network element release. Refer to the
DN09118114 2-0
© 2016 Nokia Solutions and Networks
17
Integrating Flexi Multiradio BTS LTE to NetAct
Preparing LTE iOMS and Flexi Multiradio BTS LTE
version corresponding to the network element release. In that document, go to
Configuration management → fsdistribute.
• If any operation that affects the /etc/hosts file is performed, for example, LTE
iOMS upgrade or recovery, check if the IP address and FQDN of NetAct LB WAS
Virtual IP are still contained in the /etc/hosts file. If the IP address and FQDN do
not exist, add them to the /etc/hosts file following the instruction in this section.
2.2 Preparing Flexi Multiradio BTS LTE
This section describes how to prepare Flexi Multiradio BTS LTE for NetAct integration.
The prerequisites for integrating Flexi Multiradio BTS LTE to NetAct are listed in the following table.
Flexi Multiradio BTS LTE requirements
Additional information
Flexi Multiradio BTS LTE is
For information on integrating and configuring Flexi Multiradio BTS LTE to
installed and commissioned
LTE iOMS, see Autoconnection and Autoconfiguration phases in Configur-
successfully.
ing LTE eNB using Autoconnection and Autoconfiguration. The instructions
are also available in the Commissioning Flexi Multiradio BTS LTE document
(DN0951893) in Nokia Networks Online Services (NOLS). Accessing NOLS requires authentication. This document has several versions depending on the
network element release. Refer to the version corresponding to the network element release.
The Flexi Multiradio BTS LTE
release is supported by the
current NetAct release.
See NetAct and Flexi Multiradio BTS LTE compatibility information.
If the current Flexi Multiradio BTS LTE release version is not supported by NetAct, contact the system administrator for further investigation.
IP address of Flexi Multiradio
Refer to the network management plan or contact your network element adminBTS LTE northbound interface istrator. After you get the IP address of Flexi Multiradio BTS LTE northbound inInstance ID of Flexi Multiradio
terface, check whether it is IPv4 or IPv6.
BTS LTE
Credentials of Flexi Multiradio
The password of the default Nemuadmin user must be obtained for connecting
BTS LTE for integration
to Flexi Multiradio BTS LTE through BTS Site Manager.
Note: The default name and password may not apply to your
current environment. For more information, contact your network
element administrator.
Table 5: Preparation checklist for Flexi Multiradio BTS LTE
2.2.1 Checking IP connectivity between Flexi Multiradio BTS LTE and LTE iOMS
The section describes how to check IP connectivity between Flexi Multiradio BTS LTE and LTE iOMS.
DN09118114 2-0
© 2016 Nokia Solutions and Networks
18
Integrating Flexi Multiradio BTS LTE to NetAct
Preparing LTE iOMS and Flexi Multiradio BTS LTE
Prerequisites
Ensure that Internet Control Message Protocol (ICMP) is enabled between Flexi Multiradio BTS LTE
and LTE iOMS.
1. Log in to LTE iOMS through SSH. You may use the default user Nemuadmin.
2. Ping Flexi Multiradio BTS LTE by doing one of the following:
• If the IP address of Flexi Multiradio BTS LTE northbound interface is IPv4, ping Flexi Multiradio
BTS LTE by entering:
ping <IP address of Flexi Multiradio BTS LTE northbound interface> -c
5
• If the IP address of Flexi Multiradio BTS LTE northbound interface is IPv6, ping Flexi Multiradio
BTS LTE by entering:
ping6 <IP address of Flexi Multiradio BTS LTE northbound interface> c 5
Expected outcome
An example output:
64 bytes from <IP address>: icmp_seq=1 ttl=63 time=0.238 ms
64 bytes from <IP address>: icmp_seq=2 ttl=63 time=0.276 ms
64 bytes from <IP address>: icmp_seq=3 ttl=63 time=0.253 ms
64 bytes from <IP address>: icmp_seq=4 ttl=63 time=0.264 ms
64 bytes from <IP address>: icmp_seq=5 ttl=63 time=0.211 ms
--- <IP address> ping statistics --5 packets transmitted, 5 received, 0% packet loss, time 4000ms
...
If the connectivity does not work, contact the network element administrator for further investigation.
DN09118114 2-0
© 2016 Nokia Solutions and Networks
19
Integrating Flexi Multiradio BTS LTE to NetAct
Preparing NetAct
3 Preparing NetAct
This section describes how to prepare NetAct for Flexi Multiradio BTS LTE integration.
The prerequisites on NetAct are listed in the following table.
NetAct requirements
Additional information
NetAct installation is success-
See Running Preventive Health Check.
ful.
Understand NetAct node
See Node structure overview.
structure.
Obtain NetAct IP addresses
See Locating the right virtual machine for a service.
for a node (VM) on which a
certain service is running.
Obtain NetAct virtual IP ad-
See Identifying the relevant virtual machine.
dresses.
NetAct services are running.
See Understanding the status of a service from the smanager.pl command. If
any service is not started, contact the system administrator for further investigation.
Hardening of WebSphere application server (WAS)
• For LTE 15A and earlier releases, RC4 Ciphers are disabled by default.
You need to enable RC4 Ciphers before the integration. For more information, see Handling RC4 Ciphers.
• For LTE 16 onwards, RC4 Ciphers are enabled by default so no further action is needed.
NWI3 CM certificates are in-
For more information, see Adding certificates for CM upload.
stalled.
NWI3 network element certifi-
For more information, see Adding a network element certificate to the NWI3
cates are installed.
mediation's truststore.
NWI3-HTTP certificates are in- For more information, see Configuring the Tomcat NWI3-HTTP server.
stalled.
LDAP certificates are installed. For more information, see Managing certificates.
The root objects are created.
The root objects required by Flexi Multiradio BTS LTE integration are:
• MRC-<instance ID>
– Object class: MRC (MRC)
– Instance: Set the instance value according to the network management plan and ensure that the instance is unique.
Note:
– Make sure that the instance does not contain any of the
following characters: & < > ' "
DN09118114 2-0
© 2016 Nokia Solutions and Networks
20
Integrating Flexi Multiradio BTS LTE to NetAct
NetAct requirements
Preparing NetAct
Additional information
– Make sure that the instance does not contain more than 80
characters.
• PLMN-PLMN
– Object class: PLMN (PLMN)
– Instance: PLMN
For more information on how to create the objects, see Creating managed objects.
Table 6: Preparation checklist in NetAct
3.1 Managing NetAct user for Flexi Multiradio BTS LTE integration
engineer
This section provides the information needed for creating users for integration engineers in NetAct.
User for integration operations in NetAct Start Page
For integration operations in NetAct Start Page, the administrator must create a dedicated integration
user for integration engineers.
Assign the following default roles to the group to which the integration user belongs:
• NetAct - Administrator (only needed when NE Integration Wizard is involved)
• 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
Note: SM-Security Administration role grants the integration user the access to the
credentials in the Network Element Access Control application. Consider your
company security requirements and decide whether to assign this role to the integration
user.
To support Element Management launch from Node Manager, the integration user must be assigned
to at least a Node Manager user group. For more information, see Managing Node Manager users and
user groups.
DN09118114 2-0
© 2016 Nokia Solutions and Networks
21
Integrating Flexi Multiradio BTS LTE to NetAct
Preparing NetAct
For more information on how to manage users, see User Management Help.
For more information on how to manage permissions, see Permission Management Help.
Note: During the role-scope combination, Nokia recommends you to select only the needed
root objects listed in Preparing NetAct on page 20.
User for integration operations in VMs
Use the omc user for integration operations in VMs. When root access is needed, switch to the root
user and switch back to the omc user after the operation.
Customizing user plan
The roles of permission can be customized in NetAct.
If you have your own user management plan, manage users following the instructions in User Management Help and Permission Management Help.
3.2 Checking NetAct licenses
This section describes how to check NetAct licenses which authorize the integration.
The NetAct licenses enable you to create Flexi Multiradio BTS LTE managed objects.
1. Log in to the NetAct Start Page as the integration user.
a) Enter the following URL in the address field of your internet browser: https://
<system_FQDN>/startpage
<system_FQDN> is the fully qualified domain name of the NetAct cluster load balancer for
WebSphere. For more information, see Launching the NetAct Start Page.
b) Enter the Username and Password of the integration user on the NetAct login page, and click
Log In.
c) Click Accept to accept the terms and conditions.
2. Open the license file.
a) In NetAct Start Page, open License Manager by clicking Configuration → License Manager.
b) In License Manager, if the License Browser view is not open, click Licenses → License
Browser.
c) In License Browser, click the NetAct™ Software Licenses tab if it is not already selected.
d) Click the files in the License filename column.
3. Check if the feature code of the needed license is displayed.
DN09118114 2-0
© 2016 Nokia Solutions and Networks
22
Integrating Flexi Multiradio BTS LTE to NetAct
Preparing NetAct
Feature code
Feature name
3599
NetAct Radio LTE FD TD FZ standard SW
Table 7: Required license
Expected outcome
If the feature code is not displayed, contact the system administrator for further investigation.
3.3 Deploying NetAct fast pass (formerly INES) compatible metadata
This section describes how to deploy NetAct fast pass (formerly INES) compatible metadata for Flexi
Multiradio BTS LTE on NetAct.
Note: For LTE 16 and earlier releases which are already integrated to NetAct, if you need to
upgrade them to LTE 16A and onward releases, before upgrading, you must deploy NetAct
fast pass (formerly INES) compatible metadata on NetAct first.
From LTE 16A onwards, before integration, you must deploy NetAct fast pass (formerly INES) compatible metadata on NetAct using Adaptation Deployment Suite (ADS). For other releases, skip this section.
The following table lists the network element identifiers (<NE_type> and <NE_release>) of Flexi
Multiradio BTS LTE which are used during the deployment.
Network element (NE)
NE_type
Flexi Multiradio BTS LTE NOKLTE
NE_release
LTE16A
LTE 16A
Table 8: Network element identifiers of Flexi Multiradio BTS LTE
1. Log in to any NetAct VM where the generic_mediations service is running as the omc user.
2. Navigate to the /opt/oss/NOKIA-integrationmanager/bin/ directory by entering:
cd /opt/oss/NOKIA-integrationmanager/bin/
3. Deploy NetAct fast pass (formerly INES) compatible metadata for Flexi Multiradio BTS LTE by
entering:
sh ads_client.sh -nt <NE_type> -v <NE_release>
where <NE_type> and <NE_release> are identifiers of Flexi Multiradio BTS LTE.
For example:
DN09118114 2-0
© 2016 Nokia Solutions and Networks
23
Integrating Flexi Multiradio BTS LTE to NetAct
Preparing NetAct
sh ads_client.sh -nt NOKLTE -v LTE16A
Expected outcome
An example output:
2015-12-09 08:34:27,287 - [Deploying Adaptation NOKLTE + LTE16A ...]
2015-12-09 08:34:28,552 - [Adaptation Deployment started for [NOKLTE
+ LTE16A]]
2015-12-09 08:34:29,703 - [Deployment Status:STARTED]
2015-12-09 08:34:29,703 - [Adaptation [NOKLTE + LTE16A] deployment
is up and running background. You could check status via: " sh ads_
client.sh -nt NOKLTE -v LTE16A -q"]
Note:
• If the output indicates Deployment Status:DONE immediately after the
deployment is started, skip the following steps in this section. In this case, the NetAct
fast pass (formerly INES) compatible metadata for Flexi Multiradio BTS LTE has
been deployed successfully before integration.
• For Flexi Multiradio BTS LTE, the duration of the deployment is 1-2 hours.
4. Check the deployment status by entering:
sh ads_client.sh -nt <NE_type> -v <NE_release> -q
For example:
sh ads_client.sh -nt NOKLTE -v LTE16A -q
Expected outcome
The following is part of an example output:
<DeploymentStatus>
<status neRelease="LTE16A" neType="NOKLTE" ... status="done">
...
</status>
</DeploymentStatus>
<FragmentStatus
In the output, check the deployment status under <DeploymentStatus>.
• If it indicates status="done", the deployment is completed.
• If it indicates status="started", the deployment is ongoing. In this case, wait and
check the deployment status again. The duration of the deployment varies according to the
adaptation package size of the network element. Before the deployment is completed, do not
start the deployment for another network element. Otherwise, the newly started deployment
will not be executed by ADS.
DN09118114 2-0
© 2016 Nokia Solutions and Networks
24
Integrating Flexi Multiradio BTS LTE to NetAct
Preparing NetAct
• If it indicates status="failed", the deployment is failed. In this case, record the name of
the failed fragment, and go to Failed to deploy NetAct fast pass (formerly INES) compatible
metadata for possible causes and solutions.
5. If Monitor or Performance Manager is opened before deployment, relaunch the opened application
respectively.
3.4 Enabling pre-aggregation
This section describes how to enable pre-aggregation for LTE 16A.
This section is for LTE 16A only. For other Flexi Multiradio BTS LTE releases, skip this section.
1. Log in to the NetAct Start Page as the integration user.
a) Enter the following URL in the address field of your internet browser: https://
<system_FQDN>/startpage
<system_FQDN> is the fully qualified domain name of the NetAct cluster load balancer for
WebSphere. For more information, see Launching the NetAct Start Page.
b) Enter the Username and Password of the integration user on the NetAct login page, and click
Log In.
c) Click Accept to accept the terms and conditions.
2. In NetAct Start Page, open Performance Manager by clicking Reporting → Performance
Manager.
3. In Performance Manager, click Administration → Reporter Admin Toolkit.
4. In Reporter Admin Toolkit, click Administration of Aggregates.
5. For Flexi Multiradio BTS LTE, check the LNBTS-NSN LTE Base Transceiver Station adaptation
and ensure all the corresponding measurement types are enabled.
For the measurement types of the LNBTS-NSN LTE Base Transceiver Station adaptation which
are not enabled, enable the aggregation. For detailed instructions, see Administration of Aggregates.
3.5 Managing the Maintenance Region
This section describes how to check and create Maintenance Region in NetAct.
NetAct Maintenance Region (MR) is used to maintain a group of network elements which share the
credentials for accessing the network elements.
DN09118114 2-0
© 2016 Nokia Solutions and Networks
25
Integrating Flexi Multiradio BTS LTE to NetAct
Preparing NetAct
Check your network layout and the location of the Flexi Multiradio BTS LTE in the network layout.
Based on the location, place the Flexi Multiradio BTS LTE into an existing MR or create a new MR if
there is no MR which represents the area.
For more information on how to check or create an MR, see Creating maintenance region.
Note:
• Make sure that the instance ID of the maintenance region does not contain any of the
following characters: & < > ' "
• Make sure that the instance ID of the maintenance region does not contain more than 80
characters.
3.6 Adding Flexi Multiradio BTS LTE and LTE iOMS to Domain Name
Service in NetAct
This section describes how to add Flexi Multiradio BTS LTE and LTE iOMS to NetAct Domain Name
Service.
Note: This section is only needed for Flexi Multiradio BTS LTE and LTE iOMS whose IP
addresses are IPv4. If the IP addresses of the Flexi Multiradio BTS LTE and LTE iOMS to be
integrated are IPv6, skip this section.
Add the Flexi Multiradio BTS LTE and LTE iOMS northbound IP address(es) and the host name(s) to
the DNS zones in NetAct.
To make zone file management easy, Nokia recommends 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.
For detailed instructions on how to add Flexi Multiradio BTS LTE and LTE iOMS to Domain Name Service in NetAct, see Administering DNS in NetAct.
3.7 Checking NetAct connectivity towards LTE iOMS
This section describes how to check NetAct connectivity towards LTE iOMS.
Prerequisites
Ensure that Internet Control Message Protocol (ICMP) communication is allowed between the WAS
VM and LTE iOMS before performing this procedure.
1. Log in to the NetAct VM where the was service is running as the omc user.
2. Ping LTE iOMS by doing one of the following:
• If the IP address of LTE iOMS northbound interface is IPv4, ping LTE iOMS by entering:
DN09118114 2-0
© 2016 Nokia Solutions and Networks
26
Integrating Flexi Multiradio BTS LTE to NetAct
Preparing NetAct
ping <FQDN of LTE iOMS> -c 5
An example output:
PING <FQDN>(<IP address>) 56(84) bytes of data.
64 bytes from <FQDN>(<IP address>): icmp_seq=1 ttl=63 time=0.238
64 bytes from <FQDN>(<IP address>): icmp_seq=2 ttl=63 time=0.276
64 bytes from <FQDN>(<IP address>): icmp_seq=3 ttl=63 time=0.253
64 bytes from <FQDN>(<IP address>): icmp_seq=4 ttl=63 time=0.264
64 bytes from <FQDN>(<IP address>): icmp_seq=5 ttl=63 time=0.211
--- <FQDN> ping statistics --5 packets transmitted, 5 received, 0% packet loss, time 4000ms
...
ms
ms
ms
ms
ms
If the connectivity does not work, check the firewall settings. For more information, see Setting
up firewall rules on page 40.
• If the IP address of LTE iOMS northbound interface is IPv6, ping LTE iOMS by entering:
ping6 <IP address of LTE iOMS northbound interface> -c 5
An example output:
PING <IP address> 56(84) bytes of data.
64 bytes from <IP address>: icmp_seq=1 ttl=63 time=0.238 ms
64 bytes from <IP address>: icmp_seq=2 ttl=63 time=0.276 ms
64 bytes from <IP address>: icmp_seq=3 ttl=63 time=0.253 ms
64 bytes from <IP address>: icmp_seq=4 ttl=63 time=0.264 ms
64 bytes from <IP address>: icmp_seq=5 ttl=63 time=0.211 ms
--- <IP address> ping statistics --5 packets transmitted, 5 received, 0% packet loss, time 4000ms
...
If the connectivity does not work, check the firewall settings. For more information, see Setting
up firewall rules on page 40.
3.8 Checking NetAct connectivity towards Flexi Multiradio BTS LTE
This section describes how to check NetAct connectivity towards 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 any VM on which the was service is running as the omc user.
2. Ping Flexi Multiradio BTS LTE by doing one of the following:
DN09118114 2-0
© 2016 Nokia Solutions and Networks
27
Integrating Flexi Multiradio BTS LTE to NetAct
Preparing NetAct
• If the IP address of Flexi Multiradio BTS LTE northbound interface is IPv4, ping Flexi Multiradio
BTS LTE by entering:
ping <FQDN of Flexi Multiradio BTS LTE> -c 5
An example output:
PING <FQDN>(<IP address>) 56(84) bytes of data.
64 bytes from <FQDN>(<IP address>): icmp_seq=1 ttl=63 time=0.238
64 bytes from <FQDN>(<IP address>): icmp_seq=2 ttl=63 time=0.276
64 bytes from <FQDN>(<IP address>): icmp_seq=3 ttl=63 time=0.253
64 bytes from <FQDN>(<IP address>): icmp_seq=4 ttl=63 time=0.264
64 bytes from <FQDN>(<IP address>): icmp_seq=5 ttl=63 time=0.211
--- <FQDN> ping statistics --5 packets transmitted, 5 received, 0% packet loss, time 4000ms
...
ms
ms
ms
ms
ms
If the connectivity does not work, check the firewall settings. For more information, see Setting
up firewall rules on page 40.
• If the IP address of Flexi Multiradio BTS LTE northbound interface is IPv6, ping Flexi Multiradio
BTS LTE by entering:
ping6 <IP address of Flexi Multiradio BTS LTE northbound interface> c 5
An example output:
PING <IP address> 56(84) bytes of data.
64 bytes from <IP address>: icmp_seq=1 ttl=63 time=0.238 ms
64 bytes from <IP address>: icmp_seq=2 ttl=63 time=0.276 ms
64 bytes from <IP address>: icmp_seq=3 ttl=63 time=0.253 ms
64 bytes from <IP address>: icmp_seq=4 ttl=63 time=0.264 ms
64 bytes from <IP address>: icmp_seq=5 ttl=63 time=0.211 ms
--- <IP address> ping statistics --5 packets transmitted, 5 received, 0% packet loss, time 4000ms
...
If the connectivity does not work, check the firewall settings. For more information, see Setting
up firewall rules on page 40.
3.9 Managing Flexi Multiradio BTS LTE credentials
This section describes how to manage the credentials in NetAct to enable the access to the network
elements.
DN09118114 2-0
© 2016 Nokia Solutions and Networks
28
Integrating Flexi Multiradio BTS LTE to NetAct
Preparing NetAct
Prerequisites
If the SM-Security Administration role is not assigned to the integration user, the integration user cannot launch Network Element Access Control application. The security administrator must perform the
operations in this section.
3.9.1 Checking Flexi Multiradio BTS LTE credentials
This section describes how to check the existence of the Flexi Multiradio BTS LTE credentials in
NetAct.
Check whether the needed credentials are created and associated to the right Maintenance Region.
1. Log in to the NetAct Start Page as the integration user.
a) Enter the following URL in the address field of your internet browser: https://
<system_FQDN>/startpage
<system_FQDN> is the fully qualified domain name of the NetAct cluster load balancer for
WebSphere. For more information, see Launching the NetAct Start Page.
b) Enter the Username and Password of the integration user on the NetAct login page, and click
Log In.
c) Click Accept to accept the terms and conditions.
2. Click Security → Network Element Access Control.
3. Select the Credentials tab if it is not already selected.
4. In the credential list, check the following credentials:
Service type
Profile
NWI3 Access
Default
Group
• the group to which
the integration
Service user
Network element/MR
NWI3 Access
The maintenance region created in
user in LTE iOMS
Managing the Maintenance Region on
page 25
user belongs
• sysop
• cmauto
• cmwsapi
EM Access
Default
• the group to which
the integration
EM Access user
The maintenance region created in
name
Managing the Maintenance Region on
user belongs
page 25
• sysop
Table 9: Required credentials
Note: If the Group column shows Several Groups, click it to see the groups.
DN09118114 2-0
© 2016 Nokia Solutions and Networks
29
Integrating Flexi Multiradio BTS LTE to NetAct
Preparing NetAct
3.9.2 Creating Flexi Multiradio BTS LTE credentials
This section describes how to create the non-existing Flexi Multiradio BTS LTE credentials in NetAct.
Only create the credentials which do not exist. If all the needed credentials are created, skip this section.
1. Log in to the NetAct Start Page as the integration user.
a) Enter the following URL in the address field of your internet browser: https://
<system_FQDN>/startpage
<system_FQDN> is the fully qualified domain name of the NetAct cluster load balancer for
WebSphere. For more information, see Launching the NetAct Start Page.
b) Enter the Username and Password of the integration user on the NetAct login page, and click
Log In.
c) Click Accept to accept the terms and conditions.
2. Click Security → Network Element Access Control.
3. Select the Credentials tab if it is not already selected.
4. Create the credentials as in the following table.
Service type
Profile
Displayed attributes
Values
NWI3 Access
Default
NWI3 UserName
You can define any user name
• the group to which the
and password, but an identical
integration user be-
NWI3 Password
Confirm NWI3 Password
EM Access
Default
EM Access UserName
EM Access Password
Application group
user name and password must
longs
exist in every LTE iOMS in the
• sysop
same MR.
• cmauto
The default user is Nemuadmin.
• cmwsapi
You can define any user name
• the group to which the
and password, but an identical
integration user be-
user name and password must
Confirm EM Access Pass- exist in every LTE iOMS and Flexi
word
Multiradio BTS LTE in the same
longs
• sysop
MR.
The default user is Nemuadmin.
Note: If you need to
provision LNBTS objects in Network Element Access Control,
the user name and
password must be in
accord with the user
name and password
policy on LNBTS.
DN09118114 2-0
© 2016 Nokia Solutions and Networks
30
Integrating Flexi Multiradio BTS LTE to NetAct
Preparing NetAct
Table 10: Parameters of the credentials
a) Click New....
b) From the Service type drop-down list, select the service type.
The corresponding attributes are displayed.
c) From the Profile drop-down list, select the profile type.
Note: You cannot modify this field if the profile is set to Default automatically.
d) Enter the data in respective fields.
e) In the Network element area, select Maintenance region and select the Maintenance Region
created in Managing the Maintenance Region on page 25 from the drop-down list.
f) Click Save.
Note: If two or more credentials are created with the same credential details, there is
a prompt for confirming. See Confirm credential creation for existing service user to
know more details, then click Ok.
Expected outcome
The credential shows in the Credentials tab.
g) Select the credential and click Grant/Revoke....
The Grant and Revoke Credentials window shows.
h) In the Application Group field, select the groups, and click Save.
i) Repeat the steps to create all the credentials.
3.10 Preparing applications for Element Management
This section describes how to prepare applications for Element Management.
Note: If there is more than one Node Manager Citrix Virtual Delivery Agent (VDA) server,
repeat all the operations in this chapter on every Node Manager Citrix Virtual Delivery Agent
(VDA) server.
Ensure that Node Managers are installed and configured correctly. For more information, refer to Installing Node Managers and related software.
To configure and manage the node manager groups to which the integration user belongs, see Managing Node Manager users and user groups.
DN09118114 2-0
© 2016 Nokia Solutions and Networks
31
Integrating Flexi Multiradio BTS LTE to NetAct
Preparing NetAct
Supported applications
Supported application versions
LTE iOMS Application Launcher
Install the latest version. For more information, see Installing Application Launcher in Node Manager Citrix Virtual
Delivery Agent (VDA) server on page 32.
BTS Site Manager
• BTSSiteEM-LTE60-<application version>
• BTSSiteEM-LTE70-<application version>
• BTSSiteEM-LNF70-<application version>
• BTSSiteEM-TD_LTE50-<application version>
• BTSSiteEM-LNZ50-<application version>
• BTSSiteEM-FL15A-<application version>
• BTSSiteEM-FLF15A-<application version>
• BTSSiteEM-TL15A-<application version>
• BTSSiteEM-TLF15A-<application version>
• BTSSiteEM-FL16-<application version>
• BTSSiteEM-FLF16-<application version>
• BTSSiteEM-TL16-<application version>
• BTSSiteEM-TLF16-<application version>
• BTSSiteEM-FL16A-<application version>
• BTSSiteEM-FLF16A-<application version>
• BTSSiteEM-TL16A-<application version>
• BTSSiteEM-TLF16A-<application version>
Table 11: Supported applications and versions
3.10.1 Installing Application Launcher in Node Manager Citrix Virtual Delivery Agent
(VDA) server
This section describes how to install Application Launcher in Node Manager Citrix Virtual Delivery
Agent (VDA) server.
Note:
• If LTE iOMS Application Launcher is already installed, you may proceed to Configuring
Parameter Tool in Application Launcher on page 35.
• The following steps apply to the 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).
DN09118114 2-0
© 2016 Nokia Solutions and Networks
32
Integrating Flexi Multiradio BTS LTE to NetAct
Preparing NetAct
3.10.1.1 Downloading LTE iOMS Application Launcher installer
1. Using remote desktop connection, log in to the Node Manager Citrix Virtual Delivery Agent (VDA)
server as the <Domain name>\<Administrator account>.
Note: <Domain name> is the domain name of the Node Manager Citrix Virtual Delivery
Agent (VDA) server. For more information, contact the NetAct administrator.
2. Open a web browser, and add https://<FQDN of LTE iOMS> (for IPv4 based LTE iOMS) or
https://[<IP address of LTE iOMS northbound interface>] (for IPv6 based LTE
iOMS) to the trusted sites of the web browser.
For more information about how to add a site to the trusted sites of the browser, see the browser
manual.
3. In the web browser, enter https://<FQDN of LTE iOMS> (for IPv4 based LTE iOMS) or
[<IP address of LTE iOMS northbound interface>] (for IPv6 based LTE iOMS) in the
address bar.
Note: A secure connection (HTTPS) is required when browsing the LTE iOMS website.
4. To log in, enter the proper credentials used in accessing LTE iOMS, and click Login.
5. Depending on the version of LTE iOMS, do one of the following:
• For LTO7.0 and onwards, click Download Application Launcher.
• For LTO6.0 and earlier releases, click the OMS Management drop-down list, select Download
Application Launcher, and then click Download Application Launcher Client 2.
Note: For more information on downloading Application Launcher, contact your network
element administrator.
6. Select your operating system, and download the installation file.
DN09118114 2-0
© 2016 Nokia Solutions and Networks
33
Integrating Flexi Multiradio BTS LTE to NetAct
Preparing NetAct
3.10.1.2 Installing and configuring Application Launcher
1. Using remote desktop connection, log in to the Node Manager Citrix Virtual Delivery Agent (VDA)
server as the <Domain name>\<Administrator account>.
2. From the Desktop Start menu, enter Command Prompt in the Search programs and files box,
and press Enter.
3. Go to the directory of the installation file downloaded in Downloading LTE iOMS Application
Launcher installer on page 32.
4. Execute setupwin32.exe LAX_VM "<path of JDK or JRE>".
For example:
setupwin32.exe LAX_VM "C:\Program Files\Java\jdk1.8.0_60\bin\java.exe"
or
setupwin32.exe LAX_VM "C:\Program Files\Java\jre1.8.0_60\bin\java.exe".
Expected outcome
The installation wizard of Application Launcher shows.
5. Follow the instructions of the installation wizard to install Application Launcher, and record the
directory of the Application Launcher installation folder (for example, C:\opt\nsn\ALClient_2)
which is set in the installation wizard.
Note: Select the Desktop Shortcuts option when prompted to choose shortcut folder.
Expected outcome
The Application Launcher Client 2 is successfully installed and an application shortcut appears
on the desktop.
6. Set the permissions of the cache folder.
a) Open the directory of the Application Launcher installation folder, right-click the cache folder,
and select Properties.
The cache Properties dialog appears.
b) In the cache Properties dialog, click the Security tab, and click Edit....
The Permissions for cache dialog appears.
c) In the Permissions for cache dialog, in the Group or user names area, select Users
(<domain of users>\Users) (for example, Users (SLAB483VM19\Users)) .
d) In the Permissions for Users area, allow the following permissions, and click OK.
DN09118114 2-0
© 2016 Nokia Solutions and Networks
34
Integrating Flexi Multiradio BTS LTE to NetAct
Preparing NetAct
• Read & execute
• List folder contents
• Read
• Write
• Special permissions
e) In the cache Properties dialog, click OK.
7. Create a folder for the supported network element version in the Node Manager Citrix Virtual
Delivery Agent (VDA) server.
C:\Apps\Oss\config\EM\NOKGOMS\<supported network element version>\
For example, C:\Apps\Oss\config\EM\NOKGOMS\LOMS16A\
Note: For the release version information, refer to Overview of Flexi Multiradio BTS LTE
integration on page 5.
8. From the directory of the Application Launcher installation folder, copy the Application
Launcher Client 2 shortcut and paste it in the folder created in the previous step.
9. In the newly created folder, right-click the Application Launcher Client 2 shortcut, click
Rename, and enter ApplicationLauncher.
3.10.2 Configuring Parameter Tool in Application Launcher
This section describes how to make Parameter Tool visible in Application Launcher for LTO15A and
onward releases.
For LTO15A and onward releases, Parameter Tool is hidden in the Application Launcher by default. Do
the following to display the Parameter Tool in the Application Launcher. For other releases, skip this
section.
1. Log in to LTE iOMS as the Nemuadmin user through SSH, and then switch to the root user.
2. Assign the user to the _nokfsuiparametertool group by entering:
fsgpasswd -a <user name> _nokfsuiparametertool
For example:
fsgpasswd -a Nemuadmin _nokfsuiparametertool
3. Force NWI3Adapter to update its cached authorization information by entering:
fscorbaseccli -c updatetoken
4. Restart the Application Launcher.
Expected outcome
The Parameter Tool is visible in the Application Launcher for the user.
DN09118114 2-0
© 2016 Nokia Solutions and Networks
35
Integrating Flexi Multiradio BTS LTE to NetAct
Preparing NetAct
For more information, refer to the LTE OMS Troubleshooting document (DN0962937) in Nokia Networks Online Services (NOLS). Accessing NOLS requires authentication. This document has several
versions depending on the network element release. Refer to the version corresponding to the network
element release.
3.10.3 Installing BTS Site Manager in Node Manager Citrix Virtual Delivery Agent
(VDA) server
This section describes how to install BTS Site Manager in Node Manager Citrix Virtual Delivery Agent
(VDA) server.
Note: If you have the Disaster Recovery Solution in your NetAct system, perform this
procedure in the Disaster Recovery Site (SITE-B).
1. Using remote desktop connection, log in to the Node Manager Citrix Virtual Delivery Agent (VDA)
server as the <Domain name>\<Administrator account>.
2. Run the BTSSiteEM-<build version of BTS Site Manager>.exe file (for example,
BTSSiteEM-FLF16A-0107_000113_000001.exe). Follow the instructions of the installation
wizard, and record the directory of the BTS Site Manager installation folder (for example, C:
\Program Files (x86)\NSN\Managers\BTS Site\BTS Site Manager) which is set in
the installation wizard.
Note: Contact your network element administrator for the location of the BTSSiteEM<build version of BTS Site Manager>.exe 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 new version of the BTS Site Manager and remove old versions from the system.
If an old version of BTS Site Manager is needed, install it before installing the new version of BTS Site Manager. After the new version of BTS Site Manager is installed, if you
install an old version of BTS Site Manager with the Normal Installation option, BTS Site
Manager cannot opened.
Expected outcome
The BTS Site Manager is successfully installed.
3. In the directory of the BTS Site Manager installation folder, right-click the BTSSiteManager.bat
file, select Create shortcut, and rename the created shortcut file as wbtssitemanager.
4. Create a folder for the supported network element version in Node Manager Citrix Virtual Delivery
Agent (VDA) server.
C:\Apps\Oss\config\EM\NOKLTE\<supported network element version>\
DN09118114 2-0
© 2016 Nokia Solutions and Networks
36
Integrating Flexi Multiradio BTS LTE to NetAct
Preparing NetAct
For example, C:\Apps\Oss\config\EM\NOKLTE\FLF16A\
Note: For the release version information, refer to Overview of Flexi Multiradio BTS LTE
integration on page 5.
5. From the directory of the BTS Site Manager installation folder, copy the wbtssitemanager
shortcut and paste it in the newly created folder.
3.10.4 Downloading Element Management Launch scripts
This section describes how to download Element Management Launch scripts.
1. Using remote desktop connection, log in to the Node Manager Citrix Virtual Delivery Agent (VDA)
server as the <Domain name>\<Administrator account>.
2. Navigate to the C:\Apps\Oss\config\EM directory, and create the LTE folder if it does not exist.
3. From the Desktop Start menu, enter Command Prompt in the Search programs and files box,
and press Enter.
4. Go to C:\Apps\Oss\config\EM\LTE, enter the following command, and enter omc and
password of the omc user to connect any NetAct WAS node with psftp.
psftp <IP address of a NetAct WAS node>
Note: If Store key in cache? (y/n) appears, enter y.
5. To open the base folder, enter the following command:
cd /var/opt/oss/global/NSN-fsdc/com.nsn.em/tools/NOKGOMS/base
6. To download scripts, enter the following command:
mget WEB_Launch_LTE.vbs httpssoclient_lte.bat
Expected outcome
The httpssoclient_lte.bat and WEB_Launch_LTE.vbs files are downloaded to the LTE
folder in C:\Apps\Oss\config\EM.
7. Log out of the Node Manager Citrix Virtual Delivery Agent (VDA) server.
3.10.5 Preparing for ADMIN of LTE BTS
This section describes how to prepare for ADMIN of LTE BTS.
DN09118114 2-0
© 2016 Nokia Solutions and Networks
37
Integrating Flexi Multiradio BTS LTE to NetAct
Preparing NetAct
Note: Only FL16A and TL16A support ADMIN. For other network element releases, skip this
section.
Prerequisites
Ensure that Google Chrome 48.0.2564 or onward stable release must be installed in Node Manager
Citrix Virtual Delivery Agent (VDA) server first.
1. Using remote desktop connection, log in to the Node Manager Citrix Virtual Delivery Agent (VDA)
server as the <Domain name>\<Administrator account>.
2. Navigate to the C:\Apps\Oss\config\EM directory, and create the NOKLTE folder if it does not
exist.
3. Navigate to the C:\Apps\Oss\config\EM\NOKLTE directory, and create the base folder if it
does not exist.
4. From the Desktop Start menu, enter Command Prompt in the Search programs and files box,
and press Enter.
5. Go to C:\Apps\Oss\config\EM\NOKLTE\base, enter the following command, and enter omc
and password of the omc user to connect any NetAct WAS node with psftp.
psftp <IP address of a NetAct WAS node>
Note: If Store key in cache? (y/n) appears, enter y.
6. To open the base folder, enter the following command:
cd /var/opt/oss/global/NSN-fsdc/com.nsn.em/tools/NOKLTE/base
7. To download scripts, enter the following command:
mget admin_tool.bat admin_tool.vbs
Expected outcome
The admin_tool.bat and admin_tool.vbs files are downloaded to the base folder in C:
\Apps\Oss\config\EM\NOKLTE.
8. In the C:\Apps\Oss\config\EM\NOKLTE\base directory, create a shortcut for
admin_tool.bat and rename the shortcut to admin_tool.
9. In the C:\Apps\Oss\config\EM\NOKLTE\base directory, create a shortcut for Google Chrome
and rename the shortcut to chrome.
10. Log out of the Node Manager Citrix Virtual Delivery Agent (VDA) server.
DN09118114 2-0
© 2016 Nokia Solutions and Networks
38
Integrating Flexi Multiradio BTS LTE to NetAct
Preparing NetAct
3.10.6 Configuring OMS Element Manager
This section describes how to configure OMS Element Manager.
1. Using remote desktop connection, log in to the Node Manager Citrix Virtual Delivery Agent (VDA)
server as the <Domain name>\<Administrator account>.
2. Navigate to the C:\Apps\Oss\config\EM directory, and create the NOKGOMS folder if it does not
exist.
3. Navigate to the C:\Apps\Oss\config\EM\NOKGOMS directory, and create the base folder if it
does not exist.
4. Navigate to the C:\Apps\Oss\config\EM\LTE directory.
5. Right-click the httpssoclient_lte.bat file, and select Create shortcut. Rename the created
shortcut as httpssoclient_lte.
6. Copy the httpssoclient_lte shortcut to the base folder in the C:\Apps\Oss\config\EM
\NOKGOMS directory.
7. Log out of the Node Manager Citrix Virtual Delivery Agent (VDA) server.
DN09118114 2-0
© 2016 Nokia Solutions and Networks
39
Integrating Flexi Multiradio BTS LTE to NetAct
Preparing the intermediate system
4 Preparing the 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
4.1 Setting up firewall rules
This section describes the firewall rules needed for enabling the communication between network
elements and NetAct.
The default firewall rules for connecting Flexi Multiradio BTS LTE to NetAct are listed in the table below.
Note: To prevent security risk, Nokia highly recommends you choose the secure protocol
(HTTPS instead of HTTP).
FTP service is disabled by default in NetAct. For detailed instructions on how to enable FTP service,
see Starting FTP.
Source
OMS
Source
Port
ephemeral
1
Dest.
Dest. Port
AL
LB WAS virtual
80
HTTP
2
TL
Service Object
Description
TCP
http
Exchange files be-
IP
tween netAct and
NE using HTTP protocol. Optional: This
firewall rule is not
required if the respective secure protocol is used
OMS
ephemeral
LB WAS virtual
389
LDAP
TCP
ldap
IP
LDAP port used by
OMS that is configured for CNUM
OMS
ephemeral
LB WAS virtual
443
HTTPS
TCP
https
IP
Exchange files between netAct and
NE using HTTPS
protocol
OMS
ephemeral
LB WAS virtual
446
IIOP
IP
TCP
cm-lte-oms-provi-
HTTPS port in We-
sion
bSphere Application
Server used for CM
LTE -> OMS provisioning purpose.
DN09118114 2-0
© 2016 Nokia Solutions and Networks
40
Integrating Flexi Multiradio BTS LTE to NetAct
Source
NWI3
Source
Port
ephemeral
Preparing the intermediate system
1
Dest.
Dest. Port
AL
OMS
22
SSH/SFTP
2
TL
Service Object
Description
TCP
sshd
Secured shell and
secured file transfer
from OMS
OMS
ephemeral
NWI3
80
HTTP
TCP
http
HTTP port used
by OMS file download (hardcoded
in OMS). Optional:
This firewall rule is
not required if the
respective secure
protocol is used
NWI3
ephemeral
OMS
80
HTTP
TCP
http
HTTP file transfers
from OMS Optional:
This firewall rule is
not required if the
respective secure
protocol is used
OMS
ephemeral
NWI3
123
NTP
UDP
ntp
OMS clock time set
to NWI3 node which
is used as one of
NTP server in NetAct.
OMS
ephemeral
NWI3
443
HTTPS
TCP
https
HTTPS port used
by OMS file download (hardcoded in
OMS).
NWI3
ephemeral
OMS
443
HTTPS
TCP
https
HTTPS file transfers
from OMS
OMS
ephemeral
NWI3
33749
HTTPS
TCP
httpd
For software backup
OMS
ephemeral
NWI3
49152
IIOP
TCP
nwi3-reg-service
NWI3 registration
service
OMS
ephemeral
NWI3
49164
IIOP
TCP
nwi3-notific-service
NWI3 notification
service
OMS
OMS
OMS
OMS
OMS
OMS
OMS
DN09118114 2-0
ephemeral
ephemeral
ephemeral
ephemeral
ephemeral
ephemeral
ephemeral
NWI3
NWI3
NWI3
NWI3
NWI3
NWI3
NWI3
49177
49179
49192
49300
49311
49312
49333
IIOP
IIOP
IIOP
IIOP
IIOP
IIOP
IIOP
© 2016 Nokia Solutions and Networks
TCP
TCP
TCP
TCP
TCP
TCP
TCP
nwi3-topolo-
NWI3 topology
gy-event-consumer
event consumer
nwi3-alarm-event-
NWI3 alarm event
consumer
consumer
nwi3-trace-event-
NWI3 trace event
consumer
consumer
nwi3-cm-event-no-
NWI3 CM event
tification
consumer
nwi3-topology-ser-
NWI3 topology ser-
vice-callback
vice
nwi3-topolo-
NWI3 topology
gy-delete-callback
delete
nwi3-swm-node-
NEBR download
backup
callback agent
41
Integrating Flexi Multiradio BTS LTE to NetAct
Source
NWI3
NWI3
Source
Port
ephemeral
ephemeral
Preparing the intermediate system
Dest.
Dest. Port
AL
1
2
TL
Service Object
Description
OMS
49341
IIOP
TCP
nwi3-security-frag-
NWI3 Security frag-
ment
ment
nwi3-license-mgr-
NWI3 LM Agent
OMS
49342
IIOP
TCP
agent
OMS
NWI3
ephemeral
ephemeral
NWI3
OMS
49344
49348
IIOP
IIOP
TCP
TCP
nwi3-swm-node-
NEBR upload call-
backup
back agent
nwi3-swm-node-
NWI3 SWM NEBR
backup
OMS
ephemeral
NWI3
49350
IIOP
TCP
nwi3-hw-agent
NWI3 HW event
consumer
NWI3
OMS
ephemeral
ephemeral
OMS
NWI3
49351
49354
IIOP
IIOP
TCP
TCP
nwi3-topology-ser-
NWI3 Topology Ser-
vice
vice
nwi3-audit-trail-
NWI3 audit trail
callback
OMS
ephemeral
NWI3
49355
IIOP
TCP
tcp-49355
NWI3 Symptom data upload
NWI3
ephemeral
OMS
49361
IIOP
TCP
nwi3-pm-service
NWI3 PM Service
NWI3
ephemeral
OMS
49363
IIOP
TCP
nwi3-sw-agent
NWI3 SW Agent
NWI3
ephemeral
OMS
49366
IIOP
TCP
nwi3-symptom-da-
NWI3 Symptom da-
ta-upload
ta upload
nwi3-cerma-ser-
NWI3 Certificate
vice
Service
nwi3-auditlog-ser-
NWI3 Audit Trail
vice
Service
nwi3-license-event-
NWI3 licence event
consumer
consumer
nwi3-cert-agent
NWI3 certificate
NWI3
NWI3
OMS
OMS
ephemeral
ephemeral
ephemeral
ephemeral
OMS
OMS
NWI3
NWI3
49368
49375
49509
49510
IIOP
IIOP
IIOP
IIOP
TCP
TCP
TCP
TCP
management
OMS
OMS
ephemeral
ephemeral
NWI3
NWI3
49530
49557
IIOP
IIOP
TCP
TCP
nwi3-pm-event-
NWI3 pm event
consumer
consumer
nwi3-sw-upload
NWI3 Software Upload
OMS
ephemeral
NWI3
49558
IIOP
TCP
nwi3-sw-download
NWI3 Software
Download
OMS
ephemeral
NWI3
49559
IIOP
TCP
nwi3-sw-change-
NWI3 Software
event-consumer
change event consumer
OMS
OMS
ephemeral
ephemeral
NWI3
NWI3
49560
49561
IIOP
IIOP
TCP
TCP
nwi3-sw-up-
NWI3 Software up-
date-event-con-
date event con-
sumer
sumer
nwi3-sw-commit
NWI3 Software
Commit/Rollback
NWI3
DN09118114 2-0
ephemeral
OMS
49566
IIOP
© 2016 Nokia Solutions and Networks
TCP
nwi3-adapter
NWI3 Adapter
42
Integrating Flexi Multiradio BTS LTE to NetAct
Source
OMS
OMS
Source
Port
ephemeral
ephemeral
Preparing the intermediate system
Dest.
Dest. Port
AL
1
2
TL
Service Object
Description
NWI3
49600
IIOP
TCP
nwi3-audit-trail-
NWI3 audit trail
event-consumer
event consumer
tcp-49619
NWI3 CNUM medi-
NWI3
49619
IIOP
TCP
ator management
OMS
ephemeral
NWI3
49620
IIOP
TCP
nwi3-mediator-call-
NWI3 integration
back
mediator management
OMS
NodeMgr
ephemeral
ephemeral
NWI3
49622
OMS
22
IIOP
SSH
TCP
TCP
nwi3-local-securi-
NWI3 user manage-
ty-callback
ment
ssh
Element manager
connections
NodeMgr
ephemeral
OMS
80
HTTP
TCP
http
Used to access
OMS Element Manager via WebUI.
Optional: This firewall rule is not required if the respective secure protocol
is used.
NodeMgr
ephemeral
OMS
443
HTTPS
TCP
https
Used to access
OMS Element Manager via WebUI.
NodeMgr
ephemeral
OMS
500
IIOP
TCP
udp-500
Ipsec IKE negotiation
NodeMgr
ephemeral
OMS
636
LDAPS
TCP
ldaps
Application Launcher launch
NodeMgr
ephemeral
OMS
49568
IIOP
TCP
tcp-49568
OMS connection
needed for EM
Launch
NodeMgr
ephemeral
OMS
49152-49652
IIOP
TCP
ne-applaunch-
Ephemeral ports
er-oms
used by OMS Application launcher internal applications,
i.e.: Measurement
management, Fault
management.
OMS
ephemeral
NodeMgr
49152 - 49652
IIOP
TCP
ne-applaunch-
listening ports for
er-oms
CORBA callbacks
between OMS and
Application Launcher in NodeMgr server
OMS
ephemeral
SBI-Common-
80
HTTP
Mediation
TCP
http
CM NWI3 data file
transfer. Optional:
This firewall rule is
not required if the
respective secure
protocol is used
(port 8443).
DN09118114 2-0
© 2016 Nokia Solutions and Networks
43
Integrating Flexi Multiradio BTS LTE to NetAct
Source
SBI-Common-
Source
Port
ephemeral
Preparing the intermediate system
1
Dest.
Dest. Port
AL
OMS
80
HTTP
2
TL
Service Object
Description
TCP
http
CM NWI3 data file
Mediation
transfer. Optional:
This firewall rule is
not required if the
respective secure
protocol is used
(port 443).
OMS
ephemeral
SBI-Common-
443
HTTPS
TCP
CM NWI3 data file
Mediation
SBI-Common-
ephemeral
OMS
transfer
443
HTTPS
TCP
https
Mediation
OMS
CM NWI3 data file
transfer
ephemeral
SBI-Common-
49400 - 49499
IIOP
TCP
tcp-49400 - 49499
CM NWI3
Mediation
WebSphere
ephemeral
OMS
22
SSH
TCP
ssh
SSH
WebSphere
ephemeral
OMS
80
HTTP
TCP
http
CM outgoing request. Optional:
This firewall rule is
not required if the
respective secure
protocol is used.
WebSphere
ephemeral
OMS
443
HTTPS
TCP
https
CM outgoing request.
OMS
ephemeral
WebSphere
446
HTTPS
TCP
cm-lte-oms-provi-
HTTPS port in We-
sion
bSphere Application
Server used for CM
LTE -> OMS provisioning purpose.
WebSphere
ephemeral
OMS
49350
IIOP
TCP
nwi3-hw-agent
NWI3 HW Agent
WebSphere
ephemeral
OMS
49357
IIOP
TCP
nwi3-cm-plan-
NWI3 CM Plan
mgmt
Management
WebSphere
ephemeral
OMS
49363
IIOP
TCP
nwi3-sw-agent
NWI3 SW Agent
WebSphere
ephemeral
OMS
49367
IIOP
TCP
nwi3-measure-
NWI3 Measurement
ment-hndlr
Handler
WebSphere
ephemeral
OMS
49566
IIOP
TCP
nwi3-adapter
NWI3 Adapter
WebSphere
ephemeral
OMS
33434-33523
ICMP
UDP
udp-33434-33523
Used for Displaying
the route and measuring transit delays
of packet
OMS
ephemeral
WebSphere
49400-49499
IIOP
TCP
https
For CM upload
MRBTS
ephemeral
LB WAS virtual
389
LDAP
TCP
ldap
LDAP port used by
IP
any NE that is configured for CNUM
NodeMgr
ephemeral
MRBTS
443
HTTPS
TCP
https
Secured HTTP collection to MRBTS
NodeMgr
ephemeral
MRBTS
3600
HTTPS
TCP
https
ADMIN tool launch
NodeMgr
ephemeral
MRBTS
6000
HTTP
TCP
http
File transfer via
HTTP Optional: This
DN09118114 2-0
© 2016 Nokia Solutions and Networks
44
Integrating Flexi Multiradio BTS LTE to NetAct
Source
Source
Port
Preparing the intermediate system
Dest.
Dest. Port
AL
1
2
TL
Service Object
Description
firewall rule is not
required if the respective secure protocol is used
NodeMgr
ephemeral
MRBTS
6001
HTTPS
TCP
https
File transfer via
HTTPS
NodeMgr
ephemeral
MRBTS
12000
IIOP
TCP
entextxid
SEM-FTM connection
MRBTS
ephemeral
NodeMgr
13062-13092
HTTPS
TCP
x-window
File transfer via
HTTPS
WebSphere
ephemeral
MRBTS
33434-33523
ICMP
UDP
udp-33434-33523
Used for Displaying
the route and measuring transit delays
of packet
OMS
ephemeral
DNS
53
DNS
TCP/
dns
UDP
Optional. To be
used if NetAct is
used as DNS for the
NE. DNS primarily uses this port to
serve requests.
Table 12: Firewall rules for Flexi Multiradio BTS LTE
Note:
• 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.
1
• AL : Application Layer
2
• TL : Transport Layer
• If the port is ephemeral, select a port from the port pool of the IP stack.
• NetAct performs the network element status check on the O&M connections by implementing Internet Control Message Protocol (ICMP). Before integration, enable ICMP
(ping) traffic from NetAct to Flexi Multiradio BTS LTE in firewall configuration.
Note: The firewall rules provided in Table 12: Firewall rules for Flexi Multiradio BTS LTE on
page 40 are only related to network element integration. For LTE 15A and onwards, to
use BTS site manager, OMS Element Manager, and OMS Application Launcher, ensure that
the related BTS site manager and OMS firewall rules are configured. For more information
about these firewall rules, see the LTE RAN O&M Security document (DN0958798) in Nokia
Networks Online Services (NOLS). Accessing NOLS requires authentication. This document
has several versions depending on the network element release. Refer to the version
corresponding to the network element release. In the document, go to Firewall Support →
Firewall functionality → Predefined packet filter rules.
For detailed descriptions of all the sources and destinations mentioned in Table 12: Firewall rules for
Flexi Multiradio BTS LTE on page 40, see the following table.
DN09118114 2-0
© 2016 Nokia Solutions and Networks
45
Integrating Flexi Multiradio BTS LTE to NetAct
Node object name
Preparing the intermediate system
Description
NetAct nodes
SBI-CommonMediation
IP addresses of the VMs where the common_mediations service is running
NWI3
IP address of the VM where the nwi3 service is running
NodeMgr
IP addresses of the Node Manager Citrix Virtual Delivery Agent (VDA)
servers
WebSphere
IP addresses of the VMs where the was service is running
DNS
Virtual address of the node where the DNS service is running
LB WAS virtual IP
Virtual IP address of the WebSphere Application Server Load Balancer
Network element nodes
OMS
IP address of OMS North Bound Interface for LTE
MRBTS
IP address of Base Transceiver Station (BTS) for LTE northbound interface
Table 13: Node descriptions
4.2 Configuring SOCKS proxy service
This section describes how to configure SOCKS proxy to enable LTE iOMS Element Management
launch from a workstation.
If you want to launch the OMS Element Manager LTO7.0 and onwards, 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.
DN09118114 2-0
© 2016 Nokia Solutions and Networks
46
Integrating Flexi Multiradio BTS LTE to NetAct
Integrating Flexi Multiradio BTS LTE to NetAct with NEIW
5 Integrating Flexi Multiradio BTS LTE to NetAct with
NEIW
This section describes how to integrate Flexi Multiradio BTS LTE to NetAct automatically with NE
Integration Wizard (NEIW).
5.1 Integration operations in NEIW
This section describes how to operate NE Integration Wizard (NEIW) to integrate Flexi Multiradio BTS
LTE.
1. Log in to the NetAct Start Page as the integration user.
a) Enter the following URL in the address field of your internet browser: https://
<system_FQDN>/startpage
<system_FQDN> is the fully qualified domain name of the NetAct cluster load balancer for
WebSphere. For more information, see Launching the NetAct Start Page.
b) Enter the Username and Password of the integration user on the NetAct login page, and click
Log In.
c) Click Accept to accept the terms and conditions.
2. In NetAct Start Page, click Administration → NE Integration Wizard.
Expected outcome
The NE Integration Wizard application runs.
3. Click New....
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 Maintenance Region (MR) created in Managing the Maintenance Region on page 25
DN09118114 2-0
© 2016 Nokia Solutions and Networks
47
Integrating Flexi Multiradio BTS LTE to NetAct
Integrating Flexi Multiradio BTS LTE to NetAct with NEIW
Attribute
Value
OMS O&M agent address
The value varies according to the IP address of LTE iOMS northbound interface.
• If it is IPv4, enter the fully qualified domain name (FQDN) or the IP
address of the OMS O&M Agent.
• If it is IPv6, enter the IP address of the OMS O&M Agent.
OMS distinguished name
The distinguished name of LTE iOMS, for example, PLMN-PLMN/OMS<instance ID>
Note: The OMS instance ID must be an exact match of the
OMS system ID. To get the OMS system ID, see Checking
system ID of LTE iOMS on page 16.
Table 14: Mandatory configuration parameters for OMS
6. (Optional) If you need to configure the time synchronization with NetAct or the DNS service on LTE
iOMS, fill in the optional values.
Attribute
Value
Additional information
Configure DNS
If the IP address of LTE iOMS northbound in-
If any DNS servers are already con-
forwarder in OMS
terface is IPv6, leave the value empty. If the
figured for LTE iOMS, the configura-
IP address of LTE iOMS northbound interface
tion in this step does not overwrite the
is IPv4, fill in the DNS server IP address. For
existing servers but only adds new
more information, refer to Configuring DNS for-
server(s).
warder on LTE iOMS on page 50.
Note: If you need to configure two or
more DNS servers, click the + icon.
Configure NTP
Fill in the NTP service host IP address. For
If any NTP servers are already con-
server in OMS
more information, refer to Configuring LTE
figured for LTE iOMS, the configura-
iOMS time synchronization with NetAct on page tion in this step does not overwrite the
50.
existing servers but only adds new
Note: If you need to configure two or
server(s).
more NTP servers, click the + icon.
OMS root pass-
The password used to log in to LTE iOMS as
The credentials are necessary for
word
the root user
both NTP and DNS configurations.
Confirm OMS root The password used to log in to LTE iOMS as
password
DN09118114 2-0
the root user
© 2016 Nokia Solutions and Networks
48
Integrating Flexi Multiradio BTS LTE to NetAct
Integrating Flexi Multiradio BTS LTE to NetAct with NEIW
Table 15: Optional configuration parameters for OMS
7. Click Save.
Expected outcome
The integration plan is created and shown in the list.
8. Select the plan and click Integrate.
Note: If multiple plans are triggered, the network elements are integrated one by one.
The Integration status shows In queue for those waiting ones.
Expected outcome
If the Integration status changes to Completed, integration is successful.
If the Integration status changes to Failed, click the Failed link and then click Show full log to
check the log. For more information on how to troubleshoot the problems, see the troubleshooting
sections.
DN09118114 2-0
© 2016 Nokia Solutions and Networks
49
Integrating Flexi Multiradio BTS LTE to NetAct
Integrating Flexi Multiradio BTS LTE to NetAct manually
6 Integrating Flexi Multiradio BTS LTE to NetAct
manually
This section describes how to integrate Flexi Multiradio BTS LTE to NetAct manually.
6.1 Integration operations on OMS
This section describes the operations needed on OMS for it to be integrated to NetAct.
6.1.1 Configuring DNS forwarder on LTE iOMS
This section describes how to configure DNS forwarder on LTE iOMS.
Note: This section is only needed for LTE iOMS whose IP address is IPv4. If the IP address
of the LTE iOMS to be integrated is IPv6, skip this section.
To configure DNS forwarder on LTE iOMS, see the Installing and Commissioning LTE OMS document
(DN0956464) in Nokia Networks Online Services (NOLS). Accessing NOLS requires authentication.
This document has several versions depending on the network element release. Refer to the version
corresponding to the network element release. In the document, go to Integrating LTE OMS to the
network → Configuring DNS services in LTE OMS.
Note:
• For DNS management, network element can be integrated into external DNS servers
and/or into NetAct, which means that the primary DNS server IP address and secondary
DNS server IP address can have the following values:
– External primary DNS server IP address and external secondary DNS server IP address
– External primary DNS server IP address and NetAct DNS dns-master service host IP
– NetAct DNS dns-master service host IP and NetAct DNS dns-slave service host IP
For information about external DNS server address, contact your network administrator.
• It is recommended to add all possible NetAct VM IP addresses which host DNS service
as LTE iOMS DNS reference for high availability. A NetAct system usually contains 2
DNS service hosts; one acts as the master service and the other acts as the slave service.
6.1.2 Configuring LTE iOMS time synchronization with NetAct
This section describes how to configure LTE iOMS time synchronization with NetAct.
DN09118114 2-0
© 2016 Nokia Solutions and Networks
50
Integrating Flexi Multiradio BTS LTE to NetAct
Integrating Flexi Multiradio BTS LTE to NetAct manually
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 LTE iOMS is, and what the time sharing topology is.
NetAct and LTE iOMS must synchronize their time with a time source, and the scenarios vary as the
following:
• NetAct and LTE iOMS use the same time source (external NTP server).
• NetAct and LTE iOMS use different time sources (external NTP servers).
• LTE iOMS uses NetAct as 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 LTE iOMS.
If you need to configure NetAct as the time source for LTE iOMS, note the following:
• For the purpose of high availability, 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 two NetAct VM IP addresses should be added as forwarders,
and the NetAct VM which hosts NWI3 service should be the first forwarder.
• For detailed instruction, see the Installing and Commissioning LTE OMS document (DN0956464)
in Nokia Networks Online Services (NOLS). Accessing NOLS requires authentication. This
document has several versions depending on the network element release. Refer to the version
corresponding to the network element release. In the document, go to Integrating LTE OMS to
the network → Configuring NTP services in LTE OMS.
6.2 Integration operations on NetAct
This section describes the operations needed on NetAct.
6.2.1 Creating managed objects for LTE iOMS in NetAct
This section describes how to create LTE iOMS managed objects in NetAct Monitor.
Note: To prevent security risk, Nokia highly recommends you choose the secure protocol
(HTTPS instead of HTTP).
Create managed objects in NetAct Monitor with the following hierarchy:
|-PLMN-PLMN
|-OMS-<instance ID>
|-HTTP-1
DN09118114 2-0
© 2016 Nokia Solutions and Networks
51
Integrating Flexi Multiradio BTS LTE to NetAct
Integrating Flexi Multiradio BTS LTE to NetAct manually
In the hierarchy, upper level managed object is referred to as parent object. For example, PLMNPLMN is the parent object of OMS-<instance ID>.
1. Log in to the NetAct Start Page as the integration user.
a) Enter the following URL in the address field of your internet browser: https://
<system_FQDN>/startpage
<system_FQDN> is the fully qualified domain name of the NetAct cluster load balancer for
WebSphere. For more information, see Launching the NetAct Start Page.
b) Enter the Username and Password of the integration user on the NetAct login page, and click
Log In.
c) Click Accept to accept the terms and conditions.
2. In NetAct Start Page, click Monitoring → Monitor.
3. In Monitor, open Object Explorer by selecting Tools → Managed Objects → Object Explorer.
Expected outcome
The Objects panel appears.
4. In the Objects pane, create the managed objects as in the following table:
Object Class
OMS
Assign as self
agent
Yes
Mandatory values
• Instance: get the instance ID from Checking system ID of LTE iOMS on page 16
• Version: the version of LTE iOMS
Keep other fields as default.
HTTP
No
• Instance: 1
• Host Name: the value varies according to the IP address of LTE iOMS northbound interface.
• If it is IPv4, enter the fully qualified domain name (FQDN) or the northbound IP
address of LTE iOMS.
• If it is IPv6, enter the northbound IP address of LTE iOMS.
• Security Mode: HTTPS
Keep other fields as default.
Table 16: Parameters of the managed objects
a) Right-click the parent object and select New → Object....
b) In the New Object dialog, from the Object Class drop-down list, select the object class, and, if
required (indicated in the table), select Assign as self agent.
c) Click Next >.
d) In the Fill Mandatory Values dialog, fill in the mandatory values and click Finish.
DN09118114 2-0
© 2016 Nokia Solutions and Networks
52
Integrating Flexi Multiradio BTS LTE to NetAct
Integrating Flexi Multiradio BTS LTE to NetAct manually
Expected outcome
The managed object is created and it shows in the Objects panel.
e) Repeat the steps to create all the managed objects.
6.2.2 Associating managed objects to a Maintenance Region
1. Log in to the NetAct Start Page as the integration user.
a) Enter the following URL in the address field of your internet browser: https://
<system_FQDN>/startpage
<system_FQDN> is the fully qualified domain name of the NetAct cluster load balancer for
WebSphere. For more information, see Launching the NetAct Start Page.
b) Enter the Username and Password of the integration user on the NetAct login page, and click
Log In.
c) Click Accept to accept the terms and conditions.
2. In NetAct Start Page, click Monitoring → Monitor.
3. In Monitor, open Object Explorer by selecting Tools → Managed Objects → Object Explorer.
Expected outcome
The Objects panel appears.
4. In the Objects panel, right-click the OMS-<instance ID> object that you want to associate to a
maintenance region, and select Maintenance Region Association.
The Associate Maintenance Region dialog appears.
5. Select the maintenance region created in Managing the Maintenance Region on page 25, and click
OK.
Expected outcome
The managed objects are associated to the Maintenance Region. In the Properties panel of the
OMS-<instance ID> object, the Maintenance Region is listed in the Maintenance Region field.
6.2.3 Executing integration data upload
This section describes how to perform integration data upload for LTE iOMS.
Upload the integration data.
1. Log in to the NetAct Start Page as the integration user.
DN09118114 2-0
© 2016 Nokia Solutions and Networks
53
Integrating Flexi Multiradio BTS LTE to NetAct
Integrating Flexi Multiradio BTS LTE to NetAct manually
a) Enter the following URL in the address field of your internet browser: https://
<system_FQDN>/startpage
<system_FQDN> is the fully qualified domain name of the NetAct cluster load balancer for
WebSphere. For more information, see Launching the NetAct Start Page.
b) Enter the Username and Password of the integration user on the NetAct login page, and click
Log In.
c) Click Accept to accept the terms and conditions.
2. In NetAct Start Page, click Monitoring → Monitor.
3. In Monitor, open Object Explorer by selecting Tools → Managed Objects → Object Explorer.
Expected outcome
The Objects panel appears.
4. Right-click the OMS-<instance ID> object and select Element Management → Integration
Data Upload.
Expected outcome
In the Ongoing Operations area, after the Integration Data Upload progress bar disappears,
check if Completed Successfully shows in the Operation Status in the Operations History
area.
If the integration data upload fails, see Integration data upload failure on page 74.
6.2.4 Uploading Flexi Multiradio BTS LTE alarms
This section describes how to perform alarm upload for Flexi Multiradio BTS LTE.
1. Log in to the NetAct Start Page as the integration user.
a) Enter the following URL in the address field of your internet browser: https://
<system_FQDN>/startpage
<system_FQDN> is the fully qualified domain name of the NetAct cluster load balancer for
WebSphere. For more information, see Launching the NetAct Start Page.
b) Enter the Username and Password of the integration user on the NetAct login page, and click
Log In.
c) Click Accept to accept the terms and conditions.
2. In NetAct Start Page, click Monitoring → Monitor.
3. In Monitor, open Object Explorer by selecting Tools → Managed Objects → Object Explorer.
DN09118114 2-0
© 2016 Nokia Solutions and Networks
54
Integrating Flexi Multiradio BTS LTE to NetAct
Integrating Flexi Multiradio BTS LTE to NetAct manually
Expected outcome
The Objects panel appears.
4. Right-click the OMS-<instance ID> object and select Alarm Upload.
Expected outcome
In the Ongoing Operations area, when the Alarm Upload progress bar shows 100% Completed,
check if Completed Successfully shows in the Operation Status in the Operations History
area.
DN09118114 2-0
© 2016 Nokia Solutions and Networks
55
Integrating Flexi Multiradio BTS LTE to NetAct
Operations on NetAct after integration
7 Operations on NetAct after integration
After the integration, perform the procedures in this section.
7.1 Associating maintenance region with MRBTS and LNBTS
The section describes how to associate the MRBTS and LNBTS objects with the maintenance region
that the LTE iOMS does not have.
If you need to associate the MRBTS and LNBTS objects with the maintenance region that the LTE
iOMS does not have, complete the following steps. Otherwise, skip this section.
1. Log in to the NetAct Start Page as the integration user.
a) Enter the following URL in the address field of your internet browser: https://
<system_FQDN>/startpage
<system_FQDN> is the fully qualified domain name of the NetAct cluster load balancer for
WebSphere. For more information, see Launching the NetAct Start Page.
b) Enter the Username and Password of the integration user on the NetAct login page, and click
Log In.
c) Click Accept to accept the terms and conditions.
2. In NetAct Start Page, select Monitoring → Monitor.
3. In Monitor, open Object Explorer by selecting Tools → Managed Objects → Object Explorer.
4. In the Objects pane, expand the PLMN-PLMN object, right-click the MRBTS-<instance ID>
object 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 Regions 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 check boxes.
6. Click OK.
DN09118114 2-0
© 2016 Nokia Solutions and Networks
56
Integrating Flexi Multiradio BTS LTE to NetAct
Operations on NetAct after integration
Expected outcome
The selected maintenance region is associated with MRBTS and LNBTS.
Note: The Confirm Maintenance Region Propagation dialog appears whenever
Propagate selected Maintenance Region to the sub tree is selected or cleared. To
confirm the operation, click Yes.
7. To verify if the manual association procedure succeeded, right-click the maintenance region MR<instance ID> 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
• Adaptation ID
• Release
Note: The Show Associated Objects option is disabled if multiple Maintenance Regions are selected. For more information, refer to Associating a managed object to Maintenance Region.
7.2 Provisioning Flexi Multiradio BTS LTE credentials in Network
Element Access Control
This section describes how to provision the created credentials to Flexi Multiradio BTS LTE.
Provisioning is supported only for the credentials created in Network Element Access Control (NEAC).
Provision Flexi Multiradio BTS LTE credentials only if password is intended to be provisioned to the
network element.
Note:
• Provisioning is supported only for LNBTS objects.
• The user name and password are in accord with the user name and password policy on
LNBTS.
Provisioning NE Type
LNBTS
DN09118114 2-0
Provisioning Service
Authentication NE
Authentication Ser-
Type
Type
vice Type
EM Access
OMS
NWI3 Access
© 2016 Nokia Solutions and Networks
57
Integrating Flexi Multiradio BTS LTE to NetAct
Operations on NetAct after integration
Table 17: Required service type for provisioning
For information on how to check and create the credentials, see Managing Flexi Multiradio BTS LTE
credentials on page 28.
1. Log in to the NetAct Start Page as the integration user.
a) Enter the following URL in the address field of your internet browser: https://
<system_FQDN>/startpage
<system_FQDN> is the fully qualified domain name of the NetAct cluster load balancer for
WebSphere. For more information, see Launching the NetAct Start Page.
b) Enter the Username and Password of the integration user on the NetAct login page, and click
Log In.
c) Click Accept to accept the terms and conditions.
2. Click Security → Network Element Access Control.
3. Click the Provisioning tab.
4. Select the EM Access credential.
5. Click Provision, and follow the on-screen instructions to confirm the provisioning.
Expected outcome
If completed appears in the Status column, the credential is provisioned to the network element
in the maintenance region.
7.3 Executing Configuration Management upload
The section describes how to execute Configuration Management upload.
1. Log in to the NetAct Start Page as the integration user.
a) Enter the following URL in the address field of your internet browser: https://
<system_FQDN>/startpage
<system_FQDN> is the fully qualified domain name of the NetAct cluster load balancer for
WebSphere. For more information, see Launching the NetAct Start Page.
b) Enter the Username and Password of the integration user on the NetAct login page, and click
Log In.
DN09118114 2-0
© 2016 Nokia Solutions and Networks
58
Integrating Flexi Multiradio BTS LTE to NetAct
Operations on NetAct after integration
c) Click Accept to accept the terms and conditions.
2. In NetAct Start Page, open CM Operations Manager by clicking Configuration → CM
Operations Manager.
3. In CM Operations Manager, click Upload → New Upload....
Expected outcome
The Upload dialog box opens.
4. In the Upload dialog, click the LTE tab, and then select the MRBTS-<instance ID> object or
OMS-<instance ID> object that you want to upload.
Note:
• If the MRBTS-<instance ID> object is selected, the Configuration Management
upload is for the corresponding Flexi Multiradio BTS LTE only.
• If the OMS-<instance ID> object is selected, the Configuration Management
upload is for all the Flexi Multiradio BTS LTE commissioned to the corresponding
LTE iOMS.
5. (Optional) In the Operation pane, enter a name and a description of the upload operation.
6. Select the Level of feedback.
• Summary
• Object
• Parameter
7. Click Start.
Expected outcome
The confirmation dialog opens.
8. Click Yes.
Expected outcome
The Upload dialog opens and the status of the upload operation changes to Started. After
successful operation, the status of the upload operation changes to Finished.
DN09118114 2-0
© 2016 Nokia Solutions and Networks
59
Integrating Flexi Multiradio BTS LTE to NetAct
Verifying Flexi Multiradio BTS LTE integration
8 Verifying Flexi Multiradio BTS LTE integration
This section describes how to verify the Flexi Multiradio BTS LTE integration.
Note:
To avoid impacting the running network environment, consider if you can perform the verifications before you proceed.
8.1 Verifying Element Management connectivity
This section describes how to verify the connectivity of LTE iOMS and Flexi Multiradio BTS LTE
Element Management towards NetAct.
8.1.1 Verifying Element Management connectivity of LTE iOMS
This section describes how to verify the connectivity of LTE iOMS Element Management towards
NetAct.
1. Log in to the NetAct Start Page as the integration user.
a) Enter the following URL in the address field of your internet browser: https://
<system_FQDN>/startpage
<system_FQDN> is the fully qualified domain name of the NetAct cluster load balancer for
WebSphere. For more information, see Launching the NetAct Start Page.
b) Enter the Username and Password of the integration user on the NetAct login page, and click
Log In.
c) Click Accept to accept the terms and conditions.
2. In NetAct Start Page, click Monitoring → Monitor.
3. In Monitor, open Object Explorer by selecting Tools → Managed Objects → Object Explorer.
Expected outcome
The Objects panel appears.
4. Verify the connectivity of Application Launcher by doing one of the following:
• For LTE 15A and earlier releases, right-click the OMS-<instance ID> object representing
the target network element, and select Element Management → Element Manager → OMS
EM.
DN09118114 2-0
© 2016 Nokia Solutions and Networks
60
Integrating Flexi Multiradio BTS LTE to NetAct
Verifying Flexi Multiradio BTS LTE integration
• For LTE 16 onwards, right-click the OMS-<instance ID> object representing the target
network element, and select Element Management → Element Manager → OMS
Application Launcher.
Expected outcome
The Application Launcher window opens.
Note: If the Parameter Tool is not visible in the Application Launcher, follow the
procedure in Configuring Parameter Tool in Application Launcher on page 35 to make the
Parameter Tool visible.
5. Verify the connectivity of Element Manager by doing one of the following:
• For LTE 15A and earlier releases, right-click the OMS-<instance ID> object representing
the target network element, and select Element Management → Element Manager → OMS
GUI EM.
• For LTE 16 onwards, right-click the OMS-<instance ID> object representing the target
network element, and select Element Management → Element Manager → OMS Web UI.
Note: If the Element Management launch is based on web page, disable the blocking
pop-up window function of the browser, and then add the LTE iOMS to the trusted sites of
the browser, or else the Element Management window might be blocked. Also if there is
any security warning, ignore it.
Expected outcome
The LTE iOMS Element Manager webpage window opens.
8.1.2 Verifying Element Management connectivity of Flexi Multiradio BTS LTE
This section describes how to verify the connectivity of Flexi Multiradio BTS LTE Element Management
towards NetAct.
1. Log in to the NetAct Start Page as the integration user.
a) Enter the following URL in the address field of your internet browser: https://
<system_FQDN>/startpage
<system_FQDN> is the fully qualified domain name of the NetAct cluster load balancer for
WebSphere. For more information, see Launching the NetAct Start Page.
b) Enter the Username and Password of the integration user on the NetAct login page, and click
Log In.
DN09118114 2-0
© 2016 Nokia Solutions and Networks
61
Integrating Flexi Multiradio BTS LTE to NetAct
Verifying Flexi Multiradio BTS LTE integration
c) Click Accept to accept the terms and conditions.
2. In NetAct Start Page, click Monitoring → Monitor.
3. In Monitor, open Object Explorer by selecting Tools → Managed Objects → Object Explorer.
Expected outcome
The Objects panel appears.
4. Verify the connectivity of Element Manager by doing one of the following:
• For LTE 15A and earlier releases, right-click the LNBTS object representing eNodeB target,
and select Element Management → Element Manager.
• For LTE 16 onwards, right-click the LNBTS object representing eNodeB target, select Element
Management, and then either select Element Manager (Read Only) or Element Manager
(Read Write).
Note: Element Manager can also be launched from MRBTS, FTM, or LNCEL object.
Note:
• For LTE 15A and earlier releases, for one eNodeB, only one Element Manager
launch is supported.
• For LTE 16 onwards, for one eNodeB, up to 5 Element Manager launches are
supported. For the Element Manager launches, only one has the Read and Write
permission and the others only have the Read permission.
Expected outcome
The site manager opens.
5. For FL16A and TL16A, verify the connectivity of ADMIN by right-clicking the LNBTS object
representing eNodeB target and selecting Element Management → ADMIN. For other network
element releases, skip this step.
Note:
• ADMIN can also be launched from MRBTS, FTM, or LNCEL object.
• For the same user, only one ADMIN launch is supported.
• Single Sign-On (SSO) is not supported for launching ADMIN from NetAct.
Expected outcome
The ADMIN opens.
DN09118114 2-0
© 2016 Nokia Solutions and Networks
62
Integrating Flexi Multiradio BTS LTE to NetAct
Verifying Flexi Multiradio BTS LTE integration
8.2 Verifying Fault Management connectivity
This section describes how to verify the connectivity of Flexi Multiradio BTS LTE Fault Management
towards NetAct.
Verify the Fault Management connectivity by sending a test alarm.
1. Log in to the integrated LTE iOMS as the Nemuadmin user.
2. Raise a test alarm by entering:
flexalarm --raise --sp=71137 --ap=/WAS/FSAlarmDBServer/
SolidWDforAlarmType --mo=/WAS/FSAlarmDBServer/SolidWDforAlarmType --se=4
3. Log in to the NetAct Start Page as the integration user.
a) Enter the following URL in the address field of your internet browser: https://
<system_FQDN>/startpage
<system_FQDN> is the fully qualified domain name of the NetAct cluster load balancer for
WebSphere. For more information, see Launching the NetAct Start Page.
b) Enter the Username and Password of the integration user on the NetAct login page, and click
Log In.
c) Click Accept to accept the terms and conditions.
4. In NetAct Start Page, click Monitoring → Monitor.
5. In Monitor, open Object Explorer by selecting Tools → Managed Objects → Object Explorer.
Expected outcome
The Objects panel appears.
6. In the Objects panel, right-click the OMS-<instance ID> object and select Find In → Alarm
List.
The Alarm List window opens.
7. Double-click the alarm with Alarm Number 71137.
The Alarm Details dialog opens.
8. In the Started field, check that the time is the time when you sent the test alarm.
9. Log in to the integrated LTE iOMS as the Nemuadmin user.
10. Cancel the test alarm by entering:
DN09118114 2-0
© 2016 Nokia Solutions and Networks
63
Integrating Flexi Multiradio BTS LTE to NetAct
Verifying Flexi Multiradio BTS LTE integration
flexalarm --clear --sp=71137 --ap=/WAS/FSAlarmDBServer/
SolidWDforAlarmType --mo=/WAS/FSAlarmDBServer/SolidWDforAlarmType --se=4
Expected outcome
In the Alarm List window of NetAct Monitor, the test alarm disappears.
8.3 Verifying Performance Management connectivity
This section describes how to verify the connectivity of Flexi Multiradio BTS LTE Performance
Management towards NetAct.
Prerequisites
Ensure there is performance data generated recently on LNBTS. For detailed instructions, see LNBTS
documentation.
1. Locate the Global ID of the MRBTS-<instance ID> object.
a) Log in to NetAct Start Page as the integration user.
b) In NetAct Start Page, click Monitoring → Monitor.
c) In Monitor, open Object Explorer by selecting Tools → Managed Objects → Object
Explorer.
Expected outcome
The Objects pane appears.
d) Right-click the MRBTS-<instance ID> object and select Properties.
e) In the Properties pane, check the value of the Global ID property.
2. Locate a raw measurement table with recent data arriving at NetAct.
a) Log in to the VM on which the etlcolmx service is running as the omc user.
b) Search for raw measurement table data by entering:
etlcolDBInfo.pl -t NOKLTE%RAW
Expected outcome
====================================================================
CONNECTING TO DATABASE
====================================================================
Get connection to database ... ok
-------------------------------------------------------------------NOKLTE%RAW - Checking database tables NOKLTE%RAW%
DN09118114 2-0
© 2016 Nokia Solutions and Networks
64
Integrating Flexi Multiradio BTS LTE to NetAct
Verifying Flexi Multiradio BTS LTE integration
------------------------------------------------------------------------------------------------------------------------------- Number of rows in raw measurement tables Name of the table
Yesterday
Today
Last entry
-----------------------------------------------------------…
<measurement table 1>
4639
5052 2015/04/09 12:45:00
…
*** Total number of rows in tables
: 0
*** Total number of rows in PV-views : 163459
*** Analysis executed: Thu Apr 9 10:33:30 EEST 2015
***
by user: omc
***
on host: <node name>
c) Choose one raw measurement table whose Today value is not 0.
3. Check database to see if there is data of the raw measurement table for the object.
a) Run sqlplus tool by entering:
sqlplus
b) Enter user name omc and the password.
c) Check the data availability of the raw table for the MRBTS-<instance ID> object by entering:
select * from <raw view name> where MRBTS_ID='<Global ID of the
object>';
where:
<raw view name> is the name of the raw measurement table selected in step 2.
<Global ID of the object> is the Global ID of the object located in step 1.
Expected outcome
An example output:
...
MRBTS_ID
---------BRM_ID
------------------------------------------------------------------------------FS_ID
------------------------------------------------------------------------------PERIOD_STA PERIOD_DURATION
FSUSED
---------- --------------- ---------100204
worker01
_dev_sda1
DN09118114 2-0
© 2016 Nokia Solutions and Networks
65
Integrating Flexi Multiradio BTS LTE to NetAct
10.04.2015
...
Verifying Flexi Multiradio BTS LTE integration
15
16
Check the output to see if the date is the same as the generated date of the latest performance
data on Flexi Multiradio BTS LTE. If yes, the Performance Management connectivity works
properly.
8.4 Verifying Configuration Management connectivity
This section describes how to verify the connectivity of Flexi Multiradio BTS LTE Configuration
Management towards NetAct.
1. Log in to the NetAct Start Page as the integration user.
a) Enter the following URL in the address field of your internet browser: https://
<system_FQDN>/startpage
<system_FQDN> is the fully qualified domain name of the NetAct cluster load balancer for
WebSphere. For more information, see Launching the NetAct Start Page.
b) Enter the Username and Password of the integration user on the NetAct login page, and click
Log In.
c) Click Accept to accept the terms and conditions.
2. Select Configuration → CM Editor.
Expected outcome
The 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 available.
Expected outcome
If the MRBTS, LNBTS, and child object hierarchy are visible under Actual Configuration, the
configuration management data flow from LTE iOMS and Flexi Multiradio BTS LTE to NetAct for
the newly integrated network element is verified.
DN09118114 2-0
© 2016 Nokia Solutions and Networks
66
Integrating Flexi Multiradio BTS LTE to NetAct
Using management functions for Flexi Multiradio BTS LTE
9 Using management functions for Flexi Multiradio
BTS LTE
This section describes where to find more information on how to use the management functions
supported for Flexi Multiradio BTS LTE.
For more information on how to use the management functions supported for Flexi Multiradio BTS
LTE, refer to respective documents.
• 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.
• For Optimizer, see Optimizing a Network Using Optimizer.
• For Audit Trail, see Audit Trail document set.
• For TraceViewer, see TraceViewer Help.
• For Network Element Backup and Restore Server, see Administering NetAct Network Element
Backup and Restore Server (NEBR Server).
• For Centralized Network Element User Management (CNUM), see Configuring CNUM in LTE network elements.
DN09118114 2-0
© 2016 Nokia Solutions and Networks
67
Integrating Flexi Multiradio BTS LTE to NetAct
Removing integration of LTE network elements from NetAct
10 Removing integration of LTE network elements from
NetAct
This section describes how to remove the integration of LTE network elements from NetAct.
Remove the network element integration in the following cases:
• Flexi Multiradio BTS LTE is moved to another NetAct or Network Management System.
• A re-integration is needed after Flexi Multiradio BTS LTE upgraded with massive changes.
• A rollback is needed for either the Flexi Multiradio BTS LTE or NetAct.
If LTE iOMS is integrated to another NetAct, removing the integration will unregister from the previous
NetAct but leave topology, alarms, and measurements behind.
Before removing Flexi Multiradio BTS LTE integration, ensure that a backup of the configuration is
available. For more information, see Deleting eNB from NetAct.
There are 2 scenarios when removing the integration of LTE network elements from NetAct.
• If you need to remove the Flexi Multiradio BTS LTE integration from NetAct and keep the LTE
iOMS integration to NetAct, see Removing Flexi Multiradio BTS LTE integration from NetAct on
page 68.
• If you need to remove the integration of both LTE iOMS and Flexi Multiradio BTS LTE from NetAct,
see Removing integration of both LTE iOMS and Flexi Multiradio BTS LTE from NetAct on page
70.
10.1 Removing Flexi Multiradio BTS LTE integration from NetAct
Prerequisites
Flexi Multiradio BTS LTE integration is removed from the topology of LTE iOMS. For more information,
contact the network element administrator.
1. Log in to the NetAct Start Page as the integration user.
a) Enter the following URL in the address field of your internet browser: https://
<system_FQDN>/startpage
<system_FQDN> is the fully qualified domain name of the NetAct cluster load balancer for
WebSphere. For more information, see Launching the NetAct Start Page.
b) Enter the Username and Password of the integration user on the NetAct login page, and click
Log In.
c) Click Accept to accept the terms and conditions.
2. Delete Configuration Management data.
a) From the NetAct Start Page, select Configuration → CM Operations Manager.
DN09118114 2-0
© 2016 Nokia Solutions and Networks
68
Integrating Flexi Multiradio BTS LTE to NetAct
Removing integration of LTE network elements from NetAct
Expected outcome
The CM Operations Manager application opens.
b) 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, and then from the Tools menu, select Workflow Engine
for Plan....
Expected outcome
The Workflow Engine dialog box appears.
c) In the MO(s) area, perform any of the following:
• Drag the MRBTS managed objects from CM Editor and drop them to the MO(s) area in
Workflow Engine.
• Copy the MRBTS managed objects from CM Editor and paste them to the MO(s) area in
Workflow Engine.
• 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 managed objects from CM Editor. To locate the managed objects:
1. In the NetAct Start Page, select Configuration → CM Editor.
2. In the left pane of CM Editor, expand Actual Configuration and PLMN-PLMN,
and then find MRBTS-<instance ID>.
d) From the Operation List drop-down list, select NE data deletion from Configurator.
e) (Optional) In the Name field, enter a name for the operation.
f) (Optional) In the Description field, enter a description for the operation.
g) In the Scope area, select the managed objects for which the operation needs to be done.
h) Click Start.
i) 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.
3. In NetAct Start Page, click Monitoring → Monitor.
4. In Monitor, open Object Explorer by selecting Tools → Managed Objects → Object Explorer.
DN09118114 2-0
© 2016 Nokia Solutions and Networks
69
Integrating Flexi Multiradio BTS LTE to NetAct
Removing integration of LTE network elements from NetAct
Expected outcome
The Objects panel appears.
5. In the Objects panel, expand the PLMN-PLMN object.
6. Delete the Fault Management data.
a) In the Objects panel, right-click the MRBTS-<instance ID> object, and then select Delete
All Alarms from Database → Delete Alarms For Object And Its Subnetwork.
b) When a confirmation dialog prompts, click Yes.
Expected outcome
In Ongoing Operations area, when progress bar shows 100% Completed, in Operations
History area, in Operation Status column, you can see Completed Successfully.
c) Repeat steps a and b for all the MRBTS objects to be removed integration.
7. Delete the managed objects.
a) Right-click the MRBTS-<instance ID> object and select Delete.
b) When a confirmation dialog prompts, click Yes.
c) Repeat steps a and b for all the MRBTS objects to be removed.
10.2 Removing integration of both LTE iOMS and Flexi Multiradio BTS
LTE from NetAct
1. Log in to the NetAct Start Page as the integration user.
a) Enter the following URL in the address field of your internet browser: https://
<system_FQDN>/startpage
<system_FQDN> is the fully qualified domain name of the NetAct cluster load balancer for
WebSphere. For more information, see Launching the NetAct Start Page.
b) Enter the Username and Password of the integration user on the NetAct login page, and click
Log In.
c) Click Accept to accept the terms and conditions.
2. Delete Configuration Management data.
a) From the NetAct Start Page, select Configuration → CM Operations Manager.
Expected outcome
The CM Operations Manager application opens.
DN09118114 2-0
© 2016 Nokia Solutions and Networks
70
Integrating Flexi Multiradio BTS LTE to NetAct
Removing integration of LTE network elements from NetAct
b) 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, and then from the Tools menu, select Workflow Engine
for Plan....
Expected outcome
The Workflow Engine dialog box appears.
c) In the MO(s) area, perform any of the following:
• Drag the OMS and MRBTS managed objects from CM Editor and drop them to the MO(s)
area in Workflow Engine.
• Copy the OMS and MRBTS managed objects from CM Editor and paste them to the
MO(s) area in Workflow Engine.
• 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 managed objects from CM Editor. To locate the managed objects:
1. In the NetAct Start Page, select Configuration → CM Editor.
2. In the left pane of CM Editor, expand Actual Configuration and PLMN-PLMN,
and then find OMS-<instance ID> and MRBTS-<instance ID>.
d) From the Operation List drop-down list, select NE data deletion from Configurator.
e) (Optional) In the Name field, enter a name for the operation.
f) (Optional) In the Description field, enter a description for the operation.
g) In the Scope area, select the managed objects for which the operation needs to be done.
h) Click Start.
i) 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.
3. In NetAct Start Page, click Monitoring → Monitor.
4. In Monitor, open Object Explorer by selecting Tools → Managed Objects → Object Explorer.
DN09118114 2-0
© 2016 Nokia Solutions and Networks
71
Integrating Flexi Multiradio BTS LTE to NetAct
Removing integration of LTE network elements from NetAct
Expected outcome
The Objects panel appears.
5. In the Objects panel, expand the PLMN-PLMN object.
6. Unregister the LTE iOMS.
a) In the Objects panel, right-click the OMS-<instance ID> object, and select Element
Management → Element Manager → OMS Application Launcher.
Expected outcome
The Application Launcher window appears.
Note: If the message JAVA VIRTUAL MACHINE VERSION IS NOT SUPPORTED
appears, you may ignore it by pressing I on the keyboard.
b) Double-click Parameter Tool.
Note: If the Parameter Tool is not visible in the Application Launcher, follow the
procedure in Configuring Parameter Tool in Application Launcher on page 35 to make
the Parameter Tool visible.
Expected outcome
The Parameter Tool window appears.
c) Select fsClusterId=ClusterRoot → fsFragmentId=NWI3 → fsFragmentId=mediator.
If there are multiple items under fsFragmentId=mediator, select the item that has an Active
Value of true for fsnwi3configurationActive.
d) In the right pane, remove the value designated for fsnwi3registrationServiceIOR.
To remove the value from the Active Value column of fsnwi3registrationServiceIOR, doubleclick the value to display the View/Edit Attribute Value window, clear the value after IOR: in
the window, and then click OK.
Expected outcome
The Active Value of fsnwi3registrationServiceIOR is updated to IOR:.
e) Close the Parameter Tool window and the Application Launcher window.
f) Log in to LTE iOMS as the Nemuadmin user through SSH.
g) Using the su - command, switch to root user and restart NWI3Adapter by entering:
fshascli -rn /NWI3Adapter
DN09118114 2-0
© 2016 Nokia Solutions and Networks
72
Integrating Flexi Multiradio BTS LTE to NetAct
Removing integration of LTE network elements from NetAct
Expected outcome
The NWI3Adapter restarts and the changes are saved.
7. Delete the Fault Management data.
a) In the Objects panel, right-click the MRBTS-<instance ID> object, and then select Delete
All Alarms from Database → Delete Alarms For Object And Its Subnetwork.
b) When a confirmation dialog prompts, click Yes.
Expected outcome
In Ongoing Operations area, when progress bar shows 100% Completed, in Operations
History area, in Operation Status column, you can see Completed Successfully.
c) Repeat steps a and b for all the MRBTS objects to be removed.
d) In the Objects panel, right-click the OMS-<instance ID> object, and then select Delete All
Alarms from Database → Delete Alarms For Object And Its Subnetwork.
e) When a confirmation dialog prompts, click Yes.
Expected outcome
In Ongoing Operations area, when progress bar shows 100% Completed, in Operations
History area, in Operation Status column, you can see Completed Successfully.
8. Delete the managed objects.
a) Right-click the MRBTS-<instance ID> object and select Delete.
b) When a confirmation dialog prompts, click Yes.
c) Repeat steps a and b for all the MRBTS objects to be removed.
d) Right-click the OMS-<instance ID> object and select Delete.
e) When a confirmation dialog prompts, click Yes.
DN09118114 2-0
© 2016 Nokia Solutions and Networks
73
Integrating Flexi Multiradio BTS LTE to NetAct
Troubleshooting integration problems
11 Troubleshooting integration problems
11.1 NEIW execution errors
This section describes how to troubleshoot the NE Integration Wizard execution errors.
Problem
During the integration with NE Integration Wizard (NEIW), execution errors happen with error logs.
Possible causes
• The parameters are incorrect.
• NWI3 Access credential is incorrect.
Solution
1. Check if the parameters are filled correctly. For more information, see Integration operations in
NEIW on page 47.
2. Check if the NWI3 Access credential is created properly. For more information, see Managing Flexi
Multiradio BTS LTE credentials on page 28.
11.2 Integration data upload failure
This section describes how to troubleshoot the integration data upload failure.
Problem
The integration process is not successful.
Possible causes
• NWI3 Access is not created in NEAC.
• User name or password of NWI3 Access is not configured correctly in NEAC.
• The NWI3 service of NetAct is not active.
• NWI3Adapter of LTE iOMS is locked.
Solution
1. If NWI3 Access for LTE iOMS has not been created, create it. For more information, see Managing
Flexi Multiradio BTS LTE credentials on page 28.
2. If NWI3 Access has already been created but the problem still happens, recreate the NWI3
Access.
a) Log in to NetAct Start Page as the integration user.
DN09118114 2-0
© 2016 Nokia Solutions and Networks
74
Integrating Flexi Multiradio BTS LTE to NetAct
Troubleshooting integration problems
b) In NetAct Start Page, select Security → Network Element Access Control.
c) Check if NWI3 Access has the proper credential. If the credential is not correct, proceed to the
next step.
d) Select NWI3 Access, and click Delete.
e) To recreate NWI3 Access for LTE iOMS, refer to Creating Flexi Multiradio BTS LTE credentials
on page 30.
f) Execute integration data upload. For more information, see Executing integration data upload
on page 53.
3. Check the nwi3 service status in NetAct. For more information, see Preparing NetAct.
4. Check the NWI3Adapter status and unlock LTE iOMS if it is locked.
a) Log in to LTE iOMS as the Nemuadmin user.
b) Check the NWI3Adapter status by entering:
fshascli -s /NWI3Adapter
Expected outcome
An example output:
/NWI3Adapter:
administrative(LOCKED)
operational(DISABLED)
usage(IDLE)
procedural(NOTINITIALIZED)
availability()
unknown(FALSE)
alarm()
c) If NWI3Adapter is locked, unlock it by entering:
fshascli -u /NWI3Adapter
Expected outcome
/NWI3Adapter is unlocked successfully
d) To restart NWI3Adapter, enter the following command:
fshascli -rn /NWI3Adapter
Expected outcome
/NWI3Adapter is restarted successfully
DN09118114 2-0
© 2016 Nokia Solutions and Networks
75
Integrating Flexi Multiradio BTS LTE to NetAct
Troubleshooting integration problems
e) Launch Integration Data Upload again.
11.3 Element Managements of Flexi Multiradio BTS LTE not launched
This section describes how to troubleshoot the case of Element Management launch failure of Flexi
Multiradio BTS LTE.
Problem
The Element Management cannot be launched.
Possible Causes
• After successfully deploying NetAct fast pass (formerly INES) compatible metadata, Monitor is not
restarted.
• Node Manager is not installed or configured properly.
• The required credentials are not created in NEAC.
• Element manager is not configured properly.
• Prerequisites for Element Management are not done on every Node Manager Citrix Virtual Delivery Agent (VDA) server.
Solution
1. Restart Monitor to load metadata.
2. Check Node Manager installation and configuration. For more information, contact your NetAct
administrator.
3. Check if the required credentials are created. For more information, see Managing Flexi Multiradio
BTS LTE credentials on page 28.
4. Check if the element manager is configured properly. For more information, refer to Preparing
applications for Element Management on page 31.
5. Check if all operations in Preparing applications for Element Management on page 31 are done on
all Node Manager Citrix Virtual Delivery Agent (VDA) servers.
11.4 Alarms from Flexi Multiradio BTS LTE not received
This section describes how to troubleshoot the case of not receiving alarms from Flexi Multiradio BTS
LTE.
Problem
No alarm (except the internal alarms, such as Alarm 9255 and Alarm 9047) is displayed in Alarm List
or the test alarm cannot reach NetAct.
Possible causes
DN09118114 2-0
© 2016 Nokia Solutions and Networks
76
Integrating Flexi Multiradio BTS LTE to NetAct
Troubleshooting integration problems
• Integration user permission is incorrect.
• Firewall is not properly set up.
• fm_pipe service is not started in NetAct.
• nwi3 service is not started in NetAct.
• The IP connectivity between Flexi Multiradio BTS LTE and NetAct does not work.
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 the integration user permission. For more information, see Managing NetAct user for Flexi
Multiradio BTS LTE integration engineer on page 21.
2. Check the firewall settings. For more information, see Setting up firewall rules on page 40.
3. Check the fm_pipe service status in NetAct. For more information, see Preparing NetAct.
4. Check the nwi3 service status in NetAct. For more information, see Preparing NetAct.
5. Check the IP connectivity between Flexi Multiradio BTS LTE and NetAct. For more information, see
Checking NetAct connectivity towards Flexi Multiradio BTS LTE on page 27.
11.5 Performance data of Flexi Multiradio BTS LTE not found
This section describes how to troubleshoot the case of not finding performance data from Flexi
Multiradio BTS LTE.
Problem
Performance Management (PM) data is missing in Performance Manager.
Possible Cause
• For LTE16A onwards, NetAct fast pass (formerly INES) compatible metadata of the network element is not deployed successfully.
• Before successfully deploying NetAct fast pass (formerly INES) compatible metadata, Performance Manager GUI is already open.
• PM pipe is not running.
• Some ETLOAD processes stopped working.
• Invalid OMeS files are received.
DN09118114 2-0
© 2016 Nokia Solutions and Networks
77
Integrating Flexi Multiradio BTS LTE to NetAct
Troubleshooting integration problems
Solution
1. Ensure that NetAct fast pass (formerly INES) compatible metadata of the network element is
deployed successfully. For more information, see Deploying NetAct fast pass (formerly INES)
compatible metadata on page 23.
2. Restart Performance Manager to load metadata.
3. Check the etlcolmx service status in NetAct. For more information, see Preparing NetAct.
4. For ETLOAD-related issues, refer to ETLOAD processes failures.
5. For invalid OMeS, refer to Invalid structure in the input OMeS file.
11.6 Configuration Management upload failure
This section describes how to troubleshoot the case of Flexi Multiradio BTS LTE Configuration
Management upload failure.
Problem
Configuration Management upload fails.
Possible causes
• The HTTPS protocol is used but the required certificates are not installed.
• The NWI3 service is not started in NetAct.
• Integration user permission is incorrect.
Solution
1. Make sure the required certificates are installed. For more information, see Configuring
certifications on network elements.
2. Check the nwi3 service status in NetAct. For more information, see Preparing NetAct.
3. Ensure that the appropriate user permission is granted. For more information, see Managing
NetAct user for Flexi Multiradio BTS LTE integration engineer on page 21.
DN09118114 2-0
© 2016 Nokia Solutions and Networks
78
Integrating Flexi Multiradio BTS LTE to NetAct
Upgrading integration for LTE network elements
12 Upgrading integration for LTE network elements
This section describes how to upgrade integration for LTE network elements.
Prerequisites
1. Old LTE iOMS and Flexi Multiradio BTS LTE releases are integrated to NetAct.
Note: For LTE 16 and earlier releases which are already integrated to NetAct, if you
need to upgrade them to LTE16A and onward releases, before upgrading, you must
deploy NetAct fast pass (formerly INES) compatible metadata on NetAct and enable
pre-aggregation. For more information, see Deploying NetAct fast pass (formerly INES)
compatible metadata on page 23 and Enabling pre-aggregation on page 25.
2. LTE iOMS or Flexi Multiradio BTS LTE or both are upgraded successfully to the releases that are
supported by NetAct.
• After LTE iOMS is upgraded, the DNS and NTP configurations on it remain unchanged.
For more information about the DNS and NTP configurations on LTE iOMS, see Integration
operations on OMS on page 50.
• After Flexi Multiradio BTS LTE is upgraded, ensure that the BTS Site Manager for the new
Flexi Multiradio BTS LTE release is installed. For more information, see Installing BTS Site
Manager in Node Manager Citrix Virtual Delivery Agent (VDA) server on page 36.
There are 3 scenarios when upgrading integration for LTE network elements.
• If LTE iOMS is upgraded, you can upgrade LTE iOMS integration by performing the steps in the
section.
• If Flexi Multiradio BTS LTE is upgraded, you can upgrade Flexi Multiradio BTS LTE integration by
performing the steps in the section.
• If both LTE iOMS and Flexi Multiradio BTS LTE are upgraded, you can upgrade the integration of
both LTE iOMS and Flexi Multiradio BTS LTE by performing the steps in the section.
1. Log in to the NetAct Start Page as the integration user.
a) Enter the following URL in the address field of your internet browser: https://
<system_FQDN>/startpage
<system_FQDN> is the fully qualified domain name of the NetAct cluster load balancer for
WebSphere. For more information, see Launching the NetAct Start Page.
b) Enter the Username and Password of the integration user on the NetAct login page, and click
Log In.
c) Click Accept to accept the terms and conditions.
2. In NetAct Start Page, click Monitoring → Monitor.
3. In Monitor, open Object Explorer by selecting Tools → Managed Objects → Object Explorer.
DN09118114 2-0
© 2016 Nokia Solutions and Networks
79
Integrating Flexi Multiradio BTS LTE to NetAct
Upgrading integration for LTE network elements
Expected outcome
The Objects panel appears.
4. Right-click the OMS-<instance ID> object and select Element Management → Integration
Data Upload.
Expected outcome
In the Ongoing Operations area, after the Integration Data Upload progress bar disappears,
check if Completed Successfully shows in the Operation Status in the Operations History
area.
If the integration data upload fails, see Integration data upload failure on page 74.
5. Execute Configuration Management upload.
For more information, see Executing Configuration Management upload on page 58. If the upload
fails, see Configuration Management upload failure on page 78.
6. Check the value of the Release property.
• To upgrade LTE iOMS integration, right-click the OMS-<instance ID> object, select
Properties, and check the value of the Release property.
• To upgrade Flexi Multiradio BTS LTE integration, right-click the MRBTS-<instance ID>
object, select Properties, and check the value of the Release property.
Expected outcome
For the network elements that are upgraded, the value of the Release property is updated with the
new release.
7. Verify Element Management connectivity.
• For LTE iOMS, see Verifying Element Management connectivity of LTE iOMS on page 60.
• For Flexi Multiradio BTS LTE, see Verifying Element Management connectivity of Flexi
Multiradio BTS LTE on page 61.
If the Element Management connectivity fails, see Element Managements of Flexi Multiradio BTS
LTE not launched on page 76.
DN09118114 2-0
© 2016 Nokia Solutions and Networks
80
Integrating Flexi Multiradio BTS LTE to NetAct
Migrating AoM plans and templates
13 Migrating AoM plans and templates
This section describes how to migrate AoM plans and templates created for the old Flexi Multiradio
BTS LTE releases.
This section is optional. If there are AoM plans and templates created for the old Flexi Multiradio BTS
LTE releases, and you intend to use them for the new releases, migrate them manually.
13.1 Migrating AoM plans
This section describes how to migrate AoM plans created for the old Flexi Multiradio BTS LTE
releases.
1. Log in to the NetAct Start Page as the integration user.
a) Enter the following URL in the address field of your internet browser: https://
<system_FQDN>/startpage
<system_FQDN> is the fully qualified domain name of the NetAct cluster load balancer for
WebSphere. For more information, see Launching the NetAct Start Page.
b) Enter the Username and Password of the integration user on the NetAct login page, and click
Log In.
c) Click Accept to accept the terms and conditions.
2. In NetAct Start Page, open Administration of Measurement application by clicking Reporting →
Administration of Measurements.
3. Switch to Plans tab.
4. Click Upload.
5. In the Manual Upload dialog, select the adaptation of Flexi Multiradio BTS LTE and select the MO
type in the Select MO class drop-down list. Select the Managed Objects and click Upload.
6. Switch to Plans tab.
7. Check the checkbox of the AoM plans which you want to migrate and click Modify....
Note: You cannot modify the UPL plans. For more information on UPL, see Uploaded
plan.
8. Update the plan by adding new measurements to it from the newer Flexi Multiradio BTS LTE
releases.
DN09118114 2-0
© 2016 Nokia Solutions and Networks
81
Integrating Flexi Multiradio BTS LTE to NetAct
Migrating AoM plans and templates
Note: If you cannot find the same measurement type in Measurement type field, the
measurement type is not supported anymore by new Flexi Multiradio BTS LTE release.
9. Click Add to List.
10. In Available measurement types field, check the checkbox of the measurement type for the old
Flexi Multiradio BTS LTE releases, and then click Remove.
11. Go to third page of plan creation.
12. In Define managed objects field, select the object class of the new Flexi Multiradio BTS LTE
releases from the Supported class drop-down list.
13. In Measurement types field, check the checkbox of newly added measurement types, and then
select the same managed objects as that of the old Flexi Multiradio BTS LTE releases from the
Managed objects drop-down list.
14. Click Add to list.
15. Click Save.
16. Switch to Plans tab.
17. Check the checkbox of the updated AoM plans and click Activate.
13.2 Migrating AoM templates
This section describes how to migrate AoM templates created for the old Flexi Multiradio BTS LTE
releases.
1. Log in to the NetAct Start Page as the integration user.
a) Enter the following URL in the address field of your internet browser: https://
<system_FQDN>/startpage
<system_FQDN> is the fully qualified domain name of the NetAct cluster load balancer for
WebSphere. For more information, see Launching the NetAct Start Page.
b) Enter the Username and Password of the integration user on the NetAct login page, and click
Log In.
DN09118114 2-0
© 2016 Nokia Solutions and Networks
82
Integrating Flexi Multiradio BTS LTE to NetAct
Migrating AoM plans and templates
c) Click Accept to accept the terms and conditions.
2. In NetAct Start Page, open Administration of Measurement application by clicking Reporting →
Administration of Measurements.
3. Switch to Templates tab.
4. Check the checkbox of the AoM templates which you want to migrate and click Modify....
5. In Define schedule item (measurement and schedule) field, select the adaptation of the new
Flexi Multiradio BTS LTE releases from the Adaptation drop-down list.
6. Select the measurement types from the Measurement type field, and then set the same schedule
for each measurement type as that of the old one.
Note: If you cannot find the same measurement type in Measurement type field, the
measurement type is not supported anymore by new Flexi Multiradio BTS LTE release.
7. Click Add to List.
8. In Available measurement types field, check the checkbox of the measurement type for the old
Flexi Multiradio BTS LTE releases, and then click Remove.
9. Click Save.
Note: You can create new templates for the newer release instead of modifying the
existing templates.
DN09118114 2-0
© 2016 Nokia Solutions and Networks
83