I would encourage you to review the loss of connectivity scenarios covered in our documentation. The arbiter disconnecting from both sides is not enough to trigger a hang.

https://docs.intersystems.com/irisforhealth20223/csp/docbook/Doc.View.cls?KEY=GHA_mirror_set

A hang suggests a total loss of network connection between failover members and the arbiter simultaneously. In general, the arbiter is a supplement to the communication between the two failover members, and not necessarily the first place to look for an issue.

ex. If the arbiter connections to the failover members were first lost, the primary and failover member would remain in contact via their own ISCAgents. Then, if the two members lost contact with each other, the primary would have continued to operate.

Howdy all,

Iain is right that you can get the ODBC driver from the WRC site directly if you are a customer of ours, but the new spot InterSystems hosts drivers for ODBC and so on is here:

https://intersystems-community.github.io/iris-driver-distribution/

edit: I realized this was asking for Cache, not IRIS drivers, so my answer doesn't address it.

Smythe,

Did you have a chance to review the replies on your other post? Are you trying to use the managed alert framework? If so, I'd suggest reviewing that documentation to make sure your configuration is appropriate. It sounds to me you may just want a regular router, and not to use the AlertManager, in which case a simple business rule can do that routing (or if you don't need routing, you can just make the email operation the Ens.Alert component.)

I think the following Google page explains the SMTP settings you need:

https://support.google.com/a/answer/176600?hl=en