mmsc2.0 cluster to mmsc2.1 cluster with sg upgrade manual

8/9/2019 MMSC2.0 Cluster to MMSC2.1 Cluster With SG Upgrade Manual

http://slidepdf.com/reader/full/mmsc20-cluster-to-mmsc21-cluster-with-sg-upgrade-manual 1/58

Nokia MMS Center 2.1

Installation Guides

DN02243143 © Nokia Corporation 1 (58)

Issue 1a en Nokia Proprietary and Confidential

MMSC 2.0 Cluster withServiceGuard to MMSC 2.1Cluster with ServiceGuardUpgrade Manual



MMSC 2.0 Cluster with ServiceGuard to MMSC 2.1 Cluster with ServiceGuard Upgrade Manual

2 (58) © Nokia Corporation DN02243143

Nokia Proprietary and Confidential Issue 1aen

The information in this documentation is subject to change without notice and describes onlythe product defined in the introduction of this documentation. This documentation is intendedfor the use of Nokia's customers only for the purposes of the agreement under which thedocumentation is submitted, and no part of it may be reproduced or transmitted in any form ormeans without the prior written permission of Nokia. The documentation has been prepared tobe used by professional and properly trained personnel, and the customer assumes fullresponsibility when using it. Nokia welcomes customer comments as part of the process ofcontinuous development and improvement of the documentation.

The information or statements given in this documentation concerning the suitability, capacity,or performance of the mentioned hardware or software products cannot be considered bindingbut shall be defined in the agreement made between Nokia and the customer. However, Nokiahas made all reasonable efforts to ensure that the instructions contained in the documentationare adequate and free of material errors and omissions. Nokia will, if necessary, explain issueswhich may not be covered by the documentation.

Nokia's liability for any errors in the documentation is limited to the documentary correction oferrors. NOKIA WILL NOT BE RESPONSIBLE IN ANY EVENT FOR ERRORS IN THISDOCUMENTATION OR FOR ANY DAMAGES, INCIDENTAL OR CONSEQUENTIAL(INCLUDING MONETARY LOSSES), that might arise from the use of this documentation orthe information in it.

This documentation and the product it describes are considered protected by copyrightaccording to the applicable laws.

NOKIA logo is a registered trademark of Nokia Corporation.

Other product names mentioned in this documentation may be trademarks of their respectivecompanies, and they are mentioned for identification purposes only.

Copyright © Nokia Corporation 2003. All rights reserved.





Contents

Contents 3

List of tables 5

1 About this document 91.1 Audience 91.2 Typographical conventions 9

2 Summary of the upgrade 11

3 Preparing for the upgrade 133.1 Making backup tapes from the MMS Center 13

4 Upgrade before downtime 154.1 Installing the MMS Center build 154.2 Checking the system 154.3 Disabling extra services 164.4 Updating HP Command View sdm software version if Virtual Array disk

array is used 174.5 Unloading event logs and performance data to tape 184.6 Configuring the new MMS Center builds 20

5 Upgrade during downtime 235.1 Shutting down the MMS Center 235.2 Installing the HP-UX patches and applying MC2.1 tuned kernel parameter

set in front-ends 24

5.3 Switching soft links 255.4 Upgrading database from MMS Center 2.0 to MMS Center 2.1 255.5 Installing additional libraries for the MMS Center 325.6 Adding cron entries for the sc user 325.7 Upgrading log writer to MMS Center 2.1 335.8 Deploying the GUI 355.9 Connecting to the MMS Center GUI and starting the MMS Center 36

6 Upgrade after downtime 396.1 Copying required Java classes and the GUI configuration file to the

database servers 396.2 Configuring configuration tool (COT) for servers in networked MMS

Center 406.3 Making backup tapes of the MMS Center 426.4 Loading event logs and performance data from tape 43

7 Accepting the installation 45

8 Upgrading Open View Operations interface to MMS Center 2.1 47

9 Downgrading from MMS Center 2.1 to MMS Center 2.0 49






Appendix A. Installing the HP-UX patches 53

Appendix B. Applying MC2.1 tuned kernel parameter set 55

References 57





List of tables

Table 1. History 7

Table 2. Typographical conventions 10

Table 3. DDS DAT-tape sizes 14

Table 4. DDS tape sizes 43

Table 5. Patches in MC_21_patches bundle 53





Summary of changes

Changes between documentsare cumulative. Therefore, the latest document issuecontains all changes made to previous issues.

Table 1. History

Date Issue Summary of changes

November 2002 1-0 en First issue.

December 2002 1a-0 en Minor corrections after pilot phase.



About this document



1 About this document

This document includes instructions for upgrading Nokia Multimedia MessagingService Center (MMS Center) 2.0 to Nokia MMS Center 2.1.

1.1 Audience

This document is intended for installation personnel performing the upgradeprocedure.

1.2 Typographical conventions

Several types of typographical conventions have been used in this manual todescribe different actions and restrictions. They are described in Table 2.






Table 2. Typographical conventions

Convention Description

courier Courier is used to denote:

• commands and scripts

For example:

> onstat -|

• paths and file names

For example:

/etc/opt/nokia/mmsc/script

• sections, parameters and values in configuration files

For example:

You can specify the number of rules at the

NUMBER_OF_RULES parameter.

• names of processes

For example:

gwrmanmx

• names of configuration files

For example:

gwrmanmx.cf

bold Bold is used to denote:

• buttons in the user interface

For example:

Click Ok .

sc%> sc%> is used to denote that, when performing a task from

the command line, the user must be an sc user.

For example:

sc%> cd $SC_BINPATH

# # is used to denote that, when performing a task from the

command line, the user must be a root user.

For example:

# ./start

> > is used to denote that, when performing a task from thecommand line, the user must be an informix user.

For example:

> onmode -m

<variable_data> Variable data is written between the < and > characters.

For example:

<process_name>



Summary of the upgrade



2 Summary of the upgrade

The following lists the order in which the upgrade should be executed.

Summary of the upgrade order

1. Installing the MMS Center build to each node.

2. Unloading event logs and performande data from database to tape.

3. Configuring the new MMS Center builds in front-ends.

4. Shutting down the MMS Center. Downtime starts.

5. Installing the needed patch depot to each node.

6. Upgrading the database.

a. Switching links.

b. Upgrading the database structure.

c. Unloading the configuration data from the database.

d. Recreating the database.

e. Loading the configuration data to the database.

7. Installing Visibroker libraries to MMS Center 2.1 nodes.

8. Starting the MMS Center. Downtime ends.

9. Testing that the MMS Center works. Full downtime ends.

10. Loading event logs and performance data from the tape to the database.



Preparing for the upgrade



Note

3 Preparing for the upgrade

Follow the step below to prepare for the upgrade.

To prepare for the upgrade

It is recommended that the following change be implemented, as it shortens theservice break during the upgrade.

• Gradually lower the expiration date to 24 (hours) before the upgrade, sothat there are no multimedia messages older than 24 hours in the databaseat the time of the upgrade. This can be done by editing the parameterMM_EXPIRY_TIME in the [EXPIRATION] section of the$SC_CONFPATH/xkrmanmx.cf configuration file and reinitialising thekernel through the GUI. This should be done to both MMS Center front-end nodes.

For instructions on how to reinitialise the kernel, see Section Starting,stopping and reinitialising applications and processes through the GUI inthe Operating MMS Center document.

3.1 Making backup tapes from the MMS Center

Before continuing the upgrade, make an Ignite tape so that you can fall back onthe original state if, for some reason, the upgrade fails. See Table 3 for DDS tapecapacities.

Several tapes may be needed when backing up the MMS Center cluster. Tapes areneeded also later on in the procedure.






To make an Ignite backup tape of the system disk

Make an Ignite backup tape of each server in the cluster.

• Insert an empty tape to the tape drive and enter the following command:

# make_tape_recovery -x inc_entire=vg00 -x inc_entire=vg01 -I -A -t "Pre-upgraderecovery tape"

This creates a backup of the system disk.

To take a backup of the database structures in the database

1. Log in as root user to active the database node.

2. Change the /dev/IDS_tape link to point to an actual tape device byentering the following commands as root user:

# rm /dev/IDS_tape

# ln -s /dev/rmt/0m /dev/IDS_tape

3. Insert a new tape to the drive and make a level 0 backup of the database byentering the following command as informix user:

> ontape -s -L 0

4. Remove the tape and change the /dev/IDS_tape link to point back to/dev/null by entering the following commands as root user:

# rm /dev/IDS_tape

# ln -s /dev/null /dev/IDS_tape

Table 3. DDS DAT-tape sizes

DDS tape version Capacity

uncompressed

Capacity compressed

DDS3 12GB 24 GB

DDS4 20GB 40 GB



Upgrade before downtime



4 Upgrade before downtime

4.1 Installing the MMS Center build

The MMS Center software is installed using the swinstall tool from the delivered

media (CD-ROM).

Install MMS Center 2.1 software to each server in the cluster. Follow the stepsbelow to load the MMS Center from the CD-ROM.

To load the MMS Center from the CD-ROM

1. Insert the MMS Center installation CD-ROM into the CD-ROM drive.

2. Enter the following commands:

# mount /dev/dsk/<cdrom_device> /SD_CDROM

(For example: <cdrom_device> = c1t2d0, where 1 and 2 represent thechannel and the target that may vary according to the installation.)

# swinstall -s /SD_CDROM/M2.<MMSC_build>.depot

3. Select the depot file.

4. Select Actions > Mark for install.

5. Select Actions > Install (analysis).

4.2 Checking the system

Before the upgrade, run a test script which checks the system basics, anddetermine whether the upgrade is possible. Run this script in every node.






Note

Caution

To run the check scripts

1. Log in as root user.

2. Copy the xcf_check_MC2.0–2.1_upgrade_mx.sh from the/etc/opt/nokia/new_mmsc/tools directory by entering thefollowing commands:

# mkdir /tmp/mc_21_upgrade

# chmod 777 /tmp/mc_21_upgrade

# cp /etc/opt/nokia/new_mmsc/tools/xcf_check_MC2.0-

MC2.1_upgrade_mx.sh /tmp/mc_21_upgrade

# chmod u+x /tmp/mc_21_upgrade/xcf_check_MC2.0-MC2.1_upgrade_mx.sh

3. Run the script by entering the following commands:

# cd /tmp/mc_21_upgrade

# ./xcf_check_MC2.0–2.1_upgrade_mx.sh

The script checks the system and marks every check status with an [ OK ] or[FAIL] tag. If any of the tests fail, check the upgrade_output.txt file for

errors. Fix the errors, and run the script again.

If you are unable to fix the errors, contact Nokia Technical Support. Do notproceed with the upgrade before the errors are fixed.

Make sure that all checks in every server are passed with an [ OK ] tag beforecontinuing.

4.3 Disabling extra services

Disable the extra services by running the following script in every server in thecluster:






# /etc/opt/nokia/new_mmsc/tools/xcf_modserv_mx.sh

This script comments out the following lines in the /etc/inetd.conf file.

#daytime stream tcp nowait root internal #daytime dgram udp nowait root internal #time stream tcp nowait root internal #time dgram udp nowait root internal #echo stream tcp nowait root internal #echo dgram udp nowait root internal #discard stream tcp nowait root internal #discard dgram udp nowait root internal #chargen stream tcp nowait root internal #chargen dgram udp nowait root internal #rpc xti tcp swait root /usr/dt/bin/rpc.ttdbserver 100083 1/usr/dt/bin/rpc.ttdbserver #rpc dgram udp wait root /usr/dt/bin/rpc.cmsd 100068 2-5rpc.cmsd

The script also modifies the following services if they for some reason are enabled

or disabled in the MMS Center 2.0 installation:

• Disables Apache web server from starting during the boot process

• Disables SNMP mib2 subagent from starting during the boot process

• Disables the dead gateway detection feature

• Enables online diagnostics

4.4 Updating HP Command View sdm software version

if Virtual Array disk array is used

HP Command View sdm software version needs to be updated to version 1.05 forMMS Center 2.1. This procedure must be done in both database nodes if VirtualArray disk array is used.

To remove old version of HP Command View sdm software

1. Enter the following command:

# swremove

2. Select the depot file CMDVIEWSDM.

3. Select Actions > Remove.

4. Select OK.






5. Remove the remaining San Manager directory /var/opt/sanmgr byentering the following commands:

# cd /var/opt

# rm -R sanmgr

To load version of HP Command View sdm software

1. Insert the installation CD-ROM into the CD-ROM drive.



# swinstall -s /SD_CDROM/cvsdm_11_11_v10500.depot




6. Search for Virtual Array by entering the following command:

# armdsp -i

The output should be as follows:

Product ID: HP-AxxxxA Device Type: Virtual Disk Array Alias: mmsc_1 World Wide Name: <Unique numeric string> Unique ID: <Unique string> Serial Number: <Unique string> Management Path: <hostname>:/dev/rscsi/c7t12d0

4.5 Unloading event logs and performance data to tape

Event logs and performance data must be downloaded to the tape for later use.Follow the steps below to unload event logs and performance data.






Caution

Before unloading the data, check that tape device is /dev/rmt/0mn. If not,

change the value of the TapeDeviceName parameter to /dev/rmt/0mn in/etc/opt/nokia/new_mmsc/tools/xdb_upgrade_archive_tables_mx.sh and/etc/opt/nokia/new_mmsc/tools/xdb_upgrade_load_logs_mx.shfiles.

Make sure you use a NO-REWIND device.

The /sc_var/backup directory must be created, because several scripts use thisdirectory.

Follow the step below to create the /sc_var/backup directory.

To create /sc_var/backup directory

• Log in as root to the database primary node and enter the followingcommands to create the /sc_var/backup directory for later use:

# mkdir /sc_var/backup

# chmod 777 /sc_var/backup

To unload event logs and performance data to tape

1. Insert an empty tape to the database primary node tape drive.

2. Log in as sc user and enter the following commands to unload event logsand performance data to the tape:

sc>% cd /etc/opt/nokia/new_mmsc/tools

sc>% ./xdb_upgrade_archive_tables_mx.sh






Note

Note

Depending on the amount of data in the database, you may be prompted tochange the tape.

Depending on the amount of data in the database and tape capacity, you may needup to three DDS-4 40 GB tapes or up to six DDS-3 24 GB tapes.

It is recommended that you proceed to the next chapter as unloading might takesome time.

4.6 Configuring the new MMS Center builds

Configure MMS Center builds only in front-end nodes. You do not need toconfigure MMS Center software for the database servers at this stage.

The MMS Center software is installed to the /opt/nokia/new_mmsc ,/etc/opt/nokia/new_mmsc and /var/opt/nokia/new_mmsc directories.

Follow the steps below to configure the new MMS Center build.

To configure the new MMS Center build

1. Check which configuration files have been modified in the running MMSCenter 2.0 system. Enter the following commands to compare the currentconfiguration in /etc/opt/nokia/mmsc with the factory defaults in/opt/nokia/mmsc:

sc>% mkdir /tmp/upgrade

sc>% cd /tmp/upgrade

sc>% cp/etc/opt/nokia/new_mmsc/tools/xcf_diff_mmsc_configs_mx.sh .

sc>% chmod u+x xcf_diff_mmsc_configs_mx.sh

sc>% ./xcf_diff_mmsc_configs_mx.sh



Upgrade during downtime



Note

5 Upgrade during downtime

Follow the steps below to upgrade the database to MMS Center 2.1.

Downtime begins during the next procedure (when the MMS Center is shutdown), and ends when all the configurations in this chapter have been made andthe MMS Center is restarted.

5.1 Shutting down the MMS Center

Follow the steps in the tasks below to shut down the MMS Center.

To connect to the MMS Center GUI

• Open the MMS Center graphical user interface (GUI) by entering thefollowing to your browser:

http(s)://<mmsc.operator.com>/mmsc/servlet/Home

To stop the MMS Center

Shut down every MMS Center front-end individually by following the stepsbelow:

1. In the GUI main menu, select Component Mgmt.

2. Check MMSC and click Stop.






Note

The MMS Center status should change to Not Running and the statuses forthe other processes should change to Not Known after the screen refreshes(this may take a while). Downtime begins at this point.

3. Start the event logger by entering the following command as sc user:

sc>% $SC_BINPATH/xlwmanmx

4. Log in as sc user and monitor event logger queues by entering thefollowing command:

sc>% $SC_SCRIPTPATH/ymcLsMMSCQueues 150 150

Wait until all the queues are empty. Then stop the event logger by pressingCTRL-C in the window where you started the event logger.

5. Remove MMS Center message queues by entering the following

command:

sc>% $SC_SCRIPTPATH/ymcRmMMSCQueues 1 10000

5.2 Installing the HP-UX patches and applying MC2.1tuned kernel parameter set in front-ends

Follow the steps below to install the HP-UX patches and to apply the MC2.1tuned kernel parameter set in the front-ends.

To install HP-UX patches and to apply MC2.1 tuned kernel parameterset in front-ends

1. For each front-end server, apply the instructions in Appendix A.

2. For each front-end server, apply the instructions in Appendix B.

While the front-end servers are rebooting, you can proceed with Section 5.4Upgrading database from MMS Center 2.0 to MMS Center 2.1 below.






Note

5.3 Switching soft links

Follow the steps below to switch the new_mmsc links to mmsc.

To switch the new_mmsc links to mmsc

• Enter the following command to switch the mmsc links to point to theMMS Center 2.1 directories, and the new_mmsc links to point to the MMSCenter 2.0 directories. Switch links in every server in the cluster.

# cd /

#/etc/opt/nokia/new_mmsc/tools/xcf_link_switcher_mx.sh

5.4 Upgrading database from MMS Center 2.0 to MMSCenter 2.1

If you use any type of Virtual Array, follow the steps below to upgrade thedatabase from MMS Center 2.0 to MMS Center 2.1.

To upgrade the database from MMS Center 2.0 to MMS Center 2.1 if any type of Virtual Array is used

1. Log in to the database primary node and enter the following commands assc user to ugrade the database from MMS Center 2.0 to MMS Center 2.1:

sc>% cd /etc/opt/nokia/mmsc/tools

sc>% ./xdb_upgrade_mc2_to_mc2_1_mx.sh 2>&1 | teexdb_upgrade_mc2_to_mc2_1_mx.log

sc>% ./xdb_upgrade_unload_tables_mx.sh 2>&1 | teexdb_upgrade_unload_tables_mx.log

The duration of the database upgrade depends on the amount of data in thedatabase.






2. Log in as root to the primary database node, and shut down IBM Informixdatabase server by entering the following command:

# cmhaltcl -f

3. Apply the instructions in Appendix A to both database nodes.

4. Apply the instructions in Appendix B to both database nodes.

5. Log in as root to the primary database node and copy the/opt/informix/IDS2000/etc/sqlhosts file to/opt/informix/IDS2000/etc/sqlhosts.mc2.1.SG by entering thefollowing command:

# cp –p /opt/informix/IDS2000/etc/sqlhosts/opt/informix/IDS2000/etc/sqlhosts.mc2.1.SG

6. Edit the /opt/informix/IDS2000/etc/sqlhosts file by replacing<SG packet ip> with <dbprimary node ip>.

7. Export VG02 by entering the following commands:

# cd /

# vgchange —c n vg02

# vgexport /dev/vg02

8. Set up VG02 and lvols by entering the following command:

# /etc/opt/nokia/mmsc/tools/xcf_setup_lvols_va_mx.sh

9. Remove old linking inthe primarydatabase node by entering the followingcommand:

# rm /dev/*dbs_dat*

10. Set up database linking by entering the following command:

# /etc/opt/nokia/mmsc/tools/xcf_dblinks_mx.sh

11. Log in as user informix and copy the ONCONFIG.SC file to/opt/informix/IDS2000/etc/ by entering the following command:(X stands for the number of CPUs in the database server.)

> cp/etc/opt/nokia/mmsc/tools/xcf_ONCONFIG.SC.cluster_Xcpu/opt/informix/IDS2000/etc/ONCONFIG.SC

12. Set up IBM Informix database by entering the following commands:






> cd /etc/opt/nokia/mmsc/tools/

> ./xcf_setinformix_mx.sh 2>&1 | teexcf_setinformix_mx.log

13. Create the database by entering the following command:

sc%> $SC_BINPATH/xdb_create_mx

14. Load configuration data to the database by entering the followingcommands:


> ./xdb_upgrade_load_tables_mx.sh 2>&1 | teexdb_upgrade_load_tables_mx.log

15. Stop Informix by entering the following command:

> onmode —ky

16. Log in as root and export VG02 to map file by entering the followingcommands:

# cd /

# vgexport –s –p –v –m vg02.map /dev/vg02

17. Transfer /vg02.map to the secondary database node by entering the

following command:

# rcp /vg02.map root@<secondary db hostname>:/

18. Transfer ONCONFIG.SC to the secondary database node by entering thefollowing command:

# rcp —p /opt/informix/IDS2000/etc/ONCONFIG.SCroot@<secondary dbhostname>:/opt/informix/IDS2000/etc/

19. Log in as root to the secondary database node and import vg02 by entering

the following commands:

# vgchange -c n vg02


# mkdir /dev/vg02

# mknod /dev/vg02/group c 64 0x020000






# vgimport –s –v –m vg02.map /dev/vg02

20. Remove old linking in the secondary database node by entering thefollowing command:

# rm /dev/*dbs_dat*

21. Set up database linking in the secondary database node by entering thefollowing command:


22. Log in as root to the primary database node and move the/opt/informix/IDS2000/etc/sqlhosts.mc2.1.SG file to/opt/informix/IDS2000/etc/sqlhosts by entering the followingcommand:

# mv /opt/informix/IDS2000/etc/sqlhosts.mc2.1.SG/opt/informix/IDS2000/etc/sqlhosts

23. Start ServiceGuard in the primary node by entering the followingcommands:

# cmapplyconf -v -C /etc/cmcluster/cmclconfig.ascii -P/etc/cmcluster/INFORMIX/INFORMIX.conf

# cmruncl -v

# cmmodpkg -e INFORMIX

If you use SC10 disk array, follow the steps below to upgrade the database fromMMS Center 2.0 to MMS Center 2.1.

To upgrade the database from MMS Center 2.0 to MMS Center 2.1 if SC10 disk array is used

1. Enter the following commands as sc user to upgrade the database fromMMS Center 2.0 to MMS Center 2.1:


sc>% ./xdb_upgrade_mc2_to_mc2_1_mx.sh 2>&1 | teexdb_upgrade_mc2_to_mc2_1_mx.log






Note

sc>% ./xdb_upgrade_unload_tables_mx.sh 2>&1 | teexdb_upgrade_unload_tables_mx.log

The duration of the database upgrade depends on the amount of data in thedatabase.

2. Log in as root to the primary database node, and shut down IBM Informixdatabase server by entering the following command:

# cmhaltcl —f

3. Apply the instructions in Appendix A to both database nodes.

4. Apply the instructions in Appendix B to both database nodes.

5. Log in as root to the primary database node and copy the/opt/informix/IDS2000/etc/sqlhosts file to/opt/informix/IDS2000/etc/sqlhosts.mc2.1.SG by entering thefollowing command:

# cp —p /opt/informix/IDS2000/etc/sqlhosts/opt/informix/IDS2000/etc/sqlhosts.mc2.1.SG

6. Edit the /opt/informix/IDS2000/etc/sqlhosts file by replacing<SG packet ip> with <dbprimary node ip>.

7. Activate the volume group VG02 by entering the following commands:


# vgchange -a y vg02

8. Check that logical log dbspace is 2GB by entering the following command:

# lvdisplay /dev/vg02/llogdblvol | grep Size

If the size in megabytes is not 2048, enter the following command:

# lvextend -L 2048 /dev/vg02/llogdblvol

9. Enter the following commands as root user to create a map file from vg02.

# vgexport -s -v -p -m vg02.map /dev/vg02

10. Enter the following commands as root user to relink database lvols(/dev/*dbs_dat*):






Caution

# cd /etc/opt/nokia/mmsc/tools

# ./xcf_relink_sc10_mx.sh

# ./xcf_dblinks_mx.sh

If errors are displayed after executing the script above, restore the original vg02configuration by exporting the old vg02 and recreating it from the vg02.mapmapfile.

11. Log in as user informix and copy the ONCONFIG.SC file to/opt/informix/IDS2000/etc/ by entering the following command:(X stands for the number of CPUs in the system.)

> cp/etc/opt/nokia/mmsc/tools/xcf_ONCONFIG.SC.standalone_Xcpu /opt/informix/IDS2000/etc/ONCONFIG.SC

12. Change the /dev/IDS_tape link to point to /dev/null by entering thefollowing commands as root user:

# rm /dev/IDS_tape


13. Set up IBM Informix database by entering the following commands:


> ./xcf_setinformix_mx.sh 2>&1 | teexcf_setinformix_mx.log

14. Create the database by entering the following command:

sc%> $SC_BINPATH/xdb_create_mx


# rm /dev/IDS_tape


16. Load configuration data to the database by entering the followingcommand:







> ./xdb_upgrade_load_tables_mx.sh 2>&1 | teexdb_upgrade_load_tables_mx.log

17. Stop Informix by entering the following command:

> onmode —ky

18. Export VG02 to map file by entering the following commands:

# vgchange -a n vg02

# vgchange -c y vg02

# cd /

# vgexport –s –p –v –m vg02.map /dev/vg02

19. Transfer /vg02.map to the secondary database node by entering thefollowing command:

# rcp /vg02.map root@<secondary db hostname>:/

20. Log in as root to the secondary database node and import vg02 by enteringthe following commands:



# mkdir /dev/vg02

# mknod /dev/vg02/group c 64 0x020000

# vgimport –s –v –m vg02.map /dev/vg02

21. Set up database linking in the secondary database node by entering thefollowing command:


22. Log in as root to the primary database node and move the

/opt/informix/IDS2000/etc/sqlhosts.mc2.1.SG file to/opt/informix/IDS2000/etc/sqlhosts by entering the followingcommand:

# mv /opt/informix/IDS2000/etc/sqlhosts.mc2.1.SG/opt/informix/IDS2000/etc/sqlhosts

23. Start ServiceGuard in the primary node by entering the followingcommands:






# cmapplyconf -v -C /etc/cmcluster/cmclconfig.ascii -P/etc/cmcluster/INFORMIX/INFORMIX.conf

# cmruncl -v

If the cluster does not start, enter the # cmruncl -v command once more.

# cmmodpkg -e INFORMIX

5.5 Installing additional libraries for the MMS Center

The MMS Center needs additional libraries. Those libraries are installed using theswinstall tool on the CD-ROM.

Follow the steps below to load the MMS Center libraries from the CD-ROM.

To load the MMS Center additional libraries from the CD-ROM




# swinstall -s /SD_CDROM/MC2_VBLib.depot




5.6 Adding cron entries for the sc user

Some tasks need to be performed daily in the MMS Center. These tasks are runwith cron.






Note

Follow the steps below to add the cron entries for the sc user. The tasks should beperformed on both database nodes.

If additional customer specific cron entries are needed for database servers, theycan be added now. Do not uncomment the lines in the step below in MMS Centerfront-ends. Crontab entries for the sc user can be viewed by entering thecommand: sc>% crontab -l.

To add cron entries for the sc user in database nodes

1. Edit the $SC_CONFPATH/xcfcrontab_mx.cf file and uncomment thefollowing lines:

0 3 * * * /bin/sh /etc/opt/nokia/mmsc/script/xdc_db_clean_mx.sh53 * * * * /bin/sh/etc/opt/nokia/mmsc/script/xdb_update_statistics_mx.sh

2. Enter the following command to add sc entries:

sc>% $SC_SCRIPTPATH/xcfcrontab_mx.sh

5.7 Upgrading log writer to MMS Center 2.1

Make sure that you have either Perl version 5.0 or 5.6 on your UNIX system. Theupgrade is done by running a script.

Follow the steps below to upgrade the log writer

To upgrade the log writer

1. Log in as root user.

2. Run the the script by entering the following commands:

sc%> cd /etc/opt/nokia/mmsc/tools

sc%> cp -p xamlwr_upgrade_mx.perl/etc/opt/nokia/mmsc/conf/xamlwr_upgrade_mx.perl






sc%> cd /etc/opt/nokia/mmsc/conf/

sc%> xamlwr_upgrade_mx.perl

If Perl is not found in the default path, enter the following commandinstead:

sc%> perl xamlwr_upgrade_mx.perl

3. If the upgradable log writer configuration files are not found in path/etc/opt/nokia/M2.0-23/conf/ , the path for the configuration hasto be given to the script by entering, for example:

sc%> xamlwr_upgrade_mx.perl –p/ect/opt/nokia/M2.0.

4. The expected outcome is as follows:

1. The script makes backups.

XamLoggingIf.cfand xamlwrmx.cf files are copied and placedusing file names <orig name>.<timestamp>.backup. If anyfile is missing, the script prints an error message to the standardoutput and dies.

2. All configuration files are read into memory.

If any file is missing, the script prints an error message to thestandard output and dies. Note that if either of the MMS Center 2.0XamCadmx.cf or xscmanmx.cf configuration files is missing,only a notification is given.

3. Files are upgraded.

The system modifies XamLoggingIf.cf and xamlwrmx.cfconfiguration files (in memory) and writes them to the disk.

5. Remove the perl script by entering the following command:

sc%> rm/etc/opt/nokia/mmsc/conf/xamlwr_upgrade_mx.perl

Example 1. Log writer upgrade output

Logwriter configuration files upgrade script, v1.0Copyrigth (c) 2002 Nokia Oyj

Upgrade files, are you sure (y/n)? yMake backups...Read XamLoggingIf.cf file.Read xamlwrmx.cf file.Write XamLoggingIf.cf.20021105105406.backup file.Write xamlwrmx.cf.20021105105406.backup file.Read files...






Read ymc_events.cf file.Read xlwmanmx.cf file.Remark: file 'XamCadmx.cf' not exist.Remark: file 'xscmanmx.cf' not exist.Read XamLoggingIf.cf file.Read xamlwrmx.cf file.Upgrade files...Write XamLoggingIf.cf file.Write xamlwrmx.cf file.Done.

5.8 Deploying the GUI

The graphical user interface (GUI) needs to be deployed in both front-end nodes.

Follow the steps below to deploy the MMS Center web application.

To deploy the MMS Center web application

1. Start the JRun admin server as sc user by entering the followingcommands:

sc%> cd /opt/JRun/bin

sc%> nohup ./jrun -start admin &

2. Start the browser.

3. Go to JRun by entering http://<mmsc.operator.com>:8000 and login as admin user.

4. Select JRun Default Server / Web Applications.

5. Select Remove an application.

6. Select MMS Center.

7. Click Remove.

8. Select Deploy an application.

9. Go to the servlet War file or the /opt/nokia/mmsc/lib/ygsman.wardirectory and modify the following:

• In the JRun server name drop-down menu, select JRun Defaultserver.

• In the Application name field, enter MMS Center.






Note

• In the Application host drop-down menu, select All Hosts.

• In the Application URL field, enter /mmsc.

• In the Application deploy directory field, enter/opt/nokia/mmsc/lib/gui.

(If you are using the browse function you must enter 'gui' manually.)

10. Click Deploy.

11. Restart the default server by selecting JRun default server and clickingRestart server.

12. Log out from JRun admin server by clicking Logout.

13. Stop the JRun admin server as sc user by entering the following:


sc%> ./jrun -stop admin

The first MMS Center node can now be started through the GUI as described inthe next chapter.

5.9 Connecting to the MMS Center GUI and starting theMMS Center

Once you have deployed the GUI to the MMS Center node, follow the stepsbelow to connect to the MMS Center GUI.


• Open the MMS Center GUI by entering the following to your browser:







To start the MMS Center


2. Select MMSC by checking it in the box to the left and click Start.

The MMS Center status and statuses for all processes should change toRunning after the screen refreshes (this may take a while). Downtime endsat this point.



Upgrade after downtime



6 Upgrade after downtime

6.1 Copying required Java classes and the GUIconfiguration file to the database servers

Perform the tasks in this chapter on both database servers.

To copy the required Java classes and the GUI configuration file to thedatabase servers

1. Log in to the MMS Center node as sc user.

2. Go to the $SC_LIBPATH directory by entering the following command:

sc>% cd $SC_LIBPATH

3. Copy the gui directory by entering the following command:

sc>% rcp -p -r gui <db_node_name>:/opt/nokia/mmsc/lib

4. Go to the $SC_CONFPATH directory by entering the following command:

sc>% cd $SC_CONFPATH

5. Copy the ygsguienv.cf file by entering the following command:

sc>% rcp -p -r ygsguienv.cf<db_server>:/etc/opt/nokia/mmsc/conf






Note

6.2 Configuring configuration tool (COT) for servers innetworked MMS Center

The $SC_CONFPATH/xccnodeslistmx.cf configuration file contains the listof the servers in a networked MMS Center. It is used in MMS Center 2.1 whencopying certificates between the servers. The file should be identical in bothfront-end servers.

To configure servers

The $SC_CONFPATH/ymc_mmsc.cf configuration file contains the server ID of the server in a networked MMS Center.

1. Update the $SC_CONFPATH/ymc_mmsc.cf file to contain the ID numberof the server. For example:

[NODE]# Add node-specific parameters in this sectionNODE_ID = 1

The node ID should be unique to every node. Set NODE_ID to 1 in the admin node.

2. Check the xccnodeslistmx.cf file in the $SC_CONFPATH directory.

The following changes should have been made:

• [MAIN] section:

- nodes = number of servers in network

• [NODE_1] section:

- host = The name of the admin node (uname –n)

- type = admin

- address = <ip_of_the_admin_node>

- node_id = <NODE_ID>

• [NODE_2] section:

- host = The IP-address of the other host in acluster

- type = normal






Note

- address = <ip_of_the_normal_host>

- node_id = <NODE_ID>

The configured IP addresses should be in the same subnet.

3. Edit the /etc/rc.config.d/nfsconf file to enable auto mounting forthe networked file system (NFS).

Find the AUTOMOUNT parameter and edit the value to 1.

Repeat the process for all MMS Center nodes.

4. Run the COT configuration as root user as follows:

1. Run the script xcesetadminmx.sh with parameter -c<admin_node> on all client hosts. For example:

# cd /etc/opt/nokia/mmsc/script

# ./xcesetadminmx.sh -c <admin node>

2. Run the script xcesetadminmx.sh with parameter -a on theadministration node. For example:

# cd /etc/opt/nokia/mmsc/script

# ./xcesetadminmx.sh -a

The script asks about a prompt command mode that will display allcommands and ask for confirmation before executing them. You can exitthe script from this mode by answering NO to one of the commands.

There are several lines in this script where you should answer YES tocontinue. Later, the script will ask you to write the names of the non-administration hosts for the administration COT to be able to modify fileson those hosts.

After the last host you can stop executing this script by answering CTRL+Dwhen the script asks for another host name.

5. Restart JRun default server by entering the following commands as sc user:


sc%> ./jrun -stop default

sc%> nohup ./jrun —start default&






Note

6.3 Making backup tapes of the MMS Center

Take a full backup at this point if the system has been verified to function

correctly.

Do not reuse old tapes for this procedure.

To make an Ignite backup tape of the system disk

1. To make an Ignite tape, insert an empty tape to the tape drive and enter thefollowing command:

# make_tape_recovery -x inc_entire=vg00 -x inc_entire=vg01 -I -A -t "MC2.1 recoverytape"

This creates a backup of the system disk.

2. Remove the tape from the drive and label it 'MC2.1 recovery tape'.

To back up MMS Center 2.1 directories

1. Insert a new tape into the tape drive.

2. Take a backup of the MMS Center by entering the following command:

sc>% tar cvf /dev/rmt/0m /sc_opt/<MMSC_build>/sc_etc/<MMSC_build> /sc_var/<MMSC_build>

3. Remove the tape from the drive and label it 'MC2.1 software tape'.

To take a backup of the database structures in the database

1. Log in as root user to the primary database node.


# rm /dev/IDS_tape






Note

Note


3. Insert a new tape into the drive and make a level 0 backup of the databaseby entering the following command as informix user:

> ontape -s -L 0

4. Remove the tape and change the /dev/IDS_tape link to point back to/dev/null by entering the following commands as root user:

# rm /dev/IDS_tape


6.4 Loading event logs and performance data fromtape

Follow the steps below to load event logs and performance data from the tape tothe database.

Tapes used in this procedure are the ones created in Section 4.5 Unloading eventlogs and performance data to tape.

This operation does not cause downtime, but might reduce database performancewhile completing the operation. It is adviced that this operation is not done duringpeak-hours.

Table 4. DDS tape sizes

DDS tape version Capacity

uncompressed

Capacity compressed

dds–3 12 24 GB

dds–4 20 40 GB






To load event logs and performance data from tape

1. Log in as sc user to the primary database node.

2. Insert the first tape to the primary database tape drive and enter thefollowing command:


sc>% ./xdb_upgrade_load_logs_mx.sh 2>&1 | teexdb_upgrade_load_logs_mx.log

If you have more than one tape, you will be prompted for the next tapes.

3. Log in as root user and remove the /sc_var/backup directory byentering the following commands:

# cd /sc_var

# rm -R backup



Accepting the installation



7 Accepting the installation

Follow the steps below to accept the installation.

To accept the installation

• Execute the SAT test cases (see System Acceptance Tests).

Fill in the Installation Acceptance form and fax the form to Nokia TechnicalSupport.



Upgrading Open View Operations interface to MMS Center 2.1



8 Upgrading Open View Operationsinterface to MMS Center 2.1

To upgrade the Open View Operations (OVO) interface to MMS Center 2.1, youneed to remove the old templates from the OVO agents.

Follow the steps below to upgrade Open View Operations interface to MMS

Center 2.1.

To remove MMS Center 2.0 templates from the upgradable MMSCenters

1. From the OVO GUI, open the Node Bank.

2. Select the node/nodes you have installed the smart plug-in to. Press downthe CTRL key when selecting many.

3. From the Actions drop-down list, select Agents > Assing Templates....The Define Configuration window opens.

4. Choose the node/nodes under the Node/Group and Templates list. Click Remove selected and click OK to close the window.

5. In the Node Bank window, select the MMS Center icon of the node/nodesyou removed from the Node/Group and Templates list. Press down theCTRL key when selecting many.

6. From the Actions drop-down list, select Agents > Install/Update

SW&Config....

The Install/Update Software and Configuration window opens.






Note

7. In the Components list, check Templates, Actions, Monitors andCommands. In Options, check Force Update.

Check that the desired nodes are listed in the Target Nodes list.

If you need to add a node/nodes onto the list, select the desired node/nodesin the Node Bank window. In the Install/Update Software and Configurationwindow, use the Get Map selections button to fetch the selected node/nodes ontothe Target Nodes list.

8. To enable the changes, click OK.

To install the smart plug-in for MMS Center 2.1

• To complete the upgrade, see Sections Installing the Nokia MMS Center smart plug-in, Verifying Nokia MMS Center smart plug-in installation and Activating the OVO interface in the Centralised Management with HPOVO Interface document.

To verify the smart plug-in installation for MMS Center 2.1

1. Under the Windows drop-down list, in the Node Bank window, click Message Source Templates to check whether the update was successful.

2. In the Message Source Templates window, select Nokia MMSC in theTemplate Groups list.

3. Check that you have the Nokia MMSC 2.1 template on the list in thewindow to the right.



Downgrading from MMS Center 2.1 to MMS Center 2.0



Note

9 Downgrading from MMS Center 2.1 toMMS Center 2.0

Follow the steps below to downgrade from MMS Center 2.1 to MMS Center 2.0.

To downgrade from MMS Center 2.1 to MMS Center 2.0

1. If MMS Center 2.1 is running, shut down MMS Center 2.1 through theGUI, or from the commandline by entering the following command:

sc>% /opt/nokia/mmsc/bin/xsccmdmx —s TrustMe

2. Enter the following command to switchthe new_mmsc links topoint totheMMS Center 2.1 directories, and the mmsc links to point to the MMSCenter 2.0 directories on all the nodes in the MMS Center cluster.

# cd /

# /etc/opt/nokia/mmsc/tools/xcf_link_switcher_mx.sh

3. The database downgrade from MMS Center 2.1 toMMS Center 2.0 is donewith a script. Log in as sc user to the primary database server on thedatabase primary node.

At this point the Informix database should be running.

4. Enter the following commands as sc user to downgrade the database fromMMS Center 2.1 to MMS Center 2.0:

sc>% cd /etc/nokia/new_mmsc/toolssc>% ./xdb_downgrade_mc21_to_mc2_mx.sh 2>&1 | tee downgrade.log

Follow the steps below to deploy the MMS Center web application.






To deploy the MMS Center web application

1. Start the JRun admin server as sc user by entering the followingcommands:


sc%> nohup ./jrun -start admin &

2. Start the browser.

3. Go to JRun by entering http://<mmsc.operator.com>:8000 and login as admin user.

4. Select JRun Default Server / Web Applications.

5. Select Remove an application.

6. Select MMS Center.

7. Click Remove.

8. Select Deploy an application.

9. Go to the servlet War file or the /opt/nokia/mmsc/lib/ygsman.wardirectory and modify the following:

• In the JRun server name drop-down menu, select JRun Defaultserver.

• In the Application name field, enter MMS Center.

• In the Application host drop-down menu, select All Hosts.

• In the Application URL field, enter /mmsc.

• In the Application deploy directory field, enter/opt/nokia/mmsc/lib/gui.

(If you are using the browse function you must enter 'gui' manually.)

10. Click Deploy.

11. Restart the default server by selecting JRun default server and clickingRestart server.

12. Stop the JRun admin server as sc user by entering the followingcommands:



Downgrading from MMS Center 2.1 to MMS Center 2.0




sc%> ./jrun -stop admin


• Open the MMS Center GUI by entering the following to the browser:


To start the MMS Center


2. Select MMSC by checking the box to the left and click Start.

The MMS Center status and the statuses for all processes should change toRunning after the screen refreshes (this may take a while).



Installing the HP-UX patches



Note

Appendix A. Installing the HP-UX patches

Follow the steps below to load the HP-UX patches from the CD-ROM.

The patches included in MC_21_patches bundle are listed below. To view a listof single patches, enter the command swlist -l product as root user.

Table 5 lists the HP-UX patches that must be installed to the system.

To load the HP-UX patches from the CD-ROM


2. Enter the following commands.


# swinstall -s /SD_CDROM/mmsc21patch.depot

Table 5. Patches in MC_21_patches bundle

Product Version Name

PHKL_25233 1.0 select(2) and poll(2) hang

PHKL_25389 1.0 Core PM, vPar, Psets

Cumulative Patch

PHKL_26405 1.0 PDC

retry,PDC_SCSI_PARMS,i

COD hang,PDC busy

PHKL_26705 1.0 syslog/console

handling,printf panic fix

PHNE_22722 1.0 NTP timeservicesupgrade plus utilities

PHNE_25184 1.0 sendmail(1m) 8.9.3 patch

PHNE_26728 1.0 Cumulative STREAMS

Patch

PHNE_27063 1.0 cumulative ARPA

Transport patch






3. Select needed depot files.

4. Select Actions > Mark for install for all the patches needed.


The disk devices can be found by entering the command ioscan -fnC disk.



Applying MC2.1 tuned kernel parameter set



Appendix B. Applying MC2.1 tuned kernel parameter set

UNIX kernel parameters have to be changed to match the requirements of theMMS Center software.

Follow the steps below to regenerate the UNIX kernel.

To regenerate the UNIX kernel

1. Change UNIX kernel parameters with System Administration Manager(SAM). The system reboots automatically after any changes to the systemparameters.

2. Enter the following command at the command prompt to initialise SAM:

# sam

3. Once in SAM, select the following items to set the required HP-UX OSkernel parameter changes:

a. Select the Kernel Configuration icon.

b. Select the Configurable Parameters icon.

c. From the Menu bar, select Actions.

d. Under Actions, select Apply Tuned Parameter Set.

e. Scroll to the MMS Center MC21 tuned kernel set and click OK.

The kernel set file used is/usr/sam/lib/kc/tuned/mmsc_mc21.tun .

It is provided to eliminate typographical errors that are sometimesencountered when editing the kernel parameters manually.

4. Follow the stepsbelow toaccept the modifications tothekernel parametersand to create a new kernel:

a. Select File.

b. Select Exit.

c. Select Create a New Kernel Now.

d. Confirm by clicking OK.






e. Confirm the system reboot by clicking OK.

f. Click OK to confirm the alarm message about overwriting/stand/system.

The system reboots automatically.





References

Nokia MMS Center documents:

1. Centralised Management with HP OVO Interface DN028405.

2. Operating MMS Center DN0272867.

3. System Acceptance Tests DN00148805.

mmsc2.0 cluster to mmsc2.1 cluster with sg upgrade manual

Documents