If the physical hardware (and therefore MAC) address changes, you'll need to engage TAC to re-host your license.<br><br>This begs the question - why would it take a week of downtime? Even if you do a publisher rebuild and restore, it should take 24 hours top and that's including getting new hardware from Cisco provided you're in a moderately serviced area. If you're not in a moderately serviced area, I have two questions. 1) why is the callmanager publisher not in an area where proper hardware replacement coverage can be guaranteed and/or 2) why is an on-site spare not there for a cluster servicing 30K+ phones. Just some thoughts...<br>
<br clear="all">Matthew Saskin<br><a href="mailto:msaskin@gmail.com">msaskin@gmail.com</a><br>203-253-9571<br><br>July 18, 2010 - 1500m swim (in the hudson), 40k bike, 10k run<br>Please support the Leukemia & Lyphoma Society<br>
<a href="http://pages.teamintraining.org/nyc/nyctri10/msaskin">http://pages.teamintraining.org/nyc/nyctri10/msaskin</a><br>
<br><br><div class="gmail_quote">On Thu, Jul 1, 2010 at 10:43 AM, Andrius Kislas <span dir="ltr"><<a href="mailto:andrius-conf@kislas.lt">andrius-conf@kislas.lt</a>></span> wrote:<br><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
Why would I need to involve TAC? I haven't done publisher restoration<br>
process, but reading Desister Recovery doc I haven't noticed any notes<br>
ragarding MAC address change. So I am guessing restoration procedure<br>
from backups will take care of new MAC, won't it?<br>
<br>
Also I do agree this is a already redundant system from call processing<br>
perspective, but imagine 60K mega cluster and not being able to make any<br>
changes for a week (that's without publisher). So I am adressing exactly<br>
this situation.<br>
<font color="#888888"><br>
Andrius<br>
</font><div><div></div><div class="h5"><br>
On 2010.07.01 16:59, Eric Butcher wrote:<br>
> The cost / benefit analysis of this is a pretty hard sell, but if you're looking to squeeze that last bit of redundancy out of an already very redundant phone system... It can be done. Not as simple as plugging it in, powering it up, and loading licenses though. There would need to be a tac case involved anyway.<br>
><br>
><br>
> Eric Butcher<br>
> Cisco Unified Communications Engineer<br>
> CDW Professional Services<br>
> 11711 N Meridian, Ste 225<br>
> Carmel, IN 46032<br>
> C 317.569.4282 - IP Phone<br>
> 765.744.1458 - Mobile<br>
> <a href="mailto:eric.butcher@cdw.com">eric.butcher@cdw.com</a><br>
> <a href="http://www.cdw.com" target="_blank">www.cdw.com</a><br>
><br>
><br>
> -----Original Message-----<br>
> From: <a href="mailto:cisco-voip-bounces@puck.nether.net">cisco-voip-bounces@puck.nether.net</a> [mailto:<a href="mailto:cisco-voip-bounces@puck.nether.net">cisco-voip-bounces@puck.nether.net</a>] On Behalf Of Ryan Ratliff<br>
> Sent: Thursday, July 01, 2010 9:28 AM<br>
> To: Bill<br>
> Cc: <a href="mailto:cisco-voip@puck.nether.net">cisco-voip@puck.nether.net</a><br>
> Subject: Re: [cisco-voip] Standby publisher<br>
><br>
> No you can't. All database changes can only be made to the publisher. This changes a bit in 6.x where the "user facing features" are written on each node, and replicated out to other nodes in realtime. This is what lets you set and clear CFA with the pub down in later versions.<br>
><br>
> See <a href="http://www.cisco.com/en/US/docs/voice_ip_comm/cucm/rel_notes/6_0_1/cucm-rel_note-601a.html#wp44437" target="_blank">http://www.cisco.com/en/US/docs/voice_ip_comm/cucm/rel_notes/6_0_1/cucm-rel_note-601a.html#wp44437</a> for specfics.<br>
><br>
> Having a standby publisher installed and ready for restore is not a bad idea but you will be restricted by licensing (P1 TAC SR with the licensing team should get you rehosted pretty quickly I hope). The only thing to worry about wrt to IP address is if the pub is specified in System->Server by IP address this would cause problems after the restore. This could be avoided simply by changing the IP address to match the failed publisher before starting the restore.<br>
><br>
> -Ryan<br>
><br>
> On Jul 1, 2010, at 9:18 AM, Bill wrote:<br>
><br>
> Also, at least in the 4.x days, you can still make changes to the subscriber if the publisher is down.<br>
><br>
> -----Original Message-----<br>
> From: <a href="mailto:cisco-voip-bounces@puck.nether.net">cisco-voip-bounces@puck.nether.net</a><br>
> [mailto:<a href="mailto:cisco-voip-bounces@puck.nether.net">cisco-voip-bounces@puck.nether.net</a>] On Behalf Of Ahmed Elnagar<br>
> Sent: Thursday, July 01, 2010 7:43 AM<br>
> To: Andrius Kislas<br>
> Cc: <a href="mailto:cisco-voip@puck.nether.net">cisco-voip@puck.nether.net</a><br>
> Subject: Re: [cisco-voip] Standby publisher<br>
><br>
> What about the license? The license relates to the MAC address of the server??<br>
><br>
> Best Regards;<br>
> Ahmed Elnagar<br>
> Senior Network PS Engineer<br>
> Mob: +2019-0016211<br>
> CCIE#24697 (Voice)<br>
><br>
><br>
><br>
> -----Original Message-----<br>
> From: <a href="mailto:cisco-voip-bounces@puck.nether.net">cisco-voip-bounces@puck.nether.net</a><br>
> [mailto:<a href="mailto:cisco-voip-bounces@puck.nether.net">cisco-voip-bounces@puck.nether.net</a>] On Behalf Of Andrius Kislas<br>
> Sent: Thursday, July 01, 2010 1:17 PM<br>
> To: Cisco Voip<br>
> Subject: [cisco-voip] Standby publisher<br>
><br>
> Hi All.<br>
><br>
> Correct me if I am wrong, but when the publisher fails the biggest impact we have is not being able to change configuration. In large environments this might be serious impact.<br>
><br>
> My question is - does anybody use a standby/cold publisher that has the only task - sit and wait until the primary publisher fails? This standby published would ba standalone (not a member of existing cluster), would have different IP address (in the same subnet) and the same name as existing publisher, would have no licenses uploaded and would be kept in the same version as primary publisher. During primary publisher failure we would need to change IP address and perform disaster recovery. This would save us some time that we would typiacly need to get new server, install new publisher, upgrade it and finally perform recovery.<br>
><br>
> Does it sound fine or are there any caveats for such approach?<br>
><br>
> Regards,<br>
> Andrius<br>
><br>
> _______________________________________________<br>
> cisco-voip mailing list<br>
> <a href="mailto:cisco-voip@puck.nether.net">cisco-voip@puck.nether.net</a><br>
> <a href="https://puck.nether.net/mailman/listinfo/cisco-voip" target="_blank">https://puck.nether.net/mailman/listinfo/cisco-voip</a><br>
> Disclaimer: NOTICE The information contained in this message is confidential and is intended for the addressee(s) only. If you have received this message in error or there are any problems please notify the originator immediately.<br>
> The unauthorized use, disclosure, copying or alteration of this message is strictly forbidden. Raya will not be liable for direct, special, indirect or consequential damages arising from alteration of the contents of this message by a third party or as a result of any malicious code or virus being passed on. Views expressed in this communication are not necessarily those of Raya.If you have received this message in error, please notify the sender immediately by email, facsimile or telephone and return and/or destroy the original message.<br>
><br>
> _______________________________________________<br>
> cisco-voip mailing list<br>
> <a href="mailto:cisco-voip@puck.nether.net">cisco-voip@puck.nether.net</a><br>
> <a href="https://puck.nether.net/mailman/listinfo/cisco-voip" target="_blank">https://puck.nether.net/mailman/listinfo/cisco-voip</a><br>
><br>
><br>
> _______________________________________________<br>
> cisco-voip mailing list<br>
> <a href="mailto:cisco-voip@puck.nether.net">cisco-voip@puck.nether.net</a><br>
> <a href="https://puck.nether.net/mailman/listinfo/cisco-voip" target="_blank">https://puck.nether.net/mailman/listinfo/cisco-voip</a><br>
><br>
><br>
> _______________________________________________<br>
> cisco-voip mailing list<br>
> <a href="mailto:cisco-voip@puck.nether.net">cisco-voip@puck.nether.net</a><br>
> <a href="https://puck.nether.net/mailman/listinfo/cisco-voip" target="_blank">https://puck.nether.net/mailman/listinfo/cisco-voip</a><br>
><br>
> _______________________________________________<br>
> cisco-voip mailing list<br>
> <a href="mailto:cisco-voip@puck.nether.net">cisco-voip@puck.nether.net</a><br>
> <a href="https://puck.nether.net/mailman/listinfo/cisco-voip" target="_blank">https://puck.nether.net/mailman/listinfo/cisco-voip</a><br>
><br>
<br>
_______________________________________________<br>
cisco-voip mailing list<br>
<a href="mailto:cisco-voip@puck.nether.net">cisco-voip@puck.nether.net</a><br>
<a href="https://puck.nether.net/mailman/listinfo/cisco-voip" target="_blank">https://puck.nether.net/mailman/listinfo/cisco-voip</a><br>
</div></div></blockquote></div><br>