Received packets not showing in stats

Aparna Suri

unread,

May 31, 2016, 4:21:54 PM5/31/16

to TRex Traffic Generator

Hello,

I have the following setup :

Xeon Server 1 with TRex installed sending packets to Xeon Server 2 (DUT), which is running the DPDK L2 forwarding app. Both the servers have Intel X710 NIC cards.

The question I have is that in the statistics, I see that the Rx Rate is same as the Tx Rate, however, the rx_ok counter shows 0 all the time. Also, the ipackets counter is 0.

Here are the statistics. I have highlighted the numbers of concern in bold.

-Per port stats table

ports | 0 | 1

-----------------------------------------------------------------------------------------

opackets | 3010 | 3010

obytes | 186653 | 186701

ipackets | 0 | 0

ibytes | 186701 | 186653

ierrors | 0 | 0

oerrors | 0 | 0

Tx Bw | 423.83 Kbps | 423.94 Kbps

Global stats enabled

Cpu Utilization : 0.0 % 8.8 Gb/core

Platform_factor : 1.0

Total-Tx : 415.11 Kbps

Total-Rx : 415.11 Kbps

Total-PPS : 836.67 pps

Total-CPS : 0.50 cps

Expected-PPS : 2.00 pps

Expected-CPS : 1.00 cps

Expected-BPS : 1.30 Kbps

Active-flows : 0 Clients : 508 Socket-util : 0.0000 %

Open-flows : 1 Servers : 252 Socket : 1 Socket/Clients : 0.0

drop-rate : 0.00 bps

current time : 2.3 sec

test duration : 97.7 sec

-Latency stats enabled

Cpu Utilization : 0.0 %

if| tx_ok , rx_ok , rx check ,error, latency (usec) , Jitter max window

| , , , , average , max , (usec)

----------------------------------------------------------------------------------------------------------------

0 | 3007, 0, 0, 0, 0 , 0, 0 | 0 0 0 0 0 0 0 0 0 0 0 0 0

1 | 3007, 0, 0, 0, 0 , 0, 0 | 0 0 0 0 0 0 0 0 0 0 0 0 0

DPDK app statistics :

Port statistics ====================================

Statistics for port 0 ------------------------------

Packets sent: 2913

Packets received: 2913

Packets dropped: 0

Statistics for port 1 ------------------------------

Packets sent: 2913

Packets received: 2913

Packets dropped: 0

Aggregate statistics ===============================

Total packets sent: 5826

Total packets received: 5826

Total packets dropped: 0

====================================================

This means that the packets are coming in and going out of the DUT. Any idea what's going wrong here? Is there any way for me to look at more diagnostics? Like packets dropped, etc.

Thanks and Regards,

Aparna

santhosh kumar

unread,

May 31, 2016, 8:27:57 PM5/31/16

to TRex Traffic Generator, aparn...@gmail.com

Hi,

you need to configure the Dst mac (l2fwd dut ports mac) in the /etc/trex_cfg.yaml file to receive the packets.

- dest_mac : [0x68,0x05,0xCA,0x19,0xEF,0xD2]

src_mac : [0x02,0x00,0x00,0x00,0x00,0x00] # port 0

- dest_mac : [0x68,0x05,0xCA,0x19,0xEF,0xD0]

src_mac : [0x02,0x00,0x00,0x00,0x00,0x01] # port 1

hanoh haim

unread,

Jun 1, 2016, 1:49:55 AM6/1/16

to Aparna Suri, TRex Traffic Generator

Hi,

Known issue with XL710 stats.

You should configure the DPDK l2 app to set the destination MAC for TRex port MAC from /etc/trex_cfg.yaml

Hanoh

--
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/CAP5Vxgjb_gTwLsOOw0D8rQZ1VV%2BWCSGaS%3DK5PB6z1h4LciCx_g%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

--

Hanoh

Sent from my iPhone

Aparna Suri

unread,

Jun 1, 2016, 3:47:59 PM6/1/16

to hanoh haim, TRex Traffic Generator

Thanks for the responses. I have set the destination MAC address in the app to the addresses of the TRex ports configured. The total Rx Kbps counter gets updated but rx_ok doesn't and shows 0.

Here's more information :

In my /etc/trex_cfg.yaml file :

port_limit : 2 # this option can limit the number of port of the platform

version : 2

interfaces : ["83:00.0","83:00.1"] #the interfaces using ./dpdk_setup_ports.py -s

port_info : # set eh mac addr

- dest_mac : [0x00,0x00,0x00,0x01,0x00,0x00] # router mac addr should be taken from router

src_mac : [0x00,0x00,0x00,0x02,0x00,0x00] # source mac-addr - taken from ifconfig

- dest_mac : [0x00,0x00,0x00,0x03,0x00,0x00] # router mac addr taken from router

src_mac : [0x00,0x00,0x00,0x04,0x00,0x00] #source mac-addr taken from ifconfig

And in the l2fwd app, I have set the destination MACs to be 00:00:00:02:00:00 and 00:00:00:04:00:00. Anything I'm missing here?

Thanks and Regards,

Aparna

hanoh haim

unread,

Jun 2, 2016, 12:30:43 AM6/2/16

to Aparna Suri, TRex Traffic Generator

Hi,

Can you send the output of the TRex window?

It is a MAC addr issue, try to replace the ports MAC

Hanoh

hanoh haim

unread,

Jun 2, 2016, 12:34:54 AM6/2/16

to Aparna Suri, TRex Traffic Generator

Another suggestion is to loopback TRex port and configure the MAC like this

2

4

2

Thanks,

Hanoh

Aparna Suri

unread,

Jun 2, 2016, 11:41:00 AM6/2/16

to hanoh haim, TRex Traffic Generator

Thanks Hanoh. I tried the loopback test first before trying this test out and that worked. Regarding the MAC addresses, I changed them from 1,2,3 and 4 to the 68:05:CA series, and it still doesn't show packets under rx_ok. This is the TRex window output :

Let me know if you need any more information.

Thanks and Regards,

Aparna

hanoh haim

unread,

Jun 2, 2016, 2:06:02 PM6/2/16

to Aparna Suri, TRex Traffic Generator

Hi,

It is the same issue. Try to print the packets from DPDK app. The destination MAC should be TRex port MAC from trex_cfg.yaml file

Thanks

Hanoh

Aparna Suri

unread,

Jun 6, 2016, 4:35:22 PM6/6/16

to hanoh haim, TRex Traffic Generator

Hello Hanoh,

I tried printing the MAC addresses and they match with the TRex port MAC from the file. I had configured them in the trex_cfg.yaml file and they are being printed correctly. What else could be the possible reason for TRex not being able to identify the packets as being received?

Thanks and Regards,

Aparna

hanoh haim

unread,

Jun 7, 2016, 1:23:40 PM6/7/16

to Aparna Suri, TRex Traffic Generator

Hi, it is only MAC issue.

Could you send output of trex server adding the following flags

-v 7 --iom 0

Aparna Suri

unread,

Jun 8, 2016, 12:50:43 PM6/8/16

to hanoh haim, TRex Traffic Generator

Hi Hanoh,

This is the output after adding the flags :

file stats

=================

m_total_bytes : 3.96 Kbytes

m_total_pkt : 50.00 pkt

m_total_open_flows : 25.00 flows

m_total_pkt : 50

m_total_open_flows : 25

m_total_close_flows : 25

m_total_bytes : 4050

file stats

=================

m_total_bytes : 3.96 Kbytes

m_total_pkt : 50.00 pkt

m_total_open_flows : 25.00 flows

m_total_pkt : 50

m_total_open_flows : 25

m_total_close_flows : 25

m_total_bytes : 4050

file stats

=================

m_total_bytes : 3.96 Kbytes

m_total_pkt : 50.00 pkt

m_total_open_flows : 25.00 flows

m_total_pkt : 50

m_total_open_flows : 25

m_total_close_flows : 25

m_total_bytes : 4050

file stats

=================

m_total_bytes : 3.96 Kbytes

m_total_pkt : 50.00 pkt

m_total_open_flows : 25.00 flows

m_total_pkt : 50

m_total_open_flows : 25

m_total_close_flows : 25

m_total_bytes : 4050

latency daemon has stopped

==================

interface sum

==================

---------------

port : 0

------------

opackets : 107669

obytes : 6676578

ipackets : 0

ibytes : 5028791

Tx : 297.69 Kbps

port : 1

------------

opackets : 107669

obytes : 6678178

ipackets : 0

ibytes : 5029047

Tx : 297.70 Kbps

Cpu Utilization : 0.0 % 3.2 Gb/core

Platform_factor : 1.0

Total-Tx : 595.39 Kbps

Total-Rx : 595.39 Kbps

Total-PPS : 1.20 Kpps

Total-CPS : 0.06 cps

Expected-PPS : 2.00 pps

Expected-CPS : 1.00 cps

Expected-BPS : 1.30 Kbps

Active-flows : 0 Clients : 508 Socket-util : 0.0000 %

Open-flows : 100 Servers : 252 Socket : 0 Socket/Clients : 0.0

drop-rate : 0.00 bps

==================

interface sum

==================

------------------------

per core stats core id : 1

------------------------

per core per if stats id : 1

------------------------

port 0, queue id :0 - client

----------------------------

port 1, queue id :0 - server

----------------------------

------------------------

per core stats core id : 2

------------------------

per core per if stats id : 2

------------------------

port 0, queue id :1 - client

----------------------------

port 1, queue id :1 - server

----------------------------

------------------------

per core stats core id : 3

------------------------

per core per if stats id : 3

------------------------

port 0, queue id :2 - client

----------------------------

port 1, queue id :2 - server

----------------------------

------------------------

per core stats core id : 4

------------------------

per core per if stats id : 4

------------------------

port 0, queue id :3 - client

----------------------------

port 1, queue id :3 - server

----------------------------

==================

generators

==================

normal

-------------

min_delta : 10 usec

cnt : 6504

high_cnt : 0

max_d_time : 0 usec

sliding_average : 0 usec

precent : 0.0 %

histogram

-----------

m_total_bytes : 3.96 Kbytes

m_total_pkt : 50.00 pkt

m_total_open_flows : 25.00 flows

m_total_pkt : 50

m_total_open_flows : 25

m_total_close_flows : 25

m_total_bytes : 4050

normal

-------------

min_delta : 10 usec

cnt : 6504

high_cnt : 0

max_d_time : 0 usec

sliding_average : 0 usec

precent : 0.0 %

histogram

-----------

m_total_bytes : 3.96 Kbytes

m_total_pkt : 50.00 pkt

m_total_open_flows : 25.00 flows

m_total_pkt : 50

m_total_open_flows : 25

m_total_close_flows : 25

m_total_bytes : 4050

normal

-------------

min_delta : 10 usec

cnt : 6504

high_cnt : 0

max_d_time : 0 usec

sliding_average : 0 usec

precent : 0.0 %

histogram

-----------

m_total_bytes : 3.96 Kbytes

m_total_pkt : 50.00 pkt

m_total_open_flows : 25.00 flows

m_total_pkt : 50

m_total_open_flows : 25

m_total_close_flows : 25

m_total_bytes : 4050

normal

-------------

min_delta : 10 usec

cnt : 6504

high_cnt : 0

max_d_time : 0 usec

sliding_average : 0 usec

precent : 0.0 %

histogram

-----------

m_total_bytes : 3.96 Kbytes

m_total_pkt : 50.00 pkt

m_total_open_flows : 25.00 flows

m_total_pkt : 50

m_total_open_flows : 25

m_total_close_flows : 25

m_total_bytes : 4050

==================

latency

==================

Cpu Utilization : 0.1 %

if| tx_ok , rx_ok , rx check ,error, latency (usec) , Jitter max window

| , , , , average , max , (usec)

----------------------------------------------------------------------------------------------------------------

0 | 107569, 0, 0, 0, 0 , 0, 0 | 0 0 0 0 0 0 0 0 0 0 0 0 0

1 | 107569, 0, 0, 0, 0 , 0, 0 | 0 0 0 0 0 0 0 0 0 0 0 0 0

cpu : 0.1 %

port 0

-----------------

counter

-----------

m_tx_pkt_ok : 107569

-----------

min_delta : 10 usec

cnt : 0

high_cnt : 0

max_d_time : 0 usec

sliding_average : 0 usec

precent : -nan %

histogram

-----------

jitter : 0

port 1

-----------------

counter

-----------

m_tx_pkt_ok : 107569

-----------

min_delta : 10 usec

cnt : 0

high_cnt : 0

max_d_time : 0 usec

sliding_average : 0 usec

precent : -nan %

histogram

-----------

jitter : 0

rx_checker is disabled

---------------

port : 0

------------

opackets : 107669

obytes : 6676578

ipackets : 0

ibytes : 5028791

Tx : 297.69 Kbps

port : 1

------------

opackets : 107669

obytes : 6678178

ipackets : 0

ibytes : 5029047

Tx : 297.70 Kbps

Cpu Utilization : 0.0 % 4.3 Gb/core

Platform_factor : 1.0

Total-Tx : 595.39 Kbps

Total-Rx : 595.39 Kbps

Total-PPS : 1.20 Kpps

Total-CPS : 0.06 cps

Expected-PPS : 2.00 pps

Expected-CPS : 1.00 cps

Expected-BPS : 1.30 Kbps

Active-flows : 0 Clients : 508 Socket-util : 0.0000 %

Open-flows : 100 Servers : 252 Socket : 0 Socket/Clients : 0.0

drop-rate : 0.00 bps

summary stats

--------------

Total-pkt-drop : 215338 pkts

Total-tx-bytes : 13354756 bytes

Total-tx-sw-bytes : 14199108 bytes

Total-rx-bytes : 10057838 byte

Total-tx-pkt : 215338 pkts

Total-rx-pkt : 0 pkts

Total-sw-tx-pkt : 215138 pkts

Total-sw-err : 0 pkts

maximum-latency : 0 usec

average-latency : 0 usec

latency-any-error : ERROR

My /etc/trex_cfg.yaml file :

port_limit : 2 # this option can limit the number of port of the platform

version : 2

interfaces : ["83:00.0","83:00.1"] #the interfaces using ./dpdk_setup_ports.py -s

port_info : # set eh mac addr

- dest_mac : [0x68,0x05,0xca,0x30,0xab,0x34] # router mac addr should be taken from router

src_mac : [0x68,0x05,0xca,0x30,0xac,0x69] # source mac-addr - taken from ifconfig

- dest_mac : [0x68,0x05,0xca,0x30,0xab,0x35] # router mac addr taken from router

src_mac : [0x68,0x05,0xca,0x30,0xac,0x70] #source mac-addr taken from ifconfig

DPDK L2 forwarding app :

static void

l2fwd_simple_forward(struct rte_mbuf *m, unsigned portid)

{

struct ether_hdr *eth;

void *tmp;

unsigned dst_port;

uint64_t ext_dest_mac[2] = {0x69AC30CA0568, 0x70AC30CA0568}; ==> I have declared this array globally

dst_port = l2fwd_dst_ports[portid];

eth = rte_pktmbuf_mtod(m, struct ether_hdr *);

/* 02:00:00:00:00:xx */

tmp = &eth->d_addr.addr_bytes[0];

/* *((uint64_t *)tmp) = 0x000000000002 + ((uint64_t)dst_port << 40); */

*((uint64_t *)tmp) = ext_dest_mac[portid];

Thanks and Regards,

Aparna

hanoh haim

unread,

Jun 8, 2016, 1:08:14 PM6/8/16

to Aparna Suri, TRex Traffic Generator

- I was more interested in The output of TRex server init time.

- MAC addr is 6 bytes why you are overriding the 2 MSB bytes of the src MAC?

- Let me suggest to change the L2 app to be like a wire. Configure it both ports as promiscuous . Port 0->1 and 1->0. No need to change MAC.

- Change trex_cfg to be valid for loopback (a->b, b->a)

Thanks,

Aparna Suri

unread,

Jun 8, 2016, 2:45:40 PM6/8/16

to hanoh haim, TRex Traffic Generator

Hi Hanoh,

Here are the answers to your suggestions :

- I was more interested in The output of TRex server init time.

Starting TRex v2.00 please wait ...

found configuration file at /etc/trex_cfg.yaml

port limit : 2

port_bandwidth_gb : 10

if_mask : None

thread_per_dual_if : 1

if : 83:00.0, 83:00.1,

enable_zmq_pub : 1

zmq_pub_port : 4500

m_zmq_rpc_port : 4501

src : 68:05:ca:30:ab:34

dest : 68:05:ca:30:ac:69

src : 68:05:ca:30:ab:35

dest : 68:05:ca:30:ac:70

memory per 2x10G ports

MBUF_64 : 16380

MBUF_128 : 8190

MBUF_256 : 8190

MBUF_512 : 8190

MBUF_1024 : 8190

MBUF_2048 : 4095

MBUF_4096 : 128

MBUF_9K : 512

TRAFFIC_MBUF_64 : 65520

TRAFFIC_MBUF_128 : 32760

TRAFFIC_MBUF_256 : 8190

TRAFFIC_MBUF_512 : 8190

TRAFFIC_MBUF_1024 : 8190

TRAFFIC_MBUF_2048 : 65520

TRAFFIC_MBUF_4096 : 128

TRAFFIC_MBUF_9K : 512

MBUF_DP_FLOWS : 524288

MBUF_GLOBAL_FLOWS : 5120

no platform info

flags : 8040f00

write_file : 0

verbose : 7

realtime : 1

flip : 0

cores : 4

single core : 0

flow-flip : 0

no clean close : 0

1g mode : 0

zmq_publish : 1

vlan_enable : 0

mbuf_cache_disable : 0

mac_ip_features : 0

mac_ip_map : 0

vm mode : 0

cfg file : cap2/dns.yaml

mac file :

out file :

duration : 100

factor : 1

mbuf_factor : 1

latency : 1000 pkt/sec

zmq_port : 4500

telnet_port : 4501

expected_ports : 2

mac spreading: 0

port : 0 dst:68:05:ca:30:ab:34 src:68:05:ca:30:ac:69

port : 1 dst:68:05:ca:30:ab:35 src:68:05:ca:30:ac:70

port : 2 dst:00:00:00:01:00:00 src:00:00:00:01:00:00

port : 3 dst:00:00:00:01:00:00 src:00:00:00:01:00:00

port : 4 dst:00:00:00:01:00:00 src:00:00:00:01:00:00

port : 5 dst:00:00:00:01:00:00 src:00:00:00:01:00:00

port : 6 dst:00:00:00:01:00:00 src:00:00:00:01:00:00

port : 7 dst:00:00:00:01:00:00 src:00:00:00:01:00:00

port : 8 dst:00:00:00:01:00:00 src:00:00:00:01:00:00

port : 9 dst:00:00:00:01:00:00 src:00:00:00:01:00:00

port : 10 dst:00:00:00:01:00:00 src:00:00:00:01:00:00

port : 11 dst:00:00:00:01:00:00 src:00:00:00:01:00:00

Total Memory :

MBUF_64 : 81900

MBUF_128 : 40950

MBUF_256 : 16380

MBUF_512 : 16380

MBUF_1024 : 16380

MBUF_2048 : 69615

MBUF_4096 : 256

MBUF_9K : 1024

MBUF_DP_FLOWS : 524288

MBUF_GLOBAL_FLOWS : 5120

get_each_core_dp_flows : 524288

Total memory : 72.00 Mbytes

there is no configuration file given

args

xx

-c

0x3f

-n

4

--log-level

8

-w

83:00.0

-w

83:00.1

- MAC addr is 6 bytes why you are overriding the 2 MSB bytes of the src MAC?

I am not overriding the MSB bytes of the src MAC anywhere as far as I know. Are you asking about the src MAC in the trex_cfg.yaml file? I have 6 bytes over there.

- Let me suggest to change the L2 app to be like a wire. Configure it both ports as promiscuous . Port 0->1 and 1->0. No need to change MAC.

My understanding from your suggestion is that I shouldn't configure any destination MAC address for the outgoing packet in the L2 app. This is the output for the test Let me know if I didn't understand this correctly.

if| tx_ok , rx_ok , rx check ,error, latency (usec) , Jitter max window

| , , , , average , max , (usec)

----------------------------------------------------------------------------------------------------------------

0 | 107568, 0, 0, 0, 0 , 0, 0 | 0 0 0 0 0 0 0 0 0 0 0 0 0

1 | 107568, 0, 0, 0, 0 , 0, 0 | 0 0 0 0 0 0 0 0 0 0 0 0 0

cpu : 0.1 %

port 0

-----------------

counter

-----------

m_tx_pkt_ok : 107568

-----------

min_delta : 10 usec

cnt : 0

high_cnt : 0

max_d_time : 0 usec

sliding_average : 0 usec

precent : -nan %

histogram

-----------

jitter : 0

port 1

-----------------

counter

-----------

m_tx_pkt_ok : 107568

-----------

min_delta : 10 usec

cnt : 0

high_cnt : 0

max_d_time : 0 usec

sliding_average : 0 usec

precent : -nan %

histogram

-----------

jitter : 0

rx_checker is disabled

---------------

port : 0

------------

opackets : 107668

obytes : 6676516

ipackets : 0

ibytes : 0

Tx : 297.65 Kbps

port : 1

------------

opackets : 107668

obytes : 6678116

ipackets : 0

ibytes : 0

Tx : 297.62 Kbps

Cpu Utilization : 0.0 % 4.3 Gb/core

Platform_factor : 1.0

Total-Tx : 595.27 Kbps

Total-Rx : 0.00 bps

Total-PPS : 1.20 Kpps

Total-CPS : 0.06 cps

Expected-PPS : 2.00 pps

Expected-CPS : 1.00 cps

Expected-BPS : 1.30 Kbps

Active-flows : 0 Clients : 508 Socket-util : 0.0000 %

Open-flows : 100 Servers : 252 Socket : 0 Socket/Clients : 0.0

drop-rate : 595.27 Kbps

summary stats

--------------

Total-pkt-drop : 215336 pkts

Total-tx-bytes : 13354632 bytes

Total-tx-sw-bytes : 14198976 bytes

Total-rx-bytes : 0 byte

Total-tx-pkt : 215336 pkts

Total-rx-pkt : 0 pkts

Total-sw-tx-pkt : 215136 pkts

Total-sw-err : 0 pkts

maximum-latency : 0 usec

average-latency : 0 usec

latency-any-error : ERROR :

DPDK app output :

Port statistics ====================================

Statistics for port 0 ------------------------------

Packets sent: 107668

Packets received: 107668

Packets dropped: 0

Statistics for port 1 ------------------------------

Packets sent: 107668

Packets received: 107668

Packets dropped: 0

Aggregate statistics ===============================

Total packets sent: 215336

Total packets received: 215336

Total packets dropped: 0

====================================================

- Change trex_cfg to be valid for loopback (a->b, b->a)

This configuration works. The summary is as follows :

summary stats

--------------

Total-pkt-drop : 0 pkts

Total-tx-bytes : 13355500 bytes

Total-tx-sw-bytes : 14199900 bytes

Total-rx-bytes : 13355500 byte

Total-tx-pkt : 215350 pkts

Total-rx-pkt : 215350 pkts

Total-sw-tx-pkt : 215150 pkts

Total-sw-err : 0 pkts

maximum-latency : 10 usec

average-latency : 5 usec

latency-any-error : OK

Let me know if you need any other information.

Thanks and Regards,

Aparna

hanoh haim

unread,

Jun 9, 2016, 12:35:01 AM6/9/16

to Aparna Suri, TRex Traffic Generator

- Debug info are OK

- Did the loopback trex_config worked with the L2 DPDK app? It should

Hanoh

Aparna Suri

unread,

Jun 9, 2016, 5:48:03 PM6/9/16

to hanoh haim, TRex Traffic Generator

Hi Hanoh,

Yes the loopback test worked. I changed the MAC addresses in the trex_cfg.yaml file to match the default forwarding MAC address in the l2fwd app (which is 02:00:00:00:00:01 and 02:00:00:00:00:02) and now I'm able to see packets being received and it is working fine. Thanks for all the help.

Regards,

Aparna

Shashank B.R

unread,

Oct 4, 2021, 8:15:11 AM10/4/21

to TRex Traffic Generator

Hi All,

I am testing the DPDK L2fwd application exactly as in the setup diagram using TRex traffic generator.

I have tried updating the MAC addresses of 02:00:00:00:00:01 at -dest_mac of Port 0 and 02:00:00:00:00:02 at -src_mac of Port 1 of trex_cfg file with other 2 MAC addresses with that of the traffic generator interface.

The flow direction used in dns.yaml is towards Port 0.

However I am unable to receive packets at the Rx side of TRex.

Could you suggest me the order of MAC addresses specified for loopback to work and get the packets at the Rx side of Trex?