Service Interface route is deleted from T0 after Standby T1 is relocated to another Edge
search cancel

Service Interface route is deleted from T0 after Standby T1 is relocated to another Edge

book

Article ID: 373763

calendar_today

Updated On:

Products

VMware NSX

Issue/Introduction

  • T0 is connected to T1
  • T1 is configured in Active/Standby
  • Standby Relocation is enabled on T1
  • Route is advertised to T0
    • Networking > Tier-1 Gateways > [T1] > Route Advertisement > All Connected Segments & Service Ports
  • The Edge on which the Standby T1 is located fails or is powered down
  • The Standby T1 relocates to another Edge after a set time. Default is 30 minutes
    • Relocation timer is configured via System > Fabric > Profiles > Edge Cluster Profiles > Stand By Relocation Threshold
  • The route is no-longer present in the T0 routing table.
    • get logical-router [T0 UUID] route
  • North/South traffic is affected
  • Active T1 Edge logs shows the route is deleted for the Service Interface only

/var/log/syslog
[Timestamp] [Edge]1 NSX 1 FABRIC [nsx@6876 comp="nsx-edge" subcomp="nsxa" s2comp="nestdb-lrouter" level="INFO"] FIB delete [Route] for lrouter [UUID] deleted

 

Environment

NSX 3.2.x, 4.x

Resolution

This issue is resolved in NSX 3.2.4 and 4.1.1

 

Workaround:

To readvertise the route run the following API call.

POST https://<mgr-ip>/policy/api/v1/infra/tier-1s/<t1-id>?action=reprocess&enforcement_point_path=/infra/sites/default/enforcement-points/default