Hi all
"qos pre-classify" is used to apply QoS before encryption/tunneling. By
default the ToS field is copied to the GRE , AH and ESP header and QoS can
be applied on these headers. But the problem comes
when we need to classify and apply QoS based on parameters other than ToS.
Since packets are encrypted, QoS can't be performed. This is were "qos
pre-classify" come into picture. Basically it does
QoS before encryption.
You can apply "qos pre-classify" to a Tunnel interface and crypto map.
I have two queries:
1) Was the "qos pre-classify" option given in the tunnel interface to
support pre-IP header QoS for the legacy GREoIPSec where we applied to
crypto maps on both tunnel and physical interface
or is it for the IPSec profile based GREoIPSec VPNs like DMVPN? In
other word will "qos pre-classify" work for DMVPN?
2) In the latest images, we can also apply the QoS service policy to tunnel
interface. As we can apply the service-policy to the tunnel interface, the
"qos pre-classify" is not more required to be
configured on the tunnel interfaces right?
With regards
Kings
_______________________________________________
For more information regarding industry leading CCIE Lab training, please visit
www.ipexpert.com
