we have a 3560 switch configured with EIGRP with dhcp. We have a user that we cannot ping, however the interface show up / up and no errors on interface. the ip address is 10.2.0.199 - however we have dhcp configured to exclude the range from dhcp
ip dhcp excluded-address 10.22.0.1 10.22.0.200
how can this work station get a dhcp address if we have that ip range excluded from the dhcp pool?
The user is off a different switch that is a uplink to this distribution switch. Traceroutes shows that the problem is with the distribution switch.
Since this user is on a different switch, do you have another dhcp server on the switch that they're connected to? Also, can you do a "sh ip dhcp bind" and see if you can see the address assigned to that host? Did you do the exclusion after bringing up the scope? If so, you may have assigned the host before the exclusion was done. In that case, the host wouldn't get a new address until their lease had expired.
As other friends discussed here, the ip dhcp excluded-address is valid only for new leases, not for leases that already have been assigned. You may even need to issue the clear ip dhcp binding * command to force the DHCP server to forget individual assigned leases and start assigning new IP addresses according to the current configuration, including the excluded address ranges.
There are two independent issues being solved here, in my opinion - you are complaining that the PC is assigned an IP address via DHCP that should not have been assigned at all. The second issue is that the PC itself can not be pinged. But is it certain that this IP address is indeed assigned via DHCP? Also, you have metnioned running the show ip dhcp vrf XXX binding - do you run your DHCP pools in VRFs? Are the interfaces in correct VRFs as well, then?
Perhaps posting the configuration of the device that runs the DHCP server would be helpful here.
[toc:faq]The ProblemOn traditional switches whenever we have a trunk
interface we use the VLAN tag to demultiplex the VLANs. The switch needs
to determine which MAC Address table to look in for a forwarding
decision. To do this we require the switch to do...
[toc:faq]Introduction:Netdr is a tool available on a RSP720, Sup720 or
Sup32 that allows one to capture packets on the RP or SP inband. The
netdr command can be used to capture both Tx and Rx packets in the
software switching path. This is not a substitut...
IntroductionOSPF, being a link-state protocol, allows for every router
in the network to know of every link and OSPF speaker in the entire
network. From this picture each router independently runs the Shortest
Path First (SPF) algorithm to determine the b...