Phase 2 and 3 DMVPN | DMVPN Tunnels Part 2

preview_player
Показать описание
Phase 2 and 3 DMVPN | DMVPN Tunnels Part 2
We’ve converted our static GRE tunnels to a shiny new Phase-1 DMVPN. But we’ve found some drawbacks… All traffic is flowing through the hub, which increases its load dramatically, consumes bandwidth, and adds latency.

We don’t want to be restricted in this way, so it’s time to investigate Phase-2. This allows us to use NHRP Resolution Request and Response messages to build spoke to spoke tunnels. This is a simple spoke configuration, where static GRE tunnels are converted to dynamic multipoint GRE (mGRE) tunnels. We’ll even see this configured in a lab.

But even phase-2 has its limitations. We can’t have a default route or summary route pointing to the hub any more. Spoke routers need to maintain large routing tables of their own. Fortunately we have Phase-3!

Phase-3 adds NHRP Redirect messages on the hub, and shortcut or override routes on the spoke. Now we can have spoke to spoke communication, as well as efficient routing tables!

In the next videos, we’re looking at routing over DMVPN, and advanced concepts like multi-hub, and hierarchical deployments

Overview of this video:

0:00 Introduction

0:21 Limitations of Phase-1

2:01 Phase-2

4:33 Live Configuration

6:41 Limitations of Phase-2

8:18 Phase-3

10:31 Live Configuration

LET'S CONNECT

Рекомендации по теме
Комментарии
Автор

not sure why people are not finding this video while searching DMVPN. this is best among some videos

varunkashyap-bzjv
Автор

He explains a very complex topic in such a way it becomes easy to understand
Amazing job, keep it up!

BerserkFM
Автор

Best dmvpn explanation with examples ever, just do not search for other one.

linkflap
Автор

You're the best tutor ever. Crispy explanations and great walkthroughs, 😊.. Bless you

TheRadiant
Автор

Crisp and short. Great job in explaining a complex thing in simple format.

BinuKR_KRB
Автор

Brilliant explanation! Complex design is explained in such as simple way!

arunlakshmikanth
Автор

brilliant explanation ! I can see your passion in your style of teaching..Kudos!

raakiravikiran
Автор

Excellent. We are converting to DMVPNs at work and this video clarified quite a bit. Good job!!!!

williebrown
Автор

Brilliant 💡 way of explaining things and the Way you put together all topics

trekwithistaque
Автор

Hats off to you!!! You are an amazing teacher.

MohammadAli-ykbk
Автор

Best DMVPN explanation I've ever seen!

jandrozd
Автор

Very Nice explanation, now i learned the DMVPN

najuru
Автор

you are awesome. great explanation in calm voice!

CitrusAnimates
Автор

Didn’t know you could avoid the command nhs, unless I missed it. Thought you needed to specify the next hop server with nhs on the clients.

joserivera
Автор

Thanks for the videos really helpful. Do you have content on Multi-hubs and Hierarchical Deployments yet?

johnojo
Автор

Quick question for DMVPN Phase 2:

In the video it says that when Spoke-1 wants to communicate with Spoke-2 it first sends a NHRP resolution request to the Hub, which is forwarded to Spoke-2 (destination) and it's that router that sends the NHRP resolution reply.


says
"[...] when a spoke wants to transmit a packet to another spoke (such as the subnet behind another spoke), it uses NHRP to dynamically determine the required destination address of the target spoke. The hub router acts as the NHRP server and handles this request for the source spoke. [...]"


Other links that I found in Google seems to indicate the same behaviour: the hub sends the resolution request reply to the spoke that wants to communicate with another spoke.

Is that correct?

geroni
Автор

One thing that stayed unrevealed in Phase 2 - how spokes do know when they should send NHRP resolution request to the hub? I mean If at the start point spokes do not know that any other spokes exist, as a result, they assume that any necessary network behind the hub.

JohnSmith-ecpt
Автор

Pretty Neat. I have Question on DMVPN Phase3. I see that on both the spoke routers we have a static route for 10.0.0.0/8 to the Hub Tunnel Address (192.168.254.2). You were then able to ping networks behind the Spoke routers. Am wondering how did that happen? There are no configs on the Hub Routers and they have no clue about 10.8.0.0/24 or 10.222.0.0/24. Are they routed via the Underlay Network?

shrinivasanrajagopalan
Автор

Great job, appreciate if you could make new ones more advance like for CCIE level. thanks.

JamesJohnson-jbyg
Автор

is video available for dmvpn dynamic routing protocol expalained ?

Farookhshaikh
join shbcf.ru