draft-ietf-bmwg-atm-method-00.txt   draft-ietf-bmwg-atm-method-01.txt 
Network Working Group J. H. Dunn Network Working Group J. H. Dunn
INTERNET-DRAFT C. E. Martin INTERNET-DRAFT C. E. Martin
Expires: April, 2000 ANC, Inc. Expires: September, 2000 ANC, Inc.
October, 1999 March, 2000
Methodology for ATM Benchmarking Methodology for ATM Benchmarking
<draft-ietf-bmwg-atm-method-00.txt> <draft-ietf-bmwg-atm-method-01.txt>
Status of this Memo Status of this Memo
This document is an Internet-Draft and is in full conformance with all This document is an Internet-Draft and is in full conformance with all
provisions of Section 10 of RFC2026. Internet-Drafts are working provisions of Section 10 of RFC2026. Internet-Drafts are working
documents of the Internet Engineering Task Force (IETF), its areas, and documents of the Internet Engineering Task Force (IETF), its areas, and
its working groups. Note that other groups may also distribute working its working groups. Note that other groups may also distribute working
documents as Internet-Drafts. documents as Internet-Drafts.
Internet-Drafts are draft documents valid for a maximum of six months Internet-Drafts are draft documents valid for a maximum of six months
skipping to change at page 2, line 10 skipping to change at page 2, line 17
1. Introduction. 1. Introduction.
This document defines a specific set of tests that vendors can use to This document defines a specific set of tests that vendors can use to
measure and report the performance characteristics of ATM network measure and report the performance characteristics of ATM network
devices. The results of these tests will provide the user comparable devices. The results of these tests will provide the user comparable
data from different vendors with which to evaluate these devices. The data from different vendors with which to evaluate these devices. The
methods defined in this memo are based on RFC 2544 "Benchmarking methods defined in this memo are based on RFC 2544 "Benchmarking
Methodology for Network Interconnect Devices". Methodology for Network Interconnect Devices".
The document "Terminology for ATM Benchmarking" (draft-ietf-bmwg-atm- The document "Terminology for ATM Benchmarking" (RFC 2761), defines many
term- 01.txt), defines many of the terms that are used in this document. of the terms that are used in this document. The terminology document
The terminology document should be consulted before attempting to make should be consulted before attempting to make use of this document.
use of this document.
The BMWG produces two major classes of documents: Benchmarking The BMWG produces two major classes of documents: Benchmarking
Terminology documents and Benchmarking Methodology documents. The Terminology documents and Benchmarking Methodology documents. The
Terminology documents present the benchmarks and other related terms. Terminology documents present the benchmarks and other related terms.
The Methodology documents define the procedures required to collect the The Methodology documents define the procedures required to collect the
benchmarks cited in the corresponding Terminology documents. benchmarks cited in the corresponding Terminology documents.
2. Background 2. Background
2.1. Test Device Requirements 2.1. Test Device Requirements
skipping to change at page 12, line 34 skipping to change at page 14, line 12
A list of maximum IP PDU rates for LAN connections is included in A list of maximum IP PDU rates for LAN connections is included in
Appendix B. Appendix B.
2.20. Bursty traffic 2.20. Bursty traffic
It is convenient to measure the SUT performance under steady state load; It is convenient to measure the SUT performance under steady state load;
however, this is an unrealistic way to gauge the functioning of a SUT. however, this is an unrealistic way to gauge the functioning of a SUT.
Actual network traffic normally consists of bursts of IP PDUs. Actual network traffic normally consists of bursts of IP PDUs.
Some of the tests described below SHOULD be performed with both constant Some of the tests described below SHOULD be performed with both constant
bit rate and bursty traffic. The IP PDUs within a burst are transmitted bit rate, bursty Unspecified Bit Rate (UBR) Best Effort [AF-TM4.0] and
with the minimum legitimate inter-IP PDU gap. Variable Bit Rate Non-real Time (VBR-nrt) Best Effort [AF-TM4.0]. The
IP PDUs within a burst are transmitted with the minimum legitimate
inter-IP PDU gap.
The objective of the test is to determine the minimum interval between The objective of the test is to determine the minimum interval between
bursts that the SUT can process with no IP PDU loss. Tests SHOULD be bursts that the SUT can process with no IP PDU loss. Tests SHOULD be
run with burst sizes of 10% of Maximum Burst Size (MBS), 20% of MBS, 50% run with burst sizes of 10% of Maximum Burst Size (MBS), 20% of MBS, 50%
of MBS and 100% MBS. Note that the number of IP PDUs in each burst will of MBS and 100% MBS. Note that the number of IP PDUs in each burst will
depend on the PDU size. depend on the PDU size. For UBR, the MBS refers to the associated VBR
traffic parameters.
2.21. Trial description 2.21. Trial description
A particular test consists of multiple trials. Each trial returns one A particular test consists of multiple trials. Each trial returns one
piece of information, for example the loss rate at a particular input IP piece of information, for example the loss rate at a particular input IP
PDU rate. Each trial consists of five of phases: PDU rate. Each trial consists of five of phases:
a) If the SUT is a switch supporting PNNI, send the routing update to a) If the SUT is a switch supporting PNNI, send the routing update to
the SUT receive port and wait two seconds to be sure that the routing the SUT receive port and wait two seconds to be sure that the routing
has settled. has settled.
skipping to change at page 14, line 24 skipping to change at page 16, line 18
3. Performance Metrics 3. Performance Metrics
3.1. Physical Layer- SONET 3.1. Physical Layer- SONET
3.1.1. Pointer Movements 3.1.1. Pointer Movements
3.1.1.1. Pointer Movement Propagation. 3.1.1.1. Pointer Movement Propagation.
Objective: To determine that the SUT does not propagate pointer movements Objective: To determine that the SUT does not propagate pointer movements
as defined in "Terminology for ATM Benchmarking". as defined in RFC 2761 "Terminology for ATM Benchmarking".
Procedure: Procedure:
1) Set up the SUT and test device using the uni-directional 1) Set up the SUT and test device using the uni-directional
configuration. configuration.
2) Send a specific number of IP PDUs at a specific rate through the SUT. 2) Send a specific number of IP PDUs at a specific rate through the SUT.
Since this test is not a throughput test, the rate should not be greater Since this test is not a throughput test, the rate should not be greater
than 90% of line rate. The cell payload SHOULD contain valid IP PDUs. than 90% of line rate. The cell payload SHOULD contain valid IP PDUs.
The IP PDUs MUST be encapsulated in AAL5. The IP PDUs MUST be encapsulated in AAL5.
skipping to change at page 15, line 36 skipping to change at page 17, line 36
per second. The columns SHOULD be labeled pointer movement and loss of per second. The columns SHOULD be labeled pointer movement and loss of
pointer. The elements of the table SHOULD be either True or False, pointer. The elements of the table SHOULD be either True or False,
indicating whether the particular condition was observed for each test. indicating whether the particular condition was observed for each test.
The table MUST also indicate the IP PDU size in octets and traffic rate The table MUST also indicate the IP PDU size in octets and traffic rate
in IP PDUs per second as generated by the test device. in IP PDUs per second as generated by the test device.
3.1.1.2. Cell Loss due to Pointer Movement. 3.1.1.2. Cell Loss due to Pointer Movement.
Objective: To determine if the SUT will drop cells due to pointer movements Objective: To determine if the SUT will drop cells due to pointer movements
as defined in "Terminology for ATM Benchmarking". as defined in RFC 2761 "Terminology for ATM Benchmarking".
Procedure: Procedure:
1) Set up the SUT and test device using the uni-directional 1) Set up the SUT and test device using the uni-directional
configuration. configuration.
2) Send a specific number of cells at a specific rate through the SUT. 2) Send a specific number of cells at a specific rate through the SUT.
Since this test is not a throughput test, the rate should not be greater Since this test is not a throughput test, the rate should not be greater
than 90% of line rate. The cell payload SHOULD contain valid IP PDUs. than 90% of line rate. The cell payload SHOULD contain valid IP PDUs.
The IP PDUs MUST be encapsulated in AAL5. The IP PDUs MUST be encapsulated in AAL5.
3) Count the cells that are transmitted by the SUT to verify 3) Count the cells that are transmitted by the SUT to verify
connectivity and load. If the count on the test device is the same on 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 the SUT, continue the test; else lower the test device traffic rate
until the counts are the same. until the counts are the same.
4) Inject one forward payload pointer movement. Verify that the SUT 4) Inject one forward payload pointer movement. Verify that the SUT
skipping to change at page 16, line 49 skipping to change at page 19, line 14
lost. The elements of column 1 SHOULD be either True or False, lost. The elements of column 1 SHOULD be either True or False,
indicating whether the particular condition was observed for each test. indicating whether the particular condition was observed for each test.
The elements of column 2 SHOULD be non-negative integers. The elements of column 2 SHOULD be non-negative integers.
The table MUST also indicate the traffic rate in IP PDUs per second as The table MUST also indicate the traffic rate in IP PDUs per second as
generated by the test device. generated by the test device.
3.1.1.3. IP Packet Loss due to Pointer Movement. 3.1.1.3. IP Packet Loss due to Pointer Movement.
Objective: To determine if the SUT will drop IP packets due to pointer Objective: To determine if the SUT will drop IP packets due to pointer
movements as defined in "Terminology for ATM Benchmarking". movements as defined in RFC 2761 "Terminology for ATM Benchmarking".
Procedure: Procedure:
1) Set up the SUT and test device using the uni-directional 1) Set up the SUT and test device using the uni-directional
configuration. configuration.
2) Send a specific number of IP packets at a specific rate through the 2) Send a specific number of IP packets at a specific rate through the
SUT. Since this test is not a throughput test, the rate should not be SUT. 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 greater than 90% of line rate. The IP PDUs MUST be encapsulated in
AAL5. AAL5.
skipping to change at page 18, line 16 skipping to change at page 20, line 34
The elements of column 2 SHOULD be non-negative integers. The elements of column 2 SHOULD be non-negative integers.
The table MUST also indicate the packet size in octets and traffic rate The table MUST also indicate the packet size in octets and traffic rate
in packets per second as generated by the test device. in packets per second as generated by the test device.
3.1.2. Transport Overhead (TOH) Error Count 3.1.2. Transport Overhead (TOH) Error Count
3.1.2.1. TOH Error Propagation. 3.1.2.1. TOH Error Propagation.
Objective: To determine that the SUT does not propagate TOH errors as Objective: To determine that the SUT does not propagate TOH errors as
defined in "Terminology for ATM Benchmarking". defined in RFC 2761 "Terminology for ATM Benchmarking".
Procedure: Procedure:
1) Set up the SUT and test device using the uni-directional 1) Set up the SUT and test device using the uni-directional
configuration. configuration.
2) Send a specific number of IP PDUs at a specific rate through the SUT. 2) Send a specific number of IP PDUs at a specific rate through the SUT.
Since this test is not a throughput test, the rate should not be greater Since this test is not a throughput test, the rate should not be greater
than 90% of line rate. The cell payload SHOULD contain valid IP PDUs. than 90% of line rate. The cell payload SHOULD contain valid IP PDUs.
The IP PDUs MUST be encapsulated in AAL5. The IP PDUs MUST be encapsulated in AAL5.
3) Count the IP PDUs that are transmitted by the SUT to verify 3) Count the IP PDUs that are transmitted by the SUT to verify
connectivity and load. If the count on the test device is the same on 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 the SUT, continue the test, else lower the test device traffic rate
until the counts are the same. until the counts are the same.
4) Inject one error in the first bit of the A1 and A2 Frameword. Verify 4) Inject one error in the first bit of the A1 and A2 Frameword. Verify
that the SUT does not propagate the error. that the SUT does not propagate the error.
5) Inject one error in the first bit of the A1 and A2 Frameword every 1 5) Inject one error in the first bit of the A1 and A2 Frameword every 1
second. Verify that the SUT does not propagate the error. 6) second. Verify that the SUT does not propagate the error.
Discontinue the Frameword error.
6) Discontinue the Frameword error.
7) Inject one error in the first bit of the A1 and A2 Frameword for 4 7) Inject one error in the first bit of the A1 and A2 Frameword for 4
consecutive IP PDUs in every 6 IP PDUs. Verify that the SUT indicates consecutive IP PDUs in every 6 IP PDUs. Verify that the SUT indicates
Loss of Frame. Loss of Frame.
8) Discontinue the Frameword error. 8) Discontinue the Frameword error.
Reporting Format: Reporting Format:
The results of the TOH error propagation test SHOULD be reported in a The results of the TOH error propagation test SHOULD be reported in a
skipping to change at page 19, line 14 skipping to change at page 21, line 39
be labeled error propagated and loss of IP PDU. The elements of the be labeled error propagated and loss of IP PDU. The elements of the
table SHOULD be either True or False, indicating whether the particular table SHOULD be either True or False, indicating whether the particular
condition was observed for each test. condition was observed for each test.
The table MUST also indicate the IP PDU size in octets and traffic rate The table MUST also indicate the IP PDU size in octets and traffic rate
in IP PDUs per second as generated by the test device. in IP PDUs per second as generated by the test device.
3.1.2.2. Cell Loss due to TOH Error. 3.1.2.2. Cell Loss due to TOH Error.
Objective: To determine if the SUT will drop cells due TOH Errors as Objective: To determine if the SUT will drop cells due TOH Errors as
defined in "Terminology for ATM Benchmarking". defined in RFC 2761 "Terminology for ATM Benchmarking".
Procedure: Procedure:
1) Set up the SUT and test device using the uni-directional 1) Set up the SUT and test device using the uni-directional
configuration. configuration.
2) Send a specific number of cells at a specific rate through the SUT. 2) Send a specific number of cells at a specific rate through the SUT.
Since this test is not a throughput test, the rate should not be greater Since this test is not a throughput test, the rate should not be greater
than 90% of line rate. The cell payload SHOULD contain valid IP PDUs. than 90% of line rate. The cell payload SHOULD contain valid IP PDUs.
The IP PDUs MUST be encapsulated in AAL5. The IP PDUs MUST be encapsulated in AAL5.
3) Count the cells that are transmitted by the SUT to verify 3) Count the cells that are transmitted by the SUT to verify
connectivity and load. If the count on the test device is the same on 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 the SUT, continue the test; else lower the test device traffic rate
until the counts are the same. until the counts are the same.
4) Inject one error in the first bit of the A1 and A2 Frameword. Verify 4) Inject one error in the first bit of the A1 and A2 Frameword. Verify
skipping to change at page 20, line 13 skipping to change at page 22, line 44
column 1 SHOULD be either True or False, indicating whether the column 1 SHOULD be either True or False, indicating whether the
particular condition was observed for each test. The elements of column particular condition was observed for each test. The elements of column
2 SHOULD be non-negative integers. 2 SHOULD be non-negative integers.
The table MUST also indicate the traffic rate in IP PDUs per second as The table MUST also indicate the traffic rate in IP PDUs per second as
generated by the test device. generated by the test device.
3.1.2.3. IP Packet Loss due to TOH Error. 3.1.2.3. IP Packet Loss due to TOH Error.
Objective: To determine if the SUT will drop IP packets due to TOH errors Objective: To determine if the SUT will drop IP packets due to TOH errors
as defined in "Terminology for ATM Benchmarking". as defined in RFC 2761 "Terminology for ATM Benchmarking".
Procedure: Procedure:
1) Set up the SUT and test device using the uni-directional 1) Set up the SUT and test device using the uni-directional
configuration. configuration.
2) Send a specific number of IP packets at a specific rate through the 2) Send a specific number of IP packets at a specific rate through the
SUT. Since this test is not a throughput test, the rate should not be SUT. 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 greater than 90% of line rate. The IP PDUs MUST be encapsulated in
AAL5. AAL5.
skipping to change at page 21, line 14 skipping to change at page 24, line 8
column 2 SHOULD be non-negative integers. column 2 SHOULD be non-negative integers.
The table MUST also indicate the packet size in octets and traffic rate The table MUST also indicate the packet size in octets and traffic rate
in packets per second as generated by the test device. in packets per second as generated by the test device.
3.1.3. Path Overhead (POH) Error Count 3.1.3. Path Overhead (POH) Error Count
3.1.3.1. POH Error Propagation. 3.1.3.1. POH Error Propagation.
Objective: To determine that the SUT does not propagate POH errors as Objective: To determine that the SUT does not propagate POH errors as
defined in "Terminology for ATM Benchmarking". defined in RFC 2761 "Terminology for ATM Benchmarking".
Procedure: Procedure:
1) Set up the SUT and test device using the uni-directional 1) Set up the SUT and test device using the uni-directional
configuration. configuration.
2) Send a specific number of IP PDUs at a specific rate through the SUT. 2) Send a specific number of IP PDUs at a specific rate through the SUT.
Since this test is not a throughput test, the rate should not be greater Since this test is not a throughput test, the rate should not be greater
than 90% of line rate. The cell payload SHOULD contain valid IP PDUs. than 90% of line rate. The cell payload SHOULD contain valid IP PDUs.
The IP PDUs MUST be encapsulated in AAL5. The IP PDUs MUST be encapsulated in AAL5.
skipping to change at page 22, line 6 skipping to change at page 25, line 6
per second. The columns SHOULD be labeled error propagated and loss of per second. The columns SHOULD be labeled error propagated and loss of
IP PDU. The elements of the table SHOULD be either True or False, IP PDU. The elements of the table SHOULD be either True or False,
indicating whether the particular condition was observed for each test. indicating whether the particular condition was observed for each test.
The table MUST also indicate the IP PDU size in octets and traffic rate The table MUST also indicate the IP PDU size in octets and traffic rate
in IP PDUs per second as generated by the test device. in IP PDUs per second as generated by the test device.
3.1.3.2. Cell Loss due to POH Error. 3.1.3.2. Cell Loss due to POH Error.
Objective: To determine if the SUT will drop cells due POH Errors as Objective: To determine if the SUT will drop cells due POH Errors as
defined in "Terminology for ATM Benchmarking". defined in RFC 2761 "Terminology for ATM Benchmarking".
Procedure: Procedure:
1) Set up the SUT and test device using the uni-directional 1) Set up the SUT and test device using the uni-directional
configuration. configuration.
2) Send a specific number of cells at a specific rate through the SUT. 2) Send a specific number of cells at a specific rate through the SUT.
Since this test is not a throughput test, the rate should not be greater Since this test is not a throughput test, the rate should not be greater
than 90% of line rate. The cell payload SHOULD contain valid IP PDUs. than 90% of line rate. The cell payload SHOULD contain valid IP PDUs.
The IP PDUs MUST be encapsulated in AAL5. The IP PDUs MUST be encapsulated in AAL5.
skipping to change at page 22, line 46 skipping to change at page 25, line 46
cells lost. The elements of column 1 SHOULD be either True or False, cells lost. The elements of column 1 SHOULD be either True or False,
indicating whether the particular condition was observed for each test. indicating whether the particular condition was observed for each test.
The elements of column 2 SHOULD be non-negative integers. The elements of column 2 SHOULD be non-negative integers.
The table MUST also indicate the traffic rate in IP PDUs per second as The table MUST also indicate the traffic rate in IP PDUs per second as
generated by the test device. generated by the test device.
3.1.3.3. IP Packet Loss due to POH Error. 3.1.3.3. IP Packet Loss due to POH Error.
Objective: To determine if the SUT will drop IP packets due to POH errors Objective: To determine if the SUT will drop IP packets due to POH errors
as defined in "Terminology for ATM Benchmarking". as defined in RFC 2761 "Terminology for ATM Benchmarking".
Procedure: Procedure:
1) Set up the SUT and test device using the uni-directional 1) Set up the SUT and test device using the uni-directional
configuration. configuration.
2) Send a specific number of IP packets at a specific rate through the 2) Send a specific number of IP packets at a specific rate through the
SUT. Since this test is not a throughput test, the rate should not be SUT. 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 greater than 90% of line rate. The IP PDUs MUST be encapsulated in
AAL5. AAL5.
skipping to change at page 23, line 44 skipping to change at page 27, line 6
3.2. ATM Layer 3.2. ATM Layer
3.2.1. Two-Point Cell Delay Variation (CDV) 3.2.1. Two-Point Cell Delay Variation (CDV)
3.2.1.1. Test Setup 3.2.1.1. Test Setup
The cell delay measurements assume that both the transmitter and The cell delay measurements assume that both the transmitter and
receiver timestamp information is synchronized. Synchronization SHOULD receiver timestamp information is synchronized. Synchronization SHOULD
be achieved by supplying a common clock signal (minimum of 100 Mhz or 10 be achieved by supplying a common clock signal (minimum of 100 Mhz or 10
nS resolution) to both the transmitter and receiver. The maximum ns resolution) to both the transmitter and receiver. The maximum
timestamp values MUST be recorded to ensure synchronization in the case timestamp values MUST be recorded to ensure synchronization in the case
of counter rollover. of counter rollover. The cell delay measurements SHOULD utilize the
O.191 cell (ITUT-O.191) encapsulated in a valid IP packet. If the O.191
cell is not available, a test cell encapsulated in a valid IP packet MAY
be used. The test cell MUST contain a transmit timestamp which can be
correlated with a receive timestamp. A description of the test cell MUST
be included in the test results. The description MUST include the
timestamp length (in bits), counter rollover value, and the timestamp
accuracy (in ns).
3.2.1.2. Two-point CDV/One VCC 3.2.1.2. Two-point CDV/Steady Load/One VCC
Objective: To determine the SUT variation in cell transfer delay with one Objective: To determine the SUT variation in cell transfer delay with one
VCC as defined in "Terminology for ATM Benchmarking". VCC as defined in RFC 2761 "Terminology for ATM Benchmarking".
Procedure: Procedure:
1) Set up the SUT and test device using the bi-directional 1) Set up the SUT and test device using the bi-directional
configuration. configuration.
2) Configure the SUT and test device with one VCC. The VCC SHOULD 2) Configure the SUT and test device with one VCC. The VCC SHOULD
contain one VPI/VCI. The VPI/VCI MUST not be one of the reserved 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]). signaling channels (e.g. [0,5], [0,16]).
3) Send a specific number of IP packets containing time stamps at a 3) Send a specific number of IP packets containing time stamps at a
specific rate through the SUT via the defined test VCC. Since this test 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 packets timestamps at the transmitter and receiver ends of
the test device.
Reporting Format:
The results of the Two-point CDV/Steady Load/One VCC test SHOULD be
reported in a form of text, graph, and histogram.
The text results SHOULD display the numerical values of the CDV. 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, maximum and minimum CDV
during the test in us, and peak-to-peak CDV in us.
The graph results SHOULD display the cell delay 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 cell delay in
us. The integration time per point MUST be indicated.
The histogram results SHOULD display the peak-to-peak cell delay. The
x- coordinate SHOULD be the cell delay in us with at least 256 bins.
The y- coordinate SHOULD be the number of cells observed in each bin.
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 bearer class of the
created VCC MUST also be indicated.
3.2.1.3. Two-point CDV/Steady Load/Twelve VCCs
Objective: To determine the SUT variation in cell transfer delay with
twelve VCCs 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 containing timestamps 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 packets timestamps at the transmitter and receiver ends of
the test device for all VCCs.
Reporting Format:
The results of the Two-point CDV/Steady Load/Twelve VCCs test SHOULD be
reported in a form of text, graph, and histograms.
The text results SHOULD display the numerical values of the CDV. The
values given SHOULD include: time period of test in s, test VPI/VCI
values, total number of cells transmitted and received on each VCC
during the test in positive integers, maximum and minimum CDV on each
VCC during the test in us, and peak-to-peak CDV on each VCC in us.
The graph results SHOULD display the cell delay 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 cell delay for
each VCC in ms. There SHOULD be 12 curves on the graph, one curves
indicated and labeled for each VCC. The integration time per point MUST
be indicated.
The histograms SHOULD display the peak-to-peak cell delay. There will be
one histogram for each VCC. The x-coordinate SHOULD be the cell delay
in us with at least 256 bins. The y-coordinate SHOULD be the number of
cells observed in each bin.
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 bearer class of the
created VCC MUST also be indicated.
3.2.1.4. Two-point CDV/Steady Load/Maximum VCCs
Objective: To determine the SUT variation in cell transfer delay with the
maximum number VCCs supported on the SUT 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 containing timestamps 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 packets timestamps at the transmitter and receiver ends of
the test device for all VCCs.
Reporting Format:
The results of the Two-point CDV/Steady Load/Maximum VCCs test SHOULD be
reported in a form of text, graphs, and histograms.
The text results SHOULD display the numerical values of the CDV. The
values given SHOULD include: time period of test in s, test VPI/VCI
values, total number of cells transmitted and received on each VCC
during the test in positive integers, maximum and minimum CDV on each
VCC during the test in us, and peak-to-peak CDV on each VCC in us.
The graph results SHOULD display the cell delay 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 cell delay for
each VCC in us. 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 histograms SHOULD display the peak-to-peak cell delay. There will be
one histogram for each VCC. The x-coordinate SHOULD be the cell delay in
us with at least 256 bins. The y-coordinate SHOULD be the number of
cells observed in each bin.
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 bearer class of the
created VCC MUST also be indicated.
3.2.1.5. Two-point CDV/Bursty VBR Load/One VCC
Objective: To determine the SUT variation in cell transfer delay with one
VCC 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]).
3) Send a specific number of IP packets containing timestamps at a
specific VBR 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 is not a throughput test, the rate should not be greater than 90% of
line rate. The IP PDUs MUST be encapsulated in AAL5. line rate. The IP PDUs MUST be encapsulated in AAL5.
4) Count the IP packets that are transmitted by the SUT to verify 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 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 the SUT, continue the test; else lower the test device traffic rate
until the counts are the same. 5) Record the packets timestamps at the until the counts are the same.
transmitter and receiver ends of the test device.
5) Record the packets timestamps at the transmitter and receiver ends of
the test device.
Reporting Format: Reporting Format:
The results of the Two-point CDV/One VCC test SHOULD be reported in a The results of the Two-point CDV/Bursty VBR Load/One VCC test SHOULD be
form of text, graph, and histogram. reported in a form of text, graph, and histogram.
The text results SHOULD display the numerical values of the CDV. The The text results SHOULD display the numerical values of the CDV. The
values given SHOULD include: time period of test in s, test VPI/VCI values given SHOULD include: time period of test in s, test VPI/VCI
value, total number of cells transmitted and received on the given value, total number of cells transmitted and received on the given
VPI/VCI during the test in positive integers, maximum and minimum CDV VPI/VCI during the test in positive integers, maximum and minimum CDV
during the test in us, and peak-to-peak CDV in us. during the test in us, and peak-to-peak CDV in us.
The graph results SHOULD display the cell delay values. The x- The graph results SHOULD display the cell delay values. The x-
coordinate SHOULD be the test run time in either seconds, minutes or 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 days depending on the total length of the test. The x-coordinate time
SHOULD be configurable. The y-coordinate SHOULD be the cell delay in SHOULD be configurable. The y-coordinate SHOULD be the cell delay in
us. The integration time per point MUST be indicated. us. The integration time per point MUST be indicated.
The histogram results SHOULD display the peak-to-peak cell delay. The The histogram results SHOULD display the peak-to-peak cell delay. The
x- coordinate SHOULD be the cell delay in us with at least 256 bins. x- coordinate SHOULD be the cell delay in us with at least 256 bins.
The y- coordinate SHOULD be the number of cells observed in each bin. The y- coordinate SHOULD be the number of cells observed in each bin.
The results MUST also indicate the packet size in octets and traffic The results MUST also indicate the packet size in octets, traffic rate
rate in packets per second as generated by the test device. The VCC and in packets per second, and bearer class as generated by the test device.
VPI/VCI values MUST also be indicated. 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.1.3. Two-point CDV/Twelve VCCs 3.2.1.6. Two-point CDV/Bursty VBR Load/Twelve VCCs
Objective: To determine the SUT variation in cell transfer delay with Objective: To determine the SUT variation in cell transfer delay with
twelve VCCs as defined in RFC 2761 "Terminology for ATM Benchmarking".
twelve VCCs as defined in "Terminology for ATM Benchmarking".
Procedure: Procedure:
1) Set up the SUT and test device using the bi-directional 1) Set up the SUT and test device using the bi-directional
configuration. configuration.
2) Configure the SUT and test device with twelve VCCs, using 1 VPI and 2) Configure the SUT and test device with twelve VCCs, using 1 VPI and
12 VCIs. The VPI/VCIs MUST not be one of the reserved signaling channels 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]). (e.g. [0,5], [0,16]).
3) Send a specific number of IP packets containing time stamps at a 3) Send a specific number of IP packets containing time stamps at a
specific rate through the SUT via the defined test VCCs. All of the specific VBR through the SUT via the defined test VCCs. All of the
VPI/VCI pairs will generate traffic at the same traffic rate. Since 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 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. 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 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 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 same on the SUT, continue the test; else lower the test device traffic
rate until the counts are the same. rate until the counts are the same.
5) Record the packets timestamps at the transmitter and receiver ends of 5) Record the packets timestamps at the transmitter and receiver ends of
the test device for all VCCs. the test device for all VCCs.
Reporting Format: Reporting Format:
The results of the Two-point CDV/Twelve VCCs test SHOULD be reported in The results of the Two-point CDV/Bursty VBR Load/Twelve VCCs test SHOULD
a form of text, graph, and histograms. be reported in a form of text, graph, and histograms.
The text results SHOULD display the numerical values of the CDV. The The text results SHOULD display the numerical values of the CDV. The
values given SHOULD include: time period of test in s, test VPI/VCI values given SHOULD include: time period of test in s, test VPI/VCI
values, total number of cells transmitted and received on each VCC values, total number of cells transmitted and received on each VCC
during the test in positive integers, maximum and minimum CDV on each during the test in positive integers, maximum and minimum CDV on each
VCC during the test in us, and peak-to-peak CDV on each VCC in us. VCC during the test in us, and peak-to-peak CDV on each VCC in us.
The graph results SHOULD display the cell delay values. The x- The graph results SHOULD display the cell delay values. The x-
coordinate SHOULD be the test run time in either seconds, minutes or 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 days depending on the total length of the test. The x-coordinate time
SHOULD be configurable. The y-coordinate SHOULD be the cell delay for SHOULD be configurable. The y-coordinate SHOULD be the cell delay for
each VCC in ms. There SHOULD be 12 curves on the graph, one curves each VCC in ms. There SHOULD be 12 curves on the graph, one curves
indicated and labeled for each VCC. The integration time per point MUST indicated and labeled for each VCC. The integration time per point MUST
be indicated. be indicated.
The histograms SHOULD display the peak-to-peak cell delay. There will be The histograms SHOULD display the peak-to-peak cell delay. There will be
one histogram for each VCC. The x-coordinate SHOULD be the cell delay one histogram for each VCC. The x-coordinate SHOULD be the cell delay
in us with at least 256 bins. The y-coordinate SHOULD be the number of in us with at least 256 bins. The y-coordinate SHOULD be the number of
cells observed in each bin. cells observed in each bin.
The results MUST also indicate the packet size in octets and traffic The results MUST also indicate the packet size in octets, traffic rate
rate in packets per second as generated by the test device. The VCC and in packets per second, and bearer class as generated by the test device.
VPI/VCI values MUST also be indicated. 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.1.4. Two-point CDV/Maximum VCCs 3.2.1.7. Two-point CDV/Bursty VBR Load/Maximum VCCs
Objective: To determine the SUT variation in cell transfer delay with the Objective: To determine the SUT variation in cell transfer delay with the
maximum number VCCs supported on the SUT as defined in "Terminology for ATM maximum number VCCs supported on the SUT as defined in RFC 2761
Benchmarking". "Terminology for ATM Benchmarking".
Procedure: Procedure:
1) Set up the SUT and test device using the bi-directional 1) Set up the SUT and test device using the bi-directional
configuration. configuration.
2) Configure the SUT and test device with the maximum number of VCCs 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. For example, if the maximum number of VCCs
supported on the SUT is 1024, define 256 VPIs with 4 VCIs per VPI. The supported on the SUT is 1024, define 256 VPIs with 4 VCIs per VPI. The
VPI/VCIs MUST not be one of the reserved signaling channels (e.g. [0,5], 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]).
3) Send a specific number of IP packets containing timestamps at a
specific VBR 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 packets timestamps at the transmitter and receiver ends of
the test device for all VCCs.
Reporting Format:
The results of the Two-point CDV/Bursty VBR Load/Maximum VCCs test
SHOULD be reported in a form of text, graphs, and histograms.
The text results SHOULD display the numerical values of the CDV. The
values given SHOULD include: time period of test in s, test VPI/VCI
values, total number of cells transmitted and received on each VCC
during the test in positive integers, maximum and minimum CDV on each
VCC during the test in us, and peak-to-peak CDV on each VCC in us.
The graph results SHOULD display the cell delay 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 cell delay for
each VCC in us. 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 histograms SHOULD display the peak-to-peak cell delay. There will be
one histogram for each VCC. The x-coordinate SHOULD be the cell delay in
us with at least 256 bins. The y-coordinate SHOULD be the number of
cells observed in each bin.
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.1.5. Two-point CDV/Bursty UBR Load/One VCC
Objective: To determine the SUT variation in cell transfer delay with one
VCC 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]).
3) Send a specific number of IP packets containing timestamps at a
specific UBR 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 packets timestamps at the transmitter and receiver ends of
the test device.
Reporting Format:
The results of the Two-point CDV/Bursty UBR Load/One VCC test SHOULD be
reported in a form of text, graph, and histogram.
The text results SHOULD display the numerical values of the CDV. 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, maximum and minimum CDV
during the test in us, and peak-to-peak CDV in us.
The graph results SHOULD display the cell delay 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 cell delay in
us. The integration time per point MUST be indicated.
The histogram results SHOULD display the peak-to-peak cell delay. The
x- coordinate SHOULD be the cell delay in us with at least 256 bins.
The y- coordinate SHOULD be the number of cells observed in each bin.
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 bearer class of the
created VCC MUST also be indicated.
3.2.1.6. Two-point CDV/Bursty UBR Load/Twelve VCCs
Objective: To determine the SUT variation in cell transfer delay with
twelve VCCs 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 a UBR connection. The VPI/VCIs
MUST not be one of the reserved ATM signaling channels (e.g. [0,5],
[0,16]). [0,16]).
3) Send a specific number of IP packets containing time stamps at a 3) Send a specific number of IP packets containing time stamps at a
specific rate through the SUT via the defined test VCCs. All of the specific UBR through the SUT via the defined test VCCs. All of the
VPI/VCI pairs will generate traffic at the same traffic rate. Since 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 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. 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 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 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 same on the SUT, continue the test; else lower the test device traffic
rate until the counts are the same. rate until the counts are the same.
5) Record the packets timestamps at the transmitter and receiver ends of 5) Record the packets timestamps at the transmitter and receiver ends of
the test device for all VCCs. the test device for all VCCs.
Reporting Format: Reporting Format:
The results of the Two-point CDV/Maximum VCCs test SHOULD be reported in The results of the Two-point CDV/Bursty UBR Load/Twelve VCCs test SHOULD
a form of text, graphs, and histograms. be reported in a form of text, graph, and histograms.
The text results SHOULD display the numerical values of the CDV. The
values given SHOULD include: time period of test in s, test VPI/VCI
values, total number of cells transmitted and received on each VCC
during the test in positive integers, maximum and minimum CDV on each
VCC during the test in us, and peak-to-peak CDV on each VCC in us.
The graph results SHOULD display the cell delay 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 cell delay for
each VCC in ms. There SHOULD be 12 curves on the graph, one curves
indicated and labeled for each VCC. The integration time per point MUST
be indicated.
The histograms SHOULD display the peak-to-peak cell delay. There will be
one histogram for each VCC. The x-coordinate SHOULD be the cell delay
in us with at least 256 bins. The y-coordinate SHOULD be the number of
cells observed in each bin.
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 bearer class of the
created VCC MUST also be indicated.
3.2.1.7. Two-point CDV/Bursty UBR Load/Maximum VCCs
Objective: To determine the SUT variation in cell transfer delay with the
maximum number VCCs supported on the SUT 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 a 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 containing timestamps at a
specific UBR 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 packets timestamps at the transmitter and receiver ends of
the test device for all VCCs.
Reporting Format:
The results of the Two-point CDV/Bursty UBR Load/Maximum VCCs test
SHOULD be reported in a form of text, graphs, and histograms.
The text results SHOULD display the numerical values of the CDV. The The text results SHOULD display the numerical values of the CDV. The
values given SHOULD include: time period of test in s, test VPI/VCI values given SHOULD include: time period of test in s, test VPI/VCI
values, total number of cells transmitted and received on each VCC values, total number of cells transmitted and received on each VCC
during the test in positive integers, maximum and minimum CDV on each during the test in positive integers, maximum and minimum CDV on each
VCC during the test in us, and peak-to-peak CDV on each VCC in us. VCC during the test in us, and peak-to-peak CDV on each VCC in us.
The graph results SHOULD display the cell delay values. There will be The graph results SHOULD display the cell delay values. There will be
(Max number of VCCs/10) graphs, with 10 VCCs indicated on each graph. (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 cell delay for
each VCC in us. 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 histograms SHOULD display the peak-to-peak cell delay. There will be
one histogram for each VCC. The x-coordinate SHOULD be the cell delay in
us with at least 256 bins. The y-coordinate SHOULD be the number of
cells observed in each bin.
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 bearer class of the
created VCC MUST also be indicated.
3.2.1.8. Two-point CDV/Mixed Load/Three VCC's
Objective: To determine the SUT variation in cell transfer delay with three
VCC's 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]).
3) Send a specific number of IP packets containing timestamps 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 packets timestamps at the transmitter and receiver ends of
the test device for all VCC's.
Reporting Format:
The results of the Two-point CDV/Mixed Load/Three VCC test SHOULD be
reported in a form of text, graph, and histogram.
The text results SHOULD display the numerical values of the CDV. 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, maximum and minimum CDV
during the test in us, and peak-to-peak CDV in us.
The graph results SHOULD display the cell delay 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 cell delay in
us. The integration time per point MUST be indicated.
The histogram results SHOULD display the peak-to-peak cell delay. The
x- coordinate SHOULD be the cell delay in us with at least 256 bins.
The y- coordinate SHOULD be the number of cells observed in each bin.
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.1.9. Two-point CDV/Mixed Load/Twelve VCCs
Objective: To determine the SUT variation in cell transfer delay with
twelve VCCs 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 timestamps 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 packets timestamps at the transmitter and receiver ends of
the test device for all VCCs.
Reporting Format:
The results of the Two-point CDV/Mixed Load/Twelve VCCs test SHOULD be
reported in a form of text, graph, and histograms.
The text results SHOULD display the numerical values of the CDV. The
values given SHOULD include: time period of test in s, test VPI/VCI
values, total number of cells transmitted and received on each VCC
during the test in positive integers, maximum and minimum CDV on each
VCC during the test in us, and peak-to-peak CDV on each VCC in us.
The graph results SHOULD display the cell delay 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 cell delay for
each VCC in ms. There SHOULD be 12 curves on the graph, one curves
indicated and labeled for each VCC. The integration time per point MUST
be indicated.
The histograms SHOULD display the peak-to-peak cell delay. There will be
one histogram for each VCC. The x-coordinate SHOULD be the cell delay
in us with at least 256 bins. The y-coordinate SHOULD be the number of
cells observed in each bin.
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.1.10. Two-point CDV/Mixed Load/Maximum VCCs
Objective: To determine the SUT variation in cell transfer delay with the
maximum number VCCs supported on the SUT 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. If the maximum
number of VCC's is not divisible by 3, the total for each bearer class
MUST be within 3 VCC's of each other. 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 timestamps 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 packets timestamps at the transmitter and receiver ends of
the test device for all VCCs.
Reporting Format:
The results of the Two-point CDV/Mixed Load/Maximum VCCs test SHOULD be
reported in a form of text, graphs, and histograms.
The text results SHOULD display the numerical values of the CDV. The
values given SHOULD include: time period of test in s, test VPI/VCI
values, total number of cells transmitted and received on each VCC
during the test in positive integers, maximum and minimum CDV on each
VCC during the test in us, and peak-to-peak CDV on each VCC in us.
The graph results SHOULD display the cell delay 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 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 or days depending on the total length of the test. The x-coordinate time
SHOULD be configurable. The y-coordinate SHOULD be the cell delay for SHOULD be configurable. The y-coordinate SHOULD be the cell delay for
each VCC in us. There SHOULD be no more than 10 curves on each graph, each VCC in us. There SHOULD be no more than 10 curves on each graph,
one curve indicated and labeled for each VCC. The integration time per one curve indicated and labeled for each VCC. The integration time per
point MUST be indicated. point MUST be indicated.
The histograms SHOULD display the peak-to-peak cell delay. There will be The histograms SHOULD display the peak-to-peak cell delay. There will be
one histogram for each VCC. The x-coordinate SHOULD be the cell delay in one histogram for each VCC. The x-coordinate SHOULD be the cell delay in
us with at least 256 bins. The y-coordinate SHOULD be the number of us with at least 256 bins. The y-coordinate SHOULD be the number of
cells observed in each bin. cells observed in each bin.
The results MUST also indicate the packet size in octets and traffic The results MUST also indicate the packet size in octets, traffic rate
rate in packets per second as generated by the test device. The VCC and in packets per second, and bearer class as generated by the test device.
VPI/VCI values MUST also be indicated. 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.2. Cell Error Ratio (CER) 3.2.2. Cell Error Ratio (CER)
3.2.2.1. Test Setup 3.2.2.1. Test Setup
The cell error ratio measurements assume that both the transmitter and The cell error ratio measurements assume that both the transmitter and
receiver payload information is synchronized. Synchronization MUST be receiver payload information is synchronized. Synchronization MUST be
achieved by supplying a known bit pattern to both the transmitter and achieved by supplying a known bit pattern to both the transmitter and
receiver. If this bit pattern is longer than the packet size, the receiver. If this bit pattern is longer than the packet size, the
receiver MUST synchronize with the transmitter before tests can be run. receiver MUST synchronize with the transmitter before tests can be run.
3.2.2.2. Steady Load/One VCC 3.2.2.2. CER/Steady Load/One VCC
Objective: To determine the SUT ratio of errored cells on one VCC in a Objective: To determine the SUT ratio of errored cells on one VCC in a
transmission in relation to the total cells sent as defined in "Terminology transmission in relation to the total cells sent as defined in RFC 2761
for ATM Benchmarking". "Terminology for ATM Benchmarking".
Procedure: Procedure:
1) Set up the SUT and test device using the bi-directional 1) Set up the SUT and test device using the bi-directional
configuration. configuration.
2) Configure the SUT and test device with one VCC. The VCC SHOULD 2) Configure the SUT and test device with one VCC. The VCC SHOULD
contain one VPI/VCI. The VPI/VCI MUST not be one of the reserved 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]). signaling channels (e.g. [0,5], [0,16]).
3) Send a specific number of IP packets containing one of the specified 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 bit patterns at a constant rate through the SUT via the defined test
VCC. Since this test is not a throughput test, the rate should not be 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 greater than 90% of line rate. The IP PDUs MUST be encapsulated in
AAL5. AAL5.
4) Count the IP packets that are transmitted by the SUT to verify 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 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 the SUT, continue the test; else lower the test device traffic rate
until the counts are the same. until the counts are the same.
5) Record the number of bit errors at the receiver end of the test 5) Record the number of bit errors at the receiver end of the test
device. device.
Reporting Format: Reporting Format:
The results of the Steady Load/One VCC test SHOULD be reported in a form The results of the CER/Steady Load/One VCC test SHOULD be reported in a
of text and graph. form of text and graph.
The text results SHOULD display the numerical values of the CER. The The text results SHOULD display the numerical values of the CER. The
values given SHOULD include: time period of test in s, test VPI/VCI values given SHOULD include: time period of test in s, test VPI/VCI
value, total number of cells transmitted and received on the given value, total number of cells transmitted and received on the given
VPI/VCI during the test in positive integers, and the CER for the entire VPI/VCI during the test in positive integers, and the CER for the entire
test. test.
The graph results SHOULD display the cell error ratio values. The x- The graph results SHOULD display the cell error ratio values. The x-
coordinate SHOULD be the test run time in either seconds, minutes or 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 days depending on the total length of the test. The x-coordinate time
SHOULD be configurable. The y-coordinate SHOULD be the CER. The SHOULD be configurable. The y-coordinate SHOULD be the CER. The
integration time per point MUST be indicated. integration time per point MUST be indicated.
The results MUST also indicate the packet size in octets and traffic The results MUST also indicate the packet size in octets, traffic rate
rate in packets per second as generated by the test device. The VCC and in packets per second, and bearer class as generated by the test device.
VPI/VCI values MUST be indicated. The payload bit pattern MUST be The VCC and VPI/VCI values MUST be indicated. The PCR, SCR, and MBS MUST
indicated. be indicated. The bearer class of the created VCC MUST be indicated.
The generated bit pattern MUST also be indicated.
3.2.2.3. Steady Load/Twelve VCCs 3.2.2.3. CER/Steady Load/Twelve VCCs
Objective: To determine the SUT ratio of errored cells on twelve VCCs in a Objective: To determine the SUT ratio of errored cells on twelve VCCs in a
transmission in relation to the total cells sent as defined in "Terminology transmission in relation to the total cells sent as defined in RFC 2761
for ATM Benchmarking". "Terminology for ATM Benchmarking".
Procedure: Procedure:
1) Set up the SUT and test device using the bi-directional 1) Set up the SUT and test device using the bi-directional
configuration. configuration.
2) Configure the SUT and test device with twelve VCCs, using 1 VPI and 2) Configure the SUT and test device with twelve VCCs, using 1 VPI and
12 VCIs. The VPI/VCIs MUST not be one of the reserved signaling channels 12 VCIs. The VCC's MUST be configured as either a CBR, VBR, or UBR
(e.g. [0,5], [0,16]). 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 containing one of the specified 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 bit patterns at a constant rate through the SUT via the defined test
VCCs. All of the VPI/VCI pairs will generate traffic at the same traffic 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 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 greater than 90% of line rate. The IP PDUs MUST be encapsulated in
AAL5. AAL5.
4) Count the IP packets that are transmitted by the SUT on all VCCs to 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 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 same on the SUT, continue the test; else lower the test device traffic
rate until the counts are the same. rate until the counts are the same.
5) Record the number of bit errors at the receiver end of the test 5) Record the number of bit errors at the receiver end of the test
device for all VCCs. device for all VCCs.
Reporting Format: Reporting Format:
The results of the Steady Load/Twelve VCCs test SHOULD be reported in a The results of the CER/Steady Load/Twelve VCCs test SHOULD be reported
form of text and graph. in a form of text and graph.
The text results SHOULD display the numerical values of the CER. The The text results SHOULD display the numerical values of the CER. The
values given SHOULD include: time period of test in s, test VPI/VCI values given SHOULD include: time period of test in s, test VPI/VCI
value, total number of cells transmitted and received on the given value, total number of cells transmitted and received on the given
VPI/VCI during the test in positive integers, and the CER for the entire VPI/VCI during the test in positive integers, and the CER for the entire
test. test.
The graph results SHOULD display the cell error ratio values. The x- The graph results SHOULD display the cell error ratio values. The x-
coordinate SHOULD be the test run time in either seconds, minutes or 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 days depending on the total length of the test. The x-coordinate time
SHOULD be configurable. The y-coordinate SHOULD be the CER for each SHOULD be configurable. The y-coordinate SHOULD be the CER for each
VCC. There should be 12 curves on the graph, on curve indicated and 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. labeled for each VCC. The integration time per point MUST be indicated.
The results MUST also indicate the packet size in octets and traffic The results MUST also indicate the packet size in octets, traffic rate
rate in packets per second as generated by the test device. The VCC and in packets per second, and bearer class as generated by the test device.
VPI/VCI values MUST be indicated. The payload bit pattern MUST be The VCC and VPI/VCI values MUST be indicated. The PCR, SCR, and MBS MUST
indicated. be indicated. The bearer class of the created VCC MUST be indicated. The
generated bit pattern MUST also be indicated.
3.2.2.4. Steady Load/Maximum VCCs 3.2.2.4. CER/Steady Load/Maximum VCCs
Objective: To determine the SUT ratio of errored cells with the maximum Objective: To determine the SUT ratio of errored cells with the maximum
number VCCs supported on the SUT in a transmission in relation to the total number VCCs supported on the SUT in a transmission in relation to the total
cells sent as defined in "Terminology for ATM Benchmarking". cells sent as defined in RFC 2761 "Terminology for ATM Benchmarking".
Procedure: Procedure:
1) Set up the SUT and test device using the bi-directional 1) Set up the SUT and test device using the bi-directional
configuration. configuration.
2) Configure the SUT and test device with the maximum number of VCCs 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. For example, if the maximum number of VCCs
supported on the SUT is 1024, define 256 VPIs with 4 VCIs per VPI. The supported on the SUT is 1024, define 256 VPIs with 4 VCIs per VPI. The
VPI/VCIs MUST not be one of the reserved signaling channels (e.g. [0,5], VCC's MUST be configured as either a CBR, VBR, or UBR connection. The
[0,16]). 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 containing one of the specified 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 bit patterns at a constant rate through the SUT via the defined test
VCCs. All of the VPI/VCI pairs will generate traffic at the same traffic 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 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 greater than 90% of line rate. The IP PDUs MUST be encapsulated in
AAL5. AAL5.
4) Count the IP packets that are transmitted by the SUT on all VCCs to 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 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 same on the SUT, continue the test; else lower the test device traffic
rate until the counts are the same. rate until the counts are the same.
5) Record the number of bit errors at the receiver end of the test 5) Record the number of bit errors at the receiver end of the test
device for all VCCs. device for all VCCs.
Reporting Format: Reporting Format:
The results of the Steady Load/Maximum VCCs test SHOULD be reported in a The results of the CER/Steady Load/Maximum VCCs test SHOULD be reported
form of text and graph. in a form of text and graph.
The text results SHOULD display the numerical values of the CER. The The text results SHOULD display the numerical values of the CER. The
values given SHOULD include: time period of test in s, test VPI/VCI values given SHOULD include: time period of test in s, test VPI/VCI
value, total number of cells transmitted and received on the given value, total number of cells transmitted and received on the given
VPI/VCI during the test in positive integers, and the CER for the entire VPI/VCI during the test in positive integers, and the CER for the entire
test. test.
The graph results SHOULD display the cell error ratio values. There will The graph results SHOULD display the cell error ratio values. There will
be (Max number of VCCs/10) graphs, with 10 VCCs indicated on each graph. 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 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 or days depending on the total length of the test. The x-coordinate time
SHOULD be configurable. The y-coordinate SHOULD be the CER for each SHOULD be configurable. The y-coordinate SHOULD be the CER for each
VCC. There SHOULD be no more than 10 curves on each graph, one curve 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 indicated and labeled for each VCC. The integration time per point MUST
be indicated. be indicated.
The results MUST also indicate the packet size in octets and traffic The results MUST also indicate the packet size in octets, traffic rate
rate in packets per second as generated by the test device. The VCC and in packets per second, and bearer class as generated by the test device.
VPI/VCI values MUST be indicated. The payload bit pattern MUST be The VCC and VPI/VCI values MUST be indicated. The PCR, SCR, and MBS MUST
indicated. be indicated. The bearer class of the created VCC MUST be indicated. The
generated bit pattern MUST also be indicated.
3.2.2.5. Bursty Load/One VCC 3.2.2.5. CER/Bursty VBR Load/One VCC
Objective: To determine the SUT ratio of errored cells on one VCC in a Objective: To determine the SUT ratio of errored cells on one VCC in a
transmission in relation to the total cells sent as defined in "Terminology transmission in relation to the total cells sent as defined in RFC 2761
for ATM Benchmarking". "Terminology for ATM Benchmarking".
Procedure: Procedure:
1) Set up the SUT and test device using the bi-directional 1) Set up the SUT and test device using the bi-directional
configuration. configuration.
2) Configure the SUT and test device with one VCC. The VCC SHOULD 2) Configure the SUT and test device with one VCC. The VCC SHOULD
contain one VPI/VCI. The VPI/VCI MUST not be one of the reserved contain one VPI/VCI. The VCC MUST be configured as either a CBR or VBR
signaling channels (e.g. [0,5], [0,16]). The PCR, SCR, and MBS must be 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. configured using one of the specified traffic descriptors.
3) Send a specific number of IP packets containing one of the specified 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 bit patterns at a specific VBR rate through the SUT via the defined test
VCC. Since this test is not a throughput test, the rate should not be 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. 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 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 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 the SUT, continue the test; else lower the test device traffic rate
until the counts are the same. until the counts are the same.
5) Record the number of bit errors at the receiver end of the test 5) Record the number of bit errors at the receiver end of the test
device. device.
Reporting Format: Reporting Format:
The results of the Bursty Load/One VCC test SHOULD be reported in a form The results of the CER/Bursty VBR Load/One VCC test SHOULD be reported
of text and graph. in a form of text and graph.
The text results SHOULD display the numerical values of the CER. The The text results SHOULD display the numerical values of the CER. The
values given SHOULD include: time period of test in s, test VPI/VCI values given SHOULD include: time period of test in s, test VPI/VCI
value, total number of cells transmitted and received on the given value, total number of cells transmitted and received on the given
VPI/VCI during the test in positive integers, and the CER for the entire VPI/VCI during the test in positive integers, and the CER for the entire
test. test.
The graph results SHOULD display the cell error ratio values. The x- The graph results SHOULD display the cell error ratio values. The x-
coordinate SHOULD be the test run time in either seconds, minutes or 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 days depending on the total length of the test. The x-coordinate time
SHOULD be configurable. The y-coordinate SHOULD be the CER. The SHOULD be configurable. The y-coordinate SHOULD be the CER. The
integration time per point MUST be indicated. integration time per point MUST be indicated.
The results MUST also indicate the packet size in octets and traffic The results MUST also indicate the packet size in octets, traffic rate
rate in packets per second as generated by the test device. The VCC and in packets per second, and bearer class as generated by the test device.
VPI/VCI values MUST be indicated. The payload bit pattern MUST be The VCC and VPI/VCI values MUST be indicated. The PCR, SCR, and MBS MUST
indicated. The PCR, SCR, and MBS MUST be indicated. be indicated. The bearer class of the created VCC MUST be indicated. The
generated bit pattern MUST also be indicated.
3.2.2.6. Bursty Load/Twelve VCCs 3.2.2.6. CER/Bursty VBR Load/Twelve VCCs
Objective: To determine the SUT ratio of errored cells on twelve VCCs in a Objective: To determine the SUT ratio of errored cells on twelve VCCs in a
transmission in relation to the total cells sent as defined in RFC 2761
transmission in relation to the total cells sent as defined in "Terminology "Terminology for ATM Benchmarking".
for ATM Benchmarking".
Procedure: Procedure:
1) Set up the SUT and test device using the bi-directional 1) Set up the SUT and test device using the bi-directional
configuration. configuration.
2) Configure the SUT and test device with twelve VCCs, using 1 VPI and 2) Configure the SUT and test device with twelve VCCs, using 1 VPI and
12 VCIs. The VPI/VCIs MUST not be one of the reserved signaling channels 12 VCIs. The VCC's MUST be configured as either a CBR or VBR connection.
(e.g. [0,5], [0,16]). The PCR, SCR, and MBS must be configured using one The VPI/VCIs MUST not be one of the reserved ATM signaling channels
of the specified traffic descriptors. (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 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 bit patterns at a specific VBR rate through the SUT via the defined test
VCCs. All of the VPI/VCI pairs will generate traffic at the same traffic 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 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. greater than 90% of line rate. The PCR, SCR, and MBS must be indicated.
The IP PDUs MUST be encapsulated in AAL5. The IP PDUs MUST be encapsulated in AAL5.
4) Count the IP packets that are transmitted by the SUT on all VCCs to 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 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 same on the SUT, continue the test; else lower the test device traffic
rate until the counts are the same. rate until the counts are the same.
5) Record the number of bit errors at the receiver end of the test 5) Record the number of bit errors at the receiver end of the test
device for all VCCs. device for all VCCs.
skipping to change at page 32, line 35 skipping to change at page 50, line 17
4) Count the IP packets that are transmitted by the SUT on all VCCs to 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 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 same on the SUT, continue the test; else lower the test device traffic
rate until the counts are the same. rate until the counts are the same.
5) Record the number of bit errors at the receiver end of the test 5) Record the number of bit errors at the receiver end of the test
device for all VCCs. device for all VCCs.
Reporting Format: Reporting Format:
The results of the Bursty Load/Twelve VCCs test SHOULD be reported in a The results of the CER/Bursty VBR Load/Twelve VCCs test SHOULD be
form of text and graph. reported in a form of text and graph.
The text results SHOULD display the numerical values of the CER. The The text results SHOULD display the numerical values of the CER. The
values given SHOULD include: time period of test in s, test VPI/VCI values given SHOULD include: time period of test in s, test VPI/VCI
value, total number of cells transmitted and received on the given value, total number of cells transmitted and received on the given
VPI/VCI during the test in positive integers, and the CER for the entire VPI/VCI during the test in positive integers, and the CER for the entire
test. test.
The graph results SHOULD display the cell error ratio values. The x- The graph results SHOULD display the cell error ratio values. The x-
coordinate SHOULD be the test run time in either seconds, minutes or 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 days depending on the total length of the test. The x-coordinate time
SHOULD be configurable. The y-coordinate SHOULD be the CER for each SHOULD be configurable. The y-coordinate SHOULD be the CER for each
VCC. There should be 12 curves on the graph, on curve indicated and 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. labeled for each VCC. The integration time per point MUST be indicated.
The results MUST also indicate the packet size in octets and traffic The results MUST also indicate the packet size in octets, traffic rate
rate in packets per second as generated by the test device. The VCC and in packets per second, and bearer class as generated by the test device.
VPI/VCI values MUST be indicated. The payload bit pattern MUST be The VCC and VPI/VCI values MUST be indicated. The PCR, SCR, and MBS MUST
indicated. The PCR, SCR, and MBS MUST be indicated. be indicated. The bearer class of the created VCC MUST be indicated. The
generated bit pattern MUST also be indicated.
3.2.2.7. Bursty Load/Maximum VCCs 3.2.2.7. CER/Bursty VBR Load/Maximum VCCs
Objective: To determine the SUT ratio of errored cells with the maximum Objective: To determine the SUT ratio of errored cells with the maximum
number VCCs supported on the SUT in a transmission in relation to the total number VCCs supported on the SUT in a transmission in relation to the total
cells sent as defined in "Terminology for ATM Benchmarking". cells sent as defined in RFC 2761 "Terminology for ATM Benchmarking".
Procedure: Procedure:
1) Set up the SUT and test device using the bi-directional 1) Set up the SUT and test device using the bi-directional
configuration. configuration.
2) Configure the SUT and test device with the maximum number of VCCs 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. For example, if the maximum number of VCCs
supported on the SUT is 1024, define 256 VPIs with 4 VCIs per VPI. The supported on the SUT is 1024, define 256 VPIs with 4 VCIs per VPI. The
VPI/VCIs MUST not be one of the reserved signaling channels (e.g. [0,5], 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 VBR 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 bit errors at the receiver end of the test
device for all VCCs.
Reporting Format:
The results of the CER/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 CER. 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 CER for the entire
test.
The graph results SHOULD display the cell 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 CER 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 be indicated. The
generated bit pattern MUST also be indicated.
3.2.2.5. CER/Bursty UBR Load/One VCC
Objective: To determine the SUT ratio of errored 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 UBR 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 bit errors at the receiver end of the test
device.
Reporting Format:
The results of the CER/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 CER. 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 CER for the entire
test.
The graph results SHOULD display the cell 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 CER. 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 be indicated. The
generated bit pattern MUST also be indicated.
3.2.2.6. CER/Bursty UBR Load/Twelve VCCs
Objective: To determine the SUT ratio of errored 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 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 [0,16]). The PCR, SCR, and MBS must be configured using one of the
specified traffic descriptors. specified traffic descriptors.
3) Send a specific number of IP packets containing one of the specified 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 bit patterns at a specific UBR 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 bit errors at the receiver end of the test
device for all VCCs.
Reporting Format:
The results of the CER/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 CER. 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 CER for the entire
test.
The graph results SHOULD display the cell 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 CER 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 be indicated. The
generated bit pattern MUST also be indicated.
3.2.2.7. CER/Bursty UBR Load/Maximum VCCs
Objective: To determine the SUT ratio of errored 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 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 UBR rate through the SUT via the defined test
VCCs. All of the VPI/VCI pairs will generate traffic at the same traffic 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 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 greater than 90% of line rate. The IP PDUs MUST be encapsulated in
AAL5. AAL5.
4) Count the IP packets that are transmitted by the SUT on all VCCs to 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 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 same on the SUT, continue the test; else lower the test device traffic
rate until the counts are the same. rate until the counts are the same.
5) Record the number of bit errors at the receiver end of the test 5) Record the number of bit errors at the receiver end of the test
device for all VCCs. device for all VCCs.
Reporting Format: Reporting Format:
The results of the Bursty Load/Maximum VCCs test SHOULD be reported in a The results of the CER/Bursty UBR Load/Maximum VCCs test SHOULD be
form of text and graph. reported in a form of text and graph.
The text results SHOULD display the numerical values of the CER. The The text results SHOULD display the numerical values of the CER. The
values given SHOULD include: time period of test in s, test VPI/VCI values given SHOULD include: time period of test in s, test VPI/VCI
value, total number of cells transmitted and received on the given value, total number of cells transmitted and received on the given
VPI/VCI during the test in positive integers, and the CER for the entire VPI/VCI during the test in positive integers, and the CER for the entire
test. test.
The graph results SHOULD display the cell error ratio values. There will The graph results SHOULD display the cell error ratio values. There will
be (Max number of VCCs/10) graphs, with 10 VCCs indicated on each graph. 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 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 or days depending on the total length of the test. The x-coordinate time
SHOULD be configurable. The y-coordinate SHOULD be the CER for each SHOULD be configurable. The y-coordinate SHOULD be the CER for each
VCC. There SHOULD be no more than 10 curves on each graph, one curve 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 indicated and labeled for each VCC. The integration time per point MUST
be indicated. be indicated.
The results MUST also indicate the packet size in octets and traffic The results MUST also indicate the packet size in octets, traffic rate
rate in packets per second as generated by the test device. The VCC and in packets per second, and bearer class as generated by the test device.
VPI/VCI values MUST be indicated. The payload bit pattern MUST be The VCC and VPI/VCI values MUST be indicated. The PCR, SCR, and MBS MUST
indicated. The PCR, SCR, and MBS MUST be indicated. be indicated. The bearer class of the created VCC MUST be indicated. The
generated bit pattern MUST also be indicated.
3.2.1.8. CER/Mixed Load/Three VCC's
Objective: To determine the SUT ratio of errored 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 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]).
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 bit errors at the receiver end of the test
device for all VCCs.
Reporting Format:
The results of the CER/Bursty Mixed Load/Three VCCs test SHOULD be
reported in a form of text and graph.
The text results SHOULD display the numerical values of the CER. 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 CER for the entire
test.
The graph results SHOULD display the cell 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 CER 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 be indicated. The
generated bit pattern MUST also be indicated.
3.2.1.9. CER/Mixed Load/Twelve VCCs
Objective: To determine the SUT ratio of errored 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 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 bit errors at the receiver end of the test
device for all VCCs.
Reporting Format:
The results of the CER/Bursty Mixed Load/Twelve VCCs test SHOULD be
reported in a form of text and graph.
The text results SHOULD display the numerical values of the CER. 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 CER for the entire
test.
The graph results SHOULD display the cell 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 CER 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 be indicated. The
generated bit pattern MUST also be indicated.
3.2.1.10. CER/Mixed Load/Maximum VCCs
Objective: To determine the SUT ratio of errored 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.
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 bit errors at the receiver end of the test
device for all VCCs.
Reporting Format:
The results of the CER/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 CER. 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 CER for the entire
test.
The graph results SHOULD display the cell 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 CER 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 be indicated. The
generated bit pattern MUST also be indicated.
3.2.3. Cell Loss Ratio (CLR) 3.2.3. Cell Loss Ratio (CLR)
3.2.3.1. Steady Load/One VCC 3.2.3.1. CLR/Steady Load/One VCC
Objective: To determine the SUT ratio of lost cells on one VCC in a 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 "Terminology transmission in relation to the total cells sent as defined in RFC 2761
for ATM Benchmarking". "Terminology for ATM Benchmarking".
Procedure: Procedure:
1) Set up the SUT and test device using the bi-directional 1) Set up the SUT and test device using the bi-directional
configuration. configuration.
2) Configure the SUT and test device with one VCC. The VCC SHOULD 2) Configure the SUT and test device with one VCC. The VCC SHOULD
contain one VPI/VCI. The VPI/VCI MUST not be one of the reserved 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]). signaling channels (e.g. [0,5], [0,16]).
3) Send a specific number of IP packets at a specific rate through the 3) Send a specific number of IP packets at a specific constant rate
SUT via the defined test VCC. Since this test is not a throughput test, through the SUT via the defined test VCC. Since this test is not a
the rate should not be greater than 90% of line rate. The IP PDUs MUST throughput test, the rate should not be greater than 90% of line rate.
be encapsulated in AAL5. The IP PDUs MUST be encapsulated in AAL5.
4) Count the IP packets that are transmitted by the SUT to verify 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 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 the SUT, continue the test; else lower the test device traffic rate
until the counts are the same. until the counts are the same.
5) Record the number of cells transmitted and received on the test 5) Record the number of cells transmitted and received on the test
device. device.
Reporting Format: Reporting Format:
The results of the Steady Load/One VCC test SHOULD be reported in a form The results of the CLR/Steady Load/One VCC test SHOULD be reported in a
of text and graph. form of text and graph.
The text results SHOULD display the numerical values of the CLR. The 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 values given SHOULD include: time period of test in s, test VPI/VCI
value, total number of cells transmitted and received on the given 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 VPI/VCI during the test in positive integers, and the CLR for the entire
test. test.
The graph results SHOULD display the Cell Loss ratio values. The x- The graph results SHOULD display the Cell Loss ratio values. The x-
coordinate SHOULD be the test run time in either seconds, minutes or 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 days depending on the total length of the test. The x-coordinate time
SHOULD be configurable. The y-coordinate SHOULD be the CLR. The SHOULD be configurable. The y-coordinate SHOULD be the CLR. The
integration time per point MUST be indicated. integration time per point MUST be indicated.
The results MUST also indicate the packet size in octets and traffic The results MUST also indicate the packet size in octets, traffic rate
rate in packets per second as generated by the test device. The VCC and in packets per second, and bearer class as generated by the test device.
VPI/VCI values MUST be indicated. 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. Steady Load/Twelve VCCs 3.2.3.2. CLR/Steady Load/Twelve VCCs
Objective: To determine the SUT ratio of lost cells on twelve VCCs in a 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 "Terminology transmission in relation to the total cells sent as defined in RFC 2761
for ATM Benchmarking". "Terminology for ATM Benchmarking".
Procedure: Procedure:
1) Set up the SUT and test device using the bi-directional 1) Set up the SUT and test device using the bi-directional
configuration. configuration.
2) Configure the SUT and test device with twelve VCCs, using 1 VPI and 2) Configure the SUT and test device with twelve VCCs, using 1 VPI and
12 VCIs. The VPI/VCIs MUST not be one of the reserved signaling channels 12 VCIs. The VCC's MUST be configured as either a CBR, VBR, or UBR
(e.g. [0,5], [0,16]). 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 rate through the 3) Send a specific number of IP packets at a specific constant rate
SUT via the defined test VCCs. All of the VPI/VCI pairs will generate through the SUT via the defined test VCCs. All of the VPI/VCI pairs will
traffic at the same traffic rate. Since this test is not a throughput generate traffic at the same traffic rate. Since this test is not a
test, the rate should not be greater than 90% of line rate. The IP PDUs throughput test, the rate should not be greater than 90% of line rate.
MUST be encapsulated in AAL5.
The IP PDUs MUST be encapsulated in AAL5.
4) Count the IP packets that are transmitted by the SUT on all VCCs to 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 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 same on the SUT, continue the test; else lower the test device traffic
rate until the counts are the same. rate until the counts are the same.
5) Record the number of cells transmitted and received per VCC on the 5) Record the number of cells transmitted and received per VCC on the
test device. test device.
Reporting Format: Reporting Format:
The results of the Steady Load/Twelve VCCs test SHOULD be reported in a The results of the CLR/Steady Load/Twelve VCCs test SHOULD be reported
form of text and graph. in a form of text and graph.
The text results SHOULD display the numerical values of the CLR. The 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 values given SHOULD include: time period of test in s, test VPI/VCI
value, total number of cells transmitted and received on the given 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 VPI/VCI during the test in positive integers, and the CLR for the entire
test. test.
The graph results SHOULD display the Cell Loss ratio values. The x- The graph results SHOULD display the Cell Loss ratio values. The x-
coordinate SHOULD be the test run time in either seconds, minutes or 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 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. 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 There should be 12 curves on the graph, on curve indicated and labeled
for each VCC. The integration time per point MUST be indicated. for each VCC. The integration time per point MUST be indicated.
The results MUST also indicate the packet size in octets and traffic The results MUST also indicate the packet size in octets, traffic rate
rate in packets per second as generated by the test device. The VCC and in packets per second, and bearer class as generated by the test device.
VPI/VCI values MUST be indicated. 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. Steady Load/Maximum VCCs 3.2.3.3. CLR/Steady Load/Maximum VCCs
Objective: To determine the SUT ratio of lost cells with the maximum number 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 VCCs supported on the SUT in a transmission in relation to the total cells
sent as defined in "Terminology for ATM Benchmarking". sent as defined in RFC 2761 "Terminology for ATM Benchmarking".
Procedure: Procedure:
1) Set up the SUT and test device using the bi-directional 1) Set up the SUT and test device using the bi-directional
configuration. configuration.
2) Configure the SUT and test device with the maximum number of VCCs 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. For example, if the maximum number of VCCs
supported on the SUT is 1024, define 256 VPIs with 4 VCIs per VPI. The supported on the SUT is 1024, define 256 VPIs with 4 VCIs per VPI. The
VPI/VCIs MUST not be one of the reserved signaling channels (e.g. [0,5], VCC's MUST be configured as either a CBR, VBR, or UBR connection. The
[0,16]). 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 rate through the 3) Send a specific number of IP packets at a specific constant rate
SUT via the defined test VCCs. All of the VPI/VCI pairs will generate through the SUT via the defined test VCCs. All of the VPI/VCI pairs will
traffic at the same traffic rate. Since this test is not a throughput generate traffic at the same traffic rate. Since this test is not a
test, the rate should not be greater than 90% of line rate. The IP PDUs throughput test, the rate should not be greater than 90% of line rate.
MUST be encapsulated in AAL5. The IP PDUs MUST be encapsulated in AAL5.
4) Count the IP packets that are transmitted by the SUT on all VCCs to 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 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 same on the SUT, continue the test; else lower the test device traffic
rate until the counts are the same. rate until the counts are the same.
5) Record the number of cells transmitted and received per VCC on the 5) Record the number of cells transmitted and received per VCC on the
test device. test device.
Reporting Format: Reporting Format:
The results of the Steady Load/Maximum VCCs test SHOULD be reported in a The results of the CLR/Steady Load/Maximum VCCs test SHOULD be reported
form of text and graph. in a form of text and graph.
The text results SHOULD display the numerical values of the CLR. The 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 values given SHOULD include: time period of test in s, test VPI/VCI
value, total number of cells transmitted and received on the given 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 VPI/VCI during the test in positive integers, and the CLR for the entire
test. test.
The graph results SHOULD display the Cell Loss ratio values. There will 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. 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 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 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 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 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 indicated and labeled for each VCC. The integration time per point MUST
be indicated. be indicated.
The results MUST also indicate the packet size in octets and traffic The results MUST also indicate the packet size in octets, traffic rate
rate in packets per second as generated by the test device. The VCC and in packets per second, and bearer class as generated by the test device.
VPI/VCI values MUST be indicated 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.4. Bursty Load/One VCC 3.2.3.4. CLR/Bursty VBR Load/One VCC
Objective: To determine the SUT ratio of lost cells on one VCC in a 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 "Terminology transmission in relation to the total cells sent as defined in RFC 2761
for ATM Benchmarking". "Terminology for ATM Benchmarking".
Procedure: Procedure:
1) Set up the SUT and test device using the bi-directional 1) Set up the SUT and test device using the bi-directional
configuration. configuration.
2) Configure the SUT and test device with one VCC. The VCC SHOULD 2) Configure the SUT and test device with one VCC. The VCC SHOULD
contain one VPI/VCI. The VPI/VCI MUST not be one of the reserved contain one VPI/VCI. The VCC MUST be configured as either a CBR or VBR
signaling channels (e.g. [0,5], [0,16]). The PCR, SCR, and MBS must be 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. configured using one of the specified traffic descriptors.
3) Send a specific number of IP packets containing one of the specified 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 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 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. 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 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 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 the SUT, continue the test; else lower the test device traffic rate
until the counts are the same. until the counts are the same.
5) Record the number of bit errors at the receiver end of the test 5) Record the number of cells transmitted and received on the test
device. device.
Reporting Format: Reporting Format:
The results of the Bursty Load/One VCC test SHOULD be reported in a form The results of the CLR/Bursty VBR Load/One VCC test SHOULD be reported
of text and graph. in a form of text and graph.
The text results SHOULD display the numerical values of the CLR. The 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 values given SHOULD include: time period of test in s, test VPI/VCI
value, total number of cells transmitted and received on the given 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 VPI/VCI during the test in positive integers, and the CLR for the entire
test. test.
The graph results SHOULD display the Cell Loss ratio values. The x- The graph results SHOULD display the Cell Loss ratio values. The x-
coordinate SHOULD be the test run time in either seconds, minutes or 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 days depending on the total length of the test. The x-coordinate time
SHOULD be configurable. The y-coordinate SHOULD be the CLR. The SHOULD be configurable. The y-coordinate SHOULD be the CLR. The
integration time per point MUST be indicated. integration time per point MUST be indicated.
The results MUST also indicate the packet size in octets and traffic The results MUST also indicate the packet size in octets, traffic rate
rate in packets per second as generated by the test device. The VCC and in packets per second, and bearer class as generated by the test device.
VPI/VCI values MUST be indicated. The payload bit pattern MUST be The VCC and VPI/VCI values MUST be indicated. The PCR, SCR, and MBS MUST
indicated. The PCR, SCR, and MBS MUST be indicated. be indicated. The bearer class of the created VCC MUST also be
indicated.
3.2.3.5. Bursty Load/Twelve VCCs 3.2.3.5. CLR/Bursty VBR Load/Twelve VCCs
Objective: To determine the SUT ratio of lost cells on twelve VCCs in a 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 "Terminology transmission in relation to the total cells sent as defined in RFC 2761
for ATM Benchmarking". "Terminology for ATM Benchmarking".
Procedure: Procedure:
1) Set up the SUT and test device using the bi-directional 1) Set up the SUT and test device using the bi-directional
configuration. configuration.
2) Configure the SUT and test device with twelve VCCs, using 1 VPI and 2) Configure the SUT and test device with twelve VCCs, using 1 VPI and
12 VCIs. The VPI/VCIs MUST not be one of the reserved signaling channels 12 VCIs. The VCC MUST be configured as either a CBR or VBR connection.
(e.g. [0,5], [0,16]). The PCR, SCR, and MBS must be configured using one The VPI/VCIs MUST not be one of the reserved ATM signaling channels
of the specified traffic descriptors. (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 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 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 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 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. greater than 90% of line rate. The PCR, SCR, and MBS must be indicated.
The IP PDUs MUST be encapsulated in AAL5. The IP PDUs MUST be encapsulated in AAL5.
4) Count the IP packets that are transmitted by the SUT on all VCCs to 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 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 same on the SUT, continue the test; else lower the test device traffic
rate until the counts are the same. rate until the counts are the same.
5) Record the number of bit errors at the receiver end of the test 5) Record the number of cells transmitted and received per VCC on the
device for all VCCs. test device.
Reporting Format: Reporting Format:
The results of the Bursty Load/Twelve VCCs test SHOULD be reported in a The results of the CLR/Bursty VBR Load/Twelve VCCs test SHOULD be
form of text and graph. reported in a form of text and graph.
The text results SHOULD display the numerical values of the CLR. The 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 values given SHOULD include: time period of test in s, test VPI/VCI
value, total number of cells transmitted and received on the given 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 VPI/VCI during the test in positive integers, and the CLR for the entire
test. test.
The graph results SHOULD display the Cell Loss ratio values. The x- The graph results SHOULD display the Cell Loss ratio values. The x-
coordinate SHOULD be the test run time in either seconds, minutes or 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 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 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 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. labeled for each VCC. The integration time per point MUST be indicated.
The results MUST also indicate the packet size in octets and traffic The results MUST also indicate the packet size in octets, traffic rate
rate in packets per second as generated by the test device. The VCC and in packets per second, and bearer class as generated by the test device.
VPI/VCI values MUST be indicated. The payload bit pattern MUST be The VCC and VPI/VCI values MUST be indicated. The PCR, SCR, and MBS MUST
indicated. The PCR, SCR, and MBS MUST be indicated. be indicated. The bearer class of the created VCC MUST also be
indicated.
3.2.3.6. Bursty Load/Maximum VCCs 3.2.3.6. CLR/Bursty VBR Load/Maximum VCCs
Objective: To determine the SUT ratio of lost cells with the maximum number 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 VCCs supported on the SUT in a transmission in relation to the total cells
sent as defined in "Terminology for ATM Benchmarking". sent as defined in RFC 2761 "Terminology for ATM Benchmarking".
Procedure: Procedure:
1) Set up the SUT and test device using the bi-directional 1) Set up the SUT and test device using the bi-directional
configuration. configuration.
2) Configure the SUT and test device with the maximum number of VCCs 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. For example, if the maximum number of VCCs
supported on the SUT is 1024, define 256 VPIs with 4 VCIs per VPI. The supported on the SUT is 1024, define 256 VPIs with 4 VCIs per VPI. The
VPI/VCIs MUST not be one of the reserved signaling channels (e.g. [0,5], 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 [0,16]). The PCR, SCR, and MBS must be configured using one of the
specified traffic descriptors. specified traffic descriptors.
3) Send a specific number of IP packets containing one of the specified 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 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 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 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 greater than 90% of line rate. The IP PDUs MUST be encapsulated in
AAL5. AAL5.
4) Count the IP packets that are transmitted by the SUT on all VCCs to 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 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 same on the SUT, continue the test; else lower the test device traffic
rate until the counts are the same. rate until the counts are the same.
5) Record the number of bit errors at the receiver end of the test 5) Record the number of cells transmitted and received per VCC on the
device for all VCCs. test device.
Reporting Format: Reporting Format:
The results of the Bursty Load/Maximum VCCs test SHOULD be reported in a The results of the CLR/Bursty VBR Load/Maximum VCCs test SHOULD be
form of text and graph. reported in a form of text and graph.
The text results SHOULD display the numerical values of the CLR. The 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 values given SHOULD include: time period of test in s, test VPI/VCI
value, total number of cells transmitted and received on the given 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 VPI/VCI during the test in positive integers, and the CLR for the entire
test. test.
The graph results SHOULD display the Cell Loss ratio values. There will 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. 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 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 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 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 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 indicated and labeled for each VCC. The integration time per point MUST
be indicated. be indicated.
The results MUST also indicate the packet size in octets and traffic The results MUST also indicate the packet size in octets, traffic rate
rate in packets per second as generated by the test device. The VCC and in packets per second, and bearer class as generated by the test device.
VPI/VCI values MUST be indicated. The payload bit pattern MUST be The VCC and VPI/VCI values MUST be indicated. The PCR, SCR, and MBS MUST
indicated. The PCR, SCR, and MBS MUST be indicated. be indicated. The bearer class of the created VCC MUST also be
indicated.
3.2.3.4. CLR/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 cells transmitted and received on the test
device.
Reporting Format:
The results of the CLR/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 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.5. CLR/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.
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 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 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.6. CLR/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 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 cells transmitted and received per VCC on the
test device.
Reporting Format:
The results of the CLR/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 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.3.4. CLR/Bursty Mixed Load/Three 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 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 cells transmitted and received per VCC on the
test device.
Reporting Format:
The results of the CLR/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 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.5. CLR/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 cells transmitted and received per VCC on the
test device.
Reporting Format:
The results of the CLR/Bursty Mixed 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.6. CLR/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.
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 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 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. Cell Misinsertion Rate (CMR)
To be done. 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.
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".
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.
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 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.
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.
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 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.
3.2.4.4. CMR/Bursty UBR 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 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 cell misinsertion errors at the receiver end of
the test device.
Reporting Format:
The results of the CMR/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 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 UBR 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 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.
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 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 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 UBR 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 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 cell misinsertion errors at the receiver end of
the test device per VCC.
Reporting Format:
The results of the CMR/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 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.
3.2.4.4. CMR/Bursty Mixed Load/Three 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 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 cell misinsertion errors at the receiver end of
the test device.
Reporting Format:
The results of the CMR/Bursty Mixed Load/Three VCC test SHOULD be
reported 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.5. CMR/Bursty Mixed 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 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 cell misinsertion errors at the receiver end of
the test device per VCC.
Reporting Format:
The results of the CMR/Bursty Mixed 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 Mixed 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 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.
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 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 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.
3.2.5. Cell Rate Margin (CRM) 3.2.5. Cell Rate Margin (CRM)
To be done. To Be Determined
3.2.6. CRC Error Ratio: 3.2.3. CRC Error Ratio (CRC-ER)
To be done. 3.2.3.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.
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. 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.
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.3.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.
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.3.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 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.3.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 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.
3.2.3.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. 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.3.4. 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.
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.3.5. 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.
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.3.6. 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 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.
3.2.3.4. CRC-ER/Bursty Mixed Load/Three 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 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 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.3.5. 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.
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.3.6. 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.
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.
3.2.7. Cell Transfer Delay (CTD) 3.2.7. Cell Transfer Delay (CTD)
To be done. 3.2.7.1. Test Setup
3.3. ATM Adaptation Layer (AAL) Type 5 (AAL5) The cell transfer delay measurements assume that both the transmitter
and receiver timestamp information is synchronized. Synchronization
SHOULD be achieved by supplying a common clock signal (minimum of 100
Mhz or 10 ns resolution) to both the transmitter and receiver. The
maximum timestamp values MUST be recorded to ensure synchronization in
the case of counter rollover. The cell transfer delay measurements
SHOULD utilize the O.191 cell (ITUT-O.191) encapsulated in a valid IP
packet. If the O.191 cell is not available, a test cell encapsulated in
a valid IP packet MAY be used. The test cell MUST contain a transmit
timestamp which can be correlated with a receive timestamp. A
description of the test cell MUST be included in the test results. The
description MUST include the timestamp length (in bits), counter
rollover value, and the timestamp accuracy (in ns).
To be done. 3.2.7.2. CTD/Steady Load/One VCC
3.3.1. AAL5 Reassembly Errors Objective: To determine the SUT variation in cell transfer delay with one
VCC as defined in RFC 2761 "Terminology for ATM Benchmarking".
To be done. Procedure:
3.3.2. AAL5 Reassembly Time 1) Set up the SUT and test device using the bi-directional
configuration.
To be done. 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.3.3. AAL5 CRC Error Ratio 3) Send a specific number of IP packets containing timestamps 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.
To be done. 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 packets timestamps at the transmitter and receiver ends of
the test device.
Reporting Format:
The results of the CTD/Steady Load/One VCC test SHOULD be reported in a
form of text, graph, and histogram.
The text results SHOULD display the numerical values of the CTD. 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, minimum, maximum, and mean
CTD during the test in us.
The graph results SHOULD display the cell transfer delay 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 cell transfer
delay in us. The integration time per point MUST be indicated.
The histogram results SHOULD display the cell transfer delay. The x-
coordinate SHOULD be the cell transfer delay in us with at least 256
bins. The y-coordinate SHOULD be the number of cells observed in each
bin.
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 bearer class of the
created VCC MUST also be indicated.
3.2.7.3. CTD/Steady Load/Twelve VCCs
Objective: To determine the SUT variation in cell transfer delay with
twelve VCCs 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 containing timestamps 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 packets timestamps at the transmitter and receiver ends of
the test device for all VCCs.
Reporting Format:
The results of the CTD/Steady Load/Twelve VCCs test SHOULD be reported
in a form of text, graph, and histograms.
The text results SHOULD display the numerical values of the CTD. The
values given SHOULD include: time period of test in s, test VPI/VCI
values, total number of cells transmitted and received on each VCC
during the test in positive integers, maximum and minimum CTD on each
VCC during the test in us, and mean CTD on each VCC in us.
The graph results SHOULD display the cell transfer delay 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 cell transfer
delay for each VCC in ms. There SHOULD be 12 curves on the graph, one
curves indicated and labeled for each VCC. The integration time per
point MUST be indicated.
The histograms SHOULD display the cell transfer delay. There will be one
histogram for each VCC. The x-coordinate SHOULD be the cell transfer
delay in us with at least 256 bins. The y-coordinate SHOULD be the
number of cells observed in each bin.
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 bearer class of the
created VCC MUST also be indicated.
3.2.7.4. CTD/Steady Load/Maximum VCCs
Objective: To determine the SUT variation in cell transfer delay with the
maximum number VCCs supported on the SUT 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 containing timestamps 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 packets timestamps at the transmitter and receiver ends of
the test device for all VCCs.
Reporting Format:
The results of the CTD/Steady Load/Maximum VCCs test SHOULD be reported
in a form of text, graphs, and histograms.
The text results SHOULD display the numerical values of the CTD. The
values given SHOULD include: time period of test in s, test VPI/VCI
values, total number of cells transmitted and received on each VCC
during the test in positive integers, maximum and minimum CTD on each
VCC during the test in us, and mean CTD on each VCC in us.
The graph results SHOULD display the cell transfer delay 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
cell transfer delay for each VCC in us. 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 histograms SHOULD display the cell transfer delay. There will be one
histogram for each VCC. The x-coordinate SHOULD be the cell transfer
delay in us with at least 256 bins. The y-coordinate SHOULD be the
number of cells observed in each bin.
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 bearer class of the
created VCC MUST also be indicated.
3.2.7.5. CTD/Bursty VBR Load/One VCC
Objective: To determine the SUT variation in cell transfer delay with one
VCC 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]).
3) Send a specific number of IP packets containing timestamps at a
specific VBR 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 packets timestamps at the transmitter and receiver ends of
the test device.
Reporting Format:
The results of the CTD/Bursty VBR Load/One VCC test SHOULD be reported
in a form of text, graph, and histogram.
The text results SHOULD display the numerical values of the CTD. 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, minimum, maximum, and mean
CTD during the test in us.
The graph results SHOULD display the cell transfer delay 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 cell transfer
delay in us. The integration time per point MUST be indicated.
The histogram results SHOULD display the cell transfer delay. The x-
coordinate SHOULD be the cell transfer delay in us with at least 256
bins. The y-coordinate SHOULD be the number of cells observed in each
bin.
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.7.6. CTD/Bursty VBR Load/Twelve VCCs
Objective: To determine the SUT variation in cell transfer delay with
twelve VCCs 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]).
3) Send a specific number of IP packets containing timestamps at a
specific VBR 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 packets timestamps at the transmitter and receiver ends of
the test device for all VCCs.
Reporting Format:
The results of the CTD/Bursty VBR Load/Twelve VCCs test SHOULD be
reported in a form of text, graph, and histograms.
The text results SHOULD display the numerical values of the CTD. The
values given SHOULD include: time period of test in s, test VPI/VCI
values, total number of cells transmitted and received on each VCC
during the test in positive integers, maximum and minimum CTD on each
VCC during the test in us, and mean CTD on each VCC in us.
The graph results SHOULD display the cell transfer delay 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 cell transfer
delay for each VCC in ms. There SHOULD be 12 curves on the graph, one
curves indicated and labeled for each VCC. The integration time per
point MUST be indicated.
The histograms SHOULD display the cell transfer delay. There will be one
histogram for each VCC. The x-coordinate SHOULD be the cell transfer
delay in us with at least 256 bins. The y-coordinate SHOULD be the
number of cells observed in each bin.
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.7.7. CTD/Bursty VBR Load/Maximum VCCs
Objective: To determine the SUT variation in cell transfer delay with the
maximum number VCCs supported on the SUT 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 or VBR 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 containing timestamps at a
specific VBR 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 packets timestamps at the transmitter and receiver ends of
the test device for all VCCs.
Reporting Format:
The results of the CTD/Bursty VBR Load/Maximum VCCs test SHOULD be
reported in a form of text, graphs, and histograms.
The text results SHOULD display the numerical values of the CTD. The
values given SHOULD include: time period of test in s, test VPI/VCI
values, total number of cells transmitted and received on each VCC
during the test in positive integers, maximum and minimum CTD on each
VCC during the test in us, and mean CTD on each VCC in us.
The graph results SHOULD display the cell transfer delay 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
cell transfer delay for each VCC in us. 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 histograms SHOULD display the cell transfer delay. There will be one
histogram for each VCC. The x-coordinate SHOULD be the cell transfer
delay in us with at least 256 bins. The y-coordinate SHOULD be the
number of cells observed in each bin.
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.7.5. CTD/Bursty UBR Load/One VCC
Objective: To determine the SUT variation in cell transfer delay with one
VCC 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]).
3) Send a specific number of IP packets containing timestamps at a
specific UBR 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 packets timestamps at the transmitter and receiver ends of
the test device.
Reporting Format:
The results of the CTD/Bursty UBR Load/One VCC test SHOULD be reported
in a form of text, graph, and histogram.
The text results SHOULD display the numerical values of the CTD. 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, minimum, maximum, and mean
CTD during the test in us.
The graph results SHOULD display the cell transfer delay 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 cell transfer
delay in us. The integration time per point MUST be indicated.
The histogram results SHOULD display the cell transfer delay. The x-
coordinate SHOULD be the cell transfer delay in us with at least 256
bins. The y-coordinate SHOULD be the number of cells observed in each
bin.
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 bearer class of the
created VCC MUST also be indicated.
3.2.7.6. CTD/Bursty UBR Load/Twelve VCCs
Objective: To determine the SUT variation in cell transfer delay with
twelve VCCs 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 a 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 containing timestamps at a
specific UBR 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 packets timestamps at the transmitter and receiver ends of
the test device for all VCCs.
Reporting Format:
The results of the CTD/Bursty UBR Load/Twelve VCCs test SHOULD be
reported in a form of text, graph, and histograms.
The text results SHOULD display the numerical values of the CTD. The
values given SHOULD include: time period of test in s, test VPI/VCI
values, total number of cells transmitted and received on each VCC
during the test in positive integers, maximum and minimum CTD on each
VCC during the test in us, and mean CTD on each VCC in us.
The graph results SHOULD display the cell transfer delay 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 cell transfer
delay for each VCC in ms. There SHOULD be 12 curves on the graph, one
curves indicated and labeled for each VCC. The integration time per
point MUST be indicated.
The histograms SHOULD display the cell transfer delay. There will be one
histogram for each VCC. The x-coordinate SHOULD be the cell transfer
delay in us with at least 256 bins. The y-coordinate SHOULD be the
number of cells observed in each bin.
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 bearer class of the
created VCC MUST also be indicated.
3.2.7.7. CTD/Bursty UBR Load/Maximum VCCs
Objective: To determine the SUT variation in cell transfer delay with the
maximum number VCCs supported on the SUT 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 a 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 containing timestamps at a
specific UBR 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 packets timestamps at the transmitter and receiver ends of
the test device for all VCCs.
Reporting Format:
The results of the CTD/Bursty UBR Load/Maximum VCCs test SHOULD be
reported in a form of text, graphs, and histograms.
The text results SHOULD display the numerical values of the CTD. The
values given SHOULD include: time period of test in s, test VPI/VCI
values, total number of cells transmitted and received on each VCC
during the test in positive integers, maximum and minimum CTD on each
VCC during the test in us, and mean CTD on each VCC in us.
The graph results SHOULD display the cell transfer delay 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
cell transfer delay for each VCC in us. 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 histograms SHOULD display the cell transfer delay. There will be one
histogram for each VCC. The x-coordinate SHOULD be the cell transfer
delay in us with at least 256 bins. The y-coordinate SHOULD be the
number of cells observed in each bin.
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 bearer class of the
created VCC MUST also be indicated.
3.2.7.8. CTD/Mixed Load/Three VCC's
Objective: To determine the SUT variation in cell transfer delay with three
VCC's 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]).
3) Send a specific number of IP packets containing timestamps 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 packets timestamps at the transmitter and receiver ends of
the test device for all VCC's.
Reporting Format:
The results of the CTD/Mixed Load/Three VCC test SHOULD be reported in a
form of text, graph, and histogram.
The text results SHOULD display the numerical values of the CTD. 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, minimum, maximum, and mean
CTD during the test in us.
The graph results SHOULD display the cell transfer delay 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 cell transfer
delay in us. The integration time per point MUST be indicated.
The histogram results SHOULD display the cell transfer delay. The x-
coordinate SHOULD be the cell transfer delay in us with at least 256
bins. The y-coordinate SHOULD be the number of cells observed in each
bin.
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.7.9. CTD/Mixed Load/Twelve VCCs
Objective: To determine the SUT variation in cell transfer delay with
twelve VCCs 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 timestamps 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 packets timestamps at the transmitter and receiver ends of
the test device for all VCCs.
Reporting Format:
The results of the CTD/Mixed Load/Twelve VCCs test SHOULD be reported in
a form of text, graph, and histograms.
The text results SHOULD display the numerical values of the CTD. The
values given SHOULD include: time period of test in s, test VPI/VCI
values, total number of cells transmitted and received on each VCC
during the test in positive integers, maximum and minimum CTD on each
VCC during the test in us, and mean CTD on each VCC in us.
The graph results SHOULD display the cell transfer delay 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 cell transfer
delay for each VCC in ms. There SHOULD be 12 curves on the graph, one
curves indicated and labeled for each VCC. The integration time per
point MUST be indicated.
The histograms SHOULD display the cell transfer delay. There will be one
histogram for each VCC. The x-coordinate SHOULD be the cell transfer
delay in us with at least 256 bins. The y-coordinate SHOULD be the
number of cells observed in each bin.
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.7.10. CTD/Mixed Load/Maximum VCCs
Objective: To determine the SUT variation in cell transfer delay with the
maximum number VCCs supported on the SUT 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. If the maximum
number of VCC's is not divisible by 3, the total for each bearer class
MUST be within 3 VCC's of each other. 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 timestamps 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 packets timestamps at the transmitter and receiver ends of
the test device for all VCCs.
Reporting Format:
The results of the CTD/Mixed Load/Maximum VCCs test SHOULD be reported
in a form of text, graphs, and histograms.
The text results SHOULD display the numerical values of the CTD. The
values given SHOULD include: time period of test in s, test VPI/VCI
values, total number of cells transmitted and received on each VCC
during the test in positive integers, maximum and minimum CTD on each
VCC during the test in us, and mean CTD on each VCC in us.
The graph results SHOULD display the cell transfer delay 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
cell transfer delay for each VCC in us. 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 histograms SHOULD display the cell transfer delay. There will be one
histogram for each VCC. The x-coordinate SHOULD be the cell transfer
delay in us with at least 256 bins. The y-coordinate SHOULD be the
number of cells observed in each bin.
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.
4. Security Considerations. 4. Security Considerations.
As this document is solely for the purpose of providing methodology and As this document is solely for the purpose of providing methodology and
describes neither a protocol nor an implementation, there are no describes neither a protocol nor an implementation, there are no
security considerations associated with this document. security considerations associated with this document.
5. Notices 5. Notices
The IETF takes no position regarding the validity or scope of any The IETF takes no position regarding the validity or scope of any
skipping to change at page 42, line 45 skipping to change at page 127, line 9
PARTICULAR PURPOSE. PARTICULAR PURPOSE.
7. References 7. References
[IETF-RFC-2544] IETF RFC 2544 "Benchmarking Methodology for Network [IETF-RFC-2544] IETF RFC 2544 "Benchmarking Methodology for Network
Interconnect Devices", March, 1999. Interconnect Devices", March, 1999.
[IETF-RFC-2225] IETF RFC 2225 "Classical IP and ARP over ATM", April, [IETF-RFC-2225] IETF RFC 2225 "Classical IP and ARP over ATM", April,
1998. 1998.
[IETF-TERM-ATM] IETF "Terminology for ATM Benchmarking" Internet Draft, [IETF-RFC-2761] IETF RFC 2761 "Terminology for ATM Benchmarking" Draft,
September, 1999. 2000.
[AF-ILMI4.0] ATM Forum Integrated Local Management Interface Version [AF-ILMI4.0] ATM Forum Integrated Local Management Interface Version
4.0, af-ilmi-0065.000, September 1996. 4.0, af-ilmi-0065.000, September 1996.
[AF-TEST-0022] Introduction to ATM Forum Test Specifications, af-test- [AF-TEST-0022] Introduction to ATM Forum Test Specifications, af-test-
0022.00, December 1994. 0022.00, December 1994.
[AF-TM4.0] ATM Forum, Traffic Management Specification Version 4.0, af- [AF-TM4.0] ATM Forum, Traffic Management Specification Version 4.0, af-
tm- 0056.00, April 1996. tm- 0056.00, April 1996.
 End of changes. 

This html diff was produced by rfcdiff 1.23, available from http://www.levkowetz.com/ietf/tools/rfcdiff/