Issues with 5520 HA WLC, secondary wlc shows Duplicated IP loggs... can somebody help me...

[jjalonsom]

I have a 5520 wlc in HA, when i access to the secondary unit there is a lot of loggs like below:

Version code: 8.5.151.5, both wlc are connected to HPE switches due we don't have Cisco switches...

*pemReceiveTask: Oct 07 16:21:54.368: %DTL-3-ARP_CLIENT_IP_DUPLICATED: [SS]dtl_arp.c:1883 ARP entry overwrite, conflict detected via ARP Request from client with MAC-ID 0c:d7:46:dd:33:f8 and IP Address 172.18.13.186, Old client MAC-ID was 98:00:c6:59:81
*pemReceiveTask: Oct 07 16:19:36.052: %DTL-3-ARP_CLIENT_IP_DUPLICATED: [SS]dtl_arp.c:1883 ARP entry overwrite, conflict detected via ARP Request from client with MAC-ID d0:d2:b0:0f:7a:28 and IP Address 172.18.12.103, Old client MAC-ID was d8:8f:76:56:7a
*pemReceiveTask: Oct 07 16:16:03.003: %DTL-3-ARP_CLIENT_IP_DUPLICATED: [SS]dtl_arp.c:1883 ARP entry overwrite, conflict detected via ARP Request from client with MAC-ID d8:8f:76:b5:41:5d and IP Address 172.18.8.154, Old client MAC-ID was 6c:96:cf:6e:25:
*pemReceiveTask: Oct 07 16:09:31.254: %DTL-3-ARP_CLIENT_IP_DUPLICATED: [SS]dtl_arp.c:1883 ARP entry overwrite, conflict detected via ARP Request from client with MAC-ID 80:d6:05:2d:cd:13 and IP Address 172.18.8.56, Old client MAC-ID was 64:70:33:4c:c0:9
*pemReceiveTask: Oct 07 15:54:13.967: %DTL-3-ARP_CLIENT_IP_DUPLICATED: [SS]dtl_arp.c:1883 ARP entry overwrite, conflict detected via ARP Request from client with MAC-ID 00:db:70:99:5f:3f and IP Address 172.18.13.252, Old client MAC-ID was 18:f1:d8:98:83
*pemReceiveTask: Oct 07 15:52:30.208: %DTL-3-ARP_CLIENT_IP_DUPLICATED: [SS]dtl_arp.c:1883 ARP entry overwrite, conflict detected via ARP Request from client with MAC-ID 40:98:ad:76:22:f6 and IP Address 172.18.13.86, Old client MAC-ID was 50:bc:96:7a:59:
*pemReceiveTask: Oct 07 15:44:51.722: %DTL-3-ARP_CLIENT_IP_DUPLICATED: [SS]dtl_arp.c:1883 ARP entry overwrite, conflict detected via ARP Request from client with MAC-ID 6c:96:cf:6e:25:21 and IP Address 172.18.8.154, Old client MAC-ID was 3c:2e:ff:b7:bc:
*pemReceiveTask: Oct 07 15:41:11.825: %DTL-3-ARP_CLIENT_IP_DUPLICATED: [SS]dtl_arp.c:1883 ARP entry overwrite, conflict detected via ARP Request from client with MAC-ID 3c:2e:f9:01:42:70 and IP Address 172.18.13.83, Old client MAC-ID was d0:d2:b0:3d:4a:
*pemReceiveTask: Oct 07 15:40:50.766: %DTL-3-ARP_CLIENT_IP_DUPLICATED: [SS]dtl_arp.c:1883 ARP entry overwrite, conflict detected via ARP Request from client with MAC-ID 9c:e3:3f:2f:14:6a and IP Address 172.18.13.225, Old client MAC-ID was 3c:2e:ff:e1:e6
*pemReceiveTask: Oct 07 15:40:19.336: %DTL-3-ARP_CLIENT_IP_DUPLICATED: [SS]dtl_arp.c:1883 ARP entry overwrite, conflict detected via ARP Request from client with MAC-ID 54:35:30:71:dc:d1 and IP Address 172.18.12.189, Old client MAC-ID was 40:98:ad:05:f4
*pemReceiveTask: Oct 07 15:40:00.899: %DTL-3-ARP_CLIENT_IP_DUPLICATED: [SS]dtl_arp.c:1883 ARP entry overwrite, conflict detected via ARP Request from client with MAC-ID b0:19:c6:d8:cb:18 and IP Address 172.18.13.151, Old client MAC-ID was 3c:2e:f9:a6:e0
*pemReceiveTask: Oct 07 15:32:13.625: %DTL-3-ARP_CLIENT_IP_DUPLICATED: [SS]dtl_arp.c:1883 ARP entry overwrite, conflict detected via ARP Request from client with MAC-ID 90:dd:5d:7b:8c:98 and IP Address 172.18.13.42, Old client MAC-ID was 64:a5:c3:57:4e:
*pemReceiveTask: Oct 07 15:31:57.821: %DTL-3-ARP_CLIENT_IP_DUPLICATED: [SS]dtl_arp.c:1883 ARP entry overwrite, conflict detected via ARP Request from client with MAC-ID 64:70:33:4c:c0:98 and IP Address 172.18.8.56, Old client MAC-ID was 50:bc:96:5b:be:b
*pemReceiveTask: Oct 07 15:28:09.356: %DTL-3-ARP_CLIENT_IP_DUPLICATED: [SS]dtl_arp.c:1883 ARP entry overwrite, conflict detected via ARP Request from client with MAC-ID 34:e6:ad:13:3c:ab and IP Address 172.18.10.220, Old client MAC-ID was 40:83:1d:42:ab
*pemReceiveTask: Oct 07 15:26:05.364: %DTL-3-ARP_CLIENT_IP_DUPLICATED: [SS]dtl_arp.c:1883 ARP entry overwrite, conflict detected via ARP Request from client with MAC-ID d4:a3:3d:bf:41:32 and IP Address 172.18.9.32, Old client MAC-ID was f0:98:9d:2f:3e:b
*pemReceiveTask: Oct 07 15:23:22.980: %DTL-3-ARP_CLIENT_IP_DUPLICATED: [SS]dtl_arp.c:1883 ARP entry overwrite, conflict detected via ARP Request from client with MAC-ID 30:3a:64:5c:40:40 and IP Address 172.18.13.131, Old client MAC-ID was 74:e1:b6:08:7c
*pemReceiveTask: Oct 07 15:21:31.007: %DTL-3-ARP_CLIENT_IP_DUPLICATED: [SS]dtl_arp.c:1883 ARP entry overwrite, conflict detected via ARP Request from client with MAC-ID 64:20:0c:cf:20:4c and IP Address 172.18.11.174, Old client MAC-ID was e0:33:8e:60:f9
*pemReceiveTask: Oct 07 15:20:06.497: %DTL-3-ARP_CLIENT_IP_DUPLICATED: [SS]dtl_arp.c:1883 ARP entry overwrite, conflict detected via ARP Request from client with MAC-ID 90:48:9a:49:c2:8f and IP Address 172.18.10.255, Old client MAC-ID was 64:70:33:8d:a4
*pemReceiveTask: Oct 07 15:19:16.276: %DTL-3-ARP_CLIENT_IP_DUPLICATED: [SS]dtl_arp.c:1883 ARP entry overwrite, conflict detected via ARP Request from client with MAC-ID b4:9c:df:3a:9a:10 and IP Address 172.18.13.99, Old client MAC-ID was 80:b0:3d:e6:d8:
*pemReceiveTask: Oct 07 15:16:25.349: %DTL-3-ARP_CLIENT_IP_DUPLICATED: [SS]dtl_arp.c:1883 ARP entry overwrite, conflict detected via ARP Request from client with MAC-ID d8:8f:76:a9:29:55 and IP Address 172.18.11.14, Old client MAC-ID was ac:1f:74:50:28:
*pemReceiveTask: Oct 07 15:15:45.975: %DTL-3-ARP_CLIENT_IP_DUPLICATED: [SS]dtl_arp.c:1883 ARP entry overwrite, conflict detected via ARP Request from client with MAC-ID 9c:ad:97:90:5b:8f and IP Address 172.18.10.249, Old client MAC-ID was 88:66:a5:4b:06
*pemReceiveTask: Oct 07 15:15:14.337: %DTL-3-ARP_CLIENT_IP_DUPLICATED: [SS]dtl_arp.c:1883 ARP entry overwrite, conflict detected via ARP Request from client with MAC-ID 54:9f:13:1c:de:0f and IP Address 172.18.11.134, Old client MAC-ID was 58:e2:8f:a9:70

thanks in advance  

[Haydn Andrews]

Are the WLCs connected to the same switch?

RP port connected between the two?

Can you provide a simple diagram of how connected

[jjalonsom]

Hi @Haydn Andrews 

Thanks a lot for your replay... 

Here we have a really not good network (i can say in my favor that i don't designed it) and i see some bad practices..

Are the WLCs connected to the same switch?

No, Main is connected to Core Switch and Secondary is connected on a third switch (same with DHCP Server) as you can see in the diagram.

NOTE: no stack between switches, each switch is managed individually.

RP port connected between the two?

Yes.

Can you provide a simple diagram of how connected

find it attached. 

I see the most of times it happens in one WLAN (CW-PROP) but some occasions other WLAN shows same issue...

CW-PROD is the wlan for Cisco WLC: in the switches 

• Actually we have also one HP WLC with some APs using same vlan (172.18.0.0) and same DHCP Server, but i don't see conflicts between them... (we are trying to eliminate it but its not possible yet).
• For vlan 19 (Cisco SSID: CW-PROD,  HP SSID: VTO-ACT) no IP address in any switch, the IP address 172.18.0.1 is an interface in Firewall... so Core switch doesn't shows ARP for this vlan...

Thanks a lot for your help.

JJAM.

[jjalonsom]

Hi, I find weird that "ip duplicated loggs" are only in the Secondary WLC (HA mode) while Primary not showing it... 

I attached a notepad with logs from both WLC's

10.2.0.167
WLC SECONDARY

(Cisco Controller-Standby) >show logg

Logging to Logger Queue :
- Logging of system messages to Logger Queue :
- Effective Logging Queue filter level.......... errors
- Number of Messages recieved for logging :
- Emergency severity............................ 0
- Alert Severity................................ 0
- Critical Severity............................. 0
- Error Severity................................ 1180
- Warning Severity.............................. 3886571
- Notice Severity............................... 8
- Information Severity.......................... 1753237
- Debug Severity................................ 8
- Total messages recieved....................... 5641004
- Total messages enqueued....................... 1174
- Total messages dropped........................ 5639830
Logging to buffer :
- Logging of system messages to buffer :
- Logging filter level.......................... errors
- Number of system messages logged.............. 1179
- Number of system messages dropped.............
- Number of Messages dropped due to Facility .... 07044030

--More-- or (q)uit
- Logging of debug messages to buffer ........... Disabled
- Number of debug messages logged............... 0
- Number of debug messages dropped.............. 0
- Cache of logging ............................. Disabled
- Cache of logging time(mins) ................... 10080
- Number of over cache time log dropped ........ 0
Logging to console :
- Logging of system messages to console :
- Logging filter level.......................... disabled
- Number of system messages logged.............. 0
- Number of system messages dropped............. 7043849
- Number of system messages throttled........... 0
- Logging of debug messages to console .......... Enabled
- Number of debug messages logged............... 0
- Number of debug messages dropped.............. 0
- Number of debug messages throttled............ 0
Logging to syslog :
- Syslog facility................................ local0
- Logging of system messages to syslog :
- Logging filter level.......................... errors
- Number of system messages logged.............. 1179
- Number of system messages dropped............. 7043254
- Logging of debug messages to syslog ........... Disabled

--More-- or (q)uit
- Number of debug messages logged............... 0
- Number of debug messages dropped.............. 0
- Number of remote syslog hosts.................. 0
- syslog over tls................................ Disabled
- syslog over ipsec.............................. Disabled
- ipsec profile inuse for syslog................. none
- Host 0.......................................
- Host 1.......................................
- Host 2.......................................
Logging of Debug messages to file :
- Logging of Debug messages to file.............. Disabled
- Number of debug messages logged................ 0
- Number of debug messages dropped............... 0
Logging of traceback............................. Enabled
- Traceback logging level........................ errors
Logging of source file informational............. Enabled
Timestamping of messages.........................
- Timestamping of system messages................ Enabled
- Timestamp format.............................. Date and Time
- Timestamping of debug messages................. Enabled
- Timestamp format.............................. Date and Time

Logging buffer (1179 logged, 7044030 dropped)

--More-- or (q)uit

*pemReceiveTask: Oct 10 14:52:32.332: %DTL-3-ARP_CLIENT_IP_DUPLICATED: [SS]dtl_arp.c:1883 ARP entry overwrite, conflict detected via ARP Request from client with MAC-ID 00:db:70:4e:33:f9 and IP Address 172.18.15.20, Old client MAC-ID was a8:5c:2c:62:2d:
*pemReceiveTask: Oct 10 14:50:41.506: %DTL-3-ARP_CLIENT_IP_DUPLICATED: [SS]dtl_arp.c:1883 ARP entry overwrite, conflict detected via ARP Request from client with MAC-ID 64:70:33:20:10:17 and IP Address 172.18.11.59, Old client MAC-ID was f0:98:9d:a7:10:
*pemReceiveTask: Oct 10 14:47:10.700: %DTL-3-ARP_CLIENT_IP_DUPLICATED: [SS]dtl_arp.c:1883 ARP entry overwrite, conflict detected via ARP Request from client with MAC-ID 90:dd:5d:6d:9a:f3 and IP Address 172.18.12.204, Old client MAC-ID was b0:48:1a:56:a3
*pemReceiveTask: Oct 10 14:44:25.582: %DTL-3-ARP_CLIENT_IP_DUPLICATED: [SS]dtl_arp.c:1883 ARP entry overwrite, conflict detected via ARP Request from client with MAC-ID c8:3c:85:5b:c8:bf and IP Address 172.18.12.23, Old client MAC-ID was c0:b6:58:29:08:
*pemReceiveTask: Oct 10 14:44:15.313: %DTL-3-ARP_CLIENT_IP_DUPLICATED: [SS]dtl_arp.c:1883 ARP entry overwrite, conflict detected via ARP Request from client with MAC-ID 40:98:ad:4c:b4:b4 and IP Address 172.18.12.41, Old client MAC-ID was d4:a3:3d:16:f3:
*pemReceiveTask: Oct 10 14:44:02.901: %DTL-3-ARP_CLIENT_IP_DUPLICATED: [SS]dtl_arp.c:1883 ARP entry overwrite, conflict detected via ARP Request from client with MAC-ID 30:d9:d9:00:66:85 and IP Address 172.18.11.180, Old client MAC-ID was 78:88:6d:8c:27
*pemReceiveTask: Oct 10 14:43:53.054: %DTL-3-ARP_CLIENT_IP_DUPLICATED: [SS]dtl_arp.c:1883 ARP entry overwrite, conflict detected via ARP Request from client with MAC-ID 88:66:a5:75:cb:28 and IP Address 172.18.14.99, Old client MAC-ID was 40:98:ad:94:98:
*pemReceiveTask: Oct 10 14:43:30.559: %DTL-3-ARP_CLIENT_IP_DUPLICATED: [SS]dtl_arp.c:1883 ARP entry overwrite, conflict detected via ARP Request from client with MAC-ID cc:2d:b7:7b:9d:23 and IP Address 172.18.14.96, Old client MAC-ID was f0:98:9d:aa:45:
*pemReceiveTask: Oct 10 14:42:06.895: %DTL-3-ARP_CLIENT_IP_DUPLICATED: [SS]dtl_arp.c:1883 ARP entry overwrite, conflict detected via ARP Request from client with MAC-ID d0:2b:20:a4:57:9f and IP Address 172.18.14.163, Old client MAC-ID was 98:00:c6:3e:b5
*pemReceiveTask: Oct 10 14:39:35.184: %DTL-3-ARP_CLIENT_IP_DUPLICATED: [SS]dtl_arp.c:1883 ARP entry overwrite, conflict detected via ARP Request from client with MAC-ID 34:e6:ad:42:d8:35 and IP Address 172.18.9.83, Old client MAC-ID was b4:9c:df:1a:79:c

10.2.0.168
PRIMARY WLC
(Cisco Controller) >show logg

Logging to Logger Queue :
- Logging of system messages to Logger Queue :
- Effective Logging Queue filter level.......... errors
- Number of Messages recieved for logging :
- Emergency severity............................ 0
- Alert Severity................................ 0
- Critical Severity............................. 0
- Error Severity................................ 15178
- Warning Severity.............................. 566189
- Notice Severity............................... 94
- Information Severity.......................... 249563
- Debug Severity................................ 158
- Total messages recieved....................... 831182
- Total messages enqueued....................... 12488
- Total messages dropped........................ 818694
Logging to buffer :
- Logging of system messages to buffer :
- Logging filter level.......................... errors
- Number of system messages logged.............. 13167
- Number of system messages dropped.............
- Number of Messages dropped due to Facility .... 0936417
Warning: Output is too long and has been truncated

--More-- or (q)uit
- Logging of debug messages to buffer ........... Disabled
- Number of debug messages logged............... 0
- Number of debug messages dropped.............. 486
- Cache of logging ............................. Disabled
- Cache of logging time(mins) ................... 10080
- Number of over cache time log dropped ........ 0
Logging to console :
- Logging of system messages to console :
- Logging filter level.......................... disabled
- Number of system messages logged.............. 0
- Number of system messages dropped............. 949550
- Number of system messages throttled........... 0
- Logging of debug messages to console .......... Enabled
- Number of debug messages logged............... 486
- Number of debug messages dropped.............. 0
- Number of debug messages throttled............ 0
Logging to syslog :
- Syslog facility................................ local0
- Logging of system messages to syslog :
- Logging filter level.......................... errors
- Number of system messages logged.............. 13167
- Number of system messages dropped............. 936396
- Logging of debug messages to syslog ........... Disabled

--More-- or (q)uit
- Number of debug messages logged............... 0
- Number of debug messages dropped.............. 486
- Number of remote syslog hosts.................. 0
- syslog over tls................................ Disabled
- syslog over ipsec.............................. Disabled
- ipsec profile inuse for syslog................. none
- Host 0.......................................
- Host 1.......................................
- Host 2.......................................
Logging of Debug messages to file :
- Logging of Debug messages to file.............. Disabled
- Number of debug messages logged................ 0
- Number of debug messages dropped............... 0
Logging of traceback............................. Enabled
- Traceback logging level........................ errors
Logging of source file informational............. Enabled
Timestamping of messages.........................
- Timestamping of system messages................ Enabled
- Timestamp format.............................. Date and Time
- Timestamping of debug messages................. Enabled
- Timestamp format.............................. Date and Time

Logging buffer (13167 logged, 936903 dropped)

--More-- or (q)uit

*spamApTask4: Oct 10 14:52:42.546: %LWAPP-3-REPLAY_ERR: [PA]spam_lrad.c:45290 The system has received replay error on slot 1, WLAN ID 2, count 1 from AP 00:be:75:ba:11:10
*spamApTask5: Oct 10 14:52:30.521: %LWAPP-3-REPLAY_ERR: [PA]spam_lrad.c:45290 The system has received replay error on slot 1, WLAN ID 0, count 1 from AP 00:2c:c8:69:3a:20
*Dot1x_NW_MsgTask_5: Oct 10 14:51:55.695: %DOT1X-3-INVALID_EAPOL_VER: [PA]1x_eapkey.c:2473 Invalid EAPOL version (2) in EAPOL-key message; type 3, descriptor 2, client bc:e1:43:32:0d:95
*Dot1x_NW_MsgTask_5: Oct 10 14:51:54.674: %DOT1X-3-INVALID_EAPOL_VER: [PA]1x_eapkey.c:2473 Invalid EAPOL version (2) in EAPOL-key message; type 3, descriptor 2, client bc:e1:43:32:0d:95
*Dot1x_NW_MsgTask_5: Oct 10 14:51:53.493: %DOT1X-3-INVALID_EAPOL_VER: [PA]1x_eapkey.c:2473 Invalid EAPOL version (2) in EAPOL-key message; type 3, descriptor 2, client bc:e1:43:32:0d:95
*Dot1x_NW_MsgTask_3: Oct 10 14:51:37.540: %DOT1X-3-INVALID_REPLAY_CTR: [PA]1x_eapkey.c:452 Invalid replay counter from client 9c:ad:97:90:3d:13 - got 00 00 00 00 00 00 00 00, expected 00 00 00 00 00 00 00 01
*Dot1x_NW_MsgTask_3: Oct 10 14:51:34.846: %DOT1X-3-INVALID_EAPOL_VER: [PA]1x_eapkey.c:2473 Invalid EAPOL version (2) in EAPOL-key message; type 3, descriptor 2, client 00:db:70:d9:6b:63
*Dot1x_NW_MsgTask_1: Oct 10 14:51:23.254: %DOT1X-3-INVALID_REPLAY_CTR: [PA]1x_eapkey.c:452 Invalid replay counter from client 74:e1:b6:06:e2:39 - got 00 00 00 00 00 00 00 00, expected 00 00 00 00 00 00 00 01
*Dot1x_NW_MsgTask_3: Oct 10 14:50:43.858: %DOT1X-3-INVALID_REPLAY_CTR: [PA]1x_eapkey.c:452 Invalid replay counter from client d0:2b:20:eb:a2:ab - got 00 00 00 00 00 00 00 00, expected 00 00 00 00 00 00 00 01
*spamApTask5: Oct 10 14:48:54.107: %LWAPP-3-REPLAY_ERR: [PA]spam_lrad.c:45290 The system has received replay error on slot 1, WLAN ID 2, count 1 from AP 38:90:a5:4d:f1:50
*spamApTask0: Oct 10 14:48:51.456: %LWAPP-3-REPLAY_ERR: [PA]spam_lrad.c:45290 The system has received replay error on slot 0, WLAN ID 2, count 2 from AP 00:2c:c8:69:3b:a0
*spamApTask4: Oct 10 14:48:42.556: %LWAPP-3-REPLAY_ERR: [PA]spam_lrad.c:45290 The system has received replay error on slot 1, WLAN ID 2, count 3 from AP 00:be:75:ba:11:10
*spamApTask4: Oct 10 14:48:42.556: %LWAPP-3-REPLAY_ERR: [PA]spam_lrad.c:45290 The system has received replay error on slot 1, WLAN ID 2, count 2 from AP 00:be:75:ba:11:10
*Dot1x_NW_MsgTask_6: Oct 10 14:48:24.112: %DOT1X-3-INVALID_REPLAY_CTR: [PA]1x_eapkey.c:452 Invalid replay counter from client 04:15:52:3a:3a:3e - got 00 00 00 00 00 00 00 00, expected 00 00 00 00 00 00 00 01
*Dot1x_NW_MsgTask_1: Oct 10 14:46:52.610: %DOT1X-3-INVALID_REPLAY_CTR: [PA]1x_eapkey.c:452 Invalid replay counter from client 6c:29:95:a8:68:49 - got 00 00 00 00 00 00 00 00, expected 00 00 00 00 00 00 00 01
*spamApTask4: Oct 10 14:46:44.152: %LWAPP-3-REPLAY_ERR: [PA]spam_lrad.c:45290 The system has received replay error on slot 1, WLAN ID 3, count 3 from AP 00:2c:c8:69:34:30
*spamApTask4: Oct 10 14:46:42.559: %LWAPP-3-REPLAY_ERR: [PA]spam_lrad.c:45290 The system has received replay error on slot 1, WLAN ID 2, count 2 from AP 00:be:75:ba:11:10
*spamApTask4: Oct 10 14:46:42.559: %LWAPP-3-REPLAY_ERR: [PA]spam_lrad.c:45290 The system has received replay error on slot 1, WLAN ID 2, count 1 from AP 00:be:75:ba:11:10
*Dot1x_NW_MsgTask_0: Oct 10 14:45:25.831: %DOT1X-3-PSK_CONFIG_ERR: [PA]1x_ptsm.c:749 Client 58:40:4e:ce:15:00 may be using an incorrect PSK
*spamApTask4: Oct 10 14:44:44.155: %LWAPP-3-REPLAY_ERR: [PA]spam_lrad.c:45290 The system has received replay error on slot 1, WLAN ID 3, count 2 from AP 00:2c:c8:69:34:30
*spamApTask4: Oct 10 14:44:42.562: %LWAPP-3-REPLAY_ERR: [PA]spam_lrad.c:45290 The system has received replay error on slot 1, WLAN ID 2, count 37 from AP 00:be:75:ba:11:10
*Dot1x_NW_MsgTask_0: Oct 10 14:44:24.958: %DOT1X-3-INVALID_EAPOL_VER: [PA]1x_eapkey.c:2473 Invalid EAPOL version (2) in EAPOL-key message; type 3, descriptor 2, client 58:40:4e:ce:15:00

--More-- or (q)uit

[Leo Laohoo]

---

@jjalonsom wrote:
Version code: 8.5.151.5

---

Go back to TAC and get them to diagnose this.  The firmware is an Engineering Release version.

[jjalonsom]

Hi @Leo Laohoo thanks for your advice...

I am in contact with TAC, but they sent me the firmware due a Bug in APs (AIR-AP1572EAC-A-K9) and the IP conflict messages has been there before the upgrade...

https://bst.cloudapps.cisco.com/bugsearch/bug/CSCvm68624/?reffering_site=dumpcr

The main issue with i opened a case with the TAC is because we have many clients (cell phone re-manufacturing) and a lot of them are connected to wireless but they shows a timeouts or high times response and people in production floor  complain of connectivity...  

[Leo Laohoo]

---

@jjalonsom wrote:
*pemReceiveTask: Oct 07 15:15:45.975: %DTL-3-ARP_CLIENT_IP_DUPLICATED: [SS]dtl_arp.c:1883 ARP entry overwrite, conflict detected via ARP Request from client with MAC-ID 9c:ad:97:90:5b:8f and IP Address 172.18.10.249, Old client MAC-ID was 88:66:a5:4b:06  

---

What happens if you clear our the DHCP lease?
Look at the error message above:  OUI "88:66:A5" is Apple while "9C:AD:97" is HonHai.
The only time I ever saw this was when the DHCP lease was full.  The error message, to me, is an "FYI"-like saying that the DHCP server is "re-using" the IP address.  The IP address was "last seen" or "last used" by a HonHai client and now it will be handed to an Apple client.

[jjalonsom]

Thanks @Leo Laohoo  for your comments, honestly i had not thought your suggestions... great...

What happens if you clear our the DHCP lease?

I never tried to do this.. Today was a busy day but tomorrow morning i will do... (I had not thought of it)...

Here is the actual DHCP information:

DHCP
Scope: 172.18.0.0
Total addresses 5279
in use: 3018 (57%)
available 2261 (42%)
Start IP: 172.18.0.31
End IP: 172.18.20.200

Lease Duration DHCP: 10 Minutes

Thanks a lot 

JJAM.