The override.properties file contains advanced configuration settings used by Cisco Services. These settings are read when Cisco Services application starts. If you make any changes to this file, the new values won’t take effect until you restart Cisco Services.
All the configurations can be updated at /opt/opanga-services/config/override.properties. If this file does not exist, it needs to be created:
sudo touch /opt/opanga-services/config/override.properties
The configured entries need to be added to the override.properties otherwise the default values will be used.
Note:: The Services API must be restarted for these changes to take effect. To restart Services application:
sudo docker compose -f /opt/opanga-services/docker-compose.yml restart
Network Monitoring
The Management System monitors packet anomalies to ensure that each traffic processor handles a proper amount of traffic based on its throughput capacity.
Throughput Decrease Detection
The Management System monitors average system throughput on a minute-by-minute basis. If
the agent detects a decrease in throughput by a percentage greater than
a configurable average throughput percentage threshold, the following
actions will be taken:
- When maintenance mode is OFF, an email notification will be sent.
- If short circuit cutoff is enabled, the Management System will put the affected traffic processor to BYPASS mode.
Note: Only abrupt changes in system throughput will be recognized. A
gradual decrease in throughput will not be detected by the throughput
anomaly detection process.
The throughput anomaly detection process can be configured via the
following properties:
-
dashboard.throughput.monitor.time.window.in.minutes
Description: How often the average system throughput is calculated.
Default value: 3
-
dashboard.throughput.monitor.percentage.threshold
Description: The maximum permitted percentage decrease in average system throughput between time windows.
Default value: 80
-
dashboard.throughput.monitor.short.circuit.enable
Description: Whether the traffic processor application should be set to BYPASS mode.
Default value: false
Note: If the short circuit cutoff is enabled then the system will remain
in BYPASS mode until the system is manually set back to optimize mode.
Packet Anomalies Monitoring
The Management System monitors and responds to packet anomalies on a second by second
basis. A SNMP trap and/or email notification can be sent upon detection
of the following errors:
- Transmit interface errors.
- Dropped packets on transmission exceeding a configurable error threshold.
- Dropped packets on reception exceeding a configurable error threshold.
- The sum of uplink and downlink packets per seconds overflow (Overpass predefined thresholds)
These are the predefined thresholds for the downlink and uplink packets per second (pps), for monitoring and enforcement as configured.
| Downlink PPS Limit | Uplink PPS Limit | Threshold Level | NIC Capacity (Gbps) |
|---|---|---|---|
| 8,000,000 | 4,000,000 | ONE | 100 |
| 8,500,000 | 4,500,000 | TWO | 100 |
| 3,200,000 | 1,600,000 | ONE | 40 |
| 3,400,000 | 1,800,000 | TWO | 40 |
| 2,000,000 | 1,000,000 | ONE | 25 |
| 2,125,000 | 1,125,000 | TWO | 25 |
| 800,000 | 400,000 | ONE | 10 |
| 850,000 | 450,000 | TWO | 10 |
There are several actions that can be configured base on each deployment when the Management System detects any anomalies:
| Action Method | Description |
|---|---|
| 0 | Take no |
| 1 | Turn off traffic processor service to trigger a traffic failover to the alternate path. |
| 2 | Take down a set of network interfaces on the management NIC of the traffic processor Server that triggered this overage. These network interface names across all traffic processor Server(s) must be the same. The intent is for this to act as a signal to an external customer monitor so that traffic failover can be triggered without turning off the traffic processor service. |
| 3 | Put the traffic processor in BYPASS mode which all traffic is directly forwarded between NIC ports without being pulled into the application. No optimization is performed, nor are statistics recorded, aside from layer 2 metrics which show the bytes being delivered across the network bridge. |
For example, assume:
- Error monitor time window = 60 seconds
- Error percentage level one threshold = 1%
- Error percentage level one method to enforce = 0 which is take no action
- Error percentage level two threshold = 5%
- Error percentage level two method to enforce = 3 which is to put traffic processor to BYPASS mode
This means that packet anomalies will be accumulated over a
60-second period. Then the number of anomalies during that minute is
divided by the total packets for that minute to get the error
percentage. If the error rate > 1% (error percentage threshold level one) then the Management System takes no action (enforcement type 0) and and an alarm is triggered.
If the packet anomalies reach level two threshold of 5%, the Management System will put the traffic processor service to BYPASS mode (enforcement type 3) and an alarm is triggered.
Packets processing limit monitoring example, assume this is for 100Gbps NICs:
- Error monitor time window = 60 seconds
- Uplink (4,000,000pps) and downlink (8,000,000pps) packet overflow level one threshold for 100Gbps NIC = 12,000,000
- Uplink (4,500,000pps) and downlink (8,500,000pps) packet overflow level two threshold for 100Gbps NIC = 13,000,000
- Level one enforcement method = 1 which is to turn off traffic processor service
- Level two enforcement method = 3 which is take no action
This means that the amount of uplink and downlink packets per second are
sampled at the end of every 60 seconds (configurable). If the sum of the
uplink and downlink packets per second captured in one of the 60 samples
exceeds the level one threshold the traffic processor service that reported the spike would
be turned off (enforcement type 1) to trigger a traffic failover to the alternate path and an alarm is triggered. In case the level two threshold is exceeded the Management System will take no action (enforcement type 0) and an alarm is triggered.
The above described packet anomaly and pps limit monitoring process can be configured via the
following properties:
-
dashboard.packet.anomalies.monitor.time.window.in.seconds
Description: The interval in seconds over which the anomaly rate is measured.
Default value: 60
-
opanga.services.packet.anomaly.level.one.percent.threshold
Description: Level one percentage threshold for packet anomalies. If the percentage of anomalies within the monitoring window exceeds this, then level one enforcement will be activated.
Default value: 1
-
opanga.services.packet.anomaly.level.two.percent.threshold
Description: Level two percentage threshold for packet anomalies. If the percentage of anomalies within the monitoring window exceeds this, then level two enforcement will be activated.
Default value: 5
-
opanga.services.packet.anomaly.level.one.enforced.method
Description: The method action to execute when packet anomaly level one is reached.
Default value: 0
-
opanga.services.packet.anomaly.level.two.enforced.method
Description: The method action to execute when packet anomaly level two is reached.
Default value: 3
-
opanga.services.packet.limit.level.one.enforced.method
Description: The method action to execute when packet limit level one is reached.
Default value: 3
-
opanga.services.packet.limit.level.two.enforced.method
Description: The method action to execute when packet limit level two is reached.
Default value: 0
SMTP
If SMTP server is configured during the platform infrastructure installation, then a set of emails can be configured to receive notifications:
-
opanga.services.notification.email.list
Description: The list of customer emails to receive notifications that are configured to be sent by SNMP only.
Default value: Not set
-
opanga.services.notification.customer.email.list
Description: The list of customer emails to receive notifications that are configured to be sent by SNMP only.
Default value: Not set
Installation Type
-
opanga.services.all.in.one
Description: Specify whether traffic processor is installed on the same server as the Management System.
Default value: true
© 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