Customers may hit an issue where the configuration committed from SSR conductor is not pushed to its managed routers, though the commit from conductor UI is successful. This normally is seen in situations where the conductor version (Ex. 5.6.X) and its managed router version (Ex. 5.3.X) is different.

Configuration committed from SSR conductor is not seen in its managed router's configuration.

Alarms are seen regarding configuration commit.

Solution is to make the versions of SSR conductor and its managed routers same. Routers needs to be upgraded to make the versions match.