Hi, I'm trying to prefer R2 route for the multicast traffic (without using static mroute) from R1 (receiver) to R4 (source):
Receiver (R1): 10.10.10.10
Source~(R4): 10.0.45.5
I'm completely new to multicast and still trying to understand how it works but I understand that in multi-access segments, an upstream router is selected (R2 or R3) to deal with join/prune messages. In my newtork I have changed the R2-fa0/0 - ip pim dr-prio to select it as DR however it still doesn't seem to work the way that I want it to, as traffic is still going through R3. Can the DR influence the route selection or is the route selection purely based on the RIB?
I just don't understand why whilst R2 is showing as DR, join messages are still being dealt with by R3:
message from R2: *May 12 19:06:10.035: PIM(0): Received v2 Join/Prune on FastEthernet0/0 from 192.168.123.1, not to us
this is what I see from R1:
router1# 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.123.2 FastEthernet0/0 01:24:56/00:01:23 v2 200/ DR S P G
192.168.123.3 FastEthernet0/0 01:24:56/00:01:31 v2 1 / S P G
router1# show ip route 10.0.45.5
Routing entry for 10.0.45.5/32
Known via "ospf 1", distance 110, metric 114, type intra area
Last update from 192.168.123.3 on FastEthernet0/0, 01:25:41 ago
Routing Descriptor Blocks:
* 192.168.123.3, from 4.4.4.4, 01:25:41 ago, via FastEthernet0/0
Route metric is 114, traffic share count is 1
router1#show 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, E - Extranet,
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,
G - Received BGP C-Mroute, g - Sent BGP C-Mroute,
Q - Received BGP S-A Route, q - Sent BGP S-A Route,
V - RD & Vector, v - Vector
Outgoing interface flags: H - Hardware switched, A - Assert winner
Timers: Uptime/Expires
Interface state: Interface, Next-Hop or VCD, State/Mode
(10.0.45.5, 232.1.1.5), 01:59:24/00:02:42, flags: sLTI
Incoming interface: FastEthernet0/0, RPF nbr 192.168.123.3
Outgoing interface list:
Loopback1, Forward/Sparse, 00:56:49/00:02:42
router1#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.123.2 FastEthernet0/0 01:30:17/00:01:24 v2 200/ DR S P G
192.168.123.3 FastEthernet0/0 01:30:17/00:01:33 v2 1 / S P G
