manual teletrol network router

MANUAL TELETROL NETWORK ROUTER

Rev. 4.00

Teletrol Network Router Manual

Part No. 94-097

Teletrol Systems Inc. Technology Center

286 Commercial Street Manchester, NH 03101-1109

Phone: 603-645-6061 Fax: 603-645-6174 Internet: www.teletrol.com

Manual contents may not be reproduced in whole or in part without prior written permission of Teletrol Systems Inc. Copyright © 1999 by Teletrol Systems, Inc. All rights reserved. The following products are trademarks of their respective companies: Windows, Ethernet, ARCNet, IP, IPX.

Manual Revision History

Rev. No. Rev. Date Description 1.10 09/94 General release. 2.00 12/94 Added IP TNR configuration. 3.00 02/97 Added Plug-and-Play Ethernet card support. 4.00 05/99 Manual was reorganized, revised, and updated.

Rev. 4.00 Preface

Teletrol Network Router Manual Page i

Preface

Network Requirements

The Teletrol Network Router is designed to work in conjunction with the following.

Backbone (Wide Area) Networks:

• 10 Mbps Ethernet Network. • 2.5 Mbps ARCNet Network.

Internetworking Protocols:

• IP. • IPX.

Local Area Networks (LANs):

• TELNET (Teletrol’s proprietary high-speed LAN). • ARCNet.

Workstation Requirements

The Teletrol Network Router requires a workstation running one of the following software programs:

• MCP (version 5.10 or higher). • Ensemble. • CCIM.

Software Requirements

In order to use the Teletrol Network Router on a Teletrol network of controller, the controllers must have firmware version 5.10 or above, and the workstations must have Ensemble or MCP (version 5.10 or higher) or CCIM. All versions of Ensemble as well as firmware and MCP versions 5.10 and higher reference controller and workstation addresses with a Segment number in addition to the Node number. The Segment/Node addressing scheme is required for the Teletrol Network Router.

Preface Rev. 4.00

Page ii Teletrol Network Router Manual

How the Manual is Organized

This manual includes the following chapters.

Chapter 1: Introduction to the Teletrol Network Router

This chapter provides an introduction to the Teletrol Network Router (TNR). An overview of the function of the TNR within the Teletrol network is presented. Additionally, the hardware components of the TNR are illustrated and described.

Chapter 2: Installing the Teletrol Network Router

This chapter lists the steps required to install the Teletrol Network Router, including the instructions for installing the TNR Software Key.

Chapter 3: Configuring the Teletrol Network Router

This chapter provides instructions for configuring the TNRs attached to your network. Separate instructions are given for IP and IPX protocols.

Chapter 4: Configuring the Workstations

This chapter provides instructions for configuring the workstations attached to your network. Separate instructions are given for IP and IPX protocols.

Chapter 5: Diagnostics

This chapter provides instructions on using the Diagnostics port on the TNR. It also provides instructions for verifying the setup of TNRs on the network.

Appendix A: Reconfiguring the Media Type for TNR Cards

This chapter provides instructions for reconfiguring the media type of Ethernet and ARCNet cards. These cards are shipped already configured; you only have to change the configuration if you use the TNR on a different network than originally intended.

Associated Manuals

Have the hardware and software manuals for your workstation and network handy. In addition, you may need to refer to the Teletrol Network Installation Manual (part number 94-005).

Naming Conventions

The Teletrol Network Router is the official name of the product. In this manual, it is commonly referred to simply as the “TNR.” A distinction is made between the IP Router and the Teletrol Network Router (TNR).

Rev. 4.00 Table of Contents

Teletrol Network Router Manual Page T-1

Teletrol Network Router Manual Table of Contents

1.0 Introduction to the Teletrol Network Router.................................................... 1-1

1.1 Overview of the Teletrol Network Router.......................................................................................... 1-1

1.2 Teletrol Network Router Hardware Overview................................................................................... 1-3

1.2.1 TNR Enclosure........................................................................................................................ 1-3

1.2.2 Power Supply .......................................................................................................................... 1-4

1.2.3 Floppy Drive ........................................................................................................................... 1-4

1.2.4 TELNET or ARCNet Card for Teletrol’s High-Speed LAN.............................................. 1-5

1.2.5 Ethernet or ARCNet Card for the Backbone Network ...................................................... 1-5

1.2.6 TNR Software Key ................................................................................................................. 1-6

2.0 Installing the Teletrol Network Router............................................................. 2-1

2.1.1 Installing the TNR Software Key......................................................................................... 2-1

3.0 Configuring the Teletrol Network Router......................................................... 3-1

3.1 Configuring the TNR for IPX............................................................................................................... 3-2

3.1.1 Specifying the TNR Address for IPX Networks................................................................ 3-2

3.2 Configuring the TNR for IP.................................................................................................................. 3-7

3.2.1 Understanding IP Addresses ............................................................................................... 3-8

3.2.2 Assigning the IP Address and System Network Address to the TNR........................ 3-11

3.2.3 Advanced Configuration Setup for IP .............................................................................. 3-14

4.0 Configuring the Workstations ............................................................................ 4-1

4.1 Configuring a Workstation for the IPX Protocol.............................................................................. 4-2

4.1.1 Configuring an Ensemble Workstation for IPX................................................................. 4-2

4.1.2 Configuring an MCP Workstation for IPX......................................................................... 4-2

4.2 Configuring a Workstation for the IP Protocol................................................................................. 4-4

4.2.1 Configuring an Ensemble Workstation for IP.................................................................... 4-4

4.2.2 Configuring an MCP Workstation for IP............................................................................ 4-5

5.0 Diagnostics .......................................................................................................... 5-1

5.1 Using the Serial/Diagnostics Port....................................................................................................... 5-1

5.2 Verifying TNR Communication Using the Serial/Diagnostic Port ................................................. 5-4

Table of Contents Rev. 4.00

Page T-2 Teletrol Network Router Manual

Appendix A: Reconfiguring the Media Type for TNR Cards .....................................A-1

A.1 Ethernet and ARCNet Port Connectors ............................................................................................A-1

A.1.1 Ethernet Cards .......................................................................................................................A-1

A.1.2 ARCNet Cards .......................................................................................................................A-2

A.2 Reconfiguring Hardware-Configurable Cards..................................................................................A-3

A.2.1 Ethernet Card with W9 and W10 Jumpers.........................................................................A-4

A.2.2 Ethernet Card with J5 and J6 Jumpers ................................................................................A-5

A.2.3 ARCNet Card with JP9 and JP10 Jumpers .........................................................................A-6

A.3 Reconfiguring Software-Configurable Cards...................................................................................A-7

A.3.1 Reconfiguring the Ethernet Card for a TNR with an AMI BIOS....................................A-8

A.3.2 Reconfiguring the Ethernet Card for a TNR with an Award BIOS...............................A-11

Index ...............................................................................................................................I-1

1.0 Introduction to the Teletrol Network Router.................................................. 1-1

1.1 Overview of the Teletrol Network Router....................................................................................... 1-1

1.2 Teletrol Network Router Hardware Overview............................................................................... 1-3

1.2.1 TNR Enclosure ....................................................................................................................... 1-3

1.2.2 Power Supply.......................................................................................................................... 1-4

1.2.3 Floppy Drive........................................................................................................................... 1-4

1.2.4 TELNET or ARCNet Card for Teletrol’s High-Speed LAN ......................................... 1-5

1.2.5 Ethernet or ARCNet Card for the Backbone Network.................................................... 1-5

1.2.6 TNR Software Key ................................................................................................................ 1-6

Rev. 4.00 Introduction to the Teletrol Network Router

Teletrol Network Router Manual Page 1-1

1.0 Introduction to the Teletrol Network Router

The Teletrol Network Router (TNR) functions as a gateway between an Ethernet or ARCNet network (using an IP or IPX protocol) and the Teletrol network. The TNR connects Teletrol’s high-speed LAN (TELNET or ARCNet, referred to as the System network) to a Wide Area Network (WAN). The Wide Area Network can be either a 10 Mbps Ethernet network or a 2.5 Mbps ARCNet network. The Wide Area Network is referred to in the remainder of this manual as the Backbone network or WAN.

1.1 Overview of the Teletrol Network Router

The TNR directly connects the Teletrol Integrator building automation system to a WAN. The TNR design and implementation adheres to the IEEE established protocol standards for 10 Mbps Ethernet/2.5 Mbps ARCNet networks using the IPX or IP internetworking protocol. This allows Teletrol controllers to communicate via the same WAN that connects other computer systems in a facility. This configuration allows up to 150 workstations running Ensemble, MCP, or CCIM software on the Backbone network to communicate with any controller on a Teletrol System network.

Each TNR interfaces a System network of up to 99 Teletrol controllers to an enterprise-wide Backbone network. The system architecture supports up to 254 TNRs, each of which is a node on the Backbone network. In addition to providing an interface to a WAN, the TNR expands the Teletrol network architecture, allowing up to 25,146 Teletrol controllers (not including unitary TSC controllers) and 6,754 network workstations (not including direct-connect and modem workstations).

Introduction to the Teletrol Network Router Rev. 4.00

Page 1-2 Teletrol Network Router Manual

The figure below illustrates a system architecture that uses a TNR to connect the Teletrol controllers to a WAN.

System Architecture using a TNR Figure 1-1



1.2 Teletrol Network Router Hardware Overview

This section provides an overview of the TNR hardware that includes the following components.

• TNR Enclosure

• TNR Power Supply

• TNR Floppy Drive

• TELNET or ARCNet Card for Teletrol’s High-Speed LAN

• Ethernet Card for the Ethernet Backbone network, or ARCNet Card for the ARCNet Backbone network

• TNR Software Key

Each of these hardware components is described in the sections that follow.

1.2.1 TNR Enclosure

The TNR enclosure is approximately 9.5 inches (240 mm) wide by 8.7 inches (220 mm) deep by 2.5 inches (65 mm) high. All network and power connections are accessible from the rear of the TNR as shown in Figure 1-2.

1 3 2

4 5 6 7 8 9

1. System Power Switch 4. Keyboard Port 7. Serial Port 2 2. System Network Card 5. Display Port 8. Serial Port 1 (Diagnostics) 3. Backbone Network Card 6. Printer Port 9. System Power Jack

Rear View of TNR Enclosure Figure 1-2



1.2.2 Power Supply

The TNR uses an external power supply with an operating voltage range of 90 VAC to 260 VAC. The power supply is approximately 6.5 inches (165 mm) wide by 3.15 inches (80 mm) deep by 2.17 inches (55 mm) high and plugs into the rear of the enclosure. Refer to Figure 1-3 for the location of the system power jack.

Power Supply

Connecting the External Power Supply to the Enclosure Figure 1-3

1.2.3 Floppy Drive

The TNR uses a 3.5 inch floppy disk drive, accessible from the front of the unit, to load the TNR Boot Disk. The TNR Boot Disk comes with the TNR unit; it contains the software that detects and configures the installed network cards when you boot the TNR.

Insert the TNR Boot Disk into the floppy drive at installation time to configure the router; this procedure is described in the “Configuring the Teletrol Network Router” chapter of this manual. You must insert the TNR Boot Disk in the floppy drive every time you power up or reboot the TNR.



1.2.4 TELNET or ARCNet Card for Teletrol’s High-Speed LAN

Teletrol installs a System network card in the TNR based on your network requirements. A standard Teletrol TELNET network card is installed in the TNR to provide a connection to the Teletrol TELNET 250K baud RS-485 System network, or a Teletrol ARCNet network card is installed to provide a connection to a Teletrol 2.5 Mbps System network. The cable connected to the System network card connects the TNR to a System network segment that can support up to 99 Teletrol controllers (Integrator, ICS, AHC and MINC) and up to 26 workstations. The TNR can be physically located at any point along the System network segment. Refer to Teletrol’s Network Installation Manual for more information on installing and configuring networks.

Note: The MINC can be installed only on Teletrol’s high-speed LAN network.

1.2.5 Ethernet or ARCNet Card for the Backbone Network

The TNR is shipped with either an Ethernet card or an ARCNet card for the Backbone network; you specify which card when you order the Teletrol Network Router. Both cards are described in this section.

Ethernet Card for the Ethernet Backbone Network

The 10 Mbps Ethernet card provides connectors to support two different media types commonly used with Ethernet. The first interface is to 10BASE-2, a 10 Mbps Baseband network (frequently referred to as Cheapernet). Cheapernet’s thin 50 ohm coaxial cable (RG-58A/U) supports a maximum of 30 nodes (or mating connectors) on a cable segment, each segment having a maximum length of 606 feet (185m). This interface requires the use of the BNC connector located on the Ethernet card. The BNC connector must be terminated at both ends.

The second interface is to 10BASE-T, a 10 Mbps Baseband Twisted Pair. This interface is defined by Section 14 of IEEE 802.3, and uses point-to-point cabling and repeaters to provide network services. There is no maximum node count defined for this interface. Each physical network segment can be a maximum of 328 feet (100m) in length. This interface requires the use of the RJ-45 connector located on the Ethernet card. (Older Ethernet cards may have an AUI connector.)

Teletrol workstations can be connected directly to the Ethernet. The workstation software (either Ensemble, MCP version 5.1 or higher, or CCIM) supports any Ethernet card that comes with Novell-compatible ODI drivers. Up to 150 Teletrol Ethernet workstations can be connected to the Ethernet. At any given time, however, only 26 workstations can be logged onto a single controller.

ARCNet Card for the ARCNet Backbone Network

The Teletrol ARCNet card provides connectors to support the two media types commonly used with ARCNet. The first interface uses a 93 ohm coaxial cable (RG-62/U) and requires the use of the BNC connector located on the ARCNet card. The BNC connector must be terminated at both ends. The second interface is a twisted-pair interface (IBM Type 3 Media Compatible Cable such as Belden 1154A or 1155A). Cable distance and load limitations must be considered with the TNR as they are currently documented for workstations and controllers. Refer to Teletrol’s Network Installation Manual for more information.



1.2.6 TNR Software Key

The TNR software is protected by the TNR Software Key. This key must be installed on the printer port of the TNR before applying power to the TNR. The TNR will not operate unless the TNR Software Key is installed.

2.0 Installing the Teletrol Network Router................................................................ 2-1

2.1.1 Installing the TNR Software Key........................................................................................ 2-1

Rev. 4.00 Installing the Teletrol Network Router


2.0 Installing the Teletrol Network Router

This chapter provides the instructions for installing the Teletrol Network Router (TNR). The configuration instructions for the Router and the Workstation are provided in subsequent chapters.

Installing the Teletrol Network Router consists of four simple steps:

Step 1: Install the TNR Software Key in the printer port of the TNR as described in the ‘Installing the TNR Software Key’ section of this chapter.

Step 2: Attach the network cable connectors to the network ports (see Figure 1-2 in the “Introduction to the Teletrol Network Router” chapter of this manual for the location of the network ports).

Step 3: Configure the TNR Boot Disk for the TNR (see the “Configuring the Teletrol Network Router” chapter of this guide).

Step 4: Supply power to the unit (see Figure 1-2 in the “Introduction to the Teletrol Network Router” chapter of this manual for the location of the system power jack).

When you complete these three steps, you are ready to configure the TNR as described in the next chapter.

2.1.1 Installing the TNR Software Key

The TNR software is protected by the TNR Software Key. This key must be installed in the printer port of the TNR when you supply power to the unit. Figure 2-1 below shows the location of the printer port on the rear of the TNR unit.

Note: The TNR will not operate unless the TNR Software Key is installed.

PRINTER

TeletrolTNR

SoftwareKey

Rear view of the TNR

Installing the TNR Software Key Figure 2-1

3.0 Configuring the Teletrol Network Router....................................................... 3-1

3.1 Configuring the TNR for IPX............................................................................................................ 3-2

3.1.1 Specifying the TNR Address for IPX Networks .............................................................. 3-2

3.2 Configuring the TNR for IP ............................................................................................................... 3-7

3.2.1 Understanding IP Addresses ................................................................................................ 3-8

3.2.2 Assigning the IP Address and System Network Address to the TNR ........................ 3-11

3.2.3 Advanced Configuration Setup for IP .............................................................................. 3-14

Rev. 4.00 Configuring the Teletrol Network Router


3.0 Configuring the Teletrol Network Router

This chapter describes how to configure the TNR for your network. Before you begin, ensure that the TNR Software Key is installed (see the “Installing the Teletrol Network Router” chapter of this manual for instructions).

The method of configuring the TNR depends upon which type of communications protocol you are using — IPX or IP. If you are using IPX, see the ‘Configuring the TNR for IPX’ section of this chapter. If you are using IP as your communications protocol, see the ‘Configuring the TNR for IP’ section of this chapter. Note that you are required to specify the communication protocol you will be using when you order the TNR. The version of the TNR Boot Disk you received with the TNR should correspond to the communication protocol you specify.

IMPORTANT!

Be sure to contact the Information Services (IS) personnel responsible for the Backbone network prior to connecting a TNR to the network.

Configuring the Teletrol Network Router Rev. 4.00


3.1 Configuring the TNR for IPX

If you are using the Teletrol Network Router with the IPX communication protocol, use the instructions in this section to configure the TNR for your network.

3.1.1 Specifying the TNR Address for IPX Networks

Every TNR must be assigned a Backbone Network Number and a unique System Network Number. Providing the TNR Boot Disk is NOT write-protected, it will automatically detect and configure the installed network cards when you boot the TNR.

While the Auto-Detect feature identifies and configures network cards, it is unable to automatically assign System Network (Segment) Numbers or Backbone Network Numbers. You must specify these values by editing the TIR line in the TNR Boot Disk’s AUTOEXEC.BAT file. You can edit the AUTOEXEC.BAT file on any PC using any ASCII text editor (for example, Windows Notepad).

The TNR Boot Disk is shipped with a default configuration of:

Backbone Network Number 0 System Network (Segment) Number 1

In the TIR line in the AUTOEXEC.BAT file, the first parameter is the default Backbone Network Number (0) and the second is the default System Network Number (1). The default TIR values shown below should be changed as required.

TIR 0 1

If you have only one network segment, for example, three TNRs and two workstations connected by thin Ethernet (coax cable) with no other network hardware (servers, gateways, etc.), then you have a single-segment Backbone network and do not need to specify a Backbone Network Number. In this case, leave the first parameter to TIR as a zero (0) value.

However, if your Backbone network is a multi-segmented network (more than one segment connected by a non-Teletrol network router or gateway), or your Backbone network has a Novell server, then obtain the Backbone Network Number from the router, gateway, or server. For Novell servers, run the server Monitor utility and select LAN Information>LAN Driver Information. The Backbone Network Number displays in the LAN Driver Information for each network segment. Enter the Backbone Network Number as the first parameter to TIR. The example below shows a Backbone Network Number of F0.

TIR F0 1

Specify the unique System Network (Segment) Number by entering it as the second parameter to the TIR program. Each TNR has one System network for which it routes packets to and from the Backbone network. Each System network must be identified by a number (1 through 254). No two TNRs attached to the same WAN can have the same System Network (Segment) Number — even if the two TNRs reside on different Backbone networks.

To specify the System Network (Segment) Number for the TNR, change the second parameter in the TIR line in the TNR Boot Disk’s AUTOEXEC.BAT file. After you edit the line and save the changes to this file, insert the TNR Boot Disk back into the TNR and reboot the unit. This configures the TNR with the new System Network (Segment) Numbers specified in the AUTOEXEC.BAT file.

Note: The AUTOEXEC.BAT is read only during the initial power-up cycle. To enable the changes you make to the file, the TNR must be re-booted.



A sample of the AUTOEXEC.BAT file located on the TNR Boot Disk follows.

@ECHO OFF A: PROMPT $p$g MODE COM1:9600,N,8,1 CTTY COM1 IF EXIST NET.CFG DEL NET.CFG ::---------------------------------------------------------------------- :: The following environment variables determine which network type is :: to be used for the backbone and system network segments. ::---------------------------------------------------------------------- :: Delete the "rem" before the desired backbone network type. rem SET BACKBONE=ETHERNET rem SET BACKBONE=ARCNET ::---------------------------------------------------------------------- :: Delete the "rem" before the desired system (controller) network type. rem SET SYSTEM_SEG=TELNET rem SET SYSTEM_SEG=ARCNET ::---------------------------------------------------------------------- :: If these variables are to be used instead of auto-detection, delete :: the "rem" before the following GOTO statement to skip auto-detection. rem GOTO BOOT_IT ::------------------------------------------------------------------------ :: Look for and determine the type of backbone and system segment networks. A:\NIDETECT IF ERRORLEVEL 4 GOTO AA IF ERRORLEVEL 3 GOTO AT IF ERRORLEVEL 2 GOTO EA IF ERRORLEVEL 1 GOTO ET GOTO GOODBYE :ET SET BACKBONE=ETHERNET SET SYSTEM_SEG=TELNET GOTO BOOT_IT :EA SET BACKBONE=ETHERNET SET SYSTEM_SEG=ARCNET GOTO BOOT_IT :AT SET BACKBONE=ARCNET SET SYSTEM_SEG=TELNET GOTO BOOT_IT :AA SET BACKBONE=ARCNET SET SYSTEM_SEG=ARCNET

TNR Boot Disk AUTOEXEC.BAT File (Automatic Network Detection Portion) Figure 3-1



:BOOT_IT IF "%BACKBONE%" == "ETHERNET" COPY NET.ETH NET.CFG > NUL IF "%BACKBONE%" == "ARCNET" COPY NET.ARC NET.CFG > NUL IF EXIST NET.CFG GOTO START ECHO Could not create file NET.CFG! Is the disk write-protected? GOTO GOODBYE :START ECHO Backbone network segment type is: %BACKBONE% ECHO Teletrol system segment type is: %SYSTEM_SEG% LSL IF "%BACKBONE%" == "ETHERNET" NIC2000 IF "%BACKBONE%" == "ARCNET" TARCMLID IPXODI IF "%SYSTEM_SEG%" == "TELNET" TSINET 100 IF "%SYSTEM_SEG%" == "ARCNET" TARCMLID IF "%SYSTEM_SEG%" == "ARCNET" MCPODI TIR 0 1 çç Specify the Backbone Network Number & System Network (Segment) Number for IPX :GOODBYE IF EXIST NET.CFG DEL NET.CFG SET BACKBONE= SET SYSTEM_SEG=

TNR Boot Disk AUTOEXEC.BAT File (Driver Load and TIR Execution Portion) Figure 3-2



Configuration Files for the Network

Two network configuration files are located on the TNR Boot Disk: NET.ETH and NET.ARC. The NET.ETH file is the network driver configuration file for the Ethernet Backbone network; the NET.ARC file is the network driver configuration file for the ARCNet Backbone network. When the TNR boots, the appropriate NET file is copied automatically to the NET.CFG required by the network drivers in order to initialize the network cards properly. If you are using an Ethernet Backbone network, you do not need to edit information in these files. If you are using an ARCNet Backbone network, follow the instructions in the next section.

Additional Requirements for the ARCNet Backbone

If you ordered a TNR configured to use ARCNet for the Backbone network, there is one additional configuration step required before the TNR can communicate properly on the ARCNet Backbone network — specifying the Node Address in the NET.ARC file. In the file NET.ARC, there are two sections for ARCNet cards — the first section is used if the ARCNet is on the Backbone network, the second section is used if the ARCNet is on the System network.

For an ARCNet Backbone network, the node address of the Backbone network card must be the same as the System (Segment) Network Number. The NET.ARC file specifies the ARCNet node address as a 12 digit hexadecimal value between 01h and FEh (the first 10 digits are always zero).

Using a text editor, edit the NET.ARC file and change the Node Address (the default is 000000000001h ) so that it matches the TNR’s System (Segment) Network Number. Save the file to the TNR Boot Disk, then insert the disk in the TNR’s floppy disk drive and reboot the unit.

Note: The NET.ARC file is read only during the initial power-up cycle. To enable changes to the file, the TNR must be re-booted.



An example of the Network Driver Configuration File (NET.ARC) is shown below.

PROTOCOL IPXODI BIND #1 PROTOCOL MCPODI BIND #2 #------------------------------------------------------------------------------ #Ethernet Backbone Configuration #Link driver NIC2000 # INT 5 # PORT 300 # FRAME ETHERNET_802.3 #------------------------------------------------------------------------------ #Arcnet Backbone Configuration Link driver TARCMLID INT 5 PORT 300 Node Address 000000000001h çç Specify the Node Address for the

ARCNet Backbone only #Note: The physical address of the ARCNet card must match the system segment # address assigned to the Teletrol Network Router #------------------------------------------------------------------------------ #Arcnet System Segment Configuration - Address must be 64h (100 decimal) Link driver TARCMLID INT 7 PORT 330 Node Address 000000000064L Protocol MCPODI CB NOVELL_RX-NET

Network Driver Configuration File - NET.ARC Figure 3-3



3.2 Configuring the TNR for IP

If you are using the TNR with the IP communication protocol, use the instructions in this section to configure the TNR for your network. An overview of the steps required is presented below.

Step 1: Obtain the Site Network Topology map showing all installed IP Routers and/or workstations along with their corresponding IP Addresses.

Step 2: Determine where the IP TNRs will be located physically on the site’s IP network.

Step 3: Assign an IP Address to the IP TNR. This address is based on the location of each IP TNR on the network.

Step 4: Assign a unique System Network Address (1-254) to each TNR on the IP network.

Step 5: Install the PC/TCP Kernel on every MCP or CCIM workstation communicating with the controllers via the IP TNR. Workstations located on the System Network (that is, TELNET or ARCNet networks) do NOT require this software; neither does a workstation running Ensemble.

The sections that follow briefly describe what an IP Address is and how it is assigned to TNRs. Information on configuring the workstations is presented in the “Configuring the Workstations” chapter of this manual.



3.2.1 Understanding IP Addresses

In a IP network, each computer or host has an IP Address that uniquely identifies it. An IP Address encodes the identification of the network to which the host attaches as well as the identification of a unique host on that network. IP Addresses are 32-bit numbers, conventionally expressed in dotted decimal notation. Dotted decimal notation addresses are written as four decimal integers separated by decimal points, where each integer gives the value of one octet of the IP Address. Then value of each octet can be no larger than 254. An example of a typical IP Address represented in the dotted decimal notation is shown below.

128.10.2.30

IP Addresses are broken down into three primary classes as illustrated below.

32 24 16 8 0

Class A Net ID Host ID

Class B Net ID Host ID

Class C Net ID Host ID

IP Address Classes Figure 3-4

The difference between each class is the number of bits allocated to the Net ID and Host ID. The class of an IP Address can be determined from the three higher-order bits. Class A addresses, which are used for the handful of networks that have more than 216 (65,536) hosts, devote 7 bits to Net ID and 24 bits to Host ID. Class B addresses, which are used for intermediate size networks that have between 28 (256) and 216 (65,536) hosts, allocate 14 bits to the Net ID and 16 bits to the Host ID. Finally, Class C networks, which have less than 28 (256) hosts, allocate 21 bits to the Net ID and only 8 bits to the Host ID.

IP Addresses can be used to reference network addresses as well as individual hosts. By convention, the network address has the Host ID set to zero (0).

Note: IP Addresses 255.255.255.255 and 127.nnn.nnn.nnn are reserved.



Figure 3-5 shows an example of an IP network topology map. This IP network consists of two IP networks connected via an IP Router (this is an IP Router — NOT a TNR). The purpose of the IP Router is to provide network traffic isolation between the two IP networks. The IP Router only allows packets to pass through if they are destined for a node that is located on the other IP network. Two ports on the IP Router are assigned IP Addresses; one IP Address is assigned for each network.

IP Network Map with WAN Workstations Figure 3-5

Each host or node on the network must be assigned a unique IP Address based on its physical location on the network. Since an IP Address consists of the Net ID and Host ID, all hosts located on the same IP network must have the same Net ID with a unique Host ID. For example, all hosts located on Network 1 shown above must have a Net ID of 129.1.0 .



If four IP TNRs were added to the network, two IP TNRs on Network 1 and two IP TNRs on Network 2, the network setup would appear as shown in Figure 3-6.

IP Network Map with TNRs Figure 3-6

Each IP TNR must be assigned a unique IP Address based on its location on the network, along with a unique System Network Address (1-254). The IP Address assigned to an IP TNR must adhere to the IP Addressing convention implemented at the site. Prior to assigning any IP Addresses, consult with the Network Administrator.

In Figure 3-6, the Class C addressing scheme was used. TNRs located on Network 1 must be assigned a Net ID of 129.1.0 , and TNRs located on Network 2 must be assigned a Net ID of 129.33.0 . The Host ID of each TNR is arbitrary, but must be unique.

In the example above, the following Host IDs (IP Addresses) are assigned.

Teletrol Workstation or TNR IP Address Teletrol Network Router 1 (TNR_1) 129.1.0.40

Teletrol Network Router 2 (TNR_2) 129.1.0.50

Teletrol Workstation 101 129.1.0.30



Teletrol Workstation 150 129.33.0.10



3.2.2 Assigning the IP Address and System Network Address to the TNR

To configure the TNR, you must assign it an IP Address and a System Network Address. You do this by editing the contents of two files located on the IP TNR Boot Disk.

• PCTCP.INI • AUTOEXEC.BAT

Assign the TNR’s IP Address in the PCTCP.INI file. Assign the System Network Address in the AUTOEXEC.BAT file.

Assigning the IP Address in the PCTCP.INI File

Using an ASCII text editor, edit the PCTCP.INI file located in the \PCTCP sub-directory on each IP TNR Boot Disk. Assign each TNR its own unique IP Address by specifying the IP Address in the ip-address= line. Ensure that the subnet-mask= line correctly identifies the subnet mask for the network. Consult your Network Administrator to obtain this information. Once the file is correct, save it to the TNR Boot Disk. Insert the disk in the TNR’s floppy disk drive and reboot the unit.

An example of the IP TNR PCTCP.INI file is shown below.

[pctcp general] time-zone = EST time-zone-offset = 300 etc-dir = A:\pctcp [pctcp kernel] interface = ifcust 0 host-table=a:\PCTCP\HOSTS mtu-discovery = yes multicast = no pktdrv-loopback = yes router-discovery = no kernel-does-dns = yes [pctcp ifcust 0] ip-address = 129.1.0.40 çç Specify the IP Address subnet-mask = 255.255.255.0 çç Specify the Subnet Mask router = 129.1.2.2 [pctcp time] dst-begins = 97 dst-ends = 305

IP TNR PCTCP.INI File Figure 3-7



Assigning the System Network Address in the AUTOEXEC.BAT File

Each IP TNR must be assigned a unique System Network Address. The System Network Address is assigned by passing a command line argument to the IPTIR.EXE program. To assign the System Network address, edit the IPTIR line in the AUTOEXEC.BAT file located on the IP TNR Boot Disk. Valid System Network addresses are 1 through 254. The format for the IPTIR statement is shown below.

IPTIR (System Network Address)

An example of the IP TNR’s AUTOEXEC.BAT file is shown below.

@ECHO OFF A: PROMPT $p$g MODE COM1:9600,N,8,1 CTTY COM1 SET PCTCP=A:\PCTCP\PCTCP.INI IF EXIST NET.CFG DEL NET.CFG ::--------------------------------------------------------------------------- :: The following environment variables determine which network type is to be :: used for the backbone and system network segments. ::--------------------------------------------------------------------------- :: Delete the "rem" before the desired backbone network type rem SET BACKBONE=ETHERNET rem SET BACKBONE=ARCNet ::--------------------------------------------------------------------------- :: Delete the "rem" before the desired system (controller) network type rem SET SYSTEM_SEG=TELNET rem SET SYSTEM_SEG=ARCNet ::--------------------------------------------------------------------------- :: If these variables are to be used instead of auto-detection, delete the :: "rem" before the following GOTO statement to skip auto-detection. rem GOTO BOOT_IT ::--------------------------------------------------------------------------- :: Look for and determine the type of backbone and system segment networks A:\NIDETECT IF ERRORLEVEL 4 GOTO GOODBYE IF ERRORLEVEL 3 GOTO GOODBYE IF ERRORLEVEL 2 GOTO EA IF ERRORLEVEL 1 GOTO ET GOTO GOODBYE :ET SET BACKBONE=ETHERNET SET SYSTEM_SEG=TELNET GOTO BOOT_IT

IP TNR AUTOEXEC.BAT File (Part 1) Figure 3-8



:EA SET BACKBONE=ETHERNET SET SYSTEM_SEG=ARCNET GOTO BOOT_IT :AT SET BACKBONE=ARCNET SET SYSTEM_SEG=TELNET GOTO BOOT_IT :AA SET BACKBONE=ARCNET SET SYSTEM_SEG=ARCNET :BOOT_IT IF "%SYSTEM_SEG%" == "TELNET" GOTO START IF "%SYSTEM_SEG%" == "ARCNET" COPY NET.ARC NET.CFG > NUL IF EXIST NET.CFG GOTO START ECHO Could not create file NET.CFG! Is the disk write-protected? GOTO GOODBYE :START ECHO Backbone network segment type is: %BACKBONE% ECHO Teletrol system network type is: %SYSTEM_SEG% IF "%BACKBONE%" == "ETHERNET" A:\PCTCP\NE2000.COM 0x60 5 0x300 IF "%BACKBONE%" == "ETHERNET" A:\PCTCP\ETHDRV.EXE -p 32 IF "%SYSTEM_SEG%" == "ARCNET" LSL IF "%SYSTEM_SEG%" == "ARCNET" TARCMLID IF "%SYSTEM_SEG%" == "ARCNET" MCPODI IF "%SYSTEM_SEG%" == "TELNET" TSINET 100 IPTIR 1 çç Specify the System Network Address :GOODBYE IF EXIST NET.CFG DEL NET.CFG SET BACKBONE= SET SYSTEM_SEG=

IP TNR AUTOEXEC.BAT File (Part 2) Figure 3-9



3.2.3 Advanced Configuration Setup for IP

The following instructions apply only if you have TNRs on different networks connected by IP Routers. For example, you may have TNRs on separate Ethernet Backbone networks joined by an IP Router as shown in figure 3-6. In this case, you must perform the following steps.

Step 1: Create a Host Table (HOSTS file) for every TNR. This file works in conjunction with the RMTNODES.INI file.

Step 2: Create a RMTNODES.INI file in the root directory of every TNR’s Boot Disk. This file works in conjunction with the HOSTS file.

Step 3: Specify an IP Router in the PCTCP.INI file. This steps is required only if you have two or more networks with TNRs on those networks.

Each of these steps is described in the sections that follow. Once the steps are complete, you must reboot every Teletrol Network Router that contains a new or changed file.

Create a Host Table (HOSTS File) for the TNR

Once the IP Address and System Network Address has been assigned, you must create a Host Table, a file on the TNR Boot Disk in the \PCTCP directory that lists the Host Names and their corresponding IP Addresses. This file works in conjunction with the RMTNODES.INI file to identify the location of TNRs on the WAN.

Using an ASCII text editor, create a file called HOSTS for each TNR on the network that lists the IP Address and corresponding Host Name of every other TNR on both networks. Use spaces or tabs to separate the IP Address and the Host Name as shown in the example below. Ensure that every other TNR on the network is specified in the HOSTS file for the TNR. When the HOSTS file is complete, copy it into the \PCTCP directory of the TNR Boot Disk.

The format for each entry in the file is:

IP Address Host Name

The example below shows the HOSTS file for the IP TNR 129.1.0.40 (TNR_1) from the network configuration shown in Figure 3-6 ‘IP Network Map with TNRs.’ Note that every other TNR in both networks is specified.

129.1.0.50 TNR_2 129.33.0.51 TNR_3 129.33.0.52 TNR_4

HOSTS File for IP TNR 129.1.0.40 (TNR_1) Figure 3-10



Create a RMTNODES.INI File for Every TNR Boot Disk

If your network topology consists of multiple TNRs on one network, or TNRs located on different IP networks, then a RMTNODES.INI must be created in the root directory of every TNR Boot Disk. This file lists the Segment Numbers of all other TNRs. The RMTNODES.INI file must list all other TNRs in the same IP network and all other TNRs on connected networks. This file works in conjunction with the HOST file to identify the location of TNRs on the WAN.

The format for each entry in the list is:

Hostname, System Network Address

As shown in the format example, use a comma to separate the Hostname and the System Network Address.

The example below shows the RMTNODES.INI file for the IP TNR 129.1.0.40 (TNR_1) from the network configuration shown in Figure 3-6 ‘IP Network Map with TNRs.’ Note that every other TNR in both networks is specified.

TNR_2,2 TNR_3,3 TNR_4,4

RMTNODES.INI File IP TNR 129.1.0.40 (TNR_1) Figure 3-11



Specify an IP Router in the PCTCP.INI File

If a TNR needs to send data to a workstation or to another IP TNR that is located on a different IP network, then the IP TNR must send the data to the IP Router that connects both networks. The IP Router is responsible for sending the data to the correct IP network. You must edit the PCTCP.INI file located in the \PCTCP directory of the TNR Boot Disk to specify the IP Router’s Address that corresponds to the source network.

For example, if TNR_1 needs to send information to TNR_3, TNR_4, and Workstation 150, then TNR_1 must first send the data to the IP Router that connects Network 1 and Network 2. The IP Router will forward the data to its destination on Network 2. Up to three IP Router Addresses can be specified in the PCTCP.INI file for managing the data transfer between IP networks.

Sending Data via the IP Router Figure 3-12

The example below shows the correct router= designation for the PCTCP.INI file for IP TNR 129.1.0.40 (TNR_1) from the network configuration shown in Figure 3-12 ‘Sending Data via the IP Router.’ The line router=129.1.0.254 allows TNR_1 to communicate with TNR_3 and TNR_4. Note that you would have to make the same entry in the PCTCP.INI file of IP TNR 129.1.0.50 (TNR_2) if you wanted TNR_2 to be able to communicate with TNR_3 and TNR_4.

[pctcp ifcust 0] broadcast-address = 255.255.255.255 ip-address = 129.1.0.40 subnet-mask = 255.255.0.0 router=129.1.0.254 çç Specify the source network’s IP Router’s address

PCTCP.INI File for IP TNR 129.1.0.40 (TNR_1) Figure 3-13



If you also wanted TNR_3 and TNR_4 to communicate with TNR_1 and TNR_2, you would have to specify the following router= designation for the PCTCP.INI file for IP TNR 129.33.0.51 (TNR_3) and IP TNR 129.33.0.52 (TNR_4).

TNR_3 is used in the example below. The line router=129.33.0.254 allows TNR_3 and TNR_4 to communicate with TNR_1 AND TNR_2.

[pctcp ifcust 0] broadcast-address = 255.255.255.255 ip-address = 129.33.0.52 subnet-mask = 255.255.0.0 router=129.33.0.254 çç Specify the source network’s IP Router’s address

PCTCP.INI File for IP TNR 129.33.0.52 Figure 3-14

4.0 Configuring the Workstations .......................................................................... 4-1

4.1 Configuring a Workstation for the IPX Protocol ........................................................................... 4-2

4.1.1 Configuring an Ensemble Workstation for IPX ............................................................... 4-2

4.1.2 Configuring an MCP Workstation for IPX ....................................................................... 4-2

4.2 Configuring a Workstation for the IP Protocol............................................................................... 4-4

4.2.1 Configuring an Ensemble Workstation for IP................................................................... 4-4

4.2.2 Configuring an MCP Workstation for IP........................................................................... 4-5

Rev. 4.00 Configuring the Workstations


4.0 Configuring the Workstations

Once you have installed and configured the Teletrol Network Router (TNR), you must configure the workstations running Ensemble, MCP, or CCIM that reside on the Ethernet or ARCNet Backbone. The configuration method you use depends on whether you are using the IPX or IP protocol. If you are using the IPX protocol, use the instructions presented in the ‘Configuring the Workstation for the IPX Protocol’ section of this chapter. If you are using the IP protocol, use the instruction presented in the ‘Configuring the Workstation for the IP Protocol’ section of this chapter. The IPX and IP protocols each have separate instructions for configuring a workstation running Ensemble or MCP.

IMPORTANT!

You only need to configure Ensemble, MCP, or CCIM if the workstation resides on the Ethernet or ARCNet Backbone.

Configuring the Workstation Rev. 4.00


4.1 Configuring a Workstation for the IPX Protocol

If you are using the IPX protocol for your network, use the instructions in this section to configure each workstation used within the network. Two sets of instructions are presented — one for workstations running Ensemble, and one for workstations running MCP or CCIM.

4.1.1 Configuring an Ensemble Workstation for IPX

Follow the instructions in this section to configure each Ensemble workstation within the network.

1. Use the Configuration tab of the Network dialog box in Windows to ensure there is an IPX Protocol bound to the Ethernet adapter. If the IPX Protocol is not present, add it.

Note: Refer to your Windows documentation for instructions.

2. Specify the Workstation Node address (101-250) and Workstation Segment address in Ensemble. If the workstation resides on the Ethernet or ARCNet Backbone network, use a Workstation Segment address of 255. If the workstation resides on a system segment, valid addresses are 0 through 254; however a value of 0 will NOT allow you to communicate through the TNR.

Once you complete these steps, you can begin communicating with the controller.

4.1.2 Configuring an MCP Workstation for IPX

Before you begin, you must load the 16-bit version of the Ethernet driver files. Consult the documentation that came with your Ethernet card for instructions on installing the driver files on the workstation.

Once you load the Ethernet driver files, only one additional step is required to configure the workstation. You must run the IPXCLI.EXE file that allows you to specify the Logical Node Address of the workstation. This identifies the location of the workstations that reside on the network; the TNR uses this information to direct packets to the correct workstation within the WAN. You must run this executable file on every Teletrol workstation on the IPX network after the Ethernet drivers are loaded.

The IPXCLI.EXE file comes with MCP and CCIM and should be resident on the Teletrol workstation’s hard drive in the Teletrol MCP software directory. To run the IPXCLI.EXE file, type the following command at the DOS prompt. This assumes that the file resides in the default c:\teletrol directory.

c:\teletrol\IPXCLI Logical Node Address

The Logical Node Address is a value between 101 and 250 that identifies the workstation node address. Each Teletrol Workstation on the Ethernet Backbone must have a unique Logical Node Address. When you run the IPXCLI.EXE file, a Logical Node Address Table is created in each TNR connected to the network. This table includes the addresses of all the workstations connected to the TNRs. When the TNRs are rebooted, they receive information from other TNRs on the network to build their Logical Node Address Table.



For MCP and CCIM, you must also specify the Workstation Segment address. If the workstation resides on the Backbone network, use a Workstation Segment address of 255. In MCP, specify the Workstation Segment address in the Segment Address field of the Configure MCP screen. In CCIM, specify the Workstation Segment address in the Segment Address field of the System Information screen.

If you are using MCP, you can begin to communicate with the controllers once you specify the Workstation Segment address in MCP and run the IPXCLI.EXE file from the DOS prompt. If you are using CCIM, you must specify the Workstation Segment address and load the IPXCLI.EXE file, then load Windows, and then load CCIM. Once all three are loaded, you can begin to communicate with the controllers.



4.2 Configuring a Workstation for the IP Protocol

If you are using the IP protocol for your network, use the instructions in this section to configure each workstation used within the network. Two sets of instructions are presented — one for workstations running Ensemble, and one for workstations running MCP or CCIM.

4.2.1 Configuring an Ensemble Workstation for IP

Follow the instructions in this section to configure each Ensemble workstation within the network.

1. Use the Configuration tab of the Network dialog box in Windows to ensure there is a IP Stack bound to the Ethernet adapter. If the IP Stack is not present, add it. Once the IP Stack is added, ensure that the correct IP Address and Subnet Mask are assigned to the workstation.

Note: Refer to your Windows documentation for instructions.

2. Specify the Workstation Node address (101-250) and Workstation Segment address in Ensemble.

If the workstation resides on the Ethernet or ARCNet Backbone network, use a Workstation Segment address of 255. If the workstation resides on a System segment, valid addresses are 0 through 254; however a value of 0 will NOT allow you to communicate through the TNR.

Once you complete these steps, you can begin communicating with the controller.



4.2.2 Configuring an MCP Workstation for IP

Before you begin, ensure that MCP and Net Manager’s PC/TCP IP Stack (Kernel) is installed on the workstation’s hard drive. Then follow the instructions in this section to configure each MCP workstation within the network.

1. Use an ASCII text editor to edit the PCTCP.INI file and specify the ip-address and subnet-mask values. The IP Address identifies the address of the workstation on the network; the Subnet Mask identifies the network class.

An example of a portion of the PCTCP.INI file is shown below.

[pctcp ifcust 0] broadcast-address = 255.255.255.255 ip-address = 129.33.0.10 çç Specify the Workstation Address subnet-mask = 255.255.0.0 çç Specify the Subnet Mask router=129.33.0.254

Portion of the PCTCP.INI File Figure 4-1

Note: If your Backbone network is a multi-segment network (more than one segment connected by a non-Teletrol network router or gateway), you must also specify the IP Router address in the PCTCP.INI file. This is described in Step 3 of this procedure.

2. Edit the AUTOEXEC.BAT file and ensure it includes the statements described below.

Note: Statements in the AUTOEXEC.BAT file execute automatically when the workstation is booted; therefore, we recommend that you place these statements within the file. Alternatively, you could choose to create another batch file that you run each time, or you could manually specify each of these statements at the DOS prompt each time.

A sample IP setup within the AUTOEXEC.BAT file is shown below. The statements must appear in the order they are shown. Be sure to change the IRQ Value, Port Address, and Teletrol Workstation Address to the correct values.

REM ******************** IP Setup ************************************* REM ** Sets environmental variables — c:\pctcp is the default TCPIP software ** REM ** directory.*** SET PCTCP=c:\pctcp\pctcp.ini REM ** Loads the Ethernet Driver. Replace 9 with the IRQ Value and 0x300 with the ** REM ** the Port Address of the Ethernet Card. c:\pctcp is the default TCPIP software ** REM ** directory.*** c:\pctcp\ne2000 0x60 9 0x300 REM ** Loads the IP Stack (Kernel) — c:\pctcp is the default TCPIP software directory.** c:\pctcp\ethdrv REM ** Specifies the Teletrol Workstation Address (101-250) —-. c:\teletrol is the ** REM ** default MCP directory. ** c:\teletrol\ipcli 101 REM **********************************************************************

IP Setup Portion of the AUTOEXEC.BAT File Figure 4-2



If you have a single Backbone network connecting workstations, the configuration is complete and you can begin to communicate with the controllers.

However, if your Backbone network is a multi-segment network (more than one segment connected by a non-Teletrol network router), you may need to perform the next three steps also. These steps should be performed only for a multi-segmented network. They are required only if the network segment on which the workstation resides has no TNR. While these steps are NOT required for other multi-segmented network scenarios, they can possibly improve the efficiency of communications.

Additional Steps for a Multi-Segmented Network

Information from the sample network setup shown below is used in the examples that follow. The Teletrol Workstation on Node 150 is being configured is these examples.

Multi-Segmented IP Network Figure 4-3

3. Use a text editor to edit the PCTCP.INI file and specify the router= value. This identifies the address of the IP Router you are using.

If a workstation needs to send data to an IP TNR that is located on a different IP network, then the workstation must route that data through the IP Router that connects both networks. The IP Router is responsible for sending the data to the correct IP network. The address of the IP Router that corresponds to the source network must be specified in the PCTCP.INI file.

For example, if Workstation 150 needs to send information to TNR_1 and TNR_2, then Workstation 150 must route the data through the IP Router which will forward it to its destination on the other network segment.



An example of a portion of the PCTCP.INI file is shown below.

[pctcp ifcust 0] broadcast-address = 255.255.255.255 ip-address = 129.33.0.10 subnet-mask = 255.255.0.0 router=129.33.0.254 ççSpecify the source network’s IP Router’s address

Portion of the PCTCP.INI File Figure 4-4

You need only perform Steps 4 and 5 if there are no TNRs on the network segment on which this workstation resides. The HOSTS and MCPROUTE.INI files work together to direct packets to a TNR on a different network via the IP Router.

4. Using an ASCII text editor, create a HOSTS file in the C:\PCTCP directory on the hard drive of the MCP workstation. Include the IP Addresses of the TNRs and the Host Names assigned to the TNRs on the other network segment; use either spaces or tabs to separate the information. The HOSTS file creates a Host Table in the MCP workstation that tells MCP or CCIM the IP Addresses of every TNR on the other network segments.

129.1.0.40 TNR_1 129.1.0.50 TNR_2

The HOSTS File Figure 4-5

5. Using an ASCII text editor, create the MCPROUTE.INI file in the Teletrol MCP software directory on the hard drive of the MCP workstation. The MCPROUTE.INI file consists of the names of the TNRs specified in the HOST file; in other words, it lists the names assigned to the TNRs on the other network segments. The names should match those specified in the HOSTS file.

TNR_1 TNR_2

The MCPROUTE.INI File Figure 4-6

Once you complete these steps, you are ready to begin communicating with the controllers.

5.0 Diagnostics .......................................................................................................... 5-1

5.1 Using the Serial/Diagnostics Port ..................................................................................................... 5-1

5.2 Verifying TNR Communication Using the Serial/Diagnostic Port ............................................. 5-4

Rev. 4.00 Diagnostics


5.0 Diagnostics

The TNR has built-in diagnostics capabilities through its serial diagnostics port. This chapter describes how to use the diagnostic capabilities of the TNR. In addition, the ‘Verifying the TNR Communications’ section of this chapter provides the instructions to ensure that the TNRs are communicating properly on the network. If you are experiencing problems communicating with a TNR on the network, you should perform this diagnostic test.

5.1 Using the Serial/Diagnostics Port

A standard 9-pin RS-232 port is installed on each TNR to provide you with diagnostic capabilities for the TNR. An ASCII terminal or a PC running ProComm or any other terminal emulation software can be used to interface to the diagnostics port. The diagnostics port (Serial 1) communicates at 9600 baud, 8 data bits, 1 stop bit, and no parity.

The table below shows the pinout requirements of the cable that connects your laptop or workstation to the serial/diagnostics port.

9-Pin TNR Serial Port Pin Number

9-Pin Workstation Pin Number

25-Pin Workstation Pin Number

2 3 2

3 2 3

5 5 7

Pinout Requirements for the Diagnostics Port Figure 5-1

By default in the TNR, keyboard and video display control is transferred automatically to the serial port; this enables the terminal emulation software. If you are NOT running terminal emulation software, you must comment out two lines in the AUTOEXEC.BAT file of the TNR Boot Disk as shown below. Once you comment out these lines, the TNR will use the standard keyboard attached to the keyboard port and the VGA monitor attached to the monitor port.

PROMPT $p$g rem MODE COM1:9600,N,8,1 çç Comment out for direct keyboard/video access rem CTTY COM1 çç Comment out for direct keyboard/video access SET PCTCP=A:\PCTCP\PCTCP.INI

IP TNR AUTOEXEC.BAT File Figure 5-2

Diagnostics Rev. 4.00


After connecting an ASCII terminal or starting the terminal emulation software (ProComm), the diagnostics port is ready to use. A list of the valid commands is shown below. Simply type the letter of the command; the TNR sends the requested information to the connected terminal.

[B] When you press [B], the TNR returns the amount of system network Receive Buffers available. In all, 200 system network receive buffers are allocated.

[D] When you press [D], the Debug message output toggles. Debug messages are by default disabled. This should only be used under the direction of Teletrol’s Technical Support Department because the TNR’s performance will degrade significantly when debug messages are enabled.

[R] When you press [R], the TNR generates a Router Table. The Router Table lists all Backbone TNRs that are recognized by this TNR. This is a very useful key; it can be used to determine if TNRs are communicating with each other. The following Router Table is an example of the information returned from an IPX network.

Number Address

1 000000f0:00c0a8080a6a:4003

3 000000f0:00c0a8080882:4003

4 000000f0:00c0a8080b38:4003

5 000000f0:00c0a8080de4:4003

Sample Router Table Figure 5-3

In the Router Table, the Number column lists the System Network Number assigned to the TNR. The Address column lists the physical address of the TNR on the network. The first item in the table is the current TNR; in this case, TNR #1. The above Router Table indicates that TNR #1 can communicate with TNR #3, #4, and #5.

[S] When you press [S], the TNR returns the following status information.

• TNR Software Version • Current System Time • TNR Start Time • Backbone Network Number • Number of System Network Packets Transmitted • Number of System Network Transmit Errors • Number of System Network Packets Lost • Number of Backbone Network Packets Received • Number of System Network Packets Received

Rev. 4.00 Diagnostics


[W] When you press [W], the TNR generates a Backbone Network Workstation Table. This table lists the Backbone network workstations that are recognized by this TNR. The following is an example of the information returned for an IPX network.

Stn Address 101 00c0a8080fff 102 00c0a8080fdf

In the Backbone Network Workstation Table, the Stn column specifies the logical address of the workstation. The Address column specifies the Backbone network’s physical address.

[Q] or [Esc] These commands allows you to stop running the software transmitting data on the network. When you press [Q] or [Esc], the TNR displays the following message.

“Terminate Teletrol Intelligent Router?”

To terminate the TNR software operation, type YES at the prompt and press [Enter]. To abort the termination and continue running the TNR software, press any other key and [Enter].

Diagnostics Rev. 4.00


5.2 Verifying TNR Communication Using the Serial/Diagnostic Port

Once all the TNRs have been set up, properly addressed, and connected to the Backbone network, the TNRs should be able to communicate successfully with each other. The following is the procedure for verifying TNR communications on the network. You might want to use this procedure to troubleshoot communications problems on the network.

1. Connect to the diagnostics port on one of the TNRs as described in the previous section.

2. Type [R] to display the Router Table.

3. Review the information in the Router Table to verify that the TNR to which you are connected recognizes the other TNRs on the network.

4. If one of the TNRs is not recognized, check its network cabling and configuration. Correct any problems you detect, then verify that the TNR appears in the Router Table.

5. Repeat this procedure for each TNR on the Backbone.

Appendix A: Reconfiguring the Media Type for TNR Cards ..................................A-1

A.1 Ethernet and ARCNet Port Connectors...........................................................................................A-1

A.1.1 Ethernet Cards.......................................................................................................................A-1

A.1.2 ARCNet Cards.......................................................................................................................A-2

A.2 Reconfiguring Hardware-Configurable Cards...............................................................................A-3

A.2.1 Ethernet Card with W9 and W10 Jumpers .......................................................................A-4

A.2.2 Ethernet Card with J5 and J6 Jumpers ..............................................................................A-5

A.2.3 ARCNet Card with JP9 and JP10 Jumpers.......................................................................A-6

A.3 Reconfiguring Software-Configurable Cards ................................................................................A-7

A.3.1 Reconfiguring the Ethernet Card for a TNR with an AMI BIOS.................................A-8

A.3.2 Reconfiguring the Ethernet Card for a TNR with an Award BIOS ...........................A-11

Rev. 4.00 Reconfiguring the Media Type for TNR Cards

Teletrol Network Router Manual Page A-1

Appendix A: Reconfiguring the Media Type for TNR Cards

This chapter provides the instructions for reconfiguring cards for the Teletrol Network Router (TNR). These cards are shipped already configured; you only have to change the configuration if you use the TNR on a different network than originally intended.

IMPORTANT!

If the TNR was ordered from Teletrol with the proper media type, the Ethernet Port does NOT need to be configured.

A.1 Ethernet and ARCNet Port Connectors

This section describes the port connectors available on the Ethernet and ARCNet cards. Note that while there are numerous different types of Ethernet cards, there is only one type of ARCNet card.

A.1.1 Ethernet Cards

The Ethernet card in the TNR can have up to three different types of connectors to interface to the Ethernet network. Only one type of connector can be used at one time for each TNR. Teletrol configures the Ethernet card media connector based on the information you provide when you order the TNR.

If the Ethernet network requires a different (connector) configuration, you must make certain modifications. Depending on which card type is installed in the TNR, you must either change an internal jumper (located on the Ethernet card), or make certain software configuration changes.

Teletrol has used a number of different models of Ethernet cards in the TNR. If you do not already know whether your Ethernet card is hardware-configurable or software-configurable, you must determine it before beginning. To do this, remove the TNR’s outer casing and compare the card with the illustrations in this chapter.

WARNING!

Unplug the TNR before removing the outer casing.

Note that there are two basic model types: one type has jumpers, one does not. Cards with jumpers are reconfigured by changing the position of jumpers on the card (hardware-configurable). The jumper settings are shown in the ‘Reconfiguring Hardware-Configurable Cards’ section of this chapter.

Cards without jumpers are configured through the setup software (software-configurable). The instructions are provided in the ‘Reconfiguring Software-Configurable Cards’ section of this chapter.

Reconfiguring the Media Type for TNR Cards Rev. 4.00

Page A-2 Teletrol Network Router Manual

A.1.2 ARCNet Cards

An ARCNet card can be connected to the Backbone network and/or to the System Network Segment. Therefore, it is possible to have one or two ARCNet cards installed in the TNR. Each ARCNet card in the TNR has two different types of connectors to interface to a network. Only one type of connector can be used at one time for each TNR. Teletrol configures each ARCNet card’s media connector based on the information you provide when you order the TNR.

If the Backbone or System network requires a different (connector) configuration, you must change jumper settings located on the ARCNet card. To change the jumper settings, you must remove the TNR’s outer casing.

WARNING!

Unplug the TNR before removing the outer casing.

The jumper settings are shown in the ‘Reconfiguring Hardware-Configurable Cards’ section of this chapter.



A.2 Reconfiguring Hardware-Configurable Cards

Older TNRs contain an Ethernet card that is configured by setting jumpers on the card. The ARCNet Backbone network card is always configured in this manner. The general procedure for reconfiguring the connector type on a hardware-configurable card is given below. The next sections illustrate the three cards that use jumper settings to configure the media type and provide the possible jumper settings.

1. Power down the TNR.

2. Remove the cover and locate the network card.

3. Determine which card you have in the TNR (see Figure A-1, A-2, and A-3), then locate and remove the connector-type jumpers you want to change for your particular card.

4. Install the jumpers with the desired settings (see Figure A-1, A-2, and A-3).

5. Ensure that all cards in the TNR are installed properly, then replace the unit’s cover.

6. Power the TNR with the boot disk inserted.

The card is now reconfigured to use the new connector type.



A.2.1 Ethernet Card with W9 and W10 Jumpers

This type of card has built-in jumpers W9 and W10. To change the media type, you must change the jumper settings. Figure A-1 shows the possible configurations for the W9 and W10 headers for this card.

W1-W4

W9-W10

Jumper Setting Connector Type

W9 W10

BNC Connector Enable (Default)

W9 W10

AUI Connector Enable

W9 W10

TP RJ-45 Connector Enable

Ethernet Card W9 and W10 Jumper Settings Figure A-1



A.2.2 Ethernet Card with J5 and J6 Jumpers

This type of card has built-in jumpers. To change the media type, you must change the jumper settings. Figure A-2 shows the possible configurations for the J5 and J6 headers for this card.

J5-J6


J5-J6

BNC Connector Enable (Default)

J5-J6

AUI Connector Enable

J5 J6

TP RJ-45 Connector Enable

Ethernet Card W9 and W10 Jumper Settings Figure A-2



A.2.3 ARCNet Card with JP9 and JP10 Jumpers

The ARCNet card for the ARCNet Backbone network and System network has built-in jumpers JP9 and JP10 that establish the media type. To change the media type, you must change the jumper settings. Figure A-3 shows the possible configurations for the JP9 and JP10 headers for this card.

JP11 JP12

JP8 JP6

JP5 JP4 JP3

JP9

JP10

JP1

JP2

ADDR

IRQ

JP13

EXT PWR

Twisted

Pair

Coax


JP9 JP10

BNC Connector Enable

JP9 JP10

Twisted Pair Connector Enable

ARCNet Card with JP9 and JP10 Jumper Settings Figure A-3

In addition, Jumpers JP1 and JP2 determine whether the ARCNet card is configured for the Backbone network or the System network. Ensure that jumpers JP1 and JP2 on the ARCNet card are set correctly for the card’s intended use. Use the chart below to determine the proper settings.

Jumper Function Backbone Network System Segment Network JP1 Port Address A3, A4, A5, A6, A7

(300H) A3, A6, A7 (330H)

JP2 Interrupt Request (IRQ) 5 7

ARCNet Card with JP1 and JP2 Jumper Settings Figure A-4



A.3 Reconfiguring Software-Configurable Cards

Later versions of the Teletrol Network Router use software-configurable Ethernet cards that can be reconfigured using the LAN Adapter Setup and Diagnostics Software. All software-configurable cards are reconfigured using one of two procedures. The procedure you use depends upon the BIOS of the TNR, either AMI or Award. The instructions for reconfiguring a card for the AMI BIOS or the Award BIOS follow.

You can determine which type of BIOS (AMI or Award) your TNR uses by viewing the label on the back of the TNR. In addition, this information displays whenever you boot the TNR. Once you determine the BIOS type, follow the instruction in the corresponding section.



A.3.1 Reconfiguring the Ethernet Card for a TNR with an AMI BIOS

Follow the procedure below to change the connector type for the AMI Ethernet card from Twisted Pair or BNC to AUI, or from AUI to Twisted Pair or BNC.

Note: As configured and shipped by Teletrol, the Ethernet card automatically detects the difference between the Twisted Pair or BNC connection — a change between these connector types does NOT require user configuration changes. If the Auto Detect feature is deselected, you must make the configuration changes using the procedure.

1. Insert the TNR Boot disk into a PC (not the TNR) that is running a text editor. Using the text editor, edit the AUTOEXEC.BAT making the alterations described below.

• Convert the following two statements into remark statements by adding REM to the front of the statement. When these lines are disabled, you can connect directly to the TNR using a monitor and keyboard.

REM MODE COM1:9600,N,8,1 REM CTTY COM1

• Add the following line after the REM CTTY COM1 statement.

GOTO GOODBYE

When your changes are complete, the beginning of the AUTOEXEC.BAT file should appear as shown below.

@ECHO OFF A: PROMPT $p$g REM MODE COM1:9600,N,8,1 REM CTTY COM1 GOTO GOODBYE SET PCTCP=A:\PCTCP\PCTCP.INI IF EXIST NET.CFG DEL NET.CFG

2. Save the changes and exit the AUTOEXEC.BAT file.

3. Insert the TNR Boot Disk into the TNR and connect a monitor and keyboard to it.

4. Reboot the TNR and enter the CMOS setup.

5. Enable the keyboard and video ports. Save the changes and reboot the TNR.

The DOS prompt appears.

6. At the DOS prompt, type the following line:

RSET8019.EXE

The LAN Adapter Setup and Diagnostics Software screen displays.

7. Highlight the Setup option from the Main Menu, and press [Enter] to select it.

The Setup screen displays.



8. On the Setup screen, set the parameters as shown below. Set the Boot ROM parameter first since this clears all other parameters.

Operation Mode:...........................Jumperless Medium Type:................................Auto Detect Full-duplex: .....................................Disabled I/O Base:.........................................300H Interrupt:.........................................5 Boot ROM:.....................................No Boot ROM

Note: Except for Medium Type, all parameters must be set with the values shown above. As configured and shipped by Teletrol, the Medium Type defaults to Auto Detect, but a different Medium Type value may be selected.

9. Press the [Esc] key.

The Update Confirmation screen displays the message:

“Do you really want to update?”

10. Press the [Y] key then [Enter] to save the new configuration and exit to the Main Menu.

11. Select the Exit RSET option from the Main Menu to exit the configuration program.

The Exit Confirmation screen displays the message:

“Are you sure you want to exit?”

12. Press the [Y] key then [Enter] to exit to DOS.

13. Reboot the TNR and enter the CMOS setup.

14. Disable the keyboard and video ports and save the changes.

15. Using a text editor, edit the AUTOEXEC.BAT file again to remove the REM and GOTO statements you added earlier.

• Remove the REM in the front of the two statements shown below. When these lines are enabled, you can use the PC to communication with the TNR (Debug-enabled state).

MODE COM1:9600,N,8,1 CTTY COM1

• Remove the following line, or convert it to a remark (REM) statement so that it will NOT execute.

REM GOTO GOODBYE

When your changes are complete, the beginning of the AUTOEXEC.BAT file should appear as shown below (the GOTO statement may NOT appear).

@ECHO OFF A: PROMPT $p$g MODE COM1:9600,N,8,1 CTTY COM1 REM GOTO GOODBYE SET PCTCP=A:\PCTCP\PCTCP.INI IF EXIST NET.CFG DEL NET.CFG




17. Insert the TNR disk into the TNR and reboot the TNR.

The card is now reconfigured. You can use the new port configuration to communication on the network.



A.3.2 Reconfiguring the Ethernet Card for a TNR with an Award BIOS

Follow the procedure below to change the connector type for the Award Ethernet card from Twisted Pair or BNC to AUI, or from AUI to Twisted Pair or BNC.

Note: As configured and shipped by Teletrol, the Ethernet card automatically detects the difference between the Twisted Pair or BNC connection — a change between these connector types does NOT require user configuration changes. If the Auto Detect feature is deselected, you must make the configuration changes using the procedure.

1. Insert the TNR Boot disk into a PC (not the TNR) that is running a text editor. Using the text editor, edit the AUTOEXEC.BAT making the alterations described below.

• Convert the following two statements into remark statements by adding REM to the front of the statement. When these lines are disabled, you can connect directly to the TNR using a monitor and keyboard.

REM MODE COM1:9600,N,8,1 REM CTTY COM1

• Add the following line after the REM CTTY COM1 statement.

GOTO GOODBYE

When your changes are complete, the beginning of the AUTOEXEC.BAT file should appear as shown below.

@ECHO OFF A: PROMPT $p$g REM MODE COM1:9600,N,8,1 REM CTTY COM1 GOTO GOODBYE SET PCTCP=A:\PCTCP\PCTCP.INI IF EXIST NET.CFG DEL NET.CFG


3. Insert the TNR Boot Disk into the TNR and connect a monitor and keyboard to it.

4. Reboot the TNR.

The DOS prompt appears.

5. At the DOS prompt, type the following line:

RSET8019.EXE

The LAN Adapter Setup and Diagnostics Software screen displays.

6. Highlight the Setup option from the Main Menu, and press [Enter] to select it.

The Setup sceen displays.



7. On the Setup screen, set the parameters as shown below. Set the Boot ROM parameter first since this clears all other parameters.

Operation Mode:...........................Jumperless Medium Type:................................Auto Detect Full-duplex: .....................................Disabled I/O Base:.........................................300H Interrupt:.........................................5 Boot ROM:.....................................No Boot ROM

Note: Except for Medium Type, all parameters must be set with the values shown above. As configured and shipped by Teletrol, the Medium Type defaults to Auto Detect, but a different Medium Type value may be selected.

8. Press the [Esc] key.

The Update Confirmation screen displays the message:

“Do you really want to update?”

9. Press the [Y] key then [Enter] to save the new configuration and exit to the Main Menu.

10. Select the Exit RSET option from the Main Menu to exit the configuration program.

The Exit Confirmation screen displays the message:

“Are you sure you want to exit?”

11. Press the [Y] key then [Enter] to exit to DOS.

12. Reboot the TNR.

13. Using a text editor, edit the AUTOEXEC.BAT file again to remove the REM and GOTO statements you added earlier.

• Remove the REM in the front of the two statements shown below. When these lines are enabled, you can use the PC to communication with the TNR (Debug-enabled state).

MODE COM1:9600,N,8,1 CTTY COM1

• Remove the following line, or convert it to a remark (REM) statement so that it will NOT execute.

REM GOTO GOODBYE

When your changes are complete, the beginning of the AUTOEXEC.BAT file should appear as shown below (the GOTO statement may NOT appear).

@ECHO OFF A: PROMPT $p$g MODE COM1:9600,N,8,1 CTTY COM1 REM GOTO GOODBYE SET PCTCP=A:\PCTCP\PCTCP.INI IF EXIST NET.CFG DEL NET.CFG




15. Insert the TNR disk into the TNR and reboot the TNR.

The card is now reconfigured. You can use the new port configuration to communication on the network.

Rev. 4.00 Index

Teletrol Network Router Manual Page I-1

Index

A

ARCNet 1-1, 3-5 ARCNet Backbone Network 1-1, 1-5, 3-5 ARCNet Card A-2

B

Backbone Network Number for IPX 3-2

C

Communications 5-4 Configuring TNR

Advanced IP 3-14 IP 3-7 IPX 3-1

D

Diagnostics 5-1

E

Ethernet Backbone Network 1-1, 1-2, 1-5 Ethernet Card A-1

F

File AUTOEXEC.BAT 3-2, 3-3, 3-4, 3-11, 3-12, 3-13, 4-

5 HOSTS 3-14, 4-7 IPXCLI.EXE 4-2 MCPROUTE.INI 4-7 NET.ARC 3-5, 3-6 NET.ETH 3-5 Network Configuration 3-5 PCTCP.INI 3-11, 3-16, 4-5, 4-6, 4-7 RMTNODES.INI 3-14, 3-15

G

Gateway 1-1

H

Hardware Components 1-3 Host ID 3-8 Hosts Table 3-14

I

IP 1-1 IP Address 3-8

Assigning 3-11 IP Router Address 3-16 IPTIR 3-12, 3-13 IPX 1-1

L

LAN 1-1 Logical Node Address 4-2

M

Media Type Reconfiguring A-1

N

Net ID 3-8 Network

ARCNet 1-1, 3-5 Ethernet 1-1, 3-5 Protocol

IP 1-1, 3-8, 3-10, 3-11 IPX 1-1

System Architecture 1-2 Novell 3-2

S

Software Key 1-6 System Network (Segment) Number for IPX 3-2 System Network Address 3-10

Assigning 3-11, 3-12

T

Teletrol Network Router 1-1 TELNET 1-1 TIR 3-2 TNR

Address for IP 3-8 Address for IPX 3-2 BIOS A-7 Configuring 3-1

Advanced IP 3-14

Index Rev. 4.00

Page I-2 Teletrol Network Router Manual

IP 3-7 IPX 3-2

Debug 5-2

Rev. 4.00 Index

Teletrol Network Router Manual Page I-3

Diagnostics 5-1 Debug 5-2

Hardware Cards 1-5 Enclosure 1-3 Floppy Drive 1-4 Overview 1-3 Power Supply 1-4 Printer Port 2-1 Serial 1 Port 5-1 Software Key 1-6, 2-1

Installing 2-1 Network Map 3-10 Overview 1-1 Reconfiguring Cards A-1 Verify Communications 5-4

W

WAN 1-1, 1-2 Workstation

CCIM 1-1 Configuring 4-1 Configuring for IP 4-4 Configuring for IPX 4-2, 4-5 Ensemble 1-1 MCP 1-1

manual teletrol network router

Documents