I am doing some labs on multicast with bidir and I am using autorp and keep getting this wild card address. yeah the lab works but in my lab I should be getting specific shared tree address like (*,244.5.5.5) that is the ip pim join-group 224.5.5.5 I am using? What am I doing wrong?
I though on all the routers I would be getting the speicific address not the wild card address? or what I mean by wild card is the entire range address vs the more specific? can you help me figure out why I keep getting this ?
Thank you.
Robert
SOLVE BY ME hahahaah my routing in GNS3 was bad. The training begins…check full connectivity as number 1 check then all rest will be solid. GNS3 is known for putting interfaces down by a a ghost admin so I need to always check my full routing. I am keeping A TCL script to check each lab before i start! and during. hope this help others
crap it wasn’t fixed I still get the wild card (,224.0.0.0/4) group ip mroute address and not the specific join (,224.5.5.5) that I am suppose to only get? what am I doing wrong. I have all the configs correct on each router
R3 is the bsr and rp candidate with this.
R3#show run | s pim
ip pim sparse-mode
ip pim sparse-mode
ip pim sparse-mode
ip pim bidir-enable
ip pim bsr-candidate Loopback0 0
ip pim rp-candidate Loopback0 bidir
R3#
R1, R2, R4, R5 have this:
R1#show run | i pim
ip pim sparse-mode
ip pim sparse-mode
ip pim sparse-mode
ip pim bidir-enable
R1#
R5 is off of R4 and has this:
interface Loopback0
ip address 50.1.1.1 255.0.0.0
ip pim sparse-mode
ip igmp join-group 224.5.5.5
!Hi Robert,
Did you get this to work? Just to be sure, I did adapt my PIM BIDIR example that uses static RP:
I removed the static RP commands:
R1,R2 and R3:
(config)#no ip pim rp-address 1.1.1.1 bidir
And added BSR:
R1(config)#ip pim bsr-candidate Loopback0 0
R1(config)#ip pim rp-candidate Loopback0 bidir
This works for me on Cisco VIRL:
R1#show ip pim bsr-router
PIMv2 Bootstrap information
This system is the Bootstrap Router (BSR)
BSR address: 1.1.1.1 (?)
Uptime: 00:01:33, BSR Priority: 0, Hash mask length: 0
Next bootstrap message in 00:00:27
Candidate RP: 1.1.1.1(Loopback0)
Holdtime 150 seconds
Advertisement interval 60 seconds
Next advertisement in 00:00:19
R2 recognizes it:
R2#show ip pim bsr-router
PIMv2 Bootstrap information
BSR address: 1.1.1.1 (?)
Uptime: 00:11:21, BSR Priority: 0, Hash mask length: 0
Expires: 00:01:36
And R3:
R3#show ip pim bsr-router
PIMv2 Bootstrap information
BSR address: 1.1.1.1 (?)
Uptime: 00:14:28, BSR Priority: 0, Hash mask length: 0
Expires: 00:01:32
They see the RP mapping:
R2#show ip pim rp mapping
PIM Group-to-RP Mappings
Group(s) 224.0.0.0/4
RP 1.1.1.1 (?), v2, bidir
Info source: 1.1.1.1 (?), via bootstrap, priority 0, holdtime 150
Uptime: 00:13:06, expires: 00:02:10
R3:
R3#show ip pim rp mapping
PIM Group-to-RP Mappings
Group(s) 224.0.0.0/4
RP 1.1.1.1 (?), v2, bidir
Info source: 1.1.1.1 (?), via bootstrap, priority 0, holdtime 150
Uptime: 00:15:29, expires: 00:01:46
Let’s join a group:
R5(config-if)#ip igmp join-group 224.5.5.5
And send some traffic:
R4#ping 224.5.5.5
Type escape sequence to abort.
Sending 1, 100-byte ICMP Echos to 224.5.5.5, timeout is 2 seconds:
Reply to request 0 from 192.168.35.5, 10 ms
Here’s the multicast routing table:
R1#show ip mroute 224.5.5.5
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,
N - Received BGP Shared-Tree Prune, n - BGP C-Mroute suppressed,
Q - Received BGP S-A Route, q - Sent BGP S-A Route,
V - RD & Vector, v - Vector, p - PIM Joins on route,
x - VxLAN group
Outgoing interface flags: H - Hardware switched, A - Assert winner, p - PIM Join
Timers: Uptime/Expires
Interface state: Interface, Next-Hop or VCD, State/Mode
(*, 224.5.5.5), 00:15:39/00:02:35, RP 1.1.1.1, flags: B
Bidir-Upstream: Null, RPF nbr 0.0.0.0
Outgoing interface list:
GigabitEthernet0/2, Forward/Sparse, 00:15:39/00:02:35