I am configuring DMVPN with QoS using Per Tunnel QoS in HUBs.
The fact is that in the Per Tunnel QoS I have two policy-maps correlated. On the first one a class-default shaping the traffic. On the second level some classes with some WFQ policies associated. That is, a classic QoS policy.
The fact is that I have applied the parent policy to the corresponding Spoke group, and no error is shown. When I send the traffic I see that the policy is theoretically running well, that is, the first level captures all the traffic, and even the second level policies are applied.... But the problem is that the second level policy is applying correctly the pòlicies, but the traffic shaping is not limiting the traffic.
In order to detect if there was any problem in the config, I applied the same parent policy-map without changing anything to a physical interface, running everything OK, both, the WFQ policies, and now also the shaping.
So, something is happening when traffic shaping is applied in Per Tunnel QoS. Might it be a bug? I am using 15.1(1)T and 15.1(2)T1, and in both is the same problem
Login to the FXOS chassis manager.
Direct your browser to https://hostname/, and log-in using the user-name and password.
Go to Help > About and check the current version:
Check the current version availa...
We have configured the outside and inside Interface with official ipv6 adresses, set a default route on outside Interface to our router, we also have definied a rule , which also gets hits, to permit tcp from inside Interface to any6.
In Syslog I also se...