From: Victor Cappuccio (cvictor@protokolgroup.com)
Date: Thu Jul 06 2006 - 10:44:56 ART
Hi, I had a similar problem last night, and I came to this solution, the
problem with Cisco's ping is that it doesn't let you specify how much time
between pings. The timeout value is for unsuccessful pings. But there is
always a good thing in Cisco Router, that us SLA, you can do something like
this for testing purposes
rtr 2
type udpEcho dest-ipaddr 150.1.3.3 dest-port 6060 control disable
request-data-size 1000
timeout 0
frequency 1
rtr schedule 2 life forever start-time now
That means to generate UDP Traffic to Destination 150.1.3.3:6060
With a Byte length of 1000 Bytes
You can create several RTR like this, to the same destination.
.- Thanks for the explanation of Burst Petr, that clarify many things.-
Another thing that comes into my mind, did you set the service-police
outbound the Virtual-temp 1 of R1?
Saludos,
Victor.-
-----Mensaje original-----
De: nobody@groupstudy.com [mailto:nobody@groupstudy.com] En nombre de Adam
Frederick
Enviado el: Jueves, 06 de Julio de 2006 09:19 a.m.
Para: ccielab@groupstudy.com
Asunto: Multilink Interface
Hi Group
Working on a scenario where I have 3 Pods.
BB1-----R1=====R2----------R3------LAN
Connection between R1 & R2 is MPPP. R2 & R3 is Ethernet.
I am trying to police inbound traffic w/ no success @ R2 coming from R1.
I am currently using MQC for outbound traffic @ R2 successfully. I have
3 traffic classes, 2 of which are designated "bandwidth 1000" and a 3rd
class that is using policing.
Is there a good way to get around this? I tried using service-policy
input on the Multilink interface and wasn't allowed.
Any input is greatly appreciated
Thanks,
Adam
This archive was generated by hypermail 2.1.4 : Tue Aug 01 2006 - 07:13:46 ART