DMVPN: HUB's behind a LoadBalancer and Spoke-Spoke communication

Hallo,
we are planning a scaling DMVPN network for around 2000 spokes.
Is it possible to install the HUB's behind a Load Balancer so that they are reachable only through 1 VIP address and ALSO the possibility of a direkt spoke-spoke communication when needed?
I only found Phase 2 and SLB for HUBs but
without a spoke-spoke communication.
http://www.cisco.com/application/pdf/en/us/guest/products/ps6658/c1161/cdccont_0900aecd80313ca3.pdf
see page 13 there is what we like to have but with the extension of spoke-spoke communication.
regards
Karlheinz

I have been waiting for Cisco to get the spoke-spoke functionality working for this DMVPN HUBs behind load balancer environment. The traditional DMVPN with multiple HUBs does not really scale well, plus it is not very stable routing and NHRP wise.
Would you care to tell more about your solution. As far as I know on a HUB you cannot have one tunnel for spoke to HUB connections and the other just for HUB-HUB, the NHRP requests from the spokes to find out about the other spoke public IP will not be forwarded between the tunnel interfaces on the HUB

Similar Messages

  • DMVPN HUB router behind NAT

    we are getting new sip trunks put in and in order for the provider to put them in the Providor put in a router to control all web traffic so they can QOS the voice that means our VPN routers will go behind the nat barrier. but when i switched the routers interface to the natted address the DMVPN tunnels would not build. there is a nat translation to the routers so the external(route-able) IP did not change. the IPsec tunnels did come up just fine. just the few DMVPN connected tunnels did not.
    if issue a "sh DMVPN" the Peer NBMA Addr shows up as 0.0.0.0 while the Peer Tunnel addr is what it should be, also the attrb is  "X"
    Tunnel source i have set to the interface, and the key is set to "crypto isakmp key "my key" address 0.0.0.0 0.0.0.0 no-xauth"
    i am at a loss on why this was not working. keep in mind this is the HUB router and not the Spoke.

    Here is some additional infor to help
    hub config:
    interface Tunnel0
     bandwidth 512
     ip address "hubtunnelIP" 255.255.255.0
     no ip redirects
     ip nhrp authentication "XXX"
     ip nhrp map multicast dynamic
     ip nhrp network-id 1
     tunnel source GigabitEthernet0/1
     tunnel mode gre multipoint
     tunnel protection ipsec profile net1
    crypto isakmp key "My Key" address 0.0.0.0 0.0.0.0 no-xauth
    crypto ipsec transform-set "mytransfromset" esp-des esp-md5-hmac
     mode transport
    crypto ipsec profile net1
     set transform-set "mytransformset"
    Spoke config:
    crypto isakmp key "My Key" address "Remote IP" "remote SM" no-xauth
    crypto ipsec transform-set "mytransformset" esp-des esp-md5-hmac
     mode tunnel
    crypto ipsec nat-transparency spi-matching
    crypto ipsec profile net1
     set transform-set "mytransformset"
    interface Tunnel0
     bandwidth 512
     ip address "spoketunnelIP" 255.255.255.0
     no ip redirects
     ip nhrp authentication "XXX"
     ip nhrp map multicast "Remote IP"
     ip nhrp map "hubtunnelIP" "Remote IP"
     ip nhrp network-id 1
     ip nhrp nhs "hubtunnelIP"
     tunnel source GigabitEthernet0/1
     tunnel mode gre multipoint
     tunnel protection ipsec profile net1 shared

  • DMVPN Hub and Spoke behind NAT device

    Hi All,
    I have seen many documents stating about DMVPN Hub behind NAT or DMVPN Spoke behind NAT.
    But My case i involve in both situation.
    1) HUB have a Load Balancer (2 WAN Link) ISP A & B
    2) Spoke have Load Balancer (2 WAN Link) ISP A & B
    Now the requirement is Spoke ISP A Tunnel to HUB ISP A.  Spoke ISP B tunnel to HUB ISP B
    So total of two DMVPN tunnel from spoke to hub, and i will use EIGRP and PBR to select path.
    As I know at HUB site, LB must do Static NAT for HUB router IP, so spoke will point to it as tunnel destination address. At spoke LB, i will do policy route to reach HUB ISP A IP via Spoke ISP A link, HUB ISP B IP via Spoke ISP B link.
    HUB and Spoke have to create 2 tunnel with two different network ID but using same source interface.
    The Tunnel destination IP at spoke router is not directly belongs to HUB router. Its hold by HUB LB , and forwarded to HUB router by Static NAT.
    Any problem will face with this setup? Any guide?
    Sample config at HUB.
    interface Tunnel0
    bandwidth 1000
    ip address 172.16.1.1 255.255.255.0
    ip mtu 1440
    ip nhrp authentication cisco123
    ip nhrp map multicast dynamic
    ip nhrp network-id 1
    ip nhrp holdtime 600
    delay 1000
    tunnel source FastEthernet0/0
    tunnel mode gre multipoint
    tunnel key 0
    tunnel protection ipsec profile cisco
    interface Tunnel1
    bandwidth 1000
    ip address 172.17.1.1 255.255.255.0
    ip mtu 1440
    ip nhrp authentication cisco123
    ip nhrp map multicast dynamic
    ip nhrp network-id 2
    ip nhrp holdtime 600
    delay 1000
    tunnel source FastEthernet0/0
    tunnel mode gre multipoint
    tunnel key 1
    tunnel protection ipsec profile cisco
    Spoke Config
    interface Tunnel0
    bandwidth 1000
    ip address 172.16.1.2 255.255.255.0
    ip mtu 1440
    ip nhrp authentication cisco123
    ip nhrp map 172.16.1.1 199.1.1.1
    ip nhrp network-id 1
    ip nhrp holdtime 300
    ip nhrp nhs 172.16.1.1
    delay 1000
    tunnel source FastEthernet0/0
    tunnel destination 199.1.1.1
    tunnel key 0
    tunnel protection ipsec profile cisco
    interface Tunnel1
    bandwidth 1000
    ip address 172.17.1.2 255.255.255.0
    ip mtu 1440
    ip nhrp authentication cisco123
    ip nhrp map 172.17.1.1 200.1.1.1
    ip nhrp network-id 2
    ip nhrp holdtime 300
    ip nhrp nhs 172.17.1.1
    delay 1500
    tunnel source FastEthernet0/0
    tunnel destination 200.1.1.1
    tunnel key 1
    tunnel protection ipsec profile cisco

    Hi Marcin,
    thanks for your reply. The NAT was set up in a way it was/is just to simulate the spoke to be behind NAT device.
    About AH and ESP, you are correct there... this was actually my issue. I should have used pure ESP. At the end, TAC actually assisted me with this. Before I called TAC, i did notice the following. ISAKMP traffic was NATed to 3.3.3.3, as expected. Anything after that, did not work and it has to with NAT and AH. Traffic was no longer NATed so the hub, saw the traffic come from 2.2.2.2 rather than 3.3.3.3, you can also see that in the error message you have pointed out. I also saw it in my packet captures. That caught my eye and i started troubleshooting it. I did not understand that AH can't be NATed, Below  is TAC's explanation. All is good now. Thanks
    .  Essentially, it comes down to the fact that AH will encapsulate the entire IP packet (hence why it is the outermost header) with the exception of a few mutable fields, including the DSCP/ToS, ECN, flags, fragment offset, TTL, and the header checksum.  Since the source/destination IP addresses & port numbers are actually protected by the AH integrity checking, this means that a device performing a NAT operation on the packet will alter these IP header fields and effectively cause the hub router to drop the packet due to AH failure.
    Conversely, ESP traffic is able to properly traverse NAT because it doesn't include the IP header addresses & ports in its integrity check.  In addition, ESP doesn't need to be the outermost header of the packet in order to work, which is why devices will attach an outer UDP/4500 header on the traffic going over NAT."

  • Running DMVPN Hub and Spoke on same router?

    My client has a project in which traffic flow is hierarchial in nature.  Using DMVPNs, the design is for a "center" router to be a DMVPN spoke to the cloud above it, and a DMVPN Hub to the cloud below it.  I have tried to lab this up, but no success.  I initially build the center router as a DMVPN spoke to teh upper cloud and all is well.  As soon as I had the second tunnel config (as the DMVPN hub to the lower cloud), the first tunnel goes down and my EIGRP flaps.  Im running EIGRP across the DMVPN tunnels.  The two DMVPN clouds are using different network IDs and are running separate EIGRP routing instances.
    I can post configs if desired - just wanted to see if anyone is doing this or knows whether it is possible. 
    Jeff          

    Hi,
    I know it is possible using two DMVPN clouds, but it seems that you need DMVPN phase 3 in this situation. This is suitable for the hierarchical model you want. Take a look at the following link
    http://www.cisco.com/en/US/partner/prod/collateral/iosswrel/ps6537/ps6586/ps6660/ps6808/prod_white_paper0900aecd8055c34e_ps6658_Products_White_Paper.html
    Hope this helps.

  • IPv6 WAN Adresses on DMVPN Hubs and Spokes

    Hi,
    I have one question about IPv6 and DMVPN. Let's assume we have a DMVPN Hub Site running IPv6 IP addresses on the WAN Interfaces and Spoke Sites running either IPv4 or IPv6 IP adresses on their WAN Interfaces.
    In IPv4 only Networks, the Tunnel Konfiguration looked like that:
    interface Tunnel 1
    <...>
    ip nhrp map multicast <IPv4 NMBA>
    ip nhrp map 10.0.10.1 <IPv4 NMBA>
    There are IPv6 nhrp commands as well, but they can only map an IPv6 Address to an IPv4 NMBA:
    interface Tunnel1
    <...>
    ipv6 nhrp map multicast <IPv4 NMBA>
    ipv6 nhrp map <IPv6 Tunnel Adress> <IPv4 NMBA>
    I'm wondering how you would configure DMVPN for a network using IPv6 on their WAN Interfaces ??
    Best regards,
    Thomas

    Thomas,
    VTI1(config-if)#ip nhrp map 1.2.3.4 ?  A.B.C.D     IP NBMA address  A.B.C.D     IP mask of destination  X:X:X:X::X  IPv6 NBMA address
    and
    VTI1(config-if)#ipv6 nhrp map 2001:db8::1/128 ?  A.B.C.D     IPv4 NBMA address  X:X:X:X::X  IPv6 NBMA address
    I _seem_to_remember_ this was added in 15.2T  but can't find it back.
    M.

  • DMVPN Hub Behind ASA

    Can somebody please send me a known working snippet of ASA config to support a DMVPN hub NAT'd behind an ASA. I tried for 2 days even with TAC and I was finally forced to put my DMVPN Hub out on the Internet with the IOS FW.
    Basically the issue I was seeing was that ISAKMP would almost complete at the spoke, try to go to QM_IDLE and then start the ISAKMP process over. Tried different code revs, etc. The ASA is running 8.0.3. Works great as long as the ASA was not in the path.
    Any help is appreciated.

    Hey there I am trying to do the same type of setup with a 3845 behind an ASA5510/Sec plus and I am getting similar results.
    I have access-lists permitting:
    - ESP, ISAKMP, GRE, and 4500 to the router on the inside.
    Have you made in head way to a solution?

  • What is the difference between Open hub destination and Info spokes

    what is the difference between Open hub destination and Info spokes?
    Please seacrh the forum before posting a thread
    Edited by: Pravender on Aug 16, 2010 11:17 AM

    Hi,
    When a user initiates open hub extraction by creating an InfoSpoke, behind-the-scenes activity involves OO ABAP which is calling classes to determine each of the different components involved in making the open hub extraction possible.  In particular, this enhancement will focus on 2 standard classes: one used to determine file destination name and path and the other to control the user interface of the InfoSpoke which will ultimately allow the user to enter his/her own filename and path.
    The open hub service enables us to distribute data from an SAP BW system into external data marts, analytical applications, and other applications. With this, we can ensure controlled distribution using several systems.
    The central object for the export of data is the InfoSpoke. Using this, we can define the object from which the data comes and into which target it is transferred.
    Regards,

  • Difference bw open hub destination and info spoke ???

    Hi,
    what are difference b/w open hub destination and info spoke ???
    Thanks In advance.
    Regards
      Nitin

    Hi,
    The open hub destination is the object that allows you to distribute data from a BI system to non-SAP data marts, analytical applications, and other applications. It ensures controlled distribution across multiple systems.
    The open hub destination defines the target to which the data is transferred.
    An InfoSpoke can extract data in two ways:
    1.Full mode (F): the data corresponding to the selection criteria of the InfoSpoke is transferred from the data source into the respective destination.
    2.Delta mode (D): records that were added since the last extraction only are transferred in this mode. This is only possible for the source objects InfoCube and DataStore object.
    See the below Articles:
    InfoSpoke: Part -1
    www.sdn.sap.com/irj/servlet/prt/portal/prtroot/com.sap.km.cm.docs/library/business-intelligence/g-i/infospoke%20part%201.pdf
    Open Hub Destination: Part 1
    http://www.sdn.sap.com/irj/servlet/prt/portal/prtroot/com.sap.km.cm.docs/library/business-intelligence/m-o/open%20hub%20destination%3a%20part%201.pdf
    Open Hub Destination: Part 2
    http://www.sdn.sap.com/irj/servlet/prt/portal/prtroot/com.sap.km.cm.docs/library/business-intelligence/m-o/open%20hub%20destination%3a%20part%202.pdf
    Thanks
    Reddy

  • DMVPN Hub to Hub connection

    Hi all,
    I am doing a lab in wich i'm configuring a dual-hub single-cloud DMVPN network.
    This network consists of two hubs and a spoke, where the spoks is connected with both hubs for redundancy.
    This all works fine, except 1 thing.. the hubs can´t reach eachother.
    This is because they do not have an EIGRP neighbour relationship, and I do not know what is wise way to configure this relationship.
    What I can think of is creating a seperate IPsec/GRE tunnel between the two of them, but I wonder if there is a better way?
    Any advice will beappreciated.
    Kind regards,
    Dwayne Peeters

    Hi Dwayne,
    Please check this out:
    I posted a question, how do I mark a reply as 'Correct Answer'?
    Hope to help.
    Portu.
    Message was edited by: Javier Portuguez

  • DMVPN Hub 3945 without ISM card

    Does anyone have any experience with DMVPN hub running on a 3945 with no ISM card? Specifically wondering how many 881 model spokes it will support. The network makes heavy use of PIM-SM and is used primarily for voice and video. Assume throughput of 2M from each spoke.
    thank you, E

    I know this one is old, but what I don't see on your Firewall is AH and ESP, I only see GRE. Also are you trying to offload the IPSEC protection to this firewall?

  • Strange status of DMVPN HUB

    Hi all,
    I have 2 DMVPN HUBs and 20 spokes and on one of these have strange status of DMVPN - NHRP (what does it mean? i didn't find explanation what that status is bad or good, is it mean that spoke could'n get NBMA address of HUB through NHRP?). Could anyone explain what does it mean?
    #show dmvpn
    Interface: Tunnel4, IPv4 NHRP Details
    Type:Spoke, NHRP Peers:2,
    # Ent  Peer NBMA Addr Peer Tunnel Add State  UpDn Tm Attrb
         1        7.#.#.3        10.5.5.1    UP    1d18h     S
         1        7.#.#.4        10.5.5.2  NHRP    1d18h     S
    Spoke's configuration.
    interface Tunnel4
     bandwidth 15000
     ip address 10.5.5.20 255.255.255.0
     no ip redirects
     ip mtu 1416
     ip nhrp map multicast dynamic
     ip nhrp map multicast 7.#.#.3
     ip nhrp map multicast 7.#.#.4
     ip nhrp map 10.5.5.1 7.#.#.3
     ip nhrp map 10.5.5.2 7.#.#.4
     ip nhrp network-id 101
     ip nhrp nhs 10.5.5.1
     ip nhrp nhs 10.5.5.2
     zone-member security outside
     ip tcp adjust-mss 1380
     delay 100
     keepalive 10 3
     tunnel source GigabitEthernet0/2
     tunnel mode gre multipoint
     tunnel key 111000
     tunnel protection ipsec profile dmvpn

    Marcin,
    thank you again for quick reply)
    It very strange because i follow yours tshooting steps and what i got bellow:
    1.Spoke can ping NBMA address of two HUBs
    2. Every HUB can reach NBMA address of spoke
    3. I switch on debuging on spoke and HUBs and I see request packet of NHRP to every HUBs
    Debug on spoke:
    000332: May 23 10:47:53.408 MSK: NHRP: Attempting to send packet via DEST 10.5.5.1
    000333: May 23 10:47:53.408 MSK: NHRP: NHRP successfully resolved 10.5.5.1 to NBMA 7.#.#.3
    000334: May 23 10:47:53.408 MSK: NHRP: Encapsulation succeeded.  Tunnel IP addr 7.#.#.3
    000335: May 23 10:47:53.408 MSK: NHRP: Send Registration Request via Tunnel4 vrf 0, packet size: 92
    000336: May 23 10:47:53.408 MSK:       src: 10.5.5.20, dst: 10.5.5.1
    000337: May 23 10:47:53.408 MSK: NHRP: 120 bytes out Tunnel4 
    000338: May 23 10:47:53.408 MSK: NHRP: Resetting retransmit due to hold-timer for 10.5.5.1
    000339: May 23 10:47:53.408 MSK: NHRP: Attempting to send packet via DEST 10.5.5.2
    000340: May 23 10:47:53.408 MSK: NHRP: NHRP successfully resolved 10.5.5.2 to NBMA 7.#.#.4
    000341: May 23 10:47:53.408 MSK: NHRP: Encapsulation succeeded.  Tunnel IP addr 7.#.#.4
    000342: May 23 10:47:53.408 MSK: NHRP: Send Registration Request via Tunnel4 vrf 0, packet size: 92
    000343: May 23 10:47:53.408 MSK:       src: 10.5.5.20, dst: 10.5.5.2
    000344: May 23 10:47:53.408 MSK: NHRP: 120 bytes out Tunnel4 
    000345: May 23 10:47:53.408 MSK: NHRP: Resetting retransmit due to hold-timer for 10.5.5.2
    000346: May 23 10:47:53.412 MSK: %LINEPROTO-5-UPDOWN: Line protocol on Interface Tunnel4, changed state to up
    000347: May 23 10:47:53.412 MSK: NHRP: Receive Registration Reply via Tunnel4 vrf 0, packet size: 112
    000348: May 23 10:47:53.412 MSK: NHRP: netid_in = 0, to_us = 1
    000349: May 23 10:47:53.412 MSK: NHRP: NHS 10.5.5.1 Tunnel4 vrf 0 Cluster 0 Priority 0 Transitioned to 'RE' from 'E' 
    000350: May 23 10:47:53.412 MSK: NHRP: NHS-UP: 10.5.5.1
    000351: May 23 10:47:54.920 MSK: NHRP: Setting retrans delay to 4 for nhs  dst 10.5.5.2
    000352: May 23 10:47:54.920 MSK: NHRP: Attempting to send packet via DEST 10.5.5.2 
    000353: May 23 10:47:54.920 MSK: NHRP: NHRP successfully resolved 10.5.5.2 to NBMA 7.#.#.4
    000354: May 23 10:47:54.920 MSK: NHRP: Encapsulation succeeded.  Tunnel IP addr 7.#.#.4
    000355: May 23 10:47:54.920 MSK: NHRP: Send Registration Request via Tunnel4 vrf 0, packet size: 92
    000356: May 23 10:47:54.920 MSK:       src: 10.5.5.20, dst: 10.5.5.2
    and i don't see any logs related of this spoke on second HUB!
    So... NHRP packet loss on the way to second HUB,but i can't guess about reason why is happend

  • DMVPN Hub Router QoS

    Hello DMVPN Experts,
    As we knew DMVPN Hub routers can have per-tunnel QoS configuration for the spokes.
    But I am not sure the QoS configuration for the Hub site itself. I assume it should be seperated from the per-tunnel QoS and the service-policy should be applied at the physical WAN interfaces and tunnel interfaces? Need help please. Some sample configuration would be appreciated.
    Thanks
    Cedar

    Hi Joseph,
    I am afraid I am having a bit difficulty to understand and would like to hear more if you don't mind.
    We are on the same page that Per-Tunnel QoS let the spokes to control the traffics toward the hub site, which is considered inbound traffic from the WAN/Tunnel interfaces of hub router point of view. However, in order to control the inbound and/or outbound traffic of the WAN/Tunnel interfaces of the hub router, how should we configure seperate QoS configuration other than Per-Tunnel QoS templates, if we should? 
    Here is what I know so far based on ASR1000 document.
    http://www.cisco.com/c/en/us/td/docs/ios-xml/ios/sec_conn_dmvpn/configuration/xe-3s/asr1000/sec-conn-dmvpn-xe-3s-asr1000-book/sec-conn-dmvpn-per-tunnel-qos.html
    Restrictions for Per-Tunnel QoS for DMVPN
    • The class default shaper with the QoS service policy on a physical interface that is applied to the DMVPN tunnel does not support point-to-point generic routing encapsulation (GRE) tunnels, shaper on physical interfaces, and shaper on VLAN/subinterfaces.
    • QoS on a physical interface is limited only to the class default shaper on the physical interface. No other QoS configurations on the physical interface are supported when two separate QoS policies are applied to the physical and tunnel interfaces.
    • Addition of a QoS policy with a class default shaper on a physical interface is not supported when multiple QoS policies are utilized.
    • You can attach a per-tunnel QoS policy on the tunnel only in the egress direction.
    • The class default shaper policy map on the main interface must be applied before the tunnel policy map is applied.
    • The class default shaper policy map must contain only the class class-default and shape commands.
    • The main interface policy map is checked for validity only when a QoS service policy is applied on the tunnel interface. The main interface policy map is not checked during a tunnel move or modification.
    • Adding new classes or features to the main interface policy map is not supported. Doing so, however, will not be blocked.
    After reading the above document, my understanding is that
    1. We could have seperate policy map for physical WAN interface.
    2. The policy-map for the physical WAN interface is limited to a class default shaper only.
    3. The policy-map for physical WAN interface must be applied at the physical WAN interface before the tunnel policy-maps are applied at the tunnel interface.
    But I am not 100% sure if it's correct.
    Thanks,
    Cedar

  • DMVPN Hub with Dual ISPs

    I have one Hub Router, I have 2 ISPs and would like to set it up as a dual hub. I have configured two tunnel interfaces on the hubs and spokes, set the  ipsec profile to shared, etc.
    What i was trying to do was route-map the traffic for the two tunnel  interfaces out of the relevant interfaces and came up with the following:
    route-map ROUTE-DMVPN permit 10
    match interface Tunnel1
    set ip default next-hop xxxxx
    route-map ROUTE-DMVPN permit 20
    match interface Tunnel2
    set ip default next-hop xxxxx
    and then set that as a local policy route-map on the router.
    The first section matches packets and works, the second does not. Is what I am trying to do possible? Or Do I need to be more sophisticated in my design?
    Thanks in advance!

    OK, here is something I came up really fast in my lab.
    Note that it does NOT contain best practices or some required configurations and is only meant to show a concept.
    Here is the situation
    hub ===== two links ==== "ISP" -----one link ---- spoke
    hub physical:
    10.1.1.0/24 (ISP1)
    10.2.2.0/24 (ISP2)
    spoke physical:
    10.3.3.0/24
    two DMVPN clouds:
    172.16.1.0/24
    172.16.2.0/24
    Hub lan:
    99.99.99.0/24
    spoke lan:
    88.88.88.0/24
    Hub configuration:
    interface Ethernet0/0 ip address 10.1.1.1 255.255.255.0interface Ethernet1/0 ip vrf forwarding ISP2 ip address 10.2.2.1 255.255.255.0interface Ethernet2/0 ip address 99.99.99.1 255.255.255.0interface Tunnel1 ip address 172.16.1.1 255.255.255.0 no ip redirects ip nhrp map multicast dynamic ip nhrp network-id 1 ip nhrp server-only delay 1000 tunnel source Ethernet0/0 tunnel mode gre multipoint tunnel key 1endinterface Tunnel2 ip address 172.16.2.1 255.255.255.0 no ip redirects ip nhrp map multicast dynamic ip nhrp network-id 2 delay 2000 tunnel source Ethernet1/0 tunnel mode gre multipoint tunnel key 2 tunnel vrf ISP2endrouter eigrp 100 network 99.99.99.0 0.0.0.255 network 172.16.1.0 0.0.0.255router eigrp 101 network 99.99.99.0 0.0.0.255 network 172.16.2.0 0.0.0.255ip route 0.0.0.0 0.0.0.0 10.1.1.254
    ip route vrf ISP2 0.0.0.0 0.0.0.0 10.2.2.254
    Spoke config:
    interface Ethernet0/0 ip address 10.3.3.1 255.255.255.0endinterface Tunnel1 ip address 172.16.1.2 255.255.255.0 no ip redirects ip nhrp map multicast 10.1.1.1 ip nhrp map 172.16.1.1 10.1.1.1 ip nhrp network-id 1 ip nhrp nhs 172.16.1.1 delay 1000 tunnel source Ethernet0/0 tunnel mode gre multipoint tunnel key 1endrouter eigrp 100 network 88.88.88.0 0.0.0.255 network 172.16.1.0 0.0.0.255router eigrp 101 network 88.88.88.0 0.0.0.255 network 172.16.2.0 0.0.0.255
    Some outputs:
    spoke#sh ip eigrp topology 99.99.99.0/24EIGRP-IPv4 Topology Entry for AS(100)/ID(172.16.2.2) for 99.99.99.0/24  State is Passive, Query origin flag is 1, 1 Successor(s), FD is 25881600  Descriptor Blocks:  172.16.1.1 (Tunnel1), from 172.16.1.1, Send flag is 0x0      Composite metric is (25881600/281600), route is Internal      Vector metric:        Minimum bandwidth is 100 Kbit        Total delay is 11000 microseconds        Reliability is 255/255        Load is 1/255        Minimum MTU is 1472        Hop count is 1        Originating router is 172.16.2.1EIGRP-IPv4 Topology Entry for AS(101)/ID(172.16.2.2) for 99.99.99.0/24  State is Passive, Query origin flag is 1, 0 Successor(s), FD is 4294967295  Descriptor Blocks:  172.16.2.1 (Tunnel2), from 172.16.2.1, Send flag is 0x0      Composite metric is (26137600/281600), route is Internal      Vector metric:        Minimum bandwidth is 100 Kbit        Total delay is 21000 microseconds        Reliability is 255/255        Load is 1/255        Minimum MTU is 1472        Hop count is 1        Originating router is 172.16.2.1spoke#sh ip nhrp detail
    172.16.1.1/32 via 172.16.1.1
       Tunnel1 created 00:16:33, never expire
       Type: static, Flags: used
       NBMA address: 10.1.1.1
    172.16.2.1/32 via 172.16.2.1
       Tunnel2 created 00:16:33, never expire
       Type: static, Flags: used
       NBMA address: 10.2.2.1
    spoke#                  
    and
    hub#sh ip eigrp topology 88.88.88.0/24EIGRP-IPv4 Topology Entry for AS(100)/ID(172.16.2.1) for 88.88.88.0/24  State is Passive, Query origin flag is 1, 1 Successor(s), FD is 25881600  Descriptor Blocks:  172.16.1.2 (Tunnel1), from 172.16.1.2, Send flag is 0x0      Composite metric is (25881600/281600), route is Internal      Vector metric:        Minimum bandwidth is 100 Kbit        Total delay is 11000 microseconds        Reliability is 255/255        Load is 1/255        Minimum MTU is 1472        Hop count is 1        Originating router is 172.16.2.2EIGRP-IPv4 Topology Entry for AS(101)/ID(172.16.2.1) for 88.88.88.0/24  State is Passive, Query origin flag is 1, 0 Successor(s), FD is 4294967295  Descriptor Blocks:  172.16.2.2 (Tunnel2), from 172.16.2.2, Send flag is 0x0      Composite metric is (26137600/281600), route is Internal      Vector metric:        Minimum bandwidth is 100 Kbit        Total delay is 21000 microseconds        Reliability is 255/255        Load is 1/255        Minimum MTU is 1472        Hop count is 1        Originating router is 172.16.2.2hub#show ip nhrp detail
    172.16.1.2/32 via 172.16.1.2
       Tunnel1 created 00:16:09, expire 01:43:50
       Type: dynamic, Flags: unique registered
       NBMA address: 10.3.3.1
    172.16.2.2/32 via 172.16.2.2
       Tunnel2 created 00:16:09, expire 01:43:50
       Type: dynamic, Flags: unique registered
       NBMA address: 10.3.3.1

  • Replacing the DMVPN hub router

    We are replacing our current 2921 router, Version 15.2(4)M2, with a 3925 Version 15.2(4)M6. It is the DMVPN hub router for 6 spoke routers. We cut and pasted the configuration from the old router to the new. We confirmed internet connectivity from clients on the inside. But none of the DMVPN tunnels will set up. As we were in a very short maintenance window we did not have a lot of time to troubleshoot and had to revert to the old router. Is there some procedure we need to implement to force the tunnels to come up?

    Because you are changing the Hardware and copy past the config. Spokes will not re register themselves at HUB until you reset them again. Then they will register themselves again in the NHRP table at the new HUB..

  • Info set , info provider and info spoke

    Hi gurus plz give me the difference in between info set and info provider and info spoke. and give me what are the prerequisites are needed to process infoset, infoprovider and info spoke?
    Regards
    Vidhu

    InfoProvider
    An InfoProvider is an object for which queries can be created or executed in BEx
    Check this for more,
    http://help.sap.com/saphelp_nw04/helpdata/en/4d/c3cd3a9ac2cc6ce10000000a114084/content.htm
    Infoset:
    An InfoSet is a special view of a dataset, such as logical database, table join, table, and sequential file, and is used by SAP Query as a source data. InfoSets determine the tables or fields in these tables that can be referenced by a report. In most cases, InfoSets are based on logical databases.
    SAP Query includes a component for maintaining InfoSets. When you create an InfoSet, a DataSource in an application system is selected.
    Navigating in a BW to an InfoSet Query, using one or more ODS objects or InfoObjects.You can also drill-through to BEx queries and InfoSet Queries from a second BW system, that isConnected as a data mart.
    The InfoSet Query functions allow you to report using flat data tables (master data reporting).Choose InfoObjects or ODS objects as data sources. These can be connected using joins.You define the data sources in an InfoSet. An InfoSet can contain data from one or more tables that are connected to one another by key fields.The data sources specified in the InfoSet form the basis of the InfoSet Query.
    Check the link for more,
    http://help.sap.com/saphelp_nw2004s/helpdata/en/ad/2225391d4f000be10000000a114084/frameset.htm
    InfoSpoke:
    Info spoke is an open hub destination defines to which target the data is to be relayed.
    Check this link for more,
    http://help.sap.com/saphelp_nw2004s/helpdata/en/ad/2225391d4f000be10000000a114084/frameset.htm
    Check this doc also,
    https://www.sdn.sap.com/irj/servlet/prt/portal/prtroot/docs/library/uuid/eb462104-0701-0010-07ae-d866630e0989
    Hope this gives you a good idea...

Maybe you are looking for