Why do some HCX Layer 2 Extension (L2E) segments appear as 'Disconnected' while others show as 'Routed' in NSX and the VMC Console?
search cancel

Why do some HCX Layer 2 Extension (L2E) segments appear as 'Disconnected' while others show as 'Routed' in NSX and the VMC Console?

book

Article ID: 402876

calendar_today

Updated On:

Products

VMware Cloud on AWS

Issue/Introduction

NSX UI:

VMC Console  UI:

Environment

HCX
VMware Cloud on AWS

Cause

The status depends on where the default gateway is located. If the default gateway is on the Tier-1 (T1) gateway, the status shows as "Routed." If not, it shows as "Disconnected."

  • L2E_vLan_1 is still extended between On-Prem and Cloud, with MON disabled. This means the default gateway remains On-Prem, so the status shows as "Compute Gateway | Disconnected."
  • L2E_vLan_2 was previously extended from On-Prem to Cloud using HCX. It has now been un-extended, and the default gateway is in the Cloud. So, the status shows as "Compute Gateway | Routed."

Resolution

This behavior is expected and is working as per design.