MCollective across subnets

[Jonathan Gazeley]

Hi peeps,

I recently installed MCollective using the puppetlabs module. I'm just
beginning to find my way around it but I've noticed that quite a few of
my nodes aren't appearing in MCollective. The nodes are split across 4
subnets (three publicly address, one private. Two of the public ones
also use IPv6). The only nodes showing up are in the v6-enabled subnets
(which also have v4). The MCollective broker is in one of these subnets.
The nodes in the other two subnets don't show up at all when I look at
the inventory on my MCollective broker.

My question is hopefully a user error, but I'm not entirely clear on how
my MCollective server figures out which nodes to talk to. I've had a
look at the docs and I can't really see anything that helps. Can anyone
suggest what's causing my problem? Hopefully it's just my inexperience
with MCollective and I've missed an option somewhere.

Cheers,
Jonathan

[José Luis Ledesma]

Every node has a persistent TCP connection with the middleware server port 61613.

First of all check this. Also check that the servers are time synchronize, mcollective is very sensible to time differences.

Hth,

--
You received this message because you are subscribed to the Google Groups "Puppet Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email to puppet-users+unsubscribe@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/puppet-users/5379E4A4.3010306%40bristol.ac.uk.
For more options, visit https://groups.google.com/d/optout.

[Jonathan Gazeley]

On 19/05/14 13:51, José Luis Ledesma wrote:
> Every node has a persistent TCP connection with the middleware server
> port 61613.

Thanks, that's what I needed to know. I had set all the nodes to listen
on 61613 for incoming connections from the middleware server.

Cheers,
Jonathan