From: Jason Madsen (madsen.jason@gmail.com)
Date: Sat Nov 29 2008 - 20:05:16 ARST
I wonder why your output showed "/N-Ack" instead of "/Ack" though?
I can't imagine a feature like this one being on a lab though unless it's 1
pt or so...who knows.
Jason
On Sat, Nov 29, 2008 at 2:57 PM, Hobbs <deadheadblues@gmail.com> wrote:
> That's a good tip. I will try that. Good thing it was only a 1 point task
> ;-)
>
> thanks
>
>
> On 11/29/08, Jason Madsen <madsen.jason@gmail.com> wrote:
>>
>> You could always start the test, remove PIM from your test sender's
>> interface, and then check it...not the most exciting thing in the world, but
>> at least you'll see it "in action". Alarms will pop up and remain in the
>> report.
>>
>> Jason
>>
>> On Sat, Nov 29, 2008 at 2:46 PM, Jason Madsen <madsen.jason@gmail.com>wrote:
>>
>>> I think almost everyone who has tested with it feels the same way. Every
>>> other test typically produces something tangible to look at. From what I
>>> can tell your test result was normal though.
>>>
>>> Jason
>>>
>>>
>>> On Sat, Nov 29, 2008 at 2:42 PM, Hobbs <deadheadblues@gmail.com> wrote:
>>>
>>>> I left it running for a long time then I stopped it. Here is what I saw:
>>>>
>>>> R1#show ip mrm manager
>>>> Manager:MyTest/172.31.12.1 is running, expire:22:27:44
>>>> Beacon interval/holdtime/ttl:60/86400/32
>>>> Group:239.1.1.1, UDP port test-packet/status-report:16384/65535
>>>> Test senders:
>>>> 172.31.12.2 /N-Ack
>>>> Test receivers:
>>>> 172.31.200.7 /N-Ack 172.31.80.8 /N-Ack
>>>>
>>>> R1#mrm MyTest stop
>>>> R1#
>>>> Nov 29 21:38:13.950: MRM: Send Beacon for group 239.1.1.1, holdtime 0
>>>> seconds
>>>> Nov 29 21:38:14.950: MRM: Send (stop)Test-Sender Request to 172.31.12.2for group
>>>> 239.1.1.1
>>>> Nov 29 21:38:15.950: MRM: Send (stop)Test-Receiver Request to
>>>> 172.31.200.7 for group 239.1.1.1
>>>> Nov 29 21:38:15.950: MRM: Send (stop)Test-Receiver Request to
>>>> 172.31.80.8 for group 239.1.1.1
>>>> Nov 29 21:38:15.950: MRM: Receive (stop)TS request Ack from 172.31.12.2on FastEthernet0/0
>>>> Nov 29 21:38:15.966: MRM: Receive (stop)TR request Ack from
>>>> 172.31.200.7 on FastEthernet0/0
>>>> Nov 29 21:38:15.970: MRM: Receive (stop)TR request Ack from 172.31.80.8on FastEthernet0/0
>>>>
>>>> R1#show ip mrm status-report
>>>>
>>>> IP MRM status report cache:
>>>> Timestamp
>>>> Manager Test Sender Test Receiver Pkt Loss/Dup
>>>> (%) Ehsr
>>>>
>>>>
>>>> I was hoping to see something like "YOUR MULTICAST CONFIG IS CORRECT"
>>>> :-)
>>>>
>>>>
>>>>
>>>>
>>>> On 11/29/08, Jason Madsen <madsen.jason@gmail.com> wrote:
>>>>>
>>>>> I am no MRM guru, but I do know that with it "no news is good news".
>>>>> It displays output only when there are problems e.g. packet loss or
>>>>> duplicate packets.
>>>>>
>>>>> also, you did start, stop, and then view your report, right?
>>>>>
>>>>> Jason
>>>>>
>>>>> On Sat, Nov 29, 2008 at 2:01 PM, Hobbs <deadheadblues@gmail.com>wrote:
>>>>>
>>>>>> Hello,
>>>>>>
>>>>>> I am following the DocCD as well as a couple archives but I cannot
>>>>>> seem to
>>>>>> get this to work. I have the following topology:
>>>>>>
>>>>>>
>>>>>> R1---ethernet---R2---frame---R5---ethernet---R7---serial---R8---ethernet
>>>>>>
>>>>>> R1 is my manager
>>>>>> R2 is my test sender (LAN interface = 172.31.12.2)
>>>>>> R7 and R8 are my test receivers (LAN interfaces = 172.31.200.7,
>>>>>> 172.31.80.8)
>>>>>> R5 is an RP
>>>>>>
>>>>>> All LAN interfaces have ip igmp join-group 239.1.1.1
>>>>>> Pim sparse-dense everywhere and I can ping the group address from any
>>>>>> router
>>>>>> above - not sure if this is a requirement for MRM.
>>>>>>
>>>>>> R1's config:
>>>>>>
>>>>>> access-list 21 permit 172.31.12.2
>>>>>> access-list 22 permit 172.31.200.7
>>>>>> access-list 22 permit 172.31.80.8
>>>>>> ip mrm manager MyTest
>>>>>> manager FastEthernet0/0 group 239.1.1.1
>>>>>> senders 21
>>>>>> receivers 22 no-join
>>>>>> receivers 22 sender-list 21
>>>>>>
>>>>>> R7 and R8 have the test-receiver command on LAN interfaces.
>>>>>> R2 has the test-sender command on LAN interface.
>>>>>>
>>>>>> I debug mrm events and packets but this is all I get on R1:
>>>>>>
>>>>>> R1#
>>>>>> Nov 29 20:54:50.614: MRM: Send Beacon for group 239.1.1.1, holdtime
>>>>>> 83400
>>>>>> seconds
>>>>>> Nov 29 20:55:50.614: MRM: Send Beacon for group 239.1.1.1, holdtime
>>>>>> 83340
>>>>>> seconds
>>>>>> Nov 29 20:56:50.614: MRM: Send Beacon for group 239.1.1.1, holdtime
>>>>>> 83280
>>>>>> seconds
>>>>>>
>>>>>> Is there something I need to do to generate output?
>>>>>>
>>>>>> thanks
>>>>>>
>>>>>>
>>>>>> Blogs and organic groups at http://www.ccie.net
>>>>>>
>>>>>>
>>>>>> _______________________________________________________________________
>>>>>> Subscription information may be found at:
>>>>>> http://www.groupstudy.com/list/CCIELab.html
Blogs and organic groups at http://www.ccie.net
This archive was generated by hypermail 2.1.4 : Mon Dec 01 2008 - 08:18:32 ARST