(Answer) (Category) Cisco CCIE Certification and CCNP Certification FAQs :
How can I simulate multicast traffic?
From: Cassidy D. Smith
Pinging a Multicast group address from a router works well for troubleshooting and verifying configs. You may have to manually join the multicast group in a few places, depending on your setup.
sean@ertw.com
From: Brian Dennis
Check into MRM (Multicast Routing Monitor) on a Cisco router.
                                                                                
Here is an example config:
                                                                                
R5
 ip mrm manager CCIE
 manager Ethernet 0 group 224.2.3.4
 senders 1
 receivers 2 sender-list 1
 !
 access-list 1 permit 161.12.45.4
 access-list 2 permit 202.21.12.130
R4
 interface Ethernet0/0
  ip address 161.12.45.4 255.255.255.0
  ip mrm test-sender
R3
 interface Ethernet0
  ip address 202.21.12.130 255.255.255.252
  ip mrm test-receiver
                                                                                
                                                                                
R5 (from enable mode) mrm CCIE start
sean@ertw.com
Author: kasturi cisco
Date: 2004-02-28 17:16 -600

If u have Jeff Doyle Vol2 good explanation is provided on how to use them in Mcast troubleshooting. I will try to explain in short, but better to access the Doc CD or book for more info.


As the names suggest mtrace is Multicast trace and helps to trace the Mcast path. I think it uses UDP packet. Mtrace is used to trace the RPF path between the source and destination. It can be used on any router and not necessarily on any router in the RPF path.

 R7#mtrace 136.10.1.1
 Type escape sequence to abort.
 Mtrace from 136.10.1.1 to 136.10.56.7 via RPF
 From source (?) to destination (?)
 Querying full reverse path...
0 136.10.56.7
-1 136.10.56.7 PIM [136.10.1.0/24] -2 136.10.56.6 PIM [136.10.1.0/24] -3 136.10.100.2 PIM [136.10.1.0/24] -4 136.10.12.1 PIM [136.10.1.0/24] -5 136.10.1.1
Mstat is similar to Mtrace and provides statistics of the path in addition to path info.
 R7#mstat 136.10.7.7 136.10.1.1
 Type escape sequence to abort.
 Mtrace from 136.10.7.7 to 136.10.1.1 via RPF
 From source (?) to destination (?)
 Waiting to accumulate statistics......
 Results after 10 seconds:
Mrinfo is used to provide Mcast information about a router. It can be issued on any router to get information about any other router.
 R7#R7#mrinfo
 136.10.56.7 [version 12.2] [flags: PMA]:
136.10.56.7 -> 136.10.56.6 [1/0/pim] 136.10.56.7 -> 136.10.56.5 [1/0/pim] 136.10.7.7 -> 0.0.0.0 [1/0/pim/querier/leaf]

 R7#mrinfo
 136.10.56.7 [version 12.2] [flags: PMA]:
 <<< Source address for Query ,IOS version and
 Flags = P is Prune capable, M= Mtrace capable, A=Auto RP capable]
The next 3 lines how what interfaces are multicast enabled and any peers the router may have on these interface.
 136.10.56.7 -> 136.10.56.6 [1/0/pim]
 << The interface with 56.7 address and its neighour, 56.7 and 56.6
 [metric/ttl threshold/pim enabled]
136.10.56.7 -> 136.10.56.5 [1/0/pim] <<< The interface with 56.7 address and its neighour, 56.7 and 56.5 [1 metric/ttl threshold/pim enabled]
136.10.7.7 -> 0.0.0.0 [1/0/pim/querier/leaf] <<< The interface with 7.7 address and its neighbor, 7.7 has no neighbor [metric/ttl threshold/pim enabled/ this interface is the IGMP querier on this subnet/there is no transit router attached and it is the leaf subnet]

[Append to This Answer]
Previous: (Answer) How can I simulate NetBIOS or SNA traffic?
Next: (Answer) How can you assign IPX network FFFFFFFE to an interface?
This document is: http://ertw.com/cgi-bin/fom?file=14
[Search] [Appearance]
This is a Faq-O-Matic 2.719.
This FAQ administered by ...