Hi,
This is one that comes up in almost every network that I have been trouble shooting
lately.
In the Cisco environment set you spanning-tree portfast option on ports that have a
true one to one relationship that is, servers, clients, printers and the like.
Do NOT use portfast option on hub
Yep. Seen this one. I had a fairly large switched environment (Bay, not
Cisco) where people were failing to obtain DHCP addresses. Spanning tree
was removed and the problem went away.
Craig
At 02:45 PM 12/16/2000 -0500, you wrote:
>The potential problem is spanning tree will shut down the l
The potential problem is spanning tree will shut down the link for the first
thirty seconds (default) before passing traffic. If your computer is far
enough along in the boot proccess and makes a dhcp request before the switch
activates the port, the dhcp request will fail. Use portfast to prevent
No, but I have seen issues where Spanning Tree hampered DHCP, especially on
Catalyst 2900XL switches. PortFast is Cisco's fix for the problem but be
sure to read the precautions first.
http://www.cisco.com/warp/public/473/12.html
I apologize if this answer is taking the wrong track, I just coul
Limiting it how? Give us more information if you don't mind. Are you
running into a specific problem?
-Original Message-
From: A. Ward [mailto:[EMAIL PROTECTED]]
Sent: Friday, December 15, 2000 10:42 AM
To: [EMAIL PROTECTED]
Subject: DHCP Spanning Tree
Has anyone had issues where DHCP
5 matches
Mail list logo
