> Okay, since my first post didn't get an answer, maybe this one will. I
> have a setup where I have a separate server acting as the web front end
> to all my clusters (All SGI Altix boxes). I just added a new host to be
> monitored with a separate cluster name in gmond.conf and added the
> data_source to the web front end. Here's my problem:
>
> The new node is reporting itself as part of an existing cluster, when
> it's configured that way. Not only that, but telnetting to 8649 on that
> server reports the HOST NAME as another server on the network that's
> already monitored. In other words:
>
> <HOST NAME A> is shown on Server B and
> <HOST NAME B> is shown on Server A in the XML it reports.
>
> What's the deal? It's got to be something simple, but I've yet to
get it.
>
Probably you have a gmond configuration on each node that muticast the
cluster status to every node.
For example, if you have a configuration like this in the nodes:
-----
cluster {
name = "dummy_cluster"
}
udp_send_channel {
mcast_join = 239.2.11.71
port = 8649
}
udp_recv_channel {
mcast_join = 239.2.11.71
port = 8649
bind = 239.2.11.71
}
----
This means that every node know to belong to the "dummy_cluster", and
every gmond can return the status of the entire cluster because it knows
about every each other node (talking in the same multicast channel with
each other) if telled at the default 8649 TCP port.
You can find the solution unicasting the traffic between the node & itself:
----
udp_send_channel {
host = <hostname of 127.0.0.1>
port = 8649
}
udp_recv_channel {
port = 8649
}
---
In this way you can "simulate" a cluster of a single node, monitoring in
reality the single node.
