Ericsson LBI-38965B installation manual Initial Installation, Prerequisites

Page 26

LBI-38965

INSTALLATION

Configuration Tips

The TCP port number selection can be of significance if the BCU/CAL is attached to a large or TCP protocol intensive network. If you are unsure of TCP port usage on your network, consult you network administrator prior to assigning these values. In general, beginning TCP port definition at 5000 is safe for most applications. A convenient rule of thumb is to start at 5000, with the lower digits of the port reflecting the associated site number. For example, use TCP port number 5010 for site 10.

The parameters defined in CAL.DAT must be known when the Emulex terminal servers are to be configured. Have a hard copy of this file available when you are ready to set up the terminal servers.

The System Manager must be properly configured to recognize the sites that the BCU/CAL is simulating. Be sure that these sites have been defined and the passwords are correct prior to connection establishment attempts between the System Manager and the BCU/CAL.

4.2.2. Initial Installation

The following section discusses software installation on a new BCU/CAL. An example of the expected terminal display during this sequence is also provided. This example is annotated with comments indicating user activity/procedures during the installation, as well as general information regarding the process.

PREREQUISITES

1.Verify that the BCU/CAL unit does not have power currently applied.

2.Verify that the BCU/CAL is correctly connected to a VT100-compatible terminal (user console), the IMC CAM, and the local area network (LAN) (if applicable).

3.Verify that the user console is configured as follows:

a.9600 baud, 1 start bit, 1 stop bit, no parity.

b.VT100 personality. Terminal is DTE.

c.No translation of CR to CR/LF.

d.Local echo off. Tab stop at 8 characters.

e.DCE/DTE handshaking off.

f.XON/XOFF flow control is optional. The BCU/CAL does support flow control.

4.Edit the user configuration files contained on Installation Diskette 4.

a.Edit the text file, IP.DAT, to define the unit’s Internet parameters on the local network. If the unit will not have a network connection, the file IP.DAT may be left unmodified from that supplied with the release distribution.

b.If initial routing entries are desired, edit the file ROUTES.DAT.

c.If the NFS feature is purchased, edit EXPORTS.DAT. It is a template file for configuring NFS clients of the BCU/CAL. Client entries are specified as a BCU/CAL system disk directory, followed by the IP address of the client permitted to mount it. A log file (1.2/log/nfs.log) is generated on each system boot. The log summarizes processing of this file, indicating what has been exported, who received the export, and any errors encountered in this file. This file is processed during the application loading (boot) phase only. Modifications made after the unit is up and running will take effect during the next system boot.

26

Page 25 Page 27
Image 26
Page 25 Page 27
Contents Ericssonz LBI-38965 Table of Contents Table of Contents Introduction BCU/CAL ArchitectureCall Types Supported BCU Functional DescriptionCAL Functional Description Introduction Physical Specifications Physical Description and CompatibilityBCU/CAL Architecture TVME147 CPUCPU Compatibility Backwards CompatibilityBCU Operational Specifications SpecificationsCommon BCU and CAL Operational Specifications Billing Architecture Billing Architecture BCU Operation OverviewConversations Group Billing ModeRF Channel Usage Air Time Grouping CallsContents File NameDatabase Elements Default DataOperator Functions Unit DataCDR Processing CDR Processing ErrorsCall Processing Call Processing CDR OutputProtocol Supported CAL Operational SpecificationsSystem Manager Interface Additional Product Features Network File System CAL Operation OverviewInstallation Hardware InstallationSoftware Installation Distribution MediaInstallation Diskette UsageIP.DAT File Parameters ROUTES.DAT Configuration FileParameter MeaningEXPORTS.DAT Configuration File Directory clientip EXPORTS.DAT File ParametersCAL.DAT Configuration File CAL.DAT File ParametersInitial Installation PrerequisitesInstallation Installation User Information Password Default System AccountsLogin Access LevelPrerequisite User Information Entering bcs invokes the BCS programSystem Disk Booting User Information Invoke the BCS program Software UpgradesProper System Shutdown CAL Terminal Server Configuration # accessConfiguration Tips ExampleThis page intentionally left blank Appendix a Edacs Billing CDR Format Billing for Multiple Sites OverviewBilling by Conversation Record EncodingMULTIPLE-SITE Calls Record LayoutSINGLE-SITE Calls CDR Radix-64 DigitMOBILE-TO-LAND Telephone Interconnect Calls Table A.1 Call Detail Record Field DescriptionsTable A.2 Call Types Call Type DefinitionsCall Type Hex Decimal DescriptionDescription Valid with Rec. Type A0-FF Call Type Bit Fields Table A.3 Call Type Bit Field DefinitionsCDR File Topics Page Appendix B Physical Configuration Details Jumper Settings Figure B.1 Tvme 147SA1 Single-Board Computer Figure B.2 Tvme 712/M Transition Module Figure B.4 fv5310 Main Board Figure B.5 fv5310 Mezzanine Card Scsi Connector Pwr Table B.1 WANServer Port Connector DB-25F Signal NameCable Pinouts FunctionTable B.2 WANServer Port Table B.3 WANServer Port Table B.4 WANServer Port Table B.5 BCU/CAL Hdlc Loopback Cable Specification DB-25M Connector M/W BCU/CAL Port Signal NameFigure B.9 CAL Terminal Server to Distribution Panel Cable Figure B.10 CAL 32-Port Configuration Computer Terminal Appendix C Fault Tolerance Figure C.1 Edacs Billing Fault Tolerant Architecture Redundant Operation
Top Page Image Contents