Table Of Contents
manager
To specify that an interface is the Manager for Multicast Routing Monitor (MRM), and to specify the multicast group address the Test Receiver will listen to, use the manager command in MRM manager configuration mode. To remove the Manager or group address, use the no form of this command.
manager interface-type interface-number group ip-address
no manager interface-type interface-number group ip-address
Syntax Description
Defaults
There is no MRM Manager.
Command Modes
MRM manager configuration
Command History
Usage Guidelines
This command identifies the interface that acts as the Manager, and therefore is required in order to run MRM.
Examples
The following example shows how to configure Ethernet interface 0 as the Manager and the Test Receiver to listen to multicast group 239.1.1.1:
ip mrm manager test1manager ethernet 0 group 239.1.1.1Related Commands
mdt data
To configure the multicast group address range for data multicast distribution tree (MDT) groups, use the mdt data command in VRF configuration mode. To disable this function, use the no form of this command.
mdt data group-address-range wildcard-bits [threshold threshold-value] [list access-list]
no mdt data group-address-range wildcard-bits [threshold threshold-value] [list access-list]
Syntax Description
Defaults
The command is disabled.
Command Modes
VRF configuration
Command History
12.0(23)S
This command was introduced.
12.2(13)T
This command was integrated into Cisco IOS Release 12.2(13)T.
Usage Guidelines
A data MDT group can include a maximum of 256 multicast groups per Virtual Private Network (VPN). Multicast groups used to create the data MDT group are dynamically chosen from a pool of configured IP addresses.
This command configures a range of alternative multicast destination addresses for the tunnel header. The destination address chosen depends on the traffic profile (that is, the source and destination match the specified access list and the rate of the traffic has exceeded the bandwidth threshhold value).
Examples
In the following example, Protocol Independent Multicast (PIM) Source Specific Multicast (SSM) is configured in the backbone. Therefore, the default and data MDT groups are configured within the SSM range of IP addresses. Inside the VPN, PIM sparse mode (PIM-SM) is configured and only the Auto-RP announcements are accepted.
ip vrf vrf1rd 1:1route-target export 1:1route-target import 1:1mdt default 232.0.0.1mdt data 232.0.1.0 0.0.0.255 threshold 500 list 101!ip pim ssm defaultip pim vrf vrf1 accept-rp auto-rpRelated Commands
mdt default
To configure a default multicast distribution tree (MDT) group for a Virtual Private Network (VPN) routing and forwarding (VRF) instance, use the mdt default command in VRF configuration mode. To disable this function, use the no form of this command.
mdt default group-address
no mdt default group-address
Syntax Description
Defaults
The command is disabled.
Command Modes
VRF configuration
Command History
12.0(23)S
This command was introduced.
12.2(13)T
This command was integrated into Cisco IOS Release 12.2(13)T.
Usage Guidelines
The default MDT group must be the same group configured on all PE routers that belong to the same VPN.
If Source Specific Multicast (SSM) is used as the protocol for the default MDT, the source IP address will be the address used to source the Border Gateway Protocol (BGP) sessions.
A tunnel interface is created as a result of this command. By default, the destination address of the tunnel header is the group-address argument.
Examples
In the following example, Protocol Independent Multicast (PIM) SSM is configured in the backbone. Therefore, the default and data MDT groups are configured within the SSM range of IP addresses. Inside the VPN, PIM sparse mode (PIM-SM) is configured and only the Auto-RP announcements are accepted.
Router(config)# ip vrf redRouter(config-vrf)# rd 1:1Router(config-vrf)# route-target export 1:1Router(config-vrf)# route-target import 1:1Router(config-vrf)# mdt default 232.0.0.1Router(config-vrf)# mdt data 232.0.1.0 0.0.0.255 threshold 500 list 101Router(config-vrf)# exitRouter(config)# ip pim ssm defaultRouter(config)# ip pim vrf red accept-rp auto-rpRelated Commands
mdt log-reuse
To enable the recording of data multicast distribution tree (MDT) reuse, use the mdt log-reuse command in VRF configuration mode. To disable this function, use the no form of this command.
mdt log-reuse
no mdt log-reuse
Syntax Description
This command has no arguments or keywords.
Defaults
The command is disabled.
Command Modes
VRF configuration
Command History
12.0(23)S
This command was introduced.
12.2(13)T
This command was integrated into Cisco IOS Release 12.2(13)T.
Usage Guidelines
The mdt log-reuse command generates a syslog message whenever a data MDT is reused.
Examples
In the following example, the MDT log reuse function is enabled.
mdt log-reuseRelated Commands
mdt data
Configures the multicast group address range for data MDT groups.
mdt default
Configures a default MDT group for a VPN VRF.
mrinfo
To query which neighboring multicast routers are "peering" with the local router, use the mrinfo command in user EXEC or privileged EXEC mode.
mrinfo [host-name | host-address] [source-address | interface]
Syntax Description
Defaults
The command is disabled.
Command Modes
Use EXEC
Privileged EXECCommand History
Usage Guidelines
The mrinfo command is the original tool of the multicast backbone (MBONE) to determine which neighboring multicast routers are peering with a multicast router. Cisco routers have supported responding to mrinfo requests since Cisco IOS Release 10.2.
Now you can query a multicast router using this command. The output format is identical to the multicast routed version of Distance Vector Multicast Routing Protocol (DVMRP). (The mrouted software is the UNIX software that implements DVMRP.)
Examples
The following is sample output from the mrinfo command:
Router# mrinfo192.31.7.37 (barrnet-gw.cisco.com) [version cisco 11.1] [flags: PMSA]:192.31.7.37 -> 192.31.7.34 (sj-wall-2.cisco.com) [1/0/pim]192.31.7.37 -> 192.31.7.47 (dirtylab-gw-2.cisco.com) [1/0/pim]192.31.7.37 -> 192.31.7.44 (dirtylab-gw-1.cisco.com) [1/0/pim]131.119.26.10 -> 131.119.26.9 (su-pr2.bbnplanet.net) [1/32/pim]The flags indicate the following:
•
P: prune-capable
•
•
•
mrm
To start or stop a Multicast Routing Monitor (MRM) test, use the mrm command in privileged EXEC mode.
mrm test-name {start | stop}
Syntax Description
test-name
Name of the MRM test to start or stop.
start
Starts the MRM test specified for the test-name argument.
stop
Stops the MRM test specified for the test-name argument.
Command Modes
Privileged EXEC
Command History
Usage Guidelines
You must use this command to run an MRM test. When the test runs, the Test Sender sends User Datagram Protocol (UDP) or UDP/Real-Time Transport Protocol (RTP) packets (depending on the senders command) to the Test Receiver.
Examples
The following example shows how to start an MRM test. In this example, the MRM test named test1 is started.
Router# mrm test1 startRelated Commands
mstat
To display IP multicast packet rate and loss information, use the mstat command in user EXEC or privileged EXEC mode.
mstat {source-name | source-address} [destination-name | destination-address] [group-name | group-address]
Syntax Description
Defaults
The command is disabled.
Command Modes
User EXEC
Privileged EXECCommand History
Usage Guidelines
If no arguments are entered, the router will interactively prompt you for them.
This command is a form of UNIX mtrace that reports packet rate and loss information.
Examples
The following is sample output from the mstat command in user EXEC mode:
Router> mstat lwei-home-ss2 172.16.0.1 224.0.255.255Type escape sequence to abort.Mtrace from 172.16.0.0 to 172.16.0.10 via group 224.0.255.255>From source (lwei-home-ss2.cisco.com) to destination (lwei-ss20.cisco.com)Waiting to accumulate statistics......Results after 10 seconds:Source Response Dest Packet Statistics For Only For Traffic172.16.0.0 172.16.0.10 All Multicast Traffic From 172.16.0.0| __/ rtt 48 ms Lost/Sent = Pct Rate To 224.0.255.255v / hop 48 ms --------------------- --------------------172.16.0.1 lwei-cisco-isdn.cisco.com| ^ ttl 1v | hop 31 ms 0/12 = 0% 1 pps 0/1 = --% 0 pps172.16.0.2172.16.0.3 eng-frmt12-pri.cisco.com| ^ ttl 2v | hop -17 ms -735/12 = --% 1 pps 0/1 = --% 0 pps172.16.0.4172.16.0.5 eng-cc-4.cisco.com| ^ ttl 3v | hop -21 ms -678/23 = --% 2 pps 0/1 = --% 0 pps172.16.0.6172.16.0.7 eng-ios-2.cisco.com| ^ ttl 4v | hop 5 ms 605/639 = 95% 63 pps 1/1 = --% 0 pps172.16.0.8172.16.0.9 eng-ios-f-5.cisco.com| \__ ttl 5v \ hop 0 ms 4 0 pps 0 0 pps172.16.0.0 172.16.0.10Receiver Query SourceTable 2 describes the significant fields shown in the display.
Related Commands
mtrace
Traces the path from a source to a destination branch for a multicast distribution tree.
mtrace
To trace the path from a source to a destination branch for a multicast distribution tree, use the mtrace user command in user EXEC or privileged EXEC mode.
mtrace {source-name | source-address} [destination-name | destination-address] [group-name | group-address]
Syntax Description
Defaults
The command is disabled.
Command Modes
User EXEC
Privileged EXECCommand History
Usage Guidelines
The trace request generated by the mtrace command is multicast to the multicast group to find the last hop router to the specified destination. The trace then follows the multicast path from destination to source by passing the mtrace request packet via unicast to each hop. Responses are unicast to the querying router by the first hop router to the source. This command allows you to isolate multicast routing failures.
If no arguments are entered, the router will interactively prompt you for them.
This command is identical in function to the UNIX version of mtrace.
Examples
The following is sample output from the mtrace command in user EXEC mode:
Router> mtrace 172.16.0.0 172.16.0.10 239.254.254.254Type escape sequence to abort.Mtrace from 172.16.0.0 to 172.16.0.10 via group 239.254.254.254From source (?) to destination (?)Querying full reverse path...0 172.16.0.10-1 172.16.0.8 PIM thresh^ 0 0 ms-2 172.16.0.6 PIM thresh^ 0 2 ms-3 172.16.0.5 PIM thresh^ 0 894 ms-4 172.16.0.3 PIM thresh^ 0 893 ms-5 172.16.0.2 PIM thresh^ 0 894 ms-6 172.16.0.1 PIM thresh^ 0 893 msTable 3 describes the significant fields shown in the display.
Related Commands
receivers
To establish Test Receivers for Multicast Routing Monitor (MRM) tests or modify the parameters of Test Receivers, use the receivers command in MRM manager configuration mode. To restore the default values, use the no form of this command.
Form of the Command to Establish Test Receivers
receivers access-list sender-list access-list [packet-delay]
no receivers access-list
Form of the Command to Modify the Parameters of Test Receivers
receivers access-list [window seconds] [report-delay seconds] [loss percentage] [no-join] [monitor | poll]
no receivers access-list
Syntax Description
Command Default
No Test Receivers are configured for MRM tests.
Command Modes
MRM manager configuration
Command History
Usage Guidelines
This command is required for MRM to work; the receivers access-list and sender-list access-list keyword-argument pairs must be specified.
Note
Optionally, you can use the receivers command to modify the parameters for Test Receivers.
Loss percentage is calculated based on the packet-delay value of the senders command, which defaults to 200 milliseconds, or 5 packets per second. If the window keyword defaults to 5 seconds, then the Test Receiver expects 5 packets per second for 5 seconds = 25 packets. If the Test Receiver receives only 15 packets, then 25 - 15 = 10 lost packets. Lost packets divided by packets expected equals loss percentage; 10/25 equals a loss percentage of 40 percent.
Examples
The following example shows how to establish a Test Receiver for an MRM test:
ip mrm manager test1manager Ethernet0/0 group 239.1.1.1senders 1receivers 2 sender-list 1!access-list 1 permit 10.1.1.2access-list 2 permit 10.1.4.2!Related Commands
