This is probably very obvious, and I have read some of the previous 
discussions on this topics but the answer given does not seem to work for me
at all, and the documentation is not obvious for me how to proceed further.

Scenario:  I have say 32 Linux boxes on the same core switch, no routing
involved,
but would like to partition them out into say 2 clusters of 16 machines each
and running gmetad on another Linux box, say XYZ.  I gave each cluster a
name as defined
in the /etc/gmond.conf file on the individual machine, and use as
data_source
in the /etc/gmetad.conf file on XYZ

data_source "cluster1" ... here I list the mane of the 16 machines on the
1st cluster
data_source "cluster2" ... here I list the name of the 16 machines on the
2nd cluster

1. Unless I also start gmond on XYZ, I won't be able to see anything on the
webfrontend.
   I don't want XYZ to be part of the monitored clusters.

2. Even when I start gmond on the "frontend" XYZ, if I use different
multicast IP
   in the /etc/gmond.conf for the 2 clusters, I won't be able to see
anything either,
   and would get socket php error.  Also it seems that when I use any
multicast 
   IP other than the default (239.2.11.71), I won't be able to see anything
corresponding
   to the non-default multicast IP address, and of course when I use the
same multicast 
   IP (the default one), then I wind up with 2 clusters each having all 32
machines
   which I don't want.

I know in previous reply, Steven Wagner has said that this should work, but
I am not able to get it to behave that way.  Am I missing something very
obvious ?

Thanks,
Phuong

Reply via email to