This lab is setup for static Rendezvous Point, you may use this in a small environment with only one or two multicast sources, static RP is managed by manually configuring each router with “ip pim rp-address x.x.x.x”. As you can probably tell manually updating each router with a new RP could be time conusming on larger networks, so we will cover other ways to assign or elect the RP in my future blogs.
Static RP topology
Attached are the config’s for each router (Router Configs). As I’m using GNS3 I had to enter commands “no ip route-cache” and “no ip mroute-cache” on each PIM interface. Also add “no ip cef”. You won’t need this for physical routers.
Now lets confirm our configurations with some well known commands.
From R4 we need to confirm the IGMP memberships “show ip igmp groups” will show all the IGMP joins the router has recieved from hosts wanting to join the multicast stream.
R4#sh ip igmp groups
IGMP Connected Group Membership
Group Address Interface Uptime Expires Last Reporter Group Accounted
239.4.4.4 FastEthernet0/0 00:21:26 stopped 10.10.10.4
Next we confirm the RP with the command ” show ip pim rp” lets do this from R2, this will show us all RP’s and the multicast group address they are responsible for.
R2#sh ip pim rp
Group: 239.4.4.4, RP: 10.10.10.3, v2, uptime 00:03:55, expires never
Group: 224.0.1.40, RP: 10.10.10.3, v2, uptime 00:24:12, expires never
Next from R1 we initate some traffic using “ping 239.4.4.4” you should get a reply, now we can run the command from R2 “show ip mroute summary”. This will show us the shared tree and source tree for the multicast source.
R2#sh ip mroute summary
IP Multicast Routing Table
(*, 239.4.4.4), 00:02:47/stopped, RP 10.10.10.3, OIF count: 0, flags: SPF
(56.56.56.1, 239.4.4.4), 00:02:47/00:00:46, OIF count: 1, flags: FT
This confirms our multicast setup is working correctly.
If you are struggling with source and shared tree check out this blog (http://packetlife.net/blog/2008/oct/20/pim-sm-source-versus-shared-trees)
RH
all-things-networking 