DMVPN HUB Static Route change

[wrobbin]

Currently we run DMVPN and BGP establshes via a static route  like so

ip route A.B.C.D 255.255.255.255 Tunnel100 name DMVPN-HUB-BGP-PEER

it was changed via an EEM Script to

ip route A.B.C.D 255.255.255.255 W.X.Y.Z   name DMVPN-HUB-BGP-PEER

I thought  it could be due to 

For point to point interfaces,  you can use static routes that point to the interface or to the next  hop address. There is only one possible next hop and its L2 address will  be used to build L2 frame.

For multipoint interfaces which the DMVPN tunnel interfaces are,  it is more suitable to use static routes that point to a next hop  address to avoid the need for resolving every destination address to its  L2 address. While we could  still continue to use static  routes pointing to the interface it’s not a scalable solution.

but I was told this was the incorrect reason......

What other reason could this be needed/done this way?

[Philip D'Ath]

I'm a little confused.

You can have static BGP neighbours.  You can redistribute static routes into BGP.  But BGP is a dynamic routing protocol, and does not have static routes.  What are you meaning here?

Who created the EEM script?  Perhaps you could ask them why they did this.

Are you using static routes to override a dynamic routing table for remote BGP neighbours perhaps, to prevent route recursion?

[wrobbin]

This static route is used to establish the BGP peering session over DMVPN with the hub,

[wrobbin]

what i dont get is why use the IP of the hub vice a tunnel interface. What does it gain you ?

[Philip D'Ath]

Ok, what it does is prevent the routing from using recursion for a route lookup.

If you don't specify the tunnel interface, and the Tunnel goes down but the router can find a path via another circuit, it will use that (aka recursively lookup the route).

With BGP you [mostly] want point to point connections.  If the Tunnel goes down you want BGP to go down - not to keep working via another path.

[wrobbin]

The Tunnel Interface for example is 10.x.0.1/16  and the BGP Peer is 10.x.0.35/16

Since DMVPN it  is a NBMA no need to worry about broadcast.

ip route A.B.C.D 255.255.255.255 Tunnel100 name DMVPN-HUB-BGP-PEER

So that /16 is a connected route to the tunnel.

so it wouldn't look for it out of any other interface if that route went down.