Using IP Multicast Tools.pdf

(124 KB) Pobierz
Using IP Multicast Tools
This chapter describes IP multicast tools that allow you to trace a multicast path or test a multicast
environment. For a complete description of the commands in this chapter, refer to the “IP Multicast Tools
Commands” chapter in the
Cisco IOS IP Command Reference, Volume 3 of 3: Multicast
publication. To
locate documentation of other commands that appear in this chapter, use the command reference master
index, or search online.
To identify the hardware platform or software image information associated with a feature, use the
Feature Navigator on Cisco.com to search for information about the feature or refer to the software
release notes for a specific release. For more information, see the “Identifying Supported Platforms”
section in the “Using Cisco IOS Software” chapter.
Multicast Routing Monitor Overview
The Multicast Routing Monitor (MRM) feature 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 near real time.
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. (Also, by
issuing a certain
show
EXEC command, you can see the 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
EXEC 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.
Benefits
The benefits of the MRM feature are as follows:
•
Find fault in multicast routing in near real time—If a problem exists in the multicast routing
environment, you will find out about it right away.
Cisco IOS IP Configuration Guide
IPC-521
Using IP Multicast Tools
MRM Configuration Task List
•
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.
Easy diagnostics—The error information is easy for the user to understand.
Scalable—This diagnostic tool works well for many users.
•
•
Restrictions
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.
MRM Configuration Task List
To configure and use the MRM feature, perform the required tasks described in the following sections:
•
•
•
Configuring a Test Sender and Test Receiver
(Required)
Configuring a Manager
(Required)
Conducting an MRM Test
(Required)
Configuring a Test Sender and Test Receiver
To configure a Test Receiver on a router or host, use the following commands beginning in global
configuration mode:
Command
Step 1
Step 2
Step 3
Router(config)#
interface
type number
Router(config-if)#
ip mrm test-receiver
Router(config)#
ip mrm accept-manager
{access-list}
Purpose
Specifies an interface.
Configures the interface to be a Test Receiver.
Optionally, specifies that the Test Receiver can accept status
report requests only from Managers specified by the access list.
To use MRM on test packets instead of actual IP multicast traffic, use the following commands beginning
in global configuration mode to configure a Test Sender
on a different router or host
from where you
configured the Test Receiver:
Command
Step 1
Step 2
Step 3
Router(config)#
interface
type number
Router(config-if)#
ip mrm test-sender
Router(config)#
ip mrm accept-manager
{access-list}
Purpose
Specifies an interface.
Configures the interface to be a Test Sender.
Optionally, specifies that the Test Sender can accept status report
requests only from Managers specified by the access list.
Cisco IOS IP Configuration Guide
IPC-522
Using IP Multicast Tools
MRM Configuration Task List
Monitoring Multiple Groups
If you have more than one multicast group to monitor, you could configure an interface that is a Test
Sender for one group and a Test Receiver for another group.
Figure 86
illustrates an environment where the router on the left is the Test Sender for Group A and the
Test Receiver for Group B.
Figure 86
Test Sender and Test Receiver for Different Groups on One Router
Group B
ip mrm test-sender-receiver
ip mrm test-sender
Test Receiver
and
Test Sender
Test Sender
Group A
Test Receiver
ip mrm test-receiver
23783
To configure the routers in
Figure 86
for monitoring more than one multcast group, configure the Test
Sender in Group B and the Test Receiver in Group A separately, as already discussed, and configure the
following commands beginning in global configuration mode on the router or host that belongs to both
Group A and Group B (in the upper left of
Figure 86):
Command
Step 1
Router(config)#
interface
type number
Purpose
Specifies an interface.
Cisco IOS IP Configuration Guide
IPC-523
Using IP Multicast Tools
MRM Configuration Task List
Command
Step 2
Step 3
Router(config-if)#
ip mrm test-sender-receiver
Purpose
Configures the interface to be a Test Sender for one group
and a Test Receiver for another group.
Optionally, specifies that the Test Sender or Test Receiver
can accept status report requests only from Managers
specified by the access list. By default, the command
applies to both the Sender and Receiver. Because this
device is both, you might need to specify that the
restriction applies to only the Sender or only the Receiver.
Router(config)#
ip mrm accept-manager
{access-list} [test-sender |
test-receiver]
Configuring a Manager
To configure a router as a Manager in order for MRM to function, use the following commands beginning
in global configuration mode. A host cannot be a Manager.
Command
Step 1
Router(config)#
ip mrm manager
test-name
Purpose
Identifies a test by name, and places the router in manager
configuration mode. The test name is used to start, stop,
and monitor a test.
Specifies which interface on the router is the Manager, and
specifies the multicast group address the Test Receiver will
listen to.
Optionally, changes the frequency, duration, or scope of
beacon messages that the Manager sends to the Test Sender
and Test Receiver.
•
•
•
Step 2
Router(config-mrm-manager)#
manager
type
number
group
ip-address
Step 3
beacon
[interval
seconds]
[holdtime
seconds]
[ttl
ttl-value]
Example:
Router(config-mrm-manager)# beacon interval 60
By default, beacon messages are sent at an interval of
60 seconds.
By default, the duration of a test period is 86400
seconds (1 day).
By default, the TTL is 32 hops.
Cisco IOS IP Configuration Guide
IPC-524
Using IP Multicast Tools
MRM Configuration Task List
Command
Step 4
udp-port
[test-packet
port-number]
[status-report
port-number]
Purpose
Optionally, changes the UDP port numbers to which the
Test Sender sends test packets or the Test Receiver sends
status reports.
•
Example:
Router(config-mrm-manager)# udp-port
test-packet 20202
Use the optional
test-packet
keyword and
port-number
argument to change the UDP port to
which the Test Sender sends test packets. The port
number must be even if the packets are Real-Time
Transport Protocol (RTP)-encapsulated. The range is
from 16384 to 65535.
By default, the Test Sender uses UDP port number
16834 to send test packets.
Use the optional
status-report
keyword and
port-number
argument to change the UDP port to
which the Test Receiver sends status reports. The port
number must be odd if the packets are RTP Control
Protocol (RTCP)-encapsulated. The range is from
16834 to 65535.
By default, the Test Receiver uses UDP port number
65535 to send status reports.
Use the optional
packet-delay
keyword and
milliseconds
argument to specify the delay between
test packets (in milliseconds). The range is from 50 to
10000. The default is 200 milliseconds, which results
in 5 packets per second.
Use the optional
rtp
keyword or
udp
keyword to
specify the encapsulation of test packets, either
Real-Time Transport Protocol (RTP) encapsulated or
User Datagram Protocol (UDP) encapsulated. By
default, test packets are RTP-encapsulated.
Use the optional
target-only
keyword to specify that
test packets are sent out on the targeted interface only
(that is, the interface with the IP address that is
specified in the Test Sender request target field). By
default, test packets are sent out on all interfaces that
are enabled with IP multicast.
Use the optional
all-multicasts
keyword to specify
that the test packets are sent out on all interfaces that
are enabled with IP multicast. This is the default
method for sending test packets.
Use the optional
all-test-senders
keyword to specify
that test packets are sent out on all interfaces that have
test-sender mode enabled. By default, test packets are
sent out on all interfaces that are enabled with IP
multicast.
•
•
•
Step 5
senders
access-list [packet-delay
milliseconds]
[rtp |
udp]
[target-only |
all-multicasts
|
all-test-senders]
Establishes Test Senders for MRM tests.
•
Example:
Router(config-mrm-manager)# senders 1
packet-delay 30 udp all-test-senders
•
•
•
•
Cisco IOS IP Configuration Guide
IPC-525

Plik z chomika:

Inne pliki z tego folderu:

Inne foldery tego chomika:

Zgłoś jeśli naruszono regulamin