Mulitcasting in PIM BSR Enviroment

R2 is the bsr router.
R3 and R4 are the RP candidates routers.
R7 will be acting like a multicast receiver and joining the groups 235.0.0.1 and 235.0.0.2
R5 or R6 will send multicast feeds to those groups.

R1 Config

ip multicast-routing
!
interface Loopback0
 ip address 1.1.1.1 255.255.255.255
 ip ospf 1 area 0
!
interface FastEthernet1/0
 ip address 192.168.12.1 255.255.255.0
 ip pim sparse-mode
 ip ospf 1 area 0
!
interface FastEthernet1/1
 ip address 192.168.14.1 255.255.255.0
 ip pim sparse-mode
 ip ospf 1 area 0
!
interface FastEthernet2/0
 ip address 192.168.15.1 255.255.255.0
 ip pim sparse-mode
 ip ospf 1 area 0
!
router ospf 1
 log-adjacency-changes

R2 Config

ip multicast-routing
!
interface Loopback0
 ip address 2.2.2.2 255.255.255.255
 ip pim sparse-mode
 ip ospf 1 area 0
!
interface FastEthernet1/0
 ip address 192.168.12.2 255.255.255.0
 ip pim sparse-mode
 ip ospf 1 area 0
!
interface FastEthernet1/1
 ip address 192.168.23.2 255.255.255.0
 ip pim sparse-mode
 ip ospf 1 area 0
!
interface FastEthernet2/0
 ip address 192.168.24.2 255.255.255.0
 ip pim sparse-mode
 ip ospf 1 area 0
!
router ospf 1
 log-adjacency-changes
!
ip pim bsr-candidate Loopback0
R3 Config

ip multicast-routing
!
interface Loopback0
 ip address 3.3.3.3 255.255.255.255
 ip pim sparse-mode
 ip ospf 1 area 0
!
interface FastEthernet1/0
 ip address 192.168.23.3 255.255.255.0
 ip pim sparse-mode
 ip ospf 1 area 0
 speed auto
 duplex auto
!
interface FastEthernet1/1
 ip address 192.168.34.3 255.255.255.0
 ip pim sparse-mode
 ip ospf 1 area 0
!
interface FastEthernet2/0
 ip address 192.168.36.3 255.255.255.0
 ip pim sparse-mode
 ip ospf 1 area 0
!
router ospf 1
 log-adjacency-changes
!
ip pim rp-candidate Loopback0

R4 Config

ip multicast-routing
!
interface Loopback0
 ip address 4.4.4.4 255.255.255.255
 ip pim sparse-mode
 ip ospf 1 area 0
!
interface FastEthernet1/0
 ip address 192.168.14.4 255.255.255.0
 ip pim sparse-mode
 ip ospf 1 area 0
!
interface FastEthernet1/1
 ip address 192.168.24.4 255.255.255.0
 ip pim sparse-mode
 ip ospf 1 area 0
!
interface FastEthernet2/0
 ip address 192.168.34.4 255.255.255.0
 ip pim sparse-mode
 ip ospf 1 area 0
!
interface FastEthernet2/1
 ip address 192.168.47.4 255.255.255.0
 ip pim sparse-mode
 ip ospf 1 area 0
!
router ospf 1
 log-adjacency-changes
!
ip pim rp-candidate Loopback0

R5 Config

interface FastEthernet0/0
 ip address 192.168.15.5 255.255.255.0
!
ip route 0.0.0.0 0.0.0.0 192.168.15.1

R6 Config

interface FastEthernet0/0
 ip address 192.168.36.6 255.255.255.0
!
ip route 0.0.0.0 0.0.0.0 192.168.36.3

R7 Config

interface FastEthernet0/0
 ip address 192.168.47.7 255.255.255.0
 ip igmp join-group 235.0.0.1
 ip igmp join-group 235.0.0.2
!
ip route 0.0.0.0 0.0.0.0 192.168.47.4

Verification

R1#show ip pim bsr-router
PIMv2 Bootstrap information
  BSR address: 2.2.2.2 (?)
  Uptime:      02:50:51, BSR Priority: 0, Hash mask length: 0
  Expires:     00:01:46

R1#show ip pim rp mapping
PIM Group-to-RP Mappings

Group(s) 224.0.0.0/4
  RP 4.4.4.4 (?), v2
    Info source: 2.2.2.2 (?), via bootstrap, priority 0, holdtime 150
         Uptime: 00:08:43, expires: 00:02:14
  RP 3.3.3.3 (?), v2
    Info source: 2.2.2.2 (?), via bootstrap, priority 0, holdtime 150
         Uptime: 02:39:36, expires: 00:02:15

-Since R7(multicast receiver) is requesting the multicast feeds for the 235.0.0.1 and 235.0.0.2, R4 has the *, group mroute entry for those groups.

R4#show ip mroute

(*, 235.0.0.1), 02:31:34/00:02:39, RP 4.4.4.4, flags: SJC
  Incoming interface: Null, RPF nbr 0.0.0.0
  Outgoing interface list:
    FastEthernet2/1, Forward/Sparse, 02:31:34/00:02:39

(*, 235.0.0.3), 00:23:32/00:02:39, RP 4.4.4.4, flags: S
  Incoming interface: Null, RPF nbr 0.0.0.0
  Outgoing interface list:
    FastEthernet1/0, Forward/Sparse, 00:07:05/00:02:39

(*, 224.0.1.40), 02:32:22/00:02:16, RP 0.0.0.0, flags: DCL
  Incoming interface: Null, RPF nbr 0.0.0.0
  Outgoing interface list:
    Loopback0, Forward/Sparse, 02:32:22/00:02:16

-When R5 starts to send traffic to 235.0.0.1,

R5#ping 235.0.0.1 repeat 100
Reply to request 0 from 192.168.47.7, 200 ms
Reply to request 1 from 192.168.47.7, 104 ms
Reply to request 1 from 192.168.47.7, 128 ms

-Now we see R4 and R1 updates it mroute table. Both routers are using 4.4.4.4(R4 Loopback 0) as the RP address.

R4#show ip mroute

(*, 235.0.0.1), 02:34:53/stopped, RP 4.4.4.4, flags: SJC
  Incoming interface: Null, RPF nbr 0.0.0.0
  Outgoing interface list:
    FastEthernet2/1, Forward/Sparse, 02:34:53/00:02:14

(192.168.15.5, 235.0.0.1), 00:00:12/00:02:50, flags: T
  Incoming interface: FastEthernet1/0, RPF nbr 192.168.14.1
  Outgoing interface list:
    FastEthernet2/1, Forward/Sparse, 00:00:12/00:02:47

(*, 224.0.1.40), 02:35:41/00:01:58, RP 0.0.0.0, flags: DCL
  Incoming interface: Null, RPF nbr 0.0.0.0
  Outgoing interface list:
    Loopback0, Forward/Sparse, 02:35:41/00:01:58

R1#show ip mroute

(*, 235.0.0.1), 00:00:45/stopped, RP 4.4.4.4, flags: SPF
  Incoming interface: FastEthernet1/1, RPF nbr 192.168.14.4
  Outgoing interface list: Null

(192.168.15.5, 235.0.0.1), 00:00:45/00:02:48, flags: FT
  Incoming interface: FastEthernet2/0, RPF nbr 0.0.0.0
  Outgoing interface list:
    FastEthernet1/1, Forward/Sparse, 00:00:45/00:02:46

(*, 224.0.1.40), 00:23:51/00:02:43, RP 0.0.0.0, flags: DPL
  Incoming interface: Null, RPF nbr 0.0.0.0
  Outgoing interface list: Null

Multicast Troubleshooting relating to RP

We will be using the same topology and config as the previous lab.
But in this lab I will raise the R3 candidate-rp priority value to 1 to make sure R4 is the RP used by all the routers.

R3 Config
ip pim rp-candidate Loopback0 priority 1

R1#show ip pim rp mapping
PIM Group-to-RP Mappings

Group(s) 224.0.0.0/4
  RP 4.4.4.4 (?), v2
    Info source: 2.2.2.2 (?), via bootstrap, priority 0, holdtime 150
         Uptime: 00:32:13, expires: 00:01:53
  RP 3.3.3.3 (?), v2
    Info source: 2.2.2.2 (?), via bootstrap, priority 1, holdtime 150
         Uptime: 03:03:06, expires: 00:01:54

R4#show ip mroute

(*, 235.0.0.1), 00:01:33/00:02:23, RP 4.4.4.4, flags: SJC
  Incoming interface: Null, RPF nbr 0.0.0.0
  Outgoing interface list:
    FastEthernet2/1, Forward/Sparse, 00:01:33/00:02:23

(*, 235.0.0.2), 00:00:06/00:02:53, RP 4.4.4.4, flags: SJC
  Incoming interface: Null, RPF nbr 0.0.0.0
  Outgoing interface list:
    FastEthernet2/1, Forward/Sparse, 00:00:06/00:02:53

(*, 224.0.1.40), 00:02:35/00:02:12, RP 0.0.0.0, flags: DCL
  Incoming interface: Null, RPF nbr 0.0.0.0
  Outgoing interface list:
    Loopback0, Forward/Sparse, 00:02:35/00:02:12

Then I will inject one fault which could lead R5 not being able to ping 235.0.0.1 to which address R7 is listening.


R5#ping 235.0.0.1 repeat 10

Type escape sequence to abort.
Sending 10, 100-byte ICMP Echos to 235.0.0.1, timeout is 2 seconds:
....

-It is failed. So let's try to check the RP mapping information and pim adjacency between R1 and R4.
We will see that R4(4.4.4.4) is the prefer RP to be used. We have pim adjacency between R1 and R4.
R4 has multicast receiver for 235.0.0.1 and 235.0.0.2. Then why it is failed at the first place.

R1#show ip pim rp mapping
PIM Group-to-RP Mappings

Group(s) 224.0.0.0/4
  RP 4.4.4.4 (?), v2
    Info source: 2.2.2.2 (?), via bootstrap, priority 0, holdtime 150
         Uptime: 00:02:00, expires: 00:02:11
  RP 3.3.3.3 (?), v2
    Info source: 2.2.2.2 (?), via bootstrap, priority 1, holdtime 150

R1#show ip pim neighbor
PIM Neighbor Table
Mode: B - Bidir Capable, DR - Designated Router, N - Default DR Priority,
      P - Proxy Capable, S - State Refresh Capable, G - GenID Capable
Neighbor          Interface                Uptime/Expires    Ver   DR
Address                                                            Prio/Mode
192.168.12.2      FastEthernet1/0          03:28:29/00:01:29 v2    1 / DR S P G
192.168.14.4      FastEthernet1/1          02:32:11/00:01:16 v2    1 / DR S P G


R4#show ip mroute

(*, 235.0.0.1), 00:10:03/00:02:53, RP 4.4.4.4, flags: SJC
  Incoming interface: Null, RPF nbr 0.0.0.0
  Outgoing interface list:
    FastEthernet2/1, Forward/Sparse, 00:10:03/00:02:53

(*, 235.0.0.2), 00:08:36/00:02:52, RP 4.4.4.4, flags: SJC
  Incoming interface: Null, RPF nbr 0.0.0.0
  Outgoing interface list:
    FastEthernet2/1, Forward/Sparse, 00:08:36/00:02:52

(*, 224.0.1.40), 00:11:05/00:02:39, RP 0.0.0.0, flags: DCL
  Incoming interface: Null, RPF nbr 0.0.0.0
  Outgoing interface list:
    Loopback0, Forward/Sparse, 00:11:05/00:02:39

-Now let's try to ping whether we can reach the RP address itself or not.

R5#ping 4.4.4.4

Type escape sequence to abort.
Sending 5, 100-byte ICMP Echos to 5.5.5.5, timeout is 2 seconds:
U.U.U
Success rate is 0 percent (0/5)

-We find that even though we have RP(4.4.4.4) information in the multicast routing domain wide, but in fact we don't even have the reach-ability to RP. It is really tricky, right. We have RP information that we can reach and essentially we are using that RP for multicast traffic forwarding.

-This is the fault I injected by not advertising the R4 Loopback0 network into OSPF.
So I will  correct this back.

R4(config)#int loo 0
R4(config-if)#ip ospf 1 area 0


-Now R5 can ping to RP and multicast feeds sending to 235.0.0.1 is successful.

R5#ping 4.4.4.4
!!!!!
Success rate is 100 percent (5/5), round-trip min/avg/max = 24/57/92 ms

R5#ping 235.0.0.1
Reply to request 0 from 192.168.47.7, 192 ms

Multicast MDT Using SSM

PE Routers
R1 Config

vrf definition one
 rd 1:1
 route-target export 1:1
 route-target import 1:1
  address-family ipv4
 mdt default 232.0.0.1
 mdt data 232.1.1.0 0.0.0.255
ip multicast-routing
ip multicast-routing vrf one
interface Loopback0
 ip address 10.10.10.10 255.255.255.255
 ip pim sparse-mode
interface FastEthernet1/0
 ip address 192.168.12.1 255.255.255.0
 ip pim sparse-mode
 mpls ip
interface FastEthernet1/1
 vrf forwarding one
 ip address 192.168.14.1 255.255.255.0
 ip pim sparse-mode
router ospf 1
 network 10.10.10.10 0.0.0.0 area 0
 network 192.168.12.1 0.0.0.0 area 0
router bgp 13
 no bgp default ipv4-unicast
 bgp log-neighbor-changes
 neighbor 30.30.30.30 remote-as 13
 neighbor 30.30.30.30 update-source Loopback0
 neighbor 60.60.60.60 remote-as 13
 address-family vpnv4
  neighbor 30.30.30.30 activate
  neighbor 30.30.30.30 send-community extended
  neighbor 60.60.60.60 activate
  neighbor 60.60.60.60 send-community extended
 address-family ipv4 mdt
  neighbor 30.30.30.30 activate
  neighbor 30.30.30.30 send-community extended
  neighbor 60.60.60.60 activate
  neighbor 60.60.60.60 send-community extended
 address-family ipv4 vrf one
  redistribute connected
  redistribute static
ip pim ssm default
ip route vrf one 40.40.40.40 255.255.255.255 192.168.14.4
ip route vrf one 192.168.49.0 255.255.255.0 192.168.14.4

R3 Config

vrf definition one
 rd 1:1
 route-target export 1:1
 route-target import 1:1
 address-family ipv4
 mdt default 232.0.0.1
 mdt data 232.3.3.0 0.0.0.255
ip multicast-routing
ip multicast-routing vrf one
interface Loopback0
 ip address 30.30.30.30 255.255.255.255
 ip pim sparse-mode
interface FastEthernet1/0
 ip address 192.168.23.3 255.255.255.0
 ip pim sparse-mode
 mpls ip
interface FastEthernet1/1
 vrf forwarding one
 ip address 192.168.35.3 255.255.255.0
 ip pim sparse-mode
router ospf 1
 network 30.30.30.30 0.0.0.0 area 0
 network 192.168.23.3 0.0.0.0 area 0
router bgp 13
 no bgp default ipv4-unicast
 bgp log-neighbor-changes
 neighbor 10.10.10.10 remote-as 13
 neighbor 10.10.10.10 update-source Loopback0
 neighbor 60.60.60.60 remote-as 13
 address-family vpnv4
  neighbor 10.10.10.10 activate
  neighbor 10.10.10.10 send-community extended
  neighbor 60.60.60.60 activate
  neighbor 60.60.60.60 send-community extended
 address-family ipv4 mdt
  neighbor 10.10.10.10 activate
  neighbor 10.10.10.10 send-community extended
  neighbor 60.60.60.60 activate
  neighbor 60.60.60.60 send-community extended
 address-family ipv4 vrf one
  no synchronization
  redistribute connected
  redistribute static
ip pim ssm default
ip route vrf one 192.168.105.0 255.255.255.0 192.168.35.5

R6 Config

vrf definition one
 rd 1:1
 route-target export 1:1
 route-target import 1:1
 address-family ipv4
 mdt default 232.0.0.1
 mdt data 232.6.6.0 0.0.0.255
ip multicast-routing
ip multicast-routing vrf one
interface Loopback0
 ip address 60.60.60.60 255.255.255.255
 ip pim sparse-mode
interface FastEthernet1/0
 ip address 192.168.26.6 255.255.255.0
 ip pim sparse-mode
 mpls ip
interface FastEthernet1/1
 vrf forwarding one
 ip address 192.168.67.6 255.255.255.0
 ip pim sparse-mode
router ospf 1
 network 60.60.60.60 0.0.0.0 area 0
 network 192.168.26.6 0.0.0.0 area 0
router bgp 13
 no bgp default ipv4-unicast
 bgp log-neighbor-changes
 neighbor rr peer-group
 neighbor rr remote-as 13
 neighbor rr update-source Loopback0
 neighbor 10.10.10.10 peer-group rr
 neighbor 30.30.30.30 peer-group rr
 address-family vpnv4
  neighbor rr send-community extended
  neighbor rr next-hop-self
  neighbor 10.10.10.10 activate
  neighbor 30.30.30.30 activate
 address-family ipv4 mdt
  neighbor 10.10.10.10 activate
  neighbor 30.30.30.30 activate
 address-family ipv4 vrf one
  no synchronization
  redistribute connected
ip pim ssm default

P Router
R2 Config

interface Loopback0
 ip address 20.20.20.20 255.255.255.255
 ip pim sparse-mode
interface FastEthernet1/0
 ip address 192.168.12.2 255.255.255.0
 ip pim sparse-mode
 mpls ip
interface FastEthernet1/1
 ip address 192.168.23.2 255.255.255.0
 ip pim sparse-mode
 mpls ip
interface FastEthernet2/0
 ip address 192.168.26.2 255.255.255.0
 ip pim sparse-mode
 mpls ip
router ospf 1
 network 20.20.20.20 0.0.0.0 area 0
 network 192.168.12.2 0.0.0.0 area 0
 network 192.168.23.2 0.0.0.0 area 0
 network 192.168.26.2 0.0.0.0 area 0
ip pim bsr-candidate Loopback0 0
ip pim rp-candidate Loopback0
ip pim ssm default

CE Routers 
R4 Config

ip multicast-routing
interface Loopback0
 ip address 40.40.40.40 255.255.255.255
 ip pim sparse-mode!
interface FastEthernet1/0
 ip address 192.168.14.4 255.255.255.0
 ip pim sparse-mode
interface FastEthernet1/1
 ip address 192.168.49.4 255.255.255.0
 ip pim sparse-mode
ip pim bsr-candidate Loopback0 0
ip pim rp-candidate Loopback0
ip route 0.0.0.0 0.0.0.0 192.168.14.1

R5 Config

ip multicast-routing
interface FastEthernet1/0
 ip address 192.168.35.5 255.255.255.0
 ip pim sparse-mode
interface FastEthernet1/1
 ip address 192.168.105.5 255.255.255.0
 ip pim sparse-mode
ip route 0.0.0.0 0.0.0.0 192.168.35.3

R7 Config

ip multicast-routing
interface FastEthernet1/0
 ip address 192.168.67.7 255.255.255.0
 ip pim sparse-mode
ip route 0.0.0.0 0.0.0.0 192.168.67.6

C Router
R9 Config

ip multicast-routing
interface FastEthernet0/0
 ip address 192.168.49.9 255.255.255.0
 ip pim sparse-mode
ip route 0.0.0.0 0.0.0.0 192.168.49.4

R10 Config

ip multicast-routing
interface FastEthernet0/0
 ip address 192.168.105.10 255.255.255.0
 ip pim sparse-mode
ip route 0.0.0.0 0.0.0.0 192.168.105.5

Verification

R9#show ip pim rp map
PIM Group-to-RP Mappings

Group(s) 224.0.0.0/4
  RP 40.40.40.40 (?), v2
    Info source: 40.40.40.40 (?), via bootstrap, priority 0, holdtime 150
         Uptime: 00:09:16, expires: 00:02:10

R1# show bgp ipv4 mdt all

   Network          Next Hop            Metric LocPrf Weight Path
Route Distinguisher: 1:1 (default for vrf one)
*> 10.10.10.10/32   0.0.0.0                                0 ?
*>i30.30.30.30/32   30.30.30.30              0    100      0 ?
*>i60.60.60.60/32   60.60.60.60              0    100      0 ?

R7(config)#interface fast1/0
R7(config-if)#ip igmp join-group 239.0.0.2

R10(config)#interface fast0/0
R10(config-if)#ip igmp join-group 239.0.0.1

R9#ping 239.0.0.1 repeat 10000
Reply to request 0 from 192.168.105.10, 136 ms
Reply to request 1 from 192.168.105.10, 168 ms

R9#ping 239.0.0.2 repeat 1000
Reply to request 19 from 192.168.67.7, 420 ms
Reply to request 20 from 192.168.67.7, 224 ms


R2#show ip mroute
(10.10.10.10, 232.0.0.1), 00:13:05/00:03:11, flags: sT
  Incoming interface: FastEthernet1/0, RPF nbr 192.168.12.1
  Outgoing interface list:
    FastEthernet2/0, Forward/Sparse, 00:13:05/00:03:11
    FastEthernet1/1, Forward/Sparse, 00:13:05/00:03:10

(60.60.60.60, 232.0.0.1), 00:13:07/00:03:08, flags: sT
  Incoming interface: FastEthernet2/0, RPF nbr 192.168.26.6
  Outgoing interface list:
    FastEthernet1/0, Forward/Sparse, 00:13:07/00:03:08
    FastEthernet1/1, Forward/Sparse, 00:13:07/00:03:08

(30.30.30.30, 232.0.0.1), 00:13:26/00:02:55, flags: sT
  Incoming interface: FastEthernet1/1, RPF nbr 192.168.23.3
  Outgoing interface list:
    FastEthernet1/0, Forward/Sparse, 00:13:26/00:02:52
    FastEthernet2/0, Forward/Sparse, 00:13:26/00:02:55

(10.10.10.10, 232.1.1.1), 00:00:31/00:02:58, flags: sT
  Incoming interface: FastEthernet1/0, RPF nbr 192.168.12.1
  Outgoing interface list:
    FastEthernet2/0, Forward/Sparse, 00:00:31/00:02:58

(10.10.10.10, 232.1.1.0), 00:01:35/00:02:53, flags: sT
  Incoming interface: FastEthernet1/0, RPF nbr 192.168.12.1
  Outgoing interface list:
    FastEthernet1/1, Forward/Sparse, 00:01:35/00:02:53

(*, 224.0.1.40), 00:15:49/00:02:19, RP 0.0.0.0, flags: DCL
  Incoming interface: Null, RPF nbr 0.0.0.0
  Outgoing interface list:
    Loopback0, Forward/Sparse, 00:15:46/00:02:19

R1#show ip int bri
Interface              IP-Address      OK? Method Status                Protocol
FastEthernet0/0        unassigned      YES NVRAM  administratively down down
FastEthernet1/0        192.168.12.1    YES NVRAM  up                    up
FastEthernet1/1        192.168.14.1    YES NVRAM  up                    up
Loopback0              10.10.10.10     YES NVRAM  up                    up
Tunnel0                192.168.12.1    YES unset  up                    up
Tunnel1                192.168.14.1    YES unset  up                    up
Tunnel2                10.10.10.10     YES unset  up                    up


R1#show ip mroute vrf one

(*, 239.0.0.1), 00:03:40/00:02:46, RP 40.40.40.40, flags: S
  Incoming interface: FastEthernet1/1, RPF nbr 192.168.14.4
  Outgoing interface list:
    Tunnel2, Forward/Sparse, 00:03:40/00:02:46

(192.168.49.9, 239.0.0.1), 00:03:07/00:00:22, flags: T
  Incoming interface: FastEthernet1/1, RPF nbr 192.168.14.4
  Outgoing interface list:
    Tunnel2, Forward/Sparse, 00:03:07/00:03:18

(*, 239.0.0.2), 00:02:01/00:03:28, RP 40.40.40.40, flags: S
  Incoming interface: FastEthernet1/1, RPF nbr 192.168.14.4
  Outgoing interface list:
    Tunnel2, Forward/Sparse, 00:02:01/00:03:28

(192.168.49.9, 239.0.0.2), 00:01:58/00:01:31, flags: T
  Incoming interface: FastEthernet1/1, RPF nbr 192.168.14.4
  Outgoing interface list:
    Tunnel2, Forward/Sparse, 00:01:58/00:03:28

(*, 224.0.1.40), 00:17:29/00:02:36, RP 0.0.0.0, flags: DPL
  Incoming interface: Null, RPF nbr 0.0.0.0
  Outgoing interface list: Null

R3#show ip mroute

(10.10.10.10, 232.0.0.1), 00:43:14/stopped, flags: sTIZ
  Incoming interface: FastEthernet1/0, RPF nbr 192.168.23.2
  Outgoing interface list:
    MVRF one, Forward/Sparse, 00:43:14/00:01:45

(60.60.60.60, 232.0.0.1), 00:43:16/stopped, flags: sTIZ
  Incoming interface: FastEthernet1/0, RPF nbr 192.168.23.2
  Outgoing interface list:
    MVRF one, Forward/Sparse, 00:43:16/00:01:43

(30.30.30.30, 232.0.0.1), 00:43:34/00:03:17, flags: sT
  Incoming interface: Loopback0, RPF nbr 0.0.0.0
  Outgoing interface list:
    FastEthernet1/0, Forward/Sparse, 00:43:34/00:03:17

(10.10.10.10, 232.1.1.0), 00:00:56/00:02:03, flags: sTIZ
  Incoming interface: FastEthernet1/0, RPF nbr 192.168.23.2
  Outgoing interface list:
    MVRF one, Forward/Sparse, 00:00:56/00:02:03

(*, 224.0.1.40), 00:45:38/00:02:25, RP 0.0.0.0, flags: DCL
  Incoming interface: Null, RPF nbr 0.0.0.0
  Outgoing interface list:
    Loopback0, Forward/Sparse, 00:45:34/00:02:25


R3#show ip mroute vrf one

(*, 239.0.0.1), 00:03:52/00:02:35, RP 40.40.40.40, flags: S
  Incoming interface: Tunnel1, RPF nbr 10.10.10.10
  Outgoing interface list:
    FastEthernet1/1, Forward/Sparse, 00:03:52/00:02:35

(192.168.49.9, 239.0.0.1), 00:03:19/00:00:10, flags: TY
  Incoming interface: Tunnel1, RPF nbr 10.10.10.10, MDT:[10.10.10.10,232.1.1.0]/00:01:50
  Outgoing interface list:
    FastEthernet1/1, Forward/Sparse, 00:03:19/00:03:07

(*, 239.0.0.2), 00:02:05/stopped, RP 40.40.40.40, flags: SP
  Incoming interface: Tunnel1, RPF nbr 10.10.10.10
  Outgoing interface list: Null

(192.168.49.9, 239.0.0.2), 00:02:05/00:01:47, flags: PT
  Incoming interface: Tunnel1, RPF nbr 10.10.10.10, MDT:[10.10.10.10,232.1.1.1]/00:01:50
  Outgoing interface list: Null

(*, 224.0.1.40), 00:17:02/00:02:59, RP 0.0.0.0, flags: DPL
  Incoming interface: Null, RPF nbr 0.0.0.0
  Outgoing interface list: Null