Hi Adam, Can you send me your complete QOS configuration? Also what is your desired policy so that I can try in my lab?
Best Regards, [http://www.cisco.com/web/europe/images/email/signature/horizontal06.jpg] Waris Sagheer Technical Marketing Manager Service Provider Access Group [email protected]<mailto:[email protected]> Phone: +1 408 853 6682 Mobile: +1 408 835 1389 CCIE - 19901 <http://www.cisco.com/> [Think before you print.] Think before you print. 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 <[email protected]<mailto:[email protected]>> Date: Monday, October 7, 2013 7:49 AM To: Waris Sagheer <[email protected]<mailto:[email protected]>>, "[email protected]<mailto:[email protected]>" <[email protected]<mailto:[email protected]>> Subject: RE: [c-nsp] me3600 Can NOT match ACL in an output policy-map Hi Folks, Just gave the workaround a try in the lab and figured out that it’s not applicable to our case unfortunately. It appears that if hierarchical QOS is used -than only one class is possible in parent policy (i.e. the class class-default). The below is not supported: policy-map per_customer_shape class customer_1 shape average 5120000 service-policy prioritize_voip class customer_2 shape average 1280000 service-policy prioritize_voip You can do this only once -that is with class class-default. So simple shaping yes, but no hierarchy. I have also tried to 3 level hierarchy with grand-parent policy with just class-default where a shaped at some speed and called service policy per_customer_shape -but I hit same error. adam From: Waris Sagheer (waris) [mailto:[email protected]] Sent: Thursday, October 03, 2013 11:56 PM To: Adam Vitkovsky; [email protected]<mailto:[email protected]> Subject: Re: [c-nsp] me3600 Can NOT match ACL in an output policy-map Hi Adam, ME does not support ACL match in the egress policy and there is no plan to support it. However you can use the workaround "ACLs can be matched in ingress policies and set qos-group. The qos-group can be matched in egress policies". Best Regards, [Image removed by sender.] Waris Sagheer Technical Marketing Manager Service Provider Access Group [email protected]<mailto:[email protected]> Phone: +1 408 853 6682 Mobile: +1 408 835 1389 CCIE - 19901 [Image removed by sender. Think before you print.] Think before you print. 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: Waris Sagheer <[email protected]<mailto:[email protected]>> Date: Wednesday, October 2, 2013 8:54 AM To: adam vitkovsky <[email protected]<mailto:[email protected]>>, "[email protected]<mailto:[email protected]>" <[email protected]<mailto:[email protected]>> Subject: Re: [c-nsp] me3600 Can NOT match ACL in an output policy-map Hi Adam, Let me get back to you on this. Best Regards, [http://www.cisco.com/web/europe/images/email/signature/horizontal06.jpg] Waris Sagheer Technical Marketing Manager Service Provider Access Group [email protected]<mailto:[email protected]><mailto:[email protected]> Phone: +1 408 853 6682 Mobile: +1 408 835 1389 CCIE - 19901 <http://www.cisco.com/> [Think before you print.] Think before you print. 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 <[email protected]<mailto:[email protected]><mailto:[email protected]><mailto:[email protected]%3e>> Date: Wednesday, October 2, 2013 12:37 AM To: "[email protected]<mailto:[email protected]><mailto:[email protected]><mailto:[email protected]%3e>" <[email protected]<mailto:[email protected]><mailto:[email protected]><mailto:[email protected]%3e>> Subject: [c-nsp] me3600 Can NOT match ACL in an output policy-map Hi Waris, folks, Is the ACL match in an output policy-map a hardware limitation or is there a plan to add this feature in future releases please? Or how do you folks work around this limitation please? Thank you. adam _______________________________________________ cisco-nsp mailing list [email protected]<mailto:[email protected]><mailto:[email protected]> https://puck.nether.net/mailman/listinfo/cisco-nsp archive at http://puck.nether.net/pipermail/cisco-nsp/ _______________________________________________ cisco-nsp mailing list [email protected]<mailto:[email protected]> https://puck.nether.net/mailman/listinfo/cisco-nsp archive at http://puck.nether.net/pipermail/cisco-nsp/ _______________________________________________ cisco-nsp mailing list [email protected] https://puck.nether.net/mailman/listinfo/cisco-nsp archive at http://puck.nether.net/pipermail/cisco-nsp/
