vThunder Pay-as-you-Go Licensing - Amazon S3

Installation and User Guide

vThunder Pay-as-you-Go Licensing

Document No.: D-050-01-00-0001

Ver. 1.0 1/30/2015

Confidential and Proprietary

© 1/30/2015 A10 Networks, Inc. Confidential - All Rights Reserved

Information in this document is subject to change without notice.

Patents

A10 Network products including all AX Series products are protected by one or more of the following U.S. patents: 8849938, 8826372, 8813180, 8782751, 8782221, 8595819, 8595791, 8595383, 8584199, 8464333, 8423676, 8387128, 8332925, 8312507, 8291487, 8266235, 8151322, 8079077, 7979585, 7804956, 7716378, 7665138, 7647635, 7627672, 7596695, 7577833, 7552126, 7392241, 7236491, 7139267, 6748084, 6658114, 6535516, 6363075, 6324286, 5931914, 5875185, RE44701, 8392563, 8103770, 7831712, 7606912, 7346695, 7287084, 6970933, 6473802, 6374300.

Trademarks

The A10 logo, A10 Lightning, A10 Networks, A10 Thunder, aCloud, ACOS, ACOS Policy Engine, ACOS Synergy, Affinity, aFleX, aFlow, aGalaxy, aVCS, aXAPI, IDaccess, IDsentrie, IP-to-ID, SoftAX, SSL Insight, Thunder, Thunder TPS, UASG, VirtualN, and vThunder are trademarks or registered trademarks of A10 Networks, Inc. All other trademarks are property of their respec-tive owners.

Confidentiality

This document contains confidential materials proprietary to A10 Networks, Inc. This document and information and ideas herein may not be disclosed, copied, reproduced or distributed to anyone outside A10 Networks, Inc. without prior written consent of A10 Networks, Inc.

A10 Networks Inc. Software License and End User Agreement

Software for all A10 Networks products contains trade secrets of A10 Networks and its subsidiaries and Customer agrees to treat Software as confidential information.

Anyone who uses the Software does so only in compliance with the terms of the End User License Agreement (EULA), pro-vided later in this document or available separately. Customer shall not:

1. reverse engineer, reverse compile, reverse de-assemble or otherwise translate the Software by any means

2. sublicense, rent or lease the Software.

Disclaimer

This document does not create any express or implied warranty about A10 Networks or about its products or services, includ-ing but not limited to fitness for a particular use and non-infringement. A10 Networks has made reasonable efforts to verify that the information contained herein is accurate, but A10 Networks assumes no responsibility for its use. All information is provided "as-is." The product specifications and features described in this publication are based on the latest information available; however, specifications are subject to change without notice, and certain features may not be available upon initial product release. Contact A10 Networks for current information regarding its products or services. A10 Networks’ products and services are subject to A10 Networks’ standard terms and conditions.

Environmental Considerations

Some electronic components may possibly contain dangerous substances. For information on specific component types, please contact the manufacturer of that component. Always consult local authorities for regulations regarding proper dis-posal of electronic components in your area.

Further Information

For additional information about A10 products, terms and conditions of delivery, and pricing, contact your nearest A10 Net-works location, which can be found by visiting www.a10networks.com.

http://www.a10networks.com

Customer Driven Innovation 3 of 48Document No.: D-050-01-00-0001 - 1/30/2015

vThunder Pay-as-you-Go Licensing - Installation and User Guide

Contents

vThunder Pay-as-you-Go Licensing Overview 5

Pay-As-You Go Billing with Global License Manager (GLM) 7

Rental Billing Model (RBM) and Utility Billing Model (UBM) .............................................................. 7

Using the Global License Manager (GLM)............................................................................................ 8

Configuring RBM/UBM on the GLM .................................................................................................... 11

Generating Reports for License Pools ............................................................................................... 15

Viewing Logs for License Pools ...................................................................................................... 15

CLI Commands for vThunder Instances 17

vThunder Configuration Commands .................................................................................................. 17

LLP Configuration 27

Local License Proxy (LLP) Configuration .......................................................................................... 27

System Requirements .......................................................................................................................... 27

Installing LLP with VMware ESXi 5.5 .................................................................................................. 28

Using the LLP GUI 37

Managing the LLP/GLM Connection ................................................................................................... 38

Changing the User Credentials ........................................................................................................... 40

Checking for Usage Issues.................................................................................................................. 42

License and Open Source Acknowledgments 45

Acknowledgments for LLP .................................................................................................................. 45

4 of 48 Customer Driven InnovationDocument No.: D-050-01-00-0001 - 1/30/2015


Contents

Customer Driven Innovation 5 of 48 Document No.: D-050-01-00-0001 - Ver. 1.0 1/30/2015


vThunder Pay-as-you-Go Licensing Overview

The A10 Networks™ vThunder Pay-as-you-Go Licensing solution is alicensing orchestration solution that allows you to request licenses for mul-tiple vThunder™ virtual appliances. The vThunder Pay-as-you-Go Licens-ing solution is shown below.

FIGURE 1 vThunder Pay-as-you-Go Licensing Topology

Figure 1 shows the vThunder Pay-as-you-Go Licensing solution and itsmajor components:

• Global License Manager (GLM) – The GLM is the master licensing and billing system for the vThunder Pay-as-you-Go Licensing solution. The GLM is managed by A10 Networks and is the primary portal for cus-tomers to view billing plans and data usage for their aCloud environ-ment. The GLM collects information from the distributed LLP servers and issues licenses for the vThunder instances upon request. The GLM provides a web portal to verify admin login credentials and manage all functions of the GLM for billing, data usage, and license pool creation.

• Local License Proxy (LLP) – The LLP is a software-based proxy that is installed and running in the cloud at the customer premises. It sits in the datacenter between the vThunder virtual appliances and the Global

6 of 48 Customer Driven InnovationDocument No.: D-050-01-00-0001 - Ver. 1.0 1/30/2015


Licensing Manager (GLM), with the Internet between them. The LLP sits between the two entities, gathering usage statistics from the vThun-der virtual appliances, performing metering operations, and monitoring for a constant connection with the GLM (with whom it shares all col-lected data).

LLP is an optional component for setting up an aCloud environment, but is strongly encouraged for streamlining effectiveness of communication between multiple vThunder appliances and the GLM.

• vThunder – The vThunder is a virtualized, software-only version of an SLB appliance or an IPv6 Migration device. The vThunder instances support most of the same features as standard hardware-based ACOS devices, but the set of supported features may vary based on whether vThunder is running an SLB release or an IPv6 Migration release. Note: You can download the latest vThunder image from http://www.a10networks.com/support/index.php, under the Software section of the page. You must enter your support account credentials prior to downloading the file.

Customer Driven Innovation 7 of 48Document No.: D-050-01-00-0001 - Ver. 1.0 1/30/2015


Rental Billing Model (RBM) and Utility Billing Model (UBM)

Pay-As-You Go Billing with Global License Manager (GLM)

The A10 Networks vThunder Pay-as-you-Go Licensing solution offers thefollowing two billing models: the Rental Billing Model (RBM) and the Util-ity Billing Model (UBM).

The user can configure each of these within the Global License Manager(GLM) by provisioning license pools with the specified billing model.License pools are created within the Global License Manager, which alsoallow provide users the ability to view billing plans and usage reports. Notethat most functions of aCloud pertaining to usage and reporting, billing andappliance information will be present in the GLM.

• “Rental Billing Model (RBM) and Utility Billing Model (UBM)” on page 7

• “Using the Global License Manager (GLM)” on page 8

• “Configuring RBM/UBM on the GLM” on page 11

• “Generating Reports for License Pools” on page 15

Rental Billing Model (RBM) and Utility Billing Model(UBM)

The Rental Billing Model (RBM) is designed for cloud service providers(CSPs) who offer Advanced Delivery Controller (ADC) services. Thismodel enables such providers to bill their customers for a fixed amount ofbandwidth, as well as adding surcharges for extra bandwidth consumed.

RBM provides the following features:

• Flexibility to configure bandwidth in multiple tiers.

• Support for overage usage in bytes.

• Ability to charge for provisioned bandwidth and overage.

• Capability to generate a monthly bill.

• Ability to gather hourly, daily, and monthly usage information to be able to generate reports.

• Cost predictability. RBM offers fixed pricing for plans with an optional overage rate for traffic that exceeds the plan.



Using the Global License Manager (GLM)

• Hard limits: RBM offers the ability to configure bandwidth maxi-mums, such that traffic beyond the allowable limit is not forwarded.

• Ability to configure for burst traffic. Knowing traffic patterns and being able to identify when the traffic is at its peak allows you to configure an overage limit designed for peak-time data usage.

• Ability to configure the bandwidth that will be allocated to each vThunder instance.

The Utility Billing Model (UBM) is based on actual data usage, in bytes, inwhich unlimited vThunder instances can be deployed and in which no band-width settings are required. Licensing acquisition and reporting is through aglobal or local license manager (GLM/LLP). UBM provides the followingkey features:

• It eliminates the need to configure bandwidth settings.

• Cost of services is based on actual data usage (Gigabytes).

• Can deploy an unlimited number of vThunder instances.

• Bills for data usage can be generated on a monthly basis.

• Granular usage information is reported to the GLM on an hourly, daily, or monthly basis.

• With UBM, there is no predetermined limit on the number of vThunder instances that are deployed, which means the amount of traffic can be highly variable, as well as the associated costs. While this billing model might be suitable for customers with variable traf-fic flows, the RBM approach might be better for customers who wish to impose granular limits on the amount of data used.


To access the GLM home screen (with administrative privileges):

1. Launch a browser and navigate to the GLM at https://glm.a10net-works.com.

2. Log in with username and password or register a new account.

3. Upon logging in, the aCloud GLM homepage appears, showing number of license pools created, appliances and LLPs assigned, users, and the amount of data usage on the account for the last 30 days. The feed towards the right will display a running log of all activity for instances registered on the GLM.

Note: To return to the homepage at any time, click on the A10 Networks logo onthe top left-hand corner.




FIGURE 2 aCloud GLM Homepage

Tabs to other pages appear on the top task pane along with the gravatar on the far right, which provides a drop down menu for editing the Pro-file, Billing Info, and Account Info for the GLM. Additionally, to logout of the GLM, the user will have to access the gravatar menu.

The following options are available to the user in the tabs:

• Users – Edit existing users or add additional users to the GLM account. Primary admins can add additional users to the GLM account. For an individual profile, users can change their login pass-word, company name, or email address.




FIGURE 3 Editing User Settings in GLM

• License Pools-- The most critical feature of GLM, allows for cre-ation of license pools to set UBM or RBM billing for any given number of vThunder instances. Allows for usage tracking and reporting. In this tab, users are able to:

• Create new license pools (user can set preferred billing model upon creation of license pools for any desired number of instances) and view reports on data usage and individual license pool settings. See “Configuring RBM/UBM on the GLM” on page 11 and “Generating Reports for License Pools” on page 15 for more information.

• Upload LLP usage files. This can be downloaded via the Usage tab in the LLP GUI.

• Download licenses in JSON format for additional viewing.



Configuring RBM/UBM on the GLM

FIGURE 4 Viewing License Pools and Data Usage

• LLPs-- View information regarding any Local License Proxies (LLPs) assigned to the GLM for tracking individual vThunder instances. Note that this tab will only show if an LLP account is associated with the GLM, as LLPs are an optional part of the aCloud setup. For more information on associating LLPs with a GLM account, See “Managing the LLP/GLM Connection” on page 38

• Appliances-- View data for appliances using GLM.

• Activity-- View a more detailed log of errors incurred or other details regarding internal activity of instances on the GLM.

• Audit Trail--View user activity on the GLM or any other changes made by users and admin to GLM account settings and billing infor-mation.


The primary mechanism by which cloud service providers can reserve ablock of vThunder licenses, choose a desired billing model, and view usageis through creation of license pools in the GLM. Each of these license poolsis given a serial number in the GLM. When creating the license pool, theuser can specify their preferred billing model and any number of instancesfor that model.




To configure RBM/UBM through the GLM:

1. Navigate to License Pools in the GLM.

2. Select “Add License Pool.” The following form should show on the screen:

FIGURE 5 Creating a License Pool in GLM

3. Specify a name for the license pool under “Name” and select the desired billing model from the drop down menu under “Product.” The first option shown is UBM (Uncapped usage per GB), and the subsequent choices show various billing rates for RBM.

4. Optional: Specify instances desired under “Number of Instances.” Default setting is unlimited.

5. Click “Create License Pool” to confirm.

6. The user should receive a confirmation message towards the top of the page stating “License Pool was successfully created.” The page should display the license pool name, assigned serial number, billing plan




selected, and the CLI configuration to register the license pool with the vThunder appliance.

FIGURE 6 Accessing the CLI Configuration for License Pool

7. Copy and paste the configuration displayed onto the CLI for the vThun-der appliance. Below is a sample configuration for a given license pool:

license-manager host 54.201.247.34 port 443 use-mgmt-port

license-manager sn SN50B962F9850F1C3-BA8E6E1DD791048

license-manager interval 3

license-manager instance_name test_license-pool_5926

license-manager bandwidth_base 10

license-manager connect

Text shown in italics on the GLM page may need to be customized for individual network configurations. For users running ACOS 4.0, the syntax for the license manager configuration will be the following:

license-manager host 54.201.247.34 port 443

license-manager use-mgmt-port

license-manager sn SN80558BC20BB3445AE9C29E65F225BD

license-manager interval 3




license-manager instance-name licence_manage-ment_dev_8956

license-manager bandwidth-base 200

Note: When configuring license-manager host, the user can either entertheir own LLP IP address (retrieved from the LLP installation setup forcustomer’s virtual environment. for more information, see chapter on LLPinstallation) or leave the default IP shown on the page to communicatewith GLM directly. license-manager host host-ip-address {port port-num | use-management-port}

8. Applicable to RBM only: To configure overage intervals, the user will have to enter the following into the CLI (this currently cannot be done via the GLM):

license-manager overage interval {days num | hours num | minutes num | seconds num} data {bytes num | gb num | kb num | mb num}

Note: If you do not configure an overage amount, any trafficbeyond the configured RBM bandwidth will be dropped.

The following command sets the overage limit to 2 GB within a 1 dayperiod:

license-manager overage interval days 1 data gb 2

Similarly, you can configure an overage amount for different time intervals,such as configuring an extra 1 GB per minute or 10 GB per hour.

Note: For a detailed explanation of the CLI commands that can be used to con-figure vThunder Pay-as-you-Go Licensing, please see “CLI Commandsfor vThunder Instances” on page 17.



Generating Reports for License Pools


The GLM allows you to generate usage reports for all vThunder instances inall license pools.

Viewing Logs for License Pools

To view license pool logs, do the following:

1. Click on the License Pools tab in the GLM. A graph depicting usage information for the past 30 days will show, along with a table listing individual license pool data.

FIGURE 7 License Pool Report and Table

2. To change settings for an individual license pool such as billing plan and number of instances, navigate to the row of the license pool and click on the “Settings” icon in the lower right-hand corner.

FIGURE 8 Editing License Pool Settings

Click on Sprocket Icon to Edit Settings




3. To view information for an individual license pool, click on the license pool name in the table below the graph. You will be redirected to a page similar to this:

FIGURE 9 Individual License Pool Information

The page will show information regarding the license pool serial number,selected billing plan, number of appliances assigned to the license pool andspecific information on virtual appliance data usage in the last 30 days (forusage info on an individual instance, please see “Checking for UsageIssues” on page 42 in the LLP GUI). It will also display the configurationrequired for CLI setup of the license manager on the vThunder deviceshould the user need to refer to this.



vThunder Configuration Commands

CLI Commands for vThunder Instances

The commands in this chapter configure global settings for vThunderinstances.

vThunder Configuration CommandsThis section describes the license manager configuration commands.

license-manager bandwidth_base

Description Using the Rental Billing Model (RBM), indicate the desired bandwidth in increments of 1 Mbps. This billing model enables cloud service providers (CSPs) to offer their customers fixed pricing for a fixed amount of band-width. The command also offers the CSPs the ability to configure usage maximums, such that traffic beyond this limit is dropped.

Using the Unlimited Billing Model (UBM), use this command to set the bandwidth to provide data access with a byte-count limit. This billing model is suitable for customers with variable traffic flows. Billing is based on actual data usage, in bytes, in which unlimited vThunder instances can be deployed. The bandwidth settings you indicate with this command will pro-vide a finite byte-count limit.

license-manager bandwidth_base bandwidth-in-Megabytes

For users running ACOS 4.0:license-manager bandwidth-base bandwidth-in-Megabytes

Parameter Description

bandwidth-in-Megabytes Indicate the desired bandwidth in Mbps. The

supported range is 10-102400 Megabytes.

Default None

Mode Configuration

Usage None




Example The following command sets the bandwidth to 1000 Megabytes:

vTh(config)# license-manager bandwidth_base 1000Request bandwidth base: 1000

license-manager bandwidth_unrestricted

Description Enable the Unlimited Billing Model (UBM) and set the bandwidth to pro-vide unlimited data access. This billing model is suitable for customers with variable traffic flows. Billing is based on actual data usage, in bytes, in which unlimited vThunder instances can be deployed and no bandwidth set-tings are required. Cost for services is based on actual data usage (byte count). You may deploy unlimited vThunder instances when you deploy UBM.

Syntax license-manager bandwidth_unrestricted

Default None

Mode Configuration

Usage With UBM, there is no set upper limit on how many vThunder instances aredeployed or how many bytes of traffic are used. The cost for the servicesprovided under UBM can be volatile and unpredictable. Therefore, if youwant less volatility and more predictability, consider deploying the RBMbilling model, which allows you to impose caps on the data usage.

Example The following example sets the bandwidth to unlimited, thereby indicating that the customer will be billed for every byte used. In this case, it does not show that overages are configured:

vTh(config)# license-manager bandwidth_unrestricted

license-manager connect

Description This command helps you connect to the license manager and helps you acti-vate your vThunder configuration.

Syntax license-manager connect

Default None

Mode Configuration

Usage None




Example Activate your vThunder configuration using the following command

vThunder-03(config)(NOLICENSE)#license-manager connect

license-manager host

Description Use this command to configure a connection from the vThunder instance to the LLP license manager host.

license-manager host host-ip-address {port port-num | use-management-port}

For users running ACOS 4.0:

license-manager host host-ip-address {port port-num}


host-ip-address Enter a host name or the IPv4 or IPv6 address of

the host. The supported formats are a hostname(of 1-31 characters), and IPv4 address (using theA.B.C.D format), or and IPv6 address (using theA:B:C:D:E:F:G:H format).

port-num Enter the number of the port that will be used bythe license manager host for communication withthe vThunder. Available ports range from 1-65535

use-management-port Indicates that the management port will be used

for communication between the vThunder andthe LLP host.

Note: For users running ACOS 4.0, management ports will have to be enabledin a separate command after defining the license manager host and portnumber. The configuration and command syntax is shown below:

license-manager host 54.201.247.34 port 443 license-manager use-mgmt-port




Default Port 443 is the default port that will be used if you do not specify a port.

Mode Configuration

Usage None

Example The following command specifies the LLP host IP address to be 192.168.208.131 and the desired port to be port 786:

vTh(config)# license-manager host 192.168.208.131 port 786

The following command sets the LLP host called testhost to use the man-agement port for communications:

vTh(config)# license-manager host testhost use-mgmt-port




license-manager instance_name

Description Configure the name of the vThunder instance that will be used during com-munications with the GLM and the LLP.

license-manager instance_name instance-name

For users running ACOS 4.0:license-manager instance-name instance-name


instance-name Indicate the unique name of the vThunderinstance. The range for this name is 1-63 charac-ters or a string.

Default None

Mode Configuration

Usage None

Example The following command helps a particular vThunder instance register with the GLM:

vTh(config)# license-manager instance_name 192.168.208.209Instance name: 192.168.208.209

license-manager interval

Description Configure the time interval profile using the following command. The inter-val refers to the frequency with which vThunder sends usage data to the LLP.

Syntax license-manager interval {1 | 2 | 3}


1 Sets a monthly interval.

2 Sets a daily interval.

3 Sets an hourly interval.

Default None

Mode Configuration




Usage None

Example The following command sets the interval profile to option 3, which means vThunder will send usage data to the LLP at an hourly interval:

vTh(config)# license-manager interval 3

license-manager overage

Description Configure an overage duration and number of bytes using this command. Overages can be configured as part of the Rental Billing Model (RBM). This enables providers to bill their customers for a fixed amount of band-width, as well as allowing them to add extra surcharges if their customers consume additional bandwidth above and beyond the fixed limit.

Note: If you do not configure an overage amount, any traffic beyond the config-ured RBM bandwidth will be dropped.

Syntax license-manager overage interval {days num | hours num | minutes num | seconds num} data {bytes num | gb num | kb num | mb num}


num Specify the overage interval in days, hours, min-utes, or seconds, and specify the data usage inbytes, gigabytes, kilobytes, or megabytes.

Default None

Mode Configuration

Usage None

Example The following command sets the overage limit to 2 GB within a 1 day period:

vTh(config)# license-manager overage interval days 1 data gb 2

Similarly, you can configure an overage amount for different time intervals,such as configuring an extra 1 GB per minute or 10 GB per hour.




license-manager reminder

Description Configure a reminder (an SNMP message sent by the ACOS device), which will alert you to the number of hours that remains before the grace period for this device will expire. The grace period is the amount of time that the vThunder instance will continue to pass traffic after a loss of connectivity or after the license has expired. You can set multiple reminders by issuing this command multiple times, and up to 10 reminders can be set.

Syntax license-manager reminder hours


hours Set the number of hours from 1–720.

Default None

Mode Configuration

Usage None

Example The following command sets the reminder to 2 hours before the grace time is reached:

vTh(config)# license-manager reminder 2

license-manager sn

Description Use this command to indicate the license pool serial number. Configure the serial number on each vThunder instance that is part of the same license pool. For RBM users, each license pool can have as many vThunder instances as were reserved as members of the license pool from the GLM. For UBM users, specify the license pool serial number on unlimited vThun-der instances if you want them to belong to the same license pool for billing purposes.

If indicating a UBM license pool, you also have a choice to either enter the actual serial number that is generated by the GLM.

Note: The LLP configuration allows you to import the UBM license pool serialnumbers from the GLM. This capability alleviates you from having toenter the UBM license pool serial number on each vThunder instancewithin that pool. The license pool serial number is different from the“License account serial number.” The latter is auto-generated by the GLMwhen you create an account on the GLM.




Syntax license-manager sn serial-num


serial-num RBM and UBM users, on the vThunder, enter thelicense pool serial number that you wereassigned.

Default None

Mode Configuration

Usage None

Example The following command indicates the RBM or UBM license pool serial number on the vThunder:

vTh(config)#license-manager sn SN00013FA0849AD80AA31C3BC4A2DB7DLicense manager serial number: SN00013FA0849AD80AA31C3BC4A2DB7D

show license-manager

Description Displays configured licensing information.

Syntax show license-manager

Default None

Mode All

Table 1 describes the fields in this command’s output.

TABLE 1 show license-manager fields

Field Description

License manager server Indicates the name or IP address of the LLP license manager host.




Example The following example displays the configured license manager informa-tion on the vThunder:

vTh(config)#show license-managerLicense manager server: testhost 443license pool serial number: SN00013FA0849AD80AA31C3BC4A2DB7DLicense account serial number:License bandwidth base 1000 MbInterval: 3Instance name: 192.168.208.209Feature request: bandwidth base 10 MbRemind before grace time is reached 2 hours

license pool serial number

Indicates the serial number assigned to either the RBM or UBM license pool. All members of the license pool must have the same license pool number to be counted as members of the license pool. The number of instances must match the number of requested RBM instances as part of the license pool.

License account serial number

The serial number is auto-generated by the GLM when you create an account on the GLM.

License bandwidth base Indicate the desired RBM bandwidth.

Interval The interval refers to the frequency with which vThunder sends usage data to the LLP. It should show the following: (1–monthly, 2–daily, 3–hourly)

Instance name Indicates the name that is associated with a particular vThunder instance serial number.

Feature request Indicates whether you have chosen to enable the RBM or UBM billing model.

Remind before grace time is reached

Displays the reminder (number of hours) before the vThunder grace period expires.

TABLE 1 show license-manager fields (Continued)

Field Description






Local License Proxy (LLP) Configuration

LLP Configuration

This chapter discusses how to configure the Local License Proxy (LLP).LLP resides in the customer’s datacenter and sits between the vThunderinstances and the GLM. The LLP’s main responsibility is to gather usagestatistics from the vThunder virtual appliances and to pass this informationto the GLM.

Local License Proxy (LLP) Configuration

The following sections describe how to configure the Local License Proxy(LLP) software image. Upon completing the configuration, you will beready to access the GLM and can begin requesting licenses for each of yourvThunder virtual appliances. The LLP configuration is done via the aCloudWeb UI and at the API level.

The procedure below focuses on installing LLP on VMware’s vSpherehypervisor. However, LLP can also be installed on RedHat KVM. Addition-ally, LLP can be integrated with OpenStack for cloud management.

Please consult your hypervisor provider for guest OS install instructions.

System Requirements

LLP is sold as a software-based OVA file via the A10 Networks website.The LLP OVA file can be obtained by downloading from the link providedin this document.

LLP is a virtual machine running on Ubuntu, and the software must beinstalled on a third-party server or hypervisor. The server (or hypervisor)must be dedicated, meaning that no other operating system or applicationcan be running on the server where the LLP is installed.

The virtual machine where the LLP software will be installed must meet thefollowing requirements:

• 4 GB virtual memory (8GB recommended if many vThunder instances)

• 20 GB virtual disk space

• 2 virtual CPUs (capable of supporting Intel VT technology)



Installing LLP with VMware ESXi 5.5

• Reserved resources: 4GHz CPU and 4GB memory

• When installing on a VMware server, the hardware platform must be running ESXi 5.5 or higher.

To obtain VMware ESXi 5.5 or higher, navigate to the following site on the VMware partner portal: http://www.vmware.com

Firewall Requirements

vThunder uses Secure Socket Layer (SSL) and Transport Layer Security(TLS) to communicate with LLP. The firewall must be configured to allowSSL/TLS connections. (This is true of any other devices through which theLLP/GLM traffic will pass.)

In vThunder Pay-as-you-Go Licensing deployments, connections arealways established from the network elements at the bottom of the topologyto those at the top. (See Figure 1 on page 5 for an vThunder Pay-as-you-GoLicensing diagram.) Therefore, it is recommended that TCP port 443 bekept open on devices through which the bi-directional SSL traffic will pass.

Connections between vThunder Pay-as-you-Go Licensing modules are ini-tiated from the lower-level modules to those above, so connections areestablished from the vThunder to the LLP, or from the LLP to the GLM.

The firewall can be configured to block connection requests coming fromthe wrong direction, such as a connection request sent to the LLP that origi-nates from the public Internet. Controlling the flow of information in thismanner enhances the security of the vThunder Pay-as-you-Go Licensingsolution.

The LLP will need to be able to reach the GLM on outbound port 443. Thisis necessary to ensure that LLP can retrieve licenses configured on the GLMand push usage and account information.


Note: Screen captures below show the installation procedure using VMware’sESXi 5.5 vSphere client on a Windows-based system, although this sameprocedure could also be performed on a Linux system with only minorvariations.

1. To begin, verify that the virtual disk drive has at least 20 GB of free storage.

2. Download the LLP OVA file from http://glm.a10networks.com/local_license_proxies/setup.

http://www.vmware.com

http://glm.a10networks.com/local_license_proxies/setup

http://glm.a10networks.com/local_license_proxies/setup




FIGURE 10 Setting Up LLP in GLM

3. Save the OVA file to a secure location.

4. Launch the vSphere client and log into the IP of the ESXi server with the appropriate admin credentials.

5. Select File > Deploy OVF Template. This will open a wizard in which the user will have to upload the LLP OVA file. Click Browse to locate the file and then click Next.

FIGURE 11 Deploying the OVF Template and Uploading LLP

Open the wizard to deploy OVF template




Upload the LLP OVA file




6. Confirm the OVF template details and then click Next.

FIGURE 12 OVF Template Details

7. Specify a desired name for the aCloud LLP and then click Next.

FIGURE 13 Naming the OVF Template

Specify aCloud LLP Name




8. Set the disk format to Thin Provision, and then click Next.

FIGURE 14 Setting the Disk Format




9. Complete the wizard by clicking Finish and wait for the OVF template to be loaded onto the VM.

10. Power on the VM by clicking on the OVF template name under the IP address of the ESXi server in the left-hand directory of vSphere Client. Select Power On Virtual Machine.

FIGURE 15 Powering On the Virtual Machine

11. Access the Console tab to log into the VM. The user will have to enter the LLP credentials in order to execute commands. The default login name and password is “a10” for both fields.

Note: Should the user need to change the password, enter change_passwordinto the console and specify a new password.

aCloud LLP Name




FIGURE 16 Logging into the VM via the Console

12. To change the hostname for the LLP, type change_hostname and enter a desired hostname.

Note: Names must be all text to be valid.




13. Enter ifconfig to access the IP address of the LLP. This will be needed to log into the LLP and associate it with the GLM (see “Man-aging the LLP/GLM Connection” on page 38).

FIGURE 17 Accessing the IP Address of the LLP

If the user doesn’t have DHCP setup and needs to perform a manual config-uration for the LLP IP address, follow the steps below:

1. Enter setup_interfaces into the console to begin setup of the LLP IP address.

2. Select either a loopback or ethernet interface by choosing “0” for loop-back or “1” for ethernet.

3. Specify whether the interface will run IPv4 or IPv6 by selecting “1” or “2.”

4. Select “Static” as the IP address method.

5. Enter the desired IP address, subnet mask, and default gateway.

6. The interface should be created and the LLP will now use the designated IP address. To confirm, type list_interfaces to check if the IP address is shown.






Using the LLP GUI

This chapter discusses how to use the Local License Proxy (LLP) GUI toperform basic tasks, such as creating an LLP user account, configuring theconnection between the LLP and GLM, and customizing user credentials.Note that prior setup of the LLP IP address is required to carry out tasks inthis chapter. For more information, see “Installing LLP with VMware ESXi5.5” on page 28.

For more information on tasks that can be performed using the LLP GUIinterface, access the following pages:

• “Managing the LLP/GLM Connection” on page 38

• “Changing the User Credentials” on page 40

• “Checking for Usage Issues” on page 42



Managing the LLP/GLM Connection

Managing the LLP/GLM Connection The following steps show how to setup and verify that LLP has connectedto GLM. Note that prior setup of a GLM account and the LLP IP address isrequired for this process. See “Using the Global License Manager (GLM)”on page 8 and “Installing LLP with VMware ESXi 5.5” on page 28.

1. Access the LLP by entering the management IP in the browser window. The first page will display a form to Associate Local License Proxy. In the form, the user will have to create an LLP Name for the account, username and password. The Account ID and Key will be accessed from the GLM.

FIGURE 18 Associating the Local License Proxy

2. In the GLM, click on the gravatar in the right-hand corner of the task pane and select Account Info from the drop down menu. This will



Managing the LLP/GLM Connection

allow access to the Account ID and Account Key required to complete the Associate LLP Setup Form.

FIGURE 19 Accessing Account Info in GLM

Account ID

Account Key



Changing the User Credentials

3. In the LLP, copy and paste the Account ID and Key shown in the GLM into the form. This will connect the GLM server to LLP.

4. To finish, click “Associate LLP.”

5. If the LLP has connected successfully, the user will see a new tab in the GLM titled LLPs. To verify, click on this tab to check if the LLP name shows in the table titled “Local License Proxies.”

FIGURE 20 Verifying Connection of GLM to LLP


If desired, the following illustrates how to change the username, email, andpassword:

1. In the GLM, click on the gravatar in the right-hand corner of the task pane and select “Profile” from the drop down menu. The user should see the following window:

LLP Name

New tab for LLP appears




FIGURE 21 Profile Page for User

2. Should the user want to change the username or email for the account, select “Settings” on the left-hand task pane to edit either one of these fields. Click “Update User” to confirm.

FIGURE 22 Editing the Username and Email in GLM



Checking for Usage Issues

3. Should the user want to change the password, on the left-hand task pane, select “Password” to edit the password and type in the new desired pass-word in the form shown. Click “Change Password” to confirm.

FIGURE 23 Editing the Password in GLM

Checking for Usage IssuesThere are various tools available to the user to check for data usage andissues on the LLP.

1. To check for usage of individual ports on a given vThunder instance, log into the LLP GUI and navigate to Usage.




2. The page will display a usage period under “Pending Usage” with two options to view or download the usage data. Click “View” to pull up a usage report.

3. The GUI will display a report table with various details of the vThunder instance and usage data. This includes the instance ID, bandwidth base, MAC address, data usage (in bytes), and any overage incurred.

FIGURE 24 Usage Report in the LLP GUI






Acknowledgments for LLP

License and Open Source Acknowledgments

A10 Networks Inc. acknowledgment of open source GPL and other opensource licensing based on program entity, file entity, user entity, and anyother types and variations of licensing whatsoever, either explicitly orimplicitly implied in the following acknowledgment list.


Open Source Tools:

• Ubuntu/Debian

• Python

• openssl

• swig

• nginx

• pip

• virtualenv

• git

• PostreSQL

Python Packages:

• django, requests, djangorestframework, markdown,

• django-filter, gunicorn,

• south, M2Crypto, django-twitter-bootstrap,

• django-jquery, usethis-django-bootstrap,

• dj-database-url, pyyaml, psycopg2, tornado,

• netiface






OBTAINING TECHNICAL ASSISTANCE

For all customers, partners, resellers, and distributors who hold valid A10Networks Regular and Technical Support service contracts, the A10 Net-works Technical Assistance Center provides support services online andover the phone.

A10 VIRTUAL APPLICATION DELIVERY COMMUNITY

You can use your A10 support login to access the A10 Virtual ApplicationDelivery Community (VirtualADC™). The VirtualADC is an interactiveforum where you can find detailed information from product specialists.You also can ask questions and leave comments. To access the VirtualADC,navigate here:

http://www.a10support.com/adc/

http://www.a10support.com/adc/

48

Customer Driven Innovation

Corporate Headquarters

A10 Networks, Inc.3 W Plumeria Dr.San Jose, CA 95134 USA

Tel: +1-408-325-8668 (main) Tel: +1-888-822-7210 (support – toll-free in USA)Tel: +1-408-325-8676 (support – direct dial)Fax: +1-408-325-8666

www.a10networks.com

© 2015 A10 Networks Corporation. All rights reserved.

http://www.a10networks.com

Documents

vThunder Pay-as-you-Go Licensing - Amazon S3