You are on page 1of 44

Rehosting GSM BTS Sites

DN98908338 Issue 5-0 en

Nokia Corporation Nokia Proprietary and Confidential

1 (44)

Rehosting GSM BTS Sites

The information in this documentation is subject to change without notice and describes only the product defined in the introduction of this documentation. This documentation is intended for the use of Nokia's customers only for the purposes of the agreement under which the documentation is submitted, and no part of it may be reproduced or transmitted in any form or means without the prior written permission of Nokia. The documentation has been prepared to be used by professional and properly trained personnel, and the customer assumes full responsibility when using it. Nokia welcomes customer comments as part of the process of continuous development and improvement of the documentation. The information or statements given in this documentation concerning the suitability, capacity, or performance of the mentioned hardware or software products cannot be considered binding but shall be defined in the agreement made between Nokia and the customer. However, Nokia has made all reasonable efforts to ensure that the instructions contained in the documentation are adequate and free of material errors and omissions. Nokia will, if necessary, explain issues which may not be covered by the documentation. Nokia's liability for any errors in the documentation is limited to the documentary correction of errors. NOKIA WILL NOT BE RESPONSIBLE IN ANY EVENT FOR ERRORS IN THIS DOCUMENTATION OR FOR ANY DAMAGES, INCIDENTAL OR CONSEQUENTIAL (INCLUDING MONETARY LOSSES), that might arise from the use of this documentation or the information in it. This documentation and the product it describes are considered protected by copyright according to the applicable laws. NOKIA logo is a registered trademark of Nokia Corporation. Other product names mentioned in this documentation may be trademarks of their respective companies, and they are mentioned for identification purposes only. Copyright Nokia Corporation 2005. All rights reserved.

2 (44)

Nokia Corporation Nokia Proprietary and Confidential

DN98908338 Issue 5-0 en

Contents
Contents 3 List of figures 5 1 1.1 1.1.1 1.1.2 2 3 4 5 5.1 5.2 5.3 5.4 5.5 5.6 5.7 5.8 5.9 5.10 5.11 6 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 7 7.1 7.2 7.3 7.4 About this document 7 Prerequisites 7 Functionality used in this operation 7 Other prerequisites 8 Changes in NetAct documentation 11 NetAct compatibility and capacity information 13 Rehosting a GSM BTS site 15 Preparing the rehost operation 17 Overview of the preparation phase 17 Informing customer services 19 Checking the transmission polling method 19 Stopping TRX loop tests 19 Creating a sheet 19 Creating and unlocking LAPD links 20 Creating DAPs 20 Creating managed objects and radio network parameters 21 Creating views 23 Attaching and activating the BCF software 23 Activating the BCF hardware database 24 Implementing the rehost operation 25 Overview of the implementation phase 25 Stopping measurements 27 Locking old managed objects 27 Manually switching physical links 27 Updating CI and LAC references 27 Locking, recreating, and unlocking BTSs in the MSC 29 Swapping LACs 30 Moving Site, Antenna and additional object information 30 Unlocking new managed objects 31 Updating incoming ADJGs and template IDs 31 Updating the Optimizer database 32 Running consistency checks 32 Checking the state of the objects 32 Cleaning up 35 Overview of the clean-up phase 35 Deleting old sites and LAPD links from the network 36 Deleting old objects and views 36 Restarting measurement collection 37

DN98908338 Issue 5-0 en

Nokia Corporation Nokia Proprietary and Confidential

3 (44)

Rehosting GSM BTS Sites

7.5 7.6 8 9

Reactivating scheduled TRX loop tests 37 Checking performance 38 Reverting back to the old configuration 39 Where to find more information 41 Index 43

4 (44)

Nokia Corporation Nokia Proprietary and Confidential

DN98908338 Issue 5-0 en

List of figures
Figure 1. Figure 2. Figure 3. The preparation phase of rehosting a GSM BTS site 18 The implementation phase of rehosting a GSM BTS site 26 The clean-up phase of rehosting a GSM BTS site 35

DN98908338 Issue 5-0 en

Nokia Corporation Nokia Proprietary and Confidential

5 (44)

Rehosting GSM BTS Sites

6 (44)

Nokia Corporation Nokia Proprietary and Confidential

DN98908338 Issue 5-0 en

About this document

1
1.1

About this document


This document gives you an end-to-end Nokia NetAct system-level view on how to rehost BTS sites. When rehosting a BTS site to another BSC with the Splitting BSSs application, only a small number of parameters need to be defined for new objects under the target BSC; most of the parameters are copied from the old objects under the source BSC.

Prerequisites
This section lists the minimum requirements to enable you to complete site rehosting successfully. Read this section carefully to avoid unnecessary troubleshooting later.

1.1.1

Functionality used in this operation


The following Nokia NetAct functionality is used in this operation: Splitting BSSs Radio Network Manager Network Editor Administration of Measurements Scheduled TRX Loop Test Management Inter-NetAct Update CM Editor CM Operations Manager CM Analyser Network Element Software Configuration Manager Optimizer related script for updating tables in Optimizer

DN98908338 Issue 5-0 en

Nokia Corporation Nokia Proprietary and Confidential

7 (44)

Rehosting GSM BTS Sites

1.1.2

Other prerequisites
Ensure that the following prerequisites are met before starting to rehost any sites: The site cannot be moved to a BSC that is controlled by another Nokia NetAct. Initial BTS SW package must be defined. Target BSC, SGSN, and MSC versions must be greater than or equal to the source versions. There must be enough licences in the target BSC. The new BSC is integrated with NetAct, that is: ETs are installed. Remote MML connections are working. Fault and performance data can be collected from the BSC.

The ET (Exchange Terminal) for the BTS site(s) is installed and configured in the BSC. Identification numbers for the following have been allocated in the new BSC: BCF, BTS, and TRXs DAPs, LAPD links, PCM, TRX channels, and time slots

The transmission plan is ready. If you are managing Nokia MSCs, the LA must exist in the NetAct database. If external alarms are used, alarm text (TID objects) in each BSC need to be equal. If RF hopping is activated, MAL object must be created to the target. If BCCH Allocation lists are used, BAL objects must be created to the target. CF and DAC measurement collection is stopped.

If GPRS functionality is included, the following tasks must also be completed before beginning this procedure: SGSN parameters have been created. The Gb interface between the SGSN and the BSC has been configured. For more information about configuring the Gb interface, see Enabling GPRS in the GSM Radio Network.

8 (44)

Nokia Corporation Nokia Proprietary and Confidential

DN98908338 Issue 5-0 en

About this document

The GPRS capacity parameters have been defined. The LA and RA for the new site have been configured.

If EDGE functionality is included, the following tasks must be completed before beginning the procedure: DAP must be created to the target. EGPRS must be enabled in the target BTS. GPRS must be enabled.

If Location Services are included, the following tasks must be completed before beginning this procedure: LCSEs must be created in the source BSC. Needed co-ordinates must be planned. SMLC LCS control parameter must be set correctly.

If the Dynamic Frequency and Channel Allocation (DFCA) functionality is included, Splitting BSSs requires that the following objects have been created and have the same object IDs in the source and the target BSCs: DFCA MA Lists (MALDs) DFCA MA Unsynch List (MAL)

Note
Check from the target BSC that the used DFCA MA Unsynch List is the same as in the source BSC. If the used DFCA MA Unsynch List is different, the wrong list of frequencies is used when the BTS drops into the unsynch mode. There are two ways to activate DFCA: Direct: Splitting BSSs supports activating DFCA directly to the DFCA hopping mode. This is the fastest method. In this case, BSC is expected to send a warning DX message about possible radio interference. Indirect: It is also possible to activate DFCA with CM Editor but this is more time-consuming. You must disable DFCA in the source BSC before rehosting and enable it through off and standby modes in the target BSC.

If the IMSI Based Handover (IBHO) functionality is included, Splitting BSSs requires that the following objects have been created:

DN98908338 Issue 5-0 en

Nokia Corporation Nokia Proprietary and Confidential

9 (44)

Rehosting GSM BTS Sites

ANE (Authorised Networks) SG (Subscriber Group)

The following prerequisites should be taken care of before rehosting sites that are running under BSS Synchronization: An SMLC exists under the target BSC. There should not exist an LMUA object under the target BSC with the same ID as the object ID of the corresponding target master BCF.

10 (44)

Nokia Corporation Nokia Proprietary and Confidential

DN98908338 Issue 5-0 en

Changes in NetAct documentation

Changes in NetAct documentation


The information in this document relates to OSS4 releases and deliveries. This document is compatible with the latest release of NetAct and covers the necessary release specific updates. For information on the release specific changes in this document and the related software, see Changes in NetAct Documentation.

Note
If you are using a PDF print-out of this document and also need the change information, please print out the Changes in NetAct Documentation (dn03511086) document.

DN98908338 Issue 5-0 en

Nokia Corporation Nokia Proprietary and Confidential

11 (44)

Rehosting GSM BTS Sites

12 (44)

Nokia Corporation Nokia Proprietary and Confidential

DN98908338 Issue 5-0 en

NetAct compatibility and capacity information

NetAct compatibility and capacity information


For information on NetAct system and capacity, and the compatibility between NetAct and network element releases, see the NetAct Compatibility and Capacity Information document.

DN98908338 Issue 5-0 en

Nokia Corporation Nokia Proprietary and Confidential

13 (44)

Rehosting GSM BTS Sites

14 (44)

Nokia Corporation Nokia Proprietary and Confidential

DN98908338 Issue 5-0 en

Rehosting a GSM BTS site

Rehosting a GSM BTS site


Rehosting a BTS site means changing the BSC that controls the site. Usually, BTS rehosting is carried out for one of the following reasons: The new BSC has been commissioned and capacity needs to be distributed to that BSC. To build capacity, for example, by upgrading the TRX configuration from 2+2+2 to 3+3+3, but the capacity of the current controlling BSC has been reached. A crucial area of the network, for example a major airport, conference centre or shopping centre, is covered by cells that are all under one BSC. To avoid cell outage in the unlikely event of a BSC failure, the coverage should be split to two BSCs.

The procedure of rehosting GSM BTS sites is divided into three phases. For instructions on the preparation phase, see 5 Preparing the rehost operation. For instructions on the implementation phase, see 6 Implementing the rehost operation. For instructions on the clean-up phase, see 7 Cleaning up.

DN98908338 Issue 5-0 en

Nokia Corporation Nokia Proprietary and Confidential

15 (44)

Rehosting GSM BTS Sites

16 (44)

Nokia Corporation Nokia Proprietary and Confidential

DN98908338 Issue 5-0 en

Preparing the rehost operation

Preparing the rehost operation


The following prerequisites must be met before starting the preparation: In the case of a new target BSC, all the integration tasks have been completed. The Exchange Terminal has been installed and configured in the target BSC. Information on managed object IDs, names for the BCFs and TRXs, CI and LAC information, and a transmission plan for the new sites are available.

5.1

Overview of the preparation phase


The following flowchart gives you an overview of the preparation phase as well as the tools that you can use to do the various steps.

DN98908338 Issue 5-0 en

Nokia Corporation Nokia Proprietary and Confidential

17 (44)

Rehosting GSM BTS Sites

Start

Inform customer services

Check transmission polling method

Scheduled TRX Loop Test Mgmt

Stop TRX loop tests

Splitting BSSs

Create a sheet

Splitting BSSs

Create and unlock LAPD links

Splitting BSSs

Create DAPs

Splitting BSSs

Create managed objects and radio network parameters

Splitting BSSs NE Software Configuration Manager MML

Create views

Attach and activate the BCF software

Activate the BCF hardware database

End

Figure 1.

The preparation phase of rehosting a GSM BTS site

18 (44)

Nokia Corporation Nokia Proprietary and Confidential

DN98908338 Issue 5-0 en

Preparing the rehost operation

5.2

Informing customer services


During rehosting, services will be disrupted on the rehosted site and handovers to the site will not succeed. It is advisable to inform your customer services organisation of possible disruptions to the quality of service.

Note
If you have the optional Maintenance Mode feature, you can use it to set network elements to the maintenance state. This reduces load in the system by blocking unnecessary alarms coming to the monitoring tools and the database. Maintenance Mode is started from the Top-level User Interface. For more information, see Handling the maintenance mode in Top-level User Interface Help.

5.3

Checking the transmission polling method


The transmission polling method (alarm collection via the Q1 interface) must already be defined and set up in the BSC at this stage. You can either use BSC or BTS polling of transmission equipment.

5.4

Stopping TRX loop tests


Stop the TRX loop tests using Scheduled TRX Loop Test Management. You should stop all TRX loop tests on the sites to be rehosted. You can do this by either stopping the test completely or modifying the test to omit the rehosted sites. For more information, see Scheduled TRX Loop Test Help.

5.5

Creating a sheet
Creating a sheet means creating an ASCII file with a pre-defined set of fields. For instructions on how to perform this step, see Creating a sheet in Splitting BSSs Help. The sheet can be created with Splitting BSS application or with any text or table editor that is capable of handling ASCII files. ASCII files must be saved as semicolon-separated files. When creating a sheet:

DN98908338 Issue 5-0 en

Nokia Corporation Nokia Proprietary and Confidential

19 (44)

Rehosting GSM BTS Sites

Fill in the Target BTSM Network Name and ID field. If RF hopping is activated, fill in MAL ID, MAIO Offset, and MAIO Steps to the sheet. They are not automatically copied from the source. If BCCH allocation lists are used, fill in the ID for the BAL column in the sheet. If GPRS is activated, enter Y (yes) to the GPRS enabled column. Add also the correct RAC value. If GPRS and EGPRS are activated, fill in the GPRS columns and EGPRS columns. Column EGPRS enabled should be Y (yes) and DAP data should be inserted.

If you do not have a sheet ready, the BCF objects of the sites to be rehosted can be dropped to the application and the parameter values entered for the new objects in the application UI. When you are rehosting a Multi-BCF site, the whole segment is copied to the target BSC. This means that segment split is not possible. Also, you must give the master BTS a segment ID that does not already exist in the target BSC. If same CI and LAC are used during the rehosting and Swap LACs is not used, remember to use the same RAC value also in the old and new BTS in the sheet.

5.6

Creating and unlocking LAPD links


Create and unlock LAPD links. For instructions, see Creating and unlocking LAPD links in Splitting BSSs Help.

5.7

Creating DAPs
For instructions on how to perform this step, see Creating DAPs in Splitting BSSs Help.

20 (44)

Nokia Corporation Nokia Proprietary and Confidential

DN98908338 Issue 5-0 en

Preparing the rehost operation

5.8

Creating managed objects and radio network parameters


Create managed objects and radio network parameters. For instructions, see Creating managed objects when splitting BSSs in Splitting BSSs Help.

Note
MR data will be copied from the old objects to the new objects during Send to Network. If MR needs to be changed, that must be done with Network Editor after Send to Network. In case you use the same CI/LAC in the source and target BTS, it is not possible to have different RAC in the source and target BTS. Use a dummy LAC if you must use different RACs in the source and target BTSs (for example, if you have GPRS enabled in the target BTS).

Note
In Splitting BSSs, dummy LAC means any non-operational LAC object. In case of EGPRS, EGPRS and GPRS options in the BSC should be enabled and the attached BTS and TRX software should support EGPRS. The DAP related columns present in the new side of the sheet contains the DAP data which is either newly created (using the Create DAPs operation) or already existing and will be associated with the respective TRX. If EGPRS should be enabled in the target, mark the column for EGPRS as Y (yes). The Location Services are supported by the Splitting BSSs application. If you want to use SEG/BTS for the Cell ID + TA and U-TDOA location methods you must create LCS elements for those.

Note
The U-TDOA positioning method is used only for the US emergency call positioning (E911). U-TDOA is only used in S11 and S11.5 BSCs. For lower BSC versions, only CITA method is available. The following changes are done automatically by Splitting BSSs if Location Services are used:

DN98908338 Issue 5-0 en

Nokia Corporation Nokia Proprietary and Confidential

21 (44)

Rehosting GSM BTS Sites

If the source BSC has Location Services related child managed objects, they will be rehosted to the target BSC. They are created to the target as mentioned below. If the source BTS has an LCSE and an LCSE with the given CI/LAC is not present in the target BSC, an LCSE is created for the new segment. If the LCSE with the given CI and LAC is already present in the target, the LCSE is not created in the target and the neighbours list will not be updated. You must fill in the neighbours list manually. Because of this, during the rehost, it is not recommended that you create LCS elements with a given CI and LAC in the target before the split is performed. LCSE element neighbour list in the target LCSE is created on the basis of the source LCSE: the list will be exactly the same as the source LCSE. All the LCSEs which are present in the neighbour list and missing in the target BSC are created as alien LCS elements to the target BSC. If the alien LCSEs are already present in the target BSC, they are not created. (Only valid when using the Cell ID + TA based location method.)

For more information on Location Services, see Activating Location Services.

Note
If DFCA is used, there are two ways to activate it: Direct: Splitting BSSs supports activating DFCA directly to the DFCA hopping mode. This is the fastest method. In this case, BSC is expected to send a warning DX message about possible radio interference. Indirect: It is also possible to activate DFCA with CM Editor but this is more time-consuming. You must disable DFCA in the source BSC before rehosting and enable it through off and standby modes in the target BSC.

The following changes are done automatically by the Splitting BSSs application while rehosting the sites that are running under BSS Synchronization. For all master BCFs in the source side if Clock Source is LMU and Synch Enabled is True in the source BCF: The master BCFs are created in the target side with Clock Source as LMU and Synch Enabled as True. LMUA objects are created under the target BSC with the following parameters:

22 (44)

Nokia Corporation Nokia Proprietary and Confidential

DN98908338 Issue 5-0 en

Preparing the rehost operation

The LMUA object with the same ID as that of the target Master BCF ID is created in the target BSC. The TRE ID parameter of LMUA will be one and the value of LMU Usage parameter will be Synch.

Note
If the LMUA object with this ID already exists in the target BSC, an error is thrown. In such a situation, corresponding target master BCF will not be made Synch Enabled. The Measured LCSE and Reference LCSEs of LMUA will be emptied.

5.9

Creating views
Create BCF views for the new sites in the target BSC using Splitting BSSs. For instructions, see Creating BCF views in Splitting BSSs Help. For information on how to manage views, see Building and Maintaining Views.

5.10

Attaching and activating the BCF software


Note
If an initial software package has been defined in the BSC, you do not need to activate the BCF software. BCF software can be activated by using Network Element Software Configuration Manager.

To activate BCF software using Network Element Software Configuration Manager


1. 2. Start Network Element Software Configuration Manager by clicking the icon in Application Manager. Check that the correct software package is available in SW Archive. If the correct software package is not available, import it using BCF Software Archives.

DN98908338 Issue 5-0 en

Nokia Corporation Nokia Proprietary and Confidential

23 (44)

Rehosting GSM BTS Sites

3.

Activate the software. For instructions, see Importing software and downloading it to a managed object in Network Element Software Configuration Manager Help.

For more information on BCF software handling in the Nokia BSC, see the functional descriptions in the BSC documentation.

5.11

Activating the BCF hardware database


Note
You only need to activate the BCF hardware database if you are rehosting a 2nd Generation or TalkFamily BTS. If you are not rehosting a 2nd Generation or TalkFamily BTS, move to 6 Implementing the rehost operation. The BTS hardware database must be activated using MML.

To activate the BCF hardware database


1. 2. 3. 4.
ZEVL;

Start the Top-level User Interface if it is not already open. Open a view containing the parent BSC of the rehosted site. Begin an MML session to the BSC. List the hardware databases currently available:

5.

If the required BCF hardware database does not exist, upload and create the hardware database:

ZEVU:<BCF_identity>:<file_name,file_extension,database_id>:<upload_mode>; ZEVC:<database_id>:<file_name>,<file_extension>;

6.

Attach the hardware database to the BCF:

ZEVA:<BCF_identity>:<database_id>;

7.

Activate the BCF hardware database:

ZEVV:<BCF_identity>:<database_status>:<activation_mode>;

24 (44)

Nokia Corporation Nokia Proprietary and Confidential

DN98908338 Issue 5-0 en

Implementing the rehost operation

6
6.1

Implementing the rehost operation


This chapter provides instructions for implementing the rehost operation. Note that you can bring new sites into operation group by group (PCM by PCM, for example), or you can bring all the objects involved in the split operation into use at once.

Overview of the implementation phase


The following flowchart gives you an overview of the implementation phase as well as the tools that you can use to do the various steps.

DN98908338 Issue 5-0 en

Nokia Corporation Nokia Proprietary and Confidential

25 (44)

Rehosting GSM BTS Sites

Start Administration of Measurements Splitting BSSs

Stop measurements

Lock old managed objects

Manually switch physical links

Splitting BSSs

Update CI and LAC references

Splitting BSSs

Lock, recreate, and unlock BTSs in the MSC Swap LACs

Splitting BSSs

Splitting BSSs Splitting BSSs, CM Editor CM Analyser, CM Operations Manager External script Inter-NetAct Update Radio Network Manager

Move Site, Antenna and additional object information Unlock new managed objects

Update incoming ADJGs and template IDs Update the Optimizer database

Run consistency checks

Check the state of the objects

End

Figure 2.

The implementation phase of rehosting a GSM BTS site

26 (44)

Nokia Corporation Nokia Proprietary and Confidential

DN98908338 Issue 5-0 en

Implementing the rehost operation

6.2

Stopping measurements
Stop the BSC measurements using Administration of Measurements. This applies only to the BSCs that are part of the rehosting. It is recommended that you stop the measurements immediately. For more information on how to stop measurements, see Administration of Measurements Help. If stopping measurements is needed, you also need to stop MO Upload cron tasks and take BSC SW backup before proceeding with activation. For more information, see Uploading Managed Objects Help.

6.3

Locking old managed objects


Lock the old managed objects at the BSS level with the Splitting BSSs application. For instructions, see Locking managed objects in the BSC in Splitting BSSs Help.

6.4

Manually switching physical links


BTS Site cable must be physically switched from BSC to another BSC. Swapping E1/T1 must be done when disconnecting a BTS site from its BSC and connecting it to a new BSC. The new site is usually unlocked immediately after swapping E1/T1 and verified by MML.

6.5

Updating CI and LAC references


For instructions on how to perform this step, see Updating the CI and LAC references in rehosted sites in Splitting BSSs Help. During this step, the incoming adjacencies are updated, the C/I-based handover parameters are updated, and the interfering cells (IUO) information is updated in the NetAct and BSC databases. During the operation, the old ADCE objects pointing to some other BTSs are deleted and new ADCE objects are created pointing to the new rehosted BTS.

DN98908338 Issue 5-0 en

Nokia Corporation Nokia Proprietary and Confidential

27 (44)

Rehosting GSM BTS Sites

S11 and S11.5 sites can have inter-PLMN adjacencies and they are redirected as any other incoming adjacencies from the foreign BTS.

Note
If DFCA is used and the target BSC gets new LAC values, SPC objects must be updated in adjacent BSCs. The following changes are done automatically by Splitting BSSs, if Location Services are used: The alien LCS elements in the target, which are pointing to the source site being rehosted are deleted. All other alien LCS elements that are created in this phase and point to the source sites not being rehosted are not deleted. The LCSE neighbours list is updated properly to point to the correct LCSEs if the LCSEs defined in the neighbours list are also being rehosted. (Only valid when using the Cell ID + TA based location method.) Alien LCSEs under other BSCs, pointing to the source BTS being rehosted will point to the BTS in the target.

For more information on Location Services, see Activating Location Services.

28 (44)

Nokia Corporation Nokia Proprietary and Confidential

DN98908338 Issue 5-0 en

Implementing the rehost operation

6.6

Locking, recreating, and unlocking BTSs in the MSC


Note
This step is needed only if Nokia MSC is available.

Note
This note is for RNW Manager users! When doing rehosting with the same CI and LAC without using the Swap LACs operation in BSS Split, RNW Manager must be used properly. After the BTSMs have been recreated, they are no longer connected to the old BTS but to the new BTS. If you are deleting the old sites before using RNW Manger there will be no problems. But if RNW Manager is used before the old sites have been deleted, be aware that when selecting the old BTS, RNW Manager is asking for a confirmation about establishing the connection between BTSM and BTS. This confirmation must be cancelled otherwise, the BTSM will again be connected to the old BTS and then BTSM will be deleted when deleting old sites. When the Cell ID (CI) of the BTS changes: The BTS in the MSC will always be deleted in the source before it is created again in the target.

When the LAC of the BTS changes: The BTS in the MSC will first be created in the target MSC and later deleted from the source MSC.

To lock, recreate, and unlock BTSs using Splitting BSSs


1. 2. 3. Lock the desired objects in the old sites. For instructions, see Locking BTSs in the MSC in Splitting BSSs Help. Recreate BTSs in the MSC. For instructions, see Recreating BTS in MSC objects when splitting BSSs in Splitting BSSs Help. Unlock the new BTS sites created in the MSC. For instructions, see Unlocking BTSs in the MSC in Splitting BSSs Help.

DN98908338 Issue 5-0 en

Nokia Corporation Nokia Proprietary and Confidential

29 (44)

Rehosting GSM BTS Sites

6.7

Swapping LACs
If you want to avoid adjacencies pointing to wrong BTSs in the BSC, you can use a dummy LAC when creating a new BTS, and then use the Swap LACs command to swap the dummy LAC with the old LAC.

Note
In Splitting BSSs, dummy LAC means any non-operational LAC object and dummy RA any non-operational RA object. If you have GPRS enabled in the target BSC, you need to use a dummy LAC and a dummy value should be given for the RAC also. You need a dummy RA in the source and target BSC and a real RA with a real connection to SGSN. During the Swap LAC operation, the LAC values are swapped. For instructions, see Swapping old and new LACs in Splitting BSSs Help. The following changes are done automatically by Splitting BSSs if Location services are used: The LCSEs for the sites involved in the swapping of LACs in the target BSC are updated during this operation. LCS element IDs will be changed to point to the correct LAC. The LCS element neighbour list that contains the CI and LAC of this LCSE is also updated with the swapped LAC. The LCSEs associated with old sites are updated as alien LCSEs pointing to the corresponding BTSs in the target BSC.

For more information on Location Services, see Activating Location Services.

Note
If DFCA is used and the target BSC gets new LAC values, SPC objects must be updated in adjacent BSCs.

6.8

Moving Site, Antenna and additional object information


Move the Site, Antenna and additional object information from the old sites to the new sites using Splitting BSSs. For instructions, see Moving Site, Antenna and additional object information when splitting BSSs in Splitting BSSs Help.

30 (44)

Nokia Corporation Nokia Proprietary and Confidential

DN98908338 Issue 5-0 en

Implementing the rehost operation

6.9

Unlocking new managed objects


Unlock the new managed objects created at the BSS level using Splitting BSSs. For instructions, see Unlocking managed objects in the BSC in Splitting BSSs Help. If DFCA is enabled directly, BSC is expected to send a warning DX message about possible radio interference when unlocking the BTS object. In case of indirect DFCA enabling, after the standby mode DFCA can be enabled with CM Editor.

6.10

Updating incoming ADJGs and template IDs


Since the Splitting BSSs application does not automatically update incoming ADJGs and template IDs, the update must be done separately according to the following instructions.

To update incoming ADJGs and template IDs


1. Save the sheet, if not already saved, to ensure that the
/etc/opt/nokiaoss/configurator/rac/regbss/sheets

directory contains the newly created sheet having the rehosted objects defined. 2. Update BCF, BTS, and TRX template IDs and Target Cell DN of incoming ADJGs to NetAct database by running the updIncomingADJG.pl script with the following command:

/opt/nokiaoss/configurator/rac/regbss/bin/updIncomingADJG.pl /etc/opt/nokiaoss/configurator/rac/regbss/sheets/<sheet>

where <sheet> is the name of the sheet you are using in Splitting BSSs and have saved in step 1. 3. Optional: Check that BCF, BTS, and TRX template IDs are correctly updated to the NetAct database by using the sheet from /etc/opt/nokiaoss/configurator/rac/regbss/sheets and running the updIncomingADJG.pl script with the -c option using the following command:

/opt/nokiaoss/configurator/rac/regbss/bin/updIncomingADJG.pl /etc/opt/nokiaoss/configurator/rac/regbss/sheets/<sheet> -c

DN98908338 Issue 5-0 en

Nokia Corporation Nokia Proprietary and Confidential

31 (44)

Rehosting GSM BTS Sites

where <sheet> is the name of the sheet you are using in Splitting BSSs and have saved in step 1. 4. Using CM Analyser, create a correction plan to correct the parameters of the incoming ADJGs in the network by running the Nokia.OSS3_1ed2fn1_3g.AdjgIdParams rule against all the RNCs that have outgoing adjacencies (ADJG) to the rehosted BTSs. You can find out the involved RNCs using CM Editor by selecting all the incoming ADJGs of the new BTSs and check the RNC from the Managed Object DN. 5. Using CM Operations Manager, select the Prepare Plan option and activate the plan to the network. For instructions, see Provisioning plans in CM Operations Manager Help.

6.11

Updating the Optimizer database


If you have Optimizer installed in your NetAct system, you must update the Optimizer database after you have created the new BTSs and before you delete the old BTSs. For instructions, see Updating Optimizer database in Splitting BSSs Help.

6.12

Running consistency checks


If the site has incoming inter-region adjacencies (the source cell is located in another regional NetAct), make sure that the operators in other regional NetAct clusters update the CI and LAC of the moved BTSs. Run Inter-NetAct Update to check whether there are inconsistencies in incoming adjacencies. Follow the on-screen instructions to generate a report. Inform the operators in other regional NetAct(s) about the changes in the CI and LAC of the BTSs under rehosted BCFs.

6.13

Checking the state of the objects


Check the state of the managed objects using Radio Network Manager to see more information than provided in Splitting BSSs.

32 (44)

Nokia Corporation Nokia Proprietary and Confidential

DN98908338 Issue 5-0 en

Implementing the rehost operation

To check the state of the managed objects


1. 2. 3. Start Radio Network Manager by clicking the icon in Application Manager. In the main window, select the rehosted BCF. Click the ZEEI button to see that the objects have been unlocked. The ZEEI dialog opens. The dialog shows the administrative and operational state of the site. The administrative state can be: Unlocked (U) Locked (L)

The operational state can be: Blocked by user (BL-USR) Working (WO)

For more information, see Radio Network Manager Help.

DN98908338 Issue 5-0 en

Nokia Corporation Nokia Proprietary and Confidential

33 (44)

Rehosting GSM BTS Sites

34 (44)

Nokia Corporation Nokia Proprietary and Confidential

DN98908338 Issue 5-0 en

Cleaning up

7
7.1

Cleaning up
This chapter describes the clean-up operations related to rehosting a GSM BTS site.

Overview of the clean-up phase


The following flowchart gives you an overview of the clean-up phase as well as the tools that you can use to do the various steps.

Start Delete old sites and LAPD links from the network

Splitting BSSs

Network Editor

Delete old objects and views

Administration of Measurements Scheduled TRX Loop Test Mgmt

Restart measurement collection

Reactivate scheduled TRX loop tests

Check performance

End

Figure 3.

The clean-up phase of rehosting a GSM BTS site

DN98908338 Issue 5-0 en

Nokia Corporation Nokia Proprietary and Confidential

35 (44)

Rehosting GSM BTS Sites

7.2

Deleting old sites and LAPD links from the network


LAPD links must be locked before they are deleted from the network.

To delete old sites and LAPD links


1. Delete the old sites from the network. For instructions, see Deleting old sites when splitting BSSs in Splitting BSSs Help.

Note
If you want to delete also old LAPD links, do not close the UI after deleting old sites. 2. Delete the old LAPD links from the network. For instructions, see Deleting LAPD links in Splitting BSSs Help.

You need approximately 24 hours of performance data from the new site before you can make the decision whether to delete the old sites. The following changes are automatically done by Splitting BSSs if Location Services are used: When the Delete LCSEs check box is checked, the LCSEs associated with the BTS in the source BSC will be deleted. If the Delete LCSEs check box is not checked during the deletion, the LCSEs associated with the BTS in the source BSC are changed to alien LCSEs pointing to the corresponding BTS in the target BSC. If the BCF being deleted in the source has an attached LMU equipment, it cannot be deleted. It is required that this LMU equipment is detached and connected to another BCF before deleting the old sites.

For more information on Location Services, see Activating Location Services.

7.3

Deleting old objects and views


Delete the old objects and views in the NetAct database by using Network Editor.

36 (44)

Nokia Corporation Nokia Proprietary and Confidential

DN98908338 Issue 5-0 en

Cleaning up

To delete old objects and views


1. 2. Open Network Editor (Utils System Mgmt Network Editor...). To delete a managed object, select the BCF in the view and click Delete... on the objects pop-up menu; remember to select Delete also from DB button. Also remember to delete any corresponding BTSM objects. To delete a view, click File Delete... in the main window and select the view to be deleted. Run RAC doctor script 002, which deletes the plans attached to the deleted old site.

3. 4.

In case the BSC becomes empty, you can delete the BSC object from the NetAct database by using the following instructions.

To delete the BSC object from the NetAct database


1. Set the BSC object as non-operational with Network Editor. Note that if the BSC object has any child objects, all the child objects must be non-operational as well. 2. Delete the BSC object with Network Editor.

7.4

Restarting measurement collection


Restart the measurements on the BSC using Administration of Measurements. For more information on how to restart measurements, see Administration of Measurements Help.

7.5

Reactivating scheduled TRX loop tests


Start the TRX loop tests using Scheduled TRX Loop Test Management. You should start all TRX loop tests that you stopped earlier. For more information, see Scheduled TRX Loop Test Help.

DN98908338 Issue 5-0 en

Nokia Corporation Nokia Proprietary and Confidential

37 (44)

Rehosting GSM BTS Sites

7.6

Checking performance
After completing the rehosting, you should take a look at the following statistics the next day to ensure that the site is performing normally. Call set up failure Handover failures Dropped call ratio Mobile originated calls and mobile terminated calls on the BCCH TRX and SDCCH TRX.

38 (44)

Nokia Corporation Nokia Proprietary and Confidential

DN98908338 Issue 5-0 en

Reverting back to the old configuration

Reverting back to the old configuration


There are different possibilities for reverting back to the old configuration: Before updating CI and LAC: Switch manually physical links back to the old configuration. After updating CI and LAC: Switch manually physical links back to the old configuration and recreate incoming ADCEs manually using CM Editor. Alternatively, you can create a new Splitting BSSs sheet with inverted old and new sites and revert back by rehosting site back and recreating ADCEs.

DN98908338 Issue 5-0 en

Nokia Corporation Nokia Proprietary and Confidential

39 (44)

Rehosting GSM BTS Sites

40 (44)

Nokia Corporation Nokia Proprietary and Confidential

DN98908338 Issue 5-0 en

Where to find more information

Where to find more information


For more information, refer to the following documents. For more information on Nokias radio network management tools and the concepts associated with managing you radio network, see Radio Access Configurator Principles. For more information on Nokias software and hardware configuration management tools and the concepts and tasks associated with configuration management, see System Administration Principles.

DN98908338 Issue 5-0 en

Nokia Corporation Nokia Proprietary and Confidential

41 (44)

Rehosting GSM BTS Sites

42 (44)

Nokia Corporation Nokia Proprietary and Confidential

DN98908338 Issue 5-0 en

Index A
activating BCF hardware database 24 BCF software 23 adjacencies consistency checks 32 using a dummy LAC 30 Antenna information 30

L
LAPD links 8, 20, 36 Location Services 9, 21, 28, locking old managed objects 27 30, 36

M
Maintenance Mode 19 manually switching physical links measurements restarting 37 stopping 27 moving Antenna information 30 Site information 30 MSC 8, 29 27

B
BCCH 8, 20, 38 BCF hardware database 24 BTSM 20, 29, 37

C
checking performance 38 the state of the objects

N
32 Nokia MSC locking BTSs 29 recreating BTSs 29

D
DAP 8, 9, 20, 21 deleting old LAPD links 36 old sites 36 views 36 DFCA 9, 22 dummy LAC 21, 30

O
old sites deleting 36 LCSEs 30 moving Site, Antenna and additional information. 30

E
E1/T1 27 EDGE 9 EGPRS 20 ETs 8 Exchange Terminal

P
prerequisites 7, 17

R
8, 17 remote MML 8 RF hopping 8 RNW Manager 29 running consistency checks

G
GPRS 8, 21, 30

32

S I
IBHO 9 implementation 25 inter -region adjacencies SGSN 8, 30 Site information 30 SPC 28, 30 SW Archive 23

32

DN98908338 Issue 5-0 en

Nokia Corporation Nokia Proprietary and Confidential

43 (44)

Rehosting GSM BTS Sites

T
TalkFamily BTS 24 template IDs 31 transmission plan 8, 17 polling 19 TRX channels 8 configuration 15 identification numbers 8 loop tests 7, 19, 37 names 17

U
unlocking new managed objects 31 updating CI and LAC references 27 incoming ADJGs and template IDs

31

V
views creating deleting 23 36

44 (44)

Nokia Corporation Nokia Proprietary and Confidential

DN98908338 Issue 5-0 en