I have an MM (AOS 22.214.171.124) up and mostly happy (just getting the lab built, so I'm a lot green) and am trying to connect the first MC (using a VMC to get started)
When the VMC first boots, I get the initial configuration dialog and walk through all the steps. I provide the IP address of the MM and a PSK - then hop over to the MM GUI to add the VMC and PSK so the connection will be waiting for it - and complete the dialog.
The VMC reboots and never appears to check in with the MM.
I look at running configuration on VMC and see nothing to indicate my MM settings, and don't see any suspicious loggin on MM to indicate an attempted connection.
How do I start to troubleshoot this?
I have istalled the MM license - but it was the last step. Nothing magically started to work afterwards, and I decided to ask for advice before rebuilding the VMC again.
I see today that I have MM licenses in the pool, but none in use - wouldn't my MM use one out of the pool?
I have to assign what to the global pool?
The master IS the pool isn't it?
The VMC as entered into the MM's heirarchy shows up in the Global Licensing Pool, but it hasn't connected to the MM yet (shows down in controller list)
I'm trying to troubleshoot the getting connected part - I'm sure it'll buy a license from the pool once it checks-in.
Solved: my error. <sigh>
I entered the PSK with spaces on one and without spaces on the other.
TAC reminded me:
The command "encryption disable" followed by "show running" shows the problem. The undocumented command to bypass MM control and change the PSK on the VMC fixed it.
All better now.
At Aruba, we believe that the most dynamic customer experiences happen at the Edge. Our mission is to deliver innovative solutions that harness data at the Edge to drive powerful business outcomes.
© Copyright 2020 Hewlett Packard Enterprise Development LPAll Rights Reserved.