From: ccie2be (ccie2be@nyc.rr.com)
Date: Thu Jul 29 2004 - 10:37:44 GMT-3
RE: Generating enough pings to make dialer load threshold kick inSounds
interesting, but how would I do that?
Are you saying that 1 ping would be generated by each telnet session
simultaneously?
Actually, I think I should ask this question a bit differently.
I guess what I'm really trying to get at is this.
Suppose I want to generate 50kbps of ping traffic. Is there a formula I can
use to compute what the ping settings should be to do so?
Knowing how to do this could be very useful for all sorts of testing besides
load-threshold. Testing QoS comes to mind.
PS: I know there are 3rd party products that will do this perfectly but, for
the moment and forseeable future, I don't expect Cisco will allow such
products to be used in the lab.
Thanks Richard
----- Original Message -----
From: Richard Dumoulin
To: ccie2be ; Group Study ; Dan Shechter
Sent: Thursday, July 29, 2004 9:22 AM
Subject: RE: Generating enough pings to make dialer load threshold kick in
You could telnet 4 times to the router and send ping of 1500 bytes in each
telnet session. Then on the 5th telnet session you could monitor the backup,
--Richard
-----Original Message-----
From: ccie2be [mailto:ccie2be@nyc.rr.com]
Sent: jueves, 29 de julio de 2004 15:03
To: Group Study; Dan Shechter
Subject: Re: Generating enough pings to make dialer load threshold kick in
Thanks Dan for the response.
However, I specifically want to test with a high threshold and want to know
what values for ping will generate enough traffic to exceed that threshold
regardless of what the threshold is 75%, 80%, 90%.
Anyway to do that?
Also, is there any point in setting the packet size to something greater
than 1500 bytes?
Thanks
----- Original Message -----
From: "Dan Shechter" <danshtr@yahoo.com>
To: "ccie2be" <ccie2be@nyc.rr.com>
Sent: Thursday, July 29, 2004 8:57 AM
Subject: Re: Generating enough pings to make dialer load threshold kick in
> from both sides of the interface:
>
> ping 1.1.1.1 size 1500 rep 10000
>
> and on the interfaces set the load interval to the min: interface X
> load 30
>
>
> HTH,
> Dan
>
>
> --- ccie2be <ccie2be@nyc.rr.com> wrote:
>
> > Hi guys,
> >
> > Let's say the requirement is to have the 2nd bri circuit come up
> > when the 1st
> > circuit is at 80% utilization.
> >
> > What ping parameters should I adjust to generate enough traffic to
> > get the 1st
> > circuit over 80% utilization?
> >
> > I know I can change the repeat and packet size values, but what
> > values should
> > I use?
> >
> > TIA, Tim
> >
> >
> _______________________________________________________________________
> > Please help support GroupStudy by purchasing your study materials
> > from:
> > http://shop.groupstudy.com
> >
> > Subscription information may be found at:
> > http://www.groupstudy.com/list/CCIELab.html
> >
>
>
> =====
> Best Regards,
> Dan
_______________________________________________________________________
Please help support GroupStudy by purchasing your study materials from:
http://shop.groupstudy.com
Subscription information may be found at:
http://www.groupstudy.com/list/CCIELab.html
**********************************************************************
Any opinions expressed in the email are those of the individual and not
necessarily the company. This email and any files transmitted with it are
confidential and solely for the use of the intended recipient. If you are not
the intended recipient or the person responsible for delivering it to the
intended recipient, be advised that you have received this email in error and
that any dissemination, distribution, copying or use is strictly prohibited.
If you have received this email in error, or if you are concerned with the
content of this email please e-mail to: e-security.support@vanco.info
The contents of an attachment to this e-mail may contain software viruses
which could damage your own computer system. While the sender has taken every
reasonable precaution to minimise this risk, we cannot accept liability for
any damage which you sustain as a result of software viruses. You should carry
out your own virus checks before opening any attachments to this e-mail.
**********************************************************************
This archive was generated by hypermail 2.1.4 : Sun Aug 01 2004 - 10:12:05 GMT-3