<html>
<head>
<meta http-equiv="Content-Type" content="text/html; charset=utf-8">
</head>
<body dir="auto">
It really doesn’t matter other than the order in which it will impact your environment. The “cluster” isn’t a mesh replication like CUCM, it’s more of like a master slave relationship.
<div><br>
</div>
<div>In theory, you have the same license options on both cluster peers, so one peer can function in the same capacity as the other peer.<br>
<br>
<div>I would do the Edge first, then the control; especially if you have internal-only routing on the control server ... leave that for last.</div>
<div><br>
</div>
<div>Thanks,</div>
<div><br>
</div>
<div>Ryan</div>
<div><br>
On Sep 21, 2017, at 6:15 PM, Matt Jacobson <<a href="mailto:m4ttjacobson@gmail.com">m4ttjacobson@gmail.com</a>> wrote:<br>
<br>
</div>
<blockquote type="cite">
<div>
<div dir="ltr">
<div class="gmail_default" style="font-family:"trebuchet ms",sans-serif">I've never seen any documentation that is specific about shutdown order etc. There are also 3 different restart options for Expressway/VCS -- restart, reboot, or power down. There is also
series of guides for cluster maintenance under deployment guides, which may be helpful for you. <a href="https://www.cisco.com/c/dam/en/us/td/docs/voice_ip_comm/expressway/config_guide/X8-10/Cisco-Expressway-Cluster-Creation-and-Maintenance-Deployment-Guide-X8-10.pdf">https://www.cisco.com/c/dam/en/us/td/docs/voice_ip_comm/expressway/config_guide/X8-10/Cisco-Expressway-Cluster-Creation-and-Maintenance-Deployment-Guide-X8-10.pdf</a></div>
<div class="gmail_default" style="font-family:"trebuchet ms",sans-serif"><br>
</div>
<div class="gmail_default" style="font-family:"trebuchet ms",sans-serif">Aside from upgrades, the few times I've had to do something like this was restarting Expressways to clear software errors. I did the primary, then secondary nodes once the primary was
back online. This is also the order suggested for upgrades. I personally do not see any value in doing one cluster before the other, but most of the deployments I see are the simple and supported ones. </div>
</div>
<div class="gmail_extra"><br>
<div class="gmail_quote">On Thu, Sep 21, 2017 at 3:32 PM, Lelio Fulgenzi <span dir="ltr">
<<a href="mailto:lelio@uoguelph.ca" target="_blank">lelio@uoguelph.ca</a>></span> wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
<br>
Just wondering what people are doing when they need to restart their expressway cluster? Since C is the one initiating the connection to E, and because the primary is reaching out to subscribers, I'm thinking:<br>
<br>
Shutdown Order<br>
<br>
C primary<br>
C subscribers<br>
E primary<br>
E subscribers<br>
<br>
(Re)Start Up Order<br>
<br>
E subscribers<br>
E primary<br>
C subscribers<br>
C primary<br>
<br>
Thoughts?<br>
<br>
---<br>
Lelio Fulgenzi, B.A.<br>
Senior Analyst, Network Infrastructure<br>
Computing and Communications Services (CCS)<br>
University of Guelph<br>
<br>
<a href="tel:519-824-4120%20Ext%2056354" value="+15198244120">519-824-4120 Ext 56354</a><br>
<a href="mailto:lelio@uoguelph.ca">lelio@uoguelph.ca</a><br>
<a href="http://www.uoguelph.ca/ccs" rel="noreferrer" target="_blank">www.uoguelph.ca/ccs</a><br>
Room 037, Animal Science and Nutrition Building<br>
Guelph, Ontario, N1G 2W1<br>
<br>
<br>
______________________________<wbr>_________________<br>
cisco-voip mailing list<br>
<a href="mailto:cisco-voip@puck.nether.net">cisco-voip@puck.nether.net</a><br>
<a href="https://puck.nether.net/mailman/listinfo/cisco-voip" rel="noreferrer" target="_blank">https://puck.nether.net/<wbr>mailman/listinfo/cisco-voip</a><br>
<br>
</blockquote>
</div>
<br>
</div>
</div>
</blockquote>
<blockquote type="cite">
<div><span>_______________________________________________</span><br>
<span>cisco-voip mailing list</span><br>
<span><a href="mailto:cisco-voip@puck.nether.net">cisco-voip@puck.nether.net</a></span><br>
<span><a href="https://puck.nether.net/mailman/listinfo/cisco-voip">https://puck.nether.net/mailman/listinfo/cisco-voip</a></span><br>
</div>
</blockquote>
</div>
</body>
</html>