This is a known issue affecting VMware NSX-T Data Center 3.1.0.
This issue is resolved in VMware NSX-T Data Center 3.1.1.
Workaround:
If they are different, update the mode on Policy using UI or Policy API.
Workaround:
API Example:
PATCH https://<policy-ip>/policy/api/v1/infra/global-config
{
"fips": {
"lb_fips_enabled": false
},
"l3_forwarding_mode": "IPV4_AND_IPV6",
"uplink_mtu_threshold": 9200,
"vdr_mac": "02:50:##:##:##:52",
"vdr_mac_nested": "02:50:##:##:##:53",
"allow_changing_vdr_mac_in_use": false,
"arp_limit_per_gateway": 50000,
"resource_type": "GlobalConfig",
"id": "global-config",
"display_name": "default",
"path": "/infra/global-config",
"relative_path": "global-config",
"parent_path": "/infra",
"unique_id": "6ad09314-####-####-####-cbf124c3e43d",
"marked_for_delete": false,
"overridden": false,
"_create_time": 1599172410181,
"_last_modified_user": "admin",
"_last_modified_time": 1599175772818,
"_system_owned": true,
"_create_user": "system",
"_protection": "NOT_PROTECTED",
"_revision": 1
}
See the NSX-T Product Documentation for more details.