Technology: SD-WAN

Every time we configure the in-band management IP, the health check the SSR performs does not work and config gets reverted

Configuration is successfully pushed to the device.

config authority router <rid> node node0 loopback-address ip.addr

config authority router <rid> routing default-instance static-route ip.addr/32 1 destination-prefix ip.addr/32

config authority router <rid> routing default-instance static-route ip.addr/32 1 distance   1

config authority routing filter match-redistributed-static-routes rule r0 prefix ip.addr/32

However the config is rolled back due to validation failure

ERR failed to connect to ep-terminator.mistsys.net:443 on attempt 2: dial tcp: lookup ep-terminator.mistsys.net: i/o timeout

ERR unable to establish new connection to cloud with new configuration: dial tcp: lookup ep-terminator.mistsys.net: i/o timeout

ERR Configuration did not successfully settle for version X, reverting

INF Configuration needs to be reverted from version X

INF Marking configuration health as "health: status=bad-config, version=X, connection=connected,

INF last fetched configuration is bad, not fetching a new configuration with recoveringFromBadConfig set because that will cause the same configuraiton to be generated with a new timestamp

This is a bug in SSR Version 6.2.9-5lts Only.

An upgrade SSR Version 7.0.X will fix the issue