With upgrade of WLC to 8.3.143 : CDP-4DUPLEX_MISMATCH: error is showing up.

[Sharath Karpur]

Dear All, 

I have just upgraded my test LAB WLC from 8.2.166.0 to 8.3.143.0 and observing AP connected switch ports are logging below error. ( I am not much convinced for removing CDP configuration and increasing the syslog severity level)

I am sure this because of upgrade, I went to through some blogs of similar post. But my question is what will be the stable release that I should go for ? ( i have 2505, 5508 & 5520 WLC's ).  Could you please suggest.

082621: Sep 6 08:04:56.048 UTC: %CDP-4-DUPLEX_MISMATCH: duplex mismatch discovered on GigabitEthernet1/0/45 (not half duplex), with AP GigabitEthernet0 (half duplex).
082622: Sep 6 08:05:21.633 UTC: %CDP-4-DUPLEX_MISMATCH: duplex mismatch discovered on GigabitEthernet1/0/46 (not half duplex), with AP GigabitEthernet0 (half duplex).
082623: Sep 6 08:05:52.556 UTC: %CDP-4-DUPLEX_MISMATCH: duplex mismatch discovered on GigabitEthernet1/0/45 (not half duplex), with AP GigabitEthernet0 (half duplex).
082624: Sep 6 08:06:15.562 UTC: %CDP-4-DUPLEX_MISMATCH: duplex mismatch discovered on GigabitEthernet1/0/46 (not half duplex), with AP GigabitEthernet0 (half duplex).
082625: Sep 6 08:06:52.940 UTC: %CDP-4-DUPLEX_MISMATCH: duplex mismatch discovered on GigabitEthernet1/0/45 (not half duplex), with AP GigabitEthernet0 (half duplex).
082626: Sep 6 08:07:13.727 UTC: %CDP-4-DUPLEX_MISMATCH: duplex mismatch discovered on GigabitEthernet1/0/46 (not half duplex), with AP GigabitEthernet0 (half duplex).
082627: Sep 6 08:07:53.091 UTC: %CDP-4-DUPLEX_MISMATCH: duplex mismatch discovered on GigabitEthernet1/0/45 (not half duplex), with AP GigabitEthernet0 (half duplex).
082628: Sep 6 08:08:10.648 UTC: %CDP-4-DUPLEX_MISMATCH: duplex mismatch discovered on GigabitEthernet1/0/46 (not half duplex), with AP GigabitEthernet0 (half duplex).

Regards

Sharath

[Leo Laohoo]

This is a very, very popular bug:  CSCve98689, CSCvi02106, CSCvg42928, CSCvj57770

I recommend raising a TAC case so TAC can confirm/verify which of the Bug IDs you're hitting.

[Sharath Karpur]

some blogs suggest to upgrade to 8.5.135 as it is know as some stable release.. would you also think so and Do you have this version running in your systems ?

[Sharath Karpur]

Any known bug with 8.5.135 release ? 

Also in the release notes of 8.5.135 they say we can upgrade directly from 8.2.16X to 8.5.131.0. is that also mean that we can upgrade directly to 8.5.135 release ? or its restricted to 8.5.131 only ? 

could someone please clarify.

https://www.cisco.com/c/en/us/td/docs/wireless/controller/release/notes/crn85mr3.html#whats-new-in-8dot5mr3

[Leo Laohoo]

---

@Sharath Karpur wrote:

Also in the release notes of 8.5.135 they say we can upgrade directly from 8.2.16X to 8.5.131.0. is that also mean that we can upgrade directly to 8.5.135 release ? or its restricted to 8.5.131 only  

---

Read the Release Notes.  It will state that you can go direct to 8.5.135.0 from 8.2.X.X.

[Vivek_Shukla]

I am also hitting the same bug even after upgrading to 8.5.135.0 . 

As per TAC this is resolved in 8.8.xx or the workaround is to disable LAG