Wednesday, 11 March 2015

DHCP scope exhausted with BAD_ADDRESS enteries

I noticed a new VM would not get a DHCP address from one of the customers DC's, after remoting into the DC we could see that the scope was full. Upon further inspection the scope had been filled with BAD_ADDRESS entries. We selected all the BAD_ADDRESSES and deleted them, but within minutes it was full again.  I knew it had to be some of the new equipment we had plugged in, this was disconnected and I used the PoSh below to see if any new BAD_ADDRESS entries emerged.

Get-DhcpServerv4Lease -ScopeId "" | Where {$_.HostName -eq "BAD_ADDRESS"}

Isolated the problem to two new downstream Force 10 MXL switches that have DHCP enabled in the default VLAN. The commands below were issued on the switch to resolve the problem with the scope filling.

>interface VLAN 1
>no IP address DHCP
>do wr

The PoSh command above was used to make sure that no new BAD_ADDRESS entries existed.

No comments:

Post a Comment