DCN Integration

Document number/Issue Copyright © Nokia Telecommunications Oy

NTC TAN 0839/2.2 en

1

NOKIA NMS/2000FOR MANAGING CELLULAR NETWORKS

DCN INTEGRATION

Installation Guide


NTC TAN 0839/2.2 en2

The information in this document is subject to change without notice and describes only the product definedin the introduction of this documentation. This document is intended for the use of NokiaTelecommunications' customers only for the purposes of the agreement under which the document issubmitted, and no part of it may be reproduced or transmitted in any form or means without the prior writtenpermission of Nokia Telecommunications. The document has been prepared to be used by professional andproperly trained personnel, and the customer assumes full responsibility when using it. NokiaTelecommunications welcomes customer comments as part of the process of continuous development andimprovement of the documentation.

The information or statements given in this document concerning the suitability, capacity, or performance ofthe mentioned hardware or software products cannot be considered binding but shall be defined in theagreement made between Nokia Telecommunicat ions and the customer. However, NokiaTelecommunications has made all reasonable efforts to ensure that the instructions contained in thedocument are adequate and free of material errors and omissions. Nokia Telecommunications will, ifnecessary, explain issues which may not be covered by the document.

Nokia Telecommunications' liability for any errors in the document is limited to the documentary correction oferrors. Nokia Telecommunications WILL NOT BE RESPONSIBLE IN ANY EVENT FOR ERRORS IN THISDOCUMENT OR FOR ANY DAMAGES, INCIDENTAL OR CONSEQUENTIAL (INCLUDING MONETARYLOSSES), that might arise from the use of this document or the information in it.

This document and the product it describes are considered protected by copyright according to theapplicable laws.

NOKIA logo is a registered trademark of Nokia Corporation.

Other product names mentioned in this document may be trademarks of their respective companies, andthey are mentioned for identification purposes only.

Copyright © Nokia Telecommunications Oy 1998. All rights reserved.

No. of Edited by Author Approved by Previous issuepages (2.1) approved

T Jara T Jara J Nummikoski195/TJa 5 Oct 1998 5 Oct 1998 6 Oct 1998 23 July 1998

Copyright © Nokia Telecommunications Oy 1998. All rights reserved.



TABLE OF CONTENTS

1 WHAT IS NEW. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 71.1 Changes from T9 to T10 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7

2 ABOUT THIS MANUAL . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 82.1 What you need to know first . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 82.2 How to use this manual . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 92.3 Concepts and terminology . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 92.4 Typographic conventions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12

2.4.1 Text styles . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 122.4.2 Command line conventions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13

2.5 Where to find more . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15

3 INTRODUCTION TO DCN INTEGRATION. . . . . . . . . . . . . . . . . . . 163.1 Integration principles . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 173.2 Network topologies . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 173.3 Network services . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17

3.3.1 Connectionless network service. . . . . . . . . . . . . . . . . . . . . . . . . . 183.3.2 Connection-oriented network service . . . . . . . . . . . . . . . . . . . . . 20

3.4 Integration procedures . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 223.5 Hardware . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 23

3.5.1 Network cards . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 233.5.1.1 AC25-S. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 233.5.1.2 AS7-U . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 233.5.1.3 COCEN . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 23

3.5.2 Intermediate systems . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 243.5.2.1 Nokia NMS Front End. . . . . . . . . . . . . . . . . . . . . . . . . . 243.5.2.2 Cisco routers . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 24

4 PRELIMINARY TASKS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 254.1 Filling in the configuration sheets . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 264.2 Reviewing the system requirements. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 27

4.2.1 NMS. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 274.2.2 BSC . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 284.2.3 MSC/HLR . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 29

4.3 Creating managed objects in the NMS. . . . . . . . . . . . . . . . . . . . . . . . . . . . 304.4 Creating and modifying user group profiles . . . . . . . . . . . . . . . . . . . . . . . 314.5 Creating and modifying user IDs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 32

5 CONFIGURING THE NMS COMMUNICATIONS SERVER. . . . . 345.1 Enabling X.121 subaddressing. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 355.2 Setting up the OSI subnetwork . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 37

5.2.1 Using CLNS. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 385.2.1.1 Setting up a CLNS subnetwork for X.25. . . . . . . . . . . . 395.2.1.2 Setting up a CLNS subnetwork for LAN. . . . . . . . . . . . 41



5.2.1.3 Communications Server package. . . . . . . . . . . . . . . . . . 435.2.1.4 Adding the comm package NSAP . . . . . . . . . . . . . . . . . 44

5.2.2 Using CONS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 465.2.3 Adding an ISO OSI destination . . . . . . . . . . . . . . . . . . . . . . . . . . 485.2.4 Adding an IS as an ISO OSI destination . . . . . . . . . . . . . . . . . . . 505.2.5 Adding a default route . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 51

5.3 Configuring OSI applications and addresses . . . . . . . . . . . . . . . . . . . . . . . 525.3.1 Setting up PAD services . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 53

5.3.1.1 PAD service for outgoing connections. . . . . . . . . . . . . . 535.3.1.2 PAD service for incoming connections . . . . . . . . . . . . . 54

5.3.2 Setting up DX 200 OSI applications . . . . . . . . . . . . . . . . . . . . . . 565.3.3 Configuring OSI protocol identifiers . . . . . . . . . . . . . . . . . . . . . . 58

6 CONFIGURING CONNECTION SERVER SOFTWARE . . . . . . . . 596.1 Backing up the DCN configuration file . . . . . . . . . . . . . . . . . . . . . . . . . . . 616.2 Editing the /etc/services file . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 626.3 Configuring the inetd daemon . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 636.4 Editing the Connection Server configuration file . . . . . . . . . . . . . . . . . . . 656.5 Address device information . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 666.6 Naming arcs and routes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 676.7 Adding an arc to a remote system . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 686.8 Adding a route to a remote system. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 706.9 Adding an administrative route to a remote system. . . . . . . . . . . . . . . . . . 726.10 Adding a node definition to a remote system. . . . . . . . . . . . . . . . . . . . . . . 74

6.10.1 Determining connection subtypes . . . . . . . . . . . . . . . . . . . . . . . . 766.11 Re-reading the configuration file . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 776.12 Verifying DCN integration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 78

7 CONFIGURING THE DX 200 NETWORK ELEMENT. . . . . . . . . . 797.1 Setting up the physical connection. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 80

7.1.1 Using analog X.25 (PSN). . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 817.1.1.1 Installing and configuring an AC25-S card . . . . . . . . . . 837.1.1.2 Setting the physical layer parameters . . . . . . . . . . . . . . 857.1.1.3 Creating and modifying the X.25 parameter set . . . . . . 867.1.1.4 Creating a physical channel . . . . . . . . . . . . . . . . . . . . . . 877.1.1.5 Assigning a channel group to a physical channel . . . . . 887.1.1.6 Verifying the physical connection . . . . . . . . . . . . . . . . . 88

7.1.2 Using digital X.25 (PCM) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 897.1.2.1 Installing and configuring an AS7-U card . . . . . . . . . . . 897.1.2.2 Installing and configuring an Exchange Terminal . . . . . 927.1.2.3 Setting up the semipermanent connections . . . . . . . . . . 957.1.2.4 Creating and modifying the X.25 parameter set . . . . . . 977.1.2.5 Creating a physical channel . . . . . . . . . . . . . . . . . . . . . . 987.1.2.6 Assigning a channel group to a physical channel . . . . . 997.1.2.7 Verifying the physical connection . . . . . . . . . . . . . . . . . 99

7.1.3 Using a LAN . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1007.1.3.1 Installing and configuring a COCEN card. . . . . . . . . . 100

7.2 Setting up the OSI subnetwork . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 103



7.2.1 Using CLNS. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1047.2.1.1 Setting up a CLNS object . . . . . . . . . . . . . . . . . . . . . . 1047.2.1.2 Setting up a linkage object. . . . . . . . . . . . . . . . . . . . . . 1057.2.1.3 Adding manual adjacencies . . . . . . . . . . . . . . . . . . . . . 1077.2.1.4 Creating NSAPs and network protocol addresses . . . . 1087.2.1.5 Attaching NSAPs to network protocol addresses . . . . 111

7.2.2 Using CONS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1127.2.2.1 Creating NSAPs and network protocol addresses . . . . 1137.2.2.2 Attaching NSAPs to network protocol addresses . . . . 116

7.3 Configuring OSI applications and addresses . . . . . . . . . . . . . . . . . . . . . . 1187.3.1 Setting up local PAD and MSW applications . . . . . . . . . . . . . . 1197.3.2 Setting up local OSI applications. . . . . . . . . . . . . . . . . . . . . . . . 1227.3.3 Defining the CMISE service profile . . . . . . . . . . . . . . . . . . . . . 1257.3.4 Setting up the remote PAD and MSW applications. . . . . . . . . . 1287.3.5 Adding an O&M connection . . . . . . . . . . . . . . . . . . . . . . . . . . . 1307.3.6 Setting up remote applications. . . . . . . . . . . . . . . . . . . . . . . . . . 1327.3.7 Changing power measurements levels in a BSC . . . . . . . . . . . . 1347.3.8 Adding new counters in a BSC . . . . . . . . . . . . . . . . . . . . . . . . . 1357.3.9 Setting up logical files in the MSC/HLR. . . . . . . . . . . . . . . . . . 136

8 CONFIGURING INTERMEDIATE SYSTEMS . . . . . . . . . . . . . . . . 142

9 VERIFYING DCN INTEGRATION . . . . . . . . . . . . . . . . . . . . . . . . . 143

1 AC25-S NETWORK CARD. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1451.1 Jumper blocks. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1461.2 Memory space addresses . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1471.3 Interchangeability codes. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1481.4 Communication modes. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 149

2 AS7-U NETWORK CARD. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1502.1 Jumper blocks. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1512.2 Memory space addresses . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1512.3 Interchangeability codes. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1522.4 Memory size. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 153

3 COCEN NETWORK CARD . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1543.1 Jumper blocks. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1553.2 Memory space addresses . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1553.3 Interchangeability codes. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 156

4 CABLES. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 157

1 SERVERS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 160

2 NETWORK ELEMENTS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 162

1 SERVER WORKSHEET . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 164



2 NETWORK ELEMENT WORKSHEET . . . . . . . . . . . . . . . . . . . . . . 167

1 PRELIMINARY TASKS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 170

2 CONFIGURING THE NMS COMMUNICATIONS SERVER. . . . 171

3 CONFIGURING OSI APPLICATIONS . . . . . . . . . . . . . . . . . . . . . . 172

4 CONFIGURING THE CONNECTION SERVER SOFTWARE . . 173

5 CONFIGURING THE DX 200 NETWORK ELEMENT. . . . . . . . . 174

1 N - SELECTORS AND SPIS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1751.1 N - selectors for CLNS communications . . . . . . . . . . . . . . . . . . . . . . . . . 1751.2 SPIs for CONS communications . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 175

2 NETWORK PROTOCOL ADDRESS NAMES. . . . . . . . . . . . . . . . . 1762.1 CLNS network protocol address names. . . . . . . . . . . . . . . . . . . . . . . . . . 1762.2 CONS network protocol address names . . . . . . . . . . . . . . . . . . . . . . . . . 177

3 APPLICATION PARAMETERS . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1783.1 DX 200 applications. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 178

3.1.1 DX 200 applications in the BSC . . . . . . . . . . . . . . . . . . . . . . . . 1783.1.2 DX 200 applications in the DAXnode WLL . . . . . . . . . . . . . . . 1793.1.3 DX 200 applications in the MSC . . . . . . . . . . . . . . . . . . . . . . . . 1803.1.4 DX 200 applications in the HLR . . . . . . . . . . . . . . . . . . . . . . . . 1813.1.5 DX 200 applications in the Front End . . . . . . . . . . . . . . . . . . . . 182

3.2 NMS applications. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1833.2.1 NMS applications in DX 200 network elements . . . . . . . . . . . . 1833.2.2 DX 200 applications in the Communications Server. . . . . . . . 184

1 CS SERVER PROCESS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 186

2 ADMINISTRATIVE PROTOCOL MODULES . . . . . . . . . . . . . . . . 188

3 PROTOCOL SPECIFIC MODULES . . . . . . . . . . . . . . . . . . . . . . . . . 1903.1 Session logs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 191

INDEX. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 192

What is new



1 WHAT IS NEW

This chapter lists the changes in the Data Communications Network (DCN)integration guide (releases T9-T10).

1.1 Changes from T9 to T10

This section lists the changes in the DCN integration procedure anddocumentation between release T9 and T10.

• Information regarding integration from a router or Front End to the NMShas been moved toIntegrating Intermediate Systems, TAN 0900.

• Integration information regarding the DAXnode 5000 wireless local loophas been added throughout the manual.

• Section 4.2,Reviewing the system requirements on page 27 has beenadded.

• Section 5.2.1.3,Communications Server package on page 43 has beenadded. This section includes information regarding thecomm packageNSAP, MC/ServiceGuard and minor changes to thecomm packageconfiguration instructions.

• Section 6.8,Adding a route to a remote system on page 70 has been re-written with interrogation commands.

• Section 7.1.3.1,Installing and configuring a COCEN card on page 100 hasbeen re-written.

• Section 7.3,Configuring OSI applications and addresses on page 118 hasbeen re-written with interrogation commands.

• Section 7.3.9,Setting up logical files in the MSC/HLR on page 136 hasbeen re-written with new instructions regarding the Front End.

• In Appendix A.,Network card jumpers on page 144, all memory spaceaddress tables have been modified.

• In Appendix A,AC25-S network cardon page 145, the memory start andend addresses have been modified.

• In Appendix C.,Configuration information on page 160, all tables havebeen modified.

• In Appendix F.,OSI Parameters on page 175, all tables have beenmodified.

• Appendix G.,Connection Server processes on page 186 has been added.

About this manual



2 ABOUT THIS MANUAL

This document describes how to integrate the Network Subsystem (NSS) and theBase Station Subsystem (BSS) with the Nokia NMS (release T10).

This document is primarily concerned with connections from the NMS to anetwork element. Those connections can be made using analog X.25 (PSN),digital X.25 (PCM) and/or LAN connections. For instructions regarding third-party router or Front End integration see,Integrating Intermediate Systems, TAN0900.

Before beginning integration, read the first five chapters. After completing allpreliminary tasks, continue with Chapter 5,Configuring the NMSCommunications Server. As this manual was written in logical sequence, readeach chapter in the order presented.

If you are unfamiliar with connectionless (CLNS) and connection-oriented(CONS) network services, seeDCN Management, TAN 0377.

This customer document was written for the technical personnel of atelecommunications operator. As this document was written specifically forrelease T10, do not use this document to integrate other releases of the NokiaNMS.

2.1 What you need to know first

Before using this manual, ensure you are competent in the following areas andapplications.

• BSC (S6/S7) and MSC (M7B/M8) MML commands

• DX 200 technology

• GSM/DCS/PCS cellular networks

• Nokia NMS

• Open Systems Interconnection

• UNIX operating environment

• vi or another text editor supported by your system.

Ensure the following addresses and passwords are available:

• IP addresses for workstations and network elements

• Passwords for theomc, root, sysop andsysop1 users

• X.121 and NSAP addresses for all network elements

About this manual



2.2 How to use this manual

Use this manual as a step-by-step guide when integrating the network subsystemor base station subsystem with the Nokia NMS. If integrating network elementsusing other installation manuals, refer to this manual when implementing DCNsolutions.

2.3 Concepts and terminology

This section provides a brief list of the terms used in this manual. If a term orword does not appear in section please refer to theGlossary, TAN 0717.

Term Explanation

AC25-S Network card for analog X.25 communication

AFI Authority Format Identifier

administrative route A route supervised by the APM

APM Administrative Protocol ModuleA Connection Server process that verifies thefunctionality of the physical connection to the host.

APT Application Process Title

AS7-U Network card for digital X.25 communication

BCSU Base Station Controller Signalling Unit

BDCU Basic Data Communications Unit

BSS Base Station Subsystem

CCSU Common Channel Signalling Unit

CLNS Connectionless Network Service

CMIP Common Management Information Protocol

CMISE Common Management Information ServiceElement

COCEN DX 200 Ethernet card

Communication Server A workstation running HP-UX that serves andimplements connections.

Connection Server An NMS application that provides transparentconnections to clients and network elements.

CONS Connection-oriented Network Service

DAXnode 5000 WLLDAXnode WLL

A Digital Access Node for Wireless Local Loopsthat supports 5000 subscribers.

DCE Data Circuit-terminating Equipment

About this manual


NTC TAN 0839/2.2 en10

DCN Data Communications NetworkA logical representation of the physical networkthat connects network elements to the NokiaNMS.

DSP Domain Specific Part

DTE Data Terminal Equipment

DX 200 A type of network element (digital switch)developed and manufactured by Nokia.

ES End System

ET Exchange Terminal

FE Front End

FCMU Fault and Configuration Management Unit

FTAM File Transfer, Access and ManagementA standard file transfer protocol that enables datato be accessed in remote files. Parts or all of thesefiles can then be transferred between systems.

GSW Group Switch

IDI Initial Domain Identifier

IP Internet Protocol

IS Intermediate System

ISO International Organization for Standardization

LAN Local Area Network

LLC Logical Link Control

MAC Media Access Control

MML Man-machine language

MSW Message Switch

NMS (Nokia) Network Management System

NSAP Network Service Access Point

NSS Network Subsystem

OMU Operations and Maintenance Unit

OSI Open Systems Interconnection

osiadmin OTS 9000 OSI administration program. Thisprogram allows you to set up and maintain OTS9000.

OTS HP’s OSI Transport Services

OTS/9000 Hewlett-Packard's implementation of OSITransport Services and related protocols.

Term Explanation

About this manual


NTC TAN 0839/2.2 en11

Table 1.Terms and explanations

PAD Packet Assembler Disassembler

PCM Pulse Code Modulation

PDE Power Distribution Equipment

PID Protocol Identifier

PIU Plug-in Unit

PVC Permanent Virtual CircuitPermanent virtual circuits maintains permanentassociations.

SNPA Subnetwork Point of Attachments

• X.121 address of the AC25-S card

• MAC address of the COCEN card

SPI Subsequent Protocol Identifier

SVC Switched Virtual CircuitsSwitched virtual circuits maintain associationsonly for the current connection call.

TSL Time slot

V.24 ITU-T specification for connecting DTE (forexample, a PC) with DCE (for example, a modem)

V.35 ITU-T specification for modems for synchronousdata transmission

V.36 ITU-T specification for modems for synchronousdata transmission using 60-108kHz group bandcircuits

V5.2 A dynamic multiplexer interface between a localnetwork and a separate subscriber network.

VT Virtual Terminal

WLL Wireless Local Loop

X.121 An international numbering plan for public datanetworks. Each network element in atelecommunications network has its own X.121address.

X.121 address The address assigned to each local X.25 card orport

X.21 Interface between the DTE and the DCE forsynchronous operation on a data network

X.25 An interface between the DTE and the DCE in apacket switched network using X.21 at the physicallayer.

Term Explanation

About this manual


NTC TAN 0839/2.2 en12

2.4 Typographic conventions

Several typographical conventions are used in this manual to describe differentactions and restrictions. The following table presents those conventions.

2.4.1 Text styles

Table 2.Text styles in this document

Style Explanation

Initial Upper-Case • Application names

• Hardware components

• Names of windows and dialogs

Initial Upper-Casein Italics

• Referenced documents

• Referenced sections and chapters within adocument

UPPER-CASE • Keys on the keyboard (ALT, TAB, CTRL etc.)

Italic • Emphasis

• State, status or mode

Courier font • File and directory names

• Names of database tables

• Parameters

• User names

• System output

• User input

Bold • Graphical user interface components

<bracketed text> • Variable user input

Shaded box • Further information about command lineparameters

About this manual


NTC TAN 0839/2.2 en13

2.4.2 Command line conventions

Command line prompts

The following UNIX command line prompts are used to define the type of user.Do not include the prompt in the command line.

Table 3.Command line prompts

Environment variables

This document assumes the following environment variables have the valuesindicated below:

Table 4.Environment variables used in this document

Product delivery numbers

The following symbols are used to represent the C numbers (the deliverynumbers) of network elements:

Table 5.Conventions for C numbers

Prompt User

# Root user

username>% User indicated byusername.

% Any user

> Service terminal or MML prompt

Variable Value

$OMCCONFPATH /usr/local/NokiaOMC/conf/global

$OMCROOT /usr/local/<omc_build>

Notation Explanation

<ccccc> C number of the Front End

<bbbbb> C number of the BSC/DAXnode WLL

<mmmmm> C number of the MSC

<hhhhh> C number of the HLR

<qqqqq> C number of any network element (specified inthe context of usage)

About this manual


NTC TAN 0839/2.2 en14

Line breaks

For layout purposes, long command lines may be split into two or more separatelines. This is indicated as follows:

With UNIX commands and UNIX file descriptions, a backslash (\ ) at the endof a printed line is used to indicate that the command continues on the followingline. For example:

# cat /etc/cmcluster/pkgcomm/control.sh.log | grep \"crontab" | more

With MML commands, everything between the initialZ and the semicolon ( ; )constitutes a single line. For example:

ZWTP:OMU:AS7_U,<PIU_index>,<track>::X25,<PCM_type>,<PCM_number>,TSL,0;

Optional parameters

With all types of commands, square brackets ([ ] ) are used to indicate that theportion of the command enclosed in brackets is optional or not always required.For example:

ZUSU:<unit>[,<index>];

The above example indicates when dealing with several units of the same type(for example, the BDCUs), it is necessary to also specify the index. With singleunits (for example, the OMU), the index parameter is not necessary.

Conditional parameters

With all types of commands, braces{} and pipes| are used to indicate that theportion of the command enclosed in brackets is conditional. For example:

# cmmodpkg { -e | -d } <package>

The above example indicates that you must select between the-e and-d optionswhen you enter the command.

About this manual


NTC TAN 0839/2.2 en15

2.5 Where to find more

During integration, you may need to refer to other documentation. Ensure thesemanuals are available before beginning DCN integration.

Introductory documents

• If you need information on other NMS manuals, see NMS/2000Description of Documentation, TAN 0442.

Reference guides

• For more infomation on terms used in this guide, seeGlossary, TAN 0717.

• For more information on hardware, Nokia NMS applications, processesand configuration files, seeTechnical Reference Guide, TAN 0453.

Installation guides

• For more information on NSAPs, DCN implementation and an overviewof DCN solutions, seeDCN Management, TAN 0377.

• For more information on integrating a router or the Nokia NMS Front End,seeIntegrating Intermediate Systems, TAN 0900.

System administrator’s guides

• For more information on rebooting the NMS, seeWorkstation NetworkMaintainence, TAN 0513.

• For more information on MC/ServiceGuard, seeSystem ManagementBasic Operating Principles and Procedures, TAN 0732.

System management online helps

• For more information on using User Group Profiles, seeUser GroupProfiles Online Help, TAN 0713.

• For more information on creating views and managed objects, seeNetworkEditor Online Help, TAN 0879.

Troubleshooting guides

• For more information on DCN integration tests, seeTesting Installations,TAN 0523.

Hewlett Packard documentation

• For more information on setting up PAD in the Communications Server,seeX.25/9000 User’s Guide.

Introduction to DCN integration


NTC TAN 0839/2.2 en16

3 INTRODUCTION TO DCN INTEGRATION

DCN integration represents a logical series of ordered tasks that bridge the gapbetween network elements and the Nokia NMS.

Once DCN integration is completed, the Nokia NMS will be able to performconfiguration, fault and performance management functions from a centralisedlocation.

As DCN integration is a very complicated process, do not deviate from the orderthat this information is presented. Attempts to follow advise contrary to what iswritten in this guide may result in costly delays.

To successfully integrate a data communications network, familiarise yourselfwith the logical models, principles and task sequences that are explained in thisand other DCN guides.

This chapter provides a brief introduction to the following topics:

• Integration principles

• Network topologies

• Network services

• Integration procedures

• Hardware

Note:

Before beginning DCN integration, ensure that all network elements areconfigured and functioning correctly.



NTC TAN 0839/2.2 en17

3.1 Integration principles

When integrating different systems, establish a means by which data istransferred from one network element to the other. Communication in the DataCommunications Network (DCN) is based on the Open Systems Interconnection(OSI) model.

This model defines a seven-layer structure for transferring data from onenetwork element to the other. For more information regarding OSI and DCNprinciples, seeDCN Management, TAN 0377.

3.2 Network topologies

The network topology defines whether you will connect a network elementdirectly to the NMS Communications Server (ES) or indirectly using a router orFront End (IS).

This topology also defines the cabling layout of your network. Once the networktopology is defined, identify the network services (CONS or CLNS) andprotocols to be used (X.25, ISO/IP and others).

3.3 Network services

Network services allow for the transfer of data between the OSI network andtransport layers. The network services available in an ISO OSI datacommunications network are:

• Connectionless network service

• Connection-oriented network service



NTC TAN 0839/2.2 en18

3.3.1 Connectionless network service

When using a connectionless network service (CLNS), communication isestablished using the following types of networks:

Table 6. CLNS connections from the NMS

The Nokia NMS does not support digital X.25 (PCM) connections from the ISto the NMS Communications Server. Digital X.25 (PCM) connections are onlypossible from an IS (router or Front End) to a network element.

Note:

When using analog X.25 (PSN), the actual connection can be either point-to-point or through an analog X.25 packet network.

The following figure illustrates how a network element is directly connected tothe NMS Communications Server using CLNS/LAN.

Figure 1.Direct network element integration (CLNS/LAN)

Type of network Type of connection from the Nokia NMS

Ethernet Direct (NMS - network element)Indirect (NMS - IS - network element)

Analog X.25 (PSN) Direct (NMS - network element)Indirect (NMS - IS - network element)



NTC TAN 0839/2.2 en19

The following figure illustrates how a network element is indirectly connectedto the NMS Communication Server using CLNS/LAN and CLNS/digital X.25.

Figure 2. Indirect network element integration CLNS/digital X.25 (PCM)

For more information regarding indirect connections using a router, seeIntegrating Intermediate Systems, TAN 0900.



NTC TAN 0839/2.2 en20

3.3.2 Connection-oriented network service

When using a connection-oriented network service (CONS), communication isestablished using the following type of network.

Table 7.CONS connections from the NMS

The Nokia NMS does not support digital X.25 (PCM) connections from theNMS Communications Server. Digital X.25 (PCM) connections are onlypossible from an IS (router or Front End) to a network element.

Note:

When using analog X.25, the actual connection can be either point-to-pointconnection or through an analog X.25 packet network.

The following figure illustrates how a network element is directly connected tothe NMS Communications server using CONS/analog X.25 (PSN).

Figure 3.Direct network element integration CONS/analog X.25 (PSN)

Type of network Type of connection from the Nokia NMS

Analog X.25 (PSN) Direct (NMS - network element)



NTC TAN 0839/2.2 en21

The following figure illustrates how a network element is directly connected tothe NMS Communication Server using CONS over analog X.25 (PSN).

Note:

In the figure below, the router functions as an X.25 switch, not an intermediatesystem

Figure 4.Direct network element integration CONS/analog X.25 (PSN)



NTC TAN 0839/2.2 en22

3.4 Integration procedures

The basic integration procedures for DCN integration include performing thetasks listed in the following table. When integrating an Intermediate System (IS),refer to the instructions inIntegrating Intermediate Systems, TAN 0900.

The exact procedure for DCN integration is determined by the network topology(direct or indirect), service (CLNS or CONS) and type (X.25 or LAN).

Figure 5.Basic procedures for DCN integration (ES-ES)

Task NMS Networkelement

IS(FE)

Set up the OSI subnetwork (CLNS/CONS) X X X

Configure OSI applications and addresses X X X

Edit Connection Server configuration files X - -

Setting up the physical connection - X -



NTC TAN 0839/2.2 en23

3.5 Hardware

3.5.1 Network cards

The network cards for integration are located in the Operations and MaintenanceUnit (OMU) of the BSC and in the Basic Data Communications Unit (BDCU) ofthe MSC/HLR and Front End.

Figure 6.Network cards in the DX 200

3.5.1.1 AC25-S

The AC25-S allows for the connection of synchronous data transmissionchannels following the HDLC protocol to a microcomputer unit. AC25-S cardsare used for analog X.25 (PSN) connections in the DX 200.

3.5.1.2 AS7-U

A multichannel terminal used for controlling LAPD signalling channels. AS7-Ucards are used for digital X.25 connections (PCM).

3.5.1.3 COCEN

COCEN cards are used for LAN connections. COCEN cards are connected using10Base2 (coax), 10Base5 (AUI) or 10BaseT cable (twisted pair).



NTC TAN 0839/2.2 en24

3.5.2 Intermediate systems

Due to a pre-existing network configuration, there may be an IntermediateSystem (IS) present in your network. To maintain the structure of this network,use an IS to route data from a network element(s) to the NMS CommunicationsServer.

For more information regarding indirect connections using a router, seeIntegrating Intermediate Systems, TAN 0900.

3.5.2.1 Nokia NMS Front End

The Nokia NMS Front End is based on the same DX 200 technology used fordigital switching systems. It consists of processor units with Intel 386/486 basedmicrocomputers interconnected using a fast parallel bus.

The network management functions are concentrated in the Fault andConfiguration Management Units (FCMUs) of the microcomputers. TheFCMUs are duplicated to achieve better fault tolerance.

3.5.2.2 Cisco routers

Cisco routers consist of the router itself and Cisco’s IOS software. Cisco’s IOSsoftware provides a variety of feature sets. You can choose a feature set thatsupports your specific protocol environment. This software supports both LANand WAN protocols, optimising WAN services and controlling internetworkaccess. In addition, Cisco’s IOS software allows centralised, integrated andautomated installation and management of internetworks.

Preliminary tasks


NTC TAN 0839/2.2 en25

4 PRELIMINARY TASKS

This chapter lists the tasks you must complete before beginning integration.These tasks are common to all connection types and include the following:

• Filling in the configuration sheets

• Reviewing the system requirements

• Creating managed objects in the NMS

• Creating and modifying user group profiles

Figure 7.Preliminary tasks

Preliminary tasks


NTC TAN 0839/2.2 en26

4.1 Filling in the configuration sheets

Before beginning the integration, read Appendix C.,Configuration informationon page 160 and make a copy of the worksheets on page 164. When filling in theworksheets ensure the following information is specified:

• Servers

• Hardware

• Role

• Software

• Hostname

• Physical address (IP and/or X.121)

• NSAPs addresses (physical andcomm package)

• Type of NSAPs

• Network elements

• Hardware

• Role

• Software

• Hostname

• Physical address (X.121-DTE)

• NSAPs address

• C-number

Preliminary tasks


NTC TAN 0839/2.2 en27

4.2 Reviewing the system requirements

This section lists the requirements for each of the following objects:

• NMS

• BSC

• MSC/HLR

4.2.1 NMS

Before beginning integration, ensure the NMS meets the followingrequirements:

• The T10 environment is tested and fully functional.

• OSI Transport Services (OTS) is installed on the Communications andStandby Servers.

Preliminary tasks


NTC TAN 0839/2.2 en28

4.2.2 BSC

Before beginning integration, ensure the BSC meets the following requirements:

• Software version S6/S7 is installed and fully functional.

• The following change deliveries are installed, active, and set as default.

• S6 =SX 6.9-0

• S7 =S7 7.12-0

To check which change deliveries are installed in the BSC enter:

ZWQO:CR;

The following output appears with the applicable data filled in:

LOADING PROGRAM VERSION 3.5-0

PACKAGES CREATED IN OMU:

SW-PACKAGE STATUS DIRECTORY ENVIRONMENT DEF ACTPACKAGE-ID (REP-ID) DELIVERY

CD-ID

S7000GEN BU AS7_7_16_0 S7 7.12-0 Y YS7 7.16-0 2 CID000SX 6.4-0

S7003GEN

S6980703 NW S6REL SX 6.9-0 - YSX 6.16-0 2 CID000SX 5.5-0

S6EME110

S7002GEN UT AS7_7_16_0 S7 7.12-0 - NS7 7.16-0 CID000SX 5.5-0

S7002GEN

COMMAND EXECUTED

SOFTWARE PACKAGE ADMINISTRATION COMMAND <WQ_>

Preliminary tasks


NTC TAN 0839/2.2 en29

4.2.3 MSC/HLR

Before beginning integration, ensure the MSC/HLR meet the followingrequirements:

• Software version M7B/M8 is installed and fully functional.

• The following change deliveries are installed, active, and set as default.

• M7B = M7B 7.31-0

• M8 = M8 6.10-0

To check which change deliveries are installed in the MSC/HLR enter:

ZWQO:CR;



PACKAGES CREATED IN OMU:

SW-PACKAGE STATUS DIRECTORY ENVIRONMENT DEF ACTPACKAGE-ID (REP-ID) DELIVERY

CD-ID

M8690 BU MI_6_9_0 M8 6.10-0 Y YM8 6.9-0 CID38411 8.6-0

M8680 NW MI_6_8_0 M8 6.8-0 - YM8 6.8-0 CID38411 8.5-0

M7260 UT AM_7_26_0 MX 7.24-3 - NMX 7.26-0 CID38411 2.13-0

COMMAND EXECUTED

SOFTWARE PACKAGE ADMINISTRATION COMMAND <WQ_>

Other requirements

Ensure the OSI selector values in the MSC/HLR match the NMS.

Preliminary tasks


NTC TAN 0839/2.2 en30

4.3 Creating managed objects in the NMS

Before the NMS can receive and store network element data, create the managedobjects in the NMS. For more information on creating managed objects, seeNetwork Editor Online Help, TAN 0879.

BSS integration

The managed objects required for BSS integration are:

• BAL(s)

• BSC(s)

• BCF(s)

• BTS(s)

• HOC(s)

• MAL(s)

• PCM(s)

• POC(s)

• TRX(s)

The required transmission objects are:

• DN2(s)

• SM(s)

• TC(s)

NSS integration

The managed objects required for NSS integration are:

• HLR

• MSC

• PCM(s)

DAXnode integration

The managed object required for DAXnode integration is:

• DAXnode 5000 WLL

Preliminary tasks


NTC TAN 0839/2.2 en31

4.4 Creating and modifying user group profiles

To establish a connection to a network element, ensure the user group profilesare present and their command class authorities are properly defined.

For information about setting user group profiles from the Top-level UserInterface, seeUser Group Profiles Online Help, TAN 0713.

To create or modify user group profiles

1. Start an MML session to a network element.

2. If using a BSC, ensure the customer-defined user group profiles are presentand all command class authorities are defined as250 by entering:

ZIAI:PROFILE=ALL;

The following output is displayed with the applicable data filled in.


EXECUTION STARTED

DX 200 TOM 1998-10-02 10:00:00

PROFILE NAME: TEST

COMMAND CLASS AUTHORITIES:

A=250 B=250 C=250 D=250 E=250 F=250 G=250 H=250 I=250 J=250

K=250 L=250 M=250 N=250 O=250 P=250 Q=250 R=250 S=250 T=250

U=250 V=250 W=250 X=250 Y=250

UNIQUE PROFILE: NO

PROFILE IS USED BY: SYSOP1

COMMAND EXECUTED

MMI SYSTEM AUTHORITY HANDLING COMMAND <IA_>

3. If a suitable profile is not present and/or its command class authorities arenot set to250 , create/modify the user group profile by entering:

ZIAA:<user_profile>:ALL=250;

<user_profile> The name of the customer-defined userprofile.

Preliminary tasks


NTC TAN 0839/2.2 en32

4. If using an MSC/HLR, ensure theTRAFADMI user group profile is presentand its command class authorities are defined as1 by entering:

ZIAI:PROFILE=TRAFADMI;

5. If TRAFADMI is not present and/or its command class authorities are not setto 1, create/modify theTRAFADMI by entering:

ZIAA:TRAFADMI:ALL=1;

4.5 Creating and modifying user IDs

To create or modify user IDs

1. Start an MML session to a network element.

2. Ensure theSYSOP1 user ID is present by entering:

ZIAI:USERID=SYSOP1;

The following output is displayed with the applicable data filled in.


EXECUTION STARTED

DX 200 TOM 1998-10-02 10:00:00

USER ID: SYSOP1

PROFILE NAME: SYSTEM

COMMAND CLASS AUTHORITIES:

A=250 B=250 C=250 D=250 E=250 F=250 G=250 H=250 I=250 J=250

K=250 L=250 M=250 N=250 O=250 P=250 Q=250 R=250 S=250 T=250

U=250 V=250 W=250 X=250 Y=250

UNIQUE PROFILE: NO

NETWORK USE ALLOWED: YES

COMMAND EXECUTED

MMI SYSTEM AUTHORITY HANDLING COMMAND <IA_>

Preliminary tasks


NTC TAN 0839/2.2 en33

3. If SYSOP1 is not present create theSYSOP1 user group ID by entering:

ZIAH:SYSOP1:<user_profile>;

The system will prompt you for a password.

4. When creatingSYSOP1, enter the same password present in the NMSworkstationSYSTEM user group profile.

NEW PASSWORD: <password_in_workstation>VERIFICATION: <password_in_workstation>

5. Give SYSOP1 execute rights for Configuration Management (CM),Performance Management (PM) and Fault Management (FM) applicationsby entering:

ZIOA:SYSOP1:APPL=CM-X;ZIOM:SYSOP1:APPL=PM-X;ZIOM:SYSOP1:APPL=FM-X;

6. If using an MSC/HLR, ensure theTRAFAD user group ID is present byentering:

ZIAI:USERID=TRAFAD;

7. If TRAFAD is not present create theTRAFAD user group ID by entering:

ZIAH:TRAFAD:TRAFADMI;

The system will prompt you for a password. The password forTRAFAD, isALLPASSW.

<user_profile> The name of the user profile created inSection 4.4,Creating and modifyinguser group profiles.

Configuring the NMS Communications Server


NTC TAN 0839/2.2 en34

5 CONFIGURING THE NMS COMMUNICATIONSSERVER

This chapter describes the procedure for configuring the NMS CommunicationsServer for OSI communications. The following topics are covered:

• Enabling X.121 subaddressing

• Setting up the OSI subnetwork

• Using CONS

• Configuring OSI applications and addresses

Figure 8. Configuring the NMS Communications Server



NTC TAN 0839/2.2 en35

5.1 Enabling X.121 subaddressing

X.121 subaddresses enable several X.25 addresses to be multiplexed through asingle X.25 card (using CONS and CLNS simultaneously). Traditionally X.121subaddresses are not used in DCN integration.

Only use X.121 subaddressing if integrating a system that follows at least one ofthe requirements listed below.

• you are using CONS and CLNS at the same time through a single analogX.25 card.

• you are planning to change your network service (from CONS to CLNS)soon.

If your network does not follow at least one of these requirements or you areusing a LAN, seeSetting up the OSI subnetworkon page 37.

To enable X.121 subaddressing (CONS/CLNS)

1. Login to the Communications Server as theroot user and set theDISPLAY environment.

2. Open anhpterm session by entering:

# hpterm &

3. In thehpterm window, start theosiadmin utility by entering:

# /opt/ots/bin/osiadmin

4. Using the arrow keys, selectX.25 and press ENTER.

5. Using the arrow keys, selectStop X.25 and follow the instructions given.

6. Start HP’s System Administration Manager (SAM) by selectingConfigure X.25 → and press ENTER.

7. SelectNetworking and Communications.

8. SelectNetwork Interface Cards.



NTC TAN 0839/2.2 en36

9. SelectX.25 card.

10. SelectConfigure X.25 address.

11. In theConfigure X.25 address window, remove the last two digits fromthe X.25 address (ensure the X.25 address has 10 digits) and selectOK .

12. SelectOK.

13. Ensure the X.25 card is enabled and selectFile → Exit.

14. Exit SAM by selectingFile → Exit SAM .

15. In theosiadmin window, selectPrevious Menu.

Note:

Do not exit from theosiadmin utility. This application will be used toconfigure the OSI subnetwork.

16. Go to Section 5.2,Setting up the OSI subnetwork on page 37



NTC TAN 0839/2.2 en37

5.2 Setting up the OSI subnetwork

The following figure illustrates the procedure for setting up the OSI subnetworkin the NMS Communications Server. If setting up a CONS subnetwork go toUsing CONSon page 46.

Figure 9.Setting up the OSI subnetwork in the NMS Communications Server

comm



NTC TAN 0839/2.2 en38

5.2.1 Using CLNS

When setting up an CLNS subnetwork, the NMS Communications Server doesnot make any distinction between analog or digital X.25.

Therefore, all X.25 connections (whether analog or digital) are referred to asX.25 connections. When setting up an OSI subnetwork using CLNS thefollowing options are available:

• Setting up a CLNS subnetwork for X.25

• Setting up a CLNS subnetwork for LAN

Setting up CLNS in the Communications Server requires the use of theosiadmin utility. If using a LAN, seeSetting up a CLNS subnetwork for LANon page 41.

Note:

Only set up the CLNS/X.25 subnetwork when no existing subnetwork is usable.



NTC TAN 0839/2.2 en39

5.2.1.1 Setting up a CLNS subnetwork for X.25

Depending on your network plan, CLNS over X.25 is used under in the followingsituations:

• When using a Front End

• When simultaneously using LAN and X.25

• When grouping X.25 cards using CLNS

To set up the CLNS subnetwork for X.25



# hpterm &



4. Using the arrow keys, selectOTS and press ENTER.

5. SelectConfigure OTS and press ENTER.

6. Ensure theUpdate Mode parameter is set toR (Restart) and selectF4. TheOTS Configuration screen is displayed.

Note:

If you encounter the following error message:

The osiconfchk program reported a validation error.

Exit OSIADMIN, runosiconfchk and follow the instructions given.

7. Using the arrow keys, selectSubnetworks → Configure and pressENTER.



NTC TAN 0839/2.2 en40

8. SelectCLNS over X.25→ Add... and press ENTER.

9. Fill in the appropriate fields.

10. SelectPerform task then press the space bar.

11. Repeat steps 8 through 10 until all OSI subnetworks have been added.

<Subnetwork name > clnsx25_0

If using several subnetworks, distinguishthem by entering:

clnsx25_0, clnsx25_1, clnsx25_2

<Network ID> Leave this field empty

<Local networkaddress (NSAP)>

• Grouping X.25 cards =comm packageNSAP address

• Using X.25 and LAN = Communications

Server physical NSAP address

<Subaddress> Subaddress to identify the subnetworkwithin the X.25 card.

• 01 for CLNS subnetworks

• NULL if you are not using a subaddress

If grouping X.25 cards, ensure thesubaddress is the different for each card.

<X.25Programmaticaccess name >

Name of the X.25 card. The name can befound in the/etc/x25/x25config_<no.> file where<no.> is thenumber of the X.25 card.

If grouping X.25 cards, distinguish eachprogrammatic access name by entering:

x25card_0, x25card_1

If... Then proceed to...

there is no intermediate systemAdding an ISO OSI destinationonpage 48

there is an intermediate systemAdding an IS as an ISO OSIdestinationon page 50



NTC TAN 0839/2.2 en41

5.2.1.2 Setting up a CLNS subnetwork for LAN

To set up a CLNS subnetwork for LAN, follow the instructions listed below. Ifusing redundant LAN connections enable the OTSsnet_query_subnetparameter as described in,Integrating Intermediate Systems, TAN 0900.

To set up a CLNS subnetwork for a LAN

1. Login to the Communications Server as the root user and set theDISPLAY environment.


# hpterm &






Note:







NTC TAN 0839/2.2 en42

8. SelectCLNS over 802.3→ Add... and press ENTER.

9. Fill in the in the appropriate fields:

10. SelectPerform task then press the space bar.

11. Go toCommunications Server packageon page 43.

<Subnetwork name> clnslan_0

If using several subnetworks,distinguish them by entering:clnslan_0, clnslan_1

<Network ID> Leave this field empty

<Local network address(NSAP)>

NSAP of the Communications Server.Use the same NSAP address for allCLNS/LAN connections.

<Device interface name > Name of the LAN interface.Determine the available names of theLAN interfaces by entering:# /etc/lanscan

The name of the interface is shown intheNameUnit field.

<CLNP subset> 3 (Full - Discard Null)



NTC TAN 0839/2.2 en43

5.2.1.3 Communications Server package

Applications services (HP-UX processes) and their hardware resources arebundled intopackages. Those packages are associated with a specific node andgiven a unique NSAP address. For more information regarding nodes andpackages, seeSystem Management Basic Operating Principles and Procedures,TAN 0732.

When performing DCN integration, the Communications Server acts as one ofthe primary nodes that form a high-availability cluster and it uses a unique NSAPaddress to identify its own MC/ServiceGuard package.

The Nokia NMS processes and the/global disk on the CommunicationsServer are bundled into the (comm) package.

When configuring thecomm package NSAP address use one of the free NSAPaddresses designated by your national authority. For more information aboutNSAP addresses, seeDCN Management, TAN 0377.

From the network perspective, thecomm package address is configured in the/etc/cmcluster/sgscusmx.cf configuration file and resident in theworkstations of either node. However, that address is only active in one server ata time. An example is illustrated below.

Figure 10.Usage ofcomm package NSAP address



NTC TAN 0839/2.2 en44

A comm package NSAP is only used when:

• An ISO IP LAN is used

and

• MC/ServiceGuard is used

Ensure thecomm package NSAP is different than the physical NSAP of theCommunications and Standby Server. In the event a single service, node,network or other resource failure, MC/ServiceGuard transfers the control of thecomm package from the Communication Server (primary node) to the StandbyServer (adoptive node).

Note:

In some cases, thecomm package NSAP is referred to as the dynamic NSAP. Thedynamic NSAP address is fixed and does not change. This term only refers to thedynamic nature of thecomm package NSAP. This address is dynamically addedand removed from the routing tables in the Communications or Standby Servers.

5.2.1.4 Adding the comm package NSAP

When using an ISO IP LAN as a DCN solution with MC/ServiceGuard, theCommunication Server softwarecomm package is given a NSAP address of itsown. This address is dynamically added to the Communications Server by MC/ServiceGuard.



NTC TAN 0839/2.2 en45

To add the comm package NSAP

1. Login to the Communications Server as the root user and set theDISPLAY environment.

2. Stop the MC/ServiceGuard cluster by entering:

# cmhaltcl -f -v

3. Using a text editor, open the/etc/cmcluster/sgscusmx.cf file, andensure thedcn_lan_used parameter is enabled.An example islisted below:

(cluster "<name>"

(nms_type "NMS/2000")

(oracle_sid "omc")

(oracle_home "/d/db01/app/oracle/product/7.3.2")

(dcn_x25_used "NO")

(dcn_lan_used "YES")

(cron_users "root oracle omc")

)

4. Add thecomm package NSAP in the cluster packages section of the/etc/cmcluster/sgscusmx.cf file as follows:

(package "comm"

(node "<comm_server>")

(node "<standby_server>")

(ip_address "<pkg_ip_address>")

(subnet "<subnet>")

)

(nsap "<comm_package_nsap>")

(monitor_subnet "<subnet>")

(file_system "/d/global"

(logical_volume "/dev/vgglobal/lvol1")

(symbolic_link "/global")

)

The variables are described in the comments of thesgscusmx.cf file.

5. Update the binary files of MC/ServiceGuard by entering:

# cd /etc/cmcluster# ./sgscfumx.sh -v

6. Restart MC/ServiceGuard by entering:

# cmruncl -v

7. Go to Section 5.2.5,Adding a default route on page 51.



NTC TAN 0839/2.2 en46

5.2.2 Using CONS

To set up an CONS subnetwork for X.25, follow the instructions listed below.

Note:

This task only needs to be carried out if there are no existing subnetworks thatcan be used.

To set up a CONS subnetwork for X.25

1. Login to the Communications Server as theroot user and set theDISPLAY environment

2. Open ahpterm session by entering:

# hpterm &






Note:





8. Select CONS overX.25 → Add and press ENTER.



NTC TAN 0839/2.2 en47

9. Fill in the in the appropriate fields:

10. SelectPerform task and then press the space bar.

11. Go to Section 5.2.3,Adding an ISO OSI destination on page 48.

<Subnetwork name> hpconsx25_0

If using several subnetworks, distinguishthem by entering:

hpconsx25_0 , hpconsx25_1

<NSAP> 10 first digits of the CommunicationsServer X.121 address

Subnetworkstandard(s) allowed

ISO 8878 NX.25 1980YX.25 1984YX.25 1988Y

<Subaddress> Subaddress to identify the subnetworkwithin the X.25 card.

• 00 for CONS subnetworks

• NULL if you are not using a subaddress

If grouping X.25 cards, ensure thesubaddress is the different for each card.

<X.25 Programmaticaccess name>

Name of the X.25 card. The name can befound in the/etc/x25/x25config_<no.> file where<no.> isthe number of the X.25 card.



NTC TAN 0839/2.2 en48

5.2.3 Adding an ISO OSI destination

Add an ISO OSI destination system to the network service configuration only ifyour are using:

• CONS over X.25

• CLNS over X.25without an IS

To add an ISO OSI destination system

1. In the Subnetwork Configuration window, selectPrevious Menu.

2. SelectDestination Systems→ Add and press ENTER.

3. Fill in the appropriate fields:

4. SelectPerform task and then press the space bar.

Network address (NSAP) NSAP of the remote NE

CLNS: use the full NSAP address.

CONS: use the physical (X.121)address of the remote system.

Physical address Subnetwork (X.121) address of theremote NE

Outgoing subnetwork name Name of the outgoing subnetworkused for the connection

End System, IntermediateSystem or Both?

0 = End System

Request reverse charge?(y/n)

n



NTC TAN 0839/2.2 en49

5. Using a text editor, edit the/etc/opt/ots/conf/ots_dests file.Change the line

dest_iso8878 1

to

dest_iso8878 0

After the above changes have been made, refer to the specification part ofthe ots_dests file. An example is listed below. The actual values forsome of the parameters may vary.

Note:

The value fordest_net_address is the X.121 address of the remotenetwork element. If using a CLNS connection the value fordest_net_address is the NSAP of the remote system.

dest_net_address 229315840000dest_phys_address 229315840000dest_out_subnet hpconsx25_<no.>dest_esis 0# 0 2 0dest_reverse_charge_req 0# 0 1 0dest_iso8878 0dest_x25_1980 1dest_x25_1984 1dest_x25_1988 1dest_fc_negotiation 0dest_fast_select 0dest_tc_negotiation 0

6. In theosiadmin main screen, use the arrow keys to selectOTS and pressENTER.

7. SelectUpdate OTS and press ENTER.

8. Select Previous Menu and then Exit OSIADMIN.

To ensure OSI configuration was successful

1. In thehpterm window, runosiconfchk on the Communications Serverby entering:

# /usr/bin/osiconfchk

2. Go toConfiguring OSI applications and addresseson page 52



NTC TAN 0839/2.2 en50

5.2.4 Adding an IS as an ISO OSI destination

To add an IS as an ISO OSI destination, follow the instructions listed below:

To an IS as an ISO OSI destination

1. In the Subnetwork Configuration window, selectPrevious Menu.

2. In the OTS configuration screen, selectDestination Systems→ Add...


4. SelectPerform Task and thenPrevious Menu.

5. Go to Section 5.2.5,Adding a default route on page 51.

Network address (NSAP) NSAP of the IS

Physical address X.121 address of the IS

Outgoing subnetwork name Name of the CLNS subnetwork

End System, IntermediateSystem or Both

• 1 when using a router

• 2 when using a Front End

Request reverse charge?(y/n)

n



NTC TAN 0839/2.2 en51

5.2.5 Adding a default route

To add a default route to an intermediate system, follow the instructions listedbelow.

To add a default route

1. In theosiadmin main menu, use the arrow keys to selectOTS and pressENTER.



4. SelectRoutes→ Add... and press ENTER.


6. SelectPerform Task and then press the space bar.

7. SelectBACK TO OSIADMIN and then press the space bar.

8. SelectUpdate OTS and press ENTER.

9. After OTS is updated, press ENTER.

10. Select Previous Menu and thenExit OSIADMIN .

To ensure OSI configuration was successful

1. In thehpterm window, runosiconfchk on the Communications Serverby entering:

# /usr/bin/osiconfchk

2. Go toConfiguring OSI applications and addresseson page 52.

Network ID or networkaddress (NSAP)

0 (zero)Indicates the default route

Subnetwork Name Name of the CLNS subnetwork,see 5.2.1.2,Setting up a CLNSsubnetwork for LAN on page 41.

Primary route (NSAP) NSAP of the IS



NTC TAN 0839/2.2 en52

5.3 Configuring OSI applications and addresses

The following figure illustrates the procedure of configuring the OSIenvironment in the NMS Communications Server. If using a LAN, seeSettingup DX 200 OSI applicationson page 56.

Figure 11.Configuring the OSI applications in the Communications Server

Note:

PAD service is only available when the connection is over X.25 (analog ordigital).

If X.25 is used, set up the PAD service as an additional level of network stabilityin the event OSI VT fails.



NTC TAN 0839/2.2 en53

5.3.1 Setting up PAD services

Before establishing PAD connections, the X.121 address of the network elementmust be configured in the/etc/x25/x29hosts file.

5.3.1.1 PAD service for outgoing connections

To set up the PAD service for outgoing (remote) connections, define the PADprofile in the/etc/x25/x29hosts file.

To set up PAD service for outgoing connections

1. Login to the Communications Server as theroot user

2. Using a text editor, open the/etc/x25/x29hosts and specify theremote X.121 addresses for network connections. The syntax of thepad_em and host_table entries for a single network element arepresented below:

pad_em {name x25card_<no.>

remote_x121 <ne_x.121> logging 0 profile 2 reverse_charge disable}host_table { <ne_name> <ne_x.121>}

For a complete list of optional parameters, seeHewlett Packard’s X.25/9000 User’s Guide.

Note:

Both pad_em andhost_table entries must exist for each networkelement.

<no.> Name of the X.25 card. The name can be found inthe /etc/x25/x25config_<no.> file where<no.> is the number of the X.25 card.

<ne_x.121> X.121 address of the remote network element

<ne_name> Name of the remote network element



NTC TAN 0839/2.2 en54

3. Save the/etc/x25/x29hosts file.

4. Test the remote PAD service from the NMS workstation by entering:

% padem <ne_name>

5. If establishing a PAD connection from the network element to theCommunications Server, seePAD service for incoming connectionsonpage 54. Otherwise go to Section 5.3.2,Setting up DX 200 OSIapplications on page 56.

5.3.1.2 PAD service for incoming connections

Thex29server process provides support for communications with terminalsattached to a remote PAD. To set up the remote PAD service for incomingconnections in the NMS Server, define the PAD profile in the/etc/x25/x29hosts file.

To set up PAD service for incoming connections

1. Login to the Communications Server as theroot user

2. Check if the X.29 server process is active by entering:

# ps -ef|grep x29server

3. If the X.29 server process is running, kill the process by entering:

# kill <pid>

4. Using a text editor, open the/etc/x25/x29hosts and add the pad_sptentry as follows:

# <ne_name>pad_em {

name x25card_<no.> remote_x121 <ne_x.121> logging 0 profile 2 reverse_charge disable}pad_spt { remote_x121 <ne_x.121>}

For a complete list of optional parameters, seeHewlett Packard’s X.25/9000 User’s Guide.

<pid> The process identity number associated with theX.29 server

<ne_name> Name of the remote network element

<ne_x.121> X.121 address of the remote network element



NTC TAN 0839/2.2 en55

5. Save the/etc/x25/x29hosts file.

6. Start the X.29 server by entering:

% x29server

7. Ensure the X.29 server is running by entering:

% ps -ef|grep x29server

8. Go to Section 5.3.2,Setting up DX 200 OSI applications on page 56.



NTC TAN 0839/2.2 en56

5.3.2 Setting up DX 200 OSI applications

To set up DX 200 (remote) OSI applications in the NMS workstation edit the$OMCCONFPATH/osi/ouorapmx.cf configuration file and include theinformation regarding OSI applications and their addresses.

DX 200 applications depend on the local (NMS) applications in the remotenetwork element. A comprehensive list can be found inApplication parameterson page 178.

The following figure illustrates the information required to edit the$OMCCONFPATH/osi/ouorapmx.cf configuration file.

Figure 12.Remote OSI application entries in theouorapmx.cf



NTC TAN 0839/2.2 en57

To set up DX 200 (remote) OSI applications


2. Using a text editor, edit the$OMCCONFPATH/osi/ouorapmx.cf file andinsert the following entries for each remote OSI application:

# <comment>ae_name <app_name>psap 0x<P_sel>.0x<S_sel>.0x<T_sel>.0x<NSAP>apt -aeq 0prot_proc_id <proc_name>transport_class <net_service>apt_ddn <ddn>ae_label 0end_aen <app_name>

Note:

The remote OSI applications are located in Section 3.2.2,DX 200applications in the Communications Server on page 184. Ensure all fourapplications are present in theouorapmx.cf file.

3. If simetaously using CONS/CLNS over X.25, seeConfiguring OSIprotocol identifierson page 58. If using a LAN, go toConfiguringConnection Server softwareon page 59.

<app_name> Name of the OSI application entity name(AEN), seeDX 200 applications in theCommunications Serveron page 184.

<P_sel>,<S_sel>,<T_sel>

P, S and T selectors of the OSIapplication.

<NSAP> NSAP of the remote network element

<proc_name> Name of the OSI application process inthe NMS

<net_service> Type of network service

• 0 = CONS

• 4 = CLNS

<ddn> Value for Directory Distinguished Name/Application Process Title.

• 1 = <app_name> = VFS

• 0.0 = null = Non VFS



NTC TAN 0839/2.2 en58

5.3.3 Configuring OSI protocol identifiers

When simultaneously using CONS/CLNS over X.25, configure the OSI protocolidentifiers as described below.

To configure OSI protocol identifiers

1. Determine which network service (CLNS or CONS) is usingNULLsubaddressing.

2. Using a text editor, open the/etc/opt/ots/conf/ots_subnets fileand change thesnet_bind_by_pid variable as shown below:

snet_bind_by_pid 1

Note:

Ensure you are changing thesnet_bind_by_pid variable in theappropriate network service.

3. Go toConfiguring Connection Server softwareon page 59.

Configuring Connection Server software


NTC TAN 0839/2.2 en59

6 CONFIGURING CONNECTION SERVERSOFTWARE

The NMS Connection Server is used to establish an MML connection from theTop-level User Interface to a DX 200 network element.

Connection Server is a software application distributed across severalworkstations in the Nokia NMS that provides transparent (protocol independent)connections between the NMS and the various network elements.

When a client (application or user) needs a connection to a network element, itsends its request to Connection Server. After receiving the request, ConnectionServer chooses and allocates an appropriate route to the network element. If allroutes are busy and the client is willing to wait, the connection request is addedto a queue maintained by the Connection Server software.

The cnxdcnmx.cf configuration file must include routing informationregarding the network elements that will send data streams to the Nokia NMS.

Note:

Do not confuse Connection Server with the NMS Communications Server.Connection Server is an application for managing DCN connections. The NMSCommunications Server is an actual workstation.



NTC TAN 0839/2.2 en60

The following figure illustrates the procedure for configuring the NMSConnection Server.

Figure 13.Configuring the Connection Server software



NTC TAN 0839/2.2 en61

6.1 Backing up the DCN configuration file

Before configuring the Connection Server, make a backup copy of thecnxdcnmx.cf configuration file.

To backup the configuration file

1. Log into the Communications Server as theomc user.

2. Backup the configuration file by entering:

omc>% cd $OMCCONFPATHomc>% cp cnxdcnmx.cf cnxdcnmx.cf.backup

3. If connection server is running, go to Section 6.4,Editing the ConnectionServer configuration file on page 65. Otherwise, follow the instructionslisted in Section 6.2,Editing the /etc/services file on page 62.



NTC TAN 0839/2.2 en62

6.2 Editing the /etc/services file

The /etc/services file associates official service names and aliases with theport number and protocol in use. When associating new services, follow thenaming scheme below.

<official_service_name> <port_number>/<protocol_name> <aliases>

For example:

c5xstdmx 5555/tcp osi vt/telnet

To edit the /etc/services file

1. Log into the Communications Server as theroot user.

2. Change to theetc directory and open theservices file by entering:

# cd /etc# vi services

3. Edit the /etc/services file by adding an entry for the followingservices in Nokia NMS ports section at the end of the file. An example iswritten below.

# Ports for the Nokia OMC# NOTE! Do not allocate ports for any other connections# from the 79xx range.

c5xftamx 5553/tcp ftamc5xpadmx 5554/tcp x25padc5xstdmx 5555/tcp osi vt/telnetc6xapmmx 5556/tcp apm

4. Exit vi , rebuild and distribute the new service name database by entering:

# /var/yp/ypmake

<official_service_name> The PSM binary name, for example:c5xpadmx

<port_number> Port number of the intermediate system(router or Front End)

<protocol_name> Protocol name =tcp

<aliases> The application name used over theprotocol



NTC TAN 0839/2.2 en63

6.3 Configuring the inetd daemon

The inetd daemon is a TCP/IP superserver that invokes Internet serverprocesses. If theinetd daemon has been added during the commissioning andupgrade procedure, go toEditing the Connection Server configuration fileonpage 65.

Note:

This procedure is intended to be used during the initial commissioning of T10. Ifthe inetd.conf file has been altered after commissioning, ensure all changeshave been copied to the new file.

To configure the inetd daemon

1. Change to theetc directory and backup theinetd.conf configurationfile in both the Communications and Database Servers by entering:

# cd /etc# cp inetd.conf inetd.conf.backup# rcp /etc/inetd.conf <ds_hostname>:/etc/\inetd.conf.backup

2. Open theinetd.conf configuration file by entering:

# vi inetd.conf

<ds_hostname> The hostname of the Database Server



NTC TAN 0839/2.2 en64

3. Edit theinetd.conf configuration file and add the following ConnectionServer settings. When configuring theinetd daemon follow the namingscheme below.

<service> <socket> <protocol> nowait <uid> <path> <conf_file><cf_path>

# connection server settings

## high performance/fast X.25

c5xpadmx stream tcp nowait omc /usr/local/NokiaOMC/\<active>/bin/c5xpafmx c5xpafmx /usr/local/NokiaOMC/conf/global\cnxcffmx.cf

c5xstdmx stream tcp nowait omc /usr/local/NokiaOMC/\<active>/bin/c5xstdmx c5xstdmx /usr/local/NokiaOMC/conf/global\cnxcffmx.cf

c6xapmmx stream tcp nowait omc /usr/local/NokiaOMC/\<active>/bin/c6xapmmx c6xapmmx /usr/local/NokiaOMC/conf/global\cnxcffmx.cf

c5xftamx stream tcp nowait omc /usr/local/NokiaOMC/\<active>/bin/c5xftamx c5xftamx /usr/local/NokiaOMC/conf/global\cnxcffmx.cf

4. Exitvi and copy theinetd.conf file to the Database Server by entering:

# rcp /etc/inetd.conf <ds_hostname>:/etc/inetd.conf

5. Re-read theinetd.conf configuration file by entering:

# /sbin/init.d/inetd stop# /sbin/init.d/inetd start

<service> The PSM binary name, for example:c5xpadmx

<socket_type> Type of socketstream

<protocol> tcp

<uid> User ID used when the system is running

<binary> The absolute path of the PSM binary

<conf_file> The absolute path name of thecnxcffmx.cf configuration file

<cf_path> The absolute path name of thecnxcffmx.cf configuration file

<active> The currentomc_build



NTC TAN 0839/2.2 en65

6.4 Editing the Connection Server configuration file

When editing the Connection Server configuration file, ensure the listening portis set to the appropriate value.

To edit the Connection Server configuration file


2. Change to theglobal directory and open the Connection Serverconfiguration file (cnxcffmx.cf ) by entering:

# cd $OMCCONFPATH# vi cnxcffmx.cf

3. Edit the cnxcffmx.cf configuration file by adding the followingConnection Server environment settings:

(listening port "5560")(csHost "<comm_server_hostname>")

4. Go to Section 6.5,Address device information on page 66.



NTC TAN 0839/2.2 en66

6.5 Address device information

Before editing thecnxdcnmx.cf configuration file, ensure all address deviceinformation is available.

Connections using OSI Transport Services need information about the OSIconfiguration. Theouolapmx.cf and ouorapmx.cf files contain the OSIaddresses required by FTAM, VT and CMIS Servers for local and remote hosts.The following table shows how to obtain address and device information for thevarious protocols used in the Connection Server.

Table 8.Address and device information for the Connection Server

Address or DeviceInformation Needed

How to Get the Information

Device file names Enter:ls /dev/x25*

Local X.121 Address Enter:x25stat -c -d <device file>

Remote X.121 Addresses Not used in the Nokia NMS

Programmatic AccessName

Enter:x25stat -c -d <device file>

Local Host for FTAM,OSI VT or CMIS Servers

See the address information in$OMCCONFPATH/osi/ouolapmx.cf.

Remote Hosts for FTAM,OSI VT or CMIS Servers

See the address information in$OMCCONFPATH/osi/ouorapmx.cf

IP addresses If NIS is configured, enter: ypcat hosts



NTC TAN 0839/2.2 en67

6.6 Naming arcs and routes

When naming arcs and routes in the Connection Server configuration file, followthe naming scheme listed below:

<entry_type>_<start>_<type>_<proto>_<card>_<end>

Example 1.

An arc entry from the Communications Server using OSI VT over a LAN to aBSC named "Turku" would be:

A_CSRV_VT_ISOIP_0_TURKU

Example 2.

An arc entry from the Communications Server using PAD over a X.25 to aBSC named "Turku" would be:

A_CSRV_PAD_X25_0_TURKU

<entry_type> Entry type:

• A for an arc

• R for a route

• AR for an administrative route

<start> Start point of the arc, usuallyCSRV(Communications Server)

<type> Type of service:

• PAD

• TELNET

• VT

<proto> Arc protocol:

• X25 for an analog X.25 connection

• ISOIP for a LAN connection

<card> Number of the network card (analog X.25 or LAN) usedfor the connection

<end> Name of the end system



NTC TAN 0839/2.2 en68

6.7 Adding an arc to a remote system

Arcs are the connections between two nodes. When adding an arc to a remotesystem in the Connection Server configuration follow the instruction listedbelow.

To add an arc to a remote system


2. Edit the$OMCCONFPATH/cnxdcnmx.cf configuration file by adding anentry for the remote system in theArc definitions section of the file.The syntax of an arc entry is as follows:

(arcName "<arc_name>" (maxConns "<max_conns>") (address "<end>") (connChannel "<start>") (loginSeqFileName "<login_file_name>") (logoutSeqFileName "<logout_file_name>"))

The Connection Serverlogin sequence file establishes thelogin ordera users needs to follow in order to make a connection to a network element.The default connections are to the DX 200 (F5) and MSW (F5). Eachlogin sequence file may only contain one login record per file.

Figure 14.Example arc entry in thecnxdcnmx.cf configuration file



NTC TAN 0839/2.2 en69

Table 9.Arc fields definitions in thecnxdcnmx.cf file

<arc_name> Name of the arc using naming schemesuggested inNaming arcs and routesonpage 67.

<max_conns> Maximum number of simultaneous arcconnections to the remote system.

This value is used in load balancing betweentwo parallel areas going to the samedestination

<end> Ending point of the arc (destination address)

• PAD = X.121 address of the NE

• OSI VT = The name of the localapplication in the NE that implements theVT service. The name of the applicationis typically<NE>0<ccccc>VT , forexampleBSC012345VT

• telnet = IP address of the router

<start> Starting point of the arc

• <programmatic card name> = PAD

• ouiswsmx = OSI VT

• telnet = Telnet

<login_file_name> A unique name that defines where the loginsequences are written.

<logout_file_name> A unique name that defines where thelogout sequences are written.

Network element login files names

BSC/DAXWLL/HLR/MSC cnxlogindx2mx.cf

Front End cnxlogindxxmx.cf

MSW mswlogin.cf

Router -

Network element logout files names

BSC/DAXWLL/HLR/MSC cnxlogoutdxmx.cf

Front End cnxlogoutdxxmx.cf

MSW mswlogout.cf

Router -



NTC TAN 0839/2.2 en70

3. If using OSI VT/Telnet comment out all arc names for PAD connectionsas shown below.

###################################################### (1a) ARC Names for PAD Connections######################################################(arcName "A_CSRV_PAD_x25_0_BSC1"# (maxConns "10")# (address "294854090000")# (connChannel "x25card_0")# (loginSeqFileName "cnxlogindx2mx.cf")# (logoutSeqFileName "cnxlogoutdxmx.cf")

4. After all arcs have been added, go to Section 6.8,Adding a route to aremote system on page 70

6.8 Adding a route to a remote system

When adding a route to a remote system in the Connection Server configuration,follow the instructions listed below.

To add a route to a remote system

1. Edit the$OMCCONFPATH/cnxdcnmx.cf configuration file by adding anentry for the remote system in theRoute definitions section of thefile. The syntax of a route entry is as follows:

(routeName "<route_name>" (arcs "<arc_info>") (host "<comm_srvr>") (port "<port>") (checkScript "") (commandLine "<cmdline>"))

Figure 15.Example route entry in thecnxdcnmx.cf configuration file



NTC TAN 0839/2.2 en71

2. If using OSI VT/Telnet, comment out all route definitions for PADconnections as shown below.

###################################################### (2a) Route definitions for PAD Connections######################################################(routeName "<route_name>"# (arcs "<arc_info>")# (host "<comm_srvr>")# (port "5554")# (checkScript "")# (commandLine "<cmdline>")#)

3. After all routes have been added, go to Section 6.9,Adding anadministrative route to a remote system on page 72

<route_name> Name of the route see,Naming arcs and routesonpage 67.

<arc_info> List of arc(s) names used by the route. Delineatoris the ', ' character.

<comm_srvr> Host name of the NMS Communications Server

<port> Port number of the appropriate protocol process

• 5554 = PAD

• 5555 = OSI VT / Telnet

Ensure the port number used is the same as in the/etc/services file.

<checkScript > Not used

<cmdline> Profiles

cnxdx200vtxmx.cf for CLNS connections

cnxdx200padmx.cf for CONS connections

cnxunixtelnmx.cf for Telnet connections



NTC TAN 0839/2.2 en72

6.9 Adding an administrative route to a remote system

Administrative routes are paths through an internetwork that are supervised byadministrative protocol modules (APMs).

Administrative routes are only used with PAD and OSI VT. If using Telnet,comment out all administrative routes that point to the router.

To add an administrative route to a remote system

1. Edit the$OMCCONFPATH/cnxdcnmx.cf configuration file and add anentry for the remote system in theadministrative routedefinitions section of the file. The syntax of a route entry is as follows:

(adminRoute "<adm_name>" (arcs "<arc_info>") (host "<comm_srvr>") (port "5556") (checkScript "<script>") (commandLine ""))

Note:

If you have a CONS connection, add the PSN address as the definition forthecommandLine route entry.

<adm_name> Name of the administrative route

<arc_info> Name of the arc used by the route

<script> Name of the administrative script. The scripts arelocated in the$OMCROOT/lib/scriptdirectory.

• PAD (CONS) =c6xconmx.perl

• OSI VT (CLNS) =c6xvtxmx.perl

• Telnet = not available, comment out AR entry




NTC TAN 0839/2.2 en73

Figure 16. Example administrative route entry in thecnxdcnmx.cf file

2. If using OSI VT comment out all administrative route definitions for allPAD/Telnet connections as shown below.

#######################################################(3) Administrative Route definitions#######################################################(adminRoute "<adm_name>"# (arcs "<arc_info>")# (host "<comm_srvr>")# (port "5556")# (checkScript "<script>")# (commandLine "")#)

<adm_name> Name of the administrative route

<arc_info> Name of the arc used by the route

<script> Name of the administrative script




NTC TAN 0839/2.2 en74

6.10 Adding a node definition to a remote system

Nodes are the endpoints of a network connection or the points common to twoor more lines in a network. Nodes serve as the control points in the network andare generically referred to as any entity that can access a network.

When adding a node definition to a remote system in the Connection Serverconfiguration, follow the instructions listed below:

To add a node definition for the remote system

1. Edit the$OMCCONFPATH/cnxdcnmx.cf configuration file by adding anentry for the remote system in thenode definitions section of the file.The syntax of the node entry is as follows:

(id "<int_ID>" (tecName "<rem_sys>") (maxMMLConns "6") (maxFileConns "6") (maxSpontConns "6") (totalMaxConns "20") (edMMLConns "Y") (edFileConns "Y") (edSpontConns "Y") (edAllConns "Y") (edMMLLog "N") (edFileLog "N") (edSpontLog "N") (edAllLog "Y") (users "" (groups "sysop" (connTypes \

"MML_HUMAN,MML_MACHINE"(routes "<route>")

)(connTypes "SPONT1" (routes "<route>"))

))

)



NTC TAN 0839/2.2 en75

Table 10.Node field definitions in thecnxdcnmx.cf file

<int_ID> Internal ID of the remote system, seeTop-levelUser Interface, TAN 0871.

<rem_sys> Name of the remote system

<maxMMLConns> Maximum number of simultaneous MMLconnections to a network element

<maxFileConns> Maximum number of simultaneous file transfers

<maxSpontConns> Maximum number ofsimultaneous SPONTconnections to a network element

<totalMaxConns> Total number of simultaneous connections(DX element=15)

<edMMLConns> Enable MML connections (Yes or No)

<edFileConns> Enable file transfer connections (Yes or No)

<edSpontConns> Enable spontaneous connections (Yes or No)

<edAllConns> Enable all connections (Yes or No)

<edMMLLog> Enable MML session logs (Yes, No, Verbose)

<edFileLog> Enable file transfer logs (Yes, No, Verbose)

<edSpontLog> Enable spontaneous connections logs(Yes, No, Verbose)

<edAllLog> Enable all logs (Yes, No, Verbose)

<route> Name of the route for the remote system



NTC TAN 0839/2.2 en76

6.10.1 Determining connection subtypes

The connection subtype (connSubType ) identifies the subconnection to anetwork element that is used by the host. Connection subtypes are only used inspontaneous (SPONT) connections.

Table 11. connSubType and its description

Example 3.

If collecting ASCII alarms and measurements from a single network element,SPONT1 could be used for ASCII alarms andSPONT2 could be used forcollecting measurements.

Connection type (connType) Description

SPONT<number> Spontaneous connections

The variable is replaces by an integergreater than 0 that specifies a uniquesubaddress for one spontaneousconnection



NTC TAN 0839/2.2 en77

6.11 Re-reading the configuration file

After making the modifications to the$OMCCONFPATH/cnxdcnmx.cfconfiguration file, re-read the configuration file.

To re-read the configuration file


2. Re-read the configuration file by entering:

omc>% $OMCROOT/lib/script/cnxreconfigmx.perl

This script searches for thec4xcsxmx Connection Server process anddisplays a notice listing the process found and its process identificationnumber (PID ) An example is listed below.

This script also starts thecnxcheckdcnmx.pl script and ensures thesyntax of thecnxdcnmx.cf is correct. If errors are found, re-reading iscancelled. An example is listed below.

Checking Connection Server’sDCN configuration fileFile OK

Process c4xcsxmx was found. Pid is <PID>Reconfiguration with current configuration file (Y/N) ?

3. Entery and press ENTER. The script re-reads the configuration file andthe new settings take effect.

Note:

If the reconfiguration script reports errors, refer to the followinginstructions.

To correct errors in the configuration file


2. Restore the backup configuration file by entering:

omc>% cd $OMCCONFPATHomc>% mv cnxdcnmx.cf cnxdcnmx.cf.newomc>% cp cnxdcnmx.cf.backup cnxdcnmx.cf



NTC TAN 0839/2.2 en78

3. Re-read the backup configuration file by entering:

omc>% $OMCROOT/lib/script/cnxreconfigmx.perl

This script searches for thec4xcsxmx Connection Server process anddisplays a notice listing the process found and its process identificationnumber (PID ) An example is listed below.

This script also starts thecnxcheckdcnmx.pl script and ensures thesyntax of thecnxdcnmx.cf is correct. If errors are found, re-reading iscancelled. An example is listed below.

Checking Connection Server’sDCN configuration fileFile OK

Process c4xcsxmx was found. Pid is <PID>Reconfiguration with current configuration file (Y/N) ?

4. Entery and press ENTER. The script re-reads the configuration file andthe old settings are in effect. This enables the Connection Server tofunction normally while you correct the error in the configuration file.

5. Open thewerlog4006.log file and search for further information aboutthe error by entering:

omc>% more $OMCLOGDIR/werlog4006.log

6. Edit thenew configuration file$OMCCONFPATH/cnxdcnmx.cf.new andcorrect the problem.

7. Copy the new configuration file by entering:

omc>% cd $OMCCONFPATHomc>% cp cnxdcnmx.cf.new cnxdcnmx.cf

8. Re-read the configuration file as described inStep 3.

6.12 Verifying DCN integration

To verify that the integration has been completed successfully, perform theintegration tests described inTesting Installations, TAN 0523.

After successful integration, reboot the system as described inWorkstationNetwork Maintainence, TAN 0513

Configuring the DX 200 network element


NTC TAN 0839/2.2 en79

7 CONFIGURING THE DX 200 NETWORK ELEMENT

Configuring the DX 200 network element (BSC, DAXnode WLL, MSC andHLR) requires the following tasks:

• Setting up the physical connection

This section gives instructions on setting up the physical connection fromthe network element to the NMS Communications Server.

Instructions are provided for analog X.25 (PSN), digital X.25 (PCM) andLAN connections

• Setting up the OSI subnetwork

This section gives instructions on configuring the network service in thenetwork element. Instructions are given for CLNS and CONS.

• Configuring OSI applications and addresses

This section gives instructions on setting up DX 200 and NMS OSIapplications in the network element.

Note:

The instructions for the DAXnodeWLL are only valid for ADW2.



NTC TAN 0839/2.2 en80

7.1 Setting up the physical connection

The following figure outlines the procedure for setting up the physicalconnection in a DX 200 network element:

Figure 17.Setting up the physical connection in a DX 200 network element



NTC TAN 0839/2.2 en81

7.1.1 Using analog X.25 (PSN)

Setting up the physical connection using analog X.25 (PSN) requires followingtasks:

• Installing and configuring an AC25-S card

• Setting the physical layer parameters

• Creating and modifying the X.25 parameter set

• Creating a physical channel

• Assigning a channel group to a physical channel (CONS only)

• Verifying the physical connection

Note:

If using digital X.25 (PCM), seeUsing digital X.25 (PCM)on page 89. If usinga LAN, seeUsing a LANon page 100.



NTC TAN 0839/2.2 en82

Figure 18.MML command groups when using analog X.25

ZQTC:

ZQXC:ZQXM:

ZQCS:

ZQGC:

ZQBN:

ZQDL:ZQDR:

ZQLC:

ZQEC:

ZQBC:

ZQLA:



NTC TAN 0839/2.2 en83

7.1.1.1 Installing and configuring an AC25-S card

To install and configure an AC25-S card, follow the instructions listed below.

To install and configure the AC25-S card

1. Select an empty track in the unit of the network element.

2. Using the following table, determine the PIU-index of the AC25-S card.

3. Ensure the jumper settings for the memory space addresses are unique foreach card per unit. For more information regarding jumper settings, seeAC25-S network cardon page 145.

4. Place the AC25-S card into the appropriate unit in the network element.

5. Depending on your network element, select one of the following choices:

1. With a BSC/DAXnode WLL, accept the default memory spaceaddresses and interrupt levels proposed by the system by entering:

ZWTP:OMU:AC25_S,<PIU_index>,<track>;

Table 12.Indexes, tracks and interrupt levels in the BSC/DAXnode WLL

Note:

The interrupt level does not need to be set in the BSC/DAXnode WLL.

PIU-index in the BSC/DAX Track

2 7

3 8



NTC TAN 0839/2.2 en84

2. With the MSC/HLR, accept the default memory space addressesproposed by the system and set the interrupt level by entering:

ZWTP:BDCU,<index>:AC25_S,<PIU_index>,<track>:INT=<int_level>;

-or-

With a MSC/HLR, set the memory space addresses and interruptlevel by entering:

ZWTP:BDCU,<index>:AC25_S,<PIU_index>,<track>:MS=<ms>,ME=<me>,INT=<int_level>;

Table 13.Indexes, tracks and interrupt levels in the MSC/HLR

<index> The index of the BDCU.

<PIU_index> • Index of the network card. Ensure thesesettings are unique for each card per unit.

• 2-3 in the BSC/DAXnode WLL

• 0-7 in the MSC/HLR

<track> Location of the network card in the subrack.

• In the BSC/DAXnode WLL the track rangestarts from7

• In the MSC/HLR the track range startsfrom 32

<ms> Memory space start address, seepage 147

<me> Memory space end address, seepage 147

<int_level> Interrupt level in hexadecimal

• for the MSC/HLR see the following table

PIU-index in the MSC/HLR Track Interrupt level

0 32 30H

1 37 31H

2 42 32H

3 47 33H

4 52 34H

5 57 35H

6 62 36H

7 67 37H



NTC TAN 0839/2.2 en85

7.1.1.2 Setting the physical layer parameters

To set the physical layer parameters of the AC25-S card, follow the instructionslisted below.

To set the physical layer parameters

Enter the following MML command:

ZQTC:<unit_info>:AC25S,<PIU_index>:<IF_type>,<bit_rate>;


Table 15.Interface types and components

<unit_info> Unit responsible for the connection, together with theindex, if required.

• OMU in the BSC/DAXnode WLL

• BDCU in the MSC/HLR

<PIU_index> Index of the network card. Ensure these settings are uniquefor each card per unit.



<IF_type> Interface type, see the following tables.

<bit_rate> Bit rate of the connection


2 7

3 8

Interface type (IF_type) Connecting components

V.35 from PDE to PDE

V.35 from AC25-S to PDE

X.21 from PDE to PDE

X.21 from AC25-S to PDE

X.21 from PDE to modem

V.24 from PDE to modem



NTC TAN 0839/2.2 en86

7.1.1.3 Creating and modifying the X.25 parameter set

To establish a physical X.25 connection, create and modify the X.25 parameterset. DX 200 network elements include a pre-defined parameter set calledDEFSET. Use this default set as a basis for creating the X.25 parameter set. ForX.25 parameter set values, see Appendix B.,X.25 parameter sets on page 158.

Note:

Do not directly edit theDEFSET parameter set. Create a new parameter set andthen change the values of the parameter set.

To create and modify a parameter set

1. Create a new parameter set by entering:

ZQXC:<param_set>[:<list_of_values>];

Note:

Use the default values for now and modify them later.

2. Modify the values in the parameter set by entering:

ZQXM:<param_set>:<parameter>=<value>[,<parameter>=<value>,<...>];

3. Reset the unit by entering:

ZUSU:<unit>;

<param_set> Name you want to assign to the parameter set

<list_of_values> Comma-delimited list of parameter values youwant to define in the parameter set

<parameter> Parameter name

<value> Value for the parameter

<unit> Unit responsible for the connection, togetherwith the index, if required.





NTC TAN 0839/2.2 en87

7.1.1.4 Creating a physical channel

To create a physical channel, follow the instructions listed below.

To create a physical channel

1. Create a physical channel by entering:

ZQCS:<no>:<unit_info>,<PIU_index>:<SNPA>,1:<mode>,<param_set>;

2. Unlock the physical channel by entering:

ZQSC:<no>,UNL;

3. Proceed according to the table listed below.

<no> Number that you want to assign to the physicalchannel

<unit_info> Unit responsible for the connection, together with theindex, if required



<PIU_index> Index of the network card. Ensure these settings areunique for each card per unit.



<SNPA> SNPA address (physical address) of the local system

<mode> DCE or DTE, see Appendix A.,Network cardjumpers on page 144.

<param_set> Name of the parameter set created inCreating andmodifying the X.25 parameter seton page 86.


Setting up CLNS Verifying the physical connectionon page 99.

Setting up CONS Assigning a channel group to a physicalchannelon page 88.



NTC TAN 0839/2.2 en88

7.1.1.5 Assigning a channel group to a physical channel

To assign the physical channel to a channel group determine the followinginformation:

• Whether you want to add the channel into an existing group or create a newchannel group

Note:

Only perform these tasks when using CONS.

To add a physical channel into an existing channel group


ZQGA:<group>:<channel>,0,<priority>;

To create a new channel group for a physical channel


ZQGC:<group>:<channel>,0,<priority>;

7.1.1.6 Verifying the physical connection

Verify the physical channel was created successfully by entering:

ZQSI;

Ensure the network card is in theWO-EX state and the channel isUNL-ENA. Whendata is transferred through the physical channel, its state will change toUNL-ACT.

Go toSetting up the OSI subnetworkon page 103.

<group> Name of the channel group

<channel> Number of the physical channel

<priority> Priority value you want to assign to the channel



NTC TAN 0839/2.2 en89

7.1.2 Using digital X.25 (PCM)

Setting up the physical connection using digital X.25 (PCM) requires thefollowing tasks:

• Installing and configuring an AS7-U card

• Installing and configuring an Exchange Terminal

• Setting up the semipermanent connections

• Creating and modifying the X.25 parameter set

• Creating a physical channel

• Assigning a channel group to a physical channel (CONS only)

• Verifying the physical connection

7.1.2.1 Installing and configuring an AS7-U card

To install and configure an AS7-U network card in a network element, follow theinstructions listed below.

To install and configure an AS7-U card


2. Using the following tables, determine the PIU-index of the AS7-U card.

3. Ensure the jumper settings for the memory space addresses are unique foreach card per unit. For more information regarding jumper settings, seeAS7-U network cardon page 150.

4. Place the AS7-U card into the appropriate unit in the network element.


1. With a BSC/DAXnode WLL, accept the default memory spaceaddresses proposed by the system by entering:

ZWTP:OMU:AS7_U,<PIU_index>,<track>::X25,4,<PCM_number>,TSL,<TSL>;


PIU-index in the BSC/DAX Track Interrupt level

2 7 default

3 8 default



NTC TAN 0839/2.2 en90

2. With the MSC/HLR, accept the default memory space addressesproposed by the system and set the interrupt level by entering:

ZWTP:BDCU,[<index>]:AS7_U,<PIU_index>,<track>:INT=<int_level>:X25,2,<PCM_number>,TSL,<TSL>;

Table 17.Indexes, tracks and interrupt levels in the MSC/HLR

<index> Index of the unit

<PIU_index> Index of the network card. Ensure thesesettings are unique for each card per unit.







• for the MSC/HLR see the following table

<PCM_number> Number of the PCM used for this connection.See the site-specific documentation for details.



<TSL> Next free time slot

PIU-index in the MSC/HLR Track Interrupt level

0 32 30H

1 37 31H

2 42 32H

3 47 33H

4 52 34H

5 57 35H

6 62 36H

7 67 37H



NTC TAN 0839/2.2 en91

-or-

With a MSC/HLR, set the memory space addresses and interruptlevel by entering:

ZWTP:BDCU,<index>:AS7_U,<PIU_index>,<track>:MS=<ms>,ME=<me>,INT=<int_level>:X25,2,<PCM_number>,TSL,<TSL>;

6. Create a PCM connection for the functional unit by entering:

ZWUC:<unit_info>:AS7_U,<PIU_index>;





<track> Location of the network card in thesubrack.

• In the BSC/DAXnode WLL the trackrange starts from7





• for the MSC/HLR see the followingtable

<PCM_number> Number of the PCM used for thisconnection. See the site-specificdocumentation for details.


<unit_info> Unit responsible for the connection,together with the index, if required





NTC TAN 0839/2.2 en92

7.1.2.2 Installing and configuring an Exchange Terminal

To install and configure an Exchange Terminal, follow the instructions listedbelow.

To configure an Exchange Terminal

1. Determine if there is an ET available for connection. The followingcommands interrogate the current hardware configuration:

• List the existing ET units and their plug-in units by entering:

ZWTI:P:ET;

• Display the existing ET units and their operating states by entering:

ZUSI:ET;

2. If the ET does not exist, ensure the ET is physically installed and availablefor the connection.

3. Create the ET in the hardware description files by entering:

ZWTU:ET,<index>:<coordinates>;



NTC TAN 0839/2.2 en93

4. Depending on your network element, create an ET by entering:

1. With a BSC/DAXnode WLL:

ZWTP:ET,<index>:<PIU_type>,<PIU_index>,<track>::ETT00,4,<PCM>,TSL,<TSL>;

2. With an MSC/HLR:

ZWTP:ET,<index>:ET1E,<PIU_index>,<track>::ETT00,2,<PCM>,TSL,<TSL>;

Note:

It is possible to create several ET units with the same coordinates, and usedifferent track numbers for plug-in units that belong to different ETfunctional units.

<index> Index number of the ET unit

<coordinates> Location of the ET unit

<PIU_index> Index of the following exchangeterminals. Ensure these settings are uniquefor each card per unit.

• ET1E

• ET2E

<PIU_type> • ET1E

• ET2E

<track> Location of the network card in thesubrack.

• In the BSC/DAXnode WLL the trackrange starts from0


<PCM> PCM number, usually the same as theindex of the ET




NTC TAN 0839/2.2 en94

5. Depending on your network element, create a PCM connection byentering:

• In a BSC:

ZWUC:ET:<index>:<PIU_type>,0:IF=<interface>:BCSU,<BCSU_index>;

• In a DAXnode WLL

ZWUC:ET:<index>:ET2E,0:UPART=MSW;

• In an MSC:

ZWUC:ET,<index>:ET1E,<PIU_index>::CCSU,<CCSU_index>;

• In an HLR:

ZWUC:ET,<index>:ET1E,<PIU_index>::CCSU,<CCSU_index>;

6. Change the ET to working state (WO-EX) by entering the followingcommands:

ZUSC:ET,<index>:SE;ZUSC:ET,<index>:TE;ZUSC:ET,<index>:WO;

You can check that the unit is in theWO-EX state by entering:

ZUSI:ET;

<index> Index number of the ET unit

<PIU_index> Index of the following exchangeterminals. Ensure these settings are uniquefor each card per unit.

• ET1E

• ET2E

<PIU_type> • ET1E

• ET2E

<interface> Interface type

• A = interface to MSC

• ABIS = interface to BTS

• DSS1 = ISDN interface to BTS

<BCSU_index> Index of the BCSU

<CCSU_index> Index of the CCSU



NTC TAN 0839/2.2 en95

7.1.2.3 Setting up the semipermanent connections

The communication through the MSC/HLR is facilitated by setting up asemipermanent connection between the time slots in the PCM line to the BSC/DAXnode WLL and routing devices. These external PCM lines aresemipermanently connected to the group switch of the MSC/HLR.

The semipermanent connection is established using a transcoder or a transcoder/submultiplexer (TCSM).

To reserve one of the time slots in the PCM line between the MSC/HLR and theBSC/DAXnode WLL follow the instructions listed below.

Note:

Before beginning the process, ensure the MSC/HLR is connected to the NMSFront End or a third party router using PCM over digital X.25.

To set up the semipermanent connection in the MSC/HLR

1. Ensure theTSEM0 circuit group exists by entering:

ZRCI:GSW;

2. If theTSEM0 circuit group is not displayed, create it by entering:

ZRCG:GSW:TYPE=S,CGR=158,NCGR=TSEM0,CRCT=<PCM>-<TSL>;

3. Add the time slots used by entering:

ZRCA:GSW:NCGR=TSEM0,CRCT=<PCM>-<TSL>;

4. Create a semipermanent connection from the time slot of the external PCMin routing device to the time slot of the external PCM in the BSC/DAXnode WLL by entering:

ZRSC:CRCT=<PCM>-<TSL>:CRCT=<PCM>-<TSL>;

<PCM> Number of the external PCM from the MSC/HLR to theIS

<TSL> Timeslot number of the external PCM from the MSC/HLR to the IS

<PCM> External PCM number used for the connection

<TSL> Time slot number of the external PCM used for theconnection



NTC TAN 0839/2.2 en96

5. Set up a semipermanent connection in the transcoder if it has not beencreated already. When creating a connection in the transcoder, consider thefollowing:

• If using a transcoder between the MSC and the BSC/DAXnodeWLL, ensure the actual connection is in the transcoder unit. Use thefollowing time slots:1, 16, 30 or 31.

• If a TCSM is used, create the connection according to the valueslisted below:

Table 18.Using a TCSM for semipermanent connections

To set up semipermanent connection in the transcoder

To set up the semipermanent connection in the transcoder, follow theinstructions listed below.

1. Connect the transcoder service terminal to the transcoder and switch theterminal on.

2. PressF2.

3. Select 7,Direct connection.

4. Select 1,Equipment operation.

5. Select 6,settings (permanent).

6. Select 9,unit settings.

7. Select 2,DX2M .

8. Select 4,through connection.

9. Select 2,connect.

10. Enter the time slot number.

Transcoder Outgoing TSL

First 28 (AUX1)

Second 29 (AUX2)

Third 30 (AUX3)



NTC TAN 0839/2.2 en97

7.1.2.4 Creating and modifying the X.25 parameter set

To establish the physical X.25 connection, define the X.25 parameter set. TheDX 200 based network elements include a pre-defined parameter set titledDEFSET, which you can use as a basis for the X.25 parameter set.

The correct values for the DCN X.25 parameter set are located in Appendix B.,X.25 parameter sets on page 158.

Note:

Do not edit theDEFSET parameter set directly. Instead, create a new parameterset and then make modifications.

To create and modify a parameter set

1. To create a new parameter set, enter the following MML command:

ZQXC:<param_set>[:<list_of_values>];

Note that you can use the default values for now and modify them later.

2. To modify the values in a parameter set, enter the following MMLcommand:

ZQXM:<param_set>:<parameter>=<value>[,<parameter>=<value>,<...>];

3. Finally, reset the unit by entering:

ZUSU:<unit_info>;

<param_set> Name you want to assign to the parameter set

<list_of_values> Comma-delimited list of parameter values youwant to define in the parameter set

<param_set> Name of the parameter set

<parameter> Parameter name

<value> Value for the parameter

<unit_info> Unit responsible for the connection, togetherwith the index, if required





NTC TAN 0839/2.2 en98

7.1.2.5 Creating a physical channel

When creating a physical channel, follow the instructions listed below.

To create a physical channel

1. Enter the following MML command:

ZQCC:<no.>:<unit_info>,<PIU_index>:<SNPA>:<mode>,<param_set>:<PCM>-<TSL>;

2. Unlock the physical channel:

ZQSC:<no.>,UNL;

Now proceed to the following table:

<no.> Number of the physical channel

<unit_info> Unit responsible for the connection, together withthe index, if required.



<PIU_index> Index of the network card. Ensure these settingsare unique for each card per unit.



<SNPA> SNPA address (physical address) of the localsystem

<mode> The local end of the connection

• DCE

• DTE

See Appendix A.,Network card jumpers on page144

<param_set> Name of the parameter set created inCreating andmodifying the X.25 parameter seton page 97

<PCM> Number of the external PCM

<TSL> Time slot within the PCM (any value 1 - 31)


Setting up a CLNS network serviceVerifying the physical connectiononpage 99.

Setting up a CONS networkservice

Assigning a channel group to a physicalchannelon page 99.



NTC TAN 0839/2.2 en99

7.1.2.6 Assigning a channel group to a physical channel

Channel groups are assigned to physical channels when using remote NSAPaddresses. To assign the physical channel to a channel group, determine thefollowing information:

• Whether you want to add the channel into an existing group or create a newchannel group

Note:

Only perform these tasks when using X.25.

To add a physical channel into an existing channel group


ZQGA:<group>:<channel>,0,<priority>;

To create a new channel group for a physical channel


ZQGC:<group>:<channel>,0,<priority>;

7.1.2.7 Verifying the physical connection

Verify the physical channel was created successfully by entering:

ZQSI;

Ensure the network card is in theWO-EX state and the channel isUNL-ENA. Whendata is transferred through the physical channel, its state will change toUNL-ACT.

Go toSetting up the OSI subnetworkon page 103.

<group> Name of the channel group

<channel> Number of the physical channel

<priority> Priority value you want to assign to the channel



NTC TAN 0839/2.2 en100

7.1.3 Using a LAN

Setting up the physical connection using a LAN requires the following tasks:

• Installing and configuring a COCEN card

Typically, it is not necessary to set the physical layer parameters manually, as theLink Level Control (LLC1) software can detect the interface type if an Ethernetcable is attached to the COCEN card.

7.1.3.1 Installing and configuring a COCEN card

To install and configure an COCEN network card in a DX 200 based networkelement, follow the instructions listed below:

To install and configure a COCEN card


2. Using the following tables, determine the PIU-index of the COCEN card.

3. Ensure the jumper settings for the memory space addresses are unique foreach card per unit. For more information regarding jumper settings, seeCOCEN network cardon page 154.

4. Place the COCEN card into the appropriate unit in the network element.


1. With a BSC/DAXnode WLL, accept the default memory spaceaddress proposed by the system by entering:

ZWTP:OMU:COCEN,<PIU_index>,<track>:SW=LLC1;



2 7

3 8



NTC TAN 0839/2.2 en101

2. With an MSC/HLR, set the interrupt level and software packagename for each card by entering:

ZWTP:BDCU,<index>:COCEN,<PIU_index>,<track>:INT=<int_level>;

The following output appears:

COMMAND EXECUTED

3. With a Front End, set the interrupt level and software package namefor each card by entering:

ZWTP:BDCU,<index>:COCEN,<PIU_index>,<track>:INT=<int_level>,SW=LLC1;

Table 20.Indexes, tracks and interrupt levels in the MSC/HLR/FE

<index> The index number of the OMU/BDCU

<PIU_index> Index of the COCEN card. Ensure thesesettings are unique for each card per unit.


• 0-7 in the MSC/HLR/Front End



• In the MSC/HLR/Front End the track rangestarts from32


• default in the BSC/DAXnode WLL

• for the MSC/HLR/Front End see thefollowing table

PIU-index in the MSC/HLR/FE Track Interrupt level

0 32 30H

1 37 31H

2 42 32H

3 47 33H

4 52 34H

5 57 35H

6 62 36H

7 67 37H



NTC TAN 0839/2.2 en102

6. Reset the unit by entering:

ZUSU:<<unit_info>;

The following output appears:

LOADING PROGRAM VERSION <version_no>

EXECUTION STARTED

RESTART REQUEST IN UNIT <unit_info>

CONFIRM COMMAND EXECUTION Y/N

7. Accept the action by enteringy after the prompt:

MESSAGE RESTART ORDEREDUNIT <unit_info>

8. Ensure the COCEN card has been properly installed and configured byentering:

ZWTI:P:<unit_info>,<index>:COCEN,<PIU_index>;

9. Go toSetting up the OSI subnetworkon page 103.

<unit_info> Unit responsible for the connection, togetherwith the index, if required.


• BDCU in the MSC/HLR/Front End



NTC TAN 0839/2.2 en103

7.2 Setting up the OSI subnetwork

The following figure illustrates the procedure of setting up the OSI subnetworkin a DX 200 network element. If using CONS, seeCreating NSAPs and networkprotocol addresseson page 108.

Figure 19.Setting up the OSI subnetwork in a DX 200 network element



NTC TAN 0839/2.2 en104

7.2.1 Using CLNS

Setting up the CLNS consists of the following tasks:

• Setting up a CLNS object

• Setting up a linkage object

• Adding manual adjacencies (X.25 only)

• Creating NSAPs and network protocol addresses

7.2.1.1 Setting up a CLNS object

When creating a CLNS object in a network element, follow the instrucions listedbelow.

To set up a CLNS object

1. Create a CLNS object by entering the following MML command:

ZQEC:<CLNS_name>:ES:<unit_info>:<PDU>:<sys_ID>:<max_addr>:<area_addr>;

<CLNS_name> Any unique name that defines the CLNS network.For example:CLNS_LAN.




<PDU> PDU

This value is expressed in 0.5 seconds. Calculated bymultiplying the number of systems times 3.

Example:

NMS - ES configuration (2 systems) 2 * 3 = 6

<sys_ID> System Identifier

This is a unique identifier for the local system.

For example:The C number of the network padded with sevenzeros (0000000<ccccc>)

<max_addr> Maximum manual area address count. Defines thenumber of subnetworks in the DCN.The recommended value is3.

<area_addr> Area address part of the NSAP address, seeDCNManagement, TAN 0377.



NTC TAN 0839/2.2 en105

2. Unlock the CLNS object by entering:

ZQEG:<CLNS_name>:UNL;

3. Initialise the CLNS object by entering:

ZQET:<CLNS_name>;

7.2.1.2 Setting up a linkage object

To set up a linkage object in a network element follow the instructions listedbelow.

To set up a linkage object

1. Choose one of the following steps depending on the physical connection:

• If using CLNS/X.25, create an X.25 linkage object for each X.25card by entering:

ZQLC:[<link_ID>]:ES:<unit_info>:<PIU_index>:SNPA=<SNPA>;

• If using LAN, create a broadcast linkage object by entering:

ZQLL:[<link_ID>]:ES:<unit_info>:<PIU_index>;

<link_ID> ID number of the linkage. (Optional)If not previously defined, the system willassign a free number 0-60.

<unit_info> Unit responsible for the connection, togetherwith the index, if required.






<SNPA> SNPA address (physical address) of thesystem reached via this linkage.

X.25 connections only

Same as the physical address (X.121) of theremote or intermediate system.

<CLNS_name> Any unique name that defines the CLNSnetwork. For example:CLNS_LAN.



NTC TAN 0839/2.2 en106

2. Unlock the linkage object by entering:

ZQLG:<link_ID>::UNL;

Warning:

Re-initialising the CLNS object causes all existing connections from thenetwork element to temporarily disconnect. Ensure that no critical datatransfer operations or terminal sessions are in progress when the object isinitialised.

3. Re-initialise the CLNS object by entering:

ZQET:<CLNS_name>;

4. If setting up a linkage object for a LAN, go toCreating NSAPs andnetwork protocol addresseson page 108. If setting up a linkage object forX.25, seeAdding manual adjacencies.



NTC TAN 0839/2.2 en107

7.2.1.3 Adding manual adjacencies

Manual adjacencies are only used with direct X.25 connections:

• from a BSC/DAXnode to the NMS

• from an MSC/HLR to the NMS

• from a Front End to the NMS

To add a manual adjacency from one of the linkage object listed above, completethe following instructions:

To add a manual adjacency

1. Add a manual adjacency between a network element and theCommunication Server by entering:

ZQLA:<link_ID>:<endsys_1>[,<endsys_2>];

2. Add a manual adjacency between a network element and the StandbyServer by entering:

ZQLA:<link_ID>:<endsys_1>[,<endsys_3>];

Note:

If using acomm package NSAP address, add the system identifier of theCommunication Server andcomm package in the<endsys> fields. Formore information regarding system identifiers, seeDCN Management,TAN 0377.

<link_ID> ID number of the linkage. (Optional)The system will assign a free number 0-60.

<endsys_1> NSAP of thecomm package in the NE

<endsys_2> NSAP of the Communications Server

<endsys_3> NSAP of the Standby Server



NTC TAN 0839/2.2 en108

7.2.1.4 Creating NSAPs and network protocol addresses

NSAPs and network protocol addresses are used to associate services in networkelements. Before establishing a connection from the NMS→ NE, the NSAPsand network protocol addresses must be created in all network elements.

To create NSAPs and network protocol addresses for CLNS connections, followthe instructions listed below. If usingcomm package NSAP addresses, thefollowing remote NSAPs must be configured in the DX 200 network element.

• comm package NSAP addresses

• NSAP of the Communications Server

• NSAP of the Standby Server

To create NSAPs and network protocol addresses (CLNS)

1. Define the default area address parameters if undefined by entering:

ZQBH:AFI=<AFI>,IDI=<IDI>,DFI=00,ORG=<org>,RES=00000001,AREA=<area>;

Note:

In the DX 200 dialogue, the reserved (RES) and routing domain valueshave been combined into one field. For more information on how theseparameters should be defined, seeDCN Management, TAN 0377.

2. Create thelocal NSAP for each service by entering:

ZQBN:[<NSAP>]:L:4:NSEL=00;

<AFI> Authority Format Identifier

The value39 indicates a DCC NSAP.

<IDI> Initial Domain Identifier. The country code ofthe customer, seeDCN Management, TAN 0377.

<org> Organisation identifier. Must be acquired fromthe national authorities.

<area> Routing area.

If there is only one routing area, use0001

<NSAP> Number assigned to the NSAP. If you do notspecify a number, the system will automaticallyassign the next available number.



NTC TAN 0839/2.2 en109

3. Create theremote NSAP for thecomm package NSAP addresses byentering:

ZQBN:[<NSAP>]:R:5:END=<endsys_1>,NSEL=00;

4. If creating the physical NSAP addresses for the Communications andStandby Servers, enter the following commands:

ZQBN:[<NSAP>]:R:5:END=<endsys_2>,NSEL=00;ZQBN:[<NSAP>]:R:5:END=<endsys_3>,NSEL=00;

5. Create thelocal network address namedLOCAL by entering:

ZQBC:LOCAL:L;

6. Create theremote network address titledREMNMS by entering:

ZQBC:REMNMS:R;


<endsys_1> comm package NSAP

<endsys_2> Communications Server NSAP

<endsys_3> Standby Server NSAP



NTC TAN 0839/2.2 en110

7. Interrogate the network protocol address information by entering:

ZQBI;



DX 200 TOM 1998-10-02 10:00:00

INTERROGATING NETWORK ADDRESS DATA

NET ADDR ROLE NSAP NR PRIO NSAP NR PRIO NSAP NR PRIO

--------- ---- ------- ---- ------- --- ------ -----

LOCAL LOCAL 7 -REMNMS REMOTE 8 50 9 50 10 50...

COMMAND EXECUTED

NETWORK ADDRESS AND NSAP DATA HANDLING COMMAND <QB_>

Note:

The interrogation output listed above only serves as an example. Do notcopy all values displayed to your configuration.

When creating network protocol addresses for the first time their state isLOC-DIS until they are attached to a network protocol address.

8. Ensure the following:

• NET ADDR for local CLNS applications is set toLOCAL

• NET ADDR for remote CLNS applications is set toREMNMS

• NSAP NR for local and remote CLNS applications is attached to thecorrectNET ADDR

9. Go to Section 7.2.1.5,Attaching NSAPs to network protocol addresses onpage 111.



NTC TAN 0839/2.2 en111

7.2.1.5 Attaching NSAPs to network protocol addresses

After the NSAPs and network protocol addresses have been created inCreatingNSAPs and network protocol addresseson page 108, attach the CLNS NSAPs tothe network protocol addresses.

To attach NSAPs (CLNS) to network protocol addresses

1. Attach the local network protocol address,LOCAL, to the NSAP created inStep 2. on page 108 by entering:

ZQBT:LOCAL:<NSAP>;

2. Attach the remote network protocol addressREMNMS, to the NSAP createdin Step 3. on page 109 by entering:

ZQBT:REMNMS:<NSAP>,<priority>;

Note:

Thecomm package NSAP must be set with the highest priority.

3. Unlock both local and remote NSAPs by entering one of the followingcommands:

• To unlock one NSAP or several non-subsequent NSAPs by entering:

ZQBG:<NSAP_1>[&<NSAP_2>],UNL;

• Unlock a sequence of NSAPs by entering:

ZQBG:<NSAP_1>&&<NSAP_2>,UNL;

4. Go to Section 7.3,Configuring OSI applications and addresses on page118.

<NSAP> Number assigned to the NSAP

<priority> Any value from 1 -100. The default value is 50.The higher the number, the higher the priority.

<NSAP_1><NSAP_2>

The firstand the last NSAP number in the range



NTC TAN 0839/2.2 en112

7.2.2 Using CONS

Setting up the CONS includes creating NSAPs and network protocol addresses.

NSAPs, SPIs and network protocol addresses are used to associate services in anetwork element. The number of NSAPs and network addresses created dependson the networking protocol and the services you intend to set up.

Also, before establishing an MML connection NMS→ NE using CONS, thelocal and applications must be specified in the network element.

Note:

PAD service may not be necessary as remote terminal sessions to the networkelements can be established using OSI VT.

Details on the address parameters can be found inOSI Parameterson page 175.



NTC TAN 0839/2.2 en113

7.2.2.1 Creating NSAPs and network protocol addresses

NSAPs, SPIs and network protocol addresses are used to associate services innetwork elements. Before establishing a connection from the NMS→ NE, thelocal applications must be created in all network elements.

If you are using several remote systems (NMS, NE, RTR) for PAD and MSWconnections, create a unique network protocol address name for each destination.

When creating NSAPs and network protocol addresses, repeat each step threetimes for each CONS service (CMISE/FTAM, PAD and MSW).

To create NSAPs and network protocol addresses (CONS)

1. Create thelocal NSAP for each service by entering:

ZQBN:[<NSAP>]:L:1:DTE=<ne_x.121>,SPI=<SPI>;

2. Create theremote NSAP for each service by entering:

ZQBN:[<NSAP>]:R:1:DTE=<cs_x.121>,SPI=<SPI>,CHG=<grp>;

3. Create thelocal network address for each service by entering:

ZQBC:<l_net_addr>:L;


<ne_x.121> X.121 address of the local network element

<SPI> Subsequent protocol identifier

• 03010100 for CMISE/FTAM

• 01000000 for PAD

• C0000000 for MSW

<cs_x.121> X.121 address of the NMS Communications Server

<grp> Channel group, seeSPIs for CONScommunicationson page 175.

• OMCCMISE for CMISE/FTAM

• OMCPAD for PAD

• OMCMSW for MSW

<l_net_addr> Local network protocol address name, seeCONSnetwork protocol address nameson page 177.

• LOCALCMI for CMISE/FTAM

• LOCALPAD1 for PAD

• LOCALMSW1 for MSW



NTC TAN 0839/2.2 en114

4. Create theremote network address for each service by entering:

ZQBC:<r_net_addr>:R;

5. Interrogate the network protocol address information by entering:

ZQBL:TYPE=1;



DX 200 TOM 1998-10-02 10:00:00

INTERROGATED NSAP DATA

X.25 NETWORK PROTOCOL ADDRESS INFORMATION

NBR ROLE STATE CHG DTE SPI---- ---- ------- ---- ------------- -------1 LOCAL LOC-DIS - 123456789012 030101002 LOCAL LOC-DIS - 123456789012 010000003 LOCAL LOC-DIS - 123456789012 C0000000

X.25 NETWORK PROTOCOL ADDRESS INFORMATION

NBR ROLE STATE CHG DTE SPI---- ---- ------- ---- ------------- -------4 REMOTE LOC-DIS OMCCMISE 111222199188 030101005 REMOTE LOC-DIS OMCPAD 111222199188 010000006 REMOTE LOC-DIS OMCMSW 111222199188 C0000000

COMMAND EXECUTED


Note:


When creating network protocol addresses for the first time their state isLOC-DIS until they are attached to a network protocol address.

<r_net_addr> Remote network protocol address name, seeCONSnetwork protocol address nameson page 177.

• REMCMI for CMISE/FTAM

• REMPAD1 for PAD

• REMMSW1 for MSW

When creating remote network protocol addressnames forPAD andMSW applications, ensure eachnetwork protocol address name is different.



NTC TAN 0839/2.2 en115


• SPIs for CMISE and FTAM applications are set to03010100

• SPIs for PAD applications are set to01000000

• SPIs for MSW applications are set toC0000000

7. Go to Section 7.2.2.2,Attaching NSAPs to network protocol addresses onpage 116.



NTC TAN 0839/2.2 en116

7.2.2.2 Attaching NSAPs to network protocol addresses

After the NSAPs and network protocol addresses have been created inCreatingNSAPs and network protocol addresseson page 113, attach the CONS NSAPs tothe network protocol addresses. When attaching NSAPs to network protocoladdresses, repeat each step three times for each CONS service (CMISE/FTAM,PAD and MSW).

To attach NSAPs (CONS) to network protocol addresses

1. Attach thelocal network protocol addresses to the correspondinglocalNSAPs by entering:

ZQBT:<l_net_addr>:<NSAP>;

2. Attach theremote network protocol addresses to the correspondingremoteNSAPs by entering:

ZQBT:<r_net_addr>:<NSAP>;

3. Unlock both local and remote NSAPs by entering one of the followingcommands:

• To unlock one NSAP or several non-subsequent NSAPs enter:

ZQBG:<NSAP_1>[&<NSAP_2>],UNL;

• To unlock a range of NSAPs enter:

ZQBG:<NSAP_1>&&<NSAP_2>,UNL;

<l-net_addr> Local network protocol address name see,CONSnetwork protocol address nameson page 177.

<r_net_addr> Remote network protocol address name, seeCONSnetwork protocol address nameson page 177.

• REMCMI for CMISE/FTAM

• REMPAD1 for PAD

• REMMSW1 for MSW

When creating remote network protocol addressnames forPAD andMSW applications, ensure eachnetwork protocol address name is different.

<NSAP> Number assigned to the NSAP

<NSAP_1><NSAP_2>

The firstand the last NSAP number in the range



NTC TAN 0839/2.2 en117

4. Interrogate the network address data by entering:

ZQBI;



DX 200 TOM 1998-10-02 10:00:00

INTERROGATING NETWORK ADDRESS DATA

NET ADDR ROLE NSAP NR PRIO NSAP NR PRIO NSAP NR PRIO

-------- ------ ------- ---- ------- ---- ------- ----

LOCALCMI LOCAL 1 -LOCALPAD1 LOCAL 2 -LOCALMSW1 LOCAL 3 -

REMCMI REMOTE 4 50REMPAD1 REMOTE 5 50REMMSW1 REMOTE 6 50

COMMAND EXECUTED



• The network protocol address names(NET ADDR) are specified asin CONS network protocol address nameson page 177.

• The local network addresses are in theLOCAL role

• The remote network addresses are in theREMOTE role

• The NSAP number (NSAP NBR) matches theNBR field displayed inStep 5. on page 114.

Note:


6. Go to Section 7.3,Configuring OSI applications and addresses on page118.



NTC TAN 0839/2.2 en118

7.3 Configuring OSI applications and addresses

The following figure illustrates the tasks for configuring the OSI applicationsand addresses in the DX 200 network element.

Figure 20.OSI application configuration process flowchart



NTC TAN 0839/2.2 en119

7.3.1 Setting up local PAD and MSW applications

Local PAD and MSW applications are used between a network element and anintermediate system. The type of application used depends on the intermediatesystem.

• If using X.25 with a router, set up the local PAD applications.

• If using X.25 with a Front End, set up the local PAD and MSWapplications.

• If establishing NE - NE connections, set up the local PAD and MSWapplications.

• If you are using a LAN, go toSetting up local OSI applicationson page122.

To set up these applications in a DX 200 network element, follow theinstructions listed below:

To set up the local PAD and MSW applications

1. Set up the local PAD applications by entering:

ZQDL:<aen>:::UNL:<unit_info>:<type>:<NW_addr>;



DX 200 TOM 1998-10-02 10:00:00

LOCAL OSI APPLICATION DATA

AE-NAME APP NET ADDR STATE UNIT FAM ID PROC ID---------- ----- --------- ------- ---- ------ -------BSC012345PAD PAD LOCALPAD UNL-ENA OMU

AP_TYPE : NOT IN USEAP_TITLE :AEQ :

P-SELECTOR:S-SELECTOR:T-SELECTOR:

COMMAND EXECUTED

OSI ENVIRONMENT APPLICATION DATA HANDLING COMMANDS <QD_>



NTC TAN 0839/2.2 en120

2. If using X.25 with a Front End, set up the local MSW applications byentering:

ZQDL:<aen>:::UNL:<unit_info>:<type>:<NW_addr>;

Figure 21.Creating local PAD applications in a BSC

<aen> Name of the application entity name, seeDX 200applicationson page 178.




<type> Application type, seepage 178.

<NW_addr> Local network address name used by the application,seeCONS network protocol address nameson page177.



NTC TAN 0839/2.2 en121

3. Interrogate the local application data by entering:

ZQDI:APL=LCL;



DX 200 TOM 1998-10-02 10:00:00


AE-NAME APPL NET ADDR STATE UNIT FAM ID PROC ID

------------ ---- -------- --------- ---- ----- --BSC012345PAD PAD LOCALPAD1 UNL-ENA OMUBSC012345MSW MSW LOCALMSW1 UNL-ENA OMU

COMMAND EXECUTED



• Network protocol address names(NET ADDR) are specified as inCONS network protocol address nameson page 177.

• all states are set toUNL-ENA

5. Go toSetting up local OSI applicationson page 122.



NTC TAN 0839/2.2 en122

7.3.2 Setting up local OSI applications

Local applications are used between intermediate and end systems using a LAN.Set up the following local applications when:

• using a LAN with a router.

• using a LAN with a Front End.

To set up these applications in a DX 200 network element, follow theinstructions listed below.

To set up the local OSI applications

1. Set up the local applications in the DX 200 by entering:

ZQDL:<aen>:::UNL:<unit_info>:<type>,<fam>,<process_ID>:LOCAL:<P_sel>:<S_sel>:<T_sel>;



DX 200 TOM 1998-10-02 10:00:00

CREATED OSI APPLICATION

AE-NAME APPL NET ADDR STATE UNIT FAM ID PROC ID------------- ----- -------- -------- ---- ------ -------

BSC012345A CMISE LOCAL UNL-ENA OMU 021F 0000H


P-SELECTOR: 3333030230S-SELECTOR: 3333030230T-SELECTOR: 3333

COMMAND EXECUTED




NTC TAN 0839/2.2 en123

Note:

Repeat this step for the local CLNS applications (items 1-4) in the DX 200OSI applications table beginning on page 178.

Figure 22.Creating local CLNS applications in a BSC

<aen> Name of the OSI application entity name, seeDX200 applicationson page 178.




<type> Application type, seepage 178

<fam> Process family ID. This parameter is only requiredfor CMI applications.

<process_ID> Master process ID. Use the value0

<P_sel> P selector value, seeDX 200 applicationson page178.

<S_sel> S selector value

<T_sel> T selector value



NTC TAN 0839/2.2 en124

2. Interrogate the local OSI application data by entering:

ZQDI:APL=LCL;



DX 200 TOM 1998-10-02 10:00:00


AE-NAME APPL NET ADDR STATE UNIT FAM ID PROC ID

------------ ----- -------- --------- ---- ----- -------BSC012345F VFS LOCAL UNL-ENA OMUBSC012345VT VTP LOCAL UNL-ENA OMUBSC012345A CMI LOCAL UNL-ENA OMU 021F 0000HBSC012345EHA CMI LOCAL UNL-ENA OMU 02B1 0000H

COMMAND EXECUTED



• Network protocol address names(NET ADDR) are specified as inCLNS network protocol address nameson page 176.


4. Go to Section 7.3.3,Defining the CMISE service profile on page 125.



NTC TAN 0839/2.2 en125

7.3.3 Defining the CMISE service profile

After creating all local applications in the DX 200 network element, define theCMISE service profile (<NE>0<ccccc>A ) for all CMISE applications. Thisapplication provides the OSI CMISE service.

To define the service profile for CMISE

1. Ensure the CMISE applicationA is set toLOC-ENA by entering:

ZQDI:AEN=<aen>:MAX;



DX 200 TOM 1998-10-02 10:00:00


AE-NAME APPL NET ADDR STATE UNIT FAM ID PROC ID------- ----- -------- -------- ---- ------ -------

MSC051234A CMISE LOCAL UNL-ENA OMU 21FH 0000H

AP_TYPE :AP_TITLE :AEQ :


COMMAND EXECUTED


<aen> Name of the OSI application entity name:

• BSC0<bbbbb>A in the BSC

• MSC0<mmmmm>A in the MSC

• HLR0<hhhhh>A in the HLR



NTC TAN 0839/2.2 en126

2. If the state is set toLOC-ENA go to the next step. Otherwise, change theCMISE state toLOC-ENA by entering:

ZQDG:<aen>,LOC;


LOADING PROGRAM VERSION <number>

DX 200 TOM 1998-10-02 10:00:00

CHANGING OSI APPLICATION STATE:

AE-NAME OLD STATE NEW STATE-------- --------- ----------

MSC051234A UNL-ENA LOC-ENA

COMMAND EXECUTED


3. Define the CMISE service profile by entering:

ZQDA:<aen>:MOS=Y,FLT=Y,MR=Y,ES=N,CG=Y,:VER_1_AND_2;

4. Change the CMISE state toUNL-ENA by entering:

ZQDG:<aen>,UNL;


LOADING PROGRAM VERSION <number>

DX 200 TOM 1998-02-26 10:00:00

CHANGING OSI APPLICATION STATE:

AE-NAME OLD STATE NEW STATE-------- --------- ----------

MSC051234A LOC-ENA UNL-ENA

COMMAND EXECUTED


<aen> Name of the OSI application entity name:

• BSC0<bbbbb>A in the BSC

• MSC0<mmmmm>A in the MSC

• HLR0<hhhhh>A in the HLR



NTC TAN 0839/2.2 en127

5. Interrogate the CMISE service profile, and ensure the values are correct byentering:

ZQDI:AEN=<aen>:PAR;



DX 200 TOM 1998-10-02 10:00:00

INTERROGATING SERVICE PROFILE DATA

AE-NAME SERVICE PROFILE TYPE------------ -------------------------------------

MSC051234A CMISE

MULTIPLE OBJECT SELECTION =YES FILTER SUPPORT =YESMULTIPLE REPLYS =YES EXTENDED SERVICE =NOCANCEL GET OPERATION =YES CMISE VERSION =1 AND 2

COMMAND EXECUTED



using X.25 and you have set up thelocal MSW and PAD applications

Setting up the remote PAD and MSWapplicationson page 128.

using a LAN Setting up remote applicationson page132.



NTC TAN 0839/2.2 en128

7.3.4 Setting up the remote PAD and MSW applications

Remote PAD and MSW connections are used between a network element and anintermediate system. To set up these applications in a DX 200 network element,follow the instructions listed below.

Note:

Perform the following tasks only if using X.25 and the local PAD/MSWapplications have been set up. If using a LAN, go toSetting up remoteapplicationson page 132.

To set up the remote MSW and PAD applications

1. Set up the remote PAD applications by entering:

ZQDR:<aen>:::UNL:<unit_info>:<type>:<NW_addr>;

2. If using X.25 with a Front End, set up the remote MSW applications byentering:

ZQDR:<aen>:::UNL:<unit_info>:<type>:<NW_addr>;

<aen> Name of the application entity name, seeDX 200applicationson page 178.





<NW_addr> Local network address name used by the application,seeCONS network protocol address nameson page177.



NTC TAN 0839/2.2 en129

3. Interrogate the remote application data by entering:

ZQDI:APL=REM:MAX;



DX 200 TOM 1998-10-02 10:00:00

REMOTE OSI APPLICATION DATA

AE-NAME APPL NET ADDR STATE----------- ------ -------- --------

CISCOPAD PAD REMCISCOPAD1 UNL-ENAOMC012345MSW MSW REMMSW0 UNL-ENA


P-SELECTOR:S-SELECTOR:T-SELECTOR:

COMMAND EXECUTED



• Network protocol address name(NET ADDR) is specified as inCreating NSAPs and network protocol addresses, Step 4. on page114.




NTC TAN 0839/2.2 en130

7.3.5 Adding an O&M connection

O&M connections are added to enable MSW applications (local and remote) tocommunicate with one another. The advantages of such a connection are:

• MML log print-outs can be directed to any device in the MSW network.

• MML sessions can be taken from the MSW to the exchange.

Note:

Before adding an O&M connection, ensure the local and remote MSWapplications have been set up using an X.25 connection.

To add an O&M (Operations & Maintainence) connection, follow theinstructions listed below.

To add an O&M connection

1. Add a new O&M connection by entering:

ZQNA:<NE_type>,,<qqqqq>:NAME=<name>,LOC=<location>:<unit>[,<index>]:AEN=<aen>;


LOADING PROGRAM VERSION <version_number>

CONNECTION <connection_number> CREATEDCOMMAND EXECUTED

O&M CHANNEL HANDLING <QN_>

<NE_type> The target network element (system type)

<qqqqq> C number of the target network element

<name> Name of the target network element

<location> System location

<unit> Unit responsible or the connection

<index> Index of the unit responsible for the connection

<aen> Name of the remote MSW application entityname, seepage 178.



NTC TAN 0839/2.2 en131

2. Change the state of the O&M connection toBL-US by entering:

ZQNC:<channel_number>:BL;


STATE TRANSITION EXECUTEDCHANNEL NUMBER = <channel_number> NEW STATE = BL-USCOMMAND EXECUTED


3. Change the state of the O&M connection toWO-EX by entering:

ZQNC:<channel_number>:WO;


STATE TRANSITION EXECUTEDCHANNEL NUMBER = <channel_number> NEW STATE = WO-EXCOMMAND EXECUTED


4. Interrogate the O&M connection data, and ensure the values are correct byentering:

ZQNI:CON=<connection_number>:COM;



DX 200 TOM 1998-08-25 10:00:00

CONNECTION= CHANNEL= STATE=WO-EXNAME= TOM LOC=FLATYPE= BSC SW-LEVEL=5 C-NUM=12345 ID=CTYP=PSPN COMP= F/P= S/R=AEN= TIME=

COMMAND EXECUTED




NTC TAN 0839/2.2 en132

7.3.6 Setting up remote applications

Before establishing a NE→ NMS connection, the remote applications must bespecified in the network element. To set up the remote applications in a DX 200network element, follow the instructions listed below.

To set up remote OSI applications in a DX 200 network element, follow theinstructions listed below.

To set up a remote application

1. Set up the remote applications in the DX 200 by entering:

ZQDR:<aen>:::UNL:<type>:<NW_addr>:<P_sel>:<S_sel>:<T_sel>;

Repeat this step for all remote applications in the NMS applications tablebeginning on page 183.

Figure 23.Creating remote OSI applications in the DX 200

<aen> Name of the OSI application entity name, seeNMSapplicationson page 183.


<NW_addr> Network address name used by the application, seeNetwork protocol address nameson page 176.

<P_sel> P selector value, seeNMS applications in DX 200network elementson page 183.

<S_sel> S selector value

<T_sel> T selector value



NTC TAN 0839/2.2 en133

2. Interrogate the remote OSI application data, and ensure the values arecorrect by entering:

ZQDI:APL=REM:MAX;



DX 200 TOM 1998-10-02 10:00:00

REMOTE OSI APPLICATION DATA

AE-NAME APPL NET ADDR STATE----------- ------ -------- --------

OMC000000SW VFS WS UNL-ENA



COMMAND EXECUTED



• Network protocol address name(NET ADDR) is specified as inCreating NSAPs and network protocol addresses, Step 4. on page114.




NTC TAN 0839/2.2 en134

7.3.7 Changing power measurements levels in a BSC

When upgrading from T8 to T10, the power measurements levels must bechanged from BTS to TRX in theBMPARA_SPARE file. Once the powermeasurement levels have been changed, theTRX ID andTRX frequency willbe included in the measurement record identifier.

This section describes how to change the power measurements levels in the BSCusing S6 software.

To change power measurement levels in a BSC using S6 software

1. Display the format of theBMPARA_SPARE file by entering:

ZDFD:OMU:6C7,0;



DX 200 TOM 1998-10-02 10:00:00

OMU FILE N:O 06C70000 RECORDN:O 00000000

FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF ................








COMMAND EXECUTED

MEMORY FILE HANDLING COMMAND <DF_>

2. Ensure the fourth last value (7C) is set toFF as listed above. If the value isset toFF, go to the next section required for your integration.

3. If the value is not set toFF stop the GSM power control measurements byentering:

ZTPE:MEASUR,POWER::;

4. Change the power measurement levels by entering:

ZDFS:OMU:6C7,0,7C,B;

When prompted for a value, enterFF.

5. Start the GSM power control measurements by entering:

ZTPS:MEASUR,POWER::;



NTC TAN 0839/2.2 en135

7.3.8 Adding new counters in a BSC

When upgrading from T8 to T10, two new counters, per neighbour cell, havebeen added to the handover adjacent cell measurements. To view these counters,the handover adjacent cell measurement record must be changed from 170counters/record to 238 counters/record in theBMPARA_SPARE file.

This section describes how to add the counters in the BSC using S6 software.

To add new counters in a BSC using S6 software

1. Display the format of theBMPARA_SPARE file by entering:

ZDFD:OMU:6C7,0;



DX 200 TOM 1998-10-02 10:00:00

OMU FILE N:O 06C70000 RECORDN:O 00000000








FF FF FF FF FF FF FF FF FF FF FF FF FF FF 01 FF ................

COMMAND EXECUTED

MEMORY FILE HANDLING COMMAND <DF_>

2. Ensure the second last value (7E) is set to01 as listed above. If the valueis set to01, go to the next section required for your integration.

3. If the value is not set to01 stop the GSM handover measurements byentering:

ZTPE:MEASUR,HO::;

4. Change the size of the handover adjacent cell measurement record byentering:

ZDFS:OMU:6C7,0,7E,B;

When prompted for a value, enter01.

5. Start the GSM handover measurements by entering:

ZTPS:MEASUR,HO::;



NTC TAN 0839/2.2 en136

7.3.9 Setting up logical files in the MSC/HLR

When upgrading from T8 to T10, the logical files responsible for measurements(MEAFIL), observations (OBSFIL) and event buffering (EVBFIL ) must beredirected from the Front End to the logical files in the MSC/HLR.

Logical files are used to route reading and writing tasks to I/O devices thushiding the actual I/O device from an application.

This section describes the redirection of logical files in the MSC/HLR usingM7B/M8 software.

To set up the logical files in the MSC/HLR using M7B software

1. Add the virtual data storage (VDS-2) device connection to the event bufferlogical file (EVBFIL ) by entering:

ZIIS::EVBFIL::OU=OMU,DEV=VDS-2;

2. List the logical files connected toVDS-2 by entering:

ZIIL::DEV=VDS-2;

3. Ensureonly EVBFIL is connected toVDS-2. If other logical files areconnected toVDS-2, remove them by entering:

ZIIS::<file>:OU=OMU,DEV=VDS-2:;

Figure 24.Abbreviated syntax of the ZIIS command

<file> Name of the logical file



NTC TAN 0839/2.2 en137

4. List the objects connected toEVBFIL by entering:

ZIIL::LF=EVBFIL;



OBJECT CONNECTED IN FOLLOWING LOGICAL FILES:

SYSTEM = MSC-T UNIT = OMU

PAGE 1

LOG LOG SPARE PHYSICAL OBJ SYSTEM UNIT DEVICE/

FILE FILE FILE FILE IND NAME NAME LOGICAL

NBR NAME & CLASS MODE NAME FILE

/* OBJECT NOT CONNECTED TO ANY LOGICAL FILE */

COMMAND EXECUTED

I/O CONFIGURATION HANDLING COMMAND <II_>

5. Ensure there are no connections to theEVBFIL file. If other logical filesare connected to theEVBFIL file, remove them by entering:

ZIIS::<file>:OS=<system_name>,OU=OMU,LF=EVBFIL;

6. Change the devices connected to the measurement (MEAFIL) andobservation (OBSFIL) logical files by entering:

ZIIS::OBSFIL::OU=OMU,DEV=VDS-0;ZIIS::MEAFIL::OU=OMU,DEV=VDS-1;

7. List the logical files connected toVDS-0 or VDS-1 by entering:

ZIIL::DEV=VDS-0;ZIIL::DEV=VDS-1;

8. Ensure there are no logical files connected toVDS-0 or VDS-1. If otherlogical files are connected, remove them by entering:

ZIIS::<file>:OU=OMU,DEV=VDS-0:;ZIIS::<file>:OU=OMU,DEV=VDS-1:;


<system_name> Name of the MSC/HLR



NTC TAN 0839/2.2 en138

9. List the objects connected to theGSMME1MG logical file by entering:

ZIID::GSMME1MG;



LOGICAL FILE(S):


PAGE 1



NBR NAME & CLASS MODE NAME FILE

95 GSMME1MG P 1 MSC-T OMU OBSFIL

COMMAND EXECUTED


10. Ensure there are no connections to the Front End. If a connections exists,replace the link with a connection to the observation (OBSFIL) file in theMSC/HLR by entering:

ZIIS::GSMME1MG:OS=<fe_name>,OU=PFMU,LF=MSCMEA01MG:OS=<system_name>,OU=OMU,LF=OBSFIL;

11. If there is no connections to the Front End, connect the GSM observationreport (GSMME1MG) file to theOBSFIL in the MSC/HLR by entering:

ZIIS::GSMME1MG::OS=<system_name>,OU=OMU,LF=OBSFIL;

Table 21.Logical files for observations in the MSC/HLR

12. List the information connected to theMSCMEA01MG logical file byentering:

ZIIL::OS=<fe_name>,OU=PFMU,LF=MSCMEA01MG;

<fe_name> Name of the Front End


GSMME1MG -



NTC TAN 0839/2.2 en139

13. If a connection exists to the Front End, replace the link with a connectionto the measurement (MEAFIL) logical file in the MSC/HLR by entering:

ZIIS::<file>:OS=<fe_name>,OU=PFMU,LF=MSCMEA01MG:OS=<system_name>,OU=OMU,LF=MEAFIL;

14. If there are no connections to the Front End, connect the logical file to themeasurement (MEAFIL) logical file in the MSC/HLR by entering:

ZIIS::<file>::OS=<system_name>,OU=OMU,LF=MEAFIL;

Table 22.Logical files for measurement data handling in the MSC

Table 23.Logical files for measurement data handling in the HLR




ACVLRB ROUTSTB

FIELDRMG SECCOUNTB

GSMME2MG TRAANNA

GSMME3MG TRAANNB

GSMME4MG TRABSB

GSMME5MG TRABSA

LOAOBSMG TRACGRB

MTTRAN TRACNTLB

MTTRMS TRACTDB

OSIMEAS1B TRADESTB

OSIMEAS2B TRADTDB

OSIMEAS3B TRATCATB

OSIMEAS4B TRAVANB

ACHLRB OSIMEAS2B

EIRMEASB OSIMEAS3B

FIELDRMG OSIMEAS4B

LOAOBSMG ROUTSTB

OSIMEAS1B SECCOUNTB



NTC TAN 0839/2.2 en140

15. List the logical files connected to the virtual report converter (VRP-0) byentering:

ZIIL::OS=<fe_name>,OU=OMU,DEV=VRP-0;



OBJECT CONNECTED IN FOLLOWING LOGICAL FILES:


PAGE 1



NBR NAME&CLASS MODE NAME FILE

2C DIAGNOS P 1 FE-T OMU LPT-12 FE-T OMU VRP-0

6D OMCALARM P 1 FE-T OMU VRP-0

COMMAND EXECUTED


16. If OMCALARM is connected to the Front End, replace the link fromOMCALARM to the local byte basket (BBU-0) by entering:

ZIIS::OMCALARM:OS=<fe_name>,OU=OMU,DEV=VRP-0:OS=<system_name>,OU=OMU,DEV=BBU-0;

17. If DIAGNOS is connected to the Front End, replace the link fromDIAGNOSto the local line printer (LPT-1 ) by entering:

ZIIS::DIAGNOS:OS=<fe_name>,OU=OMU,DEV=VRP-0:OS=<system_name>,OU=OMU,DEV=LPT-1;

18. List the logical files connected to the local line printer (LPT-0 ) byentering:

ZIIL::DEV=LPT-0;





NTC TAN 0839/2.2 en141

19. If any logical file for fault management data handling is connected to theFront End, replace the link from the Front End toLPT-0 in the MSC/HLRby entering:

ZIIS::<file>:OS=<fe_name>,OU=OMU,DEV=LPT-0:OS=<system_name>,OU=OMU,DEV=LPT-0;

Table 24.Logical files for fault management data handling in the MSC/HLR

Note:

Not all the logical files listed in this section are used.

If measurement are not coming through the NMS, reset the activeOperations and Maintainence Unit by entering:

ZUSU:OMU,<index>;





DIAGNOS SWITCH1

EXTERN1 SWITCH2

EXTERN2 TRANSM1

OMCALARM TRANSM2

Configuring intermediate systems


NTC TAN 0839/2.2 en142

8 CONFIGURING INTERMEDIATE SYSTEMS

If configuring a router or Front End, perform the integration tasks described inIntegrating Intermediate Systems, TAN 0900. Otherwise, go toVerifying DCNintegrationon page 143.

Verifying DCN integration


NTC TAN 0839/2.2 en143

9 VERIFYING DCN INTEGRATION

To verify that the integration has been completed successfully, perform theintegration tests described inTesting Installations, TAN 0523.

Appendix A. Network card jumpers


NTC TAN 0839/2.2 en144

Appendix A. NETWORK CARD JUMPERS

This appendix describes the jumpers on the following network cards:

• AC25-S (analog X.25)

• AS7-U (digital X.25)

• COCEN (Ethernet)

As a precaution, set all jumpers according to the instructions listed in thisappendix. You may modify the jumper settings at a later date.

Communication card modes

The following tables present the communication card modes using indirect anddirect connections between the network element and the NMS.

Table 25.Communication modes used with indirect connections

Table 26.Communication modes used in direct connections

System Mode

NMS DTE

IS DCE

DX 200 DTE

System Mode

NMS DTE

DX 200 DCE



NTC TAN 0839/2.2 en145

1 AC25-S NETWORK CARD

The following figure illustrates the jumpers on the AC25-S network card.

Figure 25.Jumpers on the AC25-S network card

W 1 W 2 W 3

AC25-S C 8596 CDEFGH 01 9137 10871

C 8596

Perlos- C

096MS-C1A -1.25/5 044

Perlos- C064MS-C1A -1.25/5 049

Perlos- C064MS-C1A -1.25/5 049

TELENOKIA

75-08596-01-0

W 1 W 2 W 3123

W 4 W 5123

123

W 6

W 7

W 8

12

123

43

654

W 1

W 1 31234567

1 41 31 21 11 098

123

AC25-5

4.13-0

A25X25GX

H

AC25-5

4.13-0

A25X25GX

L

R A M

R A M

R A M

R A M

W 2 51234

8765

8 5 9 6 B 1

8 5 9 6 A 1



NTC TAN 0839/2.2 en146

1.1 Jumper blocks

The AC25-S jumper block has the following functions:

Table 27. AC25-S jumper block functions

Jumper block(s) Function

W13 Specifies the memory address space allocated for the card

W4, W8 Defines the communication mode for the V.24 and V.35protocols

W3, W4, W5,W7, W9

Defines the communication mode for the X.21 protocol

W25 Defines the interchangeability code of the card



NTC TAN 0839/2.2 en147

1.2 Memory space addresses

The W13 jumper block defines the memory space address allocated to a cardfrom the address space of the unit.

The following table lists the memory space start addresses (MS), memory spaceend address (ME) and their corresponding jumper settings.

Table 28.Jumpers for memory space address (AC25-S)

piu MS ME W13 jumper settings (X = on)

1-14 2-13 3-12 4-11 5-10 6-9

7-8

0 80100000- 801FFFFF X X X - X X X

1 80200000- 802FFFFF X X - X X X X

2 80300000- 803FFFFF X X - - X X X

3 80400000- 804FFFFF X - X X X X X

4 80500000- 805FFFFF X - X - X X X

5 80600000- 806FFFFF X - - X X X X

6 80700000- 807FFFFF X - - - X X X

7 80800000- 808FFFFF - X X X X X X



NTC TAN 0839/2.2 en148

1.3 Interchangeability codes

The following table presents the interchangeability code jumpers on the AC25-S network card.

Table 29.Interchangeability code jumpers on the AC25-S network card

The interchangeability code is written on the network card next to the euroconnector. The text on the label may look like the following:

Example 4.

AC25-S C 8596 F G H I J K 01 19519 62604

The first visible letter in the series (F G H I J K in the above given example)is the interchangeability code. In the above example, the version of the card isF.

Code W25 jumpers (X = on)

- 1-8 2-7 3-6 4-5

A X X X X

B - X X X

C X - X X

D - - X X

E X X - X

F - X - X

G X - - X

H - - - X

J X X X -

K - X X -

L X - X -

M - - X -

N X X - -

P - X - -

R X - - -



NTC TAN 0839/2.2 en149

1.4 Communication modes

The following tables present the jumpers for the communication mode on theAC25-S network card when a straight cable (without signal change) is used.

Table 30.Jumpers for the V.24 and V.35 communication modes (AC25-S)

Table 31.Jumpers for the X.21 communication mode (AC25-S)

If the AC25-S is connected to a modem or some other DCE-type device, youshould select the DTE mode. If a direct connection to another end (AC25-S cardto an other AC25-S card) with a null-modem cable is used, the AC25-S is usuallyacting as DCE, meaning that it provides clocking. When using an X.21connection, you have to use the DCE-DTE jumper setting, and when using aV.35, V.36 or V.24 connection, the jumper setting is DCE-DCE.

Note:

In our instructions, the W6 jumper setting is configured for serial use. If youintend to use any other configuration, please refer toConfiguring the DX 200network elementon page 79.

Mode Jumper setting (X = on)

W4 W8

1-2 2-3 1-6 2-5 3-4

V.24, DTE X - X - -

V.24, DCE - X X - -

V.35, DTE X - - X -

V.35, DCE - X - X -

Mode Jumper setting (X = on)

W3 W4 W5 W7 W9

1-2 2-3 1-2 2-3 1-2 2-3 1-4 2-3 1-2 2-3

X.21, DTE - X X - - X - - - X

X.21, DCE - X - X - X X X - X



NTC TAN 0839/2.2 en150

2 AS7-U NETWORK CARD

The following figure illustrates the jumpers on the AS7-U network card.

Figure 26.Jumpers on the AS7-U network card



NTC TAN 0839/2.2 en151

2.1 Jumper blocks

The jumper blocks on the network card have the following functions:

Table 32. Important jumper blocks (AS7-U)




Table 33.Jumpers for memory space address (AS7-U)

Jumperblock(s)

Function


W9 Specifies the interchangeability code of the card

W12 Specifies the memory size of the card

PIU-index MS ME W3 jumpers (X = on)

3-4 5-6 7-8 9-10

0 80100000- 801FFFFF X X X -

1 80200000- 802FFFFF X X - X

2 80300000- 803FFFFF X X - -

3 80400000- 804FFFFF X - X X

4 80500000- 805FFFFF X - X -

5 80600000- 806FFFFF X - - X

6 80700000- 807FFFFF X - - -

7 80800000- 808FFFFF - X X X



NTC TAN 0839/2.2 en152


The following table presents the interchangeability code jumpers on the AS7-Unetwork card.

Table 34.Interchangeability code jumpers on the AS7-U network card

The interchangeability code is written on the network card next to the euroconnector. The text on the label may look like the following:

Example 5.

AS7-U C 8530 K L M N O P 04 3G 9715 3340

The first visible letter in the series (K L M N O P in the above given example)is the interchangeability code. In the above example, the version of the card isK.


- 1-5 2-6 3-7 4-8

A X X X X

B X X X -

C X X - X

D X X - -

E X - X X

F X - X -

G X - - X

H X - - -

J - X X X

K - X X -

L - X - X

M - X - -

N - - X X

P - - X -

R - - - X



NTC TAN 0839/2.2 en153

2.4 Memory size

The W12 jumper block defines the memory size. When closed, the availablememory is 256K, and when open, 64K. When the network card is used for X.25connections, the jumpers should be open. When using the AS7-U for MSWconnections, W12 should be closed.



NTC TAN 0839/2.2 en154

3 COCEN NETWORK CARD

The following figure illustrates the jumpers on the COCEN network card.

Figure 27.Jumpers on the COCEN network card

W 1W 2 W 312345678

123456

1 61 51 41 31 21 11 09

1 21 11 0987

1 2 3 4 5 6 7 8 9 1 0 1 1 1 2

W 2

W 3 W 41 2 1 2 1

23

1 2 1 2W 7 W 86 5 4

1 2 3

1234

8765

123

1 2

W 1 1

W 1 2

W 1 4

W 1 5 W 1 6

1 2 1 2

6 5 4

1 2 3

12

W 1 7

12

W 1 1

W 1 0

W 6

W 1

W 5

1 2W 9

W 1 3

B COCEN C 8669 A B C D E F 1A 1F 9719 9205

A C 8669

Perlos- C

064MS-C1A -1.2

5/5 049

Perlos- C

064MS-C1A -1.2

5/5 0498 6 6 9

D 18 6 6 9 E 1 8 6 6 9

F 1

8 6 6 9 A 1

8 6 6 9 B 1

8669

C1

R A M R A M

R A M R A M

R A M R A M

R A M R A M

A U I

COAX

T P I



NTC TAN 0839/2.2 en155

3.1 Jumper blocks

The jumper blocks on the network card have the following functions:

Table 35. Important jumper blocks (COCEN)




Table 36.Jumpers for memory space addresses (COCEN)

Jumperblock(s)

Function


W12 Specifies the interchangeability code of the card

PIU-index

MS ME W1 jumpers (X = on)

1-16 2-15 3-14 4-13

5-12

6-11

7-10

8-9

0 80100000- 801FFFFF X X X X - X X X

1 80200000- 802FFFFF X X X - X X X X

2 80300000- 803FFFFF X X X - - X X X

3 80400000- 804FFFFF X X - X X X X X

4 80500000- 805FFFFF X X - X - X X X

5 80600000- 806FFFFF X X - - X X X X

6 80700000- 807FFFFF X X - - - X X X

7 80800000- 808FFFFF X - X X X X X X



NTC TAN 0839/2.2 en156


The following table presents the interchangeability code jumpers on the COCENnetwork card.

Table 37.Interchangeability code jumpers on the COCEN network card

For information on where the interchangeability code is located, seeInterchangeability codeson page 148.


- 1-5 2-6 3-7 4-8

A X X X X

B - X X X

C X - X X

D - - X X

E X X - X

F - X - X

G X - - X

H - - - X

J X X X -

K - X X -

L X - X -

M - - X -

N X X - -

P - X - -

R X - - -



NTC TAN 0839/2.2 en157

4 CABLES

This chapter presents the cables used when integrating the Nokia NMS withother network elements.

When carrying out the integration, note the following:

• All cables that are used should be twisted pair cables.

• Differential signals should use one twisted pair.

The following cables are available:

Table 38.Cables and connections

Connection type Connecting components

V.35 from PDE to PDE

V.35 from AC25-S to PDE

X.21 from PDE to PDE

X.21 from AC25-S to PDE

X.21 from PDE to modem

V.24 from PDE to modem

Appendix B. X.25 parameter sets


NTC TAN 0839/2.2 en158

Appendix B. X.25 PARAMETER SETS

Table 39.General X.25 parameters

Table 40.Level 2 parameters

General

Parameter Value

MAXIMUM NETWORK SERVICEDATA UNIT LENGTH

8192 BYTES

L2 CONNECTION MODE INITIATED AFTER START UP

USER FACILITIES NO USER FACILITIES

Level 2

Parameter Value

L2 TIMER T1 6 SECONDS

L2 TIMER T2 NOT IN USE

L2 TIMER T3 NOT IN USE

L2 INTERFRAME FILL 01111110

L2 BITS IN FRAME 1024 BITS

L2 RETRY COUNT 10 TIMES

L2 WINDOW 7 FRAMES

L2 LINE DOWN TIMER 20 (NOT SUPPORTED)

Level 3

Parameter Value

L3 USER DATA SIZE 128 BYTES

L3 SEND WINDOW SIZE 2 FRAMES

L3 MODULO 8





L3 RESET RETRY COUNT 5 TIMES

L3 CLEAR RETRY COUNT 5 TIMES

L3 FIRST PVC 0 (= NOT IN USE)

Appendix B. X.25 parameter sets


NTC TAN 0839/2.2 en159

Table 41.Level 3 parameters

L3 LAST PVC 0 (= NOT IN USE)

L3 LIC 0 (NOT SUPPORTED)

L3 HIC 0 (NOT SUPPORTED)

L3 LTC 1

L3 HTC 16

L3 LOC 0 (NOT SUPPORTED)

L3 HOC 0 (NOT SUPPORTED)

Level 3

Parameter Value

Appendix C. Configuration information


NTC TAN 0839/2.2 en160

Appendix C. CONFIGURATION INFORMATION

This appendix lists the type of information needed when testing DCNintegration. Information regarding the following objects are included:

• Servers

• Network elements

1 SERVERS

If your server is partially configured, and the network map does not contain, allof the configuration information, interrogate or obtain the following items:

• Passwords

Passwords for theomc androot users

• Hardware

The make and model of the server, for example:

• Hewlett Packard K 370

• Role

The function of the server

• Communications Server

• Standby Server

• Database Server

• Software

The software version of the NMS, for example:

• TH-NMS10.0-7



NTC TAN 0839/2.2 en161

• Hostname

Any string value that identifies the name (alias) of the server.

• Physical address (12)

A 12-character value that defines the core address of the server.

• NSAP address

A 40-character value issued by the respective standards institute of eachcountry. For more information regarding NSAPs and their structure, seeDCN Management, TAN 0377.

• Type of NSAP

Depending on you network architecture you may have one or more of thefollowing NSAPs.

• Communications Server NSAP

• Standby Server NSAP

• comm package NSAP

Physical address Network type

IP address of the system LAN

X.121 address Analog X.25 (PSN)



NTC TAN 0839/2.2 en162

2 NETWORK ELEMENTS

If your network element is partially configured, and the network map does notcontain, all of the configuration information, interrogate or obtain the followingitems:

• Passwords

Passwords for thesystem user

• Hardware

The make and model of the network element, for example:

• Nokia DX 200

• Role

The function of the network element, for example:

• BSC

• DAXWLL

• FE

• HLR

• MSC

• Software

The software version of the network element, for example:

• S7 7.16-0

• M8 6.9-0

• Hostname

Any string value that identifies the name (alias) of the network element.



NTC TAN 0839/2.2 en163

• Physical address (DTE)

A 12-character value that defines the core address of the networkelement.The DTE identifier is always used as the network element X.121address.

• NSAP address

A 40-character value issued by the respective standards institute of eachcountry. For more information regarding NSAPs and their structure, seeDCN Management, TAN 0377.

• C-number

A 5-character value taken from the NSAP system identifier. For moreinformation regarding system identifiers, seeDCN Management, TAN0377.

Physical address Network type

X.121 address (DTE) Analog X.25 (PSN)

Abbreviation Explanation Number ofcharacters

Network element The name of the NE

AFI Authority Format Identifier 2

IDI Initial Domain Identifier 4

DFI DSP format identifier 2

ORG Organisational identifier 6

RESERVED Reserved and routing domains8 (4 + 4)

AREA Routing area 4

END SYSTEM C-number of the NE paddedwith zeros from the left.

12

SEL N-selector 2

Appendix D. Configuration worksheets


NTC TAN 0839/2.2 en164

Appendix D. CONFIGURATION WORKSHEETS

Due the amount of values needed to test DCN integration, fill in the followingworksheets before testing begins. Once all values have been interrogated andwritten down, no further memorisation and guesswork is necessary.

1 SERVER WORKSHEET

When establishing connections to a server, the physical addresses (X.121 or IP)are used to establish those connections.

To fill in the server worksheet

1. Login to the server as theroot user.

2. Interrogate the software version of the NMS server by entering:

# csh% cd $OMCROOT% exit


florida:/d/it04/builds/TH-NMS11.0-11 (116) #

3. Interrogate the hostname of the NMS server by entering:

# hostname

4. Interrogate the IP address of the NMS server by entering:

# nslookup <host>


Default NIS Server: florida.tele.nokia.fi

Address: 196.222.122.10

Aliases: florida

Trying NIS

Name: florida.tele.nokia.fi

Address: 196.222.122.10

Aliases: florida



NTC TAN 0839/2.2 en165

5. Interrogate the X.121 address by entering:

# more /etc/x25/x25config_<no.>

<no.> is the number of the X.25 card.


# X.25 Initialization File Created: Wed Oct 02 10:00:00 1998

#

# Global Parameters

#

x.121 111222199188...

6. Interrogate the NSAP addresses of the NMS server by entering:

# /opt/ots/bin/otsshownsaps

Note:

The first NSAP is the physical address of the server. The last NSAP, ifthere is one, is thecomm package NSAP.



NTC TAN 0839/2.2 en166

7. Copy required information displayed on the terminal to the followingtable.

Table 42.Server worksheet

Hardware

Role

Software

Hostname

IP address

X.121 address

NSAP address

Type of NSAP



NTC TAN 0839/2.2 en167

2 NETWORK ELEMENT WORKSHEET

To fill in the network element worksheet enter the following MML commandand copy the information displayed to the following table:

To fill in the network element worksheet

1. Login to the network element.

2. Interrogate the software version of the network element by entering:

ZWQO:RUN;

3. Interrogate the NSAP address of the network element by entering:

ZQEI;



INTERROGATING CLNS

DX 200 TOM 1998-10-02 10:00:00

NODE IN ES ROLE

NS USER NS USER MAX PDU SYSTEM

CLNS NAME ROLE PRIM UNIT ACT UNIT LIFETIME ID STATE

--------- ---- --------- --------- -------- --------- ---------

CLNSX25 ES OMU - 9 000000012345 LOC-NW-ENA

MAX MAN AREA ADDR COUNT: 3

MANUAL AREA ADDRESS: 39246F00000116000000010025

COMMAND EXECUTED

OSI ENVIRONMENT CONNECTIONLESS NETWORK SERVICE HANDLING COMMAND <QE



NTC TAN 0839/2.2 en168

4. Interrogate the C-number of the network element by entering:

ZQNI;



DX 200 TOM 1998-10-02 10:00:00PAGE 1

CON TYPE SW C-NUMID NAME LOCATION CHA STATECTYP

000 BSC 5 12345 TOM NMS-FLA

001 OMC 5 54321 NMSFLA_2 NMS-FLA 000 BL-SYPSPN

COMMAND EXECUTED




NTC TAN 0839/2.2 en169

5. Copy required information displayed on the terminal to the followingtable.

Table 43.Network element worksheet

Hardware

Role

Software

Hostname

X.121 address

NSAP address

C-number

Appendix E. Integration checklists


NTC TAN 0839/2.2 en170

Appendix E. INTEGRATION CHECKLISTS

This appendix contains several the checklists used for DCN integration. As youcomplete each task, mark the appropriate box.

1 PRELIMINARY TASKS

Copy the configuration worksheets on page 164 ❏ Task completed

Fill-in the configuration worksheets as on page 160❏ Task completed

Server information ❏ Task completed

Passwords ❏ Task completed

Hardware ❏ Task completed

Role ❏ Task completed

Software ❏ Task completed

Hostname ❏ Task completed

Physical address ❏ Task completed

NSAP address ❏ Task completed

Type of NSAP ❏ Task completed

Network element information ❏ Task completed

Passwords ❏ Task completed

Hardware ❏ Task completed

Role ❏ Task completed

Software ❏ Task completed

Hostname ❏ Task completed

Physical address ❏ Task completed

NSAP address ❏ Task completed

C-number ❏ Task completed

Review the system requirements, see page 27 ❏ Task completed

Create a managed object in the NMS as on page 30❏ Task completed

Create and define users rights as on page 31 ❏ Task completed



NTC TAN 0839/2.2 en171

2 CONFIGURING THE NMS COMMUNICATIONSSERVER

This contains the checklist for configuring the NMS Communications Server.

Determine which network service is used as on page 17❏ Task completed

Determine if X.121 subaddressing is needed, see page 35❏ Task completed

Modify X.25 addresses as on page 35 ❏ Task completed

Set up the OSI subnetwork as on page 37 ❏ Task completed

CLNS X.25 Set up the CLNS subnet as on page 39❏ Task completed

Add thecomm package NSAPs as onpage 44

❏ Task completed

LAN Set up the LAN subnet as on page 41❏ Task completed

CONS X.25 Set up the CONS subnet as on page 46❏ Task completed

If you are using an IS, add the IS as an ISO OSIdestination as on page 50

❏ Task completed

Add a route to a default IS as on page 51 ❏ Task completed

Configure the OSI applications as on page 52 ❏ Task completed



NTC TAN 0839/2.2 en172

3 CONFIGURING OSI APPLICATIONS

This contains the checklist for configuring the OSI applications within the NMSCommunications Server.

Are you using X.25 ❏ Task completed

yes

Set up the remote PAD service as on page 53❏ Task completed

Set up the DX 200 OSI applications as onpage 56

❏ Task completed

no

Set up the DX 200 OSI applications as onpage 56

❏ Task completed

Configure the OSI protocol identifiers ❏ Task completed

Configure the Connection Server software as on page 59❏ Task completed



NTC TAN 0839/2.2 en173

4 CONFIGURING THE CONNECTION SERVERSOFTWARE

This contains a checklist for configuring the Connection Server software.

Back up the DCN configuration file, see page 61 ❏ Task completed

Edit the/etc/services file, see page 62 ❏ Task completed

Configure theInetd daemon, see page 63 ❏ Task completed

Edit the CS configuration file, see page 65 ❏ Task completed

Add an arc to a remote system, see page 68 ❏ Task completed

Add a route to a remote system, see page 70 ❏ Task completed

Add an administrative route, see page 72 ❏ Task completed

Add a node definition to a remote system, see page 74❏ Task completed

Re-read the configuration file, see page 77 ❏ Task completed

Verify the DCN configuration, see page 78 ❏ Task completed



NTC TAN 0839/2.2 en174

5 CONFIGURING THE DX 200 NETWORK ELEMENT

Set up the physical connection as on page 80

X.25 see,Using analog X.25 (PSN)on page 81 ❏ Task completed

PCM see,Using digital X.25 (PCM)on page 89 ❏ Task completed

LAN see,Using digital X.25 (PCM)on page 89 ❏ Task completed

Determine which network service is used ❏ Task completed

CLNS

Set up the CLNS object ❏ Task completed

Set up the linkage object ❏ Task completed

Set up the NSAPs ❏ Task completed

Set up the network addresses ❏ Task completed

CONS

Set up the NSAPs ❏ Task completed

Set up the network addresses ❏ Task completed

Configure OSI applications and addresses as on page118

❏ Task completed

Determine local application information

Name of the OSI application ❏ Task completed

Unit responsible for OSI communication❏ Task completed

Application type ❏ Task completed

Network address used by application ❏ Task completed

P,S and T selector values ❏ Task completed

Set up the local applications ❏ Task completed

Set up the remote applications ❏ Task completed

Add an O&M connection ❏ Task completed

Appendix F. OSI Parameters


NTC TAN 0839/2.2 en175

Appendix F. OSI PARAMETERS

This appendix presents N - selectors, Subsequent Protocol Identifiers (SPIs),network addresses and OSI application address required during integration.

1 N - SELECTORS AND SPIS

1.1 N - selectors for CLNS communications

Table 44.Recommended N - selectors for CLNS

1.2 SPIs for CONS communications

DX 200 (local) SPIs

Table 45.DX 200 (local) SPIs for CONS

NMS (remote) SPIs

Table 46.NMS (remote) SPIs for CONS

Number Type N-selectors

1 Local 00

2 Remote 00

AEN Service type SPI

<ne>0<ccccc> CMISE/FTAM 03010100

<ne>0<ccccc>PAD PAD 01000000

<ne>0<ccccc>MSW MSW C0000000

Service application type Channel group SPI

CMISE/FTAM OMCCMISE 03010100

PAD OMCPAD 01000000

PAD RTRPAD1 01000000

MSW OMCMSW C0000000



NTC TAN 0839/2.2 en176

2 NETWORK PROTOCOL ADDRESS NAMES

This chapter presents the recommendations for naming network protocol addressnames in the DX 200 network elements.

2.1 CLNS network protocol address names

DX 200 (local) network protocol address names

Table 47.DX 200 (local) network protocol address names

NMS (remote) network protocol address names

Table 48.NMS (remote) network protocol address names

Note:

When creating CLNS network protocol address names, allPAD andMSW networkprotocol address names must be different. To ensure these names are differentuse the numbering scheme presented above.

Application type Abbreviation Local network address name

CMISE A/BP/EHA/SW LOCAL

FTAM F/FP LOCAL

VT VT LOCAL

PAD - (using X.25) PAD LOCALPAD1

MSW - (using X.25) MSW LOCALMSW1

Application type Abbreviation Remote network addressname

CMISE A/BP/EHA/SW REMNMS

FTAM F/FP REMNMS

VT VT REMNMS

PAD - (using X.25) PAD REMPAD1

PAD - (using X.25) PAD REMPAD2

MSW - (using X.25) MSW REMMSW1

MSW - (using X.25) MSW REMMSW2



NTC TAN 0839/2.2 en177

2.2 CONS network protocol address names

DX 200 (local) network protocol address names

Table 49.DX 200 (local) network protocol address names

NMS (remote) network protocol address names

Table 50.NMS (remote) network protocol address names

Note:

When creating CONS network protocol address names, allPAD andMSW networkprotocol address names must be different. To ensure these names are differentuse the numbering scheme presented above.

Application type Abbreviation Local network address name

CMISE A/BP/EHA/SW LOCALCMI

FTAM F/FP LOCALCMI

PAD PAD LOCALPAD1

PAD PAD LOCALPAD2

MSW MSW LOCALMSW1

MSW MSW LOCALMSW2

Application type Abbreviation Remote network address name

CMISE A/BP/EHA/SW REMCMI

FTAM F/FP REMCMI

PAD PAD REMPAD1

PAD PAD REMPAD2

MSW MSW REMMSW1

MSW MSW REMMSW2



NTC TAN 0839/2.2 en178

3 APPLICATION PARAMETERS

This chapter presents the parameters for creating the remote and localapplications in the DX 200 network elements and the NMS CommunicationsServer.

3.1 DX 200 applications

This section presents the DX 200 (local) application parameters for applicationsin DX 200 network elements.

3.1.1 DX 200 applications in the BSC

Table 51.DX 200 (local) applications in the BSC

Note:

In S6 the family for theBSC0<ccccc>EHA application is2B1.

Table 52.DX 200 (local) applications in the BSC

Item AEN Unit Type Family Network service

1 BSC0<bbbbb>F OMU VFS - CONS/CLNS

2 BSC0<bbbbb>VT OMU VTP - CONS/CLNS

3 BSC0<bbbbb>A OMU CMI 21F CONS/CLNS

4 BSC0<bbbbb>EHA OMU CMI 2B1 CONS/CLNS

5 BSC0<bbbbb>MSW OMU MSW - CONS/CLNSusing X.25

6 BSC0<bbbbb>PAD OMU PAD - CONS/CLNSusing X.25

Item AEN P-selectors S-selectors T-selectors

1 BSC0<bbbbb>F 1133030210 1133030210 1133

2 BSC0<bbbbb>VT 2233030220 2233030220 2233

3 BSC0<bbbbb>A 3333030230 3333030230 3333

4 BSC0<bbbbb>EHA 3333030231 3333030231 3333

5 BSC0<bbbbb>MSW - - -6 BSC0<bbbbb>PAD - - -



NTC TAN 0839/2.2 en179

3.1.2 DX 200 applications in the DAXnode WLL

Table 53.DX 200 (local) applications in the DAXnode WLL

Table 54.Local X.25 applications in the DAXnode WLL

Table 55.DX 200 (local) applications in the DAXnode WLL

Table 56.Local X.25 applications in the DAXnode WLL


1 BSC0<bbbbb>F OMU VFS - CONS/CLNS

2 BSC0<bbbbb>VT OMU VTP - CONS/CLNS

3 BSC0<bbbbb>A OMU CMI 21F CONS/CLNS

4 BSC0<bbbbb>EHA OMU CMI 2B1 CONS/CLNS


5 BSC0<bbbbb>MSW OMU MSW - CONS/CLNSusing X.25

6 BSC0<bbbbb>PAD OMU PAD - CONS/CLNSusing X.25


1 BSC0<bbbbb>F 1133030210 1133030210 1133

2 BSC0<bbbbb>VT 2233030220 2233030220 2233

3 BSC0<bbbbb>A 3333030230 3333030230 3333

4 BSC0<bbbbb>EHA 3333030231 3333030231 3333


5 BSC0<bbbbb>MSW - - -

6 BSC0<bbbbb>PAD - - -



NTC TAN 0839/2.2 en180

3.1.3 DX 200 applications in the MSC

Table 57.DX 200 (local) applications in the MSC

Table 58.Local X.25 applications in the MSC

Table 59.DX 200 (local) applications in the MSC

Table 60.Local X.25 applications in the MSC


1 MSC0<mmmmm>FO OMU VFS - CONS/CLNS

2 MSC0<mmmmm>VT OMU VTP - CONS/CLNS

3 MSC0<mmmmm>A OMU CMI 21F CONS/CLNS

4 MSC0<mmmmm>EHAOMU CMI 1F9 CONS/CLNS


5 MSC0<mmmmm>MSWBDCU MSW - CONS/CLNSusing X.25

6 MSC0<mmmmm>PADOMU PAD - CONS/CLNSusing X.25


1 MSC0<mmmmm>FO 1133040210 1133040210 1133

2 MSC0<mmmmm>VT 2233040220 2233040220 2233

3 MSC0<mmmmm>A 3333040230 3333040230 3333

4 MSC0<mmmmm>EHA3333040231 3333040231 3333


5 MSC0<mmmmm>MSW - - -

6 MSC0<mmmmm>PAD - - -



NTC TAN 0839/2.2 en181

3.1.4 DX 200 applications in the HLR

Table 61.DX 200 (local) applications in the HLR

Table 62.Local X.25 applications in the HLR

Table 63.DX 200 (local) applications in the HLR

Table 64.Local X.25 applications in the HLR


1 HLR0<hhhhh>FO OMU VFS - CONS/CLNS

2 HLR0<hhhhhh>VT OMU VTP - CONS/CLNS

3 HLR0<hhhhh>A OMU CMI 21F CONS/CLNS

4 HLR0<hhhhh>EHA OMU CMI 1F9 CONS/CLNS


5 HLR0<hhhhh>MSW BDCU MSW - CONS/CLNSusing X.25

6 HLR0<hhhhh>PAD OMU PAD - CONS/CLNSusing X.25


1 HLR0<hhhhh>FO 1133040210 1133040210 1133

2 HLR0<hhhhhh>VT 2233040220 2233040220 2233

3 HLR0<hhhhh>A 3333040230 3333040230 3333

4 HLR0<hhhhh>EHA 3333040231 3333040231 3333


5 HLR0<hhhhh>MSW - - -

6 HLR0<hhhhh>PAD - - -



NTC TAN 0839/2.2 en182

3.1.5 DX 200 applications in the Front End

Table 65.DX 200 (local) applications and their units in the Front End

Table 66.DX 200 (local) applications in the Front End

Table 67.DX 200 (local) applications for CONS communications in the FE

Item AEN Unit Type Family

1 OMC0<ccccc>FO OMU VFS -

2 OMC0<ccccc>VT OMU VTP -

3 OMC0<ccccc>FP OMU VFS -

4 OMC0<ccccc>EHA OMU CMI 1F9

5 OMC000000MSW0 BDCU MSW -

6 OMC000000MSW1 BDCU MSW -

7 OMC0<ccccc>FF FCMU VFS -

8 OMC000000PAD OMU PAD -


1 OMC0<ccccc>FO 1133020210 1133020210 1133

2 OMC0<ccccc>VT 2233020220 2233020220 2233

3 OMC0<ccccc>FP 1133021B10 1133021B10 1133

4 OMC0<ccccc>EHA 3333020231 3333020231 3333

5 OMC000000MSW0 - - -

6 OMC000000MSW1 - - -

7 OMC0<ccccc>FF 1133021C10 1133021C10 1133

8 OMC000000PAD - - -

Item AEN Application Local network address

5 OMC000000MSW0 MSW LOCALMSW0

6 OMC000000MSW1 MSW LOCALMSW1

8 OMC000000PAD PAD LOCALPAD



NTC TAN 0839/2.2 en183

3.2 NMS applications

This section presents the NMS (remote) applications in DX 200 network elementand the NMS.

3.2.1 NMS applications in DX 200 network elements

Table 68.NMS (remote) applications in DX 200 network elements

Item AEN Type P-selectors S-selectors T-select

1 OMC000000D1 CMI 3333010130 3333010130 3333

2 OMC000000BP CMI 3333010131 3333010131 3333

3 OMC000000FP VFS 1133010210 1133010210 1133

4 OMC000000SW VFS 1133010110 1133010110 1133

5 CISCOPAD PAD - - -



NTC TAN 0839/2.2 en184

3.2.2 DX 200 applications in the Communications Server

The following tables present the NMS applications for the DX 200 networkelements.

Table 69.DX 200 (local) applications for the NMS Communications Server

NE AEN P-selectors S-selectors T-sel

BSC BSC0<bbbbb>F 1133030210 1133030210 1133

BSC0<bbbbb>VT 2233030220 2233030220 2233

BSC0<bbbbb>A 3333030230 3333030230 3333

BSC0<bbbbb>EHA 3333030231 3333030231 3333

DAXnodeWLL

BSC0<bbbbb>F 1133030210 1133030210 1133

BSC0<bbbbb>VT 2233030220 2233030220 2233

BSC0<bbbbb>A 3333030230 3333030230 3333

BSC0<bbbbb>EHA 3333030231 3333030231 3333

MSC MSC0<mmmmm>FO 1133040210 1133040210 1133

MSC0<mmmmm>VT 2233040220 2233040220 2233

MSC0<mmmmm>A 3333040230 3333040230 3333

MSC0<mmmmm>EHA3333040231 3333040231 3333

HLR HLR0<hhhhh>FO 1133040210 1133040210 1133

HLR0<hhhhhh>VT 2233040220 2233040220 2233

HLR0<hhhhh>A 3333040230 3333040230 3333

HLR0<hhhhh>EHA 3333040231 3333040231 3333

FE OMC0<ccccc>FO 1133020210 1133020210 1133

OMC0<ccccc>FP 1133021B10 1133021B10 1133

OMC0<ccccc>FF 1133021C10 1133021C10 1133

OMC0<ccccc>VT 2233020220 2233020220 2233

OMC0<ccccc>EHA 3333020231 3333020231 3333



NTC TAN 0839/2.2 en185

Table 70.NMS processes/application types for remote applications

NE AEN NMS process Application type

BSC BSC0<bbbbb>F oufmanmx1 VFS

BSC0<bbbbb>VT ouvmanmx1 VTP

BSC0<bbbbb>A oummanmx1 CMI

BSC0<bbbbb>EHA oummanmx1 CMI

DAXnodeWLL

BSC0<bbbbb>F oufmanmx1 VFS

BSC0<bbbbb>VT ouvmanmx1 VTP

BSC0<bbbbb>A oummanmx1 CMI

BSC0<bbbbb>EHA oummanmx1 CMI

MSC MSC0<mmmmm>FO oufmanmx1 VFS

MSC0<mmmmm>A oummanmx1 CMI

MSC0<mmmmm>VT ouvmanmx1 VTP

MSC0<mmmmm>EHA oummanmx1 CMI

HLR HLR0<hhhhh>FO oufmanmx1 VFS

HLR0<hhhhhh>VT ouvmanmx1 VTP

HLR0<hhhhh>A oummanmx1 CMI

HLR0<hhhhh>EHA oummanmx1 CMI

FE OMC0<ccccc>FO oufmanmx1 VFS

OMC0<ccccc>FP oufmanmx1 VFS

OMC0<ccccc>FF oufmanmx1 VFS

OMC0<ccccc>VT oufmanmx1 VT

Appendix G. Connection Server processes


NTC TAN 0839/2.2 en186

Appendix G. CONNECTION SERVER PROCESSES

1 CS SERVER PROCESS

The CS server process (c4xcsxmx ) runs in the NMS Communications Server.Only one instance of this server process is active at a time.

PSMs and APMs run in workstations that have connections to the managednetwork (the Communications Server and the Database Server). The clientprocesses (for example, remote MML applications) run on any server in theNMS workstation network.

After start-up, one server process and a number of APMs are started in theworkstation network. The server process listens to its dedicated port, ready toserver connection requests. It is the only process in the NMS that knows thestructure of the DCN and its current connection status. All connection requestsmust pass through this server process. The Connection Server process does notestablish physical connections - it only keeps track of the available routes withinthe network.

The physical routes are administered by APMs that check if the DCN is usable.An APM can disable or enable routes by informingc4xcsxmx about route statuschanges. Based on this information,c4xcsxmx can enable and disable routes inits internal book-keeping.



NTC TAN 0839/2.2 en187

CS server process architecture

After Communications Server (host) is booted for the first time and thewpmanamx process starts:

1. The c4xcsxmx server process starts and reads the connection serverconfiguration file (cnxcffmx.cf ).

2. The c4xcsxmx server process reads the dcn configuration file(cnxdcnmx.cf ).

3. wpmanamx process begins to supervise thec4xcsxmx server process.

4. The APM process starts, seeAdministrative protocol moduleson page 188.If there administrate routes are not defined or commented out, APMs arenot used.

5. Thec4xcsxmx server process writes log entries to thec4xcsxmx.log.In the event of errorswerlog4006.log is also written.

6. The client makes a connection request.

7. The PSM application process begins, seeProtocol specific modulesonpage 190.

Figure 28.Connection Server processes



NTC TAN 0839/2.2 en188

2 ADMINISTRATIVE PROTOCOL MODULES

Administrative Protocol Modules (APMs) are perl checkscripts that verify ifthe physical connection to the host is in working order and if it can establish aconnection to a specific protocol. APMs are activated when the Nokia NMS isstarted and remain active as background processes. These checkscripts are listedin the administrative route definitions section of thecnxdcnmx.cfconfiguration file.

Thec6xapmmx process handles all APMs. The different functions of the APMsare implemented by.perl scripts started by thec6xapmmx main process. Fourcheckscripts are provided with the Nokia NMS:

Table 71.Administrative protocol modules

Note:

APMs run on all servers that contain network cards.

Figure 29.APM process path

Checkscript Purpose

c6xx25statmx.perl Checks PAD connection in the NMS

c6xconmx.perl Checks PAD connection in the NMS and DXelement

c6xftamx.perl Checks FTAM connection in the NMS

c6xvtxmx.perl Checks OSI VT connection in the NMS



NTC TAN 0839/2.2 en189

Application protocol module process path using a PAD connection

After the NMS has been started, APMs use the following process path whenmonitoring PAD connections. These modules constantly check the status of thenetwork at a user specified interval.

1. During NMS start-up, thec4xcsxmx server process also starts and opensthecnxdcnmx.cf configuration file.

2. The c4xcsxmx server process reads the arc, route and administrativeroute definitions for all PAD connections from thecnxdcnmx.cf .

3. Thec4xcsxmx processes that information and sends a request out to theinetd daemon.

4. The inetd daemon starts. Knowing the connection type (PAD) and allpossible routes,inetd starts thec6xapmmx process (APM main process).

5. Thec6apmmx process reads thecnxcffmx.cf configuration file.

6. Thec6apmmx process writes the required log file(s).

7. The c6apmmx process then runs a protocol-specific checkscript(c6xconmx.perl ) to test the PAD connection.

8. If the PAD connection is OK, a message indicating that the connection isfunctional is returned to the APM main process.

9. The c6xapmmx process forwards the message to thewnemgrmx(Workstation Communications Services) process.

10. Thewnemgrmx process forwards the message to thec4xcsxmx serverprocess.

If a route is found to be inoperable, the APM sends a negative message to theserver process. This generates a workstation alarm and causes an error log file tobe written.

The APM then continues checking the connection at pre-defined intervals. Whenthe route becomes available again, the APM sends another message indicatingthe status of the connection.

If the APM sends a message concerning a malfunction in a data communicationcard, the server process disables all routes to that card. After the malfunction hasbeen corrected, the APM enables all routes to that card and forwards thatinformation to the CS process.



NTC TAN 0839/2.2 en190

3 PROTOCOL SPECIFIC MODULES

Protocol specific modules (PSMs) implement connections to applications. ThreePSMs are provided with Nokia NMS:

Table 72.Protocol-specific modules

Note:

Telnet connections are enabled by using thec5xstdmx PSM.

To implement FTAM or OSI VT connections, the use of host processes isnecessary. As thec5xpadmx uses the X.25 host service module for PADconnections, no additional processes are needed. The implementation of eachconnection is totally transparent to the client application.

Figure 30.PSM application process using a PAD connection

Protocol specific module PSM process Protocol

c5xpadmx - PAD

c5xftamx oulfcpmx FTAM

c5xstdmx ouiswsmx OSI VT



NTC TAN 0839/2.2 en191

PSM application processes using a PAD connection

1. A client in the Nokia NMS sends a connection request to thec4xcsxmxserver process. This requests includes the name or internal ID of host(BSC) and the type of connection desired (PAD).

2. Thec4xcsxmx server process accepts the request, searches for the hostand reads the routing information in thecnxdcnmx.cf configuration file.

3. Thec4xcsxmx processes that information and sends a request out to theinetd daemon.

4. Theinetd daemon starts. Knowing the host, connection type and route,inetd starts thec5xpadmx process (PSM PAD process).

5. Thec5xpadmx PAD process reads thecnxcffmx.cf configuration file.

6. Thec5xpadmx PAD process starts

7. Inetd passes that information to the server process.

8. The server process passes that information to the client (Nokia NMS).

9. The client makes a connection, through the PSM, to the network element(BSC) and begins sending data.

10. Thec5xpadmx PAD process reads thelogin/logout system files.

Note:

If errors occur,werlog5011.log is automatically written by the PSM.

3.1 Session logs

PSMs also produce optional session logs of the connections. Session logsprovide information on who established a connection, what the connection wasused for and how long the connection was active.

If this feature is enabled, the PSM that makes the connection produces a sessionlog file (c5xpmx_<conn_ID>.log .). The<conn_ID> variable identifies theindividual connection.

To enable this feature, edit the node definitions section of thecnxdcnmx.cffile. This feature is network element and connection type specific and a log fileis produced for each connection.

Symbols

/etc/services 62


NTC TAN 0839/2.2 en192

INDEX

A

AC25-Sinstalling and configuring 83jumpers 145

addressdevice information 66network protocol 111

administrative protocol modules 188c6xconmx.perl 188c6xftamx.perl 188c6xvtxmx.perl 188c6xx25statmx.perl 188

administrative routes 72AENs 120, 128, 175APM checkscripts

c6xconmx.perl 188c6xftamx.perl 188c6xvtxmx.perl 188c6xx25statmx.perl 188

APMs 72, 188application entity names 120, 128, 175arcs

naming 67AS7-U

installing and configuring 89jumpers 150

B

backupsDCN configuration files 61

BBU-0 140BSS integration

required managed objects 30byte basket 140

C

c4xcsxmx 186checkscripts 188

c6xconmx.perl 188c6xftamx.perl 188c6xvtxmx.perl 188c6xx25statmx.perl 188

CLNSover X.25 39

setting up objects in NE 104setting up subnetworks 38

clusters 43cnxcffmx.cf 65cnxdcnmx.cf 61cnxreconfigmx.perl 78COCEN

installing and configuring 100jumpers 155

comm package 43when used 44

communication modesdirect connections 144indirect connections 144

Communications Serverpackage 43

configuration filescnxdcnmx.cf 59Connection Server 65inetd.conf 63osi 57ots_dests 49ouorapmx.cf 56

Connection Serverenvironment 65processes 186

connection subtypes 76creating physical channels

using PCM over digital X.25 98

D

DCNconfiguration files 61introduction 16

diagnos 140documents 15

Hewlett Packard 15installation guides 15introductory 15reference guides 15system administrator guides 15troubleshooting guides 15

DX 200configuring 79

dynamic NSAPs 44


NTC TAN 0839/2.2 en193

E

end system connectionsadding to Front End 142

error logswerlog4006.log 187werlog5011.log 191

evbfil 136exchange terminals

installing and configuring 92

F

figuresadmin route in cnxdcnmx.cf 73APM processes 188arc in cnxdcnmx.cf 68basic DCN integration 22comm package NSAP address 43creating local CLNS applications 123creating local CONS applications 120creating remote OSI applications 132CS processes 187direct integration CONS 20direct NE integration (CLNS) 18indirect NE integration (CLNS) 19network cards in DX 200 23PSM processes 190route in cnxdcnmx.cf 70Setting up DX 200 connections 80

flowchartsOSI application configuration 118preliminary tasks 25

FTAM 66checking 188

G

gsmme1mg 138

H

hostnames 164, 165, 167

I

inetd 63Internet superserver 63interrogation commands

hostnames 164, 165, 167network protocol addresses 110, 114NSAPs 110, 114

O&M connections data 131

J

jumpersAC25-S 145AS7-U 151COCEN 155

L

linkage objectsbroadcast 105setting up in the NE 105unlocking 106

local OSI applicationssetting up in the NE 119

M

managed objectsBSS integration 30creating 30NSS integration 30

manual adjacenciesadding 107

MC/ServiceGuard 44meafil 136, 139mscmea01mg 138

N

network addressessetting up for CONS 113

network cardsAC25-S 145AS7-U 150COCEN 154

network protocol addressescreating 108, 113

network servicessetting up in NE 103setting up using CLNS 104setting up using CONS 46, 112

NMS Communications Serverconfiguring 34

nodes 43adding definitions 74adoptive 44primary 44

NSAPsattaching 111


NTC TAN 0839/2.2 en194

dynamic 44setting up for CONS 113unlocking 111

NSS integrationrequired managed objects 30

NULL subaddressing 58

O

O&M connectionsadding 130

obsfil 136, 138omcalarm 140OSI

transport services 66OSI destination systems

adding 48OSI environment

configuring 52configuring in the NE 118

OSI subnetworksetting up in Communications Server 37

OSI VTchecking 188

osiadmin 35osiconfchk 51ots_dests 49ots_routes 51ots_subnets 58ouorapmx.cf 56, 57

P

packagescomm 43

PADchecking 188connections 70setting up in the NMS 53

physical channels 87assigning a channel group using analog

X.25 88, 99creating using analog X.25 87

physical connectionssetting up in DX 200 80setting up in the NE using LAN 100setting up using analog X.25 (PSN) 80setting up using digital X.25 (PCM) 89verifying in the NE 88

plug-in unitsAC25-S 145AS7-U 150

COCEN 154prerequisites

MSC/HLR 28, 29NMS 27

protocol-specific modules 190c5xftamx 190c5xpadmx 190c5xstdmx 190

PSM processesouiswsmx 190oulfcpmx 190

PSMs 190c5xftamx 190c5xpadmx 190c5xstdmx 190

R

references 15remote applications

setting up 56routes

adding 70administrative 72naming 67

routing tables 44

S

session logs 191c5xpmx_.log 191

sgscusmx.cf 43software

M7B 134, 135, 136SPIs 108, 113states

changing 131

T

tablesrouting 44

U

unlockinglinkage objects 106NSAPs 111

V

virtual


NTC TAN 0839/2.2 en195

report converter 140VRP-0 140

W

werlog4006.log 78

X

X.25initialization file 165

X.25 parameter setscreating and modifying 86, 97

X.29hosts file 53server 55

x25config_* 165

Z

ZIIL 136, 137ZIIS 136ZQDI

APL=LCL 121, 124ZUSU 141


NTC TAN 0839/2.2 en196

Documents

DCN Integration