Could not determine logical router indirectly connected to the provided logical port (Error code: 500060) error while performing traceflow for overlay segment connected VMs
search cancel

Could not determine logical router indirectly connected to the provided logical port (Error code: 500060) error while performing traceflow for overlay segment connected VMs

book

Article ID: 401470

calendar_today

Updated On:

Products

VMware NSX

Issue/Introduction

  • Traceflow is being attempted with a source VM connected to an NSX overlay segment to a routed destination (Eg. A VM on a different segment or a layer 3 IP)
  • Segment is not connected to a Connected Gateway (T0/T1) or segment has gateway connectivity toggled to disconnected.
  • Traceflow fails with below error:
    Traceflow request failed. The request might be cancelled because it took more time than normal. Please retry.
    Error Message: Error: Traceflow intent /infra/traceflows/<TraceflowID> realized with error Could not determine logical router indirectly connected to the provided logical port : LogicalSwitch/<LogicalSwitchID>. It is required for L3 routing of packet. (Error code: 500060)

Environment

VMware NSX 4.X
VMware NSX-T Data Center 3.X

Cause

This is an expected behaviour and occurs when the segment of the source VM does not have a Connected Gateway (T0/T1) configured on its overlay segment or if the segment has been isolated using the gateway connectivity toggle.  As NSX will attempt to parse the configured segments gateway details to run the traceflow having the segment gateway disabled will prevent traceflow from running successfully.

Resolution

Ensure the segment is configured with a Connected Gateway and that gateway connectivity is not disabled on the segment. This can be seen within the segment within the UI under Networking > Segments > NSX > Expand the segment > Gateway Connectivity.