hello guys,
i'm facing a weird issue when configuring the internal interface on an edge service gateway.
the problem is demonstrated in the attached graph.
I did configure name, type, logical switch to connect to, primary IP with prefix length...etc
but when i clicking ok to finish, there's an error-like prompt prevent me from finishing.
the prompt says nothing, not even a word, so i couldn't trouble-shoot.
by the way,
i had configured the gateway and uplink interface for the ESG successfully.
does anyone know about this situation?
thanks for any reply in advance.
If you are on NSX 6.3.2, most likely you hit issue 1909406
This should be fixed in NSX 6.3.3 as per release notes: VMware NSX for vSphere 6.3.3 Release Notes
Fixed Issue 1909406: Modifying the Interface configuration for an already deployed distributed logical router or edge services gateway fails with a blank error message
Adding or modifying Interface level parameters for an already deployed distributed logical router or edge services gateway fails with a blank error message. User is unable to modify NSX Edge interface from UI. Fixed in 6.3.3.
Is the error persistent ? Most of these issues are because of web-client(NIC not showing,Unable to type name/ip etc),reloading webclient is one way of trying to fix it. If no luck,you can try redeploying the edge and retry the step.
If you are on NSX 6.3.2, most likely you hit issue 1909406
This should be fixed in NSX 6.3.3 as per release notes: VMware NSX for vSphere 6.3.3 Release Notes
Fixed Issue 1909406: Modifying the Interface configuration for an already deployed distributed logical router or edge services gateway fails with a blank error message
Adding or modifying Interface level parameters for an already deployed distributed logical router or edge services gateway fails with a blank error message. User is unable to modify NSX Edge interface from UI. Fixed in 6.3.3.
thanks Bayu,
i'm currently using version 6.3.1, it seems that is the bug you are taking about.
i'll try 6.3.3 and check it out.
Hi Bayu,
Is there any temporary workaround for this issue instead of upgrading to NSX 6.3.3?
Hi Amol, I'm not aware of any workaround. If there is a fix, normally VMware Support/GSS will advise to upgrade. But you can try to check with VMware GSS
Hey Amol, I just happen to know there is a KB on this that explains the workaround is to use REST API call.
Here's the KB https://kb.vmware.com/selfservice/microsites/search.do?language=en_US&cmd=displayKC&externalId=21511...