ewsd x25 sys admin

Nonstandard MaintenanceNode

X.25 System Administration

A30828-X1150-N60-2-7620

2 A30828-X1150-N60-2-7620

X.25 System Administration Nonstandard MaintenanceNode

f Important Notice on Product SafetyElevated voltages are inevitably present at specific points in this electrical equipment. Some of theparts may also have elevated operating temperatures.Non-observance of these conditions and the safety instructions can result in personal injury or in prop-erty damage.Therefore, only trained and qualified personnel may install and maintain the system.The system complies with the standard EN 60950 / IEC 60950. All equipment connected has to complywith the applicable safety standards.

The same text in German:Wichtiger Hinweis zur ProduktsicherheitIn elektrischen Anlagen stehen zwangslufig bestimmte Teile der Gerte unter Spannung. Einige Teileknnen auch eine hohe Betriebstemperatur aufweisen.Eine Nichtbeachtung dieser Situation und der Warnungshinweise kann zu Krperverletzungen undSachschden fhren.Deshalb wird vorausgesetzt, dass nur geschultes und qualifiziertes Personal die Anlagen installiert undwartet.

Das System entspricht den Anforderungen der EN 60950 / IEC 60950. Angeschlossene Gertemssen die zutreffenden Sicherheitsbestimmungen erfllen.

Trademarks:All designations used in this document can be trademarks, the use of which by third parties for theirown purposes could violate the rights of their owners.

Copyright (C) Siemens AG 2002-2002.Issued by the Information and Communication Networks GroupHofmannstrae 51D-81359 Mnchen

Technical modifications possible.Technical specifications and features are binding only insofar asthey are specifically and expressly agreed upon in a written contract.

A30828-X1150-N60-2-7620 3



This document consists of a total of 72 pages. All pages are issue 2.

Contents1 General . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 71.1 Purpose of this document . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 71.2 Network element types . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 71.3 Definition . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 91.4 X.25 connection variants. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 91.4.1 Direct connection (network type X25LC) . . . . . . . . . . . . . . . . . . . . . . . . . . . 91.4.1.1 Direct local connection . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 91.4.1.2 Direct modem connection . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 101.4.1.3 Direct ISDN connection. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 101.4.2 Connection via X.25 DCN (network type X25) . . . . . . . . . . . . . . . . . . . . . . 111.5 OSI Network . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 111.5.1 X.25 address. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 121.5.1.1 DTE address . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 121.5.1.2 NSAP address . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 121.6 Installation and administration procedure . . . . . . . . . . . . . . . . . . . . . . . . . . 13

2 Requirements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 152.1 General Requirements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 152.1.1 Connection via Modem . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 152.1.2 Connection via ISDN Terminal Adapter . . . . . . . . . . . . . . . . . . . . . . . . . . . 152.1.3 Connection via X.25 DCN . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 162.2 CP Requirements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 162.2.1 CP HW Requirements. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 172.2.1.1 IOP:LAU . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 172.2.1.2 IOP:LAU Cabling. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 172.2.1.3 IOP cable for direct connection (X25LC) . . . . . . . . . . . . . . . . . . . . . . . . . . 182.2.1.4 IOP cable for connection via X.25 DCN (X25) . . . . . . . . . . . . . . . . . . . . . . 192.2.2 CP SW Requirements. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 192.3 PC Requirements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 192.3.1 PC Hardware Requirements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 192.3.1.1 X.25 EICON Board . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 192.3.1.2 PC cable for direct connection (X25LC) . . . . . . . . . . . . . . . . . . . . . . . . . . . 202.3.1.3 PC cable for connection via X.25 DCN (X25) . . . . . . . . . . . . . . . . . . . . . . . 202.3.2 PC software requirements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 21

3 CP Administration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 233.1 Definition and configuration of IOP:LAU . . . . . . . . . . . . . . . . . . . . . . . . . . . 233.1.1 CR IOP . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 233.1.1.1 Prerequisites . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 243.1.1.2 Dependencies . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 243.1.1.3 Command syntax . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 243.1.1.4 Parameter description. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 253.1.2 CONF IOP. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 253.1.2.1 Prerequisites . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 253.1.2.2 Dependencies . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 25

4 A30828-X1150-N60-2-7620


3.1.2.3 Command syntax . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 263.1.2.4 Parameter description . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 263.1.3 CONF LAU. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 263.1.3.1 Prerequisites . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 263.1.3.2 Dependencies . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 263.1.3.3 Command syntax . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 263.1.3.4 Parameter description . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 263.1.4 CAN IOP . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 263.1.4.1 Prerequisites . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 273.1.4.2 Dependencies . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 273.1.4.3 Command syntax . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 273.1.4.4 Parameter description . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 273.1.5 DISP IOP . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 273.1.5.1 Prerequisites . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 273.1.5.2 Dependencies . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 273.1.5.3 Command syntax . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 273.1.5.4 Parameter description . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 283.2 Creation of X.25 data links . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 283.2.1 CR X25LINK. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 283.2.1.1 Prerequisites . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 283.2.1.2 Dependencies . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 283.2.1.3 Command syntax . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 283.2.1.4 Parameter description . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 293.2.2 CONF X25LINK . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 303.2.2.1 Prerequisites . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 303.2.2.2 Dependencies . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 303.2.2.3 Command syntax . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 303.2.2.4 Parameter description . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 303.3 Creation of remote processors. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 303.3.1 CR PRO . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 313.3.1.1 Prerequisites . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 313.3.1.2 Dependencies . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 313.3.1.3 Command syntax . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 313.3.1.4 Parameter description . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 313.4 Creation of OSI network addresses . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 313.4.1 CR OSIADR . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 323.4.1.1 Prerequisites . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 323.4.1.2 Dependencies . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 323.4.1.3 Command syntax . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 323.4.2 Modification of OSI addresses . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 333.4.2.1 MOD OSIADR . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 333.4.2.2 Prerequisites . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 333.4.2.3 Dependencies . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 333.4.2.4 Command syntax . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 333.4.2.5 Parameter description . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 343.4.3 CAN OSIADR. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 343.4.3.1 Prerequisites . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 34

A30828-X1150-N60-2-7620 5



3.4.3.2 Dependencies . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 343.4.3.3 Command syntax . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 343.4.3.4 Parameter description. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 343.5 Definition of Applications. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 353.5.1 CR APPL. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 353.5.1.1 Prerequisites . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 353.5.1.2 Dependencies . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 353.5.1.3 Command syntax . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 353.5.2 CR X25DTE . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 363.5.2.1 Prerequisites . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 363.5.2.2 Dependencies . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 363.5.2.3 Command syntax . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 373.5.2.4 Parameter description. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 383.5.3 CR X25ROUTE. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 383.5.4 Parameter description. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 383.6 Creation of DTE Addresses and X25 Routes . . . . . . . . . . . . . . . . . . . . . . . 393.6.1 Prerequisites . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 393.6.1.1 Dependencies . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 393.6.1.2 Command syntax . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 393.6.2 Parameter description. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 403.7 Parameter value dependencies . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 41

4 PC Administration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 434.1 O&M SW installation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 434.1.1 O&M SW installation hints . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 434.1.2 Example of a PC database . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 454.2 PC Database Administration. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 474.2.1 Creation of X25DTEs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 484.2.2 Creation of processors . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 50

5 CP Hardware Installation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 535.1 IOP:LAU installation in CP113 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 535.1.1 IOP:LAU installation in R:DEVD(0) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 535.1.2 IOP:LAU installation in R:DEVD(1) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 535.1.3 Administration Hints . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 545.1.4 IOP:LAU cabling in R:DEVD(0) and R:DEVD(1). . . . . . . . . . . . . . . . . . . . . 555.2 IOP:LAU installation in CP113C . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 575.2.1 IOP:LAU installation in R:CE . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 575.2.2 Administration Hints . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 575.2.3 IOP:LAU cabling in R:CE . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 58

6 O&M DB Command Files . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 616.1 Direct Connections . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 616.2 Connections to X.25 DCN. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 65

7 Troubleshooting . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 697.1 Hardware installation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 697.2 Troubleshooting on the PC with NetM (SiM) software . . . . . . . . . . . . . . . . 697.2.1 PC Test Commands . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 70

6 A30828-X1150-N60-2-7620


7.3 Troubleshooting on the CP . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 707.4 Symptom Saving . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 71

8 Abbreviations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 72

A30828-X1150-N60-2-7620 7



1 General

1.1 Purpose of this documentThis document was produced to give O&M administration personnel a basic introductionand practical information on X.25 network installation and administration processes.This description is intended to enable the reader to commission X.25 connections toEWSD via direct links and/or via X.25 data communication networks (DCN).The necessary NetManager (NetM) PC database entries and all relevant MML com-mands for generation of the appropriate CP database are described in chapters 3 and4. Examples of the CP O&M database command file are provided in chapter 6 coveringapplications, print dialog and file transfer.

1.2 Network element typesNetManager (NetM) supports the operation of EWSD and SURPASS network elements.EWSD is the Siemens digital switching system for telephone networks and SURPASSis the Siemens product family implementing the transition from circuit-based networks(designed for voice transmission) to packet-based networks (designed for data trans-mission).The following types of EWSD network elements are available: EWSD Classic

This is a network element that is operated mainly via the MML interface. An EWSDClassic network element is accessed by its coordination processor (CP).

EWSD STP (also called SSNC SA:STP)This is a standalone signaling system network control implementing the function ofa signaling transfer point (SS7), to be operated via the Q3 interface. An EWSD STPnetwork element is accessed by its main processor (MP). Compare hiS.

EWSD PowerNodeThis contains both the EWSD Classic and the STP components.

The following types of SURPASS network element are available: hiG

This implements the physical transition from the telephone network to the Internetprotocol (IP) based data network and vice versa. The hiG contains the packet HUB,a modem pool card, and other components.

hiQThis implements the control function for hiG including the transformation from direc-tory numbers to IP addresses, authentication, authorization, and accounting.Corresponding to these functions there are different hiQ network elements: hiQ xx (e.g. hiQ10, hiQ20, hiQ30)

These transform directory numbers to IP addresses, and implement authentica-tion, authorization and accounting.

hiQ xxxx (e.g. hiQ9100 and hiQ9200)These supervise hiG. These hiQs contain a media gateway interface (MGI), a co-ordination processor (CP) and/or main processor (MP) and other components.

hiQ 9400 presents a programming interface for implementing new feature setsthat can be offered to subscribers in the telephone network as well as in the IPnetwork.

8 A30828-X1150-N60-2-7620


hiSThis implements the function of a standalone broadband signaling transfer point. Itis operated via the Q3 interface and accessed by its main processor (MP). CompareEWSD STP (also called SSNC SA:STP).

Fig. 1.1 Network element types

EWSD STP

EWSDEWSD

MP

EWSD Classic

EWSDEWSD

CP

EWSD PowerNode

EWSDEWSD CP

MP

Network Elements

MPCPSTPPHUBMGI

= Main Processor= Coordination Processor= Signaling Transfer Point= Packet HUB= Media Gateway Interface

X.25 X.25 X.25

example of network elements

MGI partMP partPHUB part

SURPASS hiG

SURPASS hiQ

A30828-X1150-N60-2-7620 9



1.3 DefinitionThere are differences between the CP hardware modules, LCUB and LAUB, and the as-sociated MML commands these modules can be administered with. An IOP hardwareunit, formed by one module LCUB (Line Control Unit, Type B) and one module LAUB(Line Adaption Unit, Type B), is defined as IOP:LAU.Refer to chapter 2 for CP requirements.The following MML commands relate to the individual IOP modules: LCUB modules are designated as IOPLAU in the CP database

(e.g. CONF IOP:IOP=IOPLAU-x, OST=ACT;) LAUB modules are designated as LAU in the CP database

(e.g. CONF LAU:LAU=x, OST=ACT;)

1.4 X.25 connection variantsThere are basically two ways of connecting an O&M PC system to EWSD or SURPASSvia X.25, either via direct connections (point to point) or via an X.25 data communicationnetwork (e.g. EWSP, HNN, Motorola X.25 Node 6525, ...). In this document direct con-nections are referred to as network type X25LC and connections via X.25 DCN as net-work type X25. Remote processors such as a PC with NetM (SiM) software are identifiedby means of OSI addresses and DTE (data terminal equipment) information adminis-tered in the CP database.

1.4.1 Direct connection (network type X25LC)This configuration represents a non-open network with one single point-to-point connec-tion and is also defined as a local network (X25LC).

1.4.1.1 Direct local connection

Fig. 1.2 Direct local connection of PC with NetM (SiM) software

64 kbit/smax. distance 15 m

PC with NetM(SiM) software

X.25EICONBoard

EWSDEWSD

IOP:LAU

Network element

PC with NetM softwareNetM software with single machine (SiM) configura-tion.The single machine configuration combines all PCtypes (file, communication server and craft terminal)on one computer).

10 A30828-X1150-N60-2-7620


1.4.1.2 Direct modem connection

Fig. 1.3 Direct modem connection of a PC with NetM (SiM) software

1.4.1.3 Direct ISDN connection

Fig. 1.4 Direct ISDN connection of a PC with NetM (SiM) software

> 100m modem link

Modem ModemX.25EICONBoard

EWSDEWSD

IOP:LAU

Network element


Network element

Modem Modem

EWSDEWSD

IOP:LAU X.25EICONBoard

NT NT

NT = Network terminationISDN


Network element

EWSDEWSD

X.25EICONboard

PC with NetM (SiM) Software

NTIOP:LAU NT

A30828-X1150-N60-2-7620 11



1.4.2 Connection via X.25 DCN (network type X25)NetM (SiM) operation via an X.25 network requires an X.25 DCN based on the CCITT1984 recommendations or alternatively CCITT 1980 plus address extension field (AEF).Closed user groups can be created by the X.25 network administrator to provide maxi-mum system security. Physical connections from the X.25 network element to CP and/orPCs with NetM (SiM) can be set up with direct cables in the range up to 15 m. Distancesof more than 15 m can be covered with modem or ISDN paths.

Fig. 1.5 Connections in an O&M network via X.25 DCN (network type X25)

1.5 OSI NetworkAn OSI network allows virtual connections to be set up between two DTEs (processors)according to the ISO 7 layer reference model. By means of the DTE address and theNSAP (Network Service Access Point) address, all processors and the associated ap-plications (e.g. print dialog, file transfer) are uniquely identified. A communication linkbetween local and remote applications can be provided either with PVCs (PermanentVirtual Circuit) or SVCs (Switched Virtual Circuit).For detailed information on this subject, please refer to the manual OMN:EXCH-SY

Network element

EWSDEWSD

IOP:LAU

X.25EICONboard

X.25EICONboard Modem

Modem

Network element

EWSDEWSD

IOP:LAU

max. distance 12 km

X.25 DCNe.g EWSP, X.25 Node

DCN



12 A30828-X1150-N60-2-7620


1.5.1 X.25 addressThe X.25 protocol provides two fields, address field (AF) and address extension field(AEF) for transmission of DTE and NSAP addresses. The address field (AF) is used fornetwork terminal identification in the X.25 network and contains the DTE address eval-uated in layer 3. The address extension field (AEF) contains the NSAP address withwhich a particular application can be identified. For EWSD O&M via X.25, OSI address-ing via AEF is required. This is defined with MML command CR X25DTE, parameterFACIL=AEFIN&AEFOUT. Fig. 1.6 shows the addressing scheme for a standard X.25O&M network.

Fig. 1.6 Addressing scheme for a standard X.25 O&M network

1.5.1.1 DTE addressA DTE address is assigned to a specific X.25 termination and defines the "physical" portin a X.25 network.According to CCITT recommendation X.121, 14 decimal digits can be used as DTE ad-dress for X.25 networks. For direct connections (X25LC) a maximum of 15 decimal dig-its are possible for the DTE address .Remote DTE addresses in X25 and ISDN networks are created with CR X25DTEwhereas all local DTE addresses and remote DTE addresses in network type X25LCmust be created with MML command CR X25ROUTE.DTE address values can be chosen freely, as long as they do not collide with existingdatabase entries. However, if a public X.25 DCN (PSPDN) is used DTE addresses willhave to be ordered from the PSPDN administration.

1.5.1.2 NSAP addressBy means of the NSAP address, provided within the address extension field of the X.25protocol, a definite application is selected. The network service access point (NSAP) de-fines the threshold between network layer (layer 3) and transport layer (layer 4) in the

print dialog file transfer

DTE address bX.25 protocol

OS

X.25 addressing

DTE address aX.25 protocol

CP

Application Layer 7

......

...

Network service access point

Network Layer 3Data Link Layer 2Physical Layer 1

AF

DTE

AEF

NSAP

Presentation Layer 6

Session Layer 5

Transport Layer 4

print dialog file transfer

NSAP addr. 1 NSAP addr. 2 NSAP addr. 3 NSAP addr. 4

A30828-X1150-N60-2-7620 13



OSI reference model. The NSAP address identifies a certain network service accesspoint with its associated application and consists of 3 fields

The DTE address is uniquely assigned to the IDI part of an OSI address (NSAP) in anX.25 network (network type X25); hence all addresses with a certain IDI value are as-signed to the same DTE and have to be assigned to one and the same processor. How-ever, the NSAP for direct connections (network type X25LC) does not contain an IDIvalue (IDI=0).The type of X.25 connection to the CP (network type X25LC, X25, ..) determines the AFIvalue to be used for NSAP addresses. Certain applications (print dialog, file transfer)can be selected with the DSP part. The following table shows the differences betweennetwork type X25 , X25LC and ISDN with the possible formats and values (refer to 3.4.1for more details):

To ensure clarity in the addressing table of the CP database a homogeneous schemefor NSAP address allocation is recommended. Use one DSP value for each applicationin the O&M network e.g. DSP=11 for application print dialog (DIALG), DSP=55 for ap-plication file transfer (NEABx)

1.6 Installation and administration procedureThe easiest way to set up an X.25 O&M network is described in the following steps.When the CP database is created, all the data required for SW installation of the PC withNetM (SiM) software is determined first. The PCs, DTE, NSAP addresses and processorname, as entered in the CP processor table, are requested during the software installa-tion.1. Install IOP:LAU (boards LCUB and LAUB) in CP shelf (B:IOC) including cabling

Refer to chapters 5 and 2 of this documentation.2. Create CP database entries for X.25 (IOP, links, applications, addresses, etc.)

Refer to chapter 3.3. Install required hardware (X.25 EICON board) and software packages (X.25 driver)

on the appropriate O&M PC.Refer to chapter 2.

NSAP AFI IDI DSP

AFI = Authority and Format IdentifierIDI = Initial Domain IdentifierDSP = Domain Specific Part

Network type AFI IDIdecimal digits

DSPdecimal digits

X25(X.25 DCN)

36 max. 14 max. 24

X25LC(direct connection)

48 1 (=0) max. 38

ISDN 44 max. 15 max. 23

Tab. 1.1 Network types and associated AFI, IDI and DSP values

14 A30828-X1150-N60-2-7620


4. Install the NetM (SiM) software on the PC and create the PC database for dialogand/or file transfer with CP. Refer to 4.

Fig. 1.7 X.25 installation and administration sequence

Cabling, modems, TA...

Modules LCUB, LAUB

CP HW InstallationChapters 2 and 5

Configuration of X.25data Links

Creation andconfiguration of IOP

CP X.25Database creationChapters 3 and 6

PC Database Administra-tion

PC with NetM (SiM) SWInstallation

X.25 HW and SW Installa-tion

PC Installation andAdministration

Chapters 2 and 4

Troubleshooting

TRANSFILE:FILE=...

CP Dialog Dest=CP1,...

PC with NetM (SiM) SWFunction Test

Chapter 7

A30828-X1150-N60-2-7620 15



2 Requirements

2.1 General RequirementsFor communication between the CP and a PC with NetM (SiM) software a data transferchannel with 64 kbit/s is required in order to achieve maximum performance. This chan-nel can be implemented by a point-to-point connection via modem or ISDN TA (asshown in chapter 1.4.1) or by X.25 DCN, e.g. EWSP (as shown in chapter 1.4.2.)

2.1.1 Connection via ModemThe maximum distance for modem-modem connection via two galvanic wires is 12 km.With four-wire modems, distances up to 20 km can be covered. The two-/four-wire linkhas to be provided by the network administrator; depending on the wires used and theattenuation, there may be deviations as regards the distances. For 64 kbit/s links onlymodems with X.21 interface are used. For example, you may use one of the following64 kbit modem types (the same type on either side)

Installation hintsThe clock mode of one of the two interconnected partner modems must be set to "mas-ter" whereas the second one needs to be set to "slave". Using switch S, select interfaceX.21 and adjust your modem settings and functions according to the following table:

For programming and test procedures refer to the "Operating Instructions" deliveredwith your modem.

2.1.2 Connection via ISDN Terminal AdapterThis enables O&M operation at an unlimited distance from the CP and requires an ISDNbasic access in the local environment on either side. The ISDN basic access with its net-work termination (NT) and S0 interface provides two data transfer channels (B chan-nels) with a net bit rate of 64 kbit/s each. The IOP:LAU is connected to the V.36 interfaceof the terminal adapter (TA) which occupies one B channel for O&M purposes.

S22382-H2032-A6 DAG 64 (for 2-wire connection)S22382-H2032-A7 DAG 64 (for 4-wire connection)

Funct. no. Mode no. Operating Mode1 1 interface X.212 2 Subscriber signaling 64 kbit/s3 x [0, 2] select 0 for Master, 2 for Slave4 0 (as supplied)5 1 (as supplied)6 1 (as supplied)7 1 (as supplied)

Tab. 2.1 Modem settings and functions

16 A30828-X1150-N60-2-7620


The connection between the two partner TAs has to be set up manually by means of thebuilt-in keyboard.

For example, the above-mentioned terminal adapter supports Red Book and Blue BookISDN (with EPROM version Q1600140). For outgoing calls FW Q1600 150 is required.Switches must be set according to the following tables:

2.1.3 Connection via X.25 DCNThis requires an X.25 data communication network (DCN) that meets the CCITT recom-mendations 1984 or 1980 plus "Address Extension Field". The X.25 DCN consists ofone or more data communication equipments (DCE) which act as network nodes andprovide the DTE terminations. If there is no public switching packet data network (PSP-DN) available as X.25 DCN , a DCE can be implemented for example with Siemens EWSP Siemens HNN (High Performance Network Node) Motorola CODEX 6525 (X.25 node with up to 48 DTE ports)When the Motorola CODEX 6525 is used, DTE connections can be established viamodem or ISDN node, as also described for direct connections. For further informationconcerning installation and administration of the above-mentioned X.25 network nodes,refer to the appropriate manuals.

2.2 CP RequirementsThe requirements specified in this section are parts of construction manuals and sys-tem-specific cabling lists.

S30807-U2559-X100 Terminal Adapter TA-X.21/X.21bis Type II

Switch S401 Switch S410DIP Switch ON,

OFFD-channelprotocol

(rotary switch pos. 0 ... 9)e.g.

1 OFF (terminal selection number)2 ON3 OFF4 OFF5 ON6 ON7 ON8 ON9 OFF10 OFF 1TR6 Set DIP switch 10 according to the D channel

protocol specified for your ISDN termination.10 ON ETSI

Tab. 2.2 Settings in the terminal adapter

A30828-X1150-N60-2-7620 17



2.2.1 CP HW RequirementsTo connect a CP to an X.25 O&M network, at least one IOP:LAU has to be installed.The IOP:LAU consists of two boards, the LAUB (line adaptation unit B) and the corre-sponding control unit LCUB (line control unit B). For redundancy reasons one IOP:LAUis connected to the IOC-0 (2) bus and the other to IOC-1 (3). One IOP:LAU pair providesfour data link ports (X.25), 2 links per IOP. Creation of a single IOP:LAU is not possible.Refer to chapter 5 for IOP:LAU installation.

2.2.1.1 IOP:LAUWhen you install the LCUB and LAUB boards in the CP113 rack R:DEVD(0) orR:DEVD1 or in the CP113C rack R:CE; make sure that the boards are compatible witheach other.

If you have modules with a different code no. status, contact the TAC2 hotline for clari-fying compatibilities as there could be changes concerning compatibilities after publica-tion of this documentation.

2.2.1.2 IOP:LAU CablingFor each IOP:LAU pair two short and two long backplane cables are required for redun-dancy (cross connection). The following table shows the required hardware equipmentaccording to the number of X.25 data links:

LCUBMain module S30810-Q1114-X200-6Firmware S30810-Q1114-X202-1

This requires a module LAUB with code no. status D1! LAUB

Main module S30810-Q1115-X100-D1Firmware S30810-Q1115-X102-3

X.25 datalinks

Number of required LCUB, LAUBpairs per IOC

Number of shortbackplane ca-bles

Number of longbackplane ca-bles

IOC-0 IOC-1 IOC-2 IOC-3 S38228-Z2-A2 S38228-Z2-A60...3 1 1 - - 2 24...7 2 2 - - 4 4

8...11 2 2 1 1 6 612...15 2 2 2 2 8 8

Tab. 2.3 IOP:LAU cabling in CP113

18 A30828-X1150-N60-2-7620


For more information concerning logical X.25 link assignment to the IOP:LAU hardwareport, refer to chapter 5.

2.2.1.3 IOP cable for direct connection (X25LC)

Cable for local direct connection IOP:LAU PC with NetM (SiM) software (EICONboard):

Alternatively the local direct connection can be set up with a combination of theEICON modem cable 1.) and an IOP:LAU cable 2.):

Direct connection via modem (DAG 64):cable IOP:LAU modem DAG 64 (X.21 interface)

Direct connection via ISDN (TA X.21/X.21 bis):Cable IOP:LAU Terminal Adapter X.21/X.21bis (V.36 Interface):

X.25 datalinks

Number of required LCUB, LAUBpairs per IOC

Number of shortbackplane ca-bles

Number of longbackplane ca-bles

IOC-0 IOC-1 IOC-2 IOC-3 S38228-Z2-A8 S38228-Z2-A120...3 1 1 2 24...7 2 2 4 4

8...11 3 3 6 612...15 4 4 8 8

Tab. 2.4 IOP:LAU cabling in CP113 C

S38228-Z148-A... (planar cable shelf) max. length 150 dmor S38228-Z149-A... (false floor cabling) max. length 150 dm

1.) S30257-Z8261-A25 X.21 HSI modem cable (EICON 300-025)

2.) S38228-Z146-A... (planar cable shelf) max. length 150 dmor S38228-Z147-A... (false floor cabling) max. length 150 dm



A30828-X1150-N60-2-7620 19



2.2.1.4 IOP cable for connection via X.25 DCN (X25)There are two ways of connecting the IOP:LAU to an X.25 DCN. If you have a DTE ter-mination of a PSPDN, a modem with X.21 interface is generally supplied. If a privateX.25 DCN is used (e.g. a single X.25 node) long distances between CP and X.25 nodecan be covered either with modems or via ISDN and terminal adapters:

Connection to DTE termination modem: cable IOP:LAU modem (X.21 interface)(for modem with X.21 interface 15-pin socket)

Connection to X.25 node (DCE) via ISDN (TA X.21/X.21 bis):Cable IOP:LAU Terminal Adapter X.21/X.21bis (V.36 Interface):

2.2.2 CP SW RequirementsBefore installation of IOP:LAU make sure that the file listed below is present. Dependingon the load type to be administered with CR IOP, parameter LOADTP, an appropriatefile is necessary for the load procedure of IOPLAU. For LOADTP=nnn a file assigned asSY.PSW.Tnnn is required:

SW patches in CP APSCheck whether all X.25 CP APS patches are installed in your exchanges to guaranteethe full range of X.25 O&M features, as the relevant patches may have changed by thetime you install your X.25. Use the TAC2 hotline for up-to-date information if necessary.

2.3 PC Requirements

2.3.1 PC Hardware Requirements

2.3.1.1 X.25 EICON BoardYour standard PC with NetM software has to be extended with an X.25 EICON board:

For installation procedures refer to MMN:PC, "Installing the EICON board" or the latestNetM documentation.



e.g. LOADTP=100 (default value) --> SY.PSW.T100

S30122-U372-X X.25 EICON Board

20 A30828-X1150-N60-2-7620


2.3.1.2 PC cable for direct connection (X25LC) Cable for local direct connection IOP:LAU PC with NetM (SiM) software (EICON

board, Port 0):(the same that is mentioned in Chapter 2.2.1.3 )

Alternatively the local direct connection can be set up with a combination of theEICON modem cable 1.) and an IOP:LAU cable 2.):

Direct connection via modem:cable EICON board Port 0 modem DAG 64 (X.21 interface)

Direct connection via ISDN (TA X.21/X.21bis):Cable EICON Board Port 0 Terminal Adapter X.21/X.21bis (V.36 Interface)

2.3.1.3 PC cable for connection via X.25 DCN (X25)If you have a DTE termination of a PSPDN, a modem with X.21 interface is generallysupplied. If an X.25 DCN is used (e.g. a single X.25 node) distances between PC withNetM (SiM) software and X.25 node can be covered with modem paths or via ISDN andterminal adapters:

Connection to DTE termination modem:cable EICON Board Port 0 modem (X.21 interface, 15 pin socket)

Connection to X.25 node (DCE) via ISDN (TA X.21/X.21 bis):Cable EICON Board, Port 0 Terminal Adapter X.21/X.21bis (V.36 Interface)


1.) S30257-Z8261-A25 X.21 HSI modem cable (EICON 300-025)

2.) S38228-Z146-A... (planar cable shelf) max. length 150 dmor S38228-Z147-A... (false floor cabling) max. length 150 dm

S30257-Z8261-A25 X.21 HSI modem cable (EICON 300-025)

S30257-Z8262-A... max. length 150 dm

S30257-Z8261-A25 X.21 HSI modem cable (EICON 300-025)

A30828-X1150-N60-2-7620 21



2.3.2 PC software requirementsOperation of an O&M PC requires the following software:

Basic installation: operating system NetM (SiM) software system-specific service packs system-specific O&M products system-specific database

SW additionally required for X.25 networking: X.25 driver software for EICON board)

S30257-Z8262-A... max. length 150 dm

i These software packages are already preinstalled on your PC if it was delivered fromGermany

i For installation procedures refer to MMN:PC, "Installing the EICON Card", or the latestNetM documentation.

22 A30828-X1150-N60-2-7620


A30828-X1150-N60-2-7620 23



3 CP AdministrationCP database entries for an X.25 PVC (permanent virtual circuit) and an X.25 SVC(switched virtual circuit) cannot exist simultaneously. Connections to the O&M PC withNetM (SiM) are to be installed as X.25 SVC only.This chapter gives you detailed information and useful hints concerning dependenciesof all the CP commands necessary for X.25 O&M database creation. Chapter 6, "O&MDB Command Files", contains complete examples of CP administration of the differentconnection variants (direct, DCN).After you have installed the necessary CP IOP hardware (see chapter 5), you can startto set up the database. As this involves entering numerous commands and parameters,it is advisable to create a command file that can be executed on the local O&M PC withNetM (SiM) software or any central PC with NetM (SiM) software that is connected tothe CP. In view of the dependencies of individual MML commands it is essential to pre-pare your command file in the following order:1. Creation of IOPLAU and configuration of IOPLAU and LAU to MBL

CR IOP, CONF IOP, CONF LAU2. Creation and configuration of X.25 data links according to MBL

CR X25LINK, CONF X25LINK3. Creation of remote processors

CR PRO4. Creation of local OSI network addresses

CR OSIADR5. Creation of local applications

CR APPL6. Creation of remote OSI network addresses

CR OSIADR7. Creation of remote applications

CR APPL8. Creation of local DTE addresses and local X.25 routes

CR X25DTE, CR X25ROUTE9. Creation of remote DTE addresses and remote X.25 routes. This point is only nec-

essary in connection with dedicated lines (not for network connections).CR X25DTE, CR X25ROUTE

10. Configuration of IOPLAU and LAU to activeCONF IOP, CONF LAU

11. Configuration of X.25 data links to activeCONF X25LINK

3.1 Definition and configuration of IOP:LAU

3.1.1 CR IOPThis command creates two IOP:LAUs and the associated line adaptation units (LAU) asa redundant IOP pair, connected to the input/output control bus B:IOC-0 and B:IOC-1.A second IOP channel pair, B:IOC-2 and B:IOC-3 can be installed in your exchange ata point where additional IOP:LAUs can be connected. Creation of one single IOP:LAUis not possible. LAU numbers are created as the corresponding IOPLAU number in the

24 A30828-X1150-N60-2-7620


range 0 ... 11. Newly created IOPLAUs are in status PLA. Fig. 3.1 shows how B:IOC,IOPLAU and LAU are logically linked and how X.25 data links are related to LAUs.

Fig. 3.1 Overview of X.25 data link installation

3.1.1.1 PrerequisitesThe IOP hardware (LCUB, LAUB) must have been installed according to chapter 5.

3.1.1.2 DependenciesNone.

3.1.1.3 Command syntax

IOPLAU-0

IOPLAU-1

IOPLAU-2

IOPLAU-3

LAU-0

LAU-1

LAU-2

LAU-3

CHAN 0CHAN 1

CHAN 0CHAN 1

CHAN 1

CHAN 0CHAN 1

X25LINK-0X25LINK-1

X25LINK-2X25LINK-3

X25LINK-4X25LINK-5

X25LINK-6X25LINK-7

B:IOC-0

B:IOC-1

CHAN 0

Parameter Possible values Defaultvalue

Note

IOC 0, 1, 2, 3 BIOC 0 ... 15 for IOC-0, 1: 11,15 only

for IOC-2, 3: 11, 13, 14, 15

Tab. 3.1 Command syntax for CR IOP

A30828-X1150-N60-2-7620 25



3.1.1.4 Parameter description

3.1.2 CONF IOPThis command configures the IOP:LAU to ACT, MBL or PLA. Configuration from ACTto MBL is dangerous as it reduces the redundancy.

3.1.2.1 PrerequisitesIOPLAU load file SY.PSW.Tnnn (nnn=LOADTP) must already exist on the CP hard diskif IOPLAU is to be entered subsequently. The IOP must have been created before.


IOP IOPLAU-0, 2, 4, 6 ...IOPLAU-10

IOPR1234567890123

IOPLAU-1, 3, 5 ...IOPLAU-11

IOPLAU-1 is partner of IOPLAU-0;IOPLAU-3 is partner of IOPLAU-2,etc.

BIOCR 0 ... 15 for IOC-0, 1: 11, 15 onlyfor IOC-2, 3: 11, 13, 14, 15

LOADTP 100 ... 120 100LDPRTY LOW, HIGH LOW

Tab. 3.1 Command syntax for CR IOP

IOC Defines the IOC to be used for the IOPLAU (0, 2). This value exactly definesthe IOC to be used for the redundant partner IOPLAU (IOPR), for examplethe partner IOP for IOPLAU-0 in IOC-0 is IOPLAU-1 in IOC-1, the redun-dant partner IOP for IOPLAU-2 in IOC-0 is IOPLAU-3 in IOC-1!

BIOC Defines the IOC bus connection number for the IOP (LCUB, LAUB). IOC-0and IOC-1 buses are mainly reserved for standard IOPs and only numbers11 and 15 can be used here for IOPLAUs. If IOC-2 and IOC-3 are installedand available, bus connection numbers 11, 13, 14 and 15 can be used forIOP:LAUs.

IOP Defines the IOP type (here IOPLAU only) and IOP number e.g. IOPLAU-0IOPR Defines the redundant partner IOPLAU, connected to the redundant IOC

specified with parameter BIOCR.Hint: Use the same values for BIOC and BIOCR for easy IOP backplane ca-bling (cable lengths).

BIOCR Defines the bus connection number of the redundant IOC bus.LOADTP Defines the load file name for the IOPLAU,

e.g. LOADTP=100 --> load file: SY.PSW.T100LDPRTY Defines the moment when IOP loading occurs during a system recovery.

26 A30828-X1150-N60-2-7620




3.1.3 CONF LAUThis command configures the LAU to ACT, MBL or PLA. Configuration from ACT to MBLis dangerous because of its influence on existing X25LINKs. The LAU is activated with-out tests.

3.1.3.1 PrerequisitesThe LAU must have been created with CR IOP.




3.1.4 CAN IOPThis command cancels the IOP:LAU and its redundant partner IOP:LAU at the sametime, e.g. IOPLAU-0 together with IOPLAU-1.

Parameter Possible values Default value NoteIOP IOPLAU-0 ... IOPLAU-11 OST ACT, MBL, PLA see 3.1.2

Tab. 3.2 Command syntax for CONF IOP

IOP Defines the IOP type (here IOP:LAU) and IOP number e.g. IOPLAU-0OST Defines the status you want to change to.

Parameter Possible balues Default value NoteLAU 0 ... 11 OST ACT, MBL, PLA see 3.1.2

Tab. 3.3 Command syntax for CONF LAU

LAU Defines the LAU and LAU number e.g. LAU=0OST Defines the status you want to change to.

A30828-X1150-N60-2-7620 27



3.1.4.1 PrerequisitesThe IOP:LAU must have been created previously.

3.1.4.2 DependenciesThe specified IOP:LAU and its LAU must be in status PLA. All relevant entries for thisIOP:LAU pair must have been cancelled beforehand.



3.1.5 DISP IOPThis command displays the operating state and all data entries specified for this IOP.Use this command to check the configuration for IOP:LAUs that have already been cre-ated and to adapt your X.25 database creation file if necessary. There is no modificationcommand for IOPs, hence if an IOP:LAU that has already been created does not matchyour requirements it has to be cancelled first (CAN IOP) and then created again(CR IOP).

3.1.5.1 PrerequisitesThe specified IOP:LAU must already have been created. You can check this with MMLcommand STAT SSP!




Note

IOP IOPLAU-0 ... IOPLAU-11 only 12 IOPLAUs are possible

Tab. 3.4 Command syntax for CAN IOP

IOP Defines the IOP type (here IOP:LAU) and IOP number e.g. IOPLAU-0


Note

IOP IOPLAU-0 ... IOPLAU-11 - -

Tab. 3.5 Command syntax for DISP IOP

28 A30828-X1150-N60-2-7620



3.2 Creation of X.25 data links

3.2.1 CR X25LINKThis command creates an X.25 data link (X25LINK) on the specified LAU and at a spe-cific channel and configures this link in status PLA. Additional layer and network param-eters can be entered. The parameter description in chapter 3.2.1.4 deals with theparameters that have to be administered and are different from the default values shownin the sample files for X.25 database creation in chapter 4.For display, modification and cancellation of X25LINK, commands DISP X25LINK,MOD X25LINK and CAN X25LINK are available. Refer to chapter 5 for information onIOP hardware port-to-X.25 data link assignments.

3.2.1.1 PrerequisitesBoth IOP:LAUs (the relevant IOP:LAU with its partner IOP:LAU), and the LAU to whichthe X.25 data link is to be assigned, must already have been created and must be instatus PLA or MBL. The channel number (0 or 1) of the specified LAU must not havebeen assigned to another link number and the desired X25LINK number must not havebeen used already.

3.2.1.2 DependenciesTo operate an X25LINK successfully, all link settings (parameters) must match the set-tings of the device at the other end (e.g. modems, X.25 driver configuration, etc.).


IOP Defines the IOP type (here IOP:LAU) and IOP number e.g. IOPLAU-0


Note

X25LINK 0 ... 23 LAU 0 ... 11 CHAN 0, 1 NET X25LC, X25, ISDN X25LC must match the NET pa-

rameter of CR X25ROUTEPRTCL X25,BX25 X25L1BAUD B9600, B64000 B2400

Tab. 3.6 Command syntax for CR X25LINK

A30828-X1150-N60-2-7620 29




L1DTT DTE, DCE DTE L1DTT=DTE for direct mo-dem connection X25LC,DCE for direct local connec-tion (15m)!NET=X25LC: L1DTT=DTE

L1IF X21, V24, V35,V36,V36DIAL

V24 L1DTT=DTEV36DIAL: L1DTT=DTE

L2DTT DCE, DTE DTE NET=X25:L2DTT=DTENET=X25LC:L2DTT=DCE

L3DTT DTE, DCE DTE NET=X25:L3DTTL2DTT=DTENET=X25LC: L3DTT=DCE

L3TCB 0 ... 4095 0 Use L3TCB=36&&85 asthis is also the default valueof the OS SW

L2N1 23 ... 4103 135L2LAM 1 RESPON

These are the parameters (out of a total of 36) which require entries for standardX25LINK creation. For the parameters not listed in the above table the default valuesare used.

Tab. 3.6 Command syntax for CR X25LINK

X25LINK Defines the logical number of the data linkLAU Specifies the IOP HW to be used e.g. IOPLAU-0 --> LAU=0CHAN Specifies the channel number (0 or 1) of the assigned LAU to be

usedNET Defines the type of X.25 network the link is connected to.

NET=X25LC is used for direct connection, NET=X25 for connectionsto an X.25 data communication network (DCN)

PRTCL X.25 protocol is used for all X.25 SVC, PRTCL=X25L1BAUD Defines the layer 1 data bit rate in Baud, the parameter is only used

if L1DTT is set to DCE!L1DTT Defines the layer 1 data terminal type; use L1DTT=DCE for local di-

rect (cable) connection, DTE for direct modem connections, directconnection via ISDN and connections to X.25 DCN

L1IF Defines the layer 1 interface. L1IF=V36DIAL for direct connectionsvia ISDN terminal adapter

L2DTT Defines layer 2 data terminal type. Use DCE for all direct connectionsand DTE for connections to an X.25 DCN

L3DTT Defines layer 3 data terminal type. Use DCE for all direct connectionsand DTE for connections to an X.25 DCN

30 A30828-X1150-N60-2-7620


Adapt these parameters to your needs. Examples of command files for the different con-nection variants are listed in chapter 6. Depending on your X.25 network you may haveto modify the standard timer and window values. For detailed information about modify-ing X.25 data link parameters, refer to your APS-specific CML, commandsCR X25LINK and MOD X25LINK.

3.2.2 CONF X25LINKThis command configures the specified X.25 data link.

3.2.2.1 PrerequisitesThe specified X25LINK must already have been created and must not be assigned toan X25PVC and an X25ROUTE at the same time. For configuration to ACT, the appro-priate LAU (e.g. X25LINK-0 --> LAU-0) must be in status ACT otherwise the link will becreated as unaccessible NAC.

3.2.2.2 DependenciesFor link configuration to ACT the link settings must match the settings of the connecteddevice (e.g. modem).



3.3 Creation of remote processorsAll O&M PCs with NetM (SiM) software connected to the CP via direct or X.25 DCN con-nections must be entered in the CP processor table so that they can be clearly identified.These entries are in the form of symbolic names. Each symbolic name of a remote pro-cessor is assigned to a processor type, depending on its application.

L3TCB Defines the channel range to be used for incoming and outgoingcalls. Use L3TCB=36&&85 as this is the default value of the OMTsoftware of the OS

L2N1 Defines layer 2 data packet size N1L2LAM Defines how to activate the X.25 link. This parameter allows only one

parameter value. INITIA (Initiator), the X.25 link activates itself orRESPON (Responder), the X.25 link is activated by the distant ex-change.

Parameter Possible values Default value NoteX25LINK 0 ... 23 OST PLA, MBL, ACT

Tab. 3.7 Command syntax for CONF X25LINK

X25LINK Defines the X.25 data link e.g. X25LINK-0OST Defines the status you want to change to

A30828-X1150-N60-2-7620 31



3.3.1 CR PROThis command creates a new (remote) processor with its processor type in the CP pro-cessor database.The local processor name (CP name PROTYP=SSP) can be entered or modified withENTR EXCHID; for more details refer to your CP CML.For display, modification and cancellation of remote processor data, commandsDISP PRO, MOD PRO and CAN PRO are available.

3.3.1.1 PrerequisitesNone

3.3.1.2 DependenciesThe new processor name must be unique in the entire O&M system. The processortypes depend on the applications to be assigned to the processor, see chapter 3.3.1.3and chapter 3.5. For print dialog (application DIALG) and file transfer via FTNEA proto-col (application NEABx), processor type OMTS (PC with NetM (SiM) software) is used,for file transfer via FTAM processor type OSS is required.



3.4 Creation of OSI network addressesAn OSI network address must be defined for the CP (local processor) and all other re-mote processors (X.25 PCs) and their different applications. The OSI address consistsof the symbolic address name (ADRNAM) and the address value of the network serviceaccess point (NSADR). The NSADR corresponds to the NSAP address described inchapter 1.5.

NB: A maximum of 50 processors (DIALG) can be created, and in theory, a maxi-mum of 50 SVCs can be set up. Of those 50 SVCs, however, only 32 can bedialog SVCs (session register limit).

Parameter Possible values Default value NotePRONAM 1... 8 characters set in "xxx" PROTYP OMTS, OSS OSS for application

FTAM, OMTS for DIALGand NEABx; see also 3.5

Tab. 3.8 Command syntax for CR PRO

PRONAM Defines the symbolic name of the remote processor to be created e.g.X.25PC1.

PROTYP Defines the processor type.

32 A30828-X1150-N60-2-7620


3.4.1 CR OSIADRThis command creates an OSI address in an X.25 network (X25, X25LC or ISDN) anddefines a symbolic address name.For display, modification and cancellation of OSI addresses commands DISP OSIADR,MOD OSIADR and CAN OSIADR are available.

3.4.1.1 PrerequisitesNone.

3.4.1.2 DependenciesThe symbolic address name must start with OSI... and must be unique in the entire sys-tem.

For remote addresses parameter LOCADR is necessary.The network type (parameter NET) defines the AFI value according to the table.NSADR values for IDI and DSP depend on the AFI value.Local OSI addresses are limited to 120.A total of 511 OSI addresses can be created (local and remote together).


Possible NSADR values for AFI (Authority and Format Identifier), IDI (Initiator DomainIdentifier) and DSP (Domain Specific Part):


Note

ADRNAM OSIxxxxx (up to 8 char-acters)

name must start with OSI

NSADR (AFI-IDI-DSP) depends on NET valuesee table 3.10

[LOCADR] OSIxxxxx (up to 8 char-acters)

for remote addresses only,name must start with OSI

NET X25LC, X25, ISDN X25LC X25LC for direct connectionX25 for connection via X.25DCN

Tab. 3.9 Command syntax for CR OSIADR

Networktype

AFI IDI zeros onleft

max.length

DSP syntax max.length

X25LC 48 1 (IDI=0) decimal digits 3848 1 (IDI=0) decimal digits 24

X25 36 no 14 decimal digits 24

Tab. 3.10 Possible NSADR values for AFI, IDI and DSP

A30828-X1150-N60-2-7620 33



3.4.2 Modification of OSI addressesThe command MOD OSIADR with its parameters ADRNAM , NSADR and NNSADR, isimportant for the modification of an OSI address that has already been created. Thestandard practice is to write this command in the log file.

3.4.2.1 MOD OSIADRThe command modifies either the AFI, the IDI, the DSP or the IDP (AFI and IDI) as apart of the NSAP (Network Service Access Point). AFI (Authority and Format Identifier),IDI (Initiator Domain Identifier) and DSP (Domain Specific Part) are data units. The partsAFI and IDI together are known as the IDP (Initial Domain Part).

3.4.2.2 PrerequisitesThe OSI address must already have been created with the command CR OSIADR in theCP database.

3.4.2.3 DependenciesIf IDI is already connected with data terminal equipment, the new DSP length, i.e. thesub-addressing length, which is defined using the command CR X25DTE, cannot be ex-tended.


37 no 14 binary octets 952 yes 14 decimal digits 2453 yes 14 binary octets 9

ISDN 44 no 15 decimal digits 2345 no 15 binary octets 958 yes 15 decimal digits 2359 yes 15 binary octets 9

If zeros on left = yes is specified for IDI values, input of left zeros is permitted e.g.00041278.

Tab. 3.10 Possible NSADR values for AFI, IDI and DSP


Note

ADRNAM OSIxxxxx (up to 8 char-acters)

Name must start with OSI

NSADR (AFI-IDI-DSP) Depends on the NET-value,see table

Tab. 3.11 Command syntax for MOD OSIADR

34 A30828-X1150-N60-2-7620



3.4.3 CAN OSIADRThis command cancels an OSI address in an X.25 network (X25, X25LC or ISDN). Thismight be necessary if you decide to change the NET parameter of an OSI addressname, although this is not possible with MOD OSIADR. In this case you have to deletethe OSI address entry and create a new one.

3.4.3.1 PrerequisitesThe OSI address must already have been created in the CP database.

3.4.3.2 DependenciesAn OSI address cannot be cancelled if it is the only address assigned to a DTE (more than one OSI address can be as-

signed to a DTE); in such a case the DTE must be cancelled first. applications are still assigned to itA local OSI address can only be cancelled if no remote addresses are assigned to it.


3.4.3.4 Parameter descriptionADRNAM Specifies the symbolic name of the OSI address

NNSADR (AFI-IDI-DSP) New NSAP address, de-pends on the NET-value,see table

Tab. 3.11 Command syntax for MOD OSIADR

ADRNAM Specified the symbolic name of the OSI address.NSADR Defines the NSAP address in the format AFI-IDI-DSP. See table.NNSADR Defines the new NSAP address in the format AFI-IDI-DSP. See ta-

ble.

Tab. 3.12 Parameter description


Note

ADRNAM OSIxxxxx (up to 8 characters) name must start with OSI

Tab. 3.13 Command syntax for CAN OSIADR

A30828-X1150-N60-2-7620 35



3.5 Definition of ApplicationsApplications are assigned to OSI addresses and processors. Applications such as dia-log or file transfer in the OSI network depend on the type of the processor they were cre-ated for. CP applications are defined as "local " applications whereas the appropriateapplications for remote processors are defined as "remote" applications. Creating re-mote applications triggers a message for the assigned local application indicating that anew remote application is to be created. The local application has to confirm this, other-wise the command will not be executed.For print dialog, the application DIALG is required, for file transfer applications NEABD,NEABI and NEABR are available. See table 3.15 for possible combinations of processortypes and applications.For modification, display and cancellation of applications, commands MOD APPL,DISP APPL and CAN APPL are available.

3.5.1 CR APPLThis command creates an application for a specific processor.

3.5.1.1 PrerequisitesThe assigned processor and OSI address name must already have been created.

3.5.1.2 DependenciesAssigning two different OSI addresses with the same IDI value to two different proces-sors is not possible, except for network type X25LC as this always requires IDI =0.A remote application can be only created if the local application required for communi-cation has already been created.If two OSI addresses are specified for one remote application, both of them must pointto the same local application.Selectors are only available for applications FTAM(I,R), SMMLB and SMMLT;see table 3.15



Note

APPLID DIALG, NEABx, FTAM (1 .. 5char.)

PRONAM 1 ... 8 char. enclosed in "xx" ADRNAM OSIxxxxx (up to 8 characters) name must start with

OSI[AUT] (1 ... 6 characters) [TSEL] (1 ... 32 characters)

Tab. 3.14 Command syntax for CR APPL

36 A30828-X1150-N60-2-7620


The parameters for file transfer have the following meanings:

3.5.2 CR X25DTEThis command creates a data terminal equipment in the CP database and assigns it toa previously created OSI address name.For display, modification and cancellation of DTE entries commands DISP X25DTE,MOD X25DTE and CAN X25DTE are available.

3.5.2.1 PrerequisitesThe specified OSI address (ADRNAM) must already have been created.An application must be created and assigned to the specified address name.

3.5.2.2 DependenciesDTE facilities can only be defined for remote DTEs.

[SSEL] (1 ... 16 characters) [PSEL] (1 ... 16 characters) [MUX] Y, YES NO[AET] 0...999999

range of decimal number

[APQ] 0...999999range of decimal number

[AEQ] 0...214748...range of decimal number

Localapplication

Remoteapplication

Remote proces-sor type

Note

DIALG DIALG OMTS for print dialog protocolNEABD NEABD

NEABRNEABI

OMTS orOMTA file for transfer

FTAMR FTAMFTAMIDIALOGNEABx

OSS file for transfer withhosts e.g. BS2000

Tab. 3.15 Applications in the OSI data network

NEABI file transfers can only be started from the remote processor (I=Initiator)NEABR files can only be received by the remote processor (R=Responder)NEABD both file transfer directions are possible

Tab. 3.14 Command syntax for CR APPL

A30828-X1150-N60-2-7620 37



If more than one address name is specified, all assigned OSI addresses must have thesame IDI value and belong to the same processor and network type. For the parameterADRNAM as well, only one address can be entered, and all further ADRNAMs whichhave the same IDE value in the NSADR are combined in this DTE. Entry for parameter DTEADR in network X25LC is not permitted here; DTEADR is

mandatory for remote DTE in network types X25 and ISDN. Local DTEADR in allnetwork types and remote DTEADR in network type X25LC must be entered in com-mandCR X25ROUTE.

Closed user group (CUG) facilities are only available in network type X.25 and incombination with AEF facilities (AEFIN, AEFOUT). Only one CUG can be created inthe database per DTE.

CUGIND can be entered only in combination with one of the CUG facilities(CUGBAS, CUGOBAS, BCUG). The length must be two digits for FACIL=CUGBASand FACIL=CUGOBAS and exactly four digits for FACIL=BCUG.

Parameter SALEN is mandatory for local DTEs, if a remote DTE already exists with-out specified AEFOUT facility.

Parameter SALEN is mandatory for remote DTEs, if no AEFIN facility is specified. If parameter SALEN is mandatory, the DTE address length must not exceed the val-

ue 15 minus SALEN length. The AEFOUT facility must be created for remote DTEs, if the local DTE was created

without SALEN or if the DSP length of one of the assigned OSI addresses exceedsthe value specified with parameter SALEN.


Note: For communication with NetMs it is necessary to specify DTE facilities AEFINand AEFOUT.


Note

DTENAM (1 ... 8 characters) ADRNAM OSIxxxxx

(up to 8 characters) multiple addresses can

be linked with &[NET] X25LC, X25, ISDN must match network

type of used ADRNAM[DTEADR] NET=X25: up to 14 digits mandatory for remote

DTE only!NET=ISDN: up to 15 digits [FACIL] AEFIN, AEFOUT(CUGBAS,

CUGOBAS, BCUG) multiple facilities can

be linked with &[CUGIND] (1 ... 4 decimal numbers) values only in conjunc-

tion with CUG facilitiesin parameter [FACIL]!

[LINKGRP] NO, YES N[SALEN] (1 decimal number 0 ... 14)

Tab. 3.16 Command syntax for CR X25DTE

38 A30828-X1150-N60-2-7620



3.5.3 CR X25ROUTEThis command creates a route with its route facilities for a data terminal equipment(DTE) and assigns it to a particular X25LINK. This is required for all local DTE and forremote DTE in network type X25LC.For display and cancellation of X.25 routes, commands DISP X25ROUTE andCAN X25ROUTE are available.

3.5.4 Parameter description

DTENAM Specifies the symbolic name of the data terminal equipmentADRNAM Defines the symbolic name of the OSI address to be used[NET] Specifies the type of network type in which the DTE is to be created.[DTEADR] Specifies the DTE address[FACIL] Defines whether the address extension field (AEF) is used for in-

coming and outgoing calls and if closed user group (CUG) facilitiesare to be used.

[CUGIND] Specifies the CUG index, if CUG facilities are administered with[FACIL].

[LINKGRP] For redundancy reasons, more than one route (link) can be definedfor a DTE as a link group . For LINKGRP=YES more than one routecan be created for a DTE with CR X25ROUTE

[SALEN] Only necessary if no AEF facilities are defined. (Specifies the max.number of decimal digits that can be used for subaddressing in theaddress field (AF))

APPLID Defines the application for the specified processor.PRONAM Specifies the processor (symbolic name) for which the application is to be

created.ADRNAM Specifies the symbolic name of the OSI address to be used for this appli-

cation.[AUT] Specifies an authorization for dialog applications. The authorization must

have been created with ENTR AUT and specified for dialog applications.

For applications such as mobile radio (D900 administration), selectors can be used.[TSEL][SSEL][PSEL][MUX][AET][APQ][AEQ]

refer to your CML

A30828-X1150-N60-2-7620 39



3.6 Creation of DTE Addresses and X25 RoutesAfter OSI addresses and the appropriate applications have been defined they have tobe assigned to data terminal equipment addresses (DTEADR) which identify the physi-cal device (remote processor) in the specified network.In network type X25LC, at least one route has to be specified for each DTE address,whereas network type X.25 only requires an X25ROUTE for local DTEs.For redundancy a second (alternative) route for one and the same DTE (processor) canbe created and assigned to a different X.25 link to increase O&M reliability. Use aX25LINK of another LAU for the second (redundant) route to guarantee route redundan-cy in the case of LAU failure.Combining two routes can be achieved with parameter LINKGRP=YES in commandCR X25DTE; the DTENAM specified with CR X25DTE has to be used for bothX25ROUTEs.

3.6.1 PrerequisitesThe specified DTE name must already have been created with CR X25DTE.The X25LINK to which the DTE is to be attached must already have been created(CR X25DTE) and must be in operating state PLA or MBL for local route creation.

3.6.1.1 Dependencies X.25 routes have to be created for all local DTE in all network types and for all re-

mote DTE in network type X25LC. In network type X25LC, local routes have to be created before remote routes. X25 routes for remote DTE are only possible in network type X25LC. X25LINK and DTE must be assigned to the same network types. All local DTE addresses and all remote DTE (in network type X25LC) must be en-

tered with parameter DTEADR (DTE addresses for remote DTE in network typesX.25 and ISDN are mandatory in CR X25DTE).

Multiple X.25 routes, assigned to different X25LINK, can be configured for oneX25DTE as a link group to increase redundancy. This is possible with multiple X.25routes assigned to one and the same DTE name created with MML commandCR X25DTE with its parameter LINKGRP=YES.

More than one route can be created for a DTE if a link group was specified(LINKGRP=Y in CR X25DTE); all routes should have the same route facilities. Thedifferent routes may have the same DTE address in one and the same link group.

If parameter SALEN had to be specified in CR X25DTE (see chapter 3.5.2) the DTEaddress length must not exceed the value 15 minus SALEN. The address fieldlength (AF) is limited to 15 digits and consists of the DTEADR and the DSP part ofthe NSAP address, if no AEF facilities are defined.



Note

ROUTNAM (1 ... 8 characters)

Tab. 3.17 Command syntax for CR X25ROUTE

40 A30828-X1150-N60-2-7620


3.6.2 Parameter description

DTENAM (1 ... 8 characters) X25LINK decimal numbers 0 ... 23 DTEADR decimal number 1 ... 15 digits [FACIL] FLOWNEG, PCKSNS, PCKSNS values can be

linked with &[WNDSZ] (window size in) - (window size out)

decimal numbers 1 ... 7 required for FACIL=

FLOWNEG only![PCKSZ] (packet size in) - (packet size out)

decimal numbers 16 ... 4096 required forFACIL=

FLOWNEG only![WNDSZNS] (non standard window size in) - (non

standard window size out)decimal numbers 1 ... 7

required for FACIL=PCKSNS only!

[PCKSZNS] (non standard packet size in) -(non standard packet size out)decimal numbers 16 ... 4096

required for FACIL=PCKSNS only!

Tab. 3.17 Command syntax for CR X25ROUTE

ROUTNAM Specifies the symbolic name of the routeDTENAM Assigns the DTE name for which the route is to be createdX25LINK Defines the X25LINK to be used for this routeDTEADR Specifies the address of the DTE. This address value is received

from the X.25 node administration if an X.25 DCN is used. In net-work type X25LC this value can be chosen freely from unused val-ues.

[FACIL] Specifies the layer 3-specific facilities. WNDSNS and PCKSNS areto be entered if non-standard values are used for window size andpacket size. Layer 3 standard values are: Window size=2, Packetsize=128

[WNDSZ] Specifies the non-standard window size if FACIL=FLOWNEG inthe format INSIZE-OUTSIZE

[PCKSZ] Specifies the non-standard window size if FACIL=FLOWNEG inthe format INSIZE-OUTSIZE

[WNDSZNS] Specifies the non-standard window size if FACIL=WNDSNS in theformat INSIZE-OUTSIZE

[PCKSZNS] Specifies the window size if FACIL=WNDSNS in the format IN-SIZE-OUTSIZEThe layer 2 packet size must be large enough for the layer 3 packetsize, hence the value PCKSZNS +7 must be equal to or greaterthan the value of parameter L2N1 of the X25LINK used(CR X25LINK).Example: If you want to change the layer 3 standard packet sizefrom 128 to 256, parameter L2N1 in command CR X25LINK has tobe changed to value 263

A30828-X1150-N60-2-7620 41



3.7 Parameter value dependenciesThe following chart shows how parameter values depend on previously entered CPMML command parameter values that are required for creation of a specific application,for the local processor (CP) and the remote processor(s).For creation of local applications, the CP processor name is required as it was originallyentered with MML command ENTR EXCHID:NAME=... . This name can be found outby means of the command DISP PRO:PRONAM=X; use the processor name with pro-cessor type SSP!

42 A30828-X1150-N60-2-7620


Fig. 3.2 Parameter value dependencies

CR PRO:PRONAM=....;PROTYP=.....;

DISP PRO:PRONAM=x;(Protyp=SSP -> Name=...)

Local Remote

CR APPL:ADRNAM=OSI....,APPLID=.....,PRONAM=.....,[,AUT=.....].....

CR OSIADR:ADRNAM=OSI.....,NSADR=.....,NET=.....,[,LOCADR=.....];

CR X25DTE:DTENAM=.....,ADRNAM=OSI.....,[DTEADR=.....].....

CR X25ROUTE:DTENAM=.....,ROUTNAM=.....,X25LINK=.....,[,FACIL=.....].....

CR APPL:ADRNAM=OSI....,APPLID=.....,PRONAM=.....,[,AUT=.....].....

CR OSIADR:ADRNAM=OSI.....,NSADR=.....,NET=.....,[,LOCADR=.....];

CR X25DTE:DTENAM=.....,ADRNAM=OSI.....,[DTEADR=.....].....

CR X25ROUTE:DTENAM=.....,ROUTNAM=.....,X25LINK=.....,[,FACIL=.....].....

A30828-X1150-N60-2-7620 43



4 PC AdministrationBefore you start installing and administering your PC with NetM (SiM) software for O&Mvia X.25 networks, have the required X.25 database files for the connected CP readybecause all the relevant parameters for remote processors are defined then. During theO&M software installation phase, parameters such as OSI and DTE addresses and theprocessor name of your specific PC with NetM (SiM) software are requested and haveto be entered accordingly.

4.1 O&M SW installationThe installation and configuration of the O&M software via X.25 networks requires anoperating system, NetM (SiM) software and the EICON X.25 driver package. For moredetails of the installation process, please refer to chapter 2.3 of this document, theMMN:PC and the current NetM documentation.

4.1.1 O&M SW installation hintsIn the course of installation according to the current NetM documentation, the followinginformation is requested for installation of the user interface (in bold type below).Which kind of File Transfer is used for this PC: 1 .... X.25 - SVC (Switched Virtual Circuit) 2 .... X.25 - PVC (Permanent Virtual Circuit)

Please enter the name of your PC (must match CP configuration) or press to use the default name unix:

Please enter the DTE address (Data Terminal Equipment):(The DTE address consists of max. 15 decimal digits)

Please enter the NSAP address for Print Dialog (Network Service Access Point):

Please enter the NSAP for File transfer

Installing the TaskDBIs the TaskDB to be installed?

i Select 1 (SVC) as this is mandatory if the application print dialog (DIALG) and file trans-fer (NEABx) are specified for this PC in the CP database

i Here you must enter the processor name as specified for your PC with CR PRO in theCP processor table e.g. NetM0.

i Enter the DTE address as you specified it for this PC with parameter DTEADR in CPcommand CR X25DTE and/or CR X25ROUTE.

i Enter the NSAP address as you specified it for the application DIALG (print dialog)for this PC with parameter NSADR in CP command CR OSIADR. The format isAFI-IDI-DSP e.g. 48-0-11000.

i Enter the NSAP address as you specified it for the application NEABx (file transfer) forthis PC with parameter NSADR in CP command CR OSIADR. The format isAFI-IDI-DSP e.g. 48-0-55000.

44 A30828-X1150-N60-2-7620


A TaskDB contains all the data such as MML, Q3 and SNMP commands, required foroperating network elements.

i If the trunk/subscriber line software (database) is to be installed on this PC, at least oneTaskDB is required. It is also possible to install several CP TaskDBs, e.g. for differentnetwork elements that are to run on the PC (for example in an X.25 DCN). For the sakeof a more user-friendly system, it is advisable to install the appropriate CP TaskDB foreach network element version, either during the O&M software installation or later andin accordance with MMN:PC Register "CP-EMML-DAT, Installation of the CP-EMMLDatabase" or the current NetM documentation.

When the above-mentioned parameters are entered during installation, all PC databaseentries for the PC are created. PC database entries for the connected CP(s), PRONAMsand X.25DTEs have to be created additionally via the BMML Workbench.

A30828-X1150-N60-2-7620 45



4.1.2 Example of a PC databaseThe following example of a PC database displays all PC entries as they are created forthe remote processor "NetM0" in the CP command file X25DIR02. The commands fordirect connections can be found in chapter 6.1..The processor table of the PC database can be displayed by means of the BMML Work-bench:Start the BMML Workbench via the NetM softwareSelect the form DISP PRO via the menu item Task -> Quick Select ... .After installation of the NetM software, DISP PRO:PRONAM=X; shows the following de-fault entries:

7916COMMAND SUBMITTED

T52/T520.MPUSA0/DBPXEK1V1665P080/203 02-03-13 08:34:107916 NetM NME34 2970/01738

DISPPRO:PRONAM=X; EXEC'D

PROCESSORS IN THE O&M-NETWORK

PRONAM PROTYP SYT PART1 SYT PART2 SYT PART3 SYT PART4---------+-------+---------------------------------------------

ALFONS OSS 0000000001-0000000037BS2A BS2CARLO OSS 0000000001-0000000030CLARA OSS 0000000001-0000000039CSE120 OSS 0000000001-0000000001CSE121 OSS 0000000001-0000000002CSE180 OSS 0000000001-0000000003CSE181 OSS 0000000001-0000000004DCP2 PDCPDRDCP3 PDCPDRDORTEL OSS 0000000001-0000000035ENM314 OSSFJMNA2 MVSFRANZ OSS 0000000001-0000000033FRIEDA OSS 0000000001-0000000031GUNHILDA OSS 0000000001-0000000036KERMET OSS 0000000001-0000000020NETMCTS OSS 0000000001-0000000000SPURLI OSS 0000000001-0000000032T52 SSP 0000000000-0000000000TRUDI OSS 0000000001-0000000034END JOB 7916

46 A30828-X1150-N60-2-7620


The X.25DTE database entries, entered after the PC software installation, can be dis-played using DISP X25DTE .Select the form DISP X25DTE via the menu item Task -> Quick Select ... .After installation of the PC operating software, DISP X25DTE:TYPE=LOCAL; orREMOTE; displays the following default entries if the values are entered in accordancewith chapter 4.1.1 as they are required for the PC "O&MPC0" and listed in the commandfile example X25DIR01.CMD. The parameter values in bold type are defined during theO&MPC software installation:



DISPX25DTE:TYPE=LOCAL; EXEC'D

DTENAM/ TYPE/ SALEN/ MAX LNKGRP/ LINK GROUP IDI/ DTEPRONAM NET CUGIND SVC BIDIR STATE DTEADR FACIL--------+------+------+----+-------+----------+---------------+---------

DTELEWSP LOCAL 02 NO 1890501351T52 X25 NODTELENM1 LOCAL NO 0T52 X25LC NOEND JOB 8010



DISPX25DTE:TYPE=REMOTE; EXEC'D

DTENAM/ TYPE/ SALEN/ MAX LNKGRP/ LINK GROUP IDI/ DTEPRONAM NET CUGIND SVC BIDIR STATE DTEADR FACIL--------+------+------+----+-------+----------+---------------+---------

DTER120 REMOTE NO 1890502471CSE120 X25 NO 1890502471 AEFIN & AEFOUTDTER121 REMOTE NO 1890503260CSE121 X25 NO 1890503260 AEFIN & AEFOUTDTER180 REMOTE NO 1890504350CSE180 X25 NO 1890504350 AEFIN & AEFOUTDTER181 REMOTE NO 1890503311CSE181 X25 NO 1890503311 AEFIN & AEFOUTDTERENM1 REMOTE NO 0

A30828-X1150-N60-2-7620 47



NETMCTS X25LC NO AEFIN & AEFOUTDTERE30 REMOTE NO 1890504451CARLO X25 NO 1890504451 AEFIN & AEFOUTDTERE31 REMOTE NO 1890504441FRIEDA X25 NO 1890504441 AEFIN & AEFOUTDTERE32 REMOTE NO 1890504510SPURLI X25 NO 1890504510 AEFIN & AEFOUTDTERE33 REMOTE NO 1890503460FRANZ X25 NO 1890503460 AEFIN & AEFOUTDTERE34 REMOTE NO 1890503470TRUDI X25 NO 1890503470 AEFIN & AEFOUTDTERE35 REMOTE NO 1890504501DORTEL X25 NO 1890504501 AEFIN & AEFOUTDTERE36 REMOTE NO 1890504450GUNHILDA X25 NO 1890504450 AEFIN & AEFOUTDTERE37 REMOTE NO 1890504511ALFONS X25 NO 1890504511 AEFIN & AEFOUTDTERE39 REMOTE NO 1890504440CLARA X25 NO 1890504440 AEFIN & AEFOUTDTER314 REMOTE NO 1890502470ENM314 X25 NO 1890502470 AEFIN & AEFOUTDTERE49 REMOTE NO 1890503471KERMET X25 NO 1890503471 AEFIN & AEFOUTEND JOB 8091

When file transfers are made from the CP to the PC the symbolic DTENAM/PRONAMfor the application NEABR must be the same as the processor name of the PC in theCP database, as specified in CR PRO, e.g. NetM0.For every other processor (CPs as well as other PCs in network type X.25) to whichthe PC with NetM (SiM) software is connected or with which it is to exchange files, ad-ditional PC database entries are necessary.

4.2 PC Database AdministrationFor each CP to which files are transferred and dialog sessions are established, a pro-cessor name and an X25DTE have to be created in the PC database for the print dialogand for the file transfer application, using the BMML Workbench.The following PC entries have to be created for the CP (processor name "CP1") to whichthe PC with NetM (SiM) software (processor name "NetM0") is directly connected, in ac-cordance with the command file example (X25DIR02.CMD):1. CR X25DTE creates the DTENAM/PRONAM for print dialog application2. CR X25DTE creates the DTENAM/PRONAM for file transfer application

48 A30828-X1150-N60-2-7620


3. CR PRO creates the CP name in the PC database and assignsDTENAM/PRONAMs for the different applications and the TaskDB if required.

Symbolic names for DTENAM/PRONAM and the name for the CP can be chosen freely.However, to avoid confusion it is advisable to use the CP name as it was defined in theCP processor table with MML command ENTR EXCHID ; this applies particularly in thecase of tables with several CP entries. The name of the CP can be determined using theCP command DISP PRO

Date post:	05-Sep-2015
Category:	Documents
Upload:	sinasabikona
View:	362 times
Download:	24 times

ewsd x25 sys admin

Documents