NSX Edge deployment fails with invalid MAC address configuration
Article ID: 326331
Updated On:
Products
VMware NSX Networking
Issue/Introduction
Symptoms:
2019-03-29 14:14:12.026 GMT ERROR TaskFrameworkExecutor-29 PublishTask:454 - Failed jobId 'jobdata-626031' for edge 'edge-2920' during publishing.
com.vmware.vshield.edge.exception.VseException: vShield Edge:10014:Configuration failed on NSX Edge vm vm-1711422.:invalid MAC address 00:50:56:XX:XX:XX
at com.vmware.vshield.edge.vse.facade.VseRpcResponseHandler.handleResponse(VseRpcResponseHandler.java:158)
at com.vmware.vshield.vsm.messaging.rpc.RpcManager.processResponse(RpcManager.java:319)
at com.vmware.vshield.vsm.messaging.rpc.ResponseEndpoint.handleMessage(ResponseEndpoint.java:63)
at sun.reflect.GeneratedMethodAccessor741.invoke(Unknown Source)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
at java.lang.reflect.Method.invoke(Method.java:498)
at org.springframework.expression.spel.support.ReflectiveMethodExecutor.execute(ReflectiveMethodExecutor.java:69)
at org.springframework.expression.spel.ast.MethodReference.getValueInternal(MethodReference.java:95)
Note: The preceding log excerpts are only examples. Date, time, and environmental variables may vary depending on your environment.
- NSX Edge deployment fails with error: Configuration failed on NSX Edge vm vm-X. (invalid MAC address XX:XX:XX:XX:XX:XX)
- NSX Edge is deployed specifying the MAC addresses (this can be the case when vCloud Director is used to deploy the NSX Edge).
- NSX Edge deployment may succeed after multiple retries.
- NSX Manager logs (show log manager) display message(s) similar to the message below:
2019-03-29 14:14:12.026 GMT ERROR TaskFrameworkExecutor-29 PublishTask:454 - Failed jobId 'jobdata-626031' for edge 'edge-2920' during publishing.
com.vmware.vshield.edge.exception.VseException: vShield Edge:10014:Configuration failed on NSX Edge vm vm-1711422.:invalid MAC address 00:50:56:XX:XX:XX
at com.vmware.vshield.edge.vse.facade.VseRpcResponseHandler.handleResponse(VseRpcResponseHandler.java:158)
at com.vmware.vshield.vsm.messaging.rpc.RpcManager.processResponse(RpcManager.java:319)
at com.vmware.vshield.vsm.messaging.rpc.ResponseEndpoint.handleMessage(ResponseEndpoint.java:63)
at sun.reflect.GeneratedMethodAccessor741.invoke(Unknown Source)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
at java.lang.reflect.Method.invoke(Method.java:498)
at org.springframework.expression.spel.support.ReflectiveMethodExecutor.execute(ReflectiveMethodExecutor.java:69)
at org.springframework.expression.spel.ast.MethodReference.getValueInternal(MethodReference.java:95)
Note: The preceding log excerpts are only examples. Date, time, and environmental variables may vary depending on your environment.
Cause
This issue occurs when inventory updates from vCenter to NSX Manager are delayed which is expected in high churn environments.
In such cases when a MAC address is specified at the NSX Edge creation, inventory updates from vCenter are not received in a timely fashion and the NSX Edge creation fails.
In such cases when a MAC address is specified at the NSX Edge creation, inventory updates from vCenter are not received in a timely fashion and the NSX Edge creation fails.
Resolution
The issue is resolved in NSX for vSphere 6.3.5 and 6.4.0.
Workaround:
To workaround the issue, do not specify MAC addresses when creating the NSX Edge.
Workaround:
To workaround the issue, do not specify MAC addresses when creating the NSX Edge.
Additional Information
Impact/Risks:
Because of this issue, the NSX Edge does not get deployed.
Because of this issue, the NSX Edge does not get deployed.
Feedback
Yes
No
Powered by
