Onboard as replacement feature

  • 1
  • Idea
  • Updated 1 year ago
I'm in the process of rolling out over 300 APs and have had a few die after a couple week burn-in (which was expected) I think a great feature in the onboarding process would be that if you are onboarding one device, you can choose another device to have it replace. It would clone the old AP (and perhaps rename it to hostname_old or somesuch) so that you can just go out, swap the pyhsical devices and be done rather than having to choose the right config, set the location, set the hostname, etc. 
Photo of Johnny Matthews

Johnny Matthews

  • 34 Posts
  • 2 Reply Likes

Posted 1 year ago

  • 1
Photo of Nick Lowe

Nick Lowe, Official Rep

  • 2491 Posts
  • 451 Reply Likes
Hi Johnny,

Thanks for the suggestion. Which model(s) of AP are you deploying?

Regards,

Nick
Photo of Johnny Matthews

Johnny Matthews

  • 34 Posts
  • 2 Reply Likes
AP130, AP250, AP550, and AP245X
Photo of Nick Lowe

Nick Lowe, Official Rep

  • 2491 Posts
  • 451 Reply Likes
Did you take a look at our auto-provisioning feature? This may achieve what you want.

Thanks,

Nick
(Edited)
Photo of Johnny Matthews

Johnny Matthews

  • 34 Posts
  • 2 Reply Likes
The idea is more about replacement rather than initial rollout. A one-step way to say "replace this AP with this new AP" would be handy. That way when I have an AP go down I can provision a new AP in the box as a replacement for a dead AP and hand it to a student worker to go do the install. When it comes up it will take the old one's place and optionally delete the old one from the hivemanager. Just an idea of something that takes up time. Not sure if it is useful to others.
Photo of Peter Powell

Peter Powell

  • 6 Posts
  • 3 Reply Likes
+++ We just deployed over 3000 APs as part of hardware upgrade and had to manually place each one on our maps. This is a really necessary function to support real world ongoing maintenance and is something I have seen in previous system we have had.