We're Sorry, Full Content Access is for Members Only...

If you like to keep on reading, Become a Member Now! Here is why:

  • Learn any CCNA, CCNP and CCIE R&S Topic. Explained As Simple As Possible.
  • Try for Just $1. The Best Dollar You've Ever Spent on Your Cisco Career!
  • Full Access to our 644 Lessons. More Lessons Added Every Week!
  • Content created by Rene Molenaar (CCIE #41726)

488 Sign Ups in the last 30 days

satisfaction-guaranteed
100% Satisfaction Guaranteed!
You may cancel your monthly membership at any time.
No Questions Asked!

Tags: , ,


Forum Replies

  1. Rene,

    what would be the reason for nbma 192.168.123.2 to inside ip 172.16.123.2 be showing twice under “show dmvpn” command? It has shown several times in your examples.

    Thanks.

  2. Hi Harvinder,

    Take a look below:

    Spoke2#show dmvpn        
    Legend: Attrb --> S - Static, D - Dynamic, I - Incomplete
            N - NATed, L - Local, X - No Socket
            T1 - Route Installed, T2 - Nexthop-override
            C - CTS Capable
            # Ent --> Number of NHRP entries with same NBMA peer
            NHS Status: E --> Expecting Replies, R --> Responding, W --> Waiting
            UpDn Time --> Up or Down Time for a Tunnel
    ==========================================================================
    
    Interface: Tunnel0, IPv4 NH
    ... Continue reading in our forum

  3. Rene I set this up, Spoke still use Hub as next-hop, Spoke 2 is fine but Spoke 1 still shows 172.6.132.1 as next hop in cef
    see output below

    Spoke 2
    Spoke2#traceroute 2.2.2.2 source loopback 0
    Type escape sequence to abort.
    Tracing the route to 2.2.2.2
    VRF info: (vrf in name/id, vrf out name/id)
      1 172.16.123.1 32 msec 28 msec 24 msec
      2 172.16.123.2 76 msec 32 msec *
    ... Continue reading in our forum

  4. How should the behavior when it is deployed with the ISIS? It would be nice to post a lesson of ISIS in phases 1, 2 and 3.

  5. Hi Ricardo,

    The difference between OSPF P2MP and broadcast/non-broadcast is that with P2MP, the next hop will always be the hub and with broadcast/non-broadcast it will be the remote spoke. I have an example for this:

    https://networklessons.com/ospf/ospf-next-hop-ip-address-with-different-network-types/

    This is about frame-relay but it’s the exact same thing with DMVPN. If it’s working with broadcast (where the next hop is the remote spoke, not the hub) then it indeed sounds like an issue with the next hop override.

    You could try to enable some NHRP and OSPF S

    ... Continue reading in our forum

6 more replies! Ask a question or join the discussion by visiting our Community Forum