Integrating SMSC to NetAct

Integrating SMSC to NetAct

DN05223827 Issue 2-1 en

© Nokia Corporation Nokia Proprietary and Confidential

1 (30)


The information in this documentation 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's customers only for the purposes of the agreement under which the documentation is submitted, and no part of it may be reproduced or transmitted in any form or means without the prior written permission of Nokia. The documentation has been prepared to be used by professional and properly trained personnel, and the customer assumes full responsibility when using it. Nokia 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 cannot be considered binding but shall be defined in the agreement made between Nokia and the customer. However, Nokia has made all reasonable efforts to ensure that the instructions contained in the documentation are adequate and free of material errors and omissions. Nokia will, if necessary, explain issues which may not be covered by the documentation. Nokia's liability for any errors in the documentation is limited to the documentary correction of errors. NOKIA WILL NOT BE RESPONSIBLE IN ANY EVENT FOR ERRORS IN THIS DOCUMENTATION OR FOR ANY DAMAGES, INCIDENTAL OR CONSEQUENTIAL (INCLUDING MONETARY LOSSES), that might arise from the use of this documentation or the information in it. This documentation and the product it describes are considered protected by copyright according to the applicable laws. NOKIA logo is a registered trademark of Nokia Corporation. Other product names mentioned in this documentation may be trademarks of their respective companies, and they are mentioned for identification purposes only. Copyright © Nokia Corporation 2006. All rights reserved.

2 (30)


DN05223827 Issue 2-1 en

Contents Contents 3 List of figures 4 1 1.1 1.2

About this document 5 NetAct compatibility and capacity information 5 Terms 5

2 2.1 2.2 2.3

Introduction to SMSC integration 7 Connection principles 7 Centralised SMSC management 7 Integration procedure 8

3 3.1 3.1.1 3.1.2 3.2 3.2.1 3.2.2 3.3 3.3.1 3.4

Preliminary tasks 11 Reviewing the system requirements 11 Nokia NetAct 12 SMSC 14 Adding managed objects to the DNS 14 Adding SMSC to DNS with BIND 15 Adding SMSC to DNS with NameSurfer 15 Creating managed objects 16 Adding the SMSC object to the network view 16 Opening the Firewall Connection 18

4 4.1 4.2

Configuring SMSC for NetAct connection 19 Configuring FM dataflow to NetAct 19 Configuring PM dataflow to NetAct 20

5

Verifying the integration 25

6

Where to find more information 27 Index 29

DN05223827 Issue 2-1 en


3 (30)


List of figures

4 (30)

Figure 1.

Integration procedure 9

Figure 2.

Preliminary tasks 11

Figure 3.

Creating an SMSC object 17

Figure 4.

Configuration tasks 19

Figure 5.

Example of the configuration file 23


DN05223827 Issue 2-1 en

About this document

1

About this document This document describes how to integrate a Nokia Short Message Service Centre (SMSC) to Nokia NetAct. This customer document was written for the management and the integration personnel of an operator. The information in this document is valid for Nokia NetAct release OSS4 and SMSC versions 8.0. Do not use this document with other NetAct releases or SMSC versions. For information on other related Nokia documentation, see Chapter 6 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.

DN05223827 Issue 2-1 en


5 (30)


Table 1.

Terms

Term

Explanation

DCN

Data Communications Network

DNS

Domain Name System

FQDN

Full Qualified Domain Name Full logical name of a computer system, rather than only its host name

NDW

Network Data Warehouse Data warehouse which collects measurement data from the network and provides reporting tools

NE3S

Nokia-specified open O&M interface for fault, configuration, performance, and security management that supports the SNMPSNMP, SOAP/HTTP, and FTP/XML protocols.

O&M

Operation and Maintenance

OMeS

Open Measurement Standard Nokia-specified standard defining the file format for measurement data transfer based on XML.

SNMP

Simple Network Management Protocol An application layer protocol used by Nokia NetAct to collect alarms from network elements

6 (30)


DN05223827 Issue 2-1 en

Introduction to SMSC integration

2

Introduction to SMSC integration This chapter provides a general description of the principles of connecting a newly commissioned SMSC to NetAct. The integration procedure consists of a series of ordered tasks that allow to connect an SMSC to NetAct. Once the integration is completed, NetAct can perform configuration, fault, and performance management functions from a centralised location. Do not deviate from the order of the tasks that is presented in this guide because that can lead to unwanted delays.

2.1

Connection principles The SMSC transmits short messages on a network and stores them for later transmission if the recipient cannot be reached. It provides interfaces towards NetAct for both fault management data (alarms) and performance management data containing system performance and traffic data. For more information on the SMSC, see SMS Centre Product Description. Network topologies

In OSS4, it is recommended that the local network elements are connected to NetAct with LAN. For establishing WAN connections between NetAct and the remote NE there are several different possibilities. For a full list of interfaces provided by the NetAct DCN backbone, see Network topologies in DCN Management for 3G. All SMSC interfaces and connections are IP-based. One TCP/IP address per server is allocated to the SMSC in all normal installations. When an SMSC is connected to the Internet, a firewall should be used to enhance security.

2.2

Centralised SMSC management Once the integration is completed, NetAct can perform the following functions from a centralised location:

DN05223827 Issue 2-1 en


7 (30)


Performance Management

The collected indicators are stored in ASCII-format files. The performance management interface takes care of transferring the collected performance management data to Nokia NetAct Regional Cluster. The data is transferred by using FTP. NetAct Regional Cluster forwards the performance management data via a common mechanism to the NetAct Regional cluster which processes the result data further. Fault Management

The SMSC sends alarm related notifications to NetAct as SNMP traps. They are converted to the Nokia Alarm format and forwarded to NetAct, where they can be processed and viewed with NetAct alarm handling applications. The SMSC supports the mandatory features of Nokia Enhanced SNMP Solution Suit (NE3S) and also GET requests.

2.3

Integration procedure To successfully integrate an SMSC, first you need to complete the preliminary tasks, then configure the SMSC, and finally verify the integration. The following flowchart covers the tasks that need to be carried out when integrating a new SMSC network element:

8 (30)


DN05223827 Issue 2-1 en

Introduction to SMSC integration

Start preliminary tasks

Review the system requirements

Configure the SMSC

Add managed objects to the DNS

Configure FM dataflow to NetAct

Create managed objects

Configure PM dataflow to NetAct

End

Task is done in: SMSC NetAct

Figure 1.

DN05223827 Issue 2-1 en

Integration procedure


9 (30)


10 (30)


DN05223827 Issue 2-1 en

Preliminary tasks

3

Preliminary tasks This chapter lists the tasks you must complete before beginning the integration. The preliminary tasks are shown in the following flowchart:

Start

Review the system requirements

Add managed objects to the DNS

Create managed objects

Go to Configuring SMSC for NetAct connection

Figure 2.

3.1

Preliminary tasks

Reviewing the system requirements This section covers the system requirements.

DN05223827 Issue 2-1 en


11 (30)


3.1.1

Nokia NetAct

Note In several procedures you are required to log into the System Server. It is possible to find out which node is the System Server by entering the following command: root>% cmviewcl

Before beginning integration, ensure that Nokia NetAct meets the following requirements and the information required during the integration procedure is available: •

Ensure the NetAct environment is configured and functioning properly: -

Check that all ServiceGuard packages are up and running by entering the following command:

root% cmviewcl

-

Check that all the relevant processes are running by entering the following command:

root% /opt/nokiaoss/diagtools/ssdiagno/bin/qapprocstatmx.perl

-

Select Test all hosts. If some process is not running, it is listed in the output.

For instructions, see Testing the System Platform. •

IP address of the osscore2 package must be available.

To find out the IP address of the osscore2 ServiceGuard package and the primary nodes for db and system packages (SS & DS) 1.

For a full list of options available with the ldapacmx.pl script, enter:

ldapacmx.pl -help

2.

Find out the active ServiceGuard package names by typing:

omc% ldapacmx.pl -sgPkgList

Example output: nfsserver system db

12 (30)


DN05223827 Issue 2-1 en

Preliminary tasks

osscore message osscore2 nww rac slt rep mvi base-nikolai base-birch base-frisbee base-hurveli

3.

Interrogate the FQDN of the osscore or osscore2 pkg by entering:

omc% ldapacmx.pl -sgPkgHost osscore

or: omc% ldapacmx.pl -sgPkgHost osscore2

Example output: rc80cor2.netact.noklab.net

4.

Interrogate the FQDNs of primary nodes (Database Server) for db and system packages by entering:

omc% ldapacmx.pl -pkgPrimaryNode db

Example output: hurveli.netact.noklab.net

5.

Interrogate the FQDNs of primary nodes (System Server) for db and system packages by entering:

omc% ldapacmx.pl -pkgPrimaryNode system

Example output: nikolai.netact.noklab.net

6.

Interrogate the IP addresses for the FQDNs by entering:

omc% nslookup

where the FQDN is, as given in the outputs above:

DN05223827 Issue 2-1 en


13 (30)


7.

3.1.2

•

FQDN of the osscore or osscore2 pkg

•

FQDN of the System Server

•

FQDN of the Database Server

Note down these IP addresses, because you need them during the NE integration.

SMSC Before you begin the integration, ensure that the SMSC meets the following requirements and the information required during the integration procedure is available: •

The IP address of the SMSC management interface is known.

•

The IP address sending traps to NetAct (if separate) is known.

•

The value of the get community string is known. NetAct performs the ‘get’ SNMP operation to supervise the IP connection to the network element. To check the correct value, follow the instructions below: 1. 2. 3.

•

Log into the SMSC server. Open the $SC_CONFPATH/xamsnmpmx.cf file. Note down the value of the Community parameter.

The password for the sc user is known.

Other prerequisites to be taken care of in the network element before starting:

3.2

•

The SMSC has been integrated to the IP network.

•

The number of the Get/Set UDP Port is known.

•

The correct version of the NE is installed.

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 SMSC to the DNS, familiarise yourself with the DNS management concepts and the list of required zones. For more information, see DNS Management Principles. When integrating a new SMSC to NetAct, you need to add the IP address and host name of the element to the NSS zone. The IP address added to the DNS must be the SMSC‘s O&M interface.

14 (30)


DN05223827 Issue 2-1 en

Preliminary tasks

The basic procedure of adding SMSC to the DNS zone includes the following tasks: 1.

Check whether the needed zone already exists. For more information, see Managing the DNS with NetAct.

2.

Add the SMSC to the zone using Name Surfer or BIND. For more information, see Managing the DNS with NetAct.

Note If you are unsure whether the primary Name Servers are implemented with BIND or NameSurfer in your system, log into the System Server and enter the following command: # ls /opt/namesurfer

If the directory is found, the software is installed on your System Server. To start the application, click Utils → System Mgmt → DNS Manager... in Top-level User Interface.

3.2.1

Adding SMSC 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: SMSC IP address: IP address of the OMU. DNS zone: paco.netact... Naming of the object: smsc To add an SMSC NE to the DNS with BIND, see Host (A) (in Section Using BIND to edit data in DNS) in Managing the DNS with NetAct.

3.2.2

Adding SMSC to DNS with NameSurfer If you have NameSurfer, you can configure the data on the DNS server from a GUI. To add an SMSC NE to DNS with NameSurfer, see Host (A) (in Section Using NameSurfer to edit data in DNS) in Managing the DNS with NetAct.

DN05223827 Issue 2-1 en


15 (30)


3.3

Creating managed objects Before NetAct can receive and store data from a network element data, you have to create a managed object for the network element with Network Editor. For more information on creating managed objects, see Network Editor Help. For information on the SMSC managed object location in the NetAct managed object hierarchy, see Managed Object Reference.

3.3.1

Adding the SMSC object to the network view The integration root object (IRO) is the main object of the integration. One such object must be created for each integrated Nokia SMSC.

To add the SMSC object to the network view 1.

Log into the System Server as the omc user.

2.

From the Top-level User Interface, start Network Editor by selecting Utils → System Mgmt → Network Editor...

3.

In the Opening a View dialogue, select any view containing the PLMNPLMN managed object.

4.

From the PLMN-PLMN pop-up menu, select Add New Child→SMSC.

5.

In the Object Creation dialogue, fill in the necessary information to create the managed object: Maintenance Region: Choose a maintenance region. SMSC ID:

Choose any free value between 0-9999 (the ID must be unique in the whole network).

Latitude/Longitude: If geographical co-ordinates are used in the network, insert the correct values in these fields (otherwise you may leave the fields empty).

16 (30)

Vendor:

Select ‘Nokia’.

Version:

The version information is interrogated from the SMSC 8.0.

Main hostname:

The hostname and IP address of the SMSC management interface (the IP address from which the SMSC sends SNMP traps). This field is optional.


DN05223827 Issue 2-1 en

Preliminary tasks

Get/Set UDP Port: 18051 Get Community: This value must be the same as the value for the Community parameter defined in the xamsnmpmx.cf file. For instructions on how to check the correct value, see Section 3.1 Reviewing the system requirements. Set Community:

This value must be the same as the value for the Community parameter defined in the xamsnmpmx.cf

file. For instructions on how to check the correct value, see Section 3.1 Reviewing the system requirements.

Figure 3.

DN05223827 Issue 2-1 en

Creating an SMSC object

6.

Place the created object into the view.

7.

Save the view by selecting File → Save.


17 (30)


3.4

Opening the Firewall Connection Before connection between Nokia NetAct and SMSC can be established, firewall needs to be opened in the operator’s network. For more information on other NEs and firewall, see the Security Policy in NetAct Firewalls document (dn03409741) in NOLS. The firewall should allow two-way SNMP connection between NetAct and the network element. •

NE to NetAct: port 162 from the IP address of the SMSC.

•

NetAct to NE: port 18051 from the NetAct server IP addresses/subnetworks to the IP address of the SMSC.

Ping is allowed from the NetAct server IP addresses/subnetworks to the IP address of the SMSC. In addition, FTP from SMSC to NetAct should be allowed in port 21.

18 (30)


DN05223827 Issue 2-1 en

Configuring SMSC for NetAct connection

4

Configuring SMSC for NetAct connection This chapter describes the tasks that you have to complete in the SMSC to enable dataflow between NetAct and the SMSC. The configuration tasks are shown in the following flowchart:

Start

Configure FM dataflow to NetAct

Configure PM dataflow to NetAct

Go to Verifying the integration

Figure 4.

4.1

Configuration tasks

Configuring FM dataflow to NetAct The SMSC sends alarm-related notifications to NetAct as SNMP traps. For information on how to configure the SMSC fault management interface to NetAct, see Integrating NMS with SMS Centre in Fault Management Interface Specification (dn0430689) included in the SMSC documentation.

DN05223827 Issue 2-1 en

•

Login to the SMSC via Telnet as the sc user.

•

When editing the $SC_CONFPATH/xamsnmpmx.cf file, use the following attributes:


19 (30)


[SNMPIF] NE3S:1 DestinationIP: TrapPort: 162 RequestPort: 18051 SNMPVersion: 2 Community: SMSCTRAP SystemDNType: SMSC IrpVersion: 1.2.7 EnterpriseOid: 1.3.6.1.4.1.94.1.41

For instructions on how to check the IP address of the osscore2 package that receives SNMP traps from the SMSC, see Section 3.1 Reviewing the system requirements. Afterwards a restarting process is needed. Proceed as follows: sc% sc% sc% sc%

4.2

cd/etc/opt/nokia/smsc/script xom_killer_mx.sh ps -ef | grep mx xom_starttimx.sh

Configuring PM dataflow to NetAct The SMSC sends PM data files to NetAct through FTP. For instructions on how to configure the SMSC performance management interface to NetAct, see Configuring the file transfer scripts in Performance Management Interface Guide (dn03305334) included in the SMSC documentation.

Caution The steps below serve only as reminders and examples, not as exact instructions.

Note The steps one and two are required only when the first SMSC is being integrated to NetAct.

20 (30)


DN05223827 Issue 2-1 en


1.

Create the ADAP_NOKSMSC topology object if it does not already exist:

cp /opt/nokiaoss/uma/umamms/madnsh/conf/template/bcmn.327.007.xml/var/opt /nokiaoss/uma/umatkt/tktcif/work/import/

Ensure that the file disappears and the object appears in topology. 2.

Configure the pmisys process: •

Generate the Import and Convert configuration files. netact_start.pl uma/umatkt/tktpmi pg pg_tktpmi_osscore2 -- pmisetConfig.pl -a madnsh

Ensure that the files $ETCROOT/uma/irp/conf/nshcapImport.cf and nshcapCustomerConvert.cf appear.

•

Add the adaptation configuration file:

cp $PRODUCTROOT/uma/umamms/madnsh/conf/default/nshcapAdaptation.cfg $ETCROOT/uma/irp/conf/nshcapAdaptation_osscore2.cfg

•

Edit the file so that the Import is active and ImportSchedule does not start the import of the files together with the other adaptations: (ImportActive “yes”) (ImportSchedule “17 *”) for example, meaning each hour at 17th minute (crontab syntax, see “man crontab”). Notify the pmisys process that the configuration is ready. Find out in which machine the pmisysmx_osscore2 is running. Login to that machine and find the PID of the process ps -ef | grep pmisysmx_osscore2

Send the HUP signal to the process kill -HUP

3.

Configure SMSC to collect the PM data. Collecting data in one file is recommended, these files will be fetched in certain intervals. • •

Login to the SMSC via Telnet as the sc user. When editing the $SC_CONFPATH/xnnmonconf_mx.cf file, use the following attributes:

IND_TO_FILE: YES:xnnmonind.dat INDICATOR_FILE_NAMING: NO LEGEND_TO_FILE: YES

Using this configuration the PM data will be collected in a single file: $SC_TMPPATH/xnnmonind.dat.

DN05223827 Issue 2-1 en


21 (30)


4.

Configure the SMSC to send the data to NetAct. • •

Login to the SMSC server as the sc user. When editing the $SC_CONFPATH/xnnmon_ndw_mx.sh file, use the following attributes:

SMSC_ID= TARGET_HOST=”IP address of osscore2 SG packet” TARGET_DIR=”/d/osscore2/uma/umatkt/pg_tktpmi_osscore2/work/import/madnsh XNNMON_IND_FILE=“xnnmonind.dat” FTPTYPE={TRANSFER_ACTIVE} LOGIN= PASSWORD=

where the is the ID number of the respective SMSC object in NetAct

Note The has to be unique for each SMSC. where the corresponds to the user name used to FTP PM files to the NetAct server running PMI processes username=nx2suser

where the is the above username’s password password=Get the password of nx2suser from NetAct Administrator

For an example configuration see, Figure Example of the configuration file. The actual configuration file of your SMSC may differ from the example presented below, as it is a function of the SMSC version you are integrating.

22 (30)


DN05223827 Issue 2-1 en


Figure 5.

5.

Example of the configuration file

It is possible to produce yesterdayDate file by using the following command:

date “+%Y%m%d“>$SC_TMPPATH/yesterdayDate

6.

Ensure that the PM deamon xnnmonmx is started

7.

Add xnnmon_ndw_mx.sh to cron Following two entries should be in the crontab of SMSC.

crontab -e

14****/etc/opt/nokia/smsc/script/xnnmon_ndw_mx.sh./dev/null. *****/bin/sh /etc/opt/nokia/smsc/script/xnnmonmx.sh keepAlive > /dev/null

DN05223827 Issue 2-1 en


23 (30)


For instructions on how to check the IP address of the osscore2 package that receives SNMP traps from the SMSC, see Section 3.1 Reviewing the system requirements.

24 (30)


DN05223827 Issue 2-1 en

Verifying the integration

5

Verifying the integration To verify that the SMSC integration has been completed successfully, perform the test described below.

To check the NetAct connections 1.

Ping the IP address(es) of the SMSC by entering the following command:

# ping

2.

Open the Telnet connection from Nokia NetAct to the SMSC.

3.

Check that the DNS entries for the SMSC are properly configured by entering the following command:

# nslookup

To check the PM data flow 1.

Start a measurement: For instructions on how to start a measurement, see Section 4.2 Configuring PM dataflow to NetAct.

2.

Verify that measurements have arrived to the NetAct database by using the following command.

omc% netact_start.pl reporter/etload -- etlcolDBInfo.pl -t MADNSH%

A listing of measurement tables is displayed indicating when the latest measurements have been inserted. SQL>select count (*) from

where is a measurement table as defined in the database description, and into which you are receiving PM data.

DN05223827 Issue 2-1 en


25 (30)


3.

Wait for the measurement time, and give the same command again.

4.

Stop the test measurements you have started.

To check the FM dataflow Note The database can be empty after the integration. Therefore, wait at least an hour after the integration before you perform this test. 1.

Open the Alarm Monitor application in Nokia NetAct.

2.

Generate the test alarm Login to the SMSC via Telnet and shut down the TCP/IP link by giving the command:

$SC_BINPATH/xsccmdmx -k xdxmanmx1

This causes the link process to go down and generate an alarm. To start the link process up again, give the command: $SC_BINPATH/xsccmdmx -r xdxmanmx1

26 (30)

3.

Check that the alarm is visible in Alarm Monitor.

4.

Cancel the test alarm.


DN05223827 Issue 2-1 en

Where to find more information

6

Where to find more information During the integration procedure, you should refer to other documentation. Ensure the following documents are available. NetAct documentation

For information on the typographical conventions used in this document, see Description of Documentation. For more information on integrating DCN backbone to NetAct, see Integrating DCN Backbone to NetAct. For information on the interfaces provided by the NetAct DCN backbone, see DCN Management Principles for 3G. For more information on NetAct user management, see Managing Users. For more information on how to create users with Service User Management, see Service User Management Help. 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 NetAct configuration files, applications and processes, see System Platform Technical Reference Guide and Monitor Technical Reference Guide For information on creating managed objects and viewing management tasks, see Network Editor Help. For information on the managed object hierarchy and the SMSC managed object location, see Managed Object Reference. For information on the DNS management concepts and a list of the required zones, see Managing the DNS with NetAct and DNS Management Principles. For information on configuring the time services, see Configuring System Level Services.

DN05223827 Issue 2-1 en


27 (30)


For information on NetAct alarm monitoring tools, see Monitoring Principles. For information on how to repair the most common operational problems in Nokia NetAct, see Troubleshooting Fault Management Problems and Troubleshooting Performance Management Problems. Nokia SMSC documentation

For information on Nokia SMS Centre, see SMS Centre Product Description, DN03305404. For instructions on how to configure the SMSC fault management interface to NetAct, see Fault Management Interface Specification, DN0430689. For instructions on how to configure the SMSC performance management interface to NetAct, see Performance Management Interface Guide, DN03305334. The documents listed in this chapter are available from http://www.online.nokia.com (authentication is required).

28 (30)


DN05223827 Issue 2-1 en

Index D DCN DNS

6 6,

14,

25,

27

7,

19,

14, 5

16

F fault management firewall 7

25

L LAN

7

M managed objects MMSC versions

N NDW NE3S

6 6,

19

O OMeS

6

P 7,

20

19,

20,

performance management

S SNMP 6, 14, 16, system requirements NetAct 12

24

T TCP IP

7

W WAN

7

X xamsnmpmx.cf

DN05223827 Issue 2-1 en

14,

17,

19

©Nokia Corporation Nokia Proprietary and Confidential

29 (30)


30 (30)


DN05223827 Issue 2-1 en

Integrating SMSC to NetAct

Recommend Documents