<html>
<head>
<meta http-equiv="Content-Type" content="text/html; charset=utf-8">
</head>
<body dir="auto">
Correct, the edge cluster and the control cluster are very much separate entities apart from themselves and load balance within their own respective clusters.
<div><br>
</div>
<div>As long as clustering has been implemented correctly, in that scenario, the edge cluster would still be able to load balance and distribute resources within its own cluster (edge 1 answered the request but edge two transported the request to control 2
because control 1 was unreachable).</div>
<div><br>
</div>
<div>In that type of a degraded “brown out” scenario, you should manually put edge 1 in maintenance mode. Not sure if you could trigger maintenance mode via API but if you could, then its conceivable that one could write a polling “heart beat” script to detect
those unique “brown out” states and then automatically make edge 1 unserviceable by placing it into maintenance mode.<br>
<br>
<div dir="ltr">Thanks,</div>
<div dir="ltr"><br>
</div>
<div dir="ltr">Ryan</div>
<div dir="ltr"><br>
<blockquote type="cite">On Jan 29, 2020, at 12:59, ROZA, Ariel <Ariel.ROZA@la.logicalis.com> wrote:<br>
<br>
</blockquote>
</div>
<blockquote type="cite">
<div dir="ltr">
<meta name="Generator" content="Microsoft Word 15 (filtered medium)">
<style><!--
/* Font Definitions */
@font-face
{font-family:"Cambria Math";
panose-1:2 4 5 3 5 4 6 3 2 4;}
@font-face
{font-family:Calibri;
panose-1:2 15 5 2 2 2 4 3 2 4;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
{margin:0cm;
margin-bottom:.0001pt;
font-size:11.0pt;
font-family:"Calibri",sans-serif;}
a:link, span.MsoHyperlink
{mso-style-priority:99;
color:blue;
text-decoration:underline;}
.MsoChpDefault
{mso-style-type:export-only;
font-family:"Calibri",sans-serif;
mso-fareast-language:EN-US;}
@page WordSection1
{size:612.0pt 792.0pt;
margin:70.85pt 3.0cm 70.85pt 3.0cm;}
div.WordSection1
{page:WordSection1;}
--></style>
<!--[if gte mso 9]><xml>
<o:shapedefaults v:ext="edit" spidmax="1026" />
</xml><![endif]--><!--[if gte mso 9]><xml>
<o:shapelayout v:ext="edit">
<o:idmap v:ext="edit" data="1" />
</o:shapelayout></xml><![endif]-->
<div class="WordSection1">
<p class="MsoNormal"><span style="mso-fareast-language:EN-US">But without clustering, if Core1 fails, Edge1 will still be active and Jabber clients will still see Edge1 running and attempt to connect through it!<o:p></o:p></span></p>
<p class="MsoNormal"><span style="mso-fareast-language:EN-US"><o:p> </o:p></span></p>
<p class="MsoNormal"><b><span lang="ES">De:</span></b><span lang="ES"> cisco-voip <cisco-voip-bounces@puck.nether.net>
<b>En nombre de </b>Charles Goldsmith<br>
<b>Enviado el:</b> martes, 28 de enero de 2020 23:18<br>
<b>Para:</b> Lelio Fulgenzi <lelio@uoguelph.ca><br>
<b>CC:</b> cisco-voip@puck.nether.net<br>
<b>Asunto:</b> Re: [cisco-voip] Expressway Cluster failover for MRA...<o:p></o:p></span></p>
<p class="MsoNormal"><o:p> </o:p></p>
<div>
<p class="MsoNormal">We've built them as individual pairs (Edge/Core) and then use DNS to control which one goes where. Without the cluster, we know that Edge1 will always talk to Core1.<o:p></o:p></p>
<div>
<p class="MsoNormal"><o:p> </o:p></p>
</div>
<div>
<p class="MsoNormal">I get the feeling that clustering was always meant to be in the same DC, and for redundancy purposes in the same DC.<o:p></o:p></p>
</div>
<div>
<p class="MsoNormal"><o:p> </o:p></p>
</div>
<div>
<p class="MsoNormal">If you have two DC's, either a cluster at each DC, or just a pair at each DC, depending on the business needs.<o:p></o:p></p>
</div>
</div>
<p class="MsoNormal"><o:p> </o:p></p>
<div>
<div>
<p class="MsoNormal">On Tue, Jan 28, 2020 at 8:11 PM Lelio Fulgenzi <<a href="mailto:lelio@uoguelph.ca">lelio@uoguelph.ca</a>> wrote:<o:p></o:p></p>
</div>
<blockquote style="border:none;border-left:solid #CCCCCC 1.0pt;padding:0cm 0cm 0cm 6.0pt;margin-left:4.8pt;margin-right:0cm">
<div>
<div>
<p class="MsoNormal"><o:p> </o:p></p>
</div>
<p class="MsoNormal">How does no. 2 actually solve the problem of having to log back in?
<o:p></o:p></p>
<div>
<p class="MsoNormal"><o:p> </o:p></p>
</div>
<div>
<p class="MsoNormal">Is this a supported/suggested deployment method? <o:p></o:p></p>
<div>
<p class="MsoNormal"><o:p> </o:p></p>
</div>
<div>
<p class="MsoNormal">It’s been a while since I first looked at things and don’t recall things mentioning using the cluster name in the SRV records. <o:p></o:p></p>
</div>
<div>
<p class="MsoNormal"><o:p> </o:p></p>
</div>
<div>
<p class="MsoNormal">I’m intrigued. And interested!<o:p></o:p></p>
</div>
<div>
<p class="MsoNormal"><o:p> </o:p></p>
</div>
<div>
<p class="MsoNormal"><o:p> </o:p></p>
<div id="gmail-m_6232252904660164997AppleMailSignature">
<p class="MsoNormal"><i>-sent from mobile device-</i><o:p></o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal"><b>Lelio Fulgenzi, B.A.</b> | Senior Analyst<o:p></o:p></p>
<p class="MsoNormal">Computing and Communications Services | University of Guelph<o:p></o:p></p>
<p class="MsoNormal">Room 037 Animal Science & Nutrition Bldg | 50 Stone Rd E | Guelph, ON | N1G 2W1<o:p></o:p></p>
<p class="MsoNormal"><span style="color:black"><a href="tel:519-824-4120;56354" target="_blank">519-824-4120 Ext. 56354</a> | <a href="mailto:lelio@uoguelph.ca" target="_blank">lelio@uoguelph.ca</a></span><o:p></o:p></p>
<p class="MsoNormal"> <o:p></o:p></p>
<p class="MsoNormal"><span style="color:black"><a href="https://nam02.safelinks.protection.outlook.com/?url=http%3A%2F%2Fwww.uoguelph.ca%2Fccs&data=02%7C01%7C%7C28abee85602c4394504a08d7a4e5024d%7C84df9e7fe9f640afb435aaaaaaaaaaaa%7C1%7C0%7C637159175814864913&sdata=4Ty7ZYZ77QBJ6FCaao%2FQOZRlnNj7Oi4y%2BOBQzilxEIA%3D&reserved=0" originalsrc="http://www.uoguelph.ca/ccs" shash="Hix6lbk/JUtVxdlmIjFcaHnXDin014eIeyNt9/AWdQuNlbD9+ctEKB6vIySH2ZWnl+lT9/N/urldBU2e7mL1mnKatNFTaOAY3cz2YbpJ3k4Z6zPNl50AOS/Ztn+j44sL17omwvTS3PoynwRzpk3c7yZL4NKL9Amks2OfxJtbYzM=" target="_blank">www.uoguelph.ca/ccs</a> |
@UofGCCS on Instagram, Twitter and Facebook</span><o:p></o:p></p>
<p class="MsoNormal"> <o:p></o:p></p>
<p class="MsoNormal"><o:p></o:p></p>
</div>
<div>
<p class="MsoNormal" style="margin-bottom:12.0pt"><br>
On Jan 28, 2020, at 9:03 PM, Ryan Huff <<a href="mailto:ryanhuff@outlook.com" target="_blank">ryanhuff@outlook.com</a>> wrote:<o:p></o:p></p>
</div>
<blockquote style="margin-top:5.0pt;margin-bottom:5.0pt">
<div>
<p class="MsoNormal">1.) It used to be in previous versions that all cluster nodes could technically be active at any time and SRV weights and priorities could influence the path selection but not guarantee it end-to-end when all cluster nodes are up and running.<br>
<br>
I believe this behavior has changed/improved and I think you are supposed to be able to control that now with SRV weights and priorities, but I could be wrong. I haven’t played with Expressway clustering in a bit.<br>
<br>
2.) As far as the Jabber registration goes; what I’ve done before in the edge is have the collab-edge SRV point to the edge cluster FQDN as the target. Then I create round robin A records for the cluster FQDN (one resolving your each edge server). The for the
edge certs, just make sure the edge cluster fqdn is in the SAN.<br>
<br>
This way if one of the edge server goes down, the Jabber client is ultimately still trying to resolve the same MRA FQDN via SRV lookup (this a key to Jabber client failover for MRA).
<br>
<br>
Thanks,<br>
<br>
Ryan<br>
<br>
<br>
<o:p></o:p></p>
<blockquote style="margin-top:5.0pt;margin-bottom:5.0pt">
<p class="MsoNormal">On Jan 28, 2020, at 20:50, Jonathan Charles <<a href="mailto:jonvoip@gmail.com" target="_blank">jonvoip@gmail.com</a>> wrote:<o:p></o:p></p>
</blockquote>
<blockquote style="margin-top:5.0pt;margin-bottom:5.0pt">
<p class="MsoNormal"><o:p> </o:p></p>
</blockquote>
<blockquote style="margin-top:5.0pt;margin-bottom:5.0pt">
<p class="MsoNormal"><o:p></o:p></p>
</blockquote>
<blockquote style="margin-top:5.0pt;margin-bottom:5.0pt">
<p class="MsoNormal">We have two pairs of Expressway clusters (C/E) at two different locations (primary and DR)...<o:p></o:p></p>
</blockquote>
<blockquote style="margin-top:5.0pt;margin-bottom:5.0pt">
<p class="MsoNormal"><o:p> </o:p></p>
</blockquote>
<blockquote style="margin-top:5.0pt;margin-bottom:5.0pt">
<p class="MsoNormal">The cluster is up, however, we want to make sure that we are in Active/Standby.<o:p></o:p></p>
</blockquote>
<blockquote style="margin-top:5.0pt;margin-bottom:5.0pt">
<p class="MsoNormal"><o:p> </o:p></p>
</blockquote>
<blockquote style="margin-top:5.0pt;margin-bottom:5.0pt">
<p class="MsoNormal">Currently, we have one of our SRV records for collab-edge set at 5 (the backup is at 10) with the same weight.<o:p></o:p></p>
</blockquote>
<blockquote style="margin-top:5.0pt;margin-bottom:5.0pt">
<p class="MsoNormal"><o:p> </o:p></p>
</blockquote>
<blockquote style="margin-top:5.0pt;margin-bottom:5.0pt">
<p class="MsoNormal">The clustering guide says we should set the priority and weight on both SRV records the same, which will cause half of the registrations to go to the DR site. It is far away and has less capability.<o:p></o:p></p>
</blockquote>
<blockquote style="margin-top:5.0pt;margin-bottom:5.0pt">
<p class="MsoNormal"><o:p> </o:p></p>
</blockquote>
<blockquote style="margin-top:5.0pt;margin-bottom:5.0pt">
<p class="MsoNormal">How do we:<o:p></o:p></p>
</blockquote>
<blockquote style="margin-top:5.0pt;margin-bottom:5.0pt">
<p class="MsoNormal"><o:p> </o:p></p>
</blockquote>
<blockquote style="margin-top:5.0pt;margin-bottom:5.0pt">
<p class="MsoNormal">1 - Make sure the primary site handles all MRA registrations and the DR site is only used when the primary is down.<o:p></o:p></p>
</blockquote>
<blockquote style="margin-top:5.0pt;margin-bottom:5.0pt">
<p class="MsoNormal">2 = Make sure failover occurs automatically... currently Jabber users have to log out and back in to connect to the DR site.<o:p></o:p></p>
</blockquote>
<blockquote style="margin-top:5.0pt;margin-bottom:5.0pt">
<p class="MsoNormal"><o:p> </o:p></p>
</blockquote>
<blockquote style="margin-top:5.0pt;margin-bottom:5.0pt">
<p class="MsoNormal"><o:p> </o:p></p>
</blockquote>
<blockquote style="margin-top:5.0pt;margin-bottom:5.0pt">
<p class="MsoNormal">Thanks!<o:p></o:p></p>
</blockquote>
<blockquote style="margin-top:5.0pt;margin-bottom:5.0pt">
<p class="MsoNormal"><o:p> </o:p></p>
</blockquote>
<blockquote style="margin-top:5.0pt;margin-bottom:5.0pt">
<p class="MsoNormal"><o:p> </o:p></p>
</blockquote>
<blockquote style="margin-top:5.0pt;margin-bottom:5.0pt">
<p class="MsoNormal">Jonathan <o:p></o:p></p>
</blockquote>
<blockquote style="margin-top:5.0pt;margin-bottom:5.0pt">
<p class="MsoNormal"><o:p> </o:p></p>
</blockquote>
<blockquote style="margin-top:5.0pt;margin-bottom:5.0pt">
<p class="MsoNormal">_______________________________________________<o:p></o:p></p>
</blockquote>
<blockquote style="margin-top:5.0pt;margin-bottom:5.0pt">
<p class="MsoNormal">cisco-voip mailing list<o:p></o:p></p>
</blockquote>
<blockquote style="margin-top:5.0pt;margin-bottom:5.0pt">
<p class="MsoNormal"><a href="mailto:cisco-voip@puck.nether.net" target="_blank">cisco-voip@puck.nether.net</a><o:p></o:p></p>
</blockquote>
<blockquote style="margin-top:5.0pt;margin-bottom:5.0pt">
<p class="MsoNormal"><a href="https://nam02.safelinks.protection.outlook.com/?url=https%3A%2F%2Fpuck.nether.net%2Fmailman%2Flistinfo%2Fcisco-voip&data=02%7C01%7C%7C28abee85602c4394504a08d7a4e5024d%7C84df9e7fe9f640afb435aaaaaaaaaaaa%7C1%7C0%7C637159175814874918&sdata=2ULQiab5aIZYA90C1VDgpALdcRZjlsP1Vwx%2FCAam4Qs%3D&reserved=0" originalsrc="https://puck.nether.net/mailman/listinfo/cisco-voip" shash="iHEKALUPqNEW2RPZbs3HQ+IJDC2cuTUilf/up5sB+dd9TdJa1QzHb25DYoFL7j1vvnPl7QztjYAljalb9aYz+qZncT5eJ18J+/uFQeogyLigr2GJXfLNjPpTSlZdaDEuv+VezFF6bb/K1olGf1NX30xMJUeUBSqBEA/M2tMXgio=" target="_blank">https://nam04.safelinks.protection.outlook.com/?url=https%3A%2F%2Fpuck.nether.net%2Fmailman%2Flistinfo%2Fcisco-voip&data=02%7C01%7C%7C2f536d8162984707853908d7a45d8e24%7C84df9e7fe9f640afb435aaaaaaaaaaaa%7C1%7C0%7C637158594035084563&sdata=atRtIR8sWZ60Ja8akD6GjzBIgBNC8GSJjaOmu%2BTxmWw%3D&reserved=0</a><o:p></o:p></p>
</blockquote>
<p class="MsoNormal">_______________________________________________<br>
cisco-voip mailing list<br>
<a href="mailto:cisco-voip@puck.nether.net" target="_blank">cisco-voip@puck.nether.net</a><br>
<a href="https://nam02.safelinks.protection.outlook.com/?url=https%3A%2F%2Fpuck.nether.net%2Fmailman%2Flistinfo%2Fcisco-voip&data=02%7C01%7C%7C28abee85602c4394504a08d7a4e5024d%7C84df9e7fe9f640afb435aaaaaaaaaaaa%7C1%7C0%7C637159175814885738&sdata=IjY%2FpOIyx%2FZzOTxUuruUDEx9UHH%2Bl0QvfLsf8K2nqQI%3D&reserved=0" originalsrc="https://puck.nether.net/mailman/listinfo/cisco-voip" shash="SlG/gtvTQO0j8R2Q1yaMIrdNqpVvuew5ENOOVRY2BTZS5W2tqMSHGJCxw7p8kuTfDsNbrWpjbHK2eUblYBX9cpjSPvvOQxVxINP1EXYIUwsc2akedUunIa+xxTrdnQj3dkJUo1CxAXNnFqkhocxgEAZszZvo/ymRJPn5ULc+XyY=" target="_blank">https://puck.nether.net/mailman/listinfo/cisco-voip</a><o:p></o:p></p>
</div>
</blockquote>
</div>
</div>
</div>
<p class="MsoNormal">_______________________________________________<br>
cisco-voip mailing list<br>
<a href="mailto:cisco-voip@puck.nether.net" target="_blank">cisco-voip@puck.nether.net</a><br>
<a href="https://nam02.safelinks.protection.outlook.com/?url=https%3A%2F%2Fpuck.nether.net%2Fmailman%2Flistinfo%2Fcisco-voip&data=02%7C01%7C%7C28abee85602c4394504a08d7a4e5024d%7C84df9e7fe9f640afb435aaaaaaaaaaaa%7C1%7C0%7C637159175814894934&sdata=VNEu5UEe0dooSVh63Wbxx4xQope8qS0oV5xlDOZat%2FA%3D&reserved=0" originalsrc="https://puck.nether.net/mailman/listinfo/cisco-voip" shash="PAjq6uzdUGV2k9hZc1rImHgKQ6AC2XxTqTXm7HkEKl66AGpWzfS/18BOjo4Tx/A/S2Lq6f8JckwEojTcikG4lvcsSs/l1poGHjN2/YEiy0OpANZp1Hrm7bwJGKhESB3u4zjhpXg5N4Od0QP1la9DoZIl0bUt/07j+BXys40lIsk=" target="_blank">https://puck.nether.net/mailman/listinfo/cisco-voip</a><o:p></o:p></p>
</blockquote>
</div>
</div>
<span>_______________________________________________</span><br>
<span>cisco-voip mailing list</span><br>
<span>cisco-voip@puck.nether.net</span><br>
<span>https://nam02.safelinks.protection.outlook.com/?url=https%3A%2F%2Fpuck.nether.net%2Fmailman%2Flistinfo%2Fcisco-voip&data=02%7C01%7C%7C28abee85602c4394504a08d7a4e5024d%7C84df9e7fe9f640afb435aaaaaaaaaaaa%7C1%7C0%7C637159175814944977&sdata=8geL2Lp2ksdsbzZ0lppv5z6Eub6QbdAGjiAjtsTshNY%3D&reserved=0</span><br>
</div>
</blockquote>
</div>
</body>
</html>