03-04-2008 06:14 PM - edited 03-13-2019 05:02 PM
I have to give a strict priority to the IP traffic between RAD IPMUX11, but as I understand my config doesn't work (round-trip min/avg/max = 4/9/92 ms) :
2621_KRKZ#ping
Protocol [ip]:
Target IP address: 192.168.106.250
Repeat count [5]: 10000
Datagram size [100]:
Timeout in seconds [2]:
Extended commands [n]:
Sweep range of sizes [n]:
Type escape sequence to abort.
Sending 10000, 100-byte ICMP Echos to 192.168.106.250, timeout is 2 seconds:
!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!
Success rate is 100 percent (10000/10000), round-trip min/avg/max = 4/9/92 ms
2801_TRKT#show policy-map interface fastEthernet 0/0
FastEthernet0/0
Service-policy output: SHAPER
Class-map: SHAPE_TRKT (match-any)
178431579 packets, 211551221854 bytes
5 minute offered rate 2237000 bps, drop rate 0 bps
Match: access-group 165
178431585 packets, 211551221746 bytes
5 minute rate 2237000 bps
Traffic Shaping
Target/Average Byte Sustain Excess Interval Increment
Rate Limit bits/int bits/int (ms) (bytes)
75 (%) 0 (ms) 0 (ms)
7500000/7500000 45000 180000 180000 24 22500
Adapt Queue Packets Bytes Packets Bytes Shaping
Active Depth Delayed Delayed Active
- 0 178431590 1097835450 959224 1187521203 no
Queueing
Output Queue: Conversation 265
Bandwidth 7500 (kbps) Max Threshold 64 (packets)
(pkts matched/bytes matched) 1138617/1223438515
(depth/total drops/no-buffer drops) 0/0/0
Service-policy : E1inIP_TRKT
Class-map: E1inIP (match-any)
138717940 packets, 205723994192 bytes
5 minute offered rate 2158000 bps, drop rate 0 bps
Match: access-group 195
138428388 packets, 205703718834 bytes
5 minute rate 2158000 bps
Match: protocol icmp
289554 packets, 20275358 bytes
5 minute rate 0 bps
Queueing
Strict Priority
Output Queue: Conversation 136
Bandwidth 2350 (kbps) Burst 58750 (Bytes)
(pkts matched/bytes matched) 235109/347943319
(total drops/bytes drops) 0/0
Class-map: class-default (match-any)
39713637 packets, 5827229108 bytes
5 minute offered rate 78000 bps, drop rate 0 bps
Match: any
Class-map: class-default (match-any)
737527 packets, 84597022 bytes
5 minute offered rate 0 bps, drop rate 0 bps
Match: any
03-08-2008 05:14 PM
Your attachment shows a 10 Mbps and 100 Mbps conections to the WAN cloud. Are these bandwidths actually guaranteed by the WAN provider both a cloud edge and throught the cloud? Can any other traffic be on the WAN connected links bypass the 2621s?
03-08-2008 05:15 PM
Ignore this (forgot to check off notify box in prior post).
03-09-2008 09:34 PM
1. Are these bandwidths actually guaranteed by the WAN provider both a cloud edge and throught the cloud? - No body knows. Provider did not answer me yet, but anyway, I want to know if my config is correct? Also I add ICMP to check if my config is correctand and as I see the ping result, it is not correct.
Can any other traffic be on the WAN connected links bypass the 2621s? - Yes, there is aprox. 2-4 Mbit/s of RDP, CIFS and HTTP.
Thank you.
03-10-2008 04:56 AM
"I want to know if my config is correct?"
It appears to be correct. However, it could also be ineffective, which might explain the poor ping results.
For it to be effective, all traffic has to be shaped. So, if there is other traffic that truly bypasses the router, you're priority traffic really isn't.
Second, the shaper must control the bandwidth. If the shaper's bandwidth restriction is larger than what the WAN cloud provides, congestion could form within the cloud were it might just be FIFO.
One issue that can also arise with WAN clouds, if multiple sources can send to the same destination, you'll either need to insure all combinations will not oversubscribe the egress bandwidth, or discover whether the WAN provider supports QoS beyond just FIFO and whether you can take advantage of it.
03-14-2008 10:03 PM
Thank you.
Find answers to your questions by entering keywords or phrases in the Search bar above. New here? Use these resources to familiarize yourself with the community: