The Acoustic™ Tealeaf packet forwarder is used to forward web traffic that is transmitted between a client and a cloud-based web server to a cloud-based PCA.
The packet forwarder is packaged with the PCA software and shares the same requirements as the PCA software.
Packet forwarder installation on SLES 12 OS
Packet forwarder installation on SLES 12 OS may give an error that it is not able to detect nmap-ncat dependencies. If such error is encountered, ensure that nmap-ncat packages are installed the concerned SLES 12 machine and you’re successfully able to execute ‘ncat' command.
If problem still persists, install packet forwarder RPM by using --nodeps option like following:
rpm -ivh tealeaf-pktfwdr-<nnnn>-<rrr>.<distro>.i686.rpm
--nodeps
Cloud-based installation with a reverse proxy server
If your cloud-based web solution includes a reverse proxy server, you can install the packet forwarder software to the reverse proxy server and to the PCA server. After the packet forwarder software is installed, you must configure packet forwarder transmitter instance on the reverse proxy server and the packet forwarder receiver instances on the PCA.
Cloud-based installation with no reverse proxy server
If your cloud-based web solution does not include a reverse proxy server, you can install the packet forwarder software to each web server in your cloud-based environment and to the PCA server. After the packet forwarder software is installed, you must configure the packet forwarder transmitter instances on your web servers and the packet forwarder receiver instances on the PCA. Each transmitter instance requires a dedicated receiver instance.
Run the following command to install the tealeaf-pktfwdr
package.
- If you are using Red Hat Package Manager, enter the following:
rpm -ivh tealeaf-pktfwdr-<nnnn>-<rrr>.<distro>.i686.rpm rpm -ivh --prefix=/opt/tealeaf tealeaf-pktfwdr-<nnnn>-<rrr>.<distro>.i686.rpm
Where:
<nnnn>
is the build version number; for example, 3650.<rrr>
is the RPM revision number. This is usually a single digit number.<distro>
is an identifier for the Linux™ distribution, such as "RHELn" for Red Hat Enterprise Linux release n.
Note: Red Hat Enterprise Linux (RHEL) 7 uses the same packet-forwarder installation package and process as Red Hat Enterprise Linux (RHEL) 6.x. In this scenario, use tealeaf-pca-<nnnn>-<rrr>.RHEL6.i386.rpm for the installation package. - If you are using Yellowdog Updater Modified (Yum), enter the following:
yum install tealeaf-pktfwdr-<nnnn>-<rrr>.<distro>.i686.rpm yum install --prefix=/opt/tealeaf tealeaf-pktfwdr-<nnnn>-<rrr>.<distro>.i686.rpm
Where:
<nnnn>
is the build version number; for example, 3650.<rrr>
is the RPM revision number. This is usually a single digit number.<distro>
is an identifier for the Linux distribution, such as "RHELn" for Red Hat Enterprise Linux release n.
By default, the PCA software is installed in /usr/local/ctccap
.
You can relocate the package to a directory other than the default /usr/local/ctccap
. You specify the alternate directory by using the rpm command's --prefix
option along with the installation and upgrade commands.
The following are some sample rpm invocations.
rpm -i --prefix=/opt/tealeaf tealeaf-pktfwdr-<nnnn>-<rrr>.<distro>.i686.rpm
rpm -U --prefix=/home/tealeaf tealeaf-pktfwdr-<nnnn>-<rrr>.<distro>.i686.rpm
Where:
<nnnn>
is the build version number; for example, 3650.<rrr>
is the RPM revision number. This is usually a single digit number.<distro>
is an identifier for the Linux distribution, such as "RHELn" for Red Hat Enterprise Linux release n.
When you do not use the --prefix
option during an install or upgrade, RPM uses the default installation directory that is specified in the package file, which is /usr/local/ctccap
. If you relocate a package, you must make sure that you always specify the alternative directory so that the package can accurately check for and update any previous installations.
If a custom installation directory is not used, the following directory structure is created.
/opt/tealeaf/
/bin/pktfwdr
/bin/ctcstats
/etc/fwdr-conf.xml
/etc/fwdr-conf-defaults.xml
/sbin/
The following core files are installed:
File name | Description |
---|---|
pktfwdr |
Packet forwarder daemon To start a packet forwarder instance, run |
ctcstats |
Operational statistics/metrics |
fwdr-conf.xml |
Packet forwarder configuration file |
fwdr-conf-defaults.xml |
Default configuration file |
yum install glibc.i686
yum install zlib.i686
or
yum install rpm -ivh --prefix=/opt/tealeaf tealeaf-pktfwdr-<nnnn>-<rrr>.<distro>.i686_24thApr14.rpm
After the installation is complete, you must configure the packet forwarder instances.
Packet Forwarder Commands
You can run the Packet Forwarder utility with command options.
The Packet Forwarder can be run with options to start an instance, stop an instance, and more. For example, to start the Packet Forwarder, run /user/local/ctccap/bin/pktfwdr -t
where -t
is the option that tells the Packet Forwarder to start the service.
The following options are available when you run the Packet Forwarder.
Option | Description |
---|---|
-c <configuration file> |
Overrides the default configuration file and gives you the ability to use of a custom configuration file, where <configuration file> is the name of the configuration file. |
-D |
Delete transmitter SHM. |
-d |
Debug option. |
-e |
Encapsulate packet mode. |
-f <filter rule> |
Override the filter rules that are specified in the configuration file. |
-h |
Version and option list. |
-i <NIC interface> |
Override the NIC settings that are specified in the configuration file. |
-I <instances#> |
Specifies the number of transmitter instances to load, where <instances#> is the number of instances that you want to run. |
-k |
Stop the service and its instances. |
-l |
Reports if the service is running. |
-n |
Debugging option for a stand-alone environment. |
-t |
Start the service. |