Remove primary iproute and inject secondary iproute when primary path is unavailable; then reverse when primary path is available

[Jeff_McLeod]

I'm trying to inject a static route 192.168.12.0/22 192.168.11.253 when gateway 192.168.8.12 fails. When 192.168.8.12 is once again available, I would like to remove the 192.168.12.0/22 192.168.11.253 route and replace it with 192.168.12.0/22 192.168.8.12. Both gateway devices are connected to my Summit L2/3 device 192.168.8.36/22. I've examined numerous documents; flow-redirect, IP SLA scripting, and route weighting. All of the knowledge base articles and user streams seem to have partial configs or the scripts are full of bugs\errors. I'm new to Extreme Networks, so my knowledge is a little lacking. I'm able to do this with my Cisco equipment using ip sla and tracking statements, but of course it's well documented in comparison to what I've found with Extreme Networks. I would appreciate any help. I'm looking for detailed configs and\or explanation.

Drowning,

Jeff

[Patrick_Voss]

Hi Jeff,

Our gtac knowledge site might be perfect for you. Based on what you are saying it sounds like flow redirect will work perfectly. Below is an article that explains how to configure it:

Browser View: https://gtacknowledge.extremenetworks.com/articles/How_To/How-to-configure-flow-redirect

I hope this helps!

[Jeff_McLeod]

Correct Jarek. I inherited a network that is all static. I'm working on a backup\failover solution. I will be migrating to dynamic routing protocols once this project is done, but I have a bunch of industry no-no's to work around (ie. One site with <500 nodes using VLAN 1 10.0.0.0/8). There are so many gotchas with the way they've done things here, I can't afford to break things in the process of implementing the backup\failover solution.

[Jarek]

Hi,

if I understand correctly, you can't use dynamic routing protocols only static route?

--
Jarek