topic Re: Path Monitoring Static Routes in General Topics

Path Monitoring Static Routes

psycoma1984 — Sat, 12 Feb 2022 22:10:07 GMT

Hello All,

For some locations we have 2xISP setup, since we have no dynamic peering with any of those, we do a default static route via each of those. Having 'ECMP/Source IP hash' enabled it works just fine in a lab. We also do path monitoring for each of default route, pining different remote hosts like 8.8.8.8/8.8.4.4 etc.

Do we need actual static routes to those monitored destinations for whole thing to work or should default route be enough?

Thanks.

Re: Path Monitoring Static Routes

BPry — Sun, 13 Feb 2022 03:40:56 GMT

@psycoma1984,

You shouldn't need to setup a static route for the monitored destinations. On the default route you have setup, simply setup path monitoring and you would likely want to setup the failure condition as 'All' instead of the default of 'Any'.

Re: Path Monitoring Static Routes

psycoma1984 — Mon, 14 Feb 2022 15:27:06 GMT

@BPry thanks, is there a way to check what interfaces particular source is been hashed to in ECMP scenario?

Re: Path Monitoring Static Routes

aleksandar.astardzhiev — Fri, 18 Feb 2022 22:03:00 GMT

Hi @psycoma1984 ,

Just to add to the question with path monitor.

- Firewall is not using the routing table when sending the ping packets for path monitor.

- Those packets also don't go through the security policy

- And you cannot capture them with packet capture.

- Firewall will use the interface that is associated with that path monitor when generating the ping packets. It will use the IP assigned on that interface as source address

On your ECMP question - you can try with the following command "> show routing fib ecmp yes"