From: Kevin K. He <he...@ya...> - 2004-03-12 20:24:19
|
I didn't mean that two PCs intereconnted with two NICs on each. What I wish to convey is an analogy of two switches interconnected in the following way. ---------- 1/1 2/1 ----------- |switch 1|----------| switch2 | | | 1/2 2/2 | | |_______ |----------|__________| Assuming all ports 1/1,1/2,2/1,2/2 are in the same Vlan (broadcast domain). Then the above topology has a "loop" because broadcast or flooded frames from switch 1 port 1/1 will be forwarded to 2/1 and then flooded by switch 2 to 2/2 , then back to switch 1 through 1/2, then switch 1 again flood the frame to 1/1,...,etc. Thus the frame will be flooded forever in a loop. I'm trying to understand what is the situation if I use TIPC as managment/control plane IPC between the two switches (imagine that the two switches form a single stack). I guess my analogy using two PCs is inaccurate since PC usually doesn't perform the "bridging" function between ports. Thanks Kevin > > > --- "Ling, Xiaofeng" <xia...@in...> wrote: > > > > > > How about the following toplogy where a loop between two PCs > > > > exist ? Essentially the following toplogy exists when STP is > > > > turned off. If TIPC can tolerate this topoplogy we may not > > > > need a underlying STP to resolve L2 loops. > > > > > > > > eth1 eth0 > > > > PC1--------- /----PC2---| > > > > |eth0 | / | > > > > |________switch_________| > > > > > > > I have not tried in such condition, but I think logically > > > TIPC can work in such topology. > > > > > If this means two PC with two ethercard to each other, then there will > > be two link for the two node. > > and it will automatically perform load balance and failover. |