HA Defaulting to Internal IP HSNM Hardware and VM configurations. Sms, Email, Backup, Database

[spike]

Hi Team,

I've asked this some time ago as a feature request, but will follow up on forum.

HA Sync doesn't work from external to external ip with second server behind NAT.

i.e

server0 202.21.XX.X --> 192.168.X.X -> Assigned to eth0 of appliance (within DMZ)
server1 202.20.X.X > Assigned to eth0 of appliance (direct Internet)

Setting up replication from server1 to server0 enter external IP 202.21.XX.X initial sync completes and database arrives.
Following initial Sync DB attempts to hold sync on 192.168.X.X (internal and unroutable IP of server0)
HA Broken.

It seems that the internal IP assigned to the server overwrites the actual accessible IP.

What's the best way to work around this?

[HSNMSupport1]

Hi Spike,

We will have our development team review it and we will get back to you as soon as possible.

Best Regards,

[HSNMSupport1]

Hi Spike,

We regret to inform you that there is no work around for the time being.

Best Regards,

[spike]

Hiya,

Yup, I know. That's why the request previously. I was hoping I could go reverse from DMZ to externally assigned Server. but I get the same issue..

2018-06-07 19:20:17 hsdev1.domain.net Error! Data replication host 202.X.X.X. Host 192.168.15.7 is now down

Initial sync is performed but then following initial sync of data the internal IP is trying to pair and is unreachable. So sadly.. it makes me rely on a particular configuration for ip addressing.. Which in itself isn't the end of the world, but annoying in a test environment.

[spike]

Just to throw on the top of that, I've managed to get it to work but forcing in a static route of real world over vpn link rather than external. I think the traffic was splitting due to the mismatch of internal and external following initial sync.

Onwards and upwards.