In this lab Modular QoS CLI is used to ensure minimum bandwidth to the PC according to the criterion IP lowest bigger bandwidth.
Note using the default CBWFQ the sum of bandwidth allocated must not exceed 75% of the total bandwidth of the interface. To change this value using max-reserved-bandwidth [1-100]
access-list 101 permit udp host 192.168.0.101 Any access-list 102 permit udp host 192.168.0.102 Any access-list 103 permit udp host 192.168.0.103 Any class-map match-all pc101 match access-group 101 class-map match- pc_103 to match access-group 103 Class-map match-all pc_102 match access-group 102 policy-map class rules pc101 bandwidth percent 30 percent 20 class class pc_102 bandwidth pc_103 bandwidth percent 10 interface Serial0 ip address 10.0.0.2 255.0.0.0 max- reserved-bandwidth 100 service-policy output rules.
In this case I gave only a 60% band of the class-map and the serial link to 1544Mbit, this means 618K of bandwidth still available, 40%, to be allocated as shown below:
JACK # sh int s0
Serial0 is up, line protocol is up
Hardware is PowerQUICC Serial
Internet address is 10.0.0.2 / 8
MTU 1500 bytes, BW 1544 Kbit, DLY 20000 usec,
reliability 255/255, txload 1 / 255, rxload 1 / 255
Encapsulation HDLC, loopback not set
Keepalive set (10 sec)
Last input 00:00:06, output 00:00:02, output hang never
Last clearing of "show interface" counters never
Input queue: 0/75/0/0 (size / max / drops / flushes); Total output drops: 0
Queueing strategy: Weighted Fair
Output queue: 0/1000/64/0 (size / max total / threshold / drops)
Conversations 0/1/256 (active / max active / max total)
Reserved Conversations 3 / 3 (Allocated / Max Allocated)
Available Bandwidth 619 kilobits / sec
This is because I used max-reserved-bandwidth 100.
We see the standard case, i.e., 75% of the total bandwidth assigned in the case of links to 1.544Mbit, will 1.158Mbit
JACK # sh int s0
Serial0 is up, line protocol is up
Hardware is PowerQUICC Serial
Internet address is 10.0.0.2 / 8
MTU 1500 bytes, BW 1 544 Kbit, DLY 20000 usec,
reliability 255/255, txload 1 / 255, rxload 1 / 255
Encapsulation HDLC, loopback not set
Keepalive set (10 sec)
Last input 00:00:06, output 00:00:06, output hang never
Last clearing of "show interface" counters never
Input queue: 0/75/0/0 (size / max / drops / flushes) Total output drops: 0
Queueing strategy: weighted fair
Output queue: 0/1000/64/0 (size / max total / threshold / drops)
Conversations 0/1/256 (active / max active / max total)
Reserved Conversations 0 / 0 (Allocated / Max Allocated)
Available Bandwidth 1158 kilobits / sec
Input 5 minute rate 0 bits / sec, 0 packets / sec
5 minute output rate 0 bits / sec, 0 packets / sec
1004 packets input, 61639 bytes, 0 no buffer
Received 965 broadcasts, 0 runts, 0 giants, 0 throttles
2 input errors 0, CRC, 2 frame, 0 overruns, 0 ignored, 0 abort
1237 packets output, 112822 bytes, 0 underruns
0 output errors, 0 collisions, 57 interface reset
JACK setup on is as follows:
access-list 101 permit udp host 192.168.0.101 Any access-list 102 permit udp host 192.168.0.102 Any access-list 103 permit udp host 192.168.0.103 Any class-map match-all pc101 match access-group 101 class-map match- pc_103 to match access-group 103 class-map match-all pc_102 match access-group 102 policy-map class rules pc101 bandwidth percent 50 percent 20 class class pc_102 bandwidth pc_103 5 percent bandwidth interface FastEthernet0 ip address 192.168.0.1 255.255.255.0 speed auto interface Serial0 ip address 10.0.0.2 255.0.0.0
NB The following tests were performed with JACK programmed in standard mode.
On each computer was installed IPerf.
The notebooks were launched three instances of program in server mode for receiving UDP packets and listen respectively on ports 5001, 5002 and 5003 to accept the three client connections.
PC was launched on a session IPerf in client mode according to the scheme:
192.168.0.101 -> 192.168.1.4:5001
192.168.0.102 -> 192.168.1.4:5002
192.168.0.103 -> 192.168.1.4:5003
and set to 1Mbit generate UDP traffic for a time of 10 sec.