Can ICMP ping can be used with different classes of traffic

[pgyogeshkumar]

Hi

Can ICMP ping can be used with different classes of traffic ?

I generated the extended ping for various classes like EF, AF41 by setting the corresponding TOS value?

Although I can see that DSCP value marked differently in Netflow reports for this ICMP ping, I cant see that it is mapped to its respective class.

Please confirm if ICMP traffic will be mapped to different class correctly based on this DSCP markings?

Else please confirm is there anyway to generate traffic for different class of traffic (voice, video, data etc) from the routers,

Thanks

Yogesh

[Mark Malone]

Hi You can use a ping to test qos if that's what you mean , you would run an extended ping with a tos value of 184 to test voice queue if you want to replicate traffic as that's equal to DSCP EF , you can then see as your pings go through that your voice queue should be filling up

ef = dscp 46 = 101110 = tos 0xb8 (184) = ip prec 5

[pgyogeshkumar]

I did exactly the same, however in netflow reports I can get see that DSCP is set to 184 or 136 as per my command. However I dont think its exactly mapped to that particular class of service?

Will it happen like this ?

Or is there any other way to generate different class of traffic from routers

[Mark Malone]

what about the device router/switch itself can you see it going to the right queues at layer 2 or 3 depending what qos you have set up when you ping, does it mark it correct locally without viewing netflow reports ?

[pgyogeshkumar]

At device level packets are increasing based on the QOS queue defined, Will analyse further and confirm

[Mark Malone]

Thats good , sounds like report just reading it wrong then main thing is traffic is marked correct at the devices , what are you using for netflow collection

[Joseph W. Doherty]

Disclaimer

The Author of this posting offers the information contained within this posting without consideration and with the reader's understanding that there's no implied or expressed suitability or fitness for any purpose. Information provided is for informational purposes only and should not be construed as rendering professional advice of any kind. Usage of this posting's information is solely at reader's own risk.

Liability Disclaimer

In no event shall Author be liable for any damages wha2tsoever (including, without limitation, damages for loss of use, data or profit) arising out of the use or inability to use the posting's information even if Author has been advised of the possibility of such damage.

Posting

Where are you generating the tagged ping packets, on the same device with Netflow, or upstream?  If the former, Netflow might be treating locally sourced packets differently.