<div dir="auto">Easy peasy. Reboot half of the E nodes after x/2 days. Now the reboots are staggered, no further impact to users. Next question. Am I rich yet? </div><div><br><div class="gmail_quote"><div dir="ltr" class="gmail_attr">On Wed, Jan 13, 2021 at 00:08 Kent Roberts <<a href="mailto:kent@fredf.org">kent@fredf.org</a>> wrote:<br></div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div style="word-wrap:break-word;line-break:after-white-space">We have a new expressway funness. Edge side of the cluster all reboot at one time.. every x number of days….<div><br></div><div>Take the easy ones!</div></div><div style="word-wrap:break-word;line-break:after-white-space"><div><br><div><br><blockquote type="cite"><div>On Jan 12, 2021, at 10:41 PM, Hunter Fuller via cisco-voip <<a href="mailto:cisco-voip@puck.nether.net" target="_blank">cisco-voip@puck.nether.net</a>> wrote:</div><br><div><div dir="auto">Whoever said that has clearly never administered Expressway. </div><div><br><div class="gmail_quote"><div dir="ltr" class="gmail_attr">On Tue, Jan 12, 2021 at 23:25 Anthony Holloway <<a href="mailto:avholloway%2Bcisco-voip@gmail.com" target="_blank">avholloway+cisco-voip@gmail.com</a>> wrote:<br></div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div dir="ltr">Nice! That was easy. This email chain goes into my folder called: When Someone Says Only Windows Servers Need Reboots.</div><br><div class="gmail_quote"><div dir="ltr" class="gmail_attr">On Tue, Jan 12, 2021 at 7:40 PM Riley, Sean <<a href="mailto:SRiley@robinsonbradshaw.com" target="_blank">SRiley@robinsonbradshaw.com</a>> wrote:<br></div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex">
<div lang="EN-US">
<div><p class="MsoNormal"><span style="color:rgb(31,73,125)">So far it seems the reboot resolved this problem. Thanks for all the replies with guidance and help.<u></u><u></u></span></p><p class="MsoNormal"><span style="color:rgb(31,73,125)"><u></u> <u></u></span></p><p class="MsoNormal"><b>From:</b> Kent Roberts <<a href="mailto:kent@fredf.org" target="_blank">kent@fredf.org</a>> <br>
<b>Sent:</b> Tuesday, January 12, 2021 4:42 PM<br>
<b>To:</b> Riley, Sean <<a href="mailto:SRiley@robinsonbradshaw.com" target="_blank">SRiley@robinsonbradshaw.com</a>><br>
<b>Cc:</b> <a href="mailto:cisco-voip@puck.nether.net" target="_blank">cisco-voip@puck.nether.net</a><br>
<b>Subject:</b> Re: [cisco-voip] CUCM call set up issue after migration<u></u><u></u></p><p class="MsoNormal"><u></u> <u></u></p><p class="MsoNormal" style="margin-bottom:12pt">Ah split brains. Gotta love it. Did you restart the ones that did not move? I have seen this when things go stupid. The sync usually isn’t the problem it’s the real-time communication between the nodes
that’s all messed up. Usually can fix with a node reboot or restarting the cucm and cti services. Course their maybe more to it but if things are in sync should not be hard to fix<u></u><u></u></p>
<div>
<div><p class="MsoNormal"><u></u> <u></u></p>
</div><p class="MsoNormal">Kent<u></u><u></u></p>
</div>
<div><p class="MsoNormal"><br>
<br>
<u></u><u></u></p>
<blockquote style="margin-top:5pt;margin-bottom:5pt"><p class="MsoNormal" style="margin-bottom:12pt">On Jan 12, 2021, at 14:06, Riley, Sean <<a href="mailto:SRiley@robinsonbradshaw.com" target="_blank">SRiley@robinsonbradshaw.com</a>> wrote:<u></u><u></u></p>
</blockquote>
</div>
<blockquote style="margin-top:5pt;margin-bottom:5pt">
<div><p class="MsoNormal"> <span style="font-size:12pt;font-family:"Times New Roman",serif">
<u></u><u></u></span></p><p class="MsoNormal"><span style="font-size:10pt;font-family:Arial,sans-serif">This past weekend we migrated 2 CUCM servers to a new datacenter. This involved changing the IP address on these 2 CUCM nodes. These 2 nodes consist of the Publisher
and 1 Subscriber. We have another Sub at a remote datacenter that was not touched this past weekend.</span><u></u><u></u></p><p class="MsoNormal"><span style="font-size:10pt;font-family:Arial,sans-serif"> </span><u></u><u></u></p><p class="MsoNormal"><span style="font-size:10pt;font-family:Arial,sans-serif">Node configuration:</span><u></u><u></u></p><p class="MsoNormal"><span style="font-size:10pt;font-family:Arial,sans-serif"> </span><u></u><u></u></p><p class="MsoNormal"><span style="font-size:10pt;font-family:Arial,sans-serif">DC A</span><u></u><u></u></p><p class="MsoNormal"><span style="font-size:10pt;font-family:Arial,sans-serif">CM1: Pub which was re-ip’d</span><u></u><u></u></p><p class="MsoNormal"><span style="font-size:10pt;font-family:Arial,sans-serif">CM2: Sub which was re-ip’d</span><u></u><u></u></p><p class="MsoNormal"><span style="font-size:10pt;font-family:Arial,sans-serif"> </span><u></u><u></u></p><p class="MsoNormal"><span style="font-size:10pt;font-family:Arial,sans-serif">DC B:</span><u></u><u></u></p><p class="MsoNormal"><span style="font-size:10pt;font-family:Arial,sans-serif">CM3: Sub at remote site that was not changed</span><u></u><u></u></p><p class="MsoNormal"><span style="font-size:10pt;font-family:Arial,sans-serif"> </span><u></u><u></u></p><p class="MsoNormal"><span style="font-size:10pt;font-family:Arial,sans-serif">Phones are at many sites, but issue is independent of the phone type, phone location or subnet. Also, Expressway phones have the same issue.</span><u></u><u></u></p><p class="MsoNormal"><span style="font-size:10pt;font-family:Arial,sans-serif"> </span><u></u><u></u></p><p class="MsoNormal"><span style="font-size:10pt;font-family:Arial,sans-serif">The issue is any phone that is registered to CM3 cannot call phones registered to CM1 or CM2 and vice versa. The phones do not see the call coming in. If SNR is
configured, the call will ring to the remote destination. Phones registered to CM3 can make outbound PSTN calls without issue, but not receive inbound from PSTN (probably because the gateway is handing off to CM1 or CM2). While the gateways are not unique
to the issue, they are running H323.</span><u></u><u></u></p><p class="MsoNormal"><span style="font-size:10pt;font-family:Arial,sans-serif"> </span><u></u><u></u></p><p class="MsoNormal"><span style="font-size:10pt;font-family:Arial,sans-serif">If the phones are both registered to CM3, they can call each other, but not phones registered to CM1 or CM2.</span><u></u><u></u></p><p class="MsoNormal"><span style="font-size:10pt;font-family:Arial,sans-serif"> </span><u></u><u></u></p><p class="MsoNormal"><span style="font-size:10pt;font-family:Arial,sans-serif">I have had my network team verify there is not anything they can see in the network causing this behavior. Database replication checks out OK and I can ping from/to
each node.</span><u></u><u></u></p><p class="MsoNormal"><span style="font-size:10pt;font-family:Arial,sans-serif"> </span><u></u><u></u></p><p class="MsoNormal"><span style="font-size:10pt;font-family:Arial,sans-serif">Anyone able to point me in the right direction to figure this out?</span><u></u><u></u></p><p class="MsoNormal"><span style="font-size:10pt;font-family:Arial,sans-serif"> </span><u></u><u></u></p><p class="MsoNormal"><span style="font-size:10pt;font-family:Arial,sans-serif">Thanks.</span><u></u><u></u></p><p class="MsoNormal"><span style="font-size:12pt;font-family:"Times New Roman",serif">_______________________________________________<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://puck.nether.net/mailman/listinfo/cisco-voip" target="_blank">https://puck.nether.net/mailman/listinfo/cisco-voip</a><u></u><u></u></span></p>
</div>
</blockquote>
</div>
</div>
_______________________________________________<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://puck.nether.net/mailman/listinfo/cisco-voip" rel="noreferrer" target="_blank">https://puck.nether.net/mailman/listinfo/cisco-voip</a><br>
</blockquote></div>
_______________________________________________<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://puck.nether.net/mailman/listinfo/cisco-voip" rel="noreferrer" target="_blank">https://puck.nether.net/mailman/listinfo/cisco-voip</a><br>
</blockquote></div></div>-- <br><div dir="ltr" data-smartmail="gmail_signature"><div dir="ltr"><div><div dir="ltr"><div><br>--<br>Hunter Fuller (they)<br>Router Jockey<br>VBH Annex B-5<br>+1 256 824 5331<br><br>Office of Information Technology<br>The University of Alabama in Huntsville<br>Network Engineering</div></div></div></div></div>
_______________________________________________<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://puck.nether.net/mailman/listinfo/cisco-voip" target="_blank">https://puck.nether.net/mailman/listinfo/cisco-voip</a><br></div></blockquote></div><br></div></div></blockquote></div></div>-- <br><div dir="ltr" class="gmail_signature" data-smartmail="gmail_signature"><div dir="ltr"><div><div dir="ltr"><div><br>--<br>Hunter Fuller (they)<br>Router Jockey<br>VBH Annex B-5<br>+1 256 824 5331<br><br>Office of Information Technology<br>The University of Alabama in Huntsville<br>Network Engineering</div></div></div></div></div>