BSC Terminal User Guide (O & M)

Alcatel 900/1800 BSS
BSC Terminal User Guide

O&M Document LMT User Guide
3BK 20351 AAAA PCZZA Ed. 02
Status Change Note
Released
Short Title BSC TUG All rights reserved. Passing on and copying of this document, use and communication of its contents not permitted without written authorization from Alcatel.
2 / 136
Contents
Contents
Preface . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1 Installing and Starting the Terminal . . . . . . . . . . . . . . . . . . 1.1 Terminal Description . . . . . . . . . . . . . . . . . . . . . . . . . . . 1.1.1 Hardware Requirements . . . . . . . . . . . . . . 1.1.2 Software Requirements . . . . . . . . . . . . . . . 1.1.3 Communication Protocols . . . . . . . . . . . . . Installing an X.25 PBA in the Terminal . . . . . . . . . . . . 1.2.1 EICON C20 PBA . . . . . . . . . . . . . . . . . . . . 1.2.2 EICON C31 PBA . . . . . . . . . . . . . . . . . . . . Installing the Terminal Software . . . . . . . . . . . . . . . . . 1.3.1 Installing the Windows BSC Terminal Software . . . . . . . . . . . . . . . . . . . . . . . . . . . 1.3.2 Installing the X.25 Software . . . . . . . . . . . 1.3.3 Configuring the X.25 Software . . . . . . . . . Connecting the Terminal to the BSC . . . . . . . . . . . . . Starting the Terminal Software . . . . . . . . . . . . . . . . . . Stopping the BSC Terminal Software . . . . . . . . . . . . . BSC Terminal Menu . . . . . . . . . . . . . . . . . . . . . . . . . . . 2.1.1 BSC Terminal Menu Tree . . . . . . . . . . . . . . 2.1.2 Commands Menu . . . . . . . . . . . . . . . . . . . Toolbar . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Command Result display in Status Bar . . . . . . . . . . . Report Handling . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2.4.1 Compressed View . . . . . . . . . . . . . . . . . . . 2.4.2 Full View . . . . . . . . . . . . . . . . . . . . . . . . . . . 2.4.3 Saving Reports . . . . . . . . . . . . . . . . . . . . . . 2.4.4 Opening a New Report View Window . . Transferring Files from the Terminal to the BSC . . . . Transferring Files from the BSC to the Terminal . . . . Transferring Files Between SSDs . . . . . . . . . . . . . . . . . Backing Up the DLS . . . . . . . . . . . . . . . . . . . . . . . . . . . Formatting a Simplex SSD . . . . . . . . . . . . . . . . . . . . . . Formatting a Duplex SSD . . . . . . . . . . . . . . . . . . . . . . . Displaying SSD Information . . . . . . . . . . . . . . . . . . . . Deleting BSC Files . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9 13 14 14 14 15 16 16 16 17 17 19 21 24 26 29 31 32 32 34 35 35 36 36 38 39 39 41 42 44 45 47 48 49 50 51
1.2 1.3
1.4 1.5 1.6 2 2.1 2.2 2.3 2.4
Terminal Menus and Functions . . . . . . . . . . . . . . . . . . . . . .
Disk Operations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3.1 3.2 3.3 3.4 3.5 3.6 3.7 3.8
3 / 136
Contents
SBL Management . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4.1 4.2 4.3 4.4 4.5 4.6 4.7 4.8 4.9 SBL Types and States . . . . . . . . . . . . . . . . . . . . . . . . . . . Resetting SBLs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Verifying SBLs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Restarting SBLs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Initializing SBLs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Disabling SBLs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Reading SBL Status . . . . . . . . . . . . . . . . . . . . . . . . . . . . Reading SBL State Lists . . . . . . . . . . . . . . . . . . . . . . . . . Testing SBLs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Displaying Alarm Lists . . . . . . . . . . . . . . . . . . . . . . . . . Enabling PC Reporting . . . . . . . . . . . . . . . . . . . . . . . . . Extending BSC Configuration . . . . . . . . . . . . . . . . . . . Downloading BSC Extension Software . . . . . . . . . . . . Resetting BSC Extension . . . . . . . . . . . . . . . . . . . . . . . . Reducing BSC Configuration . . . . . . . . . . . . . . . . . . . . Modifying BSC Configuration . . . . . . . . . . . . . . . . . . . Disabling Switch For Extension . . . . . . . . . . . . . . . . . . Initializing Switch After Reduction . . . . . . . . . . . . . . . . Adding N7 Link . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Broadcast Bus Testing . . . . . . . . . . . . . . . . . . . . . . . . . . Cable Testing . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Clock Testing . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . DC/DC Convertor Testing . . . . . . . . . . . . . . . . . . . . . . Termination Plug Testing . . . . . . . . . . . . . . . . . . . . . . . Complete G2 Testing . . . . . . . . . . . . . . . . . . . . . . . . . . Stop Loop Testing . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Stop Testing . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Going Operational . . . . . . . . . . . . . . . . . . . . . . . . . . . . Starting Traces . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Stopping Traces . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Listing Trace Jobs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Reading Trace Files from the BSC . . . . . . . . . . . . . . . . Deleting Trace Files from the BSC . . . . . . . . . . . . . . .
53 54 56 57 59 60 61 62 63 64 65 66 67 69 70 71 72 73 74 75 76 77 78 79 80 81 82 83 84 85 86 87 88 90 91 92 93
Alarm Management . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5.1 5.2
BSC Extension and Reduction . . . . . . . . . . . . . . . . . . . . . . . . 6.1 6.2 6.3 6.4 6.5 6.6 6.7 6.8 6.9 6.10 6.11 6.12 6.13 6.14 6.15 6.16 6.17
Trace Management . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7.1 7.2 7.3 7.4 7.5
4 / 136
Contents
Miscellaneous Terminal Operations . . . . . . . . . . . . . . . . . . 8.1 8.2 8.3 8.4 8.5 8.6 8.7 8.8 8.9 8.10 8.11 8.12 Initializing the System . . . . . . . . . . . . . . . . . . . . . . . . . . Loading Minibuild . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Displaying the Date and Time . . . . . . . . . . . . . . . . . . . Modifying the Date and Time . . . . . . . . . . . . . . . . . . . Adjusting the Time . . . . . . . . . . . . . . . . . . . . . . . . . . . . Performing Logs of Commands and Reports . . . . . . Monitoring the Status of A BTS Download . . . . . . . . Setting the BTS Download Status Timers . . . . . . . . . . Copy BSS Software to Terminal Hard Disk . . . . . . . . Installing New BSS Software on an Active BSC . . . . . Installing a New DLS on an Active BSC . . . . . . . . . . . Installing and Starting Software on a BSC . . . . . . . . . Test Report Format . . . . . . . . . . . . . . . . . . . . . . . . . . . . CPR/DTC/TCU Test Results . . . . . . . . . . . . . . . . . . . . . Link/Switch Test Results . . . . . . . . . . . . . . . . . . . . . . . . . N7 Test Results . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . ..........................................
95 96 97 99 100 101 102 103 104 105 106 108 110 113 114 116 121 128 131 133
Test Command Results . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9.1 9.2 9.3 9.4 Index
Abbreviations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
5 / 136
Contents
Figures
Figure 1 Figure 2 Figure 3 Figure 4 Figure 5 Figure 6 Figure 7 Figure 8 Figure 9 Figure 10 Figure 11 Figure 12 Figure 13 Figure 14 Figure 15 Figure 16 Figure 17 Figure 18 Figure 19 Figure 20 Figure 21 Figure 22 Figure 23 Figure 24 Figure 25 Figure 26 Figure 27 Figure 28 Figure 29 Figure 30 Figure 31 Figure 32 Figure 33 Figure 34 Figure 35 Figure 36 Figure 37 Figure 38 Figure 39 Figure 40 WinBSC Program Group . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18 Eicon Configuration Window . . . . . . . . . . . . . . . . . . . . . . . . . . 20 Eicon Configuration Window - with X.25 General Properties Sheet for EiconCard . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 21 Eicon Configuration Window - with HDLC Advanced Properties Sheet for EiconCard . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 22 Eicon Configuration Window - with Sync General Properties Sheet for EiconCard . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 23 RS 232 Asynchronous Link Connection . . . . . . . . . . . . . . . . . 24 X.25 EICON C20 Synchronous Link Connection . . . . . . . . . . 25 X.25 EICON C31 Synchronous Link Connection . . . . . . . . . . 25 BSC Communication Control Window . . . . . . . . . . . . . . . . . . 26 X.25 Dialing Properties Window . . . . . . . . . . . . . . . . . . . . . . . . 27 Add Remote Connection Window . . . . . . . . . . . . . . . . . . . . . . 28 BSC Terminal Window . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 28 Communication Icon . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 29 Close BSC Connection Window . . . . . . . . . . . . . . . . . . . . . . . . 29 BSC Terminal Window . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 32 BSC Terminal Menu Tree - Except for Commands . . . . . . . . 32 BSC Terminal Commands Menu Tree . . . . . . . . . . . . . . . . . . . 34 Compressed Report View Window . . . . . . . . . . . . . . . . . . . . . . 36 Extra Information Settings . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 37 Example: Report Windows in Full View Mode . . . . . . . . . . . . 39 File Transfer from PC to BSC Window . . . . . . . . . . . . . . . . . . . 42 File Transfer from PC to BSC Window - with Available Files Selected . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 43 File Transfer from BSC to PC Window . . . . . . . . . . . . . . . . . . . 44 File Transfer from BSC to BSC Window . . . . . . . . . . . . . . . . . . 45 DLS Backup Window . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 47 Format SSD Window - with Available Files Selected . . . . . . 48 Format Duplex SSD Window . . . . . . . . . . . . . . . . . . . . . . . . . . . 49 Control SSD Window . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 50 Delete File Window . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 51 SBL Reset Window . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 56 SBL Verify Window . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 57 SBL Restart Window . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 59 SBL Initialize Window . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 60 SBL Disable Window . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 61 SBL Read Status Window . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 62 SBL State List Window . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 63 SBL Test Window . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 64 Display Alarm List Window . . . . . . . . . . . . . . . . . . . . . . . . . . . . 66 Enable PC Reporting Window . . . . . . . . . . . . . . . . . . . . . . . . . . 67 BSC Extend Config Window . . . . . . . . . . . . . . . . . . . . . . . . . . . 70
6 / 136
Contents
Figure 41 Figure 42 Figure 43 Figure 44 Figure 45 Figure 46 Figure 47 Figure 48 Figure 49 Figure 50 Figure 51 Figure 52 Figure 53 Figure 54 Figure 55 Figure 56 Figure 57 Figure 58 Figure 59 Figure 60 Figure 61 Figure 62 Figure 63 Figure 64 Figure 65 Figure 66 Figure 67 Figure 68 Figure 69 Figure 70
BSC Download Extension SW Window . . . . . . . . . . . . . . . . . . BSC Extension Reset Window . . . . . . . . . . . . . . . . . . . . . . . . . . BSC Reduce Config Window . . . . . . . . . . . . . . . . . . . . . . . . . . . BSC Config Modify Window . . . . . . . . . . . . . . . . . . . . . . . . . . . Disable Switch For Extension Window . . . . . . . . . . . . . . . . . . . Init Switch After Reduction Window . . . . . . . . . . . . . . . . . . . . . Add N7 Window . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Broadcast Test Window . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Network Test Window . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Clock Test Window . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . DC/DC Convertor Test Window . . . . . . . . . . . . . . . . . . . . . . . . Plug Test Window . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Complete G2 Test Window . . . . . . . . . . . . . . . . . . . . . . . . . . . . Stop Loop Window . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Stop Test Window . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Go For Operation Window . . . . . . . . . . . . . . . . . . . . . . . . . . . . Trace Start Window . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Trace Stop Window . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Trace Job List Window . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Read Trace File from BSC Window . . . . . . . . . . . . . . . . . . . . . . Trace File Read Config Window . . . . . . . . . . . . . . . . . . . . . . . . System Initialization Window . . . . . . . . . . . . . . . . . . . . . . . . . . . Minibuild Loading Window . . . . . . . . . . . . . . . . . . . . . . . . . . . . Display Date and Time Window . . . . . . . . . . . . . . . . . . . . . . . . Modify Date and Time Window . . . . . . . . . . . . . . . . . . . . . . . . Adjust Time Window . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Overview on BTS Window . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Timer Settings Window . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Active S CPRA or SYS CPRC Front Panel LEDs . . . . . . . . . . . . Example of Test Report for Switch . . . . . . . . . . . . . . . . . . . . . . .
71 72 73 74 75 76 77 78 79 80 81 82 83 84 85 86 88 90 91 92 93 96 97 99 100 101 103 104 106 114
7 / 136
Contents
Tables
Table Table Table Table Table Table Table Table Table Table Table Table Table Table Table Table Table Table 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 BSC Terminal Specific Options . . . . . . . . . . . . . . . . . . . . . . . . . SBL Types . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . SBL States . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Test Results Format for CPR/DTC/TCU . . . . . . . . . . . . . . . . . . . Test Raw Data Results for G1 and G2 CPRs . . . . . . . . . . . . . . Test Raw Data Results for G1 and G2 DTCs . . . . . . . . . . . . . . Test Raw Data Results for G1 and G2 TCUs . . . . . . . . . . . . . . Successful Test Results Format for Link/Switch . . . . . . . . . . . . Unsuccessful Test Results Format for Link/Switch . . . . . . . . . . Decode of Example Failure Data for Link/Switch . . . . . . . . . . Test Segment Results for Link/Switch . . . . . . . . . . . . . . . . . . . . Test Fault Type Results for Link/Switch . . . . . . . . . . . . . . . . . . . Test Raw Data Results for Link/Switch . . . . . . . . . . . . . . . . . . . Link/Switch Nibble Description . . . . . . . . . . . . . . . . . . . . . . . . . Test Results Format for N7 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Decode of Example Test Raw Data for N7 . . . . . . . . . . . . . . . Test Raw Data Results for N7 . . . . . . . . . . . . . . . . . . . . . . . . . . N7 Nibble Description . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 33 54 55 116 117 118 119 121 121 122 123 124 126 127 128 128 129 129
8 / 136
Preface
Preface
Purpose
The purpose of the Base Station Controller (BSC) Terminal User Guide is to describe how to install and set up a BSC terminal, and how to use the terminal to perform operations and maintenance functions. The guide covers the following BSC and Base Transceiver Station (BTS) configurations:
" " "
Generation One (G1) BSC Generation Two (G2) BSC G1 BTS - Mark One (MKI) (Hardware One (HW1) and Hardware Two (HW2)) and Mark Two (MKII). G2 BTS - Micro, Modular Micro, Mini, 1.25 meter and 2.0 meter G3 BTS - A9100, A910.
"
"
For more information about these configurations, refer to the BSC Functional Description and the BTS Functional Description.
Audience
The guide is intended for:

" "
System support engineers Operating personnel.
9 / 136
Preface
Assumed Knowledge
The reader must be familiar with the following:

" " "
IBM compatible Personal Computers (PCs) Microsoft Windows NT 4.0 operating system software Alcatel Operations & Maintenance (O&M) concepts for the Base Station Subsystem (BSS) Security Block (SBL) hierarchies of the BSC and the BTS Telecommunication techniques including line transmission and switching.
" "
Related Documents
Refer to the following documents for more information about the BSC, the BTS and the BSC terminal:
" " " " " " " " " " "
G1 BSC Functional Description G2 BSC Functional Description G1 BSC Hardware Description G2 BSC Hardware Description G2 BSC Cable Description BSS Alarm Dictionary BTS Functional Description BTS A9100/A910 Functional Description Maintenance Handbook Operations & Maintenance Reference Guide Operator Handbook.
Document Structure
The guide is structured as follows: Chapter 1 Installing and Starting the Terminal tells you how to install the terminal hardware, and install and start the software. It also tells you how to stop the software. Terminal Menus and Functions describes the terminal menus and the functions they provide. Disk Operations tells you how to perform disk operations for the terminal and the BSC. SBL Management tells you how to perform operations on SBLs. Alarm Management tells you how to manage alarms. BSC Extension and Reduction tells you how to manage the extension and reduction of BSC capacity.
Chapter 2 Chapter 3 Chapter 4 Chapter 5 Chapter 6
10 / 136
Preface
Chapter 7 Chapter 8 Chapter 9
Trace Management tells you how to manage traces. Miscellaneous Terminal Operations tells you how to perform miscellaneous BSC operations. Test Command Results provides additional information about reports generated as a result of an SBL test or an SBL verify command.
Abbreviations Abbreviations are defined at their first use, and listed after the final chapter. Index An Index is included at the end of the document.
Conventions
The following conventions are used in the guide:

"
Keyboard keys and buttons in windows are shown in a procedure within angle brackets. For example: 'Press <Enter>' and 'Click on <OK>'. The term 'Enter' in a procedure means type in the information and then press <Enter> or click on <OK>. Selections from a menu are shown in bold. For example: 'Select Eicon Wan Adapters'. Menu paths are shown in bold and include a right oriented arrow. For example: From the Main window, follow the menu path: Commands > Date & Time > Adjust Time
"
"
"
Useful Term
SBL
An SBL is a group of hardware and/or software providing a set of specific functions. If one part of the SBL fails, the entire SBL is out of service. SBL redundancy is provided to ensure operational integrity of the system.
11 / 136
Preface
12 / 136
1 Installing and Starting the Terminal

This chapter tells you how to install the terminal hardware and software and then start it. It describes the terminal and its requirements, and contains procedures for: G G G G G Installing an X.25 PBA in the terminal (optional) Installing the terminal software Connecting the terminal to the BSC Starting the terminal software. Stopping the terminal software.
13 / 136
1.1
Terminal Description
The BSC terminal is a PC connected to the BSC and running terminal software for accessing BSC O&M functions. You can use the BSC terminal to:
" "
Initiate actions in the BSC View reports associated with the actions on the terminal screen Observe system behavior Perform local management functions such as loading, testing and repairing the system.
" "
1.1.1
Hardware Requirements
The BSC terminal requires the following hardware:
" " "
Pentium processor 32 MB RAM system memory At least 100 MB of free hard disk space for program and data storage COM1 or COM2 serial port for the RS 232 asynchronous link Optional EICON C20 or C31 PBA for the X.25 synchronous link Parallel port for printing.
" "
"
1.1.2
Software Requirements
The BSC terminal requires the following software:
" " "
Microsoft Windows NT 4.0 operating system Windows BSC Terminal application software Optional Connections for Windows NT software for the X.25 EICON C20 or C31 link.
14 / 136
1.1.3
Communication Protocols
The interchange of data between the PC and the BSC via an RS 232 asynchronous link uses an Alcatel proprietary local protocol implemented in the terminal software. If a transmission failure in either direction is detected, a re transmission is attempted. If the transmission is unsuccessful after three attempts, the terminal software informs you that the interface is malfunctioning. For communication using an X.25 synchronous link, data transmission is performed according to the X.25 protocol. This is part of the Connections for Windows software for the EICON PBAs. The terminal is connected to one of the CPRAs (G1 BSC) or CPRCs (G2 BSC). If this processor fails, the terminal is restarted by the duplex CPRA or CPRC. If the restart also fails, communication with the BSC is no longer possible. If a CPRA or CPRC fails during a communication session, the session is aborted.
NOTICE
15 / 136
1.2
Installing an X.25 PBA in the Terminal

You can install an optional X.25 PBA in the terminal PC, if required, for connection to the BSC. If you are using the RS 232 asynchronous link connection to the BSC, skip this section and go to Section 1.3. The following X.25 PBAs can be installed in the terminal:
" "
EICON C20, for a desktop PC EICON C31, for a notebook PC. An anti static wrist strap (for EICON C20 only) A small crosshead screwdriver for removing the screws on the cover of the PC (for EICON C20 only) The appropriate X.25 PBA.
Tools and Materials
You must have:

" "
"
1.2.1
EICON C20 PBA

To install an EICON C20 PBA in a desktop PC: 1. Ensure that the PC is powered off. 2. Use the screwdriver to undo the retaining screws, and then remove the cover from the PC. 3. Put on the anti static wrist strap. Connect the crocodile clip to a grounded metallic object, such as the PC casing. 4. Insert the PBA into a free Input/Output slot. 5. Remove the anti static wrist strap. 6. Replace the cover on the PC, and then secure it with the retaining screws.
1.2.2
EICON C31 PBA

Install an EICON C31 PBA into a PCMCIA slot at the side of a notebook PC. The PBA is marked with an arrow on one of its flat sides. Ensure that it is inserted with the arrow side uppermost, and in the direction indicated.
16 / 136
1.3
Installing the Terminal Software

You must install the terminal software according to requirements from the following source media:
" "
Windows BSC Terminal (4 diskettes) Connections for Windows NT (for the EICON X.25 link option) (CD ROM).
Prerequisites
If you are using the optional X.25 link, you must install the appropriate hardware (EICON PBA) in the terminal PC first (see Section 1.2). Then you must install and configure the terminal software, as described in this section, before you can use the terminal to communicate with the BSC. You do not need to connect the terminal PC to the BSC before installing and starting the terminal software. However, once it is connected, you must exit and restart the software to initialize the link.
Software Installation Process
To install and configure the terminal software, you must:

"
Install the Windows BSC Terminal software, as described in Section 1.3.1. Install and configure the optional X.25 link software, if required, as described in Sections 1.3.2 and 1.3.3.
"
1.3.1
Installing the Windows BSC Terminal Software

The Windows BSC Terminal software is required for whatever type of link is used to the BSC, RS 232 asynchronous or X.25 synchronous. To install the Windows BSC Terminal software: 1. Power on the PC and logon. 2. Insert the first Windows BSC Terminal diskette in the diskette drive. 3. From the Windows desktop, double click on My Computer. 4. Double click on 3 Floppy [A:].
17 / 136
5. Double click on Setup (Application) Follow the instructions displayed on the screen during the installation. Use default options where appropriate, and insert the other installation diskettes when required. Note Ignore the system error message "The following file(s) failed to self register", which can be displayed at the end of the installation. In the Setup Complete window at the end of the installation, you are asked if you want to restart the computer. 6. Remove the diskette from the diskette drive. 7. Select Restart the computer in the Setup Complete window, and then click on <Finish>. When the setup is complete, a WinBSC program group is created, as shown in Figure 1. This program group is accessed from the Start menu on the Windows desktop. Windows BSC Terminal is used to start the terminal program, and BSC Communication Control is used to select the link to the BSC.
Figure 1
WinBSC Program Group
When the PC restarts, go to Section 1.3.2 to install the X.25 software if you want to use an X.25 synchronous link to the BSC. Otherwise, go to Section 1.4 to connect the terminal to the BSC.
18 / 136
1.3.2
Installing the X.25 Software

To install the X.25 software for the EICON (C20 and C31) synchronous link to the BSC: 1. Logon to the PC as an Administrator or equivalent. 2. Insert the Connections for Windows NT CD ROM in the CD ROM drive. 3. From the Windows desktop, follow the menu path: Start > Settings > Control Panel The Control Panel window opens. 4. Double click on the Network icon to display the Network window. 5. Click on the Adapters tab. 6. Click on <Add> to display the Select Network Adapter window. 7. Select Eicon Wan Adapters from the scrollable list. 8. Click on <Have Disk>. 9. In the path field in the Insert Disk window, specify the CD ROM drive path (for example, D:\). 10. Click on <OK>. Follow the instructions displayed on the screen during the installation. Use default options where appropriate, until you are asked if you want to run the Eicon Configuration program. 11. Click on <Yes> to run the program. The Eicon Configuration window is displayed, as shown in Figure 2. Go to Section 1.3.3 to configure the X.25 software.
19 / 136
In Case of Problem
If something goes wrong during the use of Eicon Card do the following: 1. Go to Control Panel > Services. 2. Select EiconCard and click on <Stop>. 3. Then click on <Start> to restart EiconCard.
Figure 2
Eicon Configuration Window
20 / 136
1.3.3
Configuring the X.25 Software

To configure the X.25 software for the EICON (C20 and C31) synchronous link to the BSC: 1. In the Eicon Configuration window (see Figure 2), expand the EiconCard tree and the Port tree, and then select the X.25 icon (see Figure 3).
Figure 3
Eicon Configuration Window - with X.25 General Properties Sheet for EiconCard Put Node Type on DCE Put Packet Format to Basic Change Maximum and Default Packet Size to 1024 Change Maximum and Default Window Size to 2.
2. Click on the General tab and:

D D D D
3. Click on the Timers Tab and put Acknowledge on 500 msec. 4. Click on the Advanced Tab and put Max. Retry Count N3 to 5. 5. Expand the X.25 tree, and then select the HDLC icon. 6. Click on the Advanced Tab (see Figure 4).
21 / 136
Figure 4
Eicon Configuration Window - with HDLC Advanced Properties Sheet for EiconCard Check Point T1 = 2000 Ack Delay T2 = 500 Idle Probe T3 = 10000. Put Maximum Retry Count N2 to 5.
7. Set the timer to the following values:

D D D D
8. Expand the Direct tree, and then select the Sync icon. 9. Click on the General tab to display the Eicon Configuration window with the Sync General properties sheet, as shown in Figure 5.
22 / 136
Figure 5
Eicon Configuration Window - with Sync General Properties Sheet for EiconCard
10. From the Eicon Configuration window menu bar, follow the menu path: File > Exit 11. In the New Configuration pop up window, click on <Yes> to save the new configuration. 12. In the WAN Services Install pop up window, click on <No> to install no other services. 13. Click on <Close> to close the Network window. 14. In the Network Settings Change window, click on <Yes> to restart the computer. Go to Section 1.4 to connect the terminal to the BSC.
23 / 136
1.4
Connecting the Terminal to the BSC

The BSC terminal supports the following types of connection:
" " "
RS 232 asynchronous link X.25 synchronous link using EICON C20 PBA X.25 synchronous link using EICON C31 PBA.
When you open the front door of the BSC cabinet, put on the anti static wrist strap and connect the crocodile clip to a grounded metallic object, such as a cabinet casing. CAUTION
ATTENTION
Mobile Telephone Interference Operating a mobile telephone in the vicinity of the BSC with the doors open can interfere with the operation of the BSC. Do not use a mobile telephone when the BSC doors are open.
RS 232 Link
Open the cabinet front door and connect the RS 232 cable as shown in Figure 6.
Rear of Terminal
D 9 Connector RS 232 Cable (3BK 07948 GLAA)
COM1 or COM2 Port
O O S S S Y I I S
S Y S
B B C C
CPRC PBAs in G2 BSC cabinet
RS 232 Cable (3BK 07948 GLAA)
D 9 Connector
O S I
S O S S I
CPRA PBAs in G1 BSC cabinet
Figure 6
RS 232 Asynchronous Link Connection
24 / 136
X.25 EICON C20 PBA
Open the cabinet front door and connect the X.25 cable as shown in Figure 7.
X.25 Adapter (1AF 01138 AAAA) on EICON C20 PBA D 25 Connector X.25 Cable* (3BK 07760 GLAA) O O S S S Y I I S S Y S B B C C
Rear of Terminal Desktop PC
* The part number can differ from that shown, because it includes the length. See the G1 BSC Hardware Description and the G2 BSC Cable Description.
D 25 Connector X.25 Cable* (3BK 07760 GLAA) O S I S O S S I
Figure 7
X.25 EICON C20 Synchronous Link Connection Open the cabinet front door and connect the X.25 cable as shown in Figure 8.
X.25 EICON C31 PBA
Notebook PC Side of Terminal Cable supplied with EICON C31 PBA * The part number can differ from that shown, because it includes the length. See the G1 BSC Hardware Description and the G2 BSC Cable Description.
EICON C31 PBA in PCMCIA slot D 25 Connectors D 25 Connector O O S S S Y I I S S Y S B B C C
X.25 Cable* (3BK 07760 GLAA)
D 25 Connector X.25 Cable* (3BK 07760 AAAA) O S I S O S S I
Figure 8
X.25 EICON C31 Synchronous Link Connection
25 / 136
1.5
Starting the Terminal Software

You do not need to connect the BSC terminal PC to the BSC before starting the terminal software. However, once it is connected, you must exit and restart the software to initialize the link. To start the BSC terminal software: 1. Ensure that the terminal is connected to the BSC:
D
For an RS 232 asynchronous link, check that the COM1 or COM2 port of the terminal is connected to one of the System CPRA (S CPRA) (for a G1 BSC) or System CPRC (SYS CPRC) (for a G2 BSC) PBAs, as shown in Figure 6. For an X.25 synchronous link, check that the EICON port of the terminal is connected to one of the S CPRA (for a G1 BSC) or SYS CPRC (for a G2 BSC) PBAs, as shown in Figure 7 or Figure 8.
2. Logon to the PC. 3. From the Windows desktop, follow the menu path: Start > Programs > WinBSC > Windows BSC Terminal The BSC Communication Control program is started, and the BSC Communication Control window is displayed, as shown in Figure 9.
Figure 9
BSC Communication Control Window
26 / 136
4. If you are using an RS 232 asynchronous link, click on the COM1 or COM2 check box, as required, and then go to Step 9. If you are using an X.25 synchronous link, click on the X.25 check box (the Settings button is enabled, i.e., the text on the button changes to black). Note If a particular port is not available or not connected, it is disabled (shown in grey in the window) and you are unable to select it. 5. If you are using a direct connection to the BSC, go directly to Step 9. If you are using a remote connection to the BSC, click on <Settings> to display the X.25 Dialing Properties window, as shown in Figure 10.
Figure 10
X.25 Dialing Properties Window
6. Click in the Local Number field and enter the number of the local connection to the X.25 network. 7. Click on the Remote Connection drop down menu and select the required remote connection. You can add, modify, and delete entries to the Remote Connection drop down menu using <Add>, <Modify>, and <Delete>. For example, if you click <Add>, the Add Remote Connection window is displayed as shown in Figure 11.
27 / 136
Figure 11
Add Remote Connection Window
8. When you have selected the required remote connection, Click on <OK> to close the Dialing Properties window. 9. Click on <Connect> in the BSC Communication Control Window. The BSC terminal window is displayed, as shown in Figure 12.
Figure 12
BSC Terminal Window The Communication Icon (see Figure 13) is displayed at the right of the task bar.
28 / 136
Figure 13
Communication Icon
When communication with the BSC has been established, the Communication icon changes color to white. The facilities provided by the BSC terminal window are described in Chapter 2.
1.6
Stopping the BSC Terminal Software

When stopping the BSC Terminal software, you can choose whether or not to close the connection to the BSC. To stop the software: 1. From the BSC terminal window, follow the menu path: File > Exit The Close BSC Connection window is displayed, as shown in Figure 14
Figure 14
Close BSC Connection Window
2. To close the connection to the BSC click on <Yes>. To maintain the connection to the BSC, click on <No>.
29 / 136
30 / 136
2 Terminal Menus and Functions

This chapter describes the terminal menus and the functions they provide, and includes the: G G G BSC Terminal Menu Toolbar and status bar description Handling of reports.
31 / 136
2.1
BSC Terminal Menu

This section describes the BSC Terminal window (see Figure 15).
Menu bar Toolbar
Status bar
Figure 15
BSC Terminal Window
2.1.1
BSC Terminal Menu Tree

The BSC Terminal menu tree, except for the Commands menu, is shown in Figure 16. The Commands menu tree is shown in Figure 17.
File Commands Utilities BTS Download Status Reporting Mode Timer Settings... Minibuild Loading Logging View Window Toolbar Status Bar Extra Information Realtime Cascade Tile Horizontal Tile Vertical Arrange Icons Close All Help Menu Bar Help Topics About Win BSC
New Open Save Save As Exit
Figure 16
BSC Terminal Menu Tree - Except for Commands
32 / 136
The BSC terminal menu options specific to the BSC terminal software are described in table 1. Table 1
Menu File
BSC Terminal Specific Options

Option New Open Save Desciption Create a new Compressed Report View window. Open reports that have been stored in a Microsoft Access database into the Compressed Report View window. Save all the reports in the Compressed Report View window in a Microsoft Access database. If the reports have not been saved be fore, the Save As window is displayed. Save all the reports in the Compressed Report View window in a Microsoft Access database under a specified name. Set the reporting mode or the session timer for monitoring the downloading of files to multiple BTSs. Start a non running BSC quickly by loading new software based on a default BSS Masterfile. Refer to Section 8.2 for more information. Store commands and reports in a log file. This allows a detailed in vestigation to be performed at a later data. Refer to Section 8.6 for more information. Show or hide the Information column(s) in the Compressed Report View window. Determine whether a report received from the BSC is displayed in the Full Report View window, as well as the Compressed Report View window. In the Realtime mode, a report displayed in the Full Report View window is replaced when a new report is received from the BSC. Display help information by selecting this item. Help information can also be obtained by pressing the F1 key. When a command dia logue is displayed, pressing F1 causes context sensitive help to be provided.
Save As Utilities BTS Download Status Minibuild Loading Logging
View
Extra Information Real Time
Help
Help Topics
33 / 136
2.1.2
Commands Menu
The BSC Terminal Commands menu tree is shown in Figure 17.
Commands Menu
Date and Time Display Date & Time Modify Date & Time Adjust Time
Disk Operations File Transfer from PC to BSC File Transfer from BSC to PC File Transfer from BSC to BSC DLS Backup Format SSD Format Duplex SSD Control SSD Delete File
System Activation System Initialization
Alarm Handling Display Alarm List Enable PC Reporting
Commands Menu Test Handling SBL Test Equipment Handling SBL Reset SBL Verify SBL Restart SBL Initialize SBL Disable SBL Read Status SBL State List Extension & Reduction BSC Config Modify Add N7 Disable Switch For Extension Init Switch After Reduction BSC Extend Config BSC Extension Reset BSC Download Extension SW Go For Operation BSC Reduce Config Complete G2 Test Network Test Plug Check DC/DC Converter Test Broadcast Test Clock Test Stop Loop Stop Test Trace Invocation Trace Start Trace Stop Trace Job List Read Trace File From BSC Trace File Read Config
Figure 17
BSC Terminal Commands Menu Tree
34 / 136
2.2
Toolbar
The Toolbar contains shortcut buttons to some of the menu items (see Figure 15). Create a new Compressed Report View window. Open reports that have been stored in a Microsoft Access database into the Compressed Report View window. Save all the reports in the Compressed Report View window in a Microsoft Access database. If the reports have not been saved before, the Save As window is displayed. Display information concerning the version of the BSC terminal software and the release of the BSC where the terminal can be used. Not used.
2.3
Command Result display in Status Bar

The left side of the status bar displays the results of the communication between the terminal and the BSC. When a command is sent to the BSC, the message "Command accepted by BSC, waiting for report" is displayed on the status bar. When the report is received, the message "A report was sent by BSC" is displayed on the status bar. The Report View windows are updated according to whether or not the Realtime mode is enabled or disabled (see section 2.4). The other two parts of the bar display internal and external alarm reporting information.
35 / 136
2.4
Report Handling
The BSC sends reports to the BSC terminal to acknowledge commands, and to convey information in response to commands. Reports can be viewed in two formats:
"
Compressed Report View, which provides selected information about the event which has occurred Full Report View, which provides full information about the event which has occurred.
"
The BSC test report contains raw data and other data. Refer to Chapter 9 for more information on these data. By default, reports received from the BSC are displayed in the Compressed Report View window as they arrive. When the Realtime function is activated, reports are displayed in the Full View Report window when received from the BSC. A number of full view report windows can be simultaneously displayed by double clicking on the compressed report. This allows comparisons to be made between different reports.
2.4.1
Compressed View
When you first start the BSC terminal software, the Compressed Report View window is empty, as shown in Figure 15. As reports are received, they are displayed in the window in summary form, as shown in Figure 18.
Figure 18
Compressed Report View Window
To view a compressed report in full view, double click on the report. This window can be minimized or maximized, as required. It cannot be closed.
36 / 136
General Information
Compressed view reports comprise the following generic fields:

" " " " "
Number Date Time Report Type Job Result.
In addition to the generic fields, up to 15 Extra Info fields can be added to a report. You can determine the type of information contained in an extra information field by positioning the cursor on or near the field. A screen tip box indicates the type of information in the field.
Adding Extra Info Fields
To add Extra Info fields to a compressed report: 1. From the BSC Terminal menu bar, follow the menu path View > Extra Information The Extra Info Settings window is displayed, as shown in Figure 19.
Figure 19
Extra Information Settings
2. Click on the Report field drop down menu and select the required report from the list. Any extra information which has already been added to the report is displayed in the appropriate Extra Info fields. 3. To add extra information, click on the drop down menu of the required Extra Info field to display a list of the extra information which can be added to that particular report. Select the extra information you want to add.
37 / 136
4. Repeat step 3. for any other extra information you want to add to the report. 5. Click on <Save>to save the information. Note If you duplicate any extra information, the system generates a warning message. Some compressed reports have predefined default values. In this case the Use defaults button is enabled. To revert to the default values, click <Use defaults>. Reports in the Compressed Report View window can be sorted in the required order by clicking on the column title of the appropriate field. An arrow shows in which order and on which column the reports are sorted. In the Extra Info columns, the sort is text based. Sorts based on date, time and numbers are not possible in these columns. This is because of the variety of parameter types being displayed in a particular column.
Default Settings Sorting Reports
2.4.2
Full View
The fields provided in a full view report depend on the report type. Note The compressed version of the report is also displayed as the last entry in the Compressed Report View window. Figure 20 gives an example of the Report Window in the Realtime mode.
38 / 136
Figure 20
Example: Report Windows in Full View Mode If a field in a report is grey, this indicates that no information for that field was received from the BSC.
2.4.3
Saving Reports
To save reports in the Compressed Report View window, use the File/Save menu. The reports are saved in a Microsoft Access database. The Save type (which should already be filled in) is BSC Terminal Database (*.bdb). To print a saved report, you must open the report in Microsoft Access and then print it from there.
2.4.4
Opening a New Report View Window

To open a new Report view window or windows (depending on whether the view mode is Realtime or compressed) click on the create new file icon in the tool bar. A new Report View Window replaces the existing window. This function can also be performed by clicking on File in the menu bar and then clicking on New item.
39 / 136
40 / 136
3 Disk Operations
3 Disk Operations
This chapter tells you how to perform disk operations for the terminal and the BSC, and contains procedures for: G G G G G G G Transferring BSS files from the hard disk of the terminal to an SSD in the BSC Transferring BSS files from an SSD in the BSC to the hard disk of the terminal Transferring files between SSDs in the BSC Backing up the DLS file from an SSD to the hard disk of the terminal Formatting a simplex or duplex SSD Displaying disk and directory information Deleting BSC files.
ATTENTION
Performing disk operations such as SSD formatting can result in the loss of software and data.
NOTICE
Before transferring files, switch off the PC screen saver.
41 / 136
3 Disk Operations
3.1
Transferring Files from the Terminal to the BSC

Prerequisites Procedure
When transferring all the BSS files, you must ensure that all performance measurement jobs for the BSC are deleted first. To transfer files from the BSC terminal to an SSD in the BSC: 1. From the BSC Terminal menu bar, follow the menu path: Commands > Disk Operations > File Transfer from PC to BSC The File Transfer from PC to BSC window is displayed, as shown in Figure 21.
Figure 21
File Transfer from PC to BSC Window
2. Enter the PC directory path of the files for transfer, or click on <Browse> and navigate to the appropriate directory. The options All BSS Files and Steer Files are displayed in the Available Files panel together with other available files. 3. Select the appropriate destination disk. 4. Click on the appropriate option or file in the Available Files panel. The list of files is displayed, as shown in Figure 22.
42 / 136
3 Disk Operations
Figure 22
File Transfer from PC to BSC Window - with Available Files Selected
5. Select one or more files in the PC Files column or click on <Select All> to select all the files. 6. Click on <Go!> to start the file transfer.
43 / 136
3 Disk Operations
3.2
Transferring Files from the BSC to the Terminal

To transfer files from an SSD in the BSC to the BSC Terminal: 1. From the BSC Terminal menu bar, follow the menu path: Commands > Disk Operations > File Transfer from BSC to PC The File Transfer from BSC to PC window is displayed, as shown in Figure 23.
Figure 23
File Transfer from BSC to PC Window
2. Select the appropriate source disk. 3. In each of the File Identity fields in turn, enter the:
D D D D
Filename File number File version File sub version.
4. In the PC File field, enter a full PC pathname for the file being transferred. Alternatively, click on <Browse> and navigate to the appropriate directory, and then enter the required name for the file. 5. Click on <OK> to start the file transfer.
44 / 136
3 Disk Operations
3.3
Transferring Files Between SSDs

The File Transfer from BSC to BSC command allows you to transfer:
" " "
All BSS files A DLS file A single file.
ATTENTION
Do NOT attempt to Initialize either of the DISC SBLs while the file transfer is in progress, or perform a file copy or delete operation. Both disks can be corrupted.
If you are going to transfer the DLS file or all the BSS files, you must ensure that all performance measurement jobs for the BSC are deleted first. To transfer files between SSDs: 1. From the BSC Terminal menu bar, follow the menu path: Commands > Disk Operations > File Transfer from BSC to BSC The File Transfer from BSC to BSC window is displayed, as shown in Figure 24.
Figure 24
File Transfer from BSC to BSC Window
2. Select the appropriate source disk. 3. Select the appropriate destination disk.
45 / 136
3 Disk Operations
4. Check one of the following boxes as required:

D D D
All Files DLS File Custom (to select a single file)
If you selected All Files or DLS File, go directly to Step 6. If you selected Custom, continue to the next step. 5. Complete the Source File and Destination File fields. Enter in each field in turn the:
D D D D
6. Click on <OK> to start the file transfer.
46 / 136
3 Disk Operations
3.4
Backing Up the DLS

You must ensure that all performance measurement jobs for the BSC are deleted first. To back up the DLS file from an SSD to the hard disk of the BSC terminal: 1. From the BSC Terminal menu bar, follow the menu path: Commands > Disk Operations > DLS Backup The DLS Backup window is displayed, as shown in Figure 25.
Figure 25
DLS Backup Window
2. Select the appropriate source disk. 3. In each of the File Identity fields in turn, enter the:
D D D D
4. In the PC File field, enter a full PC pathname for the DLS file. Alternatively, click on <Browse> and navigate to the appropriate directory, and then enter the required name for the file. 5. Click on <OK> to start the back up.
47 / 136
3 Disk Operations
3.5
Formatting a Simplex SSD

NOTICE Formatting a simplex SSD results in the loss of software and data.
To format a simplex SSD from the contents of a specified file: 1. From the BSC Terminal menu bar, follow the menu path: Commands > Disk Operations > Format SSD The Format SSD window is displayed. 2. Enter the PC directory path of the files to be used for formatting, or click on <Browse> and navigate to the appropriate directory. The files available in the directory for formatting the destination disk are displayed in the Available Files panel. 3. Select the appropriate destination disk. 4. Select on the appropriate file in the Available Files panel. The list of files is displayed, as shown in Figure 26.
Figure 26
Format SSD Window - with Available Files Selected
5. Click on <GO!> to start formatting the SSD.
48 / 136
3 Disk Operations
3.6
Formatting a Duplex SSD

NOTICE Formatting a duplex SSD results in the loss of software and data.
To format a duplex SSD using information from the mate SSD: 1. From the BSC Terminal menu bar, follow the menu path: Commands > Disk Operations > Format Duplex SSD The Format Duplex SSD window is displayed, as shown in Figure 27.
Figure 27
Format Duplex SSD Window
2. Select the appropriate format direction. 3. Click on <OK> to start formatting the SSD.
49 / 136
3 Disk Operations
3.7
Displaying SSD Information

The Control SSD command allows you to obtain the following:
"
All the directory information concerning the files stored on the SSD Basic directory information concerning the files stored on the SSD Disk information concerning the type of SSD and how it is formatted.
"
"
To list disk or directory information: 1. From the BSC Terminal menu bar, follow the menu path: Commands > Disk Operations > Control SSD The Control SSD window is displayed, as shown in Figure 28.
Figure 28
Control SSD Window
2. Select the appropriate action. 3. Select the appropriate SSD. 4. Click on <OK> to start the Control SSD action. Depending on the action requested, one of the following reports is received:
" " "
Read Directory Large reports (one report for each file) Read Directory Small reports (one report for each file) Disk Info report.
50 / 136
3 Disk Operations
3.8
Deleting BSC Files

NOTICE Deleting a file can result in the loss of data. Always verify that the correct file identity is used.
To delete a file from a specified SSD: 1. From the BSC Terminal menu bar, follow the menu path: Commands > Disk Operations > Delete File The Delete File window is displayed, as shown in Figure 29.
Figure 29
Delete File Window
2. Select the appropriate SSD(s). 3. In each of the File Name fields in turn, enter the:
D D D D
4. Click on <OK> to delete the file. A Confirm File Delete dialog box is displayed.
51 / 136
3 Disk Operations
52 / 136
4 SBL Management
4 SBL Management
This chapter tells you how to perform operations on SBLs, and contains procedures for: G G G G G G G G Resetting SBLs Verifying SBLs Restarting SBLs Initializing SBLs Disabling SBLs Reading the status of SBLs Reading SBL State Lists Testing SBLs.
53 / 136
4 SBL Management
4.1
SBL Types and States

Table 2 lists the SBL types referenced in this chapter. Table 2
SBL Type ACH ATR BATTERY BC_RACK_BUS BC_SYS_BUS BSC BSC_ADAPT BSS BTS BTS_ADAPT BTS_O&M BTS_TEL CCF CLK_GEN CLK_REP CLLK CONV CPR CU DISC DTC EACB FHU FU LINK N7 OML OMU RA RS 232 RSL
SBL Types
Description A Channel A Trunk Battery Broadcast Rack Bus Broadcast System Bus Base Station Controller BSC Adaptor Base Station Subsystem Base Transceiver Station BTS Adaptor BTS Operations & Maintenance BTS Telecom Cabinet Cooling Fan Clock Generator Clock Repeater Clock Converter Central Processor Carrier Unit Solid State Disk Digital Trunk Controller External Alarm Collection Board Frequency Hopping Unit Frame Unit Network Link Number 7 Signaling Link Operations and Maintenance Signaling Link Operations & Maintenance Unit Radio Access RS 232 Connection Radio Signaling Link
54 / 136
4 SBL Management
SBL Type RTE RTS SWITCH TCU TR_O&M TSC TSL X25
Description Radio Test Equipment Radio Time Slot Network Switch Terminal Control Unit TSC Operations & Maintenance Transcoder Submultiplexer Controller TSC LAPD Link X.25 Link
Table 3 lists the SBL states referenced in this chapter. Table 3

SBL State EF FIT FLT FOS IT MSA MSD NEQ OPR SOS WTC
SBL States
Description External Fault Faulty In Traffic Faulty Faulty Out of Service In Traffic Maintenance Seized Automatically (due to an Alarm) Maintenance Seized (due to an operator action) Not Equipped Operator Out of Service Software Out of Service Wait Traffic Clear
55 / 136
4 SBL Management
4.2
Resetting SBLs
Resetting an SBL causes the Control Elements to be reloaded from either:
" "
The backup version of the software The new version of the software if a software replacement is being performed.
Note
The SBL Reset command is a combination of the SBL Disable and the SBL Initialize commands. To reset an SBL: 1. From the BSC Terminal menu bar, follow the menu path: Commands > Equipment Handling > SBL Reset The SBL Reset window is displayed, as shown in Figure 30.
Figure 30
SBL Reset Window
2. In the Object Class field, select SBL. 3. In the Unit Type field, select the appropriate unit type, BSC, BTS or TSC. 4. In the SBL Type field, select the appropriate SBL type. Refer to Table 2 for more information on SBL types. 5. In the Unit Number field, enter the unit number. 6. In the Nbr field, enter the SBL number. 7. In the SubNbr field, enter the SBL sub number. 8. Click on <OK> to reset the SBL. The SBL is put out of service. If the reset is successful, the SBL is returned to the IT state. Refer to Table 3 for more information on SBL states.
56 / 136
4 SBL Management
4.3
Verifying SBLs
The SBL Verify command allows you to set an SBL to the out of service state and to test the SBL. An SBL can be verified only if its status is one of the following:
" " " " "
IT FIT OPR FOS FLT.
Refer to Table 3 for more information on SBL states. A request for the verification of an SBL can be refused if any of the following are in progress:
" "
An action on the SBL itself An action on an SBL at a higher hierarchical level.
The action in progress can have been initiated automatically as a result of the error analysis function, or as a result of an operator request. Refer to the Operations & Maintenance Reference Guide for more information on SBL hierarchies.
Procedure
To verify an SBL: 1. From the BSC Terminal menu bar, follow the menu path: Commands > Equipment Handling > SBL Verify The SBL verify window is displayed, as shown in Figure 31.
Figure 31
SBL Verify Window
2. In the Object Class field, select SBL. 3. In the Unit Type field, select the appropriate unit type, BSC, BSS, BTS or TSC. 4. In the SBL Type field, select the appropriate SBL type. Refer to Table 2 for more information on SBL types.
57 / 136
4 SBL Management
5. In the Unit Number field, enter the unit number. 6. In the Nbr field, enter the SBL number. 7. In the SubNbr field, enter the SBL sub number. 8. In the WTC (Wait Traffic Clear) field, enter the number of minutes that the SBL is to wait for traffic to clear. 9. Click on <OK> to verify the SBL. If the test indicates that the SBL is serviceable, it is initialized. If the initialization is successful, the SBL is set to the IT state. If the test indicates that the SBL is faulty, it is set to the FLT state. Refer to Table 3 for more information on SBL states.
58 / 136
4 SBL Management
4.4
Restarting SBLs
The SBL Restart command allows you to restart a processor SBL. An SBL can be restarted only if its status is IT. Refer to Table 3 for more information on SBL states. The restart of an SBL can be refused if any actions are in progress on:
" "
The SBL itself An SBL at a higher hierarchical level.
The action in progress can have been initiated automatically as a result of the error analysis function, or as a result of an operator request. Refer to the Operations & Maintenance Reference Guide for more information on SBL hierarchies.
Procedure
To restart an SBL: 1. From the BSC Terminal menu bar, follow the menu path: Commands > Equipment Handling > SBL Restart The SBL Restart window is displayed, as shown in Figure 32.
Figure 32
SBL Restart Window
2. In the Object Class field, select SBL. 3. In the Unit Type field, select the appropriate unit type, BSC, BTS or TSC. 4. In the SBL Type field, select the appropriate SBL type. Refer to Table 2 for more information on SBL types. 5. In the Unit Number field, enter the unit number. 6. In the Nbr field, enter the SBL number. 7. In the SubNbr field, enter the SBL sub number. 8. Click on <OK> to restart the SBL.
59 / 136
4 SBL Management
4.5
Initializing SBLs
The SBL Initialize command allows you to initialize an SBL by setting the SBL to the IT state. Refer to Table 3 for more information on SBL states. Do NOT initialize the DISC SBL in a duplex BSC if a file transfer between the SSDs is in progress. Refer to Section 3.3.
NOTICE
You can execute the SBL initialize command only if the higher level SBLs are in the IT state. To initialize an SBL: 1. From the BSC Terminal menu bar, follow the menu path: Commands > Equipment Handling > SBL Initialize The SBL Initialize window is displayed, as shown in Figure 33.
Figure 33
SBL Initialize Window
2. In the Object Class field, select SBL. 3. In the Unit Type field, select the appropriate unit type, BSC, BSS, BTS or TSC. 4. In the SBL Type field,select the appropriate SBL type. Refer to Table 2 for more information on SBL types. 5. In the Unit Number field, enter the unit number. 6. In the Nbr field, enter the SBL number. 7. In the SubNbr field, enter the SBL sub number. 8. Click on <OK> to initialize the SBL. If the initialization is successful, the SBL is returned to service.
60 / 136
4 SBL Management
4.6
Disabling SBLs
The SBL Disable command allows you to disable an SBL by setting the SBL to the OPR state. Refer to Table 3 for more information on SBL states. Disabling network element SBLs (SWITCH and LINK) can result in the loss of calls and the loss of semi permanent connections for at least 30 seconds. Semi permanent connections can be used for connection with the OMC R and for the Q1 interface. Reports sent to the OMC R can be lost. Disable and replace faulty network ele ments as soon as possible. Disabling the BSC SBL results in the loss of all calls and loss of all ongoing actions such as confirmation to the terminal.
NOTICE
You cannot disable an SBL if an action is already in progress on the SBL itself, or on a higher or lower SBL. To disable an SBL: 1. From the BSC Terminal menu bar, follow the menu path: Commands > Equipment Handling > SBL Disable The SBL Disable window is displayed, as shown in Figure 34.
Figure 34
SBL Disable Window
2. In the Object Class field, select SBL. 3. In the WTC (Wait Traffic Clear) field, enter the number of minutes that the SBL is to wait for traffic to clear. 4. Click on <OK> to disable the SBL. The SBL is set to the OPR state.
61 / 136
4 SBL Management
4.7
Reading SBL Status

To read the status of an SBL: 1. From the BSC Terminal menu bar, follow the menu path: Commands > Equipment Handling > SBL Read Status The SBL Read Status window is displayed, as shown in Figure 35.
Figure 35
SBL Read Status Window
2. In the Object Class field, select SBL. 3. In the Unit Type field, select the appropriate unit type, BSC, BSS, BTS or TSC. 4. In the SBL Type field,select the appropriate SBL type. Refer to Table 2 for more information on SBL types. 5. In the Unit Number field, enter the unit number. 6. In the Nbr field, enter the SBL number. 7. In the SubNbr field, enter the SBL sub number. 8. Click on <OK> to read the SBL status.
62 / 136
4 SBL Management
4.8
Reading SBL State Lists

The SBL State List command allows you to read the status of the SBLs in a unit that is not in the IT, SOS, or NEQ state. Refer to Table 3 for more information on SBL states. To read the status of the SBLs in a unit: 1. From the BSC Terminal menu bar, follow the menu path: Commands > Equipment Handling > SBL State List The SBL State List window is displayed, as shown in Figure 36.
Figure 36
SBL State List Window
2. In the Object Class field, select SBL. 3. In Unit Type field,select the appropriate unit type, BSC, BTS or TSC. 4. In the Unit Number field, enter the unit number. 5. Click on <OK> to initiate generation of an SBL State List.
63 / 136
4 SBL Management
4.9
Testing SBLs
Before a test can be performed, the SBL must be in one of the out of service states (FOS, OPR or SOS). To test an SBL: 1. From the BSC Terminal menu bar, follow the menu path: Commands > Test Handling > SBL Test The SBL Test window is displayed, as shown in Figure 37.
Figure 37
SBL Test Window
2. In the Object Class field, select SBL. 3. In Unit Type field,select the appropriate unit type, BSC, BTS or TSC. 4. In SBL Type field, select the appropriate SBL type. Refer to Table 2 for more information on SBL types. 5. In the Unit Number field, enter the unit number. 6. In the Nbr field, enter the SBL number. 7. In the SubNbr field, enter the SBL sub number. 8. Click on <OK> to initiate the SBL test.
64 / 136
5 Alarm Management
5 Alarm Management
This chapter tells you how to manage alarms, and contains procedures for: G G Displaying lists of current alarms Enabling or disabling the display of unsolicited alarm reports.
65 / 136
5 Alarm Management
5.1
Displaying Alarm Lists

To display a list of current alarms: 1. From the BSC Terminal menu bar, follow the menu path: Commands > Alarm Handling > Display Alarm List The Display Alarm List window is displayed, as shown in Figure 38.
Figure 38
Display Alarm List Window
2. In the Object Class field, select the appropriate object class. 3. In the Unit Type field, select the appropriate unit type. 4. In the SBL Type field, select the appropriate SBL type. 5. In the Unit Number field, enter the unit number. 6. In the Nbr field, enter the SBL number. 7. In the SubNbr field, enter the SBL sub number. 8. Click on <OK> to generate the alarm list.
66 / 136
5 Alarm Management
5.2
Enabling PC Reporting
The Enable PC Reporting command allows you to enable or disable the display of unsolicited alarm reports.
Unsolicited Alarm Routing Rules
The following rules apply for routing unsolicited alarms:

"
The link connected to the first SYS CPRC (G2 BSC) or S CPRA (G1 BSC) has the highest priority. If no links are connected to the first SYS CPRC or S CPRA, the link connected to the second SYS CPRC or S CPRA has the highest priority. The SYS CPRC or S CPRA priority is independent of whether the SYS CPRC or S CPRA is in active or standby mode. If two links are connected to the same SYS CPRC or S CPRA, the RS 232 link has the higher priority.
"
"
"
Procedure
To enable or disable PC reporting: 1. From the BSC Terminal menu bar, follow the menu path: Commands > Alarm Handling > Enable PC Reporting The Enable PC Reporting window is displayed, as shown in Figure 39.
Figure 39
Enable PC Reporting Window
2. In the Object Class field, select the SBL. 3. In the Unit Type field, select BSC. 4. In the SBL Type field, select BSC. 5. In the Unit Number field, enter the unit number. 6. In the Nbr field, enter the SBL number. 7. In the SubNbr field, enter the SBL sub number.
67 / 136
5 Alarm Management
8. In the Internal Reporting field, select Enable or Disable to display unsolicited internal alarm reports. 9. In the External Reporting field, select Enable or Disable to display unsolicited external alarm reports. 10. Click on <OK> to enable or disable PC reporting. The status of internal and external reporting is displayed at the right end of the status bar. If enabled, unsolicited alarm reports are received as they are generated.
68 / 136
6 BSC Extension and Reduction

This chapter tells you how to manage extension and reduction of the BSC, and contains procedures for: G G G G G G G G G G G G G G G G G Extending the BSC configuration Downloading the BSC extension software Resetting the BSC extension Reducing the BSC configuration Modifying the BSC configuration Disabling switch ports for extension Initializing switch ports after reduction Adding an N7 signaling link Testing the Broadcast Bus Testing cables and switch PBAs Testing clock cables and PBAs Testing DC/DC convertors Testing termination plugs Complete G2 testing Stop loop testing Stop testing Going operational.
69 / 136
6.1
Extending BSC Configuration

To extend the BSC configuration database with a new set of SBLs.: 1. From the BSC Terminal menu bar, follow the menu path: Commands > Extension & Reduction > BSC Extend Config The BSC Extend Config window is displayed, as shown in Figure 40.
Figure 40
BSC Extend Config Window
2. In the Object Class field, select BSC. 3. In the Unit Type field, select BSC. 4. In the Unit Number field, enter the appropriate unit number. 5. In the New Config field, enter the required number for the new configuration. 6. In the BSI Link Type field, select the appropriate BSI link type. 7. Click on <OK> to extend the BSC configuration database.
70 / 136
6.2
Downloading BSC Extension Software

To download the BSC operational software to the added processors after extension: 1. From the BSC Terminal menu bar, follow the menu path: Commands > Extension & Reduction > BSC Download Extension SW The BSC Download Extension SW window is displayed, as shown in Figure 41.
Figure 41
BSC Download Extension SW Window
2. In the Object Class field, select BSC. 3. In the Unit Type field, select BSC. 4. In the Unit Number field, select the appropriate unit number. 5. Click on <OK> to download the BSC operational software.
71 / 136
6.3
Resetting BSC Extension

To reset the BSC processors and initiate self testing after extension: 1. From the BSC Terminal menu bar, follow the menu path: Commands > Extension & Reduction > BSC Extension Reset The BSC Extension Reset window is displayed, as shown in Figure 42.
Figure 42
BSC Extension Reset Window
2. In the Object Class field, select BSC. 3. In the Unit Type field, select BSC. 4. In the Unit Number field, select the appropriate unit number. 5. Click on <OK> to reset the BSC processors.
72 / 136
6.4
Reducing BSC Configuration

To initiate the BSC reduction process: 1. From the BSC Terminal menu bar, follow the menu path: Commands > Extension & Reduction > BSC Reduce Config The BSC Reduce Config window is displayed, as shown in Figure 43.
Figure 43
BSC Reduce Config Window
2. In the Object Class field, select BSC. 3. In the Unit Type field, select BSC. 4. In the Unit Number field, select the appropriate unit number. 5. In the New Config field, select the appropriate configuration number for the BSC reduction. 6. In the Wait Period field, select the appropriate wait period. 7. Click on <OK> to initiate the BSC reduction.
73 / 136
6.5
Modifying BSC Configuration

To modify the BSC configuration: 1. From the BSC Terminal menu bar, follow the menu path: Commands > Extension & Reduction > BSC Config Modify The BSC Config Modify window is displayed, as shown in Figure 44.
Figure 44
BSC Config Modify Window
2. In the Object Class field, select BSC. 3. In the Unit Type field, select BSC. 4. In the Unit Number field, select the appropriate unit number. 5. In the New Config field, select the appropriate configuration number for the BSC extension. 6. In the BSI Link Type field, select the appropriate BSI link type. 7. In the Wait Period field, select the appropriate wait period. 8. Click on <OK> to modify the BSC configuration.
74 / 136
6.6
Disabling Switch For Extension

The Disable Switch For Extension command allows you to isolate switch ports when you want to extend from G2 BSC rack 1 to G2 BSC racks 2 and 3. To disable the switch ports for extension: 1. From the BSC Terminal menu bar, follow the menu path: Commands > Extension & Reduction > Disable Switch For Extension The Disable Switch For Extension window is displayed, as shown in Figure 45.
Figure 45
Disable Switch For Extension Window
2. In the Object Class field, select BSC. 3. In the Unit Type field, select BSC. 4. In the Unit Number field, select the appropriate unit number. 5. In the New Config field, select the appropriate configuration number for the BSC extension. 6. Click on <OK> to disable the switch ports.
75 / 136
6.7
Initializing Switch After Reduction

To initialize the switch ports after a reduction is established: 1. From the BSC Terminal menu bar, follow the menu path: Commands > Extension & Reduction > Init Switch After Reduction The Init Switch After Reduction window is displayed, as shown in Figure 46.
Figure 46
Init Switch After Reduction Window
2. In the Object Class field, select BSC. 3. In the Unit Type field, select BSC. 4. In the Unit Number field, select the appropriate unit number. 5. In the New Config field, select the appropriate configuration number for the BSC reduction. 6. Click on <OK> to initialize the switch ports.
76 / 136
6.8
Adding N7 Link
The Add N7 command allows you to assign several N7 signaling links to requested Digital Trunk Controller/Ater trunks. To add an N7 Digital Trunk Controller signaling link: 1. From the BSC Terminal menu bar, follow the menu path: Commands > Extension & Reduction > Add N7 The Add N7 window is displayed, as shown in Figure 47.
Figure 47
Add N7 Window
2. In the Object Class field, select BSC. 3. In the Unit Type field, select BSC. 4. In the 16 DTC SBL Number fields to select the appropriate N7 link mappings. The DTC number is equal to the Ater trunk number. 5. Click on <OK> to add the N7 signaling link.
77 / 136
6.9
Broadcast Bus Testing

To test the broadcast bus: 1. From the BSC Terminal menu bar, follow the menu path: Commands > Extension & Reduction > Broadcast Test The Broadcast Test window is displayed, as shown in Figure 48.
Figure 48
Broadcast Test Window
2. In the Test field, select BROADCAST TEST. 3. In the All CEs field, select YES to test with all the Control Elements (CEs), otherwise NO. 4. In the Loop field, select YES to run the test continuously, otherwise NO. 5. Click on <OK> to test the broadcast bus.
78 / 136
6.10
Cable Testing
To test added cables and switch PBAs: 1. From the BSC Terminal menu bar, follow the menu path: Commands > Extension & Reduction > Network Test The Network Test window is displayed, as shown in Figure 49.
Figure 49
Network Test Window
2. In the Test field:

D D
to test all the connections, select GLOBAL NETWORK (go to Step 8.) to test a specific set, select SPECIFIC NETWORK (go to step 3.)
3. In the Source field, select the network address of the appropriate source CE. 4. In the Destination field, select the network address of the appropriate destination CE. 5. In the Tunnel field, select TUNNEL A or TUNNEL B, as required. 6. In the Port field, select PORT P or PORT P+4, as required. 7. In the Loop field, select YES to run the test continuously, otherwise NO. 8. Click on <OK> to test the added cables and switch PBAs.
79 / 136
6.11
Clock Testing
To test the added clock cables and PBAs: 1. From the BSC Terminal menu bar, follow the menu path: Commands > Extension & Reduction > Clock Test The Clock Test window is displayed, as shown in Figure 50.
Figure 50
Clock Test Window
2. In the Test field, select the appropriate test. 3. In the Transmission field, select YES to test the transmission equipment, otherwise NO. 4. In the External Ref field, select YES to check the external reference input, otherwise NO. 5. In the Loop field, select YES to run the test continuously, otherwise NO. 6. Click on <OK> to test the added clock cables and PBAs.
80 / 136
6.12
DC/DC Convertor Testing

To test the DC/DC convertors: 1. From the BSC Terminal menu bar, follow the menu path: Commands > Extension & Reduction > DC/DC Convertor Test The DC/DC Convertor Test window is displayed, as shown in Figure 51.
Figure 51
DC/DC Convertor Test Window
2. In the Test field, select START DC/DC TEST or STOP DC/DC TEST, as required, to start or stop the DC/DC convertor test. 3. Click on <OK> to start/stop the DC/DC convertor test.
81 / 136
6.13
Termination Plug Testing

To test all termination plugs: 1. From the BSC Terminal menu bar, follow the menu path: Commands > Extension & Reduction > Plug Check The Plug Check window is displayed, as shown in Figure 52.
Figure 52
Plug Test Window
2. In the Test field:

D D
to test all the plugs, select GLOBAL PLUG TEST to test a specific plug, select SPECIFIC PLUG TEST.
3. In the Ground Plugs field, select YES to test with ground plugs present, otherwise NO. 4. In the Transmission field, select YES to test the transmission equipment, otherwise NO. 5. If the SPECIFIC PLUG TEST option was selected in Step 2,in the CE Network Address field, select the network address of the CE to be checked. 6. In the Loop field, select YES to run the test continuously, otherwise NO. 7. Click on <OK> to test the termination plugs.
82 / 136
6.14
Complete G2 Testing
To perform a complete G2 test of the BSC: 1. From the BSC Terminal menu bar, follow the menu path: Commands > Extension & Reduction > Complete G2 Test The Complete G2 Test window is displayed, as shown in Figure 53.
Figure 53
Complete G2 Test Window
2. In the Transmission field, select YES, to test the transmission equipment, otherwise NO. 3. In the Loop field, select YES to run the test continuously, otherwise NO. 4. In the Ground Plugs field, select YES to test with ground plugs present, otherwise NO. 5. Click on <OK> to perform the complete G2 test.
83 / 136
6.15
Stop Loop Testing

To stop ongoing loop testing: 1. From the BSC Terminal menu bar, follow the menu path: Commands > Extension & Reduction > Stop Loop The Stop Loop window is displayed, as shown in Figure 54.
Figure 54
Stop Loop Window
2. Click on <OK> to stop ongoing loop testing.
84 / 136
6.16
Stop Testing
To stop ongoing testing: 1. From the BSC Terminal menu bar, follow the menu path: Commands > Extension & Reduction > Stop Test The Stop Test window is displayed, as shown in Figure 55.
Figure 55
Stop Test Window
2. Click on <OK> to stop ongoing testing.
85 / 136
6.17
Going Operational
To change the BSC from test mode to operational mode: 1. From the BSC Terminal menu bar, follow the menu path: Commands > Extension & Reduction > Go For Operation The Go For Operation window is displayed, as shown in Figure 56.
Figure 56
Go For Operation Window
2. In the Object Class field, select BSC. 3. In the Unit Type field, select BSC. 4. In the Unit Number field, select the appropriate unit number. 5. Click on <OK> to change the BSC from test mode to operational mode.
86 / 136
7 Trace Management
7 Trace Management
This chapter tells you how to manage traces, and contains procedures for: G G G G G Starting traces Stopping traces Listing the trace jobs currently running in the BSC Reading trace files from the BSC Deleting trace files from the BSC.
87 / 136
7 Trace Management
7.1
Starting Traces
To start a trace on a radio channel: 1. From the BSC Terminal menu bar, follow the menu path: Commands > Trace Invocation > Trace Start The Trace Start window is displayed, as shown in Figure 57.
Figure 57
Trace Start Window
2. In the Object Class field, select TRACE. 3. In the Unit Type field, select BSC. 4. In the Trace Originator field, select the appropriate trace originator. 5. In the Unit Number field, enter the unit number. 6. In the Trace Number field, enter the trace number. The number must not have been used previously when starting traces. 7. In the MSC Transaction Number field, select H'FFFF .
88 / 136
7 Trace Management
8. In the Radio Channel ID fields, select the following:

D D D D D D D
Channel Type Unit Type Unit Number SBL Type Nbr - SBL number SubNbr - SBL sub number Subchannel.
9. In the Flag To MSC field, select TRUE to notify the MSC that the trace job is starting, otherwise FALSE. 10. In the Trace Wait Timer field, enter the required number of minutes. If no calls are made on the radio channel during this time period, the trace job is aborted. 11. In the Trace Immediate Flag field:
D D
to trace the current call, select TRUE to trace the next call, select FALSE.
12. Click on <OK> to start the trace. If the channel configuration is incorrect or the BSC trace number is already in use, a TRACE_FAILURE report is received.
89 / 136
7 Trace Management
7.2
Stopping Traces
To stop a trace on a radio channel: 1. From the BSC Terminal menu bar, follow the menu path: Commands > Trace Invocation > Trace Stop The Trace Stop window is displayed, as shown in Figure 58.
Figure 58
Trace Stop Window
2. In the Object Class field, select TRACE. 3. In the Unit Type field, select BSC. 4. In the Trace Originator field, select the appropriate trace originator. 5. In the Unit Number field, enter the unit number. 6. In the Trace Number field, enter the trace number. 7. Click on <OK> to stop the trace.
90 / 136
7 Trace Management
7.3
Listing Trace Jobs

To obtain a list of trace jobs currently running in the BSC: 1. From the BSC Terminal menu bar, follow the menu path: Commands > Trace Invocation > Trace Job List The Trace Job List window is displayed, as shown in Figure 59.
Figure 59
Trace Job List Window
2. In the Object Class field, select TRACE. 3. In the Unit Type field, select BSC. 4. In the Trace Originator field, select the appropriate trace originator. 5. In the Unit Number field, enter the unit number. 6. In the Trace Number field, select the required trace. 7. In the MSC Transaction Number field, select H'FFFF . 8. Click on <OK> to generate the trace job list. For each trace, the following information is provided:
" " "
BSC trace number Status Radio channel identity (optional).
91 / 136
7 Trace Management
7.4
Reading Trace Files from the BSC

To read a trace file from the BSC: 1. From the BSC Terminal menu bar, follow the menu path: Commands > Trace Invocation > Read Trace File The Read Trace File from BSC window is displayed, as shown in Figure 60.
Figure 60
Read Trace File from BSC Window
2. In the Source Disk field, select the appropriate source disk. 3. In each of the File Identity fields, in turn, enter the:
D D D D
4. In the PC File field, enter the full PC pathname of the trace file, or click on <Browse> and navigate to the appropriate directory. 5. Click on <OK> to start reading the trace file.
92 / 136
7 Trace Management
7.5
Deleting Trace Files from the BSC

To delete a trace file from the BSC: 1. From the BSC Terminal menu bar, follow the menu path: Commands > Trace Invocation > Trace File Read Config The Trace File Read Config window is displayed, as shown in Figure 61.
Figure 61
Trace File Read Config Window
2. In the Object Class field, select BSS. 3. In the Unit Type field, select BSS. 4. In the Unit Number field, enter the unit number. 5. In the File Identity field, enter the file identity of the trace file to delete. 6. Click on <OK> to delete the trace file.
93 / 136
7 Trace Management
94 / 136
8 Miscellaneous Terminal Operations

This chapter tells you how to: G G G G G G G G G Initialize the system Perform Minibuild Loading Manage the date and time settings used in the BSC Perform logging of commands and reports Monitor the status of a BTS download Set the BTS download status timers Install new BSS software on an active BSC Install a new DLS on an active BSC Install and start software on a BSC.
95 / 136
8.1
Initializing the System

The System Initialization command allows you to initialize the system. There are three initialization levels:
" "
Restart - for restarting the software Reload - for reloading the software from the SSD and then restarting the software Reboot - for performing a self test, reloading the software from the SSD and then restarting the software.
"
NOTICE
System actions such as reload and reboot result in the loss of all calls and all ongoing actions such as confirmation to the terminal.
Procedure
To initialize the system: 1. From the BSC Terminal menu bar, follow the menu path: Commands > System Activation > System Initialization The System Initialization window is displayed, as shown in Figure 62.
Figure 62
System Initialization Window
2. In the Unit Identity field, select BSC. 3. In the Unit Number field, enter the unit number. 4. In the Init Level field, select the required initialization level. 5. Click on <OK> to initiate the action. After a System Initialization action, a complete audit must be performed at the OMC R.
NOTICE
96 / 136
8.2
Loading Minibuild
The Minibuild Loading utility allow you to start an out of action BSC quickly by loading new software based on a default BSS Masterfile. There are different Master files for G1 and G2 BSCs, and for the different releases. The Minibuild only performs a default build. To perform a Minibuild Load: 1. From the BSC Terminal menu bar, follow the menu path: Utilities > Minibuild Loading The Minibuild Loading window is displayed, as shown in Figure 63.
Figure 63
Minibuild Loading Window
2. Enter the PC directory path of the Masterfile in the Directory Path field, or click on <Browse> and navigate to the appropriate directory. The available Master files are displayed in the Available Files panel. 3. Click on the appropriate Masterfile in the Available Files panel. A list of files to be loaded is displayed in the adjacent panel.
97 / 136
4. Click on <Go!> to start loading the minibuild. A result window is displayed showing that the system is waiting for a new download request. The files are automatically downloaded when a download request is received from the BSC. You can monitor the progress of the download by observing the Light Emitting Diodes (LEDs) on the S CPRA (G1 BSC) or SYS CPRC (G2 BSC) PBA. Refer to the Operations & Maintenance Reference Guide for more information.
TIP
98 / 136
8.3
Displaying the Date and Time

To display the current date and time used in the BSC: 1. From the BSC Terminal menu bar, follow the menu path: Commands > Date & Time > Display Date & Time The Display Date and Time window is displayed, as shown in Figure 64.
Figure 64
Display Date and Time Window
2. In the Object Class field, select BSS. 3. In the Unit Type field, select BSS. 4. In the Unit Number field, enter the unit number. 5. Click on <OK> to send the command to the BSC.
99 / 136
8.4
Modifying the Date and Time

To modify the current date and time used in the BSC: 1. From the BSC Terminal menu bar, follow the menu path: Commands > Date & Time > Modify Date & Time The Modify Date and Time window is displayed, as shown in Figure 65.
Figure 65
Modify Date and Time Window
2. In the Object Class field, select BSS. 3. In the Unit Type field, select BSS. 4. In the Unit Number field, enter the unit number. 5. Click on or next to the appropriate field, and select the required time of day using the following:
D D D D
Hour - for the hour of the day Min - for the minutes past the hour Sec - for the seconds past the minute TSec - for the tenths of seconds past the second.
6. In the month field, select the required calender month. 7. In the year field, select the required calender year. 8. Click on the required day of the month in the month display. 9. Click on <OK> to send the command to the BSC. The message "Command accepted by BSC, waiting for report" is displayed on the status bar.
100 / 136
8.5
Adjusting the Time

To adjust the current time used in the BSC: 1. From the BSC Terminal menu bar, follow the menu path: Commands > Date & Time > Adjust Date & Time The Adjust Time window is displayed, as shown in Figure 66.
Figure 66
Adjust Time Window
2. In the Object Class field, select BSS. 3. In the Unit Type field, select BSS. 4. In the Unit Number field, enter the unit number. 5. In the Direction field, select FORWARD or BACKWARD, as required, for the adjustment. 6. In the Adjust (in seconds) field, enter the number of seconds by which the time is to be adjusted. 7. Click on <OK> to send the command to the BSC.
101 / 136
8.6
Performing Logs of Commands and Reports

To store commands generated at the BSC Terminal and reports generated in a log file: 1. From the BSC Terminal menu bar, follow the menu path: Utilities >Logging A check mark is placed against the Logging function and logging of the commands and reports is initiated. 2. To deactivate the logging function, repeat the procedure described above. Check that the check mark against the Logging function has been removed. Do not have the logging function active all the time because it can adversely affect the performance of the system.
NOTICE
102 / 136
8.7
Monitoring the Status of A BTS Download

During the downloading of software and data to the BTSs, the status of the download can be monitored. To monitor the status of a BTS download: From the BSC Terminal menu bar, follow the menu path: Utilities > BTS Download Status > Reporting Mode CTRL+B The Overview on BTS window is displayed, as shown in Figure 67. This window gives information about the files that have been downloaded to each BTS.
Figure 67
Overview on BTS Window
103 / 136
8.8
Setting the BTS Download Status Timers

There are two timers that control the monitoring of the BTS download:
"
Session Timer, which controls the interval at which the BSC expects to receive an indication from the BSC Terminal that monitoring of the download status is to continue Reporting Interval Timer, which controls the interval at which BTS download status reports are generated.
"
Procedure
To set these timers to the required intervals: 1. From the BSC Terminal menu bar, follow the menu path: Utilities > BTS Download Status > Timer Settings The Timer Settings window is displayed, as shown in Figure 68.
Figure 68
Timer Settings Window
2. If you want to use the default settings, click on <Default>. The default settings are:
D D
Session Timer: 15 minutes Reporting Interval Timer: 5 seconds.
If you do not want to use the default settings, Click on or next to the appropriate field to select the required settings. 3. Click on <OK> to accept the new timer settings.
104 / 136
8.9
Copy BSS Software to Terminal Hard Disk

This section tells you how to copy the BSS software to the hard disk of the BSC Terminal. The BSS software is contained on a number of floppy diskettes. If the build of the backup version is B5.2 and the CMA version is CMATAH75.75G or later, the files on the diskettes are compressed. In this case, ensure that the GZIP DOS tool (freeware) is installed on the hard disk of the terminal. This tool is needed to decompress the files. To copy the files to the hard disk: 1. Copy all the files from the diskettes into a directory on the hard disk of the terminal. If the build backup version is that referred to in the notice above, the files must be decompressed using the GZIP DOS tool. This is done as follows. 2. Open a Command Prompt window. 3. Change the directory to the one into which you copied the files 4. Enter the following command at the DOS prompt: " GZIP -N -d *.* where:
D D
NOTICE
N indicates that the original names and time stamps of the files are to be restored d indicates that the files are to be decompressed.
Check that the BSS files have been decompressed.
105 / 136
8.10
Installing New BSS Software on an Active BSC

This section tells you how to install a new BSS software version in the BSC. The BSC must be in the IT state. You need to install new software when:
" "
New BSS software is released A failure requires you to perform another installation.
ATTENTION
Formatting a normal SSD results in the loss of software and data. Refer to the Operations & Maintenance Reference Guide for more information.
Impact on System
Traffic is interrupted during the file transfer process from the terminal to the BSC, and during the startup phase of the BSC. This takes a minimum of 60 minutes. To install a new BSS software version on an IT BSC: 1. Identify the active S CPRA (G1 BSC) or SYS CPRC (G2 BSC). The active S CPRA or SYS CPRC PBA is the one whose front panel LEDs are as shown in Figure 69.
Front Edge of PBA Retaining Clip LED On
Procedure
Retaining Clip
LED Off LED Fast Flashing LED Fast Flashing
Figure 69
Active S CPRA or SYS CPRC Front Panel LEDs
2. Connect the link cable between the terminal and the active S CPRA or SYS CPRC, as described in Section 1.4. 3. Start the terminal software, as described in Section 1.5. 4. Disable the BSC SBL, as described in Section 4.6, and wait for a message confirming that the BSC is disabled before proceeding to the next step.
106 / 136
5. Format the SSD of the S CPRA1 or SYS CPRC1, as described in Section 3.5. You must select the BSS Masterfile as the file to use when formatting the SSD. 6. Download the BSS software to the SSD of the (formatted) S CPRA1 or SYS CPRC1, as described in Section 3.1. You must use the Specific Files option, and specify the BSS Masterfile as the reference file. Do not use the All BSS Files option because there is a risk that other files in the directory are also transferred.
NOTICE
7. Check that all files are downloaded correctly, as described in Section 3.7. 8. For a duplex BSC only, format the SSD of the standby S CPRA2 or SYS CPRC2, as described in Section 3.6. This ensures that the active and standby SSDs have the same format. 9. For a duplex BSC only, copy all the downloaded BSS files from the SSD (disk A) of S CPRA1 or SYS CPRC1 to the SSD (disk B) of S CPRA2 or SYS CPRC2, as described in Section 3.3. Note the following:
D D D
Disk A is the source disk. Disk B is the destination disk. Check that all files are downloaded correctly, as described in Section 3.7.
10. Initialize the BSC, as described in Section 8.1. 11. Check that all SBLs are initialized and in the IT state, as described in Section 4.7. If an SBL does not enter the IT state, refer to the following documents for more information:
D D D
BSS Alarm Dictionary Operations & Maintenance Reference Guide Maintenance Handbook.
107 / 136
8.11
Installing a New DLS on an Active BSC

This section tells you how to install a new DLS in a BSC. The procedure is normally used when a DLS is updated.
Prerequisites Impact on System
The BSC must be in the IT state, and you must ensure that all performance measurement jobs for the BSC are deleted first. Traffic is interrupted for a minimum of 15 minutes during the file transfer process from the terminal and the startup phase of the BSC. To install a new BSS DLS on an IT BSC: 1. Identify the active S CPRA (G1 BSC) or SYS CPRC (G2 BSC). The active S CPRA or SYS CPRC PBA is the one whose front panel LEDs are as shown in Figure 69. 2. Connect the link cable between the terminal and the active S CPRA or SYS CPRC, as described in Section 1.4. 3. Start the terminal software, as described in Section 1.5. 4. Disable the BSC SBL, as described in Section 4.6, and wait for a message confirming that the BSC is disabled before proceeding to the next step. 5. List information about the current DLS on the SSD, as described in Section 3.7. Write down the details of the current DLS. 6. Delete the DLS from the SSD of S CPRA1 or SYS CPRC1, as described in Section 3.8. 7. Download the new DLS to the SSD of S CPRA1 or SYS CPRC1, as described in Section 3.1. You must use the All BSS Files option and specify the DLS as the reference file. 8. Check that all files are downloaded correctly, as described in Section 3.7. 9. Delete the old DLS from the SSD of the (standby) S CPRA2 or SYS CPRC2, as described in Section 3.8. 10. Copy the downloaded DLS file from the SSD (disk A) of S CPRA1 or SYS CPRC1 to the SSD (disk B) of the (standby) S CPRA2 or SYS CPRC2, as described in Section 3.3. Note the following:
D D
Procedure
Disk A is the source disk. Disk B is the destination disk.
108 / 136
Check that all files are downloaded correctly, as described in Section 3.7.
11. Initialize the BSC, as described in Section 8.1. 12. Check that all SBLs are initialized and in the IT state, as described in Section 4.7. If an SBL does not enter the IT state, refer to the following documentation for more information:
D D D
109 / 136
8.12
Installing and Starting Software on a BSC

This section tells you how to install the current or a new BSS software version on a BSC in the following circumstances:
" "
At installation time When a fatal error has occurred at the BSC, the S CPRA (G1 BSC) or the SYS CPRC (G2 BSC) is no longer active, and a Minibuild is required.
ATTENTION
Formatting a normal SSD can result in the loss of software and data. Refer to the Operations & Maintenance Reference Guide for more information. If an S CPRA or SYS CPRC fails during a communication session, the session is aborted.
Restrictions Impact on System Procedure
You can only use the X.25 link option for the terminal after the Minibuild is loaded onto the S CPRA or SYS CPRC. This is because the Minibuild contains the packet handler for the X.25 link. During the installation process, the BSC is not available. All traffic handled by the BSC and its associated BTSs is interrupted. To install a new BSS software version on a BSC: 1. Connect the RS 232 asynchronous link cable between the terminal and the S CPRA1 or SYS CPRC1, as described in Section 1.4. 2. Start the terminal software, as described in Section 1.5. 3. Perform a Minibuild on the BSC, as described in Section 8.2. A complete Minibuild takes approximately 12 minutes. If a Successful Download Operation message is displayed, go to Step 6. If not, continue to the next step. 4. Remove S CPRA1 or SYS CPRC1 from its subrack, wait at least 30 seconds, and then replace it. Refer to the Maintenance Handbook for more information on removing the S CPRA or SYS CPRC. When replaced, the S CPRA1 or SYS CPRC1 performs a self test that lasts approximately 7 minutes. 5. Repeat Steps 1 to 3.
110 / 136
6. Format the SSD of the S CPRA1 or SYS CPRC1, as described in Section 3.5, using the BSS Masterfile. 7. Download the BSS software to the SSD of the (formatted) S CPRA1 or SYS CPRC1, as described in Section 3.1, using the BSS Masterfile. Do not use the All BSS Files option because there is a risk that other files in the directory are also transferred.
NOTICE
8. Check that all files are downloaded correctly, as described in Section 3.7. 9. Initialize the BSC, as described in Section 8.1. Set the Initialization Level field to REBOOT. If you are installing the software on a simplex BSC only, go to Step 13. For a duplex BSC, continue to the next step. 10. Wait for approximately three minutes until S CPRA2 or SYS CPRC2 becomes IT. 11. Format the SSD of the (standby) S CPRA2 or SYS CPRC2, as described in Section 3.6. This ensures that the active and the standby SSDs have the same format. 12. Copy all the downloaded BSS files from the SSD (disk A) of S CPRA1 or SYS CPRC1 to the SSD (disk B) of the (standby) S CPRA2 or SYS CPRC2, as described in Section 3.3. Note the following:
D D D
Disk A is the source disk. Disk B is the destination disk. Check that all files are downloaded correctly, as described in Section 3.7.
13. Check that all SBLs are initialized and in the IT state, as described in Section 4.7. If an SBL does not enter the IT state, refer to the following documents for more information:
D D D
111 / 136
112 / 136
9 Test Command Results

This chapter describes how to decode test results. The topics include: G G G G Test report format CPR/DTC/TCU test results Link/Switch test results N7 test results.
113 / 136
9.1
Test Report Format

When a test or verify command is executed in the BSC, the test results are sent as a test report. The format of the test report displayed is shown in Figure 70.
' ' ' '
' ' ' '
' ' ' '
' ' ' '
' ' ' '
Figure 70
Example of Test Report for Switch
Success or failure is reported in the Job Result field of the test report. In the case of tests applied to SBLs CPR, DTC, TCU, Link, Switch and N7, additional Test Result information is provided at the bottom of the report. This consists of:
" " "
Segment Flt type Raw Data.
114 / 136
The Test Raw Data information is displayed in hexadecimal (H'00 to H'FF). The following sections show how test results are decoded for CPR/DTC/TCU, Link/Switch, and N7.
115 / 136
9.2
CPR/DTC/TCU Test Results

The test results for CPR, DTC and TCU have the same format, as shown in Table 4.
Example Test Results

Table 4
Job Result Test Segment Test Fault Type Test Raw Data
Test Results Format for CPR/DTC/TCU

Successful (tests executed) 1 0 H'F8 H'FF H'FF H'FF H'FF H'FF H'FF H'FF (See Table 5, H'FD H'FF H'FF H'FF H'FF H'FF H'FF H'FF H'FF H'FF H'FF H'FF Unsuccessful (tests not executed) 0 0 H'FF H'FF H'FF H'FF H'FF H'FF H'FF H'FF H'FF H'FF H'FF H'FF H'FF H'FF H'FF H'FF H'FF H'FF H'FF H'FF
6, or 7)
A successful job result is accompanied by the Test Segment and Test Fault Type values shown in Table 4. This means that the tests have executed. The results of the individual tests performed is indicated by the first four bytes of the Test Raw Data information. If these bytes have the value H'FF, there are no failures. In the example in Table 4, the first four bytes, Bytes 0 to 3, have the values H'F8, H'FF, H'FD and H'FF, respectively. They are decoded using Table 5, 6, or 7. For a G1 CPR test, the values H'F8, H'FF, H'FD and H'FF mean that the following individual tests failed:
" " " "
RAM DISK EPROM Expected/unexpected interrupt.
An unsuccessful job result means that the tests did not execute. In this case, all the Test Raw Data information is set to the default values of H'FF.
116 / 136
CPR/DTC/TCU Test Raw Data Results
The meaning of the test results depends on the processor type and generation. Tables 5, 6, and 7 show the meaning for G1 and G2 CPRs, DTCs and TCUs, respectively. A bit at 0 means that the associated test failed.
Table 5
Byte 0 Bit 00 01 02 03 04 05 06 07 1 08 09 10 11 12 13 14 15 2 16 17 18 19 20 21 22 23 3 24 25 26
Test Raw Data Results for G1 and G2 CPRs

G1 Meaning Random Access Memory (RAM) test Solid State Disc (DISC) test Erasable Programmable Read Only Memory (EPROM) test Direct Memory Access (DMA) test Sanity Timer test Periodic Timer_1 test Periodic Timer_2 test Programmable Interrupt Controller (PIC) test Not used Not used Not used Control Register test OBCI test Not used Serial Communication Controller (SCC) Channel_A test SCC Channel_B test Not used Expected/Unexpected interrupt Hardware Initialization test Cyclic Redundancy Check (CRC) and Bitflip test Not used Not used Take over register test Not used Not used Not used Not used G2 Meaning Dynamic Random Access Memory (DRAM) test Static Random Access Memory (SRAM) test EPROM test DISC test Sanity Timer test Periodic Timer_0 test Periodic Timer_2 test Program Interval Timer (PIT) test Remote Inventory Register test FLASH test On Board Controller Interface (OBCI) Identity Register test Concurrence test OBCI test Small Computer System Interface (SCSI) test SCC Channel_A test SCC Channel_B test Not used Expected/Unexpected interrupt Hardware Initialization test CRC and Bitflip test Hardware Configuration test Not used Take Over Register test Control Register test Not used DMA test PIC test
117 / 136
Byte
Bit 27 28 29 30 31
G1 Meaning Not used Not used Not used Not used Not used
G2 Meaning Special Device Reset Register (SDRR) test Special Device Reset Command Register (SDRC) test Not used Broadcast Hardware test Reset test
Table 6
Byte 0 Bit 00 01 02 03 04 05 06 07 1 08 09 10 11 12 13 14 15 2 16 17 18 19 20 21 22 23
Test Raw Data Results for G1 and G2 DTCs

G1 Meaning RAM test Not used EPROM test Not used Sanity Timer test Periodic Timer_1 test Periodic Timer_2 test PIC test Interval Timer 0 test Interval Timer 1 test Interval Timer 2 test Control Register test OBCI test Digital Trunk Interface test Integrated Services Digital Network (ISDN) test Not used Clock test Expected/Unexpected interrupt Hardware Initialization test CRC and Bitflip test Combined Digital Trunk Interface Circuit (DTIC)/PIC test Combined DTIC/OBCI test Not used Not used G2 Meaning DRAM test SRAM test EPROM test Not used Sanity Timer test Periodic Timer_0 test Periodic Timer_2 test PIT test Remote Inventory Register test FLASH memory test OBCI Identity Register test Concurrence test OBCI test Not used Interface Line Circuit (ILC) test Trunk Access Circuit (TRAC) test Not used Expected/Unexpected interrupt Hardware Initialization test CRC and Bitflip test Hardware Configuration test Not used Take Over Register test Control Register test
118 / 136
Byte 3
Bit 24 25 26 27 28 29 30 31
G1 Meaning Not used Not used Not used Not used Not used Not used Not used Not used
G2 Meaning Not used Not used PIC test SDRR test SDRC test ATER test Broadcast Hardware test Reset test
Table 7
Byte 0 Bit 00 01 02 03 04 05 06 07 1 08 09 10 11 12 13 14 15 2 16 17 18 19 20 21 22
Test Raw Data Results for G1 and G2 TCUs

G1 Meaning RAM test Not used EPROM test Not used Sanity Timer test Periodic Timer_1 test Periodic Timer_2 test PIC test Not used Not used Not used Control Register test OBCI test Not used ISDN Link Controller test Not used Not used Expected/Unexpected interrupt Hardware Initialization test CRC and Bitflip test Not used Not used Not used G2 Meaning DRAM test SRAM test EPROM test Not used Sanity Timer test Periodic Timer_0 test Periodic Timer_2 test PIT test Remote Inventory Register test FLASH test OBCI Identity Register test Concurrence test OBCI test Not used ILC test Not used Not used Expected/Unexpected interrupt Hardware Initialization test CRC and Bitflip test Hardware Configuration test Not used Take Over Register test
119 / 136
Byte 3
Bit 23 24 25 26 27 28 29 30 31
G1 Meaning Not used Not used Not used Not used Not used Not used Not used Not used Not used
G2 Meaning Control Register test Not used Not used PIC test SDRR test SDRC test ABIS test Broadcast Hardware test Reset test
120 / 136
9.3
Link/Switch Test Results

The test results for Link and Switch have the same format, as shown in Tables 8 and 9. Table 8
Successful Test Results Format for Link/Switch

Successful (no failures) 0 0 H'FF H'FF H'FF H'FF H'FF H'FF H'FF H'FF H'FF H'FF H'FF H'FF H'FF H'FF H'FF H'FF H'FF H'FF H'FF H'FF
A successful job result is accompanied by the Test Segment, Test Fault Type and Test Raw Data values shown in Table 8. This means that the tests executed and there are no failures. An unsuccessful job result can mean that the tests executed but there are failures, or the tests did not execute. Both cases are shown in Table 9. Table 9
Unsuccessful Test Results Format for Link/Switch

Unsuccessful (some failures) 13 (See Table 11) 60 (See Table 12) H'00 H'45 H'00 H'40 H'13 H'10 H'10 H'12 H'10 H'10 H'10 H'10 H'10 H'10 H'10 H'10 H'10 H'10 H'10 H'10 (See Table 13) Unsuccessful (tests not executed) 0 0 H'00 H'45 H'00 H'40 H'FF H'FF H'FF H'FF H'FF H'FF H'FF H'FF H'FF H'FF H'FF H'FF H'FF H'FF H'FF H'FF
If the tests execute and failures are detected, the Test Segment and Test Fault Type values are not both at 0. Tables 11 and 12 show how to decode these values; this indicates the fault type. The meaning of the Test Raw Data bytes (Bytes 1 to 20) are shown in Table 13; this gives more information about the fault. If tests fail or do not execute, Bytes 1 to 4 of the Test Raw Data give the addresses of the link and switch associated with the test.
121 / 136
The decode of the example failure data in Table 9 is shown in Table 10. Table 10
Parameter Test Segment Test Fault Type Test Raw Data Byte 1 Test Raw Data Byte 2 Test Raw Data Byte 3 Test Raw Data Byte Test Raw Data Byte 5 Test Raw Data Byte 6 Test Raw Data Byte 7 Test Raw Data Byte 8
Decode of Example Failure Data for Link/Switch

Value Description 13 60 H'00 H'45 H'00 H'40 H'13 H'10 H'10 H'12 TDM connection between Link H'0045 and Port 0 of Switch H'0040 failed (timeout) Test OK Test OK TDM connection between Link H'0045 and Port 3 of Switch H'0040 failed (bad test packet and End Of Packets (EOPs) received) Test OK Test OK Test OK Test OK Test OK Test OK Test OK Test OK Test OK Test OK Test OK Test OK Switch NA = H'0040 Time Division Multiplex (TDM) bus TDM bus test failed Link Network Address (NA) = H'0045
Test Raw Data Byte 9 Test Raw Data Byte 10 Test Raw Data Byte 11 Test Raw Data Byte 12 Test Raw Data Byte 13 Test Raw Data Byte 14 Test Raw Data Byte 15 Test Raw Data Byte 16 Test Raw Data Byte 17 Test Raw Data Byte 18 Test Raw Data Byte 19 Test Raw Data Byte 20
H'10 H'10 H'10 H'10 H'10 H'10 H'10 H'10 H'10 H'10 H'10 H'10
122 / 136
Link/Switch Test Segment Results
The meaning of the Test Segment error code is shown in Table 11. Table 11
Test Segment 1 2 3 4 5
Test Segment Results for Link/Switch

Test Segment Where Failure Occurred Unmask Channel 0 (CH0), send interrogation and wait for the tunnel reply. Set Maintenance Busy (MB) bit to 0. This may not cause an alarm. Set up a permanent path, via test depth, towards own OBCI. Set MB and Alarm Shutoff (AS) bits to 1 and check them. Set up a temporary path towards the permanent path, via maintenance selects. The permanent path should be released. An alarm is not generated. Set MB and AS bits to 0 and check them. Set MB bit to 1 and AS bit to 0, and check them. Try to set up a path via normal selects. This should be rejected. Set MB and AS bits to 0 and check them. Set up temporary path (with interrogations included), via test depth, towards own OBCI. Check the contents of the received packet. Tunnel test. Check all depths of the tunnel, via a temporory path, with interrogations. TDM bus test using interrogation. TDM bus test using test packets. Set up permanent path via test depth, towards own OBCI, with test pattern attached. Try to set up a temporary path towards the permanent path. This should be rejected. Try to set up a temporary path towards the permanent path, using maintenance selects. The AS bit is 0, so an alarm should be generated.
6 7 8 9 10
11 12 13 14 15 16
123 / 136
Link/Switch Test Fault Type Results
The meaning of the Test Fault Type is shown in Table 12. Table 12
0 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31
Test Fault Type Results for Link/Switch

Description No errors Tunnel word interrogate not accepted Timeout of tunnel word interrogate Tunnel word command not accepted Tunnel alarm received Message out of sequence No channel available Tunnel word interrogate not accepted All channels NACKed, maintenance packet not sent Timeout for Message (MSG) 158 Wrong Program Terminator Record (PTR) received Timeout for MSG 157 Tunnel word command not accepted Tunnel word interrogate not accepted Wrong PTR received Timeout for MSG 157 No channel available Timeout - no event MSG received Timeout for MSG second path Timeout for MSG first path Tunnel word command not accepted Tunnel word interrogate not accepted Wrong PTR received Timeout for MSG 157 No NACK, but two EOPs received Timeout - no NACK received Tunnel word command not accepted Tunnel word interrogate not accepted Wrong PTR received Timeout for MSG 157 Wrong PTR decremented after EOP Wrong PTR decremented before EOP
Test Fault Type
124 / 136
Test Fault Type 32 33 34 35 36 37 38 39 40 41 42 43 44 45 46 47 48 49 50 51
Description Timeout for MSG 158 Wrong packet received before EOP Wrong packet received after EOP Timeout for MSG 158 All channels NACKed - maintenance packet not sent Wrong packet received after EOP Wrong packet received before EOP Timeout for MSG 158 Timeout for MSG 158 Timeout for all MSGs Timeout for MSG 151 and MSG second path Timeout for MSG 151 and MSG first path Timeout for MSG 151 Timeout for MSG first path and second Timeout for MSG second path Timeout for MSG first path Timeout wrong sequence message Values incompatible with Z_TUNNEL_TYPE, Z_TEST_PORT.B_SIDE and Z_TEST_PORT.B_DEPTH Wrong sequence message Result of Maintenance Interrogate: All Channels Idle (ACI) = 0 MB = 0 AS = 0
52 53 54 55 56 57 58 59 60 61 62 63
ACI = 0 MB = 0 AS = 1 ACI = 0 MB = 1 AS = 0 ACI = 0 MB = 1 AS = 1 ACI = 1 MB = 0 AS = 0 ACI = 1 MB = 0 AS = 1 ACI = 1 MB = 1 AS = 0 ACI = 1 MB = 1 AS = 1 TDM bus test failed when seizing resource TDM bus test failed Overall timer has expired Overall timer has expired Cable test failed when seizing resource
125 / 136
Test Fault Type 64 65 66 67 68 69 70 71 72 73 74 75 76 77 78
Description Wrong PTR decremented after EOP Wrong PTR decremented before EOP Timeout for MSG 158 Plug test error DCDC state change Send tunnel word not accepted Timeout for MSG 157 Processor does not control BSC Clock Type A (BCLA) BCLA: wrong ID BCLA: this is not the rack BCLA BCLA: this is not the system BCLA BCLA: the write register failed BCU pattern test failed BCU fail bit set No system test allowed according R_...
Link/Switch Test Raw Data Results
The meaning of the Test Raw Data results is shown in Tables 13 and 14. Table 13
Test Raw Data Bytes 1 and 2 Bytes 3 and 4 Byte 5 * Byte 6 * Byte 7 * Byte 8 * Byte 9 * Byte 10 * Byte 11*
Test Raw Data Results for Link/Switch

Description Link NA Switch NA TDM connection between Port 0 and Link NA. See also Table 14. TDM connection between Port 1 and Link NA. See also Table 14. TDM connection between Port 2 and Link NA. See also Table 14. TDM connection between Port 3 and Link NA. See also Table 14. TDM connection between Port 4 and Link NA. See also Table 14. TDM connection between Port 5 and Link NA. See also Table 14. TDM connection between Port 6 and Link NA. See also Table 14.
126 / 136
Test Raw Data Byte 12 * Byte 13 * Byte 14 * Byte 15 * Byte 16 * Byte 17 * Byte 18 * Byte 19 * Byte 20 *
Description TDM connection between Port 7 and Link NA. See also Table 14. TDM connection between Port 8 and Link NA. See also Table 14. TDM connection between Port 9 and Link NA. See also Table 14. TDM connection between Port A and Link NA. See also Table 14. TDM connection between Port B and Link NA. See also Table 14. TDM connection between Port C and Link NA. See also Table 14. TDM connection between Port D and Link NA. See also Table 14. TDM connection between Port E and Link NA. See also Table 14. TDM connection between Port F and Link NA. See also Table 14.
* Test Raw Data Bytes 5 to 20 are only relevant for Test Segment Results 12 and 13 (failed TDM bus tests; see Table 11). The tests try to set up paths from the tested link (Link NA) to all the ports of the switch (Switch NA). Connections towards not equipped or OBCI ports are not attempted. Table 14
Nibble High Low 0 1 0 1 2 3
Link/Switch Nibble Description

Test Result Description Connection not tested Connection tested Test OK Bad test packet and no EOPs received Bad test packet and EOPs received Timeout
127 / 136
9.4
N7 Test Results
The test results for N7 have the format shown in Table 15.

Table 15
Test Results Format for N7

Successful (tests executed) 1 0 H'12 H'01 H'00 H'00 H'40 H'00 H'00 H'00 H'00 H'00 H'00 H'FF H'FF H'FF (See Table 17) H'FF H'FF H'FF H'FF H'FF H'FF Unsuccessful (tests not executed) 0 0 H'00 H'00 H'00 H'00 H'00 H'00 H'00 H'00 H'00 H'00 H'00 H'00 H'00 H'00 H'00 H'00 H'00 H'00 H'00 H'00
A successful job result is accompanied by the Test Segment and Test Fault Type values shown in Table 15. This means that the tests executed. The results of the individual tests performed is indicated by the Test Raw Data information. If all these bytes have the value H'FF, there are no failures. In the example in Table 15, some bytes do not have the value H'FF. This information is decoded using Table 17. The decode of the example Test Raw Data information in Table 15 is shown in Table 16. An unsuccessful job result means that the tests did not execute. In this case, all the Test Raw Data information is set to the default value of H'00. Table 16
Parameter Test Raw Data Byte 0 Test Raw Data Byte 1 Test Raw Data Byte 2 Test Raw Data Byte 3 Test Raw Data Byte 4 Test Raw Data Byte 5
Decode of Example Test Raw Data for N7

Value H'12 H'01 H'00 H'00 H'40 H'00 Description 18 messages sent 1 message is faulty Messages 1 and 2 are OK Messages 3 and 4 are OK Message 5 failed (wrong length), 6 is OK Messages 7 and 8 are OK
128 / 136
Parameter Test Raw Data Byte 6 Test Raw Data Byte 7 Test Raw Data Byte 8 Test Raw Data Byte 9 Test Raw Data Byte 10
Value H'00 H'00 H'00 H'00 H'00
Description Messages 9 and 10 are OK Messages 11 and 12 are OK Messages 13 and 14 are OK Messages 15 and 16 are OK Messages 17 and 18 are OK
N7 Test Raw Data Results
The meaning of the Test Raw Data results is shown in Table 17. Table 17
Test Raw Data Byte 0 Byte 1 Byte 2 Byte 3 Byte 4 :
Test Raw Data Results for N7

Description Total number of messages sent Total number of faulty messages High nibble = message 1, low nibble = message 2. See Table 18. High nibble = message 3, low nibble = message 4. See Table 18. High nibble = message 5, low nibble = message 6. See Table 18. : Continued for the number of messages indicated by Byte 0 :
In Table 18, a bit with the value 1 indicates a failure, and a 0 indicates a pass. Table 18
Bit 0 1 2 3
N7 Nibble Description
Description Diagnostic test results not received Error in ILC occurred Wrong message length Wrong number of bytes in message
129 / 136
130 / 136
Abbreviations
Abbreviations
ACI AS BCLA BSC BSS BTS CE CH0 CRC DISC DMA DRAM DTIC EF EOP EPROM FIT FLT FOS G1 G2 HW1 HW2 ILC ISDN IT LED MB MKI MKII MSA All Channels Idle Alarm Shutoff BSC Clock Type A Base Station Controller Base Station Subsystem Base Transceiver Station Control Element Channel 0 Cyclic Redundancy Check Solid State Disc Direct Memory Access Dynamic Random Access Memory Digital Trunk Interface Circuit External Fault End Of Packet Erasable Programmable Read Only Memory Faulty In Traffic Faulty Faulty Out of Service Generation One Generation Two Hardware One Hardware Two Interface Line Circuit Integrated Services Digital Network In Traffic Light Emitting Diode Maintenance Busy Mark One Mark Two Maintenance Seized Automatically
131 / 136
Abbreviations
MSD MSG NA NEQ O&M OBCI OPR PC PIC PIT PTR RAM SBL SCC SCSI SDRC SDRR SOS SRAM SYS CPRC S CPRA TDM TRAC WTC
Maintenance Seized Message Network Address Not Equipped Operations & Maintenance On Board Controller Interface Operator Out of Service Personal Computer Programmable Interrupt Controller Program Interval Timer Program Terminator Record Random Access Memory Security Block Serial Communication Controller Small Computer System Interface Special Device Reset Command Register Special Device Reset Register Software Out of Service Static Random Access Memory System CPRC System CPRA Time Division Multiplex Trunk Access Circuit Wait Traffic Clear
132 / 136
Index
Index A
Adjusting time, 101 Alarms displaying lists, 66 management, 65 routing rules, 67
C
Commands Add N7, 77 Adjust Time, 101 Broadcast Test, 78 BSC Config Modify, 74 BSC Download Extension SW, 71 BSC Extend Config, 70 BSC Extension Reset, 72 BSC Reduce Config, 73 Clock Test, 80 Complete G2 Test, 83 Control SSD, 50 DC/DC Converter Test, 81 Delete File, 51 Disable Switch For Extension, 75 Display Alarm List, 66 Display Date & Time, 99 DLS Backup, 47 Enable PC Reporting, 67 File Transfer from BSC to BSC, 45 Format Duplex SSD, 49 Format SSD, 48 Go For Operation, 86 Init Switch After Reduction, 76 logging, 102 Modify Date & Time, 100 Network Test, 79 Plug Check, 82 Read Trace File From BSC, 92 SBL Disable, 61 SBL Initialize, 60 SBL Read Status, 62 SBL Reset, 56 SBL Restart, 59 SBL State List, 63 SBL Test, 64 SBL Verify, 57 Stop Loop, 84 System Initialization, 96 Trace File Read Config, 93 Trace Job List, 91 Trace Start, 88 Trace Stop, 90 Communications Protocols, 15 Configuration, HW1, 9
B
Backup DLS, 47 BSC Extension and Reduction, 69 adding N7 link, 77 broadcast bus testing, 78 cable testing, 79 clock testing, 80 complete G2 testing, 83 DC/DC convertor testing, 81 disabling switch for extension, 75 downloading BSC extension software, 71 extending BSC configuration, 70 going operational, 86 initializing switch after reduction, 76 modifying BSC configuration, 74 reducing BSC configuration, 73 resetting BSC extension, 72 stopping loop testing, 84 stopping testing, 85 termination plug testing, 82 BSC Terminal, installing terminal software, 17 BTS Download, status monitoring, 103 BTS Status Monitoting, timer settings, 104
133 / 136
Index
Connecting Terminal to BSC, 24
Help menu, 33 HW1 Configuration, 9 HW2 Configuration, 9
D
Deleting BSC files, 51 trace files, 93 Directories, listing information, 50 Disabling SBLs, 61 Disk operations, 41 Disks, listing information, 50 Displaying alarm lists, 66 date and time, 99 DLS backing up, 47 installing new, 108
I
Initializing SBLs, 60 system, 96 Installing EICON C20 PBA, 16 EICON C31 PBA, 16 new BSS software, 106 new DLS, 108 software on BSC, 110 terminal software, 17 X.25 PBA, 16
E
EICON installing C20 PBA, 16 installing C31 PBA, 16 Enabling PC reporting, 67
J
Jobs, listing trace, 91
L
LEDs Active CPRC or CPRA, 106 CPRC or CPRA, 98 Listing alarms, 66 disk and directory information, 50 SBL state, 63 trace jobs, 91 Loading Minibuild, 97 Logging commands, 102 reports, 102 Logging of Commands and Reports, 102
F
File menu, 33 Files deleting BSC, 51 deleting traces, 93 reading traces, 92 transferring between SSDs, 45 transferring from BSC to terminal, 44 transferring from terminal to BSC, 42 Formatting duplex SSD, 49 simplex SSD, 48 Full View, 38
M
Management alarms, 65 SBL, 53 traces, 87
H
Hardware terminal requirements, 14
134 / 136
Index
Menu file, 33 help, 33 utilities, 33 view, 33 Minibuild Loading, 97 MKI Configuration, 9 MKII Configuration, 9 Modify, Date & Time, 100
S
Saving Reports, 39 SBLs, 54 disabling, 61 initializing, 60 reading state lists, 63 reading status, 62 resetting, 56 restarting, 59 testing, 64 verifying, 57 Software installing and starting on BSC, 110 installing new BSS, 106 installing terminal, 17 starting terminal, 26 terminal requirements, 14 SSD formatting duplex, 49 formatting simplex, 48 transferring files between, 45 Starting software on BSC, 110 terminal software, 26 traces, 88 States, SBL, 54 Status, reading SBL, 62 Status Monitoring, BTS download, 103 Stopping traces, 90 System initializing, 96
O
Open a New Report View Window, 39 Operations disk, 41 miscellaneous, 95
P
PBA, installing X.25, 16 Protocols Alcatel proprietary, 15 X.25, 15
R
Reading SBL state lists, 63 SBL status, 62 trace files, 92 Reporting, enabling PC, 67 Reports full view, 38 logging, 102 saving, 39 Requirements terminal hardware, 14 terminal software, 14 Resetting SBLs, 56 Restarting SBLs, 59 Routing rules for unsolicited alarms, 67
T
Terminal description, 14 miscellaneous operations, 95 Terminal Connection alarm priority, 67 RS 232 asynchronous, 24 X.25 synchronous with EICON PBA, 25 Test results, 114 results - CPR/DTC/TCU, 116 results - Link/Switch, 121 results - N7, 128
135 / 136
Index
Test Report, 114 Testing SBLs, 64 Time, adjusting, 101 Timer Settings, BTS dowload status monitoring, 104 Traces deleting files, 93 listing jobs, 91 management, 87 reading files, 92 starting, 88 stopping, 90 Transferring files between SSDs, 45 files from BSC to terminal, 44 files from terminal to BSC, 42
X
X.25 configuring software, 21 installing PBA, 16 installing software, 19
U
Utilities, Minibuild Loading, 97 Utilities menu, 33
V
Verifying SBLs, 57 View menu, 33
W
Windows BSC Communication Control, 26 BSC Terminal, 28, 32 Compressed Report View, 36 Eicon Configuration, 20 Eicon Configuration with HDLC Advanced Properties, 22 Eicon Configuration with Sync General Properties, 23 Eicon Configuration with X.25 General Properties, 21 Report Example, 39 X.25 Dialing Properties, 27
136 / 136
C o v e r
Status Class_1 Class_2 Short Title Released Alcatel 900/1800 BSS O&M Document BSC TUG
S h e e t
Class_3 Class_4 Doc ID LMT User Guide
Main_Title Sub_Title DOCC MMCC
BSC Terminal User Guide *NA *NA
CRN No
History
Edition Date Change Note Operator: Comp. Dept. Name Originator: Comp. Dept. Name Appraisor: Comp. Dept. Name CITVY RCD/TD/O&M/CSI C. Spiers CITVY RCD/TD/O&M/CSI C. Spiers CITVY RCD/TD/O&M/CSI/GCD -A S. Gill CITVY RCD/TD/O&M/CSI/GCD -A S. Gill CITVY RCD/TD/O&M/CSI/GCD -A S. Gill CITVY RCD/TD/O&M/CSI/GCD -A S. Gill 01 991005 02 991104
External History of Last Edition
Internal History of Last Edition

Update based on information supplied by E. Gimenez from BDC readme.txt file delivered with BSC TE SW
1 / 136
C o v e r
Distribution List
Internal Code company code Site 1 External Code department
S h e e t
chars name full name 5/12/15
Abstract
Review

BSC Terminal User Guide (O & M)

Uploaded by

Document Information

Original Description:

Original Title

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

BSC Terminal User Guide (O & M)

Uploaded by

Copyright:

Available Formats

Alcatel 900/1800 BSS

BSC Terminal User Guide

3BK 20351 AAAA PCZZA Ed. 02

Status Change Note

3BK 20351 AAAA PCZZA Ed. 02

1.4 1.5 1.6 2 2.1 2.2 2.3 2.4

Terminal Menus and Functions . . . . . . . . . . . . . . . . . . . . . .

3BK 20351 AAAA PCZZA Ed. 02

Alarm Management . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5.1 5.2

Trace Management . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7.1 7.2 7.3 7.4 7.5

3BK 20351 AAAA PCZZA Ed. 02

Test Command Results . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9.1 9.2 9.3 9.4 Index

3BK 20351 AAAA PCZZA Ed. 02

3BK 20351 AAAA PCZZA Ed. 02

71 72 73 74 75 76 77 78 79 80 81 82 83 84 85 86 88 90 91 92 93 96 97 99 100 101 103 104 106 114

3BK 20351 AAAA PCZZA Ed. 02

3BK 20351 AAAA PCZZA Ed. 02

The guide is intended for:

System support engineers Operating personnel.

3BK 20351 AAAA PCZZA Ed. 02

The reader must be familiar with the following:

Chapter 2 Chapter 3 Chapter 4 Chapter 5 Chapter 6

3BK 20351 AAAA PCZZA Ed. 02

Chapter 7 Chapter 8 Chapter 9

The following conventions are used in the guide:

3BK 20351 AAAA PCZZA Ed. 02

3BK 20351 AAAA PCZZA Ed. 02

1 Installing and Starting the Terminal

1 Installing and Starting the Terminal

3BK 20351 AAAA PCZZA Ed. 02

1 Installing and Starting the Terminal

3BK 20351 AAAA PCZZA Ed. 02

1 Installing and Starting the Terminal

3BK 20351 AAAA PCZZA Ed. 02

1 Installing and Starting the Terminal

Installing an X.25 PBA in the Terminal

Tools and Materials

You must have:

EICON C20 PBA

EICON C31 PBA

3BK 20351 AAAA PCZZA Ed. 02

1 Installing and Starting the Terminal

Installing the Terminal Software

Software Installation Process

To install and configure the terminal software, you must:

Installing the Windows BSC Terminal Software

3BK 20351 AAAA PCZZA Ed. 02

1 Installing and Starting the Terminal

WinBSC Program Group

3BK 20351 AAAA PCZZA Ed. 02

1 Installing and Starting the Terminal

Installing the X.25 Software

3BK 20351 AAAA PCZZA Ed. 02

1 Installing and Starting the Terminal

Eicon Configuration Window

3BK 20351 AAAA PCZZA Ed. 02

1 Installing and Starting the Terminal

Configuring the X.25 Software

2. Click on the General tab and:

3BK 20351 AAAA PCZZA Ed. 02

1 Installing and Starting the Terminal

7. Set the timer to the following values: