Control Traffic Processor (CTP) is a part of the Traffic Processor software that processes the S1‑MME and S11 mirror traffic to help Traffic Processor improve cell performance at any given time. Control Traffic Processor should be installed on the server(s) that receive control plane information.
Install Control Traffic Processor
The Management System software must be installed prior to installing the Control Traffic Processor.
If the Platform Packages dependencies has not yet been installed on this server, it must be run before proceeding to the next section.
Install Fluentd
If installing on a server with a Traffic Processor this step would have been taken care of in the Traffic Processor installation, otherwise it needs to be done here.
export PRIMARY_MS_IP={Management System public IP}
sudo -E rpm -Uvh fluent-{VERSION}.x86_64.rpm
``### Install Dependencies and Installer```bashsudo rpm -Uvh mpc-dependencies-VERSION.x86_64.rpm
sudo /opt/mpc/install.sh
sudo rpm -Uvh mpc-installer-VERSION.x86_64.rpm
Required Args
Use the provided default installer args as a template to fill in the values according to the following guide.
Arg | Description | Default |
|---|---|---|
primary_ms_addr | The Management System public IP. Will use localhost if not given. | |
api_token | Ensures the security of the Traffic Processor connection to the Management Server. | |
use_interface_ip_addr | Management interface name to scrape the IP address from. | |
interface_conf | Define pair NICs with PCI Address for uplink and downlink. | true |
boot_conf | Define parser mode and the size of memory for ECIs, eNodeBs, subscribers and more. | true |
startup_conf | Set configuration for VPP. | true |
control_plane_cpus | Number of allocated/reserved CPUs from the available CPUs after workers are assigned. After this, the main core is assigned. Be sure to leave a core or two for the OS at minimum. | 4 |
As you can see CTP is similar to Traffic Processor configurations.
API Token
Note: If a token has already been created for installing Traffic Processor, it must be reused.
To generate the API Token:
Log into the Management System.
From Platform, navigate to Accounts and choose Users.
In the actions column of a superadmin user and select the Generate API Token option.
The API Token will automatically be downloaded into your computer as a text file. Open the file in a text editor to obtain the actual API token.
Update the api_token in the default installer args with this API token
Interface Conf
interface_conf:
rx_tx_descriptors: 2048
interfaces:
- name: p1p1
pci_addr: "0000:00:05.0"
worker_count: 4
- name: p2p1
pci_addr: "0000:00:06.0"
worker_count: 4
Name: Since forwarding pairs aren’t involved here, each interface will be of the form
pXp1.
Optional Args
Arg | Description | |
|---|---|---|
secondary_ms_addr | Secondary management server. | |
instance_hostname | Set manually or determined dynamically on the host. | |
instance_ip_address | Manually set IP address if known and statically assigned. | |
local_conf | VPP CLI commands to be ran on the boot of the process. | |
mpc_mirror_rx_queues | Set to number of workers for the traffic processor if its mirroring to this CTP. |
Run Installer
sudo /opt/mpc/setup.sh --args mpc-{host}-installer-args.yml
Important: After installing CTP, the installation manifest, specified in its installer-args as product_install_manifest (e.g., /opt/mpc/conf/installer.conf), contains the configuration of cores and huge pages. This file must never be edited or renamed, as doing so could lead to runtime conflicts between Traffic Processor and CTP and affect upgrades of either program.
© 2026 Cisco and/or its affiliates. All rights reserved.
For more information about trademarks, please visit: Cisco trademarks
For more information about legal terms, please visit: Cisco legal terms
For legal information about Accedian Skylight products, please visit: Accedian legal terms and trademarks