[cisco-voip] Expressway Cluster failover for MRA...

[Pawlowski, Adam]

Is that A record needed for some function or another of Jabber to operate? 

We have two equally weighted SRV to our E and it will fail over to the other host when it's not available, depending on the service, if it chooses to operate. The client periodically re-looks up the SRV record anyways in my experience. The failover scenario isn't instant/clean anyways with Jabber but if it does improve timing on something that would be good to know.

Adam



> -----Original Message-----
> From: cisco-voip <cisco-voip-bounces at puck.nether.net> On Behalf Of Ryan
> Huff
> Sent: Tuesday, January 28, 2020 9:04 PM
> To: Jonathan Charles <jonvoip at gmail.com>
> Cc: cisco-voip at puck.nether.net
> Subject: Re: [cisco-voip] Expressway Cluster failover for MRA...
> 
> 1.) It used to be in previous versions that all cluster nodes could technically be
> active at any time and SRV weights and priorities could influence the path
> selection but not guarantee it end-to-end when all cluster nodes are up and
> running.
> 
> I believe this behavior has changed/improved and I think you are supposed to
> be able to control that now with SRV weights and priorities, but I could be
> wrong. I haven’t played with Expressway clustering in a bit.
> 
> 2.) As far as the Jabber registration goes; what I’ve done before in the edge is
> have the collab-edge SRV point to the edge cluster FQDN as the target. Then I
> create round robin A records for the cluster FQDN (one resolving your each
> edge server). The for the edge certs, just make sure the edge cluster fqdn is in
> the SAN.
> 
> This way if one of the edge server goes down, the Jabber client is ultimately
> still trying to resolve the same MRA FQDN via SRV lookup (this a key to Jabber
> client failover for MRA).
> 
> Thanks,
> 
> Ryan
> 
> > On Jan 28, 2020, at 20:50, Jonathan Charles <jonvoip at gmail.com> wrote:
> >
> > 
> > We have two pairs of Expressway clusters (C/E) at two different locations
> (primary and DR)...
> >
> > The cluster is up, however, we want to make sure that we are in
> Active/Standby.
> >
> > Currently, we have one of our SRV records for collab-edge set at 5 (the
> backup is at 10) with the same weight.
> >
> > The clustering guide says we should set the priority and weight on both SRV
> records the same, which will cause half of the registrations to go to the DR site.
> It is far away and has less capability.
> >
> > How do we:
> >
> > 1 - Make sure the primary site handles all MRA registrations and the DR site
> is only used when the primary is down.
> > 2 = Make sure failover occurs automatically... currently Jabber users have to
> log out and back in to connect to the DR site.
> >
> >
> > Thanks!
> >
> >
> > Jonathan
> >
> > _______________________________________________
> > cisco-voip mailing list
> > cisco-voip at puck.nether.net
> >
> https://nam04.safelinks.protection.outlook.com/?url=https%3A%2F%2Fpuck.net
> her.net%2Fmailman%2Flistinfo%2Fcisco-
> voip&data=02%7C01%7C%7C2f536d8162984707853908d7a45d8e24%7C8
> 4df9e7fe9f640afb435aaaaaaaaaaaa%7C1%7C0%7C637158594035084563&am
> p;sdata=atRtIR8sWZ60Ja8akD6GjzBIgBNC8GSJjaOmu%2BTxmWw%3D&res
> erved=0
> _______________________________________________
> cisco-voip mailing list
> cisco-voip at puck.nether.net
> https://puck.nether.net/mailman/listinfo/cisco-voip