...
+ Entries in device-tracking database getting stuck in "CREATING" state and not getting purged properly: switch#show device-tracking database vlanid 62 vlanDB has 9989 entries for vlan 62, 9989 dynamic Codes: L - Local, S - Static, ND - Neighbor Discovery, ARP - Address Resolution Protocol, DH4 - IPv4 DHCP, DH6 - IPv6 DHCP, PKT - Other Packet, API - API created Preflevel flags (prlvl): 0001:MAC and LLA match 0002:Orig trunk 0004:Orig access 0008:Orig trusted trunk 0010:Orig trusted access 0020:DHCP assigned 0040:Cga authenticated 0080:Cert authenticated 0100:Statically assigned Network Layer Address Link Layer Address Interface vlan prlvl age state Time left ARP 10.62.44.202 0000.0000.00fd 62 0000 13mn CREATING ARP 10.62.55.199 0000.0000.00fd 62 0000 9mn CREATING ARP 10.62.55.172 0000.0000.00fd 62 0000 9mn CREATING ARP 10.62.55.175 0000.0000.00fd 62 0000 9mn CREATING
+ Seen on 17.6.3 + Entries are created for non-existent devices from a sweeper that sends ICMP PING Requests to discover devices on the network
+ Increase the Device-Tracking database max entries: switch(config)#device-tracking binding max-entries 700000
+ Once the database is over-utilized, any more traffic such as ARP will get dropped until clearing the database: switch#show device-tracking messages | i DROP [Wed Oct 12 17:19:14.000] VLAN 362, From Po119 MAC 2cf4.c5f8.fa16: ARP::REQ, 192.168.184.153, Drop reason=Address limit per box reached [Wed Oct 12 17:19:14.000] VLAN 662, From Po102 MAC 0012.7ffc.d524: ARP::REQ, 10.128.62.206, Drop reason=Address limit per box reached [Wed Oct 12 17:19:15.000] VLAN 401, From Po119 MAC 000e.2202.f479: ARP::REP, 10.40.5.254, Drop reason=Address limit per box reached + Resolved in 17.6.4