CAPWAP connection lost and config. failures could be your cable plant

  • 1
  • Idea
  • Updated 3 years ago
I inherited an existing Aerohive environment and was always annoyed by pervasive CAPWAP connection failed messages and even more by intermittent but persistent issues with configuration update delays and failures. Nothing I found in the knowledgebase was helping. One day I was repairing a network jack and I realized the infrastructure cabling that the WAPs are connected to is only CAT 5. We were running the WAP network ports at 1 Gbps. I set the switchports down to 100 Mbps and it was like night and day. All the CAPWAPs alerts went away and the updates are as smooth as silk so if you're having issues validate your cable plant. If you're in an old building it's likely populated with CAT5 and 100 Mbps will be your rated limit. 
Photo of Derek Morton

Derek Morton

  • 1 Post
  • 0 Reply Likes

Posted 3 years ago

  • 1
Photo of Mike Kouri

Mike Kouri, Official Rep

  • 1026 Posts
  • 269 Reply Likes
D'oh! Thank you for this posting, all too often people overlook the simple stuff and I an certain your advice will help a number of people here.
Photo of MST


  • 152 Posts
  • 3 Reply Likes
While cable can be issue, I have noticed with VM 6.6 HM that Access Points 230 and a couple of 390 randomly lost connection to HM. The cables were checked and are ok - all CAT6 new cables. With HM 6.5 I never seen any problems like that.