Extra config property is not properly deleted from Logical

Products

VMware NSX

Issue/Introduction

This setup is NSX-T overlay segments which was stretched using HCX.
The issue is happened after un-stretching the network.
Post tunnel un-extension the "extraConfig.remoteRtr" parameter was still found in logical switch API output.

GET https://www.example.com/api/v1/logical-switches/b4####-8###-###4-921b-53########d7

"extra_configs": [
{
"config_pair": {
"key": "com.vmware.nsx.port.extraConfig.remoteRtr",
"value": "IP "xx.xx.xx.xx" mac-address "XX:XX:XX:XX:XX:XX "
}
}
],

- Observing connectivity issues to VMs - Segment is dropping packets and traffic is disrupted.

Issue observed on NSX-T 3.1.3.7 and 3.2.2

Environment

VMware NSX-T Data Center

Cause

- Systems working in version 3.1.3.7 and VM's were connected to logical switches created by HCX.

- After upgrade to 3.2.2.1 the virtual machines connected to the L2E prefix created by HCX failed to carry the traffic.

- The VM's on these segments were unable to ping their default gateway.

Resolution

Workaround:

Please follow this steps to delete the remoteRtr property in the segment.

Step1:

To identify the segments to update run the GET API calls to record the ID

GET https://{nsx-manager-ip}/policy/api/v1/infra/tier-0s/<tier-0-id>/segments
GET https://{nsx-manager-ip}/policy/api/v1/infra/tier-1s/<tier-1-id>/segments
GET https://{nsx-manager-ip}/policy/api/v1/infra/segments

Step 2:

To update the segments to remove the remoteRtr property using this PUT API. Copy the payload from the GET API of the segment and remove the remoteRtr property from the response.

PUT API https://{nsx-manager-ip}/policy/api/v1/infra/tier-0s/<tier-0-id>/segments/<segment-id>
PUT API https://{nsx-manager-ip}/policy/api/v1/infra/tier-1s/<tier-1-id>/segments/<segment-id>
PUT API https://{nsx-manager-ip}/policy/api/v1/infra/segments<segment-id>

Update the segment as: "extra_configs": [],

Step 3:

To verify the remoteRtr property is deleted from the segment run the GET API calls again.

GET https://{nsx-manager-ip}/policy/api/v1/infra/tier-0s/<tier-0-id>/segments
GET https://{nsx-manager-ip}/policy/api/v1/infra/tier-1s/<tier-1-id>/segments
GET https://{nsx-manager-ip}/policy/api/v1/infra/segments

Resolution:

- The issue is fixed on NSX-T 4.1.1, NSX-T 4.2.0

- From 4.1.0 HCX uses policy API to update the extra_config property.