Tier-1 GW status becomes "Failed" when it is linked to a VRF with the same name that was recreated in another Edge Cluster.

Products

• VMware NSX

Issue/Introduction

• Tier-1 GW status becomes "Failed".
• A VRF was previously connected to a Tier-0 GW, with the Tier-1 GW linked to it.
• The original VRF was deleted, a new VRF with the same name was created, connected it to another Tier-0 GW, and the Tier-1 GW was attached to the new VRF.
• This issue does not occur if VRF is created with a different name.
• In the nsxapi.log, you will see the ObjectNotFoundException after the IpBlockSubnetAllocatorDeallocator task:

2025-06-17T06:35:00.383Z  WARN providerTaskExecutor-1-138 TransactionRetryAspect 5016 - [nsx@6876 comp="nsx-manager" level="WARNING" subcomp="manager"] Detected an active transaction retry aspect for Identifier com.vmware.nsx.management.idas.ipam.service.IpBlockServiceImpl._createBlockSubnetWithMarker(Identifier, IpBlockSubnet, String), hence ignoring this.
2025-06-17T06:35:00.383Z  INFO providerTaskExecutor-1-138 IpBlockSubnetAllocatorDeallocator 5016 POOL-MGMT [nsx@6876 comp="nsx-manager" level="INFO" subcomp="manager"] Starting Allocation for subnet block with size 2
2025-06-17T06:35:00.384Z  INFO providerTaskExecutor-1-138 IpBlockSubnetAllocatorDeallocator 5016 POOL-MGMT [nsx@6876 comp="nsx-manager" level="INFO" subcomp="manager"] Getting low ip address for block IpBlock[100.64.##.##/16] of type ipv4
2025-06-17T06:35:00.384Z  INFO providerTaskExecutor-1-138 IpBlockSubnetAllocatorDeallocator 5016 POOL-MGMT [nsx@6876 comp="nsx-manager" level="INFO" subcomp="manager"] Getting high ip address for block IpBlock[100.64.##.##/16] of type ipv4
2025-06-17T06:35:00.384Z  INFO providerTaskExecutor-1-138 IpBlockSubnetAllocatorDeallocator 5016 POOL-MGMT [nsx@6876 comp="nsx-manager" level="INFO" subcomp="manager"] Subnet available size 65536 for block id IpBlock/########-####-####-####-########
2025-06-17T06:35:00.385Z  INFO providerTaskExecutor-1-138 IpBlockSubnetAllocatorDeallocator 5016 POOL-MGMT [nsx@6876 comp="nsx-manager" level="INFO" subcomp="manager"] Found node IpBlockSubnetNode [size=2, id=IpBlockSubnetNode/########-####-####-####-########, isAllocated=false, startIpInt=########, endIpInt=null, leftSubnetNodeId=none, rightSubnetNodeId=none, parentId=none, isLeft=true]
2025-06-17T06:35:00.388Z ERROR providerTaskExecutor-1-138 PolicyProviderUtil 5016 POLICY [nsx@6876 comp="nsx-manager" errorCode="PM500015" level="ERROR" subcomp="manager"] Unexpected exception received during provider invocation.
com.vmware.nsx.management.common.exceptions.ObjectNotFoundException: null
        at com.vmware.nsx.management.container.dao.IdentifiableProxyObjectDao.findByIdentifier(IdentifiableProxyObjectDao.java:400) ~[?:?]
        at com.vmware.nsx.management.edge.lrouter.ports.dao.LRPortDaoImpl.findLRPortByIdentifier(LRPortDaoImpl.java:162) ~[?:?]
        at com.vmware.nsx.management.edge.lrouter.ports.dao.LRPortDaoImpl.findLRPort(LRPortDaoImpl.java:151) ~[?:?]
        at com.vmware.nsx.management.edge.lrouter.ports.service.LRPortsServiceImpl.getLRPort(LRPortsServiceImpl.java:346) ~[?:?]
        .....

Environment

VMware NSX 4.x

Resolution

This issue will be fixed in future release.

For temporary workaround, create a VRF with a different name and then rename it as desired.