Tek-Tips is the largest IT community on the Internet today!

Members share and learn making Tek-Tips Forums the best source of peer-reviewed technical information on the Internet!

  • Congratulations strongm on being selected by the Tek-Tips community for having the most helpful posts in the forums last week. Way to Go!

Port Fast 1

Status
Not open for further replies.

talcs

IS-IT--Management
Mar 25, 2003
86
GB
I have 3 switches on a customers network. A 1900, 2900 and a 2950. I am having a problem with Win98 clients receiving a Dynamic address from a Windows 2K DHCP server. I have checked the Port fast setting and it appears that all are enabled by default. Should I disable PF for ports that have switches daisy chained or servers plugged into them? These clients can receive address by ipconfig /renew_all or when there is little activity on the switch.
 
You can only get DHCP addresses on the Win98 machines when you do it manually? Have you tried updating the Win98 drivers for the NIC?

Portfast should be enabled for all "host" machines connected to the switches. I would even include servers in this "host" qualification.
 
Drivers are up to date. Also there are a number of various pc brands thus limiting the chance of it being the nic. Ports are set to operate at half duplex. I have not checked each pc, but assume most are 10mb nics.

Some documentation seemed to indicate portfast should be disabled for devices such as servers and interconnected switches. Couldn't quite see the point of this.
 
Does you config look like this?

interface FastEthernet0/1
spanning-tree portfast
 
Portfast shortens the whole block/listen/learn/forward cycle, but doesn't disable spanning tree. It should be disabled wherever there is a chance of a loop - switches for sure, but servers can also be an issue if they start routing/bridging. I haven't seen it cause any issues with DHCP, but definitely with IPX logon.

This might be helpful --->
-Ken
 
portfast effectivly disables spanning-tree on the port. It causes the port to go into a forwarding state immediately bypassing the blocking/learning/listening states essential to spanning tree.

 
Spanning tree loop detection is still in operation when portfast is enabled. The port would be set to blocking state if a loop was detected.
 
The FastEthernet ports are set to Disable. All other interface ports are set to enable. FE ports are connecting to routers.
 
Hi,
Ports configured with portfast do still participate in spanning tree. If the port is part of a loop it will EVENTUALLY move into blocked state. During this time there is the possibility of a loop condition, the vast increase in traffic may cause BPDUs to be dropped by the switches in the loop and the loop condition not being rectified.
Portfast should only be configured on HOST ports, not on ports that interconnect switches.
There is an enhancement to Portfast, BPDUGUARD. This effectively makes a port configured to portfast "look out" for BPDUs (a host will never send a BPDU) - if the port sees a BPDU packet it will take a configured action on that port (e.g. shutdown the port immediately).
More info is available at
Cheers,
Phil.

If everything is coming your way then you're in the wrong lane.
 
Status
Not open for further replies.

Part and Inventory Search

Sponsor

Back
Top