Hi everyone,
First off, I realize that NSX-MH is probably going to be a far stretch to get some support/answers on, but I'm going to try it anyway.
Situation:
Running NSX-MH 4.6.2, using XenServer 6.5 as the hypervisor.
We have deployed a standard setup, with all the components, controller, manager, modified openvswitch on the XenServer nodes, and all is working fine (although with some quirks, but that's another discussion altogether).
We have also deployed a gateway appliance (transport node) to act as a L3 gateway, which is all working fine.
We deployed this from the nsx-gateway-4.2.6-build46656.xva file onto XenServer.
Problem:
When we deploy second gateway appliance (transport node), which we want to add to NSX manager for a HA (active/standby) setup, it is added correctly, but the previously added one from above, is then suddenly disconnected:
The original one also halts acting as a L3 gateway, forcing us to add the newly added one to the gateway service, so it can start resume L3 gateway operations.
We've tried this a couple of times, using different hostnames, IP's, but the result is always the same. We have no clue why this is happening.
Looked at the logfiles on both the controller(s) and the faulty gateway node, and nothing comes up, other than that it seems like it looks like there is a problem with its db:
2017-02-14T19:54:12.904Z|00001|vlog|INFO|opened log file /var/log/openvswitch/ovs-had.log
2017-02-14T19:54:12.905Z|00002|rconn|INFO|ovs-had: connecting...
2017-02-14T19:54:12.905Z|00003|rconn|WARN|ovs-had: connection failed (No such file or directory)
2017-02-14T19:54:12.905Z|00004|rconn|INFO|ovs-had: waiting 1 seconds before reconnect
2017-02-14T19:54:12.906Z|00005|reconnect|INFO|unix:/var/run/openvswitch/db.sock: connecting...
2017-02-14T19:54:12.906Z|00006|reconnect|INFO|unix:/var/run/openvswitch/db.sock: connection attempt failed (No such file or directory)
2017-02-14T19:54:12.906Z|00007|reconnect|INFO|unix:/var/run/openvswitch/db.sock: waiting 1 seconds before reconnect
2017-02-14T19:54:13.816Z|00008|rconn|INFO|ovs-had: connecting...
2017-02-14T19:54:13.816Z|00009|rconn|INFO|ovs-had: connected
I'm hoping there is someone on this forum that has some or extensive experience with NSX-MH, and can push us in the right direction to get this solved.
Any help will be greatly appreciated.
Kind regards,
Koenraad