ping 224.2.2.2.reply .

Unanswered Question

hello!

i can;t ping my Multicast group from My Router:

RX

Ip multicast-routing

interface FastEthernet0/0

ip address 10.10.100.2 255.255.255.0

ip pim sparse-mode

ip igmp join-group 224.2.2.2

speed 100

full-duplex

end

ping Result

R2#ping 224.2.2.2


Type escape sequence to abort.

Sending 1, 100-byte ICMP Echos to 224.2.2.2, timeout is 2 seconds:

.

how i troubleshoot here?

10xs

  • 1
  • 2
  • 3
  • 4
  • 5
Overall Rating: 5 (2 ratings)
Loading.

R2#sh 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,

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

Outgoing interface flags: H - Hardware switched, A - Assert winner

Timers: Uptime/Expires

Interface state: Interface, Next-Hop or VCD, State/Mode

yes interface up/up

(*, 224.2.2.2), 00:28:25/00:02:45, RP 4.4.4.4, flags: SJCL

Incoming interface: Null, RPF nbr 0.0.0.0

Outgoing interface list:

FastEthernet0/0, Forward/Sparse, 00:28:25/00:02:45


(*, 224.0.1.40), 00:31:06/00:02:47, RP 4.4.4.4, flags: SJCL

Incoming interface: Null, RPF nbr 0.0.0.0

Outgoing interface list:

FastEthernet0/0, Forward/Sparse, 00:31:06/00:02:47


Edison Ortiz Thu, 11/22/2007 - 13:11

You are running in sparse mode so you need a RP for multicast.


Your mroute indicates that you do have a RP (4.4.4.4) - do you have reachability to the interface used as the RP ?


BTW,


I tried your configuration in my router.


I'm able to ping if I change the mode from sparse mode to sparse-dense mode.


sparse-dense mode allows you to run multicast without a RP as it floods the information to all interfaces.


Rack1R2#sh run int f0/0

Building configuration...


Current configuration : 151 bytes

!

interface FastEthernet0/0

ip address 10.10.100.2 255.255.255.0

ip pim sparse-dense-mode

ip igmp join-group 224.2.2.2

speed 100

full-duplex

end


Rack1R2#ping 224.2.2.2


Type escape sequence to abort.

Sending 1, 100-byte ICMP Echos to 224.2.2.2, timeout is 2 seconds:


Reply to request 0 from 10.10.100.2, 8 ms


Rack1R2#sh 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,

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

Outgoing interface flags: H - Hardware switched, A - Assert winner

Timers: Uptime/Expires

Interface state: Interface, Next-Hop or VCD, State/Mode


(*, 224.2.2.2), 00:03:38/stopped, RP 0.0.0.0, flags: DCL

Incoming interface: Null, RPF nbr 0.0.0.0

Outgoing interface list:

FastEthernet0/0, Forward/Sparse-Dense, 00:03:38/00:00:00


(10.10.100.2, 224.2.2.2), 00:00:15/00:02:44, flags: PLT

Incoming interface: FastEthernet0/0, RPF nbr 0.0.0.0

Outgoing interface list: Null


(*, 224.0.1.40), 00:05:12/00:02:52, RP 0.0.0.0, flags: DCL

Incoming interface: Null, RPF nbr 0.0.0.0

Outgoing interface list:

FastEthernet0/0, Forward/Sparse-Dense, 00:05:12/00:00:00



Actions

This Discussion