Not all KDC_FAMILIES configuration values added in a remote deploy.
This issue was reported by a customer running 6.3 FP03.
Each windows machine had a NT agent installed and by remote deploy a KLO agent was being installed and
However it was found once the agent KLO agent was insatlled, which it did successfully, it would not show up on the TEPS.
It was found to be be using localhost for the CT_CMSLIST so it was not connecting to the 2 RTEMS set in the NT agent configuration.
The settings in the MTEMS under Actions->Set Defaults For All Agents
were checked and changed to be a TEMS name rather than a localhost name, then the deploy did have the correct settings for one
RTEMS, but did not have the other RTEMS and had the connection as ip.pipe rather than the ip.spipe that was on the NT agent.
A further review of the NT agent file showed
KDC_FAMILIES=sna use:n ip6 use:n ip6.pipe use:n ip6:spipe use:n ip
use:n ip.pipe use:n ip.spipe port:3660 ephemeral:Y HTTP_CONSOLE:N
The issue was found to be the settings of HTTP and ephemeral.
6.3.0 FP3 does not support HTTP as a configurable parameter.
It supports it when coded manually, but is a problem in remote deploy.
6.3.0 FP4 is the first fixpack that supports HTTP_SERVER and that is the only parameter it supports for deployed agents.
None of the other HTTP information that is coded, is supported by any 6.3.0 release.
This behaviour is a permanent restriction at this time.
The 6.3.0 FP04 readme has the update:
Add support to disable HTTP and HTTPS ports during remote deploy,silent install/configuration, GUI install/configuration, and CLI
So the restriction is for any type of install.
Once the KDC_FAMILIES did not have the ephemeral:Y HTTP_CONSOLE:N set on the NT agent
the deploy of the KLO agent corectly configured the CT_CMSLIST and all other elements.
Both the agents then had to be configured for the extra KDC_FAMILIES settings.
Subscribe and follow us for all the latest information directly on your social feeds: