Timeline for Redundant routes between switches
Current License: CC BY-SA 4.0
6 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Aug 8, 2020 at 9:15 | history | bounty ended | Rich | ||
| Aug 8, 2020 at 9:15 | vote | accept | Rich | ||
| Aug 7, 2020 at 21:22 | comment | added | Albin | there are a lot of good explanations on how this works in detail if you wanna know more here's just one of many examples (I haven't reviewed it, it's just a pointer where you can start) | |
| Aug 7, 2020 at 21:17 | comment | added | Albin | @Rich yes, simply speaking it will automatically "kick in" (or in this case "out"). The switch will handle changes to it's MAC address table by itself and makes all necessary adjustments. No manual intervention is necessary (if you take a LAN cable from one port and put it into another, it's essentially the same thing in regards to handling the changes, no manual intervention is necessary there either) | |
| Aug 7, 2020 at 20:42 | comment | added | Rich | do you know whether the loop prevention will kick in only when required? i.e. in normal circumstances there will be a loop which is blocked (only one route back downstairs), but as soon as one of the links fails will the remaining good link automatically start fowarding packets? Or would the MAC table need to be cleared first? i.e. automatic rather than a manual process? | |
| Aug 7, 2020 at 18:29 | history | answered | Albin | CC BY-SA 4.0 |