[Spread-users] Spread Config Azure VMs

[John Lane Schultz]

Hi Ulysses, 

I agree with Ed that most public clouds support neither broadcast nor multicast, so you will have to configure Spread to only use unicast addresses, which is fine for small configurations.

But I think something deeper is going wrong here with your underlying networking.

Even in your original configuration file, you used singleton daemon segments.  In that case, I believe the segment address is effectively ignored regardless of what it is: a broadcast address, multicast address, loopback address, completely wrong address, etc.  So, changing the segment address from one thing to another while using singleton segments should have had no effect.

I would verify first that you can run some test programs on those two addresses on those two ports and get bidirectional UDP traffic working on your base port (14823), base port + 1 (14824), and base port + 2 (14825) if you want to use spmonitor.

My hunch is that something is not working correctly in your underlying networking for those addresses and those ports.

John

On Jan 21, 2020, at 4:17 PM, Grant, Ulysses S <Ulysses.Grant at chevron.com> wrote:

Thanks Edward,
 
Unfortunately the same issue with the loopback address. Being that the new recommended configuration, from Openlink, is uni vs multicast would this be an issue?
 
From: Edward Holyat <ed.holyat at iongroup.com> 
Sent: Tuesday, January 21, 2020 12:46 PM
To: Grant, Ulysses S <Ulysses.Grant at chevron.com>; spread-users at lists.spread.org
Subject: [**EXTERNAL**] RE: Spread Config Azure VMs
 
Change the broadcast 10.74.84.255 to local loopback address 127.0.0.1, Azure doesn’t allow broadcast
 
Spread_Segment  127.0.0.1:14823 {
 
                endur-dspd01   10.74.84.252
}
 
Spread_Segment  127.0.0.1:14823 {
 
                endur-dspd00   10.74.84.253
}
 
Thanks,
 
Ed Holyat
Principal Cloud Architect
 
<image001.png> <http://www.openlink.com/>    <image002.png> <https://www.linkedin.com/company/openlink-financial>  <image003.png> <https://twitter.com/OpenLink_News>  <image004.png> <https://www.openlink.com/en/inside-openlink/awards/>
<image006.png>
 

Office: +1-516-394-1231
 
From: Grant, Ulysses S <Ulysses.Grant at chevron.com <mailto:Ulysses.Grant at chevron.com>> 
Sent: Tuesday, January 21, 2020 11:54 AM
To: spread-users at lists.spread.org <mailto:spread-users at lists.spread.org>
Subject: [Spread-users] Spread Config Azure VMs
 
CAUTION: [EXTERNAL Email]
 
Hello,
 
I am having issues with spread communicating on two Azure server 16 boxes. Each box only shows one membership and each individual box as the leader. I’ve run into this issue previously but can’t recall what was done to resolve this particular issue. I have attached the information from each box and the spread.conf configuration file. I can communicate between both boxes as they are in the same resource group and have no firewall in between them.
 
Thanks
 
Ulysses S. Grant, IV
<spread.conf>_______________________________________________
Spread-users mailing list
Spread-users at lists.spread.org
http://lists.spread.org/mailman/listinfo/spread-users

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.spread.org/pipermail/spread-users/attachments/20200124/08a006c3/attachment.html>