Sony Ericsson LBI-38965 installation manual File Name Usage, Parameter Meaning

Page 20

LBI-38965

The following table summarizes the configuration files contained on Installation Diskette 4. These files are provided in template form, and should be modified to suit customer-specific requirements. The files are in MS-DOS format, and may be edited with any ASCII text editor.

 

Table 2 - BCU/CAL Configuration Diskette

 

 

File Name

Usage

IP.DAT

Defines the IP address, subnet mask, and host name of the BCU/CAL.

ROUTES.DAT

Defines network routing paths between the BCU/CAL and other hosts on the customer’s

 

network. Syntax is similar to the UNIX /etc/gateways file.

EXPORTS.DAT

Defines the BCU/CAL NFS export list for units which have been purchased with the NFS file

 

server software feature. File contents specify NFS client IP address(es) and the BCU/CAL

 

directory(s) they are privileged to mount. Syntax is similar to the UNIX/etc/exports file.

CAL.DAT

Defines the site interfaces from CAL to the EDACS System Manager. Contents of this file

 

are directly related to configuration parameters which must be set on the Emulex Terminal

 

Server(s).

 

 

4.2.1.1. User Configuration Files

This section discusses the contents of the user configuration files contained on Installation Diskette 4. These files should be modified according to customer requirements. When changes are made to the file contents, the BCU/CAL should be rebooted with the diskette installed in the floppy drive.

4.2.1.1.1. IP.DAT Configuration File

The IP.DAT configuration file is provided in template form on Installation Diskette 4. This file is common to both the BCU and CAL feature licenses. It defines the unit's Internet parameters on the end user's local or wide area network. The following three lines show the default contents of the IP.DAT file. The values shown in bold print should be modified by the end user. Only “space” characters should be used between the parameter keywords and the end user assigned values. Any errors detected in the file will be displayed on the local console during system boot.

#######################################################################

#######################################################################

IP_ADDRESS

147.117.37.226

HOST_NAME

bcu01

SUBNET_MASK

FFFFF000

 

Table 3 - IP.DAT File Parameters

 

 

Parameter

Meaning

IP_ADDRESS

IP address of the BCU/CAL, in Internet dotted-decimal notation.

HOST_NAME

Host name of the BCU/CAL, up to 32 characters long.

SUBNET_MASK

IP subnet mask for the BCU/CAL. Specified as 8 hexadecimal digits, in upper case.

 

 

4.2.1.1.2. ROUTES.DAT Configuration File

The ROUTES.DAT configuration file specifies network routing paths to be established at system boot. Typically, this file will only be required if the BCU/CAL is connected to a wide area network, where routers exist between the unit and other customer host facilities. The template file contains a few example routes, which are commented out (i.e., preceded with a # character). If no network routing is required, this file may be omitted, or left unaltered.

A log file (1.2/log/routes.log) is generated on each system boot. This file contains a summary of successful routing additions, as well as any errors detected during processing of the ROUTES.DAT file.

20

Image 20
Contents System and Installation Manual Table of Contents LBI-38965Table of Contents Introduction BCU/CAL ArchitectureCall Types Supported BCU Functional DescriptionCAL Functional Description 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 OverviewGroup Billing Mode RF Channel Usage Air TimeConversations Grouping CallsFile Name Contents Default Data Operator FunctionsDatabase Elements Unit DataCDR Processing Errors Call ProcessingCDR Processing Call Processing CDR OutputProtocol Supported CAL Operational SpecificationsSystem Manager Interface Additional Product Features Network File System CAL Operation OverviewInstallation Hardware InstallationSoftware Installation Installation Contents DisketteFile Name Usage Parameter MeaningEXPORTS.DAT Configuration File ParameterCAL.DAT Configuration File Directory Clientip EXPORTS.DAT File ParametersCAL.DAT File Parameters SITE01Initial Installation PrerequisitesInstallation Return Login Password Access Level First-Time ConfigurationDefault System Accounts Prerequisite User Information Entering bcs invokes the BCS programSystem Disk Booting Proper System Shutdown User Information Invoke the BCS programCAL Terminal Server Configuration Software UpgradesExample Configuration Tips Page Appendix a Edacs Billing CDR Format Overview Billing by ConversationBilling for Multiple Sites Record EncodingRecord Layout SINGLE-SITE CallsMULTIPLE-SITE Calls MOBILE-TO-LAND Telephone Interconnect CallsTable A.1 Call Detail Record Field Descriptions Name Size Format Range/Values DescriptionCall Type Description Valid with Hex Decimal Rec. Type Call Type DefinitionsTable A.2 Call Types A0-FF Call Type Bit Fields Table A.3 Call Type Bit Field DefinitionsCDR File Topics 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 DB-25F Signal Name Function Connector Cable PinoutsTable B.1 WANServer Port Table B.2 WANServer PortTable B.3 WANServer Port Table B.4 WANServer PortTable B.5 BCU/CAL Hdlc Loopback Cable Specification DB-25M Connector Signal Name Function BCU/CAL PortFigure B.9 CAL Terminal Server to Distribution Panel Cable A14 INM AC H106 Computer Terminal Appendix C Fault Tolerance Figure C.1 Edacs Billing Fault Tolerant Architecture Redundant Operation