diff options
Diffstat (limited to 'trex_book.asciidoc')
| -rwxr-xr-x | trex_book.asciidoc | 41 |
1 files changed, 39 insertions, 2 deletions
diff --git a/trex_book.asciidoc b/trex_book.asciidoc index 6e4e01f6..a037416c 100755 --- a/trex_book.asciidoc +++ b/trex_book.asciidoc @@ -439,7 +439,18 @@ zmq publisher at: tcp://*:4500 <13> Gb/sec generated per core of DP. Higer is better. <14> Rx and latency thread CPU utilization. -WARNING: if you don't see rx packets, revisit your MAC address configuration. +WARNING: If you don't see rx packets, revisit your MAC address configuration. + +==== Running TRex for the first time with virtual NICs + vSwitch + +[NOTE] +===================================================================== +Current limitation: following command will not work as excepted: +.... +sudo ./t-rex-64 -f cap2/dns.yaml --lm 1 --lo -l 1000 -d 100 +.... +vSwitch can't know where to "route" the packet, it supposed to be fixed once TRex supports ARP +===================================================================== ==== Running TRex for the first time with router @@ -1609,7 +1620,7 @@ The TRex output <1> this counter should be zero -=== Troubleshoot installation, FAQ +=== Troubleshoot common problems, FAQ Q: During OS installation, screen is skewed / error "Out of range" / resolution not supported etc. + A: @@ -1617,3 +1628,29 @@ A: * Fedora - during installation, choose "Troubleshooting" -> Install in basic graphic mode * Ubuntu - try Ubuntu server, which has textual installation +Q: How to determine relation between TRex ports and Router ports + +A: Run the TRex with following command and check incoming packet on router interfaces: + +sudo ./t-rex-64 -f cap2/dns.yaml --lm 1 --lo -l 1000 -d 100 + +Q: How to determine relation between Virtual OS ports and Hypervisor ports + +A: Compare the MACs address + name of interface, for example: + +* > ifconfig + +*eth0* Link encap:Ethernet *HWaddr 00:0c:29:2a:99:b2* + + ... + +* > sudo ./dpdk_setup_ports.py -s + +*03:00.0* 'VMXNET3 Ethernet Controller' *if=eth0* drv=vmxnet3 unused=igb_uio + +[NOTE] +===================================== +If at TRex side the NICs are not visible to ifconfig, run: + +.... +sudo ./dpdk_nic_bind.py -b <driver name> <1> <PCI address> <2> +.... + +<1> driver name - vmxnet3 for VMXNET3 and e1000 for E1000 +<2> 03:00.0 for example + +We are planning to add MACs to `./dpdk_setup_ports.py -s` +===================================== |