RTR, Radio Tool for Reparenting, User Guide USER GUIDE
5/1553-APR 901 0227 Uen D
Copyright © Ericsson AB 2011. All rights reserved. No part of this document may be reproduced in any form without the written permission of the copyright owner. Disclaimer The contents of this document are subject to revision without notice due to continued progress in methodology, design and manufacturing. Ericsson shall have no liability for any error or damage of any kind resulting from the use of this document.
5/1553-APR 901 0227 Uen D | 2011-12-12
Contents
Contents 1
About This Document
1
1.1
Target Group
1
1.2
Prerequisites
1
1.3
Typographic Conventions
2
2
Radio Tool for Reparenting Overview
3
2.1
Basic Functions of Radio Tool for Reparenting
4
3
Getting Started
5
3.1
The RTR License
5
3.2
Launching and Exiting Radio Tool for Reparenting
6
3.3
Navigating the Radio Tool for Reparenting GUI
7
3.4
Using the RTR CLI
16
3.5
Using the Help Function
20
3.6
Using Common Buttons
20
4
Using Radio Tool for Reparenting
21
4.1
Operational Overview
21
4.2
Support for Cut-Over
23
4.3
MIM Compatibility
24
4.4
UtranCell Naming Conventions
24
4.5
Importing a Predefined Selection
25
4.6
Results Log
26
4.7
Logging Information
27
4.8
Using Fallback with Radio Tool for Reparenting
28
4.9
Support for Parallel Reparenting
29
4.10
Commit Instruction Break Point Added in RTR
30
5
Using Online Help
33
5.1
Help Browser
33
Glossary
35
Reference List
37
5/1553-APR 901 0227 Uen D | 2011-12-12
RTR, Radio Tool for Reparenting, User Guide
5/1553-APR 901 0227 Uen D | 2011-12-12
About This Document
1
About This Document This document describes how to use the Radio Tool for Reparenting (RTR) application Graphical User Interface (GUI). RTR provides OSS-RC WCDMA RAN-CM users with the ability to automatically reconfigure their Radio Network as part of a reparent of one or more RBS Nodes.
1.1
Target Group The intended target group for this document is the following: •
1.2
Radio Network Engineer
Prerequisites It is assumed that the user of this document is familiar with the following: •
Solaris workstations
•
OSS-RC
•
The WCDMA RAN interface.
•
Planned Configuration handling, refer to the Planned Configuration, User Guide, Reference [4].
•
RBS reparenting procedures, for WCDMA RAN network reconfiguration, refer to the following Operating Instructions:
0 0 0 0
For information on ATM RBS Reparenting Preparation Phase see Reference [5]. For information on IP RBS Reparenting Preparation Phase see Reference [6]. For information on ATM RBS Reparenting Execution Phase see Reference [7]. For information on IP RBS Reparenting Execution Phase see Reference [8].
5/1553-APR 901 0227 Uen D | 2011-12-12
1
RTR, Radio Tool for Reparenting, User Guide
1.3
Typographic Conventions The typographic conventions for Customer Product Information (CPI) in OSS-RC are available in the document, OSS Library Typographic Conventions, Reference [2].
2
5/1553-APR 901 0227 Uen D | 2011-12-12
Radio Tool for Reparenting Overview
2
Radio Tool for Reparenting Overview Reparenting an RBS (or NodeB) is defined as moving the traffic control of an RBS from a source RNC to a target RNC. This means that the IubLink interface from the source RNC is removed, and a new IubLink is configured from the target RNC to the RBS resulting in the RBS being controlled by the target RNC. Note:
Using RTR in isolation does not have any effect on the WRAN node topology, that is it does not complete the actual RBS reparenting and thus is not reflected in the Common Explorer Radio Network topology. See the following documents for information on all steps needed to complete the relevant reparenting use case: •
For information on ATM RBS Reparenting Preparation Phase see Reference [5].
•
For information on IP RBS Reparenting Preparation Phase see Reference [6].
•
For information on ATM RBS Reparenting Execution Phase see Reference [7].
•
For information on IP RBS Reparenting Execution Phase see Reference [8].
RTR is part of this usecase. RTR recalculates the Radio Network as it is affected by an RBS reparenting and carries out the reconfiguration when prompted to do so by the user. The cells and channels are moved, and impacted neighboring cell relations (both in moved cells and in cells pointing to moved cells) are adjusted to match the move. All reconfiguration changes are written to a new single planned configuration, for subsequent activation. The RNC Radio Network MO configuration consists of the following entities: •
UtranCells
•
Cell Channels (including High Speed channels and the MBMS (Multimedia Broadcast Multicast Service) channel)
•
UtranRelations (both intra and inter RNC relations, including relations for which the affected cell is a target cell)
•
Coverage Relations
•
GsmRelations
•
EutranFreqRelations (Outgoing ERBS Relations)
•
UtranCellRelation (Incoming ERBS Relations)
5/1553-APR 901 0227 Uen D | 2011-12-12
3
RTR, Radio Tool for Reparenting, User Guide
2.1
•
Location Area, if the specified Location Area does not exist on the target RNC, it is automatically created along with the Routing Area and Service Area specified in the Cell that is being moved.
•
RTR points newly created UtranCells towards the specified URA (Utran Registration Area) MO (Managed Object) and creates it if necessary.
Basic Functions of Radio Tool for Reparenting Reparenting of an RBS consists of a complex series of tasks. The RTR application handles all the Radio Network configuration required for reparenting an RBS, thus simplifying the overall reparenting procedure. The RTR application calculates all necessary radio network configuration changes when reparenting one or more RBS nodes. These changes are written to a Planned Configuration that must be activated in order for these changes to be executed on the RNC node. Refer to the Planned Configuration, User Guide, Reference [4] for more information on activating planned configurations. Note:
Since the planned configurations generated by RTR do not survive Large Upgrade, the user should activate any planned configurations they require before Large Upgrade.
As part of reparenting an RBS node, a new IubLink must be configured on the target RNC. This IubLink must exist on the target RNC before the RTR application can be used to calculate and plan the necessary radio network changes. The user must specify the identity of the IubLink on the target RNC when selecting an RBS for reparenting. If the specified IubLink does not exist, an error is reported.
4
5/1553-APR 901 0227 Uen D | 2011-12-12
Getting Started
3
Getting Started This chapter is for new or infrequent users of RTR. It describes the GUI and how to perform some basic tasks, as follows:
3.1
•
The RTR License
•
Launching and Exiting Radio Tool for Reparenting
•
Navigating the Radio Tool for Reparenting GUI
•
Using the Help function
•
Using common buttons
The RTR License The RTR application is now a licensed service feature. The RTR application can now only be used if the RTR valid license is available. If there is no RTR license or if the RTR license has expired then Software Management (SM) GUI will display the RTR MC server as, Unlicensed. The Licensing service provided by Utility Services is used to perform license validation. This service provides access to the Sentinel license server in OSS.License. A license check is done whenever the RTR application is accessed, if the license check fails, then access to the RTR application is denied and a message is displayed indicating that the current license is not valid. There are two types of license available: •
Full license A full RTR license provides full access to the RTR GUI.
•
Trial license The Trial license has a license expiry date. If the license expires while the RTR GUI is open then the following message is displayed: Sorry your license has expired...The application will close now. In case you have installed a new License Please restart the server and access the RNR Application and RTR MC server will go offline and in the SM GUI the status of the rnr_config_reg (RTR MC server ) will be Unlicensed.
5/1553-APR 901 0227 Uen D | 2011-12-12
5
RTR, Radio Tool for Reparenting, User Guide
During the trial license period, RTR will display messages reminding the user of the amount of time left on the trial licence. A reminder message is displayed when there are ten days left on the trial license, five days left on the trial license, two days left on the trial license and also when there is only one day left on the trial license. The reminder messages are not displayed if a full license is acquired. To get a trial or full license for the RTR application, contact the system administrator and see Reference [11].
3.2
Launching and Exiting Radio Tool for Reparenting This chapter describes how RTR is launched. RTR is a WCDMA RAN application. It is launched from OSS Common Explorer, see the Common Explorer User Guide, Reference [3]. Prerequisite: A valid configuration must be opened. Note:
When GUI is launching, if there are any RBSs that have an undefined value for any of the attributes, userLabel, rbsIubId or connectionStatus, then the following message is displayed: Below MeContext Mo(s) have some undefined attributes,RTR wont display these RBS (s) in RTR GUI. Please check attributes userLabel rbsIubId, connectionStatus, fdnOfRncIubLink. The RBS details will be displayed. The error message is available in GUI logs and server logs. For fdnOfRncIubLink attribute, no pop-up message is displayed but an error message is available in the server logs.
The Radio Tool for Reparenting GUI can be launched in the following ways: •
On the Common Explorer main menu, select Tools, then select Reparent RBS.
The Radio Tool for Reparenting GUI is displayed as follows, Figure 1:
6
5/1553-APR 901 0227 Uen D | 2011-12-12
Getting Started
Figure 1
Radio Tool for Reparenting GUI
To exit, click the Close button.
3.3
Navigating the Radio Tool for Reparenting GUI The Radio Network Reparent GUI consists of the following four main components: •
RBS Selection pane - This allows the user to select RBSs from the Available RBSs tree, and move them to an RNC in the Target RNCs list (on the right).
•
Selection Details tab - This displays information about the RBS to be reparented, when the RBS has been moved to the target RNC, in the Target RNCs list.
•
Progress Details tab - This displays information regarding the progress of the RBS reparenting.
•
Reparenting Options dialog - This is used to select Cut-Over options and define the New Planned Configuration name before reparenting is initiated.
5/1553-APR 901 0227 Uen D | 2011-12-12
7
RTR, Radio Tool for Reparenting, User Guide
3.3.1
RBS Selection Pane The RBS Selection pane, an example of which is shown in Figure 2, comprises an Available RBSs tree and a Target RNCs list. The user can select RBSs for reparenting from the Available RBSs tree, and move them to an RNC in the Target RNCs list, using the following steps: 1. Select the required RBS in the Available RBSs tree, right-click, and then click Reparent from. 2. Select the required RNC in the Target RNCs list, right-click, and then click Reparent to. Note:
RBS selections can also be made by selecting the required RBS in the Available RBSs tree, then dragging and dropping it to the required RNC in the Target RNCs list. Only RBS Nodes that are Connected and Synchronized can be successfully selected.
Figure 2
3.3.2
RBS Selection Pane Example
Selection Details Tab The Selection Details tab an example of which is shown in Figure 3, allows the user to view information about the RBS to be reparented, to specify the IubLink.rbsId (Target Rbs Id, which is mandatory) and optionally specify new UtranCell.lac, UtranCell.rac, UtranCell.ura, and UtranCell.sib1PlmnScopeValueTag values. It is populated when an RBS selection has been performed. To view or edit the information, click the Selection Details tab.
8
5/1553-APR 901 0227 Uen D | 2011-12-12
Getting Started
Note:
To deselect an RBS, select the required row, right-click, and then click Undo Selection. The information displayed in the Selection Details tab can be sorted by double-clicking the column headers. The following attribute values must be observed: •
IubLink.rbsId must be a valid value, present under the Target RNC, not used by any UtranCell.
•
UtranCell.lac must have a value in the range: <1- 65533> <65535 - 65535>.
•
UtranCell.rac must have a value in the range: <1- 65533> <65535 - 65535>.
•
UtranCell.ura must have a value in the range: <0 - 65535>.
•
UtranCell.sib1PlmnScopeValueTag must have the value in the range: <0 - 31>.
Figure 3
Selection Details Tab Example
The columns in the Selection Details tab are configurable; they can be moved by dragging and dropping them.
5/1553-APR 901 0227 Uen D | 2011-12-12
9
RTR, Radio Tool for Reparenting, User Guide
Information is displayed under the following column headings in the Selection Details tab:
3.3.3
•
RBS userLabel
•
Source RNC userLabel
•
Target RNC userLabel
•
IubLink.rbsId
•
UtranCell.lac
•
UtranCell.rac
•
UtranCell.ura
•
UtranCell.sib1PlmnScopeValueTag
Progress Details Tab Progress reporting occurs during the preprocessing phase and execution phase of a request. The Progress Details tab an example of which is shown in Figure 4, displays information received from the server regarding the progress of the RBS reparenting, after a reparenting operation has been started. To view this information, click the Progress Details tab. Note:
When a row is selected in the Progress Details tab, information pertaining to the row is displayed at the bottom of the Progress Details tab. The information displayed in the Progress Details tab can be sorted by double-clicking the column headers.
10
5/1553-APR 901 0227 Uen D | 2011-12-12
Getting Started
Figure 4
Progress Details Tab Example
The columns in the Progress Details tab are configurable; they can be moved by dragging and dropping them. Information is displayed under the following column headings in the Progress Details tab: •
Description
•
RBS userLabel
•
Type
•
Time
To save the contents of the Progress Details tab to a text file once the reparenting is finished, click the Save progress button.
3.3.4
Reparenting Options Dialog After making RBS selections and including the IubLink.rbsId, click Prepare plan on the main GUI to launch the Reparenting Options. The Reparenting Options dialog is displayed in Figure 5, if there are invalid nodes in the plan see Section 3.3.5 on page 16 for information on how to handle invalid nodes.
5/1553-APR 901 0227 Uen D | 2011-12-12
11
RTR, Radio Tool for Reparenting, User Guide
Use the Select Cut-Over Point Options to select when to perform Cut-Over. These options determine at what stage of the reparenting process Cut-Over occurs. Use the Cut-Over Options to lock or unlock Cells at Cut-Over. Locking and unlocking Cells has traffic handling implications see Section 4.2 on page 23 for more information. Use the Select Set Breakpoint before cleanup of source RNC Options to add a (non cut-over) breakpoint to the plan, just before the deletion of Cells/Channels on the source RNC. This provides the option of delaying the clean-up of the source RNC. This can be used for example to allow all network tests be completed before clean-up of the source RNC. To create a result log file select Yes in Result Log File Choice. In Result Log File Choice, the No option is the default option, that is result log files are not created by default. Enter the Enter New Planned Configuration to enter the name of the New Planned Configuration to which the reparent changes are to be written: Enter a name for the plan. It is recommended to enter a name using a combination of the characters in the range A-Z, a-z and 1–9. Plan names are case sensitive and must be unique. The minimum length of a name is two (2) characters. The strings: network, configuration, valid or active, in any combination of upper or lower case letters may not be used in a plan name. The name may not contain a space. Plan names must start and end with a non white-space character. The maximum name length is 85 characters. The permitted characters are letters, digits (numbers), dollar sign, $ and underscore, _ . An underscore is always illegal in the first position.
12
5/1553-APR 901 0227 Uen D | 2011-12-12
Getting Started
Figure 5
Reparenting Options Dialog
The Cut-Over options and their resultant activations are explained in the following table, Table 1:
5/1553-APR 901 0227 Uen D | 2011-12-12
13
RTR, Radio Tool for Reparenting, User Guide
Table 1
Cut-Over Options and their Resultant Activations
Cut-Over Option
Resultant Activation
UtranCell and Channel Creation
This Cut-Over option activates only UtranCell and Channel creation in the first activation. For more information on the UtranCell reconfiguration task see Step 1 and for information on the Channel reconfiguration task see Step 2. All other reconfiguration tasks are done in the second activation. See Section 4.1 on page 21 for more information on the reconfiguration tasks. Deleting UtranCells and their subordinate MOs (see Step 6) and updating relations that had a recently moved UtranCell as its neighbor cell (see Step 7) are done in the second activation since they affect existing cell configuration.
14
5/1553-APR 901 0227 Uen D | 2011-12-12
Getting Started
Coverage Relation Creation
This Cut-Over option activates only UtranCell, Channel and Coverage Relation creation in the first activation. For more information on the UtranCell reconfiguration task see Step 1, for information on the Channel reconfiguration task see Step 2 and for information on the Coverage Relation reconfiguration task see Step 3. All other reconfiguration tasks are done in the second activation. See Section 4.1 on page 21 for more information on the reconfiguration tasks. Deleting UtranCells and their subordinate MOs (see Step 6) and updating relations that had a recently moved UtranCell as its neighbor cell (see Step 7) are done in the second activation since they affect existing cell configuration.
Outgoing Relation Creation
This Cut-Over option activates only UtranCell, Channel, Coverage Relation and Outgoing Relation creation in the first activation. For more information on the UtranCell reconfiguration task see Step 1, for information on the Channel reconfiguration task see Step 2, for information on the Coverage Relation reconfiguration task see Step 3and for information on the Outgoing Relation reconfiguration task see Step 5. All other reconfiguration tasks are done in the second activation. See Section 4.1 on page 21 for more information on the reconfiguration tasks. Deleting UtranCells and their subordinate MOs (see Step 6) and updating relations that had a recently moved UtranCell as its neighbor cell (see Step 7) are done in the second activation since they affect existing cell configuration.
After selecting the required reparenting options, click Start to start the reparenting operation. Click Cancel to close the dialog box and to suspend the reparenting operation.
5/1553-APR 901 0227 Uen D | 2011-12-12
15
RTR, Radio Tool for Reparenting, User Guide
3.3.5
Invalid Nodes After making RBS selections and including the IubLink.rbsId, click Prepare plan on the main GUI, RTR will start checking for invalid status of nodes. If there are any invalid nodes then the Invalid RNC Status dialog will display the information about the RNC which is in DISCONNECTED or UNSYNCHRONIZED or NOT RECOVERED state. To proceed with the reparenting select Continue. Click Abort to cancel the reparenting process. After the Invalid RNC Status dialog, RTR checks for MissingMaster inconsistency for the RNC that is going to be reparented. If there are any inconsistency recorded then the Sub-Network Inconsistencies dialog will list the inconsistent RNC node. To proceed with the reparenting select Continue. Click Abort to cancel the reparenting process. After the Sub-Network Inconsistency check the Reparenting Options Dialog will be launched see Section 3.3.4 on page 11.
3.4
Using the RTR CLI To use the RTR CLI do the following: 1. Access the following folder: /opt/ericsson/nms_umts_rnr_cli/bin/ 2. Use the following command to run RTR: ./rnr_cli.sh 3. The following arguments can be used with the RTR command, see Table 2
Argument Name (Long and short versions)
Description
Number of instances Required
-file
Location of pre-defined input file specifying RBSs to reparent. Same format as the input file used in GUI. Please see Section 4.5 on page 25
0..1 (But either the –file/-f or -rbs/-r arg must be specified)
-f
16
RTR CLI Arguments
5/1553-APR 901 0227 Uen D | 2011-12-12
Getting Started
Argument Name (Long and short versions)
Description
Number of instances Required
-rbs
Information on the reparent for 1 RBS. is same as the format of a line in a pre-defined input file.
0..* (But either the –file/-f or -rbs/-r arg must be specified)
Name of plan that RTR will create and write configuration changes to. If not specified, then RTR generates time stamped plan name as with GUI.
optional
Automatically lock source cells before cutover and add a plan breakpoint before the lock.
optional
-r
-plan -p
-lock {s|h} -l {s|h}
Applies soft lock if value “s” is specified.Applies hard lock if value “h” is specified. -unlock -u
-cut <1|2|3> -c <1|2|3>
Automatically unlock target cells after cutover and adds a plan breakpoint after the unlock.
optional
Specifies at which mandatory phase that cut-over is to be applied: 1 = After "UtranCell and Channel Creation" 2 = After "Coverage Relation Creation" 3 = After "Outgoing Relation Creation"
-tidy -t
5/1553-APR 901 0227 Uen D | 2011-12-12
Add breakpoint to plan optional before the cleanup of cells/relations on source RNC.
17
RTR, Radio Tool for Reparenting, User Guide
Argument Name (Long and short versions)
Description
Number of instances Required
-ignore
If specified, CLI execution does not ask for confirmation to continue in case of warnings about inconsistencies, incompatible MIMs or invalid RNC status.
optional but mandatory in case of saving progress into a file
Prints out CLI usage
optional
-i
-help -h E.g. for running CLI: 1. Using -r/rbs argument
./rnr_cli.sh -r RNC01,RNC01RBS03,RNC02,1041,2,3,4,3 -c 2 -p RTR_plan_2011 -l s -u Explanation -r/-rbs
shows that you are giving rbsInfo
SourceRnc
RNC01
SourceRBS
RNC01RBS03
TargetRnc
RNC02
IubLink
1041
lac
2
rac
3
ura
4
sib1PlmnScopeValueTag
3
-c
This is to provide Cut-Over breakpoint, we have given 2 = After "Coverage Relation Creation".
-p
Plan Name will be RTR_plan_2011.
-l
With "s" to put breakpoint with soft lock.
-u
To put breakpoint at auto Unlock.
./rnr_cli.sh -r RNC01,RNC01RBS03,RNC02,1041 -c 2 -p RTR_plan_2011 -l s -u Explanation:
18
5/1553-APR 901 0227 Uen D | 2011-12-12
Getting Started
-r/-rbs
shows that you are giving rbsInfo.
SourceRnc
RNC01
SourceRBS
RNC01RBS03
TargetRnc
RNC02
IubLink
1041
-c
This is to provide Cut-Over breakpoint, we have given 2 = After "Coverage Relation Creation".
-p
Plan Name will be RTR_plan_2011
-l
With "s" to put breakpoint with soft lock
-u
To put breakpoint at auto Unlock
2. Using -f/-file argument ./rnr_cli.sh -f rtrInputFile.txt -c 3 -l h -u -i -f
To give input selection file
-c
This is to provide Cut-Over breakpoint, we have given 3 = After "Outgoing Relation Creation".
-l
With "h" to put breakpoint with hard lock.
-I
To ignore warnings of prechecks.
3. To save progress in a file: ./rnr_cli.sh -r RNC01,RNC01RBS01,RNC02,1003 -c 2 -i > CliProgressFileName Explanation: -r/-rbs
shows that you are giving rbsInfo
SourceRnc
RNC01
SourceRBS
RNC01RBS01
TargetRnc
RNC02
IubLink
1003
-c
This is to provide Cut-Over breakpoint, we have given 2 = After "Coverage Relation Creation"
5/1553-APR 901 0227 Uen D | 2011-12-12
19
RTR, Radio Tool for Reparenting, User Guide
3.5
-i
To ignore warnings of prechecks
">"
used to save progress in a file. After giving ">" you have to give your filename with the path (without the path if you want to save the file in same location).
Using the Help Function Help is available by clicking the Help button (which is located at the bottom center,) on the main window. If the Help button is available in a dialog-box you can click the button to display context-sensitive help, that is, help relevant to the information currently displayed. See Using the Online Help for more details.
3.6
Using Common Buttons The following buttons are displayed in the interface. In general they have the following functions: Table 3
20
Common Buttons
Description
New plan
Click to start selections for a new reparent request or to discard an existing selection. All details are cleared.
Import selection
Click to import a predefined selection file from an external source. Refer to the chapter, Importing a Predefined Selection
Prepare plan
Click to submit the reparent request.
Close
Click to close the Radio Tool for Reparenting interface.
Help
Click to view help relating to the active window.
5/1553-APR 901 0227 Uen D | 2011-12-12
Using Radio Tool for Reparenting
4
Using Radio Tool for Reparenting This chapter describes the following:
4.1
•
Operational Overview
•
Support for Cut-Over
•
MIM Compatibility
•
UtranCell Naming Conventions
•
Importing a Predefined Selection
•
Results Log
•
Using Fallback with Radio Tool for Reparenting
Operational Overview For each selected RBS Node, the following reconfiguration tasks are performed. The RTR server runs each of the following Reparent RBS tasks: 1. Each UtranCell in each RBS is copied to its respective target RNC. Note:
If Cell MOCN is enabled for the cells on a source RNC which will be effectively moved to the target RNC (which also has Cell MOCN enabled), then the CnOperator and MocnCellProfile managed objects must already exist on the target RNC in order for RTR to calculate the changes required to the radio network.
2. Each of the UtranCell's Channels (Fach, Rach, Pch, Hsdsch, Eul,EulFach, MbmsCch) are copied to their new UtranCell parent in the target RNC. Note:
If the MbmsCch channel exists on the source RNC, then the following applies: •
If there is no Mbms MO in the target RNC, the RTR application creates the Mbms MO in the target RNC using the attribute values of the Mbms MO in the source RNC.
•
If the target RNC contains an Mbms MO, it is used and the RTR application make no changes to it.
If a new URA (Utran Registration Area) or LAC (Location Area Code) or Routing Area Code (RAC) is specified, then the UtranCells on the target RNC are configured accordingly, that is the new cells will be in the specified URA , Location Area and Routing Area.
5/1553-APR 901 0227 Uen D | 2011-12-12
21
RTR, Radio Tool for Reparenting, User Guide
It may also be necessary to define a new value for the sib1ScopePlmnValueTag in the new UtranCells. If the user has specified this value, then the specified value is used when creating the new cells on the target RNC. For more information, open the RNC library and view the relevant RNC MOM. New UtranCells created on the target RNC are always created with their administrative state set to locked. To bring these new cells into service, either manually unlock the administrative state set, or see the automatic unlocking option described in the chapter on Support for Cut-Over. 3. Each UtranCell's CoverageRelations are copied to their new UtranCell parent in the target RNC. Note:
CoverageRelations between cells on the reparented RBS Node and its new neighboring cells are not automatically created. This must be done manually after the reparent. However, if CoverageRelations exist between cells on different RBS Nodes and both RBS Nodes are reparented together to the same target RNC, then the CoverageRelations are created.
4. Each UtranCell's applicable EutranFreqRelations (Outgoing Relations) are copied to their new UtranCell parent in the target RNC. 5. Each UtranCell's remaining Relations (UtranRelation and GsmRelation) are copied to their new UtranCell parent in the target RNC. 6. Any (UtranRelation or UtranCellRelation) incoming relations that have a recently moved UtranCell as its neighbor cell are updated so that they now reference the corresponding new UtranCell in the target RNC. Note:
For outgoing relations from the cells on the target RNC and updates to the relations from existing neighbours of the cells that have moved, the setting up of IurLinks between the target RNC and other existing RNCs are done automatically. Also, due to the cells being deleted from the source RNC, IurLinks that have no further use after handover are automatically deleted. Other SubNetwork data may need to be reconfigured as a result of the handover. This SubNetwork data reconfiguration is done automatically. Reconfiguring the SubNetwork data is done to maintain SubNetwork consistency. More information on SubNetwork data can be found in the following document: Sub-Network Model Consistency Check, User Guide. See Reference [10].
7. All UtranCells and their subordinate MOs that have been successfully moved to their respective target RNCs are now deleted as part of a clean-up.
22
5/1553-APR 901 0227 Uen D | 2011-12-12
Using Radio Tool for Reparenting
4.2
Support for Cut-Over The RTR application allows the user flexibility in defining how much of the radio network reconfiguration to perform before Cut-Over. This is defined in the Reparenting Options dialog. When activating the generated planned configuration, the activation stops when all the radio network changes up to the specified Cut-Over point are activated. This allows the user to perform the Transport Network and Physical Cut-Over and any other necessary tasks (for example, traffic testing) before completing the rest of the radio network reconfiguration. The planned configuration must be activated a second time to complete this reconfiguration. If the first activation is not part of a preconfiguration step, the Utran Cells on the source RNC can be automatically locked during the first plan activation. To lock the cells prior to the first activation of the reparenting plan select the option Automatically Lock UtranCells on source RNC at Cut-Over. If Automatic Locking of source Cells is selected, then there is a mandatory new (non cut-over) Breakpoint added to the plan, just before the automatic locking of the source Cells. This allow the plan to be activated up to this point in advance of the reparent slot as the activation does not affect traffic up to this point. If Auto Lock is selected, activate the plan one more time while activating the plan using PCA. There are two options available: •
Soft Lock If Soft Lock is selected, monitor the cells traffic after the plan activation completes up to cut-over (after the automatic locking).
•
Hard Lock
To bring the newly created cells into service as soon as possible, select Automatically UnLock UtranCells on target RNC following Cut-Over. If Automatically UnLock UtranCells on target RNC following Cut-Over is selected, then a (non cut-over) Breakpoint is automatically added to the plan, just after the automatic unlocking of the target Cells. After cutover, RTR sets the administrativeState attribute of a target cell to UNLOCKED, if the corresponding source cell was UNLOCKED. If the corresponding source cell is LOCKED then RTR will not set the administrativeState attribute of a target cell to UNLOCKED, instead the CIF log will be updated in CIF System Event Log and Progress. If Automatically UnLock UtranCells on target RNC following Cut-Over is selected, activate the plan one more time when activating the plan using PCA.
5/1553-APR 901 0227 Uen D | 2011-12-12
23
RTR, Radio Tool for Reparenting, User Guide
Use the option Automatically UnLock UtranCells on target RNC following Cut-Over to add a (non cut-over) Breakpoint to the plan, just before the deletion of Cells/Channels on the source RNC. This provides the option of delaying the clean-up of the source RNC, perhaps to allow all network tests be completed first. If Cleanup breakpoint is selected user has to activate the plan one more time while Activating the plan using PCA. If the first activation of the reparenting plan is to be done as a preconfiguration step, then do not select the automatic lock option as this would affect traffic during preconfiguration. This RTR capability uses the concept of Planned Configuration breakpoints. This means a breakpoint is inserted into the Planned Configuration at the Cut-Over point. Refer to the WCDMA RAN Planned Configuration, User Guide, Reference [4] for more information on breakpoints and how they affect a planned configuration activation.
4.3
MIM Compatibility During radio network reparenting execution, it is expected that the target RNC and Source RNC MIM versions are compatible. If RTR detects that they are incompatible, a dialog is displayed stating this, and that an attempt to reparent the selected RBS may not be successful due to the MIM incompatibility. If the user chooses to continue, any errors encountered by the Radio Network configuration causes it to fail.
4.4
UtranCell Naming Conventions UtranCells that are created on the target RNC node must have unique Relative Distinguished Names (RDNs) and Cell Identities. These values are copied from the source cell so that they can be reused as long as they are unique. However, if the Cell Identity is already in use by another existing UtranCell on the target RNC, a new cell identity is automatically generated. The same applies to the UtranCell RDN, but in this situation, the user can influence how the cell is named. This is to support customer operating practices where naming conventions are important. The user can specify a UtranCell naming template (using the configuration parameter UtranCellFDNFormat), which is used for generating the new UtranCell RDN. The template can contain some special variables, which also support naming the cell according to some existing Cell, RBS, or RNC properties. The new UtranCell MO Class RDN is equal to the value of the naming template parameter with any relevant substitutions as follows:
24
5/1553-APR 901 0227 Uen D | 2011-12-12
Using Radio Tool for Reparenting
•
If the parameter value contains the string {UC}, this string is replaced with the RDN of the UtranCell being reparented.
•
If the parameter value contains the string {CID}, this string is replaced with the Cell Identity (cid) of the UtranCell being reparented. Note:
If a new unique cell identity must be generated, then this is used instead.
•
If the parameter value contains the string {RBSNAME}, this string is replaced with the RDN of the RBS MeContext for the reparented RBS.
•
If the parameter value contains the string {RNCNAME}, this string is replaced with the RDN of the target RNC MeContext.
Please refer to the following examples:
4.5
•
If the parameter value is {UC}_reparent, the UtranCell called cell23456 is reparented as cell23456_reparent.
•
If the parameter value is cell{CID}, the UtranCell with cid 23456 is reparented as cell23456, unless a new cid is generated, for example 67809, in which case it is called cell67809.
•
If the parameter value is UtranCell_{RNCNAME}{RBSNAME}_{CID}, the UtranCell cell23456 with cid 23456 being reparented to RNC RNC05 and on RBS RBS44 is called UtranCell_RNC05RBS44_23456.
Importing a Predefined Selection A selection of RBS Nodes can be specified with a comma-separated text file. This RBS predefined selection file contains the following information: •
Source RNC userLabel
•
RBS userLabel
•
Target RNC userLabel
•
IubLink.rbsId
•
UtranCell.lac (Optional)
•
UtranCell.ura (Optional)
•
UtranCell.rac (Optional)
•
UtranCell.sib1PlmnScopeValueTag (Optional)
A example of the RBS selection file, Example 1:
5/1553-APR 901 0227 Uen D | 2011-12-12
25
RTR, Radio Tool for Reparenting, User Guide
RNC01,RNC01RBS01,RNC02,21,110 RNC01,RNC01RBS02,RNC02,22,110,2,1 RNC01,RNC01RBS03,RNC03,23 RNC01,RNC01RBS02,RNC02,22,110,2,1,6 Example 1 Note:
RBS Selection file (comma-separated text file)
This file is located on the OSS Application Server.
To import a predefined selection file, click the Import selection button. The Open dialog is displayed as follows, Figure 6:
Figure 6
Open Dialog
Select the required predefined RBS selection file for import, and click OK. When this file is opened, the RBS Selection, which is specified in the text file, is displayed in the Selection Details tab. The user may then proceed by clicking the Prepare plan button.
4.6
Results Log The Result Log is created on the OSS Master Server after a reparenting operation has been completed. It indicates the reparented cells. It can be used whenever it is necessary to map from cells (by distinguished name or by traffic ID) what they were before and after reparenting. The Results Log is a comma-seperated text file containing the following information:
26
5/1553-APR 901 0227 Uen D | 2011-12-12
Using Radio Tool for Reparenting
•
RBS Name
•
Source FDN
•
Source PlmnId
•
Source RNC Id
•
Source cId
•
Source Lac
•
Source Rac
•
Source uraIdentity
•
Target FDN
•
Target PlmnId
•
Target RNC Id
•
Target cId
•
Target Lac
•
Target Rac
•
Target uraIdentity
Note:
A Result Log file is created for each GUI session. The file location is: /var/opt/ericsson/nms_umts_rnr_ser The file name format is: rnr-results__ For example: rnr-results_ReparentPlan_100904_123722_128360024969 5.log
4.7
Logging Information •
On receiving of a reparent request (from GUI), RTR logs information that a RTR request is starting execution. The RTR starting execution is logged to the CIF command logs by the command name, “Reparent Request”. The plan name and user ID are also included in the log.
•
On successful completion of a reparent request in RNR, RTR logs information that an RTR request has completed execution. The RTR completed execution is logged to the CIF command log by the command name, “Reparent Request”.
5/1553-APR 901 0227 Uen D | 2011-12-12
27
RTR, Radio Tool for Reparenting, User Guide
4.8
•
On successful completion of a reparent request in RNR, RTR logs a CIF Command log for each RBS that was reparented in the planned configuration (So 5 RBSs reparented means 5 separate CIF command logs).
•
When a "reparent request" in RTR fails to complete, RTR logs information that a RTR request has failed to CIF Command Log. The CIF Error log are updated to include the reason for the failure.
•
RTR logs to CIF Error log when a (Utran/Gsm) relation it is trying to reparent has null adjacent Cell value.
Using Fallback with Radio Tool for Reparenting The WCDMA RAN CM Fallback application can be used with the RTR application to recover from an aborted reparenting where some or all of the planned changes were activated. Where the Fallback application is used, it is recommended that a Fallback Area is created on the source, target and any other affected RNC nodes prior to activating any of the generated RTR Planned Configuration. If the RTR Planned Configuration has been activated up to (but not beyond) the Cut-Over point, it is possible to do a complete rollback of the radio network changes (for example, for all RBS nodes that were selected for reparenting) by performing a Prepare Restore of the saved Fallback Area on the affected target RNC node only. If the RTR Planned Configuration has been activated beyond the Cut-Over point, it is possible to do a complete rollback of the radio network changes (for example, for all RBS nodes that were selected for reparenting) by performing a Prepare Restore of the saved Fallback Area on the affected source RNC, target RNC and any other RNC nodes which have relations to the reparented cells. If some but not all of the RBS nodes selected for reparenting cannot be successfully completed, for example, it is discovered at or during Cut-Over that some of the RBS nodes cannot have their transport network configuration successfully Cut-Over, then it is necessary to fallback all of the radio network changes already activated up to Cut-Over and using RTR, generate a new Planned Configuration containing the changes for the RBS nodes that can be completely Cut-Over. The reason why it is necessary to fallback the entire radio network reconfiguration on the target RNC is due to the fact that all of the relations affected by the reparenting must be recalculated, since any RBS nodes which cannot be reparented may have relations to some of the cells of RBS nodes which are being reparented. Note:
28
Refer to the WCDMA RAN CM Fallback, User Guide Reference [9], for information on using the Fallback application.
5/1553-APR 901 0227 Uen D | 2011-12-12
Using Radio Tool for Reparenting
The Fallback application cannot detect inter node dependencies. Restore nodes in the correct order. Fallback restores nodes in alphabetical order by default. For example when RTR reparenting is done from a source RNC named RNC01 to a target RNC named RNC02, in this case, Fallback automatically restores the source RNC and then the target RNC. However, if the reparenting was done from a source RNC named RNC02 to a target RNC named RNC01, Fallback would restore RNC01, the target RNC first. The following is the recommended procedure for fallback of RTR changes if the cut-over has already taken place. Note:
Any transport network reconfiguration or cleanup that was done during or after the Cut-Over must be un-done as part of the procedure below:
1. Undo any post Cut-Over transport network reconfiguration and clean-up and undo transport network Cut-Over (not covered in this user guide). 2. Prepare Fallback Restore using the Fallback Area created at the beginning of the reparenting procedure and include only the source RNC. 3. Activate the planned area generated by fallback in Step 2. 4. Prepare Fallback Restore using the Fallback Area created at the beginning of the reparenting procedure and include only the target RNC. 5. Activate the planned area generated by fallback in Step 4. 6. Prepare Fallback Restore using the Fallback Area created at the beginning of the reparenting procedure and include all other affected RNC nodes. 7. Activate the planned area generated by fallback in Step 6.
4.9
Support for Parallel Reparenting The RTR application provides support for parallel reparenting, that is where multiple user can perform the reparenting activity. During parallel reparenting if there are any resource constraints (acquiring locks) in the CS database then some of the RTR sessions attempt to retry failed database transactions a number of times with delays between successive retries. While retrying the following messages are displayed in the Progress Detailed Tab along with normal reparenting messages:•
If a failure is encountered the new messages will be:
0 0
"Current Operation failed while reparenting because of Internal Database Problem." "Failed operation will be retried"
5/1553-APR 901 0227 Uen D | 2011-12-12
29
RTR, Radio Tool for Reparenting, User Guide
0 •
"Current Operation is been Retried"
If it is retrying the new message will be:
0
"Retrying the current operation"
followed by the messages that are supposed to be displayed for normal reparenting process. •
If there was a failure even after retrying the new messages will be:
0
"Retry for Current Operation was not successful"
and
0 •
"Please try reparenting again"
If the retry was a success then the new message will be:
0
"Retry was successfull for the failed operation"
In case there is a failure even after multiple retries then refer to the RTR logs that are saved in the path: /var/opt/ericsson/nms_umts_rnr_ser/nms_umts_rnr_ser.trace and check the phase during which the reparenting failed. Based on the name of the phase, configurable parameters are defined for changing the retrycount and bacthsize during reparenting. The configurable parameters name are MaxRetryCount_ and BatchSize_. By default the value of MaxRetryCount_ is 3 and BatchSize_ is 20, but these values can be modified anytime during runtime. For a higher probability for successful reparenting increase the retrycount and reduce the batchsize for a particular phase. Also in order to provide delay between successive retries, another configurable parameter MaxTimeDelayPerRetry is defined. By default the value for this parameter is 20 seconds. This value can also be modified during runtime.
4.10
Commit Instruction Break Point Added in RTR The RTR application introduces the following break points to the plan, the cut-over break point and the CS commit instructions break point. RTR uses the CS commit instructions break point to inform the PCA application where and when to give CS commit instructions in the plan.
30
5/1553-APR 901 0227 Uen D | 2011-12-12
Using Radio Tool for Reparenting
After the successful creation of a commit instruction break point, an event is published in the RTR progress GUI. This event contains a description of the break point together with a phase name as follows: For an example of an event shown in RTR GUI for a commit instruction break point: Added a commit instruction BreakPoint to Plan :RNR_ For an example of an event shown in RTR GUI for a cut-over break point instruction: Added a CutOver BreakPoint to Plan :RNR_ If the following error is thrown when invoking PCA to give the commit instruction: com.ericsson.oss.wlran.pca.domain.exceptions.PCAServerException, PCAExceptions.DATASTORE_EXCEPTION (PCA wrapper of com.ericsson.nms.cif.cslib.exception.CSException ) Then RTR retries to add a break point to the plan. All the retry rules are still applicable in this case. To change the number of retries for adding a commit instruction break point use the MaxRetryCount parameter MaxRetryCount_BreakPoint. The MaxRetryCount parameter MaxRetryCount_BreakPoint has a default value of 3. Note:
The information provided by RTR to PCA includes: •
UserId
•
Plan name
•
_ For example if there is 5 commit instructions in RTR , then the RTR will give a string COMMIT_INSTRUCTION_NO_1, COMMIT_INSTRUCTION_NO_2 and so on, up to COMMIT_INSTRUCTION_NO_5 with respect to each commit instruction to PCA.
4.10.1
RTR System Error Logging for Commit Instruction Break Point and Retry Mechanism RTR also logs the relevant messages in the system error log: •
Description of error with RTR phase name.
•
The FDN of Managed Objects and related attributes that are being reparented in the current CS transaction.
5/1553-APR 901 0227 Uen D | 2011-12-12
31
RTR, Radio Tool for Reparenting, User Guide
•
Current retry count.
•
Retry count left.
When adding commit instruction, RTR will add a description to the system error logs if PCA throws the exception, PCAExceptions.DATASTORE_EXCEPTION. The description includes the plan name and the phase name.
32
5/1553-APR 901 0227 Uen D | 2011-12-12
Using Online Help
5
Using Online Help Help is available by clicking the Help button (which is located at the bottom centre,) on the main window. The Help browser opens displaying the Online Help information.
5.1
Help Browser Online Help is shown inside a browser window with three separate frames. The toolbar frame on the top contains buttons with functions. On the left, there is a navigation frame with the Help topics. The Help topics can be shown as a tree structure or as an alphabetically-sorted index list. Click a Help topic to display the Help text for the topic in the content frame in the right pane.
5/1553-APR 901 0227 Uen D | 2011-12-12
33
RTR, Radio Tool for Reparenting, User Guide
34
5/1553-APR 901 0227 Uen D | 2011-12-12
Glossary
Glossary See Operations Support System (OSS) Glossary, Reference [1].
5/1553-APR 901 0227 Uen D | 2011-12-12
35
RTR, Radio Tool for Reparenting, User Guide
36
5/1553-APR 901 0227 Uen D | 2011-12-12
Reference List
Reference List
[1]
Operations Support System (OSS) Glossary
[2]
OSS Library Typographic Conventions
[3]
CEX, OSS Common Explorer, User Guide
[4]
PCA, Planned Configuration Administration, User Guide
[5]
ATM RBS Reparenting Preparation Phase
[6]
IP RBS Reparenting Preparation Phase
[7]
ATM RBS Reparenting Execution Phase
[8]
IP RBS Reparenting Execution Phase
[9]
Fallback, User Guide
[10] Sub-Network Model Consistency User Guide [11] License Key Administration in OSS-RC
5/1553-APR 901 0227 Uen D | 2011-12-12
37