Yesterday I was working on Edge Services Gateway in my Lab and deployed the edge gateway in HA mode. Soon after the deployment when I checked the HA status from vCenter, it reported status as Down

edge-ts-0

To counter any UI bug which might be reporting HA status as down (as this was a brand new deployment), I decided to check the HA status by logging onto edge vm’s directly.

On checking for the HA status on the VM, below message was displayed

Highavalibity healthcheck server is stopped

edge-ts1.PNG

edge-ts2

I did a search on google for this message and didn’t get much results. Then I checked the Admin guide for NSX and came to know the fact that you should have at least one vNIC configured as High availability traffic flows on one of the internal interface.

By design the edge High Availability Service will only kick in once the first Internal vNIC has been added and configured. If you have enabled HA after doing the initial interface configurations you won’t have this issue as during the HA setup you are asked which vNIC to choose. If you enable HA without a vNIC configured the service won’t kick in until that vNIC is in play.

On checking my HA configuration I found that I have not configured any internal interface on my edge gateway.

edge-ts3

I went ahead and finally configured vNIC1 interface

edge-ts4

As soon as the internal interface was configured, High availability was established on the edge gateway.

edge-ts5

On doing a check on edge VM’s, confirmed that one of em is active and other is standby

edge-ts7.PNG

edge-ts8.PNG

I hope you enjoyed reading this post. Feel free to share this on social media if it is worth sharing. Be sociable :)

Posted in: NSX.
Last Modified: January 12, 2017

Leave a reply