The RPF neighbor is the L3 router/switch that is one hop closer to the source of the multicast stream.
If the RPF neighbor in the (, G) entry was 0.0.0.0 then that would mean the source was directly connected in vlan 5.
In your example the RPF neighbor is 10.1.3.1 which means there is a L3 device with an interface using that IP that is nearer the source of the mutlicast stream.
The RPF (Reverse Path Forwarding) check is done for all multicast packets on a L3 device ie. if the interface the mutlicast packet was received on is the same interface that the IP routing table says is used to route to the source IP then the RPF check is passed and the mutlicast packets can be forwarded to any other interfaces that have devices who want the stream.
If the packet arrives on an interface and according to the IP routing table the route to the source IP is not via that interface then the packet is dropped and not forwarded.
This is how PIM avoids routing loops for multicast traffic.
Edit - the above concerning the ip mroute entries is relevant to PIM dense mode as this is what you are running.
The RPF neighbor is the L3 router/switch that is one hop closer to the source of the multicast stream.
If the RPF neighbor in the (, G) entry was 0.0.0.0 then that would mean the source was directly connected in vlan 5.
In your example the RPF neighbor is 10.1.3.1 which means there is a L3 device with an interface using that IP that is nearer the source of the mutlicast stream.
The RPF (Reverse Path Forwarding) check is done for all multicast packets on a L3 device ie. if the interface the mutlicast packet was received on is the same interface that the IP routing table says is used to route to the source IP then the RPF check is passed and the mutlicast packets can be forwarded to any other interfaces that have devices who want the stream.
If the packet arrives on an interface and according to the IP routing table the route to the source IP is not via that interface then the packet is dropped and not forwarded.
This is how PIM avoids routing loops for multicast traffic.
Edit - the above concerning the ip mroute entries is relevant to PIM dense mode as this is what you are running.
