Ericsson Internal

INSTRUCTION 1 (5)
Prepared (also subject responsible if other) No.

GSDC Australia\earmcat (Armin Catovic)

Approved Checked Date Rev Reference

2008-07-13 PA1

Performing RAN Node Upgrade Using Moshell (WI)

Abstract

This document provides step-by-step instructions on how to perform a

software upgrade using moshell. It is based on the moshell “Lazy Guide”,
accessible via h 5 directive in moshell. This document may be especially
useful in following situations:

 On-site single node upgrade in STP

 Remote single node upgrade in STP

 On-site single node upgrade on customer premises

 Remote single node upgrade on customer premises with direct

connection to the node i.e. no tunnelling required

NOTE: For multiple node upgrades it is recommended to use mobatch (see

Appendix A)

Application

Step 1:

Check for alarms and perform a general health check of the node (NOTE:
during health-check analysis ensure there are no disabled/faulty Plug-in Units
and that major alarms impacting upgrade are cleared). The results of a health
check are saved in the specified log file.

RNC> al
RNC> l+ <filename>
RNC> hc
RNC> l-

Step 2:
 Ericsson Internal
INSTRUCTION 2 (5)
Prepared (also subject responsible if other) No.

GSDC Australia\earmcat (Armin Catovic)

Approved Checked Date Rev Reference

2008-07-13 PA1

Ensure there is enough space on /c and /d partitions for the new software
package. If not then free up some space by (1) deleting upgrade packages
that are installed on the system but not used by any CVs and/or (2) deleting
old upgrade packages that are more than a year old or are not required.

Space requirements are dependant on the software being installed and these
should be verified in PLM delivery reports. Generally having 50% free space
available on /c and /d partitions will ensure successful software installation.

RNC> vols
RNC> lpr upgrade
RNC> cvls
RNC> del <upgrade_cv_proxy>

Step 3:

Create and backup a new CV.

RNC> cvmk <cv_name> <user_id> <comments>

RNC> cvget <cv_name>

Step 4:

Install any software licenses if required. This is done by executing

updateLicenseKeyFile action on the Licensing MO. Four parameters are
required: username and password of the FTP server where the license is
stored, the IP address of the FTP server and a filepath of the license file on
the FTP server.

RNC> acc Licensing updateLicenseKeyFile

If no FTP server is present and you are required to run an FTP server from
your laptop/workstation, see Appendix B.

Step 5:

Create the upgradePackage MO.

RNC> cr swmanagement=1,upgradepackage=<package_name>

(NOTE: at the prompt enter the FTP server IP, Upgrade Control File filepath
on the FTP server, and login details if applicable).

If no FTP server is present and you are required to run an FTP server from
your laptop/workstation, see Appendix B.

Step 6:
 Ericsson Internal
INSTRUCTION 3 (5)
Prepared (also subject responsible if other) No.

GSDC Australia\earmcat (Armin Catovic)

Approved Checked Date Rev Reference

2008-07-13 PA1

Check the proxy number of the newly created upgradePackage MO and start
the installation process.

RNC> lpr upgrade

RNC> acc <upgrade_mo_proxy> nonBlockingInstall

(NOTE: you can periodically check the installation progress by executing get
<upgrade_mo_proxy> progress|state)

It is also worth mentioning that there are two main methods of installation –
install (delta installation) and forcedInstall (full installation). Which one to
use will depend on the software being upgraded, and this is specified in PLM
delivery reports for that particular software. For example, upgrading P5 to P6
requires the use of forcedInstall whereas upgrading P4 to P5 doesn’t.

The nonBlocking installation type allows you to execute Moshell commands

while the installation is on-going – very useful especially for periodic checking
of installation progress. For non-blocking full installation use
nonBlockingForcedInstall.

Step 7:

Once the installation state is in INSTALL_COMPLETED, upgrade can be

performed.

RNC> acc <upgrade_mo_proxy> rebootNodeUpgrade

(NOTE: upgrade process can be periodically checked by executing get

<upgrade_mo_proxy> progressHeader|state)

Step 8:

When the upgrade state is in AWAITING_CONFIRMATION (following JVM

and node restarts, database reload and reconfiguration), the upgrade has
completed and can be confirmed.

RNC> acc <upgrade_mo_proxy> confirmUpgrade

Step 9:

Verify that the new CV is using the correct upgrade package (verify in
Upgrade Package column of CV list), and that the system-generated CV is
the final CV i.e. in following format Fi_CXP901xxxx_Rnnnnn_yymmdd_tttt

RNC> cvls

If AutoCreatedCV is enabled then after a short period of time the node will
perform a CV auto-create. In the CV list it is displayed in the following format:
Au_CXP901xxxx_Rnnnnn_yymmdd_tttt.
 Ericsson Internal
INSTRUCTION 4 (5)
Prepared (also subject responsible if other) No.

GSDC Australia\earmcat (Armin Catovic)

Approved Checked Date Rev Reference

2008-07-13 PA1

Step 10:

Perform post-upgrade health check and verify that no new alarms have been
created (see step 1).

Step 11:

If the upgrade is deemed successful create a new startable CV and back it up

onto your laptop

RNC> cvms <cv_name> <user_id> <comments>

RNC> cvget <cv_name>

Appendix A: Multiple node upgrades using mobatch

Mobatch is a tool that allows parallel execution of Moshell commands in

multiple nodes. This is particularly useful when upgrading multiple RBSs in an
RNS. Mobatch allows us to create a script and run it against a batch of nodes.

$ mobatch <node_batch_file> <moshell_command_file>

<log_file>

The batch file should be same format as the ipdatabase file i.e. first column
specifies the name of the node, the second column specified the IP address
of the node, and third column specifies the node password.

rbs01 10.0.0.2 rbs

rbs02 10.0.0.3 rbs
rbs03 10.0.0.4 rbs
rbs04 10.0.0.5 rbs
rbs05 10.0.0.6 rbs

For upgrades, it is therefore possible to specify several batches of nodes e.g.

8 batches of 10 RBSs, and execute Moshell commands one batch at a time in
order to avoid network congestion problems (particularly when performing
software installation).

The Moshell command file is a text file containing list of upgrade commands,
one line at a time. The convention is to save the command file with .mos file
extension. It is possible to have one large command file, or to split it up into
multiple scripts, each script executing set of commands related to a specific
upgrade stage e.g. pre-health-check, installation, upgrade, post-health-check,
backup.

The log file (the last mobatch argument) stores the results and output of
mobatch execution.
 Ericsson Internal
INSTRUCTION 5 (5)
Prepared (also subject responsible if other) No.

GSDC Australia\earmcat (Armin Catovic)

Approved Checked Date Rev Reference

2008-07-13 PA1

Appendix B: Setting up FTP server on your laptop/workstation

The following provides a quick guide on how to install FileZilla FTP server for
use with software upgrades. Other FTP server software can also be used
however it is the responsibility of engineer to ensure that it is configured
correctly. Generally, FTP server configuration is similar across the board,
however the interface may vary.

Step 1:

Download and install the FileZilla FTP server on the PC. FileZilla is an open
source FTP server freely available for download from http://filezilla-
project.org/download.php?type=server

Step 2:

Configure the FileZilla FTP server on your PC. Log into the FTP server
management interface by clicking Start, Programs, FileZilla Server and then
FileZilla Server Interface.

Connect to Server dialog box will pop-up; leave all the settings as default
and click Ok.

Go to Edit, Settings and under General Settings click on IP Bindings and

enter the IP address of your PC. Click Ok.

Go to Edit, Users, click on Add and type in username. (OPTIONAL: set the
password for the newly added user).

Click on Shared Folders and click Add. Select a folder that will be visible to
the node i.e. where the upgrade packages and licenses will be installed. For
example you may want to have a folder C:/ftpserver/ and in it two sub-
folders, up where upgrade packages will be installed and license where
software licenses will be installed.

Ensure that both Read and Write permissions are checked for this user and
then click Ok.

Extract all upgrade packages and licenses into the directory as setup above
and then in the FileZilla Server Interface click on Server and then Active.

Verify connectivity to FTP server using an FTP client such as FileZilla FTP
Client or WinSCP.