Wireless Access

last person joined: 27 minutes ago 

Access network design for branch, remote, outdoor and campus locations with Aruba access points, and mobility controllers.
Expand all | Collapse all

License not allocated for AP in VMM/VMC setup

Jump to Best Answer
This thread has been viewed 11 times
  • 1.  License not allocated for AP in VMM/VMC setup

    Posted Sep 16, 2021 05:31 AM
    Hi,

    we set up a VMM VMC environment in our lab. We us eval licenses an a global license pool.



    The controllers are connected to the MM. Configuration of the setup works well but the APs (AP-205) don't allocate a license. We started using 8.8.0.1, downgraded to 8.6.0.13 but the behaviuor is the same in both versions.

    APs are in a rebooting loop:

    Sep 16 12:00:16 stm[5665]: <305038> <5665> <WARN> |stm| No available license type VMC for AP AP-LAB01
    Sep 16 12:01:00 stm[5665]: <305038> <5665> <WARN> |stm| No available license type VMC for AP AP-LAB01
    Sep 16 12:11:21 sapd[1662]: <311002> <WARN> |AP AP-LAB01@192.168.155.149 sapd| Rebooting: Reboot requested by controller
    Sep 16 12:11:24 sapd[1662]: <311002> <WARN> |AP AP-LAB01@192.168.155.149 sapd| Rebooting: SAPD: Reboot requested by controller
    Sep 16 12:11:25 nanny[1637]: <303086> <ERRS> |AP AP-LAB01@192.168.155.149 nanny| Process Manager (nanny) shutting down - AP will reboot!
    Sep 16 12:14:19 KERNEL(AP-LAB01@192.168.155.149): [ 30.438000] uol_init_driver:409 HW offload not applicable, AP will use cutting through path!
    Sep 16 12:14:21 nanny[1637]: <303022> <WARN> |AP AP-LAB01@192.168.155.149 nanny| Reboot Reason: AP rebooted Thu Sep 16 12:11:25 CEST 2021; SAPD: Reboot requested by controller

    I did not find an explanation for the 

    stm[5665]: <305038> <5665> <WARN> |stm| No available license type VMC for AP AP-LAB01

    message. 

    A "show ap database" gives inconsistent information depending on where the command is run:

    (MobilityMaster01) [mm] #show ap database

    AP Database
    -----------
    Name Group AP Type IP Address Status Flags Switch IP Standby IP
    ---- ----- ------- ---------- ------ ----- --------- ----------
    AP-LAB01 default 205 192.168.155.149 Down 2 192.168.155.209 0.0.0.0
    AP-RZ01 SeclabAP 205 192.168.155.145 Up 11m:49s 2 192.168.155.209 0.0.0.0

    Total APs:2



    (MobilityMaster01) [mm] #cd MobilityController02
    (MobilityMaster01) [00:0c:29:0c:34:3c] #mdconnect

    Redirecting to Managed Device Shell

    (MobilityController02) [MDC] #show ap database

    AP Database
    -----------
    Name Group AP Type IP Address Status Flags Switch IP Standby IP
    ---- ----- ------- ---------- ------ ----- --------- ----------
    AP-LAB01 default 205 192.168.155.149 Down 2 192.168.155.209 0.0.0.0
    AP-RZ01 SeclabAP 205 192.168.155.145 Up 12m:10s 2IL 192.168.155.209 0.0.0.0



    Flag on MM is 2   -> seems to be ok but is a lie.
    Flag on MC is 2IL -> inactive and not  license seems to be the truth.


    Any idea how I can fix or narrow down the problem? 






    ------------------------------
    Joachim Becker
    ------------------------------


  • 2.  RE: License not allocated for AP in VMM/VMC setup
    Best Answer

    Posted Sep 16, 2021 08:54 AM
    Looks that you have VMC (virtual/VM) controllers. Do you have those controllers licensed?
    I would have expected the VA-MC-RW as an additional column in the license view screenshot.

    ------------------------------
    Herman Robers
    ------------------------
    If you have urgent issues, always contact your Aruba partner, distributor, or Aruba TAC Support. Check https://www.arubanetworks.com/support-services/contact-support/ for how to contact Aruba TAC. Any opinions expressed here are solely my own and not necessarily that of Hewlett Packard Enterprise or Aruba Networks.

    In case your problem is solved, please invest the time to post a follow-up with the information on how you solved it. Others can benefit from that.
    ------------------------------



  • 3.  RE: License not allocated for AP in VMM/VMC setup

    Posted Sep 16, 2021 09:19 AM
    Hello Herman,

    that was indeed missing. I  thougth we just need the MM licenses, what is true if you have hardware controllers but not for VMCs. After adding the MC-VA-RW. 

    Thank you very much.


    ------------------------------
    Joachim Becker
    ------------------------------