[c-nsp] MPLS QOS on ME3600 not working???

Pete Lumbis alumbis at gmail.com
Wed Nov 13 08:35:00 EST 2013 

This is similar, but not the right bug. This bug is fixed in the 15.3.3S
train and it is specific to class-map ACLs that are matching on L4 ports.
In Adam's case we are on later code and there are no ACLs matching L4 ports.

I've updated the release note to indicate the requirement of L4 information
in the ACL, it should change on cisco.com tomorrow.

-Pete


On Wed, Nov 13, 2013 at 5:43 AM, Shawn Nolan <
shawn.nolan at convergencegroup.co.uk> wrote:

> This is a bug. We ran into the same one a while back when we performed a
> IOS upgrade.
>
> I believe this is the code CSCug39331
>
> Options are. Upgrade to a newer release or straight from TAC:
>
> "If moving to later release is not an option, you could consider the below
> workaround for this issue which we tested already. This will make it a L4
> ACL policy case internally and should work as expected.
>
> Add a dummy class-map matching on L4 ACL to the same policymap. (class
> matching none of the traffic streams so that actual classes are not
> affected)
>
> Class Map match-all tcpudp (id 51)
>    Match access-group name tcpudp
>
> Extended IP access list tcpudp
>     10 permit tcp host 1.2.3.4 any
> "
>
>
>
> -----Original Message-----
> From: cisco-nsp [mailto:cisco-nsp-bounces at puck.nether.net] On Behalf Of
> Waris Sagheer (waris)
> Sent: 12 November 2013 19:10
> To: Adam Vitkovsky; cisco-nsp at puck.nether.net
> Subject: Re: [c-nsp] MPLS QOS on ME3600 not working???
>
> Hi Adam,
> Did you work with TAC or BU on this issue? Can you send me your
> configuration so that I can take a look at it. I need to class-maps and
> policies as well as the interface configuration.
>
> Best Regards,
>
> [http://www.cisco.com/web/europe/images/email/signature/horizontal06.jpg]
>
> Waris Sagheer
> Technical Marketing Manager
> Service Provider Access Group (SPAG)
> waris at cisco.com<mailto:waris at cisco.com>
> Phone: +1 408 853 6682
> Mobile: +1 408 835 1389
>
> CCIE - 19901
>
>
> <http://www.cisco.com/>
>
>
>
> This email may contain confidential and privileged material for the sole
> use of the intended recipient. Any review, use, distribution or disclosure
> by others is strictly prohibited. If you are not the intended recipient (or
> authorized to receive for the recipient), please contact the sender by
> reply email and delete all copies of this message.
>
> For corporate legal information go to:
> http://www.cisco.com/web/about/doing_business/legal/cri/index.html
>
>
>
> From: adam vitkovsky <adam.vitkovsky at swan.sk<mailto:adam.vitkovsky at swan.sk
> >>
> Date: Tuesday, November 12, 2013 5:39 AM
> To: "cisco-nsp at puck.nether.net<mailto:cisco-nsp at puck.nether.net>" <
> cisco-nsp at puck.nether.net<mailto:cisco-nsp at puck.nether.net>>
> Subject: [c-nsp] MPLS QOS on ME3600 not working???
>
> Hi Folks,
>
> Is anyone using MPLS QOS on ME3600 platform please or I am the only one
> hitting the issue?
> As seen below all traffic is matched into the first class defined in the
> policy-map no matter how the packets are marked.
> If I would remove the class core_class7 from the policy-map (and might
> have then add it back so that it would appears at the bottom) all the
> traffic is going to be matched by the next class that happens to be at the
> top of the policy-map which would be core_class6 and so on and so on.
> This is seen on all boxes and across couple of different IOS versions.
>
> Somehow I fail to convince Cisco that my MPLS traffic patterns are not
> changing from EXP7/Prec7 to EXP6/Prec6 to ... miraculously as I'm changing
> the inbound policy-map on some random PE even though I showed them that the
> neighboring P-core sees a variety of EXP5 to EXP1 marked packets in output
> policy-maps in direction towards the ME3600.
>
> sh policy-map int te0/1 in
> TenGigabitEthernet0/1
>
>   Service-policy input: core_policy_ver5.0_input
>
>     Class-map: core_class7 (match-any)
>       74193994 packets, 7015406412 bytes
>       30 second offered rate 33000 bps, drop rate 0000 bps
>       Match: mpls experimental topmost 7
>       Match:  precedence 7
>         set qos-group 7
>         set discard-class 7
>
>     Class-map: core_class6 (match-any)
>       0 packets, 0 bytes
>       30 second offered rate 0000 bps, drop rate 0000 bps
>       Match: mpls experimental topmost 6
>       Match:  precedence 6
>       Match: access-group name AL_BFD
>         set qos-group 6
>         set discard-class 6
>
>     Class-map: core_class5 (match-any)
>       0 packets, 0 bytes
>       30 second offered rate 0000 bps, drop rate 0000 bps
>       Match: mpls experimental topmost 5
>       Match:  precedence 5
>         set qos-group 5
>         set discard-class 5
>
>     Class-map: core_class4 (match-any)
>       0 packets, 0 bytes
>       30 second offered rate 0000 bps, drop rate 0000 bps
>       Match: mpls experimental topmost 4
>       Match:  precedence 4
>         set qos-group 4
>         set discard-class 4
>
>     Class-map: core_class3 (match-any)
>       0 packets, 0 bytes
>       30 second offered rate 0000 bps, drop rate 0000 bps
>       Match: mpls experimental topmost 3
>       Match:  precedence 3
>         set qos-group 3
>         set discard-class 3
>
>     Class-map: core_class2 (match-any)
>       0 packets, 0 bytes
>       30 second offered rate 0000 bps, drop rate 0000 bps
>       Match: mpls experimental topmost 2
>       Match:  precedence 2
>         set qos-group 2
>         set discard-class 2
>
>     Class-map: core_class1 (match-any)
>       0 packets, 0 bytes
>       30 second offered rate 0000 bps, drop rate 0000 bps
>       Match: mpls experimental topmost 1
>       Match:  precedence 1
>         set qos-group 1
>         set discard-class 1
>
>     Class-map: class-default (match-any)
>       0 packets, 0 bytes
>       30 second offered rate 0000 bps, drop rate 0000 bps
>       Match: any
>         set qos-group 0
>         set discard-class 0
>
>
>
> adam
>
> _______________________________________________
> cisco-nsp mailing list  cisco-nsp at puck.nether.net<mailto:
> cisco-nsp at puck.nether.net>
> https://puck.nether.net/mailman/listinfo/cisco-nsp
> archive at http://puck.nether.net/pipermail/cisco-nsp/
>
> _______________________________________________
> cisco-nsp mailing list  cisco-nsp at puck.nether.net
> https://puck.nether.net/mailman/listinfo/cisco-nsp
> archive at http://puck.nether.net/pipermail/cisco-nsp/
>
> ______________________________________________________________________
> This email has been scanned by the Symantec Email Security Cloud System,
> Managed and Supported by TekNet Solutions (http://www.teknet.co.uk)
> ______________________________________________________________________
>
> ______________________________________________________________________
> This email has been scanned by the Symantec Email Security Cloud System,
> Managed and Supported by TekNet Solutions (http://www.teknet.co.uk)
> ______________________________________________________________________
>
> _______________________________________________
> cisco-nsp mailing list  cisco-nsp at puck.nether.net
> https://puck.nether.net/mailman/listinfo/cisco-nsp
> archive at http://puck.nether.net/pipermail/cisco-nsp/
>

More information about the cisco-nsp mailing list