Solved: Multicast RP problem

bapatsubodh · ‎04-23-2009

Hi,

We are testing multicast in test environment between R1 and R2 connected by point-to-point serial link. configuration is as follows

R1.

ip multicast-routing

int fa0/0

ip pim sparse-dence

ip igmp join-group 224.1.1.1

int s1/0

ip pim sparse-dence

ip pim send-rp-announce s1/0 scope 5

ip pim send-rp-discovery s1/0 scope 5

R2.

ip multicast-routing

int s1/0

ip pim sparse-dence

int fa0/0

ip pim sparse-dence

I can see the neighbor relationship

by command

show ip pim neighbor

show ip pim interface also shows that pim Sp.Den mode is enabled on all the interfaces. But when I give command

sh ip pim rp on R2 is doesnt show any RP.

On R1 it shows RP as directly connected.

Surprisingly if I ping to 224.1.1.1 from R2 is gives the response as reachable from next-hop address in .... miliseconds.

Show ip mroute on R2 shows only 224.0.1.39 and 224.0.1.40 listener addresses but no group of 224.1.1.1.

Do we really need a multicast stream generator running? Can ip ignp join-group command server the purpose.

Any experience please share.

Thanks in advance

Subodh

Edison Ortiz · ‎04-23-2009

Subodh,

Not sure what you are missing but it works for me:

R1(f0/0)<--->(f0/0)R2

R1 has the loopback emulating the host with a join for group 224.1.1.1

interface Loopback0

ip address 1.1.1.1 255.255.255.255

ip pim sparse-dense-mode

ip igmp join-group 224.1.1.1

no clns route-cache

end

It's also running PIM Auto-RP:

R1#sh run | i send

ip pim send-rp-announce FastEthernet0/0 scope 16

ip pim send-rp-discovery FastEthernet0/0 scope 16

!

R1#sh ip pim rp mapping

PIM Group-to-RP Mappings

This system is an RP (Auto-RP)

This system is an RP-mapping agent (FastEthernet0/0)

Group(s) 224.0.0.0/4

RP 192.168.12.1 (?), v2v1

Info source: 192.168.12.1 (?), elected via Auto-RP

Uptime: 00:03:52, expires: 00:02:04

R2 can see the Auto-RP announcement:

R2#sh ip pim rp mapping

PIM Group-to-RP Mappings

Group(s) 224.0.0.0/4

RP 192.168.12.1 (?), v2v1

Info source: 192.168.12.1 (?), elected via Auto-RP

Uptime: 00:04:34, expires: 00:02:22

You can also see it on the mroute as RP and mapping agent MCAST groups:

R2#sh ip mroute | i 192.168.12.1

(192.168.12.1, 224.0.1.39), 00:00:23/00:02:37, flags: PT

(192.168.12.1, 224.0.1.40), 00:03:24/00:02:33, flags: PLT

On R1, I can see the IGMP join for 224.1.1.1

R1#sh ip mroute | i 224.1.1.1

(*, 224.1.1.1), 00:04:53/00:02:28, RP 192.168.12.1, flags: SJCL

Pinging from R2:

R2#ping 224.1.1.1 repeat 10

Type escape sequence to abort.

Sending 10, 100-byte ICMP Echos to 224.1.1.1, timeout is 2 seconds:

Reply to request 0 from 192.168.12.1, 80 ms

Reply to request 1 from 192.168.12.1, 44 ms

Reply to request 2 from 192.168.12.1, 16 ms

Reply to request 3 from 192.168.12.1, 16 ms

Reply to request 4 from 192.168.12.1, 24 ms

Reply to request 5 from 192.168.12.1, 52 ms

Reply to request 6 from 192.168.12.1, 40 ms

Reply to request 7 from 192.168.12.1, 28 ms

Reply to request 8 from 192.168.12.1, 12 ms

Reply to request 9 from 192.168.12.1, 28 ms

R2#sh ip mroute 224.1.1.1

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

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

(*, 224.1.1.1), 00:00:38/stopped, RP 192.168.12.1, flags: SPF

Incoming interface: FastEthernet0/0, RPF nbr 192.168.12.1

Outgoing interface list: Null

(192.168.12.2, 224.1.1.1), 00:00:38/00:02:39, flags: PFT

Incoming interface: FastEthernet0/0, RPF nbr 0.0.0.0

Outgoing interface list: Null

HTH,

__

Edison.

View solution in original post

Edison Ortiz · ‎04-23-2009

Subodh,

Not sure what you are missing but it works for me:

R1(f0/0)<--->(f0/0)R2

R1 has the loopback emulating the host with a join for group 224.1.1.1

interface Loopback0

ip address 1.1.1.1 255.255.255.255

ip pim sparse-dense-mode

ip igmp join-group 224.1.1.1

no clns route-cache

end

It's also running PIM Auto-RP:

R1#sh run | i send

ip pim send-rp-announce FastEthernet0/0 scope 16

ip pim send-rp-discovery FastEthernet0/0 scope 16

!

R1#sh ip pim rp mapping

PIM Group-to-RP Mappings

This system is an RP (Auto-RP)

This system is an RP-mapping agent (FastEthernet0/0)

Group(s) 224.0.0.0/4

RP 192.168.12.1 (?), v2v1

Info source: 192.168.12.1 (?), elected via Auto-RP

Uptime: 00:03:52, expires: 00:02:04

R2 can see the Auto-RP announcement:

R2#sh ip pim rp mapping

PIM Group-to-RP Mappings

Group(s) 224.0.0.0/4

RP 192.168.12.1 (?), v2v1

Info source: 192.168.12.1 (?), elected via Auto-RP

Uptime: 00:04:34, expires: 00:02:22

You can also see it on the mroute as RP and mapping agent MCAST groups:

R2#sh ip mroute | i 192.168.12.1

(192.168.12.1, 224.0.1.39), 00:00:23/00:02:37, flags: PT

(192.168.12.1, 224.0.1.40), 00:03:24/00:02:33, flags: PLT

On R1, I can see the IGMP join for 224.1.1.1

R1#sh ip mroute | i 224.1.1.1

(*, 224.1.1.1), 00:04:53/00:02:28, RP 192.168.12.1, flags: SJCL

Pinging from R2:

R2#ping 224.1.1.1 repeat 10

Type escape sequence to abort.

Sending 10, 100-byte ICMP Echos to 224.1.1.1, timeout is 2 seconds:

Reply to request 0 from 192.168.12.1, 80 ms

Reply to request 1 from 192.168.12.1, 44 ms

Reply to request 2 from 192.168.12.1, 16 ms

Reply to request 3 from 192.168.12.1, 16 ms

Reply to request 4 from 192.168.12.1, 24 ms

Reply to request 5 from 192.168.12.1, 52 ms

Reply to request 6 from 192.168.12.1, 40 ms

Reply to request 7 from 192.168.12.1, 28 ms

Reply to request 8 from 192.168.12.1, 12 ms

Reply to request 9 from 192.168.12.1, 28 ms

R2#sh ip mroute 224.1.1.1

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

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

(*, 224.1.1.1), 00:00:38/stopped, RP 192.168.12.1, flags: SPF

Incoming interface: FastEthernet0/0, RPF nbr 192.168.12.1

Outgoing interface list: Null

(192.168.12.2, 224.1.1.1), 00:00:38/00:02:39, flags: PFT

Incoming interface: FastEthernet0/0, RPF nbr 0.0.0.0

Outgoing interface list: Null

HTH,

__

Edison.