Aruba & ProVision-based
1753797 Members
9093 Online
108805 Solutions
New Discussion юеВ

Re: issue with dhcp snooping and windows wds server

 
Doutreleau Eric
Occasional Contributor

issue with dhcp snooping and windows wds server

Hi there
We have installed bunches of 2650 switchs on the edge of our network.
all these switches are impleting the dhcp-snooping
here is the config
DHCP Snooping Information

DHCP Snooping : Yes
Enabled Vlans : 10 15-16 21-22 24 26 28 31 33 50 60 70 100 103 110 120 130 140 160-161 190

Verify MAC : Yes
Option 82 untrusted policy : drop
Option 82 Insertion : No

Store lease database : Yes
URL : tftp://157.159.21.31/switchs/switch-B01
Read at boot : no
Write delay : 300
Write timeout : 300
File status : delaying
Write attempts : 4
Write failures : 3
Last successful file update : Mon Jun 8 09:02:14 2009


Port Trust
---- -----
1 No
.........
49 Yes
50 No

The dhcp snooping is working well.
We have installed a WDS server on the same network and in the same physical location than the DHCP server.

But the installation with wds failed. we got the following message on the client console

file: \boot\bcd

status: 0xc000000f

Info: An error occured while attempting to read the boot configuration data.

When i disable the dhcp snooping it works quite good.

i have some question on how dhcp snooping work.

i haven't put any dhcp server on the authorized section. then can i use several dhcp server as long as they answer from the trusted port?

WDS use some weird options to pass information to the client. Especially it uses option 252. does dhcp snooping remove that kind of information?

Thanks for any help. I would prefer not remove the dhcp snooping from my switch.

 

 

P.S. This thread has been moved from Switches, Hubs, Modems (Legacy ITRC forum) to ProCurve / ProVision-Based. - Hp Forum Moderator

4 REPLIES 4
cenk sasmaztin
Honored Contributor

Re: issue with dhcp snooping and windows wds server

windows deployment service use Pre-Boot Execution Environment (PXE)dhcp feature

there fore wds server port must be trust port
cenk

Doutreleau Eric
Occasional Contributor

Re: issue with dhcp snooping and windows wds server

Well my wds server is on a trusted port.

it seems that the dhcp answer from the wds server are "cleaned" by the dhcp snooping mechanism.
macneill_tru
New Member

Re: issue with dhcp snooping and windows wds server

Did you find a solution?

ChrisDrake
New Member

Re: issue with dhcp snooping and windows wds server

Use dhcp-snooping authorized-server command and specify the ip adresses of your WDS servers