Timeline for Does using a single cable to connect two switches create a bottleneck?
Current License: CC BY-SA 2.5
6 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Dec 30, 2009 at 20:13 | comment | added | joeqwerty | @Evan: I see your point. Is it a bottleneck? Yes. Is it creating performance problems? That can only be determined through monitoring and measurement. | |
| Dec 30, 2009 at 19:56 | comment | added | Javier | @Evan Anderson: yes, i see your point... but is it the worse bottleneck? and can it be called a bottleneck when it's still much wider than what you push through it? | |
| Dec 30, 2009 at 19:09 | comment | added | Evan Anderson | I take a little bit of issue with the phrase "it can be a bottleneck." It is a bottleneck. Whether or not it's creating a problem is an orthangonal concern. On any modern gigabit Ethernet switch the fabric exceeds 1Gbps, so by definition cascading gigabit switches with crossover cables creates bottlenecks. | |
| Dec 30, 2009 at 17:48 | comment | added | joeqwerty | +1. Good answer. In theory: Yes it could be a bottleneck. Reality: It probably isn't and probably won't become a bottleneck. Before rushing to make changes, set up link aggregation, etc., etc. You should monitor and measure the utilization of the link between the 2 switches. | |
| Dec 30, 2009 at 17:43 | history | edited | Javier | CC BY-SA 2.5 |
fix my math
|
| Dec 30, 2009 at 17:37 | history | answered | Javier | CC BY-SA 2.5 |