Hi all
The same scenario that I have mentioned in my earlier mail but I have used
tunnel interface.
r1 10.20.30.41 -----------asa----------------- 10.20.30.42 r2
10.20.30.47
ASA config
========
access-list out extended permit gre any any
access-list in extended permit gre any any
access-group out in interface outside
access-group in in interface inside
R1 config
=======
interface Tunnel0
ip address 1.2.3.4 255.255.255.0
tunnel source GigabitEthernet0/1
tunnel destination 10.20.30.42
interface GigabitEthernet0/1
ip address 10.20.30.41 255.255.255.0
ip igmp join-group 239.1.2.3
R2 config
=======
interface Tunnel0
ip address 1.2.3.7 255.255.255.0
tunnel source GigabitEthernet0/1
tunnel destination 10.20.30.41
The ping from r2 to 239.1.2.3 was not successful. I didn't get reply.
I enabled multicasting routing on r1 and r2 as following and the ping was
successful.
R1 config
=======
ip pim rp-address 10.20.30.42
ip multicasting-routing
interface GigabitEthernet0/1
ip address 10.20.30.41 255.255.255.0
ip pim sparse-mode
ip igmp join-group 239.1.2.3
interface Tunnel0
ip address 1.2.3.4 255.255.255.0
ip pim sparse-mode
tunnel source GigabitEthernet0/1
tunnel destination 10.20.30.42
R2 config
=======
ip pim rp-address 10.20.30.42
interface Tunnel0
ip address 1.2.3.7 255.255.255.0
ip pim sparse-mode
tunnel source GigabitEthernet0/1
tunnel destination 10.20.30.41
interface GigabitEthernet0/1
ip address 10.20.30.42 255.255.255.0
Any thoughts? It should have worked without enabling multicasting routing
right?
With regards
Kings
_______________________________________________
For more information regarding industry leading CCIE Lab training, please visit
www.ipexpert.com
