Client/Server mode STL?

[graeme.d...@netspan.co.nz]

hello,
We would like to use trex to test inter-DC performance, onw trex in each DC. I see there is client/server mode that would do this.
However Client/Server is mentioned only in ASTF. Is Client/Server mode available in STL at all?

Thanks, Graeme

[Matt Callaghan]

Not exactly sure what is meant by "client/server" mode, but I am inferring that you're talking about single port generators (and in ASTF mode, this is "client/server" sides).

See https://github.com/cisco-system-traffic-generator/trex-core/blob/master/doc/trex_book.asciidoc#36-dummy-ports

(some docs were delivered to improve the understanding of single-port generator support across the modes, and their limitations - has not yet been rebuilt/delivered to MAIN though)

Does that help/answer your question?

[graeme.d...@netspan.co.nz]

Matt, thanks for the response...

On Friday, 17 August 2018 09:43:36 UTC+12, Matt Callaghan wrote:
> Not exactly sure what is meant by "client/server" mode, but I am inferring that you're talking about single port generators (and in ASTF mode, this is "client/server" sides).
>

Yes, two separate physical units, one in each DC.
From the ASTF doc...
2.5 Client/Server only mode https://trex-tgn.cisco.com/trex/doc/trex_astf.html#_client_server_only_mode
With ASTF mode, it is possible to work in either client mode or server mode. This way TRex client side could be installed in one physical location on the network and TRex server in another.

>
> See https://github.com/cisco-system-traffic-generator/trex-core/blob/master/doc/trex_book.asciidoc#36-dummy-ports
> (some docs were delivered to improve the understanding of single-port generator support across the modes, and their limitations - has not yet been rebuilt/delivered to MAIN though)
>

Thanks, this looks promising. The table entry for "Two TRex Generators, Single Interface" shows Stateless mode with status "functional" and Comment as "bidirectional"

>
> Does that help/answer your question?
>

Thanks, that doc update for STL on two single port generators is good pointer.

Our existing use on a single Trex is all STL using the client API to generate multiple specific IP routed streams with PG FlowStats per stream.
I am looking to be able to do the same between two TRex units.

Thanks, Graeme

[brian.s...@wwt.com]

Graeme,

Did ever come up with a solution for running in STL on two separate trex instances? Looking to do the same.

Cheers,

Brian

[Graeme]

Brian,  

haven't yet got to the stage of trying across two units. Actually, we hope to be discovering the answers in the next few weeks.

Rgds, Graeme

[hanoh haim]

I don't see why it should not work. 

The latency timing won't be relevant, so timing will be relative 

--
You received this message because you are subscribed to the Google Groups "TRex Traffic Generator" group.
To unsubscribe from this group and stop receiving emails from it, send an email to trex-tgn+u...@googlegroups.com.
To post to this group, send email to trex...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/trex-tgn/02d3d644-0c8f-4dc5-b3f5-ca4127ddfa06%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

--

Hanoh

Sent from my iPhone

[Graeme]

On Thursday, 15 November 2018 01:52:07 UTC+13, Hanoch Haim wrote:

I don't see why it should not work. 

The latency timing won't be relevant, so timing will be relative 

Between two independent unit I guess STLFlowStats don't work either? (But I'm hoping they can somehow magically) 

[Graeme]

On Thursday, 15 November 2018 08:39:10 UTC+13, Graeme wrote:

Between two independent unit I guess STLFlowStats don't work either? (But I'm hoping they can somehow magically) 

oh ok I found the magic at 2.11.21. Tutorial: Per stream statistics - in-band signalling using the IPv4.id field!

So sounds like it should work between two units, is this correct? 

Thanks, Graeme

[hanoh haim]

Correct 

--

You received this message because you are subscribed to the Google Groups "TRex Traffic Generator" group.
To unsubscribe from this group and stop receiving emails from it, send an email to trex-tgn+u...@googlegroups.com.
To post to this group, send email to trex...@googlegroups.com.

To view this discussion on the web visit https://groups.google.com/d/msgid/trex-tgn/ad29ac00-d0c7-4d77-9fd0-87ce9bee124e%40googlegroups.com.

For more options, visit https://groups.google.com/d/optout.

[sathiy...@gmail.com]

Hi Graeme

Trex usage is new to me, looking forward the reason why two interfaces are mandatory required to be set initially.

Trex will be used as a transmitter to another location running Trex. If this is the case, then why the software is asking for two? during installation??

regards

Sathiyanathan

[SATHIYANATHAN L]

Give a bit more clarity on the client/server flow. If we use one Trex(server) and the other Trex(client) can i pump 100Meg bidirectional from client or only unidirectional?

regards

Sathiyanathan

--
You received this message because you are subscribed to a topic in the Google Groups "TRex Traffic Generator" group.
To unsubscribe from this topic, visit https://groups.google.com/d/topic/trex-tgn/-qj0n_orZAY/unsubscribe.
To unsubscribe from this group and all its topics, send an email to trex-tgn+u...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/trex-tgn/3d39632e-281c-4bd7-95af-27173a78dd68%40googlegroups.com.