Re: [cisco-voip] CUCM Cluster Redundancy

2015-03-21 Thread Heim, Dennis
Multiple pubs is not supported. The appropriate approach is to use some type of 
VM backup and restore solution. This could be some scripts that you run on 
VMware that back up the vmx/vmdk files and zip them up, or it could be a 
solution such as Veeam. That way if everything goes to crap you can do a full 
cluster restore to a known good state.

Dennis Heim | Emerging Technology Architect (Collaboration)
World Wide Technology, Inc. | +1 314-212-1814
[twitter]https://twitter.com/CollabSensei
[chat]xmpp:dennis.h...@wwt.com[Phone]tel:+13142121814[video]sip:dennis.h...@wwt.com
Innovation happens on project squared -- 
http://www.projectsquared.comhttp://www.projectsquared.com/

Click here to join me in my Collaboration Meeting 
Roomhttps://wwt.webex.com/meet/dennis.heim



From: cisco-voip [mailto:cisco-voip-boun...@puck.nether.net] On Behalf Of Ahmed 
Abd EL-Rahman
Sent: Friday, March 20, 2015 5:57 PM
To: nizarshab...@live.com
Cc: cisco-voip@puck.nether.net
Subject: Re: [cisco-voip] CUCM Cluster Redundancy

Hi Nizar,
  This is what I’m asking about, the client suggested this approach and 
I was asking about the pros and cons for such approach.



Best Regards

Ahmed Abd EL-Rahman
Senior Network Engineer


From: Nazar Shabour [mailto:nizarshab...@gmail.com]
Sent: Friday, March 20, 2015 5:57 PM
To: Ahmed Abd EL-Rahman
Cc: cisco-voip@puck.nether.netmailto:cisco-voip@puck.nether.net
Subject: Re: [cisco-voip] CUCM Cluster Redundancy

hi

You mean you wan t to have 2 pubs in one cluster ?!! ? What is the benefit of 
this machine.?

regards



On Fri, Mar 20, 2015 at 5:03 PM, Ahmed Abd EL-Rahman 
ahmed.rah...@bmbgroup.commailto:ahmed.rah...@bmbgroup.com wrote:
Hi All,
  I have a UC cluster V10.5 on 2 UCS Blade servers having 1 Pub and 4 
Subs, and I’d like to ask if there is any need or benefit from having a cold 
standby virtual machine for the Pub server (a replicated VM for the Pub which 
is turned off to backup Pub functionality in case of Pub failure), and also if 
the license will be valid on this cold standby VM for the Pub so that if the 
main Pub fails and we turned on the cold standby Pub VM everything will be fine 
and the operation continues normally.

Waiting your feedback.


Best Regards

Ahmed Abd EL-Rahman
Senior Network Engineer

___
cisco-voip mailing list
cisco-voip@puck.nether.netmailto:cisco-voip@puck.nether.net
https://puck.nether.net/mailman/listinfo/cisco-voip

___
cisco-voip mailing list
cisco-voip@puck.nether.net
https://puck.nether.net/mailman/listinfo/cisco-voip


Re: [cisco-voip] (no subject)

2015-03-21 Thread Justin Steinberg
I pulled the trigger on this last night with CM 10.5.2, migrating two UCMs
changing from the 2500 template to the 7500 template.  There was really
nothing to it, other than shutting down the VM and increasing the vDisk
from 80 GB to 110 GB.

Upon startup the software automatically detected the vdisk change and ran
an 'Expanding Disk' script.   The new disk space was given to the common
partition.

I did compare a new 10.5 7500 template with the expanded 2500 to 7500
template.   The difference I noticed was that on a true fresh install of
7500 user template the active and inactive software partitions have 20GB
allocated.   The 2500 had about 14 GB to these partitions.  Expanding the
2500 user template to 7500 user only increased the common partition, the
software partitions remained at 14GB.

Justin
On Mar 21, 2015 11:03 AM, Tim Frazee tfra...@gmail.com wrote:

 the resize cop file is for 9x only, 10 has it built in. I'm running around
 with a tac case to address a stock 9x or 10x 7.5 to 10k user build that
 results with a 110G disk. doesn't leave much space for those 500 moh
 sources.

 if you shut the image down and increase from 110 to at least 112G, the
 boot process grows the common partition out.

 as a standard, any of our 10x installs for large clients, we are growing
 the disk out to 120G just to be safe.

 On Fri, Mar 20, 2015 at 3:50 PM, Erick erick...@gmail.com wrote:

 The VMware disk reallocation worked for us also going from 80gig  to
 110gig for 10.5. Were on. 9.1 prior.

 The readme in the download link Is pretty good but doesn't say outright
 what to increase it to.

 High level steps ,

 Make sure you have a good backup

 Install the cop file
 Shutdown the vm
 Change virtual disk from 80G to 110G
 Save /OK settings
 Power on VM

 It will reboot a few times while extending disk then come up fine /
 normal .


 Sent from my iPhone

 On Mar 20, 2015, at 9:34 AM, Justin Steinberg jsteinb...@gmail.com
 wrote:

 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.wikl...@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 jsteinb...@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@puck.nether.net
  https://puck.nether.net/mailman/listinfo/cisco-voip
 


 ___
 cisco-voip mailing list
 cisco-voip@puck.nether.net
 https://puck.nether.net/mailman/listinfo/cisco-voip


 ___
 cisco-voip mailing list
 cisco-voip@puck.nether.net
 https://puck.nether.net/mailman/listinfo/cisco-voip



___
cisco-voip mailing list
cisco-voip@puck.nether.net
https://puck.nether.net/mailman/listinfo/cisco-voip


Re: [cisco-voip] (no subject)

2015-03-21 Thread Tim Frazee
the resize cop file is for 9x only, 10 has it built in. I'm running around
with a tac case to address a stock 9x or 10x 7.5 to 10k user build that
results with a 110G disk. doesn't leave much space for those 500 moh
sources.

if you shut the image down and increase from 110 to at least 112G, the boot
process grows the common partition out.

as a standard, any of our 10x installs for large clients, we are growing
the disk out to 120G just to be safe.

On Fri, Mar 20, 2015 at 3:50 PM, Erick erick...@gmail.com wrote:

 The VMware disk reallocation worked for us also going from 80gig  to
 110gig for 10.5. Were on. 9.1 prior.

 The readme in the download link Is pretty good but doesn't say outright
 what to increase it to.

 High level steps ,

 Make sure you have a good backup

 Install the cop file
 Shutdown the vm
 Change virtual disk from 80G to 110G
 Save /OK settings
 Power on VM

 It will reboot a few times while extending disk then come up fine / normal
 .


 Sent from my iPhone

 On Mar 20, 2015, at 9:34 AM, Justin Steinberg jsteinb...@gmail.com
 wrote:

 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.wikl...@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 jsteinb...@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@puck.nether.net
  https://puck.nether.net/mailman/listinfo/cisco-voip
 


 ___
 cisco-voip mailing list
 cisco-voip@puck.nether.net
 https://puck.nether.net/mailman/listinfo/cisco-voip


 ___
 cisco-voip mailing list
 cisco-voip@puck.nether.net
 https://puck.nether.net/mailman/listinfo/cisco-voip


___
cisco-voip mailing list
cisco-voip@puck.nether.net
https://puck.nether.net/mailman/listinfo/cisco-voip


Re: [cisco-voip] (no subject)

2015-03-21 Thread Anthony Holloway
Justin,

How do you feel about that fact? If you kept on doing it this way, you'd
end up with 1TB common and still have 14GB active. At what point would you
consider a rebuild with the desired OVA and a restore from DRS?
On Sat, Mar 21, 2015 at 10:21 AM Justin Steinberg jsteinb...@gmail.com
wrote:

 I pulled the trigger on this last night with CM 10.5.2, migrating two UCMs
 changing from the 2500 template to the 7500 template.  There was really
 nothing to it, other than shutting down the VM and increasing the vDisk
 from 80 GB to 110 GB.

 Upon startup the software automatically detected the vdisk change and ran
 an 'Expanding Disk' script.   The new disk space was given to the common
 partition.

 I did compare a new 10.5 7500 template with the expanded 2500 to 7500
 template.   The difference I noticed was that on a true fresh install of
 7500 user template the active and inactive software partitions have 20GB
 allocated.   The 2500 had about 14 GB to these partitions.  Expanding the
 2500 user template to 7500 user only increased the common partition, the
 software partitions remained at 14GB.

 Justin
 On Mar 21, 2015 11:03 AM, Tim Frazee tfra...@gmail.com wrote:

 the resize cop file is for 9x only, 10 has it built in. I'm running
 around with a tac case to address a stock 9x or 10x 7.5 to 10k user build
 that results with a 110G disk. doesn't leave much space for those 500 moh
 sources.

 if you shut the image down and increase from 110 to at least 112G, the
 boot process grows the common partition out.

 as a standard, any of our 10x installs for large clients, we are growing
 the disk out to 120G just to be safe.

 On Fri, Mar 20, 2015 at 3:50 PM, Erick erick...@gmail.com wrote:

 The VMware disk reallocation worked for us also going from 80gig  to
 110gig for 10.5. Were on. 9.1 prior.

 The readme in the download link Is pretty good but doesn't say outright
 what to increase it to.

 High level steps ,

 Make sure you have a good backup

 Install the cop file
 Shutdown the vm
 Change virtual disk from 80G to 110G
 Save /OK settings
 Power on VM

 It will reboot a few times while extending disk then come up fine /
 normal .


 Sent from my iPhone

 On Mar 20, 2015, at 9:34 AM, Justin Steinberg jsteinb...@gmail.com
 wrote:

 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.wikl...@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 jsteinb...@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@puck.nether.net
  https://puck.nether.net/mailman/listinfo/cisco-voip
 


 ___
 cisco-voip mailing list
 cisco-voip@puck.nether.net
 https://puck.nether.net/mailman/listinfo/cisco-voip


 ___
 cisco-voip mailing list
 cisco-voip@puck.nether.net
 

Re: [cisco-voip] Translation Profile out on voice port

2015-03-21 Thread Ahmed Elnagar
Yes the idea is that I am verifying the concept not a production setup.

 

Regards,

Ahmed Elnagar | Networking Consultant | CCIE #24697, Voice



 

From: Anthony Holloway [mailto:avholloway+cisco-v...@gmail.com] 
Sent: Thursday, March 19, 2015 8:47 AM
To: Ahmed Elnagar; VOIP Group
Cc: ahmed ellboudy
Subject: Re: [cisco-voip] Translation Profile out on voice port

 

The order in which digit manipulation is processed on an outbound POTS dial 
peer is:

1.  Outbound Dial-Peer

1.  Translation Profile
2.  CLID
3.  Digit Strip
4.  Prefix Digits
5.  Forward Digits

2.  Outbound Voice Port

1.  Translation Profile

Source: CVOICE

 

You're configuration looks correct to me, so I cannot explain why it's not 
working for you.  Other than maybe a defect.  In truth, I would have just used 
the no digit-strip command on the dial-peer.  Think about the resource usage in 
your method.  You're having the router strip the one off, and then put it back 
on.  In the no digit-strip method, you simply tell the router to do nothing.  
So, 2 tasks versus 0 tasks; which one is smarter?

 

On Wed, Mar 18, 2015 at 4:26 PM Ahmed Elnagar ahmed_elna...@hotmail.com 
mailto:ahmed_elna...@hotmail.com  wrote:

Hi all;

 

It has been a very long time since I posted to the mailing list but you are 
always the “gateway of last resort” to find an expert reply :)

 

I was testing voice translation rules on a VGW with the below setup

 

I want someone to be able to call extensions “1XXX” from a site connected back 
to back to another site using E1 0/3/0 “H323 GW with CUCM in each site”…I know 
I could do it with a simple forward-digits all under the pots dial-peer in 
order for the router to send 1XXX in the ISDN setup insetead of sending XXX.

 

I am trying to verify the concept of translation profiles but I am having a 
strange issue, for the below call the pots dial-peer is matched as an outgoing 
dial-peer but as soon as this happens the debugs shows that the router check if 
there is a tx profile on the voice port “before making the digit strip” and 
translate the number and then make a dial-peer match again and then go out of 
the voice port…is that a normal behavior? My expectation is that the dial-peer 
should be matched first then apply digit strip and at the exit from the E1 
interface translation profile to be applied.

 

I cannot find any document that explains this part or document this 
approach…any ideas?

 

Below is my configuration

 

Voice translation rule 1

Rule 1 /^0../ /1\0/

 

Voice translation profile PSTN_OUT

translate called 1

 

voice-port 0/3/0:15

translation-profile outgoing PSTN_OUT

 

 

dial-peer voice 1 pots

destination-pattern 1…

port 0/3/0:15

 

 

 

Regards,

Ahmed Elnagar | Networking Consultant | CCIE #24697, Voice



 

___
cisco-voip mailing list
cisco-voip@puck.nether.net mailto:cisco-voip@puck.nether.net 
https://puck.nether.net/mailman/listinfo/cisco-voip

___
cisco-voip mailing list
cisco-voip@puck.nether.net
https://puck.nether.net/mailman/listinfo/cisco-voip


Re: [cisco-voip] Translation Profile out on voice port

2015-03-21 Thread Anthony Holloway
Right on Ahmed.  I'm always in favor of exploring how things work to gain a
better understanding, eve if it means breaking something or doing something
atypical.

For learning sake, let's break down your example step by step:

   1. Outbound Dial-Peer - The caller dialed 1000 and matched the
   destination-pattern 1...
  1. Translation Profile - There isn't one, so the number is still 1000
  2. CLID - There isn't one, so the number is still 1000
  3. Digit Strip - This is configured, by default, so the number is now
  000
  4. Prefix Digits - There isn't one, so the number is still 000
  5. Forward Digits - There isn't one, so the number is still 000
   2. Outbound Voice Port - The port command on the DP takes us to the
   right port
  1. Translation Profile - This is configured, by you, so the number is
  now 1000 (matched on /^0../ and replaced with /1\0/

Unless the CVOICE book has the order of operations wrong, I'm inclined to
think you hit a bug.  Or maybe I'm not understanding your observations of
what's happening.  Could you post actual configurations as well as debug
output for debug voice translation?



On Sat, Mar 21, 2015 at 5:40 PM Ahmed Elnagar ahmed_elna...@hotmail.com
wrote:

 Yes the idea is that I am verifying the concept not a production setup.



 *Regards,*

 *Ahmed Elnagar *|* Networking Consultant *| *CCIE #24697, Voice*

 [image: Description: Description: Description: Description: MS Green]



 *From:* Anthony Holloway [mailto:avholloway+cisco-v...@gmail.com]
 *Sent:* Thursday, March 19, 2015 8:47 AM
 *To:* Ahmed Elnagar; VOIP Group
 *Cc:* ahmed ellboudy
 *Subject:* Re: [cisco-voip] Translation Profile out on voice port



 The order in which digit manipulation is processed on an outbound POTS
 dial peer is:

1. Outbound Dial-Peer


1. Translation Profile
   2. CLID
   3. Digit Strip
   4. Prefix Digits
   5. Forward Digits


1. Outbound Voice Port


1. Translation Profile

 Source: CVOICE



 You're configuration looks correct to me, so I cannot explain why it's not
 working for you.  Other than maybe a defect.  In truth, I would have just
 used the no digit-strip command on the dial-peer.  Think about the resource
 usage in your method.  You're having the router strip the one off, and then
 put it back on.  In the no digit-strip method, you simply tell the router
 to do nothing.  So, 2 tasks versus 0 tasks; which one is smarter?



 On Wed, Mar 18, 2015 at 4:26 PM Ahmed Elnagar ahmed_elna...@hotmail.com
 wrote:

 Hi all;



 It has been a very long time since I posted to the mailing list but you
 are always the “gateway of last resort” to find an expert reply J



 I was testing voice translation rules on a VGW with the below setup



 I want someone to be able to call extensions “1XXX” from a site connected
 back to back to another site using E1 0/3/0 “H323 GW with CUCM in each
 site”…I know I could do it with a simple forward-digits all under the pots
 dial-peer in order for the router to send 1XXX in the ISDN setup insetead
 of sending XXX.



 I am trying to verify the concept of translation profiles but I am having
 a strange issue, for the below call the pots dial-peer is matched as an
 outgoing dial-peer but as soon as this happens the debugs shows that the
 router check if there is a tx profile on the voice port “before making the
 digit strip” and translate the number and then make a dial-peer match again
 and then go out of the voice port…is that a normal behavior? My expectation
 is that the dial-peer should be matched first then apply digit strip and at
 the exit from the E1 interface translation profile to be applied.



 I cannot find any document that explains this part or document this
 approach…any ideas?



 Below is my configuration



 Voice translation rule 1

 Rule 1 /^0../ /1\0/



 Voice translation profile PSTN_OUT

 translate called 1



 voice-port 0/3/0:15

 translation-profile outgoing PSTN_OUT





 dial-peer voice 1 pots

 destination-pattern 1…

 port 0/3/0:15







 *Regards,*

 *Ahmed Elnagar *|* Networking Consultant *| *CCIE #24697, Voice*

 [image: Description: Description: Description: Description: MS Green]



 ___
 cisco-voip mailing list
 cisco-voip@puck.nether.net
 https://puck.nether.net/mailman/listinfo/cisco-voip


___
cisco-voip mailing list
cisco-voip@puck.nether.net
https://puck.nether.net/mailman/listinfo/cisco-voip


Re: [cisco-voip] (no subject)

2015-03-21 Thread Heim, Dennis
You could always do a migration with PCD, right?

Dennis Heim | Emerging Technology Architect (Collaboration)
World Wide Technology, Inc. | +1 314-212-1814
[twitter]https://twitter.com/CollabSensei
[chat]xmpp:dennis.h...@wwt.com[Phone]tel:+13142121814[video]sip:dennis.h...@wwt.com
Innovation happens on project squared -- 
http://www.projectsquared.comhttp://www.projectsquared.com/

Click here to join me in my Collaboration Meeting 
Roomhttps://wwt.webex.com/meet/dennis.heim



From: cisco-voip [mailto:cisco-voip-boun...@puck.nether.net] On Behalf Of 
Anthony Holloway
Sent: Saturday, March 21, 2015 6:32 PM
To: Justin Steinberg; Tim Frazee
Cc: Cisco VOIP
Subject: Re: [cisco-voip] (no subject)

Justin,

How do you feel about that fact? If you kept on doing it this way, you'd end up 
with 1TB common and still have 14GB active. At what point would you consider a 
rebuild with the desired OVA and a restore from DRS?
On Sat, Mar 21, 2015 at 10:21 AM Justin Steinberg 
jsteinb...@gmail.commailto:jsteinb...@gmail.com wrote:

I pulled the trigger on this last night with CM 10.5.2, migrating two UCMs 
changing from the 2500 template to the 7500 template.  There was really nothing 
to it, other than shutting down the VM and increasing the vDisk from 80 GB to 
110 GB.

Upon startup the software automatically detected the vdisk change and ran an 
'Expanding Disk' script.   The new disk space was given to the common partition.

I did compare a new 10.5 7500 template with the expanded 2500 to 7500 template. 
  The difference I noticed was that on a true fresh install of 7500 user 
template the active and inactive software partitions have 20GB allocated.   The 
2500 had about 14 GB to these partitions.  Expanding the 2500 user template to 
7500 user only increased the common partition, the software partitions remained 
at 14GB.

Justin
On Mar 21, 2015 11:03 AM, Tim Frazee 
tfra...@gmail.commailto:tfra...@gmail.com wrote:
the resize cop file is for 9x only, 10 has it built in. I'm running around with 
a tac case to address a stock 9x or 10x 7.5 to 10k user build that results with 
a 110G disk. doesn't leave much space for those 500 moh sources.
if you shut the image down and increase from 110 to at least 112G, the boot 
process grows the common partition out.
as a standard, any of our 10x installs for large clients, we are growing the 
disk out to 120G just to be safe.

On Fri, Mar 20, 2015 at 3:50 PM, Erick 
erick...@gmail.commailto:erick...@gmail.com wrote:
The VMware disk reallocation worked for us also going from 80gig  to 110gig for 
10.5. Were on. 9.1 prior.

The readme in the download link Is pretty good but doesn't say outright what to 
increase it to.

High level steps ,

Make sure you have a good backup

Install the cop file
Shutdown the vm
Change virtual disk from 80G to 110G
Save /OK settings
Power on VM

It will reboot a few times while extending disk then come up fine / normal .


Sent from my iPhone

On Mar 20, 2015, at 9:34 AM, Justin Steinberg 
jsteinb...@gmail.commailto:jsteinb...@gmail.com wrote:
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.wikl...@gmail.commailto:roger.wikl...@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 
jsteinb...@gmail.commailto:jsteinb...@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