Re: Ip Monitoring not working with NAT

The configuration below is working as expected. The failover is fully functional without unplug and replug any connector.

The only thing is that i don't want a specific route for in this case 8.8.8.8

When the failover takes place the new default 0/0 route with pref 1 is going through 10.255.253.254

I guess this means that RPM will try to reach 8.8.8.8 with source address 10.255.255.131/24 through next-hop 10.255.253.254/24 what is not in the same subnet.

When i disable the route 8.8.8.8/32 and i put in a next-hop in the rpm the failover will not working at all but i am able to ping the next-hop

What am i missing ?

services {
    rpm {
        probe probe1 {
            test test1 {
                target address 8.8.8.8;
                probe-count 3;
                probe-interval 2;
                test-interval 2;
                source-address 10.255.255.131;
                thresholds {
                    successive-loss 3;
                    total-loss 3;
                }
                destination-interface ge-0/0/1.0;
            }
        }
    }
    ip-monitoring {
        policy test {
            match {
                rpm-probe probe1;
            }
            then {
                preferred-route {
                    route 0.0.0.0/0 {
                        next-hop 10.255.253.254;
                    }
                }
            }
        }
    }
}

routing-options {
    static {
        route 0.0.0.0/0 next-hop 10.255.255.254;
        route 8.8.8.8/32 {
            next-hop 10.255.255.254;
            preference 1;
        }
    }
}