Transmit state on subset of flows not supported

[open-traffic-generator]

Transmit state on subset of flows not supported

[ankur-sheth]

@shramroy @biplamal @ashutshkumr I believe we've resolved this issue, right? If so, please confirm and close it.

[jamirovolt]

Hi,

sorry for the late in testing it. I just tryied with the last release but it doesn't work. If i try to start only one of the two configured flows, the engine doesn't start.

This is my conf:

{"ports":[{"location":"localhost:5555","name":"p1"},{"location":"localhost:5555","name":"p2"}],"layer1":[{"port_names":["p1","p2"],"speed":"speed_1_gbps","name":"ly"}],"captures":[{"port_names":["p1"],"name":"cp"}],"flows":[{"name":"f1","tx_rx":{"port":{"tx_name":"p1","rx_name":"p2"},"choice":"port"},"size":{"fixed":"576","choice":"fixed"},"duration":{"fixed_seconds":{"seconds":300},"choice":"fixed_seconds"},"rate":{"mbps":"1","choice":"mbps"},"packet":[{"ethernet":{"src":{"value":"00:0C:29:5D:18:88","choice":"value"},"dst":{"value":"00:50:56:FF:BF:77","choice":"value"}},"choice":"ethernet"},{"ipv4":{"src":{"value":"192.168.163.133","choice":"value"},"dst":{"value":"10.10.10.10","choice":"value"}},"choice":"ipv4"},{"udp":{"src_port":{"increment":{"start":5000,"step":2,"count":10},"choice":"increment"},"dst_port":{"values":[10000],"choice":"values"}},"choice":"udp"}],"metrics":{"enable":true}},{"name":"f2","tx_rx":{"port":{"tx_name":"p1","rx_name":"p2"},"choice":"port"},"size":{"fixed":"576","choice":"fixed"},"duration":{"fixed_seconds":{"seconds":300},"choice":"fixed_seconds"},"rate":{"mbps":"1","choice":"mbps"},"packet":[{"ethernet":{"src":{"value":"00:0C:29:5D:18:88","choice":"value"},"dst":{"value":"00:50:56:FF:BF:77","choice":"value"}},"choice":"ethernet"},{"ipv4":{"src":{"value":"192.168.163.133","choice":"value"},"dst":{"value":"10.10.10.20","choice":"value"}},"choice":"ipv4"},{"udp":{"src_port":{"increment":{"start":5000,"step":2,"count":10},"choice":"increment"},"dst_port":{"values":[10000],"choice":"values"}},"choice":"udp"}],"metrics":{"enable":true}}]}

and this is the start.json:

{
"flow_names": [
"f1"
],
"state": "start"
}

[ashutshkumr]

@jamirovolt this is still not out as part of the release. It is planned for the release we’re planning to put out in second week of July.

Will announce the release version here as soon as it’s out.

[jamirovolt]

@ashutshkumr Thank you. Just a question: in the next release there also will be the possibility to upgrade the configuration of a flow without restarting the other flows?

[shramroy]

@jamirovolt We currently support upgrading the flow rate without stopping or restarting any flow. You can visit the below link and explore the api - https://redocly.github.io/redoc/?url=https://raw.githubusercontent.com/open-traffic-generator/models/master/artifacts/openapi.yaml&nocors#tag/Control/operation/update_flows .

Any other field of the flow do you need to upgrade likewise?

[jamirovolt]

@shramroy I would like to stop a certain flow (e.g. f1) without stopping the other started flows (e.g. f2), change destination IP Address, Test duration, Rate and Packet Size of the flow f1 and then restart the flow f1 without any impact on the flow f2. In this way i would be able to test different targets without stopping other tests.

[ashutshkumr]

@jamirovolt this is currently not supported from the spec itself, and the reason is to avoid complexity.

Just trying to understand the use case in more details here so I can further discuss with team.

You can always have multiple flows with different configurations that can be started/stopped independent of each other (thus avoiding reconfiguration of single flow). i.e. in your case, you could have two different flows, each with different ip/rate/size.

[jamirovolt]

@ashutshkumr Yes, but i need to change when i want the configuration of a flow without affecting the others.

[ashutshkumr]

@jamirovolt that's why I'm trying to understand the use case better. So far whatever use case you've presented does not require re-configuring existing flow.

e.g. in your case, here's what the test step would look like

• configure flows f1, f2 and f3
  • f3 would basically be "reconfigured version" of f1
  • f2 is that independent flow that you don't wish to interrupt
• Start f1 and f2
• Stop f1
• Start f3

Please note, stopping and restarting an existing flow will always clear flow metrics - hence you're better off working with multiple flows instead of reconfiguring single flow (at least for the use case you presented).

[jamirovolt]

@ashutshkumr The problem is that i can't know the configuration of all flows in advance because i'm trying to provide a web portal by which a user can generate traffic towards an IP destination when he wants.