X-Git-Url: https://gerrit.opnfv.org/gerrit/gitweb?a=blobdiff_plain;f=docs%2Ftesting%2Fuser%2Fuserguide%2Fadvanced.rst;h=5307bd03f06dc1098bfe05472271498fd5b034ef;hb=057486b092e0a4bb1989121588eb5f8afdb8e1d3;hp=02c7fce98f3cbf1f7a53c74224471d88c933d44b;hpb=6226413ca6e1b4c3a52a3deeb66f8f487c2704ae;p=nfvbench.git diff --git a/docs/testing/user/userguide/advanced.rst b/docs/testing/user/userguide/advanced.rst index 02c7fce..5307bd0 100644 --- a/docs/testing/user/userguide/advanced.rst +++ b/docs/testing/user/userguide/advanced.rst @@ -78,6 +78,22 @@ Used parameters: * ``--no-traffic`` or ``-0`` : sending traffic from traffic generator is skipped +TRex force restart +------------------------------------ + +NFVbench allows to restart TRex traffic generator between runs. +It runs the whole test, but restart TRex instance before generating new traffic. + +To force restart, use the --restart option: + +.. code-block:: bash + + nfvbench --restart + +Used parameters: + +* ``--restart`` : restart traffic generator (TRex) + Fixed Rate Run -------------- @@ -204,43 +220,6 @@ If ``-sc PVVP`` is specified instead, there would be 6 VMs in 3 chains as this s Both **single run** or **NDR/PDR** can be run as multichain. Running multichain is a scenario closer to a real life situation than runs with a single chain. -External Chain --------------- - -NFVbench can measure the performance of 1 or more L3 service chains that are setup externally. Instead of being setup by NFVbench, -the complete environment (VMs and networks) has to be setup prior to running NFVbench. - -Each external chain is made of 1 or more VNFs and has exactly 2 end network interfaces (left and right network interfaces) that are connected to 2 neutron networks (left and right networks). -The internal composition of a multi-VNF service chain can be arbitrary (usually linear) as far as NFVbench is concerned, -the only requirement is that the service chain can route L3 packets properly between the left and right networks. - -To run NFVbench on such external service chains: - -- explicitly tell NFVbench to use external service chain by adding ``-sc EXT`` or ``--service-chain EXT`` to NFVbench CLI options -- specify the number of external chains using the ``-scc`` option (defaults to 1 chain) -- specify the 2 end point networks of your environment in ``external_networks`` inside the config file. - - The two networks specified there have to exist in Neutron and will be used as the end point networks by NFVbench ('napa' and 'marin' in the diagram below) -- specify the router gateway IPs for the external service chains (1.1.0.2 and 2.2.0.2) -- specify the traffic generator gateway IPs for the external service chains (1.1.0.102 and 2.2.0.102 in diagram below) -- specify the packet source and destination IPs for the virtual devices that are simulated (10.0.0.0/8 and 20.0.0.0/8) - - -.. image:: images/extchain-config.png - -L3 routing must be enabled in the VNF and configured to: - -- reply to ARP requests to its public IP addresses on both left and right networks -- route packets from each set of remote devices toward the appropriate dest gateway IP in the traffic generator using 2 static routes (as illustrated in the diagram) - -Upon start, NFVbench will: -- first retrieve the properties of the left and right networks using Neutron APIs, -- extract the underlying network ID (typically VLAN segmentation ID), -- generate packets with the proper VLAN ID and measure traffic. - -Note that in the case of multiple chains, all chains end interfaces must be connected to the same two left and right networks. -The traffic will be load balanced across the corresponding gateway IP of these external service chains. - - Multiflow --------- @@ -284,6 +263,24 @@ These can also be written in CIDR notation to represent the subnet. The corresponding ``step`` is used for ranging the IP addresses from the `ip_addrs``, ``tg_gateway_ip_addrs`` and ``gateway_ip_addrs`` base addresses. 0.0.0.1 is the default step for all IP ranges. In ``ip_addrs``, 'random' can be configured which tells NFVBench to generate random src/dst IP pairs in the traffic stream. +UDP ports can be controlled with the following NFVbench configuration options: + +.. code-block:: bash + + udp_src_port: ['1024', '65000'] + udp_dst_port: 53 + udp_port_step: 1 + +``udp_src_port`` and ``udp_dst_port`` are the UDP port value used by the traffic generators. +These can be written for unique port or range ports for all flow. + +The corresponding ``udp_port_step`` is used for ranging the UDP port. +1 is the default step for all UDP ranges, 'random' can be configured which tells NFVBench to generate random src/dst UDP pairs in the traffic stream. + +NB: + Use of UDP range will increase possible values of flows (based on ip src/dst and port src/dst tuple). + NFVBench will calculate the least common multiple for this tuple to adapt flows generation to ``flow_count`` parameter. + Traffic Configuration via CLI ----------------------------- @@ -313,6 +310,7 @@ MAC Addresses NFVbench will dicover the MAC addresses to use for generated frames using: - either OpenStack discovery (find the MAC of an existing VM) in the case of PVP and PVVP service chains - or using dynamic ARP discovery (find MAC from IP) in the case of external chains. +- In case of L3 chain with SDN-GW or router between traffic generator and loop VM ARP is needed to discover SDN-GW mac addresses, use ``--loop-vm-arp`` flag or ``loop_vm_arp: true`` in config file. Status and Cleanup of NFVbench Resources ---------------------------------------- @@ -371,3 +369,79 @@ Example of run: # The --force-cleanup option will do the same but without prompting for confirmation. + +Service mode for TRex +--------------------- + +The ``--service-mode`` option allows you to capture traffic on a TRex window during the NFVBench test. Thus, you will be +able to capture packets generated by TRex to observe many information on it. + +Example of use : + +.. code-block:: bash + + nfvbench ``--service-mode`` + +.. note:: It is preferable to define the minimum rate (2002 pps) to have a better capture + +In another bash window, you should connect to the TRex console doing : + +.. code-block:: bash + + cd /opt/trex/vX.XX/ #use completion here to find your corresponding TRex version + ./trex-console -r + capture start monitor --rx [port number] -v + +Start this capture once you have started the NFVBench test, and you will observe packets on the TRex console : + +.. code-block:: bash + + #26342 Port: 0 ◀── RX + + trex(read-only)> + + Type: UDP, Size: 66 B, TS: 26.30 [sec] + + trex(read-only)> + ###[ Ethernet ]### + dst = a0:36:9f:7a:58:8e + src = fa:16:3e:57:8f:df + type = 0x8100 + ###[ 802.1Q ]### + prio = 0 + id = 0 + vlan = 1093 + type = 0x800 + ###[ IP ]### + version = 4 + ihl = 5 + tos = 0x1 + len = 46 + id = 65535 + flags = + frag = 0 + ttl = 63 + proto = udp + chksum = 0x8425 + src = 120.0.0.0 + dst = 110.0.17.153 + \options \ + ###[ UDP ]### + sport = 53 + dport = 53 + len = 26 + chksum = 0xfd83 + ###[ Raw ]### + load = "xx\xab'\x01\x00?s\x00\x00\xbci\xf0_{U~\x00" + ###[ Padding ]### + load = '6\x85' + +Check on the NFVBench window that the following log appears just before the testing phase : + +.. code-block:: bash + + 2019-10-21 09:38:51,532 INFO Starting to generate traffic... + 2019-10-21 09:38:51,532 INFO Running traffic generator + 2019-10-21 09:38:51,541 INFO ``Service mode is enabled`` + 2019-10-21 09:38:52,552 INFO TX: 2004; RX: 2003; Est. Dropped: 1; Est. Drop rate: 0.0499% + 2019-10-21 09:38:53,559 INFO TX: 4013; RX: 4011; Est. Dropped: 2; Est. Drop rate: 0.0498% \ No newline at end of file