Untrust Failover Track IP Settings



  • Right now, this is what I have:

    Under my main untrust interface, in the Track IP section:
    IP: 64.59.114.18
    Interval: 60 seconds
    Threshold: 2

    IP: 24.83.96.1
    Interval: 60 seconds
    Threshold: 2

    IP: 192.43.244.18
    Interval: 60 seconds
    Threshold: 2

    And then in the Track IP Options:
    Enable Track IP: Checked
    Threshold: 6

    When all three IP addresses fail, it does automatically failover to the second untrust interface, as expected.

    However, I’m looking at the log, and last night even though only one IP failed, it still failed over… why is that?

    2006-04-05 04:50:35 crit Recovery to primary untrust interface occurred.
    2006-04-05 04:50:13 crit Track-ip IP address 192.43.244.18 succeeded.
    2006-04-05 04:48:37 crit Failover to secondary untrust interface occurred
    2006-04-05 04:48:16 crit Track IP failure reaches threshold.
    2006-04-05 04:48:15 crit Track IP IP address 192.43.244.18 failed.
    2006-04-05 03:55:35 crit Recovery to primary untrust interface occurred.
    2006-04-05 03:55:13 crit Track-ip IP address 192.43.244.18 succeeded.
    2006-04-05 03:52:37 crit Failover to secondary untrust interface occurred.
    2006-04-05 03:52:16 crit Track IP failure reaches threshold.
    2006-04-05 03:52:15 crit Track IP IP address 192.43.244.18 failed.

    Over what length of time does the threshold apply?

    As in, if it’s only valid per check, and all three IP addresses are checked at the same time every 60 seconds, if all three are down, it adds up to 6 which triggers the failover.
    Or does it just keep adding up, as in one of the remote IP’s is failing to respond, so after the first try, threshold count is now 2… and a minute later, it tries again and the same IP fails, so now the threshold count is 4… and it fails again a minute later, so now the sum is 6 and it triggers the failover.

    Is there a better way to configure the Track IP settings so that it more accurately fails over only when the primary untrust interface is REALLY down?



  • @MaxPipeline:

    You do need to configure the weights.  Basically the threshold determines at what level you want to failover to occur.  The weight will determine the cost of the failure.  For instance if your threshold is 10 and the weight on IP1 is 6 and weight on IP2 is 10 then if only IP1 fails then the total weight would be 6 which is below the threshold of 10 thus will not fail.  But if IP2 fails then the total weight would be 10 which would meet or exceed the threshold of 10 thus would fail.  If IP1 and IP2 both failed then the total weight would be 16 which again exceed the threshold of 10 and thus would fail.

    Not sure if I really understand what you’re saying.

    Each track IP entry has a threshold and weight setting.

    There is a general threshold setting in the Track IP Options page.

    I think you’re saying the general threshold setting triggers the failover if the weights add up to exceed it.

    But what is the threshold setting in each individual tracking IP for then?



  • You do need to configure the weights.  Basically the threshold determines at what level you want to failover to occur.  The weight will determine the cost of the failure.  For instance if your threshold is 10 and the weight on IP1 is 6 and weight on IP2 is 10 then if only IP1 fails then the total weight would be 6 which is below the threshold of 10 thus will not fail.  But if IP2 fails then the total weight would be 10 which would meet or exceed the threshold of 10 thus would fail.  If IP1 and IP2 both failed then the total weight would be 16 which again exceed the threshold of 10 and thus would fail.



  • @MaxPipeline:

    Did you configure the weights?  If so what did you configure the weights to?

    No, I didn’t.

    From what I see, you can choose to have the failover based on weights or the track IP option… right now I have it set on the track IP option, so I don’t think the weights matter?

    Unless weights are a better way of configuring the failover…



  • Did you configure the weights?  If so what did you configure the weights to?


 

26
Online

38.4k
Users

12.7k
Topics

44.5k
Posts