Resetting VHM (NG HMOL)

  • 1
  • Question
  • Updated 9 months ago
I've encountered some issues with migration from classic to NG that damaged my NG VHM. Focus from engineering will help prevent this from happening to others, but i'm left with irreparable issues that have stumped the best. 

My question is if anyone has had experience with resetting the VHM. I'm aware that it should start me fresh, but my concern is ensuring the existing AP's run fine until i get the policies rebuilt and pushed. My PPSK users that are in the cloud will obviously be affected, but how about RADIUS and such? Any other advice?
Photo of Jeremy Stewart

Jeremy Stewart

  • 47 Posts
  • 0 Reply Likes

Posted 9 months ago

  • 1
Photo of BJ

BJ, Champ

  • 374 Posts
  • 45 Reply Likes
Well, you've put quite a bit out there. First, as longs as you don't push anything to your APs, they will continue to function. We migrated several devices to an on-prem NG VM over a year ago and I'm assuming we're discussing NG online.

Regarding resetting the VHM, we've had to restart the database and reboot the VM, and at one point earlier this year, even had to rebuild our policies after an NG update pooched the database.

After recent updates to NG, you should be able to export/import your PPSK users & passwords. As far as the manual process of duplicating your configs from classic, I recommend putting two browser windows side by side and mirroring as much as possible. Beyond that, what exactly broke during your migration?