IBM Tivoli Netcool/OMNIbus, Version 7.4

Removing a node

Follow these steps to remove a node from the load balancing cluster.

About this task

The following parameters are used on the disjoin option when a node is removed.
  • -Dusername - specify the DB2 administrator's username
  • -Dpassword - specify the DB2 administrator's password

Procedure

  1. From a command prompt, change to the tip_home_dir/profiles/TIPProfile/bin/ha directory and issue this command:
    • For Windows operating system..\ws_ant.bat -f uninstall.ant disjoin -Dusername=DB2_username -Dpassword=DB2password
    • For Linux operating systemFor UNIX operating system../ws_ant.sh -f uninstall.ant disjoin -Dusername=DB2_username -Dpassword=DB2password
  2. Update the network dispatcher (for example, IBM HTTP Server) to remove the node from the configuration.
Parent topic: Removing a node from a cluster
Previous topic: Removing the Web GUI load balancing information
Next topic: Restarting the server as a stand-alone system

Removing a remote node

About this task

This command should be used only in the rare occasions where physical access to the node is not available or a serious hardware or software failure has occurred. If the node is remotely disjoined but continues to function, some problems with synchronization might arise that can lead to problems with data consistency and synchronization.

Procedure

  1. From a command prompt, change to the tip_home_dir/profiles/TIPProfile/bin/ha directory and issue this command:
    • For Windows operating system..\ws_ant.bat -f uninstall.ant remote-disjoin –DremoteHost=remote_host –DremotePort=9044 -Dusername=DB2_username -Dpassword=DB2_password
    • For Linux operating systemFor UNIX operating system../ws_ant.sh -f uninstall.ant remote-disjoin –DremoteHost=remote_host –DremotePort=9044 -Dusername=DB2_username -Dpassword=DB2_password
  2. Update the network dispatcher (for example, IBM HTTP Server) to remove the node from the configuration.