DSR VerifyPCRFPoolingMigration.sh Script Fails

Asset ID:	1-71-2350304.1
Update Date:	2018-02-07
Keywords:

Solution Type Technical Instruction Sure

Solution 2350304.1 : DSR VerifyPCRFPoolingMigration.sh Script Fails

Applies to:

Oracle Communications Diameter Signaling Router (DSR) - Version DSR 7.0.1 and later
Tekelec

Goal

While performing the pre-health check in the DSR NOAM as part of the preparation of the upgrade, the script verifyPCRFPoolingMigration.sh fails:

[admusr@noam-b tools]$ ./verifyPCRFPoolingMigration.sh --checkPCRFPoolingMigrationStatus

Preparing log directory ...

Log directory /var/TKLC/log/migrationStatusToolLogs already created. Taking backup of log directory...
Successfully backup taken of log directory to /var/TKLC/log/migrationStatusToolLogs.1514982559
Creating log directory...
Logging is started in /var/TKLC/log/migrationStatusToolLogs/migrationStatusTool.log
Preparation of log directory done.

============= Execution of PCRF Pooling Migration Verification Tool Started ===============

Checking host server status whether it is active NOAMP server or not.
This server is Active NOAMP server.

Application Release is 7.0.1.0.0_70.28.8
All servers in the network are not on the same release as the NOAMP server, or, all the upgrades have not been accepted.

============= Execution of PCRF Pooling Migration Verification Tool Failed ===============
[admusr@noam-b tools]$

To identify the problem
What is the impact on the upgrade if this script fails?

Solution

First run following command and then run the log file that shows the results log:

gcli isUpgradeAcceptedOnAllServers Upgrade 2>&1

[admusr@noam-b ~]$ sudo gcli isUpgradeAcceptedOnAllServers Upgrade 2>&1
Command Failed
All the servers are not yet upgraded, for details please see ServersUpgradeStatus.log file in filemgmt area
[admusr@noam-b ~]$

[admusr@noam-b filemgmt]$ sudo cat ServersUpgradeStatus.log
************************ LOG FILE FOR UPGRADE CHECK API *******************
************************ Created On : 05/01 : 12:06 : *******************
All the servers are not yet upgraded please see the below release and servers mapping
Release : Servers
7.0.1.0.0_70.28.8 : noam-b, noam-a, dr-noam-a, dr-noam-b, soam-a, soam-b, soam-s, sbr-3, sbr-1, sbr-2, mp-10, mp-21, mp-22, mp-24, mp-8, mp-9, mp-7, mp-23, sbr-1, sbr-2, sbr-3, mp-22, mp-21, mp-7, mp-8, mp-9, mp-1, mp-3, mp-5, mp-23, mp-24, mp-2, mp-4, mp-6, mp-10
7.0.1.0.0-70.28.8 : soam-s, soam-a, soam-b, mp-2, mp-4, mp-6, mp-1, mp-3, mp-5
[admusr@noam-b filemgmt]$

The ServersUpgradeStatus.log shows difference in release numbers for some servers than others.

This is because patch-25106418 erroneously uses underscore ('_') instead of dash ('-') in the name. If the prod.start is run on any server, it changes back the _ to - as seen in few servers above. However to keep the consistency in name, exact name should be used.

In order to clear this, kindly run steps 1 to 3 on each of the servers mentioned below:

iqt -E applications.00
iset -fappversion=7.0.1.0.0_70.28.8 applications.00 where "appid=17"
iqt -E applications.00
Once above 3 steps are done on all servers, Execute the following on Active NOAM:
sudo gcli isUpgradeAcceptedOnAllServers Upgrade 2>&1
The command should not produce any error or any message.
If no message/response to command in step4, run the verify script. It should come clean this time.

Servers on which commands should be run:
soam-s
soam-a
soam-b
mp-2
mp-4
mp-6
mp-1
mp-3
mp-5

Attachments

This solution has no attachment