Cisco Support Community
cancel
Showing results for 
Search instead for 
Did you mean: 
Community Member

DHCP wierd issue!!

Ok we have a branch office connected to HO using GRE tunnel. All users in branch are configured to get IP from the DHCP server in HO. Everything works fine, users get their IP from HO DHCP and no one complains. The issue arises when a user either from the HO moves his laptop to the branch or vice versa. When this move happens, users are not able to get an IP from the DHCP server. Instead it would eventually retain its old IP, which means no connectivity. I have the DHCP debug output posted below, has anyone faced this issue before? Please suggest.

--------------------------------------------------------------

*Mar 17 23:35:40.948: IP: s=0.0.0.0 (Vlan155), d=255.255.255.255, len 358, input feature, MCI Check(73), rtype 0, forus FALSE, sendself FALSE, mtu 0, fwdchk FALSE

*Mar 17 23:35:40.948: IP: s=0.0.0.0 (Vlan155), d=255.255.255.255, len 358, rcvd 2

*Mar 17 23:35:40.948: IP: s=0.0.0.0 (Vlan155), d=255.255.255.255, len 358, stop process pak for forus packet

*Mar 17 23:35:40.948: DHCPD: Reload workspace interface Vlan155 tableid 0.

*Mar 17 23:35:40.948: DHCPD: tableid for 172.13.1.2 on Vlan155 is 0

*Mar 17 23:35:40.948: DHCPD: client's VPN is .

*Mar 17 23:35:40.948: DHCPD: DHCPREQUEST received from client 0110.78d2.c162.73.

*Mar 17 23:35:40.948: DHCPD: client has moved to a new subnet.

*Mar 17 23:35:40.948: DHCPD: Sending notification of ASSIGNMENT FAILURE:

*Mar 17 23:35:40.948:   DHCPD: htype 1 chaddr 1078.d2c1.6273

*Mar 17 23:35:40.948:   DHCPD: remote id 020a0000ac1002030c000000

*Mar 17 23:35:40.948:   DHCPD: interface = Vlan155

*Mar 17 23:35:40.948:   DHCPD: class id 4d53465420352e30

*Mar 17 23:35:40.948:   DHCPD: out_vlan_id 0

*Mar 17 23:35:40.948: DHCPD: Sending notification of ASSIGNMENT_FAILURE:

*Mar 17 23:35:40.948:  DHCPD: due to: CLIENT CHANGED SUBNET

*Mar 17 23:35:40.948:   DHCPD: htype 1 chaddr 1078.d2c1.6273

*Mar 17 23:35:40.948:   DHCPD: remote id 020a0000ac1002030c000000

*Mar 17 23:35:40.948:   DHCPD: interface = Vlan155

*Mar 17 23:35:40.948:   DHCPD: class id 4d53465420352e30

*Mar 17 23:35:40.948:   DHCPD: out_vlan_id 0

*Mar 17 23:35:40.948: DHCPD: Sending DHCPNAK to client 0110.78d2.c162.73.

*Mar 17 23:35:40.948: DHCPD: no option 125

*Mar 17 23:35:40.948: DHCPD: broadcasting BOOTREPLY to client 1078.d2c1.6273.

*Mar 17 23:35:40.948: IP: s=0.0.0.0 (local), d=255.255.255.255 (Vlan155), len 328, local feature, RCLI(7), rtype 0, forus FALSE, sendself FALSE, mtu 0, fwdchk FALSE

*Mar 17 23:35:40.948: IP: s=0.0.0.0 (local), d=255.255.255.255 (Vlan155), len 328, local feature, Local Clustering(8), rtype 0, forus FALSE, sendself FALSE, mtu 0, fwdchk FALSE

*Mar 17 23:35:40.948: IP: s=0.0.0.0 (local), d=255.255.255.255 (Vlan155), len 328, local feature, Wireless Controller(10), rtype 0, forus FALSE, sendself FALSE, mtu 0, fwdchk FALSE

*Mar 17 23:35:40.948: IP: s=172.13.1.2(local), d=255.255.255.255 (Vlan155), len 328, sending broad/multicast

*Mar 17 23:35:40.948: IP: s=172.13.1.2(local), d=255.255.255.255 (Vlan155), len 328, sending full packetpak 5931DFC consumed in input feature , packet consumed, MCI Check(73), rtype 0, forus FALSE, sendself FALSE, mtu 0, fwdchk FALSE pak 57AA9C8 consumed in input feature , packet consumed, MCI Check(73), rtype 0, forus FALSE, sendself FALSE, mtu 0, fwdchk FALSE

*Mar 17 23:35:40.965: IP: s=0.0.0.0 (Vlan155), d=255.255.255.255, len 328, input feature, MCI Check(73), rtype 0, forus FALSE, sendself FALSE, mtu 0, fwdchk FALSE

*Mar 17 23:35:40.965: IP: s=0.0.0.0 (Vlan155), d=255.255.255.255, len 328, rcvd 2

*Mar 17 23:35:40.965: IP: s=0.0.0.0 (Vlan155), d=255.255.255.255, len 328, stop process pak for forus packet

*Mar 17 23:35:40.965: DHCPD: Reload workspace interface Vlan155 tableid 0.

*Mar 17 23:35:40.965: DHCPD: tableid for 172.13.1.2 on Vlan155 is 0

*Mar 17 23:35:40.965: DHCPD: client's VPN is .

*Mar 17 23:35:40.965: DHCPD: using received relay info.

*Mar 17 23:35:40.965: DHCPD: Sending notification of DISCOVER:

*Mar 17 23:35:40.965:   DHCPD: htype 1 chaddr 1078.d2c1.6273

*Mar 17 23:35:40.965:   DHCPD: interface = Vlan155

*Mar 17 23:35:40.965:   DHCPD: class id 4d53465420352e30

*Mar 17 23:35:40.965:   DHCPD: out_vlan_id 0

*Mar 17 23:35:40.965: DHCPD: DHCPDISCOVER received from client 0110.78d2.c162.73 on interface Vlan155

*Mar 17 23:35:40.965: DHCPD: using received relay info.

*Mar 17 23:35:40.965: DHCPD: Sending notification of DISCOVER:

*Mar 17 23:35:40.965:   DHCPD: htype 1 chaddr 1078.d2c1.6273

*Mar 17 23:35:40.965:   DHCPD: interface = Vlan155

*Mar 17 23:35:40.965:   DHCPD: class id 4d53465420352e30

*Mar 17 23:35:40.965:   DHCPD: out_vlan_id 0

*Mar 17 23:35:40.965: DHCPD: there is no address pool for 172.13.1.2.

*Mar 17 23:35:40.965: DHCPD: Looking up binding using address 172.13.1.2

*Mar 17 23:35:40.965: DHCPD: setting giaddr to 172.13.1.2.

*Mar 17 23:35:40.965: DHCPD: BOOTREQUEST from 0110.78d2.c162.73 forwarded to 192.168.11.10.

*Mar 17 23:35:40.965: DHCPD: BOOTREQUEST from 0110.78d2.c162.73 forwarded to 192.168.11.11.

*Mar 17 23:35:40.982: DHCPD: Reload workspace interface Vlan155 tableid 0.

*Mar 17 23:35:40.982: DHCPD: tableid for 172.13.1.2 on Vlan155 is 0

*Mar 17 23:35:40.982: DHCPD: client's VPN is .

*Mar 17 23:35:40.982: DHCPD: DHCPOFFER notify setup address 192.168.15.50 mask 255.255.255.0

*Mar 17 23:35:40.982: DHCPD: forwarding BOOTREPLY to client 1078.d2c1.6273.

*Mar 17 23:35:40.982: DHCPD: Forwarding reply on numbered intf

*Mar 17 23:35:40.990: DHCPD: no option 125

*Mar 17 23:35:40.990: DHCPD: Check for IPe on Vlan155

*Mar 17 23:35:40.990: DHCPD: creating ARP entry (192.168.15.50, 1078.d2c1.6273).

*Mar 17 23:35:40.990: DHCPD: SIOCSARP ioctl failed (error 22).

*Mar 17 23:35:40.990: DHCPD: broadcasting BOOTREPLY to client 1078.d2c1.6273.

-----------------------------------------------------------------------------------------------------------

The IP address highlighted in red is the IP from the HO. The user retains the same IP in the branch as well which means no connectivity.

Suggestions required.

Thanks.

2 REPLIES
Hall of Fame Super Bronze

DHCP wierd issue!!

The offer is made by your DHCP server, the cisco devices are simply passing the information.

You need to verify your DHCP server configuration.

Community Member

Does anybody solve this issue

Does anybody solve this issue? I got the same one.

Thank you beforehand. 

2423
Views
1
Helpful
2
Replies
CreatePlease to create content