Duplicated TEP IP assignment in the Edge node
Article ID: 322041
Updated On:
Products
VMware NSX Networking
Issue/Introduction
Symptoms:
Duplicated TEP IP assignment in the Edge node observed from the same IP Pool
Duplicated TEP IP assignment in the Edge node observed from the same IP Pool
Environment
VMware NSX-T Data Center
VMware NSX-T Data Center 3.x
VMware NSX-T Data Center 3.x
Cause
This issue can happened if an Edge was replaced with a different switch name or switch name changed while Edge in maintenance mode.
Resolution
This is a known issue in NSX-T 3.2.0, 3.2.1 and 3.2.2.
Issue is fixed in NSX-T 3.2.3.
If the conditions for this issue (hostswitch name change in maintenance mode or when redeploying edge) were already present in version less than 3.2.3 then issue can happen after even upgrade to 3.2.3. However after upgrading to 3.2.3 changing host switchname change in maintenance mode or when redeploying edge will not cause this issue.
Workaround:
Avoid replacing Edge node with a different switch name or change of switch name while Edge is in maintenance mode
Issue is fixed in NSX-T 3.2.3.
If the conditions for this issue (hostswitch name change in maintenance mode or when redeploying edge) were already present in version less than 3.2.3 then issue can happen after even upgrade to 3.2.3. However after upgrading to 3.2.3 changing host switchname change in maintenance mode or when redeploying edge will not cause this issue.
Workaround:
Avoid replacing Edge node with a different switch name or change of switch name while Edge is in maintenance mode
Additional Information
Impact/Risks:
North/South outage when traffic going through the duplicated TEP Edge IP.
North/South outage when traffic going through the duplicated TEP Edge IP.
Feedback
Yes
No
Powered by
