IBM Director not seeing agents 1

[GordoSK]

Hello,
There is a handful of agents that my install of Director 4.12 (and 4.10) cannot see. Is there anything I can do to confirm communication between the server and agent besided trying to do a "Discover IBM Director Systems".

thanks
chris

 

[catorze]

By default, IBM Director Server will only discover Agents in the same subnet. If the Agents you can't discover are not in the same subnet, you will have to define Relay Agents (one for each remote subnet) via Options > Discovery Preferences > System Discovery (IP) from the Director Console. The Relay Agent you define should be a native managed Agent that is usually running. If the Agents are on the other side of a router from the Director Server, you will need to make sure the correct UDP ports are open. The IBM Director documentation has the ports.

Some other common pitfalls are systems that were imaged (incorrectly) thus having more than one system with the same SID (TWGMachID), and in large environments (network segments) with a lot of traffic, having too short a network timeout setting (default is 15 sec) - try raising to 30-45 seconds, and restarting the Agent (net stop TWGIPC, net start TWGIPC).

 

[ddlink]

I have the same problem as Chris does.
@Catorze,

how do you install a native managed Agent? Or is that just a normally installed Agent that you point on with RELAY enabled?

How do you raise the time to 30-45 seconds?

Thanks!

 

[GordoSK]

Thank you catorze, for pointing me to the correct solution. On page 228 of dir411_sysmgt.pdf

If cloning, make sure that IBM Director Agent, which is installed on the
server to be used as the image, has never been started.
If you have started your server to confirm installation of IBM Director
Agent, perform the appropriate procedure:
Linux: Edit the following file:
/opt/IBM/director/data/ServiceNodeLocal.properties
Remove the value after the equal symbol on the following line:
ipc.UID=
Also, delete the following file:
/etc/TWGAgent/TWGagent.uid
Windows: Remove the following registry key:
HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\ControlComputerName\ComputerName\TWGMachineID
Also, delete the following file:
$(Director install path)\data\twgmach.id
For example, C:\Program Files\IBM\director\data\twgmach.id

********************
So I removed the reg entry, and deleted the file, restarted the agent and was able to correctly discover the agent via the Director console.

ddlink, you can configure the agent using the utility twfipccf.exe from the director/bin directory.

thanks again
chris

 

[catorze]

Yes. a "native" managed Agent is a system that is running IBM Director Agent. If using it as a Relay Agent, choose a system that's usually running. TWGIPCCF.EXE is the Network Driver Configuration executable. If you make changes here, you have to stop and restart the Director Support Program (net stop/net start TWGIPC).