The documentation set for this product strives to use bias-free language. For the purposes of this documentation set, bias-free is defined as language that does not imply discrimination based on age, disability, gender, racial identity, ethnic identity, sexual orientation, socioeconomic status, and intersectionality. Exceptions may be present in the documentation due to language that is hardcoded in the user interfaces of the product software, language used based on RFP documentation, or language that is used by a referenced third-party product. Learn more about how Cisco is using Inclusive Language.
The Multicast Routing Monitor (MRM) is a management diagnostic tool that provides network fault detection and isolation in a large multicast routing infrastructure. It is designed to notify a network administrator of multicast routing problems in a test environment.
Your software release may not support all the features documented in this module. For the latest feature information and caveats, see the release notes for your platform and software release. To find information about the features documented in this module, and to see a list of the releases in which each feature is supported, see the Feature Information Table at the end of this document.
Use Cisco Feature Navigator to find information about platform support and Cisco software image support. To access Cisco Feature Navigator, go to www.cisco.com/go/cfn. An account on Cisco.com is not required.
You must make sure the underlying multicast forwarding network being tested has no access lists or boundaries that deny the MRM data and control traffic. Specifically, consider the following factors:
MRM has three components that play different roles: the Manager, the Test Sender, and the Test Receiver. To test a multicast environment using test packets, perhaps before an upcoming multicast event, you need all three components.
You create a test based on various test parameters, name the test, and start the test. The test runs in the background and the command prompt returns.
If the Test Receiver detects an error (such as packet loss or duplicate packets), it sends an error report to the router configured as the Manager. The Manager immediately displays the error report. (The show ip mrm status-reportcommand also displays error reports, if any.) You then troubleshoot your multicast environment as normal, perhaps using the mtrace command from the source to the Test Receiver. If the show ip mrm status-reportcommand displays no error reports, the Test Receiver is receiving test packets without loss or duplicates from the Test Sender.
The Cisco implementation of MRM supports Internet Draft of Multicast Routing Monitor (MRM), Internet Engineering Task Force (IETF), March 1999. The IETF originally conceived MRM to use both test packets and real data. The Cisco implementation does not use real data due to technical issues and the fact that the IETF draft did not progress.
The benefits of the MRM are as follows:
Perform this task to configure a Test Receiver on a router or host.
Perform this task to configure a Test Sender on a different router or host from where you configured the Test Receiver.
If you have more than one multicast group to monitor, you can configure an interface that is a Test Sender for one group and a Test Receiver for another group.
The figure illustrates an environment where the router on the left is the Test Sender for Group A and the Test Receiver for Group B.
Figure 1 | Test Sender and Test Receiver for Different Groups on One Router |
Perform this task to configure a router as a Manager in order for MRM to function.
Note |
A host cannot be a Manager. |
From the router playing the Manager role you can start and stop the MRM test. To start and subsequently stop your MRM test, perform this task.
When the test begins, the Manager sends a unicast control packet to the Test Sender and Test Receiver, and then the Manager starts sending beacons. The Test Sender and Test Receiver send acknowledgments to the Manager and begin sending or receiving test packets. If an error occurs, the Test Receiver sends an error report to the Manager, which immediately displays the report.
Command or Action | Purpose | |
---|---|---|
|
Example: Router> enable |
Enables privileged EXEC mode.
|
|
Example: Router# clear ip mrm status-report 172.16.0.0 |
(Optional) Clears the MRM status report cache. |
|
Example: Router# show ip mrm interface Ethernet 1 |
(Optional) Displays MRM information related to interfaces.
|
|
Example: Router# show ip mrm manager test1 |
(Optional) Displays information about MRM tests.
|
|
Example: Router# mrm test1 start |
Starts the MRM test. |
|
Example: Router# mrm test1 stop |
Stops the MRM test. |
|
Example: Router# show ip mrm status-report |
(Optional) Displays the status reports in the MRM status report cache. |
The figure illustrates a Test Sender, a Test Receiver, and a Manager in an MRM environment. The partial configurations for the three devices follow the figure.
Figure 2 | MRM Example Topology |
interface GigabitEthernet 0/0/0 ip mrm test-sender
interface GigabitEthernet 0/0/0 ip mrm test-receiver
ip mrm manager test1 manager GigabitEthernet 1/0/0 group 239.1.1.1 senders 1 receivers 2 sender-list 1 ! access-list 1 permit 10.1.1.2 access-list 2 permit 10.1.4.2
Related Topic |
Document Title |
---|---|
IP multicast commands: complete command syntax, command mode, command history, defaults, usage guidelines, and examples |
Cisco IOS IP Multicast Command Reference |
Standard |
Title |
---|---|
draft-ietf-mboned-mrm-use-00.txt |
Justification and Use of the Multicast Routing Monitor (MRM) Protocol |
MIB |
MIBs Link |
---|---|
None |
To locate and download MIBs for selected platforms, Cisco IOS XE releases, and feature sets, use Cisco MIB Locator found at the following URL: |
RFC |
Title |
---|---|
No new or modified RFCs are supported by this feature, and support for existing RFCs has not been modified by this feature. |
-- |
Description |
Link |
---|---|
The Cisco Support website provides extensive online resources, including documentation and tools for troubleshooting and resolving technical issues with Cisco products and technologies. To receive security and technical information about your products, you can subscribe to various services, such as the Product Alert Tool (accessed from Field Notices), the Cisco Technical Services Newsletter, and Really Simple Syndication (RSS) Feeds. Access to most tools on the Cisco Support website requires a Cisco.com user ID and password. |
The following table provides release information about the feature or features described in this module. This table lists only the software release that introduced support for a given feature in a given software release train. Unless noted otherwise, subsequent releases of that software release train also support that feature.
Use Cisco Feature Navigator to find information about platform support and Cisco software image support. To access Cisco Feature Navigator, go to www.cisco.com/go/cfn. An account on Cisco.com is not required.
Table 1 | Feature Information for Using the Multicast Routing Monitor |
Feature Name |
Releases |
Feature Information |
---|---|---|
Multicast Routing Monitor (MRM) |
12.2(15)T |
The Multicast Routing Monitor is a network fault detection and isolation mechanism for administering a multicast routing infrastructure. |
Cisco and the Cisco Logo are trademarks of Cisco Systems, Inc. and/or its affiliates in the U.S. and other countries. A listing of Cisco's trademarks can be found at www.cisco.com/go/trademarks. Third party trademarks mentioned are the property of their respective owners. The use of the word partner does not imply a partnership relationship between Cisco and any other company. (1005R)
Any Internet Protocol (IP) addresses and phone numbers used in this document are not intended to be actual addresses and phone numbers. Any examples, command display output, network topology diagrams, and other figures included in the document are shown for illustrative purposes only. Any use of actual IP addresses or phone numbers in illustrative content is unintentional and coincidental.