I am working with customer to deploy Cisco Collaboration Edge Solution. I have attached a solution diagram with the case. The solution includes:
1. Cluster of CUCM Servers
2. Cluster of IM & Presence Servers
3. Cluster of Expressway C Servers
4. Cluster of Expressway E Servers
As you see in the diagram the servers are configured with internal domain "net.lab.com". The public domain is "lab.com" which is routable on the internet.
Following are the questions about the solution:
1. Do we need to create separate clusters for Expressway C & E?
2. Do we need to create separate cluster names for Expressway for C & E?
3. What DNS SRV records are required for Expressway C on internal and external DNS server?
4. What DNS SRV records are required for Expressway E on internal and external DNS server?
5. What DNS SRV records are required for Jabber Users on internal and external DNS server?
6. Can we use "lab.com" as our SIP domain? Is it required for in this solution?
7. Is it required to configure Expressway E with public domain name "lab.com"?
Please feel free to provide additional information.
1. You do not need separate clusters for Expressway C&E for the "domain" setup you have. You only need it for HA.
2. The cluster name will be the same on both Expressway Cs and Expressway Es. The DNS host names will be obviously different.
3. Expressway C requires only A records on the internal DNS server.
4. Expressway E requires A records on the internal and external DNS server and _collab-edge._tls.domain.com SRV record on the external DNS server.
5. See 4.
6. Yes, its possible. On the IM/P, you can choose what domain you want.
7. Yes, Expressway E needs to be configured with the lab.com domain since it will be external.
Please read the admin and install/configure guides on www.cisco.com to understand more. There are a lot more to the deployment process which is difficult to outline on the forum.
Thank you very much for your prompt response. Follwing is my understanding from your response:
1. We can have a single cluster which includes C's and E's in same cluster. In my case it is a cluster of:
2. For example the cluster name is "expwy.lab.com". This clustername can be ocnfigured on C's and E's. The DNS hostnames will be:
3. DNS A records for C's which maps to hostname to IP Address on Internal DNS server.
expwyc1.net.lab.com <---> 10.1.1.21
expwyc2.net.lab.com <---> 10.1.1.22
4. DNS A records for E's which maps to hostname to IP Address on Internal and External DNS server.
expwye1.lab.com <---> 22.214.171.124
expwye2.lab.com <---> 126.96.36.199
DNS SRV records for E's on External DNS server.
_collab-edge._tls.lab.com. SRV 10 10 8443 expwye1.lab.com.
_collab-edge._tls.lab.com. SRV 10 10 8443 expwye2.lab.com.
5. DNS SRV records for Jabber on Internal DNS server:
_cisco-uds._tcp.lab.com. SRV 10 10 8443 cucmpub.net.lab.com
_cisco-uds._tcp.lab.com. SRV 10 10 8443 cucmsub1.net.lab.com
_cuplogin._tcp.lab.com. SRV 10 10 8443 imps1.net.lab.com
_cuplogin._tcp.lab.com. SRV 10 10 8443 imps2.net.lab.com
7. Is it possible to configure Expressway E in "net.lab.com" domain with IP natting?
Do you have any updates on my above response?
You potentially could but then your public DNS server should have the zone net.lab.com configured so that you can create appropriate A records and SRV records to point to the net.lab.com A records.
In my case its little bit different.
there is no internet here. but want to use expressway E and C clustered.
So can we use same internal DNS server as external and internal dns server.
or do i need to create another DNS server in DMZ zone dedicated for expressway.
You can't use the same DNS server. This is because Jabber will only use MRA..ie go over expressway E and C only if it can't resolve the internal SRV UDS record. If you have the same DNS and have both collab-edge and uds srv record Jabber will always use the UDS record.
By the way if there is no internet why are you trying to use expressway solution?
Ok so you are confusing two things here. Like I posted already, if your users are going to use VPN for access why is your security team pushing for Expressway-E ? And most important of all you are not going to publish your edge SRV record on the public DNS so how do you plan the remote jabber clients to discover the expressway-E in the first place let alone connect through it ?
You can have the DNS in DMZ but I am not sure if that is a valid/supported deployment.
Take a look at the jabber firewall ports and have them opened within your firewall. Then just configure jabber SRV record for _cisco-uds._tcp.<yourdomain.com> to point to the CUCM UDS servers