Solved: Redundant Expressway E set up with respect to ISP Links

sanket.gawankar · ‎03-15-2016

Dear Team.

I have MRA set up with Expressway E and C. Set up is well functional.

In my network infra I have ISP links from two different service provider.

Can I use both of these as redundant link for my MRA set up.?

Currently the SRV record is pointed towards Public IP address of one of the ISP.

Kindly advice.

Thanks

Sanket

Jonathan Unger · ‎03-20-2016

A fairly simple way to accomplish this would be to setup another EXP-C / EXP-E pair with the new EXP-E connecting to the second feed. You could deploy this second pair as a standalone pair, or cluster these new nodes with your existing nodes (2 member EXP-C cluster and 2 member EXP-E cluster). If you go the cluster route the documentation is here:

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

You could then configure a second set of external SRV records (_colab-edge, _sips, etc...) with lower priority pointing to your secondary EXP-E node for fail over purposes.

Please let us know if this helps.

View solution in original post

Jonathan Unger · ‎03-20-2016

A fairly simple way to accomplish this would be to setup another EXP-C / EXP-E pair with the new EXP-E connecting to the second feed. You could deploy this second pair as a standalone pair, or cluster these new nodes with your existing nodes (2 member EXP-C cluster and 2 member EXP-E cluster). If you go the cluster route the documentation is here:

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

You could then configure a second set of external SRV records (_colab-edge, _sips, etc...) with lower priority pointing to your secondary EXP-E node for fail over purposes.

Please let us know if this helps.