Configuring a high-availability hub

A configuration that includes a high-availability (HA) hub is resilient and efficient. It is resilient because the HA hub can be relocated to any LPAR in the sysplex with minimal disruption to the other components. The configuration is efficient because the remote monitoring server on the same LPAR as the hub handles all communications with the monitoring agents and thus reduces the load on the hub. If your environment supports the requirements for a HA hub, you should configure one.

About this task

You can configure a high-availability hub monitoring server in any sysplex environment with dynamic virtual IP addressing (DVIPA) and shared DASD. A high-availability hub is configured in its own runtime environment, without any monitoring agents, and can be configured on the same LPAR with a remote monitoring server. System variables are not enabled on an high-availability hub. This configuration allows the hub monitoring server to be relocated to any suitable LPAR in the sysplex with no changes, and with minimal disruption to the components connecting to the hub.

Figure 1 depicts an HA hub monitoring server connected to a remote monitoring on the same LPAR, to remote monitoring servers on other LPARs, to remote monitoring servers on distributed systems, and to the Tivoli Enterprise Portal server.

Configuration graphic: High-availability hub connected to a remote on the same LPAR, to remotes on other LPARs, and to remotes on distributed systems. — Figure 1. High-availability hub monitoring server and its connections

Reminder: An HA hub is the only type of hub that can be on the same LPAR with a remote monitoring server that reports to it. You can configure monitoring agents to report to the remote hub. You should not configure monitoring agents to report directly to the HA hub.

Tips:

The parameters shown in this section are not the only parameters you might need to set in the configuration profile for the runtime environment. After you set the parameters shown here, be sure to go through the entire configuration profile to make sure the parameter values are correct for the configuration you want.
The parameters with names beginning KDS_HUB are not parameters for the hub monitoring server; they are parameters for remote monitoring servers.
For information on the XF (“EXCLUDE FIND") macro, seeXF edit macro.

The following instructions assume that the KDS_TEMS_TYPE parameter was set to HUB and the KDS_TEMS_HA_TYPE parameter was set to HA during the set up of the environment. If this is not the case, set those parameters in the RTE configuration profile before completing the following procedure.

Procedure

Do an EXCLUDE FIND of all _TCP_HOST strings, then customize all occurrences of the LPAR name to the reserved DVIPA name.

In this example, this is hostname OMEGHAHUB.

ISREDDE2 TSTEST.&userid.HAHUB.WCONFIG(HAHUB) 
Command ===> C &hostname OMEGHAHUB ALL                            Scroll ===> CSR  
****** ***************************** Top of Data ******************************
- - -  -  -  -  -  -  -  -  -  -  -  -  -  -  -  -   307 Line(s) not Displayed 
000308 **       000029 RTE_TCP_HOST                      "OMEGHAHUB"                
- - -  -  -  -  -  -  -  -  -  -  -  -  -  -  -  -   197 Line(s) not Displayed 
000506 RTE_TCP_HOST                      "OMEGHAHUB"                                
- - -  -  -  -  -  -  -  -  -  -  -  -  -  -  -  -   186 Line(s) not Displayed 
000693 ** Note: If this is a High-Availability Hub TEMS, KDS_TEMS_TCP_HOST     
- - -  -  -  -  -  -  -  -  -  -  -  -  -  -  -  -  -  1 Line(s) not Displayed 
000695 KDS_TEMS_TCP_HOST                 "OMEGHAHUB"                                
- - -  -  -  -  -  -  -  -  -  -  -  -  -  -  -  -  - 90 Line(s) not Displayed 
000786 ** Note: If this is a High-Availability Hub TEMS, KDS_PH01_TEMS_TCP_HOST
- - -  -  -  -  -  -  -  -  -  -  -  -  -  -  -  -  -  9 Line(s) not Displayed 
000796 KDS_PH01_TEMS_TCP_HOST            "OMEGHAHUB"                                
- - -  -  -  -  -  -  -  -  -  -  -  -  -  -  -  -  - 32 Line(s) not Displayed 
****** **************************** Bottom of Data ****************************

Do an EXCLUDE FIND of all _PORT parameters, then customize _PORT according to your site's conventions.

ISREDDE2 TSTEST.&userid.HAHUB.WCONFIG(HAHUB) 
Command ===> C ' 1918 ' ' nnnnn ' ALL                         Scroll ===> CSR  
****** ***************************** Top of Data ******************************
- - -  -  -  -  -  -  -  -  -  -  -  -  -  -  -  -   507 Line(s) not Displayed 
==CHG> RTE_TCP_PORT_NUM                  nnnnn                                 
- - -  -  -  -  -  -  -  -  -  -  -  -  -  -  -  -   176 Line(s) not Displayed 
==CHG> KDS_TEMS_TCP_PIPE_PORT_NUM        nnnnn    * IP.PIPE                    
==CHG> KDS_TEMS_TCP_UDP_PORT_NUM         nnnnn    * IP.UDP                     
- - -  -  -  -  -  -  -  -  -  -  -  -  -  -  -  -   110 Line(s) not Displayed 
==CHG> KDS_PH01_TEMS_TCP_PORT_NUM        nnnnn                                 
- - -  -  -  -  -  -  -  -  -  -  -  -  -  -  -  -   151 Line(s) not Displayed 
****** **************************** Bottom of Data ****************************

Customize the monitoring server protocols to support only IP: At least one of the values must be IPPIPE, IP6PIPE, IPSPIPE, or IP6SPIPE. Nullify the KDS_TEMS_COMM_PROTOCOL3 parameter by setting it to "" (instead of the SNA value set initially).

ISREDDE2 TSTEST.&userid.HAHUB.WCONFIG(HAHUB) 
Command ===>                                                  Scroll ===> CSR  
000658 ** TEMS communication protocols:                                        
000659 ** Specify the communication protocols to be used by the local TEMS.    
000660 ** Valid values are IPPIPE, IP, SNA, IP6PIPE, IP6, IPSPIPE, and         
000661 ** IP6SPIPE. When communication with another ITM component (TEPS, Hub   
000662 ** TEMS or Remote TEMS, Agents) is initiated, the TEMS tries Protocol 1 
000663 ** first and goes to Protocol 2 and so on, in case of failure.          
000664 ** Note: Update the corresponding KDS_TEMS_TCP_*_PORT_NUM port number   
000665 **       parameter for each KDS_TEMS_COMM_PROTOCOLx parameter enabled.  
000666 **       For example, if KDS_TEMS_COMM_PROTOCOL1="IPPIPE", set the      
000667 **       corresponding KDS_TEMS_TCP_PIPE_PORT_NUM parameter.            
000668 **       If KDS_TEMS_COMM_PROTOCOL2="IP" (for IP.UDP), set the          
000669 **       corresponding KDS_TEMS_TCP_UDP_PORT_NUM parameter.             
000670 **       If this is a Remote TEMS, update the KDS_HUB_* parameters      
000671 **       by uncommenting out the corresponding KDS_HUB_TCP_*_PORT_NUM   
000672 **       parameters and specify the Remote's Hub TEMS port numbers.     
000673 KDS_TEMS_COMM_PROTOCOL1           IPPIPE                                
000674 KDS_TEMS_COMM_PROTOCOL2           IP                                    
000675 KDS_TEMS_COMM_PROTOCOL3           ""

Uncomment the KDS_TEMS_TCP_KDEB_INTERFACELIST parameter, then change its value from the default (!*) to !dvipa_hostname, where dvipa_hostname is the private DVIPA name set for the KDS_TEMS_TCP_HOST parameter (in this example, !OMEGAHUB). This setting ensures that the high-availability hub is restricted to its private DVIPA address and cannot interfere with the remote monitoring server configured on the same LPAR.

ISREDDE2 TSTEST.&userid.HAHUB.WCONFIG(HAHUB) 
Command ===>                                                  Scroll ===> CSR  
000698 ** If the TEMS requires network interface list support:                 
000699 ** Note: If this is a High-Availability Hub TEMS, uncomment the         
000700 **       KDS_TEMS_TCP_KDEB_INTERFACELIST and set its value to           
000701 **       "!<dvipa_address>"                                             
000702 KDS_TEMS_TCP_KDEB_INTERFACELIST   "!OMEGHAHUB"

What to do next

These are not the only parameters you might want to set. For example, you might want to configure the monitoring server to enable event forwarding, support for self-describing agents, auditing, or the SOAP server.