|Oracle® Traffic Director Installation Guide
11g Release 1 (22.214.171.124.0)
Part Number E21034-04
|PDF · Mobi · ePub|
The setup that is discussed in this chapter is ideal when you are looking for application-level traffic management capabilities to monitor and shape the traffic within Exalogic. In order to achieve this, two compute nodes are allocated, wherein incoming traffic is appropriately screened and routed to one of the back-end application servers. In this scenario, Oracle Traffic Director (web tier) is typically hosted on two compute nodes and the application tier is located on other compute nodes. The web tier and application tier traffic here are isolated both at the physical level as well as the network level.
On Exalogic (Solaris), Oracle Traffic Director can be configured for high availability only when installed on a global zone. In addition, all administration nodes must be running on the global zone.
This chapter contains the following sections:
In an Exalogic environment, all compute nodes are connected to a shared storage array (ZFS storage appliance) through the InfiniBand fabric. The shared storage array is used to install and configure all applications, and it is mounted locally within each of these compute nodes through Network File System (NFS).
Before installing Oracle Traffic Director on Exalogic, you must first create new projects and shares, and then mount these shares locally.
For an Oracle Traffic Director installation, it is recommended that the share hosting Oracle Traffic Director is unique to the compute node. For example, if Oracle Traffic Director is installed on two compute nodes for high availability, then the following installation layout is recommended:
Create a share named
primary within the storage array and mount this share locally within one compute node.
Create a share named
secondary within the storage array and mount this share locally within another compute node.
If you wish to configure Oracle Traffic Director for high availability, the administration server and administration node must have
root access within the instance root directory. Similarly, the ZFS share location needs to be configured appropriately so that a
root user can read and write to this share location. This can be accomplished by enabling
root access as NFS exception within the ZFS console.
Perform the following steps for creating and mounting shares with
It is recommended that you install Oracle Traffic Director on each node. This is to ensure that there is no application downtime while patching Oracle Traffic Director.
Create a new project and create new shares within it, or create new shares within an existing project. For information about creating projects and shares, see the following sections in the "Configuring the Sun ZFS Storage 7320 Appliance" chapter of the Oracle Exalogic Elastic Cloud Machine Owner's Guide, http://docs.oracle.com/cd/E18476_01/doc.220/e18478/storage.htm :
Creating Custom Projects
Creating Custom Shares
Log in to the ZFS storage appliance.
Ensure that the shares that you just created are configured to allow
root access on the compute nodes that will host Oracle Traffic Director. This can be done by:
Using the ZFS shared storage administration console:
In the NFS Exceptions section in the ZFS shared storage administration console, ensure that the share hosting Oracle Traffic Director configuration has appropriate NFS exceptions to allow
In addition, in the Properties section in the Project Settings page, deselect the following options
Update access time on read
Restrict ownership change
For more information about using these options, see the following guides:
Oracle Exalogic Elastic Cloud Machine Owner's Guide
Oracle Exalogic Elastic Cloud Administrator's Guide
Using the CLI:
Run the following command:
For an Exalogic physical configuration,
ip-address-2 would be the
BOND0 IP addresses of the compute nodes.
For an Exalogic virtual configuration,
ip-address-2 would be the IP addresses of the vServers on the
BOND1 refer to the default interfaces for IP over InfiniBand (IPoIB) and Ethernet over InfiniBand (EoIB), respectively, on the Oracle Linux operating system.
Oracle Solaris uses the IP Multipathing (IPMP) technology to support IPMP Groups that consist of one or more physical interfaces on the same system that are configured with the same IPMP group name. This technology provides the same functionality as Bonded Interfaces on Oracle Linux. You can name the IPMP groups anything. In this guide,
BOND1 are used as example names to keep the terminology consistent with Oracle Linux.
For shares that were created without
root access, run the following commands. This ensures that a
root user within a compute node that hosts Oracle Traffic Director is able to start the administration server and administration node:
<ZFS-SharedStorage> shares <ZFS-SharedStorage> select <Project-used-for-OTD> <ZFS-SharedStorage> get sharenfs <ZFS-SharedStorage> set sharenfs ="sec=sys,rw=@<<ip-address-1>/<network-prefix-bits>,root=@<ip-address-2>/<network-prefix-bits>" <ZFS-SharedStorage> commit
After creating the shares with the appropriate permission, mount the shares based on your requirement:
For information about mounting shares on an Exalogic physical configuration, see "Creating NFSv4 Mount Points on Oracle Linux" in the chapter "Configuring NFS Version 4 (NFSv4) on Exalogic" of the Oracle Exalogic Elastic Cloud Machine Owner's Guide:
For information about mounting shares on an Exalogic virtual configuration, see "Setting Up Access to the ZFS Storage Appliance for a vServer" in the Oracle Exalogic Elastic Cloud Administrator's Guide:
The mount point that you create is the location where Oracle Traffic Director will be installed. For more information, see Chapter 4, "Installing Oracle Traffic Director."