H-REAP problem after upgrading to 4.2.112

Unanswered Question
May 6th, 2008
User Badges:

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
  • 2
  • 3
  • 4
  • 5
Overall Rating: 0 (0 ratings)
Loading.
cbaser007 Wed, 05/07/2008 - 06:33
User Badges:

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.

Actions

This Discussion

 

 

Trending Topics - Security & Network