Running TRex with another DPDK app
aparna.suri
I'm trying to run TRex v2.15 with another DPDK app like L2 forwarding on the same system. I have the L2 forwarding app running on one NIC card and TRex running on another NIC card. Both NIC cards are X710 with the latest firmware. I have also set the prefix option and limit memory option to 1024 in /etc/trex_cfg.yaml. Even then, I see the "Cannot get hugepage information" error if I try to run the TRex server and the DPDK app simultaneously. Is there anything else I can do to make this setup work?
Thanks,
Aparna
hanoh haim
--
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+unsubscribe@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/22d54777-6ba5-4f5a-b76f-3d47ac1daf63%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
aparna.s
To: Aparna Suri
You are hitting
https://trex-tgn.cisco.com/youtrack/issueMobile/trex-342
Hanoh
On Thu, 9 Feb 2017 at 20:55 hanoh haim wrote:
BTW if you have MAC configured in trex_cfg there is a bug that was fixed in v2.17 (link down need to resolved again only in case of L3)
Hanoh
On Thu, 9 Feb 2017 at 20:53 Aparna Suri wrote:
Sure, thanks a lot for the help
On Thu, Feb 9, 2017 at 12:48 PM, hanoh haim wrote:
This is expected. When link is going down and up you need to resolve again (ARP) as you might connect to another DUT.
Look into the arp chapter how to re-resolve
Hanoh
On Thu, 9 Feb 2017 at 20:45 Aparna Suri wrote:
Sure, will do. Another error I'm seeing is this : Port(s) [0] have unresolved destination addresses - please resolve them or specify 'force', on the TRex console when I try to start traffic.
So when I start the DPDK app first, and then TRex server - everything works fine.
Then I close the DPDK app, and restart it again, the TRex server is still running continuously, and I start traffic from the console and I see this error.
On Thu, 9 Feb 2017 at 20:27 Aparna Suri wrote:
Thanks a lot Hanoh, that worked!
On Thu, Feb 9, 2017 at 11:47 AM, hanoh haim wrote:
xx
-c
0x7
-n
4
--log-level
8
--master-lcore
0
-w
86:00.0
-w
86:00.1
--file-prefix
setup1
-m
1024
This is our EAL switch which work with your app (does not reset your ports)
Hanoh
On Thu, 9 Feb 2017 at 19:41 hanoh haim wrote:
Try to use -w pci for EAL in your app
On Thu, 9 Feb 2017 at 19:27 Aparna Suri wrote:
Note that the DPDK app is running on 0000:05:00.2 and 0000:05:00.3 and TRex runs on 86:00.0 and 86:00.1. So I don't understand why the links should be shown as down in the TRex server when the application isn't running, since the ports are completely independent between the two.
On Thu, Feb 9, 2017 at 11:21 AM, Aparna Suri wrote:
There's some progress - the server comes up now. For this I limited the -m option in EAL (limit memory) in the DPDK app to 512. Now, the problem is that : when I start the TRex server, and then launch the DPDK app, the ports always show as DOWN in the TRex server and I'm not able to send traffic. If I start the app first and then the TRex server, it works. Is the order important by any chance?
This is my trex_cfg.yaml :
- port_limit : 2 # this option can limit the number of port of the platform
version : 2
interfaces : ["86:00.0","86:00.1"] #the interfaces using ./dpdk_setup_ports.py -s : to specify an Rx-Tx pair, each port is unidirectional
prefix : setup1
limit_memory : 1024
port_info : # set eh mac addr
- dest_mac : [0x3c,0xfd,0xfe,0x9e,0x65,0x40] # router mac addr should be taken from router
src_mac : [0x02,0x00,0x00,0x00,0x00,0x00] # source mac-addr - taken from ifconfig
- dest_mac : [0x3c,0xfd,0xfe,0x9e,0x65,0x41] # router mac addr should be taken from router
src_mac : [0x02,0x00,0x00,0x00,0x00,0x01] # source mac-addr - taken from ifconfig
./t-rex-64 -i -v 7
Killing Scapy server... Scapy server is killed
Starting Scapy server..... Scapy server is started
Failed to read classid file: Object not found
Starting TRex v2.15 please wait ...
Using configuration file /etc/trex_cfg.yaml
port limit : 2
port_bandwidth_gb : 10
if_mask : None
prefix : setup1
limit_memory : 1024
thread_per_dual_if : 1
if : 86:00.0, 86:00.1,
enable_zmq_pub : 1
zmq_pub_port : 4500
m_zmq_rpc_port : 4501
src : 02:00:00:00:00:00
dest : 3c:fd:fe:9e:65:40
src : 02:00:00:00:00:01
dest : 3c:fd:fe:9e:65:41
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
CTimerWheelYamlInfo does not exist
flags : 8010f00
write_file : 0
verbose : 7
realtime : 1
flip : 0
cores : 1
single core : 0
flow-flip : 0
no clean close : 0
zmq_publish : 1
vlan_enable : 0
client_cfg : 0
mbuf_cache_disable : 0
vm mode : 0
cfg file :
mac file :
out file :
client cfg file :
duration : 0
factor : 1
mbuf_factor : 1
latency : 0 pkt/sec
zmq_port : 4500
telnet_port : 4501
expected_ports : 2
tw_bucket_usec : 20.000000 usec
tw_buckets : 1024 usec
tw_levels : 3 usec
port : 0 dst:3c:fd:fe:9e:65:40 src:02:00:00:00:00:00
port : 1 dst:3c:fd:fe:9e:65:41 src:02:00:00:00:00:01
port : 2 dst:00:00:00:01:00:00 src:00:00:00:00:00:00
port : 3 dst:00:00:00:01:00:00 src:00:00:00:00:00:00
port : 4 dst:00:00:00:01:00:00 src:00:00:00:00:00:00
port : 5 dst:00:00:00:01:00:00 src:00:00:00:00:00:00
port : 6 dst:00:00:00:01:00:00 src:00:00:00:00:00:00
port : 7 dst:00:00:00:01:00:00 src:00:00:00:00:00:00
port : 8 dst:00:00:00:01:00:00 src:00:00:00:00:00:00
port : 9 dst:00:00:00:01:00:00 src:00:00:00:00:00:00
port : 10 dst:00:00:00:01:00:00 src:00:00:00:00:00:00
port : 11 dst:00:00:00:01:00:00 src:00:00:00:00:00:00
port : 12 dst:00:00:00:01:00:00 src:00:00:00:00:00:00
port : 13 dst:00:00:00:01:00:00 src:00:00:00:00:00:00
port : 14 dst:00:00:00:01:00:00 src:00:00:00:00:00:00
port : 15 dst:00:00:00:01:00:00 src:00:00:00:00: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
On Thursday, February 9, 2017 at 2:10:23 AM UTC-6, Hanoch Haim wrote:
> Hi Aparna,
>
>
> See this threadhttps://groups.google.com/forum/#!topic/trex-tgn/3pE69Wqlolw
>
>
>
> thanks
> Hanoh
>
>
> On Thu, Feb 9, 2017 at 1:30 AM, aparna.suri wrote:
> Hi,
>
>
>
> I'm trying to run TRex v2.15 with another DPDK app like L2 forwarding on the same system. I have the L2 forwarding app running on one NIC card and TRex running on another NIC card. Both NIC cards are X710 with the latest firmware. I have also set the prefix option and limit memory option to 1024 in /etc/trex_cfg.yaml. Even then, I see the "Cannot get hugepage information" error if I try to run the TRex server and the DPDK app simultaneously. Is there anything else I can do to make this setup work?
>
>
>
> Thanks,
>
> Aparna
>
>
>
> --
>
> 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.