DCN Integration PDF

NOKIA NMS/2000
FOR MANAGING CELLULAR NETWORKS
DCN INTEGRATION
Installation Guide
Document number/Issue
NTC TAN 0839/2.2 en
Copyright Nokia Telecommunications Oy
The information in this document is subject to change without notice and describes only the product defined
in the introduction of this documentation. This document is intended for the use of Nokia
Telecommunications' customers only for the purposes of the agreement under which the document is
submitted, and no part of it may be reproduced or transmitted in any form or means without the prior written
permission of Nokia Telecommunications. The document has been prepared to be used by professional and
properly trained personnel, and the customer assumes full responsibility when using it. Nokia
Telecommunications welcomes customer comments as part of the process of continuous development and
improvement of the documentation.
The information or statements given in this document concerning the suitability, capacity, or performance of
the mentioned hardware or software products cannot be considered binding but shall be defined in the
agreement made between Nokia Telecommunications and the customer. However, Nokia
Telecommunications has made all reasonable efforts to ensure that the instructions contained in the
document are adequate and free of material errors and omissions. Nokia Telecommunications will, if
necessary, 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 of
errors. Nokia Telecommunications WILL NOT BE RESPONSIBLE IN ANY EVENT FOR ERRORS IN THIS
DOCUMENT OR FOR ANY DAMAGES, INCIDENTAL OR CONSEQUENTIAL (INCLUDING MONETARY
LOSSES), 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 the
applicable laws.
NOKIA logo is a registered trademark of Nokia Corporation.
Other product names mentioned in this document may be trademarks of their respective companies, and
they are mentioned for identification purposes only.
Copyright Nokia Telecommunications Oy 1998. All rights reserved.
No. of
pages
195/TJa
Edited by
Author
Approved by
T Jara
5 Oct 1998
T Jara
5 Oct 1998
J Nummikoski
6 Oct 1998
Previous issue
(2.1) approved
23 July 1998
Copyright Nokia Telecommunications Oy 1998. All rights reserved.
NTC TAN 0839/2.2 en
TABLE OF CONTENTS
1
WHAT IS NEW. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7
1.1
ABOUT THIS MANUAL . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8

2.1
2.2
2.3
2.4
2.5
3.4
3.5
Integration principles . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Network topologies . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Network services . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
3.3.1
Connectionless network service. . . . . . . . . . . . . . . . . . . . . . . . . .
3.3.2
Connection-oriented network service . . . . . . . . . . . . . . . . . . . . .
Integration procedures . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Hardware . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
3.5.1
Network cards . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
3.5.1.1 AC25-S. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
3.5.1.2 AS7-U . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
3.5.1.3 COCEN . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
3.5.2
Intermediate systems . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
3.5.2.1 Nokia NMS Front End . . . . . . . . . . . . . . . . . . . . . . . . . .
3.5.2.2 Cisco routers . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
17
17
17
18
20
22
23
23
23
23
23
24
24
24
PRELIMINARY TASKS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 25
4.1
4.2
4.3
4.4
4.5
What you need to know first . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8

How to use this manual . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9
Concepts and terminology . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9
Typographic conventions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12
2.4.1
Text styles . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12
2.4.2
Command line conventions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13
Where to find more . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15
INTRODUCTION TO DCN INTEGRATION. . . . . . . . . . . . . . . . . . . 16

3.1
3.2
3.3
Changes from T9 to T10 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7
Filling in the configuration sheets . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Reviewing the system requirements. . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
4.2.1
NMS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
4.2.2
BSC . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
4.2.3
MSC/HLR . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Creating managed objects in the NMS. . . . . . . . . . . . . . . . . . . . . . . . . . . .
Creating and modifying user group profiles . . . . . . . . . . . . . . . . . . . . . . .
Creating and modifying user IDs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
26
27
27
28
29
30
31
32
CONFIGURING THE NMS COMMUNICATIONS SERVER. . . . . 34

5.1
5.2
Enabling X.121 subaddressing. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Setting up the OSI subnetwork . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
5.2.1
Using CLNS. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
5.2.1.1 Setting up a CLNS subnetwork for X.25 . . . . . . . . . . . .
5.2.1.2 Setting up a CLNS subnetwork for LAN. . . . . . . . . . . .
NTC TAN 0838/2.2 en
35
37
38
39
41
3
5.3
5.2.1.3 Communications Server package. . . . . . . . . . . . . . . . . .

5.2.1.4 Adding the comm package NSAP . . . . . . . . . . . . . . . . .
5.2.2
Using CONS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
5.2.3
Adding an ISO OSI destination . . . . . . . . . . . . . . . . . . . . . . . . . .
5.2.4
Adding an IS as an ISO OSI destination . . . . . . . . . . . . . . . . . . .
5.2.5
Adding a default route . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Configuring OSI applications and addresses . . . . . . . . . . . . . . . . . . . . . . .
5.3.1
Setting up PAD services . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
5.3.1.1 PAD service for outgoing connections. . . . . . . . . . . . . .
5.3.1.2 PAD service for incoming connections . . . . . . . . . . . . .
5.3.2
Setting up DX 200 OSI applications . . . . . . . . . . . . . . . . . . . . . .
5.3.3
Configuring OSI protocol identifiers . . . . . . . . . . . . . . . . . . . . . .
CONFIGURING CONNECTION SERVER SOFTWARE . . . . . . . . 59

6.1
6.2
6.3
6.4
6.5
6.6
6.7
6.8
6.9
6.10
Backing up the DCN configuration file . . . . . . . . . . . . . . . . . . . . . . . . . . .

Editing the /etc/services file . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Configuring the inetd daemon . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Editing the Connection Server configuration file . . . . . . . . . . . . . . . . . . .
Address device information . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Naming arcs and routes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Adding an arc to a remote system . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Adding a route to a remote system. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Adding an administrative route to a remote system. . . . . . . . . . . . . . . . . .
Adding a node definition to a remote system. . . . . . . . . . . . . . . . . . . . . . .
6.10.1 Determining connection subtypes . . . . . . . . . . . . . . . . . . . . . . . .
6.11 Re-reading the configuration file . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
6.12 Verifying DCN integration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
43
44
46
48
50
51
52
53
53
54
56
58
61
62
63
65
66
67
68
70
72
74
76
77
78
CONFIGURING THE DX 200 NETWORK ELEMENT . . . . . . . . . . 79

7.1
7.2
Setting up the physical connection. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 80

7.1.1
Using analog X.25 (PSN). . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 81
7.1.1.1 Installing and configuring an AC25-S card . . . . . . . . . . 83
7.1.1.2 Setting the physical layer parameters . . . . . . . . . . . . . . 85
7.1.1.3 Creating and modifying the X.25 parameter set . . . . . . 86
7.1.1.4 Creating a physical channel . . . . . . . . . . . . . . . . . . . . . . 87
7.1.1.5 Assigning a channel group to a physical channel . . . . . 88
7.1.1.6 Verifying the physical connection . . . . . . . . . . . . . . . . . 88
7.1.2
Using digital X.25 (PCM) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 89
7.1.2.1 Installing and configuring an AS7-U card . . . . . . . . . . . 89
7.1.2.2 Installing and configuring an Exchange Terminal . . . . . 92
7.1.2.3 Setting up the semipermanent connections . . . . . . . . . . 95
7.1.2.4 Creating and modifying the X.25 parameter set . . . . . . 97
7.1.2.5 Creating a physical channel . . . . . . . . . . . . . . . . . . . . . . 98
7.1.2.6 Assigning a channel group to a physical channel . . . . . 99
7.1.2.7 Verifying the physical connection . . . . . . . . . . . . . . . . . 99
7.1.3
Using a LAN . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 100
7.1.3.1 Installing and configuring a COCEN card . . . . . . . . . . 100
Setting up the OSI subnetwork . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 103
NTC TAN 0839/2.2 en
7.2.1
7.3
Using CLNS. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
7.2.1.1 Setting up a CLNS object . . . . . . . . . . . . . . . . . . . . . .
7.2.1.2 Setting up a linkage object. . . . . . . . . . . . . . . . . . . . . .
7.2.1.3 Adding manual adjacencies . . . . . . . . . . . . . . . . . . . . .
7.2.1.4 Creating NSAPs and network protocol addresses . . . .
7.2.1.5 Attaching NSAPs to network protocol addresses . . . .
7.2.2
Using CONS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
7.2.2.1 Creating NSAPs and network protocol addresses . . . .
7.2.2.2 Attaching NSAPs to network protocol addresses . . . .
Configuring OSI applications and addresses . . . . . . . . . . . . . . . . . . . . . .
7.3.1
Setting up local PAD and MSW applications . . . . . . . . . . . . . .
7.3.2
Setting up local OSI applications. . . . . . . . . . . . . . . . . . . . . . . .
7.3.3
Defining the CMISE service profile . . . . . . . . . . . . . . . . . . . . .
7.3.4
Setting up the remote PAD and MSW applications. . . . . . . . . .
7.3.5
Adding an O&M connection . . . . . . . . . . . . . . . . . . . . . . . . . . .
7.3.6
Setting up remote applications. . . . . . . . . . . . . . . . . . . . . . . . . .
7.3.7
Changing power measurements levels in a BSC . . . . . . . . . . . .
7.3.8
Adding new counters in a BSC . . . . . . . . . . . . . . . . . . . . . . . . .
7.3.9
Setting up logical files in the MSC/HLR . . . . . . . . . . . . . . . . . .
104
104
105
107
108
111
112
113
116
118
119
122
125
128
130
132
134
135
136
CONFIGURING INTERMEDIATE SYSTEMS . . . . . . . . . . . . . . . . 142
VERIFYING DCN INTEGRATION . . . . . . . . . . . . . . . . . . . . . . . . . 143
AC25-S NETWORK CARD. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 145

1.1
1.2
1.3
1.4
146
147
148
149
AS7-U NETWORK CARD. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 150

2.1
2.2
2.3
2.4
Jumper blocks. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Memory space addresses . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Interchangeability codes. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Communication modes. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Jumper blocks. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Memory space addresses . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Interchangeability codes. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Memory size. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
151
151
152
153
COCEN NETWORK CARD . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 154

3.1
3.2
3.3
Jumper blocks. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 155

Memory space addresses . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 155
Interchangeability codes. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 156
CABLES. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 157
SERVERS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 160
NETWORK ELEMENTS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 162
SERVER WORKSHEET . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 164
NTC TAN 0839/2.2 en
NETWORK ELEMENT WORKSHEET . . . . . . . . . . . . . . . . . . . . . . 167
PRELIMINARY TASKS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 170
CONFIGURING THE NMS COMMUNICATIONS SERVER. . . . 171
CONFIGURING OSI APPLICATIONS . . . . . . . . . . . . . . . . . . . . . . 172
CONFIGURING THE CONNECTION SERVER SOFTWARE . . 173
CONFIGURING THE DX 200 NETWORK ELEMENT . . . . . . . . . 174
N - SELECTORS AND SPIS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 175

1.1
1.2
NETWORK PROTOCOL ADDRESS NAMES. . . . . . . . . . . . . . . . . 176

2.1
2.2
N - selectors for CLNS communications . . . . . . . . . . . . . . . . . . . . . . . . . 175

SPIs for CONS communications . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 175
CLNS network protocol address names . . . . . . . . . . . . . . . . . . . . . . . . . . 176

CONS network protocol address names . . . . . . . . . . . . . . . . . . . . . . . . . 177
APPLICATION PARAMETERS . . . . . . . . . . . . . . . . . . . . . . . . . . . . 178

3.1
3.2
DX 200 applications. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
3.1.1
DX 200 applications in the BSC . . . . . . . . . . . . . . . . . . . . . . . .
3.1.2
DX 200 applications in the DAXnode WLL . . . . . . . . . . . . . . .
3.1.3
DX 200 applications in the MSC . . . . . . . . . . . . . . . . . . . . . . . .
3.1.4
DX 200 applications in the HLR . . . . . . . . . . . . . . . . . . . . . . . .
3.1.5
DX 200 applications in the Front End . . . . . . . . . . . . . . . . . . . .
NMS applications. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
3.2.1
NMS applications in DX 200 network elements . . . . . . . . . . . .
3.2.2
DX 200 applications in the Communications Server. . . . . . . .
178
178
179
180
181
182
183
183
184
CS SERVER PROCESS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 186
ADMINISTRATIVE PROTOCOL MODULES . . . . . . . . . . . . . . . . 188
PROTOCOL SPECIFIC MODULES . . . . . . . . . . . . . . . . . . . . . . . . . 190

3.1
Session logs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 191
INDEX. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 192
NTC TAN 0839/2.2 en
What is new
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 and
documentation between release T9 and T10.
Information regarding integration from a router or Front End to the NMS

has been moved to Integrating Intermediate Systems, TAN 0900.
Integration information regarding the DAXnode 5000 wireless local loop

has been added throughout the manual.
Section 4.2, Reviewing the system requirements on page 27 has been

added.
Section 5.2.1.3, Communications Server package on page 43 has been

added. This section includes information regarding the comm package
NSAP, MC/ServiceGuard and minor changes to the comm package
configuration instructions.
Section 6.8, Adding a route to a remote system on page 70 has been rewritten with interrogation commands.
Section 7.1.3.1, Installing and configuring a COCEN card on page 100 has
been re-written.
Section 7.3, Configuring OSI applications and addresses on page 118 has
been re-written with interrogation commands.
Section 7.3.9, Setting up logical files in the MSC/HLR on page 136 has
been re-written with new instructions regarding the Front End.
In Appendix A., Network card jumpers on page 144, all memory space
address tables have been modified.
In Appendix A, AC25-S network card on page 145, the memory start and
end addresses have been modified.
In Appendix C., Configuration information on page 160, all tables have

been modified.
In Appendix F., OSI Parameters on page 175, all tables have been
modified.
Appendix G., Connection Server processes on page 186 has been added.
NTC TAN 0839/2.2 en
About this manual
ABOUT THIS MANUAL

This document describes how to integrate the Network Subsystem (NSS) and the
Base Station Subsystem (BSS) with the Nokia NMS (release T10).
This document is primarily concerned with connections from the NMS to a
network element. Those connections can be made using analog X.25 (PSN),
digital X.25 (PCM) and/or LAN connections. For instructions regarding thirdparty router or Front End integration see, Integrating Intermediate Systems, TAN
0900.
Before beginning integration, read the first five chapters. After completing all
preliminary tasks, continue with Chapter 5, Configuring the NMS
Communications Server. As this manual was written in logical sequence, read
each chapter in the order presented.
If you are unfamiliar with connectionless (CLNS) and connection-oriented
(CONS) network services, see DCN Management, TAN 0377.
This customer document was written for the technical personnel of a
telecommunications operator. As this document was written specifically for
release T10, do not use this document to integrate other releases of the Nokia
NMS.
2.1
What you need to know first

Before using this manual, ensure you are competent in the following areas and
applications.
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 the omc, root, sysop and sysop1 users
X.121 and NSAP addresses for all network elements
NTC TAN 0839/2.2 en
About this manual
2.2
How to use this manual

Use this manual as a step-by-step guide when integrating the network subsystem
or base station subsystem with the Nokia NMS. If integrating network elements
using other installation manuals, refer to this manual when implementing DCN
solutions.
2.3
Concepts and terminology

This section provides a brief list of the terms used in this manual. If a term or
word does not appear in section please refer to the Glossary, 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 Module

A Connection Server process that verifies the
functionality 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 Service

Element
COCEN
DX 200 Ethernet card
Communication Server
A workstation running HP-UX that serves and

implements connections.
Connection Server
An NMS application that provides transparent

connections to clients and network elements.
CONS
Connection-oriented Network Service
DAXnode 5000 WLL

DAXnode WLL
A Digital Access Node for Wireless Local Loops

that supports 5000 subscribers.
DCE
Data Circuit-terminating Equipment
NTC TAN 0839/2.2 en
About this manual
Term
Explanation
DCN
Data Communications Network

A logical representation of the physical network
that connects network elements to the Nokia
NMS.
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 Management

A standard file transfer protocol that enables data
to be accessed in remote files. Parts or all of these
files 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. This

program allows you to set up and maintain OTS
9000.
OTS
HPs OSI Transport Services
OTS/9000
Hewlett-Packard's implementation of OSI

Transport Services and related protocols.
NTC TAN 0839/2.2 en
10
About this manual
Term
Explanation
PAD
Packet Assembler Disassembler
PCM
Pulse Code Modulation
PDE
Power Distribution Equipment
PID
Protocol Identifier
PIU
Plug-in Unit
PVC
Permanent Virtual Circuit

Permanent virtual circuits maintains permanent
associations.
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 Circuits

Switched virtual circuits maintain associations
only for the current connection call.
TSL
Time slot
V.24
ITU-T specification for connecting DTE (for

example, a PC) with DCE (for example, a modem)
V.35
ITU-T specification for modems for synchronous

data transmission
V.36
ITU-T specification for modems for synchronous

data transmission using 60-108kHz group band
circuits
V5.2
A dynamic multiplexer interface between a local

network and a separate subscriber network.
VT
Virtual Terminal
WLL
Wireless Local Loop
X.121
An international numbering plan for public data

networks. Each network element in a
telecommunications network has its own X.121
address.
X.121 address
The address assigned to each local X.25 card or

port
X.21
Interface between the DTE and the DCE for

synchronous operation on a data network
X.25
An interface between the DTE and the DCE in a

packet switched network using X.21 at the physical
layer.
Table 1. Terms and explanations
NTC TAN 0839/2.2 en
11
About this manual
2.4
Typographic conventions
Several typographical conventions are used in this manual to describe different
actions and restrictions. The following table presents those conventions.
2.4.1
Text styles
Style
Explanation
Initial Upper-Case
Application names
Hardware components
Names of windows and dialogs
Initial Upper-Case
in Italics
Referenced documents
Referenced sections and chapters within a
document
UPPER-CASE
Keys on the keyboard (ALT, TAB, CTRL etc.)
Italic
Emphasis
State, status or mode
Courier font
Bold
Graphical user interface components
<bracketed text>
Variable user input
Shaded box
Further information about command line

parameters
File and directory names

Names of database tables
Parameters
User names
System output
User input
Table 2. Text styles in this document
NTC TAN 0839/2.2 en
12
About this manual
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.
Prompt
User
Root user
username>%
User indicated by username.
Any user
>
Service terminal or MML prompt
Table 3. Command line prompts

Environment variables
This document assumes the following environment variables have the values
indicated below:
Variable
Value
$OMCCONFPATH
/usr/local/NokiaOMC/conf/global
$OMCROOT
/usr/local/<omc_build>
Table 4. Environment variables used in this document

Product delivery numbers
The following symbols are used to represent the C numbers (the delivery
numbers) of network elements:
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 in

the context of usage)
Table 5. Conventions for C numbers
NTC TAN 0839/2.2 en
13
About this manual
Line breaks
For layout purposes, long command lines may be split into two or more separate
lines. This is indicated as follows:
With UNIX commands and UNIX file descriptions, a backslash ( \ ) at the end
of a printed line is used to indicate that the command continues on the following
line. For example:
# cat /etc/cmcluster/pkgcomm/control.sh.log | grep \
"crontab" | more
With MML commands, everything between the initial Z 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 the
portion 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 single
units (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 the
portion 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 options
when you enter the command.
NTC TAN 0839/2.2 en
14
About this manual
2.5
Where to find more

During integration, you may need to refer to other documentation. Ensure these
manuals are available before beginning DCN integration.
Introductory documents
If you need information on other NMS manuals, see NMS/2000

Description of Documentation, TAN 0442.
Reference guides
For more infomation on terms used in this guide, see Glossary, TAN 0717.
For more information on hardware, Nokia NMS applications, processes

and configuration files, see Technical Reference Guide, TAN 0453.
Installation guides
For more information on NSAPs, DCN implementation and an overview

of DCN solutions, see DCN Management, TAN 0377.
For more information on integrating a router or the Nokia NMS Front End,
see Integrating Intermediate Systems, TAN 0900.
System administrators guides
For more information on rebooting the NMS, see Workstation Network

Maintainence, TAN 0513.
For more information on MC/ServiceGuard, see System Management

Basic Operating Principles and Procedures, TAN 0732.
System management online helps
For more information on using User Group Profiles, see User Group
Profiles Online Help, TAN 0713.
For more information on creating views and managed objects, see Network
Editor Online Help, TAN 0879.
Troubleshooting guides
For more information on DCN integration tests, see Testing Installations,

TAN 0523.
Hewlett Packard documentation
For more information on setting up PAD in the Communications Server,

see X.25/9000 Users Guide.
NTC TAN 0839/2.2 en
15
Introduction to DCN integration
INTRODUCTION TO DCN INTEGRATION

DCN integration represents a logical series of ordered tasks that bridge the gap
between network elements and the Nokia NMS.
Once DCN integration is completed, the Nokia NMS will be able to perform
configuration, fault and performance management functions from a centralised
location.
As DCN integration is a very complicated process, do not deviate from the order
that this information is presented. Attempts to follow advise contrary to what is
written in this guide may result in costly delays.
To successfully integrate a data communications network, familiarise yourself
with the logical models, principles and task sequences that are explained in this
and 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 are
configured and functioning correctly.
NTC TAN 0839/2.2 en
16
3.1
Integration principles
When integrating different systems, establish a means by which data is
transferred from one network element to the other. Communication in the Data
Communications Network (DCN) is based on the Open Systems Interconnection
(OSI) model.
This model defines a seven-layer structure for transferring data from one
network element to the other. For more information regarding OSI and DCN
principles, see DCN Management, TAN 0377.
3.2
Network topologies
The network topology defines whether you will connect a network element
directly to the NMS Communications Server (ES) or indirectly using a router or
Front End (IS).
This topology also defines the cabling layout of your network. Once the network
topology is defined, identify the network services (CONS or CLNS) and
protocols 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 and
transport layers. The network services available in an ISO OSI data
communications network are:
Connectionless network service
Connection-oriented network service
NTC TAN 0839/2.2 en
17
3.3.1
Connectionless network service
When using a connectionless network service (CLNS), communication is

established using the following types of networks:
Type of network
Type of connection from the Nokia NMS
Ethernet
Direct (NMS - network element)

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

Indirect (NMS - IS - network element)
Table 6. CLNS connections from the NMS

The Nokia NMS does not support digital X.25 (PCM) connections from the IS
to the NMS Communications Server. Digital X.25 (PCM) connections are only
possible 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-topoint or through an analog X.25 packet network.
The following figure illustrates how a network element is directly connected to
the NMS Communications Server using CLNS/LAN.
Figure 1. Direct network element integration (CLNS/LAN)
NTC TAN 0839/2.2 en
18
The following figure illustrates how a network element is indirectly connected

to 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, see

Integrating Intermediate Systems, TAN 0900.
NTC TAN 0839/2.2 en
19
3.3.2
Connection-oriented network service
When using a connection-oriented network service (CONS), communication is

established using the following type of network.
Type of network
Type of connection from the Nokia NMS
Analog X.25 (PSN)
Table 7. CONS connections from the NMS

The Nokia NMS does not support digital X.25 (PCM) connections from the
NMS Communications Server. Digital X.25 (PCM) connections are only
possible 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-point
connection or through an analog X.25 packet network.
the NMS Communications server using CONS/analog X.25 (PSN).
Figure 3. Direct network element integration CONS/analog X.25 (PSN)
NTC TAN 0839/2.2 en
20

the 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 intermediate
system
Figure 4. Direct network element integration CONS/analog X.25 (PSN)

NTC TAN 0839/2.2 en
21
3.4
Integration procedures
The basic integration procedures for DCN integration include performing the
tasks listed in the following table. When integrating an Intermediate System (IS),
refer to the instructions in Integrating Intermediate Systems, TAN 0900.
Task
NMS
Network
element
IS
(FE)
Set up the OSI subnetwork (CLNS/CONS)
Configure OSI applications and addresses
Edit Connection Server configuration files
Setting up the physical connection
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)

NTC TAN 0839/2.2 en
22
3.5
Hardware
3.5.1
Network cards
The network cards for integration are located in the Operations and Maintenance
Unit (OMU) of the BSC and in the Basic Data Communications Unit (BDCU) of
the 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 transmission

channels following the HDLC protocol to a microcomputer unit. AC25-S cards
are 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-U

cards are used for digital X.25 connections (PCM).
3.5.1.3
COCEN
COCEN cards are used for LAN connections. COCEN cards are connected using
10Base2 (coax), 10Base5 (AUI) or 10BaseT cable (twisted pair).
NTC TAN 0839/2.2 en
23
3.5.2
Intermediate systems
Due to a pre-existing network configuration, there may be an Intermediate

System (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 Communications
Server.
For more information regarding indirect connections using a router, see
Integrating 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 for
digital switching systems. It consists of processor units with Intel 386/486 based
microcomputers interconnected using a fast parallel bus.
The network management functions are concentrated in the Fault and
Configuration Management Units (FCMUs) of the microcomputers. The
FCMUs are duplicated to achieve better fault tolerance.
3.5.2.2
Cisco routers
Cisco routers consist of the router itself and Ciscos IOS software. Ciscos IOS
software provides a variety of feature sets. You can choose a feature set that
supports your specific protocol environment. This software supports both LAN
and WAN protocols, optimising WAN services and controlling internetwork
access. In addition, Ciscos IOS software allows centralised, integrated and
automated installation and management of internetworks.
NTC TAN 0839/2.2 en
24
Preliminary tasks
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
NTC TAN 0839/2.2 en
25
Preliminary tasks
4.1
Filling in the configuration sheets

Before beginning the integration, read Appendix C., Configuration information
on page 160 and make a copy of the worksheets on page 164. When filling in the
worksheets ensure the following information is specified:
Servers
Hardware
Role
Software
Hostname
Physical address (IP and/or X.121)
NSAPs addresses (physical and comm package)
Type of NSAPs
Network elements
Hardware
Role
Software
Hostname
Physical address (X.121-DTE)
NSAPs address
C-number
NTC TAN 0839/2.2 en
26
Preliminary tasks
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 following

requirements:
The T10 environment is tested and fully functional.
OSI Transport Services (OTS) is installed on the Communications and

Standby Servers.
NTC TAN 0839/2.2 en
27
Preliminary tasks
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
PACKAGE-ID (REP-ID)
ENVIRONMENT
DELIVERY
CD-ID
DEF ACT
S7000GEN
AS7_7_16_0
S7 7.16-0
S7 7.12-0
CID000SX 6.4-0
S7003GEN
S6REL
SX 6.16-0
SX 6.9-0
CID000SX 5.5-0
S6EME110
S7 7.12-0
CID000SX 5.5-0
S7002GEN
S6980703
S7002GEN
BU
NW
UT
AS7_7_16_0
S7 7.16-0
COMMAND EXECUTED
SOFTWARE PACKAGE ADMINISTRATION COMMAND <WQ_>
NTC TAN 0839/2.2 en
28
Preliminary tasks
4.2.3
MSC/HLR
Before beginning integration, ensure the MSC/HLR meet the following

requirements:
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
PACKAGE-ID (REP-ID)
ENVIRONMENT
DELIVERY
CD-ID
DEF ACT
M8690
BU
MI_6_9_0
M8 6.9-0
M8 6.10-0
CID38411 8.6-0
M8680
NW
MI_6_8_0
M8 6.8-0
M8 6.8-0
CID38411 8.5-0
M7260
UT
AM_7_26_0
MX 7.26-0
MX 7.24-3
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.
NTC TAN 0839/2.2 en
29
Preliminary tasks
4.3
Creating managed objects in the NMS

Before the NMS can receive and store network element data, create the managed
objects in the NMS. For more information on creating managed objects, see
Network 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
NTC TAN 0839/2.2 en
30
Preliminary tasks
4.4
Creating and modifying user group profiles

To establish a connection to a network element, ensure the user group profiles
are present and their command class authorities are properly defined.
For information about setting user group profiles from the Top-level User
Interface, see User 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 present
and all command class authorities are defined as 250 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
K=250 L=250 M=250 N=250 O=250
U=250 V=250 W=250 X=250 Y=250
F=250 G=250 H=250 I=250 J=250

P=250 Q=250 R=250 S=250 T=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 are
not set to 250, create/modify the user group profile by entering:
ZIAA:<user_profile>:ALL=250;
<user_profile>
NTC TAN 0839/2.2 en
The name of the customer-defined user

profile.
31
Preliminary tasks
4.
If using an MSC/HLR, ensure the TRAFADMI user group profile is present

and its command class authorities are defined as 1 by entering:
ZIAI:PROFILE=TRAFADMI;
5.
If TRAFADMI is not present and/or its command class authorities are not set
to 1, create/modify the TRAFADMI 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 the SYSOP1 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
USER ID:
SYSOP1
PROFILE NAME:
SYSTEM
1998-10-02
10:00:00
COMMAND CLASS AUTHORITIES:

A=250 B=250 C=250 D=250 E=250
K=250 L=250 M=250 N=250 O=250
U=250 V=250 W=250 X=250 Y=250
F=250 G=250 H=250 I=250 J=250

P=250 Q=250 R=250 S=250 T=250
UNIQUE PROFILE: NO
NETWORK USE ALLOWED: YES
COMMAND EXECUTED
MMI SYSTEM AUTHORITY HANDLING COMMAND <IA_>
NTC TAN 0839/2.2 en
32
Preliminary tasks
3.
If SYSOP1 is not present create the SYSOP1 user group ID by entering:

ZIAH:SYSOP1:<user_profile>;
<user_profile>
The name of the user profile created in

Section 4.4, Creating and modifying
user group profiles.
The system will prompt you for a password.

4.
When creating SYSOP1, enter the same password present in the NMS
workstation SYSTEM 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) applications
by entering:
ZIOA:SYSOP1:APPL=CM-X;
ZIOM:SYSOP1:APPL=PM-X;
ZIOM:SYSOP1:APPL=FM-X;
6.
If using an MSC/HLR, ensure the TRAFAD user group ID is present by

entering:
ZIAI:USERID=TRAFAD;
7.
If TRAFAD is not present create the TRAFAD user group ID by entering:

ZIAH:TRAFAD:TRAFADMI;
The system will prompt you for a password. The password for TRAFAD, is
ALLPASSW.
NTC TAN 0839/2.2 en
33
Configuring the NMS Communications Server
CONFIGURING THE NMS COMMUNICATIONS

SERVER
This chapter describes the procedure for configuring the NMS Communications
Server 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 en
34
5.1
Enabling X.121 subaddressing

X.121 subaddresses enable several X.25 addresses to be multiplexed through a
single X.25 card (using CONS and CLNS simultaneously). Traditionally X.121
subaddresses are not used in DCN integration.
Only use X.121 subaddressing if integrating a system that follows at least one of
the requirements listed below.
you are using CONS and CLNS at the same time through a single analog
X.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 are
using a LAN, see Setting up the OSI subnetwork on page 37.
To enable X.121 subaddressing (CONS/CLNS)
1.
Login to the Communications Server as the root user and set the
DISPLAY environment.
2.
Open an hpterm session by entering:

# hpterm &
3.
In the hpterm window, start the osiadmin utility by entering:

# /opt/ots/bin/osiadmin
4.
Using the arrow keys, select X.25 and press ENTER.
5.
Using the arrow keys, select Stop X.25 and follow the instructions given.
6.
Start HPs System Administration Manager (SAM) by selecting

Configure X.25 and press ENTER.
7.
Select Networking and Communications.
8.
Select Network Interface Cards.
NTC TAN 0839/2.2 en
35
9.
Select X.25 card.
10.
Select Configure X.25 address.
11.
In the Configure X.25 address window, remove the last two digits from
the X.25 address (ensure the X.25 address has 10 digits) and select OK.
12.
Select OK.
13.
Ensure the X.25 card is enabled and select File Exit.
14.
Exit SAM by selecting File Exit SAM.
15.
In the osiadmin window, select Previous Menu.

Note:
Do not exit from the osiadmin utility. This application will be used to
configure the OSI subnetwork.
16.
Go to Section 5.2, Setting up the OSI subnetwork on page 37
NTC TAN 0839/2.2 en
36
5.2

The following figure illustrates the procedure for setting up the OSI subnetwork
in the NMS Communications Server. If setting up a CONS subnetwork go to
Using CONS on page 46.
comm
Figure 9. Setting up the OSI subnetwork in the NMS Communications Server
NTC TAN 0839/2.2 en
37
5.2.1
Using CLNS
When setting up an CLNS subnetwork, the NMS Communications Server does

not make any distinction between analog or digital X.25.
Therefore, all X.25 connections (whether analog or digital) are referred to as
X.25 connections. When setting up an OSI subnetwork using CLNS the
following 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 the

osiadmin utility. If using a LAN, see Setting up a CLNS subnetwork for LAN
on page 41.
Note:
Only set up the CLNS/X.25 subnetwork when no existing subnetwork is usable.
NTC TAN 0839/2.2 en
38
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 following
situations:
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

1.
2.

# hpterm &
3.

4.
Using the arrow keys, select OTS and press ENTER.
5.
Select Configure OTS and press ENTER.
6.
Ensure the Update Mode parameter is set to R (Restart) and select F4. The
OTS Configuration screen is displayed.
Note:
If you encounter the following error message:
The osiconfchk program reported a validation error.
Exit OSIADMIN, run osiconfchk and follow the instructions given.

7.
Using the arrow keys, select Subnetworks Configure and press

ENTER.
NTC TAN 0839/2.2 en
39
8.
Select CLNS over X.25 Add... and press ENTER.
9.
Fill in the appropriate fields.

<Subnetwork name>
clnsx25_0
If using several subnetworks, distinguish

them by entering:
clnsx25_0, clnsx25_1, clnsx25_2
<Network ID>
Leave this field empty
<Local network
address (NSAP)>
Grouping X.25 cards = comm package

NSAP address
Using X.25 and LAN = Communications
Server physical NSAP address
<Subaddress>
Subaddress to identify the subnetwork

within the X.25 card.
01 for CLNS subnetworks
NULL if you are not using a subaddress
If grouping X.25 cards, ensure the
subaddress is the different for each card.
<X.25
Programmatic
access name>
Name of the X.25 card. The name can be

found in the /etc/x25/
x25config_<no.> file where <no.> is the
number of the X.25 card.
If grouping X.25 cards, distinguish each
programmatic access name by entering:
x25card_0, x25card_1
10.
Select Perform task then press the space bar.
11.
Repeat steps 8 through 10 until all OSI subnetworks have been added.
If...
Then proceed to...
there is no intermediate system
Adding an ISO OSI destination on

page 48
there is an intermediate system
Adding an IS as an ISO OSI

destination on page 50
NTC TAN 0839/2.2 en
40
5.2.1.2
Setting up a CLNS subnetwork for LAN
To set up a CLNS subnetwork for LAN, follow the instructions listed below. If
using redundant LAN connections enable the OTS snet_query_subnet
parameter as described in, Integrating Intermediate Systems, TAN 0900.
To set up a CLNS subnetwork for a LAN
1.
2.

# hpterm &
3.

4.
5.
6.
Note:

7.

ENTER.
NTC TAN 0839/2.2 en
41
8.
Select CLNS over 802.3 Add... and press ENTER.
9.
Fill in the in the appropriate fields:

<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 all
CLNS/LAN connections.
<Device interface name>
Name of the LAN interface.

Determine the available names of the
LAN interfaces by entering:
# /etc/lanscan
The name of the interface is shown in

the NameUnit field.
<CLNP subset>
3 (Full - Discard Null)
10.
Select Perform task then press the space bar.
11.
Go to Communications Server package on page 43.
NTC TAN 0839/2.2 en
42
5.2.1.3
Communications Server package
Applications services (HP-UX processes) and their hardware resources are

bundled into packages. Those packages are associated with a specific node and
given a unique NSAP address. For more information regarding nodes and
packages, see System Management Basic Operating Principles and Procedures,
TAN 0732.
When performing DCN integration, the Communications Server acts as one of
the primary nodes that form a high-availability cluster and it uses a unique NSAP
address to identify its own MC/ServiceGuard package.
The Nokia NMS processes and the /global disk on the Communications
Server are bundled into the (comm) package.
When configuring the comm package NSAP address use one of the free NSAP
addresses designated by your national authority. For more information about
NSAP addresses, see DCN Management, TAN 0377.
From the network perspective, the comm package address is configured in the
/etc/cmcluster/sgscusmx.cf configuration file and resident in the
workstations of either node. However, that address is only active in one server at
a time. An example is illustrated below.
Figure 10. Usage of comm package NSAP address
NTC TAN 0839/2.2 en
43
A comm package NSAP is only used when:
An ISO IP LAN is used

and
MC/ServiceGuard is used
Ensure the comm package NSAP is different than the physical NSAP of the
Communications and Standby Server. In the event a single service, node,
network or other resource failure, MC/ServiceGuard transfers the control of the
comm package from the Communication Server (primary node) to the Standby
Server (adoptive node).
Note:
In some cases, the comm package NSAP is referred to as the dynamic NSAP. The
dynamic NSAP address is fixed and does not change. This term only refers to the
dynamic nature of the comm package NSAP. This address is dynamically added
and 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, the

Communication Server software comm package is given a NSAP address of its
own. This address is dynamically added to the Communications Server by MC/
ServiceGuard.
NTC TAN 0839/2.2 en
44
To add the comm package NSAP

1.
2.
Stop the MC/ServiceGuard cluster by entering:

# cmhaltcl -f -v
3.
Using a text editor, open the /etc/cmcluster/sgscusmx.cf file, and

ensure the dcn_lan_used parameter is enabled.An example is
listed below:
(cluster "<name>"
(nms_type
(oracle_sid
(oracle_home
(dcn_x25_used
(dcn_lan_used
(cron_users
)
4.
"NMS/2000")
"omc")
"/d/db01/app/oracle/product/7.3.2")
"NO")
"YES")
"root oracle omc")
Add the comm package NSAP in the cluster packages section of the /etc/
cmcluster/sgscusmx.cf file as follows:
(package "comm"
(node
(node
(ip_address
(subnet
)
(nsap
(monitor_subnet
(file_system
(logical_volume
(symbolic_link
)
"<comm_server>")
"<standby_server>")
"<pkg_ip_address>")
"<subnet>")
"<comm_package_nsap>")
"<subnet>")
"/d/global"
"/dev/vgglobal/lvol1")
"/global")
The variables are described in the comments of the sgscusmx.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 en
45
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 that
can be used.
To set up a CONS subnetwork for X.25
1.
DISPLAY environment
2.
Open a hpterm session by entering:

# hpterm &
3.

4.
5.
6.
Note:

7.

ENTER.
8.
Select CONS over X.25 Add and press ENTER.
NTC TAN 0839/2.2 en
46
9.
Fill in the in the appropriate fields:

<Subnetwork name>
hpconsx25_0
If using several subnetworks, distinguish

them by entering:
hpconsx25_0, hpconsx25_1
<NSAP>
10 first digits of the Communications

Server X.121 address
Subnetwork
standard(s) allowed
ISO 8878 N
X.25 1980Y
X.25 1984Y
X.25 1988Y
<Subaddress>
Subaddress to identify the subnetwork

within the X.25 card.
00 for CONS subnetworks
NULL if you are not using a subaddress
If grouping X.25 cards, ensure the
subaddress is the different for each card.
<X.25 Programmatic
access name>
Name of the X.25 card. The name can be

found in the /etc/x25/
x25config_<no.> file where <no.> is
the number of the X.25 card.
10.
Select Perform task and then press the space bar.
11.
Go to Section 5.2.3, Adding an ISO OSI destination on page 48.
NTC TAN 0839/2.2 en
47
5.2.3
Adding an ISO OSI destination
Add an ISO OSI destination system to the network service configuration only if
your are using:
CONS over X.25
CLNS over X.25 without an IS
To add an ISO OSI destination system

1.
In the Subnetwork Configuration window, select Previous Menu.
2.
Select Destination Systems Add and press ENTER.
3.
Fill in the appropriate fields:

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.
4.
Physical address
Subnetwork (X.121) address of the

remote NE
Outgoing subnetwork name
Name of the outgoing subnetwork

used for the connection
End System, Intermediate

System or Both?
0 = End System
Request reverse charge?

(y/n)
Select Perform task and then press the space bar.
NTC TAN 0839/2.2 en
48
5.
Using a text editor, edit the /etc/opt/ots/conf/ots_dests file.

Change the line
dest_iso8878
to
dest_iso8878
After the above changes have been made, refer to the specification part of
the ots_dests file. An example is listed below. The actual values for
some of the parameters may vary.
Note:
The value for dest_net_address is the X.121 address of the remote
network element. If using a CLNS connection the value for
dest_net_address is the NSAP of the remote system.
dest_net_address
dest_phys_address
dest_out_subnet
dest_esis
dest_reverse_charge_req
dest_iso8878
dest_x25_1980
dest_x25_1984
dest_x25_1988
dest_fc_negotiation
dest_fast_select
dest_tc_negotiation
229315840000
229315840000
hpconsx25_<no.>
0# 0
2
0
0# 0
1
0
0
1
1
1
0
0
0
6.
In the osiadmin main screen, use the arrow keys to select OTS and press
ENTER.
7.
Select Update OTS and press ENTER.
8.
Select Previous Menu and then Exit OSIADMIN.
To ensure OSI configuration was successful

1.
In the hpterm window, run osiconfchk on the Communications Server

by entering:
# /usr/bin/osiconfchk
2.
Go to Configuring OSI applications and addresses on page 52
NTC TAN 0839/2.2 en
49
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, select Previous Menu.
2.
In the OTS configuration screen, select Destination Systems Add...
3.

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, Intermediate

System or Both
1 when using a router

2 when using a Front End
Request reverse charge?

(y/n)
4.
Select Perform Task and then Previous Menu.
5.
Go to Section 5.2.5, Adding a default route on page 51.
NTC TAN 0839/2.2 en
50
5.2.5
Adding a default route
To add a default route to an intermediate system, follow the instructions listed

below.
To add a default route
1.
In the osiadmin main menu, use the arrow keys to select OTS and press
ENTER.
2.
3.
4.
Select Routes Add... and press ENTER.
5.

Network ID or network
address (NSAP)
0 (zero)
Subnetwork Name
Name of the CLNS subnetwork,

see 5.2.1.2, Setting up a CLNS
subnetwork for LAN on page 41.
Primary route (NSAP)
NSAP of the IS
Indicates the default route
6.
Select Perform Task and then press the space bar.
7.
Select BACK TO OSIADMIN and then press the space bar.
8.
Select Update OTS and press ENTER.
9.
After OTS is updated, press ENTER.
10.
Select Previous Menu and then Exit OSIADMIN.
To ensure OSI configuration was successful

1.
In the hpterm window, run osiconfchk on the Communications Server

by entering:
# /usr/bin/osiconfchk
2.
Go to Configuring OSI applications and addresses on page 52.
NTC TAN 0839/2.2 en
51
5.3

The following figure illustrates the procedure of configuring the OSI
environment in the NMS Communications Server. If using a LAN, see Setting
up DX 200 OSI applications on 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 or
digital).
If X.25 is used, set up the PAD service as an additional level of network stability
in the event OSI VT fails.
NTC TAN 0839/2.2 en
52
5.3.1
Setting up PAD services
Before establishing PAD connections, the X.121 address of the network element
must 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 PAD
profile in the /etc/x25/x29hosts file.
To set up PAD service for outgoing connections
1.
Login to the Communications Server as the root user
2.
Using a text editor, open the /etc/x25/x29hosts and specify the

remote X.121 addresses for network connections. The syntax of the
pad_em and host_table entries for a single network element are
presented 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, see Hewlett Packards X.25/

9000 Users Guide.
<no.>
Name of the X.25 card. The name can be found in

the /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
Note:
Both pad_em and host_table entries must exist for each network
element.
NTC TAN 0839/2.2 en
53
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 the

Communications Server, see PAD service for incoming connections on
page 54. Otherwise go to Section 5.3.2, Setting up DX 200 OSI
applications on page 56.
5.3.1.2
PAD service for incoming connections
The x29server process provides support for communications with terminals

attached to a remote PAD. To set up the remote PAD service for incoming
connections 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 the root 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_spt
entry 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, see Hewlett Packards X.25/

9000 Users Guide.
<pid>
The process identity number associated with the

X.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 en
54
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 en
55
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 the
information regarding OSI applications and their addresses.
DX 200 applications depend on the local (NMS) applications in the remote
network element. A comprehensive list can be found in Application parameters
on 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 the ouorapmx.cf
NTC TAN 0839/2.2 en
56
To set up DX 200 (remote) OSI applications

1.
2.
Using a text editor, edit the $OMCCONFPATH/osi/ouorapmx.cf file and

insert the following entries for each remote OSI application:
# <comment>
ae_name
psap
apt
aeq
prot_proc_id
transport_class
apt_ddn
ae_label
end_aen
<app_name>
0x<P_sel>.0x<S_sel>.0x<T_sel>.0x<NSAP>
0
<proc_name>
<net_service>
<ddn>
0
<app_name>
Note:
The remote OSI applications are located in Section 3.2.2, DX 200
applications in the Communications Server on page 184. Ensure all four
applications are present in the ouorapmx.cf file.
3.
<app_name>
Name of the OSI application entity name

(AEN), see DX 200 applications in the
Communications Server on page 184.
<P_sel>,<S_sel>,
<T_sel>
P, S and T selectors of the OSI

application.
<NSAP>
NSAP of the remote network element
<proc_name>
Name of the OSI application process in

the 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
If simetaously using CONS/CLNS over X.25, see Configuring OSI

protocol identifiers on page 58. If using a LAN, go to Configuring
Connection Server software on page 59.
NTC TAN 0839/2.2 en
57
5.3.3
Configuring OSI protocol identifiers
When simultaneously using CONS/CLNS over X.25, configure the OSI protocol
identifiers as described below.
To configure OSI protocol identifiers
1.
Determine which network service (CLNS or CONS) is using NULL

subaddressing.
2.
Using a text editor, open the /etc/opt/ots/conf/ots_subnets file

and change the snet_bind_by_pid variable as shown below:
snet_bind_by_pid
Note:
Ensure you are changing the snet_bind_by_pid
appropriate network service.
3.
variable in the
Go to Configuring Connection Server software on page 59.
NTC TAN 0839/2.2 en
58
Configuring Connection Server software
CONFIGURING CONNECTION SERVER

SOFTWARE
The NMS Connection Server is used to establish an MML connection from the
Top-level User Interface to a DX 200 network element.
Connection Server is a software application distributed across several
workstations 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, it
sends its request to Connection Server. After receiving the request, Connection
Server chooses and allocates an appropriate route to the network element. If all
routes are busy and the client is willing to wait, the connection request is added
to a queue maintained by the Connection Server software.
The cnxdcnmx.cf configuration file must include routing information
regarding 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 NMS
Communications Server is an actual workstation.
NTC TAN 0839/2.2 en
59
The following figure illustrates the procedure for configuring the NMS
Connection Server.
Figure 13. Configuring the Connection Server software
NTC TAN 0839/2.2 en
60
6.1
Backing up the DCN configuration file

Before configuring the Connection Server, make a backup copy of the
cnxdcnmx.cf configuration file.
To backup the configuration file
1.
Log into the Communications Server as the omc user.
2.
Backup the configuration file by entering:

omc>% cd $OMCCONFPATH
omc>% cp cnxdcnmx.cf cnxdcnmx.cf.backup
3.
If connection server is running, go to Section 6.4, Editing the Connection

Server configuration file on page 65. Otherwise, follow the instructions
listed in Section 6.2, Editing the /etc/services file on page 62.
NTC TAN 0839/2.2 en
61
6.2
Editing the /etc/services file

The /etc/services file associates official service names and aliases with the
port number and protocol in use. When associating new services, follow the
naming scheme below.
<official_service_name> <port_number>/<protocol_name> <aliases>
<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 the

protocol
For example:
c5xstdmx 5555/tcp osi vt/telnet
To edit the /etc/services file

1.
Log into the Communications Server as the root user.
2.
Change to the etc directory and open the services file by entering:
# cd /etc
# vi services
3.
Edit the /etc/services file by adding an entry for the following

services in Nokia NMS ports section at the end of the file. An example is
written below.
# Ports for the Nokia OMC
# NOTE! Do not allocate ports for any other connections
# from the 79xx range.
c5xftamx
c5xpadmx
c5xstdmx
c6xapmmx
4.
5553/tcp
5554/tcp
5555/tcp
5556/tcp
ftam
x25pad
osi vt/telnet
apm
Exit vi, rebuild and distribute the new service name database by entering:
# /var/yp/ypmake
NTC TAN 0839/2.2 en
62
6.3
Configuring the inetd daemon

The inetd daemon is a TCP/IP superserver that invokes Internet server
processes. If the inetd daemon has been added during the commissioning and
upgrade procedure, go to Editing the Connection Server configuration file on
page 65.
Note:
This procedure is intended to be used during the initial commissioning of T10. If
the inetd.conf file has been altered after commissioning, ensure all changes
have been copied to the new file.
To configure the inetd daemon
1.
Change to the etc directory and backup the inetd.conf configuration

file 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
The hostname of the Database Server
<ds_hostname>
2.
Open the inetd.conf configuration file by entering:

# vi inetd.conf
NTC TAN 0839/2.2 en
63
3.
Edit the inetd.conf configuration file and add the following Connection
Server settings. When configuring the inetd daemon follow the naming
scheme below.
<service> <socket> <protocol> nowait <uid> <path> <conf_file>
<cf_path>
<service>
The PSM binary name, for example:

c5xpadmx
<socket_type>
Type of socket
stream
<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 the

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

cnxcffmx.cf configuration file
<active>
The current omc_build
# 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.
Exit vi and copy the inetd.conf file to the Database Server by entering:
# rcp /etc/inetd.conf <ds_hostname>:/etc/inetd.conf
5.
Re-read the inetd.conf configuration file by entering:

# /sbin/init.d/inetd stop
# /sbin/init.d/inetd start
NTC TAN 0839/2.2 en
64
6.4
Editing the Connection Server configuration file

When editing the Connection Server configuration file, ensure the listening port
is set to the appropriate value.
To edit the Connection Server configuration file
1.
2.
Change to the global directory and open the Connection Server

configuration file (cnxcffmx.cf) by entering:
# cd $OMCCONFPATH
# vi cnxcffmx.cf
3.
Edit the cnxcffmx.cf configuration file by adding the following

Connection Server environment settings:
(listening port
(csHost
4.
"5560")
"<comm_server_hostname>")
Go to Section 6.5, Address device information on page 66.
NTC TAN 0839/2.2 en
65
6.5
Address device information

Before editing the cnxdcnmx.cf configuration file, ensure all address device
information is available.
Connections using OSI Transport Services need information about the OSI
configuration. The ouolapmx.cf and ouorapmx.cf files contain the OSI
addresses required by FTAM, VT and CMIS Servers for local and remote hosts.
The following table shows how to obtain address and device information for the
various protocols used in the Connection Server.
Address or Device
Information 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 Access
Name
Enter: x25stat -c -d <device file>
Local Host for FTAM,

OSI VT or CMIS Servers
osi/ouolapmx.cf.
See the address information in $OMCCONFPATH/
Remote Hosts for FTAM,

OSI VT or CMIS Servers
osi/ouorapmx.cf
IP addresses
If NIS is configured, enter: ypcat hosts
See the address information in $OMCCONFPATH/
Table 8. Address and device information for the Connection Server
NTC TAN 0839/2.2 en
66
6.6
Naming arcs and routes

When naming arcs and routes in the Connection Server configuration file, follow
the naming scheme listed below:
<entry_type>_<start>_<type>_<proto>_<card>_<end>
<entry_type>
Entry type:
A for an arc
R for a route
AR for an administrative route
<start>
Start point of the arc, usually CSRV

(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) used

for the connection
<end>
Name of the end system
Example 1.
An arc entry from the Communications Server using OSI VT over a LAN to a
BSC 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 a
BSC named "Turku" would be:
A_CSRV_PAD_X25_0_TURKU
NTC TAN 0839/2.2 en
67
6.7
Adding an arc to a remote system

Arcs are the connections between two nodes. When adding an arc to a remote
system in the Connection Server configuration follow the instruction listed
below.
To add an arc to a remote system
1.
2.
Edit the $OMCCONFPATH/cnxdcnmx.cf configuration file by adding an

entry for the remote system in the Arc definitions section of the file.
The syntax of an arc entry is as follows:
(arcName
(maxConns
(address
(connChannel
(loginSeqFileName
(logoutSeqFileName
"<arc_name>"
"<max_conns>")
"<end>")
"<start>")
"<login_file_name>")
"<logout_file_name>")
The Connection Server login sequence file establishes the login order
a 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). Each
login sequence file may only contain one login record per file.
Figure 14. Example arc entry in the cnxdcnmx.cf configuration file
NTC TAN 0839/2.2 en
68
<arc_name>
Name of the arc using naming scheme

suggested in Naming arcs and routes on
page 67.
<max_conns>
Maximum number of simultaneous arc

connections to the remote system.
This value is used in load balancing between
two parallel areas going to the same
destination
<end>
Ending point of the arc (destination address)

PAD = X.121 address of the NE
OSI VT = The name of the local
application in the NE that implements the
VT service. The name of the application
is typically <NE>0<ccccc>VT, for
example BSC012345VT
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 login

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

logout sequences are written.
Table 9. Arc fields definitions in the cnxdcnmx.cf file

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 en
69
3.
If using OSI VT/Telnet comment out all arc names for PAD connections
as 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.
6.8
After all arcs have been added, go to Section 6.8, Adding a route to a
remote system on page 70
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.

entry for the remote system in the Route definitions section of the
file. The syntax of a route entry is as follows:
(routeName
(arcs
(host
(port
(checkScript
(commandLine
)
"<route_name>"
"<arc_info>")
"<comm_srvr>")
"<port>")
"")
"<cmdline>")
Figure 15. Example route entry in the cnxdcnmx.cf configuration file
NTC TAN 0839/2.2 en
70
<route_name>
Name of the route see, Naming arcs and routes on

page 67.
<arc_info>
List of arc(s) names used by the route. Delineator

is 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
2.
If using OSI VT/Telnet, comment out all route definitions for PAD
connections 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 an

administrative route to a remote system on page 72
NTC TAN 0839/2.2 en
71
6.9
Adding an administrative route to a remote system

Administrative routes are paths through an internetwork that are supervised by
administrative 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 an

route
entry for the remote system in the administrative
definitions section of the file. The syntax of a route entry is as follows:
(adminRoute
(arcs
(host
(port
(checkScript
(commandLine
)
"<adm_name>"
"<arc_info>")
"<comm_srvr>")
"5556")
"<script>")
"")
<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 are

located in the $OMCROOT/lib/script
directory.
PAD (CONS) = c6xconmx.perl
OSI VT (CLNS) = c6xvtxmx.perl
Telnet = not available, comment out AR entry
<comm_srvr>
Note:
If you have a CONS connection, add the PSN address as the definition for
the commandLine route entry.
NTC TAN 0839/2.2 en
72
Figure 16. Example administrative route entry in the cnxdcnmx.cf file

2.
If using OSI VT comment out all administrative route definitions for all
PAD/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
<comm_srvr>
NTC TAN 0839/2.2 en
73
6.10 Adding a node definition to a remote system

Nodes are the endpoints of a network connection or the points common to two
or more lines in a network. Nodes serve as the control points in the network and
are generically referred to as any entity that can access a network.
When adding a node definition to a remote system in the Connection Server
configuration, follow the instructions listed below:
To add a node definition for the remote system
1.

entry for the remote system in the node 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 en
74
<int_ID>
Internal ID of the remote system, see Top-level

User Interface, TAN 0871.
<rem_sys>
Name of the remote system
<maxMMLConns>
Maximum number of simultaneous MML

connections to a network element
<maxFileConns>
Maximum number of simultaneous file transfers
<maxSpontConns>
Maximum number of simultaneous SPONT

connections 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
Table 10. Node field definitions in the cnxdcnmx.cf file
NTC TAN 0839/2.2 en
75
6.10.1
Determining connection subtypes
The connection subtype (connSubType) identifies the subconnection to a

network element that is used by the host. Connection subtypes are only used in
spontaneous (SPONT) connections.
Connection type (connType)
Description
SPONT<number>
Spontaneous connections
The variable is replaces by an integer
greater than 0 that specifies a unique
subaddress for one spontaneous
connection
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 and SPONT2 could be used for
collecting measurements.
NTC TAN 0839/2.2 en
76
6.11 Re-reading the configuration file

After making the modifications to the $OMCCONFPATH/cnxdcnmx.cf
configuration file, re-read the configuration file.
To re-read the configuration file
1.
2.
Re-read the configuration file by entering:

omc>% $OMCROOT/lib/script/cnxreconfigmx.perl
This script searches for the c4xcsxmx Connection Server process and
displays a notice listing the process found and its process identification
number (PID) An example is listed below.
This script also starts the cnxcheckdcnmx.pl script and ensures the
syntax of the cnxdcnmx.cf is correct. If errors are found, re-reading is
cancelled. An example is listed below.
Checking Connection Servers
DCN configuration file
File OK
Process c4xcsxmx was found. Pid is <PID>
Reconfiguration with current configuration file (Y/N) ?
3.
Enter y and press ENTER. The script re-reads the configuration file and
the new settings take effect.
Note:
If the reconfiguration script reports errors, refer to the following
instructions.
To correct errors in the configuration file

1.
2.
Restore the backup configuration file by entering:

omc>% mv cnxdcnmx.cf cnxdcnmx.cf.new
omc>% cp cnxdcnmx.cf.backup cnxdcnmx.cf
NTC TAN 0839/2.2 en
77
3.
Re-read the backup configuration file by entering:

omc>% $OMCROOT/lib/script/cnxreconfigmx.perl
This script searches for the c4xcsxmx Connection Server process and
displays a notice listing the process found and its process identification
number (PID) An example is listed below.
This script also starts the cnxcheckdcnmx.pl script and ensures the
syntax of the cnxdcnmx.cf is correct. If errors are found, re-reading is
cancelled. An example is listed below.
Checking Connection Servers
DCN configuration file
File OK
Process c4xcsxmx was found. Pid is <PID>
Reconfiguration with current configuration file (Y/N) ?
4.
Enter y and press ENTER. The script re-reads the configuration file and
the old settings are in effect. This enables the Connection Server to
function normally while you correct the error in the configuration file.
5.
Open the werlog4006.log file and search for further information about
the error by entering:
omc>% more $OMCLOGDIR/werlog4006.log
6.
Edit the new configuration file $OMCCONFPATH/cnxdcnmx.cf.new and

correct the problem.
7.
Copy the new configuration file by entering:

omc>% cp cnxdcnmx.cf.new cnxdcnmx.cf
8.
Re-read the configuration file as described in Step 3.
6.12 Verifying DCN integration

To verify that the integration has been completed successfully, perform the
integration tests described in Testing Installations, TAN 0523.
After successful integration, reboot the system as described in Workstation
Network Maintainence, TAN 0513
NTC TAN 0839/2.2 en
78
Configuring the DX 200 network element
CONFIGURING THE DX 200 NETWORK ELEMENT

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

This section gives instructions on setting up the physical connection from
the network element to the NMS Communications Server.
Instructions are provided for analog X.25 (PSN), digital X.25 (PCM) and
LAN connections

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

This section gives instructions on setting up DX 200 and NMS OSI
applications in the network element.
Note:
The instructions for the DAXnodeWLL are only valid for ADW2.
NTC TAN 0839/2.2 en
79
7.1

The following figure outlines the procedure for setting up the physical
connection in a DX 200 network element:
Figure 17. Setting up the physical connection in a DX 200 network element

NTC TAN 0839/2.2 en
80
7.1.1
Using analog X.25 (PSN)
Setting up the physical connection using analog X.25 (PSN) requires following
tasks:
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), see Using digital X.25 (PCM) on page 89. If using
a LAN, see Using a LAN on page 100.
NTC TAN 0839/2.2 en
81
ZQTC:
ZQXC:
ZQXM:
ZQCS:
ZQGC:
ZQEC:
ZQLC:
ZQLA:
ZQBN:
ZQBC:
ZQDL:
ZQDR:
Figure 18. MML command groups when using analog X.25
NTC TAN 0839/2.2 en
82
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 for
each card per unit. For more information regarding jumper settings, see
AC25-S network card on 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 space

addresses and interrupt levels proposed by the system by entering:
ZWTP:OMU:AC25_S,<PIU_index>,<track>;
PIU-index in the BSC/DAX
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.
NTC TAN 0839/2.2 en
83
2.
With the MSC/HLR, accept the default memory space addresses

proposed by the system and set the interrupt level by entering:
ZWTP:BDCU,<index>:AC25_S,<PIU_index>,<track>:INT=
<int_level>;
-orWith a MSC/HLR, set the memory space addresses and interrupt

level by entering:
ZWTP:BDCU,<index>:AC25_S,<PIU_index>,<track>:
MS=<ms>,ME=<me>,INT=<int_level>;
<index>
The index of the BDCU.
<PIU_index>
Index of the network card. Ensure these

settings 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 range
starts from 7
In the MSC/HLR the track range starts
from 32
<ms>
Memory space start address, see page 147
<me>
Memory space end address, see page 147
<int_level>
Interrupt level in hexadecimal

for the MSC/HLR see the following table
PIU-index in the MSC/HLR
Track
Interrupt level
32
30H
37
31H
42
32H
47
33H
52
34H
57
35H
62
36H
67
37H
Table 13. Indexes, tracks and interrupt levels in the MSC/HLR
NTC TAN 0839/2.2 en
84
7.1.1.2
Setting the physical layer parameters
To set the physical layer parameters of the AC25-S card, follow the instructions
listed below.
To set the physical layer parameters
Enter the following MML command:
ZQTC:<unit_info>:AC25S,<PIU_index>:<IF_type>,<bit_rate>;
<unit_info>
Unit responsible for the connection, together with the

index, if required.
OMU in the BSC/DAXnode WLL
BDCU in the MSC/HLR
<PIU_index>
Index of the network card. Ensure these settings are unique

for each card per unit.
0-7 in the MSC/HLR
<IF_type>
Interface type, see the following tables.
<bit_rate>
Bit rate of the connection
Track
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
Table 15. Interface types and components
NTC TAN 0839/2.2 en
85
7.1.1.3
To establish a physical X.25 connection, create and modify the X.25 parameter
set. DX 200 network elements include a pre-defined parameter set called
DEFSET. Use this default set as a basis for creating the X.25 parameter set. For
X.25 parameter set values, see Appendix B., X.25 parameter sets on page 158.
Note:
Do not directly edit the DEFSET parameter set. Create a new parameter set and
then 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 you

want to define in the parameter set
<parameter>
Parameter name
<value>
Value for the parameter
<unit>
Unit responsible for the connection, together

with the index, if required.
BDCU in the MSC/HLR
NTC TAN 0839/2.2 en
86
7.1.1.4
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.
<no>
Number that you want to assign to the physical

channel
<unit_info>

index, if required
BDCU in the MSC/HLR
<PIU_index>
Index of the network card. Ensure these settings are

unique for each card per unit.
0-7 in the MSC/HLR
<SNPA>
SNPA address (physical address) of the local system
<mode>
DCE or DTE, see Appendix A., Network card

jumpers on page 144.
<param_set>
Name of the parameter set created in Creating and

modifying the X.25 parameter set on page 86.
Unlock the physical channel by entering:

ZQSC:<no>,UNL;
3.
Proceed according to the table listed below.

If...
Then proceed to...
Setting up CLNS
Verifying the physical connection on page 99.
Setting up CONS
Assigning a channel group to a physical

channel on page 88.
NTC TAN 0839/2.2 en
87
7.1.1.5
Assigning a channel group to a physical channel
To assign the physical channel to a channel group determine the following

information:
Whether you want to add the channel into an existing group or create a new
channel 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>;
<group>
Name of the channel group
<channel>
Number of the physical channel
<priority>
Priority value you want to assign to the channel
7.1.1.6
Verify the physical channel was created successfully by entering:

ZQSI;
Ensure the network card is in the WO-EX state and the channel is UNL-ENA. When
data is transferred through the physical channel, its state will change to UNLACT.
Go to Setting up the OSI subnetwork on page 103.
NTC TAN 0839/2.2 en
88
7.1.2
Using digital X.25 (PCM)
Setting up the physical connection using digital X.25 (PCM) requires the
following tasks:
Installing and configuring an AS7-U card
Installing and configuring an Exchange Terminal
Setting up the semipermanent connections
Assigning a channel group to a physical channel (CONS only)
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 the
instructions listed below.
To install and configure an AS7-U card
1.
2.
Using the following tables, determine the PIU-index of the AS7-U card.
3.
AS7-U network card on page 150.
4.
Place the AS7-U card into the appropriate unit in the network element.
5.

1.

addresses proposed by the system by entering:
ZWTP:OMU:AS7_U,<PIU_index>,<track>::X25,4,
<PCM_number>,TSL,<TSL>;
Track
Interrupt level
default
default
NTC TAN 0839/2.2 en
89
2.
With the MSC/HLR, accept the default memory space addresses

proposed 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>;
<index>
Index of the unit
<PIU_index>

0-7 in the MSC/HLR
<track>

starts from 7
from 32
<int_level>

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.
<ms>
<me>
<TSL>
Next free time slot
PIU-index in the MSC/HLR
Track
Interrupt level
32
30H
37
31H
42
32H
47
33H
52
34H
57
35H
62
36H
67
37H
Table 17. Indexes, tracks and interrupt levels in the MSC/HLR
NTC TAN 0839/2.2 en
90
-orWith a MSC/HLR, set the memory space addresses and interrupt

level 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>;
NTC TAN 0839/2.2 en
<index>
Index of the unit
<PIU_index>

0-7 in the MSC/HLR
<track>
Location of the network card in the

subrack.
In the BSC/DAXnode WLL the track
range starts from 7
from 32
<ms>
<me>
<int_level>

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
<unit_info>
Unit responsible for the connection,

together with the index, if required
BDCU in the MSC/HLR
91
7.1.2.2
Installing and configuring an Exchange Terminal
To install and configure an Exchange Terminal, follow the instructions listed

below.
To configure an Exchange Terminal
1.
Determine if there is an ET available for connection. The following

commands 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 available
for the connection.
3.
Create the ET in the hardware description files by entering:

ZWTU:ET,<index>:<coordinates>;
NTC TAN 0839/2.2 en
92
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>;
<index>
Index number of the ET unit
<coordinates>
Location of the ET unit
<PIU_index>
Index of the following exchange

terminals. Ensure these settings are unique
ET1E
ET2E
<PIU_type>
ET1E
ET2E
<track>
Location of the network card in the

subrack.
In the BSC/DAXnode WLL the track
range starts from 0
from 6
<PCM>
PCM number, usually the same as the

index of the ET
<TSL>
Next free time slot
Note:
It is possible to create several ET units with the same coordinates, and use
different track numbers for plug-in units that belong to different ET
functional units.
NTC TAN 0839/2.2 en
93
5.
Depending on your network element, create a PCM connection by

entering:
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_inde
x>;
In an HLR:
ZWUC:ET,<index>:ET1E,<PIU_index>::CCSU,
<CCSU_index>;
6.
<index>
Index number of the ET unit
<PIU_index>
Index of the following exchange

terminals. Ensure these settings are unique
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
Change the ET to working state (WO-EX) by entering the following

commands:
ZUSC:ET,<index>:SE;
ZUSC:ET,<index>:TE;
ZUSC:ET,<index>:WO;
You can check that the unit is in the WO-EX state by entering:
ZUSI:ET;
NTC TAN 0839/2.2 en
94
7.1.2.3
Setting up the semipermanent connections
The communication through the MSC/HLR is facilitated by setting up a

semipermanent connection between the time slots in the PCM line to the BSC/
DAXnode WLL and routing devices. These external PCM lines are
semipermanently 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 the
BSC/DAXnode WLL follow the instructions listed below.
Note:
Before beginning the process, ensure the MSC/HLR is connected to the NMS
Front End or a third party router using PCM over digital X.25.
To set up the semipermanent connection in the MSC/HLR
1.
Ensure the TSEM0 circuit group exists by entering:

ZRCI:GSW;
2.
If the TSEM0 circuit group is not displayed, create it by entering:

ZRCG:GSW:TYPE=S,CGR=158,NCGR=TSEM0,CRCT=<PCM>-<TSL>;
3.
<PCM>
Number of the external PCM from the MSC/HLR to the

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

HLR to the IS
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 PCM
in 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>
External PCM number used for the connection
<TSL>
Time slot number of the external PCM used for the

connection
NTC TAN 0839/2.2 en
95
5.
Set up a semipermanent connection in the transcoder if it has not been

created already. When creating a connection in the transcoder, consider the
following:
If using a transcoder between the MSC and the BSC/DAXnode

WLL, ensure the actual connection is in the transcoder unit. Use the
following time slots: 1, 16, 30 or 31.
If a TCSM is used, create the connection according to the values

listed below:
Transcoder
Outgoing TSL
First
28 (AUX1)
Second
29 (AUX2)
Third
30 (AUX3)
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 the
1.
Connect the transcoder service terminal to the transcoder and switch the
terminal on.
2.
Press F2.
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.
NTC TAN 0839/2.2 en
96
7.1.2.4
To establish the physical X.25 connection, define the X.25 parameter set. The
DX 200 based network elements include a pre-defined parameter set titled
DEFSET, 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 the DEFSET parameter set directly. Instead, create a new parameter
set 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>];
<param_set>
Name you want to assign to the parameter set
<list_of_values>
Comma-delimited list of parameter values you

want to define in the parameter set
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 MML

command:
ZQXM:<param_set>:<parameter>=<value>
[,<parameter>=<value>,<...>];
3.
<param_set>
Name of the parameter set
<parameter>
Parameter name
<value>
Value for the parameter
<unit_info>

with the index, if required
BDCU in the MSC/HLR
Finally, reset the unit by entering:

ZUSU:<unit_info>;
NTC TAN 0839/2.2 en
97
7.1.2.5
When creating a physical channel, follow the instructions listed below.

To create a physical channel
1.

ZQCC:<no.>:<unit_info>,<PIU_index>:<SNPA>:<mode>,
<param_set>:<PCM>-<TSL>;
2.
<no.>
<unit_info>
Unit responsible for the connection, together with

the index, if required.
BDCU in the MSC/HLR
<PIU_index>
Index of the network card. Ensure these settings

are unique for each card per unit.
0-7 in the MSC/HLR
<SNPA>
SNPA address (physical address) of the local

system
<mode>
The local end of the connection

DCE
DTE
See Appendix A., Network card jumpers on page
144
<param_set>
Name of the parameter set created in Creating and

modifying the X.25 parameter set on page 97
<PCM>
Number of the external PCM
<TSL>
Time slot within the PCM (any value 1 - 31)
Unlock the physical channel:

ZQSC:<no.>,UNL;
Now proceed to the following table:

If...
Then proceed to...
Setting up a CLNS network service Verifying the physical connection on

page 99.
Setting up a CONS network
service
NTC TAN 0839/2.2 en
Assigning a channel group to a physical

channel on page 99.
98
7.1.2.6
Assigning a channel group to a physical channel
Channel groups are assigned to physical channels when using remote NSAP
addresses. To assign the physical channel to a channel group, determine the
following information:
Whether you want to add the channel into an existing group or create a new
channel 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>;
<group>
Name of the channel group
<channel>
<priority>
Priority value you want to assign to the channel
7.1.2.7
Verify the physical channel was created successfully by entering:

ZQSI;
Ensure the network card is in the WO-EX state and the channel is UNL-ENA. When
data is transferred through the physical channel, its state will change to UNLACT.
NTC TAN 0839/2.2 en
99
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 the
Link Level Control (LLC1) software can detect the interface type if an Ethernet
cable 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 network

element, follow the instructions listed below:
To install and configure a COCEN card
1.
2.
Using the following tables, determine the PIU-index of the COCEN card.
3.
COCEN network card on page 154.
4.
Place the COCEN card into the appropriate unit in the network element.
5.

1.

address proposed by the system by entering:
ZWTP:OMU:COCEN,<PIU_index>,<track>:SW=LLC1;
Track
NTC TAN 0839/2.2 en
100
2.
With an MSC/HLR, set the interrupt level and software package

name 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 name
for each card by entering:
ZWTP:BDCU,<index>:COCEN,<PIU_index>,<track>:
INT=<int_level>,SW=LLC1;
<index>
The index number of the OMU/BDCU
<PIU_index>
Index of the COCEN card. Ensure these

0-7 in the MSC/HLR/Front End
<track>

starts from 7
In the MSC/HLR/Front End the track range
starts from 32
<int_level>

default in the BSC/DAXnode WLL
for the MSC/HLR/Front End see the
following table
PIU-index in the MSC/HLR/FE
Track
Interrupt level
32
30H
37
31H
42
32H
47
33H
52
34H
57
35H
62
36H
67
37H
Table 20. Indexes, tracks and interrupt levels in the MSC/HLR/FE
NTC TAN 0839/2.2 en
101
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
<unit_info>
7.

BDCU in the MSC/HLR/Front End
Accept the action by entering y after the prompt:

MESSAGE RESTART ORDERED
UNIT <unit_info>
8.
Ensure the COCEN card has been properly installed and configured by
entering:
ZWTI:P:<unit_info>,<index>:COCEN,<PIU_index>;
9.
NTC TAN 0839/2.2 en
102
7.2

The following figure illustrates the procedure of setting up the OSI subnetwork
in a DX 200 network element. If using CONS, see Creating NSAPs and network
protocol addresses on page 108.
Figure 19. Setting up the OSI subnetwork in a DX 200 network element

NTC TAN 0839/2.2 en
103
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 listed
below.
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.
<unit_info>

BDCU in the MSC/HLR
<PDU>
PDU
This value is expressed in 0.5 seconds. Calculated by
multiplying 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 seven
zeros (0000000<ccccc>)
<max_addr>
Maximum manual area address count. Defines the

number of subnetworks in the DCN.
The recommended value is 3.
<area_addr>
Area address part of the NSAP address, see DCN

Management, TAN 0377.
NTC TAN 0839/2.2 en
104
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 listed

below.
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.25

card 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>;
NTC TAN 0839/2.2 en
<link_ID>
ID number of the linkage. (Optional)

If not previously defined, the system will
assign a free number 0-60.
<unit_info>

BDCU in the MSC/HLR
<PIU_index>

0-7 in the MSC/HLR
<SNPA>
SNPA address (physical address) of the

system reached via this linkage.
X.25 connections only
Same as the physical address (X.121) of the
remote or intermediate system.
<CLNS_name>
Any unique name that defines the CLNS

network. For example: CLNS_LAN.
105
2.
Unlock the linkage object by entering:

ZQLG:<link_ID>::UNL;
Warning:
Re-initialising the CLNS object causes all existing connections from the
network element to temporarily disconnect. Ensure that no critical data
transfer operations or terminal sessions are in progress when the object is
initialised.
3.
Re-initialise the CLNS object by entering:

ZQET:<CLNS_name>;
4.
If setting up a linkage object for a LAN, go to Creating NSAPs and

network protocol addresses on page 108. If setting up a linkage object for
X.25, see Adding manual adjacencies.
NTC TAN 0839/2.2 en
106
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, complete
the following instructions:
To add a manual adjacency
1.
Add a manual adjacency between a network element and the

Communication Server by entering:
ZQLA:<link_ID>:<endsys_1>[,<endsys_2>];
2.
Add a manual adjacency between a network element and the Standby

Server by entering:
ZQLA:<link_ID>:<endsys_1>[,<endsys_3>];
<link_ID>
ID number of the linkage. (Optional)

The system will assign a free number 0-60.
<endsys_1>
NSAP of the comm package in the NE
<endsys_2>
NSAP of the Communications Server
<endsys_3>
NSAP of the Standby Server
Note:
If using a comm package NSAP address, add the system identifier of the
Communication Server and comm package in the <endsys> fields. For
more information regarding system identifiers, see DCN Management,
TAN 0377.
NTC TAN 0839/2.2 en
107
7.2.1.4
NSAPs and network protocol addresses are used to associate services in network
elements. Before establishing a connection from the NMS NE, the NSAPs
and network protocol addresses must be created in all network elements.
To create NSAPs and network protocol addresses for CLNS connections, follow
the instructions listed below. If using comm package NSAP addresses, the
following 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=0000000
1,AREA=<area>;
<AFI>

The value 39 indicates a DCC NSAP.
<IDI>
Initial Domain Identifier. The country code of

the customer, see DCN Management, TAN 0377.
<org>
Organisation identifier. Must be acquired from

the national authorities.
<area>
Routing area.
If there is only one routing area, use 0001
<NSAP>
Number assigned to the NSAP. If you do not

specify a number, the system will automatically
assign the next available number.
Note:
In the DX 200 dialogue, the reserved (RES) and routing domain values
have been combined into one field. For more information on how these
parameters should be defined, see DCN Management, TAN 0377.
2.
Create the local NSAP for each service by entering:

ZQBN:[<NSAP>]:L:4:NSEL=00;
NTC TAN 0839/2.2 en
108
3.
Create the remote NSAP for the comm package NSAP addresses by
entering:
ZQBN:[<NSAP>]:R:5:END=<endsys_1>,NSEL=00;
4.
If creating the physical NSAP addresses for the Communications and

Standby Servers, enter the following commands:
5.
Create the local network address named LOCAL by entering:

ZQBC:LOCAL:L;
6.
Create the remote network address titled REMNMS by entering:

ZQBC:REMNMS:R;
<NSAP>

<endsys_1>
comm package NSAP
<endsys_2>
Communications Server NSAP
<endsys_3>
Standby Server NSAP
NTC TAN 0839/2.2 en
109
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
--------LOCAL
REMNMS
...
ROLE
---LOCAL
REMOTE
NSAP NR
------7
8
PRIO NSAP NR
---- ------50
9
PRIO NSAP NR PRIO

--- ------ ----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 not
copy all values displayed to your configuration.
When creating network protocol addresses for the first time their state is
LOC-DIS until they are attached to a network protocol address.
8.
9.
Ensure the following:
NET ADDR for local CLNS applications is set to LOCAL
NET ADDR for remote CLNS applications is set to REMNMS
NSAP NR for local and remote CLNS applications is attached to the

correct NET ADDR
Go to Section 7.2.1.5, Attaching NSAPs to network protocol addresses on

page 111.
NTC TAN 0839/2.2 en
110
7.2.1.5
Attaching NSAPs to network protocol addresses
After the NSAPs and network protocol addresses have been created in Creating
NSAPs and network protocol addresses on page 108, attach the CLNS NSAPs to
the network protocol addresses.
To attach NSAPs (CLNS) to network protocol addresses
1.
Attach the local network protocol address, LOCAL, to the NSAP created in
Step 2. on page 108 by entering:
ZQBT:LOCAL:<NSAP>;
2.
Attach the remote network protocol address REMNMS, to the NSAP created
in Step 3. on page 109 by entering:
ZQBT:REMNMS:<NSAP>,<priority>;
Note:
The comm package NSAP must be set with the highest priority.
3.
Unlock both local and remote NSAPs by entering one of the following
commands:
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.
<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 first
and the last NSAP number in the range
Go to Section 7.3, Configuring OSI applications and addresses on page

118.
NTC TAN 0839/2.2 en
111
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 a
network element. The number of NSAPs and network addresses created depends
on the networking protocol and the services you intend to set up.
Also, before establishing an MML connection NMS NE using CONS, the
local and applications must be specified in the network element.
Note:
PAD service may not be necessary as remote terminal sessions to the network
elements can be established using OSI VT.
Details on the address parameters can be found in OSI Parameters on page 175.
NTC TAN 0839/2.2 en
112
7.2.2.1
NSAPs, SPIs and network protocol addresses are used to associate services in
network elements. Before establishing a connection from the NMS NE, the
local applications must be created in all network elements.
If you are using several remote systems (NMS, NE, RTR) for PAD and MSW
connections, create a unique network protocol address name for each destination.
When creating NSAPs and network protocol addresses, repeat each step three
times for each CONS service (CMISE/FTAM, PAD and MSW).
To create NSAPs and network protocol addresses (CONS)
1.
Create the local NSAP for each service by entering:

ZQBN:[<NSAP>]:L:1:DTE=<ne_x.121>,SPI=<SPI>;
2.
Create the remote NSAP for each service by entering:

ZQBN:[<NSAP>]:R:1:DTE=<cs_x.121>,SPI=<SPI>,CHG=<grp>;
3.
Create the local network address for each service by entering:

ZQBC:<l_net_addr>:L;
<NSAP>

<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, see SPIs for CONS

communications on page 175.
OMCCMISE for CMISE/FTAM
OMCPAD for PAD
OMCMSW for MSW
<l_net_addr>
Local network protocol address name, see CONS

network protocol address names on page 177.
LOCALCMI for CMISE/FTAM
LOCALPAD1 for PAD
LOCALMSW1 for MSW
NTC TAN 0839/2.2 en
113
4.
Create the remote network address for each service by entering:

ZQBC:<r_net_addr>:R;
Remote network protocol address name, see CONS

REMCMI for CMISE/FTAM
REMPAD1 for PAD
REMMSW1 for MSW
<r_net_addr>
When creating remote network protocol address

names for PAD and MSW applications, ensure each
network protocol address name is different.
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
---1
2
3
ROLE
---LOCAL
LOCAL
LOCAL
STATE
------LOC-DIS
LOC-DIS
LOC-DIS
CHG
----
DTE
------------123456789012
123456789012
123456789012
SPI
------03010100
01000000
C0000000
X.25 NETWORK PROTOCOL ADDRESS INFORMATION

NBR
---4
5
6
ROLE
---REMOTE
REMOTE
REMOTE
STATE
------LOC-DIS
LOC-DIS
LOC-DIS
CHG
---OMCCMISE
OMCPAD
OMCMSW
DTE
------------111222199188
111222199188
111222199188
SPI
------03010100
01000000
C0000000
COMMAND EXECUTED
Note:
When creating network protocol addresses for the first time their state is
LOC-DIS until they are attached to a network protocol address.
NTC TAN 0839/2.2 en
114
6.
7.
SPIs for CMISE and FTAM applications are set to 03010100
SPIs for PAD applications are set to 01000000
SPIs for MSW applications are set to C0000000
Go to Section 7.2.2.2, Attaching NSAPs to network protocol addresses on

page 116.
NTC TAN 0839/2.2 en
115
7.2.2.2
Attaching NSAPs to network protocol addresses
After the NSAPs and network protocol addresses have been created in Creating
NSAPs and network protocol addresses on page 113, attach the CONS NSAPs to
the network protocol addresses. When attaching NSAPs to network protocol
addresses, repeat each step three times for each CONS service (CMISE/FTAM,
PAD and MSW).
To attach NSAPs (CONS) to network protocol addresses
1.
Attach the local network protocol addresses to the corresponding local

NSAPs by entering:
ZQBT:<l_net_addr>:<NSAP>;
2.
Attach the remote network protocol addresses to the corresponding remote

NSAPs by entering:
ZQBT:<r_net_addr>:<NSAP>;
3.
Unlock both local and remote NSAPs by entering one of the following
commands:
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, CONS

<r_net_addr>
Remote network protocol address name, see CONS

REMCMI for CMISE/FTAM
REMPAD1 for PAD
REMMSW1 for MSW
When creating remote network protocol address
names for PAD and MSW applications, ensure each
network protocol address name is different.
<NSAP>
Number assigned to the NSAP
<NSAP_1>
<NSAP_2>
The first
and the last NSAP number in the range
NTC TAN 0839/2.2 en
116
4.
Interrogate the network address data by entering:

ZQBI;
DX 200
TOM
1998-10-02
10:00:00
INTERROGATING NETWORK ADDRESS DATA

NET ADDR
-------LOCALCMI
LOCALPAD1
LOCALMSW1
ROLE
-----LOCAL
LOCAL
LOCAL
REMCMI
REMPAD1
REMMSW1
REMOTE
REMOTE
REMOTE
NSAP NR
------1
2
3
4
5
6
PRIO NSAP NR
---- -------
PRIO NSAP NR
---- -------
PRIO
----
50
50
50
COMMAND EXECUTED
5.
The network protocol address names (NET ADDR) are specified as

in CONS network protocol address names on page 177.
The local network addresses are in the LOCAL role
The remote network addresses are in the REMOTE role
The NSAP number (NSAP NBR) matches the NBR field displayed in
Step 5. on page 114.
Note:
6.
Go to Section 7.3, Configuring OSI applications and addresses on page

118.
NTC TAN 0839/2.2 en
117
7.3

The following figure illustrates the tasks for configuring the OSI applications
and addresses in the DX 200 network element.
Figure 20. OSI application configuration process flowchart

NTC TAN 0839/2.2 en
118
7.3.1
Setting up local PAD and MSW applications
Local PAD and MSW applications are used between a network element and an
intermediate system. The type of application used depends on the intermediate
system.
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 MSW
applications.
If establishing NE - NE connections, set up the local PAD and MSW

applications.
If you are using a LAN, go to Setting up local OSI applications on page

122.
To set up these applications in a DX 200 network element, follow the
instructions 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
-------------BSC012345PAD PAD
AP_TYPE
AP_TITLE
AEQ
NET ADDR
STATE
--------- ------LOCALPAD
UNL-ENA
UNIT FAM ID
---- -----OMU
PROC ID
-------
: NOT IN USE
:
:
P-SELECTOR:
S-SELECTOR:
T-SELECTOR:
COMMAND EXECUTED
OSI ENVIRONMENT APPLICATION DATA HANDLING COMMANDS <QD_>
NTC TAN 0839/2.2 en
119
2.
If using X.25 with a Front End, set up the local MSW applications by
entering:
ZQDL:<aen>:::UNL:<unit_info>:<type>:<NW_addr>;
<aen>
Name of the application entity name, see DX 200

<unit_info>

index, if required.
BDCU in the MSC/HLR
<type>
Application type, see page 178.
<NW_addr>
Local network address name used by the application,

see CONS network protocol address names on page
177.
Figure 21. Creating local PAD applications in a BSC
NTC TAN 0839/2.2 en
120
3.
Interrogate the local application data by entering:

ZQDI:APL=LCL;
DX 200
TOM
1998-10-02
10:00:00

AE-NAME
-----------BSC012345PAD
BSC012345MSW
APPL
---PAD
MSW
NET ADDR
STATE
-------- --------LOCALPAD1 UNL-ENA
LOCALMSW1 UNL-ENA
UNIT FAM ID
PROC ID
---- -----OMU
OMU
COMMAND EXECUTED
4.
5.
Network protocol address names (NET ADDR) are specified as in

CONS network protocol address names on page 177.
all states are set to UNL-ENA
Go to Setting up local OSI applications on page 122.
NTC TAN 0839/2.2 en
121
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 the

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
------------BSC012345A
AP_TYPE
AP_TITLE
AEQ
APPL
----CMISE
NET ADDR STATE

-------- -------LOCAL
UNL-ENA
UNIT FAM ID
---- -----OMU 021F
PROC ID
------0000H
: NOT IN USE
:
:
P-SELECTOR: 3333030230
S-SELECTOR: 3333030230
T-SELECTOR: 3333
COMMAND EXECUTED
NTC TAN 0839/2.2 en
122
<aen>
Name of the OSI application entity name, see DX

200 applications on page 178.
<unit_info>

BDCU in the MSC/HLR
<type>
Application type, see page 178
<fam>
Process family ID. This parameter is only required

for CMI applications.
<process_ID>
Master process ID. Use the value 0
<P_sel>
P selector value, see DX 200 applications on page

178.
<S_sel>
S selector value
<T_sel>
T selector value
Note:
Repeat this step for the local CLNS applications (items 1-4) in the DX 200
OSI applications table beginning on page 178.
Figure 22. Creating local CLNS applications in a BSC
NTC TAN 0839/2.2 en
123
2.
Interrogate the local OSI application data by entering:

ZQDI:APL=LCL;
DX 200
TOM
1998-10-02
10:00:00

AE-NAME
-----------BSC012345F
BSC012345VT
BSC012345A
BSC012345EHA
APPL NET ADDR

STATE
----- -------- --------VFS LOCAL
UNL-ENA
VTP LOCAL
UNL-ENA
CMI LOCAL
UNL-ENA
CMI LOCAL
UNL-ENA
UNIT
---OMU
OMU
OMU
OMU
FAM ID
-----
PROC ID
-------
021F
02B1
0000H
0000H
COMMAND EXECUTED
3.
4.
Network protocol address names (NET ADDR) are specified as in

CLNS network protocol address names on page 176.
Go to Section 7.3.3, Defining the CMISE service profile on page 125.
NTC TAN 0839/2.2 en
124
7.3.3
Defining the CMISE service profile
After creating all local applications in the DX 200 network element, define the
CMISE service profile (<NE>0<ccccc>A) for all CMISE applications. This
application provides the OSI CMISE service.
To define the service profile for CMISE
1.
Ensure the CMISE application A is set to LOC-ENA by entering:

ZQDI:AEN=<aen>:MAX;
DX 200
TOM
1998-10-02
10:00:00

AE-NAME
------MSC051234A
AP_TYPE
AP_TITLE
AEQ
APPL
----CMISE
NET ADDR
-------LOCAL
STATE
UNIT FAM ID
-------- ---- -----UNL-ENA
OMU 21FH
PROC ID
------0000H
:
:
:
T-SELECTOR: 3333
COMMAND EXECUTED
<aen>
NTC TAN 0839/2.2 en
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
125
2.
If the state is set to LOC-ENA go to the next step. Otherwise, change the
CMISE state to LOC-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
-------MSC051234A
OLD STATE
--------UNL-ENA
NEW STATE
---------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;
<aen>
4.
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
Change the CMISE state to UNL-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
-------MSC051234A
OLD STATE
--------LOC-ENA
NEW STATE
---------UNL-ENA
COMMAND EXECUTED
NTC TAN 0839/2.2 en
126
5.
Interrogate the CMISE service profile, and ensure the values are correct by
entering:
ZQDI:AEN=<aen>:PAR;
DX 200
TOM
1998-10-02
10:00:00
INTERROGATING SERVICE PROFILE DATA

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

------------------------------------CMISE
MULTIPLE OBJECT SELECTION =YES

MULTIPLE REPLYS
=YES
CANCEL GET OPERATION
=YES
FILTER SUPPORT
EXTENDED SERVICE
CMISE VERSION
=YES
=NO
=1 AND 2
COMMAND EXECUTED
If...
Then proceed to...
using X.25 and you have set up the

local MSW and PAD applications
Setting up the remote PAD and MSW

using a LAN
Setting up remote applications on page

132.
NTC TAN 0839/2.2 en
127
7.3.4
Setting up the remote PAD and MSW applications
Remote PAD and MSW connections are used between a network element and an
intermediate 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/MSW
applications have been set up. If using a LAN, go to Setting up remote
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 by
entering:
ZQDR:<aen>:::UNL:<unit_info>:<type>:<NW_addr>;
<aen>
Name of the application entity name, see DX 200

<unit_info>

index, if required.
BDCU in the MSC/HLR
<type>
<NW_addr>
Local network address name used by the application,

see CONS network protocol address names on page
177.
NTC TAN 0839/2.2 en
128
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
----------CISCOPAD
OMC012345MSW
AP_TYPE
AP_TITLE
AEQ
APPL
-----PAD
MSW
NET ADDR
-------REMCISCOPAD1
REMMSW0
STATE
-------UNL-ENA
UNL-ENA
: NOT IN USE
:
:
P-SELECTOR:
S-SELECTOR:
T-SELECTOR:
COMMAND EXECUTED
4.
Network protocol address name (NET ADDR) is specified as in

Creating NSAPs and network protocol addresses, Step 4. on page
114.
NTC TAN 0839/2.2 en
129
7.3.5
Adding an O&M connection
O&M connections are added to enable MSW applications (local and remote) to
communicate 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 MSW
applications have been set up using an X.25 connection.
To add an O&M (Operations & Maintainence) connection, follow the

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>;
<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 entity

name, see page 178.
LOADING PROGRAM VERSION <version_number>
CONNECTION <connection_number> CREATED
COMMAND EXECUTED
O&M CHANNEL HANDLING <QN_>
NTC TAN 0839/2.2 en
130
2.
Change the state of the O&M connection to BL-US by entering:

ZQNC:<channel_number>:BL;
STATE TRANSITION EXECUTED
CHANNEL NUMBER = <channel_number>
COMMAND EXECUTED
NEW STATE = BL-US
3.
Change the state of the O&M connection to WO-EX by entering:

ZQNC:<channel_number>:WO;
STATE TRANSITION EXECUTED
CHANNEL NUMBER = <channel_number>
COMMAND EXECUTED
NEW STATE = WO-EX
4.
Interrogate the O&M connection data, and ensure the values are correct by
entering:
ZQNI:CON=<connection_number>:COM;
DX 200
TOM
1998-08-25
CONNECTION=
NAME= TOM
TYPE= BSC
CTYP=PSPN
AEN=
CHANNEL=
LOC=FLA
SW-LEVEL=5
COMP=
STATE=WO-EX
C-NUM=12345
F/P=
TIME=
10:00:00
ID=
S/R=
COMMAND EXECUTED
NTC TAN 0839/2.2 en
131
7.3.6
Setting up remote applications
Before establishing a NE NMS connection, the remote applications must be

specified in the network element. To set up the remote applications in a DX 200
network element, follow the instructions listed below.
To set up remote OSI applications in a DX 200 network element, follow the
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 table
beginning on page 183.
<aen>
Name of the OSI application entity name, see NMS

<type>
<NW_addr>
Network address name used by the application, see

Network protocol address names on page 176.
<P_sel>
P selector value, see NMS applications in DX 200

network elements on page 183.
<S_sel>
S selector value
<T_sel>
T selector value
Figure 23. Creating remote OSI applications in the DX 200
NTC TAN 0839/2.2 en
132
2.
Interrogate the remote OSI application data, and ensure the values are
correct by entering:
ZQDI:APL=REM:MAX;
DX 200
TOM
1998-10-02
10:00:00
REMOTE OSI APPLICATION DATA

AE-NAME
----------OMC000000SW
AP_TYPE
AP_TITLE
AEQ
APPL
-----VFS
NET ADDR
-------WS
STATE
-------UNL-ENA
: NOT IN USE
:
:
T-SELECTOR: 1133
COMMAND EXECUTED
3.
Network protocol address name (NET ADDR) is specified as in

Creating NSAPs and network protocol addresses, Step 4. on page
114.
NTC TAN 0839/2.2 en
133
7.3.7
Changing power measurements levels in a BSC
When upgrading from T8 to T10, the power measurements levels must be

changed from BTS to TRX in the BMPARA_SPARE file. Once the power
measurement levels have been changed, the TRX ID and TRX frequency will
be included in the measurement record identifier.
This section describes how to change the power measurements levels in the BSC
using S6 software.
To change power measurement levels in a BSC using S6 software
1.
Display the format of the BMPARA_SPARE file by entering:

ZDFD:OMU:6C7,0;
DX 200
OMU
FF FF
FF FF
FF FF
FF FF
FF FF
FF FF
FF FF
FF FF
TOM
1998-10-02
FILE N:O 06C70000 RECORDN:O 00000000

FF FF FF FF FF FF FF FF FF FF FF FF FF FF
10:00:00
................
................
................
................
................
................
................
................
COMMAND EXECUTED
MEMORY FILE HANDLING COMMAND <DF_>
2.
Ensure the fourth last value (7C) is set to FF as listed above. If the value is
set to FF, go to the next section required for your integration.
3.
If the value is not set to FF stop the GSM power control measurements by
entering:
ZTPE:MEASUR,POWER::;
4.
Change the power measurement levels by entering:

ZDFS:OMU:6C7,0,7C,B;
When prompted for a value, enter FF.

5.
Start the GSM power control measurements by entering:

ZTPS:MEASUR,POWER::;
NTC TAN 0839/2.2 en
134
7.3.8
Adding new counters in a BSC
When upgrading from T8 to T10, two new counters, per neighbour cell, have
been added to the handover adjacent cell measurements. To view these counters,
the handover adjacent cell measurement record must be changed from 170
counters/record to 238 counters/record in the BMPARA_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 the BMPARA_SPARE file by entering:

ZDFD:OMU:6C7,0;
DX 200
OMU
FF FF
FF FF
FF FF
FF FF
FF FF
FF FF
FF FF
FF FF
FILE
FF FF
FF FF
FF FF
FF FF
FF FF
FF FF
FF FF
FF FF
TOM
1998-10-02
N:O 06C70000 RECORDN:O 00000000

FF FF FF FF FF FF FF FF FF FF FF FF
FF FF FF FF FF FF FF FF FF FF 01 FF
10:00:00
................
................
................
................
................
................
................
................
COMMAND EXECUTED
MEMORY FILE HANDLING COMMAND <DF_>
2.
Ensure the second last value (7E) is set to 01 as listed above. If the value
is set to 01, go to the next section required for your integration.
3.
If the value is not set to 01 stop the GSM handover measurements by

entering:
ZTPE:MEASUR,HO::;
4.
Change the size of the handover adjacent cell measurement record by

entering:
ZDFS:OMU:6C7,0,7E,B;
When prompted for a value, enter 01.

5.
Start the GSM handover measurements by entering:

ZTPS:MEASUR,HO::;
NTC TAN 0839/2.2 en
135
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 be
redirected 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 thus
hiding the actual I/O device from an application.
This section describes the redirection of logical files in the MSC/HLR using
M7B/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 buffer
logical file (EVBFIL) by entering:
ZIIS::EVBFIL::OU=OMU,DEV=VDS-2;
2.
List the logical files connected to VDS-2 by entering:

ZIIL::DEV=VDS-2;
3.
Ensure only EVBFIL is connected to VDS-2. If other logical files are

connected to VDS-2, remove them by entering:
ZIIS::<file>:OU=OMU,DEV=VDS-2:;
<file>
Name of the logical file
Figure 24. Abbreviated syntax of the ZIIS command
NTC TAN 0839/2.2 en
136
4.
List the objects connected to EVBFIL by entering:

ZIIL::LF=EVBFIL;
OBJECT CONNECTED IN FOLLOWING LOGICAL FILES:
SYSTEM = MSC-T
UNIT = OMU
PAGE
1
LOG
LOG SPARE
FILE
FILE FILE
NBR NAME & CLASS MODE
PHYSICAL
FILE
NAME
OBJ
IND
SYSTEM
NAME
UNIT DEVICE/
NAME LOGICAL
FILE
/* OBJECT NOT CONNECTED TO ANY LOGICAL FILE */

COMMAND EXECUTED
I/O CONFIGURATION HANDLING COMMAND <II_>
5.
Ensure there are no connections to the EVBFIL file. If other logical files
are connected to the EVBFIL file, remove them by entering:
ZIIS::<file>:OS=<system_name>,OU=OMU,LF=EVBFIL;
6.
<file>
<system_name>
Name of the MSC/HLR
Change the devices connected to the measurement (MEAFIL) and

observation (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 to VDS-0 or VDS-1 by entering:

ZIIL::DEV=VDS-0;
ZIIL::DEV=VDS-1;
8.
Ensure there are no logical files connected to VDS-0 or VDS-1. If other

logical files are connected, remove them by entering:
NTC TAN 0839/2.2 en
137
9.
List the objects connected to the GSMME1MG logical file by entering:

ZIID::GSMME1MG;
LOGICAL FILE(S):
SYSTEM = MSC-T
UNIT = OMU
PAGE
1
LOG
LOG SPARE
FILE
FILE FILE
NBR NAME & CLASS MODE
PHYSICAL
FILE
NAME
95 GSMME1MG P
OBJ
IND
SYSTEM
NAME
UNIT DEVICE/
NAME LOGICAL
FILE
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 the
MSC/HLR by entering:
ZIIS::GSMME1MG:OS=<fe_name>,OU=PFMU,LF=MSCMEA01MG:
OS=<system_name>,OU=OMU,LF=OBSFIL;
11.
<fe_name>
Name of the Front End
<system_name>
Name of the MSC/HLR
If there is no connections to the Front End, connect the GSM observation

report (GSMME1MG) file to the OBSFIL in the MSC/HLR by entering:
ZIIS::GSMME1MG::OS=<system_name>,OU=OMU,LF=OBSFIL;
GSMME1MG
Table 21. Logical files for observations in the MSC/HLR

12.
List the information connected to the MSCMEA01MG logical file by

entering:
ZIIL::OS=<fe_name>,OU=PFMU,LF=MSCMEA01MG;
NTC TAN 0839/2.2 en
138
13.
If a connection exists to the Front End, replace the link with a connection
to 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 the
measurement (MEAFIL) logical file in the MSC/HLR by entering:
ZIIS::<file>::OS=<system_name>,OU=OMU,LF=MEAFIL;
<file>
<fe_name>
<system_name>
Name of the MSC/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
Table 22. Logical files for measurement data handling in the MSC
ACHLRB
OSIMEAS2B
EIRMEASB
OSIMEAS3B
FIELDRMG
OSIMEAS4B
LOAOBSMG
ROUTSTB
OSIMEAS1B
SECCOUNTB
Table 23. Logical files for measurement data handling in the HLR
NTC TAN 0839/2.2 en
139
15.
List the logical files connected to the virtual report converter (VRP-0) by
entering:
ZIIL::OS=<fe_name>,OU=OMU,DEV=VRP-0;
OBJECT CONNECTED IN FOLLOWING LOGICAL FILES:
SYSTEM = MSC-T
UNIT = OMU
PAGE
1
LOG
LOG SPARE
FILE
FILE FILE
NBR NAME&CLASS MODE
2C DIAGNOS P
6D OMCALARM P
PHYSICAL
FILE
NAME
OBJ
IND
SYSTEM
NAME
UNIT DEVICE/
NAME LOGICAL
FILE
1
2
1
FE-T
FE-T
FE-T
OMU
OMU
OMU
LPT-1
VRP-0
VRP-0
COMMAND EXECUTED
16.
If OMCALARM is connected to the Front End, replace the link from

OMCALARM 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.
<fe_name>
<system_name>
Name of the MSC/HLR
If DIAGNOS is connected to the Front End, replace the link from DIAGNOS
to 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) by
entering:
ZIIL::DEV=LPT-0;
NTC TAN 0839/2.2 en
140
19.
If any logical file for fault management data handling is connected to the
Front End, replace the link from the Front End to LPT-0 in the MSC/HLR
by entering:
ZIIS::<file>:OS=<fe_name>,OU=OMU,DEV=LPT-0:
OS=<system_name>,OU=OMU,DEV=LPT-0;
<file>
<fe_name>
<system_name>
Name of the MSC/HLR
<index>
Index of the unit
DIAGNOS
SWITCH1
EXTERN1
SWITCH2
EXTERN2
TRANSM1
OMCALARM
TRANSM2
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 active
Operations and Maintainence Unit by entering:
ZUSU:OMU,<index>;
NTC TAN 0839/2.2 en
141
Configuring intermediate systems
CONFIGURING INTERMEDIATE SYSTEMS

If configuring a router or Front End, perform the integration tasks described in
Integrating Intermediate Systems, TAN 0900. Otherwise, go to Verifying DCN
integration on page 143.
NTC TAN 0839/2.2 en
142
Verifying DCN integration
VERIFYING DCN INTEGRATION

To verify that the integration has been completed successfully, perform the
integration tests described in Testing Installations, TAN 0523.
NTC TAN 0839/2.2 en
143
Appendix A. Network card jumpers
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 this

appendix. You may modify the jumper settings at a later date.
Communication card modes
The following tables present the communication card modes using indirect and
direct connections between the network element and the NMS.
System
Mode
NMS
DTE
IS
DCE
DX 200
DTE
Table 25. Communication modes used with indirect connections

System
Mode
NMS
DTE
DX 200
DCE
Table 26. Communication modes used in direct connections
NTC TAN 0839/2.2 en
144
AC25-S NETWORK CARD

The following figure illustrates the jumpers on the AC25-S network card.
-1 .2 5 /5
3
0 4 4
4
3
W 8
1
W 7
-1 .2 5 /5
0 4 9
W 6
W 1
W 3
W 2
6
3
4
5
4
7
W 1 3
P e r lo s - C 0 6 4 M S - C 1 A
P e r lo s - C 0 9 6 M S - C 1 A
A C 2 5 -S C 8 5 9 6 C D E F G H 0 1 9 1 3 7 1 0 8 7 1
W 4
1
2
3
W 1 W 2 W 3W 1
1
2
3
W 5
1
2
3
1 4
1 3
1 2
1 1
1 0
9
8
T E L E N O K IA
7 5 -0 8 5 9 6 -0 1 -0
R A M
R A M
A C 2 5 -5
4 .1 3 -0
A 2 5 X 2 5 G X
H
8 5 9 6
B 1
A C 2 5 -5
4 .1 3 -0
A 2 5 X 2 5 G X
L
8 5 9 6
A 1
5
4
R A M
R A M
-1 .2 5 /5
0 4 9
W 2 5
P e r lo s - C 0 6 4 M S - C 1 A
C 8 5 9 6
3
Figure 25. Jumpers on the AC25-S network card
NTC TAN 0839/2.2 en
145
1.1
Jumper blocks
The AC25-S jumper block has the following 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.35

protocols
W3, W4, W5,

W7, W9
Defines the communication mode for the X.21 protocol
W25
Defines the interchangeability code of the card
Table 27. AC25-S jumper block functions
NTC TAN 0839/2.2 en
146
1.2
Memory space addresses

The W13 jumper block defines the memory space address allocated to a card
from the address space of the unit.
The following table lists the memory space start addresses (MS), memory space
end address (ME) and their corresponding jumper settings.
piu
MS
ME
W13 jumper settings (X = on)

1-14
2-13
3-12
4-11
5-10
69
78
80100000-
801FFFFF
80200000-
802FFFFF
80300000-
803FFFFF
80400000-
804FFFFF
80500000-
805FFFFF
80600000-
806FFFFF
80700000-
807FFFFF
80800000-
808FFFFF
Table 28. Jumpers for memory space address (AC25-S)
NTC TAN 0839/2.2 en
147
1.3
Interchangeability codes
The following table presents the interchangeability code jumpers on the AC25S network card.
Code
W25 jumpers (X = on)
1-8
2-7
3-6
4-5
Table 29. Interchangeability code jumpers on the AC25-S network card

The interchangeability code is written on the network card next to the euro
connector. 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 is F.
NTC TAN 0839/2.2 en
148
1.4
Communication modes
The following tables present the jumpers for the communication mode on the
AC25-S network card when a straight cable (without signal change) is used.
Mode
Jumper setting (X = on)

W4
W8
1-2
2-3
1-6
2-5
3-4
V.24, DTE
V.24, DCE
V.35, DTE
V.35, DCE
Table 30. Jumpers for the V.24 and V.35 communication modes (AC25-S)
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.21, DCE
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, you
should select the DTE mode. If a direct connection to another end (AC25-S card
to an other AC25-S card) with a null-modem cable is used, the AC25-S is usually
acting as DCE, meaning that it provides clocking. When using an X.21
connection, you have to use the DCE-DTE jumper setting, and when using a
V.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 you
intend to use any other configuration, please refer to Configuring the DX 200
network element on page 79.
NTC TAN 0839/2.2 en
149
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 en
150
2.1
Jumper blocks
The jumper blocks on the network card have the following functions:
Jumper
block(s)
Function
W3
W9
Specifies the interchangeability code of the card
W12
Specifies the memory size of the card
Table 32. Important jumper blocks (AS7-U)
2.2

PIU-index
MS
ME
W3 jumpers (X = on)
3-4
5-6
7-8
9-10
80100000-
801FFFFF
80200000-
802FFFFF
80300000-
803FFFFF
80400000-
804FFFFF
80500000-
805FFFFF
80600000-
806FFFFF
80700000-
807FFFFF
80800000-
808FFFFF
Table 33. Jumpers for memory space address (AS7-U)
NTC TAN 0839/2.2 en
151
2.3
The following table presents the interchangeability code jumpers on the AS7-U
network card.
Code
W9 jumpers (X = on)
1-5
2-6
3-7
4-8
Table 34. Interchangeability code jumpers on the AS7-U network card

The interchangeability code is written on the network card next to the euro
connector. 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 is K.
NTC TAN 0839/2.2 en
152
2.4
Memory size
The W12 jumper block defines the memory size. When closed, the available
memory is 256K, and when open, 64K. When the network card is used for X.25
connections, the jumpers should be open. When using the AS7-U for MSW
connections, W12 should be closed.
NTC TAN 0839/2.2 en
153
COCEN NETWORK CARD

The following figure illustrates the jumpers on the COCEN network card.
2
3
5
6
6 5 4
W 1 3
1
8 6 6 9
E 1
R A M
R A M
R A M
R A M
R A M
R A M
0 4 9
8 6 6 9
D 1
R A M
-1 .2 5 /5
W 1 7
1 W 1 1
1
2
2
R A M
P e r lo s - C 0 6 4 M S - C 1 A
8 6 6 9
1 2 1 2
8 6 6 9
B 1
8 6 6 9
C 1
A C
W 1 5 W 1 6
8 6 6 9
A 1
0 4 9
W 1 1
1
2 W 1 2
3 1
8
7
2
6
3
4
5
2 W 1 4
T P I
1 2 3
-1 .2 5 /5
A B C D E F 1 A 1 F 9 7 1 9 9 2 0 5
1 6 W 1
1 5
1 4
1 2 3 4 5 6 7 8 9 1 0 1 1 1 2
1 3
1 2
1 1
W 2
1
1 0 1 2 1 2
2
W
6
9
W 3 W 4
3
1 2
1 1
1 0
9
8 1 2 1 2
7 W 7 W 8
W 5
6 5 4
W 1 0
2
1
1 2 3
W 9
P e r lo s - C 0 6 4 M S - C 1 A
C 8 6 6 9
C O A X
W 13
2
3
4
5
6
7
8
W 21
B C O C E N
A U I
8 6 6 9
F 1
Figure 27. Jumpers on the COCEN network card
NTC TAN 0839/2.2 en
154
3.1
Jumper blocks
The jumper blocks on the network card have the following functions:
Jumper
block(s)
Function
W1
W12
Specifies the interchangeability code of the card
Table 35. Important jumper blocks (COCEN)
3.2

PIUindex
MS
ME
W1 jumpers (X = on)
1-16
2-15
3-14
413
512
611
710
89
80100000-
801FFFFF
80200000-
802FFFFF
80300000-
803FFFFF
80400000-
804FFFFF
80500000-
805FFFFF
80600000-
806FFFFF
80700000-
807FFFFF
80800000-
808FFFFF
Table 36. Jumpers for memory space addresses (COCEN)
NTC TAN 0839/2.2 en
155
3.3
The following table presents the interchangeability code jumpers on the COCEN
network card.
Code
W12 jumpers (X = on)
1-5
2-6
3-7
4-8
Table 37. Interchangeability code jumpers on the COCEN network card

For information on where the interchangeability code is located, see
Interchangeability codes on page 148.
NTC TAN 0839/2.2 en
156
CABLES
This chapter presents the cables used when integrating the Nokia NMS with
other 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:

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
Table 38. Cables and connections
NTC TAN 0839/2.2 en
157
Appendix B. X.25 parameter sets
Appendix B.
X.25 PARAMETER SETS
General
Parameter
Value
MAXIMUM NETWORK SERVICE

DATA UNIT LENGTH
8192 BYTES
L2 CONNECTION MODE
INITIATED AFTER START UP
USER FACILITIES
NO USER FACILITIES
Table 39. General X.25 parameters

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)
Table 40. Level 2 parameters

Level 3
Parameter
Value
L3 USER DATA SIZE
128 BYTES
L3 SEND WINDOW SIZE
2 FRAMES
L3 MODULO
L3 TIMER T20
180 SECONDS
L3 TIMER T21
200 SECONDS
L3 TIMER T22
180 SECONDS
L3 TIMER T23
180 SECONDS
L3 RESET RETRY COUNT
5 TIMES
L3 CLEAR RETRY COUNT
5 TIMES
L3 FIRST PVC
0 (= NOT IN USE)
NTC TAN 0839/2.2 en
158
Appendix B. X.25 parameter sets
Level 3
Parameter
Value
L3 LAST PVC
0 (= NOT IN USE)
L3 LIC
0 (NOT SUPPORTED)
L3 HIC
0 (NOT SUPPORTED)
L3 LTC
L3 HTC
16
L3 LOC
0 (NOT SUPPORTED)
L3 HOC
0 (NOT SUPPORTED)
Table 41. Level 3 parameters
NTC TAN 0839/2.2 en
159
Appendix C. Configuration information
Appendix C.
CONFIGURATION INFORMATION
This appendix lists the type of information needed when testing DCN
integration. Information regarding the following objects are included:
Servers
Network elements
SERVERS
If your server is partially configured, and the network map does not contain, all
of the configuration information, interrogate or obtain the following items:
Passwords
Passwords for the omc and root 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:
NTC TAN 0839/2.2 en
TH-NMS10.0-7
160
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.
Physical address
Network type
IP address of the system
LAN
X.121 address
Analog X.25 (PSN)
NSAP address
A 40-character value issued by the respective standards institute of each
country. For more information regarding NSAPs and their structure, see
DCN Management, TAN 0377.
Type of NSAP
Depending on you network architecture you may have one or more of the
following NSAPs.
Communications Server NSAP
Standby Server NSAP
comm package NSAP
NTC TAN 0839/2.2 en
161
NETWORK ELEMENTS
If your network element is partially configured, and the network map does not
contain, all of the configuration information, interrogate or obtain the following
items:
Passwords
Passwords for the system 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 en
162
Physical address (DTE)

A 12-character value that defines the core address of the network
element.The DTE identifier is always used as the network element X.121
address.
Physical address
Network type
X.121 address (DTE)
Analog X.25 (PSN)
NSAP address
A 40-character value issued by the respective standards institute of each
country. For more information regarding NSAPs and their structure, see
DCN Management, TAN 0377.
Abbreviation
Explanation
Number of
characters
Network element
The name of the NE
AFI
IDI
Initial Domain Identifier
DFI
DSP format identifier
ORG
Organisational identifier
RESERVED
Reserved and routing domains
8 (4 + 4)
AREA
Routing area
END SYSTEM
C-number of the NE padded

with zeros from the left.
12
SEL
N-selector
C-number
A 5-character value taken from the NSAP system identifier. For more
information regarding system identifiers, see DCN Management, TAN
0377.
NTC TAN 0839/2.2 en
163
Appendix D. Configuration worksheets
Appendix D.
CONFIGURATION WORKSHEETS
Due the amount of values needed to test DCN integration, fill in the following
worksheets before testing begins. Once all values have been interrogated and
written down, no further memorisation and guesswork is necessary.
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 the root 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 en
164
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
#
#
Global Parameters
#
x.121
111222199188
...
6.
10:00:00
1998
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, if
there is one, is the comm package NSAP.
NTC TAN 0839/2.2 en
165
7.
Copy required information displayed on the terminal to the following

table.
Hardware
Role
Software
Hostname
IP address
X.121 address
NSAP address
Type of NSAP
Table 42. Server worksheet
NTC TAN 0839/2.2 en
166
NETWORK ELEMENT WORKSHEET

To fill in the network element worksheet enter the following MML command
and 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 en
167
4.
Interrogate the C-number of the network element by entering:

ZQNI;
DX 200
PAGE
CON TYPE
CTYP
000 BSC
001 OMC
PSPN
TOM
1998-10-02
10:00:00
1
SW
5
5
C-NUMID NAME
LOCATION
CHA
STATE
12345
54321
NMS-FLA
NMS-FLA
000
BL-SY
TOM
NMSFLA_2
COMMAND EXECUTED
NTC TAN 0839/2.2 en
168
5.
Copy required information displayed on the terminal to the following

table.
Hardware
Role
Software
Hostname
X.121 address
NSAP address
C-number
Table 43. Network element worksheet
NTC TAN 0839/2.2 en
169
Appendix E. Integration checklists
Appendix E.
INTEGRATION CHECKLISTS
This appendix contains several the checklists used for DCN integration. As you
complete each task, mark the appropriate box.
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 en
170
CONFIGURING THE NMS COMMUNICATIONS

SERVER
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 the comm package NSAPs as on
page 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 OSI

destination 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 en
171
CONFIGURING OSI APPLICATIONS

This contains the checklist for configuring the OSI applications within the NMS
Communications Server.
Task completed
Are you using X.25

yes
Set up the remote PAD service as on page 53
Task completed
Set up the DX 200 OSI applications as on

page 56
Task completed
Set up the DX 200 OSI applications as on

page 56
Task completed
no
Configure the OSI protocol identifiers
Task completed
Configure the Connection Server software as on page 59 Task completed
NTC TAN 0839/2.2 en
172
CONFIGURING THE CONNECTION SERVER

SOFTWARE
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 the Inetd 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 en
173
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
Set up the NSAPs
Task completed
Set up the network addresses
Task completed
CONS
Configure OSI applications and addresses as on page

118
Task completed
Determine local application information
NTC TAN 0839/2.2 en
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
174
Appendix F. OSI Parameters
Appendix F.
OSI PARAMETERS
This appendix presents N - selectors, Subsequent Protocol Identifiers (SPIs),

network addresses and OSI application address required during integration.
N - SELECTORS AND SPIS
1.1
N - selectors for CLNS communications

Number
Type
N-selectors
Local
00
Remote
00
Table 44. Recommended N - selectors for CLNS
1.2
SPIs for CONS communications

DX 200 (local) SPIs
AEN
Service type
SPI
<ne>0<ccccc>
CMISE/FTAM
03010100
<ne>0<ccccc>PAD
PAD
01000000
<ne>0<ccccc>MSW
MSW
C0000000
Table 45. DX 200 (local) SPIs for CONS

NMS (remote) SPIs
Service application type Channel group
SPI
CMISE/FTAM
OMCCMISE
03010100
PAD
OMCPAD
01000000
PAD
RTRPAD1
01000000
MSW
OMCMSW
C0000000
Table 46. NMS (remote) SPIs for CONS
NTC TAN 0839/2.2 en
175
NETWORK PROTOCOL ADDRESS NAMES

This chapter presents the recommendations for naming network protocol address
names in the DX 200 network elements.
2.1
CLNS network protocol address names

DX 200 (local) network protocol address names
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
Table 47. DX 200 (local) network protocol address names

NMS (remote) network protocol address names
Application type
Abbreviation
Remote network address

name
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
Table 48. NMS (remote) network protocol address names

Note:
When creating CLNS network protocol address names, all PAD and MSW network
protocol address names must be different. To ensure these names are different
use the numbering scheme presented above.
NTC TAN 0839/2.2 en
176
2.2
CONS network protocol address names

DX 200 (local) network protocol address names
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
Table 49. DX 200 (local) network protocol address names

NMS (remote) network protocol address names
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
Table 50. NMS (remote) network protocol address names

Note:
When creating CONS network protocol address names, all PAD and MSW network
protocol address names must be different. To ensure these names are different
use the numbering scheme presented above.
NTC TAN 0839/2.2 en
177
APPLICATION PARAMETERS
This chapter presents the parameters for creating the remote and local
applications in the DX 200 network elements and the NMS Communications
Server.
3.1
DX 200 applications
This section presents the DX 200 (local) application parameters for applications
in DX 200 network elements.
3.1.1
Item
DX 200 applications in the BSC

AEN
Unit
Type
Family
Network service
BSC0<bbbbb>F
OMU
VFS
CONS/CLNS
BSC0<bbbbb>VT
OMU
VTP
CONS/CLNS
BSC0<bbbbb>A
OMU
CMI
21F
CONS/CLNS
BSC0<bbbbb>EHA
OMU
CMI
2B1
CONS/CLNS
Table 51. DX 200 (local) applications in the BSC

5
BSC0<bbbbb>MSW
OMU
MSW
BSC0<bbbbb>PAD
OMU
PAD
CONS/CLNS
using X.25
CONS/CLNS
using X.25
Note:
In S6 the family for the BSC0<ccccc>EHA application is 2B1.
Item
AEN
P-selectors
S-selectors
T-selectors
BSC0<bbbbb>F
1133030210
1133030210
1133
BSC0<bbbbb>VT
2233030220
2233030220
2233
BSC0<bbbbb>A
3333030230
3333030230
3333
BSC0<bbbbb>EHA
3333030231
3333030231
3333
Table 52. DX 200 (local) applications in the BSC

5
6
BSC0<bbbbb>MSW
BSC0<bbbbb>PAD
NTC TAN 0839/2.2 en
178
3.1.2
DX 200 applications in the DAXnode WLL
Item
AEN
Unit
Type
Family
Network service
BSC0<bbbbb>F
OMU
VFS
CONS/CLNS
BSC0<bbbbb>VT
OMU
VTP
CONS/CLNS
BSC0<bbbbb>A
OMU
CMI
21F
CONS/CLNS
BSC0<bbbbb>EHA
OMU
CMI
2B1
CONS/CLNS
Table 53. DX 200 (local) applications in the DAXnode WLL

Item
AEN
Unit
Type
Family
Network service
BSC0<bbbbb>MSW
OMU
MSW
CONS/CLNS
using X.25
BSC0<bbbbb>PAD
OMU
PAD
CONS/CLNS
using X.25
Table 54. Local X.25 applications in the DAXnode WLL

Item
AEN
P-selectors
S-selectors
T-selectors
BSC0<bbbbb>F
1133030210
1133030210
1133
BSC0<bbbbb>VT
2233030220
2233030220
2233
BSC0<bbbbb>A
3333030230
3333030230
3333
BSC0<bbbbb>EHA
3333030231
3333030231
3333
Table 55. DX 200 (local) applications in the DAXnode WLL

Item
AEN
P-selectors
S-selectors
T-selectors
BSC0<bbbbb>MSW
BSC0<bbbbb>PAD
Table 56. Local X.25 applications in the DAXnode WLL
NTC TAN 0839/2.2 en
179
3.1.3
DX 200 applications in the MSC
Item
AEN
Unit
Type
Family
Network service
MSC0<mmmmm>FO
OMU
VFS
CONS/CLNS
MSC0<mmmmm>VT
OMU
VTP
CONS/CLNS
MSC0<mmmmm>A
OMU
CMI
21F
CONS/CLNS
MSC0<mmmmm>EHA
OMU
CMI
1F9
CONS/CLNS
Table 57. DX 200 (local) applications in the MSC

Item
AEN
Unit
Type
Family
Network service
MSC0<mmmmm>MSW
BDCU
MSW
CONS/CLNS
using X.25
MSC0<mmmmm>PAD
OMU
PAD
CONS/CLNS
using X.25
Table 58. Local X.25 applications in the MSC

Item
AEN
P-selectors
S-selectors
T-selectors
MSC0<mmmmm>FO
1133040210
1133040210
1133
MSC0<mmmmm>VT
2233040220
2233040220
2233
MSC0<mmmmm>A
3333040230
3333040230
3333
MSC0<mmmmm>EHA
3333040231
3333040231
3333
Table 59. DX 200 (local) applications in the MSC

Item
AEN
P-selectors
S-selectors
T-selectors
MSC0<mmmmm>MSW
MSC0<mmmmm>PAD
Table 60. Local X.25 applications in the MSC
NTC TAN 0839/2.2 en
180
3.1.4
DX 200 applications in the HLR
Item
AEN
Unit
Type
Family
Network service
HLR0<hhhhh>FO
OMU
VFS
CONS/CLNS
HLR0<hhhhhh>VT
OMU
VTP
CONS/CLNS
HLR0<hhhhh>A
OMU
CMI
21F
CONS/CLNS
HLR0<hhhhh>EHA
OMU
CMI
1F9
CONS/CLNS
Table 61. DX 200 (local) applications in the HLR

Item
AEN
Unit
Type
Family
Network service
HLR0<hhhhh>MSW
BDCU
MSW
CONS/CLNS
using X.25
HLR0<hhhhh>PAD
OMU
PAD
CONS/CLNS
using X.25
Table 62. Local X.25 applications in the HLR

Item
AEN
P-selectors
S-selectors
T-selectors
HLR0<hhhhh>FO
1133040210
1133040210
1133
HLR0<hhhhhh>VT
2233040220
2233040220
2233
HLR0<hhhhh>A
3333040230
3333040230
3333
HLR0<hhhhh>EHA
3333040231
3333040231
3333
Table 63. DX 200 (local) applications in the HLR

Item
AEN
P-selectors
S-selectors
T-selectors
HLR0<hhhhh>MSW
HLR0<hhhhh>PAD
Table 64. Local X.25 applications in the HLR
NTC TAN 0839/2.2 en
181
3.1.5
DX 200 applications in the Front End
Item
AEN
Unit
Type
Family
OMC0<ccccc>FO
OMU
VFS
OMC0<ccccc>VT
OMU
VTP
OMC0<ccccc>FP
OMU
VFS
OMC0<ccccc>EHA
OMU
CMI
1F9
OMC000000MSW0
BDCU
MSW
OMC000000MSW1
BDCU
MSW
OMC0<ccccc>FF
FCMU
VFS
OMC000000PAD
OMU
PAD
Table 65. DX 200 (local) applications and their units in the Front End
Item
AEN
P-selectors
S-selectors
T-selectors
OMC0<ccccc>FO
1133020210
1133020210
1133
OMC0<ccccc>VT
2233020220
2233020220
2233
OMC0<ccccc>FP
1133021B10
1133021B10
1133
OMC0<ccccc>EHA
3333020231
3333020231
3333
OMC000000MSW0
OMC000000MSW1
OMC0<ccccc>FF
1133021C10
1133021C10
1133
OMC000000PAD
Table 66. DX 200 (local) applications in the Front End

Item
AEN
Application
Local network address
OMC000000MSW0
MSW
LOCALMSW0
OMC000000MSW1
MSW
LOCALMSW1
OMC000000PAD
PAD
LOCALPAD
Table 67. DX 200 (local) applications for CONS communications in the FE
NTC TAN 0839/2.2 en
182
3.2
NMS applications
This section presents the NMS (remote) applications in DX 200 network element
and the NMS.
3.2.1
NMS applications in DX 200 network elements
Item
AEN
Type
P-selectors
S-selectors
T-select
OMC000000D1
CMI
3333010130
3333010130
3333
OMC000000BP
CMI
3333010131
3333010131
3333
OMC000000FP
VFS
1133010210
1133010210
1133
OMC000000SW
VFS
1133010110
1133010110
1133
CISCOPAD
PAD
Table 68. NMS (remote) applications in DX 200 network elements
NTC TAN 0839/2.2 en
183
3.2.2
DX 200 applications in the Communications Server
The following tables present the NMS applications for the DX 200 network
elements.
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
BSC0<bbbbb>F
1133030210
1133030210
1133
BSC0<bbbbb>VT
2233030220
2233030220
2233
BSC0<bbbbb>A
3333030230
3333030230
3333
BSC0<bbbbb>EHA
3333030231
3333030231
3333
MSC0<mmmmm>FO
1133040210
1133040210
1133
MSC0<mmmmm>VT
2233040220
2233040220
2233
MSC0<mmmmm>A
3333040230
3333040230
3333
MSC0<mmmmm>EHA
3333040231
3333040231
3333
HLR0<hhhhh>FO
1133040210
1133040210
1133
HLR0<hhhhhh>VT
2233040220
2233040220
2233
HLR0<hhhhh>A
3333040230
3333040230
3333
HLR0<hhhhh>EHA
3333040231
3333040231
3333
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
DAXnode
WLL
MSC
HLR
FE
Table 69. DX 200 (local) applications for the NMS Communications Server
NTC TAN 0839/2.2 en
184
NE
AEN
BSC
BSC0<bbbbb>F
oufmanmx1
VFS
BSC0<bbbbb>VT
ouvmanmx1
VTP
BSC0<bbbbb>A
oummanmx1
CMI
BSC0<bbbbb>EHA
oummanmx1
CMI
BSC0<bbbbb>F
oufmanmx1
VFS
BSC0<bbbbb>VT
ouvmanmx1
VTP
BSC0<bbbbb>A
oummanmx1
CMI
BSC0<bbbbb>EHA
oummanmx1
CMI
MSC0<mmmmm>FO
oufmanmx1
VFS
MSC0<mmmmm>A
oummanmx1
CMI
MSC0<mmmmm>VT
ouvmanmx1
VTP
MSC0<mmmmm>EHA
oummanmx1
CMI
HLR0<hhhhh>FO
oufmanmx1
VFS
HLR0<hhhhhh>VT
ouvmanmx1
VTP
HLR0<hhhhh>A
oummanmx1
CMI
HLR0<hhhhh>EHA
oummanmx1
CMI
OMC0<ccccc>FO
oufmanmx1
VFS
OMC0<ccccc>FP
oufmanmx1
VFS
OMC0<ccccc>FF
oufmanmx1
VFS
OMC0<ccccc>VT
oufmanmx1
VT
DAXnode
WLL
MSC
HLR
FE
NMS process
Application type
Table 70. NMS processes/application types for remote applications
NTC TAN 0839/2.2 en
185
Appendix G. Connection Server processes
Appendix G.
1
CONNECTION SERVER PROCESSES
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 managed
network (the Communications Server and the Database Server). The client
processes (for example, remote MML applications) run on any server in the
NMS workstation network.
After start-up, one server process and a number of APMs are started in the
workstation network. The server process listens to its dedicated port, ready to
server connection requests. It is the only process in the NMS that knows the
structure of the DCN and its current connection status. All connection requests
must pass through this server process. The Connection Server process does not
establish physical connections - it only keeps track of the available routes within
the network.
The physical routes are administered by APMs that check if the DCN is usable.
An APM can disable or enable routes by informing c4xcsxmx about route status
changes. Based on this information, c4xcsxmx can enable and disable routes in
its internal book-keeping.
NTC TAN 0839/2.2 en
186
CS server process architecture

After Communications Server (host) is booted for the first time and the
wpmanamx process starts:
1.
The c4xcsxmx server process starts and reads the connection server
configuration file (cnxcffmx.cf).
2.
The c4xcsxmx server process reads the dcn configuration file

(cnxdcnmx.cf).
3.
wpmanamx process begins to supervise the c4xcsxmx server process.
4.
The APM process starts, see Administrative protocol modules on page 188.
If there administrate routes are not defined or commented out, APMs are
not used.
5.
The c4xcsxmx server process writes log entries to the c4xcsxmx.log.

In the event of errors werlog4006.log is also written.
6.
The client makes a connection request.
7.
The PSM application process begins, see Protocol specific modules on

page 190.
Figure 28. Connection Server processes
NTC TAN 0839/2.2 en
187
ADMINISTRATIVE PROTOCOL MODULES

Administrative Protocol Modules (APMs) are perl checkscripts that verify if
the physical connection to the host is in working order and if it can establish a
connection to a specific protocol. APMs are activated when the Nokia NMS is
started and remain active as background processes. These checkscripts are listed
in the administrative route definitions section of the cnxdcnmx.cf
configuration file.
The c6xapmmx process handles all APMs. The different functions of the APMs
are implemented by.perl scripts started by the c6xapmmx main process. Four
checkscripts are provided with the Nokia NMS:
Checkscript
Purpose
c6xx25statmx.perl
Checks PAD connection in the NMS
c6xconmx.perl
Checks PAD connection in the NMS and DX

element
c6xftamx.perl
Checks FTAM connection in the NMS
c6xvtxmx.perl
Checks OSI VT connection in the NMS
Table 71. Administrative protocol modules

Note:
APMs run on all servers that contain network cards.
Figure 29. APM process path
NTC TAN 0839/2.2 en
188
Application protocol module process path using a PAD connection

After the NMS has been started, APMs use the following process path when
monitoring PAD connections. These modules constantly check the status of the
network at a user specified interval.
1.
During NMS start-up, the c4xcsxmx server process also starts and opens
the cnxdcnmx.cf configuration file.
2.
The c4xcsxmx server process reads the arc, route and administrative
route definitions for all PAD connections from the cnxdcnmx.cf.
3.
The c4xcsxmx processes that information and sends a request out to the
inetd daemon.
4.
The inetd daemon starts. Knowing the connection type (PAD) and all
possible routes, inetd starts the c6xapmmx process (APM main process).
5.
The c6apmmx process reads the cnxcffmx.cf configuration file.
6.
The c6apmmx 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 is

functional is returned to the APM main process.
9.
The c6xapmmx process forwards the message to the wnemgrmx

(Workstation Communications Services) process.
10.
The wnemgrmx process forwards the message to the c4xcsxmx server

process.
If a route is found to be inoperable, the APM sends a negative message to the

server process. This generates a workstation alarm and causes an error log file to
be written.
The APM then continues checking the connection at pre-defined intervals. When
the route becomes available again, the APM sends another message indicating
the status of the connection.
If the APM sends a message concerning a malfunction in a data communication
card, the server process disables all routes to that card. After the malfunction has
been corrected, the APM enables all routes to that card and forwards that
information to the CS process.
NTC TAN 0839/2.2 en
189
PROTOCOL SPECIFIC MODULES

Protocol specific modules (PSMs) implement connections to applications. Three
PSMs are provided with Nokia NMS:
Protocol specific module PSM process
c5xpadmx
Protocol
PAD
c5xftamx
oulfcpmx
FTAM
c5xstdmx
ouiswsmx
OSI VT
Table 72. Protocol-specific modules

Note:
Telnet connections are enabled by using the c5xstdmx PSM.
To implement FTAM or OSI VT connections, the use of host processes is
necessary. As the c5xpadmx uses the X.25 host service module for PAD
connections, no additional processes are needed. The implementation of each
connection is totally transparent to the client application.
Figure 30. PSM application process using a PAD connection
NTC TAN 0839/2.2 en
190
PSM application processes using a PAD connection

1.
A client in the Nokia NMS sends a connection request to the c4xcsxmx

server process. This requests includes the name or internal ID of host
(BSC) and the type of connection desired (PAD).
2.
The c4xcsxmx server process accepts the request, searches for the host
and reads the routing information in the cnxdcnmx.cf configuration file.
3.
The c4xcsxmx processes that information and sends a request out to the
inetd daemon.
4.
The inetd daemon starts. Knowing the host, connection type and route,
inetd starts the c5xpadmx process (PSM PAD process).
5.
The c5xpadmx PAD process reads the cnxcffmx.cf configuration file.
6.
The c5xpadmx 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.
The c5xpadmx PAD process reads the login/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 logs
provide information on who established a connection, what the connection was
used for and how long the connection was active.
If this feature is enabled, the PSM that makes the connection produces a session
log file (c5xpmx_<conn_ID>.log.). The <conn_ID> variable identifies the
individual connection.
To enable this feature, edit the node definitions section of the cnxdcnmx.cf
file. This feature is network element and connection type specific and a log file
is produced for each connection.
Symbols
/etc/services 62
NTC TAN 0839/2.2 en
191
INDEX
A
AC25-S
installing and configuring 83
jumpers 145
address
device information 66
network protocol 111
administrative protocol modules 188
c6xconmx.perl 188
c6xftamx.perl 188
c6xvtxmx.perl 188
c6xx25statmx.perl 188
administrative routes 72
AENs 120, 128, 175
APM checkscripts
c6xconmx.perl 188
c6xftamx.perl 188
c6xvtxmx.perl 188
APMs 72, 188
application entity names 120, 128, 175
arcs
naming 67
AS7-U
jumpers 150
B
backups
DCN configuration files 61
BBU-0 140
BSS integration
required managed objects 30
byte basket 140
C
c4xcsxmx 186
checkscripts 188
c6xconmx.perl 188
c6xftamx.perl 188
c6xvtxmx.perl 188
CLNS
over X.25 39
NTC TAN 0839/2.2 en
setting up objects in NE 104

setting up subnetworks 38
clusters 43
cnxcffmx.cf 65
cnxdcnmx.cf 61
cnxreconfigmx.perl 78
COCEN
jumpers 155
comm package 43
when used 44
communication modes
direct connections 144
indirect connections 144
Communications Server
package 43
configuration files
cnxdcnmx.cf 59
Connection Server 65
inetd.conf 63
osi 57
ots_dests 49
ouorapmx.cf 56
Connection Server
environment 65
processes 186
connection subtypes 76
creating physical channels
using PCM over digital X.25 98
D
DCN
configuration files 61
introduction 16
diagnos 140
documents 15
Hewlett Packard 15
installation guides 15
introductory 15
reference guides 15
system administrator guides 15
troubleshooting guides 15
DX 200
configuring 79
dynamic NSAPs 44
192
O&M connections data 131
end system connections

adding to Front End 142
error logs
werlog4006.log 187
werlog5011.log 191
evbfil 136
exchange terminals
linkage objects
broadcast 105
setting up in the NE 105
unlocking 106
local OSI applications
setting up in the NE 119
jumpers
AC25-S 145
AS7-U 151
COCEN 155
figures
admin route in cnxdcnmx.cf 73
APM processes 188
arc in cnxdcnmx.cf 68
basic DCN integration 22
comm package NSAP address 43
creating local CLNS applications 123
creating local CONS applications 120
creating remote OSI applications 132
CS processes 187
direct integration CONS 20
direct NE integration (CLNS) 18
indirect NE integration (CLNS) 19
network cards in DX 200 23
PSM processes 190
route in cnxdcnmx.cf 70
Setting up DX 200 connections 80
flowcharts
OSI application configuration 118
preliminary tasks 25
FTAM 66
checking 188
G
gsmme1mg 138
H
hostnames 164, 165, 167
I
inetd 63
Internet superserver 63
interrogation commands
hostnames 164, 165, 167
network protocol addresses 110, 114
NSAPs 110, 114
NTC TAN 0839/2.2 en
M
managed objects
BSS integration 30
creating 30
NSS integration 30
manual adjacencies
adding 107
MC/ServiceGuard 44
meafil 136, 139
mscmea01mg 138
N
network addresses
setting up for CONS 113
network cards
AC25-S 145
AS7-U 150
COCEN 154
network protocol addresses
creating 108, 113
network services
setting up in NE 103
setting up using CLNS 104
setting up using CONS 46, 112
NMS Communications Server
configuring 34
nodes 43
adding definitions 74
adoptive 44
primary 44
NSAPs
attaching 111
193
dynamic 44
setting up for CONS 113
unlocking 111
NSS integration
required managed objects 30
NULL subaddressing 58
O
O&M connections
adding 130
obsfil 136, 138
omcalarm 140
OSI
transport services 66
OSI destination systems
adding 48
OSI environment
configuring 52
configuring in the NE 118
OSI subnetwork
setting up in Communications Server 37
OSI VT
checking 188
osiadmin 35
osiconfchk 51
ots_dests 49
ots_routes 51
ots_subnets 58
ouorapmx.cf 56, 57
P
packages
comm 43
PAD
checking 188
connections 70
setting up in the NMS 53
physical channels 87
assigning a channel group using analog
X.25 88, 99
creating using analog X.25 87
physical connections
setting up in DX 200 80
setting up in the NE using LAN 100
setting up using analog X.25 (PSN) 80
setting up using digital X.25 (PCM) 89
verifying in the NE 88
plug-in units
AC25-S 145
AS7-U 150
NTC TAN 0839/2.2 en
COCEN 154
prerequisites
MSC/HLR 28, 29
NMS 27
protocol-specific modules 190
c5xftamx 190
c5xpadmx 190
c5xstdmx 190
PSM processes
ouiswsmx 190
oulfcpmx 190
PSMs 190
c5xftamx 190
c5xpadmx 190
c5xstdmx 190
R
references 15
remote applications
setting up 56
routes
adding 70
administrative 72
naming 67
routing tables 44
S
session logs 191
c5xpmx_.log 191
sgscusmx.cf 43
software
M7B 134, 135, 136
SPIs 108, 113
states
changing 131
T
tables
routing 44
U
unlocking
linkage objects 106
NSAPs 111
V
virtual
194
report converter 140

VRP-0 140
W
werlog4006.log 78
X
X.25
initialization file 165
X.25 parameter sets
creating and modifying 86, 97
X.29
hosts file 53
server 55
x25config_* 165
Z
ZIIL 136, 137
ZIIS 136
ZQDI
APL=LCL 121, 124
ZUSU 141
NTC TAN 0839/2.2 en
195
NTC TAN 0839/2.2 en
196

DCN Integration PDF

Uploaded by

Document Information

Original Title

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

DCN Integration PDF

Uploaded by

Copyright:

Available Formats

NOKIA NMS/2000

FOR MANAGING CELLULAR NETWORKS

NTC TAN 0839/2.2 en

Copyright Nokia Telecommunications Oy

Copyright Nokia Telecommunications Oy 1998. All rights reserved.

NTC TAN 0839/2.2 en

Copyright Nokia Telecommunications Oy

ABOUT THIS MANUAL . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8

What you need to know first . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8

INTRODUCTION TO DCN INTEGRATION. . . . . . . . . . . . . . . . . . . 16

Changes from T9 to T10 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7

Filling in the configuration sheets . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

CONFIGURING THE NMS COMMUNICATIONS SERVER. . . . . 34

Enabling X.121 subaddressing. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

NTC TAN 0838/2.2 en

Copyright Nokia Telecommunications Oy

5.2.1.3 Communications Server package. . . . . . . . . . . . . . . . . .

CONFIGURING CONNECTION SERVER SOFTWARE . . . . . . . . 59

Backing up the DCN configuration file . . . . . . . . . . . . . . . . . . . . . . . . . . .

CONFIGURING THE DX 200 NETWORK ELEMENT . . . . . . . . . . 79

Setting up the physical connection. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 80

NTC TAN 0839/2.2 en

Copyright Nokia Telecommunications Oy

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

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

AC25-S NETWORK CARD. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 145

AS7-U NETWORK CARD. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 150

COCEN NETWORK CARD . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 154

Jumper blocks. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 155

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

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

NTC TAN 0839/2.2 en

Copyright Nokia Telecommunications Oy

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

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

CONFIGURING THE NMS COMMUNICATIONS SERVER. . . . 171

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

CONFIGURING THE CONNECTION SERVER SOFTWARE . . 173

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

N - SELECTORS AND SPIS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 175

NETWORK PROTOCOL ADDRESS NAMES. . . . . . . . . . . . . . . . . 176

N - selectors for CLNS communications . . . . . . . . . . . . . . . . . . . . . . . . . 175

CLNS network protocol address names . . . . . . . . . . . . . . . . . . . . . . . . . . 176

APPLICATION PARAMETERS . . . . . . . . . . . . . . . . . . . . . . . . . . . . 178

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

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

PROTOCOL SPECIFIC MODULES . . . . . . . . . . . . . . . . . . . . . . . . . 190

Session logs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 191

NTC TAN 0839/2.2 en

Copyright Nokia Telecommunications Oy

Changes from T9 to T10

Information regarding integration from a router or Front End to the NMS

Integration information regarding the DAXnode 5000 wireless local loop

Section 4.2, Reviewing the system requirements on page 27 has been

Section 5.2.1.3, Communications Server package on page 43 has been

In Appendix C., Configuration information on page 160, all tables have

NTC TAN 0839/2.2 en

Copyright Nokia Telecommunications Oy

About this manual

ABOUT THIS MANUAL

What you need to know first

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

GSM/DCS/PCS cellular networks