Reconfiguring NSX edge transport node fails because of stale logical switch entry.

Products

• VMware NSX

Issue/Introduction

• Reconfiguring the NSX Edge transport node fails due to a stale logical switch entry, and confirming changes to the Edge Transport node configuration results in an error indicating the same issue:

           "Failed to refresh the transport node configuration: The requested object : LogicalSwitch/5c##14##-6a##-40##-98##-f6a5##d51a## could not be found. Object identifiers are case sensitive."

• Resync of the edge transport node fails with similar error error.
• Global search for the UUID mentioned in error message does not yield any results.
• API command for listing GET https://nsxmanager.your.domain/api/v1/logical-switches , does not show any information on the logical switch UUID reported in error message.

Environment

VMware NSX 

VMware NSX-T datacenter

Cause

•  The stale logical switch UUID identified from the error message was configured on one of the ports. Although the Logical Switch was deleted from the NSX Manager, configuration remained on the uplink ports and was not cleared properly.

To verify :

• Collect LRport table from corfu - /opt/vmware/bin/corfu_tool_runner.py --tool corfu-browser -n nsx -o showTable -t LrPort > Lrport.txt.
• Verify the LrPort table shows that the stale LS UUID and the port it is mapped to.

  "intentPath": "/infra/realized-state/enforcement-points/default/logical-ports/t0-trunk-1-QT-Internal-Core-T0-qt-vlan-trunk-3400_3450-external-ulrp" ====================> Port information 
  },
  "logicalRouterId": {
    "left": "253641158###8784621",
    "right": "10496177855792####92"
  },
  "linkedLogicalSwitchPortId": "a6##44##-3e##-49##-a4##-3a0e##2c##",
  "urpfMode": "URPF_MODE_STRICT_MODE",
  "interfaceType": "INTERFACE_TYPE_UPLINK",
  "logicalSwitchId": "5c##14##-6a##-40##-98##-f6a5##d51a##", ===============================> LS UUID from the error message 

 

 

Resolution

• Once the port where the stale LS UUID is identified , delete the port using API or UI.
• API call to force delete the port  DELETE https://nsxmanager.your.domain/api/v1/logical-router-ports/{logical-router-port-id}?force=true

Additional Information

Logical route port ID can be verified from the UI or verify the desired state manager file from NSX manager.

        "_revision": 0,
        "_system_owned": false,
        "description": "Logical router port for interface /infra/realized-state/enforcement-points/default/logical-ports/t0-trunk-1-QT-Internal-Core-T0-qt-vlan-trunk-3400_3450-external-ulrp",======> Port information
        "display_name": "t0-trunk-1-QT-Internal-Core-T0-qt-vlan-trunk-3400_3450-external-ulrp",
        "edge_cluster_member_index": [
          1
        ],
        "id": "5c##14##-6a##-40##-98##-f6a5##d51a##", ==================> logical router port id
        "linked_logical_switch_port_id": {
          "is_valid": false,
          "target_display_name": "a6##44##-3e##-49##-a4##-3a0e##2c##",
          "target_id": "a6##44##-3e##-49##-a4##-3a0e##2c##",