I try and try .... this worked with me
Here's an example based off my config. 184.108.40.206 would be my "gateway" while 220.127.116.11 is the upstream device I am checking to verify connectivity. 18.104.22.168 would be a secondary route if your primary is down.
add check-gateway=ping comment="Primary Default Route - Midco" distance=1 gateway=22.214.171.124
add check-gateway=ping comment="Backup Default Route - Midco" distance=2 gateway=126.96.36.199
add comment="Validate Route" distance=1 dst-address=188.8.131.52/32 gateway=184.108.40.206 scope=10
If you are unable to reach 220.127.116.11 via 18.104.22.168, the route is disabled and it uses 22.214.171.124 for connectivity.
the main problem was i did not delete my exist configuration
Thank you all ...... Thank for forum.mikrotik.com ...... Thanks for mikrotik board
Looks good, yes one has to go to the IP DHCP Client and uncheck the default route from being added into the mix.
Okay as far as setup, what this means is that you only have ONE WAN IP address and are checking it via two recursive sites.
The only difference between my recursive setup and yours is that I have a second WANIP.
add check-gateway=ping distance=2 gateway=126.96.36.199
add check-gateway=ping distance=3 gateway=188.8.131.52
add distance=10 gateway=ISPEastlinkgateway
add distance=2 dst-address=184.108.40.206/32 gateway=vlanbellgateway scope=10
add distance=3 dst-address=220.127.116.11/32 gateway=vlanbellgateway scope=10
So the logic being is that
a. the router checks google connectiivty first and if that doesnt work checks OPENDNS connectivity both using the primary ISP.
b. if both public DNS servers fail, then the router switches to the secondary ISP.
I'd rather manage rats than software. Follow my advice at your own risk! (Sob & mkx forced me to write that!)