Smarter by Design.Simpler for Business
TR7Enterprise Application Delivery & Security Platform
How many Traffic Mirroring actions can I use on a vService at most?
Short answer
At most 8. The limit is per vService: when a ninth Traffic Mirroring action is added to the Actions field of the vService form, the form shows the Max. number for Traffic mirroring rule is exceeded: (9 > 8) error and is not saved. The number of Traffic Mirroring actions that can be defined on the device is not limited; the same action can be added to more than one vService.
How Does It Work?
- Each Traffic Mirroring action carries a single Mirror Target Service and its own condition and sampling setting.
- To send a copy of a request to multiple targets, or to mirror different requests to different targets, multiple Traffic Mirroring actions are added to the vService.
- When the vService is saved, the count of each action type in the Actions field is compared with the per-vService limit of that type; if the limit is exceeded, the form is not saved.
vService Limits by Action Type in TR7
| Action type | Maximum per vService |
|---|---|
| Traffic Mirroring | 8 |
| Keep Header Names | 1 |
| Cookie Encryption | 1 |
| IPFIX Log Sending | 1 |
In the other action types, there is no count limit per vService.
Related Limit
At most 16 headers can be written to the Headers removed from the copy list of a Traffic Mirroring action.
Common Misconceptions
- "The limit is device-wide." The limit is applied separately for each vService; any number of Traffic Mirroring actions can be defined on the device.
- "A single action is enough for multiple targets." Each action has a single Mirror Target Service; separate actions are defined for different targets, and each of them on the vService counts toward the limit of 8.
- "A Backend Group can be selected as the mirror target service." This field accepts only a single Backend Service.
How it is done in the documentation
