Hi Paul
I've changed config, result is the same:
00:09:52: IP(0): s=10.242.1.2 (Vlan2018) d=233.32.210.77 id=55823, ttl=28, prot=17, len=1358(1344), not RPF interface
00:09:52: IP(0): s=10.242.1.2 (Vlan2018) d=233.32.210.77 id=55824, ttl=28, prot=17, len=1358(1344), not RPF interface
00:09:52: IP(0): s=10.242.1.2 (Vlan2018) d=233.32.210.77 id=55825, ttl=28, prot=17, len=1358(1344), not RPF interface
00:09:52: IP(0): s=10.242.1.2 (Vlan2018) d=233.32.210.77 id=55826, ttl=28, prot=17, len=1358(1344), not RPF interface
00:09:52: IP(0): s=10.242.1.2 (Vlan2018) d=233.32.210.77 id=55827, ttl=28, prot=17, len=1358(1344), not RPF interface
R1#sh ip pim int
Address Interface Ver/ Nbr Query DR DR
Mode Count Intvl Prior
10.1.1.2 Loopback0 v2/S 0 30 1 10.1.1.2
192.168.12.73 FastEthernet1/0/2 v2/S 1 30 1 192.168.12.74
192.168.15.1 FastEthernet1/0/3 v2/S 0 30 1 0.0.0.0
10.242.128.50 Vlan2018 v2/S 1 30 1 10.242.128.50
R1#sh ip mroute
IP Multicast Routing Table
Flags: D - Dense, S - Sparse, B - Bidir Group, s - SSM Group, C - Connected,
L - Local, P - Pruned, R - RP-bit set, F - Register flag,
T - SPT-bit set, J - Join SPT, M - MSDP created entry,
X - Proxy Join Timer Running, A - Candidate for MSDP Advertisement,
U - URD, I - Received Source Specific Host Report,
Z - Multicast Tunnel, z - MDT-data group sender,
Y - Joined MDT-data group, y - Sending to MDT-data group
Outgoing interface flags: H - Hardware switched, A - Assert winner
Timers: Uptime/Expires
Interface state: Interface, Next-Hop or VCD, State/Mode
(*, 233.32.210.77), 00:13:59/00:02:58, RP 10.1.1.10, flags: SP
Incoming interface: FastEthernet1/0/2, RPF nbr 192.168.12.74
Outgoing interface list: Null
(*, 224.0.1.40), 00:14:06/00:02:32, RP 10.1.1.10, flags: SJCL
Incoming interface: FastEthernet1/0/2, RPF nbr 192.168.12.74
Outgoing interface list:
Loopback0, Forward/Sparse, 00:14:04/00:02:32
R1#sh run int vlan 2018
Building configuration...
Current configuration : 106 bytes
!
interface Vlan2018
ip address 10.242.128.50 255.255.255.240
ip pim sparse-mode
load-interval 30
end
R1#sh ip route 10.242.1.2
Routing entry for 10.242.1.2/32
Known via "static", distance 1, metric 0
Redistributing via ospf 100
Advertised by ospf 100 subnets
Routing Descriptor Blocks:
* 10.242.128.49
Route metric is 0, traffic share count is 1
R1#sh ip route 10.242.128.49
Routing entry for 10.242.128.48/28
Known via "connected", distance 0, metric 0 (connected, via interface)
Routing Descriptor Blocks:
* directly connected, via Vlan2018
Route metric is 0, traffic share count is 1
R1#trace 10.242.1.2
Type escape sequence to abort.
Tracing the route to 10.242.1.2
1 10.242.128.49 0 msec 8 msec 0 msec
2 * * *
3 * * *
4 * *
10.242.1.2 and 10.242.128.49 are in provider network and dont reply to ping.
Provider send me static multicast group 233.32.210.77.
I'm really confused what is wrong.
P.S. PIM passive mode means that the device will not send PIM messages on the interface nor will it accept PIM messages from other devices across this interface. The device will instead consider that it is the only PIM device on the network and thus act as the DR and also as the DF for all bidir-PIM group ranges. Isnt it?
https://www.cisco.com/c/en/us/td/docs/ios-xml/ios/ipmulti_pim/configuration/15-s/imc-pim-15-s-book/imc_stub_routing.html
