Wireless Access

Hi,

So I have a customer with with a licensed controller, PEF+APs etcetera. We want to migrate to a conductor-based deployment. Reading through all documentation on licensing from what I understand all licensing (AP/APRF/PEF is managed through the conductors (except PEFV) and you need to convert your existing controller licenses to licenses that can be managed through the conductor? Is that correct? Hope someone can confirm, although i did find an older post stating you need to contact TAC if would be great if someone can confirm.

Thank you

Hi,

Does this answer your question: 
https://arubanetworking.hpe.com/techdocs/VIA/3x/content/via%20config/before_you_begin.htm?Highlight=license

Also, this is the licensing Guide which explains it in Detail:
https://arubanetworking.hpe.com/techdocs/ArubaOS-8.x-Books/87/ArubaOS-8.7.0.0-Licensing-Guide.pdf

As in the regards to PEFV, it states:
4. PEFV License: (Alias Box License)
• The PEFV license allows a network administrator to apply firewall policies to clients using a VPN to connect to the
controller. This license is mandatory for the Aruba VIA VPN client, but optional for all other VPN clients. The PEFV
license is purchased as a single license that enables the functionality up to the full user capacity of the controller.
• Usage Basis: Per Controller

Hi,

So I have a customer with with a licensed controller, PEF+APs etcetera. We want to migrate to a conductor-based deployment. Reading through all documentation on licensing from what I understand all licensing (AP/APRF/PEF is managed through the conductors (except PEFV) and you need to convert your existing controller licenses to licenses that can be managed through the conductor? Is that correct? Hope someone can confirm, although i did find an older post stating you need to contact TAC if would be great if someone can confirm.

Thank you

Hi Shpat,

Thanks for sharing, this is very helpful and I think I was on the right track. If I read these two paragraphs thoroughly:

• Sharable vs Controller-Specific Licenses
• Best Practices and Limitations

So if I understand this correctly AP capacity and PEF are shareable licenses.

I conclude I have to go to TAC and have them regenerate the shareable licenses (AP/PEF). Based on the text below in Italics  I conclude I do need to go to TAC to regenerate these licenses to run on the conductors. Am I right? Thanks again for finding this doc

If a controller had previously installed sharable licenses before it was added to Mobility Master as a
managed device, those licenses are no longer usable on a managed device. Those license keys must be
regenerated, added to Mobility Master, and assigned to the managed device or licensing pool using the
Mobility Master WebUI.

Hi,

Does this answer your question: 
https://arubanetworking.hpe.com/techdocs/VIA/3x/content/via%20config/before_you_begin.htm?Highlight=license

Also, this is the licensing Guide which explains it in Detail:
https://arubanetworking.hpe.com/techdocs/ArubaOS-8.x-Books/87/ArubaOS-8.7.0.0-Licensing-Guide.pdf

As in the regards to PEFV, it states:
4. PEFV License: (Alias Box License)
• The PEFV license allows a network administrator to apply firewall policies to clients using a VPN to connect to the
controller. This license is mandatory for the Aruba VIA VPN client, but optional for all other VPN clients. The PEFV
license is purchased as a single license that enables the functionality up to the full user capacity of the controller.
• Usage Basis: Per Controller

Hi,

So I have a customer with with a licensed controller, PEF+APs etcetera. We want to migrate to a conductor-based deployment. Reading through all documentation on licensing from what I understand all licensing (AP/APRF/PEF is managed through the conductors (except PEFV) and you need to convert your existing controller licenses to licenses that can be managed through the conductor? Is that correct? Hope someone can confirm, although i did find an older post stating you need to contact TAC if would be great if someone can confirm.

Thank you

In the license management part of the networking support portal, there should be a "v Licenses" drop down menu that has the option 'Transfer License'. With that, you can transfer the license yourself to a mobility conductor.

Hi Shpat,

Thanks for sharing, this is very helpful and I think I was on the right track. If I read these two paragraphs thoroughly:

• Sharable vs Controller-Specific Licenses
• Best Practices and Limitations

So if I understand this correctly AP capacity and PEF are shareable licenses.

I conclude I have to go to TAC and have them regenerate the shareable licenses (AP/PEF). Based on the text below in Italics  I conclude I do need to go to TAC to regenerate these licenses to run on the conductors. Am I right? Thanks again for finding this doc

If a controller had previously installed sharable licenses before it was added to Mobility Master as a
managed device, those licenses are no longer usable on a managed device. Those license keys must be
regenerated, added to Mobility Master, and assigned to the managed device or licensing pool using the
Mobility Master WebUI.

Hi,

Does this answer your question: 
https://arubanetworking.hpe.com/techdocs/VIA/3x/content/via%20config/before_you_begin.htm?Highlight=license

Also, this is the licensing Guide which explains it in Detail:
https://arubanetworking.hpe.com/techdocs/ArubaOS-8.x-Books/87/ArubaOS-8.7.0.0-Licensing-Guide.pdf

As in the regards to PEFV, it states:
4. PEFV License: (Alias Box License)
• The PEFV license allows a network administrator to apply firewall policies to clients using a VPN to connect to the
controller. This license is mandatory for the Aruba VIA VPN client, but optional for all other VPN clients. The PEFV
license is purchased as a single license that enables the functionality up to the full user capacity of the controller.
• Usage Basis: Per Controller

Hi,

So I have a customer with with a licensed controller, PEF+APs etcetera. We want to migrate to a conductor-based deployment. Reading through all documentation on licensing from what I understand all licensing (AP/APRF/PEF is managed through the conductors (except PEFV) and you need to convert your existing controller licenses to licenses that can be managed through the conductor? Is that correct? Hope someone can confirm, although i did find an older post stating you need to contact TAC if would be great if someone can confirm.

Thank you

Hi Shpat,

Thanks for sharing, this is very helpful and I think I was on the right track. If I read these two paragraphs thoroughly:

• Sharable vs Controller-Specific Licenses
• Best Practices and Limitations

So if I understand this correctly AP capacity and PEF are shareable licenses.

I conclude I have to go to TAC and have them regenerate the shareable licenses (AP/PEF). Based on the text below in Italics  I conclude I do need to go to TAC to regenerate these licenses to run on the conductors. Am I right? Thanks again for finding this doc

If a controller had previously installed sharable licenses before it was added to Mobility Master as a
managed device, those licenses are no longer usable on a managed device. Those license keys must be
regenerated, added to Mobility Master, and assigned to the managed device or licensing pool using the
Mobility Master WebUI.

Hi,

Does this answer your question: 
https://arubanetworking.hpe.com/techdocs/VIA/3x/content/via%20config/before_you_begin.htm?Highlight=license

Also, this is the licensing Guide which explains it in Detail:
https://arubanetworking.hpe.com/techdocs/ArubaOS-8.x-Books/87/ArubaOS-8.7.0.0-Licensing-Guide.pdf

As in the regards to PEFV, it states:
4. PEFV License: (Alias Box License)
• The PEFV license allows a network administrator to apply firewall policies to clients using a VPN to connect to the
controller. This license is mandatory for the Aruba VIA VPN client, but optional for all other VPN clients. The PEFV
license is purchased as a single license that enables the functionality up to the full user capacity of the controller.
• Usage Basis: Per Controller

Hi,

So I have a customer with with a licensed controller, PEF+APs etcetera. We want to migrate to a conductor-based deployment. Reading through all documentation on licensing from what I understand all licensing (AP/APRF/PEF is managed through the conductors (except PEFV) and you need to convert your existing controller licenses to licenses that can be managed through the conductor? Is that correct? Hope someone can confirm, although i did find an older post stating you need to contact TAC if would be great if someone can confirm.

Thank you