Service interface is not getting added to a Tier-1 GW.

Products

• VMware NSX

Issue/Introduction

• In the NSX Manager UI, the service interface is successfully added to the Tier-1 GW.
• When executing the "get logical-routers <logical-router-uuid> interfaces" command on Edge, the service interface that should have been added does not exist.
• There is a static route setting that specifies an IP address in the same subnet as the added service interface as the next hop.
• When creating the service interface, the following error message is output to nsxapi.log:

2024-12-20T00:51:59.359Z ERROR workerTaskExecutor-1-10 EdgeWorkItemExceptionAspect 5198 - [nsx@6876 comp="nsx-manager" errorCode="MP11268" level="ERROR" subcomp="manager"] Failed to process work-items [WorkItem{identifier=LrPort/########-####-####-####-########, Timestamp{epoch=34, address=814440402}}] of lr LogicalRouter/########-####-####-####-######## by method processLrLrpWorkItems
java.lang.IllegalArgumentException: Edge RouteGraphEdge{staticRouteId=StaticRoute/########-####-####-####-########, nextHopIp=##.##.##.##, adminDistance=1, exitPortSubnet=null} already exists between the following nodes: <[ nwk : ##.##.##.##/## , nh : [], node type : STATIC_ROUTE] -> [ No of nwks : 4, node type : NORTH_BOUND_PORT ]>, so it cannot be reused to connect the following nodes: <[ nwk : ##.##.##.##/## , nh : [RouteGraphEdge{staticRouteId=StaticRoute/########-####-####-####-########,, nextHopIp=##.##.##.##, adminDistance=1, exitPortSubnet=null}], node type : STATIC_ROUTE] -> [ No of nwks : 4, node type : NORTH_BOUND_PORT ]>.

Environment

VMware NSX

Resolution

This issue has been resolved in NSX 4.2.2 and later, available at Broadcom Downloads. 

Also, the fix is planned for future NSX 9.0 release.

For temporary workaround, reprocess the Tier1 GW using this command:

POST https://<manager-ip>/policy/api/v1/infra/tier-1s/<tier1-id>?action=reprocess&enforcement_point_path=/infra/sites/default/enforcement-points/default

Additional Information

This issue can happen if there is a static route setting that specifies an IP address in the same subnet as the added service interface as the next hop.

This is a concurrency issue, so it doesn't always happen.