Bare Metal Profile - Multicast

Hello BigFix Forums,

I’m trying to use multicast on a bare metal profile and I’m using a Closed Group.
The reason for this is that I also want the BMP to deploy when there’s only one client connecting to the server, I can’t let the server wait for the average clients if I only deploy one. (I don’t know how this setting does work though).
Using the closed group, I use the following values:

Multicast mode: Probe and Fallback to Unicast
Targets: 16 Clients
Wait: 5 minutes
Min Clients: 1 Client(s)

However, while deploying only one machine; the deployment ‘hangs’ on Getting files ready.
If I cancel the deployment and restart the machine, the deployment suddenly does continue after 5 minutes.

Is there a real minimum of 2 machines to this setting? And, how does the Open Group with Average Machines work? Has it a default timeout, does it wait for X machines, give or take 2?

I’d love to hear,

Thanks in advance.

Hi

I try to explain how the Closed Group works.
When the Close Group is selected, at deployment time the application waits for the first conditions that occurs between "Number of targets in group " and the “Wait for targets up to minutes”. In your case the multicast distribution will start when 16 targets join the group OR when a time of 5 minutes have elapsed since the first target joined the group. After the group is closed, the “Minimum number of targets in group” is evaluated. If the number of group members (targets that joined the group) is less than the specified value then your distribution will be deployed via unicast.

I hope this clarifies a bit
Viviana

So, If I understand correctly: the Minimum Clients has to be set to 2?, so that way the Single client will fall back to Unicast?

Yes. If your intention is that a single client is deployed leveraging a unicast distribution, you need to set Minimum Clients to 2.

1 Like