|
Table Of Contents
Using the Multicast Routing Monitor
Restrictions for Using the Multicast Routing Monitor
Information About the Multicast Routing Monitor
Multicast Routing Monitor Operation
Benefits of Multicast Routing Monitor
How to Use the Multicast Routing Monitor
Conducting an MRM Test and Viewing Results
Configuration Examples for MRM
Feature Information for Using the Multicast Routing Monitor
Using the Multicast Routing Monitor
First Published: May 2, 2005Last Updated: May 4, 2009The 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.
Finding Feature Information
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 for Using the Multicast Routing Monitor" section.
Use Cisco Feature Navigator to find information about platform support and Cisco IOS and Catalyst OS software image support. To access Cisco Feature Navigator, go to http://www.cisco.com/go/cfn. An account on Cisco.com is not required.
Contents
•Restrictions for Using the Multicast Routing Monitor
•Information About the Multicast Routing Monitor
•How to Use the Multicast Routing Monitor
•Configuration Examples for MRM
•Feature Information for Using the Multicast Routing Monitor
Restrictions for Using the Multicast Routing Monitor
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 test data are User Datagram Protocol (UDP) and Real-Time Transport Protocol (RTP) packets addressed to the configured multicast group address.
•MRM control traffic between the Test Sender, Test Receiver, and Manager is addressed to the 224.0.1.111 multicast group, which all three components join. The 224.0.1.111 group is an IANA-registered group.
•Take into account the unicast IP addresses of sources and receivers when considering what could prevent control traffic flowing.
Information About the Multicast Routing Monitor
Before using MRM, you should understand the following concepts:
•Multicast Routing Monitor Operation
•Benefits of Multicast Routing Monitor
Multicast Routing Monitor Operation
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-report command 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-report command 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.
Benefits of Multicast Routing Monitor
The benefits of the MRM are as follows:
•MRM allows network personnel to generate test flows without having to use host devices.
•MRM can verify a multicast environment prior to an event. You need not wait for real multicast traffic to fail in order to find out that a problem exists. You can test the multicast routing environment before a planned event.
•MRM provides easy diagnostics. The error information is easy for the user to understand.
•MRM is scalable. This diagnostic tool works well for many users.
How to Use the Multicast Routing Monitor
This section contains the following procedures:
•Configuring a Test Receiver (required)
•Configuring a Test Sender (required)
•Monitoring Multiple Groups (optional)
•Configuring a Manager (required)
•Conducting an MRM Test and Viewing Results (required)
Configuring a Test Receiver
Perform this task to configure a Test Receiver on a router or host.
SUMMARY STEPS
1. enable
2. configure terminal
3. interface type number
4. ip mrm test-receiver
5. ip mrm accept-manager access-list
DETAILED STEPS
Configuring a Test Sender
Perform this task to configure a Test Sender on a different router or host from where you configured the Test Receiver.
SUMMARY STEPS
1. enable
2. configure terminal
3. interface type number
4. ip mrm test-sender
5. ip mrm accept-manager [access-list]
DETAILED STEPS
Monitoring Multiple Groups
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.
Figure 1 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
SUMMARY STEPS
1. enable
2. configure terminal
3. interface type number
4. ip mrm test-sender-receiver
5. ip mrm accept-manager access-list [test-sender | test-receiver]
DETAILED STEPS
Configuring a Manager
Perform this task to configure a router as a Manager in order for MRM to function.
Note A host cannot be a Manager.
SUMMARY STEPS
1. enable
2. configure terminal
3. ip mrm manager test-name
4. manager type number group ip-address
5. beacon [interval seconds] [holdtime seconds] [ttl ttl-value]
6. udp-port [test-packet port-number] [status-report port-number]
7. senders access-list [packet-delay milliseconds] [rtp | udp] [target-only | all-multicasts | all-test-senders]
8. receivers access-list sender-list access-list [packet-delay]
9. receivers access-list [window seconds] [report-delay seconds] [loss percentage] [no-join] [monitor | poll]
DETAILED STEPS
Conducting an MRM Test and Viewing Results
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.
SUMMARY STEPS
1. enable
2. clear ip mrm status-report [ip-address]
3. show ip mrm interface [type number]
4. show ip mrm manager [test-name]
5. mrm test-name start
6. mrm test-name stop
7. show ip mrm status-report [ip-address]
DETAILED STEPS
Configuration Examples for MRM
This section provides the following configuration example:
Configuring MRM: Example
Figure 2 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
Test Sender Configuration
interface Ethernet 0ip mrm test-senderTest Receiver Configuration
interface Ethernet 0ip mrm test-receiverManager Configuration
ip mrm manager test1manager Ethernet 1 group 239.1.1.1senders 1 receivers 2 sender-list 1!access-list 1 permit 10.1.1.2access-list 2 permit 10.1.4.2Additional References
The following sections provide references related to the using the MRM.
Related Documents
Related Topic Document TitleIP multicast commands: complete command syntax, command mode, command history, defaults, usage guidelines, and examples
Standards
Standard Titledraft-ietf-mboned-mrm-use-00.txt
Justification and Use of the Multicast Routing Monitor (MRM) Protocol
MIBs
RFCs
RFC TitleNo new or modified RFCs are supported by this feature, and support for existing RFCs has not been modified by this feature.
—
Technical Assistance
Feature Information for Using the Multicast Routing Monitor
Table 1 lists the features in this module and provides links to specific configuration information. Only features that were introduced or modified in Cisco IOS Release 12.2(1) or a later release appear in the table.
For information on a feature in this technology that is not documented here, see the "IP Multicast Features Roadmap."
Not all commands may be available in your Cisco IOS software release. For release information about a specific command, see the command reference documentation.
Use Cisco Feature Navigator to find information about platform support and software image support. Cisco Feature Navigator enables you to determine which Cisco IOS and Catalyst OS software images support a specific software release, feature set, or platform. To access Cisco Feature Navigator, go to http://www.cisco.com/go/cfn. An account on Cisco.com is not required.
Note Table 1 lists only the Cisco IOS software release that introduced support for a given feature in a given Cisco IOS software release train. Unless noted otherwise, subsequent releases of that Cisco IOS software release train also support that feature.
CCDE, CCSI, CCENT, Cisco Eos, Cisco HealthPresence, the Cisco logo, Cisco Lumin, Cisco Nexus, Cisco Nurse Connect, Cisco Stackpower, Cisco StadiumVision, Cisco TelePresence, Cisco WebEx, DCE, and Welcome to the Human Network are trademarks; Changing the Way We Work, Live, Play, and Learn and Cisco Store are service marks; and Access Registrar, Aironet, AsyncOS, Bringing the Meeting To You, Catalyst, CCDA, CCDP, CCIE, CCIP, CCNA, CCNP, CCSP, CCVP, Cisco, the Cisco Certified Internetwork Expert logo, Cisco IOS, Cisco Press, Cisco Systems, Cisco Systems Capital, the Cisco Systems logo, Cisco Unity, Collaboration Without Limitation, EtherFast, EtherSwitch, Event Center, Fast Step, Follow Me Browsing, FormShare, GigaDrive, HomeLink, Internet Quotient, IOS, iPhone, iQuick Study, IronPort, the IronPort logo, LightStream, Linksys, MediaTone, MeetingPlace, MeetingPlace Chime Sound, MGX, Networkers, Networking Academy, Network Registrar, PCNow, PIX, PowerPanels, ProConnect, ScriptShare, SenderBase, SMARTnet, Spectrum Expert, StackWise, The Fastest Way to Increase Your Internet Quotient, TransPath, WebEx, and the WebEx logo are registered trademarks of Cisco Systems, Inc. and/or its affiliates in the United States and certain other countries.
All other trademarks mentioned in this document or website 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. (0903R)
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.
© 2005-2009 Cisco Systems, Inc. All rights reserved.