Thanks for taking the time to put some numbers next to these tasks. It looks like this really is a ~5 hour ordeal.<div><br></div><div>Jason, care to share a recap of how it went?</div><br><div class="gmail_quote">On Wed Nov 05 2014 at 8:08:02 PM Justin Steinberg <<a href="mailto:jsteinberg@gmail.com">jsteinberg@gmail.com</a>> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div dir="ltr">i'll take a stab at time estimates. that being said, i have heard of switch-versions taking much longer or sitting at SELINUX loading for longer than the typical 15-20 minutes.<div><br></div><div>checking for existing snapshots before doing anything is really important. if there are snapshots that someone left on their from the past, it will most likely completely hose the upgrade times and make the system extremely slow.<br><div><div><br></div><div></div></div></div></div><div dir="ltr"><div><div><div><div style="font-family:arial,sans-serif;font-size:12.8000001907349px">1. Upload ISOs to DataStore</div><div style="font-family:arial,sans-serif;font-size:12.8000001907349px">2. Disable IO Throttle on Publisher</div><div style="font-family:arial,sans-serif;font-size:12.8000001907349px">3. Mount 8.5(1)SU4 ISO</div></div></div></div></div><div dir="ltr"><div><div><div><div style="font-family:arial,sans-serif;font-size:12.8000001907349px">4. Upgrade Publisher to 8.5(1)SU4 45 - 60 minutes</div><div style="font-family:arial,sans-serif;font-size:12.8000001907349px">5. Switch Version to 8.5(1)SU4 60 minutes (includes switch version process, reboot, SELINUX loading, services startup)</div><div style="font-family:arial,sans-serif;font-size:12.8000001907349px">6. Patch Publisher with RU COP 5 minutes</div><div style="font-family:arial,sans-serif;font-size:12.8000001907349px">7. Shutdown Publisher 10 minutes</div></div></div></div></div><div dir="ltr"><div><div><div><div style="font-family:arial,sans-serif;font-size:12.8000001907349px">8. Modify VM Settings: RAM from 4GB to 8GB</div></div></div></div></div><div dir="ltr"><div><div><div><div style="font-family:arial,sans-serif;font-size:12.8000001907349px">9. Power On Publisher 15 minutes</div><div style="font-family:arial,sans-serif;font-size:12.8000001907349px">10. Mount 10.5(1)SU1 ISO </div><div style="font-family:arial,sans-serif;font-size:12.8000001907349px">11. Upgrade Publisher to 10.5(1)SU1 45-60 minutes</div><div style="font-family:arial,sans-serif;font-size:12.8000001907349px">12. Switch Version to 10.5(1)SU1 60 minutes <span style="font-size:12.8000001907349px">(includes switch version process, reboot, SELINUX loading, services startup)</span></div></div></div></div><div style="font-family:arial,sans-serif;font-size:12.8000001907349px"><span style="font-size:12.8000001907349px">13. Rerun the CAD Client Configuration Tool (10 minutes)</span></div></div><div class="gmail_extra"><br><div class="gmail_quote">On Wed, Nov 5, 2014 at 12:36 AM, Anthony Holloway <span dir="ltr"><<a href="mailto:avholloway+cisco-voip@gmail.com" target="_blank">avholloway+cisco-voip@gmail.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">Wow. Are you going MCS to UCS too? If not, I'm doing that exact upgrade very soon and no documentation I have reviewed indicated how long upgrades would take, let alone 5 hours. Right now my plan has a time budget of 3 hours for the same, which does not include moving ISOs to the datastore (I like doing local upgrades) nor upgrading clients.<div><br></div><div>Which portion is taking 5 hours? Could you break it down by task for us? E.g., L2 to SU4, Switch Version to SU4, RU COP, RU to 10.5, Switch Version to 10.5.<br></div><div><br></div><div>Did you disable IO Throttling first?</div><div><br></div><div>Based on my research here are the summary steps to this exact upgrade (sans client upgrades):</div><div><br></div><div><div>1. Upload ISOs to DataStore</div><div>2. Disable IO Throttle on Publisher</div><div>3. Mount 8.5(1)SU4 ISO</div><div>4. Upgrade Publisher to 8.5(1)SU4</div><div>5. Switch Version to 8.5(1)SU4</div><div>6. Patch Publisher with RU COP</div><div>7. Shutdown Publisher</div><div>8. Modify VM Settings: RAM from 4GB to 8GB</div><div>9. Power On Publisher</div><div>10. Mount 10.5(1)SU1 ISO</div><div>11. Upgrade Publisher to 10.5(1)SU1</div><div>12. Switch Version to 10.5(1)SU1</div></div><div><br></div><div class="gmail_quote"><span>On Tue Nov 04 2014 at 11:04:24 PM Jason Aarons (AM) <<a href="mailto:jason.aarons@dimensiondata.com" target="_blank">jason.aarons@dimensiondata.com</a>> wrote:<br></span><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><span>
<div>
<div>One UCCX node in ha pair 5 hours doing upgrades...it would be more enjoyable watching paint dry...there has got to be a better method in the future for L2 upgrades than this..</div>
<div><br>
</div>
<div><br>
</div>
<div>
<div style="font-size:8px;color:#575757">Sent from my Verizon Wireless 4G LTE Smartphone</div>
</div>
</div></span>
______________________________<u></u><u></u>_________________<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/<u></u>mailma<u></u>n/listinfo/cisco-voip</a><br>
</blockquote></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>