trex console connectivity

[Vijay Ram]

Hi,

I have a requirement to send/receive traffic between linux VMs of AWS (TRex server) and Azure (TRex client). I'm running separate TRex instances in AWS VM and Azure VM in ASTF mode. As initial step am not using DPDK ports and version used is V2.81 in both VMs. I have eth0 and eth1 in both VMs. eth0 is used for SSH Mgmt traffic so I decided to use eth1 for this TRex data traffic.

In TRex server instance, I configured my /etc/trex_cfg.yaml to use "eth1", "dummy" and specified eth1 IP/Gateway. Server was running successful and ports 0.0.0.0/4500 and 0.0.0.0/4501.

In TRex client instance (logged into eth0 interface of client VM), I tried "./trex-console -s <eth1 of server>". But am unable to connect "tcp://eth1 of server/4501". Looks like client is using eth0 port to connect eth1 of server. How to enforce trex-console client to eth1 to connect eth1 of server? 

I don't see option to input trex config file in "trex-console" utility

[hanoh haim]

Hi Vijay, 

trex should have 2 separate interfaces, one for management and one for data

without this you might cut the branch you are sitting on. 

[Vijay Ram]

Thanks for your email Hanoch.

Yes I'm using eth0 for SSH and eth1 for TRex data traffic.

Sounds too basic but am using TRex for the first time and I would like to confirm my understanding

TRex client on AWS VM -----> Router------>TRex server on Azure VM

TRex is running on two different VM machines. Based on documentation I used ASTF client/server mode.

Should I use below,

Server:

./t-rex-64 -i --astf --cfg /etc/trex_cfg.yaml --astf-server-only

Client:

./t-rex-64 -i --astf --cfg /etc/trex_cfg.yaml --astf-client-mask 0x1

Server Cgf file:

  interfaces    : ["dummy", "eth1"]

  port_info       :  # Port IPs. Change to suit your needs. In case of loopback, you can leave as is.

          - ip         : 192.168.12.78

            default_gw : 192.168.12.65

Client Cfg file:

  interfaces    : ["eth1","dummy"]

  port_info       :  # Port IPs. Change to suit your needs. In case of loopback, you can leave as is.

          - ip         : 192.168.12.40

            default_gw : 192.168.12.33

Is my port configuration correct? with the reversal of port in server mode?

Just to understand, "trex-console" can be used in both client and server machines to see the state in detailed manner