03-14-2014 10:59 AM - edited 03-04-2019 10:35 PM
Good day,
I have a router configured with CBWFQ, I applied the service policy on a physical interface that has 2 subinterfaces. I already read that as a best practices one should apply the service policy in the subinterfaces after. I have 2 questions
1) If I applied the service policy to the physical interfaces, will the subinterfaces inherit it?
Here is basically what im doing
policy-map CHILD
class xxx
bandwidth percent 10
class yyy
bandwidth percent 10
class zzz
bandwidth percent 10
class aaa
bandwidth percent 40
class class-default
bandwidth percent 30
random-detect
policy-map PARENT
class class-default
shape average 10000000
service-policy CHILD
interface FastEthernet3/1
no ip address
ip route-cache flow
duplex full
speed 10
service-policy output PARENT
****no service policy applied to the subinterfaces****
2) When i do a "show interface" I see " Queueing strategy: fifo" . I dont understand why it is not set to Queueing strategy: Class-based queueing. In other routers ive done this same configurations and the queuing strategy is Classed-based. Do you have any idea based on the configuration why this is??
ROUTER1#sh int f3/1
FastEthernet3/1 is up, line protocol is up
MTU 1500 bytes, BW 10000 Kbit/sec, DLY 1000 usec,
reliability 255/255, txload 7/255, rxload 9/255
Encapsulation 802.1Q Virtual LAN, Vlan ID 1., loopback not set
Keepalive set (10 sec)
Full-duplex, 10Mb/s, 100BaseTX/FX
ARP type: ARPA, ARP Timeout 04:00:00
Last input 00:00:00, output 00:00:00, output hang never
Last clearing of "show interface" counters never
Input queue: 0/75/209/354 (size/max/drops/flushes); Total output drops: 566263
Queueing strategy: fifo
Output queue: 0/40 (size/max)
5 minute input rate 369000 bits/sec, 102 packets/sec
5 minute output rate 275000 bits/sec, 98 packets/sec
28296300 packets input, 1795986141 bytes
Received 24720001 broadcasts, 0 runts, 0 giants, 0 throttles
2 input errors, 0 CRC, 0 frame, 0 overrun, 2 ignored
0 watchdog
0 input packets with dribble condition detected
136860230 packets output, 652952945 bytes, 0 underruns
0 output errors, 0 collisions, 3 interface resets
0 unknown protocol drops
0 babbles, 0 late collision, 0 deferred
0 lost carrier, 0 no carrier
0 output buffer failures, 0 output buffers swapped out
Solved! Go to Solution.
03-18-2014 04:58 AM
Disclaimer
The Author of this posting offers the information contained within this posting without consideration and with the reader's understanding that there's no implied or expressed suitability or fitness for any purpose. Information provided is for informational purposes only and should not be construed as rendering professional advice of any kind. Usage of this posting's information is solely at reader's own risk.
Liability Disclaimer
In no event shall Author be liable for any damages whatsoever (including, without limitation, damages for loss of use, data or profit) arising out of the use or inability to use the posting's information even if Author has been advised of the possibility of such damage.
Posting
Okay, regardless of what the show interface shows for queuing method, you have an active CBWFQ policy on the interface.
03-14-2014 07:42 PM
hi jmaires21,
You need to specify fair-queue in the CHILD policy under default class like so,
!
policy-map CHILD
class class-default
fair-queue
!
Give it a go and let us know..
Please rate helpful posts.
03-17-2014 11:33 AM
Hi Shamax,
Thanks for answering,
I tried your change but its still showing "Queueing strategy: fifo"
03-17-2014 12:19 PM
I'm going over the config over and over and I dont understand why CBWFQ after applying the service policy to the interface.
For info, im using a Cisco3845 with "c3845-ipbasek9-mz.124-25d"
03-17-2014 12:26 PM
Disclaimer
The Author of this posting offers the information contained within this posting without consideration and with the reader's understanding that there's no implied or expressed suitability or fitness for any purpose. Information provided is for informational purposes only and should not be construed as rendering professional advice of any kind. Usage of this posting's information is solely at reader's own risk.
Liability Disclaimer
In no event shall Author be liable for any damages whatsoever (including, without limitation, damages for loss of use, data or profit) arising out of the use or inability to use the posting's information even if Author has been advised of the possibility of such damage.
Posting
Could be a cosmetic bug.
What does show policy-map on interface show?
03-17-2014 12:52 PM
Hi Joseph,
Thanks for your time.
Here is the output of the sh policy-map int x/x output.
Service-policy output: POLICY_WAN
Class-map: class-default (match-any)
8700729350 packets, 4206314501012 bytes
5 minute offered rate 328000 bps, drop rate 0 bps
Match: any
Traffic Shaping
Target/Average Byte Sustain Excess Interval Increment
Rate Limit bits/int bits/int (ms) (bytes)
10000000/10000000 62500 250000 250000 25 31250
Adapt Queue Packets Bytes Packets Bytes Shaping
Active Depth Delayed Delayed Active
- 0 110293083 961529298 108168649 2064625915 no
Service-policy : POLICY_WAN_QOS
Class-map: QOS_HWK_HIPRI (match-all)
177436234 packets, 22688136898 bytes
5 minute offered rate 8000 bps, drop rate 0 bps
Match: access-group name QOS_HWK_HIPRI
Queueing
Output Queue: Conversation 265
Bandwidth 25 (%)
Bandwidth 2500 (kbps)Max Threshold 64 (packets)
(pkts matched/bytes matched) 324065/41572517
(depth/total drops/no-buffer drops) 0/0/0
Class-map: QOS_MANAGEMENT (match-all)
2645440963 packets, 1348777595719 bytes
5 minute offered rate 142000 bps, drop rate 0 bps
Match: access-group name QOS_MANAGEMENT
Queueing
Output Queue: Conversation 266
Bandwidth 5 (%)
Bandwidth 500 (kbps)Max Threshold 64 (packets)
(pkts matched/bytes matched) 3073222/1689835878
(depth/total drops/no-buffer drops) 0/0/0
Class-map: QOS_ROUTING (match-all)
25029316 packets, 3703733836 bytes
5 minute offered rate 0 bps, drop rate 0 bps
Match: access-group name QOS_ROUTING
Queueing
Output Queue: Conversation 267
Bandwidth 10 (%)
Bandwidth 1000 (kbps)Max Threshold 64 (packets)
(pkts matched/bytes matched) 4726/1939308
(depth/total drops/no-buffer drops) 0/0/0
Class-map: QOS_TELEPHONY (match-all)
118 packets, 9204 bytes
5 minute offered rate 0 bps, drop rate 0 bps
Match: access-group name QOS_TELEPHONY
Queueing
Output Queue: Conversation 268
Bandwidth 10 (%)
Bandwidth 1000 (kbps)Max Threshold 64 (packets)
(pkts matched/bytes matched) 0/0
(depth/total drops/no-buffer drops) 0/0/0
Class-map: class-default (match-any)
5852822852 packets, 2831145180567 bytes
5 minute offered rate 166000 bps, drop rate 0 bps
Match: any
Queueing
Output Queue: Conversation 269
Bandwidth 50 (%)
Bandwidth 5000 (kbps)
(pkts matched/bytes matched) 105233986/142641962552
(depth/total drops/no-buffer drops) 0/501925/0
exponential weight: 9
mean queue depth: 0
class Transmitted Random drop Tail drop Minimum Maximum Mark
pkts/bytes pkts/bytes pkts/bytes thresh thresh prob
0 1105641648/2794882281968 298313/374809101 202374/205299392 20 40 1/10
1 150/18610 0/0 0/0 22 40 1/10
2 37/2146 0/0 0/0 24 40 1/10
3 73000/39388395 1/1518 0/0 26 40 1/10
4 53/3074 0/0 0/0 28 40 1/10
5 7677849/1331363548 8/848 18/2300 30 40 1/10
6 443960666/34311937031 350/24155 861/58784 32 40 1/10
7 330/34973 0/0 0/0 34 40 1/10
rsvp 0/0 0/0 0/0 36 40 1/10
03-18-2014 04:58 AM
Disclaimer
The Author of this posting offers the information contained within this posting without consideration and with the reader's understanding that there's no implied or expressed suitability or fitness for any purpose. Information provided is for informational purposes only and should not be construed as rendering professional advice of any kind. Usage of this posting's information is solely at reader's own risk.
Liability Disclaimer
In no event shall Author be liable for any damages whatsoever (including, without limitation, damages for loss of use, data or profit) arising out of the use or inability to use the posting's information even if Author has been advised of the possibility of such damage.
Posting
Okay, regardless of what the show interface shows for queuing method, you have an active CBWFQ policy on the interface.
06-06-2018 07:07 AM
The best way to go with this is to apply the marking on your incoming interface from the LAN. This will all the scheduler to service packets correctly then pass them to the outgoing interface. You will see FIFO on the outgoing interface until you apply a queueing strategy like Policing or Shaping.
Hope this helps
Sy
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: