![]() ![]() Let’s see how this looks on the wire and at the DMVPN hub. This will show you the basics of the NHRP registration request. Neat eh? If you need a little refresher on NHRP registration please go to Fun in the Lab: Sniffer Tracing a DMVPN Tunnel Startup. ![]() Now what happens? Echo3 simply puts the name “spoke-2Mbps” into the NHRP registration request. So I simply go to Echo3 ( Branch_2) and put the command “ip nhrp group spoke-2Mbps” on the spoke’s tunnel interface. ![]() ![]() “On the DMVPN spoke configure the DMVPN interface with the mapped group name you’d like to have applied to it” “2) apply all the policies you are going to “offer” the spokes on the DMVPN tunnel interface via ip nhrp map group command” So basically what you can see above is that we are configuring our DMVPN hub to have 5 different QoS offerings to the spokes. “1) configure in the global config section the varying QoS policies you’d like the hub to “offer” as QoS policies for the spokes” On the DMVPN spoke configure the DMVPN interface with the mapped group name you’d like to have applied to it.apply all the policies you are going to “offer” the spokes on the DMVPN tunnel interface via ip nhrp map group command.configure in the global config section the varying QoS policies you’d like the hub to “offer” as QoS policies for the spokes.Since they are on the same mGRE tunnel how would we do that? We’d like to apply a QoS policy from Hub to Spoke for Branch_2 but not for Branch_1. Let’s say that Branch_1 and Branch_2 are on the same DMVPN tunnel with DMVPN Hub “ Foxtrot14“. Every time I show this to people I see eyes light up and little light bulbs turn on in their brains of where they can use this. Apparently it isn’t just me (as a lab rat) that thinks this is cool. There is this really cool thing about DMVPN that I came across a while back: DMVPN Per-Tunnel QoS. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |