Ahmed, The Expressway cluster (C or E) can have 6 member nodes (1 primary and 5 subordinate peer nodes). Here is the clustering guide for 8.7 (but all versions have an equivalent guide): http://www.cisco.com/c/dam/en/us/td/docs/voice_ip_comm/expressway/config_guide/X8-7/Cisco-Expressway-Cluster-Creation-and-Maintenance-Deployment-Guide-X8-7.pdf
Important note; if you use Expressway C clustering; CUCM will need to resolve SRV records in the FQDN of the cluster nodes as well. In fact, if you do not advertise SRV in the FQDN of the Expressway C cluster nodes, you'll win this prize (slated for fix in 12 but you'd need to get an ES for a fix in 11 or 10): http://cdets.cisco.com/apps/dumpcr?&content=summary&format=html&identifier=CSCvd15723 Sent from my iPhone On Mar 12, 2017, at 6:33 PM, Ahmed Abd EL-Rahman <[email protected]<mailto:[email protected]>> wrote: Thanks James, One more point if you please, what about Expressway HA setup? How many EXP-C and EXP-E servers can be in one setup? And could the HA units reside over the WAN in different site? And if yes what’s the requirements for that? BR Ahmed Abd EL-Rahman Senior Network Engineer Sent from my iPhone On Mar 12, 2017, at 8:09 PM, James Buchanan <[email protected]<mailto:[email protected]><mailto:[email protected]>> wrote: Also, regarding your DNS SRV, just pick a cluster to return in the query and ILS takes it from there. Check out the DNS section in this doc: http://www.cisco.com/c/en/us/support/unified-communications/expressway-series/products-installation-and-configuration-guides-list.html Thanks, James On 12 Mar 2017 16:56, "Ahmed Abd EL-Rahman" <[email protected]<mailto:[email protected]><mailto:[email protected]>> wrote: Also if the Expressway supports working with multiple CUCM/IMP clusters, how can it determine to which cluster it will direct the user client registration request ? Also as mentioned there is single DNS and single domain for the whole 4 clusters, so how the SRV records will be added for service discovery specially from inside the company to direct each user to its correct cluster? For example, this is one of the SRV records that should be added to the internal DNS and answers the queries with CUCM IP address: (_cisco-uds._tcp.domain.com<http://tcp.domain.com>), so how such record will work properly to direct each user request to its own cluster CUCM if all 4 clusters are having the same DNS system and same domain ? Best Regards Ahmed Abd EL-Rahman Senior Network Engineer Hi James, Yes currently all the 4 clusters' users can talk to each others via inter-cluster trunks over WAN links. Kindly if you have any documents explaining such setup please share it with me. Appreciated. BR Ahmed Abd EL-Rahman Senior Network Engineer Sent from my iPhone On Mar 12, 2017, at 5:51 PM, James Buchanan <[email protected]<mailto:[email protected]><mailto:[email protected]<mailto:[email protected]%3cmailto:[email protected]<mailto:[email protected]>>>> wrote: Hello, It is indeed possible. You use one cluster as a sort of "hub" cluster. Then, just make sure the users in each cluster have the Home Cluster parameter checked, but make sure it is only checked in one cluster. Also, you have to make sure you are using ILS and have peer links in IM&P between all the clusters. If all the Jabber users can talk to each other today in all the various clusters, then you're already grand for using Expressway in that scenario. Thanks, James On Sun, Mar 12, 2017 at 10:30 AM, Ahmed Abd EL-Rahman <[email protected]<mailto:[email protected]><mailto:[email protected]<mailto:[email protected]%3cmailto:[email protected]<mailto:[email protected]>>>> wrote: Hi Gents, If we have 4 standalone clusters each of them has its own CUCM and IM&P servers (version 11.5), I’d like to know if it’s possible to have only 1 Expressway C and E system to serve all the 4 cluster with MRA service ? Taking into consideration that all the 4 clusters are using the same DNS system and same domain name (company.com<http://company.com><http://company.com><http://company.com>). Best Regards Ahmed Abd EL-Rahman Senior Network Engineer _______________________________________________ cisco-voip mailing list [email protected]<mailto:[email protected]><mailto:[email protected]<mailto:[email protected]%3cmailto:[email protected]<mailto:[email protected]>>> https://puck.nether.net/mailman/listinfo/cisco-voip _______________________________________________ cisco-voip mailing list [email protected]<mailto:[email protected]><mailto:[email protected]> https://puck.nether.net/mailman/listinfo/cisco-voip _______________________________________________ cisco-voip mailing list [email protected]<mailto:[email protected]> https://puck.nether.net/mailman/listinfo/cisco-voip
_______________________________________________ cisco-voip mailing list [email protected] https://puck.nether.net/mailman/listinfo/cisco-voip
