Re: [Flent-users] [tohojo/flent] Customized test displaying error (#203)

["Toke Høiland-Jørgensen" <notifications@github.com>]

[-- Attachment #1.1: Type: text/plain, Size: 2627 bytes --]

olg33 <notifications@github.com> writes:

> Hi Toke,
> After testing with two co-located servers and tweaking the switch configuration that connects them, all is working well. Thanks.
>
> Now I'd like to test in a production network. Because we work in a multi-vendor environment (Riverbed, Procera, Idirect, etc) we had to create a customized DSCP naming convention which is based on the TOS Hexadecimal value and its DSCP decimal number, something like this:
>
>> https://support.riverbed.com/bin/support/static/n0glmtc5kegfi7htfe7msdsgcb/html/uc6d3bbkbug83sroi75ersdj9i/sc_ug_html/index.html#page/sh_sd/app_tosdscp_qosclass.html
>
>  Therefore, instead of AF11, we use as a name the DSCP number 10 whose hex value would be 0x28. We have a total of 12 DSCP values for our traffic markings. 
>
> I was thinking that perhaps it's a matter of adding these values to the list of supported symbolic values which in our case may look like this:
>
> MARKING_MAP = {'10': 0x28,
>                               '11': 0x2c,
>                               '13': 0x34,
>                               '15': 0x38,
>                               '17': 0x40,
>                               '19': 0x4c,
>                               '20': 0x50,
>                               '21': 0x54,
>                               '23': 0x5c,
>                               '25': 0x64,
>                               '27': 0x6c,
>                               '29': 0x74}
>
> So that, if I enter parameters:
>
> --test-parameter markings=10,13,15  
>
> Packets would carry ToS hex value:
>
> Differentiated Services Field: 0x28 (DSCP: 10, ECN: Not-ECT)
>  Differentiated Services Field: 0x34 (DSCP: 13, ECN: Not-ECT)
>  Differentiated Services Field: 0x38 (DSCP: 15, ECN: Not-ECT)
>
> Do you think this is possible? or what would be the right approach?

You could do that, of course, but since these will be specific to your
environment I can't include such a patch into Flent itself, so you'd
have to maintain that patch yourself.

An alternative is to use the hex values directly, and couple them with
the 'labels' test parameter to get the right plot labels. So you could
do this:

--test-parameter markings=0x28,0x34,0x38  --test-parameter labels=10,13,15

and that would achieve the same as updating the MARKING_MAP - you just
need to keep the order synced between the 'labels' and 'markings'
parameter.

Up to you which one you think is easiest to maintain, I guess :)


-- 
You are receiving this because you commented.
Reply to this email directly or view it on GitHub:
https://github.com/tohojo/flent/issues/203#issuecomment-620495061

[-- Attachment #1.2: Type: text/html, Size: 3983 bytes --]

[-- Attachment #2: Type: text/plain, Size: 151 bytes --]

_______________________________________________
Flent-users mailing list
Flent-users@flent.org
http://flent.org/mailman/listinfo/flent-users_flent.org