For all egress traffic, PFC QoS uses a configurable map to derive a CoS value from the final internal DSCP value associated with the traffic.
I understand, but what if your port is native? (ie. without 802.1p,
means without cos??) How does the router classify from unexisting cos?
Thanks for the good references.
Jerome
I do run MPLS in the core for VPN services. The core interfaces are
in mode "no switchport" and are untagged as well (routed ports on 10GE
interfaces). Here too, what happens if I have cos based queueing (as
this is native ethernet)? What happens if I run DSCP based queueing (as
this is MPLS, can dscp be used?) My goal here is more to make sure that
my qos does not break anything.
For received Layer 3 MPLS packets, the PFC usually trusts the EXP value in the received topmost label. None of the following have any effect on MPLS packets:
Interface trust state
Port CoS value
Policy-map trust command
Actually, there are a lot of information. I hope that these links will be
usefull:
1)
http://www.cisco.com/en/US/docs/routers/7600/ios/12.2SR/configuration/guide/qos.html
2)
http://www.cisco.com/en/US/docs/routers/7600/ios/12.2SR/configuration/guide/mplsqos.html
Best regards,
Olga.
--
-------------------------------------------------------------
Jerome Durand
Responsable des services aux usagers
Services operations & support manager
Réseau National de Télécommunications
pour la Technologie, l'Enseignement et la Recherche
Tel: +33 (0) 1 53 94 20 40 | GIP RENATER
Fax: +33 (0) 1 53 94 20 41 | c/o ENSAM
E-mail: [email protected] | 151 Boulevard de l'Hôpital
http://www.renater.fr | 75013 PARIS
--------------------------------------------------------------
_______________________________________________
cisco-nsp mailing list [email protected]
https://puck.nether.net/mailman/listinfo/cisco-nsp
archive at http://puck.nether.net/pipermail/cisco-nsp/
