On Tue, Mar 31, 2009 at 06:41, Arun G <[email protected]> wrote: > Try assigning different udp port for broadcast in both the clusters.
Wont be enough. You'd also need them to be running in different chroot environments. > > Default port used is #udpport 694 > > Regards, > Arun. > >> From: Devraj Mukherjee <[email protected]> > >> Hi all, >> >> I am new to Hearbeat so please be kind :) >> >> I have successfully configure two machines to use heartbeat to cluster >> httpd. The two nodes are called etk-1 and etk-2. I am trying to >> configure another two machines to act as a separate cluster (on the >> same IP subnet). These two nodes are called radu-1 and radu-2. >> >> Obviously being a broadcast protocol radu-1 and radu-2 get these >> messages from etk-1 and I can't seem to get radu-1 and radu-2 to >> cluster (mostly probably because they are not getting the messages >> from the right nodes). >> >> Is it possible to have two sets of clusters in the one IP subnet? >> >> If yes what do I have to change so these clusters don't send messages >> to the wrong nodes. >> >> heartbeat[3745]: 2009/03/30_04:48:02 ERROR: process_status_message: >> bad node [etk-1] in message >> heartbeat[3745]: 2009/03/30_04:48:02 ERROR: MSG: Dumping message with 10 >> fields >> heartbeat[3745]: 2009/03/30_04:48:02 ERROR: MSG[0] : [t=NS_ackmsg] >> heartbeat[3745]: 2009/03/30_04:48:02 ERROR: MSG[1] : [dest= etk-2] >> heartbeat[3745]: 2009/03/30_04:48:02 ERROR: MSG[2] : [ackseq=1a9601] >> heartbeat[3745]: 2009/03/30_04:48:02 ERROR: MSG[3] : >> [(1)destuuid=0xdf38de8(37 28)] >> heartbeat[3745]: 2009/03/30_04:48:02 ERROR: MSG[4] : [src= etk-1] >> heartbeat[3745]: 2009/03/30_04:48:02 ERROR: MSG[5] : >> [(1)srcuuid=0xdf39248(36 27)] >> heartbeat[3745]: 2009/03/30_04:48:02 ERROR: MSG[6] : [hg=499a2a65] >> heartbeat[3745]: 2009/03/30_04:48:02 ERROR: MSG[7] : [ts=49cfb452] >> heartbeat[3745]: 2009/03/30_04:48:02 ERROR: MSG[8] : [ttl=3] >> >> >> -- >> "The secret impresses no-one, the trick you use it for is everything" >> - Alfred Borden (The Prestiege) >> > _______________________________________________ > Linux-HA mailing list > [email protected] > http://lists.linux-ha.org/mailman/listinfo/linux-ha > See also: http://linux-ha.org/ReportingProblems > _______________________________________________ Linux-HA mailing list [email protected] http://lists.linux-ha.org/mailman/listinfo/linux-ha See also: http://linux-ha.org/ReportingProblems
