Configure DNS Server(s) on NSX Edge Cluster(s) fails from the SDDC manager.

Products

• VMware SDDC Manager

Issue/Introduction

Updating DNS server from the SDDC manager fails during update of the NSX manager.

Description	Configure DNS Server(s) on NSX Edge Cluster(s)
Progress Messages	Error occurred while configuring DNS servers [x.x.x.x, x.x.x.x] for entity with IP {1}.

operationsmanager.log shows the below errors - 

{error_message=[Fabric] Modification of some properties of an edge node is not allowed via NSX Manager. Kindly use CLI to modify these properties: node_user_settings and allow_ssh_root_login. 
Redeploy edge to modify form factor., httpStatus=BAD_REQUEST, error_code=16028, module_name=FABRIC}, errorType = INVALID_REQUEST

2024-10-07T13:54:15.936+0000 DEBUG [vcf_om,6703e80650c4a9b18081ab5f2f419bb0,9f2f] [c.v.v.c.n.s.c.c.ApiConnection,pool-3-thread-6] Closed ApiClient connection.
2024-10-07T13:54:15.936+0000 ERROR [vcf_om,6703e80650c4a9b18081ab5f2f419bb0,9f2f] [c.v.e.s.o.model.error.ErrorFactory,pool-3-thread-6] [FR5FA] 
ENTITY_DNS_CONFIGURATION_FAILED Error occurred while configuring DNS servers [x.x.x.x, x.x.x.x] for entity with IP {1}.
com.vmware.evo.sddc.orchestrator.exceptions.OrchTaskException: Error occurred while configuring DNS servers [x.x.x.x, x.x.x.x] for entity with IP {1}.
        at com.vmware.vcf.systemconfigurator.action.ConfigureDnsServersOnNsxtEdgeClustersAction.setDnsServersOnEdgeNode(ConfigureDnsServersOnNsxtEdgeClustersAction.java:202)
        at com.vmware.vcf.systemconfigurator.action.ConfigureDnsServersOnNsxtEdgeClustersAction.lambda$setDnsServersOnEdgeCluster$4(ConfigureDnsServersOnNsxtEdgeClustersAction.java:159)
        at java.base/java.util.ArrayList$ArrayListSpliterator.forEachRemaining(ArrayList.java:1625)
        at java.base/java.util.stream.ReferencePipeline$Head.forEach(ReferencePipeline.java:762)

Environment

VMware Cloud Foundation 4.x
VMware Cloud Foundation 5.x

Cause

SDDC is unable to process the modification on the NSX Edge node.

 

Resolution

Update the DNS manually on the NSX node, and retry the workflow on the SDDC manager - can help resolve this issue in some cases.

Otherwise, once the DNS has been manually updated in NSX manager,  we can skip this failed subtask in the SDDC workflow. This involves updating entries in the SDDC manager database. Contact Broadcom Support to properly resolve this issue.