To ensure that the traffic is migrated properly, the following validations need to be done. Please take note in each Result section indicating whether or not the actual output matches the expected output.
Traffic Direction
Purpose
To verify that traffic processor server(s) are receiving traffic properly.
Procedure
- Open a web browser (Google Chrome or Firefox)
- On the browser search bar, type:
https://<management system IP address> - When the management system page is loaded, use the credentials provided by Cisco to
login into the system. The security certificate may have to be manually accepted for both the management system user interface and the opanga-services may have to be accepted. - Go to Platform -> Status -> Server Throughput
The downlink throughput should be much greater than the uplink throughput.
This is an example of incorrect traffic direction as shown below. The uplink traffic is about 2Gbps vs about 200Mbps of downlink throughput.
Incorrect Traffic Direction
If this is the case, we need to change the direction of the interfaces:
SSH into the server(s) that has incorrect traffic direction
sudo vppctl show ncss int
This is the output of the incorrect traffic direction due to how the cables are connected to traffic processor server.
p1p2 (1) - Interface Direction: uplink - Link: up - Admin: up - Link Speed: 100 Gbps - Driver: dpdk
RX - Bitrate: 681.57 Mbps - PPS: 1.26 Mpps
TX - Bitrate: 14.70 Gbps - PPS: 1.31 Mpps
Loss - 30s: 0.00% - 5m: 0.00% - 1h: 0.00%
Warning: This port and its peer may have reversed traffic present.
Check cabling or interface directionality configuration in boot.conf
---------------------------------------------------------------------------------
---------------------------------------------------------------------------------
p1p1 (2) - Interface Direction: dnlink - Link: up - Admin: up - Link Speed: 100 Gbps - Driver: dpdk
RX - Bitrate: 14.70 Gbps - PPS: 1.31 Mpps
TX - Bitrate: 681.57 Mbps - PPS: 1.26 Mpps
Loss - 30s: 0.00% - 5m: 0.00% - 1h: 0.00%
---------------------------------------------------------------------------------
Here the directionality on the p1p2 and p1p1 interface pair are reserved, we can tell because the downlink interface has significantly
higher RX bitrate than TX. The CLI command has a helper warning here that confirms this.
To change the direction:
sudo vppctl ncss enable uplink p1p1 downlink p1p2
where the interface shown previous as downlink goes after uplink and vice versa.
This will fix the directionality at runtime without needing to distrupt traffic.
To ensure this is set correctly if the process reboots, edit the entry in the
/opt/ncss/conf/local.conf file with the same interfaces to run the above command.
The syntax when used in local.conf will involve some alterations to the existing file,
swapping uplink and downlink.
Original:
ncss enable uplink p1p2 downlink p1p1
set interface state p1p1 up
set interface state p1p2 up
Swapped:
ncss enable uplink p1p1 downlink p1p2
set interface state p1p1 up
set interface state p1p2 up
Correct Traffic Direction
The downlink throughput (~2Gbps) now is much bigger than the uplink throughput (~200Mbps)
Result
The downlink throughput should be much greater than the uplink throughput as shown below:
System Throughput
If the traffic processor server(s) is in BYPASS mode, then the layer 4 downlink/uplink throughput should be 0s.
Traffic Classifications
Purpose
To verify that server(s) are configured properly.
Procedure
- Open a web browser (Google Chrome or Firefox)
- On the browser search bar, type:
https://<management system IP address> - When the management system page is loaded, use the credentials provided by Cisco to
login into the system. The security certificate may have to be manually accepted for both the management system user interface and the opanga-services may have to be accepted. - Go to Platform -> Settings -> Traffic Classification
- Click on the Traffic Processor group to view traffic classifications
Result
Make sure the Traffic Processor group has the following traffic classifications
Default
- Configuration
- Policy: Unmanaged
- Tag: DEFAULT
- Identifier(s):
- Type: ALL
TCP and QUIC
Make sure the Traffic Processor group has the following traffic classifications
TCP
- Configuration
- Policy: REG
- Tag: TCP_ REG
- Identifiers:
- Type: Protocol
- Identifier(s): tcp
or alternatively:
- Configuration
- Policy: TCP_HIGH
- Tag: TCP _HIGH
- Identifiers:
- Type: Protocol
- Identifier(s): tcp
NOTE: only one option, high or reg, should be set
QUIC
- Configuration
- Policy: QUIC_ REG
- Tag: QUIC_ REG
- Identifiers:
- Type: Protocol
- Identifier(s): quic
or alternatively:
- Configuration
- Policy: QUIC_HIGH
- Tag: QUIC_HIGH
- Identifiers:
- Type: Protocol
- Identifier(s): quic
NOTE: only one option, high or reg, should be set
Traffic Metrics
Purpose
To verify that Traffic Processor server(s) optimize traffic properly.
Procedure
- Open a web browser (Google Chrome or Firefox)
- On the browser search bar, type:
https://<management system IP address> - When the management system page is loaded, use the credentials provided by Cisco to
login into the system. The security certificate may have to be manually accepted for both the management system user interface and the opanga-services may have to be accepted. - Go to Network Optimization -> Traffic Metrics
- In Absolute tab, choose to view Today
Result
Flow Interaction Breakdown
- Unmanaged elephant flows: <= 5%
- Managed elephant flows: <= 5%
- Standard flows: >= 90%
Flow Volume Breakdown
Expected Output
- Unmanaged elephant flows: ~= 25%
- Managed elephant flows: ~= 50%
- Standard flows: ~= 25%
Elephant Information
- Average recovered capacity per elephant flow: 1.1-1.6Mbps
- Average % time managed per elephant flow: ~>= 40%
Traffic Processor Performance and Usage
Purpose
To verify that Traffic Processor server(s) operating properly.
Procedure
- Open a web browser (Google Chrome or Firefox)
- On the browser search bar, type:
https://<management system IP address> - When the management system page is loaded, use the credentials provided by Cisco to
login into the system. The security certificate may have to be manually accepted for both the management system user interface and the opanga-services may have to be accepted. - Go to Platform -> Status -> Performance and Usage
- Choose Traffic Processor tab
- In Absolute tab, choose to view Today
Result
Bytes/Packets per Worker
All bytes/packets across all worker cores should be balanced as shown below.
Bytes/Packets per Worker
Resources
These graphs can only be viewed by Cisco Admin users.
All pool usage must be balanced across all worker cores as shown below:
Flow Pool / Buffer Pool Utilization
Elephant Pool Utilization
Operating Mode
Make sure that the operating mode in the graph matches with what the Operating Mode shown in the Server page:
Operating Mode Graph
Max Reported Usage Across Cores
This graph can only be viewed by Cisco Admin users.
Make sure that all pool/table/ring usage is under load (~60%-80%). If any resources is starting to approach 100% utilization, we need to inform .
Max Reported Usage Across Cores
Interface Error Counters
Make sure there is no Rx/Tx error/misses and RxNoBuff on the graph as shown below:
Interface Error Counters
Core Count
The number of worker core, control plane core, main core, and interface count should match the numbers that are configured during installation.
Network Interface Status
The should show all Server(s) and their interfaces along with the link
status.
- Link status: it should be UP
- Max negotiated link speed: it should be the NIC’s capacity
- Peak utilization:
- Mellanox NICs: These NICs use the packet per second to measure
the peak utilization in the last 12 hours. - Other NICs: These use the bytes per second to measure the peak
utilization.
- Mellanox NICs: These NICs use the packet per second to measure
Management System Performance and Usage
Purpose
To verify that Traffic Processor server(s) operating properly.
Procedure
- Open a web browser (Google Chrome or Firefox)
- On the browser search bar, type:
https://<management system IP address> - When the management system page is loaded, use the credentials provided by Cisco to login into the system. The security certificate may have to be manually accepted for both the management system user interface and the opanga-services may have to be accepted.
- Go to Platform -> Status -> Performance and Usage
- Choose management system tab
Result
Make sure that the resource meter is under load (<75%)
- CPU load: it should show the current load and make sure that it’s
under load - Disk usage: it should show the current usage and make sure that it’s
under load - Memory usage: it should show the current usage and make sure that
it’s under load
Standalone Performance and Usage
Traffic Processor Server
Purpose
To verify that management system shows the correct status of Traffic Processor Server(s).
Procedure
- Open a web browser (Google Chrome or Firefox)
- On the browser search bar, type:
https://<management system IP address> - When the management system page is loaded, use the credentials provided by Cisco to login into the system. The security certificate may have to be manually accepted for both the management system user interface and the opanga-services may have to be accepted.
- Go to Platform -> Servers -> Management
- Choose the Traffic Processor group that needs to be validated
Result
Make sure the Traffic Processor server(s) is configured correctly with the
followings:
- Group name
- Software
- Configuration
- IP
- Hostname
- Hardware ID
- Status should be ACTIVE
- Maintenance Mode should be OFF
- Instance Action
- Command: Ability to Start, Stop, and Restart this service
- Maintenance Mode: Ability to turn ON and OFF
- Operating Mode: Ability to change to one of the following modes:
- Optimize
- Bypass
- Passive
- Remove Instance: Ability to remove this instance from this management system
Server Information
License
Management
Purpose
To verify that has the correct license installed.
Procedure
- Open a web browser (Google Chrome or Firefox)
- On the browser search bar, type:
https://<management system IP address> - When the management system page is loaded, use the credentials provided by Cisco to login into the system. The security certificate may have to be manually accepted for both the management system user interface and the opanga-services may have to be accepted.
- Go to Network Optimization -> Usage
Result
Make sure that the installed license has the correct information as
agreed with customer for the following fields:
- Expiration date
- Features with the proper “Limit Value” and individual configurations
License Management
Dashboard
Purpose
To verify that management system shows the correct license statistics.
Procedure
- Open a web browser (Google Chrome or Firefox)
- On the browser search bar, type:
https://<management system IP address> - When the management system page is loaded, use the credentials provided by Cisco to login into the system. The security certificate may have to be manually accepted for both the management system user interface and the opanga-services may have to be accepted.
- Go to Platform -> Licensing -> Management
Result
Make sure that the graph shows the correct max licensed throughput that matches with what is shown in Platform -> Licensing -> Management
License Dashboard
About
Purpose
To verify that management system shows the correct software versions that are agreed
with customer.
Procedure
- Open a web browser (Google Chrome or Firefox)
- On the browser search bar, type:
https://<IP address> - When the management system page is loaded, use the credentials provided by Cisco to login into the system. The security certificate may have to be manually accepted for both the management system user interface and the opanga-services may have to be accepted.
- Go to About
Result
Make sure the following fields contained the correct software version:
- Opanga Services API
- Management System Version
- Legal Information
© 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