Error: " Next hops already exist for network " on the Virtual Service that is stuck in initializing State

Products

• VMware Avi Load Balancer

Issue/Introduction

Intermittent traffic disruptions were observed on the AVI Virtual Service, followed by the error "Next hops for this VIP already existed in NSX-T," causing the VS to transition into the Initializing state.

Environment

• NSX-T Cloud
• AVI Load Balancer Version: 22.1.3

Cause

This is due to a known bug on AVI. In VMware NSX environments, in some scenarios when VIPs are created and deleted, NSX Advanced Load Balancer retains stale routes, causing Virtual Service to go into an initializing State with the error:"Next hops already exist for network"

https://techdocs.broadcom.com/us/en/vmware-security-load-balancing/avi-load-balancer/avi-load-balancer/22-1/vmware-avi-load-balancer-release-notes/release-notes-for-22-1-6.html#:~:text=message%20size%20limitation.-,AV%2D191670,-%3A%20In%20VMware%20NSX

 

Resolution

The issue has been fixed on AVI Versions: 22.1.6, 30.2.1, 30.1.2

As a workaround, we can identify the stale entry for the Avi Virtual Service IP on NSX T1 and delete it from NSX Manager.

Additional Information