cancel
Showing results for 
Search instead for 
Did you mean: 
cancel
531
Views
10
Helpful
3
Replies

CAPWAP-IDB Error logs on catalyst 9800

Hello,

 

I have a catalyst 9800 WLC showing repeated CAPWAP-IDB Error lines in "show logging" output (pasted a sample below).

Any chance someone knows what this is about ? I tried googling the full error text (without timestamps) as well as different parts of the line separately but i could not find any result. Even searching for "CAPWAP-IDB Error" gives 0 results.

 

Thanks,

Have a nice day.

 

 

Sample error lines :

Feb 23 2021 11:31:35.520 UTC: CAPWAP-IDB Error : A0000082 - GET SWIDB : Search failed for iifid[Count : 145]
Feb 23 2021 11:31:35.520 UTC: CAPWAP-IDB Error : A0000082 - GET SWIDB : Search failed for iifid[Count : 145]
Feb 23 2021 11:31:35.718 UTC: CAPWAP-IDB Error : A0000082 - GET SWIDB : Search failed for iifid[Count : 145]
Feb 23 2021 11:31:35.718 UTC: CAPWAP-IDB Error : A0000082 - GET SWIDB : Search failed for iifid[Count : 145]
Feb 23 2021 11:31:36.106 UTC: CAPWAP-IDB Error : A0000082 - GET SWIDB : Search failed for iifid[Count : 145]
Feb 23 2021 11:31:36.406 UTC: CAPWAP-IDB Error : A0000082 - GET SWIDB : Search failed for iifid[Count : 145]
Feb 23 2021 11:31:36.724 UTC: CAPWAP-IDB Error : A0000082 - GET SWIDB : Search failed for iifid[Count : 145]
Feb 23 2021 11:31:36.724 UTC: CAPWAP-IDB Error : A0000082 - GET SWIDB : Search failed for iifid[Count : 145]
Feb 23 2021 11:31:36.724 UTC: CAPWAP-IDB Error : A0000082 - GET SWIDB : Search failed for iifid[Count : 145]
Feb 23 2021 11:31:37.210 UTC: CAPWAP-IDB Error : A0000082 - GET SWIDB : Search failed for iifid[Count : 145]
Feb 23 2021 11:31:37.314 UTC: CAPWAP-IDB Error : A0000082 - GET SWIDB : Search failed for iifid[Count : 145]
Feb 23 2021 11:31:37.314 UTC: CAPWAP-IDB Error : A0000082 - GET SWIDB : Search failed for iifid[Count : 145]
Feb 23 2021 11:31:37.538 UTC: CAPWAP-IDB Error : A0000082 - GET SWIDB : Search failed for iifid[Count : 145]

3 REPLIES 3
marce1000
VIP Advisor

 

 - Which software version ? Check if a more recent advisory release is available then currently installed, if so it is advised to upgrade.

 M.

Hi Tom.  Like @marce1000 says always specify what software version you're using.

The only related bug I see is https://bst.cloudapps.cisco.com/bugsearch/bug/CSCvt58409 but that doesn't look exactly like your problem.  So update to the latest version of code to see whether it resolves the problem and/or open a case with Cisco TAC.

Hello,

 

Yes, i forgot to specifiy that we were using 17.1.1s, which is a deferred version. Updating to 17.3.1 seems to have fixed the issue, and also improved the 5GHz stability.

Content for Community-Ad