Megabox - Megapac - Megafrad: "600B" Software Configuration Manual Guide To Parameters

E
MegaBOX - MegaPAC - MegaFRAD

MULTIPROTOCOL CONCENTRATOR / SWITCH
"600B" SOFTWARE CONFIGURATION MANUAL
GUIDE TO PARAMETERS
S
E Manual N5682000901 - Edition 1 - March 1999
Megabox - Megapac - Megafrad - "600B" software configuration manual
MegaBOX - MegaPAC - MegaFRAD

MULTIPROTOCOL CONCENTRATOR / SWITCH
"600B" SOFTWARE CONFIGURATION MANUAL
GUIDE TO PARAMETERS
X
MEGABO
RESET
ABORT
STATUS
MEGAPAC VME-21B
STATUS
TX T1 T1 T1 T1 T1 T1
HALT RX R1 R1 R1 R1 R1 R1
SUPER CN T2 T2 T2 T2 T2 T2
USER R2 R2 R2 R2 R2 R2
IRQ T3 T3 T3 T3 T3 T3
BUS R3 R3 R3 R3 R3 R3
VIRQ T4 T4 T4 T4 T4 T4
+5V R4 R4 R4 R4 R4 R4
+12V
ABORT BM BM BM BM BM BM BM
BE BE BE BE BE BE BE
RESET
J
1
AUI
J
2
CPU40 ETH XIO-B XIO-B XIO-B XIO-B XIO-B XIO-B SIO-08 SIO-08 SIO-08 SIO-08 SIO-08 SIO-08 SIO-08 SIO-08 SIO-08 SIO-08 SIO-08 SIO-08
+ 12V
- 12V
+ 5V
fusible
I
+ 12V
- 12V
+ 5V
0
fusible
The contents of this manual must not be reproduced or used without the permission of E Page i
The contents of this manual must not be reproduced or used without the permission of E Page ii
Introduction to this manual
For whom it is written
This document is written for "network" operators wishing to learn the fundamentals of how the Megapac
multiprotocol PABX operates. Its compact, thematic approach should provide rapid access to the basic
information needed to configure the software.
Content
The "Parameter guide" is organized logically, beginning with a review of general features and a
description of basic principles, followed by a second section covering operating procedures, and
describing all the commands.
The third section concerns Megapac memory and provides details for the parameters to be taken into
consideration before starting to set up the links and their associated logical channels.
The next section describes all the "descriptors" which go to make up the multiprotocol nature of the
Megapac, and then the routing mechanisms.
The next sections cover the various units for which parameters have to be set: link "descriptors" and
logical "resources" which are vital in configuring the PABX.
First to be described are the two link modes: synchronous (TYPE/ X25 descriptor) and
asynchronous (TYPE/ TERM descriptor).
Then come the many configuration options for local area network connections.
The final sections describe the descriptors used in the IBM environment.
Throughout the tables which form the very structure of the sections, the information given should be
sufficient for the more commonly encountered situations.
Conventions
The following typographical conventions are used throughout this document:
☞ This symbol indicates an action that can or should be undertaken by the user.
☛ This symbol indicates important information in the text.
▲ This symbol indicates the way Megapac responds to the user action.
The contents of this manual must not be reproduced or used without the permission of E Page iii
The contents of this manual must not be reproduced or used without the permission of E Page iv
Contents
INTRODUCTION TO THIS MANUAL.................................................................................................................. iii

1. GENERAL .......................................................................................................................................... 1-1
2. OPERATING PROCEDURES ................................................................................................................... 2-1
3. MEMORY CONFIGURATION ................................................................................................................... 3-1
4. OVERVIEW OF LINK DESCRIPTORS ........................................................................................................ 4-1
5. SYSTEM DESCRIPTORS........................................................................................................................ 5-1
6. ROUTING BY X.25 TABLE ..................................................................................................................... 6-1
7. ROUTING BY MAC TABLE .................................................................................................................... 7-1
8. OTHER TABLES .................................................................................................................................. 8-1
9. TYPE/ X25 DESCRIPTOR .................................................................................................................... 9-1
10. GIS BOARD: "S0" ISDN INTERFACE..................................................................................................10-1
11. ISDN BOARD FOR MEGAPAC ESL - MEGAFRAD..................................................................................11-1
12. "PRI-64" (30B+D) PRIMARY ACCESS BOARD ......................................................................................12-1
13. TYPE/ HDLC DESCRIPTOR .............................................................................................................13-1
14. TYPE/ NFRM DESCRIPTORS ...........................................................................................................14-1
15. TYPE/ PPP DESCRIPTOR ................................................................................................................15-1
16. TYPE/ TERM DESCRIPTOR .............................................................................................................16-1
17. PAD PARAMETERS ..........................................................................................................................17-1
18. TYPE/ CONS AND DLCX DESCRIPTOR ............................................................................................18-1
19. TYPE/ LAN AND TLAN DESCRIPTORS ..............................................................................................19-1
20. TYPE/ IP AND TIP DESCRIPTORS .....................................................................................................20-1
21. TYPE/ IPX AND TIPX DESCRIPTORS ................................................................................................21-1
22. TYPE/ ROUT DESCRIPTOR .............................................................................................................22-1
23. TYPE/ SNMP DESCRIPTOR .............................................................................................................23-1
24. TYPE/ MULT DESCRIPTOR .............................................................................................................24-1
25. TYPE/ V25B DESCRIPTOR ..............................................................................................................25-1
26. TYPE/ SDLC - QLLC DESCRIPTOR .................................................................................................26-1
27. TYPE/ CLUS DESCRIPTOR..............................................................................................................27-1
28. TYPE/ MAP DESCRIPTOR ...............................................................................................................28-1
29. TYPE/ DLC AND EDLC DESCRIPTOR ...............................................................................................29-1
30. TYPE/ SCOP DESCRIPTOR .............................................................................................................30-1
31. STATISTICS.....................................................................................................................................31-1
32. SYSTEM MESSAGES .........................................................................................................................32-1
33. GLOSSARY......................................................................................................................................33-1
The contents of this manual must not be reproduced or used without the permission of E Page v
The contents of this manual must not be reproduced or used without the permission of E Page vi
Contents
INTRODUCTION TO THIS MANUAL .................................................................................................... iii

FOR WHOM IT IS WRITTEN .......................................................................................................................... iii
CONTENT ................................................................................................................................................. iii
CONVENTIONS .......................................................................................................................................... iii
1. GENERAL ....................................................................................................................................... 1-1
1.1 "DESCRIPTORS" AND "RESOURCES".................................................................................................... 1-1
1.2 TABLES ........................................................................................................................................... 1-2
1.3 "RESOURCE" NAMES ......................................................................................................................... 1-2
1.4 ROUTING PRINCIPLES ....................................................................................................................... 1-3
1.4.1 Different routings ..................................................................................................................... 1-3
1.5 "RESOURCE" IDENTIFICATION............................................................................................................. 1-4
1.5.1 Resource NAME without wild cards ......................................................................................... 1-4
1.5.2 Resource NAME with « ∗ » wild cards...................................................................................... 1-5
1.5.3 Hunt group............................................................................................................................... 1-6
1.5.3.1 « " " " " » resource NAME ................................................................................................................. 1-6
1.5.3.2 « " ∗ ∗ ∗ » resource NAME ............................................................................................................... 1-7
1.6 PRINCIPLES OF ROUTING BY PRIORITY: "CP ≥ RP" ............................................................................... 1-8
1.7 "LOOP BAR PRIORITY" MECHANISM ....................................................................................................1-10
1.8 EXAMPLE OF ROUTING PRIORITY ........................................................................................................1-11
1.9 "LINE GROUP" LOAD BALANCING........................................................................................................1-14
1.10 « LINE GROUP » OVERFLOW ..........................................................................................................1-15
1.11 RESCUE LINK MONITORING ..............................................................................................................1-16
1.11.1 Link monitoring with transports..............................................................................................1-16
1.11.2 Link monitoring without transport...........................................................................................1-16
1.12 LINK SPEED ...................................................................................................................................1-17
1.13 BANDWIDTH MANAGEMENT.............................................................................................................1-18
1.13.1 On the X.25 link ....................................................................................................................1-18
1.13.2 On the Frame Relay link .......................................................................................................1-18
1.14 SOFTWARE VERSIONS COMPATIBILITY ..............................................................................................1-18
1.15 BLOCK DIAGRAM OF CALL ROUTING ..................................................................................................1-19
2. OPERATING PROCEDURES.......................................................................................................... 2-1
2.1 MAN/MACHINE INTERFACE ................................................................................................................. 2-1
2.1.1 Operator terminal..................................................................................................................... 2-1
2.1.2 Accessing the Megapac configuration ...................................................................................... 2-1
2.1.3 Operator commands ................................................................................................................ 2-2
2.2 NAVIGATION COMMANDS.................................................................................................................... 2-4
2.2.1 Direct access navigation commands ........................................................................................ 2-5
2.2.2 Sequential access navigation commands................................................................................. 2-6
2.3 FUNCTION COMMANDS ...................................................................................................................... 2-9
2.3.1 Display commands................................................................................................................... 2-9
2.3.2 Modification commands ..........................................................................................................2-13
2.3.3 Control commands..................................................................................................................2-16
2.4 SYSTEM COMMANDS ........................................................................................................................2-17
3. MEMORY CONFIGURATION.......................................................................................................... 3-1
3.1 « MEM » TABLE .............................................................................................................................. 3-2
3.2 DEFAULT CONFIGURATION ................................................................................................................. 3-3
3.2.1 Default configuration (system).................................................................................................. 3-3
E
3.2.2 Tailored default configuration ................................................................................................... 3-3
3.3 RETURNING TO THE DEFAULT CONFIGURATION (SYSTEM OR TAILORED) ................................................... 3-3
3.4 CONFIGURATION MEMORY ORGANIZATION............................................................................................ 3-4
3.5 PROCEDURE FOR CHANGING MEM SIZE ............................................................................................ 3-4
3.5.1 Changing table sizes (area 6)................................................................................................... 3-4
The contents of this manual must not be reproduced or used without the permission of
Page vii
3.6 MEGAPAC VME WITH CPU-V OR CPU-40 AND MEGAPAC - MEGABOX WITH CPU-E ...............................3-5
3.7 MEGAPAC VME WITH CPU-40 AND 640 SOFTWARE .............................................................................3-6
4. OVERVIEW OF LINK DESCRIPTORS.............................................................................................4-1
4.1 LINK DESCRIPTOR ASSIGNMENT RULES .................................................................................................4-1
4.2 LINK DESCRIPTORS - IDENTIFICATION AND PROTOCOLS SUPPORTED ........................................................4-4
4.3 GENERAL INFORMATION ON LOGICAL RESOURCES .................................................................................4-9
5. SYSTEM DESCRIPTORS ................................................................................................................5-1
5.1 BASE DESCRIPTOR AND RESOURCE BE00 ..........................................................................................5-1
5.1.1 BASE descriptor parameter ......................................................................................................5-1
5.1.2 Table of parameters for logical resource BE00 associated with BASE.......................................5-4
5.1.3 Control of the command port access rights ...............................................................................5-5
5.2 EPCI DESCRIPTOR AND LOGICAL RESOURCES EI00 ..............................................................................5-6
5.3 NMSC DESCRIPTOR AND RESOURCES NC00 .......................................................................................5-7
5.3.1 NMSC descriptor parameters....................................................................................................5-8
5.3.2 NC00 resource parameters.......................................................................................................5-8
6. ROUTING BY X.25 TABLE ..............................................................................................................6-1
6.1 DEFINITION OF THE X.25 TABLE ..........................................................................................................6-1
6.2 CREATING THE X.25 TABLE ................................................................................................................6-1
6.3 USING THE X.25 TABLE ......................................................................................................................6-2
6.4 ADDRESS TRANSLATION .....................................................................................................................6-3
6.4.1 Translation of destination address "T".......................................................................................6-3
6.4.2 Address translation and "ADDRESS GROUP" ..........................................................................6-4
6.4.3 Using copy (") and skip (#) characters.......................................................................................6-5
6.4.4 Inserting the source address "-" ................................................................................................6-6
6.5 MANIPULATING SOURCE ADDRESSES ...................................................................................................6-7
6.6 MANIPULATING USER DATA .................................................................................................................6-8
6.7 ROUTING ALGORITHM USING THE X.25 TABLE .......................................................................................6-9
7. ROUTING BY MAC TABLE .............................................................................................................7-1
7.1 MAC FILE SIZE ..................................................................................................................................7-1
7.2 STRUCTURE OF A MAC RECORD .........................................................................................................7-1
7.3 INPUT MAC PROGRAM .......................................................................................................................7-2
7.3.1 "FUNCTIONS" field of an input MAC program...........................................................................7-2
7.3.2 "OPTIONS" field of an input MAC program ...............................................................................7-4
7.3.3 "SELECTOR" field of an input MAC program ............................................................................7-5
7.3.4 "GENERATOR" field of an input MAC program.........................................................................7-5
7.3.5 Input MAC algorithm .................................................................................................................7-6
7.4 OUTPUT MAC PROGRAM .................................................................................................................7-10
7.4.1 "FUNCTIONS" field of an output MAC program ......................................................................7-10
7.4.2 "OPTIONS" field of an output MAC program ...........................................................................7-12
7.4.3 "SELECTOR" field of an output MAC program ........................................................................ 7-13
7.4.4 "GENERATOR" field of an output MAC program..................................................................... 7-13
7.4.5 Output MAC algorithm ............................................................................................................7-14
8. OTHER TABLES..............................................................................................................................8-1
8.1 PASS TABLE ....................................................................................................................................8-1
8.2 NAME TABLE ...................................................................................................................................8-2
8.3 MENU TABLE ...................................................................................................................................8-4
8.4 HELP TABLE ....................................................................................................................................8-6
8.5 ILAN TABLE......................................................................................................................................8-7
8.6 BILL TABLE ......................................................................................................................................8-9
8.7 ELOG TABLE..................................................................................................................................8-11
9. TYPE/ X25 DESCRIPTOR................................................................................................................9-1
E
9.1 GENERAL .........................................................................................................................................9-1
9.2 LINK CONFIGURATION PARAMETERS .....................................................................................................9-2
9.2.1 Fragmentation ........................................................................................................................9-11
9.2.2 "Recommendation X.32" XID identity check ............................................................................9-11
Page viii
9.3 BANDWIDTH MANAGEMENT ON THE X25 LINK: ....................................................................................9-12

9.3.1 Maximum link throughput ........................................................................................................9-12
9.3.2 Required throughput for an incoming call ................................................................................9-12
9.3.3 Call routing according to required throughput ..........................................................................9-13
9.3.4 Available throughput of a link ..................................................................................................9-13
9.3.5 Throughput assigned to an established virtual circuit...............................................................9-13
9.4 TRANSPORT LAYER CONFIGURATION ..................................................................................................9-15
9.4.1 Transport layer parameters.....................................................................................................9-16
9.4.2 Example of a class 3 transport configuration ...........................................................................9-18
9.4.3 Additional "transport" configuration information .......................................................................9-20
9.4.4 "Monitor" function of a transport link with backup ....................................................................9-21
9.4.4.1 Example ........................................................................................................................................ 9-22
9.5 RESOURCE CONFIGURATION PARAMETERS .........................................................................................9-23
9.6 INPUT MAC TABLE (X.25) ................................................................................................................9-26
9.6.1 "CAD, DAD, CUD, FAC" function ............................................................................................9-26
9.6.1.1 Example (CAD function and COPY Options) .................................................................................. 9-30
9.6.1.2 Example (CAD function and COPY+CAD Options) ......................................................................... 9-31
9.6.1.3 Example (DAD function and COPY+NOT Options) ......................................................................... 9-32
9.6.1.4 Example (CAD function and REJ, TLAT, TCAL Options) ................................................................ 9-33
9.6.1.5 Example (CAD function and JUMP option) ................................................................................. .... 9-34
9.6.1.6 Example (CUD function and REJ, TALK, TLAT Options) ................................................................ 9-35
9.6.1.7 Example (FAC function, THRU option) ........................................................................................... 9-36
9.6.1.8 Example (FAC function, FLAG option)............................................................................................ 9-37
9.6.2 Analysis of "Cause and Diagnostic".........................................................................................9-38
9.6.2.1 Example (ELSE function and TLAT, REJ Options).......................................................................... 9-38
9.6.2.2 Example (DAD, ELSE function and TLAT option) ........................................................................... 9-39
9.6.2.3 Example (DAD, ELSE function and TLAT, REJ Options) ................................................................ 9-40
9.6.2.4 Example (LIST, ELSE functions and TLAT, REJ Options)............................................................... 9-41
9.6.3 Mask on X3 parameters, "MASK" function ..............................................................................9-42
9.6.3.1 Example "MASK" ........................................................................................................................... 9-42
9.7 OUTPUT MAC TABLE (X25)..............................................................................................................9-43
9.7.1 Filtering on the calling DTE address........................................................................................9-43
9.7.2 Structure of the output MAC table ...........................................................................................9-44
9.7.2.1 Only in filtering mode ..................................................................................................................... 9-44
9.7.2.2 Only in "Facility Data" and "Call User Data" handling...................................................................... 9-44
9.7.2.3 Filtering and data handling use combined ...................................................................................... 9-44
9.7.3 "Facility Data" and "Call User Data" handling ..........................................................................9-45
9.7.3.1 "POSN" function ........................................................................................................ .................... 9-46
9.7.3.1.1 Example « POSN function » ............................................................................................ ........ 9-47
9.7.3.2 "INSE" function ........................................................................................................ ...................... 9-49
9.7.3.2.1 Example 1 (INSE function) ...................................................................................................... 9-51
9.7.3.2.2 Example 2 (INSE function) ...................................................................................................... 9-53
9.7.3.3 "DELE" function ............................................................................................................................. 9-54
9.7.3.3.1 Example (DELE function) ........................................................................................................ 9-55
9.7.3.4 "COPY" function ........................................................................................................ .................... 9-56
9.7.3.4.1 Example (COPY function) ....................................................................................................... 9-57
9.7.3.5 "MARK" function ............................................................................................................................ 9-58
9.7.3.5.1 Example (MARK function) .............................................................................................. ......... 9-59
9.7.3.6 "DATA" function ............................................................................................................................. 9-60
9.7.3.6.1 Example (DATA function) ........................................................................................................ 9-61
9.7.3.7 "EOF" function ......................................................................................................... ...................... 9-62
9.7.3.7.1 Example (EOF function) .......................................................................................................... 9-63
10. GIS BOARD: "S0" ISDN INTERFACE .........................................................................................10-1
10.1 INTRODUCTION ..............................................................................................................................10-1
10.2 MEGAPAC CONFIGURATION .............................................................................................................10-2
10.2.1 Operating modes ..................................................................................................................10-2
10.2.2 Correlation between the "descriptors" and physical ports.......................................................10-3
10.3 ISDN NUMBER ..............................................................................................................................10-3
10.4 LINK CONFIGURATION PARAMETERS IN NATIVE X25 MODE ...................................................................10-4
E
10.5 GIS BOARD CONFIGURATION ..........................................................................................................10-6
10.6 STRUCTURE OF THE GIS BOARD TABLES ..........................................................................................10-7
10.6.1 X.25 table syntax (GIS).........................................................................................................10-7
10.6.2 ISDN table syntax (GIS)........................................................................................................10-8
Page ix
10.6.2.1 GIS adapter ISDN address ........................................................................................................... 10-8

10.6.2.2 NAME = GIO1, GIO2 ..................................................................................................... .............. 10-8
10.6.3 LINK table syntax (GIS) ........................................................................................................10-9
10.6.4 ROUT table syntax (GIS) ....................................................................................................10-11
10.6.4.1 Incoming call routing ("IN" key) ...................................................................................... ............ 10-12
10.6.4.2 Outgoing call mode ("OUT" key)........................................................................................ ......... 10-12
10.6.4.3 D channel parameters ("TEI" key)............................................................................................... 10-13
10.6.4.4 Leased line mode parameters ("LLP" key) .................................................................................. 10-13
10.6.4.5 Example of ROUT table "LIST" ................................................................................................... 10-13
10.7 STATISTICS.................................................................................................................................10-14
10.8 HELP .........................................................................................................................................10-15
10.9 DETAILS OF COMMANDS ...............................................................................................................10-16
10.9.1 Table management commands...........................................................................................10-16
10.9.2 "General" management commands.....................................................................................10-17
10.9.3 Dialogue .............................................................................................................................10-17
10.9.4 Special characters ..............................................................................................................10-18
10.10 ACCESS TO THE GIS BOARD CONFIGURATOR ...............................................................................10-19
10.10.1 Native X.25 call in which the USER DATA takes the form "BE0∗" .....................................10-19
10.10.2 Native X.25 call in which the X.121 call number is that of the configurator......................... 10-20
10.11 ROUTING ..................................................................................................................................10-21
10.12 CALL FROM THE MEGAPAC END (B AND D CHANNEL VIRTUAL LINK) ..................................................10-21
10.12.1 Call from a "B" channel virtual link in native X.25 mode .....................................................10-21
10.12.2 Call from a "B" channel virtual link in transparent mode without V.25 Bis...........................10-22
10.12.3 Call from a "B" channel virtual link in transparent mode with V.25 Bis................................ 10-22
10.12.4 Call from the "D" channel virtual link in native X.25 mode.................................................. 10-23
10.13 CALL FROM THE ISDN END (B AND D CHANNELS) .........................................................................10-24
10.13.1 Call from the "B" channel ..................................................................................................10-24
10.13.2 Call accepted from the (B) ISDN end and relayed in native X.25 mode..............................10-25
10.13.3 Call accepted from the (B) ISDN end and relayed in transparent mode without V.25 Bis ...10-25
10.13.4 Call accepted from the(B) ISDN end and relayed in transparent mode with V.25 Bis .........10-25
10.13.5 Call from the "D" channel ..................................................................................................10-25
10.14 TYPICAL NATIVE X.25 MODE CONFIGURATION IN A B CHANNEL ........................................................10-26
10.14.1 Originating Megabox configuration ....................................................................................10-27
10.14.2 Destination Megabox configuration ...................................................................................10-28
11. ISDN BOARD FOR MEGAPAC ESL - MEGAFRAD .....................................................................11-1
11.1 INTRODUCTION..............................................................................................................................11-1
11.2 MEGAPAC CONFIGURATION .............................................................................................................11-2
11.2.1 Operating modes ..................................................................................................................11-2
11.2.2 Correlation between the "descriptors" and physical ports ......................................................11-3
11.3 ISDN NUMBER ..............................................................................................................................11-3
11.4 LINK CONFIGURATION PARAMETERS IN NATIVE X25 MODE...................................................................11-4
11.5 ISDN BOARD CONFIGURATION ........................................................................................................11-6
11.6 STRUCTURE OF THE ISDN BOARD TABLES .......................................................................................11-7
11.6.1 X.25 table syntax (ISDN board).............................................................................................11-7
11.6.2 ISDN table syntax (ISDN board)............................................................................................11-8
11.6.2.1 ISDN address of ISDN adapter..................................................................................................... 11-8
11.6.2.2 NAME = GIO1, GIO2 ..................................................................................................... .............. 11-8
11.6.3 LINK table syntax (ISDN board) ............................................................................................11-9
11.6.4 ROUT table syntax (ISDN board)........................................................................................11-11
11.6.4.1 Incoming call routing ("IN" key) ...................................................................................... ............ 11-12
11.6.4.2 Outgoing call mode ("OUT" key)........................................................................................ ......... 11-12
11.6.4.3 D channel parameters ("TEI" key)............................................................................................... 11-13
11.6.4.4 Leased line mode parameters ("LLP" key) .................................................................................. 11-13
11.6.4.5 Example of ROUT table "LIST" ................................................................................................... 11-13
11.7 STATISTICS.................................................................................................................................11-14
11.8 HELP .........................................................................................................................................11-15
11.9 DETAILS OF COMMANDS ...............................................................................................................11-16
E
11.9.1 Table management commands...........................................................................................11-16
11.9.2 "General" management commands.....................................................................................11-17
11.9.3 Dialogue .............................................................................................................................11-17
11.9.4 Special characters ..............................................................................................................11-18
Page x
11.10 ACCESS TO THE ISDN BOARD CONFIGURATOR .............................................................................11-19

11.10.1 Native X.25 call in which the USER DATA takes the form "BE0∗" .....................................11-19
11.10.2 Native X.25 call in which the X.121 call number is that of the configurator .........................11-20
11.11 ROUTING ..................................................................................................................................11-21
11.12 CALL FROM THE MEGAPAC END (B AND D CHANNEL VIRTUAL LINK) ..................................................11-21
11.12.1 Call from a "B" channel virtual link in native X.25 mode .....................................................11-21
11.12.2 Call from a "B" channel virtual link in transparent mode without V.25 Bis...........................11-22
11.12.3 Call from a "B" channel virtual link in transparent mode with V.25 Bis................................11-22
11.12.4 Call from the "D" channel virtual link in native X.25 mode ..................................................11-23
11.13 CALL FROM THE ISDN END (B AND D CHANNELS) .........................................................................11-24
11.13.1 Call from the "B" channel ..................................................................................................11-24
11.13.2 Call accepted from the "B" ISDN end and relayed in native X.25 mode..............................11-25
11.13.3 Call accepted from the "B" ISDN end and relayed in transparent mode without V.25 Bis ...11-25
11.13.4 Call accepted from the "B" ISDN end and relayed in transparent mode with V.25 Bis ........11-25
11.13.5 Call from the "D" channel ..................................................................................................11-25
11.14 TYPICAL NATIVE X.25 MODE CONFIGURATION IN A B CHANNEL ........................................................11-26
11.14.1 Originating Megapac ESL configuration.............................................................................11-27
11.14.2 Destination Megapac ESL configuration ............................................................................11-28
12. "PRI-64" (30B+D) PRIMARY ACCESS BOARD...........................................................................12-1
12.1 PRELIMINARY ................................................................................................................................12-1
12.2 « T2-ISDN » OPERATION...............................................................................................................12-2
12.2.1 Declaration of PRI-64 board descriptors ................................................................................12-2
12.2.2 Configuration of a primary access (30B+D) ...........................................................................12-2
12.2.3 Configuration of 2 primary accesses (30B+D) .......................................................................12-3
12.2.4 Configuration of 4 primary accesses(30B+D) ........................................................................12-4
12.2.5 Identification of the Numéris (ISDN) caller .............................................................................12-4
12.3 "E1 - G704" OPERATION................................................................................................................12-5
12.3.1 Typical configuration .............................................................................................................12-5
13. TYPE/ HDLC DESCRIPTOR ........................................................................................................13-1
13.1 GENERAL......................................................................................................................................13-1
13.2 LINK CONFIGURATION PARAMETERS .................................................................................................13-1
13.3 LOGICAL RESOURCE PARAMETERS ...................................................................................................13-4
13.4 PRINCIPLE OF AN "HDLC" LINK .......................................................................................................13-6
14. TYPE/ NFRM DESCRIPTORS......................................................................................................14-1
14.1 FRAME FORMAT .............................................................................................................................14-2
14.2 LINK MANAGEMENT ........................................................................................................................14-3
14.3 SELF-DISCIPLINE PRINCIPLE ............................................................................................................14-4
14.4 SWITCHING MODE ..........................................................................................................................14-5
14.4.1 Link configuration parameters ...............................................................................................14-5
14.4.2 Resource configuration parameters.......................................................................................14-8
14.4.3 Examples of Frame Relay « switching » function.................................................................14-10
14.5 IP AND/OR IPX "ACCESS POINT" MODE (RFC 1490) .......................................................................14-11
14.5.1 Link configuration parameters .............................................................................................14-11
14.5.2 Resource configuration parameters.....................................................................................14-14
14.5.3 Examples of the Frame Relay « access point » function......................................................14-16
14.6 X25 - Q922 « ACCESS POINT » MODE ...........................................................................................14-17
14.6.1 Virtual X25 link « VIO » configuration ..................................................................................14-18
14.6.2 X25 virtual descriptor resource configuration .......................................................................14-19
14.6.3 X25 virtual descriptor’s virtual resource configuration ..........................................................14-20
14.6.4 Examples of « X25 access point » function in Frame Relay................................................. 14-21
14.7 FRAME RELAY ON ISDN ...............................................................................................................14-23
14.7.1 Virtual NFRM « VIO » link configuration ..............................................................................14-23
14.7.2 Virtual NFRM descriptor’s resource configuration ................................................................14-25
E
14.7.3 Virtual NFRM descriptor’s virtual resource configuration......................................................14-27
14.7.4 Example of Frame Relay function on a ISDN B channel ......................................................14-28
14.7.5 Example of DLCI concentration on a ISDN B channel .........................................................14-29
14.8 STATISTICS OF A TYPE/ NFRM LINK ............................................................................................14-30
Page xi
15. TYPE/ PPP DESCRIPTOR...........................................................................................................15-1

15.2 LOGICAL RESOURCE CONFIGURATION PARAMETERS...........................................................................15-4
15.3 PAP - PASSWORD AUTHENTICATION PROTOCOL ............................................................................15-5
15.4 EXAMPLE OF "IP ON PPP" CONFIGURATION .....................................................................................15-6
16. TYPE/ TERM DESCRIPTOR........................................................................................................16-1
16.1 TERM IN ASYNCHRONOUS MODE....................................................................................................16-2
16.1.1 Call by resource name or subscriber number ........................................................................16-2
16.1.2 Call by service name.............................................................................................................16-2
16.1.3 Password security check ......................................................................................................16-3
16.1.4 TERM descriptor parameters in Asynchronous mode............................................................16-3
16.1.5 TERM resource parameters in Asynchronous mode .............................................................16-5
16.1.6 Using X.28 commands........................................................................................................16-10
16.1.7 PAD « X28 / X28F » commands and indications .................................................................16-11
16.2 TERM IN BSC MODE (SIO BOARD) ..............................................................................................16-12
16.2.1 TERM descriptor parameters in BSC mode......................................................................... 16-12
16.2.2 TERM resource parameters in BSC mode .......................................................................... 16-14
16.2.3 MAC table, "SYNC" function ...............................................................................................16-17
16.2.3.1 Example of the "SYNC function" ................................................................................................. 16-18
16.3 TYPE/ TERM DESCRIPTOR AND "SLIP" PROTOCOL .......................................................................16-19
16.3.1 Parameters of a TERM descriptor in IP - SLIP mode over an asynchronous link ................16-19
16.3.2 Parameters of a TERM resource in IP - SLIP mode over an asynchronous link ..................16-20
16.3.3 Example of IP -SLIP connection over an asynchronous link ................................................16-22
16.4 TYPE/ TERM DESCRIPTOR IN « PPP » ASYNCHRONOUS MODE ......................................................16-23
16.4.1 Parameters of a TERM descriptor in IP - PPP mode over an asynchronous link.................16-24
16.4.2 Parameters of a TERM resource in IP - PPP mode over an asynchronous link ..................16-25
16.4.3 PAP - Password Authentication Protocol.............................................................................16-27
16.4.4 Example of IP connection in local asynchronous PAD PPP mode .......................................16-28
16.4.5 Example of IP connection in a distant asynchronous PAD PPP...........................................16-29
17. PAD PARAMETERS ....................................................................................................................17-1
18. TYPE/ CONS AND DLCX DESCRIPTOR.....................................................................................18-1

18.1 TYPE/ CONS DESCRIPTOR ...........................................................................................................18-2
18.1.1 CONS link configuration parameters .....................................................................................18-2
18.1.2 Logical resource configuration parameters............................................................................18-2
18.1.3 MAC table parameters ..........................................................................................................18-3
18.1.3.1 MAC address of Ethernet board.................................................................................................... 18-3
18.1.3.1.1 Selection functions ................................................................................................................ 18-3
18.1.4 Example of the "CONS" connection-oriented mode ...............................................................18-4
18.2 TYPE/ DLCX DESCRIPTOR............................................................................................................18-5
18.2.1 DLCX link configuration parameters ......................................................................................18-5
18.2.3 MAC address of Token-Ring board .......................................................................................18-6
18.2.4 Example of the "DLCX" connection-oriented mode................................................................18-7
19. TYPE/ LAN AND TLAN DESCRIPTORS......................................................................................19-1
19.1 GENERAL .....................................................................................................................................19-1
19.3 LOGICAL RESOURCE CONFIGURATION PARAMETERS...........................................................................19-2
19.3.1 Preliminary choice of VC type ...............................................................................................19-2
19.3.2 Additional X.25 network configuration information .................................................................19-5
19.4 ROUTING - AGING OF SELF-LEARNING TABLE.....................................................................................19-5
19.4.1.1 Selection function......................................................................................................................... 19-6
E
19.4.1.2 MAC address of Token-Ring board............................................................................................... 19-7
19.4.1.3 MAC address of Ethernet board.................................................................................................... 19-7
19.5 EXAMPLE OF A TRANSPARENT BRIDGE ..............................................................................................19-8
Page xii
20. TYPE/ IP AND TIP DESCRIPTORS .............................................................................................20-1

20.1 GENERAL......................................................................................................................................20-1
20.2 LINK DESCRIPTOR ..........................................................................................................................20-1
20.2.1 Ethernet frame formats .........................................................................................................20-2
20.3 LINK RESOURCES...........................................................................................................................20-2
20.4 MAC TABLE ..................................................................................................................................20-4
20.4.1 Selection functions................................................................................................................20-4
20.4.2 "Simple" routing (IBEG, NONE option) ..................................................................................20-5
20.4.3 "Extended" routing (IBEG, NOT option).................................................................................20-5
20.4.5 MAC Address of Ethernet board............................................................................................20-6
20.4.6 "MASK" function ...................................................................................................................20-7
20.4.7 "MASK" function with a group of IP resources .......................................................................20-8
20.4.8 Construction principles of an X.25 address from an IP address .............................................20-9
20.4.9 Example: Constructing an X.25 address from an IP address ...............................................20-11
20.4.10 Example: Constructing an X.25 address from an IP address, with subnet..........................20-12
20.4.11 "Reverse ARP" function ....................................................................................................20-13
20.4.12 "BOOTP" function .............................................................................................................20-14
20.4.13 "Static route" function........................................................................................................20-15
20.4.14 « Default Route» and « Local Network » Function .............................................................20-16
20.4.15 Optimizing the "ARP table" (Address Resolution Protocol).................................................20-17
20.4.15.1 "Subnet mask" function ............................................................................................... ..............20-17
20.4.15.2 Filtering the data from the ARP messages (of the LAN) .............................................................20-18
20.4.15.3 Filtering the data from the RIP broadcast (of the LAN)............................................................... 20-18
20.4.15.4 ARP LAN aging, ARP WAN aging ......................................................................................... ....20-18
20.5 "RFC 1356 (877) GATEWAY" FUNCTION ....................................................................................20-19
20.5.1 Link configuration parameters .............................................................................................20-19
20.5.2 Logical resource configuration parameters ..........................................................................20-20
20.5.3 Preliminary choice of VC type .............................................................................................20-22
20.5.4 Further information on configuring the X.25 network............................................................20-22
20.5.5 Example of an RFC1356 (877) gateway..............................................................................20-23
20.6 "IP SWITCHING" FUNCTION...........................................................................................................20-25
20.7 "TELNET" FUNCTION ..................................................................................................................20-26
20.8 PAD TELNET (OR TELNET CLIENT)..................................................................................................20-26
20.8.1 Local Pad Telnet.................................................................................................................20-26
20.8.2 Remote Pad Telnet .............................................................................................................20-27
20.8.3 MAC table parameters ........................................................................................................20-27
20.8.3.1 Telnet negotiation .......................................................................................................................20-28
20.8.3.2 Alternative routing .......................................................................................................................20-29
20.8.4 IP link (Pad Telnet) descriptor parameters...........................................................................20-30
20.8.5 IP (Pad Telnet) logical resource parameters........................................................................20-30
20.9 REVERSE PAD TELNET (OR TELNET SERVICE) .................................................................................20-32
20.9.1 MAC table parameters ........................................................................................................20-32
20.9.1.1 Telnet negotiation, in Reverse Pad Telnet....................................................................................20-33
20.9.2 TCP port N° in Reverse Pad Telnet mode ........................................................................... 20-33
20.9.3 IP link (Reverse Pad Telnet) descriptor parameters.............................................................20-34
20.9.4 IP (Reverse Pad Telnet) logical resource parameters..........................................................20-35
20.10 TELNET OPTION NEGOTIATION - PROTOCOL ..................................................................................20-37
20.10.1 Six scenarios for Telnet option negotiation ........................................................................20-37
20.10.2 Options example ...............................................................................................................20-37
21. TYPE/ IPX AND TIPX DESCRIPTORS.........................................................................................21-1
21.1 GENERAL......................................................................................................................................21-1
21.1.1 Link configuration parameters ...............................................................................................21-1
21.1.2 Logical resource configuration parameters ............................................................................21-2
21.1.3.1 MAC address of Token-Ring board............................................................................................... 21-3
E
21.1.3.2 MAC address of Ethernet board ................................................................................................... 21-3
21.1.3.3 « SAP and RIP » message filtering............................................................................................... 21-4
21.1.3.4 « SAP et RIP » messages filtering example.................................................................................. 21-4
21.2 EXAMPLE OF AN "IPX ON PPP" CONFIGURATION ...............................................................................21-5
Page xiii
22. TYPE/ ROUT DESCRIPTOR........................................................................................................22-1

22.1 "ROUTER" FUNCTION IN A TCP/IP ENVIRONMENT .............................................................................22-2
22.1.1 Virtual descriptor configuration parameters ...........................................................................22-2
22.1.3 Example of "RIP router in TCP/IP" mode .............................................................................. 22-5
22.1.4 Static route in MAC table ......................................................................................................22-6
22.1.5 MAC table datagram selection ..............................................................................................22-7
22.2 "BOOTP / DHCP RELAY FUNCTION ...............................................................................................22-10
22.3 "TELNET SERVER" FUNCTION FROM THE IP ROUTER ........................................................................22-11
22.4 "ASYNCHRONOUS PPP ACCESS" FUNCTION WITH IP ADDRESS NEGOTIATION .....................................22-12
22.4.1 Logical resource configuration parameters in PPP mode.....................................................22-13
22.5 "ROUTER" FUNCTION IN A NETWARE ENVIRONMENT ........................................................................22-14
22.5.1 Virtual descriptor configuration parameters .........................................................................22-14
22.5.2 Logical resource configuration parameters..........................................................................22-15
22.5.3 Example of an "RIP router in a Netware" environment.........................................................22-17
22.5.4 "Request RIP and Request SAP" message inhibition ..........................................................22-18
22.5.5 "SAP" message inhibition....................................................................................................22-18
22.5.6 "RIP and/or SAP" static route in MAC table......................................................................... 22-19
22.5.6.1 Static route example................................................................................................................... 22-20
22.5.7 "Watchdog IPX" message spoofing .....................................................................................22-21
22.5.8 Inhibition of Netbios broadcast frames ................................................................................22-21
22.5.9 MAC table protocol selection...............................................................................................22-22
23. TYPE/ SNMP DESCRIPTOR........................................................................................................23-1
23.1 GENERAL .....................................................................................................................................23-1
23.2 SNMP MANAGEMENT....................................................................................................................23-1
23.3 VIRTUAL DESCRIPTOR CONFIGURATION PARAMETERS ........................................................................23-2
23.4 RESOURCE CONFIGURATION PARAMETERS .......................................................................................23-2
23.5 MAC TABLE..................................................................................................................................23-3
23.5.1 SNMP resource associated to the first IP/TIP resource .........................................................23-3
23.6 "SNMP AGENT" FUNCTION, WITH IP RESOURCE...............................................................................23-4
23.7 "SNMP AGENT + TRAP MANAGEMENT" FUNCTION, WITH IP RESOURCE ...............................................23-5
23.7.1 TCP/IP RIP Router with SNMP agent ...................................................................................23-6
23.7.1.1 TRAP SNMP management in "RIP" router .................................................................................... 23-7
23.8 "AGENT SNMP + TRAP SNMP" FUNCTION WITH WAN RESOURCE ....................................................23-8
24. TYPE/ MULT DESCRIPTOR ........................................................................................................24-1

24.1 MULTIPOINT LINK APPLICATION ........................................................................................................24-1
24.3 LOGICAL RESOURCE PARAMETERS...................................................................................................24-2
24.4 "MULT" OPERATING MODES ...........................................................................................................24-4
25. TYPE/ V25B DESCRIPTOR .........................................................................................................25-1
25.1 GENERAL .....................................................................................................................................25-1
25.2 EXPLOITATION IN V.25BIS PROTOCOL ..............................................................................................25-1
25.2.1 Typical configuration in backup mode "V.25bis" ....................................................................25-2
25.3 MANAGING SEVERAL V25B NUMBERS FOR A SINGLE DIRECTORY NUMBER ............................................25-5
25.4 MANAGING SEVERAL DESTINATIONS FOR THE SAME LINK.....................................................................25-6
25.5 V25 BIS HUNT GROUP....................................................................................................................25-7
25.5.1 Typical group ........................................................................................................................25-8
25.6 "MONITOR" MODE FOR A BACKUP LINK WITH V.25 BIS PROTOCOL ........................................................25-9
25.7 "MONITOR" MODE ON A BACKUP LINK WITHOUT V.25 BIS PROTOCOL..................................................25-10
25.7.1 Typical monitoring configuration (without V.25 bis protocol) ................................................25-11
25.8 REVIEW OF CP AND RP RULES .....................................................................................................25-12
25.9 ISDN CALLING LINE IDENTIFICATION FUNCTION ...............................................................................25-13
25.9.1 Description .........................................................................................................................25-13
E
25.9.2 ISDN number......................................................................................................................25-13
25.9.3 Entering the "calling party identity" ......................................................................................25-15
25.10 V.25 BIS VIRTUAL DESCRIPTOR PARAMETERS................................................................................25-16
25.11 V.25 BIS RESOURCE CONFIGURATION PARAMETERS ......................................................................25-16
Page xiv
25.12 TYPICAL CONFIGURATION IN V25 BIS SYNCHRONOUS AND ASYNCHRONOUS MODE ............................25-17
25.13 OUTPUT MAC TABLE .................................................................................................................25-18
25.13.1 "DATA" function ................................................................................................................25-18
25.13.2 "TIME" function .................................................................................................................25-19
25.13.3 "CAD" function ..................................................................................................................25-20
25.13.4 "DAD" function ..................................................................................................................25-21
25.13.5 "CUD" function ..................................................................................................................25-22
25.14 REVIEW OF ISDN NETWORK REJECT "CAUSES" ............................................................................25-23
26. TYPE/ SDLC - QLLC DESCRIPTOR............................................................................................26-1
26.1 GENERAL......................................................................................................................................26-1
26.1.1 SDLC/QLLC relation .............................................................................................................26-1
26.1.2 Link emulation types .............................................................................................................26-3
26.1.3 Additional characteristics.......................................................................................................26-3
26.1.4 Configuring a Megapac link ...................................................................................................26-3
26.2 SDLC - QLLC LINK CONFIGURATION PARAMETERS ...........................................................................26-5
26.3 LOGICAL RESOURCE CONFIGURATION PARAMETERS .........................................................................26-10
26.3.1 X.25 table in SDLC - QLLC mode .......................................................................................26-12
26.3.2 MAC table in SDLC - QLLC mode.......................................................................................26-12
27. TYPE/ CLUS DESCRIPTOR ........................................................................................................27-1
27.1 FUNCTIONALITY OF THE CLUS LINK DESCRIPTOR ..............................................................................27-3
27.1.1 IND$FILE file transfer............................................................................................................27-4
27.1.2 File transfer between PCs.....................................................................................................27-4
27.1.3 Generation of a menu when routing to a terminal ..................................................................27-5
27.1.4 Graphics characters, from the extended ASCII code .............................................................27-5
27.3 LOGICAL RESOURCE CONFIGURATION PARAMETERS ...........................................................................27-7
27.4 MAC TABLE PARAMETERS IN CLUS MODE .....................................................................................27-10
27.5 "CLUS" KEYBOARD EMULATION MAPPING .....................................................................................27-11
27.5.1 "ASYN" keyboard mapping (Terminal Type = ASYN) ..........................................................27-11
27.5.2 "ANSI" keyboard mapping (Terminal Type = ANSI) .............................................................27-12
27.5.3 "VT22" keyboard mapping (Terminal Type = VT22).............................................................27-14
27.6 MODIFICATION DE LA TABLE STANDARD DE CONVERSION ASCII - EBCDIC ........................................27-14
28. TYPE/ MAP DESCRIPTOR ..........................................................................................................28-1
28.1 MAP CONCENTRATION FUNCTION ...................................................................................................28-1
28.1.1 Role of the MAP concentration function.................................................................................28-2
28.1.2 MAP concentration function operating principle .....................................................................28-4
28.1.3 Using the MAP function.........................................................................................................28-5
28.2 "MAP" DESCRIPTOR CONFIGURATION PARAMETERS ..........................................................................28-7
28.2.1 Parameters for MAP virtual resource N°0..............................................................................28-8
28.2.2 Parameters for MAP virtual resources N°>0..........................................................................28-9
29. TYPE/ DLC AND EDLC DESCRIPTOR........................................................................................29-1
29.1 DLC GATEWAY FUNCTION ..............................................................................................................29-1
29.1.1 DLC without MAP concentration............................................................................................29-2
29.1.2 DLC gateway and MAP concentration...................................................................................29-3
29.2 XID INTERCHANGES.......................................................................................................................29-4
29.2.1 Gateway with one interchange (transparent) .........................................................................29-4
29.2.2 Gateway with two interchanges.............................................................................................29-5
29.3 « DLC / EDLC » DESCRIPTOR CONFIGURATION PARAMETERS ...........................................................29-6
29.4 « DLC / EDLC » RESOURCE CONFIGURATION PARAMETERS ..............................................................29-7
29.5 MAC TABLE ..................................................................................................................................29-9
29.5.2 MAC Address of Ethernet board............................................................................................29-9
E
30. TYPE/ SCOP DESCRIPTOR ........................................................................................................30-1
30.1 INTRODUCTION ..............................................................................................................................30-1
30.2 CONFIGURATION PARAMETERS OF THE « SCOP » DESCRIPTOR .........................................................30-2
Page xv
30.3 CONFIGURATION PARAMETERS OF THE« SCOP » RESOURCE ............................................................30-2

30.4 EXAMPLE OF CONFIGURATION .........................................................................................................30-2
30.5 « DATA-SCOPE » COMMANDS .....................................................................................................30-3
30.5.1 Port monitoring .....................................................................................................................30-3
30.5.2 Continuous display................................................................................................................30-3
30.5.3 Dump read mode ..................................................................................................................30-3
30.5.4 Buffer reset...........................................................................................................................30-3
30.6 OBSERVED RECORDS.....................................................................................................................30-4
31. STATISTICS ................................................................................................................................31-1
31.1 "BASE" DESCRIPTOR STATISTICAL REPORT .....................................................................................31-2
31.2 ALPHABETICAL LIST OF VARIABLES IN A "STATISTICS" REPORT ............................................................31-3
32. SYSTEM MESSAGES..................................................................................................................32-1
32.1 GENERAL FORMAT OF A MEGAPAC MESSAGE ....................................................................................32-1
32.2 CONNECTION AND DISCONNECTION MESSAGES .................................................................................32-1
32.3 ALPHABETICAL LIST OF "MEGAPAC" MESSAGES .................................................................................32-2
33. GLOSSARY .................................................................................................................................33-1
33.1 V24/V28 INTERFACE SIGNAL ..........................................................................................................33-6
The contents of this manual must not be reproduced or used without the permission of E Page xvi
Table of figures
FIGURE 1-1 LOOKING FOR A "RESOURCE", RP - CP ALGORITHM ................................................................. 1-9
FIGURE 1-2 LOOP CHECKING MECHANISM, LOOP BAR PRIORITY ALGORITHM ..........................................1-10
FIGURE 1-3 TYPICAL NETWORK...............................................................................................................1-11
FIGURE 1-4 SETTING UP A NUMBER OF ROUTING ALTERNATIVES..................................................................1-12
FIGURE 1-5 USE OF CALL PRIORITIES AND LOOP BARRING...........................................................................1-13
FIGURE 1-6 EVEN DISTRIBUTION ON LINKS OF EQUAL PRIORITY ...................................................................1-14
FIGURE 1-7 OVERFLOW FROM A LINK TO ANOTHER ....................................................................................1-15
FIGURE 1-8 TRANSPORT MONITORING .....................................................................................................1-16
FIGURE 1-9 MONITORING WITHOUT TRANSPORT .......................................................................................1-16
FIGURE 1-10 BLOCK DIAGRAM OF CALL ROUTING.......................................................................................1-19
FIGURE 2-1 NAVIGATION COMMANDS ........................................................................................................ 2-7
FIGURE 4-1 RELATIONSHIP BETWEEN DESCRIPTORS AND PHYSICAL PORTS ................................................... 4-3
FIGURE 5-1 LIMITATION EXAMPLE OF THE VCP COMMAND PORT RIGHTS ....................................................... 5-5
FIGURE 6-1 STRUCTURE OF THE X.25 TABLE ............................................................................................ 6-1
FIGURE 6-2 SPECIAL CHARACTERS IN THE ADDRESS FIELD ...................................................................... 6-2
FIGURE 6-3 TRANSLATION OF THE ADDRESS FIELD ................................................................................. 6-3
FIGURE 6-4 TRANSLATION WITH "T" AND THE ADDRESS GROUP FIELD .................................................... 6-4
FIGURE 6-5 ROUTING OVER A BACK-UP LINK .............................................................................................. 6-4
FIGURE 6-6 USE OF THE COPY (″) AND SKIP (#) CHARACTERS ..................................................................... 6-5
FIGURE 6-7 INSERTING THE SOURCE ADDRESS .......................................................................................... 6-6
FIGURE 6-8 USE OF THE "DITTO" WILDCARD IN LOGICAL RESOURCES ........................................................... 6-7
FIGURE 6-9 MANIPULATING THE CALL USER DATA FIELD .............................................................................. 6-8
FIGURE 6-10 ROUTING ALGORITHM WITH THE X.25 TABLE .......................................................................... 6-9
FIGURE 7-1 INPUT MAC ROUTING ALGORITHM........................................................................................... 7-6
FIGURE 7-2 OUTPUT MAC ROUTING ALGORITHM ......................................................................................7-14
FIGURE 9-1 EXAMPLE OF A CLASS 3 TRANSPORT CONFIGURATION...............................................................9-18
FIGURE 9-2 TRANSPORT ON MAIN AND BACKUP LINK WITH MONITORING .......................................................9-22
FIGURE 9-3 STRUCTURE OF THE "FACILITIES" FIELD ..................................................................................9-48
FIGURE 10-1 GIS BOARD 2B+D CHANNEL ROUTING .................................................................................10-2
FIGURE 10-2 TYPICAL GIS BOARD CONFIGURATION IN NATIVE X.25 MODE .................................................10-26
FIGURE 11-1 ISDN BOARD 2B+D CHANNEL ROUTING ...............................................................................11-2
FIGURE 11-2 TYPICAL ISDN BOARD CONFIGURATION IN NATIVE X.25 MODE...............................................11-26
FIGURE 13-1 EXAMPLE OF AN HDLC LINK ................................................................................................13-6
FIGURE 14-1 FRAME RELAY FRAME FORMAT .............................................................................................14-2
FIGURE 14-2 LMI INTERCHANGES, UNBALANCED ON THE FRAD SIDE AND BALANCED ON THE SWITCH SIDE .14-3
FIGURE 14-3 LMI INTERCHANGES, BALANCED FROM END TO END ...............................................................14-3
FIGURE 14-4 FRAME RELAY « SWITCHING » FUNCTION ...........................................................................14-10
FIGURE 14-5 FRAME RELAY « ACCESS POINT » FUNCTION .......................................................................14-16
FIGURE 14-6 X25 ENCAPSULATION IN FRAME RELAY (Q922 DL CORE) ....................................................14-17
FIGURE 14-7 X25 ENCAPSULATION IN FRAME RELAY (TRANSPAC LIKE)......................................................14-17
FIGURE 14-8 X25 « ACCESS POINT » FUNCTION (Q922 DL CORE) IN FRAME RELAY..................................14-21
FIGURE 14-9 X25 « ACCESS POINT » FUNCTION (TRANSPAC LIKE) IN FRAME RELAY ...................................14-21
FIGURE 14-10 PROTOCOL MULTIPLEXING ON THE SAME DLCI - FRAME RELAY ...........................................14-22
FIGURE 14-11 ISDN FRAME RELAY FUNCTION .......................................................................................14-28
FIGURE 14-12 DLCI FRAME RELAY CONCENTRATION ON A ISDN B CHANNEL............................................14-29
FIGURE 15-1 EXAMPLE OF IP GATEWAY ON PPP LINK ...............................................................................15-6
FIGURE 16-1 RELATIONSHIP BETWEEN RESOURCES OF TERM DESCRIPTOR AND PHYSICAL PORT ..................16-1
FIGURE 16-2 EXAMPLE OF A MEGAPAC IN IP - SLIP MODE OVER AN ASYNCHRONOUS LINK ..........................16-22
FIGURE 16-3 EXAMPLE OF A MEGAPAC IN LOCAL ASYNCHRONOUS PAD PPP MODE ...................................16-28
FIGURE 16-4 MEGAPAC IN A DISTANT ASYNCHRONOUS PAD PPP ............................................................16-29
FIGURE 17-1 THE « X » STANDARDS ......................................................................................................17-1
FIGURE 18-1 USE OF MEGAPAC WITH "CONS" CONNECTION-ORIENTED MODE ............................................18-4
FIGURE 18-1 USE OF MEGAPAC WITH "DLCX" CONNECTION-ORIENTED MODE .............................................18-7
E
FIGURE 19-1 MEGAPAC TRANSPARENT BRIDGE.........................................................................................19-8
FIGURE 20-1 ETHERNET AND IEEE 802.3 FRAME FORMATS ......................................................................20-2
FIGURE 20-2 MEGAPAC IN RFC1356 GATEWAY MODE ............................................................................20-23
FIGURE 20-3 "TELNET SERVER" CONFIGURATION, ON "BE00" VIRTUAL CONFIGURATION PORT ...................20-34
Page xvii
FIGURE 21-1 EXAMPLE OF AN IPX GATEWAY ON A PPP LINK .....................................................................21-5

FIGURE 22-1 EXAMPLE OF A MEGAPAC AS AN RIP ROUTER ON TCP/IP.......................................................22-5
FIGURE 22-2 EXAMPLE OF A STATIC ROUTE (RIP ON TCP/IP)....................................................................22-6
FIGURE 22-3 IP ROUTER IN TELNET SERVER CONFIGURATION ON THE BE00 PORT .....................................22-11
FIGURE 22-4 ASYNCHRONOUS PPP ACCESS WITH IP ADDRESS NEGOTIATION ..........................................22-12
FIGURE 22-5 EXAMPLE OF A MEGAPAC AS RIP ROUTER IN AN IPX NOVELL ENVIRONMENT ..........................22-17
FIGURE 22-6 EXAMPLE OF A STATIC ROUTE (RIP-IPX) ............................................................................22-20
FIGURE 23-1 MEGAPAC IN SNMP AGENT MODE .......................................................................................23-4
FIGURE 23-2 MEGAPAC TCP/IP RIP ROUTER AND SNMP MANAGEMENT ...................................................23-6
FIGURE 23-3 SNMP AGENT ON A NODE WITHOUT A LAN ATTACHMENT.......................................................23-8
FIGURE 25-1 TYPICAL CONFIGURATION FOR A SYNCHRONOUS LINK IN V25 BIS MODE .................................25-17
FIGURE 25-2 TYPICAL CONFIGURATION FOR A ASYNCHRONOUS LINK IN V25 BIS MODE................................25-17
FIGURE 26-1 "QLLC" DESCRIPTOR FUNCTIONS ........................................................................................26-2
FIGURE 26-2 MEGAPAC USED AS A CLUSTER CONTROLLER ........................................................................26-4
FIGURE 27-1 DIRECT CLUSTER CONNECTION TO SNA HOST ......................................................................27-1
FIGURE 27-2 CLUSTER CONNECTION VIA AN X.25 NETWORK ......................................................................27-2
FIGURE 28-1 GATEWAY MEGAPAC WITH OR WITHOUT MAP FUNCTION .......................................................28-2
FIGURE 28-2 GATEWAY MEGAPAC AND THE MAP FUNCTION .....................................................................28-3
FIGURE 28-3 BLOCK DIAGRAM OF THE MAP CONCENTRATION FUNCTION ....................................................28-4
FIGURE 28-4 EXAMPLE OF CALCULATING THE MAP FUNCTION OFFSET ........................................................28-6
FIGURE 29-1 DLC GATEWAY FUNCTION ..................................................................................................29-1
FIGURE 29-2 SETTING UP TWO VIRTUAL CIRCUITS IN THE MEGAPAC ...........................................................29-2
FIGURE 29-3 VIRTUAL CIRCUIT SETUP IN THE MEGAPAC ............................................................................29-3
FIGURE 29-4 GATEWAY WITH ONE INTERCHANGE .....................................................................................29-4
FIGURE 29-5 TWO INTERCHANGE GATEWAY ............................................................................................29-5
FIGURE 30-1 DATA-SCOPE FUNCTION CONFIGURATION .........................................................................30-2
The contents of this manual must not be reproduced or used without the permission of E Page xviii
FOREWORD
This manual describes in detail all aspects to do with installing and commissioning the Megapac
systems.
No attempt is made to describe the hardware configuration.
For this information, refer as required to the "Hardware configuration manual" supplied with the Megapac
used.
In case of problems, contact our hot line:
E
On a single phone number: +33 1 55 75 77 77
On a single fax number: +33 1 55 75 77 70
At a single address:
- INSTALLATION AND MAINTENANCE CENTRE
After Sales Service - Business Systems
11, rue Watt
75 626 Paris Cedex 13 - France
Technicians are available from Monday to Friday, 8 am to 7 pm, to answer all your technical problems
which cannot be resolved by the information contained in this manual, by your training or by your
E
experience of the Megapac - Megabox range.
notice, and the information contained in it shall in no way be binding on E

is continually striving to improve its products. This manual may be modified without prior
.
The contents of this manual must not be reproduced or used without the permission of E Page xix
The contents of this manual must not be reproduced or used without the permission of E Page xx
1. General
The Megapac is a high speed packet switch capable of handling large volumes of data. It can operate in
DMA I/O mode for high bit rates or "serial interrupt" I/O mode.
1.1 "Descriptors" and "resources"
In the Megapac, each link (physical or virtual) is associated with a link DESCRIPTOR.
A link comprises one or more logical channels.
Each logical channel is identified by a RESOURCE.
A link DESCRIPTOR therefore comprises one or more RESOURCES.
So, to set up a connection in Megapac,

you must establish a link between 2 RESOURCES.
Each Megapac link has an associated link descriptor:

• the "link descriptor" level corresponds to the OSI data link layer.
This descriptor defines:
• the protocol used on the corresponding link (according to whether it is X.25, HDLC, TERM,
ILAN, XLAN, QLLC, SDLC, MULT, CLUS, LAN , TLAN , CONS, IP , TIP, IPX , TIPX, ...),
• the number of logical resources it supports,
• other characteristics relating to the link.
• the "logical resource" level corresponds to the OSI network layer. The logical resource sets up a
virtual circuit enabling a call to be routed. Each logical resource has its own configuration defining:
• the name of the channel,
• the type of virtual circuit,
• other parameters.
General
E Page 1-1
E
1.2 Tables
Manual N5682000901 - Edition 1 - March 1999
To supplement the DESCRIPTORS and RESOURCES relating to a link (physical or virtual), the
Megapac also has a set of tables:
X.25 table This table provides routing and address translation, in particular associating an X.121
address (X.25 protocol) with a resource, and vice versa.
MAC table This table is an extension of the X.25 table’s routing function. It uses a
macrocommand language and can be used for incoming and/or outgoing calls.
ILAN table This table is for routing calls using the class 4 ISO Transport layer. It associates an
MAC 802.3 address and a TSAP (Transport Service Access Point) address with a
resource.
PROF table This table defines the standard CCITT Recommendation X.3 PAD
(Packet Assembly/Disassembly) profiles. These can be modified.
NAME table This table is used to assign a service NAME known to the user to a resource to
support routing by NAME.
HELP table This table supplements the NAME table. If routing by NAME fails, a help screen can
be selected.
PASS table This table provides password controls for incoming and/or outgoing calls.
MENU table This table can be used to display an information menu, welcoming message, etc.
BILL table This table keeps a record of connections with details for each connection. It can be
used for billing purposes.
ELOG table This table logs connection messages and routing faults.
MEM table This table defines the size of the other tables.
Note: The table names above must not be used as link descriptor and/or resource name.
1.3 "Resource" names
By default, the name given to the "resources" of a link (resource NAME/ parameter) is made up of the
link "descriptor’s" name (descriptor NAME/ parameter).
"Resource" and "descriptor" names are four-character strings.
"Resource" names are, by default, made up of:
• the first character of the "descriptor" name,
• the last character of the "descriptor" name,
• two "zeros",
• by default, all resources of a particular link have the same four-character name, to which is added a
suffix specifying the number of the "resource".
For "n resources", the number will range from 0 to n-1.
Example of a link with 16 "resources":

For a link "descriptor" for which NAME/ is PS04,
E
the associated "resources" have NAME/ P400(0) to P400(15).
General Page 1-2
E
1.4 Routing Principles
To set up a connection in the Megapac switch, two "resources" need to be temporarily associated for the
duration of a call.
In the Megapac switch, all calls and data transfers use a four-character "resource" name.
The resource name is linked to a network address when the switch needs to pair an input link with an
output link to set up a route through it for a call.
In the case of an X.25 network, with a call request packet including a called DTE address, the subscriber
number is used to select a destination "resource".
The « Destination Resource Code » (DRC) is the term given to the 4 character channel name of the
resource channel to which you wish to connect.
The Megapac has two tables for choosing the destination "resource", and therefore the output link to be
used:
1. the X.25 table, which provides simple routing, based on the number (or part of the number) of the
called DTE and a resource name, to one or more output links.
2. the MAC table, which provides more sophisticated routing based on a set of macrocommands which
offer a high degree of control and let you modify incoming and outgoing frames.
1.4.1 Different routings
The Megapac can route an X.25 call request packet in various ways:
1. transparent routing via a switched virtual circuit (SVC): a call is routed automatically when a match is
found in the X.25 table (or the MAC table) based on the X.121 address of the call request packet;
2. transport level routing: calls are checked by the internal implementation of the OSI transport layer, so
that another route can be allocated if a link fails. In this case, the loss of data is transparent;
3. routing on permanent virtual circuit (PVC): the call request takes a predefined route through the
network based on the « DRC MASK/ » (Destination Resource Code) of the incoming "resource";
4. routing by presentation service: the switch prompts the user to enter a "resource" name, a network
address or a service name for routing purposes.
General
E Page 1-3
E
1.5 "Resource" identification
It is a good idea to be able to choose the name of a resource (NAME/ parameter) to facilitate connection
to various network resources.
For this, the NAME/ parameter can contain any letter in upper or lowercase and "wildcard characters".
No distinction is drawn between uppercase and lowercase.
• The wild card character "∗" represents any character in any position.
• The wild card character "″" indicates a match in a comparison, this using is special.
The search for the destination "resource" name is conducted throughout the "resources" of the link
"descriptors".
Consider the following, where a Physical descriptor has 8 resources connections to 3 Hosts known as
VAX1, VAX2 and VAX3.
1.5.1 Resource NAME without wild cards
No wild cards are used in this example, and as you can see, 3 resources connections are available to
Hosts VAX1 and VAX2, while VAX3 only has 2.
Resource number Resource authorized

NAME/ parameter Destination Resource NAME
(0) VAX1 VAX1
(1) VAX1 VAX1
(2) VAX1 VAX1
(3) VAX2 VAX2
(4) VAX2 VAX2
(5) VAX2 VAX2
(6) VAX3 VAX3
(7) VAX3 VAX3
General
E Page 1-4
1.5.2 Resource NAME with « ∗ » wild cards
An asterisk « ∗ » wild card is used to denote any character (i.e. catch all), and can be specified at any or
all character positions.
In this example an ∗ has been entered at the beginning and end of the 4 character NAME/ parameter of
all eight resources.
The user who is originating a call to any of the eight resources allocated has only to specify a NAME
containing AX as the second and third characters.

(0) ∗AX∗ VAX1/2/3, aAXz, 0AX9, etc ...
(1) ∗AX∗ VAX1/2/3, aAXz, 0AX9, etc ...
(2) ∗AX∗ VAX1/2/3, aAXz, 0AX9, etc ...
(3) ∗AX∗ VAX1/2/3, aAXz, 0AX9, etc ...
(4) ∗AX∗ VAX1/2/3, aAXz, 0AX9, etc ...
(5) ∗AX∗ VAX1/2/3, aAXz, 0AX9, etc ...
(6) ∗AX∗ VAX1/2/3, aAXz, 0AX9, etc ...
(7) ∗AX∗ VAX1/2/3, aAXz, 0AX9, etc ...
General
E Page 1-5
E
1.5.3 Hunt group
1.5.3.1 « " " " " » resource NAME
Other wild card options include « " " " " », which is used to copy the NAME(s) of the channels above it
and establish connections as though in a hunt group.

(0) VAX1 VAX1

(1) VAX2 VAX2
(2) """" VAX1 or VAX2
(3) """" VAX1 or VAX2
(4) """" VAX1 or VAX2
(5) VAX3 VAX3

(6) """" VAX3
(7) """" VAX3
The resources (0) to (4) form a hunt group. The resources (2) to (4) are accessible through the routing
names VAX1 and VAX2.
The resources (5) to (7) form a hunt group. The resources (6) and (7) are accessible through the routing
name VAX3.
The parameters of each resources can be defined, especially the « DRC MASK/ » parameter for the
specific routings requirements. Thus, for each « DRC MASK/ » of the different hunt groups, various call
numbers can be assigned to distinguish them.
General
E Page 1-6
1.5.3.2 « " ∗ ∗ ∗ » resource NAME
A fourth wild card option « " ∗ ∗ ∗ » is used to enable the channel to match the configuration
characteristics of whichever channel name is used.

(0) VAX1 VAX1

(1) VAX2 VAX2
(2) "∗∗∗ VAX1 or VAX2
(3) "∗∗∗ VAX1 or VAX2
(4) "∗∗∗ VAX1 or VAX2
(5) "∗∗∗ VAX1 or VAX2
(6) "∗∗∗ VAX1 or VAX2
(7) "∗∗∗ VAX1 or VAX2
The resources (0) to (7) form a hunt group. The resources (2) to (7) are accessible through the routing
names VAX1 and VAX2.
When a call is connected to the logical resources (from 2 to 7), the characteristics of the channel will
echo that of channel (0) if accessed using the routing name of VAX1. It will echo the characteristics of
the channel (1) if accessed using the routing name of VAX2 .
General
E Page 1-7
1.6 Principles of routing by priority: "CP ≥ RP"
To ensure that your data is routed correctly over secondary routes, using the same destination "resource"
name (NAME/), the Megapac switch lets you define a priority for each link "resource" on two levels:
• the CALL PRIORITY/ parameter (known by the acronym CP) assigns a priority to calls according to
the "resource" via which it enters the Megapac switch, and
• the RESOURCE PRIORITY/ parameter (known by the acronym RP) represents the priority of the
"resource" via which a call can be routed out from the switch.
These two parameters are specified in the "resource" definition, and can be set from 0 to 15 in ascending
order of priority from least important to most important.
All incoming calls to a Megapac switch are assigned the CP setting for the "resource" concerned. While
the call is being routed, the Megapac first looks for an outgoing "resource" on any link for which the
NAME/ parameter matches the destination "resource" name found for the call.
Having found one or more "resources", it sets up a connection on the "resource" for which the RP
parameter has a setting not exceeding the CP parameter of the incoming "resource". If no match if
found, the Megapac looks among the available "resources" for the one with the next lower priority. If two
"resources" have the same name and the same priority level, the first is taken.
A call received over a "resource" with a given CP setting cannot be connected to an outgoing "resource"
with a higher RP setting. This means that a "resource" for which CP is zero can be connected only with
a "resource" for which RP is also zero. A resource defined with a call priority CP of 15 offers the greatest
freedom of choice because it can be connected to virtually any resource of the same name.
When look for an outgoing "resource" of a specific priority, the Megapac scans the resources of all the
links to find a match. If it does not find a match, the Megapac again scans the resources of all the links,
with RP decremented by 1, and so on until if finds a match.
If the Megapac does not find an alternative to satisfy the received call request, the Megapac clears the
call. A "resource" must be free for the call to be able to use it. If the "resource" is busy, the search
continues.
Source Resource Destination Resource Selection

RP = 7 to 15 not possible
RP = 6 not possible
RP = 5 not possible
CP = 4 RP = 4 having priority
RP = 3 possible
RP = 2 possible
RP = 1 possible
RP = 0 possible
General
E Page 1-8
The diagram below illustrates an attempt to connect the "resource" E100 to "resources" VAX1 and VAX2,
in that order of priority. Some "resources" cannot accept a call and the call is finally connected to VAX1.
(5) NAME/ VAX2

RESOURCE PRIORITY/ 15
EIA/
(4) NAME/ VAX2
EIA/ BUSY
4e (3) NAME/ VAX1

3e RESOURCE PRIORITY/ 0
EIA/
(2) NAME/ VAX1
EIA/ BUSY
2e
(1) NAME/ VAX1
1er RESOURCE PRIORITY/ 14
EIA/ BUSY
(0) NAME/ E100 (0) NAME/ P100
CALL PRIORITY/ 14 RESOURCE PRIORITY/ 4
DRC MASK/ VAX* EIA/ BUSY
EPCI PS02
TYPE/ X25
Figure 1-1 Looking for a "resource", RP - CP algorithm
Although available, "resource (5)" is not used because the RESOURCE PRIORITY/ setting is higher than
the CALL PRIORITY/ setting for the "resource" requesting a connection. In a well ordered configuration,
the parameter settings for the various "resources" must decrease sequentially.
General
E Page 1-9
1.7 "Loop Bar Priority" mechanism
Since the Megapac has the ability to look for an alternative route, there is a possibility of routing over an
outgoing "resource" that returns the call to a switch already crossed by this call request packet, which can
result in a permanent loop situation.
When scanning all the logical resources, depending on their resource priorities (RESOURCE
PRIORITY/), if the routing mechanism finds a match on the same link as the incoming "resource", and
the LOOP BAR PRIORITY/ parameter of the link descriptor has a setting greater than zero, the resource
priority of the outgoing channel is compared with the priority indicated in the LOOP BAR PRIORITY/
parameter of the link descriptor. If they match, the Megapac discards the link and resumes its search.
The call is cleared if no outgoing channel is available on the other links.
If the EIA state is OS or busy,

look for a lower resource
priority, then check EIA status
(15) NAME/ P100 again. (15) NAME/ P100
2e EIA/ BUSY
EIA/
(0) NAME/ P100 (0) NAME/ P100

RESOURCE PRIORITY/ 3 1er EIA/ BUSY
EIA/ Match on NAME,
match on priority
PS01: TYPE/ X25 check EIA state. PS02: TYPE/ X25
LOOP BAR/ 3 LOOP BAR/ 0
If LOOP BAR/ value matches

PRIORITY RESOURCE/ value,
call not connected.
Figure 1-2 Loop checking mechanism, LOOP BAR PRIORITY algorithm
In the above example:

1. a call is received on resource (0) of descriptor PS01, for which the resource CALL PRIORITY/
parameter setting is 4;
2. the search mechanism establishes that the name of the destination resource is P100. The first match
found gives resource (0) on link PS02 (same RESOURCE PRIORITY/ settings), but this resource is
busy. The subsequent matches also show busy state;
3. the next match is found on resource (15) of descriptor PS01, which represents the same link as for
the incoming call. The RESOURCE PRIORITY/ setting of this resource is 3 which matches the
LOOP BAR/ setting of link PS01, so preventing a connection;
4. no other resource is available so the call is cleared.
☛ Note that call request packet loops in most public networks are considered as a routing
error, normally leading to the call being cleared.
General
E Page 1-10
E
1.8 Example of routing priority
The diagram below describes a complex network in which, if the Network User Address (NUA) numbers
of a system were all known to each Megapac switch, expansion of the services would entail modifying
the configuration of each switch in the network.
The solution adopted for the Megapac is a decentralized mechanism in which each Megapac switch has
independent decision-making capability, without regard to its adjacent nodes. Because of this the
"destination resource" used for routing requirements requires only the name of the switch to be specified
with a partially specified NUA (in other words, using the "wildcard").
The example assumes a terminal connected to switch 6 requiring the services of switch 1, and that the
X.121 address of the call request packet has the number 23429320016. The terminal user logs on to
resource " N01H".
• The NAME/ parameter of all the "resources" between switches is defined by N01∗. All the
intermediate switches have the same X.25 record (in other words NAME/ N01H, ADDRESS/ 23429∗,
correlating all X.121 addresses beginning 23429 with routing of the call to a resource N01H), except
for node 01, which requires complete correlation and a change to the routing name in order to set up
the precise resource for placing the call.
Call request packet sent

23429320016
X.25 table
NAME/ HST* NAME/ HST1
ADDRESS/ 23429320016
Node 01
NAME/ N01*
Node 03
X.25 table
NAME/ N01* NAME/ N01H NAME/ N01*
ADDRESS/ 23429*
Node 04 Node 05
NAME/ NAME/
N01* N01* Node 07
Call request packet generated:

X.25 table 23429320016
NAME/ NO1H NAME/ N01*
access to
ADDRESS/ 23429320016 NO1H
Node 06
Figure 1-3 Typical network
• The call and resource priorities of node 07 must be used to define the main route to node 04 (the
shortest route), with an alternative to node 05. Obviously the connections to nodes other than 01
cannot be completed because there is only a single resource name for the inter-node links.
General
E Page 1-11
However, if the wildcard is used, the addition of extra connections to the switch, with similar X.121
numbers (the first five digits are always 23429 for a call to node 01), only the configuration and X.25
table of node 01 need be updated, since the X.25 table of all the other nodes is already set up for calls
beginning 23429.
The diagram below describes how to specify several routing alternatives by defining additional "resource"
names for the inter-switch links.
N01* (0)
N02* (1) N01* (0)
N03* (2) Node 3 Node 3 N02* (1)
N05* (3) N03* (2)
N06* (4) N04* (3)
N07* (5) N06* (4)
"*** (6) N07* (5)
"*** (6)
"*** (n)
"*** (n)
Node 04 Node 05
N01* (0)
N02* (1) N01* (0)
N03* (2) N02* (1)
N05* (3) N03* (2)
N06* (4) N04* (3)
N07* (5) N06* (4)
"*** (6) N07* (5)
"*** (6)
"*** (n)
N01* (0) N01* (0) "*** (n)
N02* (1) N02* (1)
N03* (2) N03* (2)
N04* (3) N04* (3)
N05* (4) Node N05* (4)
N06* (5) 07 N06* (5)
"*** (6) "*** (6)
"*** (n) "*** (n)
Call request packet

received 23429320016
Figure 1-4 Setting up a number of routing alternatives
When a particular route is unavailable, because of a link failure or because all the link's "resources" are
in use, the network can be configured to select an alternative route automatically.
For this, the same "resource" name must be declared on each possible link, with a definition of the
appropriate resource priorities to indicate the first choice route.
General
E Page 1-12
The system configuration needs to include the CP (CALL PRIORITY/) and RP (RESOURCE PRIORITY/)
parameters, as follows:
Call request packet

sent 23429320016
NAME/ HST*
CP=1 CP=1
NODE 01
NODE 03
N01*
RP=2
LOOP BAR/ 1
N01
CP=2 RP=1 CP=2
N01* N01* N01*

RP=2 RP=1 RP=1
CP=2
CP=2 CP=1
NODE 04 NODE 07 NODE 05
N01* N01*
RP=2 RP=1
CP=2
Call request packet

received 23429320016
Figure 1-5 Use of call priorities and loop barring
Before analyzing the above, it is worth reviewing the rules governing how the CALL PRIORITY/ and
RESOURCE PRIORITY/ parameters should be set up:
An incoming call over a "resource" with the CP parameter specified can be routed only over an outgoing
"resource" for which the RP parameter is the same or less. Preferably, the call tries to take a route via a
"resource" of equal priority, and if there is no such "resource", the Megapac tries to route the call to a
"resource" with an RP setting of one lower (and so on, in descending order).
In the example:
• A call is received by node 07 over a "resource" for which CP is set to 2, and leaves the switch via a
"resource" for which RP is also 2 (connected to node 04). If the outgoing "resource" is unavailable,
the call is switched to the "resource" for which RP is 1 (connected to node 05).
• The call arrives at node 04 over a "resource" with CP=2, and leaves via a "resource" with RP=2
(connected to node 01). If the outgoing "resource" is unavailable, the call is switched to the
"resource" with RP=1 (connected to node 03).
• If the call had been routed via node 03 from node 05, it would have arrived over a "resource" with
CP=2, and would have left over a "resource" with RP=2 (connected to node 01). If the outgoing
"resource" had been unavailable, the call would have been switched to the "resource" with RP=1
(connected to node 04), and then routed to node 01.
• However, if the "resource" outgoing from switch 04 to switch 01 were unavailable, node 04 would try
to loop back to node 03. To avoid this, the LOOP BAR PRIORITY/ parameter for the link to node 03
is set to 1 (equal to the RP parameter).
General
E Page 1-13
• Similarly, if the call had arrived at node 03 from node 04, it would have arrived over a "resource" with
CP=2, and left over a "resource" with RP=2 (connected to node 01). If this "resource" were not
available, Megapac would normally try switching to the "resource" with RP=1 (loopback to node 04).
To prevent this case, the LOOP BAR PRIORITY/ and RP parameters are set to 1.
The call is cleared if no alternative route is available.
1.9 "Line Group" load balancing
Load balancing is another way of maximizing use of the descriptors and logical channels in a Megapac
switch. This mechanism can be set to operate between two or more descriptors.
The LINE GROUP/ parameter can be anything from 0 to 15.
When LINE GROUP = 0, load balancing is not applied.
The LINE GROUP settings 1 to 15 activate load balancing.
The resources belonging to the links of the highest LINE GROUP (15) are used first.
For resources belonging to links of the same LINE GROUP, the load is distributed evenly according to
requirements. CRC errors also change the order in which the links of a LINE GROUP are scanned.
The LINE GROUP parameter supplements the basic rules for routing calls based on the RESOURCE
PRIORITY/ and CALL PRIORITY/ parameters. It simply describes the order in which descriptors are
scanned.
Example
The Megapac node in the figure below has three X.25 links, each supporting three logical resources.
Links SRT1 and SRT2 have the same LINE GROUP (4 for example).
Call request packet X

2 SRT1/ LG4
Load 5 RESS/RP2
ENTR/ X balancing
2 function
RESE/ CP2 5 X
2 SRT2/ LG4
5 RESS/ RP2
Figure 1-6 Even distribution on links of equal priority
The output links for which the weighting factor is the lowest is selected to route the call request packet.
On each outgoing link:
1. the weighting factor is incremented by one when a call request packet is routed,
2. the weighting factor is decremented by one on processing a call clearing packet,
3. in the absence of traffic, the weighting factor is zero.
General
E Page 1-14
E
1.10 « Line Group » Overflow
The line group parameter can be used to ensure the overflow function from a main link to a secondary
link.
The Megapac node in the figure below, has two X.25 links outgoing (SRT1 and SRT2).
• The main link SRT1 is from the LINE GROUP 4,
• The secondary link SRT2 is from the LINE GROUP 3,
• The links SRT1 and SRT2 have resources with the same name (RESS).

2 SRT1/ LG4
Overflow 5 RESS/RP2
ENTR/ X
2 function
RESE/ CP2 5 X
2 SRT2/ LG3
5 RESS/ RP2
Figure 1-7 Overflow from a link to another
For each call request packet selecting a destination resource « RESS »,

• the SRT1 link resources are assigned at first.
(the SRT1 has the biggest line group)
• when all the SRT1 link resources are busy, the SRT2 resources with the same name are assigned
(the SRT2 link has a line group inferior to the SRT1 link).
General
E Page 1-15
E
1.11 Rescue link monitoring
During an operation with a « main link » and a « rescue link », the Megapac realizes, thanks to its routing
functions, the swing to the rescue link in case of the main link failure.
When the main link is working again, the Megapac offers a « Monitoring » function which helps to get
back to a normal activity, that is, to use the main link.
There are two possibilities:
1.11.1 Link monitoring with transports
In this case, the main and the rescue link have identical NAME/.
The first character of the rescue link is « $ ».
The « monitoring » function is ensured by the transport.
The X.25 descriptor chapter describes the transport layer.
T
R
Call request packet A
N
X
S
P
2 PSRT/ LG2
T
R
O
R 5 RESS/
ENTR/ X A
N Monitoring T
2 S
P with T
RESE/ 5 O
R transport R
A X
T
N
S 2 $SRT/ LG1
P
O 5 RESS/
R
T
Figure 1-8 Transport monitoring
1.11.2 Link monitoring without transport
In this case, the main and the rescue link have identical NAME/.
The last character of the rescue link is « $ ».
The « Monitoring » function is ensured by a « V25B » descriptor resource.
The « V25B » descriptor chapter describes its application.

2 SRT1/ LG2
Monitoring 5 RESS/
ENTR/ X (without
2 transport)
RESE/ 5 X
2 SRT$/ LG1
V25B 5 RESS/
E
Figure 1-9 Monitoring without transport
General Page 1-16
E
1.12 Link speed
An asynchronous or synchronous link can be configured in several ways depending on whether the
equipment used is a Megapac E08B or E15, a Megapac ESL or Megafrad, a Megabox or Megabox SL,
or a Megapac VME21.
Depending on the type of connection card used, the available clock speeds (SPEED parameter of the
link descriptor) are as follows:
SPEED Megapac E08B - E15 Megapac ESL

Megabox and Megabox SL and Megafrad
SIO (1) MIO SIO (1) MIO XIO
Asynchronous Asynchronous Synchronous Synchronous Synchronous Asynchronous Synchronous
300 l l l l
600 l l l l
1200 l l l l
1200-75 l
75-1200 l
1800 l l l
2000 l l l
2400 l l l l l l
3600 l l l
4800 l l l l l l
7200 l l l
9600 l l l l l l l
14400 l l
19200 l l l l l l l
28800 l l
38400 l l l
48K l
57600 l l
64K l l l
115200 l l (2)
128K l l
256K l l
512K l
1024 K l
2048 K l
Note (1) also for the SIO card of the Megapac VME21.
E
(2) only for the high bitrate interfaces of the Megapac ESL and Megafrad.
The clock speed of the XIO card of the Megapac VME21 is determined by straps.
The available speeds range from 300 bit/s to 2048 kbit/s.
General Page 1-17
E
1.13 Bandwidth Management
1.13.1 On the X.25 link
The Megapac can manage the virtual circuits bandwidths of a X.25 link.
For an X.25 link, the parameters « Bandwidth » at the level of the link descriptor, and the one at the level
of the associated resources are for selecting a routing on a link resource whose available throughput is
higher than the required one.
Moreover, once the routing realized, the same parameters can limited each virtual circuits throughputs,
in order to guarantee the bandwidth assigned to each virtual circuit.
1.13.2 On the Frame Relay link
The Megapac can control the information flow of each user.

The control procedure admits some bursts from the user, but these ones are limited.
For each DLCI (Data Link Connection Identified), the user can adjust the parameters.
« CIR » Committed Information Rate
« Bc » Committed Burst size
« Be » Excess Burst
1.14 Software versions compatibility
The Megapac 600 software version has new functions compared to the previous versions (500, 400, 300,
200, 107, 073, etc .). In this version, new descriptors and new parameters are inserted. An accurate
configuration for a previous software version is not directly compatible with the 600 software.
General
E Page 1-18
E
1.15 Block diagram of call routing
You can refer back to this block diagram as you read through this document. In it you will find the basic
call routing mechanisms. It refers to various information detailed in the ensuing sections.
yes
X25 svc User indicates NAME table indicates no PASS table indicates
destination resource destination resource destination resource
CONS svc
NONE NAME PASS
TALK optio n yes
on resourc e Presentation mode
Incoming call Option? X28
no no
Extended no match in yes
TERM asyn Call Management X.25 table?
= IN
yes
CONS pvc MAC table
input with yes
TALK option
X25 pvc no
no
MAC table indicates yes
QLLC destination resource
SDLC
DRC MASK of resource

HDLC indicates a
"destination resource"
TERM bsc
Destination resource selected according

to priorities (CP >= RP)
and LINE GROUP.
LAN-TLAN
Match sought for

IP-TIP MAC, IP, IPX address
in MAC table
IPX-TIPX
Match sought for

ILAN TSAP address
in ILAN table Call request
packet constructed
Figure 1-10 Block diagram of call routing
General
E Page 1-19
General
E Page 1-20
2. Operating procedures
Any computer system must have a man/machine interface for dialogue between the operator and the
software providing the computer function.
In Megapac, configuration is performed via an asynchronous terminal:
• connected locally to the CPU board's command port A, or
• remotely, via an X.25 link.
It is then necessary to access the Virtual Command Port (VCP) through which the Megapac set-up
procedures are conducted.
This is a virtual port. However, any physical port can be used to access the VCP locally or remotely.
The VCP is identified by a name which is simply typed in to access it.
The "BASE" prompt is displayed when access to the VCP is obtained, enabling you to access all the
Megapac set-up commands.
2.1 Man/machine interface
2.1.1 Operator terminal
The operator terminal is an asynchronous terminal connected locally to command port A of the
Megapac's CPU board, or connected remotely via an X.25 link.
The terminal must be set up at logical resource level as follows:
• TERMINAL TYPE = ASYN (asynchronous terminal).
• SPEED = 9600 (data rate = 9600 bit/s).
• DATA BITS = 8 (number of data bits in the data format).
• STOP BITS = 1 (number of stop bits in the data format).
• PARITY = NONE (data format without parity).
2.1.2 Accessing the Megapac configuration
Having powered up the Megapac, or pressed the RESET button on the CPU board, the ready prompt
should be displayed on the operator terminal's screen.
Type BE00 and confirm with a carriage return <CR>.

☞ These four characters represent the default name of the logical resource representing the
virtual command port VCP.
Normally, the system then displays the time and date at which the operator session was opened.
The "BASE" prompt is displayed, indicating that you have accessed the Megapac's virtual
☛ command port.
E
You can now set up the Megapac or view its current configuration details.
Operating procedures Page 2-1
If the BASE prompt is not displayed, this means that BE00 is not the name of the logical resource
corresponding to the virtual command port VCP. In this case, you must proceed as follows to find the
name assigned to the VCP:
Press the ABORT button on the CPU board.
☞
The "BASE" prompt appears on the terminal screen.
Press the \ key then confirm: \<CR>.
☞
The first four characters displayed are the name assigned to the VCP logical resource.
Press the RESET button on the CPU board or type the BOOT command.
☞
The READY prompt appears on screen.
Type in the NAME of the VCP logical resource and confirm.
☞
"BASE" prompt should appear, indicating that you have accessed the Megapac's virtual
command port.
2.1.3 Operator commands
When you have accessed the VCP, you have a set of commands for viewing the current Megapac
configuration, or modifying its characteristics. Most of the Megapac commands are single words with
three or four letters, such as: EXAM or CONF. These words make up the command language.
Some of the commands enable the operator to access a given context - X.25, for example, to access the
X.25 table - while others are for working in an established context - EXAM, for example - for viewing the
characteristics of a preselected link descriptor.
All commands, apart from the single-character commands, must be activated by a carriage return,
indicated by <CR> throughout this manual. The Megapac editor is like a line editor, but the modify
commands are totally independent of each other.
In other words, one command gives access to a mode from which you must exit before you select
another. When you use a function command (EXAM, for example), this becomes the current active
function. It is executed automatically when you access a link descriptor, a logical resource or a table
using one of the navigation commands (apart from GOTO). It remains active until replaced by another
function command or terminated explicitly.
The escape character <ESC> lets you terminate the current mode.
The table below contains all the MEGAPAC operator commands which are explained in detail in the
remainder of this section. The MEGAPAC operator commands are arranged in three broad categories:
• Navigation commands: these are for accessing a link descriptor, a logical resource in a link
descriptor or a routing table. Access can be obtained either directly by typing the name of the item
concerned, or sequentially by moving from one item to the next in turn.
Operating procedures
E Page 2-2
• Function commands: these are for executing a function on a link descriptor, a logical resource or a
table previously selected using the navigation commands. This broad category comprises:
• view commands for displaying the current configuration settings of a link descriptor, a logical
resource or a table, or statistical data concerning a descriptor or channel,
• modify commands for modifying the configuration of a link descriptor, a logical resource or a
table,
• control commands, for running a diagnostic function on a link or logical channel.
• System commands: these are for performing various software downloading and Megapac
configuration management functions, plus, for example, resetting or shutting down the system.
NAVIGATION FUNCTION SYSTEM

COMMANDS COMMANDS COMMANDS
Direct selection Movement Display Modify Control System
XXXX* > EXAM CONF REST MEM
X25 < LIST COPY STOP LOAD

PROF ALL ALL ALL CLOS RUN
MAC \ STAT DELE TEST HALT
ILAN GOTO POLL INSE V54R BOOT
NAME VIEW SET V54L DERR
PASS CALL LINE V54X DUMP
MENU / – SEND GET
HELP = ? CMND TIME
BILL @ SAVE
ELOG & RUBC
RUBP
<ESC>
<BS>
QUIT
∗ XXXX is the 4-character name given by the user to a link descriptor or logical resource. XXXX
also represents the name assigned by default by the software to the unconfigured link
descriptors.
☞ The table names (X25, PROF, ..., BILL, ELOG) must not be used as link descriptor and/or
resource name.
E Page 2-3
E
2.2 Navigation commands
You use the navigation commands to access a data table, a link descriptor or a logical resource.
They can be used alone, or in combination with a command function (see below). If an appropriate
function command is active and you select an element by its name alone, Megapac automatically
executes the active command on the selected item.
The Megapac data structures are organized in routing tables and in two hierarchical levels:
• link descriptors, each attached to a link set up via a physical system port,
• logical resources representing the virtual circuits which can be used on a given link.
When you access a link descriptor, the command line prompt contains the name of the descriptor
followed by a colon (:). For example:
PS01:
When you access a logical resource or a routing table, the prompt contains the name of the logical
channel or the table, followed by the number of the logical channel or record (in brackets) and a colon (:).
For example:
P100(0): or
X25(0):
When you access a transport level logical channel (applicable only for ISO applications), the logical
channel name is prefixed by a hash sign (#) and followed by the reference number of the channel
between brackets and a colon (:). For example:
#TRAN(4): or
#P100(3):
To access a link descriptor or logical resource, you have two options:
• Direct access by identifying the name of the item concerned, or
• Sequential access by navigating through the hierarchy of link descriptors and, within each, through
the list of logical resources assigned to them.
The data tables are accessed directly by identifying the table concerned. The navigation commands are
then used to move from one record to another in the selected table.
E Page 2-4
2.2.1 Direct access navigation commands
The table below summarizes the names of the various tables and other Megapac set-up items which,
when typed in from the operator terminal, provide access to the data table or to the particular item to be
configured.
Action Displays Effect

XXXX<CR> XXXX: Selects the link descriptor named XXXX (PS01, for example)
XXXX<CR> XXXX(0): Selects the logical resource named XXXX (P100, for example)
X25<CR> X25(0): Selects the first record of the X.25 table
PROF<CR> PROF(0): Selects the first record of the PROF (profile) table
MAC<CR> MAC(0): Selects the first record of the MAC (macro) table
ILAN<CR> ILAN(0): Selects the first record of the ILAN table
NAME<CR> NAME(0): Selects the first record of the NAME table
PASS<CR> PASS(0): Selects the first record of the PASS table
MENU<CR> MENU(0): Selects the first record of the MENU table
HELP<CR> HELP(0): Selects the first record of the HELP table
BILL<CR> BILL(0): Selects the first record of the BILL table
ELOG<CR> ELOG(0): Selects the first record of the ELOG table
E Page 2-5
2.2.2 Sequential access navigation commands
You have a set of five commands for navigating within the Megapac data structures.
• Command >
Simply by pressing the > key, you can navigate within a particular level of the data structure, organized
in ascending order.
This means that you can move from one link descriptor to the next in turn and in order, or from one
logical resource to the next within a link descriptor, and also from one record to the next within the same
table.
If a function command is active, it is executed immediately at the new access point.
In configuration mode (activated by the modify command CONF<CR>), you can use the > key to finish
inputting a parameter for a link descriptor, a logical resource or a record, and go on to define the same
parameter for the item with the next number (without quitting the configuration mode).
• Command <
You can press the < key to perform the reverse of the > key function, in other words, to navigate within a
particular level of the data structure, in descending order.
• Command \
Press the \ key to toggle between the "link descriptor" and "logical resource" levels of a particular
descriptor.
Any currently active command will be executed automatically whenever you use this key.
If the transport level is active for a given link descriptor, this key lets you access the transport session of
each logical resource of the link descriptor.
• Command ALL<CR>
You can use this command to move from the current position to the end of the selected descriptor,
logical resource or table.
If a function command is active when you issue the ALL command, the function command is executed
immediately.
You can also use the ALL command as a modifier at the end of a command line. The command is then
executed automatically on all the data concerned. For example, COPY ALL<CR> lets you copy all the
parameters of an item.
• Command XXXX GOTO N<CR>
You can use this command to select a particular logical resource of a given link descriptor, or a specified
record of a given table, by indicating the name XXXX of the resources of a link or of the table concerned,
followed by the number N of the logical resource or particular record to be accessed.
This will prove particularly useful if you cannot directly access a channel with the same name as other
logical channels (as in the case of P100(0), P100(1), P100(2), P100(3), etc.).
You can use the GOTO command at the system prompt for a link descriptor or logical resource.
Remember that the GOTO command deactivates all active commands, and, obviously, you cannot use it
with the modifier ALL which is therefore inoperative.
The figure on the next page illustrates the free structure of the various link descriptors and logical
resources implemented, and summarizes the sequential navigation commands for moving around the
data structure in configuration memory using the movement keys (>, <, \).
E Page 2-6
E
"Link descriptor"
Link descriptor Link descriptor
Descriptor > Descriptor > Descriptor > PS01 > PS02
BASE EPCI
level
NMSC (default name) (default name)
< < < <

\ \ \ \ \
Figure 2-1

VCP logical "States" logical
resource resource Logical resource Logical resource Logical resource
BE00(0) EI00(0) NC00(0) P100(0) P200(0)
"Logical resource" level

(default name)
Navigation commands
(default name) (default name)
> > > >

< < < <
"Session
statistics" Logical resource Logical resource Logical resource
E
logical resource NC00(1) P100(1) P200(1)

EI01(1) (default name) (default name) (default name)
(default name)
> > >

< < <
Page 2-7
E Action
X25<CR>
>
Displays
X25(0):
X25(1):
Accesses the X.25 table

Effect
Displays the number of the next record in the X.25 table

> X25(2): Displays the number of the next record in the X.25 table
< X25(1): Displays the number of the previous record in the X.25 table
BASE<CR> BASE: Returns to the BASE descriptor
> EPCI: Moves you to the next descriptor, EPCI
> NMSC: Moves to the next descriptor, NMSC
> PS01: Displays the link descriptor names in turn
(< goes back through the names)
EI00<CR> EI00(0): Directly accesses logical resource EI00 of descriptor EPCI
> EI01(1): Selects the various logical channels of descriptor EPCI named EIxx
(progress is reversed with the < key).
EI00 describes the VCP to which your terminal is connected if you
dialogue with Megapac via the command interface
\ EPCI: Toggles between logical channels EIxx and their associated link descriptor
(EPCI)
\ EI00(0): Moves from the descriptor to the first resource controlled by it
PSO2 GOTO P200(3): Entering this command from any Megapac system prompt takes you
3<CR> directly to logical channel number N (3 in the example) of the link
descriptor identified by its name (PS02, in the example).
BASE: X25<CR>
X25 (0): >
X25 (1): >
X25 (2): <
X25 (1): BASE<CR>
BASE: >
EPCI: >
NMSC: >
PS01: EI00<CR>
EI00(0): >
EI01(1): \
EPCI: \
EI00(0): PS02 GOTO 3<CR>
P200(3):
E Page 2-8
E
2.3 Function commands
The three classes of function commands respectively let you view the Megapac's current configuration
parameters, modify one or more of the current configuration parameters and control the behavior of the
network's links.
2.3.1 Display commands
CALL You use this command to display information on current calls on a given logical channel, in the
form of source and destination addresses. It therefore does not apply to link descriptors or
tables.
However, when run using a link descriptor, it accesses the first logical channel (number 0) of
the descriptor.
The command CALL ALL<CR> entered at the link descriptor prompt calls up a display of all
calls corresponding to the descriptor. Remember that the CALL command displays the
addresses translated where the addresses have been translated by the Megapac.
To display only those calls for which the source or destination addresses begin with one or
more known digits, specify those digits, prefixing them with the hash character (#). For
example, the command string PS01 CALL #231 ALL<CR> will call up a display of all calls for
link descriptor PS01, with source or destination addresses beginning with the digits 231.
BASE: CALL<CR>
BE00(0): ** NONE **
BE00(0): PS05<CR>
P500(0): ** NONE **
P500(0): >
P500(1): >
.
.
.
P500(15): <- 8000
P500(15): <CR>
BASE:
E Page 2-9
E
EXAM
Use this command to examine the configuration parameters of a table, a link descriptor or a
logical channel. This command does not apply to the BILL or ELOG tables which do not
contain configurable parameters.
As a rule, the parameters displayed are arranged in two or three columns. If the content of a
column exceeds the column width, the display is adapted automatically without affecting the
legibility of the information.
For X25 link:

PS02: exam
NAME/ PS02 TYPE/ X25 SUB-TYPE/ XIO+SIO

NEW PHYSICAL INTERFACE/ YES SPEED/ 9600
PACKET SIZE/ TRAN BANDWIDTH/ 0
V54 MODEM/ NO ADDRESS/ DCE CHANNELS/ 16
OPTIONS/ NONE INIT FRAME/ SABM
T1/ 30 T3/ 60 TRIES/ 10
K LEVEL2/ 7 K LEVEL3/ 2 LINE GROUP/ 0
LCGN/ 0 LCN OFFSET/ 0 ADDRESS GROUP/ 0
FRAME SEQ/ NORM CALL TIME OUT/ 5
ERROR THRESHOLD/ 20 LOOP BAR PRIORITY/ 0
EXTENDED CALL MANAGEMENT/ NONE OPTIONAL TIMERS/ NONE
OPTIONAL FLAGS/ 0 TRANSPORT LEVEL TYPE/ NONE
TRANSPORT CLASS/ 0 DEFAULT WINDOW SIZE/ 0
DISABLE FLOW CONTROL/ NO TSAP FORMAT/ HEX
MAXIMUM TPDU SIZE/ 128 TTR/ 0
TWR/ 0
For Frame Relay link:

PS03:exam
NAME/ PS03 TYPE/ NFRM SUB-TYPE/ XIO

NEW PHYSICAL INTERFACE/ YES SPEED/ EXT
CHANNELS/ 1 ADDRESS/ 300 MODE/ DTE+DCE
LMI/ ANSI KEEP ALIVE TIMER/ 3
POLL INTERVAL/ 6 TRIES/ 3
OPTIONS/ NONE BANDWIDTH/ 0 Bc/ 0
Be/ 0
LIST This command provides a continuous display of configuration parameter settings associated
with a table, a link descriptor or a logical channel. In this case, the names of the parameters
are not displayed.
☞ To display the configuration parameters for the logical channel named EI00, for example,
type, at the BASE prompt:
EI00 LIST<CR>
The system then displays the list:
▼
BASE: EI00 LIST
EI00 .... ASYN CALL+PVC+STAT MSGS 2 11 1 0 0 0 0 0 D 0 E 0 0 E D 1 0

E 0 0 D 0 0 0 0 NONE 0 0 0 0 NONE 0
BASE:
E Page 2-10
E
STAT
This command displays statistics and variable status information for a link descriptor or a
logical channel. On the display, the value of each variable is given alongside the variable
name. Remember that this command cannot be used for examining tables, because these
tables do not contain statistical or status information.
When you request "STAT" for the descriptor "BASE", the display shows in particular the
installed software version number, the time and date the system was last booted and the
maximum system packet size.
☞ To display connection statistics for link PS02, for example, at the BASE prompt type:
PS02 STAT<CR>
The system then displays a list of statistics:
▼
PS02: stat
TYPE/ X25 EIA/ 1 1 1 1 CRC ERRORS/ 0

RETRANSMISSIONS/ 0 REJECTS/ 0
TOTAL CALL SET-UPS/ 32 CURRENT CALLS/ 32
FRAME SEQ/ NORM STATE/ DATA SUB-STATE/ NORM
NR/ 2 VS/ 3 TRIES/ 3
VR/ 7 VR(SENT)/ 0 OPTIONS/ NONE
LCGN/ 0 DATA IN/ 719662080
DATA OUT/ 719779328 DATA FRAMES IN/ 1405616
DATA FRAMES OUT/ 1405849 DATA FRAME RATE IN/ 229
DATA FRAME RATE OUT/ 228 CALLS RECEIVED/ 16
CALLS SENT/ 16 CLEARS RECEIVED/ 0
RESETS RECEIVED/ 0 INTERRUPTS RECEIVED/ 0
REMOTE LOOP STATUS/ NONE LOCAL LOOP STATUS/ NONE
OUTPUT QUEUE LENGTH/ 0
For PS03 Frame Relay link:

PS03: stat
TYPE/ NFRM EIA/ 1 0 1 1 CRC ERRORS/ 0

STATE/ DISC SUB-STATE/ IDLE LMI/ DOWN
DATA IN/ 0 DATA OUT/ 0 DATA FRAMES IN/ 0
DATA FRAME RATE OUT/ 0 OUTPUT QUEUE LENGTH/ 0
RCV BECN/ 0 RCV FECN/ 0 DE/ 0
THROUGHPUT/ 0 TIMER/ 10 TX SEQ LOST/ 0
RX SEQ LOST/ 0 TX SEQ/ 5 DCE TX SEQ/ 0
RX SEQ/ 0 DCE RX SEQ/ 0
POLL Like the STAT command, the POLL command provides a continuous display of statistical
variable values, but without naming the variables. In a way, STAT and POLL can be regarded
as dependents of EXAM and LIST.
PS02 POLL<CR>
X25 1 1 1 1 0 0 0 0 32 DATA 6 0 3 3 0 12851 13076 251 256 227 226 0 0 0 0

0
PS03 POLL<CR>
NFRM 1 0 1 1 0 0 0 DISC IDLE 0 0 0 0 0 0 0 0 0 0 0
E Page 2-11
E
VIEW
The effect of the VIEW command varies according to the context in which it is used.
For example, if you use it at the BASE: prompt, or if you type VIEW BASE<CR>, you obtain a
display of all status information for all link descriptors for which the TYPE/ parameter is set to
X.25.
On a logical channel or an X.25 (and other) type link level descriptor, the VIEW command
calls up a summary of calls. This summary contains the source and destination addresses on
the link (or the descriptor). Remember that the VIEW command displays the addresses
translated where they have been translated by the Megapac.
On a LAN or IP type logical channel or link descriptor (or if you type VIEW XXXX, where XXXX
is the name of a LAN or IP descriptor), the VIEW command displays the MAC (Ethernet) or IP
addresses mapped on the router bridge.
Like other commands, you can have it repeated automatically by typing "/" or navigating within
the configuration data structure.
BASE: view
Link State Errors Curr Calls Rate in Rate Out
PS02 SABM 0 0 0 0
PS04 DISC 0 0 0 0
PS05 DATA 0 1 0 0
PS06 DISC 0 0 0 0
BASE: PS02 view

Channel Calling Called Direction
P200(2) 123 OUT
BASE: PS03 view

Link DLCI State Sub Errors Becn Fecn Throughput
PS03 300 DATA IDLE 1 0 0 2
/ This key (oblique slash) repeats the last command and redisplays the variables with new
values where appropriate.
= This key (Equal sign) is used to toggle between the channel on which a call is incoming and
the channel to which it is onwardly connected.
incoming channel → outgoing channel
←
E Page 2-12
E
2.3.2 Modification commands
Modification commands (like some system commands) let you modify the configuration of the Megapac
system.
☛ Make sure that you are fully aware of the effect of the commands before you start to
use them, because their effects can be irreversible.
? When modifying a parameter, use the question mark (?) to determine the possible settings of
the current parameter.
CONF You use this command whenever you want to create or modify records in a table or
parameters of a link descriptor or logical channel. Remember that the BILL and ELOG tables
cannot be modified by the user, because they contain only general information collected by
the Megapac system.
Once started, the CONF command remains active until canceled (by <ESC><ESC> or
<SPACE><SPACE>); the Megapac then takes you to the BASE link descriptor. When you
have displayed the last parameter, <CR><CR> also takes you to the BASE descriptor.
The configuration mode remains active if you press <ESC> or <SPACE> only once; you
simply terminate the table, link descriptor or logical channel configuration process.
If you do not want to quit the configuration mode, use the navigation commands to select the
link descriptor, logical channel or table record to be modified.
The configuration procedure for a table, a link descriptor or a logical channel always begins
with a display of the first configurable parameter followed by its current setting. To change this
setting, type the new setting at the cursor position and press <CR>. If you make no change,
the <CR> key calls up the next parameter. To specify a number of options for one parameter,
separate the options using the plus sign (+).
In the example below, the DRC MASK parameter is modified for a number of logical channels.
(DRC = Destination Resource Code).
BASE: EI00 CONF<CR>
EI00(0): NAME/ EI00 <CR>

EI00(0): DRC MASK/ .... >
EI00(1): DRC MASK/ .... ?
4 CHARACTERS
EI00(1): DRC MASK/ .... <ESC>
EI00(0): BE00<CR>
BE00(0): NAME/ BE00 <ESC>
BE00(0): <ESC>
BASE:
E Page 2-13
E
COPY
This command copies all the configuration parameter settings for a logical channel and applies
them to the next logical channel of the same link descriptor.
When run on the basis of a logical channel (P100, for example), it takes all the parameter
settings for that channel and copies them into the following logical channel or channels
selected in turn using the > key or all at once using the ALL command. The command string
P100 COPY ALL<CR>, for example, copies all the configuration settings for the first logical
channel P100(x) to all channels P100(x+1 to x+n). This string can be used to clear all the
settings which previously had a particular configuration which is now not required.
DELE This command deletes all the records from a table or initializes the statistics for a link
descriptor or its logical channel. The command string ELOG DELE ALL<CR>, for example,
deletes all the entries from the ELOG table. The string PS01 DELE<CR> resets the statistics
for link descriptor PS01.
Remember that the DELE command remains active until deactivated by <ESC>.
INSE This command inserts a blank record (which can be left blank or subsequently completed
using the CONF command) above the record selected in a configurable table. The prompt
displayed is for the new record; in other words, the order number of the previously selected
record and that of the subsequent records are incremented by one.
Remember that the INSE command remains active until deactivated by <ESC>. This
means that you can use the INSE command with the > key when you have to create several
new records.
LINE When you use the VIEW command, the display shows 24 lines by default. If all the
information cannot be shown on 24 lines, the message MORE appears on line 24. Type any
character apart from <ESC> to view the next page. <ESC> quits the display but the VIEW
command remains active. To deactivate it, type <ESC><ESC> or enter a new command.
You can modify the length of the display using the LINE command followed by the required
number of lines. Then use the VIEW command at the prompt for the type of information
required.
BASE: LINE 4
BASE: VIEW
Link State Errors Curr Calls Rate In Rate Out
PS02 SABM 0 0 0 0
PS03 DATA 0 1 0 0
PS04 DISC 0 0 0 0
MORE
Link State Errors Curr Calls Rate In Rate Out
PS05 DATA 0 1 0 0
PS06 DISC 0 0 0 0
BASE:
E Page 2-14
E
SET
This command is used from a PC to set up the Megapac when downloading configuration files.
You first access a link descriptor, a logical channel or a table according to normal procedures
and then use the SET command. The parameter settings, separated by slash characters (/),
are entered in the form of a continuous string (without carriage return) and the command line
must be terminated by <ESC> or a less than sign character (<) immediately after the last
setting.
_ (Underscore character). In configuration mode, you can use this character to copy individually
one or more characters of a parameter setting. This copy command can be used only when
setting up addresses or parameters in a menu. In all other cases (part of a name or parameter
with option), the "_" character is interpreted as an underscore character.
To change the address 123456789 or record X25(0) to 123456914, for example, enter the
command X25 CONF<CR> to access the X.25 table, then <CR><CR> to move to the
ADDRESS/ parameter; then type six underscore characters to copy the first six characters of
the existing address and end with 914<CR>.
@ ("At" character). This character is used to indicate that the following character is not to be
interpreted. (e.g.: @& allows the & character to be passed over). This character can be used in
the MENU and HELP tables, along with certain record fields in the MAC table.
& ("Ampersand" character). This character is used to indicate that the following character chain,
up to the next &, is not to be interpreted.
(e.g.: &DRT_GES_PAR_____& allows the DRT_GES_PAR_____ chain to be passed over).
This character can be used in the MENU and HELP tables, along with certain record fields in
the MAC table.
E Page 2-15
E
2.3.3 Control commands
These commands are for "controlling" the links and logical channels of the network.
CLOS (For "close"). This command "closes" the selected logical channel without affecting current
calls, and prevents new calls. The channel becomes unavailable when the last current call is
cleared.
You can therefore use this command to close a logical channel in an orderly fashion, without
disturbing users currently connected, or isolate certain channels for line tests between two
Megapac switches. When based on the link descriptor, it applies to all logical channel, without
affecting the active descriptor.
The CLOS command applied to a channel is deactivated by the REST command applied to
the same channel. The command string PS03 CLOS ALL<CR> closes all the logical channels
associated with descriptor PS03. The command string P300 REST ALL<CR> applied to the
first logical channel of PS03 descriptor, restores all the channels linked to descriptor PS03.
REST (For restart). You use this command to restart a link descriptor (X25 or HDLC) or logical
channel. The configuration parameter settings are then copied from RAM into the link
descriptor or logical channel selected.
If the REST command is applied to an link descriptor (X.25 or HDLC), all the current calls on
this descriptor are interrupted. The command modifier ALL is inoperative at descriptor level to
prevent prematurely restarting all the links. The command string REST or REST ALL <CR>
can be used at link level and causes restart all the channels associated with a descriptor
(unless the channels are « CLOS »).
If applied to a logical channel, only the current call on that channel is interrupted. When the
logical channels are « CLOS », the command string REST ALL <CR> on the first channel
causes restart all the channels associated with a descriptor.
The REST command can be used on primary mode QLLC logical channels to restart polling
on a unit to which the STOP command had been applied previously.
STOP The STOP command is used to disconnect the link (level 2) of a descriptor. If there is no level
2, no information can be conveyed over the link, which is equivalent to clearing all the calls.
The statistics displayed on screen for the descriptor concerned then show STATE/ STOP.
This command can also be used on primary QLLC logical channels to deactivate the polling of
an associated terminal in a multipoint link. The STOP condition is canceled by the REST
command.
TEST The TEST command is used to test Megapac-to-Megapac links. When you run this command,
the Megapac uses the specified descriptor to send a test frame to the corresponding link
descriptor of the remote Megapac which returns it to the originating Megapac. The command
string PS01 TEST<CR> initiates a test frame over the disconnected line of the link dependent
on descriptor PS01. When a test indication or response is received, a diagnostic message is
written to the Virtual Report Channel and to the error log ELOG. This message takes the
following format:
<time><date> TEST (I or R) ABCDEFGHIJKLMNOP, (with I = indication and R = response)
The TEST command can be run only on X.25, CONS and ILAN type line descriptors. If no
loop can be set up on a link (because the Megapac is not linked to another Megapac), this
command will probably result in an FRMR frame being returned and the link being restarted.
The TEST command can be used in conjunction with V.54 loop commands. In this case, the
remote unit need not be a Megapac. The test results are represented by the REMOTE LOOP
STATUS/ and LOCAL LOOP STATUS/ variables, which are the same as those displayed by
the STAT command applied to the descriptor concerned.
E Page 2-16
E
CMND
The CMND command is used to access and modify a "reserved buffer" for the modem
configuration. The current content on the "reserved buffer" is displayed. You can then enter
the new content of the buffer, ending with <CR>.
You can use the transparency character "@" to introduce metacharacters into the Megapac
dialogue including "> < \ @ & ? / etc".
The maximum length of the "reserved buffer" is 64 characters and it is cleared when Megapac
is rebooted.
SEND The SEND command is used to send a UI (unnumbered information) frame over a Megapac
X.25 link, the information field of which is the content of the "reserved buffer" (see CMND).
If the X.25 link crosses an XIO interface, it must be configured with the UI option. Viewing the
response requires the V54R (or V54L) loop which means that the V54 MODEM parameter
must be set to YES. The SEND command automatically releases level 2.
If the X.25 link crosses an SIO interface, it must be configured with the UI option. This is also
sufficient to view the response.
From a PSXX link descriptor, the SEND command sends the content of the "reserved buffer"
over the PSXX link.
From the BASE prompt, you can activate the PSXX SEND <CR> command.
The SEND command can take three seconds to be executed.
The response displayed has a maximum of 64 characters.
2.4 System commands
<BS> If you make an input error in a parameter setting (in configuration mode), you can use the
"backspace key" (<BS>, equivalent to Ctrl-H on a PC keyboard) to delete input one character
at a time. If no setting is entered, the <BS> key displays the previous parameter of the same
link descriptor, the same logical resource or the same table.
ESC The escape command terminates execution of a command or, after using a navigation
command, displays the system prompt BASE.
BOOT This command restarts the system and restores the configuration settings stored in RAM. All
calls are cleared. The BOOT command must be used after making any change to the
memory configuration with the MEM command or after creating a link descriptor.
DERR This command is used to display the latest "fatal error" details of the system. These details are
kept in backup memory on the Megapac E08-E15 equipped with CPU-E, the Megabox-SL,
Megapac ESL/Megafrad, and the Megapac VME.
DUMP This command is used to back up the current configuration in a file (MS-DOS file, for
example) for subsequent re-use (downloading).
GET This command can be used to back up, on a PC, for example, preselected elements of a
configuration (a link descriptor, logical resource or table) for subsequent downloading.
HALT This command is a function of the software downloading system. It can be used to revert to
the software contained in EPROM (see the RUN command). It toggles the software in RAM
from ACTIVE to LOADED and boots the system. It is then the EPROM software which is run
when the system is subsequently rebooted, until the next RUN command. Any attempt to use
HALT when the EPROM software is active will result in display of the message ERROR.
The HALT and RUN commands always cause all calls to be cleared when the system is
rebooted.
E Page 2-17
E
LOAD
This command is a function of the software downloading system. It can be used to download
the system software into the Megapac's battery-backed RAM.
When this command has been entered, the system waits for a preformatted ASCII file to be
transferred. Remember that the downloading operation does not affect normal operation of
the Megapac and does not cause the system to be rebooted.
In a MegaPAC ESL and/or a MegaFRAD, the RUBP command (rubout program) must precede
the LOAD command.
RUBP This command is specific of the MegaPAC ESL and MegaFRAD.
In a MegaPAC ESL and/or MegaFRAD, this command allows the rubout of a downloaded
software. This command is required before starting the downloading by the LOAD command.
MEM You use the MEM command to assign the memory space required for each configuration table
in battery-backed RAM, and define the number of records allowed for X.25, MAC and other
tables. The memory size is calculated according to requirements.
As with the CONF command, the Megapac prompts you to enter information one parameter at
a time and displays the current setting of the parameter. Here, too, the ? and <BS> keys
operate in the same way and have the same effects as in the CONF command.
Press <ESC><ESC> to quit the current configuration process.
☛ When a parameter is changed in the MEM table, you must use the BOOT command to
activate the changes and ensure data consistency.
QUIT This command forces the Megapac to interrupt the connection established with the BASE link
descriptor (default resource name: BE00).
RUN This command is a function of the software downloading system. When the ASCII file has
been transferred into RAM using the LOAD command, the RUN command switches the
downloaded software to the ACTIVE state and then reboots the system. If no error is detected
in the downloaded software, and provided that the HALT command is not run, the new
operating system will be run each time the system is subsequently rebooted. Any attempt to
use RUN when the downloaded software is active will result in display of the message ERROR.
TIME The TIME command is used to set the system date and time. Date and time information are
used by the system to time-stamp charging records, error log records, reports and so on.
SAVE This command allows to define a personalized configuration by default from the current
configuration. The SAVE command works only if the previous personalized configuration by
default has been rubbed out by the RUBC command.
This command is available with CPU-D or CPU-E cards from Megapac - Megabox boxes, and
with Megapac ESL - Megafrad boxes.
RUBC This command allows to rub out the personalized configuration by default.
This command is available with CPU-D or CPU-E cards from Megapac - Megabox boxes, and
with Megapac ESL - Megafrad boxes.
SAVE On Megapac VME21 and VME9 versions with CPU-60 boards installed, the SAVE and RUBC
RUBC commands can be used to save or delete the personalized, default configuration, depending
on the system software currently running. The CPU-60 board will store four different system
CPU-60 software versions and their respective personalized, default configurations.
(Refer to the TELELOAD ENABLE/ NO YES 2ND 3RD parameter of the BASE descriptor).
E Page 2-18
3. Memory configuration
Link descriptor information, the definitions of logical channels and the routing files form the basis for a
particular allocation of RAM memory. You use the MEM command to access the MEM table and enter
the allocation parameters.
As a rule, the default settings for the various parameters in the MEM table should be adequate for most
configurations.
% However, it is important to plan and organize the configuration process correctly to

be allowed the option to keep the default settings or modify them.
The following table shows, in the order in which they appear in set-up mode, the memory allocation
parameters with their default settings.
Memory configuration
E Page 3-1
E
3.1 « MEM » table
PARAMETER RANGE OF
MEANING AND SCOPE
NAME SETTINGS
RESET N (by default) Parameters in the MEM table are not reset.
Y Parameters throughout the MEM table are reset to
their default settings on next boot.
All current data for all tables is deleted.
The MEM RESET = YES command from downloaded
software retains this software providing the software in
PROM is from the same family.
(Before modifying « MEM SIZE » any personalized
default configuration must be erased by using the
command « RUBC »)
SIZE 7680 to 63488 Number of bytes allocated to configuring system
descriptors and resources.
By default:
20448 (CPU-E) The default setting depends on the type of CPU board.
20430 (CPU-VME) The default setting « 20448 » is that of the CPU_E;
« 20430 » for CPU_V and CPU_40 boards.
NUMBER OF MENUS Setting from 1 to 32 Number of records (screens) in the MENU table
(presentation mode).
By default: 1 Each record occupies 1024 bytes.
NUMBER OF HELP Setting from 1 to 32 Number of records in the HELP table (help displayed to
SCREENS the user).
NUMBER OF PASSWORDS Setting from 1 to 2000 Number of records (passwords) in the PASS table.
NUMBER OF SERVICE Setting from 1 to 2000 Number of records (8-character service names) in the
NAMES NAME table.
By default: 6
Each record occupies 18 bytes.
NUMBER OF X.25 Setting from 1 to 2000 Number of records in the X.25 table.
ADDRESSES By default: 32 Each record occupies 54 bytes.
NUMBER OF ISO Setting from 1 to 2000 Number of records in the ILAN table.
ETHERNET ADDRESSES By default: 16 Each record occupies 62 bytes.
NUMBER OF MACRO FILE Setting from 1 to 2000 Number of records in the MAC table.
RECORDS By default: 32 Each record occupies 74 bytes.
NUMBER OF BILLING Setting from 1 to 2000 Number of records in the BILL table.
RECORDS By default: 20 Each record occupies 70 bytes.
NUMBER OF ERROR LOG Setting from 1 to 2000 Number of records in the ELOG table.
RECORDS By default: Each record occupies 82 bytes.
- 20 (on E)
E
- 200 (on VME)
Memory configuration Page 3-2
E
3.2 Default configuration
The whole MegaPAC switch range includes a default configuration (system).

A part of the MegaPAC switch range includes a memory space dedicated to the tailored default
configuration.
3.2.1 Default configuration (system)
The default configuration (system) includes the default values detailed for each parameter described in
this manual. Particularly, the default configuration (system) includes at least 2 X25 type descriptors
(PS01 and PS02).
In the tailored default configuration’s absence, the default configuration (system) is taken into account.
3.2.2 Tailored default configuration
A memory space (memory saved by a battery or FLASH memory) allows to define a tailored default
configuration.
This function is available on the Megapac - Megabox equipped with CPU-E cards, on Megabox SL
boxes, and on Megapac ESL - Megafrad boxes.
☛ The tailored default configuration must be a minimum configuration implementing a minimum

number of descriptors (and thus a minimum number of cards) in order to allow a restart of the
system.
The tailored default configuration isn’t a backup of the current configuration.
The RUBC system command allows to rub out the tailored default configuration.
The SAVE system command allows to define a tailored default configuration from the current
configuration.
The SAVE command can work only if the previous tailored default configuration has been rubbed out by
the RUBC command. The SAVE command leads to the « ERROR » system message when the previous
tailored configuration hasn’t been rubbed out.
The tailored default configuration includes the specific table size and their contents, as well as the whole
specific parameters of the associated descriptors and resources.
3.3 Returning to the default configuration (system or tailored)
Setting MEM RESET = YES returns you to the default configuration (system or tailored).
Changes to this parameter take effect on the next BOOT.
If the MEM SIZE parameter is unchanged, BOOTING restarts the system with the default configuration
(system or tailored) and table sizes adopt their default settings.
It is normal to find a reduction in MEM SIZE following each MEM RESET = YES.
E Page 3-3
3.4 Configuration memory organization
The configuration memory is divided into areas, some fixed, others adjustable (if necessary) according to
user requirements.
These areas are:
1. a reserved fixed area of 2048 bytes.
2. a fixed area of 72 bytes containing the pointers for the next two areas.
3. a fixed area containing the link descriptor configuration including descriptors of TYPE = NULL.
4. a variable area containing the resource or resource group configuration, each resource or resource
group occupying 66 bytes.
5. a fixed area of 464 bytes containing the Megapac table pointers.
6. a variable area containing the Megapac table records:
• MENU
• HELP
• PASS
• NAME
• X25
• ILAN
• MAC
• PROF (this table is fixed)
• BILL
• ELOG
• MEM (this table is fixed)
The MEM SIZE parameter controls the size of the group of areas (2+3+4), to the detriment or advantage
of the group of areas (5+6).
3.5 Procedure for changing MEM SIZE
☞ When a personalized default configuration is saved, modification of « MEM SIZE » is not

possible. Before modifying « MEM SIZE » any personalized default configuration must be erased by
using the command « RUBC ».
When you change MEM SIZE, you must at the same time request a MEM RESET = YES.
Megapac then adjusts MEM SIZE as close as possible to the setting required.
In this case, the default configuration system replaces the previous current configuration and table sizes
adopt their default settings.
3.5.1 Changing table sizes (area 6)
Changing (increasing) the number of records in a table, adds a new size table at the end of the table
area (area 6). The memory space occupied by the old table is lost.
The modification takes effect on the next BOOT.
Note: Reducing the number of records in a table is not taken into account.
Use MEM RESET/ YES then BOOT commands to return to default values.
E Page 3-4
3.6 Megapac VME with CPU-V or CPU-40 and Megapac - Megabox with CPU-E
The effective configuration memory is limited to 128 Kbytes.

By default, MEM SIZE is 20 448 (CPU-E), 20 430 (CPU-VME).
This setting lets you configure:
• 105 descriptors and approximately 160 resources with CPU-E.
• 160 descriptors and approximately 120 resources with CPU-V and CPU-40.
There is then still an area 6 of approximately 107 000 bytes for the Megapac tables.
The maximum setting for MEM SIZE is 63 448.
If the number of resources is insufficient, you must change MEM SIZE.
Area 1 2048 bytes (reserved) 0

Area 2 72 bytes (pointers)
Area 3 Link descriptor configuration.
(including TYPE=NULL descriptors)
105 x 80 bytes = 8400 bytes (CPU-E)

160 x 80 bytes = 12800 bytes (CPU-V, CPU-40)
Area 4 Resource configuration MEM SIZE
One block of 66 bytes for each resource or resource group
N x 66 bytes
(approximately 160 resources with CPU-E)
Area 6 Table configuration
Table Record bytes total

MENU 1 1024 1024
HELP 1 1024 1024
PASS 4 18 72
NAME 6 18 108
X25 32 54 1728
ILAN 16 62 992
MAC 32 74 2368
PROF 48 30 1440 (fixed)
BILL 20 70 1400
ELOG 200 82 16400
MEM 12 10 120 (fixed)
Total 26676
E
131 071
Memory configuration Page 3-5
3.7 Megapac VME with CPU-40 and 640 software
The effective configuration memory is limited to 128 Kbytes.
☞ With CPU-40 board,

the memory size reserved for area (2+3+4) is extended at MEM SIZE + 65536 bytes.
By default, MEM SIZE is 20 430, the size of area (2+3+4) is equal at 85966 bytes.
This setting lets you configure 604 descriptors and approximately 570 resources with CPU-40.
There is then still an area 6 of approximately 43 000 bytes for the Megapac tables.
The maximum setting for MEM SIZE is 63 448.

If the number of resources is insufficient, you must change MEM SIZE.
Area 1 2048 bytes (reserved) 0

Area 3 Link descriptor configuration.
(including TYPE=NULL descriptors)
65536
604 x 80 bytes = 48320 bytes (CPU-40 and 640 software)
+
Area 4 Resource configuration MEM SIZE
One block of 66 bytes for each resource or resource group
N x 66 bytes (approximately 570 resources)
Area 6 Table configuration
Table Record bytes total
MENU 1 1024 1024
HELP 1 1024 1024
PASS 4 18 72
NAME 6 18 108
X25 32 54 1728
ILAN 16 62 992
MAC 32 74 2368
PROF 48 30 1440 (fixed)
BILL 20 70 1400
ELOG 200 82 16400
MEM 12 10 120 (fixed)
Total 26676
131 071
E Page 3-6
4. Overview of link descriptors
4.1 Link descriptor assignment rules
Each physical port of the switch is assigned a link descriptor which represents the data link layer of the
OSI model. For a given port, the associated link descriptor constitutes the data structure defining:
• the name of the link used to identify it uniquely in the Megapac, for example: PSxx in which xx can be
the number n of the link in the set of links;
• the protocol used on that link: X.25, PPP, Frame Relay, Bridge, Router, etc;
• the number of logical resources supported by the link and which provide the virtual circuits for setting
up calls over the link;
• the various characteristics profiling the link.
The link descriptor must be defined in the order representing the hardware configuration of
☛ each Megapac and working from the top left position (nearest the CPU) to the bottom
right position.
In practice, for links of the same type - X.25, for example - and the same sub-type - XIO, for example -
the Megapac links the nth link descriptor to the nth physical port able to support the link type and sub-
type defined by the descriptor, in this example, the nth XIO port available.
There is no fixed relationship between an I/O descriptor as it appears in the configuration and the
physical position it occupies in the Megapac subrack. The address of each board which identifies its
position on the bus is determined by a jumper located on each board. The descriptor (software) is linked
to its module (hardware) by the definition of the SUB-TYPE/ parameter in one of the following four ways:
• SUB-TYPE/ GIO Addresses a module supporting the "generic interface"

GIS module, RNIS module for Megapac ESL and Megafrad
• SUB-TYPE/ XIO Addresses an XIO module
• SUB-TYPE/ SIO Addresses an SIO module
• SUB-TYPE/ SCC Addresses an communication controller module (68302 type)
• SUB-TYPE/ PRI Addresses a PRI-64 module allowing the connection of 1 or 2xT2 primary access
• SUB-TYPE/ VIO Addresses a virtual input-output descriptor
Note: SUB-TYPE/ XIO+SIO is proposed for Megapac E, Megabox and Megabox SL.
The combination XIO+SIO means that either an XIO-E or SIO-E card can be addressed when
the link is used in X25 protocol (TYPE/ X25).
For the other protocols (TYPE ≠ X25), the SUB-TYPE parameter must indicate which card is
being used (XIO, SIO, GIS, etc.).
In the following example, six physical boards have been defined. Although there is no relationship
between the descriptors and the I/O boards, the first descriptor assigned a set of TYPE/ and SUB-TYPE/
E
parameters is always mapped with the port of a similar SUB-TYPE/ having the lowest address on the
BUS, and so on.
Overview of link descriptors Page 4-1
The table below illustrates the principle applied when assigning link descriptors to physical ports.
The example is of a Megabox with:
• a CPU-EE board (with 2 XIO ports),
• an Ethernet board,
• an XIO board,
• an MIO board,
• an SIO board,
• and an GIS board.
Link descriptors Physical assignment Comments

BASE : >
EPCI : >
NMSC : >
PS01: TYPE/ X25 Port 1 on XIO interface of CPU-EE One X.25 link on XIO.
SUB-TYPE/ XIO
PS02: TYPE/ X25 Port 2 on XIO interface of CPU-EE One X.25 link on XIO.
SUB-TYPE/ XIO
ETHE: TYPE/ LAN Ethernet board One Ethernet port.
PS03: TYPE/ X25 Port 1 of XIO board One X.25 link on XIO.
SUB-TYPE/ XIO (lowest address)
PS04: TYPE/ X25 Port 2 on XIO board One X.25 link on XIO.
SUB-TYPE/ XIO
MIO1 to MIO6: TYPE/ TERM Port 1 to 6 of MIO board Six asynchronous ports (MIO)
SUB-TYPE/ SCC
PS05: TYPE/ TERM Port 1 of SIO board Two asynchronous ports (SIO).
(lowest address)
PS06: TYPE/ TERM Port 2 of SIO board Two asynchronous ports (SIO).
GIB1: TYPE/ X25 Port 1 of GIS board One X.25 link in a B channel on
GIS.
SUB-TYPE/ GIO (lowest address)
GIB2: TYPE/ X25 Port 2 of GIS board One X.25 link in a B channel on
GIS.
SUB-TYPE/ GIO
GISD: TYPE/ X25 Port 3 of GIS board One X.25 link in a D channel on
GIS.
SUB-TYPE/ GIO
Note:
SUB-TYPE/ GIO indicates that the descriptor addresses a board supporting the "Generic Interface".
• For GIS (S0) you must declare three descriptors (2B + D).
The first descriptor of a GIS board contains the interchanges with the board.
Overview of link descriptors
E Page 4-2
E Descriptors
Backplane
Boards
PS01
SUB-TYPE/ XIO
TYPE/ X25
PS02
SUB-TYPE/ XIO
TYPE/ X25
Configurations defined without
XIO CPU port 1
observing the physical constraints
ETHE of the modules installed will cause
TYPE/ LAN XIO CPU port 2
system failures.
This would be the case for a
PS03 Ethernet Megapac containing only two XIO
SUB-TYPE/ XIO ports installed for which you had
TYPE/ X25 defined three descriptors with the
TYPE/ X25 and SUB-TYPE/ XIO
PS04 XIO port 1 parameters.
SUB-TYPE/ XIO
TYPE/ X25 XIO port 2 The Megapac would terminate the
session, try to reset the system
and generate a bus access error.
MIO1 MIO port 1
MIO2
MIO port 2
MIO3
MIO4 MIO port 3
MIO5
MIO port 4
MIO6
SUB-TYPE/ SCC MIO port 5
TYPE/ TERM
MIO port 6
PS05
TYPE/ TERM
SIO port 1
SIO port 2
PS06
TYPE/ TERM
G1B1
SUB-TYPE/ GIO GIS canal B
TYPE/ X25
GIS canal B
G1B2 GIS canal D
SUB-TYPE/ GIO
TYPE/ X25
G1D1
SUB-TYPE/ GIO
TYPE/ X25
E
Figure 4-1 Relationship between descriptors and physical ports
Overview of link descriptors Page 4-3
4.2 Link descriptors - Identification and protocols supported
By default, two X.25 links are defined with the default names: PS01 and PS02.
All the other link descriptors are identified by the name: NAME/ XXXX and the type: TYPE/ NULL
indicating that they are not assigned.
You use the TYPE parameter of the link descriptor to determine the nature (protocol) of the link.
Parameter Range of Meaning and scope

Name settings
NAME 4-character name Link reference name.
(By default = PS01, Each link has a unique name within the Megapac configuration,
PS02, then XXXX) identifying it unambiguously.
TYPE By default = NULL Type of protocol supported on the link.
Each parameter setting is mutually exclusive and defines a specific
protocol from the extensive range of protocols supported by the
MEGAPAC.
EDLC DLC protocol (Data Link Control) used by IBM in SNA architecture
(System Network Architecture).
Protocol bearing the following layers :
- Physical layer : RLE Ethernet at 10 Mbps.
- First link sub-layer : MAC 802.3.
- Second link sub-layer : LLC2 802.2.
The MegaPAC acts as a cluster controller, with a connection to the host
in X25 or SDLC, on a PPP link, or on an Ethernet network.
DLCX Protocol allowing the implementation of X25 connections (1984)
by using the link layer of level 2 on a Token Ring local area
network at 4 or 16 Mbps.
Protocol bearing the following layers :
- Physical support : RLE Token Ring at 4 or 16 Mbps.
- First link sub-layer : MAC 802.5.
- Second link sub-layer : LLC2 802.2.
- Network layer : X.25.
ESIS not used in this software version
TIPX IPX protocol on Token-Ring.
IPX IPX protocol on Ethernet.
PPP WAN point-to-point protocol
E Page 4-4
E Parameter
TYPE
Name
ROUT
settings
Range of
Routing protocol
Meaning and scope
(continued) RIP on TCP/IP, RIP on IPX Netware.

TIP Protocol for setting up connections via an X.25 network between
TCP/IP (Transmission Control Protocol/Internet Protocol) networks in
a TOKEN RING environment.
XFRM This protocol offers an X.25 access point to Frame Relay with level 3 -
X.25
NFRM Basic WAN frame relay link protocol.
This protocol offers an X25, IP, IPX, SNA (BNN) access point to Frame
Relay.
It also offers a Frame Relay link "switching" mode.
SNMP Protocol dedicated to SNMP network supervisors.
The Megapac offers an "SNMP agent" function.
TLAN Protocol for setting up links between TOKEN RING and other
LANs in transparent bridge mode.
Protocol used in the following layers:
- Physical link: 4 or 16 Mbit/s TOKEN RING LAN.
- First link sublayer: MAC - IEEE 802.5.
- Transparent to the higher layers.
MAP 3174-1R, -3R or -53R cluster controller emulation protocol.
(PU 2) 1. The Megapac emulates a 3174-1R cluster controller.
In this mode, it shows only a PU (Physical Unit) to the host,
representing logical resource number zero on the MAP virtual link.
It concentrates a set of LU (Logical Units) connected to an MAP
logical resource numbered 2 to 256.
2. The Megapac node emulates a 3174-3R or - 53R cluster controller.
It can then be used to connect directly to a host connected to
TOKEN RING, or QLLC or SDLC system, various equipment
handled using the DLC, QLLC, SDLC and CLUS protocols.
E Page 4-5
E Parameter
TYPE
Name
DLC
settings
Range of Meaning and scope
DLC (Data Link Control) protocol used by IBM in the System

(continued) Network Architecture (SNA).
Protocol supporting the following layers:
- Physical link: 4 or 16 Mbit/s Token Ring LAN.
- First link sublayer: MAC 802.5.
- Second link sublayer: LLC2 802.2.
The Megapac emulates a cluster controller with connection to the host
in X.25 or SDLC mode by point-to-point link or Token-Ring
configuration.
NMS Protocol reserved for the NMS virtual links of the Megapac nodes
in the network management system (NMS).
See NMSC descriptor and NCxx resources.
CONS Protocol for setting up X.25 connections (1984) using the level 2
link layer of a 10 Mbit/s ETHERNET LAN.
- Physical: 10 Mbit/s Ethernet LAN.
- Network layer: X.25.
V25B V.25 bis protocol for setting up connections in switched circuit
mode via the PSTN or ISDN.
A virtual link provides the resources for controlling the transmission of
address information in V.25 bis mode - prefix CRN - to the PSTN.
The V25B link virtual descriptor also handles the V.25 bis incoming call
indication (prefix INC) from the PSTN.
With a dedicated ISDN adapter - GIS board - PRI64 board - links can
be set up in the same way as via the ISDN.
SCOP The SCOP descriptor is used for internal DATASCOPE function on the
others descriptors (X25, Ethernet, ...).
IP Protocol for setting up connections via an X.25 network between
TCP/IP (Transmission Control Protocol/Internet Protocol) networks in
the ETHERNET environment.
The Megapac emulates a gateway or IP router compliant with the RFC
877 standard.
E Page 4-6
E Parameter
TYPE
Name
SDLC
settings
SDLC (Synchronous Data Link Control) protocol.

(continued) Provides an IBM SDLC interface for connecting SNA hosts and X.25
native SNA controllers via an X.25 network. In other words, when the
controllers are incapable of handling data packets with the Q bit.
On the WAN side, the SDLC link descriptor replaces the X.25 link
descriptor.
MULT Pseudo-protocol for multiplexing and demultiplexing logical
channels.
From Server ---> Terminals, the data packets received over MULT
resource number 0 are broadcast to all other channels of the MULT
virtual link.
From Terminals ---> Server, the data packets received over MULT
resources numbered > 0 are concentrated onto resource number 0
associated with the server.
CLUS Protocol for emulating an IBM 3270 cluster controller connected
to VT100, VT220 and ANSI terminals.
The type 2 PU responds to logical channel number 0 of the CLUS
virtual link. Each type 2 LU is connected to a CLUS logical resource
numbered 2 to 256.
LAN Protocol for setting up links between ETHERNET LANs in
transparent bridge mode.
Protocol used in the following layers:
- Physical: 10 Mbit/s Ethernet LAN.
- Transparent to the top layers.
TERM Range of protocols for directly connecting a BSC bisynchronous
or asynchronous terminal.
The protocols supported are defined for each logical resource
associated with the link:
- PAD - X.3, X.28, X.29.
- VIDEOTEX protocol.
- Transparent BSC protocol - duplex, half-duplex.
- ENQ/ACK emulation for HP3000 and HP264X.
- 3270 BT emulation for VT100, IBM, 3278.
E Page 4-7
E Parameter
TYPE
Name
ILAN
settings
Protocol for setting up class 4 transport connections between an

(continued) ETHERNET LAN and a WAN (X.25 link descriptor), or vice versa.
The Megapac emulates an OSI gateway.
- Physical: 10 Mbit/s ETHERNET LAN.
- Network layer: Internet inactive - ISO 8473.
- Transport layer: Class 4 - ISO 8073/AD2.
QLLC QLLC (Qualified Logical Link Control) protocol.
Provides an IBM SDLC interface for connecting SNA hosts and X.25
native SNA controllers via an X.25 network, using the QLLC packet
transmission standard.
HDLC HDLC (High Level Data Link Control) protocol.
Provides an interface for the transparent transport of any bit-oriented
synchronous data stream via an X.25 network.
NULL Link not configured.
(By default: links numbered 3 and above)
X25 X.25 protocol.
(By default: first two Compliant with the X.25 LAP-B standard from the CCITT (1984 -
links) 1988).
LLC2 not used in this software version
Link descriptor parameters

Apart from its name and the type of protocol supported, each link descriptor is assigned a variable set of
parameters profiling the link.
The sections that follow describe the parameters for each link descriptor.
E Page 4-8
4.3 General information on logical resources
Each link descriptor is associated with a number of logical resources corresponding to the network layer
of the OSI model.
Each logical resource provides a virtual circuit for setting up a call over the link with which it is
associated. A logical resource defines:
• the name of the virtual circuit used to identify it within the Megapac (routing in the Megapac is based
on resource names);
• the virtual circuit type;
• the various characteristics that identify the resource uniquely.
Logical resource identification format

By default, each logical resource is identified by the first and last characters of the associated link
descriptor name, followed by two zeros and a resource number.
For descriptor PS01 comprising 16 resources, the resources are designated P100(0) to P100(15).
Parameter Range of Meaning and scope

Name settings
NAME 4-character name Logical resource reference name.
By default = P100(0) to
P100(15)
Other modifiable parameters depend on the type specified for the link descriptor.
E Page 4-9
E Page 4-10
5. System descriptors
5.1 BASE descriptor and resource BE00
The BASE descriptor defines the general operating attributes of the Megapac node. It represents the
first data structure in the Megapac node configuration. At any initial log-on, the "BASE" prompt is
displayed.
The BASE descriptor is also the structure towards which output from the other descriptors is directed.
A single logical resource named BE00 is assigned to the BASE descriptor. This is the logical resource
representing the virtual command port (VCP) via which Megapac configuration procedures are carried
out.
This is a virtual port. Any physical port can be used to access the VCP. The virtual command port can
also be accessed locally or remotely. It is identified by a name which, once entered, provides access to
the BASE descriptor and then to the Megapac configuration as a whole.
5.1.1 BASE descriptor parameter
Parameter Range of Meaning and Scope

Name Settings
REPORTS 4-character name Name of the logical resource representing the asynchronous
channel towards which Megapac diagnostic messages are
sent.
By default = EI00 The default resource EI00 is assigned to command ports A of
the CPU board.
SESSION 4-character name Name of the logical resource representing the asynchronous
channel towards which Megapac connect/disconnect
STATISTICS
statistical reports are sent.
By default = EI01 The resource EI01 is associated with the command ports B of
the CPU board.
BUFFER 5 to 1000 Minimum threshold accepted for buffers available.
No units When the number of buffers available falls below this
THRESHOLD
By default = 40 threshold, link level flow control is automatically implemented.
INITIAL PRESENTATION 0 to 255 When initially setting up a call in the Presentation mode -
TIMER Seconds "Menu 0" - the setting specifies the time delay within which
By default = 30 the connection to the logical resource must be set up.
If the caller fails to specify an address or a call destination
code before the timer runs out, the Presentation mode is
terminated.
System descriptors
E Page 5-1
E Parameter
Name
SECONDARY
Range of
Settings
0 to 255
Meaning and Scope
After setting up a call in the Presentation mode - "Menu 0" -

PRESENTATION TIMER Seconds then on disconnecting from the remote logical resource, this
setting specifies the maximum time allowed for the caller to
connect to another logical resource, if required, via the
By default = 30
"Menu 0" which is automatically displayed.
If the timer runs out, the presentation mode is terminated -
"Menu 0".
Note:
There is no connection and/or reconnection for the
Presentation mode - "Menu 0" - if this parameter is set to 0
and the previous INITIAL PRESENTATION TIMER/ parameter
is also 0.
INACTIVITY DETECT 0 to 30 Minimum time delay before disconnection due to inactivity
TIMER Minutes can occur.
By default = 15 Double the parameter setting is the maximum time after which
disconnection due to inactivity will occur.
This time delay applies only to logical resources set with
the IDLE option.
SEGMENT ACCOUNTING By default = NO Call charging criterion - see also the BILL table.
YES Billing is proportional to the number of 64 byte segments
exchanged.
NO Billing is proportional to the number of information packets
exchanged.
TERMINAL EMULATION 0 to 2048 Total number of terminal emulation buffers required.
BUFFERS No units This number depends on the protocols used.
By default = 0
TRANSPORT BUFFERS 0 to 2048 Total number of buffers allocated to the OSI transport
No units layer for transporting calls via the Megapac node.
By default = 0 This number depends on the protocols used.
Two buffers are required for each transport connection.
One buffer is also required for each asynchronous session
configured in the resources of TYPE TERM descriptors.
COUNTRY SETTINGS NONE (By default) Standard IP router operation (RIP 1)
SUBN IP router operation with forcing of a specific SUBNet mask
(that of the resource via which the RIP datagram arrived) -
Matisse operation -
System descriptors
E Page 5-2
E Parameter
Name
TELELOAD
Settings
By default =
Range of Meaning and Scope
Criterion for implementing the "Software download" function - in

ENABLED 160K conjunction with the network manager and the STM software.
The « software download » can be executed by a datagram transfer
under TCP/IP. We will use then, the TFTP utilitarian (Trivial FTP.) in
« picture » mode. The software download by TFTP requires the
configuration of a SNMP descriptor.
160K Enables the "Software download" function, reserving 160 K of RAM.
After using the LOAD<CR> command with the BASE descriptor, the
Megapac system software is downloaded from a preformatted ASCII
file to the battery backed RAM on the CPU board.
When executed after the RUN command, activates the downloaded
software and BOOTs the Megapac.
At this point, each time the system is reset, the downloaded software
is run in RAM, instead of the software stored in the CPU board's
EPROM.
YES (192K) Enables the "Software downloading" function, reserving 192 K in
RAM.
256K Enables the "Software downloading" function, reserving 256 K in
RAM.
NO Disables the "Software downloading" function.
Note: YES, 160K and 256K parameters enables the "Software downloading"
Megapac ESL function, reserving 256 K in RAM.
Megafrad NO parameter disables the "Software downloading" function.
CPU-60 board NO Disables the "Software downloading" function, and run the Software
in Flash memory.
YES Enables the "Software downloading" function, and allows to restart
with the ZONE 1 memory Software (BOOT command).
2ND Enables the "Software downloading" function, and allows to restart
3RD Enables the "Software downloading" function, and allows to restart
DEFAULT IF PROM By default = NO This parameter must be set to NO (reserved use)
System descriptors
E Page 5-3
5.1.2 Table of parameters for logical resource BE00 associated with BASE

Name Settings
NAME 4-character name Name of the logical resource for accessing the virtual
By default = BE00 command port.
OPTIONS By default = NONE Logical resource configuration options.

NONE No option for the logical resource is implemented.
IDLE Implements the function for disconnecting due to
inactivity.
A call to the VCP is then disconnected if inactivity is
detected for a time longer than the INACTIVITY DETECT
TIMER/ time delay specified at the BASE descriptor level.
GATE Implements the call presentation mode.
The VCP port caller is prompted to enter a password at
"Menu 0". This password, which must be enabled in the
PASS table, then controls access to the Megapac
configuration.
The IDLE and GATE option can be used together in the
form: IDLE+GATE.
RESOURCE PRIORITY (RP) 0 to 15 Level of access priority - RP - to the destination logical
No units resource associated with the VCP.
By default = 0 Only the source logical resources assigned a source access
priority level - CP - equal to or greater than RP can access
the resource.
If the GATE option described above is set, a caller assigned
a source priority level - CP - other than 1 in the PASS table
is authorized to set up the Megapac node.
Access rights
If the « GATE » option, described above, is set, a caller will
be assigned of the priority source level - CP- indicated in the
PASS table.
The value -CP- controls the access rights to the command
port.
Note: Access to the BE00 resource of the « BASE » configurator by a PAD-X25 connection
causes the configurator to send a modified PAD profile (X29 packet).
This profile modification sets the PAD parameters as follows:
• parameter 2 at 1 (ECHO=YES)
• parameter 4 at 1 (DELAY=1)
• parameter 15 at 0 (EDIT=NO)
System descriptors
E Page 5-4
5.1.3 Control of the command port access rights
When the « GATE » configuration is set at the level of the descriptor « BASE » resource (BE00):
• the caller receives the « prompt » of the Menu(0).
• The caller has to give his password.
• The caller is assigned of the priority level - CP - indicated in the PASS table for the selected
password.
According to the CP assigned to the caller, the access will be the following one:
CP Values VCP command port access rights

0, 2 à 15 All the commands are approved.
1 The VIEW, EXAM, STAT commands are approved.
The LIST command is approved except for the BILL and PASS tables.
The other commands are not allowed.
16, 18 à 31 All the commands are approved, except:
• The LIST and the DUMP from the PASSword table are rejected,
• The CONF, SET, MEN, INSE commands are rejected,
• The DELE command on the tables is rejected but approved in the STATistiques.
MENU table
Megapac MENU(0): Enter your password: ^J^M^G
PASS table
PASS(0): PASSWORD/ HELENE

NAME/ EI00 DRC MASK/ BE00
NAME/ BE00 CALL PRIORITY/ 18
etc ... OPTIONS/ GATE
CALL PRIORITY/ 2 MENU NUMBER/ 0
RESOURCE PRIORITY/ 2 BILLING/ D
etc ...
PASS(1): PASSWORD/ JEAN
link to BE00 DRC MASK/ BE00
EPCI descriptor BASE descriptor
CALL PRIORITY/ 2
MENU NUMBER/ 0
BILLING/ D
Figure 5-1 Limitation example of the VCP command port rights
In this example,
• The access to the « BASE » descriptor is reserved to the callers with CALL PRIORITY/ 2 at least.
• When a caller gives the « JEAN » PASSword he has access to the whole configuration commands
(CP = 2).
E
• When the caller gives the « HELENE » PASSword, his rights are limited (CP = 18).
System descriptors Page 5-5
5.2 EPCI descriptor and logical resources EI00
The EPCI descriptor is the second link descriptor used directly after the BASE descriptor. It represents
the two asynchronous links available on the CPU board's command port.
At the link level, it has no parameters which can be modified by the operator or displayable parameters.
The EPCI descriptor is exclusively linked to the two logical resources handling the asynchronous links A
and B of the command port:
• a first logical resource corresponds to CPU board command port A, named by default: EI00(0),
• a second logical resource corresponds to CPU board command port B, named by default: EI01(1).
These asynchronous ports provide local access to the Megapac set-up functions, and are used for
conveying Megapac diagnostic messages and statistics reports - see also the REPORTS and SESSION
STATISTICS parameters of the BASE descriptor.
The names identifying the associated logical resources, and their parameters, can be displayed and
modified in the same way as any other logical resource. The configuration parameters are the same as
for resources of a terminal type link: TERM. The disconnect character (DISC MODE) is by default « 11 »,
which correspond to ^K command.
System descriptors
E Page 5-6
5.3 NMSC descriptor and resources NC00
This descriptor represents the third data structure seen in Megapac node configuration, and appears after
the BASE and EPCI descriptors. In a network of Megapac nodes, the Network Management System
(NMS) uses management centers organized around PCs connected to the network via X.25 ports to
provide the following functions:
• Real time observation of network status: status of links and equipment, use of links and equipment,
operational statistics and call billing management,
• Network administration,
• Troubleshooting.
For this, each target Megapac node handled by the network management system must have a virtual
NMS link. The NMSC descriptor parameters for the NMS link are used to define its name and the
number of logical resources associated with it.
A single logical resource is created by default. It may be beneficial to have several, differentiated logical
resources. The logical resources of the NMS link are individually assigned event filters and activity
statistics profiles using the NMS software. This means that you can, via multiple logical resources,
access the observation data for each Megapac node differentiated by data type and with regard to their
frequency of reporting to the management center or centers.
The logical resources are individually identified by a name and associated, displayable and modifiable
configuration parameters.
Special features include:
• A number of NMS link logical resources can be set up with identical names to form a virtual circuit
group with mutual backup coverage. Consider, for example, three logical resources sharing the name
NC01: NC01(1), NC01(2) and NC01(3).
The virtual circuit set up between a network management center (NMC) and the logical
resource group NC01 will first choose the lowest numbered logical resource: NC01(1).
If that virtual circuit is disconnected - logical resource state = DISC - an attempt to set up a
new virtual circuit will then be directed in turn to the higher numbered logical resources:
NC01(2) then NC01(3).
The virtual circuit to logical resource NC01(1) is then re-established automatically when its
state reverts to DATA.
• Compared to other logical resources, the NMS link logical resource configuration parameters are
limited to two, as detailed below.
System descriptors
E Page 5-7
E
5.3.1 NMSC descriptor parameters
Parameter

Name Settings
NAME 4-character name NMS link reference name.
By default = NMSC
TYPE By default = NMS Only possible type attribute specifically identifying the
protocol specific to the Megapac node's NMS link.
CHANNELS 0 to 4096 Number of logical resources associated with the NMS
No units link.
By default = 1 A number of logical resources can be associated with the
NMS link to enable the Megapac node to be connected to
several management centers or to a single management
center via multiple virtual circuits.
POLL INTERVAL By default = 0 Time in seconds while the NMS descriptor is « passive »
(0 to 127) as a result of a BOOT, a RESTART, etc.
The timer guarantees a waiting time, before restoring a
dialogue with the management centers.
5.3.2 NC00 resource parameters

Name Settings
NAME 4-character name Name of each logical resource assigned to the NMS
By default = NC00 link.
DRC MASK 4-character name Name fully identifying the destination logical resource
By default = •••• on output from the Megapac, if the NMS link resource is
assigned to send calls to the management centers.
The default setting is applied if the NMS link resource is set
to receive only calls from the management centers.
CIRCUIT TYPE By default = Type of logical (channel) resource.
CALL + STAT The possible attributes for each logical resource associated
with the NMS link are as follows:
CALL The logical resource initializes the call to the resource
identified by the DRC MASK parameter described above, if
specified.
If not specified, the resource can only receive calls.
OUT The logical resource can only receive calls. The DRC
MASK parameter must be set to its default.
SVC Does not apply to an NMS resource.
PVC Is used with the test function (RESP mode).
System descriptors
E Page 5-8
E Parameter
Name
CIRCUIT TYPE STAT
Range of
Settings
Meaning and Scope
When connecting or disconnecting, a statistical report

(continued) is sent to the logical resource identified by the SESSION
STATISTICS/ parameter of the BASE descriptor.
This attribute can be used in conjunction with one of the
previous two attributes.
BUFFERS 1 to 240 Number of receive buffers assigned to the logical
By default = 2 resource.
The number of buffers reserved is 8 + the setting specified.
MODE By default = NONE Logical resource operating mode.
NONE Qualifies a standard NMS type logical resource.
A number of logical resources can be configured in this
way.
RESP Qualifies an NMS logical resource for which the
response time test function is enabled.
At a command from a management center, it runs a test
linked with an identified standard NMS type logical
resource, designed to determine the connection set-up time
and test execution time.
DATA Qualifies an NMS type logical resource behaving as a
traffic generator.
A test sequence is sent continuously via the logical
resource.
Several logical resources can be configured in this way.
CALL PRIORITY 0 to 15 Calling line priority (CP >= RP).
(CP) By default = 0
RESOURCE PRIORITY 0 to 15 Called line priority.
(RP) By default = 0
System descriptors
E Page 5-9
System descriptors
E Page 5-10
6. Routing by X.25 table
6.1 Definition of the X.25 table
The X.25 table contains a number of entries or records defining the relationship between network
address (or X.121 addresses in the X.25 protocol) and resource names. The size of the table is defined
in the MEM (MEMORY) table. Its default size is 32 records.
6.2 Creating the X.25 table
The various records in the X.25 table can be input from the system prompt. The X25 command can be
entered at any time to select the table. The CONF command can be used to introduce the parameters of
the record and the prompt displayed on screen specifies the record number and the current parameter.
The order of the records in the table has a significant effect on search procedures. The INSE and DELE
commands can be used to arrange the records as appropriate.
A record is configured as follows:
NAME/ 4 characters. This name should be equivalent to the NAME/ parameter of the
"resource" to which a call will be routed.
ADDRESS GROUP/ A number from 0 to 15.
This parameter is used to segment the records in the X.25 table. It is used in
conjunction with the parameter of a descriptor of the same name.
You can assign a setting to this field to restrict the correlation with the NAME/ field.
The correlation is limited to one "resource" with the same setting in the ADDRESS
GROUP/ parameter. In this way, you can partition a network into different
addressing domains.
The ADDRESS GROUP mechanism is used only by the Megapac after address
translation.
ADDRESS/ Alphanumeric field with up to 16 characters.
This address is compared with the called DTE number in the call request packet
incoming to a switch.
This field is also used to generate or modify the X.121 address of the call request
packet outgoing from the switch when the "resource" corresponds to the previous
two parameters.
USER DATA/ Alphanumeric field with up to 30 characters.
This parameter is used to assign facilities and call user data.
If more than the 30 characters of this field are required, the hyphen character (-) at
the end of the line will indicate that the field is continued in the next X.25 record.
Figure 6-1 Structure of the X.25 table
Routing by X.25 table
E Page 6-1
E
6.3 Using the X.25 table
The X.25 address of the called DTE in the call request packet is compared with the ADDRESS/
parameters of the records in the X.25 table (in sequence) to find a match. When a match is found, the
corresponding resource name (NAME/) is chosen. However, the ADDRESS/ field can include characters
which perform functions on the number concerned.
The use of these characters (or wildcards) to perform the substitute function is specified below:
∗ Replaces a character string of any length.
! Replaces a single character.
"n After a change of network domain, retains a number "n" of characters.
#n After a change of network domain, deletes a number "n" of characters.
T After a change of network domain, reconstructs a called DTE address.
T– After a change of network domain, reconstructs the calling DTE address.
The table below shows a few examples of the power and flexibility of the X.25 table with the use of wild
cards.
Record NAME/ ADDRESS GROUP/ ADDRESS/ Match

(n) N011 0 37219810 37219810
(n+1) N012 0 3721 3721
(n+2) N013 0 3721∗ 3721 followed by any digits.
(n+3) N014 0 3721!8!0 3721 followed by any digit, followed by 8,

followed by any digit, followed by 0.
(n+4) N021 0 3721!!8∗ 3721 followed by any two digits, followed by
an 8, followed by any digits.
(n+5) N031 0 ∗8! String of any digits with an 8 in the
penultimate character position.
(n+6) PSS1 1 2342∗ 2342 followed by any string of digits. The
call will be routed to a descriptor defined with
ADDRESS GROUP/1 and a "resource" name
NAME/PSS1.
(n+7) POUB 0 ∗ Any number read will be accepted. This
record is often the last in the X.25 table, and
is defined with an unfindable "resource"
name. This option is used when you need to
clear calls on which a match has not yet
been found.
Figure 6-2 Special characters in the ADDRESS field
E Page 6-2
E
6.4 Address translation
6.4.1 Translation of destination address "T"
When a call request packet is received by the Megapac switch, the destination address (called DTE) is
compared sequentially with the ADDRESS field of the records in the X.25 table.
When a match is found in the table, the presence of a letter T at the end of the address in the X.25
record triggers a special process.
Using the resource name found in the NAME field of the X.25 record, the MAC table is analyzed if
necessary (if Extend Call Management=OUT), to determine whether there is an output MAC program for
this resource (facilities and user data manipulating).
If there is no output MAC program, the X.25 table is analyzed again, from the beginning, to find a
matching resource name (NAME/).
The address specified in the ADDRESS/ field will be taken for the new destination.
Record NAME/ ADDR. GROUP/ ADDRESS/ USER DATA/
(n) P100 0 7777777777
(n+1) P200 0 2222222222
(n+2) P100 0 12345666
(n+3) P100 0 123456789T
Figure 6-3 Translation of the ADDRESS field
For a call request packet for which the called DTE address is 123456789, a first scan of the X.25 table
finds an address match in record (n+3), which generates a resource name P100.
When the address field ends with a T, the table is scanned again, but this time using the resource
name previously found as the search criterion.
A match is found in record (n) of NAME/ P100, and the called DTE address in the call request packet is
replaced by the address of this record (7777777777).
The call request packet is then sent to a logical resource named P100, with the new destination address.
☛ All scans of the X.25 table start at the beginning of the table.
E Page 6-3
6.4.2 Address translation and "ADDRESS GROUP"
If the main link of resource P100 fails, another route via another link descriptor defined with resources of
the same name (P100), but with a lower priority, can be used.
For translation to an address dependent on the route used, the ADDRESS GROUP/ parameters of the
link descriptor and of the X.25 record must be used.
The first destination "resource" is always determined irrespective of the address translation request.
(ADDRESS GROUP/ is meaningless when first scanning the X.25 table).
When the destination "resource" has been found in the X.25 table, Megapac selects an available
"resource" in accordance with the RP - CP rules, and stores the ADDRESS GROUP of the link descriptor
supporting this "resource".
The X.25 table is scanned again, this time looking for a match between "resource" NAME and the
"descriptor" ADDRESS GROUP. The record found can be used to generate the call request packet with
the content of the ADDRESS/ field.

(n) P100 0 7777777777
(n+1) P200 0 2222222222
(n+2) P100 1 12345666
(n+3) P100 0 123456789T
Figure 6-4 Translation with "T" and the ADDRESS GROUP field
• In the example, on resource P200 (CP=2) of the PS02 link, a call request packet requests
"123456789".
• Record (n+3) indicates a routing over a resource P100 with address translation.
• Megapac selects resource P100 (RP=2) of the PS03 link, in which ADDRESS GROUP = 0. If this link
can be used, record (n) of the X.25 table indicates a routing over a resource P100 with AG=0, and the
destination address is " 7777777777".
• If the PS03 link is unavailable, Megapac selects resource P100 (RP=1) of the PS04 link, in which
ADDRESSGROUP = 1. If this link can be used, record (n+2) of the X.25 table indicates a routing
over a resource P100 with AG=1, and the destination address is "12345666" .
Call request packet Normal routing

called DTE 123456789 PS03 call 7777777777
P100 RP=2
X25
PS02 MEGAPAC AG=0
P200 CP=2 X25 node
Back up routing
PS04 P100 RP=1 call 12345666
X25
AG=1
Figure 6-5 Routing over a back-up link
E Page 6-4
6.4.3 Using copy (") and skip (#) characters
There are two characters which let you manipulate destination addresses with even greater flexibility.
With them, you can copy certain parts of the original address to the new call request packet, while other
parts are generated by the Megapac software.
• The "#" (hash) character followed by a single digit can be used to skip the specified number of
characters in the original address.
• The "″" character (double apostrophe) followed by a single digit can be used to copy the specified
number of characters from the original address.
The digit following the special character is a hexadecimal digit, indicating the number of characters to be
copied or skipped (up to 15).

(n) P100 0 2342″4#5″227
(n+1) P100 0 12345678900T
Figure 6-6 Use of the copy (″) and skip (#) characters
For a call request packet for which the called DTE address is 12345678900, the Megapac finds a match
in record "n+1" of the X.25 table, which generates a resource name P100.
The address field finishes with a T, so the table is scanned again, but this time taking the resource name
as the search key.
A match is found in record (n) of NAME/ P100.
The called DTE address in the call request packet is constructed as follows:
• take 2342,
• then copy the first 4 digits of the original address,
• then skip 5 characters of the original address,
• then copy the last 2 characters of the original address,
• then add 27.
The final address is then 2342 1234 00 27.
E Page 6-5
E
6.4.4 Inserting the source address "-"
When scanning the X.25 table to route a call, if the selected record includes a "-" (hyphen) character
immediately after the address, the X.25 table is scanned again, this time looking for a match on the
resource name (NAME/) of the incoming channel.
The content of the address field associated with the corresponding NAME/ field is then inserted as the
source address (calling DTE address) in the outgoing call request packet.

(n) P200 0 222123456
(n+1) P100 0 123456789–
(n+2) ∗∗∗∗ 0 23421200012500
Figure 6-7 Inserting the source address
In the above example, imagine that the call request packet with destination address 123456789 is
received over a "resource" with the name P200.
The X.25 table search finds record (n+1), but the – character after the number indicates insertion of a
calling address.
The X.25 table is scanned again, this time using the incoming "resource" name (P200) as the search
criterion.
A match is found in record (n) and a number 222123456 is inserted in the source address of the outgoing
call request packet.
The call request packet is then forwarded over a "resource" named P100, with the source address
222123456 and destination address 123456789.
Note 1
When scanning the X.25 table to find the source name (in the above example, NAME/ P200), the
ADDRESS GROUP/ field must match that of the outgoing link descriptor. In this way, the source
address inserted can be closely matched to the selected route.
E Page 6-6
E
Note 2
It is important to remember that for "resources" named ″ ″ ″ ″ or ″∗∗∗, the name of the "resource"
referenced is the last name spelt out in the list of incoming "resources".
In the above example, if the call is received over "resource" 4 of the incoming link (see below), the
corresponding name in the X.25 table is PADA.
The match is found in record n+2 (containing the wildcards ∗∗∗∗), which is translated into generation of
the source address 23421200012500.
resource number NAME/

0 P200
1 PADA
2 ″ ″ ″ ″
3 ″ ″ ″ ″
4 ″ ″ ″ ″
Figure 6-8 Use of the "ditto" wildcard in logical resources
Think of record n+2 as a net for catching all logical resource names (NAME/) without a match in the X.25
table. This technique can also be used to allocate a single source address to all call request packets
received.
The SKIP and COPY functions described above can be applied to the source address (calling DTE) to
construct a source address in which certain parts of the original address (for example, the supplementary
address) are retained.
Where appropriate, in cases where the translation of both addresses (source and destination) is required,
the address field in the X.25 record can contain T–.
6.5 Manipulating source addresses
Verification, insertion or substitution of the source address (calling DTE) cannot be specified in the
OPTIONS/ parameter of the X25 link descriptor (VRFY, INSE, SUBS Options).
The MAC table with the CAD function "Calling DTE address", and the TLAT option "Call request packet
reconstruction" may be used.
E Page 6-7
E
6.6 Manipulating user data
Use of the USER DATA/ field

Facilities and call User Data are inserted in a call request packet by specifying the USER DATA/ field of
a record in the X.25 table.
This information can be generated
• automatically if the user specifies a particular destination "resource" using the presentation mode. In
this case, the Megapac is responsible for generating the call request packet, or
• specifically by the use of the letter T in the ADDRESS/ field. In this case, the Megapac is responsible
for routing a call request packet generated elsewhere.
The USER DATA/ field can contain any number of call user data or facility bytes.
When the X.25 record cannot contain all of the information, the – (hyphen) character can be added to the
end of each record to indicate that the field concerned extends to the next record.
The user data can be entered in hexadecimal, or in hexadecimal followed by a character text string. A
character string must be prefixed with an ' (apostrophe) indicating that the ensuing characters must be
treated as ASCII. You cannot redefine hexadecimal characters after text characters.
In the example below, a match is found for the first four digits of an X.25 destination address. To be able
to insert the USER DATA/ field (assuming that the call request packet does not have one), the
ADDRESS/ field of the X.25 record includes a letter T to trigger address translation. The Megapac scans
the X.25 table again and looks for a matching logical resource name (NAME/). When it finds a match (in
this case, in the same record), the content of the USER DATA/ field is used to modify the call request
%
packet. The routing data is unchanged.
When the call request packet already has a facilities field or a call user data field,
despite the match in the table and the existence of the letter T, the call request packet
is routed unaltered.
The facilities field must be specified in hexadecimal in brackets and before the call user data field. No
space is allowed in the specification of these fields. The length of each field is computed automatically
and inserted in the call request packet with the fields concerned.

(n) NODA 0 2342*T (01020304050607080910111213–
(n+1) NODA 0 141516)4890123456789001030–
(n+2) NODA 0 ‘abcdefghijklmnopqrstuvwxyz
Figure 6-9 Manipulating the call user data field
The new call request packet will contain:

1. the original X.25 address (beginning 2342),
2. the "length of the facilities field" is 10 hex (16 decimal),
3. the "facilities" field in brackets,
4. the "call user data" field containing hexadecimal data 48 90 12 34, etc, followed by the text abc...,
converted into hexadecimal.
E Page 6-8
6.7 Routing algorithm using the X.25 table
State 0
Incoming call request packet

" Called DTE" address
extracted
"Called DTE address" YES

A
length = 0?
NO
Match with X.121 YES

address in B
X.25 table?
NO
Failure
Return to state 0
Figure 6-10 Routing algorithm with the X.25 table
E Page 6-9
Routed directly
over DRC
First link
YES descriptor
Search priority > 0?
NO
First logical
resource
Search priority
decremented
Search priority: RP
of this resource?
NO
YES
Next logical
resource
Logical resource name
in packet: name of
NO this resource?
YES
NO YES
Next
link descriptor? Resource name present
NO in X.25 table?
NO
YES YES
Failed
Return to state 0
Last
logical resource? Logical resource
NO available?
YES
Call request packet

sent out over this
logical resource
E Page 6-10
Corresponding
resource name
extracted
Search priority
CP of calling DTE
First link
YES descriptor
Search priority > 0?
NO
First logical
resource
Search priority
decremented
Search priority: RP
NO of this resource?
Next logical YES

resource
Corresponding resource
name: name of this
NO resource?
NO
NO YES
Next link
descriptor? Logical resource
available?
NO
NO
Failed YES YES

Return to state 0
Last
logical resource?
Call request packet
sent out over this
logical resource
E Page 6-11
E Page 6-12
7. Routing by MAC table
For links requiring a special routing, the MAC table is activated by the link descriptor's EXTENDED CALL
MANAGEMENT/ parameter (IN, OUT or V25B).
For other links, the MAC table is used by default.
Each MAC record can be associated with one or more link descriptors.
The association is declared in the NAME field of the MAC record. This field fully or partially identifies a
link.
After a BOOT or REST command has been used, each MAC program is linked with the link descriptors
concerned, and then executed.
7.1 MAC file size
The size of the MAC file is set using the MEM command.
The file size is specified in the "NUMBER OF MACRO FILE RECORDS" record of the MEM table. By
default, the MAC file is set to 32 records.
The MAC table is accessed by the MAC then CONF commands.
7.2 Structure of a MAC record
Parameter Settings Meaning

NAME 4 characters Identifies the link descriptor(s) concerned.
or
Identifies the logical resource(s) concerned.
^DRC. Used exclusively with the LIST function.
The wildcard character "∗" can be used.
FUNCTION see following pages Specifies a particular operation.
OPTIONS see following pages Specifies an option for processing the function specified.
SELECTOR 0 to 32 characters According to the function selected, the specification of a line can be
continued in subsequent records. For this, enter a hyphen (-) in the
last character position of the line to be continued.
GENERATOR 0 to 32 characters According to the function selected, the specification of a line can be
continued in subsequent records. For this, enter a hyphen (-) in the
last character position of the line to be continued.
Modifications made to the MAC table necessitate a switch reset (BOOT command), or require
☛ « RESTART » commands to be implemented for the descriptors of which the routing has been
modified.
Routing by MAC table
E Page 7-1
E
7.3 Input MAC program
Apart from certain particular functions, each function (specified in the FUNCTION field of a MAC record)
must be located between the IBEG and IEND delimiters respectively marking the beginning and end of
an input MAC program.
In the OPTIONS field of an MAC record, the setting reinforces or modifies the action performed by the
associated function.
7.3.1 "FUNCTIONS" field of an input MAC program
A detailed description of each "FUNCTION" is included in the following section(s).

For each link "descriptor" in which a MAC function is available, the function is explained.
The table below gives an idea of the functionalities of the MAC table.
The functions are listed in the order in which they are displayed on screen ("?" command).
FUNCTIONS Brief description Position with respect

to
(input MAC program)
IBEG ... IEND
DHCP Used to activate the "DHCP Relay" function in a TCP/IP network. between the delimiters
TIME Output MAC program for V25B descriptor.
TIME Used to define a time field or period when the Megapac is configured outside
in an IPX Router environment (ROUT descriptor).
BAR Used to filter IP and IPX layer datagrams in an IP, IPX router immediately before
environment (ROUT descriptor).
ADD Used to define "MAC address", "IP address" combinations in a TCP/IP immediately after
environment (IP and TIP descriptors).
NMVT Use reserved (IBM Netview).
ROUT Used to define one or more static routes in an RIP IP and/or IPX
router environment (ROUT descriptors).
NDI Used to filter an ISDN call according to the number received. outside
TAB Modification of the "default" ASCII/EBCDIC conversion table used in outside
3270 emulation.
SYNC The presence of a SYNC function indicates the use of a BSC protocol, outside
in Full Duplex communication.
MASK Used to define a subnet mask for the IP and TIP descriptors thereby immediately after
reducing the number of records in the ARP routing table.
MASK Used to define a subnet mask and route datagrams taking account of between the delimiters
the subnet mask (IP and TIP descriptors).
MASK Used to specify a MASK for the PAD parameters from an X.29 packet. outside
LIST Used to specify a series of destination resources. without delimiters at the
A call is routed to the destination resource with "^" as its first beginning of the table
character (example ^LSA).
A series of routes with the NAME ^LSA must be declared at the
beginning of the MAC table.
XID Used to define an identity check in accordance with the X.32 protocol outside
E
(X.25 descriptor).
XID Used to define "XID" dialogue in a Token Ring - SNA environment outside
(DLC descriptor).
Routing by MAC table Page 7-2
EFUNCTION
(continued)
Brief description
(input MAC program)
Position with respect
to
IBEG ... IEND
PU In a Token Ring environment, a PU record is used to specify without delimiters at the
operation of the ring (UTP/STP, 4 or 16 Mbit/s). beginning of the table
PU Specifies type 2 PU operation for a resource (0) of a CLUS descriptor without delimiters at the
(cluster controller function). beginning of the table
PU Used to associated an IP address with a record in the NAME table in without delimiters at the
the PAD Telnet functions (IP, TIP descriptors). beginning of the table
PU Used to define a station address and an XID for resource (0) of an without delimiters at the
MAP descriptor. beginning of the table
OEND Output MAC program.
OBEG Output MAC program.
IEND Input MAC program end delimiter.
IBEG Input MAC program beginning delimiter.
EOF Output MAC program.
DATA Output MAC program.
DATA General "SNMP" supervision information for a Megapac node. without delimiters at the
beginning of the table
MARK Output MAC program.
POSN Output MAC program.
COPY Output MAC program.
DELE Output MAC program.
INSE Output MAC program.
DPR Selection on an IP protocol and one or more destination addresses between the delimiters
CPR Selection on an IP protocol and one or more source addresses between the delimiters
FAC Selection on "facilities" data. between the delimiters
ELSE Used to define other routing. between the delimiters
CUD Selection on call user data. between the delimiters
DAD Selection on a called address, on a destination address. between the delimiters
CAD Selection on a calling address, on a source address. between the delimiters
NOP Used to reserve a record for subsequent use. between the delimiters
E Page 7-3
7.3.2 "OPTIONS" field of an input MAC program
OPTIONS
WIPX When the Megapac is configured in the IPX router environment:
the TIME function and WIPX option are used to filter the Watchdog IPX (Spoofing) messages.
SAP When the Megapac is configured in the IPX router environment:
the TIME function and SAP option are used to filter the SAP messages,
the ROUT function and SAP option are used to define an SAP static route.
TLAT Accesses the X.25 table.
Reconstructs a field in the outgoing call request packet.
REJ Transmits a clearing packet with predefined "cause/diagnostic".
Filters IP datagrams.
TCAL Establishes a class 2 or 3 OSI transport connection.
ISO Sets up a class 3 OSI transport connection to implement the reassignment on fault procedure.
This enables a restart after disconnection at "network" level.
Y13 ISO+Y13: this option adds information to the TPDU_CR (Connection Request) specifying insertion
of the calling address on reconstruction of the X.25 level 3 call request packet at the destination
Megapac output.
CAD Completes the "Calling DTE address" field of a call request packet.
THRU Assigns a default throughput class to all virtual circuits using the incoming link. This is the
maximum throughput class allowed in each direction of transmission.
TALK Indicates use of the presentation service.
TALK Indicates a Terminal emulation type or a TELNET emulation via the NAME table.
BILL The call is subject to billing.
You can jointly specify TCAL and BILL. In this case, the virtual circuit underlying the OSI
transport connection is subject to billing.
DISC Output MAC program.
EXPE Sets up a class 2 or 3 OSI transport connection with use of the "expedited data" service.
JUMP Performs a jump conditioned by another input MAC record.
COPY Transfers all or some of the content of a field (calling DTE address, called DTE address, facilities,
call user data), in an incoming call request packet, into the buffer associated with the X.121
address field of the X.25 file.
FLAG Reserved for future use.
TRAP Reserved for future use.
NOT Used to reverse the role of the BAR function.
NONE No option can modify the action performed by the associated function.
E Page 7-4
7.3.3 "SELECTOR" field of an input MAC program
SELECTOR
0 to 32 As a rule, the content of the SELECTOR field of an input MAC record validates the content of the
characters relevant field in the call request packet.
According to the function selected, the specification of a line can be continued in subsequent
records. For this, enter a hyphen (-) in the last character position of the line to be continued.
7.3.4 "GENERATOR" field of an input MAC program
GENERATOR
0 to 32 As a rule, the content of the GENERATOR field of an input MAC record represents the destination
characters logic resource on which routing is to be performed.
There are many exceptions:
• with the CAD option, the GENERATOR field contains the name of an originating resource
associated with a calling address.
• with the THRU option, the GENERATOR field contains the default throughput class assigned
to the incoming link.
• with the COPY option, the GENERATOR field contains a string containing special characters
"+", "#", and/or """.
This character string can be prefixed by the name of an outgoing resources which must be
followed by a comma.
• with the TALK option, indicating an emulation type (Terminal, Telnet), the GENERATOR field
contains a string representing an entry in the "NAME" table.
• etc. ...
E Page 7-5
E
7.3.5 Input MAC algorithm
Page A
Incoming call
request packet
Extended Call
Management IN?
Does NAME field YES
X.25 ROUTING
contain the name
of an incoming link?
YES
X.25 ROUTING
YES IBEG
FUNCTION
field? Next MAC
Start of input record?
MAC prog.
YES
X.25 ROUTING
CAD
NO FUNCTION CONTINUE
field?
"Current" record
DAD disregarded
NO FUNCTION
field?
DISREGARD
PROCESS (page c)
CUD YES
NO
FUNCTION
field?
FAC
NO FUNCTION
field?
Does SELECTOR field

IEND validate appropriate
YES FUNCTION NO
field of call request
field? packet?
. End of input MAC program.

. Input program linked to link
descriptor concerned.
. Preparation of each outgoing call request
packet.
. X.25 routing.
Figure 7-1 Input MAC routing algorithm
E Page 7-6
E Page B
(continued)
Clear indication packet

received after recognition of
a record (source)
Does next record

include an "ELSE"
FUNCTION field? Does SELECTOR
field validate
YES "cause/diagnostic"
DISREGARD field of clear
indication packet?
YES DISREGARD
(page A)
NONE OPTION
field?
NO
TLAT OPTION
field?
YES
Content of outgoing
call request packet
Field concerned stays unchanged
reconstructed in
outgoing call request
packet
CONTINUE
Does SELECTOR field (page A)
of source record
validate appropriate
field of outgoing call
request packet?
YES
PROCESS DISREGARD
(page C) (page A)
E Page 7-7
E Page C
(continued)
PROCESS
"Current" MAC
record serviced CONTINUED
(page A)
NONE Content of outgoing call

OPTION YES
request packet unchanged
field?
CAD Characters inserted in

YES "calling DTE address" field
OPTION of outgoing call request
field? packet
REJ Clear indication packet

YES
OPTION sent with predefined
field? "cause/diagnostic" codes
TCAL Class 4 OSI transport

YES connection on INTERNET
OPTION
network layer inactive
field?
- ISO 8473 -
TLAT Field concerned

OPTION YES reconstructed in
field? outgoing call request
packet
THRU Default throughput class

OPTION YES assigned to incoming
field? link
TALK
OPTION YES Presentation mode
field?
EXPE Class 2 or 3 OSI transport
OPTION YES connection with use of
field? "expedited data" service
ISO Class 3 OSI transport

OPTION YES
connection with use of
field? reassign on fault procedure
BILL Each virtual circuit

OPTION YES
using the incoming link
field? is subject to charging
All or none of field

COPY belonging to incoming call
YES request packet transferred
OPTION
into buffer associated
field? with X.121 address field of
X.25 table
JUMP
NO Content of outgoing
OPTION
call request packet
BRC field? unchanged
(page D)
E Page 7-8
E Page D
(continued)
BRC
Connection to next
record with NAME
field containing
a reference
Does GENERATOR
field contain a
reference?
YES
Is call request packet
validated by SELECTOR field?
Connection to input
DISREGARD YES MAC record associated
(page A) with reference
Does GENERATOR YES Is call request packet validated

field contain
by first reference of SELECTOR
two references?
field?
Connection to input
MAC record associated
YES with first reference
Does GENERATOR
field contain
three references? Connection to input
YES with second reference
Is call request packet
DISREGARD validated by first
(page A) reference of selector field?
YES Connection to input

with first reference
Is content of SELECTOR
field greater than
corresponding field in
call request packet?
Connection to input
YES
with second reference
Connection to input
with third reference
E Page 7-9
E
7.4 Output MAC program
Each function (specified in the FUNCTION field) must be located between the OBEG and OEND
delimiters, respectively marking the beginning and end of an output MAC program.
The OPTIONS field of an output MAC record is not used.
Notes:
• Before executing an output MAC record, "T" or "T-" must be specified in the "ADDRESS" field of the
corresponding record in the X.25 table.
• When processing various types of facility (X.25 - "OSI" DTE), the MAC software keeps a record of
insertions, deletions and/or copies performed previously.
7.4.1 "FUNCTIONS" field of an output MAC program
A detailed description of each "FUNCTION" is included in the following section(s).

For each link "descriptor" in which a MAC function is available, the function is explained.
The table below gives an idea of the functionalities of the MAC table.
The functions are listed in the order in which they are displayed on screen ("?" command).
FUNCTION Brief description Position with

(output MAC program) respect to
IBEG ... IEND
DHCP Input MAC program
TIME allows to control the duration of a call when the mode of this call is the between the
V25bis mode. A virtual « V25B » descriptor must be configured. delimiters
BAR Input MAC program.
ADD Input MAC program.
NMVT Reserved use.
ROUT Input MAC program.
NDI Input MAC program.
TAB Input MAC program.
SYNC Input MAC program.
MASK Input MAC program.
LIST Input MAC program.
XID Input MAC program.
E Page 7-10
EFUNCTION
(continued)
Brief description
(output MAC program)
Position with
respect to
IBEG ... IEND
PU Input MAC program.
OEND Output MAC program end limit.
OBEG Output MAC program start limit.
IEND Input MAC program.
IBEG Input MAC program.
EOF Terminates execution of the output MAC program, bearing in mind that between the
only facilities are concerned. Users Data are deleted. delimiters
DATA Stores information in the "user data" field of an incoming call request between the
packet. delimiters
Terminates execution of the output MAC program.
DATA Transfers a telephone number to the V.25 bis link virtual descriptor. between the
delimiters
MARK Sets a service type marker in the "facilities" field of an incoming call between the
request packet. delimiters
POSN Sets the MAC logic subsystem at the start of one of the following service between the
types: "X.25" or "OSI DTE", in the "facilities" field of a call request packet. delimiters
COPY Copies one or more codes and their associated parameters into the between the
"facilities" field of an incoming call request packet. delimiters
DELE Deletes a code and its associated parameters from the "facilities" field of between the
an incoming call request packet. delimiters
INSE Inserts a code and its associated parameters in the "facilities" field of an between the
incoming call request packet. delimiters
DPR Input MAC program.
CPR Input MAC program.
FAC Selection on "facilities" data. between the
delimiters
ELSE Input MAC program.
CUD Reconstructs (or does not reconstruct) the "Call user data" field of a call between the
request packet. Transfers the resulting telephone number to the V.25 bis delimiters
link virtual descriptor.
DAD Reconstructs (or does not reconstruct) the "Called DTE address" field of a between the
call request packet. Transfers the resulting telephone number to the delimiters
V.25 bis link virtual descriptor.
CAD Reconstructs (or does not reconstruct) the "Calling DTE address" field of a between the
call request packet. Transfers the resulting telephone number to the delimiters
V.25 bis virtual descriptor.
CAD Allows to authorize or forbid to a caller (calling ETTD address) the access between the
to an output resource. delimiters
NOP Used to reserve a record for subsequent use. between the
delimiters
E Page 7-11
7.4.2 "OPTIONS" field of an output MAC program
OPTIONS
WIPX Input MAC program.
SAP Input MAC program.
TLAT Input MAC program.
REJ Input MAC program.
TCAL Input MAC program.
ISO Input MAC program.
Y13 Input MAC program.
CAD Input MAC program.
THRU Input MAC program.
TALK Input MAC program.
BILL Input MAC program.
DISC Output MAC program (see V25B descriptor).
EXPE Input MAC program.
JUMP Input MAC program.
COPY Input MAC program.
FLAG Reserved for future use.
TRAP Reserved for future use.
NOT Input MAC program.
NONE No option can modify the action performed by the associated function.
E Page 7-12
7.4.3 "SELECTOR" field of an output MAC program
SELECTOR
0 to 32 As a rule, the content of the SELECTOR field conditions execution or non-execution of the
characters function concerned.
7.4.4 "GENERATOR" field of an output MAC program
GENERATOR
0 to 32 As a rule, the content of the GENERATOR field is:
characters • Facility code.
• Facility parameter(s).
• Facility type marker.
• Telephone number (V.25 bis link).
• Syntax for reconstructing the field of the call request packet, to obtain a telephone number
(V.25 bis link).
E Page 7-13
E
7.4.5 Output MAC algorithm
Page A
Outgoing call
request packet
Extended
Call Management X.25 routing
OUT? Transparently copies F and
YES
UD from incoming call
request packet.
Does NAME field
contain name of
outgoing link?
X.25 routing
Deletes F and UD found in
incoming call request
packet.
YES
OBEG
FUNCTION
field?
YES
Start of output
MAC prog.
CONT 1 F = Facilities
(page B) UD = User Data
Figure 7-2 Output MAC routing algorithm
E Page 7-14
E Page B
(continued)
CONT 1
NEXT
Positioning and
marking functions
POSN
FUNCTION YES Are conditions in SELECTOR
field? field satisfied?
DISREGARD
YES Does GENERATOR

field contain 00?
Incoming call request

"Current" packet
YES -Positions MAC logic at
record
start of X.25 F
disregarded
-Masks associated with
X.25 F codes reset to 0.
NEXT
Does GENERATOR
field contain OF?
YES Next
record? Incoming call request
DISREGARD
YES packet
-Positions MAC logic at
start of OSI DTE F
-Masks associated with
OSI DTE F codes reset
to 0.
X.25 routing
incoming call request
MARK packet.
FUNCTION YES
field? Are SELECTOR field
conditions satisfied?
DISREGARD
YES Outgoing call request
packet
-Stores second byte of
Does GENERATOR YES
marker 0000, marking
field contain start of X.25 F
00? -All corresponding masks
CONT 2 reset to 0.
(page C)
Outgoing call request
packet
-Stores second byte of
YES marker 000F, marking
Does GENERATOR
start of OSI DTE F
field contain
-All corresponding masks
OF? reset to 0.
F = Facilities
UD = User Data
DISREGARD
E Page 7-15
E Page C
(continued)
CONT 2
F insertion, deletion
and copy functions NEXT
INSE
FUNCTION YES
Are conditions in SELECTOR
field? field satisfied?
YES
DISREGARD
In outgoing call request packet,
is corresponding marker already
stored there?
YES
Is mask associated DISREGARD
with F code already
set to 1? Outgoing call request packet
NO -Inserts corresponding F code and
DISREGARD parameters.
-Mask associated with F inserted
DELAY already set to 1.
YES
FUNCTION
field? Are conditions in SELECTOR
field satisfied?
YES
DISREGARD In outgoing call request packet,
stored there?
YES DISREGARD
Is mask associated
with F code already
set to 1? Incoming call request packet
NO -Deletes corresponding F code and
DISREGARD parameters.
COPY -Mask associated with deleted F code
FUNCTION YES already set to 1.
field? In SELECTOR field, are
YES
DISREGARD In outgoing call request packet,
stored?
YES DISREGARD
Does GENERATOR
field contain 20 H Output call request packet
(space)? -In F field concerned, copies each
YES code (if mark set to 0) and
CONT 3 parameters.
(page D) -Mask associated with each F code
copied then set to 1.
Does GENERATOR field Outgoing call request packet

contain 2A H (*)? YES -In F field concerned, copies each
code (if mark set to 0) and
parameters.
-Mask associated with each F code
Outgoing call request packet
Does GENERATOR field
contain a valid F YES -In F field concerned, copies code
specified (if mark set to 0) and
code? parameters.
-Mask associated with each F code
F = Facilities
UD = User Data DISREGARD
E Page 7-16
E Page D
(continued)
CONT 3
Output MAC prog.

termination and UD
insertion functions
EOF
FUNCTION YES
In SELECTOR field, are
field? conditions satisfied?
YES Does GENERATOR

field contain
DISREGARD 20 H (space)?
YES
DISREGARD -Constructs/reconstructs F
field.
-Inserts information in
"F length" field.
DATA
FUNCTION YES
field? In SELECTOR field, are
-Constructs/reconstructs F
field.
YES -Inserts information in
"F length" field.
-Inserts information in UD
field.
X.25 routing
OEND X.121 address to which
YES outgoing call request packet
FUNCTION
is routed must have T-.
field?
Otherwise, F and UD cannot be
handled by output MAC program.
X.25 routing
incoming call request packet.
F = Facilities
UD = User Data
E Page 7-17
E Page 7-18
8. Other Tables
8.1 PASS table
A logical resource can be associated with an input password control ("source resource" with PASS
option) or an output password control ("destination resource" with GATE option).
When the PASS option is specified, the caller must enter the password, when prompted, after the
menu (0) is displayed.
The content of the PASSWORD field is then checked against the records in the PASS file.
In the DRC MASK field, all or part of a destination resource can be identified. This identification will be
used for routing.
The content of the CALL PRIORITY (CP) field dictates the call priority assigned to the calling DTE. For
routing to take place, the destination logical resource must have a resource priority (RP) less than or
equal to the calling DTE's call priority.
The MENU NUMBER field contains the number of the menu displayed, associated with the calling DTE's
logical resource.
The BILLING field determines whether a record is to be stored in the "charging" file at the end of the
session.
The above procedure remains valid for the GATE option.
However, the password check is applied on output, in other words, when the calling DTE is connected to
the "destination resource" (which has the GATE option).
The PASS file size is established by the MEM command.

The file size is specified in the "Number of passwords" record of the MEM table.
The PASS command provides manual access to the PASS file.
PARAMETERS SETTINGS MEANING

PASSWORD 8 characters maximum Password, to be entered by the calling DTE.
DRC MASK 4 characters Fully or partly identifies the destination resource.
Important note:
The DRC MASK format must be ^ddd. This is then
compatible with the redirection LIST function used in
the input MAC program.
CALL PRIORITY 0 to 15 Calling DTE priority (CP >= RP).
By default = 0 Values higher than 15 are only usable with the
resource (BE00) of the VCP command port. This
allows to curb the command port rights.
MENU NUMBER 0 to 32 Number of menu to be displayed associated with the
By default = 0 password.
BILLING E At the end of the session, a record is stored in the
BILL billing table.
D (default setting) The "billing" service is deactivated.
Other Tables
E Page 8-1
E
8.2 NAME table
Each record of the NAME table links a service name to a resource name (known to Megapac only).
The NAME field contains a service name to be entered by the caller.
In the DRC MASK field, you can identify a destination resource fully or partially. This identification will
be used for routing purposes.
The content of the CALL PRIORITY field (CP) represents the call priority, assigned to the caller.
For routing to take place, the destination logical resource must have a resource priority (RP) less than or
equal to the caller's call priority.
The BILLING field establishes whether a record is to be stored in the "charging" file at the end of the
session.
For the OPTIONS field, the following options are available :

• ISO Refers to use of the OSI transport layer.
• PROF Refers to a PROFILE CODE/xxxx, record stored in the PROF file, in which
"xxxx" represents the DRC MASK specified in this NAME record.
• 7561 ICL 7561 emulation
• PPP Emulation of an asynchronous IP connection in point to point.
• PPP+PAP Emulation of an asynchronous IP connection in point to point, with « PAP »
authentication protocol.
• TELN PAD TELNET emulation (TELNET client).
• TELR REVERSE PAD TELNET emulation (TELNET server).
• NONE No option selected.
NAME Table :
The size of the NAME table is established using the MEM command.
The size of the table is specified in the "Number of Service Names" record of the MEM table.
The NAME command can be used to access the NAME table manually.
Routing :
Direct routing based on the service name entails configuring (OPTIONS = NAME) the resource of the
calling DTE. Two possibilities must be considered :
• The DRC MASK of the resource isn’t informed ( DRC MASK/ . . . . ), the caller must dial a service
name composed with 1 to 8 characters corresponding to an input of the NAME table.
• The DRC MASK of the resource is informed ( DRC MASK/ ABCD ), in this case ABCD is interpreted
as a 4-character service name, which must correspond to an input of the NAME table.
Other Tables
E Page 8-2
E
Structure of a NAME record
PARAMETERS
SETTINGS MEANING
NAME 0 to 8 characters Service name.
DRC MASK 4 characters Fully or partly identifies a destination resource, used for non-
automatic routing.
The DRC MASK format can be ^ddd. This is compatible with
the LIST function of an input MAC program.
CALL PRIORITY 0 to 15 Calling line priority(CP >= RP).
By default = 0
BILLING E At the end of each session, a record is stored in the BILL
table.
D (default setting) The "billing" service is deactivated.
OPTIONS ISO OSI transport layer - class 2 or 3.
PROF The PROF table contains a PROFILE CODE/xxxx record.
"xxxx" corresponds to the content of the DRC MASK field
specified in this NAME record.
3270 3270 terminal emulation.
An emulation buffer must have been configured first (BASE
descriptor).
PPP Emulation of an asynchronous IP connection in point to point
(see TERM descriptor).
Beforehand, the emulation buffer must have been configured
(BASE descriptor).
PPP+PAP Emulation of an asynchronous IP connection in point to
point, with « PAP » authentication protocol (see TERM
descriptor).
Beforehand, the emulation buffer must have been configured
(BASE descriptor).
TELN PAD TELNET emulation (Telnet client).
descriptor).
TELR REVERSE PAD TELNET emulation (Telnet server).
descriptor).
NONE No option.
default setting
Other Tables
E Page 8-3
E
8.3 MENU table
The MENU file is used in conjunction with the MENU NUMBER/NEWS NUMBER parameter ("logical
resource" level) or with a PASS record ("MENU NUMBER" field).
It can be used to show information to the caller, for guidance in the routing process.
Situations triggering the display of menus

• A non-X.25 call is received by the Megapac over a logical resource for which the MENU NUMBER/
parameter has been set. The MENU record for this number is displayed to the caller and indicates
the resources that are accessible.
• A non-X.25 call is received at the Megapac over a logical resource for which the OPTIONS/ PASS
parameter has been set. In this case:
• the MENU record number 0 is displayed to the caller. This introductory menu mainly
comprises a field prompting the caller to enter a password;
• the PASS table is then scanned and the appropriate PASS(n) record selected. The content of
its MENU NUMBER/ n field conditions display of the MENU(n) record of the same number.
This menu indicates the resource or resources accessible to the caller.
• A call request packet in which the "called DTE address" field is incorrect is received at the Megapac
over a logical resource for which the MENU NUMBER/ n parameter has been set. The MENU(n)
record of the same number is displayed to the caller indicating the resources that can be accessed.
• A call request packet in which the "called address" field is correct is received at the Megapac over a
logical resource for which the OPTIONS/ TALK parameter has been set. In this case::
• the PASS table is then scanned and the corresponding PASS(n) record selected. The
content of its MENU NUMBER/ n field conditions display of record MENU(n) of the same
number. This menu mainly indicates the resource or resources that can be accessed by the
caller.
• An incoming call uses a destination logical resource for which the OPTIONS/ GATE parameter has
been set. In this case:
• the PASS field is then scanned and the corresponding PASS(n) record selected. The content
of its MENU NUMBER/ n field conditions display of record MENU(n) of the same number.
This menu mainly indicates the resource or resources that can be accessed by the caller.
• After a call by service name over a logical resource configured with OPTIONS/ NAME parameter, the
incoming call is required to use a destination logical resource made temporarily unavailable. In this
case:
• if the NEWS NUMBER/ parameter is set with this destination logical resource, the
corresponding number menu is displayed to the caller. This record should contain a message
of the following type: "Logical resource xxxx, not currently available".
Other Tables
E Page 8-4
E
Structure of the MENU file
Maximum length = 1023 bytes

0 Introductory menu mainly prompting the caller to
enter a password.
1 Resources accessible to the caller.
1<n<32 Resource xxxx not currently available.
32 Resources accessible to the caller.
The MENU file size defaults to one record, so a MENU record number 1-32 can always be defined.
The size of the MENU file is established using the MEM command.
The size of the file is specified in the "Number of Menus" record of the MEM table.
The MENU command provides manual access to the MENU file.
Notes:
• the 7 or 8-bit character located immediately after the "@" character is processed transparently.
• each 8-bit character after the "&" character is processed transparently.
• ^J this command inserts a line feed without altering the cursor position.
• ^M this command inserts a carriage return and positions the first character of the next line at the
start of the line to the left of the screen. For display quality purposes, it is best to have a line feed (^J)
before the carriage return (^M).
• ^G this command inserts a beep which will be replayed on display to draw the user's attention
(EXAM command or on receipt of the menu).
• # this command displays the name of the logical resource used by the caller.
• #% this command displays the list of service names of the NAME file.
E.g.:
^J^M Your call is received on circuit # ^J^M

^J^M
The available services are: ^J^M
#%
^J^M
Indicate the service required ^J^M
^J^M
Other Tables
E Page 8-5
E
8.4 HELP table
The HELP table is used exclusively when the caller has selected the "service name" mode (OPTIONS =
NAME at "logical resource" level).
The value set for the HELP NUMBER parameter ("logical resource" level) provides access to the
corresponding HELP record.
Situations triggering display of a HELP record
A call with a wrong service name is received at the Megapac over a logical resource for which the HELP
NUMBER parameter has been set.
The HELP record number 0 is then displayed to the caller containing an introductory message.
When the caller enters "HELP <CR>" or "?", the HELP record with the number corresponding to the
value set in the HELP NUMBER parameter is displayed.
Structure of the HELP file
Maximum length = 1023 bytes

0 Introductory message.
1 Service names allowed.
32 Service names allowed.
The HELP file size defaults to one record, so a HELP record number 1-32 can always be defined.
The size of the HELP file is established using the MEM command.
The size of the file is specified in the "Number of Help Screens" record of the MEM table.
The HELP command provides manual access to the HELP file.
Notes:
• the 7 or 8-bit character immediately after the "@" character is processed transparently.
• each 8-bit character after the "&" character is processed transparently.
• ^J this command inserts a line feed without altering the cursor position.
• ^M this command inserts a carriage return and positions the first character of the next line at the
start of the line to the left of the screen. For display quality purposes, it is best to have a line feed (^J)
before the carriage return (^M).
• ^G this command inserts a beep which will be replayed on display to draw the user's attention
(EXAM command or on receipt of the menu).
• # this command displays the name of the logical resource used by the caller.
• #% this command displays the list of service names of the NAME file.
Other Tables
E Page 8-6
E
8.5 ILAN table
The NAME field identifies a resource or a logical resource.

• When the WAN initializes the transport connection, NAME identifies a resource corresponding to the
called TSAP.
• When the LAN initializes the transport connection, NAME identifies the destination logical resource.
The OPTIONS field can be used to specify the following mnemonics:
• ISO: (Can be selected only when the LAN initializes the transport connection).
Implementation of class 4 transport layer - ISO 8073/AD2.
• ISO + EXPE: (Can be selected only when the LAN initializes the transport connection).
Implementation of the class 4 transport layer - ISO 8073/AD2, with use of the "expedited data"
service.
• DBIT:
• the connection is initialized by the LAN: the D bit field is activated in the outgoing X.25 call
request packet and the ILAN interface inserts a D bit in all data packets before they are
transmitted over the X.25 network;
• the connection is initialized by the X.25 network: this implies that the D bit field has been
activated in the call request packet. In this case, the ILAN interface merely inserts the D bit in
the subsequent data packets.
• TALK: if this option is included in the ILAN table scanned for the incoming call request, the call is
forced to the Megapac's presentation mode and the caller receives the menu(n) configured.
• Y13: if this option is included in the ILAN table in a record used by an outgoing connection request
packet, the Megapac inserts a protocol identifier Y.13 in this packet for the transfer mode for the
protocol to be adopted, as described in option Y.13 of the MAC table (refer to the description in the
previous chapter).
• NONE: (Can be selected when the WAN or LAN initializes the connection).
No implementation of the class 4 transport layer - ISO 8073/AD2.
The ETHERNET ADDRESS field contains a destination address DA (MAC - IEEE 802.3), identifying a
LAN station.
The TSAP field identifies one or more transport service access points, used by the class 4 transport
protocol - ISO 8073/AD2. This field can be reconstructed using the "#"," syntax.
The USER DATA field contains call user data.
The size of the ILAN file is established using the MEM command.
The size of the file is specified in the "Number of ISO ETHERNET Addresses" record of the MEM table.
The ILAN command provides manual access to the file.
Other Tables
E Page 8-7
E
Structure of an ILAN record
PARAMETERS
SETTINGS MEANING
NAME 4 characters Resource/logical resource name.
OPTIONS ISO Class 4 transport layer - ISO 8073/AD2.
EXPE Class 4 transport layer - ISO 8073/AD2, with use of the
"expedited data" service.
DBIT Inserts the D bit in X.25 call request packet and data
packets.
TALK Activates the Megapac presentation mode.
Y13 Inserts a Y.13 protocol identifier in the call request packet.
NONE Cancels implementation of the class 4 transport layer - ISO
default setting 8073/AD2.
ETHERNET ADDRESS 12 characters Destination address DA (Mac-IEEE 802.3).
blank by default Note:
The DA address is used only if the WAN initializes the
connection to the LAN.
TSAP 0 to 20 characters Class 4 TSAP addresses - ISO 8073/AD2.
blank by default This field can contain the following information:
RRRR, LLLL The WAN initializes the connection:
RRRR = called TSAP.
LLLL = calling TSAP.
RRRR The LAN initializes the connection:
RRRR, LLLL RRRR = original called TSAP.
RRRR, (DDDD, LLLL) DDDD = reconstructed called TSAP.
LLLL = calling TSAP.
USER DATA 0 to 30 characters User data.
blank by default
Other Tables
E Page 8-8
E
8.6 BILL table
The "BILL" table retains information on calls through the Megapac and calls generated by the Megapac.
The size of the BILL file is established using the MEM command.
The size of the file is specified in the "Number of Billing Records" record of the MEM table.
The BILL table is circular.
When its specified maximum capacity is reached, excess records overwrite records at the start of the
file.
The BILL command provides manual access to the BILL table.
☞ Access to the "BILL" table is denied for incoming calls with a call priority CP=1 where the
GATE option is set (outgoing password control).
At the end of each session, a "billing" record is stored when any of the following situations applies:
• In "automatic routing" mode, the call request packet uses a logical resource set with the BILL option.
Remember that if the PASS or GATE option is specified for the resource, the BILL option is not
applicable. The "BILL" table service is provided by the BILLING parameter of the PASS table.
In "automatic routing" mode, connections successfully established and rejected connections are
logged in the "BILL" table.
• In "presentation" mode, the corresponding PASS record has "E" (Enable) in its BILLING field.
• In "service names" mode, the corresponding NAME record has "E" (Enable) in its BILLING field.
• The incoming link uses the input MAC table (ECM=IN). The MAC table has a record (DAD, CAD,
FAC, CUD) with the BILL option.
For a record using CUD "routing based on call user data", the "password" field of the BILL record
contains the first 8 characters of the "user data" field.
For a record using the transport layer, TCAL+BILL option, the "calling address" and "called address"
field of the BILL record contains the corresponding TSAP (SSAP and DSAP) in hexadecimal.
Other Tables
E Page 8-9
Megapac prints out charging tickets at the end of a call when configured to do so. These tickets are
placed in the circular "BILL" file.
• Charging tickets always contain the following information:
• The serial number of the ticket (this number is zeroed when memory is initialized by the MEM
RESET/YES command),
• The date and time of the start of the call,
• The call duration (minutes and seconds),
• The number of "packets" sent and received,
• The number of bytes sent and received.
• Tickets can also contain the following optional information:
• The caller's password, if there is one (PASS or GATE option),
• The call request packet's user data (on X.25 with the BILL option in the MAC-IN table),
• The call request packet's calling and called addresses (on X.25 without transport),
• The call request packet's reverse charging facility (on X.25),
• The call clearing packet's cause and diagnostic code (on X.25),
• The SSAP and DSAP if the Transport layer is used (TCALL+BILL option).
The ticket is placed in the BILL file where the two Megapac resources are disconnected, provided that:
• The calling resource (or called resource in X.25) is configured with the BILL option, or
• The BILL option is dynamically requested on this resource by the BILLING ENABLE parameter of the
PASS or NAME files or via the BILL option in the MAC-IN table.
Typical Meaning Number

display (Each field is separated by a tab) of characters
(00) Queue record number (Cyclic sequence number). 1-3
john Password entered by caller / user data. 8
03/09/94 Connection set up date. 8
16:08 Connection set up time. 5
0/0 Cause and Diagnostic Codes. 1-3/1-3
- Reverse charging: 1
R activated,
– deactivated.
Link service packets must be in extended format (EXT option
of X25 descriptor).
1/55 Connection time in minutes/seconds. 1-n/1-n
EI00 Calling party address / SSAP. 15
BE00 Called party address / DSAP. 15
0001;0002; Number of packets sent and received. 2-n
Number of segments sent and received when SEGMENT
E
ACCOUNTING = YES (BASE descriptor).
0013;0085 Total number of bytes sent and received. 2-n
Other Tables Page 8-10
E
8.7 ELOG table
This table stores messages concerning "system" errors and anomaly situations.
The text of these messages is normally self-explanatory.
The size of the ELOG file is established using the MEM command.
The size of the file is specified in the "Number of Error Log Records" record of the MEM table.
The ELOG file is circular.
When its specified maximum capacity is reached, excess records overwrite records at the start of the
file.
The ELOG command provides manual access to the ELOG file.
Structure of an ELOG record
FIELD NAME CONTENT MEANING

TIME HH:MM:SS Time event occurred.
DATE DD/MM/YY Date event occurred.
MESSAGE Self-explanatory text Event.
System error.
Irregularity.
Other Tables
E Page 8-11
Other Tables
E Page 8-12
9. TYPE/ X25 descriptor
9.1 General
The Megapac can be configured to handle X.25 calls via an XIO, MIO, SIO interface board, or board with
SCC controller as the range Megapac ESL and Megafrad.
The XIO board has a dedicated built-in processor and is therefore the best suited for this protocol.
The Megapac can also be configured to handle X.25 calls via the ISDN network. For this, and depending
on the Megapac type, the GIS card offers S0 (2B+D) basic rate access, and the PRI card offers T2
(30B+D) primary rate access.
The TYPE/ parameter of any link descriptor determines the Megapac's operating mode and must be set
to X25 to enable an X.25 synchronous link to be set up. In the event, a TYPE/ X25 link descriptor
corresponds to a physical controller which requires each I/O board which might be accessed by the CPU
to be addressed uniquely.
The next (SUB-TYPE) parameter of the descriptor, containing the type of board that the physical
controller is required to address, is important to enable the system to differentiate the boards installed in
the Megapac.
TYPE/ X25 descriptor
E Page 9-1
9.2 Link configuration parameters
The tables on the following pages summarize the various parameters which can be set in the X.25 link
descriptor.

Name Settings
NAME Up to 4 characters Link name.
Two X.25 links (normally PS01, PS02) are always configured by
default.
The remaining links are named XXXX with the NULL type.
TYPE By default = X25 The default setting of X25 (PS01 or PS02) specifies that the
descriptor will be used on an X.25 link.
SUB-TYPE By default = XIO+SIO, Type of interface board that the descriptor must address.
XIO, SCC or NONE
VIO X25 Virtual input - output descriptor
Used to perform protocol conversion, typically X.25 levels 2 and 3,
on frame relay service.
SCC The descriptor addresses a board with SCC controller (68302).
• an MIO board for this link, or
• a link of Megapac ESL and Megafrad.
GIO The descriptor addresses a board supporting the "Generic
Interface" for this link.
For GIS (S0) three descriptors must be declared (2B+D).
The first descriptor of a GIS board contains the interchanges with
the board.
XIO The descriptor addresses an XIO board for this link.
SIO The descriptor addresses an SIO board for this link.
XIO+SIO On the Megapac E, Megabox and Megabox SL, this combination
can address either an XIO-E or SIO-E card in X25 protocol.
PRI The descriptor addresses a PRI-64 board for this link. A PRI-64
board allows the connection of 1 or 2 T2 primary accesses
(30B+D) on the VME Megapac.
For each Primary access from 1 to 30 SUB TYPE/ PRI descriptors
must be configured.
The first descriptor of PRI-64 board (1 or 2 T2 accesses) must be
NPI/ YES. All the other descriptors of the same PRI-64 board
must be NPI/ NO.
NONE Usage reserved - Do not use.
NEW PHYSICAL by default = NO This descriptor shares the same link as previously defined in X25
INTERFACE (NPI) mode.
YES A new X.25 link is assigned to this descriptor.
For XIO, SIO, MIO/SCC boards, this parameter should normally
be set to YES.
With PRI-64 and GIS boards, only the first descriptor of the board
should be set to NPI/ YES.
E Page 9-2
E
SPEED
1MHZ, 512K, 256K,
Choice of : 2MHZ,
128K, 64K, 48K, 19.2,

9600, 4800, 2400,
Link operating speed, in bits per second.
With an SIO board, the limit is 19 200 bit/s.
With an XIO-E board, the possible speeds are 9600 to 2 Mbit/s.
1200, 600, 300 or EXT. With an XIO-VME board the speed is strap selectable 300 to
2 Mbit/s.
By default = EXT
With an MIO board (SUB TYPE/ SCC) the possible speeds are
2400 to 64 Kbit/s.
With a Megapac ESL or Megafrad (SUB TYPE/ SCC), the
possible speeds are 2400 to 256 Kbit/s.
EXT: the speed is determined by the external clock.
(T2 board) For a X25 descriptor with SUB-TYPE=PRI-64 (T2 board) and
Megapac VME NEW PHYSICAL INTERFACE=YES, this parameter specifies the
operating mode of the T2 board interfaces.
SPEED=EXT Specifies the operating mode as DTE with external clock (the T2
card uses the network clock).
Is usually used when connected to an ISDN network.
SPEED=2MHZ Specifies the operating mode as DCE with internal clock (the T2
card uses the internal clock board).
PIGGY TYPE By default = V24 Choice of the interface type
Megapac ESL and (DCE+V24) The hardware must be correctly configured (straps) to allow the
Megafrad software to choose the interface type.
DCE The physical interface type is the DCE type.
This mode must be used in V24 interface.
It can be used in X21 and V35 interface on the J1 and J2 ports.
V24 (J1 to J6) The V24 interface is used. it provides :
or DCE+V24 • a DCE port (to a terminal), using the straight cable 55.670.243
• a DTE port (to a modem), using the crossed cable 55.670.357
DCE+X21 (J1 to J2) The optional X21 interface of the J1 and J2 ports is used in DCE
mode (to a terminal).
DCE (J1 to J2) The optional V35 interface of the J1 and J2 ports is used in DCE
DTE The physical interface type is the DTE type.
This mode must not be used in V24 interface.
DTE+X21 (J1 to J2) The optional X21 interface of the J1 and J2 ports is used in DTE
mode (to a modem).
DTE (J1 to J2) The optional V35 interface of the J1 and J2 ports is used in DTE
mode (to a modem).
PACKET SIZE Choice of: 32, 64, 128, Maximum negotiable outgoing packet size, in bytes.
256, 512, 1024, 2048,
4096 or TRAN.
By default = TRAN Packet size transparency.
Any packet size accepted, up to the size of the internal buffers.
BANDWIDTH 0 to 32767. Maximum throughput , in characters per second tenth.
By default = 0 An incoming call is routed over a virtual circuit of the link if the
required throughput (specified for the incoming resource either by
E
BANDWIDTH/, or by the THRU option of the input MAC table) is
less than or equal to the available throughput of the link.
TYPE/ X25 descriptor Page 9-3
E
V54 MODEM
By default = NO Enables or disables the facility to run V.54 tests on the link.
When this mode is enabled, V.54 tests can be run using the
commands V54L (local loop), V54R (remote loop) and then TEST
(test activation), and are deactivated by the V54X command.
YES V.54 tests can be run on the link.
With an XIO board, the "TEST" option should be selected.
NO V.54 tests cannot be run on the link.
ADDRESS By default = DCE Establishes the profile of the link descriptor between data
circuit terminating equipment - DCE, or data terminal
equipment - DTE.
The defaults links descriptors PS01 and PS02 are respectively
DTE and DCE mode.
DTE or A The link descriptor is a logical DTE, and can communicate only
with a "logical DCE".
DCE or B The link descriptor is a logical DCE, and can communicate only
with a "logical DTE".
AUTO In V.25bis configuration:
(AUTO+DTE) The link descriptor is a logical DTE when it initiates the call.
The link descriptor is a logical DCE when it receives the call.
AUTO+DCE In V.25bis configuration:
The link descriptor is a logical DCE when it initiates the call.
The link descriptor is a logical DTE when it receives the call.
CHANNELS By default = 1 Number of logical resources associated with the link.
1 to 4096, if the LCGN Any change to the number of "CHANNELS" associated with a link
parameter is 0 must be followed by a BOOT command for the change to take
effect.
1 to 256, if the LCGN
The defaults links descriptors PS01 and PS02 are configured with
parameter is other
16 channels (number from 0 to 15).
than 0
E Page 9-4
E
OPTIONS
By default = NONE Level 2 operating options for the link.

Various parameter settings can be aggregated for a given link.
By default, no special level 2 operating options for the link are
implemented.
POLL Attribute qualifying transmission of an RR frame with the P bit
set to 1 when no frame has been received over the link for a
time representing 1 to 2 times timer T1.
see below the DCD option.
If the RR frames are not acknowledged, after the permitted
number of TRIES, the link is reset (message - link NOT
RESPONDING).
The XIO card does not have this option.
1984 Attribute qualifying acceptance over the link of data packets
and interrupt packets in the extended format (X.25 mode -
1984).
In the second type of packet, the call user data field can have a
maximum length of 32 bytes.
EXT Attribute qualifying acceptance over the link of call set up and
clearing packets in the extended format.
(Extension of "supplementary services" field)
HOLD Attribute qualifying the maintenance of exchanges at level 3 on
the link, following disconnection or reconnection at the link
level.
After reconnection at the link level, the Megapac does not send
restart packets.
This option must be used only in exceptional circumstances.
STAT Attribute qualifying the insertion of a "diagnostic" code in a
clear request or indication packet sent over the link.
NET The DTE logical link behaves like a DCE logical link, while
respecting the "Command - Response" codes of the DTE.
This option offers the possibility of transmitting a "cause"
code across a Megapac network, even if the link has been
configure in DTE logical mode at the "ADDRESS" field level.
DMOD Attribute qualifying the forcing of the D bit to 0 (end-to-end
acknowledgment) in an outgoing data packet.
This option applies only to outgoing routing.
DCD Attribute qualifying supervision of carrier detection (CD signal)
on the link.
DCD option only : the Megapac indicates loss of carrier if the input
signal DCD(DTE) or RTS(DCE) is absent after two samples on a
period of 1 to 2 times 6 seconds.
DCD+POLL option, the Megapac indicates loss of carrier if the
input signal DCD(DTE) or RTS(DCE) is absent after two samples
over a period of 1 to 2 times T1 (or 6 seconds).
(message - link LOSS OF CARRIER)
Note : this option cannot be used with a PRI-64 board (T2 card),
that is to say a X25 descriptor and SUB-TYPE=PRI.
E Page 9-5
E
OPTIONS
(CONTINUED)
CRC4
(Megapac VME)
For an X25 descriptor of SUB-TYPE=PRI (T2 card) and

NEW PHYSICAL INTERFACE=YES, this parameter indicates the
operating mode of the T2 card interfaces.
CRC4 option = ETSI operation- (Euro-ISDN with CRC4)
Without CRC4 option (NONE) = France without CRC4 operation
IDLE Not significant with X25 descriptor.
VRFY Since the 500 software release, verification, insertion or
INSE (+VRFY) substitution of the originating address (calling DTE) can no
longer be specified in the OPTIONS/ parameter of the X.25 link
SUBS (+VRFY)
descriptor (Options VRFY, INSE, SUBS).
The MAC table with the CAD function "Calling DTE address" and
the TLAT option "Call request packet reconstruction" will be used
for this purpose.
UI Attribute qualifying acceptance over the link of Unnumbered
Information frames, UI.
This option applies on to links on XIO and GIO modules and is
needed where the V.25 bis procedure is used on the link.
With SIO and XIO, enables modem management commands to
be used.
See commands CMND and SEND described in the Operating
procedures section.
XIDC Enables XID-X.32 control on the link in command mode.
The link switches to command mode when set up.
The Megapac sends an XID command at frequency T1 until it
receives an XID response frame or a set-up frame.
Only the first record in the MAC table for the link concerned is
taken into account.
XIDR Enables XID-X.32 checks on the link in response mode.
The link switches to the response mode when set up.
The Megapac waits for an XID command frame before returning
an XID response frame then a set up frame, if a record in the MAC
table (for the link concerned) matches the content of the XID
received.
TEST Test frame management on XIO board.
On XIO boards, the test option is used with V54 MODEM = YES.
This option enables the XIO board to handle level 2 test frames.
DTR Management of signal 108 / DTR on initialization, only on SIO
(SIO board only) board.
Without DTR option : On initialization (BOOT), on the "SIO"
board, the Megapac turns off the DTR signal and turns it on again
before the SABM / UA interchanges.
With DTR option : On initialization (BOOT), on the "SIO" board,
the Megapac turns off the DTR signal and keeps it off. With this
option, when the link is used in V25B, V25 Bis mode signaling is
not carried out by the associated V25B. The associated V25B
resource sends on the DTR signal so as to trigger the V25B call
from an external adapter.
E Page 9-6
E
INIT FRAME
SABM
By default : SABM Link reset method.

Various parameter settings can be aggregated for a given link.
Attribute qualifying transmission of an SABM frame when the

link is reset.
This entails use of the LAPB procedure.
PBIT (+SABM) Aggregated with SABM, this attribute qualifies the transmission
of an SABM frame with the P-bit set.
In the absence of response, this frame is retransmitted. A DISC
frame with the P bit set to 1 is sent.
When a 10 s timer runs out, the above sequence is repeated.
DISC Attribute qualifying transmission of a DISC frame when the link
is reset.
The link is then in the disconnected state, waiting to be initialized.
NONE The link is set up in passive mode; the link is set up from the other
end.
T1 2 to 80 Time after which an unacknowledged frame is retransmitted
In 1/10ths of a second over the link.
By default = 30 By default, the time delay is 3 seconds.
The T1 value must be reduced with respect to the link speed. For
1 or 2 Mbit/s links, the value T1=5 is recommended (0.5 seconds).
T3 4 to 255 Time, by default = 6 seconds, after which the "channel idle for
In 1/10ths of a second excessive time" indication is sent over the link.
By default = 60 T3 applies only to XIO board links.
On the SIO board, the POLL option can be used (which provides
the T3 function).
TRIES 2 to 80 Maximum number of retries for a level 2 information frame,
(N2 of X.25) By default = 10 before the link is reset.
(message - link DOWN)
K LEVEL2 1 to 31 Window size at the "frame" level 2.
By default = 7 (Depends on the FRAME SEQ setting)
for 1, the window = 1 In normal frame mode, with the "FRAME SEQ" link parameter set
for 2, the window = 2 to its default "NORM" setting (see below), the settings are:
for 3, the window = 3 Window size: 1 to 7.
for 4, the window = 4
other, the window = 7
for 1, the window = 3 In extended frame mode, with the "FRAME SEQ" link parameter
for 2, the window = 7 set to "EXT" (see below), possible setting for the parameter
for 3, the window = 15 correspond to the following window sizes:
for 4, the window = 31 Window size: 3 to 127.
other, the window = 127
E Page 9-7
E
K LEVEL3 1 to 127
for 1 to 7
for 8 to 127
Window size at the "packet" level 3. (see § 9.2.1)

Normal frame mode (the window size level 3 is modulo 8)
Extended frame mode (the window size level 3 is modulo 128)
(By default = 2) Note : In extended frame mode with an SIO board, the buffer size
(PACKET SIZE parameter), must be smaller than the internal
buffer size.
LINE GROUP 0 to 15 Attribute qualifying an even distribution of calls within a link

No units. group.
By default = 0 When the parameter has a setting other than 0, the Megapac
implements a procedure for evenly distributing calls over the links
assigned the same parameter setting, provided that the links are
assigned the same other routing criteria: RP, CP, etc.
The setting 0 disables the call distribution function.
LCGN 0 to 15 Logical resource group number.
By default = 0 This parameter defines the range of numbers for virtual circuits
associated with the link.
Logical resource group numbers are generally assigned as
follows:
• 0, 1: Permanent virtual circuits.
• 2, 3: Incoming logical resources.
• 4, 5: Both way logical resources.
• 6, 7: Outgoing logical resources.
0 The number of logical resources, the "CHANNELS" parameter
of the link (see above), which can be associated with the link is
between 1 and 4096.
For each logical resource, the Megapac computes the LCGN
setting and inserts it in the "logical channel group number" field of
the packet.
from 1 to 15 The number of logical resource which can be associated with
the link is from 1 to 256.
LCN OFFSET 0 to 4095 Threshold for number assigned to the first logical resource
By default = 0 attached to the link.
The first logical resource attached to the link is assigned a number
equal to:
("LCGN" x 256) + "LCN OFFSET"
in which "LCGN" is the setting of the "LCGN" parameter, and
"LCN OFFSET" is the setting of the present parameter.
The ensuing logical resources are assigned numbers incremented
by 1 as the link's logical resources are described.
ADDRESS 0 to 15 Link address domain or group.
GROUP By default = 0 A number of X.121 addresses with the same "ADDRESS GROUP"
setting belong to the same network domain.
This attribute, used in conjunction with the same parameter in the
X.25 table's records, can be used to implement a routing
mechanism between multiple addresses in different network
domains, depending on the outgoing link selected.
E Page 9-8
E
FRAME SEQ
EXT
By default = NORM Normal or extended frame sequencing mode (level 2).

Extended (level 2) mode frame sequencing:
Sequence numbers from 0 to 127 (modulo 128).
NORM Normal (level 2) mode frame sequencing:
Sequence numbers from 0 to 7 (modulo 8).
CALL TIME OUT 2 to 200 Call confirmation supervision timer (TP2).
In seconds Represents the maximum time waiting for a call accepted packet
By default = 5 in response to a call request packet.
When the timer runs out, a clear indication packet is sent to the
local DTE and to the remote DTE.
ERROR 1 to 250 Threshold for the number of the CRC errors detected,
THRESHOLD By default = 20 triggering generation of a message in the ELOG table.
The counter is then reset and the cycle continues.
Note : There is no link with the CRC ERRORS counter displayed
after executing the STAT command.
LOOP BAR 0 to 15 Call loop.
PRIORITY By default = 0 This parameter can be used to prevent outgoing calls being
looped back via the link over which they arrived. The loop is
barred when the parameter has the same setting as the
"RESOURCE PRIORITY" parameter of the outgoing link.
You can then prevent calls being looped over the same link.
EXTENDED CALL By default = NONE Extension of routing facilities.
MANAGEMENT NONE = routing does not use the MAC table.
IN Activates the input MAC table for this link.
OUT Activates the output MAC table for this link.
V25M The NAME/ parameter of the TYPE/ X25 descriptor is used by the
V25B virtual descriptor to activate monitor mode on a backup link.
Note : The class 3 OSI transport protocol can be used to allow the
procedure for reassigning VC on fault to be implemented.
V25B This option activates the V.25 bis dialing facility in conjunction
with the V25B virtual descriptor. The NAME/ parameter of the
TYPE/ X25 descriptor is used by the V25B virtual descriptor to
send V.25 bis dialing information taken from the MAC table to the
modem connected to the public network.
E Page 9-9
E
OPTIONAL
TIMERS
T13 (180 seconds)
By default = NONE Implement optional timers.
Call clear confirmation packet timer in logical DCE mode.

If the link is set to logical DCE mode, a clear confirmation packet
is awaited for 180 seconds before sending a clear request.
When the timer runs out, the clear request is retransmitted and
the logical resource forced to the DISC state.
T23 (180 seconds) Call clear confirmation packet timer in logical DTE mode.
If the link is set to logical DTE mode, a clear confirmation packet
is awaited for 180 seconds after sending a clear request.
When the timer runs out, the clear request is retransmitted and
the logical resource forced to the DISC state.
OPTIONAL 0 to 60 Number of flags (7E hex) to be inserted between consecutive
FLAGS By default = 0 frames.
Applicable to links on XIO boards only, the insertion of flags
between frames can be used to adapt the link to equipment which
cannot handle a short inter-frame gap at high bit rates.
If several flags are needed, specify the number required minus 1.
E Page 9-10
E
9.2.1 Fragmentation
Rising bit rates over X.25 links have lead to an increase in packet size and mean that the Megapac is
increasingly being required to fragment packets in X.25 switching/concentration mode. Such is the case,
for example, of a site concentrating 9600 bit/s X.25 ports with 128-byte packets into 128 kbit/s ports with
512-byte packets and a window size of 3.
The table below gives the maximum packet window size that can be set according to the packet
fragmentation ratio between the two X.25 ports. In the above example, in which the fragmentation ratio
is 512/128 - 4, the packet window size can be set to its maximum value (7).
Fragmentation ratio Maximum packet window size

2 7 or 16 (extended format)
4 7or 8 (extended format)
8 4
16 2
32 1
The window to be taken into account is that of the X.25 port with the biggest packet size. By observing
the requirement of this table, the Megapac will not lose packets even in the worst case X.25 level 3 flow
control conditions (port speed, PAD imbalance, etc).
9.2.2 "Recommendation X.32" XID identity check
The XIDR and XIDC options previously described require records in the MAC table.
The list of XIDs must be entered before any input MAC program (IBEG, etc) or output MAC program
(OBEG, etc).
The list of all the XIDs of all the links must be included at the start of the MAC table. This list must not
have gaps and, for convenience, the XIDs of the same link are kept together.
NAME FUNCTION OPTION SELECTOR GENERATOR

link descriptor XID NONE XIDC information with extension
(∗ is authorized) of the link by "-" if necessary (hex
and uppercase)
link descriptor XID NONE XIDR information with
(∗ is authorized) extension of the link by "-" if
necessary (hex and uppercase)
E Page 9-11
9.3 Bandwidth Management on the X25 link:
Bandwidth management on calls over a link is implemented if the bandwidth parameter of the link
descriptor is set to a non-zero value. This defines the maximum bandwidth that can be handled by the
link (bit rate shared between calls). To take account of encapsulation and the random nature of the
traffic, it is best to define approximately 80% of the link bit rate. The value should be expressed in bytes
per tenth of a second.
The "BANDWIDTH" parameters of the X.25 link descriptors and of the associated resources enable
bandwidth management.
9.3.1 Maximum link throughput
The "BANDWIDTH" parameter of the link descriptor represents the maximum throughput that can be
handled by the link.
⇒ the "BANDWIDTH" of the link descriptor is expressed in characters per tenth of a second.
Line bit rate Effective throughput = theoretical Link descriptor BANDWIDTH

throughput - 20% parameter settings
64 kbit/s 6.400 characters/s 640
9.3.2 Required throughput for an incoming call
On an X.25 link, the required throughput for an incoming call can be defined in two ways:
1 - MAC table and THRU option
The incoming link descriptor has the EXTENDED CALL MANAGEMENT parameter set to IN (ECM=IN)
and an input MAC table record with the THRU option.
NAME FUNCTION OPTIONS SELECTOR GENERATOR

PS04 IBEG NONE
PS04 DAD THRU ∗ 9600
PS04 IEND NONE
All incoming calls from link PS04 are assigned a required throughput of 9600 bit/s, in other words 1200
characters/s.
The MAC table and the THRU option take priority over the bandwidth parameter on the incoming
resource.
2 - Bandwidth on the incoming resource
If there is no record in the MAC table with the THRU option, the required throughput for an incoming
call can be specified using the BANDWIDTH parameter for the incoming resource.
⇒ the "BANDWIDTH" on the resource is expressed in characters per tenths of a second.
E Page 9-12
9.3.3 Call routing according to required throughput
A virtual circuit of an incoming link which has a required throughput indication can be routed only on a
virtual circuit of a link for which the available throughput is equal to or greater than the requested
throughput.
9.3.4 Available throughput of a link
The available throughput of a link is equal to the maximum throughput of the link minus the
throughput assigned to each virtual circuit set up on the link.
9.3.5 Throughput assigned to an established virtual circuit
Throughput assigned to an incoming virtual circuit:

The throughput assigned to an incoming virtual circuit depends on:
• the parameters of the incoming link descriptor, and
• the parameters of its associated resources.
The dynamic throughput is updated once a second.
Bandwidth of incoming link = 0 Bandwidth on incoming link > 0
ECM=IN ECM=NONE ECM=IN ECM=NONE

+ THRU in MAC table + THRU in MAC table
incoming incoming incoming incoming incoming incoming incoming incoming

resource resource resource resource resource resource resource resource
bandwidth bandwidth bandwidth bandwidth bandwidth bandwidth bandwidth bandwidth
=0 >0 =0 >0 =0 >0 =0 >0
Throughput assigned Throughput Throughput Throughput assigned = Dynamic Throughput

= assigned assigned bandwidth given by the throughput assigned
bandwidth given by the = = incoming THRU option = =
incoming THRU option All the link bandwidth of the available bandwidth of
bandwidth incoming throughput of the incoming
resource the link / resource
number of
established
virtual circuits
E Page 9-13
Throughput assigned to an outgoing virtual circuit:

The throughput assigned to an outgoing virtual circuit depends on:
• the parameters of the outgoing link descriptor,
• the parameters of its associated resources, and
• the requested throughput for the incoming call.
The dynamic throughput is updated once a second.
Bandwidth on outgoing link = 0 Bandwidth on outgoing link > 0

outgoing outgoing resource outgoing resource outgoing resource
resource bandwidth bandwidth bandwidth
bandwidth >0 =0 >0
=0
ECM=IN incoming Throughput Throughput

resource assigned assigned
bandwidth = =
=0
+ THRU in incoming bandwidth given Throughput bandwidth given Throughput
MAC table resource by the incoming assigned by the incoming assigned
Incoming
bandwidth THRU parameter = THRU parameter =
>0
link incoming Throughput bandwidth of the Dynamic bandwidth of the
resource assigned outgoing resource throughput outgoing resource
bandwidth = =
ECM = =0 all the bandwidth available
NONE of the outgoing throughput of the
link outgoing link /
number of
established virtual
circuits
incoming Throughput Throughput
resource assigned assigned
bandwidth = =
>0 bandwidth of the bandwidth of the
incoming incoming resource
resource
E Page 9-14
9.4 Transport layer configuration
The Megapac can handles class 0, 2 and 3 transport facilities.

There are three ways of invoking the transport layer (source Megapac):
a) by specifying the ISO option for a source resource.
b) using the NAME table in which the ISO option will be specified.
c) if the descriptor is X25, the ISO option can be set in the MAC table.
In each of the above three cases, the source Megapac sends an X.25 connection request to which the
remote end responds with confirmation.
For this operation, the remote Megapac uses the MAC (IN) table specifying the TCAL option (Transport
CALL), indicating the presence of the transport facility.
The source Megapac, on receiving the X.25 confirmation, initiates a Transport connection request (T_CR
-> Transport Protocol Data Unit_Connect Request) acknowledging the remote end (T_CC -> Connect
Confirm).
The structure of the Transport address is designated TSAP (Transport Service Access Point).
This is used to identify both ends of the transport "circuit".
The Megapac uses :
• the four characters of the source resource name for the local TSAP,
• the four characters of the "destination" resource name to make up the remote TSAP.
It is therefore important to have the same destination resource names in the Megapacs at both ends of
the transport connection.
E Page 9-15
9.4.1 Transport layer parameters
TRANSPORT LEVEL TYPE/ NONE Transport function not enabled for this link.
ISO This parameter activates the transport function for this
link.
TRANSPORT CLASS/ NONE The transport function is not enabled for this link.
0 The "simplest" service, requires a network layer
providing an acceptable error ratio.
Simple end-to-end connections, without error correction
(transmission problems or release).
Errors are detected by the network layer and transmitted
to the transport layer, but with no action taken.
Conventional application: teletex terminals.
2 Multiplexes a number of transport connections over
one network connection.
Flow control may be requested to avoid congestion
problems on the network connection.
No restart on error mechanism.
3 Multiplexes a number of transport connections on the
same network connection.
Flow control may be required to avoid problems of
congestion on the network connection.
Restart on errors reported mechanism
implemented.
DEFAULT WINDOW SIZE/ 0 to 7 Credit limit for transport session calls.
By default = 0 Must be set to 1 at least.
DISABLE FLOW CONTROL/ NO Default setting.
YES Flow control set to YES only if the transport class is 2.
E Page 9-16
E
TSAP FORMAT/
TEXT Outgoing and incoming resource names (4 characters)

form the TSAPs used for transport layer connection
requests.
For example, when the NAME/ parameter of an
incoming resource is defined as P200, with the DRC
NAME/ parameter specified as P300, the following rule
applies:
TSAP FORMAT/ TEXT.
LOCAL TSAP = P200.
REMOTE TSAP = P300.
NAME As TEXT, but the NAME table is analyzed according to
the REMOTE TSAP received.
This is used mainly to activate a TELNET session using
the transport layer.
HEX Reserved for future use.
MAXIMUM TPDU SIZE/ 128, 256, 512 or 1024 Maximum packet size at the transport level.
By default = ???? Depends on the size of the buffers in the software
release.
If the TPDU size is greater than the PACKET SIZE, an
appropriate number of BUFFERS must be configured for
each level 3 resource.
Example: (system buffers = 512) and (TPDU= 1024).
PACKET SIZE: 256 TRAN
BUFFERS: 1024:256=4 1024:512=2
TTR/ 0 to 120 seconds Reassignment/resynchronization test timer.
By default = 0 This timer is initiated by the sending end when a call is
cleared (reset or reassigned on fault) by the X.25
network, allowing time for the network to replace the
defective link, for example, then send a
resynchronization request.
The resynchronization request entails forwarding or
reforwarding any TPDU_DT (Data) which has not yet
been acknowledged.
An acceptable setting is between 10 and 15 seconds.
TWR/ 0 to 120 seconds Time delay awaiting reassignment/resynchronization.
By default = 0 This timer is initiated by the receiving end on a network
fault. When the timer runs out, the transport session is
declared disabled.
The timer setting is correlated with that of TTR; TWR
must be greater than TTR. A typical setting is
approximately 25 seconds.
Note concerning timers

The various timers should be handled with particular care.
When a reconnection problem occurs, it is advisable to check the settings of the TTR and TWR
parameters, and of CALL TIME OUT, T1, T3 and TRIES.
E Page 9-17
9.4.2 Example of a class 3 transport configuration
TRANSPORT BUFFERS/ 10 TRANSPORT BUFFERS/ 10
X25 table: MAC table:

Name AG. Address User data Name Function Options Selector Generator
P300 0 789* PST4 IBEG
PST4 DAD TCAL 789* TATA
PST4 IEND
NAME/ P300 NAME/ P400

... ...
OPTIONS/ NONE OPTIONS/ ISO
NAME/ PST4
NAME/ PST3 TYPE/ X25
TYPE/ X25 OPTIONS/ DCD
OPTIONS/ DCD ...
... EXTENDED CALL MANAGEMENT/ IN
TRANSPORT LEVEL TYPE/ ISO ...
TRANSPORT CLASS/ 3 WAN TRANSPORT LEVEL TYPE/ ISO
DEFAULT WINDOW SIZE/ 7 TRANSPORT CLASS/ 3
DISABLE FLOW CONTROL/ NO DEFAULT WINDOW SIZE/ 7
TSAP FORMAR/ TEXT DISABLE FLOW CONTROL/ NO
MAXIMUM TPDU SIZE/ 256 TSAP FORMAR/ TEXT
TTR TIME/ 15 MAXIMUM TPDU SIZE/ 256
TWR TIME/ 30 TTR TIME/ 15
TWR TIME/ 30

... ...
OPTIONS/ ISO OPTIONS/ NONE
NAME/ PS02 NAME/ PS03

TYPE/ tout type TYPE/ tout type
MEGAPAC 1 MEGAPAC 2
called 789
Figure 9-1 Example of a class 3 transport configuration
E Page 9-18
A transport connection is set up as follows:
Megapac Setting up a transport connection

1 A resource of link PS02 receives a call for N° 789.
1 The resource initializing the call has the ISO option set, so buffers are reserved.
The ISO option specifies that a transport connection must be set up after a virtual circuit.
1 The X.25 table is used for routing and the destination resource is P300.
1 A P300 resource of link PST3 is selected and an X.25 call is sent over the WAN.
2 An X.25 call is received over link PST4 with Extended Call Management set to IN.
2 The MAC table is scanned for link PST4, and indicates that:
• for called number 789, it is essential to wait for the transport connection to be set up for call
routing purposes (TCAL option).
• TATA specifies a unique reference for the X.25 call and this indicator is used when
resynchronizing the transport connection.
2 The X.25 call confirmation is returned over the WAN.
1 A transport connection request is sent over the WAN with the following indications:
• Local TSP = P200
• Remote TSAP - P300
2 The remote end acknowledges the transport connection, and uses "Remote TSAP = P300" to route
the call.
E Page 9-19
9.4.3 Additional "transport" configuration information
BASE "descriptor" parameters:

TRANSPORT BUFFERS (0-2048): defines the number of transport sessions allowed on a Megapac.
For each resource using a transport connection, two buffers must be reserved. The first is for checking
the multiplexing of other transport session on the virtual circuit and the second is for transferring data to
the transport level.
INACTIVITY DETECT TIMER (0-30): controls disconnection on inactivity.
If a number of transport sessions are multiplexed on a virtual circuit, each initiates an equivalent timer;
when there is only one current session left, and the associated timer runs out, the transport layer is
disconnected.
This timer setting is specified in minutes and the sampling setting is twice the timer setting. By setting
the INACTIVITY DETECT TIMER to 1, disconnection on inactivity will occur after 2 minutes.
To be able to use this timer on a resource, you must set the IDLE option for that resource.
Y13 option - insertion of the calling address

For the "source" Megapac, this function should be indicated in the OPTION field of an MAC table record.
Source Megapac:
Name Function Options Selector Generator
Mac (n) PS** IBEG NONE
Mac (n+1) PS** DAD ISO + Y13 55 P100
Mac (n+2) PS** IEND NONE
• ISO: can be used to invoke the transport layer.

• Y13: this option adds to the TPDU_CR (Connection Request), information specifying the insertion of
the calling address when reconstructing the level 3 X.25 call request packet at the destination
Megapac output.
Destination Megapac:
Mac (n) PS** IBEG NONE
Mac (n+1) PS** DAD TCAL 55 999
Mac (n+2) PS** IEND NONE
• TCAL: indicates use of a transport layer call.

• GENERATOR field: the setting specified (in this case, 999) is used to specify a unique reference for
each X.25 call, which means that transport sessions can be resynchronized in the event of network
problems.
E Page 9-20
9.4.4 "Monitor" function of a transport link with backup
The main link handling the transport function is named NAME/xxxx and its LINK GROUP/ is greater
than the backup link.
The backup link for the transport link is named NAME/$xxx, and its LINE GROUP/ is at least 1.
The last three characters of the main link and backup link names are the same.
The NAME/ parts of the resources of the two links are similar.
When the main link goes down, the OSI class 3 transport protocol activates the reassignment on fault
procedure (network disconnection), and the Megapac performs the new routing procedure:
• It tries to set up a virtual circuit over the main link and, if it fails, it uses a resource of the backup link
(same name beginning with the character $).
When connections are set up on the backup link, the Megapac checks periodically to see whether a main
link has become operational again, provided it has the following characteristics:
NAME/xxxx The last three characters should match those specified with the NAME/ parameter of
the backup link.
LINE GROUP/y This value should be greater than that specified with the LINE GROUP/ parameter of
the backup link.
If it has, the backup link is restarted, clearing the virtual circuits backed up.
The OSI class 3 transport protocol activates the reassignment on fault procedure (network
disconnection).
The virtual circuits are therefore set up again on the main X.25 link resource, the characteristics of which
were given above.
E Page 9-21
E
9.4.4.1 Example
TRANSPORT BUFFERS/ 10
TRANSPORT BUFFERS/ 10
X25 table: MAC table:

Name AG. Address User data Name Function Options Selector Generator
P300 0 789* PST* IBEG
PST* DAD TCAL 789* TATA
PST* IEND
... ...
OPTIONS/ NONE OPTIONS/ ISO
NAME/ $ST3 NAME/ PST5
TYPE/ X25 TYPE/ X25
OPTIONS/ DCD OPTIONS/ DCD
... ...
LINE GROUP/ 1 EXTENDED CALL MANAGEMENT/ IN
... ...
TRANSPORT LEVEL TYPE/ ISO TRANSPORT LEVEL TYPE/ ISO
TRANSPORT CLASS/ 3 Backup WAN TRANSPORT CLASS/ 3
DEFAULT WINDOW SIZE/ 7 DEFAULT WINDOW SIZE/ 7
DISABLE FLOW CONTROL/ NO DISABLE FLOW CONTROL/ NO
TSAP FORMAR/ TEXT TSAP FORMAR/ TEXT
MAXIMUM TPDU SIZE/ 256 MAXIMUM TPDU SIZE/ 256
TTR TIME/ 15 TTR TIME/ 15
TWR TIME/ 30 TWR TIME/ 30
NAME/ P300
... NAME/ P400
OPTIONS/ NONE ...
OPTIONS/ ISO
NAME/ PST3 NAME/ PST4
TYPE/ X25 TYPE/ X25
OPTIONS/ DCD OPTIONS/ DCD
... ...
LINE GROUP/ 2 EXTENDED CALL MANAGEMENT/ IN
... ...
TRANSPORT LEVEL TYPE/ ISO Main WAN TRANSPORT LEVEL TYPE/ ISO
TRANSPORT CLASS/ 3 TRANSPORT CLASS/ 3
DEFAULT WINDOW SIZE/ 7 DEFAULT WINDOW SIZE/ 7
DISABLE FLOW CONTROL/ NO DISABLE FLOW CONTROL/ NO
TSAP FORMAR/ TEXT TSAP FORMAR/ TEXT
MAXIMUM TPDU SIZE/ 256 MAXIMUM TPDU SIZE/ 256
TTR TIME/ 15 TTR TIME/ 15
TWR TIME/ 30 TWR TIME/ 30

... ...
OPTIONS/ ISO OPTIONS/ NONE

TYPE/ all type TYPE/ all type
MEGAPAC 1 MEGAPAC 2
E
Called 789
Figure 9-2 Transport on main and backup link with monitoring
9.5 Resource configuration parameters

Name Settings
NAME Up to 4 alphanumeric Name of a logical resource.
characters
DRC MASK Up to 4 characters Fully or partly identifies a destination resource, used for non-
By default = . . . . automatic routing.
The ^ddd function of the DRC MASK is compatible with the LIST
function of the input MAC table.
TERMINAL TYPE By default = ASYN Identifies the terminal type.
ASYN Supports asynchronous terminals generating a call request using
the Megapac presentation mode.
VT22 Used in conjunction with an emulation service called by the NAME
table, this attribute specifies use of the VT220 screen display
format.
other The other attributes available (SYNC, MINI, X28, X28F, ANSI,
EXTA, MTRM, SLIP, BUF, TPAD) have no effect on a logical
resource of an X.25 descriptor.
CIRCUIT TYPE By default = Identifies the main I/O characteristics of the resource.
CALL+STAT
CALL This attribute enables the resource to send and receive call
requests transparently or via the presentation mode.
PVC This attribute specifies that the resource is a permanent VC.
Note : The DRC MASK parameter must be fully defined.
SVC Call request packets are switched transparently.
The presentation mode must be disabled.
OUT The logical resource is reserved for receiving an incoming call.
STAT Following a connection/disconnection, statistics are compiled and
sent to the resource defined by the SESSION STATISTICS/
parameter of the BASE descriptor (resource EI01 by default).
OPTIONS By default = NONE Level 3 operating options.
Various parameter settings can be aggregated for a given logical
channel.
By default, none of the specific level 3 operating options is
implemented.
XCHG reserved use (only on Megapac ESL and Megafrad)
RTS Does not concern X25 resource.
This option is unavailable on Megapac ESL and Megafrad.
BUSY The logical resource is held in the busy state for 30 seconds after
the call is cleared.
E Page 9-23
E
OPTIONS
(continued)
HOLD
PASS
The level 3 connection (packet) is not interrupted following a level

2 (frame) disconnection.
Used in conjunction with the TALK option, this attribute activates
password protection (defined in the PASS table) for incoming
calls.
The call is cleared if the correct password is not entered within 30
seconds.
BILL Any incoming call over this logical channel results in insertion of a
billing ticket (in the BILL table) when cleared.
See the SEGMENT ACCOUNTING/ parameter of the BASE
descriptor.
MSGS Service messages are sent to the caller over the logical channel
(UNAVAILABLE, BUSY, NO RESPONSE, etc.).
GATE This attribute activates password protection (defined in the PASS
table) for outgoing calls.
Having obtained a connection with the outgoing logical channel
but before sending the call over the WAN, the caller must enter
the appropriate password.
TALK All call requests are intercepted by the presentation mode.
SUPR Used in conjunction with the NAME option (see above), this
attribute activates the supervisor mode for routing by an operator.
NAME DRC MASK/ . . . .
The calling end specifies the routing by entering a service name (8
chars max). This name should match an entry in the NAME table.
DRC MASK/ ABCD
ABCD is interpreted as a service name. This name should match
an entry in the NAME table.
NAME+X28 Used only in conjunction with the NAME option, this attribute
activates support of the X.28 command syntax.
NO_M not used with X25 resource.
ISO This attribute activates the transport function for this resource.
DIAG This attribute activates the Cause and Diagnostic code recording
procedure in clear confirmation packets.
SNMP, TELR Does not concern X25 resource.
IDLE This attributes activates the timer specified in the INACTIVITY
DETECT TIMER/ parameter of the BASE descriptor.
NONE None of the options is implemented.
BUFFERS Setting from 1 to 240 Setting determining the total number of buffers that can be
By default = 2 used for transmitting input data before the receive mode
level 3 window is closed.
This figure is added to that defined by the K LEVEL3/ parameter
of the X.25 descriptor.
DISC MODE Setting from 0 to 32 This parameter does not apply to an X.25 "resource".
By default = 0
E Page 9-24
E
MENU NUMBER
By default = 0
Setting from 0 to 32 Number of the MENU record to be displayed to the caller in

presentation mode.
If the setting is (0), no MENU is displayed.
HELP NUMBER Setting from 0 to 32 If the OPTIONS/ NAME parameter is set, the number of the
By default = 0 HELP screen to be displayed to the caller in presentation
mode.
If the setting is 0, no HELP screen is displayed.
NEWS NUMBER Setting from 0 to 32 Number of the MENU record to be displayed on a connection
By default = 0 request on an outgoing channel incapable of handling the
call request as a result of a link fault.
Note : A clear confirmation immediately follows transmission of
the MENU.
CALL PRIORITY Setting from 0 to 15 Calling line priority (CP >= RP).
By default = 0
RESOURCE Setting from 0 to 15 Called line priority.
PRIORITY By default = 0
BANDWIDTH Setting from 0 to Required bandwidth, in characters per second tenth.

32767 incoming resource:
By default = 0 Bandwidth=0, no guaranteed bandwidth is required.
Bandwidth>0, to define the required bandwidth before routing.
This value can be canceled by use of the THRU option of the input
MAC table.
outgoing resource:
Bandwidth=0, the throughput assigned to the resource depends on
the required throughput of the incoming resource.
Bandwidth>0, the throughput assigned to the resource is limited to
the bandwidth indicated.
PAD ENABLE By default = D Pseudo-PAD function operating options.
MINI Minitel.
X28F Defines an X.28 logical resource with messages in French.
E Activates the pseudo-PAD function. In presentation mode, the
caller receive a MENU followed by a qualified data packet
containing the PAD parameters configured for the resource.
E+REV This attribute activates the reverse PAD mode. When a
connection request is drawn up in output mode, a qualified data
packet containing the PAD parameters configured for the
resource is sent. See also the PROF attribute.
E+PROF For an incoming call using the presentation mode, the incoming
resource name corresponds to a Profile defined in the PROF
table.
The duly selected profile is sent to the caller in a "qualified" data
packet.
E+MASK The PAD parameters are "masked" selectively by the mask
previously set in the MAC table.
D The logical resource does not send X.29 packets and does not
respond to those it receives.
The other parameters displayed are associated with the Megapac's PAD function.
Refer to "PAD parameters".
E Page 9-25
E
9.6 Input MAC table (X.25)
When the link descriptor's "EXTENDED CALL MANAGEMENT" parameter is set to "IN", the MAC table
is used in input mode.
9.6.1 "CAD, DAD, CUD, FAC" function
The functions listed below enable various processes on the call request packet:
CAD Caller's ADdress Calling DTE address.
DAD Destination ADdress Called DTE address.
CUD Call User Data Call user data.
FAC FACilities Facilities.

Lxxx CAD NONE Calling DTE address Destination resource,
DAD Called DTE address or name of LIST (^xxx).
CUD Call use data
FAC Facilities
Lxxx REJ Cause/diagnostic
Lxxx TLAT Destination resource
Lxxx TCAL Destination resource
Lxxx TALK
Lxxx BILL Destination resource
Ref. 0 JUMP Ref. 1*
Ref. 1, Ref. 2*
Ref. 1, Ref. 2, Ref. 3
Lxxx ISO Destination resource
Lxxx ISO+Y13 Destination resource
Lxxx EXPE Destination resource
Lxxx CAD Source logical resource
Lxxx THRU Default throughput class
Lxxx COPY Destination resource, character
COPY+NOT string, character string.
Lxxx COPY Destination resource, character

string, Character string
Lxxx TALK Service name
Lxxx FLAG Destination resource, character
string, character string
* The jump reference is applied also to the COPY and FLAG options.
It then replaces the name of an outgoing logical resource.
E Page 9-26
E
NAME
Link descriptor name, linked with the input MAC program.
FUNCTION The SELECTOR field is compared with the:

• "Calling DTE address" field for the CAD function.
• "Called DTE address" field for the DAD function.
• "Call user data" field for the CUD function.
• "Facilities" field for the FAC function.
SELECTOR Comparison of the call request packet data and the SELECTOR field results in:
Validation OK, processing of the input MAC record continues. The content the
OPTION field is analyzed.
Validation not OK, the input MAC record is disregarded. The next input MAC record is
taken into account.
Note:
When the JUMP option is specified, non-validation of the content of the SELECTOR
field and the call request packet data does not necessarily mean that the input MAC
record is disregarded.
GENERATOR This field contains:

• "cause/diagnostic" codes, or
• the name of a logical resource, or a name of LIST (^xxx), or
• one or more references, each identifying an input MAC record, or
• a default throughput class assigned to the input link, or
• a character string (with or without special characters +, # and or ”).
This may be preceded by the name of an outgoing logical resource, and must be
followed by the comma, or
• a service name associated with a NAME record.
E Page 9-27
E
OPTIONS:
NONE
The call request packet is routed to the logical resource indicated by the GENERATOR
field.
REJ A clearing packet is returned to the caller. The "cause/diagnostic" fields contain the
codes indicated in the GENERATOR field.
TLAT The call request packet is reconstructed in the X.25 table. It is then routed to the X.121
address associated with the resource name and corresponding to the content of the
GENERATOR field.
The Facilities and Call User Data fields are not kept. The outgoing MAC table (MAC -
OUT) can be used to reconstruct the Facilities and Call User Data fields of the call
packet.
TCAL The established virtual circuit supports one or more transport connections.
The called transport entity uses an X.25 network.
The transport connection is set up using the destination transport group name specified
in the GENERATOR field.
This name conditions direct routing to the logical resource concerned.
TALK When the GENERATOR field is blank, the call request packet is subject to presentation
mode.
When the GENERATOR field contains a service name, the Megapac automatically
selects PAD TELNET emulation, the PROF option and ICL 7561 emulation using the
NAME table.
BILL Each virtual circuit set up is subject to billing.
JUMP The content of the GENERATOR field is analyzed.
The following situations can apply:
The GENERATOR field contains a unique reference.
If prior validation is OK, the input MAC record associated with the reference is counted.
If the previous validation is not OK, the input MAC record associated with the reference
is disregarded.
The GENERATOR field contains "Ref. 1, Ref. 2".
If the previous validation is OK, the input MAC record associated with "Ref. 1" is
counted.
If the previous validation is not OK, the input MAC record associated with "Ref. 2" is
counted.
The GENERATOR field contains "Ref. 1, Ref. 2, Ref. 3".
If the previous validation is OK, the input MAC record associated with "Ref. 1" is
counted.
If the previous validation is not OK, there are two possibilities:
1. when the selected data (CAD, DAD, CUD, FAC) in the call request packet has a
setting greater than that of the SELECTOR field, the input MAC record associated
with "Ref. 3" is counted.
2. when the selected data (CAD, DAD, CUD, FAC) in the call request packet has a
setting less than that of the SELECTOR field, the input MAC record associated with
"Ref. 2" is counted.
E Page 9-28
E
ISO
The virtual circuit set up supports a class 3 ISO transport connection. This can be used
to implement the reassignment on fault procedure following disconnection at the
"network" level.
The TSAP of the calling entity corresponds to the logical resource name conveying the
The TSAP of the called entity corresponds to the logical resource name specified in the
GENERATOR field of the input MAC record.
Note:
You can use a logical resource name (TSAP of the called entity) with the following
format: “^xxx”.
However, this does require prior implementation of the corresponding "LIST" MAC
function (routing with a DRC MASK).
ISO+Y13 Call request packet information is placed in the "call user data" field of the connection
request TPDU in class 2 or 3 transport mode.
EXPE The virtual circuit set up supports a class 2 or 3 ISO transport connection, with use of
the "expedited data" service.
CAD The X.121 address associated with the source logical resource name of the
GENERATOR is inserted in the "calling DTE address" field of the call request packet.
THRU The default throughput class defined in the GENERATOR is assigned to all virtual
circuits using the incoming link.
In practice, this is the maximum throughput class allowed in each direction of
transmission.
Execution of THRU takes priority over other options set.
COPY All or some of the data selected (CAD, DAD, CUD, FAC) in the call request packet is
transferred into the buffer associated with the X.121 address field of the X.25 table,
used to modify the called DTE address.
At the outset, an origin pointer is located on the first character of the selection and a
target pointer on the first position of the buffer.
#X advances the origin pointer by X half-bytes (hex).
Only the data ahead of this position is transferred.
+Y advances the target pointer by Y half-bytes (hex).
The data transferred is buffered from this resulting position.
Information located behind in the buffer remains unchanged.
“Z transfers Z half-bytes (hex) from the selection. After the transfer, the origin and
target pointers are advanced by Z half-bytes (hex).
Data to which the COPY option is applied is processed in bytes (hex).
FLAG The character string defined in the GENERATOR field is logically added (logical OR
operation) to the content of the binary flags buffer, beginning with the leftmost position
of that buffer.
COPY+CAD Identical to CAD option, with handling means of COPY option.
This double option is used to modify the calling DTE address.
COPY+NOT Similar to the COPY option, but the called DTE address is modified only in the call
confirmation packet in extended format.
E Page 9-29
9.6.1.1 Example (CAD function and COPY Options)
take, for example, the following input MAC program:

1 PS02 IBEG NONE
2 PS02 CAD COPY 987654321 RESS,#3"288"4
3 PS02 IEND NONE
1 Input MAC program entry point.

2 The content of the "calling DTE address" field of the call request packet is compared with the value
987654321 specified in the SELECTOR field.
There is a match. The content of the OPTION field is analyzed, COPY is specified.
The call is routed to destination resource RESS and the call request packet sent includes a change of called
DTE address, as follows:
The starting base is the calling DTE address (CAD function).
#3 delete 3 digits (987),
"2 retain 2 digits (65),
88 insert 88,
the called DTE address becomes 65884321.
3 Input MAC program exit point.
On link PS02, the call confirmation packet sent is in the basic or extended format, according to the
setting chosen (EXT absent or included) for the link's OPTION parameter.
OPTION parameter Call confirmation packet information sent (link PS02)

EXT absent The call confirmation packet sent is in basic format (3 bytes, no called, calling address
field, etc).
EXT present The call confirmation packet sent is in extended format, and the called and calling address
DCE mode of the call request packet is copied into the call confirmation packet.
EXT present The call confirmation packet sent is in extended format, but the called and calling address
DTE mode fields are empty to ensure connection to the Transpac network.
E Page 9-30
9.6.1.2 Example (CAD function and COPY+CAD Options)

1 PS02 IBEG NONE
2 PS02 CAD COPY+CAD 987654321 RESS,#3"288"4
3 PS02 IEND NONE

2 The content of the "calling DTE address" field of the call request packet is compared with the value
There is a match. The content of the OPTION field is analyzed, COPY+CAD is specified.
The call is routed to destination resource RESS, and the call request packet sent includes a change of
calling DTE address as follows:
The starting base is the calling DTE address (CAD function),
#3 delete 3 digits (987),
88 insert 88,
the calling DTE address becomes 65884321.
On link PS02, the call confirmation packet sent is in basic or extended format, according to the setting
chosen (EXT absent or included) for the link's OPTION parameter.

EXT absent The call confirmation packet sent is in basic format (no called and calling address fields).
EXT included The call confirmation packet sent is in extended format, and the called and calling address
of the call request packet is copied into the call confirmation packet.
E Page 9-31
9.6.1.3 Example (DAD function and COPY+NOT Options)

1 PS02 IBEG NONE
2 PS02 DAD COPY+NOT 123456789 RESS,#3"244"4
3 PS02 IEND NONE

2 The content of the "called DTE address" field of the call request packet is compared with the value
There is a match. The content of the OPTION field is analyzed, COPY+NOT is specified.
The call is routed to destination resource RESS and the call request packet sent is not modified.
On link PS02, the call confirmation packet sent is in basic or extended format, according to the setting
chosen (EXT absent or present) for the link's OPTION parameter.

EXT absent The call confirmation packet sent is in basic format (no called and calling address fields).
EXT included The call confirmation packet sent is in extended format and the calling and called address
are modified as below :
• the calling address of the call request packet is not copied into the call confirmation
packet,
• the called address 123456789 of the call request packet is changed as follows:
the starting base is the called DTE address (DAD function).
#3 delete 3 digits (123)
"2 retain 2 digits (45)
44 insert 44
"4 retain 4 digits (6789)
• the called DTE address in the call confirmation packet becomes 45446789 and the
calling address field is empty.
E Page 9-32
9.6.1.4 Example (CAD function and REJ, TLAT, TCAL Options)

1 PS02 IBEG NONE
2 PS02 CAD NONE 1∗ PSAU
3 PS02 CAD REJ 2∗ Cause / Diagnostic
4 PS02 CAD TLAT 3∗ PSAI
5 PS02 CAD TCAL 4∗ PSAT
6 PS02 IEND NONE

2 The content of the "calling DTE address" field of the call request packet is compared with the
setting 1* of the SELECTOR field.
There is no match. Record 2 is disregarded.
There is a match. The content of the OPTION field is analyzed. REJ was specified. A clear
packet in which the "cause/diagnostic" fields match the content of the GENERATOR field is sent
in return to the caller.
There is a match. The content of the OPTION field is analyzed. TLAT was specified. The
content of the GENERATOR field (PSAI) provides access to the PSAI record of the X.25 file.
After reconstructing the call request packet where necessary, the call is routed to the associated
X.121 address.
There is a match. The content of the OPTION field is analyzed. TCAL was specified. The
content of the GENERATOR field (PSAT) indicates a logical resource belonging to an ILAN link
descriptor.
The PSAT record of ILAN file is accessed.
Double routing is implemented:
1. to an ETHERNET MAC destination (level 2) using the ETHERNET ADDRESS field,
2. to a called transport entity (level 4) using the TSAP field.
E Page 9-33
9.6.1.5 Example (CAD function and JUMP option)

1 Lxxx IBEG NONE
2 4001 CAD JUMP 34 4002, 4006, 4004
3 4002 CAD NONE 34 RSL1
6 Lxxx IEND NONE

2 First hypothesis:
In the call request packet, the content of the "calling DTE address" field is 34.
The content of the SELECTOR field of record 2 validates this setting.
Record 3, associated with reference 4002, is counted.
Second hypothesis:
This setting is greater than that of the SELECTOR field of record 2.
Third hypothesis:
This setting is less than that of the SELECTOR field of record 2.
3 The content of the SELECTOR field of record 3 validates that of the "calling DTE address" field
(first hypothesis) in the call request packet.
Routing takes place over logical resource RSL1.
(second hypothesis) in the call request packet.
(third hypothesis) in the call request packet.
E Page 9-34
9.6.1.6 Example (CUD function and REJ, TALK, TLAT Options)

1 PS02 IBEG NONE
2 PS02 CUD NONE ∗42!44 PSAU
3 PS02 CUD REJ !!!!4E4F4E Cause / Diagnostic

4 PS02 CUD TALK 0100000050524553
5 PS02 CUD TLAT 01000000534154 PSAT
6 PS02 IEND NONE

2 The content of the "call user data" field of the call request packet is compared with the setting
*42!44 (syntax character - hex character - syntax character - hex character) of the SELECTOR
field.
There is no match. Record 2 is disregarded.
!!!!4E4F4E (4 syntax characters - "NO" in hex) of the SELECTOR field.
There is a match. The content of the OPTION field is analyzed. REJ is specified.
A clear packet with the "cause/diagnostic" fields corresponding to the content of the
GENERATOR field is returned to the caller.
0100000050524553 (X.29 protocol identifier - "PRES" in hex) of the SELECTOR field.
There is a match. The presentation mode is selected.
5 The content of the "Call user data" field of the call request packet is compared with the setting
01000000534154 (X.29 protocol identifier - "SAT" in hex) of the SELECTOR field.
There is a match. The content of the OPTION field is analyzed. TLAT is specified.
The content of the GENERATOR field (PSAT) provides access to the PSAT record of the X.25
file.
After reconstructing the call request packet where necessary, the call is routed to the associated
X.121 address.
E Page 9-35
9.6.1.7 Example (FAC function, THRU option)

1 ENTR IBEG NONE
2 ENTR FAC THRU 00029B 9600
3 ENTR IEND NONE

2 The content of the "Facilities - X.25 type" field of the call request packet is compared with the
setting 00029B of the SELECTOR field of the FAC record.
00029B respectively corresponds to the type of facilities (00 = X.25), the facility code (02 =
throughput class negotiation), the "transmission from called DTE" parameter (9 = 4800 bps), and
finally the "transmission from calling DTE" parameter (B = 19200 bps).
There is a match. The THRU option is counted.
The content of the GENERATOR field then represents the default throughput class (9600 bit/s),
assigned to the input link ENTR. This is, in practice, the maximum throughput class allowed on
the ENTR link for each direction of transmission.
Notes:
• In the SELECTOR field, the facility type marker must be specified.
Remember that "00" corresponds to the "X.25" type and "0F" the "OSI-DTE" type.
• In the SELECTOR field, the facility code is optional.
• In the SELECTOR field, any byte (2 hex characters) in the "parameters" field can be replaced by "!".
• In the SELECTOR field, with regard to the category D facilities, the facility code is immediately
followed by a byte indicating the length (in bytes) of the "facility parameters" field.
E Page 9-36
9.6.1.8 Example (FAC function, FLAG option)

1 LIAE IBEG NONE
... LIAE ... ... ... ...
2 LIAE FAC FLAG 000304,08,09 RESS,000007,04,0501
3 LIAE IEND NONE

... First, assume that the content of the "exchange buffer" contains 40002004 hex.
2 In the "X.25 facilities" field of the input call request packet, a search is performed to determine
whether code 0003 (choice of CUG) is included.
If it is, the FAC record is counted, and routing takes place over the "destination" resource RESS.
The following situations can then apply:
• if CUG is set to 04, 000007 is logically added (logical OR operation) to the "binary flags"
buffer, which becomes 40002704 hex.
• if CUG is set to 08, 04 is logically added (logical OR operation) to the content of the "binary
flags" buffer, which becomes 44002004 hex
• if CUG is set to 09, 0501 is logically added (logical OR operation) to the content of the "binary
flags" buffer, which becomes 45012004 hex.
Note:
• In the SELECTOR field, the facility type marker must be specified.
Remember that "00" corresponds to the "X.25" type and "0F" to the "OSI-DTE" type.
"Exchange buffer":
The "Exchange buffer" is a 4-byte buffer (32 bits).
It is used to exchange information between a "Source Resource - Destination Resource" pairing.
The exchange buffer is set to (00000000) at the start of the input MAC program.
E Page 9-37
9.6.2 Analysis of "Cause and Diagnostic"
9.6.2.1 Example (ELSE function and TLAT, REJ Options)

Lxxx ELSE NONE Cause/Diagnostic Logical resource
Lxxx TLAT Cause/Diagnostic Logical resource
Lxxx REJ Cause/Diagnostic Cause/Diagnostic (forced)
NAME Name(s) of the link descriptor or descriptors, linked with the input MAC program.
FUNCTION Same as for the above input MAC record. So:
• called DTE address, when it is a DAD function,
• calling DTE address, when it is a CAD function,
• call user data, when it is a CUD function,
• facilities, when it is an FAC function.
SELECTOR When routing fails, as specified in the previous input MAC record, the content of the SELECTOR
field is analyzed.
If it matches the content of the "Cause/diagnostic" fields of the clearing packet, the ELSE record
is counted.
The Cause/Diagnostic format (in hex and uppercase) may be:
(space) unconditional execution
CCDD content of the Cause and Diagnostic field
CC or CC∗ content of the Cause field; the content of the Diagnostic field disregarded
∗DD content of the Diagnostic field; the content of the Cause field disregarded.
NONE OPTION The incoming call request packet is routed to the logical resource indicated by the GENERATOR
field.
1. The logical resource is available.
The incoming call request packet is transmitted.
2. The logical resource is not available.
A clearing packet is returned to the caller.
The content of the "cause/diagnostic" fields is analyzed. This analysis triggers execution of the
next ELSE function, where appropriate.
TLAT OPTION The call request packet is reconstructed in the X.25 table. The Facilities and Call User Data
fields are not kept. The outgoing MAC table (MAC - OUT) can be used to reconstruct the
Facilities and Call User Data fields of the call packet.
There are then two possibilities:
1. The content (reconstructed) of the call request packet field is validated and the logical
resource is available.
The call request packet is then transmitted.
2. The content (reconstructed) of the call request packet field is not validated and the
logical resource is/is not available.
A clearing packet is transmitted to the caller.
The content of its "cause/diagnostic" fields is analyzed, triggering execution of the next ELSE
function, where appropriate.
OPTION REJ The incoming call is unconditionally rejected;
1. with the Cause/Diagnostic received when the GENERATOR field is empty.
2. with a forced Cause/Diagnostic (that of the GENERATOR field).
E
GENERATOR Name of a logical resource or Cause/Diagnostic forced with the REJ option.
9.6.2.2 Example (DAD, ELSE function and TLAT option)
Take for example the following input MAC program:

1 PS02 IBEG NONE
2 PS02 DAD NONE 5∗ PSAU
3 PS02 ELSE NONE Cause / Diag PSIA

4 PS02 ELSE TLAT Cause / Diag PSAU
5 PS02 DAD TLAT 7∗ PSKL
6 PS02 IEND NONE
2 Execution of the DAD function (called DTE address) results in failure.

The "cause/diagnostic' fields of the clearing packet returned are analyzed.
There is a match with the "cause/diagnostic" codes stipulated in the SELECTOR field of record 3
(ELSE function). Record 3 is processed.
3 The same function (DAD) is again activated, but the content of the OPTION, SELECTOR and
GENERATOR fields may have been modified.
So, the GENERATOR field contains a new logical resource name (PSIA).
Execution of this DAD function again results in failure.
The "call/diagnostic" fields of the clearing packet returned are analyzed.
4 The same function (DAD) is again activated, but the content of the OPTION, SELECTOR and
GENERATOR field may have been changed.
So, the OPTION field contains TLAT.
The content of the "called DTE address" field of the call request packet is reconstructed in the
X.25 file.
The GENERATOR field again contains PSAU.
This time the reconstructed call request packet is transmitted over logical resource PSAU.
5 Another DAD function is executed.

Important note:
In the event of failure, the call request packet cannot be routed and/or reconstructed.
In practice, record 5 is not followed by a record with an ELSE function.
E Page 9-39
9.6.2.3 Example (DAD, ELSE function and TLAT, REJ Options)

1 PS01 IBEG NONE
2 PS01 DAD NONE 10030206 P200
3 PS01 ELSE TLAT 0900 P300
4 PS01 ELSE REJ ∗ FE00
5 PS01 IEND NONE
2 Calls received on PS01 with the destination address 10030206 are routed to resource P200.
Execution of the DAD function (called DTE address) results in failure.
The "cause/diagnostic" fields of the clearing packet returned are analyzed.
If the cause/diagnostic is 0900, record 3 is processed.
If the cause/diagnostic is other than 0900, record 4 is processed.
3 The same function (DAD) is again activated.

An alternative standby routing is performed to resource P300 with the called DTE address
translated in the X.25 table.
4 The call received on PS01 is unconditionally rejected with the cause FE and the diagnostic 00.
E Page 9-40
9.6.2.4 Example (LIST, ELSE functions and TLAT, REJ Options)

1 ^LS1 LIST NONE P200
2 ^LS1 ELSE NONE 0900 P300
3 ^LS1 ELSE TLAT 0A00 P400
4 ^LS1 ELSE REJ ∗ FE00
5 PS01 IBEG NONE

6 PS01 DAD NONE 10030206 ^LS1
7 PS01 IEND NONE
5 PS01 link MAC program entry point.

6 Calls received on PS01 with the destination address 10030206 refer to list LS1.
The MAC table is scanned from the beginning searching for a NAME = ^LS1.
7 PS01 link MAC program exit point.
1 Calls received on PS01 with the destination address 10030206 are routed to resource P200.
Execution of the DAD function (called DTE address) results in failure.
If the cause/diagnostic is 0900, record 2 is processed.
If the cause/diagnostic is 0A00, record 3 is processed.
If the cause/diagnostic is different, record 4 is processed.
An alternative standby routing is performed to resource P300.
The "cause/diagnostic" fields of the returned clearing packet are analyzed.
If the cause/diagnostic is 0A00, record 3 is processed.
If the cause/diagnostic is different, record 4 is processed.
An alternative standby routing is performed to resource P300 with the called DTE address
translated in the X.25 table.
4 The call received on PS01 is unconditionally rejected with the cause FE and the diagnostic 00.
E Page 9-41
9.6.3 Mask on X3 parameters, "MASK" function
This function is linked to the use of PAD ENABLE = E+MASK.

XXXX MASK NONE Series of "D" and/or "E"
characters
NAME Logical resource name.

FUNCTION Selective deactivation of X.3 parameters, conveyed in an X.29 "set" or "set and read" packet.
SELECTOR String of "D" and/or "E" characters.
The position occupied by a "D" or "E" character conditions disabling or enabling respectively
of the relevant X.3 parameter.
GENERATOR This field is not used.
9.6.3.1 Example "MASK"

RLS1 MASK NONE EEEDDEEEEEEEEEEE
In an X.29 "set" or "set and read packet", the logical resource RLS1, the following X.3 parameters are
disabled:
• Parameter 4 (Data forwarding delay).
• Parameter 5 (Control of the start/stop mode DTE by the PAD).
All the remaining X.3 parameters can be enabled.
E Page 9-42
E
9.7 Output MAC table (X25)
9.7.1 Filtering on the calling DTE address
When the "EXTENDED CALL MANAGEMENT" parameter of the link descriptor is set to "OUT", the
MAC table is used for output.
ECM = OUT, with "CAD" records can be used to enable or prevent access to the output resources from a
calling line (Calling DTE address).
The output MAC table can have one or more records with the CAD function. These records specify the
calling DTE addresses that are allowed to use the selected destination resource.

Lxxx OBEG NONE
Lxxx CAD NONE calling address allowed
* and ! are allowed
Lxxx OEND NONE
The "CAD" records for filtering calling addresses should be placed immediately after the start record
(OBEG).
A number of "CAD" records can be strung together.
In a set of a filtering "CAD" records, an "NOP" record is not allowed.
E Page 9-43
9.7.2 Structure of the output MAC table
9.7.2.1 Only in filtering mode
In this case, the structure is as follows:
NAME FUNCTION OPTION SELECTOR GENERATOR use

Lxxx OBEG NONE
Lxxx CAD NONE calling address allowed filtering
Lxxx OEND NONE
9.7.2.2 Only in "Facility Data" and "Call User Data" handling
In this case, there is no filtering on the calling address, and the structure is as follows:

Lxxx OBEG NONE
Lxxx NOP NONE separator
Lxxx INSE NONE handling
Lxxx COPY NONE handling
Lxxx DATA NONE handling
Lxxx OEND NONE
9.7.2.3 Filtering and data handling use combined
In this case, the structure is as follows:

Lxxx OBEG NONE
Lxxx NOP NONE separator
Lxxx INSE NONE handling
Lxxx COPY NONE handling
Lxxx DATA NONE handling
Lxxx OEND NONE
E Page 9-44
9.7.3 "Facility Data" and "Call User Data" handling
When the ECM parameter of the link descriptor is set to OUT, the MAC table is used in output mode.
ECM = OUT is used to handle:
• "facility data",
• "call user data".
For data handling purposes, it is important for a record in the X.25 table to indicate that "translation" is
required. The "T" indicator should be specified.
A "translation" can also be requested through an input MAC program including a record with the "TLAT"
option.
When "translation" is requested, the following processing options are available:
ECM is not OUT The "facility data" and "call user data" are not modified, and are
transmitted transparently.
ECM = OUT The "facility data" and "call user data" are deleted.
No output MAC program
ECM = OUT The "facility data" and "call user data" are modified or reconstructed
Output MAC program according to the output MAC program.
An output MAC program can include the following "FUNCTIONS":
FUNCTION Meaning
OBEG Start of output MAC program.
INSE
COPY The functions are used to manipulate the "facility data".
DELE These functions must be followed by a record with the EOF or DATA function.
POSN
MARK
EOF This function specifies the end of "facility data" handling, and terminates processing with
no "call user data" inserted.
DATA and field This function specifies the end of "facility data" handling and terminates transparent
GENERATOR empty processing for the "call user data".
DATA and field This function specifies the end of "facility data" handling and terminates the process by
GENERATOR = xyz inserting the "call user data" specified in the GENERATOR field.
OEND End of output MAC program.
E Page 9-45
E
9.7.3.1 "POSN" function
NAME FUNCTION
OPTIONS SELECTOR GENERATOR

Lxxx POSN NONE DEST Second byte of a marker delimiting
DEST, SRCE the start of a facility type (hex).
space
DEST = Destination logical resource.

SRCE = Source logical resource.
NAME Names of the link descriptors linked with the output MAC program.
FUNCTION In an incoming call request packet, positions the output MAC logic at the start of a facility
type (X.25, ISO-DTE).
SELECTOR Conditional execution of the POSN function. The following situations can apply:
No information is specified.
The POSN function is executed regardless of the names of the source and destination logical
resources used.
The name of a destination logical resource is specified.
The POSN function is executed when the name of the destination logical resource used
matches the name defined in the SELECTOR field.
The names of both destination and source logical resources are specified.
The POSN function is executed when the names of the destination and source logical
resources used respectively match the names defined in the SELECTOR field.
GENERATOR This field contains two hex characters representing the second byte of a marker, marking the
start of a facility type. The following characters can be specified:
00 = Position at start of "X.25" facility type.
OF = Position at start of "ISO-DTE" facility type.
Note
Positioning at the start of a facility type is accompanied by reinitialization (resetting) of all
masks associated with that type.
E Page 9-46
9.7.3.1.1 Example « POSN function »

Take, for example, the following output MAC program:

1-1 Lxxx OBEG
1-2 Lxxx POSN NONE 00
1-3 Lxxx OEND
2-1 Lxxy OBEG
2-2 Lxxy POSN NONE RDES FC
2-3 Lxxy OEND
3-1 Lxyy OBEG
3-2 Lxyy POSN NONE RESD, RESS 0F
3-3 Lxyy OEND
1-1 Output MAC program entry point, for link Lxxx.

1-2 No validation is carried out on names of source and destination logical resources used respectively by the
incoming and outgoing call request packets.
The output MAC logic is positioned at the start of the "X25" facility type.
This positioning determines the scope of the subsequent COPY, INSE, DELE records, in sequence.
All masks associated with the X.25 type are reset to 0.
1-3 Output MAC program exit point, for link Lxxx.
2-1 Output MAC program entry point, for link Lxxy.

2-2 Validation is carried out on the name of the destination logical resource used by the outgoing call request
packet.
1. The name of the destination logical resource matches the RDES.
Processing of record N° 2-2 continues.
2. The name of the destination logical resource does not match RDES.
Record N° 2-2 is disregarded and record N° 2-3 is counted.
"FC" does not match the second byte of a "facility" type marker so the output MAC logic is positioned at the
start of the "call user data" field, where appropriate.
2-3 Output MAC program exit point, for link Lxxy.
E Page 9-47
E
3-1
3-2
Output MAC program entry point, for link Lxyy.

Validation is carried out concerning the names of the source and destination logical resources used
respectively by the incoming and outgoing call request packets.
1. The names of the source and destination logical resources respectively match RESS and RESD.
2. A source and/or destination logical resource name does not match RESS and/or RESD.
Record N° 3-2 is disregarded. Record N° 3-3 is counted.
The output MAC logic is positioned at the start of the "ISO-DTE" facility type.
This positioning determines the scope of the subsequent COPY, INSE, DELE records, in sequence.
All masks associated with the "ISO-DTE" type are reset to 0.
3-3 Output MAC program exit point, for link Lxyy.
"X.25"
marker
{ 0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0 "X.25" masks
256 inputs (32 bytes)

"X.25"
facilities
"ISO-DTE"
marker { 0
0
0
0
0
0
0
0
0
1
0
1
0
1
0
1
"ISO-DTE" masks
"ISO-DTE" facilities 256 inputs (32 bytes)
Figure 9-3 Structure of the "facilities" field
E Page 9-48
E
9.7.3.2 "INSE" function

Lxxx INSE NONE DEST Facility code followed by:
DEST, SRCE - one or more pairs of hex
DEST, character string, characters, or
character string, etc - a number of hex character strings,
DEST, SRCE, character separated from each other by
string, character string, etc commas.

NAME Name(s) of the link descriptor(s) linked with the output MAC program.
FUNCTION Inserts a code and one or more associated parameters in the "facilities" field of an outgoing call
or request packet.
SELECTOR Conditional execution of the INSE function.
The following situations can arise:
The INSE function is executed regardless of the names of the source and destination logical
resources used.
The name of a destination resource is specified.
The INSE function is executed when the name of the destination logical resource used matches the
name defined in the SELECTOR field.
The names of destination and source logical resources are specified.
The INSE function is executed when the names of the "destination" and "source" logical resources
used respectively match the names defined in the SELECTOR field.
The name of a destination resource is followed by a hex character string (maximum 4 bytes).
The INSE function is executed when:
• the name of the "destination" resource used by the call request packet is the same as that of
the SELECTOR field.
• at least one character string in the SELECTOR field matches the content of the "binary flags"
buffer associated with the input MAC program concerned.
The source and destination resource names are followed by a hex character string
(maximum 4 bytes).
The INSE function is executed when:
• the names of the "destination and source" resources used by the call request packet
respectively match those of the SELECTOR field,
• at least one character string in the SELECTOR field matches the content of the "binary flags"
buffer associated with the input MAC program concerned.
E Page 9-49
E
GENERATOR
•
This field contains two hex characters, representing the facility code to be inserted, followed by:
one or more pairs of hex characters, indicating the parameter setting or settings to be inserted,
or
• a series of hex character strings, each associated with parameter settings. These settings are
inserted only when the corresponding character strings in the SELECTOR field validate the
content of the "binary flags" buffer associated with the input MAC program concerned.
Notes
Insertion of a "facility" code, sets the mask for that facility to 1.
Consequently, before inserting a code and one or more "facility" parameters, the associated mask is
scanned.
If the mask is set to 1, the INSE function is not executed.
E Page 9-50
9.7.3.2.1 Example 1 (INSE function)


1 Lxxx OBEG
2 Lxxx INSE NONE 02AA
3 Lxxx INSE NONE RSDE 420707
4 Lxxx INSE NONE RSDE, RSDS 430707
5 Lxxx INSE NONE RSDE 02CA
6 Lxxx OEND
1 Output MAC program entry point.

2 No validation is carried out concerning the names of the source and destination resources used respectively
by the incoming and outgoing call request packets.
Assume that the output MAC logic is positioned at the start of the "X.25" facilities type.
The "facilities - X.25 type" field of the outgoing call request packet has inserted in turn:
• "02", corresponding to the "Throughput class negotiation" facility code.
• "AA", respectively corresponding to the "Throughput class (called DTE to network) = 9600 bit/s" and
"Throughput class (calling DTE to network) = 9600 bit/s" parameters.
The mask for code 02 is set to 1.
3 Validation is carried out for the name of the destination resource used by the outgoing call request packet.
1. The destination logical resource name matches RSDE.
Processing of record N° 3 continues.
2. The destination logical resource name does not match RSDE.
Record N°4 is counted.
Assume that the output MAC logic is positioned at the start of the "X.25" facility type field.
The "facilities - X.25 type" field of the outgoing call request packet has inserted, in turn:
"42", corresponding to the "Default non standard packet size" facility code.
"07", corresponding to the "packet size (called DTE to network) = 128" parameter.
"07", corresponding to the "packet size (calling DTE to network) = 128" parameter.
E Page 9-51
E
4
Validation is carried out on the names of the source and destination resources used respectively by the
1. The source and destination resource names match RSDS and RSDE.
The processing of record N° 4 continues.
2. A source and/or destination resource name does not match RSDS and/or RSDE.
Record N° 5 is counted.
Assume that the output MAC logic is positioned at the start of the "X.25" facility type.
• "43", corresponding to the "Default non standard window size" facility code.
• "07", corresponding to the "window size (called DTE to network) = 7" parameter.
• "07", corresponding to the "window size (calling DTE to network) = 7" parameter.
5 Validation is the same as for record N° 3.
However, the mask for code 02 is already set to 1. Consequently, the INSE function cannot be executed
and record N° 5 is disregarded.
6 Output MAC program exit point.
E Page 9-52
9.7.3.2.2 Example 2 (INSE function)


1 Lxxx OBEG
2 Lxxx INSE NONE RSDE,RSDS,000007,04,0501 0304,08,09
3 Lxxx OEND

2 First, assume that the content of the "binary flags" buffer for the input MAC program concerned is
40002704 hex.
The names of the destination and source resources used by the call request packet respectively match
RSDE and RSDS in the SELECTOR field.
The INSE record is therefore counted and its analysis is continued.
A first comparison is carried out between the character string 0000007 in the SELECTOR field and the
content 40002704 of the "binary flags" buffer.
There is match, so the CUG setting 04 in the GENERATOR field is stored.
A second comparison is carried out between the character string 04 in the SELECTOR field and the content
40002704 of the "binary flags" buffer.
There is no match, so the CUG setting 08 in the GENERATOR field is disregarded.
A third comparison is carried out between the character string 0501 in the SELECTOR field and the content
40002704 of the "binary flags" buffer.
There is no match, so the CUG setting 09 in the GENERATOR field is disregarded.
• "03", corresponding to the "choice of CUG" facility code.
• "04", respectively corresponding to the first and second digits of the CUG.
E Page 9-53
E
9.7.3.3 "DELE" function
NAME FUNCTION

Lxxx DELE NONE DEST Facility code (hex).
DEST, SRCE
space

FUNCTION Deletes a code and one or more associated parameters from the "facilities" field of an incoming
SELECTOR Conditional execution of the DELE function.
The DELE function is executed, regardless of the names of the source and destination resources
used.
The DELE function is executed when the name of the destination logical resource used matches
the name defined in the SELECTOR field.
Destination and source resource names are specified.
The DELE function is executed when the names of the destination and source resources used
respectively match the names defined in the SELECTOR field.
GENERATOR This field contains two hex characters, representing the "facility" code to be deleted.
The parameters for this code are also deleted.
Notes
The deletion of a "facility" code sets the mask for that facility to 1.
Consequently, before deleting a code and one or more "facility" parameters, the mask concerned is
scanned.
If the mask is at 1, the DELE function is not executed.
E Page 9-54
9.7.3.3.1 Example (DELE function)

take, for example, the following output MAC program:

1 Lxxx OBEG
2 Lxxx DELE NONE 02
3 Lxxx DELE NONE RSDE 42
4 Lxxx DELE NONE RSDE, RSDS 43
5 Lxxx DELE NONE 02
6 Lxxx OEND

2 No validation is carried out on the names of the source and destination resources used respectively by the
Assume that the output MAC logic is positioned at the start of the "X.25" facilities type:
The "facilities - X.25 type" field of the incoming call request packet has the code (02) and the associated
"Throughput class negotiation" parameters deleted.
3 Validation is carried out on the name of the destination logical resource used by the outgoing call request
packet.
The destination resource name matches RSDE.
The destination resource name does not match RSDE.
The "facilities - X.25 type" field of the incoming call request packet has the code (42) and associated "Non-
standard default packet size" parameters deleted.
4 Validation is carried out on the names of the source and destination logical resources used respectively by
the incoming and outgoing call request packets. There are two possibilities:
The source and destination resource names respectively match RSDS and RSDE.
A source and/or destination resource name does not match RSDS and/or RSDE.
The "facilities - X.25 type" field of the incoming call request packet has the code (43) and associated
"Default non-standard window size" parameters deleted.
5 No validation is carried out on the names of the source and destination logical resources used respectively
by the incoming and outgoing call request packets.
However, the mask for code 02 is already set to 1.
Consequently, the DELE function cannot be executed and record N° 5 is disregarded.
E Page 9-55
E
9.7.3.4 "COPY" function
NAME FUNCTION

Lxxx COPY NONE DEST space
DEST, SRCE ∗
space Facility code (hex).
FUNCTION To copy one or more codes and their associated parameters into the "facilities" field of an
outgoing call request packet.
SELECTOR Conditional execution of the COPY function.
The COPY function is executed regardless of the names of the source and destination resources
used.
The COPY function is executed when the name of the destination resource used matches the
The COPY function is executed when the names of the destination and source resources used
GENERATOR The content of this field is:
• "space", or
• "*", or
• a facility code.
Notes
Copying a facility code sets the mask for that facility to 1.
Consequently, before copying any facility codes, the mask concerned is scanned.
If the mask is set to 1, the COPY function is not executed.
E Page 9-56
9.7.3.4.1 Example (COPY function)


1 Lxxx OBEG
2 Lxxx COPY NONE
3 Lxxx COPY NONE RSDE ∗
4 Lxxx COPY NONE RSDE, RSDS 02
5 Lxxx COPY NONE 02
6 Lxxx OEND

2 No validation is performed on the names of the source and destination resources used respectively by the
Assume that the output MAC logic is positioned (POSN) at the start of the "OSI-DTE" facilities type.
The codes and parameters associated with the "facilities - OSI-DTE type" field of the incoming call request
packet are copied into the "facilities - OSI-DTE type" field of the outgoing call request packet.
The mask for each code copied is set to 1.
3 Validation is carried out on the name of the destination resource used by the outgoing call request packet.
Assume that the output MAC logic is positioned (POSN) at the start of the "X.25" facilities type.
The codes and parameters associated with all of the "facilities" field of the incoming call request packet are
copied into the "facilities" field (types = X25, "ISO" DTE) of the outgoing call request packet.
The mask for each code copied is set to 1.
4 Validation is carried out on the names of the source and destination resources used respectively by the
The source and destination resource names respectively match RSDS and RSDE.
Processing of record N° 4 is continued.
A source and/or destination name does not match RSDS and/or RSDE.
Record N° 4 is disregarded. Record N° 5 is counted.
Assume that the output MAC logic is positioned (POSN) at the start of the "X.25" facilities type.
Code 02 and the associated "Throughput class negotiation" parameters of the incoming call request packet
are copied into the "facilities - X.25 type" field of the outgoing call request packet.
5 No validation is carried out from the names of the source and destination resources used respectively by
the incoming and outgoing call request packets.
However, the mask for code 02 is already set to 1.
Consequently, the COPY function cannot be executed and record N° 5 is disregarded.
E Page 9-57
E
9.7.3.5 "MARK" function
NAME FUNCTION

Lxxx MARK NONE DEST Second byte of a marker, indicating the
DEST, SRCE start of a facility type (hex).
space
NAME Link descriptor names linked with the output MAC program.
FUNCTION In an outgoing call request packet, stores a marker indicating the start of a "facility" type.
SELECTOR Conditional execution of the MARK function.
The MARK function is executed regardless of the names of the source and destination resources
used.
The MARK function is executed when the name of the destination resource used matches the
The MARK function is executed when the names of the destination and source resources used
GENERATOR This field contains two hex characters representing the second byte of a marker indicating the start
of a facility type.
The following characters can be specified:
OO = Set marker indicating start of "X.25" facilities.
OF = Set marker indicating start of "OSI-DTE" facilities.
Note
The setting of a marker is accompanied by a reset (to 0) of all masks associated with this "facility" type.
E Page 9-58
9.7.3.5.1 Example (MARK function)


1-1 Lxxx OBEG
1-2 Lxxx MARK NONE 00
1-3 Lxxx OEND
2-1 Lxxy OBEG
2-2 Lxxy MARK NONE RDES 0F
2-3 Lxxy OEND

1-2 No validation is carried out on the names of the source and destination resources used respectively by the
The marker (0000) indicating the start of the "X.25" type is set in the "facilities" field of the outgoing call
request packet.
All masks associated with the "X.25" type are reset (to 0).
2-1 Output MAC program entry point, for link Lxxy.

2-2 Validation is carried out on the name of the destination resource used by the outgoing call request packet.
The destination resource name matches RDES.
The name of the destination resource does not match RDES.
Record N° 2-2 is disregarded.
Record N° 2-3 is counted.
The marker (000F) indicating the start of the "OSI-DTE" type is set in the "facilities" field of the outgoing call
request packet.
All masks associated with the "OSI-DTE" type are reset (to 0).
2-3 Output MAC program exit point, for link Lxxy.
E Page 9-59
E
9.7.3.6 "DATA" function

Lxxx DATA NONE DEST character string (hex and/or text) space
DEST, SRCE
space
FUNCTION Concerning an outgoing call request packet:
Terminates processing of the content of the "facilities" field, and inserts information in the "Facility
length" field.
Stores information in the "Call user data" field.
SELECTOR Conditional execution of the DATA function.
The DATA function is executed regardless of the names of the source and destination resources
used.
The DATA function is executed when the name of the destination resource used matches the name
defined in the SELECTOR field.
The DATA function is executed when the names of the destination and source resources used
GENERATOR The content of the field can be:
Space
The user data in the call request packet is copied in full into the "Call user data" field of the
Character strings
The characters specified are stored in the "Call user data" field of the outgoing call request packet.
Notes:
Text can be specified. This must be prefixed and followed by the "'" character.
The continuation sign "-" is allowed.
E Page 9-60
9.7.3.6.1 Example (DATA function)


1-1 Lxxx OBEG
1-2 Lxxx DATA NONE RDES
1-3 Lxxx OEND
2-1 Lxyy OBEG
2-2 Lxyy DATA NONE RDES, RESS 534154
2-3 Lxyy OEND

1-2 Validation is carried out on the name of the destination resource used by the outgoing call request packet.
Information is inserted in the "Facility length" field.
User data from the incoming call request packet is copied in full into the "Call user data" field of the
2-1 Output MAC program entry point, for link Lxyy.

2-2 Validation is carried out on the names of the source and destination resources used respectively by the
The source and destination resource names respectively match RESS and RDES.
The processing of record N° 2-2 continues.
A source and/or destination resource name does not match RESS and/or RDES.
Record N° 2-2 is disregarded.
Record N° 2-3 is counted.
Information is inserted in the "Facility length" field.
The information specified in the GENERATOR field (SAT in hex) is stored in the "Call user data" field of the
2-3 Output MAC program exit point for link Lxyy.
E Page 9-61
E
9.7.3.7 "EOF" function
NAME FUNCTION

Lxxx EOF NONE DEST space
DEST, SRCE
space
FUNCTION Concerning an outgoing call request packet:
Terminates processing of the content of the "facilities" field, and inserts information in the "Facility
length" field.
SELECTOR Conditional execution of the EOF function.
No EOF information is specified.
The EOF function is executed regardless of the names of the source and destination resources
used.
A destination resource name is specified.
The EOF function is executed when the name of the destination resource used matches the name
defined in the SELECTOR field.
The EOF function is executed when the names of the destination and source resources used
GENERATOR The content of this field must be set to "space".
E Page 9-62
9.7.3.7.1 Example (EOF function)


1 Lxxx OBEG
2 Lxxx POSN NONE 0F
3 Lxxx DELE NONE CB
4 Lxxx EOF NONE RSDE, RSDS
5 Lxxx OEND

2 In the incoming call request packet, positions on the "OSI-DTE" facility type.
3 In the incoming call request packet, deletes the facility code and associated "Calling line address extension"
parameters.
4 Validation is carried out on the names of the source and destination logical resources respectively used by
the incoming and outgoing call request packets.
The source and/or destination resource names match RESS and RDES.
A source and/or destination resource name does not match RESS and/or RDES.
Record N° 4 is disregarded. Record N° 5 is counted.
Inserts information in the "Facility length" field.
E Page 9-63
E Page 9-64
10. GIS board: "S0" ISDN interface
10.1 Introduction
The GIS board is for connecting to the ISDN. It provides an S0 port (2B+D channels).
The GIS board has its own system software installed in IC31.
Depending on the software release installed on the Megapac or Megabox CPU board, the GIS board can
be used to relay information from protocols such as X.25, PPP, Frame Relay and SDLC to the B and D
channels of the ISDN interface.
This manual is for GIS board software reference "3.02.cc.X-YY" (cc is the revision index, X-YY specify
a country and a standard).
This version supports relaying to the 2B+D channels of the following protocols:
• native X.25, with Megapac 400 and above
software
• X.25, HDLC, transparent mode, no V.25 Bis management with Megapac 400 and above
software
• X.25, HDLC, transparent mode, with V25 Bis management with Megapac 400 and above
software
• PPP, transparent mode, no V.25 Bis management with Megapac 500, 600 software
• PPP, transparent mode, with V25 Bis management with Megapac 500, 600 software
LK2
P1
- IC50
IC31
battery GENERIC
"GIS" INTERFACE
software
+
SRAM
IC49
S0
LK4
Interface
SRAM
68302
68302 LK1
J1
SRAM
S0 LK3
IC1
87654321
SW2 4
SRAM 3
4321 4321 2
1
SW5 SW4 SW1
GIS board: "S0" ISDN interface
E Page 10-1
E
10.2 Megapac configuration
It is important to configure three links, in other words three "Descriptors", each corresponding to one B
channel or the D channel of the ISDN S0 interface. These three links are called "virtual links" in that
they are internal to the Megapac, and they must be configured as shown in the tables below.
10.2.1 Operating modes
The three vertical links can be used in the following modes:
ISDN Operating TYPE SUB-TYPE OPTION Extended Call

interface mode Management
(Megapac software)
channel
B or D Native X.25 X25 GIO NONE NONE
(UI not required) (V25B not required)
(400 and + software)
B Transparent X25, HDLC GIO UI NONE
without V.25 Bis (V25B not required)
B Transparent X25, HDLC GIO UI V25B
with V.25 Bis
B Transparent PPP GIO (no OPTION field in NONE
without V.25 Bis PPP) (V25B not required)
B Transparent PPP GIO (no OPTION field in V25B
with V.25 Bis PPP)
Note • The descriptor associated with the "D" channel must be in native X.25 mode.
• The descriptors associated with the "B" channels can be in a different mode on the
same GIS board.
GIS
Megapac 1st virtual link B

routing X.25,HDLC,PPP
via tables: 2nd virtual link B ISDN
X.25 X.25,HDLC,PPP
MAC 3rd virtual link D
etc. ... native X.25
X.25 table ISDN table
ROUT table LINK table
Figure 10-1 GIS board 2B+D channel routing
E Page 10-2
10.2.2 Correlation between the "descriptors" and physical ports
The "Overview of link descriptors" section explains the relationships between the descriptors and
physical ports.
For example:
For two GIS boards in the same Megapac, the descriptors can be configured as follows:
"Name" Physical correlation "Name"

of descriptor of resources
G1B1 channel B1 of first GIS board B1G1(1 to 16)
G1B2 channel B2 of first GIS board B2G1(1 to 16)
G1D1 channel D of first GIS board D1G1(1 to 16)
G2B1 channel B1 of second GIS board B1G2(1 to 16)
G2B2 channel B2 of second GIS board B2G2(1 to 16)
G2D1 channel D of second GIS board D1G2(1 to 16)
10.3 ISDN number
An ISDN subscriber is identified by:

• The Installation Designation Number, "NDI".
• The Supplementary Designation Number, "NDS".
The calling party can be identified by the abbreviation "CGP" and the called party by the abbreviation
"CDP".
The ISDN number is made up of the following numbers:

• destination number (NDS-CDP);
• user origination number (NDS-CGP);
• network origination number (NDI-CGP).
This gives the general form: (NDS-CDP); (NDS-CGP); (NDI-CGP).
E Page 10-3
10.4 Link configuration parameters in native X25 mode

Name Settings
NAME Up to 4 characters Name of virtual link between "GIS" and Megapac.
TYPE By default = X25 X.25 link
SUB-TYPE GIO For GIS (S0) three descriptors must be declared (2B+D).
The first descriptor of a GIS board contains the
interchanges with the board.
NEW PHYSICAL By default = NO This descriptor shares the same link as previously
INTERFACE defined in X25 mode.

With GIS board, only the first descriptor of the board
SPEED By default = EXT This parameter is not used with GIS board.
PACKET SIZE max 1024 Maximum negotiable outgoing packet size, in bytes.
With GIS board, available PACKET SIZE are 128, 256,
512 or 1024 bytes.
BANDWIDTH By default = 0 Identical to an TYPE/ X25 descriptor and
SUB TYPE/ XIO
V54 MODEM By default = NO This parameter is not used with GIS board.
ADDRESS DCE or B The link descriptor is a logical DCE.
Use DCE mode with the GIS board (without V25.Bis)
Use AUTO in transparent with V25.Bis mode.
max 32 With "GIS" board
OPTIONS By default = NONE Identical to an TYPE/ X25 descriptor and
SUB TYPE/ XIO
MODM Do not use with "GIS" board.
INIT FRAME By default: SABM This parameter is not used with GIS board.
T1 By default = 30 This parameter is not used with GIS board
T3 By default = 60 This parameter is not used with GIS board
TRIES By default = 10 This parameter is not used with GIS board
(N2 of X.25)
K LEVEL2 By default = 7 This parameter is not used with GIS board
K LEVEL3 By default = 2 Use the same window size that the window size used
value of 1 to 7 in LINK table of "GIS" board.
E Page 10-4
E
LINE GROUP
LCGN
LCN OFFSET
By default = 0
By default = 0
By default = 0
Identical to an TYPE/ X25 descriptor and SUB TYPE/ XIO
Threshold for number assigned to the first logical
resource attached to the link.
1 With the "GIS" board
ADDRESS GROUP By default = 0 Identical to an TYPE/ X25 descriptor and SUB TYPE/ XIO
FRAME SEQ By default = NORM This parameter is not used with GIS board
CALL TIME OUT In seconds Call confirmation supervision timer (TP2).
By default = 5
60 Recommended with the "GIS" board
ERROR THRESHOLD By default = 20 This parameter is not used with GIS board
LOOP BAR PRIORITY By default = 0 Call loop.
MANAGEMENT Identical to an TYPE/ X25 descriptor and SUB TYPE/ XIO
OPTIONAL TIMERS By default = NONE Implement optional timers.
T13 (60 seconds) Call clear confirmation packet timer in logical DCE mode
T13+T23 Recommended with the "GIS" board
OPTIONAL FLAGS By default = 0 This parameter is not used with GIS board
E Page 10-5
E
10.5 GIS board configuration
The configurator of a GIS board can be used to modify or display the tables listed below.
The GIS board configurator can be accessed via a channel or a virtual link running in native X.25 mode.
The configurator is therefore always accessible via the "D" channel of the ISDN interface or via the
virtual link associated with the "D" channel.
The parameters for the GIS adapter are saved on the board, in four tables:
• X25 links a routing identifier to an X.121 address outgoing on the ISDN.

• ROUT links a link number to a routing identifier.
• ISDN links a node name to an E.164 address (ISDN number).
• LINK links a set of X.25 link parameters to a node name.
There are three other read-only tables, as follows:
• HELP displays a summary of the configurator commands.

• STAT displays the current status of the virtual links (2B + D).
• MEMD displays the content of a memory area (use reserved).
To administer these tables, the configurator supports the following functions:
MGET displays the content of a table with no particular formatting.

INIT clears all of the current table.
DELE deletes the current line.
INSE inserts a blank line.
COPY copies the previous line.
Gxxx is used to go to line xxx of the current table.
LIST is used to display a table one page at a time.
CONF is for configuring (modifying) the content of a table.
DUMP displays the content of the X.25, LINK, ISDN and ROUT tables with no particular
formatting.
The configurator supports five "general" functions, as follows:
QUIT releases the link providing access to the GIS board configurator.
LOOP is used to set up a test loop.
CALL is used to set up a test call.
DISC is used to disconnect a test call.
E
ECHO is used to select echo mode.
GIS board: "S0" ISDN interface Page 10-6
10.6 Structure of the GIS board tables
10.6.1 X.25 table syntax (GIS)
The "X.25" table for the GIS board has 256 records.
A record in the "X.25" table (GIS) comprises two fields separated by a "space" character..
The "X.25" table (GIS) appears in tabular form:
NAME X121 ADDRESS
The meaning of the columns is as follows:
field length meaning format

NAME 4 Identifier used by the routing function. alphanumeric
characters
The identifier "BE0∗" is reserved. It provides access to the (wildcard * possible)
GIS board configurator.
The identifier "XXXX" is reserved; it is used to define a routing
in the absence of an originating ISDN number (PBXNB-CGP).
X121 15 X.121 address outgoing on the ISDN decimal
ADDRESS characters
(wildcards * and !
possible)
E Page 10-7
E
10.6.2 ISDN table syntax (GIS)
The ISDN table for the GIS board has 256 records.
A record in the ISDN table (GIS) comprises two fields separated by a "space" character.
The ISDN table (GIS) appears in tabular form:
NAME E164 NUMBER

NAME 4 Node name used by the routing function alphanumeric
characters
(wild card * possible)
E164 25 ISDN number (NDI-CGP) or (NDS CDP) decimal
NUMBER characters the address and sub-address of which are separated by ":"
(wild card * and !
possible)
10.6.2.1 GIS adapter ISDN address
NAME E164 NUMBER

IDS0 ISDN number of the adapter.
Outgoing, this number is used as the originating user number (NDS-CGP).
Incoming, the number is used to identify the call, and is compared to the destination
number (NDS-CDP).
(wildcards * and 1 are prohibited)
An incoming call is rejected if it contains a destination number (NDS-CDP) that does not match the ISDN
number of the record with the NAME IDS0.
For a record "IDS0", when the numbers (that of the adapter and NDS-CDP) are of different lengths, the
match is based on the lower order digits of the longer number. For example, the number 0140771212
matches the number 40771212.
Changes to the IDS0 field do not take effect immediately. For this, the GIS board must be reset. The
GIS board can be reset by a Megapac BOOT sequence or by the command "STOP" on the 1st virtual
link of the board.
10.6.2.2 NAME = GIO1, GIO2
NAME E164 NUMBER

GIO∗ ISDN number
The names GIO1 and GIO2 are names reserved for routing frames in transparent mode.
E Page 10-8
E
10.6.3 LINK table syntax (GIS)
The LINK table of the GIS board has 16 records.

A record in the LINK table (GIS) comprises ten fields separated by "space" characters.
The LINK table (GIS) appears in tabular form:
NAME NBCH PSIZ K3 ADR T25 N2 T1 EXT 1LCN

(wildcard * possible)
NBCH 1 to 4 Maximum number of virtual circuits decimal
PSIZ 1 to 4 Maximum packet size (128, 256, 512 or 1024) decimal
K3 1 Level 3 window size (1 to 7) decimal
ADR 1 Link DTE / DCE mode. alphanumeric
• T: the link is DTE
• C: the link is DCE
• A: the link is DTE for outgoing calls, DCE for incoming
calls (AUTO).
• R: the link is DCE for outgoing calls, DTE for incoming
calls (REVERSE).
T25 1 to 2 Inactivity timer (1 to 80 seconds) decimal
ISDN call clearing timer, effective after clearing the last virtual
circuit (of an active B channel)
N2 1 to 2 Number of level 2 retries (1 to 20) decimal
T1 1 to 3 Timer T1 (1 to 999 seconds) decimal
Level 2 frame relay timer (Lap B)
EXT 1 to 3 Extended mode (modulo 8 to 128) alphanumeric
1LCN 1 to 4 Number threshold assigned to the first logical resource decimal
attached to the link (LCN OFFSET>0). (1 to n)
For the B channels, when the LINK table is used and there is no corresponding node name a default
profile is used.
E Page 10-9
For the D channel, a profile can be specified in the LINK table. The node name TEI∗ must be used to
establish this profile. Changes to the TEI∗ field do not take effect immediately. For this, the GIS board
must be reset. If there is no node name TEI∗, a default profile is used.
Likewise, for the "leased line" service (specifically Germany D64S), a profile can be specified in the LINK
table. The node name CHB1 (or CHB2) must be used to set the profile of channel B1 (or B2).
The GIS board can be reset by a Megapac BOOT sequence or by the command "STOP" on the 1st
virtual link of the board.
Default profile parameters B channels D channel

• Maximum number of virtual circuits 16 16
• Maximum packet size 128 128
• Level 3 window size 2 2
• Link DTE / DCE mode AUTO DTE
• Inactivity timer "T25" 6 sec 6 sec
• Number of retries at level 2 10 10
• Frame retry timer "T1" 1 sec 1 sec
• Extended mode Modulo 8 Modulo 8
• Number threshold assigned to the first logical 1 1
resource attached to the link (LCN OFFSET).
E Page 10-10
E
10.6.4 ROUT table syntax (GIS)
The ROUT table for the GIS board has 16 records.

A record in the ROUT table (GIS) comprises seven fields separated by "space" characters.
The unused fields must contain at least "hyphen" characters.
The ROUT table (GIS) appears in tabular form:
NAME KEY FUN SEL OPT ROUT DEST

NAME 4 Identifier used by the routing function alphanumeric
(fixed) or (wild card * possible)
Node name used by the routing function
KEY 2 or 3 Identification key alphanumeric
IN: for selecting a descriptor for an incoming call (necessary
for incoming call filtering)
OUT: use reserved
(used with the "OPT" field, the KEY=OUT field can be used to
define an outgoing call on a B channel in packet mode)
LLP: to force the use of one of the 2 B channels into leased
line mode.
TEI: to define a TEI number (01 to 62) for the D channel.
TNA: to define a TEI number (0) for the D channel.
FUN 1 to 4 Function alphanumeric
(nothing, 1 to 3, *)
SEL 1 to 4 Selection alphanumeric
(nothing, CAD)
OPT 1 to 3 Option alphanumeric
(nothing, PAQ)
ROUT 1 to 4 Route (reserved)
DEST 1 to 4 Destination (reserved)
E Page 10-11
10.6.4.1 Incoming call routing ("IN" key)
For the "IN" key, the "FUN" function field indicates:
FUN meaning
1 use the 1st virtual link
2 use the 2nd virtual link
∗ use the 2nd virtual link if free, otherwise the 1st
nothing or - the call is rejected
For the "IN" key, the "SEL" selection field indicates:
SEL meaning
CAD When the address of the caller does not exist, the NDI of the installation is used as the
(native X25) calling address in the X.25 call request packet.
nothing or - In the X.25 call request packet, the address of the caller is unchanged.
10.6.4.2 Outgoing call mode ("OUT" key)
For the key "OUT", the "OPT" option field indicates the mode of the call in the B channel:
OPT meaning
nothing The outgoing call on the B channel is in circuit mode
(circuit mode is selected by default)
PAQ The outgoing call on the B channel is in packet mode (specifically for Germany)
(similar to packet mode in a D channel)
E Page 10-12
E KEY
10.6.4.3 D channel parameters ("TEI" key)
NAME FUN SEL OPT ROUT DEST

Identifier name TEI 3 TEI number - = 2B+D
∗∗∗∗ by default 01 to 62 D = no B channels
TNA
The D channel of the ISDN interface works in permanent logical link (PLL) mode.
The "TEI or TNA" key record does not take effect until the GIS board is reset.
If this record does not exist, calls cannot be made on the D channel.
The "TNA" key record provides to use the TEI number 0. In this case, the FUN, SEL and OPT fields are
not used, and 2B+D channels are enable.
When the network causes of a loss of "TEI", the message "CARRIER LOSS" is displayed on the
Megapac supervisory console, provided that the "DCD" option has been assigned to the link descriptor
associated with the D channel. After a loss of "TEI", the D channel cannot be used until the GIS board
has been reset.
The GIS board can be reset by a Megapac BOOT sequence or by the command "STOP" on the 1st
10.6.4.4 Leased line mode parameters ("LLP" key)
The "leased line" mode is a specific service of Germany (D64S). It allows a physical connection of a B
channel to be set up on the S0 bus, with the other B channel not being used. The "leased line" mode is
used to relay X25 and HDLC protocols in transparent mode.
In "leased line" mode, the identifier name must be "CHB∗".

Identifier name LLP B channel number
CHB∗ 1
2
∗ (both)
This record is used to force the use of one of the 2 B channels into leased line mode.
Recording of the "LLP" key is only registered after reset of the GIS board.
If this record does not exist, the B channels cannot be used in leased line mode.
10.6.4.5 Example of ROUT table "LIST"

TOTO IN 1
TATA OUT - - PAQ
E
TUTU TEI 3 54 -
E
10.7 Statistics
The STAT table for the GIS board has three records.
This table is read only. It provides access to statistical information concerning the links associated with
channels B1 and B2 and the D channel.
The statistics are displayed in tabular form:
L TYPE NAME STATE CAUSE LCN 1LCN PS K ADR EXT
L number Number of data links connected.

from 0 to 3
0 = no connection
1 = connection on B1 or B2
3 = connection on D
TYPE operating mode X25 = for native X.25 mode.
HDLC = for transparent mode without V.25 Bis.
V25 B = for transparent mode with V.25 Bis.
NAME name name of the node to which the current call is connected.
or "nothing"
"nothing" if there is no connection.
STATE DISC, IN, OUT, DISC = no current connection (B or D channel)
PRO, CNX, IN = incoming ISDN call (B channel)
READY OUT = outgoing ISDN call (B channel)
PRO = call being set up (B channel)
CNX = B channel connected
READY = D channel connected
CAUSE L or R with a hexadecimal type of disconnection.

number
L = local
R = remote
cause of disconnection, compliant with Q.931.
The information below is specific to the native X.25 mode.
LCN number of resources set up 01 to 99
1LCN (LCN OFFSET). 1 to 4095
PS Max packet 128, 256, 512, 1024
size
K3 Level 3 window 1 to 7
ADR DTE or DCE mode DTE
DCE
E
EXT Extended mode E = modulo 128
nothing = modulo 8
E
10.8 Help
The "HELP" table for the GIS board has 29 records.

This table is read only. It can be used to display the various commands available from the GIS board
configurator.
The "HELP" is displayed in tabular form:
Commands GIS board software release number

ECHO Set echo on, or Set echo off
QUIT Quit VCP
CALL Set up a test call
DISC Release the test call
LOOP Set / Remove test loopback
MGET Dump table
DUMP Dump all tables
INIT Erase current table
DELE Erase current record
INSE Insert new record
COPY Duplicate current record
Gxxx Go to record xxx
LIST Display table
CONF Configure mode
X25 Change to X25 table
ISDN Change to ISDN table
LINK Change to LINK table
ROUT Change to ROUT table
STAT Display STAT table
MEMD Display memory contents from xxxxxx (use reserved)
HELP Display this table
0x08 ← Erase character
0x0D ↵ Validate entry
0x1B Esc Escape from command

0x15 ^\ Copy current character
0x20 space Field separator
0x2F / Repeat current command
0x3C > Next record
0x3E < Previous record
E
0x40 @ Transparency character
E
10.9 Details of commands
10.9.1 Table management commands
MGET This command is used to display the entire content of a table, without pausing, with no
header and with no current line indication.
The display always begins from the first line of the current table.
DUMP As MGET for the X25, LINK, ISDN and ROUT tables.
INIT The INIT command is used to clear all of the current table.
Only the modifiable tables (X25, ISDN, LINK and ROUT) can be deleted.
DELE The DELE command is used to delete the current line.
This command is applicable only to modifiable tables.
The current line is deleted and the content of each line that follows is copied to the previous
line. The last line becomes blank.
INSE The INSE command is used to insert a blank link at the current line position.
The content of each line from the current line is copied to the next line. The last line is lost.
The current line is replaced by a blank line.
COPY This command is used to copy the current line.
The current line is unchanged.
Gxxx This command is used to go to the specified line.
The number of the new current line is given by "xxx".
When the number "xxx" is greater than the number of records in a table, the command
takes you to the last record in the table.
LIST This command is used to display one page of the current table, from the current line.
The header of the table is displayed at the top of each page, and the prompt is displayed at
the beginning of each line. On each page, a pause for any character is implemented
before the next page is displayed.
CONF This command is used to configure (modify) the content of a table.
The content of the current line prefixed by the prompt character is displayed, followed by
the pause character "/". The characters, apart from special characters, are temporarily
buffered, and then when committed, they replace the current line.
E Page 10-16
E
10.9.2 "General" management commands
QUIT
This command is used to clear the link providing access to the GIS board configurator.
The link providing access to the configurator is also released after inactivity for longer than
three minutes.
LOOP This command is used to set up or clear a test loop between transmission and reception on
a channel.
This command is useful for approval tests.
CALL This command is used to initialize a test ISDN call.
This command is useful for approval tests; the ISDN destination number must be defined in
a NAME = TEST record. The node is defined by the "ROUT" table.
DISC This command is used to clear a test call.
This command is useful for approval tests. If there is no test call in progress, another
current call is cleared.
ECHO This command is used to enable or cancel character echo mode.
By default, with each new connection, echo mode is not enabled.
10.9.3 Dialogue
Prompt The configurator displays a prompt text comprising:

• the name of the current table,
• followed, between brackets, by the number of the current line,
• ending with the ">" sign.
The configurator is then ready for a command line with one or more four-character key
words, separated by one or more spaces. The key words can be a table name and an
operation or a command. The command line is committed by the "CR" character, and each
key word is interpreted in order of entry.
Navigation A "table name" key word can be used to change current table.
The current line number and the current operation type are always retained. Because of
this, with a change of table, the last current operation remains active.
The "MEMD" table must be followed by a hexadecimal number on 1 to 8 characters
defining the starting address of the memory block to be displayed.
E Page 10-17
E
10.9.4 Special characters
Carriage Return
The "CR" character confirms the content of the input buffer.

↵ At the prompt, the input buffer contains key words analyzed and interpreted after
committal by the "CR" character.
In configuration mode, the input buffer contains the new content of the current line.
Backspace The "←" character can be used to delete the last character entered in the input
buffer.
←
Slash The "/" character can be used to repeat the previous command line.
/ In configuration mode, if this character is the last character entered by the operator,
it is interpreted as an escape character: return to the prompt without canceling
configuration mode.
Esc The "Esc" character cancels the current command and the current table.
By default, the current table is the "HELP" table, the current line is the first line of
the table and no operation is in progress.
The "Esc" character can also be used to exit "LIST" or "CONF" mode.
Space The "Space" character is used to separate key words in a command line.
In configuration mode, it can also be used to separate the fields of the current
record, or leave one or more fields blank.
> At the prompt, or in configuration mode, when the current line is empty, these
characters can be used to move to the next line ( > ) or the previous line ( < ).
<
Otherwise, these characters are normally entered in the input buffer.
Ctrl Back Slash In configuration mode, the "^ \" character is used to copy the character in the same
position of the current line to the input buffer.
^\
Commercial at In configuration mode, the "@" character is used to enter special characters in the
input buffer. The character after "@" is entered in the current line without being
@
interpreted as a special character. The "@" character is not copied to the input
buffer (or into the tables).
When displaying a table, the special characters are prefixed by the "@" character.
Ctrl All the control characters, apart from those described previously, are not supported
("ERROR" message displayed).
E Page 10-18
10.10 Access to the GIS board configurator
The configurator can be accessed:

• through a native X.25 call in which the USER DATA takes the form "BE0∗", or
• through a native X.25 call in which the X.121 call number is that of the configurator.
10.10.1 Native X.25 call in which the USER DATA takes the form "BE0∗"
When a GIS board is commissioned, the ISDN and X.25 tables (GIS) are empty.
A native X.25 call to one of the resources of the three descriptors of the GIS board, with USER DATA in
the form "BEO*" can always be used to access the GIS board configuration functions.
To return to the example of a Megapac with two GIS boards, the Megapac X.25 table contains the
following records:
NAME ADDRESS ADDRESS USER DATA

GROUP
B1G1 0 (blank) ‘BE0∗

(one of the resources of the three descriptors of the
first GIS board)
second GIS board)
From the terminal connected to the "CPU" board's VCP control port:
• a call to resource B1G1 provides access to the configurator of the first GIS board,
• a call to resource B1G2 provides access to the configurator of the second GIS board.
E Page 10-19
10.10.2 Native X.25 call in which the X.121 call number is that of the configurator
A node with a name that takes the form "BE0∗" provides access to the GIS board configurator.
After first accessing the GIS board's configurator using the previous method, it is then possible to place a
record in the X.25 table (GIS), specifying:
• an identifier in the form "BE0∗",
• an X.121 number to call the node.
To return to the example of a Megapac with two GIS boards, the X.25 tables of the GIS boards contain
the following record:
X.25 table of the first GIS board

prompt NAME X121 ADDRESS
X25(00): BE0∗ 101
X.25 table of the second GIS board

X25(00): BE0∗ 102
The Megapac's X.25 table contains the following records:

GROUP
B1G1 0 101
(one of the native X.25 resources of the three
descriptors of the first GIS board)
B1G2 0 102
descriptors of the second GIS board)
• a call to number 101 provides access to the configurator of the first GIS board,
• a call to number 102 provides access to the configurator of the second GIS board.
E Page 10-20
E
10.11 Routing
The adapter can be used to relay calls (in native X.25, transparent without V.25 Bis mode and
transparent with V.25 Bis mode) between three virtual links (three descriptors) of the Megapac switch,
and the two "B" channels and the "D" channel of the "S0" interface. The "D" channel supports only the
native X.25 mode.
Calls from the Megapac over a virtual link (resources of one of the three descriptors) are routed to the
channel associated with it, and only to that channel.
Similarly, calls received over a channel are all routed to the same virtual link (resource of one of the
three descriptors) of the Megapac.
10.12 Call from the Megapac end (B and D channel virtual link)
10.12.1 Call from a "B" channel virtual link in native X.25 mode
When a native X.25 mode call from the Megapac is offered:

• Its destination X.121 address is examined.
• If it is present in the corresponding field of an X.25 table (GIS) record, the associated
identifier name is used.
• Otherwise, the USER DATA is examined, and if in the form "BE0*", the call is connected to
the GIS board configurator.
• Otherwise, the call is rejected.
• If the associated identifier name is in the form "BE0∗", the call is connected to the GIS board
configurator.
• If no call is in progress:
• The identifier is strictly compared with the node names in the ISDN table to find a
destination ISDN number. When an IDS0 record exists, the associated number is used as the
originating number (NDS-CGP).
• The node name found is assigned to the channel.
• The GIS board initializes:
• the ISDN call in CIRCUIT mode by default, or in PACKET mode if the ROUT
table contains a record corresponding to the node name of the channel, with
the fields KEY=OUT and OPT=PAQ,
• then the X.25 call in a B channel with the X.25 characteristics of the link
associated with the node taken from the LINK table. When the LINK table
has no record for this node, the default profile is used.
• If there is no correlation between the identifier and the node names in the ISDN table, the
native X.25 mode call is rejected.
• If there is a call already in progress on the associated channel, the associated node name must be
compatible with the identifier, otherwise the X.25 call is cleared by the adapter.
When the last X.25 call on a channel is cleared, the ISDN call is cleared after the inactivity time-delay
(timer T25).
E Page 10-21
10.12.2 Call from a "B" channel virtual link in transparent mode without V.25 Bis
When a frame in transparent mode without V.25 Bis from the Megapac is offered:
• If there is no call in progress:
• The identifier GIO1 is used for the 1st virtual link, the identifier GIO2 is used for the 2nd
virtual line.
• The identifier (GIO1 or GIO2) is strictly compared with the node names in the ISDN table, to
find a destination ISDN number. When there is an IDS0 record, the associated number is
used as the originating number (NDS-CGP).
• If there is no record approaching GIO1 or GIO2 in the ISDN table, the frame from the virtual
link is rejected.
The GIS board initializes the ISDN call in CIRCUIT mode by default, or in PACKET mode if the ROUT
table contains a record corresponding to the node name of the channel, with the fields KEY=OUT and
OPT=PAQ.
When the call to the ISDN is set up, the frames are relayed transparently between the B channel and the
associated virtual link, with no flow control.
The ISDN call is cleared after the link inactivity time-delay.
10.12.3 Call from a "B" channel virtual link in transparent mode with V.25 Bis
When a frame in transparent mode with V.25 Bis from the Megapac is offered:
• The frame received is interpreted as a V.25 Bis command.
• When the "CRN" command is recognized, the "VAL" and "CNX" indications are sent over the
virtual link, and the destination number taken from the "CRN" command is used as the
destination ISDN number.
When there is an IDS0 record, the associated number is used as the originating number
(NDS-CGP).
The node name used is the one found in the ISDN table, corresponding to the destination
ISDN number. By default, the node names GIO1 and GIO2 are used according to the origin
of the frames (1st or 2nd virtual link).
When the ISDN call is rejected by the network, the indication "CFI" with the cause is sent over
the virtual link.
The GIS board initializes the ISDN call in CIRCUIT mode by default, or in PACKET mode if the ROUT
OPT=PAQ.
The ISDN call is cleared after the link activity time-delay.
E Page 10-22
10.12.4 Call from the "D" channel virtual link in native X.25 mode
The ROUT table must include a record with the key "TEI".
Presence of this record enables the "packet in D" function.
This record defines the "D only" or "2B+D" operating mode.
This record defines the TEI number to be used for the "packet in D" call.
• If it is included in the corresponding field of a record in the X.25 table (GIS), the associated
identifier name is used. When the identifier is "BE0*", the call is connected to the GIS board
configurator.
• Otherwise, the USER DATA is examined, and if in the form "BE0∗", the call is connected to
the GIS board configurator.
• When the identifier is found:
• The identifier is compared with the node name of the record in the ROUT table having the
key "TEI".
• When the identifier and the node name are compatible, the "packet in D" call is initialized,
otherwise the native X.25 mode call is rejected.
The X.25 profile on the D channel is the one in the "TEI∗" record of the LINK table, if any, or the default
profile.
E Page 10-23
10.13 Call from the ISDN end (B and D channels)
10.13.1 Call from the "B" channel
An ISDN call is accepted when:

• The adapter does not have a specific ISDN address (no "IDS0" record).
• The adapter has a specific ISDN address (the "ISDN" table has an ISDN address record with the node
name "IDS0"), and the destination address of the ISDN call received (the NDS-CDP) corresponds to
the adapter's ISDN address.
An ISDN call is not accepted when the adapter has a specific ISDN address and the destination address
of the ISDN call received (NDS-CDP) does not match the ISDN address of the adapter.
When an ISDN call is accepted, the originating ISDN number (NDI-CGP) is examined.
• NDI-CGP is present, the call is from the public network.
• NDI-CGP is absent, the call is from a private network.
When the NDI-CGP number is present:

• The "ISDN" table (GIS), for this NDI-CGP, indicates a specific node name.
• Otherwise, the node name "XXXX" is used for routing requirements.
When the NDI-CGP number is absent:
• The node name "XXXX" is used for routing requirements.
When the node name is specific, the ROUT table (KEY = IN) indicates whether the call is accepted or
rejected. If accepted, the ROUT table indicates which virtual link (1st or 2nd) is associated with the call.
When the ROUT table has no record for the specific node name, the call is rejected.
When the node name is "XXXX", the ROUT table (KEY = IN) indicates whether the call is accepted or
When the ROUT table has no record for the node name "XXXX", the call is accepted as a priority on the
2nd virtual link if free, and on the 1st link otherwise.
The associated virtual link indicates the mode (native X.25, transparent with or without V.25 Bis).
E Page 10-24
10.13.2 Call accepted from the (B) ISDN end and relayed in native X.25 mode
The node name found previously is looked up in the LINK table to determine the X.25 parameters to be
used on the B channel. If there is no corresponding node name, the default profile is used.
The B channel can then accept X.25 calls.
When the destination address for a native X.25 mode call matches the identifier "BE0∗" (GIS X.25 table),
the call is connected to the GIS board configurator. Otherwise the call is relayed to the associated virtual
link.
10.13.3 Call accepted from the (B) ISDN end and relayed in transparent mode
without V.25 Bis
The frames are relayed transparently between the B channel and the associated virtual link, with no flow
control.
10.13.4 Call accepted from the(B) ISDN end and relayed in transparent mode with
V.25 Bis
The V.25 Bis "INC" and "CNX" indications are sent over the associated virtual link.
After sending the "CNX" indication, the frames are relayed transparently between the B channel and the
10.13.5 Call from the "D" channel
The ROUT table must include a record with the KEY "TEI".
The presence of this record enables the "packet in D" function.
When a native X.25 mode call from the "D" channel is offered:
• If it corresponds to the identifier "BE0*", the call is connected to the GIS board configurator.
• Otherwise the call is relayed to the associated virtual link.
E Page 10-25
10.14 Typical native X.25 mode configuration in a B channel
Called 999
X25
X
MEGABO
RESET
ABORT
STATUS
ISDN
(NDI=65773333)
ISDN Network
X
MEGABO
RESET
ABORT
STATUS
ISDN
(NDI=65772222)
Figure 10-2 Typical GIS board configuration in native X.25 mode
In the above example, the terminal generates an X.25 call in which the "called number" is "999".
The originating Megabox is connected to the ISDN and its NDI is 01.65.77.33.33.
The terminating Megabox is connected to the ISDN, its NDI is 01.65.77.22.22 and it accepts only ISDN
calls from subscriber 01.65.77.33.33 (in other words, the originating Megabox).
E Page 10-26
10.14.1 Originating Megabox configuration
The X.25 call request packet contains the called address "999".
The Megabox's X.25 table includes a record as follows:
NAME ADDRESS GROUP ADDRESS USER DATA
G110 0 999
"G110" is a resource of a descriptor which corresponds to the B1 channel of a GIS board.
The GIS board's X.25 table includes a record as follows:
NAME X121 ADDRESS

DEST 999
"DEST" is a routing identifier for called number "999".
The GIS board's ISDN table includes a record as follows:
NAME E164 NUMBER

DEST 0165772222
For the called number "999", call ISDN subscriber "0165772222".
The GIS board's LINK table includes a record as follows:

DEST 16 512 7 A 10 10 1 8 1
For the called number "999", the X.25 call in the B channel is based on the above characteristics (16
virtual circuits, 512 byte packets, 7 byte window, etc).
Note:
In this example, the outgoing call is set up in circuit mode so there is no need for a record in the GIS
board's ROUT table.
E Page 10-27
10.14.2 Destination Megabox configuration
The ISDN call reaches the destination Megabox with the originating ISDN number (NDI-CGP)
01.65.77.33.33.
The GIS board's ISDN table includes a record as follows:
NAME E164 NUMBER

ARR1 0165773333
Because the ISDN call is from the public network, NDI-CGP is included and the ISDN table indicates a
node name "ARR1" for this NDI-CGP.
The GIS board's ROUT table includes a record as follows:

ARR1 IN 1
For NDI-CGP "01.65.77.33.33", the call is accepted (KEY=IN), and the first virtual link is used.
The GIS board's link table includes a record as follows:

ARR1 16 512 7 A 10 10 1 8 1
For NDI-CGP "01.65.77.33.33", the X.25 call in the B channel is based on the above characteristics (16
Note: These characteristics must be the same as those defined for the outgoing call.
To terminate routing of the source X.25 call, the X.25 table of the destination Megabox includes a record
as follows:
P400 0 999
"P400" is a resource of an X.25 link descriptor corresponding to subscriber "999".
Note:
At the incoming end, the GIS board's X.25 table is not used.
E Page 10-28
11. ISDN board for Megapac ESL - Megafrad
11.1 Introduction
The ISDN board is for connecting to the ISDN. It provides an S0 port (2B+D channels).
The ISDN board has its own system software installed in MX110.
Depending on the software release installed on the Megapac ESL basic board, the ISDN board can (or
will) be used to relay information from protocols such as X.25, PPP, Frame Relay and SDLC to the B and
D channels of the ISDN interface.
This manual is for ISDN board software reference "2.01.cc.X-YY" (cc is the revision index, X-YY
specify a country and a standard).
This version supports relaying to the 2B+D channels of the following protocols:
• native X.25, with Megapac 500 and above software
• X.25, HDLC, transparent mode, no V.25 Bis management with Megapac 500 and above software
• X.25, HDLC, transparent mode, with V25 Bis management with Megapac 500 and above software
• PPP, transparent mode, no V.25 Bis management with Megapac 500 and above software
• PPP, transparent mode, with V25 Bis management with Megapac 500 and above software
MX110
(Software)
68302
68302
S0
P1
ISDN board for Megapac ESL - Megafrad
E Page 11-1
E
11.2 Megapac configuration
It is important to configure three links, in other words three "Descriptors", each corresponding to one B
channel or the D channel of the ISDN S0 interface. These three links are called "virtual links" in that
they are internal to the Megapac, and they must be configured as shown in the tables below.
11.2.1 Operating modes
The three vertical links can be used in the following modes:
ISDN Operating TYPE SUB-TYPE OPTION Extended Call

interface mode Management
(Megapac software)
channel
B or D Native X.25 X25 GIO NONE NONE
(UI not required) (V25B not required)
B Transparent X25, HDLC GIO UI NONE
without V.25 Bis (V25B not required)
B Transparent X25, HDLC GIO UI V25B
with V.25 Bis
B Transparent PPP GIO (no OPTION field in NONE
without V.25 Bis PPP) (V25B not required)
B Transparent PPP GIO (no OPTION field in V25B
with V.25 Bis PPP)
Note • The descriptor associated with the "D" channel must be in native X.25 mode.
• The descriptors associated with the "B" channels can be in a different mode on the same
ISDN board.
ISDN
board
Megapac 1st virtual link B

routing X.25,HDLC,PPP
via tables: 2nd virtual link B ISDN
X.25 X.25,HDLC,PPP
MAC 3rd virtual link D
etc. ... native X.25
X.25 table ISDN table
ROUT table LINK table
Figure 11-1 ISDN board 2B+D channel routing
E Page 11-2
11.2.2 Correlation between the "descriptors" and physical ports
The "Overview of link descriptors" section explains the relationships between the descriptors and
physical ports.
For example:
"Name" Physical correlation "Name"

of descriptor of resources
G1B1 channel B1 of ISDN board B1G1(1 to 16)
G1B2 channel B2 of ISDN board B2G1(1 to 16)
G1D1 channel D of ISDN board D1G1(1 to 16)
11.3 ISDN number
An ISDN subscriber is identified by:

• The Installation Designation Number, "NDI".
• The Supplementary Designation Number, "NDS".
The calling party can be identified by the abbreviation "CGP" and the called party by the abbreviation
"CDP".
The ISDN number is made up of the following numbers:

• destination number (NDS-CDP);
• user origination number (NDS-CGP);
• network origination number (NDI-CGP).
This gives the general form: (NDS-CDP); (NDS-CGP); (NDI-CGP).
E Page 11-3
11.4 Link configuration parameters in native X25 mode

Name Settings
NAME Up to 4 characters Name of virtual link between "ISDN" board and Megapac.
TYPE By default = X25 X.25 link
SUB-TYPE GIO For ISDN option (S0) three descriptors must be declared
(2B+D).
The first descriptor of ISDN option board contains the
interchanges with the board.
NEW PHYSICAL By default = NO This descriptor shares the same link as previously
INTERFACE defined in X25 mode.

With ISDN board, only the fisrt descriptor of the board
SPEED By default = EXT This parameter is not used with ISDN board.
PACKET SIZE max 1024 Maximum negotiable outgoing packet size, in bytes.
With ISDN board, available PACKET SIZE are 128, 256,
512 or 1024 bytes.
BANDWIDTH By default = 0 Identical to an TYPE/ X25 descriptor and
SUB TYPE/ XIO
V54 MODEM By default = NO This parameter is not used with ISDN board.
ADDRESS DCE or B The link descriptor is a logical DCE.
Use DCE mode with the ISDN board (without V25.Bis)
Use AUTO in transparent with V25.Bis mode.
max 32 With "ISDN" option board
OPTIONS By default = NONE Identical to an TYPE/ X25 descriptor and
SUB TYPE/ XIO
MODM Do not use with "ISDN" board.
INIT FRAME By default : SABM This parameter is not used with ISDN board.
T1 By default = 30 This parameter is not used with ISDN board
T3 By default = 60 This parameter is not used with ISDN board
TRIES By default = 10 This parameter is not used with ISDN board
(N2 of X.25)
K LEVEL2 By default = 7 This parameter is not used with ISDN board
K LEVEL3 By default = 2 Use the same window size that the window size used
value of 1 to 7 in LINK table of "ISDN" option board.
E Page 11-4
E
LINE GROUP
LCGN
LCN OFFSET
By default = 0
By default = 0
By default = 0
Threshold for number assigned to the first logical
resource attached to the link.
1 With the "ISDN" option board
ADDRESS GROUP By default = 0 Identical to an TYPE/ X25 descriptor and SUB TYPE/ XIO
FRAME SEQ By default = NORM This parameter is not used with ISDN board
CALL TIME OUT In seconds Call confirmation supervision timer (TP2).
By default = 5
60 Recommended with the "ISDN" option board
ERROR THRESHOLD By default = 20 This parameter is not used with ISDN board
LOOP BAR PRIORITY By default = 0 Call loop.
MANAGEMENT Identical to an TYPE/ X25 descriptor and SUB TYPE/ XIO
OPTIONAL TIMERS By default = NONE Implement optional timers.
T13 (60 seconds) Call clear confirmation packet timer in logical DCE mode
T13+T23 Recommended with the "ISDN" option board
OPTIONAL FLAGS By default = 0 This parameter is not used with ISDN board
E Page 11-5
E
11.5 ISDN board configuration
The configurator of a ISDN board can be used to modify or display the tables listed below.
The ISDN board configurator can be accessed via a channel or a virtual link running in native X.25
mode. The configurator is therefore always accessible via the "D" channel of the ISDN interface or via
the virtual link associated with the "D" channel.
The parameters for the ISDN adapter are saved on the board, in four tables:
• X25 links a routing identifier to an X.121 address outgoing on the ISDN.
• ROUT links a link number to a routing identifier.
• ISDN links a node name to an E.164 address (ISDN number).
• LINK links a set of X.25 link parameters to a node name.
There are three other read-only tables, as follows:

• HELP displays a summary of the configurator commands.
• STAT displays the current status of the virtual links (2B + D).
• MEMD displays the content of a memory area (use reserved).
To administer these tables, the configurator supports the following functions:

MGET displays the content of a table with no particular formatting.
INIT clears all of the current table.
DELE deletes the current line.
INSE inserts a blank line.
COPY copies the previous line.
Gxxx is used to go to line xxx of the current table.
LIST is used to display a table one page at a time.
CONF is for configuring (modifying) the content of a table.
DUMP displays the content of the X.25, LINK, ISDN and ROUT tables with no particular
formatting.
SAVE lows to safeguard modifications brought to the different tables (X25, etc. )
The configurator supports five "general" functions, as follows:

QUIT releases the link providing access to the ISDN board configurator, and safeguard
modifications brought to the different tables (X25, etc. ).
LOOP is used to set up a test loop.
CALL is used to set up a test call.
DISC is used to disconnect a test call.
ECHO is used to select echo mode.
E Page 11-6
11.6 Structure of the ISDN board tables
11.6.1 X.25 table syntax (ISDN board)
The "X.25" table for the ISDN board has 256 records.
A record in the "X.25" table (ISDN board) comprises two fields separated by a "space" character..
The "X.25" table (ISDN board) appears in tabular form:
NAME X121 ADDRESS

NAME 4 Identifier used by the routing function. alphanumeric
characters
The identifier "BE0∗" is reserved. It provides access to the (wildcard * possible)
ISDN board configurator.
The identifier "XXXX" is reserved; it is used to define a routing
in the absence of an originating ISDN number (PBXNB-CGP).
X121 15 X.121 address outgoing on the ISDN decimal
ADDRESS characters
(wildcards * and !
possible)
E Page 11-7
11.6.2 ISDN table syntax (ISDN board)
The ISDN table for the ISDN board has 256 records.
A record in the ISDN table (ISDN board) comprises two fields separated by a "space" character.
The ISDN table (ISDN board) appears in tabular form:
NAME E164 NUMBER

characters
(wild card * possible)
E164 20 ISDN number (NDI-CGP) or (NDS CDP) decimal
NUMBER characters the address and sub-address of which are separated by ":"
(wild card * and !
possible)
11.6.2.1 ISDN address of ISDN adapter
NAME E164 NUMBER

IDS0 ISDN number of the adapter.
Outgoing, this number is used as the originating user number (NDS-CGP).
Incoming, the number is used to identify the call, and is compared to the destination
number (NDS-CDP).
(wildcards * and 1 are prohibited)
An incoming call is rejected if it contains a destination number (NDS-CDP) that does not match the ISDN
number of the record with the NAME IDS0.
For a record "IDS0", when the numbers (that of the adapter and NDS-CDP) are of different lengths, the
match is based on the lower order digits of the longer number. For example, the number 0140771212
matches the number 40771212.
Changes to the IDS0 field do not take effect immediately. For this, the ISDN board must be reset. The
ISDN board can be reset by a Megapac BOOT sequence or by the command "STOP" on the 1st virtual
link of the board.
11.6.2.2 NAME = GIO1, GIO2
NAME E164 NUMBER

GIO∗ ISDN number
The names GIO1 and GIO2 are names reserved for routing frames in transparent mode.
E Page 11-8
11.6.3 LINK table syntax (ISDN board)
The LINK table of the ISDN board has 16 records.

A record in the LINK table (ISDN board) comprises ten fields separated by "space" characters.
The LINK table (ISDN board) appears in tabular form:

(wildcard * possible)
NBCH 1 to 4 Maximum number of virtual circuits decimal
PSIZ 1 to 4 Maximum packet size (128, 256, 512, 1024) decimal
K3 1 Level 3 window size (1 to 7) decimal
ADR 1 Link DTE / DCE mode. alphanumeric
• T : the link is DTE
• C : the link is DCE
• A : the link is DTE for outgoing calls, DCE for incoming
calls (AUTO)
• R : the link is DCE for outgoing calls, DTE for incoming
calls (REVERSE).
T25 1 to 2 Inactivity timer T1 (1 to 999 seconds) decimal
ISDN call clearing timer, effective after clearing the last virtual
circuit (of an active B channel)
N2 1 to 2 Number of level 2 retries (1 to 20) decimal
T1 1 to 3 Timer T200 (1 to 80 seconds) decimal
Level 2 frame retry timer (Lap B)
EXT 1 to 3 Extended mode (modulo 8 to 128) alphanumeric
1LCN 1 to 4 Number threshold assigned to the first logical resource decimal
attached to the link (LCN OFFSET>0). (1 to n)
For the B channels, when the LINK table is used and there is no corresponding node name a default
profile is used.
E Page 11-9
For the D channel, a profile can be specified in the LINK table. The node name TEI∗ must be used to
establish this profile. Changes to the TEI∗ field do not take effect immediately. For this, the ISDN board
must be reset. If there is no node name TEI∗, a default profile is used.
Likewise, for the "leased line" service (specifically Germany D64S), a profile can be specified in the LINK
table. The node name CHB1 (or CHB2) must be used to set the profile of channel B1 (or B2).
The ISDN board can be reset by a Megapac BOOT sequence or by the command "STOP" on the 1st
Default profile parameters B channels D channel

• Maximum number of virtual circuits 16 16
• Maximum packet size 128 128
• Level 3 window size 2 2
• Link DTE / DCE mode AUTO DTE
• Inactivity timer "T25" 6 sec 6 sec
• Number of retries at level 2 10 10
• Frame retry timer "T1" 1 sec 1 sec
• Extended mode Modulo 8 Modulo 8
• Number threshold assigned to the first logical 1 1
resource attached to the link (LCN OFFSET).
E Page 11-10
11.6.4 ROUT table syntax (ISDN board)
The ROUT table for the ISDN board has 16 records.

A record in the ROUT table (ISDN board) comprises seven fields separated by "space" characters.
The unused fields must contain at least "hyphen" characters.
The ROUT table (ISDN board) appears in tabular form:

NAME 4 Identifier used by the routing function alphanumeric
(fixed) or (wild card * possible)
Node name used by the routing function
KEY 2 or 3 Identification key alphanumeric
IN: for selecting a descriptor for an incoming call (necessary
for incoming call filtering)
OUT: use reserved
(used with the "OPT" field, the KEY=OUT field can be used to
define an outgoing call on a B channel in packet mode)
LLP: to force the use of one of the 2 B channels into leased
line mode.
TEI: to define a TEI number for the D channel
FUN 1 to 4 Function alphanumeric
(nothing, 1 to 3, *)
SEL 1 to 4 Selection alphanumeric
(nothing, CAD)
OPT 1 to 3 Option alphanumeric
(nothing, PAQ)
ROUT 1 to 4 Route (reserved)
DEST 1 to 4 Destination (reserved)
E Page 11-11
11.6.4.1 Incoming call routing ("IN" key)
For the "IN" key, the "FUN" function field indicates:
FUN meaning
1 use the 1st virtual link
2 use the 2nd virtual link
∗ use the 2nd virtual link if free, otherwise the 1st
nothing or - the call is rejected
For the "IN" key, the "SEL" selection field indicates:
SEL meaning
CAD When the address of the caller does not exist, the NDI of the installation is used
as the calling address in the X.25 call request packet.
nothing or - In the X.25 call request packet, the address of the caller is unchanged.
11.6.4.2 Outgoing call mode ("OUT" key)
For the key "OUT", the "OPT" option field indicates the mode of the call in the B channel:
OPT meaning
nothing The outgoing call on the B channel is in circuit mode
(circuit mode is selected by default)
PAQ The outgoing call on the B channel is in packet mode (specifically for Germany)
(similar to packet mode in a D channel)
E Page 11-12
11.6.4.3 D channel parameters ("TEI" key)

Identifier name TEI 3 TEI number - = 2B+D
∗∗∗∗ by default 01 to 62 D = no B channels
The D channel of the ISDN interface works in permanent logical link (PLL) mode.
The "TEI" key record does not take effect until the ISDN board is reset.
If this record does not exist, calls cannot be made on the D channel.
When the network causes of a loss of "TEI", the message "CARRIER LOSS" is displayed on the
Megapac supervisory console, provided that the "DCD" option has been assigned to the link descriptor
associated with the D channel. After a loss of "TEI", the D channel cannot be used until the ISDN board
has been reset.
The ISDN board can be reset by a Megapac BOOT sequence or by the command "STOP" on the 1st
11.6.4.4 Leased line mode parameters ("LLP" key)
The "leased line" mode is a specific service of Germany (D64S). It allows a physical connection of a B
channel to be set up on the S0 bus, with the other B channel not being used. The "leased line" mode is
used to relay X25 and HDLC protocols in transparent mode.
In "leased line" mode, the identifier name must be "CHB∗".

Identifier name LLP B channel number
CHB∗ 1
2
∗ (both)
This record is used to force the use of one of the 2 B channels into leased line mode.
Recording of the "LLP" key is only registered after reset of the GIS board.
If this record does not exist, the B channels cannot be used in leased line mode.
11.6.4.5 Example of ROUT table "LIST"

TOTO IN 1
E
TATA OUT - - PAQ
TUTU TEI 3 54 -
ISDN board for Megapac ESL - Megafrad Page 11-13
E
11.7 Statistics
The STAT table for the ISDN board has three records.
This table is read only. It provides access to statistical information concerning the links associated with
channels B1 and B2 and the D channel.
The statistics are displayed in tabular form:
L TYPE NAME STATE CAUSE LCN 1LCN PS K ADR EXT
L number Number of data links connected.

from 0 to 3
0 = no connection
3 = connection on D
TYPE operating mode X25 = for native X.25 mode.
HDLC = for transparent mode without V.25 Bis.
V25 B = for transparent mode with V.25 Bis.
NAME name name of the node to which the current call is connected.
or "nothing"
"nothing" if there is no connection.
STATE DISC, IN, OUT, DISC = no current connection (B or D channel)
PRO, CNX, IN = incoming ISDN call (B channel)
READY OUT = outgoing ISDN call (B channel)
PRO = call being set up (B channel)
CNX = B channel connected
READY = D channel connected
CAUSE L or R with an hexadecimal type of disconnection.

number
L = local
R = remote
cause of disconnection, compliant with Q.931.
The information below is specific to the native X.25 mode.
LCN number of resources set up 01 to 99
1LCN (LCN OFFSET). 1 to 4095
PS Max packet 128, 256, 512, 1024
size
K3 Level 3 window 1 to 7
ADR DTE or DCE mode DTE
DCE
E
EXT Extended mode E = modulo 128
nothing = modulo 8
E
11.8 Help
The "HELP" table for the ISDN board has 35 records.

This table is read only. It can be used to display the various commands available from the ISDN board
configurator.
The "HELP" is displayed in tabular form:
Commands ISDN board software release number

ECHO Set echo on, or Set echo off
QUIT Quit VCP
CALL Set up a test call
DISC Release the test call
LOOP Set / Remove test loopback
MGET Dump table
DUMP Dump all tables
INIT Erase current table
DELE Erase current record
INSE Insert new record
COPY Duplicate current record
Gxxx Go to record xxx
LIST Display table
CONF Configure mode
SAVE Save all tables modified
LOAD, RUBP, reserved
RUN, HALT
X25 Change to X25 table
ISDN Change to ISDN table
LINK Change to LINK table
ROUT Change to ROUT table
STAT Display STAT table
MEMD Display memory contents from xxxxxx (use reserved)
HELP Display this table
0x08 ← Erase character
0x0D ↵ Validate entry
0x1B Esc Escape from command

0x15 ^\ Copy current character
0x20 space Field separator
0x2F / Repeat current command
E
0x3C > Next record
0x3E < Previous record
0x40 @ Transparency character
E
11.9 Details of commands
11.9.1 Table management commands
MGET This command is used to display the entire content of a table, without pausing, with no
header and with no current line indication.
The display always begins from the first line of the current table.
DUMP As MGET for the X25, LINK, ISDN and ROUT tables.
INIT The INIT command is used to clear all of the current table.
Only the modifiable tables (X25, ISDN, LINK and ROUT) can be deleted.
DELE The DELE command is used to delete the current line.
The current line is deleted and the content of each line that follows is copied to the previous
line. The last line becomes blank.
INSE The INSE command is used to insert a blank link at the current line position.
The current line is replaced by a blank line.
COPY This command is used to copy the current line.
The current line is unchanged.
Gxxx This command is used to go to the specified line.
The number of the new current line is given by "xxx".
When the number "xxx" is greater than the number of records in a table, the command
takes you to the last record in the table.
LIST This command is used to display one page of the current table, from the current line.
The header of the table is displayed at the top of each page, and the prompt is displayed at
the beginning of each line. On each page, a pause for any character is implemented
before the next page is displayed.
CONF This command is used to configure (modify) the content of a table.
The content of the current line prefixed by the prompt character is displayed, followed by
the pause character "/". The characters, apart from special characters, are temporarily
buffered, and then when committed, they replace the current line.
SAVE This commands allows to safeguard the totality of information of all tables.
E Page 11-16
E
11.9.2 "General" management commands
QUIT
This command is used to clear the link providing access to the ISDN board configurator,
and safeguard modifications brought to the different tables (X25, etc. ).
The link providing access to the configurator is also released after inactivity for longer than
three minutes.
LOOP This command is used to set up or clear a test loop between transmission and reception on
a channel.
This command is useful for approval tests.
CALL This command is used to initialize a test ISDN call.
This command is useful for approval tests; the ISDN destination number must be defined in
a NAME = TEST record. The node is defined by the "ROUT" table.
DISC This command is used to clear a test call.
This command is useful for approval tests. If there is no test call in progress, another
current call is cleared.
ECHO This command is used to enable or cancel character echo mode.
By default, with each new connection, echo mode is not enabled.
LOAD These commands are reserved for a ulterior usage.

RUBP
RUN
HALT
11.9.3 Dialogue
Prompt The configurator displays a prompt text comprising:

• the name of the current table,
• followed, between brackets, by the number of the current line,
• ending with the ">" sign.
The configurator is then ready for a command line with one or more four-character key
words, separated by one or more spaces. The key words can be a table name and an
operation or a command. The command line is committed by the "CR" character, and each
key word is interpreted in order of entry.
Navigation A "table name" key word can be used to change current table.
The current line number and the current operation type are always retained. Because of
this, with a change of table, the last current operation remains active.
The "MEMD" table must be followed by a hexadecimal number on 1 to 8 characters
defining the starting address of the memory block to be displayed.
E Page 11-17
E
11.9.4 Special characters
Carriage Return
The "CR" character confirms the content of the input buffer.

↵ At the prompt, the input buffer contains key words analyzed and interpreted after
committal by the "CR" character.
In configuration mode, the input buffer contains the new content of the current line.
Backspace The "←" character can be used to delete the last character entered in the input
buffer.
←
Slash The "/" character can be used to repeat the previous command line.
/ In configuration mode, if this character is the last character entered by the operator,
it is interpreted as an escape character: return to the prompt without cancelling
configuration mode.
Esc The "Esc" character cancels the current command and the current table.
By default, the current table is the "HELP" table, the current line is the first line of
the table and no operation is in progress.
The "Esc" character can also be used to exit "LIST" or "CONF" mode.
Space The "Space" character is used to separate key words in a command line.
In configuration mode, it can also be used to separate the fields of the current
record, or leave one or more fields blank.
> At the prompt, or in configuration mode, when the current line is empty, these
characters can be used to move to the next line ( > ) or the previous line ( < ).
<
Otherwise, these characters are normally entered in the input buffer.
Ctrl Back Slash In configuration mode, the "^ \" character is used to copy the character in the same
position of the current line to the input buffer.
^\
Commercial at In configuration mode, the "@" character is used to enter special characters in the
input buffer. The character after "@" is entered in the current line without being
@
interpreted as a special character. The "@" character is not copied to the input
buffer (or into the tables).
When displaying a table, the special characters are prefixed by the "@" character.
Ctrl All the control characters, apart from those described previously, are not supported
("ERROR" message displayed).
E Page 11-18
11.10 Access to the ISDN board configurator
The configurator can be accessed:

• through a native X.25 call in which the USER DATA takes the form "BE0∗", or
• through a native X.25 call in which the X.121 call number is that of the configurator.
11.10.1 Native X.25 call in which the USER DATA takes the form "BE0∗"
When a ISDN board is commissioned, the ISDN and X.25 tables (ISDN board) are empty.
A native X.25 call to one of the resources of the three descriptors of the ISDN board, with USER DATA in
the form "BEO*" can always be used to access the ISDN board configuration functions.
To return to the example of a Megapac ESL with one ISDN board, the Megapac X.25 table contains the
following records:

GROUP

ISDN board)
• a call to resource B1G1 provides access to the configurator of the ISDN board,
E Page 11-19
11.10.2 Native X.25 call in which the X.121 call number is that of the configurator
A node with a name that takes the form "BE0∗" provides access to the ISDN board configurator.
After first accessing the ISDN board's configurator using the previous method, it is then possible to place
a record in the X.25 table (ISDN board), specifying:
• an identifier in the form "BE0∗",
• an X.121 number to call the node.
To return to the example of a Megapac ESL with one ISDN board, the X.25 table of the ISDN board
contain the following record:
X.25 table of the ISDN board

X25(00): BE0∗ 101
The Megapac's X.25 table contains the following records:

GROUP
B1G1 0 101
descriptors of the ISDN board)
• a call to number 101 provides access to the configurator of the ISDN board,
E Page 11-20
E
11.11 Routing
The adapter can be used to relay calls (in native X.25, transparent without V.25 Bis mode and
transparent with V.25 Bis mode) between three virtual links (three descriptors) of the Megapac switch,
and the two "B" channels and the "D" channel of the "S0" interface. The "D" channel supports only the
native X.25 mode.
Calls from the Megapac ESL over a virtual link (resources of one of the three descriptors), are routed to
the channel associated with it, and only to that channel.
Similarly, calls received over a channel are all routed to the same virtual link (resource of one of the
three descriptors) of the Megapac.
11.12 Call from the Megapac end (B and D channel virtual link)
11.12.1 Call from a "B" channel virtual link in native X.25 mode

• If it is present in the corresponding field of an X.25 table (ISDN board) record, the associated
identifier name is used.
• Otherwise, the USER DATA is examined, and if in the form "BE0*", the call is connected to
the ISDN board configurator.
• If the associated identifier name is in the form "BE0∗", the call is connected to the ISDN board
configurator.
• If no call is in progress:
• The identifier is strictly compared with the node names in the ISDN table to find a
destination ISDN number. When an IDS0 record exists, the associated number is used as the
originating number (NDS-CGP).
• The node name found is assigned to the channel.
• The ISDN board initializes:
• the ISDN call in CIRCUIT mode by default, or in PACKET mode if the ROUT
table contains a record corresponding to the node name of the channel, with
the fields KEY=OUT and OPT=PAQ,
• then the X.25 call in a B channel with the X.25 characteristics of the link
associated with the node taken from the LINK table. When the LINK table
has no record for this node, the default profile is used.
• If there is no correlation between the identifier and the node names in the ISDN table, the
native X.25 mode call is rejected.
• If there is a call already in progress on the associated channel, the associated node name must be
compatible with the identifier, otherwise the X.25 call is cleared by the adapter.
When the last X.25 call on a channel is cleared, the ISDN call is cleared after the inactivity time-delay
(timer T25).
E Page 11-21
11.12.2 Call from a "B" channel virtual link in transparent mode without V.25 Bis
When a frame in transparent mode without V.25 Bis from the Megapac is offered:
• The identifier GIO1 is used for the 1st virtual link, the identifier GIO2 is used for the 2nd
virtual line.
• The identifier (GIO1 or GIO2) is strickly compared with the node names in the ISDN table,
to find a destination ISDN number. When there is an IDS0 record, the associated number is
used as the originating number (NDS-CGP).
• If there is no record approaching GIO1 or GIO2 in the ISDN table, the frame from the virtual
link is rejected.
The ISDN board initializes the ISDN call in CIRCUIT mode by default, or in PACKET mode if the ROUT
OPT=PAQ.
The ISDN call is cleared after the link inactivity time-delay.
11.12.3 Call from a "B" channel virtual link in transparent mode with V.25 Bis
When a frame in transparent mode with V.25 Bis from the Megapac is offered:
• The frame received is interpreted as a V.25 Bis command.
• When the "CRN" command is recognized, the "VAL" and "CNX" indications are sent over the
virtual link, and the destination number taken from the "CRN" command is used as the
destination ISDN number.
When there is an IDS0 record, the associated number is used as the originating number
(NDS-CGP).
The node name used is the one found in the ISDN table, corresponding to the destination
ISDN number. By default, the node names GIO1 and GIO2 are used according to the origin
of the frames (1st or 2nd virtual link).
When the ISDN call is rejected by the network, the indication "CFI" with the cause is sent over
the virtual link.
The ISDN board initializes the ISDN call in CIRCUIT mode by default, or in PACKET mode if the ROUT
OPT=PAQ.
The ISDN call is cleared after the link activity time-delay.
E Page 11-22
11.12.4 Call from the "D" channel virtual link in native X.25 mode
Presence of this record enables the "packet in D" function.
• If it is included in the corresponding field of a record in the X.25 table (ISDN board), the
associated identifier name is used. When the identifier is "BE0*", the call is connected to the
ISDN board configurator.
• Otherwise, the USER DATA is examined, and if in the form "BE0∗", the call is connected to
the ISDN board configurator.
• When the identifier is found:
• The identifier is compared with the node name of the record in the ROUT table having the
key "TEI".
• When the identifier and the node name are compatible, the "packet in D" call is initialized,
otherwise the native X.25 mode call is rejected.
The X.25 profile on the D channel is the one in the "TEI∗" record of the LINK table, if any, or the default
profile.
E Page 11-23
11.13 Call from the ISDN end (B and D channels)
11.13.1 Call from the "B" channel
An ISDN call is accepted when:

• The adapter does not have a specific ISDN address (no "IDS0" record).
• The adapter has a specific ISDN address (the "ISDN" table has an ISDN address record with the node
name "IDS0"), and the destination address of the ISDN call received (the NDS-CDP) corresponds to
the adapter's ISDN address.
An ISDN call is not accepted when the adapter has a specific ISDN address and the destination address
of the ISDN call received (NDS-CDP) does not match the ISDN address of the adapter.
When an ISDN call is accepted, the originating ISDN number (NDI-CGP) is examined.
• NDI-CGP is present, the call is from the public network.
• NDI-CGP is absent, the call is from a private network.
When the NDI-CGP number is present:

• The "ISDN" table (ISDN board), for this NDI-CGP, indicates a specific node name.
• Otherwise, the node name "XXXX" is used for routing requirements.
When the NDI-CGP number is absent:
• The node name "XXXX" is used for routing requirements.
When the node name is specific, the ROUT table (key = IN) indicates whether the call is accepted or
When the ROUT table has no record for the specific node name, the call is rejected.
When the node name is "XXXX", the ROUT table (key = IN) indicates whether the call is accepted or
When the ROUT table has no record for the node name "XXXX", the call is accepted as a priority on the
2nd virtual link if free, and on the 1st link otherwise.
The associated virtual link indicates the mode (native X.25, transparent with or without V.25 Bis).
E Page 11-24
11.13.2 Call accepted from the "B" ISDN end and relayed in native X.25 mode
The node name found previously is looked up in the LINK table to determine the X.25 parameters to be
used on the B channel. If there is no corresponding node name, the default profile is used.
The B channel can then accept X.25 calls.
When the destination address for a native X.25 mode call matches the identifier "BE0∗" (ISDN board’s
X.25 table), the call is connected to the ISDN board configurator. Otherwise the call is relayed to the
associated virtual link.
11.13.3 Call accepted from the "B" ISDN end and relayed in transparent mode
without V.25 Bis
The frames are relayed transparently between the B channel and the associated virtual link, with no flow
control.
11.13.4 Call accepted from the "B" ISDN end and relayed in transparent mode
with V.25 Bis
The V.25 Bis "INC" and "CNX" indications are sent over the associated virtual link.
After sending the "CNX" indication, the frames are relayed transparently between the B channel and the
11.13.5 Call from the "D" channel
The presence of this record enables the "packet in D" function.
When a native X.25 mode call from the "D" channel is offered:
• If it corresponds to the identifier "BE0*", the call is connected to the ISDN board configurator.
• Otherwise the call is relayed to the associated virtual link.
E Page 11-25
11.14 Typical native X.25 mode configuration in a B channel
Called 999
X25
S
RNIS
(NDI=65773333)
ISDN Network
S RNIS
(NDI=65772222)
Figure 11-2 Typical ISDN board configuration in native X.25 mode
In the above example, the terminal generates an X.25 call in which the "called number" is "999".
The originating Megapac ESL is connected to the ISDN and its NDI is 01.65.77.33.33.
The terminating Megapac ESL is connected to the ISDN, its NDI is 01.65.77.22.22 and it accepts only
ISDN calls from subscriber 01.65.77.33.33 (in other words, the originating Megapac ESL).
E Page 11-26
11.14.1 Originating Megapac ESL configuration
The X.25 call request packet contains the called address "999".
The Megapac ESL's X.25 table includes a record as follows:
G110 0 999
"G110" is a resource of a descriptor which corresponds to the B1 channel of a ISDN board.
The ISDN board's X.25 table includes a record as follows:
NAME X121 ADDRESS

DEST 999
"DEST" is a routing identifier for called number "999".
The ISDN board's ISDN table includes a record as follows:
NAME E164 NUMBER

DEST 0165772222
For the called number "999", call ISDN subscriber "0165772222".
The ISDN board's LINK table includes a record as follows:

DEST 16 512 7 A 10 10 1 8 1
For the called number "999", the X.25 call in the B channel is based on the above characteristics (16
Note:
In this example, the outgoing call is set up in circuit mode so there is no need for a record in the ISDN
board's ROUT table.
E Page 11-27
11.14.2 Destination Megapac ESL configuration
The ISDN call reaches the destination Megapac ESL with the originating ISDN number (NDI-CGP)
01.65.77.33.33.
The ISDN board's ISDN table includes a record as follows:
NAME E164 NUMBER

ARR1 0165773333
Because the ISDN call is from the public network, NDI-CGP is included and the ISDN table indicates a
node name "ARR1" for this NDI-CGP.
The ISDN board's ROUT table includes a record as follows:

ARR1 IN 1
For NDI-CGP "01.65.77.33.33", the call is accepted (KEY=IN), and the first virtual link is used.
The ISDN board's link table includes a record as follows:

ARR1 16 512 7 A 10 10 1 8 1
For NDI-CGP "01.65.77.33.33", the X.25 call in the B channel is based on the above characteristics (16
Note: These characteristics must be the same as those defined for the outgoing call.
To terminate routing of the source X.25 call, the X.25 table of the destination Megapac ESL includes a
record as follows:
P400 0 999
"P400" is a resource of an X.25 link descriptor corresponding to subscriber "999".
Note:
At the incoming end, the ISDN board's X.25 table is not used.
E Page 11-28
12. "PRI-64" (30B+D) primary access board
The basic "PRI-64" board for the Megapac VME provides one T2 primary access (30 B channels).
The "PRI-64" board can be equipped with a daughter board to provide two T2 ports (60 B channels).
The Megapac VME can be equipped with 2 "PRI-64" boards (maximum 120 B channels).
A primary rate access can be used:

• in switched circuit mode (T2 - ISDN) with 30 B channels for data and the D channel for signalling, or
• in permanent circuit mode (E1 - G.704) with B channels of the primary rate access interface grouped
by configuration.
Depending on the ISDN (Numéris) user subscription, the number of B channels can be reduced to less
than 30 channels of a primary access.
12.1 Preliminary
• By default, the memory size allocated to the configuration of the descriptors and resources of a
Megapac VME is 20,430 bytes (see chapter 3).
Depending on the number of XIO boards used, and the number of T2 ports connected, the default
size may be insufficient. For two T2 ports, a value of MEM SIZE/ 40,000 is recommended.
• It is recommended to declare the T2 primary access board descriptors (SUB-TYPE/ PRI) after the
PS01 and PS02 descriptors.
• Concurrent "T2-ISDN" and "E1-G.704" operation on the same 2 Mbit/s link is not allowed.
• The sections dealing with the TYPE/X25 and HDLC descriptors describe the special settings of the
T2 board.
"PRI-64" (30B+D) primary access board
E Page 12-1
E
12.2 « T2-ISDN » operation
12.2.1 Declaration of PRI-64 board descriptors
The descriptors of the B channels of the PRI-64 board may be declared without registering the position of
the PRI-64 board in the VME shelf.
The system always proposes a default configuration consisting of two PS01 and PS02 descriptors of
TYPE/ X25 and SUB-TYPE/ XIO.
12.2.2 Configuration of a primary access (30B+D)
The basic "PRI-64" primary access board provides access to 30 B channels, but the ISDN (Numéris)
subscription may involve the reduction of the number of B channels (10 in this example).
NAME TYPE SUB-TYPE NPI SPEED CHANNELS OPTIONS ECM

IA01 X25, HDLC PRI YES EXT n NONE / CRC4 IN+V25B
IA02 X25, HDLC PRI NO n IN+V25B
E Page 12-2
12.2.3 Configuration of 2 primary accesses (30B+D)
The "PRI-64" board with the option "second T2 port" allows up to 60 B channels, but the ISDN (Numéris)
subscription may involve the reduction of the number of B channels (40 in this example).

IB01 X25, HDLC PRI NO n IN+V25B
E Page 12-3
12.2.4 Configuration of 4 primary accesses(30B+D)
The NEW PHYSICAL INTERFACE (NPI) is at YES for the first B channel of each board.

à X25, HDLC PRI NO n IN+V25B
IC01 X25, HDLC PRI YES EXT n NONE / CRC4 IN+V25B
IC02 X25, HDLC PRI NO n IN+V25B
ID01 X25, HDLC PRI NO n IN+V25B
12.2.5 Identification of the Numéris (ISDN) caller
A record in the MAC table, with the function "NDI", must be configured in the Megapac in order for ISDN
caller identification to be possible. With the PRI-64 card, the network origin number (NDI-DR) alone is
available.
E Page 12-4
E
12.3 "E1 - G704" operation
In this mode of operation, channel 0 is reserved for 2 Mbit/s link synchronization and channel 16 cannot
be used.
Concurrent "T2-ISDN" and "E1-G.704" operation on the same 2 Mbit/s link is not allowed.
On the same PRI-64 board, for one 2 Mbit/s link to be used in "T2-ISDN" mode and another 2 Mbit/s link
to be used in "E1-G.704" mode, the first link must be in T2 mode and the second link in E1 mode.
PRI-64 board operating mode Port "B" Port "A"

2 Mbit/s link - basic board 2 Mbit/s link - daughter board
Two "T2-ISDN" T2-ISDN T2-ISDN
One "T2-ISDN" and one E1-G.704" T2-ISDN E1-G704
Two "E1-G.704" E1-G704 E1-G704
To set up a link for "E1-G704" operation, you must define one descriptor for each group of 64 kbit/s
channels.
For this descriptor, a record in the MAC table (PU function) specifies the 64 kbit/s channels used in the
group.
12.3.1 Typical configuration
The following example represents a configuration comprising:

• six descriptors, IA01, IA02, IA03, IA04, IA05 and IA06, associated with the 2 Mbit/s interface of the
basic board,
• one descriptor, IB01, associated with the 2 Mbit/s interface of the daughter board.
Assignment of timeslots on the 2 Mbit/s link of the PRI-64 basic board (B)
TS 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31
IA01
IA02
IA03
IA04
IA05
IA06
Assignment of timeslots on the 2 Mbit/s link of the PRI-64 daughter board (A)
TS 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31
IB01
E Page 12-5
E
Descriptors configuration
NAME
IA01
IA02
TYPE
X25, HDLC
X25, HDLC
SUB-TYPE
PRI
PRI
NPI
YES
NO
SPEED
EXT
EXT
CHANNELS
n
n
OPTIONS
NONE
NONE
ECM
NONE
NONE
IA03 X25, HDLC PRI NO EXT n NONE NONE
IB01 X25, HDLC PRI NO EXT n NONE NONE
Associated MAC table

IA01 PU NONE 1 31
IA02 PU NONE 1 1,2,3,12,17,26,27,28
IA03 PU NONE 1 29,30
IA04 PU NONE 1 4,5,6,7,8,9,10,11
IA05 PU NONE 1 13,14,15,18
IA06 PU NONE 1 19,20,21,22,23,24,25
IB01 PU NONE 2 1,2,3,4,5,6,7,8,9,10,11,12,13,-
IB01 NOP NONE 2 14,15,17,18,19,20,21,22,23,24,-
IB01 NOP NONE 2 25,26,27,28,29,30
Format of the records in the MAC table
XXXX PU NONE 1 or 2 string of numbers (1 to 15 and 17 to 30)

separated by a comma
link link operation 1 for the first port specifies the channels assigned to the descriptor
descriptor in "E1-G704" (B channel) of
name mode the PRI-64 board the GENERATOR field can span several records,
with a hyphen "-" after the comma at the end of
2 for the second each record.
port (A)
To register the MAC record (PU function) you must reboot the Megapac.
When rebooted, the MAC record (PU function) is interpreted, and may cause an error message to be
generated (SELECTOR field empty or other than 1 or 2, channel numbers not in the list, channel number
duplicated, syntax error in GENERATOR field, etc).
An MAC table error causes:

• a diagnostic message (hh:mm:ss DD/MM/YY XXXX PRI MAC ERROR) where XXXX = descriptor
name,
• the message to be stored in the ELOG file,
• a level 1 NMS alarm to be generated,
• the descriptor to be taken out of service.
E Page 12-6
13. TYPE/ HDLC descriptor
13.1 General
The Megapac can be configured to support the HDLC (High Level Data Link Control) protocol.
All data received by the TYPE/ HDLC descriptor is placed in data packets and transmitted otherwise
unchanged to the network.
The HDLC "descriptor" provides transparent transportation of any protocol within an HDLC or its SDLC
frame.
On an X.25 network, each frame is converted into a packet.
An HDLC "descriptor" must have only one "resource". On one side of the network, the "resource" is
incoming and on the other, it is outgoing.

Name Settings
NAME 4 characters Link name.
TYPE HDLC Defines the link type.
XIO, SCC or NONE
VIO HDLC Virtual input - output descriptor.
Used to perform protocol conversion.
the board.
XIO The descriptor addresses an XIO board.
SIO The descriptor addresses an SIO board.
XIO+SIO Do not use for a link of type HDLC.
PRI The descriptor addresses a PRI-64 board for this link. A PRI-64
board allows the connexion of 1 or 2 T2 primary accesses
(30B+D) on the VME Megapac.
For each Primary access from 1 to 30 SUB TYPE/ PRI descriptors
must be configured.
E
The first descriptor of PRI-64 board (1 or 2 T2 accesses) must be
NPI/ YES. All the other descriptors of the same PRI-64 board
must be NPI/ NO.
TYPE/ HDLC descriptor Page 13-1
E
NEW PHYSICAL
INTERFACE
YES
by default = NO This descriptor shares the same link as previously defined in

HDLC mode.
A new HDLC link is assigned to this descriptor.
be set to YES.
With PRI-64 and GIS boards, only the fisrt descriptor of the board
SPEED Choice of : 2MHZ, Link operating speed, in bits per second.
1MHZ, 512K, 256K, With an SIO board, the limit is 19 200 bit/s.
128K, 64K, 48K, 19.2,
9600, 4800, 2400, With an XIO-E board, the possible speeds are 9600 to 2 Mbit/s.
By default = EXT 2 Mbit/s.
2400 to 64 Kbit/s.
(T2 board) For a HDLC descriptor with SUB-TYPE=PRI-64 (T2 board) and
Megapac VME NEW PHYSICAL INTERFACE=YES, this parameter specifies the
SPEED=EXT Specifies the operating mode as DTE with external clock (the T2
board uses the network clock).
Is usually used when connected to an ISDN network.
SPEED=2MHZ Specifies the operating mode as DCE with internal clock (the T2
card uses the internal clock board).
It can be used in X21 and V35 interfave on the J1 and J2 ports.
mode (to a modem).
mode (to a modem).
TYPE/ HDLC descriptor
E Page 13-2
E
PACKET SIZE
Choice of: 32, 64, 128,

256, 512, 1024, 2048,
4096 or TRAN
Maximum outgoing packet size, in bytes.
When an incoming packet has a size greater than the setting, an
FRMR frame is generated (reject).
By default = TRAN Transparent to packet size.
Any packet size is accepted, up to the size of the internal buffers.
BANDWITH 0 to 32767. Not used with HDLC descriptor.
By default = 0
V54 MODEM By default = NO Enables or disables the facility to run V.54 tests on the link.
When this function is enabled, V.54 tests can be activated by the
commands V54L (local loop), V54R (remote loop) and then TEST
(activate test), and deactivated by the V54X command.
YES V.54 tests can be run on the link.
NO V.54 tests cannot be run on the link.
ADDRESS By default = DCE This parameter has no significance for an "HDLC" link descriptor.
Only one resource must be specified.
OPTIONS NONE By default
UI Attribute qualifying acceptance over the link of Unnumbered
Information frames, UI.
This option applies only to links on XIO, GIO modules and is
needed where the V.25 bis procedure is used on the link.
IDLE With an XIO card, this option allows to send « FF » permanent 1’s
instead of « 7E » flags after the reception of at least one « 7E »
flag.
CRC4 For a HDLC descriptor with SUB-TYPE=PRI (T2 board) and
(Megapac VME) NEW PHYSICAL INTERFACE=YES, this parameter specifies the
With CRC4 option = ETSI operating mode (Euro ISDN with
CRC4)
Without CRC4 option (NONE) = French without CRC4 operating
mode
CALL TIME OUT 2 to 200 Call confirmation timer (TP2).

In seconds Represents the maximum time waiting for a call confirmation in
By default = 5 response to transmission of a call request packet.
When the timer runs out, a clearing packet is sent to the local
DTE and to the remote DTE.

V25B This option activates the V.25 bis dialling facility in conjunction
TYPE/ HDLC descriptor is used by the V25B virtual descriptor to
send V.25 bis dialling information taken from the MAC table to the
E
The other parameters can retain their default settings
TYPE/ HDLC descriptor Page 13-3
13.3 Logical resource parameters
To set up a connection between two resources supporting HDLC communications:

• one logical resource must be the source of the call request packet,
• the other must be the destination.

Name Settings
NAME 4 characters Logical resource name.
DRC MASK 4 characters maximum Fully or partly identifies a destination resource, used for
By default = . . . . routing.
ABCD Calling logical resource

"CALL+PVC+STAT"
The call request packet requesting the setting up of the virtual
circuit between the two Megapacs will be sent to this logical
resource.
"ABCD" is the name of the destination resource.
.... Called logical resource
"OUT+PVC+STAT"
The DRC MASK is not used.
TERMINAL TYPE By default = ASYN Identifies the terminal type
This parameter has no significance for an "HDLC" link descriptor.
CIRCUIT TYPE By default = Main I/O characteristics of the resource.
CALL+STAT
CALL CALL: The resource originates the call to be used with the PVC
parameter.
PVC CALL+PVC. The resource sends the call when it detects
presence of data from the HDLC equipment.
STAT Optional. This supplies connection/disconnection statistics for the
resource defined in the SESSION STATISTICS parameter of the
BASE descriptor (resource EI01 by default).
OUT OUT+PVC. The logical resource is reserved for receiving
incoming calls.
others Other settings have no effect on an "HDLC" descriptor.
E Page 13-4
E
OPTIONS
IDLE
By default = NONE Level 3 operating options.

By default, no options required.
This option activates the time delay specified in the INACTIVITY
The caller specifies the routing by entering a service name (8
characters maximum). This name must correspond to an input of
the NAME table.
DRC MASK/ ABCD
ABCD is interpreted as a service name. This name must
correspond to an input of the NAME table.
other The other options do not effect the HDLC descriptor.
BUFFERS from 1 to 240 Setting determining the total number of buffers available for
By default = 2 use.
This figure must be multiplied by the agreed packet size to
determine the total number of HDLC bytes that can be stored.
CALL PRIORITY from 0 to 15 This parameter is not used by a resource receiving a call.
By default = 0
RESOURCE from 0 to 15 This parameter is not used by a resource originating a call.
BANDWITH 0 to 32767 Required bandwidth size in characters per second tenth.
By default = 0 Only towards an X25 link.
incoming resource : :
Bandwidth=0, no bandwidth guarantee is requested.
Bandwidth>0, allows to define the requested speed before routing.
E Page 13-5
13.4 Principle of an "HDLC" link

DRC MASK/ P200 DRC MASK/ ....
CIRCUIT TYPE/ OUT+PVC
NAME/ PS02
NAME/ PS01
TYPE/ HDLC
TYPE/ X25 (physical DTE,
...
... external clock)
NPI/ YES
NPI/ YES
CHANNELS/ 1
MEGAPAC
A
HDLC
Link

DRC MASK/ .... DRC MASK/ P900
CIRCUIT TYPE/ CALL+PVC
NAME/ PS08
NAME/ PS09
TYPE/ HDLC
TYPE/ X25 (physical DCE,
... internal clock)
...
NPI/ YES
NPI/ YES
CHANNELS/ 1
MEGAPAC
B
Figure 13-1 Example of an HDLC link
E Page 13-6
14. TYPE/ NFRM descriptors
The Megapac can be configured to support Frame Relay calls through an XIO, MIO, SIO interface board,
or system with SCC controller (Megapac ESL and Megafrad).
The MIO and XIO boards are recommended for high link speeds and for managing frames that are larger
than the system buffer size.
The Megapac frame relay operating modes are:

• Frame Relay link "switching" mode.
• Frame Relay IP and/or IPX "access point" mode (RFC 1490).
• Frame Relay « X25 access point » mode, with Q922 DL Core or owner encapsulation of the X25
protocol level 2 and 3 in Frame Relay. These modes require a virtual X25 descriptor ("VIO") to be
used between the X25 link and the Frame Relay link.
• the Q922 DL Core encapsulation is compliant with ANSI T1.617 annex G.
• the owner encapsulation (Transpac like) is compatible with RFC 1490 and allows protocol
multiplexing in the same DLCI.
• operating on specialized line and on ISDN (using a GIS card in HDLC-V25B mode).
In frame relay, the MegaPAC provides the following services:

• Switch mode operation and Frad mode operation in PVC configuration,
• LMI ANSI Annexe D and Group of Four management,
• FECN et BECN bytes management thanks to the introduction of a delay in case of a congestion,
• setting of the BECN bit sent in the event of internal congestion,
• CIR, Bc and Be management, the Megapac controls its outgoing flow to respect the contract,
• transparency or setting of the DE and CR bits,
• possibility to activate or deactivate a DLCI (STOP and RESTART commands).
• multiprotocol management, ANSI compliant X.25 and RFC 1490 compliant IP-IPX,
• X.25 proprietory multiplexing capability compatible with RFC 1490.
Note : In Frame Relay mode, the Megapac detects the connected or disconnected state of the
connecting cable.
For the link to be operational, for an X.25/V.11 interface, the IA signal must be asserted.
Similarly, for a V.24/V.28 interface, the CTS signal must be asserted.
TYPE/ NFRM descriptors
E Page 14-1
E
14.1 Frame format
To equally handle long IP frames, small X25 packets, SDLC, HDLC frames,... or asynchronous flows,
Frame Relay offers a frame with a variable length.
The DLCI corresponds to the notion of logical path number.
The basic frame is the following:
Flag Address Data FCS Flag

1 2 up to 4 bytes maxi 1600 bytes 2 1
DLCI C/R EA DLCI FECN BECN DE EA

6 bits (most significant bit) 1 1 4 bits (low significant bit) 1 1 1 1
Figure 14-1 Frame Relay frame format
Flag Flag (7E) for recognition of HDLC frame beginning and end,
DLCI Data Link Connection Identifier.
For a DLCI field coding on 2 bytes:
DLCI n° 0 is reserved for management channel (LMI),
DLCI n° 1 à 15 are reserved identifiers,
DLCI n° 16 à 991 are available for temporary or permanent virtual circuits,
DLCI n° 992 à 1007 are reserved identifiers for Frame Relay management,
DLCI 1008 à 1022 are reserved identifiers,
DLCI 1023 is reserved for higher layer management messages.
C/R Command / Response indication
EA Extend Address
FECN Forward Explicit Congestion Notification,
Congestion information to "destination" exchange.
BECN Backward Explicit Congestion Notification,
Congestion information to "source" exchange.
DE Discard Eligibility:
A Frame Relay access device enters a « DE » mark on frames, when the user rate reaches
a value between Bc and (Bc + Be). This mark points out that a rate superior to the contract
has been submitted by the user.
When a node gets in congestion, it first rejects frames with a « DE » mark.
FCS Frame Check Sequence.
E Page 14-2
E
14.2 Link management
The "LMI" (Local Management Interface) protocol is used to manage interfaces between two elements of
a Frame Relay network. This protocol based on a local polling checks especially the link status and the
various active virtual circuits status.
The network (DCE side) sends the state of the link and of the virtual circuits to the terminal (DTE side).
The interchange of LMI messages is unbalanced or balanced depending on the selected configuration.
Normally, the interface between the network and the user is unbalanced (UNI), whereas the interface
between two switches in the network is balanced (NNI).
Note: For a Frame Relay link with several DLCIs, the operating parameters of the LMI are those of the
descriptor for which NPI (New Physical Interface) is set to YES.
FRAD SWITCH SWITCH FRAD
DCE DCE
DTE dlci DCE dlci Frame Relay dlci dlci DTE
+ + DCE
(UNI) (NNI) Network (NNI) (UNI)
DTE DTE
full status
Figure 14-2 LMI interchanges, unbalanced on the FRAD side and balanced on the SWITCH side
FRAD SWITCH SWITCH FRAD
DCE DCE DCE DCE DCE DCE

+ dlci + + dlci Frame Relay dlci + + dlci +
DTE (UNI) DTE DTE (NNI) Network (NNI) DTE DTE (UNI) DTE
full status
Figure 14-3 LMI interchanges, balanced from end to end
E Page 14-3
E
14.3 Self-discipline principle
Frame Relay uses a simplified protocol in each switching node. No flow control is made on the
connections. Therefore a Frame Relay network is subject to congestion problems. To avoid this risk,
Frame Relay proposes self-discipline mechanisms for far-end equipment.
Each user subscribes to a « contract » which he commits himself to respect.

• The user shall not send in average more information than previewed in the contract,
• The operator shall convey at least the information quantity noticed in the contract.
When the user needs to get close to the rate ceiling set by his contract, he shall modify this contract in
order to switch to upper rate class.
Terminals or network access points have flow management functions to check that the quantity of
information sent on the network does not exceed the contract.
The network shall protect itself and be able to control the information flow of each user. The control
mechanism authorizes bursty traffic from the user, however any overflow shall remain in the contract
limits.
The contract Parameters:
« CIR » Committed Information Rate (characters / second number)

specify the average rate guaranteed by the network at connection on a 1 second period of
time.
« Bc » Committed Burst size (characters number)
This parameter describes the maximum number of bits which can be transmitted during a
period of time Tc. Thus, Tc = Bc/CIR. The Tc value choice depends on the type of
information to transmit.
« Be » Excess Burst Size (characters number)
This parameter describes the maximum number of bits which the network will try to
transmit in addition to the contract (Bc) during the period of time Tc.
Therefore, during the period of time Tc:

• Up to the Bc rate, the input flow is accepted, and its conveying is guaranteed,
• Between Bc and (Bc + Be), the input flow is accepted, frames receive a « DE » mark, conveying is
not guaranteed,
• Beyond (Bc + Be), the input flow is not accepted.
E Page 14-4
E
14.4 Switching mode
TYPE/ NFRM specifies a native operating mode. The resource of the NFRM descriptor with
PROTOCOL/ NONE specifies a transparent operating mode.
This is the mode to use to support a transparent Frame Relay link "switching" function.
Each descriptor can be used to define one DLCI.
In this mode, one descriptor contains only one resource.
14.4.1 Link configuration parameters

Name Settings
NAME 4 characters maximum Name of a "Frame Relay" link.
TYPE NFRM Native "Frame relay" function.
(SWITCH = exchange)
SUB-TYPE By default = XIO+SIO, Type of board that the descriptor must address.
XIO, SCC or NONE
VIO Virtual input - output descriptor.
GIO Usage reserved
XIO+SIO Does not have to be used for a link of type NFRM.
PRI Usage reserved
NONE Usage reserved
NEW PHYSICAL By default = NO This descriptor shares the same link as previously defined in
INTERFACE Frame Relay mode.
(NPI) Note: All descriptors sharing the same link must be in the same
mode (all DTE, all DCE).
YES A new Frame Relay link is allocated to this descriptor.
E Page 14-5
E
SPEED Choice of: 2MHZ,
1MHZ, 512K,
256K, 128K, 64K,
48K, 19.2, 9600,
4800, 2400, 1200,
Link operating speed, in bits per second.

With an XIO-VME board the speed is strap selectable 300 to 2 Mbit/s.
600, 300 or EXT. With an MIO board (SUB TYPE/ SCC) the possible speeds are 2400 to
By default = EXT 64 Kbit/s.
With a Megapac ESL or Megafrad (SUB TYPE/ SCC), the possible
speeds are 2400 to 256 Kbit/s.
V24 (J1 to J6) The V24 interface is used. it provides:
DCE+X21 The optional X21 interface of the J1 and J2 ports is used in DCE mode
(J1 to J2) (to a terminal).
DCE The optional V35 interface of the J1 and J2 ports is used in DCE mode
DTE+X21 The optional X21 interface of the J1 and J2 ports is used in DTE mode
(J1 to J2) (to a modem).
DTE The optional V35 interface of the J1 and J2 ports is used in DTE mode
CHANNELS 0 to 4096 In switching mode, the descriptor contains only one resource
By default = 1
ADDRESS 1 to 1022 Number of the DLCI used.
By default = 0 This number must be the same as the number of the DLCI used at the
other end of the link. The first 16 DLCIs are reserved for supervision
purposes.
For a given trunk, DLCI Number must appear in increasing order.
MODE By default = DTE The Frame Relay link acts as a DTE (Terminal side)
It is the DTE side that engages the local management interface (LMI).
A DTE must be connected to a DCE.
DCE The Frame Relay link behaves like a DCE (Network side).
The DCE side sends the status of the link and of the associated circuits
(Full Status).
A DCE must be connected to a DTE.
DCE+DTE The Frame Relay link behaves like a DCE and a DTE.
Each end sends a link status request and transmits the status of the
link and of the associated circuits(Full Status).
E
In this case, each end of the link must be DCE+DTE.
TYPE/ NFRM descriptors Page 14-6
E
LMI
YES
By default = NO Deactivates the local management interface (LMI).

Activates the LMI based on the original standard.
(ANSI T1.S1)
ANSI Activates the LMI based on the new standard.
(ANSI T1.617)
KEEP ALIVE 2 to 80 seconds Significant only if the LMI is active.
TIMER By default = 0 Specifies a time-delay in seconds (for example 3 seconds).
(T391 = T392) (recommended = 3) For the DTE, this delay is equivalent to the time between two LMI
frames « Status Enquiry ».
For the DCE, this delay is used to detect a disconnection.
POLL INTERVAL 2 to 80 Significant only if the LMI is active.
(N391 = N393) By default = 0 Specifies the interval at which a complete LMI message is sent DTE
"N" (Full Status Enquiry) or expected DCE side (Full Status Response).
(recommended = 6) A complete LMI message is exchanged every
N x KEEP ALIVE TIMER (for example, six time).
TRIES 0 to 80 LMI error threshold (must be ≤ N393).
(N392) By default = 0
Number of LMI receive failures beyond which the interface is declared
(recommended = 3) faulty (for example, three times).
BANDWIDTH 0 up to 32767 CIR « Committed Information Rate »
By default = 0 Average speed negotiated, on the link.
In characters per second tenth.
The MegaPAC carries out a control of the flow transmitted on the
DLCI, during a period of time « Tc »:
Tc « Committed rate measurement interval »
Tc = 10 Bc/CIR rounded up to the nearest second tenth
Tc = 1 sec. when Bc=0
Bc 0 à 32767 « Burst Commit »
By default = 0 Allowed maximum speed.
Be 0 à 32767 « Burst Excess »
By default = 0 Speed excess (in addition to Bc)
For the conveyance of data without any traffic burst (like the voice),
the Bc parameter will equal to 0.
E Page 14-7
Maximum speed in character per second = 10 BANDWIDTH (1 + Be/Bc).
Observation period « Tc » Maximum speed in character per second

Bc = BANDWIDTH Tc = 1 second Be = 0 Max Speed = 10 BANDWIDTH
Bc = 2 BANDWIDTH Tc = 2 seconds Be = 1/2 Bc Max Speed = 15 BANDWIDTH
Bc = 3 BANDWIDTH Tc = 3 seconds Be = Bc Max Speed = 20 BANDWIDTH
Bc = 4 BANDWIDTH Tc = 4 seconds Be = 2 Bc Max Speed = 30 BANDWIDTH
etc. etc. Be = 3 Bc Max Speed = 40 BANDWIDTH
Bc = 0 Tc = 1 second etc. etc.
14.4.2 Resource configuration parameters

Name Settings
NAME 4 alphanumeric Name of the logical resource
characters
maximum
DRC MASK 4 characters Fully or partly identifies a destination resource used for
maximum routing.
By default = . . . . When CIRCUIT TYPE = OUT+PVC
4 characters When CIRCUIT TYPE = CALL+PVC
PROTOCOL By default = NONE Identifies the type of protocol supported.
NONE in "switching" mode.
DSAP/ By default = 0 usage reserved (LLC2)
SSAP/ By default = 0 usage reserved (LLC2)
PU TYPE/ By default = NONE usage reserved (LLC2)
2.0 usage reserved (LLC2)
PRIORITY 0 to 7 Priority management when a DLCI sends several protocols.
By default = 0
0 By default, there is no priority between the protocols.
1 to 7 Enables a degree of priority to be assigned between the
protocols to be sent over a particular DLCI.
A weighting of 7 is highest priority and 1 is lowest priority.
E Page 14-8
E
CIRCUIT TYPE
CALL+STAT
CALL+PVC
By default = Identifies the resource's main I/O characteristics.
The resource name specified by the DRC MASK/ parameter is the

destination resource.
In SWITCH mode, CALL+PVC on both calling and called resources
enables the connection to be set up or re-established regardless of the
direction via which the data has arrived.
In this case, the two resources must have different CPs.
(for example, one resource with CP=1 and the other with CP=2)
OUT+PVC The NAME/ or this resource is used as destination resource of another
Megapac resource.
STAT Following a connection/disconnection, the statistics are generated and
sent to the resource defined by the SESSION STATISTICS/ parameter
of the BASE descriptor
OPTIONS By default: NONE The DE (Discard Eligibility) and CR (Command / Response indication)
bits are forced to 0 in transmit.
TRAN The Megapac is transparent to the DE, CR, FECN and BECN bits.
CR1 Used to force permanently to 1 the CR bit.
DE1 Used to force permanently to 1 the DE bit.
DEP Used to set the DE bit in event of CIR being exceeded.
The DE bit is set at 1 if, during the time interval TC, the transmitted
data quantity (burst size) exceeds BC (Burst Committed).
The DE bit is not set if the CIR is not defined (parameter BANDWIDTH
= 0).
TRAN+DEP Used to be transparent to the CR, FECN, BECN bits, and to set the DE
bit at 1 if the received DE bit is at 1 or when the BC is exceeded during
the TC interval.
TRAN+DEP+CR1 Used to force the CR bit to 1, and to set the DE bit at 1 if the received
DE bit is at 1 or when the BC is exceeded during the TC interval.
TRAN+CR1 Used to force the CR bit to 1 while remaining transparent to the DE,
FECN, BECN bits.
TRAN+DE1 Used to force the DE bit to 1 while remaining transparent to the CR,
FECN, BECN bits.
DEP+CR1 Used to force the CR bit to 1 and to set the DE bit when the BC is
exceeded during the TC interval.
DE1+CR1 Used to force DE and CR bits to 1.
BUFFERS Setting from 1 to Setting determining the number of buffers available to this resource.
240 40 for Ethernet and 4 Mbit/s Token Ring.
By default = 2 80 for 16 Mbit/s Token Ring.

By default = 0 In SWITCH mode, see CIRCUIT TYPE/ CALL+PVC
RESOURCE 0 to 15 Called line priority.
BANDWIDTH 0 to 32767 Not used in Frame Relay.

By default = 0
E
14.4.3 Examples of Frame Relay « switching » function

DRC MASK/ P500 DRC MASK/ P200
PROTOCOL/ NONE PROTOCOL/ NONE
CIRCUIT TYPE/ CALL+PVC CIRCUIT TYPE/ CALL+PVC
CALL PRIORITY/ 1 CALL PRIORITY/ 2

DLCI(a) TYPE/ NFRM TYPE/ NFRM DLCI(A)
SUB-TYPE/ XIO SUB-TYPE/ XIO
NPI/ YES NPI/ YES
ADDRESS/ DLCI(a) ADDRESS/ DLCI(A)
MODE/ DTE+DCE MODE/ DTE+DCE


DLCI(b) TYPE/ NFRM TYPE/ NFRM
SUB-TYPE/ XIO SUB-TYPE/ XIO DLCI(B)
NPI/ YES NPI/ NO
ADDRESS/ DLCI(b) ADDRESS/ DLCI(B)


DLCI(c) TYPE/ NFRM TYPE/ NFRM DLCI(C)
NPI/ YES NPI/ NO
ADDRESS/ DLCI(c) ADDRESS/ DLCI(C)
MEGAPAC
Figure 14-4 Frame Relay « switching » function
E Page 14-10
14.5 IP and/or IPX "access point" mode (RFC 1490)
TYPE/ NFRM with a resource specifying PROTOCOL/ IP or IPX, is used to transmit IP (TCP/IP) or IPX
(Novell) datagrams over a Frame Relay link. Document RFC 1490 describes this function.
IP and IPX multiplexing is possible on the same Frame Relay DLCI.
In this mode, one descriptor can contain two resources (one for the IP protocol the other for the IPX
protocol).

Name Settings
NAME Up to 4 characters Name of a "Frame Relay" link.
TYPE NFRM Native "Frame relay" function.
SUB-TYPE By default = XIO+SIO, Type of board that the descriptor must address.
XIO, SCC or NONE
GIO Usage reserved
XIO+SIO Does not have to be used for a link of type NFRM.
PRI Usage reserved
NONE Usage reserved
INTERFACE Frame Relay mode.
(NPI) Note: All descriptors sharing the same link must be in the same
mode (all DTE, all DCE).
YES A new Frame Relay link is allocated to this descriptor.
E Page 14-11
E
SPEED
1MHZ, 512K,
256K, 128K, 64K,
48K, 19.2, 9600,
Choice of: 2MHZ, Link operating speed, in bits per second.

4800, 2400, 1200, With an XIO-VME board the speed is strap selectable 300 to 2 Mbit/s.
600, 300 or EXT. With an MIO board (SUB TYPE/ SCC) the possible speeds are 2400 to
By default = EXT 64 Kbit/s.
With a Megapac ESL or Megafrad (SUB TYPE/ SCC), the possible
speeds are 2400 to 256 Kbit/s.
V24 (J1 to J6) The V24 interface is used. it provides:
DCE+X21 The optional X21 interface of the J1 and J2 ports is used in DCE mode
DCE The optional V35 interface of the J1 and J2 ports is used in DCE mode
DTE+X21 The optional X21 interface of the J1 and J2 ports is used in DTE mode
DTE The optional V35 interface of the J1 and J2 ports is used in DTE mode
CHANNELS 0 to 4096 1 or 2 resources
By default = 1 one resource for the IP protocol
the other for the IPX protocol
ADDRESS 1 to 1022 Number of the DLCI used.
By default = 0 This number must be the same as the number of the DLCI used at the
other end of the link. The first 16 DLCIs are reserved for supervision
purposes.
The DCE side sends the status of the link and of the associated circuits
(Full Status).
E
ELMI
YES
By default = NO Deactivates the local management interface (LMI).

Activates the LMI based on the original standard.
(ANSI T1.S1)
ANSI Activates the LMI based on the new standard.
(ANSI T1.617)
KEEP ALIVE 2 to 80 seconds Significant only if the LMI is active.
TIMER By default = 0 Specifies a time-delay in seconds (for example 3 seconds).
(T391 = T392) (recommended = 3) For the DTE, this delay is equivalent to the time between two LMI
Bc 0 à 32767 « Burst Commit »
Be 0 à 32767 « Burst Excess »
Maximum speed in character per second = 10 BANDWIDTH (1 + Be/Bc).
Observation period « Tc » Maximum speed in character per second

Bc = BANDWIDTH Tc = 1 second Be = 0 Max Speed = 10 BANDWIDTH
Bc = 2 BANDWIDTH Tc = 2 seconds Be = 1/2 Bc Max Speed = 15 BANDWIDTH
Bc = 3 BANDWIDTH Tc = 3 seconds Be = Bc Max Speed = 20 BANDWIDTH
Bc = 4 BANDWIDTH Tc = 4 seconds Be = 2 Bc Max Speed = 30 BANDWIDTH
etc. etc. Be = 3 Bc Max Speed = 40 BANDWIDTH
E
Bc = 0 Tc = 1 second etc. etc.
E
14.5.2 Resource configuration parameters
Parameter Range of
Meaning and Scope

Name Settings
characters
maximum
DRC MASK 4 characters Fully or partly identifies a destination resource used for routing.
maximum
PROTOCOL By default = No identification of the transit protocol type.
NONE Protocol multiplexing on the same DLCI is not possible.
IP IP protocol over Frame Relay link.
(Multiplexed protocol possibilities)
IPX IPX protocol over Frame Relay link.
ISO ISO encapsulation RFC 1490 conformance (ISO protocol).
SNA usage reserved
FRAG IP/IPX/ISO + FRAG, fragmentation is allowed.
TPAC Owner X25 encapsulation (TRANSPAC like)
PU TYPE/ By default = usage reserved (LLC2)
NONE
By default = 0
1 to 7 Enables a degree of priority to be assigned between the protocols to be
sent over a particular DLCI.
CIRCUIT TYPE By default = Identifies the resource's main I/O characteristics.
CALL+STAT
CALL+PVC The resource name specified by the DRC MASK/ parameter is the
OUT+PVC The NAME/ or this resource is used as destination resource of another
Megapac resource.
STAT Following a connection/disconnection, the statistics are generated and
sent to the resource defined by the SESSION STATISTICS/ parameter
E
of the BASE descriptor
E
OPTIONS
TRAN
By default: NONE The DE (Discard Eligibility) and CR (Command / Response indication)

bits are forced to 0 in transmit.
The Megapac is transparent to the DE and CR bits.
The DE bit is not set if the CIR is not defined (parameter BANDWITH =
0).
DEP+CR1 Used to force the CR bit to 1, and to set the DE bit when the BC is
BUFFERS Setting from 1 to Setting determining the number of buffers available to this resource.
240 40 for Ethernet and 4 Mbit/s Token Ring.
By default = 2 80 for 16 Mbit/s Token Ring.

By default = 0
BANDWIDTH 0 à 32767 Not used in Frame Relay.

By default = 0
E Page 14-15
14.5.3 Examples of the Frame Relay « access point » function
NAME/ ER00 NAME/ P200

DRC MASK/ P200 PROTOCOL/ IPX
Ethernet
IPX
NAME/ ETHR NAME/ PS02
TYPE/ IPX TYPE/ NFRM
SUB-TYPE/ XIO
DLCI(a)
NPI/ YES
CHANNELS/ 1 NPI/ YES
MAC PROTOCOL/ 8023 ADDRESS/ DLCI(a) MEGAPAC
MODE/ DTE A
NAME/ TE00 NAME/ P200

DRC MASK/ P200 PROTOCOL/ IP
NAME/ TKRE NAME/ PS02

TYPE/ NFRM
Token Ring TYPE/ TIP DLCI(b)
NPI/ YES SUB-TYPE/ XIO
IP NPI/ YES
CHANNELS/ 1
DEF. MAC. PROTO/ ETHR ADDRESS/ DLCI(b) MEGAPAC
MODE/ DTE B
Figure 14-5 Frame Relay « access point » function
E Page 14-16
14.6 X25 - Q922 « access point » mode
In this mode, the levels 2 and 3 of the X25 protocols are encapsulated in a Frame Relay link’s DLCI. The
encapsulation can be:
• compliant with standard ANSI T1.617 annex G and Q922 DL Core annex A. This encapsulation can
be used to transport the LapB-X25 frame (CRC not included) in 1 Frame Relay DLCI. In this case it is
not possible to multiplex another protocol in the same DLCI.
• of the proprietary type (such as Transpac), compatible with RFC 1490. This encapsulation can be
used for protocol multiplexing in the same DLCI, but in this case the flow control mechanisms are not
all available.
This mode requires a virtual X25 descriptor (« VIO ») to be used between the X25 link and the Frame
Relay link. This mode must be used to ensure an interoperation between an X25 link and a link in Frame
Relay.
This connection mode imposes to configure:
• on the X25 side, an « X25 » descriptor with its resources for each X25 link.
• on the Frame Relay side, a « NFRM » descriptor with one resource (1DLCI).
• with PROTOCOL/ NONE parameter for a Q922 DL Core encapsulation
• with PROTOCOL/ TPAC for an owner encapsulation - Transpac like.
• between those 2 descriptors, a virtual « X25 » descriptor (SUB-TYPE/ VIO), acting as a protocol
converter between X25 Frame Relay.
The data routed towards the virtual X25 descriptor (« VIO ») and originating from the X25 resources are
then encapsulated in a Frame Relay frame on the « NFRM » descriptor ’s DLCI.
X25 level 2 Address Niv 2 Control Niv 2 Data Niv 2

(encapsulation Q922 DL Core)

Figure 14-6 X25 encapsulation in Frame Relay (Q922 DL Core)
Address Niv 2
X25 Level 2 Control Niv 2 Data Niv 2

(encapsulation TRANSPAC mode)

Figure 14-7 X25 encapsulation in Frame Relay (Transpac like)
E Page 14-17
14.6.1 Virtual X25 link « VIO » configuration

Name Settings
NAME 4 characters Name of the logical resource
maximum
TYPE X25 Operating in X25 protocol
SUB-TYPE VIO I/O virtual X25 descriptor
NEW PHYSICAL YES A new X25 virtual link is allocated to this descriptor
INTERFACE
NO This virtual descriptor shares the same link as previously
defined in X25
SPEED EXT Doesn’t concern an X25 virtual descriptor
PIGGY TYPE By default = V24 Doesn’t concern an X25 virtual descriptor
Megapac ESL et
Megafrad
PACKET SIZE By default = TRAN Doesn’t concern an X25 virtual descriptor
BANDWIDTH By default = 0 Doesn’t concern an X25 virtual descriptor
V54 MODEM By default = NO Doesn’t concern an X25 virtual descriptor
ADDRESS DTE or A The X25 virtual link descriptor is a logical ETTD (DTE) and
can only communicate with a « logical DCE »X25 link
DCE or B The X25 virtual link descriptor is a logical ETCD (DCE) and
can only communicate with a « logical DTE »X25 link
CHANNELS By default = 1 Number of logical resources associated to a virtual link.
Any modification in the number of « CHANNELS » associated
to a link must be followed by a BOOT to be allowed.
OPTIONS By default = NONE
E Page 14-18
14.6.2 X25 virtual descriptor resource configuration

Name Settings
characters
maximum
DRC MASK By default = . . . .
CALL+STAT
CALL This logical resource to send and receive call requests.
OUT The logical resource is reserved to receive an incoming call.
STAT Following a connection/disconnection, the statistics are
generated and sent to the resource defined by the SESSION
STATISTICS/ parameter of the BASE descriptor
OPTIONS By default: NONE No options required
BUFFERS at least 8 Setting determining the number of buffers available to this
resource.
CALL PRIORITY 0 up to 15 Calling line priority (CP >= RP).

By default = 0
RESOURCE PRIORITY 0 up to 15 Called line priority.
By default = 0
BANDWIDTH 0 up to 32767 Not used in Frame Relay.
By default = 0
E Page 14-19
14.6.3 X25 virtual descriptor’s virtual resource configuration
This virtual resource is only allocated to the virtual descriptor whose NEW PHYSICAL INTERFACE
parameter is YES. This virtual resource groups together the data coming from the resources of the
virtual descriptor(s) having the same TYPE and SUB-TYPE.
This resource configuration is implicit.
The parameters can’t be modified.
The « major » parameters are the following:

Name Settings
NAME 4 alphanumeric This resource and the X25 virtual descriptor share the same
characters name
maximum
DRC MASK abcd Identifies the resource destination used for the routing.
This name is built with the last 2 characters of the virtual X25
descriptor name, in addition with 2 zeros.
example: descriptor PS09 ---> resource 0900
CIRCUIT TYPE CALL+STAT Identifies the resource's main I/O characteristics.
The called resource must be OUT+PVC
CALL PRIORITY 4 Calling line priority (CP >= RP).
The calling resource must have a RESSOURCE PRIORITY < 5.
RESOURCE PRIORITY 0 Called line priority
E Page 14-20
14.6.4 Examples of « X25 access point » function in Frame Relay
NAME/ P100(2) NAME/ P900(2)

DRC MASK/ . . . . DRC MASK/ . . . .
CIRCUIT TYPE/ CALL CIRCUIT TYPE/ CALL
BUFFERS/ 8
NAME/ P100(1) NAME/ P900(1)

MAC, X25 CIRCUIT TYPE/ CALL
CIRCUIT TYPE/ CALL routing
BUFFERS/ 8
tables
NAME/ P100(0) NAME/ P900(0) NAME/ 0900

DRC MASK/ . . . . DRC MASK/ . . . . DRC/ . . . .
CIRCUIT TYPE/ CALL CIRCUIT TYPE/ CALL PROTOCOL/ NONE
BUFFERS/ 8 CIRCUIT TYPE/ OUT+PVC
RP/ (<5)
NAME/ PS01 NAME/ PS09 NAME/ PS02
X25 TYPE/ X25 TYPE/ X25 TYPE/ NFRM DLCI(a)
SUB-TYPE/ XIO SUB-TYPE/ VIO NPI/ YES
NPI/ YES NPI/ YES ADDRESS/ DLCI(a)
ADDRESS/ DCE ADDRESS/ DTE MODE/ DTE
NAME/ PS09
DRC MASK/ 0900
CIRCUIT TYPE/ CALL
CP/ 4
Figure 14-8 X25 « access point » function (Q922 DL Core) in Frame Relay
NAME/ P100(2) NAME/ P900(2)

BUFFERS/ 8
NAME/ P100(1) NAME/ P900(1)

MAC, X25 CIRCUIT TYPE/ CALL
CIRCUIT TYPE/ CALL routing
BUFFERS/ 8
tables
NAME/ P100(0) NAME/ P900(0) NAME/ 0900

CIRCUIT TYPE/ CALL CIRCUIT TYPE/ CALL PROTOCOL/ TPAC
BUFFERS/ 8 CIRCUIT TYPE/ OUT+PVC
RP/ (<5)
NAME/ PS01 NAME/ PS09 NAME/ PS02
X25 TYPE/ X25 TYPE/ X25 TYPE/ NFRM DLCI(a)
SUB-TYPE/ XIO SUB-TYPE/ VIO NPI/ YES
NPI/ YES NPI/ YES ADDRESS/ DLCI(a)
ADDRESS/ DCE ADDRESS/ DTE MODE/ DTE
NAME/ PS09
DRC MASK/ 0900
CIRCUIT TYPE/ CALL
CP/ 4
Figure 14-9 X25 « access point » function (Transpac like) in Frame Relay
E Page 14-21
NAME/ EX00
DRC MASK/ P202
NAME/ ETHX
TYPE/ IPX
NPI/ NO
CHANNELS/ 1
MAC PROTOCOL/ 8023
NAME/ P202
DRC/ . . . .
Ethernet PROTOCOL/ IPX
IP and IPX NAME/ ER00 CIRCUIT TYPE/ OUT+PVC
DRC MASK/ P201
NAME/ P201
NAME/ ETHR DRC/ . . . .
PROTOCOL/ IP
TYPE/ IP
NPI/ YES
CHANNELS/ 1
MAC PROTOCOL/ ETHR NAME/ 0900
DRC/ . . . .
PROTOCOL/ TPAC
RP/ (<5)
NAME/ PS02
NAME/ P100(2) NAME/ P900(2)
DRC MASK/ . . . . DRC MASK/ . . . . TYPE/ NFRM DLCI(a)
CIRCUIT TYPE/ CALL CIRCUIT TYPE/ CALL SUB-TYPE/ XIO
BUFFERS/ 8 NPI/ YES
ADDRESS/ DLCI(a)
NAME/ P900(1) MODE/ DTE
NAME/ P100(1)
MAC, X25 DRC MASK/ . . . .
DRC MASK/ . . . .
routing CIRCUIT TYPE/ CALL
CIRCUIT TYPE/ CALL tables
BUFFERS/ 8
NAME/ P100(0) NAME/ P900(0)

BUFFERS/ 8

X25 TYPE/ X25 TYPE/ X25
SUB-TYPE/ XIO SUB-TYPE/ VIO
NPI/ YES NPI/ YES
ADDRESS/ DCE ADDRESS/ DTE
NAME/ PS09
DRC MASK/ 0900
CIRCUIT TYPE/ CALL
CP/ 4
Figure 14-10 Protocol multiplexing on the same DLCI - Frame Relay
E Page 14-22
E
14.7 Frame Relay on ISDN
To convey a link whose protocol is Frame Relay on ISDN, it is necessary to use the HDLC protocol on
the « GIS » ISDN interface card, and thus to transparently convey the initial frame (frame relay).
Therefore, a « NFRM » descriptor of SUB-TYPE/ VIO acting as a protocol converter must be inserted
between the HDLC descriptor bound to one of the GIS card’s channels B and the incoming link descriptor
(for example a SWITCH Frame Relay).
14.7.1 Virtual NFRM « VIO » link configuration

Name Settings
NAME 4 characters Name of the virtual NFRM link.
maximum
TYPE NFRM Operating in Frame Relay protocol.
SUB-TYPE VIO Virtual I/O NFRM descriptor.
Used to perform protocol conversion
NEW PHYSICAL YES A new virtual NFRM link is allocated to this descriptor.
INTERFACE
NO This virtual descriptor shares the same link as previously defined in
Frame Relay.
SPEED EXT Doesn’t concern a virtual NFRM descriptor.
PIGGY TYPE By default = V24 Doesn’t concern a virtual NFRM descriptor.
Megapac ESL and
Megafrad
ADDRESS 1 up to 1022 Used DLCI number.
By default = 0 This number must correspond to the DLCI number used at the other
end of the link. The first 16 DLCIs are reserved for the supervision.
The DCE side sends the status of the link and of the associated
circuits (Full Status).
LMI By default = NO Deactivates the Local Management Interface (LMI).
YES Activates the LMI at the start norm.
(ANSI T1S1)
E
ANSI Activates the LMI at the new norm.
(ANSI T1.617)
E
KEEP ALIVE
TIMER
(T391 = T392)
2 to 80 seconds
By default = 0
(recommended = 3)
Significant only if the LMI is active.

Specifies a time-delay in seconds (for example 3 seconds).
For the DTE, this delay is equivalent to the time between two LMI
Bc 0 up to 32767 « Burst Commit »
Be 0 up to 32767 « Burst Excess »
E Page 14-24
14.7.2 Virtual NFRM descriptor’s resource configuration

Name Settings
characters
maximum
DRC MASK By default = . . . .
PROTOCOL By default = NONE No identification of the type of protocol used.
Protocol multiplexing on the same DLCI is not possible.
IP IP protocol over Frame Relay link.
IPX IPX protocol over Frame Relay link.
ISO ISO encapsulation RFC 1490 conformance (ISO protocol).
SNA usage reserved
FRAG IP/IPX/ISO + FRAG, fragmentation is allowed.
TPAC Owner X25 encapsulation (TRANSPAC like)
PU TYPE/ By default = NONE usage reserved (LLC2)
By default = 0
1 to 7 Enables a degree of priority to be assigned between the protocols to
be sent over a particular DLCI.
CALL+STAT
OUT+PVC The NAME/ or this resource is used as destination resource of
another Megapac resource.
STAT Following a connection/disconnection, the statistics are generated
and sent to the resource defined by the SESSION STATISTICS/
parameter of the BASE descriptor
E Page 14-25
E
OPTIONS
TRAN
By default: NONE The DE (Discard Eligibility) and CR (Command / Response

indication) bits are forced to 0 in transmit.
The Megapac is transparent to the DE and CR bits.
The DE bit is not set if the CIR is not defined (parameter BANDWITH
= 0).
DEP+CR1 Used to force the CR bit to 1, and to set the DE bit when the BC is
BUFFERS at least 8 Setting determining the number of buffers available to this resource.
CALL PRIORITY 0 up to 15 Calling line priority (CP >= RP).

By default = 0
RESOURCE 0 up to 15 Called line priority.
BANDWIDTH 0 up to 32767 Not used in Frame Relay.

By default = 0
E Page 14-26
14.7.3 Virtual NFRM descriptor’s virtual resource configuration
This virtual resource is only allocated to the virtual descriptor whose NEW PHYSICAL INTERFACE
parameter is YES. This virtual resource groups together the data coming from the resources of the
virtual descriptor(s) having the same TYPE and SUB-TYPE.
This resource configuration is implicit.
The parameters can’t be modified.
The « major » parameters are the following:

Name Settings
NAME 4 alphanumeric This resource and the virtual NFRM descriptor share the same
characters name.
maximum
DRC MASK abcd Identifies the destination resource used for the routing..
This name is built with the last 2 characters of the virtual NFRM
descriptor name plus 2 zeros.
example: descriptor PS09 ---> resource 0900
CIRCUIT TYPE CALL+STAT Identifies the resource’s main I/O characteristics.
The called resource must be OUT+PVC.
The called resource must have a RESSOURCE PRIORITY < 5.
RESOURCE PRIORITY 0 Called line priority
E Page 14-27
14.7.4 Example of Frame Relay function on a ISDN B channel
In the following example, the DLCI(x) of the PS03 link is normally routed on the DLCI(b) of the main
PS04 link. If the main link is unavailable, the routing is carried out on the P900 resource of the virtual
PS09 Frame Relay descriptor. Thus, the DLCI(a) is transparently conveyed on a ISDN B channel, via the
G1B1 descriptor associated to one of the GIS card’s channels.
NAME/ P900(0)
DRC MASK/ . . . .
PROTOCOL/ NONE
....
RP/ 2
NAME/ PS04
TYPE/ NFRM
SUB-TYPE/ XIO
DRC NPI/ YES Main link
routing
ADDRESS/ DLCI(b) DLCI(b)
MODE/ DTE
NAME/ P900(0)
NAME/ P300(0) DRC MASK/ . . . . NAME/ 0900
DRC MASK/ P900 PROTOCOL/ NONE DRC/ . . . .
PROTOCOL/ NONE CIRCUIT TYPE/ OUT+PVC CIRCUIT TYPE/ OUT+PVC
CIRCUIT TYPE/ CALL+PVC BUFFERS/ 8 ....
CP/ 2 RP/ 0 RP/ (<5)
NAME/ PS03 NAME/ PS09 NAME/ G1B1
DLCI(x) TYPE/ NFRM TYPE/ NFRM TYPE/ HDLC
SUB-TYPE/ XIO SUB-TYPE/ VIO SUB-TYPE/ GIO
NPI/ YES NPI/ YES NPI/ YES
ADDRESS/ DLCI(x) ADDRESS/ DLCI(a) ....
MODE/ DCE MODE/ DTE Backup link
OPTION/ UI
DLCI(a)
NAME/ PS09 ....
DRC MASK/ 0900
ISDN - B channel
ECM/ V25B
CIRCUIT TYPE/ CALL
CP/ 4
Figure 14-11 ISDN Frame Relay function
E Page 14-28
14.7.5 Example of DLCI concentration on a ISDN B channel
Several virtual « NFRM » descriptors of SUB-TYPE/ VIO can be associated to each others (NPI/YES on
the first one, NPI/NO on the others), and then constitute a multiprotocol converter managing a DLCI per
protocol, the whole being concentrated on a HDLC link.
NAME/ P900(0)
DRC MASK/ . . . .
NAME/ IPX1 PROTOCOL/ IPX
DRC MASK/ P900 CIRCUIT TYPE/ OUT+PVC
CIRCUIT TYPE/ CALL+PVC BUFFERS/ 8
NAME/ ETHX NAME/ PS09

TYPE/ IPX TYPE/ NFRM
NPI/ YES SUB-TYPE/ VIO
CHANNELS/ 1 NPI/ NO
MAC PROTOCOL/ 8023 ADDRESS/ DLCI(a)
MODE/ DTE
LAN
IP + IPX NAME/ P800(0)
NAME/ IP01 DRC MASK/ . . . .
DRC MASK/ P800 PROTOCOL/ IP
CIRCUIT TYPE/ CALL+PVC CIRCUIT TYPE/ OUT+PVC
BUFFERS/ 8

TYPE/ IP TYPE/ NFRM
SUB-TYPE/ VIO
NPI/ NO
NPI/ NO
CHANNELS/ 1
ADDRESS/ DLCI(b)
DEF. MAC PROTO./ ETHR
MODE/ DTE
NAME/ P300(0) NAME/ P700(0) NAME/ 0700

PROTOCOL/ NONE MAC, X25 PROTOCOL/ NONE CIRCUIT TYPE/ OUT+PVC
CIRCUIT TYPE/ CALL+PVC routing CIRCUIT TYPE/ OUT+PVC ....
tables BUFFERS/ 8
CP/ 2 RP/ (<5)
NAME/ PS03 NAME/ PS07 NAME/ G1B1
TYPE/ NFRM TYPE/ NFRM MAC, X25 TYPE/ HDLC
DLCI(x)
SUB-TYPE/ XIO SUB-TYPE/ VIO routing SUB-TYPE/ GIO
NPI/ YES NPI/ YES tables
NPI/ YES
ADDRESS/ DLCI(x) ADDRESS/ DLCI(c) ....
MODE/ DCE MODE/ DTE Backup link
OPTION/ UI
DLCI(a, b and c)
NAME/ PS07 ....
DRC MASK/ 0700
ISDN - B channel
ECM/ V25B
CIRCUIT TYPE/ CALL
CP/ 4
Figure 14-12 DLCI Frame Relay concentration on a ISDN B channel
E Page 14-29
14.8 Statistics of a TYPE/ NFRM link
The « STAT » and « POLL » commands allow the access to the statistics of a link.
Concerning a « NFRM » type link, the « POLL » command only displays the static variables pointed out
in bold in the following statistic state
BASE: PS01 STAT
TYPE/ NFRM EIA/ 1 1 1 1 CRC ERRORS/ 9

STATE/ DATA SUB-STATE/ ACTV LMI/ UP
DATA IN/ 1967638 DATA OUT/ 2792131 DATA FRAMES IN/ 26819
DATA FRAME RATE OUT/ 0 OUTPUT QUEUE LENGTH/ 0
RCV BECN/ 0 RCV FECN/ 0 DE/ 0
THROUGHPUT/ 1 TIMER/ 10 TX SEQ LOST/ 0
RX SEQ LOST/ 2 TX SEQ/ 85 DCE TX SEQ/ 83
RX SEQ/ 85 DCE RX SEQ/ 85
BASE: PS01 POLL

NFRM 1 1 1 1 9 0 0 DATA ACTV 1967692 2792132 26820 27699 0 0 0 0
0 0 1
The chapter describing the STATISTICS details the whole data available in the various descriptors and
resources of the MegaPAC.
E Page 14-30
15. TYPE/ PPP descriptor
The Megapac can be configured to support point-to-point protocol calls through an XIO, MIO, SIO
interface board, or based on the SCC controller included on the Megapac ESL and Megafrad.
The Megapac can also be configured to support PPP calls over the ISDN network. For this, and
depending on the Megapac type, the GIS board offers an S0 (2B+D) basic access.
The « PPP » descriptor manages a synchronous PPP link, and allows transmission of IP and/or IPX
protocol datagrams. The "PAP" authentication protocol is supported (PASSword Authentication Protocol).
The XIO and MIO boards are recommended for high speed links and for managing frames larger than
the system buffer size.
The tables on the following pages summarize the different parameters that can be modified for the type
PPP link descriptor.

Name Settings
NAME Up to 4 characters Name of a link
(This is the name used in the MAC table)
TYPE PPP Asynchronous mode PPP.
Point-to-point protocol function.
XIO, SCC or NONE
the board.
XIO+SIO Not used with PPP link.
PRI Usage reserved.
E
NONE Usage reserved, not use.
TYPE/ PPP descriptor Page 15-1
E
NEW PHYSICAL
INTERFACE
(NPI) YES
By default = NO This descriptor shares the same link as previously defined in PPP
mode.
A new PPP link is assigned to this descriptor.
be set to YES.
With GIS board, only the first descriptor of the board should be
set to NPI/ YES.
128K, 64K, 48K, 19.2,
By default = EXT 2 Mbit/s.
2400 to 64 Kbit/s.

mode (to a modem).
mode (to a modem).
CHANNELS 0 to 4096 Number of resources associated with the link.
By default = 1 In PPP mode, a resource is required for each protocol supported.
One resource for the IP protocol.
One resource for the IPX protocol.
TYPE/ PPP descriptor
E Page 15-2
E
ACTIVE
YES
By default = NO The Megapac tries to initialize the link periodically a limited

number of times (see TRIES)
The Megapac tries to initialize the link periodically and continually.
IDLE DETECT 0 to 100 In 1/10 of s Frame transmission frequency
TIME By default = 0 0 = no transmission
30 = transmission all 3 seconds
TRIES 2 to 80 When ACTIVE=NO, this parameter indicates the maximum
By default = 10 number of attempts to initialize the link.
PAP The Megapac initializes the link by negotiating an authenticity
according to the PAP protocol.
The PASS table must have two specific recordings including the
ID information (identification) and the PAP protocol PW
(PASSword).
POLL Supervises the PPP link.
The Megapac convey a control message towards all the « IDLE
DETECT TIME ».
If the messages has no answers after the « TRIES » tests, the link
will be restarted (disconnection and attempt to reconnect).
TYPE/ PPP descriptor is used by the V25B virtual descriptor to
send V.25 bis dialing information taken from the MAC table to the
V25M This option activates the monitor mode of a rescue link. It is
ensured by a « V25B » virtual descriptor resource.
E Page 15-3
15.2 Logical resource configuration parameters

Name Settings
characters
DRC MASK 4 characters Fully or partly identifies a destination resource used for routing.

CALL+STAT
OUT+PVC The NAME/ or this resource is used as destination resource of
STAT Following a connection/disconnection, the statistics are generated
and sent to the resource defined by the SESSION STATISTICS/
parameter of the BASE descriptor.
OPTIONS By default : NONE No options required
BUFFERS Setting from 1 to 240 Setting determining the number of buffers available to this
40 for Ethernet and 4 Mbit/s Token Ring.
80 for 16 Mbit/s Token Ring.
PROTOCOL By default = NONE Only one resource is required for each type of protocol used
simultaneously.
IP The resource is used with the TCP/IP protocol.
IPX The resource is used with the IPX Netware protocol.
E Page 15-4
15.3 PAP - PASSword Authentication Protocol
This protocol (RFC 1334) allows to the extremities of a link to identify each other thanks to a simple
procedure.
This identification occurs at the end of the link connection.
The Megapac, whose link has the EXTENDED CALL MANAGEMENT/ PAP parameter initializes the link
indicating the use of the PAP protocol during the negotiation..
In a PPP link between two Megapac, only one extremity must be

EXTENDED CALL MANAGEMENT/ PAP.
The two extremities must have two table PASS recording in the following order :
PASS(n) PASSWORD/ ABCDEFGH A Peer-ID with 8 characters max.

DRC MASK/ xyID xy represents the two first characters of the resource
name (0) of the PPP link with the PAP protocol.
ID is required.
CALL PRIORITY/ 0
MENU NUMBER/ 0
BILLING/ D
PASS(n+1) PASSWORD/ PQRSTUVW A PASSWORD (PW) of 8 characters max

DRC MASK/ xyPW xy represents the two first characters of the resource
name (0) of the PPP link with the PAP protocol.
Pw is required.
CALL PRIORITY/ 0
MENU NUMBER/ 0
BILLING/ D
E Page 15-5
15.4 Example of "IP on PPP" configuration

DRC MASK/ ER00 DRC MASK/ ER00
BUFFERS/ 40 BUFFERS/ 40
PROTOCOL/ IP PROTOCOL/ IP

TYPE/ PPP TYPE/ PPP
NPI/ YES NPI/ YES
CHANNELS/ 1 CHANNELS/ 1
ACTIVE/ YES WAN (PPP) ACTIVE/ YES
IDLE DETECT TIME/ 30 IDLE DETECT TIME/ 30
ECM/ NONE ECM/ NONE
NAME/ ER00 NAME/ ER00

DRC MASK/ .... DRC MASK/ ....
CIRCUIT TYPE/ OUT+PVC CIRCUIT TYPE/ OUT+PVC
NAME/ ETHR NAME/ ETHR

TYPE/ IP TYPE/ IP
NPI/ YES NPI/ YES
MEGAPAC 1 MEGAPAC 2
LAN LAN
(Ethernet - IP) (Ethernet - IP)
Figure 15-1 Example of IP gateway on PPP link
The example above indicates the significant parameters of an IP gateway function between the two
Ethernet networks.
The WAN here is a point-to-point protocol link.
E Page 15-6
16. TYPE/ TERM descriptor
The TYPE/ TERM descriptor provides connections in Asynchronous mode or Binary Synchronous
Character mode (BSC).
It can also be configured to support an Point to Point connection on an asynchronous link :

• SLIP Serial Line IP Protocol, described by the RFC 1172.
• PPP Point to Point Protocol in Asynchronous mode, described by the RFC 1331, 1548.
The « Authentication » protocol « PAP » is bore (Password Authentication Protocol).
IP address negotiation is supported; for this, it is necessary to configure a router port (ROUT
descriptor).
In asynchronous mode, with SIO board. Each resource attached to the TERM descriptor is directly
linked to a physical port of an SIO interface board. In asynchronous applications, resources must be
assigned in multiples of two, and the setting must not exceed the maximum number of SIO ports
available on a Megapac.
In asynchronous mode, with MIO board. Each resource attached to the TERM descriptor is directly
linked to a physical port of an MIO interface board. In asynchronous applications with the MIO board, it is
possible to assign 1 descriptor and 1 resource to 1 physical port, or 1 descriptor and n resources to n
physical ports.
In asynchronous mode, with Megapac ESL and Megafrad system, only one resource is assigned to
the TERM descriptor . This resource is directly linked to the physical port controlled by the SCC.
A TERM descriptor must be defined for each BSC terminal installed. Resources allocations are limited to
two. However, only one resource is active. This protocol is only available with the SIO board. The MIO
interface board and the Megapac ESL and Megafrad cannot be used to manage this protocol.
Type of board SUB-TYPE Descriptor / Resource Physical assignment

assignment
SIO board SIO 1 descriptor and 2 resources 2 asynchronous ports
Asynchronous mode or or
1 descriptor and 2 x n resources 2 x n asynchronous ports
MIO board SCC 1 descriptor and 1 resource 1 asynchronous port
Asynchronous mode or or
1 descriptor and n resources n asynchronous ports
(n = 2 to 36 for 6 MIO boards)
Megapac ESL and Megafrad SCC 1 descriptor and 1 resource 1 asynchronous port
Asynchronous mode
SIO board SIO 1 descriptor and 2 resources only one BSC port
BSC mode (1 active resource, 1 inactive resource)
Figure 16-1 Relationship between resources of TERM descriptor and physical port
TYPE/ TERM descriptor
E Page 16-1
E
16.1 TERM in Asynchronous mode
A TERM descriptor can be used to configure one or several asynchronous resources which, by default,
use the Megapac's presentation service to initiate a call. With this service, you can specify the following
functions according to user requirements:
• predefined connection for connecting the user to a predefined resource of the network;
• call set up after entering the name of the destination resource (4 character name);
• call set up on entering a service name (8 characters);
• call set up using an X.28 PAD command;
• password entry for access to one of the previous three functions.
All these functions can be configured to control the display of a presentation service screen (MENU,
HELP or NEWS), so that the user is not involved with the complexities of the network.
16.1.1 Call by resource name or subscriber number
When a resource is configured with the parameters DRC MASK/ .... (default setting) and OPTIONS/ not
included in the PASS, NAME, and other tables, the user is free to connect to any logical resource of the
Megapac by typing in the four characters of the name of the required resource, or the called subscriber
number.
The X.25 table is then used,
• to link a subscriber number to the required resource name, or
• to link a "destination" resource name to the called subscriber number.
16.1.2 Call by service name
The caller types a service name

The Megapac allows the user to select by service name (mnemonics on up to eight characters) to call a
resource of the network instead of typing the internal, four-character routing code. This facility is
activated by specifying the OPTIONS/ NAME parameter for the resource to which the user is connected.
The resource DRC MASK is not informed ( DRC MASK/ . . . . ).
The service name typed in by the user is analyzed via the NAME table and the DRC MASK of a NAME
record is then used transparently to the user, for internal routing.
The caller is passive or emulation selection

The Megapac offers to a terminal an easy procedure by selecting service names (mnemonic of 4
characters) to call a network resource. This facility is activated by specifying the OPTIONS/ NAME
parameter for the resource to which the terminal is connected. The resource DRC MASK is informed
( DRC MASK/ ABCD ). ABCD is interpreted as a service name.
The service name (ABCD) is analyzed through the table NAME, then the DRC MASK of a recording
NAME is used for an internal routing. The OPTIONS field of the table NAME specifies a type of
emulation (PPP, TELN, ...).
E Page 16-2
E
16.1.3 Password security check
The Megapac allows you to choose a password on up to eight characters. A resource can be assigned
an input password check (OPTIONS/ PASS field) or output password check (OPTIONS/ GATE field). If
OPTIONS/ GATE is specified, the password procedure directly controls access to the destination
resource, in other words, the control is applied to the outgoing call. In both cases, the caller is prompted
to enter a password when the menu (0) is displayed; the Megapac compares the character string entered
by the caller with the content of the PASSWORD field in the records of the PASS table.
16.1.4 TERM descriptor parameters in Asynchronous mode
PARAMETER SETTINGS MEANING

NAME Up to 4 characters Asynchronous link name.
TYPE TERM TERM indicates that the descriptor will be used on an
asynchronous link (or BSC link).
XIO, SCC or NONE
VIO Virtual input - output descriptor
SCC The descriptor addresses an MIO board for this link, or the
descriptor addresses one of six ports of Megapac ESL and
Megafrad system.
GIO, XIO, NONE not used
XIO+SIO Do not use with TERM link.
mode (to a modem).
mode (to a modem).
E Page 16-3
E
CHANNELS
No units
Setting from 0 to 4096 Number of logical resources associated with the link. This
By default = 1
must not exceed the number of physical ports.
With SIO board, it must be specified in multiples of 2 (2, 4, 6,
8, etc).
With MIO board, it can be specified from 1 to 36 for six MIO
boards (see Figure 16-1).
With Megapac ESL and Megafrad port, it must be specified 1.
PACKET SIZE Setting from 32 to Maximum negotiable size of outgoing packets, in bytes.
4096 Normally set to 128.
By default = TRAN By default, transparent to packet size. Any packet size will be
accepted up to the size of the internal buffers.
DELAY TO RTS LOW Setting from 0 to 512 Does not concern Asynchronous mode.
By default = 0
DELAY TO CTS HIGH Setting from 0 to 512 Does not concern Asynchronous mode.
By default = 0
SYNC DELETE By default = NO Does not concern Asynchronous mode.

SYNC INSERT Setting from 0 to 255 Does not concern Asynchronous mode.
By default = 0
DCD FILTER Setting from 0 to 20 Filtering time delay before processing to handle the DCD
In 1/10ths of a second signal state transition.
By default = 0
INHIBIT TIME FILL By default = NO Does not concern Asynchronous mode.
CALL TIME OUT Setting from 2 to 200 Call confirmation supervision time delay (TP2).
In seconds Represents the maximum time waiting for a call accepted
By default = 5 packet in response to a call request packet.
When the timer runs out, a clear indication packet is sent to
the local DTE and the remote DTE.
E Page 16-4
16.1.5 TERM resource parameters in Asynchronous mode
Data via a resource of a TYPE/ TERM descriptor can be transmitted immediately (default condition) or in
accordance with the settings of a PAD profile.
In the first case, the received data is transmitted directly. This solution provides the best transit times.
In the second case, the Megapac's PAD function can be used to maximize the productivity of an X.25
link. You can also use the PAD function when the Megapac controls the output of asynchronous data
(activating/deactivating character echo, operating on the forwarding of data in file transfer mode, etc).

NAME 4 alphanumeric Name of a logical resource.
characters
maximum
DRC MASK 4 characters Fully or partly identifies a destination resource, used for default
maximum routing purposes.
By default = . . . .
By default, supports VT100 type asynchronous terminals.
In 3270 emulation, enables a "VT100" standard terminal to be
connected.
SYNC Does not concern Asynchronous mode.
ASYN+MINI Supports MINITEL function keys.
ASYN+X28 Lets the caller send a call via the presentation mode using the
X.28 syntax.
This attribute automatically activates the NAME option and the
PAD ENABLE/ E parameter.
The X.28 service messages are in English and in accordance
with CCITT specifications.
ASYN+X28F Enables the caller to send a call via the presentation mode using
the X.28 syntax.
This attribute automatically activates the NAME option and the
PAD ENABLE/ E parameter.
The X.28 service messages are in French, and in accordance
with "Transpac" specifications.
ANSI In 3270 emulation, enables an "ANSI" standard terminal to be
connected.
EXTA In 3270 emulation, enables an "EXTended Ansi" standard
terminal to be connected.
MTRM Does not concern the TERM descriptor.
ASYN+SLIP Supports an IP (TCP/IP) connection over an asynchronous link.
E Page 16-5
E
TERMINAL TYPE
(continued)
TPAD
BUF Activates the buffer function so that, for a default call (via DRC),
all data after a <CR> is held while the call is set up and then
forwarded.
Used in conjunction with the BS4505 TPAD retransmission
protocol.
VT22 In 3270 emulation, enables a "VT220" standard terminal to be
connected.
CIRCUIT TYPE CALL+PVC+STAT Identifies the main I/O characteristics of an asynchronous
resource.
with the V25B virtual descriptor.
OSI Does not concern the TERM descriptor.
CALL The resource can send and receive call requests transparently
or using the presentation mode.
PVC The DCD/RTS V24 input control signal does not affect the state
of the resource.
DTE mode : The DCD V24 input control signal is disregarded.
DCE mode : The RTS V24 input control signal is disregarded.
To indicate its connection state (READY), the Megapac turn on
the RTS/DCD output control signal.
SVC The DCD/RTS V24 input control signal is activated.
RTS DCD
OUT DTR OUT CTS
Mode - DTE Mode - DCE
DCD RTS
IN CTS IN DTR
SIO and MIO To know the status of the equipment to which it is connected,
boards the Megapac checks the DCD/RTS input control signal.
The Megapac waits for the DCD/RTS to be sent before
establishing a connection. Likewise, the loss of the DCD/RTS
causes a break in the current call.
To indicate its connection status (READY), the Megapac sets
the RTS/DCD output control signal when the DCD/RTS input
control signal is sent, or when the PAD is called.
Megapac ESL and To know the status of the equipment to which it is connected,
Megafrad without the Megapac checks the DCD/RTS input control signal.
XCHG option. The Megapac waits for the DCD/RTS to be sent before
establishing a connection. Likewise, the loss of the DCD/RTS
To indicate its connection status (READY), the Megapac fixes
the permanent setting of the RTS/DCD output control signal.
Megapac ESL and To know the status of the equipment to which it is connected,
Megafrad with the Megapac checks the CTS/DTR input control signal.
XCHG option. The Megapac waits for the CTS/DTR to be sent before
establishing a connection. Likewise, the loss of the CTS/DTR
To indicate its connection status (READY), the Megapac fixes
the permanent setting of the RTS/DCD output control signal.
OUT The logical resource is reserved to receive a call.
E
STAT After a connection/disconnection, statistics are compiled and
sent to the resource defined by the SESSIONS STATISTICS/
parameter of the BASE descriptor (resource EI01, for example).
TYPE/ TERM descriptor Page 16-6
E
OPTIONS
NONE
RTS
By default = No options required.
(This option does not exist on Megapac ESL - Megafrad)

(SIO board) The RTS and DTR control signals must be ON to activate the
resource. The Megapac waits for RTS to turn on before turning
on the CTS signal.
XCHG (Only on the Megapac ESL - Megafrad)
In V24/V28 physical DCE mode to a terminal, this option is used
to permutate the role of the DTR and RTS interface signals.
See DRO parameter in chapter on PAD parameters and the
description of the CIRCUIT TYPE/ SVC parameter.
BUSY The resource is kept busy for 30 s after the call is cleared.
HOLD If CIRCUIT TYPE = SVC:
Simulates a state transition on expiry of a 10 s time delay when
circuit 109 (DCD) remains active following disconnection of a
session. The port can then be reconnected automatically on
direct routing via the DRC MASK of the logical resource.
HOLD enables an SVC to be used without control of the V.24
signals.
PASS On routing, this attribute activates password protection (defined
in the PASS table) for an outgoing call using this "source"
resource.
The call is cleared if the correct password is not entered within
30 s.
BILL Any call handled by this resource causes a (billing) record to be
inserted in the BILL table when cleared, whether or not the
connection was successful.
Refer to the BILL table.
MSGS Service messages are sent to the caller (UNAVAILABLE, BUSY,
NO RESPONSE, etc).
GATE On routing, this attribute activates password protection (defined
in the PASS table) for incoming calls using this "destination"
resource.
The call is cleared if the correct password is not entered within
30 s.
TALK Does not concern a TERM resource.
SUPR This attribute activates the supervisor mode for routing by the
operator.
For example, a printer can be connected by the operator (under
base) using the (X.28) command ENTR followed by the name of
the resource to be connected.
NAME+X28 Used only in conjunction with the NAME option, this option
activates X.28 support or "PAD compatibility". See TERMINAL
TYPE/. X28, X28F.
NO_M Does not concern a TERM resource.
ISO Class 3 ISO transport connection.
Implements the "reassignment on fault" procedure following a
disconnection at the network level.
E Page 16-7
E
OPTIONS (continued)
SNMP, TELR
DIAG This attribute activates the function for saving Cause and
Diagnostic codes in clear confirmation packets.
Does not concern an Asynchronous resource.
The caller specifies the routing typing a service name (8
characters max.). This name must correspond to an input of the
NAME table.
DRC MASK/ ABCD
ABCD are interpreted as a service name. This name must
IDLE This attribute activates the timer specified in the INACTIVITY
BUFFERS 1 to 240 Total number of buffers assigned to the resource.
By default = 2
SESSIONS 0 to 7 Setting for opening several sessions on asynchronous ports.
By default = 0 It is important to define as many transport buffers as there are
possible sessions (see TRANSPORT BUFFERS/ under BASE).
The session context appears at level 4 for display of statistics
and parameters.
The first connection is established on session "0".
To switch from one session to another, use the STX sequence
(control B) followed by the session number:
STX 0 accesses session 0.
STX 1 accesses session 1, and so on.
SPEED 300 to 115Kbit/s Link throughput in bit/s
By default = 9600 Chapter 1 explain available speeds according to the hardware
configuration used.
SIO from 300 to 19.200 bit/s
MIO from 300 to 115.200 bit/s
Megapac ESL from 300 to 57.600 for J3 to J6 ports.
and Megafrad from 300 to 115.200 for J1 and J2 port.
DATA BITS 6 to 8 Number of bits per character.
By default = 8
STOP BITS 1, 1.5 or 2 Number of stop bits used in a character.
By default = 1.5
PARITY By default = No parity.
NONE
EVEN Even parity.
ODD Odd parity.
SYNC CHAR By default = 00 Does not concern an Asynchronous resource.
TRANSPARENCY CHAR By default = 00 Does not concern an Asynchronous resource.
BURST LIMIT 0 to 255 Counter specially designed for Reverse PAD asynchronous
By default = 0 applications (Telnet clients).
By default, flow control is deactivated. Any other setting
indicates the effective flow control frequency.
E
Example: the setting 80 initiates XOFF or CTS flow control every
80 characters.
E
DISC MODE
0 to 32
By default = 0
Decimal value specifying the disconnect character when routing
has been defined via the presentation mode.
(example : ^K command , decimal 11).
Note : This character must not conflict with the PAD recall
character ^P (DLE, decimal 16) when using the X.28 PAD
function.
MENU NUMBER 0 to 32 Number of MENU records to be displayed to the caller in
By default = 0 presentation mode.
If the parameter is set to 0, no MENU is displayed.
In Asynchronous mode, menu 1 is used by default.
HELP NUMBER 0 to 32 If the OPTIONS/ NAME parameter is used, this parameter
By default = 0 defines the HELP screen number to be displayed to the caller in
presentation mode following a failure.
See HELP table.
NEWS NUMBER 0 to 32 If the OPTIONS/ NAME parameter is used, this parameter
By default = 0 defines the MENU screen number to be displayed to the caller in
presentation mode when the destination resource is unavailable.
See MENU table.
By default = 0
By default = 0
BANDWIDTH 0 to 32767 Required bandwidth in characters per second tenth.
By default = 0 Only towards a X25 link.
Incoming resource.
Bandwidth>0, allows to define the requested speed before
routing.
PAD ENABLE By default = D PAD function operating options.
The logical resource does not send X.29 packets and does not
However, parameters 02 (ECHO/), 05 (DRI/) and 12 (DRO/)
remain active.
MINI, X28F usage reserved
E Activates the PAD function.
E+REV E+REV. Activates the reverse PAD mode. When a connection
request is created in output mode, a qualified data packet
containing the PAD parameters configured for the resource is
sent. See also PROF attribute.
E+MASK E+MASK. The PAD parameters are "hidden" selectively by the
mask previously configured in the MAC table.
E+PROF E+PROF. The PAD parameters are selected in a Profile of the
same name as the resource.
E+REV+PROF Activates the reverse PAD function and a specific Profile.
The other parameters are associated with the Megapac's PAD (X.3) function.
E Page 16-9
E
16.1.6 Using X.28 commands
In X.28 mode, all data is sent in accordance with the conditions defined by the parameters set for the
resource. If a connection is already established, for X.28 commands to be sent to the Megapac the
command Ctrl P (or ^P) must be sent before the X.28 command (provided that PAD parameter 01 is set
to 1).
X.28/X28F Meaning
Command
C nnnn nnnn is the NUA (Network User Address), in other words, the X.25 address of the call
or destination equipment.
nnnn
R-nnnn calls NUA "nnnn", with reverse charging request.
F-nnnn calls NUA "nnnn", with fast select request.
Gxx-nnnn calls NUA "nnnn", with indication of a CUG "xx" (Closed User Group).
CLR / LIB Clears the call.
STAT Displays the connection status.
PAR? Displays a list of current X.3 parameters.
SET:n:x,n:x Alters the setting of a parameter. The first n:x group represents the parameter number
and its required setting. The second group represents another parameter number
followed by its setting, and so on. For example, SET1:1,2:0 specifies the setting 1 for
parameter (1) and the setting 0 for parameter (2).
SET? Forces all parameters to their initial settings and displays them.
PROF nnnn Forces all the parameters to the settings defined in the PROF table record for which the
name (NAME field) matches the name indicated by nnnn (4 characters maximum).
RESET Re-initializes an SVC.
INT Generates an interrupt packet.
RSET Generates an X.28 or X.29 packet for altering the settings of the remote PAD.
ENTR With the SUPR option, inserts data on an SVC.
E Page 16-10
16.1.7 PAD « X28 / X28F » commands and indications
The notation @ signifies "address".

The notation RESS signifies "resource name".
Type X28/X28F Local Remote

Commands Indications Indications
Call called @ COM X28 - @ caller COM (facilities) (call data)
with caller @ X28F - COM @ caller (facilities) (call data)
Call COM X28 - RESS caller COM (facilities) (call data)
without caller @ X28F - COM RESS caller (facilities) (call data)
Call release CLR/LIB CLR/LIB CONF CLR/LIB OCC (engaged)
CLR/LIB ERROR CLR/LIB NC (congestion)
CLR/LIB INV (supplementary services invalid)

CLR/LIB NA (invalid access)
CLR/LIB ERR (local error)
CLR/LIB RPE (remote error)
CLR/LIB NP (no. inaccessible)
CLR/LIB DER (disturbance)
CLR/LIB PAD xyz
CLR/LIB DTE xyz
CLR/LIB NRC (PCV at no)
Profile PROF n ∗ (none)
Reset RESET ∗ RESET DTE xyz
Interruption INT ∗ Break > 400 msec
Setting SET x:y, ... PAR x:INV (none)

Setting & Display SET? x:y, ... PAR x:y, z:INV, (none)
...
Display PAR? PAR 1:1, ... (none)
Status STAT FREE (none)
ENGAGED
param. 22 PAGE (none)
param. 5 d3 (X-Off) (none)
d1 (X-On) (none)
E Page 16-11
16.2 TERM in BSC mode (SIO board)
The BSC (Binary Synchronous Characters) protocol is a set of telecommunication rules defined by IBM
for connecting its terminals, in particular the 3270, 2780/3780 terminals, to its computers (370 + 37xx
front-end).
BSC can be used to transfer data in non transparent mode (EBCDIC or ASCII) or transparent mode
(EBCDIC, transmission of any byte unconverted).
Data is exchanged in blocks, consisting of strings of bytes bounded by control characters (SYN, etc).
This is a "send and wait" procedure operating in synchronous mode.
A synchronous call means that each transmission begins with specific control characters (SYN) for
"character" synchronization purposes.
BSC can operate on a full duplex or half-duplex link, and can handle multipoint (BSC 3270) or point-to-
point (BSC 3270 or BSC 2780/3780) links.
In BSC mode, the PAD service is not used.
16.2.1 TERM descriptor parameters in BSC mode

NAME Up to 4 characters Name of asynchronous link.
TYPE TERM TERM indicates that the descriptor will be used on a BSC link.
(Or Asynchronous link).
XIO, SCC or NONE
SCC not used
XIO+SIO Do not use with a BSC link.
Megapac ESL and (DCE+V24) The BSC protocol is unavailable with Megapac ESL - Megafrad.
Megafrad
E Page 16-12
E
CHANNELS
By default = 1
Setting from 0 to 4096 Number of logical resources associated with the link. This must
not exceed the number of physical ports.
With SIO board in BSC mode, a setting of 2 must be specified.
By default = TRAN By default, transparent to packet size. Any packet size is
accepted, up to the size of the internal buffers.
DELAY TO RTS LOW Setting from 0 to 512 Half-duplex operation only.
By default = 0 Number of padding characters to be inserted between the end of
data transmission and the OFF state of the RTS signal.
DELAY TO CTS Setting from 0 to 512 Half-duplex operation only.
HIGH By default = 0 Number of padding characters to be inserted between
deassertion of the RTS signal and assertion of CTS.
Applicable only if OPTIONS/ RTS has been defined for the
resource.
SYNC DELETE NO Duplex operation only.

(default setting). Option for processing SYNC characters.
By default, no character deletion.
YES YES activates deletion by the Megapac of starting SYNC
characters before transmission of the BSC frame.
SYNC INSERT Setting from 0 to 255 Duplex operation only.
By default = 0 Number of SYNC characters to be sent before the start of the
BSC frame.
DCD FILTER By default = 0 Filter time delay before processing to handle the DCD signal
From 0 to 20 in state transition.
1/10ths of a second
INHIBIT TIME FILL By default = NO Applies only to character oriented synchronous protocols not
supporting the insertion of sync characters (SYNC or DLE
SYNC).
By default, the parameter is deactivated.
YES All transmissions are barred until a complete packet sequence is
received.
CALL TIME OUT Setting from 2 to 200. Call confirmation supervision time delay (TP2).
In seconds. Represents the maximum time waiting for a call accepted packet
By default = 5 in response to a call request packet.
When the timer runs out, a clear indication packet is sent to the
local DTE and the remote DTE.
E Page 16-13
16.2.2 TERM resource parameters in BSC mode

NAME 4 characters maximum Name of a logical resource.
DRC MASK 4 characters maximum Fully or partly identifies a destination resource, used for default
By default = . . . . routing purposes.
Calling end:
DRC MASK/ fully defined.
CIRCUIT TYPE/ CALL.
Called end:
DRC MASK/ left to its default setting (. . . .).
CIRCUIT TYPE/ OUT.
TERMINAL TYPE By default = ASYN Does not concern the BSC mode.
SYNC Supports synchronous data.
Note : The Megapac's presentation mode must be deactivated
for this logical resource.
MINI Does not concern the BSC mode.
X28, X28F Does not concern the BSC mode.
ANSI, EXTA Does not concern the BSC mode.

MTRM Does not concern the TERM descriptor.
SLIP, BUF Does not concern the BSC mode.
TPAD Use in conjunction with the BS4505 TPAD retransmission
protocol.
VT22 Does not concern the BSC mode.
CALL+STAT In BSC mode, specify CALL+PVC for the resource connected
to the terminal (calling end).
In BSC mode, specify OUT+PVC for the resource connected to
the host (called end).
V25B Does not concern the TERM descriptor.
OSI Does not concern the TERM descriptor.
or via the presentation mode.
The V.24 control signals are disregarded.
SVC This attribute activates the V.24 control signals.
OUT The logical resource is reserved to receive a call.
STAT Following a connection/disconnection, statistics are compiled
and sent to the resource defined by the SESSIONS
STATISTICS/ parameter of the BASE descriptor (resource
EI01, by default).
E Page 16-14
E
OPTIONS
XCHG
RTS
By default = NONE No options required.

Usage reserved (only with Megapac ESL and Megafrad).
The RTS and DTR control signals must be ON to activate the
resource.
RTS must be specified for half-duplex operation.
BUSY The resource is kept busy for 30 s after the call is cleared.
HOLD If CIRCUIT TYPE = SVC
Simulates a state transition on expiry of a 10 s time delay
when circuit 109 (DCD) has remained active following
disconnection of a session. The port can then be reconnected
automatically on direct routing via the DRC MASK of the
logical resource.
PASS Does not concern the BSC mode.
BILL Does not concern the BSC mode.
MSGS Does not concern the BSC mode.
GATE Does not concern the BSC mode.
TALK Does not concern a TERM resource.
SUPR Does not concern the BSC mode.
NAME+X28 Does not concern the BSC mode.

NO_M Does not concern the BSC mode.
ISO Class 3 ISO transport connection.
Implements the "reassignment on fault" procedure following
disconnection at the network level.
DIAG This attribute activates the function for storing Cause and
Diagnostic codes in clear confirmation packets.
SNMP, TELR, NAME Does not concern the BSC mode.
IDLE This attribute activates the time delay specified in the
INACTIVITY DETECT TIMER/ parameter of the BASE
descriptor.
BUFFERS 1 to 240 Total number of buffers assigned to the resource.
By default = 2
SESSIONS By default = 0 Does not concern the BSC mode.
configuration used.
DATA BITS By default = 8 Number of bits per character, must be 8.
STOP BITS By default = 1.5 Does not concern the BSC mode.
PARITY By default = NONE Does not concern the BSC mode.
SYNC CHARACTER By default = 00 Sync character used in the protocol.
00 to FF (hex or BCD)
TRANSPARENCY By default = 00 Transparency character used in the protocol.
E
CHARACTER 00 to FF (hex or BCD)
E
BURST LIMIT
DISC MODE
MENU NUMBER
By default = 0
By default = 0
By default = 0
Does not concern the BSC mode.

Does not concern the BSC mode.
No MENU displayed.
HELP NUMBER By default = 0 Does not concern the BSC mode.
NEWS NUMBER By default = 0 Does not concern the BSC mode.
By default = 0
BANDWIDTH 0 to 32767 Required bandwidth in characters per second tenth.

By default = 0 Only towards a X25 link.
Incoming resource.
routing.
PAD ENABLE By default = D In BSC mode, the PAD must be deactivated.
MINI
X28F
E Does not concern the BSC mode.
E+REV Does not concern the BSC mode.
E+MASK Does not concern the BSC mode.
E+PROF Does not concern the BSC mode.
E+REV+PROF Does not concern the BSC mode.
The other parameters are associated with the Megapac's PAD function and do not concern the BSC mode.
E Page 16-16
16.2.3 MAC table, "SYNC" function
The presence of a SYNC function indicates the use of a BSC protocol in Full Duplex communication.
When an end of block delimiter is detected, the input data and resynchronization signals are forwarded.
XXXX SYNC NONE Beginning of block delimiter(s) End of block delimiter(s)
NAME Name of a logical resource

FUNCTION SYNChronization function
SELECTOR Beginning of block delimiter.
This file contains:
• hexadecimal characters.
• hexadecimal character strings separated by commas.
GENERATOR End of block delimiter.
This file contains:
• hexadecimal characters.
• character strings (hexadecimal and/or special), separated by commas.
E Page 16-17
16.2.3.1 Example of the "SYNC function"
Take for example the following MAC program:

1 RSL∗ SYNC NONE 2D,37,2F,3D FF
2 RSL∗ SYNC NONE 1070,61,6B,7C FF
3 RSL∗ SYNC NONE 1002,01 1026,03!!FF
4 RSL∗ SYNC NONE 01,022D FF
5 RSL∗ SYNC NONE 01,02 26,03!!FF
6 RSL∗ SYNC NONE FFFF FFFF
1 The information block is delimited:

at the beginning, by one of the following characters: ENQ (2D), EOT (37), BEL (2F), NAK (3D)
at the end, by the filler character (FF).
at the beginning, by one of the following character strings:
DLE-ACKO (1070), DLE-ACK1 (1061), DLE-WACK (106B), DLE-RVI (107C)
at the end, by the filler character (FF).
at the beginning, by one of the following character strings: DLE-STX (1002), DLE-SOH (1001)
at the end, by one of the following character strings: DLE-ETB (1026) or DLE-ETX (1003)
This character string is followed by two special "block control" special characters (!!), and then by
two filler characters (FF).
at the beginning, by one of the following character strings: SOH-ENQ (012D), STX-ENQ (022D)
at the end, by the filler character (FF)
at the beginning, by one of the following characters: SOH(01), STX(02)
at the end, by one of the following characters: ETB(26), ETX(03)
This character is followed by two special "block control" characters (!!), and then by two filler
characters (FF).
6 The information block is delimited at the beginning and end by the character string FFFF.
Notes
• Record 4 must precede record 5.
• Otherwise, record 5 "steals" the sequence ENQ.
E
• Record 6 prevents the forwarding of errored blocks (ones that have not satisfied the validation
procedure) over the link.
16.3 TYPE/ TERM descriptor and "SLIP" protocol
In this mode, the Megapac is used to set up one or more IP - SLIP connections over asynchronous links.
The Megapac inserts (outgoing) or deletes (incoming) asynchronous characters specific to the SLIP
protocol (Serial Line IP Protocol).
The following tables list the significant parameters of a TERM descriptor and its resource(s) in "SLIP"
mode.
16.3.1 Parameters of a TERM descriptor in IP - SLIP mode

over an asynchronous link

TYPE TERM TERM indicates that the descriptor will be used on an
asynchronous link (or BSC link).
XIO, SCC or NONE
Megafrad system.
mode (to a modem).
E
mode (to a modem).
E
CHANNELS
No units
Setting from 0 to 4096 Number of logical resources associated with the link. This
By default = 1
must not exceed the number of physical ports.
With SIO board, it must be specified in multiples of 2 (2, 4, 6,
8, etc).
With MIO board, it can be specified from 1 to 36 for six MIO
boards (see Figure 16-1).
By default = TRAN By default, transparent to packet size. Any packet size will be
By default = 0
DELAY TO CTS HIGH Setting from 0 to 512 Does not concern Asynchronous mode.
By default = 0
By default = 0
By default = 0
16.3.2 Parameters of a TERM resource in IP - SLIP mode


NAME 4 characters Name of a logical resource.
maximum
DRC MASK 4 characters Fully or partly identifies a destination resource, used for default
maximum routing purposes.
ASYN+SLIP Supports an IP (TCP/IP) connection over an asynchronous link.
E Page 16-20
E
CIRCUIT TYPE
or
CALL+PVC+STAT
CALL+SVC+STAT
Identifies the main I/O characteristics of an asynchronous
resource.
OPTIONS By default = no option required.
NONE
BUFFERS 1 to 240 Setting determining the number of buffers available to this
By default = 0
configuration used.
By default = 8
By default = 1.5
PARITY By default = No parity.
NONE
EVEN Even parity.
ODD Odd parity.

remain active.
In SLIP mode the ECHO, DRI et DRO parameters must be
« D » (DISABLE).
The other parameters can be left at their default settings.
E Page 16-21
16.3.3 Example of IP -SLIP connection over an asynchronous link
NAME/ ER00 NAME/ SL01

DRC MASK/ .... DRC MASK/ ER00
CIRCUIT TYPE/ OSI+PVC+OUT TERMINAL TYPE/ ASYN+SLIP
BUFFERS/ 40 CIRCUIT TYPE/ CALL+PVC
PORT MATCH/ NO BUFFERS/ 40
PRESET PORT MATCH/ 0 SPEED/ 9600

TYPE/ IP TYPE/ TERM Serial Link IP
NPI/ YES CHANNELS/ 2
CHANNELS/ 1 PACKET SIZE/ TRAN
MEGAPAC
LAN
(Ethernet - IP)
Figure 16-2 Example of a Megapac in IP - SLIP mode over an asynchronous link
In this example, the connection is set up when "datagrams" are received over the serial link.
E Page 16-22
16.4 TYPE/ TERM descriptor in « PPP » asynchronous mode
In this mode, the Megapac is used to set up one or more IP - PPP connections over asynchronous links.
The IP - PPP links can be local or concentrated on a distant Megapac.
The Megapac manages a protocol similar to the HDLC over links where Asynchronous characters of
8 bits (1 start + 8 data bits + 1 stop) convey.
The Megapac starts the emulation of the PPP mode.
It requires the use of the presentation service through the « NAME » table.
A « NAME » table recording must have OPTION/ PPP parameters.
To activate the authentication protocol « PAP », the « NAME » table recording must have the
OPTION/ PPP+PAP parameter.
The configuration of as much « TERMINAL EMULATIONS BUFFERS/ » as PPP asynchronous
connections under « BASE » is required.
To implement IP address negotiation, a router interface must be configured. The chapter describing
the ROUT descriptor gives an example of configuration with an asynchronous PPP interface and IP
address negotiation.
The following table lists the significant parameters of a TERM descriptor and its resources in « PPP »
mode.
E Page 16-23
16.4.1 Parameters of a TERM descriptor in IP - PPP mode


TYPE TERM TERM indicates that the descriptor will be used on an asynchronous
link (or BSC link).
XIO, SCC or NONE
Megafrad system.
mode (to a modem).
mode (to a modem).
CHANNELS Setting from 0 to 4096 Number of logical resources associated with the link. This must not
No units exceed the number of physical ports.
By default = 1 With SIO board, it must be specified in multiples of 2 (2, 4, 6, 8,
etc).
With MIO board, it can be specified from 1 to 36 for six MIO boards
(see Figure 16-1).
E Page 16-24
E
PACKET SIZE
Setting from 32 to 4096
By default = TRAN
Maximum negotiable size of outgoing packets, in bytes.
Normally set to 128.
By default, transparent to packet size. Any packet size will be
By default = 0
DELAY TO CTS Setting from 0 to 512 Does not concern Asynchronous mode.
HIGH
By default = 0
By default = 0
By default = 0
16.4.2 Parameters of a TERM resource in IP - PPP mode


NAME 4 characters maximum Name of a logical resource.
DRC MASK 4 characters maximum Fully or partly identifies a destination resource, used for default
By default = . . . . routing purpose.
When the OPTION/ NAME is specified , the four characters of
the DRC MASK/ represents the service name.
CIRCUIT TYPE CALL+PVC+STAT Identifies the main I/O characteristics of an asynchronous
or CALL+SVC+STAT resource.
E Page 16-25
E
OPTIONS
NAME
By default = NONE no option required.

DRC MASK/ . . . .
The caller specifies the routing typing a service name (8
characters max.). This name must correspond to an input of the
NAME table.
DRC MASK/ ABCD
ABCD are interpreted as a service name. This name must
BUFFERS 1 to 240 Setting determining the number of buffers available to this
By default = 0
configuration used.
By default = 8 8 bit with PPP
By default = 1.5 1 stop bit with PPP
PARITY By default = NONE No parity with PPP

remain active.
In PPP Asynchronous mode the ECHO, DRI et DRO
parameters must be « D » (DISABLE).
E Page 16-26
16.4.3 PAP - Password Authentication Protocol
This protocol (RFC 1334) allows to the extremities of a link to identify each other thanks to a simple
procedure.
This identification occurs at the end of the link connection.
The Megapac, whose asynchronous link has a recording in a NAME table with the OPTION/ PPP+PAP
parameter initializes the link indicating the use of the PAP protocol during the negotiation.
In a PPP asynchronous link between two Megapac, only one extremity must have a recording in a NAME
table with the OPTION/ PPP+PAP parameter.
The two extremities must have two table PASS recording in the following order :
PASS(n) PASSWORD/ ABCDEFGH A Peer-ID with 8 characters max.

DRC MASK/ xyID xy represents the two first characters of the resource name
(0) of the PPP link with the PAP protocol.
ID is required.
CALL PRIORITY/ 0
MENU NUMBER/ 0
BILLING/ D
PASS(n+1) PASSWORD/ PQRSTUVW A PASSWORD (PW) of 8 characters max

DRC MASK/ xyPW xy represents the two first characters of the resource name
(0) of the PPP link with the PAP protocol.
Pw is required.
CALL PRIORITY/ 0
MENU NUMBER/ 0
BILLING/ D
E Page 16-27
16.4.4 Example of IP connection in local asynchronous PAD PPP mode
TERMINAL EMULATION BUFFERS = 10
NAME table
NAME/ TOTO
DRC MASK/ IPPP
CALL PRIORITY/ 0
BILLING/ D
OPTIONS/ PPP
NAME/ PPP1
DRC MASK/ TOTO
NAME/ IPPP
TERMINAL TYPE/ ASYN
DRC MASK/ ....
TERMINAL TYPE/ ASYN
OPTIONS/ NAME
BUFFERS/ 40
OPTIONS/ NONE
SPEED/ 19.2
BUFFERS/ 40
PAD ENABLE/ D
NAME/ ETHR NAME/ PS01 Asynchronous

TYPE/ IP TYPE/ TERM PPP link
NPI/ YES CHANNELS/ 2
CHANNELS/ 1 PACKET SIZE/ TRAN
MEGAPAC
LAN
(Ethernet - IP)
Figure 16-3 Example of a Megapac in local asynchronous PAD PPP mode
In this example, the connection is set up when « datagrams » are received over the serial link.
E Page 16-28
16.4.5 Example of IP connection in a distant asynchronous PAD PPP
NAME table
NAME/ TOTO
DRC MASK/ RT02
CALL PRIORITY/ 0
BILLING/ D
OPTIONS/ PPP
X25 table MAC table

PS03 IBEG
P300 0 123456 PS03 DAD TALK 123456 TOTO
PS03 IEND

BUFFERS/ 40 OPTIONS/ NAME
BUFFERS/ 40

TYPE/ X25 WAN (X25) TYPE/ X25
NPI/ YES NPI/ YES
...
EXTENDED
CALL MANAGEMENT/ IN
NAME/ PPP1
DRC MASK/ P300
TERMINAL TYPE/ ASYN NAME/ RT02
CIRCUIT TYPE/ CALL+PVC DRC MASK/ ....
OPTIONS/ NONE CIRCUIT TYPE/ OUT
BUFFERS/ 40 OPTIONS/ NONE
SPEED/ 19.2 BUFFERS/ 40
PAD ENABLE/ D PORT ADDRESS/ "WAN"
NAME/ IP01
DRC MASK/ RT01 NAME/ RT01
NAME/ PS01
TERMINAL TYPE/ ASYN DRC MASK/ ....
TYPE/ TERM
CIRCUIT TYPE/ CALL CIRCUIT TYPE/ PVC+OUT
CHANNELS/ 2 BUFFERS/ 40
OPTIONS/ NONE
PACKET SIZE/ TRAN BUFFERS/ 40 PORT ADDRESS/ "LAN"
NAME/ RIPP
NAME/ ETHR
TYPE/ ROUT
TYPE/ IP
MEGAPAC 1 SUB-TYPE/ RIP
NPI/ YES
CHANNELS/ 2
CHANNELS/ 1
ADDRESS/ "LAN"
MEGAPAC 2
TERMINAL EMULATION BUFFERS = 10
Asynchronous
PPP link
LAN
(Ethernet - IP)
Figure 16-4 Megapac in a distant asynchronous PAD PPP
E Page 16-29
E Page 16-30
17. PAD parameters
PAD = Packet Assembler Disassembler.
There are 3 recommendations for PADs, the standards X3, X28 and X29.
The areas of each standard is illustrated below.
X28 X3 X29
X25 X25
Packets
Network
Switching
Asynchronous PAD
Terminal
Host
Figure 17-1 The « X » standards
• The X3 recommendation defines the PAD services. The PAD supplies a class of supplementary
services for characters oriented asynchronous terminals. The services are implemented by some
parameters. These parameters define some specifics characteristics for the terminal and the link with
the PAD.
The X3 recommendation allows configuration and control of the PAD by all asynchronous terminal
connected to this PAD.
• The X28 recommendation defines the procedures used by an asynchronous terminal to reach the
services presented by the PAD.
• The X29 recommendation is a similar function of X3 recommendation, except that the PAD is
controlled now by the remote DTE. The remote DTE can be a other PAD, a host or all other
equipment working in packet mode.
PAD parameters
E Page 17-1
The table below describes the effects of the X.3 parameters on the Megapac.
PARAMETER VALUES MEANING AND SCOPE

PAD RECALL (01) By default = 0 The escape character enables the start-stop mode DTE to send
a command to the PAD during the data transfer phase.
By default, no escape character.
1 The escape character is DLE, obtained by <CTRL>P.
2 to 126 Escape character corresponding to the decimal value specified.
ECHO (02) By default = CONT Echo facility.
E Echo of characters sent by the start-stop mode DTE.
D No echo.
CONT (see note) Echo service activated (<CTRL> O) or deactivated (<CTRL> N) by
the operator.
E+CONT (see note) Combination of the two commands.
DATA By default = 0 Data forwarding characters.
FORWARDING (03) 0 – Data sent when the buffer is full.
1 Data forwarding after A-Z, a-z, 0-9.
2 Data forwarding after <CR>.
4 Data forwarding after <ESC>, <BEL>, <ENQ>, <ACK>.
8 Data forwarding after <DEL>, <CAN>, <DC2>.
16 Data forwarding after <ETX>, <EOT>.
32 Data forwarding after <HT>, <LF>, <VT>, <FF>.
64 Data forwarding after any character from columns 0 and 1 of the N°
5 ASCII table.
128 Data forwarding after any graphic character generated by videotex
function keys.
DELAY (04) By default = 0 Delay before sending data.
0 = no sending data after delay
1 to 255 In 1/10ths of a second.
Note : Recommendation X.3 states that this delay should be
calculated in 1/20ths of a second.
Note :
The "CONT" parameter enables the activation/deactivation of the echo facility by the operator.
This command is not standard PAD. It should normally be used with the PAD function disabled
(parameter PAD ENABLE = D).
When the "CONT" parameter is used with the PAD function, the PAD parameter 2 display is invalid
(PAR 2:INV).
PAD parameters
E Page 17-2
E
DRI (05)
By default = D DTE-C slaving by PAD

By default, the Megapac PAD does not control the receive data flow (no
slaving).
RTS DCD
OUT DTR OUT CTS
DCD RTS
IN CTS IN DTR
E Megapac PAD controls the receive data flow, by transmission of XON
and XOFF characters.
RTS (does not apply to Megapac ESL and Megafrad)
Megapac sets the RTS/DCD output control signal to control the receive
data flow.
RTS/105 control for physical DTE V24/V28.
DCD/109 control for physical DCE V24/V28
CTS Megapac sets the DTR/CTS output control signal to control the
SIO and MIO receive data flow.
boards DTR/108 control for physical DTE V24/V28.
CTS/106 control for physical DCE V24/V28.
CTS Megapac sets the DTR/CTS output control signal to control the
receive data flow.
Megapac ESL DTE mode DTR/108 control for physical DCE V24/V28 and crossed
and Megafrad cable.
DCE mode CTS/106 control for physical DCE V24/V28 and straight
cable.
PAD SIGNALS (06) By default = D Transmission of indications by the PAD.
The PAD transmits no indications to the start-stop mode DTE.
E The PAD sends indication messages to the start-stop mode DTE.
BREAK (07) By default = 1 Procedure on BREAK signal from the start-stop mode DTE.
0 Simple data forwarding signal.
1 Transmission of an interrupt packet to the packet mode DTE.
2 Transmission of a reset packet to the packet mode DTE (loss of data).
5 Transmission of an interrupt packet and a "BREAK indication" PAD
message to the packet mode DTE.
8 BREAK signal precedes forwarding of a command, as escape
characters.
21 Transmission of an interrupt packet and a "BREAK indication" PAD
message to the packet mode DTE.
Data received by the PAD (from the packet mode DTE) is sent not sent to
the start-stop mode DTE but deleted by the PAD.
This function is equivalent to setting parameter 8 to 1 (rejecting
output data).
PADDING (09) By default = 0 Padding after <CR> facility.
By default, no padding characters inserted.
1-7 Number of <NUL> à characters to be inserted by the PAD after a <CR>
E
character to the start-stop mode DTE.
PAD parameters Page 17-3
E
FOLD (10)
1-255
By default = 0 Line folding facility.

By default, service not required.
The PAD inserts a format indicator when the counter reaches the
specified value (1 to 255) in characters to be sent to the start-stop mode
DTE.
DRO (12) By default = D DTE-C flow control.
By default, the Megapac does not control its transmit data flow.
RTS DCD
OUT DTR OUT CTS
DCD RTS
IN CTS IN DTR
E Megapac PAD controls its transmit data flow on reception of the XON
and XOFF characters.
INIT Transmission of the XON character following system reset or clearing of
virtual circuit.
CTS Megapac PAD uses the CTS/DTR input control signal to control its
SIO and MIO transmit data flow.
boards CTS/106 control for physical V24/V28 DTE.
DTR/108 control for physical V24/V28 DCE.
CTS Megapac PAD uses the CTS/DTR input control signal to control its
transmit data flow.
Megapac ESL DTE mode CTS/106 control for physical V24/V28 DCE and crossed
and Megafrad cable.
without XCHG DCE mode DTR/108 control for physical V24/V28 DCE and straight
option cable.
CTS Megapac PAD uses the DCD/RTS input control signal to control its
transmit data flow.
Megapac ESL DTE mode DCD/109 control for physical V24/V28 DCE and crossed
and Megafrad cable.
with XCHG DCE mode RTS/105 control for physical V24/V28 DCE and straight
option cable.
LFI (13) By default = 4 Insertion of <LF> after <CR>.
0 No <LF> inserted.
1 <LF> inserted after each <CR> in a character string to the start-stop
mode DTE.
4 <LF> inserted after each <CR> in a character string echoed to the start-
stop mode DTE.
5 Function 1 + function 4.
6 <LF> inserted after each <CR> in a character string from the start-stop
mode DTE to the packet mode DTE.
<LF> inserted after each <CR> in a character string echoed to the start-
stop mode DTE.
PAD parameters
E Page 17-4
E
LF PAD (14)
0
1-7
By default = 4 Padding after <LF> facility.

Service not required.
Any <LF> character transmitted in the data transfer phase by the PAD to
the start-stop mode DTE causes insertion by the PAD of a <NUL>
number of characters corresponding to the specified value.
EDIT (15) By default = D Editing in the data transfer phase.
No editing.
E Editing used.
CHAR DEL (16) By default = 0 "Character delete" function.
By default, no character deletion.
1 to 128 The IA5 character, the position of which in the table corresponds to the
specified value, represents the delete character.
BUFFER DEL (17) By default = 0 "Line delete" function.
By default, no line deletion.
DISP (18) By default = 0 "Line display" function.
By default, no display character.
EDIT SERVICE By default = 0 "Editing indications" function.
SIGNALS By default, the PAD sends no character delete indication to the start-stop
(19) mode DTE.
1 The PAD sends the "\" character to the start-stop mode DTE.
2 The PAD transmits editing indications appropriate for the display
terminals ("backspace" character).
8 The PAD sends the IA5 character for which the position in the table
32 < N < 126 corresponds to the specified value (8 or N).
Note : This function applies only when D (Disable) has been specified in
parameter 6 (Transmission of indications by the PAD).
ECHO MASK (20) By default = "Echo mask" function.
NONE By default, no echo mask.
1 No echo of <CR>.
2 No echo of <LF>.
4 No echo of <VT>, <HT> and <FF>.
8 No echo of <BEL> and <BS>.
16 No echo of <ESC> and <ENQ>.
32 No echo of <ACK>, <NAK>, <STX>, <SOH>, <EOT>, <ETB> and
<ETX>.
64 No echo of editing characters as designated by parameters 16 (character
delete), 17 (line delete) and 18 (line display).
128 No echo of meaningless characters from IA5 not mentioned above for
other possible values of this parameter.
E
Note : A decimal representation of the various values (0 to 128) lets you
encode a single function or a set of functions combined.
PAD parameters Page 17-5
E
PARITY
TREATMENT (21)
1
By default = 0 "Parity treatment" function.

Service not required.
The PAD checks the parity of characters sent by the start-stop mode
DTE.
2 The PAD generates a parity bit in all characters to the start-stop mode
DTE.
Note : Use of this function entails programming of the following, at the
"logical resource" level:
DATA BITS /8.
PARITY/NONE.
PAGE WAIT (22) By default = 0 "Page wait" function.
No page waiting.
1 < N < 255 Page wait after N line feed characters sent by the PAD to the start-stop
mode DTE.
The following parameters are not PAD parameters.

FORCE By default = 0 "Data forwarding forcing" function.
By default, no character specified.
specified value, represents the data forwarding forcing character.
This must be PAD Disable.
BREAK CHAR By default = 0 "Interrupt signal simulation" function.
By default, no character specified.
1 to 32 The IA5 character for which the position of the table corresponds to the
specified value, represents the character simulating an interrupt signal.
NETWORK PARITY By default = "Network parity forcing" function.
NONE
EVEN Even parity.
ODD Odd parity.
MARK Parity forced to ONE.
SPAC Parity forced to ZERO.
ESCAPE DELAY By default = 0 Timer on receiving the <ESC> character.
By default, no time delay.
1 < N < 15 On receipt of an ESC character, this can be echoed in accordance with
the value of parameter 20 (ECHO MASK).
The value N represents a time delay (1/20ths of a second) after which
data forwarding takes place.
During this period, received character echo is suppressed.
PAD parameters
E Page 17-6
18. TYPE/ CONS and DLCX descriptor
The Megapac with its Ethernet or Token-Ring interface can be configured to set up X.25 connections
(1984) using the level 2 link layer of a 10 Mbit/s Ethernet LAN or a 4 / 16 Mbit/s Token-Ring LAN.
In other words, an X.25 connection is forwarded on an existing Token-Ring or Ethernet cable.
Data communications are very reliable through use of the connection-oriented mode at the "Data link"
(LLC2) and "Network" levels of the OSI model.
• DSAP = Destination Service Access Point

• SSAP = Source Service Access Point
• LSAP = Link layer Service Access Point
TYPE/ CONS and DLCX descriptor
E Page 18-1
E
18.1 TYPE/ CONS descriptor
Connection mode with Ethernet LAN
X.25 Megapac Ethernet Megapac X.25
18.1.1 CONS link configuration parameters
The tables below summarize the various parameters which can be set for the CONS link descriptor.

Name Settings
NAME Up to 4 characters Name of a link.
TYPE CONS CONS operation type.
NEW PHYSICAL YES On an Ethernet link, the first descriptor using this link must be
INTERFACE NPI=YES.
(NPI) By default = NO The other descriptors using the same Ethernet link must be
NPI=NO.
CHANNELS Setting from 0 to 4096 Number of logical resources associated with the link.
No units. This parameter defines the number of X.25 logical resources with
By default = 1 which a data link can be set up to or from the DTE over the LAN.
DESTINATION Remote MAC address Parameter defining the Ethernet address of the remote station with
ADDRESS/ (12 characters) which the link is set up.
DSAP Setting from 0 to 254 Parameter defining the destination LSAP (in decimal) on which the
By default = 0 session needs to be established.
Normally, set to 126.
SSAP Setting from 0 to 254 Parameter defining the source LSAP of the Megapac and must be
By default = 0 set to 126.
The other parameters are standard with regard to a TYPE/ X25 descriptor.
18.1.2 Logical resource configuration parameters

Name Settings
NAME/ XXXX Name of CONS link descriptor logical resource. Four characters.
DRC MASK/ .... No direct routing.
Use of the X.25 or MAC table (if ECM=IN).
BUFFERS Setting from 1 to 240 Setting determining the total number of buffers available to this
Settings required :
40 for Ethernet and Token Ring 4 Mbit/s configuration.
80 for Token Ring 16 Mbit/s configuration.
E
TYPE/ CONS and DLCX descriptor Page 18-2
E
18.1.3 MAC table parameters
18.1.3.1 MAC address of Ethernet board
The MAC address of the Ethernet card (burned-in Ethernet address), can be modified by a PU function
recording at the beginning of the MAC table. This recording only modifies the Ethernet MAC address for
the descriptors corresponding to the recording NAME.
name of the Ethernet PU NONE local MAC address alloted to

descriptors the Ethernet card
∗ is allowed address in 12 upper-case
hexadecimal characters
18.1.3.1.1 Selection functions

If the ECM (Extended Call Management) parameter is IN, routing is executed by the MAC table.
Function
IBEG Start of an MAC record.
DAD Selection based on destination Ethernet address.
CAD Selection based on source Ethernet address.
CUD Selection based on Ethernet frame type.
FAC Selection based on "facilities" field.
NOP No operation.
IEND End of MAC record.
Options
NONE no option,
TLAT address translation by X.25 table,
REJ unknown addresses rejected.
Selector
* character string of any length,
nnnn* character string beginning nnnn,
*nnnn character string ending nnnn,
nnnn!nn ! replacing one character.
Generator
* broadcast over all logical channels,
LANx broadcast over logical channel "LANx",
LANx,nnnn broadcast over logical channel "LANx", and change source address to nnnn.
E Page 18-3
18.1.4 Example of the "CONS" connection-oriented mode

CIRCUIT TYPE/ CALL+STAT CIRCUIT TYPE/ CALL+STAT
NAME/ PS04
TYPE/ CONS
TYPE/ CONS TYPE/ CONS
NPI/ YES 16
CHANNELS/ NPI/ YES
CHANNELS/ 16
DESTINATION ADRESS/ 0080020005E4 CHANNELS/ 16
DESTINATION
DSAP/ 126 ADRESS/ 0080020005E4 LAN DESTINATION ADRESS/ 0080020001B4
DSAP/ 126
SSAP/ 126 DSAP/ 126
SSAP/ 126 SSAP/ 126

CIRCUIT TYPE/ CALL+STAT
CALL CIRCUIT TYPE/ CALL+STAT

TYPE/ X25 TYPE/ X25
PACKET
NPI/ YESSIZE/ TRAN NPI/ YES
ADDRESS/
PACKET SIZE/
DTETRAN PACKET SIZE/ TRAN
CHANNELS/DTE
ADDRESS/ 16 ADDRESS/ DTE
MEGAPAC 1 MEGAPAC 2
WAN 1 WAN 2
Figure 18-1 Use of Megapac with "CONS" connection-oriented mode
The above example shows the significant parameters of the "CONS" function between two WAN.
In the example, a call request arrives on Megapac 1 - WAN1, and the X121 number is "1234567".
Megapac 1 Side (the Ethernet board MAC address is 0080020001B4)

X25 table
GROUP
P400 0 1234567
Megapac 2 Side (the Ethernet board MAC address is 0080020005E4)

X25 table
GROUP
E
P600 0 1234567
E
18.2 TYPE/ DLCX descriptor
Connection mode with Token-Ring LAN
X.25 Megapac Token-Ring Megapac X.25
18.2.1 DLCX link configuration parameters
The tables below summarize the various parameters which can be set for the DLCX link descriptor.

Name Settings
TYPE DLCX DLCX operation type.
NEW PHYSICAL YES On an Token-Ring link, the first descriptor using this link
INTERFACE must be NPI=YES.
(NPI) By default = NO The other descriptors using the same Token-Ring link
must be NPI=NO.
CHANNELS Setting from 0 to 4096 Number of logical resources associated with the link.
No units. This parameter defines the number of X.25 logical
By default = 1 resources with which a data link can be set up to or from
the DTE over the LAN.
DESTINATION ADDRESS/ Remote MAC address Parameter defining the 802.5 Ethernet address of the
(12 characters) remote station with which the link is set up.
DSAP Setting from 0 to 254 Parameter defining the destination LSAP (in decimal) on
By default = 0 which the session needs to be established.
Normally, set to 126.
SSAP Setting from 0 to 254 Parameter defining the source LSAP of the Megapac and
By default = 0 must be set to 126.
E Page 18-5

Name Settings
NAME/ XXXX Name of CONS link descriptor logical resource. Four
characters.
DRC MASK/ .... No direct routing.
Use of the X.25 or MAC table (if ECM=IN).
BUFFERS Setting from 1 to 240 Setting determining the total number of buffers available
By default = 2 to this resource.
Settings required :
18.2.3 MAC address of Token-Ring board
The MAC table must contain a record defining the using of the ring.

name of PU NONE STP,4 4000nnnnnnnn to
TokenRing 4 Mbit/s Token-Ring on 9-way connector 7FFFnnnnnnnn
descriptor(s)
STP,16 local MAC address
∗ is allowed 16 Mbit/s Token-ring on 9-way connector assigned to Token-Ring
board
UTP,4
4 Mbit/s Token-Ring on RJ45 connector address on 12 upper-case
UTP,16
16 Mbit/s Token-Ring on RJ45 connector
E Page 18-6
18.2.4 Example of the "DLCX" connection-oriented mode
MAC table MAC table
TKNR PU NONE UTP,4 400011112222 TKNR PU NONE UTP,4 400033334444
NAME/ P400
TR01 NAME/ TR01
CIRCUIT TYPE/ CALL+STAT CIRCUIT TYPE/ CALL+STAT
BUFFERS/ 80
40 BUFFERS/ 80
NAME/ PS04
NAME/ TKNR NAME/ TKNR
TYPE/ CONS
TYPE/ DLCX TYPE/ DLCX
NPI/ YES 16
CHANNELS/ NPI/ YES
CHANNELS/ 16
DESTINATION ADRESS/ 0080020005E4 CHANNELS/ 16
DESTINATION
DSAP/ 126 ADRESS/ 400033334444 LAN DESTINATION ADRESS/ 400011112222
DSAP/ 126
SSAP/ 126 DSAP/ 126
SSAP/ 126 SSAP/ 126

CIRCUIT TYPE/ CALL
CALL+STAT CIRCUIT TYPE/ CALL+STAT
BUFFERS/ 80
40 BUFFERS/ 80

TYPE/ X25 TYPE/ X25
PACKET
NPI/ YESSIZE/ TRAN NPI/ YES
ADDRESS/
PACKET SIZE/
DTETRAN PACKET SIZE/ TRAN
CHANNELS/DTE
ADDRESS/ 16 ADDRESS/ DTE
MEGAPAC 1 MEGAPAC 2
WAN 1 WAN 2
Figure 18-1 Use of Megapac with "DLCX" connection-oriented mode
The above example shows the significant parameters of the "DLCX" function between two WAN.
In the example, a call request arrives on Megapac 1 - WAN1, and the X121 number is "1234567".
Megapac 1 Side (the Token-Ring board MAC address is 400011112222, and X25 table is :)
GROUP
P400 0 1234567
Megapac 2 Side (the Ethernet board MAC address is 400033334444 and X25 table is :)
E
GROUP
P600 0 1234567
E Page 18-8
19. TYPE/ LAN and TLAN descriptors
19.1 General
The LAN and TLAN descriptors provide transparent bridge mode connections between two LANs. At
each end, the Megapac bridge function operates at the MAC sublayer of the OSI link layer and
disregards frame information.
With the TYPE/ LAN descriptor, the bridge function is compatible with the MAC 802.3 frame (supporting
LLC1 or LLC2 of the 802.2 standard), the SNAP type MAC 802.3 frame and the Xerox V2 type Ethernet
frame.
With the TYPE/ TLAN descriptor, the bridge function is compatible with the MAC 802.5 frame
(supporting an LLC1 or LLC2 compliant with the 802.2 standard and the IBM type MAC 802.5 frame).
Ethernet Megapac X.25 Megapac Ethernet

(LAN) (LAN)
The tables below summarize the various parameters which can be modified in the LAN or TLAN link
descriptor.

Name Settings
TYPE LAN Transparent bridge mode operation on an Ethernet LAN.
TLAN Transparent bridge mode operation on a Token Ring
network.
NEW PHYSICAL YES On an Ethernet or Token Ring link, the first descriptor
INTERFACE using this link must be NPI=YES.
(NPI) By default = NO The other descriptors using the same Ethernet or Token
Ring link must be NPI=NO.
CHANNELS 0 to 4096 Number of logical resources associated with the link.
By default = 1 (1 resource per network).
DIRECTED BROADCASTS By default = NO Type of broadcast frames processed: general broadcast
or group broadcast.
NO All frames sent and detected on the LAN are broadcast
over all logical resources of the LAN or TLAN descriptor
so to all remote LANs.
YES Transmission to the remote LANs of frames sent and
detected on the local LAN is handled by the MAC table.
The MAC table can be used to filter transmission of the
frames or reject them selectively according to their
source or destination address (FUNCTION/ CAD or DAD,
OPTION/ REJ) to limit the transmission of broadcast and
E
group broadcast frames to certain remote networks.
TYPE/ LAN and TLAN descriptors Page 19-1
19.3.1 Preliminary choice of VC type
1) Permanent virtual circuit
The virtual circuit is set up from the link RESTart point. Setup is independent of traffic detected on the
LANs. In case of failure, the call request packet is sent every five seconds.
• In one Megapac, the logical resource associated with the descriptor (LAN or TLAN) will be set to
"CIRCUIT TYPE/ CALL+SVC" and handle transmission of the call request packet.
• In the other Megapac, the logical resource associated with the descriptor (LAN or TLAN) will be set to
"CIRCUIT TYPE/ OUT+SVC".
2) Virtual circuit setup when frames need to be sent to the remote bridge
The virtual circuit is set up when the bridge detects a frame on the LAN or local ring which needs to be
sent to the remote ring associated with this virtual circuit after scanning the "self-learning" and MAC
tables.
• In one Megapac, the logical resource associated with the descriptor (LAN or TLAN) is set to "CIRCUIT
TYPE/ CALL+PVC" and handles transmission of the call request packet on detection of frames to be
sent.
• In the other Megapac, the logical resource associated with the descriptor (LAN or TLAN) is set to
"CIRCUIT TYPE/ OUT+PVC" and can only receive the call request packet.
So that each LAN can initiate a transmission, it is important to define two "crossed" virtual circuits, each
bridge having both "CALL+PVC" and "OUT+PVC" logical resources. With PVC type logical resources,
you can configure the system to clear the virtual circuit if there is no traffic.
TYPE/ LAN and TLAN descriptors
E Page 19-2
E
NAME
Parameter
Name
Range of
Settings
4 characters
Meaning and Scope
Name of a logical resource.

maximum Each logical resource of the LAN or TLAN descriptor represents
a virtual circuit to a remote bridge. It is therefore important to
customize the name of each logical resource so that frames can
be sent and received from the appropriate remote LAN.
DRC MASK 4 characters Fully or partly identifies a destination resource, used for routing.
maximum
XXXX "CALL+PVC" or "CALL+SVC"
type logical resource
Name of the logical resource associated with the "serial" link
descriptor (X.25, for example) linking this Megapac to the
Megapac connected to the remote LAN.
The call request packet, requesting the setting up of the virtual
circuit between the two bridges is sent by this logical resource
associated with the "serial" link descriptor.
.... "OUT+PVC" or "OUT+SVC"
type logical resource
CALL+STAT
CALL+SVC This logical resource initiates transmission of the call request
packet (X.25) requesting setting up of the virtual circuit between
the two remote bridges.
Transmission takes place immediately the link is RESTarted. It
is independent of traffic detected on the local LAN. In the event
of failure, the call request packet is sent every 5 seconds.
CALL+PVC This logical resource initiates transmission of the call request
packet (X.25) requesting the setting up of the virtual circuit
linking the two remote bridges.
Transmission takes place on detecting a frame on the local LAN
which needs to be sent, after scanning the FILTER and MAC
tables, to the remote LAN associated with this logical resource.
OUT+SVC This logical resource corresponds, in one of the two remote
bridges, to a "CALL+SVC" type logical resource of the other
remote bridge.
It "receives" the X.25 call request packet and cannot initiate
transmission.
OUT+PVC This logical resource corresponds, in one of the two remote
bridges, to a "CALL+PVC" type logical resource of the other
remote bridge.
It "receives" the X.25 call request packet and cannot initiate its
transmission.
E Page 19-3
E
OPTIONS
IDLE
By default: NONE No options required.

The virtual circuit is cleared if it sends no further data for the
time set by the INACTIVITY TIMER/ parameter of the BASE
descriptor.
Do not use this setting for a "CALL+SVC" or "OUT+SVC" type
logical resource.
BUFFERS 1 to 240 Setting determining the total number of buffers available to this
BROADCAST FILTER 0 to 12000 Period in tenths of a second with which broadcast packets or
TIMER By default = 0 group broadcast packets are sent to the remote network
corresponding to this logical resource.
0: no timer.
12000: no transmission of broadcast or group broadcast frames.
INHIBIT LEARNING By default = NO Activates learning mode.

The Megapac learns only the routing of the frames transmitted
to the remote LAN corresponding to this logical resource by
updating the self-learning table using the frames received from
that LAN.
YES Deactivates the learning mode.
The Megapac does not update the self-learning table with
frames received from the remote LAN corresponding to this
logical resource.
The routing of frames sent to this remote LAN must be
programmed in the MAC table.
By default = 0
By default = 0
BANDWIDTH 0 to 32767 Required bandwidth, in characters per second tenth.
Incoming resource :
routing.
E Page 19-4
19.3.2 Additional X.25 network configuration information
The X.25 network side configuration uses the standard X.25 configuration elements of the Megapac.
The only parameters specifically to be taken into account are :
• PACKET SIZE/ (X25 descriptor parameter) - this must be defined with the TRAN value,
• BUFFERS/ (X25 resource parameter) - the settings to be used for LAN and TLAN are :
• 40 for Ethernet and Token Ring 4 Mbit/s configuration.
• 80 for Token Ring 16 Mbit/s configuration.
• K LEVEL 3/ (X25 descriptor parameter) - this must be set to 7 for optimum performance.
19.4 Routing - Aging of self-learning table
In order to define which MAC addresses are routed, it is necessary to configure a recording string in MAC
table so that the Megapac fulfills the « PONT » function.
Two filtering modes are available :
Self-Learning mode : the Megapac discovers which machines are on the remote LAN.
Listed mode : the Megapac includes a MAC table defining a MAC address or a group of MAC addresses
which have to be routed towards a specific WAN.
Megapac uses a "notebook" to record at which termination (local or remote) are located the active
machines For each machine, the Megapac saves the machine's MAC address, and the records the
termination (local or distant) to which each machine is connected.
By default, the "MAC address - local or remote" pairs do not incorporate the notion of aging.
The "TIME" function of the MAC table can be used to specify an "age" limit for the "MAC address -
local or remote" pairs of the "notebook".
The "TIME" recording must be placed immediately after the input MAC program of the LAN or TLAN
descriptor concerned. (IBEG then IEND is the obligatory minimum)
ETHE IBEG
ETHE IEND
ETHE TIME NONE Aging LAN, Aging WAN
• Aging LAN LAN-side aging in seconds.

This aging affects the "MAC address, local" pairs acquired by datagrams coming from the
LAN side.
The value 0 or none indicates "no aging".
• Aging WAN WAN-side aging in seconds.
This aging affects the "MAC address, remote" pairs acquired by datagrams coming from the
WAN side.
E Page 19-5
E
19.4.1.1 Selection function
NAME Name of the LAN link.
FUNCTION
DAD Selection based on destination Ethernet address.
CAD Selection based on source Ethernet address.
DATA Selection based on Ethernet frame information.
NOP No operation.
IEND End of an MAC record.
TIME Used to specify an "age" limit for the "MAC address, local or remote" pairs of the "notebook".
OPTION
NONE no option
REJ unknown addresses rejected
SELECTOR Filtering on the source or destination MAC address, or on the data of the Ethernet or Token
Ring frame.
∗ character string of any length (auto learning mode)
nnnn∗ character string beginning nnnn (cataloged mode)
∗nnnn character string ending nnnn (cataloged mode)
nnnn!nn ! = replaces one character (cataloged mode)
GENERATOR Describes the LAN resource(s) to be used.

∗ Broadcasting on every resources of the LAN descriptor. The LAN resource(s) have a DRC
towards the suitable WAN resources.
LANx Broadcasts on the « LANx » resource of the LAN descriptor. The LAN resource(s) have a DRC
towards the suitable WAN resources.
E Page 19-6
19.4.1.2 MAC address of Token-Ring board
For Token-Ring, the MAC table needs to have a record defining use of the ring.

name of Token PU NONE STP,4 4000nnnnnnnn to
Ring Token-Ring on 9-way connector at 4 Mbit/s. 7FFFnnnnnnnn
descriptor(s) (Physical
Unit). STP,16 local MAC address,
∗ is accepted Token-Ring on 9-way connector at 16 Mbit/s. assigned to the Token-
Ring board
UTP,4
Token-Ring on RJ45 connector at 4 Mbit/s. 12 upper-case
UTP,16
Token-Ring on RJ45 connector at 16 Mbit/s.

name of the Ethernet PU NONE local MAC address allotted to
E Page 19-7
19.5 Example of a transparent bridge


TYPE/ X25 TYPE/ X25
NPI/ YES NPI/ YES
PACKET SIZE/ TRAN PACKET SIZE/ TRAN
ADDRESS/ DTE ADDRESS/ DCE
CHANNELS/ 16 WAN CHANNELS/ 16
K LEVEL2/ 7 K LEVEL2/ 7
K LEVEL3/ 7 K LEVEL3/ 7
NAME/ LAN1 NAME/ LAN2

BROADCAST FILTER TIMER/ 10 BROADCAST FILTER TIMER/ 10
INHIBIT LEARNING/ NO INHIBIT LEARNING/ NO
NAME/ ETHE NAME/ ETHE
TYPE/ LAN TYPE/ LAN
NPI/ YES NPI/ YES
DIRECTED BROADCAST/ NO DIRECTED BROADCAST/ NO
MEGAPAC 1 MEGAPAC 2
LAN 1 LAN 2
Figure 19-1 Megapac transparent bridge.
The above example shows the significant parameters of the transparent bridge function between two
RLE.
When there are LAN1 datagrams to be sent to LAN2, Megapac 1 initializes the link on the WAN.
E Page 19-8
E
Megapac 1 side
X.25 table
NAME ADDRESS GROUP
ADDRESS USER DATA
P300 0 1234567
MAC table
ETHE IBEG NONE

ETHE DAD NONE ∗ ∗
ETHE IEND NONE
The "VIEW" command lets you view the scratch pad (self-learning table)
ETHE: VIEW
Number Channel Physical Address IP Address

1 Filtered 08005AA0829B
2 LAN1(0) 02608C2FF792
3 Filtered 080020107FD2
4 Filtered 08002011345F
5 LAN1(0) 008002000769
6 Filtered 00001D0B69BA
7 Filtered 08005A0123F1
8 Filtered 0000C9020D99
9 LAN1(0) 0000A2064210
10 Filtered 00001D0C677A
11 Filtered 080020005212
Megapac 2 side
X.25 table
LAN2 0 1234567
MAC table
ETHE IBEG NONE

ETHE DAD NONE ∗ ∗
ETHE IEND NONE
E Page 19-9
E Page 19-10
20. TYPE/ IP and TIP descriptors
20.1 General
The TYPE/ IP and TIP descriptors are for linking TCP/IP functions with the Ethernet or Token-Ring link
physically installed in the unit. For Token-Ring operation, the system software must be set with 512 byte
buffers.
Several IP and/or TIP descriptors can be configured for the same access board.
The IP (or TIP) descriptor is used for IP Switching functions, for the RFC 1356 (877) gateway functions,
for the Telnet Server functions and Reserve Telnet Server functions, and also for the TCP/IP RIP
router functions, for the SNMP agent function, etc.
In "IP Switching" mode, the datagrams coming from the LAN can be routed towards a WAN with
reference to the following criteria:
• IP source address,
• IP destination address,
• protocol type and source port number,
• protocol type and destination port number.
In an X25 network, the IP source or destination address can be used to construct the X121 address of an
X25 call packet.
20.2 Link descriptor
The table below briefly describes the parameters of an IP descriptor.

Name Settings
NAME Up to 4 Name of a link.
characters
TYPE IP IP operation on an Ethernet LAN.
TIP IP operation on a Token Ring LAN.
NEW PHYSICAL INTERFACE YES On an Ethernet or Token Ring link, the first descriptor
using this link must be NPI=YES.
By default = 1 This parameter defines the number of functions required for
the IP environment.
DEFAULT MAC PROTOCOL ETHR Specifies operation with the IEEE 802.3 Ethernet protocol.
In Token Ring mode this parameter is not used.
SNAP Specifies operation with the IEEE 802.3 Ethernet protocol
with SNAP (Sub Network Access Protocol).
E
In Token Ring mode this parameter is not used.
TYPE/ IP and TIP descriptors Page 20-1
E
20.2.1 Ethernet frame formats
Ethernet
Destination address Source address Type field Data field CRC

6 6 2 1500 4
IEEE 802.3 with SNAP

Destination address Source address Length field DSAP SSAP Control SNAP header Data field CRC
6 6 2 1 1 1 1496 4
or LLC1
Organization EtherType
3 2
Figure 20-1 Ethernet and IEEE 802.3 frame formats
20.3 Link resources
The table below briefly describes the parameters of the IP descriptor resources.

Name Settings

CIRCUIT TYPE By default = CALL+STAT Identifies the main I/O characteristics of the resource.
CALL, PVC, OUT, OSI
OPTIONS By default: NONE No options required.
IDLE The virtual circuit is cleared if it sends no further
information for the time specified by the
INACTIVITY TIMER/parameter of the BASE descriptor.
GATE A password controls access to a destination logical
resource.
NAME Routing is based on a name previously defined in the
NAME file.
TALK Selects the presentation mode.
ARPS Forces the Megapac to send an ARP message before each
SYN request.
RARP Specifies operation in Reverse ARP.
The MAC table must include a record with the "ADD"
function.
INAC Used to clear on INACtivity in Reverse Pad Telnet mode.
MBIT In Reverse Pad Telnet mode used to specify a transfer of
IP datagrams in linked X.25 packets (via the M bit).
TYPE/ IP and TIP descriptors
E Page 20-2
E
BUFFERS
Setting from 1 to 240

By default = 2
Setting determining the number of buffers available to this
resource.
MODE By default = NONE Does not manage "Source Quench" messages.
SQM Source Quench - WAN congestion management in IP RFC
1356 gateway mode.
Slows the throughput of a local host when the Megapac
node is approaching WAN congestion
PORT MATCH By default = SRCE+???? Manages a TCP port number.
WILD, SRCE, DEST, NO
PRESET PORT 0 to 32767 Manages a TCP port number.
MATCH By default = 2048
REVERSE TELNET 0 to 32767 Manages a TCP port number.
PORT By default = 0

By default = 0
RESOURCE PRIORITY 0 to 15 Called line priority..
By default = 0
BANDWIDTH Setting from 0 to 32767 Required bandwidth, in characters per second tenth.
Incoming resource:
routing.
The other parameters can retain their default settings.
E Page 20-3
E
20.4 MAC table
20.4.1 Selection functions
Function
DAD Selection based on destination IP address.
CAD Selection based on source IP address.
CPR Selection based on protocol and one or more source port numbers.
DPR Selection based on protocol and one or more destination port numbers.
MASK Defines a mask on the IP addresses for the use of subnetworks.
NOP No operation.
IEND End of an MAC record.
IBEG Options
NONE simple routing (a single path corresponds to 1 IP address)
NOT extended routing (several paths correspond to 1 IP address)
Options
NONE No option.
JUMP to jump a label when the selection criterion is "true"
TLAT Enables an X.25 call request packet to be constructed from an IP address, using the
X.25 table address handling facilities (# skip, " copy).
REJ rejection of unknown addresses, ARP address filtering, RIP broadcast filtering.
Selector IP address in hexadecimal uppercase with wildcards * and !

* character string of any length
nnnn* character string beginning nnnn
*nnnn character string ending nnnn
nnnn!nn ! = substitution of one character
Generator
* broadcasts over all logical channels
LANx broadcasts over logical channel "LANx"
LANx,RESy broadcasts over logical channel "LANx" and routes over resource RESy of a WAN
link.
With the TLAT option the IP address can serve to construct an X.121 address.
LANx,RESy,rot broadcasts over logical channel "LANx" and routes over resource RESy of a WAN
link.
With the TLAT option the IP address conserve to construct an X.121 address.
The IP address can be rotated before handling.
Hex value in hex uppercase, represents the value of the MASK.
GATEWAY keyword, for responding to ARP procedures.
The recording can be placed anywhere in the MAC table.
E Page 20-4
20.4.2 "Simple" routing (IBEG, NONE option)
All data flows for the same destination IP address take the same path.
☞
Datagrams coming from the LAN are routed to a WAN resource,
1. by seeking (in the "notebook") a path already used for this IP destination address,
2. by looking to see if a router function can handle this IP destination address,
3. by using the MAC table routing in the event of failure of solutions 1 and 2. In this case, the routing
selected in the MAC table is kept in the "notebook" and the path will then be used for any datagram
having the same destination IP address.
20.4.3 "Extended" routing (IBEG, NOT option)
The different types of data flow for the same destination IP address can take different suitable
☞ paths. Path management is dynamic. (see paragraph 20.6)
Datagrams coming from the LAN are routed to a WAN resource,
1. by using the MAC table routing to determine which LAN and WAN resource POOL can be used,
2. by seeking a path already used for this IP destination address (in the "notebook") and which adheres
to the no. 1 criteria (i.e. corresponding to the LAN and WAN resource names),
3. by opening a new path, the characteristics of which are preserved in the "notebook".
The CPR and DPR functions are used for the following selections:
XXXX CPR NONE protocol, port no., port no., port no. LANx
or JUMP or LANx,RESy
DPR TLAT protocol, port no.-port no. LANx,RESy,rot
REJ
Function
CPR Selection based on protocol and one or more source port numbers.
DPR Selection based on protocol and one or more destination port numbers.
Selector
protocol protocol type
2 characters in hexadecimal and capitals (06 for TCP, 11 for UDP, etc. ...)
Port no. Port no. (source if CPR, destination if DPR)
4 characters in hexadecimal and capitals (up to 3 port numbers)
Port no.-Port no. Port no. field (source if CPR, destination if DPR)
each Port no. has 4 characters in hexadecimal and capitals
Generator
LANx broadcasts on the "LANx" logical channel
LANx,RESy broadcasts on the "LANx" logical channel, and routes on the RESy resource of a
WAN link.
With the TLAT option the IP address can be used to construct an X 121 address.
LANx,RESy,rot broadcasts on the "LANx" logical channel, and routes on the RESy resource of a
WAN link.
E
With the TLAT option the IP address can be used to construct an X 121 address.
The IP address can be rotated before manipulation.

name of Token PU NONE STP,4 4000nnnnnnnn to
Ring 4 Mbit/s Token-Ring on 9-way connector 7FFFnnnnnnnn
descriptor(s)
STP,16 local MAC address
board
UTP,4
UTP,16
20.4.5 MAC Address of Ethernet board

name of the Ethernet PU NONE local MAC address allotted to
E Page 20-6
E
20.4.6 "MASK" function
The "MASK" function used between the IBEG ... IEND delimiters of an input MAC program are used to
route datagrams according to a sub-network address.
Example:

1 ETHE IBEG NONE
2 ETHE DAD NONE 9009 0001 GATEWAY
3 ETHE MASK NONE FFFF C000
4 ETHE DAD NONE 9009 4000 IP01
5 ETHE DAD NONE 9009 8000 IP02
6 ETHE DAD NONE 9009 C000 IP03
7 ETHE IEND NONE
1 Start of input MAC program delimiter.

2 The Megapac provides a "gateway" function and responds to the ARP procedures for the address
of machine 0001, in the class B network with the NetId 9009.
3 The IP address is received with the mask FFFF C000.
The operation "IP destination address" AND "FFFF C000" is performed.
The result is compared with the next three "MAC" records.
4 The machines with addresses 4000 to 7FFF in the 9009 network are routed over resource IP01.
Resource IP01 has a DRC MASK to a resource of a WAN1 link.
5 The machines with addresses 8000 to BFFF in the 9009 network are routed over resource IP01.
6 The machines with addresses C000 to FFFF in the 9009 network are routed over resource IP03.
7 End of input MAC program delimiter.
E Page 20-7
20.4.7 "MASK" function with a group of IP resources
route datagrams according to a sub-network address.
The GENERATOR field in its form LANx,RESy is used to define a group of IP resources without
specifying for each IP resource the WAN destination resource using the DRC MASK.
Example:

1 ETHE IBEG NONE
2 ETHE DAD NONE 9009 0001 GATEWAY
3 ETHE MASK NONE FFFF C000
4 ETHE DAD NONE 9009 4000 IP1∗,WAN1
5 ETHE DAD NONE 9009 8000 IP1∗,WAN2
6 ETHE DAD NONE 9009 C000 IP1∗,WAN3
7 ETHE IEND NONE

2 The Megapac provides a "gateway" function and responds to the ARP procedures for the address
of machine 0001, in the class B network with the NetId 9009.
3 The IP address is received with the mask FFFF C000.
The operation "IP destination address" AND "FFFF C000" is performed.
The result is compared with the next three "MAC" records.
4 The machines with addresses 4000 to 7FFF in the 9009 network are routed over resource IP1*.
The IP resource has no DRC MASK specified.
The destination resource is the WAN1 resource of a WAN link.
5 The machines with addresses 8000 to BFFF in the 9009 network are routed over resource IP1*.
6 The machines with addresses C000 to FFFF in the 9009 network are routed over resource IP1*.
E Page 20-8
20.4.8 Construction principles of an X.25 address from an IP address
The conversion of an IP address into an X.25 address is defined by:

1. a conversion sequence of the IP address including left rotations with or without conversion of the bits
fields into decimal digits.
2. a conversion of digits sequence into X.121 address by the X.25 table (addition, suppression, storage
of the digits).

1 ETHE IBEG NONE
2 ETHE DAD TLAT adr1 IP11,P400,« seq »
3 ETHE IEND NONE
1 Start of input MAC program delimiter

2 The machines with IP « adr1 » address are routed over a IP11 resource.
The IP resource have no specified DRC MASK.
The destination resource is the P400 resource of an X.25 link.
The destination IP address is converted into decimal digits.
Conversion:
• « seq » is a sequence of conversion from the IP address 32 bits « adr1 », including the
#n "n characters.
• Any different character will cause the end of the sequence.
• In this sequence, the « n » number is hexadecimal and upper-case.
• The #n sequence causes a left rotation of n bits of the IP address.
• The "n sequence causes a left rotation of n bits of the IP address, and the conversion of
those bits into decimal digits.
• "1 causes one step rotation and the result is included between 0 and 1
• "2 causes two steps rotation and the result is included between 0 and 3
• "3 causes three steps rotation and the result is included between 0 and 7
• "4 causes four steps rotation and the result is included between 00 and 15
• "5 causes five steps rotation and the result is included between 00 and 31
• "6 causes six steps rotation and the result is included between 00 and 63
• "7 causes seven steps rotation and the result is included between 000 and 127
• "8 causes eight steps rotation and the result is included between 000 and 255
• "9 causes nine steps rotation and the result is included between 000 and 511
• "A causes ten steps rotation and the result is included between 000 and 1023
• "B causes eleven steps rotation and the result is included between 0000 and 2047
• "C causes twelve steps rotation and the result is included between 0000 and 4095
• "D causes thirteen steps rotation and the result is included between 0000 and 8191
• "E causes fourteen steps rotation and the result is included between 00000 and 16383
• "F causes fifteen steps rotation and the result is included between 00000 and 32767
E
The decimal address can be used by an X.25 table record.
3 End of input Mac program delimiter.
E
Conversion by the X.25 table:

1 P400 0 « trad »
1 For the P400 destination resource, the address previously defined can be converted again.
• « trad » is a conversion sequence from the decimal digits including the characters
#n "n n
• In this sequence, the n digit is decimal.
• n allows the addition of n digits,
• "n allows the storage of n digits,
• #n allows the suppression of n digits.
The converted address is inserted into the call request.
E Page 20-10
20.4.9 Example: Constructing an X.25 address from an IP address

1 ETHE IBEG NONE
2 ETHE DAD TLAT 0A00 ∗ IP1∗,P400,"8"8"8"8
3 ETHE IEND NONE

2 The machines with addresses 00 00 00 to 00 FF FF in network 10 are routed over a resource
IP1∗
The IP resources have no DRC MASK specified.
The destination resource is a P400 resource of an X.25 link (PS04).
The destination IP address is converted into 12 decimal digits (4 groups of 000 to 255).
The IP addresses are converted as:
• 0A00 0000 to 010 000 000 000
• 0A00 FFFF to 010 000 255 255
The decimal address can be used by an X.25 table record.

1 P400 0 #6"3
1 For the P400 destination resource:

The number between 010 000 000 000 and 010 000 255 255 is modified:
• skip six digits,
• retain the next three digits.
The X.121 number of the X.25 "P400" resource is therefore between
000 and 255 which is the third byte of the destination IP address.
E Page 20-11
20.4.10 Example: Constructing an X.25 address from an IP address, with subnet
route datagrams according to a sub-network address. The "MASK" must be placed before a TLAT option
DAD record. In this case the mask is applied before the IP address is converted to a decimal address.
When the Subnet of a network is not standard, in other words it overlaps two bytes, the destination IP
address can be left rotated to obtain the Subnet in one byte.
Example:
Assuming the IP addresses 0000.1010.0000.000S.SSMM.MMMM.MMMM.MMMM

are defined as: where S are the Subnet bytes
and M the machine address bits.
To form an X.25 address as a function of the Subnet:

1 ETHE IBEG NONE
2 ETHE DAD TLAT 0A0∗ IP1∗,P400,#2"8"8"8"8
3 ETHE IEND NONE

2 The machines of network 10 are routed over a resource IP1∗.
The IP resources have no DRC MASK specified.
The destination resource is a P400 resource of an X.25 link (PS04).
A two steps left rotation is performed on the destination IP address.
Before the rotation, the IP address is: 0000.1010.0000.000S.SSMM.MMMM.MMMM.MMMM
After the rotation, the Ip becomes: 0010.1000.0000.0SSS.MMMM.MMMM.MMMM.MM00
The destination IP address is converted into 12 decimal digits (4 groups of 000 to 255).
The IP addresses are converted into:
• "040 000 and so on" to "040 007 and so on"
The decimal address can be handled by an X.25 table record.

1 P400 0 4329#5"1
1 For the P400 destination resource:

The number between "040 000 and so on" and "040 007 and so on" changes:
• start with 4329,
• skip five digits,
• keep one digit.
The X.121 number of the X.25 "P400" resource is therefore between 43290 and 43297.
E Page 20-12
E
20.4.11 "Reverse ARP" function
RARP = Reverse Address Resolution Protocol (RFC 903).

This function enables IP machines that do not know their IP address to obtain their address from the
RARP protocol with the Megapac.
An RARP table with the ADD function must be constructed immediately after the input MAC program of
the IP or TIP descriptor concerned. (IBEG then IEND is the mandatory minimum).

ETHE IBEG
ETHE etc ...
ETHE IEND
ETHE ADD NONE 00608CF2041D 192.1.1.5,E
ETHE ADD NONE 00608CF2067D 128.1.5.5,S
SELECTOR IP or TIP Specifies the Ethernet or Token Ring MAC address of the machine using
the RARP protocol (in hexadecimal and uppercase).
GENERATOR IP Specifies the IP address of the machine used in the RARP protocol,
(dot notation or upper-case hexadecimal).
a comma (as separator), and the "E" or "S" protocol.
"E" for the Ethernet protocol.
"S" for the IEEE 802.3 Ethernet protocol with SNAP.
TIP Specifies the IP address of the machine using the RARP protocol
• The NOP function is not allowed in an ADD function sequence.

• For resource(0) of the IP descriptor concerned, the OPTION parameter must be ARPS+RARP.
For the same IP or TIP descriptor, RARP protocol or BOOTP protocol (or nothing) can be used.
E Page 20-13
E
20.4.12 "BOOTP" function
BOOTP = BOOTstrap Protocol (RFC 1048).

This function enables IP machines that do not know their IP address to obtain their address via a server
(in this case the Megapac) without using the RARP protocol. BOOTP is based on UDP.
An address table with the ADD function must be constructed immediately after the input MAC program of
ETHE IBEG
ETHE etc ...
ETHE IEND
ETHE ADD NONE 008002000D0F 192.1.1.99
for the first "ADD" record

SELECTOR IP or TIP Specifies the Ethernet or Token Ring MAC address of the Megapac
(hexadecimal and uppercase).
GENERATOR IP or TIP Specifies the IP GATEWAY address of the Megapac.
for the subsequent "ADD" records

SELECTOR IP or TIP Specifies the Ethernet or Token Ring MAC address of the machine using
the BootP protocol, (hexadecimal and uppercase).
GENERATOR IP Specifies the IP address of the machine used in the BootP protocol,
TIP Specifies the IP address of the machine using the BootP protocol

• For resource(0) of the IP descriptor concerned, the OPTION parameter must be NONE
(OPTION parameter = RARP must not be used).
For the same IP or TIP descriptor, RARP protocol, or BOOTP protocol (or nothing) can be used.
E Page 20-14
E
20.4.13 "Static route" function
It may be necessary to define a "static route" (MAC address, IP address combination) in networks with
several routers over the same LAN without using the RIP protocol.

ETHE IBEG
ETHE etc ...
ETHE IEND
ETHE ADD NONE 00608CF2041D 192.1.1.0,E
ETHE ADD NONE 00800DE1455D 128.1.0.0,S
SELECTOR IP or TIP Specifies the Ethernet or Token Ring MAC address of a router,
(hexadecimal and uppercase).
GENERATOR IP Specifies the IP address of remote network,
TIP Specifies the IP address of remote network

• In an IP address, when the machine number is "0", the IP address specifies all the machines in the
network.
ADD none MAC-1 Netid-B

Megapac ADD none MAC-2 Netid-C
Netid-A
Router Router
MAC-1 address MAC-2 address
Netid-B Netid-C
E Page 20-15
20.4.14 « Default Route» and « Local Network » Function
The « static route » function can be used to define:

• The MAC address of a router by default,
• and to specify all the machines in the network.

ETHE IBEG
ETHE etc ...
ETHE IEND
1 ETHE ADD NONE 00608CF2041D 0.0.0.0,E
2 ETHE ADD NONE 000000000000 135.21.0.0,E
3 ETHE ADD NONE 000000000000 135.22.0.0,E
The « 1 » recording defines the MAC address of a router by default.
SELECTOR Specifies the MAC address of a router by default.

GENERATOR IP address: 0.0.0.0
The « 2 et 3 » recordings define the IP local address:
SELECTOR The MAC address is equal to 0 (12 zero).

GENERATOR Specifies a local network address (Net) with a machine address (Id) =0

• In an IP address, when the machine number is "0", the IP address specifies all the machines in the
network.
E Page 20-16
20.4.15 Optimizing the "ARP table" (Address Resolution Protocol)
IP datagram routing uses an "ARP table" which saves the "MAC address, IP address" pairs and the
associated LAN or WAN resource. The VIEW command is used to view the "ARP table".
This "ARP table" updates itself using the following information:
1. Static routes definition (ADD records in the MAC table),
2. Data from the ARP message responses,
3. Data from the RIP broadcast messages.
20.4.15.1 "Subnet mask" function
When the "subnet mask" function is not used, (by default the subnet mask = 255.255.255.255), a "WAN
resource, IP address" combination is stored in the "ARP table" for each IP machine at the other end of
the WAN.
Routing performance can be optimized by reducing the number of records in the "ARP table" by retaining
only the "WAN resource, NetId" combination.
To do so, a record with the MASK function can be inserted immediately after the input MAC program of
the IP or TIP descriptor concerned, to indicate a subnet mask for each connection. (IBEG then IEND is
the mandatory minimum).

1 ETHE IBEG NONE
2 ETHE DAD NONE C00101∗ IP01
3 ETHE IEND NONE

4 ETHE MASK NONE IP01 255.255.255.0
4 ETHE MASK NONE resource IP address mask (complete)

∗ is allowed in dot notation,
or hexadecimal uppercase
IP destination address datagrams starting with "C00101" are routed over resource IP01. Resource IP01
includes a DRC MASK to WAN.
Record number 4 after the IEND of the ETHE descriptor specifies a mask of 255.255.255.0 for resource
IP01.
The "ARP table" then contains one "WAN resource, NetId" record which is the result of a logical AND
between the IP address of the number 2 SELECTOR and the IP mask of the number 4 GENERATOR.
• The NOP function is not allowed in a MASK (or ADD) function sequence.
• Do not confuse this static MASK with the dynamic MASK function that can be specified between the
IBEG and IEND delimiters.
E Page 20-17
20.4.15.2 Filtering the data from the ARP messages (of the LAN)
The automatic updating of the "ARP table", based on the ARP exchanges coming from the LAN, can be
disabled by using the REJ option for the first record of the MAC table associated with the IP or TIP
descriptor (i.e. the IBEG record).
20.4.15.3 Filtering the data from the RIP broadcast (of the LAN)
The automatic updating of the "ARP table", based on the RIP broadcast messages data coming from the
LAN, can be disabled by using the REJ option for any MAC record associated with the descriptor, by the
use of the ADD function.
20.4.15.4 ARP LAN aging, ARP WAN aging
By default, the "MAC address, IP address" pairs do not incorporate the notion of aging.
The "TIME" function of the MAC table can be used to specify an "age" limit for the "MAC address, IP
address" pairs of the ARP table. The notion of "age" only applies to dynamic inputs and not to static
routes.
The "TIME" recording must be placed immediately after the input MAC program of the LAN or TLAN
descriptor concerned. (IBEG then IEND is the obligatory minimum)
ETHE IBEG
ETHE IEND
ETHE TIME NONE Aging LAN, Aging WAN
LAN-side aging in seconds.

• Aging LAN
This aging affects the "MAC address, IP address" pairs acquired by datagrams coming from
the LAN side.

WAN-side aging in seconds.
• Aging WAN
This aging affects the "MAC address, IP address" pairs acquired by datagrams coming from
the WAN side.
E Page 20-18
20.5 "RFC 1356 (877) GATEWAY" function
The TYPE/ IP and TIP descriptors can be used to provide IP gateway connections between two local
area networks. At each end, the Megapac gateway function operates at IP datagram level. It places the
datagrams in one or more data packets in accordance with the X.25 link protocol connecting the two
gateways.
TCP/IP Megapac X.25 Megapac TCP/IP

on on
Ethernet or Token-Ring Ethernet or Token-Ring
The tables on the following pages summarize the parameters that can be set in an IP or TIP link
descriptor.

Name Settings
NAME 4 characters Name of a link.
TYPE IP IP gateway function on an Ethernet network.
TIP IP gateway function on a Token Ring network.
By default = 1 This parameter defines the number of remote RLE with
which a data link can be set up.
DEFAULT MAC PROTOCOL ETHR Specifies an IEEE 802.3 Ethernet protocol operation.
In a Token Ring LAN this parameter is not used.
SNAP Specifies IEEE 802.3 Ethernet protocol operation with SNAP
(Sub Network Access Protocol)
In a Token Ring LAN this parameter is not used.
E Page 20-19

Name Settings
characters maximum Each logical resource of the IP or TIP descriptor represents
a virtual circuit to a remote gateway.
XXXX "CALL+PVC" or "CALL" type logical resource

Name of the logical resource associated with the "serial"
link descriptor (X.25, for example) linking this Megapac to
the Megapac connected to the remote RLE.
.... "OUT+PVC" or "OUT" type logical resource
CIRCUIT TYPE By default = CALL+STAT Identifies the main I/O characteristics of the resource.
CALL+OSI CALL: This logical resource initiates transmission of the
call request packet (X.25) requesting setup of the virtual
circuit between the two remote gateways.
OSI (mandatory): The gateway complies with RFC 1356
which defines the encapsulation of IP datagrams in X.25
packets.
CALL+PVC+OSI CALL+PVC: This logical resource initiates transmission of
the call request packet (X.25) requesting setting up of the
virtual circuit between the two remote gateways, when a
datagram is to be sent.
OSI (mandatory): Same remark as above.
OUT+OSI OUT: This logical resource corresponds, in one of the two
remote gateways, to a "CALL+OSI" type logical resource of
the other gateway.
OUT+PVC+OSI OUT+PVC: This logical resource corresponds, in one of the
two gateways, to a "CALL+PVC+OSI" type logical resource
of the other gateway.
IDLE The virtual circuit is cleared if it sends no further data for
the time set by the INACTIVITY TIMER/ parameter of the
BASE descriptor.
Do not use this setting for a "CALL+OSI" or "OUT+OSI"
type logical resource (without the type PVC).
GATE A password controls access to a destination logical
resource.
E Page 20-20
E
OPTIONS
(continue) TALK
NAME Routing is based on a name previously defined in the

NAME file.
Selects the presentation mode.
ARPS Forces the Megapac to send an ARP message before each
SYN request.
RARP Specifies operation in Reverse ARP.
The MAC table must include a record with the "ADD"
function.
SQM Source Quench - WAN congestion management in IP RFC
1356 gateway mode.
Slows the throughput of a local host when the Megapac
node is approaching WAN congestion
PORT MATCH By default = SRCE+???? Reserved.
WILD Reserved.
SRCE Reserved.
DEST Reserved.
NO Setting to be used in "IP gateway" mode.
PRESET PORT 0 to 32767 In "IP gateway" mode use 0.
MATCH By default = 2048
REVERSE TELNET 0 to 32767 In "IP gateway" mode use 0.
PORT By default = 0

By default = 0
By default = 0
MANAGED Setting from 0 to 32767 Required bandwidth, in characters per second tenth.
BANDWIDTH By default = 0 Only towards an X25 link.
Incoming resource:
routing.
In "IP gateway" mode use 0.
E Page 20-21
E
20.5.3 Preliminary choice of VC type
1) Permanent virtual circuit

The virtual circuit is set up when the link is RESTarted. The setup procedure is independent of the traffic
detected on the RLEs. In the event of failure, the call request packet is sent every five seconds.
• In a Megapac, the logical resource attached to the descriptor (IP or TIP) is set to "CIRCUIT TYPE/
CALL” and transmits the call request packet.
• In the other Megapac, the logical resource attached to the descriptor (IP or TIP) is set to "CIRCUIT
TYPE/ OUT".
2) Virtual circuit setup when frames are to be sent to the remote gateway.
The virtual circuit is set up when the gateway detects a frame to be sent over the RLE or the local ring,
after scanning the self-learning and MAC tables (see Routing), to the remote RLE associated with this
virtual circuit.
• In one Megapac, the logical resource attached to the descriptor (IP or TIP) is set to "CIRCUIT TYPE/
CALL+PVC" and transmits the call request packet when a frame to be transmitted is detected.
• In the other Megapac, the logical resource attached to the descriptor (IP or TIP) is set to "CIRCUIT
TYPE/ OUT+PVC" and can only receive the call request packet.
Insofar as each RLE can initiate a transmission, it is necessary to define two "crossover" virtual circuits,
each gateway having a "CALL+PVC" and "OUT+PVC" logical resource respectively. It is possible with
PVC logical resources to program the clearing of the virtual circuit set up if there is no traffic.
20.5.4 Further information on configuring the X.25 network
X.25 link
The configuration procedure on the X.25 network side uses Megapac's standard X.25 configuration
elements.
The only parameters to be taken specifically into consideration are:
• the PACKET SIZE/ parameter for logical resources; it must be defined with the maximum possible
setting on the X.25 link.
• the BUFFERS/ parameter; it must complete the number of logical resources configured for the TYPE/
IP descriptor. The settings to be used in IP and TIP mode are:
• 40 for Ethernet and 4 Mbit/s Token Ring.
• 80 for 16 Mbit/s Token Ring.
X.25 table
To comply with RFC1356, the X.25 table call record must include a USER DATA field = CC.
E Page 20-22
20.5.5 Example of an RFC1356 (877) gateway


TYPE/ X25 TYPE/ X25
NPI/ YES WAN NPI/ YES
PACKET SIZE/ 128 PACKET SIZE/ 128
ADDRESS/ DTE ADDRESS/ DCE
NAME/ IP01 NAME/ IP01

CIRCUIT TYPE/ CALL+PVC+OSI CIRCUIT TYPE/ OUT+PVC+OSI
MODE/ SQM MODE/ SQM
PORT MATCH/ NO PORT MATCH/ NO
NAME/ ETHE NAME/ ETHE
TYPE/ IP TYPE/ IP
NPI/ YES NPI/ YES
MEGAPAC 1 MEGAPAC 2
LAN LAN
11.XX.XX.XX 10.XX.XX.XX
Figure 20-2 Megapac in RFC1356 gateway mode
The example above specifies the significant parameters of an RFC1356 gateway function.
When a machine in LAN 11.xx.xx.xx wants to communicate with a machine in LAN 10.xx.xx.xx,
Megapac number 1 initiates the connection over the WAN.
Megapac 1 has the gateway address 11.11.11.11

X.25 table
P300 0 1234567 CC
E Page 20-23
E
MAC table
NAME FUNCTION OPTION
SELECTOR GENERATOR
ETHE IBEG NONE
ETHE DAD NONE 0A∗ IP01
ETHE DAD NONE 0B0B0B0B GATEWAY

ETHE IEND NONE
Megapac 2 has the gateway address 10.10.10.10

X.25 table
IP01 0 1234567 CC
MAC table
ETHE IBEG NONE
ETHE DAD NONE 0B∗ IP01
ETHE DAD NONE 0A0A0A0A GATEWAY

ETHE IEND NONE
The "VIEW" command lets you analyze the learning table of the network machines.
ETHE: VIEW
Number Channel Physical Address IP Address

1 Local LAN 0000A2064210 10.0.0.0 (0A000000)
2 Local LAN 0000A2064210 89.0.0.0 (59000000)
3 Local LAN 0000A2064210 134.20.0.0 (86140000)
4 Local LAN 0000A2064210 135.62.0.0 (873E0000)
5 Local LAN 0000A2064210 136.4.0.0 (88040000)
6 Local LAN 0000A2064210 136.27.0.0 (881B0000)
7 Local LAN 0000A2064210 138.62.0.0 (8A3E0000)
8 Local LAN 0000A2064210 192.1.0.0 (C0010000)
9 Local LAN 008002000769 9.0.0.0 (09000000)
10 Local LAN 0000C0597663 10.50.30.48 (0A321E30)
11 Local LAN 08005AA0829B 10.52.6.2 (0A340602)
12 Local LAN 0000C0163266 10.50.30.134 (0A321E86)
E Page 20-24
E
20.6 "IP Switching" function
NAME/ P400
DRC MASK/ ....
CIRCUIT TYPE/ CALL
BUFFERS/ 40
NAME/ IP01
NAME/ PS04
DRC MASK/ . . . .
TYPE/ X25 WAN2
CIRCUIT TYPE/ CALL
BUFFERS/ 40 NPI/ YES only FTP traffic
NAME/ IP01
PORT MATCH/ NO PACKET SIZE/ 128 on 135.11.35.162
DRC MASK/ . . . . ADDRESS/ DTE
CIRCUIT TYPE/ CALL
BUFFERS/ 40
NAME/
PORTIP01
MATCH/ NO
DRC MASK/ . . . .
CIRCUIT TYPE/ CALL
BUFFERS/ 40
PORT MATCH/ NO NAME/ P300
NAME/ ETHE DRC MASK/ ....
TYPE/ IP CIRCUIT TYPE/ CALL
NPI/ YES BUFFERS/ 40
CHANNELS/ 1 NAME/ PS03
TYPE/ X25 WAN1
NPI/ YES all traffic except FTP traffic
PACKET SIZE/ 128 on 135.11.35.162
LAN ADDRESS/ DTE
The IP Switching function uses extended routing possibilities (see paragraph 20.4.3).
In this example, WAN2 only sends FTP type data streams to machine 135.11.35.162, and WAN1 sends
all the other datagrams.
The MAC table (IBEG NOT option) is used to this effect:

1 ETHE IBEG NOT
2 DAD JUMP 870B23A2 JDD1
3 DAD NONE ∗ IP0∗,P30∗
4 JDD1 DPR NONE 21, IP0∗,P40∗
5 DAD NONE ∗ IP0∗,P30∗
6 ETHE IEND NONE
1 Input terminal of the input MAC program, with the NOT option indicating extended routing.
2 The datagrams of the destination IP address (135.11.35.162) are analyzed by the MAC program beginning
with label JDD1.
3 All the other datagrams (except those of the destination IP address [135.11.35.162]) are routed to a
resource with a P30∗ type name
4 The datagrams of the destination IP address (135.11.35.162), which transport an "FTP" type data flow, are
routed to a resource with a P40∗ type name
5 The other data flows of the destination IP address (135.11.35.162) are routed to a resource with a P30∗
E
type name
6 Output terminal of the input MAC program
E
20.7 "TELNET" function
In the Telnet environment, Megapac offers the following functions:

• "PAD TELNET" (in other words, Telnet client), enabling a local or remote asynchronous terminal to
communicate with a TCP/IP machine having the Telnet server function.
• "REVERSE PAD TELNET" (in other words, Telnet server), enabling a TCP/IP machine to
communicate with a local or remote asynchronous terminal (a printer, for example).
Each simultaneous "Pad Telnet" or "Reverse Pad Telnet" session, requires the reservation of 1
emulation buffer (Terminal Emulation Buffer parameter of the "BASE" descriptor).
For each function, the size of the distant machine must be limited to a TCP window size inferior or equal
to 32767 (« 7FFF » hexa).
20.8 Pad Telnet (or Telnet client)
TERM Asynchronous TERM local

TERM terminals TERM
MEGAPAC TCP/IP HOST
MEGAPAC Telnet Telnet
customer server
X.25 distant
Three elements are needed for "Pad Telnet" configuration:

• The Pad Telnet function is enabled by the TELN option of a record in the NAME table.
• The MAC table is used to mark the IP addresses used.
• The IP or TIP resource is used to exchange datagrams over the Ethernet or Token-Ring LAN.
20.8.1 Local Pad Telnet
An asynchronous terminal accesses the Telnet service using the presentation service. The
corresponding record in the NAME table contains the option TELN.
typical record in the NAME table:
NAME/ PARSUN1
DRC MASK/ IP01
CALL PRIORITY/ 0
BILLING/ D
OPTIONS/ TELN+PROF
The user requests "PARSUN1"
The NAME table record activates the Telnet service.
The NAME table record specifies the IP or TIP resource to be used via its DRC.
The PROF option defines a specific X.3 profile having the same name as the specified DRC.
E Page 20-26
E
20.8.2 Remote Pad Telnet
An X.25 call request packet arrives at a node for which the link is set to ECM=IN (Extended Call
Management). The X.25 resource used includes the NAME option. The MAC table is used in input
mode, and has a routing record including the TALK option. The GENERATOR field of this record has a
service name matching an entry in the NAME table.
sample MAC record for the X.25 link:
Name Function Option Selector Generator
PSXX IBEG NONE
PSXX DAD TALK 123456 PARSUN1
PSXX IEND NONE
The path is then the same for the local Pad Telnet.
With the service activated, the local or remote call is routed over a resource (IP01 in the example) of the
IP or TIP descriptor (TKNR, for example).
The first records of the MAC table contain:
• information on the Token-Ring board if that board is used.
• the source and destination IP addresses used on the network.
then:
• an input record for the source IP address, for resolving the association between IP address and MAC
address (ARP procedure).

.... PU NONE UTP,16 xxxxxxxxxxx
.... PU NONE PARSUN1 sourceip,destinationip
TKNR IBEG NONE
TKNR DAD NONE sourceip GATEWAY
TKNR IEND NONE
"sourceip" is the IP address assigned to the local or remote caller, specified in hexadecimal
and upper-case.
"destinationip" is the IP address of the TCP/IP machine acting as the Telnet service, specified in
hexadecimal and upper-case.
"GATEWAY" is a keyword, for including an ARP procedure.
E Page 20-27
E
20.8.3.1 Telnet negotiation
By default, a Telnet session is opened on port 23 and the terminal type is DEC-VT100.
The PU line of the MAC table specifying the source and destination IP addresses can have the following
information added:

.... PU NONE PARSUN1 sourceip,destinationip
.... NONE negotiation port,type
"-" the "hyphen" is mandatory, at the end of the first PU line.

"port,type" the "comma" is always mandatory.
"port" the "port" number is optional and defaults to 23 (decimal).
"type" the terminal "type" is mandatory (for example: DEC-VT100 , DEC-VT220 ...).
NONE: can be used to cancel the TELNET level, in which case the data is transmitted
and received in purely TCP/IP form. This option enables machines connected by
asynchronous link to communicate transparently with UNIX machines running under
TCP/IP.
"negotiation" is a hex character string (Telnet command) that the Megapac sends to the Host at the
start of the Telnet session.
(see $ 20.10)
All of the Telnet options and commands to be sent are defined in the RFCs.
example of negotiation: "FFFD00FFFB00" initiates transition to binary mode, by sending
IAC DO BINARY and IAC WILL BINARY to the HOST.
FF = IAC (Interpret As command)
FD = DO
FB = WILL
00 = binary mode
Another negotiating method can be used with the command format 7FFB00
7F = local command
FB = WILL
00 = binary mode
The Megapac can manage the « TELNET Send Location ».
The « FFFB17 » sequence, that is, « Will Send Location » must be negotiated.
In that case, when the Host sends back « DO Send Location », the Megapac answers:
« MAC source address»-« X121 source address».
Both fields are separated by an « hyphen », one or both fields can be eliminated.
The Megapac does not accept next functions (it replies « WONT »):
06 = do timing mark
1F = window size
20 = send terminal speed
23 = display location
24 = environment variables
27 =
C8 =
E Page 20-28
E
20.8.3.2 Alternative routing
The PU line of the MAC table specifying the source and destination IP addresses can have the following
information added:

.... PU NONE name1,name2 sourceip,destinationip
"name2" is used when the Telnet connection on "name1" (PARSUN1, in the example), fails to be set up.
In this case, the connection on "name1" (PARSUN1) is disconnected and Telnet emulation is canceled.
"name2" is interpreted instead of "name1". The NAME table is analyzed again. This second analysis of
the NAME table can result in another Pad Telnet session on another IP or TIP resource (can lead to X.25
rerouting).
In the case of another Telnet session, the MAC table must contain a PU record with the "name2" of the
previous PU record as "name1".
The sequence name1, name2, name3, etc could be envisaged, using a number of records in the NAME
table and a number of PU records in the MAC table.
E Page 20-29
20.8.4 IP link (Pad Telnet) descriptor parameters

Name Settings
TYPE IP IP operation on an Ethernet network.
TIP IP operation on a Token Ring network.
CHANNELS 0 to 4096 This parameter defines the number of line units with which
By default = 1 the data link can be set up.
DEFAULT MAC PROTOCOL ETHR Specifies Ethernet protocol operation.

In a Token Ring network this parameter is not used.
SNAP Specifies an IEEE 802.3 Ethernet protocol operation with
SNAP (Sub Network Access Protocol).
20.8.5 IP (Pad Telnet) logical resource parameters

Name Settings
characters maximum Each logical resource provides a connection with a
TCP/IP machine.
DRC MASK 4 characters Fully or partly identified a destination resource, used for
maximum routing.
By default = . . . . In PAD TELNET operation, this DRC Mask is not used.
CALL+STAT
OUT+PVC+OSI In PAD TELNET mode, the resource is "outgoing" only
OSI (conforming to RFC1356).
BUFFERS Setting from 1 to 240 Setting defining the number of buffers available to this
MODE NONE Does not manage "Source Quench" messages.
E Page 20-30
E
PORT MATCH
By default =
SRCE+ ????
Criterion for selecting a resource according to the port
identifying the application program.
The parameters are mutually exclusive.
NO Routing is based only on IP addresses.
SRCE Routing is based on the source port N° and IP addresses.
DEST Routing is based on destination port N° and IP
addresses.
Setting to use in Pad Telnet mode.
WILD Routing is based on port N° and IP addresses, and as a
last resort, IP addresses only.
WILD is normally used only at the end of a group.
PRESET PORT MATCH 0 to 32767 TCP port N° to be used in PAD Telnet mode.
By default = 2048 as a rule, "23" for Telnet
0 if Port Match = NO
REVERSE TELNET PORT 0 to 32767 TCP port N° to be used in Reverse Pad Telnet mode.

By default = 0
By default = 0
32767 Only towards an X25 link.
By default = 0 Incoming resource:
Bandwidth>0, allows to define the requested speed
before routing.
E Page 20-31
20.9 Reverse Pad Telnet (or Telnet service)
TERM Asynchronous TERM local

TERM Terminals TERM
MEGAPAC TCP/IP HOST
MEGAPAC Telnet Telnet
service client
X.25 remote
In "Reverse Pad Telnet" mode, the following elements are used:

• The MAC table for the Ethernet or Token-Ring link is used to select an IP or TIP resource according
to the Destination-IP address of the datagram received from the network.
• The IP or TIP resource selected is used for routing by its DRC Mask (and, if necessary, according to
the TCP port N°) to a local asynchronous link (for example, a printer, a terminal, the command port
accessing "BASE", etc), or an X.25 link, if the asynchronous terminal is remote.
A datagram received from the network asks for the "destinationip" address.
The link is a Token-Ring network, the associated descriptor is "TKNR" and the resources are "IP0x".
The first record of the MAC table contains:

• information related to the Token-Ring, if that board is used.
then:
• input records for the "destinationip" address, from which to:
• associate an IP or TIP resource.
• resolve the association between IP address and MAC address (ARP procedure).

TKN∗ PU NONE UTP,16 xxxxxxxxxxx
TKNR IBEG NONE
TKNR DAD NONE destinationip IP01
TKNR IEND NONE
E Page 20-32
20.9.1.1 Telnet negotiation, in Reverse Pad Telnet
A PU recording in the MAC table allows the negotiation of the Telnet options (see $ 20.10).
This recording is only required in particular exploitation cases.

Name of the IP or TIP resource PU NONE (empty) (empty) or
used in Reversed Pad Telnet negotiation
The « GENERATOR » field specifies the type of negotiation.
GENERATOR MEANING AND SCOPE’

(empty) There is no negotiation when the GENERATOR does not hold any characters.
In this mode, the data is transmitted and received in purely TCP/IP form. This option
enables machines, connected by asynchronous link, to communicate transparently with
UNIX machines running under TCP/IP.
negotiation Is a hex character string (Telnet Command) that the Megapac sends to the Host at the
start of the Telnet session. The whole Telnet option and commands to be sent are
defined in the RFCs.
« - », the « Hyphen » is mandatory, at the end of the first PU line. It must not separate a
couple of Hexa value.
Sequence Example for a TN3270 session:
FFFD18FFFA1801FFF0-
FFFD00FFFB00-
FFFD19FFFB19
20.9.2 TCP port N° in Reverse Pad Telnet mode
It may be beneficial to use only one "destination ip" address for several asynchronous terminals (printers,
for example).
In this case, continuing with the above example, you can associate a number of resources IP01 with the
link descriptor TKNR, each IP01 resource having:
• a different DRC Mask
• PORT MATCH\ DEST
• REVERSE TELNET PORT\ nnn
E Page 20-33
20.9.3 IP link (Reverse Pad Telnet) descriptor parameters

Name Settings
TYPE IP IP operation on an Ethernet network.
TIP IP operation on a Token Ring network.
CHANNELS 0 to 4096 This parameter defines the number of line units with which
By default = 1 the data link can be set up.
DEFAULT MAC PROTOCOL ETHR Specifies Ethernet protocol operation.

SNAP Specifies an IEEE 802.3 Ethernet protocol operation with
SNAP (Sub Network Access Protocol).
MAC table
ETHE IBEG
ETHE DAD NONE 0B0B0B0B IP01
ETHE IEND
NAME/ IP01
DRC MASK/ BE00 NAME/ BE00
CIRCUIT TYPE/ CALL+PVC+OSI OPTIONS/ NONE
OPTIONS/ TALK+INAC RP/ 0
BUFFERS/ 40
PORT MATCH/ DEST
PRESET PORT MATCH/ 0 BASE:
REVERSE TELNET PORT/ 23
...
...
PAD ENABLE/ E TERMINAL EMULATION BUFFER/ 1
...
LAN NAME/ ETHE
11.XX.XX.XX TYPE/ IP
NPI/ YES
CHANNELS/ 1
Figure 20-3 "Telnet Server" configuration, on "BE00" Virtual Configuration Port
The IP address 11.11.11.11 is allocated to the configuration port interface (BE00) of the Megapac.
E Page 20-34
20.9.4 IP (Reverse Pad Telnet) logical resource parameters

Name Settings
NAME 4 alphanumeric Name of a logical resource
characters maximum Each logical resource provides a connection with a
TCP/IP machine.
Mandatory in REVERSE PAD TELNET mode.
CALL+STAT
CALL+PVC+OSI In REVERSE PAD TELNET mode, the IP or TIP resource
establishes the connection by DRC.
OSI (conforms to RFC1356).
PVC+OSI The resources that are not « CALL » can be configured at
the end of the group resource to warn the « Telnet
Client » that no resources are available in the « Telnet
server ».
These resources are used as overflowing resources.
Then, the « Telnet Client » receives the NUMBER MENU
specified in the resource.
TALK Activates the Telnet server function (REVERSE PAD
TELNET), and uses an emulation buffer.
INAC A "Reverse Pad Telnet" session is cleared when the
Megapac observes traffic absence for a period of around
5 minutes.
MBIT Used to specify a transfer of IP datagrams in linked X.25
packets (via the Mbit).
BUFFERS Setting from 1 to 240 Setting defining the number of buffers available to this
E Page 20-35
E
PORT MATCH
By default =
SRCE+ ????
Criterion for selecting a resource according the port
identifying the application program.
The parameters are mutually exclusive.
NO Routing is based only on IP addresses.
In this case, RTP = 0.
SRCE Routing is based on source port N° and IP address.
DEST Routing is based on destination port N° and IP
addresses.
Setting to be used in REVERSE PAD TELNET mode if
necessary with the RTP parameter.
WILD Routing is based on port N° and IP addresses and, as a
last resort IP addresses only.
WILD is normally used only at the end of a group.
PRESET PORT MATCH 0 to 32767 TCP port N° to be used in PAD Telnet mode.
REVERSE TELNET PORT 0 to 32767 TCP port N° to be used in Reverse Pad Telnet mode.
(RTP) By default = 0 as a rule, "23" for Telnet
DISC MODE By default = 0 not used
MENU NUMBER 0 to 32 For the resource with TYPE CIRCUIT that are not
By default = 0 « CALL », a menu can be specified to warn a « Telnet
Client » that the « Telnet Server » can not reply to its
demand.
HELP NUMBER By default = 0 not used
NEWS NUMBER By default = 0 not used
CALL PRIORITY 0 to 15 Calling line priority ( CP >= RP ).
By default = 0
By default = 0
BANDWIDTH Setting from 0 to 32767 Required bandwidth, in characters per second tenth.
Incoming resource:
before routing.
E Page 20-36
20.10 Telnet option negotiation - Protocol
The first exchange that normally takes place across a Telnet connection is option negotiation. The option
negotiation is symmetric, either side can send a request to the other.
Either side can send one of four different requests for any given option.
1. WILL (FB) The sender wants to enable the option itself.
2. DO (FD) The sender wants the receiver to enable the option.
3. WONT (FC) The sender wants to disable the option itself.
4. DONT (FE) The sender wants the receiver to disable the option.
Start of negotiation begins by IAC (FF) « Interpret As Command ».
20.10.1 Six scenarios for Telnet option negotiation
Sender Receiver Meaning
WILL (FB) → Sender wants to enable option,

← DO (FD) receiver says OK
WILL (FB) → Sender wants to enable option,

← DONT (FE) receiver says NO
DO (FD) → Sender wants receiver to enable option,

← WILL (FB) receiver says OK
DO (FD) → Sender wants receiver to enable option,

← WONT (FC) receiver says NO
WONT (FC) → Sender wants to disable option,

← DONT (FE) receiver must say OK
DONT (FE) → Sender wants receiver to disable option,

← WONT (FC) receiver must say OK
Option negotiation requires 3 bytes: the IAC byte, followed by the byte for WILL, DO, WONT, or DONT,
followed by an ID byte specifying the option to enable or disable.
20.10.2 Options example
Option (hexa) Name RFC
00 Binary mode 856

01 Echo 857
03 Suppress go ahead 858
05 Status 859
06 Timing mark 860
18 Terminal type 1091
1F Window size 1073
20 Terminal speed 1079
E
21 Remote flow control 1372
22 Linemode 1184
24 Environment variables 1408
E Page 20-38
21. TYPE/ IPX and TIPX descriptors
21.1 General
The TYPE/ IPX and TIPX descriptors are used to associate "Novell" functions with an Ethernet or Token-
Ring link physically installed in the cabinet.
For Token-Ring operation, the system software must be in 512 byte buffers.
The tables on the following pages summarize the different parameters that can be altered in an IPX or
TIPX link descriptor.

Name Settings
TYPE IPX Manages the IPX (Novell) protocol on an Ethernet network.
TIPX Manages the IPX (Novell) protocol on a Token Ring network.
NEW PHYSICAL YES On an Ethernet or Token Ring link, the first descriptor using
INTERFACE this link must be NPI=YES.
(NPI) By default = NO The other descriptors using the same Ethernet or Token Ring
link must be NPI=NO.
By default = 1 This parameter defines the number of remote RLE with which a
data link can be set up.
MAC PROTOCOL AUTO The Megapac adapts itself to the protocol supported on the link.
SNAP The Megapac supports only the SNAP (Sub Network Access
Protocol) for this link.
8022 The Megapac supports only the 802.2 LLC (Logical Link Control)
protocol for this link.
ETHR The Megapac supports only the Ethernet "DIX" (Digital
equipment - Intel - Xeros ) protocol for this link.
8023 The Megapac supports only the "IEEE 802.3" Ethernet protocol
for this link.
TYPE/ IPX and TIPX descriptors
E Page 21-1

Name Settings
characters maximum
DRC MASK 4 characters Fully or partly identifies a destination resource, used for
maximum routing.
XXXX "CALL" - type logical resource
Name of the logical resource attached to the "WAN" link
descriptor (for example, X.25).
.... "OUT+PVC" - type logical resource
DRC MASK is not used.
CALL+STAT
CALL The resource name specified by DRC MASK/ is the
OUT+PVC The NAME/ of this resource is used as the destination
resource of another Megapac resource.
OPTIONS By default : NONE No options required.
IDLE The virtual circuit is cleared if it is no longer transmitting
information during the time predefined by the
INACTIVITY TIMER/ parameter of the BASE descriptor.
BUFFERS Setting from 1 to 240 Setting determining the number of buffers available to
By default = 2 this resource.
BROADCAST FILTER 0 to 12000 Interval in tenths of a second at which broadcast or
TIMER By default = 0 group broadcast packets are sent to the remote network
corresponding to this logical resource.
0: no timer.
12000: no broadcast or group broadcast frames
transmitted.
INHIBIT LEARNING By default = NO Activates learning mode.
The Megapac learns only the routing of the frames
transmitted to the remote RLE corresponding to this
logical resource, by updating the self-learning table using
frames received from this RLE.
YES Disables learning mode.
The Megapac does not enable the learning table with
frames received from the remote RLE corresponding to
this logical resource.
The routing of frames sent to this remote RLE must be
set in the MAC table.
E Page 21-2
E
CALL PRIORITY
RESOURCE PRIORITY
0 to 15
By default = 0
0 to 15
Calling line priority (CP >= RP).
Called line priority..

By default = 0
By default = 0 Incoming resource :
before routing.
21.1.3.1 MAC address of Token-Ring board

descriptor(s) STP,16 local MAC address
UTP,4 board
UTP,16 hexadecimal characters

E Page 21-3
21.1.3.3 « SAP and RIP » message filtering
IPX messages for the selection of « SAP » services and « RIP » routing messages coming from the LAN
can be filtered if requested.
Thus, « SAP and RIP » messages coming from the LAN can’t be sent on the uniting WAN(s).
Therefore, the MAC table is used under input mode.

name of the IP CAD NONE MAC address nothing
or IPX or in hexadecimal and upper-case
descriptor
REJ ∗ and ! jokers are accepted
« CAD » recordings must be located between the IBEG...IEND terminals.

If there isn’t any input MAC program for this descriptor, every « SAP and RIP » messages are accepted.
If there is an input MAC program for this descriptor, « SAP and RIP » messages corresponding to the
specified MAC addresses are :
• accepted if the recording includes the NONE option
• rejected if the recording includes the REJ option.
21.1.3.4 « SAP et RIP » messages filtering example
For the IPX type ETHR descriptor, let’s assume the following input MAC program :

1 ETHR IBEG
2 ETHR CAD NONE 123∗
3 ETHR CAD REJ ∗
4 ETHR IEND
1 Input terminal of the input MAC program

2 MAC address « SAP and RIP » messages beginning with « 123 » are accepted
3 All the other « SAP and RIP » messages are rejected
4 Output terminal of the input MAC program
E Page 21-4
21.2 Example of an "IPX on PPP" configuration

DRC MASK/ TX00 DRC MASK/ EX00
PROTOCOL/ IPX PROTOCOL/ IPX
TYPE/ PPP TYPE/ PPP
NPI/ YES NPI/ YES
WAN (PPP)
ACTIVE/ YES ACTIVE/ YES
IDLE DETECT TIME/ 30 IDLE DETECT TIME/ 30
NAME/ TX00 NAME/ EX00

CIRCUIT TYPE/ OUT+PVC CIRCUIT TYPE/ OUT+PVC
NAME/ TKNX NAME/ ETHX

TYPE/ TIPX TYPE/ IPX
NPI/ YES NPI/ YES
MAC PROTOCOL/ AUTO MAC PROTOCOL/ AUTO
MEGAPAC 1 MEGAPAC 2
LAN
LAN (Ethernet - IPX)
(TokenRing - IPX)
Figure 21-1 Example of an IPX gateway on a PPP link
The example above specifies the significant parameters of an IPX gateway function between an Ethernet
network and a TokenRing network.
In this case the WAN is a point-to-point protocol link.
The "VIEW" command lets you analyze the machines present on the LANs.
ETHX: view
Channel Type SAP-Net IPX-Net Node Socket Hops Server

Local LAN 030C 00000000 00000000 0800091CB69E 400C 1 0800091CB6
Local LAN 045A 00002000 00002000 080086100EB8 4114 1 BB3_BETA_T
TKNX: view
Channel Type SAP-Net IPX-Net Node Socket Hops Server
E
TX00(0) 030C 00000000 00000000 0800091CB69E 400C 3 0800091CB6
TX00(0) 045A 00002000 00002000 080086100EB8 4114 3 BB3_BETA_T
TYPE/ IPX and TIPX descriptors Page 21-5
E Page 21-6
22. TYPE/ ROUT descriptor
The TYPE/ ROUT descriptor is used for IP and/or IPX router operation.
• In TCP/IP mode, the Megapac manages the RIP protocol.
• In a Netware environment, the Megapac provides compatibility with IPX routing algorithms. In this
environment, Megapac propagation includes Netbios broadcast frames.
For a Token-Ring network, the system software must be in 512 byte buffers.
In the same Megapac, the "ROUT" descriptors of sub-type "RIP" and "IPX" can be configured
simultaneously.
Several resources of a single ROUT can be connected to the resources of a single LAN. Thus, the
routing between various Subnet of a single LAN is eased.
The tables on the following pages summarize the different parameters that can be set for the "ROUT"
virtual descriptor in TCP/IP and IPX (Novell) environments.
TYPE/ ROUT descriptor
E Page 22-1
22.1 "Router" function in a TCP/IP environment
22.1.1 Virtual descriptor configuration parameters

Name Settings
NAME Up to 4 characters Name of virtual descriptor.
TYPE ROUT Manages a routing protocol (TCP/IP or Netware).
SUB-TYPE RIP Manages the RIP routing protocol in a TCP/IP environment.
CHANNELS 0 to 4096 Number of logical resources associated with the descriptor.
By default = 1 This parameter defines the number of LAN + WAN with which
the Megapac is connected.
The WAN(s) can be X.25, PPP or Frame Relay links.
POLL INTERVAL 0 to 127 The type ROUT descriptor remains passive during this time (in
By default = 30 second), after a Boot, a Restart...
This timer is used to prevent the WANs from connecting (or
disconnecting) themselves to quickly after a system
reinitialization.
ADDRESS in hexadecimal and Defines an IP Megapac address.
upper-case "NetID LAN side - HostID Megapac"
or in DOT notation. This address must also be used for the router resources that
are dedicated to SNMP management and/or VCP (BE00)
access in Reverse Telnet.
This IP address supports the PING function.
The virtual descriptor of type "ROUT" and sub-type "RIP" recognizes and updates the IP routing
information using the RIP protocol. There are no special parameters other than those of the descriptor
and its resources for standard operation as an RIP router. RIP messages are exchanged (by default)
every 30 seconds.
By default, the MAC table is not used. However in a particular environment, the traffic generated by the
RIP messages may become harmful (over low bit rate WAN links).
Static route
The Megapac can operate without generating RIP messages and in this case the MAC table is used to
define one or more static routes (ROUT function).
Static route and dynamic route prioritization
When a "static route" is defined and the Megapac is informed via RIP exchanges of a "routing signal"
concerning the same NetId, routing is carried out over the route with the smallest metric.
The Megapac accepts a "dynamic RIP" route of the same NetId as a "static route" if the dynamic route
metric is smaller.
Datagram selection
In a TCP/IP network with several routers, it is important to be able to select certain protocols (FTP,
Telnet, etc. ...) to optimize traffic in the network.
The Megapac lets you filter IP, TCP and UDP layer datagrams using the MAC table with the BAR
E
function and the NOT option.
TYPE/ ROUT descriptor Page 22-2

Name Settings
characters maximum Resource "0" is dedicated to the LAN.
The other resources are dedicated to the WAN(s).
XXXX "CALL" type logical resource.
Name of the logical resource attached to the WAN link descriptor
(example, X.25), or service Name when NAME option is used.
.... "OUT+PVC" type logical resource.
CALL+STAT
CALL The resource name specified by DRC MASK/ is the destination
CALL+PVC resource.
OUT+PVC The NAME/ of this resource is used as a destination resource of
IDLE The virtual circuit is cleared if it is no longer transmitting information
during the time predefined by the INACTIVITY DETECT TIMER/ of
the BASE descriptor.
When BROADCAST INTERVAL = 0, no RIP message is generated
and the link is cleared on inactivity at the end of the
INACTIVITY DETECT TIMER/ delay.
When BROADCAST INTERVAL > 0, an RIP message is sent when
the connection is set up and the link is cleared on inactivity when
the INACTIVITY DETECT TIMER/ expires.
If the "RIP" local routing table changes when the link is released, the
Megapac makes a call to transmit the new routing table
("triggered RIP"). The link is then cleared on inactivity when the
INACTIVITY DETECT TIMER/ expires.
NAME The DRC MASK/ indicates a service name that must be configured
in the NAME table. Routing is over the DRC MASK/ of the
associated NAME record.
NAME+TELR Routing by the NAME table, specific to a Reverse Telnet interface
(for access to VCP and/or GIS card configurator).
SNMP Specific routing to the resource of an SNMP type descriptor.
BUFFERS Setting from 1 to 240 Setting determining the number of buffers available to this resource.
By default = 2 40 for Ethernet and 4 Mbit/s Token Ring.
By default = 0
E Page 22-3
E
PORT ADDRESS
upper-case
in hexadecimal and
or in DOT notation.
Defines an IP address for the resource (LAN or WAN side).
In association with the SUBNET MASK/ parameter, the
PORT ADDRESS/ parameter is used to define a network address
(NetId) for each LAN and WAN connected to this Megapac.
NetId = "PORT ADDRESS" AND "SUBNET MASK"
(for SNMP and Reverse Telnet functions on the VCP, this address
must be the same as that defined in the ADDRESS field of the
descriptor).
This IP address replies to the PING function when the resource is in
"DATA" state (possible routing).
BROADCAST in hexadecimal and Address used as message header in IP and RIP BROADCAST
ADDRESS upper-case mode.
or in DOT notation. This address is calculated by the Megapac according to the PORT
ADDRESS parameter.
This address can be modified if the IP addressing plan used does
not conform to the IP class definition.
SUBNET MASK in hexadecimal and Defines a sub-network mask for this port.
upper-case This mask is calculated by the Megapac according to the PORT
or in DOT notation. ADDRESS parameter.
This mask can be modified if the IP addressing plan used does not
conform to the IP class definition.
- see Note "SUBNET MASK"
- for SNMP and Reverse Telnet on the VCP port (BE00), the
SUBNET MASK must be 255.255.255.255.
BROADCAST 30 Defines the intervals between two RIP messages.
INTERVAL in seconds See IDLE OPTION.
"0" causes RIP messages to be deleted.
Note "SUBNET MASK"

The subnet definition (subnet mask of a resource) and/or (subnet mask of a static route) is completed by
the dynamic incorporation of subnet data received in the RIP broadcast messages.
• NetID reception (the last byte of the IP address is NIL)
The last none-nil byte of the IP address gives the class which is allotted to the subnet.
There is no over-classification.
Example: 11.0.0.0 gives a subnet 255.0.0.0
28.0.3.0 gives a subnet 255.255.255.0
135.13.0.0 gives a subnet 255.255.0.0
192.15.0.0 gives a subnet 255.255.255.0
192.0.0.0 gives a subnet 255.255.255.0
• HostID reception (the last byte of the IP address is NIL)

The subnet mask is that of the received IP address class.
Example: 135.13.3.6 gives a subnet 255.255.0.0
28.0.3.5 gives a subnet 255.0.0.0
E Page 22-4
22.1.3 Example of "RIP router in TCP/IP" mode
NAME/ RT01 X25 table

DRC MASK/ P400
CIRCUIT TYPE/ CALL P400 0 12345
BUFFERS/ 40
PORT ADDRESS/ "WAN"
NAME/ ER00 NAME/ RT00 NAME/ P400

DRC MASK/ RT00 DRC MASK/ .... DRC MASK/ ....
CIRCUIT TYPE/ CALL CIRCUIT TYPE/ PVC+OUT CIRCUIT TYPE/ CALL
BUFFERS/ 40 BUFFERS/ 40 BUFFERS/ 40
MODE/ NONE PORT ADDRESS/ "LAN"
NAME/ ETHR NAME/ RIPP NAME/ PS04
TYPE/ IP TYPE/ ROUT TYPE/ X25
NPI/ YES SUB-TYPE/ RIP NPI/ YES
POLL INTERVAL/ 10
ADDRESS/ "LAN"
MEGAPAC - TCP/IP RIP router
LAN WAN
Figure 22-1 Example of a Megapac as an RIP router on TCP/IP
This example shows a configuration of the descriptors and resources of a Megapac as an RIP router in a
TCP/IP environment between an Ethernet LAN and X.25 link (WAN).
The "VIEW" command lets you analyze the IP routing table.
RIPP: VIEW
Num. Channel IP Address Subnetmask Metric

1 RT00(0) 9.0.0.0 (09000000) 255.0.0.0 (FF000000) 5
2 RT00(0) 10.200.10.2 (0AC80A02) 255.0.0.0 (FF000000) 1
3 RT00(0) 12.0.0.0 (0C000000) 255.0.0.0 (FF000000) 2
4 RT01(1) 13.10.10.1 (0D0A0A01) 255.0.0.0 (FF000000) 1
5 RT00(0) 14.0.0.0 (0E000000) 255.0.0.0 (FF000000) 3
6 RT01(1) 15.0.0.0 (0F000000) 255.0.0.0 (FF000000) 2
7 RT00(0) 89.0.0.0 (59000000) 255.0.0.0 (FF000000) 3
8 RT00(0) 126.0.0.0 (7E000000) 255.0.0.0 (FF000000) 5
9 RT00(0) 134.20.0.0 (86140000) 255.255.0.0 (FFFF0000) 3
10 RT00(0) 135.62.0.0 (873E0000) 255.255.0.0 (FFFF0000) 2
11 RT00(0) 136.4.0.0 (88040000) 255.255.0.0 (FFFF0000) 3
12 RT00(0) 136.27.0.0 (881B0000) 255.255.0.0 (FFFF0000) 3
13 RT00(0) 138.62.0.0 (8A3E0000) 255.255.0.0 (FFFF0000) 3
14 RT00(0) 192.1.0.0 (C0010000) 255.255.255.0 (FFFFFF00) 3
When the LAN-Ethernet cable is disconnected, the "Metric" of the associated resource (RT00 in the
example) jumps to 16, that is "inaccessible network".
E Page 22-5
E
22.1.4 Static route in MAC table
The example in Figure 22-2 contains three RIP router Megapacs.

To minimize traffic, Megapac 1 generates no RIP messages (BROADCAST INTERVAL=0).
Because of this, Megapacs 2 and 3 have no knowledge of Megapac 1.
Megapacs 2 and 3 each have a MAC record defining a static route to Megapac 1.
When the subnet mask isn’t informed, the MegaPAC calculates the mask in accordance with the IP
address class.

RIPP ROUT NONE RT01,subnet mask IP address ,metric
(. . . . ,dot notation) (dot notation, decimal)
name of defines a name of WAN side IP address and metric of the static route for
"ROUT" static route resource the WAN.
virtual and An IP address with a null machine identifier
descriptor (0) indicates the network itself.
IP subnet mask
address as a rule, the "metric" is 1
Note The Megapac accepts a "dynamic RIP" route of the same NetId as a "static route" if the
dynamic route metric is smaller.
RIP NAME/ RT01
BROADCAST INT/ 30
NAME/ RT00
WAN(2)
BROADCAST INT/ 30 LAN(2)
NAME/ RT02
NAME/ RIPP
BROADCAST INT/ 0 TYPE/ ROUT
SUB-TYPE/ RIP
NAME/ RT01
BROADCAST INT/ 0 MEGAPAC n°2
NAME/ RT00 WAN(1)

LAN(1) BROADCAST INT/ 30 NAME/ RT01
RIP
BROADCAST INT/ 30
NAME/ RIPP
TYPE/ ROUT
SUB-TYPE/ RIP NAME/ RT00
LAN(3)
BROADCAST INT/ 30
MEGAPAC n°1
NAME/ RIPP
TYPE/ ROUT
SUB-TYPE/ RIP
E
MEGAPAC n°3
Figure 22-2 Example of a static route (RIP on TCP/IP)
22.1.5 MAC table datagram selection
The Megapac lets you filter TCP or UDP protocol of IP layer datagrams using the MAC table with the
BAR function and the NOT option. (Telnet, FTP, etc. ..)
The filtering can be carried out from the LAN to the WAN and/or from the WAN to the LAN.
The BAR recording SELECTOR field details the resource on which the filtering is carried out. The first
resource of the ROUT descriptor is dedicated to the WAN-to-LAN direction, the resources of the upper
rank are dedicated to the LAN-to-WAN direction.
The BAR function with the NOT option lets you select a particular datagram with specific data specified
in the GENERATOR field for the link connected to the resource specified in the SELECTOR field.
A BAR recording with the NOT option for a specific resource requires a BAR recording with the NONE
option in order to forbid the routing of other datagrams on this resource.

name of BAR NONE name of resource to Protocol,Port number,Ip address
"ROUT" or which filtering applies (hex),(hex),(decimal or hex)
virtual the "wildcard" (hex = hexadecimal and upper-case)
descriptor NOT
character ∗ is allowed When the GENERATOR is not specified
(blank) filtering is total.
"," can be used when one of the fields is not
required.
For the GENERATOR field:
• Protocol (2 digits) Points out the TCP or UDP protocol in hexa upper-case (06 or 11 hexa)
• Port (2 or 4 Points out the port number associated to the service (of the TCP or UDP
number digits) protocol) in hexadecimal and upper-case.
By default, it is the destination port number.
When the letter "S" precedes the port number, it is the source port
number.
• IP address (2 digits Points out the destination IP address in hexa upper-case or dot notation.
multiple)
When the IP machine number is "0", the Netid concerned is filtered.
Details of records:
• The BAR records must be between the IBEG and IEND delimiters.
• When there is an input MAC program (IBEG ... IEND) for this descriptor, the BAR records must
precede the input MAC program.
• BAR record sequences must begin with "BAR, NOT option" followed by "BAR, NONE option".
• When SELECTOR specifies resource "0" of an ROUT descriptor, filtering applies to the datagrams
from the WAN(s) to the LAN.
• When SELECTOR specifies the other resource(s) (other than "0") of an ROUT descriptor, filtering
applies to datagrams from the LAN to the WAN(s).
• When an existing BAR record is edited, the edited information takes effect immediately.
E Page 22-7
E
Examples:
GENERATOR
06 selects TCP
06,17 selects Telnet on TCP
,,128.1.0.0 selects class B network with NetID "128.1"
,,128.1.1.1 selection on machine with IP address 128.1.1.1
11,,128.1.1.1 selects UDP datagrams from the machine with IP address 128.1.1.1
MAC table example:

RIPP BAR NOT RT01 11,,128.1.1.1
RIPP BAR NONE RT01
The datagram coming from the LAN is looking for the destination IP address 128.1.1.1
The router RIP table asks for taking the RT 01 resource for this destination IP address.
The MAC table, for this destination address, allows the routing of the datagram for the UDP protocol
(BAR function with option NOT),
The MAC table for this destination resource forbids any other (BAR function with option NONE).
E Page 22-8
E
TCP
PROTOCOL
List of "PROTOCOLs" and "SERVICES" (TCP/IP)
(decimal)
06
(hex)
06
UDP 17 11
SERVICES Port number for these services

(decimal) (hex)
ECHO 7 07 Echo
DISCARD 9 09 Discard
USERS 11 0B Active Users
DAYTIME 13 0D Daytime
QUOTE 17 11 Quote of the day
FTP-DATA 20 14 File transfer (default)
FTP 21 15 File transfer (control)
TELNET 23 17 Telnet
SMTP 25 19 Simple Mail Transfer
TIME 37 25 Time
NAMASERVER 42 2A Host Name Server
NICNAME 43 2B Who is
DOMAIN 53 35 Domain Name Server
BOOTPS 67 43 Bootp server
BOOTPC 68 44 Bootp client
TFTP 69 45 Trivial File Transfer
FINGER 79 4F Finger
ISO-TSAP 102 66 ISO-TSAP
X400 103 67 X.400
X400-SND 104 68 X.400-SND
SUNRPC 111 6F Sun Remote Procedure Call
NETBIOS - NS 137 89 Netbios Name Service
NETBIOS - DGM 138 8A Netbios Datagram Service
NETBIOS - SSN 139 8B Netbios Session Service
ISO-TPO 146 92 ISO-TPO
ISO_IP 147 93 ISO-IP
SGMP 153 99 SGMP
SNMP 161 A1 SNMP
SNMPTRAP 162 A2 SNMP Trap
CMIP-MANAGE 163 A3 CMIP/ TCP Manager
CMIP-AGENT 164 A4 CMIP/ TCP Agent
AT-RMTP 201 C9 AppleTalk Routing Maintenance
E
AT-NBP 202 CA AppleTalk Name Binding
AT-ECHO 204 CC AppleTalk Echo
AT-ZIS 206 CE AppleTalk Zone Information
E
22.2 "BootP / DHCP relay function
DHCP ("Dynamic Host Configuration Protocol") is a protocol based on UDP/IP, the purpose of which is to
supply configuration data to workstations of a TCP/IP type network.
This data may be:
• the default gateway name,
• the DNS ("Domain Name Server"),
• the sub-network mask,
• etc.
The Megapac provides the "BootP / DHCP relay" function between DHCP client apparatus and a DHCP
server.
To activate the "DHCP relay" function, the MAC table must contain a string of records (DHCP function)
associated with the descriptor that provides the "RIP router" function.
name of IBEG NONE

1 "ROUT" DHCP NONE 1 NbHopMax,NbSecMax
2 virtual DHCP NONE Name1 Name2
3 descriptor DHCP NONE Name3 Name(n)
IEND NONE
The first record with the DHCP function indicates:

SELECTOR 1 = the "DHCP relay" function is active.
0 = the "DHCP relay" function is inactive.
GENERATOR NbHopMax = number of hops (maximum 16) - (4 by default)
NbSecMax = number of seconds x 256 (maximum 32767) - (32767 by default)
These fields are not obligatory.
The following record(s) with the DHCP function indicate:

SELECTOR Name1, Name2, Name3, Name(n), are a list of router resources via which the DHCP
and
frames are sent.
GENERATOR The ∗ character may be used.
E Page 22-10
22.3 "Telnet Server" function from the IP router
This example describes a Megapac in IP router configuration, with one of the IP router resources
allowing access to the "BE00" configuration port.
The RT02 resource of the router uses the service name "TOTO" (NAME+TELR option).
The NAME table includes a TOTO record which indicates:
• routing to a BE00 configuration port,
• Telnet server operation (TELR option),
• use of a specific PAD profile (PROF option).
The "PROFILE" table includes a BE00 code record with the following parameters:
>PROFILE CODE BE00
PAR 1:1, 2:1, 3:2, 4:1, 5:0, 6:0, 7:1, 8:0, 9:0, 10:0, 11:1
12:0, 13:0, 14:0, 15:0, 16:13, 17:13, 18:13, 19:0, 20:0, 21:0, 22:0
When an IP device (Telnet client) connects to the IP address of the RT02 resource, the Megapac
activates a "Telnet Server" session and negotiates the binary mode (WILL Binary - DO Binary), along
with the local echo (DONT Echo - WILL Echo).
Note: The "Telnet Server" service (Reverse Pad Telnet) and the Telnet negotiations options are detailed
in the chapter describing the IP type descriptor.
Table NAME Table MAC
NAME/ TOTO RT02 PU NONE FFFB00FFFD00FFFE01FFFB01

DRC MASK/ BE00
CP/ O
BILLING/ D NAME/ RT02
OPTIONS/ TELR+PROF DRC MASK/ TOTO Table X25
OPTIONS/ NAME+TELR P400 0 12345
NAME/ BE00 BUFFERS/ 40
OPTIONS/ NONE PORT ADDRESS/ "NetId1-HostID(Megapac)"
RP/ 0 SUBNET MASK/ 255.255.255.255
BASE: NAME/ RT01
... DRC MASK/ P400
TERMINAL EMULATION BUFFER/ 1 CIRCUIT TYPE/ CALL
BUFFERS/ 40
PORT ADDRESS/ "NetId2-WAN"
NAME/ ER00 NAME/ RT00

DRC MASK/ .... NAME/ P400
DRC MASK/ RT00 DRC MASK/ ....
BUFFERS/ 40 CIRCUIT TYPE/ CALL
MODE/ NONE PORT ADDRESS/ "NetId1-LAN"

POLL INTERVAL/ 10
ADDRESS/ "NetID1-HostID(Megapac)"
LAN - NetID1 WAN - NetID2
E
Figure 22-3 IP router in Telnet server configuration on the BE00 port
22.4 "Asynchronous PPP access" function with IP address negotiation
The "TYPE/ TERM descriptor" chapter presents the configuration parameters of an asynchronous PPP
protocol link.
To implement IP address negotiation, a router access must be configured.
The example below shows a configuration with a PC having an indefinite IP address (0.0.0.0).
At the time of connection, the PC initializes IP address negotiation with the Megapac.
The PC then receives the IP address: ‘NetID3-HostID(negotiation)".
The BROADCAST ADDRESS/ parameter of the RT02 resource of the ROUT descriptor is used for the
IP address negotiation.
Terminal emulation buffer = 10
NAME/ P500 Table NAME

DRC MASK/ TATA
CIRCUIT TYPE/ CALL+PVC NAME/ TATA
OPTIONS/ NAME DRC MASK/ RT02
BUFFERS/ 40 CP/ 0
SPEDD/ 57.6 BILLING/ D
PAD ENABLE/ D OPTIONS/ PPP
NAME/ PS05
TYPE/ TERM
SUB-TYPE/ SCC
CHANNELS/ 1
NAME/ RT02
DRC MASK/ . . . .
OPTIONS/ NONE
BUFFERS/ 40
PORT ADDRESS/ "NetId3-HostID(port PPP)"
BROADCAST ADDRESS/ "NetID3-HostID(negotiation)"
Asynchronous PPP SUBNET MASK/ "NetID3"
BROADCAST INTERVAL/ 0
NAME/ RT01
@ip 0.0.0.0 DRC MASK/ P400
CIRCUIT TYPE/ CALL
BUFFERS/ 40
PORT ADDRESS/ "NetId2-WAN"
NAME/ ER00 NAME/ RT00

DRC MASK/ .... NAME/ P400
DRC MASK/ RT00 DRC MASK/ ....
BUFFERS/ 40 CIRCUIT TYPE/ CALL
MODE/ NONE PORT ADDRESS/ "NetId1-LAN"

POLL INTERVAL/ 10
LAN - NetID1 WAN - NetID2
Figure 22-4 Asynchronous PPP access with IP address negotiation
E Page 22-12
22.4.1 Logical resource configuration parameters in PPP mode

Name Settings
CALL+STAT
BUFFERS Setting from 1 to 240 Setting determining the number of buffers available to this resource.
By default = 0
PORT ADDRESS in hexadecimal and Defines an IP address for the resource (LAN or WAN side).
upper-case In association with the SUBNET MASK/ parameter, the
or in DOT notation. PORT ADDRESS/ parameter can be used to define a network
address (NetId) for each LAN and WAN connected to this Megapac.
NetID = "PORT ADDRESS" AND "SUBNET MASK"
BROADCAST in hexadecimal and This address is used for IP - PPP address negotiation.
ADDRESS upper-case This address is calculated by the Megapac according to the PORT
This address must be modified for IP - PPP address negotiation.
SUBNET MASK in hexadecimal and Defines a sub-network mask for this port.
upper-case This mask is calculated by the Megapac according to the PORT
This mask must be modified for IP - PPP address negotiation.
BROADCAST 30 The value "0" (no RIP message) must be used for IP - PPP
INTERVAL in seconds address negotiation.
E Page 22-13
22.5 "Router" function in a Netware environment
22.5.1 Virtual descriptor configuration parameters

Name Settings
NAME Up to 4 characters Name of virtual descriptor.
TYPE ROUT Manages a routing protocol (TCP/IP or Netware).
SUB-TYPE IPX Manages the RIP routing protocol in a Novell environment.
CHANNELS 0 to 4096 Number of logical resources associated with the descriptor.
By default = 1 This parameter defines the number of LAN + WAN with which
the Megapac is connected.
The WAN(s) can be X.25, PPP or Frame Relay links.
POLL INTERVAL 0 to 127 The type ROUT descriptor remains passive during this time (in
By default = 30 second), after a Boot, a Restart...
This timer is used to prevent the WANs from connecting (or
disconnecting) themselves to quickly after a system
reinitialization.
ADDRESS 12 characters This address must be the MAC address assigned to the
(in hexadecimal and Ethernet or Token Ring board supporting the link with the LAN.
upper-case) In an RIP-IPX message this address is used for the "source
node" field.
The virtual descriptor of type "ROUT" and sub-type "IPX" recognizes and updates the Netware network
routing information. There are no special parameters other than those of the descriptor and its resources
for standard Novell router operation.
By default, the MAC table is not used. However in a particular environment, the traffic generated by the
RIP and SAP messages of IPX-Novell protocol may become harmful (over low bit rate WAN links, ISDN
links, ...).
In the IPX environment, the Megapac propagates type 20 Netbios frames (Netbios broadcast). So as to
limit the traffic generated by the propagation of these frames, a record in the MAC table can inhibit their
propagation.
For specific applications, parameters of the IPX router function and the associated MAC table recordings
allow to:
• inhibit "Request RIP" and "Request SAP" messages towards the WAN ,
• inhibit "SAP" messages towards the LAN and/or the WAN,
• inhibit "RIP et SAP" messages the LAN and/or the WAN,
• inhibit Netbios broadcast frames (type 20 frames) towards the WAN,
• define RIP and/or SAP static paths
• implement a spoofing function for IPX watchdog messages towards the WAN,
E
• select certain services of the SAP protocol on the LAN and/or the WAN side.

Name Settings
XXXX "CALL" type logical resource.
Name of the logical resource attached to the WAN link descriptor
(example, X.25).
CALL+STAT
CALL The resource name specified by DRC MASK/ is the destination
resource.
IDLE The virtual circuit is cleared if it is no longer transmitting
information during the time predefined by the
INACTIVITY DETECT TIMER/ of the BASE descriptor.
When BROADCAST INTERVAL = 0, no RIP-IPX message is
generated and the link is cleared on inactivity at the end of the
INACTIVITY DETECT TIMER/ delay.
When BROADCAST INTERVAL > 0, an RIP-IPX message is sent
when the connection is set up and the link is cleared on inactivity
when the INACTIVITY DETECT TIMER/ expires.
If the "RIP-IPX" local routing table changes when the link is
released, the Megapac makes a call to transmit the new routing
table ("triggered RIP"). The link is then cleared on inactivity when
the INACTIVITY DETECT TIMER/ expires.
NAME not used with ROUT descriptor
By default = 0
E Page 22-15
E
PORT ADDRESS
8 characters
in hexadecimal and
upper-case
Defines an IPX network address for each LAN and WAN
connected to this Megapac.
This address must be input on eight characters.
or in DOT notation If on a BIND IPX NET server = 5678,
PORT ADDRESS = 00005678
In an RIP-IPX message this address is used for the "source
network" field.
BROADCAST ADDRESS in hexadecimal and In an IPX router environment, this parameter is forced so
upper-case that BROADCAST ADDRESS = PORT ADDRESS and
or in DOT notation. should not normally be changed.
SUBNET MASK in hexadecimal and In an IPX router environment, this parameter is forced to
upper-case FFFFFFFF and should not normally be changed.
or in DOT notation.
BROADCAST INTERVAL 30 BROADCAST INTERVAL ¹ 0 defines the time interval
in seconds between 2 RIP messages towards the concerned resource
(LAN or WAN).
BROADCAST INTERVAL = 0 allows the SAP and RIP
message inhibition towards the concerned resource (LAN or
WAN).
By default, RIP messages are sent towards the concerned
resource (LAN or WAN) every 30 seconds(BROADCAST
INTERVAL value by default).
By default, SAP messages are sent every 30 seconds
towards the LAN and every 20 minutes towards the WAN
(the TIME function in MAC table allows to modify these
values).
E Page 22-16
22.5.3 Example of an "RIP router in a Netware" environment
NAME/ RX01 X25 table

DRC MASK/ P400
BUFFERS/ 40
PORT ADDRESS/ "WAN"
NAME/ ER00 NAME/ RX00 NAME/ P400

DRC MASK/ RX00 DRC MASK/ .... DRC MASK/ ....
PORT ADDRESS/ "LAN"
NAME/ ETHR NAME/ RIPX NAME/ PS04
TYPE/ IPX TYPE/ ROUT TYPE/ X25
NPI/ YES SUB-TYPE/ IPX NPI/ YES
MAC PROTO./ AUTO POLL INTERVAL/ 10
ADDRESS/ "MAC"
MEGAPAC - IPX RIP router
LAN WAN
Figure 22-5 Example of a Megapac as RIP router in an IPX Novell environment
The example shows the configuration of the descriptors and resources of a Megapac as an RIP router in
an IPX Novell environment between an Ethernet LAN and an X.25 link (WAN).
The "VIEW" command lets you analyze the machines present on the LANs.
RIPX: VIEW
Number Channel IPX Address Ticks Hops

1 RX00(0) 0AC80A02 (10.200.10.2) 10 1
2 RX01(1) 0D0A0A01 (13.10.10.1) 10 1
When the LAN-Ethernet cable is disconnected, the "Hop" of the associated resource (RX00 in the
example) jumps to 16, that is "inaccessible network".
E Page 22-17
22.5.4 "Request RIP and Request SAP" message inhibition
When a WAN link is established, the IPX-Novell routing protocol requests the sending of "Request RIP"
and "Request SAP" messages towards remote machines.
The MegaPAC is compliant with this specificity, however, the sending of these messages can be
canceled by a recording in MAC table with the "ROUT" function and the "NOT" option.

RIPX ROUT NOT RX01
Name of the "Request RIP" Name of the nothing
virtual ROUT and resource on the
descriptor "Request SAP" WAN side
message cancellation
22.5.5 "SAP" message inhibition
By default, "SAP" messages are sent every 30 seconds towards the LAN and every 20 minutes towards
the WAN.
The MAC table with the "TIME" function and the "NONE" option allows to modify these timers.
The time interval between 2 SAP messages can be defined in accordance with the needs, either on the
LAN side or on the WAN side, or simultaneously for the LAN and the WAN.
WAN side:

RIPX TIME NONE RX01 time interval between 2 SAP towards the
concerned resource
name of the defines a static path name of the decimal value in second
virtual "ROUT" time interval SAP resource on the 0 = no SAP message
descriptor WAN side
"∗" allowed
LAN side:

RIPX TIME NONE RX00 0 =no SAP message
name of the defines a static path name of the • The value "0" inhibits SAP messages
virtual "ROUT" time interval SAP resource on the towards the LAN side.
descriptor LAN side
• A different value is not significant. In this
"∗" allowed case, 1 SAP message is sent towards the
LAN every 30 seconds, which
E
corresponds to the value by default.
22.5.6 "RIP and/or SAP" static route in MAC table
"RIP" static route

The MAC table with the "ROUT" function and the "NONE" option allows to define a static "RIP" routing
for a resource associated to a WAN.

RIPX ROUT NONE RX01 IPX address,hops,number of ticks
name of defines a RIP name of WAN IPX address, hops and static route transit time
"ROUT" virtual static route static route side resource for the WAN.
descriptor As a rule the "hops" is 1
18 "ticks" = 1 second
"SAP" static route

The MAC table with the "ROUT" function and the "SAP" option allows to define a static "SAP" routing for
a resource associated to a WAN.

RIPX ROUT SAP RX01 Type,SAP-Network,Node,Socket-
4 char. hexa and upper, 8 char. hexa and upper,
Hops,Server-Name
(hexa and upper),(hexa),(text)
name of defines a SAP name of • "," can be used when one of the fields is not
"ROUT" virtual static route static route WAN side required.
descriptor resource • The GENERATOR field can be located on
several recordings with an hyphen "-" at the
end of each recording.
• "@" and "&" transparency characters can be
used.
Type 4 char. (hexa and uppercase)
SAP-Network 8 char. (hexa and uppercase)
Node, 12 char. (hexa and uppercase)
Socket- 4 char. (hexa and upper) and -
Hops 1 or 2 char. (decimal)
Server-Name ASCII string of 1 to 48 char.
For the memory:

"@_" renders transparent the character which follows; here: "_".
"&string&" renders transparent any string of ASCII characters (except &).
E Page 22-19
E
22.5.6.1 Static route example
The example in Figure 22-6 contains three RIP-IPX router Megapacs.

To minimize traffic, Megapac 1 generates no RIP and SAP messages (BROADCAST INTERVAL=0).
Because of this, Megapacs 2 and 3 have no knowledge of Megapac 1.
Megapacs 2 and 3 each have a MAC record defining a static route to Megapac 1.
RIP NAME/ RX01
BROADCAST INT/ 30
NAME/ RX00
WAN(2)
BROADCAST INT/ 30 LAN(2)
NAME/ RX02
NAME/ RIPX
BROADCAST INT/ 0 TYPE/ ROUT
SUB-TYPE/ IPX
NAME/ RX01
BROADCAST INT/ 0 MEGAPAC n°2
NAME/ RX00 WAN(1)

LAN(1) BROADCAST INT/ 30 NAME/ RX01
RIP
BROADCAST INT/ 30
NAME/ RIPX
TYPE/ ROUT
SUB-TYPE/ IPX NAME/ RX00
LAN(3)
BROADCAST INT/ 30
MEGAPAC n°1
NAME/ RIPX
TYPE/ ROUT
SUB-TYPE/ IPX
MEGAPAC n°3
Figure 22-6 Example of a static route (RIP-IPX)
E Page 22-20
22.5.7 "Watchdog IPX" message spoofing
In the IPX-Novell protocol, "watchdog IPX" messages allow a server to supervise the presence of
working stations.
In order to minimize a traffic on a WAN, the MegaPAC provides a spoofing function taking care of
exchanges with the server, while eliminating the traffic which may have been induced on the WAN.
The MAC table with the "TIME" function and the "WIPX" option allows to implement the spoofing function
vis-à-vis a WAN resource.
NB: The WAN link resource must be configured with the IDLE option.

RIPX TIME WIPX RX01 hh:mn,hh:mn
name of the defines a slot during which name of the slot during which the spoofing is implemented.
virtual "ROUT" the spoofing is implemented resource on the start hour:minute, end hour:minute.
descriptor WAN side
when the slot isn’t specified, the spoofing is
"∗" allowed permanent.
Slot Example:
GENERATOR slot
08:30,21:30 no "Watchdog IPX" message on the WAN from 8:30 am until 9:30 pm
23:30,07:15 no "Watchdog IPX" message on the WAN from 11:30 pm until 7:15 am
22.5.8 Inhibition of Netbios broadcast frames
By default, Megapac propagation includes Netbios frames (Packet type 20 decimal).

In order to limit traffic, propagation of messages over a WAN may be deleted by recording in the MAC
table the function "ROUT" and option "NOT".

RIPX ROUT NOT RX01 NETBIOS
name of the suppression of frames name of the Packet type 20 decimal
virtual "ROUT" detailed by the GENERATOR resource on the "NETBIOS Broadcast»
descriptor field WAN side
E Page 22-21
22.5.9 MAC table protocol selection
In a Novell network with several routers, it is important to be able to select certain services of the "SAP"
(Service Advertising Packets) protocol to optimize traffic in the network.
The Megapac lets you filter IPX and SAP (Service Advertising Packets) layer datagrams using the MAC
table with the BAR function and the NOT option.
The BAR function with the NOT option lets you select a particular protocol specified in the GENERATOR
field for the link connected to the resource specified in the SELECTOR field. (The other protocols are
disregarded).
A BAR recording with a NOT option for a specific resource requires a BAR recording with a NONE option
in order to forbid the routing of other services on this resource.

name of BAR NONE name of resource to SAP-Network,Type,Server-Name
"ROUT" or which filtering applies (8 char., 4 char., 1 to 18 characters)
virtual the "wildcard" (hex and uppercase),(hex),(text)
descriptor NOT
character ∗ is allowed When the GENERATOR is not specified
(blank) filtering is total.
"," can be used when one of the fields is not
required.
Examples:
GENERATOR
FFFC selects all the services of server "FFFC".
FFFC,0007 selects the print service of server "FFFC".
,0007 selects all print services.
,0007,GEO selects all print services of servers with a name beginning with GEO.
,,GEO selects all services of servers with a name beginning with GEO.
Details of records:
• The BAR records must be between the IBEG and IEND delimiters.
• When there is an input MAC program (IBEG ... IEND) for this descriptor, the BAR records must
precede the input MAC program.
• BAR record sequences must begin with "BAR, NOT option" followed by "BAR, NONE option".
• When SELECTOR specifies resource "0" of an ROUT descriptor, filtering applies to the datagrams
from the WAN(s) to the LAN.
• When SELECTOR specifies the other resource(s) (other than "0"), filtering applies to datagrams from
the LAN to the WAN(s).
• When an existing BAR record is edited, the edited information takes effect immediately.
E Page 22-22
E
List of Netware services
Type
0001
Description
User
0002 User group

0003 Print queue
0004 File server
0005 Job server
0007 Print server
0021 NAS SNA Gateway
0023 NACS
0027 TCP/IP Gateway
0053 Print queue user
0098 Netware access server
0107 Netware 386
0137 Netware 386 print queue
E Page 22-23
E Page 22-24
23. TYPE/ SNMP descriptor
23.1 General
The TYPE/ SNMP descriptor enables the Megapac to offer the "SNMP agent" function, and if requested,
it can generate TRAPs towards an SNMP manager. The SNMP descriptor also acts as a TFTP customer;
this function allows the downloading of an other software originating from the MegaPAC memory.
The SNMP manager used must include the MIB (Management Information Database) adapted to the
MegaPAC software used.
The TYPE/ SNMP descriptor is a virtual descriptor, the resource must be linked with:
• either with the first resource of an IP or TIP descriptor
• or with a resource of a ROUT descriptor acting as a router.
• or with a WAN resource, when the Megapac is not connected locally to a LAN.
In a Megapac, only one SNMP descriptor is allowed.
The SNMP descriptor also acts as a server for the TFTP protocol (Trivial FTP).
Thus, it is possible to download a software version in the MegaPAC central unit.
In this case, the "TELELOAD ENABLED/" parameter under base must allow the downloading.
The TFTP command must be used under the "image" mode (binary transfer).
23.2 SNMP Management
The Megapac handles three tables that make up the "Group IP" of the standard MIB.
1. IpAddrTable IP address of each IP router input
2. IpRouteTable router RIP routing table
3. IpNetToMedia table mapping IP addresses to MAC addresses (ARP table)
The Megapac-Megabox ARP table is limited to:

• 1024 inputs for Megapac/Megabox with CPU-E or CPU-V boards installed,
• 2048 inputs for Megapac with CPU-40 or CPU-60 boards installed.
When the SNMP manager asks for the ARP table (IpNetToMedia), the number of inputs sent is limited to
E
100 for a CPU-E board with no memory extension.
TYPE/ SNMP descriptor Page 23-1
23.3 Virtual descriptor configuration parameters

Name Settings
NAME Up to 4 characters Name of the virtual descriptor.
TYPE SNMP Specifies the "SNMP agent" function.
CHANNELS 0 to 4096 Number of resources associated with the descriptor.
By default = 1 (One resource for SNMP agent).
POLL INTERVAL 0 à 127 The SNMP descriptor remains passive during this time
By default = 30 (in second) after a Boot, a Restart...
23.4 Resource configuration parameters

Name Settings
NAME 4 characters Name of the "SNMP" agent resource.
DRC MASK 4 characters Fully or partly identifies a destination resource used for
By default = . . . . linking.
XXXX "CALL+PVC" type logical resource.
Name of the IP resource dedicated to the SNMP agent.
CALL+STAT
CALL+PVC This resource is linked with that defined by DRC MASK/.
OUT+PVC This resource is a destination resource of another
Megapac resource.
OPTIONS NONE By default
NAME, IDLE not used
SNMP, TELR not used
BUFFERS 1 to 240 Setting determining the number of buffers available to
By default = 2 this resource.
CALL PRIORITY 0 to 15 Not used.
By default = 0
RESOURCE PRIORITY 0 to 15 Not used.
By default = 0
TYPE/ SNMP descriptor
E Page 23-2
E
23.5 MAC table
The MAC table allows to describe certain information concerning the MegaPAC.
These information expand the MIB and are thus available from the SNMP manager.
The table below specifies the order in which the information can be entered.

name of SNMP DATA NONE Identifies the network manager.
descriptor
name of SNMP DATA NONE Administrative name of Megapac
descriptor node.
name of SNMP DATA NONE Geographic location of site.
descriptor
name of SNMP DATA NONE Name of a link Information on the link(s).
descriptor descriptor
∗ is allowed.
name of SNMP DATA NONE Name of a link Information on the link(s).
descriptor descriptor
∗ is allowed.
etc. etc. etc. etc. etc.
The GENERATOR field can be extended to the next record using the "-" character at the end of the
GENERATOR field.
"DATA" records of the SNMP descriptor require no IBEG ... IEND delimiters.
23.5.1 SNMP resource associated to the first IP/TIP resource
In this case, the MAC table is used to define the IP address of the SNMP agent.
The datagrams corresponding to this address are routed towards the IP resource bound to the SNMP
descriptor resource.
E Page 23-3
23.6 "SNMP agent" function, with IP resource
NAME/ SNM1 NAME/ IP01

DRC MASK/ .... DRC MASK/ SNM1
CIRCUIT TYPE/ PVC+OUT CIRCUIT TYPE/ CALL
O¨TIONS/ NONE BUFFERS/ 40
BUFFERS/ 40 MODE/ NONE
NAME/ ETHS
NAME/ ETHE
TYPE/ SNMP
TYPE/ IP
CHANNELS/ 1
NPI/ YES
POLL INTERVAL/ 10
CHANNELS/ 1
Megapac - "SNMP Agent"
LAN
Figure 23-1 Megapac in SNMP Agent mode
The example above specifies the significant parameters of an "SNMP agent" function on a TCP/IP
Ethernet network. The IP address 11.11.11.11 is assigned to the SNMP agent.
MAC table

ETHS DATA NONE Mr NMC3000
ETHS DATA NONE Multiprotocol Megapac
ETHS DATA NONE 25 quai Panhard and Levassord
ETHS DATA NONE PS03 Lannion
ETHS DATA NONE PS04 Bayonne
ETHE IBEG NONE
ETHE IEND NONE
This combination, SNMP resource, IP or TIP resource:

• requires an input MAC program to define the IP address of the SNMP agent,
• answers to the PING function of the TCP/IP protocol,
E
• provides the SNMP agent function (without generating any TRAP),
• provides the "software downloading" by using the TFTP function of the TCP/IP protocol.
23.7 "SNMP agent + trap management" function, with IP resource
The resource combination is identical to the previous case.

The IP address 11.11.11.11 is allocated to the SNMP agent, that is the Megapac.
The IP address 11.01.01.01 is allotted to the SNMP manager, that is the one receiving the SNMP traps.
A "ROUT" recording for the SNMP descriptor can be necessary in MAC table, the GENERATOR field
details:
GENERATOR
"source IP address","destination IP address","community name"
"Megapac source IP address","Management system IP address","public"
This recording isn’t necessary when the SNMP manager initializes the dialogue with the Megapac.
MAC table example

ETHS ROUT NONE 0B0B0B0B,0B010101,public
ETHS DATA NONE Mr NMC3000
ETHS DATA NONE Megapac multiprotocols
ETHS DATA NONE 25 quai Panhard et Levassord
ETHS DATA NONE PS03 Lannion
ETHS DATA NONE PS04 Bayonne
ETHE IBEG NONE
ETHE IEND NONE
This combination, SNMP resource, IP or TIP resource:

• requires an input MAC program to define:
• the IP address of the SNMP agent (0B0B0B0B),
• the IP address of the SNMP manager (0B010101),
• answers to the PING function of the TCP/IP protocol,
• provides the SNMP agent function and generates the TRAP SNMP,
• provides the "software downloading" by using the TFTP function of the TCP/IP protocol, in this case,
only the SNMP manager can carry out a downloading through TFTP.
E Page 23-5
23.7.1 TCP/IP RIP Router with SNMP agent
NAME/ RT03
NAME/ SNM1 DRC MASK/ SNM1 Megapac 1
DRC MASK/ .... CIRCUIT TYPE/ CALL
CIRCUIT TYPE/ OUT+PVC OPTIONS/ SNMP
PORT ADDRESS/ "NetID1-HostID(Megapac)"
NAME/ ETHS SUBNET MASK/ 255.255.255.255
BROADCAST INTERVAL/ 0
TYPE/ SNMP
CHANNELS/ 1 NAME/ RT02 Table X25
POLL INTERVAL/ 20 DRC MASK/ P400
BUFFERS/ 40
PORT ADDRESS/ "NetID2-WAN"
NAME/ IP01 NAME/ RT01 NAME/ P400
MODE/ NONE PORT ADDRESS/ "NetID1-LAN"
POLL INTERVAL/ 10
LAN-NetID1
WAN
NetID2
NAME/ RT03
NAME/ SNM1 DRC MASK/ SNM1 Megapac 2
DRC MASK/ .... CIRCUIT TYPE/ CALL
CIRCUIT TYPE/ OUT+PVC OPTIONS/ SNMP
PORT ADDRESS/ "NetID3-HostID(Megapac)"
NAME/ ETHS SUBNET MASK / 255.255.255.255
TYPE/ SNMP BROADCAST INTERVAL/ 0
Table X25
CHANNELS/ 1 NAME/ RT02
POLL INTERVAL/ 20 DRC MASK/ .... RT02 0 12345
BUFFERS/ 40
PORT ADDRESS/ "NetID2-WAN"
NAME/ IP01 NAME/ RT01 NAME/ P400

MODE/ NONE PORT ADDRESS/ "NetID3-LAN"
NAME/ RIPP NAME/ PS04
NAME/ ETHR
TYPE/ ROUT TYPE/ X25
TYPE/ IP
SUB-TYPE/ RIP NPI/ YES
NPI/ YES
CHANNELS/ 3
CHANNELS/ 1
POLL INTERVAL/ 10
LAN - NetID3
Figure 23-2 Megapac TCP/IP RIP router and SNMP management
E Page 23-6
The previous example details the major parameters of a "Router RIP" function with "SNMP agent" on a
TCP/IP network on Ethernet.
The "SNMP" descriptor resource must be associated with a "ROUT" descriptor resource with the SNMP
option. The "ROUT" descriptor resource (here RT03) must include the same NetID1-HostID(Megapac)
address as the ROUT descriptor. The SUBNET MASK must be at 255.255.255.255 and the
BROADCAST INTERVAL parameter at "0".
Likewise, the NetID3-HostID(Megapac) address of the Megapac 2 is the same for the ROUT descriptor
and the RT03 resource.
A LAN1 device can download software to the Megapac 1 with the NetID1-HostID(Megapac) address, or
to the Megapac 2 with the NetID3-HostID(Megapac) address, with the same applying to a LAN2 device.
This resource combination (SNMP , IP or TIP, ROUT):

• answers to the PING function, [address NetID1-HostID(Megapac) or NetID3-HostID(Megapac)],
• provides the SNMP agent function,
• provides the "software downloading" by using the TFTP function of the TCP/IP protocol,
• provides the TCP/IP Router function, with the RIP protocol.
23.7.1.1 TRAP SNMP management in "RIP" router
If one wishes the MegaPAC to generate SNMP TRAPs in an operating, it may be necessary to add a
ROUT recording in the MAC table. The GENERATOR field details:
GENERATOR
"source IP address","destination IP address","community name"
"Megapac source IP address","Management system IP address","public"
This recording isn’t necessary when the SNMP manager initializes the dialogue with the Megapac.
Example:
Supposing the LAN1 network is a class B network in 135.21.xx.xx
The Megapac 1 receives the IP address 135.21.20.20 (87151414 in hexa).
The SNMP manager receives the IP address 135.21.64.64 (87154040 in hexa).
For the MegaPAC 1, the addresses are as follows:

• for the ROUT descriptor, the ADDRESS/ field is 135.21.20.20
• for the RT01 resource, the ADDRESS/ field can be also 135.21.20.20
• for the RT03 resource, the ADDRESS/ field is 135.21.20.20 and the SUBNET/ field is
255.255.255.255
• in MAC table, the ROUT recording includes:
E
ETHS ROUT NONE 87151414,87154040,public
23.8 "Agent SNMP + Trap SNMP" function with WAN resource
When the Megapac is used without attachment to a local network (e.g. in "switch" mode), it can be
configured with an SNMP agent and thus integrated in a network using this supervision protocol.
In the example,
IP address 11.11.11.11 is allocated to the SNMP agent, i.e. the Megapac.
IP address 11.01.01.01 is allocated to the SNMP manager, i.e. that which receives the SNMP traps.
Table MAC
TRAP ROUT NONE 0B0B0B0B,0B010101,public
NAME/ SNM1
DRC MASK/ . . . .
BUFFERS/ 40
NAME/ TRAP NAME/ P400

TYPE/ SNMP DRC MASK/ SNM1
CHANNELS/ 1 PROTOCOL/ IP
CIRCUIT TYPE/ CALL
POLL INTERVAL/ 20
BUFFERS/ 40
NAME/ PS04
TYPE/ NFRM
SUB TYPE/ XIO WAN
NPI/ YES IP / Frame Relay
ADDRESS/ DLCI(a)
Megapac MODE/ ...
Figure 23-3 SNMP agent on a node without a LAN attachment
E Page 23-8
24. TYPE/ MULT descriptor
"MULT" is an application object providing for multiple associations.

The "MULT" descriptor is for connecting one resource to several other resources.
In a "MULT" descriptor, a call on the master resource (resource 0) is broadcast to one, some or all the
other resources of the "MULT" (resources 1 to n).
In the other direction, data from the connected resources numbered 1 to n is concentrated onto the
master resource but not broadcast to the other resources.
All the resources of a "MULT" descriptor can be designated as called or calling.
The master resource is the first resource of the "MULT" descriptor.
connection (Megapac routing) channel 1

established on (Megapac routing) channel 2 Channel 0 (Megapac routing)
each channel (Megapac routing) channel 3
24.1 Multipoint link application
An "MULT" descriptor is used to implement a multipoint connection on a link.

The server must be connected to logical resource number 0.
In the Server → Terminals" transfer phase, data is broadcast from logical resource 0 to the various
"destination" logical resources.
CALL PRIORITY and RESOURCE PRIORITY values are set respectively on logical resource 0 and the
"destination" logical resources to enable implementation of an alternate routing.
In the "Terminals → Server" transfer phase, data is concentrated from the various logical resources to
the "destination" logical resource (0).
CALL PRIORITY and RESOURCE PRIORITY values are set respectively on the logical resources
numbered > 0 and logical resource n° 0, allowing for the implementation of an alternate routing.
Notes
• Flow control is applied in both directions between logical resource n° 0 and logical resources
numbered > 0.
• In the absence of flow control on a logical resource, the content of the most recent buffers is saved at
the cost of the content of the older buffers.
TYPE/ MULT descriptor
E Page 24-1

Name Settings
NAME Up to 4 characters Link name.
TYPE MULT Operation using the virtual multiplexer.
CHANNELS 0 to 4096 Number of "resources".
By default = 2
Specify 3 or more
FLOW CONTROL By default = NO No flow control.
YES Flow control.
PACKET SIZE By default = TRAN Packet size, from 32 to 4096 bytes.
See also the PUSH option of the "resources".
POLL INTERVAL 1 to 127 Timer between an incoming call from the master
By default = 30 resource and the setting up of an outgoing call from the
slave resources (1 to n).
24.3 Logical resource parameters

Name Settings
NAME Up to 4 characters Name of the resource. Used for internal routing.
Resource 0 must have a unique name and must not be
configured with a hunt group name.
DRC MASK By default = .... Defines the name of the destination resource for calls
sent by that resource.
CIRCUIT TYPE CALL+PVC Default setting.
CALL The resource can send or receive calls.
PVC The resource sends the call when data is present.
SVC If resource "0" is free, it initiates the call (every five
seconds, in the event of failure).
The DRC MASK must be specified.
If a call is routed on resource "0", a call sent by this
resource is cleared.
OUT The resource can only accept incoming calls. It cannot
send calls.
STAT For any call connection or disconnection, the resource
generates statistical information (to resource EI01, by
default).
BUFFERS 1 to 240 Number of buffers required for queuing received data.
E
By default = 2 10 buffers are required for a MULT resource.
TYPE/ MULT descriptor Page 24-2
E
MODE
SAT
LSTN
By default = NONE By default, data is routed transparently.

Does not apply to a MULT descriptor.
If the call on resource "0" was sent by that resource,
resources (1 to n) cannot keep calls.
If the call on resource "0" was received by that
resource, resources (1 to n) can receive or send calls.
WAIT Does not apply to a MULT descriptor.
DATA Reserved use.
RESP Reserved use.
SYM see LSTN
AUTO If AUTO is specified on resource 0 (CIRCUIT TYPE/
CALL), that resource can initiate a call only if at least one
of resources 1 to n is connected. If none of the resources
is connected, resource 0 clears its call.
If AUTO is specified on resources 1 to n, these can
initiate a call only if resource 0 is connected.
PATH Enables selective broadcasting.
A data packet received by resource "0" is not sent over
the slave resources "1 to n" unless the first four
characters of the packet contain the name of the slave
resource.
PUSH When this parameter is used, the name of the slave
resource is inserted at the start of the data before being
transmitted to resource 0.
The transmitted packet size is then increased by four.
If the resource is connected to a PAD, the PACKET SIZE
parameter defines the PAD buffer size as N-4 characters
(the four characters of the name of the resource).
PULL The first four characters of a data packet are deleted
before the packet is sent by the slave resource (the
packet was previously received on resource "0").
STOP Do not use in broadcast mode.
With this parameter, the call from the master resource is
routed over the first resource which has the required DRC
MASK, or goes on to the next if the first is unavailable.
By default = 0
By default = 0
E Page 24-3
E
24.4 "MULT" operating modes
MODE Operation
ABCDE Channel 1
PUSH
MUL1
Channel 2 Channel 0 MUL1ABCDE

PUSH MUL2 MULT MUL0
Channel 3
MUL3
Channel 1 ABCDE
MUL1 PULL
MULXABCDE
PULL
MULXABCDE Channel 0
MUL0
MULT Channel 2
MUL2
Channel 3 ABCDE
PULL
MUL3
Channel 1
MUL1
MUL2ABCDE
PATH
MUL2ABCDE Channel 0
MUL0
MULT Channel 2
MUL2
PATH
Channel 3
MUL3
E Page 24-4
25. TYPE/ V25B descriptor
25.1 General
The V25B descriptor is a virtual descriptor.

• It is used to manage the establishment at output and input of a synchronous or asynchronous link
over the telephone network using the V.25bis protocol.
• It provides a "monitor" function for a backup link.
In a Megapac, there should be only one V25B descriptor, with a number of resources if necessary.
25.2 Exploitation in V.25bis protocol
The following protocols are supported: TERM-ASYN, HDLC, X.25, PPP.
A V25B descriptor resource is associated,

• with a resource of a link (HDLC, X.25, etc.) with the Extended Call Management ECM parameter set
to V25B, or
• with a resource of a TERM link having the parameter CIRCUIT TYPE = SVC+V25B.
The telephone number element of the V.25 bis call command (prefix CRN) is generated using the output
MAC program (DATA, CAD, DAD, CUD record).
The V.25 bis link virtual descriptor also handles the V.25 bis incoming call indication (prefix INC) from
the PSTN, ISDN, etc.
A V.25 bis destination logical resource or one or more V.25 bis hunt groups can be specified.
The V25B descriptor is used to monitor for each call:

• call duration,
• the time after which the call will be released, if there is no traffic.
For this a record is needed in the MAC table with the "TIME" function.
TYPE/ V25B descriptor
E Page 25-1
25.2.1 Typical configuration in backup mode "V.25bis"
A typical application is backup of an X.25 link via the PSTN, ISDN, etc.
For example, the Megapac is configured with the main X.25 link and a backup X.25 link, the backup
being connected to a modem via the PSTN. The backup link is declared by a "descriptor", for example
PS04 and has "resources" P400.
To be able to handle the call on the PSTN, the Megapac must be configured with a V.25 bis descriptor,
for example:
V.25 bis descriptor: NAME/ DIAL
TYPE/ V25B
CHANNELS/ 1
This "descriptor" must have a resource of the same name as the backup link's resources.
In addition, the DRC of the V25B resource must have the name of the backup link "descriptor".
V.25 bis resource: NAME/ P40*
DRC MASK/ PS04
CIRCUIT TYPE/ OUT+SVC+STAT
BUFFERS/ 2
MODE/ NONE
CALL PRIORITY/ 0
Principle:
When a call is offered, it is routed over a resource of the main link (highest RP and LG).
If the main link is out of service, the call is routed over a resource of the same name but with a lower RP
(in other words, the backup link).
Because the "descriptor" of the backup link is set to ECM = V25B:
• setting up of the X.25 call is delayed,
• the V25B "resource" is polled,
• the MAC table is read in output mode (OBEG), to find the number to be sent in the V.25 bis
procedure,
• CRN, VAL and number are exchanged.
When the connection is set up, establishment of the X.25 level 2 follow after which the initial X.25 call
can be routed.
E Page 25-2
E X.25
call 789 and CP=1
PS03 - X25 - LG=2

P400 - RP=1
Main link
Main link
PS04 - X25 - LG=1 - ECM=V25B to dial up modem

P400 - RP=0
Backup link
DIAL - V25B
NAME/ P40*
DRC/ PS04
TYPE/ OUT+SVC
CP/ 0
RP/ 0
X.25 table
Name Address group Address User Data

P400 0 789T
MAC table

DIAL OBEG NONE
DIAL DATA NONE P400 44567732
DIAL OEND NONE
The "VIEW" command on a V25B descriptor can be used to view current calls set up in V.25 Bis mode.
DIAL: VIEW
Channel LINK NAME ASSIGNED NAME ADDRESS
P40∗(0) PS04 P400 44567732 →
The "REST" command on a V25B descriptor can be used to clear manually all active calls set up in
V.25 Bis mode.
E Page 25-3
E
Additional configuration information
Main link:
• The configuration is standard, but special attention is needed for the RP, CP and LG parameters.
Backup link:
• The configuration is standard, but attention is needed for the RP, CP and LG parameters.
• The backup link must have the parameter ECM = V25B.
• In X.25 mode, it must have at least two "resources", with the first used by the V.25 bis dialing phase.
• On the XIO board, in X.25 mode, the UI option (unnumbered information frame) will be specified.
V25B descriptor:
• It is important to declare as many "resources" as there are links using the V.25 bis protocol.
V25B resources:
• NAME/ the name of the "resources" of the link using the V.25 bis protocol
• DRC/ the name of the "descriptor" of the link using the V.25 bis protocol
• TYPE/ OUT+SVC
• BUFFERS/ as for the link using the V.25 bis protocol
• MODE/ NONE
• Call Priority/ 0
• Resource Priority/ lowest
X.25 table:
• The configuration is standard, but with the indicator "T" to reconstruct the X.25 call request packet.
MAC table:
• The MEGAPAC stores the content of the SELECTOR field (destination logical resource name) of the
output MAC record (CAD, DAD, CUD or DATA) that generated the telephone number associated with
the V.25 bis call request command (CRN).
• This means it is possible to provide successive backup of different X25 links on a single backup X.25
link.
• NAME/ NAME of the V25B "descriptor"
• FUNCTION/
• OBEG start of an output MAC record
• TIME specifies check on call duration.
• DATA the "generator" field contains the number to be sent
• CAD the number to be sent is constructed from the calling line address
• DAD the number to be sent is constructed from the called line address
• CUD the number to be sent is constructed from the calling line user data
• NOP no operation
• OEND end of an output MAC record
• OPTIONS/ NONE (or DISC)
• SELECTOR/ The NAME of the V25B resource ( * is allowed).
• GENERATOR/
• with DATA, specifies the number to be sent; all characters can be used. In case of conflict
with the Megapac control characters, use the control character "@".
• with CAD the skip and copy functions (#) and ( ) can be used.
• with DAD the skip and copy functions (#) and ( ) can be used.
• with CUD the skip and copy functions (#) and ( ) can be used.
E Page 25-4
25.3 Managing several V25B numbers for a single directory number
When the backup link in V.25 Bis mode can be set up from several numbers (V25B), it is important to
use the input MAC table to define a list of destination resources.
The MAC table associated with the V.25 Bis descriptor then includes as many "DATA" records as there
are different V25B numbers.
Typical configuration
PS01 - X.25 PS03 - X25 - LG=2 Main link

call 123 and CP=1 P40∗ - RP=1
(input link with ECM=IN) Main link
PS04 - X25 - LG=1 - ECM=V25B to PSTN modem

P40∗ - RP=0
Backup link
DIAL - V25B
NAME/ P40∗
DRC/ PS04
TYPE/ OUT+SVC
MODE/ WAIT
CP/ 0
RP/ 0
MAC table

^LS1 LIST NONE P401
^LS1 ELSE NONE P402
^LS1 ELSE NONE P403
PS01 IBEG NONE
PS01 DAD NONE 123 ^LS1
PS01 IEND NONE
DIAL OBEG NONE
DIAL OEND NONE
The routing procedure is as follows:

• Input link PS01 is ECM=IN. For the called number "123" the input MAC table refers to list LS1. Routing uses in
turn resources P401 then, in the event of failure, P402, then P403.
• A resource P40* of link PS03 is selected first (RP=CP=1).
• If this fails, a resource P40* of V.25 Bis link PS04 is selected.
• Depending on the name of the resource requested (P401, P402, P403), the MAC table indicates the V.25 Bis
number to be sent:
• For the first routing, resource P401, the number is 44567732.
• For the second routing, resource P402, the number is 44778899.
E
• For the last routing, resource P403, the number is 44771234.
TYPE/ V25B descriptor Page 25-5
25.4 Managing several destinations for the same link
When the backup link in V.25 Bis mode is used to connect different sites, it is important to use the X.25
table to differentiate the destination resources.
The MAC table associated with the V.25 Bis descriptor then includes as many "DATA" records as there
are different sites.
Typical configuration
X25 PS03 - X25 - LG=2 Main link

call 789 or 123, and CP=1 P40∗ - RP=1
Main link

P40∗ - RP=0
Backup link
DIAL - V25B
NAME/ P40∗
DRC/ PS04
TYPE/ OUT+SVC
MODE/ NONE
CP/ 0
RP/ 0
X.25 table

P401 0 789T
P402 0 123T
MAC table

DIAL OBEG NONE
DIAL OEND NONE

• For the called number "789", resource P401 is the destination resource.
• For called number "123", resource P402 is the destination resource.
• A resource P40* of link PS03 is selected first (RP=CP=1).
• If this fails, a resource P40* of V.25 Bis link PS04 is selected.
• Depending on the name of the resource requested (P401 or P402), the MAC table indicates the
V.25 Bis number to be sent:
• For the called number "789", resource P401, the number is 44567732.
E
• For called number "123", resource P402, the number is 44778899.
E
25.5 V25 bis Hunt group
A group of backup links operating in V.25 Bis protocol mode can be formed by associating a resource of
the V25B type descriptor to each of the backup links.
The resources of the V25B descriptor must then be set up as follows:
• The first link associated with the first backup link should be clearly identified (NAME/ XXXX).
• The subsequent resources associated with the other backup links of the group are all programmed
with NAME/ " " " " (four double quotes).
• Each resource has a different DRC MASK/ which identifies the different backup links (different
modems), but all these links call the same number.
In the event of failure:

• the V.25 bis logical resource becomes BUSY (unavailable),
• the logical resource (receiving the incoming call) becomes ROUT (hunting for the remote resource),
• a connection attempt is made on each V.25 bis logical resource in turn (NAME/"""") remaining in the
group.
• If the connection cannot be set up, conventional routing can be used, and, in particular, the ELSE
record of the input MAC program.
E Page 25-7
E
25.5.1 Typical group
X25 PS03 - X25 - LG=2 Main link

call 789, and CP=1 P400 - RP=1
Main link

P400 - RP=0
Backup link N°1

P400 - RP=0
Backup link N°2
DIAL - V25B
NAME/ P40*
DRC/ PS04
TYPE/ OUT+SVC
MODE/ NONE
CP/ 0
RP/ 0
NAME/ """"
DRC/ PS05
TYPE/ OUT+SVC
MODE/ NONE
CP/ 0
RP/ 0
X.25 table

P400 0 789T
MAC table

DIAL OBEG NONE
DIAL OEND NONE

• For the called number "789", resource P400 is the destination resource.
• Resource P400 of link PS03 is selected first (RP=CP=1).
• In the event of failure, resource P400 of V.25 Bis link PS04 is selected
(1st resource of the descriptor DIAL - V25B).
• In the event of failure, resource P400 of V.25 Bis link PS05 is selected
(2nd resource of the descriptor DIAL - V25B).
The number in V.25 Bis mode is the same for links PS04 and PS05 (44567732).
E Page 25-8
25.6 "Monitor" mode for a backup link with V.25 bis protocol
In this mode, the backup link uses the V.25 bis protocol.
When the main link is disconnected, the backup link is used. The "monitor" function is used to switch
over from the "backup link" to the "main link" when the main link becomes operational again.
For this function:

• The main link is set as follows:
• it has the name NAME/xxxx,
• its LINE GROUP/ is greater than the backup link.
• The backup link is set as follows:
• it is named NAME/xxx$,
• its LINE GROUP/ is at least equal to 1,
• EXTENDED CALL MANAGEMENT = V25B.
• The first three characters of the main and backup link names are the same.
• The NAME/ parameters of the resources of the two links are the same.
• A resource of a V25B type descriptor is assigned to the backup link to:
• dial according to the V.25 bis protocol,
• handle the monitoring function.
• The first resource of the backup link is used for the V.25 bis dialing phase.
The "monitor" mode is selective.

The backup link using the V.25 bis protocol can handle two types of traffic:
• virtual circuits set up as backups of peer virtual circuits existing first on a higher "LINE GROUP/"
main link.
• source virtual circuits, set up on the backup V.25 bis link which should therefore be kept as they are.
The procedure on which this selection is based is explained below:

• The link on which the virtual circuits will be re-established should have a LINE GROUP value higher
than the one associated with the LINE GROUP parameter of the backup V.25 bis link.
• When this higher priority link is restarted, the software checks to see whether the name of logical
resource N° 1 matches one or more of the logical resource names of the backup V.25 bis link.
• If it does, the virtual circuit or circuits concerned are cleared.
Clearing options:
When the backup link is initialized outgoing, the "DISC" option in a DATA record of the MAC table can
be used to clear the call set up on a backup link, when the main link becomes operational again. This
option should be used with the monitoring function.
When the backup link is initialized incoming, the "DISC" option in a NDI record of the MAC table is used
to clear calls set up on a backup link when the main link becomes operational again. This option should
be used with the monitoring function.
E Page 25-9
25.7 "Monitor" mode on a backup link without V.25 bis protocol
In this mode, the backup link does not use the V.25 bis protocol.
When the main link is disconnected, the backup link is used. The "monitor" function is used to switch
over from the "backup link" to the "main link" when the main link becomes operational again.
For this function:

• The main link is set as follows:
• it has the name NAME/xxxx,
• its LINE GROUP/ is greater than the backup link.
• The backup link is set as follows:
• it is named NAME/xxx$,
• its LINE GROUP/ is at least equal to 1,
• EXTENDED CALL MANAGEMENT = V25M.
• The NAME/ parameters of the resources of the two links are the same.
• A resource of a V25B type descriptor is assigned to the backup link to handle the monitoring function.
The "monitor" mode is selective.

The backup link can handle two types of traffic:
• virtual circuits set up as backups of peer virtual circuits existing first on a higher "LINE GROUP/"
main link.
• source virtual circuits, set up on the backup link which should therefore be kept as they are.
The procedure on which this selection is based is explained below:

• The link on which the virtual circuits will be re-established should have a LINE GROUP value higher
than the one associated with the LINE GROUP parameter of the backup V.25 bis link.
• When this higher priority link is restarted, the software checks to see whether the name of logical
resource N° 1 matches one or more of the logical resource names of the backup V.25 bis link.
• If it does, the virtual circuit or circuits concerned are cleared.
Clearing options:
The "PULL" mode can be used to clear all calls set up on a backup link without V.25 bis protocol, when
the main link (with ECM=V25M) becomes operational again. This option should be used with the
monitoring function.
Notes:
• No link is set up between logical resource number 0 (link descriptor) and a logical resource of the
V25B descriptor when the backup link is in "V25M monitor" mode.
E Page 25-10
25.7.1 Typical monitoring configuration (without V.25 bis protocol)
X25 LA30 - X25 - LG=2 Main X.25 link

call 789, and CP=1 L300 - RP=1
Main link
LA3$ - X25 - LG=1 - ECM=V25M Backup X.25 link

L30∗ - RP=1
Backup link
DIAL - V25B
NAME/ L30∗
DRC/ LA3$
TYPE/ OUT+SVC
MODE/ NONE
CP/ 0
RP/ 0
X.25 table

L300 0 789

• For the called number "789", resource L300 (RP=1) is the destination resource.
• Resource L300 for link LA30 is selected first (LG=2).
• In the event of failure, a resource L30* of link LA3$ is selected (LG=1). The Megapac stores the fact
that the resource replaces a resource "L300".
• When the main link becomes operational again (Restart on LA30).
• The VC open on link LA3$ which are normally routed over a resource L300 are disconnected.
• Link LA3$ is cleared when there are no more VC active.
Subsequent calls to subscriber "789" will be routed over a resource L300 of main link LA30.
E Page 25-11
E
25.8 Review of CP and RP rules
Following a failure to set up a connection (to a logical resource or a V.25 bis hunt group), the CALL
PRIORITY/ setting of the calling logical resource is decremented automatically by 1.
The following situations can then apply:
• if the resulting CALL PRIORITY/ setting is > 0, the system tries again to set up a connection with a
resource (V.25 bis or other) which has a compatible RESOURCE PRIORITY/ setting,
• if the resulting CALL PRIORITY/ setting is 0, the calling logical resource assumes the DISC state
(virtual circuit cleared).
• Conventional routing can then be used and, in particular, the ELSE record of the input MAC program.
E Page 25-12
25.9 ISDN calling line identification function
This function is available on links which accept V25 Bis mode.

The ISDN calling line identification function can be used on a Megapac with one of the following ISDN
connection cards: ISA, GIS, PRI-64.
☛ This function is required when using the resources of an X.25 link previously set up by an
incoming V.25 Bis call for outgoing purposes.
This function can also be used on any adapter providing the ISDN number on the V.25 Bis indication
"INC".
25.9.1 Description
On an incoming ISDN call, the ISDN connection board sends the Megapac an indication "INC" followed
by the ISDN number. The Megapac uses this indication to identify incoming ISDN calls.
The Megapac configuration must support the V.25 Bis protocol on the link on which the ISDN connection
board is connected. The MAC table associated with the X.25 link must contain a record with the "NDI"
identification function.
25.9.2 ISDN number
An ISDN subscriber is recognized by:

• An Installation Designation Number "NDI".
• An Additional Designation Number "NDS".
The calling party is identified by the abbreviation "CGP" and the called party by "CDP".
The ISDN number is transmitted in the form of an ASCII character string.

This string consists of, in order:
• the destination number (NDS-CDP)
• the source user number (NDS-CGP)
• the source network number (NDI-CGP)
These numbers are separated by ";" characters.
This gives the general form: (NDS-CDP);(NDS-CGP);(NDI-CGP)
When a source number is present, the end of destination number separator is always present. Similarly
if the source network number is present the end of source user number separator is always present.
☛ With the T2 primary access card (PRI-64), only the source network number (NDI-DR) is
available.
E Page 25-13
E
This gives:
NDS-CDP;NDS-CGP;NDI-CGP
NDS-CDP;NDS-CGP NDS-CDP
;NDS-CGP;NDI-CGP ;;NDI-CGP etc. ...
NDS-CDP;;NDI-CGP ;NDS-CGP
Each of these numbers consists of an address (Addr) and a sub-address (subAddr).

The address and sub-address are separated by ":" characters.
The separator is always present when there is a sub-address.
Addr:subAddr :subAddr Addr
Therefore globally, but not exhaustively:
Addr(NDS-CDP):subAddr(NDS-CDP);Addr(NDS-CGP):subAddr(NDS-CGP);Addr(NDI-CGP):subAddr(NDI-CGP)
:subAddr(NDS-CDP) ;:subAddr(NDS-CGP) ;;Addr(NDI-CGP):subAddr(NDI-CGP)
;;:subAddr(NDI-CGP) ;Addr(NDS-CGP);:subAddr(NDI-CGP) :subAddr(NDS-CDP);;:subAddr(NDI-CGP)
etc...
E Page 25-14
25.9.3 Entering the "calling party identity"
A MAC table record with the function "NDI" must be configured in the Megapac to initiate identification
on the ISDN number. This record should be found in the input MAC program of the V25B descriptor
(that is, between points IBEG and IEND concerning the V25B descriptor).
The format of the record is:
name of NDI NONE A string containing the ISDN number name of

X.25 link (destination, source user, source network) "resource"
DISC (NDS-CDP);(NDS-CGP);(NDI-CGP) identifying the
REJ in the form described previously. calling party
The wildcard character "*" is allowed. (see Note)
A record can continue on the next line by entering "-" in "*" is allowed
the end of line position.
The "SELECTOR" field string is compared with the ISDN number received (only NDI-CGP with the PRI-
64 board).
When the ISDN number does not match the "SELECTOR" field of the "NDI" record(s) the call is rejected.
Note:
In order to use the resources of an X.25 link established by an incoming V.25 Bis call in outgoing mode,
the "resource" name in the GENERATOR field is required, to identify the calling party.
This "resource" name replaces the resource identifier associated with the link for the duration of the call,
enabling X.25 calls to be accepted or rejected on this link.
Options:
The "DISC" option can be used to clear calls set up on a backup link when the main link becomes
operational again. This option should be used with the monitoring function.
The "REJ" option can be used to reject a particular incoming call.
Example A number of "NDI" records can be defined in sequence, each record representing a
particular number.
DIAL IBEG
DIAL NDI REJ 400*;*;700012345*:56
DIAL NDI NONE 400*;*;7000123*:56 P520
DIAL NDI NONE 400*;*;6000123456-
DIAL NDI NONE 789:* P510
DIAL NDI DISC *;*;* P500
E
DIAL IEND
25.10 V.25 bis virtual descriptor parameters

Name Settings
NAME up to 4 characters Virtual descriptor name.
TYPE V25B Virtual descriptor of the links dialing in V.25 bis protocol mode
and/or the "monitor" mode.
CHANNELS 0 to 4096 It is important to declare as many "resources" as there are links
By default = 1 using the V.25 bis protocol and/or the "monitor" mode.
POLL INTERVAL By default = 30 Time in seconds during which the V25B descriptor remains
(0 to 127) "passive" after a Boot, link Restart, etc.
This timer is used to insert a waiting time before re-establishing the
connections associated with the resources of the "V25B" descriptor.
25.11 V.25 bis resource configuration parameters

Name Settings
NAME/ 4 characters Must match the NAME of the "resources" of the link using the V.25
bis protocol.
"""" "Hunt group" mode.
DRC MASK 4 characters Must be the NAME of the "descriptor" of the link using the V.25 bis
By default = . . . . protocol.
In HDLC, X25, PPP this name is that of the "descriptor",
In TERM (asynchronous), this name is that of the "resource".
CIRCUIT TYPE OUT+SVC Qualifies the V25B descriptor virtual resources.
BUFFERS 1 to 240 Should be the same as the number of buffers declared on the link
By default = 2 using the V.25 bis protocol.
MODE By default = Normally the Megapac locally acknowledges the call.
NONE The establishment of level 2 (CRN/VAL, CNX, SABM/UA, Restart)
has twice the timeout value of the CALL TIMEOUT of the link in
V25 Bis mode.
WAIT The WAIT option will cause the V25B descriptor to suppress local
acceptance of the incoming call request, and to wait until a call
accept is received from the outgoing V25 Bis line.
Remote accept timeout has three times the timeout value of the
CALL TIMEOUT of the link in V25 Bis mode.
LSTN Can be used to reserve a V25B resource and the associated
descriptor pending an incoming telephone call.
PULL The "PULL" mode can be used to clear all calls set up on a
backup link without V.25 bis protocol when the main link (with
ECM=V25M) becomes operational again. This option should be
used with the monitoring function.
PUSH For use of modem in CALL-BACK mode.
In this case, there is no call establishment timeout, and the status
of the CTS (circuit 106) is ignored. The clearing of the link should
E
be checked manually.
CALL PRIORITY 0
RESOURCE PRIORITY 0 Lowest.
25.12 Typical configuration in V25 Bis Synchronous and Asynchronous mode
NAME/ P40*
DRC MASK/ . . . .
TERMINAL TYPE/ ASYN
CIRCUIT TYPE/ CALL
OPTIONS/ NONE
...
NAME/ PS04
TYPE/ X25
SUB-TYPE/ XIO Call setup, in V25 Bis mode
...
ADDRESS/ AUTO
...
ECM/ V25B
CALL 5555
CP = 1
NAME/ P40* table X25
DRC MASK/ PS04 P401 0 5555
CIRCUIT TYPE/ OUT+SVC
BUFFERS/ 2
MODE/ NONE
CALL PRIORITY/ 0
table MAC
DIAL OBEG
NAME/ DIAL DIAL DATA NONE P401 N°RTC
TYPE/ V25B DIAL OEND
CHANNELS/ 1
...
Figure 25-1 Typical configuration for a Synchronous link in V25 Bis mode
NAME/ T800
DRC MASK/ . . . .
TERMINAL TYPE/ ASYN
CIRCUIT TYPE/ SVC+V25B Call setup, in V25 Bis mode
OPTIONS/ NONE
...
NAME/ PS08 table X25

TYPE/ TERM T800 0 5555
SUB-TYPE/ SIO
... table MAC
DIAL OBEG
CALL 5555
DIAL DATA NONE TATA N°RTC
CP = 1
NAME/ TATA DIAL OEND
DRC MASK/ T800
CIRCUIT TYPE/ OUT+SVC
BUFFERS/ 2
MODE/ NONE
CALL PRIORITY/ 0
NAME/ DIAL
TYPE/ V25B
CHANNELS/ 1
...
Figure 25-2
E
Typical configuration for a Asynchronous link in V25 Bis mode
Page 25-17
E
25.13 Output MAC table
The MAC table gives the number in V.25 bis mode.

The "DATA" function gives a number in explicit form.
The "DAD, CAD and CUD" functions are used to construct the number from the calling or called DTE
address or call user data.
25.13.1 "DATA" function

LLLL DATA NONE Destination logical Character string
resource
DISC
NAME V.25 bis link virtual descriptor name linked with the output MAC program.
FUNCTION Transfers the telephone number to the V.25 bis link virtual descriptor.
OPTIONS In monitoring mode:
The "DISC" option can be used to clear all calls set up on a backup link when the main link
becomes operational again (RESTART).
The "NONE" option can be used to clear only those calls set up in backup mode on a backup
link, when the main link becomes operational again (RESTART).
SELECTOR Conditional execution of the DATA function.
The content of the SELECTOR field must match a resource name associated with the V.25 bis
GENERATOR This field specifies the number to be sent, all characters can be used.
In the event of conflict with the Megapac command characters, use control character "@".
If the characters "# or "" are used, they are interpreted as number terminators.
Example: take, for example, the following output MAC program::

1 DIAL OBEG
2 DIAL DATA NONE RDES 80312458
3 DIAL OEND
First, consider the following points as given:

• the NAME of the V25B descriptor is DIAL.
• the APPL link must have EXTENDED CALL MANAGEMENT = V25B.
• the RDES destination logical resource must be linked to the APPL link.

2 The telephone number "80312458" is sent to the destination logical resource RDES as a V.25 bis call
request command element for which the prefix is CRN.
E
E
25.13.2 "TIME" function

LLLL TIME NONE Destination logical duration,period,delay
resource
The record or records with the "TIME" function should be between points OBEG ... OEND and placed before
records handling the V.25 B number.
NAME Name of the V.25 bis link virtual descriptor, linked with the output MAC program.
FUNCTION Specifies a maximum call duration, and an inactivity period after which the call is cleared.
SELECTOR Conditionally executes the TIME function.
The content of the selector field should be linked to a resource name, associated with the
V.25 bis link virtual descriptor.
GENERATOR This field specifies the duration of the call and the inactivity period after which the call is
cleared.
This field also specifies a time-delay during which a backup call is deferred.
duration, period and delay are decimal values that express seconds.
duration or the call is cleared after the specified duration.
duration,0
duration, period after the specified duration, incoming and outgoing traffic is observed.
The call is cleared when traffic becomes non-existent during the
specified period.
duration, period, Time in seconds, for which a backup call is deferred, following a Boot,
delay Restart, etc.
or This timer is used to avoid connecting (or reconnecting) a backup link
..delay too quickly following system initialization.
Example: Take, for example, the following output MAC program:

1 DIAL OBEG
2 DIAL TIME NONE RDES 50,10
3 DIAL DATA NONE RDES 80312458
4 DIAL OEND
First, let us look at the following points:

• The TYPE/ V25B descriptor has the NAME/ DIAL.
• The APPL link should have EXTENDED CALL MANAGEMENT = V25B.
• The destination logical resource RDES should be associated with the APPL link.

2 The call set up on destination logical resource RDES is maintained for 50 seconds.
After this time (50 seconds), traffic is observed.
When the line is inactive for a period of ten seconds, the line is cleared.
E
3 The telephone number "80312458" is sent over destination logical resource RDES, as an element of the
V.25 bis call request command, the prefix of which is CRN.
E
25.13.3 "CAD" function

SELECTOR GENERATOR
LLLL CAD NONE Destination logical Character string including special characters #
resource and/or ".
DISC
Space.
NAME The name of the V.25 bis link virtual descriptor linked with the output MAC program.
FUNCTION In a call request packet, extracts the content of the "Calling DTE address" field.
Reconstructs the character string obtained for formatting as a telephone number.
Transfers this number to the V.25 bis link virtual descriptor.
The "DISC" option is used to clear all calls set up on a backup link when the main link becomes
operational again (RESTART).
The "NONE" option is used to clear only those calls set up in backup mode on a backup link
when the main link becomes operational again (RESTART).
SELECTOR Conditional execution of the CAD function.
The content of the SELECTOR field must match a resource name linked to the V.25 bis link
virtual descriptor.
GENERATOR The content of this field can be:
Space
The content of the "Calling DTE address" field of the call request packet is the telephone
number.
Character string
The content of the "Calling DTE address" field of the call request packet is reconstructed
according to this character string.
The result is the telephone number.
Example: take, for example, the following output MAC program:

1 DIAL OBEG
2 DIAL CAD NONE RDES # 2 "8
3 DIAL OEND
First, consider the following points as given:

• the destination logical resource RDES must be associated with link APPL,
• in the call request packet, the "Calling DTE address" field contains 0175485603.

2 In the call request packet, the content of the "Calling DTE address" field (0175485603) is extracted.
This character string is reconstructed using the syntax specified in the GENERATOR field.
The result of reconstruction (75485603) is a telephone number.
E
This will be transmitted over the destination logical resource RDES as a V.25 bis call command element for
which the prefix is CRN.
E
25.13.4 "DAD" function

SELECTOR GENERATOR
LLLL DAD NONE Destination logical Destination character string comprising special
resource characters # and/or ".
DISC
Space.
NAME Name of the V.25 bis link virtual descriptor linked with the output MAC program.
FUNCTION In a call request packet, extracts the content of the "Called DTE address” field.
Reconstructs the character string obtained to format it as a telephone number.
Transfers this number to the V.25 bis link virtual descriptor.
SELECTOR Conditional execution of the DAD function.
The content of the SELECTOR field must match a resource name associated with the V25 bis
Space
The content of the "Called DTE address" field of the call request packet is the telephone number.
Character string
• The content of the "Called DTE address" field of the call request packet is reconstructed
according to this character string.
• The result is the telephone number.

1 DIAL OBEG
2 DIAL DAD NONE RDES # 1 "8
3 DIAL OEND
First, consider the following points as given :

• in the call request packet, the "Called DTE address" field contains 267314754.

2 In the call request packet, the content of the "Called DTE address" field (267314754) is extracted.
The result of reconstruction (67314754) is a telephone number. This will be transmitted over the
E
destination resource (RDES) as a V.25 bis call command element with the CRN prefix.
E
25.13.5 "CUD" function
NAME FUNCTION OPTIONS

SELECTOR GENERATOR
LLLL CUD NONE Destination logical Character string including special characters #
resource and/or ".
DISC
Space.
NAME Name of the V.25 bis link virtual descriptor linked to the output MAC program.
FUNCTION In a call request packet, extracts the content of the "Call user data" field.
Reconstructs the character string obtained to format it as a telephone number.
Transfers this number to the TYPE/ V25B link virtual descriptor.
SELECTOR Conditional execution of the CUD function.
The content of the SELECTOR field must match a logical resource name associated with the
V25B link virtual descriptor.
Space
The content of the "Called user data" field of the call request packet forms the telephone
number.
Character string
The content of the "Call user data" field of the call request packet is reconstructed according to
this character string.
The result forms the telephone number.
1 DIAL OBEG
2 DIAL CUD NONE RDES # 4 "8
3 DIAL OEND
First, consider the following points as given :

• in the call request packet, the "Call user data" field contains 157940817022.

2 In the call request packet, the content of the "Call user data" field (157940817022) is extracted.
The result of reconstruction (40817022) is a telephone number. This will be transmitted over the
destination logical resource RDES as a V.25 bis call command element for which the prefix is CRN.
E
25.14 Review of ISDN network reject "Causes"
The following list is derived from a CNET document. The "cause" is given by a decimal code.
Cause Meaning
07 Call assigned and being handed over to an established link
16 Normal release
17 User busy
18 No answer from user
19 Facility not registered
21 Call reject
22 Number changed
24 Unassigned number
27 Destination out of order
28 Incomplete address
31 Normal not specified
34 No circuit or channel available

41 Network out of order
42 Network congestion
44 Requested channel or circuit unavailable
47 Network resources temporarily unavailable, unspecified
49 UUS not sent

50 Not entitled to facility
59 Call restriction
60 National call transfer rejected
62 Not entitled to service
63 Service or option unavailable, unspecified
65 Bearer service not enabled

66 Type of channel not enabled
69 Facility not implemented
79 Service or option not enabled, unspecified
E Page 25-23
E
81
82
Invalid call reference value

Identified channel does not exist
83 Call identity does not exist
84 Call identity in use
92 Facility parameter error
95 Invalid message, unspecified
96 Mandatory information element omitted

97 Unknown message
98 Message incompatible with call state
99 Information element not known or not enabled
100 Invalid information element content
103 Message received with mandatory information element of incorrect length
111 Protocol error, not specified
113 Bearer service not available

114 End-to-end information transfer not possible
126 Switch to conversation
127 Interworking not specified
E Page 25-24
26. TYPE/ SDLC - QLLC descriptor
26.1 General
The Megapac can be used to emulate the protocols and physical and/or logical units used in the SNA
architecture.
For this, the Megapac's packet switching characteristics are used to provide a communications network
conforming to the OSI model while maintaining supporting for the existing IBM protocol.
The Megapac can be configured to support the SDLC/QLLC (Synchronous Data Link Control) protocol.
According to this protocol a master terminal (the host) polls the other terminals to send in turn; each
terminal must respond to each transmission. With the Megapac controller, all SDLC pollings cycles are
acknowledged locally.
A number of SDLC controllers (IBM 3x74 or 5x94 type cluster controllers, for example) can be
concentrated and, using the Megapac can be connected to the SDLC port of a front-end processor in
point-to-point mode or multipoint mode.
The X.25 packets assembled by the Megapac carry only control information and the data required by the
receiving equipment. SNA data transmission information (contained in standard X.25 packets) is sent
directly to the IBM equipment having an X.25 QLLC facility, or reconstructed to the original SDLC format
using another Megapac controller.
The cluster function can provide multiple type 2 PU emulations, each in turn allowing multiple LU1 or
LU2 connections. This enables VT100, VT220, ANSI or PC terminals to access applications connected
in SNA mode. The Megapac software contains the functions required for screen management and
character mapping.
Note : The MIO board cannot be used with SDLC and QLLC mode (descriptor TYPE/ SDLC and QLLC).
26.1.1 SDLC/QLLC relation
The normal way for IBM to establish a network is to use a data link to connect a host computer to a 3274
cluster controller with its terminals, linked by a coaxial cable, and their attached printers. The protocol is
SDLC. The SDLC (BLU) frames carry the SNA network information and data.
QLLC is a method of using X.25 to transmit SNA data directly to IBM equipment. The three SDLC
header and trailer bytes are replaced by X.25 headers and trailers.
The Megapac enables SDLC equipment (3174 for example) to be connected via X.25 packet switching
networks. The principle is based on using the X.25 advantages for sharing network resources, adaptive
routing and network management.
In addition, SNA traffic can co-exist with other network connections and services.
TYPE/ SDLC - QLLC descriptor
E Page 26-1
Megapac
QLLC Descriptor
(Primary Station=NO)
Polls
QLLC link
X25 over X25
SDLC QLLC
Responses Descriptor
Secondary Primary
SDLC link (SDLC2) (QLLC1)

to SNA Host
Front End
Processor
X.25
Network
Megapac
QLLC Descriptor
(Primary Station=YES)
Polls
X25
QLLC SDLC
Descriptor Responses
QLLC link Secondary Primary
over X25
(QLLC2) (SDLC1) SDLC link
to cluster
controller
Figure 26-1 "QLLC" descriptor functions
E Page 26-2
E
26.1.2 Link emulation types
The Megapac adopts the IBM QLLC function for connection to the packet switched networks, enabling
the SDLC protocol to be carried on X.25 networks, but without a surfeit of network-to-network polling.
The primary/secondary relationships employed in the SDLC and QLLC protocols are supported by the
Megapac which provides two operating modes:
SDLC primary: provides host/front-end emulation towards a cluster controller. The host polls the
cluster controller using SDLC and transfers the QLLC data received from the X.25
network to the cluster controller.
SDLC secondary: provides cluster controller emulation towards a host/front-end. The cluster controller
responds to polling messages from the host and transfers the SNA data to the X.25
network as QLLC data.
The Megapac can support both point-to-point and multipoint links.
26.1.3 Additional characteristics
The Megapac also allows to peer-to-peer connections in which both ends use an exchange of XID to
negotiate secondary station status. The Megapac responds dynamically to the XID by configuring the
QLLC/SDLC operating mode and the negotiated address of the station.
PU switching is also provided, enabling the Megapac to support SSCP to LU session emulation and
display a menu giving a choice of hosts and services. After selecting the required host, the Megapac
provides an X.25 connection which enables the SSCP/PU and SSCP/LU session to be established. The
Megapac then becomes transparent immediately the BIND command is sent.
26.1.4 Configuring a Megapac link
The Megapac supports the two primary and secondary terminations of a link using the SDLC or QLLC
protocol.
The Megapac normally supports only NRZ coding with SDLC. However, the Megapac E and Megapac
ES feature a hardware option supporting NRZI coding.
When beginning a configuration, you should establish a network diagram to determine which link
descriptors are required for the Megapac(s).
To configure the Megapac you must:
• configure the interface between Megapac and host,
• configure the interface between cluster controller and Megapac,
• establish the virtual connections.
E Page 26-3
HOST
VTAM
QLLC
NCP
SNA S Q
D L
(FEP) L L
SDLC C C
2 1
X25
X25 network
X25
Megapac
X25
X25
M
X25
e
g
M a
e X25 p
g a
a c
p
a
c QLLC 2 Q
QLLC 2 C L
L L
SDLC 1
3174 U C
emulator S
P
A SDLC
D
VT100 terminals Cluster

Controller
(3174)
IBM terminals
Figure 26-2 Megapac used as a cluster controller
E Page 26-4
26.2 SDLC - QLLC link configuration parameters

Name Settings
NAME 4 characters Link name.
TYPE Defines the link type.
QLLC Used for a Qualified Logical Link Control type link via an X.25
network.
The descriptor offers a QLLC to X.25 interface and an SDLC to
"SNA" host interface.
SDLC Used for a Synchronous Data Link Communication protocol type
link via an X.25 network.
For this type of link, the QLLC procedure will be deactivated.
XIO, SCC or NONE
The first descriptor of a GIS board contains interchanges with
the board.
XIO The descriptor addresses an XIO board.
SIO The descriptor addresses an SIO board.
XIO+SIO Do not use for a link of type SDLC - QLLC.
INTERFACE SDLC/QLLC mode.
(NPI) YES A new SDLC/QLLC link is allocated to this descriptor.

This parameter must normally be at YES.
128K, 64K, 48K, 19.2,
2 Mbit/s.
By default = EXT
2400 to 64 Kbit/s.
E Page 26-5
E
PIGGY TYPE
Megapac ESL and
Megafrad
(DCE+V24)
By default = V24 Choice of the interface type

The hardware must be correctly configured (straps) to allow the
software to choose the interface type.
or DCE+V24 • a DCE port (to a terminal), using the straight cable
55.670.243
• a DTE port (to a modem), using the crossed cable
55.670.357
mode (to a modem).
mode (to a modem).
1 Point-to-point mode: only one cluster connection.
n>1 Only in QLLC mode.
Multipoint mode: several clusters are polled.
PRIMARY NO Determines the primary or secondary SDLC interface.
STATION (default setting) By default, the QLLC descriptor behaves as a secondary
interface with respect to the SDLC controller and as a primary
QLLC interface with respect to the X.25 network.
YES The QLLC descriptor behaves as a primary (host) interface with
respect to the SDLC controller and a secondary QLLC interface
with respect to the X.25 network.
E Page 26-6
E
IDLE DETECT TIME 0 to 100
(in 1/10s of a second)

Frame retransmission timing
with PRIMARY STATION/ YES, therefore primary SDLC
interface
The IDLE DETECT TIME timer is used to detect
By default = 0 acknowledgment faults for the data frames sent with the
Megapac (on the SDLC link).
On timer expiry, the Megapac retransmits the unacknowledged
data frames. When the number of retransmissions reaches the
TRIES parameter value, the Megapac clears the virtual circuit.
with PRIMARY STATION/ NO , therefore primary QLLC interface
In the same way, the IDLE DETECT TIME timer is used to detect
ò 90 x N x K
+ 1 acknowledgment faults for the data frames sent with the
V
Megapac (on the X25 link).
Note:
The IDLE DETECT TIME timer only applies to data frames.
For the service frames (XID, SNRM, DISC, etc.) an internal timer
(set at 300 msec) is used.
In practice: IDLE DETECT TIME ò 9 0 x N x K + 1
V
N = number of bytes per frame (e.g. 256)
K = window value (e.g. 7)
V = line rate in bauds (e.g. 9600)
For this example, the recommended value is 18 (i.e. 1.8
seconds)
POLL INTERVAL 0 to 100 Polling frequency.
(in 1/10ths of a second) This parameter affects only the cluster side Megapac. It defines
By default = 0 the frequency of polling messages to be sent to a cluster
controller.
DUPLEX HALF Reserved attribute.
FULL Simultaneous bilateral (full duplex) communication.
(default setting)
TRANSMIT DELAY 0 to 20 Time delay to be observed between receipt of an RR (Receiver
(in 1/10ths of a second) Ready) frame with the P bit set and transmission of the RR
By default = 0 response from the Megapac with the F bit set.
Note: the IDLE DETECT TIME parameter must also be defined
on the secondary machine since this machine is used to
synchronize retransmission of QSM, QXID and other commands
via the network, even if the network comprises only a single
node.
E Page 26-7
E
OPTIONS NONE
(default
setting)
DCD
When a connection is set up normally, the Megapac responds to the poll message
from the host with a DM response until the QLLC connection is set up.
In a PU4 to PU4 connection , the DCD option allows to control the link in
accordance with the signal state (CTS or DTR).
The signal (CTS or DTR) depends on the type of cable used.
The « low » state of the signal is pointed out by the DCD bit of the EIA indicator’s
link STATistics.
PU4 Enables PU4 to PU4 communication; in this mode, the master/slave relationship
is negotiated as described above for XID. When the link is initiated, the primary
station uses an address without the MSB set, while the secondary station uses the
same address but with the MSB set (SDLC Echo Defeat bit). For example, in
hexadecimal, Primary = 01, Secondary = 81.
In this mode, the following parameters must be configured (and at each end if
both the ends are connected by QLLC Megapac link):
- descriptor level CHANNELS/ 1,
- descriptor level OPTIONS/ XID+PU4 (for a transparent exchange of XID and
PU4 to PU4 transmission),
- descriptor level PRIMARY STATION/ NO,
- logical resource level STATION ADDRESS/ must be configured with the address
of the station without the Echo Defeat bit set (for example, both ends at 01).
TLAT see PU4 option
DUPX Full duplex mode
WAIT In a multipoint environment, a DM response to an XID or SNRM request causes
the host to shut down the SDLC link (after the time delay specified has run out at
the host end). To avoid this, the WAIT option can be used as follows:
1. If the host sends an XID request, the Megapac sends an XID response
containing the XID defined in the MAC table. Remember that the WAIT option
must be combined with the XID option described below.
2. If the host sends an SNRM request, the Megapac sends a UA response.
3. If the host sends an RR poll, the Megapac sends an RNR response until a
QLLC connection is set up. Remember that when the QLLC network connection
is disconnected, the Megapac sends a DM response which results in states 1 and
2 above.
XID For AS400 to AS400 peer-to-peer connections in which the two ends negotiate a
Primary/Secondary relationship by an exchange of XID with the STATION
ADDRESS parameter set to FF, one of the ends assumes the Primary role by
sending an SNRM frame with a normal address. In this mode, the following
parameters must be configured (and at each end if both ends are connected by
QLLC Megapac link):
- descriptor level CHANNELS/ 1,
- descriptor level OPTIONS/ XID (for a transparent exchange of XID),
- descriptor level PRIMARY STATION/ NO,
- logical resource level STATION ADDRESS/ FF.
WAIT+XID Generates an XID response (in response to an XID request and before an SNRM
is received), using the MAC table.
IDLE With an "XIO" board this option enables you to send permanent 1s "FF", instead
of flags "7E", after receiving at least one flag "7E".
E Page 26-8
E
SLOW POLL
TIMER
0 to 255
(in 1/10ths of a second)

By default = 0
If PRIMARY STATION/ is set to YES, a poll speed can be defined for
slow polling to a cluster controller that is down. This prevents the
generation of delays when cluster controllers are working in multipoint
mode.
MAXIMUM 0 to 20 If PRIMARY STATION/ is set to YES, a call request interval can be
CALL (in minutes) defined to avoid situations in which successive call requests are
INTERVAL By default = 0 continually generated via the network. The initial call interval is 2
seconds, which is successively multiplied by 2 until the MAXIMUM
(0 means 2 second) CALL INTERVAL setting is reached or exceeded.
This cycle is then repeated a number of times (the number of times is
specified by the MAXIMUM CALL CYCLES parameter), after which
each retransmission of a call request is separated by the highest time
interval associated with the MAXIMUM CALL INTERVAL parameter.
Notes:
- MAXIMUM CALL INTERVAL/ 0 represents a maximum interval of 2
seconds;
- on receipt of a QLLC restart (for example, receipt of a QSM packet),
the cycle is reset.
MAXIMUM 0 to 255 Used in conjunction with the MAXIMUM CALL INTERVAL parameter.
CALL By default = 0 Defines the maximum number of call request cycles which take place
CYCLES before the MAXIMUM CALL INTERVAL setting is reached. Each
cycle consists of two call requests sent at intervals incremented by
multiples of 2 seconds until the MAXIMUM CALL INTERVAL setting is
reached or exceeded.
For example, if MAXIMUM CALL INTERVAL is 2 (in minutes) and
MAXIMUM CALL CYCLES is 4, the call request cycle is (in seconds):
Cycle 1 = 2, 4, 8, 16, 32, 64.
Cycle 2 = 2, 4, 8, 16, 32, 64.
Cycle 3 = 2, 4, 8, 16, 32, 64.
Cycle 4 = 2, 4, 8, 16, 32, 64.
Cycle 5 = 64, 64, 64, 64, 64, ....
GROUP POLL 00 to FF "SNA Group Poll" function.
ADDRESS (hexadecimal or BCD) "00" renders the function INACTIVE.
TRIES 2 to 80 If PRIMARY STATION/ is set to YES, this parameter indicates the
By default = 10 number of consecutive polls which will be sent without receiving any
response from the IBM cluster before the virtual circuit is released.
WINDOW SIZE 1 to 31 Maximum number of SDLC frames that the Megapac can send before
By default = 7 requiring an SDLC acknowledgment.
FRAME SEQ NORM Frame sequencing.
(default setting) Normal frame sequencing (modulo 8, numbers in sequence from 0 to
7, one check byte).
EXT Extended frame sequencing (modulo 128, numbers in sequence from
0 to 127, two check bytes).
CALL TIME 2 to 200 Maximum time delay during which the Megapac will wait for a
OUT (in seconds) response from the host (on setting up the call) before canceling the
By default = 5 call request.
E Page 26-9
Each QLLC descriptor resource represents a logical connection with an IBM cluster controller or a host
system.

Name Settings
Each resource must be defined with a unique name.
DRC MASK 4 characters Fully or partly identifies a destination resource, used for
maximum routing.
....
(default setting)
TERMINAL TYPE ASYN Identifies the terminal type.
(default setting) This parameter does not affect the resources of a QLLC or SDLC
descriptor.
STATION ADDRESS from 00 to FF Secondary station address.
(hexadecimal) 1. If the link descriptor has PRIMARY STATION set to NO and
By default = 0B CHANNELS set to 1, the address must be FF. The Megapac will
respond to any poll from the host up to the address limit FF.
2. If the link descriptor has PRIMARY STATION set to YES and
CHANNELS set to 1, the address must be FF. The Megapac will
broadcast an XID request to the cluster controller, which will return
an XID response with its address, enabling the Megapac to send a
startup frame (for example, SNRM) to this cluster address.
3. If the link descriptor has PRIMARY STATION set to YES and
CHANNELS with a setting greater than 1, each resource must
define the address of a cluster (for example, C1, C2, C3, etc). The
link will be started up when an SNRM frame is sent.
4. If the link descriptor has PRIMARY STATION set to NO and
CHANNELS with a setting greater than 1, each resource must
define the polling address of the host (for example, C1, C2, C3, etc).
The link will then be started up when an SNRM frame is sent by the
host.
PROVIDE XID By default = YES XID response frame.
YES If the link descriptor has PRIMARY STATION set to YES, an XID
will be generated by the MAC table in response to an XID request
from the host.
NO When an XID request is sent by the host, the XID response will be
generated by the cluster controller.
E Page 26-10
E
CIRCUIT TYPE
CALL+STAT
(default setting)
CALL
Main I/O characteristics of the resource.
Operates as an SVC and will automatically generate setup of the

call circuit (using DRC MASK) when the cluster is interrogated and
a positive response is received, or when a poll is received from the
host requiring an XID response. See also MAXIMUM CALL
INTERVAL and MAXIMUM CALL CYCLES parameters of the link
descriptor.
PVC CALL+PVC. On detection of data, a virtual circuit is set up using
the DRC MASK specified to define the routing.
OUT The resource supports only incoming calls.
STAT Option. It provides connection/disconnection statistics on the
resource defined in SESSION STATISTICS of the base descriptor
(EI01 by default).
OSI not used
other Other settings have no effect on a QLLC or SDLC descriptor.
OPTIONS NONE No options required.
(default setting)
IDLE In QLLC, the "IDLE" option must be set on both sides (primary and
secondary).
The virtual circuit is cleared if it is no longer transmitting information
during the time predefined by the INACTIVITY TIMER/ parameter of
the BASE descriptor.
others Other settings have no effect on a QLLC or SDLC descriptor.
BUFFERS 1 to 240 Setting determining the total number of buffers available.
By default = 2 This figure must be multiplied by the contractual packet size to
determine the total number of HDLC bytes that can be stored.
CALL PRIORITY from 0 to 15 Calling line priority (CP >= RP).

By default = 0 This parameter is not used for a call destination resource.
RESOURCE from 0 to 15 Called line priority.
PRIORITY By default = 0 This parameter is not used for a call source resource.
Bandwidth>0, allows to define the requested speed before routing.
E Page 26-11
26.3.1 X.25 table in SDLC - QLLC mode

characters maximum Adopts the name of a resource of an SDLC or QLLC link.
ADDRESS GROUP 0 to 15 Address group.
By default = 0 Used to devise a network into different address fields (for
example, to separate a private network from a public network).
ADDRESS X.121 routing address.
Indicates the X.25 address which will be generated for all calls
including the name of the logical resource specified in the
NAME parameter.
USER DATA C3 (hexadecimal) Facilities and/or User data
Must be configured to contain the QLLC PID (Packet
IDentifier). When a call request packet is received, the host
searches the PID table using this setting and recognizes the
packet as carrying the QLLC protocol. Optionally, functions
can be configured in the call request packet by including them
in this field following the PID.
Note: These functions must be defined in brackets.
26.3.2 MAC table in SDLC - QLLC mode

NAME 4 alphanumeric Adopts the name of a resource of an SDLC or QLLC link.
characters maximum
FUNCTION XID Specifies that the function of this record is to replace the XIDs.
OPTIONS NONE No options.
SELECTOR Not used.
GENERATOR 12 alphanumeric The XID specified is used in response to an XID prompt from
characters the host. The characters ! (replacing a character) and *
(replacing a character string) can be used.
E Page 26-12
27. TYPE/ CLUS descriptor
The "CLUS" descriptor works as a cluster controller for Type 2.0 physical units supporting from 1 to n
logical units (type 1 or 2 LUs).
The "CLUS" descriptor is a virtual descriptor for connecting terminals other than 3270 to an IBM SNA
site.
The « CLUS » descriptor also and simultaneously allows to connect terminals in 3270 native mode.
Communications with the host machine are handled by a QLLC link in X.25 mode or by a connection in
SDLC mode.
The "CLUS" descriptor behaves as a secondary QLLC unit with respect to the host.
HOST
Megapac
VTAM
QLLC
NCP
SNA S Q
D L
(FEP) L L
SDLC
C C
2 1
QLLC 2 C
L
3174 U
emulator S
TERM
X25
TERM
VT100
VT200
ANSI
etc ...
terminals
Figure 27-1 Direct cluster connection to SNA host
The « CLUS » descriptor simultaneously provides accesses with terminal emulation, and accesses in
3270 native mode. Thanks to the « Reverse Pad Telnet » function of the Megapac, the Megapac acts as
an Ethernet or Token ring coupler vis-à-vis an SNA IBM host.
TYPE/ CLUS descriptor
E Page 27-1
HOST
Megapac
VTAM
QLLC
NCP
SNA S Q
D L
(FEP) L L
SDLC C C
2 1
X25
QLLC link
over X25
M
e X25
g
a
p
a
c QLLC 2 C
L
3174 U
emulator S
TERM
X25
TERM
VT100
VT200
ANSI
etc ...
terminals
Figure 27-2 Cluster connection via an X.25 network
E Page 27-2
27.1 Functionality of the CLUS link descriptor
3270 identifies a family of IBM products including cluster controllers, visual display terminals and printer
terminals.
A Megapac mode serves as a 327x cluster controller following the simultaneous use:
• of a CLUS link descriptor
The PU2 then corresponds to the CLUS logical resource number 0.
Resource number 1 must not be used.
Each LU2 is connected to a CLUS logical resource number > 2.
• of the input MAC file
This is the PU function for a PU/LU cluster connection.
Remember that in this regard, execution of a REST command on logical resource number 0
automatically results in a search for a PU function in the input MAC file.
The resources of a "CLUS" descriptor are configured as follows:

• in the CLUS link descriptor, TYPE = CLUS, CHANNELS = number of LU + 1 PU + 1
• in CLUS resource number 0, DRC MASK = xxxx
• in CLUS resource number 1, NAME = xxxx, DRC MASK = . . . .
• in CLUS resources numbers 2 to n, NAME = according to use
• in the X.25 link descriptor, TYPE = X25, CHANNELS = number of LU + 1 PU
• in the X.25 logical resource, NAME = according to use
Using the DRC MASK, logical resource number 0 (PU2) defines both an "upstream" routing (X.25 link
descriptor) and a "downstream" routing (each LU2).
Each resource of a "CLUS" descriptor must have a memory area for emulating a terminal. The
"TERMINAL EMULATION BUFFER" parameter of the BASE descriptor should therefore be set
accordingly.
E Page 27-3
E
27.1.1 IND$FILE file transfer
For memory, the character "~" corresponds to the hexadecimal value "7E".
The CLUS resource associated with the LU2 concerned must be configured as TERMINAL
TYPE = MTRM.
1) When the file is transferred from the terminal, enter ESC [ 255 ~ to activate the IND$FILE
mode.
• The Megapac node then handles the transfer of the information entered transparently, only
the TH (Transmission Header) and RH (Request Header) being generated by the Megapac.
• Terminal input sequences:
• ~1 Start of RU (Request Unit)
• ~2 Replacement of the sequence (~ 2) by the character (~)
• ~3 End of RU
• ~4 Deactivation of the IND$FILE mode
2) When the file is transferred from the host
• The Megapac node assumes that it is a structured file and that all information is conveyed
transparently, in other words after the RU header.
• Control sequences, generated by the Megapac node:
• ~1 Start of RU
• ~2 Replacement of the (~) character
• ~3 End of RU
27.1.2 File transfer between PCs
The input sequence ESC [°214 ~ sets up flow control for data entered from a PC.
In this mode, the 3270 emulator of the Megapac node concerned:
• sends an X-OFF character (13 hex) each time it wants to lock out the PC keyboard.
• sends an X-ON (11 hex) each time it wants to free the keyboard of the PC when one of the following
conditions is met: in the RH (Request Header), the EBI (End Bracket Indicator) or CDI (Change
Direction Indicator) is set to 1.
The input sequence ESC [°215 ~ restores the normal mode.
Terminal input sequences for dynamically modifying the terminal configuration

ESC [ 200 ~ VT100 terminal
ESC [ 201 ~ ANSI terminal
ESC [ 202 ~ MTRM terminal
ESC [ 203 ~ VT220 terminal
ESC [ 210 ~ Delete message line
E
ESC [ 211 ~ Display message line
ESC [ 212 ~ Print screen
ESC [ 213 ~ No screen print
TYPE/ CLUS descriptor Page 27-4
27.1.3 Generation of a menu when routing to a terminal
The Megapac node configuration is as follows:

• in the CLUS resource with a number greater than or equal to 2
NAME = nnnn, MENU NUMBER = N,
• in the input X.25 logical resource, OPTIONS = NAME.
• The NAME file must contain a record, the main characteristics of which are given below :
NAME = service name, DRC MASK = nnnn.
When handling the call on the CLUS logical resource, the MENU NUMBER = N parameter initiates
display of menu N to the caller, in other words on the input X.25 logical resource.
This menu lists the terminal types (VT100, VT220, etc).
The call must then enter a service name (VT100, for example). A search is then carried out in the
NAME file to find a match between the service name entered (VT100, in this example) and the content
of a NAME field.
If a match is found, the associated DRC MASK ([ 200, for example) establishes the connection to the
CLUS logical resource and the LU concerned.
Remember that the content of the DRC MASK is an abbreviated terminal input sequence.
27.1.4 Graphics characters, from the extended ASCII code
The extended ASCII code is selected using the following input sequence: ESC [ 204 ~.
In it, the most significant bit is set to 1, representing a binary configuration in which the setting is
>= 80 hex.
Currently, only the extended ASCII characters 9C hex and AA hex are available.
In the "default" ASCII/EBCDIC mapping table, they respectively correspond to the EBCDIC characters
5B hex (£) and 5F hex (NO operation).
When the input sequence mentioned above is not executed, the EBCDIC characters 5B hex and 5F hex
are respectively converted by default to ASCII 23 hex (#) and 5E hex (^).
E Page 27-5
E
Parameter

Name Settings
NAME Up to 4 characters Link reference name.
TYPE CLUS Operation in cluster mode.
CHANNELS 0 to 4096 Number of resources available on this descriptor. The
By default = 1 setting should reflect emulation requirements.
Applicable settings are 2 to 254.
POLL INTERVAL By default = 30 The CLUS descriptor remains « passive » during this
(1 to 127) time (in second), after a Boot or a Restart.
This timer allows to guarantee a waiting time before the
restoring of the connections associated to the « CLUS »
descriptor resources.
DEFAULT LOCAL PRINTER 0 to 128 Number of resources reserved as screen display
By default = 0 servers.
Screen print requests from each LU are directed to this
server.
By default (0), the display function is inactive.
Note: The LOCAL PRINTER/ parameter defined for the
resource takes precedence over the DEFAULT LOCAL
PRINTER/ parameter.
NMVT By default = NO Operation in 3270 cluster controller mode.
YES Reserved for future use (IBM Netview).
E Page 27-6

Name Settings
NAME Up to 4 characters The name specified for logical resource 0 is used in
conjunction with the NAME/ field of the MAC table which
defines that this resource is a PU and supplies the XID
needed by the host to recognize the PU.
XXXX The name specified for resource 1 must be XXXX to indicate
that it is a null resource.
The name specified for a resource 2 to n defines the name
used for internal routing.
You can use the syntax NAME/ “ “ “ “ to create discrete hunt
groups.
DRC MASK 4 characters The logical resource 0 (PU) must be fully specified to enable
By default = . . . . the connection to a named resource to be set up
automatically. If the named resource is an X.25 resource, its
RP must be 0.
.... The default DRC is left for logical resource 1.
If the DRC of one of the resources 2 to n is specified . . . .,
call requests will be accepted only to an emulation resource
XXXX If the DRC of one of the resources 2 to n is specified in its
entirety, a call request will be sent by the emulator on
detecting data from the host.
TERMINAL TYPE By default = ASYN Defines the terminal emulation profile required by the user
when accessing a resource configured as a type 2 LU. This
parameter applies only to resources 2 to n.
By default, ASYN specifies emulation of a monochrome
VT100 terminal.
ASYN+3270 « Native 3270 data stream » mode.
ANSI Emulation of a synchronous VT100 terminal with the options
" color display" and "line 25 status display".
MTRM Emulation of an "old model" ANSI terminal.
Supports IND$FILE file transfer mode.
VT22 Emulation of a synchronous VT220 terminal with the options
"color display" and "line 25 status display".
other The other settings available do not affect a CLUS descriptor.
E Page 27-7
E
OPTIONS
ISO
By default = NONE By default, no option is required.

This setting activates the Megapac's internal class 3
transport implementation.
IDLE Attribute applicable to resources 2 to n only.
If the resource remains inactive after the time delay specified
in INACTIVITY DETECT TIMER/ (BASE descriptor),
connection will be broken.
NO_M This option forces the « More » information bit to zero.
other The other settings available do not affect a CLUS descriptor.
By default = 0
RESOURCE PRIORITY 0 to 15 Called line priority..
By default = 0
MENU NUMBER 0 to 32 Activates/deactivates the presentation mode.
By default = 0 By default, the user is directly linked to the LU session.
For any setting greater than 0, calls incoming on this
resource are intercepted; the Megapac activates the
presentation mode and displays the number corresponding
to the specified record number.
RETAIN SESSION By default = NO Parameter applicable to resources 2 to n only.
By default, after a disconnection from this resource, the
session is not maintained. If INTERLOCK BIND is YES, an
UNBIND request is sent to the host.
NTFY The session is not retained after a call disconnection. The
NOTIFY and LUSTAT requests indicate a connection and
disconnection state transition.
Apart from specific cases, this option must not be used in
conjunction with INTERLOCK BIND/YES.
YES The current session is kept active after a resource
disconnection.
E Page 27-8
E
PRINTER TYPE
By default = NONE Parameter applicable to resources 2 to n only.

By default, the logical resource operates in screen emulation
mode.
IBM The logical resource behaves as a system printer.
SCREEN PRINTER By default = YES Parameter applicable to resources 2 to n only.
By default, hard copy requests are processed and sent to
this resource. In this mode, the terminal connected to this
resource must have a printer connected.
NO Hard copy is handled via the LOCAL PRINTER parameter or
the DEFAULT LOCAL PRINTER parameter.
LOCAL PRINTER 0 to 128 Parameter applicable to resources 2 to n only. Specifies the
By default = 8 destination resource for hard copy. This means it is possible
to configure an arbitrary number of printers for each cluster.
By default, this option is inactive and the hard copy facility is
governed by the DEFAULT LOCAL PRINTER parameter.
INTERLOCK BIND By default = YES Parameter applicable to resources 2 to n only.
By default, the Megapac sends an UNBIND request to the
host before clearing the connection.
NO The Megapac sends an RSHUTD request to the host before
disconnecting.
REDIRECT PRINT TO By default = 0 Parameter applicable to resources 2 to n only.
By default, data is not redirected.
0 to 128 Type 1 LU session data is directed to the specified logical
resource, each block preceded by an escape sequence to
redirect the data to the auxiliary port, and followed by
another sequence to send it again to the screen.
E Page 27-9
27.4 MAC table parameters in CLUS mode
For logical resource 0 of the CLUS descriptor to operate as a type 2 PU, an MAC table record must be
configured to contain the address of the PU station and the XID description to be used to respond to a
QXID request sent by the host.
Parameter Settings Meaning

NAME 4 alphanumeric Logical resource name.
characters maximum Must match the NAME parameter of the CLUS descriptor's logical
resource.
FUNCTION PU Specifies that the logical resource is used as a type 2 PU.
OPTIONS NONE No option
SELECTOR [IC] Optional parameter, entered between brackets and in uppercase,
which, whatever the terminal type and for all type 2 LU sessions:
-. deactivates display of the status line,
-. changes Blue to Cyan.
Note : display of the status line can be re-enabled using the
escape sequence Esc [ 200 ~
[Ix] Optional parameter, entered between brackets with the X in
lowercase and the L in uppercase, which deactivates display of
the status line, regardless of the terminal type and or all Type 2
LU sessions.
Note : display can be re-enabled using the escape sequence
ESC [ 200 ~
[xC] Optional parameter, entered between brackets with the X in
lowercase and the C in uppercase, which changes Blue to Cyan
regardless of the terminal type and for all Type 2 LU sessions.
GENERATOR 32 alphanumeric This parameter indicates the address of the CLUS virtual
characters controller station (C1, for example) and the XID information
needed to describe the PU type and the cluster address to the
host.
In the C1,0200017nnnn format, nnnn is the PU block number.
If the host requests additional XID information exceeding the
limits of the GENERATOR field (more than 32 characters), the -
(hyphen) character must be used in position 32 to indicate that
the data is continued in the GENERATOR field of the next record.
If the host does not ask for XID, an erroneous XID indication
(required for compatibility reasons) must follow the station
address in the GENERATOR field.
E Page 27-10
27.5 "CLUS" Keyboard Emulation Mapping
27.5.1 "ASYN" keyboard mapping (Terminal Type = ASYN)
When a VT100 is being used, the 3270 keyboard function are mapped as follows :
IBM KEY Equivalent VT100 IBM KEY Equivalent VT100

ENTER ENTER PF1 Esc 1
NEWLINE LINEFEED PF2 Esc 2
CLEAR CLEAR (HOME+SHIFT) PF3 Esc 3
CURSOR UP CURSOR UP PF4 Esc 4
CURSOR DOWN CURSOR DOWN PF5 Esc 5
CURSOR LEFT CURSOR LEFT PF6 Esc 6
CURSOR RIGHT CURSOR RIGHT PF7 Esc 7
FIELD TAB Esc CURSOR RIGHT PF8 Esc 8
BACK TAB Esc CURSOR LEFT PF9 Esc 9
ERASE TO EOF Esc Delete PF10 Esc 0
ERASE INPUT ESC CLEAR PF11 Esc -
TOGGLE INSERT MODE ESC O n PF12 Esc =
ERASE CHARACTER DEL PF13 Esc !
SYSTEM REQ (QUIT) ESC ' . PF14 Esc @
PF15 Esc #
F16 Esc $
PF17 Esc %
PF18 Esc ^
PF19 Esc &
PF20 Esc *
PF21 Esc (
PF22 Esc )
PF23 Esc _
PF24 Esc +
PA1 Esc ,
PA2 Esc .
PA3 Esc /
E Page 27-11
27.5.2 "ANSI" keyboard mapping (Terminal Type = ANSI)
When a VT100 is being used, the 3270 keyboard function are mapped as follows :
ANSI KEY Equivalent VT100 ANSI KEY Equivalent VT100

CLEAR Esc O M or Esc [ 2 J PA1 Esc O S
ENTER CR PA2 Esc O m
HOME Esc [ H PA3 Esc O l
LEFT Esc O D or BS PF1 Esc O q
RIGHT Esc O C PF2 Esc O r
UP Esc O A PF3 Esc O s
DOWN Esc O B PF4 Esc O t
FIELD TAB Esc Esc O C or Esc Esc [ C PF5 Esc O u
BACK TAB Esc Esc O D or Esc Esc [ D PF6 Esc O v
NEW LINE LF PF7 Esc O w
DELETE DEL PF8 Esc O x
ERASE EOF Esc DEL PF9 Esc O y
ERASE INPUT Esc BS or Esc Esc O M or Esc Esc [ 2 J PF10 Esc O P
TOGGLE INSERT Esc O n PF11 Esc O Q
PF12 Esc O R
PF13 Esc O p Esc O q
PF14 Esc O p Esc O r
PF15 Esc O p Esc O s
PF16 Esc O p Esc O t
PF17 Esc O p Esc O u
PF18 Esc O p Esc O v
PF19 Esc O p Esc O w
PF20 Esc O p Esc O x
PF21 Esc O p Esc O y
PF22 Esc O p Esc O P
PF23 Esc O p Esc O Q
PF24 Esc O p Esc O R
E Page 27-12
Alternative ANSI KEY

PA1
Equivalent VT100
Esc ,
PA2 Esc .
PA3 Esc /
PF1 Esc 1
PF2 Esc 2
PF3 Esc 3
PF4 Esc 4
PF5 Esc 5
PF6 Esc 6
PF7 Esc 7
PF8 Esc 8
PF9 Esc 9
PF10 Esc 0
PF11 Esc -
PF12 Esc =
PF13 Esc !
PF14 Esc "
PF15 Esc _ (Shift 3)
PF16 Esc $
PF17 Esc %
PF18 Esc ^
PF19 Esc &
PF20 Esc *
PF21 Esc (
PF22 Esc )
PF23 Esc _
PF24 Esc +
DUP Esc D
Double Right Esc >
Double Left Esc <
Reset Control-G
Attention Esc A
Print Esc P
Print Esc C
Sys Request Esc ` .
E Page 27-13
27.5.3 "VT22" keyboard mapping (Terminal Type = VT22)
When a VT220 is being used, the keyboard is the same as color VT100 (Config ANSI) except the
following input sequences replace the standard VT100 equivalents. All other sequences are as in VT100
(ANSI) mode :
VT220 KEY Equivalent VT100

ENTER ESC O M
NEWLINE 0D hexadecimal
FORWARD TAB TAB (09 hexadecimal)
CLEAR ESC [ 1 ~
INSERT ESC [ 2 ~
DELETE ESC [ 3 ~
RESET ESC [ 4 ~
ERASE INPUT ESC [ 5 ~
ERASE EOF ESC [ 6 ~
BACK TAB DEL (7F hexadecimal)
27.6 Modification de la table standard de conversion ASCII - EBCDIC
One or more MAC table records with the TAB function may be used in order to personalize the
(standard) ASCII - EBCDIC conversion table.
MAC table example:
CL∗∗ TAB NONE 3270 C131C239
CL∗∗ TAB NONE 3270 005B005D
The line must be above the PU lines in the MAC file.

The NAME should match the CLUS descriptor(s).
The SELECTOR field must contain the indicator 3270 (emulation 3270).
The GENERATOR contains one or more EBCDIC-ASCII translation pairs
• C131 translate EBCDIC« A » to ASCII« 1 », and vice-versa.
• C239 translate EBCDIC« B » to ASCII« 9 », and vice-versa.
• When the code EBCDIC code is « 00 », the associated ASCII code is ignored. The ASCII and
EBCDIC values between 00 and 1F (hexadecimal) must not be used.
• 005B code ASCII 5B is ignored.
• 005D code ASCII 5D is ignored.
E Page 27-14
28. TYPE/ MAP descriptor
28.1 MAP concentration function
The MAP concentration function is used in the IBM environment when, in particular, the Megapac is used
as a "gateway" between a "DLC termination", "X.25" or "SDLC/QLLC" link and a host computer
conforming to IBM's SNA architecture rules.
The MAP concentration function offers the following advantages:
• lower running costs for a commercial "serial" link;
• reduction of the number of line drivers required in the communication front-end;
• reduction in the interval between two R/R commands with the P bit at 1 ("polling time"), the host
seeing only one PU;
• flexible network extension;
• multiplicity of "source" or downstream protocols (machine side), for example DLC, X.25, SDLC/QLLC,
for the same upstream virtual circuit (host side).
A number of MAP functions can be implemented in one Megapac.
TYPE/ MAP descriptor
E Page 28-1
28.1.1 Role of the MAP concentration function
Through this concentration function, the Megapac acts as a cluster controller emulating an IBM PU2.0.
Figure 28-1 shows a Megapac used as a "gateway" between a set of machines connected to a token ring
network and a host computer:
• Without MAP concentration function. In this case each machine monopolises a virtual circuit of the
serial link.
• With the MAP concentration The information relative to two machines is concentrated onto
function. the same virtual circuit of the "serial" link.
Token Ring MEGAPAC
Virtual channel Virtual channel

for for
station n°1 station n°2
Station n°1 Station n°2 Host

computer
DLC without MAP
Token Ring MEGAPAC
Virtual channel
for
station n°1 and n°2
Station n°1 Station n°2 Host

computer
DLC with MAP
Figure 28-1 Gateway Megapac with or without MAP function
E Page 28-2
Figure 28-2 shows the operation performed by the MAP function:

• each of the downstream stations (indicated by the IBM acronym PU) (downstream because they are
downstream from the Megapac seen from the host computer) support several applications (indicated
by the IBM acronym IU);
• the MAP function concentrates the different application supported by the downstream stations onto a
single virtual circuit;
• the host computer "sees" only one station.
STATION (PU) n°1

Downstream Stations (PU)
Application (LU) A and downstream applications (LU)
Application (LU) B
DLC
STATION (PU) n°2
Application (LU) C
Token MEGAPAC
Ring with
Application (LU) D
MAP FONCTION
Application (LU) E
only one
virtual channel
STATION (PU) n°3

Upstream APPLICATIONS
Application (LU) F
Application (LU) n°2
Upstream Stations (PU) Application (LU) n°5

(only one PU for the host)
Host
Computer
Figure 28-2 Gateway Megapac and the MAP function
Conclusion: the MAP function concentrates several downstream stations onto a single upstream station
E
(upstream because it is upstream of the Megapac). If it is used, the PROVIDE XID/ parameter of the
logical resource must be set to YES.
TYPE/ MAP descriptor Page 28-3
28.1.2 MAP concentration function operating principle
The MAP function is based on a "MAP" type virtual descriptor. Figure 28-3 is a block diagram of the
MAP function.
The descriptor is "virtual" in that, unlike a conventional link descriptor, it is not attached to any one
equipment item, like an interface board, for example. For the same reasons, the term "virtual resource"
is also used. The Megapac man/machine language disregards this distinction.
RESOURCE RESOURCE MAP n°3

DRC MASK/ RVM3 NAME/ RVM3
LINK
RESOURCE MAP n°2
TYPE/ QLLC
NAME/ RVM2
RESOURCE
RESOURCE MAP n°1
DRC MASK/ RVM2
NAME/ RVM1
LINK
TYPE/ X.25
RESOURCE MAP N°0

RESOURCE
NAME/ RVM0
DRC MASK/ RLX0
DRC MASK/ RVM1
LINK VIRTUAL DESCRIPTOR

TYPE/ DLC NAME/ DVMP
TYPE/ MAP
Token
Ring
RESOURCE
NAME/ RLX0
LINK
TYPE/ X.25
"SERIAL" LINK
TO THE HOST COMPUTER:
ONLY ONE VIRTUAL CIRCUIT USED
E
Figure 28-3 Block diagram of the MAP concentration function
• a link descriptor is assigned to each downstream station. In the case of a token ring, the Token-Ring
interface board supports a DLC link descriptor for each station connected to the ring and affected by
the DLC function;
• the single logical resource attached to each link descriptor is associated by its DRC MASK with an
MAP virtual resource which must have a number other than zero;
• all virtual resources with a number other than zero are concentrated on to virtual resource number
zero;
• MAP virtual resource number zero is associated by its DRC MASK with a logical resource (X.25
logical channel) of the "serial" link.
Virtual resource number zero has a special role, which means that its parameter settings are different
from those of the other virtual resources.
28.1.3 Using the MAP function
Add a buffer for each MAP function to the "TERMINAL EMULATION BUFFERS/" parameter of the BASE
system descriptor.
Method:
1. define the number of LUs available and their numbers at host level. Their numbers must be
consecutive and between 2 and 254 (column 1);
2. for each downstream station, define the number of LUs to be processed and their numbers (column
2). Their numbers must be consecutive and between 2 and 254. The total number of downstream
LUs, for all downstream PUs is the same as the number of upstream LUs. In the example, this total is
15 LUs;
3. for each virtual resource, define the LU TOTAL/ parameter which represents the number of
consecutive upstream (or downstream) LUs allocated to the downstream station associated with the
virtual resource (column 5). In the example, the number of upstream LUs allocated to station number
1 is 3;
4. for each virtual resource, define the LU BASE/ parameter which represents the number of the first
upstream LU assigned to the downstream station associated with the virtual resource (column 3). In
the example, this number appears in bold and is equal to upstream LU number 9 for station number 3;
5. for each virtual resource, define the LU OFFSET/ parameter (column 4):
• calculate the difference "D" = LU BASE - the number of the first downstream LU of the station
associated with the virtual resource. In the example, this number is underlined and the
difference is zero for stations 1 and 2 because the upstream and downstream LUs have the
same numbers;
• if this difference "D" is positive, LU OFF-SET = D. In the example, this is the case for station
number 3;
• if this difference "D" is negative, LU OFFSET = 256 -IDI. IDI is the absolute value of D and is
a positive number. This calculation is used to express the offset in the form of a "zeros
complement on eight bits". In the example, this is the case for station number 4.
E Page 28-5
E Offset
calculation
col. 1
col. 2 col. 3 col. 4 col. 5 col. 6
UPSTREAM DOWNSTRM VIRTUAL RESOURCE ASSOCIATED

PU PU n° 1 WITH DOWNSTREAM PU n° 1
UPSTREAM DOWNSTRM LU LU LU Offset
LU NUMBER LU NUMBER BASE OFFSET TOTAL COMMENTARY
n° 2 n° 2 LU OFFSET =
n° 3 n° 3 2 0 3 LU base - n° of 1st
downstream LUl =
n° 4 n° 4 2 (col 3) - 2 (col 2) = 0
DOWNSTRM VIRTUAL RESOURCE ASSOCIATED

PU n° 2 WITH DOWNSTREAM PU n° 2
DOWNSTRM LU LU LU Offset
LU NUMBER BASE OFFSET TOTAL COMMENTARY
n° 6 n° 6 5 0 4 LU base - n° of 1st
downstream LUl =
n° 7 n° 7 5 (col 3) - 5 (col 2) = 0
n° 8 n° 8

n° 10 n° 7 9 3 4 LU base - n° of 1st
downstream LUl =
n° 11 n° 8 9 (col 3) - 6 (col 2) = 3
n° 12 n° 9

n° 13 n° 17 Difference "D" =
n° 14 n° 18 13 252 4 LU base - n° of 1st
downstream LUl =
n° 15 n° 19 13 (col 3) - 17 (col 2) = - 4
n° 16 n° 20 LU OFFSET = 256 - 4 = 252
E
Figure 28-4 Example of calculating the MAP function offset
The three parameters LU BASE/, LU OFFSET/ and LU TOTAL/ define the mapping between the
downstream PU/LUs and the LUs of the upstream PU. They require a preparation and certain additional
explanations, illustrated by an example presenting the different possible situations. Refer to Figure 28-4
in which the six columns can be described as follows:
col. 1 assignment of upstream LUs and upstream PU;

col. 2 assignment of downstream LUs for each of the four downstream PUs (as in the
example);
col. 3, 4, 5 LU BASE/, LU OFFSET/ and LU TOTAL/ parameters of each virtual resource
associated with a downstream station;
col. 6 detailed calculation of the LU OFFSET/ parameter.
28.2 "MAP" descriptor configuration parameters

Name Settings
NAME XXXX 4 characters.
MAP virtual descriptor name.
TYPE MAP
CHANNELS 0 to 4096 Represents the number of virtual resources connected to the
MAP virtual descriptor.
The ("CHANNELS"-1) setting defines the number of
machines (PU) concentrated by the MAP function. The
offset of 1 is due to MAP resource n°0.
For example, if three machines are concentrated, set it to 4.
POLL INTERVAL 30 by default The MAP descriptor remains « passive » during this time (in
(0 to 127) second) after a Boot, a Restart, etc...
This timer allows to guarantee a waiting time before the
restoring of the connection with the resource « 0 ».
E Page 28-7
28.2.1 Parameters for MAP virtual resource N°0

Name Settings
Name of MAP resource n° 0.
This name is used in the MAC table.
DRC MASK .... 4 characters.
Normally "...."
Name of the resource associated with the X.25 link
descriptor and used for the virtual circuit linking to the host
computer.
CIRCUIT TYPE CALL The Megapac sends the X.25 call request packet to the host
computer. The STAT function can be implemented.
BUFFERS By default = 2 Setting determining the number of buffers available to this
resource.
MODE NONE Unused.
CALL PRIORITY 0 Calling line priority (CP > = RP).
RESOURCE PRIORITY 0 Called line priority.
LU BASE 0 to 255 Number of first LU defined in the NCP.
LU OFFSET 0 to 255 Offset of "0" for MAP(0).
LU TOTAL 0 to 255 Number of LU(s) defined in the NCP.
INTERLOCK BIND NO Not used for resource MAP(0).
MAC table

name of PU NONE CC,NNNN
resource
MAP(0)
CC cluster station address

NNNN XID used to communicate with the primary station
E Page 28-8
28.2.2 Parameters for MAP virtual resources N°>0

Name Settings
This name must match the DRC MASK of the logical
resource attached to the physical descriptor of the machine
(PU) concerned.
DRC MASK .... Not used.
CIRCUIT TYPE SVC+OUT Does not send call request packets.
BUFFERS By default = 2 Setting determining the number of buffers available to this
resource.
MODE NONE Not used.
CALL PRIORITY 0 Calling line priority (CP > = RP).
LU BASE 0 to 255 Name of first upstream LU assigned to the downstream
machine (PU) associated with the virtual resource.
0 and 1 must not be used.
LU OFFSET 0 to 255 Difference between BASE LU (previous parameter) and the
number of the first LU downstream of the machine (PU)
associated with the virtual circuit;
- if the difference "D" is positive,
LU OFFSET = D
- if the difference "D" is negative, the offset is in the form of
"zero complement on 8 bits" based on the following
calculation:
LU OFFSET = 256 - IDI.
IDI representing a positive value.
LU TOTAL 0 to 255 Number of consecutive upstream LU attached to the
downstream machine (PU) associated with the virtual
resource.
INTERLOCK BIND NO If a machine (PU) is disconnected.
- if the LU is active and connected to the host computer, an
LU STAT and then a NOTIFY are sent to the host computer;
- if the LU is active without being connected, an LU NOTIFY
is sent.
YES If a machine (PU) is disconnected:
- if the LU is active and connected to the host computer, an
LU UNBIND and then a NOTIFY are sent to the host
computer;
- if the LU is active without being connected, an LU NOTIFY
is sent.
E Page 28-9
E Page 28-10
29. TYPE/ DLC and EDLC descriptor
29.1 DLC gateway function
DLC (Data Link Control) is the data link protocol mainly used by IBM in the System Network Architecture
(SNA). It is used in particular to provide the link between 3270 cluster controllers and S/370 computers.
The protocol is physically supported by a token ring or a Ethernet Lan . Approximately, it embraces
standards 802.5 (Token Ring) or 802.3 (Ethernet) of the MAC sub-layer and 802.2 of the LCC sub-layer
in level 2 of the OSI model (LLC2).
In the DLC termination function, the Megapac is connected between the local token ring and the host
computer, either directly or via another Megapac linked to the previous one by a serial link.
Token MEGAPAC
Ring
Station n°1 Station n°2

HOST
Figure 29-1 DLC gateway function
TYPE/ DLC and EDLC descriptor
E Page 29-1
29.1.1 DLC without MAP concentration
Procedure:
• a station sends a frame over the ring,
• the link descriptor associated with that station (DEST ADDRESS/ station number) sends the frame to
the single logical resource to which it is attached,
• the DRC MASK of the logical resource switches the call to the logical resource attached to the X.25
link descriptor,
• if the virtual circuit between the Megapac and the host computer is not set up, the resource (X.25) is
used a search criterion in the X.25 table to supply the called line address needed for the X.25 call
request packet; a call request packet is sent to the remote computer to set up this circuit (logical
resource CALL+PCV). The frames are then encapsulated in X.25 data packets.
RESOURCE MEGAPAC
NAME/ RLT2
DRC MASK/ RLX2 X.25 Table
input output
LINK
RLX1 address 1
RLX2 address 2
NAME/ DLT2
TYPE/ DLC
DEST. AD./
222222222222
RESOURCE
RESOURCE 1
NAME/ RLT1
DRC MASK/ RLX1 NAME/ RLX2
LINK RESOURCE 0
NAME/ DLT1 NAME/ RLX1

TYPE/ DLC
DEST. AD./ LINK
111111111111
TYPE / X.25
Token Virtual channel

Ring for
station n°1 Virtual channel
for
station n°2
Note: The MAC table is not used.
E
Figure 29-2 Setting up two virtual circuits in the Megapac
TYPE/ DLC and EDLC descriptor Page 29-2
29.1.2 DLC gateway and MAP concentration
The gateway function can be used with MAP concentration mode.

The function of the DLC gateway with MAP concentration is the same as the previous case, except for
the role of the DRC MASK.
In this case, the DRC MASK of the resources (DLC) switches a virtual resource of the MAP virtual
descriptor.
MEGAPAC RESOURCE 2
RESOURCE
NAME/ RVM2
NAME/ RLT2
DRC MASK/
DRC MASK/ RVM2
LINK RESOURCE 1
NAME/ DLT2 NAME/ RVM1

TYPE/ DLC DRC MASK/
DEST. AD./
222222222222 RESOURCE 0
NAME/ RVM0
DRC MASK/ RLX0
RESOURCE
VIRTUAL DESCRIPTOR
NAME/ RLT1
TYPE/ MAP
DRC MASK/ RVM1
LINK
NAME/ DLT1
TYPE/ DLC
RESOURCE
DEST. AD./
111111111111
NAME/ RLX0
LINK
X.25 Table TYPE/ X.25

input output
RLX0 address 0
Token
Ring
Virtual channel
for
stations n°1 and n°2
Note: The MAC table is not used.
Figure 29-3 Virtual circuit setup in the Megapac
E Page 29-3
E
29.2 XID interchanges
29.2.1 Gateway with one interchange (transparent)
In this mode, the station takes the initiative to set up the data link with the Megapac.
The Megapac transmits transparently:
• to the station, the XID command sent by the host computer,
• to the host computer, the XID SNA response sent by the station.
These interchanges are repeated for each station connected to the ring.
Token
Station MEGAPAC Host
Ring
TEST Command
TEST Response
CALL
1
CALL ACCEPT X.25 channel
setup
Q. XID Command
XID Command
XID Response 2
XID
XID SNA Response exchange
Q. XID SNA Response
Q. SNRM
SABME
3
UA - SDLC link
- LLC2 link
Q. UA setup
ACT PU
4
+RSP SNA
exchange
Figure 29-4 Gateway with one interchange
MAC table
E
DLT1 XID NONE TRANSPARENT
TYPE/ DLC and EDLC descriptor Page 29-4
29.2.2 Gateway with two interchanges
In this mode, the Megapac takes the initiative to set up the data link with the station.
The content of the SNA XID command that the Megapac transmits to the host computer depends on:
• the MAC table identification record,
• the PROVIDE XID/ parameter of the logical resource.
These interchanges are repeated for each station connected to the ring.
Token
Station MEGAPAC HOST
Ring
TEST Command
TEST Response
CALL
1
X.25 channel
CALL ACCEPT setup
XID Command
XID Response
2
XID SNA Response LLC2 link setup
station-Megapac
SABME
UA
Q. Command XID
Q. Response XID SNA 3

LLC2 link setup
Q. SNRM Megapac-computer
Q. UA
ACT PU
4
+RSP SNA
exchange
Figure 29-5 Two interchange gateway

MAC table

RLT1 XID NONE xxxxxxxxxxx1
RLT2 XID NONE xxxxxxxxxxx2
E Page 29-5
29.3 « DLC / EDLC » descriptor configuration parameters

Name Settings
NAME up to 4 char. Link descriptor name.
TYPE DLC DLC termination type operation with a Token Ring.
EDLC DLC termination type operation with a Ethernet Lan.
NEW PHYSICAL YES On an Ethernet or Token Ring link, the first descriptor using
INTERFACE this link must be NPI=YES.
(NPI) By default = NO The other descriptors using the same Ethernet or Token Ring
link must be NPI=NO.
CHANNELS 0 to 4096 In DLC mode, there is only one logical resource for each link
By default = 1 descriptor.
DESTINATION ADDRESS nnnnnnnnnnnn 802.5 destination address of the equipment connected to the
1 to 12 char. ring (a station, for example), which is "managed" by the DLC
link descriptor with respect to the host computer.
DSAP 0 to 254 Destination Service Access Point
For IBM, the reserved SAP range in increments of 4
default setting 4
possible settings: 4 - 8 - 12 - 16 - 20 - ... - 248 - 252
SSAP 0 to 254 Source Service Access Point:
as DSAP
OPTIONS/ SRCE Source Routing
With this option, the Megapac transmits alternately test frames
with and without "source routing" information.
Without this option, the Megapac transmits test frames without
"source routing" information.
POLL Polling. Depends on the primary or secondary mode.
POLL is used only for the primary.
Transmission of an R/R command frame with the P bit at 1,
when no information frame has been received within a 100 ms
period.
INIT FRAME SABM+PBIT The Megapac is primary (UPSTREAM).
It sends SABME frames.
NONE The Megapac is secondary (DOWNSTREAM).
PACKET SIZE TRAN Transparent to packet size.
T1 2 to 80 For DLC, set 5.
By default = 30
T3 By default = 60 Does not concern DLC / EDLC descriptor.
TRIES 2 to 80 For DLC, set 10.
By default = 10
Other parameters can retain their default settings
E Page 29-6
29.4 « DLC / EDLC » resource configuration parameters

Name Settings
NAME 4 characters Logical resource name of the link descriptor to which it is
attached.
DRC MASK 4 characters WITHOUT MAP concentration
By default = . . . . Name of another logical resource, attached to the X.25 link
descriptor and associated with this logical resource.
WITH MAP concentration
Name of the MAP virtual resource associated with this logical
resource.
TERMINAL TYPE By default = ASYN By default, ASYN specifies VT100 terminal emulation. Do not
change.
STATION ADDRESS/ By default = 0B see below
FF The Megapac serves as a gateway between equipment
connected to the ring and the host computer.
Normal setting for this mode.
80 The Megapac serves as a concentrator between the equipment
directly connected to it and the ring.
00 The Megapac is connected by the "serial" link to another
Megapac which is itself connected to another ring.
PROVIDE XID/ NO 1) TRANSPARENT DLC MODE
This mode entails a special FUNCTION/XID record in the MAC
table, with TRANSPARENT in the SELECTOR field.
The Megapac analyzes and transmits the XID commands and
responses transparently.
2) DLC MODE without XID in MAC table
This mode is implemented by declaring no FUNCTION/XID
record in the MAC table for the logical resource.
The Megapac initiates setting up of the LLC2 data link and
sends only the SNA XID response received from the equipment
connected to the ring transparently.
E Page 29-7
E
PROVIDE XID/
(continued)
YES
1) DLC mode with XID in MAC table

This mode entails a FUNCTION/XID record in the MAC table for
each DLC type link descriptor using this mode.
The Megapac initiates the setting up of the LLC2 data link. It
sends to the host computer an SNA XID response constructed
from the MAC table.
2) DLC mode with MAP
This mode entails a FUNCTION/PU record in the MAC table. It
must include the XID function referring to MAP virtual resource
n°0.
The Megapac initiates the setting up of the LLC2 data link. It
sends the host computer a single type of SNA XID response
(referring to MAP virtual resource n°0) constructed from the
MAC table.
CIRCUIT TYPE CALL+STAT UPSTREAM
The Megapac sends the call request packet to the host
computer.
PVC+STAT DOWNSTREAM
The Megapac is connected to the stations.
OPTIONS/ NONE No options required.
BUFFERS/ Setting from 1 to Setting determining the number of buffers available to this
240 resource.

This parameter isn’t used for a resource being the addressee of
a call.
This parameter isn’t used for a resource at the origin of a call.
routing.
E Page 29-8
E
29.5 MAC table
NAME FUNCTION OPTIO SELECTOR GENERATOR

N
descriptor(s) STP,16 local MAC address
UTP,4 board
4 Mbit/s Token-Ring on RJ45 connector address on 12
UTP,16 hexadecimal characters
29.5.2 MAC Address of Ethernet board

∗ is allowed address in 12 hexadecimal
characters
E Page 29-9
E Page 29-10
30. TYPE/ SCOP descriptor
30.1 Introduction
The « SCOP » descriptor is used to install a DATA-SCOPE function in order to collect data on frames
exchanged by another descriptor. This function offers these local or remote operations:
• Real time observation of level 2 and 3 data for one or more link descriptors,
• Off-line data records,
• Summary formatting of recorded data.
To implement this, a SCOP type virtual descriptor must be defined with one single resource.
For SUB-TYPE/ XIO links, only level 3 data is accessible.
Note
• The configuration of a Megapac containing a « SCOP » descriptor cannot be downloaded to a
Megapac of which the software does not include the DATA-SCOPE function.
• The DATA-SCOPE function increases the operational load. In normal operation, it is recommended to
deactivate the DATA-SCOPE function.
Use
To use the DATA-SCOPE function, the « SCOP » descriptor resource must be called via an X25 call or
its equivalent (PAD X25, Reverse Telnet). Special commands can then be used to collect transmitted or
received frames on a given physical descriptor and on certain none-physical descriptors.
The SCOPE descriptor uses a buffer of 1024 entries in which the path records from the managed ports
are saved.
The DATA-SCOPE function is used to read this buffer, to format each record and to send records to the
terminal connected to the DATA-SCOPE.
DATA-SCOPE formatting is very concise. For ease of use, it is recommended to use appropriate
software on PC which interprets the received data.
TYPE/ SCOP descriptor
E Page 30-1
30.2 Configuration parameters of the « SCOP » descriptor
Parameter designation Range of values Meaning and scope of parameter

NAME up to 4 characters Name of link descriptor.
TYPE SCOP DATA-SCOPE function.
CHANNELS By default = 1 1 single resource in DATA-SCOPE mode.
IDLE DETECT TIME By default = 0 not used.
30.3 Configuration parameters of the« SCOP » resource
Parameter designation Range of values Meaning and scope of parameter

NAME 4 characters Name of the logical resource of the link descriptor to
which it is attached.
DRC MASK 4 characters
CIRCUIT TYPE CALL+STAT calling resource.
PVC+OUT+STAT called resource.
BUFFERS/ By default = 2 Value determining the number of buffers that can be used
by this resource.
MODE NONE not used.
CALL PRIORITY from 0 to 15 Caller priority ( CP >= RP ).
By default = 0
RESOURCE PRIORITY from 0 to 15 Called party priority.
By default = 0
30.4 Example of configuration
table X25
DA00 0 5555
NAME/ P800
DRC MASK/ . . . . NAME/ DA00
TERMINAL TYPE/ ASYN+X28F DRC MASK/ ....
OPTIONS/ MSGS BUFFERS/ 2
... ...
CALL 5555 NAME/ PS08 NAME/ DATA

TYPE/ TERM TYPE/ SCOP
SUB-TYPE/ SIO CHANNELS/ 1
...
...
Figure 30-1 DATA-SCOPE function configuration
E Page 30-2
E
30.5 « DATA-SCOPE » commands
All DATA-SCOPE commands are single characters preceded by the character « / », succeeded by
parameters (as appropriate), and terminated by a hard return.
All lines received that have incorrect syntax or do no begin by « / » are ignored.
30.5.1 Port monitoring
Command Meaning Example

/S or /s Activates the record function for the specified link descriptor. /SPS01
The simultaneous analysis of several link descriptors is possible.
This command only permits recording of send or receive frames of the
descriptor specified in the DATA-SCOPE buffer.
/T or /t Deactivates the record function for the specified link descriptor. /TPS01
This command only stops recording of send or receive frames of the specified
descriptor.
30.5.2 Continuous display

/C or /c Activates the continuous display mode. /C
Records pass via the DATA-SCOPE buffer before being sent to the PC. Records
send to the PC are not saved in the DATA-SCOPE buffer. The buffer is
managed as a cyclical FIFO.
/X or /x Deactivates the continuous display mode. /X
Records are made in the buffer without being sent to the PC.
30.5.3 Dump read mode

/B or /b Activates dump read mode. /B
Records present in the buffer are sent to the PC then display is discontinued.
The buffer contents are saved.
30.5.4 Buffer reset

/F or /f Deletion of buffer and activation of the record function for the monitored /F
descriptors.
This command is recommended when connecting to the SCOP descriptor
resource.
E Page 30-3
E
30.6 Observed records
The example below shows the format of records sent to the PC. In this example:
• PS03 is a TYPE/ NFRM link on XIO card (Frame Relay).
• PS04 is a TYPE/ X25 link on XIO card.
• PS06 is a TYPE/ X25 link on SIO card.
• ETHR is a TYPE/ IP link.
• ETHX is a TYPE/IPX link.
->PS064134 1 0 0 100000000000000020361
->PS064135 1 0 0 1000000000000000501641002A1
<-PS064135 1 0 0 100000000000000020161
->PS034135 1 0 0 100000000000000064AC1641002A1
<-PS034135 1 0 0 1000000000000000348C161
->PS03414A 1 0 0 1000000000000009E4AC1661002A845000098355C0000401136D0870F000B870FFFFF020802080084
<-PS04414A 1 0 0 1000000000000009B1002A845000098355C0000401136D0870F000B870FFFFF020802080084000002
<-PS03414A 1 0 0 100000000000000064AC1861002A1
->PS03414A 1 0 0 1000000000000000348C181
->PS06414B 1 0 0 1000000000000009D01661002A845000098355C0000401136D0870F000B870FFFFF02080208008400
<-PS06414B 1 0 0 1000000000000000503861002A1
->PS04414B 1 0 0 100000000000000031002A1
->PS06414B 1 0 0 100000000000000020381
->PS034163 1 0 0 1000000000000000E00010308007595010100030265CE
<-PS034163 1 0 0 1000000000000001300010308007D950101000302CF65070312E082
<-PS034166 1 0 0 1000000000000003248C10300800000008137FFFF0028000014141414FFFFFFFFFFFF045314141414
->PS034195 1 0 0 1000000000000000E00010308007595010101030266CF
<-PS034195 1 0 0 1000000000000000E00010308007D950101010302D066
->PS034196 1 0 0 1000000000000003248C10300800000008137FFFF0028000015151515FFFFFFFFFFFF045315151515
->PS0341C7 1 0 0 1000000000000000E00010308007595010100030267D0
<-ETHX41F6 000000000000003EFFFFFFFFFFFF0080020012558137FFFF003000000D0D0D0DFFFFFFFFFFFF0453
->PS0341F9 1 0 0 1000000000000000E00010308007595010101030268D1
<-PS0341F9 1 0 0 1000000000000000E00010308007D950101010302D268
->PS03422B 1 0 0 1000000000000000E00010308007595010100030269D2
<-PS03422B 1 0 0 1000000000000001300010308007D950101000302D369070312E082
<-ETHR424C 0000000000000092FFFFFFFFFFFF008002001255080045000084158D0000401156C1870D0001870D
<-PS064260 1 0 0 1000000000000006103881002AA4500005C158D0000401156D9870F000D870FFFFF02080208004800
For the last record on the PS06 link (X25 on SIO card):
-> Direction indicator ( -> Megapac input, <- Megapac output ).
PS06 Link descriptor name.
4260 Clock hexadecimal value in 1/10ths of a second.
1001 Status of link descriptor interface signals.
0000 CRC error total.
0000 Number of rejected frames.
0000 Number of frames having needed to be retransmitted.
E
0061 Frame length (hexadecimal).
03881002AA4500... First 32 bytes of the frame.
TYPE/ SCOP descriptor Page 30-4
31. Statistics
The "STAT" command displays variable status information and statistics for a link descriptor or a logical
resource. On the display, the value of each variable is shown opposite the name of the variable.
According to the type of link, physical or virtual, the variables are different.
Statistics
E Page 31-1
31.1 "BASE" descriptor statistical report
When you run "STAT" for the "BASE" descriptor, the display contains the following information:
VERSION Installed software version number.

SIG1 Type of CPU (CPUC, CPUE, ESL, ES1, CPUV, 6840, V101)
RESTART TIME Time and date of the last system BOOT.
MAXIMUM PACKET SIZE System's maximum packet size.
BUFFER POOL MAX Maximum number of buffers in the system.
BUFFER POOL NOW Number of buffers currently available.
BUFFER POOL LOWEST Minimum value reached by the buffer pool.
BUFFER POOL EMPTY Number of times that the buffer pool has been insufficient for the system.
BUFFER THRESHOLD When the pool of available buffers is ≤ this value, the flow control
function tries to regulate the system.
MEMORY SIZE (K BYTES) Memory capacity addressable by the system (in Kbytes).
DATA FRAMES IN Number of information frames received.
DATA FRAMES OUT Number of information frames sent.
DATA FRAME RATE IN Number of information frames received per second.
DATA FRAME RATE OUT Number of information frames sent per second.
TOTAL CALL SET-UPS Total number of connections set up.
CURRENT CALLS Number of connections set up.
RETRANSMISSIONS Number of frames requiring a retransmission.
REJECTS Number of frames rejected.
TOTAL TRANSPORT CALLS Total number of transport connections.
CURRENT TRANSPORT CALLS Number of active transport connections.
RUN STATUS Software running in PROM or in RAM.
BASE: stat
VERSION/ 600B SIG1/ CPUE RESTART TIME/ 9:34:21 6/1/99

MAXIMUM PACKET SIZE/ 512 BUFFER POOL MAX/ 862
BUFFER POOL NOW/ 616 BUFFER POOL LOWEST/ 589
BUFFER POOL EMPTY/ 0 BUFFER THRESHOLD/ 40
MEMORY SIZE (K BYTES)/ 832 DATA FRAMES IN/ 544
DATA FRAME RATE OUT/ 0 TOTAL CALL SET-UPS/ 1
CURRENT CALLS/ 1 RETRANSMISSIONS/ 0
REJECTS/ 0 TOTAL TRANSPORT CALLS/ 0
CURRENT TRANSPORT CALLS/ 0 RUN STATUS/ PROM
BASE:
Statistics
E Page 31-2
31.2 Alphabetical list of variables in a "Statistics" report
When you run "STAT" on a link descriptor or associated resources, the display contains the information
listed below:
Some variables reflect parameters specified in the descriptor or the resources of the link concerned.
ACTIVE MULT Reserved use (DATA mode)

ARP REQUESTS IP, TIP Number of ARP procedures received by the Megapac.
RECEIVED
ARP REQUESTS IP, TIP Number of ARP procedures sent by the Megapac.
SENT
ARP RESPONSES IP, TIP Number of ARP procedures sent by the Megapac and
RECEIVED acknowledged by a remote station.
BIND ACTIVE YES CLUS The LU of the Megapac node has responded positively
to a BIND command.
The LU of the Megapac node has not received a BIND
command or has responded negatively.
BREAKS RECEIVED TERM Number of BREAK signals received from the terminal.
BUFFERS resource Settings configured in the resource.
CALL PRIORITY resource Settings configured in the resource.

CALLS RECEIVED Decimal value link Total call request packets received over the link.
CALLS SENT Decimal value link Total call request packets sent over the link.
CAUSE resource Content of the clearing calls field belonging to the last
clear request packet sent.
CIRCUIT TYPE resource Settings configured in the resource.
CLEARS RECEIVED Decimal value link Total clear request packets received over the link.
CONNECTED TO (Link, resource resource Identifies the link and the logical resource on which the
number) connection is set up.
CONNECTION NAME name of V25B Name allocated to the V25Bis resource when it is
resource active.
CRC ERRORS Decimal value link Total CRC errors detected on the link.
CUR RX SEQ Decimal value NFRM Points out the LMI sequence number received on a
Frame Relay link.
CUR TX SEQ Decimal value NFRM Points out the LMI sequence number transmitted on a
Frame Relay link.
CURRENT CALLS Decimal value link Number of active calls at the time of the enquiry.
Statistics
E Page 31-3
E
DATA FRAME RATE
IN
Decimal value link Number of information frames received per second.

The sampling time is five seconds but may increase
according to the load on the system.
DATA FRAME RATE Decimal value link Number of information frames sent per second.
OUT
The sampling time is five seconds but may increase
according to the load on the system.
DATA FRAMES IN Decimal value link Total information frames received.
DATA FRAMES OUT Decimal value link Total information frames transmitted.
DATA IN Decimal value link Total data characters received.
DATA OUT Decimal value link Total data characters transmitted.
DCE RX SEQ Decimal value NFRM LMI order number for Request received messages.
DCE TX SEQ Decimal value NFRM LMI order number for Ack send messages
DE Decimal value NFRM Received frame number with DE bit set.
DESTINATION Transport Identifies the transport connection in the remote
REFERENCE transport entity.
Note that this reference is never associated with a
main transport context block (MASTER).
DIAGNOSTIC resource Content of the diagnostic code field belonging to the
last clear request packet sent.
EIA Ø Ø Ø Ø resource EIA/ specifies the states of the signals at the interfaces
of the SIO and XIO boards for X.25, HDLC, QLLC,
NRMR and PPP descriptors.
The format is: EIA/ Ø Ø Ø Ø
Each Ø represents a signal at 1 (active) or a signal at
0 (inactive).
Interpretation depends on the interface's operating
mode (DCE or DTE).
Each Ø gives in turn the state of:
Mode output input input output
DTE RTS CTS DCD DTR
DCE DCD DTR RTS CTS
DCD resource MUX or TERM link descriptor.
Either circuit 108 is ON.
Or circuits 108 and 105 are ON.
DOWN resource The "link" level is inactive.
CLS resource This resource has been closed. (CLOS command).
Statistics
E Page 31-4
E
ERROR
MULT Reserved use (DATA mode)
FRAME SEQ NORM link Sequence numbers from 0 to 7.

EXT Sequence numbers from 0 to 127.
FRAMING ERRORS TERM Number of characters received with no STOP BITS.
The Megapac inserts a "#" character at each point
concerned.
HELP NUMBER resource Settings configured in the resource.
IDENTITY PPP When LINK STATE is not OPEN:

IDENTITY depends on the state of the "Point-to-point
protocol" link.
PPP When LINK STATE = OPEN,
and PROTOCOL STAT is not OPEN:
IDENTITY depends on the state of the "Point-to-point
protocol" protocol.
PPP In other case, IDENTITY has no significance.
INPUT OVERRUNS TERM Number of input characters lost following a node
overload.
The Megapac inserts a "%" character at each point
concerned.
INTERRUPTS Decimal value link Total interrupt request packets received over the link.
RECEIVED
K LEVEL 2 SDLC, SDLC frame window size.

QLLC
Normally, this is set to 7.
Statistics
E Page 31-5
E
LCGN
LEVEL 3 STATE
from 0 to 15 link
resource
Logical resource group number specified in the link
descriptor.
State of the logical resource (level 3).
DISC resource Disconnected.
DATA resource Data transfer.
CALL resource Waiting for a call accepted packet.
CLS resource Waiting for a clear confirmation packet.
RESE resource Reset indication packet received.
REST resource Logical resource number 0 only.
Restart request packet sent.
CLR resource Clear request packet received.
INIT resource Connect request generated.
LINK STATE PPP State of the "point-to-point protocol" link
OPEN PPP Open.
ACKS PPP Acknowledgement sent.
ACKR PPP Acknowledgement received.
REQS PPP Request Configure Sent.
STPI PPP Stopping.
CLSI PPP Closing.
STOP PPP Stopped.
CLOS PPP Closed.
LMI NFRM Internal qstate of the robot managing the
« Local Management Interface » of a Frame Relay link.
DOWN NFRM The MegaPAC has received an LMI frame including an
information element about the DLCI state making a
previously active PVC inactive.
UP NFRM The MegaPAC has received an LMI frame including an
information element about the DLCI state making a
previously inactive PVC active.
LOCAL LOOP NONE link The local V.54 tests are not configured or inactive.
STATUS
PASS link The local V.54 tests are correct.
FAIL link Local V.54 tests failed.
LU ACTIVE YES CLUS The LU node of the Megapac has responded positively
to an ACTLU command.
NO CLUS The LU of the Megapac node has not received an
ACTLU command or has responded to it negatively.
LU TYPE 0, 1, 2, 3 CLUS Type of session carried in the BIND command.
Statistics
E Page 31-6
E
MENU NUMBER
resource Settings configured in the resource.
NAME (N) Transport NAME represents the name of the transport context
block.
N is 0 when it is the MASTER block.
1 _ N _ 254 in the case of a block associated with a
particular transport connection.
NEWS NUMBER resource Settings configured in the resource.
NR Decimal value link Receive sequence number.
OFFSET MULT Reserved use (DATA mode)

OPTIONS Decimal value link Indicates the Option(s) specified in the link descriptor.
OUTPUT QUEUE Decimal value link Number of information frames awaiting transmission
LENGTH and stored in the output queue.
Statistics
E Page 31-7
E
PACKET SIZE
SDLC, QLLC Maximum size of a Megapac node block. It must be

greater than the maximum size of a frame that the
SNA host can transmit.
PACKETS TO ACK resource Number of unacknowledged packets.
Number of unacknowledged TPDU-DT (transport class
2 or 3).
PAD ENABLE resource Settings configured in the resource.
PARITY ERRORS TERM Number of characters received with a parity error.
PIGGY TYPE Soft Megapac ESL The junction interface is configured by the software.
JV24 Megafrad The junction interface is a V24 interface.
JX21 The junction interface is a V11/X21 interface.
JV35 The junction interface is a V35 interface.
+HX21 The junction interface is configured by the software,
and the V11/X21 module (piggy-back) is implemented.
+HV35 The junction interface is configured by the software,
and the V35 module (piggy-back) is implemented.
PNR resource P(R) (receive packet sequence number) of the last
packet received.
YR-TU (response sequence number) of the last TPDU-
AK received.
POLLS SDLC, QLLC Number of polls sent when the Megapac is the primary
PU.
Number of polls received when the Megapac s the
secondary PU.
PR resource P(R) (receive packet sequence number).
TPDU number of a received TPDU-DT (transport class
2 or 3).
PR (SENT) resource P(R) (receive packet sequence number) of the last
packet sent.
YR-TU (response sequence number) of the last TPDU-
AK sent.
PRIMARY STATION YES SDLC, QLLC The Megapac node is acting as an SDLC primary
station.
NO SDLC, QLLC The Megapac node is acting as an SDLC secondary
station.
Statistics
E Page 31-8
E
PROTOCOL
PROTOCOL STAT
PPP
PPP
Protocol carried by this resource.
State of the "point-to-point protocol" protocol
when LINK STATE = OPEN.
OPEN PPP Open.
ACKS PPP Acknowledgement sent.
ACKR PPP Acknowledgement received.
REQS PPP Request Configure Sent.
STPI PPP Stopping.
CLSI PPP Closing.
STOP PPP Stopped.
CLOS PPP Closed.
PS resource P(S) (send packet sequence number).
TPDU number of a send TPDU-DT (transport class 2
or 3).
QLLC STATE CLSD SDLC, The Megapac node has received a QDISC packet and
QLLC sent a QUA packet in response.
The SDLC port then acquires the DISC state.
CLSI SDLC, The Megapac node has sent a QDISC packet and is
QLLC waiting to receive a QUA packet.
FRMR SDLC, The Megapac node has received the QFRMR packet.
QLLC
INOP SDLC, Level 3 disconnection.
QLLC
OPEN SDLC, The level 3 connection is set up. The QSM and QUA
QLLC packets have been exchanged correctly.
OPNI SDLC, The Megapac node has sent the QSM packet and is
QLLC waiting to receive a QUA packet.
Statistics
E Page 31-9
E
RCV BECN
RCV FECN
Decimal value
Decimal value
NFRM
NFRM
Number of frames received with the BECN indicator on
a Frame Relay link.
Number of frames received with the FECN indicator on
a Frame Relay link.
REJECTS Decimal value link Total reject frames received.
REMOTE LOOP NONE link The remote V.54 tests are not configured or inactive.
STATUS
PASS link The remote V.54 tests are correct.
FAIL link Remote V.54 tests failed.
RESET CAUSE resource Content of the reset cause field belonging to a last
reset request packet sent.
RESET CAUSE resource Content of the reset cause field belonging to the last
RECEIVED reset indication packet received.
RESET DIAGNOSTIC resource Content of the diagnostic code field belonging to the
last reset request packet sent.
RESET DIAGNOSTIC resource Content of the diagnostic code field belonging to the
RECEIVED last reset indication packet received.
RESETS RECEIVED Decimal value link Total reset request packets received over the link.
RESOURCE resource Settings configured in the resource.
PRIORITY
RETRANSMISSIONS Decimal value link Total retransmissions over the link. (for send side)
RX SEQ Decimal value NFRM LMI order number received in the Ack messages.
RX SEQ LOST Decimal value NFRM Number of LMI messages lost (non received) on a
Frame Relay link.
RX SIZE resource Maximum receive packet size.
Maximum proposed size of a TPDU (transport class 2
or 3).
RX WINDOW resource Receive window size (level 3).
Initial credit CDT allocated to a transport connection by
the system.
Statistics
E Page 31-10
E
SDLC STATE ACTIVE
SDLC,
QLLC
SNRM and UA frames exchanged correctly.
When the Megapac node is the primary station, frames
with the P bit at 1 have not yet been sent.
When the Megapac node is the secondary station,
frames with the F bit at 1 have not yet been sent.
DISC SDLC, When the Megapac node is the primary station.
QLLC
The Megapac node sends a DISC command frame
with the P bit at 1, under the following situations:
Execution of the STOP command.
Receipt of a QDISC packet.
POLL SDLC, When it is the primary station, the Megapac node has
QLLC sent a frame with the P bit at 1.
When it is the secondary station, the Megapac node
has received a frame with the P bit at 1.
SNRM SDLC, When the Megapac node is the primary station.
QLLC
The Megapac node has sent an SNRM frame but has
not receive the UA frame.
SDLC TRANSMIT NORM SDLC, The Megapac node can send information frames.
STATE QLLC
NULL SDLC, The Megapac node cannot send information frames.
QLLC
RNR SDLC, The Megapac node has received an RNR frame.
QLLC
RTRY SDLC, The Megapac node is trying to retransmit an
QLLC information frame.
SESSION STATUS resource State of the resource when a connection is set up.
CALL resource Connect request generated.
DRI resource Input flow control active.
DRO resource Output flow control active.
TRAN resource Call set up has not involved the presentation service.
QUEU resource Queued until the resource selected is available.
STAT resource Queued.
A queue occupancy report has been requested.
PAD resource X.28 environment (PAD ENABLE).
DISC resource Before the call is cleared, the buffers containing data
are emptied.
Statistics
E Page 31-11
E
SIG1 CPUE
CPUC
ESL
BASE
descriptor
type « CPU_E » central processor unit
type « CPU_C » central processor unit
Megapac ESL or Megafrad » box
ES1 Megapac ES1 box
CPUV VME rack with « CPU_V » central processor unit
6840 VME rack with « 68040 » central processor unit
V101 VME rack with « CPU+DIS » central processor unit
STATE DISC link The link is in the "disconnected" state.
SABM link An SABM frame has been sent on a link reset.
SARM link An SARM frame has been sent on a link reset.
CLS link No response following transmission of a DISC frame.
DATA link The network is in the NORMAL state.
STOP link Use of STOP command. In this case, no information
frames can be exchanged until the link is reset.
BLKD link The network is in the BLOCKED state.
WAKE link The network is in the AWAKE state.
RESP link The network is in the RESPONSE state.
WAIT link The network is in the CONNECTION REQUESTED
state.
STATE DISC resource The logical resource is in the "Disconnection" state.
DATA resource Data transfer (call in progress).
BUSY resource Temporarily unavailable.
ADDR resource The resource is waiting for selection of the name of the
output logical resource.
ROUT resource The input logical resource is waiting for the output
logical resource to be assigned.
SETU resource The input logical resource is waiting for the call to be
set up to the output logical resource.
CALL resource Call set up to the output logical resource.
WAKE resource Transmission on the output logical resource (DRC
MASK).
MNGE resource Logical resource connected to network management
centre.
POST resource Data processed before transfer (e.g. PAD parameter
13).
SERV resource In presentation mode, awaiting composition of the
service name (eight characters) representing the
content of the NAME field.
Statistics
E Page 31-12
E
STATION ADDRESS
value
Hexadecimal TIP, TIPX MAC address assigned to the TokenRing board

installed in the Megapac.
This MAC address is specified by a PU record in the
MAC table.
STATION ADDRESS Hexadecimal LAN, ILAN, 802.3 MAC address of the Ethernet board installed in
value XLAN, IP, the Megapac.
IPX, CONS
SUB-STATE NORM link The network is in the NORMAL state (data frames).
REJ link Data frame received out of sequence. The network
sends a reject frame.
WAIT NFRM At the beginning of the control period, the local is
waiting for an « LMI » message.
ACTV NFRM During the control period, the local has received at least
1 « LMI » message.
IDLE NFRM At the end of the control period, the local hasn’t
received any « LMI » message from the remote.
Statistics
E Page 31-13
E
TERMINAL TYPE
THROUGHPUT Decimal value
resource
NFRM
Settings configured in the resource.
On a Frame Relay link, « THROUGHPUT » points out
the number of characters received during the last time
interval « Tc » during which the data flow is controlled.
TIMER Decimal value NFRM The MegaPAC carries out a control of the flow
transmitted on the DLCI during a period of time « Tc ».
TIMER points out the value of the period of time, in
second tenth.
TOTAL CALL SET- Decimal value link Total calls set up since a REST or DELE command
UPS was executed.
TOTAL CHARS IN Decimal value resource Total data bytes received.

TOTAL CHARS OUT Decimal value resource Total data bytes sent.
TOTAL FRAMES IN Decimal value resource Total information frames received, or
Total segments received
(SEGMENT ACCOUNTING = YES)
TOTAL FRAMES Decimal value resource Total information frames sent, or
OUT
Total segments sent
(SEGMENT ACCOUNTING = YES)
TRANSPORT Transport Name of routing identifying a transport context.
CONNECTION NAME
On set up of a transport connection:
at the level of the local MegaPAC (initializing the
transport connection), TRANSPORT CONNECTION
NAME represents the name of the destination resource
(remote TSAP);
at the level of the remote MegaPAC (receiving the
transport connection), TRANSPORT CONNECTION
NAME represents the first 4 charactersof the input
MAC recording GENERATOR field (with the TCAL
option).
TRIES Decimal value link Number of times that the current frame has been sent.
TX SEQ Decimal value NFRM LMI order number send in request messages.
TX SEQ LOST Decimal value NFRM Number of LMI messages without any answer, on a
Frame Relay link.
TX SIZE resource Maximum send packet size.
Maximum selected size of a TPDU (transport class 2
or 3).
TX WINDOW resource Send window size (level 3).
Initial credit CDT allocated by the remote system to a
transport connection.
TYPE X25, NFRM, link Indicates the "TYPE" of descriptor used.
PPP,
LAN, IP, IPX,
TIP, ROUT,
SDLC, DLC,
EDLC, MAP, etc
...
Statistics
E Page 31-14
E
VR
VR (SENT)
VS
Decimal value
Decimal value
Decimal value
link
link
link
Receive status variable (network).
Send sequence number.
Send status variable (network).
WINDOW MULT Reserved use (DATA mode)

WAIT Decimal value NFRM When a DLCI transmit many protocols with different
resource priority level, WAIT indicate the buffers numbers puted
back on this resource.
XID IDENTIFICATION Hexadecimal SDLC, This field contains the first 64 bytes of the XID
value QLLC interchange identification used.
This is supplied either by the Megapac node or
generated by the SNA host.
Statistics
E Page 31-15
Statistics
E Page 31-16
32. System messages
32.1 General format of a Megapac message
Time Date Name Text Suffix
Time hh/mm/ss
Date DD/MM/YY
Name Four alphanumeric characters identifying a link or a logical resource
Text Message generated by the Megapac node
Suffix Optional qualifier
There are 3 types of messages :

• The diagnostic messages : its are sent by default to EI00(0) resource,
• The connect / disconnect messages : its are sent by default to EI01(1) resource,
• The system messages : its are always sent to the first resource of EPCI descriptor.
In the following description :
• « R » indicates the diagnostic messages (REPORT),
• « S.S » indicates the connect / disconnect messages (SESSION STATISTICS),
• « SYS » indicates the system messages.
32.2 Connection and disconnection messages
Type TEXT / SUFFIX MEANING

S.S xxxx (nn) → yyyy (nnn) A virtual circuit is using:
• the input logical resource xxxx (nn),
• the output logical resource yyyy (nnn).
S.S xxxx (nn) ← (23 ; 189 ; 060 ; 1002) A clear request packet has been received from the output
resource.
The figures in brackets indicate from left to right:
• the number of packets received,
• the number of packets sent,
• the number of characters received,
E
• the number of characters sent.
System messages Page 32-1
32.3 Alphabetical list of "Megapac" messages
Type TEXT / SUFFIX Meaning

SYS When the Megapac is in PC program counter
« ABORT » state, in SR stack register
"BUS ERROR", etc., the
following status is displayed : ABORT, BUS ERR, ... content of system registers
STACK content of stack system
The latest "fatal error" data is saved on the Megapac E08-E15 equipped
with CPU-E, the Megabox-SL, Megapac ESL/Megafrad, and the
Megapac VME.
This data can be displayed via the DERR (Dump Error) command from
the configuration port.
Type TEXT / SUFFIX Protocol Meaning

R ADDRESS ERROR (b1) X25-N2 There is an error in the ADDRESS field of the received frame.
b1 is the hexadecimal value of the ADDRESS field:
if b1 is 01 or 03, the DTE/DCE configuration (ADDRESS
parameter) is incorrect.
if b1 is other than 01 or 03, there is a hardware or software
problem.
R ADDRESS ERROR NFRM On a FRAME RELAY link, the Megapac indicates that a frame
(HHHH) has arrived on an unconfigured DLCI number.
HHHH in hexadecimal character represents the DLCI. The
relevant bits are shown by the positions marked X below :
H1 H2 H3 H4
XXXX XX00 XXXX 0000
Most significant bit Low significant bit
R BAD FRAME TYPE (b1) X25-N2, The content of the COMMAND field in the received frame is
SDLC, corrupted.
QLLC, b1 is the hexadecimal value of the COMMAND/ field.
Token
Ring
R BAD FRAME TYPE b1 XLAN, The content of the "control" field in the received frame does not
CONS identify an LLC-PDU.
R BAD N(R) ILAN The Megapac received an acknowledgment (incorrect N(R) field)
concerning TPDUs that it has not sent.
R BAD N(R) b1 b2 X25-N2, A frame with an incorrect N(R) has been received.
SDLC, b1 is the COMMAND field of the incorrect frame.
QLLC
b2 is the value of the send and receive status variables of the
DTE or the local DCE.
The CMDR/FRMR response frame is sent to the DTE or to the
remote DCE.
R BAD P(K) X25-N3 A data packet has been received in which the content of the P(S)
field is greater than the value associated with the K LEVEL 3/
E
parameter of the line descriptor.
A reset request or indication packet is sent.
E
Type
R
TEXT / SUFFIX
BAD P(R) b1
Protocol
X25-N3
Transport
Meaning
A data packet has been received in which the content of the
P(R) field is incorrect (out of sequence).
R BAD P(S) b1 X25-N3 A data packet has been received in which the content of the P(S)
field is incorrect (out of sequence).
R BAD QLLC C-FIELD SDLC, A QLLC packet has been received in which the content of the
QLLC COMMAND field is corrupt.
R BAD TYPE/LENGTH X25-N3 A packet has been received with one of the following
(b1 b2 b3 b4) characteristics.
Its length is greater than the minimum length for this type of
packet.
The content of the "packet type identification" field has not been
accepted.
b1, b2, b3, b4 are the contents of the first four bytes of the
packet received.
Note: setting the parameters of the DIAG option is optional.
R BLOCKED X25-N2 One of the following situations may occur:
an RNR command frame has been received with the P bit set to
0 or 1,
an RNR response frame has been received with the F bit set to
0.
R BUFFER POOL EMPTY system All the system buffers are in use.
There are insufficient system buffers.
R BUFFER THRESHOLD system The number of buffers in the pool is equal to the BUFFER
REACHED: THRESHOLD/ parameter (BASE descriptor).
FLOW CONTROLLING The flow control function is trying to regulate the system.
R CALL X25-N3 Call request packet received.
Transport Note: the calling DTE address and the called DTE address
appear in the TEXT field.
SYS CHECKSUM IN MEMORY system A checksum error is detected in memory.
R CLEARED V25B A call in V25 node is cleared.
R D-CHANNEL STATUS: X25, Channel D initialization (reset) message from the T2 (30B+D)
T2B;T2A HDLC, primary access card.
PPP T2B and T2A take the values UP or DOWN.
T2B corresponds to the basic T2 port of the PRI-64 card
T2A corresponds to the T2 port of the "second T2" option.
SYS DEFAULTS USED system CRC error detected in the configurator.
(CHECKSUM) The system's default configuration is restored automatically.
SYS DEFAULTS USED (FLAG) system The system's default configuration is restored automatically.
R DISCONNECTED general Disconnection of a link.
R DM RESPONSE X25-N2, An unsolicited DM response frame has been received.
SDLC, The link is disconnected.
QLLC
R DOWN X25-N2, The maximum number of retransmissions (TRIES parameter) of
SDLC, an information frame has been exceeded.
E
QLLC The link is reset.
E
Type
R
TEXT / SUFFIX
DST-REF ERROR (bb .....
etc)
Protocol
ILAN
Transport
Meaning
On receipt of a TPDU, the content of the REFERENCE
DESTINATION field identifies a logical resource not belonging to
the link descriptor associated with the calling (or called)
transport service user concerned.
R ER TPDU (bb ..... etc) ILAN A TPDU ER has been received.
Transport This results from one of the following situations:
TPDU error,
content of the TPDU incorrect.
SYS ERROR The SAVE command displays an « ERROR » message when the previous
personalized configuration has not been erased.
Only with CPU-D or CPU-E, Megabox SL, Megapac ESL - Megafrad.
R ERROR (b1 b2) X25-N2 The level 2 XIO processor (MK 5025) generates this message
when an event message has been transferred by the Control and
Status register number 0.
R ERROR RECOVERY XIO T1.N2 time-out:
TIMEOUT board T1 is the interval (in tenths of a second) after which a frame is
retransmitted.
N2 is the maximum number of retransmissions of an information
frame before the link is reset.
R ERROR THRESHOLD general The number of CRC errors detected over the link is greater than
EXCEEDED the value associated with the ERROR THRESHOLD/ parameter
of the link descriptor.
R FRAME LENGTH < 2 X25-N2, A frame shorter than two bytes has been received.
Token
Ring
R FRAME LENGTH < 3 XLAN, An LLC-PDU shorter than three bytes has been received.
CONS
R FRMR b1 b2 b3 b4 X25-N2 A CMDR or FRMR response frame has been received.
other XIO Meaning
b1 Show the COMMAND field identifying a
CMDR/FRMR response frame.
b2 b1 Show the COMMAND field of the erroneous
frame generating transmission of an FRMR
response frame.
b3 b2 Show the value of the receive and send status
variables of the DTE or the remote DCE
b4 b3 contains an error code:
01 - the content of the COMMAND field is
incorrect,
03 - the content of the INFORMATION field is
not valid,
04 - the INFORMATION field is too long,
08 - N(R) incorrect.
b4 show the first byte of FCS frame.
System messages
E Page 32-4
E
Type
R
TEXT / SUFFIX
FRMR SENT b1 b2 b3
Protocol
X25-N2,
SDLC,
QLLC
Meaning
An FRMR response frame has been sent by the Megapac
(The XIO board does not supply this message).
b1 is the content of the COMMAND field of the incorrect frame
leading to the Megapac sending an FRMR response frame.
b2 is the value of the receive and sent status variables of the
DTE or the remote DCE.
b3 contains an "error" code:
• 01 - the content of the COMMAND field is incorrect,
• 03 - the length frame is incorrect,
• 04 - the INFORMATION field is too long,
• 08 - N(R) incorrect.
R I-FIELD TOO LARGE X25-N2, A frame has been received containing an information field larger
SDLC, than the standard Megapac buffer size.
QLLC,
HDLC
R INVALID GENERATOR CLUS In the MAC table, the PU record contains a field in which the
FOR PU content is incorrect.
R INVALID LENGTH FIELD XLAN, In the frame received, the "length" field contains a value
CONS (number of bytes) greater than the number of bytes occupied by
the LCC data.
R LCGN ERROR (b1) X25-N3 A packet has been received in which the "Logical channel group
number" field does not contain the value associated with the
LCGN/ parameter of the link descriptor.
b1 is the logical channel group number received.
Note: Setting the parameters of the DIAG option is optional.
R LCN TOO LARGE X25-N3 The number of the logical resource is incompatible with the
value associated with the LCGN/ parameter of the link
(b1 b2 b3 b4) descriptor.
b1 is the general packet format identifier (in hex).
b2 is the logical group resource number (in hex).
b3 and b4 are the value of the "Logical channel number" field of
the packet (in hex).
R LENGTH INDICATOR ILAN, In the frame received, the "length" field contains a value
ERROR Transport (number of bytes) greater than the number of bytes occupied by
the LLC data.
R LMI DOWN NFRM The « LMI »timer expired.
No answer to the LMI messages during the interval :
(KEEP ALIVE TIMER x POLL INTERVAL)
R LMI MODE ERROR NFRM MODE error.
« Status Enquiry » received in mode DTE, or
« Status Response » received in DCE mode.
R LMI RESTART NFRM The « LMI »timer expired.
The Megapac has received an LMI frame during the period
(enquiry or answer)
(KEEP ALIVE TIMER x POLL INTERVAL)
System messages
E Page 32-5
E
Type
R LMI:
TEXT / SUFFIX
ACTIVE PVC (HHHH)

Protocol
NFRM
Meaning
(DTE only). An LMI message from the DCE indicates that a
previously inactive PVC has become active.
H1 H2 H3 H4
∅∅∅∅ ∅∅XX XXXX XXXX
Most significant bits (non ansi) least significant bits
H1 H2 H3 H4
∅∅XX XXXX ∅XXX X∅∅∅
(MSB) (ANSI) (LSB)
R LMI: NFRM (DTE only). An LMI message from the DCE indicates that a
INACTIVE PVC (HHHH) previously active PVC has become inactive.
H1 H2 H3 H4
H1 H2 H3 H4
(MSB) (ANSI) (LSB)
R LMI: NFRM An LMI message has referenced an unknown DLCI ;
UNKNOWN PVC HHHH in hexadecimal character represents the DLCI. The
(HHHHSS) relevant bits are shown by the positions marked X below :
H1 H2 H3 H4
H1 H2 H3 H4
(MSB) (ANSI) (LSB)
SS in hexadecimal represents the state of the link:

X=1 active link ; X=0 inactive link.
S1 S2
∅∅∅∅ ∅∅X∅
MSB LSB
R LOSS OF CARRIER X25-N2, Link descriptor - DCD option.
HDLC No signal 109 following two consecutive samplings (3 second
interval).
R NO ACKNOWLEDGMENT ILAN The maximum number of retransmissions of a TPDU has been
reached and the Megapac has not received a valid
acknowledgment.
R NO RAM system The configuration specified is greater than the SIZE/ parameter
(MEM table).
System messages
E Page 32-6
E
Type
R
TEXT / SUFFIX
NO RESPONSE
Protocol
system
Meaning
Following transmission of a call request packet, a call accepted
packet has been received within the time determined by timer
TP2 (CALL TIME OUT/ parameter of the link descriptor).
This message is subject to the following modifications and
extensions:
The NAME field now has the format LLLL(nnn) or LLLL in which
LLLL identifies the link and (nnn) is the logical resource number.
It is stored in the ELOG table of the Megapac node.
An EF (event) frame is automatically sent to the NMS
management center.
The called DTE address and the calling DTE address appear in
the TEXT field.
R NOT RESPONDING X25-N2 Link descriptor - POLL option.
The number of RR command frames with the P bit set to 1
(POLLs) sent is equal to the maximum number of
retransmissions (TRIES parameter) with no response.
The link is reset.
R OVERRUN system Loss of data due to capacity overrun:
from the input data buffers (no flow control or flow control
violation),
from the receive buffers (insufficient value associated with the
BUFFERS/ parameter of the logical resource).
Note: When this situation happens often, a filter prevents
multiple messages being generated and artificially overloading
the system.
R PACKET TOO LARGE ILAN, The length of the "LLC data" field is greater than the Megapac
XLAN, buffer capacity.
CONS,
Token
Ring
R PRI MAC ERROR X25, Syntax error in MAC table (E1-G704 operation)
HDLC
R PRI MSG: (FFFF) message X25, For PRI-64 (30B+D) board this message means "disconnect" of
HDLC one B channel.
R PU ACTIVATED RESP+ CLUS, Following transmission of an ACTPU command by the IBM host,
3270 the Megapac has sent an ACTPU response, activating the PU
concerned.
R PVC STOPPED NFRM The FRAME is stopped when the DLCI receives it.
The frame is rejected.
R QFRMR SDLC, A QFRMR packet has been received by the Megapac.
QLLC,
CLUS,
3270
R QLLC RESTART SDLC, Exchange of QSM/QUA packet establishing the QLLC level.
QLLC,
CLUS,
3270
System messages
E Page 32-7
E
Type
R
TEXT / SUFFIX
RECEIVER ERROR (b1)
Protocol
ILAN,
XLAN,
CONS,
LAN, IP
Meaning
A special situation or an error has occurred on receipt of a
frame.
b1 hex value with the following meaning:
01 - end of "LLC data" field,
02 - beginning of "LLC data" field,
04 - buffer management level error,
08 - the CRC calculated is not the same as the content of the
FCS field,
10 - input buffer capacity exceeded,
20 - frame structure incorrect,
40 - error indication generated in the following cases:
• frame size greater than "max frame size",
• frame size is not a whole number of bytes.
80 - buffers allocated to ETHERNET chip are full.
R RESET X25-N3 A reset request or indication packet has been received.
R RESTART general The link has been reset.
R RESTART (E) X25-N2 The link has been reset following an exchange of RESTART
(Extended) SARME/UA or SABME/UA frames.
(E or e) indicates the use of "modulo 128 frames".
R RESTART (e) X25-N2 The restart has been performed with 116 at ZERO and then in
SIO the event of failure with 116 at ONE (standby link) and so on.
RESTART (n) Circuit 116 controls a modem which manages two links (main
and standby).
If the link is restarted with 116 at ZERO, the message RESTART
(E) or RESTART (N) is displayed.
If the link is restarted with 116 at ONE, the message RESTART
(e) or RESTART (n) is displayed.
R RESTART (N) X25-N2 The link has been reset following an exchange of SARM/UA or
SABM/UA frames.
(N or n) indicates the use of "modulo 8" frames.
R SRC-REF ERROR ILAN, One of the following situations has occurred:
(bb ..... etc) Transport on receipt of a TPDU DR, the content of the REFERENCE
SOURCE field is not the name of the logical resource associated
with the calling transport service user,
on receipt of a TPDU DC, the content of the REFERENCE
SOURCE field is not the name of the logical source associated
with the called transport service user.
R SSAP ERROR ILAN, A destination LSAP (transmission of a "command" LLC-PDU) is
XLAN, not the same as a source LSAP (transmission of the
CONS, symmetrical "response" LLC-PDU).
Token
Ring
System messages
E Page 32-8
E
Type
R
TEXT / SUFFIX
SYSTEM RESTART
Protocol
system
Meaning
The system has been reset because of one of the following
situations:
• Megapac powered down then powered up,
• use of the BOOT command,
• use of the REST ALL command,
• there are no "system" buffers available.
During the Restart System, the Megapac check the available
memory. When an memory error is detected, the next message
is generated :
SYSTEM RESTART - MEMORY ERROR (aaaaaa,vvvv,rrrr)
• aaaaaa memory address in error (hexadecimal)
• vvvv data written in memory.
• rrrr data read in memory.
R TEST I (INDICATION) X25-N2 A "command" TEST frame has been sent.
R TEST R (RESPONSE) X25-N2, Following transmission of a "command" TEST frame by the
ILAN, Megapac, a "response" TEST frame has been returned.
(ABCDEFGHIJKLMNOP) CONS "ABCDEFGHIJKLMNOP" is the content of the information field
(hex).
R TKN1 A/C Token Adapter Check.
(HHHHHHHHHHHHHHHH) Ring Irrecoverable hardware or software error at board level.
R TKN1 C/F Token Command Failure.
(HHHHHHHHHHHHHHHH) Ring If the first HHHH is 0003, the Open command has failed.
In this case, the HH after 0003 has the following meaning:
80 concluding Open command
40 node address error (address specified incorrect)
20 "List Error" on sending or receiving
10 buffer size error (buffer used by board)
08 reserved
04 counting error in send buffer
02 open error on insertion in the ring
01 open options not supported by the board
R TKN1 I/B ERR S = HHHH Token Initialization Block error.
Ring HHHD board CRC error. Irrecoverable hardware error.
R TKN1 OPEN Token The Token-Ring interface has been opened correctly and is
Ring operational.
System messages
E Page 32-9
E
Type
R
TEXT / SUFFIX
TKN1 R/S
(HHHHHHHHHHHHHHHH)
Protocol
Token
Ring
Ring Status report.
Meaning
This message does not necessarily indicate a failure or an error.

The first HHHH group must be 0000 and the following HHH can
have the following meanings:
800 loss of signal
400 hardware error
200 software error
100 the card is sending or receiving a "Beacons" frame
080 "Lobe Wire Fault"
040 "Auto Removal Error"
020 reserved
010 "Remove MAC" frame received
008 error counter overflow
004 the board is "ring station" only
002 "Ring Recovery"
This message is not written in the ELOG table.
R TKN1 S/U ERR S = HHHH Token Start-Up error.
Ring HHHH indicates:
HHH0 initial test error
HHH1 board software checksum error
HHH2 board RAM error
HHH3 instruction test error
HHH4 Context/Interrupt test error
HHH5 protocol manager hardware error
HHH6 system interface register error
R TX INT FAIL X25-N2 Overflow problem in XIO board controller.
R UNSOLICITED UA OR F- X25-N2 One of the following situations has occurred on the XIO board:
BIT • an unsolicited UA response frame has been received,
• an unsolicited response frame with the F bit set to 1 has
been received.
S.S V25bis INDICATION (....) V25B A V.25bis message has been received by the Megapac.
"...." is a prefix, followed by the parameter(s) concerned.
S.S XID nnnnnnnnnnnnnnnn X25 An "XID" identification check message has been received
(Recommendation X.32) by the Megapac.
"nnnnnnnnnnnnnnn" are the first 24 characters received.
System messages
E Page 32-10
33. Glossary
Asynchronous Terminal transmitting data in asynchronous mode.

A method of sending data in which the interval between characters may be of
unequal length.
Start and stop bits are inserted at the beginning and/or the end of each character
to be transmitted.
BOOT The BOOT command is used to commit changes to configuration memory, to link
configuration descriptor, to routing tables, etc.
It restarts the system.
BSC (Bisync) "Character" oriented IBM communication protocol.
This uses a defined set of control characters and sequences for synchronized
transmission of binary-coded data.
On a BSC link, communications can be in "duplex" or "half-duplex" mode.
When a BSC link is resynchronized, characters are scrapped.
CCITT International Telegraph and Telephone Consultative Committee.
An organization defining recommendations concerning communications.
CI V.24 interchange circuit n°125.
Call indicator.
CP Priority at the "calling" end
CALL PRIORITY When setting up a logical resource, a priority (0-15) can be assigned to an
originating (calling) resource.
The calling resource can only access the destination resources for which RP is
less than or equal to the calling resource's CP.
When a resource has a password ("logical resource" parameters - PASS option),
the CP defined in a PASS file record takes precedence.
CSMA / CD IEEE 802-3 protocol used in Ethernet local area networks (Carrier Sense Multiple
Access/Collision Detection).
CTS Alternative name for V.24 interchange circuit 106. Clear to send (see also RFS).
DCD V.24 interchange circuit n° 109.
Data channel received line signal detector (data carrier detect).
DCE Equipment providing the functions required to establish, maintain and terminate a
connection for data transmission purposes.
DMA Direct memory access.
DRC "Destination Resource Code", abbreviation used for routing to a resource.
DSAP Destination Service Access Point.
Refers to a local area network.
Identifies the receiving LLC entities of an LLC PDU.
DSR V.24 interchange circuit n° 107.
Date set ready.
Glossary
E Page 33-1
E
DTE
•
•
Data terminal equipment. This may be qualified as:

a start-stop mode DTE, working in "character" mode, or
a packet mode DTE.
DTR V.24 interchange circuit n° 108/2.
Data terminal ready.
EPROM Erasable, Programmable, Read Only Memory.
ETHERNET A local area network using "carrier sense" multiple access with collision detection
(CSMA CD).
The transmission medium is a 10 Mbit/s IEEE 802.3 cable.
Remember that an ETHERNET bearer can have a LAN link descriptor, an IP link
descriptor and a number of ILAN and CONS link descriptors at the same time.
Gateway Logical or physical mechanisms for interconnecting different networks.
It handles protocol conversion and provides the interface between the networks.
HDLC "Bit oriented" synchronous protocol used in the "OSI data link" layer.
IP See TCP/IP.
ISO International Organization for Standardization.
LAN Local area network.
Basically, used to connect (at very high data rates) communication equipment
within a building.
Link In a communication network, a connection established between a number of items
of equipment.
LLC Logical Link Control. Refers to a local area network.
Starting from the top layers, the "link" layer comprises, in turn, the LLC and MAC
(Medium Access Control) sublayers.
The functions handled by the LLC sublayer are:
• Exchange of control signals.
• Data flow control.
• Interpretation of "command" LLC PDU received and generation of
corresponding "response" LLC PDU.
• Error checking.
• Backup on error.
LLC1 LLC conforming to IEEE Recommendation 802-2.
Comprises in particular the "connectionless" type LLC1.
LLC PDU Protocol data unit exchanged between LLC entities.
MAC Medium Access Control. Refers to a local area network.
Starting from the top layers, the "link" layer comprises, in turn, the LLC (Logical
Link Control) and MAC (Medium Access Control) sublayers.
The functions handled by the MAC sublayer are:
• Organization of data in frames and vice versa.
• Error checking.
E
• Underlying physical layer access control.
Glossary Page 33-2
E
Network
Node
An interconnected group of nodes.

Equipment (X.25 switch or statistical multiplexer, for example) handling the
connection of multiple resources to a network.
OSI Reference model
ISO standard concerning "layered" architectures for a communication network.
The model comprises the following layers:
"Application" layer (n° 7)
This provides the semantics (or meanings) for the data exchanged between end
users.
"Presentation" layer (n° 6)
This handles and converts the syntax of data units exchanged between end users.
"Session" layer (n° 5)
This sets up and disconnects call sessions.
"Transport" layer (n° 4)
This handles the transfer of data, with error correction, between end users.
"Network" layer (n° 3)
This routes the data through the network and handles flow control.
"Data link" layer (n° 2)
This arranges the data in frames.
It transfers the frames, with error detection, over a link.
"Physical" layer (n° 1)
This handles the transfer of bits.
Each layer is independent, and provides a service to the layer immediately above.
Functionally, the architecture can be divided into two parts:
• "network" services, provided by layers 1-2-3,
• "end user" services, provided by layers 4-5-6-7.
Packet A block of data (and associated control elements) transmitted as a complete
package over a network.
PAD (Packet Assembler/Disassembler)
A device used to connect several asynchronous or synchronous terminals or a
number of "computer" ports to a packet switched network.
PAD TELNET The Megapac behaves like a "Telnet client".
Port In communication equipment or networks, a physical or logical entity via which
data is exchanged.
Priority (of routing) Refer to CP.
Refer to RP.
PROM Programmable Read Only Memory.
Glossary
E Page 33-3
E
Protocol
PVC
A set of conventions used to control the exchange of information between two peer
entities in a data network.
Permanent virtual circuit
A logical channel is permanently assigned to the destination resource.
QLLC
RCLK V.24 interchange circuit n° 115.
Receiver signal element timing (DCE).
RD V24 interchange circuit n° 104.
Received data.
Resource Network equipment or output logical resource with which a "calling" device can set
up a call.
Each logical resource is identified by a resource name on four characters. This
means that routing can be based on a resource name.
Resource class A group of "destination" logical resources having the same resource name.
RFC (Request For Comment)
Specifications concerning the TCP/IP environment and published by the network
information centre (NIC) of the US Department of Defense.
RFS V.24 interchange circuit n° 106.
Ready for sending (see also CTS).
Routing In a network, selection of a valid path for a call to the required resource.
RP Priority operating at the "called" level
Resource Priority When setting up a logical resource, a priority (0-15) can be assigned to a
Only a caller with a CP that is greater than or equal to the RP of the required
resource can access that resource.
RTS V.24 interchange circuit n° 105.
Request to send.
Source Calling DTE or line.
The MEGAPAC sees the caller as an input resource.
SSAP Source Service Access Point
Refers to a local area network.
Identifies the LLC entity sending an LLC PDU.
Statistical multiplexer A multiplexer for which time (on a communication channel) is allocated to a
terminal (only when there is data to be sent).
SVC Switched virtual circuit
A call procedure and a clearing procedure are respectively required at the start
and end of the call.
Synchronous Data transmission in which the data characters and bits are transmitted at a fixed
rate.
The transmitter and receiver are synchronized.
TCLK V.24 interchange circuit n° 114.
E
Transmitter signal element timing (DCE).
Glossary Page 33-4
E
TCP/IP
•
•
Transmission Control Protocol/Internet Protocol.

TCP provides a connected mode "transport" service (CONS).
IP provides a "datagram" type connectionless "network" service (CLNS).
TD V.24 interchange circuit n° 103.
Transmitted data.
TELNET This protocol normally provides a standard interface between a client terminal and
a process running in a server host.
TELNET mainly incorporates the concept of network virtual terminal NVT and
option negotiation.
The concept of virtual terminal relieves the host of having to handle specific
information concerning a particular terminal type.
The Telnet user program converts the client terminal's character set into an NVT
standard character set. This is again converted by the Telnet server program into
a character set specific to the server host.
TELNET also enables the two devices concerned to negotiate options (change of
character set, echo mode, etc), located above the NVT level.
For example, a sending device can declare that it supports or does not support a
particular option and simultaneously asks the receiving device to implement or not
implement that option.
A MEGAPAC node can support PAD TELNET emulation on the client side or
TELNET SERVER emulation on the server host side.
Terminal Asynchronous terminal.
TPDU OSI Transport Protocol Data Unit.
Translation (of a call This is used to reconstruct a call request packet before routing it.
request packet)
The calling DTE address, the facilities and the call user data can be modified.
This service is invoked from the X.25 file by adding "T" or "T-" at the end of the
address concerned.
TSAP OSI Transport Service Access Point.
V.11 Electrical characteristics for balanced double-current interchange circuits for
general use with integrated circuit equipment in the field of data communications.
V.24 CCITT Recommendation defining the interchange circuits between data terminal
equipment and data circuit-terminating equipment.
V.25 bis Automatic calling and/or answering equipment on the general switched telephone
network using the 100-series interchange circuits.
V.32 A family of two-wire, duplex modems operating at data signalling rates of up to
9600 bit/s for use on the general switched telephone network and on leased
telephone-type circuits.
V.35 CCITT Recommendations defining data transmission at 48 kbit/s using 60-
108 kHz group band circuits.
V.54 Loop test devices for modems.
VIDEOTEX A terminal operating mode characterized by its displayable character sets and
function keys.
Virtual circuit A caller sets up a virtual circuit to a destination resource by assigning a logical
channel. This channel is then used to exchange data.
Glossary
E Page 33-5
E
WAN
X.3
Wide area network.

Example: network connecting distant computers.
CCITT Recommendation defining the packet assembly/disassembly facility (PAD)
in a public data network.
X.21 CCITT Recommendation defining the interface between data terminal equipment
(DTE) and data circuit-terminating equipment (DCE) for synchronous operation on
public data networks.
X.24 List of definitions for interchange circuits between data terminal equipment (DTE)
and data circuit-terminating equipment (DCE) on public data networks.
X.25 CCITT Recommendation, defining the 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.
X.28 CCITT Recommendation, defining the DTE/DCE interface for a start-stop mode
DTE accessing the packet assembly/disassembly facility (PAD) in a public data
network situated in the same country.
X.29 CCITT Recommendation, defining the procedures for the exchange of control
information and user data between a packet assembly/disassembly (PAD) facility
and a packet mode DTE or another PAD.
X.121 CCITT Recommendation, defining the international numbering plan for public data
networks.
33.1 V24/V28 interface signal
N° Direction Meaning Meaning

DTE - DCE (France) (USA)
102 Terre de signalisation TS Signal ground SG
103 è Emission de données ED Transmitted Data TD
104 ç Réception de données RD Received Data RD
105 è Demande pour Emettre DPE Request To Send RTS
106 ç Prêt A Emettre PAE Clear To Send CTS
107 ç Poste de Données Prêt PDP Data Set Ready DSR
108/1 è Connectez le Poste de Données CPD Connect Data Set to line CDS
108/2 è Terminal de Données Prêt TDP Data Terminal Ready DTR
109 ç Détection de Signal/Porteuse DS Data Carrier Detect DCD
111 è Sélection Débit SD Data Rate Select DRS
114 ç Horloge Emission Modem HEM Transmitter Timing SCT
115 ç Horloge Réception Modem HRM Receiver Timing SCR
116 è Sélection liaison de secours Select Standby SS
125 ç Indicateur d’Appel IA Ring Indicator RI
140 è Boucle 2 (distante) CT2 Remote Loop Back RLB
è
E
141 Boucle 3 (locale) CT3 Local Loop Back LLB
142 ç Indicateur d’Essai IE Test Indicator TI
Glossary Page 33-6
E
Division Réseaux
BP 410 - 11 rue watt - 75626 Paris Cedex 13 - France
Tel : +33 1 55 75 75 75
Fax : +33 1 55 75 31 91
S

Megabox - Megapac - Megafrad: "600B" Software Configuration Manual Guide To Parameters

Uploaded by

Copyright:

Available Formats

Megabox - Megapac - Megafrad: "600B" Software Configuration Manual Guide To Parameters

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

Megabox - Megapac - Megafrad: "600B" Software Configuration Manual Guide To Parameters

Uploaded by

Copyright:

Available Formats

E

MegaBOX - MegaPAC - MegaFRAD

"600B" SOFTWARE CONFIGURATION MANUAL

MegaBOX - MegaPAC - MegaFRAD

"600B" SOFTWARE CONFIGURATION MANUAL

Introduction to this manual

For whom it is written

The following typographical conventions are used throughout this document:

☛ This symbol indicates important information in the text.

INTRODUCTION TO THIS MANUAL.................................................................................................................. iii

INTRODUCTION TO THIS MANUAL .................................................................................................... iii

9.3 BANDWIDTH MANAGEMENT ON THE X25 LINK: ....................................................................................9-12

10.6.2.1 GIS adapter ISDN address ........................................................................................................... 10-8

11.10 ACCESS TO THE ISDN BOARD CONFIGURATOR .............................................................................11-19

15. TYPE/ PPP DESCRIPTOR...........................................................................................................15-1

18. TYPE/ CONS AND DLCX DESCRIPTOR.....................................................................................18-1

20. TYPE/ IP AND TIP DESCRIPTORS .............................................................................................20-1

22. TYPE/ ROUT DESCRIPTOR........................................................................................................22-1

24. TYPE/ MULT DESCRIPTOR ........................................................................................................24-1

30.3 CONFIGURATION PARAMETERS OF THE« SCOP » RESOURCE ............................................................30-2

FIGURE 21-1 EXAMPLE OF AN IPX GATEWAY ON A PPP LINK .....................................................................21-5

No attempt is made to describe the hardware configuration.

In case of problems, contact our hot line:

On a single fax number: +33 1 55 75 77 70

- INSTALLATION AND MAINTENANCE CENTRE

After Sales Service - Business Systems

11, rue Watt

75 626 Paris Cedex 13 - France

notice, and the information contained in it shall in no way be binding on E

1.1 "Descriptors" and "resources"

So, to set up a connection in Megapac,

Each Megapac link has an associated link descriptor:

1.3 "Resource" names

Example of a link with 16 "resources":

1.4.1 Different routings

1.5.1 Resource NAME without wild cards

Resource number Resource authorized

1.5.2 Resource NAME with « ∗ » wild cards

Resource number Resource authorized

(1) ∗AX∗ VAX1/2/3, aAXz, 0AX9, etc ...

(2) ∗AX∗ VAX1/2/3, aAXz, 0AX9, etc ...

(3) ∗AX∗ VAX1/2/3, aAXz, 0AX9, etc ...

(4) ∗AX∗ VAX1/2/3, aAXz, 0AX9, etc ...

(5) ∗AX∗ VAX1/2/3, aAXz, 0AX9, etc ...

(6) ∗AX∗ VAX1/2/3, aAXz, 0AX9, etc ...

(7) ∗AX∗ VAX1/2/3, aAXz, 0AX9, etc ...

1.5.3.1 « " " " " » resource NAME

Resource number Resource authorized

(0) VAX1 VAX1

(5) VAX3 VAX3

1.5.3.2 « " ∗ ∗ ∗ » resource NAME

Resource number Resource authorized

(0) VAX1 VAX1

(3) "∗∗∗ VAX1 or VAX2

(4) "∗∗∗ VAX1 or VAX2

(5) "∗∗∗ VAX1 or VAX2

(6) "∗∗∗ VAX1 or VAX2

(7) "∗∗∗ VAX1 or VAX2

"* (n) "* (n)