Real-World Deployment Test
The WaveQoE Real-World Deployment Test accurately replicates the complex interaction of clients, servers and traffic profiles. By creating usage profiles and traffic mixtures that were found to be representative in various network environments, the test measures and reports key application layer metrics that affect end-user Quality of Experience. The test also reports if the Service Level Agreement criteria set by the user for the different application layer traffic types have been met. The real-world networks replicated include: enterprise, health-care, education and retail. Each deployment model is characterized by a mix of clients, servers, client locations and behavior, traffic mix and other characteristics. These clients and servers can be configured to use different security schemes, run various higher layer applications, and utilize different QoS functions of the network. Users may also create their own application and client mixes if so desired.
Layer2/3 triple play QoS:
Objectives:
Measure the capability of the System Under Test (SUT) in performing layer2 QoS when overloaded.
Preloaded Config steps:
1) Clients page has three client types named voice, video and data. All client types are 802.11b/g
clients with DHCP disabled and QoS enabled
2) Server page has one single server with a static IP address.
3) Traffic page has three flows named voice, video and data.
4) All three traffic flows are of type UDP, downlink traffic each with an intended load of 20 Mbps.
5) DSCP values for the voice, video and data flows are set to 48,40 and 0 respectively. The test
assumes the APUT will make DSCP values on the wired side to WMM UPs on the wireless side.
6) On the test page the trail duration is set to 60 secs with the 'Vs time graphs' option checked
and the sample interval set to 1 sec with 'save results' option chosen.
7) On the WaveQoE properties page the Client Mix option is chosen and a client mix is created with
the three client types.
8) Traffic profiles voice, video and data are selected for the respective client types voice, video
and data in the clien mix.
9) The number of clients per AP/port is set to 5 and the percentage of clients for voice, video and
data is set to 20% each inorder to get 1 client of each type.
10) The start times for the data, video and voice clients are set to 0,20 and 40 seconds respectively.
# # Layer2/3三网融合QoS:
# # #目标:
在超载的情况下，测量在测试(SUT)下的系统的性能。
预加载的配置步骤:
1)客户端页面有3个客户端类型，包括语音、视频和数据。所有客户机类型都是802.11 b/g
具有DHCP禁用和QoS的客户端
2)服务器页面有一个带有静态IP地址的单一服务器。
3)流量页面有3个流，名为语音、视频和数据。
4)这三种流量都是类型UDP的，下行流量每一个都有一个预期的20mbps的流量。
5)语音、视频和数据流的DSCP值分别设置为48,40和0。测试
假设APUT将在无线端对WMM UPs进行DSCP值的处理。
6)在测试页面上，跟踪时间设置为60秒，并带有“Vs时间图”选项
样本间隔设置为1秒，并选择“保存结果”选项。
7)在波浪qoe属性页面上，选择客户端混合选项，并创建一个客户端混合
三个客户机类型。
8)流量配置文件、视频和数据被选择为各自的客户端类型的声音，视频
还有克里昂混合的数据。
9)每个api/端口的客户端数量设置为5，以及用于语音、视频的客户机的百分比。
每个输入的数据被设置为20%，以获得每种类型的一个客户端。
10)数据、视频和语音客户机的启动时间分别设置为0-20秒和40秒。
User Config Steps:
1) Load the Config, connect to the chassis, select one ethernet blade and one wireless blade and
scan for the wireless networks on the wireless blade.
2) Go to the clients page and select the right SSID for the voice, video and data client.
3) Set the right security options if security is enabled on the selected SSID.
Running Test and Result Analysis:
1) Run the 60 sec test and observe the client connections, ARPing, Starting and Stopping of the
traffic flows, computation of the results and the report generation.
2) At the end of the test go to the results page on the GUI and click on the 'WaveQoE Vs Time
results' tab and select the flow type to be 'udp' and then plot the forwarding rate over time for all the
flows.
3) Observe how the QoS on the AP works when high priority flows are added to the mix during the
course of the test.
4) Study the pdf report and the overtime results csv files for more detailed information.
Expected Results:
1) When the test starts at 0 secs, the data traffic flow should have the maximum forwarding rate
with zero loss and low latencies.
2) When the video flow starts 20 secs into the test, the SUT should prioritize the video flow over
the data flow, hence resulting in higher forwarding rate, lower packet loss, lower latencies for the
video low when compared to the data flow.
3) When the voice flow starts 40 secs into the test, the SUT should prioritize voice over video and
data.
4) The voice flow should have the highest forwarding rate, lowest latency and lowest packet loss,
followed by the video and data flows in that order.
用户配置步骤:
1)加载配置，连接到底盘，选择一个以太网刀片和一个无线刀片服务器
扫描无线网络上的无线网络。
2)到客户端页面，为语音、视频和数据客户端选择正确的SSID。
3)如果在选择的SSID上启用了安全性，就设置正确的安全选项。
运行测试和结果分析:
1)运行60秒的测试，观察客户端连接，ARPing，启动和停止
交通流量，计算结果和报告生成。
2)在测试结束时，到GUI上的结果页面，点击“波卡比Vs时间”
“结果”选项卡并选择流类型为“udp”，然后在所有时间内绘制转发率。
流。
3)观察当高优先级流被添加到混合时，AP的QoS是如何工作的
的测试。
4)研究pdf报告和加班结果的csv文件以获得更详细的信息。
预期结果:
1)当测试从0秒开始时，数据流量流应该具有最大的转发速率
零损失和低延迟。
2)当视频流开始20秒进入测试时，SUT应该优先考虑视频流
数据流，从而导致更高的转发率，更低的包丢失，更低的延迟
与数据流相比，视频很低。
3)当声音流开始40秒进入测试时，SUT应该优先考虑声音而不是视频。
数据。
4)语音流应该具有最高的转发率、最低的延迟和最低的包丢失，
然后是视频和数据流按顺序排列。
WMM/Legacy power save:
Objectives:
1) Measure the performance of the System Under Test (SUT) in buffering data traffic for WMM/Legacy
power save clients.
2) Comparing the performance of clients operating in no power-save, legacy power save and WMM
Powersave modes.
Preloaded Config steps:
1) Clients page has five client types named awakeClient, legacyPs2, legacyPs10, wmmPs2 and wmmPs10.
All client types are 802.11b/g clients with DHCP disabled and QoS enabled.
2) In the '802.11 clients options' section, the following settings are made for each client type.
a) Power save option is disabled for the 'awakeclient' client
b) Power save enabled and listen interval is set to 10 for the 'legacyPs10' client
c) Power save enabled and listen interval is set to 2 for the 'legacyPs2' client
d) Power save enabled,listen interval is set to 10 and WMM powersave is enabled with WMM
uAPSD AC flags set to 15 and SP length set to 3 for the 'wmmPs10' client
e) Power save enabled,listen interval is set to 2 and WMM powersave is enabled with WMM uAPSD
AC flags set to 15 and SP length set to 3 for the 'wmmPs2' client
3) Server page has one single server with a static IP address.
4) Traffic page has one traffic profile called UDPTraffic with 2000 Kbps UDP traffic load in the
downlink (Ethernet to Wireless).
5) On the test page the trail duration is set to 30 secs with the 'Vs time graphs' option checked
and the sample interval set to 1 sec with 'save results' option chosen.
6) On the WaveQoE properties page the Client Mix option is chosen and a client mix is created with
the five client types.
7) The same traffic profile (UDPTraffic) is selected for all the 5 client types in the client mix.
8) The number of clients per AP/port is set to 5 and the percentage of clients for each client type
is set to 20% each inorder to get 1 client of each type.
User Config Steps:
1) Load the Config, connect to the chassis, select one ethernet blade and one wireless blade and
scan for the wireless networks on the wireless blade.
2) Go to the clients page and select the right SSID for all the 5 client types.
3) Set the right security options if security is enabled on the selected SSID.
Running Test and Result Analysis:
1) Run the 30 sec test and observe the client connections, ARPing, Starting and Stopping of the
traffic flows, computation of the results and the report generation.
2) At the end of the test go to the results page on the GUI and click on the 'WaveQoE Vs Time
results' tab and select the flow type to be 'udp' and then plot the forwarding rate over time for all the
flows.
3) Observe the forwarding rate over time for all the 5 flows, each flow going to a different client
from the same server.
4) Study the pdf report and the overtime results csv files for more detailed information.
Expected Results:
1) As the 'awakeclient' is not set to go to sleep at anytime during the test, the traffic flow to
this client should have the highest forwarding rate, least latency and least packet loss.
2) Since WMM power save is considered to be a more efficient method of power save, the flows on the
clients with WMM power save should perform better than the flows on the legacy power save clients.
3) Since the amount of the time the client goes to sleep is directly proportional to the listen
interval, the flows on the clients with the smaller listen interval should perform better than the flows
on clients with larger listen interval.
个子/遗留省电:
目的:
1)度量在测试中(SUT)下的系统的性能，在wm/遗赠的缓冲数据流量中
省电的客户。
2)比较在没有电源的情况下运行的客户机的性能、遗留的电源和WMM的性能
Powersave模式。
预加载的配置步骤:
1)客户端页面有5个客户端类型，包括觉醒、legacyPs2、legacyPs10、wmmPs2和wmmPs10。
所有客户机类型都是802.11 b/g客户端，并且启用了DHCP禁用和QoS。
2)在“802.11客户端选项”一节中，为每个客户端类型设置了以下设置。
a)电源保存选项是为“醒着”的客户端禁用的
b)启用了电源，并且监听间隔为“legacyPs10”客户端设置为10
c)电源保存和监听间隔为“legacyPs2”客户端设置为2
d)电源保存，监听间隔设置为10，WMM启用WMM powersave
为“wmmPs10”客户端设置的uAPSD AC标志为15和SP长度为3
e)电源保存，监听间隔设置为2，WMM uAPSD启用WMM powersave
为“wmmPs2”客户端设置为15和SP长度设置为3的AC标志
3)服务器页面有一个带有静态IP地址的单一服务器。
4)流量页面有一个名为udp浏览量的流量配置文件，其中包含2000 Kbps UDP流量负载
下行(无线以太网)。
5)在测试页面上，跟踪时间设置为30秒，带有“Vs时间图”选项
样本间隔设置为1秒，并选择“保存结果”选项。
6)在波浪qoe属性页上选择客户混合选项，并创建一个客户端混合
5客户端类型。
7)在客户端混合中为所有5个客户端选择相同的流量配置文件(udf)。
8)每个api/端口的客户端数量设置为5，每个客户端类型的客户端百分比
设置为每个输入的20%，以获得每种类型的1个客户端。
用户配置步骤:
1)加载配置，连接到底盘，选择一个以太网刀片和一个无线刀片服务器
扫描无线网络上的无线网络。
2)转到客户端页面，并为所有5个客户端选择正确的SSID。
3)如果在选择的SSID上启用了安全性，就设置正确的安全选项。
运行测试和结果分析:
1)运行30秒的测试，观察客户端连接，ARPing，启动和停止
交通流量，计算结果和报告生成。
2)在测试结束时，到GUI上的结果页面，点击“波卡比Vs时间”
“结果”选项卡并选择流类型为“udp”，然后在所有时间内绘制转发率。
流。
3)在所有5个流的时间内观察转发率，每个流流向一个不同的客户端
从相同的服务器。
4)研究pdf报告和加班结果的csv文件以获得更详细的信息。
预期结果:
1)当“醒着”的人在测试的任何时候都不准备睡觉，交通会流到
此客户端应该具有最高的转发率、最小的延迟和最小的包丢失。
2)由于WMM的功率节约被认为是一种更有效的节能方法，在
使用WMM power save的客户机应该比传统的power save客户机上的流更好。
3)因为客户睡觉的时间和倾听的时间成正比
间隔，客户端与较小的侦听间隔的流应该比流的性能更好
对于有较大的侦听间隔的客户端。
FTP goodput:
Objectives:
Measure the FTP Goodput of a single FTP traffic stream on the SUT.
Preloaded Config steps:
1) Clients page has one client type named FTPClient. All client types are 802.11b/g clients with
DHCP disabled and QoS disabled
2) Server page has one single server named FTPserver with a static IP address.
3) Traffic page one single downlink (Ethernet to Wireless) FTP traffic stream with 1500 layer2
frame size, destination layer4 port number set to 21.
4) On the test page the trail duration is set to 30 secs.
5) On the WaveQoE properties page the Traffic Mix option is chosen and a traffic mix is created
with the single traffic stream to the single FTP client.The load per port is set to 30 Mbps
User Config Steps:
1) Load the Config, connect to the chassis, select one ethernet blade and one wireless blade and
scan for the wireless networks on the wireless blade.
2) Go to the clients page and select the right SSID for the FTPClient client.
3) Set the right security options if security is enabled on the selected SSID.
Running Test and Result Analysis:
1) Run the 30 sec test and observe the client connections, ARPing, Starting and Stopping of the
traffic flows, computation of the results and the report generation.
2) At the end of the test look at the FTP goodput value in the summary results table.
Expected Results:
1) The achieved goodput should be close to the theoritical layer4 goodput value on the wireless
channel.
2) The theoritical values can be computed using the Veriwave Therotical Throughput Calculator tool
available for free download at www.veriwave.com
http goodput:
Objectives:
Measure the HTTP Goodput of a single HTTP traffic stream on the SUT.
Preloaded Config steps:
1) Clients page has one client type named HTTPClient. All client types are 802.11b/g clients with
DHCP disabled and QoS disabled
2) Server page has one single server named HTTPserver with a static IP address.
3) Traffic page one single downlink (Ethernet to Wireless) HTTP traffic stream with 1500 layer2
frame size, destination layer4 port number set to 80.
4) On the test page the trail duration is set to 30 secs.
5) On the WaveQoE properties page the Traffic Mix option is chosen and a traffic mix is created
with the single traffic stream to the single HTTP client.The load per port is set to 30 Mbps
User Config Steps:
1) Load the Config, connect to the chassis, select one ethernet blade and one wireless blade and
scan for the wireless networks on the wireless blade.
2) Go to the clients page and select the right SSID for the HTTPClient client.
3) Set the right security options if security is enabled on the selected SSID.
Running Test and Result Analysis:
1) Run the 30 sec test and observe the client connections, ARPing, Starting and Stopping of the
traffic flows, computation of the results and the report generation.
2) At the end of the test look at the HTTP goodput value in the summary results table.
Expected Results:
1) The achieved goodput should be close to the theoritical layer4 goodput value on the wireless
channel.
2) The theoritical values can be computed using the Veriwave Therotical Throughput Calculator tool
available for free download at www.veriwave.com
FTP goodput:
目的:
测量SUT上一个FTP传输流的FTP。
预加载的配置步骤:
1)客户端页面有一个名为FTPClient的客户端类型。所有客户机类型都是802.11 b/g客户机
禁用DHCP和QoS禁用
2)服务器页面有一个名为FTPserver的服务器，它具有一个静态IP地址。
3)流量页面一个单一的下行链路(以太网到无线)FTP流量流，有1500个layer2
帧大小，目的地的端口4端口号设置为21。
4)在测试页面上，跟踪时间设置为30秒。
5)在波qoe属性页上，选择了交通混合选项，并创建了一个交通组合
将单一的流量流传输到单一的FTP客户端。每个端口的负载设置为30 Mbps
用户配置步骤:
1)加载配置，连接到底盘，选择一个以太网刀片和一个无线刀片服务器
扫描无线网络上的无线网络。
2)转到客户端页面，并为FTPClient客户端选择正确的SSID。
3)如果在选择的SSID上启用了安全性，就设置正确的安全选项。
运行测试和结果分析:
1)运行30秒的测试，观察客户端连接，ARPing，启动和停止
交通流量，计算结果和报告生成。
2)在测试的最后，在总结结果表中查看FTP goodput值。
预期结果:
1)所取得的好货应该接近于理论上的对无线网络的价值
通道。
2)理论值可以使用Veriwave的传输量计算器工具进行计算
可以在www.veri波浪网上免费下载。
http goodput:
目的:
测量SUT上单个HTTP流量流的HTTP Goodput。
预加载的配置步骤:
1)客户端页面有一个名为HTTPClient的客户机类型。所有客户机类型都是802.11 b/g客户机
禁用DHCP和QoS禁用
2)服务器页面有一个名为HTTPserver的服务器，它有一个静态IP地址。
3)流量页面一个单一的下行链路(以太网到无线)HTTP流量流，有1500个layer2
帧大小，目的地的端口4端口号设置为80。
4)在测试页面上，跟踪时间设置为30秒。
5)在波qoe属性页上，选择了交通混合选项，并创建了一个交通组合
将单一的流量流发送到单个HTTP客户端。每个端口的负载设置为30 Mbps
用户配置步骤:
1)加载配置，连接到底盘，选择一个以太网刀片和一个无线刀片服务器
扫描无线网络上的无线网络。
2)转到客户端页面，并为HTTPClient客户端选择正确的SSID。
3)如果在选择的SSID上启用了安全性，就设置正确的安全选项。
运行测试和结果分析:
1)运行30秒的测试，观察客户端连接，ARPing，启动和停止
交通流量，计算结果和报告生成。
2)在测试的最后，在总结结果表中查看HTTP goodput值。
预期结果:
VOIP admission control
Objectives:
Measure the number of voice calls the System Under Test (SUT) can admit using WMM Admission
Control.
Preloaded Config steps:
1) Clients page has one client type named voipClient. All client types are 802.11b/g clients with
DHCP disabled and QoS enabled.
2) Server page has one single server named voipserver with a static IP address.
3) Traffic page has one single bi-directional VOIP traffic stream with codec type set to G711 and
SIP signaling turned ON in the L3-7 properties section.Acceptable R-value is set to 78.
4) In the QoS properties section of the traffic page the WMM and 802.1p priorities are set to 7 and
DSCP value is set to 56.
5) Admission Control is turned on with TID set to 7, Nominal MSDU size set to 280, min PHY rate set
to 2 Mbps, Mean data rate 200 Kbps and surplus bandwidth allowance 100%
6) On the test page the trail duration is set to 10 secs.
7) On the WaveQoE properties page the Client Mix option is chosen and a client mix is created with
the single voip traffic stream to the single voip client.
8) The client load is set to a linear search mode with start number of clients set to 1, end number
set to 75 and client step set to 1.
9) Both 'Continue when Flow admission control fails' and 'Continue when test fails' options are
unchecked to make sure the test stops when admission control or SLA on any traffic stream fails.
User Config Steps:
1) Load the Config, connect to the chassis, select one ethernet blade and one wireless and scan
for the wireless networks on the wireless blade.
2) Go to the clients page and select the right SSID for the voipClient client.
3) Set the right security options if security is enabled on the selected SSID.
Running Test and Result Analysis:
1) Run the test and observe the client connections, ARPing, Starting and Stopping of the traffic
flows, the linear search, computation of the results and the report generation.
2) At the end of the test look check the final report that is generated and this report will show
the max number of voice calls supported that are successfully admitted by the SUT and meet the SLA
requirements.
Expected Results:
1) The max number of calls supported should be close the therotical max number of voice calls that
can be supported on the link.
2) The theoritical values can be computed using the Veriwave Therotical Throughput Calculator tool
available for free download at www.veriwave.com.
unicast video sessions:
Objectives:
Measure the number of unicast video sessions the System Under Test (SUT) can support with
acceptable performance levels.
Preloaded Config steps:
1) Clients page has one client type named videoClient. All client types are 802.11b/g clients with
DHCP disabled and QoS enabled.
2) Server page has one single server named videoserver with a static IP address.
3) Traffic page has one single downlink MPEG2 video traffic stream with codec type set to MPEG2 in
the L3-7 properties section.Acceptable MDI score is set to DF = 50 msecs and MLR = 1%.
4) In the QoS properties section of the traffic page the WMM and 802.1p priorities are set to 7 and
DSCP value is set to 56.
5) On the test page the trail duration is set to 10 secs.
6) On the WaveQoE properties page the Client Mix option is chosen and a client mix is created with
the single video traffic stream to the single video client.
7) The client load is set to a linear search mode with start number of clients set to 1, end number
set to 50 and client step set to 1.
8) 'Continue when test fails' option is unchecked to make sure the test stops when SLA on any
traffic stream fails.
User Config Steps:
1) Load the Config, connect to the chassis, select one ethernet blade and one wireless and scan
for the wireless networks on the wireless blade.
2) Go to the clients page and select the right SSID for all the clients.
3) Set the right security options if security is enabled on the selected SSID.
Running Test and Result Analysis:
1) Run the test and observe the client connections, ARPing, Starting and Stopping of the traffic
flows, the linear search, computation of the results and the report generation.
2) At the end of the test look check the final report that is generated and this report will show
the max number of unicast video sessions supported that meet the SLA requirements.
Expected Results:
1) User to decide expected results.
Near/Far Client:
Objectives:
1) Measure the performance of the System Under Test (SUT) with client at different distances from
the AP.
2) Comparing the performance of near and far clients.
Preloaded Config steps:
1) Clients page has three client types named Near_Client, Medium_Client and Far_Client. All client
types are 802.11b/g clients with DHCP disabled and QoS disabled.
2) In the '802.11 clients options' section, the following settings are made for each client type.
a) Trasmit power set to -6dBm, Frame Error Rate set to 0%, Flow Phyrate set to 54 Mbps and
client connection Phyrate set to 24 Mbps for "Near_Client"
b) Trasmit power set to -20dBm, Frame Error Rate set to 30%, Flow Phyrate set to 36 Mbps and
client connection Phyrate set to 12 Mbps for "Medium_Client"
c) Trasmit power set to -40dBm, Frame Error Rate set to 60%, Flow Phyrate set to 12 Mbps and
client connection Phyrate set to 6 Mbps for "Far_Client"
3) Server page has one single server with a static IP address.
4) Traffic page has one traffic profile called UDPTraffic with 1000 Kbps UDP traffic load in the
downlink (Ethernet to Wireless).
5) On the test page the trail duration is set to 30 secs.
6) On the WaveQoE properties page the Client Mix option is chosen and a client mix is created with
the three client types.
7) The same traffic profile (UDPTraffic) is selected for all the 3 client types in the clien mix.
8) The number of clients per AP/port is set to 5 and the percentage of clients for each client type
is set to 20% each inorder to get 1 client of each type.
User Config Steps:
1) Load the Config, connect to the chassis, select one ethernet blade and one wireless blade and
scan for the wireless networks on the wireless blade.
2) Go to the clients page and select the right SSID for all the 3 client types.
3) Set the right security options if security is enabled on the selected SSID.
Running Test and Result Analysis:
1) Run the 30 sec test and observe the client connections, ARPing, Starting and Stopping of the
traffic flows, computation of the results and the report generation.
3) Observe the difference in forwarding rates for all the 3 flows, each flow going to a different
client from the same server.
Expected Results:
1) The forwarding rate of the near_client should be the highest followed by the Medium_client and
the far_client.
2) The latencies and packet loss of the near_client should be the least followed by the
Medium_client and the far_client.
802.11b/g/n mixed client
Objectives:
1) Measure the performance of the System Under Test (SUT) in handling 802.11b, 802.11g and 802.11n
clients simultaneously in the same BSS.
2) Comparing the performance of 802.11b, 802.11g and 802.11n clients.
Preloaded Config steps:
1) Clients page has four client types named 11b, 11g, 11n_no_agg and 11n_agg. All client types have
DHCP disabled.
2) In the '802.11 clients options' section, the following settings are made for each client type.
a) 11b client is set in 802.11b mode
b) 11g client is set in 802.11g mode
c) 11n_no_agg client is set in 2X2 MIMO 802.11n mode with AMPDU aggregation option unchecked
d) 11n_agg client is set in 2X2 MIMO 802.11n mode with AMPDU aggregation option checked
3) Server page has one single server with a static IP address.
4) Traffic page has one traffic profile called UDPTraffic with 20000 Kbps UDP traffic load in the
downlink (Ethernet to Wireless).
5) On the test page the trail duration is set to 30 secs.
6) On the WaveQoE properties page the Client Mix option is chosen and a client mix is created with
the four client types.
7) The same traffic profile (UDPTraffic) is selected for all the 4 client types in the client mix.
8) The number of clients per AP/port is set to 5 and the percentage of clients for each client type
is set to 20% each inorder to get 1 client of each type.
User Config Steps:
1) Load the Config, connect to the chassis, select one ethernet blade and one wireless blade and
scan for the wireless networks on the wireless blade.
2) Go to the clients page and select the right SSID for all the 4 client types.
3) Set the right security options if security is enabled on the selected SSID.
Running Test and Result Analysis:
1) Run the 30 sec test and observe the client connections, ARPing, Starting and Stopping of the
traffic flows, computation of the results and the report generation.
2) Observe the forwarding rate for all the 4 flows, each flow going to a different client from the
same server.
Expected Results:
1) The forwarding rate of the "11n_agg" client should be the highest followed by the "11n_no_agg",
"11g" and "11b" clients in that order.
2) The latencies and packet loss of the "11n_agg" client should be the least followed by the
"11n_no_agg", "11g" and "11b" clients in that order.
VOIP允许控制
目的:
测量被测系统的语音呼叫数量(SUT)可以承认使用WMM的承认
控制。
预加载的配置步骤:
1)客户端页面有一个名为voipClient的客户机类型。所有客户机类型都是802.11 b/g客户机
启用了DHCP禁用和QoS。
2)服务器页面有一个名为voipserver的服务器，它有一个静态IP地址。
3)交通页面有一个单一的双向VOIP交通流，它的编码类型设置为G711和G711。
在l3-7属性部分中出现了SIP信号转换。可接受的r值设置为78。
4)在流量页面的QoS属性部分中，WMM和802.1 p优先级被设置为7
DSCP值被设置为56。
5)使用TID设置为7，名义上的MSDU的大小设置为280，最小值设置
2 Mbps，平均数据速率为200 Kbps和剩余带宽，100%
6)在测试页面上，跟踪时间设置为10秒。
7)在波浪qoe属性页面上，选择客户端混合选项，并创建一个客户端混合
单一voip客户端的单一voip通信流。
8)客户端负载被设置为线性搜索模式，并将客户端设置为1、结束数
设置为75，客户端步骤设置为1。
9)“当流进入控制失败”和“在测试失败时继续”选项都是“继续”
未经检查，确保测试在进入控制或任何流量流的SLA失败时停止。
用户配置步骤:
1)加载配置，连接到底盘，选择一个以太网刀片和一个无线和扫描
无线网络上的无线网络。
2)转到客户端页面，并为voipClient客户端选择正确的SSID。
3)如果在选择的SSID上启用了安全性，就设置正确的安全选项。
运行测试和结果分析:
1)运行测试并观察客户端连接、ARPing、启动和停止流量
流量、线性搜索、结果的计算和报告生成。
2)在测试结束时，检查生成的最终报告，这个报告将显示
最大的语音呼叫支持被SUT成功地承认并满足SLA
要求。
预期结果:
1)所支持的最大的电话号码应该是关闭语音通话的最大数量
可以在链接上支持。
2)理论值可以使用Veriwave的传输量计算器工具进行计算
可在www.veri波浪网上免费下载。
单播视频会议:
目的:
测量被测系统(SUT)可以支持的单播视频会话的数量
可接受的性能水平。
预加载的配置步骤:
1)客户端页面有一个名为可视性的客户端类型。所有客户机类型都是802.11 b/g客户机
启用了DHCP禁用和QoS。
2)服务器页面有一个名为videoserver的服务器，带有一个静态IP地址。
3)流量页面有一个单一的下行链路MPEG2视频流量流，其中的codec类型设置为MPEG2
L3-7属性的一部分。可接受的MDI分数设置为DF=50 msecs和MLR=1%。
4)在流量页面的QoS属性部分中，WMM和802.1 p优先级被设置为7
DSCP值被设置为56。
5)在测试页面上，跟踪时间设置为10秒。
6)在波浪qoe属性页上选择客户混合选项，并创建一个客户端混合
单一视频传输流到单个视频客户端。
multicast video performance:
Objectives:
1) Measure the performance of the System Under Test (SUT) in handling multiple Multicast Video
sessions.
2) Test emulates a real world scenario of a home having 3 wireless TVs each of them viewing upto 2
TV channels all connected to the same wireless Access Point.
Preloaded Config steps:
1) Clients page has 3 clients WirelessTV1, wirelessTV2 and wirelessTV3. All client types are
802.11b/g clients with DHCP disabled and QoS enabled.
2) Server page has one single server named videoServer with a static IP address.
3) Traffic page has 12 multicast traffic streams, 6 of the RTPVideo streams and 6 RTPAudio stream
each forming a seperate multicast group.
4) Each RTPVideo stream is set to 1500 byte frame size with a 600 Kbps Intened load per session,
with an acceptable delay factor of 50 msecs and acceptable MLR of 1% and codec type set to H.261 in the
layer4-7 parameters.
5) Each RTPAudio stream is set to 1500 byte frame size with a 72 Kbps Intened load per session with
codec type chosen as G711 in the layer4-7 parameters.
6) In the QoS properties section the 802.1p priorities are set to 5 and DSCP value is set to 40 for
all traffic flows.
7) Each TV channel is cosidered as a combination of 1 multicast RTPVideo stream for the video
portion and 1 multicast RTPAudio stream for the audio portion of the program.
8) Everytime the user switched channels the wirelessTV would join the multicast groups for the
respective audio and video sessions.
9) Each TV can be considered to have joined two multicast audio and video groups each at any given
time (the current channel being watched and the last viewed channel).
10) On the test page the trail duration is set to 30 secs.
11) On the WaveQoE properties page the Client Mix option is chosen and a client mix is created with
the 3 wireless TV clients.
12) The IPTV_video_stream1, IPTV_audio_stream1,IPTV_video_stream2 and IPTV_audio_stream2 are chosen
as traffic profiles for wirelessTV1 and the remaning traffic profiles are chosen for wirelessTV2 and
wirelessTV3 clients in the same fashion.
13) The number of clients per AP/port is set to 5 and the percentage of clients for each client
type is set to 20% each inorder to get 1 client of each type.
多播视频性能:
目的:
1)在处理多个多播视频的测试中(SUT)测量系统的性能
会话。
2)测试模拟一个真实的世界场景一个家庭有3个无线电视每个人都看2个
电视频道都连接到相同的无线接入点。
预加载的配置步骤:
1)客户端页面有3个客户端，无线esstv1，无线和无线。所有客户端类型
具有DHCP禁用和QoS的802.11 b/g客户端。
2)服务器页面有一个名为videoServer的服务器，带有一个静态IP地址。
3)交通页面有12个多播流量，6个rtp视频流和6个RTPAudio流
每一个都形成一个独立的多播组。
4)每个rtp视频流被设置为1500字节帧大小，每个会话的负载为600 Kbps，
可接受的延迟因子为50 msecs，可接受的MLR为1%和codec类型为h。261年
layer4-7参数。
5)每个rtp音频流被设置为1500字节帧大小，每个会话的负载为72 Kbps。
在layer4-7参数中选择的G711类型为G711。
6)在QoS属性部分中，802.1 p优先级设置为5，DSCP值被设置为40
所有流量。
7)每一个电视频道都被作为一组多播的rtp视频流结合在一起。
部分和一组多播的rtp音频流用于程序的音频部分。
8)当用户切换频道时，无线电视将加入多播组
各自的音频和视频会话。
9)每个电视可以被认为加入了两个多播音频和视频组。
时间(正在观看的当前频道和最后一个观看的频道)。
10)在测试页面上，跟踪时间设置为30秒。
11)在波qoe属性页上，选择客户端混合选项，并创建一个客户端混合
3个无线电视客户。
12)选择了iptvvideostream1、iptv音频流、iptvvideostream2和iptv音频流。
当无线网络和重新配置的流量配置文件被选择为无线网络的时候。
用同样的方式，无线的客户端。
13)每个客户端/端口的客户端数量设置为5，每个客户端客户端百分比
类型设置为每个输入的20%，以获得每种类型的1个客户端。
User Config Steps:
1) Load the Config, connect to the chassis, select one ethernet blade and one wireless blade and
scan for the wireless networks on the wireless blade.
2) Go to the clients page and select the right SSID for all the clients.
3) Set the right security options if security is enabled on the selected SSID.
Running Test and Result Analysis:
1) Run the test and observe the client connections, ARPing, Starting and Stopping of the traffic
flows, computation of the results and the report generation.
2) Analyze the report to check if all the traffic flows met the SLA.
Expected Results:
1) User to decide expected results.
用户配置步骤:
1)加载配置，连接到底盘，选择一个以太网刀片和一个无线刀片服务器
扫描无线网络上的无线网络。
2)到客户端页面，为所有客户选择正确的SSID。
3)如果在选择的SSID上启用了安全性，就设置正确的安全选项。
运行测试和结果分析:
1)运行测试并观察客户端连接、ARPing、启动和停止流量
流量，计算结果和报告生成。
2)分析报告以检查所有的流量是否满足SLA。
预期结果:
1)用户来决定预期的结果。
