Impact 5.1.1 FPs or IFs not installing correctly on non-primary Cluster members

Flash (Alert)


Abstract

There is a known issue with installing Fix Packs and Interim Fixes on Impact 5.1.1 to the secondary cluster members (all cluster members other then the primary server).

Content

If the Fix Pack or Interim Fix does not get installed correctly, none of the fixes included in Fix Pack/Interim Fix will be applied to the secondary cluster member(s).

To install on secondary cluster members correctly, take the following steps:

1) Stop the secondary cluster server (stopping eWAS).

2) Modify the secondary cluster server's $NCHOME/impact/etc/nameserver.props file, to point to itself (see the examples below). Be sure to change the index and count values.

Change the current secondary cluster server's $NCHOME/impact/etc/nameserver.props (hostname on secondary in this example it's "shark"):

------------------------------------------------
impact.nameserver.0.host=snowpea
impact.nameserver.0.port=9887
impact.nameserver.0.location=/nameserver/services

impact.nameserver.1.host=shark
impact.nameserver.1.port=9888
impact.nameserver.1.location=/nameserver/services

impact.nameserver.2.host=beans
impact.nameserver.2.port=9889
impact.nameserver.2.location=/nameserver/services

impact.nameserver.count=3

impact.nameserver.ssl_enabled=false
impact.nameserver.netcall_timeout=60

------------------------------------------------

Change it to look like this (changes in underline bold text):

------------------------------------------------
#impact.nameserver.0.host=snowpea
#impact.nameserver.0.port=9887
#impact.nameserver.0.location=/nameserver/services

impact.nameserver.0.host=shark
impact.nameserver.0.port=9888
impact.nameserver.0.location=/nameserver/services

#impact.nameserver.2.host=beans
#impact.nameserver.2.port=9889
#impact.nameserver.2.location=/nameserver/services

impact.nameserver.count=1

impact.nameserver.ssl_enabled=false
impact.nameserver.netcall_timeout=60

------------------------------------------------

3) Stop the primary cluster member

4) Now start and install the Fix Pack or Interim Fix on the secondary cluster server (be sure to follow the patch's Readme for proper patch installation).

5) After installing, take the following steps to verify that the patch was successfully installed:

Do "ls $NCHOME/eWAS/profiles/ImpactProfile/installableApps/" (note 5.1.1.1.ear, and not 5.1.1.ear) :

-------------------------------
NC-guiserver-5.1.1.1.ear
<your instance name>-impact-5.1.1.1.ear

-------------------------------

Check the NCHOME/eWAS/profiles/ImpactProfile/logs/server1/SystemOut.log file. Look for the following entry:

--------------------------------
For 5.1.1 Fix Pack 1:
"Application build level: IMPACT [b213]"

For 5.1.1 Interim Fix 1:"
Application build level: IMPACT [b180]"

For 5.1.1 Interim Fix 2:
"Application build level: IMPACT [b237]"

--------------------------------

6) Stop the secondary cluster server (stopping eWAS again).

7) Change the secondary cluster server's $NCHOME/impact/etc/nameserver.props file back to its original values. Again be sure to change the index and count back to their original values.

8) Follow steps 1 - 6 on all subsequent cluster members (in the example above, "beans" is next).

9) Restart the primary cluster member.

10) Once the primary is up and running, start the secondary cluster member(s).

Rate this page:

(0 users)Average rating

Add comments

Document information


More support for:

Tivoli Netcool/Impact
Netcool/Impact

Software version:

5.1.1

Operating system(s):

AIX, HP-UX, Linux, Solaris, Windows

Software edition:

All Editions

Reference #:

1439209

Modified date:

2012-02-16

Translate my page

Machine Translation

Content navigation