The configuration for Spoke-1 is shown below. The spoke routers use a similar configuration to the hub. The tunnel key, if set, is in the GRE header. The tunnel key is an optional value that we can use for more authentication. This enables more than one spoke router to connect to the tunnel. It is recommended to keep this value the same across all your routers, to make it easier to troubleshoot.įinally, we can set the tunnel mode to GRE multipoint. It is not sent to any other router, so you can basically set this to whatever you want. This value is completely local to the router. The ID tells the router if the interfaces are in the same domain or not. Perhaps for another DMVPN network, or some other use. It’s possible to have NHRP enabled on more than one interface on a router. This is conceptually similar to an OSPF process ID. This is a cleartext key that is sent with NHRP packets. First, we (optionally) set authentication. Notice that there is no tunnel destination address? That’s because the destinations are added dynamically, through the NHRP registration process. The source IP is the NBMA Address of the tunnel, and the Tunnel IP is the logical address. This includes a tunnel IP address, the MTU/MSS (to adjust for the GRE headers), and the tunnel source IP. There are several parts which will be familiar from when you configured a GRE tunnel. We’ll start by configuring tunnel 0 on the hub router. It is recommended to read up on GRE and How DMVPN Works before proceeding. You may think that phase 1 is outdated, but it’s especially useful for learning DMVPN in general. We’re going to look at the configuration for each DMVPN phase.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |