<html xmlns:v="urn:schemas-microsoft-com:vml" xmlns:o="urn:schemas-microsoft-com:office:office" xmlns:w="urn:schemas-microsoft-com:office:word" xmlns:m="http://schemas.microsoft.com/office/2004/12/omml" xmlns="http://www.w3.org/TR/REC-html40">
<head>
<meta http-equiv="Content-Type" content="text/html; charset=utf-8">
<meta name="Generator" content="Microsoft Word 15 (filtered medium)">
<!--[if !mso]><style>v\:* {behavior:url(#default#VML);}
o\:* {behavior:url(#default#VML);}
w\:* {behavior:url(#default#VML);}
.shape {behavior:url(#default#VML);}
</style><![endif]--><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;}
@font-face
{font-family:Consolas;
panose-1:2 11 6 9 2 2 4 3 2 4;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
{margin:0in;
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;}
pre
{mso-style-priority:99;
mso-style-link:"HTML Preformatted Char";
margin:0in;
margin-bottom:.0001pt;
font-size:10.0pt;
font-family:"Courier New";}
span.HTMLPreformattedChar
{mso-style-name:"HTML Preformatted Char";
mso-style-priority:99;
mso-style-link:"HTML Preformatted";
font-family:Consolas;}
span.EmailStyle21
{mso-style-type:personal-reply;
font-family:"Calibri",sans-serif;
color:windowtext;}
.MsoChpDefault
{mso-style-type:export-only;
font-size:10.0pt;}
@page WordSection1
{size:8.5in 11.0in;
margin:1.0in 1.0in 1.0in 1.0in;}
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]-->
</head>
<body lang="EN-US" link="blue" vlink="purple">
<div class="WordSection1">
<pre><span style="color:black">>>><i> 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></i></span></pre>
<p class="MsoNormal">The cluster shares a common DB and distribute the calls across the cluster. If you’re going to use SRV records to try this, only use different priorities if you have different clusters allowing failover from one primary cluster to another
(secondary) cluster. <o:p></o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal">Here is what we just deployed to deal with the added load of remote workers. I have a couple of lessons learned. We recently rebuilt our entire Expressway C and E cluster dedicated to MRA. <o:p></o:p></p>
<p class="MsoNormal">We weighted them the same but have 2C’s and 2E’s in DC1 and in DC2 we put their peers, 2 additional 2C’s and 2E’s. doesn’t matter which DC is impacted we are covered with 1 cluster.<o:p></o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal">We created a cluster of 4 MRA C and E “Large VM’s” for a total of 10,000 registrations. I would avoid Small VMs (because there's no capacity gain from clustering 2 or more Small VMs this is why we had to rebuild with Large VM).<o:p></o:p></p>
<p class="MsoNormal">If MRA endpoints lose connection to their initial peer, they automatically re-register to another one in the cluster. MRA call preservation is out the window and you will have to place or take another call. Failover to the next server was
seamless during testing (Maintenance mode or rebooting the expressway) by the time the call drops and I place another call my system has already registered to a different peer on the cluster.<o:p></o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal">Respectfully,<o:p></o:p></p>
<p class="MsoNormal">Keith Croft | Collaboration Engineer – IT Infrastructure & Security<o:p></o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<div style="border:none;border-top:solid #B5C4DF 1.0pt;padding:3.0pt 0in 0in 0in">
<p class="MsoNormal"><b><span style="font-size:12.0pt;color:black">From: </span></b><span style="font-size:12.0pt;color:black">cisco-voip <cisco-voip-bounces@puck.nether.net> on behalf of "Mark H. Turpin" <mturpin@covene.com><br>
<b>Date: </b>Tuesday, July 7, 2020 at 2:41 PM<br>
<b>To: </b>Gerence Guan <cisco.guan@gmail.com>, Anthony Holloway <avholloway+cisco-voip@gmail.com><br>
<b>Cc: </b>cisco-voip voyp list <cisco-voip@puck.nether.net><br>
<b>Subject: </b>Re: [cisco-voip] Expressway Cluster failover for MRA<o:p></o:p></span></p>
</div>
<div>
<p class="MsoNormal"><o:p> </o:p></p>
</div>
<div>
<p class="MsoNormal"><span style="font-size:12.0pt;color:black">I don't believe running unclustered is supported though. <o:p></o:p></span></p>
</div>
<div>
<p class="MsoNormal"><span style="font-size:12.0pt;color:black"><o:p> </o:p></span></p>
</div>
<div>
<p class="MsoNormal"><span style="font-size:12.0pt;color:black">The way I interpreted this section in Unsupported Deployments: <a href="https://nam05.safelinks.protection.outlook.com/?url=https%3A%2F%2Fwww.cisco.com%2Fc%2Fen%2Fus%2Ftd%2Fdocs%2Fvoice_ip_comm%2Fexpressway%2Fconfig_guide%2FX12-6%2Fexwy_b_mra-expressway-deployment-guide%2Fexwy_b_mra-expressway-deployment-guide_chapter_011.html&data=02%7C01%7CKeith.Croft%40wwt.com%7C9a9e4931a0d24fe82f0408d822adbe98%7Ca2d8e6b4e26e44218f3dec288c827c7d%7C1%7C0%7C637297476905880278&sdata=hOI%2F7zXPUoOhGUecWCtVs3n6IE92Q%2B1BH6tpaL84Mmg%3D&reserved=0">https://www.cisco.com/c/en/us/td/docs/voice_ip_comm/expressway/config_guide/X12-6/exwy_b_mra-expressway-deployment-guide/exwy_b_mra-expressway-deployment-guide_chapter_011.html</a> read
to me like you needed to have your C's and E's clustered for your UC zones.<o:p></o:p></span></p>
</div>
<div>
<p class="MsoNormal"><span style="font-size:12.0pt;color:black"><o:p> </o:p></span></p>
</div>
<div>
<p class="MsoNormal"><span style="font-size:12.0pt;color:black">That's just my interpretation, though, I might be wrong.<o:p></o:p></span></p>
</div>
<div>
<p class="MsoNormal"><span style="font-size:12.0pt;color:black"><o:p> </o:p></span></p>
</div>
<div>
<p class="MsoNormal"><span style="font-size:12.0pt;color:black"><o:p> </o:p></span></p>
</div>
<div>
<div>
<p class="MsoNormal"><span style="font-size:12.0pt;color:black"><o:p> </o:p></span></p>
</div>
<div class="MsoNormal" align="center" style="text-align:center">
<hr size="0" width="100%" align="center">
</div>
<div id="divRplyFwdMsg">
<p class="MsoNormal"><b><span style="color:black">From:</span></b><span style="color:black"> cisco-voip <cisco-voip-bounces@puck.nether.net> on behalf of Gerence Guan <cisco.guan@gmail.com><br>
<b>Sent:</b> Monday, July 6, 2020 8:04 PM<br>
<b>To:</b> Anthony Holloway <avholloway+cisco-voip@gmail.com><br>
<b>Cc:</b> cisco-voip voyp list <cisco-voip@puck.nether.net><br>
<b>Subject:</b> Re: [cisco-voip] Expressway Cluster failover for MRA</span> <o:p>
</o:p></p>
<div>
<p class="MsoNormal"> <o:p></o:p></p>
</div>
</div>
<div>
<p class="MsoNormal" style="margin-bottom:12.0pt">*** EXTERNAL EMAIL - DO NOT CLICK LINKS ***
<o:p></o:p></p>
<div>
<div>
<p class="MsoNormal">@Brian<o:p></o:p></p>
<div>
<p class="MsoNormal">Clustering is not that critical. As long as the Jabber can register back via the DR without any manual system level changes. It is acceptable even if users need to logout and login jaber again.<o:p></o:p></p>
</div>
<div>
<p class="MsoNormal"><o:p> </o:p></p>
</div>
<div>
<p class="MsoNormal">@Anthony<o:p></o:p></p>
</div>
<div>
<p class="MsoNormal">it would be good if someone has that table. It will help a lot.<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>
<div>
<p class="MsoNormal"><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>
<div>
<p class="MsoNormal"><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>
<div>
<p class="MsoNormal"><o:p> </o:p></p>
</div>
</div>
<p class="MsoNormal"><o:p> </o:p></p>
<div>
<div>
<p class="MsoNormal">On Tue, Jul 7, 2020 at 1:57 AM Anthony Holloway <<a href="mailto:avholloway%2Bcisco-voip@gmail.com" target="_blank">avholloway+cisco-voip@gmail.com</a>> wrote:<o:p></o:p></p>
</div>
<blockquote style="border:none;border-left:solid #CCCCCC 1.0pt;padding:0in 0in 0in 6.0pt;margin-left:4.8pt;margin-right:0in">
<div>
<p class="MsoNormal">Brian, <o:p></o:p></p>
<div>
<p class="MsoNormal"><o:p> </o:p></p>
</div>
<div>
<p class="MsoNormal">This wouldn't support failover in all scenarios though, correct? E.g., CUCM sub to sub failover.<o:p></o:p></p>
</div>
<div>
<p class="MsoNormal"><o:p> </o:p></p>
</div>
<div>
<p class="MsoNormal">Does anyone have a nice table of failover scenarios covered and not covered by expressway clustering versus not?<o:p></o:p></p>
</div>
</div>
<p class="MsoNormal"><o:p> </o:p></p>
<div>
<div>
<p class="MsoNormal">On Mon, Jul 6, 2020 at 9:29 AM Brian Meade <<a href="mailto:bmeade90@vt.edu" target="_blank">bmeade90@vt.edu</a>> wrote:<o:p></o:p></p>
</div>
<blockquote style="border:none;border-left:solid #CCCCCC 1.0pt;padding:0in 0in 0in 6.0pt;margin-left:4.8pt;margin-right:0in">
<div>
<p class="MsoNormal">I would not use Expressway clustering and just have 2 different C/E pairs with different SRV Weights/Priorities instead.<o:p></o:p></p>
</div>
<p class="MsoNormal"><o:p> </o:p></p>
<div>
<div>
<p class="MsoNormal">On Mon, Jul 6, 2020 at 3:17 AM Gerence Guan <<a href="mailto:cisco.guan@gmail.com" target="_blank">cisco.guan@gmail.com</a>> wrote:<o:p></o:p></p>
</div>
<blockquote style="border:none;border-left:solid #CCCCCC 1.0pt;padding:0in 0in 0in 6.0pt;margin-left:4.8pt;margin-right:0in">
<div>
<p class="MsoNormal">Hi Everyone. <o:p></o:p></p>
<div>
<p class="MsoNormal"><o:p> </o:p></p>
</div>
<div>
<p class="MsoNormal">I was googling the answer for MRA failover and found this maillist.<o:p></o:p></p>
</div>
<div>
<p class="MsoNormal">Got a similar setup as Jonathan's environment. <o:p></o:p></p>
</div>
<div>
<p class="MsoNormal">Having a pair of expressway C&E in primary DC, and planning to setup another pair of expressway C&E in the DR site. All MRA should go via primary DC, only use DR site when primary is down.<o:p></o:p></p>
</div>
<div>
<p class="MsoNormal"><o:p> </o:p></p>
</div>
<div>
<p class="MsoNormal">Can I achieve this with different priorities in SRV? Anyone tested or make it working?<o:p></o:p></p>
</div>
<div>
<p class="MsoNormal"><o:p> </o:p></p>
</div>
<div>
<p class="MsoNormal">Best Regards,<o:p></o:p></p>
</div>
<div>
<p class="MsoNormal">Guan<o:p></o:p></p>
</div>
<div>
<p class="MsoNormal"><o:p> </o:p></p>
</div>
<div>
<pre style="white-space:pre-wrap"><span style="color:black">>>><i> On Jan 28, 2020, at 8:49 PM, Jonathan Charles <<a href="https://nam05.safelinks.protection.outlook.com/?url=https%3A%2F%2Fpuck.nether.net%2Fmailman%2Flistinfo%2Fcisco-voip&data=02%7C01%7CKeith.Croft%40wwt.com%7C9a9e4931a0d24fe82f0408d822adbe98%7Ca2d8e6b4e26e44218f3dec288c827c7d%7C1%7C0%7C637297476905890273&sdata=%2BiCz8XEyBOA1pd0l%2BgRSxoNuvD5CIAmTq2oYxieMxbo%3D&reserved=0" target="_blank">jonvoip at gmail.com</a>> wrote:<o:p></o:p></i></span></pre>
<pre><span style="color:black">>>><i><o:p> </o:p></i></span></pre>
<pre><span style="color:black">>>><i> We have two pairs of Expressway clusters (C/E) at two different<o:p></o:p></i></span></pre>
<pre><span style="color:black">>>><i> locations (primary and DR)...<o:p></o:p></i></span></pre>
<pre><span style="color:black">>>><i><o:p> </o:p></i></span></pre>
<pre><span style="color:black">>>><i> The cluster is up, however, we want to make sure that we are in<o:p></o:p></i></span></pre>
<pre><span style="color:black">>>><i> Active/Standby.<o:p></o:p></i></span></pre>
<pre><span style="color:black">>>><i><o:p> </o:p></i></span></pre>
<pre><span style="color:black">>>><i> Currently, we have one of our SRV records for collab-edge set at 5 (the<o:p></o:p></i></span></pre>
<pre><span style="color:black">>>><i> backup is at 10) with the same weight.<o:p></o:p></i></span></pre>
<pre><span style="color:black">>>><i><o:p> </o:p></i></span></pre>
<pre><span style="color:black">>>><i> The clustering guide says we should set the priority and weight on both<o:p></o:p></i></span></pre>
<pre><span style="color:black">>>><i> SRV records the same, which will cause half of the registrations to go to<o:p></o:p></i></span></pre>
<pre><span style="color:black">>>><i> the DR site. It is far away and has less capability.<o:p></o:p></i></span></pre>
<pre><span style="color:black">>>><i><o:p> </o:p></i></span></pre>
<pre><span style="color:black">>>><i> How do we:<o:p></o:p></i></span></pre>
<pre><span style="color:black">>>><i><o:p> </o:p></i></span></pre>
<pre><span style="color:black">>>><i> 1 - Make sure the primary site handles all MRA registrations and the DR<o:p></o:p></i></span></pre>
<pre><span style="color:black">>>><i> site is only used when the primary is down.<o:p></o:p></i></span></pre>
<pre><span style="color:black">>>><i> 2 = Make sure failover occurs automatically... currently Jabber users<o:p></o:p></i></span></pre>
<pre><span style="color:black">>>><i> have to log out and back in to connect to the DR site.<o:p></o:p></i></span></pre>
<pre><span style="color:black">>>><o:p> </o:p></span></pre>
</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://nam05.safelinks.protection.outlook.com/?url=https%3A%2F%2Fpuck.nether.net%2Fmailman%2Flistinfo%2Fcisco-voip&data=02%7C01%7CKeith.Croft%40wwt.com%7C9a9e4931a0d24fe82f0408d822adbe98%7Ca2d8e6b4e26e44218f3dec288c827c7d%7C1%7C0%7C637297476905890273&sdata=%2BiCz8XEyBOA1pd0l%2BgRSxoNuvD5CIAmTq2oYxieMxbo%3D&reserved=0" target="_blank">https://puck.nether.net/mailman/listinfo/cisco-voip</a><o:p></o:p></p>
</blockquote>
</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://nam05.safelinks.protection.outlook.com/?url=https%3A%2F%2Fpuck.nether.net%2Fmailman%2Flistinfo%2Fcisco-voip&data=02%7C01%7CKeith.Croft%40wwt.com%7C9a9e4931a0d24fe82f0408d822adbe98%7Ca2d8e6b4e26e44218f3dec288c827c7d%7C1%7C0%7C637297476905900265&sdata=9GSS1uujt2hn%2Fks%2BxbBO12fZgGdHbJBdDBpcn5xj%2FOk%3D&reserved=0" target="_blank">https://puck.nether.net/mailman/listinfo/cisco-voip</a><o:p></o:p></p>
</blockquote>
</div>
</blockquote>
</div>
</div>
</div>
</div>
</div>
</body>
</html>