3BK%2D17429%2D9089%2DRJZZA %289359%2DNPO Software Replacement %28Intra Muse Kernel%29 01%2E15 Standard June 2009

8/14/2019 3BK%2D17429%2D9089%2DRJZZA %289359%2DNPO Software Replacement %28Intra Muse Kernel%29 01%2E15

1/69


2/69

Wireless Service Provider Solutions

Alcatel-Lucent 9359 Network Performance Optimizer

Software Replacement (Intra Muse Kernel)Document number: 3BK-17429-9089-RJZZADocument issue: 01.15/ENDocument status: StandardProduct release: OAM 5.2Date: June 2009

Alcatel-Lucent - Internal - Proprietary - Use pursuant to Company instruction

Copyright 2004-2008 Alcatel-Lucent, All Rights Reserved

UNCONTROLLED COPY: The master of this document is stored on an electronic database and is "writeprotected"; it may be altered only by authorized persons. While copies may be printed, it is notrecommended. Viewing of the master electronically ensures access to the current issue. Any hardcopiestaken must be regarded as uncontrolled copies.

ALCATEL-LUCENT CONFIDENTIAL: The information contained in this document is the property ofAlcatel-Lucent. Except as expressly authorized in writing by Alcatel-Lucent, the holder shall keep allinformation contained herein confidential, shall disclose the information only to its employees with a needto know, and shall protect the information from disclosure and dissemination to third parties. Except asexpressly authorized in writing by Alcatel-Lucent, the holder is granted no rights to use the informationcontained herein. If you have received this document in error, please notify the sender and destroy itimmediately.

Alcatel-Lucent, Alcatel, Lucent Technologies and their respective logos are trademarks and service marksof Alcatel-Lucent, Alcatel and Lucent Technologies.

Oracle is a registered trademark of Oracle Corporation and/or its affiliates.

All other trademarks are the property of their owners.


3/69

PUBLICATION HISTORYSYSTEM RELEASE NPO 5.2 (M2.3)

June 2009

Issue 01.15/EN, Standard

Resolution of FR: 3BKA85FBR279358

October 2008


Update of Schedule section

September 2008


Update of Import Dictionaries

September 2008


Update of Backup and Restore procedures

September 2008


Update of Start NPO Application procedure

September 2008


Update after internal review

Resolution of FR 3BKA85FBR251522

July 2008Issue 01.09/EN, Standard

Update for server in cluster configuration

June 2008


Update ofStart NPO Client Applicationprocedure.

Improvement of the procedure

Publication history 3

Copyright 2004-2008 Alcatel-Lucent Software Replacement (Intra Muse Kernel)


4/69

June 2008Issue 01.07/EN, Preliminary

Update of the cluster configuration section

April 2008

Issue 01.06/EN, Preliminary


March 2008

Issue 01.05/EN, Draft


February 2008



December 2007



November 2007


Add the CD2P and Oracle sections

October 2007


Creation of the document

Publication history 4

3BK-17429-9089-RJZZA 01.15/EN Standard June 2009 Copyright 2004-2008 Alcatel-Lucent


5/69

1 About this Publication................................................................................................................................................... 7

2 UMTS Access Network Collection Roadmap...............................................................................................................8

3 New in This Release.......................................................................................................................................................9

4 Overview....................................................................................................................................................................... 10

4.1 Before You Start....................................................................................................................................................... 11

4.2 Initial Status.............................................................................................................................................................. 12

4.3 Final Status...............................................................................................................................................................13

4.4 Schedule..................................................................................................................................................................14

4.5 Impact on Service...................................................................................................................................................15

4.6 Restrictions.............................................................................................................................................................16

4.7 Supplies, Tools and Documentation.........................................................................................................................17

4.7.1 Supplies..............................................................................................................................................................18

4.7.2 Tools...................................................................................................................................................................19

4.7.3 Documentation................................................................................................................................................... 20

4.8 Conventions............................................................................................................................................................21

5 PI01 - Upgrade Server in non Cluster Configuration................................................................................................ 22

5.1 Initial Tasks on Server............................................................................................................................................23

5.1.1 Perform a Full Backup.................................................................................................................................. 24

5.1.2 Check Active Instance.................................................................................................................................. 26

5.1.3 Stop Processes.............................................................................................................................................27

5.2 Perform Software Upgrade.................................................................................................................................... 28

5.2.1 Upgrade CD1................................................................................................................................................29

5.2.2 Upgrade CD2S............................................................................................................................................. 30

5.2.3 Upgrade CD2P............................................................................................................................................. 32

5.2.4 Upgrade ORACLE........................................................................................................................................ 34

5.2.5 Upgrade CD3S............................................................................................................................................. 38

5.2.6 Upgrade CD4................................................................................................................................................41

5.2.7 Upgrade Generic Documentation................................................................................................................. 43

5.2.8 Start the Application......................................................................................................................................45

5.2.9 Import Dictionaries........................................................................................................................................47

5.3 Post Upgrade Tasks................................................................................................................................................. 49

5.4 Upgrade NPO Client Application.............................................................................................................................. 51

5.4.1 Uninstall Client Software.................................................................................................................................... 52

5.4.2 Start NPO Client Application.............................................................................................................................. 54

5.5 Remove Old Instance............................................................................................................................................... 56

Table of contents 5



6/69

6 Reverse Procedure.......................................................................................................................................................57

7 PI02 - Upgrade Server in Cluster Configuration........................................................................................................58

7.1 Initial Tasks on Server............................................................................................................................................59

7.1.1 Perform a Full Backup.................................................................................................................................. 60

7.1.2 Check Active Instance.................................................................................................................................. 62

7.1.3 Stop Processes.............................................................................................................................................63

7.2 Perform Software Upgrade.......................................................................................................................................64

7.3 Post Upgrade Tasks................................................................................................................................................. 66

Table of contents 6



7/69

1 About this PublicationThis document describes how to perform a software upgrade from MS-OMC Portal/9359-NPO

software version "N" to MS-OMC Portal/9359-NPO software version "N+m" on Server and Client

configurations with the same hardware (based on MUSE 2.3). This document covers both cluster and

non-cluster configurations.

Audience

This document is intended for:

Field service technicians

Project managers

Site administrators

System support engineers (specialists)

Occasional users (e.g. subcontractors).

Prerequisites

You must have a basic understanding of the following:

ALCATEL-LUCENT operations and maintenance concepts.

Solaris 10 administration

Oracle 10g administration

Installation tools and materials

Safety Instructions.

7



8/69


9/69

3 New in This ReleaseThe following sections detail what is new or updated in NPO software replacement for a same

hardware (OAM 5.2 based on Muse 2.3).

New Sections

PI02 - Upgrade Server in Cluster Configuration

Modified Sections

Schedule

Perform a Full Backup

Post Upgrade Tasks

Reverse Procedure

Import Dictionaries

Start NPO Client Application

9



10/69

4 OverviewThis Overview provides general information about this procedure.

ATTENTIONDuring the whole procedure, consult the appropriate and most recent ReleaseNote according to your configuration, cluster or non-cluster: refer to the [5]External Release Notes for 9359 NPO OAM5.2 & OAM6.0K to apply additionalcommands if needed.

10



11/69

4.1 Before You StartBefore starting the migration, perform the following checks:

Check that the customer has been informed about the operations:

date

time

site name

site address

purpose of the operation has been indicated

Check that human resources are available and complete for the operation. Check that tools and supplies are available and complete for the operation.

Check that the documentation is available and complete.

See theUpgrade CD1

11



12/69

4.2 Initial StatusBefore starting, ensure that:

The MS-OMC Portal/9359-NPO software is installed and running.

Several WMS data sources are declared on NPO Server.

A full backup of the MS-OMC Portal/9359-NPO Server has been made.

12



13/69

4.3 Final StatusAt the end of the upgrade, you can check:

The MS-OMC Portal/9359-NPO newer software is installed and running.

The same WMS data sources are declared on NPO Server.

A full backup of the MS-OMC Portal/9359-NPO Server has been made.

13



14/69

4.4 ScheduleThe following table displays the time required to perform the different tasks. It depends on the CD to

install

PI No. PI Titles Time

PI 01 Upgrade Server in noncluster configuration

from 7h to 11h(Depending on configura-tion)

PI 02 Upgrade Server in clusterconfiguration

In Master node: from 7h to 11h

In Slave node: around 3h

(Depending on configuration)

14



15/69

4.5 Impact on ServiceNone.

The NPO service is unavailable during the upgrade. At the end of the upgrade, all the remaining

NPO data are retrieved from WMS.

Therefore, there is no loss of NPO data.

15



16/69


17/69

4.7 Supplies, Tools and DocumentationThis section provides information about:

Supplies

Tools

Documentation

17



18/69

4.7.1 SuppliesA tape is needed to perform the full backup of NPO database.

18



19/69

4.7.2 ToolsThe needed tools are listed below.

Item Version Case

CD1 CD-ROM, DVD-ROM, CD4CD-ROM, Generic Documenta-tion CD-ROM

The currently installed version onServer machine

Server

DVD-ROM (CD2S + CD3S) The new version, to be used at up-

grade procedure:

CD2S_MS_*

CD3S_MS_*

OMC_INST_*

Server

Client

CD4 CD-ROM CD4_NPO_M2* Server

CD-ROM for Generic CustomerDocumentation

Customer generic documentation Server

19



20/69

4.7.3 DocumentationThe needed applicable documentation is listed below.

No. Designation Reference

[1] Alcatel-Lucent 9359 Network Performance Op-timizer- Server and Client Installation

3BK 17429 9087 RJZZA

[2] 9953 MP / NPO Platform Administration Guide 3BK 21315 AAAB PCZZA

[3] Alcatel-Lucent 9359 Network Performance Op-timizer- Completion Check List

3BK 17429 9085 RJZZA

[4] Alcatel-Lucent 9359 Network Performance Op-

timizer- Service Reference Sheet

3BK 17429 9086 RJZZA

[5] External Release Notes for for 9359 NPOOAM5.2 & OAM6.0K

UMT/OAM/DJD/

NPO_W23xxxxxfile for a non-cluster

configuration

NPO_W23xxxxxCfor a cluster config-

uration

20



21/69

4.8 ConventionsThe following conventions are used in the document:

Keyboard keys are indicated in the text as [XX]

System messages appear in bold font after a double left-oriented arrow:operator_input

For the axadmin user:

>>axadmin@host$ operator_input

Software buttons and icons on a terminal screen are also indicated in the text as [XX] .

Menu paths are chained with"->". Example:

Tools -> Options -> Printer -> ...

21



22/69

5 PI01 - Upgrade Server in non Cluster ConfigurationThis chapter describes the procedures to be followed for the MS-OMC Portal/9359-NPO Server

software replacement.

22



23/69

5.1 Initial Tasks on ServerThree initial tasks has to be done before performing the software replacement in non cluster

configuration:


Check Active Instance

Stop Processes

23



24/69

5.1.1 Perform a Full BackupDifferent solutions are available to backup data before proceeding with the software replacement in

non-cluster configuration. Using one or the other depends on your hardware configuration. This can

be useful in case you need to restore data.

Note: This procedure takes at least 1h 30 on the server.

ATTENTION

All chapters indicated in this section refer to procedures detailed in thePlatform

Administration Guidedocument (3BK 21315 AAAA PCZZA)

Read also the appropriate and most recent Release Note: [5] External Release Notes

for NPO OAMx.x to apply additional commands if needed.

Solution 1 - Local backup using Oracle Secure Backup.

This solution allows a direct backup of Oracle DB files and user management data on a single tape

for:

N240 / DAT72

N240 / SDLT600

V490 (2 or 4 CPU) / SDLT600 devicesIf you choose this solution then:

Refer to the section7.1.4 - Tapes devicesto prepare the tape device

Perform the backup:

If the1 OSBoption has been chosen when generating the server profile at the serverinstallation, then theBACKUP_TYPEparameter has been automatically set toOSB value. Inthis case, refer to the section 7.3.2 - Perform Backup with OSB

If the2 Otheroption has been chosen when generating the server profile at the serverinstallation, then theBACKUP_TYPEparameter has been automatically set toNETWORKERvalue. In this case, you must firstly refer to the section 7.3.1 - Install the OSBSoftwarebefore referring to the section7.3.2 - Perform Backup with OSB.

Note: With the OSB solution, the Oracle Data Base must always run in ARCHIVELOG modewhichever the schedule of backup is. In another words, the offline backup performed while theOracle data Base is in NOARCHIVELOG mode is not supported by OSB scripts.

Solution 2 - Legato Centralized Backup

This solution allows a direct backup of Oracle DB files and user management data for the V490 (2 or

4 CPU) / SDLT600 device. Legato Networker must be installed on an external SUN server with at

least 1TByte of disk space and a gigabit Ethernet interface.

24



25/69

If you choose this solution then:

Refer to the section7.2 - Configure Gb/s Network Interface for Backup Serverto configure the IPinterface device

Refer to the section7.4 - Legato Backup / Restore

If Legato Networker is not installed , refer to the section7.4.1 - Install Legato NetworkerServerto install and configure it.

If Legato Networker is installed, start from the section7.4.1.6 - Configure Legato Device fromLegato Clientto configure it.

Refer to the section7.4.2 - Perform Backup on Legato Clientto perform the backup

Note: With the Legato solution, the Oracle Data Base must always run in ARCHIVELOG modewhichever the schedule of backup is. In another words, the offline backup performed while theOracle data Base is in NOARCHIVELOG mode is not supported by Legato backup scripts.

25



26/69

5.1.2 Check Active InstanceNote: This procedure takes2 min .

Procedure

Step Action

1. Open a Terminal window as root.

2. Launch the Firefox browser from the command line:

>>cd /usr/local/firefox

>>./firefox

If an "Alert" pop-up window appears, click on [OK] .

3. Open the following URL address:

http:///osm/admin

4. In the prompt window:

Log in withosmadmin(default password: alcatel ).

Click on [OK].

Click on process monitoring.

Read System version / Instance.

Note down active instance number on a paper.

--End--

26



27/69

5.1.3 Stop ProcessesNote: This procedure takes8 min.

Procedure

Step Action

1. Using the same firefox browser:

Click on "process monitoring". Clic on "Stop all".

2. Wait until the processes of NPO part and CoreServices part are stopped (orange leds)

--End--

27



28/69

5.2 Perform Software UpgradeThis section describes how to upgrade the software:

Upgrade CD1

Upgrade CD2S

Upgrade CD2P

Upgrade ORACLE

Upgrade CD3S

Upgrade CD4

Upgrade Generic Documentation Start the Application

Import Dictionaries

28



29/69

5.2.1 Upgrade CD1

ATTENTION

See the [5] External Release Notes for NPO OAMx.x document to know whether it is

mandatory to change it.If the CD1 must be changed, you must perform a complete

reinstallation and not only an upgrade. In this case, use the [1] Alcatel-Lucent

9359 Network Performance Optimizer-Server and Client Installation document.

29



30/69

5.2.2 Upgrade CD2SNote: This procedure takes10 min.

ATTENTION

Ensure that the CD2S version has changed before proceeding with the upgrade.

ATTENTION

All actions on the NPO server MUST BE PERFORMED ON THE LOCAL CONSOLE (

whatever is defined for the specific server: either local Screen and Keyboard, or serial

connection)

Perform the following actions as root on the server:

Procedure

Step Action

1. Insert in the drive the DVD-ROM containing the new software version.

2. Mount the CD2S_MSx_xxxxxxxx. iso image as follows:

>>#cd /alcatel

>>#mkdir -p iso/cd2s

>>#lofiadm -a /cdrom/cdrom0/CD2S_MSx_xxxxxxxx.iso

#mount -F hsfs -o ro /dev/lofi/n /alcatel/iso/cd2s

nis given by the system

3. Launch the CD2S upgrade:

>>cd /alcatel/iso/cd2s/UPG

>>./upg_3PP

4. Wait for the software upgrade.

5. Unmount the CD2S_MSx_xxxxxxxx. iso image as follows:

>>#cd /

30



31/69

>>#mount -v

Look in alcatel/iso/cd2s and note the related number of /dev/lofi:

>>#cd /alcatel

>>#umount /alcatel/iso/cd2s

>>#lofiadm -d /dev/lofi/n

nis the number noted above:

6. Verify that the signature of CD2S version is updated:

>>#more /etc/A1353RA.signature

7. Check the CD2S log file:>>cd /var/omc3/install

>>egrep -i " error|^error" *.log

Note: If errors appear during the software upgrade procedure, please check the [5] ExternalRelease Notes for NPO OAMx.x document.

--End--

31



32/69

5.2.3 Upgrade CD2PNote: This procedure takes20 min.

ATTENTION

Ensure that the CD2P version has changed before proceeding with the upgrade.

ATTENTION

In "Remote " connection, use onlyssh, do not use telnet or rlogin.

Perform the following actions as root on the server.

Procedure

Step Action

1. Mount the CD2P_MSx_xxxxxxxx. iso image as follows:>>#cd /alcatel

>>#mkdir -p iso/cd2p

>>#lofiadm -a /cdrom/cdrom0/CD2P_MSx_xxxxxxxx.iso

cd /alcatel/iso/cd2p

>>./install_PATCHESNote: The server automatically reboots during this step.

3. Check that the software upgrade is finished:

>>vi /var/sadm/system/logs/time.log

4. Wait for the software upgrade.

5. Verify that the signature of CD2P version is updated:


32



33/69

6. Check the CD2P log file:>>cd /var/omc3/install

>>egrep -i " error|^error" install_PATCHES.log

>>egrep -i " error|^error" install_mng.log


--End--

33



34/69

5.2.4 Upgrade ORACLENote: This procedure takes1h00.

ATTENTION

Ensure that the Oracle version has changed before proceeding with the upgrade.

ATTENTION

In remote connection, use onlyssh, do not use telnet or rlogin.


Procedure

Step Action

1. Edit the file :>>vi /etc/inittab

Comment the following line:

m1:234:respawn:/alcatel/omc1/OMC_MON/script/mon

-c/alcatel/omc1/OMC_MON/conf/mon.cf 1>/dev/null 2>&1 #OSM mon daemon

2. To take into account the modification of the file /etc/inittab, execute the command:

>>init q

3. Stop the Base Oracle

Non Cluster Configuration su - oracle dbshut exit

Cluster Configuration su - oracle cd / opt/app/oracle/product/10.2.0/bin/ ./srvctl stop

database -d SNM exit

4. Check that the database is stopped:

>>ps -ef | grep ora_

>>ps -ef | grep lsn

34



35/69

Wait until each of the previous commands returns nothing on the screen.

5. Asroot, type:

>>cd /alcatel

>>cp /cdrom/cdrom0/OMC_INST_Mxx.Xxxxxx.tar.gz .

>>gzip -cd OMC_INST_Mxx.Xxxxxx.tar.gz | tar xvf -

6. Regenerate server profile, asrootuser:

>>cd /alcatel/OMC_INST_M23_Xxxxx

>>./gen_profile

Note: Do not edit the "Server Profile" file because it is automatically generated and should notbe modified.

7. At the question,

y

8. The following information is displayed:


36/69

If no SDLT device is connected, the OSB option will not be available.

Note: The option number 3 -No archive is only for testing. You are not allowed to use it in anyother situation.

Type your option for backup/restore solution, then press [Enter]

9. The following message is displayed:

./server_install /var/tmp/server.profile

The software to be installed appears and the following message is displayed:

[Enter] to continue the installation

12. Check that only Oracle Patch is installed.

13. After patch installation, uncomment the last line of the file /etc/inittab

14. Execute the command:

>>init q

15. Reboot the Server:

>>reboot

Wait for this machine to comes up.

16. Verify that the signature of Oracle version is updated:


17. Check the Oracle log files:

36



37/69

>>cd /alcatel/install/log

>>egrep -i " error|^error" oraclepatch.log

>>egrep -i " error|^error" server_install.log_xxx (xxx is the file date)


--End--

37



38/69

5.2.5 Upgrade CD3SNote: This procedure takes30 min.

ATTENTION

Ensure that the CD3S version has changed before proceeding with the upgrade.

ATTENTION



Procedure

Step Action

1. Mount the CD3S_MS_xxxxxxxx. iso image as follows:>>#cd /alcatel

>>#mkdir -p iso/cd3s

>>#lofiadm -a /cdrom/cdrom0/CD3S_MS_xxxxxxxx.iso

#mount -F hsfs -o ro /dev/lofi/n /alcatel/iso/cd3s


2. Launch the installation script:

>>cd /alcatel/iso/cd3s

>>./gen_install.pl

3. Answer at the following questions as follows:


39/69


40/69


8. Unmount the CD3S_MS_xxxxxxxx. iso image as follows

>>#cd /

>>#mount -v

The tag of product currently installed, if you want to upgrade the software.

Look in alcatel/iso/cd3s and note the related number of /dev/lofi:

>>#umount /alcatel/iso/cd3s

>>#lofiadm -d /dev/lofi/n


9. Remove the current DVD from the drive:

>>cd /

>>eject

10. Reboot the Server :

>>reboot

Wait for this machine to comes up.

11. Customize Iconbox as Supervision / NPO Only

This task can be performed only if the current installed product is MS-OMC Portal. It allows you

to configure only Supervision or only NPO. In this case, perform Customize Iconbox as

Supervision / NPO Only from [2] 9953 MP / NPO Platform Administration Guide.

Note: This task cannot be used to migrate from 9159 NPO product to MS-OMC Portal.

--End--

40



41/69

5.2.6 Upgrade CD4Note: This procedure takes10 min.

ATTENTION

Ensure that the CD4 version has changed before proceeding with the upgrade.

ATTENTION



Procedure

Step Action

1. Insert thenew CD4 CD-ROM in the drive.

2. Launch the CD4 installation

>>cd /cdrom/cdrom0

>>./install.sh

The following message appears

>cd /var/sadm/install/logs

>>egrep -i " error|^error" *.log

Note: If errors appear during the software procedure upgrade, please check the [5] External

41



42/69

Release Notes for NPO OAMx.x document.

Note: If the problems persists, apply theReverse Procedure

--End--

42



43/69

5.2.7 Upgrade Generic DocumentationNote: This procedure takes5 min.

ATTENTION

Ensure that the Documentation version has changed before proceeding with the

upgrade.

ATTENTION



Procedure

Step Action

1. Insert the documentation CD-ROM

2. Change the current directory:

>>cd /cdrom/cdrom0

3. Remove the documentation:

Note: When launching the removal, some files can not be accessed and causes 2 errormessages, do not take into account.

>>./remove_muse_doc

./install_muse_doc

The documents are installed in /alcatel/docs/21368/data/collection directory.

5. Remove the current CD-ROM from the drive:

>>cd /

>>eject

43



44/69

--End--

44



45/69

5.2.8 Start the ApplicationNote: This procedure takes10 min.on the Server.

ATTENTION



Procedure

Step Action



>>./firefox

If an "Alert" pop-up window appears, click on [ OK ]


http:///osm/adm

Thecan be:

The IP address of the server, if you upgrade NPO in non cluster configuration

The Master IP address, if you upgrade the master node of NPO in cluster configuration

The Slave IP address, if you upgrade the slave node of NPO in cluster configuration


Log in with osmadmin (default password: alcatel )

Click on [ OK ]

4. In "Process Monitoring" window, select:

Processes -> Start All

"Confirmation: do you want to start the system ?" Click on [OK]

5. Wait until all leds are green.

45



46/69

6. If there are still red leds, please call Alcatel-Lucent GPS for support.

7. Close the Firefox browser.

--End--

46



47/69

5.2.9 Import DictionariesNote: This procedure takes from2h45to 4h45on the Server. (Depending on configuration)

ATTENTION

Ensure that the Dictionaries version has changed before proceeding with the upgrade.

ATTENTION


Procedure

Step Action

1. Change in "offlinetool.properties" file

Caution:The change in "offlinetool.properties has to be made ONLY if you are not doing amigration from RNO/NPA.

Edit the file: /alcatel/muse/MUSE_QOS/offlinetool/config/offlinetool.properties

Set the value of the parameter muse.offlinetool.historic.partition=FALSE

Save the file and close the editor.

2. Import dictionaries

Caution:Before launching this script, ensure that the NPO server is running in order to import

dictionaries successfully.

If needed, insert the CD4 in the drive.

Log in asroot

Launch the Import Dictionaries:

>>cd /cdrom/cdrom0

./umtsfullinstall.sh

Answer "y" and then press Enter

47



48/69


49/69

5.3 Post Upgrade TasksIt is recommended to perform a backup at the end of the software upgrade. Several backup / restore

solutions are available. Using one or the other depends on your hardware configuration.


ATTENTION

All chapters indicated in this section refer to procedures described in the Platform




Solution 1 - Local backup using Oracle Secure Backup.

This solution allows a direct backup of Oracle DB files and user management data on a single tape

for:

N240 / DAT72

N240 / SDLT600

V490 (2 or 4 CPU) / SDLT600 devices


Refer to the section7.1.4 - Tapes devicesto prepare the tape device

Perform the backup:

If the1 OSBoption has been chosen when generating the server profile at the serverupgrade, then theBACKUP_TYPEparameter has been automatically set toOSB value. Inthis case, refer to the section 7.3.2 - Perform Backup with OSB

If the2 Otheroption has been chosen when generating the server profile at the serverupgrade, then theBACKUP_TYPEparameter has been automatically set toNETWORKERvalue. In this case, you must firstly refer to the section 7.3.1 - Install the OSB Software, thenrefer to the section7.3.2 - Perform Backup with OSB.

Note: With the OSB solution, the Oracle Data Base must always run in ARCHIVELOG modewhichever the schedule of backup is. In another words, the offline backup performed while theOracle data Base is in NOARCHIVELOG mode is not supported by OSB scripts.


This solution allows a direct backup of Oracle DB files and user management data for the V490 (2 or

4 CPU) / SDLT600 device. Legato Networker must be installed on an external SUN server with at

least 1TByte of disk space and a gigabit Ethernet interface.


49



50/69



If Legato Networker is not installed, refer to the section7.4.1 - Install Legato NetworkerServerto install and configure it.




50



51/69

5.4 Upgrade NPO Client ApplicationThis procedure describes how to upgrade the NPO application on the Client PC. You must:

Uninstall Client Software


51



52/69

5.4.1 Uninstall Client Software

Note: This procedure takes20 minon the Client.

ATTENTION

Perform this procedure only if the NPO Client application has been previously installed

with the M2.2.1 software version.

Procedure

Step Action

1. Logon as administrator on the Client PC

2. Close all opened applications

3. SelectStart -> Run,

Entercmd

press [enter]

A command window opens. Enter>>C:to be sure to be on C:\

4. Enter the following path to go to the Tools folder

>>C:\CD PC_install\OMC_INST_y\OMC_INST_x\windows\Tools

Note: OMC_INST_y and OMC_INST_x corresponds to the software currently installed on thePC, and not the new one.

5. Editclient.Uninstall.profile

EnterN for JRE (Java)

EnterY in the flag position for all other installed applications

Save and close the file

6. Reboot the Client PC

7. Go to the following folder:

>>C:\CD PC_install\OMC_INST_y\OMC_INST_x\windows

52



53/69

Note: OMC_INST_y and OMC_INST_x corresponds to the software currently installed on thePC, and not the new one.

8. LaunchUninstall.pland wait for the end of the uninstallation

Note: If theRegSrv32pop-up appears, click on [OK].

The Client PC automatically reboots

9. Logon as administrator on the Client PC

10. SelectStart -> Settings -> Control Panel -> Add/Remove programs

11. Remove all JREs and Perl softwares

Confirm the reboot of the machine when it is requested.

12. Close the Add and Remove Programs Tool window

13. Delete manually the following directories if they are present:

c:\ILOGdirectory

c:\log_Uninstalldirectory

c:\omcdirectory

c:\omc_installdirectory c:\PC_installdirectory

c:\Perldirectory

14. Check thatc/\cygwindirectory does not exist anymore. If it still exists, rename it.

15. Reboot the PC.

--End--

53



54/69

5.4.2 Start NPO Client Application

Note: This procedure takes5 min on the Client.

ATTENTION

In order to start the 9359 NPO Application on the Client machine, JDK 1.5.0.14 ( "J2SE

Developement KIT 5.0 update 14") must be available on the machine.

Procedure

Step Action

1. To check the JDK version, go tostart -> setting -> control panel -> Add/remove program

2. Ensure that the "J2SE Developpement KIT 5.0 update 14" is available on the machine else youmust install it such as indicated below:

Enter the following IP address in a web browser:http://

Click on the "INSTALL FIRST" button

Click on "Download jdk-1-5-0-14-windows-i586-p.exe to PC"

Answer to the installation questions (confirm, continue,etc...)

3. To start the NPO application, click on the START button on your PC to open iconbox

4. Log in to the Client application (user: "osmadmin", password: "alcatel" and check that the newinstance is OK).

5. Check that the declared data sources are present:

Open Muse applications / NPO data Management / configuration / data source and check

datasources.

Check import follow up: see (NPO data Management / administration / import follow-up).

Check consolidation follow-up: see (NPO data management /administration / Consolidationfollow-up

After scheduled consolidation: see ( NPO data Management / configuration / systemscheduling to know the schedule).

If necessary, launch manual consolidation for the day datasource you re-declared as well asfor recovery days (depends on the supervision outage due to upgrade). The manualconsolidation can take several hours.

54



55/69

Open AD (Muse applications / optimization / Analysis Desktop), select CELL3G and click ontopology. Check that the NEs corresponding to the datasource are present.

--End--

55



56/69

5.5 Remove Old Instance

Note:This procedure takes 5 min .

ATTENTION


Procedure

Step Action

1. Open a Terminal window asroot.

2. Launch the following commands:

>>cd /alcatel

>>ls

3. Find out the right old instance number: 1 or 2Below it is noted the {old_x} as the old instance and {x} as the new instance.

4. Run the OMC removal scripts:

>>cd /alcatel/omc{old_x}/scripts

>>./evinpkgremoveomc -f /alcatel/omc{old_x}/ install/data/UMTS_instPrd.lst -R/alcatel/omc{old_x}

where {old_x} is the old instance value retrieved before.

At the question, answery.

--End--

56



57/69

6 Reverse ProcedureThis chapter describes the tasks to apply the Reverse Procedure on the NPO server.

Procedure

Step Action

1. If any, install from scrath the NPO machine using the old software version. Refer to [1]9359Network Performance Optimization-Server and Client Installation method(3BK 17429 9087RJZZA).

2. Restore the NPO database backup performed before starting the Software Upgrade procedure.The database recovery procedure to be applied depends on your hardware configuration and onthe solution you have chosen to backup the data. Look at:

Perform a Full Backupfor a non-cluster configuration

Perform a Full Backupfor a cluster configuration

then report to the [2] 9953 MP / NPO Platform Administration Guide(3BK 21315 AAAA PCZZA),

to retrieve the detailed database recovery procedure.

--End--

57



58/69

7 PI02 - Upgrade Server in Cluster ConfigurationThis chapter describes the tasks for MS-OMC Portal/9359-NPO Server Upgrade in cluster

configuration.

58



59/69

7.1 Initial Tasks on ServerThree initial tasks has to be done before performing the software replacement in cluster

configuration:


Check Active Instance

Stop Processes

59



60/69

7.1.1 Perform a Full BackupDifferent solutions are available to backup data before proceeding with the software replacement in

cluster configuration. Using one or the other depends on your hardware configuration. This can be

useful in case you need to restore data.

Keep in mind that:

The network drive is mounted on both cluster nodes (master and slave) but the backup andrecovery operations are performed on the master node only

A backup using V490 / OSB and N240 / DAT72 devices is not possible.


ATTENTION






This solution allows a direct backup of Oracle DB files and user management data for the V490

(Cluster) / Legato device. Legato Networker must be installed on an external SUN server with at least

1TByte of disk space and a gigabit Ethernet interface.




If Legato Networker is not installed , refer to the section7.4.1 - Install Legato NetworkerServerto install and configure it.

If Legato Networker is installed, start from the section7.4.1.6 - Configure Legato Device from

Legato Clientto configure it. Refer to the section7.4.2 - Perform Backup on Legato Clientto perform the backup


Solution 2 - Media Manager (MM) Support Backup

This solution allows a backup of Oracle DB files and user management data for the V490 (Cluster) /

MM device. This solution is based on an open API which operates with an External Manager such as

60



61/69

Veritas NetBackup or HP Data Protector.

Oracle RMAN is integrated with Veritas NetBackup thanks to the supplied Media Manager Library

(MML) API. It allows Oracle RMAN to interwork with Veritas NetBackup , therefore providing a

block-level corruption detection during a backup/restore procedure

In cluster configuration, there is no direct connection between the MM and the Oracle RMAN, so an

intermediate local hard drive storage (network disk storage) is required. The MM backups the data on

the local hard drive, then the Veritas NetBackup or HP Data Protector backups these data from this

local disk.



Refer to the section7.7 - Backup / Restore to/from Disk for Cluster Configurationto perform thebackup

For a Veritas backup of the system, you can also refer to the section7.8.2 - Veritas NetBackupProcedure in case of the Backup for the System

61



62/69

7.1.2 Check Active InstanceNote: This procedure takes2 min .

Procedure

Step Action

1. Open a Terminal window as root.



>>./firefox

If an "Alert" pop-up window appears, click on [OK] .


http:///osm/admin


Log in withosmadmin(default password: alcatel ).

Click on [OK].

Click on process monitoring.

Select Show Details.

Read System version / Instance.

Note down active instance number on a paper.

--End--

62



63/69

7.1.3 Stop ProcessesNote: This procedure takes8 min.

Procedure

Step Action

1. Using the same firefox browser:

Click on "process monitoring". Click on "Stop Cluster".

2. Wait until the processes of NPO part and CoreServices part are stopped (orange leds)

--End--

63



64/69

7.2 Perform Software UpgradeThis chapter describes how to upgrade the server in cluster configuration. The following actions must

be performed in the specified order, for both master and slave machines.

Procedure

Step Action

1. Perform the following asrootuser on the mastermachine: Stop the cluster monitoring

>>cd /alcatel/omc/CLUSTER

>>./activate_monitoring stop

Perform the actions described in the following procedures:

Verify that you have perform theInitial Tasks on Server

Upgrade CD2S

Upgrade CD2P

Upgrade ORACLE

Upgrade CD3S

Insert the CD4 CD-ROM in the master machine drive, then launch the CD4:

>>cd /cdrom/cdrom0

>> ./install.sh

Wait for the software upgrade.

2. Asrooton the slavemachine:

Perform the actions described in the following procedures:

Upgrade CD2S

Upgrade CD2P

Upgrade ORACLE

Upgrade CD3S

Insert the CD4 CD-ROM in the slave machine drive, then launch the CD4:

>>cd /cdrom/cdrom0

>> ./install.sh

64



65/69

Wait for the software upgrade.

3. On themastermachine, perform the actions described in the following procedures:

Upgrade Generic Documentation

Start the Application

Import Dictionaries

Post Upgrade Tasks

Uninstall Client Software


Remove Old Instance

4. On theslavemachine, perform the actions described in the following procedures


Remove Old Instance

5. On themastermachine, start the cluster monitoring process:

>>cd /alcatel/omc/CLUSTER

>> ./activate_monitoring start

--End--

65



66/69

7.3 Post Upgrade TasksIt is recommended to perform a backup at the end of the software upgrade. Several backup / restore

solutions are available. Using one or the other depends on your hardware configuration.

Keep in mind that:

The network drive is mounted on both cluster nodes (master and slave) but the backup andrecovery operations are performed on the master node only

A backup using V490 / OSB and N240 / DAT72 devices is not possible.


ATTENTION






This solution allows a direct backup of Oracle DB files and user management data for the V490

(Cluster) / Legato device. Legato Networker must be installed on an external SUN server with at least

1TByte of disk space and a gigabit Ethernet interface.




If Legato Networker is not installed, refer to the section7.4.1 - Install Legato NetworkerServerto install and configure it.



Solution 2 - Media Manager (MM) Support Backup

This solution allows a backup of Oracle DB files and user management data for the V490 (Cluster) /

Open MM device. This solution is based on an open API which operates with an External Manager

such as Veritas NetBackup or HP Data Protector.

Oracle RMAN is integrated with Veritas NetBackup thanks to the supplied Media Manager Library

(MML) API. It allows Oracle RMAN to interwork with Veritas NetBackup , therefore providing a

block-level corruption detection during a backup/restore procedure

66



67/69

In cluster configuration, there is no direct connection between the MM and the Oracle RMAN, so an

intermediate local hard drive storage (network disk storage) is required. The MM backup the data on

the local hard drive, then the Veritas NetBackup or HP Data Protector backup these data from this

local disk.



Refer to the section7.7 - Backup / Restore to/from Disk for Cluster Configurationto perform thebackup

For a Veritas backup of the system, you can also refer to the section7.8.2 - Veritas NetBackupProcedure in case of the Backup for the System

67



68/69

68



69/69

Wireless Service Provider SolutionsAlcatel-Lucent 9359 Network Performance OptimizerSoftware Replacement (Intra Muse Kernel)

Alcatel-Lucent - Internal - Proprietary - Use pursuant to Company instruction

Copyright 2004-2008 Alcatel-Lucent, All Rights Reserved

UNCONTROLLED COPY: The master of this document is stored on an electronic database and is "write protected"; it may be alteredonly by authorized persons. While copies may be printed, it is not recommended. Viewing of the master electronically ensures accessto the current issue. Any hardcopies taken must be regarded as uncontrolled copies.

ALCATEL-LUCENT CONFIDENTIAL: The information contained in this document is the property of Alcatel-Lucent. Except as

expressly authorized in writing by Alcatel-Lucent, the holder shall keep all information contained herein confidential, shall disclose theinformation only to its employees with a need to know, and shall protect the information from disclosure and dissemination to thirdparties. Except as expressly authorized in writing by Alcatel-Lucent, the holder is granted no rights to use the information containedherein. If you have received this document in error, please notify the sender and destroy it immediately.

Alcatel-Lucent, Alcatel, Lucent Technologies and their respective logos are trademarks and service marks of Alcatel-Lucent, Alcateland Lucent Technologies.

Oracle is a registered trademark of Oracle Corporation and/or its affiliates.

All other trademarks are the property of their owners.

Document number: 3BK-17429-9089-RJZZADocument issue: 01.15/ENDocument status: StandardProduct Release: OAM 5.2

Date: June 2009

Documents

3BK%2D17429%2D9089%2DRJZZA %289359%2DNPO Software Replacement %28Intra Muse Kernel%29 01%2E15 Standard June 2009