Timeline for Best practice for the combination of HSRP and ECMP
Current License: CC BY-SA 3.0
8 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Jul 11, 2013 at 10:58 | vote | accept | Mike Pennington | ||
| Jul 3, 2013 at 15:44 | comment | added | Marco Marzetti | @MikePennington, thank you. Anyway you're right ARP timeout resolution is implemented in minutes | |
| Jul 3, 2013 at 15:03 | comment | added | Marco Marzetti | Didn't know. So our trick is totally useless. We picked a prime number to minimize the overlap of the timers. | |
| Jul 3, 2013 at 12:39 | comment | added | ytti | ACK. ARP timeout less or equal to MAC timeout should be BCP. There doesn't even need to be HSRP, just if there are two routers it can bite you and cause even loops. | |
| Jul 3, 2013 at 12:37 | history | edited | Mike Pennington | CC BY-SA 3.0 | added 1 characters in body |
| Jul 3, 2013 at 12:36 | comment | added | Mike Pennington | Technically Cisco IOS fires the ARP walker on 60 second intervals so you should use 240... I neglected to include that in my answer... editing it in... i am curious why you picked a prime number... | |
| Jul 3, 2013 at 12:09 | comment | added | Marco Marzetti | We sorted this problem choosing the first proposed solution, but we weren't sure of the order in which IOS would clean the table, then we set ARP timeout to 293s ( the closest prime number below the mac-address table timeout ). Still do not know if this was a good choice or not | |
| Jul 3, 2013 at 10:58 | history | answered | Mike Pennington | CC BY-SA 3.0 |