Applying a different QoS policy for peering traffic in SR (S3/M3/L3)
Posted by Padam J Singh on 28 October 2016 09:41 AM

For applying a differentiated QoS on a SR, please follow the steps below:

1. On the S3/M3/L3:
1.1 Add a firewall rule in table forward :
table forward continue inport CPETHX src A.B.C.D/M set-pcc peering

For example, if the subnet of google peering is and the WAN interface is cpeth0 then the rule will look like:

table forward continue inport cpeth0 src set-pcc peering
If there are multiple subnets or different ways in which peering traffic is determined then alter the matches according and add multiple firewall rules to address each.

2. On the UNIFY:
2.1 Go the rate plan and add the following meta-tag to the selected rate-plan:
Name: AddRadiusReplyAttribute, Value: Filter-Id=PCC=peering;gating=on;qos=QOS_POLICY_ID;acct=on
For example, if the qos policy ID in UNIFY is 2mbps, then the value will be Filter-Id=PCC=peering;gating=on;qos=2mbps;acct=on

When the session re-logs in, it should apply a different qos policy to peering traffic. Please note than "what" is peering traffic (subnets, ToS bits) etc. are known to the SR, not UNIFY. However, what to do with peering traffic is provided by UNIFY.

Padam J. Singh
VP Engineering

+91-120-464-7000 When replying, please ensure subject line contains the ticket number [TCKT !123456] and the recipient in the "To:" field is set to "" ######

(3 vote(s))
Not helpful

Comments (0)