Wireless Access

last person joined: 18 hours ago 

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

Question about license pooling with two 6000 controllers

This thread has been viewed 0 times
  • 1.  Question about license pooling with two 6000 controllers

    Posted Sep 02, 2013 01:00 PM

    Our current setup is two 6000 controllers (1 master and 1 standby) that perform double duty (master and local). We eventually want to split out and have two dedicated master controllers and let the 6000s be local only.

     

    My question, though is with license pooling. Can we use this feature in the setup described above? From what I was reading, the license pooling happens at the master controller level and checks out licenses to the local controllers.

     

    Thanks!



  • 2.  RE: Question about license pooling with two 6000 controllers

    EMPLOYEE
    Posted Sep 02, 2013 09:35 PM

    You have to be specific.  The 6000 is just a chassis.  Do you have an M3, SC-I or SC-II in that Chassis?  Only the M3 is available for Centralized Licensing.

     

    You can use separate masters, where one is the centralized licensing server.  If anything happens to that controller however...



  • 3.  RE: Question about license pooling with two 6000 controllers

    EMPLOYEE
    Posted Sep 03, 2013 08:49 AM

    Assuming these are M3s, yes, you can enable centralized licensing in 6.3.x.  IF that master controller goes down, the aggregate license pool is available for 30 days post failure.  This is assuming your 1st scenario with 2 controllers (Master/local).

     

    Once you break out to dedicated masters, then they will be in charge of the management of these license pools.  The same failure scenario applies however.  IF BOTH masters die (extremely unlikely), then the 2 locals will have 30 days of ability to use the centralized licenses.  

     

    IF it takes you longer than 30 days to restore your mobility network, we have other issues to talk about :-)