[cisco-voip] UC on UCS auto failover in hardware

[Wes Sisk]

Eric,

That used to be 100% true.  For better or worse Truth is a function of 
time T=f(t).

VMotion is starting to be supported:
http://docwiki.cisco.com/wiki/Unified_Communications_VMware_Requirements#VMware_vMotion

Regards,
Wes

On 7/13/2011 2:16 PM, Eric Butcher wrote:
>
> I think what you're describing is VMotion and is very much not 
> supported.  (Moving an active VM on a blade that is having trouble to 
> another blade in production)
>
> I do believe you can shut down the VM completely, copy it to a new 
> blade, and turn it back up.
>
> *Eric Butcher | **CDW **Professional Services*
>
> ( 317.569.4282 (SNR) *|**eric.butcher at cdw.com 
> <mailto:eric.butcher at cdw.com>
>
> *From:*cisco-voip-bounces at puck.nether.net 
> [mailto:cisco-voip-bounces at puck.nether.net] *On Behalf Of *ciscozest
> *Sent:* Wednesday, July 13, 2011 6:51 AM
> *To:* cisco-voip mailinglist
> *Subject:* [cisco-voip] UC on UCS auto failover in hardware
>
> I am going to deploy UC on UCS and I am aware that we can move the UC 
> application from one blade server to other slot or UCS chassis easily. 
> However the question is how much redundancy/failover can be supported 
> with UC on UCS system.
>
> An example for CallManager; if the Subscriber 1 server is down, all 
> the voice endpoints will failover to the backup CCM server 
> automatically. This is application redundancy and auto failover.
>
> As for hardware ie: blade server /disks are down for any reason, would 
> UCS system be able to auto failover the UC applications into another 
> spare blade server?
>
> As far as I know from reading some doco, we have to manualy 
> dissassociate service profile and reassociate that to the spare blade 
> and then power it ON to achieve the recovery.
>
> Can anyone with UC on UCS experience share this thought?
>
> Thank you,
>
>
> _______________________________________________
> 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/20110713/82c31d2a/attachment.html>