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

    Creating an RFC 2544-Based Benchmarking Test

    You can configure a benchmarking test to detect and measure performance attributes, such as throughput, latency, frame loss, and bursty or back-to-back frames, of network devices. RFC 2544-based benchmarking test is performed by transmitting test packets from a device that functions as the generator or the initiator. These packets are sent to a device that functions as the reflector, which receives and returns the packets back to the initiator.

    The test name that you configure contains details, such as the address family and the test mode, for the test. You can associate the same test profile with multiple test names. You can define the attributes for the RFC 2544-based benchmarking test to examine and analyze the performance characteristics of a network interconnecting device.

    The test configuration is applied only when you start the test. If you update the test configuration during the test, you have to start the test again for the updated configuration to take effect.

    You must configure a test profile and reference the test profile in a unique test name that defines the parameters for the test to be performed on a certain device. However, the test profile is required when the test mode is configured as initiation and termination. The test-profile parameter is disregarded when the test mode is configured as reflection.

    Creating an RFC 2544-Based Benchmarking Test

    To begin to create an RFC2544 test:

    Tip: Apart from creating an RFC 2544-based test from Build 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 to select a service name. The RFC Tests tab is displayed on the right pane. In the table of listed RFC 2544 tests, you can click the Start or Stop buttons to commence ot terminate a 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 Deploy 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. From the Tasks pane, select the OAM functionality that you want to configure. To manage an RFC2544 test for a device, select OAM > RFC2544 Test.

      The Manage RFC 2544 Tests page is displayed.

    5. Click the New icon at the top of the page to start the wizard to create a new RFC 2544 test.

      The Create RFC 2544 Test page is displayed.

    Configuring the General Settings of an RFC 2544 Test

    A wizard is available to create and modify a service order in an intuitive and easily-navigable format. The settings that you can configure in the service order are organized in separate pages of the wizard, which you can launch by clicking the appropriate buttons at the top of the Create or Edit an RFC 2544 Test page. Alternatively, you can proceed to the corresponding setting-related pages by clicking the Back and Next buttons at any point in the wizard during the creation of the service order.

    To continue to create an RFC 2544 test, from the General Settings window:

    1. In the Create RFC2544 Test window, enter information in the fields of the General Settings panel.

      Field

      Description

      Name

      Define the name of the RFC 2544-based benchmarking test. For each unique test name that you configure, you can specify a test profile, which contains the settings for a test and its type, and also a test interface, which contains the settings for test packets that are sent and received on the selected interface.

      The name can be up to 32 characters in length.

      Comments

      A meaningful, easily-identifiable description of the RFC 2544-based test.

      The comments can be up to 255 characters in length.

      RFC Test Profile

      Specify the name of the test profile to be associated with a particular test name. You must have previously configured the profile using the test-profile profile1 statement at the [edit services rpm rfc2544-benchmarking] hierarchy level using the Junos OS CLI or from the Manage OAM Profiles page in Build mode of Device View of the Connectivity Services Director GUI.

      Click View to open a pop-up dialog box to view all the previously configured RFC 2544-based test profiles and select a profile to associate with the test.

      If you have not previously configured an RFC 2544-based test profile, click Create to open the Create RFC Test Profile wizard and configure the test profile.

      The test profile is required when the test mode is configured as initiation and termination.

      The test-profile parameter is disregarded when the test mode is configured as reflection. A reflection service does not use the parameters specified in the test profile because the reflection service uses the same parameters for the test frames as the received test frames when it returns the frames to the initiator.

    2. Configuring the Initiator Device

      To configure the Initiator device to support operation of the RFC2544 test:

      1. Click on Initiator in the left panel and enter information in the fields in the Initiator panel.

        Note: The appearance of the Initiator window depends on the value you specify for the Family parameter. The following illustration shows the window that appears when you specify ccc. The subsequent illustration shows the window that appears when you specify inet.




        Field

        Description

        PE Device

        Select the name of the device on which the initiator interface is located.

        Click Select beside the field to open the Choose Endpoints dialog box. From the Choose Endpoints dialog box that appears, select the devices that you want to participate in the RFC 2544 test. Use the multiple selection feature to select one or more devices. The lower part of the dialog box refreshes to display the interfaces associated with the selected device. Select the check boxes next to the interfaces you want to associate with the RFC 2544-based benchmarking test.

        UNI Interface

        Specify the logical interface on which the RFC 2544-based benchmarking test is run on the initiator device. This is a local user-to-network interface (UNI) on behalf of which the test frames are generated when the test direction is egress.

        Family

        Specify the address type family for the benchmarking test:

        • inet—Indicates that the test is run on an IPv4 service.

          Note: Family inet is not supported on ACX5048 and ACX5096 routers.

        • ccc—Indicates that the test is run on a circuit cross-connect (CCC) or Ethernet pseudowire service. The direction option specifies the direction (ingress or egress) to be used for the test.

        Source IPV4 Address

        Specify the source IPv4 address to be used in generated test frames. This parameter is optional for both circuit cross-connect (CCC) and, inet , and also for bridge family. If you do not configure the source IPv4 address for an inet family, the source address of the interface is used to transmit the test frames.

        Source MAC Address

        Specify the MAC address of the device from which test data originates. This parameter is effective for a circuit cross-connect (CCC) family and it is not applicable for an inet family. If you specify this parameter for an inet family, a commit error occurs when you commit the configuration. This parameter is optional for a CCC family.

        Specify the MAC address as six hexadecimal bytes in one of the following formats: nnnn.nnnn.nnnn or nn:nn:nn:nn:nn:nn; for example, 0011.2233.4455 or 00:11:22:33:44:55.

        If you do not configure the destination MAC address, the default value of 0x00:0x60:0x67:0x71:0xC6:0x62 is used.

        Source UDP Port

        Specify the UDP port of the source to be used in the UDP header for the generated frames. If you do not specify the UDP port, the default value of 4040 is used.

        Range: 1 through 65535

        Default: 4040

        Destination IPV4 Address

        Specify the destination IPv4 address to be used in generated test frames. This is optional for the family bridge. You must configure this option if you specify inet as the family. This option is not required if you specify circuit cross-connect (CCC).

        If you do not configure the destination IPv4 address, the default value of 192.168.1.20 is used.

        Destination MAC Address

        Specify the destination MAC address used in generated test frames. This parameter is not applicable for an inet family and is considered only for a CCC family. If you specify this parameter for the inet family, a commit error occurs when you commit the configuration. This parameter is optional for a CCC family. If you do not configure the destination MAC address, then the default value of 0x00:0x11:0xAE:0x92:0x2F:0x28 is used. This is a mandatory parameter for family bridge.

        Specify the MAC address as six hexadecimal bytes in one of the following formats: nnnn.nnnn.nnnn or nn:nn:nn:nn:nn:nn; for example, 0011.2233.4455 or 00:11:22:33:44:55.

        If you do not configure the destination MAC address, the default value of 0x00:0x11:0xAE:0x92:0x2F:0x28 is used.

        Destination UDP Port

        Specify the UDP port of the destination to be used in the UDP header for the generated frames. If you do not specify the UDP port, the default value of 4041 is used. This parameter is optional for a bridge family.

        Range: 1 through 65535

        Default: 4041

        Direction

        Specify the direction of the interface on which the test must be run. This parameter is valid only for a CCC family. Select either of the following values from the list:

        • Egress—Enable the test to be run in the egress direction of the interface (traffic sent towards network-to-network interface (NNI)). This option is applicable for a CCC and bridge family.
        • Ingress—Enable the test to be run in the ingress direction of the interface (traffic sent towards user-to-network interface (UNI)). You cannot configure this option for a bridge family.

        DSCP Code Points

        Specify the value of the Differentiated Services (DiffServ) field within the IP header of the test frames. The DiffServ code point (DSCP) bits value must be set to a valid 6-bit pattern. If you do not specify this value, 0 is used in the DSCP fields in the IP header.

        dscp-bits—A valid 6-bit pattern; for example, 001111, or one of the following configured DSCP aliases:

        • af11—Default: 001010
        • af12—Default: 001100
        • af13—Default: 001110
        • af21—Default: 010010
        • af22—Default: 010100
        • af23 —Default: 010110
        • af31 —Default: 011010
        • af32 —Default: 011100
        • af33 —Default: 011110
        • af41 —Default: 100010
        • af42 —Default:100100
        • af43 —Default:100110
        • be—Default: 000000
        • cs1—Default: 001000
        • cs2—Default: 010000
        • cs3—Default: 011000
        • cs4—Default: 100000
        • cs5—Default: 101000
        • cs6—Default: 110000
        • cs7—Default: 111000
        • ef—Default: 101110
        • nc1—Default: 110000
        • nc2—Default: 111000

        Forwarding Class

        Specify the forwarding class to be used for test frames. The forwarding class specifies the manner in which the test frames are processed by the Packet Forwarding Engine of the router. If you do not configure this parameter, test frames are treated as best-effort traffic.

        You must have previously configured this forwarding class by including the forwarding-class statement at the [edit class-of-service interfaces interface-name unit logical-unit-number] hierarchy level.

        CoS packet classification assigns an incoming packet to an output queue based on the packet’s forwarding class. Each packet is associated with one of the following default forwarding classes:

        • Expedited forwarding (EF)—Provides a low-loss, low-latency, low- jitter, assured bandwidth, end-to-end service.
        • Assured forwarding (AF)—Provides a group of values you can define and includes four subclasses: AF1, AF2, AF3, and AF4, each with three drop probabilities: low, medium, and high.
        • Best effort (BE)—Provides no service profile. For the best effort forwarding class, loss priority is typically not carried in a class-of-service (CoS) value and random early detection (RED) drop profiles are more aggressive.
        • Network control (NC)—This class is typically high priority because it supports protocol control.

        Halt on Prefix Down

        By default, an RFC2544 test ignores a prefix down event (that is, when the prefix associated with the test goes down) and continues to run. If you select this check box, when a prefix goes down, corresponding tests are aborted. The show output for the test indicates that the test was aborted due to prefix going down.

        Inner VLAN ID

        Specify the inner VLAN ID for the test frames. This parameter is valid only for a circuit cross-connect (CCC) or Ethernet pseudowire family. This parameter is applicable for dual-tagged packets.

        Range: 0 through 4094

        Outer VLAN ID

        Specify the outer VLAN ID for the test frames. This parameter is applicable for single tagged and dual-tagged packets. This parameter is valid only for a circuit cross-connect (CCC) or Ethernet pseudowire family.

        Range: 0 through 4094

        Skip ARP Iteration

        This parameter is valid only in family inet mode. ARP iteration is a 3-second iteration that is run for all inet tests. The results of this iteration are ignored in test result calculations. Sending test frames for 3 seconds ensures that all devices on the path to the destination build their ARP entries.

        Test Iteration Duration

        Specify the duration of each iteration in seconds. If you configure this value, the default value of each iteration depends on the type of test being run. For throughput, back-back-frames and frame-loss types of tests, the default value is 20 seconds. For latency tests, the default value is 120 seconds.

        Range: 1 through 172800

      2. When you are done entering information in the Initiator panel, select Reflector in the left panel.
    3. Configuring the Reflector Device

      To configure the reflector device to support operation of the RFC2544 test:

      1. Enter information in the fields in the Reflector panel.

        Note: The appearance of the Reflector window depends on the value you specify for the Family parameter. The following illustration shows the window that appears when you specify ccc. The subsequent illustration shows the window that appears when you specify inet.




        Field

        Description

        PE Device

        Select the name of the device on which the reflector interface is located.

        Click Select beside the field to open the Choose Endpoints dialog box. From the Choose Endpoints dialog box that appears, select the devices that you want to participate in the RFC 2544 test. Use the multiple selection feature to select one or more devices. The lower part of the dialog box refreshes to display the interfaces associated with the selected device. Select the check boxes next to the interfaces you want to associate with the RFC 2544-based benchmarking test.

        UNI Interface

        Specify the logical interface on which the RFC 2544-based benchmarking test is run. This is a local user-to-network interface (UNI) on behalf of which the test frames are generated when the test direction is egress.

        Family

        Specify the address type family for the benchmarking test:

        • inet—Indicates that the test is run on an IPv4 service.

          Note: Family inet is not supported on ACX5048 and ACX5096 routers.

        • ccc—Indicates that the test is run on a circuit cross-connect (CCC) or Ethernet pseudowire service. The direction option specifies the direction (ingress or egress) to be used for the test.

        Source IPV4 Address

        Specify the source IPv4 address to be used in generated test frames. This parameter is optional for both circuit cross-connect (CCC) and, inet , and also for bridge family. If you do not configure the source IPv4 address for an inet family, the source address of the interface is used to transmit the test frames.

        Source MAC Address

        Specify the MAC address of the device from which test data originates. This parameter is effective for a circuit cross-connect (CCC) family and it is not applicable for an inet family. If you specify this parameter for an inet family, a commit error occurs when you commit the configuration. This parameter is optional for a CCC family.

        Specify the MAC address as six hexadecimal bytes in one of the following formats: nnnn.nnnn.nnnn or nn:nn:nn:nn:nn:nn; for example, 0011.2233.4455 or 00:11:22:33:44:55.

        If you do not configure the destination MAC address, the default value of 0x00:0x60:0x67:0x71:0xC6:0x62 is used.

        Source UDP Port

        Specify the UDP port of the source to be used in the UDP header for the generated frames. If you do not specify the UDP port, the default value of 4040 is used.

        Range: 1 through 65535

        Default: 4040

        Destination IPV4 Address

        Specify the destination IPv4 address to be used in generated test frames. This is optional for the family bridge. You must configure this option if you specify inet as the family. This option is not required if you specify circuit cross-connect (CCC).

        If you do not configure the destination IPv4 address, the default value of 192.168.1.20 is used.

        Destination MAC Address

        Specify the destination MAC address used in generated test frames. This parameter is not applicable for an inet family and is considered only for a CCC family. If you specify this parameter for the inet family, a commit error occurs when you commit the configuration. This parameter is optional for a CCC family. If you do not configure the destination MAC address, then the default value of 0x00:0x11:0xAE:0x92:0x2F:0x28 is used. This is a mandatory parameter for family bridge.

        Specify the MAC address as six hexadecimal bytes in one of the following formats: nnnn.nnnn.nnnn or nn:nn:nn:nn:nn:nn; for example, 0011.2233.4455 or 00:11:22:33:44:55.

        If you do not configure the destination MAC address, the default value of 0x00:0x11:0xAE:0x92:0x2F:0x28 is used.

        Destination UDP Port

        Specify the UDP port of the destination to be used in the UDP header for the generated frames. If you do not specify the UDP port, the default value of 4041 is used. This parameter is optional for a bridge family.

        Range: 1 through 65535

        Default: 4041

        Direction

        Specify the direction of the interface on which the test must be run. This parameter is valid only for a CCC family. Select either of the following values from the list:

        • Egress—Enable the test to be run in the egress direction of the interface (traffic sent towards network-to-network interface (NNI)). This option is applicable for a CCC and bridge family.
        • Ingress—Enable the test to be run in the ingress direction of the interface (traffic sent towards user-to-network interface (UNI)). You cannot configure this option for a bridge family.

        DSCP Code Points

        Specify the value of the Differentiated Services (DiffServ) field within the IP header of the test frames. The DiffServ code point (DSCP) bits value must be set to a valid 6-bit pattern. If you do not specify this value, 0 is used in the DSCP fields in the IP header.

        dscp-bits—A valid 6-bit pattern; for example, 001111, or one of the following configured DSCP aliases:

        • af11—Default: 001010
        • af12—Default: 001100
        • af13—Default: 001110
        • af21—Default: 010010
        • af22—Default: 010100
        • af23 —Default: 010110
        • af31 —Default: 011010
        • af32 —Default: 011100
        • af33 —Default: 011110
        • af41 —Default: 100010
        • af42 —Default:100100
        • af43 —Default:100110
        • be—Default: 000000
        • cs1—Default: 001000
        • cs2—Default: 010000
        • cs3—Default: 011000
        • cs4—Default: 100000
        • cs5—Default: 101000
        • cs6—Default: 110000
        • cs7—Default: 111000
        • ef—Default: 101110
        • nc1—Default: 110000
        • nc2—Default: 111000

        Forwarding Class

        Specify the forwarding class to be used for test frames. The forwarding class specifies the manner in which the test frames are processed by the Packet Forwarding Engine of the router. If you do not configure this parameter, test frames are treated as best-effort traffic.

        You must have previously configured this forwarding class by including the forwarding-class statement at the [edit class-of-service interfaces interface-name unit logical-unit-number] hierarchy level.

        CoS packet classification assigns an incoming packet to an output queue based on the packet’s forwarding class. Each packet is associated with one of the following default forwarding classes:

        • Expedited forwarding (EF)—Provides a low-loss, low-latency, low- jitter, assured bandwidth, end-to-end service.
        • Assured forwarding (AF)—Provides a group of values you can define and includes four subclasses: AF1, AF2, AF3, and AF4, each with three drop probabilities: low, medium, and high.
        • Best effort (BE)—Provides no service profile. For the best effort forwarding class, loss priority is typically not carried in a class-of-service (CoS) value and random early detection (RED) drop profiles are more aggressive.
        • Network control (NC)—This class is typically high priority because it supports protocol control.

        Halt on Prefix Down

        By default, an RFC2544 test ignores a prefix down event (that is, when the prefix associated with the test goes down) and continues to run. If you select this check box, when a prefix goes down, corresponding tests are aborted. The show output for the test indicates that the test was aborted due to prefix going down.

        Inner VLAN ID

        Specify the inner VLAN ID for the test frames. This parameter is valid only for a circuit cross-connect (CCC) or Ethernet pseudowire family. This parameter is applicable for dual-tagged packets.

        Range: 0 through 4094

        Outer VLAN ID

        Specify the outer VLAN ID for the test frames. This parameter is applicable for single tagged and dual-tagged packets. This parameter is valid only for a circuit cross-connect (CCC) or Ethernet pseudowire family.

        Range: 0 through 4094

        Reflector Etype

        Specify the EtherType to be used for reflection of the test frames, which is a two-octet field in an Ethernet frame that defines the protocol encapsulated in the frame payload. This parameter is valid only if you configured the test mode to be a reflector. If you do not configure this parameter, all EtherTypes are reflected. Use an EtherType value that matches the EtherType value set on the customer premises equipment (CPE) to which your router connects. The EtherType value appears in the Ethernet type field of the packet. It specifies the protocol being transported in the Ethernet frame.

        Range: 1 through 65535

        Reflector Mode

        Specify the reflection mode for the benchmarking test. Select one of the following values from the drop-down list:

        • mac-rewrite—Enables rewriting of the MAC address on the reflected frames. The MAC addresses specified in the source-mac-address and destination-mac-address options are used.
        • mac-swap—Swaps the source and destination MAC addresses in the test frame. This is the default behavior.
        • no-mac-swap—Does not swap the source and destination MAC addresses in the test frame. The frame is returned to the originator without any modification to the MAC addresses.

        For benchmarking tests on the UNI direction of an Ethernet pseudowire service, if reflection mode is configured, you must configure a static ARP entry. Otherwise, the tests fail when test frames on the UNI interface are reflected. ARP resolution does not enable a successful reflection of test frames for UNI interfaces.

        Skip ARP Iteration

        Disable the Address Resolution Protocol (ARP) test iteration for IPv4 services during a benchmarking test. This parameter is valid only for an inet family. An ARP test iteration is a 3-second iteration that is run for all inet tests. The results of this iteration are disregarded in the test result calculations. The ARP test iteration is performed by sending test frames for 3 seconds to ensure that all devices on the path to destination add ARP entries in the cache of the corresponding devices.

      2. When you are done entering information in the Reflector tab fields, click Finish.
    4. When you are done entering information in the General Settings fields, click Next. The Review page appears.

      Alternatively, click Done to complete the test creation and save the test settings. You are returned to the Manage RFC 2544 Test page and the test you created in listed in the table.

    Reviewing the Configured RFC 2544 Test Settings

    The Review page of the RFC 2544 Test creation and modification wizards enable you to view and evaluate the service parameters and components you configured in preceding steps or pages of the wizard. This page provides a comprehensive, single-page view of all the service elements configured in the different pages of the wizard. You can either click the buttons corresponding to the various settings at the top of the wizard page to directly traverse to the page you want to modify or click the navigation buttons at the bottom of the wizard page to go to the different pages of the wizard.

    To review the configured RFC 2544-based test settings:

    1. Click Review to view the defined parameters. You can examine and modify the created RFC 2544 test parameters. Alternatively, click the corresponding buttons at the top of the wizard page to navigate to the specific pages pertain to the settings you want to modify.
    2. Click Edit next to the section that contains the parameter you want to modify. You are navigated to the corresponding page of the wizard in which the parameter settings are defined.
    3. Click Finish to save the RFC 2544-based test. Click Back to return to the previous page of the wizard; else click Cancel to discard the changes. The service order inventory window appears.

      The RFC 2544 test is saved in the database and appears in the Manage RFC 2544 Test inventory page. You can modify a previously created test as necessary.

    Modified: 2016-03-14