<div dir="ltr">Is TFTP really that trivial? What would happen to an endpoint, which is in the middle of a firmware upgrade, when you deactivate TFTP?</div><div class="gmail_extra"><br><div class="gmail_quote">On Thu, Dec 1, 2016 at 2:51 PM, Nick Barnett <span dir="ltr"><<a href="mailto:nicksbarnett@gmail.com" target="_blank">nicksbarnett@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 dir="ltr">I figured that a reboot would work, but TAC told me it wouldn't... and rather than experimenting, I just did what they said to do :) Besides, deactivating TFTP is trivial and in a properly laid out deployment should have 0 impact.</div><div class="HOEnZb"><div class="h5"><div class="gmail_extra"><br><div class="gmail_quote">On Wed, Nov 30, 2016 at 8:28 AM, NateCCIE <span dir="ltr"><<a href="mailto:nateccie@gmail.com" target="_blank">nateccie@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 dir="auto"><div>A reboot does work. What the deal is the new https version of tftp (port 6972) does not restart with the service restart. So it continues to use the old cert. But it does stop and start with a service deactivation and reactivation. Before cucm 11 the tftp over http was only plain text (port 6970)</div><div id="m_157446718757769233m_6164531748084802322AppleMailSignature"><br><br>Sent from my iPhone</div><div><div class="m_157446718757769233h5"><div><br>On Nov 30, 2016, at 1:12 AM, James Buchanan <<a href="mailto:james.buchanan2@gmail.com" target="_blank">james.buchanan2@gmail.com</a>> wrote:<br><br></div><blockquote type="cite"><div><div dir="ltr"><div><div><div>Hello,<br><br></div>If I remember right, it actually has to be deactivated under Service Management. It's not just restarting the service.<br><br></div>Thanks,<br><br></div>James<br></div><div class="gmail_extra"><br><div class="gmail_quote">On Tue, Nov 29, 2016 at 11:36 PM, Derek Andrew <span dir="ltr"><<a href="mailto:Derek.Andrew@usask.ca" target="_blank">Derek.Andrew@usask.ca</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div dir="ltr">Would a simple reboot accomplish the same as deactivating and activating?<br></div><div class="gmail_extra"><br><div class="gmail_quote">On Mon, Nov 28, 2016 at 2:19 PM, Nick Barnett <span dir="ltr"><<a href="mailto:nicksbarnett@gmail.com" target="_blank">nicksbarnett@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>
<div dir="ltr">I just thought I would share what happened with this, even though it is super old. Changing the node names to FQDN was mostly painless. The one thing that bit me was bug CSCuy13916. After changing the names of the nodes, the TFTP service needs
to be DEACTIVATED and then re-activated in order to fully update the certificates. Before taking those steps, I kept getting certificate errors from CuciLync, but afterwards, everything worked as designed.
<div><br>
</div>
<div>Other than that, any CTI route points (and any other device as well) that exist will fall to another node in the CMG. Not a big deal, just something to be aware of.</div>
<div><br>
</div>
<div>Thanks,</div>
<div>Nick</div>
</div>
<div class="gmail_extra"><br>
<div class="gmail_quote">On Wed, Aug 31, 2016 at 3:13 PM, Nick Barnett <span dir="ltr">
<<a href="mailto:nicksbarnett@gmail.com" target="_blank">nicksbarnett@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 dir="ltr">We are on 10.0 and this cluster has been upgraded over the years from 8.0 to 8.6 to 10.0. I know it used to be common practice to rip the host name out of a new node and put in the IP address. That's how we are set up... but now that I need
to do some work with certs so that jabber and cucilync work properly, it's time to fix this.
<div><br>
</div>
<div>Is there anything I should watch out for? Anything that may bite me in rare cases? We have CER, CVP, CUC, UCCE and a rarely used IMP.</div>
<div><br>
</div>
<div>I checked that each node has DNS enabled by looking at "show network eth0" on each sub. I also then looked up each FQDN from each node and they all resolve properly. As far as I know, that's about it.</div>
<div><br>
</div>
<div>Thanks in advance!</div>
<span class="m_157446718757769233m_6164531748084802322m_-7183505427918358531m_1672962014693800631HOEnZb"><font color="#888888">
<div><br>
nick</div>
</font></span></div>
</blockquote>
</div>
<br>
</div>
</div>
</blockquote></div><br><br clear="all"><br>-- <br><div class="m_157446718757769233m_6164531748084802322m_-7183505427918358531gmail_signature" data-smartmail="gmail_signature"><div dir="ltr"><div><div dir="ltr"><div><div dir="ltr"><div><div dir="ltr"><div><div dir="ltr"><div><div dir="ltr"><div><div dir="ltr">Copyright 2016 Derek Andrew (excluding quotations)<br><br><a href="tel:(306)%20966-4808" value="+13069664808" target="_blank">+1 306 966 4808</a></div><div dir="ltr"><font size="1">Communication and Network Services</font></div><div dir="ltr"><font size="1">Information and Communications Technology</font></div><div dir="ltr"><font size="1">Infrastructure Services<br></font><b>University of Saskatchewan<br></b><font size="1">Peterson 120; 54 Innovation Boulevard<br>Saskatoon,Saskatchewan,Canada. S7N 2V3<br>Timezone GMT-6<br></font><br>Typed but not read.<br><br><img src="http://homepage.usask.ca/dfa878/uofs.gif" width="200" height="15"><br><br></div></div></div></div></div></div></div></div></div></div></div></div></div></div>
</div>
<br>______________________________<wbr>_________________<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/mailma<wbr>n/listinfo/cisco-voip</a><br>
<br></blockquote></div><br></div>
</div></blockquote><blockquote type="cite"><div><span>______________________________<wbr>_________________</span><br><span>cisco-voip mailing list</span><br><span><a href="mailto:cisco-voip@puck.nether.net" target="_blank">cisco-voip@puck.nether.net</a></span><br><span><a href="https://puck.nether.net/mailman/listinfo/cisco-voip" target="_blank">https://puck.nether.net/mailma<wbr>n/listinfo/cisco-voip</a></span><br></div></blockquote></div></div></div><br>______________________________<wbr>_________________<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/mailma<wbr>n/listinfo/cisco-voip</a><br>
<br></blockquote></div><br></div>
</div></div><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>