04-10-2007 05:21 PM - edited 03-03-2019 04:29 PM
Hi,
When I apply QoS configuration, 7206 router generates input errors on ingress Ethernet interface (fa1/1). Does anybody have similar experience?
QoS setting:
policy-map Outbound-Queuer
description Provides outbound queuing.
class Routing
bandwidth percent 4
random-detect dscp-based
class Mission-Critical-Data
bandwidth percent 10
random-detect dscp-based
class Transactional-Data
bandwidth percent 30
random-detect dscp-based
class Network-Management
bandwidth percent 5
random-detect dscp-based
class Bulk-Data
bandwidth percent 10
random-detect dscp-based
class Scavenger
bandwidth percent 1
random-detect dscp-based
class Proxy
bandwidth percent 15
random-detect dscp-based
class class-default
fair-queue
random-detect dscp-based
policy-map Outbound-Queuer-Shaper
class class-default
shape average 1000000
service-policy Outbound-Queuer
policy-map Inbound-Marker
description Colours inbound traffic on a LAN interface.
class Routing
set ip dscp cs6
class Mission-Critical-Data
set ip dscp 25
class Transactional-Data
set ip dscp af21
class Network-Management
set ip dscp cs2
class Bulk-Data
set ip dscp af11
class Scavenger
set ip dscp cs1
class Proxy
set ip dscp af43
class class-default
set ip dscp default
interface FastEthernet1/0
service-policy output Outbound-Queuer-Shaper
!
interface FastEthernet1/1
service-policy input Inbound-Marker
Errors:
Input queue: 0/75/61/0 (size/max/drops/flushes); Total output drops: 0
Queueing strategy: fifo
Output queue: 0/40 (size/max)
5 minute input rate 1265000 bits/sec, 1447 packets/sec
5 minute output rate 1624000 bits/sec, 1463 packets/sec
2098432647 packets input, 3156190990 bytes
Received 10899486 broadcasts, 0 runts, 0 giants, 0 throttles
26739 input errors, 0 CRC, 0 frame, 0 overrun, 26739 ignored
0 watchdog
0 input packets with dribble condition detected
Tried different IOS: C7200-JK9S-M), Version 12.4(8c) and (C7200-ADVENTERPRISEK9-M), Version 12.4(11)T1
Same problem.
04-10-2007 08:08 PM
Hi
Did you try to clear the counters and check ?
regds
04-10-2007 09:53 PM
Thanks for reply. I tried many times. Sometime the errors are up to 55k per hour.
Even I only applied QoS config in one interface. Eg. int fa1/1 service-policy input Inbound-Marker. No service-policy out on another interface.
It could be something to do IOS. The old 12.3-13 seems no that many input errors. However, there were more encryption type of errors.
Cheers,
Cheers.
04-11-2007 03:37 AM
Hi,
Which NPE are you using?
Is this a PA-2FE ? If so, watch out because the particular hardware is seriously troubled at handling sustained traffic and can exhibit problems like you are having. You should replace it with two single-port FE PA's.
This said, you might try to alleviate the problem doing a troubleshoot on input drops and possibly buffer tuning. See for a start:
http://cisco.com/en/US/products/hw/modules/ps2033/products_tech_note09186a00800d76e5.shtml
The document is titled for ATM but can be applied to all media.
Hope this helps, if so please rate post!
04-11-2007 05:44 PM
Thanks for reply. It is a PA-2FE. We have changed a new one. Also the input errors appear on the other router on different site. If no QoS, there is no error at all.
04-11-2007 06:13 PM
Hi, my previous comment about performance trouble was actually related to an older 2-FE card, so please ignore it.
I think you have CEF enabled ? Which NPE is that? Significant processing power is needed to process sizeable amount of traffic with a marking policy complex like your. Perhaps you could simplify it a little?
04-11-2007 07:51 PM
Hi, CEF has been enabled. It's NPE400. This is very strange case. Even I took out input marker from ingress interface and just applied service policy out on egress interface. It still generates input errors on ingress interface. If none of QoS config applied on both interfaces, then no errors on ingress interface at all. The egress interface has no error whatever QoS config applied or not.
04-11-2007 04:08 AM
The issue is with your Input Queue. The FIFO hardware buffer is getting saturated. You have applied a Policy map to the input of your interface. Try increasing the HOLD Queue IN on the Fast Ethernet. It is currently set for 75 packets. Set it for 125.
Interface Fast Ethernet 1/1
Hold-Queue in 125
Do not make this value too large it increases your final stage FIFO buffer. If too long then you will add too much delay, if too short you will still incur errors....Good Luck...
04-11-2007 05:48 PM
I have tried tunning buffers. Whatever I change the Hold-Queue size, it still generates errors. With old IOS, it didn't have so many input erros. I'll try down grade the IOS.
Many thanks,
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: