Any link (router link T1, downlink, uplink) connected to T0 is not realized after upgrading from 2.3 to 2.5.x

Products

• VMware NSX

Issue/Introduction

Symptoms:

Any new interface ( Router Link T1, Downlink, Uplink )  on T0 is not getting realized after upgrading.

This issue is only encountered if we are doing upgrade from Eclipse (2.3.x) to Firestar (2.5.x).

Environment

VMware NSX-T Data Center
VMware NSX-T Data Center 2.5.x

Cause

When user upgrade, as a part of data migration, router link lifs of T0LR is updated  to support IPv6 functionality. So the existing T0 router links might affect processing of new interfaces created on T0 after upgrade.

Resolution

This is a known issue affecting NSX-T Data Center 2.5.x and is planned to be fixed in a future release.

Workaround:

Execute Logical Router GET and PUT API X number of times without changing even single data of payload. Execute GET and PUT each time as revision changes.

Where X = ((Existing T0 router link ports before upgrade)/25) + 1.  Let’s say if customer has 210 T0 router link ports before upgrade, it should trigger X = (210/25) + 1 = 9 activities of T0 before user creates any new interfaces on that T0.

GET

URI Path(s):

/api/v1/logical-routers/<logical-router-id> of T0

PUT

URI Path(s):

/api/v1/logical-routers/<logical-router-id>

Additional Information

Impact/Risks:

This will cause the new provision of  interface on T0 to fail  and traffic will be impacted for those interfaces. 

Existing interfaces on  T0 and connected T1 will work and there is no impact of traffic .