ES16 general CoS & burst size guide line

Traffic flow parameters:

Ingress Peak Rate (InPkR
InPkR)
InPkR ------> Policing rate (CIR
CIR and or PIR)
PIR ---> Egress Port Line rate (EgPLr
EgPLr)
EgPLr

Ingress Peak Rate (InPkR

InPkR)
InPkR == maximum traffic peak rate reached at ingress port (up to Ingress port line
rate)
Policing rate (CIR
CIR and or PIR)
PIR == parameters defined on traffic descriptor

Generally the size of burst depends of difference between Ingress Peak Rate and Policing rate.

Two cases could be meet:

- Incoming Traffic shaped, it means that the rate incoming of traffic flow submitted at policing
parameters choose is constant and its value is around CIR and/or PIR; this solution is
recommended when running services required for low latency, The traffic type of traffic descriptor
could be Guaranteed,
Guaranteed Regulated,
Regulated Best Effort,
Effort the minimum CBS & or PBS required = > MTU and
the maximum value of CBS == 16Kbytes the PBS <= 1,4 PIR

- Incoming Traffic bursty, it means that the rate incoming of traffic flow submitted at policing
parameters choose is not constant, its instantaneously value could be up to the Ingress Port Line
rate but the its average is around CIR and/or PIR. In this case the traffic type of traffic descriptor
could be Regulated & Best Effort [ the Guaranteed traffic type should be
be avoided this Class of
Service can be replaced by Regulated traffic type using a trick as CIR=PIR;
CIR=PIR CBS=16kBytes and
the PBS tuned as below],
], the minimum CBS & or PBS required = > MTU and the maximum value
of CBS == 16Kbytes the PBS <= 1,4*PIR, the value of burst size should be based on the
maximum Ingress Peak Rate PBS = { [ ( (1 - (PIR
PIR / InPkR)
InPkR ) * PIR ] / 8 }; in the worst case the
Ingress Peak Rate is equal at Ingress Port Line Rate.
Rate
Policing & Queuing

Inside the ES16 the Class of Service or Traffic Type define the queue where the traffic is forwarded and
how the policer marks the incoming traffic as conforming (green and/or yellow) and/or not conforming
(red) in according with the policing parameters;

About Policer:

Guaranteed
policer == color blind (the policing doesn’t take account on 802.1p priority bits) / Guaranteed

• CIR + CBS Conforming packets marked green

• CIR + CBS Not conforming packets marked red (will be discarded)

policer == disabled / Guaranteed

all packets marked green

Regulated

policer == color blind (the policing doesn't take account on 802.1p priority bits) / Regulated

• CIR + CBS conforming packets marked green

• PIR + PBS conforming packets marked yellow
• PIR + PBS not conforming packets marked red (will be discarded)

policer == color aware (the policing takes account on 802.1p priority bits than the color map it will be
used) / Regulated
• Incoming packets where 802.1p priority bits are green on color profile with conforming
CIR + CBS packets marked green
• Incoming packets where 802.1p priority bits are green on color profile with not conforming
packets CIR but conforming to PIR + PBS will be marked yellow
• Incoming packets where 802.1p priority bits are yellow 802.1p priority bits on color profile
with conforming PIR + PBS packets marked yellow
• Incoming packets where 802.1p priority bits are green/yellow on color profile with not
conforming PIR + PBS packets marked red (will be discarded)
• All incoming packets where 802.1p priority are red bits on color profile will be discarded
policer == disabled; the policing is not take in account 802.1p priority bits / Regulated
all packets marked green/yellow red as chose as color profile, default values all traffic is marked green

Best Effort
policer == color blind (the policing doesn’t take in account on 802.1p priority bits) / Best Effort
• PIR + PBS conforming packets marked yellow
• PIR + PBS not conforming packets marked red (will be discarded)
policer == disabled / Best Effort
all packets marked yellow

About Queuing:

a) for ES16 in bridge mode == none:

Guaranteed / Expedited Forwarding CoS is a queue High Priority served in strict priority
Regulated / Assured Forwarding CoS is a queue Low Priority where RED algorithm is applied for
green(low discard probability), yellow packets(high discard probability)
Best Effort / Default Behavior CoS is the same queue of Regulated / Assured Forwarding CoS only
yellow packets(high discard probability)

a) for ES16 in bridge mode == 802.1D, 802.1Q,802.1AD:

Guaranteed CoS is a queue High Priority served in strict priority

Regulated CoS is a queue MID Priority where RED algorithm is applied for green(low discard
probability), yellow packets(high discard probability)
Best Effort CoS is a queue Low Priority

Example: if IPkR = 1Gigabit/s , CIR or PIR=1Megabit/s

PIR
the BS should be = { [ ( (1 - ( 1e+6 / 1e+9 ) ) 1e+6 ] / 8 } = 124875 Bytes,
being the BS required more than 16KBytes:
- the CoS Guaranteed is not suggested to use because BS required is more than 16kBytes
- if the CoS is Regulated the CIR=PIR=1000Kbit CBS=16384Bytes PBS =124875Bytes
- if the CoS is Best Effort the PIR=1000Kbit PBS = 124875Bytes.
124875Bytes
Triple Play suggested CoS(defined by traffic type of traffic descriptor):

Voip -> Guaranteed up to 16kBytes burst size required otherwise (if the incoming traffic is not shaped)
Regulated

Video Streaming -> Guaranteed up to 16kBytes burst size required otherwise Regulated

Internet High Speed -> generally Best Effort,

Effort Regulated (if some guaranteed traffic is required from
Customer)

When enable the Policing of inflow?

Only if on Egress Port placed in the same or different NE some congestion with others flow could be
reached

Where enable the Policing of inflow?

Only on the inflow placed on the first ingress port where customer service is incoming; avoiding all others
policing point in the middle or in the end of the network.

How check if the Police parameters are corrects?

Using PM check if the incoming traffic is discarded (TRCFr & TRCOr) on QoS Maintenance Tab of inflow.