1. © 2007 IBM Corporation ® Netcool Impact 7.x Clustering Setup Pedro Guerra - IBM Tivoli Support Engineer This call is being recorded, You may hang up if you object. Please mute your phone when not speaking.

2. IBM Software Group | Tivoli software 2 Agenda  What is Nameserver Clustering?  Setup Nameserver Clustering  Configuration properties  Q&A Source:If applicable, describe source origin

3. IBM Software Group | Tivoli software 3 What is Netcool Clustering?  Server clustering is a feature of Netcool/Impact that allows you to install a group of related Netcool/Impact servers and configure them to operate as a single server instance.  You use this feature to add failover and load-balancing functionality to a Netcool/Impact installation.  Secondary server synchronizes its services, data types, data sources, policies, and configuration settings with the primary server before becoming active.

4. IBM Software Group | Tivoli software 4 Source:If applicable, describe source origin Setup Nameserver Clustering

5. IBM Software Group | Tivoli software 5 Setup Nameserver Clustering  There is two ways to setup clustering on Impact 7.x: –During Installation –Two stand alone Impact servers Note: Impactadmin has to have the same password in all cluster members.

6. IBM Software Group | Tivoli software 6 What can I cluster? NCI NCICLUSTER NCS NCICLUSTER NCI NCICLUSTER NCI NCICLUSTER NCI NCICLUSTER NCI NCISECLUSTER = YES = NO X X

7. IBM Software Group | Tivoli software 7  Primary Nameserver Host  Primary Nameserver Port  Secondary Nameserver Host  Secondary Nameserver Port  Example: Primary: impact.nameserver.0.host=nc9053113106.tivlab.austin.ibm.com impact.nameserver.0.port=9080 Secondary: impact.nameserver.0.host=nc9053113184.tivlab.austin.ibm.com impact.nameserver.0.port=9080 Setup Nameserver Clustering

8. IBM Software Group | Tivoli software 8 Setup Nameserver Clustering 1.During Installation:

9. IBM Software Group | Tivoli software 9 Setup Nameserver Clustering

10. IBM Software Group | Tivoli software 10 2. Two stand alone Impact servers: In Primary Impact server go to $IMPACT_HOME/install/nameserver/ setNameServer.sh -add myhost.mycompany.com,9080  [pedro@nc9053113106 nameserver]$./setNameServer.sh -add nc9053113184.tivlab.austin.ibm.com,9080 Complete. Nameserver changes require that the server be restarted before the changes take effect.  [pedro@nc9053113106 nameserver]$./setNameServer.sh -list impact.nameserver.0.host=nc9053113106.tivlab.austin.ibm.com impact.nameserver.0.port=9080 impact.nameserver.1.host=nc9053113184.tivlab.austin.ibm.com impact.nameserver.1.port=9080 Setup Nameserver Clustering

11. IBM Software Group | Tivoli software 11  Stop Primary Impact server by running “stopImpactServer.sh”  Copy the $IMPACT_HOME/etc/nameserver.props from the Primary to the Secondary server in $IMPACT_HOME/tmp  On the Secondary import the nameserver.props file that you copy from Primary server  Go to $IMPACT_HOME/install/nameserver/ setNameServer.sh -import /tmp/nameserver.properties [pedro@nc9053113184 nameserver]$./setNameServer.sh -import /opt/IBM/tivoli/impact/tmp/nameserver.props Complete. Nameserver changes require that the server be restarted before the changes take effect. [pedro@nc9053113184 nameserver]$./setNameServer.sh -list impact.nameserver.0.host=nc9053113106.tivlab.austin.ibm.com impact.nameserver.0.port=9080 impact.nameserver.1.host=nc9053113184.tivlab.austin.ibm.com impact.nameserver.1.port=9080 Setup Nameserver Clustering

12. IBM Software Group | Tivoli software 12  Check the following files in both Primary and Secondary Impact servers to make sure the configuration is correct: $IMPACT_HOME/wlp/usr/servers/ /apps/nameserver.war/WEB-INF/web.xml $IMPACT_HOME/etc/nameserver.props http://primary.com:9080/nameserver/services Finally Start Primary Impact server and then Secondary Impact server. Check the $IMPACT_HOME/logs/impactserver.log Setup Nameserver Clustering

13. IBM Software Group | Tivoli software 13 Setup Nameserver Clustering Primary impactserver.log

14. IBM Software Group | Tivoli software 14 Setup Nameserver Clustering Secondary impactserver.log

15. IBM Software Group | Tivoli software 15 Configuration properties  $IMPACT_HOME/etc/nameserver.props impact.nameserver.netcall_timeout = Number of seconds that the Impact server waits on each call to the Name Server before timing out. The default value is set to 30 seconds.  $IMPACT_HOME/etc/servername_server.props impact.cluster.name = Name of the server cluster. The default value is NCICLUSTER. impact.cluster.pinginterval = Interval in milliseconds at which to ping other cluster members. The default value is 6000. impact.cluster.pingtimeout = Time in milliseconds to wait before retrying ping. The default value is 6000. impact.cluster.repingcount = Number of times to retry ping if the first fails. The default value is 3.

16. IBM Software Group | Tivoli software 16 Configuration properties  Primary Impact server: $IMPACT_HOME/etc/ _server.props impact.server.preferredprimary=true  Secondary Impact server: $IMPACT_HOME/etc/ _server.props file of the secondary server. Required: To enable the feature use this property: impact.server.waitforprimaryonstartup=true Optional: Use this property to change the default time the secondary server waits for the primary server: impact.server.waitforprimary.duration= If you do not use this property or provide no value for it, by default, the secondary server waits for 240000 miliseconds (4 minutes).

17. IBM Software Group | Tivoli software 17 Questions?