APPLICATION NOTE

Using the Azimuth MIMO Range ACE

Benchmark Test

Revision 1.0

Azimuth Systems, Inc.

31 Nagog Park
Acton, MA 01720
Tel. 978.263.6610
Fax 978.263.5352
www.azimuthsystems.com

2006 Azimuth Systems, Inc.

Pub. No. 102706, Rev. v1.0, 10/27/06

Printed in USA

Copyright 2006 Azimuth Systems, Inc. All rights reserved.

Azimuth, Azimuth DIRECTOR, SpyNIC, ACE, ADEPT, RadioProof and testMAC are trademarks of
Azimuth Systems, Inc. Microsoft and Windows are trademarks of Microsoft Corporation. Adobe, Acrobat,
and Acrobat Reader are trademarks of Adobe Systems Incorporated. All other third-party trademarks and
service marks referred to in these materials are the property of their owners.
No part of this documentation may be reproduced in any form or by any means or used to make any
derivative work (such as translation, transformation, or adaptation) without written permission from
Azimuth Systems, Inc. Azimuth Systems, Inc. provides this documentation AS IS, without warranty,
term, or condition of any kind, either implied or expressed, including, but not limited to, the implied
warranties, terms, or conditions of merchantability, satisfactory quality, non-infringement and fitness for a
particular purpose. Azimuth Systems, Inc. reserves the right to make changes to equipment design or
program components described in this documentation, as progress in engineering, manufacturing methods,
or other circumstances may warrant. No responsibility is assumed for the use of Azimuth Systems, Inc.
software or hardware, all rights, obligations and remedies related to which are as set forth in the applicable
sales and license agreements.
Azimuth Systems, Inc.
31 Nagog Park
Acton, MA 01720
Tel. 978.263.6610
Fax 978.263.5352
www.azimuthsystems.com
Technical Publications Doc. No. 102706, Rev. v1.0
Published 10/27/06
Printed in United States of America

Using the Azimuth MIMO Range ACE Benchmark Test

i-ii
Rev. v1.0

Table of Contents
Running the Azimuth MIMO Range ACE Benchmark Test
Overview .............................................................................................................................. 1-1
Theory of Operation ............................................................................................................. 1-1
Required Hardware/Software .............................................................................................. 1-2
Physical Configuration ........................................................................................................ 1-3
Setting Up the Access Point (AP) ........................................................................................ 1-4
Setting Up the Azimuth Wireless Standalone Client (WSC) ................................................. 1-7
Setting Up and Running the Azimuth MIMO Range ACE Benchmark Test ........................ 1-8
Troubleshooting the Test .................................................................................................... 1-17
Reviewing Test Results ...................................................................................................... 1-19
Log Tab ........................................................................................................................ 1-19
..................................................................................................................................... 1-20
Graphs Tab - Throughput ............................................................................................ 1-21
Graphs Tab RSSI ...................................................................................................... 1-22
Graphs Tab Packet Errors ........................................................................................ 1-23
Graphs Tab Data Rate .............................................................................................. 1-24
Zooming In to a Results Graph .................................................................................... 1-24
Viewing and Comparing Test Results in Azimuth Studio ............................................. 1-25
Appendix A: Azimuth MIMO Range ACE Benchmark Test Parameters
Common Graphic User Interface (GUI) Elements ............................................................... A-1
Info Tab ............................................................................................................................... A-1
Setup General Tab ........................................................................................................... A-2
Setup Traffic Tab .............................................................................................................. A-4
Setup - Channel Tab ........................................................................................................... A-7
Setup - Lib Connections Tab ............................................................................................... A-8
Setup Security Tab ........................................................................................................... A-8
Configuration Security Parameters ............................................................................... A-9
Setup - AP Config Tab ....................................................................................................... A-12

Using the Azimuth MIMO Range ACE Benchmark Test

i-iii
Rev. v1.0

Overview

Running the Azimuth MIMO Range ACE

Benchmark Test
Overview
From the CE guide... The ACE is a multi-path MIMO channel emulator designed for 802.11 applications.
It is designed to work with the emerging 802.11n standard as well the 802.11a, b and g standards. The ACE
can emulate multiple antenna channel models in indoor MIMO WLANs defined by the 802.11n High
Throughput Task Group (TGn) in the document IEEE P802.11 Wireless LANs, TGn Channel Models (May
10, 2004).1
The ACE is designed to be an easy-to-use test system. The front panel has two groups of four RF ports.
These ports are bi-directional and allow for direct connection to 802.11 devices. The emulator can be
configured to operate on any combination of ports supporting 1x1 SISO up to 4x4 MIMO. The ACE can be
configured to operate with TGn channel models A-F, with user defined variables such as antenna spacing
and line-of-sight components. In addition, a variable attenuator is provided to allow for virtually
positioning the distance or path loss between the connected devices.
The ACE is designed to be used as a system with the Azimuth N-Series WLAN Test Platform. Command
and control of the ACE is performed using the Azimuth DIRECTOR.

Theory of Operation
MIMO Range ACE measures the device throughput as a function of range. Range is controlled by virtually
positioning the STAUT relative to the APUT by means of the Azimuth Smart Motion attenuators. This flat
channel attenuation (or fading of the signal) provides a simulated range between the devices.
Throughput in an 802.11 system is determined by the transmit data rate of the transmit station and the
receiver performance of the receiving station. As the attenuation between the devices is increased, the
signal strength at the receiver decreases. Eventually the signal reaches a point where it can no longer be
received without error. When this occurs, the receiving DUT will not send an acknowledgement (ACK) in
response to the frame it received. The transmitting station, in response to no receipt of ACK, determines if
it must decrease the transmit rate. Decreasing the transmit rate decreases the modulation used by the
transmitter. The lower modulation rate results in a signal that requires less overall signal-to-noise ratio
(SNR) at the receiver to be decoded properly. Thus, the receiver is able to properly decode the signal over
an extended further decrease in signal strength. The test continues increasing the attenuation until the
station is disassociated.

1.The ACE is based on a MatLab implementation of the TGn channel models, the work of which was supported by
European Union IST Research Project IST-2000-30148 I-METRA (Multi Element Transmit and Receive Antennas).
See A Stochastic MIMO Radio Channel Model with Experimental Validation, IEEE Journal on Selected Areas in
Communications, Volume 20, No. 6, August 2002.

Using the Azimuth MIMO Range ACE Benchmark Test

1-1
Rev. v1.0

Required Hardware/Software

In a single input / single output (SISO) environment, a single RF path with Smart Motion attenuation is
used to control the signal strength. In a multi input / multi output (MIMO) environment, multiple RF paths
with Smart Motion attenuators are required.
A typical MIMO device is characterized as an NxM configuration of MIMO, where N indicates the
number of transmitters and M indicates the number of receivers. With a MIMO device that implements
spatial multiplexing, multiple simultaneous data transmissions occur carrying unique data in each stream
(N streams). The M receivers are used to receive and recover the original transmitted streams.

Required Hardware/Software
The hardware and software requirements for the Azimuth MIMO Range ACE Benchmark Test include the
following:
Azimuth-Provided

Azimuth DIRECTOR 4.6.0

Azimuth Benchmark Test and Tcl Library CD (release 4.3 or higher)

NOTE: Contact your Azimuth sales representative for information on licensing the application.

One (1) Azimuth chassis (ACE 400NB)

One (1) Azimuth RadioProof Enclosure (Model RPE-402)
One (1) RadioProof Enclosure (Model RPE-401/421) (STAUT is to be tested in a user-provided laptop)
RF Cable Kit (see your Azimuth Sales Representative for more information)

Optional Equipment:

TMM for Front Panel Ethernet L2 or L3 Traffic Endpoint.

Customer-Provided

One (1) AP
One (1) Station
One (1) Ethernet 10/100 switch (to connect the STAUT in a Wireless Standalone Client (WSC) to the
Bus-Net on director)
One (1) Ethernet 10/100 or 10/100/1000 switch, depending on the AP Ethernet connectivity options (to
connect the AP Ethernet to the Test-Net)
Traffic analyzer (Ixia Chariot)
Radius Server (depending on the security protocols used)

Using the Azimuth MIMO Range ACE Benchmark Test

1-2
Rev. v1.0

Physical Configuration

Physical Configuration
This following figure (Figure 1-1) presents physical configuration information for the Azimuth MIMO
Range ACE Benchmark Test.

TM

Status

400NB

Sync

1 2

Bus-Net
192.168.2.1

3 4

RF Port A
RF Port B

RF1
Bus-Net

RF2

RF3

RF4

Warning: +5VDC Output

on all RF ports

RF Port A

RF1

RF2

RF3

RF4

RF Port B

Sync-In

Sync-Out

Comm

Chariot Traffic
Analyzer

Test-Net
192.168.1.1
RF1

RF2

RF3

RF4

RF5

RF6

RF7

RF8

RF1

RF2

RF3

RF4

RF1

CHAMBER1

RadioProof

Victory

TM

Enclosure

RF2

RF3

RF4

CHAMBER2

RadioProof

TM

Enclosure

WSC Station
in the Azimuth MIMO RPE-401

Twisted Pair Ethernet

RF

Access Point
in the Azimuth MIMO RPE-402

Ethernet
10/100 Switch

Figure 1-1. MIMO Range ACE Configuration

Using the Azimuth MIMO Range ACE Benchmark Test

1-3
Rev. v1.0

Setting Up the Access Point (AP)

Setting Up the Access Point (AP)

The following procedure describes how to set up the AP for use in the Azimuth MIMO Range ACE
Benchmark Test. Azimuth Director 4.5 or older does not support MIMO directly. Compared to the standard
SISO Range Vs. Rate (RvR) test, there are several differences. The RF connections used in the Azimuth
MIMO Range ACE Benchmark Test are input in the Azimuth MIMO Range ACE Benchmark Test setup
menu (instead of being deduced from the Connected Devices Manager). For the Azimuth MIMO Range
ACE Benchmark Test, adding the AP and Wireless Standalone Client (WSC) to the connected device
manager is necessary to enable the Azimuth MIMO Range ACE Benchmark Test to browse for the AP and
Station under test.
When testing 802.11n MIMO in the Azimuth system, the objective is to generate the maximum throughput
from a client or AP device under test. In some cases, due to the design of the access point having only
10/100 ethernet ports, the throughput might be limited by port speed. Most APs have a multiport ethernet
switch integrated into the product and so this throughput bottleneck can be solved by using multiple 10/100
ethernet ports on the AP and passing multiple parallel chariot streams through these ports to multiple
chariot endpoints on the wired side of the AP. Using multiple parallel streams on the Ethernet might
remove the wired-side bottleneck, depending on the APs architecture, and allows the Wi-Fi traffic to reach
maximum theoretical throughput, enabling full potential for running the benchmark test.
Setting up to three parallel streams to three unique ethernet endpoints can be achieved by connecting three
ethernet cables to the APs switch ports and via the two ethernet filter ports of the RPE enclosure and the
comm port of the RPE enclosure, each connected to a separate station with chariot endpoint software.
NOTE: To configure your test environmnet, you need to identify the IP address of the WSC MIMO wireless station
card and configure the Chariot endpoint stations appropriately, based on the AP or router device you are using. One of
the Chariot endpoints must be the Azimuth DIRECTOR. To identify the IP address of the station card in DIRECTOR,
right-click on the station card and select Ping Tool from the menu that displays. The IP address is displayed as the
Source IP Address.

To set up an AP for use in the Azimuth MIMO Range ACE Benchmark Test:
1.

In the Azimuth DIRECTOR main menu, select Tools > Connected Devices > New. The New Device
window appears (Figure 1-2).
NOTE: The APs RADIUS server (if present) must be on the same subnet as the APs Ethernet port.

Using the Azimuth MIMO Range ACE Benchmark Test

1-4
Rev. v1.0

Setting Up the Access Point (AP)

Figure 1-2. New Devices

2.

From the Device Type drop-down menu, select the Access Point option.

3.

Enter the vendor, model, and version information in the appropriate fields.

4.

Enter the same information for configuring the AP as you do in the rest of the test configurations, such as
SSID and IP address. The IP address must be on one of the Director TestNets, but not the same subnet as the
WSC client. If the AP supports a WAN port, it may be configured on a different TestNet subnet than the
Ethernet Port. Each RadioProof Enclosure (RPE) supports up to three RJ-45 connections. NOTE: If a
high-speed port (gigabit) is being used, it must be connected to the COMM port RJ-45 connector on the
RPE. Refer to the Azimuth RPE-102/402 User Guide (Pub. No. 14219) for more information on Azimuth
RPEs.

5.

Enter only one of the MIMO APs antenna connections in the RF Connection area. Entering the AP here
enables the Azimuth MIMO Range ACE Benchmark Test to browse for the AP. Director 4.5 (and earlier) is
not MIMO aware, so actual RF connections are configured in the Setup tab of the Benchmark test.
a.

From the Chassis ID drop-down menu, select the appropriate chassis ID number for the ACE 400NB to
which the AP is connected.

b.

For the Port, select the Module front panel option.

c.

From the Module slot drop-down menu, select the slot number of the ACE 400NB.

Using the Azimuth MIMO Range ACE Benchmark Test

1-5
Rev. v1.0

Setting Up the Access Point (AP)

6.

d.

From the Front panel RF port drop-down menu, select the port to which one of the MIMO Station's
antenna is connected. For an APUT, use port 1A. For a STAUT, use port 1B.

e.

In the Additional loss field, indicate any additional RF path loss. (For the TvR test, this value is
inconsequential.) NOTE: You can enter the External Pathloss value in the TvR setup menu described
later (see section on RF configuration under the TvR setup menu).

Click OK. The Connected Devices window appears (Figure 1-3), displaying the AP name, connection,
address, and vendor name for the device.

Figure 1-3. Connected Devices - API

NOTE: If changes are made to a device, you must select the check box to have those changes saved when
the window is closed. In addition, in the Setup tab of the Benchmark test, you must reselect the device once
changes have been made.
7.

Click OK to close the Connected Devices window.

Using the Azimuth MIMO Range ACE Benchmark Test

1-6
Rev. v1.0

Setting Up the Azimuth Wireless Standalone Client (WSC)

Setting Up the Azimuth Wireless Standalone Client

(WSC)
The following procedure describes how to set up the Azimuth WSC for use in the Azimuth MIMO Range
ACE Benchmark Test.
NOTE: Enter only one of the MIMO Stations antenna connections in the RF connection. Entering the Station in
Connected Devices enables the Azimuth MIMO Range ACE Benchmark Test to browse for the Station. Director 4.5
(and earlier) is not MIMO aware, so actual RF connections are configured in the Setup tab of the Azimuth MIMO
Range ACE Benchmark Test.

Prerequisites:

The WSC has already been installed and running on a laptop PC. Refer to the Azimuth WSC Installation
Guide for more information.
The STAUT has been installed in the WSC laptop with drivers loaded. Refer to the Azimuth
RPE-101/401/421 User Guide for more information about installing a laptop.
The station client must be configured for DHCP. If you assign a static IP address, it must be on a Director
TestNet, but not the same subnet as the AP Ethernet. By default, when the WSC is rebooted, the station
sub-net should come up on 192.168.3.0.
The WSC laptop assembly is physically connected to the Director BusNet network.

Procedure:
1.

In the Azimuth DIRECTOR main menu, select Tools > Connected Devices to open the Connected Devices
window.

2.

In the Name column of the Connected Devices menu, select the WSC containing the MIMO STAUT.

3.

Click Edit. The STA RF Connection window appears (Figure 1-4).

Figure 1-4. STA RF Connection

a.

In the STA is connected to drop-down menu, select the Module or Chassis option.

b.

In the Chassis ID drop-down menu, select the chassis ID number.

c.

For the Port, select the Module front panel option.

d.

In the Module slot drop-down menu, select the slot number of the ACE 400NB.

Using the Azimuth MIMO Range ACE Benchmark Test

1-7
Rev. v1.0

Setting Up and Running the Azimuth MIMO Range ACE

4.

e.

In the Front panel RF port drop-down menu, select the RF port (1B or 1C) to which one of the MIMO
Stations antenna is connected.

f.

In the Additional loss field, indicate any additional RF path loss. (For the Azimuth MIMO Range ACE
Benchmark Test, this value is inconsequential.) NOTE: You can enter the External Pathloss value in the
TvR setup menu described later. (See the section on RF configuration under the TvR setup menu.)

Click OK. The Connected Devices window appears (Figure 1-5).

Figure 1-5. Connected Devices - Wireless

NOTE: If changes are made to a device, you must select the check box to have those changes saved when
the window is closed. On the WSC client, the WSC and the client both must be checked to have the change
saved when the window is closed. In addition, in the Setup tab of the Benchmark test, you must reselect the
device once changes have been made.
5.

Click OK to close the Connected Devices window. The WSC has been successfully added to the test system
configuration.

Setting Up and Running the Azimuth MIMO Range ACE

Benchmark Test
Prerequisites:

Set up the physical configuration as shown in the example shown in Physical Configuration on page 1-3.
Set up your AP as directed in Setting Up the Access Point (AP) on page 1-4.
Install the Azimuth MIMO Range ACE Benchmark Test application (supplied on the Azimuth
Benchmark/Tcl Library CD) on the Azimuth DIRECTOR PC. Contact your Azimuth sales representative for
information on licensing the application.
When running Chariot, the Chariot console should be running the Chariot program. Consult your Chariot
documentation for more information. The Chariot server may be installed on the Director PC or on another
PC connected to the DIRECTOR's TestNet. If the Chariot server is installed on another PC, Chariot endpoint
software must be installed on the DIRECTOR PC
Install Chariot Endpoint software on the WSC. The STAUT in the WSC should be configured for DHCP.
Make sure that there is an AP in the Azimuth RPE-402 and that your client station is able to associate with
the AP.

Using the Azimuth MIMO Range ACE Benchmark Test

1-8
Rev. v1.0

Setting Up and Running the Azimuth MIMO Range ACE

Disable any DHCP servers on the AP.

Assign a static IP address for the AP.
NOTE: Some Access Points may have a WAN port in addition to LAN port(s). The WAN port may also be
connected through the Mini Test Head RPE. If the port is connected, DHCP must be disabled and it must be
configured for a static IP address on one of the Director's Test Nets, but on a different subnet than either the
AP's Ethernet port or the WSC's STA client subnets.

Procedure:
1.

Open the Azimuth MIMO Range ACE Benchmark Test by double-clicking the icon in the Benchmarks area
of the Test Manager tab in the Azimuth DIRECTOR.

Figure 1-6. Test Manager Tab

Using the Azimuth MIMO Range ACE Benchmark Test

1-9
Rev. v1.0

Setting Up and Running the Azimuth MIMO Range ACE

Info Tab
2.

In the MIMO Range ACE window that displays, select the Info Tab. (For more information, see Info Tab
on page A-1.)

Figure 1-7. Info Tab

3.

Specify the test engineer, location, output directory, and any test comments.
NOTE: If you are using Azimuth Studio to view test reports, some fields appear in a red typeface to indicate
that you must complete them so you can differentiate the test from others in the Azimuth Studio list of
reports.

Using the Azimuth MIMO Range ACE Benchmark Test

1-10
Rev. v1.0

Setting Up and Running the Azimuth MIMO Range ACE

General Sub-Tab
4.

Click the Setup tab and click the General sub-tab. (For more information, see Setup General Tab on
page A-2.)

Figure 1-8. General Sub-Tab

a.

In the Device-Under-Test Type field, select the device under test, either PC Client Under Test or AP
Under Test.

b.

In the PC Client field, click Browse and select the appropriate client station.

c.

In the Access Point field, click Browse and select the appropriate AP.

d.

In the Test Iterations field, enter the number of test iterations.

e.

In the respective Starting Path Loss and Ending Path Loss fields, enter the starting and ending path
loss. To start at the minimum possible path loss, leave the Starting Path Loss field blank. To end the
test iteration when the station disassociates, leave the Ending Path Loss field blank.

f.

In the Path Loss Delta field, specify the attenuation (in dBs) that should be added in between samples.

g.

In the Wait Between Samples field, enter the time (in seconds) for the script to wait between measuring
samples.

h.

In the Input File field of the Pass/Fail Criteria section, enter the name of the input file that contains the
station under test pass/fail criteria to be used.

Using the Azimuth MIMO Range ACE Benchmark Test

1-11
Rev. v1.0

Setting Up and Running the Azimuth MIMO Range ACE

Traffic Sub-Tab
5.

Select the Traffic sub-tab. (For more information, see Setup Traffic Tab on page A-4.)

Figure 1-9. Traffic Sub-Tab

a.

Select a traffic direction. If the Device Under Test Type selection on the General tab is PC Client Under
Test, the top option is for traffic heading upstream, the middle option is for traffic heading downstream,
and the bottom option is for bidirectional traffic. If the Device Under Test Type selection on the General
tab is an AP, the top option is for traffic heading downstream, the middle option is for traffic heading
upstream, and the bottom option is still for bidirectional traffic. NOTE: The Traffic Direction option
may not be available when a Client or AP device is not properly configured in the Azimuth Connected
Devices window. If you do not have Traffic Direction as a selection, return to the Connected Devices
window and select the appropriate RF connection to which the device is connected.

b.

In the Traffic Type field, select the appropriate traffic analyzer option (Chariot or Layer-3) so the test
uses that tool to measure the traffic characteristics. (Layer 3 is for downstream traffic only.)
NOTE: If you select Chariot as the Traffic generator, one of the traffic endpoints must be DIRECTOR.

c.

If the Traffic Type is Chariot, the Stream Type section displays. You can select the Single Stream radio
button to configure and send a single traffic stream between two endpoints; select the Duplicate Streams
radio button to send duplicates of the defined traffic stream between two endpoints. Select the Multiple
Wired Endpoints radio button to configure and send a traffic stream between the station and multiple
Ethernet ports; you can set up to 4 Ethernet endpoints by making a selection from the drop-down list for
(Number of Ethernet Endpoints), allowing you to possibly exceed the 100Mbps traffic limitation
imposed by a single 10/100 Ethernet port.

Using the Azimuth MIMO Range ACE Benchmark Test

1-12
Rev. v1.0

Setting Up and Running the Azimuth MIMO Range ACE

d.

Enter traffic endpoints in the fields that display on the Pair Options sub-tab after you selected options
for the Traffic Type and Stream Type. You can select DIRECTOR as a Chariot endpoint or TMM as a
Layer 3 endpoint from the Azimuth device browser by clicking the associated Browse button. You can
also enter the IP address of an external PCs Ethernet port and APs port.

e.

Select the Unicast radio button for Packet Destination.

f.

Select the UDP or TCP radio button for Traffic Protocol, depending on the Chariot script you select in
the Chariot Script field. If you are implementing the High_Performance_Throughput.scr, Chariot
requires TCP as the protocol.

g.

In the Traffic Duration field, enter the length of time (in seconds) the traffic should be sent.

h.

In the Traffic Throughput field, select the data rate at which to transmit traffic. NOTE: Traffic sourced
by an STM or TMM module is limited to less that 100Mbs. Since 802.11n devices are capable of higher
throughput rates, it is recommended to use Chariot with a gigabit interface (if the AP has a gigabit
Ethernet port) to run the Azimuth MIMO Range ACE Benchmark Test. Also, gigabit Ethernet ports
need to be connected through the Azimuth Test head on the COM port. Ports E1 and E2 filtering can
interfere with the Link integrity of the gigabit Ethernet connection.

i.

In the Traffic Payload Size field, specify the size of the packet payload (in bytes). This field sets the
size of the Chariot send and receive buffers, setting the amount of data to be sent in a single Chariot
send command.

j.

If you are on the Chariot Pair Options tab, select the Save Chariot Output File checkbox to have
Chariot save its output file from the test run.

For the Packet Destination, select Unicast.

For the Traffic Protocol, select TCP.

In the Timing Record Size field, specify 200000.

In the Remote Chariot IP field, specify the IP address of the Chariot Relay Server.

In the Chariot Script field, specify the Chariot test script for the desired traffic type and rates.
Azimuth recommends using the High_Performance_Throughput.scr as the script.

For the Chariot Uses FPE field, note that Chariot uses the Front Panel Ethernet (FPE) on an STM
or TMM that has a Chariot Endpoint installed on it, and then select Yes or No accordingly.

Using the Azimuth MIMO Range ACE Benchmark Test

1-13
Rev. v1.0

Setting Up and Running the Azimuth MIMO Range ACE

Channel Sub-Tab
6.

Select the Channel sub-tab. (for more information, see Channel Options Tab on page A-7).

Figure 1-10. Channel Sub-Tab

a.

Select a band from the Band drop-down menu. This setting is dependent on the band supported by the
AP.

b.

Select a channel from the Channel drop-down menu. The channel drop-down menu displays available
channels for the band you selected.

Using the Azimuth MIMO Range ACE Benchmark Test

1-14
Rev. v1.0

Setting Up and Running the Azimuth MIMO Range ACE

c.

Select a channel emulation model from the Model drop-down menu. ACE channel models include A to
F, BYPASS, and BUTLER. There is an option to run all channel models; when selected, channel
models are run in sequence.

d.

Ports A and B antenna spacing define the physical spacing between the transmit and receive antennas.
The available options are half wavelength, one, and four.

Tx/Rx ports : The number of Transmit and Receive ports at both port A and port B can be selected
by using this menu.

Transmit Input Power: The transmit input power field accepts values from -5 to 25 dBm. This is
used to vary the input power level at port A and port B.,

e.

Enter a percentage between the 1 - 100 range in the Doppler Rate field for varying the Doppler rate. The
default value is 100.

f.

To specify whether traffic emulation should be for antennas within sight of each other, make the
appropriate selection for the Line of Sight radio buttons (Yes or No). This setting specifies whether the
selected channel model has a line of sight component.

Lib Connections Sub-Tab

NOTE: The Lib Connections sub-tab displays the device libraries used. You do not need to configure any
parameters on this sub-tab.

Figure 1-11. Lib Connections Sub-Tab

Security Sub-Tab
7.

Select the Security sub-tab. (For more information, see Configuration Security Parameters on page A-9.)

Figure 1-12. Security Sub-Tab

Using the Azimuth MIMO Range ACE Benchmark Test

1-15
Rev. v1.0

Setting Up and Running the Azimuth MIMO Range ACE

a.

From the Managed By drop-down menu, select the appropriate security manager (security supplicant)
for the DUT. If only one manager is available, this field will not be editable. For example, in the case of
a Wi-Fi Test Engine enabled DUT, the only option that appears is the DUT. With other devices, you may
see options such as NDIS, Funk, or Meetinghouse.

b.

From the Protocol drop-down menu, select the appropriate security protocol (None, WPA, or WPA2).

c.

In the SSID field, enter the SSID of the STAUT or AP.

d.

From the Cipher drop-down menu, select the appropriate security cipher (Open or WEP) and, if
applicable, enter the appropriate settings for the cipher.

AP Config Sub-Tab
NOTE: The AP Config sub-tab lets you specify the 802.11 channel. If you leave the Channel field blank,
the channel is auto-detected; therefore, you do not need to configure any parameters on this sub-tab. You can
also load a different TCL Package by clicking the Load button, and you can select the Yes or No radio
buttons to auto configure the access point.

Figure 1-13. AP Config Sub-Tab

Run the Test

8.

Click Go to begin the Azimuth MIMO Range ACE Benchmark Test. Upon completion of the test, the data
associated with the test is plotted in real time on the chart in the TvR results area of the window.

Using the Azimuth MIMO Range ACE Benchmark Test

1-16
Rev. v1.0

Troubleshooting the Test

Troubleshooting the Test

If you are having trouble obtaining test output or if you want to verify that the system is properly
configured, perform each of the troubleshooting steps in the following procedure. Please refer to
Figure 1-1 on page 1-3 to enhance your understanding of the physical configuration of the Azimuth MIMO
Range ACE Benchmark Test.
To troubleshoot the Azimuth MIMO Range ACE Benchmark Test:
1.

Obtain the IP addresses of the AP by right-clicking on the AP in the main explorer tree and selecting
Configuration. The IP address appears in the General tab.

Figure 1-14. AP Configuration

2.

Obtain the Stations IP address by right-clicking on the WSC in the explorer tree and selecting Ping Tool. The
IP address appears as the Source IP address on the top of the window.

Figure 1-15. Ping Configuration

3.

If you are having difficulties in either running the Azimuth MIMO Range ACE Benchmark Test or in
plotting data, examine the System Log to see if there are any messages indicating why you may be having
problems.

Using the Azimuth MIMO Range ACE Benchmark Test

1-17
Rev. v1.0

Troubleshooting the Test

4.

If you receive an error message that specifies there is no association between the client station and the AP,
then do the following:
a.

Examine the physical cabling between the client station and the AP (Figure 1-1). Verify that Tx/Rx
antennas are connected to the appropriate ports on the ACE.

b.

Verify the logical connection between the Azimuth DIRECTOR and the AP by selecting Start and then
Run in the Windows menu of the Azimuth DIRECTOR. The Run window appears.
In the Run window, enter the following command:

cmd
The command prompt window appears. Determine if there is a connection between the Azimuth
DIRECTOR and the AP by entering the following command (replace 1.1.1.1 with the AP IP address):

ping 1.1.1.1
If there is a connection between the Azimuth DIRECTOR and the AP, you will see a message indicating
the number of packets received. If you see the message Request timed out, then there is no connection
between Azimuth DIRECTOR and the AP.
c.

Verify the logical connection between the WSC and the Azimuth DIRECTOR by selecting the WSC
configured to generate traffic.
Open the remote desktop for that WSC and verify that the STA can associate to the AP and that it
obtains an IP address from DHCP.
Open a command prompt box by selecting Start and then Command Prompt in the Windows menu.
Determine if there is a connection between the STM and the Azimuth DIRECTOR by entering the
following command (192.168.1.1 is the IP address of the Azimuth DIRECTOR over Test-Net):

ping 192.168.1.1
If there is a connection between the STM and the Azimuth DIRECTOR then you will see a message
indicating the number of packets received. If you see the message Request timed out, then there is no
connection between Azimuth DIRECTOR and the WSC.
5.

If you receive an error message that specifies that no traffic is being received by the WSC:
a.

Unplug the Ethernet cable from the WSC.

b.

Verify the connection between the Azimuth DIRECTOR and the AP by selecting Start and then Run in
the Windows menu of the Azimuth DIRECTOR. The Run window appears.
In the Run window, enter the following command:

cmd
The command prompt window appears.
Determine if there is a connection between the WSC and the AP by entering the following command
(where 1.1.1.1 is the AP IP address):

ping 1.1.1.1
If there is a connection between the WSC and the AP, you will see a message indicating the number of
packets received. If you see the message Request timed out, then there is no connection between
WSC and the AP. If this occurs, verify the channel, SSID, and security settings on both the AP and the
Station and associate the Station to the AP.

Using the Azimuth MIMO Range ACE Benchmark Test

1-18
Rev. v1.0

Reviewing Test Results

Reviewing Test Results

The optimal results of the Azimuth MIMO Range ACE Benchmark Test are to verify the expected
operation of the client station over a range of power levels. The results enable you to determine if the
throughput and RSSI, in particular, are operating at the expected parameters at various attenuation levels.
This section shows selected output examples of test results.
You can view the test results in several ways:

Log Tab For detailed information on test runs, select the Log tab. This highly detailed log describes the
result of the test, throughput, operation results, configuration setup messages, measured output, errors,
causes of errors, and other statistics. This is perhaps the most useful method to review and determine what
caused a failure in the test, or to see what events were occurring at a particular time during the test iteration
at which the test results were or were not as expected.

System Log This log provides general system messages related to the module, station, and chassis.

Graphs Tab To see the results graphs during various attenuation levels during each test iteration, select
the Graphs Tab. The graphs depict throughput, RSSI, packet error, and data rate test results. The parameters
in each of the Graphs tabs are presented in Azimuth MIMO Range ACE Benchmark Test Parameters on
page A-1.

Azimuth Studio You can view and compare test results from different test runs in Azimuth Studio.
Studio offers a database server to store test results and offers a browser-based solution for viewing and
comparing test results. For specific information on viewing these results, please see Viewing and
Comparing Test Results in Azimuth Studio on page 1-25. For more information about Azimuth Studio, see
the Azimuth Studio User Guide (publication number 15503).

Log Tab

Figure 1-16. Log Tab

Using the Azimuth MIMO Range ACE Benchmark Test

1-19
Rev. v1.0

Reviewing Test Results

Table 1-1. Log Tab

Parameter

Definition

Start Time

Time that the test started.

Stop Time

Time that the test ended.

Status

Status of the running of the test.

Run Time

How long the test is running (while it is still in progress) or ran (when complete).

Emulation time is a new feature for the Log tab, providing the ability to track results between a specific
time frame. A graphic example is shown next, with the Emulation column circled in red.

Figure 1-17. Log Tab Highlighting Emulation Time

Using the Azimuth MIMO Range ACE Benchmark Test

1-20
Rev. v1.0

Reviewing Test Results

Graphs Tab - Throughput

Figure 1-18. Graphs Tab Showing Throughput

Table 1-2. Throughput Graph
Parameter

Definition

Average Throughput Mbps The measure of throughput occurring over the attenuation range during the test.
Total Path Loss dB

The attenuation range occurring during the test.

Using the Azimuth MIMO Range ACE Benchmark Test

1-21
Rev. v1.0

Reviewing Test Results

Graphs Tab RSSI

Figure 1-19. Graphs Tab Showing RSSI

Table 1-3. RSSI Graph
Parameter

Definition

Average RSSI

The received signal strength measurement occurring over the attenuation range during the
test.

Total Path Loss dB

The attenuation range occurring during the test.

Using the Azimuth MIMO Range ACE Benchmark Test

1-22
Rev. v1.0

Reviewing Test Results

Graphs Tab Packet Errors

Figure 1-20. Graphs Tab SHowing Packet Errors

Table 1-4. Packet Errors Graph
Parameter

Definition

Packet Errors

The number of packet errors occurring over the attenuation range during the test.

Total Path Loss dB

The attenuation range occurring during the test.

Using the Azimuth MIMO Range ACE Benchmark Test

1-23
Rev. v1.0

Reviewing Test Results

Graphs Tab Data Rate

Figure 1-21. Graphs Tab Showing Data Rate

Table 1-5. Data Rate Graph
Parameter

Definition

Data Rate Histogram The data rate occurring over the attenuation range during the test. Speeds are color-coded at
the bottom of the graph.
Total Path Loss dB

The attenuation range occurring during the test.

Zooming In to a Results Graph

You can zoom in to a selected section of any results graph to see the results in finer detail.
To zoom in:
1.

Place the cursor on the graph.

2.

Click the left mouse button.

3.

Drag the cursor to draw a square over the area of the graph you want to enlarge.

4.

Click the left mouse button again.

5.

Repeat this process to zoom in to the next level of magnification.

To zoom out to the previous level of magnification, place the cursor on the graph and click the right mouse
button.

Using the Azimuth MIMO Range ACE Benchmark Test

1-24
Rev. v1.0

Reviewing Test Results

Viewing and Comparing Test Results in Azimuth Studio

If you have installed a licensed version of Azimuth Studio, you can open Azimuth Studio to view and
compare test results from different runs of the Azimuth MIMO Range ACE Benchmark Test.
An example of the test results in Azimuth Studio is presented in the procedure below that describes how to
view and compare test runs.
To view and compare test results in Azimuth Studio:
1.

Open Azimuth DIRECTOR and select the database icon on the main toolbar. The Internet Explorer browser
opens and the Azimuth Studio login page appears.

2.

Enter your user name and password in the appropriate fields and click OK. The Quick Search window
appears.

3.

In the TEST field, select the MIMO Range ACE option.

4.

In the FROM and TO fields, select the date range in which the tests were run. The results for each test run
appear in the GUI under the Test Description field (Figure 1-22).

Figure 1-22. Studio Quick Search Window Showing Test Results

All of the same information that is available in separate tabs (like the Graphs, Log and System Log tabs) of
the Azimuth MIMO Range ACE Benchmark Test GUI is presented in the Azimuth Studio report.
NOTE: In the lower portion of the report, there are expandable fields with plus (+) signs adjacent to them.
When you select these plus signs with your cursor to expand them, the full content of the field appears, as
shown in Figure 1-22.

Using the Azimuth MIMO Range ACE Benchmark Test

1-25
Rev. v1.0

Reviewing Test Results

5.

To compare two test runs, display the list of test results as explained in step 4. Then select the comparison
icon adjacent to two of the appropriate reports in the Compare column. Each time you select the comparison
icon, a message appears with wording similar to the following: Adding Test Run 106 to the comparison
page. Click OK to close each message box.

6.

Select the Compare Test Runs option. The selected tests to compare appear (Figure 1-23).

Figure 1-23. Compare Test Runs

7.

Click Compare Test. The two tests appear side-by-side in the comparison report.

Using the Azimuth MIMO Range ACE Benchmark Test

1-26
Rev. v1.0

Common Graphic User Interface (GUI) Elements

Appendix A: Azimuth MIMO Range ACE

Benchmark Test Parameters
This appendix provides the meanings of the fields in the Azimuth MIMO Range ACE Benchmark Test
GUI and the images of many of the tabbed windows.
NOTE: Fields that appear in Table A-1 are common to all tabs in the test GUI.

Common Graphic User Interface (GUI) Elements

Table A-1.
Parameter

Value Default

Definition

Go

N/A

N/A

Starts the application.

Close

N/A

N/A

Closes the application window.

Defaults

N/A

N/A

Returns all user-specified fields to the default values defined by Azimuth.

Verbose Logging

On
Off

Off

When set to On, the system logs debug messages in the Log tab. When set
to Off, no debug messages are displayed.

Info Tab
NOTE: Fields that appear in red in the Info tab must be completed or you cannot run the test. These fields appear red
when you are writing the test output reports to the Azimuth Studio server database.
Table A-2. Info Tab
Parameter

Value

Definition

Test Engineer

Alphanumeric text Identity of the test engineer who is setting up and running the test. If Director
logs to Studio, this is a selection of Accounts available on the Studio Server.

Location

Alphanumeric text Location of the test system.

Output
Directory

Selected directory Displays the directory to which the test results are saved for each test:

output.log contains all data that appears in the log tab.

results.csv contains the results of each iteration of the test.
system.log contains messages from the System Log tab.
NOTE: Click Browse to navigate to the desired folder.

Test Comments Alphanumeric text Additional information about the test or test setup.

Using the Azimuth MIMO Range ACE Benchmark Test

A-1
Rev. v1.0

Setup General Tab

Setup General Tab

Table A-3. Setup General Tab
Parameter

Value

Default

Definition

Device-Under-Test Type

PC Client
Under Test

N/A

Specifies that a PC client will be the device under test.

ASD Under
Test

N/A

Specifies that a application specific device (ASD) will be

the device under test.

AP Under
Test

N/A

Specifies that an access point (AP) will be the device under

test.

PC Client

PC client

N/A

Specifies which PC client will be in the test bed. When you

click Browse, only PC clients that are visible in the
explorer tree can be selected.

ASD

ASD

N/A

Specifies which ASD will be in the test bed. When you

click Browse, only ASDs that are visible in the explorer
tree can be selected.

Access Point

AP

N/A

Specifies which AP will be in the test bed. When you click

Browse, only APs that are visible in the explorer tree can
be selected.

Test Iterations

1 - 10

Number of times the test will run.

Starting Path Loss

Integer

N/A

RF path loss (in dBs) at which to start the test.

If you specify a Starting Path Loss value that exceeds the
specified Ending Path Loss value, then the attenuation
decreases until the Ending Path Loss value is reached.
Likewise, if you specify a Starting Path Loss value that is
less than the Ending Path Loss value, then attenuation
increases until the Ending Path Loss value is reached.
Leave this field blank to specify the minimum path loss.

Ending Path Loss

Integer

N/A

RF path loss (in dBs) at which to end the test.

If you specify a Starting Path Loss value that exceeds the
specified Ending Path Loss value, then the attenuation
decreases until the Ending Path Loss value is reached.
Likewise, if you specify a Starting Path Loss value that is
less than the Ending Path Loss value, then attenuation
increases until the Ending Path Loss value is reached.
Leave this field blank to end the test when the station
disassociates.

Path Loss Delta

Integer

N/A

Attenuation (in dBs) that should be added in between

samples.

Using the Azimuth MIMO Range ACE Benchmark Test

A-2
Rev. v1.0

Setup General Tab

Table A-3. Setup General Tab (Continued)

Parameter

Value

Default

Definition

Wait Between Samples

Integer

Number of seconds to wait in between incrementing the RF

path loss.

N/A

Name of the file that contains the STAUT pass/fail criteria.

This file enables you to change the pass/fail criteria for the
STAUT for each sample at each data rate. Each value is the
maximum packet error rate allowed for that sample.
An example of a Pass/Fail Criteria input file (input.txt or
input.csv) can be found on the Azimuth DIRECTOR in the
following path:
\data\tests\ACI

Pass/Fail Criteria Input File File name

Using the Azimuth MIMO Range ACE Benchmark Test

A-3
Rev. v1.0

Setup Traffic Tab

Setup Traffic Tab

Figure A-1. Traffic Tab Options

NOTE: Fields that appear in Figure A-1 are described in Table A-4.
Table A-4. Traffic Tab Options
Parameter

Value

Default

Definition

Traffic
Direction

Varies

N/A

Specifies the direction in which traffic is being sent (upstream, downstream

or bidirectional) between each selected test bed device and the traffic
endpoint. The order in which devices communicate directly depends on the
test bed devices selected in the following fields: PC Client (page A-2),
ASD (page A-2), and Access Point (page A-2).
NOTE: The options for this parameter are not visible until the Test-Bed
Setup fields are selected in the General tab.

Using the Azimuth MIMO Range ACE Benchmark Test

A-4
Rev. v1.0

Setup Traffic Tab

Table A-4. Traffic Tab Options (Continued)

Parameter

Value

Default

Definition

Traffic Type

Chariot

Chariot

Specifies the use of the Chariot tool to measure and report bandwidth.

Stream Type

Layer-2

Specifies the use of Layer-2 traffic to measure and report bandwidth. If this
value is not present, you must select PC Client or Access Point on the
previous view.

Layer-3

(Downstream only) Specifies the use of Layer-3 traffic to measure and report
bandwidth. If this value is not present, you must select PC Client or Access
Point on the previous view.

Single
Stream

Single data stream between two endpoints.

Duplicate
Streams

Duplicates a single stream a specified number of times to increase the amount

of data streams between two endpoints, which you set in the field that
displays after you select the Duplicate Streams radio button.
NOTE: The maximum amount is limited by the number of licenses endpoint
pairs on the Chariot server; bi-directional traffic selection uses 2 licenses per
data stream.

Multiple
Wired
Endpoints

Configures a select number of Ethernet endpoints, which you enter in the

field that displays after you select the Multiple Wired Endpoints radio button.
The maximum is 4.

Traffic
Endpoint

N/A

N/A

Traffic endpoint to be used. Click Browse to select a device to be used as a

Traffic Endpoint.
NOTE: When you want to specify the Azimuth DIRECTOR, you must enter
Director in the Traffic Endpoint field. For external endpoints added to the test
setup, such as PCs, enter the IP address of the device.

Packet
Destination

Unicast

Unicast

Specifies that the destination of the transmitted packets is a unicast address.

Multicast

Traffic Proto- UDP

col
TCP

Traffic
Duration

Integer

Specifies that the destination of the transmitted packets is a multicast address.

Note: Multicast is not a valid option for Chariots
High_Performance_Throughput.scr.
UDP

Specifies the use of the User Datagram Protocol (UDP) in traffic generation.

UDP

Specifies the use of the Transmission Control Protocol (TCP) in traffic

generation.
NOTE: TCP is required when using Chariots
High_Performance_Througput.scr.

60

Number of seconds that the traffic is transmitted from the test station to the
station under test.

Using the Azimuth MIMO Range ACE Benchmark Test

A-5
Rev. v1.0

Setup Traffic Tab

Table A-4. Traffic Tab Options (Continued)

Parameter

Value

Default

Traffic
Throughput

N/A
Integer
DEFAUL
T
UNLIMI
TED

Traffic throughput (in Mbps) sent by the test station. When UNLIMITED is
selected it tries to achieve the maximum throughput. When DEFAULT is
selected, the default value for the Chariot script should be used.

Traffic
Payload Size

Integer

Payload, in bytes, transmitted by the test station. For Chariot, Payload relates
to the buffer size. DEFAULT is recommended, which uses the buffer size
designated in the script.
NOTE: For Layer-3, fragmentation is not allowed; the maximum size in this
case is 1480 bytes.

1472
(Chariot)
1500
(Layer-3)

DEFAUL
T
Timing
Record Size

Integer

Remote
Chariot IP

IP
Address

Save Chariot
Output File

Specifies that the default value for the Chariot script should be used.
200000

Size (in bytes) of each Chariot Timing Record. When DEFAULT is selected,
the default value for the Chariot script should be used.

N/A

IP address of the Chariot Relay Server. The server must be configured before
you specify this address.

DEFAUL
T

Chariot Script Chariot

script path
and file
name

Definition

Streamin Chariot script folder and name (in the format folder/chariotScriptName) to
use for the test. Azimuth recommends using the
g/
NetMtgv. High_Performance_Throughput.scr as the script.
scr

Checked/ Uncheck After the test is run, Chariot data files are saved to the Chariot server
installation directory, typically located at:
Unchecke ed
d
C\:Program Files ixia\IXChariot\Tests\MimoRangeWSeries
Output data files can be viewed using Chariot after the test is complete.

Chariot Uses
FPE?

Yes
No

No

Specifies whether Chariot uses the transmitting modules Front Panel

Ethernet (FPE) connection for traffic control. NOTE: Chariot uses the Front
Panel Ethernet (FPE) on an STM or TMM that has a Chariot Endpoint
installed on it.

Using the Azimuth MIMO Range ACE Benchmark Test

A-6
Rev. v1.0

Setup - Channel Tab

Setup - Channel Tab

The Channel sub-tab displays the...

Figure A-2. Channel Tab

Table A-5. Channel Options Tab
Parameter

Value

Default

Definition

Band

11b/g, 11a,
11h, 11j,
11n_2.4,
11n_5.0

11b/g

Specifies the radio band on which the connected devices are

operating.

Channel

varies

N/A

Specifies the channel on which the connected devices are

operating. Both the channel number and the frequency are listed.
The channels and frequencies that are listed vary according to
the selected radio band.

Model

A, B, C, D, N/A
E, F, Butler,
and Bypass

Specifies the emulation model to be used. For more information

about these models, please see IEEE TGn Channel Models, doc:
IEEE 802.11-03/940r4.

Using the Azimuth MIMO Range ACE Benchmark Test

A-7
Rev. v1.0

Setup - Lib Connections Tab

Table A-5. Channel Options Tab

Parameter

Value

Default

Definition

Port A: TX/RX
Antenna Spacing

Half
One
Four

Half

Specifies the antenna spacing (in wavelength () units)

emulated by the emulation mode on RF Ports A and B.
They include:
half (wavelength) - antenna spacing is one-half
wavelength from each other.
one - antenna spacing is one wavelength from each
other.
four - antenna spacing is four wavelengths from
each other.

Port B: TX/RX
Antenna Spacing

Line of Sight

Yes/No

Yes

When Yes is selected, the emulation model should emulate

the situation in which antennas are within line-of-sight of
each other. This is the default setting for the Line of sight
parameter. When No is selected, the emulation model
should emulate traffic with antennas that are not within
sight of each other. If the Emulation Model is set to
Bypass, Line of sight is not available.

Setup - Lib Connections Tab

The Lib Connections sub-tab displays the device libraries used. You do not need to configure any
parameters on this sub-tab.

Setup Security Tab

Figure A-3. Setup - Security Tab

NOTE: Fields that appear in Figure A-3 are described in Table A-6.
NOTE: Use Table A-6 to cross-reference supported security protocols, authentication types, ciphers, and which
security manager handles each one in the Azimuth MIMO Range ACE Benchmark Test script. Each security
parameter is described in Table A-7.

Using the Azimuth MIMO Range ACE Benchmark Test

A-8
Rev. v1.0

Setup Security Tab

Table A-6. Associated Security Settings

Security
Manager

Security
Protocol

Funk

None

Open

Shared Key
Open
AP Transmit Key
Station Transmit Key

WEP

WPA

EAP-FAST
EAP-TLS
LEAP
PEAPv1/GTC
PEAPv1/MSCHAPv2
Pre-Shared Key

TKIP

EAP-FAST
EAP-TLS
LEAP
PEAPv1/GTC
PEAPv1/MSCHAPv2

802.1x

NDIS

Cipher

None

WPA2

Wireless Zero
Config

Authentication

None

AES-CCMP
TKIP

Dynamic WEP

Open

None

Shared Key
Open

WEP

WPA

EAP-TLS
Pre-Shared Key

TKIP

WPA2

EAP-TLS
Pre-Shared Key

AES-CCMP
TKIP

None
None

Open

Shared Key
Open

WEP

Configuration Security Parameters

You must configure RADIUS and certificates when running the Azimuth MIMO Range ACE Benchmark
Test if you are configuring 802.1x, WPA, or WPA2 and you are using any of the following: EAP-FAST,
EAP-TLS, LEAP, PEAPv1/GTC and PEAP/MSCHAPv2. Certificates can reside in two places depending
on the authentication type they are using. TLS requires a client certificate (that can reside in a WSC or
STM). If using PEAP, you need to install a server certificate on the RADIUS server (usually the
DIRECTOR). If the station under test is not configured to check certificates, you do not have to install a
certificate on the client. If the station under test is configured to check certificates, you must install a
certificate on the client.
NOTE: The NDIS or Funk security management features are persistent. Even after rebooting the STM or the
Azimuth DIRECTOR, the option will remain as selected.

Using the Azimuth MIMO Range ACE Benchmark Test

A-9
Rev. v1.0

Setup Security Tab

Table A-7. Configuration Security Parameters

Parameter

Value

Default

Description

Managed By

Funk

N/A

Specifies that STM security is to be managed by Funk Softwares

Odyssey Client Manager. Funk can be used to manage the STMs
WEP, WPA or 802.1x security protocols.
NOTE: If you select this option and have not installed the Funk
Software Odyssey Client Manager, the security protocol will be
managed by the NDIS protocol.
NOTE: After installing the Odyssey Client Manager, the Funk
option appears in this menu.

NDIS

N/A

Specifies that STM security is to be managed by the Microsoft

Network Device Interface Specification (NDIS) protocol. NDIS
can be used to manage the STMs Wired Equivalent Privacy
(WEP) security protocol.

Wireless Zero
Config

N/A

Specifies that STM security is to be managed by the Microsoft

Wireless Zero Configuration (WZC) service. The WZC service
can be used to manage the STMs WEP, WPA, or WPA2 security
protocols.

None

N/A

Specifies that no security will be used for this STM station.

WPA

N/A

Specifies the use of the Wi-Fi Protected Access (WPA) security

protocol. This is the first generation of WPA security.

WPA2

N/A

Specifies the use of the Wi-Fi Protected Access 2 (WPA2)

security protocol, the second generation of WPA security. The
Azimuth DIRECTOR requires that, when using this protocol, the
STM is running Windows XP, Service Pack 2 and Windows patch
XPKB891859-Beta1.

802.1x

N/A

Specifies the use of the 802.1x security protocol necessary for

running tests.

SSID

alphanumeric
characters

N/A

Specifies the Service Set Identifier (SSID).

WEP:
Authentication
Type

open

open

When WEP protocol is in use, this specifies the use of

open-system authentication in which the AP accepts the station
without verifying its identity.

Protocol

shared

When WEP protocol is in use, this specifies the use of shared-key

authentication, which requires that a shared key be distributed to
stations before attempting authentication.

WEP Key 1

alphanumeric
characters

N/A

Specifies the use of the first of four WEP keys. You can specify
either a 40-bit or 128-bit WEP key.

WEP Key 2

alphanumeric
characters

N/A

Specifies the use of the second of four WEP keys. You can specify
either a 40-bit or 128-bit WEP key.

WEP Key 3

alphanumeric
characters

N/A

Specifies the use of the third of four WEP keys. You can specify
either a 40-bit or 128-bit WEP key.

WEP Key 4

alphanumeric
characters

N/A

Specifies the use of the fourth of four WEP keys. You can specify
either a 40-bit or 128-bit WEP key.

Using the Azimuth MIMO Range ACE Benchmark Test

A-10
Rev. v1.0

Setup Security Tab

Table A-7. Configuration Security Parameters (Continued)

Parameter

Value

Default

Description

WEP: AP
Transmit Key

1-4

Specifies the value of the AP transmit key.

WEP: Station
Transmit Key

1-4

Specifies the value of the station transmit key.

Authentication
Type

PSK

N/A

Specifies the use of a WPA or WPA2 pre-shared key

authentication. The TKIP or AES cipher is available for use with
this parameter.

EAP-TLS

N/A

This protocol combines the Extensible Authentication Protocol

(EAP) with Transport Level Security (TLS). provides for mutual
authentication, integrity protected cipher suite negotiation, and
key exchange between two endpoints through the exchange of
certificates. This authentication allows the use of a user name,
certifying authority and specification of who the certificate was
issued to (Issued To).

PEAP

N/A

Specifies the use of the Protected Extensible Authentication

Protocol (LEAP). This authentication type requires the use of a
user name and password and Inner PEAP authentication type.

LEAP

N/A

Specifies the use of the Lightweight Extensible Authentication

Protocol (LEAP). This authentication type requires the use of a
user name and password.

EAP-FAST

N/A

Specifies the use of the Extensible Authentication

Protocol-Flexible Authentication via Secure Tunneling
(EAP-FAST) authentication. This requires the use of a user name
and password.

AES-CCM

N/A

Specifies use of the Advanced Encryption Standard (AES) cipher

algorithm, which uses a 128-bit key size.

TKIP

N/A

The Temporal Key Integrity Protocol (TKIP) cipher uses a 128-bit

shared secret called a temporal key (TK). The transmitters MAC
address is joined with the TK to produce a Phase 1 key that is, in
turn, joined with an initialization vector (IV) to derive per-packet
keys. Each key is used to encrypt one data packet.

WEP

N/A

Specifies the use of the Wired Equivalent Privacy (WEP) security

protocol. The length of the WEP key implicitly determines if
WEP40 or WEP128 is configured.

Pass phrase

alphanumeric
characters

N/A

Specifies a phrase to use as part of the specified authentication

process. This parameter is required for Pre-Shared Key
authentication.

Radius Server
IP

IP address
192.168.1.1 Specifies the IP address of the RADIUS server.
(dotted decimal
notation)

Radius Server
Port

Integer

Cipher

1645

Specifies the RADIUS authentication port number to be used by

the RADIUS server.

Using the Azimuth MIMO Range ACE Benchmark Test

A-11
Rev. v1.0

Setup - AP Config Tab

Table A-7. Configuration Security Parameters (Continued)

Parameter

Value

Default

Description

Radius Shared
Secret

alphanumeric
characters

N/A

Specifies the shared secret to be used by the RADIUS server for

authentication purposes.

Radius User
Name

alphanumeric
characters

console

Specifies the user name to be used by the RADIUS server for

authentication purposes.

Radius User
Password

alphanumeric
characters

azimuth

Specifies the password to be used by the RADIUS server for

authentication purposes.

Authentication
Timeout

Integer

90

Specifies the period of time to wait (in seconds) for authentication

to occur.

Inner PEAP
Authentication
Type

Gtc

N/A

Specifies that the GTC EAP authentication protocol be used for

password authentication of the RADIUS server.

MSChapv2

N/A

Specifies that the MsChapv2 EAP authentication protocol be used

for password authentication of the RADIUS server.

Client
Certificate

alphanumeric
characters

N/A

Specifies the name of the client certificate to be used in RADIUS

authentication.

Trusted Root

alphanumeric
characters

N/A

Specifies the name of the trusted root certification authority.

Setup - AP Config Tab

Figure A-4. Setup - AP Config Tab

NOTE: Fields that appear in Figure A-4 are described in Table A-8.
Table A-8. Setup - AP Config Tab
Parameter

Value

Default

Definition

Channel

alphanumeric characters

N/A

If you leave this field blank, the channel is auto-detected.

Using the Azimuth MIMO Range ACE Benchmark Test

A-12
Rev. v1.0

Index
A

acknowledgement, 1-1

Rate Versus Range

troubleshooting steps, 1-17

Request timed out, 1-18

Bypass emulation model, A-7

C
Channel models
TGn, 1-1

RF path loss, 1-8

S
security cipher, 1-16
signal-to-noise ratio, 1-1

Chariot, 1-8

SISO, 1-2

Cipher, 1-16

spatial multiplexing, 1-2

Configuration tab
Port A
TX/RX Antenna Spacing parameters, A-8
RF Port B
TX/RX Antenna Spacing parameters, A-8

Studio, 1-10

T
transmit data rate, 1-1

endpoint, 1-8

WEP, 1-16

errors, 1-19

WPA, 1-16
WPA2, 1-16

F
Funk, 1-16

G
gigabit, 1-5
Gigabit Ethernet, 1-13

H
high-speed port, 1-5

M
Managed By, 1-16
Meetinghouse, 1-16
modulation rate, 1-1

N
NDIS, 1-16

P
ping, 1-18
Protocol, 1-16

Using the Azimuth MIMO Range ACE Benchmark Test

Index-1

Using the Azimuth MIMO Range ACE Benchmark Test

Index-2