cancel
Showing results for 
Search instead for 
Did you mean: 
cancel
958
Views
75
Helpful
33
Replies
Highlighted
Beginner

Business Edition 6k upcoming Rls

After Prime Collaboration gone EOS, how many applications are available for C220M?

Expressway-c and Expressway-E are included or are available as a separate .ova format?

Any consolidated implementation and configurational document for BE6k along with ISR 4XXX routers and Expressway -C and expressway-E?

How can we design BE6K + ISR 4xxx + Expressway-c & E within a same building but different data centers as fully HA format?any relevant CVD?

 

 

33 REPLIES 33
Highlighted
Beginner

Hi Nithin,

Hope you are fine. Once again i need your help regarding HA.

Design diagram is attached here. please check and let me confirm that for HA configuration (Publisher + Subscriber) we need to connect BE6K and ISR4431 on LAN (Same Subnet) or can configure on WAN as well.

If LAN and WAN both are the possibilities for HA then what is the switch over/response time( Shifting on subscriber and revert back) in case of network failure?

Note: i will use ISDN E1/PRI for each gateway instead of SIP trunks.

 

 

 
 

 

Highlighted

You  can do clustering over the Wan, but you need to consider below prerequisites. And you need to make sure all required ports are opened through the wan. if you meet all prerequisites, switch over will be same. 

 

if your TSP supports, you can have HA on PRI, and it should be done  by TSP. 

 

 

https://www.ciscopress.com/articles/article.asp?p=2743756&seqNum=6

Port Usage

https://www.cisco.com/c/en/us/td/docs/voice_ip_comm/cucm/admin/12_0_1/systemConfig/cucm_b_system-configuration-guide-1201/cucm_b_system-configuration-guide-1201_chapter_01010110.html

Clustering over the IP WAN

Cisco supports CUCM clustered over an IP WAN. Figure 2-7 shows the publisher and two subscribers at one location while another pair of subscribers from the same cluster resides at a different location. The QoS-enabled IP WAN connects the two sites. Note the requirement of a round trip time less than 80 ms between the sites. This requirement is in support of database replication occurring between the publisher and all the subscribers in the cluster.

 

 

Figure 2-7 Clustering over the WAN

Some of the characteristics of this model include:

  • Applications and CUCM servers of the same cluster can be distributed over the IP WAN.
  • The IP WAN carries intracluster server communication and signaling.
  • Limited number of sites:
    • Two to four sites for local failover (two CUCM servers per site)
    • Up to eight sites for remote failover across the IP WAN (one CUCM server per site).

The cluster design is useful for customers who require more functionality than the limited feature set that is offered by Cisco Unified SRST. This network design also allows remote offices to support more IP phones than SRST if the connection to the primary CUCM is lost.

Design Guidelines for Clustering over WAN Deployment Model

Although the distributed single-cluster call-processing model offers some significant advantages, it must adhere to these strict design guidelines:

  • Two CUCM servers in a cluster must have a maximum round-trip delay of 80 ms between them. Because of this strict guideline, this design can be used only between closely connected, high-speed locations.
  • A minimum of 1.544 Mbps (T1) of bandwidth is required for Intra-Cluster Communication Signaling (ICCS) between each site and every other site that is clustered over the WAN. This bandwidth supports up to 10,000 busy hour call attempts (BHCAs) within the cluster. The BHCA represents the number of call attempts that are made during the busiest hour of the day.
  • In addition to the bandwidth required for ICCS traffic, a minimum of 1.544 Mbps (T1) of bandwidth is required for database and other inter-server traffic between the publisher and every subscriber node within the cluster.
  • Up to eight small sites are supported using the remote failover deployment model. Remote failover allows you to deploy one server per location. (A maximum of eight call-processing servers are supported in a cluster.) If CUCM fails, IP phones register to another server over the WAN. Therefore, Cisco Unified SRST is not required in this deployment model (although it is supported). The remote failover design may require significant additional bandwidth, depending on the number of telephones at each location.

 

 

==Please rate all useful posts and mark as answer if it solves your issue==

View solution in original post

Highlighted

Dear Nithin,

 

Hope you are fine.

"Two CUCM servers in a cluster must have a maximum round-trip delay of 80 ms between them". 

This round trip delay 80 ms threshold is default/fix or we can change this threshold to prevent frequent splitting in between Publisher & Subscriber? Secondly after switch back from subscriber to publisher, every configuration that have been made on subscriber will be shown/implement on publisher after coming back or we need to reconfigure on publisher..?

 

 

  

 

 

Highlighted

This round trip delay 80 ms threshold is default/fix or we can change this threshold to prevent frequent splitting in between Publisher & Subscriber? This is the recommended round trip delay between publisher and subscriber to avoid db replication issues  when u do the  clustering through WAN.  This value is  not a setting on CUCM. 

 

subscriber to publisher, every configuration that have been made on subscriber will be shown/implement on publisher after coming back or we need to reconfigure on publisher..? its   recommended to make configurations changes on publisher. what ever configurations you make on publisher will be replicated to subscriber if DB replication is good. if publisher is down you cannot make any administrative changes  Only end user facing features can be modified.

 

 

 

 

==Please rate all useful posts and mark as answer if it solves your issue==

View solution in original post

Content for Community-Ad