<div dir="ltr">Hello,<div><br></div><div>I think I mentioned this once on this forum, but I did have a problem with 12.5 re: MOH due to an unclean shutdown. Rebuilding was the only option. In my case, the shutdown had happened with 10.5 but carried through apparently. Very mysterious! Still, the rebuild fixed it.</div><div><br></div><div>Thanks,</div><div><br></div><div>James</div></div><br><div class="gmail_quote"><div dir="ltr" class="gmail_attr">On Tue, Mar 22, 2022 at 3:51 AM russon81 via cisco-voip <<a href="mailto:cisco-voip@puck.nether.net">cisco-voip@puck.nether.net</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 dir="auto"><div dir="auto">I've already rebuilt 3 clusters because of this. Thanks Cisco!</div><div><br></div><div align="left" dir="auto" style="font-size:100%;color:rgb(0,0,0)"><div>-------- Original message --------</div><div>From: Lelio Fulgenzi <<a href="mailto:lelio@uoguelph.ca" target="_blank">lelio@uoguelph.ca</a>> </div><div>Date: 3/21/22 8:23 PM (GMT-08:00) </div><div>To: Kent Roberts <<a href="mailto:dvxkid@gmail.com" target="_blank">dvxkid@gmail.com</a>> </div><div>Cc: <a href="mailto:cisco-voip@puck.nether.net" target="_blank">cisco-voip@puck.nether.net</a> </div><div>Subject: Re: [cisco-voip] Just an FYI </div><div><br></div></div>
As far as I know, the COP file doesn’t fix anything. It just removes the warning. TAC can still see an ungraceful shutdown happened and can still direct you to rebuild.
<div><br>
</div>
<div>And yes. It’s ridiculous that there isn’t a way to do a system check to determine whether or not the system is operating ok. </div>
<div><br>
</div>
<div><a href="https://www.cisco.com/web/software/286319173/139477/ciscocm.add_utils_ungraceful_warn_disable_v1.0.cop-README.pdf" target="_blank">https://www.cisco.com/web/software/286319173/139477/ciscocm.add_utils_ungraceful_warn_disable_v1.0.cop-README.pdf</a><br>
<br>
<div dir="ltr">Sent from my iPhone</div>
<div dir="ltr"><br>
<blockquote type="cite">On Mar 21, 2022, at 11:05 PM, Kent Roberts <<a href="mailto:dvxkid@gmail.com" target="_blank">dvxkid@gmail.com</a>> wrote:<br>
<br>
</blockquote>
</div>
<blockquote type="cite">
<div dir="ltr"><span>CAUTION: This email originated from outside of the University of Guelph. Do not click links or open attachments unless you recognize the sender and know the content is safe. If in doubt, forward suspicious emails to <a href="mailto:IThelp@uoguelph.ca" target="_blank">IThelp@uoguelph.ca</a></span><br>
<span></span><br>
<span></span><br>
<span>Intersting that TAC didn’t offer that as a solution nor could they provide any way to validate the box was safe for production. </span><br>
<span></span><br>
<span></span><br>
<span></span><br>
<blockquote type="cite"><span>On Mar 21, 2022, at 9:03 PM, Lelio Fulgenzi <<a href="mailto:lelio@uoguelph.ca" target="_blank">lelio@uoguelph.ca</a>> wrote:</span><br>
</blockquote>
<blockquote type="cite"><span></span><br>
</blockquote>
<blockquote type="cite"><span>Yes. This has been making the rounds in some forums and spaces. </span><br>
</blockquote>
<blockquote type="cite"><span></span><br>
</blockquote>
<blockquote type="cite"><span>Great thing is… there’s a COP file to remove the warning from the login screen.
</span><br>
</blockquote>
<blockquote type="cite"><span></span><br>
</blockquote>
<blockquote type="cite"><span>¯\_(ツ)_/¯ </span><br>
</blockquote>
<blockquote type="cite"><span></span><br>
</blockquote>
<blockquote type="cite"><span>Sent from my iPhone</span><br>
</blockquote>
<blockquote type="cite"><span></span><br>
</blockquote>
<blockquote type="cite">
<blockquote type="cite"><span>On Mar 21, 2022, at 11:00 PM, Kent Roberts <<a href="mailto:dvxkid@gmail.com" target="_blank">dvxkid@gmail.com</a>> wrote:</span><br>
</blockquote>
</blockquote>
<blockquote type="cite">
<blockquote type="cite"><span></span><br>
</blockquote>
</blockquote>
<blockquote type="cite">
<blockquote type="cite"><span>CAUTION: This email originated from outside of the University of Guelph. Do not click links or open attachments unless you recognize the sender and know the content is safe. If in doubt, forward suspicious emails to <a href="mailto:IThelp@uoguelph.ca" target="_blank">IThelp@uoguelph.ca</a></span><br>
</blockquote>
</blockquote>
<blockquote type="cite">
<blockquote type="cite"><span></span><br>
</blockquote>
</blockquote>
<blockquote type="cite">
<blockquote type="cite"><span></span><br>
</blockquote>
</blockquote>
<blockquote type="cite">
<blockquote type="cite"><span>Just through I would share. For those that don’t know…
</span><br>
</blockquote>
</blockquote>
<blockquote type="cite">
<blockquote type="cite"><span></span><br>
</blockquote>
</blockquote>
<blockquote type="cite">
<blockquote type="cite"><span>New in CUCM 12.5 su4, a excellent new feature (a stupid one) was added…. If a CUCM node takes an unscheduled power down…it must be rebuilt. There is no way to remove the ungraceful shutdown alert that becomes present. Only
way to recover is via DRS, so make sure your DRS backups are working. A snapshot backup will trigger the same event as it wasn’t a clean power down. If no DRS is available, its a complete removal of the entire node, and rebuild from scratch.</span><br>
</blockquote>
</blockquote>
<blockquote type="cite">
<blockquote type="cite"><span></span><br>
</blockquote>
</blockquote>
<blockquote type="cite">
<blockquote type="cite"><span>So, once you complete your upgrade, run a full backup.</span><br>
</blockquote>
</blockquote>
<blockquote type="cite">
<blockquote type="cite"><span></span><br>
</blockquote>
</blockquote>
<blockquote type="cite">
<blockquote type="cite"><span>Just thought I would share…...</span><br>
</blockquote>
</blockquote>
<blockquote type="cite">
<blockquote type="cite"><span>_______________________________________________</span><br>
</blockquote>
</blockquote>
<blockquote type="cite">
<blockquote type="cite"><span>cisco-voip mailing list</span><br>
</blockquote>
</blockquote>
<blockquote type="cite">
<blockquote type="cite"><span><a href="mailto:cisco-voip@puck.nether.net" target="_blank">cisco-voip@puck.nether.net</a></span><br>
</blockquote>
</blockquote>
<blockquote type="cite">
<blockquote type="cite"><span><a href="https://puck.nether.net/mailman/listinfo/cisco-voip" target="_blank">https://puck.nether.net/mailman/listinfo/cisco-voip</a></span><br>
</blockquote>
</blockquote>
<span></span><br>
</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>