[cisco-voip] Migrating from C200 blades to HP
Mike King
me at mpking.com
Fri Aug 17 12:51:25 EDT 2012
According to the Wiki, CMBE6K is not supported on spec based hardware.
(3rd line of the table in the below link)
http://docwiki.cisco.com/wiki/Cisco_Unified_Communications_Manager_Business_Edition_6000
On Fri, Aug 17, 2012 at 7:53 AM, Matthew Loraditch <
MLoraditch at heliontechnologies.com> wrote:
> ** **
>
> That is a very interesting question. Pretty much all the CMBE6K docs
> reference buying the TRC hardware C200M2 or now C220M3, but none of it says
> it’s required… of course nothing I’ve found says you can use specs hardware
> for it either… Please let us know what answer you find. I have a feeling
> you will have to run that question up to your account team.****
>
> ** **
>
> Matthew G. Loraditch – CCNP-Voice, CCNA, CCDA
>
> 1965 Greenspring Drive
> Timonium, MD 21093
>
> voice. 410.252.8830
> fax. 410.252.9284
>
> Twitter <http://twitter.com/heliontech> | Facebook<http://www.facebook.com/#!/pages/Helion/252157915296>
> | Website <http://www.heliontechnologies.com/> | Email Support<support at heliontechnologies.com?subject=Technical%20Support%20Request>
> ****
>
> ** **
>
> ** **
>
> *From:* cisco-voip-bounces at puck.nether.net [mailto:
> cisco-voip-bounces at puck.nether.net] *On Behalf Of *Kevin Hobson
> *Sent:* Thursday, August 16, 2012 3:04 PM
> *To:* 'Lelio Fulgenzi'; 'Chris Ward (chrward)'
> *Cc:* cisco-voip at puck.nether.net
>
> *Subject:* Re: [cisco-voip] Migrating from C200 blades to HP****
>
> ** **
>
> Hi,****
>
> ** **
>
> I was thinking of just shifting them to the blades.****
>
> ** **
>
> If its moved off the C200's though it becomes a full CUCM cluster?
>
> What are the licensing implications with this?
>
> Thanks
>
> Kev****
>
> ** **
>
> *From:* Lelio Fulgenzi [mailto:lelio at uoguelph.ca]
> *Sent:* 16 August 2012 18:31
> *To:* Chris Ward (chrward)
> *Cc:* Kevin Hobson; cisco-voip at puck.nether.net
> *Subject:* Re: [cisco-voip] Migrating from C200 blades to HP****
>
> ** **
>
> Do you need vMotion to do this or is that just for keeping them live
> during the move?
>
> Sent from my iPhone...****
>
> ** **
>
> "There's no place like 127.0.0.1"****
>
>
> On Aug 16, 2012, at 1:01 PM, "Chris Ward (chrward)" <chrward at cisco.com>
> wrote:****
>
> Why would you want to rebuild it? Can’t you just shut them down on the
> UCS and boot them on the HP? Probably take an hour or two to move the data
> but then you don’t need to re-install/re-configure anything.****
>
> ****
>
> +Chris****
>
> Unity Connection TME****
>
> ****
>
> *From:* cisco-voip-bounces at puck.nether.net [
> mailto:cisco-voip-bounces at puck.nether.net<cisco-voip-bounces at puck.nether.net>]
> *On Behalf Of *Kevin Hobson
> *Sent:* Thursday, August 16, 2012 2:56 AM
> *To:* cisco-voip at puck.nether.net
> *Subject:* [cisco-voip] Migrating from C200 blades to HP****
>
> ****
>
> All,****
>
> ****
>
> I have a customer who i am looking to migrate off the C blade into a HP
> blade solution and had a couple of questions:****
>
> ****
>
> **1. **They maybe running Business Edition 6000 which as i
> understand it is the full UCM just limited by the platform it is on at the
> moment. So i believe as long as the ip and password between the cluster is
> the same this can be backed up and restored on the new VM?****
>
> **2. **How would i go about migrating the licenses over as
> obviously these will be different Virtual Machines sat on a different
> platform?****
>
> ****
>
> Cheers****
>
> ****
>
> Kev****
>
> _______________________________________________
> 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/20120817/4f94a4ee/attachment.html>
More information about the cisco-voip
mailing list