IQ is abbreviation of Intelligent Queuing. The main different with another PIC is in the queing process which is all traffic queued process are in the PIC itself.
Shaping rate is supported on logical interface basis (Vlan, DLCI, etc). Usually IQ PIC is used for PE interfaces to serving customer connection using VLAN or DLCI. I don’t see benefit using IQ PIC in the core network (MPLS or BGP upstream) rather than to utilize traffic shaping itself.
What I’m talking here is about traffic shaping which are needed to guarantee the traffic flows between provider and customers. Provider should give guaranteed traffic to all customers which are connected to single GigE interface using VLAN. Let say you have a hundred customer using VLAN, mean that you have a hunder VLAN in single GigE interface. IQ Pic can do traffic shaping directly to interface itself. Configuration are simple like shown below:
enugadi@M7i# show interfaces ge-3/3/0
description interface;
per-unit-scheduler;
vlan-tagging;
unit 0 {
vlan-id 100;
family inet {
address 192.168.1.1/30;
}
}
unit 1 {
vlan-id 101;
family inet {
address 192.168.1.5/30;
}
}
enugadi@M7i# show class-of-service
forwarding-classes {
queue 1 be;
queue 0 af;
queue 2 ef;
queue 3 nc;
}
traffic-control-profiles {
customer_100k {
scheduler-map m1;
guaranteed-rate 50k;
delay-buffer-rate 100k;
}
upstream {
shaping-rate 300m;
}
}
interfaces {
ge-0/0/0 {
shaping-rate 10m;
unit 1 {
output-traffic-control-profile customer_100k;
}
}
ge-0/0/3 {
shaping-rate 500m;
}
}
scheduler-maps {
m1 {
forwarding-class be scheduler be;
forwarding-class ef scheduler ef;
forwarding-class af scheduler af;
forwarding-class nc scheduler nc;
}
}
schedulers {
be1 {
transmit-rate percent 30;
}
ef1 {
transmit-rate percent 35;
}
af1 {
transmit-rate percent 25;
}
nc1 {
transmit-rate percent 5;
}
}
From configuration above, you can see there is shaping parameter and guaranteed rate parameter configured in the traffic-control-profiles.
Shaping parameter is called with PIR and guaranteed rate is called with CIR.
You can define specific PIC and CIR for each customer, respectively.
Another approach to do traffic shaping is used rate limit policy which is called with “Policer” in Junos. Both of them has similar function to do rate limit, but the process are really different, IQ PIC doing it in hardware level J, the PIC itself. Another benefit is Hierarchical CoS/QoS supported in the IQ PIC.
Just to give you a clue how to check IQ PIC ASIC components:
iq2(uart)#— hidden—
Output ifd resources
===================
ifd speed bw_remain bw_latent default_ifls latent_ifls total_shaped_bw
– — —– ————————-
128 10000000 7800000 0 0 0 2200000
129 1000000000 1000000000 0 0 0 0
130 1000000000 1000000000 0 0 0 0
131 500000000 500000000 0 0 0 0
ifd guar_bw_remain guar_latent_ifls guar_bw_ifls delay_bw_remain delay_latent_ifls
– ——- ————– ——– ———
128 8900000 0 2 8000000 0
129 1000000000 0 0 1000000000 0
130 1000000000 0 0 1000000000 0
131 500000000 0 0 500000000 0
.
for me as innocent guy (I’m not politician), because I knew these items which is claimed by another when I was a kid.
. Peace
