SSR router could not connect with conductor after migration from old to new conductor.

Router fails with "No route to host" error while checking the data path from router to conductor.

SSR router remains in "Disconnected" state on conductor UI.

salt-call (salt-call test.ping) to conductor fails.

1. Check the "salt-call test.ping" from minion, If it fails with "TCP timed out" message.

2. Stop the 128T.service on the router and check the data path from Linux space of the SSR router to reach to the  conductor IP  "required ports for success salt and connectivity  (TCP 4505/4506 and 930)"

Issue the command "nc -zv <dst-ip> <port> => to check if the IP of conductor and connectivity ports can be reached. (if it fails with "No route to host") and if the forwarding interface from SSR is used to reach to conductor, please do the below.

=> Create the service and service-route to reach to destination IP in this case the conductor IP. (this is required when the SSR uses forwarding interface to reach to conductor and not directly from linux space)

=> Verify the route via "show fib service <service-name>"

=> Check the connectivity again (mentioned in Step 2)