TCU Integration MOP

Public TCU INTEGRATION MOP Prepared (Subject resp)

1 (10)

No.

Ogün SIY Approved (Document resp)

Checked

Ogün SIY

Date

Rev

2013-12-26

PA1

Reference

Contents 1 2 3 3.1 3.2 3.3 3.4 3.5 3.6

Scope.................................................................................................2 Prerequisites.......................................................................................2 Work process......................................................................................2 HW Introduction..................................................................................3 Local Connection................................................................................4 Load SIU configuration script..............................................................6 Modify/Verify RBS IDB........................................................................7 RBS TCU Connection.........................................................................9 Troubleshooting................................................................................10

Public 2 (10)

TCU INTEGRATION MOP Prepared (Subject resp)

No.


Checked

Ogün SIY

1

Date

Rev

2013-12-26

PA1

Reference

Scope The scope of this document is to have a closure approach to TCU Integration. This document describes the steps how to set the STN parameters and further migrate traffic.

2

Prerequisites Before setting the TCU parameters, ensure the following:       

3

TCU is powered up and grounding connected. The on-site TCU engineer is in contact with the Integration operator, and check for any existing RBS alarms. Integration Engineer is available for RBS HW Data configuration in BSC. Site configuration data is available. PC equipped with telnet (Putty/Winfiol) and Ethernet ports are available with Firewall turned OFF. Console cable (straight Ethernet cable) should be available to make connection between TCU and PC. MUX end ports are available as plan and configured. Software on RBS and BSC should be 73F.

Work process The basic overview for Abis over IP can be shown as below:

Public 3 (10)


No.


Checked

Ogün SIY

3.1

Date

Rev

2013-12-26

PA1

Reference

HW Introduction The equipment consists of No Fan 4 E1/T1 ports (each port supports 2 E1) 4 Ethernet100/1000 Base-T ports 4 Ethernet100/1000 SFP ports One Clock port for GPS connection

Public 4 (10)


No.


Checked

Ogün SIY

3.2

Date

Rev

2013-12-26

PA1

Reference

Local Connection

Connect an Ethernet (RJ45) cable between LMT port on the TCU and the PC.

Local access is achieved through the Console port, using a PC equipped with a Local access is achieved through the Console port, using a PC equipped with a Telnet client. To establish contact between the local terminal and the TCU, configure your local terminal IP address to be on the same subnet as the SIU (Computer IP @ set manually to 192.168.1.X/24 and GW 192.168.1.1/24)

Public 5 (10)


No.


Ogün SIY

Checked

Date

Rev

2013-12-26

PA1

Reference

SET COMPUTER IP TO: 192.168.1.2 255.255.255.0 192.168.1.1

Note: For PC with windows Vista Operating system, do not forget to deactivate the firewall before running the telnet. Then, Launch a Telnet connection to TCU as below Note: SIU IP address is 192.168.1.1

Public 6 (10)


No.


Checked

Ogün SIY

Date

Rev

2013-12-26

PA1

Reference

, then enter the following data: login: admin password: hidden The screen below will pop up:

3.3

Load SIU configuration script As per the Design, script will be made by product configuration team. Here is an example script to be loaded.

T1492 SIU Script .txt

T1494 SIU Script .txt

Each command in the script should be run step by step. OSmon> starttransaction trans1 OperationSucceeded OSmon> setMOAttribute trans1 STN=0 STN_Name T1492

Public 7 (10)


No.


Checked

Ogün SIY

Date

Rev

2013-12-26

PA1

Reference

OperationSucceeded OSmon> setMOAttribute trans1 STN=0 wakeUpRegistration 10.133.78.106 OperationSucceeded OSmon> setMOattribute trans1 STN=0 systemClockTimeServer 10.135.14.253 OperationSucceeded ……………………… ……………………… ………………………

OSmon> checkconsistency trans1 consistent OSmon> commit trans1 forcedcommit Note: The TCU will restart automatically after this command. Please note that you have to reconnect to node. OSmon> endtransaction trans1 OperationSucceeded

3.4

Modify/Verify RBS IDB Transmission parameters need to be defined in the IDB When changing BTS transmission from normal E1 to Abis over IP by connecting a TCU, one important step is modify/verify the IDB to have correct transmission definition. Save a copy of present IDB (TDM mode) on laptop in case process need to be reverted back. 1. With OMT (50L), On the OMT system view right click the transmission box and choose “Define” transmission.

Public 8 (10)


No.


Checked

Ogün SIY

Date

Rev

2013-12-26

PA1

Reference

2. Set STN equipment to "SIU" 3. set CRC-4 to “Activated” 4. Set receiver sensitivity to "short haul" 5. Set appropriate PCM sync as per Super channel plan ( SC0- Port A, SC1 – Port B , SC2 – Port C , SC3 – Port D ) 6. click OK See figure below.

Public 9 (10)


No.


Checked

Ogün SIY

Date

Rev

2013-12-26

PA1

Reference

NOTE: If the settings are as above do not change anything.

3.5

RBS TCU Connection

RBS and DUG connection should be done between ET ports. The ETA port in the first DUG should be connected to ETA port on the TCU. And the ETA port in the second DUG should be connected to ETA port on the TCU. Each ET ports support 2E1s. If 4E1 used per DUG then, The ETA port in the first DUG is to be connected to ETA on TCU, ETB port in the first DUG is to be connected to ETB on TCU. And the ETA port in the second DUG is to be connected to ETC on TCU; ETB port in the second DUG is to be connected to ETD on TCU. The Connection towards TN has to be done via TN_A port with a straight (RJ45) cable.

Public 10 (10)


No.


Checked

Ogün SIY

3.6

Date

Rev

2013-12-26

PA1

Reference

Troubleshooting a. Check physical links to the transport network are up. b. If using Ethernet transport, verify that Ethernet Port TN_A is enabled, TN_A LED should be blinking c. If using E1 transport, verify that all E1 ports are enabled. If there are 2 E1s connected, the leds on E1/T1 Port ETA should be on Note: The Ethernet ports towards the TN will not be enabled until after the RBS is integrated. d. Check alarms "getalarmlist" Note: The TCU should be fault free. e. ping PGW IP address in configuration file to verify that BSC is reachable "ping "PGW IP Address""

TCU Integration MOP

Recommend Documents