QoS Traffic Generation

So I am taking a gander at the other Cisco certifications as I am not too far from getting my CCNP.. and I am finishing up the ONT right now. This exam is mostly QoS theory with very little implementation. I do much better if i can lab it out.. so i started to lab a few things out.. and I realized that I can type commands in all day, but without any traffic generation I can't "see" my traffic get shaped or policed..

I know there was a free application that generates multicast traffic for you.. but what I would like is a free (or low cost) application that generates a variety of different types of traffic (gnutella, ftp, http, xwindows..etc).. I was reading about something called NetIQ chariot.. but it seems the application no longer exists or was integrated into something else NetIQ owns.

Anyway.. other than setting up virtual machines and integrating my lab into my home network to generate various traffic.. is there any other way that is suggested?

I'm sure this has been asked before, so feel free to re-direct my question

Find more posts tagged with

Comments

mikej412

There are some links in this thread.

And since I did lots just using the extended ping, the ping program Ed mentioned in this thread could be even more fun.

QoS is something that might be best learned on real hardware. I'm not sure how well Dynamips handles the emulation of the hardware queues, but it should let you practice typing in the configurations.

Plazma

I was thinking extended ping for some things.. but wasn't 100% sure how i could fa-nagle it to work to simulate other types of traffic.. it probably can't but maybe i'm overlooking something.

Also i could use netcat or something i suppose .. somehow

Paul Boz

I set up QoS in my home network and just stress-tested my QoS rules. It's not hard to max out a 10mb cable connection with junk. For example, I'd make a class for my xbox 360 traffic, make a class for FTP transfers, and another class for BitTorrent. I would put BT as the scav class, run several torrents wide open, then watch the traffic die as FTP traffic takes priority. The same can be done with just about any type of packet which you can tag or identify.