Professional Documents
Culture Documents
BSC Terminal. - User Guide
BSC Terminal. - User Guide
Status RELEASED
Contents
Preface . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9
1 Installing and Starting the Terminal . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11
1.1 Terminal Description . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12
1.2 Install an X.25 PBA in the Terminal . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13
1.2.1 Tools and Materials . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13
1.2.2 Install EICON C91 PBA . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13
1.2.3 Install ACB-PCMCIA PBA . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13
1.2.4 Install LayGO MG-100 PCMCIA Card . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14
1.3 Install the Terminal Software . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16
1.3.1 Install the Windows BSC Terminal Software . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16
1.3.2 Install and Configure the EICON X.25 Software . . . . . . . . . . . . . . . . . . . . . . . . . . . 18
1.4 Upgrade BSC Terminal Software . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 22
1.5 Connect the Terminal to the BSC . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 22
1.5.1 RS-232 Link . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 23
1.5.2 X.25 EICON C91 PBA . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 23
1.5.3 X.25 ACB-PCMCIA PBA . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 24
1.6 Start the Terminal Software . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 24
1.7 Stop the BSC Terminal Software . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 27
2 Terminal Menus and Functions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 29
2.1 BSC Terminal Menu . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 30
2.1.1 BSC Terminal Menu Tree . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 30
2.1.2 Commands Menu . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 32
2.2 Toolbar . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 34
2.3 Command Result Display in Status Bar . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 34
2.4 Handle Reports . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 35
2.4.1 Compressed View . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 35
2.4.2 Full Report View . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 38
2.4.3 Save Reports . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 38
2.4.4 Print Reports . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 39
2.4.5 Open a New Report View Window . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 39
3 Disk Operations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 41
3.1 Recommendations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 42
3.2 Transfer Files from the Terminal to the BSC . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 42
3.3 Transfer Files from the BSC to the Terminal . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 44
3.4 Transfer Files Between SSDs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 45
3.5 Back Up the DLS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 46
3.6 Format a Simplex SSD . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 47
3.7 Format a Duplex SSD . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 48
3.8 Display SSD Information . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 49
3.9 Rename, Delete, Erase and Purge BSC Files . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 50
4 SBL Management . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 53
4.1 Reset SBLs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 54
4.2 Verify SBLs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 54
4.3 Restart SBLs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 56
4.4 Initialize SBLs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 57
4.5 Disable SBLs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 58
4.6 Read SBL Status . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 59
4.7 Read SBL State Lists . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 60
4.8 Test SBLs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 61
5 Alarm Management . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 63
5.1 Display Alarm Lists . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 64
5.2 Enable PC Reporting . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 64
Figures
Figure 1: Eicon Configuration Window . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18
Figure 2: RS-232 Asynchronous Link Connection . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 23
Figure 3: X.25 EICON C91 Synchronous Link Connection . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 23
Figure 4: X.25 ACB-PCMCIA Synchronous Link Connection . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 24
Figure 5: BSC Terminal Window . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 30
Figure 6: BSC Terminal Commands Menu Tree . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 33
Figure 7: Modify BSC Peer Entities - X.25 - 1 Window . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 93
Figure 8: Modify BSC Peer Entities - X.25 - 2 Window . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 94
Figure 9: Declare BSC Peer Entities - X.25 - 1 Window . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 96
Figure 10: Declare BSC Peer Entities - X.25 - 2 Window . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 97
Figure 11: Active SYS-CPRC Front Panel LEDs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 109
Tables
Table 1: BSC Terminal-Specific Options . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 31
Table 2: Successful Test Results Format for Link/Switch . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 121
Table 3: Unsuccessful Test Results Format for Link/Switch . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 121
Table 4: Decode of Example Failure Data for Link/Switch . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 122
Table 5: Test Segment Results for Link/Switch . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 123
Table 6: Test Fault Type Results for Link/Switch . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 126
Table 7: Test Raw Data Results for Link/Switch . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 127
Table 8: Link/Switch Nibble Description . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 128
Table 9: Test Results Format for N7 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 129
Table 10: Decode of Example Test Raw Data for N7 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 130
Table 11: Test Raw Data Results for N7 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 130
Table 12: N7 Nibble Description . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 130
Preface
Purpose The purpose of the BSC Terminal User Guide is to describe how to install and
set up a BSC terminal, and how to use the terminal to perform O&M functions.
In Edition 01
First official release of document for B11.
This document contains information about the Support of Windows Vista for PC
LMT feature in Install the Windows BSC Terminal Software (Section 1.3.1)
Operating personnel
Training department.
IBM-compatible PCs
Microsoft Windows 2000 / XP / Vista operating system software
This section tells you how to install the terminal hardware and software and
then start it.
Communication Protocols
The interchange of data between the PC and the BSC via an RS-232
asynchronous link uses an Alcatel-Lucent 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 or ACB-PCMCIA PBAs.
The terminal is connected to one of the System CPRCs. If this processor fails,
the terminal is restarted by the duplex System CPRC. If the restart also fails,
communication with the BSC is no longer possible.
A small crosshead screwdriver for removing the screws on the cover of the
PC (for EICON C91 only)
6. Then check Include this location in the search: complete this location
C:\Laygo\drv\ then click on [ Next ] .
Connections for Windows for the EICON or ACB-PCMCIA X.25 link option
(CD-ROM).
Prerequisites If you are using the optional X.25 link, you must install the
appropriate hardware (EICON or ACB-PCMCIA PBA) in the terminal PC first
(see Install an X.25 PBA in the Terminal (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 (Section 1.3.1)
The Windows BSC Terminal software is required for whatever type of link is
used to the BSC, RS-232 asynchronous or X.25 synchronous.
Note: Ignore the system error message ’The following file(s) failed to
self-register’ , which can be displayed at the end of the installation.
6. In the setup type window select Eicon or Laygo .
In the Setup Complete window at the end of the installation, you may be
asked if you want to restart the computer.
7. If Restart the computer appear in the "Setup Complete" window, select
Restart and then click on [ Finish ]. Otherwise click directly on [ Finish ].
When the setup is complete, a WinBSC program group is created, as
shown in the figure below.
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.
In Case of a Problem If something goes wrong during the use of Eicon Card do the following:
During Installation 1. Go to Control Panel -> Services .
2. Select Eicon Card and click on [ Stop ] .
3. Then click on [ Start ] to restart Eicon Card .
Configure the EICON To configure the X.25 software for the EICON synchronous link to the BSC:
X.25 Software 1. In the Eicon Configuration window (see Figure 1 ), expand the Eicon Card
tree and the Port tree.
2. Then select the X.25 icon (see figure below).
3. Click on the General tab to display the Eicon Configuration window with the
X.25 General properties sheet, as shown in the above figure.
11. From the Eicon Configuration window menu bar, follow the menu path:
File -> Exit
12. In the New Configuration pop-up window, click on [ Yes ] to save the new
configuration.
13. In the WAN Services Install pop-up window, click on [ No ] to install no
other services.
14. Click on [ Close ] to close the Network window.
15. In the Network Settings Change window, click on [ Yes ] to restart the
computer.
Go to Connect the Terminal to the BSC (Section 1.5) to connect the terminal to
the BSC.
The Windows BSC Terminal software is required for whatever type of link
is used to the BSC:
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.
Rear of desktop
or notebook D−9
Connector CPRC
(male) PBAs
in BSC
cabinet 1
RS−232 Cable O O S S B B
(3BK 07948 GLAA) S S Y Y C C
I I S S
COM1 or COM2 Port
D9 connector (female)
Rear of Terminal
D−25 CPRC
D−25
Connector PBAs
Connector
(female) in BSC
Desktop PC (male)
cabinet 1
X.25 Adapter X.25 Cable * O O S S B B
(1AF01138AAA) (3BK 07760 GLAA) S S Y Y C C
on EICON C91 PBA I I S S
* The part number can differ from that shown, because it includes the length.
See the Evolium BSC Cable Description.
* The part number can differ from that shown, because it includes the length.
See the Evolium BSC Cable Description.
For an RS-232 asynchronous link, check that the COM1 or COM2 port
of the terminal is connected to one of the System-CPRC PBAs, as
shown in Figure 2
For an X.25 synchronous link, check that the EICON port of the terminal
is connected to one of the SYS-CPRC PBAs, as shown in Figure 3
or Figure 4 .
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 cannot select it.
5. If you are using a direct connection to the BSC, go 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 the figure below.
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 on [ Add ] , the Add Remote Connection window is displayed as
shown in the figure below.
This section describes the terminal menus and the functions they provide,
and includes the:
Handle reports.
The BSC terminal menu options specific to the BSC terminal software are
described in following table.
Save 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.
Save As Save all the reports in the Compressed Report View window in
a Microsoft Access database under a specified name.
Print Save the reports on hard disk into a TXT file and print this file
from within Notepad.
Print Setup Select the printer and change the properties for the selected
printer.
Utilities BTS Download Status Set the reporting mode or the session timer for monitoring the
downloading of files to multiple BTSs.
Logging Store commands and reports in a log file. This allows a detailed
investigation to be performed at a later data. Refer to Section
9.6 for more information.
View Extra Information Show or hide the Information column(s) in the Compressed
Report View window.
Real Time 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 Realtime Mode, a report displayed in
the Full Report View window is replaced when a new report is
received from the BSC.
Window Compressed Report When checked, shows that the Compressed Report View
View window is selected. Because the Compressed View Report
window is always open, this item is always present.
Full Report View Shows that a Full Report View window is open (Realtime Mode
enabled). When checked, shows that the Full Report View
window is selected.
Help Help Topics Display help information by selecting this item. Help information
can also be obtained by pressing the F1 key. When a command
dialogue is displayed, pressing F1 causes context-sensitive
help to be provided.
Commands Menu
Display Date & Time File Transfer from PC to BSC System Initialization Display Alarm List
Modify Date & Time File Transfer from BSC to PC Enable PC Reporting
Adjust Time File Transfer from BSC to BSC
DLS Backup
Format SSD
Format Duplex SSD
Control SSD
Delete File
Commands Menu
Test Handling Equipment Handling BTS Extension/Reduction BSC Extension/Reduction Trace Invocation
SBL Test SBL Reset Upload BIE Table BSC Config Modify Trace Job List
SBL Verify TCU Config Read
SBL Restart DTC Config Read Read Trace
SBL Initialize Disable Switch For Extension File From BSC
SBL Disable Init Switch After Reduction
SBL Read Status Trace File
BSC Extend Config Read Config
SBL State List BSC Extension Reset
BSC Download Extension SW
Go For Operation
BSC Reduce Config
Program Transmission
Commands Menu
2.2 Toolbar
The Toolbar contains shortcut buttons to some of the menu items (see Figure 5
).
window is displayed. .
Save the report into a TXT file and print this file from within Notepad. .
Display information concerning the version of the BSC terminal software and
Full Report View, which provides full information about the event which
has occurred.
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.
Date
Time
Report Type
Job Result.
In addition to these five 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.
2.4.1.2 Add 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 the figure below.
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.
4. Repeat step 3 for any other extra information you want to add to the report.
If a field in a report is grey, this indicates that no information for that field
was received from the BSC.
3 Disk Operations
This section tells you how to perform disk operations for the terminal and the
BSC, and contains procedures to:
Transfer BSS files from the hard disk of the terminal to an SSD in the BSC
Transfer BSS files from an SSD in the BSC to the hard disk of the terminal
Back up the DLS file from an SSD to the hard disk of the terminal
3.1 Recommendations
Read the following information before you start.
Procedure 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 the
figure below.
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 the figure below.
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.
File name
File number
File version
File sub-version.
4. In the PC File field, enter a full PC path name 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.
A DLS file
A single file.
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.
Prerequisites If you are going to transfer the DLS file or all the BSS files, first
delete all performance measurement jobs for the BSC.
Procedure 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 the
figure below.
All Files
DLS File
File name
File number
File version
File sub-version.
File name
File number
File version
File sub-version.
4. In the PC File field, enter a full PC path name 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.
Simplex SSD 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 the appropriate file in the Available Files panel. The list of files is
displayed, as shown in the figure below.
Duplex SSD 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 the figure below.
Deleting, erasing or purging a file can result in the loss of data. Always verify
that the correct file identity is used.
File number
File version
File sub-version.
4 SBL Management
This section tells you how to perform operations on SBLs, and contains
procedures to:
Reset SBLs
Verify SBLs
Restart SBLs
Initialize SBLs
Disable SBLs
Test SBLs.
Note: The SBL Reset command is a combination of the SBL Disable and the
SBL Initialize commands.
IT
FIT
OPR
FOS
FLT
A request for the verification of an SBL can be refused if any of the following
are in progress:
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.
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.
Do NOT initialize the DISC SBL in a duplex BSC if a file transfer between the
SSDs is in progress. Refer to Section 3.4 .
Prerequisites You can execute the SBL initialize command only if the higher
level SBLs are in the IT state.
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 elements 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.
5 Alarm Management
This section tells you how to manage alarms, and contains procedures to:
The link connected to the first SYS-CPRC has the highest priority
If no links are connected to the first SYS-CPRC, the link connected to the
second SYS-CPRC has the highest priority
If two links are connected to the same SYS-CPRC, the RS-232 link has
the higher priority.
This section tells you how to manage extension and reduction of the BTS
and BSC/TC.
For BTS extension/reduction this section contains one procedure: Upload
BIE Table.
For BSC/TC extension/reduction this section contains procedures to:
Program Transmission
Complete G2 test
Test Network
Check Plugs
Test DC/DC convertors
Test Clock
Stop test.
3. Click on [ OK ] to send the command to the BSC. The requested BIE table is
created on CPRC disk A, e.g,. for a BTS with unit number 1, the file name
is TR001001/01/A/8302.
The file identity of the BIE table is always 8302. This means that the file is
overwritten with the next upload command.
4. Transfer the BIE table from BSC to PC as described in Transfer Files from
the BSC to the Terminal (Section 3.3)
5. Repeat steps 1 and 2 for all the required BIE tables.
Extension To reset the BSC processors and initiate self-testing after extension of the
database:
1. From the BSC Terminal menu bar, follow the menu path:
Commands -> BSC Extension/Reduction -> BSC Extension Reset
The BSC Extension Reset window is displayed, as shown in the figure below.
Extension Software To download the BSC operational/test software to the added processors
after extension:
1. From the BSC Terminal menu bar, follow the menu path:
Commands -> BSC Extension/Reduction -> BSC Download Extension
SW
The BSC Download Extension Software window is displayed, as shown
in the figure below.
Clock test
Plug check
Broadcast test.
3. In the ’Source’ field, select the network address of the appropriate source
control element.
4. In the ’Destination’ field, select the network address of the appropriate
destination control element.
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.
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 control element 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.
2. In the ’Test’ field, select START DC/DC TEST or STOP DC/DC TEST ,
as required.
3. Click on [ OK ] to start/stop the DC/DC convertor test.
7 Trace Management
Status
Radio channel identity (optional).
File name
File number
File version
File sub-version.
4. In the ’PC File’ field, enter the full PC path name of the trace file, or click on
[ Browse... ] and navigate to the appropriate directory.
5. Click on [ OK ] to start reading the trace file.
8 BSS Operations
This section tells you how to perform BSS Operations, and contains procedures
to:
4. Click on the X.25 - 1 Tab (see Figure 7 ) and complete the sheet as follows:
In ’BSC X.25 Primary Address’ and ’BSC X.25 Secondary Address’ ,
enter the appropriate 15-digit X.25 Address.
In ’ X.25 Virtual Circuit Nbr’ , enter the number of X.25 Virtual Circuits
In ’X.25 Packet Size Transmit’ and ’X.25 Packet Size Receive’ , indicate
the size of the X.25 packets
5. Click on the X.25 - 2 Tab to display the second X.25 sheet (see Figure 8 )
and complete the sheet as follows:
In ’Pref OMC X.25 Primary Address’ and ’Pref OMC X.25 Secondary
Address’ , indicate the appropriate 15-digit X.25 Address
4. Click on the X.25 Tabs (see Figure 9 and Figure 10 ) and complete the
sheets as follows:
In ’BSC X.25 Address Flag’ , indicate whether or not the BSC must
put its own X.25 address in the Call Setup message when indicating
a connection with the OMC-R
In ’Physical Routing’ , indicate whether the X.25 is extracted/inserted
at the BSC (direct)
through the A-interface at the MSC (MSC routed)
through the A-interface at the TC (TC routed).
For all other parameters, enter the original value obtained by the Display
BSC Peer Entities command.
3. Click on the X.25-2 Tab and make sure that all parameters fields are empty.
4. Click on [ OK ] to modify the Physical Routing parameter.
Load Minibuild
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.
System actions such as reload and reboot result in the loss of all calls and all
ongoing actions such as confirmation to the terminal.
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.
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 LEDs on
the SYS-CPRC PBA.
2. In the ’Place log files in this directory’ field, enter the path of the directory
where you want the log files to be stored.
3. To activate the logging function, click in the ’Log this session’ check box. A
check mark is displayed in the box.
4. To deactivate the logging function, repeat the procedure described in Steps
1 and 3 . Check that the check mark has been removed.
Do not have the logging function active all the time because it can adversely
affect the performance of the system.
Reporting Interval Timer, which controls the interval at which BTS download
status reports are generated.
2. If you want to use the default settings, Click on [ Default ] . The default
settings are:
If you do not want to use the default settings, click on the increment or
decrement button next to the appropriate field to select the required settings.
3. Click on [ OK ] to accept the new timer settings.
Ensure that the GZIP DOS tool (freeware) is installed on the hard disk
of the terminal. This tool is needed to decompress the files. This GZIP
program is delivered with the terminal software.
N indicates that the original names and time stamps of the files are to
be restored
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.
LED On
LED Off
2. Connect the link cable between the terminal and the active SYS-CPRC, as
described in Section 1.5 .
3. Start the terminal software, as described in Section 1.6 .
4. Disable the BSC SBL, as described in Section 4.5 , and wait for a message
confirming that the BSC is disabled before proceeding to the next step.
5. Format the SSD of the SYS-CPRC1, as described in Section 3.6 .
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) SYS-CPRC1, as
described in Section 3.2 .
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.
7. Check that all files are downloaded correctly, as described in Section 3.8 .
8. For a duplex BSC only, format the SSD of the standby SYS-CPRC2, as
described in Section 3.7 . 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 SYS-CPRC1 to the SSD (disk B) of SYS-CPRC2, as described in
Section 3.4 .Note the following:
Check that all files are downloaded correctly, as described in Section 3.8 .
Check that all files are downloaded correctly, as described in Section 3.8 .
At installation time
When a fatal error has occurred at the BSC, the SYS-CPRC is no longer
active, and a Minibuild is required.
Formatting a normal SSD can result in the loss of software and data.
If an SYS-CPRC fails during a communication session, the session is aborted.
Restrictions You can only use the X.25 link option for the terminal after the
Minibuild is loaded onto the SYS-CPRC. This is because the Minibuild contains
the packet handler for the X.25 link.
Impact on System During the installation process, the BSC is not available. All
traffic handled by the BSC and its associated BTSs is interrupted.
Procedure To install a new BSS software version on a BSC:
1. Connect the RS-232 asynchronous link cable between the terminal and
the SYS-CPRC1, as described in Section 1.5 .
2. Start the terminal software, as described in Section 1.6 .
3. Perform a Minibuild on the BSC, as described in Section 9.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 SYS-CPRC1 from its subrack, wait at least 30 seconds, and then
replace it. When replaced, the SYS-CPRC1 performs a self-test that lasts
approximately 7 minutes.
5. Repeat Steps 1 to 3.
6. Format the SSD of the SYS-CPRC1, as described in Section 3.6 , using
the BSS Masterfile.
7. Download the BSS software to the SSD of the (formatted) SYS-CPRC1, as
described in Section 3.2 , 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.
8. Check that all files are downloaded correctly, as described in Section 3.8 .
9. Initialize the BSC, as described in Section 9.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 SYS-CPRC2 becomes IT.
11. Format the SSD of the (standby) SYS-CPRC2, as described in Section 3.7 .
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 SYS-CPRC1 to
the SSD (disk B) of the (standby) SYS-CPRC2, as described in Section
3.4 . Note the following:
Check that all files are downloaded correctly, as described in Section 3.8 .
13. Check that all SBLs are initialized and in the IT state, as described in
Section 4.6 .
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.
Test Segment 0
A successful job result is accompanied by the Test Segment, Test Fault Type
and Test Raw Data values shown in Table 2 . 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 the following
table.
Test Raw Data H’00 H’45 H’00 H’40 H’13 H’00 H’45 H’00 H’40 H’FF
H’10 H’10 H’12 H’10 H’10 H’FF H’FF H’FF H’FF H’FF
H’10 H’10 H’10 H’10 H’10 H’FF H’FF H’FF H’FF H’FF
H’10 H’10 H’10 H’10 H’10 H’FF H’FF H’FF H’FF H’FF
(See Table 7 )
If the tests execute and failures are detected, the Test Segment and Test Fault
Type values are not both at 0. Tables 5 and 6 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 7 ; 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.
The decode of the example failure data in Table 3 is shown in the table below.
Test Raw Data Byte 5 H’13 TDM connection between Link H’0045 and
Port 0 of Switch H’0040 failed (timeout)
Test Raw Data Byte 8 H’12 TDM connection between Link H’0045 and
Port 3 of Switch H’0040 failed (bad test
packet and End Of Packets received)
1 Unmask Channel 0, send interrogation and wait for the tunnel reply.
5 Set up a temporary path towards the permanent path, via maintenance selects. The
permanent path should be released. An alarm is not generated.
10 Set up temporary path (with interrogations included), via test depth, towards own OBCI.
Check the contents of the received packet.
11 Tunnel test. Check all depths of the tunnel, via a temporary path, with interrogations.
14 Set up permanent path via test depth, towards own OBCI, with test pattern attached.
15 Try to set up a temporary path towards the permanent path. This should be rejected.
16 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.
0 No errors
6 No channel available
16 No channel available
52 ACI = 0 MB = 0 AS = 1
53 ACI = 0 MB = 1 AS = 0
54 ACI = 0 MB = 1 AS = 1
55 ACI = 1 MB = 0 AS = 0
56 ACI = 1 MB = 0 AS = 1
57 ACI = 1 MB = 1 AS = 0
58 ACI = 1 MB = 1 AS = 1
72 BCLA: wrong ID
Byte 5 * TDM connection between Port 0 and Link NA. See also Table 8 .
Byte 6 * TDM connection between Port 1 and Link NA. See also Table 8 .
Byte 7 * TDM connection between Port 2 and Link NA. See also Table 8 .
Byte 8 * TDM connection between Port 3 and Link NA. See also Table 8 .
Byte 9 * TDM connection between Port 4 and Link NA. See also Table 8 .
Byte 10 * TDM connection between Port 5 and Link NA. See also Table 8 .
Byte 11* TDM connection between Port 6 and Link NA. See also Table 8 .
Byte 12 * TDM connection between Port 7 and Link NA. See also Table 8 .
Byte 13 * TDM connection between Port 8 and Link NA. See also Table 8 .
Byte 14 * TDM connection between Port 9 and Link NA. See also Table 8 .
Byte 15 * TDM connection between Port A and Link NA. See also Table 8 .
Byte 16 * TDM connection between Port B and Link NA. See also Table 8 .
Byte 17 * TDM connection between Port C and Link NA. See also Table 8 .
Byte 18 * TDM connection between Port D and Link NA. See also Table 8 .
Byte 19 * TDM connection between Port E and Link NA. See also Table 8 .
Byte 20 * TDM connection between Port F and Link NA. See also Table 8 .
* Test Raw Data Bytes 5 to 20 are only relevant for Test Segment Results 12
and 13 (failed TDM bus tests; see Table 5 ). 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.
1 Connection tested
Low 0 Test OK
3 Timeout
Test Segment 1 0
Test Raw Data H’12 H’01 H’00 H’00 H’40 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’FF H’FF H’FF H’FF H’00 H’00 H’00 H’00 H’00
H’FF H’FF H’FF H’FF H’FF H’00 H’00 H’00 H’00 H’00
(See Table 11 )
A successful job result is accompanied by the Test Segment and Test Fault
Type values shown in the above table. 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 the above table, some bytes do not have the value H’FF. This
information is decoded using Table 11 .
The decode of the example Test Raw Data information in Table 9 is shown in
the following table.
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.
In the above table, a bit with the value 1 indicates a failure, and a 0 indicates a
pass.
Bit Description