Prerequisites
You administer all Traffic Manager variants through a Web-enabled user interface known as the Admin UI. The Traffic Manager supports the following browsers for this purpose:
•Internet Explorer: v.11 or newer
•Microsoft Edge: latest version
•Mozilla Firefox: latest version
•Apple Safari: latest version
•Google Chrome: latest version
Ivanti does not warrant the use of browser versions older than those listed here due to potential discontinuation of security updates by the vendor.
ATTENTION
If you are installing the Traffic Manager software on an preexisting Linux or UNIX virtual machine, make sure your virtual machine firewall rules allow access to the Traffic Manager Admin UI on TCP port 9090. If you also require access to the Traffic Manager REST API, enable access to TCP port 9070.
Ivanti recommends using one or more test servers (for example, Web servers) to which you can direct traffic.
Additional Prerequisites for Amazon EC2
The Traffic Manager is available on EC2 as a software-only package (for use with existing Linux and UNIX virtual machines) or as a fully packaged Amazon Machine Image (AMI), from which you can create virtual machine instances. To install the software variant, see Installing the Traffic Manager Software on EC2 or GCE. To create instances from the Traffic Manager AMI, see Creating a Traffic Manager Instance on Amazon EC2
To use either variant of the Traffic Manager on EC2, you need the following items:
•An Amazon Web Services (AWS) user account.
•A subscription to the EC2 version of the Traffic Manager software you want to use, or a valid Traffic Manager software license.
•Management tools that allow you to create and delete EC2 instances, such as Amazon's EC2 command line tools, Amazon's AWS management console, or the ElasticFox Firefox extension.
To install the Traffic Manager software on an existing EC2 Linux or UNIX virtual machine, you must ensure that the target machine includes the “netcat” package. Standard Amazon Linux and Ubuntu virtual machines typically include netcat by default, although others might not. Consult your vendor specifications or support provider for more information.
For more information on setting up an AWS account, including EC2 subscriptions, see the Ivanti Community Web site (https://community.pulsesecure.net).
Amazon’s EC2 command line tools are available in a standard software package (ec2-api-tools) on most common Linux variants. You can also download the software package from the Amazon Web Services Developer Tools website (http://aws.amazon.com/developertools). The commands described in this guide are based on API version 2011-02-28.
Additional Prerequisites for Microsoft Azure
To use the Traffic Manager with Microsoft Azure, you need the following items:
•A Microsoft Azure user account.
•Access to the Microsoft Azure Web management portal.
•A subscription for an applicable Traffic Manager image, or a valid license for use with non-subscription unlicensed Traffic Manager images.
•If you intend to use command line tools to manage your Azure deployment, Ivanti recommends you install the Azure Command Line Interface (CLI) Tool package (for OSX and Linux), or Windows Azure PowerShell (for Microsoft Windows). To install and use the Azure CLI Tool, see the documentation on the Microsoft Azure website: http://azure.microsoft.com/en-us/documentation/articles/command-line-tools/.
Additional Prerequisites for GCE
The Traffic Manager is available on GCE as a software-only package (for use with existing Linux and UNIX virtual machines) or as a fully packaged virtual machine image, from which you can create virtual machine instances. To install the software variant, see Installing the Traffic Manager Software on EC2 or GCE To create instances from the virtual machine image, see Creating a Traffic Manager Instance on Google Compute Engine
When installing the Traffic Manager software on an existing Linux or UNIX virtual machine, you must first ensure your host virtual machine has Read/Write permission set for “Compute” API access. The Traffic Manager requires this access to interact with the gcloud compute API.
To use either variant of the Traffic Manager on GCE, you need the following items:
•A GCE user account and subscription.
•A subscription to the GCE version of the Traffic Manager software you want to use.
•Access to the GCE Web management portal.
•A suitable GCE project in which to launch your GCE-based Traffic Manager instances.
The Traffic Manager supports the use of GCE External IP addresses to implement front-end fault tolerance within your Traffic Manager cluster. To use External IP addresses for fault tolerance on a Traffic Manager, add extra network interfaces (one per IP address) to the host virtual machine at launch time and configure a Traffic IP Group to handle the traffic distribution.
All Traffic Managers require a single network interface reserved for administration and management, so any further interfaces you add must be in addition to the primary interface.
GCE supports a maximum of 8 network interfaces per virtual machine. Consequently, the Traffic Manager can support a maximum of 7 External IP addresses per instance. GCE also requires that virtual machines must be specified with 1 CPU core per network interface, including the primary management address. Therefore, to use fault tolerance on a Traffic Manager deployment in GCE, make sure you perform the following actions before launching your virtual machines:
•Create as many GCE External IP addresses in the GCE console as required for your fault tolerant service (up to a maximum of 7).
•For every new Traffic Manager virtual machine you are creating (or host virtual machine, in the case of Traffic Manager software variants), add an additional network interface and CPU core for each External IP address you want to use. Make sure that the total number of interfaces attached to a virtual machine, and the total number of CPU cores, is at least equal to the number of External IP addresses you want to use plus one more for management.
ATTENTION
You must create additional network interfaces at launch time. GCE does not allow you to add further interfaces to an existing instance.
To learn more about fault tolerance on GCE, see Traffic IP Groups and Fault Tolerance on GCE.