T0 gateway status "Failed" after upgrading from 2.5.x to 3.0.x/3.1.x

Products

• VMware NSX
• VMware NSX-T Data Center

Issue/Introduction

After upgrading NSX-T from 2.5.x to 3.0.x/3.1.x. T0 gateway status changed to Failed and the following error is received in the /var/log/proton/nsxapi.log.

Errors:
<timestamp>: Field level validation errors: {value "<IP>/24" of property advanced_config.internal_transit_network violates format 'ipv4-cidr-block'}

Environment

VMware NSX-T Data Center

Cause

Tier0 properties import from key-value store have double quote around internal_transit_network i.e. "169.254.0.0/24"  and NSX-T 3.x is sensitive to double quotes which cause this issue.

Resolution

Upgrade to NSX-T 3.2.0

Workaround:

Using any REST API Tool:

- Get tier0 config using API GET https://<MANAGER_IP>/policy/api/v1/infra/tier-0s/<TIER0_NAME>

- Amend tier0 config using API PATCH https://<MANAGER_IP>/policy/api/v1/infra/tier-0s/<TIER0_NAME> with payload having corrected subnet config. Complete payload should be send which was received in GET API but with corrected subnet and without double quotes.

Impact/Risks:
Tier0 is in the failed state, however, there is no impact on the data-plane traffic.

Additional Information

There is no risk of the PATCH API call. It indicates that the user is updating the configuration. Ensure that the entire payload is sent with the updated subnet.