Académique Documents
Professionnel Documents
Culture Documents
Status RELEASED
Contents
Preface . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7
1 Install and Start Terminal . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11
1.1 Terminal Description . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12
1.1.1 Hardware Requirements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12
1.1.2 Software Requirements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12
1.1.3 Communication Protocols . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12
1.2 Install Windows BSC Terminal Software . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13
1.3 Install TightVNC Software . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14
1.4 Connect Terminal to the BSC . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15
1.5 Start Terminal Software . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16
1.6 Stop BSC Terminal Software . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17
2 Terminal Menus and Functions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19
2.1 BSC Terminal Menu . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 20
2.1.1 BSC Terminal Menu Tree . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 20
2.1.2 Commands Menu . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 23
2.2 Toolbar . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 24
2.3 Command Result Display in Status Bar . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 24
2.4 Handle Reports . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 25
2.4.1 Compressed View . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 25
2.4.2 Full Report View . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 27
2.4.3 Save Reports . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 27
2.4.4 Print Reports . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 28
2.4.5 Open a New Report View Window . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 28
3 SBL Management . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 29
3.1 Reset SBLs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 30
3.2 Verify SBLs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 31
3.3 Restart SBLs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 32
3.4 Initialize SBLs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 33
3.5 Disable SBLs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 34
3.6 Read SBL Status . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 35
3.7 Read SBL State Lists . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 36
3.8 Test SBLs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 37
4 Manage Alarms . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 39
4.1 Display Alarm Lists . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 40
4.2 Enable PC Reporting . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 40
5 Extend/Reduce BTS and BSC . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 43
5.1 Upload BIE Table . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 44
5.2 Get Abis Occupancy-Mx . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 45
5.3 Modify BSC/TC Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 46
5.4 Read TCU Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 47
5.5 Read DTC Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 48
5.6 Go For Operation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 49
5.7 Program Transmission (Abis) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 50
5.8 Program Transmission (Ater) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 51
5.9 Activate/Deactivate HSL . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 52
5.10 BTS Grouping . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 53
5.11 BSC Reduce Config . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 54
6 Manage Traces . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 55
6.1 List Trace Jobs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 56
6.2 Delete Trace Files from the BSC . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 57
7 BSS Operations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 59
Figures
Figure 1: Ethernet BSC Terminal Connection. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15
Figure 2: BSC Terminal Window . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 20
Figure 3: BSC Terminal Commands Menu Tree . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 23
Figure 4: Modify BSC Peer Entities - Address - 1 Window . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 62
Figure 5: Modify BSC Peer Entities - Address - 2 Window . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 63
Figure 6: Declare BSC Peer Entities - Cell Window . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 64
Figure 7: Declare BSC Peer Entities - Address - 1 Window . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 66
Figure 8: Declare BSC Peer Entities - Address - 2 Window . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 67
Figure 9: Declare BSC Peer Entities - Address - 3 Window . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 69
Tables
Table 1: Hardware Environment . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12
Table 2: BSC Terminal-Specific Options . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 22
Table 3: Successful Test Results Format for Link/Switch . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 91
Table 4: Unsuccessful Test Results Format for Link/Switch . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 91
Table 5: Decode of Example Failure Data for Link/Switch . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 92
Table 6: Test Segment Results for Link/Switch . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 93
Table 7: Test Fault Type Results for Link/Switch . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 96
Table 8: Test Raw Data Results for Link/Switch . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 97
Table 9: Link/Switch Nibble Description . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 98
Table 10: Test Results Format for N7 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 99
Table 11: Decode of Example Test Raw Data for N7 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 100
Table 12: Test Raw Data Results for N7 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 100
Table 13: N7 Nibble Description . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 100
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 13
Description improvement in:
BSC Reduce Config (Section 5.11)
In Edition 12
Section Program Transmission (Abis) (Section 5.7) was added.
Description improvement in:
In Edition 11
Description improvement in the following sections:
In Edition 10
Command “Display HW Log Mapping Type” was removed from the document
as it is no more available at BSC terminal.
In Edition 09
Description improvement in Write BSC Inventory (Section 7.6).
In Edition 08
Update for new equipment naming.
In Edition 07
Description improvement in:
In Edition 06
Overall document quality was improved following a quality review.
In Edition 05
The following sections were added:
Activate Steer File (Section 8.10)
In Edition 04
The following sections were added:
In Edition 03
Description improvement in Read BSC Remote Inventory (Section 7.5).
In Edition 02
3BKA20FBR217710 Restriction introduction in Read SBL Status (Section 3.6).
In Edition 01
First release of the document.
Operating personnel
Training personnel.
This section describes how to install the terminal hardware and software
and then start it.
RAM 64 MByte
Hard disk At least 100 Mbyte free for program and data storage
Monitor SVGA
TightVNC Server
TightVNC Viewer
8. Click on [ Next ].
9. Select the Start Menu folder where the shortcuts will be created.
10. Click on [ Next ].
11. Select the additional tasks:
Before 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.
Open the cabinet front door and connect the Ethernet cable as shown in
the figure below.
There are two ways to connect the PC to the BSC, using the BSC terminal:
When the connection is established in the status bar (see figure below),
the following information appears:
Connection status
User mode
Status.
This section describes the terminal menus and the functions they provide,
including the:
BSC Terminal Menu
Handle reports.
The following table describes the BSC terminal menu options specific to
the BSC terminal software.
Save Save all the reports in the Compressed Report View window
in a Microsoft Access database. If the reports are not already
saved, the Save As window appears.
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.
Reconnect Interval Use the Reconnect Interval utility to set the timers used for the
WinBSC Terminal to reconnect to the BSC.
(The default value of interval is 5 seconds.)
Download BSC Remote Download the BSC remote inventory file to the LMT PC.
inventory file
Logging Store commands and reports in a log file. This allows a detailed
investigation to be performed at a later data. Refer to Log
Commands and Reports (Section 8.5) 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 appears
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.
View All the Reports The display of reports by BSC Term in the Compressed Report
View is limited to the latest 250 reports by default. Use this
command to display all the reports received by the Terminal.
This allows the user to view reports which are not displayed due
to the limit of 250 latest reports.
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 [ F1 ] . When a command
dialogue appears, pressing [ F1 ] displays the associated
context-sensitive help.
Display Date & Time Display Alarm List SBL Test SBL Reset
Enable PC Reporting SBL Verify
SBL Restart
SBL Initialize
SBL Disable
SBL Read Status
SBL State List
Commands Menu
Commands Menu
Display BSC Peer Entities System Test Change QMUX Activate Steer File
Modify BSC Peer Entities Address Request Deactivate Steer File
Display Declare BSC Peer Entities Delete Steer File and Rollback File
Display HW Log Mapping Type Display History File
BSC Remote Inventoy Read
BSC Remote Inventoy Write
BSC Remote Inventoy Write Header
2.2 Toolbar
The Toolbar contains shortcut buttons to some of the menu items (see Figure 2).
appears. .
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.
Display a number of full view report windows simultaneously 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, select View -> Extra Information.
The "Extra Info Settings" window appears, as shown in the figure below.
2. Click on the ’Report’ field dropdown menu and select the required report
from the list.
Any extra information which has already been added to the report appears
in the appropriate Extra Info fields.
3. To add extra information, click on the dropdown 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.
5. Click on [ Save ] to save the extra information settings.
Note: If you duplicate any extra information, the system generates a warning
message.
If a field in a report is grey, this indicates that no information for that field
was received from the BSC.
3 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.
To reset an SBL:
1. From the BSC Terminal menu bar, select:
Commands -> Equipment Handling -> SBL Reset
The "SBL Reset" window appears, as shown in the figure below.
IT
FIT
OPR
FOS
FLT
A request for the verification of an SBL can be refused if any of the following
are in progress:
Note: 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, select:
Commands -> Equipment Handling -> SBL Initialize
The "SBL Initialize" window appears, as shown in the figure below.
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.
Note: 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, select:
Commands -> Equipment Handling -> SBL Disable
The "SBL Disable" window appears, as shown in the figure below.
4 Manage Alarms
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
This section tells you how to manage BTS and BSC/TC extension and
reduction.
For BTS extension/reduction, it describes how to:
Upload the BIE table
3. Click on [ OK ] to send the command to the BSC. The requested BIE table is
created on CPRC disk A (for example, 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.
’EXTENDED’ for the Signal Unit frame with extended sequence number
format.
Note: The LSL uses the normal MTP_Sequence_Number_Format and the HSL
may use the normal MTP_Sequence_Number_Format or the extended
MTP_Sequence_Number_Format
8. Click on [ OK ] to configure signalling on the AterMux.
6 Manage Traces
Status
7 BSS Operations
This section tells you how to perform the following BSS operations:
4. Click on the Address - 1 Tab and Address - 2 Tab (see Figure 4 and
Figure 5) and complete the sheets as described in Display Declare BSC
Peer Entities (Section 7.3).
9. Click on the Address - 1 Tab (see Figure 7) and complete the sheet 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 O&M traffic 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).
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
In ’X.25 L3 Window Size Transmit’ and ’X.25 L3 Window Size Receive’,
indicate the value of the layer 3 window size for X.25 calls (default
value = 2)
In ’X.25 Max I Frame Size’, indicate the maximum number of octets
in a layer 3 frame
In ’Window RFH FTAM’, indicate the window size of the local interface
in the BSC for the control between the remote file handler and the
FTAM (default value = 4).
In ’IP MLPP’, indicate the number of time slots used for MLPP connection
This field is used only if for the Physical Routing ’MSC Routed’ or ’TC
Routed’ is selected.
10. Click on the Address - 2 Tab to display the second Address sheet (see Figure
8) and complete the sheet as follows:
In ’CBC X.25 Primary Address’ and ’CBC X.25 Secondary Address’,
indicate the appropriate 15-digit X.25 Address
In the ’BSC IP SUB NET B:’, type the new IP subnet address
11. Click on Address - 3 Tab to display the third Address sheet (see Figure 9)
and complete the sheet as follows:
In ’Pref OMC PID’, indicate the Protocol Identifier of the preferred OMC
In ’Pref TSAP ID’, indicate the Transport Service Access Point Identifier
for the preferred OMC
In ’Pref SSAP ID’, indicate the Session Service Access Point Identifier
for the preferred OMC
1 JSXLIU shelf 1
2 JSXLIU shelf 2
3 JSXATCA shelf 3
4 JSXATCA shelf 4
7. In the ’Local path for saving Remote Inventory file’ field, enter the path for
saving the Remote Inventory file.
8. Click on [ OK ] to read the remote inventory.
When the remote inventory file is created a confirmation message is
displayed asking if you want to download the file on local PC.
9. Click on [ Yes ] if you want to download the file or on [ No ], otherwise.
If you click on [ Yes ] the "Download Remote Inventory File" window
is displayed.
Note: Select ANYORNOTSNF to update the first commissioing date on all boards in
one step.
9. In the ’Rack ID’ field, enter the rack ID.
10. In the ’Shelf ID For FRU’ field, enter shelf ID for the FRU.
11. In the ’Slot ID’ field, enter the slot ID.
12. In the ’Rem in Area Addr’ field, enter the remote inventory area address.
13. In the ’Data’ field, enter the current date.
14. Click on [ OK ] to write the remote inventory.
2. Enter the ’E1 Link ID’ field, enter ID link (between 0 to 251).
3. Click on [ OK ] to update the Compressed Report View window.
2. Enter the ’E1 Link ID’ field, enter ID link (between 0 to 251).
3. Click on [ OK ] to update the Compressed Report View window.
2. In the ’Place log files in this directory’ field, enter the path of the directory in
which to store the log files.
3. To activate the logging function, click in the ’Log this session’ check box. A
check mark appears in the box.
4. To deactivate the logging function, repeat the procedure described in Steps
1 and 3. Check that the check mark is removed.
Do not leave the logging function active all the time because it can adversely
affect system performance.
The Reporting Interval Timer, which controls the interval at which BTS
download status reports are generated.
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.
2. If you want to switch to master user mode, click on [ Yes ], otherwise click
on [ No ].
Remote File Path: The path where the file is located on the BSC:
/common/BSC/RI
Local File Path: The path on the BSC terminal PC where the file is saved
Default path is C:\BSC_RI.
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 3. 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 8)
If the tests execute and failures are detected, the Test Segment and Test Fault
Type values are not both at 0. Tables 6 and 7 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 8; 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 following table shows the decode of the example failure data in Table 4.
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 9.
Byte 6 * TDM connection between Port 1 and Link NA. See also Table 9.
Byte 7 * TDM connection between Port 2 and Link NA. See also Table 9.
Byte 8 * TDM connection between Port 3 and Link NA. See also Table 9.
Byte 9 * TDM connection between Port 4 and Link NA. See also Table 9.
Byte 10 * TDM connection between Port 5 and Link NA. See also Table 9.
Byte 11* TDM connection between Port 6 and Link NA. See also Table 9.
Byte 12 * TDM connection between Port 7 and Link NA. See also Table 9.
Byte 13 * TDM connection between Port 8 and Link NA. See also Table 9.
Byte 14 * TDM connection between Port 9 and Link NA. See also Table 9.
Byte 15 * TDM connection between Port A and Link NA. See also Table 9.
Byte 16 * TDM connection between Port B and Link NA. See also Table 9.
Byte 17 * TDM connection between Port C and Link NA. See also Table 9.
Byte 18 * TDM connection between Port D and Link NA. See also Table 9.
Byte 19 * TDM connection between Port E and Link NA. See also Table 9.
Byte 20 * TDM connection between Port F and Link NA. See also Table 9.
* Test Raw Data Bytes 5 to 20 are only relevant for Test Segment Results 12
and 13 (failed TDM bus tests; see Table 6). 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
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 12.
The following table shows the decode of the example Test Raw Data information
in Table 10.
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.
Byte 2 High nibble = message 1, low nibble = message 2. See Table 13.
Byte 3 High nibble = message 3, low nibble = message 4. See Table 13.
Byte 4 High nibble = message 5, low nibble = message 6. See Table 13.
In the above table, a bit with the value 1 indicates a failure, and a 0 indicates a
pass.
Bit Description