Nokia Siemens Networks LTE
Radio Access, Rel. RL10,
Operating Documentation,
Issue 01, Doc Change Delivery
2
Integrating Flexi Multiradio BTS LTE to
NetAct
DN0968394
Issue 01A
Approval Date 2010-06-21
Integrating Flexi Multiradio BTS LTE to NetAct
The information in this document is subject to change without notice and describes only the
product defined in the introduction of this documentation. This documentation is intended for the
use of Nokia Siemens Networks customers only for the purposes of the agreement under which
the document is submitted, and no part of it may be used, reproduced, modified or transmitted
in any form or means without the prior written permission of Nokia Siemens Networks. The
documentation has been prepared to be used by professional and properly trained personnel,
and the customer assumes full responsibility when using it. Nokia Siemens Networks welcomes
customer comments as part of the process of continuous development and improvement of the
documentation.
The information or statements given in this documentation concerning the suitability, capacity,
or performance of the mentioned hardware or software products are given "as is" and all liability
arising in connection with such hardware or software products shall be defined conclusively and
finally in a separate agreement between Nokia Siemens Networks and the customer. However,
Nokia Siemens Networks has made all reasonable efforts to ensure that the instructions
contained in the document are adequate and free of material errors and omissions. Nokia
Siemens Networks will, if deemed necessary by Nokia Siemens Networks, explain issues which
may not be covered by the document.
Nokia Siemens Networks will correct errors in this documentation as soon as possible. IN NO
EVENT WILL Nokia Siemens Networks BE LIABLE FOR ERRORS IN THIS DOCUMENTATION OR FOR ANY DAMAGES, INCLUDING BUT NOT LIMITED TO SPECIAL, DIRECT, INDIRECT, INCIDENTAL OR CONSEQUENTIAL OR ANY LOSSES, SUCH AS BUT NOT LIMITED
TO LOSS OF PROFIT, REVENUE, BUSINESS INTERRUPTION, BUSINESS OPPORTUNITY
OR DATA,THAT MAY ARISE FROM THE USE OF THIS DOCUMENT OR THE INFORMATION
IN IT.
This documentation and the product it describes are considered protected by copyrights and
other intellectual property rights according to the applicable laws.
The wave logo is a trademark of Nokia Siemens Networks Oy. Nokia is a registered trademark
of Nokia Corporation. Siemens is a registered trademark of Siemens AG.
Other product names mentioned in this document may be trademarks of their respective
owners, and they are mentioned for identification purposes only.
Copyright © Nokia Siemens Networks 2010. All rights reserved
f
Important Notice on Product Safety
Elevated voltages are inevitably present at specific points in this electrical equipment.
Some of the parts may also have elevated operating temperatures.
Non-observance of these conditions and the safety instructions can result in personal
injury or in property damage.
Therefore, only trained and qualified personnel may install and maintain the system.
The system complies with the standard EN 60950 / IEC 60950. All equipment connected
has to comply with the applicable safety standards.
The same text in German:
Wichtiger Hinweis zur Produktsicherheit
In elektrischen Anlagen stehen zwangsläufig bestimmte Teile der Geräte unter Spannung. Einige Teile können auch eine hohe Betriebstemperatur aufweisen.
Eine Nichtbeachtung dieser Situation und der Warnungshinweise kann zu Körperverletzungen und Sachschäden führen.
Deshalb wird vorausgesetzt, dass nur geschultes und qualifiziertes Personal die
Anlagen installiert und wartet.
Das System entspricht den Anforderungen der EN 60950 / IEC 60950. Angeschlossene
Geräte müssen die zutreffenden Sicherheitsbestimmungen erfüllen.
2
Id:0900d8058078e3d9
DN0968394
Issue 01A
Integrating Flexi Multiradio BTS LTE to NetAct
Table of Contents
This document has 26 pages.
1
1.1
1.2
About this document . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6
NetAct compatibility and capacity information . . . . . . . . . . . . . . . . . . . . . 6
Terms. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6
2
2.1
2.1.1
2.1.2
2.2
Introduction to the LTE BTS integration. . . . . . . . . . .
Integration principles . . . . . . . . . . . . . . . . . . . . . . . . .
Connection principles . . . . . . . . . . . . . . . . . . . . . . . .
Management interfaces and protocols. . . . . . . . . . . .
Integration procedure. . . . . . . . . . . . . . . . . . . . . . . . .
3
3.1
3.1.1
3.1.2
3.2
3.2.1
3.2.2
Preliminary tasks . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Reviewing the system requirements . . . . . . . . . . . . . . . . . . . . . . . . . . .
NetAct . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
OMS. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Adding managed objects to the DNS. . . . . . . . . . . . . . . . . . . . . . . . . . .
Adding OMS to DNS with BIND . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Adding OMS to DNS with NameSurfer . . . . . . . . . . . . . . . . . . . . . . . . .
10
10
10
12
12
13
13
4
4.1
4.1.1
4.1.2
4.2
4.3
Configuring the OMS for O&M connection. . . . . . . . . . . . . . . . . . . . . . .
Configuring the OMS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Configuring OMS system identifier . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Configuring NetAct interface with OMS . . . . . . . . . . . . . . . . . . . . . . . . .
Checking the IP configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Configuring NTP services . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
14
14
14
14
16
17
5
5.1
5.2
5.3
5.3.1
Configuring NetAct for OMS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18
Checking Maintenance Region Service Users in NetAct . . . . . . . . . . . . 18
Creating managed objects for the OMS. . . . . . . . . . . . . . . . . . . . . . . . . 20
Providing users with access to NetAct applications and network elements
21
Providing users access via service user management . . . . . . . . . . . . . 21
6
6.1
6.2
6.3
6.4
Verifying the integration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Verifying IP connectivity. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Verifying the EM launch . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Verifying Fault Management data flow. . . . . . . . . . . . . . . . . . . . . . . . . .
Verifying the Performance Management data flow . . . . . . . . . . . . . . . .
7
Where to find more information . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 25
......
......
......
......
......
.......
.......
.......
.......
.......
..
..
..
..
..
8
8
8
9
9
23
23
23
23
24
Index . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 26
DN0968394
Issue 01A
Id:0900d8058078e3d9
3
Integrating Flexi Multiradio BTS LTE to NetAct
List of Figures
Figure 1
Figure 2
Figure 3
Figure 4
4
Operations and Maintenance connections between NetAct and LTE BTS.
8
Integration procedure . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9
Heartbeat Parameter . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16
Object Model. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 21
Id:0900d8058078e3d9
DN0968394
Issue 01A
Integrating Flexi Multiradio BTS LTE to NetAct
List of Tables
Table 1
Table 2
Table 3
Table 4
Table 5
DN0968394
Issue 01A
Terms . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6
Information needed for adding managed objects to the DNS . . . . . . . . 12
Information needed for adding OMS to DNS with BIND . . . . . . . . . . . . 13
Maintenance Region Service users needed during OMS integration . . 19
Variable list . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 23
Id:0900d8058078e3d9
5
About this document
Integrating Flexi Multiradio BTS LTE to NetAct
1 About this document
This document describes how to integrate an Operations and Management Server
(OMS) to Nokia Siemens Networks NetAct and create eNodeB (LNBTS) object in
NetAct. For integration of eNodeB to OMS, see Commissioning Flexi Multiradio BTS
LTE.
This customer document is written for the management and the integration personnel of
an operator.
The information in this document is valid for LTE OMS LTO1.0 versions. Do not use this
document with other LTE OMS versions. Once the integration is completed, NetAct can
perform fault and element management functions on the OMS from a centralised location.
For information on other related Nokia Siemens Networks documentation, see chapter
Where to find more information.
1.1
NetAct compatibility and capacity information
For information on NetAct system and capacity, and the compatibility between NetAct
and network element releases, see the NetAct Compatibility and Capacity Information
document.
1.2
Terms
This section provides a brief list of the terms used in this document. If a term or word
does not appear in the section, see the Glossary.
Term
Explanation
CUAA
Centralised User Authentication and Authorisation
DCN
Data Communication Network
eNB
evolved NodeB
FM
Fault Management
FTM
Flexi Transport Module
GOMS
Managed object for OMS in the NetAct topology database
GUIS
Graphical User Interface Server
IP-BTS
IP Base Transceiver Station
IPRC
IP Radio Controller
LNBTS
LTE Base Station
LNCEL
LTE Cell
MF
Mediation Function
MR
Maintenance Region
O&M
Operation and Maintenance
OMS
Operations and Management Server
SSH
Secure Shell
Table 1
6
Terms
Id:0900d8058079014d
DN0968394
Issue 01A
Integrating Flexi Multiradio BTS LTE to NetAct
About this document
g GOMS, OMS and iOMS mentioned in this document refer to the same object, and
they are names used in different occasions.
DN0968394
Issue 01A
Id:0900d8058079014d
7
Introduction to the LTE BTS integration
Integrating Flexi Multiradio BTS LTE to NetAct
2 Introduction to the LTE BTS integration
This chapter provides a general description of the principles of connecting a newly commissioned LTE BTS to NetAct.
The integration procedure consists of a series of ordered tasks that allow you to connect
an OMS to NetAct.
2.1
2.1.1
Integration principles
Connection principles
It is recommended that the local network elements are connected to NetAct with
LAN.The connections among NetAct, OMS and eNB are based on IP protocols. For
establishing WAN connections between NetAct and the remote network elements, there
are several different possibilities.
Figure 1
8
Operations and Maintenance connections between NetAct and LTE BTS
Id:0900d8058079014d
DN0968394
Issue 01A
Integrating Flexi Multiradio BTS LTE to NetAct
2.1.2
Introduction to the LTE BTS integration
Management interfaces and protocols
NWI3 is a CORBA-based Nokia Siemens Networks proprietary management interface
between network management system (NMS) and mediation devices or network
elements for 3G and 4G networks.
Fault Management
The FM interface of OMS is plain CORBA-based Nokia Siemens Networks proprietary
management interface.
2.2
Integration procedure
To successfully integrate an OMS, first you need to complete the preliminary tasks, then
configure the OMS, and finally verify the integration.
The following flowchart covers the tasks that need to be carried out when integrating a
new OMS network element:
Start
Configure the OMS
Review the system
requirements
Add managed
objects to the DNS
Configure OMS
for O&M connection
Check the MR
service users
End
Create managed
objects
Task is done in:
OMS
NetAct
Figure 2
DN0968394
Issue 01A
Integration procedure
Id:0900d8058079014d
9
Preliminary tasks
Integrating Flexi Multiradio BTS LTE to NetAct
3 Preliminary tasks
This chapter lists the tasks you must complete before beginning the integration.
3.1
Reviewing the system requirements
This section covers the system requirements.
3.1.1
NetAct
Before beginning the integration, make sure the NetAct environment is configured and
functioning properly:
•
Use the Diagnostic Tool to check that all packages, processes, and the system
platform are up and running properly.
For instructions, see Testing the System Platform.
Make also sure the following information is available:
•
•
•
•
•
•
The NetAct users and passwords for:
• omc and root users for integration tasks and additionally a non-sysop user for
integration verification
The network element local IDs and passwords:
• Administrator and local network element user account to be used in service user
definitions
Service user accounts:
• user IDs, passwords and groups for service types, in planned Maintenance
Region
Network element IP addresses:
• for local and remote management purpose
NetAct cluster IP addresses, for following services:
• Configured ntp servers in NetAct:
• Source for external NTP server synchronization: ldapacmx.pl ntpServer
• Check configured internal primary and secondary nodes from
/etc/ntp.conf on connectivity cell nodes, or execute command ntpq np on one of the connectivity cell nodes.
• Configured name servers in NetAct:
• Primary and secondary name servers are defined in connectivity cell nodes
in /etc/resolv.conf files.
NetAct cluster IP and FQDN addresses for all available nodes and packages available:
• Use LDAP management tools, such as LDAPAccess.pl to query out node and
package addresses.
For instructions, give LDAPAccess.pl -h command, or see chapter LDAP
directory management in System Administration Principles.
g In several procedures you are required to log into the Connectivity Server. It is
possible to find out which node the Connectivity Server is by entering the following
command:
10
Id:0900d8058079014d
DN0968394
Issue 01A
Integrating Flexi Multiradio BTS LTE to NetAct
Preliminary tasks
[omc]$ hamgrmx.pl status
g The registration account username should be neregn. The registration account
password should be the password of the neregn user you have previously configured in NetAct.
To find out the IP address of the osscore2 package and the primary nodes for db
and system packages (Connectivity Server & Data Server)
1. For a full list of options available with the ldapacmx.pl script, enter:
ldapacmx.pl -help
2. To find out the active package names, enter:
[omc]$ /usr/bin/nokia/IFWGetData.pl --PackageList
Example output:
system
db
message
base-gene
dns
cmessage
httpd
osscore2
nww
rac
slt
rep
rep2
3. To interrogate the FQDN of the osscore2 package, enter:
[omc]$ ldapacmx.pl -sgPkgHost osscore2
4. To interrogate the FQDNs of primary nodes (Data Servers) for db and system packages, enter:
[omc]$ ldapacmx.pl -pkgPrimaryNode db
5. To interrogate the IP addresses for the FQDNs, by enter:
[omc]$ nslookup <FQDN>
where the FQDN is, as given in the outputs above:
•
•
FQDN of the osscore2 package
FQDN of the Data Server
6. Note down these IP addresses, because you need them during the network element
integration.
To get the IOR string
You need to complete the following task to fetch the IOR string. The IOR is needed in
the network element for registering it to the NetAct database.
DN0968394
Issue 01A
Id:0900d8058079014d
11
Preliminary tasks
Integrating Flexi Multiradio BTS LTE to NetAct
1. Retrieve the IOR string from Corba Naming Service in NetAct. Enter the following
command:
nsconfmx cat
corbaname:rir:#NokiaOSS/local/subsystems/NW3N3C/NWI3_Registr
ationService/i0
3.1.2
OMS
Before you begin the integration, ensure that the OMS meets the following requirements
and that the information required during the integration procedure is available:
•
•
•
•
•
3.2
The administrator username and password for accessing the network element configuration are available.
OMS has been integrated to the IP network.
The IP address of the OMS is known for the Element Manager.
The correct version of the OMS has been installed.
The DNS client has been configured in OMS.
Adding managed objects to the DNS
Domain Name Service (DNS) is a distributed database containing naming information
on network elements (NEs). The system provides the service of converting hostnames
into IP addresses and vice versa. Before you start to add OMS to the DNS, familiarise
yourself with the DNS management concepts and the list of required zones. For more
information, see DNS Management Principles.
The IP address added to the DNS must be the IP address of the OMS server.
The basic procedure of adding OMS to the DNS zone includes the following tasks:
1. Check whether the needed zone already exists. For more information, see
Managing the DNS in NetAct.
2. Add the OMS to the zone using Name Surfer or BIND. For more information, see
Managing the DNS in NetAct.
The following information is needed for adding managed objects to the NetAct DNS. The
managed object for OMS is GOMS.
Object
IP address of the
O&M unit
DNS zone
Naming of the
object
OMS
IP address of the
OMS
For example:
nss.netact.done.fi
GOMS <id>
Table 2
Information needed for adding managed objects to the DNS
g If you are unsure whether the primary Name Servers are implemented with BIND or
NameSurfer in your system, log into the NetAct Start application. Check if the NameSurfer application is present in the Administration menu. If yes, then NameSurfer is
in use in the cluster.
12
Id:0900d8058079014d
DN0968394
Issue 01A
Integrating Flexi Multiradio BTS LTE to NetAct
3.2.1
Preliminary tasks
Adding OMS to DNS with BIND
If you want to add elements to the DNS with BIND, you need to use a text editor, such
as vi. In addition, you must have the following information available:
Object
IP address of the
O&M unit
DNS zone
Naming of the
object
OMS
IP address of the
OMS
DNS zone of the
OMS
OMS host name
Table 3
Information needed for adding OMS to DNS with BIND
To add OMS to the DNS with BIND, see Host (A) (in Section Using BIND to edit data in
DNS) in Managing the DNS in NetAct.
3.2.2
Adding OMS to DNS with NameSurfer
If you have NameSurfer, you can configure the data on the DNS server from a GUI.
To add an OMS to DNS with NameSurfer, see Host (A) (in Section Using NameSurfer
to edit data in DNS) in Managing the DNS in NetAct.
DN0968394
Issue 01A
Id:0900d8058079014d
13
Configuring the OMS for O&M connection
Integrating Flexi Multiradio BTS LTE to NetAct
4 Configuring the OMS for O&M connection
This chapter describes the tasks that you must complete in OMS to enable dataflow
between NetAct and OMS.
4.1
4.1.1
Configuring the OMS
Configuring OMS system identifier
This procedure configures the system identifier of OMS. The systemId must have the
same value as the identifier of the network element. In this scenario, the system consists
of a managed network element and OMS, which is logically seen as part of the network
element itself. In this case, the system identifier and network element identifier are the
same.
g The systemId value must be chosen between 1 - 4095.
Make sure that the systemId is configured correctly, otherwise there can be
problems in sending notifications to the NetAct. Note also that the systemId must
be unique in the whole network.
To configure OMS system identifier
1. Start the zchangecluster-id script.
Enter the following command:
zchangecluster-id
2. See further instructions in zchangecluster-id below:
OMS ID
The value could be for example NE-OMS-<oms_id> or MD-SITE<number>.
The value must be chosen between 1 - 4095, for example NE-OMS1.
NWI3Adapter restart
The new clusterid will be valid after the NWI3Adapter restart.
Do you want restart NWI3Adapter and OMS SW's?
(yes/no)
To restart NWI3Adapter, answer Yes.
g The cluster id will not change during default/current session. It
is valid from new sessions onward.
4.1.2
Configuring NetAct interface with OMS
g This procedure must be executed before Centralised User Authentication and
Authorisation configuration.
This procedure instructs how to configure the connection from OMS to NetAct.
To configure NetAct interface with OMS
1. Open the Parameter tool via the Application Launcher.
2. Select entry to default instances of:
•
14
fsClusterId=ClusterRoot
Id:0900d8058079014d
DN0968394
Issue 01A
Integrating Flexi Multiradio BTS LTE to NetAct
•
•
•
Configuring the OMS for O&M connection
fsFragmentId=NWI3
fsFragmentId=mediator
fsnwi3N3CFId=1
Then initialize the attributes below by editing the required attributes and their values:
•
•
•
•
•
NetAct’s Registration Service IOR (RSIOR) fsnwi3registrationServiceIOR
field
NetAct’s Registration Service username fsnwi3initialRegistrationUsername
field (The default username is neregn, but it should be changed for security
reasons. For more information on default user accounts, see Section Default
NetAct user accounts in System Administration Principles.)
NetAct’s Registration Service password fsnwi3initialRegistrationPassword
field (The default password is neregn, but it should be changed for security
reasons. For more information on default user accounts, see Section Default
NetAct user accounts in System Administration Principles.)
Change the value of the boolean parameter
fsnwi3takeIntoUseNext=true, which means that this configuration parameter set will be taken into use during the next (re)start or re-registration.
Change the value of the boolean parameter
fsnwi3ConfigurationActive=true.
3. Select entry to default instances of:
•
•
•
•
•
fsClusterId=ClusterRoot
fsFragmentId=AlarmMgmt
fsFragmentId=AlarmProcessors
fsAlarmProcessorId=AlarmProcessor1
fsAlarmProcessorConfigurationId=Default
4. Edit the value of fsHeartbeatInterval and set it to '0'.
Double-click the current value and enter '0'.
DN0968394
Issue 01A
Id:0900d8058079014d
15
Configuring the OMS for O&M connection
Figure 3
Integrating Flexi Multiradio BTS LTE to NetAct
Heartbeat Parameter
5. Take the new parameter values into use.
NWI3Adapter takes the new parameter values into use within a re-registration
period and registers itself to NetAct (the default re-registration is 60 minutes). The
re-registration depends on the situation and the parameters in the LDAP server. The
new parameters can be taken into use immediately by restarting the NWI3Adapter
recovery group.
•
•
•
4.2
Log in CLI as Nemuadmin user and then change to root.
Restart the recovery group by entering the following command:
[root]# fshascli –r /NWI3Adapter
The request terminates all the processes running in NWI3Adapter.
The command prompts the question:
Are you sure you want to proceed? [y/n]
Answer y.
NWI3Adapter is restarted.
Checking the IP configuration
When checking the IP configuration, two IP addresses must be reserved for OMS, one
for Northbound and the other for Southbound interface. Besides the IP addresses must
be in the same subnet.
16
Id:0900d8058079014d
DN0968394
Issue 01A
Integrating Flexi Multiradio BTS LTE to NetAct
4.3
Configuring the OMS for O&M connection
Configuring NTP services
The Connectivity Server IP must be configured as the NTP source. After this, the
elements it is mediating will be able to use it as time reference source.
DN0968394
Issue 01A
Id:0900d8058079014d
17
Configuring NetAct for OMS
Integrating Flexi Multiradio BTS LTE to NetAct
5 Configuring NetAct for OMS
This chapter provides information on how to configure NetAct for OMS. The following
topics are covered in this chapter:
•
•
•
5.1
Checking Maintenance Region Service Users in NetAct
Creating managed objects for the OMS
Providing users with access to NetAct applications and network elements
Checking Maintenance Region Service Users in NetAct
To ensure that the required Maintenance Region (MR) Service Users with correct properties have been created in NetAct, you need to use the Service User Management
application to check and/or create the users listed in the Maintenance Region Service
users needed during OMS integration table:
The default maintenance region is MR-NWI3.
g All the elements OMS is mediating must belong to the same maintenance region
OMS belongs to.
g All usernames and passwords below are examples only and are not to be copied to
your environment.
“Freely selectable” in the table below means that password or username can be set
freely but there can be some system limitations to the length and use of special characters in the passwords.
The following table depicts the MR service users needed during the OMS integration to
NetAct.
18
Id:0900d8058079014d
DN0968394
Issue 01A
DN0968394 Issue 01A
Connected to
NetAct user
group
sysop
sysop
Service Type
and profile
NWI3 Access
Programmatic
PC Access
Password
dependencies
The password
can be freely
selected but it
must match the
password given to
this user in OMS.
An identical user
account must
exist in all OMS in
the same MR.
The password
can be freely
selected but it
must match the
applau user`s
password in
GUIS.
Maintenance Region Service users needed during OMS integration
Applau
The username can
be freely selected
but a matching
user must exist in
GUIS and the user
in GUIS must
belong to the
domain Adminstrator`s group.
Table 4
Nw3user
Examples of a
MR service
user’s
username
The username can
be freely selected,
but an identical
user must exist in
every OMS in the
same MR.
MR Service users
and username
dependencies
final OMS MR
or
MR-NWI3
final OMS MR
or
MR-NWI3
MR
GOMS
GOMS
MO
OMS element
manager launch
from NetAct
NWI3 interface
usage
For example,
needed for
Integrating Flexi Multiradio BTS LTE to NetAct
Configuring NetAct for OMS
Id:0900d8058079014d
19
Configuring NetAct for OMS
Integrating Flexi Multiradio BTS LTE to NetAct
For a full list of service types and their purposes, see Chapter Service types in System
Administration Principles. For information on principles of user management related
tasks during network expansions, see User management procedure in network expansion and network element integration in System Administration Principles.
5.2
Creating managed objects for the OMS
LTO1.0 OMS supports topology upload. Follow the steps below to perform it.
To perform NWI3 topology upload
1. Log into NetAct Start application as omc user.
2. Select Desktop under Categories.
3. From the Desktop window, click Top Level User Interface.
The Opening a View dialog appears.
4. Select the view which contains the PLMN object, and then click OK.
The view window which contains the PLMN object appears.
5. Click Utils, and from the drop-down list, click Topology Upload (NWI3).
The Topology upload from the NWI3 mediator window appears.
6. In the pop-up window, enter the NWI3 system ID. For example, NE-GOMS-2.
7. Then enter y and press ENTER.
8. If the result shows:
NE-GOMS-2 uploaded successfully.
Then the topology upload has been successful.
To add the GOMS object to the network view
g Make sure the GOMS object is present in the NetAct topology database. Then
modify and add GOMS to the network views with Network Editor as instructed
below. For more information on Network Editor, see Network Editor Help and for
more information on building network views, refer to document Building and Maintaining Views.
Ensure that NWI3 MR is created and available. All service users must be configured
in the MR as mentioned before.
1. Log into NetAct Start application as omc user.
2. Select Desktop under Categories.
3. From the Desktop window, click Network Editor.
The Opening a View dialog appears.
4. Open the view to which the managed object will be added.
5. Right-click the PLMN object and select Add Existing Child....
6. Select the GOMS from the list of objects, click Add and place the object in the view.
7. Right-click GOMS object and select Modify Information....
8. Fill in the name of the object in Object Details dialog.
9. Click Apply and Close the dialog.
20
Id:0900d8058079014d
DN0968394
Issue 01A
Integrating Flexi Multiradio BTS LTE to NetAct
Configuring NetAct for OMS
10. All NWI3 attributes of the added object are automatically uploaded from GOMS. You
can modify the information by right-clicking the GOMS object and select Modify
Information....
g Repeat the steps above to add objects of MRBTS, LNBTS, LNCEL and FTM.
For LNCEL, you need to select version LN1.0 manually in object details dailog.
Refer to hierachy below when you add those objects.
Figure 4
5.3
5.3.1
Object Model
Providing users with access to NetAct applications and
network elements
Providing users access via service user management
To provide users of a group access to the network via the applications in NetAct, you
need to check/create Maintenance Region service users and associate them with the
service types the users in the group will need. For the NetAct applications to be able to
use this MR service user, it must be connected with the user group. This connection
allows the users in the group to access a network element according to the service type
of the MR service user (for example NWI3 access). For the members of the group, the
access to managed objects (NEs) will be transparent.
In order to ensure that the users have access to OMS, you need to check if the Maintenance Region where this new network element was added contains the MR service
users needed. To find out the kind of service types that are needed with a particular
network element, see Service types in System Administration Principles. For instruc-
DN0968394
Issue 01A
Id:0900d8058079014d
21
Configuring NetAct for OMS
Integrating Flexi Multiradio BTS LTE to NetAct
tions on how to create user groups and set service accesses, see NetAct Permission
Manager Help and Managing Users.
22
Id:0900d8058079014d
DN0968394
Issue 01A
Integrating Flexi Multiradio BTS LTE to NetAct
Verifying the integration
6 Verifying the integration
This chapter describes the tests that must be performed to verify that OMS has been
integrated successfully to NetAct.
6.1
Verifying IP connectivity
After the LTE BTS has been installed and configured, check that the connection from
NetAct is working properly.
To test the LTE BTS integration
1. Ping the IP addresses of the GOMS by entering:
# ping <IP_address>
Variable
Description
<IP_address>
Test the following address:
OMS
Table 5
Variable list
2. Launch the Element Manager of the GOMS from the Top-level User Interface by
right-clicking the GOMS icon and selecting Element Managers... → OMS EM... and
OMS GUI EM...from the pop-up menu.
3. Verify that alarms sent by the GOMS can be seen in Alarm Monitor in NetAct.
For troubleshooting instructions, see Troubleshooting System Management Problems.
6.2
Verifying the EM launch
To check the EM launch
1. Log into NetAct Start application as omc user.
2. In the Top-level User Interface, right-click on the GOMS object and select Element
Managers... → OMS EM....
If there is no problem, the JAVASE-based Element Manager is launched successfully.
6.3
Verifying Fault Management data flow
To check whether the Fault Management (FM) data is arriving from the network element
to NetAct, complete the following tasks:
To verify FM data flow
1. Open the Alarm Monitor application in NetAct.
2. Generate test alarm:
a. Start the OMS element manager and choose Parameter Tool to enable OMS
FlexiPlatform test alarm (Heartbeat warning).
DN0968394
Issue 01A
Id:0900d8058079014d
23
Verifying the integration
Integrating Flexi Multiradio BTS LTE to NetAct
b. Edit the value of fsHeartbeatInterval and set it to 1 by double-clicking the
current value and entering 1.
NWI3Adapter takes the new parameter values into use within a re-registration
period and registers itself to NetAct (the default re-registration is 60 minutes). The
re-registration depends on the situation and the parameters in the LDAP server. The
new parameters can be taken into use immediately by restarting the NWI3Adapter
recovery group. Restart the recovery group by entering the following command:
fshascli –r /NWI3Adapter
3. Check that the alarm is visible in Alarm History. Using the NetAct Alarm History,
verify that warning 70246 is arriving in 10 minutes from OMS.
Cancel the test alarm by setting the fsHeartbeatInterval to 0.
6.4
Verifying the Performance Management data flow
To verify the PM data flow
1. Make sure GOMS has been configured to be able to send measurements data to
NetAct.
2. Generate some performance data from eNB.
3. After configuring interval time, log in CS server of NetAct via SSH using omc
account.
Use the following command to see if any LTE BTS PM data has been inserted into
DB successful:
etlcolDBInfo.pl -t NOKLTE%02
If the value of corresponding Last Entry varies from before, the PM function works
successfully.
24
Id:0900d8058079014d
DN0968394
Issue 01A
Integrating Flexi Multiradio BTS LTE to NetAct
Where to find more information
7 Where to find more information
During the integration procedure, you should refer to other documentation. Ensure the
following documents are available.
NetAct documentation
For more information on NetAct user management, see Managing Users.
For information on permission management, see NetAct Permission Manager Help.
For instructions on testing the NetAct system platform and network element connections, see Testing the System Platform.
For information on creating managed objects and viewing management tasks, see
Network Editor Help and Managed Object Reference.
For information on the DNS management concepts and a list of the required zones, see
DNS Management Principles.
For more information on managing DNS in NetAct, see Managing the DNS in NetAct.
For a full list of service types and their purposes, see System Administration Principles.
DN0968394
Issue 01A
Id:0900d8058079014d
25
Integrating Flexi Multiradio BTS LTE to NetAct
Index
A
NWI3Adapter 16
abbreviations 6
Alarm History 24
Alarm Monitor 23
O
Operations and Management Server (OMS) 6
osscore2 package 11
B
P
BIND 13
Parameter Tool 14
C
configuration of the OMS 14
configuring NetAct interface with OMS 14
configuring OMS system identifier 14
IP configuration 16
NTP services 17
Connectivity Server 11
CORBA 9
Corba Naming Service 12
D
Data Server 11
Diagnostic Tool 10
DNS Client 12
Domain Name Service (DNS) 12
adding managed objects to the DNS 12
E
S
Service Type and Profile
NWI3 Access 19
Programmatic PC Access 19
Service Type and profile 19
Service User Management 18
system identifier of OMS 14
system requirements 10
FQDN addresses 10
NetAct cluster IP addresses 10
NetAct users and passwords 10
network element iP addresses 10
network element local IDs and passwords 10
service user accounts 10
T
terms 6
Element Manager 12, 23
U
I
I-HSPA OMS 6
integration procedure 9
completing the preliminary tasks 9
configuring the OMS 9
verifying the integration 9
integration verification 23
verifying Fault Management data flow 23
IOR string 11
IP connectivity 23
users' access to NetAct applications and network
elements 22
via service user management 22
W
where to find more information 25
NetAct documentation 25
M
Maintenance Region Service Users 18
managed objects 12
GOMS 12
mediation devices 9
N
NameSurfer 13
network management system (NMS) 9
26
Id:0900d8058078e3d9
DN0968394
Issue 01A