Imagine you have both a private MPLS network and public Internet, and you wish to use DMVPN on both. If you set your network ID's on both tunnel interfaces to be the same, clear and re-register everything, then suddenly your spokes get the correct addresses to allow for direct spoke-to-spoke communication. This means that if you use two different NHRP network ID's, the two sets of spokes can not communicate directly between each other, they must pass traffic through the hub. However, if you ask the spokes associated with the first tunnel about the spokes associated with the second, you'll see that their NBMA address is listed as the hub, not as the other spoke. If you set the second tunnel interface as a new tunnel key and a new nhrp network, you can register the first two spokes without issue, and you can add new spokes with the second interface. However, if we enable a second tunnel interface on the hub and we tie it to the same source interface with the same key (None), then things don't work at all. If we configure the first two with network id 1 and no tunnel key, everything works fine. I put 4 spokes and a hub on a common physical interface. Here's a follow to the key's vs network id's question.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |