I've run into this one personally. Not only can't you get an IP address,
but on a faster machine, you can start domain login before you actually
have network connectivity too.
If you add things like trunking and PAgP to the mix, the delay is even
longer. Thats why I turn off EtherChannel and Trunking on all user node
ports as well Portfast. The spanning tree port negotiation still takes
place, but its done in the background after connectivity is established.
Karen E Young
Network Engineer
ELF Technologies, Inc
[EMAIL PROTECTED]
Desk: 206-770-4035
Pager: 206-994-4514
"Tuline, Andrew"
<AndrewTuline@SierraSy To: "'[EMAIL PROTECTED]'"
<[EMAIL PROTECTED]>
stems.com> cc:
Sent by: Subject: Ethernet switches and
DHCP problem
[EMAIL PROTECTED]
07/20/00 04:38 PM
Please respond to
"Tuline, Andrew"
Here's a Microsoft article that discussed how DHCP can have problems with
the Spanning Tree.
http://support.microsoft.com/support/kb/articles/q168/4/55.asp?LN=EN-US&SD=g
n&FR=0
My understanding from this article is that when a port goes active (due to
powerup of a PC), that it will cause the Spanning Tree Algorithm to
determine if there's a loop, effectively shutting down the port for 10-15
seconds.
If I'm to take this literally, then it would behoove me to implement
PortFast as much as possible, so that I don't have any problems. Funny, I
haven't noticed this before though.
Anyone have comments on this?
Andrew Tuline CCNA, CCDP (only CIT is remaining)
___________________________________
UPDATED Posting Guidelines: http://www.groupstudy.com/list/guide.html
FAQ, list archives, and subscription info: http://www.groupstudy.com
Report misconduct and Nondisclosure violations to [EMAIL PROTECTED]
___________________________________
UPDATED Posting Guidelines: http://www.groupstudy.com/list/guide.html
FAQ, list archives, and subscription info: http://www.groupstudy.com
Report misconduct and Nondisclosure violations to [EMAIL PROTECTED]
