3BK-17429-9089-RJZZA (9359-NPO Software Replacement (Intra Muse Kernel) 01.15 Standard June 2009

3BK-17429-9089-RJZZA Wireless Service Provider Solutions
Alcatel-Lucent 9359 Network Performance Optimizer
Software Replacement (Intra Muse Kernel)

3BK-17429-9089-RJZZA 01.15/EN Standard June 2009
Wireless Service Provider Solutions
Alcatel-Lucent 9359 Network Performance Optimizer

Document number: Document issue: Document status: Product release: Date: 3BK-17429-9089-RJZZA 01.15/EN Standard OAM 5.2 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 "write protected"; it may be altered only by authorized persons. While copies may be printed, it is not recommended. Viewing of the master electronically ensures access to 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 the information only to its employees with a need to know, and shall protect the information from disclosure and dissemination to third parties. Except as expressly authorized in writing by Alcatel-Lucent, the holder is granted no rights to use the information contained herein. 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, 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.
Publication history
PUBLICATION HISTORY
SYSTEM RELEASE NPO 5.2 (M2.3) June 2009
Issue 01.15/EN, Standard Resolution of FR: 3BKA85FBR279358
October 2008
Issue 01.14/EN, Standard Update of Schedule section
September 2008
Issue 01.13/EN, Standard Update of Import Dictionaries
September 2008
Issue 01.12/EN, Standard Update of Backup and Restore procedures
September 2008
Issue 01.11/EN, Standard Update of Start NPO Application procedure
September 2008
Issue 01.10/EN, Standard Update after internal review Resolution of FR 3BKA85FBR251522
July 2008
Issue 01.09/EN, Standard Update for server in cluster configuration
June 2008
Issue 01.08/EN, Standard Update of Start NPO Client Application procedure. Improvement of the procedure
Copyright 2004-2008 Alcatel-Lucent
Publication history
June 2008
Issue 01.07/EN, Preliminary Update of the cluster configuration section
April 2008
Issue 01.06/EN, Preliminary Improvement of the procedure
March 2008
Issue 01.05/EN, Draft Improvement of the procedure
February 2008
December 2007
November 2007
Issue 01.02/EN, Draft Add the CD2P and Oracle sections
October 2007
Issue 01.01/EN, Draft Creation of the document
Table of contents
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
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
About this Publication

This 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.
UMTS Access Network Collection Roadmap

For Alcatel-Lucent support team : For more information about the UMTS Access Document Collection, refer to UMTS Access Document Collection - Overview and Update Summary (NN-20500-050) document
New in This Release

The 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
10
Overview
This Overview provides general information about this procedure.
ATTENTION During the whole procedure, consult the appropriate and most recent Release Note according to your configuration, cluster or non-cluster: refer to the [5] External Release Notes for 9359 NPO OAM5.2 & OAM6.0K to apply additional commands if needed.
11
4.1
Before You Start

Before 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 the Upgrade CD1
12
4.2

Initial Status
Before 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.
13
4.3

Final Status
At 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.
14
4.4
Schedule
The following table displays the time required to perform the different tasks. It depends on the CD to install PI No. PI 01 PI 02 PI Titles Upgrade Server in non cluster configuration Upgrade Server in cluster configuration Time from 7h to 11h (Depending on configuration) In Master node: from 7h to 11h In Slave node: around 3h (Depending on configuration)
15
4.5
Impact on Service
None. 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.
16
4.6
Restrictions
None.
17
4.7

Supplies, Tools and Documentation

This section provides information about: Supplies Tools Documentation
18
4.7.1
Supplies
A tape is needed to perform the full backup of NPO database.
19
4.7.2
Tools
The needed tools are listed below. Item Version Case Server
CD1 CD-ROM, DVD-ROM, CD4 The currently installed version on CD-ROM, Generic Documenta- Server machine tion CD-ROM DVD-ROM (CD2S + CD3S) The new version, to be used at upgrade procedure: CD4 CD-ROM CD-ROM for Generic Customer Documentation CD2S_MS_* CD3S_MS_* OMC_INST_*
Server Client
CD4_NPO_M2* Customer generic documentation
Server Server
20
4.7.3
Documentation
The needed applicable documentation is listed below. No. Designation [1] [2] [3] [4] [5] Alcatel-Lucent 9359 Network Performance Optimizer- Server and Client Installation 9953 MP / NPO Platform Administration Guide Alcatel-Lucent 9359 Network Performance Optimizer- Completion Check List Alcatel-Lucent 9359 Network Performance Optimizer- Service Reference Sheet External Release Notes for for 9359 NPO OAM5.2 & OAM6.0K Reference 3BK 17429 9087 RJZZA 3BK 21315 AAAB PCZZA 3BK 17429 9085 RJZZA 3BK 17429 9086 RJZZA UMT/OAM/DJD/ NPO_W23xxxxx file for a non-cluster configuration NPO_W23xxxxxC for a cluster configuration
21
4.8

Conventions
The 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: <<system message Operator input is shown after a double right-oriented arrow, in bold font. The UNIX prompt of the user looks as shown below: For the root user: >>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 -> ...
22
PI01 - Upgrade Server in non Cluster Configuration

This chapter describes the procedures to be followed for the MS-OMC Portal/9359-NPO Server software replacement.
23
5.1
Initial Tasks on Server

Three initial tasks has to be done before performing the software replacement in non cluster configuration: Perform a Full Backup Check Active Instance Stop Processes
24
5.1.1
Perform a Full Backup
Different 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 the Platform Administration Guide document (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 devices
If you choose this solution then: Refer to the section 7.1.4 - Tapes devices to prepare the tape device Perform the backup: If the 1 OSB option has been chosen when generating the server profile at the server installation, then the BACKUP_TYPE parameter has been automatically set to OSB value. In this case, refer to the section 7.3.2 - Perform Backup with OSB If the 2 Other option has been chosen when generating the server profile at the server installation, then the BACKUP_TYPE parameter has been automatically set to NETWORKER value. In this case, you must firstly refer to the section 7.3.1 - Install the OSB Software before referring to the section 7.3.2 - Perform Backup with OSB. Note: With the OSB solution, the Oracle Data Base must always run in ARCHIVELOG mode whichever the schedule of backup is. In another words, the offline backup performed while the Oracle 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.
25
If you choose this solution then: Refer to the section 7.2 - Configure Gb/s Network Interface for Backup Server to configure the IP interface device Refer to the section 7.4 - Legato Backup / Restore If Legato Networker is not installed , refer to the section 7.4.1 - Install Legato Networker Server to install and configure it. If Legato Networker is installed, start from the section 7.4.1.6 - Configure Legato Device from Legato Client to configure it. Refer to the section 7.4.2 - Perform Backup on Legato Client to perform the backup Note: With the Legato solution, the Oracle Data Base must always run in ARCHIVELOG mode whichever the schedule of backup is. In another words, the offline backup performed while the Oracle data Base is in NOARCHIVELOG mode is not supported by Legato backup scripts.
26
5.1.2
Check Active Instance

Note: This procedure takes 2 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://<NPO Server_IP_address>/osm/admin 4. In the prompt window: Log in with osmadmin (default password: alcatel ). Click on [OK]. Click on process monitoring. Read System version / Instance. Note down active instance number on a paper. --End--
27
5.1.3
Stop Processes
Note: This procedure takes 8 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--
28
5.2

Perform Software Upgrade

This 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
29
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.
30
5.2.2
Upgrade CD2S
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 <</dev/lofi/n >>#mount -F hsfs -o ro /dev/lofi/n /alcatel/iso/cd2s n is 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 /
31
>>#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 n is 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|êrror" *.log Note: If errors appear during the software upgrade procedure, please check the [5] External Release Notes for NPO OAMx.x document. --End--
32
5.2.3
Upgrade CD2P
ATTENTION Ensure that the CD2P version has changed before proceeding with the upgrade.
ATTENTION In "Remote " connection, use only ssh, 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 <</dev/lofi/n #mount -F hsfs -o ro /dev/lofi/n /alcatel/iso/cd2p n is the number noted above. 2. Launch the CD2P upgrade: >>cd /alcatel/iso/cd2p >>./install_PATCHES Note: 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: >>#more /etc/A1353RA.signature
33
6. Check the CD2P log file: >>cd /var/omc3/install >>egrep -i " error|êrror" install_PATCHES.log >>egrep -i " error|êrror" install_mng.log Note: If errors appear during the software upgrade procedure, please check the [5] External Release Notes for NPO OAMx.x document. --End--
34
5.2.4
Upgrade ORACLE
Note: This procedure takes 1h00.
ATTENTION Ensure that the Oracle version has changed before proceeding with the upgrade.
ATTENTION In remote connection, use only ssh, 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 Cluster Configuration su - oracle dbshut exit 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
35
Wait until each of the previous commands returns nothing on the screen. 5. As root, 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, as root user: >>cd /alcatel/OMC_INST_M23_Xxxxx >>./gen_profile Note: Do not edit the "Server Profile" file because it is automatically generated and should not be modified. 7. At the question, <<Copy iso images to /alcatel/iso directory? (y/n) Enter >>y 8. The following information is displayed: <<MS_PORTAL hostname [ server.profile ]: <<MS_PORTAL IP address X.Y.Z.T <<MS_PORTAL instance number {1|2} [ 2]: Give the active instance number (running before the migration), see Check Active Instance and press [Enter] <<MS_PORTAL identifier [ 1 ]: press [Enter]. <<TAG_PRODUCT :{ 9953-MP | 9159 | 9359-NPO } [ 9159 ]: type 9359-NPO and press [Enter] <<Give market information {Global/Korean} [Global]: press [Enter] <<WEEKLY_CONSOLIDATION {MONDAY, TUESDAY, WEDNESDAY, THURSDAY, FRIDAY, SUNDAY, SATURDAY} [MONDAY]:press [Enter] <<CI MODE { true | false } [ false ] : press [Enter] <<Enter keystore password(6 to 24 characters): [ secret ]: press [Enter] <<Enter your first and last name: [ Name ]: <<Enter the name of your organizational unit: [ orgUnit ]: <<Enter the name of your organization: [ org ]: <<Enter the name of your City or Locality: [ Paris ]: <<Enter the name of your State or Province: [ France ]: <<Enter the two-letter country code for this unit: [ FR ]: <<Enter the alias [ alias ]: press [Enter] <<Enter key size from 512 to 2048 (multiple of 64): [ 512 ]: press [Enter] <<Which backup/restore solution ? <<Backup Type { 1 OSB | 2 Other | 3 No archive [unsupported - only for testing]} [ 1 ]:
36
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 any other situation. Type your option for backup/restore solution, then press [Enter] 9. The following message is displayed: <</var/tmp/server.profile generated. 10. Edit the new generated profile /var/tmp/server.profile and put on [N] the following iso images: THIRD_PARTIES PATCHES ORACLE_CLUSTER ORACLE_DISK1 ORACLE_BACKUP MS_PORTAL
Check that only ORACLE_PATCH iso image is set to [Y]. 11. Launch the ORACLE Patch upgrade: >>./server_install /var/tmp/server.profile The software to be installed appears and the following message is displayed: <<Do you want to continue? Press >>[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: >>#more /etc/A1353RA.signature 17. Check the Oracle log files:
37
>>cd /alcatel/install/log >>egrep -i " error|êrror" oraclepatch.log >>egrep -i " error|êrror" server_install.log_xxx (xxx is the file date) Note: If errors appear during the software upgrade procedure, please check the [5] External Release Notes for NPO OAMx.x document. --End--
38
5.2.5
Upgrade CD3S
ATTENTION Ensure that the CD3S version has changed before proceeding with the upgrade.
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 <</dev/lofi/n >>#mount -F hsfs -o ro /dev/lofi/n /alcatel/iso/cd3s n is given by the system 2. Launch the installation script: >>cd /alcatel/iso/cd3s >>./gen_install.pl 3. Answer at the following questions as follows: <<MS_PORTAL instance number {1|2} [ 1 ]: Give the new instance number in case the old instance is 2, the new one is 1
in case the old instance is 1, the new one is 2 <<MS_PORTAL identifier [ 1 ]: type the same value as for MS_PORTAL instance number, then press [Enter]
39
<<TAG_PRODUCT :{ 9953-MP | 9159 | 9359-NPO } [ 9159 ]: type 9359-NPO and press [Enter] <<Give market information {Global/Korean} [Global]: press [Enter] <<WEEKLY_CONSOLIDATION {MONDAY, TUESDAY, WEDNESDAY, THURSDAY, FRIDAY, SUNDAY, SATURDAY} [MONDAY]:press [Enter] <<Current CI MODE { true | false } [ false ]:press [Enter] <<Do you perform a software upgrade? {Y/N} [ Y ]: press [Enter] <<MS_PORTAL old instance number {1|2} [ 1 ]: Give the old instance number in case the old instance is 2, the new one is 1 in case the old instance is 1, the new one is 2
Press [ Enter ] . <<Which backup/restore solution ? <<Backup Type { 1 OSB | 2 Other | 3 No archive [unsupported - only for testing]} [ 1 ]: If no SDLT device is connected, the OSB option must not be selected. Note: The option number 3 -No archive is only for testing. You are not allowed to use it in any other situation. Type your option for backup/restore solution, then press [Enter] Enter keystore password (6 to 24 characters): [ secret ]: press [Enter] Enter your first and last name: [ Name ]: Enter the name of your organizational unit: [ orgUnit ]: Enter the name of your organization: [ org ]: Enter the name of your City or Locality: [ Paris ]: Enter the name of your State or Province: [ France ]: Enter the two-letter country code for this unit: [ FR ]: Enter the alias [ alias ]: press [Enter] Enter key size from 512 to 2048 (multiple of 64): [ 512 ]: press [Enter] 4. Launch the installation script: >>./install 5. Wait for the end of install script. 6. Verify that the signature of CD3S version is updated: >>#more /etc/A1353RA.signature 7. Check the CD3S log file: >>cd /alcatel/omc{x}/var/sadm/install/logs >>egrep -i " error|êrror" *.log (where {x} is the new instance number 2 (or 1)).
40
Note: If errors appear during the software upgrade procedure, please check the [5] External Release Notes for NPO OAMx.x document. 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 n is given by the system 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--
41
5.2.6
Upgrade CD4
ATTENTION Ensure that the CD4 version has changed before proceeding with the upgrade.
Procedure
Step Action
1. Insert the new CD4 CD-ROM in the drive. 2. Launch the CD4 installation >>cd /cdrom/cdrom0 >>./install.sh The following message appears << Which market do you want to install, press key for your choice: <<(1 for Global; 2 for Korean; others for quit) Please, answer 1 (except if the customer is Korean) and press [Enter] Note: Korean market is only for Korean while Global market is for all countries except Korean (type 1 for Global and 2 for Korean. 3. Verify that the signature of CD4 version is updated: >>#more /etc/A1353RA.signature 4. Check the CD4 log file: >>cd /var/sadm/install/logs >>egrep -i " error|êrror" *.log Note: If errors appear during the software procedure upgrade, please check the [5] External
42
Release Notes for NPO OAMx.x document. Note: If the problems persists, apply the Reverse Procedure --End--
43
5.2.7
Upgrade Generic Documentation

ATTENTION Ensure that the Documentation version has changed before proceeding with the upgrade.
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 error messages, do not take into account. >>./remove_muse_doc <<Do you want to remove the documentation (y/n/q)?: y 4. Start the installation: >>./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
44
--End--
45
5.2.8
Start the Application

Note: This procedure takes 10 min. on the Server.
Procedure
Step Action
1. Launch the Firefox browser from the command line: >>cd /usr/local/firefox >>./firefox If an "Alert" pop-up window appears, click on [ OK ] 2. Open the following URL address: http://<Server_IP_Address >/osm/adm The <Server_IP_address> can 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
3. In the prompt window: 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.
46
6. If there are still red leds, please call Alcatel-Lucent GPS for support. 7. Close the Firefox browser. --End--
47
5.2.9
Import Dictionaries
Note: This procedure takes from 2h45 to 4h45 on the Server. (Depending on configuration)
ATTENTION Ensure that the Dictionaries version has changed before proceeding with the upgrade.
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 a migration 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 as root Launch the Import Dictionaries: >>cd /cdrom/cdrom0 <<Are you ready for CD4 UMTS installation? >>./umtsfullinstall.sh Answer "y" and then press Enter
48
Note: The script "umtsfullinstall.sh" does not import extended indicators 3. Checks At the end of all imports, the traces must be checked for errors before continuing. If some errors appear, check the [5] External Release Notes for NPO OAMx.x document. For Parameters: >>cd /alcatel/temp/data/trace/ >>grep -i " error" RTP_Offline_<hostname>_0.traces For Counters/Indicators: >>cd /alcatel/muse/data/trace >>grep -i " error" OT_<hostname>_0.traces 4. Remove the CD4 from the drive >>cd / >>eject --End--
49
5.3
Post Upgrade Tasks

It 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. Note: This procedure takes at least 1h 30 on the server.
ATTENTION All chapters indicated in this section refer to procedures described in the Platform Administration Guide document (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 devices
If you choose this solution then: Refer to the section 7.1.4 - Tapes devices to prepare the tape device Perform the backup: If the 1 OSB option has been chosen when generating the server profile at the server upgrade, then the BACKUP_TYPE parameter has been automatically set to OSB value. In this case, refer to the section 7.3.2 - Perform Backup with OSB If the 2 Other option has been chosen when generating the server profile at the server upgrade, then the BACKUP_TYPE parameter has been automatically set to NETWORKER value. In this case, you must firstly refer to the section 7.3.1 - Install the OSB Software, then refer to the section 7.3.2 - Perform Backup with OSB. Note: With the OSB solution, the Oracle Data Base must always run in ARCHIVELOG mode whichever the schedule of backup is. In another words, the offline backup performed while the Oracle 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. If you choose this solution then:
50
Refer to the section 7.2 - Configure Gb/s Network Interface for Backup Server to configure the IP interface device Refer to the section 7.4 - Legato Backup / Restore If Legato Networker is not installed, refer to the section 7.4.1 - Install Legato Networker Server to install and configure it. If Legato Networker is installed, start from the section 7.4.1.6 - Configure Legato Device from Legato Client to configure it. Refer to the section 7.4.2 - Perform Backup on Legato Client to perform the backup Note: With the Legato solution, the Oracle Data Base must always run in ARCHIVELOG mode whichever the schedule of backup is. In another words, the offline backup performed while the Oracle data Base is in NOARCHIVELOG mode is not supported by Legato backup scripts.
51
5.4

Upgrade NPO Client Application

This procedure describes how to upgrade the NPO application on the Client PC. You must: Uninstall Client Software Start NPO Client Application
52
5.4.1
Uninstall Client Software

Note: This procedure takes 20 min on 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. Select Start -> Run, Enter cmd 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 the PC, and not the new one. 5. Edit client.Uninstall.profile Enter N for JRE (Java) Enter Y 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
53
Note: OMC_INST_y and OMC_INST_x corresponds to the software currently installed on the PC, and not the new one. 8. Launch Uninstall.pl and wait for the end of the uninstallation Note: If the RegSrv32 pop-up appears, click on [OK]. The Client PC automatically reboots 9. Logon as administrator on the Client PC 10. Select Start -> 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:\ILOG directory c:\log_Uninstall directory c:\omc directory c:\omc_install directory c:\PC_install directory c:\Perl directory
14. Check that c/\cygwin directory does not exist anymore. If it still exists, rename it. 15. Reboot the PC. --End--
54
5.4.2
Start NPO Client Application

Note: This procedure takes 5 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 to start -> setting -> control panel -> Add/remove program 2. Ensure that the "J2SE Developpement KIT 5.0 update 14" is available on the machine else you must install it such as indicated below: Enter the following IP address in a web browser: http://<NPO Server_IP_address> 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 new instance 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 / Consolidation follow-up After scheduled consolidation: see ( NPO data Management / configuration / system scheduling to know the schedule). If necessary, launch manual consolidation for the day datasource you re-declared as well as for recovery days (depends on the supervision outage due to upgrade). The manual consolidation can take several hours.
55
Open AD (Muse applications / optimization / Analysis Desktop), select CELL3G and click on topology. Check that the NEs corresponding to the datasource are present. --End--
56
5.5
Remove Old Instance

Procedure
Step Action
1. Open a Terminal window as root. 2. Launch the following commands: >>cd /alcatel >>ls 3. Find out the right old instance number: 1 or 2 Below 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, answer y. --End--
57
Reverse Procedure
This 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] 9359 Network Performance Optimization-Server and Client Installation method (3BK 17429 9087 RJZZA). 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 on the solution you have chosen to backup the data. Look at: Perform a Full Backup for a non-cluster configuration Perform a Full Backup for 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--
58
PI02 - Upgrade Server in Cluster Configuration

This chapter describes the tasks for MS-OMC Portal/9359-NPO Server Upgrade in cluster configuration.
59
7.1
Initial Tasks on Server

Three initial tasks has to be done before performing the software replacement in cluster configuration: Perform a Full Backup Check Active Instance Stop Processes
60
7.1.1
Perform a Full Backup
Different 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 and recovery operations are performed on the master node only A backup using V490 / OSB and N240 / DAT72 devices is not possible. Note: This procedure takes at least 1h 30 on the server.
Solution 1 - Legato Centralized Backup 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 you choose this solution then: Refer to the section 7.2 - Configure Gb/s Network Interface for Backup Server to configure the IP interface device Refer to the section 7.4 - Legato Backup / Restore If Legato Networker is not installed , refer to the section 7.4.1 - Install Legato Networker Server to install and configure it. If Legato Networker is installed, start from the section 7.4.1.6 - Configure Legato Device from Legato Client to configure it. Refer to the section 7.4.2 - Perform Backup on Legato Client to perform the backup Note: With the Legato solution, the Oracle Data Base must always run in ARCHIVELOG mode whichever the schedule of backup is. In another words, the offline backup performed while the Oracle data Base is in NOARCHIVELOG mode is not supported by Legato backup scripts. 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
61
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. If you choose this solution then: Refer to the section 7.2 - Configure Gb/s Network Interface for Backup Server to configure the IP interface device Refer to the section 7.7 - Backup / Restore to/from Disk for Cluster Configuration to perform the backup For a Veritas backup of the system, you can also refer to the section 7.8.2 - Veritas NetBackup Procedure in case of the Backup for the System
62
7.1.2
Check Active Instance

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://<NPO Server_IP_address>/osm/admin 4. In the prompt window: Log in with osmadmin (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--
63
7.1.3
Stop Processes
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--
64
7.2
Perform Software Upgrade

This 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 as root user on the master machine: Stop the cluster monitoring >>cd /alcatel/omc<instance_number>/CLUSTER >>./activate_monitoring stop Perform the actions described in the following procedures: Verify that you have perform the Initial 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. As root on the slave machine: 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
65
Wait for the software upgrade. 3. On the master machine, perform the actions described in the following procedures: Upgrade Generic Documentation Start the Application Import Dictionaries Post Upgrade Tasks Uninstall Client Software Start NPO Client Application Remove Old Instance
4. On the slave machine, perform the actions described in the following procedures Start NPO Client Application Remove Old Instance
5. On the master machine, start the cluster monitoring process: >>cd /alcatel/omc<instance_number>/CLUSTER >> ./activate_monitoring start --End--
66
7.3
Post Upgrade Tasks

It 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 and recovery operations are performed on the master node only A backup using V490 / OSB and N240 / DAT72 devices is not possible. Note: This procedure takes at least 1h 30 on the server.
Solution 1 - Legato Centralized Backup 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 you choose this solution then: Refer to the section 7.2 - Configure Gb/s Network Interface for Backup Server to configure the IP interface device Refer to the section 7.4 - Legato Backup / Restore If Legato Networker is not installed, refer to the section 7.4.1 - Install Legato Networker Server to install and configure it. If Legato Networker is installed, start from the section 7.4.1.6 - Configure Legato Device from Legato Client to configure it. Refer to the section 7.4.2 - Perform Backup on Legato Client to 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) / 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
67
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. If you choose this solution then: Refer to the section 7.2 - Configure Gb/s Network Interface for Backup Server to configure the IP interface device Refer to the section 7.7 - Backup / Restore to/from Disk for Cluster Configuration to perform the backup For a Veritas backup of the system, you can also refer to the section 7.8.2 - Veritas NetBackup Procedure in case of the Backup for the System
68
Wireless Service Provider Solutions Alcatel-Lucent 9359 Network Performance Optimizer Software 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 altered only by authorized persons. While copies may be printed, it is not recommended. Viewing of the master electronically ensures access to 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 the information only to its employees with a need to know, and shall protect the information from disclosure and dissemination to third parties. Except as expressly authorized in writing by Alcatel-Lucent, the holder is granted no rights to use the information contained herein. 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, 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. Document number: Document issue: Document status: Product Release: Date: 3BK-17429-9089-RJZZA 01.15/EN Standard OAM 5.2 June 2009

3BK-17429-9089-RJZZA (9359-NPO Software Replacement (Intra Muse Kernel) 01.15 Standard June 2009

Загружено:

Сведения о документе

Исходное описание:

Оригинальное название

Авторское право

Доступные форматы

Поделиться этим документом

Поделиться или встроить документ

Параметры публикации

Этот документ был вам полезен?

Это неприемлемый материал?

Авторское право:

Доступные форматы

3BK-17429-9089-RJZZA (9359-NPO Software Replacement (Intra Muse Kernel) 01.15 Standard June 2009

Загружено:

Авторское право:

Доступные форматы

3BK-17429-9089-RJZZA Wireless Service Provider Solutions

Alcatel-Lucent 9359 Network Performance Optimizer

Software Replacement (Intra Muse Kernel)

Wireless Service Provider Solutions

Alcatel-Lucent 9359 Network Performance Optimizer

Software Replacement (Intra Muse Kernel)

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

Copyright 2004-2008 Alcatel-Lucent

Software Replacement (Intra Muse Kernel)

3BK-17429-9089-RJZZA 01.15/EN Standard June 2009

Copyright 2004-2008 Alcatel-Lucent

Copyright 2004-2008 Alcatel-Lucent

Software Replacement (Intra Muse Kernel)

3BK-17429-9089-RJZZA 01.15/EN Standard June 2009

Copyright 2004-2008 Alcatel-Lucent

About this Publication

Copyright 2004-2008 Alcatel-Lucent

Software Replacement (Intra Muse Kernel)

UMTS Access Network Collection Roadmap

3BK-17429-9089-RJZZA 01.15/EN Standard June 2009

Copyright 2004-2008 Alcatel-Lucent

New in This Release

Copyright 2004-2008 Alcatel-Lucent

Software Replacement (Intra Muse Kernel)

3BK-17429-9089-RJZZA 01.15/EN Standard June 2009

Copyright 2004-2008 Alcatel-Lucent

Before You Start

Copyright 2004-2008 Alcatel-Lucent

Software Replacement (Intra Muse Kernel)

3BK-17429-9089-RJZZA 01.15/EN Standard June 2009

Copyright 2004-2008 Alcatel-Lucent

Copyright 2004-2008 Alcatel-Lucent

Software Replacement (Intra Muse Kernel)

3BK-17429-9089-RJZZA 01.15/EN Standard June 2009

Copyright 2004-2008 Alcatel-Lucent

Copyright 2004-2008 Alcatel-Lucent

Software Replacement (Intra Muse Kernel)

3BK-17429-9089-RJZZA 01.15/EN Standard June 2009

Copyright 2004-2008 Alcatel-Lucent

Supplies, Tools and Documentation

Copyright 2004-2008 Alcatel-Lucent

Software Replacement (Intra Muse Kernel)

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

3BK-17429-9089-RJZZA 01.15/EN Standard June 2009

Copyright 2004-2008 Alcatel-Lucent

CD4_NPO_M2* Customer generic documentation

Copyright 2004-2008 Alcatel-Lucent

Software Replacement (Intra Muse Kernel)

3BK-17429-9089-RJZZA 01.15/EN Standard June 2009

Copyright 2004-2008 Alcatel-Lucent

Copyright 2004-2008 Alcatel-Lucent

Software Replacement (Intra Muse Kernel)

PI01 - Upgrade Server in non Cluster Configuration

3BK-17429-9089-RJZZA 01.15/EN Standard June 2009

Copyright 2004-2008 Alcatel-Lucent

Initial Tasks on Server

Copyright 2004-2008 Alcatel-Lucent

Software Replacement (Intra Muse Kernel)

Perform a Full Backup

3BK-17429-9089-RJZZA 01.15/EN Standard June 2009

Copyright 2004-2008 Alcatel-Lucent

Copyright 2004-2008 Alcatel-Lucent