169 IP issue in specific Vlan

[Shadow_200]

Hi All ,

I am getting 169.X.X.X IP in vlan 103.

As i checked DHCP pool for same vlan, Pool was not full. aslo there are no IP conflict .

as I change the interface vlan from 103 to 104 , system take the IP from vlan 104 and when I revert it back to vlan 103 then system easily take IP from Vlan 103. and after some time system realeased the IP and again take 169 IP.

Multiple users in single vlan is affected .

Please suggest.

[Flavio Miranda]

Hi

 This is a real device or simulador?

 Something you can do to work around is extend the lease time but for sure something weird is there.

 It is a good idea look in the logs or/and debug.

[Shadow_200]

this is real working scenario .

[MHM Cisco World]

show ip dhcp statistic <<- share this please 
also are you use any dhcp exclude with broadcast subnet mask ?

[Shadow_200]

this is C9300-24Y device and dont know why but sh ip dhcp statistics  command is not taking by device .

getting option like.

sh ip dhcp ?

binding

conflict

database

exclude-address

import

limit

pool

relay server

snooping

vrf

and I am not using ip dhcp exclude with braodcast subnet mask.

IOS version 17.05.01

[MHM Cisco World]

Some times it take and other it not!! 

Now let start TS

The vlan103 have SVI and vlan104 have SVI both have pool with correct GW point to SVI IP of vlan103/104

Can I see this config ?

Are you using any l2 secuirty in SW like dhcp snooping DAI ..etc. ?

[Shadow_200]

interface Vlan103
ip address 10.41.44.2 255.255.255.0
standby 103 ip 10.41.44.1
standby 103 priority 90
standby 103 preempt
arp timeout 240

interface Vlan104
ip address 10.41.45.2 255.255.255.0
standby 104 ip 10.41.45.1
standby 104 priority 150
standby 104 preempt
arp timeout 240

snooping configuration on L2

sh run | i snooping

ip dhcp snooping vlan 1-2,50,55,100-105
no ip dhcp snooping information option
ip dhcp snooping
ip dhcp snooping trust
ip dhcp snooping trust

[MHM Cisco World]

https://www.routexp.com/2019/08/configure-hsrp-aware-dhcp-relay.html

the HSRP explain some of this unnormal behave,
the HSRP must config with dhcp reply and the DHCP server must point to other Network Device and not run DHCP in any of HSRP peer