I have created a simple task that runs an action on a relevant host (Linux). I select it and click ‘Take Action’ and nothing happens- it just stays open and 0% complete. What am I missing? I just want to click Take Action and have it run now, not i hour from now, not two days from now. I’ve tried setting the action to start and end within a time frame and sometimes the action will expire with nothing happening. If I restart the BES agent on my host, THEN the action runs.
Problem might be that UDP communication towards the target BES agent is blocked.
This might be due to a Company’s firewall as well as a firewall local to the BES agent system.
BigFix uses UDP communications to notify BES agents of new content to process.
As BES agents are restarted, they immediately synchronize with the upper level (Relay or Server), and so if there’s new content to process (e.g. a new action to run), they find it right away.
1 Like
also please creating exceptions in antivirus to bigfix path some time its blocking
https://www-01.ibm.com/support/docview.wss?uid=swg21616338
Regards,
Shaban
Thanks for the replies- I verified, there are no firewall rules blocking UDP or host-based anti-virus software in use.
You can easily confirm that the BigFix Client is properly receiving notifications via either the Client log (look for lines containing things like ‘GatherHashMV command received’), or even via property/relevance (ex: https://bigfix.me/relevance/details/3021681). Here’s an additional topic on this to potentially review: TCP/UDP port query
If you find that notifications are not getting through for some reason, you might consider command-polling, or even the new persistent connections feature introduced with 9.5.11: https://www.ibm.com/support/knowledgecenter/en/SSQL82_9.5.0/com.ibm.bigfix.doc/Platform/Config/c_persistenconn.html
1 Like
It turns out I was wrong- a host-based firewall rule was blocking UDP from the relay. Thanks for the replies.
2 Likes