L4S FrameBlasting Flow

{
   "type":  "l4s_frame_blasting",
   "name":  "<flow_name:str>",
   "source": {
         "port_group": [
            "<source_group:str>"
         ]
   },
   "destination": {
         "port_group": [
            "<destination_group:str>"
         ]
   },
   "l4s_ecn": "<l4s_ecn_marking_type:str>",
   "dscp": "<dscp_code_point:str|int>",
   "add_reverse_direction": "<add_reverse_direction_flow:bool>",
   "initial_time_to_wait": "<initial_time_to_wait:float|int|timedelta>",
   "bitrate": "<flow_bitrate:float>",
   "frame_size": "<frame_size_without_crc:int>",
   "frame_rate": "<frame_rate:float>",
   "number_of_frames": "<number_of_frames:float>",
   "duration": "<flow_duration:float|int|timedelta>",
   "udp_src": "<udp_source_port:int>",
   "udp_dest": "<udp_destination_port:int>",
   "nat_keep_alive": "<activate_nat_keep_alive:bool>",
   "analysis": {
      "latency":"<enable_latency_analysis:bool>",
      "max_threshold_latency": "<max_threshold_latency:float>",
      "max_loss_percentage": "<max_loss_percentage:float>",
      "quantile": "<quantile:float>",
      "min_percentile": "<min_percentile:float>",
      "max_percentile": "<max_percentile:float>"
   }
}

L4S frame blasting flow

Specific parameters for L4S frame blasting flow. The type MUST be defined as l4s_frame_blasting.

Note

Not supported by ByteBlower Endpoint.

type

object

properties

  • type

l4s_frame_blasting

  • name

Name of this Flow, defaults to auto-generated name when set to none

type

string

  • source

Specifying the source of transmitted data for this flow

type

object

properties

  • port_group

List of port groups specifying the transmitting ports

type

array

items

Port group

additionalProperties

False

  • destination

Specifying the destination for receiving data for this flow

type

object

properties

  • port_group

List of port groups specifying the receiving ports

type

array

items

Port group

additionalProperties

False

  • l4s_ecn

IP ECN

Explicit Congestion Notification code point, defaults to DEFAULT_IP_ECN (0x00)

oneOf

type

number

type

string

  • dscp

IP DSCP

Differentiated Services Code Point, defaults to DEFAULT_IP_DSCP (0x00)

oneOf

type

number

type

string

  • add_reverse_direction

Enables adding a flow in the reverse direction of the original flow with the same configuration, defaults to false

type

string

  • initial_time_to_wait

Initial time to wait to start the flow in seconds, defaults to 0 (start immediately).

type

number

  • bitrate

Rate at which the bits are transmitted in bits/s. Excludes the VLAN tag bytes (when applicable), mutual exclusive with frame_rate, defaults to none

type

string

  • frame_size

Frame size in Bytes without CRC, defaults to none

type

number

  • frame_rate

Rate at which the frames are transmitted (in frames per second), mutual exclusive with bitrate, defaults to DEFAULT_FRAME_RATE (100) when bitrate is not provided.

type

number

  • number_of_frames

Number of frames to transmit, defaults to DEFAULT_NUMBER_OF_FRAMES (none == defined by scenario maximum run time).

type

string

  • duration

Duration of the flow in seconds, defaults to none (use number_of_frames instead)

type

string

  • udp_src

UDP port number in range [49152,65534] , defaults to udp_dynamic_port

type

number

  • udp_dest

UDP port number in range [49152,65534] , defaults to udp_dynamic_port

type

number

  • nat_keep_alive

Enable a flow to keep Network Address (and Port) Translation (NAT/NAPT) entries alive. The direction will be from the endpoint behind a NAT/NAPT gateway to the port at the public side of the NAT/NAPT gateway, defaults to false.

We always enable the NAT/NAPT keep alive when the user asks for it, even when:

  • the reverse flow is enabled and source and destination UDP ports are the same

  • the source is the endpoint behind the NAT/NAPT gateway: An initial time to wait on the flow can still cause the NAPT entries at the gateway might still timeout before the traffic starts. This might cause the NAPT gateway to create a new (and maybe different!) NAPT entry, causing our traffic analysis to fail (with 100% loss).

type

boolean

  • napt_keep_alive

Deprecated since version v1.1.0: Use nat_keep_alive instead. Will be removed in v1.3.0.

type

boolean

  • analysis

Sets latency related analysis configuration parameters

oneOf

Frame loss analysis parameters

Latency & frame loss analysis parameters