cancel
Showing results for 
Search instead for 
Did you mean: 
cancel
1045
Views
5
Helpful
3
Replies

Queuing not working on 9300

ccosgb
Level 1
Level 1

Hello.

There are cisco 9300 switches connected via etherchannel.

Service-policy queuing does not work on output. Or statistics are not displayed.

The settings on the switch are identical, traffic and telephony pass through them exactly
and the one in the ACL.

There are hits in the statistics for input the service policy,
But on both switches, the output is generally zero-based,
even in class-default. (0 packets hits)

Even if the traffic does not fall under the match, there should be statistics
for the default class.

Tried and set cos 5, match cos 5 instead of qos-group 3 on both switches.


Why are there no hits? (0 packets hits)?

---------------------------------------------------------------------

Конфигурация:

ip access-list extended qos_10_10_acl
10 permit tcp host 192.168.x.y 10.200.x.y 0.0.0.63 eq 1521
20 permit tcp 10.200.x.y 0.0.0.63 eq 1521 host 192.168.x.y

class-map match-any qos_10_10_class
match access-group name qos_10_10_acl

policy-map qos_policy_input
class qos_10_10_class
set qos-group 3


class-map match-all qos_rtp_class
match dscp EF

class-map match-all qos_cos5_class
match qos-group 3

policy-map qos_policy_output
class qos_rtp_class
priority level 1 percent 10
class qos_cos5_class
priority level 2 percent 20
class class-default
bandwidth remaining percent 100
queue-limit 25 packets
random-detect


и на транковых портах:
service-policy input qos_policy_input
service-policy output qos_policy_output

---------------------------------------------------------------------

 


c9300# show policy-map interface Ten 1/1/1


Service-policy input: qos_policy_input

Class-map: qos_10_10_class (match-any)
32985283 packets
Match: access-group name qos_10_10_acl
QoS Set
qos-group 3

Class-map: class-default (match-any)
786617977 packets
Match: any

Service-policy output: qos_policy_output

queue stats for all priority classes:
Queueing
priority level 1

(total drops) 0
(bytes output) 0

queue stats for all priority classes:
Queueing
priority level 2

(total drops) 0
(bytes output) 0

Class-map: qos_rtp_class (match-all)
0 packets
Match: dscp ef (46)
Priority: 10% (1000000 kbps), burst bytes 25000000,

Priority Level: 1

Class-map: qos_cos5_class (match-all)
0 packets
Match: qos-group 3
Priority: 20% (2000000 kbps), burst bytes 50000000,

Priority Level: 2

Class-map: class-default (match-any)
0 packets
Match: any
Queueing
queue limit 25 packets
(total drops) 0
(bytes output) 0
bandwidth remaining 100%


AFD WRED STATS BEGIN
Virtual Class min/max Transmit Random drop AFD Weight


0 0 / 0 (Byte)0 0 0
(Pkts)0 0
precedence :


1 0 / 0 (Byte)0 0 0
(Pkts)0 0
precedence :


2 0 / 0 (Byte)0 0 0
(Pkts)0 0
precedence :

Total Drops(Bytes) : 0

Total Drops(Packets) : 0
AFD WRED STATS END

3 Replies 3

Joseph W. Doherty
Hall of Fame
Hall of Fame

NB: I have no actual experience with 9300s, so what I suggest might not work.

BTW, you do realize an ingress and egress policy on the same interface doesn't "impact" the same traffic.  I.e. an ingress policy on one interface doing QoS classification is not used by the egress policy on the same interface.

Anyway, try the following:

ip access-list extended qos_10_10_acl
!insure source and destination are correct for applied interface
10 permit tcp host 192.168.x.y 10.200.x.y 0.0.0.63 eq 1521
20 permit tcp 10.200.x.y 0.0.0.63 eq 1521 host 192.168.x.y

class-map match-any qos_10_10_class
match access-group name qos_10_10_acl

class-map match-all qos_rtp_class
match dscp EF

policy-map qos_policy_output
class qos_rtp_class
priority level 1 percent 10
class qos_10_10_class
priority level 2 percent 20
class class-default
bandwidth remaining percent 100

interface x
service-policy output qos_policy_output

I tried splitting ingress and egress policy into different interfaces. Ingress mark - set to trunked ports, egress queue set to server access port. The result is the same - i don't see any hits in egress policy-map.

Even class-default has no hits. And they should be in any case.

 

Yea, not getting any hits on class-default is strange, although that was a common issue on the earlier 3750s.  For those, you had to issue additional commands to see QoS stats tied to the hardware (the ASICs).  I.e., those stats were not reflected at the higher interface "software" level.  (I'm unsure, but Cisco might have eventually updated their IOS, in later versions, to pull the ASIC stats into the interface stats.  Possibly a similar issue with your 9300.  Do you have a support contract for the device?)