cancel
Showing results for 
Search instead for 
Did you mean: 

Per-CVID Traffic Shaping, not rate limiting

Per-CVID Traffic Shaping, not rate limiting

Philip_Loenneke
New Contributor
We have been building a PoC for a new service. We need to do traffic shaping on individual cvids within an svid (VMAN). We have successfully configured it 2 ways but neither achieve our requirements.

Test network design is:

Router 1
SFP1 with VMAN3999 tagged and VLANs 10-20 inside it
|
Port 33 with VMAN3999 tagged
X670 #1
Port 53 with VMAN3999 untagged
|
Port 53 with VLANs 10-20 tagged
X670 #2
Port 33 with VLANs 10-20 tagged
|
SFP1 with VLANs 10-20 tagged
Router 2

Customers would be on cvids attached to router 1, and download traffic to those customers is the primary target for traffic control. They must be controlled independently.

1st test:
X670 #1:
- Meters for various speeds
- Policy to map meters to cvids
- Attach policy to port 33
IP addresses on each of the routers for the metered VLANs and are used for speed tests.
Result: Traffic limits work per-cvid as required, however traffic is dropped on exceed, causing TCP traffic to have significantly reduced throughput due to a high resend count.

2nd test:
X670 #1:
- Create QoS profiles, assign to port 33 with required speeds
- Policy to map qos profiles to cvids
- Attach policy to port 53 (must be on ingress)
IP addresses on each of the routers for the metered VLANs and are used for speed tests.
Result: Traffic shaping works with far less dropped packets, however the queue size is aggregate for all cvids matching an individual queue on port 33, which means we can't shape individual customers.

Does anyone know if it is possible to get per-cvid traffic shaping, or can we only do traffic limiting (dropping packets instead of queuing them)?
2 REPLIES 2

Philip_Loenneke
New Contributor
I have had confirmation from GTAC that it is not currently possible to achieve this. They have transferred the case to a feature request, that being to allow meters to shape traffic as well as the current drop and re-mark functions. If anyone is interested, the reference number for the feature request is 01174075.

Drew_C
Valued Contributor III
Thanks for coming back with an update Philip.
GTM-P2G8KFN