[cisco-voip] Standby publisher

Fri Jul 2 08:46:48 EDT 2010

Yeah I think that would be a good idea, but still the virtualization is still not that mature...plus it is exclusively available for UCS B series only...I think in the future this would be very applicable.

 Best Regards;
  Ahmed Elnagar
  Senior Network PS Engineer
  Mob: +2019-0016211
  CCIE#24697 (Voice)

-----Original Message-----
From: Eric Butcher [mailto:Eric.Butcher at cdw.com] 
Sent: Thursday, July 01, 2010 7:52 PM
To: Ryan Ratliff; Ahmed Elnagar
Cc: cisco-voip at puck.nether.net
Subject: RE: [cisco-voip] Standby publisher

You bring up a good point.  The best way to support this is a virtualized CUCM 8.x publisher on UCS-B series.  The mac doesn't really matter at that point since you can configure a fake one and use it for the license.

Eric Butcher
Cisco Unified Communications Engineer
CDW Professional Services
11711 N Meridian, Ste 225
Carmel, IN  46032
C 317.569.4282 - IP Phone
  765.744.1458 - Mobile
  eric.butcher at cdw.com
www.cdw.com

-----Original Message-----
From: cisco-voip-bounces at puck.nether.net [mailto:cisco-voip-bounces at puck.nether.net] On Behalf Of Ryan Ratliff
Sent: Thursday, July 01, 2010 12:50 PM
To: Ahmed Elnagar
Cc: cisco-voip at puck.nether.net
Subject: Re: [cisco-voip] Standby publisher

Then you need to get such a requirement prioritized by BU. Having your account team work with the marketing folks in the BU is the way to get this done.

You can also look at moving to a virtualized publisher now.

-Ryan

On Jul 1, 2010, at 11:49 AM, Ahmed Elnagar wrote:

No the issue is some customers "especially call centers and service providers" almost have daily changes and add on...they cannot withstand the time that a Publisher is down...we need another server in the cluster that replicates that DB real time for CUCM Publisher and it can act as a Publisher in the event that the "primary" Publisher fail.

 Best Regards;
  Ahmed Elnagar
  Senior Network PS Engineer
  Mob: +2019-0016211
 CCIE#24697 (Voice)

-----Original Message-----
From: Bill [mailto:bill at hitechconnection.net]
Sent: Thursday, July 01, 2010 5:18 PM
To: Ahmed Elnagar; 'Ryan Ratliff'
Cc: cisco-voip at puck.nether.net
Subject: RE: [cisco-voip] Standby publisherpublisher. This changes a bit in6.x where the "user facing features" are written on each node,and replicated out to other nodes in realtime. This is what lets youset and clear CFA with the pub down in later versions.

Yes it's called a subscriber. :)

Like the other person that responded said you are adding another level of redundancy to an already redundant system.

-----Original Message-----
From: cisco-voip-bounces at puck.nether.net
[mailto:cisco-voip-bounces at puck.nether.net] On Behalf Of Ahmed Elnagar
Sent: Thursday, July 01, 2010 9:02 AM
To: Ryan Ratliff
Cc: cisco-voip at puck.nether.net
Subject: Re: [cisco-voip] Standby publisherpublisher. This changes a bit in6.x where the "user facing features" are written on each node,and replicated out to other nodes in realtime. This is what lets youset and clear CFA with the pub down in later versions.

Ryan;

Do Cisco has any plans for a "Backup Publisher" I have this discussion with customers since the 4.x train till now.

 Best Regards;
  Ahmed Elnagar
  Senior Network PS Engineer
  Mob: +2019-0016211
 CCIE#24697 (Voice)

-----Original Message-----
From: Ryan Ratliff [mailto:rratliff at cisco.com]
Sent: Thursday, July 01, 2010 4:28 PM
To: Bill
Cc: Ahmed Elnagar; 'Andrius Kislas'; cisco-voip at puck.nether.net
Subject: Re: [cisco-voip] Standby publisherpublisher. 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.

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.

See
http://www.cisco.com/en/US/docs/voice_ip_comm/cucm/rel_notes/6_0_1/cucm-rel_
note-601a.html#wp44437 for specfics.

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.

-Ryan

On Jul 1, 2010, at 9:18 AM, Bill wrote:

Also, at least in the 4.x days, you can still make changes to the subscriber if the publisher is down. 

-----Original Message-----
From: cisco-voip-bounces at puck.nether.net
[mailto:cisco-voip-bounces at puck.nether.net] On Behalf Of Ahmed Elnagar
Sent: Thursday, July 01, 2010 7:43 AM
To: Andrius Kislas
Cc: cisco-voip at puck.nether.net
Subject: Re: [cisco-voip] Standby publisher

What about the license? The license relates to the MAC address of the server??

Best Regards;
 Ahmed Elnagar
 Senior Network PS Engineer
 Mob: +2019-0016211
CCIE#24697 (Voice)

-----Original Message-----
From: cisco-voip-bounces at puck.nether.net
[mailto:cisco-voip-bounces at puck.nether.net] On Behalf Of Andrius Kislas
Sent: Thursday, July 01, 2010 1:17 PM
To: Cisco Voip
Subject: [cisco-voip] Standby publisher

Hi All.

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.

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.

Does it sound fine or are there any caveats for such approach?

Regards,
Andrius

_______________________________________________
cisco-voip mailing list
cisco-voip at puck.nether.net
https://puck.nether.net/mailman/listinfo/cisco-voip
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.
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. 

_______________________________________________
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

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.
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. 

_______________________________________________
cisco-voip mailing list
cisco-voip at puck.nether.net
https://puck.nether.net/mailman/listinfo/cisco-voip

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. 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. 

_______________________________________________
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
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. 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. 