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?
Solved! Go to Solution.
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.
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.
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:
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:
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..?
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.