Hi,   Can you explain what you mean by saying :   " if i want to filter default route form Site A to advertise only to Site D not sure if i can do it?. now side D see default route was advertised from Site A B and C via my SITE"     ... View more

You said only G4 interfaces of R1 and R2 are in the vrf but it looks like some tunnels interfaces also are in the vrf.   ROUTER1 interface Loopback0 ip address 5.5.5.1 255.255.255.255 ! interface Tunnel12 description RTR1 to RTR2 (ospf) ip vrf forwarding INTERNAL ip address 20.1.1.1 255.255.255.0 keepalive 10 3 tunnel source GigabitEthernet5 tunnel destination 172.1.1.2 tunnel vrf INTERNAL  I think the issue is related to EIGRP internal and EIGRP ex.    could you provide the "show ip route ei" when interface to R3 is Up and when it is down? ... View more

Looks like on spoke side everything is OK. The packets are digested and verified in that tunnel before and after the reboot.   Could you confirm the same on the hub side before and after reboot?   ... View more

Looks like everything OK on network ip configuration. Maybe the issue is related to the ipsec.   Could you provide the output of theses commands   1 when the tunnel is up and running show crypto isa sa show crypto ipsec sa   2 after the device's reboot and the tunnel is in nhrp state show crypto isa sa show crypto ipsec sa ... View more

Yes it will. In that case do not add the tunnel key.  ... View more

Ok that sounds better.   Could you perform these tests from the spoke router.   Before the reboot when the tunnel is UP show dmvpn sh ip route 69.46.229.X sh ip cef 69.46.229.X ping 69.46.229.X   After the reboot when the tunnel is in NHRP state show dmvpn sh ip route 69.46.229.X sh ip cef 69.46.229.X ping 69.46.229.X   After the reboot when you remove the tunnel configuration sh ip route 69.46.229.X sh ip cef 69.46.229.X ping 69.46.229.X   Also add a tunnel key on both tunnel interfaces. ... View more

Hi Sathish   Your configuration looks wierd. Following what you posted the simple configuration looks as followed: HUB Tunnel Config: interface Tunnel1 ip address 172.16.254.1 255.255.255.0 ip nhrp map multicast dynamic ip nhrp network-id 101 tunnel source GigabitEthernet0/3.305 tunnel mode gre multipoint tunnel protection ipsec profile ODMVPN2 !tunnel key 0 end interface GigabitEthernet0/3.305 encapsulation dot1Q 305 ip address 69.46.229.X 255.255.255.252 ip nat outside end   Spoke Config: interface Tunnel0 ip address 10.254.254.20 255.255.255.0 ip nhrp map multicast 108.58.212.26 ip nhrp map 10.254.254.1 108.58.212.26 ip nhrp network-id 100 ip nhrp nhs 10.254.254.1 tunnel source GigabitEthernet0/0/0 tunnel mode gre multipoint tunnel key 0 tunnel protection ipsec profile ODMVPN ! interface GigabitEthernet0/0/0 ip address 75.99.252.X 255.255.255.248 ip nat outside   Theres is no "tunnel key 0" in the hub config and also the nhs server configured on the spoke need to be the IP address of the tunnel interface configured on the hub. This nhs address need to have the nbma address correspond to the source interface of tunnel configured on the hub. But in your configuration the HUB nbma address configured in the hub is 69.46.229.X and the HUB nbma address configured in the spoke is 108.58.212.26   Also the underlay configuration need to be Ok, both nbma addresses need to be reachable form each other.   Could you modify the config ? ... View more

What command do I need to check the mc traffic ? ... View more

I cannot right now perfom the test you recommanded. But I did another easier test by skipping both N7Ks VRF on the routing process and configured interface vlan 1762 to join both multicast groups 239.225.1.3 and 239.225.1.4 and we have the same behavior.   Only one stream is received. I do not think the issue is related to the receiver IP address.   NPGVDC02-N7K# sh ip mroute 239.225.1.3 detail IP Multicast Routing Table for VRF "default" Total number of routes: 34 Total number of (*,G) routes: 12 Total number of (S,G) routes: 22 Total number of (*,G-prefix) routes: 0 (*, 239.225.1.3/32), uptime: 07:42:18, pim ip Stats: 0/0 [Packets/Bytes], 0.000 bps Attached oif(s) : No Incoming interface: Vlan3131, RPF nbr: 172.19.1.241 Outgoing interface list: (count: 1) Vlan3131, uptime: 07:42:18, pim, (RPF) (172.19.35.5/32, 239.225.1.3/32), uptime: 00:01:05, pim mrib ip Stats: 0/0 [Packets/Bytes], 0.000 bps Attached oif(s) : No Incoming interface: Vlan3105, RPF nbr: 172.19.0.83 Outgoing interface list: (count: 1) Vlan3131, uptime: 00:01:05, pim NPGVDC02-N7K# NPGVDC02-N7K# NPGVDC02-N7K# sh ip mroute 239.225.1.4 detail IP Multicast Routing Table for VRF "default" Total number of routes: 34 Total number of (*,G) routes: 12 Total number of (S,G) routes: 22 Total number of (*,G-prefix) routes: 0 (*, 239.225.1.4/32), uptime: 07:42:23, pim ip Stats: 0/0 [Packets/Bytes], 0.000 bps Attached oif(s) : No Incoming interface: Vlan3131, RPF nbr: 172.19.1.241 Outgoing interface list: (count: 1) Vlan3131, uptime: 07:42:23, pim, (RPF) (172.19.35.5/32, 239.225.1.4/32), uptime: 00:01:22, pim mrib ip Stats: 421/567508 [Packets/Bytes], 75.668 kbps Attached oif(s) : No Incoming interface: Vlan3105, RPF nbr: 172.19.0.83 Outgoing interface list: (count: 1) Vlan3131, uptime: 00:01:22, pim ... View more