When NAT's are configured on the North 3rd party component/interface and not controlled by NSX-T/T-0 you will see various portions of the Service Insertion setup in a down(detached) or only partially setup.
Service Insertion setup will be unaware of NAT's north bound and traffic for SI dropped. When this occurs it will never create a path for SI traffic and other components will not be accessible to complete SI setup in the NSX-T UI. One example, you can run from the edge to confirm connectivity. We can see its properly configured for N/S policy but, shows "BFD_DOWN" for connectivity.
Edge_CLI> get service-insertionService Insertion Policy:
Policy UUID : e8f84d67-3536-49f8-af5b-example-UUIDTransport type : L2_BRIDGEIs EW policy : 0 <---------------------0 stats this is a North/South policyIs BFD enabled : 1BFD status : BFD_DOWN <---------No communication.Ingress lookup count : 8427477Egress lookup count : 85322Service link1 IP : 169.###.##.4Service link2 IP : 169.###.##.4Service link1 nexthop IP : 169.###.##.2Service link2 nexthop IP : 169.###.##.2Failure Policy : FAIL_ALLOW
It will show "BFD_UP" and "Is EW policy 0" when properly configured for N/S Service Insertion policy.
Apply NAT's at the NSX-T T-0 for proper Service Insertion Integration.
NSX-T NAT documentation
https://techdocs.broadcom.com/us/en/vmware-cis/nsx/nsxt-dc/3-2/administration-guide/network-address-translation.html
NSX-T Service Insertion Document
https://techdocs.broadcom.com/us/en/vmware-cis/nsx/nsxt-dc/3-2/administration-guide/security/endpoint-protection/configure-endpoint-protection.html