Ericsson LBI-38965B installation manual Default System Accounts, Login, Password, Access Level

Page 30

LBI-38965

INSTALLATION

4.2.2.1. First-Time Configuration

 

The following section describes the

minimal set of system initializations that a user must perform to set up a

BCU/CAL.

 

When the BCU/CAL software is first installed, three user accounts are initialized. Each account has a varying level of system access security. The following table defines the initial accounts and their passwords, arranged in decreasing levels of access. The login name and password are case-sensitive. These passwords can be changed from their default values, and new accounts installed, using the passwd command. Any new accounts added will have the same level of access as the "user" account.

Table 7 - Default System Accounts

Login

root

admin user

Password

root

admin

user

Access Level

Anything. This account is the “super-user.”

Can access any BCS commands for system configuration.

Most restricted, particularly for the BCS commands.

Log onto the BCU/CAL under the "root" account. The console display will be similar to the following:

Login: root

Password:

Copyright (c) Integrated Systems, Inc., 1992. Welcome to pSOSystem...

pSH+>

USER INFORMATION: Enter “ls” to observe the root level directory files and subdirectories which were created during the software installation process.

pSH+> ls

 

 

 

BITMAP.SYS

backup

etc

mnt

FLIST.SYS

bin

export

tmp

LOADER.SX

cdr

loads

usr

activity

cnfg

log

var

USER INFORMATION: The following example shows the configuration files for the unit. The .BIN files were created during the software installation process.

pSH+> cd cnfg

 

 

 

 

 

pSH+> ls -als

 

 

 

 

 

total 41

 

 

 

 

 

2

-rwxrwxrwx

1

root

622

Feb 01 1994 10:45 CAL.DAT

2

-rwxrwxrwx

1

root

892

Feb 01 1994

10:45 IP.DAT

2

-rwxrwxrwx

1

root

568

Feb 01 1994

10:47 SYSTEM.BIN

1

-rwxrwxrwx

1

root

131072

Feb 01 1994

10:47 UNIT.BIN

33

-rwxrwxrwx

1

root

16384

Feb 01 1994

10:47 GROUP.BIN

USER ACTION: Two system parameters may need to be set. If the BCU/CAL is operating in a Multi- Node/StarGate configuration, the IMC NIM slot number needs to be defined. If the BCU/CAL service area (IMC) has a Jessica interconnect system installed, the IMC PIM slot number needs to be defined. These parameters must be set appropriately for the BCU to correctly provide billing for calls involving these “sites” (i.e., StarGate or Jessica). They are required by the CAL to simulate secondary drops from the site(s) it is providing service for. If the parameter (NIM or PIM slot) does not apply, it should be set to zero (default value).

30

Image 30
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 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 OutputCAL Operational Specifications System Manager InterfaceProtocol Supported 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 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 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