HOWTO: PUSH NODEB SCRIPT CHANGES

CONTENTS

Purpose ......................................................................................................................................................... 1
Preparation ................................................................................................................................................... 2
Backup the NodeB..................................................................................................................................... 2
Backup the RNC......................................................................................................................................... 3
Executing the change .................................................................................................................................... 4
If the script is an XML file... ....................................................................................................................... 4
1. Push the script from your PC to M2000 server............................................................................. 4
2. push the script from M2000 server to the site ............................................................................. 5
3. ACTIVATE the script that you just pushed .................................................................................... 5
If the script is in MML Format... (.txt file) ................................................................................................. 6
Confirmation/Troubleshooting ..................................................................................................................... 7
Things to check... .................................................................................................................................. 7
Rolling back ................................................................................................................................................... 8

PURPOSE

With frequent Carrier Adds, Underlay changes, and just general config clean-up, it has become a
common task on most night shifts which we should ALL be very familiar with.

This document describes how to push a nodeb script to a site in a safe manner so that even in the
event of script errors, we can ensure that we are at least not causing a NEGATIVE impact, as well as
how to identify if a script has problems, and how to roll-back if necessary.
 PREPARATION

!Important!
Before you do anything else... Always make note of which cells were active before you began.
Depending on what the script is doing, you may be left with extra alarms, or cells that are supposed
to be left OFF until we are ready to test them. Or the script may have unexpected errors that cause
previously working cell-ids to fail.

Unless you know where you are starting from, you may not be able to tell if it was a success or not.

From the NodeB, run the MML command...

LST LOCELL;

Make note of these, and if these same cells are NOT active once you are done, you will have to roll-
back the change.

BACKUP THE NODEB

1. Login to M2000 and go to...

MAINTENANCE > BACKUP MANAGEMENT > NE BACKUP
2. Change the Drop-down on the left panel to NODEB

3. Drill down and click the check-box for your NodeB.

a. If you arent sure which district or RET_Ring to find it in, just open up the
Maintenance Topology and CTRL-F to find your NodeB ID. (The folder structure on
the left will indicate which district & RET Ring it is in)
 4. Click the BACKUP button
5. The backup progress will show in the bottom panel. Wait for it to reach 100%
6. The 3 most recent backups will be stored on the right. Check the backup time to ensure the
most recent timestamp is current.

a. To be EXTRA safe, you can also highlight your backup, and click DOWNLOAD TO OMC
CLIENT to save a Hard Copy of the XML onto your computer
**** If doing a nodeB or enodeB ID change, then make sure to download to
OMC client, as the backup disappears when the site number is changed

BACKUP THE RNC

If the changes are purely on the NodeB side, this may not be required. But its better to be safe than
sorry.

Login to MML for the appropriate RNC, and execute...

1. EXP CFGMML;
2. EXP INNERCFGMML;
3. BKP DB;

Also, you can do a complete backup of the RNC, using the same steps as for the NodeB

However, on Step 2, select BSC6900 UMTS instead of NodeB.

 EXECUTING THE CHANGE

If you arent specifically sent a script, they should be found on the network.

Y:\WirelessOps\UMTS\Site Scripts\

IF THE SCRIPT IS AN XML FILE...

If the scripts were done with XML, they are usually more reliable, since CME rule checking can
prevent a lot of the human errors.

Pushing an XML script is done in 3 steps...

1. PUSH THE SCRIPT FROM YOUR PC TO M2000 SERVER

From M2000
Select Software > NE File Transfer
Select > From OMC Client to OMC Server (from your PC to M2000)
NE Type = DBS3900WCDMA
File Type = Data
Click Select at the bottom, and browse to the folder where you saved the XML file
**MAKE SURE** you change the NE to the site you wish to modify

Hit OK to push the script up to M2000

Check the status in the bottom panel under the tab FTP Task
 2. PUSH THE SCRIPT FROM M2000 SERVER TO THE SITE

From M2000
Select Software > NE File Transfer
Select > From OMC Server to NE
NE Type = DBS3900 WCDMA
File Type = Data
Scroll down to your site, and Check the box of the File you wish to push (Note: The last
digits on the filename indicate the Date/Timestamp of when you uploaded it. This can help
to determine the correct file)

Hit OK to push the script to the site.

Check the status in the bottom panel under the tab Intermediate Task

3. ACTIVATE THE SCRIPT THAT YOU JUST PUSHED

Login to the LMT for the NodeB you are updating

Run MML > SET CFGFILEENB: FLAG=ENABLE, RSTMODE=IMMEDIATELY;
It will take around 5-10 minutes for the script to apply, and the NodeB to reset.

** WARNING! **
Once you hit hit OK, the site will reboot, and any changes you made will become active.
Make SURE you have pushed the proper script before enabling it...
If you push a script with bad IP information, you MAY lose continuity, and require rolling a truck to
manually load the proper BBU script again.
 IF THE SCRIPT IS IN MML FORMAT... (.TXT FILE)

The MML commands will most often be saved to a text document in the Site-Scripts folder on the
network. Proof-read the NodeB MML commands for errors against the CIQ.

The NodeB file requires the cells to be deactivated/activated in the RNC (The file should
indicate which lines to run from the RNC, and which lines to run from the NodeB)
The bulk of the commands will be run on the NodeB in the Maintenance client.
o Either run as a batch command
o Or run line by line from the MML window
(this method is slower, but easier to identify and fix errors on the fly.)
You will have to re-activate the cells on the RNC side once you are done.
 CONFIRMATION/TROUBLESHOOTING

The quickest way to confirm that the cell was successfully activated

LST LOCELL;

If the original cells fail to come back up, there are a few common things to look for

THINGS TO CHECK...

Some common reasons which a cell will fail to turn up, are...

1. License information is insufficient for the number of cells you are attempting to activate
a. Refer to http://netops/wiki/index.php/WNO:NodeB_License_Configuration
2. The cell is an EXTENDED CELL and has non-sufficient resources
a. Refer to http://netops/wiki/index.php/WNO:EXTENDED_CELL_HOWTO
3. 1 or more parameters are inconsistent between the RNC side and the NodeB side.
a. Check the cell configuration on both sides and ensure these key parameters all
match...

Local cell ID
Uplink UARFCN/ Uplink Frequency Channel Number
Downlink UARFCN/Downlink Frequency Channel Number
Max Output Power
Local Cell Radius

Check, and compare parameters on both NodeB & RNC side to ensure parameters are consistent.

NodeB LST LOCELL: MODE=LOCALCELL, LOCELL=102701301;

RNC LST UCELL:LSTTYPE=ByCellId,CELLID=2701,LSTFORMAT=VERTICAL;

 ROLLING BACK

After checking for any errors in the previous section, if the original cells still fail to come back
up, you will have to roll back the configuration to the latest backup.

1. Follow steps 1-3 from the Backup section

2. Select the most recent backup, and click Restore

3. Confirming the prompt will cause the NodeB to be restarted.

4. Once you are able to login to the NodeB again, check alarms, and make sure that all cells
are active.