Maximum number of KNI ports are reached in multi-VRF use case

Products

• VMware NSX

Issue/Introduction

• On an NSX edge, the maximum number of KNI ports are reached and the configuration fails to send to the edge datapath.
• You see messages similar to the following in /var/log/syslog on the NSX edge node:
  
  2024-12-20T16:11:46.041Z clpl-en-cl2-2.clearpathsg.us NSX 1913 FABRIC [nsx@6876 comp="nsx-edge" subcomp="datapathd" s2comp="dpc-pb" tname="dp-ipc31" level="ERROR" errorCode="EDG0400102"] Failed to create kni port kni-lrport-0
2024-12-20T16:11:46.042117+00:00 clpl-en-cl2-2.clearpathsg.us datapath-systemd-helper 1762 - -  2024-12-20T16:11:46Z datapathd 1913 dpc-pb tname="dp-ipc31" [ERROR] Failed to create kni port kni-lrport-0  errorCode="EDG0400102"

Environment

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

Cause

In a multi-VRF use case, there are too many trunk VLAN segments created. Each trunk VLAN segment would need to a trunk router port backed up with a KNI port on the edge. This exceeds the supported limit of KNI ports for each NSX edge.

Resolution

In a multi-VRF use case, it is recommended to configure only one trunk VLAN segment per Tier0 gateway instead of multiple trunk VLAN segments. The trunk VLAN segment should include the VLAN ranges used for all VRFs associated to the Tier0 gateway.