>> If I mark a packet with qos-group 1 and that packet goes to the other end directly connected router, will that router also see this packet with qos-group 1 or not?
No, qos-group is an internal tag in a node and it is not exported in the outgoing packet.
There are some scenarios when you mark the qos-group at an ingress interface and then on the outgoing interface you have a policy-map outbound that performs some actions on traffic classes defined on the qos-group basis.
The QoS group value is local to the router, meaning that the QoS group value that is marked on a packet does not leave the router when the packet leaves the router. If you need a marking that resides in the packet, use IP precedence setting, IP differentiated services code point (DSCP) setting, or another method of packet marking.
I'm looking to deploy QoS for DMVPN network at the hub site and is referring to the Cisco DMVPN design document has a sample how to do it.
My question is that in the sample, the criterion for classify traffic into different spoke site is based on static pre-configured prefixes. But I would like it to be route based. Is there a way to do it? Please look at the QoS section at the document below.
On the headend hub router, the mGRE tunnel interface is configured for qos pre-classify because the service policy is matching on the destination IP address in the original unencrypted IP header. The service policy, however, is applied to the outside interface, and the packets are encrypted when the QoS matching decision is invoked. Configuring qos pre-classify gives the service policy the ability to match on the clear text values.
description Outside interface
This is from page 49 of the document in your link.
Normally, a DiffServ Model is used with some traffic classes based on the DSCP field with some well-known settings like EF for VoIP bearer channels (conversations)
I see that there is also an example based on destination address with ip access-lists. This can be helpful if your address plan allows to identify some services with some type of destinations
This directly maps to the routing table in a static way.
However, the scheduler you can use is elastic resources not used are redistributed between the other traffic classes.
So we can say there is not a strict need to be able to map to the routes in a "dynamic way".
If you look at the QoS command reference we can see that among the many parameters/options of the match commands there are no attribute of dynamic routes.
One could think to match a route tag or other route property but all the commands for setting and for matching a route tag are available only in route-maps and not within class-map objects.
So as far as I know QoS objects are oriented to traffic flows and you have a choice between using in-band markings like DSCP in DiffServ model or you can classify the flows based on the destination address but referencing them directly with ACLs
I am trying to do exactly that - mark qos-group on the incoming and use that on the outgoing on the same router. The problem I am facing is that the outgoing policy does not seem to be picking up the qos-group internal markings. When I view the output of the outgoing policy, I do not see any hits against the policies which are using qos-groups. I am using a ME3800X to do this.
Have been going though the soft conf guide but cannot seem to figure out why this is not behaving as detailed in the guide.
I wanted to find out if you have experience of using qos-group and came across such a situation.
We are pleased to announce availability of Beta software for 16.6.3.
16.6.3 will be the second rebuild on the 16.6 release train targeted
towards Catalyst 9500/9400/9300/3850/3650 switching platforms. We are
looking for early feedback from customers befor...
Introduction Featured Speakers Luis Espejel is the Telecommunications
Manager of IENova, an Oil & Gas company. Currently he works with Cisco
IOS® and Cisco IOS XE platforms, and NX to some extent. He has also
worked as a Senior Engineer with the Routing P...
In this session you can learn more about Layer 3 multicast and the best
practices to identify possible threats and take security measures. It
provides an overview of basic multicast, the best security practices for
use of this technology, and recommendati...