You are here
SEC0005 - DMVPN Interesting Traffic and Per-Tunnel QoS
Difficulty Level:
Lab Document:
<Please login to see the content>
Category:
Security
The first half of the video shows you how to specify an interesting traffic that will cause a DMVPN spoke-to-spoke tunnel to be initiated, and utilized. In the second half, we will look at an ability to configure per-tunnel QoS from hub to spokes using NHRP group.
Sometimes, it might be desirable to allow spokes to communicate directly to one another for only certain type of traffic, for example VOIP to minimize latency, while still routing other applications through hub for access control.
Conventionally, having a single tunnel interface at the DMVPN hub allows only one QoS policy to be applied outbound to spokes. With NHRP 'map group' feature, you are able to group spokes with similar requirements together and apply unique QoS policy per group, while the policy actually takes effect on per-spoke basis.
Topic includes
- DMVPN interesting traffic matching for Spoke-to-Spoke tunnel
- DMVPN per-tunnel QoS policy
Quick Fact:
- 'nhrp map group' was introduced in 12.4(22)T
About Author
Metha Chiewanichakorn, CCIE#23585 (Ent. Infra, Sec, SP), is a Cisco networking enthusiast with years of experience in the industry. He is currently working as a consulting engineer for a Cisco partner. As a founder of and an instructor at labminutes.com, Metha enjoys learning and challenges himself with new technologies.