IBM Support

Problem with multiple Remote Tivoli Enterprise Monitoring server(TEMS) running on the same AIX LPAR

Technote (troubleshooting)


Problem working multiple Remote TEMS on same LPAR and one of the Remote TEMS is not starting at all


The second Remote TEMS is unable to bind to the well known defined port

(50F6CA85.0115-5:kde12cl.c,110,"KDE1_ServerCall") <0xF4A1019E,0x1A> binding control block: F4A10098 portNo 49624
(50F6CA85.0117-4:kdcsuse.c,120,"KDCS_UseFamily") status=1c010005, "cant bind socket", ncs/KDC1_STC_CANT_BIND_SOCK
+50F6CA85.0115 00000000 1400C1D8 00000000 00000000 00000000 ................
+50F6CA85.0115 00000010 00000000 00000000 0000 ..........


IPV6 protocol is grabbing the well known port so IPV4 protocol is unable to bind to the well known port. The netstat -an will display the port information

Resolving the problem

To resolve the problem, disable the IPV6 protocol by using the below variable on both the Remote TEMS and recycle them.

edit $candlehome/config/<hostname>_ms_<tems node name>.config and add


Points to Remember :

1. In Windows, you can't have multiple Remote TEMS running on the same server. Basically, multiple Remote TEMS on the same windows server is NOT supported

2. In Linux/UNIX

You can have multiple Remote TEMS but

a. Each Remote TEMS should use different IP address (nic address)
b. Must be installed in different candlehome directory
c. KDEB_INTERFACELIST must be defined to use interface specific bind
ex : KDEB_INTERFACELIST=!ip address
d. Also, you can have multiple HUB and combination of HUB and Remote TEMS but as along as they satisfies the above criteria
e. You may have to disable discovery of IPV6 interfaces on all the TEMS running on the same server using the below variable


Document information

More support for: IBM Tivoli Monitoring V6
ITM Tivoli Enterprise Mgmt Server V6

Software version: All Versions

Operating system(s): AIX, Linux

Reference #: 1623344

Modified date: 27 June 2016

Translate this page: