- Community Home
- >
- Networking
- >
- Wireless
- >
- M and MSM Series
- >
- rfmgr_ap: Error starting foreground scan on Radio ...
Categories
Company
Local Language
Forums
Discussions
Forums
- Data Protection and Retention
- Entry Storage Systems
- Legacy
- Midrange and Enterprise Storage
- Storage Networking
- HPE Nimble Storage
Discussions
Forums
Discussions
Discussions
Forums
Discussions
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Community
Resources
Forums
Blogs
- Subscribe to RSS Feed
- Mark Topic as New
- Mark Topic as Read
- Float this Topic for Current User
- Bookmark
- Subscribe
- Printer Friendly Page
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
07-21-2016 10:45 AM
07-21-2016 10:45 AM
rfmgr_ap: Error starting foreground scan on Radio (on 2.4GHz radio)
Hi,
I recently upgraded my access-points to firmware 6.6.4. Since then, I observe some recurrent clients deconnections on several access points. I investigated in logs, and found this recurring line (sometimes separated by ~ 30 seconds from a same access point):
rfmgr_ap: Error starting foreground scan on Radio [1 or 2, according to access point model; I have MSM410s and MSM460s]
I cannot assert that this is related to clients deconnections, but:
- I found online evidences that deconnections may occur during a scan,
- I'm willing to tackle the issue for the readability of my log files nonetheless.
I reduced scan ratio to 0.1%, dwell time to 20ms; scan mode is passive on operating-only band and regulatory-only channels.
Documentation lead me to believe these parameters were related to neighborhood scanning (current 'HP MSM APs Configuration Guide', p49), however my configuration is set to 'no wireless-scan', so I wonder how all this adds up.
On some posts, it is said that scan is related to RRM and/or IDS; I still have these messages with these disabled. I also disabled 'severe interference detection' (which may trigger scans if I recall correctly).
Any ideas ?
--
Jean-Jacques Puig