[Spread-users] Spread Config Azure VMs

[Grant, Ulysses S]

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

[cid:image009.png at 01D33124.4DD206F0]<http://www.openlink.com/>    [cid:image011.png at 01D33124.4DD206F0] <https://www.linkedin.com/company/openlink-financial>   [cid:image013.png at 01D33124.4DD206F0] <https://twitter.com/OpenLink_News>   [cid:image015.png at 01D33124.4DD206F0] <https://www.openlink.com/en/inside-openlink/awards/>




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
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.spread.org/pipermail/spread-users/attachments/20200121/42c37ede/attachment-0001.html>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: image001.png
Type: image/png
Size: 2542 bytes
Desc: image001.png
URL: <http://lists.spread.org/pipermail/spread-users/attachments/20200121/42c37ede/attachment-0006.png>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: image002.png
Type: image/png
Size: 1110 bytes
Desc: image002.png
URL: <http://lists.spread.org/pipermail/spread-users/attachments/20200121/42c37ede/attachment-0007.png>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: image003.png
Type: image/png
Size: 1128 bytes
Desc: image003.png
URL: <http://lists.spread.org/pipermail/spread-users/attachments/20200121/42c37ede/attachment-0008.png>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: image004.png
Type: image/png
Size: 1162 bytes
Desc: image004.png
URL: <http://lists.spread.org/pipermail/spread-users/attachments/20200121/42c37ede/attachment-0009.png>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: image005.png
Type: image/png
Size: 174 bytes
Desc: image005.png
URL: <http://lists.spread.org/pipermail/spread-users/attachments/20200121/42c37ede/attachment-0010.png>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: image006.png
Type: image/png
Size: 178 bytes
Desc: image006.png
URL: <http://lists.spread.org/pipermail/spread-users/attachments/20200121/42c37ede/attachment-0011.png>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: spread.conf
Type: application/octet-stream
Size: 444 bytes
Desc: spread.conf
URL: <http://lists.spread.org/pipermail/spread-users/attachments/20200121/42c37ede/attachment-0001.obj>