Discovery not populating Cisco WAP IP Addresses
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎01-29-2025 06:15 AM
We are currently experiencing an issue where around 200 out of >13k WAPs are not populating the IP address field.
When I test the Cisco WAP pattern on the Controller, I can see that Discovery is pulling the IP Address for the WAPs fine, but not populating the record.
Does anybody know where to start to fix this issue of IP address not populating for Cisco WAP?
Thank you!
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎01-29-2025 07:18 AM
- There are no changes to the IP Address field in the Audit list.
- The device is listed with the IP address in the ECC Queue Payload for Network Switch Pattern
- The devices with missing IP addresses are not listed under the Devices tab, but still have the 'Most recent discovery' value updated.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎02-02-2025 06:55 PM
I noticed this issue appeared to have been resolved in v6.21.3 of Visibility Content
I updated to the latest, 6.23.0, and can confirm Discovery is now working as expected for me: WAP IP addresses are correctly populated.
Tony
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎02-02-2025 04:44 PM
Hi Jeffrey
I have the same issue. Pattern debug shows that the IP addresses are retrieved from the WLC, they are in the payload, and payload processing shows no errors. But the IP addresses aren't populated in the WAP table, although all other attributes are.
I suspect we may be experiencing this: DISCOVERY: IP Address Not Updating for Wireless Access Points - Known Error
I personally don't see the error in the logs referred to in the KB, and I'm on 6.19.1 of Visibility Content, but it's close enough for me to think this is the cause.
Tony