Tech-invite3GPPspaceIETFspace
96959493929190898887868584838281807978777675747372717069686766656463626160595857565554535251504948474645444342414039383736353433323130292827262524232221201918171615141312111009080706050403020100
in Index   Prev   Next

RFC 3116

Methodology for ATM Benchmarking

Pages: 127
Informational
Part 3 of 5 – Pages 47 to 76
First   Prev   Next

Top   ToC   RFC3116 - Page 47   prevText

3.2.3. Cell Loss Ratio (CLR)

3.2.3.1. CLR/Steady Load/One VCC
Objective: To determine the SUT ratio of lost cells on one VCC in a transmission in relation to the total cells sent as defined in RFC 2761 "Terminology for ATM Benchmarking". Procedure: 1) Set up the SUT and test device using the bi-directional configuration. 2) Configure the SUT and test device with one VCC. The VCC SHOULD contain one VPI/VCI. The VCC MUST be configured as either a CBR, VBR, or UBR connection. The VPI/VCI MUST not be one of the reserved ATM signaling channels (e.g., [0,5], [0,16]). 3) Send a specific number of IP packets at a specific constant rate through the SUT via the defined test VCC. Since this test is not a throughput test, the rate should not be greater than 90% of line rate. The IP PDUs MUST be encapsulated in AAL5. 4) Count the IP packets that are transmitted by the SUT to verify connectivity and load. If the count on the test device is the same on the SUT, continue the test; else lower the test device traffic rate until the counts are the same. 5) Record the number of cells transmitted and received on the test device.
Top   ToC   RFC3116 - Page 48
   Reporting Format:

      The results of the CLR/Steady Load/One VCC test SHOULD be reported
      in a form of text and graph.

      The text results SHOULD display the numerical values of the CLR.
      The values given SHOULD include: time period of test in s, test
      VPI/VCI value, total number of cells transmitted and received on
      the given VPI/VCI during the test in positive integers, and the
      CLR for the entire test.

      The graph results SHOULD display the Cell Loss ratio values.  The
      x-coordinate SHOULD be the test run time in either seconds,
      minutes or days depending on the total length of the test.  The
      x-coordinate time SHOULD be configurable.  The y-coordinate SHOULD
      be the CLR.  The integration time per point MUST be indicated.

      The results MUST also indicate the packet size in octets, traffic
      rate in packets per second, and bearer class as generated by the
      test device.  The VCC and VPI/VCI values MUST be indicated.  The
      PCR, SCR, and MBS MUST be indicated.  The bearer class of the
      created VCC MUST also be indicated.

3.2.3.2. CLR/Steady Load/Twelve VCCs
Objective: To determine the SUT ratio of lost cells on twelve VCCs in a transmission in relation to the total cells sent as defined in RFC 2761 "Terminology for ATM Benchmarking". Procedure: 1) Set up the SUT and test device using the bi-directional configuration. 2) Configure the SUT and test device with twelve VCCs, using 1 VPI and 12 VCIs. The VCC's MUST be configured as either a CBR, VBR, or UBR connection. The VPI/VCIs MUST not be one of the reserved ATM signaling channels (e.g., [0,5], [0,16]). 3) Send a specific number of IP packets at a specific constant rate through the SUT via the defined test VCCs. All of the VPI/VCI pairs will generate traffic at the same traffic rate. Since this test is not a throughput test, the rate should not be greater than 90% of line rate. The IP PDUs MUST be encapsulated in AAL5.
Top   ToC   RFC3116 - Page 49
   4)  Count the IP packets that are transmitted by the SUT on all VCCs
       to verify connectivity and load.  If the count on the test device
       is the same on the SUT, continue the test; else lower the test
       device traffic rate until the counts are the same.

   5)  Record the number of cells transmitted and received per VCC on
       the test device.

   Reporting Format:

      The results of the CLR/Steady Load/Twelve VCCs test SHOULD be
      reported in a form of text and graph.

      The text results SHOULD display the numerical values of the CLR.
      The values given SHOULD include: time period of test in s, test
      VPI/VCI value, total number of cells transmitted and received on
      the given VPI/VCI during the test in positive integers, and the
      CLR for the entire test.

      The graph results SHOULD display the Cell Loss ratio values.  The
      x-coordinate SHOULD be the test run time in either seconds,
      minutes or days depending on the total length of the test.  The
      x-coordinate time SHOULD be configurable.  The y-coordinate SHOULD
      be the CLR for each VCC.  There should be 12 curves on the graph,
      on curve indicated and labeled for each VCC.  The integration time
      per point MUST be indicated.

      The results MUST also indicate the packet size in octets, traffic
      rate in packets per second, and bearer class as generated by the
      test device.  The VCC and VPI/VCI values MUST be indicated.  The
      PCR, SCR, and MBS MUST be indicated.  The bearer class of the
      created VCC MUST also be indicated.

3.2.3.3. CLR/Steady Load/Maximum VCCs
Objective: To determine the SUT ratio of lost cells with the maximum number VCCs supported on the SUT in a transmission in relation to the total cells sent as defined in RFC 2761 "Terminology for ATM Benchmarking". Procedure: 1) Set up the SUT and test device using the bi-directional configuration. 2) Configure the SUT and test device with the maximum number of VCCs supported on the SUT. For example, if the maximum number of VCCs supported on the SUT is 1024, define 256 VPIs with 4 VCIs per
Top   ToC   RFC3116 - Page 50
       VPI.  The VCC's MUST be configured as either a CBR, VBR, or UBR
       connection.  The VPI/VCIs MUST not be one of the reserved ATM
       signaling channels (e.g., [0,5], [0,16]).

   3)  Send a specific number of IP packets at a specific constant rate
       through the SUT via the defined test VCCs.  All of the VPI/VCI
       pairs will generate traffic at the same traffic rate.  Since this
       test is not a throughput test, the rate should not be greater
       than 90% of line rate.  The IP PDUs MUST be encapsulated in AAL5.

   4)  Count the IP packets that are transmitted by the SUT on all VCCs
       to verify connectivity and load.  If the count on the test device
       is the same on the SUT, continue the test; else lower the test
       device traffic rate until the counts are the same.

   5)  Record the number of cells transmitted and received per VCC on
       the test device.

   Reporting Format:

      The results of the CLR/Steady Load/Maximum VCCs test SHOULD be
      reported in a form of text and graph.

      The text results SHOULD display the numerical values of the CLR.
      The values given SHOULD include: time period of test in s, test
      VPI/VCI value, total number of cells transmitted and received on
      the given VPI/VCI during the test in positive integers, and the
      CLR for the entire test.

      The graph results SHOULD display the Cell Loss ratio values.
      There will be (Max number of VCCs/10) graphs, with 10 VCCs
      indicated on each graph.  The x-coordinate SHOULD be the test run
      time in either seconds, minutes or days depending on the total
      length of the test.  The x-coordinate time SHOULD be configurable.
      The y-coordinate SHOULD be the CLR for each VCC.  There SHOULD be
      no more than 10 curves on each graph, one curve indicated and
      labeled for each VCC.  The integration time per point MUST be
      indicated.

      The results MUST also indicate the packet size in octets, traffic
      rate in packets per second, and bearer class as generated by the
      test device.  The VCC and VPI/VCI values MUST be indicated.  The
      PCR, SCR, and MBS MUST be indicated.  The bearer class of the
      created VCC MUST also be indicated.
Top   ToC   RFC3116 - Page 51
3.2.3.4. CLR/Bursty VBR Load/One VCC
Objective: To determine the SUT ratio of lost cells on one VCC in a transmission in relation to the total cells sent as defined in RFC 2761 "Terminology for ATM Benchmarking". Procedure: 1) Set up the SUT and test device using the bi-directional configuration. 2) Configure the SUT and test device with one VCC. The VCC SHOULD contain one VPI/VCI. The VCC MUST be configured as either a CBR or VBR connection. The VPI/VCI MUST not be one of the reserved ATM signaling channels (e.g., [0,5], [0,16]). The PCR, SCR, and MBS must be configured using one of the specified traffic descriptors. 3) Send a specific number of IP packets containing one of the specified bit patterns at a specific rate through the SUT via the defined test VCC. Since this test is not a throughput test, the rate should not be greater than 90% of line rate. The IP PDUs MUST be encapsulated in AAL5. 4) Count the IP packets that are transmitted by the SUT to verify connectivity and load. If the count on the test device is the same on the SUT, continue the test; else lower the test device traffic rate until the counts are the same. 5) Record the number of cells transmitted and received on the test device. Reporting Format: The results of the CLR/Bursty VBR Load/One VCC test SHOULD be reported in a form of text and graph. The text results SHOULD display the numerical values of the CLR. The values given SHOULD include: time period of test in s, test VPI/VCI value, total number of cells transmitted and received on the given VPI/VCI during the test in positive integers, and the CLR for the entire test. The graph results SHOULD display the Cell Loss ratio values. The x-coordinate SHOULD be the test run time in either seconds, minutes or days depending on the total length of the test. The x-coordinate time SHOULD be configurable. The y-coordinate SHOULD be the CLR. The integration time per point MUST be indicated.
Top   ToC   RFC3116 - Page 52
      The results MUST also indicate the packet size in octets, traffic
      rate in packets per second, and bearer class as generated by the
      test device.  The VCC and VPI/VCI values MUST be indicated.  The
      PCR, SCR, and MBS MUST be indicated.  The bearer class of the
      created VCC MUST also be indicated.

3.2.3.5. CLR/Bursty VBR Load/Twelve VCCs
Objective: To determine the SUT ratio of lost cells on twelve VCCs in a transmission in relation to the total cells sent as defined in RFC 2761 "Terminology for ATM Benchmarking". Procedure: 1) Set up the SUT and test device using the bi-directional configuration. 2) Configure the SUT and test device with twelve VCCs, using 1 VPI and 12 VCIs. The VCC MUST be configured as either a CBR or VBR connection. The VPI/VCIs MUST not be one of the reserved ATM signaling channels (e.g., [0,5], [0,16]). The PCR, SCR, and MBS must be configured using one of the specified traffic descriptors. 3) Send a specific number of IP packets containing one of the specified bit patterns at a specific rate through the SUT via the defined test VCCs. All of the VPI/VCI pairs will generate traffic at the same traffic rate. Since this test is not a throughput test, the rate should not be greater than 90% of line rate. The PCR, SCR, and MBS must be indicated. The IP PDUs MUST be encapsulated in AAL5. 4) Count the IP packets that are transmitted by the SUT on all VCCs to verify connectivity and load. If the count on the test device is the same on the SUT, continue the test; else lower the test device traffic rate until the counts are the same. 5) Record the number of cells transmitted and received per VCC on the test device. Reporting Format: The results of the CLR/Bursty VBR Load/Twelve VCCs test SHOULD be reported in a form of text and graph. The text results SHOULD display the numerical values of the CLR. The values given SHOULD include: time period of test in s, test VPI/VCI value, total number of cells transmitted and received on
Top   ToC   RFC3116 - Page 53
      the given VPI/VCI during the test in positive integers, and the
      CLR for the entire test.

      The graph results SHOULD display the Cell Loss ratio values.  The
      x-coordinate SHOULD be the test run time in either seconds,
      minutes or days depending on the total length of the test.  The
      x-coordinate time SHOULD be configurable.  The y-coordinate SHOULD
      be the CLR for each VCC.  There should be 12 curves on the graph,
      on curve indicated and labeled for each VCC.  The integration time
      per point MUST be indicated.

      The results MUST also indicate the packet size in octets, traffic
      rate in packets per second, and bearer class as generated by the
      test device.  The VCC and VPI/VCI values MUST be indicated.  The
      PCR, SCR, and MBS MUST be indicated.  The bearer class of the
      created VCC MUST also be indicated.

3.2.3.6. CLR/Bursty VBR Load/Maximum VCCs
Objective: To determine the SUT ratio of lost cells with the maximum number VCCs supported on the SUT in a transmission in relation to the total cells sent as defined in RFC 2761 "Terminology for ATM Benchmarking". Procedure: 1) Set up the SUT and test device using the bi-directional configuration. 2) Configure the SUT and test device with the maximum number of VCCs supported on the SUT. For example, if the maximum number of VCCs supported on the SUT is 1024, define 256 VPIs with 4 VCIs per VPI. The VCC MUST be configured as either a CBR or VBR connection. The VPI/VCIs MUST not be one of the reserved ATM signaling channels (e.g., [0,5], [0,16]). The PCR, SCR, and MBS must be configured using one of the specified traffic descriptors. 3) Send a specific number of IP packets containing one of the specified bit patterns at a specific rate through the SUT via the defined test VCCs. All of the VPI/VCI pairs will generate traffic at the same traffic rate. Since this test is not a throughput test, the rate should not be greater than 90% of line rate. The IP PDUs MUST be encapsulated in AAL5.
Top   ToC   RFC3116 - Page 54
   4)  Count the IP packets that are transmitted by the SUT on all VCCs
       to verify connectivity and load.  If the count on the test device
       is the same on the SUT, continue the test; else lower the test
       device traffic rate until the counts are the same.

   5)  Record the number of cells transmitted and received per VCC on
       the test device.

   Reporting Format:

      The results of the CLR/Bursty VBR Load/Maximum VCCs test SHOULD be
      reported in a form of text and graph.

      The text results SHOULD display the numerical values of the CLR.
      The values given SHOULD include: time period of test in s, test
      VPI/VCI value, total number of cells transmitted and received on
      the given VPI/VCI during the test in positive integers, and the
      CLR for the entire test.

      The graph results SHOULD display the Cell Loss ratio values.
      There will be (Max number of VCCs/10) graphs, with 10 VCCs
      indicated on each graph.  The x-coordinate SHOULD be the test run
      time in either seconds, minutes or days depending on the total
      length of the test.  The x-coordinate time SHOULD be configurable.
      The y-coordinate SHOULD be the CLR for each VCC.  There SHOULD be
      no more than 10 curves on each graph, one curve indicated and
      labeled for each VCC.  The integration time per point MUST be
      indicated.

      The results MUST also indicate the packet size in octets, traffic
      rate in packets per second, and bearer class as generated by the
      test device.  The VCC and VPI/VCI values MUST be indicated.  The
      PCR, SCR, and MBS MUST be indicated.  The bearer class of the
      created VCC MUST also be indicated.

3.2.4. Cell Misinsertion Rate (CMR)

3.2.4.1. CMR/Steady Load/One VCC
Objective: To determine the SUT ratio of cell misinsertion on one VCC in a transmission in relation to the total cells sent as defined in RFC 2761 "Terminology for ATM Benchmarking". Procedure: 1) Set up the SUT and test device using the bi-directional configuration.
Top   ToC   RFC3116 - Page 55
   2)  Configure the SUT and test device with one VCC.  The VCC MUST be
       configured as either a CBR, VBR, or UBR connection.  The VCC
       SHOULD contain one VPI/VCI.  The VPI/VCI MUST not be one of the
       reserved ATM signaling channels (e.g., [0,5], [0,16]).

   3)  Send a specific number of IP packets at a specific constant rate
       through the SUT via the defined test VCC.  Since this test is not
       a throughput test, the rate should not be greater than 90% of
       line rate.  The IP PDUs MUST be encapsulated in AAL5.

   4)  Count the IP packets that are transmitted by the SUT to verify
       connectivity and load.  If the count on the test device is the
       same on the SUT, continue the test; else lower the test device
       traffic rate until the counts are the same.

   5)  Record the number of cell misinsertion errors at the receiver end
       of the test device.

   Reporting Format:

      The results of the CMR/Steady Load/One VCC test SHOULD be reported
      in a form of text and graph.

      The text results SHOULD display the numerical values of the CMR.
      The values given SHOULD include: time period of test in s, test
      VPI/VCI value, total number of cells transmitted and received on
      the given VPI/VCI during the test in positive integers, and the
      CMR for the entire test.

      The graph results SHOULD display the Cell misinsertion rate
      values.  The x-coordinate SHOULD be the test run time in either
      seconds, minutes or days depending on the total length of the
      test.  The x-coordinate time SHOULD be configurable.  The y-
      coordinate SHOULD be the CMR.  The integration time per point MUST
      be indicated.

      The results MUST also indicate the packet size in octets, traffic
      rate in packets per second, and bearer class as generated by the
      test device.  The VCC and VPI/VCI values MUST be indicated.  The
      PCR, SCR, and MBS MUST be indicated.  The bearer class of the
      created VCC MUST also be indicated.

3.2.4.2. CMR/Steady Load/Twelve VCCs
Objective: To determine the SUT rate of misinserted cells on twelve VCCs in a transmission in relation to the total cells sent as defined in RFC 2761 "Terminology for ATM Benchmarking".
Top   ToC   RFC3116 - Page 56
   Procedure:

   1)  Set up the SUT and test device using the bi-directional
       configuration.

   2)  Configure the SUT and test device with twelve VCCs, using 1 VPI
       and 12 VCIs.  The VCC's MUST be configured as either a CBR, VBR,
       or UBR connection.  The VPI/VCIs MUST not be one of the reserved
       ATM signaling channels (e.g., [0,5], [0,16]).

   3)  Send a specific number of IP packets at a specific constant rate
       through the SUT via the defined test VCCs.  All of the VPI/VCI
       pairs will generate traffic at the same traffic rate.  Since this
       test is not a throughput test, the rate should not be greater
       than 90% of line rate.  The IP PDUs MUST be encapsulated in AAL5.

   4)  Count the IP packets that are transmitted by the SUT on all VCCs
       to verify connectivity and load.  If the count on the test device
       is the same on the SUT, continue the test; else lower the test
       device traffic rate until the counts are the same.

   5)  Record the number of cell misinsertion errors at the receiver end
       of the test device per VCC.

   Reporting Format:

      The results of the CMR/Steady Load/Twelve VCCs test SHOULD be
      reported in a form of text and graph.

      The text results SHOULD display the numerical values of the CMR.
      The values given SHOULD include: time period of test in s, test
      VPI/VCI value, total number of cells transmitted and received on
      the given VPI/VCI during the test in positive integers, and the
      CMR for the entire test.

      The graph results SHOULD display the Cell misinsertion rate
      values.  The x-coordinate SHOULD be the test run time in either
      seconds, minutes or days depending on the total length of the
      test.  The x-coordinate time SHOULD be configurable.  The y-
      coordinate SHOULD be the CMR for each VCC.  There should be 12
      curves on the graph, on curve indicated and labeled for each VCC.
      The integration time per point MUST be indicated.

      The results MUST also indicate the packet size in octets, traffic
      rate in packets per second, and bearer class as generated by the
      test device.  The VCC and VPI/VCI values MUST be indicated.  The
      PCR, SCR, and MBS MUST be indicated.  The bearer class of the
      created VCC MUST also be indicated.
Top   ToC   RFC3116 - Page 57
3.2.4.3. CMR/Steady Load/Maximum VCCs
Objective: To determine the SUT rate of misinserted cells with the maximum number VCCs supported on the SUT in a transmission in relation to the total cells sent as defined in RFC 2761 "Terminology for ATM Benchmarking". Procedure: 1) Set up the SUT and test device using the bi-directional configuration. 2) Configure the SUT and test device with the maximum number of VCCs supported on the SUT. For example, if the maximum number of VCCs supported on the SUT is 1024, define 256 VPIs with 4 VCIs per VPI. The VCC's MUST be configured as either a CBR, VBR, or UBR connection. The VPI/VCIs MUST not be one of the reserved ATM signaling channels (e.g., [0,5], [0,16]). 3) Send a specific number of IP packets at a specific constant rate through the SUT via the defined test VCCs. All of the VPI/VCI pairs will generate traffic at the same traffic rate. Since this test is not a throughput test, the rate should not be greater than 90% of line rate. The IP PDUs MUST be encapsulated in AAL5. 4) Count the IP packets that are transmitted by the SUT on all VCCs to verify connectivity and load. If the count on the test device is the same on the SUT, continue the test; else lower the test device traffic rate until the counts are the same. 5) Record the number of cell misinsertion errors at the receiver end of the test device per VCC. Reporting Format: The results of the CMR/Steady Load/Maximum VCCs test SHOULD be reported in a form of text and graph. The text results SHOULD display the numerical values of the CMR. The values given SHOULD include: time period of test in s, test VPI/VCI value, total number of cells transmitted and received on the given VPI/VCI during the test in positive integers, and the CMR for the entire test. The graph results SHOULD display the Cell misinsertion rate values. There will be (Max number of VCCs/10) graphs, with 10 VCCs indicated on each graph. The x-coordinate SHOULD be the test run time in either seconds, minutes or days depending on the total
Top   ToC   RFC3116 - Page 58
      length of the test.  The x-coordinate time SHOULD be configurable.
      The y-coordinate SHOULD be the CMR for each VCC.  There SHOULD be
      no more than 10 curves on each graph, one curve indicated and
      labeled for each VCC.  The integration time per point MUST be
      indicated.

      The results MUST also indicate the packet size in octets, traffic
      rate in packets per second, and bearer class as generated by the
      test device.  The VCC and VPI/VCI values MUST be indicated.  The
      PCR, SCR, and MBS MUST be indicated.  The bearer class of the
      created VCC MUST also be indicated.

3.2.4.4. CMR/Bursty VBR Load/One VCC
Objective: To determine the SUT rate of misinserted cells on one VCC in a transmission in relation to the total cells sent as defined in RFC 2761 "Terminology for ATM Benchmarking". Procedure: 1) Set up the SUT and test device using the bi-directional configuration. 2) Configure the SUT and test device with one VCC. The VCC SHOULD contain one VPI/VCI. The VCC MUST be configured as either a CBR or VBR connection. The VPI/VCI MUST not be one of the reserved ATM signaling channels (e.g., [0,5], [0,16]). The PCR, SCR, and MBS must be configured using one of the specified traffic descriptors. 3) Send a specific number of IP packets containing one of the specified bit patterns at a specific rate through the SUT via the defined test VCC. Since this test is not a throughput test, the rate should not be greater than 90% of line rate. The IP PDUs MUST be encapsulated in AAL5. 4) Count the IP packets that are transmitted by the SUT to verify connectivity and load. If the count on the test device is the same on the SUT, continue the test; else lower the test device traffic rate until the counts are the same. 5) Record the number of cell misinsertion errors at the receiver end of the test device. Reporting Format: The results of the CMR/Bursty VBR Load/One VCC test SHOULD be reported in a form of text and graph.
Top   ToC   RFC3116 - Page 59
      The text results SHOULD display the numerical values of the CMR.
      The values given SHOULD include: time period of test in s, test
      VPI/VCI value, total number of cells transmitted and received on
      the given VPI/VCI during the test in positive integers, and the
      CMR for the entire test.

      The graph results SHOULD display the Cell misinsertion rate
      values.  The x-coordinate SHOULD be the test run time in either
      seconds, minutes or days depending on the total length of the
      test.  The x-coordinate time SHOULD be configurable.  The y-
      coordinate SHOULD be the CMR.  The integration time per point MUST
      be indicated.

      The results MUST also indicate the packet size in octets, traffic
      rate in packets per second, and bearer class as generated by the
      test device.  The VCC and VPI/VCI values MUST be indicated.  The
      PCR, SCR, and MBS MUST be indicated.  The bearer class of the
      created VCC MUST also be indicated.

3.2.4.5. CMR/Bursty VBR Load/Twelve VCCs
Objective: To determine the SUT rate of misinserted cells on twelve VCCs in a transmission in relation to the total cells sent as defined in RFC 2761 "Terminology for ATM Benchmarking". Procedure: 1) Set up the SUT and test device using the bi-directional configuration. 2) Configure the SUT and test device with twelve VCCs, using 1 VPI and 12 VCIs. The VCC's MUST be configured as either a CBR or VBR connection. The VPI/VCIs MUST not be one of the reserved ATM signaling channels (e.g., [0,5], [0,16]). The PCR, SCR, and MBS must be configured using one of the specified traffic descriptors. 3) Send a specific number of IP packets containing one of the specified bit patterns at a specific rate through the SUT via the defined test VCCs. All of the VPI/VCI pairs will generate traffic at the same traffic rate. Since this test is not a throughput test, the rate should not be greater than 90% of line rate. The PCR, SCR, and MBS must be indicated. The IP PDUs MUST be encapsulated in AAL5.
Top   ToC   RFC3116 - Page 60
   4)  Count the IP packets that are transmitted by the SUT on all VCCs
       to verify connectivity and load.  If the count on the test device
       is the same on the SUT, continue the test; else lower the test
       device traffic rate until the counts are the same.

   5)  Record the number of cell misinsertion errors at the receiver end
       of the test device per VCC.

   Reporting Format:

      The results of the CMR/Bursty VBR Load/Twelve VCCs test SHOULD be
      reported in a form of text and graph.

      The text results SHOULD display the numerical values of the CMR.
      The values given SHOULD include: time period of test in s, test
      VPI/VCI value, total number of cells transmitted and received on
      the given VPI/VCI during the test in positive integers, and the
      CMR for the entire test.

      The graph results SHOULD display the Cell misinsertion rate
      values.  The x-coordinate SHOULD be the test run time in either
      seconds, minutes or days depending on the total length of the
      test.  The x-coordinate time SHOULD be configurable.  The y-
      coordinate SHOULD be the CMR for each VCC.  There should be 12
      curves on the graph, on curve indicated and labeled for each VCC.
      The integration time per point MUST be indicated.

      The results MUST also indicate the packet size in octets, traffic
      rate in packets per second, and bearer class as generated by the
      test device.  The VCC and VPI/VCI values MUST be indicated.  The
      PCR, SCR, and MBS MUST be indicated.  The bearer class of the
      created VCC MUST also be indicated.

3.2.4.6. CMR/Bursty VBR Load/Maximum VCCs
Objective: To determine the SUT rate of misinserted cells with the maximum number VCCs supported on the SUT in a transmission in relation to the total cells sent as defined in RFC 2761 "Terminology for ATM Benchmarking". Procedure: 1) Set up the SUT and test device using the bi-directional configuration. 2) Configure the SUT and test device with the maximum number of VCCs supported on the SUT. For example, if the maximum number of VCCs supported on the SUT is 1024, define 256 VPIs with 4 VCIs per
Top   ToC   RFC3116 - Page 61
       VPI.  The VCC's MUST be configured as either a CBR or VBR
       connection.  The VPI/VCIs MUST not be one of the reserved ATM
       signaling channels (e.g., [0,5], [0,16]).  The PCR, SCR, and MBS
       must be configured using one of the specified traffic
       descriptors.

   3)  Send a specific number of IP packets containing one of the
       specified bit patterns at a specific rate through the SUT via the
       defined test VCCs.  All of the VPI/VCI pairs will generate
       traffic at the same traffic rate.  Since this test is not a
       throughput test, the rate should not be greater than 90% of line
       rate.  The IP PDUs MUST be encapsulated in AAL5.

   4)  Count the IP packets that are transmitted by the SUT on all VCCs
       to verify connectivity and load.  If the count on the test device
       is the same on the SUT, continue the test; else lower the test
       device traffic rate until the counts are the same.

   5)  Record the number of cell misinsertion errors at the receiver end
       of the test device per VCC.

   Reporting Format:

      The results of the CMR/Bursty VBR Load/Maximum VCCs test SHOULD be
      reported in a form of text and graph.

      The text results SHOULD display the numerical values of the CMR.
      The values given SHOULD include: time period of test in s, test
      VPI/VCI value, total number of cells transmitted and received on
      the given VPI/VCI during the test in positive integers, and the
      CMR for the entire test.

      The graph results SHOULD display the Cell misinsertion rate
      values.  There will be (Max number of VCCs/10) graphs, with 10
      VCCs indicated on each graph.  The x-coordinate SHOULD be the test
      run time in either seconds, minutes or days depending on the total
      length of the test.  The x-coordinate time SHOULD be configurable.
      The y-coordinate SHOULD be the CMR for each VCC.  There SHOULD be
      no more than 10 curves on each graph, one curve indicated and
      labeled for each VCC.  The integration time per point MUST be
      indicated.

      The results MUST also indicate the packet size in octets, traffic
      rate in packets per second, and bearer class as generated by the
      test device.  The VCC and VPI/VCI values MUST be indicated.  The
      PCR, SCR, and MBS MUST be indicated.  The bearer class of the
      created VCC MUST also be indicated.
Top   ToC   RFC3116 - Page 62

3.2.5. CRC Error Ratio (CRC-ER)

3.2.5.1. CRC-ER/Steady Load/One VCC
Objective: To determine the SUT ratio of CRC errors on one VCC in a transmission in relation to the total cells sent as defined in RFC 2761 "Terminology for ATM Benchmarking". Procedure: 1) Set up the SUT and test device using the bi-directional configuration. 2) Configure the SUT and test device with one VCC. The VCC SHOULD contain one VPI/VCI. The VCC MUST be configured as either a CBR, VBR, or UBR connection. The VPI/VCI MUST not be one of the reserved ATM signaling channels (e.g., [0,5], [0,16]). 3) Send a specific number of IP packets at a specific constant rate through the SUT via the defined test VCC. Since this test is not a throughput test, the rate should not be greater than 90% of line rate. The IP PDUs MUST be encapsulated in AAL5. 4) Count the IP packets that are transmitted by the SUT to verify connectivity and load. If the count on the test device is the same on the SUT, continue the test; else lower the test device traffic rate until the counts are the same. 5) Record the number of CRC errored cells received on the test device. Reporting Format: The results of the CRC-ER/Steady Load/One VCC test SHOULD be reported in a form of text and graph. The text results SHOULD display the numerical values of the CRC- ER. The values given SHOULD include: time period of test in s, test VPI/VCI value, total number of cells transmitted and received on the given VPI/VCI during the test in positive integers, and the CRC-ER for the entire test. The graph results SHOULD display the CRC Error ratio values. The x-coordinate SHOULD be the test run time in either seconds, minutes or days depending on the total length of the test. The x-coordinate time SHOULD be configurable. The y-coordinate SHOULD be the CRC-ER. The integration time per point MUST be indicated.
Top   ToC   RFC3116 - Page 63
      The results MUST also indicate the packet size in octets, traffic
      rate in packets per second, and bearer class as generated by the
      test device.  The VCC and VPI/VCI values MUST be indicated.  The
      PCR, SCR, and MBS MUST be indicated.  The bearer class of the
      created VCC MUST also be indicated.

3.2.5.2. CRC-ER/Steady Load/Twelve VCCs
Objective: To determine the SUT ratio of lost cells on twelve VCCs in a transmission in relation to the total cells sent as defined in RFC 2761 "Terminology for ATM Benchmarking". Procedure: 1) Set up the SUT and test device using the bi-directional configuration. 2) Configure the SUT and test device with twelve VCCs, using 1 VPI and 12 VCIs. The VCC's MUST be configured as either a CBR, VBR, or UBR connection. The VPI/VCIs MUST not be one of the reserved ATM signaling channels (e.g., [0,5], [0,16]). 3) Send a specific number of IP packets at a specific constant rate through the SUT via the defined test VCCs. All of the VPI/VCI pairs will generate traffic at the same traffic rate. Since this test is not a throughput test, the rate should not be greater than 90% of line rate. The IP PDUs MUST be encapsulated in AAL5. 4) Count the IP packets that are transmitted by the SUT on all VCCs to verify connectivity and load. If the count on the test device is the same on the SUT, continue the test; else lower the test device traffic rate until the counts are the same. 5) Record the number of CRC errored cells received per VCC on the test device. Reporting Format: The results of the CRC-ER/Steady Load/Twelve VCCs test SHOULD be reported in a form of text and graph. The text results SHOULD display the numerical values of the CRC- ER. The values given SHOULD include: time period of test in s, test VPI/VCI value, total number of cells transmitted and received on the given VPI/VCI during the test in positive integers, and the CRC-ER for the entire test.
Top   ToC   RFC3116 - Page 64
      The graph results SHOULD display the CRC Error ratio values.  The
      x-coordinate SHOULD be the test run time in either seconds,
      minutes or days depending on the total length of the test.  The
      x-coordinate time SHOULD be configurable.  The y-coordinate SHOULD
      be the CRC-ER for each VCC.  There should be 12 curves on the
      graph, on curve indicated and labeled for each VCC.  The
      integration time per point MUST be indicated.

      The results MUST also indicate the packet size in octets, traffic
      rate in packets per second, and bearer class as generated by the
      test device.  The VCC and VPI/VCI values MUST be indicated.  The
      PCR, SCR, and MBS MUST be indicated.  The bearer class of the
      created VCC MUST also be indicated.

3.2.5.3. CRC-ER/Steady Load/Maximum VCCs
Objective: To determine the SUT ratio of lost cells with the maximum number VCCs supported on the SUT in a transmission in relation to the total cells sent as defined in RFC 2761 "Terminology for ATM Benchmarking". Procedure: 1) Set up the SUT and test device using the bi-directional configuration. 2) Configure the SUT and test device with the maximum number of VCCs supported on the SUT. For example, if the maximum number of VCCs supported on the SUT is 1024, define 256 VPIs with 4 VCIs per VPI. The VCC's MUST be configured as either a CBR, VBR, or UBR connection. The VPI/VCIs MUST not be one of the reserved ATM signaling channels (e.g., [0,5], [0,16]). 3) Send a specific number of IP packets at a specific constant rate through the SUT via the defined test VCCs. All of the VPI/VCI pairs will generate traffic at the same traffic rate. Since this test is not a throughput test, the rate should not be greater than 90% of line rate. The IP PDUs MUST be encapsulated in AAL5. 4) Count the IP packets that are transmitted by the SUT on all VCCs to verify connectivity and load. If the count on the test device is the same on the SUT, continue the test; else lower the test device traffic rate until the counts are the same. 5) Record the number of CRC errored cells received per VCC on the test device.
Top   ToC   RFC3116 - Page 65
   Reporting Format:

      The results of the CRC-ER/Steady Load/Maximum VCCs test SHOULD be
      reported in a form of text and graph.

      The text results SHOULD display the numerical values of the CRC-
      ER.  The values given SHOULD include: time period of test in s,
      test VPI/VCI value, total number of cells transmitted and received
      on the given VPI/VCI during the test in positive integers, and the
      CRC-ER for the entire test.

      The graph results SHOULD display the CRC Error ratio values.
      There will be (Max number of VCCs/10) graphs, with 10 VCCs
      indicated on each graph.  The x-coordinate SHOULD be the test run
      time in either seconds, minutes or days depending on the total
      length of the test.  The x-coordinate time SHOULD be configurable.
      The y-coordinate SHOULD be the CRC-ER for each VCC.  There SHOULD
      be no more than 10 curves on each graph, one curve indicated and
      labeled for each VCC.  The integration time per point MUST be
      indicated.

      The results MUST also indicate the packet size in octets, traffic
      rate in packets per second, and bearer class as generated by the
      test device.  The VCC and VPI/VCI values MUST be indicated.  The
      PCR, SCR, and MBS MUST be indicated.  The bearer class of the
      created VCC MUST also be indicated.

3.2.5.4. CRC-ER/Bursty VBR Load/One VCC
Objective: To determine the SUT ratio of lost cells on one VCC in a transmission in relation to the total cells sent as defined in RFC 2761 "Terminology for ATM Benchmarking". Procedure: 1) Set up the SUT and test device using the bi-directional configuration. 2) Configure the SUT and test device with one VCC. The VCC SHOULD contain one VPI/VCI. The VCC MUST be configured as either a CBR or VBR connection. The VPI/VCI MUST not be one of the reserved ATM signaling channels (e.g., [0,5], [0,16]). The PCR, SCR, and MBS must be configured using one of the specified traffic descriptors. 3) Send a specific number of IP packets containing one of the specified bit patterns at a specific rate through the SUT via the defined test VCC. Since this test is not a throughput test, the
Top   ToC   RFC3116 - Page 66
       rate should not be greater than 90% of line rate.  The IP PDUs
       MUST be encapsulated in AAL5.

   4)  Count the IP packets that are transmitted by the SUT to verify
       connectivity and load.  If the count on the test device is the
       same on the SUT, continue the test; else lower the test device
       traffic rate until the counts are the same.

   5)  Record the number of CRC errored cells received per VCC on the
       test device.

   Reporting Format:

      The results of the CRC-ER/Bursty VBR Load/One VCC test SHOULD be
      reported in a form of text and graph.

      The text results SHOULD display the numerical values of the CRC-
      ER.  The values given SHOULD include: time period of test in s,
      test VPI/VCI value, total number of cells transmitted and received
      on the given VPI/VCI during the test in positive integers, and the
      CRC-ER for the entire test.

      The graph results SHOULD display the CRC Error ratio values.  The
      x-coordinate SHOULD be the test run time in either seconds,
      minutes or days depending on the total length of the test.  The
      x-coordinate time SHOULD be configurable.  The y-coordinate SHOULD
      be the CRC-ER.  The integration time per point MUST be indicated.

      The results MUST also indicate the packet size in octets, traffic
      rate in packets per second, and bearer class as generated by the
      test device.  The VCC and VPI/VCI values MUST be indicated.  The
      PCR, SCR, and MBS MUST be indicated.  The bearer class of the
      created VCC MUST also be indicated.

3.2.5.5. CRC-ER/Bursty VBR Load/Twelve VCCs
Objective: To determine the SUT ratio of lost cells on twelve VCCs in a transmission in relation to the total cells sent as defined in RFC 2761 "Terminology for ATM Benchmarking". Procedure: 1) Set up the SUT and test device using the bi-directional configuration. 2) Configure the SUT and test device with twelve VCCs, using 1 VPI and 12 VCIs. The VCC MUST be configured as either a CBR or VBR connection. The VPI/VCIs MUST not be one of the reserved ATM
Top   ToC   RFC3116 - Page 67
       signaling channels (e.g., [0,5], [0,16]).  The PCR, SCR, and MBS
       must be configured using one of the specified traffic
       descriptors.

   3)  Send a specific number of IP packets containing one of the
       specified bit patterns at a specific rate through the SUT via the
       defined test VCCs.  All of the VPI/VCI pairs will generate
       traffic at the same traffic rate.  Since this test is not a
       throughput test, the rate should not be greater than 90% of line
       rate.  The PCR, SCR, and MBS must be indicated.  The IP PDUs MUST
       be encapsulated in AAL5.

   4)  Count the IP packets that are transmitted by the SUT on all VCCs
       to verify connectivity and load.  If the count on the test device
       is the same on the SUT, continue the test; else lower the test
       device traffic rate until the counts are the same.

   5)  Record the number of CRC errored cells received per VCC on the
       test device for all VCCs.

   Reporting Format:

      The results of the CRC-ER/Bursty VBR Load/Twelve VCCs test SHOULD
      be reported in a form of text and graph.

      The text results SHOULD display the numerical values of the CRC-
      ER.  The values given SHOULD include: time period of test in s,
      test VPI/VCI value, total number of cells transmitted and received
      on the given VPI/VCI during the test in positive integers, and the
      CRC-ER for the entire test.

      The graph results SHOULD display the CRC Error ratio values.  The
      x-coordinate SHOULD be the test run time in either seconds,
      minutes or days depending on the total length of the test.  The
      x-coordinate time SHOULD be configurable.  The y-coordinate SHOULD
      be the CRC-ER for each VCC.  There should be 12 curves on the
      graph, on curve indicated and labeled for each VCC.  The
      integration time per point MUST be indicated.

      The results MUST also indicate the packet size in octets, traffic
      rate in packets per second, and bearer class as generated by the
      test device.  The VCC and VPI/VCI values MUST be indicated.  The
      PCR, SCR, and MBS MUST be indicated.  The bearer class of the
      created VCC MUST also be indicated.
Top   ToC   RFC3116 - Page 68
3.2.5.6. CRC-ER/Bursty VBR Load/Maximum VCCs
Objective: To determine the SUT ratio of lost cells with the maximum number VCCs supported on the SUT in a transmission in relation to the total cells sent as defined in RFC 2761 "Terminology for ATM Benchmarking". Procedure: 1) Set up the SUT and test device using the bi-directional configuration. 2) Configure the SUT and test device with the maximum number of VCCs supported on the SUT. For example, if the maximum number of VCCs supported on the SUT is 1024, define 256 VPIs with 4 VCIs per VPI. The VCC MUST be configured as either a CBR or VBR connection. The VPI/VCIs MUST not be one of the reserved ATM signaling channels (e.g., [0,5], [0,16]). The PCR, SCR, and MBS must be configured using one of the specified traffic descriptors. 3) Send a specific number of IP packets containing one of the specified bit patterns at a specific rate through the SUT via the defined test VCCs. All of the VPI/VCI pairs will generate traffic at the same traffic rate. Since this test is not a throughput test, the rate should not be greater than 90% of line rate. The IP PDUs MUST be encapsulated in AAL5. 4) Count the IP packets that are transmitted by the SUT on all VCCs to verify connectivity and load. If the count on the test device is the same on the SUT, continue the test; else lower the test device traffic rate until the counts are the same. 5) Record the number of CRC errored cells received per VCC on the test device for all VCCs. Reporting Format: The results of the CRC-ER/Bursty VBR Load/Maximum VCCs test SHOULD be reported in a form of text and graph. The text results SHOULD display the numerical values of the CRC- ER. The values given SHOULD include: time period of test in s, test VPI/VCI value, total number of cells transmitted and received on the given VPI/VCI during the test in positive integers, and the CRC-ER for the entire test. The graph results SHOULD display the CRC Error ratio values.
Top   ToC   RFC3116 - Page 69
      There will be (Max number of VCCs/10) graphs, with 10 VCCs
      indicated on each graph.  The x-coordinate SHOULD be the test run
      time in either seconds, minutes or days depending on the total
      length of the test.  The x-coordinate time SHOULD be configurable.
      The y-coordinate SHOULD be the CRC-ER for each VCC.  There SHOULD
      be no more than 10 curves on each graph, one curve indicated and
      labeled for each VCC.  The integration time per point MUST be
      indicated.

      The results MUST also indicate the packet size in octets, traffic
      rate in packets per second, and bearer class as generated by the
      test device.  The VCC and VPI/VCI values MUST be indicated.  The
      PCR, SCR, and MBS MUST be indicated.  The bearer class of the
      created VCC MUST also be indicated.

3.2.5.7. CRC-ER/Bursty UBR Load/One VCC
Objective: To determine the SUT ratio of lost cells on one VCC in a transmission in relation to the total cells sent as defined in RFC 2761 "Terminology for ATM Benchmarking". Procedure: 1) Set up the SUT and test device using the bi-directional configuration. 2) Configure the SUT and test device with one VCC. The VCC SHOULD contain one VPI/VCI. The VCC MUST be configured as a UBR connection. The VPI/VCI MUST not be one of the reserved ATM signaling channels (e.g., [0,5], [0,16]). The PCR, SCR, and MBS must be configured using one of the specified traffic descriptors. 3) Send a specific number of IP packets containing one of the specified bit patterns at a specific rate through the SUT via the defined test VCC. Since this test is not a throughput test, the rate should not be greater than 90% of line rate. The IP PDUs MUST be encapsulated in AAL5. 4) Count the IP packets that are transmitted by the SUT to verify connectivity and load. If the count on the test device is the same on the SUT, continue the test; else lower the test device traffic rate until the counts are the same. 5) Record the number of CRC errored cells received per VCC on the test device.
Top   ToC   RFC3116 - Page 70
   Reporting Format:

      The results of the CRC-ER/Bursty UBR Load/One VCC test SHOULD be
      reported in a form of text and graph.

      The text results SHOULD display the numerical values of the CRC-
      ER.  The values given SHOULD include: time period of test in s,
      test VPI/VCI value, total number of cells transmitted and received
      on the given VPI/VCI during the test in positive integers, and the
      CRC-ER for the entire test.

      The graph results SHOULD display the CRC Error ratio values.  The
      x-coordinate SHOULD be the test run time in either seconds,
      minutes or days depending on the total length of the test.  The
      x-coordinate time SHOULD be configurable.  The y-coordinate SHOULD
      be the CRC-ER.  The integration time per point MUST be indicated.

      The results MUST also indicate the packet size in octets, traffic
      rate in packets per second, and bearer class as generated by the
      test device.  The VCC and VPI/VCI values MUST be indicated.  The
      PCR, SCR, and MBS MUST be indicated.  The bearer class of the
      created VCC MUST also be indicated.

3.2.5.8. CRC-ER/Bursty UBR Load/Twelve VCCs
Objective: To determine the SUT ratio of lost cells on twelve VCCs in a transmission in relation to the total cells sent as defined in RFC 2761 "Terminology for ATM Benchmarking". Procedure: 1) Set up the SUT and test device using the bi-directional configuration. 2) Configure the SUT and test device with twelve VCCs, using 1 VPI and 12 VCIs. The VCC MUST be configured as a UBR connection. The VPI/VCIs MUST not be one of the reserved ATM signaling channels (e.g., [0,5], [0,16]). The PCR, SCR, and MBS must be configured using one of the specified traffic descriptors. 3) Send a specific number of IP packets containing one of the specified bit patterns at a specific rate through the SUT via the defined test VCCs. All of the VPI/VCI pairs will generate traffic at the same traffic rate. Since this test is not a throughput test, the rate should not be greater than 90% of line rate. The PCR, SCR, and MBS must be indicated. The IP PDUs MUST be encapsulated in AAL5.
Top   ToC   RFC3116 - Page 71
   4)  Count the IP packets that are transmitted by the SUT on all VCCs
       to verify connectivity and load.  If the count on the test device
       is the same on the SUT, continue the test; else lower the test
       device traffic rate until the counts are the same.

   5)  Record the number of CRC errored cells received per VCC on the
       test device for all VCCs.

   Reporting Format:

      The results of the CRC-ER/Bursty UBR Load/Twelve VCCs test SHOULD
      be reported in a form of text and graph.

      The text results SHOULD display the numerical values of the CRC-
      ER.  The values given SHOULD include: time period of test in s,
      test VPI/VCI value, total number of cells transmitted and received
      on the given VPI/VCI during the test in positive integers, and the
      CRC-ER for the entire test.

      The graph results SHOULD display the CRC Error ratio values.  The
      x-coordinate SHOULD be the test run time in either seconds,
      minutes or days depending on the total length of the test.  The
      x-coordinate time SHOULD be configurable.  The y-coordinate SHOULD
      be the CRC-ER for each VCC.  There should be 12 curves on the
      graph, on curve indicated and labeled for each VCC.  The
      integration time per point MUST be indicated.

      The results MUST also indicate the packet size in octets, traffic
      rate in packets per second, and bearer class as generated by the
      test device.  The VCC and VPI/VCI values MUST be indicated.  The
      PCR, SCR, and MBS MUST be indicated.  The bearer class of the
      created VCC MUST also be indicated.

3.2.5.9. CRC-ER/Bursty UBR Load/Maximum VCCs
Objective: To determine the SUT ratio of lost cells with the maximum number VCCs supported on the SUT in a transmission in relation to the total cells sent as defined in RFC 2761 "Terminology for ATM Benchmarking". Procedure: 1) Set up the SUT and test device using the bi-directional configuration. 2) Configure the SUT and test device with the maximum number of VCCs supported on the SUT. For example, if the maximum number of VCCs supported on the SUT is 1024, define 256 VPIs with 4 VCIs per
Top   ToC   RFC3116 - Page 72
       VPI.  The VCC MUST be configured as a UBR connection.  The
       VPI/VCIs MUST not be one of the reserved ATM signaling channels
       (e.g., [0,5], [0,16]).  The PCR, SCR, and MBS must be configured
       using one of the specified traffic descriptors.

   3)  Send a specific number of IP packets containing one of the
       specified bit patterns at a specific rate through the SUT via the
       defined test VCCs.  All of the VPI/VCI pairs will generate
       traffic at the same traffic rate.  Since this test is not a
       throughput test, the rate should not be greater than 90% of line
       rate.  The IP PDUs MUST be encapsulated in AAL5.

   4)  Count the IP packets that are transmitted by the SUT on all VCCs
       to verify connectivity and load.  If the count on the test device
       is the same on the SUT, continue the test; else lower the test
       device traffic rate until the counts are the same.

   5)  Record the number of CRC errored cells received per VCC on the
       test device for all VCCs.

   Reporting Format:

      The results of the CRC-ER/Bursty UBR Load/Maximum VCCs test SHOULD
      be reported in a form of text and graph.

      The text results SHOULD display the numerical values of the CRC-
      ER.  The values given SHOULD include: time period of test in s,
      test VPI/VCI value, total number of cells transmitted and received
      on the given VPI/VCI during the test in positive integers, and the
      CRC-ER for the entire test.

      The graph results SHOULD display the CRC Error ratio values.
      There will be (Max number of VCCs/10) graphs, with 10 VCCs
      indicated on each graph.  The x-coordinate SHOULD be the test run
      time in either seconds, minutes or days depending on the total
      length of the test.  The x-coordinate time SHOULD be configurable.
      The y-coordinate SHOULD be the CRC-ER for each VCC.  There SHOULD
      be no more than 10 curves on each graph, one curve indicated and
      labeled for each VCC.  The integration time per point MUST be
      indicated.

      The results MUST also indicate the packet size in octets, traffic
      rate in packets per second, and bearer class as generated by the
      test device.  The VCC and VPI/VCI values MUST be indicated.  The
      PCR, SCR, and MBS MUST be indicated.  The bearer class of the
      created VCC MUST also be indicated.
Top   ToC   RFC3116 - Page 73
3.2.5.10. CRC-ER/Bursty Mixed Load/Three VCC
Objective: To determine the SUT ratio of lost cells on three VCC's in relation to the total cells sent as defined in RFC 2761 "Terminology for ATM Benchmarking". Procedure: 1) Set up the SUT and test device using the bi-directional configuration. 2) Configure the SUT and test device with three VCC's. Each VCC MUST be defined as a different Bearer class; one CBR, one UBR and one VBR. Each VCC SHOULD contain one VPI/VCI. The VPI/VCI MUST not be one of the reserved ATM signaling channels (e.g., [0,5], [0,16]). The PCR, SCR, and MBS must be configured using one of the specified traffic descriptors. 3) Send a specific number of IP packets containing one of the specified bit patterns through the SUT via the defined test VCCs. Each generated VCC stream MUST match the corresponding VCC Bearer class. All of the VPI/VCI pairs will generate traffic at the same traffic rate. Since this test is not a throughput test, the rate should not be greater than 90% of line rate. The IP PDUs MUST be encapsulated in AAL5. 4) Count the IP packets that are transmitted by the SUT to verify connectivity and load. If the count on the test device is the same on the SUT, continue the test; else lower the test device traffic rate until the counts are the same. 5) Record the number of CRC errored cells received per VCC on the test device. Reporting Format: The results of the CRC-ER/Bursty Mixed Load/Three VCC test SHOULD be reported in in a form of text and graph. The text results SHOULD display the numerical values of the CRC- ER. The values given SHOULD include: time period of test in s, test VPI/VCI value, total number of cells transmitted and received on the given VPI/VCI during the test in positive integers, and the CRC-ER for the entire test. The graph results SHOULD display the CRC Error ratio values. The x-coordinate SHOULD be the test run time in either seconds, minutes or days depending on the total length of the test. The
Top   ToC   RFC3116 - Page 74
      x-coordinate time SHOULD be configurable.  The y-coordinate SHOULD
      be the CRC-ER for each VCC.  There should be 12 curves on the
      graph, on curve indicated and labeled for each VCC.  The
      integration time per point MUST be indicated.

      The results MUST also indicate the packet size in octets, traffic
      rate in packets per second, and bearer class as generated by the
      test device.  The VCC and VPI/VCI values MUST be indicated.  The
      PCR, SCR, and MBS MUST be indicated.  The bearer class of the
      created VCC MUST also be indicated.

3.2.5.11. CRC-ER/Bursty Mixed Load/Twelve VCCs
Objective: To determine the SUT ratio of lost cells on twelve VCCs in a transmission in relation to the total cells sent as defined in RFC 2761 "Terminology for ATM Benchmarking". Procedure: 1) Set up the SUT and test device using the bi-directional configuration. 2) Configure the SUT and test device with twelve VCC's. Each VCC MUST be defined as one of the Bearer classes for a total of four CBR, four UBR and four VBR VCC's. Each VCC SHOULD contain one VPI/VCI. The VPI/VCI MUST not be one of the reserved ATM signaling channels (e.g., [0,5], [0,16]). 3) Send a specific number of IP packets containing one of the specified bit patterns through the SUT via the defined test VCCs. Each generated VCC stream MUST match the corresponding VCC Bearer class. All of the VPI/VCI pairs will generate traffic at the same traffic rate. Since this test is not a throughput test, the rate should not be greater than 90% of line rate. The IP PDUs MUST be encapsulated in AAL5. 4) Count the IP packets that are transmitted by the SUT on all VCCs to verify connectivity and load. If the count on the test device is the same on the SUT, continue the test; else lower the test device traffic rate until the counts are the same. 5) Record the number of CRC errored cells received per VCC on the test device for all VCCs. Reporting Format: The results of the CRC-ER/Bursty Mixed Load/Twelve VCCs test SHOULD be reported in a form of text and graph.
Top   ToC   RFC3116 - Page 75
      The text results SHOULD display the numerical values of the CRC-
      ER.  The values given SHOULD include: time period of test in s,
      test VPI/VCI value, total number of cells transmitted and received
      on the given VPI/VCI during the test in positive integers, and the
      CRC-ER for the entire test.

      The graph results SHOULD display the CRC Error ratio values.  The
      x-coordinate SHOULD be the test run time in either seconds,
      minutes or days depending on  the total length of the test.  The
      x-coordinate time SHOULD be configurable.  The y-coordinate SHOULD
      be the CRC-ER for each VCC.  There should be 12 curves on the
      graph, on curve indicated and labeled for each VCC.  The
      integration time per point MUST be indicated.

      The results MUST also indicate the packet size in octets, traffic
      rate in packets per second, and bearer class as generated by the
      test device.  The VCC and VPI/VCI values MUST be indicated.  The
      PCR, SCR, and MBS MUST be indicated.  The bearer class of the
      created VCC MUST also be indicated.

3.2.5.12. CRC-ER/Bursty Mixed Load/Maximum VCCs
Objective: To determine the SUT ratio of lost cells with the maximum number VCCs supported on the SUT in a transmission in relation to the total cells sent as defined in RFC 2761 "Terminology for ATM Benchmarking". Procedure: 1) Set up the SUT and test device using the bi-directional configuration. 2) Configure the SUT and test device with maximum number of VCCs supported on the SUT. For example, if the maximum number of VCCs supported on the SUT is 1024, define 256 VPIs with 4 VCIs per VPI. Each VCC MUST be defined as one of the Bearer classes for a total of (max VCC/3) CBR, (max VCC/3) UBR and (max VCC/3) VBR VCC's. The VPI/VCI MUST not be one of the reserved ATM signaling channels (e.g., [0,5], [0,16]). 3) Send a specific number of IP packets containing one of the specified bit patterns through the SUT via the defined test VCCs. Each generated VCC stream MUST match the corresponding VCC Bearer class. All of the VPI/VCI pairs will generate traffic at the same traffic rate. Since this test is not a throughput test, the rate should not be greater than 90% of line rate. The IP PDUs MUST be encapsulated in AAL5.
Top   ToC   RFC3116 - Page 76
   4)  Count the IP packets that are transmitted by the SUT on all VCCs
       to verify connectivity and load.  If the count on the test device
       is the same on the SUT, continue the test; else lower the test
       device traffic rate until the counts are the same.

   5)  Record the number of CRC errored cells received per VCC on the
       test device for all VCCs.

   Reporting Format:

      The results of the CRC-ER/Bursty Mixed Load/Maximum VCCs test
      SHOULD be reported in a form of text and graph.

      The text results SHOULD display the numerical values of the CRC-
      ER.  The values given SHOULD include: time period of test in s,
      test VPI/VCI value, total number of cells transmitted and received
      on the given VPI/VCI during the test in positive integers, and the
      CRC-ER for the entire test.

      The graph results SHOULD display the CRC Error ratio values.
      There will be (Max number of VCCs/10) graphs, with 10 VCCs
      indicated on each graph.  The x-coordinate SHOULD be the test run
      time in either seconds, minutes or days depending on the total
      length of the test.  The x-coordinate time SHOULD be configurable.
      The y-coordinate SHOULD be the CRC-ER for each VCC.  There SHOULD
      be no more than 10 curves on each graph, one curve indicated and
      labeled for each VCC.  The integration time per point MUST be
      indicated.

      The results MUST also indicate the packet size in octets, traffic
      rate in packets per second, and bearer class as generated by the
      test device.  The VCC and VPI/VCI values MUST be indicated.  The
      PCR, SCR, and MBS MUST be indicated.  The bearer class of the
      created VCC MUST also be indicated.



(page 76 continued on part 4)

Next Section