<html>
<head>
<meta http-equiv="Content-Type" content="text/html; charset=us-ascii">
</head>
<body style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space;">
Still trying to look into this some more but it's worth noting that phones are restarted (simply a re-registration), not reset. This process should be extremely fast and most users won't even notice.
<div><br>
<div>-Ryan </div>
<br>
<div>
<div>On Nov 4, 2014, at 12:34 PM, TG <<a href="mailto:techguy.ca@gmail.com">techguy.ca@gmail.com</a>> wrote:</div>
<br class="Apple-interchange-newline">
<div>
<div bgcolor="#FFFFFF" text="#000000">
<p dir="ltr">Hi Charles, I'm not promoting a sub into pub, rather moving phones to the other cluster. If you meant segregated planned controlled outages, then that can't be done as "ALL" phones take a hit by cert combination regardless of which sub they are
registered to. My only ask was to see if that reset could be prohibited so phones could be manually reset in a controlled and clean manner. Comparing this with firmware upgrade, the process itself doesn't initiate a reset to 'ALL" ones in one shot so you
have control over how you want to bulk that activity, either server level or DP level etc.<br>
</p>
<p dir="ltr">Thanks,<br>
TG<br>
</p>
<div class="gmail_quote">On Nov 3, 2014 10:53 PM, "Charles Goldsmith" <<a href="mailto:wokka@justfamily.org">wokka@justfamily.org</a>> wrote:<br type="attribution">
<blockquote class="gmail_quote" style="margin:0 0 0
.8ex;border-left:1px #ccc solid;padding-left:1ex">
<div dir="ltr">TG, you state that you aren't trying to promote a sub, but your subject line indicates that you are. When talking about combining certs and TVS restarts, thats for a migration, moving phones from one cluster to another. This is not a way to
promote a sub to a pub, which you cannot do.
<div><br>
</div>
<div>If you are upgrading while rebuilding a new cluster, that is one thing, but we don't do this often, and most customers do not ever do this. What I mean by this is if you are building a fresh, new cluster with the latest version and then moving phones
to this new setup.</div>
<div><br>
</div>
<div>Rebuilding to resolve dial plan best practices or splitting a company are the only reasons I've seen the need of a migration, but perhaps moving a group of phones from one cluster to another in a very large deployment could be a practical use of it.</div>
<div><br>
</div>
<div>Pushing new certs down (by combining them) is going to cause some restarts of phones, plan for that with your outages. It's really no different than planned outages around upgrading firmware in prep for a software upgrade, which causes another round of
resets as they re-register with subs.</div>
<div><br>
</div>
<div>Good luck and ask your questions, but please clarify your plan and intents.</div>
</div>
<div class="gmail_extra"><br>
<div class="gmail_quote">On Mon, Nov 3, 2014 at 5:53 PM, TG <span dir="ltr"><<a href="mailto:techguy.ca@gmail.com" target="_blank">techguy.ca@gmail.com</a>></span> wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0
.8ex;border-left:1px #ccc solid;padding-left:1ex">
<div bgcolor="#FFFFFF" text="#000000">Brian,<br>
Thanks for your input. It's unfortunate we have to live with it. <br>
Need to know the significance and purpose of TVS restart on subs, as results are seen without doing it as well. Also does that cause another reset on the phones?
<br>
<br>
Ryan,<br>
Maybe you misunderstood it, it is about bulk cert, and not pub recovery. Do you know of a way to stop phones from resetting just by combining the cert? We see this being fixed in 9.5 but not everyone is willing to jump to 9.5 for this gap. Cisco should consider
addressing this on 8.6 and 9.1 as well as many customers are using these releases. If your 30k phones have to take a hit because of cert combining, then that's a big drawback to this whole procedure of cluster replacements.<br>
<br>
Thanks,<br>
TG<span><br>
<br>
<div>On 2014-11-03 4:39 PM, Ryan Ratliff (rratliff) wrote:<br>
</div>
<blockquote type="cite">I'm not aware of the specifics of the doc bug Brian referenced but the original question sounds less like bulk cert import and more like a publisher recovery. Can you provide a bit more details on what you mean by "promote a new publisher
to existing phones"?
<div><br>
<div>
<div>-Ryan </div>
<br>
</div>
</div>
</blockquote>
<br>
</span></div>
<br>
_______________________________________________<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>
<br>
</blockquote>
</div>
<br>
</div>
</blockquote>
</div>
</div>
</div>
</div>
<br>
</div>
</body>
</html>