'KDC1_STC_FAMILY_NOT_VALID' message repeated in the TEMS log

Technote (troubleshooting)


There is not a way to disable these harmless messages without turning off all RAS1 messages. However, you can adopt some best-practices for the KDC_FAMILIES parameter.


You find the following message repeated hundreds of times in the TEMS log:

kdcs0la.c,74,"KDCS0_LocalizeAddress") status=1002000a, "address family invalid", ncs/KDC1_STC_FAMILY_NOT_VALID

Resolving the problem

For the "address family invalid", ncs/KDC1_STC_FAMILY_NOT_VALID" there is not a way to disable these harmless messages without turning off all RAS1 messages.
They occur any time that two ends of a connection do not have exactly the same set of protocols enabled.
The message is issued each time a new thread makes a connection.

The message only appears when two ends of a connection do not match exactly.
Keep in mind that in addition to IP.UDP, IP.PIPE, and SNA, there is IP.SPIPE as well as all the IP6 protocols that are enabled by default.

The connections need to be the same between each point (for example, from agent to RTEMS, from RTEMS to HTEMS, etc). You would need to look at your KxxENV file for each and make sure that the KDC_FAMILIES parameter is set the same. However, even though they may look the same, there may be some protocols that have defaulted to a setting, thus causing you to get these messages.

For example, if you look at the KxxENV file on both ends of a connection, you may or may not see a protocol for ip6. If one end of the connection has an ipv6 stack, then ip6 will be enabled on the ipv6 stack end, and not on the other end of the connection. As an example:

kdc_families=ip.pipe use:y ip.udp use:y ip.spipe use:n sna use:n on both ends but one end has an ipv6 stack and the other does not .

On the end with an ipv6 stack, ip6.udp, ip6.pipe, and ip6.spipe will be enabled

So, the best practice would be to list all the protocols in the KDC_FAMILIES parameter:
kdc_families=ip.pipe use:y ip.udp use:y ip.spipe use:n sna use:n ip6.udp use:n ip6.pipe use:n ip6.spipe use:n

In order to see what you have enabled, you can look at the logs for each component (RTEMS, HTEMS, etc). The log format (for the TEMS) would be "*_ms-01.log". You would look for this type of information:

(*,"KDE1I_OpenTransportProvider") Transport opened: socket/ip.pipe (00A2) 127 2
(*,"KDE1I_OpenTransportProvider") Transport opened: socket/ip.tcp (0092) 125 2
(*,"KDE1I_OpenTransportProvider") Transport opened: socket/ip.ssl (00B2)123 2
(*,"KDE1I_OpenTransportProvider") Transport opened: socket/ip6.pipe (00A4) 121 3
(*,"KDE1I_OpenTransportProvider") Transport opened: socket/ip6.udp (0084) 118 3
(*,"KDE1I_OpenTransportProvider") Transport opened: socket/ip6.tcp (0094) 115 3
(*,"KDE1I_OpenTransportProvider") Transport opened: socket/ip6.spipe (00C4) 112 3
(*,"KDE1I_OpenTransportProvider") Transport opened: socket/ip6.ssl (00B4) 109 3

The KDC_FAMILIES parm that relates to the above log entry is this:

KDC_FAMILIES="ip.pipe port:1918 ip use:n ip.spipe use:n sna use:n HTTP:1920"

As you can see, since there happens to be an ipv6 interface available, those protocols show as opened in the log, even though they are not listed in the KDC_FAMILIES parameter.

The default on this parameter is use:y, and the format is:
protocol, options, protocol, options, etc.

Rate this page:

(0 users)Average rating

Document information

More support for:

Tivoli Components
ITM Tivoli Enterprise Mgmt Server V6

Software version:


Operating system(s):

Windows XP, i5/OS

Reference #:


Modified date:


Translate my page

Machine Translation

Content navigation