why only on edge devices? what do you mean by edge? last year we added Exchange 2003 to our network and i was having issues with it. when it booted some of the Exschange services would not start and had to be done manually. when i enabled fast link on this port the problem disappered Nigel
great - i was hoping you would say computers. so by enabling this i would think boot time of PCs on our domain would improve too, as the network would be found and connected quicker. would you agree?
The ability for the network switch to forward "user traffic" from your client PC or host sooner than 45secs which is standard spanning tree (L2 switch sequence of device contect : learning -> listening -> forwarding).
By using fastlink (or also known as portfast) you skip the learning, listening stages and hence speed up access to the network.
Caveats : Only use for PC ,Server device........not meant for router --> switch, or switch --> switch conenctions, because you could cause a broadcast storm. In normal SPT stages the port would "listen" for BPDU's (Bridge Protocol Data Units) to ensure a loop free topology - and only going into forwarding mode if safe to do so.
Hence must be a PC or server - as you are the decision point now !!
As long as you PC/Server IP stack and application build are well organised you sholud be able to access the netwotk straight away.
drgnslyr
19 Posts
0
January 29th, 2008 13:00
NigelRobson
1 Rookie
•
54 Posts
0
January 29th, 2008 13:00
drgnslyr
19 Posts
0
January 29th, 2008 14:00
NigelRobson
1 Rookie
•
54 Posts
0
January 29th, 2008 14:00
sentinel-master
345 Posts
0
February 3rd, 2008 11:00
The ability for the network switch to forward "user traffic" from your client PC or host sooner than 45secs which is standard spanning tree (L2 switch sequence of device contect : learning -> listening -> forwarding).
By using fastlink (or also known as portfast) you skip the learning, listening stages and hence speed up access to the network.
Caveats : Only use for PC ,Server device........not meant for router --> switch, or switch --> switch conenctions, because you could cause a broadcast storm. In normal SPT stages the port would "listen" for BPDU's (Bridge Protocol Data Units) to ensure a loop free topology - and only going into forwarding mode if safe to do so.
Hence must be a PC or server - as you are the decision point now !!
As long as you PC/Server IP stack and application build are well organised you sholud be able to access the netwotk straight away.