[cisco-voip] (no subject)
Justin Steinberg
jsteinberg at gmail.com
Fri Mar 20 10:34:55 EDT 2015
So in the CUCM 10.5 download section for the Utilities, it seems to have
combined the common cleanup COP file and the VMware Disk Size Reallocation.
There is a COP file title '*VMware Disk Size Reallocation COP file' *but
the actual file is *ciscocm.free_common_space_v1.3.k3.cop.sgn*
The actual reallocation cop file isn't part of the CUCM 10.5 download, I
had to go back into an older version to file that COP. So that is why I
was thinking in 10.5 all you would need to do is change the size of the
vDisk in VMware and restart CUCM 10.5.
Is there an official document on the process to follow for this change ?
Justin
On Fri, Mar 20, 2015 at 10:12 AM, Roger Wiklund <roger.wiklund at gmail.com>
wrote:
> I have.
>
> Went from 2500 to 7500 on CUCM 10.5(1).
>
> You need to download the VMware Disk Size Reallocation COP file for
> 10.5. Worked like a charm.
>
>
> http://www.cisco.com/web/software/282204704/18582/CleanupCommonCOPfilev1.3.pdf
>
> http://www.cisco.com/web/software/282204704/18582/ciscocm.vmware_disk_size_reallocation_v1.0.pdf
>
> On Fri, Mar 20, 2015 at 2:28 PM, Justin Steinberg <jsteinberg at gmail.com>
> wrote:
> > Has anyone successfully expanded the virtual disk size of CUCM VMs
> without
> > rebuild/DRS?
> >
> >
> >
> > I have an install where CM 10.5 is using the 2500 user template and we
> want
> > to increase to 7500 users. The 2500 OVA is 1 vCPU, 4GB, 1x80GB. The
> 7500
> > OVA is 2vCPU, 6 GB, 1x110GB. In the past, the older 7500 user CM
> versions
> > had two virtual 80 GB disks, however since 9.1 the 7500 user is a single
> 110
> > GB disk. It seems like with a single virtual disk it would be easier to
> > expand an existing VM without rebuild.
> >
> >
> >
> > There are several bugs on the topic:
> >
> > https://tools.cisco.com/bugsearch/bug/CSCug63058
> >
> > https://tools.cisco.com/bugsearch/bug/CSCuc58936
> >
> >
> >
> > In older CM versions there was a COP file to assist with allowing the VM
> to
> > use more disk when the vdisk was increased. However, now I believe that
> it
> > is just built in to CM to use more disk on reboots if it detects a vdisk
> > change instead of needing to run the OVA.
> >
> >
> >
> > There is still conflicting documentation on the topic, so I will probably
> > open a TAC case but curious if anyone has dealt with this before?
> >
> >
> > Justin
> >
> >
> > _______________________________________________
> > 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/20150320/662b409a/attachment.html>
More information about the cisco-voip
mailing list