karren
07-23-2009, 04:17 PM
A switch first decides the role( such as root port, designated port etc) before deciding whether to put a port in blocking or forwarding state. until such port role is decided, the port remains in blocking state.
Let say we have a switch,sw1 which has portfast enabled on f0/1. This port was formally connected to windows xp host.
Let say we have a another switch, sw2 which is also connected to same switched network like sw1.
sw2 has few ports available( not in use).
we take sw2's f0/2 port and connect it to f0/1 of sw1 which has portfast enabled.
According to my book loop could form, but here is my reasoning why loop can not form in the above case.
sw2:
As soon as sw2 finds its f0/2 is up and up, it starts sending bpdu on that port while keeping that port blocked.
Sw1:
sw1 has already determined its f0/1 port being designated port when f0/1 was connected to host. When sw1 receives the bpdu on f0/1 from sw2, it will have decide again that port role.
Two things could happen:
1) port f0/1 could become a blocked port if the received bpdu from sw2 is superior.
2) port f0/1 could remain designated port if the received bpdu is not superior.
While this role is being decided, sw2's f0/2 remains blocked, so how could loop form?
Even if consider the fact that the portfast-enabled port f0/1 on sw1 was in forwarding state, when sw1 received the bpdu from sw2'f0/2, the loop should not form as sw2's f0/2 is in blocking state while sw1 is reconsidering the role for f0/1 and sw2 is considering the role for its f0/2 port.
Let say we have a switch,sw1 which has portfast enabled on f0/1. This port was formally connected to windows xp host.
Let say we have a another switch, sw2 which is also connected to same switched network like sw1.
sw2 has few ports available( not in use).
we take sw2's f0/2 port and connect it to f0/1 of sw1 which has portfast enabled.
According to my book loop could form, but here is my reasoning why loop can not form in the above case.
sw2:
As soon as sw2 finds its f0/2 is up and up, it starts sending bpdu on that port while keeping that port blocked.
Sw1:
sw1 has already determined its f0/1 port being designated port when f0/1 was connected to host. When sw1 receives the bpdu on f0/1 from sw2, it will have decide again that port role.
Two things could happen:
1) port f0/1 could become a blocked port if the received bpdu from sw2 is superior.
2) port f0/1 could remain designated port if the received bpdu is not superior.
While this role is being decided, sw2's f0/2 remains blocked, so how could loop form?
Even if consider the fact that the portfast-enabled port f0/1 on sw1 was in forwarding state, when sw1 received the bpdu from sw2'f0/2, the loop should not form as sw2's f0/2 is in blocking state while sw1 is reconsidering the role for f0/1 and sw2 is considering the role for its f0/2 port.