Aruba Mobility Master Licensing Guide 5l391k

[email protected]

.

7 | Mobility Master Software Licenses

Aruba Mobility Master  | Licensing Guide

For example, (host) [mynode] (config) #change-config-node mm (host) [mm] (config) #database synchronize period 25

The example below shows a primary and backup license server connected using VRRP. Licenses must be installed on the primary Mobility Master, but are shared between that redundant pair. If the primary Mobility Master had 32 AP licenses, 32 PEFNG licenses, and 32 xSec licenses installed, both Mobility Masters would share a combined global pool of 32 AP, 32 PEFNG, and 32 xSec licenses. By default, any managed devices connected to this pair of redundant servers use licenses from this shared license pool. Figure 2 Shared Licenses on a Primary and Backup Mobility Master

Communication Between the License Server and License Clients The sharable licenses for all managed devices associated with a Mobility Master are managed through the Mobility Master license table. The information in this table is then shared with all managed devices as a pool of available licenses. When a managed device uses a license in the available pool, it communicates this change to the Mobility Master, which updates the license pool information, and sends the updated information to the managed devices. If a controller had previously installed sharable licenses before it was added to a Mobility Master as a managed device, those licenses are no longer usable on a managed device. These license keys must be added to the Mobility Master and then Mobility Master WebUI and then assign them to the Managed node. Those license keys must be regenerated and associated with to a managed device or licensing pool using the Mobility Master WebUI. When a new AP associates with managed devices, the managed devices sends updated licensing information to Mobility Master. Mobility Master then recalculates the available total for that pool, and sends the revised license count back to the managed devices. If a managed device uses an AP license from the license pool, it also


Mobility Master Software Licenses |  8

consumes a PEFNG and a RFProtect license from the pool, even if that AP has not enabled any features that would require that license. A managed device cannot use more licenses than what is ed by its controller platform, regardless of how many licenses are available in the license pool.

Multi-Version Licensing ArubaOS s multi-version licensing, which allows a managed device to run a different version of ArubaOS 6.x and 8.x software than the primary (and backup) Mobility Master. If a license is introduced in a newer version of ArubaOS, Mobility Master can still distribute licenses to licensing clients running an older version of ArubaOS, even if the managed device does not recognize the newer license type. In Mobility Master Redundancy, the standby Mobility Master becomes the standby license server. You must enable database synchronization on both active and standby Mobility Masters for the license database to synchronize.

Failover Behaviors Managed devices can continue to operate as usual in the event that a managed device fails to the Mobility Master. The following sections describe failover behaviors.

Mobility Master Fails Over to a Backup Mobility Master If the primary Mobility Master fails, the backup Mobility Master will retain the shared license limits until the backup Mobility Master reboots. If both the primary and the backup Mobility Master fail, or if the backup Mobility Master reboots before the primary Mobility Master comes back up, managed devices will retain the license limits sent to them by Mobility Master for 30 days. Although a managed device retains its licensing information for 30 days after it loses with the Mobility Master, if the managed device reboots at any time during this 30-day window, the window will restart, and the managed device will retain its information for another 30 days.

Mobility Master Must be Replaced If you need to replace a stand-alone Mobility Master, the keys installed on the previous Mobility Master must be regenerated and added to the new Mobility Master. You do not need to reinstall keys on Mobility Master if it is is using a redundancy solution with a backup Mobility Master, as the replacement Mobility Master will synchronize its licensing database with the backup Mobility Master once the replacement Mobility Master comes back online.

Mobility Master is Unreachable If a managed device does not receive three consecutive heartbeats from the Mobility Master, it assumes that Mobility Master is down, but continues to use the licenses it received from its Mobility Master license pool. When a managed device is unable to reach a license server for 30 consecutive days, it removes any shared licenses pushed to it from Mobility Master. If the 30-day window has ed and the managed device does not have enough installed licenses for all of its associated APs, the managed device will nonetheless continue to each AP. However, when an AP reboots and its managed device does not have enough licenses, that AP will not come up. For more information on replacing a managed device, see the ArubaOS 8.0.0.0 Guide.

A Managed Device is Unreachable Mobility Master sends keepalive heartbeats between the license server and the licensing client controllers every 30 seconds. If Mobility Master fails to receive three consecutive heartbeats from a client, it assumes that the licensing client is down, and that any APs associated with that client are also down or have failed over to



another controller. Therefore, Mobility Master adds any licenses used by that client back into the available pool of licenses. The WebUI of the licensing client and Mobility Master display a warning message when a licensing client and Mobility Master are unable to communicate.

An AP Fails Over to Another Licensing Client If an AP fails over from one client controller to another, the AP will be allowed to come up even if there aren’t sufficient licenses present on the backup controller. APs continue to stay active until they reboot; however, if there are not sufficient available licenses to bring up an AP after it reboots, that AP will not become active.

License Types and Usage Licenses are platform independent and can be installed on any controller. Installation of the feature license unlocks that feature’s functionality for the maximum capacity of the controller. Table 3 lists the license types and describes how licenses are consumed on the controllers. Table 3: Usage per License Type License

Usage Basis

What Consumes One License

AP

AP

An AP license is required for each operational LAN-connected, mesh, or remote AP that is advertising at least one BSSID (virtualAP).

ACR

Client Session

This license enables ArubaOS Advanced Cryptography (ACR) features. A license is required for each active client termination using Suite-B algorithms or protocols.

PEF

AP

One operational AP using one or more Policy Enforcement Firewall (PEF) features, such as intelligent application identification, policybased traffic management and controls, or stateful firewalls. NOTE: The PEF license was called PEF-NG in some previous versions of ArubaOS.

PEFV

Controller

The PEFV license allows a network 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 capacity of the controller.

RFprotect

AP

An RFProtect (RFP) license is required for each operational AP using one or more RF Protect features, such as spectrum analysis and Wireless Intrusion Protection (WIP).



License MM

VMC

WebCC

Usage Basis Associated device (Controller/AP)

AP

AP

What Consumes One License Starting with ArubaOS 8.0.1, the MM license is required to terminate devices (controllers or APs) on Mobility Master. If the Mobility Master does not have sufficient MM licenses and an AP fails to obtain a license, that AP can get an IP address and connect to its controller, but will not broadcast an SSID. Starting with ArubaOS 8.0.1, the VMC license is a sharable license required to terminate APs on a virtual controller. In ArubaOS 8.0.0, the VMC-TACT and VMC-TACT8 licenses are non-sharable licenses that must be installed on a virtual machine before you can install ArubaOS as a controller on that VM. The Web Content Classification (WebCC) license is a subscriptionbased, per-AP license that s Web content classification features on an AP for the duration of the subscription period (up to 10 years per license.

Sharable vs Controller-Specific Licenses Many licenses are consumed on a per-AP, or per- basis, and are not unique to any specific hardware device. These sharable license types can be assigned to a licensing pool and used by any device within a group of managed devices. A non-sharable licenses is generated using a controller serial number, and can only be used by the individual controller for which it was generated. Both sharable and non-sharable licenses are installed using Mobility Master, allowing network s with root-level access to remotely add licenses to any licensing pool or managed devices on the network. For more information on adding a license to a remote managed device, see License Installation on page 20. Table 4: Sharable Licenses vs Controller-Specific Licenses Sharable via a Licensing Pool AP

Controller-Specific License PEFV

ACR PEF RF Protect xSec VMC MM WebCC

Evaluation vs Permanent Licenses Each license can be either an evaluation or permanent license. A permanent license permanently enables the desired software module on a specific Aruba controller. You obtain permanent licenses through the sales order



process only. Permanent software license keys are sent to you via email. An evaluation license allows you to evaluate the unrestricted functionality of a software module on a specific controller for 90 days (in three 30-day increments). Evaluation licenses are added to Mobility Master and made sharable within a licensing pool. An expired evaluation license will remain in the license database until the controller is reset using the command write erase all, where all license keys are removed. An expired evaluation license has no impact on the normal operation of the controller, but it is kept in the license database to prevent abuse. To determine your remaining time on an evaluation license, select the Alert flag ( )in the WebUI titlebar. The WebUI displays information about evaluation license status. When an evaluation period expires: l

The controller automatically backs up the startup configuration and reboots itself at midnight (according to the system clock).

l

All permanent licenses are unaffected. The expired evaluation license feature is no longer available and is displayed as Expired in the WebUI.

Perpetual vs Subscription Licenses A perpetual license is a purchased license that has no end date; once installed, it does not expire. Most purchased licenses are perpetual licenses. The Web Content and Classification (WebCC) license is a subscription license that enables WebCC features only for the duration of the subscription (1,3,5,7 or 10 years). The subscription time period starts from the time license key is generated from the licensing Web site. Thirty days before the license period expires, an alert appears in the banner in the Mobility Master WebUI, warning the that the license is ready to expire. After the license expiration date is ed, the license continues to operate as an active license for an extended grace period of 120 days. After this final grace period elapses, the license permanently expires. Subscription licenses cannot be renewed. Once a license subscription expires, a new license subscription key must be generated and installed on Mobility Master.

Starting with ArubaOS 8.0.1, if one or more subscription WebCC licenses expire so that a controller has fewer active WebCC subscription licenses than AP licenses, that controller will no longer be able to WebCC updates from the cloud or perform classification using cloud lookup. The APs associated to that device, can, however, continue to use the cached WebCC date currently on the controller. This is a change from ArubaOS 8.0.0, where an expired WebCC license did not impact AP or controller behavior.

Licensing Best Practices and Limitations The following best practices and limitations apply to ArubaOS licenses: l

New licenses can only be associated to a managed device via the Mobility Master WebUI or command-line interfaces. Licenses cannot be added directly to a managed device.

l

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.

l

When allocating licenses, allow for the maximum quantity of licenses required at any given time. A common estimate when calculating licenses is 20 s per AP. Do not forget to consider occasional large assemblies or gatherings.

l

Before you upgrade or make database changes to Mobility Master, back up its configuration (backup flash) and its license database (license export filename.db).



l

Rebooting, resetting, or issuing the write erase command on Mobility Master does not affect its license key management database. However, issuing the write erase all command resets the device to a factory default state and deletes all databases, including the license key management database. If you reset Mobility Master to its factory default state, you must reinstall all previously-installed license keys.

l

Abnormal tampering of the Mobility Master or managed device system clock can disable evaluation licenses on that device. This can disable the features ed by this license, and affect network services.

l

The Advanced Cryptography (ACR) license includes the following caveats: n

On a platform that s 2048 IPsec tunnels, the maximum number of Suite B IPsec tunnels ed is 2048, even if a larger capacity license is installed.

n

ACR licenses are cumulative. For example, if you want to 2048 Suite B connections, you can install two ACR licenses that 1024 connections each.

n

If your Mobility Master or managed device uses an ACR license that allows fewer IPsec tunnels that is ed by that device platform, that device can still IPsec tunnels using non-Suite B modes (for example, AES-CBC), up to the platform maximum.

n

The ACR license allows Mobility Master or a managed device to use both IPsec Suite B and 802.11i Suite B connections simultaneously. The combined number of these sessions may not exceed the ACR license maximum.

n

A single client using both 802.11i Suite B and IPsec Suite B connections will simultaneously consume two ACR licenses.

ArubaOS provides the ability to move a license from one stand-alone controller to another, for maximum flexibility in managing an organization’s network and to minimize an RMA impact. Aruba monitors and detects license fraud. Abnormally high volumes of license transfers for the same license certificate to multiple devices can indicate a breach of the Aruba end software license agreement and will be investigated.



Chapter 2 Licensing Pools

Licensing Pools Overview By default, all managed devices associated to the same Mobility Master share a global pool of licenses that includes all the sharable licenses added to the Mobility Master. However, ArubaOS also allows you to create individual licensing pools at a configuration node, allowing managed devices below that node to share licenses amongst themselves but not with other managed devices.

Licensing Pool Topologies The following examples show how licenses can be allocated within one or more license pools. These examples use only AP licenses for simplicity, but the same methodology applies to all sharable licenses. For more information on licensing pool configuration, see Creating and Managing Licensing Pools on page 16

Topology 1: Global Pool Only In the topology shown in Figure 3 , all seven managed devices are part of the default "/" global license pool defined at the Mobility Master configuration root. The licenses installed on Mobility Master are all sharable between the managed devices using this global license pool. For example, if there are 100 AP licenses installed on the Mobility Master, all managed devices share the global pool of 100 AP licenses. Figure 3 All Controllers Use the Global License Pool

Table 5: License Pool Allocation for Topology 1 Pool Name / (Global pool)


Licenses from Mobility Master 100

Licensing Pools | 14

Topology 2: Global and Custom Pools If you create a license pool for the configuration node /USA, as shown in Figure 4, the four managed devices below this node use licenses from the /USA pool, while the other managed devices continue to use the global pool. In the previous example, all managed devices shared a single pool of 100 licenses. If the /USA license pool is allocated 40 of the 100 AP licenses installed on Mobility Master, the four managed devices using the /USA pool can share 40 AP licenses from Mobility Master. The global license pool now contains only 60 of the AP licenses from the Mobility Master. Figure 4 Controllers Use Global or Custom License Pools

Table 6: License Pool Allocation for Topology 2 Pool Name

AP Licenses from Mobility Master

/ (Global pool)

60

/USA

40

Topology 3: All Custom Pools If you create a separate license pool for each second-level configuration node, as shown in Figure 5, none of the managed devices is associated with the global license pool. All licenses installed on Mobility Master must be allocated to one of the three pools (/USA, /India or /China), or those licenses will not be used.

15 | Licensing Pools


Figure 5 All Controllers Use a Custom License Pool

If 40 of the 100 AP licenses installed on the Mobility Master are allocated to the /USA pool, 35 AP licenses are allocated to the /India pool, and 25 AP licenses are allocated to the /China pool, the licenses available to the managed devices within each pool will vary, as shown in Table 7. Table 7: License Pool Allocation for Topology 3 Pool Name

AP Licenses from Mobility Master

/ (Global pool)

0

/USA

40

/India

35

/China

25

Creating and Managing Licensing Pools Starting with ArubaOS 8.0.1, centralized licensing is ed on standalone controllers, and is enabled by default. Standalone controllers running ArubaOS 8.0.0 require that licenses are directly to that individual controller using the license add command.

Before you Begin If your network includes a controller running an earlier version of ArubaOS that ed the installation of licenses directly on that device, make a note of the licenses installed on that legacy device before you ArubaOS 8.0 or later. If you add that controller as a managed device under a Mobility Master, those locally installed licenses will become inactive and you will need to regenerate those keys and reinstall them via the Mobility Master.



This section contains the following information: l

Adding a Sharable License to the Global License Pool on page 17

l

Creating and Managing a Local License pool on page 17

l

Adding an Individual (non-Sharable) license to a Managed Device on page 19

Adding a Sharable License to the Global License Pool The following steps describe the procedure to add a sharable license to the global licensing pool on a Mobility Master. When adding a license, you must enable the global licensing pool in the WebUI, or issue the licensing-pool-profileroot command to enable licensing features using the command-line interface before that license can be used. For more information on the specific commands to enable individual license types, see Creating and Managing a Local License pool on page 17.

Using the WebUI To add a license via the Mobility Master WebUI: 1. In the Mobility Master node hierarchy, navigate to Configuration > System > Licensing. 2. Click the Mobility Master Licenses subtab. 3. Click + below the Key table. The Install Licenses window appears. 4. In the Install Licenses window, enter the license keyfor one or more licenses. Each license key must be on a separate line. 5. Click OK. 6. Click Apply. 7. Click Pending Changes. 8. In the Pending Changes window, select the check box and click Deploy changes.

Using the CLI From any configuration node, issue the command license add . Example: (host)[mynode](config) #license add lnZSpC2vkLMlJw8KVYdgj2

Creating and Managing a Local License pool When you add a local license pool to a configuration node, those licenses in that local pool are reserved for that configuration node, and usable only for managed devices at or below the level of configuration. For an overview of global and local license pool usage, see Licensing Pools Overview on page 14.

Using the WebUI 1. In the Mobility Master node hierarchy, navigate to Configuration > System > Licensing. 2. Select the Usage sub-tab. The License Usage table appears, showing the numbers of licenses currently used for each Mobility Master configuration node. 3. Select the configuration node for which you want to create a local license pool. 4. Select Enable Local License Pool. Another table appears below the License Usage table, showing the numbers of sharable licenses currently allocated to that license pool. If this is the first time you have



enabled a local license pool on this configuration node, this table shows zero allocated licenses for all license types. 5. Click the allocated licenses value for any license type to change the number of licenses in that license pool. The Allocate Licenses window opens, displaying the number of available licenses that are free to be allocated to a local pool. 6. Enter the number of permanent and/or evaluation licenses to be added to the selected pool, then click Done. 7. Repeat steps 6-7 as required to allocate licenses for other license types. Figure 6 Allocating Licenses for a Global License Pool

8. Click Apply. 9. Click Pending Changes. 10.In the Pending Changes window, select the check box and click Deploy changes. Starting with ArubaOS 8.0.1, the Global License Pool table displays license usage statistics for each configuration pool, as well as the license usage for the devices associated to those license pools. In ArubaOS 8.0.0, the Global license pool table does not display license usage data at the device level.

Using the CLI Navigate to the configuration node for which you want to add a local configuration pool, and issue the following command: license-pool-profile <node-path> [acr-licenses {eval key }| ][ap-licenses {eval key }| ][mm-license {eval key }| ][pefng-licenses {eval key }| ][rfp-licenses {eval key }| ][webcc-licenses {eval key }|{subscript key }][xsc-licenses [{eval key }| ]

Example:



(host)[mm] (config) #license-pool-profile /group/config (host) [mm] (License pool profile "/group/config") #ap-licenses 64

After you create the license pool, you must issue the license-pool-profile-root command to enable shared license features within the global licensing pool. (host) [mm](config) #license-pool-profile-root (host) [mm](License root(/) pool profile) #acr-license-enable The AP, Mobility Master (MM), virtual mobility controller (VMC) licenses are automatically for their specific device type. These licenses do not need to be enabled within the global licensing pool.

Adding an Individual (non-Sharable) license to a Managed Device Non-sharable licenses are generated using the serial number of a specific device, and can only be assigned to the device for which they were created. A non-sharable license is associated to an individual managed device using the Mobility Master WebUI or command-line interfaces.

Using the WebUI To add a license via the Mobility Master WebUI: 1. In the Mobility Master node hierarchy, navigate to Configuration > System > Licensing. 2. Select the Controller Licenses subtab. 3. Select the managed device to which you want to add a license. 4. The Licenses table appears, showing the licenses currently associated to that device. 5. Click + below the Licenses table. 6. Enter the serial number for one or more licenses. Each license key must be on a separate line. 7. Click OK. 8. Click Apply. 9. Click Pending Changes. 10.In the Pending Changes window, select the check box and click Deploy changes.

Using the CLI Navigate to the configuration for the managed device for which you want to add a license, then issue the command license add . Example: (host)[group/node/managed-node-14]#license add lnZSpC2vkLMlJw8KVYdgj2



Chapter 3 License Installation

Adding a License in a Mobility Master Deployment Starting in ArubaOS 8.0, the only way to install a license in a Mobility Master deployment is to install that device on Mobility Master, and then associate that license to either a specific managed device, or a shared pool of licenses. Licenses cannot be added directly to a managed device via the managed device's UI. Before you can use the Aruba Software License Management Web site to generate licenses for Mobility Master and your managed devices , you must obtain the following: l

A License Certificate ID, which you can request from your sales manager or authorized reseller

l

The auto-generated ArubaOS phrase for Mobility Master

l

The auto-generated ArubaOS phrase for any managed device installed on a server VM (virtual controller)

l

The serial numbers of your physical controllers

l

Access to the HPE Aruba licensing Web site at https://hpe.com/networking/

Starting with ArubaOS 8.0.1, a VM serial number is not required to generate a Mobility Master (VMM) or virtual mobility controller (VMC) license. This is a change from ArubaOS 8.0.0, as the licensing website does require a serial number to generate a Mobility Master (VMM) or virtual mobility controller (VMC) license for a Mobility Master or virtual managed device running ArubaOS 8.0.0. This serial number is obtained by your Aruba reseller and configured via the command product serial-number <serial-number>.

Step 1: Identify the Mobility Master phrase Use the Mobility Master phrase in the licensing website to generate a Mobility Master (MM) license, or to generate a sharable license that can be added to Mobility Master license pools. l

To identify the Mobility Master phrase, access Mobility Master via the command-line interface and issue the command show license phrase.

l

(For Mobility Master devices running ArubaOS 8.0.0 only): To identify the Mobility Master serial number, access Mobility Master via the command-line interface and issue the command show inventory.

Step 2: Identify the Serial Number or phrase for your Managed Devices Each managed device has a unique identifier that you can use to create a non-sharable, device-specific license for that managed device. A physical controller uses a serial number, and a virtual controller installed on a server VM uses an auto-generated VM phrase. l

To identify the serial number for a physical managed device, access that managed device via the commandline interface and issue the command show inventory.

l

To identify the VM phrase for a virtual controller installed on a server VM, access that managed device via the command-line interface and issue the command show license phrase.

Step 3: Enable Sharable Licensing Features You must enable Mobility Master to sharable ArubaOS licenses by enabling each licensing feature type via the Mobility Master WebUI or command-line interfaces. Enabling a licensing feature in Mobility Master activates all licenses of that type in all licensing pools, allowing managed devices to use that licensing feature.


License Installation | 20

Best practices is to perform this step before you install your sharable licenses. Installed sharable licenses will not become active until these license features are enabled.

Enabling Sharable License Features Using the WebUI To enable a sharable license via the Mobility Master WebUI: 1. In the Mobility Master node hierarchy, navigate to Configuration > System > Licensing. 2. Select the Usage sub-tab. The Global License Pool and Usage for Global License Pool tables appear. 3. In the Usage for Global License Pool table, click the check box by each license type to enable features ed by those licenses. The AP, Mobility Master (MM), virtual mobility controller (VMC) licenses are automatically for their specific device type. These licenses do not need to be enabled within the global licensing pool.

Enabling Sharable License Features Using the CLI Access the Mobility Master command-line interface in config mode and execute the following command: (host)[mm] (config) # license-pool-profile-root acr-feature-enable|pefng-feature-enable|rfpfeature-enable|webcc-feature-enable

Step 4: Create a License Key The procedures to create a license key vary, depending upon the license type. Sharable licenses and, the license required to install Mobility Master on a server VM must be generated using the Mobility Master phrase. Device-specific licenses for physical Aruba controllers are generated using the serial number for that controller. Device-specific licenses for virtual controllers installed on a server VM are generated using the phrase for that virtual managed device. Use the following procedure to create a license key via the HPE Aruba License Management Website. 1. From the HPE Aruba License Management website, select License from the navigation menu. 2. In the Order number or Registration ID/Certificate ID field, enter the certificate ID(s) you received from your Aruba sales representative or reseller, then click Next. 3. Enter the required information to identify the device that will use the license. This can be the device MAC address, serial number or IP address, depending upon the device or license type. (For ArubaOS 8.0.0 only) If you are creating a sharable or MM license key for an ArubaOS 8.0.0 Mobility Master, you must also enter the Mobility Master serial number

4. Click Next to display the licensing agreement. 5. Select I accept all of the above to accept the license agreement, then click Finish to display a table of license products for that order. 6. In the product order table, select the product name for the license you want to activate. 7. In the Redeem field, enter the number of available licenses you would like to redeem for that product, from one license to the maximum quantity available. 8. Click Next to display the confirmation page. This page displays transation details and includes options to the license key or have the key sent to a specified email adress.. 9. (Optional) Click More to return to the License navigation menu, or select More for this order to return to the product order table for the previous order and activate additional licenses for that order.

21 | License Installation


Step 5: Install the Licenses Use the Mobility Master WebUI and command-line interfaces to add sharable license keys to the global licensing pool, or to assign a non-sharable license to a specific managed device. After you receive the email with your license key, use the following procedure to add a sharable license key to the global licensing pool on Mobility Master.

Adding a Sharable License Using the WebUI To add a sharable license via the Mobility Master WebUI: 1. In the Mobility Master node hierarchy, navigate to Configuration > System > Licensing. 2. Select the Mobility Master Licenses subtab. The Key table appears 3. Click + below the Key table. The Install Licenses window appears. 4. In the Install Licenses window, enter the serial number for one or more licenses. Each license key must be on a separate line. 5. Click OK. 6. Click Apply. 7. Click Pending Changes. 8. In the Pending Changes window, select the check box and click Deploy changes. The Key table displays detailed information about the licenses added to Mobility Master, including the license type and count, expiration date (if applicable) and current status (active or expired).

Adding a Device-Specific License Using the WebUI Use the following procedure to add a MM license or any another device-specific license via the Mobility Master WebUI: 1. In the Mobility Master node hierarchy, navigate to Configuration > System > Licensing. 2. Select the Controller Licenses sub-tab. The Controller Licenses table appears. 3. Expand the Root menu in the Controller Licenses table to select the device or Mobility Master server on which you want to install the device-specific license. The license table for the selected device appears below the Controller Licenses table. 4. Click + below the device licenses table. The Install Licenses window appears. 5. In the Install Licenses window, enter the serial number for one or more licenses. Each license key must be on a separate line. 6. Click OK. 7. Click Pending Changes. 8. In the Pending Changes window, select the check box and click Deploy changes.

Adding a Sharable License Using the CLI From any configuration node, execute the command license add . Example: (host)[mynode] #license add lnZSpC2vkLMlJw8KVYdgj2

Adding a Device-Specific License Using the CLI To add a device-specific license (such as a PEF-V license) in ArubaOS 8.0.1 and later, navigate to the Mobility Master (mm) configuration node and issue the command license remote remote-ip-addr add , where is the address of the managed device to which you are adding the license. For example:



(host)[mm] #license remote remote-ip-addr 192.0.2.14 add lnZSpC2vkLMlJw8KVYdgj2

In ArubaOS 8.0.0, the command to add a license is license remote ip-addr add . The remote-ipaddr parameter was introduced to this command in ArubaOS 8.0.1.

Adding a License to a Stand-Alone Controller You can use the Aruba Software License Management website to generate all the licenses for a stand-alone master controller, or associate a stand-alone controller to an external licensing server.

Associating a Stand-Alone Controller to an External License Server If you associate a stand-alone controller to an external license server, the controller can obtain licenses from a license pool on that external server.

Using the WebUI 1. From the Mobility Controller configuration node, navigate to the Configuration > System > Licensing page of the WebUI. 2. Enable the connect to external license server option. 3. Enter the IP address of the external license server. 4. Click Submit to save your changes. Figure 7 Associating a Stand-Alone Controller to an External License Server

Via the CLI To associate a standalone controller with an external license server, issue the command no license-poolprofile-root from the Mobility Master (mm) configuration node to remove this profile, then issue the command license server-ip to define the external server.

Adding Licenses directly to the Stand-Alone Controller Before you can use the Aruba Software License Management website to generate a license for a stand-alone master controller, you must obtain the following: l

A License Certificate ID, which you can request from your sales manager or authorized reseller.

l

The serial number of the Aruba controller.

l

Access to the HPE Aruba licensing Web site https://hpe.com/networking/

Step 1: Enable Licensing Features on a Stand-Alone Controller Enable for sharable ArubaOS licenses on a stand-alone controller by enabling each licensing feature type via the controller command-line interface. If you are generating a non-sharable license for a specific managed device, you can skip this step, as the licensing features for a multi-controller topology must be enabled via Mobility Master.



Best practices is to perform this step before you install licenses on the controller. Installed licenses will not become active until the license feature is enabled.

Access the command-line interface of the stand-alone controller and execute the following command: (host)[node](config) # license-pool-profile-root acr-feature-enable|pefng-feature-enable|rfpfeature-enable|webcc-feature-enable.

Step 2: Generate the License Key Use the following procedure to create a license key for a specific controller using the certificate ID, and device serial number. 1. From the HPE Aruba License Management website, select License from the navigation menu. 2. In the Order number or Registration ID/Certificate ID field, enter the certificate ID(s) you received from your Aruba sales representative or reseller, then click Next. 3. Enter the required information to identify the device that will use the license. Depending upon the device or license type, this can be the device MAC address, serial number or IP address, (For ArubaOS 8.0.0 only) If you are creating a sharable or MM license key for an ArubaOS 8.0.0 Mobility Master, you must also enter the Mobility Master serial number

4. Click Next to display the licensing agreement. 5. Select I accept all of the above to accept the license agreement, then click Finish to display a table of license products for that order. 6. In the product order table, select the product name for the license you want to activate. 7. In the Redeem field, enter the number of available licenses you would like to redeem for that product, from one license to the maximum quantity available. 8. Click Next to display the confirmation page. This page displays transation details and includes options to the license key or have the key sent to a specified email adress.. 9. (Optional) Click More to return to the License navigation menu, or select More for this order to return to the previous product order table and activate additional licenses for that order.

Step 5: Install the Licenses After you receive the email with your license key, use the following procedure to add a license key to the standalone controller. Licenses for managed devices, even non-sharable, device-specific licenses, must be associated to the managed device via Mobility Master. Using the WebUI To add a license via the WebUI of a stand-alone controller: 1. Access the controller WebUI. 2. From the Mobility Controller configuration node, navigate to Configuration > System > Licensing. 3. Select the Inventory menu. The Key table appears. 4. Click + below the Key table. The Install Licenses window appears. 5. In the Install Licenses window, enter the serial number for one or more licenses. Each license key must be on a separate line. 6. Click OK. Using the CLI From the command-line interface of a stand-alone controller, execute the command license add . Aruba Mobility Master | Licensing Guide


Example: (host)[mm](config) #license add lnZSpC2vkLMlJw8KVYdgj2

Removing a License You can use the WebUI or command-line interfaces to remove a license key from a stand-alone controller or Mobility Master.

Using the WebUI To remove a sharable license from Mobility Master: 1. In the Mobility Master node hierarchy, navigate to Configuration > System > Licensing. 2. Click the MM Licenses tab. The Key table opens. 3. Select the license key you want to delete, then click the delete icon to the right of the highlighted key. To remove a device-specific license from a managed device: 1. Navigate to the Configuration > System > Licensing page . 2. Click the Managed device Licenses tab. The Managed device Licenses table opens. 3. Expand the root configuration group to display the Mobility Master configuration tree, then select the device with the license you want to delete. A list of non-sharable licenses used by that device appears below the Managed device Licenses table. 4. Select a license key from the list, and then click the delete icon to remove that license key. 5. Click Apply. 6. Click Pending Changes. 7. In the Pending Changes window, select the check box and click Deploy changes.

Using the CLI To delete any license (sharable or non-sharable) via the command-line interface, access the Mobility Master (mm) configuration in enable mode, and then issue the command license delete : (host)[mm] #license delete lnZSpC2vkLMlJw8KVYdgj2



Aruba Mobility Master Licensing Guide 5l391k

Overview 3z723u

More details 2i4a6q

Related Documents g842

Aruba Mobility Master Licensing Guide 5l391k

Aruba Mobility Master And Vmc Install Guide 51o3g

Aruba Activate Guide 3j5rl

Aruba Instant Guide 126e35

Aruba pm Guide 301r5o

Maya Installation Licensing Guide 4m515z

More Documents from "kamal" 30698

Automatic Pen Manufacturing Project 38d57

929

Aruba Mobility Master Licensing Guide 5l391k

Class 6 Imo Wkbsol E Book 4e5g1z

Omr Sheet Nso Imo Nco Ieo 1g1l54

Visual Inspection -sample Report For Spherical Vessel 3b6q45