UDP small servers and qos

Jannar,

If you want to use routers as sources/sinks of test data, then you should put them outboard of your systems-under-test.

i.e. do this:

[source]-{network-under-test}-[sink]

not this

{[some router [source]]-{cloud}-[[sink] some router]} ||

For using a router as a source/sink of data packets, one option is to use ttcp which is built into some feature sets.

(This example violates my advice above, as it has the router under test act as a source of test data ... but that's OK because I wasn't testing the router's internal queueing technique.)

Cheers,

Aaron

Yes, I have a separate hardware sending those UDP echo packets (source). My problem is how to manage the routing at the far end (Cisco IOS small-server as a destination). Now the destination IOS seems to reply directly from the WAN interface and I cannot do any policing/queuging for the reply traffic.

So my setup is like this:

[UDP echo src] ---- [WAN] ---- [IOS router with UDP echo server] ---- [VoIP VLAN and Data-VLAN]

I need to use IP DSCP 56 for those echo replies. My source is sending DSCP 56 just fine, and it's working across the WAN just fine.

Any hints?

I'm sorry, you've lost me.

My point was that you should not expect to use one and the same IOS router simultaneously act as the source/sink of your test data and also to run data policing/queueing of that data.

Aaron

Do you mean, that I should not try to use it or it's impossible? :-)

~ >My point was that you should not expect to use one and the ~ >same IOS router ~ ~ Do you mean, that I should not try to use it or it's impossible? :-)

Well, by all means try it, but if it doesn't produce the expected results, then you should question the expected results.

Perhaps just as important, even if it does produce the expected results, you should _still_ question the results.

Good luck and have fun!