Exactly the same mistake.
-
Thank you very much for the quick response. Well, I will try to use the google translator to comment.
As reported to me, our network makes use of the MSTP. I thought that with this protocol, no port fast configuration would be necessary. Although I don’t understand how to implement it on my network.
However on Monday when I get back to work I will try this as a network person.
Thank you!
-
@Sckendall While I have worked with STP and RSTP I don’t know too much about MSTP. Searching the web I found this: https://www.arubanetworks.com/techdocs/ArubaOS_74_Web_Help/Content/mas_guides/mstp/Portfast.htm
When the link on a bridge port goes up, MSTP runs its algorithm on that port. If the port is connected to a host that does not “speak” MSTP, it takes approximately 30 seconds for the port to transition to the forwarding state. During this time, no user data passes through this bridge port and some user applications may timeout.
-
@Sckendall MSTP should be an extension to RTP with the option of having multiple STP zones. BUT not all switch manufacturer implement it the same way. Some when you turn on MSTP, RTP features are enabled other MSTP is just a multizone extension to STP, where the fast spanning tree needs to be enabled separately.
Or to say it with less words MSTP !(always)= Multizone RTP. Check with your switch manufacture if you need to enable the port_fast equivalent with MSTP.
-
@george1421, Thank you! I will try this now.
-
Thank you guys! It worked here.
Initially we deactivated STP and activated port fast on a swicht port and it worked very quickly.
Apparently the solution is between disabling STP and enabling port fast. We will do more tests later to see which solution is most ideal.
I believe that this issue can now be marked as resolved!
-
@Sckendall said in Exactly the same mistake.:
apparently the solution is between disabling STP and enabling port fast.
Just to be clear because others may get confused. You did not disable STP and enable port fast, but you turned on port-fast features which changed STP to RSTP (rapid spanning tree).
STP is still enabled, but its using optimistic blocking (hope there is no loop back while checking - rapid spanning tree protocol) instead of pessimistic blocking (assume there is a loop back while checking - standard spanning tree protocol).
-
Well, that’s what the person from the networks told me.
So when enabling port fast on a particular port, am I enabling RSTP at the same time?
From what I saw in the management of the Switch, there are two options to check, () STP and just below () Fast Link. From what I was told, the STP option was deselected and Port Link was checked
-
@Sckendall said in Exactly the same mistake.:
So when enabling port fast on a particular port, am I enabling RSTP at the same time?
Yes, RSTP is an extension of STP. I assume in the web ui its a radio button in that you can select STP or port fast (another name for RSTP). We are saying the same thing, I was just concerned about someone following this thread in the future when you said “turn off STP”. Its not a good idea to ever turn off spanning tree on user facing network ports. Users do dumb things every so often.
-
@george1421, well, i think i understand now.
-
I have another problem on a different subnet. “TFTP open time out …”. I’m searching the forum and there are several topics, but I still don’t understand the solution. I don’t know if you could help me around here or would I need to create another topic?
-
@Sckendall Best to create a new topic.
-
@Sckendall Yes start a new topic, they are free and keep problems and solutions together with the subject of the thread.
