The esw modules do not have any qos features. There's no need to use
access lists because traffic entering the esw will not be remarked - the
default (and only) l2 option is to trust the markings received from the
switch ports. For lan qos focus on the 3750.
On a slightly related note there are other things to mark on site b and c
routers you can use ip qos dscp cs3 sig inside voip dial peers, prefix
mgcp to that for mgcp signalling, and use sccp ip precedence 3 for sccp
traffic. That should handle signaling markings from router-generated
traffic (default for these is af31). Other option is to use acl/nbar to
mark traffic.
On Oct 29, 2013 1:01 PM, StefanoS stefan...@gmail.com wrote:
...in other words to trust or not to trust incoming traffic from phones
connected to the 4ESW modules. I think to be at the safe side we should use
access lists. But there's more configuration to be done (not if you use
auto qos and FRF.12 LFI)
Thanks,
Stefanos
On Tue, Oct 29, 2013 at 6:47 PM, StefanoS stefan...@gmail.com wrote:
Hello all.
What do you think is the best practice approach in the lab exam?
Using mls qos trust commands on the 4ESW phone ports where the phones are
connected (trusted devices) or use access lists for classification and
marking and then applying accordingly to the policy?
Thanks you,
Stefanos
___
For more information regarding industry leading CCIE Lab training, please
visit www.ipexpert.com
Are you a CCNP or CCIE and looking for a job? Check out
www.PlatinumPlacement.com
___
For more information regarding industry leading CCIE Lab training, please visit
www.ipexpert.com
Are you a CCNP or CCIE and looking for a job? Check out
www.PlatinumPlacement.com
