anchor.diff:  ==== TRex traffic does not show up on Wireshark, so I can not capture the traffic from the TRex port
   TRex uses DPDK which takes ownership of the ports, so using Wireshark is not possible. You can use switch with port mirroring to capture the traffic.
   
  -==== How can I map betwean TRex port-id (e.g. port 0) and physical router interface?
  -Load TRex in stateless mode, run traffic from each port, and look at the counters on the router interfaces.
  -
  -
   ===  Stateful 
   
   ==== How do I start using the stateful mode?
   You should first have a YAML configuration file. See link:trex_manual.html#_traffic_yaml_parameter_of_f_option[here].
   Then, you can find some basic examples link:trex_manual.html#_trex_command_line[here].
   
  -==== TRex is connected to a switch and we observe many dropped packets at TRex startup.
  -A switch might be configured with spanning tree enabled. TRex initializes the port at startup, making the spanning tree drop the packets. 
  +==== TRex is connected to a switch and I observe many dropped packets at TRex startup.
  +A switch might be configured with spanning tree enabled. TRex reset the port at startup, making the switch reset it side as well,
  +and spanning tree can drop the packets until it stabilizes.
   Disabling spanning tree can help. On Cisco nexus, you can do that using `spanning-tree port type edge`
  -This issue would be fixed when we consolidate ``Stateful'' and ``Stateless'' RPC.
  +You can also start Cisco with -k <num> flag. This will send packets for k seconds before starting the actual test, letting the spanning
  +tree time to stabilize.
  +This issue will be fixed when we consolidate ``Stateful'' and ``Stateless'' RPC.
   
   ==== I can not see RX packets
   TRex does not support ARP yet, you should configure the DUT to send the packets to the TRex port MAC address. From Stateless mode, you can change the port mode to promiscuous. +
  
positive.code: 2. To run the real product, check link:trex_manual.html#_download_and_installation[here] for hardware recommendation and
  installation instructions.
  
  ==== During OS installation, screen is skewed / error "out of range" / resolution not supported etc
  
          * Fedora - during installation, choose "Troubleshooting" -> Install in basic graphic mode
          * Ubuntu - try Ubuntu server, which has textual installation
  
  ==== How to determine relation between TRex ports and device under test ports
  
  Run the TRex with following command and check incoming packet on router interfaces:
  
  [source,bash]
  ----
          sudo ./t-rex-64 -f cap2/dns.yaml --lm 1 --lo -l 1000 -d 100
  ----
  
  ==== How to determine relation between Virtual OS ports and Hypervisor ports
  
  Compare the MACs address + name of interface, for example:
  
  [source,bash]
  ----
  * > 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]
  
negative.code:                             flow_stats = STLFlowLatencyStats(pg_id = 12+port_id))
  --------
  <1> non latency stream will be amplified 
  <2> latency stream, the speed will be constant 1KPPS
  
  
  ===== Latency stream has constant rate of 1PPS, and is not getting amplified by multiplier. Why?
  