Ericsson LBI-38965B installation manual EXPORTS.DAT Configuration File

Page 24

LBI-38965

INSTALLATION

Configuration Tips

Network routes should be entered in a logical order. That is, if there are multiple gateways between the BCU/CAL and a destination, the most direct route(s) should be specified first.

Network routes may be manually added and deleted using the route command discussed in the User Interface Manual (LBI-38967). If you are unsure of proper routing, use the route command to experimentally determine the proper, or most efficient, parameters and then add these to the ROUTES.DAT file.

Proper routing is intimately related to the IP address and subnet mask specified in the IP.DAT configuration file. Keep these parameters in mind when adjusting ROUTES.DAT contents.

4.2.1.1.3. EXPORTS.DAT Configuration File

The EXPORTS.DAT file only applies to BCU/CAL units which have been purchased with the NFS Server software feature. The NFS feature is always provided with the BCU. It is an option for the CAL feature. BCU users may disable the NFS by using the “product” command discussed in LBI-38967.

EXPORTS.DAT defines which network clients are privileged to mount the BCU/CAL system disk. Example exports provided on the template disk are commented out (i.e., preceded with a # character), and thus have no effect when the file is processed.

A log file (1.2/log/nfs.log) is generated on each system boot. The log summarizes the processing of this file, indicating what has been exported, who received the export, and any errors encountered in processing the EXPORTS.DAT file.

Export entries are specified in the following form:

directory client_ip

Table 5 - EXPORTS.DAT File Parameters

Parameter

directory

client_ip

Meaning

Directory structure(s) to be exported. Must be a fully specified, valid directory on the BCU/CAL system disk (volume 1.2). Note that directories are case-sensitive.

Specifying the BCU/CAL root directory (1.2/) indicates that the entire volume may be mounted by the host specified by client_ip.

Internet address of the NFS client permitted to mount directory, specified in dotted-decimal notation. If no address is specified, it indicates that any client may mount the directory.

The examples below show several valid export entries in the EXPORTS.DAT file:

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

#In the following example, hosts `fallwell and `hagee may NFS mount

#the entire BCU/CAL system disk (volume 1.2).

#Host `robertson may only mount the BCU/CAL cdr directory.

#Any host may mount the log directory.

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

1.2/

147.117.37.245

# host name - fallwell

1.2/

147.117.37.248

# host name - hagee

1.2/cdr

147.117.37.249

# host name - robertson

1.2/log

 

# any client may mount

24

Page 23 Page 25
Image 24
Page 23 Page 25
Contents Ericssonz LBI-38965 Table of Contents Table of Contents Introduction BCU/CAL ArchitectureBCU Functional Description CAL Functional DescriptionCall Types Supported Introduction Physical Specifications Physical Description and CompatibilityBCU/CAL Architecture TVME147 CPUCPU Compatibility Backwards CompatibilitySpecifications Common BCU and CAL Operational SpecificationsBCU Operational Specifications Billing Architecture Billing Architecture BCU Operation OverviewGroup Billing Mode RF Channel Usage Air TimeConversations Grouping CallsContents File NameDefault Data Operator FunctionsDatabase Elements Unit DataCDR Processing Errors Call ProcessingCDR Processing Call Processing CDR OutputCAL Operational Specifications System Manager InterfaceProtocol Supported Additional Product Features Network File System CAL Operation OverviewInstallation Hardware InstallationSoftware Installation Distribution MediaInstallation Diskette UsageROUTES.DAT Configuration File ParameterIP.DAT File Parameters MeaningEXPORTS.DAT Configuration File Directory clientip EXPORTS.DAT File ParametersCAL.DAT Configuration File CAL.DAT File ParametersInitial Installation PrerequisitesInstallation Installation User Information Default System Accounts LoginPassword Access LevelPrerequisite User Information Entering bcs invokes the BCS programSystem Disk Booting Software Upgrades Proper System ShutdownUser Information Invoke the BCS program CAL Terminal Server Configuration # accessConfiguration Tips ExampleThis page intentionally left blank Appendix a Edacs Billing CDR Format Overview Billing by ConversationBilling for Multiple Sites Record EncodingRecord Layout SINGLE-SITE CallsMULTIPLE-SITE Calls CDR Radix-64 DigitMOBILE-TO-LAND Telephone Interconnect Calls Table A.1 Call Detail Record Field DescriptionsCall Type Definitions Call Type Hex DecimalTable A.2 Call Types 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 Connector DB-25F Signal Name Cable PinoutsTable B.1 WANServer Port 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