The NSX-T API number of routes does not match the number of routes displayed in the cli of the edge node
search cancel

The NSX-T API number of routes does not match the number of routes displayed in the cli of the edge node

book

Article ID: 322484

calendar_today

Updated On:

Products

VMware NSX Networking

Issue/Introduction

Symptoms:
  • You are using NSX-T 2.4 or greater.
  • The Tier 0 Gateway/Tier 0 VRF is configured as Active/Active mode with ECMP.
  • There is no functional impact.
  • For example, using the CLI (Command Line Interface) on the edge node, we see 19 routes listed below:

10-173-73-154(tier0_sr)> get route
Flags: t0c - Tier0-Connected, t0s - Tier0-Static, b - BGP,
t0n - Tier0-NAT, t1s - Tier1-Static, t1c - Tier1-Connected,
t1n: Tier1-NAT, t1l: Tier1-LB VIP, t1ls: Tier1-LB SNAT,
t1d: Tier1-DNS FORWARDER, t1ipsec: Tier1-IPSec, isr: Inter-SR,
- selected route, * - FIB route
Total number of routes: 19
o > * 0.0.0.0/0 [110/1] via 4.4.4.10, uplink-281, 01:08:39
...
t0c> * fe80::/64 is directly connected, uplink-281, 03:18:36

  • And then if we use the policy API to get the number of routes, example below, we see 22 routes listed:
GET /policy/api/v1/infra/tier-0s/<tier-0-Gateway>/routing-table
{
    "results": [
        {
            "edge_node": "/infra/sites/default/enforcement-points/default/edge-clusters/5612d443-e81c-411d-87c4-c95a3caecad3/edge-nodes/1",
            "count": 22,
            "route_entries": [


Environment

VMware NSX-T Data Center

Cause

The edge node cli counts the number of prefixes, while the Policy GET API count the number of paths.

Resolution

This is a known issue impacting NSX-T Data Center.

Workaround:
There is no functional impact due to this issue, no workaround is required.