Copyright: Copyright © 1995 Eicon Technology Corp.
Citation: Copyright © 1995 Eicon Technology Corporation, Inc. All rights reserved.


WAN Services for Windows NT System Guide

Welcome

Chapter 1: Introducing WAN Services for Windows NT

Chapter 2: Getting Started

Chapter 3: WAN Services Configuration

Chapter 4: IP Routing Services

Chapter 5: Using Microsoft SNA Server

Chapter 6: Using X.PAD

Chapter 7: Using LANPAD

Chapter 8: Network Management Services

Chapter 9: Command Line Utilities

Chapter 10: Using ECMODULE

Chapter 11: The MPR.INI Initialization File

Appendix A: Modemless Connections and Cables

Appendix B: Performance Optimization

Appendix C: User Facilities and DTE Address Structure

Appendix D: Router Interoperation

Appendix E: X.3 PAD Parameters

Appendix F: X.28 and X.29 Commands


Welcome

WAN Services for Windows NT™ Version 3 Release 3 integrates seamlessly with the Windows NT environment, giving you wide area networking (WAN) capabilities. WAN Services provides X.25 connectivity for Microsoft RAS (Remote Access Service) enabling remote users to access LAN resources over an X.25 network. It also provides QLLC and SDLC connections for Microsoft SNA Server, enabling LAN users to access remote IBM hosts. WAN Services also includes IP Routing Services to access IP backbone networks over WANs.

WAN Services for Windows NT supports the entire Microsoft BackOffice suite of applications

In addition, WAN Services for Windows NT lets you run your X.25 applications (developed with Eicon Technology's X.25 Network-Level Developers Toolkit) on a Windows NT machine.

What is WAN Services for Windows NT?

Core Services

X.PAD

Eicon SNA Link Drivers

IP Routing Services

LANPAD Services

Network and Systems Management

Key Features of WAN Services for Windows NT

System Requirements

Customer Services


Welcome

What is WAN Services for Windows NT?

WAN Services for Windows NT consists mainly of protocol software which runs on the EiconCard, and gives your Windows NT machine wide area networking capabilities. WAN Services consists of the following components:

•	Core Services

•	X.PAD

•	SNA Link Drivers

•	IP Routing Services

•	LANPAD Services

•	Management Utilities


Welcome

What is WAN Services for Windows NT?

Core Services

WAN Services requires one or more EiconCards to establish links with X.25 or Frame Relay packet-switched networks, or make use of SDLC or PPP over a leased or dial-up line. WAN Services can also use an ISDN network as the physical medium while using X.25, Frame Relay, or PPP as the network-level protocol. The Core Services software provides the necessary software support to manage the EiconCards. This includes:

•	X.25, Frame Relay, SDLC, and PPP protocol processing software that is loaded onto the EiconCard, enabling it to process communications based on these four protocols, plus support for EiconCard-based dialers and a wide variety of external dialer types.

•	A Windows configuration program which allows you to customize the X.25, Frame Relay, SDLC, and PPP protocol processing software and dialer-related parameters, and define IP mappings and IP packet filters for routing.

About the EiconCard

The EiconCard is the hardware component of WAN Services for Windows NT. It is sold separately by Eicon Technology. The EiconCard is an intelligent communications coprocessor, with its own CPU and on-board memory.

The type of EiconCard you choose depends on the volume of information you need to transmit and receive and the number of connection types you want to make. Up to six EiconCards can be installed in a WAN Services PC. See the section, "Key Features of WAN Services for Windows NT", for a list of supported EiconCards.

Note:
Micro Channel PCs support a maximum of four EiconCards.
IP routing services can use a maximum of 16 ports.


Welcome

What is WAN Services for Windows NT?

X.PAD

X.PAD performs as a serial port driver. This allows third-party asynchronous communications programs to communicate with an X.25 Packet Switched Data Network (PSDN). X.PAD includes extensions specifically designed to integrate tightly with the Remote Access Service (RAS). See the section "Microsoft Remote Access Service" for more information.


Welcome

What is WAN Services for Windows NT?

Eicon SNA Link Drivers

WAN Services includes drivers that allow Microsoft SNA Server to use installed EiconCards as wide area network adapters. These drivers are written to Microsoft's SNA Device Interface Specification (SNADIS). See the section "Microsoft SNA Server" for more information.


Welcome

What is WAN Services for Windows NT?

IP Routing Services

The IP Routing Services driver, ECNDIS.SYS, works with Microsoft’s IP stack to form the heart of the IP Routing Services software, to provide routing services for local and remote TCP/IP applications. See the section "IP Routing Services" for more information.

Note:
ECNDIS.SYS complies with the NDIS 3.0 specification.


Welcome

What is WAN Services for Windows NT?

LANPAD Services

LANPAD is a TCP/IP socket to COM port redirector. LANPAD enables a user or device on the internetwork to initiate a TCP/IP session with a WAN Services PC, the session is then redirected to an X.PAD port to connect to an X.25 attached device on the X.25 network. See the section "LANPAD Services" for more information.


Welcome

What is WAN Services for Windows NT?

Network and Systems Management

WAN Services for Windows NT also includes:

•	SNMP sub-agent (MIB II compliant)

•	Windows 3.1 SNMP console program which enables you to remotely monitor and control WAN Services

•	Command line utilities to monitor and control the EiconCard(s) installed in the WAN Services PC

•	Command line utilities to locally monitor, control, and dynamically configure the routing portion of WAN Services


Welcome

Key Features of WAN Services for Windows NT

•	Supports Microsoft Windows NT 3.51 (Workstation and Server)

•	Supports these EiconCards: DPNA/PC, EC/PC, HSI/PC, IMC/PC, MPNA/PC, EC/MC, HSI/MC, MPNA/MC, and EiconCard S51

•	Automatically detects the I/O port, IRQ, and memory segment for your EiconCard to ease configuration

•	Interoperates with other Eicon Technology products: Router for NetWare & Router for NetWare Router (NLM), Router for Unix, and IP Router for OS/2

•	Eicon Technology’s SNMP Console allows remote monitoring and control of all facets of your WAN Services product, including dynamic router configuration

•	Graphical interface for all elements of WAN Services configuration

•	SNMP sub-agent (MIB II compliant)

•	Multi-Processor support

•	Alpha support

•	MIPS support

•	PowerPC support

•	ISDN BRI (Basic Rate Interface) support

•	ISDN switch types: NI-1 (North America), TPH1962 (Australia), Euro-ISDN, and 5ESS support

With SNA Link Drivers

•	Provides X.25/QLLC and SDLC connections to IBM hosts with Microsoft SNA Server

•	Supports multiple PUs on the same physical SDLC connection as Microsoft SNA Server

With X.PAD

•	Supports up to 254 serial ports in the range COM1...COM999

•	Supports TOA/NPI addressing according to X.25 CCITT Recommendation 1988

•	Supports Windows NT Performance Monitor

With IP Routing Services

•	Connects TCP/IP local area networks over X.25 packet-switched networks (SVCs and PVCs for Eicon remote routers, SVCs for third-party remote routers), Frame Relay networks, leased or dial-up lines using PPP, and over ISDN data networks using any of X.25, Frame Relay, or PPP

•	Interoperates with RFC-compliant routers from third-party vendors including Bay Networks (formerly Wellfleet Communications, Inc. and Synoptics Communications, Inc.), Cisco Systems, Inc., and IBM Corp.

•	Includes data compression for links between two Eicon Technology routers

•	Router driver is NDIS Compliant (NDIS 3.0)

•	Complies with RFCs 877/1356, 1294/1490, and 1331/1548

•	Special features:

•	Supports dynamic routing table management via RIP

•	Dial-on-demand

•	Dial backup

•	Advanced IP packet filtering, and support for IP datagrams and broadcast datagrams


Welcome

System Requirements

•	Intel-based (ISA, EISA, or Micro Channel bus), Alpha, MIPS PC, or PowerPC, running Microsoft Windows NT 3.51 (Workstation or Server) with at least 12 MB of RAM (16 MB recommended)

•	At least one EiconCard with a minimum of 512KB of RAM (1 MB is recommended): DPNA/PC, EC/PC, HSI/PC, IMC/PC, MPNA/PC, EC/MC, HSI/MC, MPNA/MC, and EiconCard S51

•	A connection to a WAN medium supported by WAN Services for Windows NT, and the necessary hardware for that connection (see Chapter 2)

•	If you are using the IP Routing Services you must install the TCP/IP protocol and SNMP option of Windows NT

•	If you are installing the Eicon Network Management Services and the Eicon SNMP Console, then you must install the TCP/IP protocol, SNMP Service, and FTP Server option of Windows NT

•	If you are installing SNA Link drivers, you must install SNA Server version 2.1 or later


Welcome

Customer Services

Eicon Technology Customer Services personnel are committed to providing the best possible technical support to all Eicon Technology customers.

Eicon Technology Customer Services

To obtain technical support you must contact either Eicon Technology or your Eicon Technology supplier, depending on your location. Note that in some regions you can save time and long distance charges by sending a fax describing your situation instead of calling. Customer service personnel will then call you to provide a solution or to request additional information.

•	In the United States, call (214) 490-3270 or send a fax to (214) 239-8069.

•	In Canada, Central and South America, Asia (excluding the Middle East), Australia, and the Pacific Rim, call (514) 631-5246, or send a fax to
(514) 631-3092 (please mark it "Attn: Customer Services").

•	In Europe, Latin America, Russia, Iceland, the Middle East, and Africa, contact your Eicon Technology supplier.

•	Visit our Web server at http://www.eicon.com.

Eicon Technology on CompuServe

An inexpensive way to get up-to-date advice and patches is through the Eicon Technology forum on the CompuServe bulletin board. If you are already a CompuServe member, simply enter "go eicon" at the ! prompt.


Chapter 1: Introducing WAN Services for Windows NT

This chapter describes WAN Services for Windows NT, and what it enables you to do. Brief introductions to X.PAD, IP Routing Services, and LANPAD are also included.

WAN Services for Windows NT Components

What Does it Do?

Microsoft Remote Access Service

Microsoft SNA Server

Microsoft Exchange Server

Microsoft Systems Management Server

IP Routing Services

LANPAD

Event Viewer

Performance Monitor


Chapter 1: Introducing WAN Services for Windows NT

WAN Services for Windows NT Components

WAN Services for Windows NT is composed of several components: Core Services, the EiconCard drivers including drivers for Remote Access Service (RAS), SNA Server, IP Routing Services, LANPAD, and the remote management utility. The Eicon SNMP Console can be run remotely to monitor WAN Services activity, such as port and protocol statistics. This console can also be used to remotely monitor, control, and dynamically configure your IP Routing Services. Also included are command line utilities to locally monitor, configure, and control WAN Services.


Chapter 1: Introducing WAN Services for Windows NT

What Does it Do?

WAN Services for Windows NT allows you to extend the services of Microsoft’s Windows NT servers, such as Windows NT Server (RAS), SNA Server, Exchange Server, and System Management Server to reach across WANs. The IP Routing Services will also allow you to interconnect your TCP/IP LANs.

The diagram above shows how WAN Services operates in conjunction with SNA Server and Remote Access Service. WAN Services’ IP Routing Service also makes it possible to interconnect your IP LANs and connect to the Internet.

The following sections describe what WAN Services for Windows NT does for each of these communications servers.

Microsoft Remote Access Service

Microsoft SNA Server

Microsoft Exchange Server

Microsoft Systems Management Server

IP Routing Services

LANPAD


Chapter 1: Introducing WAN Services for Windows NT

What Does it Do?

Microsoft Remote Access Service

Remote Access Service (RAS) which is included with Windows NT, provides remote users with access to any resource on the corporate network, particularly Windows NT SMS or SQL servers. WAN Services enables remote users to connect to RAS over X.25 Networks. This is achieved with Eicon Technology’s X.PAD. For more information, see Chapter 6, "Using X.PAD."


Chapter 1: Introducing WAN Services for Windows NT

What Does it Do?

Microsoft SNA Server

Eicon Technology's WAN Services for Windows NT integrates seamlessly with SNA Server and provides X.25/QLLC and SDLC SNA Link (ecx25.dll and ecsdlc.dll) drivers for Microsoft SNA Server. This support enables end-users on local area networks to access remote SNA hosts over leased lines, switched lines, or X.25 packet-switching networks. In addition to providing drivers for SNA Server, WAN Services for Windows NT also has IP routing capabilities. It can therefore be employed at remote LAN sites to route SNA client traffic over a backbone network to the Microsoft SNA Server at the centrally located "glass house."

Eicon Technology also has client-side products that are tightly integrated with Microsoft SNA Server. Access for Windows NT 3270 and 5250 provide reliable, easy-to-use access to IBM host applications. These 32-bit-enabled desktop connectivity products are available in both LAN client and stand-alone versions.

The stand-alone version includes Microsoft SNA Workstation and drivers for Eicon’s line of WAN interface cards. Stand-alone PCs can connect to the host over SNA networks using LLC2 (Token-Ring and Ethernet), SDLC, and X.25 adapters.

The LAN client version of Access for Windows NT connects to the Microsoft SNA Server, and can be installed on individual Windows NT LAN workstations, or on a file server.

For more information on using SNA Server with WAN Services for Windows NT, see Chapter 5 "Using Microsoft SNA Server".


Chapter 1: Introducing WAN Services for Windows NT

What Does it Do?

Microsoft Exchange Server

This Microsoft product is an X.400 Message Transfer Agent (MTA) for Windows NT, which can exchange X.400 messages with any other accessible MTA. WAN Services allows Exchange Server and other MTAs to exchange such messages across an X.25 packet-switched data network (PSDN).

Note:
As of this writing, Microsoft Exchange Server is only available in beta form.


Chapter 1: Introducing WAN Services for Windows NT

What Does it Do?

Microsoft Systems Management Server

This Microsoft product is a software distribution and inventory tool. When used in conjunction with WAN Services for Windows NT, it enables enterprise-wide management capability.


Chapter 1: Introducing WAN Services for Windows NT

What Does it Do?

IP Routing Services

When IP Routing Services is installed, all workstations on the LAN are able to run TCP/IP applications like FTP or Telnet to exchange information with computers on remote LANs whether they are in the same building or around the world.

IP Routing Services routes traffic between local and remote TCP/IP networks over X.25 or Frame Relay PSDNs. The local and remote TCP/IP networks can also be connected by leased or dial-up telephone lines using the Point-to-Point Protocol (PPP). These protocols are also supported over ISDN connections.

Two or more TCP/IP networks may be transparently linked together into a single internetwork with an EiconCard and IP Routing Services. TCP/IP application protocols such as FTP and TELNET may be used on any platform to transparently communicate with any other platform. From the user's perspective, all platforms are connected to one large network.

The EiconCard also carries SNMP traffic transparently over X.25, Frame Relay, or PPP protocols, allowing remote machines to be managed over a WAN link using SMS (SMS uses integrated SNMP MIB II).

Installing IP Routing Services will also allow your workstations running Windows NT or Windows for Workgroups on the TCP/IP internetwork to transparently share drives and printers with each other.

Using IP Routing Services to connect two remote LANS over an X.25 PSDN and ISDN, using the EiconCard S51

On the TCP/IP internetwork, local traffic is handled by the TCP/IP software. Local traffic that is destined for a remote host is received by the router, which directs it across the X.25 packet-switched network.

Using IP Routing Services to connect two remote LANs over an X.25 PSDN and ISDN, using the EiconCard S51

Special Features

WAN Services for Windows NT and its IP routing capabilities incorporates three useful features related to managing your IP-based internetwork:

Microsoft RIP

WAN Services for Windows NT is completely compatible with the Microsoft RIP (Routing Information Protocol) service. RIP enables the router to automatically update its routing tables for all available remote routers while operating, without intervention. This is known as dynamic routing.

The Microsoft RIP service provides automatic routing of data from end-to-end by the most efficient route. If a router goes down, data is automatically dynamically rerouted to its destination.

This is in contrast to static routing, which requires every possible router link to be configured and started. Also, if a router goes down, data is not able to reach its destination until a new router connection is configured and started.

Dial-on-Demand

Dial-on-demand helps keep connect-time charges to a minimum when you are interconnecting IP LANs over a public PSDN, and requires almost no configuration. When you are multiplexing two or more logical connections over a single physical line, Dial-on-demand keeps the physical connection with the WAN medium closed when the line is not being used.

Dial Backup

Dial backup allows you to protect against the unexpected failure of a link between the local and remote LANs by allowing you to configure and designate a backup connection for any primary connection. The backup link is activated only when the primary link fails.

IP Routing Services is discussed in more detail in Chapter 4 "Using IP Routing Services".


Chapter 1: Introducing WAN Services for Windows NT

What Does it Do?

LANPAD

Eicon Technology’s LANPAD, when used in conjunction with X.PAD, offers users on the internetwork an X.25 gateway. Users initiate a TCP/IP session with the LANPAD server. LANPAD then redirects the session to an X.PAD port, giving the user access to the X.25 network and the ability to connect to any X.25-attached device.

LANPAD is discussed in more detail in Chapter 7 "Using LANPAD".


Chapter 1: Introducing WAN Services for Windows NT

Event Viewer

Event Viewer is a native Windows NT application which is used to record and view a list of most Windows NT system, application, and security errors. For WAN Services, any error messages will be generated in either the system or the application log. The most common of these errors occurs upon system startup when a Service or device driver fails to initialize.

Event Viewer records these errors and the date and time. By double-clicking one of the entries, you get a detailed analysis of the error and a proposed solution. An example of a typical problem that could arise is when a new adapter is installed in the Windows NT machine using the same memory segment as another adapter. The Event Viewer would list this entry in the system log, indicating that it was unable to initialize this adapter on Windows NT startup. When you double-click the entry, you would be presented with the message text telling you to check memory segment address, IRQ, etc.

If you encounter any problems when running Eicon Technology’s WAN Services for Windows NT with X.PAD, IP Routing Services, Eicon Network Management Services, LANPAD, or SNA Server Link Drivers, then Event Viewer is one of the first places to look. A listing of all WAN Services error messages is available in the WAN Services program group.

For more information on how to use Event Viewer, see the Microsoft Windows NT™ System Guide.


Chapter 1: Introducing WAN Services for Windows NT

Performance Monitor

Performance Monitor is a monitoring tool which aids in performance troubleshooting. It also allows you to chart and log current activity, set alerts, and create reports. WAN Services’ X.PAD supports Performance Monitor and can be a valuable tool for fine-tuning your configuration, as described in "Performance Monitor and X.PAD".

For more information on how to use Performance Monitor, see the Microsoft Windows NT™ System Guide.


Chapter 2: Getting Started

This chapter presents the steps required to install and configure Eicon Technology's WAN Services for Windows NT and its related programs. Once you have done this, you can proceed to WAN Services configuration, as described in Chapter 3.

While we recommend that you read all of this chapter before installing WAN Services for Windows NT, you may jump directly to “WAN Services for Windows NT Installation”.

Overview

System Requirements

Installation Strategy

Gather Configuration Information

EiconCard Installation

Multi-EiconCard Installations

WAN Services for Windows NT Installation

Creating Install Disks from the CD-ROM

Install Core Services

Install Optional Services Software

Services and Devices

Uninstalling WAN Services


Chapter 2: Getting Started

Overview

WAN Services for Windows NT installation has several components:

•	Hardware installation

•	Core Services

•	Software installation

•	IP Routing Services

•	Eicon Network Management Services

•	X.PAD

•	LANPAD Services

•	Eicon SNA Link Drivers

•	Eicon SNMP Console

The Core Services, X.PAD, IP Routing Services, and the Eicon Network Management Services are installed through the Network Control Panel Applet (NCPA) found in Control Panel.

The Eicon SNA Link Drivers are installed through SNA Server. The Eicon SNMP Console is installed with its own installation program.


Chapter 2: Getting Started

System Requirements

The basic requirements for WAN Services for Windows NT are as follows:

•	A personal computer running Microsoft Windows NT 3.51 (Server or Workstation)

•	At least 12 MB of RAM (16 MB is recommended)

•	At least one EiconCard with at least 512KB of RAM (1 MB is recommended): DPNA/PC, EC/PC, HSI/PC, IMC/PC, MPNA/PC, EC/MC, HSI/MC, MPNA/MC, and EiconCard S51

•	If you are using SNA Server, you must install SNA Server version 2.1 or above

•	If you want to use IP routing services, you must install:

•	The TCP/IP Protocol options of Windows NT 3.51 which includes:

•	TCP/IP Networking

•	Connectivity utilities

•	Simple TCP/IP Services (ROUTE, PING, TELNET, etc.)

•	SNMP Services

•	If you want to use the Eicon Network Management Services and the Eicon SNMP Console, you must install:

•	The TCP/IP Protocol options of Windows NT 3.51

•	The FTP Server option of Windows NT 3.51

•	The SNMP Service option of Windows NT 3.51

See the TCP/IP booklet that came with Windows NT for information on installing and configuring TCP/IP and SNMP services.

Note:
When configuring Windows NT SNMP security, you must make sure that the Eicon SNMP Console PC will have access to the WAN Services directory on the WAN Services PC. See the Windows NT documentation on TCP/IP for more information on how to install and configure Microsoft SNMP services.


Chapter 2: Getting Started

Installation Strategy

Before installing WAN Services for Windows NT, you must choose a PC on your LAN to function as the WAN Services PC. The WAN Services PC is the PC in which you install one or more EiconCards, and WAN Services for Windows NT.

To use WAN Services you must install the EiconCard(s), then the Core Services of WAN Services, and at least one other optional service. If you are using WAN Services with Exchange Server or Eicon Technology X.25 Toolkit applications, then Core Services are all you need.

To install the EiconCard(s), see “EiconCard Installation” .

The table below gives a quick reference to the Services available for installation.

Software	Description
Core Services	This is the mandatory component of WAN Services. Install it as directed in “Install Core Services”.
X.PAD	This is used in conjunction with RAS. Install it as directed in “Install Optional Services Software”.
IP Routing Services	This is used to interconnect IP LANs. Install it as directed in “Install Optional Services Software”.
LANPAD Services	This is used in conjunction with X.PAD. Install it as directed in “Install Optional Services Software”.
Eicon NetWork Management Services	This is needed if you want to use the Eicon SNMP Console. Install it as directed in “Install Optional Services Software”.
Eicon SNA Link Drivers	These drivers are for use with SNA Server. Install it as directed in “SNA Server Eicon Link Software”.
Eicon SNMP Console	This is used to remotely manage your WAN Services server. Install it as directed in “Eicon SNMP Console Installation”.

Before you start installing WAN Services for Windows NT, it is a good idea to gather the configuration information you will need to properly set it up. See “Gather Configuration Information”, for more information.


Chapter 2: Getting Started

Gather Configuration Information

We suggest that you make photocopies of the following configuration checklists, and complete one checklist for each connection you need to configure.

Configuration Checklists

The following checklists summarize the information you need to collect to configure the protocol software you will be using with WAN Services. Use the “F1” context sensitive online help in the WAN Services Configuration program for complete descriptions of these parameters.

X.25 Connections Checklist

SDLC Connections Checklist

Frame Relay Connections Checklist

PPP Connections


X.25 Connections

Collect the following information for each X.25 connection you will make

Description	Default	Value
X.25 address (Local DTE address)	none	________
Does your X.25 network support basic or extended packets? In 1984, the ITU (formerly CCITT) added an Extended Packet definition to the X.25 specification. Consult your network subscription to see if you can make use of Extended Packet features. This parameter affects Window size and Packet size.	extended	________
Does your X.25 network support CCITT 1988 X.25 Recommendation and TOA/NPI addressing?	1984	________
What is the maximum window size?		________
Default window size	2	________
What is the maximum packet size?		________
Default packet size	128	________
Number of virtual circuits	4	________
If your network uses non-sequential assignment of virtual circuits then determine the starting number  for each one	1	________
Determine the facilities you require	none	________
Determine the call user data you require	none	________
HDLC Parameters

Any connection using the X.25 protocol also uses HDLC at a lower level. Collect the following HDLC-related information for each X.25 connection you will make:

Description	Default	Value
Determine if the EiconCard port for this connection is DCE or DTE. For null-modem or back-to-back connections, one WAN Services PC must be DTE and the other DCE.	DTE	_________
Determine if your network uses the Poll bit in a non-standard manner. (FRMR to RR/RNR/REJ)	Yes	_________
Determine if your network supports extended sequence features.	Active	_________


SDLC Connections

Collect the following information for each SDLC connection you will make:

Description	Default	Value
Maximum Window Size	7	_________
Maximum Frame Size	267	_________


Frame Relay Connections

Collect the following information for each Frame Relay connection you will make:

Description	Default	Value
Type of local management interface (LMI) protocol supported by your network.	Annex.D	_________
How many DLCIs are assigned to the Frame Relay line?	1	_________
What is the starting number for your DLCI sequence?	varies	_________
What is the Window Size for each DLCI? This number must match the window size of the destination node.	7	_________
What is the maximum number of bytes of user data that can be contained in a Frame Relay frame?	1514	_________


PPP Connections

Collect the following information for each PPP connection you will make:

Description	Default	Value
Determine the maximum size (in bytes) of the data packet which can be transmitted over the link.	1500	_________
Define a 30 character user name to use for authentication during link establishment.	none	_________
Define a 30 character password to use for authentication during link establishment.	none	_________


Chapter 2: Getting Started

EiconCard Installation

The EiconCard installation is the first step to installing WAN Services for Windows NT.

⇒	Follow these steps to install the EiconCard(s):

1.	Install each EiconCard in the Windows NT machine.

Follow the directions in the installation guide that came with the EiconCard.

2.	Check for IRQ, I/O address, and memory segment conflicts.

Note:
WAN Services is able to automatically detect the I/O port physically configured on your EiconCard, and is able to scan for free IRQs and memory segments. However, if conflicts arise, we recommend the use of the Windows NT utility, WINMSD.EXE, or the Windows NT Diagnostics Application in the Administrative tools Program Manager group, to help determine free IRQs and memory segments. See the Microsoft Windows NT System Guide for more information on how to use WINMSD.EXE.

3.	If you are installing multiple EiconCards in the same ISA-bus file server, make sure that each EiconCard is set to a different IRQ (Interrupt Request Level), I/O Address, and Memory Segment. The same holds true for other cards in your system; all cards must be set to a different IRQ, I/O Address, and Memory Segment.

The only parameter that can be physically set on the EiconCard is the I/O Address. All other parameters are set with the WAN Services Configuration program.

For Micro Channel servers, all settings are made for you by IBM's Programmable Option Select (POS). POS automatically configures all adapter boards so that no conflicts occur. The POS program is found on the reference diskette that comes with your Micro Channel PC. However, you must take note of the slot number you installed the EiconCard in. See the Installation Guide that came with your EiconCard for details.

Caution:
Special consideration should be taken when installing an EiconCard in an AT-class PC (ISA bus). If the PC contains 16-bit peripheral cards which use memory windows (such as LAN or video adapters), then the EiconCard cannot share the same 128k group memory address.

The 128k memory group addresses are as follows:

A000-BFFF
C000-DFFF
E000-FFFF

For example, if you have a 16-bit LAN card which uses a memory window at C800-CFFF then you would not be able to put your EiconCard, or any other 8-bit card which uses a memory window, at any address in the range
C000 to DFFF.
If there is difficulty in managing the memory segments, most peripheral 16-bit cards can be configured as 8-bit cards. This can usually be done through jumper selections on the card or by placing the 16-bit card in an 8-bit slot. Check the manufacturer's documentation for their recommendations.

4.	Connect all external cables.

If the EiconCard is making a connection via a modem, connect the EiconCard to a synchronous modem as appropriate, and attach the modem to a dedicated or switched (dial) line.

The EiconCard is also capable of making a null-modem connection to another EiconCard or to a host. For more information, see Appendix A, “Modemless Connections and Cables.”


Chapter 2: Getting Started

EiconCard Installation

Multi-EiconCard Installations

WAN Services for Windows NT supports up to six EiconCards, with a maximum of 16 ports being used by the IP Routing Services. This enables you to support different types of connections through a single WAN Services PC.

If you intend to build a complex installation—one involving many EiconCards—it is recommended that you proceed incrementally, building up your installation from simple to complex. This way if you encounter a problem you will be able to isolate it more easily.

PC Power Supply

The EiconCard requires less power than most hard disks. Yet if your system is already loaded with a number of components (hard drive, tape backup, multiple floppy drives) you should verify that installing more than one EiconCard will not overload your system. The power requirements for each EiconCard is listed in its Installation Guide.


Chapter 2: Getting Started

WAN Services for Windows NT Installation

WAN Services installation has several components:

•	Core Services

•	Eicon Technology's X.PAD software

•	IP Routing Services

•	Eicon Network Management Services

•	EiconCard Link drivers for SNA Server

•	Eicon Technology’s SNMP Console

WAN Services installation is done through the Windows NT Network Control Panel applet (NCPA) except for the Eicon SNA Link drivers, which are installed through SNA Server, and the Eicon SNMP Console, which has its own installation program.

See Chapter 5, “Using Microsoft SNA Server” for more information on how to install and configure the Eicon SNA Link drivers.

See Chapter 8, “Network Management Services” for more information on how to install and use the Eicon SNMP Console.


Chapter 2: Getting Started

WAN Services for Windows NT Installation

Creating Install Disks from the CD-ROM

A batch file (TRANSFER.CMD) that creates the eight WAN Services for Windows NT install disks (1.44 MB) is included with WAN Services. It is located in the root directory of the WAN Services for Windows NT CD-ROM.

The syntax for TRANSFER.CMD:

TRANSFER [platform] [drive letter] [disk number disk number ...]

Where platform is “i386”, “alpha”, “mips”, or “ppc”.

Where drive letter is the disk drive on which you are creating the disks, either “A:” or “B:”.

Where disk number specifies the number of the disk you want to create. Value can be 1 to 8. Multiple disk numbers can be used.

For example,

TRANSFER i386 A:

will create all eight disks on drive A:, for the Intel version of WAN Services for Windows NT.

For example,

TRANSFER alpha B: 1 3 5

will create disks 1, 3, and 5 on drive B:, for the ALPHA version of WAN Services.

To assist in the installation of WAN Services for Windows NT, label the disks as indicated in the following table:

DISK	LABEL
1	WAN Services for Windows NT (Install) Disk 1
2	WAN Services for Windows NT Disk 2
3	WAN Services for Windows NT Disk 3
4	WAN Services for Windows NT Disk 4
5	WAN Services for Windows NT Disk 5
6	WAN Services for Windows NT (SNA) Disk 6
7	WAN Services for Windows NT (Console) Disk 7
8	WAN Services for Windows NT (Console) Disk 8
Note:
If you are creating disk to install the Eicon SNMP Console, you need only to create disks 7 and 8. The Eicon SNMP Console Install program is on the WAN Services for Windows NT (Console) Disk 7.


Chapter 2: Getting Started

WAN Services for Windows NT Installation

Install Core Services

SETUP.CMD is used to install any of the WAN Services components.

The Core Services software consists of a number of Eicon Loadable Modules (ELMs), EiconCard executables (EXEs), a few configuration files, and the WAN Services Configuration program files. All ELMs and the WAN Services Configuration program are installed in a directory of your choice.

⇒	Follow these steps for a successful Core Services installation:

1.	At the Windows NT console, logon as Administrator or equivalent.

2.	Insert the WAN Services for Windows NT CD-ROM into your CD-ROM drive and run the SETUP.CMD file located in the root directory.

3.	The Network Control Panel Applet (NCPA) is automatically started and the Network Settings dialog box appears.

4.	Click Add Adapter.

5.	From the Add Network Adapter dialog box, scroll down to the <Other> Requires disk from manufacturer entry, and click Continue.

Note:
If you have already installed one EiconCard, then choose EiconCard Adapter from the Add Network Adapter list and not from the <Other> Requires disk from manufacturer entry.

6.	Indicate the drive to which the WAN Services CD-ROM is mapped and click OK.

7.	From the displayed list, highlight the EiconCard Adapters entry and click OK.

8.	You are presented with the EiconCard Properties dialog box. Here you must configure the basic properties for the EiconCard.

a.	Select the type of EiconCard you are configuring. Click the Detect button to automatically detect which EiconCard is installed. You can also manually select an EiconCard from the drop-down list.

Note:
Automatic detection of your installed EiconCard should take about 30 seconds. If your PC fails to respond after this time or if you experience subsequent problems with another installed adapter card, you must shutdown, reboot and restart the WAN Services for Windows NT installation process. On subsequent installation attempts, DO NOT attempt to auto-detect your EiconCard.

b.	Click the Settings tab. The values displayed in the Settings tab have been detected as available for use by the EiconCard. You can use these values or manually select the values from the drop-down lists. See the section “EiconCard Installation”, for important information on setting the I/O port, IRQ, and memory segment on your EiconCard. Use the Help button for descriptions of any parameter.

Repeat steps 4 to 8 for each EiconCard that is installed in your PC.

After installing each EiconCard, you are presented with a dialog box giving you the option of immediately starting the WAN Services Configuration program. To save time, it is recommended that you install all the EiconCards before starting the WAN Services Configuration program.

Important:
This is the only place where you can set these parameters for your EiconCard(s). You can not set these values with the WAN Services Configuration program.

After installation, the newly-added EiconCard is displayed in the Installed Adapter Cards list:

⇒	To reconfigure the basic properties of an existing EiconCard:

1.	From the Installed Adapter Cards list, highlight the EiconCard that you want to reconfigure, and click Configure.

2.	After setting all your values, click OK.

Important:
You must shutdown and reboot the PC so that any changes will take effect.

With Core Services installation now complete, you are ready to install the optional software portion of WAN Services for Windows NT.


Chapter 2: Getting Started

WAN Services for Windows NT Installation

Install Optional Services Software

The optional Services software is made up of the following components:

•	IP Routing Services

•	Eicon’s Network Management Services

•	X.PAD

•	LANPAD

To install Eicon’s SNA Link drivers for Microsoft SNA Server, see Chapter 5, “Using Microsoft SNA Server.” To install the Eicon SNMP Console, see Chapter 8, “Network Management Services".”

To install the optional Services portion of WAN Services you must have already installed the Core Services component of WAN Services for Windows NT. Also, you must be logged in as Administrator or equivalent.

⇒	To install the optional services software for WAN Services for Windows NT:

1.	From Control Panel start the Network Control Panel Applet (NCPA). The Network Settings dialog box appears.

2.	Insert the WAN Services for Windows NT CD-ROM into your CD-ROM drive.

3.	From the Network Settings dialog box, click Add Software.

4.	From the Add Network Software dialog box, scroll down to the <Other> Requires disk from manufacturer entry, and click Continue.

5.	Indicate the drive to which the WAN Services CD-ROM is mapped and click OK.

6.	From the displayed list, highlight the service you want to install and click OK.

a.	IP Routing Services installs itself as both a driver and a logical network adapter. After installing IP Routing Services you are presented with two configuration screens. The first configuration screen is to configure the driver, the second is to configure the logical adapter (Eicon NDIS driver). See “Configuring the Router Driver and NDIS Adapter”, for more information.

b.	After installing X.PAD, you are presented with the X.PAD configuration program. Configure X.PAD as described in “Configuring X.PAD”.

c.	After installing LANPAD, you are presented with the LANPAD configuration program. Configure LANPAD as described in “Configuring LANPAD”.

Important:
You must install a separate instance of IP Routing Services for each EiconCard port on which you wish to use IP Routing. This will install a separate instance of an Eicon NDIS logical adapter for each EiconCard port used for routing. Windows NT sees each of these ports as a separate network adapter. This enables the flexibility of individually configuring each virtual adapter with different configuration parameters.

For example, if you install an MPNA EiconCard with six ports, and you want to use three of them for routing, you must install the IP Routing Services three times. This will result in three separate instances of the Eicon NDIS Logical Adapter entry in the Installed Network Adapters list.

7.	Repeat steps 3 to 6 for each additional service you want to install.

Note:
If you have already installed one instance of IP Routing Services, then choose Eicon IP Routing Services from the Add Network Software list and not from the <Other> Requires disk from manufacturer entry.

8.	If you have installed IP Routing Services, you are also required to set the TPC/IP parameters for each instance of the Eicon NDIS logical adapter. See “Configuring the Router Driver and NDIS Adapter”, for more information.

After installing all the services you require, you are now ready to configure your EiconCard(s). Configure your EiconCard(s), as described in Chapter 3, “WAN Services Configuration.”


Chapter 2: Getting Started

Services and Devices

WAN Services is installed as a number of services and device drivers. All of them can be controlled through the respective Services or Drivers applet in Control Panel. They can also be controlled with the NET STOP and NET START commands. See the Microsoft Windows NT System Guide for information on using the Services and Drivers applets as well as how to use the NET START and NET STOP commands.

The core functions of WAN Services are installed as the EICONCARDS service and the EiconCard device driver, ECNB. The EiconCards service and the EiconCard driver can be started, stopped, and their startup method configured with the Services or Devices applet through Control Panel. We recommend that you leave the startup methods at their defaults to ensure proper functioning of WAN Services for Windows NT.

To use the NET STOP and NET START commands with the EiconCards service and EiconCard device driver, use EICONCARDS and ECNB, respectively. The example below first starts the EiconCard driver, and then starts the EiconCard service.

NET START ECNB
NET START EICONCARDS

For information on the services and device drivers for IP Routing Services, see “IP Routing Services and Device Drivers”.

For information on the device driver for X.PAD, see “X.PAD Device Driver”.


Chapter 2: Getting Started

Uninstalling WAN Services

⇒	To uninstall WAN Services for Windows NT:

1.	Make sure that all applications that are using WAN Services are closed. This includes Microsoft SNA Server, Remote Access Service (RAS), Event Log, and Performance Monitor.

2.	From Control Panel, Start the Network Control Panel Applet (NCPA).

3.	To remove only one part of WAN Services, such as X.PAD, do the following:

a.	In the Installed Software list box, highlight the entry of the WAN Services software which you want removed, and click Remove.

4.	To remove all of WAN Services for Windows NT, do the following:

a.	Highlight the EiconCard Driver entry in the Installed Software list box, and click Remove.

b.	This will bring up a dialog box to confirm which components you want to delete. Mark all components for deletion, and click OK.

WAN Services is now uninstalled. You must shutdown and reboot your system so that any changes will take effect.

Note:
If, after uninstalling WAN Services for Windows NT, you want to re-install it, you must first shutdown and reboot your system.


Reconfiguring the EiconCard properties

⇒	To reconfigure the basic properties of an existing EiconCard:

1.	Start the NCPA.

2.	From the Installed Adapter Cards list, highlight the EiconCard that you want to reconfigure, and click Configure.

3.	After setting all your values, click OK.

Important:
You must shutdown and reboot the PC so that any changes will take effect.


Chapter 3: WAN Services Configuration

This chapter describes how to configure WAN Services for Windows NT using the WAN Services Configuration program. The WAN Services Configuration program is used to configure the EiconCard, high-level protocols, line protocols, dialers, and IP Routing Services. IP Routing Services configuration is described in Chapter 4, “IP Routing Services.”

X.PAD is configured with its own configuration program, as described in Chapter 6, “Using X.PAD.”

LANPAD is configured with its own configuration program, as described in Chapter 7, “Using LANPAD.”

The Eicon SNA Link drivers are configured through Microsoft’s SNA Server, as described in Chapter 5, “Using Microsoft SNA Server.”

Overview

Configuration Components

Navigating through WAN Services Configuration

Adding and Deleting Configuration Components

Modifying Parameters

WAN Services Configuration Program Menus

Starting WAN Services Configuration

Configuring the EiconCard


Chapter 3: WAN Services Configuration

Overview

WAN Services for Windows NT configuration is a two-part process. First, you must configure the EiconCards, Routing Services, X.PAD, and Eicon’s SNA Link drivers. Second, you must configure the applications that will use the EiconCards (Microsoft SNA Server and Remote Access Service).

The WAN Services Configuration program is an intuitive application that provides a graphical view of all configurable resources, enabling you to easily manipulate the configuration process. For example, clicking the EiconCard icon immediately presents the EiconCard configuration panel. Double-click the same icon to reveal additional icons which invoke port and protocol configuration options.

The configuration program sets all configuration parameters and the relations between them. Default values, which are provided for most parameters, facilitate the selection process and may generally be left unchanged.

In addition, to help simplify the configuration process further, WAN Services displays only the frequently modified parameters. Experienced users may click the Details button, to reveal additional but rarely-modified parameters.


Chapter 3: WAN Services Configuration

Configuration Components

The WAN Services software consists of several modules. These modules form the following components: Server, EiconCard, and Router (if it was installed). WAN Services Configuration integrates configuration of these different components into one program.

Note:
Before attempting to configure any protocols, open the online help (ECADMIN.HLP) and quickly read through the Contents topics. It will significantly reduce the time you spend configuring your WAN Services.

Server

The server component displays the Server Information panel.

EiconCard

The EiconCard handles all line-level and high-level protocol processing for each type of connection. You must configure a separate EiconCard port for each individual physical connection (SDLC, X.25, Frame Relay, or PPP) you want to make.

Router

The router configuration portion of WAN Services is not explained here. See the section “Configuring the Router Connections”.


Chapter 3: WAN Services Configuration

Navigating through WAN Services Configuration

The WAN Services Configuration program is designed to assist you in the configuration of WAN Services for Windows NT resources. Its graphical user interface provides a view of the logical structure of WAN Services, displaying all installed hardware and software communications components.

The Navigator is composed of a series of icons that show the current logical configuration path. When you click an icon, the parameters associated with the corresponding component appear in the parameter area. The + symbol beside an icon indicates that this branch of the Navigator can be expanded to display sub-components.

Adding and Deleting Configuration Components

Modifying Parameters

WAN Services Configuration Program Menus


Chapter 3: WAN Services Configuration

Navigating through WAN Services Configuration

Adding and Deleting Configuration Components

Once you have finished setting the parameter values for a particular configuration component on the Navigator, you may click the √ button or another item in the Navigator to retain them or the X button to cancel your entries.

Each time a change or addition is made, the Navigator reflects the modifications to the logical configuration path. With this mechanism, you can select any component directly, and then modify the desired parameters in the parameter area. In addition, the WAN Services Configuration program scans the Navigator to detect which components, if any, are affected by a change. See the “Scanning for Dependencies Utility” topic provided by the online help.

Once you leave a configuration panel and select another item in the Navigator, all newly configured parameters are automatically stored in memory.


Chapter 3: WAN Services Configuration

Navigating through WAN Services Configuration

Modifying Parameters

When a parameter is changed, all parameters affected by the change in the current configuration panel are updated. In addition, if these changes affect parameters in other WAN Services components, a warning message appears displaying the names of the affected parameters.

WAN Services will not enable you to proceed to the next parameter or configuration panel if there is an invalid entry anywhere on the current panel. Also, all required parameters must be configured for proper functionality.


Chapter 3: WAN Services Configuration

Navigating through WAN Services Configuration

WAN Services Configuration Program Menus

The following table describes all the available menu options.

File Menu

Option	Description
Save...	Saves the WAN Services configuration that is currently displayed in the Windows NT registry.
Exit Alt-F4	Closes all WAN Services windows and exits the WAN Services Configuration program.
Parameters Menu

Option	Description
Confirm entries	Saves all changes made to the configuration panel currently displayed.
Cancel	Cancels all changes made to the current configuration panel.
Edit entry	Invokes the configuration panel for certain configurable parameters.
Advanced	When selected the current panel displays additional parameters.
Help Menu

Option	Description
Contents	Contains general help topics for WAN Services.
Index	Displays descriptions about the WAN Services configuration parameters.
About	Copyright and version information for the WAN Services Configuration program.
Online Help

Included with the WAN Services Configuration program is extensive and context-sensitive online help descriptions for each configuration parameter. Just place your cursor on the parameter you are interested in and press “F1.”

Note:
You may wish to have the WAN Services Configuration Online Help window open while configuring your WAN Services components. To do this, choose the Always on Top command from under the Help menu. You can then position the online help window beside the configuration panel and make it easier to refer to when setting the parameters.

The WAN Services Configuration Online Help provides information that will greatly facilitate the WAN Services configuration process. The following topics are covered online:

•	About the WAN Services Configuration Program

•	The Navigator: An Overview - displays a graphical representation of each WAN Services component and subcomponent as well as a brief description

•	Using the Navigator - describes how to move around the Navigator and access information quickly and easily

•	Commands and Buttons - complete descriptions of all toolbar buttons, menu options, and on getting help

•	 Alphabetical index of all program parameters showing the valid ranges and default values (click Index button)

•	Glossary of networking terms (click Glossary button)


Chapter 3: WAN Services Configuration

Starting WAN Services Configuration

The WAN Services Configuration program is a native Windows NT application. After installing the EiconCard(s) and related Eicon Services through the Network Control Panel Applet (NCPA), the EiconCard must then be configured.

To start the WAN Services Configuration program, double-click on the WAN Services Configuration icon in the WAN Services group in Program Manager.

This section contains a step-by-step description to configure your EiconCard(s).

Configuring the EiconCard


Chapter 3: WAN Services Configuration

Starting WAN Services Configuration

Configuring the EiconCard

Each EiconCard installed in your WAN Services PC is represented by an EiconCard icon. WAN Services can support up to six separate EiconCard configurations (Micro Channel supports up to four EiconCards). See the section “EiconCard Installation”.

Each EiconCard component contains a number of different configuration views that let you adjust parameters in the following areas:

•	EiconCard Configuration

•	High-Level Protocols

•	Line Protocols and Dialers

Router Connections

Configure the router connections as described in “Configuring the Router Connections”.


EiconCard Configuration

This component displays the currently configured parameters for the specified EiconCard. You are not able to alter the settings for Slot *Position, IRQ Level, Memory Segment Address, and I/O Port Address with the WAN Services Configuration program. These parameters were set when you first installed the EiconCard through the Network Control Panel Applet (NCPA). To reconfigure these parameters, see “Reconfiguring the EiconCard properties.”

⇒	To configure the EiconCard:

1.	Click the EiconCard icon to display the EiconCard configuration panel.

Note:
If you are configuring an EiconCard S51, make sure that you choose the correct switch which is determined by the region where the protocol is being used. Currently, WAN Services supports four different implementations of ISDN: Euro-ISDN (Europe), NI-1 (North America), 5ESS (AT&T North America), and TPH1962 (Australia).

2.	You are not able to alter the settings for IRQ Level, Memory Segment Address, and I/O Port Address with the WAN Services Configuration program. These parameters were set when you first installed the EiconCard through the Network Control Panel Applet (NCPA). To reconfigure these parameters, see “Reconfiguring the EiconCard properties.”

Note:
If you reconfigure the “IRQ Level,” “I/O Port Address,” or “Memory Segment Address” parameters, you must shutdown and reboot your system.

3.	Click the √ button on the toolbar to save the parameter settings for the EiconCard.


High-Level Protocol Configuration

This version of WAN Services for Windows NT supports Transport Bull TGX, Transport ISO, and Connection Manager high-level protocols.

Transport

WAN Services supports both ISO and Bull TGX transport implementations, however, both are only required to support third-party applications.

Connection Manager

Connection Manager is a high-level service that is required by WAN Services IP Routing Services. It also defines the operating environment in which the router functions, such as the maximum number of connections, and the maximum number of connection manager sessions. Connection Manager also handles data compression for X.25, PPP, and Frame Relay subnetworks.

Note:
Unless you are using IP Routing Services, do NOT enable Connection Manager, as it will needlessly consume EiconCard memory.

⇒	To configure the High-Level protocols:

1.	Click the High-Level Protocols icon to display its configuration panel.

2.	Select the high-level protocols that you need for your particular communications setup by clicking the box beside the protocol that you wish to enable. When there is an x beside a protocol, it is selected.

3.	Click the √ button on the toolbar to save your selections and then click the High-Level Protocol icon to update the Navigator.

4.	Configure each high-level protocol by clicking its corresponding icon. This displays the appropriate configuration panel for that protocol, where you can configure the necessary parameters. For most protocols, the default parameters should suffice.


Port Configuration

The configuration program also lets you assign protocols and dialer options on a per port basis. Line protocols handle the data transfer.

Important:
The Port Number specified here must match the port number which was assigned in the Eicon NDIS Logical Adapter configuration panel and the Port Number in the Router Connection configuration panel.

Line Protocols Supported

Dialer Selection

Altering Protocol Parameters

Restarting the EiconCard

⇒	To configure line protocols

1.	 Double-click the Port icon to expand the branch and view the complete tree of line protocols and dialer types.

2.	Select the Line Protocol and Dialer type that you will be using.

3.	Click each protocol and dialer subcomponent in the tree and alter the settings as required.

4.	Click the √ button to save your selections. This will automatically update the Navigator.

Note:
If you select more than one Port for an EiconCard you will have multiple Line Protocol Modules and Dialer Selections to configure. Once you configure High-Level Protocols for an EiconCard, they are available to all ports on the card, but used only as needed.

Important:
If you decide to change the line protocol type on your EiconCard port after you have configured the router connections, all the router connections configured for that line type must be modified to reflect this change. You can choose to manually change associated resource parameters or have it all done automatically. See the “Scanning for Dependencies Utility” online help topic for complete details.


Line Protocols Supported

The configuration program supports the following line protocols through the physical ports of the EiconCard.

X.25

X.25 is an international standard for data communications. It is supported in almost every country of the world. WAN Services Configuration supports CCITT Recommendation 1984 and 1988 and TOA/NPI addressing. Choosing X.25 automatically includes HDLC.

SDLC

SDLC (Synchronous Data Link Control) is the primary data link protocol used for wide-area network connections within SNA. It is used to manage information exchange across a single physical data link between two nodes. SDLC is part of the original design of SNA, and is the foundation upon which all other connections are based. The EiconCard supports point-to-point, multi-point, and switched SDLC links.

Frame Relay

Frame Relay is a multiplexing protocol designed to operate on today’s virtually error-free transmission facilities. Frame Relay delivers higher throughput than X.25 can achieve but with the sacrifice of some of X.25’s error checking capabilities.

Point-to-Point Protocol

The Point-to-Point Protocol (PPP) is a synchronous communications protocol developed in the Internet world to encapsulate IP protocol for transmission over a point-to-point link. It was designed for the purpose of interconnecting routers, and it automatically handles the negotiation of communications parameters when establishing connections.


Dialer Selection

The WAN Services Configuration program supports a number of options for dialing both internal and external modems. Choose one of these options based on the EiconCard and line type you are using:

•	Direct (hardware dialer)

•	Hayes AT (asynchronous dialer)

•	V.25bis

•	V.22bis

•	V.32bis

•	B-channel (ISDN)

•	SIG.+X.25 (ISDN)


Altering Protocol Parameters

Each protocol has a number of parameters associated with it. These parameters let you customize the protocol software for your particular connection. However, in most cases you will not have to change the default values of these parameters.

WAN Services protocols can be configured to suit almost any communications situation. This control is achieved through hundreds of parameters in over twenty different protocol configuration views in the WAN Services Configuration program.

Since there are so many types of equipment, switches, and networks with which WAN Services can interact, there can be uncertainty about which parameters need to be changed. To simplify the configuration process, the best possible default values have already been determined for each protocol parameter, and in most cases the parameters do not need to be changed.

Changing Default Values

In some cases, you will have to change the default values of certain parameters. Here are a few ways to discover which protocol parameters to change and how to determine their proper values.

•	When you are connected to an X.25 network, you should be provided with documentation on the characteristics of that network. Go through each parameter of the X.25 network, and make sure that each WAN Services configuration parameter value matches the X.25 network parameter value. For example, if the X.25 network has a default packet size of 256, and the WAN Services configuration parameter is set to a default packet size of 128, then you may encounter problems transmitting data over the X.25 network. If such documentation has not been provided, then contact the agency that installed the connection, and request this information.

•	When connecting to a host using SDLC, you must make sure that parameters such as your window and frame size match those of the host. For example, WAN Services configuration frame size is set to a default of 267 octets. If the hosts frame size is different, you will encounter problems transmitting data. If you do not know the hosts parameter values, contact the hosts system operator.

•	Similarly, you should have also received documentation about network characteristics such as your DLCI(s) and the N1 through N3 parameters when you subscribed to a Frame Relay network. You should ensure the best possible match between the WAN Services Configuration values for Frame Relay and those used by your Frame Relay network.


Restarting the EiconCard

Each time you reconfigure the EiconCard port, High-Level protocol, the line protocol, or the dialer, the EiconCard must stopped and restarted with the commands:

  ECCARD STOP
  ECCARD START

For information on the ECCARD command, see “ECCARD: Starting the EiconCard”.


Chapter 4: IP Routing Services

This chapter explains what a router is, and covers some basics about TCP/IP. It also explains how to configure the Eicon IP Routing Services (NDIS driver) and explains how to configure the router connections using the WAN Services for Windows NT Configuration program.

We recommend that you read through this introductory explanation of routing and TCP/IP. To configure the IP Routing Services, see Configuring the IP Routing Service.

Router Functions

Transparency to Upper Layers

Functions

Circuits and IP Mappings

The TCP/IP Protocol Suite

IP Routing Services and Device Drivers

Configuring the IP Routing Service

Gathering Information

Circuit Management for Multipoint Routing

Configuring the Router Driver and NDIS Adapter

Configuring the Router Connections

Step 1: Starting the WAN Services Configuration Program

Sample Configuration

Using Command Line Utilities


Chapter 4: IP Routing Services

Router Functions

A router is a combination of hardware and software that interconnects two or more local-area networks. Like a bridge, the interconnection can be local or remote. Each router connects multiple LANs together at OSI Layer 3, and requires that all LANs use the same network protocol. Multiple routers can be installed on a LAN to provide additional links.

Transparency to Upper Layers

Functions

Circuits and IP Mappings

The TCP/IP Protocol Suite


Chapter 4: IP Routing Services

Router Functions

Transparency to Upper Layers

Each router is concerned only with the packets of the networks that it is linking. This makes them transparent to anything above the network layer, and also independent of the LAN topology. This makes it possible for routers to connect LANs with different topologies (for example, Token-Ring and Ethernet), as long as both use the same network protocol.


Chapter 4: IP Routing Services

Router Functions

Functions

A router is more complicated than a bridge. The router must:

•	maintain routing tables that describe the internetwork configuration

•	receive packets intended for a remote LAN

•	determine the destination and appropriate path using the routing table

•	update the routing table as changes occur in the internetwork (congestion, link failure, etc.)

As a result of this added capability, routers require more processing power than bridges to achieve similar throughput. However, they typically have little difficulty in dealing with network problems.


Chapter 4: IP Routing Services

Router Functions

Circuits and IP Mappings

In the chapters that follow, particularly in discussions of the IP Routing Services command line utilities and router management, you will see frequent references to circuits and IP mappings. You may find it useful, before attempting to configure and start your router, to read the definitions provided below for these two terms.

A circuit is a potential router-to-router connection: a kind of database record containing all the information required to establish a connection between two routers—the local router and the remote router—over a wide area networking (WAN) medium. However, it does not contain the critical piece of information required to route Internet Protocol (IP) protocol packets back and forth between two routers: the IP address of the remote router.

An IP mapping is an association between a circuit and that remote IP address; IP mappings are also database records of a kind. You can think of a IP-routing connection between two routers as consisting of one circuit plus one IP mapping.


Chapter 4: IP Routing Services

Router Functions

The TCP/IP Protocol Suite

The TCP/IP protocol suite consists of three main protocols: IP (Internet Protocol), UDP (User Datagram Protocol), and TCP (Transmission Control Protocol).

The IP Protocol

The Internet Protocol (IP) makes up the lower layer of the TCP/IP protocol suite. Its main purpose is to route individual datagrams locally to other LAN card connections on the same LAN, and to route datagrams remotely by sending them on the first leg (hop) of their journey. IP Routing Services accepts datagrams targeted by IP for remote delivery and sends them across a WAN.

IP is concerned with individual IP datagrams. TCP handles grouping of datagrams into logical data streams.

The TCP Protocol

The TCP protocol resides one layer above IP. It provides higher-level features such as connection-oriented virtual circuits and reliable stream-oriented data exchange.

The UDP Protocol

The User Datagram Protocol provides the main mechanism that applications use to transmit datagrams to other applications. UDP also resides above the IP layer. It provides protocol ports that are used to distinguish among multiple programs executing on a single source. UDP is a connectionless service that provides an unreliable, but very efficient, data exchange.

IP Routing

IP datagrams, the basic IP information units, are sent to a local LAN connection by the originating host if the destination host is on the same network. If the destination host is on a different network, the datagram is sent to a Router on the local LAN which routes it toward its destination.

The word “toward” is used here since only the address of the next Router is processed by IP. If the destination host is not directly connected to the LAN that the Router connects to, the Router looks up the IP address of the next Router that lies along the path to the ultimate destination system. The Router then passes the datagram on to the next Router. This is continued until the ultimate destination Router is reached and the datagram is sent by IP over the LAN card to the destination host.

TCP/IP Application Protocols

A set of four TCP/IP application protocols are provided on most TCP/IP systems. These protocols provide basic services such as remote terminal access (TELNET), file transfer (FTP), and electronic mail (SMTP). The application protocols and their expanded abbreviations (where applicable) are as follows:

•	TELNET

•	FTP (File Transfer Protocol)

•	SMTP (Simple Mail Transfer Protocol)

•	RPC (Remote Procedure Call)


Chapter 4: IP Routing Services

IP Routing Services and Device Drivers

IP Routing Services are installed as the Eicon NDIS Router service, and the Eicon NDIS Interface Driver for EiconCard device driver. This service and device driver can be started, stopped, and their startup method configured, with the Services or Drivers applet through Control Panel. Eicon Technology recommends that you leave the startup methods at their defaults to ensure proper functioning of WAN Services for Windows NT.

To use the NET START and NET STOP commands with the Eicon NDIS Router service and Eicon NDIS Interface Driver for EiconCard device driver, use EICONNDISROUTER and ECNDIS, respectively. The example below first starts the Eicon NDIS device driver and then starts the Eicon NDIS Router service.

NET START EICONNDISROUTER
NET START ECNDIS

The ECNDIS driver is dependent on a number of other services. Therefore, to reinitialize the ECNDIS device driver Eicon Technology recommends rebooting your WAN Services PC to re-enable the ECNDIS driver, rather than using NET STOP ECNDIS and/or NET START ECNDIS.

IP Addresses (Dynamic Routing) and Microsoft RIP

WAN Services for Windows NT is fully compatible with Microsoft RIP (Routing Information Protocol) The RIP service enables the router to automatically update its routing tables for remote routers while operating. This is known as dynamic routing.

If you choose not to use the Microsoft RIP service, the router relies on static routing to properly route network data to any remote router. In this case, you must create a routing table that maps the IP address of the remote LAN to the IP address of the router on that LAN. This is done with the ROUTE command included as part of the Windows NT TCP/IP package.


Chapter 4: IP Routing Services

Configuring the IP Routing Service

This section explains how to configure the IP Routing service, the Eicon NDIS driver, and how to configure the router connections.

Gathering Information

Circuit Management for Multipoint Routing

Configuring the Router Driver and NDIS Adapter


Chapter 4: IP Routing Services

Configuring the IP Routing Service

Gathering Information

Before attempting to configure IP Routing Services, it is important to plan your network connections and have all pertinent information on hand. The following section explains what information you will need to successfully configure IP Routing Services.

Bindings with NDIS Adapters

If you are configuring multiple EiconCard ports, it is recommended you keep track of the following information so that these numbers are used accurately elsewhere:

•	Eicon NDIS Adapter numbers which are determined by the NetWork Control Panel Applet (NCPA)

•	NDIS port numbers which are configured in the NCPA (these are the same numbers used to define the Eiconcard ports)

•	EiconCard ports which are configured in the WAN Services Configuration program

•	Associated IP addresses which are configured in the TCP/IP Configuration program

You can use this information with the WAN Services Configuration program and the MPRCCT and IPMAP commands:

Adapter Number	Adapter Name	EiconCardPort Number or NDIS Port Number	Local IP Address
[09]	Eicon NDIS Adapter	1	200.200.2.1
[10]	Eicon NDIS Adapter	2	200.200.3.1
[11]	Eicon NDIS Adapter	3	200.200.4.1
Note:
You can verify the “Adapter Name” and “IP Address” information in by typing “IPCONFIG” or “MPR CONFIG” at the command prompt.

The Windows NT Adapter numbers in column 1 have no direct relationship to the EiconCard Port Numbers in column 3. The Eicon port numbers are defined in the WAN Services Configuration program.


Chapter 4: IP Routing Services

Configuring the IP Routing Service

Circuit Management for Multipoint Routing

If you are building a WAN with X.25 or Frame Relay, you need to define the list of circuit names that you are going to use. A circuit is the virtual connection that links a local LAN to a remote LAN. Eicon Technology suggests making photocopies of the following configuration checklists, for each connection you need to configure.

X.25 Circuits

Associate each circuit name with the X.25 address of the WAN Services PC on the local LAN, and the X.25 address and IP address of the WAN Services PC on the remote LAN.

You will use this information with the WAN Services IP routing services MPRCCT and IPMAP commands.

Local Router Circuit Name	Local Router X.25 Address	Remote Router X.25 Address	Remote Router IP Address
Frame Relay Circuits

Associate each circuit name with the Data Link Control Identifier (DLCI) of the WAN Services PC on the local LAN and with the IP address of the WAN Services PC on the remote LAN.

Circuit Name	Local DLCI	IP Address of Remote Router
IP Addresses

Collect all the IP addresses of the remote LANs and their Routers.

WAN Services includesfull support for the Microsoft RIP service, which greatly increases the ease of IP address management between your routers. See “IP Routing Services and Device Drivers” for more information.

Remote LAN Name	IP Address of Remote LAN	IP Address of Remote Router


Chapter 4: IP Routing Services

Configuring the IP Routing Service

Configuring the Router Driver and NDIS Adapter

This section explains how to configure the Eicon router driver and Eicon NDIS logical adapter.

The IP Routing service and Eicon NDIS driver are configured through the NCPA. See “Install Optional Services Software”, for information on how to install IP Routing Services. You must install one instance of the NDIS driver for every Eicon port you wish to use with the IP Routing Services.

⇒	Follow these steps for configuring the Router Driver and NDIS Adapter:

1.	From the NCPA, highlight the “Eicon Router Driver” entry in the Installed Network Software list, and click Configure.

2.	The Eicon Router Driver dialog box appears.

These parameters apply globally to all router connections. Consult online help, by clicking Help or by pressing “F1”, for a definition of each parameter. Click OK when you are done.

3.	Highlight an Eicon NDIS Logical Adapter entry from the Installed Adapter Cards list, and click Configure.

4.	The configuration dialog box for the Eicon NDIS Logical Adapter is displayed. Each Eicon NDIS Logical Adapter must be assigned to use a unique EiconCard port. Specify a valid EiconCard port number and click OK.

5.	Repeat step 4 for every instance of the Eicon NDIS Logical Adapter in the Installed Adapter Cards list.

Important:
The Port Number specified here must match the port number which was assigned in the WAN Services Configuration program’s Port configuration panel (see “Port Configuration”) and the Port Number in the Router Connection configuration panel (see “Step 1.1: Router Connection Configuration”).

6.	From the Network Control Panel dialog box, click the Bindings button.

7.	Windows NT automatically binds all new adapters to all installed services and/or protocols. However, all Eicon NDIS Logical Adapters should only be bound to the following:

TCP/IP Protocol
Server
Workstation

Use the Disable button to unbind each Eicon NDIS Logical Adapter from the following:

NetBIOS Interface
NetBEUI Protocol
NWLink IPX/SPX Compatible Protocol

Click OK.

8.	To close the Network Settings dialog box, click OK.

9.	The TCP/IP configuration dialog box automatically appears. Choose each installed Eicon NDIS Logical Adapter from the Adapter drop-down list, and specify an IP address and subnet mask, then click OK.

Note:
The Adapter number and IP Address specified here must be recorded for proper referencing. See “Bindings with NDIS Adapters” for an information table.

To configure router connections and IP filters you must now use the WAN Services Configuration program. See “Configuring the Router Connections” for more information.

Note:
Before you shutdown and restart the WAN Services system, ensure that you have configured your router connections using the WAN Services Configuration program.


Chapter 4: IP Routing Services

Configuring the Router Connections

WAN Services IP Routing Services software lets you interconnect IP LANs for transparent sharing of data and resources between all LAN users.

The WAN Services Configuration program is used only once when first configuring your router connections. Once the router is running, all other additions or modifications to connections can be done via router command line utilities. For more information on the router command-line utilities, see Chapter 9, “Command Line Utilities.”

Configuration parameters required for IP Routing Services include information on the type of connection (e.g. data compression on or off), and the remote router itself (e.g. DTE address).

The configuration program enables you to configure point-to-point or multi-point lines to other LANs. For multi-point connections, individual connection entries must be made for each possible router connection.

The WAN Services Configuration program is used to define all the possible connections which may be established between the local router and remote router. This information is stored in the MPR.INI file (see Chapter 11), and includes details on the local and remote router along with connection information, such as the DTE addresses of each router and the WAN protocol used.

Each remote router can be:

•	Another WAN Services server

•	An Eicon Technology InterConnect Server or Router

•	A Eicon Technology V3R2 or higher Router for NetWare (NLM)

•	A third-party router which implements one or more certain "Requests for Comments (RFCs) related to wide-area networking. RFCs are documents issued by the Internet Engineering Task Force (IETF) and are widely used as standards. For more information, see Appendix D, “Router Interoperation.”

About Connections, Circuits, and IP MAPs

Dynamic Configuration

About the Database

To configure the router connections, see "Step 1: Starting the WAN Services Configuration Program."


About Connections, Circuits, and IP MAPs

WAN Services for Windows NT provides three mechanisms for creating, deleting, or modifying connections between the local IP Router Services and remote routers:

•	the WAN Services Configuration program

•	use this to permanently setup your router connections, circuits, and IP mappings

•	cannot be used to dynamically add delete or modify router connections, circuits, and IP mappings

•	the Eicon SNMP Console

•	used to remotely dynamically add, delete or modify router connections, circuits, and IP mappings

•	the dynamic changes to the router are not recognized in subsequent use of the WAN Services Configuration program

•	any connection created dynamically must be recreated with the WAN Services Configuration program before the configuration is saved

•	the combination of the MPRCCT and IPMAP commands

•	used to locally dynamically add, delete or modify router connections, circuits, and IP mappings

•	the dynamic changes to the router are not recognized in subsequent use of the WAN Services Configuration program

•	any connection created dynamically must be recreated with the WAN Services Configuration program before the configuration is saved


Dynamic Configuration

You can use the WAN Services Configuration program to create, modify, and delete IP mappings and circuits, and in fact this is the best way to do this. However, if you create or delete mappings and circuits while the router is running (dynamically changing the current configuration of the router) using the MPRCCT and IPMAP utilities or the Eicon SNMP Console, these changes will not be displayed the next time you run the WAN Services Configuration program.

This is because:

•	When the WAN Services Configuration saves the current configuration, it records both the entire configuration in the Windows NT registry, and saves different parts of it to a number of files including MPR.INI, and

•	The MPRCCT and IPMAP utilities and Eicon SNMP Console can only modify MPR.INI, not the Windows NT registry used by the WAN Services Configuration program.

Note that changes made to MPR.INI by the MPRFLT utility cannot be displayed by the WAN Services Configuration program either.

Information WAN Services requires about connections with remote routers is stored in a file called the connection database (MPR.INI).

Note:
Modifying circuits with the command line utilities MPRCCT, MPRFLT, and IPMAP does not change the Windows NT registry information used by the WAN Services Configuration program. Therefore, if you start Configuration program after making changes with MPRCCT, these changes will not be reflected in the configuration you see. They are only added to the MPR.INI file.


About the Database

The connection database described above is contained in a file named MPR.INI. This file is located in the directory containing your WAN Services Configuration program and configuration files residing on your WAN Services PC. Each database record contains data such as the nature of the remote router, its address (if applicable) on the wide area networking medium, and information about the router-to-router connection. Examples of router-to-router connection information include the WAN communications protocol that will be used to connect the routers, and whether or not the data transmitted between them will be compressed.

Note that each record represents a potential connection between the local router and a remote router. You turn them into active connections either by defining them as Auto Start before starting the router software, or by activating them with the Eicon SNMP Console while the router software is already running. For further information, see “Managing Routing Services”, in Chapter 8 and see Chapter 11, “The MPR.INI Initialization File.”


Chapter 4: IP Routing Services

Configuring the Router Connections

Step 1: Starting the WAN Services Configuration Program

Before configuring the router connections, you must first configure the EiconCards, EiconCard ports, and their associated line protocols. This information is needed as the router connections are associated with the individual EiconCard ports. For information on how to configure your EiconCard, see Chapter 3, “WAN Services Configuration.”

⇒	To start WAN Services Configuration program:

1.	Open the WAN Services group in Program Manager. This group was created when WAN Services was installed.

2.	Double-click the WAN Services Configuration program.

Step 1.1: Router Connection Configuration

Step 1.2: Configuring IP Packet Filters

Step 1.3: Setting Up Dial-on-Demand

Step 1.4: Creating Backup Links


Chapter 4: IP Routing Services

Configuring the Router Connections

Step 1: Starting the WAN Services Configuration Program

Step 1.1: Router Connection Configuration

The Router Connection configuration panel allows you to add or modify router connections.

⇒	To configure router connections:

1.	To add a new router connection, double-click the Router icon to expand the tree if it is not already so.

2.	Click on the Connection icon to bring up the Connection panel.

3.	Click inside the Connection panel, and from the configuration toolbar, click Insert, or press the “Insert” key on your keyboard.

4.	To modify an existing connection, select the connection from the displayed list and press enter or double-click it.

5.	From the Router Connection Information panel, set parameter values for the connection as necessary. Context-sensitive help for any parameter is available by pressing “F1.”

6.	Under WAN Protocol, select the wide area networking protocol.

Note:
WAN Protocol lists only those communications protocols you have selected as the Line Protocol for at least one EiconCard port.

7.	Check Auto start if you want this connection to be established as soon as the router software is started.

Note:
After router startup, you must use the Eicon SNMP Console or command line utilities to manually start any router connections which you do not configure as Auto start.

8.	Under Connection Usage, select “Backup” if this connection will back up a primary connection you have already created.

Note:
You cannot designate a connection as “backup” if no primary connections exist. See “Step 1.4: Creating Backup Links” for more information.

9.	Click the √ button to modify this router connection, or add it as a new entry in the Router Connection information panel.

Deleting Connections

The Router Connection configuration panel allows you to add or modify a router connection.

⇒	To delete router connections:

1.	From the Connection panel, highlight the router connection you want to delete.

2.	From the configuration toolbar, click Delete, or press the “Delete” key on your keyboard.


Chapter 4: IP Routing Services

Configuring the Router Connections

Step 1: Starting the WAN Services Configuration Program

Step 1.2: Configuring IP Packet Filters

For any connection (circuit + IP mapping) you configure between the local router and a remote router, you can create one or more filters to be applied to IP packets being transmitted between the local and remote routers.

The IP packet filter serves two main purposes:

•	Provides security of the local network and resources from unauthorized user access

•	Preserves the bandwidth of the WAN circuits and limits the use of WAN links by local users

IP filtering is configurable for each router connection created. You can have WAN Services drop or forward IP packet types to any direction using the TCP, UDP, or All port type. Each connection may have more than one connection filter applied to it.

Filter Effects

Tips

Addresses and Masks

IP Filters and Port Numbers

Examples

⇒	To configure IP Packet Filtering:

1.	Select the Router Connection subcomponent by clicking its icon from the Navigator to display a panel similar to the following:

2.	You will first need to configure a router connection before requesting a filter of IP packets to that connection. See “Step 1.1: Router Connection Configuration” for more information.

3.	Once you have configured a connection, you can configure an IP filter. To do this:

a.	Highlight the router connection to which you want to assign an IP filter

b.	Click inside the IP Filter panel

c.	Click the Insert button on the toolbar

4.	Complete the general parameters on the Connection Filter dialog box as required. Press the “F1” key to display online help for the requested parameter.

5.	If desired, you may create another IP filter for the same connection. Ensure that the same connection is still highlighted. From the IP Filtering panel, press the Insert button to display the Connection Filter dialog box.

The order in which the connection filters are created is important. For each packet being transmitted, the router scans the filter list from top to bottom. On a matching filter, the action specified is applied to the packet.

Note:
If no match is found, the packet is forwarded to its destination.


Filter Effects

A filter does one of two things to packets that match the parameters it contains: they are either forwarded or dropped. All packets are forwarded for a connection for which you create no IP packet filters; the WAN Services Configuration program allows you to create a filter that can forward packets because you may need a sequence of two or more filters to achieve exactly the filtering effect you want for a particular connection.

The order in which filters will be applied is the order in which they are displayed in the Filters section of the Router Connections configuration panel. This section shows the filters, if any, for the currently selected connection.


Tips:

•	The more filters you put on a circuit, the more processing has to be done for every packed handled. Performance will drop accordingly.

•	Plan the filtering process well to make sure that you do not have redundant filters in the chains.

•	Make use of the IN and/or OUT keywords to make sure that you process packets only in the direction that they are meant to be processed.

•	Filters only apply on directed packets, not broadcasted packets (MAC destination address 0xFFFFFFFFFFFF).


Addresses and Masks

If you are not very familiar with IP subnet or address masks and how they interact with IP addresses with respect to IP routing, Eicon Technology recommends you read the following before attempting to set the Source and Destination IP Address and Mask parameters for your IP packet filters.

IP addresses are composed of four eight-bit numbers, each of which can have a value between 0 and 255, for a total of 32 bits. A source or destination address in an IP packet “matches” the one you specify in a filter if the value of each of the 32 bits is identical. However, before WAN Services actually compares the two addresses, it performs a binary mathematical operation called a bitwise AND with the packet’s IP address and the value of Mask. The result of this operation is what WAN Services compares with all or part of the IP address you specify.

A bitwise AND compares each of the corresponding bits, each of which can have a value of 1 or 0, in two binary numbers. The results of a bitwise AND is also 1 or 0 for each bit, but it is only 1 if both the compared bits are 1. Therefore,

  11001100 AND 00000000 = 00000000

  11001100 AND 11111111 = 11001100

  11001100 AND 10101010 = 10001000

What this allows you to do with the Mask and IP Address parameters you specify for a filter is match a range of source and/or destination IP addresses. The simplest and most common way to do this is by setting the same parts of Mask and IP Address to 0, and the remaining parts of Mask to 255.


IP Filters and Port Numbers

The Destination Port field of any TCP or UDP data packet contains a number between 0 and 65,535. This TCP/UDP port number is used to identify or target a particular application running on a TCP/IP-enabled computer where two or more applications may be running simultaneously. On UNIX systems, where the TCP/IP protocol suite originated, multitasking is a fact of life.

A substantial number of Destination Port values have been assigned to specific applications commonly executed on TCP/IP-enabled computers. Therefore, when you are configuring IP packet filters for WAN Services for Windows NT, the High Port and Low Port parameters can be used to drop or forward packets based on the application that transmitted them, or should receive them.

The table below lists some of the most commonly used TCP/UDP port numbers assigned to specific applications. For a complete and up-to-date listing of these assignments, refer to Request for Comments (RFC) 1700, “Assigned Numbers,” by J. Reynolds and J. Postel.

Configuration of the Port Numbers in Decimal

Port Number (decimal)	Application
5	RJE
7	ECHO
11	DISCARD
13	USERS
15	NETSTAT
17	QUOTE
19	CHARGEN
20	FTP-DATA
21	FTP
23	TELNET
25	SMTP
37	TIME
39	RLP
42	NAMESERVER
43	NICNAME
53	DOMAIN
67	BOOTPS
68	BOOTPC
69	TFTP (Trivial FTP)
75	Any private dial-out service
77	Any private RJE service
79	FINGER
82	XFER UTILITY
95	SUPDUP
101	HOSTNAME
102	ISO-TSAP
113	AUTH
115	Simple File Transfer Protocol
117	UUCP-PATH
118	SQL Service
123	NTP
137	NetBIOS Name Service
138	NetBIOS Datagram Service
139	NetBIOS Session Service
161	SNMP
162	SNMPTRAP
520	Local Routing Process (RIP)


Examples

•	To match any source IP address that begins with 128.252.135, set Source IP Address to 128.252.135.0 and Source Mask to 255.255.255.0. With Direction set to OUT and Action set to Drop, this would prevent workstations with IP addresses from 128.252.135.0 through 128.252.135.255 from sending IP packets across the connection. To prevent them from receiving packets would require another filter.

•	To reject incoming IP packets from remote IP address 184.4.99.4, set Direction to IN, Action to Drop, Source IP Address to 184.4.99.4, and Source Mask to 255.255.255.255.

•	To deny access to remote network 131.28.0.0 to all but the workstation with IP address 129.192.20.221 (i.e., the network manager’s) requires a total of three filters.

•	Source IP Address = 129.192.20.221, Source Mask = 255.255.255.255, Destination IP Address = 131.28.0.0, Destination Mask = 255.255.0.0, Action = Forward, Packet Direction = OUT

•	Source IP Address = 131.28.0.0, Source Mask = 255.255.0.0, Destination IP Address = 129.192.20.221, Destination Mask = 255.255.255.255, Action = Forward, Packet Direction = IN

•	Source IP Address = 0.0.0.0, Source Mask = 0.0.0.0, Destination IP Address = 0.0.0.0, Destination Mask = 0.0.0.0, Action = Drop, Packet Direction = ALL

A sequence of filters combined in this way to perform a single task is known as a filter chain. Note that while the third filter effectively drops all packets going in both directions, this would not affect the packets forwarded by the first two filters as long as they precede the third filter in the displayed list of filters for this connection.

Some other points:

•	If you want to filter packets based only on non-address-related parameters, set all IP address and mask parameters to 0.0.0.0. Of course, you can also combine address-related restrictions with restrictions based on TCP port number and/or port type.

•	While the examples described above do not refer to the Port Type, Port - Low and Port - High parameters, these parameters should not be ignored when you are attempting to configure your own IP packet filters. Their default values may be completely inappropriate for your situation; see the online help for these topics for more information.


Chapter 4: IP Routing Services

Configuring the Router Connections

Step 1: Starting the WAN Services Configuration Program

Step 1.3: Setting Up Dial-on-Demand

Dial-on-demand is a feature of WAN Services you can use to minimize connect-time charges for dial-up router connections to X.25 or Frame Relay networks or PPP connections. It works by keeping the physical connection to a wide-area network inactive when no virtual circuits have been using the physical connection for a specified length of time.

Understanding Dial-on-Demand

Depending on the communications protocol used, many packet-based virtual (or “logical”) connections can be multiplexed over a single physical link. This means that not only is the physical link able to be “opened” or “closed,” but so can each multiplexed logical connection carried on the link.

Because there are two levels of connection and disconnection, there are also two levels of idle timeouts:

1.	One for each virtual circuit (VC) using a physical connection. This timeout is set within the Router Configuration Information panel for “router connections”. If no packets have been sent and/or received for a specified number of seconds, then the VC is closed.

2.	One for the physical connection itself. This timeout is set when configuring the “line protocol” for the EiconCard port that the connection uses. The line is dropped when no VCs have been open for the specified number of seconds.

Note:
The physical line is dropped at the dialer level.

RIP and Broadcasts

Microsoft RIP (Routing Information Protocol) service enables the router to automatically update its routing tables for remote routers while operating. This is achieved by the routers broadcasting RIP packets to each other. RIP broadcasts must be disabled in order for dial-on-demand to work, as the RIP broadcasts would keep the line up indefinitely.

RIP can be controlled on either a global or per connection basis.

•	To disable RIP on all ports, disable the Microsoft RIP service through the Services applet in Control Panel

•	To disable RIP on a per-connection basis, uncheck the Broadcast parameter in the Router Configuration Information panel in the WAN Services Configuration program

Making Dial-on-Demand Work

A physical connection can only be closed if no VCs are currently using it. If even one virtual circuit, that is used by a WAN Services component, is configured to remain idle indefinitely (no timeout), the physical connection always remains open. No connect-time savings are possible.

There are two elements to making Dial-on-demand work effectively for X.25 SVC (switched virtual circuits):

1.	Ensure that for all the routing connections you have configured, the Inactivity Timeout parameter does not have a value of 0. A value of 0 corresponds to a “never-time-out” condition.

2.	Set the X.25 line timeout parameter (Idle Timer) to a relatively small value. If you keep the line open for too long after all virtual circuits have been closed, VCs may be reopened before the physical connection can be terminated.

For Frame Relay and PPP there is only one element to set for Dial-on-demand.

•	Set the line timeout parameter (Idle Timer) to a relatively small value, in the “line protocol” configuration panel.


Chapter 4: IP Routing Services

Configuring the Router Connections

Step 1: Starting the WAN Services Configuration Program

Step 1.4: Creating Backup Links

WAN Services gives you a way to protect against the unexpected failure of the physical or logical link between the local server and a remote router.

This feature is called Dial Backup, and enables you to configure a backup connection for any primary connection between the local WAN Services and remote router. The backup connection remains inactive until the primary connection fails.

Configuring Dial Backup

The Connection Usage parameter, in the Router Connection Information configuration panel, dictates whether the connection you are configuring is primary, or a back-up of an existing primary connection. To create a primary connection, simply leave Connection Usage at the default value of “Primary.”

⇒	To create a backup connection:

1.	Set Connection Usage to “Backup.” This causes the Primary Name parameter to appear.

2.	Select a primary connection from those listed in the Primary Name drop-down list.

Important Notes

•	You must have at least one primary connection before configuring a backup connection

•	Only one backup connection may be assigned per primary connection

•	A primary connection and its backup can use the same EiconCard port, or two different ports

•	If the primary and backup connection use two different ports, both ports must be part of the same EiconCard

•	You can configure backup connections for X.25, Frame Relay, and PPP protocols, but the primary and backup connection must both use the same line protocol

Note:
An X.25 SVC can be a backup connection of an X.25 PVC primary connection.

•	If you back up a connection you configured on router A to connect it to router B, you must also back up the connection you configured on router B to connect it to router A

•	Each filter defined on the primary connection is applied on the backup connection automatically


Chapter 4: IP Routing Services

Sample Configuration

This section is a step-by-step explanation on how to configure IP Routing Services. An explanation of how to configure the router connections for LAN 1 is provided (see the diagram below). Before starting these steps, make sure that WAN Services and IP Routing Services have already been installed. To install WAN Services and IP Routing Services, see Chapter 2, “Getting Started.”

Each LAN in the following topology has WAN Services for Windows NT with IP Routing Services installed. LAN 1 has an EiconCard with two ports. Each of the other LANs have single-port EiconCards.

⇒	Follow the steps below to configure your IP Routing Services on LAN 1:

1.	Make sure that you have installed two instances of the Eicon NDIS logical adapter through the NCPA. For more information, see “Install Optional Services Software.”

2.	Configure the Eicon IP router driver and Eicon NDIS adapter driver as described in the section, “Configuring the Router Driver and NDIS Adapter”.

Note:
Record which IP address you are using for each instance of the Eicon NDIS logical adapter and its associated EiconCard port number.

After your EiconCard has been configured and started, the MPR CONFIG command can be used to check if the proper IP addresses are assigned to your EiconCard ports. Refer to the section “MPR: Starting, Stopping, Statistics, and Configuration”, for more information.

3.	When configuring the Eicon NDIS adapter drivers, record the EiconCard port for which you configure this driver. Each driver must be configured with a different EiconCard port number.

4.	Start the WAN Services Configuration program. Follow the steps as described in the section, “Starting WAN Services Configuration”.

5.	In the Port configuration panels, the Port Number parameter referenced here stipulates which copy of the Eicon NDIS adapter driver will bind with which EiconCard port.

After configuring your EiconCard and its ports you are ready to begin configuring the router connections. Begin by first creating a router connection between LAN 1 and LAN 2.

6.	Double-click the router icon if it is not already expanded in the Navigator.

a.	Click on the Connections icon to show the Connections view.

b.	Click in the Connection view and click the Insert button in the toolbar.

7.	In the Router Connection Information dialog box, begin entering the information needed to establish a connection between LAN 1 and LAN 2.

8.	Set the following parameters as described:

a.	Set the Connection Name parameter to a descriptive name of the connection. In this case, use LAN1-LAN2.

b.	Set the WAN Protocol to match the type of connection you are using. In this example, X.25 SVC is being used.

c.	Set the Connection Type to Two Way. This allows either LAN 1 or LAN 2 to initialize the connection.

d.	Set the Remote IP Address to 192.100.10.2.

e.	Set the Local DTE to 11.

f.	Set the Remote DTE to 12

g.	Set the Eicon Port to 1.

The other parameters can be left at their default values. However, if you choose to enable Data Compression, it must also be enabled on the LAN2 router for data compression to work.

9.	You must now set up the connection between LAN 1 and LAN 3. Repeat steps 1 to 6, but change the Port Number to 2.

10. From the Router Connection Information dialog box, begin entering the information needed to establish a connection between LAN 1 and LAN 3.

11. Set the following parameters as described:

a.	Set the Connection Name parameter to a descriptive name of the connection. In this case, use LAN1-LAN3.

b.	Set the WAN Protocol to match the type of connection you are using. In this example, X.25 SVC is being used.

c.	Set the Connection Type to Two Way. This allows either LAN 1 or LAN 3 to initialize the connection.

d.	Set the Remote IP Address to 192.200.10.2.

e.	Set the Local DTE to 21.

f.	Set the Remote DTE to 22.

g.	Set the Eicon Port to 2.

The other parameters can be left at their default values. However, if you choose to enable Data Compression, it must also be enabled on the LAN3 router for compression to work.

The other WAN Services PCs on LAN 2 and LAN 3 must also be appropriately configured and the routers started on their ends.

If the LAN 1 WAN Services PC has not restarted since WAN Services has been installed, do so now. This will start the EiconCard and all related services and device drivers.

To make sure that your configuration is correct, you can verify the Eicon NDIS logical adapter configuration with the MPR CONFIG command.

The example below shows the output for MPR CONFIG command if the connections have been configured correctly.

MPR CONFIG

WAN Services for Windows NT Management Utility.
MPR 3.02 Rev.01
Copyright (c) Eicon Technology Corporation 1995.
All Rights Reserved.

Eicon IP configuration

Logical Adapter  Port #       IP Address         Subnet Mask
[ 2]Ecndis         1         192.100.10.1       255.255.255.0
[ 3]Ecndis         2         192.200.10.1       255.255.255.0


Chapter 4: IP Routing Services

Sample Configuration

Using Command Line Utilities

The previous sample connections can also be configured from the command line, using the Eicon router commands.

You must first perform steps 1 to 5 in the previous example.

⇒	Follow the steps below to configure your router connections:

1.	You must first create a circuit to handle the link between LAN 1 and LAN 2 on port 1 of the EiconCard. Issue the command:

MPRCCT ADD X25 LAN1-LAN2 /A 12 /L 11 /P 1

where:

•	/A is the DTE address of WAN Services PC on LAN 2 (Remote DTE)

•	/L is the DTE address of WAN Services PC on LAN 1 (Local DTE)

•	/P refers to port 1 on the EiconCard

2.	Link the circuit created in step 1 with the IP address of the EiconCard port in the Router PC on LAN 2. Issue the command:

IPMAP ADD LAN1-LAN2 192.100.10.2 /B

where:

•	LAN1-LAN2 is the name of the circuit created with MPRCCT

•	192.100.10.2 is the IP address of the EiconCard port in the WAN Services PC on LAN 2

•	/B is the broadcast parameter. It allows you to use applications that rely on broadcast

3.	Create a circuit to handle the link between LAN 1 and LAN 3 on port 2 of the EiconCard. Issue the commands:

MPRCCT ADD X25 LAN1-LAN3 /A 22 /L 21 /P 2
IPMAP ADD LAN1-LAN3 192.200.10.2 /B

If the LAN 1 WAN Services PC has not restarted since WAN Services has been installed, do so now. This will start the EiconCard and all related services and device drivers.

Any circuit created with MPRCCT defaults to Auto Start. This parameter can be configured in the MPR.INI file. For more information on the MPR.INI file, see Chapter 11, “The MPR.INI Initialization File.”


Chapter 5: Using Microsoft SNA Server

Eicon Technology supplies drivers that enable Microsoft SNA Server to operate through Eicon Technology's EiconCard family of intelligent communications coprocessors. These drivers support an X.25/QLLC or SDLC link. To allow you to match parameter settings between the Eicon Link Support parameters and the WAN Services for Windows NT parameters, Eicon Technology's WAN Services for Windows NT configuration program is available from within SNA Server setup.

SNA Server Eicon Link Software

Configuring the Eicon Link Services


Chapter 5: Using Microsoft SNA Server

SNA Server Eicon Link Software

Eicon Technology SNA Server Link drivers are installed through SNA Server. WAN Services Core services and SNA Server must already be installed.

⇒	Follow these steps for a successful installation:

1.	At the Windows NT console, log on as Administrator or equivalent.

2.	In the SNA Server group, double-click the SNA Server Setup icon. Click Continue.

3.	In the Setup Options dialog box, click the Links button to add the Eicon Link Service, and click Other.

4.	Insert the WAN Services CD-ROM in your CD-ROM drive. Indicate the root of CD-ROM drive and click Continue.

5.	Choose the appropriate Eicon Technology Link Service from the available Link Services in the Link Service Installation dialog box, and click Install.

6.	You are presented with the Eicon Link Service Setup dialog box that corresponds to the Eicon Link Service you selected.

7.	Click OK or see "Configuring the Eicon Link Services" below to configure the Eicon Link service.

8.	Follow the SNA Server Setup instructions to further continue with the SNA Server configuration. See the Microsoft SNA Server for Windows NT manual for more information.


Chapter 5: Using Microsoft SNA Server

Configuring the Eicon Link Services

After the Eicon Link Services drivers are installed, they must be configured. Follow the steps below to configure the Eicon Link Services drivers.

⇒	To configure the Eicon Link Services:

1.	Start the SNA Server setup by double-clicking the appropriate icon through Program Manager.

2.	Continue until you get the Setup Options dialog box. Click the Configure Link Services option.

3.	Highlight the previously installed Eicon Link Service you want to configure and click Configure.

4.	Set the appropriate parameters in the Eicon Link Service Setup dialog box. Use the Help for parameter specific help.

5.	Click Advanced to call up the WAN Services Configuration program.

For both X.25 and SDLC connections, make sure the Card Port number in the Eicon X.25 and SDLC Link Service Setup dialog box matches Port Number in the port configuration panel using the WAN Services Configuration program.

In addition, for SDLC, the Line Type parameter must match the Line Interface parameter in the Sync configuration panel using the WAN Services Configuration program.

6.	Save and exit the WAN Services Configuration program. Click Continue in the Eicon Link Service Setup dialog box to exit to the SNA Server Setup program. Follow the SNA Server Setup instructions to start the SNA Services.

Note:
In the SNA Server Admin program, for SDLC PU configuration, the following parameters in the Advanced Setup dialog boxes are ignored:

Encoding (NRZ/NRZI)                            Idle Retries

Duplex (Half/Full)                                   Data Rate (Low/High)

Idle Timeout

Equivalent parameters are configured with the WAN Services Configuration program and take precedence over what is configured in the SNA Server Admin program.


Chapter 6: Using X.PAD

X.PAD includes extensions specifically designed to integrate tightly with the Remote Access Service (RAS). RAS, which is included with Windows NT, provides remote users with access to any resource on the LAN, including Microsoft SMS or SQL server. Through X.PAD, WAN Services for Windows NT provides a means for RAS to connect to remote users over X.25 Packet Switched Data Networks (PSDNs).

Configure X.PAD using Eicon Technology's X.PAD configuration program. This program is automatically started when you add X.PAD software to your Windows NT machine through the Network Control Panel Applet (NCPA). To install X.PAD, see "Install Optional Services Software".

Note:
WAN Services Core Services must be installed before you install the X.PAD service.

To configure X.PAD, see "Configuring X.PAD". For information on using RAS over X.25, see "RAS Considerations".

Introducing X. PAD

What is a PAD?

How X.PAD works

X.PAD Features

X.PAD Device Driver

Configuring X.PAD

Step1: Add or Delete COM Ports

Step 2: Configure Ports

Step 3: Setting Defaults

Step 4: Setting Profiles

Performance Monitor and X.PAD

RAS Considerations

Server Configuration

Workstation Configuration


Chapter 6: Using X.PAD

Introducing X. PAD

If you are unfamiliar with asynchronous and/or packet-based communications, the information in the following section may help you understand what X.PAD does in conjunction with RAS on the Windows NT machine.

What is a PAD?

How X.PAD works

X.PAD Features


Chapter 6: Using X.PAD

Introducing X. PAD

What is a PAD?

PAD stands for Packet Assembler/Disassembler. PADs can be implemented as hardware devices, or as a combination of hardware and software. Eicon Technology’s X.PAD is a PAD implemented mostly in software, and designed to work with EiconCards.

All PADs perform the basic functions of:

•	Disassembly: Dividing data into packet-sized blocks for transmission over packet-switched data networks (PSDNs).

•	Assembly: Concatenating received data packets back into usable data units.


Chapter 6: Using X.PAD

Introducing X. PAD

How X.PAD Works

X.PAD redirects selected COM ports' input and output to and from the EiconCard, which in turn uses its X.25 services to send and receive data over an X.25 network. The X.PAD configuration program allows you to configure one or more X.PAD ports simultaneously. Global or individual COM port parameters are configured with the X.PAD configuration program. Local and remote X.3 parameters can also be configured on a global or individual, per-port basis. See "Configuring X.PAD", for more information.

X.PAD provides you with PAD services for your asynchronous communications package. Eicon Technology's X.PAD acts as a serial port driver which intercepts RAS or your terminal emulation's output inside your PC, before it gets to a serial communications (COM) port. X.PAD then redirects the data stream to the EiconCard after assembling it into packets, and sends it through the X.25 network using Eicon Technology's WAN Services.

X.PAD performs the same service in reverse for messages received from the X.25 network: the EiconCard passes received X.25 packets, via WAN Services, to X.PAD. X.PAD re-assembles disassembled data according to X.3 parameter settings and passes it on to RAS or to a terminal emulation program designed for asynchronous input/output.

X.3 parameters, among other things, are the guidelines that the PAD uses in translation (packetizing and depacketizing): whether to insert line feeds (LFs) after carriage returns (CRs), echo characters to the screen, let the operator interrupt the transmission process, etc. For more information, see Appendix E, "X.3 PAD Parameters."

X.28 is a command language for talking to the PAD. This is the level that is used to connect and disconnect from the network.

X.29 is the interface between the PAD and the remote. You can think of it as the command language the remotes use to communicate with the PAD: the user is not aware of the process. For more information, see Appendix F, "X.28 and X.29 Commands."


Chapter 6: Using X.PAD

Introducing X. PAD

X.PAD Features

•	Provides simultaneous access to multiple remote hosts

•	Fully compatible with CCITT Recommendations X.3, X.28, and X.29

•	Flexibility for changing X.PAD parameters

•	Before starting X.PAD, by using the X.PAD configuration tool

•	After starting the emulation, but before connecting to the remote with X.28 commands from the X.PAD prompt.

•	Connecting from the X.PAD prompt, using X.28 commands

•	Performance Monitor support


Chapter 6: Using X.PAD

X.PAD Device Driver

X.PAD is installed as a device driver called ECXPAD. The Eicon X.PAD Driver can be started and stopped, and its startup method configured, with the Control Panel Devices applet. We recommend that you leave the startup method at its default to ensure proper functioning of WAN Services for Windows NT.

The service name for the Eicon X.PAD device is ECXPAD. This service can be started and stopped using the NET START and NET STOP commands, respectively. The example below shows how to start the Eicon X.PAD driver.

NET START ECXPAD

Note:
Before trying to stop the ECXPAD driver, make sure you shut down all applications which may be using X.PAD, such as RAS or other asynchronous communications programs.


Chapter 6: Using X.PAD

Configuring X.PAD

Eicon Technology’s X.PAD is configured through the NCPA.

⇒	To start the X.PAD Configuration program:

•	From the NCPA, highlight the Eicon X.PAD entry in the Installed Network Software list, and click Configure.

The Available Ports list box displays all currently available X.PAD-specific ports not in use by other resources on your Windows NT system. These ports are only available for X.PAD configuration and have unique names. Therefore, the ports are not in conflict with any other driver on your system. The Windows NT serial port driver normally handles input and output for each of these ports.

The X.PAD Ports list box displays the COM port(s), if any, whose output and input X.PAD will redirect to and from the EiconCard and its PAD services. X.PAD can control a maximum of 254 ports ranging from COM 1 to COM 999.

Note:	If you are using X.PAD only with RAS, you must leave all X.PAD configuration settings at their default values. This does not apply if you will be using X.PAD with more than one EiconCard port configured for X.25. In this case some default settings may have to be changed. See "RAS Considerations," for more information.

Step 1: Add or Delete COM Ports

Step 2: Configure Ports

Step 3: Setting Defaults

Step 4: Setting Profiles


Chapter 6: Using X.PAD

Configuring X.PAD

Step 1: Add or Delete COM Ports

Use this panel to add or delete the highlighted COM port(s) from the list boxes.

Note:
It is recommended that the number of COM ports configured in the X.PAD configuration program should be equal to or less than the number of virtual circuits (TVC+IVC) which were configured using WAN Services Configuration. See "Step 1: Configuring the EiconCard," for more information.


Chapter 6: Using X.PAD

Configuring X.PAD

Step 2: Configure Ports

This option allows you to configure the COM port(s) currently selected in the X.PAD Ports list box. It displays the following dialog box:


Chapter 6: Using X.PAD

Configuring X.PAD

Step 3: Setting Defaults

This allows you to set default values for all the parameters associated with the configuration of an X.PAD port before creating it. These are the configuration values saved for any X.PAD ports you have not explicitly configured with the Configure Ports option.

Default X.3 Parameters

Default X.3 profiles cannot be added or deleted. However, you can configure the X.3 parameters for a specific port and apply these changes to the profile associated with this port(s).

If you wish to configure a number of ports with the same settings, it is easy by using the default settings dialog box. by setting a default, any port or ports subsequently added, will all reflect the default settings. Do this as follows:

1.	Select a set of X.3 parameters (the profile) in the Defaults dialog box, and click OK.

2.	Add the ports, from the Available Ports dialog box, with which you want to use these default settings.

3.	Use the Configure Ports dialog box to set the individual X.3 parameters in the default profile for that port.

The Local and Remote X.3 parameters set here will override any of the values set in the Local and Remote Profiles. Also, note that when you create a new profile based on an existing set, the profile name of the new set is blanked.

Note:
Setting defaults must be done prior to adding any new COM ports in order for them to reflect the set defaults.


Chapter 6: Using X.PAD

Configuring X.PAD

Step 4: Setting Profiles

When installed, the X.PAD software includes seven pre-defined profiles (named 1, 2, 3, 4, 5, 6, and RAS) which have the values in the table shown below. All are configurable except for the RAS profile. Use the X.PAD Profiles Configuration panel to set the X.3 parameter values for each of the six predefined X.PAD profiles, or to add new, custom profiles.

Predefined PAD Profiles:

You can edit these profiles to suit your needs.

PAR	Function		Profile Name
			1	2	3	4	5	6	RAS (Local)	RAS (Remote)
1	Escape to Command Mode		1	1	0	1	1	0	0	0
2	Local echo		0	1	0	0	0	0	0	0
3	Selection of data forwarding character		126	2	0	2	2	0	0	0
4	Selection of idle delay timer (1/20 of a second)		0	0	20	0	0	1	0	1
5	Auxiliary device control		1	0	0	0	0	0	0	0
6	Pad service signal		5	5	0	5	5	0	1	1
7	PAD action on break signal		2	21	2	21	2	0	0	0
8	Discard pending output		0	0	0	0	0	0	0	0
9	Insert padding characters after carriage return		0	2	0	2	2	0	0	0
10	Line display width		0	0	0	0	0	0	0	0
11	Transmission speed		0	0	0	0	0	0	0	Blank (not sent)
12	Flow control by PAD		1	1	0	0	1	0	0	0
13	Linefeed after carriage return		16	4	0	16	21	0	0	0
14	Number of padding characters after linefeed		0	0	0	0	0	0	0	0
15	Local editing of data		0	1	0	0	0	0	0	0
16	Character delete symbol		127	127	127	127	127	127	0	0
17	Line delete symbol		24	24	24	24	24	24	0	0
18	Line redisplay symbol		18	18	18	18	18	18	0	0
19	PAD service signal		0	2	0	0	0	0	0	0
20	Echo mask		0	0	0	0	0	0	0	0
21	Parity treatment		0	0	0	0	0	0	0	0
22	Page wait		0	0	0	0	0	0	0	0
Remote X.3 Parameters

If you do not want to send out X.29 commands when connecting to a remote PAD, set the following:

•	The Remote Profile must be set to NONE

•	The Remote X.3 Parameters must be left blank

If you want to send out individual X.29 commands when connecting to a remote PAD, set the following:

•	The Remote Profile must be set to NONE

•	The individual Remote X.3 Parameters that you want sent

If you want to send out all 22 X.29 commands when connecting to a remote PAD, set the following:

•	The Remote Profile must be set to a specified profile (1-6)

•	The Remote X.3 Parameters must be left blank

If you want to override individual X.29 commands when connecting to a remote PAD, set the following:

•	The Remote Profile must be set to a specified profile (1-6)

•	The individual Remote X.3 Parameters with the value that you want to override

For more information, see Appendix E, "X.3 PAD Parameters."

Note:
If you wish to cancel a specific X.3 value, you must insert a space character.


Chapter 6: Using X.PAD

Performance Monitor and X.PAD

Performance Monitor is a graphical tool for measuring the performance of your computer. X.PAD includes support for Performance Monitor. Listed below are the different types of counters that Performance Monitor can use with X.PAD.

Counter Name	Description
ECXPAD Port	The ECXPAD Object Type handles the ECXPAD device on your system.
Bytes Received	The total number of bytes received for this connection.
Bytes Transmitted	The total number of bytes transmitted for this connection.
Bytes Received/Sec	The total number of bytes received per second.
Bytes Transmitted/Sec	The total number of bytes transmitted per second.
Count of Reads	The total number of bytes transmitted per second.
Count of Writes	The total number of user writes for this connection.
No Read Resources	The total number of reads - no resources for this connection.
No Write Resources	The total number of writes - no resources for this connection.
Packets Received	The total number of packets received for this connection.
Packets Transmitted	The total number of packets transmitted for this connection.
Packets Received/Sec	The total number of packets received per second.
Packets Transmitted/Sec	The total number of packets transmitted per second.
For more information on how to use Performance Monitor, please see the Microsoft Windows NT System Guide.


Chapter 6: Using X.PAD

RAS Considerations

This section contains information which will help configure Microsoft’s Remote Access Service (RAS) and RAS clients when operating over an X.25 network and using WAN Services.

Server Configuration

Workstation Configuration


Chapter 6: Using X.PAD

RAS Considerations

Server Configuration

This section contains WAN Services and RAS-specific configuration parameters which must be set accordingly.

Specifying the number of RAS Clients

When configuring WAN Services to be used with RAS over X.25, several parameters must be properly configured to define the number of clients that can connect to the server. The list below shows which parameters need to be configured.

1.	The sum total of the TVC (two-way virtual circuits) and IVC (incoming virtual circuits) must be equal to the number of incoming X.25 clients that the server must support at one time. These parameters are found in the X.25 screen using the WAN Services Configuration program. See "Step 1: Configuring the EiconCard," for more information.

2.	It is recommended that the number of COM ports configured in the X.PAD configuration program should be equal or less than the number of VCs (TVC+IVC) which were configured using the WAN Services Configuration. See "Step 1: Configuring the EiconCard," for more information.

3.	Configure the number of COM ports in RAS to be equal to the number of COM ports which you configured to use Eicon Technology’s X.PAD. See Microsoft’s Remote Access Service™ System Guide for more information on how to configure RAS.

Server Bandwidth

In order to obtain maximum performance for RAS clients and to ensure reliable links, you should ensure that the aggregate throughput of all clients does not exceed the bandwidth of the RAS.

For example, four clients running at 2400 bps can be connected to a server with a 9600 bps X.25 line. However, attaching a fifth client at 2400 bps will exceed the server’s bandwidth. This will cause all clients to operate at speeds below 2400 bps. If a VC, X.PAD, and RAS port is defined for five ports then five clients can connect over X.25. However, connecting five clients at one time is not recommended, as the throughput of each client will be too low and may cause the network protocols running over RAS to have time-outs.

Server/Remote Disconnect

The Event Viewer is a valuable tool when trying to troubleshoot clients being disconnected from RAS. The Event Viewer log can be set to record all error messages concerning RAS. Those error messages can then be checked to see why RAS client disconnected or why RAS (server) disconnected.

Remote Disconnect

If the remote client (through a dial-up PAD or local PAD) disconnects from RAS, the following warning message will appear in the system event log:

Remote DTE cleared the X.25 call on COMxxx, X.25 Return Codes : Cause yy (hex) Diagnostic yy (hex)

The COMxxx is the port name defined in the Eicon X.PAD Configuration program. When the DTE (remote client) clears the call, the cause is always 00 (hex). If the Diagnostic code is 00 (hex), then this indicates that the remote client requested a disconnect. If the diagnostic code is non-zero, it indicates a clearing cause due to a problem with the remote clients’ dial-up PAD service. Contact the X.25 service provider on the client end to troubleshoot the problem. You may also find it useful to consult Appendix C, "User Facilities and DTE Address Structure."

Network Disconnect

If the X.25 network disconnects the RAS link, the following warning message will appear in the system event log:

Network cleared the X.25 call on COMxxx, X.25 Return Codes : Cause yy (hex) Diagnostic yy (hex)

The COMxxx is the port name defined in the X.PAD Configuration program. If the network clears the call, the cause value will always be a non-zero value. The diagnostic code in this case can be any value. Consult your local X.25 service provider with the cause and diagnostic value to determine the exact reason for the network disconnect. For more information, see Appendix C, "User Facilities and DTE Address Structure."

General Recommendations

In order to ensure a reliable RAS link when using a WAN connection (COM port or X.25 port), the following guidelines should be followed:

•	At lower speed links (2400 BPS, 4800 BPS, 9600 BPS) only one transport protocol should be used.

IP, IPX, and NetBEUI can be run simultaneously with RAS. All three protocols are supported at all speeds and can be activated, however, using all three stacks at the same time at low speeds is not recommended. During testing it was shown that one transport protocol would remain active while the others would fail. The RAS link stays up, but only the most robust transport protocol would stay on line.

For lower speeds, the order of reliability of the transport stacks is as follows:

•	 IP is the most robust network protocol for WAN links

•	 IPX is the second most robust

•	NetBEUI is the least robust

On higher speeds links (56 Kbps, 64 Kbps, etc.), two or three transport protocols can be supported simultaneously without problems.

If there are excessive timeouts or very slow links, you may have to disable Write Buffering for the X.PAD COM ports. See "Configuring X.PAD," for information on how to configure your X.PAD ports.

Note:
Disabling Write Buffering will degrade throughput in most cases.

To use facilities and user-data when using Remote Access Service, you need to edit the PAD.INF file located under %SYSTEMROOT%\SYSTEM32\RAS. Do this as follows:

1.	Open the PAD.INF file for editing with any ASCII editor.

2.	Locate the section [Eicon X.PAD] and find the line containing COMMAND_DIAL below it.

3.	Change the line from:

COMMAND_DIAL=<x25address><cr><lf>

 to:

COMMAND_DIAL=CONNECT<x25address> /F<facilities> /U<userdata><cr><lf>

PAD Protocol ID

Some networks require that you place the PAD protocol ID 1,0,0,0 at the front of your user data. If so, complete the above procedure, then do the following:

1.	In the Remote Access window, choose the Remote Access icon.

2.	Select a phone book entry and choose Edit. The Edit phone book entry dialog box appears.

3.	Click the X.25 button.

4.	In the Userdata box, enter the PAD protocol ID, followed by your regular user data. For example, if your regular user data looks like this:

"PASSWORD"

then, change it to this:

1,0,0,0,"PASSWORD"

5.	In the Facilities box, enter your regular user facilities. An example of the facilities field would be:

42,7,7,43,2,2


Chapter 6: Using X.PAD

RAS Considerations

Workstation Configuration

This section contains RAS client-specific configuration parameter values.

General

The following is recommended on all workstations that are going to access a dial up PAD in order to connect through an X.25 network to a RAS using Eicon Technology’s WAN Services for Windows NT.

•	Establish all modem connections using reliable link (either V.42, LAPM, or MNP4) and enable hardware handshaking between your local modem and the workstation

⇒	To configure the RAS client for a reliable link and hardware handshaking

1.	From the main RAS client screen, choose Modem from the Edit menu.

2.	Make sure that Error Correction and Hardware Flow Control are enabled.

Enabling error correction and hardware flow control ensures that there is end-to-end flow control and no data can be lost between the dial-up PAD and the client workstation. Problems have been observed during testing when this feature is not enabled.

A DOS RAS client, as well as some third-party clients may have no way to enable modem error correction and hardware flow control. See your modem’s documentation on how to set these particular parameters.

Note:
Verify with your local service provider if this is a supported feature (modem error correction).

We also recommend that you do not use modem compression (V.42bis, MNP5 or higher) on your links since RAS already does compression and this may interfere with or decrease throughput.


Chapter 7: Using LANPAD

Eicon Technology’s LANPAD is a TCP/IP socket-to-COM-port redirector. LANPAD works in conjunction with WAN Services for Windows NT’s X.PAD. LANPAD enables users on the internetwork to connect via the telnet or other TCP/IP port on the WAN Services PC and then be redirected to one of the configured X.PAD ports. This provides the user with full X.25 network access, permitting communications with any X.25-attached device.

Configure LANPAD using Eicon Technology's LANPAD configuration program. This program is automatically started when you add LANPAD software to your Windows NT machine through the Network Control Panel Applet (NCPA).

To install LANPAD, see "Install Optional Services Software".

How LANPAD Works

LANPAD as a Service

Configuring LANPAD


Chapter 7: Using LANPAD

How LANPAD Works

LANPAD works by listening to a pre-configured socket-port (default is port 23) and then redirecting the session data to an X.PAD port. LANPAD is designed to automatically pass on each session to the next available X.PAD port. The number of sessions that LANPAD can handle is limited only by the number of configured X.PAD ports.

The diagram above shows how a user on the LAN can initiate a TCP/IP session to the WAN Services PC, have the session answered and redirected by LANPAD to an X.PAD port, and then connect to an X.25-attached device.

A typical LANPAD configuration may consist of 50 configured X.PAD ports available for LANPAD use. This enables 50 users on the LAN to simultaneously connect to the WAN Services PC and initiate X.PAD sessions. This provides each user access to the X.25 network.


Chapter 7: Using LANPAD

LANPAD as a Service

LANPAD is installed as a service called Eicon LANPAD Service. The Eicon LANPAD service can be started and stopped, and have its startup method configured with the Control Panel Services applet. LANPAD is installed with its startup method set to manual. After making sure that LANPAD is configured correctly, you can set its startup method to automatic.

The service name for the Eicon LANPAD service is ECLANPAD. This service can be controlled using the NET START, NET STOP, NET PAUSE, and NET CONTINUE commands.

The NET PAUSE command will prevent new users from connecting to LANPAD, but allow existing connections to operate. The NET CONTINUE command is used to re-enable new users to connect to LANPAD. The example below shows how to start the Eicon LANPAD service.

NET START ECLANPAD


Chapter 7: Using LANPAD

 Configuring LANPAD

Eicon Technology’s LANPAD is configured through the NCPA.

⇒	To start the LANPAD Configuration program:

•	From the NCPA, highlight the Eicon LANPAD entry in the Installed Network Software list, and click Configure.

The LANPAD configuration program is used to set which TCP/IP port is monitored by LANPAD. The default port is 23, which is also the default Telnet port.

This means if you are using a Telnet server or other TCP/IP application using port 23, LANPAD will fail to initialize. In this case you must configure LANPAD to use an alternate TCP/IP port. Users on the internetwork who want to access LANPAD services must also connect to LANPAD using the newly configured TCP/IP port.

See "IP Filters and Port Numbers," for more information on TCP/IP port numbers.


Chapter 8: Network Management Services

The Eicon Network Management Services consist of the Eicon SNMP sub-agent and the Eicon SNMP Console.

The Eicon SNMP sub-agent works in conjunction with Microsoft’s SNMP agent to give WAN Services for Windows NT SNMP MIB II (Management Information Base) support. The Eicon SNMP sub-agent interoperates with third party consoles such as HP OpenView, IBM NetView/6000, and Novell NMS. For more information on SNMP MIB II support, see "Eicon SNMP Sub-Agent".

The Eicon SNMP Console gives you the ability to locally or remotely monitor and control WAN Services functions on your LAN or WAN. The console also enables remote dynamic configuration of the router connections. For information on dynamic configuration of your router connections, see "Dynamic Configuration".

The Eicon SNMP Console is a Windows program which you can run on a Windows or Windows NT machine.

Before you install the Eicon SNMP Console, the Eicon Network Management Services must be installed on the WAN Services PC. These services activate the Eicon SNMP sub-agent which enables the SNMP Console to remotely monitor and control your WAN Services PC.

Management software is also available locally on the WAN Services PC, in the form of command line utilities. These commands can be issued from the Windows NT system prompt. For more information, see Chapter 9, "Command Line Utilities" and Chapter 10, "Using ECMODULE."

Eicon SNMP Sub-Agent

Eicon SNMP Console

Requirements

Eicon SNMP Console Installation

Eicon SNMP Console Operations

Eicon SNMP Console Menus

Operating the Console

Logging into the Console

Setting LAN Protocol Support

Discovering and Selecting Servers

Obtaining Server Information

Monitoring the EiconCard

Managing Routing Services

Dynamic Configuration


Chapter 8: Network Management Services

Eicon SNMP Sub-Agent

The Eicon SNMP sub-agent interoperates with third-party consoles such as HP OpenView, IBM NetView/6000, and Novell NMS. However, the SNMP MIB II (Management Information Base) support is partially handled by the Microsoft SNMP agent, while the Eicon SNMP sub-agent supplies a rich set of WAN private MIB extensions.

Eicon MIB and Third-Party Console Support

These extensions enable management control and reporting for any services provided by WAN Services. Therefore, in addition to monitoring Eicon-specific SNMP information, you can also monitor System, Interfaces, IP, ICMP, TCP, UDP, and other SNMP information from any one of the consoles listed above, via MIB Browser.

The Eicon MIBs are located in the MIBS subdirectory on the WAN Services for Windows NT CD-ROM. The table below lists the MIBs available for use by third-party consoles:

MIB	Description
RFC1315.MIB	Frame Relay DTE Interface Type MIB (Proposed Standard)
CARD.MIB	EiconCard MIB
DIALER.MIB	Dialers MIB
ECPPP.MIB	PPP Protocol MIB
LAPBEXT.MIB	LAPB Extensions MIB
PORT.MIB	EiconCard Port MIB
ROUTER.MIB	Router MIB
SDLC.MIB	SDLC Protocol MIB
SERVER.MIB	Server Information MIB
TRACE.MIB	Protocol Trace MIB
X25EXT.MIB	X.25 Extensions MIB
Note:
Support for RFC1381 and RFC1382 is included in the X.25EXT.MIB and LAPBEXT.MIB.

RFC1315.MIB has also been modified to support MIBII transmissions in a Windows NT environment.


Chapter 8: Network Management Services

Eicon SNMP Console

The Eicon SNMP Console uses its own install program. It can be installed on the WAN Services PC, or on a remote PC running any of Windows 3.1, Windows for Workgroups 3.11, or Windows NT 3.1 or later.

Note:
If you install the Eicon SNMP Console on the WAN Services PC, you must first stop Microsoft’s SNMP service if it is running. After the Eicon SNMP Console is installed, you should restart Microsoft’s SNMP service if necessary.

Requirements

Eicon SNMP Console Installation


Chapter 8: Network Management Services

Eicon SNMP Console

Requirements

If you are installing the console on a PC running DOS, Windows 3.1, Windows for Workgroups 3.11 or Windows NT 3.1 or higher, the PC must have:

Windows Environment

•	At least 2.5 MB free disk space and 2 MB RAM

•	Mouse recommended

•	Microsoft Windows v3.1 or Windows for Workgroups v3.11

•	For TCP/IP support:

•	WinSock v1.1 compliant

•	FTP Software PCTCP v2.3 with 231PATCH.EXE (update available from FTP Software’s BBS or Internet site ftp.ftp.com)

•	Novell LAN WorkPlace for DOS TCP/IP v4.10 Rev A and above

Windows NT Environment

If you are installing the Eicon SNMP Console onto a PC running Windows NT 3.1 or later, you must have the Microsoft TCP/IP stack and SNMP agent, available with Windows NT, installed. See your Windows NT System Guide for more information on installing Microsoft TCP/IP.


Chapter 8: Network Management Services

Eicon SNMP Console

Eicon SNMP Console Installation

The Eicon SNMP Console can be installed in three different ways:

1.	From the CD-ROM.

2.	From diskettes created from the CD-ROM.

3.	From a directory on the LAN created from the CD-ROM.

If you wish to install the Console from diskettes, you must create the diskettes from the CD-ROM. See "Creating Install Disks from the CD-ROM," for more information.

Note:
The TCP/IP protocol stack on the Eicon SNMP Console PC must be WinSock v1.1 compatible. See "Requirements," for more information.

⇒	To create an install directory on the LAN:

•	Copy the entire directory contents of \CONSOLE to the directory on the LAN from which you want to install.

Installation

This section details the steps involved in installing the Eicon SNMP Console.

The Eicon SNMP Console has the ability to dynamically add delete or modify router connections. To do this certain steps must be performed on the WAN Services PC, such as creating an FTP user account. See "Dynamic Configuration," for more information.

⇒	Follow these steps for a successful installation:

1.	If you are installing the Eicon SNMP Console from diskette, insert the WAN Services for Windows NT (Console) Disk 7 into a floppy disk drive.

From the Program Manager or File Manager, choose File Run and type the following:

A:INSTALL

If you are installing from the CD-ROM or from a directory on the LAN, then from Program Manager or File Manager, choose File Run and type the following:

drive:dir\INSTALL

where drive is the drive letter of your CD-ROM or your LAN directory and dir is the directory where the install program is located. The install directory on the CD-ROM is \CONSOLE.

2.	After reading the Welcome notes, choose Continue or choose the Start Install option from the File menu to proceed with the software installation procedure.

3.	The Install dialog box identifies the version of the Eicon SNMP Console software.

Click the Overwrite files box if you have cancelled the installation and wish to reinstall. Also, this box is applicable when updating to the next release of this product. The Install program will automatically overwrite all previously installed files with the same name without prompting you each time.

If you are installing the Eicon SNMP Console program for the first time, choose OK to continue.

4.	From the Install window, click OK:

The installation program copies these programs to the C:\ECSNMP directory by default.

Important:
If you wish to change the default Executable Directory path, ensure that you do not exceed the FAT limit of eight characters. The Install program does not validate nor truncate the path length which is displayed on the progress bar.

To choose another directory location to install these programs, click Disk space.

5.	Verify that you have sufficient resources to install the selected WAN Services programs in the highlighted directory by clicking the Disk space... button. The window will indicate the number of bytes required to install the Eicon SNMP Console program and whether installation is possible. Scroll the directory list from your PC and verify that sufficient resources are available. Choose OK to continue.

Click the Change directories to selected drive check box if you wish to change the directory used for installation. The selected drive letter displays for the executable directory on the Install - directories window.

Important:
For security reasons, it is highly recommended that you do not install the Eicon SNMP Console in a shared directory, or in a publicly accessible network directory. The best place to install it is in a non-shared directory on a workstation hard disk.

6.	From the Install directories window, click the Install button to begin the installation process.

7.	When the Eicon SNMP Console files have been unpacked and copied to the target directory, a message is displayed indicating that this component has been successfully installed.

The Eicon SNMP Console program group is automatically created.

The table below provides a list and describes the function of each Program Manager group item created by the Install program. Double-click the desired icon to perform the associated action:

Item	Function
Installation Utility	The Installation and Maintenance utility installs, restores, or deletes your Eicon SNMP Console program files. Use the install program online help for complete instructions on any of the actions listed.
Read Me	The README file is a text file of the WAN Services Release Notes. It contains important information about WAN Services requirements and limitations that were not covered in the manuals. Read this file before starting the programs.
Eicon SNMP Console	This is a Windows 3.1 application that enables you to remotely monitor, manage, and control your WAN Services components and resources.
Eicon SNMP Console  Help	You can view the contents of the online help file provided with the Eicon SNMP Console program directly by double-clicking this icon or by running the Eicon SNMP Console program.

Update, Delete, and Install Console

Console Security


Chapter 8: Network Management Services

Eicon SNMP Console

Eicon SNMP Console Installation

Update, Delete, and Install Console

There are two possible ways to update, delete, and install the Eicon SNMP Console program files:

1.	Directly from the Install program opening screen by choosing the Start Install option from the File menu

2.	Through the Installation and Maintenance Utility program

Caution:
If you wish to delete the Eicon SNMP Console, you should do so by choosing any one of the above methods. Do not delete the files directly from the SNMP Console directory, as this will not update the EPFWIS.INI file. This file, which is located in the \WINDOWS directory, contains important historical information necessary for successful software maintenance by the Install program.

Install Program

When you choose the Start Install option the File menu of the Install program, you are presented with the following options: Update, Delete, or Install.

Click the button beside the selection you want to make (update, delete, install) and choose Continue to proceed. Follow the on-screen instructions to complete your request.

Installation and Maintenance Utility

You can also delete, install, or restore the Remote Management Tools using the Installation and Maintenance Utility program.

Important:
Do use the Update option in the Installation and Maintenance Utility to update a previously installed Eicon SNMP Console for corrective service or the next release of the product. Use the INSTALL Program as described in the previous section.

Listed below are a variety of actions that can be performed on items that have already been installed:

•	Install Eicon SNMP Console on your PC

•	Restore a previous release of the Eicon SNMP Console

•	Delete the Eicon SNMP Console from your PC

If you have not installed the Eicon SNMP Console, you must open a product catalog to see a list of possible utilities. You will then have the option of installing them from the Action menu.

For complete instructions on how to perform any of the actions listed above, use the online help provided with the Installation and Maintenance utility.

Caution:
If you wish to delete the Eicon SNMP Console, you should do so by choosing any one of the above methods. Do not delete the files directly from its file directory as this will not update the EPFWIS.INI file. This file, which is located in the \WINDOWS directory, contains important historical information necessary for successful software maintenance by the INSTALL program.

Deleting the Installation and Maintenance Utility

The Install program displays the following message while deleting the Eicon SNMP Console:

This message displays because you have requested to delete the Installation and Maintenance utility. Since you are currently running this utility, deleting it is not possible. You will need to exit the Installation and Maintenance utility and run the following command from your root directory from your boot drive (C:\) to delete the Eicon SNMP Console program items completely from your system:

EPFIDEFI.BAT


Chapter 8: Network Management Services

Eicon SNMP Console

Eicon SNMP Console Installation

Console Security

Console security is provided via a file named ECLOGIN.DAT. This file is copied down to the directory pathname where you have specified to load your Eicon SNMP Console program files. This password file contains a blank security password which enables you to log into your Eicon SNMP Console. See "Logging into the Console," for more information.

If for any reason you have forgotten your password, you can recopy the ECLOGIN.DAT blank password file from the diskette which you named Eicon SNMP Console Disk 2 or from the WAN Services for Windows NT CD-ROM in the \CONSOLE directory. Type the following command from the directory in which you have your Eicon SNMP Console files, assuming A: is the disk drive containing your WAN Services installation diskette and C:\ECSNMP is where your Eicon SNMP program is located:

COPY A:\ECLOGIN.DAT C:\ECSNMP

Doing this overwrites your current password file and re-establishes the program password file as current. You can then use the blank password to log into the console and change it accordingly.


Chapter 8: Network Management Services

Eicon SNMP Console Operations

The Eicon SNMP Console enables you to perform a wide range of operations on remote WAN Services PCs via the Simple Network Management Protocol (SNMP). SNMP is used to transparently communicate management information between the console and the SNMP network agents. See the Windows NT documentation on TCP/IP for more information on how to install and configure SNMP services.

The console communicates with WAN Services via SNMP over IP. To monitor and control WAN Services resources you must ensure that the Microsoft SNMP agent has been configured and activated and the Eicon Technology SNMP sub-agent has been loaded.

There is no restriction on the number of consoles that can be run on the LAN, but to avoid potential conflicts, you should have only one Eicon SNMP Console set up at a central site.

The following resources can be monitored or controlled on WAN Services from a central site:

•	All EiconCards and their respective ports

•	Integrated modems onboard the EiconCards

•	All port-level protocol modules within an EiconCard

•	Routing Services (dynamic configuration possible)

Optimizing Memory Resources

There are no system limitations or restrictions when running the Eicon SNMP Console. For best results, if you are running the console on a Windows 3.1 machine, you should increase DOS conventional memory before starting Windows. Make sure that you have at least 500K of conventional memory before you start Windows. Consult your DOS documentation for details on how to free available conventional memory.

The Eicon SNMP Console is able to perform specific network management functions that can be categorized into one of the five following groups:

•	Monitoring

•	Controlling

•	Status

•	Dynamic Configuring (Click here to jump to the section "Dynamic Confiuration"

•	Tools

Topics in this section:

Eicon SNMP Console Menus

Operating the Console

Logging into the Console

Setting LAN Protocol Support

Discovering and Selecting Servers

Obtaining Server Information

Monitoring the EiconCard

Managing Routing Services


Monitoring

Monitoring involves maintenance of network resources and components. Network management resources include routers which have management agents responsible for performing the network management functions requested by the management console.

Through the Eicon SNMP Console, you can generate statistical information about the communications data streaming through WAN Services. You can also obtain status information on various WAN connections, as well as all EiconCards in WAN Services. Protocol traces can also be performed on all link-level protocols.


Controlling

As a WAN Services Administrator you have the privilege of starting or stopping any Eicon service, individual EiconCard ports, or IP router connections.

You can also perform fault management functions such as the detection, isolation, and correction of abnormal conditions on your internetwork.


Status

General status of any WAN Service component is represented graphically in the Navigator window with warning or inactive symbols beside their respective icon. This indicates problems quickly and easily. For a complete description and graphic representation of these symbols, see the online help for the Eicon SNMP Console.


Dynamic Configuring

Dynamic configuring involves the definition of routing connections. To configure the IP Router connections component, in the Navigator click on the Router which you want to configure, then click on the Configuration button to invoke the WAN Services Configuration program panel for IP Router connections.


Tools

The Tools module is a collection of useful utilities for network management. The tools enable you to customize console behavior and manage a log of WAN Services network statistics.


Chapter 8: Network Managerment Services

Eicon SNMP Console Operations

Eicon SNMP Console Menus

This section presents all the menus available from the Eicon SNMP Console and describes the options available under each menu. The content of the menus may vary depending on the active window and on the View panel selected for the application workspace. Unavailable options are dimmed and cannot be selected for the current view.

File Menu

View Menu

Monitor Menu

Operations Menu

Configure Menu

Tools Menu

The Window and Help menu have the standard Windows NT options.


File Menu

Option	Description
Login...	Ensures that the user is authorized to make use of the Eicon SNMP Console. Once you have successfully logged into the console, the Login command disappears.
Logout	Logs out of the Eicon SNMP Console and closes all console windows, leaving the "Login" and "Exit" menu items as the only available commands.
Password...	Enables the user to change the Login password for the Eicon SNMP Console.
Exit	The Eicon SNMP Console implicitly performs a logout, closes all windows, and exits the console program.


View Menu

Option	Description
Navigator	The Navigator option enables the user to select which view mode should be displayed in the Navigator. Different views are available for each WAN Services component. For example, if the Server icon is selected, Administration, Agent and Hardware views are available.
Server Selection...	The Discover feature determines which WAN Services PCs on the LAN are active and allows the user to add or remove them from the list of servers to be monitored.
Toolbar	Displays the Eicon SNMP Console toolbar which consists of common action buttons such as stop, start, show components, show statistics, show details, configure, refresh, logout.


Monitor Menu

Option	Description
Show Components	Displays information about the object selected in the working area.
Advanced	Displays further details about the object selected.
Show Statistics	Enables you to get statistical information for a specific protocol (high-level protocol or line protocol), and its connections.


Operations Menu

Option	Description
Start	Enables you to start a component (i.e. a server, routing services, or a card) currently selected in the Navigator.
Stop	Enables you to stop a component (except for a server) currently selected in the Navigator. Before stopping the component, the Eicon SNMP Console displays a dialog box asking you to confirm your action.
Reset	Enables you to stop and automatically restart the EiconCard. Instead of stopping and restarting the card (two operations), you can simply use the Reset command from the console.
Trace...	Enables you to start a trace on WAN Services for a specific protocol or a specific connection of a protocol on an EiconCard. You can start a protocol trace or a protocol connection trace from any "protocol" window. This command enables you to store the packets flowing at the protocol level on the EiconCard, into a log file located on WAN Services. Once the trace is completed, you can retrieve the file directly from WAN Services.
Dialer	Enables you to dynamically control your dialer and modem. You will be able to perform the following operations:  Disconnect: disconnects the current connection. Dial: displays the primary and secondary phone numbers for the port. This option also enables you to enter another telephone number to use. Execute Script: displays an Open dialog box which enables you to choose an ECDIALER script for programming an external modem (AT Dialer only).  Answer Mode: enables the dialer to answer incoming calls. Data Rate Select: (DRS) This is functional for direct dialers only. Defines the setting of the DRS signal on an RS-232 interface (this selection is only available for an EC/PC card).


Configure Menu

Option	Description
Server...	Enables you to add a new WAN Services PC.
Insert Ins	Enables you to insert a router connection. This choice is only available when the Router Connection view is selected.
Modify Enter	Reconfigures an existing Router Connection. This choice is only available when the Router Connection view is selected.
Delete Del	Deletes an existing Router Connection job. This choice is only available when the Router Connection view is selected.


Tools Menu

Option	Description
Refresh	Forces the Eicon SNMP Console to update the status information of a window without waiting for the next poll interval.
Refresh Navigator	Redisplays the Navigator tree without waiting for the next poll interval.
Community...	Sets the SNMP Community name for the WAN Services PC. Defining a Community name enables the Eicon SNMP Console to communicate with the selected server(s). A name should only be entered here if the SNMP Agent was originally configured with a Community name. Likewise, the Community name you enter here must match the community name set during configuration of the Microsoft SNMP Agent. If the names do not match, then you will not be able to issue commands to that WAN Services PC.
Start Logging	Enables you to set up a file to log statistical information for WAN Services. This file contains information appended at intervals set in the Refresh Navigator command.
Statistics Log...	Displays a list box of all active log files on the console. You may stop a log by selecting a file and then the Close button.
Options...	Displays a dialog box which enables you to set server and log polling times, LAN protocols used for discovering and monitoring, LAN timeouts, number of retries, LAN broadcasts timeouts, and saving of your console windows preferences.


Chapter 8: Network Management Services

Eicon SNMP Console Operations

Operating the Console

Upon invoking the Eicon SNMP Console, you will be required to login to the system. The login process is required to start the console. You must use the correct password, otherwise access will be denied. See "Logging into the Console," for more information.

Identifying WAN Services PCs

The first time you login to the Eicon SNMP Console, you will have to "discover" all available WAN Services PCs on your internetwork. Use the View Servers Selection menu option to include any WAN Services PCs that you want to monitor. See "Discovering and Selecting Servers," for more information.

Community Names

Community names act like passwords, and are designed to prevent execution of unauthorized remote commands on WAN Services PCs. The Community names are assigned to WAN Services through Microsoft’s SNMP agent. See the Windows NT TCP/IP booklet on how to install and configure the Microsoft SNMP agent.

In order for the Eicon SNMP Console to monitor or issue commands to any WAN Services PC, you must enter a matching Community name for each WAN Services PC.

To enter the Community name, select Community under the Tools menu. Select a WAN Services PC and then enter the corresponding Community name. Multiple server selection is possible if they all have the same Community name. This action has to be performed only once, or when a WAN Services PC changes its Community name.

Background Monitoring

During the console session, background monitoring can be activated to periodically refresh the displayed information. This monitoring mechanism updates the status of each component displayed in the Navigator and the information displayed in the working area of the Main window. Set your preferred rate of monitoring under Options from the Tools menu. The default refresh interval is set to 5 minutes. You may increase this interval to minimize the traffic on the network.

Statistical Logging

WAN Services offers the ability to monitor all high-level and link-level protocols and log the statistics to a user-specified file. Each protocol is logged separately in a tab-delimited ASCII file, and can be loaded into most spreadsheet programs.

Opening Multiple Windows

The Eicon SNMP Console enables you to simultaneously monitor several WAN Services PCs and their different components. You can also use this feature to compare information between two or more WAN Services for Windows NT components.

Use the New Window option under the Windows menu to duplicate the Main window. You may open several windows using this method. In each case, select a different component to monitor.

Eicon Manual Operations

For most console functions, there is an equivalent EiconCard command that can be run at the Windows NT system prompt. Although it is recommended that you use the Eicon SNMP Console, you may have to resort to manually starting and stopping WAN Services components if you cannot start the Eicon SNMP Console. For more information, see Chapter 9, "Command Line Utilities."

Eicon SNMP Console Windows

Each Eicon SNMP Console window is divided into two main parts: the Navigator and the Application Workspace area. The view area to the right of the window is a working area that presents specific information related to the icon selected in the Navigator. This working area can display different view types (list format, table format, etc.), depending on the type of information requested. From the working area, you can also open dialog boxes or spawn other windows.

Whenever the Eicon SNMP Console detects that a Navigator component is inactive or has failed, it displays the component’s icon and all its subcomponents in a different color, and marks the components with an inactive symbol. Any related icons at a higher level in the tree are marked with a warning symbol to indicate a problem with a subcomponent.

For example, an EiconCard that has not been started will be accompanied by an inactive symbol, and the WAN Services PC in which it is installed will display a warning symbol.

Selecting Views

Each icon on the Navigator tree has a number of selected views, except for the LAN Transport icon which only has one. You can access these views, using any one of the following three methods:

•	Select-click any of the available tabs presented across the console screen

•	Click the icon of your choice with the right mouse button to bring up the menu of available views

•	Use the View/Navigator menu to select the available views for the selected icon


Chapter 8: Network Management Services

Eicon SNMP Console Operations

Logging into the Console

To login to the Eicon SNMP Console, you must enter a valid password. A password file, ECLOGIN.DAT, containing a blank password is shipped on your WAN Services CD. See "Console Security".

The only time you may bypass entering a password is the first time you use the Eicon SNMP Console since the default password is blank.

Eicon SNMP Console Security

Typically, only a few individuals, such as the network administrator, will be given privileges to access the Eicon SNMP Console. This level of security prevents unauthorized users from inadvertently misusing or reconfiguring WAN Services.

Powerful functions, such as starting and stopping EiconCards, and starting WAN Services software from any console on the LAN, are protected by this level of Eicon management-level security.

Changing the Eicon Password

The first time you run the console you can simply press Enter to login to the console. After starting the console for the first time, you should change the console password so that unauthorized users cannot gain access.

⇒	To change the Eicon SNMP Console password:

1.	Select the Password option from the File menu.

2.	In the New Password field, enter the new console password.

3.	In the Confirm New Password field, confirm the new password by re-entering it, and clicking OK.

For all future password changes, you must enter the current password as well as the new one you want to use.


Chapter 8: Network Management Services

Eicon SNMP Console Operations

Setting LAN Protocol Support

Before using the Eicon SNMP Console, you must first set the LAN protocols used to discover and monitor your servers. IP support is already selected by default. You may also enable SPX support if you want to monitor, control or configure any NetWare-based Eicon Technology products on your internetwork.

⇒	To enable SPX support:

1.	Choose the Options command from the Tools menu.

2.	Under Preferences, check or uncheck the LAN protocol(s) you wish to support.

3.	Exit and restart the Eicon SNMP Console.


Chapter 8: Network Management Services

Eicon SNMP Console Operations

Discovering and Selecting Servers

After logging on to the Eicon SNMP Console, you must identify which servers you wish to monitor and/or control. This is known as "discovering your servers" and is accomplished by accessing the Server Selection option under the View menu.

⇒	To Discover and Select servers:

1.	Choose the Server Selection option under the View option to display the following dialog box:

2.	From the Server Selection dialog box, choose IP from the LAN Protocol list.

3.	Choose the SLP button to display the Service Location Provider dialog box.

4.	In the bottom box, enter the IP addresses of all your WAN Services PCs in the form xxx.xxx.xxx.xxx, clicking Add after each one.

5.	After entering all the addresses, you must select which ones you wish to use for discovering. Choose Select All to use all the addresses. Click Close.

6.	Click Discover to view all the available Servers. Select the servers to be monitored by the console, by highlighting the server name(s) from the Servers list and choosing OK. Hold down the "Ctrl" key and click on each desired server for selective server choices. The Select All button, selects all servers in the Servers list.

Note:	To be able to use the IP stack protocol, the TCP/IP protocol stack on the Eicon SNMP Console PC must be WinSock v1.1 compatible. See "Requirements," for more information.


Chapter 8: Network Management Services

Eicon SNMP Console Operations

Obtaining Server Information

WAN Services information has three different views: Administration, Agent, and Hardware. To select any one of the following views, click the server icon and select any one of the available tabs presented across the console screen.

Administration Information

Agent Information

Hardware Information


Chapter 8: Network Management Services

Eicon SNMP Console Operations

Obtaining Server Information

Administration Information

The Administration view displays general information including the WAN Services physical location and the amount of time that it has been active.


Chapter 8: Network Management Services

Eicon SNMP Console Operations

Obtaining Server Information

Agent Information

The Agent view displays the Microsoft SNMP statistics for the selected WAN Services system.


Chapter 8: Network Management Services

Eicon SNMP Console Operations

Obtaining Server Information

Hardware Information

The Server Hardware view shows the network hardware and software currently installed on the selected server.


Chapter 8: Network Management Services

Eicon SNMP Console Operations

Monitoring the EiconCard

There are two views for EiconCard components: Protocol and Hardware.

Protocol Information

Hardware Information

Double-clicking the EiconCard icon shows the different components of the EiconCard.

Port Information

Dialer Information


Chapter 8: Network Management Services

Eicon SNMP Console Operations

Monitoring the EiconCard

Protocol Information

The Protocol view lists all high-level protocols loaded and currently used on the selected EiconCard.


Chapter 8: Network Management Services

Eicon SNMP Console Operations

Monitoring the EiconCard

Hardware Information

The Hardware view is associated with the EiconCard icon and presents the EiconCard hardware setup and status.


Chapter 8: Network Management Services

Eicon SNMP Console Operations

Monitoring the EiconCard

Port Information

The port component in the Navigator offers views of the available link level and dialer protocols for that port. Under the Protocols view, you can display detailed configuration and status for any selected link level protocol. The connection Status window displays all connections for this protocol. Protocol traces can be run on any specified protocol from the Operations menu.

Note:
Stopping a specific port on an EiconCard is not possible. If you need to stop communicates going through a port, you must stop the EiconCard which contains the port.

Click the Details button on any link level protocol to display a panel similar to the following:

Click the Statistics button on any link level protocol to display a panel similar to the following:


Chapter 8: Network Management Services

Eicon SNMP Console Operations

Monitoring the EiconCard

Dialer Information

Under the Dialer view, you are shown the Dialer status and interface information.

Dialing Operations

From the Dialer view, you may also perform certain dialer operations such as:

•	dial a number

•	disconnect the dialer

•	execute a script file

•	set the dialer to answer mode

•	set the Data Rate Select (DRS) for direct dialers

These functions are available under the Operations menu.

Execute a Script File

ECDIALER also supports the use of modem scripts which tell your AT dialer what information to send in response to specific cues. The WAN Services administrator can automate a wide range of communications functions by writing scripts to program external modems.

Selecting the Execute menu command displays a dialog box listing all scripts for a specific server that is selected in the console Navigator window. This list of script names represents script files that must be located on the remote server in the WSNT\DIALSCPT directory. This list is obtained via the SNMP Agent. For more information about modem scripts, see "ECDIALER Script Language".


Chapter 8: Network Management Services

Eicon SNMP Console Operations

Managing Routing Services

IP routing services has two different views: Status and Connection. To choose between the two views, select any one of the available tabs presented across the console screen. The Connection window is also used to start, stop, add, modify, or delete a Router connection.

To add, delete or modify router entries, use the Configure menu.

Starting and Stopping Routing Services

Starting and stopping all Routing Services is as easy as clicking on the Router icon in the Navigator, then clicking on the Start or Stop buttons. You can also select the Start or Stop options under the Operations menu.

Status Information

Connection Information


Chapter 8: Network Management Services

Eicon SNMP Console Operations

Managing Routing Services

Status Information

The Router Status window displays a general status panel and port status panel.


Chapter 8: Network Management Services

Eicon SNMP Console Operations

Managing Routing Services

Connection Information

The Connection window also has two additional panels of information. By clicking on a router connection, you have the option of obtaining statistical or detailed information through the appropriate icon on the toolbar.

The connection window also enables you to stop, start, add, delete, or modify a router connection. Click the Router Connection window to make it active. To stop or start a connection, highlight the connection entry, then choose the Stop or Start button from the toolbar.

Click the Details button on a routing services connection to display a panel similar to the following:

Click the Statistics button to a display a panel similar to the following:


Chapter 8: Network Management Services

Eicon SNMP Console Operations

Dynamic Configuration

To dynamically configure a router connection, you need an FTP user account on the WAN Services PC. The Eicon SNMP Console uses the FTP protocol to transfer configuration data between itself and the WAN Services PC. See "Creating an FTP User Account," for more information.

To dynamically configure, modify, or add a router connection, choose Configure from the menu, then Modify, Insert, or Delete. You may also use the keyboard to configure a router connection. To do this, highlight an existing entry, then press "Enter" to modify it, "Insert" to insert a new entry, or "Delete" to delete the entry. See "Step 1.1: Router Connection Configuration," for more information.

Note:
Modifying circuits with the Eicon SNMP Console or the MPRCCT command line utility does not change the configuration file used by the WAN Services Configuration program (EC.CFG). Therefore, if you start the configuration program after making changes with MPRCCT or the Console, these changes will not be reflected in the configuration you see. They only affect the MPR.INI file.

Important:
To dynamically modify or delete a router connection, the connection must not be active. Stop the connection first, then modify or delete it.


Chapter 8: Network Management Services

Creating an FTP User Account

The Eicon SNMP Console has the ability to remotely dynamically configure your router connections on the WAN Services PC. To be able to do this, it must be able to FTP to the WAN Services PC and get and put the WAN Services configuration files. This means that you must create a special user on the WAN Services PC: a user with access to the WAN Services configuration files.

⇒	To create a user account on the WAN Services PC:

1.	From Program Manager, start the User Manager application.

a.	Select User, then New from the menu.

b.	Specify a username and Password.

The user name must be the exact name you used to specify the WAN Services directory. The default directory name is WSNT.

2.	From Control Panel, select the FTP Server applet and choose Security.

a.	From the FTP Server Security dialog box, enable read and write access to the partition on which your WAN Services program files are located.

If you need to FTP to the WAN Services PC while using the Eicon SNMP Console, supply the username and password which was recently created in step 1b earlier.


Chapter 9: Command Line Utilities

This chapter presents the EC commands for use with WAN Services for Windows NT. Each command is completely described, including descriptions for all parameters. These commands offer a local alternative to the Eicon SNMP Console.

Command Reference

Overview of WAN Services Commands

ECCARD: Starting the EiconCard

Using ECCARD

ECCARD Error Level Values

ECDIALER: Using a Modem

Modem Protocols

Using ECDIALER

ECDIALER and ISDN

Using ECDIALER with ISDN NI-1 (North America)

Using ECDIALER with TPH1962 (Australia)

Using ECDIALER with 5ESS (AT&T)

Using ECDIALER with Euro-ISDN

ECDIALER Script Language

ECTEST: Testing the EiconCard

ECVER: Searching for Eicon Software

Using ECVER

IPMAP: IP Mapping Management

Using IPMAP

MPR: Starting, Stopping, Statistics, and Configuration

Using MPR

MPRCCT: Circuit Management

Using MPRCCT

MPRFLT: Filtering of IP Packets

The Filtering Process

Using MPRFLT STATUS

Using MPRFLT STATS

MPRTRC: Trace Management

Using MPRTRC


Chapter 9: Command Line Utilities

Command Reference

These commands are described in detail, starting here. For help with any of the commands, type the command name followed by /?. For example:

ECCARD /?

Start an EiconCard

ECCARD START [/E n ] [/M m ] [/N n ][/S]

Get Protocol Information

ECMODULE STATS | STATUS | TRACE protocol [/P p| /E n] [/G g | /R r]

For more information, see Chapter 10, "Using ECMODULE."

Test an EiconCard

ECTEST [/E e ] [/C] [/S] [/FO]

Stop an EiconCard

ECCARD STOP [/E n ][ /Y ]

Use a Modem

ECDIALER STORE [/P n | portname] [/M n] [/AL n] [/C x] [/B n] [/AC x] [/AB b][/G g]
ECDIALER DIAL [/P n | portname] [/C x] [/B n] [/N n] [/G g]

Start/Stop the router and View Global Router Statistics

MPR START | STOP | STATS | CONFIG

Add/Delete Circuits and View Circuit Status and Statistics

MPRCCT ADD X25 cctName /V pvcnum [/B primaryname] [/T timer] [/R retrynum] [/E retrydelay] [/A remDTE] [/L locDTE] [/C I | O | T] [/IF facilities] [/OF facilities] [/U userdata] [/K] [/P port]

MPRCCT ADD FRBS cctName /DLCI dnum [/X] [/S] [/K] [/P port] [/B primaryname]

MPRCCT ADD PPP cctName [/K] [/P port] [/B primaryname]

MPRCCT DELETE cctName

MPRCCT STATUS cctName

MPRCCT STATS

MPRCCT LIST

MPRCCT START cctName

MPRCCT STOP cctName

See the MPRCCT section of this chapter for a full listing of the X.25, Frame Relay, and PPP parameters you can include when issuing MPRCCT ADD commands.

Map Circuits to a Remote IP Address and View Mapping Status

IPMAP ADD cctName IPAddr [/B]

IPMAP DELETE cctName IPAddr

IPMAP STATUS

Manage IP Filters for Connections

MPRFLT ADD cctN13ame

MPRFLT DELETE filterID

MPRFLT STATUS cctName

MPRFLT STATS cctName

MPRFLT ACTIVATE filterID

MPRFLT DEACTIVATE filterID

Trace the router Data Exchanges

MPRTRC DUMP NDIS | NCB

MPRTRC RESET NDIS | NCB


Chapter 9: Command Line Utilities

Overview of WAN Services Commands

WAN Services command-line utilities offer an alternative to operating the Eicon SNMP Console program. These command-line utilities allow you to stop or start an EiconCard, and add, delete, or modify a router connection. This chapter explains how to do this, and provides an explanation of all the command-line utilities.

Command Error Levels

Many commands return error level values indicating their status on completion. This is useful when you are writing batch files to automate certain procedures. A complete list of error levels and their descriptions is included with each command that supports them.

Configuration

The only way to configure the EiconCard and its associated ports and protocols is to use the Windows-based WAN Services Configuration. You cannot configure the EiconCard using the command line utilities described in this chapter. For more information, see Chapter 3, "WAN Services Configuration."

You can also use the Eicon SNMP Console program to create and delete circuits and IP mappings.

ECCARD

Jump to ECCARD: Starting the EiconCard

ECDIALER

Jump to ECDIALER: Using a Modem

ECMODULE

Jump to Chapter 10, "Using ECMODULE."

ECTEST

Jump to ECTEST: Testing the EiconCard

ECVER

Jump to ECVER: Searching for Eicon Software

IPMAP

Jump to IPMAP: IP Mapping Management

MPR

Jump to Chapter 11, "The MPR.INI Initialization File."

Jump to MPR: Starting, Stopping, Statistics, and Configuration

MPRCCT

Jump to MPRCCT: Circuit Management

MPRFLT

Jump to MPRFLT: Filtering of IP Packets

MPRTRC

Jump to MPRTRC: Trace Management


ECCARD

This command loads and starts the EiconCard. ECCARD must be executed for you to operate WAN Services. ECCARD can also be used to stop the EiconCard, view EiconCard status, and dump the contents of an EiconCard's memory to a file for analysis.


ECDIALER

This command is used to control the EiconCard dialer and physical layer connections using on-board or external modems. ECDIALER instructs an external modem (or a modem integrated into the EiconCard) to dial out, answer calls, and to provide status information.


ECMODULE

If you need to monitor the data communications traffic going through the WAN Connection, ECMODULE lets you analyze different levels of protocols. ECMODULE is not required to run WAN Services: it is a diagnostic and monitoring tool.


ECTEST

This command verifies the validity of the EiconCard's hardware configuration parameters, such as EiconCard type, I/O port address, memory segment address, and interrupt request level (IRQ). ECTEST also verifies the hardware integrity of the EiconCard. ECTEST is not required to run WAN Services: it is a diagnostic tool.


ECVER

The ECVER command scans your hard drive for other Eicon Technology software, and for previous versions of WAN Services.

Note:
This command only detects Version 3.0 and above of the Eicon Technology software.


IPMAP

Links the IP address of the remote router to the circuit specified by MPRCCT. When you issue this command, the IP mapping information you specify is saved to the MPR.INI initialization file. When you run MPR START in the future, the IPMAP information saved in MPR.INI is loaded and used.

You can also use the Eicon SNMP Console program to create and delete IP mappings.


MPR

Starts and stops the IP Routing Services, and displays global routing statistics. Using MPRCCT to create circuits and IPMAP to link circuits to remote IP addresses makes a file called MPR.INI. This initialization file contains circuit and mapping information. When MPR START is executed, the MPR.INI file is read: circuit and mapping information is read, and the circuits are auto-activated.

The auto-activation function can be disabled, if necessary.


MPRCCT

The circuit management utility MPRCCT creates circuits, deletes circuits, and displays status and statistical information. When you issue this command, the circuit information you specify is saved to the MPR.INI initialization file. When you run MPR START in the future, the circuit information saved in MPR.INI is loaded and used to auto-activate the circuit.

You can also use the Eicon SNMP Console program to create and delete circuits.


MPRFLT

You use the MPRFLT utility to create, delete, and modify filters to be applied to IP packet traffic between the local router and remote routers, and to display status information about the IP packet filters currently configured on the router. You can also use the WAN Services Configuration program to create, modify, and delete IP packet filters.


MPRTRC

This utility is used to view and reset the router's internal traces. Both upper level (NDIS) and lower level (NCB) data can be traced, and the information saved to a text file. The size of the trace buffer, and whether it is active, is defined in using the NCPA in the Windows NT Control Panel.


Chapter 9: Command Line Utilities

ECCARD: Starting the EiconCard

Command	ECCARD.EXE
Purpose	Starts, stops, and monitors the EiconCard and its associated protocols. Use ECCARD START to activate WAN Services.
Syntax	ECCARD	START	[/Eiconcard n] [/Mail m] [/Ncb n] [/Show]
	ECCARD	START	/Port p | portname
	ECCARD	STOP	[/Eiconcard n] [/Yes]
	ECCARD	STOP	/Port p | portname
	ECCARD	DUMP	/Eiconcard n [/Binary file] [/Yes]
	ECCARD	LIST	[/Eiconcard n]
	ECCARD	STATUS
Parameters	START /Eiconcard	Starts the specified EiconCard and all X.25 and Frame Relay ports with the Auto-Activate Ports option selected. There is no need to start these ports individually (i.e., START /Port).  All configuration information is taken from the Windows NT registry.
	START /Port	Starts a specific Port. This command can only be issued if this port's EiconCard has already been started.
	STOP	Stops the specified EiconCard or port. Stopping the last or only port on an EiconCard does not stop the EiconCard itself. You must use the command ECCARD STOP to stop the EiconCard.
	DUMP	Dumps EiconCard memory to disk. Using ECCARD DUMP disconnects any active connections and stops only the specified EiconCard.
	LIST	Displays information on each EiconCard protocol module as if it were loaded, but does not actually load the module.
	STATUS	Provides information on the EiconCard(s).
	/Eiconcard n	Indicates the number (n) of the EiconCard to start, stop, or dump when you have more than one EiconCard installed in your PC. You may have up to four EiconCards installed in the WAN Services PC. This parameter is mandatory only with the DUMP option. For other options, if it is not specified, the action is performed on all EiconCards.
	/Mail m	The size (m) of the MAIL trace buffer on the EiconCard, in kilobytes, ranging from 1 to 64. This is used to perform an internal mail trace when directed to do so by a representative of Eicon Technology Customer Services.
	/Ncb n	The size (n) of the NCB trace buffer on the EiconCard, in kilobytes, ranging from 1 to 64. This is used to perform an internal NCB trace when directed to do so by a representative of Eicon Technology Customer Services.
	/Show	Displays detailed information on each EiconCard protocol module as it is loaded.
	/Port p |  portname	Indicates the port number (p) or the port name (portname) of the EiconCard to start, or stop. This parameter is mandatory if acting on a specific port.
	/Yes	Eliminates "Y/N" question from the ECCARD STOP or ECCARD DUMP command. This is useful for batch files.
	/Binary file	The EiconCard dump filename if the default DUMP*.* file is not used. Specify the full path if the file is not in the current directory.
Auto-Activate Ports

Each X.25 or Frame Relay port that you configure as Auto-Activate is automatically started when ECCARD START is issued. This option saves you having to start each port individually with the ECCARD START /P command.

Using ECCARD

ECCARD Error Level Values


Chapter 9: Command Line Utilities

ECCARD: Starting the EiconCard

Using ECCARD

The following examples show how the different ECCARD options can be used.

ECCARD START

The ECCARD START command starts the specified EiconCard or port. When you start an EiconCard all ports are automatically started unless you turn off the Auto-activate option.

Consider these examples:

ECCARD START

Starts all EiconCards in the WAN Services PC that have been configured with the WAN Services Configuration program.

ECCARD START /SHOW

Starts all EiconCards and displays each software module as it is loaded.

ECCARD START /E 4

Starts EiconCard #4.

ECCARD STOP

Stops the specified EiconCard or port. Stopping an EiconCard halts all ports on it. Any active connections are lost. Stopping the last or only port on an EiconCard does not stop the EiconCard itself: you must explicitly stop it.

Examples

ECCARD STOP /E 3

Stops EiconCard #3. It displays the following:

Do you really want to stop CARD 3 ? (Y/N) Y
EiconCard 3 stopped.
Command completed successfully.

ECCARD STOP /E 2 /Y

Stops EiconCard #2, and suppresses the Yes/No message, like this:

EiconCard 2 stopped.
Command completed successfully.

ECCARD DUMP

The DUMP command saves the contents of EiconCard memory to disk for later analysis. Running ECCARD DUMP disconnects all active connections through WAN Services and stops the EiconCard.

If you are having trouble establishing a connection and are unable to find the source of the problems, then a DUMP can be useful. In most cases, the DUMP is done under the advice or supervision of an Eicon Technology representative. The DUMP file can then be analyzed, and a solution found to your problem.

If you are dumping the contents of an EiconCard for the first time, then the default filename is DUMPx.001, where x is the number of the EiconCard. For each subsequent dump, the file extension is incremented by 1: DUMP1.001, DUMP1.002, DUMP1.003, etc. If you delete all the DUMP files from the target directory, then the counter will restart at 001.

Example

ECCARD DUMP /E 2 /B TESTDUMP.DMP

Dumps EiconCard #2 to a file called TESTDUMP.DMP located in the same directory as the ECCARD program.

ECCARD LIST

The ECCARD LIST command displays information on each EiconCard protocol module as if it were being loaded, but does not actually load the module. This is useful to determine if the right software will be loaded based on the configuration selected.

Example

ECCARD LIST > LISTFILE.TXT

Outputs a list of all modules to a file called LISTFILE.TXT.

ECCARD STATUS

The ECCARD STATUS command provides a list of EiconCards and their ports, detailing hardware configuration information based on the Windows NT registry information.

When you issue the ECCARD STATUS command, detailed information about the EiconCard is displayed. For example:

EiconCard Configuration:
Card  Type         Status    PCB       Memory  I/O   IRQ  Segment
1     MPNA/PC      LOADED    800075.1   512 K  380    3   D000
2     EC/PC        HALTED    -          512 K  388    4   D200
3     EC HSI/PC 1M LOADING   800156.4  1024 K  390    5   FD400
4     DPNA/PC      DETECTED  800051.1   512 K  398   11   D600

EiconCard Port mapping:
Card  Port  Port name  Protocol
1     01    MPPORT1    X25
      02    MPPORT2    X25
      03    MPPORT3    HDLC
      04    MPPORT4    HDLC
2     05    ECPORT     X25

The following table explains the headings in this display.

Parameter	Description
Card	EiconCard card number.
I/O	I/O port memory address of the EiconCard. Make sure that no other peripheral is using this I/O port address.
IRQ	Interrupt Request Level used by the EiconCard. Make sure that no other peripheral is using this IRQ on an ISA bus (AT or PC bus). On a Micro Channel bus, the same IRQ can be shared by other Micro Channel cards.
Memory	Memory capacity of the EiconCard.
PCB	Printed Circuit-Board number: this is an identification code showing the revision number of the EiconCard in use. If the software does not detect a PCB number, you will have to check the EiconCard itself for a physically engraved number.
Port	Port number on the specified EiconCard.
Port Name	The name of the port on the specified EiconCard.
Protocol	The protocol currently in use by the specified port.
Segment	Memory segment used by the EiconCard. Make sure that no other peripheral is using this memory segment.
Status	Status of the EiconCard: refer to the following table for a detailed list of all the different EiconCard status values.
Slot	(Not shown in the example above.) Micro-Channel bus slot number.
Type	Type of EiconCard installed in the WAN Services PC and configured by the WAN Services Configuration program.

This table lists the different EiconCard status values:

Status Value	Description
DETECTED	The EiconCard I/O Port Address and Memory Segment has been properly configured, but the Card Identification (type) or IRQ test has failed or has not yet been performed.
DUMPING	The contents of the EiconCard's memory is currently being dumped to disk.
HALTED	All EiconCard tests have been completed successfully, the hardware settings are correct, and the size of the EiconCard's memory has been determined. The EiconCard has now been stopped, and must be reactivated to be used.
IDLE	This EiconCard has not been properly configured with the WAN Services Configuration program. Make sure you have the correct I/O, IRQ, and Memory Segment values configured for this EiconCard.
LOADED	The EiconCard has been loaded, is functioning, and can be used for communication, assuming the Ports have been activated.
LOADING	The necessary protocol modules are being loaded onto the EiconCard.
TESTING	An EiconCard test (ECTEST) is now in progress, or is in an intermediate state of the start process.
Examples

The following examples illustrate how to use ECCARD STATUS.

ECCARD STATUS

Provides detailed information on all EiconCards in the WAN Services PC.

ECCARD STATUS > INFO.TXT

Presents information on all EiconCards in the WAN Services PC, and saves that information to a file called INFO.TXT.


Chapter 9: Command Line Utilities

ECCARD: Starting the EiconCard

ECCARD Error Level Values

ECCARD returns the following error levels.

Error Level	Description
0	SUCCESS. The command was completed successfully.
1	WARNING. A warning was displayed while the command was running. The command was executed anyway.
2	PARTIAL. The command was partially completed. (This occurs mostly when using the ECCARD START command to load all EiconCards at once, but some EiconCards could not be loaded.)
3	ABORT. The CONTROL-C or CONTROL-Break key combinations were pressed while an ECCARD command was executing, or the command was canceled from an input prompt such as: Binary dump file DUMPCARD.DAT already exists, do you want to overwrite? (Y/N) N.
4	FAILED. The command failed. For ECCARD START (without /Eiconcard e), this happens when ALL the EiconCards specified in the Windows NT registry could not be loaded.


Chapter 9: Command Line Utilities

ECDIALER: Using a Modem

Command	ECDIALER.EXE
Purpose	Dials, hangs up, monitors, and configures the EiconCard dialers.
Syntax	ECDIALER STORE		[/Port p | portname] [/Main n] [/Config x] [/Bitrate n][/ALternate n] [/Aconfig x] [/Abitrate n]
	ECDIALER DIAL		[/Port p | portname]] [/Number n] [/Config x] [/Bitrate n]
	ECDIALER EXEC		/File script [/Port p | portname]
	ECDIALER ANSWER		/Enable|/Disable [/Port p | portname]
	ECDIALER HANGUP		[/Port p | portname]
	ECDIALER STATUS		[/Port p | portname]
	ECDIALER LINE		/ON | /OFF [/Port p | portname]
Parameters	STORE	Store the primary or alternate telephone number to call.
	DIAL	Dial the telephone number specified with the /N parameter. If no number is specified, dial the Main or Alternate number that has been STOREd. If the Retry parameter has been enabled in the WAN Services Configuration program, then dialing is repeated until successful.
	EXEC	Execute a script for programming an external modem when using the Hayes asynchronous dialer.
	ANSWER	Enables or disables the dialer from answering incoming calls.
	HANGUP	Hangs up the current connection.
	STATUS	Performs the same function as the ECMODULE DIALER STATUS command. See ECMODULE for more information.
	LINE	Defines the setting of the Data Rate Select (DRS) signal on an RS-232 interface (Direct Dialer only).
	/Port p | portname	The EiconCard port or portname through which you wish to dial. Port #1 is the default.
	/Main n	Sets the main telephone number. This is the first number dialed when the ECDIALER DIAL command is issued without a number parameter.
	/Config x	The modem protocol to employ when originating a call using a V.32bis dialer: V22bis, V32, V32TCM, or V32bis.
	/Bitrate n	The bits per second rate to employ when originating a call using a V.32bis dialer: 1200, 2400, 4800, 7200, 9600, 12K, or 14.4K.
	/ALternate n	Sets the alternate telephone number. This is dialed when the ECDIALER DIAL command is issued.
	/AConfig x	The modem protocol to employ when originating a call using a V.32bis dialer: V22bis, V32, V32TCM, or V32bis. This setting is applied to the /ALternate telephone number.
	/ABitrate n	The bits per second rate to employ when originating a call using a V.32bis dialer: 1200, 2400, 4800, 7200, 9600, 12K, or 14.4K. This setting is applied to the /ALternate telephone number.
	/Number n	Dial the override number n, regardless of what is stored as the Primary or Alternate phone number.
	/File script	Filename of the ECDIALER script file to execute.
	/Enable	Enable the dialer to answer any incoming calls.
	/Disable	Disable the dialer from answering any incoming calls.
	/ON	Switches the Data Rate Select (DRS) line to ON This option is not available for DPNA, MPNA or HSI EiconCards.
	/OFF	Switches the Data Rate Select (DRS) line to OFF. This option is not available for DPNA, MPNA or HSI EiconCards.
The following commands apply to ISDN users only. Use these commands when storing or dialing a number. See "ECDIALER and ISDN" for more information.

For ISDN NI-1 (North America), use the following command to store and dial a number:

	ECDIALER STORE	/Port n | portname [/Main n] [/NType type] [/NPlan plan] [/SAddr subaddr] [/Tns tns] [/SType subtype] [BCtype bearer]
	ECDIALER DIAL	/Port p | portname  [/NUmber n] [/Tns tns] [NType type] [/NPlan plan] [/SType subtype] [/SAddr subaddr] [/BCtype bearer]
For ISDN TPH1962 (Australia), use the following command to store and dial a number:

	ECDIALER STORE	/Port n | portname [/Main n] [/NType type] [/NPlan plan] [/SAddr subaddr] [/SType subtype] [BCtype bearer]
	ECDIALER DIAL	/Port p | portname [/NUmber n] [/NPlan plan] [NType type] [/SType subtype] [/SAddr subaddr][/BCtype bearer]
For ISDN 5ESS (AT&T North America), use the following command to store and dial a number:

	ECDIALER STORE	/Port n | portname [/Main n] [/SAddr subaddr] [/SType subtype] [BCtype bearer]
	ECDIALER DIAL	/Port p | portname [/NUmber n] [/SType subtype] [/SAddr subaddr] [/BCtype bearer]
For ISDN Euro-ISDN (Europe), use the following command to store and dial a number:

	ECDIALER STORE	/Port n | portname [/Main n] [/SAddr subaddr] [/SType subtype] [BCtype bearer]
	ECDIALER DIAL	/Port p | portname [/Number n] [/SType subtype] [/SAddr subaddr] [/BCtype bearer]
You can use ECDIALER to make and receive calls, display status information, and to hang up the line.

Modem Protocols

Using ECDIALER


Chapter 9: Command Line Utilities

ECDIALER: Using a Modem

Modem Protocols

Use the following table to determine your bitrate-configuration choices (/Config  /Bitrate parameter) for using ECDIALER with the V.32bis EiconCard dialer:

Protocol	Speed	Bit Rate	Config
V.32bis	14,400 TCM	14.4 K	V.32bis
V.32bis	12,000 TCM	12.0 K	V.32bis
V.32bis	9,600 TCM	9,600	V.32bis
V.32bis	7,200 TCM	7,200	V.32bis
V.32bis	4,800 QAM	4,800	V.32bis
V.32	9,600 TCM	9,600	V.32TCM
V.32	9,600 QAM	9,600	V.32
V.32	4,800 QAM	4,800	V.32
V.22bis	2,400 QAM	2,400	V.22bis
V.22bis	1,200 DPSK	1,200	V.22bis
Acronyms:  TCM (Trellis Code Modulation)
QAM (Quadrature Amplitude Modulation)
DPSK (Differential Phase Shift Keying)


Chapter 9: Command Line Utilities

ECDIALER: Using a Modem

Using ECDIALER

The following examples illustrate how to use ECDIALER.

ECDIALER STORE /P 2 /M 555-1212
ECDIALER DIAL /P 2

Stores the primary phone number for port #2 and then dials it.

ECDIALER ANSWER /E /P 3

Enables port #3 to accept incoming calls.

ECDIALER EXEC /F LOGON.SCR /P 2

Executes the script file LOGON.SCR on the Hayes dialer connected to port #2 on the WAN Services PC.

ECDIALER STORE /M 555-1212 /C V32BIS /B 144K /P 2
ECDIALER DIAL /P 2

Commands the V32bis dialer to dial the number 555-1212, using the V.32bis modem protocol at 14,400 bits per second.

ECDIALER STORE /M 555-1212 /C V22BIS /B 1200 /P 2
ECDIALER DIAL /P 2

Instructs the V32bis dialer to dial the number 555-1212, using the V.22bis protocol at 1200 bits per second.


Chapter 9: Command Line Utilities

ECDIALER and ISDN

This section contains information pertinent to using the ECDIALER command to control the EiconCard S51 with ISDN support.

Using ECDIALER with ISDN NI-1 (North America)

Using ECDIALER with TPH1962 (Australia)

Using ECDIALER with 5ESS (AT&T)

Using ECDIALER with Euro-ISDN


Chapter 9: Command Line Utilities

ECDIALER and ISDN

Using ECDIALER with ISDN NI-1 (North America)

This section describes how to make an ISDN connection to an NI-1 switch.

X.25 on the D-channel

If a port on the EiconCard has been configured as a D-channel to carry X.25 data, the only ecdialer command that you can use on that port is the ecdialer status command. Other ecdialer commands are not supported for X.25 D-channels.

ISDN NI-1 Parameters

The following table below lists all the ISDN NI-1 specific parameters for ECDIALER.

Parameter	Explanation
/Main n	Stores the main telephone number. This is the first number dialed when you issue the ECDIALER DIAL command without a number parameter. This option is not required for packet calls when connecting to ISDN through an NI-1 type switch.
/NUmber n	Dials the number specified, regardless of what is stored as the main telephone number.
/NType type	Specifies the remote number type, Abbreviated, International, National, Netspecific, Subscriber, or Unknown (default), assigned to the called party by its local telephone company.
/NPlan plan	Numbering plan for the ISDN dialer. Possible values are Unknown, ISDN (default), Data, Private, Telex, or National.
/SAddr subaddr	Provides the subaddress to further identify the remote terminal on the ISDN Basic Rate Interface. If two terminals share the same directory number, the subaddress identifies which terminal will answer a particular incoming call.
/SType subtype	The types of subaddress used, NSAP (default) or User. If you include this option in the command, you must also use the /SAddr option.
/Tns tns	The transit network selector allows you to specify the transit carrier to be used on long-distance calls.
/BCtype bearer	Defines the Bearer Capability (i.e., the information-transfer rate and mode). Possible values are 56K, 64K (default), or Packet. 56K and 64K are for circuit-switched services, while Packet is the equivalent of 64K for packet-switched services.
/Port p | portname	The EiconCard port number or port name through which you wish to dial. Port 1 is the default. With ISDN connections, this refers to the EiconCard channel you are using.

ECDIALER STORE

ECDIALER DIAL

ECDIALER ANSWER

ECDIALER HANGUP

ECDIALER STATUS


ECDIALER STORE

Command syntax:

ECDIALER STORE	[/M mainnumber] [/NType type] [/NPlan plan] [/Tns tns] [/SAddr subaddress] [/SType subtype] /BCtype bearercapability /Port port

The number stored used ECDIALER STORE permanently replaces whatever value was previously configured or stored.


ECDIALER DIAL

Command syntax:

ECDIALER DIAL	[/NUmber number] [/NType type] [/NPlan plan] [/Tns tns]  [/SAddr subaddress] [/SType subtype] [/BCtype bearercapability] /Port port

To dial a number that has been configured or that has already been stored using the ECDIALER STORE command, enter the following command:

ecdialer dial /P port


ECDIALER ANSWER

Command syntax:

ECDIALER ANSWER	/Enable | /Disable /Port port

Enables /disables the dialer to answer any incoming calls. Answer Mode allows a correctly configured port to answer a call.


ECDIALER HANGUP

Command syntax:

ECDIALER HANGUP	/Port port

This command allows you to hangup an ISDN connection on the specified port.


ECDIALER STATUS

Command syntax:

ECDIALER STATUS	/Port port

ECDIALER STATUS displays summary information on all ports. Specify a port name or number to see detailed information about a specific port.


Chapter 9: Command Line Utilities

ECDIALER and ISDN

Using ECDIALER with TPH1962 (Australia)

This section describes how to make an ISDN connection to the TPH1962 switch type used in Australia.

X.25 on the D-channel

If a port on the EiconCard has been configured as a D-channel to carry X.25 data, the only ecdialer command that you can use on that port is the ecdialer status command. Other ECDIALER commands are not supported for X.25 D-channels.

ISDN TPH1962 Parameters

The following table below lists all the ISDN TPH1962 specific parameters for ECDIALER.

Parameter	Explanation
/Main n	Stores the main telephone number. This is the first number dialed when you issue the ECDIALER DIAL command without a number parameter.
/NUmber n	Dials the number specified, regardless of what is stored as the main telephone number.
/NType type	Specifies the remote number type, Abbreviated, International, National, Netspecific, Subscriber, or Unknown (default), assigned to the called party by its local telephone company.
/NPlan plan	Numbering plan for the ISDN dialer. Possible values are Unknown, ISDN (default), Data, Private, Telex, or National.
/SAddr subaddr	Provides the subaddress to further identify the remote terminal on the ISDN Basic Rate Interface. If two terminals share the same directory number, the subaddress identifies which terminal will answer a particular incoming call.
/SType subtype	The types of subaddress used, NSAP (default) or User. If you include this option in the command, you must also use the /SAddr option.
/BCtype bearer	Defines the Bearer Capability (i.e., the information-transfer rate and mode). Possible values are 56K, 64K (default), or Packet. 56K and 64K are for circuit-switched services, while Packet is the equivalent of 64K for packet-switched services.
/Port p | portname	The EiconCard port number or port name through which you wish to dial. Port 1 is the default. With ISDN connections, this refers to the EiconCard channel you are using.
ECDIALER STORE

ECDIALER DIAL

ECDIALER ANSWER

ECDIALER HANGUP

ECDIALER STATUS


ECDIALER STORE

Command syntax:

ECDIALER STORE	[/M mainnumber] [/NType type] [/NPlan plan] [/SAddr subaddress] [/SType subtype] /BCtype bearercapability /Port port

The number stored used ECDIALER STORE permanently replaces whatever value was previously configured or stored.


ECDIALER DIAL

Command syntax:

ECDIALER DIAL	[/NUmber number] [/NType type] [/NPlan plan] [/SAddr subaddress] [/SType subtype] [/BCtype bearercapability] /Port port

To dial a number that has been configured or that has already been stored using the ECDIALER STORE command, enter the following command:

ECDIALER DIAL /P port


ECDIALER ANSWER

Command syntax:

ECDIALER ANSWER	/Enable | /Disable /Port port

Enables/disables the dialer to answer any incoming calls. Answer Mode allows a correctly configured port to answer a call.


ECDIALER HANGUP

Command syntax:

ECDIALER HANGUP	/Port port

This command allows you to hangup an ISDN connection on the specified port.


ECDIALER STATUS

Command syntax:

ECDIALER STATUS	/Port port

ECDIALER STATUS displays summary information on all ports. Specify a port name or number to see detailed information about a specific port.


Chapter 9: Command Line Utilities

ECDIALER and ISDN

Using ECDIALER with 5ESS (AT&T)

This section describes how make an ISDN connection to the 5ESS switch type.

ISDN 5ESS Parameters

The following table below lists all the ISDN 5ESS specific parameters for ECDIALER:

Parameter	Explanation
/Main n	Stores the main telephone number. This is the first number dialed when you issue the ECDIALER DIAL command without a number parameter.
/NUmber n	Dials the number specified, regardless of what is stored as the main telephone number.
/SAddr subaddr	Provides the subaddress to further identify the remote terminal on the ISDN Basic Rate Interface. If two terminals share the same directory number, the subaddress identifies which terminal will answer a particular incoming call.
/SType subtype	The types of subaddress used, NSAP (default) or User. If you include this option in the command, you must also use the /SAddr option.
/BCtype bearer	Defines the Bearer Capability (i.e., the information-transfer rate and mode). Possible values are 56K, 64K (default), or Packet. 56K and 64K are for circuit-switched services, while Packet is the equivalent of 64K for packet-switched services.
/Port p | portname	The EiconCard port number or port name through which you wish to dial. Port 1 is the default. With ISDN connections, this refers to the EiconCard channel you are using.

ECDIALER STORE

ECDIALER DIAL

ECDIALER ANSWER

ECDIALER HANGUP

ECDIALER STATUS


ECDIALER STORE

Command syntax:

ECDIALER STORE	[/M mainnumber] [/SAddr subaddress] [/SType subtype] /BCtype bearercapability /Port port

The number stored used ECDIALER STORE permanently replaces whatever value was previously configured or stored.


ECDIALER DIAL

Command syntax:

ECDIALER DIAL	[/NUmber number] [/SAddr subaddress] [/SType subtype] [/BCtype bearercapability] /Port port

To dial a number that has been configured or that has already been stored using the ECDIALER STORE command, enter the following command:

ECDIALER DIAL /P port


ECDIALER ANSWER

Command syntax:

ECDIALER ANSWER	/Enable | /Disable /Port port

Enables/disables the dialer to answer any incoming calls. Answer Mode allows a correctly configured port to answer a call.


ECDIALER HANGUP

Command syntax:

ECDIALER HANGUP	/Port port

This command allows you to hangup an ISDN connection on the specified port.


ECDIALER STATUS

Command syntax:

ECDIALER STATUS	/Port port

ECDIALER STATUS displays summary information on all ports. Specify a port name or number to see detailed information about a specific port.


Chapter 9: Command Line Utilities

ECDIALER and ISDN

Using ECDIALER with Euro-ISDN

This section describes how make an ISDN connection to the Euro-ISDN switch type.

X.25 on the D-channel

If a port on the EiconCard has been configured as a D-channel to carry X.25 data, the only ecdialer command that you can use on that port is the ecdialer status command. Other ecdialer commands are not supported for X.25 D-channels.

ISDN Euro-ISDN Parameters

The following table below lists all the ISDN Euro-ISDN specific parameters for ECDIALER:

Parameter	Explanation
/Main n	Stores the main telephone number. This is the first number dialed when you issue the ECDIALER DIAL command without a number parameter.
/NUmber n	Dials the number specified, regardless of what is stored as the main telephone number.
/NType type	Specifies the remote number type, Abbreviated, International, National, Netspecific, Subscriber, or Unknown (default), assigned to the called party by its local telephone company.
/NPlan plan	Numbering plan for the ISDN dialer. Possible values are Unknown, ISDN (default), Data, Private, Telex, or National.
/SAddr subaddr	Provides the subaddress to further identify the remote terminal on the ISDN Basic Rate Interface. If two terminals share the same directory number, the subaddress identifies which terminal will answer a particular incoming call.
/SType subtype	The types of subaddress used, NSAP (default) or User. If you include this option in the command, you must also use the /SAddr option.
/Tns tns	The transit network selector allows you to specify the transit carrier to be used on long-distance calls.
/BCtype bearer	Defines the Bearer Capability (i.e., the information-transfer rate and mode). Possible values are 56K, 64K (default), or Packet. 56K and 64K are for circuit-switched services, while Packet is the equivalent of 64K for packet-switched services.
/Port p | portname	The EiconCard port number or port name through which you wish to dial. Port 1 is the default. With ISDN connections, this refers to the EiconCard channel you are using.

ECDIALER STORE

ECDIALER DIAL

ECDIALER ANSWER

ECDIALER HANGUP

ECDIALER STATUS


ECDIALER STORE

Command syntax:

ECDIALER STORE	[/M mainnumber] [/NType type] [/NPlan plan] [TNS tns] [/SAddr subaddress] [/SType subtype] /BCtype bearercapability /Port port

The number stored used ECDIALER STORE permanently replaces whatever value was previously configured or stored.


ECDIALER DIAL

Command syntax:

ECDIALER DIAL	[/NUmber number] [/NType type] [/NPlan plan] [TNS tns] [/SAddr subaddress] [/SType subtype] [/BCtype bearercapability] /Port port

To dial a number that has been configured or that has already been stored using the ECDIALER STORE command, enter the following command:

ECDIALER DIAL /P port


ECDIALER ANSWER

Command syntax:

ECDIALER ANSWER	/Enable | /Disable /Port port

Enables/disables the dialer to answer any incoming calls. Answer Mode allows a correctly configured port to answer a call.


ECDIALER HANGUP

Command syntax:

ECDIALER HANGUP	/Port port

This command allows you to hangup an ISDN connection on the specified port.


ECDIALER STATUS

Command syntax:

ECDIALER STATUS	/Port port

ECDIALER STATUS displays summary information on all ports. Specify a port name or number to see detailed information about a specific port.


Chapter 9: Command Line Utilities

ECDIALER Script Language

A modem script tells your dialer what information to send, in response to specific cues. A script is like a program, and elaborate scripts can be written to automate a wide range of communications functions. ECDIALER script is used for the AT Dialer and programming of external asynchronous/synchronous Hayes compatible modems.

The ECDIALER Script feature supports most external modems. Use any ASCII text editor to create the script file.

Modem Considerations (Hayes AT)

Sample Script

Blank lines are accepted in the script. All commands must start in the first column. Valid commands are as follows:

:label  When you use a GOTO label command, the script jumps to the specified label and continues execution from there. A label is any alphanumeric ASCII string with a colon in the first position. The "æ" (dash) and "_" (underscore) characters can also be used for the label.

*comment  Any script line starting with an asterisk (*) in the first column is treated as a comment, and ignored by the script. A comment is only there for your information.

CLOSE_COMM  This command closes the EiconCard port which is connected to the external modem. This does not hang up the modem. CLOSE_COMM must be the last statement executed when you are finished with the port.

DIAL number  This command dials the specified number. Success or failure can be tested with the IFERROR statement. A MATCH command is commonly used directly after DIAL to look for the CONNECT message from the modem.

GOTO label  This command causes processing of the script file to continue at the specified label. The label can be forward or backward, and can thus be used for looping.

IFERROR label  This command causes execution of the script file to continue from the specified label if an error occurred during one of the following commands: MATCH, DIAL, OPEN_COMM, or TYPE. Use IFERROR immediately after these commands to test for errors.

MATCH string  This command pauses execution of the script file until input is received that matches the specified string. For instance, a Hayes modem usually returns "OK" to acknowledge a command. Use MATCH "OK" to wait for the "OK" string: the string must be enclosed in quotation marks. MATCH waits the number of seconds specified in a previous TIMEOUT command. Use IFERROR directly following MATCH to test for success or failure. This command reads and ignores any characters before the match is found or a timeout occurs.

OPEN_COMM  This command initializes the EiconCard for communication with the external modem. The initialization values for this command are specified with the five SET_xxxx commands. Success or failure is determined with the IFERROR command.

PAUSE  Pauses execution of the script file until any key is pressed on the keyboard. This is useful when debugging a script.

PRINT string  Displays the specified string on the screen.

SET_DATA_BITS n  This command sets the number of data bits put into effect by a subsequent OPEN_COMM command. Valid values for "n" are 7 or 8 data bits. The default is 8 data bits.

This is the asynchronous data bit setting used by the EiconCard Hayes dialer port to communicate with an external modem.

SET_PARITY n  Selects the parity of the connection put into effect by a subsequent OPEN_COMM command. Valid values for n are: NO_PARITY, EVEN_PARITY, or ODD_PARITY. The default is NO_PARITY.

This is the parity setting used by the EiconCard Hayes dialer port to communicate with an external modem.

SET_PORT n  Specifies the EiconCard port to use when communicating with a modem. SET PORT takes effect when an OPEN_COMM command is executed. Valid values for n range from 1 to 48. The default is 1.

SET_SPEED n  Sets the bits per second (bps) rate put into effect by a subsequent OPEN_COMM command. Valid values are: 1200, 2400, 4800, 9600. The default is 2400 bps.

This is the speed setting used by the EiconCard Hayes dialer port to communicate with an external modem.

SET_STOP_BITS n  Selects the number of stop bits. Set n to 1 or 2 stop bits. By default, 1 stop bit is used. This command is not taken into account by OPEN_COMM, but you must have the same stop bit setting as the computer to which you are connected.

This is the stop bits setting used by the EiconCard Hayes dialer port to communicate with an external modem.

TIMEOUT n  Sets the timeout value in seconds for the MATCH command. Default is 15 seconds.

TYPE string  | hex,...  This command sends a string to the modem. The string must be enclosed in quotes (single or double) and can also comprise any text or hexadecimal value. If you need to insert control codes, enter them in hexadecimal. Here is an example of TYPE:

TYPE "AT\S",07,'ATDT5551212',0d

Success or failure of this command can be tested with the IFERROR command.

WAIT n  Causes the execution of the script file to pause for n seconds.


Chapter 9: Command Line Utilities

ECDIALER Script Language

Modem Considerations (Hayes AT)

If Dialer type is configured as "HAYES AT" in the WAN Services Configuration program, certain parameters must be set on your external modem. The table below lists settings and modes which a Hayes-compatible modem should be set to in order to interoperate successfully with WAN Services.

AT Command	Description
AT&F	Restores all factory defaults and deletes all stored numbers.
AT&C1	Sets the Data Carrier Detect (DCD) to track the data carrier from the remote modem. DCD is on when the data carrier is detected.
AT&D2 or D3	Sets the Data Terminal Ready (DTR) mode so that the modem hangs up, assumes command state, and disables auto-answer when an ON-to-OFF transition of DTR is detected.
AT&M1 and &Q1	This sets the modem to synchronous mode 1. The call placement is initiated using asynchronous methods, but the modem switches to synchronous operation when the connection is fully established. The modem returns to asynchronous mode when it detects an ON-to-OFF transition on the DTR interchange circuit.
AT&S1or S2	Sets the Data Set Ready (DSR) to trade carrier. The DSR cannot be changed from this mode if the modem is operating in synchronous mode.

If the AT commands given above are not compatible with your modem, you should determine from your modem’s operating guide which equivalent commands are used to control the following parameters:

Parameter	Settings Required
DTR on/off	The Data Terminal Ready signal will be turned off to cause the modem to hang up. The modem should interpret DTR this way.
DSR on/off	The Data Set Ready signal is used to detect a connection. It should be turned on only when data is ready to be sent (modem negotiation complete).
Sync/Async mode	The modem must operate in asynchronous mode while in an off-line command state. It must operate in synchronous mode from the time the connection is fully established until the on-line data-transfer state is terminated.
The Request-To-Send/Clear-To-Send (RTS/CTS) delay interval value may also need to be adjusted. This value determines the delay time a modem uses before turning on CTS after detecting an OFF-to-ON transition on RTS.

The RTS/CTS delay interval can be adjusted by adjusting the modem’s S26 register. If you are using a Hayes-compatible modem, this is achieved with the AT command:

ATS26=x

where x is the value of the delay interval in increments of 10 ms.

If you do not own a Hayes compatible modem, consult your modem’s operating guide for directions on adjusting the interval between detection of the Request-To-Send mode and enabling of the Clear-To-Send signal.


Chapter 9: Command Line Utilities

ECDIALER Script Language

Sample Script

The ECDIALER script does three things:

•	Initializes the EiconCard for communications with the modem. This is done with the SET_PORT, SET_DATA_BIT, SET_SPEED, and finally the OPEN_COMM commands.

•	Programs the modem. The modem is set in asynchronous mode using V.22, and then this configuration is written into the modem's permanent memory. This is done with the Type "AT xxxx" command, where xxxx is a Hayes AT command. The modem responds with an "OK" string.

•	Calls the DATAPAC online service from Montreal. This is done with the Type "ATDT8614750" command. When a connection is established, the modem answers with a "CONNECT 2400" string.

Below is the sample script text that works with a Hayes-compatible modem. Therefore, the settings may be slightly different for your own particular modem type. Use this example as a base for writing your own script.

*****************************************************************
*
* This script file is used to configure *
* hayes-compatible modems. *
*
*****************************************************************

*close_comm
set_port 3
set_speed 9600
set_parity NO_PARITY
set_data_bits 8
iferror bye_comm
print "Initialization successful "
wait 1
******************************************************************
*  The AT (ATtention code) is examined by modems which support   *
*  auto bauding in order to determine the communications and     *
*  parity setting of the DTE device. Modems which do not         *
*  support auto bauding can only communicate at the configured   *
*  speed and parity setting.                                     *
*  Some modems may require that the ATtention code be sent twice.*
*  If this is the case, repeat the sending of the ATtention code.*
******************************************************************
type "AT",0d,0a
iferror bye_t1
timeout 15
match "OK"
iferror bye_m1
***************************************
*  Programming modem                  *
***************************************
***************************************
***  Initialize to factory settings ***
***************************************
type "AT&F",0d,0a
match "OK"
iferror FACTORY
***************************************
*** Set speaker volume to low       ***
***************************************
type "ATL1",0d,0a
match "OK"
iferror ATFORM
***************************************
*** Select V22bis modulation        ***
*** when operating at               ***
*** 1200 bps instead of Bell 103,   ***
*** unless you want Bell 103.	      ***
***************************************
type "ATB",0d,0a
match "OK"
iferror MODERR
***************************************
*** DCD setting AT&C1               ***
*** DCD is asserted by modem only   ***
*** if a data carrier which meets   ***
*** the modems suitable criteria    ***
*** is present.  On some modems     ***
*** the factory setting for DCD     ***
*** to remain on at all times       ***
*** disregarding the                ***
*** state of the data carrier.      ***
***************************************
type "AT&C1",0d,0a
match "OK"
iferror TELCO
wait 1
***************************************
*** DTR Setting AT&D2               ***
*** Set modem to answer when DTR is ***
*** raised by the DTE and set to hangup*
*** to asynchronous command mode    ***
*** when DTR switches from ON to OFF.**
***************************************
type "AT&D2",0d,0a
match "OK"
iferror TELCO
***************************************
*** ATS0 = 1"                       ***
*** Set modem to answer on the first***
*** ring.                           ***
***************************************
type "ATS0=1",0d,0a
match "OK"
iferror TELCO
***************************************
*** Asyn/Sync Mode Selection  AT&M1 ***
***                                 ***
*** Call is initiated in asynchronous**
*** mode.  The modem will automatically*
*** switch to synchronous mode once the*
*** telephone connection is established.*
*** The factory setting for most modems*
*** is asynchronous.                ***
***                                 ***
***************************************
type "AT&M1",0d,0a
match "OK"
iferror TELCO
***************************************
*** DSR setting  AT&S1              ***
***                                 ***
*** DSR is controlled by the modem. ***
*** With this setting, DSR is asserted*
*** when the modem completes answer ***
*** tone detection and training.  If***
*** the modem hangups after dialing ***
*** and answer tone detection, this ***
*** setting is the cause.  The factory*
*** setting for most modems is to   ***
*** DSR at all times.               ***
***                                 ***
***************************************
type "AT&S1",0d,0a
match "OK"
iferror TELCO
***************************************
*** Write active configuration to   ***
*** nonvolatile memory. These settings*
*** will be restored automatically  ***
*** whenever the modem is turned on.***
***                                 ***
***************************************
type "AT&W",0d,0a
match "OK"
iferror TELCO
goto bye
:TELCO
print "TELCO ERROR"
goto exit
:bye_t1
print "Error during modem programming. Type failed."
goto exit
:MODERR
print "Error while setting modulation for 1200 bauds"
goto exit
:FACTORY
print "Error while initializing to factory setting"
goto exit
:bye_m1
print "No answer from modem."
goto exit
:bye_comm
print "**** INIT ERROR !!"
goto exit
:bye
print "Modem programmed successfully"
:exit


Chapter 9: Command Line Utilities

ECTEST: Testing the EiconCard

Command	ECTEST.EXE
Purpose	ECTEST is the EiconCard test program. The purpose of ECTEST is to validate the EiconCard hardware configuration and verify the integrity of the hardware component of the server through a series of small tests. You must have configured an EiconCard using the WAN Services Configuration program to test it with ECTEST.
Syntax	ECTEST	[/Eiconcard e] [/Continuous] [/Show] [/FOrce]
Parameters	/Eiconcard e	Indicates a specific EiconCard to test, where e is the EiconCard number, as specified by the WAN Services Configuration program. If no EiconCard number is specified, then all EiconCards configured in theWindows NT registry are tested.
	/Continuous	Continuous testing. The test sequence repeats itself until CTRL-C or CTRL-BREAK is pressed.
	/Show	Activates the verbose option.This provides more detailed information about the tests being performed than is normally displayed by ECTEST.
	/FOrce	Stops the card and forces the execution of the EiconCard tests, even when an application is already running on the EiconCard. If no card number is specified, then all configured EiconCards are tested, even if an application is running on them. This deactivates the application(s).

ECTEST tests the EiconCard. It verifies the integrity of the hardware component of the WAN Services through a series of small tests. You must have configured an EiconCard using the Eicon Configuration program to be able to test it with ECTEST.

If an attempt is made to run ECTEST on an EiconCard in the "loaded" state, then a warning is issued to the user and no tests are performed. If the /FOrce parameter is used with ECTEST, then the EiconCard is halted before ECTEST performs its diagnostics. The EiconCard software must be re-loaded afterwards to function correctly.

Using ECTEST

ECTEST Display Screen

ECTEST Error Messages

Hardware Tests

ECTEST Error Levels


Chapter 9: Command Line Utilities

ECTEST: Testing the EiconCard

Using ECTEST

The following examples illustrate how to use ECTEST.

ECTEST /C

Continuously tests all EiconCards that have been configured with the WAN Services Configuration program.

ECTEST /E 2 /S

Performs regular tests on EiconCard #2, and displays the results in verbose form.

ECTEST /S > TEST.TXT

Places the EiconCard test results into a text file called TEST.TXT.

ECTEST | MORE

Displays the ECTEST results one screen at a time, uses the DOS command MORE.

ECTEST /FO

Deactivates any loaded EiconCard(s), and tests them. Using this option stops the EiconCard(s).


Chapter 9: Command Line Utilities

ECTEST: Testing the EiconCard

ECTEST Display Screen

A screen similar to the following appears when you run ECTEST without the verbose option:

EiconCard Self-Test Utility
ECTEST 1.01 Rev.01
Copyright (c) Eicon Technology Corporation 1995. All Rights Reserved.

                         -------------------------
                            Card #1: MPNA/PC

                            CARD CONFIGURATION:

I/O Port Address        :  798
Memory Segment Address  :  de00
Interrupt Request Level :  4
Memory size             :  2048 K

                             CARD DIAGNOSTIC:
In progress...

Multi-Port Network Adapter/PC, Diagnostic:  :  Passed

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

                            DIAGNOSTIC SUMMARY:

Card #1: Success.

Standard	Description
Slot Number	Micro Channel EiconCards only. This indicates the slot number of the EiconCard.
I/O Port Address	Indicates the base I/O port address of the EiconCard.
Memory Segment Address	Shows the beginning address of the EiconCard's memory segment.
Interrupt Request Level	Displays the IRQ currently used by the EiconCard.
Memory Size	Amount of memory on the EiconCard, in kilobytes.

Each time an EiconCard is tested, the validity of its configuration (EiconCard type, IRQ, I/O Address, and Memory Segment) is verified. If a configuration error is detected, then no further tests are performed until a correct EiconCard Configuration is set with the WAN Services Configuration program. An error may mean that the jumpers or switch settings on the EiconCard, and the values set in the Eicon Configuration Program, do not match.

If no valid EiconCard configuration parameters can be found, there may be no available resources on your host computer, or there may be a hardware problem with the EiconCard.

If the tested EiconCard configuration values are found to be valid, then a set of tests on the EiconCard's hardware is performed. A test that fails indicates a hardware problem on the EiconCard.


Chapter 9: Command Line Utilities

ECTEST: Testing the EiconCard

ECTEST Error Messages

For a list of ECTEST error messages, and instructions on what you are supposed to do when you receive an error message, see the WANNTERR.TXT file located in your WAN Services installation directory.


Chapter 9: Command Line Utilities

ECTEST: Testing the EiconCard

Hardware Tests

The following is an extensive list of the tests that may be performed by ECTEST on a given EiconCard. All tests may not be relevant to all EiconCards. In the /Show operating mode, the name and result ("Passed" or "Failed") for each test is displayed. A test that fails indicates the possibility of a hardware problem on the EiconCard. If at least one of the tests fails, the EiconCard diagnostic is reported to have failed. Here is a description of each hardware test:

Hardware Test	Description
4K Memory Window test	Tests the circuitry that provides access to the EiconCard's memory.
CIO Registers Access test	Tests the Register Access of the Counter Timer and Parallel I/O Unit (CIO) chip.
CIO Timers test	Tests the Timers of the Counter Timer and Parallel I/O Unit (CIO) chip.
CIO Interrupt test	Counter Timer and Parallel I/O Unit (CIO) chip Interrupt to Main CPU test.
DMA Registers Access test	Tests the EiconCard's Direct Memory Access channel registers.
DMA Data Transfer test	Tests the EiconCard's Direct Memory Access channel transfers.
DMA Interrupt test	Tests the EiconCard's Direct Memory Access channel interrupts.
CPU test	Tests the main microprocessor that runs the EiconCard.
EC to HOST Interrupt test	Tests the EiconCard to Host interrupt circuitry.
Memory test	Tests the EiconCard's onboard memory.
HOST to EC Interrupt test	Host computer to EiconCard interrupt test.
I/O Interface test	Tests the EiconCard to Host I/O interface registers.
Modem Registers Access test	Tests the EiconCard's modem registers.
Modem Receiver to EC Interrupt test	Tests the modem's receiver interrupt of the EiconCard's CPU.
Modem Transmitter to EC Interrupt test	Tests the modem's transmitter interrupt of the EiconCard's CPU.
Modem Local Analog Loopback test	Performs a local analog loopback test on the modem on the EiconCard.
Pseudo DMA Data Transfer test	Tests the simulated Direct Memory Access (DMA) channels on the EiconCard.
SCC Registers Access test	Tests the Register Access of the Serial Communications Controller (SCC) chip.
SCC Internal Loop test	Serial Communications Controller (SCC) chip Internal loopback test.
SCC Interrupt test	Tests the Interrupt of the Serial Communications Controller (SCC) chip to main CPU.
SCP Registers Access test	Tests the integrity of the Serial control Port link between the EiconCard’s CPU and the ISDN S/T Interface Transceiver chip.
CPU SCC Loopback test	Tests the integrity of the Serial Communications Controller.
CPU ISDN S/T Transceiver Loopback  test	Tests the integrity of the Interchip Digital Link between the EiconCard’s CPU and the ISDN S/T Transceiver chip.

If one or more tests fail, run them again using the /S option, and save the results to a text file using the > redirector, like this:

ECTEST /S > CARDTEST.TXT

This will write detailed information about the tests to a text file called CARDTEST.TXT. You can then print this file, and provide a copy to your Eicon Technology distributor.


Chapter 9: Command Line Utilities

ECTEST: Testing the EiconCard

ECTEST Error Levels

An error level code is issued when ECTEST finishes; this can be useful when writing batch files. Here is a list of the ECTEST error levels:

Error Level	Description
0	Command completed successfully.
1	Command line syntax error.
2	EiconCard driver not loaded.
3	Command aborted by Control-C key.
4	EiconCard configuration file could not be found.
5	Specified EiconCard number could not be found in the EiconCard configuration file.
7	Command ignored: Application software is running on the EiconCard.
10	Invalid I/O Port address or hardware failure.
11	Invalid Segment address or hardware failure.
12	Invalid IRQ setting or hardware failure.
13	One of the EiconCard image files (*.ELM) could not be found.
15	Diagnostic failure: Hardware failure.
16	Invalid Configuration: Invalid slot number.
17	Invalid Configuration: Invalid card type.
18	Card type is not supported by this version of ECTEST.
50	Insufficient user privilege. Valid only for multi-user operating systems.
51	A required EiconCard device driver resource is currently unavailable.
52	Insufficient memory on HOST to run program.
53	Improper version of one of the EiconCard image files (*.ELM).
54	Improper version of the ECTEST program.
56	Invalid bus type selected with the EiconCard configuration program.
57	An application is currently running on an EiconCard located in the specified slot. (Micro Channel EiconCards only).
58	Error after system call to the EiconCard device driver ECNB.SYS.
59	According to the driver, the computer's bus type differs from the one selected in the EiconCard configuration file.
60	An application is running on the EiconCard using the specified I/O port address.
61	An application is running on the EiconCard using the specified memory segment address.
62	An application is running on the EiconCard using the specified interrupt request (IRQ) level.
67	ECTEST.MSG file could not be found.

If more than one EiconCard is being tested by ECTEST, then the error level returned by ECTEST applies only to the most recently tested EiconCard.


Chapter 9: Command Line Utilities

ECVER: Searching for Eicon Software

Command	ECVER.EXE
Purpose	Searches your hard drive for any existing Eicon Technology software, and indicates the version number of that software.
Syntax	ECVER	[path/filename] [/S]
Parameters	path/filename	The drive, directory, and filename you want to scan. Wild cards are accepted in the filename. The default for filename is *.*.
	/S	Scan all subdirectories of the directory you specified with path.

ECVER scans the specified drive or directory for any Eicon Technology software, and displays the location and version number of that software.

Note:
ECVER only lists Version 3.0 and above of the Eicon Technology software.

Using ECVER


Chapter 9: Command Line Utilities

ECVER: Searching for Eicon Software

Using ECVER

The following examples illustrate how to use ECVER.

ECVER C:\ /S

Scans all of drive C: for existing Eicon Technology software.

ECVER F:\COMM\APPS

Searches the directory F:\COMM\APPS for existing Eicon Technology software.


Chapter 9: Command Line Utilities

IPMAP: IP Mapping Management

Command	IPMAP.EXE
Purpose	To link the circuit created with MPRCCT to the IP address of the remote router.
Syntax	IPMAP	ADD cctName IPAddr [/B]
		DELETE cctName IPAddr
		STATUS
Parameters	ADD	Maps the specified router circuit to a remote IP address.
	DELETE	Deletes the mapping information for the specified circuit. The circuit still exists, and can be later mapped to a new address using the IPMAP ADD command.
	STATUS	Displays information about the mapping used on the specified circuit.
	cctName	The name of the circuit to associate to the mapping.
	IpAddr	Specifies the remote device's IP address in the form xxx.xxx.xxx.xxx.
	/B	Enables IP protocol broadcasts. If this parameter is not used, then applications that rely on broadcasts, such as ROUTE, cannot be used over the WAN.

The third stage in activating the router (after running MPR START and MPRCCT ADD) is to use IPMAP to link the circuit you created with MPRCCT to the remote TCP/IP address. IPMAP can also display information about the mappings that have been performed.

Note:
You do not need to map a Frame Relay connection to a remote IP address.

Using IPMAP


Chapter 9: Command Line Utilities

IPMAP: IP Mapping Management

Using IPMAP

The following examples illustrate IPMAP in action.

IPMAP ADD CIRCUIT1 12.44.67.33 /B

Maps the circuit called CIRCUIT1 to the remote TCP/IP address of 12.44.67.33, and enables packets to be transmitted. The utility MPRCCT ADD creates circuits.

IPMAP DELETE CIRCUIT2 98.76.54.32

Deletes IP address mapping for the circuit called CIRCUIT2. The circuit can be mapped to a new IP address later.

IPMAP STATUS

Provides information about all mappings being performed.

IPMAP STATUS Display

When you issue an IPMAP STATUS command, a display similar to the following appears:

[C:\MPR]IPMAP STATUS

WAN Services for Windows NT IP Mapping Management Program.
IPMAP 3.02 Rev.01
Copyright (c) Eicon Technology Corporation 1995.
All Rights Reserved.

IP Address       Circuit            Broadcast
---------------------------------------------

131.28.61.1      CCT_TO_MC          ON

IPMAP STATUS Fields

IP Address  The IP address to which each specified Circuit Name has been mapped.

Circuit  The name of the circuit about which information is being displayed.

Broadcast  Indicates whether broadcasts of IP protocol are active on this circuit. When broadcasts are OFF, then applications that rely on broadcasts, such as TCP/IP's ROUTE, cannot be used over the WAN. For Broadcast to be active, the mapping must have been created using IPMAP with the /B parameter, or the Broadcast parameter must be set to "Y" in the [Mapper Entry] section of MPR.INI file.


Chapter 9: Command Line Utilities

MPR: Starting, Stopping, Statistics, and Configuration

Command	MPR.EXE
Purpose	To start and stop the router, and to display the router's global statistics and configuration
Syntax	MPR	START | STOP | STATS | CONFIG
Parameters	START	Starts the router software. If any connections have been configured in the MPR.INI file auto start (default), then these connections are automatically activated when the MPR START command is issued.
	STOP	Halts the router by disabling packet forwarding on all ports, and terminates any remaining connections on all active ports.
	STATS	Displays global router statistics, such as packet and bytes transmitted, and errors.
	CONFIG	Displays IP configuration information on the currently installed Eicon logical NDIS adapters (EiconCard ports).

Running MPR is the first step in activating the router. MPR can be used to start and stop the router program, and can also be used to display statistics and general configuration about the router's operation.

MPR START uses the settings saved in the MPR.INI file. For more information, see Chapter 11, "The MPR.INI Initialization File."

Using MPR


Chapter 9: Command Line Utilities

MPR: Starting, Stopping, Statistics, and Configuration

Using MPR

The following examples illustrate MPR in action.

MPR START

Starts the router software, and activates any router connections that have been configured in the MPR.INI file to be AUTO_START=Y (default).

Each time you create a circuit with MPRCCT, that information is saved to MPR.INI. Thus the next time you start the router, you only need to run MPR START to reactivate that previously created circuit.

MPR STOP

Halts the router, and terminates all remote connections.

MPR STATS

Displays global statistics about the router, without halting the router's operations.

MPR CONFIG

Displays IP configuration information on the currently installerouterd Eicon logical NDIS adapters (EiconCard ports).

MPR STATS Display

MPR STATS Fields

MPR CONFIG Display


MPR STATS Display

The MPR STATS command provides general statistics about the operation of the router. Here is a sample display:

[C:\MPR]MPR STATS

WAN Services for Windows NT Management Utility.
MPR 3.02 Rev.01
Copyright (c) Eicon Technology Corporation 1995.
All Rights Reserved.

router operation state.........: Running
IP Mappings available/maximum..: 13/16
Circuits available/maximum.....: 14/16
Ports maximum..................: 1
IP Filters available/maximum.....15/16

Tx Statistics                Rx Statistics
-------------                -------------

Packets...........: 16632    Packets.........: 37051
Bytes.............: 702407   Bytes...........: 19594524

Tx Errors                    Rx Errors
---------                    ---------

Packets dropped......: 0     Packets dropped....: 0
Out of resources.....: 0     Out of resources...: 0
Unknown protocol.....: 0     Unknown protocol...: 0
Route not found......: 0     Receive errors.....: 0


MPR STATS Fields

Router Operation State The current overall status of the router.

Value	Description
Running	The router is active.
Failed	An error has occurred and the router has been halted.

IP Mappings available/maximum  The number of remote IP address mappings currently available, compared to the maximum number possible with your configuration. The utility IPMAP is used to control mappings.

Circuits available/maximum  The number of Circuits currently available, compared to the maximum number possible with your configuration. The utility MPRCCT is used to add and delete circuits.

Ports maximum  The maximum number of EiconCard ports possible with your configuration. The number of ports depends on the number configured in the Registry database. This is done with the Network Control Panel applet.

IP Filters available/maximum  The total number available.

Packets  The total number of IP packets sent or received since the router software was started.

Bytes  The number of bytes sent or received since the router software was started.

Packets Dropped  The sum of the total Unknown Protocol, Out of Resources, and Route Not Found errors that have occurred during transmission.

Unknown protocol  The number of times that an unknown packet or protocol type was sent or received. This error occurs when a remote router sends a packet in a protocol not supported by the Eicon NDIS router.

Out of resources  The number of times that the router ran out of system resources. This error occurs when there is not enough buffer space to contain incoming or outgoing packets while they are being processed. This type of error can occur on slow data lines.

Route not found  The number of times that an outgoing packet has not found a forwarding route. This error occurs when the IPMAP command has been used to delete mapping information on a circuit that is currently in use, and the protocol stack tries to send a packet to that deleted mapping.

Receive Error  The number of times that the EiconCard received a packet with an error code.


MPR CONFIG Display

The MPR CONFIG command provides general IP configuration of the installed Eicon NDIS logical adapters (EiconCard ports). Here is a sample display:

[C:\MPR]MPR CONFIG

WAN Services for Windows NT Management Utility.
MPR 3.02 Rev.01
Copyright (c) Eicon Technology Corporation 1995.
All Rights Reserved.

Eicon IP configuration

Logical Adapter  Port #       IP Address         Subnet Mask
[ 9]Ecndis         1         200.200.101.1       255.255.255.0
[10]Ecndis         2         200.200.102.1       255.255.255.0


Chapter 9: Command Line Utilities

MPRCCT: Circuit Management

Command	MPRCCT.EXE
Purpose	To create a circuit, which later can be mapped to a remote IP address using IPMAP. This command also provides status and statistics on the circuit, and can delete a circuit as well. Whenever a circuit is created using MPRCCT, that circuit's settings is added to the MPR.INI initialization file, and is automatically set to AUTO_START mode.
Syntax	MPRCCT	ADD X25 cctName /V pvcnum [/P port]  [/B primaryname] [/K]
		ADD X25 cctName [/P port]  [/B primaryname] [/K] [/T timer] [/R retrynum] [/E retrydelay] [/A remDTE] [/L localDTE] [/C  I | O | T]  [/IF facilities] [/OF facilities] [/Userdata]
		ADD FRBS cctName [/X] [/S] DLCI dnum [/K] [/P port] [/B primaryname]
		ADD PPP cctName  [/K] [/P port] [/B primaryname]
		DELETE cctName
		STATUS [cctName]
		STATS
		START cctName
		STOP cctName
		LIST [cctName]
Parameters	ADD	Creates a new circuit, which then can be mapped to a remote IP address using IPMAP. A circuit must be created before it can be mapped. (Frame Relay circuits do not need to be mapped.) Using this command adds the circuit information to the MPR.INI file.
	DELETE	Deletes an existing circuit, and all mappings associated with that circuit. Using this command also deletes the circuit entry from the MPR.INI initialization file, but leaves the mapping entry in that file intact.
	STATUS	Displays information about the circuit active on the router.
	STATS	Displays general traffic information about the data passing through the circuits currently active in the router.
	STOP cctName	Stop an existing circuit. Using this command does not delete the circuit entry from the MPR.INI initialization file.
	START cctName	Start a circuit already defined in the MPR.INI initialization file.
	LIST cctName	Lists the connection name, WAN protocol, port and parameters defined for cctName in the configuration file. If cctName is omitted, these parameters are displayed for all connections.
	X25	Used with the MPRCCT ADD command to create a new X.25 circuit.
	FRBS	Used with the MPRCCT ADD command to create a new Frame Relay circuit.
	PPP	Used with the MPRCCT ADD command to create a new PPP circuit.
	cctName	A unique name that identifies the circuit. The circuit name can be 1 to 15 ASCII characters long, and is case insensitive. The name is only important on the WAN Services PC itself.
	/V pvcNum	The number of the PVC you want to use.
	/P port	Specifies the EiconCard port to use for the connection. If no port is specified, then port #1 is used by default.
	/B primary name	Specifies that the circuit is a backup circuit. Enter a name of the circuit that you are providing a backup for.
	/K	Enables software-based compression. Note that compression only works between EiconCards. Data compression can considerably reduce the amount of information sent through the circuit, thus taking less time to send the same information. The compression ratio varies with the type of data being compressed.
	/T timer	Inactivity timer, in seconds. This timer has an effect on a two-way circuit only: the circuit is terminated when there is no data traffic for the specified number of seconds. The range is 0 to 86400 seconds, and the default is 0.
	/R  retryNumber	The number of times the connection is attempted when the previous call request has been issued and refused for some reason. The range is 0 to 100, and the default is 0. Setting this to 100 sets the retries to infinite.
	/E  retryDelay	Sets up the retry delay between each connection attempt. The range is 5 to 65535 seconds, and the default is 5.
	/A remDTE	Specifies the remote DTE. This is mandatory when using a X.25 Switched Virtual Circuit (SVC) subnetwork.
	/L localDTE	Specifies the local DTE. This is mandatory for two-way connections on a X.25 Switched Virtual Circuit (SVC) subnetwork.
	/C I | O | T	Sets the connection type: "I" for Incoming "O" for Outgoing "T" for Two-way on a X.25 Switched Virtual Circuit (SVC) subnetwork.
	/IF facilities	X.25 Listening Facilities: input facility settings for incoming and two-way circuits. For example:  /F 42,8,8 sets packet size to 256 instead of 128 characters.  These settings must be enclosed in single quotes  (‘ ’)from the MPRCCT command line. From the WAN Services Configuration program, enclose these settings in double quotes (" "). For more information, see Appendix C, "User Facilities and DTE Address Structure."
	/OF facilities	X.25 Calling Facilities: output facility settings (two-way and outgoing circuits only).  These settings must be enclosed in single quotes (‘ ’)from the MPRCCT command line. From the WAN Services Configuration program, enclose these settings in double quotes (" "). For more information, see Appendix C, "User Facilities and DTE Address Structure."
	/U userData	X.25 User Data (value appended). User Data can be used to request services specific to the remote router you are calling, such as a password, or to indicate your Protocol ID code. The call user data field can contain up to 128 characters. MPRCCT follows RFC-1356 (RFC-877), which means that the first byte of the User Data for IP is set to 0xCC, as is the standard. The User Data entered by the user is appended to the 0xCC byte. For example: /U ‘48 45 4C 4C 4F’ sets user data equal to the text HELLO. These settings must be enclosed in single quotes (‘ ’)from the MPRCCT command line. From the WAN Services Configuration program, enclose these settings in double quotes (" ").
	/X	Enable XID. Including this parameter will enable the negotiation of Exchange Station Identification U-Frames between the local and remote router. XIDs are a type of UI U-frame (Unnumbered Information U-Frame) that are used to negotiate exchange parameters between link stations (Frame Relay connections only). For the V3R3 release only packet size will be negotiated.  NOTE: For XID negotiation to be possible, XID negotiation must also be enabled, for this connection, on the remote Router.
	/S	Enables segmentation of large packet sizes for efficient transmission between the local and remote routers. (Frame Relay connections only) If the Remote router is an Eicon Technology router, selecting the segmentation check box will enable the negotiation of segmentation. The result of the negotiation will indicate whether or not segmentation will be supported. If the Remote router is not an Eicon Technology router, selecting the segmentation check box will enable segmentation but negotiation will not take place.  NOTE: For segmentation to be possible, segmentation must also be enabled, for this connection, on the remote Router.
	/DLCI dNum	Number of the DLCI you want to use for this circuit. Each circuit you use to connect to a different remote router needs a different DLCI. The DLCI is a circuit assigned to a remote address at the time you purchase your subscription (Frame Relay connections only).

The second stage in activating the router (after running MPR START) is to use MPRCCT to create circuits. The circuit is then linked to the remote IP address using the IPMAP utility. MPRCCT can also display information about the circuits that have been created.

Using MPRCCT


Chapter 9: Command Line Utilities

MPRCCT: Circuit Management

Using MPRCCT

The following examples illustrate MPRCCT in action.

MPRCCT ADD X25 CIRCUIT1 /A 12345678 /L 987654321 /P 2

Creates a circuit called CIRCUIT1, to be used over an X.25 network (where the local DTE address is 987654321 and the remote router's address is 12345678), connecting through port 2 on the EiconCard.

MPRCCT ADD FRBS CIRCUIT2 /DLCI 321 /K

Creates a circuit called CIRCUIT2, to be used over a Frame Relay connection using DLCI number 321, and with software-based compression enabled.

MPRCCT DELETE CIRCUIT1

Deletes the circuit called CIRCUIT1, and all IP mappings associated with it.

MPRCCT STATUS CIRCUIT2

Provides detailed information about the circuit called CIRCUIT2.

MPRCCT STATUS

Provides basic information about all circuits.

MPRCCT STATS

Shows general traffic statistics on all circuits.

MPRCCT STATUS Display

MPRCCT STATUS Display on an X.25 Circuit

MPRCCT STATUS Display on a Frame Relay Circuit or Point-to-Point Protocol

MPRCCT STATS Display

MPRCCT LIST Display


Chapter 9: Command Line Utilities

MPRCCT: Circuit Management

Using MPRCCT

MPRCCT STATUS Display

When you issue an MPRCCT STATUS command, a display similar to the following appears:

[C:\MPR]MPRCCT STATUS

WAN Services for Windows NT Circuit Management Program.
MPRCCT 3.02 Rev.01
Copyright (c) Eicon Technology Corporation 1995.
All Rights Reserved.

Name        Subnet       State      Port    Parameters
------------------------------------------------------

ROUTER1     X.25 svc     Idle          1    rdte: 05

MPRCCT STATUS Fields

Name  A list of all active circuits.

Subnet  The WAN protocol currently being used by the circuit.

Value	Description
X.25 SVC	X.25 packet switched data network protocol, on a Switched Virtual Circuit.
X.25 PVC	Permanent Virtual Circuit Number.
Frame Relay	Frame Relay protocol.
PPP	Point-to-Point Protocol.
State  The current state of each listed circuit.

Value	Description
Connected	The circuit is currently connected to a remote router.
Disconnected	The circuit failed to connect, or has been disconnected.
Idle	The circuit has not been connected since the router was started.
Not Bound	A problem occurred when the connection was established with Connection Manager.
Terminated	The port was disconnected. Stop the router and restart the EiconCard. Then restart the router and reload all connections.
Unknown	The port is in transitional state: "Connecting" or "Disconnecting."

Port  The EiconCard port assigned to each circuit.

Parameters  The information in this field depends on the protocol in use, and its status.

SubNet	Possible Information Displayed
X.25 SVC	Cause and diagnostic codes, and DTE address. The information displayed depends on the state of the circuit.
X.25 PVC	Cause and diagnostic codes, and DTE address. The information displayed depends on the state of the circuit.
Frame Relay	The DLCI being used for this circuit.
PPP	Whether or not data compression is active for this circuit.


Chapter 9: Command Line Utilities

MPRCCT: Circuit Management

Using MPRCCT

MPRCCT STATUS Display on an X.25 Circuit

When you issue an MPRCCT STATUS command on an X.25 circuit, a display similar to the following appears:

[C:\MPR]MPRCCT STATUS XCIRCUIT

WAN Services for Windows NT Circuit Management Program.
MPRCCT 3.02 Rev.01
Copyright (c) Eicon Technology Corporation 1995.
All Rights Reserved.

Name: XCIRCUIT

Circuit Parameters
------------------

Status.............: Connected    Retry number.......: 0
Compression........: On           Retry delay........: 5
Port...............: 1            Timeout............: 60
Compression Ratio..: 2.1:1
Code...............: 091ch    Only appears if the Status is Not Bound.

X.25 subnetwork parameters
--------------------------

X25 type.........: Switched
Connection type..: Twoway
Remote DTE.......: 1234
Local DTE........: 9876
Calling facil....: (none)
Listening facil..: (none)
User data........: (none)
Cause/Diag.......: 0Dh/00h    Only appears if the circuit failed to connect.

MPRCCT STATUS Fields for X.25

Name  The name of the circuit about which information is being displayed.

Status  The current state of each listed circuit.

Value	Description
Connected	The circuit is currently connected to a remote router.
Disconnected	The circuit failed to connect, or has been disconnected.
Idle	The circuit has not been connected since the router was started.
Not Bound	A problem occurred when the connection was established with Connection Manager.
Terminated	The port was disconnected. Stop the router and restart the EiconCard. Then restart the router and reload all connections.
Unknown	The port is in transitional state: "Connecting" or "Disconnecting."

Compression  Indicates whether software-based data compression is On or Off. Compression is activated by using the "/K" parameter on the MPRCCT command.

Retry number  The number of times the router attempts to make a connection to the remote address before abandoning the effort.

Retry delay  The number of seconds between attempts to make a connection to the remote address.

Timeout  If there has been no data to or from the remote address for this amount of time, then the connection is broken.

Port  The EiconCard port being used by this circuit.

Compression Ratio  This field only appears if Compression is On. The degree of data compression currently being achieved on this connection. A 4:1 compression ratio means that each 4K of data is being compressed into 1K before being transmitted. The compression ratio varies with the type of data being compressed.

Code  If the Status field displays "Not Bound," then the Code field appears. Code is the error code of the problem which caused the connection to abort. These codes may indicate a configuration problem, and are meaningful to advanced users only. Here is a list of the possible codes that relate to circuit errors, and their definitions:

Code	Circuit Error Description
0304h	Port binding error.
0305h	Port unbinding error.
0308h	Subnetwork not loaded.
0309h	Connection manager session not available.

Here is a list of Connection Manager error codes and their definitions:

Code	Connection Manager Error Description
0901h	No UCB for dst_ref in BIND.MSG.
0902h	Both the NM and DT sessions must be established.
0903h	Less than minimum size of BIND data.
0904h	Call directory entry selector is not zero.
0905h	Invalid connection specification.
0906h	Reserved bits in connection specification must be zero.
0907h	Inactivity timer must be zero if PERMANENT.
0908h	Reserved bits in FLAGS must be zero.
0909h	PERMANENT cannot be TWO-WAY.
090ah	Must be DYNAMIC to negotiate DYNAMIC.
090bh	Inactivity TIMER too big.
090ch	Calling length and listening length both zero.
090dh	Data less than calling length and listening length.
090eh	Invalid broadcast selection bit used.
090fh	No resources to allocate a BIND entry.
0910h	Subnetwork task not loaded.
0911h	Subnetwork must be PERMANENT.
0912h	Subnetwork does not support compression.
0913h	Undefined subnetwork type.
0914h	Less than minimum calling/listening length.
0915h	Subnetwork must be outgoing for calling parameters.
0916h	Calling/listening subnetwork types do not match.
0917h	Subnetwork must be incoming/two-way.
0918h	Calling/listening subnetwork lana numbers do not match.
0919h	Calling/listening subnetwork Virtual Circuits do not match.
091ah	Subnetwork does not support calling parameters.
091bh	Lana number in bind is not valid.
091ch	No memory for compression.
091dh	No compression session is available.
091eh	X.25 port is not activated.
091fh	Lana number in bind has already been used.
0920h	Qualifies Listen for Incoming Call only.
0926h	Listening parameters not allowed.

X25 Type  Shows the type of X.25 circuit currently being used.

Value	Description
Switched	Switched Virtual Circuit (SVC).
Permanent	Permanent Virtual Circuit (PVC).

Connection Type  Indicates whether the X.25 connection is being made through an incoming only, out-going, or two-way virtual X.25 circuit.

Value	Description
INCOMING	Incoming virtual X.25 SVC circuit.
TWOWAY	Two-way X.25 SVC virtual circuit.
OUTGOING	For PPP, Frame Relay, X.25 SVC, and X.25 PVC.

Remote DTE  The X.25 DTE address of the remote router.

Local DTE  The X.25 DTE address of this router.

Calling Facil  Specified by the local router, Calling Facilities are optional network services that provide features such as reverse charging, access to a Closed User Group, or specification of a Network User Identification. The Calling Facility field can contain up to 109 bytes.

Listening Facil  Specified by the remote router, Listening Facilities are optional network services that provide features such as reverse charging, access to a Closed User Group, or specification of a Network User Identification. The Listening Facility field can contain up to 109 bytes.

User Data  User Data can be used to request services specific to the remote router you are calling, such as a password, or to indicate your Protocol ID code. The call user data field can contain up to 128 bytes. MPRCCT follows RFC-1356 (RFC-877), which means that the first byte of the User Data for IP is set to 0xCC, as is the standard. The User Data entered by the user is appended to the 0xCC string.

Cause/Diag  This field only appears if the circuit is Disconnected. The Cause/Diag field displays X.25 cause and diagnostic codes. These codes can help you in tracing the source of problems with an X.25 connection. For an explanation of each cause and diagnostic code, see Appendix C "User Facilities and DTE Address Structure."


Chapter 9: Command Line Utilities

MPRCCT: Circuit Management

Using MPRCCT

MPRCCT STATUS Display on a Frame Relay Circuit or Point-to-Point Protocol

When you issue an MPR STATUS command on a Frame Relay or Point-to-Point circuit, a display similar to the following appears:

[C:\MPR]MPRCCT STATUS CIRCUIT1

WAN Services for Windows NT Circuit Management Program.
MPRCCT 3.02 Rev.01
Copyright (c) Eicon Technology Corporation 1995.
All rights reserved.

Name: circuit1

Circuit Parameters
------------------

Status..............: Connected
Compression.........: On
Port................: 1
Compression Ratio...: 4.7:1
Code...............: 091ch    Only appears if the Status is Not Bound.

Frame Relay subnetwork parameters
---------------------------------
DLCI number......: 16

MPRCCT STATUS Fields for Frame Relay or Point-to-Point Protocol

Name  The name of the circuit about which information is being displayed.

Status  The current state of each listed circuit.

Value	Description
Connected	The circuit is currently connected to a remote router.
Terminated	The circuit failed to connect, or has been disconnected.
Idle	The circuit has not been connected since the router was started.
Not Bound	A problem occurred when the connection was established with Connection Manager.
Unknown	The port is in transitional state: "Connecting" or Disconnecting."

Compression  Indicates whether software-based data compression is On or Off. Compression is activated by using the "/K" parameter on the MPRCCT command line. For compression to work, there must be an Eicon Technology router on both ends of the connection.

Port  The EiconCard port being used by this circuit.

Compression Ratio  This field only appears if Compression is On. The degree of data compression currently being achieved on this connection. A 4:1 compression ratio means that each 4K of data is being compressed into 1K before being transmitted, thus taking only 1/4 of the time to transmit as the original uncompressed data. The compression ratio varies with the type of data being compressed.

Code  If the Status field displays "Not Bound," then the Code field appears. Code is the error code of the problem which caused the connection to abort. These codes may indicate a configuration problem, and are meaningful to advanced users only. Here is a list of the possible codes that relate to circuit errors, and their definitions:

Code	Circuit Error Description
0304h	Port binding error.
0305h	Port unbinding error.
0308h	Subnetwork not loaded.
0309h	Connection manager session not available.

DLCI  The Data Link Connection ID. This identifies a particular logical link in the Frame Relay network.


Chapter 9: Command Line Utilities

MPRCCT: Circuit Management

Using MPRCCT

MPRCCT STATS Display

The MPRCCT STATS command provides general statistics about the operation of the router's circuits. Here is a sample display:

[C:\MPR]MPRCCT STATS

WAN Services for Windows NT Circuit Management Program.
MPRCCT 3.02 Rev.01
Copyright (c) Eicon Technology Corporation 1995.
All Rights Reserved.

Circuit name   tx packets  tx bytes  rx packets  rx bytes
---------------------------------------------------------

PCIRCUIT       1216091     470229977 1549370    384585908

MPRCCT STATS Fields

Circuit Name  The name of the circuit(s) about which information is being displayed.

tx packets  The total number of IP packets sent through the specified circuit since it was started.

tx bytes  The total number of bytes sent through the specified circuit since that circuit was started.

rx packets  The total number of IP packets received from the specified circuit since that circuit was started.

rx bytes  The total number of bytes received from the specified circuit since that circuit was started.


Chapter 9: Command Line Utilities

MPRCCT: Circuit Management

Using MPRCCT

MPRCCT LIST Display

MPRCCT LIST

WAN Services for Windows NT Circuit Management Program.
MPRCCT 3.02 Rev.01
Copyright (c) Eicon Technology Corporation 1995.  All Rights Reserved.

Name                Subnet         State         Port    Parameters

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

TEST01              X.25 svc       Active        1       rdte: 123
REMOTE_LAB          X.25 svc       Active        1       rdte: 100400809
OFFICE_XYZ          X.25 svc       Active        1       rdte: 100400806

MPRCCT LIST REMOTE_LAB

WAN Services for Windows NT Circuit Management Program.
MPRCCT 3.02 Rev.01
Copyright (c) Eicon Technology Corporation 1995.  All Rights Reserved.

Name: REMOTE_LAB

Circuit Parameters
------------------
Status.............: Active         Retry number.......: 0
Compression........: Off            Retry delay........: 5
Port...............: 1              Timeout............: 60
Usage..............: Primary

X.25 subnetwork parameters
--------------------------
X25 type.........: Switched         Remote DTE.......: 100400809
Connection type..: Twoway           Local DTE........: 100400803
Calling facil....: (none)
Listening facil..: (none)
User data........: (none)

MPRCCT LIST Fields

State The current state of this connection. Active indicates that the circuit is loaded. Inactive means it is not loaded.

All other MPRCT LIST fields are described under the headings "MPRCCT Status Fields" and "MPRCCT STATUS Fields for protocol," where protocol is one of X.25, Frame Relay, and PPP. Look under the heading, earlier in this chapter, corresponding to the subnetwork (X.25, Frame Relay, or PPP) of the connection you named in the MPRCCT LIST command.


Chapter 9: Command Line Utilities

MPRFLT: Filtering of IP Packets

Command	MPRFLT.EXE
Purpose	To forward or block out certain types of IP datagram packets being transmitted or received by the server.
Prerequisites	The router must be operating to be able to use MPRFLT successfully.
Syntax	MPRFLT	ADD cctname DROP | FORWARD   [IN | OUT] [/A filterID]  [[/P low high] [TCP | UDP]]    [/S addr mask] [/D addr mask]
		DELETE filterID
		STATUS [cctname] [IN | OUT]
		STATS [cctname]
		ACTIVATE filterID
		DEACTIVATE filterID
Parameters	ADD	Adds an IP filter.
	DELETE	Deletes an IP filter.
	STATUS	Displays information about the IP filters currently configured on the router.
	STATS	Displays statistical information on the filtered data flowing through the port.
	ACTIVATE	Activate the filter ID specified.
	DEACTIVATE	Deactivate the filter ID specified.
	cctname	Specifies the circuit name to which the filter applies.
	DROP | FORWARD	Specifies the action to be performed on the packet by this filter.
	IN | OUT	Specifies the direction to which the filter applies. IN indicates that the DROP or FORWARD action will apply to packets received by the server; OUT refers to all packets transmitted by the server. If this options is not used, then the default is taken to be both directions.
	/A filterID	The filter ID after which the filter will be added. If this parameter is not specified, then all filters are added at the end of the filter chain.
	/P low high	The destination port range, defined in the TCP/UDP header, that this filter acts upon. Values range between 1 and 65 535. For example, /P 5 15 would match ports 5 to 15 inclusively. If this option is not specified, the filter applies to all destination IP ports. If you want to filter only one port, the low parameter should equal the high parameter value.
	TCP | UDP	Valid only with the /P option. The protocol type to be filtered: TCP or UDP. If an option is not specified, the value is taken to be both protocols.
	/S addr mask	The source IP address and mask. For example, /S 131.28.2.3 255.255.255.0. If this option is not specified, the filter applies to all source addresses.
	/D addr mask	The destination IP address and mask. If not specified, the filter matches all destination addresses.
	filterID	Specifies the assigned filter identification number. The filter ID is assigned by the router.

The IP filter blocks out data as specified by the chain of filter commands entered by the user. These commands can be tailored to block out or forward packets destined for a certain IP address on the internetwork, or a destination IP port.

The Filtering Process

Using MPRFLT STATUS

Using MPRFLT STATS


Chapter 9: Command Line Utilities

MPRFLT: Filtering of IP Packets

The Filtering Process

IP packets are filtered based on the order of the filter commands they encounter in the filtering chain. The filtering chain is a linear list of pre-defined filters for a specific router connection. This means that the first filter is checked for a match first, then the second, and so on. When a packet’s specification (port values and/or addresses) is found to match a filter, the action defined for this filter is applied to the packet. The first filter to match the packet is applied regardless of the other filters that follow in the list.

Important:
If no match is found in the filter list, the packet is forwarded by default.

Tips:

•	The more filters you put on a circuit, the more processing has to be done for every packed handled and performance also drops accordingly

•	Plan the filtering process well to make sure that you do not have redundant filters in the chains

•	Make use of the IN and/or OUT keywords to make sure that you process packets only in the direction that they are meant to be processed

•	Filters only apply on directed packets, not broadcasted packets


Chapter 9: Command Line Utilities

MPRFLT: Filtering of IP Packets

Using MPRFLT STATUS

The MPRFLT STATUS command provides status information about the IP filters on the server. The following is a sample display:

MPRFLT STATUS

WAN Services for Windows NT IP Filter Management Program
MPRFLT 3.02 Rev.01
Copyright (c) Eicon Technology Corporation 1995.  All Rights Reserved.

Id    Circuit        Dir    Action  State    Port        S-addr   D-addr
-------------------------------------------------------------------------
1     TEST01         In-Out Drop    Active   Set         All      Set
2     TEST01         In-Out Drop    Active   Set         All      All
3     TEST01         In-Out Forward Active   All         All      All

MPRFLT STATUS Fields

Id  The identification number of the filter command in the chain.

Circuit  The circuit name to which this filter applies.

Dir  The direction of the packets that the filter will act upon: Incoming, outgoing, or both.

Action  Specifies whether the filter will drop or forward the matching packets.

Port The destination port range that this filter acts on. ‘Set’ means that there is a specified range (done at configuration time) to which the filter applies. ‘All’ means that the filter applies to all destination ports. To determine exactly which ports have been specified issue the MPRFLT STATUS cname on the particular circuit. See the display below.

S-addr  The IP address from which the packets originate. ‘Set’ means that there is a specified range (done at configuration time) to which the filter applies. ‘All’ means that the filter applies to all destination ports.

D-addr  The IP address to which the packets are destined. ‘Set’ means that there is a specified range (done at configuration time) to which the filter applies. ‘All’ means that the filter applies to all destination ports.

To display detailed filtering information on any given circuit issue the following type of command:

MPRFLT STATUS TEST01

WAN Services for Windows NT IP Filter Management Program
MPRFLT 3.02 Rev.01
Copyright (c) Eicon Technology Corporation 1995.  All Rights Reserved.

Filter globals         Matching parameters
--------------------------------------------------------------------------
Filter id : 1
Action    : Drop       Port type/range     : All / 23-23
Direction : In-Out     Source address/mask : All
State     : Active     Dest. address/mask  : 131.28.61.1 / 255.255.255.255
--------------------------------------------------------------------------
Filter id : 2
Action    : Drop       Port type/range     : All / 20-21
Direction : In-Out     Source address/mask : All
State     : Active     Dest. address/mask  : All
--------------------------------------------------------------------------
Filter id : 3
Action    : Forward    Port type/range     : All / All
Direction : In-Out     Source address/mask : All
State     : Active     Dest. address/mask  : ALL
-----------------------------------------------------------------


Chapter 9: Command Line Utilities

MPRFLT: Filtering of IP Packets

Using MPRFLT STATS

The MPRFLT STATS command provides statistics information about the IP filters on the server. The following is a sample display:

MPRFLT STATS

WAN Services for Windows NT IP Filter Management Program
MPRFLT 3.02 Rev.01
Copyright (c) Eicon Technology Corporation 1995.  All Rights Reserved.

Dropped Packets Out....: 14
Dropped Packets In.....: 3
Forwarded Packets Out..: 1092
Forwarded Packets In...: 1416

Id    Circuit        Dir    Action  State    In         Out
--------------------------------------------------------------------------

1     TEST01         In-Out Drop    Active   0          5
2     TEST01         In-Out Drop    Active   3          9
3     TEST01         In-Out Forward Active   1391       1080

MPRFLT STATS Fields

Dropped Packets Out  The number of dropped outbound packets.

Dropped Packets In  The number of dropped inbound packets.

Forwarded Packets Out  The number of forwarded outbound packets.

Forwarded Packets In  The number of forwarded inbound packets.

Id  The identification number of the filter command in the chain.

Circuit  The circuit name to which this filter applies.

Dir  The direction of the packets that the filter will act upon: Incoming, outgoing, or both.

Action  Specifies whether the filter will drop or forward the matching packets.

In  Specifies the number of inbound packets in which the specified action has taken place.

Out  Specifies the number of outbound packets in which the specified action has taken place.


Chapter 9: Command Line Utilities

MPRTRC: Trace Management

Command	MPRTRC.EXE
Purpose	To view and reset the router's internal traces. Before you can use MPRTRC you must activate the trace option in the Eicon router Driver. Use the NCPA to do this. See "Configuring the IP Routing Service," for more information.
Syntax	MPRTRC	DUMP NDIS | NCB
		RESET NDIS | NCB
Parameters	DUMP	Dumps the contents of the router's trace buffer. The size of the trace buffer is defined in the NCPA, Eicon NDS router configuration.
	NDIS | NCB	Specifies which trace to act upon. NDIS: upper level (trace between IP and NDIS router) Network Control Block: lower level (trace between NDIS router and EiconCard)
	RESET	Clears the trace buffer.
When seeking the source of a communications problem, it can be invaluable to have a trace of the information sent and received by the router. MPRTRC traces information flowing through the router discarding irrelevant data. The trace can be viewed on screen, or saved to a file.

The information provided by MPRTRC is designed for use by Eicon Technology distributors and support personnel.

Using MPRTRC


Chapter 9: Command Line Utilities

MPRTRC: Trace Management

Using MPRTRC

The following examples illustrate MPRTRC in action.

MPRTRC DUMP NDIS > TRACE.TXT

Copies the contents of the NDIS trace buffer to a text file called TRACE.TXT.

MPRTRC RESET NCB

Clears the contents of the NCB trace buffer, so you can get a fresh reading of the information flowing through the router.


Chapter 10: Using ECMODULE

The EiconCard command ECMODULE provides detailed information on the protocols streaming through WAN Services. This chapter describes what ECMODULE does and contains sample ECMODULE STATS and ECMODULE STATUS display screens, and explains the different fields on those screens. Instructions on using the ECMODULE TRACE utility are also provided. These commands offer a local alternative to the Eicon SNMP Console.

Introduction

The ECMODULE Command

ECMODULE Display Information

DIALER Status

Frame Relay Status

Frame Relay Statistics

HDLC Status

HDLC Statistics

PPP Status

PPP Statistics

SDLC Status

SDLC Statistics

Transport ISO and BULL TGX Status

Transport ISO and BULL TGX Statistics

X.25 Status

X.25 Statistics

Analyzing Data: ECMODULETRACE

The Trace Buffer

The Trace Filter

Sample ECMODULETRACE Commands


Chapter 10: Using ECMODULE

Introduction

ECMODULE is used to examine the protocol information streaming through the Eicon Technology WAN Services PC, and to provide statistical information about the various connections.

ECMODULE has four main parts:

•	ECMODULE STATUS: provides global information on the status of all applications running on the WAN Services PC. Information about connection status for all established links on each EiconCard is presented.

Application     Protocol        Connection                             Port
Name            Name            ID  State
------------------------------------------------------------------------
Card number : 1
ECNDIS          CONMGR          2   CONNECTED       @11:22:47 Aug 27   1
ECNDIS          CONMGR          3   CONNECTED       @11:22:47 Aug 27   1

•	ECMODULE STATUS protocol: this derivative of ECMODULE STATUS provides detailed information on the status of the specified protocol that the Eicon Technology WAN Services PC is using. Information about the protocol configuration, the WAN Services status and its connections is presented.

X.25 Loadable Module Status

Port number: 1      Port name: MONTREAL01A
                              Default  Maximum
Window size.................: 2        7
Packet size (bytes).........: 256      256

Packet format...............: Extended Maximum retry count N3......: 3
Restart timer T20 (sec).....: 60       Reset timer T22 (sec).......: 60
Call timer T21 (sec)........: 60       Clear timer T23 (sec).......: 60
Idle timer (sec)............: 0        Acknowledgment timer (msec): 10
Two-way VCs configured......: 4        Permanent VCs configured....: 0
In-coming VCs configured....: 0        Out-going VCs configured....: 0

Trace.......................: Off      Trace buffer size (bytes)...: 0
Trace filter (hex)..........: 00       Trace entry size (bytes)....: 0

Link activated at...........: @13:04:03 Feb 12
Last restart................: @13:04:11 Feb 12

VC Local Address  Remote Address  Type     Status
-----------------------------------------------------------------------
1  31312222222222 31311111111111  2-Way    Circuit Ready   @13:37:01 Feb 12
2  31313333333333 31319999999999  2-Way    Circuit Ready   @15:00:01 Feb 12

•	ECMODULE STATS protocol: provides statistical information about the protocol. Statistics on data transmission are generated from the traffic streaming through the WAN Services PC and can be useful in determining the performance of the transport medium.

X.25 Loadable Module Statistics
Port number: 1       Port name:

                    Sent      Received                     Sent      Received
Call      request..: 17563     0       Data Packets......: 223      246
          confirm..: 0         3       Data Segments.....: 223      311
Restart   request..: 1         0       Characters........: 4019    8596
          confirm..: 0      1       Receiver ready....: 146      126
Register  request..: 0      0       Receiver not ready: 0        0
          confirm..: 0      0       Diagnostic packets: 0        0
Clear     request..: 0      17563   Unknown packets...: 0        0
          confirm..: 2      0       Rejects...........: 0        0
Reset     request..: 0      0
          confirm..: 0      0
Interrupt request..: 0      0
          confirm..: 0      0

•	ECMODULE TRACE protocol: lets you capture and examine the low-level communications data streaming through the WAN Services PC. The trace function can be an essential tool for the data communications expert.

X.25 Loadable Module Trace
Port number: 01                      Port name:

X.25 Trace. Size = 8192  Length = 512   Block = 14    Mask = FF
BLK   DAY-HH:MM:SS:MSEC
2     000-16:36:00.365 TX CALL REQ                     0F 0B   Data =18
      52 15 10 00 00 00 C3 01 00 00 F3 F2 F0 F4 40 40  R.............@@
      40 40                                            @@
3     000-16:36:00.525 RX CLEAR IND                   0F 13    Data = 2
      00 EC                                            ..
4      000-16:36:00.663 TX CLEAR CNF                           0F 17      Data =  0
5     000-16:36:01.563 TX CALL REQ                         10 0B    Data = 20
      A2 15 10 10 10 10 10 00 C3 01 00 00 F3 F2 F0 F5  ................
      40 40 40 40                                      @@@@
6     000-16:36:01.615 RX CLEAR IND                    10 13    Data =  2
      00 EC                                            ..
7     000-16:36:01.763 TX CLEAR CNF                    10 17    Data =   0
8     000-16:36:03.463 TX CALL REQ                     10 0B    Data = 19
      82 15 10 10 10 10 00 C3 01 00 00 F3 F2 F0 F6 40  ...............@
      40 40 40                                         @@@
9     000-16:36:03.465 TX CALL REQ                     0F 0B    Data = 9
      72 15 10 01 00 10 00 C3 01 00 00 F3 F2 F0 F2 40  r..............@
      40 40 40                                         @@@
10    000-16:36:03.605 RX CLEAR IND                    10 13    Data =  2
      00 EC                                            ..
11    000-16:36:03.680 TX CLEAR CNF                    10 17    Data =   0
12    000-16:36:03.683 RX CLEAR IND                    0F 13    Data =  2
      00 EC                                            ..
13    000-16:36:03.863 TX CLEAR CNF                    0F 17    Data =   0
14    000-16:36:20.363 TX CALL REQ                     10 0B    Data = 19
      72 15 10 10 10 10 00 C3 01 00 00 F3 F2 F0 F1 40  r..............@
      40 40 40                                         @@@
15    000-16:36:20.425 RX CLEAR IND                    10 13    Data =  2
      00 EC                                            ..
16    000-16:36:20.567 TX CLEAR CNF                    10 17    Data =  0
       00 EC                                           ..
Command Completed Successfully.


Chapter 10: Using ECMODULE

The ECMODULE Command

Command	ECMODULE.EXE
Purpose	You can use ECMODULE to monitor the traffic on the WAN Services PC, and provide a wide range of protocol statistics and other protocol information on your connections.
Syntax	ECMODULE	STATUS	[Option] [/?]
		STATS	Option [/Reset] [/?]
		TRACE	Option [/Filter f] [/Reset][/Block b]  [/Size s] [/Truncate n] [/EBcdic] [/Outfile f] [/?]
	Where Option is any of the following:
	X25	[/Port p | portname][/Connection c]
	SDLC	[/Port p | portname] [/Connection n]
	HDLC	[/Port p | portname]
	FRELAY	[/Port p | portname] [/Connection n]
	PPP	[/Port p | portname] [/NCP p]
	XPORTISO	[Eiconcard n]
	XPORTTGX	[Eiconcard n]
	Option for STATUS only:
	DIALER	[/Port p | portname]
	Option for TRACE only:
	Q931	[Eiconcard n] [Connection n]
	LAPD	[Eiconcard n] [Connection n]
Parameters	STATUS	Displays the status of all applications running on the WAN Services PC. Connections on all active ports, on all EiconCards are shown.
	STATS	Allows display of global or detail statistics about a specified protocol.
	TRACE	Displays the communications data that is streaming through the WAN Services PC. The trace can filter out unimportant information.
	Option	Displays the status of the specified protocol and its connections. STATUS provides both general and detailed information.
	/Reset	Clears the trace buffer or sets the statistics counters to zero.
	/Filter f	Allows you to focus the trace and filter out unwanted information. See the "The Trace Filter" section at the end of this chapter for filter definitions.
	/Block b	The block number in the trace at which the display will begin.
	/Size s	Size of the trace buffer in bytes. The default is 2048 bytes. If an odd value is specified, the trace size is set to the next lower even value. For example, /S 1025 will set the trace size to 1024. Entering a value of 0 stops any active trace. if s is less than 1024, the trace size value is set to 1024.
	/Truncate n	The block size of the protocol elements to be traced, where n is the size of the block in bytes. If the data exceeds this size, then the remainder of it is ignored. Note that this size also includes the 3-byte protocol header. If n is less than 16, the truncation size value is set to 16.
	/Ebcdic	Displays the information in IBM EBCDIC.
	/Outfile f	Replace f with the name of the file to send the output of this command to.
	/Port p |portname	EiconCard port or portname about which to display status.
	/Connection c	Specifies a circuit, or connection, at the protocol level, where c is the circuit or connection number.
	/Ncp p	The name of the protocol supported. Only the  IP protocol is supported by this version of ECMODULE.
	/Eiconcard n	EiconCard to monitor, where n is the EiconCard number, as specified in the WAN Services Configuration program.


Chapter 10: Using ECMODULE

ECMODULE Display Information

ECMODULE displays a different status or statistics of information depending on the type of protocol you are examining. The rest of this chapter is devoted to describing the ECMODULE display for each protocol type. Sample commands and screens, as well as full parameter descriptions are provided.

Note:
ECMODULE TRACE displays are not shown for all protocols.


Chapter 10: Using ECMODULE

DIALER Status

Command	ECMODULE STATUS DIALER [/Port p | portname]

When you issue the command ECMODULE STATUS DIALER to an Eicon Technology WAN Services PC to monitor the EiconCard Dialer module, then status information on that module is displayed.

Note:
There are no statistics available for the Dialers.

The following command shows dialer status for all ports, on all EiconCards, loaded in the WAN Services PC:

[C:\EICON]ECMODULE STATUS DIALER

Dialer Loadable Module Status
Port Number  Dialer type   State              Phone Number
-------------------------------------------------------------------------------
Card Number: 1

01           Asynchronous  Off Hook           T8614750
02           V.22 bis      On Hook

Card Number: 2
03           Direct        Opened
06           V.25 bis      Dialing           CRN642890

Card Number: 3

07           V.32 bis      Opened            T6314095

The following example shows detailed information on a specific dialer.

[C:\EICON]ECMODULE STATUS DIALER /P 1

Dialer Loadable Module Status
Port number: 01                      Port name:

ASYNC Dialer Status

State...................: On Hook
Line speed..............: 2400
Connect time............: 14:35:48 Feb 10
Main number.............: ATDT15162222233
Alternate number........:
Answer enable...........: Yes
Retry allowed...........: No          Maximum number of retry.....: 4
Parity..................: Odd         Bits per byte...............: 7

Clock type..............: External
Data encoding...........: NRZ         Ring Indicator signal.......: Off
Data Set Ready signal...: Off         Data Terminal Ready signal..: Off

Retry delay (msec)......: 5000        Inter-ring min delay (msec).: 5000
RI DTR delay (msec).....: 1000        Delay off hook (msec).......: 2000
DSR loss delay (msec)...: 1500        DSR on/off delay (msec).....: 2000
Hangup delay (msec).....: 2000        Max delay connect(msec).....: 30000

Global Status Fields

Detail Status Fields


Chapter 10: Using ECMODULE

DIALER Status

Global Status Fields

Card Number  The EiconCard number being monitored.

Port Number  The number of the EiconCard Port being monitored.

Port Name  The name of the EiconCard Port being monitored.

Dialer type  Type of interface connecting the WAN Services PC to local or remote host computers.

Value	Description
Direct	Direct Dialer.
Asynchronous	AT Dialer.
V.22bis	V22bis Dialer.
V.25bis	V25bis Dialer.
V.32bis	V32bis Dialer.

State  The current state of the dialer.

These are the possible states for the Direct Dialer:

Value	Description
Closed	Dialer not activated.
Opening	Link is being set up.
Answering	Accepting call from remote.
Delaying	Waiting for a timer to expire.
Opened	Physical link is established.
Closing	Disconnecting the physical link.

The following states are available on the AT Dialer:

Value	Description
On hook	Dialer is on hook.
Dialing	Dialing a number.
Answering	Accepting call from remote.
Ringing	Incoming call present.
Retrying	Awaiting new call attempt.
Off hook	The physical link is established. Connection established.
HangingUp	Disconnecting from DCE.

These are the states available on the V.22bis Dialer:

Value	Description
Dialing Phone	Dialing a number on the phone attached to the DNA phone plug.
Dialing Modem	Dialing a remote modem.
Retrying	Awaiting call attempt.
Ringing	Incoming call present.
Line Busy	Busy signal encountered.
Off Hook	Active: the physical link is already established.
On Hook	Not active: the physical link must be established.
Answering	Accepting call from remote.
Delaying	Waiting for timer to expire.
Voice Communication	The line is already in use by a voice connection. (DNA only)
Hand Shaking	Synchronizing communications with remote.
Waiting Ringback	Awaiting remote answer.
Initializing	Initializing modem.

These are the states available on the V.25bis Dialer:

Value	Description
On hook	Not active.
Ready	Ready to program external DCE.
Dialing	Dialing a number.
Connected	Originate call established.
Transmitting Data	Data transfer state enabled.
Retrying	Awaiting call attempt.
Ringing	Incoming call present.
Answer Started	Connect request received. Awaiting DSR.
Answer Completed	Answer call established.
Hanging Up	Dialer disconnecting from DCE.
Ignoring Ring	Ringing signal ignored.
Call Collision	Collision between connection request and incoming call. Priority given to incoming call.
Accepting Answer	Accepted incoming call.
Program Ready	Dialer ready to communicate with external DCE.
Programming	External DCE  ready to communicate with dialer; dialer may issue commands.
Program Ring	Ring signal detected from DCE; dialer cannot accept call in program mode.
Program Not Ready	Dialer not ready to communicate with external DCE.

The following states are available on an internal V.32bis Dialer:

Value	Description
Closed	Dialer not activated.
Opened	No connection established.
Local Test	Local analog loopback.
Ringing	Incoming call present.
Dialing	Dialing a number.
Answering	Call answer in progress.
Originating	Call originate in progress.
Retrying	Awaiting call attempt.
Connected	Connection present.
Retraining	Performing retrain.
Remote Test	Remote digital loopback.
Remote Disconnect	Remote has disconnected.
Local Disconnect	Local has disconnected.
Hangup Idle	Idle after hangup.
Closing	Awaiting local disconnect.
Offhook Idle	Modem goes off hook on command.

Phone Number  The phone number of the remote modem which you are calling (local originate).


Chapter 10: Using ECMODULE

DIALER Status

Detail Status Fields

Port number  The number of the EiconCard port being monitored.

Port name  The name of the EiconCard port being monitored.

State  The current state of the dialer. See the Global Status Fields for the different states available for each dialer.

Line speed  The speed setting of the driver (line speed), or of the dialer (modem speed).

Connect time  The time and date that the dialer established the current connection.

Main number  The main telephone number stored in the dialer.

Alternate number  The alternate telephone number stored in the dialer. This number is dialed if the main number is busy or if there is no answer.

Answer enable  States whether or not the dialer answers incoming calls.

Value	Description
Yes	Answer incoming calls: auto-answer mode.
No	Ignore incoming calls.

Speaker level  The volume level of the EiconCard's speaker.

Value	Description
High	High volume.
Low	Low volume.

Retry allowed  Indicates whether the dialer will try to redial a number that is busy or does not answer.

Value	Description
Yes	Redials unresponsive number.
No	Does not redial unresponsive number.

Maximum number of retry  Specifies how many times a number that is busy or otherwise unresponsive will be redialed.

Line type  States whether the modem is connected to a Leased or Dial-Up phone line.

Value	Description
Leased	The EiconCard interface is lease type.
Dial-Up	The EiconCard  interface is dial type.

Leased operation  Leased Line Type only. This field states whether the dialer will go off-hook in Originate or Answer mode. Only for V.32bis or V.22bis dialers on IMC EiconCards.

Value	Description
Originate	Initiate outgoing calls.
Answer	Answer incoming calls: auto-answer mode.

Clock type  The type of clocking used by the modem.

Value	Description
Internal	The EiconCard uses an external clock supplied by the DCE for receiving and transmitting.
External	The EiconCard generates an internal clock for receiving and transmitting, and outputs this clock on the interface for use by the DCE.
INT+DPLL	The EiconCard employs a DPLL which uses an internally generated clock which is 32 (NRZI) or 16 (FM) times the data rate.
EXT+DPLL	The EiconCard employs a DPLL which uses a DCE generated clock which is 32 (NRZI) or 16 (FM) times the data rate.

Carrier signal  Indicates whether there is currently a modem carrier signal. When there is no carrier signal, then there is no connection.

Value	Description
On	Carrier signal present.
Off	Carrier signal not present.

Data encoding  The type of data encoding used on the connection. Both ends must use the same data encoding.

Ring Indicator signal  The current status of the RI signal.

Data Set Ready signal  The current status of the DSR signal.

Data Terminal Ready signal  The current status of the DTR signal.

Call progress  The tone management mode. If this value is set to Yes, then the dial tone, busy tone, and ringback tone are detected during call establishment.

Value	Description
Yes	Tone management on.
No	Tone management off.

Tx level attenuation (dB)  The attenuation level on data transmission, once the handshake is completed with the remote modem.

Make break ratio  The pulse dialing ratio, which is the equivalent of the Hayes &P command.

Rx level attenuation (dB)  Minimum acceptable receiver threshold value. This indicates whether a 3dB attenuation is used on the receive signal at line input.

Value	Description
Yes	A 3dB attenuation used on the receive signal.
No	A 3dB attenuation is not used on the receive signal.

Guard tone  Indicates if a guard tone will be used in V.22bis transmissions, and if so, the type.

Value	Description
none	No guard tone.
550 Hz	550 Hz guard tone.
1800 Hz	1800 Hz guard tone.

DTMF Tx level (dB)  The tone dialing level attenuation in dB.

Number of rings  The number of rings required before the modem answers, if it is set to auto-answer mode.

Decadic  Indicates whether Decadic dialing is active or not. Decadic dialing does the following: each digit you dial is subtracted from 10, and the result is the number actually dialed. For example, if you enter the digit 4, it is subtracted from 10, and the digit 6 is actually dialed. The number 0 remains unchanged when Decadic is on.

Value	Description
Yes	Decadic on.
No	Decadic off.

Retry delay (msec)  The amount of time between redial attempts.

Inter-ring min delay (msec)  The minimum amount of time allowed between rings. If this minimum is not met, then the incoming calls are not recognized.

Dial delay (msec)  The length of delay associated with a comma placed in an ECDIALER dialing command.

Handshake abort timer(msec)  The amount of time the modem waits for a carrier from the remote modem. This is the equivalent of the Hayes S7 register.

Wait for carrier (msec)  The amount of time the modem waits for a valid carrier after completing a dial. If this time period expires without realizing a valid carrier, the modem goes onhook and the call attempt fails.

Wait for dial tone (msec)  The amount of time the modem waits when it encounters the wait for dial tone modifier in (a “W” character) in an ECDIALER dial string.

DTMF duration (msec)  The tone duration used in DTMF dialing.

DTMF interdigit delay(msec)  The delay between digits dialed when in tone dial mode.

Delay DSR RTS (msec)  Delay between DSR going ON, and the interface being configured for synchronous communications and transmit/receive operations.

Pulse interdigit delay(msec)  The delay between the digits dialed on a pulse line.

Delay ring DTR (msec)  The delay between the ring signal detection and the V.22 dialer response for offhook.


Chapter 10: Using ECMODULE

Frame Relay Status

Command	ECMODULE STATUS FRELAY [/Port p | portname]                        [/Connection n]

When you issue the command ECMODULE STATUS FRELAY to an Eicon Technology WAN Services PC with an active Frame Relay module, then status information is displayed.

The following command displays global status of the Frame Relay connections on the specified EiconCard port.

[C:\EICON]ECMODULE STATUS FRELAY /P 1

Frame Relay Loadable Module Status
Port number: 01                      Port name: FRELAY01

Management Protocol type ..........: Annex 'D'
Number of configured FRLL .........: 2   Maximum frame size .........: 1515

FRLL errors before reported .......: 3   Interval for error report ..: 4
Frequency of STATUS_ENQUIRY (sec) .: 6   STATUS_ENQUIRY pending .....: 0
STATUS ENQUIRY response time (sec).: 10  Internal sequence number ...: 5

Number of active DLCI .............: 2
Line state ........................: Opened             @04:23:56 Feb 20

Trace......................: Off      Trace buffer size (bytes)....: 0
Trace filter (hex).........: 00       Trace entry size (bytes).....: 0

DLCI           Management Protocol State
------------------------------------------
16              Active
17              Active

You may further obtain detailed link station status by issuing the following command:

[C:\EICON]ECMODULE STATUS FRELAY /P 1 /C 16

Frame Relay Loadable Module Status
Port number: 01                      Port name: FRELAY01
Tx buffer window size (K).......: 2

Trace......................: Off      Trace buffer size (bytes)....: 0
Trace filter (hex).........: 00       Trace entry size (bytes).....: 0

DLCI           Management Protocol State
------------------------------------------
16              Active

Global Status Fields

Detail Status Fields


Chapter 10: Using ECMODULE

Frame Relay Status

Global Status Fields

Port number  The number of the EiconCard Port being monitored.

Port name  The name of the EiconCard Port being monitored.

Management Protocol type  The Local Management Interface protocol used. LMI is a protocol and associated procedures operating on the local interface between the user and the network. LMI provides management of DLCI, which have their endpoints and bearer capabilities defined at subscription time. Pre-ANSI LMI is older, and ANSI T1.617 Annex D is newer; networks usually support one or the other.

Number of configured FRLL  The maximum number of Frame Relay Logical Links (FRLLs) allowed on a single port. There can be a maximum of 255 FRLLs on an EiconCard.

Maximum frame size  The Frame Relay Information Field size, in octets.

FRLL errors before reported  The number of reliability Errors, and/or Protocol Errors, that can occur before a Frame Relay port is declared inactive.

Frequency of STATUS_ENQUIRY (sec)  Indicates how frequently the WAN Services PC initiates a Status Enquiry message. This timer is in increments of 5 seconds. This timer is set to less than the timer used by the Frame Relay Network to verify that the user is sending Status Enquiry messages.

STATUS_ENQUIRY pending  The number of STATUS_ENQUIRY messages that have been sent without any response from the Frame Relay Network.

STATUS_ENQUIRY response time (sec)  Indicates how frequently the WAN Services PC initiates a STATUS_ENQUIRY message.

Internal sequence number  The sequence number in the last STATUS_ENQUIRY message sent.

Number of active DLCI  The number of active DLCI currently in use.

Line state  The Frame Relay Protocol state.

Value	Description
Closed	Frame Relay port is deactivated.
Closing	Request to deactivate Frame Relay port.
Opening	Request to activate Frame Relay port.
Opened	Frame Relay port is activated.
Disconnect	Loss of Frame Relay link.
Reconnect	Attempting to re-establish Frame Relay link.

Trace  Indicates whether this protocol is currently being traced using ECMODULE TRACE.

Trace buffer size (bytes)  The size of the trace buffer.

Trace filter (hex)  The trace filter lets you tailor the trace to examine certain groups of elements within the data stream. The trace filter is one byte long, with each bit filtering a specific type of protocol element. When you filter an element, you hide everything but that element. The trace filter is specified as a two-digit hexadecimal number. For a more detailed description, see the “The Trace Filter” section of this chapter.

Trace entry size (bytes)  This configures Trace to only examine the first n bytes of each frame or packet traced. If you have a Trace Entry Size of 32 bytes, then only the first 32 bytes of each frame or packet is loaded into the trace buffer.

DLCI  The Data Link Connection ID. Identifies a particular logical link in the Frame Relay network.

Management Protocol State  The DLCI state.

Value	Description
Active	The Management Protocol State is active.
Inactive	The Management Protocol State is not active.


Chapter 10: Using ECMODULE

Frame Relay Status

Detail Status Fields

Port number  The number of the EiconCard being monitored.

Port name  The name of the EiconCard port being monitored.

Tx buffer window size (K)  The size of the Frame Relay window for each DLCI. This window is used for transmission buffer control.

Trace  Indicates whether this protocol is currently being traced using ECMODULE TRACE.

Trace buffer size (bytes)  The size of the trace buffer.

Trace filter (hex)  The trace filter lets you tailor the trace to examine certain groups of elements within the data stream. The trace filter is one byte long, with each bit filtering a specific type of protocol element. When you filter an element, you hide everything but that element. The trace filter is specified as a two-digit hexadecimal number. For a more detailed description, see the “The Trace Filter” section of this chapter.

Trace entry size (bytes)  This configures Trace to only examine the first n bytes of each frame or packet traced. If you have a Trace Entry Size of 32 bytes, then only the first 32 bytes of each frame or packet is loaded into the trace buffer.

DLCI  The Data Link Connection ID. Identifies a particular logical link in the Frame Relay network.

Management Protocol State  The DLCI state.

Value	Description
Active	The Management Protocol State is active.
Inactive	The Management Protocol State is not active.


Chapter 10: Using ECMODULE

Frame Relay Statistics

Command	ECMODULE STATS FRELAY [/Port p | portname] [/Connection  n]

When you issue the command ECMODULE STATS FRELAY on an Eicon Technology WAN Services PC with an active Frame Relay connection, then global statistical information about the protocol is displayed.

The following command displays global statistics of the Frame Relay connections on the specified EiconCard port.

[C:\EICON]ECMODULE STATS FRELAY /P 1

Frame Relay Loadable Module Statistics
Port number: 01                      Port name: FRELAY01

Link up....................: 1         Link down....................: 0
Link errors................: 0         Expired T1 timer.............: 35
Parse error................: 0

Status Enquiry Message
Full status sent...........: 6
Sequence # exchange only...: 29

Unexpected Status Enquiry Response Message
Full status received.......: 0
Sequence # exchange only...: 0

                             Sent      Received
Frames.....................: 0             2599
bytes......................: 0             332672
Sequence #0................: 1             0

You may also obtain detailed statistical information on a particular DLCI station by issuing the following command:

[C:\EICON]ECMODULE STATS FRELAY /E 1 /C 16

Frame Relay Loadable Module Statistics
Port number: 01                      Port name: FRELAY01

Port number................: 0
DLCI.......................: 16

DLCI up....................: 1         DLCI down....................: 0
Backward congestion........: 0         Forward congestion...........: 0

                             Sent      Received
Frames.....................: 0             1300
bytes......................: 0             166400

Global Statistics Fields

Detail Statistics Fields


Chapter 10: Using ECMODULE

Frame Relay Statistics

Global Statistics Fields

Port number  The number of the EiconCard port number being monitored.

Port name  The name of the EiconCard port being monitored.

Link up  The number of times the link went up.

Link down  The number of times the link went down.

Link errors  The number of times the modem signal was lost on the link.

Expired T1 timer  The interval of time at which the EiconCard initiates a Status Enquiry message.

Parse error  The number of communications errors that were received.

Full Status sent  The number of times a Full Status Report was sent.

Sequence # exchange only  The number of Status message exchanges sent.

Full status received  The number of times a Full Status Report was received.

Sequence # exchange only  The number of Status message exchanges received.

Frames  The number of frames sent or received.

bytes  The number of bytes sent or received.

Sequence #0  The Status Enquiry message received or sent with a Receive Sequence = 0.


Chapter 10: Using ECMODULE

Frame Relay Statistics

Detail Statistics Fields

Port number  The number of the EiconCard port being monitored.

Port name  The name of the EiconCard port being monitored.

DLCI  The Data Link Connection ID.

DLCI up  The number of times the DLCI goes from active to inactive.

DLCI down  The number of times the DLCI goes from inactive to active.

Backward congestion  The number of frames received with backward congestion.

Forward congestion  The number of frames received with forward congestion.

Frames  The number of frames sent or received on this port connection.

bytes  The number of bytes sent or received on this port connection.


Chapter 10: Using ECMODULE

HDLC Status

Command	ECMODULE STATUS HDLC [/Port p | portname]

When you issue the command ECMODULE STATUS HDLC to an Eicon Technology WAN Services PC with an active HDLC module, then status information is displayed.

The following command displays status of the HDLC connections on the specified EiconCard port.

[C:\EICON]ECMODULE STATUS HDLC /P 2

HDLC Loadable Module Status
Port number: 02                       Port name:
Addressing.................: DTE      Check point timer T1 (msec).: 2900
Link setup.................: Active   Ack delay timer T2 (msec)...: 200
Maximum retry count N2.....: 10       Idle probe timer T3 (msec)..: 15000
Maximum window size K......: 7        Maximum frame size N1 (byte): 272

Protocol state.............: Opened       @08:06:47 Feb 27

Line state.................: Opened       @08:06:47 Feb 27

Trace......................: Off      Trace buffer size (bytes)....: 0
Trace filter (hex).........: 00       Trace entry size (bytes).....: 0

The following status is displayed when a TRANSPAC X.32 selection is made in the WAN Services Configuration program:

[C:\EICON]ECMODULE STATUS HDLC /P 1

HDLC Loadable Module Status
Port number: 1               Port name: MONTREAL01A
Addressing.................: DTE       Check point timer T1 (msec).: 2900
Link setup.................: Active    Ack delay timer T2 (msec)...: 200
Maximum retry count N2.....: 10        Idle probe timer T3 (msec)..: 15000
Maximum window size K......: 7         Maximum frame size N1(bytes): 272

Protocol state.............: Opened      @16:37:01 Feb 27

Line state.................: Opened      @16:37:01 Feb 27

TRANSPAC X.32 CID..........: 00 01 02 03 04 05 06 07 08 09 10 11 12 13 14 15
                             16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31
TRANSPAC X.32 SID..........: 00 01 02 03 04 05 06 07 08 09 10 11 12 13 14 15
                             16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31

Trace......................: Off       Trace buffer size (bytes)...: 0
Trace filter (hex).........: 00        Trace entry size (bytes)....: 0

Note:
Status displays for ERIPAK and CCITT X.32 selections are slightly different than shown above.

Status Fields


Chapter 10: Using ECMODULE

HDLC Status

Status Fields

Port number  The number of the EiconCard Port being monitored.

Port name  The name of the EiconCard Port being monitored.

Addressing  Indicates whether the monitored EiconCard port is configured as a DTE (data terminal equipment) or a DCE (data circuit-terminating equipment).

Value	Description
DTE	Used when the EiconCard port is connected to an X.25 network, or to another computer configured as DCE (null-modem connection).
DCE	Used when the EiconCard port is connected to another computer which is configured as DTE.

Check point timer T1 (msec)  When this timer expires an attempt is made to determine the status of the remote device.

Link setup  Controls how the HDLC Link setup procedure is handled. Note, if both ends are PASSIVE, then the link cannot be made.

Value	Description
Active	The EiconCard port initiates the setup procedure.
Passive	The EiconCard port waits for the other side to initiate the setup procedure.

Ack delay timer T2 (msec)  To optimize communications efficiency, acknowledgments can be piggy-backed onto outgoing frames rather than being sent out on their own. This field defines the length of the wait for an outgoing information frame.

Maximum retry count N2  Specifies the limit to the number of retries made when a particular frame meets with repeated negative acknowledgments from the remote device.

Idle probe timer T3 (msec)  When the line has become idle, an RR (receiver ready) frame (has a command P-bit set) is sent to determine the status of the remote device. If the remote device is still functioning it will respond with an RR frame (has a command F-bit set) as well.

Maximum window size (K)  The number of frames that can be sent before waiting for an acknowledgment. Maximum window size can never be exceeded.

Maximum frame size N1(bytes)  Indicates the maximum size of the HDLC frame.

Protocol state  The current status of the HDLC protocol.

Value	Description
Closed	Protocol not activated.
Closing	Terminating HDLC protocol.
Opening	Activating HDLC protocol.
Opened	HDLC active (Data mode).
Resetting	HDLC line is resetting (Sent or received a SABM).
Wait Reset	Waiting for a remote to reset the HDLC line.
Wait Open	When passive or DCE, wait for remote to activate the line using SABM.
XID Send	An X.32 XID has been sent.
XID Recv	Wait for an X.32 XID from remote.

Line state  The current status of the line itself.

Value	Description
Closed	Line is closed.
Closing	Line is closing.
Opening	Opening the line.
Opened	Line is ready.
Delaying	Waiting for a small delay in order to re-open the line.

TRANSPAC X.32 CID and TRANSPAC X.32 SID  These fields are only displayed when an X.32 selection is made in the WAN Services Configuration program. The TRANSPAC X.32 CID is a code that identifies you to other systems. This is useful when you are using a dial-up line and the temporary DTE address is insufficient to properly identify you.

ERIPAK  This field is only displayed when an ERIPAK selection is made in the WAN Services Configuration program. The ERIPAK CID is a code that identifies you to other systems. This is useful when you are using a dial-up line and the temporary DTE address is insufficient to properly identify you.

CCITT X.32  This field is only displayed when a CCITT X.32 selection is made in the WAN Services Configuration program. The CCITT X.32 is a code that identifies you to other systems. This is useful when you are using a dial-up line and the temporary DTE address is insufficient to properly identify you.

Trace  (On/Off) Indicates whether this protocol is currently being traced using ECMODULE TRACE.

Trace buffer size (bytes)  The size of the trace buffer.

Trace filter (hex)  The trace filter lets you tailor the trace to examine certain groups of elements within the data stream. The trace filter is one byte long, with each bit filtering a specific type of protocol element. When you filter an element, you hide everything but that element. The trace filter is specified as a two-digit hexadecimal number. For more information, see the “The Trace Filter” section later in this chapter.

Trace entry size (bytes)  This configures Trace to only examine the first n bytes of each frame or packet traced. If you have a Trace Entry Size of 32 bytes, then only the first 32 bytes of each frame or packet is loaded into the trace buffer.


Chapter 10: Using ECMODULE

HDLC Statistics

Command	ECMODULE STATS HDLC [/Port p | portname]

When you issue the command ECMODULE STATS HDLC on an Eicon Technology WAN Services PC with an active HDLC module, then statistical information is displayed.

The following command displays statistics of the HDLC connections on the specified EiconCard port.

[C:\EICON]ECMODULE STATS HDLC /P 1

HDLC Loadable Module Statistics

Port number:       1                    Port name: MONTREAL01A
T1 expired.......: 0                    Retransmissions....: 0
Underrun.........: 0
Overrun..........: 0

                   Sent      Received                      Sent      Received
SABM.............: 1         0          XID..............: 0         0
DISC.............: 0         0          I................: 165       181
UA...............: 0         1          RR...............: 53        51
DM...............: 0         0          RNR..............: 0         0
FRMR.............: 0         0          Rejects..........: 00
Abort............: 0         0
Bad Type.........: 0         0
Bad CRC..........:           0

Statistics Fields


Chapter 10: Using ECMODULE

HDLC Statistics

Statistics Fields

Port name  The name of the EiconCard port being monitored.

Port number  The number of the EiconCard port being monitored.

T1 expired  The number of times the Checkpoint timer (T1) has been exceeded.

Retransmissions  The number of times a frame has had to be retransmitted.

Underrun  The number of times that more frames have been transmitted than the receiver can handle.

Overrun  The number of times that the EiconCard could not handle incoming frames.

SABM  The number of Set Asynchronous Balanced Mode frames sent/received. This is used to initialize the HDLC connection. Note that, a large number of SABM frames could indicate an unstable HDLC connection.

XID  The number of exchange station identification frames sent/received.

DISC  The number of disconnect frames sent/received. Note that, a large number of DISC frames could indicate an unstable HDLC connection.

I  The number of information frames sent/received.

UA  The number of Unnumbered Acknowledgment frames sent/received. This is used to respond to a SABM or to a DISC frame when the link is closed at initialization time. Note that a large number of UA frames could indicate an unstable HDLC connection.

RR  The number of Receiver Ready frames sent/received.

DM  The number of Disconnected Mode frames sent/received.

RNR  The number of Receiver Not Ready frames sent/received.

FRMR The number of Frame Reject frames sent/received.

Rejects  The number of HDLC frames that have been rejected.

Abort  The number of frames received with abort indication.

Bad type  The number of unknown frames received.

Bad CRC  The number of frames received with bad CRC.


Chapter 10: Using ECMODULE

PPP Status

Command	ECMODULE STATUS PPP [/Port p | portname] [/NCP p]

When you issue the command ECMODULE STATUS PPP to an Eicon Technology WAN Services PC with an active PPP module, then status information is displayed.

The following command displays global status of the PPP module on the specified EiconCard port.

[C:\EICON]ECMODULE STATUS PPP /P 1

EiconCard Loadable Module Management Utility
ECMODULE 3.02 Rev. 05
Copyright (c) Eicon Technology Corporation 1995. All Rights Reserved.

PPP Loadable Module Status
Port number: 01                      Port name: PORT1

Packet size configured (bytes)  : 1504  Window size ...................: 8
Packet size negotiated (bytes)  : 1500  Retransmission Timer (sec).....: 3

Retransmissions:
Maximum terminate : 10      Maximum configure : 10      Maximum failure : 10

Authentication protocol name.....: None
      Maximum  Configure ........: 10           Maximum  Failure .......: 5
      Identification ............:
      Password ..................:

Protocol state...................: CLOSED
Network Protocol supported ......: None

Trace......................: Off      Trace buffer size (bytes)....: 0
Trace filter (hex).........: 00       Trace entry size (bytes).....: 0

You may obtain detailed information about the (routed) IP protocol by issuing the following command:

[C:\EICON]ECMODULE STATUS PPP /P 1 /NCP IP

EiconCard Loadable Module Management Utility
ECMODULE 3.02 Rev. 05
Copyright (c) Eicon Technology Corporation 1995. All Rights Reserved.

PPP Loadable Module Status
Port number: 01                      Port name: PORT1

Network Protocol name ......: Internet
Network Protocol state......: Initial
Internet address............: 0

Retransmissions:
   Maximum terminate : 2
   Maximum configure : 50
   Maximum failure   : 5
Global Status Fields

Global Status Fields

IP Protocol Status Fields


Chapter 10: Using ECMODULE

PPP Status

Global Status Fields

Port number  The number of the EiconCard Port being monitored.

Port name  The name of the EiconCard Port being monitored.

Packet size configured (bytes)  The size, in bytes, of the PPP data packets as configured on  the local router.

Packet size negotiated (bytes)  The size, in bytes, of the PPP data packets as negotiated by the local and remote routers.

Window size  Specifies the number of PPP packets that can be sent before a pacing response (Acknowledgment) is required as negotiated by the local and remote routers.

Retransmission Timer  How long, in seconds, the local router will wait for an acknowledgment (-Ack) packet for any Configure-Request, Terminate-Request, or Authenticate-Request packet before resending that packet.

Retransmissions / Maximum terminate  The maximum number of times PPP will retransmit a Terminate-Request without receiving a Terminate-Ack packet.

Retransmissions / Maximum configure  The maximum number of times PPP will retransmit a Configure-Request without receiving a Configure-Ack (Acknowledge) or Configure-Nak (Not Acknowledge) packet.

Retransmissions / Maximum failure  The maximum number of times PPP will retransmit a Configure-Nak packet—without transmitting a Configure-Ack packet—before it begins transmitting Configure-Reject packets.

Authentication protocol name  Specifies the Authentication protocol used.

Maximum configure  Used during the password authentication stage (see Password, below). This is the number of times PPP will retransmit an Authenticate-Request packet, without receiving an Authenticate-Ack or Authenticate-Nak packet, before it aborts the attempt to establish the initial connection with the remote PPP.

Maximum Failure  Used during the password authentication stage (see Password, below). This is the number of times PPP will retransmit an Authenticate-Nak packet, without transmitting an Authenticate-Ack packet, before it aborts the attempt to establish the initial connection with the remote PPP.

Identification  Used as a “user name” during the password authentication stage (see Password, below) to identify Point-to-Point Protocol (the local PPP module) to the remote PPP.

Password  Used during the password authentication stage, when the initial connection between the local and remote PPPs is being negotiated, to identify Point-to-Point Protocol (the local PPP module) to the remote PPP.

Protocol state  Specifies the state of the PPP connection as one of the following:

Value	Description
CLOSED	A point-to-point link connection is terminated.
OPENING	A point-to-point link connection is being established.
NEGOTIATING	A point-to-point link connection is being negotiated by the local and remoter router.
OPENED	A point-to-point link is active.
CLOSING	A point-to-point link connection is being terminated.

Network Protocol supported  When a point-to-point connection is active, the network protocols (IP, IPX, AT) that can be routed over it.

Trace   Whether or not protocol tracing is active for PPP.

Trace buffer size (bytes) If protocol tracing is active for PPP, the size of the trace buffer in bytes.

Trace filter (hex)  The trace mask (2-digit hexadecimal number) used for tracing PPP.

Trace entry size (bytes)  Number of bytes of each protocol element to trace. This may be fewer than in a single protocol element.


Chapter 10: Using ECMODULE

PPP Status

IP Protocol Status Fields

Port number  The number of the EiconCard Port being monitored.

Port name  The name of the EiconCard Port being monitored.

Network Protocol name  The name of the (routed) network protocol for which you are displaying detailed status information. For now this can only be IP.

Network Protocol state  Specifies the state of the connection during the Network Control Protocol phase.

Internet address  For purposes of routing IP packets, the IP address of the local router.

Retransmissions / Maximum terminate  The maximum number of times IPCP will retransmit a Terminate-Request without receiving a Terminate-Ack packet.

Retransmissions / Maximum configure  The maximum number of times IPCP will retransmit a Configure-Request without receiving a Configure-Ack (Acknowledge) or Configure-Nak (Not Acknowledge) packet.

Retransmissions / Maximum failure  The maximum number of times IPCP will retransmit a Configure-Nak packet—without transmitting a Configure-Ack packet— before it begins transmitting Configure-Reject packets.


Chapter 10: Using ECMODULE

PPP Statistics

Command	ECMODULE STATS PPP [/Port p | portname] [/NCP p]

When you issue the command ECMODULE STATS PPP to an Eicon Technology WAN Services PC with an active Frame Relay module, then status information is displayed.

The following command displays global status of the Frame Relay connections on the specified EiconCard port.

[C:\EICON]ECMODULE STATS PPP /P 1

EiconCard Loadable Module Management Utility
ECMODULE 3.02 Rev. 05
Copyright (c) Eicon Technology Corporation 1995. All Rights Reserved.
PPP Loadable Module Statistics
Port number: 01                      Port name: PORT1
LCP                TX,  RX                              TX,  RX
Conf Req.........   0,   0           Conf Ack.........   0,   0
Conf Nak.........   0,   0           Conf Rej.........   0,   0
Term Req.........   0,   0           Term Ack.........   0,   0
Code Rej.........   0,   0           Prot Rej.........   0,   0
Echo Req.........   0,   0           Echo Rep.........   0,   0
Disc Req.........   0,   0           Retransmission Timer     0
Term Req Retrans         0           Conf Req Retrans         0
TOTAL NCP          TX,  RX                              TX,  RX
Conf Req.........   0,   0           Conf Ack.........   0,   0
Conf Nak.........   0,   0           Conf Rej.........   0,   0
Term Req.........   0,   0           Term Ack.........   0,   0
Code Rej.........   0,   0           Retransmission Timer     0
Term Req Retrans         0           Conf Req Retrans         0
Info Frame.......   0,   0           Info Char........   0,   0

You may obtain further detailed link station status information by issuing the following command:

[C:\EICON]ECMODULE STATS PPP /P 1 /NCP IP

EiconCard Loadable Module Management Utility
ECMODULE 3.02 Rev. 05
Copyright (c) Eicon Technology Corporation 1995. All Rights Reserved.
PPP Loadable Module Statistics
Port number: 01                      Port name: PORT1
NCP :  IP          TX,  RX                               TX,  RX
Conf Req.........   0,   0           Conf Ack.........   0,   0
Conf Nak.........   0,   0           Conf Rej.........   0,   0
Term Req.........   0,   0           Term Ack.........   0,   0
Code Rej.........   0,   0           Retransmission Timer     0
Term Req Retrans         0           Conf Req Retrans         0
Datagrams........   0,   0           Characters.......   0,   0
Command Completed Successfully.

Port number The number of the EiconCard Port being monitored.

Port name  The name of the EiconCard Port being monitored.

Global Statistics Fields

IP Detailed Statistics Fields


Chapter 10: Using ECMODULE

PPP Statistics

Global Statistics Fields

LCP

Conf Req  The number of Link Control Protocol Configure-Request packets transmitted and received.

Conf Nak  The number of Link Control Protocol Configure-NAk packets transmitted and received.

Term Req  The number of Link Control Protocol Terminate-Request packets transmitted and received.

Code Rej  The number of Link Control Protocol Code-Reject packets transmitted and received.

Echo Req  The number of Link Control Protocol Echo-Request packets transmitted and received.

Disc Req  The number of Link Control Protocol Disconnect-Request packets transmitted and received.

Term Req Retrans  The total number of Link Control Protocol Terminate-Request retransmissions.

Conf Ack  The number of Link Control Protocol Configure-Ack packets transmitted and received.

Conf Rej  The number of Link Control Protocol Configure-Reject packets transmitted and received.

Term Ack  The number of Link Control Protocol Terminate-Acknowledge packets transmitted and received.

Prot Rej  The number of LCP Protocol-Reject packets transmitted and received.

Echo Rep  The number of LCP Echo-Reply packets transmitted and received.

Retransmission Timer  For Link Control Protocol packets, the number of times the retransmission timer has expired.

Conf Req Retrans  The total number of Link Control Protocol Configure-Request retransmissions.

Total NCP

Conf Req  The number of Configure-Request packets transmitted and received for all network control protocols (NCPs): IPCP, IPXCP, ATCP.

Conf Nak  The number of Configure-NAk packets transmitted and received for all network control protocols (NCPs): IPCP, IPXCP, ATCP.

Term Req  The number of Terminate-Request packets transmitted and received for all network control protocols (NCPs): IPCP, IPXCP, ATCP.

Code Rej  The number of Code-Reject packets transmitted and received for all network control protocols (NCPs): IPCP, IPXCP, ATCP.

Term Req Retrans  The number of Terminate-Request retransmissions for all network control protocols (NCPs): IPCP, IPXCP, ATCP.

Info Frame  The total number of packets transmitted and received by the local PPP module while negotiating with the remote PPP module.

Conf Ack  The number of Configure-Ack packets transmitted and received for all network control protocols (NCPs): IPCP, IPXCP, ATCP.

Conf Rej  The number of Configure-Reject packets transmitted and received for all network control protocols (NCPs): IPCP, IPXCP, ATCP.

Term Ack  The number of Terminate-Acknowledge packets transmitted and received for all network control protocols (NCPs): IPCP, IPXCP, ATCP.

Retransmission Timer  The number of times the retransmission timer has expired for all network control protocols (NCPs): IPCP, IPXCP, ATCP.

Conf Req Retrans  The total number of Configure-Request retransmissions for all network control protocols (NCPs): IPCP, IPXCP, ATCP.

Info Char  The total number of characters transmitted and received by the local PPP module while negotiating with the remote PPP module.


Chapter 10: Using ECMODULE

PPP Statistics

IP Detailed Statistics Fields

Port number  The number of the EiconCard Port being monitored.

Port name  The name of the EiconCard Port being monitored.

NCP  The Network Control Protocol (NCP) for which detailed statistics are being displayed. For now this can only be IP.

Conf Req  The number of Configure-Request packets transmitted and received for the IPCP Network Control Protocol (NCP).

Conf Nak  The number of Configure-NAk packets transmitted and received for the IPCP Network Control Protocol (NCP).

Term Req  The number of Terminate-Request packets transmitted and received for the IPCP Network Control Protocol (NCP).

Code Rej  The number of Code-Reject packets transmitted and received for the IPCP Network Control Protocol (NCP).

Term Req Retrans  The number of Terminate-Request retransmissions for the IPCP Network Control Protocol (NCP).

Datagrams  The total number of IP datagrams (packets) encapsulated and routed to the remote router (TX), and received from the remote router and de-encapsulated (RX).

Conf Ack  The number of Configure-Ack packets transmitted and received for the IPCP Network Control Protocol (NCP).

Conf Rej  The number of Configure-Reject packets transmitted and received for the IPCP Network Control Protocol (NCP).

Term Ack  The number of Terminate-Acknowledge packets transmitted and received for the IPCP Network Control Protocol (NCP).

Retransmission Timer  The number of times the retransmission timer has expired for the IPCP Network Control Protocol (NCP).

Conf Req Retrans  The total number of Configure-Request retransmissions for the IPCP Network Control Protocol (NCP).

Characters  The total number of characters transmitted to, and received from, the remote router inside IP datagrams (packets).


Chapter 10: Using ECMODULE

SDLC Status

Command	ECMODULE STATUS SDLC [/Port p | portname] [/Connection n]

When you issue the command ECMODULE STATUS SDLC on an Eicon Technology WAN Services PC with an active SDLC connection, then status information on that protocol is displayed.

The following command displays the global status of the SDLC connections on the specified EiconCard port:

ECMODULE STATUS SDLC /P 2

SDLC Loadable Module Status
Port number: 02                      Port name:
Line type..................: Leased  Duplex.......................: Full
Maximum window size........: 7       Maximum frame size(octets)...: 1996
Maximum multi-drop stations: 9       Multi-drop stations in use...: 5
Trace......................: On      Trace buffer size (bytes)....: 2048
Trace filter (hex).........: FF      Trace entry size (bytes).....: 256

Addr  Type       Protocol State
-------------------------------------------------
1     Secondary  Opened           08:41:34 Feb 30
2     Secondary  Opened           08:41:36 Feb 30
3     Secondary  Opened           08:41:38 Feb 30
4     Secondary  Opened           08:44:40 Feb 30
5     Secondary  Opened           08:41:42 Feb 30

You may also obtain detailed connection status by issuing this command:

ECMODULE STATUS SDLC /P 2 /C 1

SDLC Loadable Module Status
Port number: 02                      Port name:
Maximum frame size (octets): 265
Maxin (bytes)..............: 7        Maxout (bytes)...............: 7
Trace......................: Off      Trace buffer size (bytes)....: 0
Trace filter (hex).........: 00       Trace entry size (bytes).....: 0

Addr  Type       Protocol State
-------------------------------------------------
1     Secondary  Opened           08:41:34 Feb 30

Global and Detailed Status Fields


Chapter 10: Using ECMODULE

SDLC Status

Global and Detailed Status Fields

Port number  The number of the EiconCard port being monitored.

Port name  The name of the EiconCard port being monitored.

Line type  Indicates whether the modem is connected to a Leased or Dial-Up line.

Value	Description
Leased	The EiconCard is connected to a null-modem cable or a modem that links to a dedicated leased line.
Dial-Up	The EiconCard must dial a number to make a connection.

Duplex  The type of device to which the port is connected. Full-duplex devices enable the port to transmit and receive data at the same time. With a half-duplex device, the port must alternate between transmitting and receiving.

Value	Description
Full	Full-duplex
Half	Half-duplex

Maximum window size  The number of frames that can be received before an acknowledgment is sent. It is sometimes desirable to have a large window size. This is particularly true for satellite networks that have significant transmission delays.

Maximum frame size (octets)  Maximum SDLC frame size.

Maximum multi-drop stations  The number of multi-drop stations (controllers and/or Nodes) defined for the same line.

Multi-drop stations in use  The number of multi-drop stations currently being used.

Trace  Indicates whether this protocol is currently being traced using ECMODULE TRACE.

Trace buffer size (bytes)  The size of the trace buffer.

Trace filter (hex)  Indicates the trace filter that is currently being used. See “The Trace Filter,” for more information.

Trace entry size (bytes)  This configures Trace to only examine the first bytes of each frame or packet traced. If you have a Trace Entry Size of 512 bytes, then only the first 512 bytes of each frame or packet is loaded into the trace buffer.

Addr  The control unit (CU) hexadecimal address (up to FF) of the SDLC link connection.

Type  The kind of station role the Eicon Technology WAN Services PC is performing.

Value	Description
Primary	The WAN Services PC is the primary (master) multi-drop station.
Secondary	The WAN Services PC is a secondary (slave) multi-drop station.


Chapter 10: Using ECMODULE

SDLC Statistics

Command	ECMODULE STATS SDLC [/Port p | portname] [/Connection n]

When you issue the command ECMODULE STATS SDLC on an Eicon Technology WAN Services PC with an active SDLC connection, then statistical information about the protocol is displayed.

The following command displays the global statistics of all SDLC stations on the specified EiconCard port:

ECMODULE STATS SDLC /P 1

SDLC Loadable Module Statistics
Port number: 01                      Port name: SDLC

T1 expired.......: 0                    Retransmissions..:           0
Underrun.........: 0
Overrun..........: 0
                  Sent      Received                      Sent      Received
DM...............: 0         0          FRMR.............: 0         0
UA...............: 1         0          SNRM.............: 0         8
XID..............: 1         15         TEST.............: 0         0
I................: 18        16         DISC.............: 0         0
RR...............: 8980      8978       REJ..............: 0         0
RNR..............: 0         0
Bad type.........: 0
Bad CRC..........: 0

You may also obtain detailed statistical information on each active SDLC station by issuing this command:

ECMODULE STATS SDLC /P 1 /C 4

SDLC Loadable Module Statistics
Port number: 01                      Port name: SDLC
Station address............: 04

T1 expired.......: 0                    Retransmissions..:           0
Underrun.........: 0
Overrun..........: 0
                 Sent      Received                      Sent      Received
DM...............: 0         0          FRMR.............: 0         0
UA...............: 1         0          SNRM.............: 0         1
XID..............: 1         1          TEST.............: 0         0
I................: 18        16         DISC.............: 0         0
RR...............: 9260      9258       REJ..............: 0         0
RNR..............: 0         0
Bad type.........: 0
Bad CRC..........: 0

Statistics Fields


Chapter 10: Using ECMODULE

SDLC Statistics

Statistics Fields

Port number  The number of the EiconCard Port being monitored.

Port name  The name of the EiconCard Port being monitored.

Station address  The hexadecimal control unit address (up to FF) of the station being monitored.

T1 expired  The number of times the Checkpoint timer (T1) protocol timer has been exceeded.

Retransmissions  The number of retransmitted frames.

Underrun  The number of times an underrun occurred. An underrun occurs when transmission of a frame could not keep up with the line speed.

Overrun  The number of times an overrun occurred. An overrun occurs when the EiconCard port driver cannot handle incoming frames.

DM  The number of disconnected mode U-frames sent/received.

FRMR  The number of frame reject U-frames sent/received.

UA  The number of unnumbered acknowledgment U-frames sent/received.

SNRM  The number of set normal response mode U-frames sent/received.

XID  The number of exchange station identification U-frames sent/received.

TEST  The number of TEST U-frames sent/received.

I  The number of information frames sent/received.

DISC  The number of disconnect U-frames sent/received.

RR  The number of receiver ready I-frames sent/received.

REJ  The number of reject I-frames sent/received.

RNR  Number of receiver not ready I-frames sent/received.

Bad type  The number of unknown frames received.

Bad CRC  The number of frames received with bad CRC.


Chapter 10: Using ECMODULE

Transport ISO and BULL TGX Status

Command	ECMODULE STATUS XPORTISO | XPORTTGX [/Eiconcard n]  [/Connection n]

When you issue the above command to an WAN Services PC with an active Transport module, then status information is displayed. The following command displays the global status of the connections on the specified EiconCard.

ECMODULE STATUS XPORTISO /E 2

ISO Transport Loadable Module Status

Card number: 2

Maximum TPDU size...........: 512

Maximum number of connections: 8

Maximum credit per connection: 2

Active sessions..............: 2

Activated at.................: 13:16:04 Jan 15

Trace........................: On       Trace buffer size (bytes)....: 2048
Trace filter (hex)...........: FF       Trace entry size (bytes).....: 32

TC   Status                           Local  TSAP
                                      Remote TSAP
----------------------------------------------------------------------
1    Opened         @13:37:02 Feb 15  LOCAL
                                      REMOTE
2    Opened         @13:37:02 Feb 15  LOCAL1234
                                      RE345678901234567890123456789012

You may also obtain detailed connection status by issuing the following command:

ECMODULE STATUS XPORTISO /E 2 /C 1

ISO Transport Loadable Module Status
Card number: 2

Transport connection........: 1       Transport class...  ..........: 0
Sequencing..................: Normal   Explicit flow................: No   Expedited data..............: No       TPDU size....................: 512

X.25 Virtual Circuit used...: 04       Packet size of the connection: 128
Port number used by VC......: 01       No. of TCs multiplexed on VC.: 1
Remote DTE address..........: 56300026
Local DTE address...........:
Virtual circuit state.......: Circuit  Ready     @80:98:61 May 12

X.25 Call user facilities: None
X.25 Call user data: None

Trace......................: Off      Trace buffer size (bytes)....: 0
Trace filter (hex).........: 00       Trace entry size (bytes).....: 0

TC   Status                           Local  TSAP
                                      Remote TSAP
----------------------------------------------------------------------
1    Opened         @13:37:02 Feb 15  LOCAL
                                      REMOTE

Global Status Fields

Detail Status Fields


Chapter 10: Using ECMODULE

Transport ISO and BULL TGX Status

Global Status Fields

Card number  The EiconCard card number being monitored.

Maximum TPDU size  The maximum TPDU (Transport Protocol Data Unit) size.

Maximum number of connections  The maximum allowable number of Transport connections that can be made simultaneously.

Maximum credit per connection  The Credit is the maximum number of data TPDUs that can be awaiting an acknowledgement from the remote Transport entity.

Active sessions  The total number of active transport connections.

Activated at  The time and date when the Transport protocol module was started.

Trace  Indicates whether this protocol is currently being traced using ECMODULE TRACE.

Trace buffer size (bytes)  The size of the trace buffer.

Trace filter (hex)  The trace filter lets you tailor the trace to examine certain groups of elements within the data stream. The trace filter is one byte long, with each bit filtering a specific type of protocol element. When you filter an element, you hide everything but that element. The trace filter is specified as a two-digit hexadecimal number. For more information, see the “The Trace Filter” section later in this chapter.

Trace entry size (bytes)  This configures Trace to only examine the first n bytes of each frame or packet traced. If you have a Trace Entry Size of 32 bytes, then only the first 32 bytes of each frame or packet is loaded into the trace buffer.

TC  Transport Connection reference number.

Status  The current status of the line used by the Transport connection.

Value	Description
Closed	Transport connection not used.
Opened	Data mode.
Wait for NC	An X.25 virtual circuit has been requested. The transport connection waits for the virtual circuit to be established.
Wait TX CR	Wait for available resources to send Call Request.
Wait for CC	Wait for Call Confirm; a Call Request TPDU was sent.
Wait TX DR	Wait for available resources to sent Disconnect request.
Wait for DC	Wait for Disconnect Confirm. A Disconnect Request TPDU was sent.
Wait for EA	An expedited data TPDU was sent. Wait for expedited data acknowledge.
Wait for UResp	Wait for user application to accept or reject an incoming Transport Call Request.
Wait TX CC	Wait for available resources to send a Call Confirm TPDU.

Local  SAP  The Transport Service Access Point address of the Eicon Technology WAN Services PC. The TSAP is an address required to set up a transport connection.

Remote TSAP  The Transport Service Access Point address of the remote computer. The TSAP is an address required to set up a transport connection.


Chapter 10: Using ECMODULE

Transport ISO and BULL TGX Status

Detail Status Fields

Card number  The number of the EiconCard being monitored.

Transport connection  The specific connection being monitored.

Transport class  Transport class used for the connection. Can be either Class 2 or Class 0.

Sequencing  The extended sequencing used to provide a larger window size. Normal sequencing is the default.

Explicit flow  The use of flow control for the Transport connection.

Expedited data  Indicates whether or not expedited TPDU data is allowed on the connection.

TPDU size  The maximum TPDU (Transport Protocol Data Unit) size.

X.25 Virtual Circuit used  The virtual circuit connection number used for this connection.

Packet size of the connection  The Packet Size of the X.25 connection used for the transport connection.

Port number used by VC  The EiconCard port number for the X.25 connection used by this Transport connection.

No. of TCs multiplexed on VC  The number of Transport Connections that share the same X.25 Virtual Circuit.

Remote DTE address  The X.25 DTE Address of the remote Transport endpoint.

Local DTE address  The gateway's local X.25 address used for the Transport connection.

Virtual circuit state  The current state of the X.25 Virtual Circuit.

Value	Description
Pkt CLS	Closed
Packet Idle	Idle (for port status only)
DTE Restart	The WAN Services PC has sent a Restart Request packet.
DCE Restart	Restart indication packet was received.
Packet Ready	Virtual circuit is disconnected.
DTE Call	Outgoing Call Request was sent.
DCE Call	A Call Indication packet was received.
Call Collision	X.25 call collision.
Circuit Ready	X.25 level is up on the port and the virtual circuit is ready to be established.
DTE Clear	A Clear Request packet was sent.
DCE Clear	A Clear Indication packet was received. Remote requested termination of virtual circuit.
DTE Reset	The virtual circuit is locally reset.
DCE Reset	Remote reset the virtual circuit.

X.25 Call user facilities  Call User Facilities are optional network services that provide features such as reverse charging, access to a Closed User Group, or specification of a Network User Identification. The Call User Facility field can contain up to 63 bytes.

X.25 Call user data  Call User Data can be used to request services specific to the host you are calling, such as a password, or to indicate your Protocol I.D. code. The Call User Data field can contain up to 128 bytes. The display shows both a dump format (see left column) and the ASCII equivalent (see right-hand column).

Trace  Indicates whether this protocol is currently being traced using ECMODULE TRACE.

Trace buffer size (bytes)  The size of the trace buffer.

Trace filter (hex)  The trace filter lets you tailor the trace to examine certain groups of elements within the data stream. The trace filter is one byte long, with each bit filtering a specific type of protocol element. When you filter an element, you hide everything but that element. The trace filter is specified as a two-digit hexadecimal number. For more information, see the “The Trace Filter” section later in this chapter.

Trace entry size (bytes)  The configures Trace to only examine the first n bytes of each frame or packet traced. If you have a Trace Entry Size of 32 bytes, then only the first 32 bytes of each frame or packet is loaded into the trace buffer.

TC  The Transport Connection reference number.

Status  The current status of the Transport Connection (TC). Refer to previous table for Status values.


Chapter 10: Using ECMODULE

Transport ISO and BULL TGX Statistics

Command	ECMODULE STATS XPORTISO | XPORTTGX [/Eiconcard n]  [/Connection n]

When you issue the above command on a WAN Services PC with an active Transport module, then statistical information is displayed.

The following command displays the global statistics of the connections on the specified EiconCard.

ECMODULE STATS XPORTISO /E 1

ISO Transport Loadable Module Statistics

Card Number:1

Retransmissions..................: 0
Session resets...................: 0
Connection request timeout (CR)..: 0
Disconnect request timeout (DR)..: 0
Data acknowledgment timeout (AK).: 0

                                  Sent       Received
Connection request (CR)..........: 1          0
Disconnect request (DR)..........: 0          0
Data (DT)........................: 4          7
Connect confirm (CC).............: 0          1
Disconnect confirm (DC)..........: 0          0
Data acknowledgment (AK).........: 7          4
Expedited data (ED)..............: 0          0
Reject (RJ)......................: 0          0
Expedited data ack (EA)..........: 0          0
ERROR (ER).......................: 0          0

The detailed statistical information can be displayed with the following command:

ECMODULE STATS XPORTISO /E 1 /C 2

ISO Transport Loadable Module Statistics

Transport Connection:2

Retransmissions..................: 0
Session resets...................: 0
Connection request timeout (CR)..: 0
Disconnect request timeout (DR)..: 0
Data acknowledgment timeout (AK).: 0

                                  Sent       Received
Connection request (CR)..........: 0          1
Disconnect request (DR)..........: 0          1
Data (DT)........................: 0          15
Connect confirm (CC).............: 1          0
Disconnect confirm (DC)..........: 1          0
Data acknowledgment (AK).........: 15         0
Expedited data (ED)..............: 0          0
Reject (RJ)......................: 0          0
Expedited data ack (EA)..........: 0          0
ERROR (ER).......................: 0          0

Global and Detailed Statistics Fields


Chapter 10: Using ECMODULE

Transport ISO and BULL TGX Statistics

Global and Detailed Statistics Fields

Card number  The number of the EiconCard being monitored.

Transport Connection  The EiconCard connection being monitored.

Retransmissions  The number of retransmitted TPDUs.

Session resets  The number of times the Transport connections have been closed due to packet level restarts or resets.

Connection request timeout (CR)  The number of times the Connection Request timer has been exceeded.

Disconnect request timeout (DR)  The number of times the Disconnect Request timer has been exceeded.

Data acknowledgment timeout (AK)  The number of times the Data Acknowledgement timer has been exceeded. This is not an error condition. This count is incremented every time an acknowledge is sent because of the timer expiration.

Connection request (CR)  The number of Connection Request TPDUs that have been sent or received.

Disconnect request (DR)  The number of Disconnect Request TPDUs that have been sent or received.

Data (DT)  The number of Data TPDUs that have been sent or received.

Connect confirm (CC)  The number of Connect Confirm TPDUs that have been sent or received.

Disconnect confirm (DC)  The number of Disconnect Confirm TPDUs that have been sent or received.

Data acknowledgment (AK)  The number of Data Acknowledgement TPDUs that have been sent or received.

Expedited data (ED)  The number of Expedited Data TPDUs that have been sent or received.

Reject (RJ)  The number of Reject TPDUs that have been sent or received.

Expedited data ack (EA)  The number of Expedited Data Acknowledgement TPDUs that have been sent or received.

ERROR (ER)  The number of Error TPDUs that have been sent or received.


Chapter 10: Using ECMODULE

X.25 Status

Command	ECMODULE STATUS X25 [/Eiconcard n][/Connection n]

When you issue the command ECMODULE STATUS X25 to an Eicon Technology WAN Services PC with an active X.25 module, then status information is displayed.

The following command can be used to examine a specific port of an Eicon Technology WAN Services PC with an active X.25 module:

[C:\EICON]ECMODULE STATUS X25 /P 1

X.25 Loadable Module Status
Port number: 1            Port name: MONTREAL01A

                              Default  Maximum
Window size.................: 2        7
Packet size (bytes).........: 256      256
Packet format...............: Extended Maximum retry count N3......: 3
Restart timer T20 (sec).....: 60       Reset timer T22 (sec).......: 60
Call timer T21 (sec)........: 60       Clear timer T23 (sec).......: 60
Idle timer (sec)............: 0        Acknowledgment timer (msec): 10
Two-way VCs configured......: 4        Permanent VCs configured....: 0
In-coming VCs configured....: 0        Out-going VCs configured....: 0

Trace.......................: Off      Trace buffer size (bytes)...: 0
Trace filter (hex)..........: 00       Trace entry size (bytes)....: 0

Link activated at...........: @13:54:03 Feb 12
Last restart................: @13:54:11 Feb 12

VC Local Address  Remote Address  Type     Status
-------------------------------------------------------------------------
1  31312222222222 31311111111111  2Way  Circuit Ready   @13:37:01 Feb 12
2  31313333333333 31319999999999  2Way  Circuit Ready   @15:00:01 Feb 12

You may also obtain detailed connection status by issuing this command:

[C:\EICON]ECMODULE STATUS X25 /P 1 /C 16

X.25 Loadable Module Status
Port number: 01                      Port name:
                               Transmit Receive
Window size.                 : 2        2
Packet size (bytes)..........: 128      128
Last reset........... .......: @12:06:10 Feb 30

X.25 Call user facilities: 43,2,2,42,7,7

X.25 Call user data:
c3 00 00 00  ................

Trace........................: Off      Trace buffer size (bytes)....: 0
Trace filter (hex)...........: 00       Trace entry size (bytes).....: 0

VC  Local Address  Remote Address  Type   Status
-------------------------------------------------------------------------
16         .       131445162220052 2Way   Circuit Ready  @12:06:28 Feb 30

Global Status Fields

Detail Status Fields


Chapter 10: Using ECMODULE

X.25 Status

Global Status Fields

Port number  The number of the EiconCard Port being monitored.

Port name  The name of the EiconCard Port being monitored.

Window size  The number of packets that can be sent before waiting for an acknowledgment. Both Receive and Transmit values are shown. They are usually the same (symmetrical), but could be different.

Packet size (bytes)  The size of the X.25 packet, in bytes. Both Receive and Transmit values are shown. They are usually the same (symmetrical), but could be different.

Packet format  In 1984 the CCITT added an Extended Packet definition to the X.25 specification.

Value	Description
Standard	Allow only the standard packets supported on all networks.
Extended	Allow a larger window size, and use of extended clearing, call user data, and other features supported only by certain networks.

Maximum retry count N3  When a particular packet meets with repeated negative acknowledgments from the remote device, there must be a limit as to the number of retries made.

Restart timer T20 (sec)  The Packet Level Restart timer, in seconds.

Reset timer T22 (sec)  The Reset Supervision timer, in seconds.

Call timer T21 (sec)  The Call Supervision timer, in seconds.

Clear timer T23 (sec)  This Clear Supervision timer, in seconds.

Idle timer (sec)  The Idle Connection timer, in seconds.

Acknowledgment timer (msec)  This is the Acknowledgment timer, in milliseconds. If the application sends no data for the duration of this timer, then WAN Services sends a Window Update.

Two-way VCs configured  The total number of Two-way Virtual Circuits (TVC) configured in the WAN Services Configuration program.

Permanent VCs configured  The total number of Permanent Virtual Circuits (PVC) configured in the WAN Services Configuration program.

In-coming VCs configured  The total number of Incoming Virtual Circuits (IVC) configured in the WAN Services Configuration program.

Out-going VCs configured  The total number of Out-going Virtual Circuits (OVC) configured in theWAN Services Configuration program.

Trace  Indicates whether this protocol is currently being traced using ECMODULE TRACE.

Trace buffer size (bytes)  The size of the trace buffer.

Trace filter (hex)  The trace filter lets you tailor the trace to examine certain groups of elements within the data stream. The trace filter is one byte long, with each bit filtering a specific type of protocol element. When you filter an element, you hide everything but that element. The trace filter is specified as a two-digit hexadecimal number. For more information, see the “The Trace Filter” section later in this chapter.

Trace entry size (bytes)  This configures Trace to examine only the first n bytes of each frame or packet traced. If you have a Trace Entry Size of 32 bytes, then only the first 32 bytes of each frame or packet is loaded into the trace buffer.

Link activated at  The time and date when the X.25 port was activated.

Last restart  The time and date when the X.25 port was last reset.

VC  The Virtual Circuit number of the Virtual Circuit being monitored.

Local Address  The X.25 DTE Address of the Eicon Technology WAN Services PC for the circuit.

Remote Address  The X.25 DTE Address of the remote computer for the virtual circuit.

Type  Type of Virtual Circuit in use.

Value	Description
Permanent	Permanent, leased circuit.
Incoming only	Circuit for receiving calls only.
Outgoing only	Circuit for originating calls only.
Two-way	Circuit for receiving and originating calls.

Status  The current status of the specified X25 port.

Value	Description
Pkt CLS	Closed
DTE Restart	The Eicon WAN Services PC has sent a Restart Request packet.
DCE Restart	Restart indication packet was received.
Packet Ready	Virtual circuit is disconnected.
DTE Call	Outgoing Call Request was sent.
DCE Call	A Call Indication packet was received.
Call Collision	X.25 call collision.
Circuit Ready	X.25 virtual circuit is  established.
DTE Clear	A Clear Request packet was sent.
DCE Clear	A Clear Indication packet was received. Remote requested termination of virtual circuit.
DTE Reset	The virtual circuit is locally reset.
DCE Reset	Remote reset the virtual circuit.


Chapter 10: Using ECMODULE

X.25 Status

Detail Status Fields

Port number  The number of the EiconCard port being monitored.

Port name  The name of the EiconCard port being monitored.

Transmit Receive Window size  The number of packets that can be sent before waiting for an acknowledgment. Both Receive and Transmit values are shown. They are usually the same (symmetrical), but could be different.

Packet size (bytes)  The size of the transmit and receive X.25 data packets, in bytes. They are usually the same (symmetrical), but could be different.

Last reset  The time and date when the connection was last reset.

X.25 Call user facilities  Call user facilities are optional network services that provide features such as reverse charging, access to a Closed User Group, or specification of a Network User Identification. The call user facility field can contain up to 63 bytes.

X.25 Call user data  Call user data can be used to request services specific to the host you are calling, such as a password, or to indicate your Protocol ID code. The call user data field can contain up to 10 bytes. The display shows both a “dump” format (see left column) and the ASCII equivalent (see right-hand column).

Trace  Indicates whether this protocol is currently being traced using ECMODULE TRACE.

Trace buffer size (bytes)  The size of the trace buffer.

Trace filter (hex)  The trace filter lets you tailor the trace to examine certain groups of elements within the data stream. The trace filter is one byte long, with each bit filtering a specific type of protocol element. When you filter an element, you hide everything but that element. The trace filter is specified as a two-digit hexadecimal number. For more information, see the “The Trace Filter” section later in this chapter.

Trace entry size (bytes)  This configures Trace to only examine the first n bytes of each frame or packet traced. If you have a Trace Entry Size of 32 bytes, then only the first 32 bytes of each frame or packet is loaded into the trace buffer.

VC  The Virtual Circuit number of the Virtual Circuit being monitored.

Local Address  The X.25 DTE Address of the Eicon Technology WAN Services PC for the virtual circuit.

Remote Address  The X.25 DTE Address of the remote computer for the virtual circuit.

Type  Type of Virtual Circuit in use.

Value	Description
Permanent	Permanent, leased circuit.
Incoming only	Circuit for receiving calls only.
Outgoing only	Circuit for originating calls only.
Two-way	Circuit for receiving and originating calls.

Status  The current status of the specified X25 port.

Value	Description
Pkt CLS	Closed
DTE Restart	The Eicon WAN Services PC has sent a Restart Request packet.
DCE Restart	Restart indication packet was received.
Packet Ready	Virtual circuit is disconnected.
DTE Call	Outgoing Call Request was sent.
DCE Call	A Call Indication packet was received.
Call Collision	X.25 call collision.
Circuit Ready	X.25 virtual circuit is established.
DTE Clear	A Clear Request packet was sent.
DCE Clear	A Clear Indication packet was received. Remote requested termination of virtual circuit.
DTE Reset	The virtual circuit is locally reset.
DCE Reset	Remote reset the virtual circuit.


Chapter 10: Using ECMODULE

X.25 Statistics

Command	ECMODULE STATS X25 [/Eiconcard n][/Connection n]

When you issue the command ECMODULE STATS X25 on an Eicon Technology WAN Services PC with an active X.25 module, then statistical information is displayed.

The following command can be used to examine specific port statistics of an Eicon Technology WAN Services PC with an active X.25 module:

[C:\EICON]ECMODULE STATS X25 /P 1

X.25 Loadable Module Statistics

Port number: 1                Port name:

                     Sent      Received                     Sent      Received
Call      request..: 30                 Data Packets......: 223       246
          confirm..: 0         3        Data Segments.....: 223       311
Restart   request..: 1         0        Characters........: 4019      8596
          confirm..: 0         1        Receiver ready....: 146       126
Register  request..: 0         0        Receiver not ready: 0         0
          confirm..: 0         0        Diagnostic packets: 0         0
Clear     request..: 0         2        Unknown packets...: 0         0
          confirm..: 2         0        Rejects...........: 0         0
Reset     request..: 0         0
          confirm..: 0         0
Interrupt request..: 0         0
          confirm..: 0         0

You may also obtain detailed statistical information by issuing this command:

[C:\EICON]ECMODULE STATS X25 /P 1 /C 16

X.25 Loadable Module Statistics
Port number: 01                      Port name:

Virtual Circuit....: 16

                     Sent      Received                     Sent      Received
Call      request..: 20        0        Data packets......: 26613     98781
          Confirm..: 0         20       Data segments.....: 26613     164826
Restart   request..: 0         0        Characters........: 479509   8483480
          Confirm..: 0         0        Receiver Ready....: 78562     16330
Register  request..: 0         0        Receiver Not Ready: 0         0
          Confirm..: 0         0        Diagnostic packets: 0         0
Clear     request..: 0         19       Unknown packets...: 0         0
          Confirm..: 19        0        Rejects...........: 0         0
Reset     request..: 0         10
          Confirm..: 10        0
Interrupt request..: 0         0
          Confirm. .: 0        0

Global and Detail Statistics Fields


Chapter 10: Using ECMODULE

X.25 Statistics

Global and Detail Statistics Fields

Call Request  The number of requests to establish a connection.

Call Confirm  The number of acknowledged requests for a connection.

Virtual Circuit  The X.25 VC connection number.

Data Packets  The number of data packets transmitted and received.

Data Segments  The number of 64 bytes data blocks sent and received.

Restart Request  The number of requests to restart the packet level connection sent and received.

Restart Confirm  The number of acknowledged requests for a packet level connection.

Characters  The number of characters transmitted and received.

Receiver ready  The number of RR flow control packets sent and received.

Register Request  The number of register packets sent or received. Register packets are used to exchange registration information.

Register Confirm  The number of acknowledged register packets sent or received.

Receiver not ready  The number of times the receiver has not been ready for the incoming packet.

Diagnostic packets  The number of error information packets sent and received.

Clear Request  The number of requests to terminate a Virtual Circuit sent and received.

Clear Confirm  The number of acknowledged requests for a Virtual Circuit termination.

Unknown packets  The number of packets that could not be recognized as following the X.25 structure sent and received.

Rejects  The number of times a packet has been rejected.

Reset Request  The number of reset packets sent or received.

Reset Confirm  The number of acknowledged requests for reset packets sent or received.

Interrupt Request  The number of Interrupt packets, which are packets which go ahead of other normal packets, sent and received.

Interrupt Confirm  The number of acknowledged requests for Interrupt packets sent or received.


Chapter 10: Using ECMODULE

Analyzing Data: ECMODULE TRACE

Command	ECMODULE TRACE option  [/Filter f] [/REset] [/Block b] [/Size n] [/Truncate n] [/EBcdic]

The ECMODULE TRACE function can be an essential tool for the data communications expert. In most cases, you will use ECMODULE TRACE with the guidance of an Eicon Technology representative.

The following command shows trace data on an X.25 connection:

[C:\EICON]ECMODULE TRACE X25 /T 256

X.25 Loadable Module Trace
Port number: 01                      Port name:

X.25 Trace. Size = 8192  Length = 512   Block = 14    Mask = FF
BLK   DAY-HH:MM:SS:MSEC
2     000-16:36:00.365 TX CALL REQ                     0F 0B    Data =  18                	      52 15 10 00 00 00 C3 01 00 00 F3 F2 F0 F4 40 40  R.............@@       	      40 40                                            @@
3     000-16:36:00.525 RX CLEAR IND                    0F 13    Data =   2       	      00 EC                                            ..
4     000-16:36:00.663 TX CLEAR CNF                    0F 17    Data =   0
5     000-16:36:01.563 TX CALL REQ                     10 0B    Data =  20       	      A2 15 10 10 10 10 10 00 C3 01 00 00 F3 F2 F0 F5  ................       	      40 40 40 40                                      @@@@
6     000-16:36:01.615 RX CLEAR IND                    10 13    Data =   2       	      00 EC                                            ..
7     000-16:36:01.763 TX CLEAR CNF                    10 17    Data =   0
8     000-16:36:03.463 TX CALL REQ                     10 0B    Data =  19       	      82 15 10 10 10 10 00 C3 01 00 00 F3 F2 F0 F6 40  ...............@       	      40 40 40                                         @@@
9     000-16:36:03.465 TX CALL REQ                     0F 0B    Data =  19       	      72 15 10 01 00 10 00 C3 01 00 00 F3 F2 F0 F2 40  r..............@       	      40 40 40                                         @@@
10    000-16:36:03.605 RX CLEAR IND                    10 13    Data =   2         	      00 EC                                            ..
11    000-16:36:03.680 TX CLEAR CNF                    10 17    Data =   0 12    000-16:36:03.683 RX CLEAR IND                    0F 13    Data =   2       	      00 EC                                            ..
13    000-16:36:03.863 TX CLEAR CNF                    0F 17    Data =   0 14    000-16:36:20.363 TX CALL REQ                     10 0B    Data =  19       	      72 15 10 10 10 10 00 C3 01 00 00 F3 F2 F0 F1 40  r..............@       	      40 40 40                                         @@@
15    000-16:36:20.425 RX CLEAR IND                    10 13    Data =   2       	      00 EC                                            ..
16    000-16:36:20.567 TX CLEAR CNF                    10 17    Data =   0        	      00 EC                                            ..
Command Completed Successfully.

The Trace Buffer

The Trace Filter

Sample ECMODULETRACE Commands


Chapter 10: Using ECMODULE

Analyzing Data: ECMODULE TRACE

The Trace Buffer

Multiple trace buffers may be active at the same time for different port or connection numbers. The amount of available memory on your EiconCard limits the number of traces you can have active. Each time you start a trace ECMODULE TRACE sets aside a new trace buffer (default size 2048 bytes) on the EiconCard.

Blocks and Protocol Elements

Information in the trace buffer is stored in blocks, each block being based on a protocol element. ECMODULE TRACE creates a block by extracting the first n bytes, as indicated by the /Truncate parameter, from each protocol element in the data stream.

Protocol	Protocol Element
Frame Relay	Frame
HDLC	Frame
LAPD	Frame
PPP	Packet
Q931	Message
SDLC	Frame
TRANSPORTISO / TRANPORTTGX	TPDU
X.25	Packet
Changing the Trace Buffer Size

The trace must be stopped before the buffer size can be changed. Use the command ECMODULE TRACE /SIZE n, where n is the buffer size. A size of 0 stops the trace.


Chapter 10: Using ECMODULE

Analyzing Data: ECMODULE TRACE

The Trace Filter

The trace filter lets you tailor the trace to examine certain groups of elements within the data stream. The trace filter is one byte long, with each bit filtering a specific type of protocol element. When you filter an element, you hide everything but that element. The filter is specified as a two-digit hexadecimal number.

Protocol	Filter	Description
Frame Relay	01h	DATA_FRAMES
	02h	LMI_FRAMES
HDLC Frame	01h	I-frames
	02h	RR frames
	04h	RNR, REJ frames
	08h	FRMR, SABM, DISC, UA frames
	10h	All other frames
PPP	01h	IP Packets
	02h	IPX Packets
	04h	AT Packets
	10h	LCP Packets
	20h	PAP Packets
	40h	LQR Packets
	80h	CHAP Packets
SDLC	01h	I Frames
	02h	RR Frames
	04h	RNR and REJ Frames
	08h	FRMR, SABM, DISC, UA, and DM Frames
	10h	XID and all other Frames
TRANSPORTISO / TRANSPORTTGX	01h	CR, CC, DR, and DC TPDUs
	02h	DT and ED TPDUs
	04h	AK and EA TPDUs
	08h	ER and REJ TPDUs
X.25 Packet	01h	Data packets
	02h	RR, RNR packets
	04h	RESET, INTERRUPT packets
	08h	CALL, CLEAR packets
	10h	All other packets
Note:
There are no TRACE Filters available for the LAPD and Q931 protocols.

Easy Mask Change

The easiest way to change the trace mask is to always clear the mask before setting a new mask. The command:

ECMODULE TRACE /F FFnn

does this. Replace nn with the value of the new mask(s). For example:

ECMODULE TRACE /F FF03

To trace all elements use this command:

ECMODULE TRACE /F FFFF

To trace more than one type of protocol element, you can create a composite filter by adding together the filter value for each individual element. For example, with the X.25 protocol, to trace both RR/RNR and CALL/CLEAR packets, add their individual hexadecimal filters together. 02h + 08h = 0A:

ECMODULE TRACE X25 /F FFOA


Chapter 10: Using ECMODULE

Sample ECMODULE TRACE Commands

Here are some examples of ECMODULE TRACE with different command line parameters:

ECMODULE TRACE X25 /P 2

Displays trace information on the X.25 protocol on port #2.

ECMODULE TRACE HDLC /P 4 /S 4096

Traces the HDLC protocol, on port #4, with a trace buffer size of 4096 bytes.

ECMODULE TRACE X25 /P 2 /F FF01

Displays only the data packets from an X.25 trace on port #2.

ECMODULE TRACE HDLC /P 2 /F FF03

Displays only the I and RR frames from the trace of the HDLC protocol on port #2. In this command the filter is set to hexadecimal 03 to display only the I and RR frames. The trace filter mask for I is hexadecimal 01, and for RR is hexadecimal 02, so to display both you add the masks together to get hexadecimal 03.

ECMODULE TRACE /R

Clears and resets the trace buffer.

ECMODULE TRACE X25 /P 3 /S 0

Ends the trace of the X.25 protocol on port #3.

ECMODULE TRACE FRELAY /P 2

Traces the communications data streaming through a Frame Relay connection on port #2.

ECMODULE TRACE FRELAY /C 3 /P 4

Traces the Frame Relay connection #3, on port #4, of a the server.

ECMODULE TRACE PPP /P 1

Traces the communications data streaming through a PPP connection on port #1.


Chapter 11: The MPR.INI Initialization File

This chapter explains how the MPR Start Initialization File is organized, and defines the parameters that appear in it.

About MPR.INI

Sample MPR.INI File

Sample MPR.INI Entries for Other Protocols

MPR.INI Parameters

Circuit Entry Parameters

Mapper Entry Parameters


Chapter 11: The MPR.INI Initialization File

About MPR.INI

Each time you use the command line utilities or the WAN Services Configuration program to create a circuit and map it to a remote IP address, the configuration information you specify is saved in the MPR.INI initialization file. When you use IPMAP to map a circuit to a remote IP address, this information is also saved in MPR.INI. The next time MPR START is run, the circuit and mapping information is read from MPR.INI, and the circuit is automatically started.

The MPR.INI file is divided into two sections: Circuit Entry, which contains parameters defined by MPRCCT, and Mapper Entry, which contains parameters defined by IPMAP.

You can edit MPR.INI directly using an ASCII text editor. The WAN Services Configuration program and the command-line utilities can also modify MPR.INI.

Note:
Do not edit MPR.INI while IP Routing Services is active.

The AUTO_START parameter is set by default to Y for yes, and so each time you run MPR START, all the circuit and mapping entries defined in MPR.INI are automatically activated.

Sample MPR.INI File

Sample MPR.INI Entries for Other Protocols


Chapter 11: The MPR.INI Initialization File

About MPR.INI

Sample MPR.INI File

This section shows a sample MPR.INI file used by the WAN Services system located in LAN 1, in the diagram below.

This MPR.INI file shows two sample circuits needed for the WAN Services system in LAN 1 to connect to the WAN Services systems in LAN 2 and LAN 3.

; this circuit entry is for the connection to the WAN
; Services PC located in LAN 2 in the diagram

[CIRCUIT_ENTRY\ROUTER1_2]
Directory_Entry_Comment=Entry added by the Command Line Utility.
    Connection_ID=1
    Auto_Start=Y
    Connection_Type=TWOWAY
    Data_Compression=N
    Eicon_Port=1
    Inactivity_Timeout=60
    Number_Of_Retries=0
    Retry_Delay=5
    Lan_Protocol=IP
    Wan_Protocol=X25_SVC
    X25_Local_DTE=01
    X25_Remote_DTE=02
    Connection_Usage=Primary

[MAPPER_ENTRY\192.100.100.2]
    Circuit_Name=ROUTER1_2
    Broadcast=Y

; this circuit entry is for the connection to the WAN
; Services PC located in LAN 3 in the diagram

[CIRCUIT_ENTRY\ROUTER1_3]
Directory_Entry_Comment=Entry added by the Command Line Utility.
    Connection_ID=2
    Auto_Start=Y
    Connection_Type=TWOWAY
    Data_Compression=N
    Eicon_Port=1
    Inactivity_Timeout=60
    Number_Of_Retries=0
    Retry_Delay=5
    Lan_Protocol=IP
    Wan_Protocol=X25_SVC
    X25_Local_DTE=01
    X25_Remote_DTE=03
    Connection_Usage=Primary

[MAPPER_ENTRY\192.100.100.3]
    Circuit_Name=router1_3
    Broadcast=Y


Chapter 11: The MPR.INI Initialization File

About MPR.INI

Sample MPR.INI Entries for Other Protocols

[CIRCUIT_ENTRY\FRAME_CIRCUIT]
     Directory_Entry_Comment=Added by MPRCCT utility.
     Connection_ID=2
     Auto_Start=Y
     Connection_Type=Outgoing
     Data_Compression=Y
     Eicon_Port=1
     Lan_Protocol=IP
     Wan_Protocol=FRAME_RELAY
     FR_DLCI=16

[CIRCUIT_ENTRY\PPP_CIRCUIT]
     Directory_Entry_Comment=Added by MPRCCT utility.
     Connection_ID=4
     Auto_Start=Y
     Connection_Type=Outgoing
     Data_Compression=Y
     Lan_Protocol=IP
     Eicon_Port=1
     Wan_Protocol=PPP


Chapter 11: The MPR.INI Initialization File

MPR.INI Parameters

This section presents all the MPR.INI parameters and their syntax.

Circuit Entry Parameters

Mapper Entry Parameters


Chapter 11: The MPR.INI Initialization File

MPR.INI Parameters

Circuit Entry Parameters

[CIRCUIT_ENTRY\name]  This indicates the beginning of a circuit parameters section of MPR.INI, where name is the name of the circuit being defined.

Auto_start  Sets whether the router-to-router connection is activated immediately upon running the MPR START command.

Value	Description
Y	Automatically starts the router connection.
N	Does not automatically start the router connection.

Connection_ID  This parameter is controlled by the WAN Services software, and should not be modified.

Connection_Type  Sets whether the X.25 connection is being made through an incoming only, out-going, or two-way virtual X.25 circuit.

Value	Description
INCOMING	Incoming virtual X.25 circuit.
TWOWAY	Two-way X.25 virtual circuit.
OUTGOING	Outgoing X.25 SVC or X.25 PVC, Frame Relay, or PPP connection.

Data_Compression  Specifies whether the software-based compression is active or inactive. This requires an Eicon Technology router at both ends of the connection.

Value	Description
Y	Enables data compression.
N	Disables data compression.

Directory_Entry_Comment  A comment about the circuit. The default comment is "Added by MPRCCT utility."

Value	Description
0 - 80 ASCII characters	Short comment about the circuit.

Eicon_Port  Sets the port on the EiconCard through which the router connection circuit is being made.

Value	Description
1 - 16	The EiconCard port being used by this circuit.

FR_DLCI  Frame Relay connections only. Specifies the Frame Relay DLCI that the circuit is to use. This number is assigned to your Frame Relay connection when you purchase the subscription.

Value	Description
16 - 1007	DLCI to be used by the circuit.

Inactivity_Timeout  Sets the amount of time the router waits before disconnecting an inactive switched Virtual Circuit.

Value	Description
0 - 86400	Number of seconds to wait before disconnection of a switched Virtual Circuit. Setting this to 0 means there is no timeout.

Lan_Protocol  Sets the LAN protocol to be used by the circuit. Only TCP/IP is supported: entering any other value causes an error.

Value	Description
IP	Only TCP/IP LAN Protocol is supported.

Number_of_Retries  Specifies the number of times the router tries to make a connection to a remote router.

Value	Description
0 - 100	Number of connection attempts to be made to the remote router before the effort is abandoned.

Retry_Delay  Sets the amount of time, in seconds, the router waits between retries when attempting to make a connection to a remote router.

Value	Description
5 - 65536	Number of seconds between connection attempts.

X25_Calling_ Facilities  X.25 SVC connections only. Specified by the local router, Calling Facilities are optional network services that provide features such as reverse charging or access to a Closed User Group. For more information, see Appendix C, "User Facilities and DTE Address Structure."

Value	Description
up to 109 ASCII characters	Entry for optional network services specified by the local router.

X25_Listening_Facilities  X.25 SVC connections only. Specified by the remote router, Listening Facilities are optional network services that provide features such as reverse charging, or access to a Closed User Group. For more information, see Appendix C, "User Facilities and DTE Address Structure."

Value	Description
up to 109 ASCII characters	Entry for optional network services specified by the remote router.

X25_Local_DTE  Specifies your DTE address on the X.25 network.

Value	Description
1 to 17 digits long	X.25 DTE address of the local router.

X25_PVC  X.25 PVC connections only. Specifies the PVC circuit you want to use to connect to the remote router. The number of PVCs available depends on your X.25 network subscription, and on the Number of PVCs parameter on the X.25 configuration panel of the WAN Services Configuration program.

Value	Description
1 - 64	PVC that the specified router Circuit will use.

X25_Remote_DTE  Sets the DTE address on the X.25 network of the router to which you want to connect.

Value	Description
1 to 17 digits long	X.25 DTE address of the remote router.

X25_User_Data  X.25 SVC connections only. User Data can be used to request services specific to the host you are calling, such as a password, or to indicate your Protocol ID code.

Value	Description
up to 128 ASCII characters	Request for services specific to the host, like a password.

WAN_Protocol  Indicates the type of Wide Area Network (WAN) protocol to be used on the connection between the local and remote routers.

Value	Description
X25_SVC	X.25 protocol on a Switched Virtual Circuit.
X25_PVC	X.25 protocol on a Permanent Virtual Circuit.
FRAME_RELAY	Frame Relay protocol over a Frame Relay packet-switched network.
PPP	Point-to-Point Protocol connection over a leased or dial-up line.

Connection_Usage  Indicates whether this connection is a primary or backup connection.

Value	Description
Primary	Connection is a primary connection.
Backup	Connection is a backup connection.

Primary_Name  For a backup connection, indicates the name of the primary connection it is backing up.

Value	Description
1-15 characters	Name of the primary circuit for this backup circuit.


Chapter 11: The MPR.INI Initialization File

MPR.INI Parameters

Mapper Entry Parameters

[MAPPER_ENTRY\ipaddress]  This indicates the beginning of a mapping parameters section of MPR.INI, where ipaddress is the IP Address of the remote router.

Circuit_Name  Indicates the name of the circuit on which the mapping should be performed.

Value	Description
1-15 characters	Name of the circuit to be mapped.

Broadcast  Activating this parameter allows you to use applications that rely on protocol broadcasts.

Value	Description
Y	Enables IP broadcasts on the circuit.
N	Disables IP broadcasts on the circuit.


Appendix A: Modemless Connections and Cables

This appendix contains instructions for making null-modem connections between two WAN Services PCs, as well as diagrams showing the wiring and signals for each cable.

Connecting Two WAN Services PCs

Establishing Contact

X.25 Back-to-Back Connection

PPP Back-to-Back Connection

Frame Relay Back-to-Back Connection

Modem and Null-Modem Cables

Null-Modem Cables

Modem Cables

Testing Cables


Appendix A: Modemless Connections and Cables

Connecting Two WAN Services PCs

This section describes how to connect two Eicon Technology WAN Services PCs back-to-back using a null-modem cable. A null-modem cable can be used to connect EiconCards in either stand-alone or LAN-based routers. Depending on the types of EiconCards you are linking, cable requirements vary. Match the correct cable to the EiconCards you want to link.

Note:
WAN Services for Windows NT has been tested with the following EiconCards: DPNA/PC, EC/PC, HSI/PC, IMC/PC, MPNA/PC, EC/MC, HSI/MC, MPNA/MC, and EiconCard S51.

Establishing Contact

X.25 Back-to-Back Connections

PPP Back-to-Back Connection

Frame Relay Back-to-Back Connection


Appendix A: Modemless Connections and Cables

Connecting Two WAN Services PCs

Establishing Contact

The IP router software portion of WAN Services for Windows NT is able to make back-to-back null modem connections using X.25. You can even activate compression on both ends to test that function. Following is information on how to make each type of link.


Appendix A: Modemless Connections and Cables

Connecting Two WAN Services PCs

X.25 Back-to-Back Connection

The diagram below summarizes the proper configuration of hardware and software for an X.25 null-modem connection.

To make a back-to-back X.25/HDLC connection using a null-modem cable, perform the following steps.

1.	Install all the necessary hardware and software onto the two WAN Services PCs, including TCP/IP.

2.	Connect WAN Services A to WAN Services B using a null-modem cable. It does not matter which computer you select as A or B.

Note:
Make sure that the Packet Size, Window Size, and the number of TVCs match on both ends. This can be verified by running the Windows-based WAN Services Configuration program on WAN Services A and B. Match the X.25 configuration values and the HDLC configuration values on the two WAN Services PCs.

3.	On WAN Services PC A, run the WAN Services Configuration program as described in Chapter Three, "Configuration."

4.	Go to the Sync Driver Configuration panel and set the Clocking parameter to Internal.

Note:
When using an X.21 HSI Null-Modem Cable (300-032) to connect two EiconCards be sure to set both ends to NRZI encoding and the line speed to 19.2 kbps or less.

5.	Go to the HDLC Configuration panel and set DTE/DCE Addressing to DCE.

6.	Save the changes you have made and exit the WAN Services Configuration program.

Important:
You must reload the EiconCard for any changes you have made in the WAN Services Configuration program to take effect. Rebooting your system is not required if no changes to the EiconCard hardware configuration parameters (IRQ, I/O port, or memory address) were made.

7.	Run the WAN Services Configuration program on WAN Services B.

8.	Go to the Sync Driver Configuration panel and set the Clocking parameter to External.

9.	Go to the HDLC Configuration panel and set the DTE/DCE Addressing parameter to DTE.

10. Save the changes you have made, and exit the WAN Services Configuration program. Rebooting your system is not required since no changes to the EiconCard configuration parameters were made.

Note:
You must reload the EiconCard for any changes you have made in the WAN Services Configuration program to take effect. Rebooting your system is not required if no changes to the EiconCard hardware configuration parameters (IRQ, I/O port, or memory address) were made.

11. Run the MPR STATS and ECCARD STATUS commands to ensure that your router and EiconCard are started. Make certain TCP/IP is active on WAN Services A and start the Eicon Technology WAN Services for Windows NT hardware and software with these commands:

MPRCCT ADD X25 WANServicesPC-B /A 1234 /L 5678
IPMAP ADD WANServicesPC-B xxx.xxx.xxx.xxx

Replace xxx.xxx.xxx.xxx with the IP address of WAN Services PC B. This is the address you specified in the Network applet in Control Panel when you installed and configured WAN Services.

Note:
The IP addresses on the two WAN Services PCs must belong to the same network or subnetwork.

12. Run the MPR STATS and ECCARD STATUS commands to ensure that your router and EiconCard are started. Make sure TCP/IP is active on WAN Services B. Ensure that the router and EiconCard are already started. Then, start the Eicon Technology WAN Services for Windows NT hardware and software with these commands:

MPRCCT ADD X25 WANServicesPC-A /A 5678 /L 1234
IPMAP ADD WANServicesPC-A yyy.yyy.yyy.yyy

Replace yyy.yyy.yyy.yyy with the IP address of WAN Services PC A. This is the address you specified in the Network applet in Control Panel when you installed and configured the WAN Services PC.

Note:
The IP addresses on the two WAN Services systems must belong to the same network or subnetwork.

13. If you receive the error message "Modem Not Ready" you may have the two ends of the null-modem cable reversed. Unplug the cable and reverse the ends. This error may also be caused by a damaged cable. See "Testing Cables," for more information.

14. Check the status of each WAN Services PC by issuing MPR STATS and MPRCCT status commands.

15. Use the TCP/IP command PING to test the connection.

16. You can issue commands on the remote WAN Services PC by using TELNET which is part of Windows NT TCP/IP.


Appendix A: Modemless Connections and Cables

Connecting Two WAN Services PCs

PPP Back-to-Back Connection

The diagram below summarizes the proper configuration of hardware and software for a Point-to-Point Protocol (PPP) null-modem connection.

To make a back-to-back Point-to-Point Protocol (PPP) connection using a null-modem cable, perform the following steps.

1.	Install all the necessary hardware and software, including TCP/IP, onto the two WAN Services PCs.

2.	Connect WAN Services A to WAN Services B using a null-modem cable. It does not matter which computer you select as A or B.

3.	Run the WAN Services Configuration program on WAN Services PC A. See Chapter Three, "Configuration," for more detailed information.

4.	Go to the Sync Driver Configuration panel and set the Clocking parameter to Internal.

Note:
When using an X.21 HSI Null-Modem Cable (300-032) to connect two EiconCards be sure to set both ends to NRZI encoding, internal clocking, and the line speed to 19.2 kbps or less.

5.	Go to the PPP Configuration panel and make a note of the parameter settings. PPP settings must be identical on WAN Services PC A and WAN Services PC B for the back-to-back connection to work.

6.	Save any changes and exit the WAN Services Configuration program.

Note:
You must restart all EiconCards installed in the WAN Services PC for any changes you have made in the WAN Services Configuration program to take effect. Rebooting your system is not required if no changes to the EiconCard configuration parameters were made.

7.	Run the WAN Services Configuration program on WAN Services B.

8.	Go to the PPP Configuration panel, and make sure the PPP settings are identical on WAN Services A and WAN Services B.

9.	Go to the Sync Driver Configuration panel and set the Clocking parameter to Internal.

10. Save any changes and exit the WAN Services Configuration program.

Note:	You must restart all EiconCards installed in the WAN Services PC for any changes you have made in the WAN Services Configuration program to take effect. Rebooting your system is not required if no changes to the EiconCard configuration parameters were made.

11. Run the MPR STATS and ECCARD STATUS commands to ensure that your router and EiconCard are started. Go to WAN Services A and start WAN Services with these commands:

MPRCCT ADD PPP WANServicesPC-B
IPMAP ADD WANServicesPC-B xxx.xxx.xxx.xxx

Replace xxx.xxx.xxx.xxx with the IP address of WAN Services B. This is the address you specified in the Network applet in Control Panel when you installed and configured the WAN Services PC.

Note:
The IP addresses on the two WAN Services must belong to the same network or subnetwork.

12. Run the MPR STATS and ECCARD STATUS commands to ensure that your router and EiconCard are started. Go to the WAN Services B and start WAN Services with these commands:

MPRCCT ADD PPP WANServicesPC-A
IPMAP ADD WANServicesPC-A yyy.yyy.yyy.yyy

Replace yyy.yyy.yyy.yyy with the IP address of WAN Services A. This is the address you specified in the Network applet in Control Panel when you installed and configured the WAN Services PC.

Note:
The IP addresses on the two WAN Services PCs must belong to the same network or subnetwork.

13. If you receive the error message "Modem Not Ready" you may have the two ends of the null-modem cable reversed. Unplug the cable and reverse the ends. This error may also be caused by a damaged cable. See "Testing Cables," for more information.

14. Check the status of the WAN Services PC by issuing the MPR STATS and MPR STATUS commands.

15. Use the TCP/IP command PING to test the connection.

16. You can issue commands on the remote WAN Services PC by using TELNET, which is part of Windows NT TCP/IP.


Appendix A: Modemless Connections and Cables

Connecting Two WAN Services PCs

Frame Relay Back-to-Back Connection

The diagram below summarizes the proper configuration of hardware and software for a Frame Relay null-modem connection.

To make a back-to-back Frame Relay connection using a null-modem cable, perform the following steps.

1.	Install all the necessary hardware and software onto the two WAN Services PCs, including TCP/IP.

2.	Connect WAN Services A to WAN Services B using a null-modem cable. It does not matter which computer you select as A or B.

3.	Run the WAN Services Configuration program on WAN Services PC A. See For more information, see Chapter 3, "WAN Services Configuration."

4.	Go to the Sync Driver Configuration panel and set the Clocking parameter to Internal.

Note:
When using an X.21 HSI Null-Modem Cable (300-032) to connect two EiconCards be sure to set both ends to NRZI encoding and the line speed to 19.2 kbps or less.

5.	Go to the Frame Relay Configuration panel. Make sure that the value of the Information Field Size [dN1] (octets) parameter is 1514, and that Local Management Interface Protocol parameter is set to ANNEX.D. All Frame Relay settings must be identical on WAN Services PC A and WAN Services PC B for the back-to-back connection to work.

6.	Save the changes you have made, and exit the WAN Services Configuration program.

Note:
You must restart all EiconCards installed in the WAN Services PC for any changes you have made in the WAN Services Configuration program to take effect. Rebooting your system is not required if no changes to the EiconCard configuration parameters were made.

7.	Run the WAN Services Configuration program on WAN Services B.

8.	Go to the Sync Driver Configuration panel and set the Clocking parameter to External.

9.	Go to the Frame Relay Configuration panel. Make sure that the value of the Information Field Size [dN1] (octets) parameter is 1514, and that Local Management Interface Protocol parameter is set to ANNEX.D. All Frame Relay settings must be identical on WAN Services B and WAN Services PC A for the back-to-back connection to work.

10.Save the changes you have made and exit the WAN Services Configuration program.

Note:	You must reload the EiconCard for any changes you have made in the WAN Services Configuration program to take effect. Rebooting your system is not required if no changes to the EiconCard configuration parameters were made.

11. Run the MPR STATS and ECCARD STATUS commands to ensure that your router and EiconCard are started. Go to WAN Services A and start WAN Services with this command:

MPRCCT ADD FRBS WANServicesPC-B /DLCI 1007

You do not need to use the IPMAP command for Frame Relay connections.

12. Run the MPR STATS and ECCARD STATUS commands to ensure that your router and EiconCard are started. Go to WAN Services B and start WAN Services with these commands:

MPRCCT ADD FRBS WANServicesPC-A /DLCI 1007

Note:
The DLCI number must be the same on both ends.

13. If you receive the error message "Modem Not Ready" you may have the two ends of the null-modem cable reversed. Unplug the cable and reverse the ends. This error may also be caused by a damaged cable. See "Testing Cables," for more information.

14. Check the status of the WAN Services PC by issuing an MPR STATS and ECCARD STATUS commands.

15. Use the TCP/IP command PING to test the connection.

16. You can issue commands on the remote WAN Services PC by using TELNET, which is part of Windows NT TCP/IP.


Appendix A: Modemless Connections and Cables

Modem and Null-Modem Cables

This section contains information on all the Eicon Technology null-modem and modem cables, including diagrams of the pin-outs.

Null-Modem

Modem Cables

All cables for the EiconCard and the EiconCard HSI are shown in the table below.

Cable Name	Part Number
V.24 Modem Cable	300-007
V.24 Null-Modem Cable	300-022
V.35 HSI Modem Cable	300-024
X.21 HSI Modem Cable	300-025
V.24 HSI Modem Cable	300-026
V.24/V.35 HSI Null-Modem Cable	300-031
X.21 HSI Null-Modem Cable	300-032
HSI Null-Modem Conversion Cable	300-033
HSI/V.24 Converter	300-046
AS/400 V.35/HSI Null Modem Cable	300-047
ISDN S/T1 Interface Cable	810-015

These cables may be ordered from your Eicon Technology supplier

Note:
Not all cables are symmetrical: both ends of a cable are not necessarily identical.


Appendix A: Modemless Connections and Cables

Modem and Null-Modem Cables

Null-Modem Cables

This section contains the pin-out diagrams for various null-modem cables. Here is a list of what these cables do:

•	The V.24 Null-modem Cable connects an EiconCard to another EiconCard, using an V.24 interface

•	The X.21 HSI Null-modem Cable connects an EiconCard HSI to another EiconCard HSI, using an X.21 interface

•	When using the X.21 HSI Null-modem Cable to connect two EiconCards, be sure to set both ends to NRZI encoding, Internal Clocking, and the line speed to 19.2 kbps or less

•	The V.24/V.35 HSI Null-modem Cable connects an EiconCard HSI to another EiconCard HSI, using a V.24 or V.35 interface

•	The HSI Null-Modem Conversion Cable connects an EiconCard HSI to an HSI Modem Cable connector

All connectors specified in the diagrams must have shielded ground. Small boxes around the wires denote a twisted pair.


Appendix A: Modemless Connections and Cables

Modem and Null-Modem Cables

Modem Cables

This section contains the pin-out diagrams for various Modem Cables. Here is a list of what these cables do:

•	The V.24 Modem Cable connects the EiconCard to a modem.

•	The X.21 HSI Modem Cable connects an EiconCard HSI to an X.21 modem.

•	The V.24 HSI Modem Cable connects an EiconCard HSI to a V.24 modem.

•	The V.35 HSI Modem Cable connects an EiconCard HSI to a V.35 modem.

•	The HSI/V.24 Converter makes an HSI port look like a regular V.24 port.

Note:
All connectors specified in the diagrams must have a shielded ground. Small boxes around the wires denote a twisted pair. The V.24 Modem Cable, the V.24 HSI Modem Cable, and the HSI/V.24 Converter are fully symmetrical.

For complete wiring diagrams, please contact your Eicon Technology representative.


Appendix A: Modemless Connections and Cables

Error! Bookmark not defined.Testing Cables

Eicon Technology thoroughly tests its modem and null-modem cables, assuring you of the highest quality product. Yet defects do occur. If there is a problem with a cable, then you can test it using the following technique:

1.	Obtain an ohmmeter.

2.	Disconnect both ends of the cable.

3.	Using the pin-out diagrams as a guide, test each connection to make sure that there is no resistance between connected pins. No resistance indicates a good connection. In the following example, pin 16 is connected to pin 24.

If there is a problem with the cable, contact your Eicon Technology representative.


Appendix B: Performance Optimization

This appendix presents performance statistics for all EiconCards, and offers guidelines for optimizing performance. This will let you choose the EiconCard that will take full advantage of the bandwidth of your line, and maximize packet switching capability given practical LAN and X.25 line constraints. Modification of X.25 or HDLC parameters is performed with the WAN Services Configuration program.

Line Speeds and Performance

Propagation delay

X.25 Window Size

HDLC Window Size

Buffer and Packet Size


Appendix B: Performance Optimization

Line Speeds and Performance

Although the Eicon Technology WAN Services for Windows NT software lets you adjust network parameters for the best performance, certain restrictions inherent to the network itself can limit throughput. Line speeds in excess of 128 kbps are possible on dedicated lines, but public X.25 data networks may be as slow as 2400 bps. A slow line will be filled well before the EiconCard reaches its transmission capacity.

Note:
To modify the parameters discussed in this section, run the WAN Services Configuration program. If you are unfamiliar with communications protocols, you should not experiment with parameter settings.

Propagation delay

X.25 Window Size

HDLC Window Size

Buffer and Packet Size


Appendix B: Performance Optimization

Line Speeds and Performance

Propagation delay

Propagation delay is a pitfall of public networks. Propagation delay is the time taken for signal transmission, error checking, and queuing between all the nodes in the transmission path. On some links, such as the ones serviced by satellites, round trip transmission time can approach a full second. Large propagation delays are often observed during heavy traffic periods.

Two features of the X.25 protocol work to minimize the impact of propagation delay.

•	X.25 does error checking between intermediary nodes. This allows packets to be transmitted without waiting for end-to-end acknowledgment.

•	X.25's windowing capability increases the number of packets that can be sent before receiving confirmation from the next node in the transmission path.


Appendix B: Performance Optimization

Line Speeds and Performance

X.25 Window Size

Window size designates the packet interval at which information transfer stops while the sending node awaits acknowledgment from the receiver. Windowing allows more than one packet to be transmitted before an acknowledgment is received from the nearest node. X.25 windowing is designed to reduce waiting time for acknowledgments between nodes, as well as end-to-end waiting time.

If the Window Size is 10, then an application can send ten packets before having to wait for an acknowledgment of receipt from the remote computer. Transmission of packets will stop only when the maximum number of packets allowed by the transmit window has been sent, and when no acknowledgment has yet been received from the remote computer.

When the remote computer acknowledges packets quickly enough, packets can flow more or less continuously across the link. An acknowledgment may confirm the reception of several packets.

The EiconCard allows window sizes ranging from 1 to 127 packets. Window size should be increased for networks with larger delays.

Note:
Few public X.25 networks allow clients to use a Window Size greater than 2.

Possible Drawbacks

When packet sizes are small, increasing the size of X.25 windows can increase effective throughput by as much as 20 percent. The ideal window size is one that allows continuous data flow without ever having the window closed waiting for an acknowledgment. However, as the window size increases, so does the amount of data which must be re-transmitted in case of data error. The increased traffic from error recovery with a very large window may outweigh the efficiency gained by reduction of the effect of propagation delay.

Note:
X.25 allows negotiation of Window Size on a connection basis, depending on your subscription to the X.25 network.

Satellite X.25 Networks

If you are transmitting data on an X.25 network that uses satellites, then you may need a larger X.25 window. Satellite networks experience greater delays because signals must travel into orbit and back.


Appendix B: Performance Optimization

Line Speeds and Performance

HDLC Window Size

When modifying X.25 Window Size, you must also consider HDLC Window Size. X.25 packets are contained within HDLC Frames, and you can modify the HDLC Window Size to optimize transmission. If you are having HDLC frames transmitted intermittently, in bursts, or are receiving many RNRs (Receiver Not Ready signals), then you may need to change the HDLC Window Size. Try increasing the HDLC Window Size first. If this is unsuccessful, then try reducing the Window Size. Unfortunately, most X.25 networks do not allow you to greatly modify Window Size.

Note:
The DTE and the DCE must have the same Window Size when the remotes are connected directly through a null-modem cable, with the router on one end of the cable functioning as DTE and the other functioning as DCE. If the connection is through an X.25 network, then the HDLC window must match that of the network (DCE), not that of the remote host.


Appendix B: Performance Optimization

Line Speeds and Performance

Buffer and Packet Size

Packet switching time constitutes a large share of the total processing time on X.25 equipment. The switching time rises with the number of packets being processed. Increasing packet size improves performance by reducing transmission overhead because fewer packets are required to transmit a given amount of data. Processing time at each node in the circuit also is reduced.

Note:
If the line quality is poor, you may consider reducing the packet size. A smaller packet would have less data to reassemble and re-transfer, and thus would be faster.

For optimal performance of the EiconCard, the size of the data buffer ideally should be a multiple of the X.25 packet size. If the buffer size is not a multiple of the X.25 packet size, some X.25 packets will not be filled to their capacity. The buffer is set by the application you are using, but most applications do not let you modify the data buffer size.


Appendix C: User Facilities and DTE Address Structure

This appendix describes user facilities, and the DTE address structure. User Facilities are optional network services that let you do things such as reverse charging on your calls, accessing a Closed User Group, or specifying a Network User Identification (NUI). Included in this appendix is an explanation of the structure of the called-DTE and calling-DTE fields.

The DTE address structure described here is based on CCITT Recommendation X.25 (1988). To find out if your network differs from these specifications or uses earlier versions of them, see your X.25 subscription or your network manager.

Also included in this chapter are X.25 and ISDN Cause and Diagnostic Codes.

User Facility Support

Facility Types

Facility Syntax

User Facility Request Codes

Examples of User Facilities

Further Information on User Facilities

DTE Address Structure

DNIC

National Number

Examples of DTE Addresses

Networks and DNICs

X.25 Cause and Diagnostic Codes

Cause Codes

ISDN Cause and Diagnostic Codes

NI-1 (North America)

TPH1962 (Australia)

Euro (Europe)

AT&T 5ESS (North America)


Appendix C: User Facilities and DTE Address Structure

User Facility Support

Facilities are encoded into the Facility field of the call request packet without any interpretation on the part of the program. This allows you to specify any optional User Facilities except for the packet retransmission Facility and extended packet sequence numbering (modulo 128).

The Facility field contains both Facility codes and their associated parameters. The code format varies since some Facilities may have one, two, or more parameters. Enter the contents of the User Facilities field as hexadecimal numbers separated by commas, as ASCII characters within either single or double quotation marks, or as a combination of both.

Facility Types

Facility Syntax

User Facility Request Codes

Examples of User Facilities

Further Information on User Facilities


Appendix C: User Facilities and DTE Address Structure

User Facility Support

Facility Types

Facilities fall into two groups: those specified at subscription time, and those specified on a per-call basis.

Subscription Facilities

The first group includes CCITT Facilities such as nonstandard default window and packet sizes, Closed User Group definitions, barring of incoming or outgoing calls, and Reverse Charging.

Per-Call Facilities

The second group of Facilities are agreed upon at the time of subscription but can be used on a per-call basis. These Facilities include: Reverse Charging, indexing of a Closed User Group (CUG), or specification of a Network User Identification (NUI).


Appendix C: User Facilities and DTE Address Structure

User Facility Support

Facility Syntax

Facility codes are entered as a string of numbers and/or ASCII characters. The first parameter of a Facility code indicates the Facility you want to use. The subsequent parameters supply information about that Facility.

A request for CCITT Facilities must always precede all requests for non-CCITT Facilities. The National Facility Marker (0,0) need only be included when at least one request for a non-CCITT facility is present.

The following sections explain the syntax for Network User Identification, and Flow Control Negotiation.

Network User Identification (NUI): C6, NUIlength,NUI

The first parameter after the Facility code specifies the length in bytes of the NUI. This is followed by the NUI itself, in a format determined by the network administration. The following shows how to encode the seven-character NUI pass.id.

 C6,07,"pass.id"

Flow Control Negotiation (packet size):42,insize,outsize

Insize and outsize specify, respectively, the maximum length of incoming and outgoing packets. They are coded as the logarithm base 2 of the packet size, and may be offered by networks in the range of 4 through 12. That is, packet sizes from 16 through 4096 bytes. All networks must offer packet size 7 (128 bytes).


Appendix C: User Facilities and DTE Address Structure

User Facility Support

User Facility Request Codes

Certain Facilities may be specified on the X.PAD call request (CALL) command line. These same Facility Codes may also appear as a part of PAD Service Signals such as CLEAR and LISTENING.

Code	Facility
C	Charging information
E  Address Extension String	Called Address Extension
F	Fast select with no restriction on response
G CUG string	Closed user group
N  NUI string	Network user identification
O CUG string	Closed user Group with outgoing access
Code	Facility
Q	Fast select with restriction on response
R	Reverse charging
T  RPO string	RPO transit network selection
P	Puts a Datapac Priority Traffic Indicator at the beginning of the Facility field. This is not a standard CCITT facility.


Appendix C: User Facilities and DTE Address Structure

User Facility Support

Examples of User Facilities

The following are examples of User Facilities and their corresponding codes.

User Facility	Code
National Facility Marker	0,0
Reverse Charging	1,1
Throughput Class Negotiation	2,table
Closed User Group (CUG) Selection	3,CUG index
Flow Control Negotiation (packet size)	42,insize,outsize
Flow Control Negotiation (window size)	43,insize,outsize
Network User Identification (NUI)	C6,NUIlength,NUI
An Example of a Non-CCITT Facility

The DATAPAC Traffic Class Facility is an example of a non-CCITT Facility. One of its significant aspects is that it is compulsory when making an international call. Its coding is 1,1 and it must be preceded by the National Facility Marker (0,0). For example:

Priority Traffic:	0,0,1,1
Reverse Charging and Priority Traffic:	1,1,0,0,1,1

Other networks also define their own Facilities. If you receive repeated "Invalid Facility Request" messages or if you wish to find out more about the Facilities applicable to you, contact your network representative.


Appendix C: User Facilities and DTE Address Structure

User Facility Support

Further Information on User Facilities

The forgoing text is not intended as an exhaustive description of the User Facilities supported either by the CCITT, or by the network you may be attempting to use. For information on CCITT User Facilities, consult the CCITT Recommendation International User Services and Facilities in Public Data Networks, Vol. VIII, Fascicle VIII.2, Rec. X.2.


Appendix C: User Facilities and DTE Address Structure

DTE Address Structure

This section describes the structure of the called-DTE and calling-DTE field.

The DTE address structure described here is based on CCITT Recommendation X.25 (1988). To find out if your network differs from these specifications, or uses earlier versions of them, refer to your network manager.

DNIC

National Number

Examples of DTE Addresses

Networks and DNICs


Appendix C: User Facilities and DTE Address Structure

DTE Address Structure

DNIC

CCITT Recommendation X.121 defines a general address format which may be 12, 13, or 14 digits long. The first four digits make up the Data Network Identification Code (DNIC). The first three digits of the DNIC generally identify the country— much like area codes—with the exception of large countries such as the United States. The fourth digit identifies a particular network within that country.

In Canada, for example, DNICs begin with the digits 302. DATAPAC’s DNIC is 3020. The DNIC for Infoswitch is 3029.

There is a listing of major public data networks together with their DNICs later in this chapter.


Appendix C: User Facilities and DTE Address Structure

DTE Address Structure

National Number

Digits 5 through 12 of the DTE address are known as the National Number, which identifies the DTE within the network. This is an address assigned to a specific location at the time of subscription.

Some networks support optional sub-addressing for use by the DTE on a per-call basis. When a sub-address is used, it will pass transparently through the network and will not be verified by the network. This one- or two-digit number may be used to address a particular PC on a local area network or a specific application program within a PC.

Note:
The DTE Address format may vary from one network to another. You should, therefore, verify with your administration to what degree it is compatible with CCITT recommendations. For example, some networks prefix an international address with an escape digit: Telecom Canada's DATAPAC uses prefix 1.


Appendix C: User Facilities and DTE Address Structure

DTE Address Structure

Examples of DTE Addresses

The following are examples of the DTE Address structures.

Example: SprintNet (Formerly Telenet)

The SprintNet numbering plan is consistent with CCITT Recommendation X.121 and follows the address structure of a four-digit Data Network Identification Code (DNIC) followed by a Network Terminal Number (NTN).

A SprintNet network address, which can consist of up to 14 digits, is defined by the following fixed-length fields:

Data Network Identification Code (4 digits)

The first four digits are the Data Network Identification Code as described earlier in this appendix.

Area Code Field (3 digits)

This field defines the area code associated with the Called DTE Address, and functions like a telephone area code.

Server DTE Address Field (5 digits)

This is the address assigned to the particular DTE at subscription time.

Port Field (2 digits)

This is an optional field used by the DTE only, and is not interpreted by the network. For example, it can be used to identify different PCs on a LAN, or a specific application program. The Port Field must be in the range of 0 through 90; otherwise the network will clear the call.

When making a call within the SprintNet network, the DNIC must be 3110 and the address length must be either 12 or 14 digits. For calls outside SprintNet, the DTE Address length must be 4 to 14 digits long, including the DNIC.

Example: DATAPAC (Telecom Canada)

DATAPAC local network addresses consist of up to ten digits: an eight-digit local address plus an optional two-digit sub-address. International addresses are composed in the following form: 1 + DNIC + NA, where NA is the network address.

DATAPAC internal calls can use either the national address or the international address with the DATAPAC DNIC (3020). All international addresses, however, must be preceded by the digit 1 (this international prefix is a DATAPAC option and is not passed between networks).

Note:
All international calls must select Priority Traffic Class. For more information see "An Example of Non-CCITT Facilities" in this appendix.

For more information contact your DATAPAC representative, or access the DATAPAC Information Service (its DTE Address is 3020 92100086).

Example: Packet SwitchStream (British Telecom)

When connected to Packet SwitchStream (PSS) the full X.121 address (DNIC+ National Address number) must be used for inland as well as international calls.

Note:
Your PC operates as a PSS packet mode DTE. Therefore, do not prefix an international address with the escape digit 9.


Appendix C: User Facilities and DTE Address Structure

DTE Address Structure

Networks and DNICs

The following table shows the DNICs of various public data networks around the world. This table also includes information/test numbers. You can call them for further information about a given network, or to test the results of your X.3 PAD parameter settings.

The numbers in this table are in effect at the time of publication.

Country	Network	DNIC	Test Number
Argentina	ARPAC	7220
Austria	Radio Austria	2320
Austria	RADAUS	2329
Austria	Datex-P	2322
Bahamas	Batelco	3640
Barbados	IDAS	3420
Belgium	DCS	2062
Bermuda	IPSD	3500
Brazil	Interdata	7240
Canada (Telecom)	Datapac	3020	76000002  Include "ECHO" in Call User Data field of call request or CONNECT command.
Canada (CN/CP)	Infoswitch	3029
Chile	ENTEL	7302
Colombia	DAPAQ	3107
Denmark	Datapak	2382
Dominican Republic	UDTS	3700
Egypt	Arento	6020
Finland	Finnpak	2442
France	Transpac	2080	0030100
France	NTI	2081
Germany	Datex-P	2624	5690049002  Include "ECHO" in Call User Data field of call request or CONNECT command.
Greece	Helpak	2022
Guatemala	Guatel	7040
Hong Kong	IDAS	4542
Iceland	Icepak	2740
Indonesia	SKDP	5101
Ireland	IPSS	2721
Ireland	EIRPAC	2724
Israel	Isranet	4251
Italy	ITAPAC	2227
Jamaica	Jamatel	3380
Japan (NTT)	DDX-P	4401
Japan (KDD)	Venus-P	4408
Luxembourg	Luxpac	2704
Malaysia	Maypac	5021
Mexico	Telepac	3340
Netherlands	Datanet 1	2044
Norway	Datapak	2422
Panama	Intelpaq	7141
Portugal	SABD	2682
Puerto Rico	UDTS-PDIA	3301
Singapore	Telepac	5252
South Korea	DNS	4501
Spain	Iberpac	2145
Sweden	Telepak	2402
Switzerland	Telepac	2284
Thailand	IDAR	5250
United Kingdom	IPSS	2341
United Kingdom	PSS	2342	1920100513
United States	Accunet	3134
United States	Autonet	3126
United States	ITT	3103
United States	RCA	3113
United States	SprintNet	3110	20200142  ID: PHONES,  PW: PHONES
United States	Tymnet	3106
United States	WUI	3104
Virgin Islands	UDTS-PDIA	3300


Appendix C: User Facilities and DTE Address Structure

X.25 Cause and Diagnostic Codes

Here is a list of X.25 diagnostic and cause codes. These codes can help you trace the source of problems encountered with an X.25 connection.

Diagnostic Codes

Description	Diagnostic	Hex Code
NO ADDITIONAL INFORMATION	EX25NOINFO	OOh
	Invalid P(S)	EX25INVPS	01h
	Invalid P(R)	EX25INVPR	02h
PACKET TYPE INVALID	EX25PKTINV	10h
	For state r1	EX25PKTIR1	11h
	For state r2	EX25PKTIR2	12h
	For state r3	EX25PKTIR3	13h
	For state p1	EX25PKTIP1	14h
	For state p2	EX25PKTIP2	15h
	For state p3	EX25PKTIP3	16h
	For state p4	EX25PKTIP4	17h
	For state p5	EX25PKTIP5	18h
	For state p6	EX25PKTIP6	19h
	For state p7	EX25PKTIP7	1Ah
	For state d1	EX25PKTID1	1Bh
	For state d2	EX25PKTID2	1Ch
	For state d3	EX25PKTID3	1Dh
PACKET NOT ALLOWED	EX25PKTNA	20h
	Unidentifiable packet	EX25UPKT	21h
	Call on one way logical channel	EX25COWLC	22h
	Invalid packet type on a PVC	EX25IPKT	23h
	Packet on unassigned LCN	EX25PKTULC	24h
	Reject not subscribed to	EX25REJNST	25h
	Packet too short	EX25PKT2S	26h
	Packet too long	EX25PKT2L	27h
	Invalid GFI (General Format Identifier)	EX25IGFI	28h
	Restart with non-zero GFI	EX25RN0GFI	29h
	Packet type not compatible with facility	EX25PKTNCF	2Ah
	Unauthorized interrupt confirmation	EX25UINTRC	2Bh
	Unauthorized interrupt	EX25UINTR	2Ch
	Unauthorized reject	EX25UREJ	2Dh
TIMER EXPIRED	EX25TIMEXP	30h
	For incoming call	EX25TEIC	31h
	For clear indication	EX25TECI	32h
	For reset indication	EX25TERI	33h
	For restart indication	EX25TERAI	34h
CALL SET-UP, CALL CLEARING OR REGISTRATION PROBLEM	EX25CSUP	40h
	Facility/registration code not allowed	EX25FCNA	41h
	Facility parameter not allowed	EX25FPNA	42h
	Invalid called address	EX25ICDA	43h
	Invalid calling address	EX25ICGA	44h
	Invalid facility/registration length	EX25IFRLEN	45h
	Incoming call barred	EX25ICBARRED	46h
	No logical channel available	EX25NLCAVAIL	47h
	Call collision	EX25CALLCOLL	48h
	Duplicate facility requested	EX25DUPFACREQ	49h
	Non-zero address length	EX25N0ADDRLEN	4Ah
	Non-zero facility length	EX25N0FACLEN	4Bh
	Facility not provided when expected	EX25FNOTPROV	4Ch
	Invalid CCITT-specified DTE facility	EX25ICCITTF	4Dh
MISCELLANEOUS		50h
	Improper cause code from DTE	EX25IMPCCODE	51h
	Non-aligned byte (octet)	EX25NOTALIGN	52h
	Inconsistent Q-bit setting	EX25IQBITSET	53h
INTERNATIONAL PROBLEM	EX25INTLPROB	70h
	Remote network problem	EX25RNETPROB	71h
	International protocol problem	EX25INTLPPROB	72h
	International link out of order	EX25INTLLOOR	73h
	International link busy	EX25INTLBUSY	74h
	Transit network facility problem	EX25TNETFPROB	75h
	Remote network facility problem	EX25RNETFPROB	76h
	International routing problem	EX25INTLRPROB	77h
	Temporary routing problem	EX25TEMPRPROB	78h
	Unknown called DNIC	EX25UCDNIC	79h
	Maintenance action	EX25MAINTACT	7Ah

Cause Codes


Appendix C: User Facilities and DTE Address Structure

X.25 Cause and Diagnostic Codes

Cause Codes

Description	Causes	Hex Code
CLEARING CAUSES
	DTE originated call	EX25DTEORG	00h
	Number busy	EX25NUMBUSY	01h
	Invalid facility request	EX25IFREQ	03h
	Network congestion	EX25NETCONG	05h
	Out-of-order	EX25OUTORDER	09h
	Access barred	EX25ABARRED	0Bh
	Not obtainable	EX25NOTOBT	0Dh
	Remote procedure error	EX25REMPROC	11h
	Local procedure error	EX25LOCPROC	13h
	RPOA out of order	EX25RPOAOOR	15h
	Reverse charging not subscribed to	EX25REVCHRGNS	19h
	Incompatible destination	EX25INCDEST	21h
	Fast Select acceptance not subscribed to	EX25FASTSELNS	29h
	Ship absent (for mobile maritime service)	EX25SHIPABS	39h
RESETTING CAUSES
	DTE originated call	EX25RDTEORG	00h
	Out of order (PVC only)	EX25ROUTORDER	01h
	Remote procedure error	EX25RREMPROC	03h
	Local procedure error	EX25RLOCPROC	05h
	Network congestion	EX25RNETCONG	07h
	Remote DTE operational (PVC only)	EX25RREMDTEOP	09h
	Network operational (PVC only)	EX25RNETOP	0Fh
	Incompatible destination	EX25RINCDEST	11h


Appendix C: User Facilities and DTE Address Structure

ISDN Cause and Diagnostic Codes

This section lists all ISDN cause and diagnostic codes according to ISDN implementation. These codes can be useful when tracing the source of problems with an ISDN connection. Note that some cause values may have further meanings in addition to the diagnostics given.

NI-1 (North America)

TPH1962 (Australia)

Euro (Europe)

AT&T 5ESS (North America)


Appendix C: User Facilities and DTE Address Structure

ISDN Cause and Diagnostic Codes

NI-1 (North America)

1. CCITT-standardized cause values

2. National-specific cause values

3. Network-specific cause values


Appendix C: User Facilities and DTE Address Structure

ISDN Cause and Diagnostic Codes

NI-1 (North America)

1. CCITT-standardized cause values:

Hex	Cause	Diagnostic
01	Unallocated (unassigned) number	None
02	No route to specified transit network	None
03	No route to destination	None
06	Channel unacceptable	None
07	Call awarded and being delivered in an established channel	None
10	Normal clearing	None
11	User busy	None
12	No user responding	None
13	User alerting, no answer	None
15	Call rejected	None
16	Number Changed	New Destination
1A	Non-selected user clearing	None
1B	Destination out of order	None
1C	Invalid number format (incomplete address)	None
1D	Facility rejected	Facility ID
1E	Response to STATus ENQuiry	None
1F	Normal, unspecified	None
22	Circuit/channel congestion	None
29	Temporary failure	None
2A	Switching equipment congestion	None
2B	Access information discarded	Info element ID
2C	Requested channel not available	None
2F	Resource unavailable, unspecified	None
32	Requested facility not subscribed	None
39	Bearer capability not authorized	None
3A	Bearer capability not presently available	None
3F	Service or option not available, unspecified	None
41	Bearer capability not implemented	None
45	Requested facility not implemented	None
4F	Service or option not implemented, unspecified	None
51	Invalid call reference value	None
58	Incompatible destination	None
60	Mandatory information element is missing	Info element ID
61	Message type non-existent or not implemented	Message type
63	Information element non-existent or not implemented	Info element ID
64	Invalid information element contents	Info element ID
65	Message not compatible with call state	Message type
66	Recovery of timer expiry	None
6F	Protocol error, unspecified	None
7F	Interworking, unspecified	None


Appendix C: User Facilities and DTE Address Structure

ISDN Cause and Diagnostic Codes

NI-1 (North America)

2. National-specific cause values:

Hex	Cause	Diagnostic
04	Vacant Code	None
08	Prefix 0 dialed in error	None
09	Prefix 1 dialed in error	None
0A	Prefix 1 not dialed	None
0B	Excessive digits received, call is proceeding	None


Appendix C: User Facilities and DTE Address
Appendix C: User Facilities and DTE Address Structure

ISDN Cause and Diagnostic Codes

NI-1 (North America)

3. Network-specific cause values:

Hex	Cause	Diagnostic
08	Call is proceeding	None
0D	Service denied	None
1C	Special Intercept Announcement	None
1D	Special Intercept Announcement Undefined Code	None
1E	Special Intercept Announcement Number Unassigned	None
1F	Special Intercept Announcement Call Blocked Due To Group Restriction	None
33	Call Type incompatible with service request	None
35	Service operation violated	Long-term denial, short-term denial
65	Protocol error threshold exceeded	None


Appendix C: User Facilities and DTE Address Structure

ISDN Cause and Diagnostic Codes

TPH1962 (Australia)

Hex	Cause
01	Unallocated (unassigned) number
06	Channel unacceptable
10	Normal clearing
11	User busy
12	No user responding
15	Call rejected
16	Number Changed
1A	Non-selected user clearing
1B	Destination out of order
1C	Invalid number format (incomplete address)
1D	Facility rejected
1E	Response to STATUS ENQUIRY
1F	Normal, unspecified
22	No circuit/channel available
26	Network out of order
29	Temporary failure
2A	Switching equipment congestion
2B	Access information discarded
2C	Requested circuit/channel not available
2F	Resource unavailable, unspecified
32	Requested facility not subscribed
35	Outgoing calls barred within CUG
37	Incoming calls barred within CUG at destination
39	Bearer capability not authorized
3A	Bearer capability not presently available
3F	Service or option not available, unspecified
41	Bearer capability not implemented
42	Channel type not implemented
46	Only restricted digital information bearer capability is available
4F	Service or option not implemented, unspecified
51	Invalid call reference value
52	Identified channel does not exist
53	A suspended call exists, but this call identity does not
54	Call identity in use
55	No call suspended
57	Destination not member of CUG
58	Incompatible destination
5A	Non-existent CUG
5F	Invalid message, unspecified
60	Mandatory information element is missing
61	Message type non-existent or not implemented
62	Message not compatible with call state or message type non-existent or not implemented
63	Information element non-existent or not implemented
64	Invalid information element contents
65	Message not compatible with call state
66	Recovery on timer expiry
6F	Protocol error, unspecified
7F	Interworking, unspecified


Appendix C: User Facilities and DTE Address Structure

ISDN Cause and Diagnostic Codes

Euro (Europe)

Hex	Cause	Diagnostic
01	Unallocated (unassigned) number
02	No route to specified transit network	Transit network identity
03	No route to destination
06	Channel unacceptable
07	Call awarded and being delivered in an established channel
10	Normal call clearing
11	User busy
12	No user responding
13	No answer from user (user alerted)
15	Call rejected	User supplied diagnostic
16	Number changed	New destination
1A	Non-selected user clearing
1B	Destination out of order
1C	Invalid number format
1D	Facility rejected	Facility identification
1E	Response to STATUS ENQUIRY
1F	Normal, unspecified
22	No circuit/channel available
26	Network out of order
29	Temporary failure
2A	Switching equipment congestion
2B	Access information discarded	Discarded information element identifier(s)
2C	Requested circuit/channel not available
2F	Resources unavailable, unspecified
31	Quality of service unavailable
32	Requested facility not subscribed	Facility identification
39	Bearer capability not authorized
3A	Bearer capability not presently available
3F	Service or option not available, unspecified
41	Bearer capability not implemented
42	Channel type not implemented	Channel type
45	Requested facility not implemented	Facility identification
46	Only restricted digital information bearer capability is available
4F	Service or option not implemented, unspecified
51	Invalid call reference value
52	Suspended call exists, but identified channel does not	Channel identity
53	Call identity does not exist
54	Call identity in use
55	No call suspended
56	Call having the requested call identity has been cleared	Clearing cause
58	Incompatible destination	Incompatible parameter
5B	Invalid transit network selection
5F	Invalid message, unspecified
60	Mandatory information element is missing	Information element identifier(s)
61	Message type non-existent or not implemented	Message type
62	Message not compatible with call state or message type non-existent or not implemented	Message type
63	Information element non-existent or not implemented	Information element identifier(s)
64	Invalid information element contents	Information element identifier(s)
65	Message not compatible with call state	Message type
66	Recovery on timer expiry	Timer number
6F	Protocol error, unspecified
7F	Interworking, unspecified


Appendix C: User Facilities and DTE Address Structure

ISDN Cause and Diagnostic Codes

AT&T 5ESS (North America)

Hex	Cause
01	Unallocated (unassigned) number
02	No route to specified network
03	No route to specified transit network
10	Normal clearing
11	User busy
12	No user responding
13	User alerting, no answer
15	Call rejected
16	Number Changed
1B	Destination out of order
1C	Invalid number format (incomplete number)
1D	Requested facility rejected
1E	Response to STATus ENQuiry
1F	Normal, unspecified
22	No channel available
23	Call queued
29	Temporary failure
2A	Network congestion
2B	Access information discarded
32	Requested facility not subscribed
34	Outgoing calls barred
36	Ingoing calls barred
3A	Bearer capability not presently available
3F	Service or option not available, unspecified
41	Bearer capability not implemented
42	Channel type not implemented
45	Requested facility not implemented
51	Invalid call reference value
52	Identified channel does not exist
58	Incompatible destination
5B	Transit network does not exist
60	Mandatory information element is missing
61	Message type nonexistent or not implemented
62	Message not compatible with call state
64	Invalid information element contents
66	Recovery of timer expiry
6F	Protocol error, unspecified
7F	Interworking, unspecified


Appendix D: Router Interoperation

If you want to connect WAN Services for Windows NT to remote routers from other manufacturers, such as Cisco Systems, Inc., and Bay Networks (formerly Wellfleet Communications, Inc. and Synoptics Communications, Inc.), this appendix tells you how to configure the local and remote routers for successful interoperation.

Interoperability

RFCs and Third-Party routers

Interoperating With a Cisco Router

Routing Over a Point-to-Point Link

Routing Over a Multi-Point Link

Interoperating with a Bay Networks Router

Routing Over a Point-to-Point Link

Routing Over a Multi-Point Link


Appendix D: Router Interoperation

Interoperability

This section describes what you must do to get WAN Services to interoperate successfully with multi-protocol routers produced by other manufacturers. Before turning to the section for the third-party router you are dealing with, please read the following section.

RFCs and Third-Party routers


Appendix D: Router Interoperation

Interoperability

RFCs and Third-Party routers

This version of WAN Services interoperates with any multi-protocol router which implements one or more of the following RFCs:

RFC	Obselete RFC(s)	Name
1490	1294	Multiprotocol InterConnect over Frame Relay
1356	877	Multiprotocol InterConnect on X.25 and ISDN in the Packet Mode
1548	1171,1172, 1331	The Point-to-Point Protocol (PPP) for the Transmission of Multi-protocol Datagrams over Point-to-Point Links

Eicon Technology has rigorously tested the interoperability of WAN Services only with routers manufactured by Eicon Technology, Cisco Systems, Inc., IBM Corp., and Bay Networks. Testing was successful for the following WAN protocols:

Router	PPP	X.25	Frame Relay
Cisco	3	3	3
Bay Networks	3	3	3
IBM	3	3	3
router for NetWare V3R2	3	3	3
ICS V3R1 & V3R2	3	3	3
IP router for OS/2 V3R1	3	3 (SVC only)	3
IP router for UNIX V3R1	3	3 (SVC only)	3


Appendix D: Router Interoperation

Interoperating With an IBM Router

WAN Services interoperates with the 6611 series of multi-protocol routers manufactured by IBM. However, this appendix contains no detailed instructions for interconnecting WAN Services and a router of this type.


Appendix D: Router Interoperation

Interoperating With a Cisco Router

This section describes how to configure a Cisco router and Eicon Technology’s WAN Services for Windows NT for successful interoperation.

Routing Over a Point-to-Point Link

Routing Over a Multi-Point Link


Appendix D: Router Interoperation

Interoperating With a Cisco Router

Routing Over a Point-to-Point Link

In this scenario, the routers are connected through a back-to-back null-modem connection, or over a leased or dial-up line.

Cisco Router Side

At the console command line, enter configuration mode and make sure that encapsulation is set to PPP for the serial interface which connects this router to WAN Services for Windows NT. (This interface is connected directly to the router PC if the connection is back-to-back, and to a modem if the connection is over a leased or dial-up line.)

The two critical commands are:

interface serial x
encapsulation PPP

WAN Services Side

Make sure the EiconCard port you are using to connect to the Cisco router uses PPP for the line protocol module. You do not need to modify any configuration parameters for the PPP module. When configuring this router connection entry using the WAN Services Configuration program, make sure that WAN Protocol is set to PPP.

•	You must specify the IP address of the Cisco router in the IP Address text box.

•	Make sure that Data Compression is unchecked.


Appendix D: Router Interoperation

Interoperating With a Cisco Router

Routing Over a Multi-Point Link

In these scenarios the routers are connected across an X.25 and Frame Relay packet-switched data networks (PSDN).

X.25

This section describes an X.25 connection.

Cisco Router Side

At the console command line, enter configuration mode and make sure that encapsulation is set to X.25 for the serial interface x which connects this router to the X.25 PSDN. The IP address of the Eicon Technology WAN Services PC is mapped to its DTE address.

The critical commands are:

interface serial x
encapsulation X.25
X.25 address ciscodte
X.25 default ip
X.25 map ip eiconip eicondte BROADCAST

where:

x is the serial interface connecting the Cisco router to the X.25 PSDN.

ciscodte is the DTE address of the Cisco router.

eiconip is the IP address of the Eicon Technology WAN Services router.

eicondte is the DTE address of the Eicon Technology WAN Services router.

WAN Services Side

Make sure the EiconCard port you are connecting to the Cisco router uses X.25 for the line protocol module. Unlike the PPP module, the defaults for X.25 may not be exactly suited to your situation. For this reason, you should not skip parameter-by-parameter configuration of the X.25 component.

Pay special attention to the following parameters when creating the router connection for the Eicon-to-Cisco link:

•	You must specify the IP address of the Cisco router in the IP Address text box

•	Make sure that Data Compression is unchecked

Frame Relay

This section describes a Frame Relay connection.

Cisco Router Side

At the console command line, enter configuration mode and make sure that encapsulation is set to Frame Relay /ETF for the serial interface x which connects this router to the Frame Relay PSDN. The IP address of the Eicon Technology WAN Services PC is mapped to its DTE address.

The critical commands are:

interface serial x
encapsulation Frame Relay /ETF
Frame Relay LOCAL_DLCI ciscodlci
Frame Relay LMI_TYPE ANSI
Frame Relay MAP IP eiconip eicondlci BROADCAST

where:

x is the serial interface connecting the Cisco router to the Frame Relay PSDN.

ciscodlci is the DLCI address of the Cisco router.

eiconip is the IP address of the Eicon Technology WAN Services router.

eicondlci is the DLCI address of the Eicon Technology WAN Services router.

WAN Services Side

Make sure the EiconCard port you are connecting to the Cisco router uses Frame Relay for the line protocol module. Unlike the PPP module, the defaults for Frame Relay may not be exactly suited to your situation. For this reason, you should not skip parameter-by-parameter configuration of the Frame Relay component.

Pay special attention to the following parameters when creating the router connection for the Eicon-to-Cisco link:

•	You must specify the IP address of the Cisco router in the IP Address text box

•	Make sure that Data Compression is unchecked


Appendix D: Router Interoperation

Interoperating with a Bay Networks Router

This section describes how to configure a Bay Networks router and Eicon Technology’s WAN Services for Windows NT for successful interoperation.

Routing Over a Point-to-Point Link

Routing Over a Multi-Point Link


Appendix D: Router Interoperation

Interoperating with a Bay Networks Router

Routing Over a Point-to-Point Link

In this scenario the routers are connected through a back-to-back null-modem connection or over a leased or dial-up line.

Bay Networks Router Side

At the Bay Networks router console, do the following to make sure successful routing of IP protocol packets between the Bay Networks router and WAN Services for Windows NT:

1.	From the console main menu, select Configuration Editor, enter a filename of your choosing, and press <Enter>.

2.	Select 7) DoD Internet router from the next menu, press <Enter>, cursor to Browse, and press <Enter>.

3.	Select 3) Static Routes from the next menu and Add a router as follows:

Internet address = eiconip

Type = Adjacent Host

LAN address = {leave this blank}

Subnet Mask = {you must determine this}

Encapsulation = Ethernet

where eiconip is the IP address of the server on the other side of the link.

4.	Return to the previous menu repeatedly until you have returned to the Configuration Menu. Save and exit from this menu to the main menu.

WAN Services Side

Make sure that the EiconCard port you are using to connect to the Bay Networks router uses PPP for the line protocol module. You do not need to modify any configuration parameters for the PPP module.

•	You must specify the IP address of the Bay Networks router in the IP Address text box

•	Make sure that Data Compression is unchecked


Appendix D: Router Interoperation

Interoperating with a Bay Networks Router

Routing Over a Multi-Point Link

In this scenario the Bay Networks and Eicon Technology routers are connected across an X.25, Frame Relay, or ISDN packet-switched data network (PSDN).

Bay Networks Router Side Using Frame Relay

Follow these steps to make sure you will be able to transmit and receive IP protocol packets between the Bay Networks router and WAN Services for Windows NT.

1.	Select 4. Circuits from the Configuration menu, and select a circuit you have defined with Type set to Frame Relay. If you have no Frame Relay circuits defined, refer to your Bay Networks documentation and define a Frame Relay circuit first.

2.	For Max. Packet Size specify the same value as you specified for the Information Field Size parameter when configuring the Frame Relay communications protocol module for WAN Services. You may find it useful to refer to the WAN Services Configuration online help for the Frame Relay module.

3.	For Mgmt. Type specify the same protocol as you specified for the Local management interface protocol parameter when configuring the Frame Relay communications protocol module on WAN Services. You may find it useful to refer to the Eicon WAN Services Configuration online help for the Frame Relay module.

Note:
If you choose Annex D for Local management interface protocol, you must select ANSI Annex D when configuring your Bay Networks router for Frame Relay communications.

4.	Do not change the value of DLCI Encoding Length from the default of two bytes.

5.	Return to the Configuration menu and select 7. DoD Internet router. Select 2. Network Interface Definitions, then make sure that Address Resolution is set to ARP.

Bay Networks router Side If You Are Using X.25

•	Under 4. Circuits from the configuration menu, the circuit you have defined for the connection to the X.25 packet-switched data network must have Quality of Service set to X.25 and Circuit Type set to X.25 PDN

•	You must also use the X.25 Address Map function to map the IP address of the WAN Services PC to its DTE address

•	In the Network Interface Definitions section under 7. DoD Internet router, make sure the following is true for the interface with line type SYNC:

•	Address Resolution is set to PDN

•	Normal ARP, Proxy ARP, Address Mask Replay, and MTU Discovery Option are all set to No

WAN Services Side (X.25 or Frame Relay)

Make sure the EiconCard port you are using to connect to the Bay Networks router uses X.25 or Frame Relay for the line protocol module. Unlike the PPP module, the defaults for X.25 or Frame Relay may not be exactly suited to your situation, and you should NOT skip parameter-by-parameter configuration of the X.25 or Frame Relay module.

Pay special attention to the following parameters when creating router Connection entries for the Eicon-to-Bay Networks link:

•	For X.25, you must specify the IP address of the Bay Networks router in the IP Address text box (not required for Frame Relay)

•	Peer router must be set to Universal

•	Make sure that Data Compression is unchecked


Appendix E: X.3 PAD Parameters

X.3 PAD parameters set the guidelines for how the pad deals with different terminal emulations. Using WAN Services for Windows NT with X.PAD and setting X.3 PAD parameters, you can control such features as local echo, line feed insertions after carriage returns, as well as enabling local editing and determining what service signals are forwarded to the user, etc.

X.3 PAD Parameter Support

How to Set X.3 PAD Parameters

X.3 PAD Parameter Names

X.3 PAD Parameters


Appendix E: X.3 PAD Parameters

X.3 PAD Parameter Support

There are twenty-two standard X.3 PAD parameters which are recognized internationally. These parameters and the functions they control are listed in this chapter. There also exists national X.3 PAD parameters numbered higher than 22, but their definition varies from country to country. X.PAD does not support national parameters.

You should be aware that each of the twenty-two international X.3 PAD parameters has both mandatory and optional values. X.PAD supports all mandatory values (as defined in CCITT Recommendation X.3, 1988); it also supports many of the optional values. Network support, however, will vary. Consult your network manager for specifics.

How to Set X.3 PAD Parameters

X.3 PAD Parameter Names


Appendix E: X.3 PAD Parameters

X.3 PAD Parameter Support

How to Set X.3 PAD Parameters

There are several ways to set X.3 PAD parameters. You can set them inside your terminal emulation program by using X.28 PAD commands before you connect with a host, or by shifting into Command mode after the connection is established. For more information, see Appendix F, “X.28 and X.29 Commands.”

The initial values of X.3 PAD Parameters can also be specified with the X.PAD Configuration program. See “Configuring X.PAD,” for more information.


Appendix E: X.3 PAD Parameters

X.3 PAD Parameter Support

X.3 PAD Parameter Names

When you use X.3 PAD Parameters as input to X.28 PAD Commands, you have the option of specifying them by name. The table below shows the abbreviated CCITT PAD Parameter names, with the remainder of each parameter's full name in parentheses, either of which is accepted from the X.PAD prompt.

Number	Name	Description
1	esc(ape)	PAD recall using a character
2	ech(o)	Echo
3	for(ward)	Selection of data forwarding character
4	idl(e)	Selection of idle timer delay
5	dev(ice)	Ancillary device control
6	sig(nals)	Control of PAD service signals
7	bre(ak)	Operation on receipt of break signal
8	dis(card)	Discard output
9	CRp(ad)	Padding after carriage return
10	fol(ding)	Line folding
11	spe(ed)	Binary speed of start-stop mode DTE
12	flo(w)	Flow control of the PAD
13	LFi(nsert)	Linefeed insertion after carriage return
14	LFp(ad)	Padding after linefeed
15	Edi(t)	Editing
16	Cdel(ete)	Character delete
17	Ldel(ete)	Line delete
18	Ldis(play)	Line display
19	Esig(nals)	Editing PAD service signals
20	Mas(k)	Echo mask
21	par(ity)	Parity treatment
22	pag(e)	Page wait


Appendix E: X.3 PAD Parameters

X.3 PAD Parameters

The following table lists all 22 international X.3 PAD parameters in numerical order, together with the functions they control. All parameters and their possible values are decimal numbers.

ASCII control characters (ASCII characters 0 through 31) are entered as key sequences such as CTRL-P. A table of ASCII control characters, their keyboard entry sequences, and their common mnemonic references appears in Appendix C, “User Facilities and DTE Address Structures”.

Certain X.3 PAD parameters can be coded as the sum of their listed values. This allows you to specify several values simultaneously. Parameter 7, for example, which deals with response to a break signal, has a default value of 21. This is the sum of three of the previous values: 1 (send an interrupt packet), 4 (send an indication of a break), and 16 (discard data). The X.3 PAD parameters that can be coded this way are parameters 3, 6, 7, 13, and 20.

1:n Escape from data transfer --- esc(ape)

2:n Echo --- ech(o

3:n Selection of data forwarding signal --- for(ward)

4:n Selection of idle timer delay --- idl(e)

5:n Auxiliary Device Control --- dev(ice)

6:n Control of service signals --- sig(nals)

7:n Procedure on receipt of break signal --- bre(ak

8:n Discard data --- dis(card)

9:n Carriage return padding --- CRp(ad)

10:n Line folding --- fol(ding)

11:n Communication speed --- spe(ed)

12:n Flow control of the PAD by the PC --- flo(w)

13:n Line Feed insertion after Carriage Return --- LFi(nsert)

14:n Linefeed padding --- LFp(ad)

15:n Editing --- edi(t)

16:n Character delete --- Cdel(ete)

17:n Line delete --- Ldel(ete)

18:n Line redisplay --- Ldis(play)

19:n Editing service signals --- Esig(nals

20:n Echo mask --- mas(k)

21:n Parity treatment --- par(ity)

22:n Page wait --- pag(e)


1:n Escape from data transfer --- esc(ape)

When you are sending or receiving data, this parameter allows you to escape from Data Transfer mode (Terminal mode) and enter Command mode. Flow of data from the network is temporarily suspended.

Value	Description
0	No escape allowed
32-126	Escape is possible by typing the ASCII character represented by the number n
1	Escape from data transfer using CTRL-P


2:n Echo --- ech(o)

This parameter provides for all characters to be echoed on your screen in data and command mode as well as being forwarded to the remote device.

Value	Description
0	No echo
1	Echo


3:n Selection of data forwarding signal --- for(ward)

This parameter defines sets of characters that act as data forwarding signals when they are input to X.PAD.

Value	Description
0	No data forwarding character
1	Alphanumeric characters (A - Z, a - z, 0 - 9)
2	Character CR
4	Character ESC, BEL, ENQ, ACK
8	Character DEL, CAN, DC2
16	Character ETX, EOT
32	Character HT, LF, VT, FF
64	All other characters: ASCII 0 to 31

Coding of parameter 3 can be a single value or the sum of any combination of values listed above. A useful combination would be value 126, which is the sum of the values 2 through 64 (2+4+8+16+32+64 = 126). This would allow you to use any control character as the data forwarding signal.

Note:
These characters are included in the forwarded data packet.


4:n Selection of idle timer delay --- idl(e
4:n Selection of idle timer delay --- idl(e)

This parameter specifies the value of an idle timer used for data forwarding.

Value	Description
0	No data forwarding on time-out
1-255	Units of 1/20 second, maximum 255


5:n Auxiliary Device Control --- dev(ice)

This parameter was originally designed to give the control of data flow to the PAD, when it was dealing with high-speed input devices which could overflow its processing capacity. This is no longer necessary, since X.PAD provides buffering services automatically.

Value	Description
0	No use of DC1 (X-ON) and DC3 (X-OFF) for auxiliary devices or intelligent terminals


6:n Control of service signals --- sig(nals)

This parameter determines whether or not PAD service signals are to be transmitted by the PAD to the DTE (terminal). It also governs the use of Extended Service Signals, as well as the language in which service signals are displayed.

Note:
For Extended Service Signals to be available, you must specify the languages you wish to use with the X.PAD Configuration program.

Value	Description
0	No service signals transmitted to the terminal.
1	All Standard Service Signals other than the prompt are transmitted to the terminal.
4	Only the prompt signal is transmitted to the terminal.
5	All Standard Service Signals are transmitted to the data terminal, plus the prompt signal (4 + 1).
16	Extended Service Signal support for English. No service signals displayed (Base value).
17	Extended Service Signals in English with all service signals other than the prompt (16 + 1).
21	Extended Service Signals in English with all service signals, plus the prompt (16 + 4 + 1).
32	Extended Service Signal support for French. No service signals displayed (Base value).
33	Extended Service Signals in French with all service signals other than the prompt (32 + 1).
37	Extended Service Signals in French with all service signals, plus the prompt (32 + 4 + 1).


7:n Procedure on receipt of break signal --- bre(ak)

This parameter specifies the operation upon entry of a break character.

Value	Description
0	Nothing
1	Send an interrupt packet
2	Send a reset packet
4	Send an indication of break
8	Escape from data transfer state
16	Discard output
21	Send an interrupt packet, send an indication of break, and discard output (16 + 4 + 1)
Coding of parameter 7 can be a single value or the sum of any combination of values listed above. The default value (21) is the sum of 16 + 4 +1.


8:n Discard data --- dis(card)

Value	Description
0	Normal data delivery to terminal
1	Discard pending data

This parameter allows the PAD to discard data. It is permanently set to 0 (normal delivery to terminal) and cannot be directly modified, even in Command mode. You can, however, arrange for data to be discarded after a break signal, by setting X.3 parameter 7 to 16.


9:n Carriage return padding --- CRp(ad)

This parameter provides for the automatic insertion of a time delay referred to as a padding character into the character string after a carriage return. This allows for a printing mechanism to perform the carriage return function properly.

Value	Description
0-31	A value from 0 to 31 indicating the number of padding characters to be inserted after a carriage return
2	Insert 2 padding characters after a carriage return


10:n Line folding --- fol(ding)

This parameter determines the maximum number of characters which can be printed or displayed on each line on your terminal. If more characters are entered, a new line will automatically be started.

Value	Description
0	No line folding
1-255	Line folding after n characters


11:n Communication speed --- spe(ed)

This parameter originally specified the speed of data transmission. You can set it to one of the values below, if you are dealing with a host computer that needs to check this parameter when you first connect. This is a formality, however, and will not affect the speed of your X.25 link.

Value	Description
0	110 bits/second
1	134.5 bits/second
2	300 bits/second
3	1200 bits/second
4	600 bits/second
5	75 bits/second
6	150 bits/second
7	1800 bits/second
8	200 bits/second
9	100 bits/second
10	50 bits/second
11	75/1200 bits/second
12	2400 bits/second
13	4800 bits/second
14	9600 bits/second
15	19200 bits/second
16	48000 bits/second
17	56000 bits/second
18	64000 bits/second


12:n Flow control of the PAD by the PC --- flo(w)

This parameter allows for flow control of received data using X-ON and X-OFF characters. The X-ON character is DC1 (CTRL-Q) and the X-OFF character is DC3 (CTRL-S).

Value	Description
0	No use of X-ON and X-OFF
1	Use of X-ON and X-OFF


13:n Line Feed insertion after Carriage Return --- LFi(nsert
13:n Line Feed insertion after Carriage Return --- LFi(nsert)

This parameter instructs the PC to routinely insert a Line Feed (LF) into the data stream following each appearance of a Carriage Return (CR) character.

Value	Description
0	No LF insertion
1	Insert a LF after each CR in the received data stream
2	Insert a LF after each CR in the transmitted data stream
4	Insert a LF after each CR in the echo to the screen

Coding of parameter 13 can be a single value or the sum of any combination of values listed above.


14:n Linefeed padding --- LFp(ad)

This parameter provides for the automatic insertion, by the PAD, of padding characters to allow for a time duration delay after each linefeed character. This will allow for a printing mechanism to perform a line feed correctly.

Value	Description
0-15	Any number from 0 to 15 indicating the number of padding characters to be inserted after a linefeed
0	No padding characters inserted


15:n Editing --- edi(t)

This parameter allows you to perform local editing after making a connection with the host. If you enable local editing (set parameter 15 to 1), you can correct any data buffered locally, rather than sending it across the network to the host for later correction. When local editing is allowed, the PC will monitor for characters which have been assigned per 16 (Character delete), 17 (Line delete), and 18 (Line redisplay).

Local editing cannot be enabled unless the idle timer (parameter 4) is set to 0.

Value	Description
0	No editing in the data transfer state
1	Editing in the data transfer state


16:n Character delete --- Cdel(ete)

This parameter lets you specify which ASCII character will delete the previously typed character from the buffer (provided local editing has been enabled).

Value	Description
0	No character delete
1-127	Character-delete character
127	Character delete with DEL


17:n Line delete --- Ldel(ete)

This parameter lets you specify which ASCII character will delete the previously typed line from the buffer (provided local editing has been enabled).

Value	Description
0	No line delete
1-127	Line-delete character
24	CAN (CTRL-X) serves as line-delete character


18:n Line redisplay --- Ldis(play)

This parameter lets you specify which ASCII character will redisplay the previously typed line (provided local editing has been enabled).

Value	Description
0	No line redisplay
1-127	Line-redisplay character
18	DC2 (CTRL-R) is line-redisplay character


19:n Editing service signals --- Esig(nals
19:n Editing service signals --- Esig(nals)

This parameter specifies what service signal to send to the terminal once the editing functions described by Character Delete, Line Delete, and Line Display characters (parameters 16, 17, and 18).

Value	Description
0	No service signal
1	Display “\” for each deleted character; display “XXX” for each deleted line
2	Display <BS><SP><BS> for each deleted character and for each subsequent character on the same line that is deleted
8	Backspace character will be the editing service signal
32-126	The character specified will be the editing service signal


20:n Echo mask --- mas(k)

This parameter specifies the characters from the PC for which the PAD is to echo back to the DTE (terminal). The echo mask applies only when parameter 2 (echo) is set to 1.

Value	Description
0	No Echo mask (all characters echoed)
1	No echo of character CR
2	No echo of character LF
4	No echo of characters VT, HT, FF
8	No echo of characters BEL, BS
16	No echo of characters ESC, ENQ
32	No echo of characters ACK, NAK, STX, SOH, EOT, ETB, ETX
64	No echo of editing characters as designated by parameters 16, 17 and 18
128	No echo of all other ASCII control characters (0-31) not mentioned above, and the character DEL (ASCII character 127)

Coding of parameter 20 can be a single value or the sum of any combination of values listed above. If parameter 5, 12 or 22 is set to a non-zero value, then X-ON (DC1) and X-OFF (DC3) are not echoed.


21:n Parity treatment --- par(ity)

	Description
0	No parity checking or generation

Not necessary for a software PAD, since an asynchronous signal is not being generated. Parameter 21 is permanently set to 0 and does not influence parity.

If your application generates parity signals, however, then the PAD will also generate them and will incorporate them into the packets it transmits. In this case the PAD will also remove parity signals from incoming packets before sending the data to your application.


22:n Page wait --- pag(e)

The PC will be able to suspend the transmission of additional characters after a specified number of linefeeds have been received. No further data will be transmitted until the page wait condition is canceled.

Value	Description
0	Page wait disabled
1-255	Page wait condition after n linefeed characters are received by the PC

The PC will cancel the page wait condition and resume normal transmission on receipt of an X-ON character (CTRL-Q).


Appendix F: X.28 and X.29 Commands

X.28 PAD commands let you manipulate the pad from within the terminal emulation. X.28 PAD commands can be used to display the X.3 PAD parameters in effect for your sessions. You can also use X.28 PAD commands to set selected X.3 PAD parameters, or to set the values of all X.3 PAD parameters at once.

X.29 commands (PAD messages) are the signals exchanged between the remote and local computers over the X.25 networks.

Using X.28 PAD Commands

PAD Profiles

Extended Service Signals

Loading Extended Service Signal Support

Enabling Extended Service Signals

X.28 PAD Command Summary

X.28 PAD Commands: Syntax and Examples

X.3 Parameter Specification

Extended Service Signals

Parameter Abbreviations

X.29 Commands (PAD Messages)


Appendix F: X.28 and X.29 Commands

Using X.28 PAD Commands

When your terminal emulation package first starts, it is in Command mode. In Command mode you can enter X.28 PAD commands. After you have established your connection with the host, using the standard call request command or Eicon Technology's CONNECT or CALL commands, you are considered to be in Terminal mode.

If you want to use any of the X.28 PAD commands after you have connected to your host computer, you can re-enter Command mode by pressing CTRL-P, or whatever key sequence is defined as your Escape sequence. You will not see any immediate change on the screen. But if you type in a command such as PAR, for example, and then press Enter, you should see the output for that command on the next line.

The output for the PAR command is the list of X.3 PAD parameters in effect for your current session. Since many host computers set your X.3 PAD parameters automatically when you connect, the output of PAR, once you have connected, may be quite different than X.PAD's default list. In fact, if the host computer you have called sets parameter 1 to 0, you may not be able to use Command mode at all.

If you want to change the values of any X.3 PAD parameter once you're in Command mode, use the SET or SET? commands.

When you're through setting your parameters and you want to resume Terminal mode, press Enter (Return) on an empty line. It may take a few seconds but you should soon see the host prompt or application on your screen again.

Note:
Pressing CTRL-P (or whatever sequence you have defined as your Escape sequence) twice will not put you into Command mode: it will insert an escape character—CTRL-P, for example—into the data stream.

If X.3 PAD parameter 1 is set to a value other than 1, then the character sequence that puts you into Command mode will not be CTRL-P. For more information, see Appendix E, “X.3 PAD Parameters".”

PAD Profiles


Appendix F: X.28 and X.29 Commands

Using X.28 PAD Commands

PAD Profiles

The set of all the X.3 PAD parameters in effect for a PAD is called its profile. You can display the profile of your PAD with the PAR command. At startup, if you are running a freshly-installed X.PAD, the PAR command produces the following listing:

XPAD:PAR
XPAD:PAR1:1,2:1,3:2,4:0,5:0,6:5,7:21,9:2,10:0,11:0,12:1,
13:4,14:0,15:1,16:127,17:24,18:18,19:2,20:0,21:0,22:0

If you change two parameters, for example, with the SET? command

XPAD:SET? 10:80,12:0
XPAD:PAR 10:80,12:0

you change the profile to

XPAD:PAR
XPAD:PAR1:1,2:1,3:2,4:0,5:0,6:5,7:21,9:2,10:80,11:0,12:0,
13:4,14:0,15:1,16:127,17:24,18:18,19:2,20:0,21:0,22:0

Predefined PAD Profiles

When installed, the X.PAD software includes seven predefined profiles (1, 2, 3, 4, 5, 6, and RAS) which have the values shown below. You can edit these profiles to suit your needs, except for the RAS profile which is read-only. See “Configuring X.PAD,” for more information.

You can view these profiles with the PROF? command. As an example, if you use the transparent profile frequently, you can define the profile named 1. You can then assign it to the current PAD with the statement

PROFILE 1

This table shows the default Profile definitions when X.PAD is installed.

PAR	Function		Profile Name
			1	2	3	4	5	6	RAS (Local)	RAS (Remote)
1	Escape to Command Mode		1	1	0	1	1	0	0	0
2	Local echo		0	1	0	0	0	0	0	0
3	Selection of data forwarding character		126	2	0	2	2	0	0	0
4	Selection of idle delay timer (1/20 of a second)		0	0	20	0	0	1	0	1
5	Auxiliary device control		1	0	0	0	0	0	0	0
6	Pad service signal		5	5	0	5	5	0	1	1
7	PAD action on break signal		2	21	2	21	2	0	0	0
8	Discard pending output		0	0	0	0	0	0	0	0
9	Insert padding characters after carriage return		0	2	0	2	2	0	0	0
10	Line display width		0	0	0	0	0	0	0	0
11	Transmission speed		0	0	0	0	0	0	0	Blank (not sent)
12	Flow control by PAD		1	1	0	0	1	0	0	0
13	Linefeed after carriage return		16	4	0	16	21	0	0	0
14	Number of padding characters after linefeed		0	0	0	0	0	0	0	0
15	Local editing of data		0	1	0	0	0	0	0	0
16	Character delete symbol		127	127	127	127	127	127	0	0
17	Line delete symbol		24	24	24	24	24	24	0	0
18	Line redisplay symbol		18	18	18	18	18	18	0	0
19	PAD service signal		0	2	0	0	0	0	0	0
20	Echo mask		0	0	0	0	0	0	0	0
21	Parity treatment		0	0	0	0	0	0	0	0
22	Page wait		0	0	0	0	0	0	0	0


Appendix F: X.28 and X.29 Commands

Extended Service Signals

X.PAD supports Extended Service Signals in two of the three official CCITT languages—French and English. When Extended Service Signals are enabled, a few words of descriptive text appear in the service signals. For example, if you use the PAR Command to display the values of X.3 Parameters 2 and 6:

XPAD:parameter 2, 6
XPAD: PAR 2:0 - Echo, 6:21 - Control of PAD Service Signals

then, after each Parameter value, you will see a phrase to remind you of the Parameter's function.

Loading Extended Service Signal Support

Enabling Extended Service Signals


Appendix F: X.28 and X.29 Commands

Extended Service Signals

Loading Extended Service Signal Support

For Extended Service Signals to be available, you must specify that the support files be loaded when the X.PAD driver is loaded. This is done with the X.PAD Configuration program by specifying language support. Once the support files are loaded, all PADs have access to the languages configured. See “Configuring X.PAD,” for more information.


Appendix F: X.28 and X.29 Commands

Extended Service Signals

Enabling Extended Service Signals

Once language support files are loaded, Extended Service Signals are enabled for a specific PAD using X.3 Parameter 6. If Parameter 6 is set to 21, English language Extended Service Signals, as well as the prompt, are displayed. For more information, see Appendix E, “X.3 PAD Parameters.”

Language support may also be enabled with the X.28 command LANGUAGE or LANG).


Appendix F: X.28 and X.29 Commands

X.28 PAD Command Summary

Command	Definition
Break	Sends a break signal.
Call	Make connection with host.
Cancel	Terminates LISTEN on the current PAD.
call request	See Call.
Clr	Clear connection with host.
Clear	See Clr.
Connect	Make connection with host.
Iclr	Sends an Invitation to Clear to remote PAD.
ID	Identifies the PAD to the network.
Idoff	Disables ID command.
Int	Send interrupt packet.
Intd	Interrupt and discard data.
Interrupt	See Int.
Language	Enable language support.
Lang	See Language.
Listen	Puts X.PAD into host mode.
Par	Display current parameters.
Par?	See Par.
Parameter	See Par.
Prof	Assigns a predefined profile.
Prof?	List a predefined profile.
Profile	See Prof.
PVC	Specify the PVC to be used for this connection.
Read	See Par.
Reset	Reset circuit counters.
Rpar?	Obtains remote PAD X.3 Parameters.
Rread	See Rpar?
Rret	Reads X.3 parameters returned by the RPAR or RREAD.
Rset	Set and read X.3 parameters of the remote PAD.
Rsetread	See Rset.
Set	Sets X.3 Parameters without listing them.
Set?	Set and list current PAD's X.3 Parameters.
Setread	See Set?
Stat?	Gives extended connection information.
Command	Definition
Stat	Obtain connection status.
Status	See Stat.


Appendix F: X.28 and X.29 Commands

X.28 PAD Commands: Syntax and Examples

This section lists all of the X.28 PAD commands supported by X.PAD. It shows their syntax and gives examples of their action. The following information applies to all of the commands in this section.

X.3 Parameter Specification

Extended Service Signals

Parameter Abbreviations


Appendix F: X.28 and X.29 Commands

X.28 PAD Commands: Syntax and Examples

X.3 Parameter Specification

All X.28 Commands accept X.3 Parameter names, as well as numbers, as input. The output from these Commands, however, specifies X.3 Parameters by number only. For example, if you enable Extended Service Signals with SET?, you would see:

XPAD:SET?   sig:23
XPAD: PAR 6:23 - Control of PAD service signals

For more information, see Appendix E, “X.3 PAD Parameters.”


Appendix F: X.28 and X.29 Commands

X.28 PAD Commands: Syntax and Examples

Extended Service Signals

The places where Extended Service Signals may appear is indicated by angle brackets. For example

FREE   <- No Call established >


Appendix F: X.28 and X.29 Commands

X.28 PAD Commands: Syntax and Examples

Parameter Abbreviations

The following table shows abbreviations that are used throughout this chapter.

Parameter	Description
param	Specifies an X.3 PAD Parameter.
value	Specifies an X.3 PAD Parameter value.
udata	Indicates where user data fields may appear. The format of user data fields is network dependent.
fac_code	Indicates one of the facility codes that appear in the table “Facility Request Codes” in Appendix C, “User Facilities and DTE Address Structures.”
facilities	Indicates full CCITT facilities support, as described in Appendix C.


BREAK

Purpose  The action of this command depends on the value to which X.3 PAD Parameter 7 is set.

Format

  BREAK

Output

  None


CALL (also known as call request)

Purpose  Makes connection with a remote host computer. Call request supports the CCITT User Facilities shown in the “Facility Request Codes” table. If you need other User Facilities, use the CONNECT command.

Format

  [CALL] [fac_code] called-DTE [,calling-DTE ] [[P|D|*] udata]

Parameter	Description
CALL	An Eicon Technology addition to the call request command. It's optional.
called-DTE	The network address of the host you want to connect with. The number can be up to 15 (17 if TOA/NPI addressing is enabled) digits long (with no embedded blanks).**
calling-DTE	The network address of the PC making the call.**
fac_code	Any of the codes found . Facility codes should be separated with commas shown in the “Facility Request Codes” table.
udata	The letter P or D, or asterisk(*), followed by up to 12 bytes (124 with Fast Select) of data destined for the called-DTE (as opposed to the network). This is where you request services specific to the host you are calling. There should be no blanks embedded within this field. When it assembles your call request packet, X.PAD automatically puts a four-byte code at the beginning of this field. This code identifies the calling computer as an ASCII terminal. The code does not appear on the screen. (These four bytes would be represented in hexadecimal notation as 01,00,00,00.).

**For more information on the structure of DTE Addresses see Appendix C, "User Facilities and DTE Address Structures".

Example One

  XPAD:R,F   92100086,9999  Dpie314

This line represents a fictitious calling-DTE (9999) attempting to place a Reverse Charge call to a called-DTE whose network address is 91200086. The Fast Select Facility is also selected.

Example Two

  XPAD:CALL 92100086

This example shows the alternative form of the call-request command, showing the optional Eicon Technology key word CALL.


CANCEL

Purpose  Terminates LISTEN on the current PAD.

Format

  CANCEL

Output

  LISTEN Canceled


CLR or CLEAR

Purpose  Terminates the connection with the selected host. PAD parameters are restored to their original values.

Format

  CLR   [ udata]

or

  CLEAR  [ udata]

Where udata is user data. The user data field can contain up to 128 characters in conjunction with Fast Select; otherwise, its limit is 16. The format of user data fields is network dependent.

Output

  CLR CONF [fac_code]  <- Call cleared, confirmed>

Where fac_code indicates one of the facility codes that appear in the table “Facility Request Codes”. Additional facility codes indicating the duration of the call, the amount of data sent, and the charges incurred, may appear here if prior arrangements have been made with the network.

Note:
The CLEAR (or CLR) service signal appears for many reasons.


CONNECT

Purpose  Establishes a connection with a remote host. This command allows you full control over the Facilities and User Data fields.

Format

  CONNECT called_DTE [,calling_DTE] [/F facilities][/U user data][ /X param:value..[,param:value]]

Parameter	Description
called_DTE	Up to 15 decimal digits (no spaces allowed). This is the network address of the host computer being called. For more information on DTE address structure, see Appendix C, "User Facilities and DTE Address Structures".
calling_DTE	Up to 15 (17 if TOA/NPI addressing is enabled) decimal digits (no spaces allowed). This is the network address/number of the PC making the call.
facilities	The CCITT has defined the Facilities which may be made available to users. Facility support varies from network to network. Some Facilities are determined for the client at subscription time. Others are available on a per-call basis.
	The facilities field can contain up to 63 bytes. These bytes are encoded as hexadecimal numbers separated by commas. For example, a request for reverse charges would be included in the CONNECT command as follows:
	C   92100086 /F 1,1
	For further information on User Facilities and how they are employed, see Appendix C, "User Facilities and DTE Address Structures".
user data	Up to 128 bytes of data (with Fast Select) destined for the called-DTE (as opposed to the network). This is where you might request services specific to the host you are calling: specify a password, for example. User data is entered as hexadecimal values and/or ASCII strings in quotation marks, separated by commas.
	Note: It is often necessary to include your Protocol I.D. code at the beginning of this field when you call some hosts. The CCITT PAD Protocol I.D. for X.PAD is 1,0,0,0.
parm:value	Specifies the X.3 parameters you want set on the remote PAD. If parameters and values are specified here, then the first thing X.PAD tries to do when a connection is established is to use these values to initialize the remote PAD.

Example

  XPAD:CONNECT 92100086 /F 1,1 /U 1,0,0,0,“pie”,FF

This is how you might call a host computer with the network address 92100086 and request Reverse Charging. The information in the user data field will be passed through to the host computer which will interpret its meaning.


ICLR or ICLEAR

Purpose  Sends an Invitation to Clear to the remote PAD.

Format

  ICLR

or

  ICLEAR

Output

  CLR PAD  < - Call cleared, remote request >

Note:
The CLEAR (or CLR) service signal appears for many reasons.


ID

Purpose   Automatically includes NUI identification in the packets being sent. ID stays in effect until an IDOFF is issued.  The ID command must be issued before you connect with a host.

Format

  ID  NUI string

NUI string format is network dependent.


IDOFF

Purpose  Disables the ID PAD command. The IDOFF command must be issued before you connect to a host.

Format

  IDOFF


INT

Purpose  Sends an interrupt packet to the host without discarding output pending from the host.

Format

  INT


INTD

Purpose  Sends an interrupt packet to the host computer and discards output pending from the host.

Format

  INTD


LANG or LANGUAGE

Purpose Provides an easy way to set X.3 PAD Parameter 6 and enable language support. The files to support the desired language must be in memory when you issue this command. Language support files are configured with the X.PAD Configuration program. See “Configuring X.PAD,” for more information.

Format

  LANG FR[ENCH] EN[GLISH]

or

  LANGUAGE FR[ENCH] EN[GLISH]

The LANGUAGE command also accepts abbreviations for these languages: FR or EN.

Specifying one of these languages will automatically add the base language value to whatever value was already in effect for Parameter 6. For example, if Parameter 6 was set to 1 (show prompt and service signals), then the command

  XPAD: LANG french

would set parameter 6 to 37. For more information, see Appendix E, “X.3 PAD Parameters.”


LISTEN

Purpose  The LISTEN command enables X.PAD to receive incoming calls. Outgoing calls can be issued on a PAD which has a LISTEN in effect. When the connection is hung up, the LISTEN remains pending until terminated by a CANCEL (This is only if AUTO_CONNECT=ANSWER).

When the ECXPAD driver is installed with the AUTO_CONNECT=ANSWER in the X.PAD Configuration program, a LISTEN is issued on all PADs whenever your terminal emulation program enables its DTR. If you wish to issue another LISTEN on any PAD (to use the user data field to restrict access, for example) you must first CANCEL the LISTEN in effect for that PAD.

Format

LISTEN [address ] [/F facilities ] [/U user data] [/X  param:value...[,param:value ]]

Parameter	Description
address	Use this field to restrict access to specified callers. This field accept up to 15 (17 if TOA/NPI addressing is enabled) numerals, allowing you to specify the DTE address from which you wish to accept calls. Wild cards are accepted (e.g. “*” or “?”).
facilities	The CCITT has defined the Facilities which may be made available to users. Facility support varies from network to network. Some Facilities are determined for the client at subscription time. Others are available on a per-call basis. The facilities field can contain up to 63 bytes. These bytes are encoded as hexadecimal numbers separated by commas. For example, a request for access to Closed User Group 13 would be included in the LISTEN command as follows: LISTEN  /F 3,C
	For further information on User Facilities and how they are employed, see the appendix on "User Facilities and DTE Address Structures".
user data	Up to 128 bytes of data (with Fast Select) destined for the called-DTE (as opposed to the network). This is where you might request services specific to the host you are calling: specify a password, for example. User data is entered as hexadecimal values and/or ASCII strings in double quotation marks, separated by commas. For example:
	LISTEN /U "Eicon Technology",1,0,0,0,"Connecting People to Information"
param:value	Specifies the X.3 parameters you want set on the remote PAD. If parameters and values are specified here, then the first thing X.PAD tries to do when a connection is established is to use these values to initialize the remote PAD.

Output

LISTENING calling_DTE  FAC: facilities user_data


PAR or PAR?

Purpose  Displays all the X.3 PAD parameters and values of the active PAD profile. Or, displays the values of selected X.3 PAD parameters of the active PAD profile.

X.3 PAD Parameters can be specified by name or number.

Format

  PAR [ param...[,param ]  ]
  PAR? [ param...[,param ] ]
  PARAMETER [ param...[,param ] ]
  READ  [ param...[,param ] ]

Parameter	Description
param	Specifies an X.3 PAD Parameter.

Example One

  XPAD:PAR?

Example One Output

  XPAD: PAR 1:1,2:1,3:2,4:0,5:0,6:5,7:21,9:2,10:0,11:0,12:1,13:4,14:0,15:1,16:127,17:24,18:18,19:2,20:0,21:0,22:0

Example Two

  XPAD:read, esc,fol

Example Two Output

  XPAD:PAR 1:1, 10:0

This displays the current values for X.3 PAD parameters 1 and 10.

Example Three: Extended Service Signals in English

  XPAD:par ech, sig

Example Three Output

  XPAD: PAR 2:1, 6:5


PROF or PROFILE

Purpose  Assigns one of the predefined profiles to the active PAD. Predefined profiles are initialized through the X.PAD Configuration program.

You can display the parameters of a predefined profile using the PROF? command.

Format

 PROF profname

or

  PROFILE  profname

where profname specifies one of the seven predefined profiles defined in the X.PAD Configuration program.


PROF?

Purpose  Displays all X.3 PAD parameters and their values for one of the predefined profiles. Predefined profiles are initialized through the X.PAD Configuration program.

You can activate a predefined profile for the current PAD using the PROF command.

Format

  PROF? profname

where profname specifies one of the seven predefined profiles defined in the X.PAD Configuration program.

Example

  XPAD:Prof? standard

Example Output

  XPAD:PAR
  1:1,2:1,3:2,4:0,5:0,6:5,7:21,9:2,10:0,11:0,12:1,13:4,14:0,15:1,16:127,
  17:24,18:18,19:2,20:0,21:0,22:0.


PVC

Purpose  Instructs X.PAD to use one of the X.25 permanent virtual circuits (PVCs) defined in your X.25 network subscription. The n parameter indicates which PVC to use, and is related to the Number of PVCs parameter contained in the X.25 Configuration screen of the WAN Services Configuration program.

Format

  PVC n

Example One

  PVC 27

Example One Output

  COM

Example Two

  PVC

Example Two Output

  CLR DTE C:0 D:1

Note:
Entering PVC without a parameter disconnects the call.


RESET

Purpose  Sets the counters on the current connection to zero without breaking the connection with the host computer. All pending data is discarded.

Format

  RESET

Example

  XPAD:RESET

Output

  RESET DTE cause <-Reset by remote device, data may be lost >

Where cause is one of the X.25 diagnostic codes listed in Appendix C, “User Facilities and DTE Address Structure”.


RPAR? or RREAD

Purpose Requests X.3 Parameters of the remote PAD (the one being used by the host computer). Since the information requested may be proceeded by data packets already in transit from the host, you should return to Terminal Mode (Data Mode) for a few seconds to allow the EiconCard time to process the pending data. Then, return to Command mode and issue the RRET Command.

X.3 PAD Parameters can be specified by name or number.

Format

  RPAR   [ param:value...[,param:value ] ]

or

  RREAD [param:value...[,param:value ] ]

Parameter	Description
param	Specifies an X.3 PAD Parameter.
value	Specifies an X.3 PAD Parameter value.


RRET

Purpose  Reads the X.3 parameters returned by the RPAR? or RREAD Command.

Format

  RRET

Example

  XPAD:RRET

Example Output

  XPAD: PAR 1:1,10:60


RSET or RSETREAD

Purpose  Sets and lists the X.3 parameters of the remote PAD.

Format

  RSET [param:value...[,param:value ]  ]

or

  RSETREAD [param:value...[,param:value ] ]

Parameter	Description
param	Specifies an X.3 PAD Parameter.
value	Specifies an X.3 PAD Parameter value.

Example

  XPAD: RSET  ech:0, signals:0

Example Output

  XPAD: PAR 2:0,6:0


SET

Purpose  Sets the values of specified X.3 PAD parameters in the active PAD without redisplaying them. X.3 PAD Parameters can be specified by name or number.

Format

  SET param:value...[,param:value ]

Parameter	Description
param	Specifies an X.3 PAD Parameter.
value	Specifies an X.3 PAD Parameter value.
Example

XPAD:SET 10:60,13:0

Example Output

  XPAD:


SET? or SETREAD

Purpose   Sets the values of specified X.3 PAD parameters in the current PAD and redisplays them. X.3 PAD Parameters can be specified by name or number.

Format

  SET? param:value...[,param:value ]

or

  SETREAD   param:value...[,param:value ]

Parameter	Description
param	Specifies an X.3 PAD Parameter.
value	Specifies an X.3 PAD Parameter value.

Example

  XPAD:SET? 10:60,13:0

Example Output

  XPAD:PAR 10:60,13:0


STAT or STATUS

Purpose  Ascertains whether the current PAD is engaged or free. Use the Eicon Technology command STAT? for more detailed information.

Format

  STATUS or STAT

Output

  ENGAGED < - Call established >

or

  FREE  < - No call established >


STAT?

Purpose  Displays information about the connection.

Format

  STAT?

Output

  ENGAGED -  called_DTE  FAC: fac_code udata  <-Call established>

or

  LISTENING -   called_DTE  FAC: fac_code udata

or

  FREE   < - No call established >

Where fac_code and udata indicate the facilities and user data specified with CALL, CONNECT, or LISTEN.


Appendix F: X.28 and X.29 Commands

X.29 Commands (PAD Messages)

X.29 commands (PAD messages) are the signals exchanged between the remote and local computers over the X.25 networks. Here is a list of the X.29 commands and their meanings.

	X.29 Command	Result
0	Set	Remote computer sets local X.3 parameters.
1	Set and Read	Remote computer sets and reads local X.3 parameters.
2	Indication	Local PAD (X.PAD) sends requested X.3 parameters to remote computer.
3	Read	Remote computer reads local X.3 parameters.
4	Invitation to clear	Connection is cleared by local PAD (X.PAD).
5	Error	Local PAD (X.PAD) sends a RESET to remote computer.
6	Indication of break	Remote parameter 8 is reset for normal delivery.
7	Reselection	Call will be redirected to another destination.
8	TOA/NPI	Call will be redirected to another destination (if TOA/NPI addressing is enabled).