Ericsson EDACS Series Installation And Maintenance Manual
Ericsson EDACS Series Installation And Maintenance Manual

Ericsson EDACS Series Installation And Maintenance Manual

Data gateway

Advertisement

Quick Links

LBI-38962
ERICSSONZM
Mobile Communications
® ®
EDACS
Data Gateway
INSTALLATION AND MAINTENANCE

Advertisement

Table of Contents
loading
Need help?

Need help?

Do you have a question about the EDACS Series and is the answer not in the manual?

Questions and answers

Subscribe to Our Youtube Channel

Summary of Contents for Ericsson EDACS Series

  • Page 1 LBI-38962 ERICSSONZM Mobile Communications ® ® EDACS Data Gateway INSTALLATION AND MAINTENANCE...
  • Page 2: Table Of Contents

    MODIFYING THE HOSTS' CONFIGURATION (IP HOSTS ONLY).......33 MODIFYING THE REST OF THE EDACS™ SYSTEM ...........34 MAINTENANCE..........................35 PASSWORD MAINTENANCE ...................35 ACTIVITY LOG MAINTENANCE..................35 LOADING NEW SOFTWARE RELEASES................35 ICMP MESSAGES RETURNED BY EDG ..................36 TROUBLE-SHOOTING GUIDE.......................37 Copyright © September 1994, Ericsson GE Mobile Communications Inc.
  • Page 3: Preface

    MS-DOS (trademark of Microsoft Corporation) and PC-DOS. Landline Data Release Notes (SRN1036-1): This manual documents the installation procedure for the IMC and Sites. Mobile Data Terminal Interface, Hardware and Protocol, Version 1.92 This manual documents the RDI Interface. Contact Ericsson-GE for more information.
  • Page 4: Network Planning For Ip Host Configurations

    LBI-38962 NETWORK PLANNING FOR IP HOST CONFIGURATIONS Prior to configuring and installing the EDG, it is important to determine the IP Addresses that will be used. In addition to this document, the EDG Technical Description explains the concepts behind the EDG. Also, the EDG Configuration Reference Manual contains several example configurations which are helpful in building the SYSTEM.TXT configuration file once the configuration is known.
  • Page 5: Edacs Addresses

    LBI-38962 EDACS Addresses There are two types of EDACS Addresses, Logical IDs (LIDs) and Group IDs (GIDs). LIDs are used to reference a single host, radio, or TSI Master. GIDs are used to reference one or more radios. LIDs and GIDs are programmed into radios and can be changed as desired.
  • Page 6: Assigning Network Ip Addresses

    LBI-38962 ASSIGNING NETWORK IP ADDRESSES An internet consists of multiple networks connected together, with each network on the internet assigned a unique network address. Therefore, the first step is to determine the IP Network Addresses that will be used. In the simplest case, three network addresses will be used: one each for the IP Host Network, the Internal EDG Network, and the EDACS Network.
  • Page 7: Assigning Individual Addresses

    LBI-38962 For this example, it is assumed that you have chosen to assign Network Address 128.1.0.0 to your EDACS Network. Remember that since each network address must be unique, 128.1.0.0 should be reserved so that it is not used by any one else on the internet. Radio/RDI/RDT Host A Radio/RDI/RDT...
  • Page 8: Using Network Layer Rdts

    LBI-38962 USING NETWORK LAYER RDTS If Network Layer Radio Data Terminals (RDTs) are being used, i.e. RDTs with the EDACS Network Driver (END) installed, all message source and destination references are to IP addresses. EDACS addresses are not important or relevant to either the IP host or RDT, and are effectively hidden. This is analagous to an ethernet network, where an ethernet address is assigned to all devices, but the user need not know this address to communicate with other devices on the network - a higher layer addressing scheme such as IP is utilized.
  • Page 9: Sample System.txt File

    LBI-38962 Sample SYSTEM.TXT File The following is a SYSTEM.TXT configuration file that would match the example configuration: IP hosts with all network layer RDTs. Note here that since only network layer RDTs are being used, no entries are required in the [ip_map_id_table] for the IP hosts.
  • Page 10: Using Non-Network Layer Rdts

    LBI-38962 USING NON-NETWORK LAYER RDTs If there are any Radio Data Terminals (RDTs) that do not have the EDACS Network Driver installed, EDACS addresses become important to the user. Specifically, a Host LID needs to be mapped to each of the IP hosts. For this example, it is assumed that LID 1 has been assigned to Host A and LID 2 has been assigned to Host B.
  • Page 11: Sample System.txt File

    LBI-38962 Sample SYSTEM.TXT File The following is a SYSTEM.TXT configuration file that would match the example configuration: IP hosts with no network layer RDTs. Note here that since non-network layer RDTs are being used, entries are required in the [ip_map_id_table] for the IP hosts. The EDG Configuration Reference Manual contains a detailed explanation of each command.
  • Page 12: Network Planning For Rdi Host Configurations

    LBI-38962 NETWORK PLANNING FOR RDI HOST CONFIGURATIONS RDI hosts communicate directly to the EDG, through an HDI board, over 9600 baud asynchronous serial data links using the RDI protocol. Radio/RDI/RDT Host A Radio/RDI/RDT Host B Internal EDG Network RDI Host Network Radio/RDI/RDT EDACS Network internet with RDI hosts...
  • Page 13 LBI-38962 Radio/RDI/RDT LID 64 Host A GID 2 LID 61 Radio/RDI/RDT Host B LID 64 LID 62 GID 1 Internal EDG Network RDI Host Network Radio/RDI/RDT LID 64 GID 1 EDACS Network RDI Host internet with addresses assigned As mentioned previously, no IP addresses need to be assigned by the user in an RDI host only configuration ;...
  • Page 14: Sample System.txt File

    LBI-38962 Sample SYSTEM.TXT File The following is a SYSTEM.TXT configuration file that would match the example configuration. The EDG Configuration Reference Manual contains a detailed explanation of each command. During the initial load analysis, it was found that host A would be lightly loaded, with a single serial link sufficient to handle all data traffic.
  • Page 15: Network Planning For Combined Ip And Rdi Host Configurations

    LBI-38962 NETWORK PLANNING FOR COMBINED IP AND RDI HOST CONFIGURATIONS Both IP and RDI hosts may exist in an EDACS system configuration. It is recommended that if you have not read the two previous sections, "Network Planning for IP Host Configurations" and "Network Planning for RDI Host Configurations", that you do so at this time.
  • Page 16 LBI-38962 In this example, we will use 200.0.0.0 as the RDI host network address, which is the default assigned by the EDG if none is specified by the user. The addresses for the other networks will be the same as in the IP host example. IP Host A IP Host B IP Host Network...
  • Page 17 LBI-38962 We will use the same addresses as in the IP and RDI host examples, plus we now need to assign a unique IP address to each RDI host. In this example, we will just use the EDACS LID assigned to the RDI host as the Host ID portion of the IP address Note that this is the default value assigned by the EDG if an individual IP address is not specified for the RDI host.
  • Page 18: Sample System.txt File

    LBI-38962 Sample SYSTEM.TXT File The following is a SYSTEM.TXT configuration file that would match the example configuration. The EDG Configuration Reference Manual contains a detailed explanation of each command. ############################################### # SYSTEM.TXT configuration file. ############################################### [board 1] type cap load 01.02/loads/CAP.SX [board 2] type tsi_master load 01.02/loads/TSI.SX...
  • Page 19: Installation

    LBI-38962 INSTALLATION CONTENTS The EDG is shipped with the following items: • VT100 compatible terminal with power cord • Terminal interface cable • EDACS Data Gateway Technical Description manual • EDACS Data Gateway Installation and Maintenance Manual • EDACS Data Gateway Configuration Reference Manual •...
  • Page 20: Installation Steps

    LBI-38962 INSTALLATION STEPS A few simple steps are required to install the EDG. The sections that follow describe some of the steps in more detail. Set the board jumpers and install EPROMs. Connect the terminal to the EDG. Connect the printer to the EDG (optional). Connect the Host computers to the EDG.
  • Page 21: Board Hardware Setup

    LBI-38962 BOARD HARDWARE SETUP There are two types of boards installed in the EDG: MVME147S and VCOM24. There will be only one MVME147S board, located in the leftmost slot (slot 1). There will be one or more VCOM24 boards, beginning at slot 3.
  • Page 22 LBI-38962 Shown below are the jumper settings for the VCOM24 board. The two EPROMs for this board are to be installed in U49 and U50. U54 and U55 will not have any EPROMs installed. J2 J3 J5 J6 J7 J8 J9 J15 J16 J25 J26 VCOM24 Board Jumper Settings...
  • Page 23: Connecting The Terminal

    LBI-38962 CONNECTING THE TERMINAL A VT100 compatible terminal with a power cord and a terminal cable is included with the EDG. Read the user's manual included with the terminal for information on how to connect the terminal to an AC source and turn it on. The following diagram shows the minimum number of pin connections required in the terminal cable.
  • Page 24: Connecting The Printer (Optional)

    LBI-38962 CONNECTING THE PRINTER (OPTIONAL) NOTE A printer and printer cable are NOT included with the EDG. Connect the female end of the printer cable to your printer. Locate the PRINTER port on the rear of the EDG electronics chassis. Connect the male end of the cable to the EDG PRINTER port.
  • Page 25: Connecting The Host Computers To The Edg

    LBI-38962 CONNECTING THE HOST COMPUTERS TO THE EDG IP HOST COMPUTER NETWORK CONNECTION This is required only if your configuration includes IP hosts. Connect your Ethernet Transceiver to the EDG using the DB15 AUI Ethernet port on the rear of the EDG electronics chassis.
  • Page 26: Connecting The Edg Control Line To The Imc/Cec

    LBI-38962 CONNECTING THE EDG CONTROL LINE TO THE IMC/CEC On the EDG, the TSI Control Link Cable takes the signals from the front panel connector on the TSI Master Board to one of the RJ-12 connectors on the EDACS Interface board. The EDACS Interface board combines the ten RJ-12 connectors (J11 and J12 aren't used) into Champ connector J15.
  • Page 27: Connecting The Edg Data Lines To The Imc/Cec

    LBI-38962 On the IMC/CEC, the EDG control line is connected to a data concentrator panel using a Data Concentrator Cable plugged into J13. The control line is broken out and sent to the Data Interface Module (DIM) Controller Board using one of the ten breakout connectors on the concentrator panel. EDG Data Connector J2 J4 J6 J8 J10 Data Concentrator Panel...
  • Page 28 LBI-38962 Cross Connect I/O Board ADVANCED CONTROL TECHNOLOGY, INC. PT. NO. 4103340G1 MADE IN USA EDG to DM Audio Interface Connector Cross Connect I/O Board...
  • Page 29 LBI-38962 On the IMC/CEC, the EDG audio lines are connected to an audio concentrator panel using an audio concentrator cable. The concentrator panel has four Champ connectors of which only two (J9 & J10) can be used for the EDG audio lines.
  • Page 30: Connecting To An Ac Source

    LBI-38962 CONNECTING TO AN AC SOURCE The EDG comes with two different AC line cords: one for use in the United States and the other for international use. One end of the international line cord does not have a plug on it so that you can add the connector needed for your country.
  • Page 31: Turning On The Edg

    LBI-38962 TURNING ON THE EDG To turn the EDG on, turn the key on the power supply to the UNLOCK position and flip the circuit breaker to the ON position. The following sequence occurs when the EDG is booted (via power cycle, reset key, or reboot command): EDG BOOT SEQUENCE Step...
  • Page 32 LBI-38962 A banner is displayed on the Diagnostic Board waits for parser to complete. Terminal. On configured boards, all small LEDs are SYSTEM.TXT is parsed a second time. lit. /cnfg/system.rpt is built with the results. Phase 1 verifies each command and its parameters.
  • Page 33: Vcom24 Boot Error Codes

    LBI-38962 VCOM24 Boot Error Codes If an error is detected while starting the application on the VCOM24, one of the following LED patterns will be displayed on the eight small LEDs. LEDs Error Severity 7 and 0 OS Clock could not be started. Fatal 7 and 1 Memory Manager could not be initialized.
  • Page 34: Modifying The Rest Of The Edacs System

    LBI-38962 MODIFYING THE REST OF THE EDACS SYSTEM Section 4 of the Landline Data Release Notes (SRN1036-1) contains the complete installation procedure for Landline Data using the RDI Only version of the EDG. Execute Section 4 with the following exceptions: Section 4.1 Installation Order: Steps 4 (Install the EDG) and 5 (Connect the host computers) have already been performed.
  • Page 35: Maintenance

    LBI-38962 MAINTENANCE PASSWORD MAINTENANCE Passwords can be changed by logging in and using the passwd command. They can be added when logged in as root by entering the passwd command with the new User-id as the first parameter. They can be deleted by coping the /etc/passwd file to diskette, removing the line containing the user-id, coping the file back to the EDG and rebooting the EDG.
  • Page 36: Icmp Messages Returned By Edg

    LBI-38962 ICMP MESSAGES RETURNED BY EDG This section is relevant only to those configurations containing IP hosts. ICMP TYPE ICMP Code Reason Echo Reply Echo Request received Destination Network 1. EDG has failed to sync with the IMC on Unreachable Unreachable Startup.
  • Page 37: Trouble-Shooting Guide

    LBI-38962 TROUBLE-SHOOTING GUIDE When trying to correct problems, the activity log, /cnfg/system.rpt, ICMP messages, and Site Reports can be useful in locating problems. If the problem can't be resolved, contact your EGE Service Representative. Problem Corrective Actions EDG Fails to power up 1.
  • Page 38 LBI-38962 Problem Corrective Actions Telnet or FTP are not accepted 1. Verify that host has the correct IP Address of the EDG CAP External Address. 2. Verify that the Host and EDG can reach each other by using "ping" or equivalent. 3.
  • Page 39 LBI-38962 Problem Corrective Actions Time interval between consecutive 1. Verify that the radio is in range and isn't being interfered calls is excessive. with. 2. Verify that the SYSTEM.TXT Outbound_Msg_Delay value isn't too large. TSI Boards run out of memory. 1.
  • Page 40 LBI-38962 Ericsson-GE Mobile Communications Inc. Mountain View Road • Lynchburg, Virginia 24502 Printed in U.S.A.

Table of Contents