cancel
Showing results for 
Search instead for 
Did you mean: 
cancel
326
Views
0
Helpful
1
Replies

H-REAP problem after upgrading to 4.2.112

cbaser007
Level 1
Level 1

I just upgraded a WLC from 4.1.185 to 4.2.112. Now none of my H-REAP AP's will connect to the WLC. It appears that they connected long enough to upgrade their code, but never reappear after the reboot. The AP ports are trunked and VLAN tagging is enabled on the WLC H-REAP AP Config. Did anything change from 4.1.185 to 4.2.112?

1 Reply 1

cbaser007
Level 1
Level 1

Update - After 4 hours 45 minutes the H-REAP AP's joined the WLC and stayed connected. I rebooted one to see what would happen and after an hour it's still bouncing on the WLC. Very strange that AP's in local mode are fine.

Getting Started

Find answers to your questions by entering keywords or phrases in the Search bar above. New here? Use these resources to familiarize yourself with the community:

Review Cisco Networking products for a $25 gift card