DMVPN QOS in HUB

[waleedmatter]

I have DMVPN QOS implemeted in one tunnel associated with one physical ISP and it worked fine between the HUB and spoke , my question there will be new ISP will connect the hub and new tunnel will create it so my question can i use the same group names which i am using with the existing tunnel with the new tunnel or not 

interface tunnel 70(existing)
ip nhrp map group 1M-SPOKES service-policy output 1M-SPOKES
ip nhrp map group 2M-SPOKES service-policy output 2M-SPOKES
ip nhrp map group 3M-SPOKES service-policy output 3M-SPOKES
ip nhrp map group 4M-SPOKES service-policy output 4M-SPOKES
ip nhrp map group 5M-SPOKES service-policy output 5M-SPOKES
ip nhrp map group 6M-SPOKES service-policy output 6M-SPOKES
ip nhrp map group 7M-SPOKES service-policy output 7M-SPOKES
ip nhrp map group 8M-SPOKES service-policy output 8M-SPOKES
ip nhrp map group 9M-SPOKES service-policy output 9M-SPOKES
ip nhrp map group 10M-SPOKES service-policy output 10M-SPOKES
ip nhrp map group 11M-SPOKES service-policy output 11M-SPOKES
ip nhrp map group 12M-SPOKES service-policy output 12M-SPOKES
ip nhrp map group 16M-SPOKES service-policy output 16M-SPOKES
ip ip nhrp attribute group To-Hub
!
!
interface tunnel 20(new one)
ip nhrp map group 1M-SPOKES service-policy output 1M-SPOKES
ip nhrp map group 2M-SPOKES service-policy output 2M-SPOKES
ip nhrp map group 3M-SPOKES service-policy output 3M-SPOKES
ip nhrp map group 4M-SPOKES service-policy output 4M-SPOKES
ip nhrp map group 5M-SPOKES service-policy output 5M-SPOKES
ip nhrp map group 6M-SPOKES service-policy output 6M-SPOKES
ip nhrp map group 7M-SPOKES service-policy output 7M-SPOKES
ip nhrp map group 8M-SPOKES service-policy output 8M-SPOKES
ip nhrp map group 9M-SPOKES service-policy output 9M-SPOKES
ip nhrp map group 10M-SPOKES service-policy output 10M-SPOKES
ip nhrp map group 11M-SPOKES service-policy output 11M-SPOKES
ip nhrp map group 12M-SPOKES service-policy output 12M-SPOKES
ip nhrp map group 16M-SPOKES service-policy output 16M-SPOKES
ip ip nhrp attribute group To-Hub

[Giuseppe Larosa]

Hello @waleedmatter ,

I think you can re-use the same names for the policy map shapers I'm not sure you can re-use the NHRP group names. It is likely. I would expect it.

I would suggest you to use a different NHRP ID in each tunnel even if second tunnel exits to a different physical interface to a second new ISP.

For making the configuration more readable you might use different names addind a "2 " or "20" at the end of each group name on mGRE tunnel 20.

Hope to help

Giuseppe

[waleedmatter]

Hi@Giuseppe Larosa 

It is difficult to use different names because this will need the name of it in the all the branches because we have another site has two Hub routers and each one has one ISP and all branches connected to it recently we added this site but it has only one HUB router with two ISP physical interfaces 

[Giuseppe Larosa]

Hello @waleedmatter ,

try to re-use the same names then.

Hope to help

Giuseppe

[waleedmatter]

The router didn't deliver yet , this is why i asked the question here because maybe any one implemented it 

[Elliot Dierksen]

If your service policy will be the same on the new provider, I would go along with @Giuseppe Larosa and say you should use the same names. If the service policy towards the spokes on the new provider are going to use different service policies then you need different names.

[waleedmatter]

The same policies will be the same in the two ISP to avoid any change in the spokes , my question very simple , can i use the same group names in the two tunnel 20 , 70 in the same  new Hub router or not ?

In the current setup 

HUB-1--(tunnel20)----------ISP-1-----------Spokes

HUB-2--(tunnel70)----------ISP-2-----------Spokes

We will add one router as a Hub but it will connect the two ISP's in the same router

New HUB-3---(tunnel20)------ISP-1---------Spokes

                  ---(tunnel70)------ISP-2---------Spokes

[Elliot Dierksen]

To the best of my knowledge, yes you can use the same names. You will have to duplicate the config on the new tunnel that maps name to service policies.