Help us improve your experience.

Let us know what you think.

Do you have time for a two-minute survey?

Navigation
Guide That Contains This Content
[+] Expand All
[-] Collapse All

    Examining the Health of Network Devices by Viewing RFC 2544 Test Results

    RFC 2544 defines a series of tests that can be used to describe the performance characteristics of network interconnecting devices. RFC2544-based benchmarking tests methodology can be applied to a single device under test (DUT), or a network service (set of devices working together to provide end-to-end service). When applied to a service, the RFC2544 test results can characterize the Service-Level-Agreement (SLA) parameters.

    After you create an RFC 2544 test profile, which defines attributes, such as the period for the test and the type of test to be performed, for the RFC 2544-based benchmarking test, you must create an RFC test, which defines attributes of the test iteration, such as the address family (type of service, IPv4 or Ethernet), the logical interface, test duration, and test packet size, that are used for a benchmarking test to be run. The test name combined with the test profile represent a single real-time performance monitoring (RPM) configuration instance.. The test profile is referenced in the test interface to perform a specific type of benchmarking test and compute statistics to describe the performance characteristics of a network interconnecting device.

    You must start the test on the router that operates as the reflector before you start the test on router that functions as the initiator. You can configure the test mode for the packets that are sent during the benchmarking test. The initiate-and-terminate test mode causes the test frames to be initiated at the router and the reflected back frames to be terminated. This mode requires a reflector to be configured at the peer end of the network to return back the generated frames. The reflect test mode causes the received test frames to be reflected back on the configured service (for example, bridge, inet, ccc).

    After you configure the RFC 2544 test on the necessary devices, you can start the test on the initiator and reflector as appropriate. After the test is completed, you can view the results of the test to analyze and examine the performance characteristics of a network interconnecting device.

    You can view information about the results of each category or state of the RFC 2544-based benchmarking test, such as aborted tests, active tests, and completed tests, for each RPM instance.

    Viewing a Consolidated Summary of All RFC 2544 Tests

    You can display information about the results of each category or state of the RFC 2544-based benchmarking test, such as aborted tests, active tests, and completed tests, for each real-time performance monitoring (RPM) instance. You can view the results of each test state for all of the configured test IDs or for a specific test ID. Also, you can display statistics about the total number of tests of each state for a high-level, quick analysis. The values in the output displayed vary, depending on the state in which the test is passing through, when you issue the command.

    To view the test results for an RFC2544 test:

    1. From the View selector, select Device View.

      The workspaces that are applicable to this view are displayed.

    2. From the Junos Space user interface, click the Monitor icon on the Connectivity Services Director banner.

      The functionalities that you can configure in this mode are displayed in the task pane.

    3. From the View pane, click the plus sign (+) beside the My Network item in the View pane to expand the tree and select the device node you want for which you want to manage the RFC2544 test.

      The device type selected within the device model tree is highlighted.

    4. Click the RFC2544 Tests tab on the right pane. The RFC2544 Tests page is displayed.

      The following fields are displayed in a table at the top of the page:

      • Initiatior—Name of the device configured as the generator or initiator of frames for the test
      • Name—Name of the configured RFC 2544 test that contains the parameters of the test
      • Reflector—Name of the device configured as the reflector for the test
      • Test Status—Status of the RFC 2544-based test, such as whether the test is started or not, is in progress, or has been completed
      • Start/Stop—Commence or terminate a RFC 2544-based test

      Tip: Apart from viewing test results an RFC 2544-based test from Monitor mode of Device View for a particular device, you can also create, start, or stop an RFC 2544-based test from Monitor mode of Service View for a particular service configured on a device. To administer such tests for a service, select Service View from the View selector, click the Monitor icon on the Connectivity Services Director banner, and from the View pane, drill-down the Network Services > OAM > RFC2544 Tests tree and select an RFC 2544 test. The RFC2544 Tests tab is displayed on the right pane. The following fields are displayed on the page:

      • Name—Name of the configured RFC 2544 test that contains the parameters of the test
      • Initiator/Reflector—Name of the device configured as the initiator or reflector for the test
      • Test Status—Status of the RFC 2544-based test, such as whether the test is started or not, is in progress, or has been completed
      • Start/Stop—Commence or terminate a RFC 2544-based test
    5. From the list of tests in the table, select the check box beside the test for which you want to view results.

      The RFC2544 Tests page displays information in four panels or widgets:

      • Throughput (top left panel)
      • Latency (bottom left panel)
      • Frameloss (top right panel)
      • Back Back (bottom right panel)

      Each widget contains the Status field, which indicates whether the test is currently in progress or has been terminated.

      Click Refresh (rotating circle icon) at the top of the monitor to update and display the contents of the table. From the Time Interval drop-down box, select 1 Hour, 8 Hours, 1 Day, 1 Week, 1 Month, 3 Months, 6 Months, 1 Year, or Custom to specify the duration for which the data polled from devices needs to be displayed. If you select the Custom option, the Time range popup dialog box is displayed. Specify the date from the calendar, and select the Time From (Start time in the 24-hour time format of collection of data), and Time To (End time in the 24-hour time format of collection of data). Click OK to save the settings. Else, click Cancel to discard the configuration.

      Each of the four widgets includes three tabs. If you click on a tab, you can view detailed illustration of the test result for the corresponding test profile. If a parameter was not configured in the RFC2544 test profile, the corresponding panel displays the message, “Test case not configured for this profile.”


    Viewing the Throughput Test Results

    A throughput test performs the following:

    • Sends a specific number of frames at a specified rate from the initiator through the network service or a DUT. The test starts with a user-configured theoretical maximum rate.
    • Counts the number of transmitted frames and the number of received frames.
      • If the number of frames received is less than those transmitted, the test is repeated with a 50 percent reduced frame rate.
      • Throughput is the maximum rate at which the count of test frames received is equal to the number of test frames transmitted through the network service.

    You can repeat throughput tests for different frame sizes.

    The following illustration shows the information displayed by the Throughput Chart tab. A bar graph is displayed with the frame length, which signifies the packet size of the test frames in bytes, along the x axis and the throughput in Mbps along the y axis. Color-coded legends reference the frame or packet sizes (green). The valid packet sizes are 64, 68, 72, 128, 256, 512, 768, 1024, 1280, 1518, 1522, 1600, 1728, 2496, 3584, 4016, 9104, and 9136 bytes. Mouse over the different segments of the bar chart to highlight and view the throughput test results in a tool-tip.



    The following illustration shows the information displayed by the Throughput Test Result tab. The following fields are displayed in a table:

    Field

    Description

    Packet Size

    Size of the test packets in bytes.

    Iteration

    Number of the test iteration.

    Duration (sec)

    Period in seconds for which the test iteration is run

    Tx Packets

    Number of transmitted test packets.

    Rx Packets

    Number of received test packets.

    Tx Bytes

    Number of transmitted bytes.

    Rx Bytes

    Number of received bytes.

    PPS

    Total count of packets-per-second (pps) transmitted during the test.

    Bandwidth

    The theoretical limit of the media for the frame size configured for the test. This value is typically set to the bandwidth of the server being tested.

    Throughput %

    Percentage of throughput for the test iteration.



    The following illustration shows the information displayed by the Throughput Summary tab. The following fields are displayed in a table:

    Field Name

    Field Description

    Test-profile Configuration

    Details of the specified test profile

    Test-profile name

    Name of the configured test profile that contains the parameters for the test

    Test packet size

    Size of the test packets in bytes

    Theoretical max bandwidth

    Theoretical maximum bandwidth configured for the test. This value is typically set to the bandwidth of the server being tested. Valid values are 1,000 Kbps through 1,000,000 Kbps (1 Gbps). The value defined is the highest bandwidth value tested for this test.

    Test Configuration

    Details of the configured test ID.

    Test mode

    Mode configured for the test. Test modes are Initiate-and-Terminate and Reflect.

    Duration in seconds

    Period in seconds for which the test has been performed.

    Test finish wait duration in seconds

    Waiting period in seconds after which the test has been performed.

    Test family

    The underlying service on which the test is run. Test families are:

    • INET: Indicates that the test is run on a IPv4 service.
    • CCC: Indicates that the test is run on a circuit cross-connect (CCC) or pseudowire service.

    Routing Instance Name

    Name of the routing instance for the test

    Inet family Configuration

    Details of the configured inet family for an IPv4 service

    Egress Interface

    Name of the egress interface from which the test frames are sent

    Source ipv4 address

    Source IPv4 address used in the IP header of the generated test frame.

    Destination ipv4 address

    Destination IPv4 address used in the IP header of the generated test frame.

    Source udp port

    Source UDP port number used in the UDP header of the generated test frame.

    Destination udp port

    Destination UDP port number used in the UDP header of the generated test frame.

    Ccc family Configuration

    Details of the configured CCC family for an Ethernet service

    Source MAC address

    Source MAC address used in generated test frames for a CCC or Ethernet pseudowire service.

    Destination MAC address

    Destination MAC address used in generated test frames for a CCC or Ethernet pseudowire service.

    Ivlan-id

    Inner VLAN ID for test-frames

    Ovlan-id

    Outer VLAN ID for test-frames

    Direction egress

    Test is run in the egress direction of the interface (NNI)

    Direction ingress

    Test is run in the ingress direction of the interface (UNI)

    Rfc2544 throughput test informationDetails of the throughput test

    Initial test load percentage

    Percentage of the steady state load for the test.

    Test iteration mode

    Mode of the test iteration: Binary or step-down.

    Test iteration step percent

    The test step percentage for tests. If not specified, the default step-percent is 10 percent. This parameter is ignored for all type of tests other than frame-loss tests.

    Theoretical max bandwidth

    The theoretical limit of the media for the frame size configured for the test. This value is typically set to the bandwidth of the server being tested.

    Test packet size:

    Packet size of the test frames in bytes.

    Iteration

    Number of the test iteration.

    Duration (sec)

    Period in seconds for which the test iteration is run

    Elapsed time

    Amount of time that has passed, in seconds, since the start of the test.

    pps

    Total count of packets-per-second (pps) transmitted during the test.

    Tx Packets

    Number of transmitted test packets.

    Rx Packets

    Number of received test packets.

    Tx Bytes

    Number of transmitted bytes.

    Rx Bytes

    Number of received bytes.

    Percentage throughput

    Percentage of throughput for the test iteration.

    Result of the iteration runs (Throughput) :

    Results of the completed throughput test for a particular packet size.

    Best iteration

    Number of the iteration with the highest throughout, among the listed iterations.

    Best iteration (pps)

    Packets-per-second (pps) count of the iteration with the highest throughout, among the listed iterations.

    Best iteration throughput

    Percentage of throughput of the iteration with the highest throughout, among the listed iterations.

    RFC2544 Throughput test results summary

    Consolidated information of the throughput test.

    Packet Size

    Size of the test packet in bytes.

    Theoretical rate (pps)

    Theoretical frame rate in packets-per-second.

    Tx Packets

    Number of transmitted packets.

    Rx Packets

    Number of received packets.

    Offered throughput (percentage)

    The offered throughput in percentage of the chosen service (such as Layer 3 or Ethernet pseudowire).

    Measured bandwidth (kbps)

    Available bandwidth of the service based on the calculated throughput.



    Viewing the Latency Test Results

    A latency test performs the following:

    Note: To run latency test, you need to determine the throughput for DUT or a network service at each of the specified frame sizes.

    • Starts with a stream of frames at a particular frame size through the DUT at the determined throughput rate.
    • Sends an identifying tag in one frame after 60 seconds and calculate the latency when the frame with the same tag is received by the initiator.
    • Is repeated for at least 20 times with the reported latency value being the average of the recorded values.

    You can repeat latency tests for different frame sizes.

    The following illustration shows the information displayed by the Latency Chart tab. A line chart is displayed with the frame length, which signifies the packet size of the test frames in bytes, along the x axis and the latency in nanoseconds (ns) along the y axis. Color-coded legends reference the frame or packet sizes (brown). The valid packet sizes are 64, 68, 72, 128, 256, 512, 768, 1024, 1280, 1518, 1522, 1600, 1728, 2496, 3584, 4016, 9104, and 9136 bytes. Mouse over the different points in the line chart to highlight and view the latency test results in a tool-tip.



    The following illustration shows the information displayed by the Latency Test Result tab. The following fields are displayed for the different packet sizes:

    Field

    Description

    Packet Size

    Size of the test packets in bytes.

    Iteration

    Number of the test iteration.

    Duration (sec)

    Period in seconds for which the test iteration is run

    Tx Packets

    Number of transmitted test packets.

    Rx Packets

    Number of received test packets.

    Latency MIN

    Aggregated minimum latency in nanoseconds.

    Latency AVG

    Aggregated average latency in nanoseconds.

    Latency MAX

    Aggregated maximum latency in nanoseconds.

    Latency PROBE

    Aggregated probe latency in nanoseconds.

    PPS

    Total count of packets-per-second (pps) transmitted during the test.

    Bandwidth

    The theoretical limit of the media for the frame size configured for the test. This value is typically set to the bandwidth of the server being tested.



    The following illustration shows the information displayed by the Latency Summary tab. The following fields are displayed in a table:

    Field Name

    Field Description

    Test-profile Configuration

    Details of the specified test profile

    Test-profile name

    Name of the configured test profile that contains the parameters for the test

    Test packet size

    Size of the test packets in bytes

    Theoretical max bandwidth

    Theoretical maximum bandwidth configured for the test. This value is typically set to the bandwidth of the server being tested. Valid values are 1,000 Kbps through 1,000,000 Kbps (1 Gbps). The value defined is the highest bandwidth value tested for this test.

    Test Configuration

    Details of the configured test ID.

    Test mode

    Mode configured for the test. Test modes are Initiate-and-Terminate and Reflect.

    Duration in seconds

    Period in seconds for which the test has been performed.

    Test finish wait duration in seconds

    Waiting period in seconds after which the test has been performed.

    Test family

    The underlying service on which the test is run. Test families are:

    • INET: Indicates that the test is run on a IPv4 service.
    • CCC: Indicates that the test is run on a circuit cross-connect (CCC) or pseudowire service.

    Routing Instance Name

    Name of the routing instance for the test

    Inet family Configuration

    Details of the configured inet family for an IPv4 service

    Egress Interface

    Name of the egress interface from which the test frames are sent

    Source ipv4 address

    Source IPv4 address used in the IP header of the generated test frame.

    Destination ipv4 address

    Destination IPv4 address used in the IP header of the generated test frame.

    Source udp port

    Source UDP port number used in the UDP header of the generated test frame.

    Destination udp port

    Destination UDP port number used in the UDP header of the generated test frame.

    Ccc family Configuration

    Details of the configured CCC family for an Ethernet service

    Source MAC address

    Source MAC address used in generated test frames for a CCC or Ethernet pseudowire service.

    Destination MAC address

    Destination MAC address used in generated test frames for a CCC or Ethernet pseudowire service.

    Ivlan-id

    Inner VLAN ID for test-frames

    Ovlan-id

    Outer VLAN ID for test-frames

    Direction egress

    Test is run in the egress direction of the interface (NNI)

    Direction ingress

    Test is run in the ingress direction of the interface (UNI)

    Rfc2544 latency test information : Details of the latency test

    Theoretical max bandwidth

    Theoretical maximum bandwidth configured for the test. This value is typically set to the bandwidth of the server being tested. Valid values are 1,000 Kbps through 1,000,000 Kbps (1 Gbps). The value defined is the highest bandwidth value used for this test.

    Initial test load percentage

    Percentage of the steady state load for the test.

    Duration in seconds

    Period in seconds for which the test has been performed.

    Test packet size

    Size of the test packet in bytes.

    Iteration

    Number of the test iteration.

    Duration (sec)

    Period in seconds for which the test iteration is run.

    Elapsed time

    Amount of time that has passed, in seconds, since the start of the test.

    pps

    Total count of packets-per-second (pps) transmitted during the test.

    Tx Packets

    Number of transmitted test packets.

    Rx Packets

    Number of received test packets.

    Latency

    Displays the latency parameters.

    Min(ns)

    Aggregated minimum latency in nanoseconds.

    Avg(ns)

    Aggregated average latency in nanoseconds.

    Max(ns)

    Aggregated maximum latency in nanoseconds.

    Probe(ns)

    Aggregated probe latency in nanoseconds.

    Result of the iteration runs (Latency)

    Results of the latency test completed for a particular packet size.

    Avg (min) Latency

    Average of the minimum latency in nanoseconds.

    Avg (avg) latency

    Average of the average latency in nanoseconds.

    Avg (Max) latency

    Average of the maximum latency in nanoseconds.

    Avg (probe) latency

    Average of the probe latency in nanoseconds.

    RFC2544 Latency test results summary:

    Consolidated statistics of the latency test.

    Packet Size

    Size of the test packet in bytes.

    Theoretical rate (pps)

    Theoretical frame rate in packets-per-second.

    Tx Packets

    Number of transmitted packets.

    Rx Packets

    Number of received packets.

    Latency

    Displays the latency parameters.

    Min(ns)

    Aggregated minimum latency in nanoseconds.

    Avg(ns)

    Aggregated average latency in nanoseconds.

    Max(ns)

    Aggregated maximum latency in nanoseconds.

    Probe(ns)

    Aggregated probe latency in nanoseconds.


    Viewing the Frame Loss Test Results

    A frame loss test performs the following:

    • Involves sending a specific number of frames at a specified rate through the DUT or a network service to be tested and counting the frames that are transmitted.
    • Calculates frame loss rate at each point using the equation:
      ( ( input_count - output_count ) x 100 ) / input_count.
    • Runs a trial for the frame rate that corresponds to 100 percent of the configured maximum theoretical rate.
    • Is repeated for the frame rate that corresponds to 90 percent of the maximum rate used and then for 80 percent of the maximum rate until a certain trial result shows no lost frames.

    You repeat the frame loss rate tests for different frame sizes.

    The following illustration shows the information displayed by the Frameloss Chart tab. A bar graph is displayed with the frame length, which signifies the packet size of the test frames in bytes, along the x axis and the frame loss in percentage along the y axis. Color-coded legends reference the frame or packet sizes (green). The valid packet sizes are 64, 68, 72, 128, 256, 512, 768, 1024, 1280, 1518, 1522, 1600, 1728, 2496, 3584, 4016, 9104, and 9136 bytes. Mouse over the different segments of the bar chart to highlight and view the frame-loss test results in a tool-tip.



    The following illustration shows the information displayed by the Frameloss Test Result tab. The following fields are displayed in a table:

    Field

    Description

    Packet Size

    Size of the test packets in bytes.

    Iteration

    Number of the test iteration.

    Duration (sec)

    Period in seconds for which the test iteration is run

    Tx Packets

    Number of transmitted test packets.

    Rx Packets

    Number of received test packets.

    Tx Bytes

    Number of transmitted bytes.

    Rx Bytes

    Number of received bytes.

    PPS

    Total count of packets-per-second (pps) transmitted during the test.

    Bandwidth

    The theoretical limit of the media for the frame size configured for the test. This value is typically set to the bandwidth of the server being tested.

    Throughput

    Percentage of throughput for the test iteration.

    Frame-loss rate %

    Percentage of frames that must been forwarded by the router under steady state (constant) load, but were not forwarded due to lack of resources.


    The following illustration shows the information displayed by the Frameloss Summary tab. The following fields are displayed in a table:

    Field Name

    Field Description

    Test-profile Configuration

    Details of the specified test profile

    Test-profile name

    Name of the configured test profile that contains the parameters for the test

    Test packet size

    Size of the test packets in bytes

    Theoretical max bandwidth

    Theoretical maximum bandwidth configured for the test. This value is typically set to the bandwidth of the server being tested. Valid values are 1,000 Kbps through 1,000,000 Kbps (1 Gbps). The value defined is the highest bandwidth value tested for this test.

    Test Configuration

    Details of the configured test ID.

    Test mode

    Mode configured for the test. Test modes are Initiate-and-Terminate and Reflect.

    Duration in seconds

    Period in seconds for which the test has been performed.

    Test finish wait duration in seconds

    Waiting period in seconds after which the test has been performed.

    Test family

    The underlying service on which the test is run. Test families are:

    • INET: Indicates that the test is run on a IPv4 service.
    • CCC: Indicates that the test is run on a circuit cross-connect (CCC) or pseudowire service.

    Routing Instance Name

    Name of the routing instance for the test

    Inet family Configuration

    Details of the configured inet family for an IPv4 service

    Egress Interface

    Name of the egress interface from which the test frames are sent

    Source ipv4 address

    Source IPv4 address used in the IP header of the generated test frame.

    Destination ipv4 address

    Destination IPv4 address used in the IP header of the generated test frame.

    Source udp port

    Source UDP port number used in the UDP header of the generated test frame.

    Destination udp port

    Destination UDP port number used in the UDP header of the generated test frame.

    Ccc family Configuration

    Details of the configured CCC family for an Ethernet service

    Source MAC address

    Source MAC address used in generated test frames for a CCC or Ethernet pseudowire service.

    Destination MAC address

    Destination MAC address used in generated test frames for a CCC or Ethernet pseudowire service.

    Ivlan-id

    Inner VLAN ID for test-frames

    Ovlan-id

    Outer VLAN ID for test-frames

    Direction egress

    Test is run in the egress direction of the interface (NNI)

    Direction ingress

    Test is run in the ingress direction of the interface (UNI)

    Rfc2544 frame-loss test information : Details of the frame-loss test.

    Initial burst length:

    Length of the first burst when test frames are sent, as a measure of number of seconds at the rate of Kbps.

    Test iteration mode :

    Mode of the test iteration: Binary or step-down.

    Test iteration step percent

    The test step percentage for tests. If not specified, the default step-percent is 10 percent. This parameter is ignored for all type of tests other than frame-loss tests.

    Theoretical max bandwidth

    The theoretical limit of the media for the frame size configured for the test. This value is typically set to the bandwidth of the server being tested.

    Test packet size

    Size of the test packets in bytes.

    Iteration

    Number of the test iteration.

    Duration (sec)

    Period, in seconds, for which the test iteration is run.

    Offered throughput (percentage)

    The offered throughput in percentage of the chosen service (such as Layer 3 or Ethernet pseudowire)

    Elapsed time

    Amount of time that has passed, in seconds, since the start of the test.

    pps

    Theoretical frame rate in packets-per-second.

    Tx Packets

    Number of transmitted test packets.

    Rx Packets

    Number of received test packets.

    Tx Bytes

    Number of transmitted bytes.

    Rx Bytes

    Number of received bytes.

    Frame-loss rate %

    Percentage of frames that must been forwarded by the router under steady state (constant) load, but were not forwarded due to lack of resources.

    Result of the iteration runs :

    Results of the frame-loss test completed for a certain packet size.

    Frame-loss rate (percent) :

    Percentage of dropped frames for the specified packet size

    RFC2544 Frame-loss test results summary

    Consolidated statistics of the frame-loss test

    Packet Size

    Size of the test packet in bytes.

    Theoretical rate (pps)

    Theoretical frame rate in packets-per-second.

    Percentage throughput

    Percentage of throughput for the test iteration.

    Tx Packets

    Number of transmitted packets.

    Rx Packets

    Number of received packets.

    Frame Loss rate percent

    Percentage of dropped frames for the specified packet size


    Viewing the Back-to-Back Frames Test Results

    A back-to-back frames test or a bursty frames test performs the following operations:

    • Involves sending a burst of frames with minimum interframe gaps through the DUT or a network service and counting the number of frames forwarded.
    • Is rerun with an increased length of burst frames if the count of transmitted frames is equal to the number of frames forwarded.
    • Is rerun with a reduced length of burst frames if the count of forwarded frames is less than the number of frames transmitted.

    The back-to-back value is the number of frames in the longest burst that the DUT or a network service can handle without the loss of any frames.

    You can repeat back-to-back frame tests for different frame sizes.

    The following illustration shows the information displayed by the Back Back Frames Chart tab. A bar graph is displayed with the frame length, which signifies the packet size of the test frames in bytes, along the x axis and the burst length, which signifies the length of the first burst when test frames are sent as a measure of number of seconds at the rate of Kbps, along the y axis. Color-coded legends reference the frame or packet sizes (green). The valid packet sizes are 64, 68, 72, 128, 256, 512, 768, 1024, 1280, 1518, 1522, 1600, 1728, 2496, 3584, 4016, 9104, and 9136 bytes. Mouse over the different segments of the bar chart to highlight and view the bursty frames test results in a tool-tip.



    The following illustration shows the information displayed by the Back Back Frames Test Result tab. The following fields are displayed in a table:

    Field

    Description

    Packet Size

    Size of the test packets in bytes.

    Iteration

    Number of the test iteration.

    Duration (sec)

    Period in seconds for which the test iteration is run

    Tx Packets

    Number of transmitted test packets.

    Rx Packets

    Number of received test packets.

    Tx Bytes

    Number of transmitted bytes.

    Rx Bytes

    Number of received bytes.

    PPS

    Total count of packets-per-second (pps) transmitted during the test.

    Bandwidth

    The theoretical limit of the media for the frame size configured for the test. This value is typically set to the bandwidth of the server being tested.

    Burst %

    Percentage of of frames that are forwarded by the device on which the test is performed when a burst of frames with minimum inter-frame gaps is sent to that device from another source device.



    The following illustration shows the information displayed by the Back Back Frames Summary tab. The following fields are displayed in a table:


    Field Name

    Field Description

    Test-profile Configuration

    Details of the specified test profile

    Test-profile name

    Name of the configured test profile that contains the parameters for the test

    Test packet size

    Size of the test packets in bytes

    Theoretical max bandwidth

    Theoretical maximum bandwidth configured for the test. This value is typically set to the bandwidth of the server being tested. Valid values are 1,000 Kbps through 1,000,000 Kbps (1 Gbps). The value defined is the highest bandwidth value tested for this test.

    Test Configuration

    Details of the configured test ID.

    Test mode

    Mode configured for the test. Test modes are Initiate-and-Terminate and Reflect.

    Duration in seconds

    Period in seconds for which the test has been performed.

    Test finish wait duration in seconds

    Waiting period in seconds after which the test has been performed.

    Test family

    The underlying service on which the test is run. Test families are:

    • INET: Indicates that the test is run on a IPv4 service.
    • CCC: Indicates that the test is run on a circuit cross-connect (CCC) or pseudowire service.

    Routing Instance Name

    Name of the routing instance for the test

    Inet family Configuration

    Details of the configured inet family for an IPv4 service

    Egress Interface

    Name of the egress interface from which the test frames are sent

    Source ipv4 address

    Source IPv4 address used in the IP header of the generated test frame.

    Destination ipv4 address

    Destination IPv4 address used in the IP header of the generated test frame.

    Source udp port

    Source UDP port number used in the UDP header of the generated test frame.

    Destination udp port

    Destination UDP port number used in the UDP header of the generated test frame.

    Ccc family Configuration

    Details of the configured CCC family for an Ethernet service

    Source MAC address

    Source MAC address used in generated test frames for a CCC or Ethernet pseudowire service.

    Destination MAC address

    Destination MAC address used in generated test frames for a CCC or Ethernet pseudowire service.

    Ivlan-id

    Inner VLAN ID for test-frames

    Ovlan-id

    Outer VLAN ID for test-frames

    Direction egress

    Test is run in the egress direction of the interface (NNI)

    Direction ingress

    Test is run in the ingress direction of the interface (UNI)

    Rfc2544 Back-Back test information : Details of the back-to-back frames or bursty frames test.

    Initial burst length:

    Length of the first burst when test frames are sent, as a measure of number of seconds at the rate of Kbps.

    Test iteration mode :

    Mode of the test iteration: Binary or step-down.

    Test iteration step percent

    The test step percentage for tests. If not specified, the default step-percent is 10 percent. This parameter is ignored for all type of tests other than frame-loss tests.

    Theoretical max bandwidth

    The theoretical limit of the media for the frame size configured for the test. This value is typically set to the bandwidth of the server being tested.

    Test packet size:

    Packet size of the test frames in bytes.

    Iteration

    Number of the test iteration.

    Burst Length (Packets)

    Number of packets in the burst.

    Elapsed time

    Amount of time that has passed, in seconds, since the start of the test.

    Tx Packets

    Number of transmitted test packets.

    Rx Packets

    Number of received test packets.

    Tx Bytes

    Number of transmitted bytes.

    Rx Bytes

    Number of received bytes.

    Result of the iteration runs :

    Results of the back-to-back frames test completed for a certain packet size.

    Best iteration :

    Number of the iteration with the longest burst.

    Measured burst (num sec)

    Time in seconds of the burst of the iteration with the longest burst.

    Measured burst (num pkts)

    Number of packets during the burst of the iteration with the longest burst.

    RFC2544 Back-Back test results summary:

    Consolidated statistics of the back-to-back frames test.

    Packet Size

    Size of the test packets in bytes.

    Measure Burst length (Packets)

    Computed burst length in terms of number of packets.


    Modified: 2016-03-14