[cisco-voip] UCM Upgrade Poll

Mon Aug 28 03:30:40 EDT 2017

Yep. Besides the steps in docs above,

The expand space cop file if the upgrade needs you to change the disk space
for new version per OVA template specs.

The RTMT low watermark trick works very well, but sometimes doesn't free up
quite enough so then you need to manually go find files to clear.

Check your MoH files -- once had a system with dozens of larger size MoH
files. Had to temp remove some of them to gain space and put them back
afterward.

TFTP files -- I usually delete the larger ones (DX650s, CIUS, etc).   (file
list tftp * detail size) if needed. Usually, a very small % of disk
reclaimed on newer versions.

Check for packet capture files under platform/cli

On Sun, Aug 27, 2017 at 10:30 PM, Charles Goldsmith <wokka at justfamily.org>
wrote:

> I should have looked at that link a bit closer, it doesn't mention the cop
> file: http://www.cisco.com/web/software/282204704/18582/
> CleanupCommonCOPfilev1.4.pdf
>
> Which is the 3rd method, but there is a caveat, so read it closely.
>
> On Sun, Aug 27, 2017 at 11:25 PM, Charles Goldsmith <wokka at justfamily.org>
> wrote:
>
>> There is!
>>
>> http://docwiki.cisco.com/wiki/Unified_CM_L2_Upgrade_Disk_Spa
>> ce_issues#Free_Up_Space_for_Unified_CM_L2_Upgrade.C2.A0
>>
>> That entire page is good reading.
>>
>>
>> On Sun, Aug 27, 2017 at 11:20 PM, Lelio Fulgenzi <lelio at uoguelph.ca>
>> wrote:
>>
>>> Are there instructions on how to free up disk space?
>>>
>>> Sent from my iPhone
>>>
>>> On Aug 27, 2017, at 11:18 PM, Erick Bergquist <erickbee at gmail.com>
>>> wrote:
>>>
>>> I've done a few dozen inplace upgrades of CUCM, Unity, UCCX with
>>> existing VMs with no real issues over the past few years. Talking 8.x to
>>> 10.x  or 11.x or 9.x to 10/11.x.
>>>
>>> Issues encountered:
>>>
>>> Freeing up disk space on existing VM for the RU/SU to install on a few
>>> upgrades (more of a slow down)
>>>
>>> Recently had issue with IM&P 9.x to 11.x where a invalid ntp entry was
>>> in the platformcfg.xml XML file that there is a bug ID on that TAC had to
>>> get in with root access to remove. After that the IM&P inplace upgrade went
>>> fine.
>>>
>>> And a few non-upgrade issues involving license matters and getting
>>> correct number of licenses.
>>>
>>> I was reading another post about 12.0 using CentOS now, need to read
>>> that over more and see what is changing with upgrade process.
>>>
>>>
>>> My only wish was if these would go faster. Maybe have an incremental
>>> patch with just fixes instead of a full size SU/install file and
>>> reinstalling every file - especially for SU patches within same major
>>> version.
>>>
>>> YMMV, Erick
>>>
>>>
>>> On Thu, Aug 24, 2017 at 10:34 AM, Anthony Holloway <
>>> avholloway+cisco-voip at gmail.com> wrote:
>>>
>>>> Why not just come along with me on my next upgrade.  You can feel the
>>>> pain...err excitement, of planning and executing an upgrade in the real
>>>> world.  ;)
>>>>
>>>> On Thu, Aug 24, 2017 at 9:52 AM Ryan Ratliff (rratliff) <
>>>> rratliff at cisco.com> wrote:
>>>>
>>>>> Thanks everyone for the feedback.
>>>>>
>>>>> We are looking at ways to make upgrades easier and stories like these
>>>>> are very helpful.
>>>>>
>>>>> -Ryan
>>>>>
>>>>> On Aug 24, 2017, at 10:17 AM, Scott Voll <svoll.voip at gmail.com> wrote:
>>>>>
>>>>> 1. I'm guessing we are 10% True bugs and 90% environment, but I will
>>>>> agree with other comments about DNS and NTP being a dumb reason to fail
>>>>>
>>>>> 2. as for time, over the years we used to spend over 6 months on
>>>>> upgrades...... we are down to about 2 months.  in our enviroment we have to
>>>>> document all the changes before so it can be communicated to the end user.
>>>>> Researching for the answers has moved from Anthony's 100 documents to just
>>>>> opening a TAC case.  It has become way to time consuming to find all the
>>>>> right doc's to get the correct answer.
>>>>>
>>>>> YMMV
>>>>>
>>>>> Scott
>>>>>
>>>>>
>>>>> On Wed, Aug 23, 2017 at 1:46 PM, Anthony Holloway <
>>>>> avholloway+cisco-voip at gmail.com> wrote:
>>>>>
>>>>>> Wow, it's kind of cool that you're even asking.  Thanks for that.
>>>>>>
>>>>>> Already I can see this is going to be a wide gap in responses.
>>>>>> Partner vs end user, this customer vs that customer, this version vs that
>>>>>> version, this scenario vs that one, and on, and on, and on.
>>>>>>
>>>>>> 1) I feel like it's always a bug (100%), in that, developers should
>>>>>> code solutions that can work around most issues.  E.g., I had an upgrade
>>>>>> fail on a CUCM because the ntp was 0.us.pool.ntp.org, despite CUCM
>>>>>> happily syncing to it in the current version.  OR Common partition not
>>>>>> having enough space, when devs could just purge old logs to make room, or
>>>>>> simply make better logs to begin with (I do admit, moving to compress logs
>>>>>> [TAR/GZ] was sweet)
>>>>>>
>>>>>> 2) This is a painful one for me, but I put in a lot of time preparing
>>>>>> for an upgrade.  A large portion of the time is, in my opinion, wasted
>>>>>> finding the right documentation and then trying to interpret it.  Here's a
>>>>>> fun one: there's over 100 documents an Engineer needs to reference in
>>>>>> preparation for what I would consider a low-medium level environment.  I've
>>>>>> posted this before, but I'll post it again, I have a matrix of documents I
>>>>>> need to reference during the planning and execution phase of an upgrade:
>>>>>>
>>>>>>
>>>>>>
>>>>>>
>>>>>> On Wed, Aug 23, 2017 at 8:38 AM Ryan Ratliff (rratliff) <
>>>>>> rratliff at cisco.com> wrote:
>>>>>>
>>>>>>> Quick 2 question poll, feel free to unicast or share your response
>>>>>>> with the group.
>>>>>>>
>>>>>>> 1. When you or your customers have a UCM or IMP upgrade fail, what
>>>>>>> percentage of failures are due to a bug vs something in the environment
>>>>>>> (user error, db updates, etc)?
>>>>>>> % bug:
>>>>>>> % not a bug:
>>>>>>> Yes it’s a very subjective question but that’s ok, use your
>>>>>>> judgement.
>>>>>>>
>>>>>>> 2. When an upgrade goes smoothly with no issues, how much time do
>>>>>>> you put into the planning and preparation for the upgrade (not the
>>>>>>> execution)?
>>>>>>>
>>>>>>> Thanks,
>>>>>>>
>>>>>>> -Ryan
>>>>>>>
>>>>>>> _______________________________________________
>>>>>>> cisco-voip mailing list
>>>>>>> cisco-voip at puck.nether.net
>>>>>>> https://puck.nether.net/mailman/listinfo/cisco-voip
>>>>>>>
>>>>>>
>>>>>> _______________________________________________
>>>>>> cisco-voip mailing list
>>>>>> cisco-voip at puck.nether.net
>>>>>> https://puck.nether.net/mailman/listinfo/cisco-voip
>>>>>>
>>>>>>
>>>>>
>>>>>
>>>> _______________________________________________
>>>> cisco-voip mailing list
>>>> cisco-voip at puck.nether.net
>>>> https://puck.nether.net/mailman/listinfo/cisco-voip
>>>>
>>>>
>>> _______________________________________________
>>> cisco-voip mailing list
>>> cisco-voip at puck.nether.net
>>> https://puck.nether.net/mailman/listinfo/cisco-voip
>>>
>>>
>>> _______________________________________________
>>> cisco-voip mailing list
>>> cisco-voip at puck.nether.net
>>> https://puck.nether.net/mailman/listinfo/cisco-voip
>>>
>>>
>>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://puck.nether.net/pipermail/cisco-voip/attachments/20170828/33749899/attachment.html>