Configuring a default route on an Isolated T1 with multiple segments in NSX

Products

• VMware NSX
• VMware Cloud on AWS
• Azure VMware Solution

Issue/Introduction

• You are running VMC (VMware cloud on AWS) versions 1.18, 1.19 or 1.20 or Azure VMware Solution.
• You have configured multiple NSX segments to connect to a isolated T1 gateway.
• Configuring a static default route (0.0.0.0/0) on the connected T1 gateway will fail with the below error:
  "Error: Default route next-hop address ##.##.##.## must belong to Tier-1 /infra/tier1-s/<Tier-1 name> connected segment subnets /infra/segments/<segment name>. (Error code: 503637"
  

Environment

VMware NSX
VMware Cloud on AWS
Azure VMware Solution

Cause

The issue occurs due to a validation issue.

Resolution

This is a known issue impacting NSX on VMware cloud on AWS and Azure VMware Solution

Workaround:
Configure the static default route on the T1 gateway when it has only a single segment attached to it or none attached to it.
Once the static default route is added, additional segments can be attached to the T1 gateway.