From: Petr Lapukhov (petrsoft@gmail.com)
Date: Sun May 28 2006 - 14:28:47 ART
Pierre,
Monitoring MLS QoS on 3550 is a bit complicated and somewhat limited in
functionality.
1) You can monitor either bytes/or packets statistic
(bytes is the default). You need to configure that command on
"master" port:
SW1(config-if)#mls qos monitor bytes
QoS: This command is only applicable on a master port.
On a 24 ports switch:
-port 1 controls interface 1 to 12
-port 13 controls interface 13 to 24
On a 48 ports switch:
-port 25 controls interface 25 to 36
-port 37 controls interface 37 to 48
2) You need to specify dscp to collect statistics on (up to 8 values)
interface FastEthernet0/2
service-policy input MARK
mls qos monitor dscp 11
3) You may verify results with:
SW1#show mls qos interface fastEthernet 0/2 statistics
FastEthernet0/2
Ingress
dscp: incoming no_change classified policed dropped (in pkts)
11: 0 0 5 0 0
Others: 285 280 0 0 0
Egress
dscp: incoming no_change classified policed dropped (in pkts)
11: 0 n/a n/a 0 0
Others: 1467 n/a n/a 0 0
----Citing the DocCD:
Do not use the *show policy-map interface* privileged EXEC command to display classification information for incoming traffic. The *interface* keyword is not supported, and you should ignore the statistics shown in the display. Instead, you should specify the DSCPs to be monitored by using the *mls qos monitor dscp* *dscp1 ... dscp8*interface configuration command, and then you should use the *show mls qos interface* *interface-id * *statistics* privileged EXEC command. For more information about these commands, see the command reference for this release.
HTH Petr 2006/5/28, Pierre-Alex <paguanel@hotmail.com>: > > Thanks Petr, > > My traffic is being marked on R5 > > However the counters on the switch are not incrementing. > > Is this a bug, or is it normal (i.e. the counters only work in the > outbound > direction)? > > > ----- Original Message ----- > From: Petr Lapukhov > To: Pierre-Alex > Cc: ccielab@groupstudy.com > Sent: Sunday, May 28, 2006 6:40 PM > Subject: Re: QoS DSCP marking inbound 3550 > > > Pierre, > > Basically, you cannot classify/mark traffic with class-default on 3550. > At least, it did not work with me :) > > You need to match ip packets witch IP access-list, e.g. > > class IP > match access-group 100 > > access-list 100 permit ip any any > > policy-map MARK > class IP > set ip dscp 11 > > HTH > Petr > > > 2006/5/28, Pierre-Alex <paguanel@hotmail.com>: > I am trying to accomplish the following (apparently very basic): > > > Diagram: > > R5 --------------(fa0/5)---Switch--(fa0/4)------------------R4 > > > Task: > > On switch2 mark all packets coming from R5 with af11. > Do this on port fa 0/5 > > > Configs: > > On Switch: > > interface FastEthernet0/5 > switchport access vlan 34 > switchport mode access > service-policy input r5-i > > policy-map r5-i > class class-default > set dscp 11 > > > Verification: > > I am pinging R4 from R5 and checking the dscp received using a > class-map > on > R4 > As you can see, no packet is marked > > On R4 > > r4#sh policy-map interface > Ethernet0/1.34 > > Service-policy input: marking > > Class-map: af11 (match-all) > 0 packets, 0 bytes > 30 second offered rate 0 bps > Match: ip dscp af11 (10) > > Class-map: class-default (match-any) > 1006859 packets, 118805079 bytes > 30 second offered rate 408000 bps, drop rate 0 bps > Match: any > > Please note that configuring "mls qos trust dscp" removes the service > policy > from the interface . So adding this command does not solve the problem > > Any idea? > > Thanks > > Pierre > > > _______________________________________________________________________ > Subscription information may be found at: > http://www.groupstudy.com/list/CCIELab.html > > _______________________________________________________________________ > Subscription information may be found at: > http://www.groupstudy.com/list/CCIELab.html
This archive was generated by hypermail 2.1.4 : Thu Jun 01 2006 - 06:33:22 ART