Why are my BigFix Clients not choosing their specified BigFix Relay?
Reasons why the TEM Clients are not choosing a specified Relay.
Resolving the problem
During manual or automatic BigFix Relay selection the BigFix Clients will attempt to connect to the BigFix Relay at http://relayname:port/cgi-bin/bfenterprise/clientregister.exe?requesttype=version (8.2 and below) or http://relayname:port/cgi-bin/bfenterprise/clientregister.exe?RequestTypeRegisterMe60 (version 9 and above) . If they cannot make this connection, they cannot use the BigFix Relay.
There are a few common reasons why clients might not correctly find a relay:
- The clients cannot resolve the DNS name of the relays - Many times with this type of issue, the BigFix Clients cannot resolve the DNS name of the BigFix Relay and therefore cannot use the BigFix Relay. The BigFix Relay reports its DNS name to the BigFix Server and that list is distributed to the BigFix Clients. You can see the DNS name of the BigFix Relay by looking at the "DNS Name" in the BigFix Console (right click on the column headings if you cannot see this property).
If the DNS name of the BigFix Relay is unresolvable by the BigFix Clients because the DNS name is not fully qualified or because of another DNS issue, you can override the BigFix Relay's DNS name by changing the "_BESClient_Relay_NameOverride" setting on the BigFix Relay computer to return a different DNS name or an IP address. More information on how to do this is available at:
BigFix Configuration Settings..
- The TEM Clients are not set to use a BigFix Relay - By default, the BigFix Clients will connect to the main TEM Server. You will need to either manually point the BigFix Clients at a BigFix Relay or set the TEM Clients to automatically find their closest TEM Relay. More information on how to do this is available in the TEM Administrators Guide at:
TEM Administrators Guide.
- A TEM Client is blocked from contacting the TEM Relay because of a firewall or NAT - The TEM Client connects to the TEM Relay using HTTP on the specified port number (default is 52311). Verify that the TEM Client computer can make a connection to the TEM Relay by going to the TEM Client computer and pasting http://relayname:port/cgi-bin/bfenterprise/clientregister.exe?requesttype=version into a browser. If you see a version number, then the TEM Client can properly connect to the TEM Relay. If you receive an HTTP error, then you will need to determine why the TEM Client cannot contact the TEM Relay.
- The TEM Relay is not correctly installed - If the TEM Relay is not correctly installed, the TEM Clients won't be able to connect to it. You can attempt to connect to the TEM Relay by pasting http://relayname:port/cgi-bin/bfenterprise/clientregister.exe?requesttype=version into a browser. If you do not see a version number returned in the browser, you should try to reinstall the TEM Relay to see if that fixes the problem.
- ICMP is blocked between TEM Clients and TEM Relays and the TEM Clients are using automatic relay selection - The TEM Clients use ICMP to determine how many network hops are between the TEM Client and the TEM Relay. If ICMP is blocked, the TEM Clients will not be able to figure out their best TEM Relay and they will randomly choose a TEM Relay to use. Ping the TEM Relay from the TEM Client computer to see if ICMP is blocked.
Contact IBM if you continue to have a problem.
Translate this page: