<html xmlns:v="urn:schemas-microsoft-com:vml" xmlns:o="urn:schemas-microsoft-com:office:office" xmlns:w="urn:schemas-microsoft-com:office:word" xmlns:st1="urn:schemas-microsoft-com:office:smarttags" xmlns="http://www.w3.org/TR/REC-html40">
<head>
<META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=us-ascii">
<meta name=Generator content="Microsoft Word 11 (filtered medium)">
<!--[if !mso]>
<style>
v\:* {behavior:url(#default#VML);}
o\:* {behavior:url(#default#VML);}
w\:* {behavior:url(#default#VML);}
.shape {behavior:url(#default#VML);}
</style>
<![endif]--><o:SmartTagType
namespaceuri="urn:schemas-microsoft-com:office:smarttags" name="PostalCode"/>
<o:SmartTagType namespaceuri="urn:schemas-microsoft-com:office:smarttags"
name="State"/>
<o:SmartTagType namespaceuri="urn:schemas-microsoft-com:office:smarttags"
name="City"/>
<o:SmartTagType namespaceuri="urn:schemas-microsoft-com:office:smarttags"
name="Street"/>
<o:SmartTagType namespaceuri="urn:schemas-microsoft-com:office:smarttags"
name="address"/>
<o:SmartTagType namespaceuri="urn:schemas-microsoft-com:office:smarttags"
name="place"/>
<!--[if !mso]>
<style>
st1\:*{behavior:url(#default#ieooui) }
</style>
<![endif]-->
<style>
<!--
/* Font Definitions */
@font-face
{font-family:Tahoma;
panose-1:2 11 6 4 3 5 4 4 2 4;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
{margin:0in;
margin-bottom:.0001pt;
font-size:12.0pt;
font-family:"Times New Roman";}
a:link, span.MsoHyperlink
{color:blue;
text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
{color:blue;
text-decoration:underline;}
span.EmailStyle17
{mso-style-type:personal-reply;
font-family:Arial;
color:navy;}
@page Section1
{size:8.5in 11.0in;
margin:1.0in 1.25in 1.0in 1.25in;}
div.Section1
{page:Section1;}
-->
</style>
</head>
<body lang=EN-US link=blue vlink=blue>
<div class=Section1>
<p class=MsoNormal><font size=2 color=navy face=Arial><span style='font-size:
10.0pt;font-family:Arial;color:navy'>I think we are using product and hardware
instead of design. <o:p></o:p></span></font></p>
<p class=MsoNormal><font size=2 color=navy face=Arial><span style='font-size:
10.0pt;font-family:Arial;color:navy'><o:p> </o:p></span></font></p>
<div>
<div class=MsoNormal align=center style='text-align:center'><font size=3
face="Times New Roman"><span style='font-size:12.0pt'>
<hr size=2 width="100%" align=center tabindex=-1>
</span></font></div>
<p class=MsoNormal><b><font size=2 face=Tahoma><span style='font-size:10.0pt;
font-family:Tahoma;font-weight:bold'>From:</span></font></b><font size=2
face=Tahoma><span style='font-size:10.0pt;font-family:Tahoma'> cisco-voip-bounces@puck.nether.net
[mailto:cisco-voip-bounces@puck.nether.net] <b><span style='font-weight:bold'>On
Behalf Of </span></b>Matthew Saskin<br>
<b><span style='font-weight:bold'>Sent:</span></b> Thursday, July 01, 2010
10:02 AM<br>
<b><span style='font-weight:bold'>To:</span></b> Andrius Kislas<br>
<b><span style='font-weight:bold'>Cc:</span></b> cisco-voip@puck.nether.net<br>
<b><span style='font-weight:bold'>Subject:</span></b> Re: [cisco-voip] Standby
publisher</span></font><o:p></o:p></p>
</div>
<p class=MsoNormal><font size=3 face="Times New Roman"><span style='font-size:
12.0pt'><o:p> </o:p></span></font></p>
<p class=MsoNormal style='margin-bottom:12.0pt'><font size=3
face="Times New Roman"><span style='font-size:12.0pt'>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 <st1:City w:st="on"><st1:place w:st="on">hudson</st1:place></st1:City>),
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>
<o:p></o:p></span></font></p>
<div>
<p class=MsoNormal><font size=3 face="Times New Roman"><span style='font-size:
12.0pt'>On Thu, Jul 1, 2010 at 10:43 AM, Andrius Kislas <<a
href="mailto:andrius-conf@kislas.lt">andrius-conf@kislas.lt</a>> wrote:<o:p></o:p></span></font></p>
<p class=MsoNormal><font size=3 face="Times New Roman"><span style='font-size:
12.0pt'>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"><span style='color:#888888'><br>
Andrius</span></font><o:p></o:p></span></font></p>
<div>
<div>
<p class=MsoNormal><font size=3 face="Times New Roman"><span style='font-size:
12.0pt'><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 <st1:place w:st="on">N Meridian</st1:place>, <st1:address w:st="on"><st1:Street
w:st="on">Ste</st1:Street> 225</st1:address><br>
> <st1:place w:st="on"><st1:City w:st="on">Carmel</st1:City>, <st1:State
w:st="on">IN</st1:State> <st1:PostalCode w:st="on">46032</st1:PostalCode></st1:place><br>
> C 317.569.4282 - IP Phone<br>
> 765.744.1458 - <st1:City w:st="on"><st1:place w:st="on">Mobile</st1:place></st1:City><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><o:p></o:p></span></font></p>
</div>
</div>
</div>
<p class=MsoNormal><font size=3 face="Times New Roman"><span style='font-size:
12.0pt'><o:p> </o:p></span></font></p>
</div>
</body>
</html>