From: Jason Cash (cash2001@swbell.net)
Date: Sat Jun 28 2003 - 00:09:25 GMT-3
Thanks that what I was looking for exactly...although now I just can't get
it to work...here is the output:
r2#u
*Mar 4 01:12:42: IP MRM status report -- Test:r1-r5 Receiver:140.10.1.1
*Mar 4 01:12:42: Sender:140.10.56.5 Pkt Loss:25(100%) Ehsr:0
*Mar 4 01:13:43: IP MRM status report -- Test:r1-r5 Receiver:140.10.1.1
*Mar 4 01:13:43: Sender:140.10.56.5 Pkt Loss:25(100%) Ehsr:0
*Mar 4 01:14:43: IP MRM status report -- Test:r1-r5 Receiver:140.10.1.1
*Mar 4 01:14:43: Sender:140.10.56.5 Pkt Loss:25(100%) Ehsr:0
*Mar 4 01:15:43: IP MRM status report -- Test:r1-r5 Receiver:140.10.1.1
*Mar 4 01:15:43: Sender:140.10.56.5 Pkt Loss:25(100%) Ehsr:0
*Mar 4 01:16:43: IP MRM status report -- Test:r1-r5 Receiver:140.10.1.1
*Mar 4 01:16:43: Sender:140.10.56.5 Pkt Loss:25(100%) Ehsr:0
*Mar 4 01:17:43: IP MRM status report -- Test:r1-r5 Receiver:140.10.1.1
*Mar 4 01:17:43: Sender:140.10.56.5 Pkt Loss:25(100%) Ehsr:0
-----Original Message-----
From: Mark Foster [mailto:mfoster@foster-consulting.com]
Sent: Friday, June 27, 2003 9:15 PM
To: 'Jason Cash'
Jason,
See if the config sniplets and explanation below provide you some
assistance. In addition to these config statements, make sure you have pim
configured on any interfaces that will transport multicast traffic.
R1:
!
interface Loopback0
ip address 10.28.255.13 255.255.255.252
ip pim sparse-dense-mode
ip mrm test-sender
!
R2:
!
interface Loopback0
ip address 10.208.255.13 255.255.255.252
ip pim sparse-dense-mode
ip mrm test-receiver
!
R3:
!
ip mrm manager r1-r2
manager Loopback0 group 239.255.255.255
senders 1
receivers 2 sender-list 1
!
access-list 1 permit 10.28.255.13
access-list 2 permit 10.208.255.13
!
As part of the configuration changes for IP multicast, the MRM function was
configured as an initial pilot implementation on R1, R2, and R3. Each of
these devices currently performs a different functional MRM role, as shown
below:
R1 - Interface lo0 is MRM test sender.
R2 - Interface lo0 is MRM test receiver.
R3 - MRM manager, with a test group defined as 'r1-r2'
To check the current MRM test status, issue the following command on R3:
R3#sh ip mrm manager
Manager:r1-r2/10.208.255.5 is not running
Beacon interval/holdtime/ttl:60/86400/32
Group:239.1.1.1, UDP port test-packet/status-report:16384/65535
Test senders:
10.28.255.13
Test receivers:
10.208.255.13
To start the MRM test traffic between R1 and R2, issue the following command
on R3:
mrm r1-r2 start
The following log message confirms that the MRM test is started:
IP MRM test 'r1-r2' starts ......
Now the mrm manager status shows the test running:
R3#sh ip mrm manager
Manager:r1-r2/10.208.255.5 is running, expire:1d00h
Beacon interval/holdtime/ttl:60/86400/32
Group:239.1.1.1, UDP port test-packet/status-report:16384/65535
Test senders:
10.28.255.13 /Ack
Test receivers:
10.208.255.13 /Ack
The MRM test results messages are written to the log:
IP MRM status report -- Test:r1-r2 Receiver:10.208.255.13
Sender:10.28.255.13 Pkt Loss:1(4%) Ehsr:9
To stop the MRM test traffic, issue the following command:
mrm r1-r2 stop
The following log message confirms that the MRM test is stopped.
IP MRM test 'r1-r2' stops
To display the status of the test sender or receiver interfaces on one of
those devices, the following command and output is provided:
R1#sh ip mrm int
Interface Address Mode Status
Loopback0 10.28.255.13 Test-Sender Up
R2#sh ip mrm int
Interface Address Mode Status
Loopback0 10.208.255.13 Test-Receiver Up
HTH!
Mark
This archive was generated by hypermail 2.1.4 : Fri Jul 04 2003 - 11:11:13 GMT-3