NSX-T IPv4 prefix limit alarm incorrectly triggering at 400000
search cancel

NSX-T IPv4 prefix limit alarm incorrectly triggering at 400000

book

Article ID: 322655

calendar_today

Updated On:

Products

VMware NSX

Issue/Introduction

Symptoms:
  • Running VMware NSX 4.0.x, 4.1.0, and 4.1.1.
  • In the NSX-T UI, an alarm is triggered, indicating the maximum number of IPv4 routes has been reached at 400000.
Feature: Routing, Event Type: Maximum IPv4 Route Limit Exceeded Description: IPv4 routes has exceeded limit of 400000 on Tier0 Gateway and all Tier0 VRFs on Edge node <>.


Environment

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

Cause

The alarm logic is incorrect and based on the value of 400000.
There is no functional impact from this alarm and it is possible to scale up to the supported max prefix of 500000.
Please review the VMware Configuration Maxims tool for more details.

Resolution

This is a known issue impacting NSX-T data center.

Workaround:
There is no functional impact due to this alarm and you can continue to add routes up to the correct supported maxim.