rehostinggsmbtssites1pdf-pdf-free

NetAct™
16
Rehosting GSM BTS Sites
DN98908338
Issue: 2-1
Rehosting GSM BTS Sites
DN98908338 2-1
Disclaimer
The information in this document applies solely to the hardware/software product (“Product”) specified herein, and only as specified herein.
This document is intended for use by Nokia Solutions and Networks' customers (“You”) only, and it may not be used except for the purposes
defined in the agreement between You and Nokia Solutions and Networks (“Agreement”) under which this document is distributed. No part of
this document may be used, copied, reproduced, modified or transmitted in any form or means without the prior written permission of Nokia
Solutions and Networks. If you have not entered into an Agreement applicable to the Product, or if that Agreement has expired or has been
terminated, You may not use this document in any manner and You are obliged to return it to Nokia Solutions and Networks and destroy or
delete any copies thereof.
The document has been prepared to be used by professional and properly trained personnel, and You assume full responsibility when
using it. Nokia Solutions and Networks welcome Your comments as part of the process of continuous development and improvement of the
documentation.
This document and its contents are provided as a convenience to You. Any information or statements concerning the suitability, capacity,
fitness for purpose or performance of the Product are given solely on an “as is” and “as available” basis in this document, and Nokia
Solutions and Networks reserves the right to change any such information and statements without notice. Nokia Solutions and Networks has
made all reasonable efforts to ensure that the content of this document is adequate and free of material errors and omissions, and Nokia
Solutions and Networks will correct errors that You identify in this document. But, Nokia Solutions and Networks' total liability for any errors in
the document is strictly limited to the correction of such error(s). Nokia Solutions and Networks does not warrant that the use of the software
in the Product will be uninterrupted or error-free.
N O WA RRA NT Y O F AN Y KI ND , EI T HER EXPR ES S OR I M P L I E D , I N C L U D I N G B U T N O T L I M I T E D TO A N Y
WARR ANT Y OF AVA IL ABI LI T Y, AC CU RAC Y, R EL I A B I L IT Y, T I T L E , N O N - I N F R I N G E M E N T, M E R C H A N TA B I L I TY O R
FITNESS F OR A PA RT I CULA R PU RPO SE, I S M A D E IN R E L AT I O N TO T H E C O N T E N T O F T H I S D O C U M E N T. I N
N O E VE NT WI L L NOK IA S OL UT I ON S AN D NET W O RK S B E L I A B L E F O R A N Y D A M A G E S , I N C L U D I N G B U T N OT
LIMI TE D TO SPECIA L , D IREC T, IN DI REC T, IN CI DE N TA L OR C O N S E Q U E N T I A L O R A N Y L O S S E S , S U C H A S B U T
N OT LI MIT ED TO L OS S OF PR OF I T, REVEN UE, B U S I NE S S I N T E R R U P T I O N , B U S I N E S S O P P O RT U N I T Y O R D ATA
THAT MAY A RI SE F RO M T HE U SE OF T HI S DO CU M E N T O R T H E I N F O R M AT I O N I N I T, E V E N I N T H E C A S E O F
ER RO RS IN O R O M IS S ION S F RO M T H IS DO CU M E N T O R IT S C O N T E N T.
This document is Nokia Solutions and Networks’ proprietary and confidential information, which may not be distributed or disclosed to any
third parties without the prior written consent of Nokia Solutions and Networks.
Nokia is a registered trademark of Nokia Corporation. Other product names mentioned in this document may be trademarks of their
respective owners, and they are mentioned for identification purposes only.
Copyright © 2018 Nokia Solutions and Networks. All rights reserved.
Important Notice on Product Safety
This product may present safety risks due to laser, electricity, heat, and other sources of danger.
Only trained and qualified personnel may install, operate, maintain or otherwise handle this product and only after having carefully read the
safety information applicable to this product.
The safety information is provided in the Safety Information section in the “Legal, Safety and Environmental Information” part of this
document or documentation set.
Nokia Solutions and Networks is continually striving to reduce the adverse environmental effects of its products and services. We would like
to encourage you as our customers and users to join us in working towards a cleaner, safer environment. Please recycle product packaging
and follow the recommendations for power use and proper disposal of our products and their components.
If you should have questions regarding our Environmental Policy or any of the environmental services we offer, please contact us at Nokia
Solutions and Networks for any additional information.
Rehosting GSM BTS Sites
DN98908338 2-1
Table of Contents
Contents
1 About rehosting............................................................................................................................................... 6
2 Introduction to rehosting a GSM BTS site................................................................................................... 7
3 Preparing a rehosting operation....................................................................................................................9
3.1 Prerequisites for the operation..................................................................................................................9
3.1.1 Prerequisites for GPRS.................................................................................................................. 10
3.1.2 Prerequisites when external alarms are used................................................................................ 10
3.1.3 Prerequisites for RF Hopping......................................................................................................... 10
3.1.4 Prerequisites for BCCH Allocation lists.......................................................................................... 11
3.1.5 Prerequisites for Dynamic Frequency and Channel Allocation (DFCA)......................................... 11
3.1.6 Prerequisites for IMSI Based Handover (IBHO).............................................................................11
3.1.7 Prerequisites for the sites running under BSS synchronization..................................................... 11
3.1.8 Prerequisites for BTS sites using pseudowire................................................................................11
3.1.9 Prerequisites for Packet Abis BCFs............................................................................................... 11
3.1.10 Prerequisites for Pseudowire........................................................................................................12
3.1.11 Prerequisites for Packet Abis Transport Media Conversion......................................................... 12
3.1.12 Prerequisites for OSC capable sites............................................................................................ 13
3.2 Overview of the preparation phase........................................................................................................ 13
3.3 Overview of the preparation phase in NetAct Advanced Configurator................................................... 15
3.4 Identifying the BCFs to be rehosted.......................................................................................................17
3.5 Planning BSC RNW and transmission parameters................................................................................ 17
3.6 Informing customer services................................................................................................................... 18
3.7 Checking the transmission polling method............................................................................................. 18
3.8 Stopping the TRX loop tests...................................................................................................................18
3.9 Creating a rehosting plan....................................................................................................................... 18
3.9.1 Selecting BCFs to be rehosted...................................................................................................... 19
3.9.2 Entering parameters for the new objects....................................................................................... 19
3.9.2.1 Objects included in the rehosting plan...................................................................................20
3.9.3 Creating BSC-BTS connections with MMLs...................................................................................20
3.9.4 Defining object parameters using GSM Rehosting Wizard............................................................ 21
3.9.5 Planning when same LAC is used in both old and new BSC........................................................ 30
3.9.6 Creating a rehosting plan............................................................................................................... 30
3.9.7 GSM Rehosting Wizard constraints............................................................................................... 30
3.9.8 Defining parameter values in GSM Rehosting Wizard using an import file....................................31
3.9.8.1 Rehosting Wizard file in TXT format......................................................................................31
3.9.8.2 Rehosting Wizard file in CSV format..................................................................................... 33
3.9.8.3 Defining parameter names in Rehosting Wizard import file...................................................34
3.10 Provisioning the RNW creation plan to the new BSC.......................................................................... 35
3.11 Uploading BTS site configuration data from old BSC...........................................................................35
3.12 Validating BTS site configuration plan.................................................................................................. 35
3.13 Attaching software to new BCFs.......................................................................................................... 36
3.14 Creating NetAct monitoring views manually......................................................................................... 36
NetAct™ 16
© 2018 Nokia Solutions and Networks
3
Rehosting GSM BTS Sites
DN98908338 2-1
Table of Contents
4 Performing the rehosting operation............................................................................................................ 37
4.1
4.2
4.3
4.4
4.5
Overview of the rehosting phase............................................................................................................37
Overview of the rehosting phase in NetAct Advanced Configurator...................................................... 39
Stopping measurements......................................................................................................................... 41
Locking old BCFs....................................................................................................................................42
Activating maintenance mode for the BCFs in the old BSC...................................................................42
4.5.1 To activate the maintenance mode for the old BCFs.....................................................................42
4.6 Activating maintenance mode for the BTSs in NetAct Advanced Configurator...................................... 42
4.7 Provisioning BTS site configuration plan in old BSC..............................................................................42
4.8 Cutting transmission over....................................................................................................................... 43
4.9 Provisioning BTS in MSC (BTSM) update plan......................................................................................43
4.10 Provisioning an adjacency update plan................................................................................................ 43
4.11 Provisioning a cell reference update plan.............................................................................................43
4.12 Provisioning swap LACs update plan................................................................................................... 44
4.13 Uploading a new BSC.......................................................................................................................... 45
4.14 Uploading old and new BSC in NetAct Advanced Configurator........................................................... 45
4.15 Activating BSC-BTS connections with MMLs....................................................................................... 45
4.16 Uploading BTS SC data from the new BSC........................................................................................ 45
4.17 Uploading BTS SC data from the new BSC in NetAct Advanced Configurator.................................... 46
4.18 Deactivating maintenance mode for BCFs in the new BSC.................................................................46
4.19 Unlocking new BCFs.............................................................................................................................46
4.20 Updating references in NetAct databases............................................................................................ 46
4.21 Updating references in NetAct databases in NetAct Advanced Configurator....................................... 47
4.22 Updating references in regional NetAct................................................................................................47
4.23 Refreshing BSC topology in Q3/MML mediation.................................................................................. 47
4.24 Checking the state of the objects......................................................................................................... 47
4.24.1 To check the state of the managed objects................................................................................. 47
5 Cleaning up.................................................................................................................................................... 49
5.1
5.2
5.3
5.4
Overview of the clean-up phase.............................................................................................................49
Overview of the clean-up phase in NetAct Advanced Configurator....................................................... 49
Provisioning an RNW deletion plan........................................................................................................ 50
Removing external cells from the old region in NetAct Advanced Configurator..................................... 51
5.5
5.6
5.7
5.8
5.9
Deleting old objects and views............................................................................................................... 51
Restarting measurement collection.........................................................................................................51
Restarting the scheduled TRX loop tests............................................................................................... 51
Checking performance............................................................................................................................ 52
Deleting a rehosting plan........................................................................................................................52
6 Customizing Rehosting Tool........................................................................................................................ 53
6.1 Creating a customized rehosting view....................................................................................................53
6.1.1 To create a customized rehosting CM view in CM Editor.............................................................. 54
6.2 Creating a customized operation list...................................................................................................... 54
6.2.1 To create a customized rehosting operation list.............................................................................54
6.2.2 Creating script operations...............................................................................................................56
NetAct™ 16
© 2018 Nokia Solutions and Networks
4
Rehosting GSM BTS Sites
DN98908338 2-1
Table of Contents
6.2.2.1 To create script operations.....................................................................................................56
6.3 Creating a customized wizard file...........................................................................................................57
6.3.1 To create a customized wizard file.................................................................................................57
7 Reverting back to the old configuration.....................................................................................................59
8 Troubleshooting guidelines for rehosting GSM BTS sites....................................................................... 60
8.1 Send files to customer support...............................................................................................................60
8.2 Enable rehost-specific temporary plans..................................................................................................61
9 Appendix A: Rehosting CM view parameters............................................................................................ 62
10 Appendix B: Rehosting Wizard parameters and special values............................................................ 72
NetAct™ 16
© 2018 Nokia Solutions and Networks
5
Rehosting GSM BTS Sites
DN98908338 2-1
About rehosting
1 About rehosting
The document gives instructions on how to move GSM BTS sites from one BSC to another. The
instructions apply to UltraSite, BTSPlus, Horizon, Flexi EDGE, Flexi Multiradio, Flexi Multiradio 10 and
Single RAN BTS.
Functionality requirements in this operation:
• CM Operations Manager
• CM Editor
• Monitor
• Administration of Measurements (not needed in NetAct Advanced Configurator)
• Software Manager (not needed in NetAct Advanced Configurator)
Licence requirements in this operation:
• CM Rehosting for GSM
• CM HW Management for GSM LK (needed for HW upload to be done during rehosting operation).
This license is not needed in NetAct Advanced Configurator.
• CM Rehosting for SRAN (needed for planning and activating Single RAN BTS site configuration
changes)
NetAct™ 16
© 2018 Nokia Solutions and Networks
6
Rehosting GSM BTS Sites
DN98908338 2-1
Introduction to rehosting a GSM BTS site
2 Introduction to 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 (a major airport, conference centre, or shopping centre, for example)
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.
All BTS types can be rehosted using the same rehost plan. The rehosting procedure consists of three
phases.
• For instructions on the preparation phase, see Preparing the rehosting operation.
• For instructions on the change-over phase, see Performing the rehosting operation in Rehosting
GSM BTS Sites.
• For instructions on the clean-up phase, see Cleaning up.
The following pictures illustrate the difference between GSM BTS site and Single RAN BTS rehosting.
In GSM, the BTS site is managed via BSC. In Single RAN, the BTS site has a direct management
interface towards NetAct. This difference is reflected also in the topology in NetAct.
Figure 1: Rehosting GSM BTS overview
NetAct™ 16
© 2018 Nokia Solutions and Networks
7
Rehosting GSM BTS Sites
DN98908338 2-1
Introduction to rehosting a GSM BTS site
Figure 2: GSM BTS
Figure 3: Single RAN BTS
NetAct™ 16
© 2018 Nokia Solutions and Networks
8
Rehosting GSM BTS Sites
DN98908338 2-1
Preparing a rehosting operation
3 Preparing a rehosting operation
This chapter provides information on preparing a rehosting operation. Before starting the operation
some prerequisites must be met. Read this carefully to avoid unnecessary troubleshooting later.
3.1 Prerequisites for the operation
Ensure that the following prerequisites are met before starting the rehosting operation:
• NetAct Configurator functionality is operational. In NetAct Advanced Configurator the connection
to the regional NetAct is ok (connection configured, events are arriving from the reginal NetAct).
• XML event handling needs to be active in all BSCs.
• Sites need to be selected from an old BSC, since the tool supports only rehosting from an old BSC
to a new BSC.
• Radio network data in BSC and MSC is consistent with the network elements and NetAct/NetAct
Advanced Configurator.
• The new BSC exists under the same controlling NetAct as the old BSC. (Not in NetAct Advanced
Configurator.)
• In NetAct Advanced Configurator the new BSC can be under a different region than the old BSC.
• Initial BTS software package is defined.
• There are enough licenses in the new BSC. The features in the new BSC are at least the same as
in the old BSC.
• The new BSC is integrated with NetAct, that is:
– ETs (Exchange Terminals) are installed.
– Remote MML connections are working.
– Fault and performance data can be collected from the BSC.
• The ET for the BTS site(s) is installed and configured in the BSC.
• The transmission plan is ready.
• It is recommended that the old BSCs and the new BSCs are of the same version and release.
If they are of different versions and releases, it may be that there are differences in parameters
and/or object classes between the two BSC versions. Some parameters/object classes may
have been added, deleted, or changed between the versions. For example, the allowed value
range of a parameter may have been changed, or a new parameter which needs to be planned
in object creation may have been introduced. In order to create a proper rehosting plan in such
cases, the operator needs to either create a rehosting view with additional parameters and plan
NetAct™ 16
© 2018 Nokia Solutions and Networks
9
Rehosting GSM BTS Sites
DN98908338 2-1
Preparing a rehosting operation
the parameter values in the data fill of Rehosting Tool, or correct the rehosting plan manually with
CM Editor or via plan import before provisioning it to the network.
• Rehosting Tool supports Multipoint A with the following restriction: if a BSCM object for a BSC
exists under several MSCs, all Location Areas of that BSC are considered pooled. Before
rehosting, check that the used LA exists in the NetAct database. In case of Multipoint A, LAs and
BTSMs must be correctly defined in all MSCs linked with the BSCs. If you use dummy LAC in
rehosting, a dummy LA must exist in all MSCs that are linked with the old and new BSCs.
In NetAct Advanced Configurator run the Workflow Engine operation 'Update Linked Cell DN for
BTSM' to link BTSM to the related BTS.
• If you want to run the rehosting operation for a set of BCFs (not all BCFs included in the Provision
RNW Creation Plan), you need to run the whole change-over and clean-up procedure using the
same scope selection. Changing the scope during the change-over and clean-up phases may
result in a loss of data.
• CF and DAC measurement collection is stopped.
In NetAct Advanced Configurator alien LCSE modifications are supported only when source BSC,
target BSC, and BSC having alien LCSE are integrated to the same regional NetAct.
In NetAct Advanced Configurator use a different location area LAC in the source and target BSC
when the source and target BSC are integrated to different NetAct regions and one of following
functionalities is used in the rehosted site:
– reference cells for ADCE
– interferring cell (IUO) information in TRX
– location service LCSE
3.1.1 Prerequisites for GPRS
• SGSN parameters are defined.
• The Gb interface between the SGSN and the BSC is configured.
• The GPRS capacity parameters are defined.
• RAs for the new sites are configured.
3.1.2 Prerequisites when external alarms are used
If external alarms are used, alarm text (TID objects) in each BSC needs to be equal.
3.1.3 Prerequisites for RF Hopping
If RF hopping is activated, the MAL object to be used by the new site have already been created to
the new BSC with the same ID it has in the old BSC. When creating the new BTS, the rehosting tool
copies the old Used MAL ID value to the new BTS. If you want to use different MAL ID, you need to
create a user-defined rehosting view.
NetAct™ 16
© 2018 Nokia Solutions and Networks
10
Rehosting GSM BTS Sites
DN98908338 2-1
Preparing a rehosting operation
3.1.4 Prerequisites for BCCH Allocation lists
If BCCH Allocation lists are used, BAL objects to be used by the new site have already been created
to the new BSC with the same ID it has in the old BSC. When creating the new BTS, the rehosting
tool copies the old Idle State BCCH Allocation List (BAL) ID value to the new BTS. If you want to use
different BAL ID, you need to create a user-defined rehosting view.
3.1.5 Prerequisites for Dynamic Frequency and Channel Allocation (DFCA)
If the Dynamic Frequency and Channel Allocation (DFCA) functionality is included, the Rehosting
dialog requires that the following objects are created and have the same object IDs in the old and the
new BSCs:
• DFCA MA List (MALD)
• DFCA MA Unsynch List (MAL)
Note: If you want to use different MALD/MAL ID in the new BSC, you need to create a userdefined rehosting view. Check from the new BSC that the used DFCA MA Unsynch List is
the same as in the old 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.
3.1.6 Prerequisites for IMSI Based Handover (IBHO)
If the IMSI Based Handover (IBHO) functionality is included, the Rehosting dialog requires that the
following objects are created:
• ANE (Authorised Networks)
• SG (Subscriber Group)
3.1.7 Prerequisites for the sites running under BSS synchronization
• An SMLC exists under the new BSC.
• There exists an LMUA object under the old BSC with the same ID as the old master BCF.
3.1.8 Prerequisites for BTS sites using pseudowire
• ETIP1-A basic software license is installed and ETIP card is commissioned.
• IP address, PSN tunnel and pseudowire settings in ETIP have been configured.
3.1.9 Prerequisites for Packet Abis BCFs
• The BSCs are S16_2 level or higher.
• ETP/ETME unit has been commissioned in the new BSCs. The ETP object has been created to
represent theETP/ETME unit.
NetAct™ 16
© 2018 Nokia Solutions and Networks
11
Rehosting GSM BTS Sites
DN98908338 2-1
Preparing a rehosting operation
• PCU/PCUM with correct software exists in the new BSCs (if GPRS/EGPRS is in use, the BSCs
must have PCU2s dedicated for Packet Abis).
• Security Gateways for BSC have been configured if Packet Abis Security for BTS is used.
• IPv4 addresses for the physical (ETP/ETMEs, BCSU/BCXUs) and logical (VLAN) network
interfaces to be used by the new sites have been configured in the new BSCs.
• In case E1/T1 is used to connect BSC to Packet Abis over TDM, an STM/ADM equipment exist at
new BSC site. BSC supports only STM-1/OC3 connectivity for Packet Abis over TDM sites. New
STM/ADM cross-connections have been planned for BSC in case Packet Abis over TDM is in use.
• Static Routes (BCSUs and BCXUs for OMUSIG and TRXSIG) to be used by the new sites have
been configured in the new BSCs.
• SCTP parameters: SCTP associations for the use of OMUSIGs and TRXSIGs of the new sites,
and IP addresses for each association have been configured in the new BSCs.
• In case Packet Abis over Ethernet is used, multilayer switches have been commissioned in the
new BSC site.
• Some of the following feature licenses are active in the new BSCs.
– Packet Abis over TDM, if the rehosted site uses Packet Abis over TDM transport.
– Packet Abis over Ethernet, if the rehosted site uses Packet Abis over Ethernet transport.
– BTS Autoconnection to be able to implement the required changes to the BTS site
configuration via NetAct.
– Packet Abis over Satellite, if the rehosted site uses Packet Abis over Satellite.
– Packet Abis Synchronous Ethernet, if the rehosted sites use Synchronous Ethernet.
– Local Switching for Packet Abis if the rehosted sites use local switching.
– Packet Abis IP/TDM Aggregation if the rehosted sites use IP/TDM aggregation.
– Packet Abis Security for BTS if the rehosted sites have IPSec in use.
– Packet TRS for UltraSite/BTSPlus if Flexi EDGE, Flexi Multiradio BTS, or Flexi Compact
provides Abis transport for a co-located UltraSite/BTSPlus.
3.1.10 Prerequisites for Pseudowire
The following prerequisites must be met before rehosting Flexi EDGE or Flexi Multiradio BTS
providing Abis transport for a co-located UltraSite/BTSPlus, when pseudowire is used for the
UltraSite/BTSPlus and Packet Abis is used for the Flexi BTS:
• At BSC either an external CESoPSN gateway (A2200) or BSC internal ETIP card exists, and has
been configured.
• UltraSite/BTSPlus pseudowire IP address has been configured in the ETIP card, or in the external
CESoPSN gateway (A2200).
3.1.11 Prerequisites for Packet Abis Transport Media Conversion
• Licenses for both Packet Abis over IP/Ethernet and Packet Abis over TDM are active.
• A media conversion device is integrated to the new BSC.
NetAct™ 16
© 2018 Nokia Solutions and Networks
12
Rehosting GSM BTS Sites
DN98908338 2-1
Preparing a rehosting operation
3.1.12 Prerequisites for OSC capable sites
• The BSCs are S16_2 level or higher.
• The needed OSC licenses are available in the new BSC:
– Double Half Rate with SAIC MS
– OSC Full Rate with SAIC MS
• If the rehosted OSC Half Rate BCFs use legacy Abis, license for Circuit Switched Dynamic Abis
Pool is active in the new BSCs.
• If the rehosted OSC Full Rate BCFs use legacy Abis, 8k TRAU for OSC AMR FR and/or Circuit
Switched Dynamic Abis Pool is active in the new BSCs.
• If the rehosted BCFs use Packet Abis, see the Packet Abis related requirements above.
3.2 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 carry out the various steps. Click a process in the figure for more information.
During each provision step of the operation a backup plan can be created by setting Create
BackupPlan to True in the dropdown list of the rehosting operations window.
NetAct™ 16
© 2018 Nokia Solutions and Networks
13
Rehosting GSM BTS Sites
NetAct™ 16
DN98908338 2-1
© 2018 Nokia Solutions and Networks
Preparing a rehosting operation
14
Rehosting GSM BTS Sites
DN98908338 2-1
Preparing a rehosting operation
3.3 Overview of the preparation phase in NetAct Advanced Configurator
The following flowchart gives you an overview of the preparation phase as well as the tools that you
can use to carry out the various steps. Click a process in the figure for more information.
During each provision step of the operation a backup plan can be created by setting Create
BackupPlan to True in the dropdown list of the rehosting operations window.
NetAct™ 16
© 2018 Nokia Solutions and Networks
15
Rehosting GSM BTS Sites
NetAct™ 16
DN98908338 2-1
© 2018 Nokia Solutions and Networks
Preparing a rehosting operation
16
Rehosting GSM BTS Sites
DN98908338 2-1
Preparing a rehosting operation
3.4 Identifying the BCFs to be rehosted
All types of BCFs (Abis type, site type, legacy and Single RAN BTS) can be rehosted in the same
rehosting operation. The BCF type must remain the same during the rehosting operation.
To rehost Multi-BCF sites, all the BTSs in the segment must be rehosted at the same time. The
segment configuration must stay the same in the rehosting process.
In case of Packet Abis over TDM, all the BTSs in the same Local Switching group (Packet Abis BCF
Group) must be rehosted at the same time to retain configuration consistency. The same applies for
the Packet Abis for IP/TDM Aggregation groups. This limitation is due to the different roles of the BTSs
(hub, tail), which reflects in the BSC RNW and BTS SC configuration. The rehosting tool does not
support configuration change during rehosting.
In case of Packet Abis over Ethernet, or Packet Abis Media Conversion, it is possible to split the
Packet Abis BCF Group ID by moving some of the BTSs under the new BSC provided that in both the
old area in the source BSC and the new area in the target BSC, there are more than 1 BTS. In Packet
Abis over Ethernet case, the local switching configuration can be changed more easily, by allocating
the BTSs to a new group.
3.5 Planning BSC RNW and transmission parameters
Operators can use any tool to plan the RNW and transmission parameters and transfer the plan to
NetAct Configurator in CSV or RAML2.0 file format. Planning must be based on the latest BSC RNW
and BTS site configuration data.
To create the BSC RNW and BTS SC plans, the following information should be available:
• Identification for BCF and BTS. For TRXs, the ID will be the same as in the old BSC
• Identification for DAPs, LAPDs, CSDAPs, HDLCs
• PCM for DAP, legacy Abis LAPD, CSDAP and HDLC
• PCU index and BCSU IDs for DAPs
• Packet Abis BCF Group ID
• ETP ID
• SCTP Association Name for Packet Abis LAPD links
• Minimum SCTP port for OMUSIG
• VLAN IDs of the ETP-E/ETME unit
• IP addresses for:
– ETP-E/ETME unit
– ETIP unit or an external CESoPSN gateway (A2200) for pseudowire connections
– BCSU/BCXU
NetAct™ 16
© 2018 Nokia Solutions and Networks
17
Rehosting GSM BTS Sites
DN98908338 2-1
Preparing a rehosting operation
– BTS site
– Security Gateway
– Site Support Equipment
Time slots of TRXs, DAPs, CSDAPs, HDLCs and LAPDs will be the same as in the old BSC. To
change the time slots, a user-defined rehosting view needs to be made.
3.6 Informing customer services
During the rehosting, services are disrupted on the rehosted site, and handovers to the site do not
succeed. It is advisable to inform your customer services organization of possible disruptions in 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 Monitor in the regional NetAct. For more information, see
About maintenance mode in Maintenance Mode Help.
3.7 Checking the transmission polling method
The transmission polling method (alarm collection via the Q1 interface) needs to be defined and set up
in the BSC at this stage. You can use either BSC or BTS polling of transmission equipment.
3.8 Stopping the TRX loop tests
Stop all TRX loop tests on the sites to be rehosted. The tests can be stopped in Operation History or
Scheduled Operations in CM Operations Manager in the regional NetAct. To stop the tests, interrupt
the ongoing loop test operations or delete the scheduled operations.
Note:
Some of the tests can only be managed with MML and therefore cannot be stopped from CM
Operations Manager.
For instructions on deleting scheduled operations, see Viewing and working with scheduled operations
in CM Operations Manager Help.
NetAct™ 16
© 2018 Nokia Solutions and Networks
18
Rehosting GSM BTS Sites
DN98908338 2-1
Preparing a rehosting operation
3.9 Creating a rehosting plan
Rehosting plans are managed in CM Operations Manager. You can create a rehosting plan in CM
Operations Manager or import one in XML or CSV format. It is also possible to import a complete plan
or just some part of it, such as BTS parameters.
Note:
When user-specific values are saved for GEN_STRING parameters in the topology database
for the rehosted objects, those parameter values are not copied automatically during a
rehosting operation.
Note:
Recommended maximum length of a rehosting plan name is 40 characters.
For more information on importing a rehosting plan, see CSV file format overview in CSV Interface
for Configuration Management Data or XML interface overview in XML Interface for Configuration
Management Data.
3.9.1 Selecting BCFs to be rehosted
If you try to drag and drop or copy and paste objects that are not defined in the used CM view, the
objects are ignored. Note that the object is not created in the database and saved in the plan unless
the objects and their IDs or name of the LAPD link are defined, so fill them in first. The recommended
maximum capacity of Rehosting Tool is 50 BCFs
Choose one of the following to select the BCFs to be rehosted:
• Drag and drop (or copy and paste) the BCF(s) to be rehosted from CM Editor to the Rehosting
dialog.
• Select the sites to be rehosted with the Add BTS sites dialog of Rehosting Tool.
• Import the sites to be rehosted with the Rehosting Wizard import functionality.
3.9.2 Entering parameters for the new objects
When you drag and drop (or copy and paste) the BCFs to be rehosted, for example from CM Editor,
the Rehosting Wizard dialog opens. To define object parameters without using Rehosting Wizard,
click the Cancel button. Select the Rehosting Wizard file and enter missing IDs and parameters by
following the guidance in the information area in the Rehosting Wizard dialog. When reaching the last
wizard page, it is possible to finish and the focus returns to the Rehosting dialog where the data fill is
filled in automatically with IDs and parameters.
It is recommended to use Rehosting Wizard for parameter planning. Wizard gives a notification when
a parameter must be planned using the data fill. Moreover, if you create a customized view, the
planning of the additional parameters must be done in the data fill.
For more information on the parameters, see Appendix A: Rehosting CM view parameters.
When defining the parameter values, you should note the following dependencies and restrictions:
NetAct™ 16
© 2018 Nokia Solutions and Networks
19
Rehosting GSM BTS Sites
DN98908338 2-1
Preparing a rehosting operation
• All object identifiers need to be defined before any other parameters of that object are saved to the
database. LAPD ID is not immediately visible in the data fill right after LAPD Name is entered. It is
visible after a refresh period.
• The SCTP association created in the BSC (MML interface only) has the following dependencies to
the parameters in the rehosting view:
– LAPD parameter Association Name must match with the name given for the SCTP
association.
– PABTRS parameter M Plane Local IP Address in BTS SC must match with the destination
address of the OMUSIG SCTP association.
– PABTRS parameter M Plane Remote IP Address in BTS SC must match with the source
address of the OMUSIG SCTP association.
– SCTP parameter Minimum SCTP Port in BTS SC must match with the destination port of the
OMUSIG SCTP association.
For more information, see the Rehosting CM view parameters in Appendix A: Rehosting CM view
parameters.
3.9.2.1 Objects included in the rehosting plan
A plan made with the default rehosting view may include the following BSC objects:
• DAP
• LAPD
• BCF
• BTS
• TRX
• BTSM
• HDLC
• CSDAP
The following objects in the Flexi EDGE, Flexi Multiradio BTS, and Flexi Compact site configuration
are also included in the default rehosting view:
• BTSNE
• IPSEC
• IPRTAB
• PABBAC (Flexi EDGE, Flexi Multiradio BTS, Flexi Multiradio 10 BTS)
• PABTRS
• PPPATH (Flexi Compact)
• PWCONF (Flexi Compact)
• SCTP
• SSE
NetAct™ 16
© 2018 Nokia Solutions and Networks
20
Rehosting GSM BTS Sites
DN98908338 2-1
Preparing a rehosting operation
3.9.3 Creating BSC-BTS connections with MMLs
Creating BSC-BTS connections with MMLs is a manual task in NetAct Advanced Configurator. In the
Rehosting dialog it appears as a reminder task.
3.9.4 Defining object parameters using GSM Rehosting Wizard
The following tables list the parameters that can be changed in GSM Rehosting Wizard.
Parameter
Description
BCF ID
BCF ID copied from old and set automatically to
BCF and BTSNE.
BCF Name
BCF Name copied from old and set automatically
to BCF.
BTS ID
BTS ID copied from old and set automatically to
BTS ID and Segment ID. In Multi-BCF, the slave
BTSs get the Segment ID from the master BTS.
LAC
Location Area Code copied from old and set
automatically to BTS and BTSM.
RAC
BTS Routing Area Code copied from old and set
automatically to BTS.
Table 1: Legacy Abis
Parameter
Description
BCF ID
BCF ID copied from old and set automatically to
BCF and BTSNE.
BCF Name
BCF Name copied from old and set automatically
to BCF.
Used ETP ID
NetAct™ 16
Enter ETP the BCF is connected to.
© 2018 Nokia Solutions and Networks
21
Rehosting GSM BTS Sites
DN98908338 2-1
Preparing a rehosting operation
Parameter
Description
Packet Abis BCF
Local Switching and IP/TDM Aggregation Group ID
Group ID
is copied from old and set automatically to BCF.
BTS ID
BTS ID copied from old and set automatically to
BTS ID and Segment ID. In Multi-BCF, the slave
BTSs get the Segment ID from the master BTS.
LAC
Location Area Code copied from old and set
automatically to BTS and BTSM.
RAC
BTS Routing Area Code copied from old and set
automatically to BTS.
Table 2: Packet Abis over TDM
Parameter
Description
BCF ID
BCF ID copied from old and set automatically to
BCF and BTSNE.
BCF Name
BCF Name copied from old and set automatically
to BCF.
Used ETP ID
Enter ETP the BCF is connected to.
Packet Abis BCF
Local Switching and IP/TDM Aggregation Group ID
Group ID
is copied from old and set automatically to BCF.
BTS ID
BTS ID copied from old and set automatically to
BTS ID and Segment ID. In Multi-BCF, the slave
BTSs get the Segment ID from the master BTS.
LAC
Location Area Code copied from old and set
automatically to BTS and BTSM.
NetAct™ 16
© 2018 Nokia Solutions and Networks
22
Rehosting GSM BTS Sites
DN98908338 2-1
Preparing a rehosting operation
Parameter
Description
RAC
BTS Routing Area Code copied from old and set
automatically to BTS.
Table 3: Packet Abis over IP/Ethernet
Parameter
Description
BCF ID
BCF ID copied from old and set automatically to
BCF and BTSNE.
BCF Name
BCF Name copied from old and set automatically
to BCF.
Used ETP ID
Enter ETP the BCF is connected to.
Packet Abis BCF
Local Switching and IP/TDM Aggregation Group ID
Group ID
is copied from old and set automatically to BCF.
BTS ID
BTS ID copied from old and set automatically to
BTS ID and Segment ID. In Multi-BCF, the slave
BTSs get the Segment ID from the master BTS.
LAC
Location Area Code copied from old and set
automatically to BTS and BTSM.
RAC
BTS Routing Area Code copied from old and set
automatically to BTS.
Table 4: Packet Abis Transport Media Conversion
Parameter
Description
LAPD Name
LAPD Name copied from old and set automatically
to LAPD and BCF/TRX.
NetAct™ 16
© 2018 Nokia Solutions and Networks
23
Rehosting GSM BTS Sites
DN98908338 2-1
Parameter
Description
LAPD PCM
Enter PCMs for the site. Set automatically to
Preparing a rehosting operation
LAPDs, TRXs and DAPs sharing the PCM.
SCTP
LAPD Association Name copied from old and set
Association
automatically to LAPD.
Name
Table 5: LAPDs
Parameter
Description
CSDAP ID
CSDAP ID copied from old and set automatically to
CSDAP and BCF.
CSDAP PCM
Enter PCMs for CSDAPs. Set automatically to
CSDAPs sharing the PCM.
Table 6: CSDAPs
Parameter
Description
DAP ID
DAP ID copied from old and set automatically to
DAP and TRXs.
PCU Index
Enter PCUs for DAPs. Set automatically to DAPs
sharing the PCU.
BCSU ID
Enter BCSUs for DAPs. Set automatically to DAPs
sharing the BCSU.
NetAct™ 16
© 2018 Nokia Solutions and Networks
24
Rehosting GSM BTS Sites
DN98908338 2-1
Preparing a rehosting operation
Table 7: DAPs
Parameter
Description
BTSM ID
BTSM ID copied from old and set automatically to
BTSM.
Table 8: BTSMs
Parameter
Description
HDLC ID
HDLC ID copied from old and set automatically to
HDLC and BCF.
HDLC PCM
Enter PCMs for HDLCs. Set automatically to
HDLCs sharing the PCM.
Table 9: HDLCs
Parameter
Description
U-plane ETP Vlan Enter U-Plane EPT Vlan ID for BCF.
ID
CU-Plane BTS IP CU-Plane BTS IP Address copied from old and set
NetAct™ 16
Address
automatically to BCF.
CU-Plane BTS
CU-Plane BTS Subnet Mask copied from old and
Subnet Mask
set automatically to BCF.
M-Plane BSC IP
Enter M-Plane BSC IP Address. Set automatically
Address
to PABTRS.
M-Plane BTS IP
Enter M-Plane BTS IP Address. Set automatically
Address
to PABTRS and BCF, including CU-Plane.
© 2018 Nokia Solutions and Networks
25
Rehosting GSM BTS Sites
DN98908338 2-1
Preparing a rehosting operation
Parameter
Description
M-Plane BTS
Enter M-Plane BTS Subnet Mask. Set
Subnet Mask
automatically to PABTRS and BCF, including CUPlane.
CU-Plane BTS
CU-Plane BTS Vland ID copied from old and set
Vlan ID
automatically to PABTRS and copied to OAMMA.
M-Plane BSC IP
Enter M-Plane BSC IP Address. Set automatically
Address
to PABTRS.
M-Plane BTS IP
M-Plane BTS IP Address copied from old and set
Address
automatically to PABTRS and BCF.
M-Plane BTS
M-Plane BTS Subnet Mask copied from old and
Subnet Mask
set automatically to PABTRS and BCF.
M- and C-Plane
Enter M- and C-Plane Gateway IP Address (at
Gateway IP
ETPT). Set automatically to PABTRS.
address
M-Plane BTS
M-Plane BTS Vlan ID copied from old and set
Vlan ID
automatically to PABTRS and OAMMA.
M-Plane BSC IP
Enter M-Plane BSC IP Address. Set automatically
Address
to PABTRS.
M-Plane BTS IP
Enter M-Plane BTS IP Address. Set automatically
Address
to PABTRS and BCF, including CU-Plane.
M-Plane BTS
Enter M-Plane BTS Subnet Mask. Set
Subnet Mask
automatically to PABTRS and BCF, including CUPlane.
NetAct™ 16
CU-Plane BTS
CU-Plane BTS Vland ID copied from old and set
Vlan ID
automatically to PABTRS and OAMMA.
© 2018 Nokia Solutions and Networks
26
Rehosting GSM BTS Sites
DN98908338 2-1
Preparing a rehosting operation
Parameter
Description
M-Plane BSC IP
Enter M-Plane BSC IP Address. Set automatically
Address
to PABTRS.
M-Plane BTS IP
M-Plane BTS IP Address copied from old and set
Address
automatically to PABTRS and BCF.
M-Plane BTS
M-Plane BTS Subnet Mask copied from old and
Subnet Mask
set automatically to PABTRS and BCF.
M- and C-Plane
Enter M- and C-Plane Gateway IP Address (at
Gateway IP
ETPT). Set automatically to PABTRS.
address
M-Plane BTS
M-Plane BTS Vlan ID copied from old and set
Vlan ID
automatically to PABTRS and OAMMA.
Minimum SCTP
Enter SCTP Port for M-Plane. Set automatically to
Port
SCTP.
Minimum SCTP
Enter SCTP Port for M-Plane. Set automatically to
Port
SCTP.
IP Security
IP Security Tunnel Settings are copied from old
and set automatically to IPSEC.
IP Security
IP Security Tunnel Settings are copied from old
and set automatically to IPSEC.
NetAct™ 16
Service OAM
Remote maintenance endpoint list copied from old
MEP
and set automatically to OAMMA.
Service OAM
Remote maintenance endpoint list copied from old
MEP
and set automatically to OAMMA.
© 2018 Nokia Solutions and Networks
27
Rehosting GSM BTS Sites
DN98908338 2-1
Preparing a rehosting operation
Parameter
Description
Site Support
Site Support Equipment IP Addresses are copied
Equipment
from old and set automatically to SSE.
Site Support
Site Support Equipment IP Addresses are copied
Equipment
from old and set automatically to SSE.
Remote IP
Enter PWE Remote IP Address at BSC end (ETIP
Address for PWE or external GW). Set automatically to PWCONF.
Remote IP
Enter Subnet Mask for Remote IP Address. Set
Subnet Mask for
automatically to PWCONF.
PWE
Local IP Address
Local IP Address for PWE copied from old and set
for PWE
automatically to PWCONF.
Gateway IP
Gateway IP Address for PWE copied from old and
Address for PWE set automatically to PWCONF.
Remote UDP Port Enter Remote UDP Port for PWE. Set
for PWE
automatically to PWCONF.
Local UDP Port
Local UDP Port for PWE copied from old and set
for PWE
automatically to PWCONF.
Remote IP
Enter PWE Remote IP Address at BSC end (ETIP
Address for PWE or external GW). Set automatically to PWCONF.
Remote IP
Enter Subnet Mask for Remote IP Address. Set
Subnet Mask for
automatically to PWCONF.
PWE
NetAct™ 16
Local IP Address
Local IP Address for PWE copied from old and set
for PWE
automatically to PWCONF.
© 2018 Nokia Solutions and Networks
28
Rehosting GSM BTS Sites
DN98908338 2-1
Preparing a rehosting operation
Parameter
Description
Gateway IP
Gateway IP Address for PWE copied from old and
Address for PWE set automatically to PWCONF.
Remote UDP Port Enter Remote UDP Port for PWE. Set
for PWE
automatically to PWCONF.
Local UDP Port
Local UDP Port for PWE copied from old and set
for PWE
automatically to PWCONF.
Table 10: IP Connectivity
Parameter
Description
CU-Plane Backup CU-Plane Backup Gateway IP Address copied
Gateway IP
from old when the same mcBSC backup is used.
Address
M-Plane Backup
M-Plane Backup Gateway IP Address copied from
Gateway IP
old when the same mcBSC backup is used.
Address
M-Plane Backup
Backup mcBSC IP Address copied from old when
BSC IP Address
the same mcBSC backup is used.
CU-Plane Backup CU-Plane Backup Vlan ID copied from old when
Vlan ID
the same mcBSC backup is used.
M-Plane Backup
M-Plane Backup Vlan ID copied from old when the
Vlan ID
same mcBSC backup is used.
Table 11: IP Connectivity for mcBSC resiliency
Only MO parameters defined in the selected GSM Rehosting Wizard are visible in the Rehosting
Wizard dialog. For more information on how to customize the GSM Rehosting Wizard file, see
Creating a customized wizard file. When not all managed object parameters, which are needed to be
changed, are visible in the Rehosting Wizard dialog, enter them to the data fill.
NetAct™ 16
© 2018 Nokia Solutions and Networks
29
Rehosting GSM BTS Sites
DN98908338 2-1
Preparing a rehosting operation
3.9.5 Planning when same LAC is used in both old and new BSC
If you want to use the same LAC in the new BSC, it is recommended to assign a dummy LAC
temporarily to the rehosted BTSs to preserve the configuration consistency. If a dummy LAC is not
used, the BSC updates the incoming adjacencies inside the new BSC to point to the new, still locked
BTSs, instead of the BTSs in the old BSC. The dummy LAC can be any free LAC value. A dummy
RAC is also required if the rehosted site is using GPRS.
The dummy versus real LAC and RAC values are swapped between the old and new BSC later by
executing the Provision swap LAC’s update plan.
Note:
In NetAct Advanced Configurator use a different location area LAC in the source and target
BSC when the source and target BSC are integrated to different NetAct regions and one of
following functionalities is used in the rehosted site:
• reference cells for ADCE
• interferring cell (IUO) information in TRX
• location service LCSE
3.9.6 Creating a rehosting plan
Rehosting plans are managed in CM Operations Manager. You can create a rehosting plan in CM
Operations Manager or import one in XML or CSV format. It is also possible to import a complete plan
or just some part of it, such as BTS parameters.
Note:
When user-specific values are saved for GEN_STRING parameters in the topology database
for the rehosted objects, those parameter values are not copied automatically during a
rehosting operation.
Note:
Recommended maximum length of a rehosting plan name is 40 characters.
For more information on importing a rehosting plan, see CSV file format overview in CSV Interface
for Configuration Management Data or XML interface overview in XML Interface for Configuration
Management Data.
3.9.7 GSM Rehosting Wizard constraints
Chained BTSs are not fully supported by GSM Rehosting Wizard, and you need to enter the required
parameter updates manually to the data fill.
The allocation of PCMs, BCSUs and PCUs remains unchanged in the wizard. For example, if in
the source BSC, two PCMs were allocated for the site, the wizard proposes also two PCMs for the
NetAct™ 16
© 2018 Nokia Solutions and Networks
30
Rehosting GSM BTS Sites
DN98908338 2-1
Preparing a rehosting operation
rehosted site in the target BSC. The LAPDs, TRXs and DAPs sharing the same PCM in the source
BSC are handled as an entity and allocated together to the new PCM. In the data fill, the allocation of
objects to PCMs can be changed.
3.9.8 Defining parameter values in GSM Rehosting Wizard using an import file
It is possible to define parameter values in GSM Rehosting Wizard by importing a file containing
the planned parameters. You can import the file with the Import to Wizard dialog in the data fill of
Rehosting Tool. The Rehosting Wizard export functionality can be used to create a basic template for
the import file.
Note the following about the Rehosting Wizard import and export functionality:
• All the parameters visible in Rehosting Wizard can be imported to Rehosting Wizard by using the
import file.
• A part of the parameters can be imported to Rehosting Wizard using the import file. If you import
a part of the parameters, you have to define the rest of the parameters manually in Rehosting
Wizard.
• You can import parameters for multiple sites in a single file.
• The Rehosting Wizard export functionality creates a file which contains all the parameter names
and values taken from Rehosting Wizard.
• The format of the import file can be TXT or CSV.
3.9.8.1 Rehosting Wizard file in TXT format
Parameter name and value are on the same row in the Rehosting Wizard TXT format. The name and
the value are separated by the ‘=’ character. The table below shows the special values used in the
TXT import file.
Value
Description
$rehostingWizardFile
Defines the used Rehosting Wizard file name
$oldBTSSiteDN
Defines the DN of the BTS site to be imported
#
Line starting with the # character is considered as a comment line
:
Separator in a parameter name
=
Used as a separator between the name of the parameter and value
of the parameter
Table 12: Special values in TXT import file
The structure of the TXT format is the following:
#Rehosting Wizard file is defined
$rehostingWizardFile=Rehosting Wizard file name
#The BTS sites and parameter names and values
NetAct™ 16
© 2018 Nokia Solutions and Networks
31
Rehosting GSM BTS Sites
DN98908338 2-1
Preparing a rehosting operation
$oldBTSSiteDN=btsSiteDN1
paramName1=value1
paramName2=value2
paramName3=value3
...
$oldBTSSiteDN=btsSiteDN2
paramName1=value1
paramName2=value2
paramName3=value3
...
The following example shows an import file in TXT format:
#Rehost export details
#Rehost plan name: GSM Rehost Example
#Old controller: PLMN-PLMN/BSC-244964
#New controller: PLMN-PLMN/BSC-517345
#Exported parameter values: new
#Export taken: 23/08/12 08:00:43
#Rehosting wizard file name
$rehostingWizardFile=2g_rehosting_wizard.xml
$oldBTSSiteDN=PLMN-PLMN/BSC-244964/BCF-888
BCF ID=888
BCF Name=Fronius
Used ETP ID=0
BTS ID:BTS-889=889
BTS ID:BTS-890=890
LAC=910
RAC=255
LAPD Name:LAPD-46=OM888
LAPD Name:LAPD-48=T8881
LAPD Name:LAPD-49=T8882
LAPD Name:LAPD-50=T8883
LAPD Name:LAPD-51=T8884
SCTP Association Name:LAPD-46=OM888
SCTP Association Name:LAPD-48=T8881
SCTP Association Name:LAPD-49=T8882
SCTP Association Name:LAPD-50=T8883
SCTP Association Name:LAPD-51=T8884
U-plane ETP Vlan ID=Not used
CU-Plane BTS IP Address=10.8.86.202
CU-Plane BTS Subnet Mask=24
M-Plane BSC IP Address=10.8.213.52
M-Plane BTS IP Address=10.8.86.202
M-Plane BTS Subnet Mask=24
Minimum SCTP Port=49152
$oldBTSSiteDN=PLMN-PLMN/BSC-244964/BCF-2450
BCF ID=2450
BCF Name=Stahlwille
NetAct™ 16
© 2018 Nokia Solutions and Networks
32
Rehosting GSM BTS Sites
DN98908338 2-1
Preparing a rehosting operation
Used ETP ID=0
BTS ID:BTS-2451=2451
BTS ID:BTS-2452=2452
BTS ID:BTS-2453=2453
LAC=910
RAC=255
LAPD Name:LAPD-47=O2450
LAPD Name:LAPD-52=T2451
LAPD Name:LAPD-53=T2452
LAPD Name:LAPD-54=T2453
SCTP Association Name:LAPD-47=O2450
SCTP Association Name:LAPD-52=T2451
SCTP Association Name:LAPD-53=T2452
SCTP Association Name:LAPD-54=T2453
U-plane ETP Vlan ID=Not used
CU-Plane BTS IP Address=10.8.233.246
CU-Plane BTS Subnet Mask=26
M-Plane BSC IP Address=10.8.213.52
M-Plane BTS IP Address=10.8.233.246
M-Plane BTS Subnet Mask=26
Minimum SCTP Port=49152
3.9.8.2 Rehosting Wizard file in CSV format
The Rehosting Wizard import file in CSV format uses comma-separated values. The parameter name
and value are on different rows. The table below shows the special values used in the CSV import file.
Value
Description
$rehostingWizardFile
Defines the used Rehosting Wizard file name
$oldBTSSiteDN
Defines the DN of the BTS site to be rehosted
#
Line starting with the # character is considered as a comment line
:
Separator in a parameter name
=
Used as a separator between the values on a row
Table 13: Special values in CSV import file
The structure of the CSV format is the following:
#Rehosting Wizard file is defined
$rehostingWizardFile,Rehosting Wizard file name
#$oldBTSSiteDN parameter name is defined as the first parameter in
parameter row. The values for the BTS sites are defined under the
parameter row.
$oldBTSSiteDN,paramName1,paramName2,paramName3
btsSiteDN1,value1,value2,value3
btsSiteDN2,value1,value2,value3
NetAct™ 16
© 2018 Nokia Solutions and Networks
33
Rehosting GSM BTS Sites
DN98908338 2-1
Preparing a rehosting operation
#Note that it is possible to add multiple parameter rows if needed
$oldBTSSiteDN,param4,param5,param6
btsSiteDN3,value1,value2,value3
The following example shows an import file in CSV format:
#Rehost export details
#Rehost plan name: GSM Rehost Example
#Old controller: PLMN-PLMN/BSC-244964
#New controller: PLMN-PLMN/BSC-517345
#Exported parameter values: new
#Export taken: 23/08/12 08:00:47
#Rehosting wizard file name
$rehostingWizardFile,2g_rehosting_wizard.xml
$oldBTSSiteDN,BCF ID,BCF Name,Used ETP ID,BTS ID:BTS-889,BTS ID:BTS890,LAC,RAC,LAPD Name:LAPD-46,LAPD Name:LAPD-48,LAPD Name:LAPD-49,
LAPD Name:LAPD-50,LAPD Name:LAPD-51,SCTP Association Name:LAPD-46,SCTP
Association Name:LAPD-48,SCTP Association Name:LAPD-49,SCTP Association
Name:LAPD-50,SCTP Association Name:LAPD-51,U-plane ETP Vlan ID,CU-Plane
BTS IP Address,CU-Plane BTS Subnet Mask,M-Plane BSC IP Address,M-Plane
BTS IP Address,M-Plane BTS Subnet Mask,Minimum SCTP Port
PLMN-PLMN/BSC-244964/BCF-2450,2450,Stahlwille,0,2451,2452,2453,910,255,
O2450,T2451,T2452,T2453,O2450,T2451,T2452,T2453,Not used,10.8.233.246,26,
10.8.213.52,10.8.233.246,26,49152
3.9.8.3 Defining parameter names in Rehosting Wizard import file
A parameter name in the Rehosting Wizard import file has to match to a single parameter name in
Rehosting Wizard. The easiest way to get correct parameter names is to open Rehosting Wizard and
use the Rehosting Wizard export functionality.
The parameter name is located on the left side of the parameter field in Rehosting Wizard. Normally, it
is enough to define the parameter name only, but sometimes there are more than one parameter with
the same name. In that case some additional info has to be defined for the parameter name.
If a parameter has multiple fields for different objects, then the object identifier has to be added in
the parameter name. For example, defining different LAPD names in TXT format, can be done in the
following way:
LAPD Name:LAPD-46=OM888
LAPD Name:LAPD-48=T8881
If the parameter field is in the parameter window of Rehosting Wizard and the parameter has
structured values, then the parameter window name, object identifier, structure number, and
parameter name have to be added in the parameter name. For example defining value for Site support
Equipment values in TXT format:
Site Support Equipment:SSE-1:Structure 1:IP Address=10.11.12.13
NetAct™ 16
© 2018 Nokia Solutions and Networks
34
Rehosting GSM BTS Sites
DN98908338 2-1
Preparing a rehosting operation
3.10 Provisioning the RNW creation plan to the new BSC
By provisioning the RNW creation plan in the Rehosting dialog, the objects (LAPDs, DAPs, CSDAPs,
HDLCs, LMUAs, BCFs, BTSs, GPCs, TRXs, HOCs, POCs, ADJLs and outgoing ADCEs and ADJWs)
are created in the NetAct database and the new BSC.
LAPDs and HDLCs are created unlocked. You can select to keep the old maintenance region, or to
move the BCFs under a new maintenance region.
If you are going to rehost only some of the planned BCFs at a time, you must complete the whole
rehosting procedure for the selected set of BCFs before proceeding with the remaining BCFs.
Note:
LADPs are created automatically to unlocked state. If LAPD objects are created to the ET
unit which is in blocked state during provisioning, the LADP objects cannot be automatically
unlocked. In this case, LADP objects are automatically unlocked when the Unlock operation
is performed.
LAPD objects are added to the backup plan after the plan provision is finished successfully. In case of
a provisioning error, LAPDs are not included in the backup plan.
The template ID is copied from old managed objects to new managed objects in a plan.
To provision the creation plan, see Provisioning plans in CM Operations Manager Help.
3.11 Uploading BTS site configuration data from old BSC
Uploading the old BTS data is recommended as this is the only way to make sure that the BTS site
configuration used as a basis of the plan is up-to-date.
Note:
This operation is valid only for S16_2 or higher BSCs and BCFs that require changes to the
BTS site configuration (for example, BCFs that are using Packet Abis).
This operation is not supported in NetAct Advanced Configurator.
3.12 Validating BTS site configuration plan
Validating BTS site configuration plan generates a temporary plan for all BCFs that require changes to
the site configuration data, and validates the temporary plan. This is an optional operation, but useful
for checking the validity of the BTS site configuration before the actual rehosting operation.
NetAct™ 16
© 2018 Nokia Solutions and Networks
35
Rehosting GSM BTS Sites
DN98908338 2-1
Preparing a rehosting operation
Note:
The option to split successful and failed plans upon validation error is not available for this
provisioning operation by default.
Note:
This operation is valid only for S16_2 or higher BSCs and BCFs that require changes to BTS
site configuration (for example, BCFs that are using Packet Abis). The operation requires
that Remote Site Configuration Management for 2G is enabled in NetAct.
This operation is not supported in NetAct Advanced Configurator.
3.13 Attaching software to new BCFs
In Software Manager, you can attach software to new BCFs. For more information, see About
Software Manager in Software Manager Help.
3.14 Creating NetAct monitoring views manually
In Monitor, you can create NetAct monitoring views. For more information, see Creating a view in View
Explorer Help.
NetAct™ 16
© 2018 Nokia Solutions and Networks
36
Rehosting GSM BTS Sites
DN98908338 2-1
Performing the rehosting operation
4 Performing the rehosting operation
This chapter provides instructions for performing the rehosting operation.
4.1 Overview of the rehosting phase
The following flowchart gives you an overview of the change-over phase as well as the tools that you
can use to carry out the various steps. Click a process in the figure for more information.
During each provisioning step, as well as during unlock and update references steps, a backup plan
can be created by setting Create backup plan to True in the drop-down list of the rehosting operations
window.
NetAct™ 16
© 2018 Nokia Solutions and Networks
37
Rehosting GSM BTS Sites
NetAct™ 16
DN98908338 2-1
© 2018 Nokia Solutions and Networks
Performing the rehosting operation
38
Rehosting GSM BTS Sites
DN98908338 2-1
Performing the rehosting operation
During each provision step of the operation a backup plan can be created by setting Create
BackupPlan to True in the drop-down list of the rehosting operations window.
4.2 Overview of the rehosting phase in NetAct Advanced Configurator
The following flowchart gives you an overview of the change-over phase as well as the tools that you
can use to carry out the various steps. Click a process in the figure for more information.
During each provisioning step, as well as during unlock and update references steps, a backup plan
can be created by setting Create backup plan to True in the dropdown list of the rehosting operations
window.
NetAct™ 16
© 2018 Nokia Solutions and Networks
39
Rehosting GSM BTS Sites
NetAct™ 16
DN98908338 2-1
© 2018 Nokia Solutions and Networks
Performing the rehosting operation
40
Rehosting GSM BTS Sites
DN98908338 2-1
Performing the rehosting operation
During each provision step of the operation a backup plan can be created by setting Create
BackupPlan to True in the dropdown list of the rehosting operations window.
4.3 Stopping measurements
Stop the BSC measurements with Administration of Measurements in the regional NetAct. This
applies only to the BSCs that are part of the rehosting operation. It is recommended that you stop the
measurements immediately.
For more information on how to stop measurements, see Deactivating plans in Administration of
Measurements Help.
NetAct™ 16
© 2018 Nokia Solutions and Networks
41
Rehosting GSM BTS Sites
DN98908338 2-1
Performing the rehosting operation
When stopping measurements, you also need to stop MO Upload cron tasks and take a BSC
software backup before proceeding with activation. For more information, see the Safecopying in BSC
document in the BSC documentation set.
4.4 Locking old BCFs
After locking, the administrative state for the selected old BCF(s) hierarchy is locked in NetAct and
BSC.
4.5 Activating maintenance mode for the BCFs in the old BSC
The maintenance mode is activated to avoid unnecessary alarm flow to NetAct from the old BCFs.
This operation reduces the load in the system by blocking unnecessary alarms coming to the
monitoring tools and database.
4.5.1 To activate the maintenance mode for the old BCFs
Activate the maintenance mode for the BCFs with Maintenance Mode. For instructions, see
Maintenance Mode Help.
4.6 Activating maintenance mode for the BTSs in NetAct Advanced
Configurator
In NetAct Advanced Configurator activate the maintenance mode for the BTSs with the Object
Explorer application in the regional NetAct. For instructions, see About Object Explorer in Object
Explorer Help.
4.7 Provisioning BTS site configuration plan in old BSC
Provisioning BTS site configuration plan in the old BSC creates a temporary plan for the changes in
the site configuration data of the selected BCFs and provisions the temporary plan in the old BSC.
Note:
This operation is valid only for S16_2 or higher BSCs and BCFs that require changes to BTS
site configuration (for example BCFs that are using Packet Abis).
Note:
The option to split successful and failed plans upon validation error is not available for this
provisioning operation by default.
NetAct™ 16
© 2018 Nokia Solutions and Networks
42
Rehosting GSM BTS Sites
DN98908338 2-1
Performing the rehosting operation
4.8 Cutting transmission over
Cutting transmission over is a manual task. It needs to be carried out by a field engineer by
establishing the physical links. In the Rehosting dialog it appears as a reminder task during the
execution of the Cutting transmission over operation.
4.9 Provisioning BTS in MSC (BTSM) update plan
In the Rehosting dialog you can provision BTS in the MSC update plan. For more information, see
Provisioning plans in CM Operations Manager Help.
After this operation:
• BTSMs are updated in old MSCs, when MSCs are the same for the old and new BSC and only
LAC is modified, or
• new BTSMs are created in old MSCs, when ID, CI, (LAC) and NW Name changes and MSCs are
the same for old and new BSC, or
• new BTSMs are created in new MSCs, when MSCs are different for old and new BSC
The system automatically unlocks the new BTSM after creation. BTSMs that are not needed after
rehosting will be deleted in the cleaning-up phase.
Rehosting Tool supports Multipoint A with the following restriction: if a BSCM object of a BSC exists
under several MSCs, all Location Areas of that BSC are considered pooled.
4.10 Provisioning an adjacency update plan
Provisioning adjacency update plan is performed in the Rehosting dialog. This operation redirects
the incoming adjacencies for selected BCF sites. For more information, see Provisioning plans in CM
Operations Manager Help.
After the adjacency update:
• Incoming adjacencies have been redirected in network and NetAct.
• Target Cell DN has been updated for adjacencies in NetAct.
4.11 Provisioning a cell reference update plan
Provisioning a cell reference update plan is performed in the Rehosting dialog. This operation
updates C/I-based handover parameters (reference cells for ADCEs), Interfering Cells (IUO) for TRXs,
and LCSEs.
After cell reference update:
NetAct™ 16
© 2018 Nokia Solutions and Networks
43
Rehosting GSM BTS Sites
DN98908338 2-1
Performing the rehosting operation
• The adjacencies LAC, if changed, and C/I-based handover parameters (reference cells for
ADCEs) and Interfering Cells (IUO) for TRXs are updated in NetAct and BSC, and the Target Cell
DN for adjacencies is updated in NetAct.
• In case there is related LCSE in the old BSC, then the new LCSE is created in the new BSC, if
that does not exist yet as alien. If in the new BSC an alien LCSE already exists, that is updated to
relate to the new BTS.
• When in the Delete related LCSEs in the old BSC drop-down list true is selected, then LCSEs
in the old BSC are deleted. When false is selected, then the related LCSEs in the old BSC are
updated to relate to the new BTS. Related LCSEs in other BSCs are updated to relate to the new
BTS.
In NetAct Advanced Configurator it is recommended to set option Delete related LCSEs to True
when the source and target BSCs are integrated to different NetAct regions. Alien LCSE modifications
are supported only when source BSC, target BSC, and BSC having alien LCSE are integrated to the
same regional NetAct.
4.12 Provisioning swap LACs update plan
Provisioning the swap LACs update plan shall be performed when keeping the same CI and LAC in
the old and new BSC. Dummy LAC (and RAC) is needed for BTSs and BTSMs in the preparation
phase.
After swapping LACs:
• Dummy LAC (and RAC) is updated in the old BTS and the correct LAC (and RAC) is updated in
the new BTS.
• Incoming adjacencies (ADCE, ADJG) are recreated, the reference cells for ADCEs are updated,
and the interfering cell (IUO) information is updated in the NetAct and BSC databases.
• If Location Services are used, the LCSEs LAC values are updated in NetAct and BSC.
• BTS in MSC is updated for the selected BCF sites in NetAct and MSC.
When GPRS is enabled in the new BSC (BTS parameter GPRS enabled in true) and a dummy LAC
is used, then a dummy value should be given for the RAC also by the user. The dummy RAC is
swapped in BTSs and incoming adjacencies (ADCE) for the selected BCF sites at the same time when
swapping the LAC.
The Upload new BSC operation needs to be run to have data fill updated and BSC and NetAct
database consistent.
Note:
In NetAct Advanced Configurator use a different location area LAC in the source and target
BSC when the source and target BSC are integrated to different NetAct regions and one of
following functionalities is used in the rehosted site:
• reference cells for ADCE
• interferring cell (IUO) information in TRX
NetAct™ 16
© 2018 Nokia Solutions and Networks
44
Rehosting GSM BTS Sites
DN98908338 2-1
Performing the rehosting operation
• location service LCSE
For more information, see Provisioning plans in CM Operations Manager Help.
4.13 Uploading a new BSC
This operation is performed in the Rehosting dialog.
The operation uploads the new BSC to have consistent BSC and NetAct databases. In NetAct,
adjacencies may point to old BTSs (Target Cell DN of the adjacencies has an old value) until a
new BSC has been uploaded. Note that in network the adjacencies are correctly defined.
For more information, see Provisioning plans in CM Operations Manager Help.
4.14 Uploading old and new BSC in NetAct Advanced Configurator
In NetAct Advanced Configurator uploading an old and new BSC needs to be carried out manually.
Upload an old BSC with the source regional NetAct and a new BSC with the target regional NetAct.
Operation is needed only when operation Provision Swap LACs Update Plan is run. The operation can
be marked completed for bookkeeping purposes.
4.15 Activating BSC-BTS connections with MMLs
This operation is a manual task. It needs to be carried out by the field engineer either by activating the
SCTP associations for Packet Abis LAPD links or opening the pseudowire tunneling for sites using
pseudowire configuration. In the Rehosting dialog it appears as a reminder task during the execution
of activating SCTP associations.
Note:
TRXSIG SCTP associations are not directly changed to ASP-ACTIVE state after activation
with MML, but they are automatically switched to ASP-ACTIVE state after the new BTS site
has been unlocked.
4.16 Uploading BTS SC data from the new BSC
Uploading BTS data means that BTS Site Configuration data of the rehosted BTSs is uploaded via the
new BSC to the NetAct database.
If RF sharing is in use, BSC relationship (using BCF object) is created under MRSITE automatically
after upload. You do not need to create new MRSITE objects under the BSCs.
NetAct™ 16
© 2018 Nokia Solutions and Networks
45
Rehosting GSM BTS Sites
DN98908338 2-1
Performing the rehosting operation
Note:
This operation is valid only for S16_2 or higher BSCs and BCFs that require changes to BTS
site configuration (for example, BCFs that are using Packet Abis).
This operation is not supported in NetAct Advanced Configurator and needs to be executed in the
regional NetAct.
4.17 Uploading BTS SC data from the new BSC in NetAct Advanced
Configurator
In NetAct Advanced Configurator uploading BTS SC data from the new BSC needs to be carried out
manually. Upload BTS SC data from a new BSC with the target regional NetAct. The operation can be
marked completed for bookkeeping purposes.
4.18 Deactivating maintenance mode for BCFs in the new BSC
Deactivate the maintenance mode for BCFs with the Monitor application. For instructions, see About
maintenance mode in Maintenance Mode Help.
This operation is not supported in NetAct Advanced Configurator and needs to be executed in the
regional NetAct.
4.19 Unlocking new BCFs
This operation is performed in the Rehosting dialog and unlocks the selected new sites.
After Unlock the Administrative state for the selected new BCF(s), the hierarchy is unlocked in NetAct
and BSC.
4.20 Updating references in NetAct databases
This operation performs the following:
• Update the antenna reference data
Linked Cell DN for GCAL
• Update the SITE references
Site ID for BCF
• Update the PM database
Update the BCF, BTS AND TRX global identifiers and BTS Segment IDs for Reporter use.
NetAct™ 16
© 2018 Nokia Solutions and Networks
46
Rehosting GSM BTS Sites
DN98908338 2-1
Performing the rehosting operation
• Updates hardware data for BTSs.
Note: In NetAct Advanced Configurator some tasks are replaced with manual operations.
4.21 Updating references in NetAct databases in NetAct Advanced
Configurator
This operation performs the following in NetAct Advanced Configurator:
• Update the antenna reference data Linked Cell DN for GCAL.
• Update the SITE references Site ID for BCF.
4.22 Updating references in regional NetAct
In NetAct Advanced Configurator this is a reminder task for updating the references for the rehosted
site in the old and new regional NetAct. The listed updates cannot be made with NetAct Advanced
Configurator. Upload the license status with License Manager, upload software information with
Software Manager, and copy the rehosted site object notes from the old regional NetAct Monitor to the
new NetAct region. The operation can be marked completed for bookkeeping purposes.
4.23 Refreshing BSC topology in Q3/MML mediation
If BSC counters or performace indicators are enabled on a BSC, the BSC topology should be
refreshed in the Q3/MML mediation. This step is needed to synchronize measurement data with
topology changes which can occur on BSCs after rehosting.
For more information, see Refreshing BSC topology in Q3/MML mediation in Administering Q3/MML
Southbound Interface.
4.24 Checking the state of the objects
Check the state of the managed objects with CM Editor.
This operation is not supported in NetAct Advanced Configurator and needs to be executed in the
regional NetAct.
NetAct™ 16
© 2018 Nokia Solutions and Networks
47
Rehosting GSM BTS Sites
DN98908338 2-1
Performing the rehosting operation
4.24.1 To check the state of the managed objects
1. Start CM Editor.
2. Under the actual configuration, select the BCFs to be rehosted.
3. Select ZEEI under the Actual menu to see that the objects are 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)
NetAct™ 16
© 2018 Nokia Solutions and Networks
48
Rehosting GSM BTS Sites
DN98908338 2-1
Cleaning up
5 Cleaning up
This chapter describes the clean-up operations related to rehosting a GSM BTS site.
5.1 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 carry out the various steps. Click a process in the figure for more information.
During each provision step of the operation a backup plan can be created by setting Create
BackupPlan to True in the dropdown list of the rehosting operations window.
NetAct™ 16
© 2018 Nokia Solutions and Networks
49
Rehosting GSM BTS Sites
DN98908338 2-1
Cleaning up
5.2 Overview of the clean-up phase in NetAct Advanced Configurator
The following flowchart gives you an overview of the clean-up phase as well as the tools that you can
use to carry out the various steps. Click a process in the figure for more information.
During each provision step of the operation a backup plan can be created by setting Create
BackupPlan to True in the dropdown list of the rehosting operations window.
5.3 Provisioning an RNW deletion plan
The Provision deletion plan operation locks LAPDs, and deletes unused DAPs, CSDAPs, HDLCs,
LAPDs, LMUAs, BCFs including child objects, outgoing adjacencies (ADCE, ADJG) in the old BSC in
the NetAct database.
NetAct™ 16
© 2018 Nokia Solutions and Networks
50
Rehosting GSM BTS Sites
DN98908338 2-1
Cleaning up
This operation also deletes the BTSM in the old MSC when the MSC is changed, or when the MSC
remains the same and a new BTSM is created because ID, CI, (LAC) and NW Name have changed
for the BTSM.
If RF sharing is in use, old BSC relationship (under BCF) is removed from MRSITE and NetAct
database.
If CM HW Management for GSM is in use, the HW objects and their child objects are deleted from the
old BTSs.
For more information, see Provisioning plans in CM Operations Manager Help.
5.4 Removing external cells from the old region in NetAct Advanced
Configurator
In NetAct Advanced Configurator this is a reminder task for removing unused external cells from the
old NetAct region.
Run CM Analyzer checks UnusedExenbf, UnusedExeuce, UnusedExuce, and UnusedExgce to
identify unused LTE, WCDMA, and GSM external cells from the old NetAct region. Create a correction
plan and provision the correction plan to remove the unused LTE, WCDMA, and GSM external cells.
The operation can be marked completed for bookkeeping purposes.
5.5 Deleting old objects and views
Delete the old objects and views in the NetAct database with the regional NetAct Monitor.
For more information, see About Network View in Network View Help.
Note: Delete CM and FM non-agent managed objects.
For more information, see Deleting non-agent managed objects in Object Explorer Help.
5.6 Restarting measurement collection
Restart the measurements on the BSC with Administration of Measurements in the regional NetAct.
For more information on how to restart measurements, see About Administration of Measurements in
Administration of Measurements Help.
5.7 Restarting the scheduled TRX loop tests
Create new TRX loop tests for the rehosted objects. Start the loop tests with CM Operations Manager
in the regional NetAct.
NetAct™ 16
© 2018 Nokia Solutions and Networks
51
Rehosting GSM BTS Sites
DN98908338 2-1
Cleaning up
For more information, see TRX Loop Test in CM Operations Manager Help and Scheduling operations
in CM Operations Manager Help.
5.8 Checking performance
After completing the rehosting operation, you should check 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
5.9 Deleting a rehosting plan
Delete a rehosting plan with CM Operations Manager or CM Editor.
NetAct™ 16
© 2018 Nokia Solutions and Networks
52
Rehosting GSM BTS Sites
DN98908338 2-1
Customizing Rehosting Tool
6 Customizing Rehosting Tool
This chapter covers customization of the Rehosting Tool.
You can customize the following:
• Rehosting views
• Rehosting wizard files
• Rehosting operation lists
• Object dropping to rehosting tool
In the Rehosting Tool rehost file transfer dialog you can transfer files from your local computer to
NetAct file system:
Target folder in dialog
Location in NetAct file system
Rehosting Wizard files custom folder
/etc/opt/nokia/oss/custom/conf/rac/wizard/
rehosting3g
Rehosting Operation List files custom folder
/etc/opt/nokia/oss/custom/conf/rac/opdefs/
oplists/rehosting3g
Rehosting Operation Description files custom folder
/etc/opt/nokia/oss/custom/conf/rac/opdefs/
ops/rehosting3g
Rehosting custom files folder
/var/opt/nokia/oss/global/racrsv/customfiles
Table 14: Folder locations
Note:
File transfer dialog is only visible for users that have the Rac Rehost Administration
Operation permission enabled.
6.1 Creating a customized rehosting view
This is an optional task and should be performed by an administrator.
The Rehosting GSM BTS Sites view is the default rehosting CM view that defines the object classes
and parameters that are visible in the data fill pane. If the default rehosting CM view does not contain
all the parameters that you need, you can create a customized rehosting view. You can also remove
parameters from the rehosting view.
Note:
New object classes cannot be added to the view.
For more information on the related parameters, see Appendix A: Rehosting CM view parameters.
NetAct™ 16
© 2018 Nokia Solutions and Networks
53
Rehosting GSM BTS Sites
DN98908338 2-1
Customizing Rehosting Tool
6.1.1 To create a customized rehosting CM view in CM Editor
If you want to customize the rehosting CM view, you can create a new CM view in CM Editor. In
this case, use the default rehosting CM view as a template for your own view. To see the new view
in CM Operations Manager, first close the Rehosting dialog in CM Operations Manager and then
open it again. The new view has to be updated in CM Editor before you can select it from the CM
view list in CM Operations Manager.
For instructions, see Creating a new editor view from a selected view in CM Editor Help.
6.2 Creating a customized operation list
This is an optional task and should be performed by an administrator.
You can create a customized operation list if necessary. To view the operations included in the default
operation list, open the Rehosting dialog in CM Operations Manager, and select Rehosting GSM BTS
sites in the operation list.
You can add, modify, and delete operations in the operation list. You can also change the order of
the operations in the list. However, if you change the order, the Rehosting dialog in CM Operations
Manager does not check if the order in which the rehosting operations are performed is logical.
This is an optional task and should be performed by an administrator.
Note:
To avoid problems with the customized operations list and operation definition files in
$ETCROOT/rac/conf/opdefs/ops/rehosting2g/ and $ETCROOT/rac/conf/
opdefs/oplists/rehosting2g/ directories, the files are renamed to non-xml extension
files during an OSS upgrade. This is to avoid problems when for example, syntax for the files
has changed and therefore the files become unusable with Rehosting Tool.
6.2.1 To create a customized rehosting operation list
1. Log as omc user into the Virtual Machine where WebSphere application server is installed.
2. Create a copy of the default rehosting operation list. The list is located in $ETCROOT/rac/conf/
opdefs/oplists/rehosting2g/rehostinglist2g.xml.
3. Copy the file to $ETCROOT/custom/conf/rac/opdefs/oplists/rehosting2g/.
You need to change the name of the file to distinguish the new file from the old one.
4. Modify the file with any text editor. You need to change the name of the list (oplist name) in the
file to distinguish the new list from the old one in the user interface.
NetAct™ 16
© 2018 Nokia Solutions and Networks
54
Rehosting GSM BTS Sites
DN98908338 2-1
Customizing Rehosting Tool
The attributes in the operationInfo element define the following in the operation’s dialog of the
CM Operations Manager user interface:
• type attribute defines the name of the operation.
Note that the type attribute values of this operationInfo element have to match the type
attribute values of the operationInfo element in the rehosting operations file (located in
$ETCROOT/custom/conf/rac/opdefs/ops/rehosting2g/). See the following example:
operationInfo element in the operation list file:
<operationInfo type="Create file for external system"
description="Operation runs script that creates file of rehosted
objects to be used in external system."shortDescription="Execute
script"/>
• description attribute defines the operation’s description that is visible in the operation list’s
tooltip, and in the Operation Start dialog.
• shortDescription attribute defines the text on the button in the Operation Start dialog.
Note:
If there are faults in the customized list(s), the list does not appear in the Operation List
drop-down list.
Possible errors are logged in the server logs. For more information about logging, see document
Configurator in NetAct Logging Reference.The following errors, for example, can prevent the use
of the operation list:
• The XML syntax is not valid.
• The XML files in the same directory declare similarly named operation lists twice.
• The XML files in the same directory declare two or more operationInfo elements that have
the same value in the type attribute.
• There is one-to-one relation between operationInfo in the operation list file and the
rehosting operation file. If the operation list refers to a non-existing operationInfo, it results
in an error. Also, if the operation list refers to the same operationInfo more than once, it
results in an error.
Once the error is corrected, the lists are usable again. When you make changes in the XML
files, the changes become visible in the system within a few minutes.
The system searches the following directories for XML files (that is, files ending in ”.xml”):
• $ETCROOT/custom/conf/rac/opdefs/oplists/rehosting2g/
• $ETCROOT/custom/conf/rac/opdefs/ops/rehosting2g/
• $ETCROOT/rac/conf/opdefs/oplists/rehosting2g/
• $ETCROOT/rac/conf/opdefs/ops/rehosting2g/
The system checks which operation lists and operationInfo elements are defined in the found
XML files, and if there are operation lists or operationInfo elements that have the same name
NetAct™ 16
© 2018 Nokia Solutions and Networks
55
Rehosting GSM BTS Sites
DN98908338 2-1
Customizing Rehosting Tool
both in the $ETCROOT/custom directory and the $ETCROOT/rac directory, the system uses the
data found in the $ETCROOT/custom directory.
6.2.2 Creating script operations
This is an optional task and should be performed by an administrator.
If you create new script operations, the operation list needs to be updated once the operations are
created. In the rehosting operation list file (located in $ETCROOT/custom/conf/rac/opdefs/
oplists/rehosting2g/), add a new operationInfo element.
For an example of a script operation file, see the following script operation file including the
operationInfo element.
<operationInfo type="Create file for external system"
description="Operation runs script that creates file of rehosted objects
to be used in external system." shortDescription="Execute script"/>
Example: Create file for external system
<?xml version=”1.0” encoding=”UTF-8”?>
<!DOCTYPE ops SYSTEM “ops11.dtd”>
<ops>
<operationInfo type=”Create file for external system” name=”Create file
for external system” description=”Operation runs script that creates
file of rehosted objects to be used in external system.”>
<operationDef type=”Script execution” operation=”scriptExecution”>
<attr name=”execTargetCommand”>:concat ("sh path/your_script.sh") />
</operationDef>
</operationInfo>
</ops>
6.2.2.1 To create script operations
1. Log as omc user into the Virtual Machine where WebSphere application server is installed.
2. Create a copy of the default rehosting operations. The operations are located in $ETCROOT/rac/
conf/opdefs/ops/rehosting2g/.
3. Copy the file to $ETCROOT/custom/conf/rac/opdefs/ops/rehosting2g/.
4. Modify the file with any text editor.
You can add new operations and modify the default ones. However, note the following:
• The type attribute of the operationInfo element in the rehosting operations file identifies
the operation. Thus, when you add a new operation, you need to create an operationInfo
element with another type attribute value than what the default rehosting operations in the
$ETCROOT/rac/conf/opdefs/ops/rehosting2g/rehosting2g.xml file have.
NetAct™ 16
© 2018 Nokia Solutions and Networks
56
Rehosting GSM BTS Sites
DN98908338 2-1
Customizing Rehosting Tool
• After creating the new operation, the operation list needs to be updated. For instructions, see
To create a customized rehosting operation list.
• If there are operations in the $ETCROOT/custom/conf/rac/opdefs/ops/rehosting2g/
rehosting2g.xml file that are not modified, remove them. The operations in this file
override the default operations in the $ETCROOT/rac/conf/opdefs/ops/rehosting2g/
rehosting2g.xml file, so if there are operations that are not modified, they need to be
removed.
5. Save the operations file.
6.3 Creating a customized wizard file
This is an optional task and should be performed by an administrator.
You can create a customized wizard file, if necessary.
For an example of a wizard file, see the BCF object parameters declaration in the default wizard file.
6.3.1 To create a customized wizard file
1. Log as omc user into the Virtual Machine where WebSphere application server is installed.
2. Create a copy of the default wizard file. The file is located in
$ETCROOT/rac/conf/wizard/rehosting2g/2g_rehosting_wizard.xml.
3. Copy the file to $ETCROOT/custom/conf/rac/wizard/rehosting2g.
4. Rename the file.
5. Modify the file with any text editor.
You can add new objects which you want to include in the Rehosting Wizard dialog and modify
the default ones.
Note:
Only objects supported by the Rehosting CM View can be included in the Rehosting
Wizard dialog. For more information, see appendix Appendix A: Rehosting CM view
parameters.
Before starting the file edition, it is recommended to familiarize with the overall file structure. site
is the root element which contains one or more group elements. Each group can have one or
more item elements and each item element can contain one or more parameter elements.
parameter element can have zero or more copyTo elements.The Rehosting Wizard dialog
generates the data for each site that is dropped to the data fill based on a selected XML file.
Groups and their items’ parameters are visible in the Rehosting Wizard dialog only if they
NetAct™ 16
© 2018 Nokia Solutions and Networks
57
Rehosting GSM BTS Sites
DN98908338 2-1
Customizing Rehosting Tool
contain at least one visible parameter. copyTo elements are not visible in the Rehosting Wizard
dialog, they only define to what object a parameter’s value is copied to.
For a description of possible XML parameters and special values, see appendix Possible
parameters and special values.
6. Save the wizard file.
NetAct™ 16
© 2018 Nokia Solutions and Networks
58
Rehosting GSM BTS Sites
DN98908338 2-1
Reverting back to the old configuration
7 Reverting back to the old configuration
It is highly recommended that you take backup plans. During each provision step of the operation
a backup plan can be created by setting Create BackupPlan to True in the dropdown list of the
rehosting operations window.
It is possible to revert back to the old configuration after the following operations if the site
configuration data has not been modified in the rehosting:
Before the Provision BTS in MSC Update Plan operation:
• Manually switch physical links back to the old configuration.
Before the Provision Adjacency Update Plan operation:
• Manually switch physical back to the old configuration.
• Create and provision the backup plan for modifying old BTSMs in case the MSC in the old and
new BSC is the same.
Before the Provision Cell Reference Update Plan operation:
• Manually switch physical links back to the old configuration.
• Create and provision the backup plan for modifying old BTSMs in case the MSCs in the old and
new BSC are the same.
• Create and provision the backup plan for redirecting incoming adjacencies.
NetAct™ 16
© 2018 Nokia Solutions and Networks
59
Rehosting GSM BTS Sites
DN98908338 2-1
Troubleshooting guidelines for rehosting
GSM BTS sites
8 Troubleshooting guidelines for rehosting GSM BTS
sites
General checks:
• Is the NetAct database consistent with the Network for rehosted sites.
• Is the connection from NetAct working to element (BSCs, BTSs and MSCs).
• Are the RNW events working for BSCs and all the element having incoming adjacencies for the
rehosted sites.
• Is everything planned correctly in datafill.
8.1 Send files to customer support
In case of problems during rehosting GSM BTS Sites, the following files should be taken and sent to
the customer support:
Before rehosting
Actual configuration files from source BSC and target BSC.
During rehosting
1. Configuration files from following rehosting plans:
• Rehosting plan
Example:
• rehome.xml
• Rehosting Operation plans
Examples:
• rehome_RNWCreationPlan_<time_stamp>.xml
• rehome_LockPlan_<time_stamp>.xml
• rehome_ScCreationPlan_<time_stamp>.xml
• rehome_MSCCreationPlan_<time_stamp>.xml
• rehome_Update2GAdjacenciesPlan_<time_stamp>.xml
• rehome_UpdateCGIPlan_<time_stamp>.xml
• rehome_UpdateLCSEPlan_<time_stamp>.xml
• rehome_SwapLACsPlan_<time_stamp>.xml
• rehome_UpdateMRSitePlan_<time_stamp>.xml
• rehome_UpdateAntennaPlan_<time_stamp>.xml
• rehome_UnlockPlan_<time_stamp>.xml
• rehome_RNWDeletionPlan_<time_stamp>.xml
NetAct™ 16
© 2018 Nokia Solutions and Networks
60
Rehosting GSM BTS Sites
DN98908338 2-1
Troubleshooting guidelines for rehosting
GSM BTS sites
2. Feedbacks of Rehosting Operations from rehosting tool
Example of how to get the LockPlan provision feedback:
a. Wait until operation finishes.
b. Select operation, for example, LockPlan from the rehosting tool’s Operation history.
c. Click right mouse button -> View feedback.
d. From feedback window select All feedback.
e. Press Export button.
After rehosting
1. Log files from Virtual Machine with Q3 service.
Examples:
• /var/opt/oss/log/q3user/oss_error*_*.log
• /var/opt/oss/log/q3user/oss_activity*_*.log
For more information about Q3 service logs for NetAct Configurator, see Log files for Configuration
Management in NetAct Logging Reference.
For more information about Q3/MML southband interface log files, see Q3/MML log files in
Administering Q3/MML Southbound Interface.
2. Actual configuration files from source BSC and target BSC.
8.2 Enable rehost-specific temporary plans
You can generate rehost-specific temporary plans when running rehosting operations that require plan
provisioning from Rehosting Tool. By enabling the generation of the rehost-specific plans, it is possible
to run rehosting operations without provisioning the plan to the network.
The option for enabling this, rehostingPlanGenerationOperation is not shown
by default in the Operation Start dialog. You can activate the rehost-specific plan
generation option by setting the Java environment variable JAVAWS_VM_ARGS to value
Dracopc.rehost.plan.only.generation.enabled=true. Plan prepare is not run for the
generated plan.
Note: Since Java 7 update 45 you can activate the rehost-specific plan generation
option by setting the Java enviroment variable _JAVA_OPTIONS with value Dracopc.rehost.plan.only.generation.enabled=true
You can also create a plan without provisioning by setting "Generate plans only" to true in the plan
creation dialog. Plan prepare is not run for the generated plan.
NetAct™ 16
© 2018 Nokia Solutions and Networks
61
Rehosting GSM BTS Sites
DN98908338 2-1
Appendix A: Rehosting CM view
parameters
9 Appendix A: Rehosting CM view parameters
Parameter
Full name
GSM Rehosting Wizard
$instance
Instance id
Entered by user in 2G Wizard GUI.
adminState
Administrative State
Copied from old.
bcfHdlcIdList
BCF HDLC ID list
Set automatically based on predefined
definitions in GSM Rehosting Wizard
XML file.
btsCuPlaneIpAddress
BTS C/U-plane IP Address
Entered by user in 2G Wizard GUI or
set automatically based on predefined
definitions in GSM Rehosting Wizard
XML file.
btsIpv4SubnetMasklengthCUplane
BTS IPv4 Subnet Mask Length for C/U-
Entered by user in 2G Wizard GUI or
plane
set automatically based on predefined
definitions in GSM Rehosting Wizard
XML file.
btsIpv4SubnetMasklengthMplane
BTS IPv4 Subnet Mask Length for M-
Set automatically based on predefined
plane
definitions in GSM Rehosting Wizard
XML file.
btsMPlaneIpAddress
BTS M-plane IP address
Set automatically based on predefined
definitions in GSM Rehosting Wizard
XML file.
csdapId1
Attached CSDAP 1
Set automatically based on predefined
definitions in GSM Rehosting Wizard
XML file.
csdapId2
Attached CSDAP 2
Set automatically based on predefined
definitions in GSM Rehosting Wizard
XML file.
csdapId3
Attached CSDAP 3
Set automatically based on predefined
definitions in GSM Rehosting Wizard
XML file.
csdapId4
Attached CSDAP 4
Set automatically based on predefined
definitions in GSM Rehosting Wizard
XML file.
lapdLinkName
LAPD Link Name
Set automatically based on predefined
definitions in GSM Rehosting Wizard
XML file.
NetAct™ 16
lapdLinkNumber
LAPD Link Number
Copied from old.
name
Name
Entered by user in 2G Wizard GUI.
© 2018 Nokia Solutions and Networks
62
Rehosting GSM BTS Sites
DN98908338 2-1
Appendix A: Rehosting CM view
parameters
Parameter
Full name
GSM Rehosting Wizard
pcmPortId0
PCM Port ID 0
Set automatically based on predefined
definitions in GSM Rehosting Wizard
XML file.
pcmPortId1
PCM Port ID 1
Set automatically based on predefined
definitions in GSM Rehosting Wizard
XML file.
pcmPortId2
PCM Port ID 2
Set automatically based on predefined
definitions in GSM Rehosting Wizard
XML file.
pcmPortId3
PCM Port ID 3
Set automatically based on predefined
definitions in GSM Rehosting Wizard
XML file.
pcmPortId4
PCM Port ID 4
Set automatically based on predefined
definitions in GSM Rehosting Wizard
XML file.
pcmPortId5
PCM Port ID 5
Set automatically based on predefined
definitions in GSM Rehosting Wizard
XML file.
pcmPortId6
PCM Port ID 6
Set automatically based on predefined
definitions in GSM Rehosting Wizard
XML file.
pcmPortId7
PCM Port ID 7
Set automatically based on predefined
definitions in GSM Rehosting Wizard
XML file.
usedEtpId
Used ETP ID
Entered by user in 2G Wizard GUI or
set automatically based on predefined
definitions in GSM Rehosting Wizard
XML file.
vlanId
Vlan ID
Entered by user in 2G Wizard GUI or
set automatically based on predefined
definitions in GSM Rehosting Wizard
XML file.
Table 15: NOKBSC:BCF
NetAct™ 16
Parameter
Full name
GSM Rehosting Wizard
$instance
Instance id
Entered by user in 2G Wizard GUI.
adminState
Administrative State
Copied from old.
locationAreaIdLAC
LAC
Entered by user in 2G Wizard GUI.
© 2018 Nokia Solutions and Networks
63
Rehosting GSM BTS Sites
DN98908338 2-1
Appendix A: Rehosting CM view
parameters
Parameter
Full name
GSM Rehosting Wizard
name
Name
Set automatically based on predefined
definitions in GSM Rehosting Wizard
XML file.
rac
RAC
Entered by user in 2G Wizard GUI.
segmentId
Segment ID
Set automatically based on predefined
definitions in GSM Rehosting Wizard
XML file.
Table 16: NOKBSC:BTS
Parameter
Full name
GSM Rehosting Wizard
$instance
Instance id
Entered by user in 2G Wizard GUI.
name
Name
Set automatically based on predefined
definitions in GSM Rehosting Wizard
XML file.
pcmCircuit_ID
PCM Circuit ID
Entered by user in 2G Wizard GUI.
Parameter
Full name
GSM Rehosting Wizard
$instance
Instance id
Entered by user in 2G Wizard GUI.
bcsuID
BCSU ID
Entered by user in 2G Wizard GUI.
name
Name
Set automatically based on predefined
Table 17: NOKBSC:CSDAP
definitions in GSM Rehosting Wizard
XML file.
pcmCircuit_ID
PCM Circuit ID
Set automatically based on predefined
definitions in GSM Rehosting Wizard
XML file.
pcuID
PCU Index
Entered by user in 2G Wizard GUI.
Parameter
Full name
GSM Rehosting Wizard
$instance
Instance id
Entered by user in 2G Wizard GUI.
hdlcAdministrativeState
HDLC Administrative State
Copied from old.
hdlcPcmId
HDLC PCM ID
Entered by user in 2G Wizard GUI.
Table 18: NOKBSC:DAP
NetAct™ 16
© 2018 Nokia Solutions and Networks
64
Rehosting GSM BTS Sites
DN98908338 2-1
Appendix A: Rehosting CM view
parameters
Parameter
Full name
GSM Rehosting Wizard
name
Name
Set automatically based on predefined
definitions in GSM Rehosting Wizard
XML file.
Table 19: NOKBSC:HDLC
Parameter
Full name
GSM Rehosting Wizard
$instance
Instance id
Set automatically based on predefined
definitions in GSM Rehosting Wizard
XML file.
abisSigChannelTimeSlotPcm
PCM
Entered by user in 2G Wizard GUI.
adminState
Administrative State
Copied from old.
associationName
Association Name
Entered by user in 2G Wizard GUI.
name
Name
Entered by user in 2G Wizard GUI.
Parameter
Full name
GSM Rehosting Wizard
$instance
Instance id
Set automatically based on predefined
Table 20: NOKBSC:LAPD
definitions in GSM Rehosting Wizard
XML file.
adminState
Administrative State
Copied from old.
channel0Pcm
Channel 0 PCM
Set automatically based on predefined
definitions in GSM Rehosting Wizard
XML file.
daPool_ID
DAP ID
Set automatically based on predefined
definitions in GSM Rehosting Wizard
XML file.
lapdLinkName
LAPD Link Name
Set automatically based on predefined
definitions in GSM Rehosting Wizard
XML file.
lapdLinkNumber
LAPD Link Number
Copied from old.
name
Name
Set automatically based on predefined
definitions in GSM Rehosting Wizard
XML file.
NetAct™ 16
© 2018 Nokia Solutions and Networks
65
Rehosting GSM BTS Sites
DN98908338 2-1
Appendix A: Rehosting CM view
parameters
Table 21: NOKBSC:TRX
Parameter
Full name
GSM Rehosting Wizard
$instance
Instance id
Copied from old.
bcfId
BCF identifier
Set automatically based on predefined
definitions in GSM Rehosting Wizard
XML file.
bscId
BSC Identifier
Set automatically based on predefined
definitions in GSM Rehosting Wizard
XML file.
bscName
BSC Name
Set automatically based on predefined
definitions in GSM Rehosting Wizard
XML file.
Table 22: NOKBTSF:BTSNE
Parameter
Full name
GSM Rehosting Wizard
$instance
Instance id
Copied from old.
ipRouting
IP Routing List
Copied from old.
Parameter
Full name
GSM Rehosting Wizard
$instance
Instance id
Set automatically based on predefined
Table 23: NOKBTSF:IPRTAB
definitions in GSM Rehosting Wizard
XML file.
tunnelSettings
Tunnel Settings List
Entered by user in 2G Wizard GUI.
Parameter
Full name
GSM Rehosting Wizard
$instance
Instance id
Set automatically based on predefined
Table 24: NOKBTSF:IPSEC
definitions in GSM Rehosting Wizard
XML file.
remoteMepList
Remote Maintenance End Point
Entered by user in 2G Wizard GUI.
Identifier
vlanId
VLAN Identifier of Maintenance
Set automatically based on predefined
Association
definitions in GSM Rehosting Wizard
XML file.
NetAct™ 16
© 2018 Nokia Solutions and Networks
66
Rehosting GSM BTS Sites
DN98908338 2-1
Appendix A: Rehosting CM view
parameters
Table 25: NOKBTSF:OAMMA
Parameter
Full name
GSM Rehosting Wizard
cuPlaneBackupGatewayIPAddress
CU-Plane Backup Gateway IP Address
Entered by user in 2G Wizard GUI.
mPlaneBackupGatewayIPAddress
M-Plane Backup Gateway IP Address
Entered by user in 2G Wizard GUI.
mPlaneBackupRemoteIPAddress
M-Plane Backup BSC IP Address
Entered by user in 2G Wizard GUI.
cuPlaneBackupVlanId
CU-Plane Backup Vlan ID
Entered by user in 2G Wizard GUI.
mPlaneBackupVlanId
M-Plane Backup Vlan ID
Entered by user in 2G Wizard GUI.
Parameter
Full name
GSM Rehosting Wizard
$instance
Instance id
Copied from old.
cPlaneVlanId
C and U Plane Vlan Identifier
Entered by user in 2G Wizard GUI.
cuPlaneGatewayIpAddress
C-U Plane Gateway IP address
Set automatically based on predefined
Table 26: NOKBTSF:PABBAC
definitions in GSM Rehosting Wizard
XML file.
mPlaneGatewayIpAddress
M Plane Gateway IP Address
Entered by user in 2G Wizard GUI or
set automatically based on predefined
definitions in GSM Rehosting Wizard
XML file.
mPlaneLocalIpAddress
M Plane Local IP Address
Entered by user in 2G Wizard GUI.
mPlaneRemoteIpAddress
M Plane Remote Ip Address
Entered by user in 2G Wizard GUI.
mPlaneSubnetMask
M Plane Subnet Mask
Entered by user in 2G Wizard GUI.
mPlaneVlanId
M Plane Vlan Identifier
Entered by user in 2G Wizard GUI.
Parameter
Full name
GSM Rehosting Wizard
$instance
Instance id
Copied from old.
chapAuthentication
CHAP Authentication List
Copied from old.
papAuthentication
PAP Authentication List
Copied from old.
Table 27: NOKBTSF:PABTRS
NetAct™ 16
© 2018 Nokia Solutions and Networks
67
Rehosting GSM BTS Sites
DN98908338 2-1
Appendix A: Rehosting CM view
parameters
Table 28: NOKBTSF:PPPATH
Structure
Parameter
Full name
GSM Rehosting Wizard
$instance
Instance id
Copied from old.
psnTunnelConfig
PSN Tunnel Configuration
List
gatewayIPAddress
Gateway IP Address
Copied from old.
localIPAddress
Local IP Address
Copied from old.
remoteIPAddress
Remote IP Address
Copied from old.
subnetMask
Subnet Mask
Copied from old.
pwSettings
Pseudowire Settings List
localUDPPort
Local UDP Port
Copied from old.
remoteUDPPort
Remote UDP Port
Copied from old.
Table 29: NOKBTSF:PWCONF
Parameter
Full name
GSM Rehosting Wizard
$instance
Instance id
Copied from old.
minSctpPort
Minimum SCTP Port
Entered by user in 2G Wizard GUI.
Parameter
Full name
GSM Rehosting Wizard
$instance
Instance id
Set automatically based on predefined
Table 30: NOKBTSF:SCTP
definitions in GSM Rehosting Wizard
XML file.
sseSettings
SSE Settings List
Entered by user in 2G Wizard GUI.
Parameter
Full name
GSM Rehosting Wizard
$instance
Instance id
Copied from old.
bcfId
BCF identifier
Set automatically based on predefined
Table 31: NOKBTSF:SSE
definitions in GSM Rehosting Wizard
XML file.
NetAct™ 16
© 2018 Nokia Solutions and Networks
68
Rehosting GSM BTS Sites
DN98908338 2-1
Appendix A: Rehosting CM view
parameters
Parameter
Full name
GSM Rehosting Wizard
bscId
BSC Identifier
Set automatically based on predefined
definitions in GSM Rehosting Wizard
XML file.
bscName
BSC Name
Set automatically based on predefined
definitions in GSM Rehosting Wizard
XML file.
Table 32: NOKBTSFM:BTSNE
Parameter
Full name
GSM Rehosting Wizard
$instance
Instance id
Copied from old.
ipRouting
IP Routing List
Copied from old.
Parameter
Full name
GSM Rehosting Wizard
$instance
Instance id
Set automatically based on predefined
Table 33: NOKBTSFM:IPRTAB
definitions in GSM Rehosting Wizard
XML file.
tunnelSettings
Tunnel Settings List
Entered by user in 2G Wizard GUI.
Parameter
Full name
GSM Rehosting Wizard
$instance
Instance id
Set automatically based on predefined
Table 34: NOKBTSFM:IPSEC
definitions in GSM Rehosting Wizard
XML file.
remoteMepList
Remote Maintenance End Point
Entered by user in 2G Wizard GUI.
Identifier
vlanId
VLAN Identifier of Maintenance
Set automatically based on predefined
Association
definitions in GSM Rehosting Wizard
XML file.
Table 35: NOKBTSFM:OAMMA
NetAct™ 16
Parameter
Full name
GSM Rehosting Wizard
$instance
Instance id
Copied from old.
cPlaneVlanId
C and U Plane Vlan Identifier
Entered by user in 2G Wizard GUI.
© 2018 Nokia Solutions and Networks
69
Rehosting GSM BTS Sites
DN98908338 2-1
Appendix A: Rehosting CM view
parameters
Parameter
Full name
GSM Rehosting Wizard
cuPlaneGatewayIpAddress
C-U Plane Gateway IP address
Set automatically based on predefined
definitions in GSM Rehosting Wizard
XML file.
mPlaneGatewayIpAddress
M Plane Gateway IP Address
Entered by user in 2G Wizard GUI or
set automatically based on predefined
definitions in GSM Rehosting Wizard
XML file.
mPlaneLocalIpAddress
M Plane Local IP Address
Entered by user in 2G Wizard GUI.
mPlaneRemoteIpAddress
M Plane Remote Ip Address
Entered by user in 2G Wizard GUI.
mPlaneSubnetMask
M Plane Subnet Mask
Entered by user in 2G Wizard GUI.
mPlaneVlanId
M Plane Vlan Identifier
Entered by user in 2G Wizard GUI.
Parameter
Full name
GSM Rehosting Wizard
$instance
Instance id
Copied from old.
chapAuthentication
CHAP Authentication List
Copied from old.
papAuthentication
PAP Authentication List
Copied from old.
Table 36: NOKBTSFM:PABTRS
Table 37: NOKBTSFM:PPPATH
Structure
Parameter
Full name
GSM Rehosting Wizard
$instance
Instance id
Copied from old.
psnTunnelConfig
PSN Tunnel Configuration
List
gatewayIPAddress
Gateway IP Address
Copied from old.
localIPAddress
Local IP Address
Copied from old.
remoteIPAddress
Remote IP Address
Copied from old.
subnetMask
Subnet Mask
Copied from old.
pwSettings
NetAct™ 16
Pseudowire Settings List
localUDPPort
Local UDP Port
Copied from old.
remoteUDPPort
Remote UDP Port
Copied from old.
© 2018 Nokia Solutions and Networks
70
Rehosting GSM BTS Sites
DN98908338 2-1
Appendix A: Rehosting CM view
parameters
Table 38: NOKBTSFM:PWCONF
Parameter
Full name
GSM Rehosting Wizard
$instance
Instance id
Copied from old.
minSctpPort
Minimum SCTP Port
Entered by user in 2G Wizard GUI.
Parameter
Full name
GSM Rehosting Wizard
$instance
Instance id
Set automatically based on predefined
Table 39: NOKBTSFM:SCTP
definitions in GSM Rehosting Wizard
XML file.
sseSettings
SSE Settings List
Entered by user in 2G Wizard GUI.
Parameter
Full name
GSM Rehosting Wizard
cuPlaneBackupGatewayIPAddress
CU-Plane Backup Gateway IP Address
Entered by user in 2G Wizard GUI.
mPlaneBackupGatewayIPAddress
M-Plane Backup Gateway IP Address
Entered by user in 2G Wizard GUI.
mPlaneBackupRemoteIPAddress
M-Plane Backup BSC IP Address
Entered by user in 2G Wizard GUI.
cuPlaneBackupVlanId
CU-Plane Backup Vlan ID
Entered by user in 2G Wizard GUI.
mPlaneBackupVlanId
M-Plane Backup Vlan ID
Entered by user in 2G Wizard GUI.
Parameter
Full name
GSM Rehosting Wizard
$instance
Instance id
Entered by user in 2G Wizard GUI.
adminState
Administrative State
Copied from old.
locationAreaCode
LAC
Set automatically based on predefined
Table 40: NOKBTSFM:SSE
Table 41: NOKBTSFM:PABBAC
definitions in GSM Rehosting Wizard
XML file.
name
Name
Set automatically based on predefined
definitions in GSM Rehosting Wizard
XML file.
Table 42: NOKMSS:BTSM
NetAct™ 16
© 2018 Nokia Solutions and Networks
71
Rehosting GSM BTS Sites
DN98908338 2-1
Appendix B: Rehosting Wizard
parameters and special values
10 Appendix B: Rehosting Wizard parameters and
special values
Parameter
Value
Description
copyFromOld
Possible values:
Allows the parameter value to be automatically copied from old to
• false (default)
• true
new. Useful for not changing IDs, names, and parameters.
For false, new parameter does not have any default value. For
true, new parameter is filled in automatically with the old value.
copyValueToNext
Possible values:
• false (default)
• true
Allows the parameter value to be copied to the next site
automatically. Useful when, for example, LAC is changing but it is
the same for all the new sites. When used, the Copy value to Next
check box appears. For false, it is not selected by default. For
true, it is selected by default.
Sets a value to the parameter if it is not changed, for example by
default
parameter(s) rule. It can be used when parameter is hidden and its
value is needed.
enforceMultiValues
Possible values:
• false (default)
Sets to indicate if user needs to give multiple values for parameters
in wizard for objects that have many instances.
• true
Used together with the parentParam option to fetch new value
fetchFromNew
for the parameter when it is parent value is set. When set to true
and value of parent parameter is filled, wizard resolves object ID for
this parameters object ID and fetches the new value (if exists). New
value is automatically put to the parameter if only one desire value is
found.
Sets a filter to parameter or copyTo. If filter does not match to
filter
dropped site or its objects, then parameter or copyTo is ignored (not
shown in Rehosting Tool and not put to generated plan).
dnFilter:<string>
Can be used to filter out source objects by Distinguished Names.
For example, if there are multiple BCFs, dnFilter:BCF-1 enables
showing and applying changes only for BCF-1. In such case other
BCFs are not visible.
hideValueFilter:
<string>
Can be used to hide parameter if its value matches to given filter
value. For example, hideValueFilter:"0.0.0.0" hides
parameter if its value is 0.0.0.0. Parameters new value can still be
copied from old or old value can be copied to other parameters.
legacyAbis
Parameter or copyTo is used only if the site is Legacy Abis BCF or
Legacy Abis BCF using Pseudowire.
Parameter or copyTo is used only if the site is Packet Abis over
packetAbis
TDM BCF.
OverTdm
Parameter or copyTo is used only if the site is Packet Abis over
packetAbis
NetAct™ 16
Ethernet BCF.
© 2018 Nokia Solutions and Networks
72
Rehosting GSM BTS Sites
Parameter
DN98908338 2-1
Value
Appendix B: Rehosting Wizard
parameters and special values
Description
OverEthernet
Parameter or copyTo is used only if the site is Packet Abis over
packetAbis
TDM (LS HUB) BCF.
OverTdmLsHub
Parameter or copyTo is used only if the site is Packet Abis over
packetAbis
TDM (AGG HUB) BCF.
OverTdmAggHub
Parameter or copyTo is used only if the site is Packet Abis over
packetAbis
Ethernet - TDM BCF.
MediaConversion
Parameter or copyTo is used only if the site is Packet Abis over
packetAbis
Ethernet - TDM (LS) BCF.
MediaConversionLs
valueFilter:<string> Can be used to remove parameters which values match to given
filter value. For example, valueFilter:0.0.0.0 filters out
parameter with value 0.0.0.0. Filtered parameter value cannot be
used again.
Hides parameters, which do not change during rehosting from the
hidden="true"
Rehosting Tool.
For example, when LAC parameters for BTS do not change during
rehosting, it replaces following lines:
<param uiName="LAC" name="LAC"
copyValueToNext="true" tooltip="Location Area
Code copied from old and set automatically to
BTS and BTSM."/>
<param name="LAC" copyFromOld="true"
hidden="true"/>
When parameters are hidden in the default wizard file and they need
to be changed during rehosting, user removes the hidden="true"
tag, and define desired XML tags.
itemToChange
Possible values:
• first
Used with list parameters to indicate which list value should be
changed.
• last
• all
listName
Shows the abbreviated name of the list of parameter.
name
Shows the abbreviated name for the parameter. You can find the
supported objects and parameters names in Adaptation Information
Browser
objectClass
Defines the object class of the item and copyTo elements. Use
qualified class name. Separate adaptation ID and class abbreviation
with :, for example NOKBSC:BCF.
NetAct™ 16
© 2018 Nokia Solutions and Networks
73
Rehosting GSM BTS Sites
DN98908338 2-1
Appendix B: Rehosting Wizard
parameters and special values
Parameter
Value
Description
parameterRule
actualTargetValue
Indicates that value from target object should be set to this
parameter.
Used with parameter rule value <number> to indicate that something
add
should be added to or distracted from a number (usually IP address).
Counts the gateway IP address from given CU-Plane BTS IP
countTargetPabtrsCu
Address and CU-Plane BTS Subnet Mask parameters. The first
PlaneGatewayAddress
address in the subnet is given for the gateway. If the parameters are
not present in the wizard, the gateway value is not changed.
Counts the gateway IP address from given M-Plane BTS IP Address
countTargetPabtrs
and M-Plane BTS Subnet Mask parameters. The first address in the
MPlaneGatewayAddress subnet is given for the gateway. If the parameters are not present in
the wizard, the gateway value is not changed.
generateInstance
Generates temporary instance for selected objects. Used mainly with
the LAPD objects.
pattern
Parameter rule value defines a pattern that is used to form value.
Finds the item on the old list of parameter value. Name given in
replaceWithMatching
parameterRuleValue is the same as old parameter value.
OldValues
usedPwSettingsEntry
Finds the pwSettings entry from PWCONF object where
parameter pwInUse is set to 1- Yes.
Used in connection with the parameterRule parameter.
parameterRuleValue
Using parameterRule="add" and parameterRuleValue tags,
increases or decreases the old value. For example, changing IP
address:
... parameterRule="add" parameterRuleValue="-1">
In this case the old value, for example 10.10.10.10 will be
changed to 10.10.10.9.
Used together with the showFromNew option. Items in combo box
parentParam
are fetched as usual but filtered with the values the user gave to
parent parameters.Value example: "NOKBCS:BCF;$instance"
indicating that parent parameter is NOKBSC:BCF objects' $instance
parameter.
showFromNew
Possible values:
• false (default)
• true
Used only with the instance parameters ($instance). For other
parameters, this attribute is ignored. If set to true, parameters
values (object IDs) are fetched from objects under new BSC and
shown in the combo box in rehosting wizard instead of text fields.
tooltip
Shows the parameter tooltip.
uiName
Shows the parameter name in the Wizard dialog.
Table 43:
• copyFromOld - allows the parameter value to be automatically copied from old to new. Useful for
not changing IDs, names and parameters. Possible values are false or true, by default false.
NetAct™ 16
© 2018 Nokia Solutions and Networks
74
Rehosting GSM BTS Sites
DN98908338 2-1
Appendix B: Rehosting Wizard
parameters and special values
For false the parameter new value is not having any value by default in the Wizard dialog. For
true the parameter new value is having the old value filled in automatically.
• copyValueToNext - allows the parameter value to be copied to the next site automatically.
Useful when, for example LAC is changing but it is the same for all the new sites. Possible values
are false or true, by default false. For false, the Copy value to Next checkbox is appearing
in the Wizard dialog for the parameters, but it is not selected by default. For true, then Copy
value to Next checkbox is appearing in the Wizard dialog for the parameters and it is selected by
default. When tag is not present, the checkbox does not appear.
• default - sets a value to the parameter if it is not changed, for example by parameter(s) rule. It is
usually used when parameter is hidden and some value is needed.
• enforceMultiValues - Set to indicate whether or not user is forced to give multiple values for
parameters in wizard for objects that have many instances. Possible values: true and false,
default is false.
• fetchFromNew - Can be used together with parentParam option to fetch new value for parameter
when it’s parent value is set. When set to true and parameter’s parent parameter is filled, wizard
resolves object ID for this parameter’s object ID and fetches the new value if existing. New value
is automatically put to parameter if only one unique value is found.
• filter - sets a filter to parameter or copyTo. If filter does not match to dropped site or it's
objects, then parameter or copyTo is ignored (not shown in Rehosting Tool and not put to
generated plan). Possible filter values:
– dnFilter:<string> - can be used to filter out source objects by Distinguished Name,for
example, if there are multiple BCFs, dnFilter:BCF-1 would make the parameter to show
and changes to apply only for BCF-1, otherwise all the BCFs would be visible in rehosting
wizard.
– hideValueFilter:<string> - can be used to set parameter hidden if it's value matches
to given filter value, for example, hideValueFilter:"0.0.0.0" would hide parameter if
it's value is 0.0.0.0. Parameters new value can still be copied from old or old value can be
copied to other parameters.
– legacyAbis - parameter or copyTo is used only if the site is Legacy Abis BCF or Legacy
Abis BCF using Pseudowire.
– packetAbisOverTdm - parameter or copyTo is used only if the site is Packet Abis over
TDM BCF.
– packetAbisOverEthernet - parameter or copyTo is used only if the site is Packet Abis
over Ethernet BCF.
– packetAbisOverTdmLsHub - parameter or copyTo is used only if the site is Packet Abis
over TDM (LS HUB) BCF.
– packetAbisOverTdmAggHub - parameter or copyTo is used only if the site is Packet Abis
over TDM (AGG HUB) BCF.
NetAct™ 16
© 2018 Nokia Solutions and Networks
75
Rehosting GSM BTS Sites
DN98908338 2-1
Appendix B: Rehosting Wizard
parameters and special values
– packetAbisMediaConversion - parameter or copyTo is used only if the site is Packet Abis
over Ethernet - TDM BCF.
– packetAbisMediaConversionLs - parameter or copyTo is used only if the site is Packet
Abis over Ethernet - TDM (LS) BCF.
– valueFilter:<string> - can be used to remove parameters whose value matches to
given filter value e.g. valueFilter:0.0.0.0 would filter out parameter if it's value is 0.0.0.0.
Parameters value cannot be used any more when parameter is removed based on this filter.
• hidden="true" - hide parameters, which do not change during rehosting from Rehosting Tool.
For example, when LAC parameters for BTS do not change during rehosting replace following
lines:
<param uiName="LAC" name="LAC" copyValueToNext="true" tooltip="Location Area Code
copied from old and set automatically to BTS and BTSM."/>
<param name="LAC" copyFromOld="true" hidden="true"/>
When some parameters are set as hidden in the default wizard file, which are needed to be
changed during rehosting, remove the hidden="true" tag and define wanted XML tags.
• itemToChange - used with list parameters to indicate which list value should be changed. The
possible values are first, last and all.
• listName - abbreviated name of the list parameter.
• name - this is the abbreviated name for the parameter. You can find the supported objects and
parameters names in Adaptation Information Browser.
• objectClass - defines the object class of the elements item and copyTo. Use qualified class
name (adaptation id and class abbreviation separated with ":"), for example NOKBSC:BCF.
• parameterRule
Possible parameter rules:
– actualTargetValue - indicates that value from target object should be set to this
parameter.
– add - Used with parameter rule value <number> to indicate that something should be added
to or distracted from a number, usually IP address.
– countTargetPabtrsCuPlaneGatewayAddress - Counts the gateway ip address from
given CU-Plane BTS IP Address and CU-Plane BTS Subnet Mask parameters. The first
address in the subnet is given for the gateway. If the parameters are not present in the wizard,
the gateway value is not changed.
– countTargetPabtrsMPlaneGatewayAddress - Counts the gateway ip address from
given M-Plane BTS IP Address and M-Plane BTS Subnet Mask parameters. The first address
in the subnet is given for the gateway. If the parameters are not present in the wizard, the
gateway value is not changed.
NetAct™ 16
© 2018 Nokia Solutions and Networks
76
Rehosting GSM BTS Sites
DN98908338 2-1
Appendix B: Rehosting Wizard
parameters and special values
– generateInstance - Generates temporary Instance for selected objects. Used mainly with
the LAPD objects.
– pattern - Parameter rule value defines a pattern that is used to form value.
– replaceWithMatchingOldValues - Find the item in the old list parameter value where its
name is given in parameterRuleValue is the same as old parameter value.
– usedPwSettingsEntry - Finds the pwSettings entry from PWCONF object where
parameter pwInUse is set to 1- Yes.
• parameterRuleValue - used in connection with parameterRule parameter.
Using parameterRule="add" and parameterRuleValue tags, it is possible to increase or
decrease the old value. For example, changing IP address:
... parameterRule="add" parameterRuleValue="-1">
In this case the old value, for example 10.10.10.10 will be changed to 10.10.10.9.
• parentParam - used together with showFromNew option, items in combo box are fetched
as usual but filtered with the values the user has given to parent parameters. Value example:
"NOKBCS:BCF;$instance" indicating that parent parameter is NOKBSC:BCF objects' $instance
parameter.
• showFromNew - used only with instance parameters ($instance). For other parameters, this
attribute is ignored. If set to true, parameter's values (object id's) are fetched from objects under
new BSC and shown in combo box in rehosting wizard instead of textfields. Possible values: true
and false, default is false.
• tooltip - parameter tooltip
• uiName - the parameter name in the Wizard dialog.
NetAct™ 16
© 2018 Nokia Solutions and Networks
77