wierd scenario with dhcp server

[Rafael Jimenez]

I'm having a problem with clientes (pc and APs) getting their ip address from a dhcp server (windows 2008) running in a virtual machine.
The vsphere was done by a vmware team and I just had to work with they did in the past.

The attached picture shows the scenario.
1-WLC manage, ap-management and APs are in the same vlan 200.
2-DHCP server is in a port group with no tagging (0) with ip 192.168.3.3
3-vlan 30 SVI is 192.168.3.1, dhcp is in this subnet.
4-vSwitch uplinks are configured in access mode in the 4507

Problem:
everything (PCs and APs) that is connected to the vlan 200 (access vlan 200) in the cat4507 (and others SWs) is receiving a wrong ip address, instead of receive a 192.168.200.x ip addr, they are getting a 192.168.3.x ip address.

attached also a debug client mac-addr-of-ap  on the wlc  and a output on the ap.

please help me to troubleshoot this problem.
thanks.

[Traian Bratescu]

Hi,

I would asume either a networking issue or DHCP (less likely - do you use superscope on the DHCP server?).

For further troubleshooting I would do the following:

1. Put a computer in VLAN 200 and asign static IP address (one from 3.x and than one from 200.x); verify that you have network connectivity with the default gateway - if everything is configured correctly you shouldn't be able to reach the 3.1 IP address. Reconfigure it to use DHCP.

2. Make a packet capture on the DHCP Server (wireshark?) to view the exact DHCP packets that are coming in order to verify the DHCP relay functionality.... you could also use "debug dhcp detail" on the equipment which hosts the SVI interfaces.

Traian

[Rafael Jimenez]

By mistake the end user put ip default-gateway 192.168.3.254.

when I take out this command with no ip default-gateway 192.168.3.254

the probles was solved.