06 01 rn33156en10gla0 rnc sw maintenance

8/18/2019 06 01 Rn33156en10gla0 Rnc Sw Maintenance

http://slidepdf.com/reader/full/06-01-rn33156en10gla0-rnc-sw-maintenance 1/35

1 © Nokia Siemens Networks Presentation / Author / Date / Document Number

For public use – IPR applies

RNC Software Maintenance



2 © Noki a Si emens Net works Present ati on / Aut hor / Date / Doc ument Number


Nokia Siemens Networks Academy

Legal notice

Intellectual Property Rights

All copyrights and intellectual property rights for Nokia Siemens Networks training documentation,product documentation and slide presentation material, all of which are forthwith known as NokiaSiemens Networks training material, are the exclusive property of Nokia Siemens Networks. NokiaSiemens Networks owns the rights to copying, modification, translation, adaptation or derivativesincluding any improvements or developments. Nokia Siemens Networks has the sole right to copy,distribute, amend, modify, develop, license, sublicense, sell, transfer and assign the Nokia SiemensNetworks training material. Individuals can use the Nokia Siemens Networks training material for theirown personal self-development only, those same individuals cannot subsequently pass on that sameIntellectual Property to others without the prior written agreement of Nokia Siemens Networks. TheNokia Siemens Networks training material cannot be used outside of an agreed Nokia SiemensNetworks training session for development of groups without the prior written agreement of NokiaSiemens Networks.





Content

• CD Installation

• SW upgrade

• Rollback





CD Installation

CD Installation may add one or more of the following tasks:

• HMS Upgrade

• Boot Upgrade

• Conversions

• Multiple CD installation





CD Installation Procedures

1. Preparations

2. Transferring software into RNC

3. File conversions

4. CD installation

5. Activation new package





Preparation

Check pre-requiredsoftware

Make safecopy of active

package

Record RNC

configuration

Check pre-conditions

//run PRECHECKRNC.TEL

//delete non-default package

//create CDTEMP directory





Transferring Software into RNC

Download CD from NOLS

Copy CD from NetAct to RNC

Check CDTEMP directory

//IXX

//IXX

//MAS:XV





File Conversion

Copy needed files to

TMPDIR and CONVPR

Copy memory files to

disk

Check integrity&

Safecopy database

Run database and file

conversions

Copy converted files to

CDTEMP



10 ©Nokia Siemens Networks Presentat ion / Author / Date / Document Number


CD Installation

Add CD to active

package

Create new package

Activate new package

Upgrade Boot proms

Check package

consistency





Activate New Package

Activate new softwarepackage

Verify new package and

check database

Record RNC configuration

//WQC

//run PRECHECKRNC.TEL

//USS

HMS Upgrade





HMS Software Update Procedure

1. Preparation

2. Update HMS Nodes

3. Troubleshooting





Preparation (1/2)

Every criterion must be fulfilled

• OMU-1 must be in use (SP-EX, WO-EX)

• Perform updating during low traffic periods

• Remote update is not supported

• During updating the unit’s recovery functions are disabled

• PIUs must be in SE-NH, SP-EX or WO-EX and no faulty flag in anyunit

• While updating HMS slave and bridge RSMU, RRMU and OMUspare must be inSE-NH

• Do not detach the updating unit or turn its power off • Slave updating can be performed with a command for either all

units in subrack or each unit one by one





Preparation (2/2)

• No HMS services during the updating HMS bridge subrack

• Use HMEXTE service terminal extension to update&check HMSslave/bridge/master code versions Check alarm history related HWalarms (AAP,UDU)

• Check Flash programmer ’s version before HMS update

• Check variants of HMS node

• Check HMS code version

• Do not continue if problems occur during the update. Stop andrepair problem before continuing

• Updating order is Slave nodes, Bridge nodes, and Masternodes.





Check HMS Flash Programmer

Block alarms and change

RSMU OMU state

Check Slave nodes

Unblock alarms and change

RSMU, OMU state

Enable switchover and clear

FBAN

Check Master nodesCheck Bridge nodes

Set FBAN flags for all units





Check HMS Code Version

Check Master’s code version

Check Bridge’s code version

Check Slave’s code version

//HCI →address of the local HMS master node

//HCO:0,0,0 and HCO:0,0,1

//HFB, HCM, HCO, HFD, HFC

//HCO:c,s,ppa





HMS Updating Sequence

Update HMS-slave

Update HMS-bridge

Update HMS-master





Updating HMS Slave Node

Set FBAN flags and block

alarms

Update HMS-slave code in all

PIUs in the subrack

Update HMS-slave code in

one PIU in the subrack

Enable switchovers and clear

FBAN flags

//FA:<rack>,<subrack>,<ppa>::<directory/file_name>,

<file_type>

//AFB,AFP

//JT:ALL,,,S,FBAN

//FB//DP

//FA:<rack>,<subrack>,3C::<directory/file_name>,

<file_type>

//CM

//TBU

//FD

//FC

//JT:ALL,,,C,FBAN

//AFU

//AFP

//DP





Updating HMS Bridge Node

Set FBAN flags and blockalarms

Update HMS-bridge code in all

TSS3 and TBUF


FBAN flags

//AFB,AFP//JT:ALL,,,S,FBAN

//FB

//CM

//DP

//FA:<rack>,<subrack>,<ppa>::<directory/file_name>,

<file_type> ; <ppa> line00=3D, line01=3E

//DP

//FD

//CM

//TBU

//FD

//FC//JT:ALL,,,C,FBAN

//AFU

//AFP

//DP





Updating HMS Master Node

Set FBAN flags and block

alarms

Update HMS-bridge code in all

TSS3 and TBUF


FBAN flags

//AFB,AFP

//FB

//JT:ALL,,,S,RBAN

//JT:ALL,,,C,FBAN

//FA:0,0,2::WO-/<directory/file_name>,<file_type>

//CM

//TBU

//FD

//FC

//FB

//CM

//TBU

//FD

//FC//JT:ALL,,,C,RBAN

//AFU

//AFP

//DP





RNC SW Upgrade

1. Preparation

2. Safecopying The Current Package

3. Copying The New Software

4. Checking Precondition

5. Running The Upgrade Macro

6. Checking The System Configuration

7. Updating HMS SW (see previous topic)





Preparation

• Checking Prerequisites – General

▪ RNC user account with full MML command authority (250)

▪ Telnet connection to the RNC

▪ General compatibility requirement (see SW Compatibility RN4.0)

▪ PC with HIT v2.8.0 or later

▪ Unit has to be either WO-EX, SP-EX or SE-NH

▪ No FLTY flag on any unit or sub-unit

▪ Enough free disk space for the new RN4.0 SW (about 1 000 000 BLOCK)Check with ZI WX: : WS, NODEF: : %, DI R, ;

– SW and Instruction

▪ RN4.0 Software Package

▪ Software Upgrade RN4.0

▪ RN4.0 CD0.0 Installation Instruction

▪ Boot and HMS Software Version for Q4 1.11-0

▪ Nokia Siemens Networks WCDMA RAN, Rel. RU10, System Library (NED)





Preparation – Supported Path

RN2.2RN2.2

RN3.0 + CD0.0RN3.0 + CD0.0

RN4.0 + CD0.0RN4.0 + CD0.0

CD1.0CD1.0

CD1.xCD1.x

CD2.0CD2.0

CD2.xCD2.x

trial & pilotCDs

RN4.0 release supports upgrade from RN3.0 release at any CD level. To

upgrade from RN2.2 release, the RNC must be upgraded to RN3.0 release first.





Preparation – Boot Compatibility

• RNC boot proms are NOT onwards compatible.

• At other hand, RNC boot proms are backward compatible.

• When RN3.0 SW is active, the required RN4.0 level boot promsneed to be burned first before the activation of RN4.0 SW package.

• Check required RN4.0 level boot proms from Boot and HMSSoftware Version for Q4 1.11-0 document





Safecopying The Current Package (1/2)

•Check the status of the current running software package

– ZWQO:CR;

•If the status is NW change it to BU

– ZWSC:STAT=NW:STAT=BU;

•If the status is FB change it to NW

– ZWSR;

•Verify the current software package

– ZWQB:NAME=<active_package_name>:FORM=FAILED;

•Make a safecopy of the current running package

– ZWKS:NAME=<fallback_package_name>,DIRE=<fallback_package_dir>,MODE=FULL;





Copying The New Software (1/2)

To copy the software from your PC (local/remote) to the RNC:

1. Transfer the compressed packages to the RNC with a File

Transfer Protocol (FTP) application.

2. Copy the compressed package to the /shadows/ directory of the

RNC.

– Q4011100_1.ZIP

– Q4011100_2.ZIP

– Q4011100_3.ZIP

3. Copy the Change Delivery to the / shadows/ directory of the

RNC.

– R400000N.ZIP





Copying The New Software (2/2)

To copy the software from NetAct to the RNC:

1. Transfer the compressed packages to the NetAct with an FTP application.

2. Import the compressed SW package files to the NetAct archive:

a. In the Top-level User Interface window, select Utils → Software Configuration Mgmt → NE

Software Configuration Mgmt.

b. In the NE Software Configuration Manager window:

c. Select Software Archive → RNC Software Packages

d. Select where compressed SW package files are stored.

e. Select → Import.

f. Select ZIP files and give the archive directory a name.

3. Download the compressed SW package files to the RNC:

a. In the NE Software Configuration Manager window, select Software Archive → RNC

Software Packages.b. Select the Archive Directory.

c. In the NE Software Configuration Manager window, select Managed Objects → RNC (where

to download)→ Download.





Checking PreconditionSaving configuration from the running package

• Open HIT and load RNC_configuration_check.tel macro

– If necessary create a new connection in HIT

Device Set Configuration New Telnet

fill in a name and the RNC IP address. If necessary select the Login tab and set theRNC user name and password

• Start the macro by clicking on the Play icon and fill in a name forthe log file that will be created in the same directory as the macrowas stored.





Checking PreconditionChecking and releasing locked files

• Check that there are no locked files

ZIWX::WS,DEF:LFILES,:%,%,;

• Check the HIT log. An L in the ATTR column will next to a fileinformation will indicate that a file is locked

• Release any locked files that are found

ZIWS::<disk>,DEF:LFILES:<file_name>,<ext>,,R,L;





Checking PreconditionChecking all active alarms and stopping command calendar jobs

• Printout and save all active alarmsZAAP;

• This step may have done during the execution ofRNC_configuration_check.tel macro.

• Examine alarms, try to remove alarms by carrying outmaintenance actions.

• Check that there are no command calendar jobs activeZICL;

• If any command calendar jobs are active then make a note of

them so that they can be restored after the upgrade and deletethe tasksZICD:<task_identifier>;





Checking PreconditionStopping NE and RNW measurements

• Stop NE measurement by following command

– ZT2E:NAME=<measurement_identifier>:; stop measurement

– ZT2E:NAME= to see list of measurements

– ZT2I; check measurement parameters for recreation later

• Stop RNW measurement by RNW measurement management application.





Running The Upgrade Macro (2/2)

– Updating boot proms

– Copying FIFILE

– Copying License files

– Activate the new SW package

– Change the new SW package status to BU

– Deleting temporary files and directories

– Safecopying the new SW package





Checking The System Configuration

To check the system configuration:

1. After the upgrade macro execution, run theRNC_configuration_check.tel macro again to collect up-to-dateinformation about the system.

2. When the macro has finished, compare the two log files: the onegenerated before the upgrade, and the one generated after theupgrade.





Rollback

• Rollback means activate the RN3.0 back again.

• Only possible before any HW changing takes place (includingreconfiguration RRMU to ICSU)

• Select RN3.0 SW package as default package

ZWSD:NAME=<RN3.0 package name>:;

06 01 rn33156en10gla0 rnc sw maintenance

Documents