Traffic Generation and Error Injection

 

Traffic Setup

  • Traffic Flow: Select from Constant, Ramp, or Burst traffic flow - available selections depend on FC-1 or FC-2
    • Constant: Continuous traffic (no traffic shaping)
    • Burst: Two burst bandwidths are configured with variable burst time in seconds
    • Ramp: Start and stop bandwidths are configured along with the bandwidth step size and duration
  • Frame Size: Set the frame size in bytes.
    • Available in FC-2 mode only
    • Valid settings are 56 bytes to 2148 bytes.
    • The frame length includes the SOF and EOF overhead bytes.
  • Constant Bandwidth: Configure the transmit rate or bandwidth in %
    • Valid settings are 1% to 100% in 0.01% increments

 

FC-BERT/FC-Throughput Traffic Setup

 

Error Injection Setup

Error injection can be performed during a test. The type of errors and error injection rate or flow are configured in the Error Injection tab.

  • Error type: Select from Bit and CRC.
  • Injection Flow: Determines how the selected errors will be injected. The user can select a single error injection, a specific count, or error rate.
  • Count:When Count is selected, configure the error count via the numeric pop-up keypad.

 

FC-BERT/FC-Throughput Error Injection Setup

 

Once the test is running, error injection can be enabled by selecting the Error Injection icon from the action drop-down menu at the top of the screen. Press the Error Inject button to start injecting errors.

 

FC-1/2 Throughput - General

 

General tab (Throughput only)

  • RTD Measurement: Enable or Disable Round Trip Delay Measurement
  • SDT Measurement Trigger (>µs): Any inter-frame gap that is equivalent or greater than the configured threshold will trigger the SDT measurement. This is useful if a known threshold is expected from a given network under test. For example, if the known switchover time is 50ms, the trigger can be set to a value slightly below 50ms to assure that the SDT is measured.
  • SDT Violation Threshold (µs): Triggers an SDT Violation event in the event log. This is helpful for historical purposes during any given test. If the measured SDT is equivalent or greater than the configured threshold an SDT Violation event is counted.