OSP Platform For GSM/EDGE BSS: OSI Guide

OSP Platform for GSM/EDGE
BSS
OSI Guide
DN9812567
Issue 14-1
OSI Guide
The information in this document applies solely to the hardware/software product (“Product”) specified
herein, and only as specified herein. Reference to “Nokia” later in this document shall mean the respective
company within Nokia Group of Companies with whom you have entered into the Agreement (as defined
below).
This document is intended for use by Nokia's customers (“You”) only, and it may not be used except for the
purposes defined in the agreement between You and Nokia (“Agreement”) under which this document is
distributed. No part of this document may be used, copied, reproduced, modified or transmitted in any form
or means without the prior written permission of Nokia. If You have not entered into an Agreement
applicable to the Product, or if that Agreement has expired or has been terminated, You may not use this
document in any manner and You are obliged to return it to Nokia and destroy or delete any copies thereof.
The document has been prepared to be used by professional and properly trained personnel, and You
assume full responsibility when using it. Nokia welcomes your comments as part of the process of
continuous development and improvement of the documentation.
This document and its contents are provided as a convenience to You. Any information or statements
concerning the suitability, capacity, fitness for purpose or performance of the Product are given solely on
an “as is” and “as available” basis in this document, and Nokia reserves the right to change any such
information and statements without notice. Nokia has made all reasonable efforts to ensure that the
content of this document is adequate and free of material errors and omissions, and Nokia will correct
errors that You identify in this document. Nokia's total liability for any errors in the document is strictly
limited to the correction of such error(s). Nokia does not warrant that the use of the software in the Product
will be uninterrupted or error-free.
NO WARRANTY OF ANY KIND, EITHER EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO
ANY WARRANTY OF AVAILABILITY, ACCURACY, RELIABILITY, TITLE, NON-INFRINGEMENT,
MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE, IS MADE IN RELATION TO THE
CONTENT OF THIS DOCUMENT. IN NO EVENT WILL NOKIA BE LIABLE FOR ANY DAMAGES,
INCLUDING BUT NOT LIMITED TO SPECIAL, DIRECT, INDIRECT, INCIDENTAL OR CONSEQUENTIAL
OR ANY LOSSES, SUCH AS BUT NOT LIMITED TO LOSS OF PROFIT, REVENUE, BUSINESS
INTERRUPTION, BUSINESS OPPORTUNITY OR DATA THAT MAY ARISE FROM THE USE OF THIS
DOCUMENT OR THE INFORMATION IN IT, EVEN IN THE CASE OF ERRORS IN OR OMISSIONS
FROM THIS DOCUMENT OR ITS CONTENT.
This document is Nokia proprietary and confidential information, which may not be distributed or disclosed
to any third parties without the prior written consent of Nokia.
Nokia is a registered trademark of Nokia Corporation. Other product names mentioned in this document
may be trademarks of their respective owners.
Copyright © 2016 Nokia. All rights reserved.
f Important Notice on Product Safety

This product may present safety risks due to laser, electricity, heat, and other sources of danger.
Only trained and qualified personnel may install, operate, maintain or otherwise handle this
product and only after having carefully read the safety information applicable to this product.
The safety information is provided in the Safety Information section in the “Legal, Safety and
Environmental Information” part of this document or documentation set.
Nokia is continually striving to reduce the adverse environmental effects of its products and services. We
would like to encourage you as our customers and users to join us in working towards a cleaner, safer
environment. Please recycle product packaging and follow the recommendations for power use and proper
disposal of our products and their components.
If you should have questions regarding our Environmental Policy or any of the environmental services we
offer, please contact us at Nokia for any additional information.
2 © 2016 Nokia DN9812567 Issue: 14-1

OSI Guide
Table of Contents
This document has 222 pages
Summary of changes ...................................................................11
1 DX 200 OSI environment............................................................. 12

1.1 Required OSI services................................................................. 14
1.2 OSI vendors involved................................................................... 15
1.3 Determine the OSI network structure...........................................16
1.4 OSI addressing scheme...............................................................22
1.5 Data terminals of the PCI bus based DX 200.............................. 28
1.6 Usage of data terminals in OSI connections................................ 28
1.7 X.25 subnetwork (CONS).............................................................29
1.8 Alternative remote NSAP address............................................... 32
1.9 OSI measurements...................................................................... 33
1.10 Usage of OSI file service commands........................................... 37
1.11 O23MTS service terminal extension............................................ 39
1.12 FTAM user account management................................................ 40
1.13 OSI security..................................................................................41
1.14 Sources of information on OSI errors and alarms........................44
1.15 Logic of the conversion program..................................................44
2 Example configuration of an ES with LAN interface.....................46

2.1 Structure of example network in ES with LAN interface...............46
2.2 Configuration information of ES with LAN....................................46
2.3 Configuration sheets for ES with LAN..........................................47
2.4 ES with LAN - summary of configuration steps............................51
2.5 Configuration inquiries of ES with LAN........................................ 52
3 Example configuration of an IS with LAN and X.25 interfaces.....54

3.1 Structure of an example network in IS with LAN and X.25
interfaces......................................................................................54
3.2 Configuration information of IS with LAN and X.25 interfaces..... 54
3.3 Configuration sheets for IS with LAN and X.25 interfaces........... 57
3.4 IS with LAN and X.25 - summary of configuration steps..............66
3.5 Configuration inquiries for IS with LAN and X.25 interfaces........ 68
4 Example configuration of an ES with LAN and X.25 interfaces... 73

4.1 Structure of an example network in ES with LAN and X.25
interfaces......................................................................................73
4.2 Configuration information of ES with LAN and X.25 interfaces....73
4.3 Configuration sheets for ES with LAN and X.25 interfaces..........74
4.4 ES with LAN and X.25 - summary of configuration steps............ 77
4.5 Configuration inquiries for ES with LAN and X.25 interfaces....... 78
5 Example configuration of OSI over TCP/IP interface................... 82

5.1 Structure of an example network................................................. 82
DN9812567 Issue: 14-1 © 2016 Nokia 3

OSI Guide
5.2 OSI over TCP/IP - summary of configuration steps..................... 82

5.3 Configuration inquiries of OSI over TCP/IP..................................83
6 Defining local DX 200 OSI environment.......................................85

6.1 Defining AS7–C or AS7–D data terminal..................................... 85
6.2 Creating connection-oriented network service (CONS)............... 87
6.3 Creating connectionless network service (CLNS)........................88
6.4 Defining local OSI addresses.......................................................90
6.5 Defining local OSI applications.................................................... 94
6.5.1 Creating local network addresses................................................ 95
6.5.2 Creating local OSI applications.................................................... 97
6.5.3 Defining selectors for applications............................................... 98
7 Defining remote OSI environment..............................................101

7.1 Defining remote NSAP addresses............................................. 101
7.2 Defining remote network addresses...........................................104
7.3 Defining remote OSI applications...............................................105
7.4 Using access control list.............................................................107
7.5 Creating FTAM user profile........................................................ 108
8 Verifying your OSI configuration................................................. 110

8.1 Verifying OSI network service.....................................................110
8.2 Verifying FTAM service...............................................................112
8.3 Converting the OSI configuration information.............................115
8.3.1 Preparing the conversion of the OSI configuration information........
115
8.3.2 Converting the OSI configuration information.............................116
8.3.3 Converting the OSI parameter file..............................................121
9 OSI troubleshooting................................................................... 123

9.1 Checking the status of the links, the OSI stack, and the services....
123
10 Common OSI configuration mistakes.........................................130

10.1 Creation of the physical channels fails.......................................130
10.2 Problems with Ethernet.............................................................. 130
10.3 Problems with X.25 interface..................................................... 130
10.4 Problems with CLNS linkage state.............................................133
10.5 CLNS configuration problems.................................................... 134
10.6 Networking problems................................................................. 136
10.7 CLNS routing problems..............................................................138
10.8 Problems with establishing OSI connection............................... 139
10.9 Application errors....................................................................... 143
10.10 Changing CP4HX based computer unit to CP6LX.....................144
11 Defining and starting an OSI measurement............................... 146
12 Using O23MTS service terminal extension................................ 148

12.1 Monitoring statistics of OSI layers 1 - 4......................................149
4 © 2016 Nokia DN9812567 Issue: 14-1

OSI Guide
12.2 Monitoring status information of X.25.........................................153

12.3 Displaying the contents of OSI management files..................... 154
12.3.1 OSI File Checker........................................................................155
12.3.2 Current OSI sessions................................................................. 157
12.3.3 Registered OSI service processes.............................................157
12.3.4 Registered OSI terminals........................................................... 158
12.3.5 Dynamic linkage information (OMLFIL)......................................161
12.3.6 Information on distributed parts of CLNS (OMDFIL).................. 161
12.3.7 Dynamic information on CLNS (OMNFIL)..................................161
12.4 Monitoring X.25 traffic................................................................ 161
12.4.1 On-line analysis of X.25 frames................................................. 162
12.4.2 Analysis of X.25 frames stored into the ring buffer.................... 164
12.4.3 Storing captured frames into ring buffer - no analysis................164
12.5 Capturing transport protocol data...............................................165
12.5.1 On-line analysis of transport protocol data units (TPDUs)......... 165
12.5.2 Analysis of TPDUs stored into the ring buffer............................ 167
12.5.3 Storing captured TPDUs into ring buffer - no analysis............... 168
12.6 Monitoring X.25 acknowledgement delays.................................169
12.6.1 Defining the terminal to be monitored........................................ 169
12.6.2 Monitoring and resetting link level acknowledgement statistics. 170
12.6.3 Monitoring link level acknowledgement statistics - no resetting.170
12.6.4 Enabling packet level acknowledgement monitoring................. 171
12.6.5 Inquiring packet level acknowledgement statistics.....................171
12.6.6 Time-out delay adjustment......................................................... 172
12.7 Inquiring IS-IS routing information..............................................172
12.7.1 CLNS adjacency information......................................................173
12.7.2 CLNS destination information.................................................... 174
12.8 Testing MAC Ethernet interface................................................. 175
12.8.1 Monitoring MAC statistics in the DMC bus based DX 200 network
element...................................................................................... 175
12.8.2 Monitoring MAC statistic in the PCI bus based DX 200 network
element...................................................................................... 177
13 AS7-C and AS7-D switch block and connectors........................ 179

13.1 AS7-C C105007......................................................................... 179
13.2 AS7-D C110791......................................................................... 181
14 Parameters of X.25.................................................................... 185
15 Parameters of CLNS.................................................................. 189
16 Counters of CLNS...................................................................... 193
17 OSI configuration sheets............................................................196
18 DX 200 and standard FTAM error codes....................................206

18.1 DX 200 FTAM error codes..........................................................206
18.2 Standard FTAM error codes....................................................... 207
DN9812567 Issue: 14-1 © 2016 Nokia 5

OSI Guide
19 Notices, disturbances, and alarms initiated by the DX 200 OSI

software......................................................................................215
6 © 2016 Nokia DN9812567 Issue: 14-1

OSI Guide
List of Figures
Figure 1 DX 200 OSI stack............................................................................... 13
Figure 2 MML command groups for creating an OSI configuration.................. 14
Figure 3 Example of a network map................................................................. 17
Figure 4 Example of routing network elements within a routing domain.......... 18
Figure 5 Benefits of OSI Routing...................................................................... 21
Figure 6 RFC1006 adaptation architecture.......................................................22
Figure 7 Usage of selectors..............................................................................23
Figure 8 NSAP address interpretation.............................................................. 24
Figure 9 OSI applications, network address, and NSAP addresses.................29
Figure 10 Using an alternative physical channel when the physical connection is
lost...................................................................................................... 30
Figure 11 Assigning a specific set of physical channels for applications............31
Figure 12 Prioritisation of existing subnetworks................................................. 31
Figure 13 Binding the local application to an X.25 permanent virtual circuit...... 32
Figure 14 Example of choosing an alternative remote NSAP address...............33
Figure 15 Network structure of an example network in ES with LAN................. 46
Figure 16 Network structure of an example network in IS with LAN and X.25... 54
Figure 17 Network structure of an example network in ES with LAN and X.25......
73
Figure 18 OSI over TCP/IP solution for CBC, Q3 and Node manager connection.
82
Figure 19 Usage of local network address......................................................... 95
Figure 20 Adjacencies and destinations as seen by the DX 200......................172
Figure 21 Connectors and micro switches of AS7-C........................................ 179
Figure 22 Connectors and micro switches of AS7-D........................................ 181
Figure 23 Connectors and micro switches of AS7-D........................................ 182
DN9812567 Issue: 14-1 © 2016 Nokia 7

OSI Guide
List of Tables
Table 1 Examples of interoperability between DX 200 OSI products and some
corresponding products from other vendors.......................................16
Table 2 All possible states of CLNS object (administrative state — status —
operational state)................................................................................20
Table 3 Example of ISO Data Country Code (DCC) NSAP address...............25
Table 4 Example of ISO 6253-International Code Designator (ICD) NSAP
address...............................................................................................26
Table 5 Subsequent Protocol Identifiers of network layer............................... 26
Table 6 NTC de facto selector values for OSI applications............................. 27
Table 7 OSI stack layers and their logical files................................................34
Table 8 CLNS configuration sheet...................................................................48
Table 9 Broadcast linkage configuration sheet for ES1...................................48
Table 10 N-selector NSAP configuration sheet................................................. 48
Table 11 Local network address configuration sheet for transport layer........... 48
Table 12 Local application configuration sheet for FTAM..................................48
Table 13 Local application configuration sheet for CMISE................................49
Table 14 Local application configuration sheet for VT.......................................49
Table 15 CLNS NSAP configuration sheet for OMC......................................... 50
Table 16 Remote network address configuration sheet for ES1....................... 50
Table 17 Remote application configuration sheet for OMC CMISE.................. 50
Table 18 Configuration sheet for AS7-C............................................................57
Table 19 Physical channel group configuration sheet for local PVC channel... 57
Table 20 Physical channel group configuration sheet for TOPCKNET............. 58
Table 22 PVC X.25 linkage configuration sheet for IS2.................................... 58
Table 23 SVC X.25 linkage configuration sheet for IS2.................................... 58
Table 24 SVC X.25 linkage configuration sheet for ES2................................... 59
Table 25 Broadcast linkage configuration sheet for ES1...................................59
Table 26 Local X.25 NSAP configuration sheet for PAD................................... 59
Table 27 Local X.25 NSAP configuration sheet for transport layer................... 59
Table 28 Local PVC X.25 NSAP configuration sheet for MSW......................... 59
Table 30 Local network address configuration sheet for PAD........................... 60
Table 32 Local network address configuration sheet for MSW......................... 60
Table 33 Local application configuration sheet for MSW.................................. 60
Table 35 Local application configuration sheet for PAD.................................... 61
Table 36 Local application configuration sheet for VT.......................................62
8 © 2016 Nokia DN9812567 Issue: 14-1

OSI Guide
Table 37 Remote X.25 NSAP configuration sheet for IS2 PAD.........................62

Table 38 Remote X.25 NSAP configuration sheet for IS2 transport layer.........62
Table 39 Remote X.25 NSAP configuration sheet for ES2 transport layer....... 62
Table 40 CLNS NSAP configuration sheet for ES1 transport layer...................63
Table 41 CLNS NSAP configuration sheet for IS1 transport layer.................... 63
Table 42 Remote network address configuration sheet for ES1 transport layer...
63
Table 43 Remote network address configuration sheet for IS2 transport layer.....
63
Table 44 Remote network address configuration sheet for IS2 PAD................ 64
Table 45 Remote network address configuration sheet for ES2 transport layer...
64
Table 46 Remote application configuration sheet for ES1 CMISE.................... 64
Table 47 Remote application configuration sheet for ES2 CMISE.................... 64
Table 48 Remote application configuration sheet for ES1 FTAM...................... 65
Table 49 Remote application configuration sheet for IS2 FTAM....................... 65
Table 50 Remote application configuration sheet for IS2 PAD..........................65
Table 51 Configuration sheet for AS7-D............................................................75
Table 53 Broadcast linkage configuration sheet for ES.....................................75
Table 58 Local network address configuration sheet for PAD........................... 76
Table 60 Local application configuration sheet for PAD.................................... 77
Table 61 Selector values for NTC applications................................................. 98
Table 62 Possible states of X.25 data terminals............................................. 124
Table 63 Possible states of NSAP addresses................................................. 125
Table 64 Possible states of OSI addresses.....................................................125
Table 65 Possible states of linkages............................................................... 126
Table 66 Possible states of CLNS objects...................................................... 126
Table 67 Location of failure determined according to the program block sending
the alarm...........................................................................................128
Table 68 New linkage has been created and the user has forgotten to unlock it..
133
Table 69 Reasons for linkage operational state DIS....................................... 133
Table 70 CLNS related errors returned by MML commands...........................134
Table 71 X.25 call clearing cases....................................................................136
Table 72 Outgoing call error cases..................................................................139
DN9812567 Issue: 14-1 © 2016 Nokia 9

OSI Guide
Table 73 Incoming call error cases..................................................................140

Table 74 Output fields of transport traffic analysis for different TPDUs...........166
Table 75 Ethernet interface error cases.......................................................... 176
Table 76 Ethernet interface error cases.......................................................... 178
Table 77 SW1 switch settings......................................................................... 179
Table 78 Interchangeability code settings....................................................... 180
Table 79 Switch settings (SWA)...................................................................... 182
Table 80 Interchangeability code settings....................................................... 183
Table 81 FTAM error codes 1000–1017.......................................................... 207
Table 87 Notices initiated by DX 200 OSI software.........................................215
Table 88 Disturbances initiated by DX 200 OSI software................................215
Table 89 Alarms initiated by DX 200 OSI software......................................... 217
10 © 2016 Nokia DN9812567 Issue: 14-1

OSI Guide Summary of changes
Summary of changes
Changes between document issues are cumulative. Therefore, the latest document
issue contains all changes made to previous issues.
Changes made between issues 14-1 and 14-0

Editorial change.
Changes made between issues 14-0 and 13-0

AS7 related contents have been added to the document.
Chapter Data terminal jumper settings has been removed.
Chapter AS7-C and AS7-D switch block and connectors has been added.
Changes made between issues 13-0 and 12–0

Section "Converting the OSI parameter information" has been added to Chapter 8
"Verifying your OSI configuration".
Alarm 2263 and 2735 have been added to Chapter 19 "Notices, disturbances, and
alarms initiated by the DX 200 OSI software".
DN9812567 Issue: 14-1 © 2016 Nokia 11

DX 200 OSI environment OSI Guide
1 DX 200 OSI environment

Open Systems Interconnection (OSI) Reference Model defines a seven-layer protocol
stack for computer communication purposes between OSI applications. The OSI model
includes standardised application protocols for various services, such as file and
management data transfer.
There are implementations of the OSI model for several environments, for example, for
DX 200. The services supported by the DX 200 OSI software are the following:
• FTAM for file transfer

• VT for virtual terminal over IEEE 802.3 LAN and X.25
• CMISE for transmission of management data
• SMRSE for short message service
• Transport Service for applications needing reliable end-to-end data transfer
• PAD for terminal session over X.25
• Virtual PAD Printer for remote printing facilities over X.25
• CONS for connection-oriented network service over X.25
• CLNS for connectionless network service over IEEE 802.3 LAN and X.25
• CONS for connection-oriented network service over TCP/IP (RFC 1006)
g Note: Notice
For mcBSC, there are three types of configurations: stand-alone mcBSC, combined
mcBSC with TRX capacity extension to FlexiBSC and combined mcBSC with PS
datacapacity extension to FlexiBSC. Only in the combined configurations is X.25
supported.
The structure of the DX 200 OSI stack is presented in the following figure.
12 © 2016 Nokia DN9812567 Issue: 14-1

OSI Guide DX 200 OSI environment
Figure 1 DX 200 OSI stack
non-OSI OSIapplications
applications
FTAM VT CMISE SMRSE
ACSE ROSE
Presentationlayer
Sessionlayer
Transport
service user
TP class0 Transport layer TP class4
CONS CLNS
PAD
CONSnetwork
service user ISOIP,
ES-IS,
SNDCF
TCP X.25packetlevel IS-IS
IP X.25datalinklevel LLC
Ethernetinterface physicallevel CSMA/CD
LAN X.25 LAN
Before OSI communication can take place in a DX 200 network element, you need to
define and describe the following:
• the OSI configuration of the local Open System: data terminals, interface
parameters, and so on
• the addresses that are used in application associations
• the applications using OSI stack in local and remote open systems
• how local OSI resources are used in application associations
Configuration command groups

The following figure presents the command groups used for configuring different parts of
the OSI system.
DN9812567 Issue: 14-1 © 2016 Nokia 13

Figure 2 MML command groups for creating an OSI configuration
1.1 Required OSI services
When you start planning your network, you must first determine the OSI services that are
needed to solve your communication problems. This can be done based on your data
transfer requirements.
In a DX 200 network element, various OSI services are selected using the software
package options below.
FTAM
FTAM provides you with a file transfer and management facility either over an OSI
connection-oriented (CONS) or connectionless (CLNS) network service. A DX 200
network element can be either the initiator or the responder of an FTAM file transfer.
CMISE
CMISE provides you with a management information transfer facility between the
manager and agents either over an OSI connection-oriented (CONS) or connectionless
(CLNS) network service.
VT
14 © 2016 Nokia DN9812567 Issue: 14-1

VT provides you with a remote login facility either over an OSI connection-oriented
(CONS) or connectionless (CLNS) network service. A DX 200 network element can act
only as a responder in a VT connection.
PAD
PAD provides you with a remote login facility over an X.25 connection. A DX 200 network
element may be the initiator or the responder of a PAD connection.
Virtual PAD Printer

Virtual PAD Printer provides you with a printing facility over an X.25 connection. Printer
output is redirected from a DX 200 network element to the X.25 network after the remote
end has established the X.25 connection.
Short Message Service

Short Message Service provides you with the transfer of short messages between the
MSC and the short message center.
Transport Layer Service

Transport Layer Service provides you with access to the services of the transport layer.
User-defined applications can use the transfer services directly for inter-process
communication.
You should also consider the required quality of service by establishing the desired level
of performance, connectivity, and error rate. These may have an effect on the
parameters of the transport and network layers.
1.2 OSI vendors involved

Supported Services
To resolve the complete layout of your network, you need to evaluate the equipment
used in communication. Ensure that all network elements provide the services necessary
to support end-to-end communication.
For example, when considering an FTAM transfer from network element A to B, you
must ensure that:
• the network elements have an interoperable FTAM implementation.

• communication network between A and B supports OSI data communication. The
provided network service can be either connection-oriented (CONS) or
connectionless (CLNS).
• you have the authorisation for file transfer, for example, you know the user
identification and file system password of the network elements.
Interoperability
To establish a successful data transfer between network elements, you must have
interoperable OSI implementations in them. Every vendor should provide PICS
proformas for their implementations. These can be used to determine whether two
implementations are interoperable or not. Implementations should conform to one
DN9812567 Issue: 14-1 © 2016 Nokia 15

another and they should support compatible versions and functional units.
Implementations should also have links to the required subnetwork (for example, LAN or
X.25).
Examples of interoperability between DX 200 OSI products and corresponding products
from other vendors are presented in the table below. The list is not complete. Only some
implementations have been listed here. Other OSI vendors usually provide similar lists
for their products.
Table 1 Examples of interoperability between DX 200 OSI products and some

corresponding products from other vendors
OSI product/ vendor FTAM VT CMISE SMR PAD X.25 ES/IS IS/IS
Bull DPS-6 x ? ? ? x x ? N/A
Cisco Router N/A N/A N/A N/A N/A x x x
DEC Ultrix x ? ? ? x x x N/A
DEC VAX/VMS x ? ? ? x x x ?
HP/UX x ? ? ? x x x N/A
IBM AIX x ? ? ? ? ? x N/A
NTC OSI in Unix x x x x N/A N/A N/A N/A
Siemens Open FT x N/A N/A N/A N/A N/A x N/A

(Windows NT)
SunOS ? ? ? ? x x ? N/A
Tandem x ? ? ? x x ? N/A
x product is interoperable with the

corresponding DX 200 OSI product
— product is not interoperable with the

corresponding DX 200 OSI product
? interoperability is not tested
N/A not applicable/relevant
1.3 Determine the OSI network structure

Network elements to be connected
16 © 2016 Nokia DN9812567 Issue: 14-1

To resolve the structure of your network you first identify the network elements and
connections between them. At this point you should assign a unique name and system
identifier to each OSI network element (preferably the C-number of the DX 200 network
element) if they are not already given. You also need to determine who is responsible for
the maintenance of the network elements.
Choosing between CONS and CLNS

After identifying the network elements, resolve the subnetworks needed for getting all the
network elements connected. It is useful to draw a network map presenting all the
network elements and subnetworks with their type. See the figure Example of a network
map. Managing the network is easier if there is a clear picture of the whole network
structure.
Figure 3 Example of a network map
DX200C
DX200 A
802.3subnet A WORKSTATIONX
X.25subnetwork
DX200B
router AA
(Level2IS) DX200D WORKSTATION Y
802.3subnetB
You can use both the connection-oriented network service (CONS) and the
connectionless network service (CLNS) in your network at the same time. If OSI over
TCP/IP feature is in use, other transferring mode cannot be used at the same time. The
structure of your network dictates the required network service:
• CONS is sufficient if your network consists of only two network elements which are
connected to the X.25 subnetwork.
• you need CLNS if you have several network elements in LAN or X.25 subnetworks
and you need a network connection where there are network elements between the
end points: OSI routing of CLNS enables the network elements to recognise other
elements even if they are not in the same subnetwork.
• If OSI over TCP/IP feature is in use, there can be several networks elements with
different subnetwork.
OSI routing in connectionless networks (CLNS)
DN9812567 Issue: 14-1 © 2016 Nokia 17

The OSI protocol suite includes several routing protocols and one router discovery
protocol. An OSI network consists of routing domains. A routing domain is a part of an
OSI network that is under common administrative authority. Any routing domain can be
defined as one or more areas (see the figure below).
The term End System (ES) refers to a non-routing network element. Intermediate
System (IS) refers to a router. The routing protocols of the suite are End System to
Intermediate System routing protocol (ES-IS) and Intermediate System to Intermediate
System intra-domain routing protocol (IS-IS). Routing within an area is called level 1
routing and routing between the areas is called level 2 routing. An IS that routes only
within one area is called a Level 1 IS. A Level 1 IS needs to know only the ESs and other
Level 1 ISs within its own area and the nearest Level 2 IS (backbone router) if there is
one.
Figure 4 Example of routing network elements within a routing domain
Area A
DX200C
DX200 A ES
Level1IS
WORKSTATIONX
802.3subnet A ES
X.25subnetwork
DX200B
ES
router AA
(Level2IS) DX200D WORKSTATION Y
ES
ES
802.3subnetB
AreaB
IS intermediate system
ES end system
CLNS data transfer optimisation

By default, all incoming and outgoing data transfer using Connectionless Network
Service (CLNS) is routed via single point, that is, Network Service User (NS-User). The
unit of the NS-User is set with the QEC command when CLNS data are created. The task
of the NS-User, that is, the O54LRS program block, is to handle transport connections
established by remote and local OSI applications.
18 © 2016 Nokia DN9812567 Issue: 14-1

When the O54LRS receives data from upper layers, it sends the data to the OFFICE
program block located in its own unit. OFFICE selects the most optimal linkage for the
data transfer. If the linkage resides in the same unit, the data can be sent directly to the
network via that linkage, but if the linkage is located in another unit, then the data is sent
via another OFFICE of the unit where that linkage is located. When the linkage receives
data from the network, it sends it to the OFFICE program block of its own unit. OFFICE
forwards the data to the O54LRS program block that is configured to be the NS-User.
The CLNS can utilise redundant linkages in data transfer, so it is possible that data
belonging to a certain Transport connection is received via several linkages and
computer units. Also the cost metrics of linkages may vary during Transport connections
and move data flow from one linkage to another. The dynamic nature of CLNS linkage
utilisation makes it difficult to distribute Transport level processing without having a
mechanism to identify a correct O54LRS program block. In a DX environment, such a
mechanism exists and it is described in this section below.
N-selector value mapping

The optimisation of CLNS data transfer is based on the full utilisation of the N-selector
value range. N-selector is a part of CLNS NSAP structure and it is used locally to identify
an NS-User within a computer system. In a DX environment, the N-selector value 'FF'
(0xFF) in a local NSAP means that all the data transfer identified with this NSAP is
routed via the default NS-User. Values other than this are interpreted so that they
actually identify the computer unit where a desired NS-User reside. If it is not possible to
decide the target unit on the basis of the N-selector value or the target unit does not
contain an O54LRS program block, then the unit of the default NS-User is selected.
When the target unit is duplicated, then the active unit is selected automatically.
DX 200 extension to ES network element

The OSI routing protocols do not offer prioritising of the subnetworks in ES network
elements. When the desired destination network element is straightly connected to more
than one subnetwork in the ES network element, the ES makes the decision between the
subnetworks randomly. To improve the performance in DX 200 ES network elements,
LAN subnetworks are prioritised before X.25 subnetworks if the ES network element and
the destination network element are connected to several subnetworks.
For example, in the figure above, if there was an extra connection between the DX 200 B
and DX 200 A network elements to the X.25 subnetwork, DX 200 B (ES) would still use
the LAN subnetwork in the first place.
CLNS object states

The parameters of a CLNS are defined in CLNS objects. Each object defines the
properties of one parameter set. The object used in the initialisation of a CLNS is
determined according to the states of the CLNS objects.
The state of a CLNS object is a combination of the administrative state, status, and
operational state, which are listed in the following table.
DN9812567 Issue: 14-1 © 2016 Nokia 19

Table 2 All possible states of CLNS object (administrative state — status —

operational state)
Administrative state Status Operational state
UNL unlocked BU backup ACT active
permitting the use of the object indicating an object proven to be indicating an object currently in
operational use
LOC locked NW new ENA enabled
prohibiting the use of the object indicating a new configuration to be indicating permission to use the
tested object in initialisation
DIS disabled
indicating prohibition to use the

object in initialisation
CLNS objects are handled with the QE command group.

CLNS parameters are presented in Parameters of CLNS.
Benefits of OSI Routing in DX 200 networks

A DX network element can work as an ES or a Level 1 IS. If the planned network is
remarkably big (containing hundreds of network elements) or the subnetworks are
geographically scattered, then forming several areas and linking them with a non-DX
backbone router can be considered.
The figure below illustrates one of the benefits of using OSI Routing. If network elements
are managed by the Administrative Computer (AdC) using the OSI interface, the OSI
connection is usually established between the AdC and one of the network elements (for
example, MSW or OMC). The AdC cannot communicate directly with other network
elements. Management data must be transferred between DX 200 network elements
with some other protocol and stored in DX 200 A before transferring data with OSI to the
AdC.
20 © 2016 Nokia DN9812567 Issue: 14-1

Figure 5 Benefits of OSI Routing
AdC AdC
DX200 A DX200 A DX200C
OSIRouting
DX200B DX200C
DX200B DX200D
Physicalconnection
DX200D MSWconnection
OSIconnection
a)NetworkmanagementwithoutOSIRouting b)NetworkmanagementwithOSIRouting
It is possible to build a separate data network which connects the AdC to all the DX 200
network elements and all the DX 200 network elements to one another. But a better
solution is to utilise the existing connections (for example, X.25 over PCM) between DX
200 network elements.
With the OSI Routing feature in the CLNS, the AdC can communicate directly with all the
DX 200 network elements without any additional physical connections. OSI traffic
between the AdC and, for example, DX 200 D is routed through DX 200 A and DX 200
B. The route is transparent to the AdC and DX 200 D.
System types of DX 200 network elements

As described above, the system type (also known as role) of a DX network element can
be either ES or Level 1 IS. The role is a delivery-dependent parameter, and it can be
determined in advance, in which case the software of the network element supports only
the selected role. By default, the system type is not determined in advance; the software
supports both system types and the network element can be configured to operate in
either role.
CONS with OSI over TCP/IP feature

With RFC1006 implementation OSI services will be available on top of TCP/IP protocols.
This feature is optional and needs license to get feature activated. When feature is
activated ISO Transport Service traffic is directed to the TCP/IP protocol layer.
Adaptation is done inside OMU unit which means that all IP traffic coming from Ethernet
port of OMU will be pure TCP/IP. After that all services of BSC site IP configuration can
be utilized also for OSI traffic. The figure below represents OSI over TCP/IP adaptation
at protocol layer level.
DN9812567 Issue: 14-1 © 2016 Nokia 21

Figure 6 RFC1006 adaptation architecture
Q3
FTAM VT CMISE
ACSE ROSE
Presentationlayer
anewapplication
COTSuser adaptingOSIprimitives
Sessionlayer e.g. TPPIPE for TCP/IP stack
TP class4 Transport layer TP class0 "RFC1006"
CLNS CONS
TCP
ISOIP,ES-IS,IS-IS IP
LLC X.25packetlevel Ethernetinterface

CSMA/CD X.25datalinklevel
physicallevel
IP over
analog
LAN digital X.25 LAN E1/T1
1.4 OSI addressing scheme

OSI Addresses
An OSI address consists of a Network Service Access Point (NSAP) and possible
selector values. The NSAP identifies a computer system and one of its network service
users, which is typically the OSI transport layer.
The NSAP is realised by Network Protocol Address Information (NPAI), that is, the NSAP
address. The NSAP is structured hierarchically, so that geographical location of the
computer system can be determined according to the value of the NSAP address. NSAP
address values are managed by a national authority. One company may assign NSAP
address values within its own NSAP address range.
22 © 2016 Nokia DN9812567 Issue: 14-1

Figure 7 Usage of selectors
P r es e ntati o n l ay er P D U to P res e nta t io n layer

a p p l ica ti o n pe e r protoco l a p p li ca ti o n
d a ta d a ta
P P DU
SD U to l ower lay er P -s e lecto r

Se s s i on la yer S e ss io n lay e r
P SD U PSDU
SPDU
S- s ele cto r
Tra n sp ort l a ye r Tra ns po rt laye r

SS D U S SD U
TP D U
S D U to upper lay er T -s e l ecto r

N e two rk l aye r N e two rk l ayer
TSDU T SD U
N PDU
NS AP
p ro to col d ep en d e nt inf orm a tion
lo we r l a ye rs
Selectors are necessary for routing connection establishment through OSI stack within a
computer system (figure above). One selector is needed for each protocol layer, so there
are selectors for Transport, Session, and Presentation layers (see the table NTC de facto
selector values for OSI applications below in this section). The NSAP together with the T-
, S-, and P-selectors constitute a Presentation Service Access Point (PSAP), also called
the Presentation Address.
Application identification is usually based on the PSAP, but it is possible to use additional
identification information. If several applications are identified with a common
presentation address, the actual selection is based on Application Entity Titles (AET). An
AET consists of an Application Process Title (APT) and an Application Entity Qualifier
(AEQ). The structure of the APT may be a directory name (Form 1) or an object identifier
(Form 2). In DX 200 systems, a local application is always identified with a presentation
address, so only a remote application may require AET values.
Structure of NSAP address

In general, an NSAP address consists of an area address, a system identifier and an N-
selector (figure below). The routing protocol requires that the area address must be
common for all network elements within the routing area. The system identifier must be
unique: it should identify the whole network element within a routing area. From the
routing protocol's point of view, only the header of the NSAP address, excluding the N-
selector, is significant. A common name for this part of the NSAP address is Network
Entity Title (NET).
DN9812567 Issue: 14-1 © 2016 Nokia 23

On the other hand, from the OSI address administration's point of view, the NSAP
address consists of the Authority Format Identifier (AFI), Initial Domain Identifier (IDI),
and Domain Specific Part (DSP). The AFI value defines the format of the NSAP and the
possible IDI values. DSP values are managed locally within the authority specified by
AFI and IDI fields. Usually the DSP field is structured hierarchically in order to make the
distribution of NSAP address management easier.
Figure 8 NSAP address interpretation
ROUTING
NET
Area Address
System I dentifier
N-selector
NSAP
1 4 max 20
AFI IDI DSP
ISO Data Country Code (DCC) NSAP address

ISO DCC NSAP is used in OSI routing protocols. Its common format is as follows:
AFI (1 octet) + IDI (2 octets) + DSP (17 octets)
• AFI (Authority Format Identifier)

– ISO DCC NSAP
• IDI (Initial Domain Identifier)

– Country code
• DSP (Domain Specific Part)

– DSP Format Identifier (1 octet)
– Organisation Identifier (3 octets)
– Reserved (4 octets)
– Area (2 octets)
– End System Identifier (6 octets)
– N-selector (1 octet)
One way to achieve a unique NSAP is to use the MAC address of the Ethernet data
terminal as the End System Identifier. A more preferred method is to use the C-number
of the DX network element because the End System Identifier represents the whole
network element.
24 © 2016 Nokia DN9812567 Issue: 14-1

The N-selector is always interpreted locally and it is not a part of the routing information.
The reserved country codes are presented in ISO 3166-1:1997 Codes for the
representation of names of countries and their subdivisions -- Part 1: Country codes.
Example:ISO Data Country Code (DCC) NSAP address
The following table presents an example of NSAP in a network of NTC in Finland.
Table 3 Example of ISO Data Country Code (DCC) NSAP address
Part of the NSAP address Value
AFI 39
IDI 246 (country code of Finland)
DSO Format Identifiier 00
Organisation Identifier 000116 (organisation identifier of NTC)
Reserved 00000001
Area 0001
End System 000000330970
N-selector FF
The whole NSAP address 3924600000116000000010001000000330970FF
ISO 6253-International Code Designator (ICD) NSAP address

ISO 6253-ICD NSAP is used in OSI routing protocols. Its common format is as follows:
AFI (1 octet) + IDI (2 octets) + DSP (17 octets)
• AFI (Authority Format Identifier)

– ISO ICD NSAP
• IDI (Initial Domain Identifier)

– Organisation code
• DSP (Domain Specific Part)

– DSP Format Identifier (1 octet)
– Administrative Authority (3 octets)
– Reserved (2 octets)
– Routing Domain Identifier (2 octets)
– Area (2 octets)
– End System Identifier (6 octets)
– N-selector (1 octet)
DN9812567 Issue: 14-1 © 2016 Nokia 25

Example:ISO 6253-International Code Designator (ICD) NSAP address

The only difference between ISO DCC and ISO ICD NSAP is the way the four spare
octets are allocated.
The following table presents an example of the NSAP in a network of the NIST (National
Institute of Technology).
Table 4 Example of ISO 6253-International Code Designator (ICD) NSAP address
Part of the NSAP address Value
AFI 47
IDI 0005 (organisation code of NIST)
DSP Format Identifier 00
Administrative Authority 000001
Reserved 0000
Routing Domain Identifier 0002
Area 0003
End System 000000330970
N-selector FF
The whole NSAP address 47000500000001000000020003000000330970FF
Unstructured (unspecific) NSAP address

Unstructured NSAPs do not have a specified structure. An unstructured NSAP address
can be up to 20 bytes long. You can use this format when configuring an NSAP address
that conforms to a structure not presently supported by the DX OSI software.
Other Network layer addresses

X.25 address
Typically, an X.25 address consists of the Data Terminal Equipment (DTE) number and
Subsequent Protocol Identifier (SPI). The most commonly used SPI values are listed in
the table below.
Table 5 Subsequent Protocol Identifiers of network layer
Protocol SPI
Transport layer -
Transport layer 03010100
26 © 2016 Nokia DN9812567 Issue: 14-1

Table 5 Subsequent Protocol Identifiers of network layer (Cont.)
Protocol SPI
PAD 01000000
X.25 SNDCF 81
Locally agreed interpretation Cx
The DTE number is not needed when the X.25 connection uses a Permanent Virtual
Circuit (PVC). In this case, the channel group name identifying the PVC number must be
given.
OSI Application Addresses

After the NSAP addresses are allocated, you need to decide how the different OSI
service elements using a common NSAP address are distinguished from each other.
This is achieved by using unique selector values. The administration of these selector
values requires that you establish an addressing scheme for the whole network.
For example, you can use the types of different OSI applications as an addressing
criteria. You simply attach a unique selector value to each OSI application.
The following table presents the NTC de facto standard to construct selector values for
the DX network element.
Table 6 NTC de facto selector values for OSI applications
Application Appl. nr Unit type Selector
Virtual File Store 1 OMU (2) 0201
Alarm downloader 2 OMU (2) 0202
CMIP agent 3 OMU (2) 0203
Performance manager 4 PFMU (1B) 1B04
Alarm mailbox 5 OMU (2) 0205
ISO Virtual Terminal 6 OMU (2) 0206
IP based NSAP address RFC1006

When OSI over TCP/IP feature is active, NSAP addresses are given as IP address
format. Local address is OMU units IP address and remote address is remote ends IP
address. Local port is set by default and value is 102 which is iso-tsap port value.
Remote port can be given when remote NSAP address is created.
DN9812567 Issue: 14-1 © 2016 Nokia 27

1.5 Data terminals of the PCI bus based DX 200
In a PCI bus based DX 200 network element there is an Ethernet interface in every
computer unit, that is, there is no need for the COCEN plug-in unit. The Ethernet
interface provides a connection to Local Area Networks (LANs), using LLC1 data link
transfer protocol. The interface type can be either 10Base-T or 100Base-TX. The
hardware detects automatically the connection type.
A connection to an X.25 packet network is made by using an AS7-C or AS7-D plug-in
unit. It provides two different interface types: V.24 and V.28. Both plug-in units support
the DTE and DCE device types, so it is possible to connect other DTE devices directly to
a DX 200 network element.
The use of the X.25 plug-in units AS7-Cand AS7-D is realised with the help of Physical
Channels. A physical channel, or channel for short, is an abstract concept, which
transforms an X.25 plug-in unit into an X.25 data terminal, hiding the replication when the
plug-in unit is located in a duplicated unit. Together with the information associated with
the plug-in unit, the channel defines the features of the X.25 interface.
The information associated with the X.25 plug-in unit defines hardware-specific matters
such as unit data, possible interface types, and so on. The channel defines the dynamic
attributes of the X.25 terminal equipment, such as the communication method, speed,
and the DTE terminal number of the terminal equipment.
1.6 Usage of data terminals in OSI connections
Remote systems are usually reachable through several alternative routes in order to
avoid communication failures. These alternative routes require that the data terminals
are replicated. The method of replication depends on the subnetwork structure and
interface types available at remote systems.
A path to the remote end is realised by an NSAP address mapped to a route either
dynamically or manually. By the time you attach an NSAP address to a remote system,
you have already established whether the routing is based on CLNS data routing or not.
If the routing is not based on CLNS data routing, you need to plan how data terminals
are used in outgoing call routing before you can attach the NSAP address to the remote
system.
An OSI application may be reachable through several Network Service Access Points,
which means that it has multiple NSAP addresses. It can have, for example, one NSAP
address for the CONS (X.25) interface and one NSAP address for the CLNS interface.
OSI applications are not directly attached to an NSAP address, but instead to a network
address, which can contain up to ten NSAP addresses (figure below).
28 © 2016 Nokia DN9812567 Issue: 14-1

Figure 9 OSI applications, network address, and NSAP addresses
Each NSAP address for the CONS (X.25) interface belonging to a certain network
address has a priority which is significant only within this network address. Using
priorities, it is possible to start carrying out the routing possibilities with the most
favourable alternative.
When the selected NSAP address is used in the CLNS interface, the routing of the CLNS
data is done by IS-IS and ES-IS protocols. These protocols attach cost information
dynamically to each data terminal (linkage) providing a route to a remote system
identified by the NSAP address. This makes it possible to select automatically the most
favourable linkage.
When an NSAP address is used in the CONS (X.25) interface, there is no routing
protocol for selecting the data terminal automatically. So there is a need to include extra
routing information in the remote X.25 NSAP addresses. The next section describes how
this information is included in an X.25 NSAP address.
When OSI over TCP/IP feature is used, NSAP address is given as IP address format .
On that case IP protocol layer handles the routing functionality automatically so physical
channels or linkages are not needed.
1.7 X.25 subnetwork (CONS)
Just like a network address combines alternative NSAP addresses, a channel group
combines the alternative X.25 data terminals. A channel group is a virtual data transfer
network, which provides the user with the possibility to structure existing data transfer
networks.
A channel group has a four-fold role as a virtual data transfer network.
DN9812567 Issue: 14-1 © 2016 Nokia 29

Firstly, a channel group combines a defined set of physical channels into a group of
gates through which the virtual data transfer networks are accessible. If the subnetwork
interface corresponding to a channel in the channel group has a malfunction, an
alternative channel is chosen from the list of channels belonging to the channel group
(see the figure below).
Figure 10 Using an alternative physical channel when the physical connection is lost
Secondly, a remote X.25 address is always associated with a channel group, which
makes it possible to assign a defined set of channels for a specific purpose (see figure
below). By using this abstraction, the user can assign, for example, FTAM sessions to
specific terminal equipment units and PAD sessions to others. This means that the
response times of PAD sessions with real-time requirements do not grow excessively
long because of queuing between long FTAM sessions.
30 © 2016 Nokia DN9812567 Issue: 14-1

Figure 11 Assigning a specific set of physical channels for applications
Thirdly, by using channel groups, the user can combine different physical networks into
one virtual network. For example, it is possible to define a channel group where the
remote application is accessible both by means of a semipermanent connection and a
public X.25 packet network (see the figure below).
Figure 12 Prioritisation of existing subnetworks
DN9812567 Issue: 14-1 © 2016 Nokia 31

To enable a choice between channels to be used, a channel-specific priority is assigned

to the channels of a channel group. When establishing a connection, the channel with
the highest priority is used. If there are several channels with the highest priority, the
choice is made on the basis of the load sharing principle. By using this abstraction, the
user can select the most favourable transfer path to serve as the primary transfer
connection and has recourse to the spare system only when there is a breakdown in the
primary system.
Fourthly, a channel group provides a method for binding the local OSI applications to an
X.25 Permanent Virtual Circuit (see the figure below). In addition to the priority
parameter, there is another parameter associated with the X.25, which, if necessary,
indicates the permanent virtual circuit number used in the channel. The default value of
this parameter is zero, which means that data transfer is started by establishing an X.25
connection. If the parameter has a value other than zero, the network connection uses
the permanent virtual circuit identified with the virtual circuit number.
Figure 13 Binding the local application to an X.25 permanent virtual circuit
To enable handshaking before the data transfer phase, the permanent virtual circuit user
has to be located. By creating a channel group, which contains a permanent virtual
circuit, and mapping it to a local NSAP (belonging to a given network address), the DX
200 OSI software is able to find the application using the given permanent virtual circuit.
1.8 Alternative remote NSAP address
When configuring OSI connections, it is possible to define an alternative remote NSAP

address in case the primary NSAP address is unreachable. This means that when a
local application tries to establish a connection to the remote NSAP address and fails to
32 © 2016 Nokia DN9812567 Issue: 14-1

do it, the remote NSAP address becomes unreachable and it is not contacted for two
minutes. So if the same or another application is trying to contact the unreachable
remote NSAP address, the alternative NSAP address is contacted instead.
The alternative NSAP address is defined by attaching two (or more) NSAP addresses to
one network address and by giving them different priorities.
For example, in the figure below, an OSI application in DX 200 is trying to reach the node
Y (to the NSAP address yyyyy) but fails to do it because of connection failure outside the
DX. When the application tries again (within two minutes) to reach the same NSAP
address, the DX immediately makes connection to the node X (to the NSAP address
xxxxx).
Figure 14 Example of choosing an alternative remote NSAP address
DX200
X.25network
NODEX NODE Y
NSAP =xxxxx NSAP =yyyyy
PRIOR=40 PRIOR=60
1.9 OSI measurements
The OSI statistics feature offers a tool for investigating the load of different X.25 physical
channels and the stability of the whole operation and maintenance network. Through this
service, the user gets information on the traffic, performance, and various error situations
in the operation and maintenance network.
If OSI over TCP/IP feature is in use, only transport layer’s measurement can be done.
That because there is no any other layers in use where measurement could be done.
When creating the measurement, the user can define the object to be measured, the
required measurement schedule, and the report interval.
The OSI measurements can be created, started, and stopped with the commands of the
OO command group. Measurement reports can be directed via logical files to the OMC
or a printer.
The OSI stack layers which can be included in the measurements and the logical files
are listed in the following table. By default, the logical files are connected to the line
printer (LPT-1).
DN9812567 Issue: 14-1 © 2016 Nokia 33

Table 7 OSI stack layers and their logical files
Layer Logical file
physical layer OSIMEAS1
data link layer OSIMEAS2
network layer OSIMEAS3
transport layer OSIMEAS4
Physical layer measurement report

An example of a physical layer measurement report is presented below.
DX 200 JANKAHLR 1999-02-17 11:15:00
TRAFFIC MEASUREMENT REPORT OSI STATISTICS ITMEAS
SAMPLE DATE: FROM 1999-02-17 11:00:00
TO 1999-02-17 11:15:00
OSI LEVEL: PHYSICAL LAYER
CHAN SHORTS CRCS ABORTEDS LONGS DOWNS
20 0 0 0 0 0
21 0 0 0 0 1
END OF REPORT
The physical level counters are increased when errors are detected on the physical
layer.
• If the received frame is too short, the SHORTS counter is increased.

• If the contents of the received frame have been corrupted during the transfer, the
Cyclic Redundancy Check (CRCS) counter is increased.
• If the sending of a frame is aborted for some reason, the ABORTEDS counter is
increased.
• The LONGS counter counts the number of frames that are too long (that is, which
have no ending flag).
• The DOWNS counter counts the number of the losses of a carrier.
If the physical media is working properly, the physical level counters should be zero (0)
or close to zero.
Data link layer measurement report

An example of a data link layer measurement report is presented below.
DX 200 JANKAHLR 1999-02-17 11:15:07
SAMPLE DATE: FROM 1999-02-17 11:00:00
TO 1999-02-17 11:15:00
OSI LEVEL: LINK LAYER
34 © 2016 Nokia DN9812567 Issue: 14-1

TRANSMITTED FRAMES TYPE:

CHAN INFO REJ RNR FRMR1 FRMR2 FRMR3 FRMR4
20 3256 0 0 0 0 0 0
21 12343 1 0 0 0 0 0
RECEIVED FRAMES TYPE:

20 3046 0 0 0 0 0 0
21 1343 0 0 0 0 0 0
CHAN RET.INFOS RESETS T1.EXP
20 0 0 0
21 0 0 2
END OF REPORT
The link level counters count the number of different frames sent and received by the link
level. The INFO counter is increased when information frames are sent and received.
The REJ counter indicates that frames have been lost and they are retransmitted. The
RNR counter counts the number of Receiver Not Ready frames, which are sent when the
receiver is temporarily unable to receive information frames. The FRMR (Frame Reject)
counter is sent when there is an error condition that cannot be recovered by
retransmitting the frames. The RESETS counter counts the number of link level resets.
The T1.EXP is increased if the peer entity does not respond within the time limit.
All the other counters, except the INFO counters, indicate error situations.
Network layer measurement report

An example of a network layer measurement report is presented below.
SAMPLE DATE: FROM 1999-02-17 11:00:00
TO 1999-02-17 11:15:00
OSI LEVEL: NETWORK LAYER
TRANSMITTED PACKETS TYPE: SEGMENTS

CHAN DATA RESET CLEAR RESTART RNR TRANS. RECEIVED
20 4000 0 0 0 0 1756 1800

21 14000 0 0 0 0 5785 678
RECEIVED PACKETS TYPE:
CHAN DATA RESET0 RESET1 CLEAR0 CLEAR1 RESTART RNR
20 4000 0 0 0 0 1756 1800

21 1500 0 0 0 0 0 0
CALLS:
CHAN SUCC.IN SUCC.OUT UNSUCC.IN UNSUCC.OUT REJ.OUT IN DUR.A IN DUR.B
20 0 0 0 0 0 0 0
21 4 1 0 0 0 0 0
CALLS: TIMEOUTS: PACKETS
DN9812567 Issue: 14-1 © 2016 Nokia 35

CHAN IN DUR.C IN DUR.D T20 T21 T22 T23 DISCARDED
20 1 0 0 0 0 0
21 0 0 0 0 0 0
END OF REPORT
The packet level counters count the number of packets sent and received by the X.25
packet level.
• The DATA counter counts the number of transferred data packets.

• The RESET counter is increased when a logical channel is reset, that is, when all the
untransmitted packets are deleted, and the send and receive variables are initialised.
The RESET0 counter counts the received reset packets whose cause field has the
value zero (0).
The RESET1 counter is increased if the cause field value of the received reset
packet is higher than zero (>0).
If the cause field is zero (0) or higher than 127, the originator of the reset is a remote
DTE.
If the cause field is higher than zero (>0), but lower than 128, the originator of the
reset is the DCE (in other words, the packet switching network). It is very unlikely that
any DTE would use a cause field whose value is larger than zero (>0).
• The CLEAR counter counts the number of connection clearings.
The CLEAR0 counter counts the received clear packets whose cause field is zero
(0).
The CLEAR1 counter is increased if the cause field of the received clear packet is
higher than zero (>0).
If the cause field is zero or higher than 127, the originator of the clearing is a remote
DTE.
If the cause field is higher than zero (>0), but lower than 128, the originator of the
clearing is the DCE (in other words, the packet switching network). It is very unlikely
that any DTE would use a cause field whose value is higher than zero (>0).
• The RESTART counter is increased when the whole packet level is initialised.
• The RNR counts the times a single logical channel has been unable to receive any
more data packets. Usually, this means that the user of the X.25 connection is not
consuming data at the rate it is received from the X.25 connection.
• The SUCC.IN and the SUCC.OUT counters count the number of successful
incoming and outgoing calls. The UNSUC.IN and the UNSUC.OUT counters count
the number of unsuccessful incoming and outgoing calls.
• The duration of calls is indicated in the DUR.A, DUR.B, DUR.C, and DUR.D
counters.
– DUR.A counts the calls whose duration is less than 10 seconds.
– DUR.B counts the calls whose duration is between 10 and 300 seconds.
– DUR.C counts the calls whose duration is between 300 and 3600 seconds.
– DUR.D counts the calls whose duration is more than 3600 seconds.
• The counter T20 is increased when there is no answer to a RESTART REQUEST.

The T21 is increased if there is no answer to a CALL REQUEST. The T22 counts the
number of unanswered RESET REQUESTS. The T23 is increased if there is no
answer to a CLEAR REQUEST.
Transport layer measurement report
36 © 2016 Nokia DN9812567 Issue: 14-1

An example of a transport layer measurement report is presented below.

DX 200 JANKAHLR 1999-02-17 11:15:10
SAMPLE DATE: FROM 1999-02-17 11:00:00
TO 1999-02-17 11:15:00
OSI LEVEL: TRANSPORT LAYER
CHAN L.ERR.DIS L.NOR.DIS L.SUC.CON L.UNS.CON R.ERR.DIS R.NOR.DIS
20 0 1 1 0 0 0
21 0 0 0 0 0 3
TPDUS:
CHAN R.SUC.CON R.UNS.CON SENT RECEIVED RETRANSM. INV.REC.
20 0 0 3332 3767 0 0
21 4 1 23332 2767 0 0
OCTETS:
CHAN CHKSUM.DIS RECEIVED SENT RETRANSM.
20 0 42674 43373 0
21 0 42624 123343 0
END OF REPORT
The transport level counters count the number of Transport Protocol Data Units
(TPDUs). The counters also count connections and disconnections.
The counters which handle connection establishments show successful and
unsuccessful connection establishments separately. Similarly, disconnection counters
show normal and error disconnections separately. An L (=local) or an R (=remote) in the
beginning of a counter name defines whether the connections or disconnections are
initiated by a local or a remote system.
Other counters count the number of the sent and received TPDUs.
1.10 Usage of OSI file service commands
In DX 200 there are special MML commands for handling and managing the files in a
virtual file store. Usually, these commands are used when testing OSI connections and
when you want to manually list, copy, delete, or create files in the virtual file store.
With these commands you can list the files in a local or remote virtual file store, copy
files between local and remote virtual file stores, and delete files from local or remote
virtual file stores. You can also create files in a virtual file store and change the attributes
of the files in a virtual file store so that other FTAM applications can access the files.
To use these commands locally you must have the FTAM application configured in the
local node. And to use these commands, for example, to copy files between two nodes,
the FTAM application must exist in both nodes.
The OSI File Service commands are presented below.
DN9812567 Issue: 14-1 © 2016 Nokia 37

QFA – COPY FILE

The command copies a file from a local device to a remote one or the other way round.
For instance, in the example presented in section Example configuration of an IS with
LAN and X.25 interfaces, to copy a file from IS1 to ES1 you give the command
ZQFA:LFTAM,”FILE.TXT”,ES1FTAM,”ES1FILE.TXT”,””:;
where LFTAM is the virtual file store of the own node (IS1), FILE.TXT is the name of the
file to be copied, ES1FTAM is the virtual file store of the remote node (ES1) where the
file is copied, and ES1FILE.TXT is the name of the copied file in the remote node.
PASSWORD is the password needed to access the file in the remote node. Usually, the
password is not needed, but it is enough to give only quotation marks (“”) in the
command.
g Note: The MML command with given parameters is saved to the MML command log,
and the given password can be read by users who have full access rights to the
command log.
QFC – CREATE FILE

The command creates a new file in a local device.
For example, the following command creates a file in the local virtual file store:
ZQFC:LFTAM,”DIR/FILE.TXT”,TEXT,2:;
where LFTAM is the virtual file store, DIR is the directory where the new file is located,
and FILE.TXT is the name of the new file. TEXT indicates that the file is a text file and
the size of the file is 2 blocks (=1024 bytes).
By default, all file operations are allowed. If you need to restrict particular file operations,
check the parameters one by one.
QFD – DELETE FILE

The command deletes a file in a local or a remote device.
QFL – LIST FILE DIRECTORY

The command lists a directory of the local virtual filestore system.
QFM – DISPLAY/MODIFY FILE ATTRIBUTES

The command examines and modifies the file attributes in a local device.
Look at the example in section Example of configuration of an ES with LAN and X.25
interfaces. If there is a file in node ES1 that is supposed to be read by the administrative
computer AdC, the attributes of the file has to be changed so that AdC is able to read the
file.
You change the attributes of the file so that AdC is allowed to read the file with the
following command:
ZQFM:LFTAM,”FILE.TXT”:REA=YES,RAT=YES;
where LFTAM is the virtual file store of the own node (IS1) and FILE.TXT is the name of
the file to be read. REA is for permitting reading and RAT is for permitting reading the file
attributes.
38 © 2016 Nokia DN9812567 Issue: 14-1

If the application in AdC needs to delete or replace the file in node ES1, the needed
attributes are set by the following command:
ZQFM:LFTAM,”FILE.TXT”:REA=YES,RAT=YES,REP=YES,DEL=YES;
where LFTAM is the virtual file store of the own node (IS1) and FILE.TXT is the name of
the file to be read. The REA is for permitting reading and RAT is for permitting reading
the file attributes. REP is for permitting the replacement of the file and DEL is for
permitting the deleting of the file.
For further details about the parameters of the commands mentioned above, refer to the
information on OSI file services.
1.11 O23MTS service terminal extension
There is a set of software tools by which the OSI stack can be monitored and the
configuration examined. These tools are available in the O23MTS service terminal
extension.
MML commands are used to define the OSI configuration (applications, OSI addresses,
channels, and so on), whereas the tools in O23MTS can be used when you need
detailed information of the status of OSI processes. With the tools of O23MTS, it is
usually not possible to change any data.
Load the O23MTS extension with the following service terminal commands:
ZLE:1,O23MTSGX;
Z1;
and you will receive the main menu presented below.
OSI LAYERS 1–5 MONITOR AND TEST SYSTEM
? ..... menu / help
C ..... CVOPS nucleus monitor
X ..... layers 1-4 state and statistics
N ..... X.213 interface
O ..... OSI-file viewer
A ..... X.25 monitor
B ..... transport monitor
R ..... X.25 active addresses
F ..... monitor X.25 ack delays
L ..... CLNS finder
M ..... test MAC interface
Z ..... return to main level
The following tools are available in the main menu of O23MTS:
• C starts a tool for examining the internal data structures and status variables of the
processes made with the CVOPS tool. Usually, this tool is used for troubleshooting
by Nokia Customer Service.
• X starts a tool for monitoring the states of protocol automatons of OSI layers 1 to 4
(physical level, link level, packet level, and transport layer). In the X menu there are
commands for displaying the statistical data and status information of layers 1 to 4.
This tool is handled in sections Monitoring statistics of OSI layers 1 - 4 and
Monitoring status information of X.25.
DN9812567 Issue: 14-1 © 2016 Nokia 39

• N starts a tool for displaying information on the cause and originator of the resetting
or disconnection of an X.25 connection.
– Use the E command of the X.213 menu, giving the cause or diagnostics code of
the received message as the parameter.
• O starts a tool for displaying the contents of the OSI management files in a more
readable form than just dumping the contents in hex. In section Displaying the
contents of OSI management files, there is a more detailed description of this tool.
• A starts the X.25 monitor for displaying X.25 frames sent and received by the DX. In
section Monitoring X.25 traffic, there is a more detailed description of this tool.
• B starts a transport monitor for displaying the network service data units sent and
received by the DX. In section Capturing transport protocol data, there is a more
detailed description of this tool.
• R starts a tool for displaying the network addresses of the users currently logged in
through the X.25 interface.
• F starts a tool for monitoring the acknowledgement delays of the link level and the
packet level. In section Monitoring X.25 acknowledgement delays, there is a more
• L starts a tool for displaying the adjacency and destination information of the
connectionless network service. In section Inquiring IS-IS routing information, there
is a more detailed description of this tool.
• M starts a tool for testing the Ethernet interface. In section Testing MAC ethernet
interface, there is a more detailed description of this tool.
You can get a short description of the syntax and semantics of each command by typing
'?' and the command letter.
1.12 FTAM user account management
FTAM transfer can be performed using local user account or remote user account.
Local users are defined locally in one network element and managed with MML
commands. A local user can only log in to the network element where the local account
is defined.
Remote users are defined centrally in a directory server. With a remote user account a
user can log in to any network element that uses directory server as authentication
centre. A remote user has an access list of the network elements and can log in to those
network elements only which are on the access list.
Access rights
Local user accounts use locally defined user profiles. If local user account is used, the
target network element must contain the local user account with FTAM access right FO-
X (execution rights to open FTAM) or FS-X (execution rights to secured FTAM) in the
FTAM user profile.
Remote user accounts are managed outside the network element with the user interface
of NetAct. It is not possible to create new remote users from DX 200. These user
accounts use remotely defined user profiles, which contain session access rights
information. If a remote user does not have any profile, the user is not marked as a user
of the network elements.
40 © 2016 Nokia DN9812567 Issue: 14-1

A network element based on DX 200 technology uses directory server through LDAP
interface. With the LDAP directory it is possible to authenticate the user and enquire user
profile information. If a remote user account is used, the centralised database (LDAP
directory) must contain the remote user account with profile access right to the target
network element and FTAM profile FS-X. Open FTAM rights (FO-X) are not supported for
remote user accounts. If FO-X access rights are needed, a local FTAM user must be
created. When the local FTAM user with FO-X access right transfers a file, only the local
username and profile is specified, a password must not be given.
For more information on handling user accounts, see Information Security.
1.13 OSI security

X.25 access control
When you attach a DX network element to a public X.25 network, you should carefully
design how unwanted X.25 connection attempts are rejected and/or registered. There
are two possible methods to do this: you can either subscribe a Closed User Group
service from the network operator, or you can start using an X.25 access list provided by
the DX OSI software. With this application you can define those remote X.25 sites that
are allowed to establish X.25 connections to the local DX network element.
The X.25 access list information is managed with the QQ command group. There are
three different security policies, of which you can choose with the QQM command:
ZQQM:;
/* IDENTIFY ACCESS CONTROL METHOD
A ... ALL INCOMING CALLS ALLOWED
D ... ALL INCOMING CALLS DENIED
L ... USE ACCESS CONTROL LIST */
ZQQM:D;
DX 200 DX200-LAB 1995-01-01 00:10:25
MODIFYING OSI ACCESS CONTROL METHOD
OLD METHOD NEW METHOD
-------------------------- --------------------------
ALL INCOMING CALLS ALLOWED ALL INCOMING CALLS DENIED
COMMAND EXECUTED
By default, all incoming calls are allowed, but the access control policy can be changed
so that all incoming calls are denied or a user-defined access control list is taken into
use. All unsuccessful connection attempts are registered.
When comparison is made between the calling address and the addresses on the
access control list, only as many digits are taken from the calling address as there are
digits in the address of the access control list. So it is also possible to give access, with
one command, to several nodes, the address of which have the same starting digits. It is
possible for the user to define only the start of the addresses from where the connections
are allowed. This feature also allows the use of X.25 subaddresses, for example, the
network address of the calling party is 123, but the call comes from subaddress 12399,
which is within the node 123.
OSI application layer security
DN9812567 Issue: 14-1 © 2016 Nokia 41

One way to have security options within the upper layers of the OSI stack is naturally the
OSI address. This means that the initiator of an incoming call must know the appropriate
OSI address (NSAP, selectors) in order to make a successful call.
Moreover, it is possible to set file-specific attributes or define user profiles to prevent
unauthorised users to use files in the hard disks of the DX 200 network element via the
FTAM file handling services. See the following topics.
• FTAM security with file-specific attributes

Files in a local virtual file store can be protected against unauthorised use with file-
specific FTAM attributes, namely:
– owner of the file
– list of permitted operations (read, write, delete, and so on)
– passwords for permitted operations (one password for read, another for write,
and so on)
In order to carry out an operation on a protected file, the initiator of the incoming
FTAM connection must know the owner identity and the file-specific password for the
operation.
By default, files in the file system of DX 200 do not have FTAM attributes. However,
with the QFM command the user can define values for FTAM attributes of a file. Also,
when an application running in the DX creates a file, it can define values for the
FTAM attributes.
There is an example output of the QFM command in the section Application errors.
• FTAM security with user profiles
With the FTAM security function it is possible to prevent unauthorised users from
using the hard disks of the DX 200 network element via the FTAM file handling
services.
The remote FTAM users must have a valid network user ID and a password before
FTAM operations are permitted.
Virtual terminal security and Nokia VT profile

Incoming VT and PAD calls are directed either to an MMI session or to a remote printer.
The MMI checks the identity of the caller by requesting the username and password. In
the case of remote printer (VPP device), the user identity is not checked. However, a
VPP connection creates only an output which can be directed with MML commands into
a VPP. No data can be sent into DX 200 through a VPP connection.
The ISO VT standard default profile allows only printable characters in the data flow. The
MML command line editor is usable only if non-printable characters can be passed
through a VT connection. It is possible if a Nokia proprietary VT profile is used instead of
the default profile. If a Nokia profile is used when the ISO VT connection is established,
DX 200 treats the connection as a transparent tube and does not filter non-printable
characters from the data flow to the VT client. Such filtering is done when using the
standard default profile.
The VT-client can establish a Nokia profile connection by using the value
{1,0,9040,1,255} in the profile name parameter in the vt-associate-request protocol data
unit (see the output of the Sniffer protocol analyser below).
VTP: ----- ISO VTP Virtual Terminal Protocol -----
VTP:
VTP: VTPDU type = Associate request (length = indefinite)
VTP: Class = 1 (Basic)
42 © 2016 Nokia DN9812567 Issue: 14-1

VTP: Functional units = 0000

VTP: 0... .... .... .... = No profile switch
VTP: .0.. .... .... .... = No multiple interaction negotiation
VTP: ..0. .... .... .... = No negotiated release
VTP: ...0 .... .... .... = No urgent data
VTP: .... 0... .... .... = No destructive break
VTP: .... .0.. .... .... = No enhanced access
VTP: .... ..0. .... .... = No structured COs
VTP: .... ...0 .... .... = No blocks
VTP: .... .... 0... .... = No fields
VTP: .... .... .0.. .... = No reference InfOs
VTP: Profile name = {1.0.9040.1.255} (ISO standard.9040.1.255)
Now, when the Nokia profile is used, the DX 200 is able to send non-printable characters
(such as Backspace, Bel, and so on) and VT100 terminal control sequences to the VT-
client and thus the connection requires a VT-client that handles VT100 emulation (for
instance, xterm).
During an MML session the MML command line editor and service terminal command
line editor are usable if control characters are passed as data to DX 200.
However, the following things need to be noted and considered when using editors
through the ISO VT:
• The length of the command line

By default, the length of the command line is undefined during an ISO VT
connection, that is, DX 200 does not fold lines. In other words, from the VTERMD's
point of view even the command of maximum length (223 characters) is in one line.
If the command length exceeds the length of the window and xterm for instance folds
the command line, the cursor movements sent by DX 200 may be incorrect.
The best way to keep screen updates in order is to maintain a suitable size window
so that the command can be fitted to the line. An alternative possibility is to define
the line length of DX 200. However, the change has to be made in the VT1FIL file.
• The command line and protocol dependent controls
Basically the same controls function during an ISO VT connection as in a VDU and
during a PAD connection. However, there are a few exceptions:
– The flow controls CNTRL-S and CNTRL-Q do not function during an ISO VT
connection, though the controls are listed in the MML editor's help (it can be seen
with CNTRL-W).
– CNTRL-D is handled in VT-client and it kills the whole process. CNTRL-D is not
transmitted to the DX 200 and so it does not function as 'cursor left'. The same
function can be given with the left arrow key.
– CNTRL-T is an escape character of the ISO VT connection and it is not
transmitted to DX 200. CNTRL-T is one of the two controls of the hard copy
function, which is one kind of display log implemented in DX 200.
– CNTRL-O is another kind of display log and it can be used if someone is using a
hard copy.
– Furthermore, CNTRL-X is 'stronger' when ISO VT is used because it is handled
in every case. When VTP is used through PAD or VDU, CNTRL-X functions only
in the case of reading tasks, hence it does not stop the output. The reason for
this behaviour is prior implementation and it remains as such for the time being.
DN9812567 Issue: 14-1 © 2016 Nokia 43

1.14 Sources of information on OSI errors and alarms

Error messages sent by MML commands
Several MML commands return a descriptive error message. For more information about
the specific error you encountered, see section CLNS configuration problems. If no
description is found, use the corresponding instructions on the commands or on the
general error messages to retrieve the error description.
Printouts of the alarm printer

The alarm printer shows the alarm history. With the help of the alarm history, you can
trace the events and states of the components when the error occurred. The tables in
section Notices, disturbances, and alarms initiated by the DX 200 OSI software provide
more information on the notices, disturbances, and alarms initiated by the DX 200 OSI
software. Refer to the alarm instructions for further details on the alarm descriptions.
Computer unit log entries

Each computer unit contains a log file where the program blocks write log entries when
an error takes place. You can use these log entries in conjunction with alarm history
information to get a more detailed picture of the error situation.
DMX RTE error counters and log files

The last error information source is the set of the error counters and log files maintained
by the DMX RTE operating system. See the corresponding operating manual for further
information.
1.15 Logic of the conversion program
The conversion program first checks if it is able to give an application type classification
to all OSI applications. The application type is a new concept and it is not present in the
old version of OSI configuration data. The program retrieves the application type of a
local OSI application from its address information (SS user type field). The type of a
remote OSI application is derived from the selector values of its PSAP address. If the
selector values do not confirm to NTC de facto values, then the program is not able to
figure out the remote application type. When this happens, it outputs the AE name of the
application and asks for the correct application type value from the user. The default
value for the unknown application type is FTAM.
In the second phase, the program creates the CLNS data. The program goes through all
physical channels and finds out if there are any Ethernet terminals in use and creates a
broadcast linkage for each of them. After this, the program creates the CLNS data. The
data of the CLNS depends on the contents of the physical channels and local OSI
addresses using Ethernet terminals:
• If there is no Ethernet interface, the CLNS is created with the default parameters
because the content of the CLNS data does not matter.
• If an Ethernet interface was found, the program examines the local OSI addresses:
44 © 2016 Nokia DN9812567 Issue: 14-1

– If there are no local OSI addresses using an Ethernet interface, the CLNS is
created with the default parameters if an Ethernet interface exists, but no OSI
application is using it.
– If there are local OSI addresses using an Ethernet interface and their AFI, IDI,
and DSP fields are identical (the last octet, that is, the N-selector, may vary), the
manual area address and system id fields (together they form the NET) is built
from these values. So a full conversion is possible and there is no need to update
the OSI address database of other hosts.
– If there are local OSI addresses using an Ethernet interface but their AFI, IDI, or
DSP fields are not identical, then the program builds the values of the manual
area address and the system id fields from the first local OSI address using an
Ethernet interface. Even if a full conversion is not possible, the OSI associations
using an Ethernet interface may succeed. After the conversion the user must
update the OSI address databases of the other hosts.
The last phase consists of an OSI application and an address data conversion. The
conversion program examines the OSI applications one by one and creates the NSAP
addresses and Network addresses only when it is necessary. By default, the applications
share the existing NSAP and Network addresses.
About the conversion

The conversion program is executed after a packet change, but there are some actions
that should be done before activating the new packet.
If the conversion program detects an error during the conversion, it writes the event type
to its own log. After this it tries to continue conversion normally. To solve the problems
that occur, the log file can be printed out.
If errors occur during the conversion, it is possible to return back to the previous software
packet, correct the configuration problems there, and execute the conversion again.
For more information about how the conversion is done, refer to section Converting the
OSI configuration information.
DN9812567 Issue: 14-1 © 2016 Nokia 45

Example configuration of an ES with LAN interface OSI Guide
2 Example configuration of an ES with LAN

interface
A summary of the configuration steps is presented in Section ES with LAN - summary of
configuration steps. In the summary, the example commands are for thePCI bus-based
DX 200 network element. For more information, see Section Defining local DX 200 OSI
environment.
2.1 Structure of example network in ES with LAN

interface
In this example, a DX 200 network element with the LAN interface is configured with the
ES operating role. The ES and the OMC are connected to each other using the OSI
routing network, and OSI services are needed for data transfer between them. The
example structure is presented in Figure Network structure of an example network in ES
with LAN.
The network structure and the required services are determined first. The information is
presented using configuration sheets. When configuring your own environment, you can
use the empty configuration sheets enclosed in Section OSI configuration sheets.
Figure 15 Network structure of an example network in ES with LAN
2.2 Configuration information of ES with LAN

Required OSI services in ES1
The ES1 network element is handled as a local network element. The required services
are the following:
• FTAM for file transfer from the OMC (CLNS)

• CMISE for transmitting events to and actions from the OMC (CLNS)
46 © 2016 Nokia DN9812567 Issue: 14-1

OSI Guide Example configuration of an ES with LAN interface
• VT for virtual terminal sessions initiated by the OMC (CLNS)
Hardware configuration of ES1

The hardware configuration of the DX 200 network element ES1 is as follows:
• Central Memory (CM)

• OMU
– Ethernet interface: index 0
Address and parameter information of ES1

Ethernet (CLNS):
Parameter Value
operating mode: ES
C-number: 12345
system identifier (where the last five digits 000000012345

are from the C-number of your network
element):
manual area address: 39246F00000116000000000001
MaximumDPULifetime value: 9 hops
MaximumAreaAddresses value: 3
unit of active NS user (O54LRS): OMU
The selectors of the local applications are the following:
FTAM tsel 0x0201, ssel 0x0201, psel 0x0201
CMISE tsel 0x0203, ssel 0x0203, psel 0x0203
VT tsel 0x0206, ssel 0x0206, psel 0x0206
Address information of OMC

NSAP 39246F0000011600000000000000000019283FF
2.3 Configuration sheets for ES with LAN

Sheets for the local network element
DN9812567 Issue: 14-1 © 2016 Nokia 47

The following tables illustrate the use of configuration sheets in this example
configuration.
Table 8 CLNS configuration sheet

1 CLNS name ES_1
2 CLNS role ES
3 NS user primary unit OMU
4 MaximumPDULifetime 9
5 System identification 000000012345
6 MaximumAreaAddresses 3
7 Manual area addresses 39246F00000116000000000001
Table 9 Broadcast linkage configuration sheet for ES1

1 Identification of linkage 1
2 Role of linkage ES
3 Computer unit type and index OMU
4 Plug-in unit index/PCI device 1

identification
5 IS priority default
Table 10 N-selector NSAP configuration sheet

1 Identification of NSAP 1
2 NSEL FF
Table 11 Local network address configuration sheet for transport layer

1 Network address name LOCALTRA
2 NSAP 1
Table 12 Local application configuration sheet for FTAM

1 Application entity name LFTAM
2 Application process title type -
48 © 2016 Nokia DN9812567 Issue: 14-1

Table 12 Local application configuration sheet for FTAM (Cont.)

3 Application entity qualifier -
4 Application type VFS
5 Computer unit and index OMU
6 Family -
7 Process or device index -
8 Network address LOCALTRA
9 P-selector 0x0201
10 S-selector 0x0201
11 T-selector 0x0201
Table 13 Local application configuration sheet for CMISE

1 Application entity name LCMISE
4 Application type CMI
6 Family -
9 P-selector 0x0203
Table 14 Local application configuration sheet for VT

1 Application entity name LVT
4 Application type VTP
DN9812567 Issue: 14-1 © 2016 Nokia 49

Table 14 Local application configuration sheet for VT (Cont.)

6 Family -
9 P-selector 0x0206
Sheets for a remote network element

Table 15 CLNS NSAP configuration sheet for OMC
2 IDP initial domain part 39
3 IDI initial domain identifier 246
4 DSP format identifier 00
5 DSP organisation identifier 000116
6 DSP reserved field 00000000
7 DSP area 0001
8 End system identifier 000000019283
9 N-selector FF
Table 16 Remote network address configuration sheet for ES1

1 Network address name OMCTRA
2 NSAP 10
3 Priority default
Table 17 Remote application configuration sheet for OMC CMISE

1 Application name OMCCMISE
50 © 2016 Nokia DN9812567 Issue: 14-1

Table 17 Remote application configuration sheet for OMC CMISE (Cont.)

4 Application type OMI
8 Network address OMCTRA
5 P-selector 0x0203
6 S-selector 0x0203
7 T-selector 0x0203
2.4 ES with LAN - summary of configuration steps
The following is an example for configuring ES with LAN.
1. Create CLNS object ES_1 in ES role:

ZQEC
:ES_1:ES:OMU:9:000000012345:2:39246F00000116000000000001;
2. Unlock the created CLNS object:
ZQEG:ES_1:UNL;
3. Restart CLNS using the parameters of ES_1 (backup timer is not used):
ZQET:ES_1:N;
4. Unlock the created linkages:
ZQLG:1::UNL;
5. Create local CLNS NSAP for OSI transport service:
ZQBN:1:L:4:NSEL=FF;
6. Create remote CLNS NSAP for ES1:
ZQBN:10:R:0:UNS=39246F0000011600000000000111000000019283FF;
g Note: You can also create this NSAP using NSAP type 5.
7. Create local network address for OSI transport service:

ZQBC:LOCALTRA:L;
8. Create remote network address for transport layer of OMC:
ZQBC:OMCTRA:R;
9. Attach NSAP 1 to the local network address of transport layer:
ZQBT:LOCALTRA:1;
10. Attach NSAP 10 to the remote network address:
ZQBT:OMCTRA:10;
11. Unlock the local NSAP:
ZQBG:1,UNL;
12. Unlock the remote NSAP:
ZQBG:10,UNL;
13. Create local FTAM application:
ZQDL:LFTAM:0::UNL:OMU:VFS:LOCALTRA:0201:0201:0201;
14. Create local CMISE application:
ZQDL:LCMISE:0::UNL:OMU:CMI:LOCALTRA:0203:0203:0203;
15. Create local VT application:
DN9812567 Issue: 14-1 © 2016 Nokia 51

ZQDL:LVT:0::UNL:OMU:VTP:LOCALTRA:0206:0206:0206;
16. Create remote CMISE application to OMC:
ZQDR:OMCCMISE:0::UNL:CMI:OMCTRA:0203:0203:0203;
2.5 Configuration inquiries of ES with LAN
You can check the configuration created in Section ES with LAN - summary of
configuration steps using inquiry commands of the MML interface. The commands and
their outputs are listed in chronological order.
ZQEI;
INTERROGATING CLNS
NODE IN ES ROLE
NS USER NS USER MAX PDU SYSTEM

CLNS NAME ROLE PRIM UNIT ACT UNIT LIFETIME ID STATE
--------- ---- --------- --------- -------- ---------------- ---------
-
ES_1 ES OMU-1 OMU-0 9 000000012345 UNL-BU-ACT
MAX MAN AREA ADDR COUNT: 3

MANUAL AREA ADDRESS: 39246F00000116000000000001
COMMAND EXECUTED
ZQLI;
INTERROGATING LINKAGE DATA
NODE IN ES ROLE
LINKAGE TYPE ROLE UNIT LOG UNIT TERM SNPA ADDRESS PVC PRIO STATE
------- ---- ---- ------- -------- ---- ---------------- ---- ---- -------
1 BRO ES OMU 4002H 1 - - - UNL-ENA
COMMAND EXECUTED
ZQBL;
INTERROGATED NSAP DATA
UNSPECIFIC NSAP
NBR ROLE STATE NETWORK ADDRESS INFORMATION

----- ------ ------- ----------------------------------------
10 REMOTE UNL-ENA 39246F0000011600000000000000000019283FF
LOCAL N-SELECTOR
NBR ROLE STATE SEL

----- ------ ------- ---
1 LOCAL UNL-ENA FF
COMMAND EXECUTED
52 © 2016 Nokia DN9812567 Issue: 14-1

ZQBI;
INTERROGATING NETWORK ADDRESS DATA
NET ADDR ROLE NSAP NR PRIO NSAP NR PRIO NSAP NR PRIO

-------- ------ ------- ---- ------- ---- ------- ----
LOCALTRA LOCAL 1 -
OMCTRA REMOTE 10 50
COMMAND EXECUTED
ZQDI;
LOCAL OSI APPLICATION DATA
AE-NAME APPL NET ADDR STATE UNIT FAM ID PROC ID

---------------- ------ -------- ------- ---------- ------- -------
LCMISE CMI LOCALTRA UNL-ENA OMU
LFTAM VFS LOCALTRA UNL-ENA OMU
LVT VTP LOCALTRA UNL-ENA OMU
DX 200 DX200-LAB 1995-01-01 19:50:18
REMOTE OSI APPLICATION DATA
AE-NAME APPL NET ADDR STATE

---------------- ------ -------- -------
OMCCMISE CMI OMCTRA UNL-ENA
COMMAND EXECUTED
DN9812567 Issue: 14-1 © 2016 Nokia 53

Example configuration of an IS with LAN and X.25 OSI Guide
interfaces
3 Example configuration of an IS with LAN and

X.25 interfaces
A summary of the configuration steps is presented in Section IS with LAN and X.25 -
summary of configuration steps. In the summary, the example commands are for the PCI
bus-based DX 200 network element. In this section, Flexi BSC is used as a configuration
example. For more information, see Section Defining local DX 200 OSI environment.
3.1 Structure of an example network in IS with LAN and

X.25 interfaces
In this example a DX 200 network element with LAN and X.25 interfaces is configured
with the IS operating role. The IS acts as a router and it also uses OSI services for data
transfer to other network elements. The example structure is presented in the Figure
Network structure of an example network in IS with LAN and X.25.
use empty configuration sheets enclosed in the Section OSI configuration sheets.
Figure 16 Network structure of an example network in IS with LAN and X.25
Nodetobeconfigured
systemid:020202020202
areaaddr:39246F00000116000000000001
systemid:010101010101
areaaddr:39246F00000116000000000001 systemid:010203040506
areaaddr:39246F00000116000000000001
X.25over IS2
ES1 PCM
IS1
LAN
PublicX.25
CLNSroute
CONSroute ES2 OMC
systemid:111111111111
areaaddr:39246F00000116000000000001
3.2 Configuration information of IS with LAN and X.25

interfaces
Required OSI services in IS1
54 © 2016 Nokia DN9812567 Issue: 14-1

OSI Guide Example configuration of an IS with LAN and X.25
interfaces
Network element IS1 is handled as a local network element. The required services are
the following:
• FTAM for file transfer to ES1 (CLNS) and IS2 (CLNS over X.25) and from OMC
(CLNS)
• CMISE for transmitting events to and actions from ES1 (CLNS) and ES2 (CONS)
• VT for virtual terminal sessions initiated by OMC (CLNS)
• PAD for X.25 sessions initiated by IS1 and responded by IS2 (CONS)
• MSW for MSW terminal sessions initiated by IS2 (CONS)
Hardware configuration of IS1

Hardware configuration of DX 200 network element IS1 is the following:
• 2N Central Memory (CM)

• OMU
– AS7-D data terminal to IS2: plug-in unit index 0, track 3 (Flexi BSC)
Address and parameter information of IS

AS7-C X.25 data terminal
Parameter Value
internal PCM: 15
internal PCM time slot: 1
external PCM: 25
external PCM time slot: 2
PVC channels to IS2: 1 (CONS)
2 (CLNS over X.25)
CLNS
Parameter Value
operating mode: IS
C-number 12345
system identifier: 000000012345
DN9812567 Issue: 14-1 © 2016 Nokia 55

interfaces
Parameter Value
MaximumPDULifetime value: 9 hops
MaximumAreaAddresses value: 3
unit of active NS user (O54LRS): OMU-0
The physical channels for X.25 data terminals are the following:
• physical channel 1 for AS7-C X.25 data terminal
The physical channel group for local PVC applications (MSW) is the following:
• channel group MSWPVC
The physical channel group for outgoing routing is the following:
• channel group TOPCKNET for public X.25 packet network
The selectors of the local applications are the following:
VT tsel 0x0206, ssel 0x0206, psel 0x0206
Address information of ES1

NSAP 39246F000001160000000000000000098765FF
Address information of IS2

NSAP 39246F00000116000000000001000000045678FF
DTE address 11112222
PVC channel for CONS 1
PVC channel for CLNS 2
Address information of ES2

DTE address 11113333
56 © 2016 Nokia DN9812567 Issue: 14-1

interfaces
3.3 Configuration sheets for IS with LAN and X.25

interfaces
Sheets for the local network element
configuration.
Table 18 Configuration sheet for AS7-C

1 Computer unit and index (OMU/ OMU,0
MSW / CHU)

identification
3 Dual port memory address default
4 Interface type (V.24 / V.35 / X.21) -
5 Source of clock signal (YES / NO) -
6 Bit rate -
7 Mode (DTE / DCE) DCE
8 Name of X.25 parameter set AS7C_2
9 Range of logical channels 1-31
10 Link level window size default
11 Packet level window size default
12 Maximum user data on packet level default
13 SNPA address (that is, DTE not used

number)
14 Own SNPA address filled by (AC25 / not used

Network / Not filled)
15 Channel number 1
Table 19 Physical channel group configuration sheet for local PVC channel
1 Physical channel group name MSWPVC
2 Class (PVC/outgoing call routing) PVC
DN9812567 Issue: 14-1 © 2016 Nokia 57

interfaces
Table 19 Physical channel group configuration sheet for local PVC channel (Cont.)
3 Channel number and priority 1 50
Table 20 Physical channel group configuration sheet for TOPCKNET

1 Physical channel group name TOPCKNET
2 Class (PVC/outgoing call routing) outgoing
3 Channel number and priority 2 50

1 CLNS name IS_1
2 CLNS role IS
3 NS user primary unit OMU,0
Table 22 PVC X.25 linkage configuration sheet for IS2

2 Role of linkage IS
3 Computer unit type and index OMU,0

identification
5 X.25 address/PVC number 2
Table 23 SVC X.25 linkage configuration sheet for IS2

58 © 2016 Nokia DN9812567 Issue: 14-1

interfaces
Table 23 SVC X.25 linkage configuration sheet for IS2 (Cont.)

identification
Table 24 SVC X.25 linkage configuration sheet for ES2

4 Plug-in unit index 3
Table 25 Broadcast linkage configuration sheet for ES1


identification
Table 26 Local X.25 NSAP configuration sheet for PAD

2 DTE number 12345678
3 SPI 01000000
Table 27 Local X.25 NSAP configuration sheet for transport layer

3 SPI 03010100
Table 28 Local PVC X.25 NSAP configuration sheet for MSW

DN9812567 Issue: 14-1 © 2016 Nokia 59

interfaces
Table 28 Local PVC X.25 NSAP configuration sheet for MSW (Cont.)
2 CHG MSWPVC

2 NSEL FF
Table 30 Local network address configuration sheet for PAD

1 Network address name LOCALPAD
2 NSAP 1

2 NSAP 2
3 NSAP 4
Table 32 Local network address configuration sheet for MSW

1 Network address name LOCALMSW
2 NSAP 3
The value of the network address role is 'BOTH'.
Table 33 Local application configuration sheet for MSW

1 Application entity name LMSW
4 Application type MSW
6 Family -
8 Network address LOCALMSW
9 P-selector -
60 © 2016 Nokia DN9812567 Issue: 14-1

interfaces
Table 33 Local application configuration sheet for MSW (Cont.)

10 S-selector -
11 T-selector -

6 Family -
9 P-selector 0x0201
Table 35 Local application configuration sheet for PAD

1 Application entity name LPAD
4 Application type PAD
5 Computer unit and index OMU,0
6 Family -
8 Network address LOCALPAD
9 P-selector -
10 S-selector -
11 T-selector -
DN9812567 Issue: 14-1 © 2016 Nokia 61

interfaces
Table 36 Local application configuration sheet for VT

1 Application entity name LVT
4 Application type VTP
6 Family -
9 P-selector 0x0206
Table 37 Remote X.25 NSAP configuration sheet for IS2 PAD

3 SPI 01000000
4 Channel group TOPCKNET
Table 38 Remote X.25 NSAP configuration sheet for IS2 transport layer
3 SPI 02010100
Table 39 Remote X.25 NSAP configuration sheet for ES2 transport layer
3 SPI 03010100
62 © 2016 Nokia DN9812567 Issue: 14-1

interfaces
Table 40 CLNS NSAP configuration sheet for ES1 transport layer

7 DSP area 0001
9 N-selector FF
Table 41 CLNS NSAP configuration sheet for IS1 transport layer

7 DSP area 0001
9 N-selector FF
Table 42 Remote network address configuration sheet for ES1 transport layer
1 Network address name ES1TRA
2 NSAP 13
3 Priority default
Table 43 Remote network address configuration sheet for IS2 transport layer
1 Network address name IS2TRA
2 NSAP 11
DN9812567 Issue: 14-1 © 2016 Nokia 63

interfaces
Table 43 Remote network address configuration sheet for IS2 transport layer (Cont.)
3 Priority 60
4 NSAP 14
5 Priority 50
Table 44 Remote network address configuration sheet for IS2 PAD

1 Network address name IS2PAD
2 NSAP 10
3 Priority 50
Table 45 Remote network address configuration sheet for ES2 transport layer
1 Network address name ES2TRA
2 NSAP 12
3 Priority default
Table 46 Remote application configuration sheet for ES1 CMISE

1 Application name ES1CMISE
5 P-selector 0x0203
6 S-selector 0x0203
7 T-selector 0x0203
8 Network address ES1TRA
Table 47 Remote application configuration sheet for ES2 CMISE

1 Application name ES2CMISE
5 P-selector 0x0203
64 © 2016 Nokia DN9812567 Issue: 14-1

interfaces
Table 47 Remote application configuration sheet for ES2 CMISE (Cont.)

6 S-selector 0x0203
7 T-selector 0x0203
Table 48 Remote application configuration sheet for ES1 FTAM

1 Application name ES1FTAM
5 P-selector 0x0201
6 S-selector 0x0201
7 T-selector 0x0201
Table 49 Remote application configuration sheet for IS2 FTAM

1 Application name IS2FTAM
5 P-selector 0x0201
6 S-selector 0x0201
7 T-selector 0x0201
8 Network address IS2TRA
Table 50 Remote application configuration sheet for IS2 PAD

1 Application name IS2PAD
DN9812567 Issue: 14-1 © 2016 Nokia 65

interfaces
Table 50 Remote application configuration sheet for IS2 PAD (Cont.)

5 P-selector
6 S-selector
7 T-selector
8 Network address IS2PAD
3.4 IS with LAN and X.25 - summary of configuration

steps
The following is an example for configuring IS with LAN and X.25.
1. Create and connect AS7-C data terminal:

ZWTP:OMU:AS7_C,1,4::X25,4,14,TSL,1,0;
ZWUC:OMU:AS7_C,1;
2. Create X.25 parameter set AS7C_2 for AS7-C data terminal:
ZQXC:AS7C_2;
ZQXM:AS7C_2:FPVC=1,LPVC=2;
3. Create physical channel 1 for AS7-C (no SNPA address is given):
ZQCC:1:OMU,0,2:,DTE,AS7C_2:25-2;
4. Unlock the created physical channels:
ZQSC:1,UNL;
5. Create the channel group for PVC channel #1:
ZQGC:MSWPVC:1,1,50;
6. Create the channel group for TOPCKNET. It includes only the SVC channels:
ZQGC:TOPCKNET:2,0,50;
7. Create CLNS object IS_1 in IS role:
ZQEC
:IS_1:IS:OMU:9:000000012345:2:39246F0000116000000000001;
8. Create PVC X.25 linkage #1 to IS2 (primary linkage):
ZQLC:1:IS:OMU:2:PVC=2;
9. Create SVC X.25 linkage #2 to IS2 (backup linkage):
ZQLC:2:IS:OMU:3:SNPA=11112222::;
10. Create SVC X.25 linkage #3 to ES2:
ZQLC:3:IS:OMU:3:SNPA=11113333::;
11. Create the broadcast linkage #4 for Ethernet interface (default parameter set and
priority):
ZQLL:4:IS:OMU,0:1:::;
ZQEG:IS_1:UNL;
13. Restart the CLNS using parameters of IS_1 (backup timer is not used):
ZQET:IS_1:N;
14. Unlock the created linkages:
ZQLG:1&&3::UNL;
15. Create X.25 NSAP for the transport layer:
66 © 2016 Nokia DN9812567 Issue: 14-1

interfaces
ZQBN:1:L:1:DTE=12345678,SPI=03010100;
16. Create X.25 NSAP for PAD using SVC:
ZQBN:2:L:1:DTE=12345678,SPI=01000000;
17. Create X.25 NSAP for MSW using PVC:
ZQBN:3:L:3:CHG=MSWPVC;
18. Create CLNS NSAP for the transport layer:
ZQBN:4:L:4:NSEL=FF;
19. Create X.25 NSAP for IS2 PAD:
ZQBN:10:R:1:DTE=11112222,SPI=01000000,CHG=TOPCKNET;
20. Create X.25 NSAP for IS2 transport layer:
21. Create X.25 NSAP for ES2 transport layer:
22. Create CLNS NSAP for ES1:
ZQBN:13:R:0:UNS=39246F000001160000000000001000000098765FF;
g Note: NSAP can also be created using NSAP type 5.
23. Create CLNS NSAP for IS2:

ZQBN:14:R:0:UNS=39246F00000116000000000001000000045678FF;
g Note: NSAP can also be created using NSAP type 5.
24. Create network address for the transport layer:

ZQBC:LOCALTRA:L;
25. Create network address for PAD:
ZQBC:LOCALPAD:L;
26. Create network address for MSW:
ZQBC:LOCALMSW:B;
27. Create network address for transport layer of ES1:
ZQBC:ES1TRA:R;
28. Create network address for IS2 transport layer:
ZQBC:IS2TRA:R;
29. Create network address for IS2 PAD:
ZQBC:IS2PAD:R;
30. Create network address for transport layer of ES2:
ZQBC:ES2TRA:R;
31. Attach NSAPs to network address for transport layer:
ZQBT:LOCALTRA:1;
ZQBT:LOCALTRA:4;
32. Attach NSAPs to network address for PAD:
ZQBT:LOCALPAD:2;
33. Attach NSAPs to network address for MSW:
ZQBT:LOCALMSW:3;
34. Attach NSAPs of network address for ES1 transport layer
ZQBT:ES1TRA:13;
35. Attach NSAPs of network address for IS2 transport layer:
ZQBT:IS2TRA:14,50;
ZQBT:IS2TRA:11,40;
36. Attach NSAPs of network address for IS2 PAD:
DN9812567 Issue: 14-1 © 2016 Nokia 67

interfaces
ZQBT:IS2PAD:10;
37. Attach NSAPs of network address for ES2 transport layer:
ZQBT:ES2TRA:12;
38. Unlock the created NSAPs:
ZQBG:1&&14,UNL;
39. Create local PAD application:
ZQDL:LPAD:::UNL:OMU,0:PAD:LOCALPAD;
40. Create local MSW application:
ZQDL:LMSW:::UNL:OMU,0:MSW:LOCALMSW;
42. Create remote FTAM application to ES1:
ZQDR:ES1FTAM:0::UNL:VFS:ES1TRA:0201:0201:0201;
43. Create remote FTAM application to IS2:
ZQDR:IS2FTAM:0::UNL:VFS:IS2TRA:0201:0201:0201;
44. Create remote PAD application to IS2:
ZQDR:IS2PAD:::UNL:PAD:IS2PAD;
45. Create remote CMISE application to ES1:
ZQDR:ES1CMISE:0::UNL:CMI:ES1TRA:0203:0203:0203;
46. Create remote CMISE application to ES2:
ZQDR:ES2CMISE:0::UNL:CMI:ES2TRA:0203:0203:0203;
47. Create local VT application:
ZQDL:LVT:0::UNL:OMU:VTP:LOCALTRA:0206:0206:0206;
3.5 Configuration inquiries for IS with LAN and X.25

interfaces
You can check the configuration created in Section IS with LAN and X.25 - summary of
configuration steps using the inquiry commands of the MML interface. The commands
and their outputs are listed in chronological order.
ZWTI:P:OMU:AS7_C,1
OMU IN LOC 1A003-08
AS7_C 1 TRACK: 4
MS:FA000000 ME:FBFFFFFF IS:7140 IE:717F
INT:2AH SW:06490048
TSLS 30 20 10 0
X25 4M PCM: 14 B 00000000000000000000000000000010
R 00000000000000000000000000000010
CONNECTOR SIDE: HOR: VER: POINT: 0
TOTAL OF 1 UNITS, 1 PLUG-IN UNITS AND 1 FUNCTIONS

COMMAND EXECUTED
ZQXI;
PARAMETER SET NAME: AS7U_2
==================
MAXIMUM NETWORK SERVICE DATA UNIT LENGTH: 2048 BYTES
L2 CONNECTION MODE: INITIATED AFTER START UP
68 © 2016 Nokia DN9812567 Issue: 14-1

interfaces
LEVEL 2 PARAMETERS:
------------------
L2 TIMER T1: 6 SECONDS L2 BITS IN FRAME: 1024 BITS
L2 TIMER T2: NOT IN USE L2 RETRY COUNT: 10 TIMES
L2 TIMER T3: NOT IN USE L2 WINDOW: 7 FRAMES
L2 INTERFRAME FILL: 01111110 L2 LINE DOWN TIMER: 20 (NOT
SUPPORTED)
LEVEL 3 PARAMETERS:
------------------
L3 USER DATA SIZE: 128 BYTES
L3 SEND WINDOW SIZE: 2 FRAMES
L3 MODULO: 8
L3 TIMER T20: 10 SECONDS

L3 TIMER T22: 10 SECONDS L3 RESET RETRY COUNT: 5 TIMES
L3 TIMER T23: 10 SECONDS L3 CLEAR RETRY COUNT: 5 TIMES
L3 FIRST PVC: 1 L3 LAST PVC: 2

L3 LIC: 0 (NOT SUPPORTED) L3 HIC: 0 (NOT SUPPORTED)
L3 LTC: 0 (= NOT IN USE) L3 HTC: 0 (= NOT IN USE)
L3 LOC: 0 (NOT SUPPORTED) L3 HOC: 0 (NOT SUPPORTED)
USER FACILITIES:
---------------
NO USER FACILITIES
PARAMETER SET NAME: AC25S_3

==================

LEVEL 2 PARAMETERS:
------------------
L2 INTERFRAME FILL: 01111110 L2 LINE DOWN TIMER: 20 (NOT
SUPPORTED)
LEVEL 3 PARAMETERS:
------------------
L3 MODULO: 8

L3 FIRST PVC: 0 (= NOT IN USE) L3 LAST PVC: 0 (= NOT IN USE)

DN9812567 Issue: 14-1 © 2016 Nokia 69

interfaces
L3 LTC: 1 L3 HTC: 16
USER FACILITIES:
---------------
NO USER FACILITIES
COMMAND EXECUTED
ZQCI;
PHYSICAL CHANNELS THROUGH DIGITAL TERMINAL
DTE/ X.25 ACTIVE INTERNAL
CHANNEL SNPA-ADDRESS UNIT TERM DCE PARAM SET PCM - TSL PCM - TSL
------- ---------------- -------- ---- ---- --------- ---------- ----------
1 SNPA NOT IN USE OMU-0 2 DTE AS7U_2 25 - 2 14 - 22
PHYSICAL CHANNELS THROUGH ANALOG TERMINAL
SNPA DTE/ X.25 PHYS DATA RATE

CHANNEL SNPA-ADDRESS INTP UNIT TERM DCE PARAM SET LEVEL BITS/S
------- ---------------- ---- -------- ---- ---- --------- ------ ---------
2 12345678 SIGN OMU-0 3 DTE AC25S_3 V.24 9600
COMMAND EXECUTED
ZQSI;
INTERROGATING PHYSICAL CHANNEL STATE
CHANNEL TERM
CHANNEL UNIT TERM STATE STATE INFO
------- ---------- ---- ------- ----- ----
1 OMU-0 2 UNL-ENA WO-EX CHAN USES DIGITAL TERM
2 OMU-0 3 UNL-ENA WO-EX CHAN USES ANALOG TERM
COMMAND EXECUTED
ZQGI;
INTERROGATED PHYSICAL CHANNEL GROUP DATA
GROUP VC CHAN
GROUP ID STATE CHAN NUMBER PRIO STATE
-------- ----- --------------------------
TOPCKNET AV 2 0 50 UNL-ENA
MSWPVC AV 1 1 50 UNL-ENA
COMMAND EXECUTED
ZQEI;
INTERROGATING CLNS
NODE IN ES ROLE

--------- ---- --------- --------- -------- ---------------- ---------
70 © 2016 Nokia DN9812567 Issue: 14-1

interfaces
-
IS_1 IS OMU-0 OMU-0 9 000000012345 UNL-BU-ENA

COMMAND EXECUTED
ZQLI;
NODE IN ES ROLE
------- ---- ---- ------- -------- ---- ---------------- ---- ---- -------
1 X.25 IS OMU-0 4121H 2 - 2 - UNL-ENA
2 X.25 IS OMU-1 4121H 7 11112222 - - UNL-ENA
3 BRO IS OMU-0 4121H 5 - - - UNL-ENA
COMMAND EXECUTED
ZQBL;
UNSPECIFIC NSAP

----- ------ ------- ----------------------------------------
X.25 NETWORK PROTOCOL ADDRESS INFORMATION
NBR ROLE STATE CHG DTE SPI

----- ------ ------- -------- --------------- --------
1 LOCAL UNL-ENA - 12345678 03010100
2 LOCAL UNL-ENA - 12345678 01000000
10 REMOTE UNL-ENA TOPCKNET 11112222 01000000
X.25 PERMANENT VIRTUAL CIRCUIT
NBR ROLE STATE CHG

----- ------ ----- --------
3 LOCAL UNL MSWPVC
LOCAL N-SELECTOR
NBR ROLE STATE SEL

----- ------ ----- ---
4 LOCAL UNL FF
COMMAND EXECUTED
DN9812567 Issue: 14-1 © 2016 Nokia 71

interfaces
ZQBI;

-------- ------ ------- ---- ------- ---- ------- ----
LOCALTRA BOTH 1 - 4 -
LOCALMSW LOCAL 3 -
LOCALPAD LOCAL 2 -
ES1TRA REMOTE 13 50
ES2TRA REMOTE 12 50
1S2PAD REMOTE 10 50
1S2TRA REMOTE 11 40 14 50
COMMAND EXECUTED
ZQDI;

---------------- ------ -------- ------- ---------- ------- -------
LPAD PAD LOCALPAD UNL-ENA OMU-0
LMSW MSW LOCALMSW UNL-ENA OMU-0
LVT VTP LOCALTRA UNL-ENA OMU

---------------- ------ -------- -------
ES1FTAM VFS ES1TRA UNL-ENA
IS2FTAM VFS IS2TRA UNL-ENA
ES1CMISE CMI ESITRA UNL-ENA
ES2CMISE CMI ES2TRA UNL-ENA
COMMAND EXECUTED
72 © 2016 Nokia DN9812567 Issue: 14-1

OSI Guide Example configuration of an ES with LAN and X.25
interfaces
4 Example configuration of an ES with LAN and

X.25 interfaces
A summary of the configuration steps is presented in Section ES with LAN and X.25 -
summary of configuration steps. In the summary, the example commands are for the PCI
bus-based DX 200 network element. In this section, Flexi BSC is used as a configuration
example. For more information, see Section Defining local DX 200 OSI environment.
4.1 Structure of an example network in ES with LAN

and X.25 interfaces
In this example, a DX 200 network element with LAN and X.25 interfaces is configured
with the ES operating role. The ES and the Administrative Computer (AdC) are
connected to each other using the OSI routing network, and X.25 packet network. OSI
services are needed for data transfer between them. All OSI connections are initiated by
the AdC. The example structure is presented in Figure Network structure of an example
network in ES with LAN and X.25.
use empty configuration sheets enclosed in Section OSI configuration sheets.
Figure 17 Network structure of an example network in ES with LAN and X.25
C-number:12345 C-number:98765
systemid:000000012345 systemid:000000098765
areaaddr:39246F00000116000000000001 areaaddr:39246F00000116000000000001
OSIRoutingNetwork
ES1 AdC
X.25PacketNetwork
CLNSroute
CONSroute
Nodetobeconfigured
max.3hops
4.2 Configuration information of ES with LAN and X.25

interfaces
Required OSI services in ES1
The ES1 network element is handled as a local network element. The required services
are the following:
• FTAM for file transfer from the AdC

• PAD for X.25 sessions initiated by the AdC
Hardware configuration of ES1
DN9812567 Issue: 14-1 © 2016 Nokia 73

Example configuration of an ES with LAN and X.25 OSI Guide
interfaces
The hardware configuration of the DX 200 network element ES1 is the following:
• central memory (CM)

• OMU with:
Address and parameter information of ES1

AS7-C X.25 data terminal
DTE number 12345678
SVC channels 1-16
Ethernet interface (CLNS)
Parameter Value
operating mode: ES
C-number 12345
system identifier 000000012345
MaximumAreaAddress value: 3
MaximumPDULifetime value: 9 hops
unit of active NS user (O54LRS): OMU
The physical channel for X.25 data terminals is physical channel 2 for AS7-C X.25 data
terminal.
The selector of the local applications is the following:
4.3 Configuration sheets for ES with LAN and X.25

interfaces
Sheets for Local Network Element
configuration.
74 © 2016 Nokia DN9812567 Issue: 14-1

interfaces
Table 51 Configuration sheet for AS7-D

1 Computer unit and index (OMU / MSW / OMU,0
CHU)
2 Plug-in unit index/PCI device identification 2
3 Dual port memory address default
4 Interface type (V.24 / V.35 / X.21) V.24
5 Source of clock signal (YES / NO) NO
6 Mode (DTE / DCE) DTE
7 Name of X.25 parameter set AS7D_2
8 Range of logical channels DEFAULT
9 Link level window size default
10 Packet level window size default
11 Maximum user data in packet level default
12 SNPA address (that is, DTE number) not used

1 CLNS name ES_1
2 CLNS role ES
3 NS user primary unit OMU
Table 53 Broadcast linkage configuration sheet for ES

2 Role of linkage ES
DN9812567 Issue: 14-1 © 2016 Nokia 75

interfaces
Table 53 Broadcast linkage configuration sheet for ES (Cont.)

4 Plug-in unit index/PCI device identification 0

2 NSEL FF

3 SPI 01000000

3 SPI 03010100

2 NSAP 1
3 NSAP 3
Table 58 Local network address configuration sheet for PAD

1 Network address name LOCALPAD
2 NSAP 2

76 © 2016 Nokia DN9812567 Issue: 14-1

interfaces
Table 59 Local application configuration sheet for FTAM (Cont.)

6 Family -
9 P-selector 0x0201
Table 60 Local application configuration sheet for PAD

1 Application entity name LPAD
5 Computer unit and index OMU,0
6 Family -
8 Network address LOCALPAD
9 P-selector -
10 S-selector -
11 T-selector -
4.4 ES with LAN and X.25 - summary of configuration

steps
The following is an example for configuring ES with LAN and X.25.
1. Create and connect to AS7-D data terminal:

ZWTP:OMU,0:AS7_D,0,3::X25,2,15,TSL,1;
ZWUC:OMU,0:AS7_D,2;
2. Create X.25 parameter set AS7D_2 for AS7-D data terminal:
ZQXC:AS7D_2;
ZQXM:AS7D_2:FPVC=1,LPVC=2;
DN9812567 Issue: 14-1 © 2016 Nokia 77

interfaces
3. Create physical channel 1 for AS7-D (no NSAP address is given):

ZQCC:2:OMU,0,2:,DTE,AS7D_2:25-2;
4. Unlock the created physical channel:
ZQSC:2,UNL;
5. Create CLNS object ES_1 in ES role:
ZQEC
:ES_1:ES:OMU,0:0:9:000000012345:2:39246F0000011600000000000
1;
6. Create broadcast linkage 1 for Ethernet interface (default parameter set and priority):
ZQLL:1:ES:OMU,0:0:::;
ZQEG:ES_1:UNL;
8. Restart CLNS using the parameters of ES_1 (backup timer is not used):
ZQET:ES_1:N;
9. Unlock the created linkage:
ZQLG:1::UNL;
10. Create local CLNS NSAP for OSI transport service:
ZQBN:1:L:4:NSEL=FF;
11. Create X.25 NSAP for transport layer:
ZQBN:3:L:1:DTE=12345678,SPI=03010100;
12. Create X.25 NSAP for PAD using SVC:
ZQBN:2:L:1:DTE=12345678,SPI=01000000;
13. Create local network address for the OSI transport service:
ZQBC:LOCALTRA:L;
14. Attach NSAPs 1 and 3 to the local network address of transport layer:
ZQBT:LOCALTRA:1;
ZQBT:LOCALTRA:3;
15. Create network address for the PAD:
ZQBC:LOCALPAD:L;
16. Attach NSAP 2 to the network address of the PAD:
ZQBT:LOCALPAD:2;
17. Unlock the local NSAPs:
ZQBG:1&&3,UNL;
18. Create local PAD application:
ZQDL:LPAD:::UNL:OMU:PAD:LOCALPAD;
4.5 Configuration inquiries for ES with LAN and X.25

interfaces
You can check the configuration created in Section ES with LAN and X.25 - summary of
configuration steps using inquiry commands of the MML interface. The commands and
their outputs are listed in chronological order.
ZWTI:P:OMU:AC25_A,2;
OMU IN LOC 1A033-00
AC25_A 2 TRACK: 44
78 © 2016 Nokia DN9812567 Issue: 14-1

interfaces
MS:80100000 ME:801FFFFF IS: IE:

INT:32H SW:
TOTAL OF 1 UNITS AND 1 PLUG-IN UNITS
COMMAND EXECUTED
ZQXI;
PARAMETER SET NAME: AC25A_2
==================
LEVEL 2 PARAMETERS:
------------------
L2 INTERFRAME FILL: 01111110 L2 LINE DOWN TIMER: 20(NOT
SUPPORTED)
LEVEL 3 PARAMETERS:
------------------
L3 MODULO: 8

L3 FIRST PVC: 0 (= NOT IN USE) L3 LAST PVC: 0 (= NOT IN USE)

L3 LTC: 1 L3 HTC: 16
USER FACILITIES:
---------------
NO USER FACILITIES
COMMAND EXECUTED
ZQCI;
PHYSICAL CHANNELS THROUGH DIGITAL TERMINAL
DTE/ X.25 ACTIVE INTERNAL
CHANNEL SNPA-ADDRESS UNIT TERM DCE PARAM SET PCM - TSL PCM - TSL
------- ---------------- -------- ---- ---- --------- ---------- ----------
PHYSICAL CHANNELS THROUGH DIGITAL TERMINAL NOT FOUND
PHYSICAL CHANNELS THROUGH ANALOG TERMINAL
SNPA DTE/ X.25 PHYS DATA RATE

CHANNEL SNPA-ADDRESS INTP UNIT TERM DCE PARAM SET LEVEL BITS/S
------- ---------------- ---- -------- ---- ---- --------- ------ ---------
DN9812567 Issue: 14-1 © 2016 Nokia 79

interfaces
2 12345678 SIGN OMU 3 DTE AC25A_3 V.24 9600
COMMAND EXECUTED
ZQSI;
CHANNEL TERM
------- ---------- ---- ------- ----- ----
2 OMU 3 UNL-ENA WO-EX CHAN USES ANALOG TERM
COMMAND EXECUTED
ZQEI;
INTERROGATING CLNS
NODE IN ES ROLE

--------- ---- --------- --------- -------- ---------------- ---------
-
ES_1 ES OMU OMU 5 000000012345 UNL-BU-
ACT

COMMAND EXECUTED
ZQLI;
NODE IN ES ROLE
------- ---- ---- ------- -------- ---- ---------------- ---- ---- -------
1 BRO ES OMU 4002H 0 - - - UNL-ENA
COMMAND EXECUTED
ZQBL;

----- ------ ------- -------- --------------- --------
2 LOCAL UNL-ENA - 12345678 01000000
3 LOCAL UNL-ENA - 12345678 03010100
LOCAL N-SELECTOR
NBR ROLE STATE SEL

----- ------ ----- ---
80 © 2016 Nokia DN9812567 Issue: 14-1

interfaces
1 LOCAL LOC FF
COMMAND EXECUTED
ZQBI;

-------- ------ ------- ---- ------- ---- ------- ----
LOCALTRA LOCAL 1 - 3 -
LOCALPAD LOCAL 2 -
COMMAND EXECUTED
ZQDI;

---------------- ------ -------- ------- ---------- ------- -------
LPAD PAD LOCALPAD UNL-ENA OMU
COMMAND EXECUTED
DN9812567 Issue: 14-1 © 2016 Nokia 81

Example configuration of OSI over TCP/IP interface OSI Guide
5 Example configuration of OSI over TCP/IP

interface
When OSI over TCP/IP feature is in use, OSI traffic goes via OMU’s LAN interface. On
that case only NSAP addresses and OSI applications need to be configured. NSAP
addresses configuration commands got new parameters for IP based NSAP addresses,
OSI application configuration related commands are given as before.
OSI over TCP/IP feature shall be configured to both end of OSI communication peers, in
BSC and NetAct.
5.1 Structure of an example network.
Below is an example figure for OSI over TCP/IP solution for CBC, Q3 and Node
manager connection:
Figure 18 OSI over TCP/IP solution for CBC, Q3 and Node manager connection
Q3
NetAct NodeManager
Serverwith
Q1over TCP/IP
communicationserver NodeManagers
IP address:10.12.17.121
Port:102
NSAP:10
OSIover TCP/IP
OSIover TCP/IP
IP backbone
OSIover TCP/IP
BSC CBCserver
IP address:10.12.17.42 IP address:10.12.17.122
Port:102
NSAP:20
5.2 OSI over TCP/IP - summary of configuration steps
The following is an example for configuring OSI over TCP/IP feature with FTAM and
CMISE applications.
1. At first check that license is installed and activated:

• Transfer license file (e.g. E1718113.XML) to DW0-/LICENCE/ dirctory on OMU
disk.
• Install license by command: ZW7L:E1718113;
82 © 2016 Nokia DN9812567 Issue: 14-1

OSI Guide Example configuration of OSI over TCP/IP interface
• Activate license: ZW7M:FEA=1242:ON:;
2. Check OMU’s IP address:

ZQRI:OMU;
3. Create local NSAP for OSI transport service (add OMU’s IP address to IPV4 field):
ZQBN:1:L:6:IPV4="10.12.17.42";
4. Create remote NSAP for OSI transport service (you can create as many NSAP’s as
there are end systems):
ZQBN:10:R:6:IPV4="10.12.17.121",PORT=102;
5. Create local network address for OSI transport service:.
ZQBC:LOCALTRA:L;
6. Create remote network address for transport layer of OMC:
ZQBC:OMCTRA:R;
7. Attach NSAP 1 to the local network address of transport layer:
ZQBT:LOCALTRA:1;
8. Attach NSAP 10 to the remote network address:
ZQBT:OMCTRA:10;
9. Unlock the local NSAP:
ZQBG:1,UNL;
10. Unlock the remote NSAP:
ZQBG:10,UNL;
12. Create local CMISE application:
ZQDL:LCMISE:0::UNL:OMU:CMI,2B1,0:LOCALTRA:0203:0203:0203;
13. Create remote CMISE application to OMC:
ZQDR:OMCCMISE:0::UNL:CMI:OMCTRA:0203:0203:0203;
14. Create remote FTAM application:
ZQDR:REMFTAM:0::UNL:VFS:OMCTRA:0201:0201:0201;
15. Create remote NSAP for CBC server:
ZQBN:20:R:6:IPV4="10.12.17.122",PORT=102,;
16. Create remote network address:
ZQBC:REMCBC:R:;
17. Attach remote NSAPs to network address:
ZQBT:REMCBC:20,75:;
18. Create local OSI application for CBC:
ZQDL:BSC012345CBC:::UNL:OMU:TPU,038C,0:LOCALTRA:::7733:;
19. Create remote OSI application for CBC:
ZQDR:CBCREMOTEAPPL:0::UNL:TPU:REMCBC:::7733:;
20. Unlock CBC NSAP:
ZQBG:20,UNL;
5.3 Configuration inquiries of OSI over TCP/IP
You can check the configuration created in Section OSI over TCP/IP - summary of
configuration steps using the inquiry commands of the MML interface.
INTERROGATE NETWORK NSAP DATA
DN9812567 Issue: 14-1 © 2016 Nokia 83

Example configuration of OSI over TCP/IP interface OSI Guide
ZQBL:;
BSC HOLSTI 2008-09-17 11:21:12
IP BASED NSAP
NBR ROLE STATE IP ADDRESS PORT

----- ------ ------- -------------------------------- -----
1 LOCAL UNL-ENA 10.12.17.42 102
10 REMOTE UNL-ENA 10.12.17.121 102
20 REMOTE UNL-ENA 10.12.17.122 102
COMMAND EXECUTED
INTERROGATE NETWORK ADDRESS DATA

ZQBI:;
BSC HOLSTI 2008-09-17 11:21:27

-------- ------ ------- ---- ------- ---- ------- ----
LOCALTRA LOCAL 1 -
OMCTRA REMOTE 10 50
REMCBC REMOTE 20 75
COMMAND EXECUTED
INTERROGATE OSI APPLICATION DATA

ZQDI:;
BSC HOLSTI 2008-09-17 11:21:43

---------------- ------ -------- ------- ---------- ------- -------
LCMISE CMISE LOCALTRA UNL-ENA OMU 02B1H 0000H
BSC012345CBC TPU LOCALTRA UNL-ENA OMU 038CH 0000H
HLRi HALSSILA 2008-12-02 09:33:49

---------------- ------ -------- -------
REMFTAM VFS OMCTRA UNL-ENA
OMCCMISE CMISE OMCTRA UNL-ENA
CBCREMOTEAPPL TPU REMCBC UNL-ENA
COMMAND EXECUTED
84 © 2016 Nokia DN9812567 Issue: 14-1

OSI Guide Defining local DX 200 OSI environment
6 Defining local DX 200 OSI environment

Purpose
After establishing a detailed plan of your network as described in chapter DX 200 OSI
environment, you are ready to configure your local OSI environment. The following six
steps briefly describe how the configuration proceeds.
1. Define the hardware configuration, set the strappings of the data terminals, and
define the physical layer parameters according to your hardware configuration and
the corresponding subnetwork interfaces as described in section Defining AS7–C or
AS7–D data terminal.
Refer to the instructions about hardware configuration management for more
information on the subject.
2. Create the CONS as described in section Creating connection-oriented network
service (CONS) if needed.
3. Create the CLNS as described in section Creating connectionless network service
(CLNS) if needed.
4. Retrieve the local NSAP address information from the local NSAP address
administration and create the NSAP addresses according to this information as
described in section Defining local OSI addresses.
5. Create local network addresses and local applications as described in section
Defining local OSI applications.
6. After the local DX 200 OSI environment configuration, define the remote OSI
environment as described in chapter Defining remote OSI environment.
Chapter OSI configuration examples includes detailed examples of the configuring

procedures.
6.1 Defining AS7–C or AS7–D data terminal

Purpose
In the PCI bus-based network element, you can use the AS7–C or AS7-D type of data
terminal.
Procedure
1 Create the AS7 data terminal

You can define an AS7–C, or an AS7-D data terminal with the WTP command. The
required parameters are the following:
• identification parameters of the data terminal
– unit type
– unit index
– plug-in unit index
– plug-in unit track
DN9812567 Issue: 14-1 © 2016 Nokia 85

Defining local DX 200 OSI environment OSI Guide
• type of the data terminal (AS7–C, or AS7-D)

• function (X.25)
• PCM type
• PCM number
• PCM time slots
For example, if you would like to create an AS7–D data terminal (plug-in unit index 0,
track 3) in OMU-0, with the X.25 function, 2 M circuit, PCM number 1, time slot 1,
and default memory address space and parameters, use the following command:
ZWTP:OMU,0:AS7_D,0,3::X25,2,1,TSL,1;
For example, if you would like to create an AS7-D data terminal (plug-in unit index 0,
track 3) in OMU-0, with the X.25 function, 4 M circuit, PCM number 1, time slots 1-
17, and the default memory address space and parameters, use the following
command:
ZWTP:OMU,0:AS7_D,0,3::X25,4,1,TSL,1&&17;
For more information on the WTP command, refer to the information on equipment
management.
The PCM number can be retrieved from the site-specific document Use of PCM links
of GSW.
For more information on the AS7–C, or AS7-D data terminals, refer to the
descriptions of the plug-in units.
2 Connect the circuits

After the AS7-C, or AS7-D plug-in unit has been created with the WTP command, the
circuit connection must be made with the WUC command, for example:
ZWUC:OMU,0:AS7_D,2;
For more information on the WUC command, refer to the information on unit
connections handling.
When the above configuration has been made, the unit must be restarted in order to
get the configuration into effect. The number of used PCMs must be exactly the
same in both the internal and external PCMs as at the remote end.
3 Check the strappings of the AS7 data terminal

The dual port memory address ranges of the AS7–C and AS7–D data terminals are
set dynamically.
For more information, refer to the section Data terminal strappings.
The current hardware settings of the AS7-D data terminal is located in the OMU-0
unit can be displayed with the following command:
ZWTI:P:OMU,0:AS7_D;
4 Restart the newly configured functional unit
86 © 2016 Nokia DN9812567 Issue: 14-1

6.2 Creating connection-oriented network service

(CONS)
Procedure
1 Create an X.25 parameter set

X.25 parameter sets are handled with the QX command group. An X.25 parameter
set describes the data link and packet level parameters of an X.25 interface. The
X.25 data link and packet level parameters are presented in the section Parameters
of X.25.
An easy way to create a new parameter set is to create first a parameter set with the
default values and then make the necessary changes. Usually, only the range of the
X.25 logical channels of the packet level and the packet size need to be changed.
The range of logical channels must be equal for both the communicating X.25
entities, otherwise the call establishment may fail.
For example, if you would like to create an X.25 parameter set called 'X25PAK' with
16 logical channels starting from channel 11, first create the X25PAK set with the
default values, and then modify the range of logical channels with the correct values:
ZQXC:X25PAK;
ZQXM:X25PAK:L3LTC=11,L3HTC=26;
If you want to change the range of logical channels to 155-171 and add the new
permanent virtual circuits 1, 2, 3, and 4 later on, give the following command:
ZQXM:X25PAK:FPVC=1,HPVC=4,L3LTC=155,L3HTC=171;
For more information on the QXC and QXM commands, refer to the instructions on
X.25 interface configuration parameters handling.
2 Define the physical channel for the X.25 data terminal

A physical channel identifies an X.25 data terminal and hides the redundancy
method if the data terminal is located in a duplicated unit. Physical channels are
created with the QC command group.
It is possible to give the identification number for a physical channel manually in the
first parameter block. Otherwise, the OSI software allocates the next free channel
number (in this case 0).
Physical channels for the AS7-C data terminals are created in a similar way, except
that, in this case, the external PCM and TSL information is also needed. The OSI
software creates the circuit group for the external PCM and adds circuits to the circuit
groups automatically when the QCC command is issued. The circuit group name is
X25CGR and the corresponding number is 149 (in decimal).
If, for example, the external PCM number is 11 and the TSL has the value 5, and the
previously created AS7-C data terminal is going to be taken into use with these
parameters, give the following command:
ZQCC::OMU,5:,DTE,X25PAK:11-5;
The created physical channels need to be unlocked with the QSC command before
you can take them into use or group them with the QGC command.
DN9812567 Issue: 14-1 © 2016 Nokia 87

For more information on the QCS and QCC commands, refer to the instructions on
physical channel data handling.
6.3 Creating connectionless network service (CLNS)

Purpose
The following procedure is valid for creating both the ES and IS roles of the CLNS
network service. Just give the right values (ES or IS) in the parameters clns role and
linkage role in the QEC and QLL commands.
Procedure
1 Create a new CLNS object

Create a new CLNS object with the QEC command.
The parameters required for creating a CLNS object are the following:
• system ID
• manual area address
• MaximumAreaAddresses value
• network service user identification (NS-User)
With the NS-User parameter you can define the location of the O54LRS process,
that is, the network service user to a specific computer unit. With this option you can
try to limit the message traffic in the internal message bus.
For example, if there are linkages planned only to one computer unit, the NS user
can be located in the same unit, or if it is known that most of the traffic will be
generated by the FTAM file transfer, then the NS user can be placed in the same unit
as the FTAM application.
For example, to create a new CLNS object in the ES role with the following
definitions:
• MaximumPDULifetime value is 9
• system ID is 000000012345 according to the C-number 12345
• manual area address is 01020304050607080910111213
• MaximumAreaAddresses value is 3
• unit of the NS user is BDCU-0
give the following command:
ZQEC:ES1:ES:BDCU,0:9:000000012345:3:
01020304050607080910111213;
The state of the new object after the creation is LOC-NW-ENA.
88 © 2016 Nokia DN9812567 Issue: 14-1

2 Unlock the new object

Unlock the new object with the QEG command.
To unlock an already created object, use the following command.
ZQEG:ES1:UNL;
The state of the object becomes UNL-NW-ENA.
3 Initialise the connectionless network service

Initialise the connectionless network service with the QET command.
To initialise the connectionless network service with the previously created CLNS
object (changing the object state into UNL-NW-ACT), use the following command.
ZQET:ES1:Y;
The last parameter defines if the backup timer is in use (Yes/-) when the CLNS is
started. With the help of this timer you can use a time limit for accepting the new
CLNS configuration. If the time limit is exceeded, the DX 200 OSI software cancels
the CLNS initialisation and initialises the CLNS with the old configuration setting the
backup timer on again. The value for the time limit is set with the CLNS system
parameter BackupTimer. (See Parameters of CLNS.)
The backup timer should be set on when the CLNS configuration is updated remotely
using the OSI VT service: if something goes wrong during the configuration, the
adjacency to the new CLNS is not established and without the backup timer it is
impossible to connect to the network element any more.
4 Accept the connectionless network service

Accept the connectionless network service with the QEH command.
If the initialisation succeeds and the backup timer is on, you can accept the new
CLNS with the QEH command:
ZQEH;
The command cancels the backup timer and changes the CLNS object state into
UNL-BU-ACT.
For more information on the QEC, QEG, QET, and QEH commands, refer to the
instructions on OSI environment connectionless network service handling.
5 Define a new linkage object

Define a new linkage object with the QLL command.
The CLNS uses linkages as ports to the data network. Linkages are realised by the
Ethernet interface (broadcast linkages) and X.25 virtual circuits (SVC/PVC X.25
linkages). Linkages must be created and unlocked for each Ethernet interface and
X.25 virtual circuit used by the CLNS.
The parameters of linkages are stored in the OSI database as linkage objects. Each
object defines the properties of one linkage. There may be more than one linkage
defined for one Ethernet interface but only one may be used at a time.
DN9812567 Issue: 14-1 © 2016 Nokia 89

The linkage type is either ES linkage or IS linkage. The linkage type reflects the
system type, that is, only ES linkages can be unlocked in an ES system and only IS
linkages in an IS system.
Linkages are handled with the QL command group.
For example, to create broadcast linkage number 1 for COCEN in the BDCU-0
computer unit in plug-in unit 7, use the command:
ZQLL:1:ES:BDCU,0:7;
Another example in a PCI bus based DX 200: to create broadcast linkage number 3
for the Ethernet interface (usually the index of the Ethernet interface is 0) in the OMU
computer unit, use the command:
ZQLL:3:ES:OMU:0;
If you want to create an X.25 linkage, first you need to define the X.25 parameter set
and the physical channels for the virtual circuit (SVC or PVC) as described in section
Creating connection-oriented network service (CONS).
You also have to ensure that the calling address (SNPA) is always supplied. With
AS7–C you always have to configure the SNPA number when creating the physical
channel.
For example, to create X.25 linkage number 2 in the BDCU-0 computer unit in plug-
in unit 2 with the remote SNPA address 12345678, use the command:
ZQLC:2::BDCU,0:2:SNPA=12345678;
6 Unlock the linkage

Unlock the linkage with the QLG command.
To unlock an already created linkage object, use the following commands.
ZQLG:1::UNL;
ZQLG:2::UNL;
ZQLG:3::UNL;
The default values of the linkage object parameters should be used unless there is a
specific reason to change them. See Parameters of CLNS.
For more information on the QLL, QLC, and QLG commands, refer to the instructions
on OSI environment linkage handling.
6.4 Defining local OSI addresses

Purpose
Defining an OSI address starts with defining the NSAP address. A local NSAP address
identifies the user of the network service, which can be the following:
• PAD service provider

• transport protocol class 0
• transport protocol class 4
• other network service user
90 © 2016 Nokia DN9812567 Issue: 14-1

The type of the local NSAP address has to be chosen according to the subnetwork
interface and service type in question:
type 1 X.25 Network Protocol Address Information for identifying

the CONS user (DTE number + SPI)
type 2 TRIAL X.25 Network Protocol Address Information for

identifying the CONS user located at the TRIAL side during
software package update (DTE number + SPI)
type 3 X.25 Permanent Virtual Circuit for identifying the PVC user
(physical channel group identifier)
type 4 local N-selector for identifying the CLNS user
Procedure
1 Create the NSAP for local CONS user

Create the NSAP for a local CONS user with the QBN command.
The X.25 address information contains two fields, a DTE number and a Subsequent
Protocol Identifier (SPI). The DTE number is usually derived from the SNPA number
of the data terminal that provides the X.25 connection between the network service
users. Subsequent Protocol Identifier identifies a network service user among the
users with a common DTE number.
As for the SPI value, there are some well known, already reserved values as a de
facto standard (see the table Subsequent Protocol Identifiers of network layer in the
section Planning OSI services). These values cannot be used in other contexts.
For example, if you would like to create a local NSAP identifying a local PAD host
(NSAP type 1), let the external ID for the address receive the default value (NBR
field in the output). The SNPA number is 123456789. Give the command
ZQBN::L:1:DTE=123456789,SPI=01000000;
and you will receive the following output:
DX 200 DX200-LAB 1995-01-01 00:07:04
CREATED NSAP
----- ------ ------- -------- --------------- --------
38 LOCAL LOC-DIS - 123456789 01000000
COMMAND EXECUTED
As another example, you create a local NSAP identifying transport protocol class 0.
In this case, the SNPA number is again 123456789, but the SPI field is different. You
can create this NSAP address with the command
ZQBN::L:1:DTE=123456789,SPI=03010100;
and you will receive the following output:
DX 200 DX200-LAB 1995-01-01 00:07:30
CREATED NSAP
DN9812567 Issue: 14-1 © 2016 Nokia 91


----- ------ ------- -------- --------------- --------
39 LOCAL LOC-DIS - 123456789 03010100
COMMAND EXECUTED
For more information on the QBN command, refer to the instructions on OSI network
address and NSAP data handling.
2 Create an NSAP for local CONS user located at TRIAL side

During a software package update, there is usually a need to establish a PAD
session on the TRIAL side. By default all OSI connections are routed to the TELE
side if the user has not explicitly defined the NSAP to be used on the TRIAL side
(NSAP type 2).
Create an NSAP for a local CONS user located on the TRIAL side with the QBN
command.
In the previous example, the SNPA number was 123456789. The X.25 packet
network allows you to include extra numbers after the DTE number, so a
straightforward way to build a unique DTE number for the TRIAL side is to create a
TRIAL NSAP with the DTE number 1234567890.
You can create this TRIAL NSAP address with the command:
ZQBN::L:2:DTE=1234567890,SPI=01000000;
In this case, you receive the following output:
DX 200 DX200-LAB 1995-01-01 00:07:04
CREATED NSAP
TRIAL X.25 NETWORK PROTOCOL ADDRESS INFORMATION
----- ------ ------- -------- --------------- --------
40 LOCAL LOC-DIS - 123456789 01000000
COMMAND EXECUTED
3 Create an NSAP for Permanent Virtual Circuit

Permanent Virtual Circuits are X.25 connections that are initialised straight into the
data transfer state by the X.25 software when the X.25 packet level is restarted.
To keep the service interfaces of the PVC and SVC identical, the DX 200 OSI
software allows that the handshake between the PVC provider and the PVC user is
delayed until either the local PVC user wants to transfer data or the remote PVC
starts to transfer the data through the subnetwork.
The handshake requires that the local PVC user is mapped to the PVC provider in
some way. The OSI software uses channel groups for this mapping. The PVC NSAP
is a reference to a channel group, which contains the PVC number of a specific
physical channel.
92 © 2016 Nokia DN9812567 Issue: 14-1

In the following example we suppose that physical channel number 0 (configured in

the section Creating connection-oriented network service (CONS)) through the AS7-
C data terminal provides PVC number 1.
a) Create and define a channel group (if necessary) with the QSC and QGC
commands.
You can create a channel group named MYPVC containing physical channel
number 0 by first unlocking the physical channel with the command:
ZQSC:0,UNL;
and then you can define the channel group with the command:
ZQGC:MYPVC:0,1,70;
CREATED PHYSICAL CHANNEL GROUP DATA
VC CHAN CHAN
GROUP ID CHAN NUMBER PRIO STATE
-------- --------------------------
MYPVC 0 1 70 UNL-ENA
COMMAND EXECUTED
A virtual circuit number other than 0 means that a permanent virtual circuit is
used instead of a switched virtual circuit.
b) Define the channel group as a PVC NSAP with the QBN command.
To define this channel group as a PVC NSAP, simply give the command:
ZQBN::L:3:CHG=MYPVC;
CREATED NSAP
X.25 PERMANENT VIRTUAL CIRCUIT
NBR ROLE STATE CHG
----- ------ ------- --------
41 LOCAL LOC-DIS MYPVC
COMMAND EXECUTED
For more information on the QSC command, refer to the instructions on physical
channel state handling.
For more information on the QGC command, refer to the instructions on physical
channel group data handling.
For more information on the QBN command, refer to the instructions on OSI
network address and NSAP data handling.
4 Create an NSAP for local CLNS user

The NSAP address of a local CLNS user is built from the CLNS parameters: area
address and system ID. The only field to be specified is the N-selector field.
Because in the CLNS the NSAP address represents the whole network element, you
should define only one local NSAP for each N-selector.
Create a local CLNS NSAP address with the QBN command.
For example, you can create a local CLNS NSAP address with the command:
ZQBN::L:4:NSEL=FF;
DN9812567 Issue: 14-1 © 2016 Nokia 93


CREATED NSAP
LOCAL N-SELECTOR
NBR ROLE STATE SEL
----- ------ ------- ---
43 LOCAL LOC-DIS FF
COMMAND EXECUTED
5 Create an NSAP for local OSI over TCP/IP user

When OSI over TCP/IP feature is active, NSAP address is given as IP address
format. Only one local NSAP address is needed and it needs to match with OMU’s IP
address. That because OSI over TCP/IP connection goes via OMU’s LAN interface.
At first check OMU’s IP address by command:
ZQRI:OMU;
If OMUs IP address is e.g. 10.12.17.121 then create local NSAP by command:
ZQBN:1:L:6:IPV4=”10.12.17.121”;
BSC HOLSTI 2008-09-22 12:40:19
CREATED NSAP
IP BASED NSAP

----- ------ ------- -------------------------------- -----
1 LOCAL LOC-DIS 10.12.17.121 102
COMMAND EXECUTED
6.5 Defining local OSI applications

Purpose
Before you are able to define a local OSI application, you need to specify how it uses the
existing subnetwork interfaces in OSI connections (see the figure below).
The role of a network address depends on the location of the application to be attached.
Local network addresses are attached only to local applications, and remote network
addresses only to remote applications. The third network address type 'both' may be
attached to both local and remote applications. The type 'both' is used in NSAP
addresses defining X.25 PVC channels. Both outgoing and incoming application
associations are realised using this single network service access point.
94 © 2016 Nokia DN9812567 Issue: 14-1

Figure 19 Usage of local network address
Application Application Application
outgoingcall2
outgoingcall1
outgoingcall3
Network Network
Address Address
NSAP NSAP
CONS CLNS
In the following example commands, we suppose that the virtual file store for FTAM
transfer is going to use both CONS (X.25) and CLNS interfaces.
6.5.1 Creating local network addresses
Procedure
1 Create a local network address to connect a local application to the interfaces

Create a local network address with the QBC command to connect a local application
to the interfaces it is going to use.
For example, you can create a local network address, named FORVFS, to combine
the NSAP addresses of the required interfaces with the following command:
ZQBC:FORVFS:L;
DX 200 DX200-LAB 1995-01-03 23:08:58
CREATED NETWORK ADDRESS
NET ADDR ROLE
-------- ------
FORVFS LOCAL
COMMAND EXECUTED
DN9812567 Issue: 14-1 © 2016 Nokia 95

2 Lock the NSAP addresses

Lock the NSAP addresses to be attached to the network addresses with the QBC
command.
In the example commands above, the NSAP address #39 was created for the CONS
(X.25) interface and the NSAP address #43 for the CLNS interface.
An NSAP address must be in the administrative state 'locked' when it is attached to a
network address. After creation, an NSAP address is in the locked state. However, if
the NSAP addresses #39 and #43 have been taken into use and they are in the
unlocked state, you can lock them with the command:
ZQBG:39&43,LOC;
3 Attach the NSAP addresses of the interfaces to the previously created network
address
Attach the NSAP addresses of the interfaces to the previously created network
address with the QBT command.
You attach the NSAP addresses #39 and #43 to the local network address FORVFS
with the following commands (followed by the corresponding outputs):
ZQBT:FORVFS:39;
DX 200 DX200-LAB 1995-01-03 23:13:30
ATTACHED NSAP
NET ADDR ROLE NSAP NR PRIO
-------- ------ ------- ----
FORVFS LOCAL 39 -
COMMAND EXECUTED
and
ZQBT:FORVFS:43;
DX 200 DX200-LAB 1995-01-03 23:13:30
ATTACHED NSAP
-------- ------ ------- ----
FORVFS LOCAL 43 -
COMMAND EXECUTED
4 Unlock the new network address

Unlock the new network address with the QBG command.
Finally, you can unlock the NSAP addresses #39 and #43 with the command:
ZQBG:39&43,UNL;
DX 200 DX200-LAB 1995-01-03 23:13:40
CHANGING NSAP STATE
NBR OLD STATE NEW STATE
----- --------- ---------
96 © 2016 Nokia DN9812567 Issue: 14-1

39 LOC-DIS UNL-ENA
43 LOC-DIS UNL-ENA
COMMAND EXECUTED
For more information on the QBC, QBG, and QBT commands, refer to the instructions
on OSI network address and NSAP data handling.
6.5.2 Creating local OSI applications

Purpose
Applications located in a local node and using OSI services belong to a local open
system. These applications are called local OSI applications.
Procedure
1 Create the local application

Create the local application with the QDL command.
When creating local OSI applications, the following parameters are called for:
• name of the application (AE-name)
• location of the application
– unit type
– unit index
• family/device identification
– family/device type
– process/device index
• P-, S-, and T-selector values according to the type of the application
• name of the network address
The naming of the applications has no restrictions, except that they must be unique
within the system and contain 1 to 16 characters. However, the maintenance of the
address database is easier if each open system has an evident and unique name as
part of the AE-name. Because of limited name length, it is recommended to include
the C-number of the DX 200 network element in the AE-name if possible.
For example, if you are going to create a local virtual file store application, OMUVFS,
located in the OMU, with the network address FORVFS and having the selector
values 0x0201, give the command:
ZQDL:OMUVFS::::OMU:VFS:FORVFS:0201:0201:0201;
DX 200 DX200-LAB 1995-01-09 19:12:34
CREATED OSI APPLICATION
---------------- ------ -------- ------- ---------- ------- -------
OMUVFS VFS FORVFS LOC-ENA OMU
DN9812567 Issue: 14-1 © 2016 Nokia 97

AP_TYPE : NOT IN USE

AP_TITLE :
AEQ :
P-SELECTOR: 0201
S-SELECTOR: 0201
T-SELECTOR: 0201
COMMAND EXECUTED
2 Unlock the created applications

Unlock the created applications with the QDG command.
The state of the created application is by default LOCKED. Before the application
can make application associations it needs to be unlocked. In this example the
command is the following:
ZQDG:OMUVFS,UNL;
The resulting output is the following:
DX 200 DX200-LAB 1995-01-09 19:21:03
CHANGING OSI APPLICATION STATE:
AE-NAME OLD STATE NEW STATE
---------------- --------- ---------
OMUVFS LOC-ENA UNL-ENA
COMMAND EXECUTED
You can also create the OMUVFS application straight in the unlocked state with the
command:
ZQDL:OMUVFS:::UNL:OMU:VFS:FORVFS:0201:0201:0201;
For more information on the QDL and QDG commands, refer to the instructions on
OSI environment application data handling.
6.5.3 Defining selectors for applications

Purpose
Route selection of the incoming calls is based on the NSAP address and selector values.
There is no ISO standard for the selector values, like the Internet suite has for TCP port
numbers. However, there is an NTC de facto standard to construct selector values for
DX network elements. Each application type has a unique number, which is catenated to
the unit information of the unit in which the application is located. The following table
shows the values that have been allocated to the units so far.
Table 61 Selector values for NTC applications
Virtual File Store 1 OMU (2) 0201
98 © 2016 Nokia DN9812567 Issue: 14-1

Table 61 Selector values for NTC applications (Cont.)
Alarm downloader 2 OMU (2) 0202
CMIP agent 3 OMU (2) 0203
Performance manager 4 PFMU (1B) 1B04
Alarm mailbox 5 OMU (2) 0205
ISO Virtual Terminal 6 OMU (2) 0206
If, for some reason, the remote end is unable to conform to the allocated selector values,
it is possible to attach an additional selector set to the local application. For example, if
some remote FTAM implementation is unable to use selector values other than non-
space ASCII characters, you can create an additional selector set for OMUVFS.
Procedure
1 Change the administrative state of the local application to locked

Suppose that the remote end is willing to use the string 'FTAM' (4654414D in
hexadecimal) as the P-selector and the T- and S-selectors are empty. First change
the administrative state of the local application to locked with the following command:
ZQDG:OMUVFS,LOC;
2 Attach secondary selector group to OSI application

To attach the secondary selector group to an OSI application give the command:
ZQDT:OMUVFS:SPARE:4654414D::;
DX 200 DX200-LAB 1995-01-09 20:58:22
ATTACHED SELECTOR GROUP
AE-NAME
----------------
OMUVFS
GROUP TYPE: SPARE
P-SELECTOR: 4654414D
S-SELECTOR:
T-SELECTOR:
COMMAND EXECUTED
DN9812567 Issue: 14-1 © 2016 Nokia 99

Another usage of the additional selector set is when a connection to the TRIAL side
is needed during a software package update. The need may be, for example, to
retrieve charging and statistical information from the TRIAL side instead of the TELE
side. A connection to the TRIAL side can be established using a dedicated OSI
address.
If the local application is using CONS directly, this dedicated address is a TRIAL
NSAP address created in the step NSAP for the local CONS user located on the
TRIAL side in section Defining local OSI addresses.
If the local application is using upper layer services (session or presentation), you
can create this address with the QDT command.
Suppose that the Billing Center wants to retrieve charging information from the
TRIAL side. First decide the selector set value (it can be the string 'TRIAL', 'TRIAL',
'TRIAL') and then give the command:
ZQDT:OMUVFS:TRIAL:545249424C:545249424C:545249424C;
DX 200 DX200-LAB 1995-01-09 20:58:22
ATTACHED SELECTOR GROUP
AE-NAME
----------------
OMUVFS
GROUP TYPE: TRIAL
P-SELECTOR: 545249424C
S-SELECTOR: 545249424C
T-SELECTOR: 545249424C
COMMAND EXECUTED
For more information on the QDL, QDG, and QDT commands, refer to the instructions
on OSI environment application data handling.
100 © 2016 Nokia DN9812567 Issue: 14-1

OSI Guide Defining remote OSI environment
7 Defining remote OSI environment

Purpose
After the local OSI configuration, you are ready to configurate your remote OSI
environment. The following three steps briefly describe the configuration procedure.
1. Determine the NSAP addresses provided by the remote end either for the CLNS or
CONS as described in section Defining remote NSAP addresses.
2. Define the remote network addresses as described in section Defining remote
network addresses.
3. Define the remote applications as described in section Defining remote OSI
applications.
Section Using access control list deals with procedures concerning data security in a
public X.25 network.
Sections Example configuration of an ES with LAN interface, Example configuration of
an IS with LAN and X.25 interfaces, and Example configuration of an ES with LAN and
X.25 interfaces include detailed examples of the configuration procedures.
7.1 Defining remote NSAP addresses

Purpose
An NSAP address may be a logical address, like ISO DCC NSAP or Permanent Virtual
Circuit (PVC), or it may define the Network Protocol Address Information (NPAI) directly.
In the latter case, the NSAP address defines either an X.25 address or it is an
unstructured address used only in a CLNS environment.
A remote NSAP address is attached to a remote application with a network address. A
network address consists of a set of NSAP addresses. Each NSAP address attached to
a network address has a priority, which is significant only within this network address.
Thus, it is possible to prioritise the usage of different subnetwork types and routes
according to the application association type.
Procedure
1 Define remote NSAP addresses for CLNS

There are two types of structured remote NSAP addresses for the CLNS. A
structured NSAP address conforms with either the ISO DCC or ISO 6253-ICD NSAP
address type. The default values for the area address fields of structured NSAP
addresses are set with the QBH command.
Create the right type of the remote NSAP for CLNS with the QBH or QBN commands.
For example, you can define the default values of area addresses in a network of
NTC (refer to subsection OSI addressing scheme) with the command:
ZQBH
:AFI=39,IDI=246,DFI=00,ORG=000116,RES=00000001,AREA=0001;
The output of this command is as follows:
DN9812567 Issue: 14-1 © 2016 Nokia 101

Defining remote OSI environment OSI Guide
DX 200 DX200-LAB 1995-01-01 01:43:48

SET DEFAULT VALUES OF NSAP
ISO DCC/ISO 6253-ICD NSAP
AFI IDI DFI ORG RESERVED AREA
--- ---- --- ------ -------- ----
39 246F 00 000116 00000001 0001
COMMAND EXECUTED
The NSAP addresses of ISO DCC and ISO 6253-ICD contain fields for the end
system ID and the N-selector also. The values of these fields vary between end
systems according to the numbering plan of the target network.
For example, you can create a remote CLNS NSAP with the end system identifier
000000330970 and N-selector value FF with the command:
ZQBN::R:5:END=000000330970,NSEL=FF;
DX 200 DX200-LAB 1995-01-01 01:58:19
CREATED NSAP
ISO DCC/ISO 6253-ICD NSAP
NBR ROLE STATE AFI IDI DFI ORG RESERVED AREA END SYSTEM
SEL
----- ------ ------- --- ---- --- ------ -------- ---- ------------
---
15 REMOTE LOC-DIS 39 246F 00 000116 00000001 0001 000000330970
FF
COMMAND EXECUTED
If, for some reason, it is not possible to use either the ISO DCC or ISO 6253-ICD
NSAP format, the remote NSAP is to be configured as an unstructured NSAP.
For example, you can create a remote unstructured NSAP for CLNS describing a 3-
byte octet string '0x123456' as the network protocol address information with the
command:
ZQBN::R:0:UNS=123456;
DX 200 DX200-LAB 1995-01-01 02:20:54
CREATED NSAP
UNSPECIFIC NSAP
----- ------ ------- ----------------------------------------
22 REMOTE LOC-DIS 123456
COMMAND EXECUTED
For more information on the QBH and QBN commands, refer to the instructions on
OSI network address and NSAP data handling.
2 Define remote NSAP addresses for CONS (X.25)

The routing of CONS data requires manual routing information because there is no
routing protocol for selecting the interface providing the optimal route to the remote
end. In the DX 200 OSI software, this routing information is attached to each remote
102 © 2016 Nokia DN9812567 Issue: 14-1

X.25 NSAP with the help of the channel group. X.25 calls can be routed using this
dedicated group of prioritised data terminals, so it is possible to define virtual X.25
subnetworks.
Remote X.25 NSAP information is composed of the following three fields:
• The DTE number is the X.25 address of the remote X.25 interface. The value
may be absent.
• SPI defines the Subsequent Protocol Identifier. It is carried in the first four octets
in the Call User data field of the Call Request packet. The value may be absent.
• The channel group name identifies the channel group which defines how the data
terminal is selected when establishing the outgoing call.
a) Create a channel group (if necessary).

Suppose that you have created a channel group named X25NET with the QGC
command as described in section Defining local OSI addresses.
b) Define the channel group as an NSAP.
You can define this channel group as a a remote X.25 NSAP, with the DTE
number 244320010312 and SPI value 01000000 with the command:
ZQBN::R:1:DTE=244320010312,SPI=01000000,CHG=X25NET;
DX 200 DX200-LAB 1995-01-01 00:07:04
CREATED NSAP
----- ------ ------- -------- --------------- --------
23 REMOTE LOC-DIS X25NET 244320010312 01000000
COMMAND EXECUTED
For more information on the QBN command, refer to the instructions on OSI
network address and NSAP data handling.
3 Define remote NSAP addresses for OSI over TCP/IP

When OSI over TCP/IP feature is active, NSAP address is given as IP address
format and destination port as a decimal value. You can create as many remote
NSAP as there is end system.
If remote system’s IP address is e.g. 10.12.17.221 and default iso_tsap port (102) is
used then create remote NSAP by command:
ZQBN:10:R:6:IPV4="10.12.17.221",PORT=102;
BSC HOLSTI 2008-09-22 12:51:18
CREATED NSAP
IP BASED NSAP

----- ------ ------- -------------------------------- -----
DN9812567 Issue: 14-1 © 2016 Nokia 103

10 REMOTE LOC-DIS 10.12.17.221 102
COMMAND EXECUTED
7.2 Defining remote network addresses

Purpose
You create a remote network address with the following procedure.
Procedure
1 Create a network address

Create a network address with the QBC command.
You can create a network address in the OSI database with the QBC command.
Suppose that the name of the remote network address you want to create is
PADADDR. The command is as follows:
ZQBC:PADADDR:R;
DX 200 DX200-LAB 1995-01-01 01:23:55
CREATED NETWORK ADDRESS
NET ADDR ROLE
-------- ------
PADADDR REMOTE
COMMAND EXECUTED
2 Lock the NSAPs to be attached to the created network address

Lock the NSAPs to be attached to the created network address with the QBG
command.
An NSAP address must be in the administrative state 'locked' when it is attached to a
network address.
You can lock the NSAP address #23 with the following command.
ZQBG:23,LOC;
3 Attach the NSAPs to the network address

Attach the NSAPs to the network address with the QBT command.
You can attach the NSAP address #23 to the created network address PADADDR
with the command:
ZQBT:PADADDR:23,50;
104 © 2016 Nokia DN9812567 Issue: 14-1


DX 200 DX200-LAB 1995-01-01 01:29:05
ATTACHED NSAP
-------- ------ ------- ----
PADADDR REMOTE 23 50
COMMAND EXECUTED
Define also an alternative NSAP for the remote application in this stage if needed.
4 Unlock the NSAPs

Unlock the NSAPs with the QBG command.
You can unlock the NSAP address #23 with the command:
ZQBG:23,UNL;
DX 200 DX200-LAB 1995-01-01 01:32:42
CHANGING NSAP STATE
NBR OLD STATE NEW STATE
----- --------- ---------
23 LOC UNL
COMMAND EXECUTED
For more information on the QBC, QBG, and QBT commands, refer to the instructions
on OSI network address and NSAP data handling.
7.3 Defining remote OSI applications

Purpose
Applications belonging to other open systems are remote OSI applications. Creating a
remote application is necessary only if it has a responder role in application associations
or if it has an initiator role in Q3 management connections.
Procedure
1 Create remote OSI applications

Remote OSI applications are created with the QDR command. The following
parameters are called for when creating a local OSI application:
• name of the application (AE-name)
• type of the application
• name of the network address
Remote applications are named according to the same rules as local applications.
The C-number of the remote network element is recommended to be included in the
AE-name. The application type information is necessary in the connection
DN9812567 Issue: 14-1 © 2016 Nokia 105

establishment phase because the DX 200 OSI software allows application

associations only between applications of the same type. The network address
information is mandatory because the subnetwork interface and the network protocol
address are selected according to the network address.
The possible additional parameters to be attached to the remote application
information are the following:
• application process title value (APT)
• application entity qualifier value (AEQ)
• selector values of the application
Optional fields are used depending on the requirements of the remote end. The
application entity title value AET (APT and AEQ) is defined when additional binding
information is needed besides the PSAP address. So far only AET form number 2 is
supported, which means that the AET is defined as an object identifier. Usually, the
PSAP address is adequate for the identification of the remote application.
Expected outcome
Example:Creating a remote PAD application
For example, suppose that you are going to create a remote PAD application called
BSC050164PAD using the network address PADADDR. You can create this application
in the unlocked state with the command:
ZQDR:BSC050164PAD:::UNL:PAD:PADADDR;
DX 200 DX200-LAB 1995-01-02 15:31:33
---------------- ------ -------- -------
BSC050164PAD PAD PADADDR UNL-ENA
AP_TYPE : NOT IN USE
AP_TITLE :
AEQ :
P-SELECTOR:
S-SELECTOR:
T-SELECTOR:
COMMAND EXECUTED
Example:Creating a remote VFS application

Another, more complicated, example could be the creation of a remote VFS application,
named BSCXXXXVFS. Let us assume that you have created a network address named
LAN, which is going to be used by this remote application. The string of selector values
for this application is 'FTAM', 'FTAM', 'FTAM' and the APT has the value 1.3.9999.1.7.
In this case, you can create the remote application with the command:
ZQDR
:BSCXXXXVFS:2,1,3,9999,1,7,::UNL:VFS:LAN:4654414D:4654414D:465
4414D;
106 © 2016 Nokia DN9812567 Issue: 14-1


DX 200 DX200-LAB 1995-01-02 19:45:22
---------------- ------ -------- -------
BSCXXXXVFS VFS LAN UNL-ENA
AP_TYPE : FORM2
AP_TITLE : 0000000001.0000000003.0000009999.0000000001.
0000000007
AEQ :
P-SELECTOR: 4654414D
S-SELECTOR: 4654414D
T-SELECTOR: 4654414D
COMMAND EXECUTED
For more information on the QDR command, refer to the instructions on OSI environment
application data handling.
7.4 Using access control list

Purpose
For example, suppose that there is a need to establish PAD connections over the public
packet network from a remote system with the DTE number 244320010599. No other
remote system is allowed to establish X.25 connections.
Procedure
1 Add number to the access control list

In this case, first add this number to the access control list with the command:
ZQQC:244320010599;
DX 200 DX200-LAB 1995-01-01 00:30:20
CREATING ACCESS CONTROL DATA
CREATED ACCESS CONTROL DATA
NBR SNPA-ADDRESS ACCESS LIST INFO

----- ---------------- --------------------------
1 244320010599 ALL INCOMING CALLS DENIED
COMMAND EXECUTED
2 Take the access list into use

After this take the access list into use with the following command:
ZQQM:L;
DN9812567 Issue: 14-1 © 2016 Nokia 107


DX 200 DX200-LAB 1995-01-01 00:34:25
MODIFYING OSI ACCESS CONTROL METHOD
OLD METHOD NEW METHOD
-------------------------- --------------------------
ALL INCOMING CALLS DENIED ACCESS CONTROL LIST IN USE
COMMAND EXECUTED
3 Interrogate the current status of the access control policy

You can always interrogate the current status of the access control policy with the
command:
ZQQI;
DX 200 DX200-LAB 1995-01-01 00:34:49
INTERROGATING ACCESS CONTROL DATA
DATA OF OSI ACCESS CONTROL DATA
NBR SNPA-ADDRESS ACCESS LIST INFO
----- ---------------- --------------------------
1 244320010599 ACCESS CONTROL LIST IN USE
COMMAND EXECUTED
For further details on the QQM ,QQC, and QQI commands, refer to the information on
OSI access control.
7.5 Creating FTAM user profile

Purpose
Remote FTAM users must have a valid network user ID and a password before FTAM
operations are permitted.
The following procedure shows how the FTAM security function is taken into use.
Procedure
1 Use the default profile to create an FTAM user profile

Note that the FTAM user profile must be given the minimum user access rights.
ZIAA:<user_profile>:ALL=1;
For more information on the IAA command, refer to the instructions on MMI system
authority handling.
108 © 2016 Nokia DN9812567 Issue: 14-1

2 Create the FTAM user ID

The command asks for the user password during the execution of the command.
ZIAH:<user_id>,<user_profile>;
For more information on the IAH command, refer to the instructions on MMI system
authority handling.
3 Create the FTAM network user

ZIOA:<user_id>:APPL=FS-X;
For more information on the IOA command, refer to the instructions on network user
authority data handling.
DN9812567 Issue: 14-1 © 2016 Nokia 109

Verifying your OSI configuration OSI Guide
8 Verifying your OSI configuration

Purpose
The OSI configuration of a local node should be checked when configuration is
completed and before the OSI interface is taken into actual use. This chapter describes
the basic connectivity tests, that is, checking the basic operations of the interface and
connectivity to remote nodes.
Examples of configuration inquiries are presented in sections Example configuration of
an ES with LAN interface, Example configuration of an IS with LAN and X.25 interfaces,
Example configuration of an ES with LAN and X.25 interfaces, and Example
configuration of OSI over TCP/IP interface.
If some function does not work, refer to OSI troubleshooting in order to find out te
possible reasons for the malfunction and the instructions for corrective actions.
8.1 Verifying OSI network service

Procedure
1 Check if all the X.25 channels to be used are in the WO-EX state
Check if all the X.25 channels to be used are in the WO-EX state by giving the
command:
ZQSI;
LOADING PROGRAM VERSION 1.8-0
CHANNEL TERM
------- ---------- ---- ------- ----- ----
4 OMU-0 3 UNL-ACT WO-EX CHAN USES ANALOG TERM
6 OMU-0 4 UNL-ENA WO-BL CHAN USES ANALOG TERM
7 OMU-1 4 UNL-DIS SE-OU CHAN USES ANALOG TERM
11 OMU-1 6 UNL-DIS SE-OU CHAN USES ANALOG TERM
COMMAND EXECUTED
In the example output above, the X.25 channels 2, 4, and 13 are ready to be used by
the OSI connections.
2 Check if all Ethernet interfaces to be used are in the UNL-ENA state

Check if all the Ethernet interfaces to be used are in the UNL-ENA state. The X.25
and Ethernet interfaces are mapped to linkages which are used by the CLNS. You
can display the CLNS linkages with the command:
ZQLI;
110 © 2016 Nokia DN9812567 Issue: 14-1

OSI Guide Verifying your OSI configuration

NODE IN ES ROLE
LINKAGE TYPE ROLE UNIT LOG UNIT TERM SNPA ADDRESS PVC PRIO
STATE
------- ---- ---- ------- -------- ---- ---------------- ---- ---- --
-----
0 X.25 IS OMU-0 4121H 2 - 1 -
LOC-DIS
1 X.25 IS OMU-0 4121H 2 12345678 - -
LOC-DIS
2 X.25 IS OMU-1 4122H 7 12345678 - -
LOC-DIS
3 X.25 IS OMU-0 4121H 2 123456 - -
LOC-DIS
4 BRO ES OMU-0 4121H 5 - - -
LOC-DIS
5 BRO IS OMU 4002H 5 - - 60
UNL-ENA
6 BRO ES OMU-0 4121H 5 - - -
LOC-DIS
7 BRO ES OMU-1 4122H 5 - - -
LOC-DIS
11 X.25 IS OMU-1 4122H 7 1234567 - -
LOC-DIS
12 X.25 IS OMU-1 4122H 7 - 1 -
LOC-DIS
COMMAND EXECUTED
In this example, linkage 5 is ready to be used by the CLNS.
3 Interrogate the adjacent nodes reachable through a specified linkage

You can interrogate the adjacent nodes reachable through a specified linkage or
linkage information of an adjacent node with the QLP command.
For example, you can interrogate the adjacency information of linkage 5 with the
command:
ZQLP:5;
DX 200 TEST-LAB 1995-03-15 10:58:50
INQUIRING X.25 LINKAGE
NODE IN IS ROLE
LINKAGE TYPE ROLE UNIT LOG UNIT TERM SNPA ADDRESS PVC PRIO
STATE
------- ---- ---- ------- -------- ---- ---------------- ---- ---- --
-----
5 BRO IS OMU 4002H 5 - - 60
UNL-ENA
ADJACENCY DATA
SYSTEM ID SET SNPA ADDRESS STATE USAGE TIME PRIORITY TYPE INFO
DN9812567 Issue: 14-1 © 2016 Nokia 111

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

--
111111111111 00FF83400081 UP - - - ES AUTO
222222222222
AREA ADDRESSES : -
SYSTEM ID SET SNPA ADDRESS STATE USAGE TIME PRIORITY TYPE

INFO
---------------- ---------------- ----- ----- ---- -------- ----- ---
---
222222222222 00FF83444444 DOWN L1 600 DEFAULT L1-IS
AUTO
AREA ADDRESSES : 11223344556677889900112233

11111111111111111111111111
22222222222222222222222222
SYSTEM ID SET SNPA ADDRESS STATE USAGE TIME PRIORITY TYPE

INFO
---------------- ---------------- ----- ----- ---- -------- ----- ---
---
333333333333 00FF83444455 UP L1 600 DEFAULT L1-IS
AUTO
AREA ADDRESSES : 11223344556677889900112233
COMMAND EXECUTED
If you do not give the linkage ID as a parameter, the command displays all linkages
and the corresponding adjacent nodes.
8.2 Verifying FTAM service

Purpose
In most cases FTAM is used so that the DX functions as an FTAM responder and the
peer entity (Billing Center, and so on) acts as an FTAM initiator which reads files from
and writes files to the DX. In these cases the testing utilities of the peer hosts should be
used.
This section presents a set of FTAM tests and the corresponding MML commands by
which the basic operations of the FTAM initiator can be tested. These test cases can be
used also in the peer host if the supplier of the peer host has not provided any FTAM test
cases.
Before testing, the OSI configuration should be completed in both entities. Also the
paths, the filenames, and the owner identifiers to be used in the tests should be planned
beforehand.
112 © 2016 Nokia DN9812567 Issue: 14-1

The following test cases are based on EurOSInet FTAM Test Suite. With them you can
verify the transfer of binary files to/from the DX 200. EuroOSInet defines other test cases
also, but the following should be sufficient for the basic interoperability testing of the
FTAM.
In this example:
• the name of the peer host in the DX is PEERHOST

• the name of the DX in PEERHOST is DXHOST
• if the initiator of the test is in DXHOST, it has an account (username and password)
in PEERHOST (my_username and my_passw)
• there are three files in my_username's home directory in the peer host
– smallfile.tst (less than 10 Kbytes)
– bigfile.tst (more than 100 Kbytes)
– f1234567.tst (the name is eight characters long and it contains numbers)
Before you start

The tests should be made in the following order because some of the files used in the
test cases are created in earlier test cases.
A passed test generates the normal output of command execution.
A failed test generates an error printout. More information on error printouts is provided
in DX 200 and standard FTAM error codes.
For further details on the QFA, QFM, and QFD commands, refer to the information on OSI
file services.
Procedure
1 Read a small FTAM-3 (binary) file (FTAM3-R-1)

ZQFA
:PEERHOST,"smallfile.tst",LOCALVFS,"LFILES/SMALLINDX.TST",
"my_passw":UID="my_username";
2 Read a large FTAM-3 file (FTAM3-R-2)

ZQFA:PEERHOST,"bigfile.tst",LOCALVFS,"LFILES/BIGINDX.TST",
3 Read a file whose name is eight characters long (FTAM3-R-3)

Read a file whose name is eight characters long and contains numeric values.
ZQFA
:PEERHOST,"f1234567.tst",LOCALVFS,"LFILES/F1234567.TST",
DN9812567 Issue: 14-1 © 2016 Nokia 113

4 Attempt to read a file that does not exist (FTAM3-R-4)

ZQFA
:PEERHOST,"doesnot_exist.tst",LOCALVFS,"LFILES/TEST3R4.TST"
,"my_passw":UID="my_username";
5 Check error handling (FTAM3-R-5)

Check error handling for invalid filename format.
ZQFA
:PEERHOST,"invalid_form.tst",LOCALVFS,"LFILES/FTAM3R5.TST",
6 Check close-down and handling of a lost connection (FTAM3-R-6)

ZQFA:PEERHOST,"bigfile.tst",LOCALVFS,"LFILES/BIGINDX.TST",
Close down the physical media by, for example, disconnecting the cable to the
preprocessor terminal until an error text appears as a result of disconnection during
the reading.
7 Prevent reading files (FTAM3-W-0)

In PEERHOST, permitted action prevents reading files.
ZQFM:LOCALVFS,"LFILES/F1234567.TST",BIN:REA=NO;
Try to read the file from DXHOST:
ZQFA:PEERHOST,"LFILES/F1234567.TST",LOCALVFS,"ftam3r7.tst",
8 Replace an FTAM-3 file (FTAM3-W-1)

ZQFA:LOCALVFS,"LFILES/BIGINDX.TST",PEERHOST,"ftam3w1.tst",
9 Replace a large FTAM-3 file with a small FTAM-3 file (FTAM3-W-3)

ZQFA
:LOCALVFS,"LFILES/SMALLINDX.TST",PEERHOST,"ftam3w3.tst",
10 Delete local files (FTAM-D-1)

ZQFD:LOCALFTAM,"LFILES/SMALLINDX.TST";
ZQFD:LOCALFTAM,"LFILES/BIGINDX.TST";
ZQFD:LOCALFTAM,"LFILES/F1234567.TST";
114 © 2016 Nokia DN9812567 Issue: 14-1

11 Delete remote files

ZQFD
:PEERHOST,"ftam3w1.tst":UID="my_username",PASS="my_passw";
ZQFD
:PEERHOST,"ftam3w3.tst":UID="my_username",PASS="my_passw";
8.3 Converting the OSI configuration information

Purpose
This procedure describes how to convert and move the old OSI configuration data from
semi-permanent files to the DX database system. This should be done when the
software packet in the DX is updated to the version that supports the new OSI
configuration. The need of conversion is mentioned in the software update instructions.
g Note: When using the conversion, you should have experience and knowledge about
the DX 200 OSI configuration because in some cases the conversion does not
necessarily convert all files correctly.
8.3.1 Preparing the conversion of the OSI configuration

information
Purpose
These steps should be carried out before the new packet is activated.
Procedure
1 Check if all file references between files OADFIL, OAPFIL, OOAFIL, OAEFIL,
OCGFIL, and OPCFIL are in correct order
Use the following commands
ZQAI;
ZQPI;
ZQOI;
ZQGI;
ZQCI;
ZQSI;
2 Check if the 'FILE CONFLICT ERROR' alarm occurs

Check if alarm 2065 'FILE CONFLICT ERROR' occurs.
DN9812567 Issue: 14-1 © 2016 Nokia 115

Use the following command

ZAHO::NR=2065;
If it does not occur, everything is alright. If it does, the file references should be fixed.
3 Copy the old OSI configuration files to WDU

Use the following service MML commands:
ZDEY:S:I:OMU/<old packet directory>/LFILES:WDU-S:;
ZDEY:D:I:OMU/<new packet directory>/LFILES:WDU-SB:;
ZDEM:OPCFILGX;
ZDEM:OADFILGX;
ZDEM:OAPFILGX;
ZDEM:OAEFILGX;
ZDEM:OCGFILGX;
ZDEM:OOAFILGX;
ZDEM:OOIFILGX;
ZDEM:OIPARAGX;
ZDEM:OALFILGX;
ZDEM:OPHX25GX;
4 Convert the ATFILE and OETFIL files
g Note: The ATFILE and OETFIL files have to be converted if you are updating a
software packet which is based on platform software packet older than B4 2.1-0.
Use the following MML commands to convert the files:

ZDEE:ATFCNVGX.IMG;
ZDEE:OETCNVGX.IMG;
5 Activate the new packet

After these steps, you can activate the new packet.
8.3.2 Converting the OSI configuration information

Purpose
The steps should be carried out after activating the new packet.
116 © 2016 Nokia DN9812567 Issue: 14-1

Procedure
1 Check the central memory and the address of the message bus
The conversion program should be executed in the logical central memory (CM).
Check the unit where the CM is and the message bus address (MB) of the active CM
(in state WO-EX) with the command:
ZUSI;
See example 1 below.
2 Load the conversion program into OMU

Use the following service terminal commands:
ZDDS;
ZLP:M,MAS;
ZMR:W0-BLCODE/OMGCONGX.IMG,G40;
3 Move the program to the active side of CM

Use the following service terminal command:
ZRM:G40,20000>G40,<MB number of active CM>
4 Check the checksum

Use the following service terminal command:
ZSSA:G40;
If the checksum is correct, you receive the following output:
OMGCONGX.PAC 2.2-0 96/10/09 PLAENVB3.PAC 2.2-0
CHECKSUM IN MODULE: A163C912 CALCULATED: A163C912
If the checksum is incorrect, you receive a `checksum failed' message. In this case
you should contact Nokia Customer Service.
5 Exit the service extension program

Use the ZE service terminal command.
6 Start the service extension program again

Start the service extension program again in the active CM or in the unit where the
active CM is located.
Use the following command:
ZDDS:<unit where active CM is>,<number of the active CM>;
DN9812567 Issue: 14-1 © 2016 Nokia 117

7 Make service extension link

Use the following service terminal commands:
ZL:1;
ZLPM:1,G40;
8 Start the conversion program
a) Give the following command:

1
b) Start the conversion with the H command.
You get a general overview of the program which tells you the steps of the
conversion. See the output below:
This service terminal extension converts OSI management
information from
several management files to the management database (OEDATA).
1. With I command you ensure that conversion is possible. The
first
part of the command checks that all remote applications
have a valid
application type. If the local configuration is using LAN
interface,
the latter part shows the new CLNS parameters and, when
needed,
notifies from the possible incompatibilities.
2. After that you can execute the conversion with C command.
Error count
should be zero.
3. The trace of the conversion is collected and it can be

displayed
with P command.
c) Start the conversion analysis with the I command.
Supply the AE names of the remote applications which the conversion program
could not find if there is any.
The output of this phase is the following:
You get list of applications which types were not known based on
the
name of the application. You must fill the types with right
values.
Valid application types:
VPP : Virtual PAD Printer
VFS : Virtual File Store
MSW : MSW connection
SMS : Short Message Service
VTP : Virtual Terminal Protocol
CMI : CMISE Application
PAD : PAD Terminal
118 © 2016 Nokia DN9812567 Issue: 14-1

TSU : Transport Service User

OTH : Other Application Type
PRESS RETURN TO CONTINUE
9 Press Ctrl-x
In this case, you receive different outputs where the conversion program defines the
changes that will be done. Example output 1:
Connectionless service conversion
The new CLNS is going to be created using following information.
No incompatibilities were found.
CLNS NAME ROLE PRIM UNIT ACT UNIT LIFETIME ID
--------- ---- --------- --------- -------- ----------------
DEF_ES_C ES OMU OMU 7 123451234512
PARAMETER NAME VALUE
-------------------------------- -----------
ENABLE CHECKSUM FALSE
BACKUP TIMER 600 SEC
Example output 2:
Connectionless service conversion
The new CLNS is going to be created using following information.
Conversion program found other local OSI CLNS NSAP addresses which
are no more reachable through other network elements in this new
software version. We suggest that you give a new NSAP address for
this DX network element and update the address database of the
other systems, too.
CLNS NAME ROLE PRIM UNIT ACT UNIT LIFETIME ID
--------- ---- --------- --------- -------- ----------------
DEF_ES_C ES OMU OMU 7 123451234512
PARAMETER NAME VALUE
-------------------------------- -----------
ENABLE CHECKSUM FALSE
BACKUP TIMER 600 SEC
10 Give command C
You can start the conversion giving the C command. When the conversion is done,
the data is stored in the database.
After the conversion, you receive a short output, like the following:
EXECUTING CONVERSION
Applications : created 27, modified 0
Application profiles : created 3, modified 0
Application selectors : created 1, modified 0
Network addresses : created 21
DN9812567 Issue: 14-1 © 2016 Nokia 119

NSAPs : created 22
Linkages : created 2, modified 0
CLNSs : created 1, modified 0
Errors : 0
11 Check the log

If there were errors detected during the conversion, you can get a more detailed
conversion log with the P command. With the log it is possible to trace the detected
errors and the actual error code of the defect.
If the problems cannot be solved, submit the trace and the contents of the OADFIL,
OAPFIL, OOAFIL, OAEFIL, OCGFIL, and OPCFIL files to Nokia Customer Service.
See an example output below:
Local application OMC012345D1 was created:
profile was attached,
no additional selector set was attached,
network address name TRANSP00 with role LOCAL was created,
NSAP #2 was created.
Local application OMC012345BP was created:
network address name TRANSP00 with role LOCAL was shared,
NSAP #2 was shared.
Local application BSC054321A was created:
network address name TRANSP01 with role LOCAL was created,
NSAP #3 was created.
Local application BSC054321EHA was created:

no profile was attached,
network address name TRANSP01 with role LOCAL was shared,
NSAP #3 was shared.
12 Exit the service terminal

Use the ZE service terminal command.
13 Check if there are physical channels

Check if there are physical channels which are using ethernet terminals.
Use the following command:
ZQSI;
You can remove these channels.
120 © 2016 Nokia DN9812567 Issue: 14-1

14 Finish the conversion

If there are no error messages, the conversion is finished.
Further information
Example:Starting the conversion program when the active CM is in unit CAC-0
REMOTE DEBUGGER SESSION COMMANDS <DD_>
< ZUSI;
EXECUTION STARTED
DX 2100 DX200-LAB 1995-05-22 17:21:01
WORKING STATE OF UNITS

UNIT MB STATE LOCATION INFO
OMU 00 WO-EX -
CAC-0 04 WO-EX -
CAC-1 05 SP-EX -
CLS-0 WO-EX FLTY
MB-0 WO-EX -
MB-1 SE-NH -
TOTAL OF 6 UNITS
FAULTY UNIT 1
INCORRECT STATES 2
COMMAND EXECUTED
< ZDDS:OMU;
00-MAN> ZMR:W0-CONVPR/OMGCONGX.IMG,G40
00-REM> ZRM:G40,20000>G40,4
00-REM> ZE
< ZDDS:CAC,0;
05-MAN> ZL:1
05-MAN> ZLPM:1,G40
05-MAN> 1
Example of starting the conversion program when the active CM is in unit CAC-0
8.3.3 Converting the OSI parameter file

Purpose
The steps should be carried out after activating the new packet.
DN9812567 Issue: 14-1 © 2016 Nokia 121

Procedure
1 Set source path of parameter file os7par

ZIWY:S:UNIT=OMU,PATH=/<old packet directory>/LFILES,DRIVE=WDU-S;
2 Set destination path of parameter file os7par

ZIWY:D:UNIT=OMU,PATH=/<new packet directory>/LFILES,DRIVE=WDU-S;
3 Copy old parameter file to WDU

ZDEY:S:I:OMU/(old packet directory)/LFILES:WDU-S:;
4 Copy new parameter file to WDU

ZDEY:D:I:OMU/(new packet directory)/LFILES:WDU-SB:;
5 Finish the conversion

ZDEE:WS,NODEF:(conversion packet),CONVPR:OS7CNVGX;
122 © 2016 Nokia DN9812567 Issue: 14-1

OSI Guide OSI troubleshooting
9 OSI troubleshooting
Purpose
The following are the basic troubleshooting steps:
1. Check the alarms that are currently on and interpret the initial error.
Section Sources of information on OSI errors and alarms gives reference information
according to the source of the error message.
2. Determine the status of the DX 200 hardware and OSI software. Make sure that all
the components are in their normal working state. Refer to section Checking the
status of the links, the OSI stack, and the services.
3. Verify the operation of the components. If all the components report that they are up
and there are no problems, run the verification tests described in section Verifying
your OSI configuration.
4. Gather more information. If the information from the verification tests was insufficient
to diagnose the problem, get additional information through DX 200 OSI software
tracing facilities. See sections Using O23MTS service terminal extension.
5. Validate the configuration. See section Common OSI configuration mistakes.
g Note: For more information about the MMLs used below, refer to the corresponding
MML command descriptions.
9.1 Checking the status of the links, the OSI stack, and
the services
Purpose
There are several tools that enable you to check the status of the links, the OSI stack,
and the services. Perform the following steps to verify that your local system is up and
running.
Procedure
1 List the computer unit state information

List the computer unit state information with the USI command.
The DX 200 OSI software requires that the working state of the unit where the data
terminals are located is neither separated nor blocked.
If the state of the unit is separated, go through the alarm history to solve the reason
for this state transition and try to correct it.
2 Interrogate the states of the X.25 data terminals

Interrogate the states of the X.25 data terminals with the QSI command.
DN9812567 Issue: 14-1 © 2016 Nokia 123

OSI troubleshooting OSI Guide
The QSI command displays the administrative and functional states of the X.25 data
terminals (table below). The preferred states are indicated with bold typeface. In
other states the X.25 connection establishment is not possible.
Table 62 Possible states of X.25 data terminals
Channel state Term state Description
LOC-ENA RESET LOCKED by the user
UNL-ENA RESET UNLOCKED and ENABLED: initialisation of the data

terminal is not completed
UNL-ENA WP-BL UNLOCKED and ENABLED: initialisation of the data

terminal is completed, but the X.25 Packet level has
not yet restarted
UNL-ENA WO-EX UNLOCKED and ENABLED: data terminal is ready

for X.25 connection establishment
UNL-ACT WO-EX UNLOCKED and ACTIVE: there are established X.25

connections and there are still free X.25 virtual
circuits to be taken into use
UNL-BSY WO-EX UNLOCKED and BUSY: all X.25 virtual circuits are
taken into use. Data terminal cannot provide any
more X.25 connections
SHD-ACT WO-EX SHUTTING DOWN and ACTIVE: the user has

initialised the shutting down of the data terminal.
SHD-BSY WO-EX SHUTTING DOWN and BUSY: the user has

initialised the shutting down of the data terminal
UNL-DIS SE-OU UNLOCKED and DISABLED: DX 200 OSI software

has found the X.25 interface faulty
UNL-DIS SE-NH UNLOCKED and DISABLED: DX 200 OSI software

cannot locate a data terminal for this Physical
Channel
3 Check the states of the channel groups

Check the states of the channel groups with the QGI command.
The QGI command displays the functional states of the channel groups. Group state
AV (available) means that there is at least one physical channel in the channel group
that can provide an X.25 connection. State UA (unavailable) means that the direction
represented by the channel group is unreachable.
124 © 2016 Nokia DN9812567 Issue: 14-1

4 Check the states of the NSAP addresses

Check the states of the NSAP addresses with the QBL command.
The QBL command displays the administrative and functional states of the NSAP
addresses (table below). The preferred state is indicated with bold typeface. In other
states the NSAP address cannot be used in connection establishment.
Table 63 Possible states of NSAP addresses
NSAP address Description

state
LOC-DIS LOCKED by the user
UNL-ENA UNLOCKED and ENABLED: NSAP is available and it can be

used in connection establishment
UNL-DIS UNLOCKED and DISABLED: DX 200 OSI software has found

that the remote end represented by this NSAP address is
unreachable. A network connection with this NSAP is not
possible
5 Check the states of the OSI applications

Check the states of the OSI applications with the QDI command.
The QDI command displays the administrative and functional states of the OSI
applications (table below). The preferred state is indicated with bold typeface. In
other states the application association is not possible.
Table 64 Possible states of OSI addresses
Application state Description
LOC-ENA LOCKED by the user. Network address of the application contains

available NSAP addresses
LOC-DIS LOCKED by the user. All NSAP addresses belonging to the network
address of the application are either locked or disabled
UNL-ENA UNLOCKED and ENABLED: application is ready for establishing

application associations
UNL-DIS UNLOCKED and DISABLED: all NSAP addresses belonging to the

network address of the application are either locked or disabled.
Application association is not possible
6 Check the states of the linkages

Check the states of the linkages with the QLI command.
DN9812567 Issue: 14-1 © 2016 Nokia 125

The QLI command displays the administrative and functional states of linkages (see
the table below). The preferred state is indicated with bold typeface. In other states
the use of linkage to transfer CLNS data is not possible.
Table 65 Possible states of linkages
Linkage state Description
LOC-DIS LOCKED by the user
UNL-ENA UNLOCKED and ENABLED: linkage is able to transfer CLNS data
UNL-DIS UNLOCKED and DISABLED: DX 200 OSI software has found that
linkage cannot provide CLNS data transfer
7 Check the states of the CLNS objects

Check the states of the CLNS objects with the QEI command.
The QEI command displays the administrative and functional states of CLNS objects
(see the table below).
Table 66 Possible states of CLNS objects
Administrative Activity Functional Description

state state state
UNL BU ACT CLNS has been activated with this parameter set.
The set is unlocked and configured to be the
default set by the user.
UNL NEW ACT CLNS has been activated with this parameter set.
The set is unlocked and configured to be a trial
set by the user. After the user has resetted the
backup timer, the state is changed to UNL-BU-
ACT by the system.
LOC NEW ACT CLNS has been activated with this parameter set.
The trial configuration was considered faulty after
the backup timer expired, but because there were
no alternative sets to be taken into use, the CLNS
was not restarted.
UNL BU ENA This set is ready to be used in CLNS initialisation.

The restart of CLNS is done without the setting of
the backup timer.
UNL NEW ENA This set is ready to be used in CLNS initialisation

at the next CLNS restart. The restart of the CLNS
is done with the setting of the backup timer.
126 © 2016 Nokia DN9812567 Issue: 14-1

Table 66 Possible states of CLNS objects (Cont.)
Administrative Activity Functional Description

state state state
LOC NEW ENA CLNS has been activated with this parameter set.
The set is unlocked and configured to be the
default set by the user. After initialisation the
CLNS has informed the system that it is faulty.
One possible reason is that the CLNS is in the
wrong role.
UNL BU DIS The user has prevented the use of this parameter
set for CLNS initialisation.
UNL NEW DIS CLNS was previously activated with this trial
parameter set and it may be still in use. The trial
configuration failed and the state of this set was
changed to LOC-NEW-DIS by the system. After
this the user has changed the administrative state
to unlocked. One possible reason is that the
CLNS is in the wrong role.
LOC NEW DIS CLNS was previously activated with this trial
parameter set. The trial configuration failed and
the state of this set was changed to LOC-NEW-
DIS by the system. One possible reason is that
the CLNS is in the wrong role.
8 List the alarms that are currently on

List the alarms that are currently on with the AHO command.
The notifications related to the DX 200 OSI software are presented in the following
three tables. The first table contains notices which help you to operate the DX 200
OSI software. The disturbances, presented in the second table, are to be taken more
seriously, and alarms presented in third table usually require further actions. If any of
these alarms is set on, try to figure out the reason and act according to the alarm
instructions.
9 List the log files of computer units

List the log files of the computer units with the ZGD service terminal extension
program.
Pay attention to log entries made by the program blocks presented in the table
below. The defect causing the alarm can be determined according to the program
block sending the alarm.
DN9812567 Issue: 14-1 © 2016 Nokia 127


the alarm
Family name Family ID Symptom
ONSEND 12E DMC bus problems
ONRECE 12F DMC bus problems
ODCMAN 13D Problems with supervision of the OSI data

terminals
OOPADI 15C Problems with PAD connections
O7AMAN 172 Problems with OSI name service, incoming and

outgoing call routing, supervision of DX 200 OSI
software
OMGISI AF Problems with DX 200 OSI database

management
O7MANA 155 Problems with OSI data terminal configuration

files management
OEPROG 262 Problems with DX 200 OSI database

management
ODPUPD 14A Problems with OSI data terminal configuration

files management
O45LRS 164 Problems with Transport and Session service

(Transport class 0)
O54LRS 1DC Problems with Transport and Session service

(Transport class 4)
OVTBAS 1DD Problems with ISO VT service
OOFTAM 145 Problems with FTAM initiator service
O7FRSP 146 Problems with FTAM responder service
OVFSRP 153 Problems with FTAM Virtual File Store service
OCMISE 152 Problems with CMIP service
NMCOMM 151 Problems with CMIP service
OSHORT 1AF Problems with Short message service
VTERMD 98 Problems with ISO VT or PAD terminal session

service
128 © 2016 Nokia DN9812567 Issue: 14-1


the alarm (Cont.)
Family name Family ID Symptom
OFFICE 263 Problems with CLNS service
ODEUPD 261 Problems with CLNS service
OXFORD 264 Problems with ISO IP/X.25 SNDCF service
DN9812567 Issue: 14-1 © 2016 Nokia 129

Common OSI configuration mistakes OSI Guide
10 Common OSI configuration mistakes

This section is part of OSI troubleshooting.
10.1 Creation of the physical channels fails
If creation of a physical channel fails producing the error text

/**** NO FREE DATA TERMINALS ***/,
the reason is either that the data terminal is already in use or it is not registered by the
DX 200 OSI software. Inquire the physical channel information and make sure that the
terminal number is not already in use. If the terminal number is free, the registration of
the plug-in unit has failed. The reason for this can be the following:
• The unit where the plug-in unit is located has not been restarted after the
configuration of the plug-in unit. Restart the unit with the USU command.
• The plug-in unit strapping is not correct, so communication over the DMC bus fails.
Usually, there are alarms related to the plug-in unit or log entries such as
MAILBOX STRUCTURE ERROR,
sent by the ONSEND and/or ONRECE program blocks located in the unit where the
plug-in unit resides. Make sure that there are no conflicts between strappings of the
plug-in units, and that the strappings are set according to the hardware configuration
(refer to Data terminal strappings).
• If the strappings are OK, but the alarms are not cancelled and the log entries are not
cleared even when the unit is restarted, check the strappings again: they are
certainly not correct (it is especially the dual port memory setting that should be
checked).
• If there are no log entries or alarms set on but the creation of the physical channel
keeps failing, the problem is probably a faulty plug-in unit. Try again with a spare
plug-in unit.
If after all these attempts the creation fails, contact Nokia Customer Service.
10.2 Problems with Ethernet
If there are a lot of CRC or frame alignment errors in the Ethernet interface (COCEN or
PCI ethernet) but the data somehow still flows (and the Ethernet device is connected to
the Ethernet connetor), check if the autonegation function is enabled in that device.
10.3 Problems with X.25 interface
If the alarm 2262 OSI SUBNETWORK INTERFACE OUT OF ORDER is set on with the
last field having the value 4, the X.25 interface does not detect carrier. The reason for
this can be the following:
130 © 2016 Nokia DN9812567 Issue: 14-1

OSI Guide Common OSI configuration mistakes
• the physical connection is lost due to hardware problems with cabling, the remote
terminal not running, or clock signal source missing
• there is a conflict between the strappings of the plug-in unit and the actual cabling
If the alarm 2262 is not set on, but the state of the physical channel remains UNL-ENA
WO-BL, there is an X.25 link level synchronisation problem. Use the O23MTS service
terminal extension to interrogate the status of the X.25 link level (see section Monitoring
status information of X.25). The possible reasons are the following:
• both data terminals have the same role (DTE/DTE or DCE/DCE). Modify the link so
that one end acts as a DTE and the other as a DCE.
• physical connection is reported to be up although it is down. Change the local X.25
parameters (listed in Parameters of X.25) so that the link level is initiated after start-
up. Try decreasing the L2 retransmission and retry the counter values. Restart the
X.25 interface at the remote end.
If the state of the physical channel is most of the time either UNL-ENA WO-EX or UNL-
ACT WO-EX, but the X.25 interface seems to be unreliable, either the X.25 parameters
require modification or the physical connection between the terminals is unreliable. The
symptoms indicating an unreliable X.25 interface are as follows:
• the unit where the X.25 interface is located contains log entries as 'N RESET
INDICATION RECEIVED'. Use the N command in the main menu of the O23MTS
service terminal extension program (see Using O23MTS service terminal extension)
to retrieve information on the reset.
• the DX 200 OSI software initiates the disturbance 1260 X.25/ETHERNET DATA
TERMINAL SPONTANEOUS RESTART, indicating that either the plug-in was
spontaneously restarted or it was restarted by the system because it was not
responding to the supervision messages. The typical reason for this kind of
behaviour is that the memory area allocated in the plug-in unit for X.25 connections
was exhausted. Make sure that the number of concurrent X.25 connections does not
exceed the following:
– 64 in any circumstances
– 20 if the data transfer rate is heavy
– 8 if the X.25 packet size is set to 1024 bytes
– 3 if the X.25 packet size is set to 1024 and the window size is set to 8
In conjunction with the disturbance 1260, the DX 200 OSI software may also initiate
notice 9 OSI FORCED CONNECTION CLEARING, indicating that the connection
was cleared due to the restart of the plug-in unit.
• the transfer rate of the X.25 interface is exceptionally low. Use either the OOP
command or the O23MTS service extension program to interrogate the statistical
counters of the X.25 interface (see section Monitoring statistics of OSI layers 1 - 4).
Link level problems, such as CRC errors, decrease the transfer rate.
Problems with digital X.25 Interface

If the digital X.25 channel remains in WO-BL status, or in a status other than WO-EX,
even though it is unlocked, the reason might be that the frames are not transferred
trough PCM connection.
In this case, check the contents of the circuits groups X25CGR and OSIAS7 with the
RCI command.
DN9812567 Issue: 14-1 © 2016 Nokia 131

The circuit group OSIAS7 should contain the internal PCMs and time-slots used by
digitlal X.25 channels. The contents of OSIAS7 is updated when then internal PCM is
routed with the WUC command.
The circuit group X25CGR should contain the external PCMs and time-slots used by
digital X.25 channels. The contents of X25CGR is updated when creating, modifying, or
deleting the digital X.25 channels with the QCC, QCM, or QCD commands.
OSIAS7 and X25CGR must contain information of all the PCMs and time slots used by
all the digital X.25 channels of the swicth. The OSI configuration database contains the
information of PCMs and time slots attached to each digital X.25 channel. This
information can be displayed with the QCI command.
In some error cases when modifying or deleting the digital X.25 channels, it might
happen that the contents of X25CGR and the OSI configuration database do not match,
that is, the QCI command lists external PCMs and time-slots that are not found in
X25CGR. In these cases, the connection between the internal and external connection
does not succeed.
If the digital X.25 channel does not become available after unlocking it (state WO-EX),
check the contents of the OSIAS7 and X25CGR circuit groups.
If the required PCMs and time-slots are not in X25CGR, the problem can be recovered
by executing the create or modify command again (QCC or QCM).
If this does not help, you can add the missing or remove the extra PCMs and time-slots
with the commands found in the RC command group.
If the contents of OSIAS7 and X25CGR match with the information displayed with the
QCI command, and if the status of the digital X.25 channel does not become WO-EX,
the reason is that the frames are not passed between AS7 plug in units. In this case, do
the following:
1. Check the status of the channel and circuit group information of the other X.25 entity
running in the peer AS7-U.
2. If the status of the peer X.25 is also OK, then you can check if the frames are passed
properly between AS7-U and ET in the following way:
a) Install a 'loop device' in the ET of the external PCM.
b) Start the X.25 analysis with the O23MTS service terminal.
• If the connection between AS7-U and ET is working, all the X.25 frames sent
by AS7-U are echoed back by the loop device, and you should see the
following on the display of the X.25 analyser:
>SABM
<SABM
or
>DM
<DM
• If there is only the sending of frames, then the connection between AS7-U
and ET, that is, the internal PCM is in some way out of order.
3. Check both ends of the connection.
132 © 2016 Nokia DN9812567 Issue: 14-1

• If the internal PCMs are woking at both ends of the connection, then the problem
is in the external PCM. You can check with the O23MTS X.25 analyser if the
AS7-U is just sending frames. If both entities are both sending and receiving
frames, then the most probable reason is that the two X.25 entities have the
same X.25 role, that is, both are DTEs or DCEs.
• If both or the other entity is just sending frames, then the external PCM is out of
order.
• If the reason for problems in the digital X.25 channel seems to be in the internal
or external PCM, you should contact the people responsible for that DX 200
switch. They should be able to find out why the PCM connection is not working
(broken AS7, broken ET, wrong PCM used, and so on).
10.4 Problems with CLNS linkage state
Normally, the administrative state of a linkage is unlocked (UNL) and the operational
state is enabled (ENA). The administrative state may also be locked in some situations -
most of them are listed in the table below. The operational state may change to disabled
(DIS) due to operational or configuration errors. The most common errors are listed in
the table below.
Table 68 New linkage has been created and the user has forgotten to unlock it
Description Action
New linkage has been created and the user has Unlock the linkage.
forgotten to unlock it.
New linkages are created for forecoming CLNS role Leave the situation unchanged.
change, that is, role of the linkages differ from the
current role.
Linkage with faulted data terminal is locked to Leave the situation unchanged. Unlock the
cancel the alarm 2175. linkage when the data terminal is working
correctly.
Linkage has faulty parameters and it is locked by Correct the parameters and unlock the linkage or
the user. leave the situation unchanged.
Table 69 Reasons for linkage operational state DIS
Description Action
Data terminal is defective. Correct the data terminal or lock the linkage to
cancel the alarm 2175.
Peer X.25 entity does not accept the connection Check the parameters of the linkage. There may
request. also be a configuration problem in the peer site.
DN9812567 Issue: 14-1 © 2016 Nokia 133

Table 69 Reasons for linkage operational state DIS (Cont.)
Description Action
Role of the linkage does not match with the role of Lock the linkage or change the role of the CLNS.
active CLNS.
There is already another unlocked linkage for that Lock the linkage.
data terminal.
10.5 CLNS configuration problems
The most typical errors returned by CLNS MML commands are listed in the following
table.
Table 70 CLNS related errors returned by MML commands
Code Error text Description Action
10558 PHYSICAL DATA Physical terminal of the channel Check the configuration data in
TERMINAL NOT is not found in the OSCFIL file. OSCFIL and OPCFIL files of the
FOUND channel.
Data terminal may be broken. Correct
the problem with the data terminal.
11335 NETWORK The network address is Delete the application first and after
ADDRESS IS IN attached to an application and that the network address.
USE cannot be deleted.
11480 UNABLE TO Locking of an active CLNS is Restart CLNS with another CLNS
LOCK ACTIVE prohibited. parameter set and lock the previous
CLNS BU CLNS.
11486 CLNS MUST BE CLNS must be locked for Lock the CLNS.
LOCKED FOR requested operation.
THIS OPERATION
11496 CLNS CANNOT The CLNS cannot be used for Unlock the CLNS.
BE USED FOR the initialisation of ODEUPD
INITIALIZATION program block because it is
probably locked.
11635 WRONG The terminal type does not Delete the linkage and create a new
TERMINAL TYPE match the type of linkage. The one with correct linkage type.
FOR GIVEN linkage cannot be activated to a
LINKAGE data terminal of that type.
134 © 2016 Nokia DN9812567 Issue: 14-1

Table 70 CLNS related errors returned by MML commands (Cont.)
11636 TERMINAL There is already an active First, lock the other linkage with
ALREADY HAS linkage in the data terminal, identical parameters. Then unlock the
ACTIVE LINKAGE which prohibits activation of the required linkage.
given linkage. A terminal may
have several linkages, but they
must not have identical
parameters.
11637 ROLE (ES/IS) The roles of the linkage and Lock the linkages mismatching the
MISMATCH CLNS do not match. CLNS.
11646 INVALID RANGE The CLNS cannot be used for Check the parameters of the CLNS,
OF ATTRIBUTE initialisation because the CLNS especially the role.
VALUES parameters are invalid. One
possible reason is that the role
of the CLNS is wrong.
11652 TERMINAL IS The terminal of a linkage is in Correct the problem with data terminal
DISABLED disabled state, which prevents of the linkage.
the activation of the linkage.
11653 ACTIVITY STATE 1) Locking of a CLNS in the 1) Restart CLNS with another CLNS
OF CLNS IS activity state backup (BU) is parameter set and lock the previous
BACKUP prohibited. BU CLNS.
2) Occurs also when user tries 2) No actions.
to accept a CLNS already in the
activity state BU.
11673 LINKAGE IS NOT The linkage is not active at the The message is only for information.
ACTIVE moment. The reason may be a Defects requiring actions generate an
fault in the data terminal or in alarm providing more information on
the connectionless network the situation.
service. This may occur, for
example, when linkage with
faulted data terminal is locked.
11696 NO ACTIVE None of the CLNS objects in the

OSI database was active.
CLNS FOUND
11697 DATA TERMINAL The administrative state of a Unlock the data terminal.
IS LOCKED physical channel of the data
terminal is LOCKED, which
prohibits the use of the terminal.
11755 NO There is no CLNS object which Restart CLNS with the backup timer.
could be accepted by the user. After restart you can accept the new
ACCEPTABLE
Acceptance of a CLNS requires configuration.
CLNS
that its operational state is
ACTIVE, its administrative state
is UNLOCKED, and its activity
state is NEW.
DN9812567 Issue: 14-1 © 2016 Nokia 135

Table 70 CLNS related errors returned by MML commands (Cont.)
11787 CLNS HAS A CLNS object already has the Adding a new area address to the
ALREADY maximum number of manual CLNS is not possible. Remove one
MAXIMUM area addresses. address if possible and then add the
NUMBER OF new address.
MANUAL AREA
ADDRESSES
11788 CLNS HAS A CLNS object already has the Removing a manual area address from
ALREADY minimum number of manual the CLNS is not possible. Add a new
MINIMUM area addresses. address and remove the old one.
NUMBER OF
MANUAL AREA
ADDRESSES
10.6 Networking problems
When the remote end is not directly connected to the local system, it is difficult to check
the state of the remote system. Problems concerning networking, that is, the
communication between network elements, are detected when the actual connection
establishment takes place. When an X.25 connection establishment fails, the DX 200
OSI software sends notice 12 X.25 CALL ESTABLISHMENT FAILED indicating that the
remote X.25 interface is unreachable.
The first field of notice 12 identifies the plug-in unit used in the X.25 connection
establishment, and the second contains the remote NSAP address number indicating the
called DTE number. The third and the fourth fields define the originator and the reason
for call clearing according to the X.223 specification. The fifth and the sixth fields contain
the reason for call clearing and code fields from the X.25 packet level. A summary of the
possible reasons is presented in the following table.
Table 71 X.25 call clearing cases
Originator Reason Cause Code
00: remote NS- There is one-to-one 00:DTE originated 241, 242, 244, 245, 246, 247, 248
user relationship between the
values of Reason and
Code fields
01: NS-provider There is one-to-one 00:DTE originated 225, 226, 227, 228, 229, 230,
relationship between the 232, 235
values of Reason and
Code fields
136 © 2016 Nokia DN9812567 Issue: 14-1

Table 71 X.25 call clearing cases (Cont.)
01: NS-provider 00:Disconnection - 09:Out of order See X.25/ANNEX E for further

permanent condition information
11:Remote procedure
error
13:Local procedure error
15:RPOA out of order
01: NS-provider 00:Disconnection - 122:Maintenance action

permanent condition
01: NS-provider 01:Disconnection - 05:Network congestion

transient condition
01: NS-provider 01:Disconnection - 113:International protocol problem

transient condition
115:International link out of order
01: NS-provider 01:Disconnection - 00:DTE originated 162, 163

transient condition
01: NS-provider 02:Connection rejection - 0D:Not obtainable See X.25/ANNEX E for further
NSAP address unknown 39:Ship absent information
(permanent condition)
01: NS-provider 03:Connection rejection - 04:Invalid facility request See X.25/ANNEX E for further
reason unspecified/ 09:Out of information
permanent condition order0B:Access barred
11:Remote procedure
error 13:Local procedure
error 15:RPOA out of
order 19:Reverse
charging acceptance not
subscribed
21:Incompatible
destination 29:fast select
acceptance not
subscribed
01: NS-provider 03:Connection rejection - 121:Unknown called DNIC;

reason 122:Maintenance action
unspecified/permanent
condition
01: NS-provider 03:Connection rejection - 00:DTE originated 164 164

reason unspecified/
permanent condition
01: NS-provider 04:Connection rejection - 01:Number busy See X.25/ANNEX E for further
reason unspecified/ 05:Network congestion information
transient condition
DN9812567 Issue: 14-1 © 2016 Nokia 137

Table 71 X.25 call clearing cases (Cont.)
01: NS-provider 04:Connection rejection - 112:International problem;

reason unspecified/ 113:Remote network problem;
transient condition 114:International protocol
problem; 115:International link out
of order; 116:International link
busy; 117:Transit network facility
problem; 118:Remote network
facility problem; 119:International
routing problem; 120:Temporary
routing problem
01: NS-provider 04:Connection rejection - 00:DTE originated Diagnostic code other than 112-
reason unspecified/ 120.
transient condition
02: unknown 07:Undefined See X.25/Table 18 for See X.25/ANNEX E for further
originator further information information
63: local 5B: Requested service is Not meaningful Not meaningful

DTE/DCE not implemented 5D:
Physical connection is
down 5E: Administrative
state prevents the
connnection
establishment 5F: All
Virtual Circuits are
reserved 60: PVC
number out of range 61:
Invalid address field 62:
X.25 Packet Level not
restarted
10.7 CLNS routing problems
Most of the routing problems are caused by configuration errors or failures in underlying
linkages. If the route to the desired destination is not found, for example, FTAM transfer
fails, check if:
• the length of the system ID is the same in every network element within the routing
domain. Anomalies cause the alarm 2181 (see the table of alarms in the section
Notices, disturbances, and alarms initiated by the DX 200 OSI software) to be set on
in those network systems which fail to form an adjacency.
• the system ID of each network system is unique within the area, that is, no two
systems (IS or ES) use the same system ID value.
138 © 2016 Nokia DN9812567 Issue: 14-1

• the value of the MaximumAreaAddresses parameter is the same in every network

system within the area. Anomalies cause the alarm 2178 (see the table of alarms in
the section System status and OSI related data) to be set on in those network
systems which fail to form an adjacency.
• the network system has at least one manual area address in common with all the
other network systems within the area. Procedures for establishing an adjacency
require this. Anomalies cause the alarm 2182 (see the table of alarms in the
section ) to be set on in those network systems which fail to form an adjacency.
• the total amount of different area addresses in any area does not exceed the amount
specified in the MaximumAreaAddresses parameter of the network system.
Otherwise, some destinations may be unreachable because the network systems
maintain only as many area addresses in their routing tables as the
MaximumAreaAddresses parameter indicates. Anomalies cause the alarm 2177
(see the table of alarms in section Notices, disturbances, and alarms initiated by the
DX 200 OSI software) to be set on.
Check also the log entries of the logical CM.
10.8 Problems with establishing OSI connection
If an outgoing OSI connection routing fails locally, the alarm 2185 ROUTING OF OSI
OUTGOING CALL FAILED is set on. The first field of the alarm indicates the called AE-
name and the last field indicates the failure reason. A summary of the possible reasons
is presented in the following table.
Table 72 Outgoing call error cases
Error mask Description
0 DX 200 OSI software cannot locate the reason for the outgoing call failing. Submit the
trace information to Nokia Customer Service.
1 DX 200 OSI software cannot locate the called application in the local OSI
configuration. Check the application information with the QDI command.
2 DX 200 OSI software cannot locate the calling application in the local OSI
configuration. Check the application information with the QDI command.
4 The administrative state of the called application is locked, so the connection is not
allowed. Check the application state information with the QDI command.
8 The administrative state of the calling application is locked, so the connection is not
allowed. Check the application state information with the QDI command.
10 The network address belonging to the called application is disabled. Check the NSAP
address state information with the QBL command.
20 The network address belonging to the calling application is disabled. Check the NSAP
address state information with the QBL command.
DN9812567 Issue: 14-1 © 2016 Nokia 139

Table 72 Outgoing call error cases (Cont.)
40 There is no proper local NSAP address for the routes defined by the called network
address. Check the NSAP address information with the QBL command.
80 DX 200 OSI software cannot locate the application service provider in the local
configuration. Check if the software package contains the family identified by the type
of the called application: VFS - O7FRSP, CMI - OCMISE, VT - OVTBAS, SMS -
OSHORT.
100 DX 200 OSI software cannot locate the session service provider in the local
configuration. Check if the software package contains the family O45LRS (X.25
interface) or O54LRS (CLNS interface).
200 All data terminals used by the called network address are busy. Check the data
terminal state information with the QSI command.
400 A database error occurred during outgoing call routing. Submit the trace information to
Nokia Customer Service.
800 The application type information of the calling and called applications does not match.
Check the application location information with the QDI command.
1000 According to the location information either the called application is a local application
or the calling application is a remote application. Check the application location
information with the QDI command.
2000 All data terminals used by the called network address are disabled. Check the data
terminal state information with the QSI command.
If an incoming OSI connection routing fails locally, notice 2 OSI INCOMING CALL
ROUTING FAILED is set on. The first field of the notice indicates the type of the
application in which the connection routing failed and the last field indicates the reason
why the incoming call failed. A summary of the possible reasons is presented in the
following table.
Table 73 Incoming call error cases
0 DX 200 OSI software cannot locate the reason for incoming call failing. Submit the
trace information to Nokia Customer Service.
1 The administrative state of the data terminal passing the incoming call is SHD-ACT, so
the network connection is not allowed. Check physical channel state information with
the QSI command.
2 The PVC handshake fails because there is no channel group for this PVC connection.
Check channel group information with the QGI command.
140 © 2016 Nokia DN9812567 Issue: 14-1

Table 73 Incoming call error cases (Cont.)
4 The PVC handshake fails because there is no PVC NSAP for this PVC connection.
Check NSAP information with the QBL command.
8 DX 200 OSI software cannot locate the calling NSAP address in the local OSI
configuration. The NSAP information is needed because the called local OSI
application wants to know the AE-name of the calling OSI application. Check NSAP
information with the QBL command.
10 DX 200 OSI software found the called NSAP information in the local OSI configuration,
but it cannot locate a network address attached to it. Check the network address and
application information with the QBI and QDI commands.
20 The administrative state of the called NSAP is locked, so the connection is not allowed.
Check the NSAP state information with the QBL command.
40 DX 200 OSI software found the called network address information in the local OSI
configuration, but it cannot locate a local application attached to it. Check network
address and application information with the QBI and QDI commands.
80 The administrative state of the called network address is locked, so the connection is
not allowed. Check network address state information with the QBL command.
100 Remote application initiates a PAD connection, but DX 200 OSI software cannot locate
a PAD service provider in the computer unit where the data terminal passing the
incoming call is located. Check if the OOPADI family is located in this computer unit.
200 DX 200 OSI software cannot locate the called NSAP address in the local OSI
configuration. The NSAP address information is needed because otherwise it is not
possible to identify the called local application. Check NSAP address information with
the QBL command.
400 Remote application initiates a FTAM transfer, but DX 200 OSI software cannot locate
FTAM service provider in the computer unit where the called VFS is located in. Check
if the O7FRSP family is located in this computer unit.
800 Remote application establishes a CMIP connection, but DX 200 OSI software cannot
locate a CMISE service provider in the computer unit where the called local application
is located. Check if the OCMISE family is located in this computer unit.
1000 Remote application initiates an ISO VT connection, but DX 200 OSI software cannot
locate a VT service provider in the local configuration. Check if the software package
contains the OVTBAS family in the OMU.
2000 Remote application initiates a short message connection, but DX 200 OSI software
cannot locate short message service provider in the local configuration.
4000 Either the administrative state of the called local application is locked or the unit where
the called local application is located is not active, so the connection is not allowed.
Check the application and computer unit state information with the QDI and USI
commands.
DN9812567 Issue: 14-1 © 2016 Nokia 141

8000 DX 200 OSI software cannot locate the called TSAP address in the local OSI
configuration. None of the local applications attached to the called NSAP have a T-
selector value that is equal to the T-selector value of the called TSAP. Check the T-
selector information with the QDI command.
10000 DX 200 OSI software cannot locate the called SSAP address in the local OSI
configuration. None of the local applications attached to the called NSAP have an S-
selector value that is equal to the S-selector value of the called SSAP. Check the S-
selector information with the QDI command
20000 DX 200 OSI software cannot locate the called PSAP address in the local OSI
configuration. None of the local applications attached to the called NSAP have a P-
selector value that is equal to the P-selector value of the called PSAP. Check the P-
selector information with the QDI command.
40000 The administrative state of the calling NSAP address is locked, so the connection is
not allowed. The information is needed because the called local OSI application wants
to know the AE-name of the calling OSI application. Check the NSAP address state
information with the QBL command.
80000 DX 200 OSI software found the calling NSAP address information in the local OSI
configuration, but cannot locate a remote network address attached to it. The
information is needed because the called local OSI application wants to know the AE-
name of the calling OSI application. Check the NSAP and network address information
with the QBI and QBL commands.
100000 DX 200 OSI software cannot locate the calling TSAP address in the local OSI
configuration. None of the remote applications attached to the calling NSAP have a T-
selector value that is equal to the T-selector value of the calling TSAP. The information
is needed because the called local OSI application wants to know the AE-name of the
calling OSI application. Check the T-selector information with the QDI command.
200000 DX 200 OSI software cannot locate the calling SSAP address in the local OSI
configuration. None of the remote applications attached to the calling NSAP have an S-
selector value that is equal to the S-selector value of the calling SSAP. The information
calling OSI application. Check the S-selector information with the QDI command.
400000 DX 200 OSI software cannot locate the calling PSAP address in the local OSI
configuration. None of the remote applications attached to the calling PSAP have a P-
selector value that is equal to the P-selector value of the calling PSAP. The information
calling OSI application. Check the P-selector information with the QDI command.
800000 Remote application initiates a transport layer connection, but the DX 200 OSI software
cannot locate transport service provider in the computer unit where the data terminal
passing the incoming call is located in. Check that the O45LRS family is located in this
computer unit.
142 © 2016 Nokia DN9812567 Issue: 14-1

1000000 DX 200 OSI software found the calling network address information in the local OSI
configuration, but it cannot locate a remote application attached to it. The information is
needed because the called local OSI application wants to know the AE-name of the
calling OSI application. Check the information with the QBL command.
2000000 The administrative state of the calling remote application is locked, so the connection is
not allowed. The information is needed because the called local OSI application wants
to know the AE-name of the calling OSI application. Check the application state
information with the QDI command.
10.9 Application errors

FTAM Problems
Usually, an FTAM file transfer is initiated by the peer host (Billing Center, and so on), and
troubleshooting instructions and error recovery procedures of that host should be utilised
to solve the problem. Most FTAM implementations of different vendors display the FTAM
error code if an FTAM transfer fails. FTAM error codes defined in the FTAM standard are
listed in the section DX 200 and standard FTAM error codes.
The common reasons for an FTAM transfer failure are the following:
• mismatching OSI addresses, that is, incorrect NSAP or selector values

• incorrect path name of the file
• incorrect user identity or password
• missing network connection to the peer host
• missing file size attribute
When files are copied from the DX, the whole path name must be given in CAPITAL
letters. It is recommended not to specify the disk if there is no particular reason to do so,
for example, use 'VIDAST/TTTCOF01.IMG' instead of 'W0-VIDAST/TTTCOF01.IMG'.
When the DX is the responder in an FTAM transfer, the peer host must submit its user
identity. It is also possible to define a file-specific password for each FTAM operation.
The values of the FTAM attributes of a single file can be displayed and changed with the
QFM command. For example:
ZQFM:LOCALFTAM,"BIN.TST",BIN;
/* FILE ATTRIBUTES AND THEIR CURRENT VALUES WHERE AVAILABLE
NAME..... NEW FILE NAME
REA ..... FILE READ: PERMITTED
REP ..... FILE REPLACE: PERMITTED
EXT ..... FILE EXTEND: NOT PERMITTED
RAT ..... READ FILE ATTRIBUTES: PERMITTED
CAT ..... CHANGE FILE ATTRIBUTES: NOT PERMITTED
DEL ..... FILE DELETE: PERMITTED
REAC .... READ CONCURRENCY LOCKS:
DN9812567 Issue: 14-1 © 2016 Nokia 143

REPC .... REPLACE CONCURRENCY LOCKS:

EXTC .... EXTEND CONCURRENCY LOCKS:
RATC .... READ ATTR CONCURRENCY LOCKS:
DELC .... DELETE CONCURRENCY LOCKS:
OID ..... OWNER ID: USER_NAME
STR ..... MAX STRING LENGTH: NOT SIGNIFICANT
REAP .... READ PASSWORD
REPP .... REPLACE PASSWORD
EXTP .... EXTEND PASSWORD
RATP .... READ ATTRIBUTES PASSWORD
DELP .... DELETE PASSWORD */
QFM:LOCALFTAM,"BIN.TST",BIN:
The operation that is executed on a particular file must be PERMITTED.

Concurrency locks are used to define permitted concurrent access. In most cases the
values of concurrency locks need not be changed.
Owner identity (OID) identifies the owner of the file. OID is a text string exactly 8
characters long. For example in VAX FTAM the owner's identity is given in the initiator-ID
parameter in the remote file specification:
$copy/appl=ftam/alloc= DX 200"USER_NAME"::"DX file name" ...
It is possible to set passwords for different operations. This feature can be used only if
the peer host initiating the FTAM transfer can define password values for different
operations. For example, in the latest versions of DECNET/OSI of VAX, it is possible to
define passwords for different operations with the /PARAMETER qualifier.
The file system of the DX requires that the size of the file is known when the file is
created. Thus, when the peer entity copies a file into the DX, it should use the future file
size attribute specified in FTAM. For example, in DECNET/OSI of VAX the future file size
is given with the /ALLOCATION parameter in the copy command of DCL.
If a previous version of the file to be transferred already exists in the DX, and if the size
of the new version has not grown, the FTAM transfer succeeds even though the future
file size has not been given, and the DX uses the old size when it creates the new
version.
A new file smaller than 52 Kbytes can be copied without the future file size because the
FTAM of the DX creates a new file with the size of 100 blocks if the peer does not give
the future file size and if there is no previous version of that file.
PAD Problems
If the PAD connection is initiated from the DX with the command QVC and the connection
establishment fails, the DX 200 OSI software sends a notice explaining the reason for
call clearing (see section Networking problems).
10.10 Changing CP4HX based computer unit to CP6LX
In principle when a CP4HX based computer unit is changed into a CP6LX based
computer, the whole OSI configuration in that computer has to be defined from scratch,
that is, there are no special conversion programs for this purpose.
144 © 2016 Nokia DN9812567 Issue: 14-1

At least you should delete all network interfaces (TCP/IP) and broadcast linkages (OSI)
in the computer. After this, turn off the computer, remove the COCEN, and change the
processor. When you have turned the computer on, define the interfaces and linkages
again.
g Note: If the network element contains both CP6LX and CP4HX based computer units,
then the COCEN preprocessors can be used only in CP4HX-based computer units. In
the CP6LX computer unit the LAN interface is allways through the PCI LAN interface on
the CPU.
DN9812567 Issue: 14-1 © 2016 Nokia 145

Defining and starting an OSI measurement OSI Guide
11 Defining and starting an OSI measurement

Procedure
1 Create necessary directories and files on the OMU disk (if needed)
If you want to transfer the OSI measurement reports to the OMC, or just store the
report on the OMU's disk, you have to create the necessary directories and files on
the OMU's disk.
To create directories or files, use the commands of the IW command group. For more
information, refer to the instructions on the disk file and directory handling.
2 Connect the logical files (if needed)

If you want to transfer the OSI measurement reports to the OMC, or just store the
report on the OMU's disk, you have to connect the logical files in the directories and
files on the OMU's disk.
By default, the logical files are connected to the line printer (LPT-1).
For more information, refer to the instructions on I/O configuration handling.
3 Create an OSI measurement

Create an OSI measurement called OSIMEAS. Include OSI layers 3 and 4 and
channels 0 to 7 in it. Define the measurement day to cover every day of the week
(Monday to Sunday) and set the measurement interval so that the measurements
are carried out every morning at 07.00 to 10.00. Set the output interval to 60
minutes.
ZOOC:OSIMEAS:3&4,0&&7:ALL,07–00–10–00,60;
The syntax and parameters of the example is as follows:
ZOOC:<name>:<OSI layers>,<channel numbers>:<measurement day>,<measurement
interval>,<output interval>;
For more information on the OOC command, refer to the instructions on OSI statistics
handling.
4 Start the OSI measurement

Set the measurement perioid, that is, start date (6 Dec 1997) and stop date (13 Dec
1997) for the previously created measurement.
ZOOS:OSIMEAS:1997–12–06,1997–12–13;
The syntax and parameters of the example is as follows:
ZOOS:<name>:<start date>,<stop date>;
For more information on the OOS command, refer to the instructions on OSI statistics
handling.
146 © 2016 Nokia DN9812567 Issue: 14-1

OSI Guide Defining and starting an OSI measurement
5 Read the OSI measurements

After the first measurement period is over, you can read the measurement results
from the line printer or the place where you connected the logical files.
Below there are examples of the measurement reports of each layer.
DN9812567 Issue: 14-1 © 2016 Nokia 147

Using O23MTS service terminal extension OSI Guide
12 Using O23MTS service terminal extension

There is a set of software tools by which the OSI stack can be monitored and the
configuration examined. These tools are available in the O23MTS service terminal
extension.
MML commands are used to define the OSI configuration (applications, OSI addresses,
channels, and so on), whereas the tools in O23MTS can be used when you need
detailed information on the status of OSI processes. With the tools of O23MTS it is
usually not possible to change the configuration.
You can load the O23MTS extension with the following service terminal commands:
ZLE:1,O23MTSGX;
1;
In this case, you receive the main menu presented below.
OSI LAYERS 1–5 MONITOR AND TEST SYSTEM
? ..... menu / help
C ..... CVOPS nucleus monitor
X ..... layers 1-4 state and statistics
N ..... X.213 interface
O ..... OSI-file viewer
A ..... X.25 monitor
B ..... transport monitor
R ..... X.25 active addresses
F ..... monitor X.25 ack delays
L ..... CLNS finder
M ..... test MAC interface
The following tools are available in the main menu of O23MTS:
• C starts a tool for examining the internal data structures and status variables of the
processes made with the CVOPS tool. Usually this tool is used for troubleshooting by
• X starts a tool for monitoring the states of the protocol automatons of OSI layers 1 to
4 (physical level, link level, packet level, and transport layer). In the X menu there are
commands for displaying the statistical data and status information of layers 1 to 4.
This tool is handled in sections Monitoring statistics of OSI layers 1 - 4 and
Monitoring status information of X.25.
• N starts a tool for displaying information on the cause and originator of the resetting
or disconnection of an X.25 connection.
– Use the E command of the X.213 menu, giving the cause or diagnostics code of
the received message as the parameter.
• O starts a tool for displaying the contents of OSI management files in a more
readable form than just dumping the contents in hex. In section Displaying the
contents of OSI management files, there is a more detailed description of this tool.
• A starts the X.25 monitor for displaying X.25 frames sent and received by the DX. In
section Monitoring X.25 traffic, there is a more detailed description of this tool.
148 © 2016 Nokia DN9812567 Issue: 14-1

OSI Guide Using O23MTS service terminal extension
• B starts a transport monitor for displaying the network service data units sent and
received by the DX. In section Capturing transport protocol data, there is a more
• R starts a tool for displaying network addresses of the users currently logged in
through the X.25 interface.
• F starts a tool for monitoring acknowledgement delays of the link level and the
packet level. In section Monitoring X.25 acknowledgement delays, there is a more
• L starts a tool for displaying the adjacency and destination information of the
connectionless network service. In section Inquiring IS-IS routing information, there
is a more detailed description of this tool.
• M starts a tool for testing the Ethernet interface. In section Testing MAC ethernet
interface, there is a more detailed description of this tool.
You get a short description of the syntax and semantics of each command by typing '?'
and the command letter.
12.1 Monitoring statistics of OSI layers 1 - 4
You can start the status monitoring tool by choosing X in the O23MTS main menu. You
receive the menu presented below by typing '?'.
LAYERS 1-4 STATE AND STATISTICS
? ..... menu / help
A ..... layers 1-4 statistics
L ..... state of the X.25 layers
N ..... zero layer 1-4 statistic counters
T ..... transport and session layer connection information
Z ..... return
With the A command in the X menu you can display the values of the statistical counters
of layers 1 to 4.
The parameters of the A command are the following:
• message bus address of the computer unit where the X.25 data terminal (AC25 or
AS7) is located
• plug-in unit index of the X.25 data terminal
• target layer
• to display the transport layer counters, you need to define the transport protocol
class also
You can retrieve the message bus address with the USI MML command and the plug-in
unit index with the QCI MML command (refer to the corresponding instructions on
commands).
You can reset the statistical counters with the N command. Counters are located inside
the X.25 software running on the X.25 data terminal.
Physical level counters
DN9812567 Issue: 14-1 © 2016 Nokia 149

Physical level counters are incremented when errors are detected in the received frames
on OSI layer 1:
SHORTS counts too short frames
LONGS counts too long frames, that is, there is no ending flag
CRCS (cyclic redundancy check) counts frames corrupted during

the transfer
ABORTEDS is incremented when the sending of a frame is aborted
DOWNS counts carrier losses
For example, you can display the physical level (OSI layer 1) statistics with the
command:
A:41,3,1;
OSI STATISTICS MEASUREMENT REPORT
Computer: 0041 Plug unit: 03 OSI layer: 01
CHAN SHORTS CRCS ABORTEDS LONGS DOWNS
- 00000000 00000000 00000000 00000000 00000000
If the physical medium is working properly, the physical level counters should be (near)
zero.
Link level counters

Link level counters count the number of different frames sent and received by the link
level:
INFO counts sent and received information frames
REJ counts lost and thus retransmitted frames
RNR counts Receiver Not Ready frames, sent when the receiver
is temporarily not able to receive information frames
FRMR counts Frame Reject frames, sent when an error condition

not recoverable by retransmission of frames takes place
(CCITT Red Book X.25)
FRMR1 command or response control field of

the frame is undefined or not
implemented
FRMR2 information field of the frame exceeds

the maximum length established
FRMR3 invalid notification of frame expected

to be received next
150 © 2016 Nokia DN9812567 Issue: 14-1

FRMR4 information field of the frame is not

permitted, or length of the supervisory
or unnumbered frame is incorrect
RET.INFOS counts retransmitted information frames
RESETS counts link level resets
T1.EXP counts peer entity's failures to respond within time limit
Thus, all other counters except the INFO indicate some error situations.
For example, you can display the link level (OSI layer 2) statistics with the command:
A:41,3,2;
TRANSMITTED FRAMES TYPE:
- 00000265 00000000 00000000 00000000 00000000 00000000 00000000
RECEIVED FRAMES TYPE:
- 00000263 00000000 00000000 00000000 00000000 00000000 00000000
CHAN RET.INFOS RESETS T1.EXP
- 00000000 00000000 0000000B
Packet level counters

Packet level counters count the number of packets sent and received by the X.25 packet
level:
DATA counts the number of data packets transferred
RESET counts logical channel resets, that is, all untransmitted

packets are destroyed, and send and receive variables are
initialised
RESET0 counts received reset packets with the cause field value 0
If the cause field value is 0 or higher than 127, the
originator of the reset is a remote DTE. (It is very unlikely,
though, that any DTE would use a cause field value higher
than 0.)
RESET1 counts received reset packets with the cause value higher
than 0
If the cause field value is higher than 0 but lower than 128,
the originator of the reset is a DCE (that is, packet
switching network).
CLEAR counts connection clearings
DN9812567 Issue: 14-1 © 2016 Nokia 151

CLEAR0 counts received clear packets with the cause field value 0
If the cause field value is 0 or higher than 127, the
originator of the clear is a remote DTE. (It is very unlikely,
though, that any DTE would use a cause field value higher
than 0.)
CLEAR1 counts received clear packets with the cause value higher
than 0
If the cause field value is higher than 0 but lower than 128,
the originator of the clear is a DCE (that is, packet
switching network).
RESTART counts initialisations of the whole packet level
RNR counts the times a single logical channel has been unable
to receive any more data packets. Usually this means that
the user of the X.25 connection is not consuming data at
the rate it is received.
SUCC.IN and count the number of successful incoming and outgoing

SUCC.OUT calls
UNSUC.IN and count the number of unsuccessful incoming and outgoing

UNSUC.OUT calls
DUR.A counts calls that have lasted less than 10 seconds
DUR.B counts calls that have lasted more than 10 but less than
300 seconds
DUR.C counts calls that have lasted between 300 and 3600
seconds
DUR.D counts calls that have lasted more than 3600 seconds
T20 counts the number of unanswered RESTART REQUESTs
T21 counts the number of unanswered CALL REQUESTs
T22 counts the number of unanswered RESET REQUESTs
T23 counts the number of unanswered CLEAR REQUESTs
For example, you can display the packet level (OSI layer 3) statistics with the command:
A:41,3,3;
TRANSMITTED PACKETS TYPE: SEGMENTS:
------------------------- ---------
CHAN DATA RESET CLEAR RESTART RNR TRANS RECEIVED
152 © 2016 Nokia DN9812567 Issue: 14-1

- 000001E4 00000000 00000000 00000001 00000000 000001E6 0000002D

RECEIVED PACKETS TYPE:
----------------------
CHAN DATA RESET0 RESET1 CLEAR0 CLEAR1 RESTART RNR
- 0000002D 00000000 00000000 00000001 00000000 00000000 00000000
CALLS:
------
CHAN SUCC.IN SUCC.OUT UNSUC.IN UNSUC.OU REJ.OUT IN DUR.A IN DUR.B
- 00000002 00000000 00000000 00000000 00000000 00000000 00000000
CALLS: TIMEOUTS: PACKETS
------ --------- DISCARDED
CHAN IN DUR.C IN DUR.D T20 T21 T22 T23
- 00000001 00000000 00000000 00000000 00000000 00000000 00000000
12.2 Monitoring status information of X.25
You can start the X.25 status monitoring tool by choosing X in the O23MTS main menu.
There you can display the status of X.25 layers (OSI layers 1-3) and the logical channels
of the packet level with the L command.
The parameters of the L command are the following:
• message bus address of the computer unit where the X.25 data terminal (AS7-C or
AS7-D) is located
• target layer
• parameter defining whether to display layers, channels, or both
You can retrieve the message bus address with the USI MML command and the plug-in
unit index with the QCI MML command (refer to the corresponding MML command
descriptions.)
For example, you can display the status of X.25 layers and logical channels with the
command:
L:41,3;
The status of the X.25-interface
================================
Computer: 0041 Plug unit: 03
O23LRS init status: Valid start message received.
Physical level status: The physical level is up and running.
Link level status: The link level is up and running.
Packet level status: Packet level has been restarted (up and
running)
Status of the logical channels
------------------------------
Net ref Channel state NS user Credit given Credit left
0001 Data transfer state 0041 015C 0780 0489
0002 - 0004 Not in use 0000 0000 0000 0000
DN9812567 Issue: 14-1 © 2016 Nokia 153

In this case, the X.25 is up and running. Five logical channels have been defined, one of
which is in use (Data transfer state). The other channels are idle. The user of the first
channel is process 15C (OOPADI) in a computer unit with the message bus address is
41 (OMU-0). The credit variables indicate how much data each entity can send to the
other.
In case the physical connection to the peer entity is not working properly, the output of
the layers could be:
The status of the X.25-interface
================================
Computer: 0042 Plug unit: 04
O23LRS init status: Valid start message received.
Physical level status: The physical level is down. Status of
signals is:
DSR = FF DCD = FF CTS = FF
TI = 00 CI = 00 I = 00
Link level status: The link level is disconnected.
Packet level status: Packet level is waiting for link level to
connect.
The possible reasons for this might be the following:
• the cable is of the wrong type

• type of the interface set with data terminal strapping is different from what has been
defined with the QTC command
• data terminal strapping defining the clock signal source is not set correctly
• some other strappings are not set correctly
• the remote entity is not running
If the L command states that the physical level is up and running but the link level is not,
the link connection to the peer entity is not working properly.
The possible reasons for this might be the following:
• both entities have the same role, that is, both are defined to be DCEs or DTEs
• the frame sent by one entity never reaches the other entity, that is, the physical layer
is not working, even though carrier has been detected and the L command claims
that the physical level is up and running.
Section Problems with X.25 interface gives more information on fault situations.
12.3 Displaying the contents of OSI management files
You can display the contents of OSI management files with the File Viewer tool to
examine the status of local and remote OSI processes, OSI addresses, and OSI
terminals. You can start the File Viewer tool by choosing O in the O23MTS main menu.
Type '?' and you get the file viewer menu shown below.
OSI file viewer
? ..... menu / help
C ..... OSI File Checker
S ..... current OSI sessions (OCSFIL-file)
P ..... registered OSI service processes (OCOFIL-file)
154 © 2016 Nokia DN9812567 Issue: 14-1

T ..... registered OSI terminals (OSCFIL-file)

U ..... view OMLFIL file
V ..... view OMDFIL file
W ..... view OMNFIL file
Z ..... return
12.3.1 OSI File Checker
By choosing C in the file viewer menu, you can check the conflicts between the OSI
configuration files which are the following:
• physical channel file

• OSI physical channel state file
• analogue terminal file
• physical channel group file
If everything is correct, the outputs could be:

Checking conflicts between OSI configuration files...
The record 0A of the physical channel file (OPC) corresponds to

the record 01 of the analog data terminal file (ATF).
The record 0A of the physical channel file (OPC) corresponds to

the record 0B of the OSI physical channel state file (OSC).
The physical channel file (OPC) corresponds to the physical channel

group file (OCG).
...Files have checked.
If there are conflicts between the physical channel file and the analogue terminal file, the
output could be:
Contents of record of the physical channel file (OPC):
rec unit piu term

num: addr: ind: type:
---- ----- ---- -----
0A OMU-0 03 analog
The definition of plug-in unit in analog data terminal file (ATF)

does not correspond to definition in the physical channel file (OPC).
This indicates that the plug-in unit whose index is 03 cannot be found in the analogue
terminal file.
If there are conflicts between the physical channel file and the OSI physical channel
state file, the output could be:
rec unit piu term

DN9812567 Issue: 14-1 © 2016 Nokia 155

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

0A OMU-0 03 analog
There is a plug-in unit in the OSI physical channel state file (OSC)
but the type of plug-in unit 03C5 does not correspond to the type in the physical
channel file (OPC).
Check out the OSI configuration and equipment.
This indicates that in the OSI physical channel state file the type of plug-in unit is 03C5,
which is a digital type, but in the physical channel file type the plug-in unit is analogue.
Or the output could be:
rec unit piu term

---- ----- ---- -----
0A OMU-0 03 analog
This computer unit/plug-in unit pair cannot be found from

the OSI physical channel state file (OSC).
This indicates that the OMU-0 computer unit / 03 plug-in unit pair cannot be found in the
OSI physical state file.
All outputs mentioned above have the following fields:
Rec num indicates the record of the physical channel file
Unit addr indicates the computer unit in the record of the physical
channel file
Piu ind indicates the index of plug-in unit in the record of the
physical channel file
Term type indicates the type of plug-in unit in the record of the
If there are conflicts between the physical channel group file and the physical channel
file, the output could be:
Contents of record of the physical channel group file (OCG):
rec chan group chan

num: identification: num:
---- --------------- ----
02 PADLOOP 00
This channel cannot be found from the physical channel file (OPC).
This indicates that channel number 00 cannot be found in the physical cannel state file.
The output has the following fields:
Rec num indicates the record of the physical channel group file
which contains the channel which cannot be found in the
156 © 2016 Nokia DN9812567 Issue: 14-1

Chan group indicates the group identification

identification
Chan num indicates the channel number which cannot be found in the
12.3.2 Current OSI sessions
You can monitor the current OSI sessions by choosing S in the file viewer menu. The
output can be:
Current OSI sessions (OSCFIL-file)
cep p ns ns ns ss ss osi osi osi
state 3 4 5 6 7 u unit fam pro unit fam unit fam pro
--------- -- -- -- -- -- - ------ ---- ---- ----- ---- ----- ---- ----
conn_up 11 10 - - - 7 OMU-1 015C 0000 0000 OMU-0 0098 0009
This indicates that there is one PAD session in progress in the switch.
The output of the current OSI sessions has the following fields:
state are CVOPS connection virtual task identifiers used for

identifying the connection. Ceps 3 to 7 are displayed the
internal state of the session
ceps are CVOPS connection virtual task identifiers used for

identifying the connection; ceps 3 to 7 are displayed
ns-unit indicates the unit of the network service user
ns-fam indicates the family of the network service user
ns-pro indicates the process of the network service user
ss-unit indicates the unit of the session service
ss-fam indicates the family of the session service
osi-unit indicates the unit of the OSI application used by the

session
osi-fam indicates the family of the OSI application used by the

session
osi-pro indicates the process of the OSI application used by the

session
12.3.3 Registered OSI service processes
You can monitor the registered OSI service processes by choosing P in the file viewer
menu. The output can be:
Registered OSI service processes (OCOFIL-file)
unit family family family family family family family family
DN9812567 Issue: 14-1 © 2016 Nokia 157

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

OMU-0 o45lrs o54lrs ocmise o7frsp ooftam ovtbas -
success success no need success success no need no need
The output of the registered OSI service processes has the following fields:
unit lists the units containing registered OSI service processes

in the switch
family lists the names of the families of registered processes
initialisation state fields indicate the initialisation states of registered processes
no need means that the process does not

need initialisation
pending means that the initialisation has not

yet started or it is in progress
success means that the initialisation has been

successful
failed means that initialisation of the

process has failed
12.3.4 Registered OSI terminals
You can display all computer units containing OSI terminals by choosing T in the file
viewer menu. The output can be:
Registered OSI terminals (OSCFIL-file)
unit piu map con state substate p alarm connect MAC
addr ind typ sta sta adm fun -1 -2 -3 i set rea max cur address
------ --- ---- --- --- --- --- --- --- --- - --- --- --- --- ---------
OMU-1 05 00B2 NO - UNL ENA RUN 00 RUN 1 - - 00 00 00 004043FF8008
OMU-1 06 007A YES - UNL DIS NOA 00 RUN 2 YES 04 04 00 -
OMU-1 07 007A YES - UNL ACT NOA 00 RUN 3 YES 04 1B 01 -
OMU-1 04 007A YES - UNL ENA RUN 00 RUN 4 - - 1 00 -
OMU-0 05 00B2 NO - UNL ENA RUN 00 RUN 2 - - 00 00 004043FF8007
OMU-0 04 007A YES - UNL ENA RUN 00 RUN 3 - - 01 00 -
The output of the registered OSI terminals has the following fields:
unit-addr lists the computer units containing OSI terminals in the

switch
piu-ind lists indexes of the plug-in units accommodating OSI

terminals
piu-typ lists the types of registered data terminals
158 © 2016 Nokia DN9812567 Issue: 14-1

00B2 a data terminal for Ethernet networks

(COCEN data terminal)
007A an X.25 data terminal for analogue

packet networks (AC25–S)
006C an X.25 data terminal for digital

packet networks (AS7–U)
0090 an X.25 data terminal for digital

packet networks (AS7–V)
0102 an Ethernet interface (PCI bus based

DX 200 network element)
03C3 an AC25–A data terminal (PCI bus

based DX 200 network element)
03C5 an AS7–A data terminal (PCI bus

based DX 200 network element)
The index of the Ethernet interface is not the same as that

of the QLL command. 128 corresponds to the QLL index 0.
map-sta indicates the mapping state of X.25 data terminals
YES means that the data terminal is

mapped to a physical terminal
NO means that the X.25 channel is not in

use
The mapping state values of COCEN data terminals have

no meaning in IS-IS routing administration.
con-sta indicates the connection status of the X.25 data terminals

of the type 6C
YES means that the external and internal

PCM-TSLs have been connected
NO means that the channel is not in use
REQ means that the connection has been

requested but not confirmed
RRQ means that the connection release

has been requested but not confirmed
state-adm lists the administrative states of the terminals
DN9812567 Issue: 14-1 © 2016 Nokia 159

LOC means that the terminal is not in use

(locked)
UNL means that the terminal is in use

(unlocked)
state-fun lists how the switch sees the functional states of the
terminals
DIS means that the terminal is not in use

(disabled)
ENA means that terminal is available

(enabled)
ACT means that the terminal is in use and

active (active)
BUS means that the terminal is in use and

busy (busy)
functional substate give additional information on the terminals

fields
Substate-1 field means that the terminal is starting up
STA
Substate-1 field means that the terminal is available
AVA
Substate-1 field means that the terminal is unavailable
NOA
Substate-1 field means that the terminal is running
RUN
Substate-2 is in reserve
Substate-3 field means that the terminal is under

TES testing
pi indicates the process ID number of the hand processes of

each terminal
alarm-set field YES indicates that the alarm 2262 (OSI plug-in unit out of
order) is set on
alarm-rea gives the reason code for the alarm 2262 to be set on
connect-max indicates the maximum number of simultaneous

connections through each X.25 data terminal
connect-cur indicates the present number of connections through each

X.25 data terminal
MAC address indicates the physical address of each Ethernet interface
160 © 2016 Nokia DN9812567 Issue: 14-1

12.3.5 Dynamic linkage information (OMLFIL)
You can display the OSI environment work file for linkages (OMLFIL) by choosing U in
the file viewer menu. The file contains dynamic information about physical linkages and
their states.
The information is collected by OMGISI during the normal execution of the CLNS. The
file is located in the logical central memory.
12.3.6 Information on distributed parts of CLNS (OMDFIL)
You can display the OSI environment work file for the distributed parts (OMDFIL) by
selecting V in the file viewer menu. The file contains state information about the
distributed parts of the CLNS.
The information is collected by OMGISI during the normal execution of the CLNS. The
file is located in the logical central memory.
12.3.7 Dynamic information on CLNS (OMNFIL)
You can display the OSI environment work file for information on the CLNS (OMNFIL) by
choosing W in the file viewer menu. The file contains dynamic information like the
operational state and active network service user of each CLNS stored in the OEDATA
database.
The file is located in the logical central memory.
12.4 Monitoring X.25 traffic
By selecting A in the O23MTS main menu, you can start the X.25 Analyser tool with
which you can monitor X.25 traffic on a single X.25 line.
By typing '?', you receive the X.25 Analyser menu shown below.
X.25 ANALYSER
? ..... menu / help
C ..... capture traffic into memory buffer
M ..... analyse traffic from memory buffer
L ..... analyse traffic from line
T ..... display only defined frames (triggers)
H ..... short guide about this analyser
Z ..... return
With the X.25 Analyser tool you can capture X.25 traffic, analyse it on-line, store the
captured LAPB frames in the ring buffer, and analyse them there.
The capacity of the memory buffer is 1000 frames.
DN9812567 Issue: 14-1 © 2016 Nokia 161

g Note: When sending copies of LAPB frames to the analyser, the X.25 process
deliberately decreases the throughput of X.25 frames, so it is recommended to use this
tool only when investigating existing problems.
12.4.1 On-line analysis of X.25 frames
You can capture X.25 frames for on-line analysis with the L command in the X.25
Analyser menu. The parameters of the L command are the following:
AS7-D) is located
• plug-in unit index of the X.25 controller
• terminal mode: DTE or DCE
• storage of frames: B(uffer) or N(o)
You can retrieve the message bus address with the USI MML command, and the plug-in
unit index and the mode of the terminal with the QCI MML command (refer to the
corresponding MML command descriptions).
For example, if your DTE X.25 controller has the index 5, it is located in an OMU with the
message bus address 4A, and you decide to store the captured frames in the ring buffer
also for further analysis, give the command:
L:4A,5,DTE,B;
The output could look like the following:
>>> Timeout
>>> Timeout
>>> Timeout
> A I 7 0 P/F 0 LCN20 CALL REQ
Calling address: None
Called address: 320010312
Facilities length 00
User data 01000000
< A RR 0 P/F 0
< B I 0 0 P/F 0 LCN20 CALL ACC
Calling address: None
Called address: 320010312
Facilities length 00
User data
> B RR 1 P/F 0
< B I 1 0 P/F 0 LCN20 DATA Q 0 0 040100020003000400050006
> B RR 2 P/F 0
> A I 0 2 P/F 0 LCN20 RR 1
< B I 2 0 P/F 0 LCN20 DATA Q 1 0 020200
> B RR 3 P/F 0
> A I 1 3 P/F 0 LCN20 RR 2
< A RR 1 P/F 0
< B I 3 1 P/F 0 LCN20 DATA Q 2 0 02037E04000F01
> B RR 4 P/F 0
If there is no X.25 traffic, the text '>>> Timeout' is displayed after every 5 seconds.
Analysis of the first captured frame:
162 © 2016 Nokia DN9812567 Issue: 14-1

• sent out by the local X.25 (>)

• LAPB address of the frame is A
• it is an information frame (I)
• sequence number of this frame is 7 (modulo 8 numbering)
• the local entity expects next an LAPB frame with the sequence number 0
• value of the poll/final bit is 0
• the frame contains a packet level Call Request on logical channel 20
– without the calling address
– with the called address 320010312
– without facilities
– with user data 01000000 (hex)
The second frame is sent by the peer X.25 (<) responding with a Receiver Ready frame
(RR) expecting next a frame with the sequence number 0 and poll/final bit 0.
The peer X.25 (<) accepts the call with an I frame containing a packet level CALL
ACCEPTED packet.
The local X.25 sends a Receiver Ready frame expecting next a frame with the sequence
number 1, thus acknowledging the previous I frame sent by the peer entity.
The peer entity sends an I frame containing packet level data. The value of the Q bit in
packet header is 1 indicating that the packet contains X.29 control data. The sequence
number of this packet is 0, and the sequence number of the packet expected next is 0.
The packet level data is hex pattern: 0401000, and so on.
The local entity accepts the received I frame number 1 by a Receiver Ready frame,
expecting frame number 2 to be next.
The local entity sends an I frame containing a packet level Receiver Ready, indicating
that the sequence number of the next packet received from logical channel 20 is
expected to be 1, and so on.
When you think you have seen the relevant part of the X.25 traffic in progress, you can
quit the monitoring by pressing control-C (it can take up to 5 seconds to quit the
monitoring).
If you have enabled storage by supplying the B parameter in the L command, you are
able to further analyse the captured frames in the ring buffer memory as described in
section Analysis of X.25 frames stored into the ring buffer.
The memory buffer will be cleared when you leave the O23MTS session. If you use a PC
as the service terminal, you can store the contents of the buffer in a PC disk file by using
the PC logging utility and displaying the whole buffer with the A command in the ring
buffer analysis menu presented in the section Analysis of X.25 frames stored into the
ring buffer.
g Note: To capture X.25 frames, the analyser program tells the X.25 process running on
AS7-C or AS7-D to send a copy of each LAPB frame passed between link and physical
levels (that is sent to or received from line). Thus, if there is something wrong with the
physical layer, the result of the X.25 traffic analysis made with this tool can be different
from an analysis made with some external X.25 analyser capturing frames directly from
the physical media.
DN9812567 Issue: 14-1 © 2016 Nokia 163

If the LAPB frame is longer than 40 bytes, only the first 40 bytes of the frame are copied.
12.4.2 Analysis of X.25 frames stored into the ring buffer
You can analyse frames that are stored in the ring buffer memory with the M command in
the X.25 Analyser menu.
For example, if you decide to further analyse the frames captured in the previous
example, issue the M command, giving the mode of the terminal (DTE or DCE) as the
parameter:
M:DTE;
In this case, you receive the menu of the M command presented below.
F ... goto first frame and display it
E ... goto last frame and display it
Snnn ... goto frame nnn and display it
N ... display next frame
V ... display next page
P ... display previous frame
B ... display previous page
A ... display whole buffer
H ... This help text
Z ... stop monitoring from buffer
You can scroll the contents of the buffer one frame or one page (20 frames) at a time or
leap to any specific frame using the index of the frame in hexadecimal.
The next and previous are relative to the current point, which is the frame displayed last.
In the beginning the current point is the first frame. The output of the M command also
displays the number of frames in the buffer.
The output of the stored frames is similar to the output created in the on-line analysis (of
which an example was presented in section On-line analysis of X.25 frames). The only
difference is the frame index in the buffer being displayed in the first field, before the
direction of communication.
buffer analysis menu.
12.4.3 Storing captured frames into ring buffer - no analysis
You can capture and store the traffic in the ring buffer memory with the C command in
the X.25 Analyser menu. The parameters of the C command are the following:
• message bus address of the computer unit where the X.25 controller (AS7-C or AS7-
D) is located
• plug-in unit index of the X.25 controller
descriptions).
164 © 2016 Nokia DN9812567 Issue: 14-1

The capacity of the memory buffer is 1000 frames.

ring buffer.
12.5 Capturing transport protocol data
You can start the Transport Analyser tool by choosing B in the O23MTS main menu. You
can display the Transport Analyser menu presented below by typing '?'.
TRANSPORT ANALYSER
? ..... menu / help
C ..... capture traffic into memory buffer
M ..... analyse traffic from memory buffer
L ..... analyse traffic from line
H ..... short guide about this analyser
Z ..... return
You receive a short description of the syntax and semantics of each command by typing
With the Transport Analyser tool you can capture transport protocol data units (TPDUs),
analyse them on-line, store the captured units in the ring buffer, and analyse them there.
The capacity of the memory buffer is 1000 data units.
12.5.1 On-line analysis of transport protocol data units (TPDUs)
You can capture TPDUs for on-line analysis with the L command in the Transport
Analyser menu. The parameters of the L command are the following:
• message bus address of the computer unit where the transport protocol is located
• storage of frames: B(uffer) or N(o)
You can retrieve the message bus address with the QEI MML command (active NS-
User).
For example, if you decide to monitor your transport traffic on-line and store the captured
TPDUs in the ring buffer for further analysis, give the following command:
ZL:0,B;
The output could look like the following:
>>> Time-out
>>> Time-out
>>> Time-out
> CR 0000 1B65 Transport protocol 4. Normal format.
> CR 0000 1B65 Transport protocol 4. Normal format.
< CC 1B65 1C55 Transport protocol 4. Normal format.
> DT 1C55
> DT 1C55
DN9812567 Issue: 14-1 © 2016 Nokia 165

> DR 1C55 1B65 Normal disconnect initiated by the session entity.

< DC 1B65 1C55
>>> Time-out
>>> Time-out
If there is no transport traffic, the text '>>> Timeout' is displayed after every 5 seconds.
You can use the following table to interpret the contents of the on-line analysis output.
Table 74 Output fields of transport traffic analysis for different TPDUs
Type if TPDU Index in Direction Type Transport Transport Others

buffer destination source
Connection HHHH '<' or '>' CR 0000 HHHH Class

request option
Connection confirm HHHH '<' or '>' CC HHHH HHHH Class

option
Disconnection HHHH '<' or '>' DR HHHH HHHH Reason

request
Disconnection HHHH '<' or '>' DC HHHH HHHH

confirm
Data HHHH '<' or '>' DT HHHH
Expedited data HHHH '<' or '>' ED HHHH
Data HHHH '<' or '>' AK HHHH

acknowledgement
Expedited data HHHH '<' or '>' EA HHHH

acknowledgement
Error HHHH '<' or '>' ER HHHH
The index of the data unit in hexadecimal is displayed only when analysing TPDUs in the
buffer.
The direction indication is > if the data unit is sent, and < if it is received by the local
transport entity.
The type of TPDU is indicated with a mnemonic.
The transport connection is identified with the transport destination and transport source
references in hexadecimal.
The proposed (in CRs) or confirmed (in CCs) transport protocol class identified in the last
field can only be TP4 because the analyser decodes only TP4 data units.
When you think you have seen the relevant part of the transport traffic in progress, you
can quit the monitoring by pressing control-C (it can take up to 5 seconds to quit the
monitoring).
166 © 2016 Nokia DN9812567 Issue: 14-1

If you have enabled storage by supplying the B parameter in the L command, you are
able to further analyse the captured data units in the ring buffer memory as described in
section Analysis of TPDUs stored into the ring buffer.
ring buffer.
g Note: To capture transport protocol data units (TPDUs), the analyser program tells the
local transport entity to send a copy of each network service data unit (NSDU) passed
between the transport and network layers (that is, a copy of each NSDU sent to or
received from the network). Thus, if there is something wrong with the network layer,
the result of the transport analysis made with this tool can be different from an analysis
made with some external transport analyser capturing data units directly from the
physical media.
12.5.2 Analysis of TPDUs stored into the ring buffer
You can analyse data units that are stored in the ring buffer memory with the M
command in the Transport Analyser menu.
You can choose from two modes of displaying the network service data units stored in
the ring buffer. The output in the short mode is presented above in this subsection with
the interpretation table. The long mode provides you with more information on the
transport traffic.
For example, if you decide to further analyse the data units captured in the previous
example, issue the M command, giving the mode of display (S or L) as the parameter:
ZM:L;
In this case, you receive the menu of the M command presented below.
F ... go to first data unit and display it
E ... go to last data unit and display it
Snnn ... go to data unit nnn and display it
N ... display next data unit
V ... display next page (Only in short mode)
P ... display previous data unit
B ... display previous page (Only in short mode)
A ... display whole buffer (Only in short mode)
H ... This help text
Z ... stop analysing from buffer
You can scroll the contents of the buffer one data unit or one page (20 units) at a time, or
leap to any specific unit using the index of the unit (in hexadecimal).
Next and previous are relative to the current point, which is the unit displayed last. At the
beginning, the current point is the first data unit. The output of the M command also
displays the number of data units in the buffer.
Your display in the long mode could look like this:
0000 Direction: DX200 > Peer OSI stack
Destination NSAP: 122345000044556666678965
DN9812567 Issue: 14-1 © 2016 Nokia 167

Source NSAP: 323432434345335454545434

TPDU type: Connection request (E0)
Number of TPDU's the transport entity may send (credit): 1
Destination transport reference: 0000
Source transport reference: 13B6
Transport protocol 4. Normal format.
Data (HEX): 1F1D3D4F5635378283630202876352673572
The first line indicates the index of the displayed data unit in the memory buffer and the
direction of communication.
The second line shows the NSAP address of the destination of the data unit.
The third line shows the NSAP address of the source of the data unit.
The fourth line shows the type of the data unit.
The fifth line indicates how many TPDUs the remote entity may send without waiting for
acknowledgement.
Destination and source references (in hexadecimal) in the sixth and seventh lines
identify the transport connection.
If the TPDU is a connection request or a connection confirm, the eighth line expresses
the transport protocol class. If the TPDU is a disconnection request, the eighth line gives
the reason for the disconnection.
The rest of the lines show TPDU variables. They can contain up to 30 bytes of user data
if the TPDU is a connection request, connection confirm, disconnection request, data, or
expedited data.
The capacity of the memory buffer is 1000 data units, and the buffer is organised as a
ring.
ring buffer.
12.5.3 Storing captured TPDUs into ring buffer - no analysis
You can capture and store TPDUs in the ring buffer memory with the C command in the
Transport Analyser menu presented. The parameter of the C command is the message
bus address of the OMU which is 0.
The capacity of the memory buffer is 1000 data units.
ring buffer.
168 © 2016 Nokia DN9812567 Issue: 14-1

12.6 Monitoring X.25 acknowledgement delays
With the X.25 Acknowledgement Delay Monitor tool you can monitor X.25
acknowledgement delays, that is, delays of I-frames (LAPB, link level) and packets
(packet level).
You can start the tool by selecting F in the O23MTS main menu. By typing '?' you get the
X.25 Acknowledgement Delay Monitor menu shown below.
X.25 Acknowledgement Delay Monitor
? ... menu / help
C ... define monitored terminal
Q ... initialise level 2 counters
W ... inquire average acknowledgement time on level 2 (link level)
E ... initialise level 3 counters
R ... inquire average acknowledgement time on level 3 (packet level)
T ... set time-out
H ... short guide
Z ... return
The H command displays a small guide to the monitoring tool.
12.6.1 Defining the terminal to be monitored
You can define the X.25 terminal you want to monitor with the C command, supplying the
following parameters:
AS7-D) is located
descriptions).
For example, if you decide to monitor the X.25 terminal with the plug-in unit index 4 in
the computer unit with message bus address 41, enter the command:
C:41,4;
Computer 41, plug-in unit 4
Without any parameters, the C command shows the currently selected computer unit
and plug-in unit.
DN9812567 Issue: 14-1 © 2016 Nokia 169

12.6.2 Monitoring and resetting link level acknowledgement

statistics
By selecting Q in the acknowledgement delay monitor menu you can do the following:
• display the number of information frames sent and received since the last reset of
the counters
• display the cumulative acknowledgement delay time of these I-frames
• display the average acknowledgement delay time of these I-frames
• reset the counters
For example, enter the following command:

ZQ;
Number of I frames : 7
Cumulative acknowledgement time: 80 ms
Average acknowledgement time : 11 ms
Counters are initialized.
Although the acknowledgement times are shown in milliseconds, the real precision of
measurement (in cumulative acknowledgement time counter) is a hundredth part of a
second. That is because one tick of clock in an X.25 terminal is 10 ms. This means that if
the real acknowledgement time is 1 to 9 ms, then 10 ms is added to the cumulative
counter. So acknowledgement times are just suggestions, not exact values.
If the X.25 process does not reply in five seconds, the Q command sends the following
error message:
>>>> Time-out, no reply from X.25 terminal
You can change the waiting time of the Q command (and all other commands except C)
with the T command presented in section Time-out delay adjustment.
12.6.3 Monitoring link level acknowledgement statistics - no

resetting
By selecting W in the acknowledgement delay monitor menu presented above, you can
do the following:
• display the number of information frames sent and received since the last reset of
the counters (with the Q command or by restart of the X.25)
• display the cumulative acknowledgement delay time of these I-frames
• display the average acknowledgement delay time of these I-frames
Unlike the Q command, the W command does not reset the statistical counters.
The output of the W command is similar to that of the Q command (see section
Monitoring and resetting link level acknowledgement statistics), except for the note of the
counter reset.
170 © 2016 Nokia DN9812567 Issue: 14-1

If the X.25 process does not respond to the W command within a specified time limit (the
default value is five seconds, you can modify it with the T command), the W command
prints the 'Time-out, no reply' error message.
12.6.4 Enabling packet level acknowledgement monitoring
By selecting E in the acknowledgement delay monitor menu, you can do the following:
• enable monitoring of the packet level acknowledgement delay times of the next
connection
• reset the corresponding statistical counters
The E command sends the following message:

Acknowledgement times of next X.25 connection will be monitored.
After this, the packet level acknowledgement times of your next X.25 connection will be
monitored and you can display the results with the R command.
If the X.25 process does not respond to the E command within a specified time limit (the
default value is five seconds, you can modify it with the T command), the E command
12.6.5 Inquiring packet level acknowledgement statistics
If you have enabled the monitoring of packet level acknowledgement times with the E
command and an X.25 connection has taken place, you can display the results by
choosing the R command in the acknowledgement delay monitor menu.
The output of the R command displays the following:
• the logical channel used in the monitored X.25 connection

• the number of data packets sent and received during the monitored connection
• the cumulative acknowledgement delay time of these data packets
• the average acknowledgement delay time of these data packets

ZR;
Logical channel : 9
Number of data packets : 6
Cumulative acknowledgement time: 120 ms
Average acknowledgement time : 20 ms
Although the acknowledgement times are shown in milliseconds, the real precision of
measurement (in cumulative acknowledgement time counter) is a hundredth part of a
second. That is because one tick of clock in an X.25 terminal is 10 ms. This means that if
the real acknowledgement time is 1 to 9 ms, then 10 ms is added to the cumulative
counter. So the acknowledgement times are just suggestions, not exact values.
If the X.25 process does not respond to the R command within a specified time limit (the
default value is five seconds, you can modify it with the T command), the R command
DN9812567 Issue: 14-1 © 2016 Nokia 171

12.6.6 Time-out delay adjustment
With the T command you can change the time-out delay if the default delay (five
seconds) is not suitable. Time-out delay is the time that commands (all except C) wait for
the X.25 software to respond. You can give the new time in seconds as the parameter of
the T command. The maximum value is 60 seconds.
12.7 Inquiring IS-IS routing information
With the CLNS Finder tool you can display the CLNS adjacency and destination
attributes of your OSI configuration. The information is stored in the logical central
memory. The figure below presents adjacencies and destinations as they are seen from
the viewpoint of the DX 200.
Figure 20 Adjacencies and destinations as seen by the DX 200
ES
LAN
X.25 ADJACENCIES ES
X.25
DX200 IS
ES DESTINATIONS
LAN
ES ES
ADJACENCY
You can start the CLNS Finder by choosing L in the O23MTS main menu. By typing '?',
you get the CLNS Finder menu shown below.
CLNS managed object finder 04/01/95
? ..... menu / help
A ..... Adjacency information
D ..... Destination information
172 © 2016 Nokia DN9812567 Issue: 14-1

12.7.1 CLNS adjacency information
You can display CLNS adjacency information with the A command in the CLNS Finder
menu. Entering '?', you get the CLNS Adjacency Finder menu shown below.
CLNS Adjacency managed object finder
? ..... menu / help
1 ..... Give a local circuit and do search
2 ..... Give a linkage id and do search
3 ..... List active linkages
4 ..... List error codes
You can display your active linkages entering the 3 command in the CLNS Adjacency
Finder menu. The output could look like this:
1. LOCAL CIRCUIT : 0001 LINKAGE : 0000
There are no more linkages
You can display the adjacency information of a specific linkage with the 1 command
giving the local circuit ID as the parameter, or with the 2 command giving the linkage ID
as the parameter.
g Note: You can display the same adjacency information with the QLP MML command.
For example, if you choose to display adjacency information of local circuit number 1,
give the following command:
1:1;
The output could look like this:
ADJ_ID STATE USE TIM(s) PRTY ADDRESS NEIGH SYSTEM_ID_SET
------- ------ ------ ------- ------ --------------- ------ ----------------
2 UP LEVEL1 30 - MISSING VALUE LEV1IS 222222222222
2 AREA_ADDRESS(ES) 39246F00000116000000010001
01020304050607080910111213
NUMBER OF ADJACENCIES : 1
In this case, local circuit 1 has only one adjacency:
• ID of the adjacency is 2
• state of the adjacency is UP
• it is used for level 1 routing
• holding timer (TIM) of the adjacency is set to 30 seconds
• if this neighbour has a defined priority, the PRTY field indicates it
• SNPA address of the neighbour system, if any, is in the first line of the ADDRESS
field
• type of the neighbour system is level 1 IS
• system ID of the neighbour is 222222222222
• the neighbour has two area addresses presented under the SNPA address
DN9812567 Issue: 14-1 © 2016 Nokia 173

If there are error codes in the output, you can get their explanations with the 4 command
of the CLNS Adjacency Finder menu.
If your network element is in the ES role, only the STATE, NEIGH, and
SYSTEM_ID_SET attributes are displayed.
12.7.2 CLNS destination information
You can display CLNS destination information with the D command in the CLNS Finder
menu. Entering '?', you get the CLNS Destination Finder menu shown below.
CLNS Destination managed object finder
? ..... menu / help
1 ..... Give a net and do search
2 ..... List nets
You can list the available NETs (NSAP without the N-selector) with the 2 command in the
CLNS Destination Finder menu. If your network element is in the IS role, the output could
look like this:
1. NET : 39246F00000116000000010001004043FF8026
2. NET : 01020304050607080910111213004043FF8026
3. NET : 39246F00000116000000010001004043FF8046
4. NET : 01020304050607080910111213004043FF8046
5. NET : 39246F00000116000000010001004043FF8005
6. NET : 01020304050607080910111213004043FF8005
7. NET : 39246F00000116000000010001004043FF80A4
8. NET : 01020304050607080910111213004043FF80A4
9. NET : 39246F00000116000000010001111312281381
10. NET : 01020304050607080910111213111312281381
11. NET : 39246F00000116000000010001131228121029
12. NET : 01020304050607080910111213131228121029
13. NET : 39246F00000116000000010001131228120187
14. NET : 01020304050607080910111213131228120187
15. NET : 39246F00000116000000010001004043FF8021
16. NET : 01020304050607080910111213004043FF8021
17. NET : 39246F00000116000000010001222222222222
18. NET : 01020304050607080910111213222222222222
19. NET : 01020304050607080910111213AA0004000E08
NUMBER OF NETS : 19
If your network element is in the ES role, there is no information of NETs.

You can display the destination information of a specific NET with the 1 command giving
the NET ID as the parameter.
1:01020304050607080910111213AA0004000E08;
THE SET OF THE ADJACENCY MANAGED OBJECT IDENTIFIERS :
NUMBER OF ELEMENTS : 1
INSTANCE TYPE : 0x3
INSTANCE ID 1 : 2
INSTANCE ID 2 : 2
COST OF LEAST COST PATH(S) : 0x14
174 © 2016 Nokia DN9812567 Issue: 14-1

The useful part in this output is the last line indicating the relative cost of this route.
12.8 Testing MAC Ethernet interface

12.8.1 Monitoring MAC statistics in the DMC bus based DX 200
network element
With the MAC Test toolset you can test the performance of the MAC interface, trace
reasons for transmission failures, and perform module tests on the COCEN software.
You can start the MAC Test toolset by choosing M in the O23MTS main menu.
You can display MAC interface statistics counters with the MC command of the MAC
Test toolset. The parameters of the MC command are the following:
• message bus address of the computer unit where the COCEN data terminal is
located
• plug-in unit index of the COCEN data terminal
You can list the computer units providing the MAC interface and their plug-in unit indexes
with the T command of the File Viewer tool as described in section Registered OSI
terminals. With the USI MML command you can retrieve the message bus address of
the computer unit (refer to the corresponding MML command descriptions).
For example, if you have an Ethernet data terminal in message bus address 0 and the
index of the data terminal is 7, you can display the statistical MAC interface counters of
this interface by entering the command:
ZMC:0,7;
Status answer received
MAC interface is ready.
Transmit statistics: 0000000000 MAC_not_ready indications sent
00 coll. 0000002164 01 coll. 0000000017 02 coll. 0000000023 03 coll.
0000000019
0000000000
0000000000
0000000000
Packets transmitted : 0000002257 Bytes transmitted : 0000180610
Aborted transmissions : 0000000000 Deferred transmissions : 0000000140
Carrier sense lost : 0000000002 CDH errors : 0000000000
Late collisions : 0000000000 FIFO underruns : 0000000000
Receive statistics:
Unicasts received : 0000000385 Multicasts received : 0000887261
Broadcasts received : 0000000000 Buffer overruns : 0000000000
Packets received : 0000887646 Bytes received : 0119179594
Filtered packets : 0000819556 Bad receive status : 0000000000
CRC errors : 0000000003 Frame alignment errors : 0000000001
Too short packets : 0000000000 Too long packets : 0000000000
DN9812567 Issue: 14-1 © 2016 Nokia 175

Corrupted rx buffer : 0000000000 Semaphore cntr overruns: 0000000000

Out of msg buffers : 0000000000 FIFO overruns : 0000000000
The 'MAC interface is ready' indication means that the situation is normal. Other possible
cases are as follows:
• no response at all
– indicates incorrect COCEN configuration
– check the hardware configuration with the WTI MML command
– check if the W1 strapping of the COCEN indicated in the MS field in the output of
the WTI command is the same as that presented in Data terminal strappings.
– if no driver code has been loaded for the COCEN, the lowest red LED of the
COCEN plug-in unit is blinking at the rate of 25 Hz
• not initialised message

– no initialisation command has been received (yet) from OSI management
– value is possible, for example, right after a system or unit restart, if the unit is in
the SE state, or if it has not yet found a working interface
• disabled (not ready) message

– a packet transmission failure has occurred after initialisation
– COCEN will not start looping through all interfaces; it sticks to the first one it
found to be working in the initialisation phase
It is not considered an error if no packets are received, so it does not cause a disabled
state.
In the case of 'not ready', the reason is also reported. The following table lists the error
cases and corresponding actions to get the interface back to the ready state.
Table 75 Ethernet interface error cases
Error Description Action
transmission The serial interface controller has not Check if the coaxial cable is connected
timeout been able to start packet properly to COCEN (if the COAX interface is
transmission. used) or to the external transceiver (if AUI is
used).
excessive Too many packets sent to the Ethernet Check if there are terminating resistors (50 Ω)
collisions have collided with packets sent from at both ends of the coaxial segment.
other units (or from the same unit).
carrier sense When packets were sent to the TX If TPI is used, check if the twisted pair cable is
lost output, they were not sensed on the connected properly to COCEN and to the
RX input simultaneously. Normally the repeater, and that the repeater is switched on.
signal is sent back to the RX input
If AUI is used, check if the external
from the external transceiver, or from
transceiver is properly connected. Check also
the repeater. The sent and received
if the 'SQE test' function on the transceiver is
signals are compared in order to
set ON (enabled).
detect if a collision has occurred.
176 © 2016 Nokia DN9812567 Issue: 14-1

The counters to keep an eye on to detect malfunctions are the following:
• Bad receive status

– check this if the transmissions have been successful but the station still does not
seem to receive any packets
– usually this is caused by the SQE test function of an external transceiver
connected to a repeater in LAN
– check if the SQE test dip switch on such transceivers is set to OFF
• Late collisions
– incremented if some station does not abide by the CSMA/CD protocol, or if two
stations transmitting simultaneously are too far apart
– make sure that the distances and the amount of segments in the LAN do not
exceed the limits defined in IEEE 802.3 standard
After reading the counters you can reset them with the command:
ZMCZ;
12.8.2 Monitoring MAC statistic in the PCI bus based DX 200

network element
With the ETHTST service terminal extension you can test the performance of the MAC
interface, trace reasons for transmission failures, and perform module tests on the
ETHLIB software in the PCI computer units.
The ETHTST service terminal extension has to be started in the computer unit which has
monitored the MAC interface.
You can display MAC interface statistics counters with the C command of the statistic
menu.
Init/Dev_reset/Tests/Statistic/Loopback_set/Quit/S
Counters/Reset_counters/View_mac_addr/set_Mac_addr/Dump/Parameters/Quit/C

tx buffer overflow = 0 rx buffer overflow = 0
fifo underrun = 0 fifo overrun = 0
out of msg buffers = 0 line not ready = 0
transmit collisions:
0:278 1:0 2:0 3:0 4:0 5:0 6:0 7:0
8:0 9:0 10:0 11:0 12:0 13:0 14:0 15:0
aborted transmissions = 0 deferred transmissions = 0
tx late collisions = 0 tx carrier sense lost = 0
tx cd heartbeat = 0
packets transmitted = 323 bytes transmitted = 15498
packets received = 552 bytes received = 40296
filtered packets = 0
unicasts received = 0 current unicast filter = 2
multicasts_received = 552 current multicast filter = 7
broadcasts received = 0 current broadcast filter = 5
crc errors = 0 frame alignment errors = 0
too_long_packets = 0 too_short_packets = 0
DN9812567 Issue: 14-1 © 2016 Nokia 177

More information on the MAC interface can be displayed with the V command that shows
the MAC address, connection type, operation mode, and validity of the link.
Counters/Reset_counters/View_mac_addr/set_Mac_addr/Dump/Parameters/Quit/V

MAC address: 00:40:43:F3:00:00
conn type: 100Base-TX half-duplex
operation mode: normal
link valid: Yes
The connection type shows the physical connection type.

The operation mode shows if the loopback mode is used. In normal mode, packets are
sent to network and in loopback mode, packets are sent back to the same interface
without going to the network.
If the link is 'not valid', the following table lists the error cases and corresponding actions
to get the interface back to the 'valid' state.
Table 76 Ethernet interface error cases
Error Description Action
carrier sense lost When packets were sent to the TX output, they were Check if the twisted pair
not sensed on the RX input simultaneously. cable is connected properly
Normally, the signal is sent back to the RX input to the computer unit and to
from the external transceiver, or from the repeater. the repeater, and if the
The sent and received signals are compared in repeater is switched on.
order to detect if a collision has occurred.
The counters to keep an eye on to detect malfunctions are as follows:
• Late collisions
– incremented if some station does not abide by the CSMA/CD protocol, or if two
stations transmitting simultaneously are too far apart
– make sure that the distances and the amount of segments in the LAN do not
exceed the limits defined in the IEEE 802.3 standard
After reading the counters, you can reset them with the R command:
Counters/Reset_counters/View_mac_addr/set_Mac_addr/Dump/Parameters/Quit/R
178 © 2016 Nokia DN9812567 Issue: 14-1

OSI Guide AS7-C and AS7-D switch block and connectors
13 AS7-C and AS7-D switch block and

connectors
13.1 AS7-C C105007
The figures below shows the AS7-C layout with location of switch block and connectors.
AS7-C layout
Figure 21 Connectors and micro switches of AS7-C
SW1 P5
P4
SW1
OFF ON
1 12
2 11
3 10
4 9
5 8
P1 6 7
DN03309124
Interchangeability code settings

The Interchangeability Switch Block consists of a 6–position DIP switch. This switch
contains the four interchangeability code bits. The interchangeability lines drive to '0'
when the switches are OFF.
g Note: 'OFF' is GND, 'ON' is VCC.
Table 77 SW1 switch settings.
Switch 1 Setting Meaning
1-12 OFF*) Interchangeability code bit 3 (MSB)
2-11 OFF*) Interchangeability code bit 2
DN9812567 Issue: 14-1 © 2016 Nokia 179

AS7-C and AS7-D switch block and connectors OSI Guide
Table 77 SW1 switch settings. (Cont.)
Switch 1 Setting Meaning
4-9 OFF*) Interchangeability code bit 0 (LSB)
5-8 OFF Not in use
6-7 OFF Not in use.
*) The first interchangeability code A corresponds to all switches OFF, after which the
settings start to roll for each interchangeability code change.
The table below presents the setting of the interchangeability code.
Table 78 Interchangeability code settings
ICC code Meaning
SW 1: 1–12 SW 1: 2–11 SW 1: 3–10 SW 1: 4–9 (LSB)

(MSB)
A OFF OFF OFF OFF
B OFF OFF OFF ON
C OFF OFF ON OFF
D OFF OFF ON ON
E OFF ON OFF OFF
F OFF ON OFF ON
G OFF ON ON OFF
H OFF ON ON ON
J ON OFF OFF OFF
K ON OFF OFF ON
L ON OFF ON OFF
M ON OFF ON ON
N ON ON OFF OFF
180 © 2016 Nokia DN9812567 Issue: 14-1

Table 78 Interchangeability code settings (Cont.)
ICC code Meaning
P ON ON OFF ON
R ON ON ON OFF
13.2 AS7-D C110791
The AS7-D has two vendors that differ in layout but are identical in function.
Advantech AS7-D
Figure 22 Connectors and micro switches of AS7-D
Interchangeability
P5 SWA
OFFON
ON
1 8
1
7
2 3 4
1 2
P4 3 6
SWB
4 5
1
SWA
P3 Bootsource
SWB
OFFON
ON
1 8
1
P2
7
2 3 4
2
3 6
4 5
P1
DN70542436
g Note: There are other pin headers on the board which are not presented in the figure.
Only the DIP switches which can be set by the user are described here. Do not make
any changes to other DIP switches or pin headers. Other DIP switches are used for
production, debugging and testing purposes only.
RadiSys AS7-D
DN9812567 Issue: 14-1 © 2016 Nokia 181

Figure 23 Connectors and micro switches of AS7-D
1
SWA
P5
P4
P3
Interchangeability
SWA
P2 OFFON
ON
8
1
1
2 3 4
2 7
3 6
4 5
P1
DN70542596
Interchangeability code settings

The Interchangeability Switch Block (SWA) consists of a 4–position DIP switch. This
switch contains the four interchangeability code bits. The interchangeability lines drive to
'0' when the switches are OFF.
g Note: 'OFF' is GND, 'ON' is VCC.
Table 79 Switch settings (SWA)
Switch Default Setting Meaning
1-8 OFF*) Interchangeability code bit 3 (MSB)
4-5 OFF*) Interchangeability code bit 0 (LSB)
*) The first interchangeability code A corresponds to all switches OFF, after which the
settings start to roll for each interchangeability code change.
The table below presents the setting of the interchangeability code.
182 © 2016 Nokia DN9812567 Issue: 14-1

Table 80 Interchangeability code settings
ICC code Setting
SW 1–8 (MSB) SW 2–7 SW 3–6 SW 4–5 (LSB)
A OFF OFF OFF OFF
B OFF OFF OFF ON
C OFF OFF ON OFF
D OFF OFF ON ON
E OFF ON OFF OFF
F OFF ON OFF ON
G OFF ON ON OFF
H OFF ON ON ON
J ON OFF OFF OFF
K ON OFF OFF ON
L ON OFF ON OFF
M ON OFF ON ON
N ON ON OFF OFF
P ON ON OFF ON
R ON ON ON OFF
Boot source selection

The boot source selection switch block (SWB) consists of a 4-position DIP switch. It is
only present in the Advantech variant of AS7-D.
1-8 OFF Not in use.
2-7 OFF Not in use.
3-6 OFF Not in use.
DN9812567 Issue: 14-1 © 2016 Nokia 183

4-5 ON Boot mode. Default setting. Do not change this

setting.
184 © 2016 Nokia DN9812567 Issue: 14-1

OSI Guide Parameters of X.25
14 Parameters of X.25
Data link level (OSI layer 2) parameters
Timer T1:
• time limit for the peer to acknowledge the receipt of the frame
• if the time limit is exceeded, the frame is retransmitted
• the time limit is given in seconds as all the time limit parameters
• the default value is 6 seconds
• refer to ITU-T Recommendation X.25 Interface between Data Terminal Equipment
(DTE) and Data Circuit-terminating Equipment (DCE) for terminals operating in the
packet mode and connected to public data networks by dedicated circuit (section
2.4.8.1)
Timer T2:
• time limit for the local entity to initiate the acknowledgement frame
• T2 is derived from T1 and cannot be configured by the user
• refer to ITU-T Recommendation X.25 (section 2.4.8.2)
Timer T3:
• time limit for idle channel state condition

• T3 is derived from T1 and cannot be configured externally
• refer to ITU-T Recommendation Book X.25 (section 2.4.8.3)
Bits In Frame:
• a maximum number of bits in an I frame

• the value is derived from the 'user data size' packet level parameter
Retry Count:
• a maximum number of times a frame is retransmitted

• the default value is 10
• refer to ITU-T Recommendation Book X.25 (section 2.4.8.4)
Window Size:
• a maximum number of frames to be transmitted without acknowledgement
Inter Frame Time Fill:
• contiguous flags transmitted between frames

• the default value for the flag sequence is 0111 1110 (7EH)
• the value can be changed to 1111 1111 (FFH)
– this can be necessary if the version of the HPC HDLC controller is V16
(HPC46400V16)
• refer to ITU-T Recommendation Book X.25 (section 2.2.11)
Line Down Timer:
DN9812567 Issue: 14-1 © 2016 Nokia 185

Parameters of X.25 OSI Guide
• time limit for the physical line to be down before the X.25 software reports an error
situation to the OSI management software
• the value is 20 seconds and it cannot be changed
Operating Mode:
• operating mode of the X.25 software

• the value is DTE for a line connected to the Public Packet Switching Network (PPSN)
• when using a direct line and/or modem eliminators, you must configure one side to
be a DTE and the other one a DCE
• the default value is DTE
Connection Mode:
• specifies when the link level connection is initialised

• the default value is poll_sabm
– poll_sabm is an active connection mode, in which the link layer tries to initialise
the link immediately after a startup (sending an SABM frame)
– wait_sabm is a passive connection mode, in which the software waits for an
SABM frame from the line
• the link is also initialised when network service user requests the first packet level
connection and the link level is not running
• the packet level is restarted immediately after the link level has been initialised
Modulo:
• specifies the modulo used in frame numbering (indicating the ordinance number of
the frame transmitted and the one that is expected next)
• the value is derived from the link level window size parameter
• refer to ITU-T Recommendation X.25 (section 2.3.2.2.1)
Packet level (OSI layer 3) parameters:

User Data Size:
• maximum number of user data bytes in a packet level data packet

• the possible values are from 1 to 1024
• the parameter does not restrict the size of N_DATA_REQUEST primitives
• if an NSDU exceeds the size limit, the more bit feature of the X.25 is used to carry
the data as one logical data unit to the peer entity
• refer to ITU-T Recommendation X.25 (section 4.3.2)
L3 Max Data With More:
• a maximum number of bytes in a sequence of data packets sent with the more bit
feature
– the more bit feature allows the delivery of a sequence of data packets to the peer
as one logical data unit; refer to ITU-T Recommendation X.25 (section 4.3.4)
– user can exceed the size limit set with the user data size parameter
186 © 2016 Nokia DN9812567 Issue: 14-1

OSI Guide Parameters of X.25
• the maximum value of the parameter is limited by the local implementation

– the DX 200 system allows the maximum value of 8192 bytes
• the default value is 2560 bytes
Window Size:
• a maximum number of packets sent or received without confirmation

• possible values are from 1 to 127
Modulo:
• specifies the packet level numbering modulo

• possible values are 8 and 128
Timer T20:
• time limit for restart after a PLP PDU issues a RESTART REQUEST
• possible values are from 1 to 4096 seconds
• refer to ITU-T Recommendation X.25 (Annex D table D-2/X25)
Timer T21:
• time limit for accepting a call after a PLP PDU issues a CALL REQUEST
Timer T22:
• time limit for reset after a PLP PDU issues a RESET REQUEST
Timer T23:
• time limit for call clearing after a PLP PDU issues a CLEAR REQUEST
Reset Retry Count:
• the maximum number of RESET packets transmitted before admitting failure

• refer to ITU-T Recommendation X.25 (Section 4.4.3.4)
Clear Retry Count:
DN9812567 Issue: 14-1 © 2016 Nokia 187

Parameters of X.25 OSI Guide
• the maximum number of CLEAR packets transmitted before admitting failure

• refer to ITU-T Recommendation X.25 (Section 4.1.8)
First PVC and last PVC:
• specify the logical channel numbers of the permanent virtual circuits

• possible values for logical channel numbers are from 1 to 4095
• the default value is 0 (no PVC channels in use)
• refer to ITU-T Recommendation X.25 (Annex A)
First Two-way Circuit and Last Two-way Circuit:
• specify the logical channel numbers of the two-way switched virtual circuits
• the default value is 0 (no SVC channels in use)
188 © 2016 Nokia DN9812567 Issue: 14-1

OSI Guide Parameters of CLNS
15 Parameters of CLNS
Parameters of both system types (ES and IS):
SystemId:
• length of system IDs in bytes within the routing domain

• every system ID within the routing domain must comply with this value
ManualAreaAddresses:
• a set of area addresses attached to a system, referring only to this system

• each system must have at least one area address
• the maximum number of area addresses in this set is limited with the
MaximumAreaAddresses parameter (see below)
g Note: The total amount of different manual area addresses in one area must not
exceed the value of the MaximumAreaAddresses parameter.
MaximumPDULifetime:
• a maximum value (in half seconds) allowed in the lifetime field of ISO 8473 data or
error report PDUs generated by the local system
• the value does not affect PDUs generated by other systems
• the value must be at least three times the network span (number of network
elements)
MaximumAreaAddresses:
• the maximum number of area addresses permitted for a system within this area
g Note: For correct operation, you must define the same parameter value for all the ISs
within the area.
EnableChecksum:
• defines if the generation of checksums in data PDUs is enabled
BackupTimer:
• time limit for accepting a new system configuration

• if the time limit is exceeded, the system is automatically initialised with the old
configuration
• very advisable to enable when configuring remotely with Virtual Terminal
IS parameters only:
MaximumPathSplits:
• a maximum number of paths between which the traffic to a destination is split
MinimumLSPTransmissionInterval:
DN9812567 Issue: 14-1 © 2016 Nokia 189

Parameters of CLNS OSI Guide
• a minimum interval between the transmissions of LSP PDUs
MaximumLSPGenerationInterval:
• a maximum interval between the regeneration of LSP PDUs
MinimumBroadcastLSPTransmissionInterval:
• a minimum interval between the transmissions of LSP PDUs on a broadcast circuit
CompleteSNPInterval:
• interval between generation of Complete SNP PDUs by a designated IS on a

broadcast circuit
OriginatingL1LSPBufferSize:
• the maximum size of level 1 LSP and SNP PDUs originated by the local system
MinimumLSPGenerationInterval:
• the minimum interval between the regeneration of LSP PDUs by the local system
PollESHelloRate:
• the value used for the SuggestedESConfigurationTimer in ISH PDUs when soliciting
the ES configuration
g Note: To be effective, this value must be lower than the DefaultESConfigurationTimer

value of the end systems (or the SuggestedESConfigurationTimer) within the LAN.
PartialSNPInterval:
• the minimum interval between sending Partial SNP PDUs
WaitingTime:
• the time for the local IS to stay in waiting state after running out of memory space for
LSP PDUs
• during waiting time, the local IS:
– ignores all received LSP PDUs
– declares itself unable to forward traffic by sending overload LSP PDUs to the
network
– continues to forward data PDUs (forwarding paths cannot be up to date)
dRISISHelloTimer:
• interval between generation of IIH PDUs by the designated IS in the LAN
g Note: This value must always be lower than any of the ISISHelloTimer values of any of
the broadcast linkages (both in this system and in other systems in the same LAN).
Parameters for all linkage types:

HoldingTimerMultiplier:
190 © 2016 Nokia DN9812567 Issue: 14-1

OSI Guide Parameters of CLNS
• used in deriving the holding time in ISO 9542 (ESIS) HELLO PDUs from the
configuration timer (IS or ES)
EnableChecksum:
• enables the generation of checksums in ISO 9542 PDUs
IS linkage parameters only (Broadcast and X.25):

ISConfigurationTimer:
• interval between reporting the configuration information to ESs with ISO 9542 (ESIS)
HELLO PDUs
SuggestedESConfigurationTimer:
• the value for the ISO 9542 SuggestedESConfigurationTimer

• the value is advertised in IS hellos generated by the local system
RedirectHoldingTime:
• holding time for ISO 9542 redirect PDUs generated by the local system
ISISHelloTimer:
• the interval between generating IIH PDUs

• also the interval between generating ISH PDUs when polling the ES configuration
DefaultMetric:
• defined for each circuit to indicate its throughput

• the lower the value the more favourable the linkage
ExternalDomain:
• if this value is TRUE, the normal transmission and reception of PDUs is prevented on
this circuit
IS broadcast linkage parameters only:

L1IntermediateSystemPriority:
• priority of becoming LAN Level 1 Designated Intermediate System
X.25 linkage parameters only:

InitialMinimumTimer:
• time for which a call remains connected after being established, irrespective of traffic
IdleTimer:
• time for which a call is permitted to remain idle before being released by the SNDCF
ES linkage parameters only:

DefaultESConfigurationTimer:
• default value for the ISO 9542 (ESIS) ES configuration timer
DN9812567 Issue: 14-1 © 2016 Nokia 191

Parameters of CLNS OSI Guide
• used when the ES has not received or has not accepted a suggested configuration
timer value from an IS
192 © 2016 Nokia DN9812567 Issue: 14-1

OSI Guide Counters of CLNS
16 Counters of CLNS
CLNS counters:
OctetsReceived:
• counts data octets in valid data packets received

– user data octets in rejected data packets are ignored
– user data octets in non-data packets are ignored
OctetsSent:
• counts data octets sent in data packets
SegmentsSent:
• counts data and error report NPDUs sent when segmentation has occurred
SegmentsReceived:
• counts data and error report NPDUs received prior to reassembly

– including those which can be subsequently discarded
SegmentsDiscarded:
• counts data and error report NPDUs discarded without being delivered to the
Network Service user or forwarded
• counts segments discarded for any reason except reassembly time expiration
NPDUsDiscarded:
• counts discarded data NPDUs except those discarded due to congestion
ErrorNPDUsReceived:
• counts received error report NPDUs addressed to the Network Service user
NPDUsDiscardedDueCongestion:
• counts data or error report PDUs discarded due to congestion

• incremented irrespective of the Error Report bit setting in the received PDU
SequenceNumberSkipped events:
• counts times when the sequence number of an LSP PDU is incremented by more
than one
OwnLSPPurged events:
• counts times when a zero aged copy of a system's own LSP PDU has been received
from some other system
– this represents an erroneous attempt to purge the local system's LSP PDU
MaxAreaAddressMismatch events:
DN9812567 Issue: 14-1 © 2016 Nokia 193

Counters of CLNS OSI Guide
• counts times when the MaximumAreaAddresses value of a received PDU has been
different from that of the receiving IS
ManualAddressDropped events:
• counts times when a manual area address assigned to the local system has been
ignored when computing area addresses because the number of area adresses
exceeds the MaximumAreaAddresses value
L1LSPDatabaseOverload events:
• counts times when the L1 state of the system has changed between 'On' and
'Waiting'
IdFieldLengthMismatch events:
• counts times when the SystemId field length value of a received PDU has been
different from that of the receiving IS
CorruptedLSPDetected events:
• counts times when a corrupted LSP PDU has been detected in memory
MaxSequenceNumberExceeded events:
• counts attempts to increment the sequence number of an LSP PDU beyond the
maximum sequence number
Counters for linkages:

RejectedAdjacency events:
• counts times when an attempt to create a new adjacency has been rejected, due to
the lack of resources
IntermediateSystemChange events:
• counts times when the local system either elects itself as or resigns from being the
LAN L1 Designated Intermediate System on the circuit
ControlPDUsSent:
• counts control PDUs (LSP, SNP) sent on this circuit
ControlPDUsReceived:
• counts control PDUs (LSP, SNP) received on this circuit
InitialisationFailed events:
• counts linkage initialisation failures
AdjacencyStateChange events:
• counts adjacency state changes
MaxAreaAddressesMismatch events:
• counts PDUs received with a different value for MaximumAreaAddresses from that of
the receiving IS
194 © 2016 Nokia DN9812567 Issue: 14-1

OSI Guide Counters of CLNS
IdFieldLengthMismatch events:
• counts PDUs received with a different value for IdFieldLength from that of the
receiving IS
ESReachabilityChanges:
• counts reachability changes of End Systems (according to the local system)
X.25CallsEstablished:
• counts successfully established X.25 virtual circuits
X.25CallsFailed:
• counts failures during X.25 call establishment
Invalid9542PDUsReceived:
• counts received ISO 9542 PDUs discarded due to ISO 9542

– PDU Header Error Detection
– Protocol Error Processing Function
ISReachabilityChanges:
• counts reachability changes of Intermediate Systems (according to the local system)
DN9812567 Issue: 14-1 © 2016 Nokia 195

OSI configuration sheets OSI Guide
17 OSI configuration sheets

X.25 data terminal configuration sheet (CONS, CLNS with X.25)
Fill in this sheet for each X.25 preprocessor.
1 Computer unit and index

(OMU / MSW / CHU)
2 Plug-in unit index/PCI device

indentification
3 Dual port memory address
4 Mode (DTE / DCE)
5 Name of X.25 parameter set
6 Range of logical channels
7 Link level window size
8 Packet level window size
9 Maximum user data on packet

level
10 SNPA address
(that is, DTE number)
11 Own SNPA address filled by

(AC25 / Network / Not filled)
12 Channel number
1 Location of the data terminal
2 Plug-in unit index of the data terminal
3 Default value suggested by the MML to be used
4 DTE / DCE
5 Parameter set defining the X.25 parameters
6 PVC channels and SVC channels; must be the same as in

peer X.25
7 Usually 7; 128 if extended numbering is used; must be the

same as in peer X.25
196 © 2016 Nokia DN9812567 Issue: 14-1

OSI Guide OSI configuration sheets
8 Usually 2; must be the same as in peer X.25
9 Usually 128; 1024 gives better performance in file transfer;

must be the same as in peer X.25
10 DTE address; from 1 to 15 digits
11 The Calling Address field of outgoing X.25 packets is filled
12 Defined either by the user or the system
Physical channel group configuration sheet (CONS)
1 Physical channel group name
2 Class (PVC/outgoing call routing)
3 Channel number and priority
Channel number and priority
1 Name of the channel group
2 Class of the channel group
• PVC: channel group identifies a PVC X.25 channel

• routing of outgoing X.25 calls: channel group prioritises
the use of the channels
3 Channel identifier and its priority within the channel group
• traffic is shared between the channels according to

their priority
CLNS configuration sheet (CLNS)

Fill in this sheet for each CLNS.
DN9812567 Issue: 14-1 © 2016 Nokia 197

1 CLNS name
2 CLNS role
3 NS user primary unit
4 MaximumPDULifetime
5 System identification
6 MaximumAreaAddresses
7 Manual area addresses
1 A string (maximum length is 8 characters) identifying the

CLNS
2 ES (End System) or IS (Intermediate System)
3 The unit where the active O54LRS is located
• normally the unit where the data terminals are located
4 Maximum lifetime (in half seconds) for a data PDU sent by

the local system
• the value has to be at least three times the network

span (number of network elements)
5 ID of the local system
• the length of the field has to be the same in every

system within the routing domain
• the identifier must be unique (for example, the C
number of the DX network element)
6 Maximum number of area addresses permitted to be

attached to this system
• the permitted values are 1, 2, or 3

• the value must be the same in every network system
within the area
7 Area addresses referring to the local system
• normally only one area address is needed
X.25 linkage configuration sheet (CLNS with X.25)

Fill in this sheet for each X.25 linkage.
1 Identification of linkage
198 © 2016 Nokia DN9812567 Issue: 14-1

2 Role of linkage
3 Computer unit type and index
4 Plug-in unit index
5 X.25 address/PVC number
1 ID number of linkage
2 ES / IS
3 Location of the data terminal providing the X.25 linkage
5 X.25 address of the remote end or PVC number of the

permanent connection
Broadcast linkage configuration sheet (CLNS)

Fill in this sheet for each broadcast (that is, LAN) linkage.
1 Identification of linkage
2 Role of linkage
3 Computer unit type and index
4 Plug-in unit index/PCI device

identification
5 IS priority
1 ID number of linkage
2 ES / IS
3 Location of the data terminal providing the broadcast

linkage
5 Only if the role is IS
Local X.25 NSAP configuration sheet (CONS)

SVC X.25 NSAP
1 Identification of NSAP
DN9812567 Issue: 14-1 © 2016 Nokia 199

2 DTE number
3 SPI
1 ID number given either by the system or the user
• the ID must be unique within the routing area
2 DTE number of the local X.25 interface
3 the Subsequent Protocol Identifier determines the type of

the CONS user
• for example, 01000000 for PAD
PVC X.25 NSAP
2 CHG
2 The channel group that contains the X.25 data terminal

providing the permanent virtual circuit
Local CLNS NSAP configuration sheet (CLNS)

Fill in this sheet for each CLNS NSAP.
2 NSEL
2 Selector value to be catenated to the NET string
• the default value is FF
NSAP ID and NSEL identify the connectionless network service user.
Local network address configuration sheet (CONS, CLNS)

Fill in this sheet for each network address.
200 © 2016 Nokia DN9812567 Issue: 14-1

1 Network address name
2 NSAP
3 NSAP
4 NSAP
5 NSAP
6 NSAP
7 NSAP
8 NSAP
9 NSAP
10 NSAP
Up to nine NSAPs may be attached to a single network address. This makes local OSI
applications reachable through different network interfaces.
Local application configuration sheet (CONS, CLNS)

Fill in this sheet for each address of each local OSI application.
1 Application entity name
2 Application process title type
3 Application entity qualifier
4 Application type
5 Computer unit and index
6 Family
7 Process or device index
8 Network address
9 P-selector
10 S-selector
11 T-selector
1 Name of the local OSI application
DN9812567 Issue: 14-1 © 2016 Nokia 201

2 Usually not needed
• only the Object Identifier type is supported
• used together with AET
4 Defines what OSI services the local application uses
5 Location of the local OSI application
6 Needed only for application types OTH and TSU
7 Process information is needed only for application types

OTH and TSU; device index is needed only for application
type VPP
8 Name of the network address used by the application
• The system uses the P-, S-, and T-selectors to

distinguish between the different OSI applications
using upper layer services. For example, a local Virtual
File Store must have a different selector value than a
Virtual Terminal session provider.
Remote X.25 NSAP configuration sheet (CONS)

Fill in this sheet for each remote X.25 NSAP.
2 DTE number
3 SPI
4 Channel group
2 DTE number of the remote X.25 interface
3 the Subsequent Protocol Identifier determines the type of

the CONS user
• for example, 01000000 for PAD
4 The channel group that contains the X.25 data terminals

providing routes for the remote end
Remote CLNS NSAP configuration sheet (CLNS)
202 © 2016 Nokia DN9812567 Issue: 14-1

Fill in this sheet for each remote CLNS NSAP.
2 IDP initial domain part
3 IDI initial domain identifier
4 DSP format identifier
5 DSP organisation identifier
6 DSP reserved field
7 DSP area
8 End system identifier
9 N-selector
2 AFI value defines how the NSAP address is structured
• possible values are 39 and 47

• other structures are given using the non-structured
NSAP type OTHER
3 IDI value contains usually a country code defined by ISO
• together with the AFI value, it defines the authority

responsible for the structure of the rest of the NSAP
and how the allocation of the values is decentralised
• for example, the value is 246 in Finland
4 DSP format identifier provided by the authority
5 Organisation identifier allocated by the authority
6 The user organisation decides the values of these fields
9 Identifies the CLNS user within the system
Remote network address configuration sheet (CLNS, CONS)

Fill in this sheet for each remote network address.
DN9812567 Issue: 14-1 © 2016 Nokia 203

1 Network address name
2 NSAP
3 Priority
4 NSAP
5 Priority
6 NSAP
7 Priority
NSAP
8 Priority
9 NSAP
10 Priority
11 NSAP
12 Priority
13 NSAP
14 Priority
15 NSAP
16 Priority
17 NSAP
18 Priority
• Up to nine NSAPs may be attached to a single network address. This makes remote
OSI applications reachable through different network interfaces.
• The network address can use NSAPs according to user-defined priorities.
Remote application configuration sheet (CONS, CLNS)

Fill in this sheet for each address of each remote OSI application.
1 Application name
2 Application process title type
3 Application entity qualifier
204 © 2016 Nokia DN9812567 Issue: 14-1

4 Application type
5 Network address
6 P-selector
7 S-selector
8 T-selector
1 Name of the remote OSI application
• only Object Identifier type is supported
• used together with AET
4 Defines what OSI services the remote application uses
• if the OSI connection is established from the DX, the

system requires the initiator and responder
applications to have the same type
5 Name of the network address used by the application
• The system uses the P-, S-, and T-selectors to

distinguish between different OSI applications using
upper layer services. For example, an FTAM Virtual
File Store must have a different selector value than an
application using CMIP services.
DN9812567 Issue: 14-1 © 2016 Nokia 205

DX 200 and standard FTAM error codes OSI Guide
18 DX 200 and standard FTAM error codes
18.1 DX 200 FTAM error codes
Error codes of local VFS:
1 Responder error (unspecific)
7 Initiator error (unspecific)
9 Temporary insufficiency of resources
10 Access request violates VFS security
11 Access request violates local security
30 FTAM process failed to open a local file
31 FTAM process failed to close a local file
32 Failure in reading a local file
33 Failure in writing a local file
34 Failure in reading attributes of a local file
35 Failure in deleting a local file
36 Directory listing from local virtual file store fails
37 Requested file operation is going on
38 Local file cannot be deleted
39 Application entity title not found
40 This protocol primitive or message is not allowed in this

state
41 Remote entity aborted connection
42 Abnormal termination of connection
43 Remote file open failed
44 This FTAM document type is not supported
45 FTAM process received negative f data end indication
46 FTAM process received f cancel indication
206 © 2016 Nokia DN9812567 Issue: 14-1

OSI Guide DX 200 and standard FTAM error codes
47 FTAM process received negative f transfer end

confirmation
48 FTAM process received negative f close confirmation
49 FTAM process received negative f deselect confirmation
50 Timer expired when an ooftam process was waiting for a

local file operation
18.2 Standard FTAM error codes
Key to the tables in this section:
Error types
0 Informative
1 Transient error
2 Permanent error
Observer, Source
0 No categorisation possible
1 Initiating file service user
2 Initiating file protocol machine
3 Service supporting the file protocol machines
4 The responding file protocol machine
5 The responding file service user (file system)
Protocol and supporting service-related diagnostics

Table 81 FTAM error codes 1000–1017
Type Identifier Observer Source Reason
2 1000 2 4 Conflicting parameter values
4 2 Conflicting parameter values
2 1001 2 4 Unsupported parameter values
4 2 Unsupported parameter values
DN9812567 Issue: 14-1 © 2016 Nokia 207

Table 81 FTAM error codes 1000–1017 (Cont.)
2 1002 2 4 Mandatory parameter not set
4 2 Mandatory parameter not set
2 1003 2 4 Unsupported parameter
4 2 Unsupported parameter
2 1004 2 4 Duplicated parameter
4 2 Duplicated parameter
2 1005 2 4 Illegal parameter type
4 2 Illegal parameter type
2 1006 2 4 Unsupported parameter types
4 2 Unsupported parameter types
2 1007 2 4 FTAM protocol error (unspecific)
4 2 FTAM protocol error (unspecific)
2 1008 2 4 FTAM protocol error, procedure error
4 2 FTAM protocol error, procedure error
2 1009 2 4 FTAM protocol error, functional unit error
4 2 FTAM protocol error, functional unit error
2 1010 2 4 FTAM protocol error, corruption error
4 2 FTAM protocol error, corruption error
2 1011 2-4 3 Lower layer failure
1, 2 1012 3 2 Lower layer addressing error
1, 2 1013 0-5 0-5 Timeout
1, 2 1014 0-5 0-5 System shutdown
2 1015 2 4 Illegal grouping sequence
4 2 Illegal grouping sequence
2 1016 2 4 Grouping threshold violation
208 © 2016 Nokia DN9812567 Issue: 14-1

4 2 Grouping threshold violation
2 1017 4 2 Specific PDU request inconsistent with current

request access
Association-related diagnostics
2 2000 3, 5 1 Association with user not allowed
2 2001 1 (not assigned)
2 2002 4, 5 1 Unsupported service class
0, 2 2003 4, 5 1 Unsupported functional unit
0, 1 ,2 2004 5 1 Attribute group error (unspecific)
2 2005 5 1 Attribute group not supported
0, 2 2006 5 1 Attribute group not allowed
0, 2 2007 5 1 Bad account
0, 1, 2 2008 4 1 Association management (unspecific)
2 2009 4 1 Association management (bad address)
1, 2 2010 4 1 Association management (bad account)
0, 2 2011 4 2 Checkpoint window error (too large)
0, 2 2012 4 2 Checkpoint window error (too small)
0, 2 2013 4 2 Checkpoint window error (unsupported)
0, 1, 2 2014 3 2 Communications QoS not supported
2 2015 4, 5 1 Initiator identity unacceptable
0 2016 4 1 Context management refused
0 2017 4 1 Rollback not available
0 2018 5 1 Contents type list cut by responder
DN9812567 Issue: 14-1 © 2016 Nokia 209

0 2019 3, 5 1 Contents type list cut by Presentation service
2 2020 5 1 Invalid file system password
2 2021 4, 5 1 Incompatible service classes
Selection-related diagnostics
1, 2 3000 5 5 Filename not found
1, 2 3001 5 5 Selection attributes do not match
2 3002 5 5 Initial attributes not possible
2 3003 5 Bad attribute name
1, 2 3004 4 5 File does not exist
1, 2 3005 5 5 File already exists
1, 2 3006 5 5 File cannot be created
1, 2 3007 5 5 File cannot be deleted
0, 2 3008 5 5 Concurrency control not available
0, 2 3009 5 5 Concurrency control not supported
0, 2 3010 5 5 Concurrency control not possible
0, 1 3011 5 5 More restrictive lock
1, 2 3012 5 5 File busy
1, 2 3013 5 5 File not available
0, 1, 2 3014 5 5 Access control not available
0, 1, 2 3015 5 5 Access control not supported
0, 1, 2 3016 5 5 Access control inconsistent
0 3017 4, 5 4, 5 Filename truncated
210 © 2016 Nokia DN9812567 Issue: 14-1

0 3018 5 5 Initial attributes altered
1, 2 3019 5 1 Bad account
0 3020 5 5 Override selected existing file
0 3021 5 5 Override deleted file recreated with old

attributes
0 3022 5 5 Create override deleted and recreated file with

new attributes
1, 2 3023 5 5 Create override not possible
1, 2 3024 5 5 Ambiguous file specification
2 3025 5 1 Invalid create password
2 3026 5 1 Invalid delete password on override
2 3027 5 1 Bad attribute value
2 3028 5 1 Requested access violates permitted actions
2 3029 5 1 Functional unit not available for requested

access
0, 1 3030 5 5 File created but not selected
File management-related diagnostics

Type Identifier Ibserver Source Reason
0, 1, 2 4000 5 5 Attribute does not exist
1, 2 4001 5 5 Attribute cannot be read
1, 2 4002 5 5 Attribute cannot be changed
1, 2 4003 4, 5 4, 5 Attribute not supported
2 4004 4 2 Bad attribute name
2 4005 5 1 Bad attribute value
0 4006 5 5 Attribute partially supported
DN9812567 Issue: 14-1 © 2016 Nokia 211

Type Identifier Ibserver Source Reason
0 4007 5 5 Additional set attribute value not distinct
Access-related diagnostics
1, 2 5000 5 1 Bad FADU (unspecific)
2 5001 5 1 Bad FADU - size error
2 5002 5 1 Bad FADU - type error
2 5003 5 1 Bad FADU - poorly specified
2 5004 5 1 Bad FADU - bad location
0, 1 5005 5 5 FADU does not exist
0, 1, 2 5006 5 5 FADU not available (unspecific)
1, 2 5007 5 5 FADU not available for reading
1, 2 5008 5 5 FADU not available for writing
1, 2 5009 5 5 FADU not available for location
1, 2 5010 5 5 FADU not available for erasure
1, 2 5011 5 5 FADU cannot be inserted
1, 2 5012 5 5 FADU cannot be replaced
0, 1, 2 5013 5 5 FADU cannot be located
0, 1, 2 5014 3 1 Bad data element type
2 5014 5 2, 4 Bad data element type
1, 2 5015 5 5 Operation not available
1, 2 5016 5 5 Operation not supported
0, 2 5017 5 1 Operation inconsistent
0, 1, 2 5018 5 5 Concurrency control not available
212 © 2016 Nokia DN9812567 Issue: 14-1

0, 2 5019 5 5 Concurrency control not supported
0, 2 5020 5 1 Concurrency control inconsistent
0, 1, 2 5021 5 5 Processing mode not available
0, 2 5022 5 5 Processing mode not supported
0, 2 5023 5 1 Processing mode inconsistent
0, 2 5024 5 5 Access context not available
0,2 5025 5 5 Access context not supported
Access-related diagnostics
1, 2 5026 5 5 Bad write (unspecific)
1, 2 5027 5 5 Bad read (unspecific)
0, 1, 2 5028 5 5 Local failure (unspecific)
0, 1, 2 5029 5 5 Local failure - file space exhausted
0, 1, 2 5030 5 5 Local failure - data corrupted
0, 1, 2 5031 5 5 Local failure - device failure
2 5032 5 5 Future file size exceeded
0 5034 5 5 Future file size increased
0, 2 5035 5 1 Functional unit invalid in processing mode
0, 2 5036 5 1 Contents type inconsistent
0 5037 1 5 Contents type simplified
0 5038 5 5 Duplicate FADU name
1, 2 5039 2 4 Damage to select/open regime
1, 2 5039 4 2 Damage to select/open regime
DN9812567 Issue: 14-1 © 2016 Nokia 213

1, 2 5040 5 5 FADU locking not available on file
1, 2 5041 5 5 FADU locked by another user
214 © 2016 Nokia DN9812567 Issue: 14-1

OSI Guide Notices, disturbances, and alarms initiated by the DX
200 OSI software
19 Notices, disturbances, and alarms initiated by

the DX 200 OSI software
The notifications related to the DX 200 OSI software are presented in the following three
tables. The first table contains notices which help you to operate the DX 200 OSI
software. The disturbances, presented in the second table, are to be taken more
seriously, and the alarms presented in the third table usually require further actions. If
any of these alarms is set on, try to figure out the reason and act according to the alarm
instructions.
Table 87 Notices initiated by DX 200 OSI software
Nr Alarm text Description Action
2 OSI INCOMING An incoming OSI connection cannot The situation may be due to a lack of
CALL ROUTING be established in the exchange. available addresses or available
FAILED resources. Check the reason code
and act according to the alarm
description.
9 OSI FORCED OSI System Management is forced Go through the alarm history and
CONNECTION to clear OSI connection due to the find out what has caused the change
CLEARING changes in availability of the OSI in the availability of the OSI
resources. resources.
12 X.25 CALL X.25 connection attemp to a remote Check the clearing codes and try to
ESTABLISHMENT system fails. find the reason for call failing.
FAILED
Table 88 Disturbances initiated by DX 200 OSI software
1004 COMMUNICATION The partner program block Either ODCMAN or OMGISI is

ERROR BETWEEN does not reply to the message unable to communicate with
PROGRAM BLOCKS sent to it within the specified O7AMAN. Check the state
time limit, or the received information of the units where these
reply is erroneous. program blocks are located.
1018 PROGRAM BLOCK The partner program block O7MANA is unable to communicate
COMMUNICATION does not respond within the with its pair or with O7AMAN. Check
ERROR specified time to the message the state information of the units
sent to it, or the reply is faulty. where these program blocks are
located.
1033 OSI CLNS The configuration of the CLNS The reason is either the expiration of
CONFIGURATION failed. the CLNS parameter acceptance
FAILED timer or errors in CLNS parameter
values. The system will
automatically restore the previous
DN9812567 Issue: 14-1 © 2016 Nokia 215

Notices, disturbances, and alarms initiated by the DX OSI Guide
200 OSI software
Table 88 Disturbances initiated by DX 200 OSI software (Cont.)
values for CLNS. If the configuration

failed due to the erroneous
parameters, check the values again
with the QEI command. One
possible reason is that the role of the
CLNS object is wrong.
1034 MAXIMUM The CLNS protocol sequence The reason for the protocol
SEQUENCE NUMBER number has exceeded its sequence number overflow is
OF OSI CLNS maximum value. probably a badly behaving IS router.
EXCEEDED Connectionless Network service is
out of service the next 20 minutes,
so neither routing nor user data
transfer is possible. This holding
time ensures that the reinitialisation
of the protocol sequence number
does not disturb the functioning of
other network elements.
1065 DISK UPDATE The modification of the central Check the state of the OMU
FAILURE memory has not been computer unit disks.
updated on the disk. The files
have been transferred into the
central memory.
1260 X.25/ETHERNET DATA A spontaneous request to Go through the alarm history and
TERMINAL reinitialise a plug-in unit find out what has caused the
SPONTANEOUS causes the System reinitialisation of the plug-in unit.
RESTART Management to cut all OSI Check also the log file of the
connections relayed through computer unit where the plug-in unit
the plug-in unit. The cut is is located.
followed by a reinitialisation of
the plug-in unit.
1261 OSI CHANNEL The Channel Group becomes The Channel Group becoming
GROUP unavailable and this means unavailable is caused by the fact
UNREACHABLE that the remote applications, that the group contains no available
whose labels use unavailable channels. Go through the alarm
Channel Groups, become history and find out what has caused
unreachable. the change in the availability of the
OSI resources.
1262 OSI SERVICE An OSI program block restart The memory allocation situation of
PROVIDER RESET is caused by an internal fault the program block prior to the restart
situation, for example, when is written into the log where the
the memory space allocated centralised part of the OSI
to the program block has been administration is located.
exceeded.
216 © 2016 Nokia DN9812567 Issue: 14-1

200 OSI software
Table 88 Disturbances initiated by DX 200 OSI software (Cont.)
1263 OSI FAMILY An OSI program block has The sender of the message is
INTERFACE ERROR received a message that has written into the log of the unit that
not been specified in its accommodates the centralised part
interface. of the OSI administration.
1264 OSI INCOMING CALL A call has been sent from the Check the DTE number and the
DENIED network to a local Application interface ID. If the connection
with incoming call denial. attempt is repeated 10 times within 5
minutes, an alarm 2265 is set.
Table 89 Alarms initiated by DX 200 OSI software
2012 ERROR IN FILE File opening has failed. The Contact Nokia Customer Service.
OPENING process that set the alarm can
neither use the file concerned
nor function in a normal
manner.
2060 CENTRAL MEMORY Error in the files of the central During the update of the files OETFIL,
FILE ERROR memory. ATFILE, OPHX25, OPCFIL, or
OCGFIL an acknowledgement with
the wrong status is received from the
pair unit. Find the file and the record
and message ID, and try to locate the
erroneous field. If no obtainable fault
seems to exists, rearrange the file
operation and save the message
trace of the O7MANA program block
on the spare and active side. Submit
the trace information to Nokia
Customer Service
2065 FILE CONFLICT While a program block is The contents of the files OETFIL,
ERROR updating a file or performing ATFILE, OPHX25, OPCFIL, or
check-ups associated with an OCGFIL differs in the main memory of
update, a difference is the active and spare side of the
discovered in the data of the logical CM. Find the file and record ID
files of the two computer units. and compare the contents on both
sides. Correct the contents of the
corrupted file by restarting the unit.
Rearrange the file operation and save
the message trace of the O7MANA
program block on the spare and
active side. If the alarm is set, submit
Customer Service.
DN9812567 Issue: 14-1 © 2016 Nokia 217

200 OSI software
Table 89 Alarms initiated by DX 200 OSI software (Cont.)
2137 PLUG-IN UNIT The locations of signalling link Check the strappings of the plug-in
LOCATION ERROR terminals do not correspond to units against the hardware definition
the set-up of the addresses, or (WTI command).
several terminals have been
placed in the same address.
2138 PLUG-IN UNIT A checksum error has been The file containing the software
SOFTWARE detected in the software package is corrupted. Restart the unit
PACKAGE CHECK package loaded into the where the plug-in unit is located.
SUM ERROR program memory (RAM Obtain a new file image if necessary.
memory) of a plug-in unit on
the DMC bus. The error was
detected by the plug-in unit's
checksum counting function.
2165 EXCESSIVE Error ratio counter alarm Use a protocol analyser (for example,
REJECTIONS OF indicates that too many Sniffer) to locate the source of the
OSI CLNS (excluding congestion) protocol distorted protocol messages.
PROTOCOL DATA messages related to the CLNS
UNITS have been discarded during the
last monitoring time interval.
2166 CORRUPTED OSI Link state information protocol Use a protocol analyser (for example,
CLNS LINK STATE message related to the CLNS Sniffer) to locate the source of the
PROTOCOL DATA routing is considered to be distorted protocol messages.
UNIT corrupted. Local routing
database has been initialised
due to this error. This can
temporarily decrease the
quality of the CLNS transfer
service.
REJECTIONS OF indicates that too many link Sniffer) to locate the source of the
OSI CLNS LINK state information protocol distorted protocol messages.
STATE PDU messages related to the CLNS
routing were discarded during
the last monitoring time
interval. State information of
the remote nodes represented
by the discarded messages
has been reinitialised in local
routing database. This can
quality of CLNS transfer
service.
REJECTIONS OF indicates that too many Sniffer) to locate the source of the
OSI CLNS 9542 (excluding congestion) ES/IS distorted protocol messages.
PDUS protocol messages were
discarded during the last
218 © 2016 Nokia DN9812567 Issue: 14-1

200 OSI software
monitoring time interval. This

can temporarily decrease the
service.
2169 OSI CLNS LINK The maximum size of CLNS Contact Nokia Customer Service.
STATE PDU LEVEL routing database has been
1 DATABASE exceeded. More space is
OVERLOAD received when routing state
information is out-dated and
removed from the local
database. This can temporarily
decrease the quality of the
CLNS transfer service.
2171 NO USER FOR OSI Local OSI application cannot Check the state information of the
CLNS use CLNS because there is no computer units where alternative
CLNS providing the transport transport service providers are
service. This can temporarily located. Change the unit state
decrease the quality of the information so that at least one of the
CLNS transfer service. units where a transport service
provider is located changes its state
to active.
2174 OSI CLNS SERVICE CLNS is out of service. This Check the command calendar for the
NOT AVAILABLE can be a consequence of failed last configuration changes. One
CLNS configuration or local possible reason is that the role of the
procedure error. This can CLNS is wrong. If no apparent reason
temporarily decrease the for erroneous behavour is found,
quality of the CLNS transfer contact Nokia Customer Service.
service.
2175 OSI CLNS LINKAGE One of the CLNS linkages is Check if there are any alarms 2262
NOT AVAILABLE out of service. This can be a related to the data terminal. In the
consequence of failed linkage case of X.25 linkage, check the
or data terminal configuration administrative and functional state of
or local procedure error. This the physical channel. Check also if
can temporarily decrease the the DTE number related to the ISO/IP
quality of the CLNS transfer X.25 SNDCF configuration is valid at
service. both ends. If no apparent reason for
erroneous behavour is found, contact
2176 NO CLNS OBJECT CLNS is out of service. There Interrogate CLNS information with the
are no CLNS objects, all CLNS QEI command and correct the
IN OSI DATABASE
objects are locked, or the situation.
FOR
unlocked CLNS objects have a
INITIALIZATION
wrong role. This can
quality of the CLNS transfer
service.
DN9812567 Issue: 14-1 © 2016 Nokia 219

200 OSI software
2177 DISCARDED A manual area address is Some network elements have too
MANUAL AREA removed from use by the CLNS many manual area addresses. Try to
ADDRESS OF OSI because the maximum number locate the source of extra manual
CLNS of area addresses has been area addresses starting from the local
exceeded. This is probably node and continuing with the protocol
caused by an erroneous area analyser (for example, Sniffer).
address configuration. Due to
this error some of the network
elements may become
unreachable.
2178 MISMATCH OF Local CLNS has received a The value for maximum area address
MAXIMUM AREA protocol message where the count differs in some network
ADDRESS OF OSI maximum area address count elements. Try to locate the source of
CLNS differs from the own maximum the different maximum area address
area address count. This is values starting from the local node
probably caused by erroneous and continuing with the protocol
configuration information. Due analyser (for example, Sniffer).
to this error some of the
network elements may become
unreachable.
2179 INCOMPATIBLE Local CLNS has received a Some network elements have wrong
PROTOCOL protocol message that has protocol version information. Try to
VERSIONS OF OSI wrong version information. This locate the source of protocol
CLNS is probably caused by messages with wrong version
erroneous configuration information starting from the local
information. Due to this error node and continuing with the protocol
some of the network elements analyser (for example, Sniffer).
may become unreachable.
2181 MISMATCH OF Local CLNS has received a Some network elements have system
SYSTEM ID protocol message where the identifiers of different length. Use a
LENGTH OF OSI system identification length protocol analyser (for example,
CLNS differs from the length of the Sniffer) to locate the source of
own system identifier. This is protocol messages with wrong length
probably caused by erroneous information.
configuration information. Due
to this error some of the
unreachable.
2182 MISMATCH OF Local CLNS has received a Some network element has a set of
AREA ADDRESS OF protocol message that has an manual area addresses that has no
OSI CLNS area address that is not common manual area address with
registered in the local the local node. Try to locate the
configuration. This is probably source of the unknown manual area
caused by erroneous addresses starting from the local
configuration information. Due node and continuing with the protocol
to this error some of the analyser (for example, Sniffer).
unreachable.
220 © 2016 Nokia DN9812567 Issue: 14-1

200 OSI software
2183 REJECTED OSI C The creation of adjacency The creation of adjacency information
information to local to local configuration failed due to the
LNS ADJACENCY
configuration failed due to the lack of available resources. This is
DUE TO LACK OF
lack of available resources. probably caused by erroneous
RESOURCES
This is probably caused by configuration. This can temporarily
erroneous configuration. This decrease the quality of CLNS transfer
can temporarily decrease the service.
service.
2184 OSI CLNS Management information of If the error is a database error, use
MANAGEMENT OSI Environment Support the QB, QD, QL and QE MML
INFORMATION Services is corrupted. commands to correct the corrupted
CORRUPTED information. When you correct the
information, you may have to delete
the information and create it again.
If the error is a work file error, use the
QET MML command to restart the
connectionless network service. In
addition, lock and unlock all the
linkages to be used. If the desired
effect is not achieved, restart the
object unit of the alarm.
2185 ROUTING OF OSI An outgoing OSI connection The situation may be due to a lack of
OUTGOING CALL cannot be established from the available addresses, a temporary
FAILED exchange. overload, or a lack of transmission
paths. Check the reason code and act
according to the alarm description.
2260 FILE UPDATING An updating error occurred in The updating of the file OSCFIL,
ERROR the updating operation of a file OETFIL, ATFILE, OPHX25, OPCFIL,
located outside the program or OCGFIL failed. Find the file and
block. record ID. Rearrange the file
operation and save the message
trace of the O7MANA program block
on the spare and active sides. Submit
Customer Service.
2261 CONFLICT There are inconsistencies There is an inconsistency between

BETWEEN TWO between the data of two files. the files OSCFIL and OPCFIL,
FILES OSCFIL and ATFILE, ATFILE and
OPCFIL, or OPCFIL and OCGFIL.
Find the file and record IDs and try to
locate the erroneous field. If there
seems ro be no apparent fault ,
rearrange the file operation and save
the message trace of the O7MANA
program block on the spare and
DN9812567 Issue: 14-1 © 2016 Nokia 221

200 OSI software
active sides. Submit the trace

information to Nokia Customer
Service.
2262 OSI SUBNETWORK If the initialisation of a plug-in The fault in the OSI subnetwork
INTERFACE OUT unit is unsuccessful, or the interface may be corrected by a
OF ORDER plug-in unit sends the switchover or by establishing the
information that the physical connections via other plug-in units in
connection is lost, it is not the channel group of the plug-in unit.
possible to establish OSI The reason for the plug-in unit
connections via the plug-in unit initialisation error can be found in the
in question. The system will not files MUFILE, ATFILE/ PIPCMI,
attempt to use the plug-in unit OPCFIL, and OPHX25. The reason
when establishing connections. for the physical connection to be lost
can be found in the cabling.
The system should cancel the
alarm automatically when the
fault has been corrected. In
some cases, however, the
alarm is not cancelled by the
system, and it should be
cancelled manually if the
interface works properly.
2263 OSI An outgoing OSI connection The situation maybe due to a lack of
OUTGOINGCALL cannot be established from the available addresses, a temporary
FAILED exchange. overload, or a lack of transmission
path. The diagnostics table indicates
Arisen from an error in
the cause.
theinternal functioning..
2264 ADMINISTRATIVE The OSI administration files Identify the corrupted files and contact
FILES CORRUPTED contain contradictory record Nokia Customer Service.
references. The situation has
arisen from an error in the
internal functioning.
2265 POSSIBLE During a certain period of time Go through the alarm history and find
SECURITY there has been several all alarms with number 1264. Pick the
VIOLATION attempts to establish an X.25 alarms with an identical interface
connection to the exchange number and retrieve the calling DTE
from a source that is not number information.
authorised to do so.
2735 EVENT BUFFER This alarm maybe issued if the Check the the connection to the
OVERFLOW connection to OMC is down, OMC: by giving the MML command
the queue is blocked, or the QLI, check the state of the OSI link. It
OMC cannot recieve any should be in WO-EX state. If the state
events. is not WO-EX, it means that X.25( or
LAN) connection doesn't fuction as it
SHOUL. Check that OSI connection
has been created successfully.
222 © 2016 Nokia DN9812567 Issue: 14-1

OSP Platform For GSM/EDGE BSS: OSI Guide

Uploaded by

Copyright:

Available Formats

OSP Platform For GSM/EDGE BSS: OSI Guide

Uploaded by

Document Information

Original Description:

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

OSP Platform For GSM/EDGE BSS: OSI Guide

Uploaded by

Copyright:

Available Formats

OSP Platform for GSM/EDGE

Copyright © 2016 Nokia. All rights reserved.

f Important Notice on Product Safety

2 © 2016 Nokia DN9812567 Issue: 14-1

Summary of changes ...................................................................11

1 DX 200 OSI environment............................................................. 12

2 Example configuration of an ES with LAN interface.....................46

3 Example configuration of an IS with LAN and X.25 interfaces.....54

4 Example configuration of an ES with LAN and X.25 interfaces... 73

5 Example configuration of OSI over TCP/IP interface................... 82

DN9812567 Issue: 14-1 © 2016 Nokia 3

5.2 OSI over TCP/IP - summary of configuration steps..................... 82

6 Defining local DX 200 OSI environment.......................................85

7 Defining remote OSI environment..............................................101

8 Verifying your OSI configuration................................................. 110

9 OSI troubleshooting................................................................... 123

10 Common OSI configuration mistakes.........................................130

11 Defining and starting an OSI measurement............................... 146

12 Using O23MTS service terminal extension................................ 148

4 © 2016 Nokia DN9812567 Issue: 14-1

12.2 Monitoring status information of X.25.........................................153

13 AS7-C and AS7-D switch block and connectors........................ 179

14 Parameters of X.25.................................................................... 185

15 Parameters of CLNS.................................................................. 189

16 Counters of CLNS...................................................................... 193

17 OSI configuration sheets............................................................196

18 DX 200 and standard FTAM error codes....................................206

DN9812567 Issue: 14-1 © 2016 Nokia 5

19 Notices, disturbances, and alarms initiated by the DX 200 OSI

6 © 2016 Nokia DN9812567 Issue: 14-1

DN9812567 Issue: 14-1 © 2016 Nokia 7

8 © 2016 Nokia DN9812567 Issue: 14-1

Table 37 Remote X.25 NSAP configuration sheet for IS2 PAD.........................62

DN9812567 Issue: 14-1 © 2016 Nokia 9

Table 73 Incoming call error cases..................................................................140

10 © 2016 Nokia DN9812567 Issue: 14-1

Changes made between issues 14-1 and 14-0

Changes made between issues 14-0 and 13-0

Changes made between issues 13-0 and 12–0

DN9812567 Issue: 14-1 © 2016 Nokia 11

1 DX 200 OSI environment

• FTAM for file transfer

12 © 2016 Nokia DN9812567 Issue: 14-1

Figure 1 DX 200 OSI stack

FTAM VT CMISE SMRSE

LAN X.25 LAN

Configuration command groups

DN9812567 Issue: 14-1 © 2016 Nokia 13

Figure 2 MML command groups for creating an OSI configuration

1.1 Required OSI services

14 © 2016 Nokia DN9812567 Issue: 14-1

Virtual PAD Printer

Short Message Service

Transport Layer Service

1.2 OSI vendors involved

• the network elements have an interoperable FTAM implementation.

DN9812567 Issue: 14-1 © 2016 Nokia 15

Table 1 Examples of interoperability between DX 200 OSI products and some

DX200 A DX200 A DX200C

TP class4 Transport layer TP class0 "RFC1006"

LLC X.25packetlevel Ethernetinterface