ArubaOS 8.6.0.0 Help Center

Centralized Licensing Support for IPv6

ArubaOS now supports centralized licensing architecture in IPv6 network also, where a local controller containing IPv4 or IPv6 address acts as the license client and communicates with the license server containing IPv6 address to obtain the available licenses. The centralized licensing information is sent between license server and license client through heartbeat messages based on UDPUser Datagram Protocol. UDP is a part of the TCP/IP family of protocols used for data transfer. UDP is typically used for streaming media. UDP is a stateless protocol, which means it does not acknowledge that the packets being sent have been received.. With the introduction of IPv6 address support, the heartbeat messages between the license server and license client must use IPv6 address as source and destination IP address.

 

The license server now supports both IPv4 and IPv6 address clients. However, you cannot configure both IPv4 and IPv6 addresses and must configure either IPv4 address or IPv6 address as license server IP address.

Associating Mobility Master or Stand-alone Controller to External License Server

You can associate one or more stand-alone controllers or Mobility Masters to an external license server, allowing the controller or Mobility Master to obtain licenses from a license pool on that external server. If Mobility Master connects to a license server, that Mobility Master then acts a proxy license server, distributing licenses to the managed devices that are part of the root licensing pool on the Mobility Master server.

If you use an external license server, all primary and backup Mobility Master servers, and standalone controllers must be able to communicate with the external license server. Managed devices associated to Mobility Master do not need connectivity with the license server.

You can connect one or more stand-alone controllers or Mobility Masters to an external license server in the following scenarios:

Single Mobility Master and Local Controller in IPv6 Network

The centralized licensing feature is supported in a single Mobility Master that acts as a centralized license server configured with IPv6 controller IP address. A local controller works as a license client that is configured with IPv6 controller IP address as shown in the following table:

Table 1: Mobility Master and Local Controller in IPv6 matrix

License Server Controller IP

Licenses from Mobility Master

Compatible

License heartbeat transport from client to master

IPv4 + IPv6 address

IPv4 + IPv6 address

Yes

IPv6 address

Single Mobility Master and Local Controller in Mixed Network

The CFGM process of the License Manager upgrades the Mobility Master license server from IPv4 to IPv6 address before the Mobility Master license client IP address is upgraded to IPv6 address. The license server can have both IPv4 and IPv6 controller IP addresses while the license client can have IPv4 controller IP address only as shown in the following table:

Table 2: Mobility Master and Local Controller in IPv4 IPv6 matrix

License Server Controller IP

Licenses from Mobility Master

Compatible

License heartbeat transport from client to master

IPv4 address only

IPv4 address only

Yes

IPv4 address

IPv4 + IPv6 address

IPv4 address only

Yes

IPv4 address

 

The License Manager supports IPv6 address only when you configure IPv4 address of the managed device. If no license server IP address is configured, the license client uses either IPv4 or IPv6 address of license server based on master IPv4 or master IPv6 address.

Multiple Mobility Masters in IPv6 network

The centralized licensing feature is now supported for multiple Mobility Masters where a single Mobility Master acts as a license server that is configured with the IPv6 address of the controller. The remaining Mobility Masters act as relay servers that support configuration of IPv6 license server IP addresses pointing to the IPv6 license server as shown in the following table:

Table 3: Multiple Mobility Masters in IPv6 matrix

License Server Controller IP

License Relay Server License Server IP

License Relay Server Controller IP

Compatible

License heartbeat transportfrom license relay server to license server

IPv4 + IPv6 address

IPv6 address only

IPv4 + IPv6 address

Yes

IPv6 address

 

The relay servers and their license client controllers follow single Mobility Master and local IPv6 support network.

Multiple Mobility Masters in Mixed Network

The centralized licensing feature for multiple Mobility Masters in a mixed network is supported in the following scenarios:

When the license server is configured with IPv4 address of controller, the remaining Mobility Masters acting as relay servers can only work with IPv4 license server. However, the relay server itself can have IPv4 or IPv6 controller IP configured.

When the license server is configured with IPv6 address of controller, the remaining Mobility Masters acting as relay servers can work with IPv4 license server; and the relay server itself can have IPv4 or a combination of IPv4 and IPv6 controller IP configured.

The following table describes the scenarios:

Table 4: Multiple Mobility Masters in IPv4 IPv6 matrix

License Server Controller IP

License Relay Server License Server IP

License Relay Server Controller IP

Compatible

License heartbeat transport from license relay server to license server

IPv4 address only

IPv4 address only

IPv4 + IPv6 address

Yes

IPv4 address

IPv4 + IPv6 address

IPv4 address only

IPv4 + IPv6 address

Yes

IPv4 address

The following procedure describes how to associate a Mobility Master or stand-alone controller to an external license server.

1. Before you begin, access the command-line interface Mobility Master and remove any unnecessary license pool profiles.

2. From the Mobility Controller configuration node on a standalone controller, or from the Mobility Master configuration node for a Mobility Master, navigate to Configuration > License page.

3. In the License Management option, select External license server radio button.

The External License Server fields are displayed.

4. Select either IPv4 or IPv6 radio button based on your preference.

5. In the IP address field, enter the IPv4 or IPv6 address of the external license server.

6. Click Submit to save your changes.

To associate a Mobility Master with an external license server, run the no license-pool-profile <profile> command from the Mobility Master (mm) configuration node to remove any local license pools. Then, run the license server-ip<ip-addr>|<ipv6-addr> command to define the external server.

For example:

(host)[mm] (config) #no license-pool-profile /USA/southwest

(host)[mm] (config) #no license-pool-profile /USA/northeast

(host)[mm] (config) #no license-pool-profile /APAC/India

(host)[mm] (config) #no license-pool-profile /USA/Beijing

(host)[mm] (config) #license server-ip 2002::6

To view license usage details for standalone controllers or Mobility Master servers connected to an external licensing pool, run the command.

To associate a standalone controller to an external license server, run the license server-ip<ip-addr>|<ipv6-addr> command to define the external server.

For example:

(host)[mm] (config) #license server-ip 10.1.1.91

/*]]>*/