- A virtual community of network engineers
 Home  BookStore  StudyNotes  Links  Archives  StudyRooms  HelpWanted  Discounts  Login
RE: Traffic Shaping and LLQ on MSFC's and RSM's [7:61575] posted 01/23/2003
[Chronological Index] [Thread Index] [Top] [Date Prev][Date Next] [Thread Prev][Thread Next]

Once I tried to use LLQ on the MSFC to priorize audio multicast traffic.

The command 'sh mls ip multicast' (a tip from a groupstudy guy) showed that
the multicast traffic was going through the PFC, so the LLQ was not

"John Humphrey" em 22/01/2003 19:47:44

Favor responder a "John Humphrey" 

Enviado Por:      nobody@xxxxxxxxxxxxxx

Para:  cisco@xxxxxxxxxxxxxx

Assunto:    RE: Traffic Shaping and LLQ on MSFC's and RSM's [7:61575]

I've encountered this issue in our production environment with policy-maps.
Here's the answer Cisco's TAC gave me. Since the msfc interfaces are
software based, the MLS engine will bypass the route processor on most of
your layer 3 packets. This prevents the shaping/policing policy from being
applied on all egress traffic. You can, however, successfully apply the
policies to all ingress traffic because it must travel thru the Layer 3
process before it is sent to the destination node. So, if you're applying a
service-policy to a msfc interface it must be applied with "input" as the
direction. I'm not sure what effect disabling MLS would have on this
but I'm sure the benefits (if there would be any) would not be worth it.
can however use QoS policies on the layer 2 modules with acl mapping to
achieve much of the same benefits.


Message Posted at:
FAQ, list archives, and subscription info:
Report misconduct and Nondisclosure violations to abuse@xxxxxxxxxxxxxx