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.5.8. CRC-ER/Bursty UBR Load/Twelve VCCs
Objective: To determine the SUT ratio of lost cells on twelve VCCs in
a transmission in relation to the total cells sent as defined in RFC
2761 "Terminology for ATM Benchmarking".
Procedure:
1) Set up the SUT and test device using the bi-directional
configuration.
2) Configure the SUT and test device with twelve VCCs, using 1 VPI
and 12 VCIs. The VCC MUST be configured as a UBR connection.
The VPI/VCIs MUST not be one of the reserved ATM signaling
channels (e.g., [0,5], [0,16]). The PCR, SCR, and MBS must be
configured using one of the specified traffic descriptors.
3) Send a specific number of IP packets containing one of the
specified bit patterns at a specific rate through the SUT via the
defined test VCCs. All of the VPI/VCI pairs will generate
traffic at the same traffic rate. Since this test is not a
throughput test, the rate should not be greater than 90% of line
rate. The PCR, SCR, and MBS must be indicated. The IP PDUs MUST
be encapsulated in AAL5.
4) Count the IP packets that are transmitted by the SUT on all VCCs
to verify connectivity and load. If the count on the test device
is the same on the SUT, continue the test; else lower the test
device traffic rate until the counts are the same.
5) Record the number of CRC errored cells received per VCC on the
test device for all VCCs.
Reporting Format:
The results of the CRC-ER/Bursty UBR Load/Twelve VCCs test SHOULD
be reported in a form of text and graph.
The text results SHOULD display the numerical values of the CRC-
ER. The values given SHOULD include: time period of test in s,
test VPI/VCI value, total number of cells transmitted and received
on the given VPI/VCI during the test in positive integers, and the
CRC-ER for the entire test.
The graph results SHOULD display the CRC Error ratio values. The
x-coordinate SHOULD be the test run time in either seconds,
minutes or days depending on the total length of the test. The
x-coordinate time SHOULD be configurable. The y-coordinate SHOULD
be the CRC-ER for each VCC. There should be 12 curves on the
graph, on curve indicated and labeled for each VCC. The
integration time per point MUST be indicated.
The results MUST also indicate the packet size in octets, traffic
rate in packets per second, and bearer class as generated by the
test device. The VCC and VPI/VCI values MUST be indicated. The
PCR, SCR, and MBS MUST be indicated. The bearer class of the
created VCC MUST also be indicated.
3.2.5.9. CRC-ER/Bursty UBR Load/Maximum VCCs
Objective: To determine the SUT ratio of lost cells with the maximum
number VCCs supported on the SUT in a transmission in relation to the
total cells sent as defined in RFC2761 "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.5.10. CRC-ER/Bursty Mixed Load/Three VCC
Objective: To determine the SUT ratio of lost cells on three VCC's in
relation to the total cells sent as defined in RFC2761 "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.5.11. CRC-ER/Bursty Mixed Load/Twelve VCCs
Objective: To determine the SUT ratio of lost cells on twelve VCCs in
a transmission in relation to the total cells sent as defined in RFC
2761 "Terminology for ATM Benchmarking".
Procedure:
1) Set up the SUT and test device using the bi-directional
configuration.
2) Configure the SUT and test device with twelve VCC's. Each VCC
MUST be defined as one of the Bearer classes for a total of four
CBR, four UBR and four VBR VCC's. Each VCC SHOULD contain one
VPI/VCI. The VPI/VCI MUST not be one of the reserved ATM
signaling channels (e.g., [0,5], [0,16]).
3) Send a specific number of IP packets containing one of the
specified bit patterns through the SUT via the defined test VCCs.
Each generated VCC stream MUST match the corresponding VCC Bearer
class. All of the VPI/VCI pairs will generate traffic at the
same traffic rate. Since this test is not a throughput test, the
rate should not be greater than 90% of line rate. The IP PDUs
MUST be encapsulated in AAL5.
4) Count the IP packets that are transmitted by the SUT on all VCCs
to verify connectivity and load. If the count on the test device
is the same on the SUT, continue the test; else lower the test
device traffic rate until the counts are the same.
5) Record the number of CRC errored cells received per VCC on the
test device for all VCCs.
Reporting Format:
The results of the CRC-ER/Bursty Mixed Load/Twelve VCCs test
SHOULD be reported in a form of text and graph.
The text results SHOULD display the numerical values of the CRC-
ER. The values given SHOULD include: time period of test in s,
test VPI/VCI value, total number of cells transmitted and received
on the given VPI/VCI during the test in positive integers, and the
CRC-ER for the entire test.
The graph results SHOULD display the CRC Error ratio values. The
x-coordinate SHOULD be the test run time in either seconds,
minutes or days depending on the total length of the test. The
x-coordinate time SHOULD be configurable. The y-coordinate SHOULD
be the CRC-ER for each VCC. There should be 12 curves on the
graph, on curve indicated and labeled for each VCC. The
integration time per point MUST be indicated.
The results MUST also indicate the packet size in octets, traffic
rate in packets per second, and bearer class as generated by the
test device. The VCC and VPI/VCI values MUST be indicated. The
PCR, SCR, and MBS MUST be indicated. The bearer class of the
created VCC MUST also be indicated.
3.2.5.12. CRC-ER/Bursty Mixed Load/Maximum VCCs
Objective: To determine the SUT ratio of lost cells with the maximum
number VCCs supported on the SUT in a transmission in relation to the
total cells sent as defined in RFC2761 "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.6. Cell Transfer Delay (CTD)
3.2.6.1. Test Setup
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).
3.2.6.2. CTD/Steady Load/One VCC
Objective: To determine the SUT variation in cell transfer delay with
one VCC as defined in RFC2761 "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 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.
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.6.3. CTD/Steady Load/Twelve VCCs
Objective: To determine the SUT variation in cell transfer delay with
twelve VCCs as defined in RFC2761 "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.6.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 RFC2761
"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.6.5. CTD/Bursty VBR Load/One VCC
Objective: To determine the SUT variation in cell transfer delay with
one VCC as defined in RFC2761 "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.6.6. CTD/Bursty VBR Load/Twelve VCCs
Objective: To determine the SUT variation in cell transfer delay with
twelve VCCs as defined in RFC2761 "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.6.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 RFC2761
"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.6.8. CTD/Bursty UBR Load/One VCC
Objective: To determine the SUT variation in cell transfer delay with
one VCC as defined in RFC2761 "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.6.9. CTD/Bursty UBR Load/Twelve VCCs
Objective: To determine the SUT variation in cell transfer delay with
twelve VCCs as defined in RFC2761 "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.6.10. 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 RFC2761
"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.6.11. CTD/Mixed Load/Three VCC's
Objective: To determine the SUT variation in cell transfer delay with
three VCC's as defined in RFC2761 "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.6.12. CTD/Mixed Load/Twelve VCCs
Objective: To determine the SUT variation in cell transfer delay with
twelve VCCs as defined in RFC2761 "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.6.13. 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 RFC2761
"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