当前位置:首页 >> 信息与通信 >>

Generic Wireless LAN evaluation test plan


Wireless LAN evaluation test plan

-1-

Table of Contents Wireless LAN evaluation test plan Overview 1. Ease of use 1.1 Guest access with captive portal and employee access with 802.1x/WPA - one IP address, no external authentication server 1.2 Guest account provisioning 1.3 Automatic channel and power assignment 1.4 Dynamic RF intelligence 2. Security - Intrusion Detection/Prevention capabilities 2.1 Rogue AP (WEP) detection/classification/containment 2.2 Ad-hoc networks detection and containment 2.3 Blacklist WiFi client based on firewall violations 3. Performance and Scalability 3.1 Intra-VLAN roaming 3.2 Inter-VLAN roaming 3.3 Secure Inter-switch mobility 3.4 Self-Healing – AP failure due to AP shut down 3.5 Self-Healing – AP failure due to Radio failure 3.6 Controller Redundancy 3.7 QoS prioritization of user-specified traffic on single SSID 3.8 Load balancing based on user thresholds 4. Troubleshooting and Management 4.1 Station statistics 4.2 Per-user debugging capabilities 4.3 Remote packet capture 4.4 Session mirroring 4.5 RF heat maps 4.6 Location tracking 1 3 4 4 5 6 7 8 8 10 11 12 12 13 14 16 17 18 19 20 22 22 23 24 25 26 27

-2-

Overview
This document outlines the test plan to evaluate an enterprise WLAN solution. The results of the tests conducted as a part of such an evaluation provides the evaluator with the data required to compare different WLAN solutions and make an educated choice on the right solution for the needs. The different parameters that should be considered by an evaluator before choosing the solution are: Ease of use Security Performance and Scalability Manageability and Troubleshooting This test plan has been divided into different sections for the different areas that need to be tested and compared when evaluation a wireless LAN solution. Each section has a set of test cases. Each of the test cases has been presented in the following format: Test case

Equipment required Topology

Description and testing steps

Expected results

-3-

1. Ease of use
This section includes scenarios that verify the ease of use for basic features needed in an enterprise WLAN.

1.1 Guest access with captive portal and employee access with 802.1x/WPA - one IP address, no external authentication server
Test case Equipment required Verify support for employee access using 802.1x/WPA and guest access using captive portal with only one IP address and no external authentication server 1 WLAN controller 1 AP 1 Laptop – Windows XP SP2 1 L2/L3 switch (optional)

Topology

Description and testing steps

Expected results.

1. Assign the controller an IP address and default gateway (statically or via DHCP) 2. Create VLANs for employees and guests, and for APs 3. Configure the employee and guests to be NAT’d using the controller’s IP address 4. Configure the DHCP server for employees, guests, and APs 5. Configure an employee SSID to support WPA 6. Configure an employee account on the controller 7. Configure a guest SSID to be open-system and use captive portal 8. Configure a guest account on the controller 9. Configure access policies for guest (HTTP, HTTPS to Internet only) and employee (any access) 10. Associate a laptop configured to use open-system to the guest SSID and logon using the guest ID and password 11. Verify that the laptop gets an IP address from the configured DHCP server and verify connectivity 12. Associate a laptop configured to use WPA to the employee SSID and logon using the employee SSID and password Employees and guests should be able to connect to their respective SSIDs and access control should allow employees full access while limiting guests to Internet only for http and https. If external/Internet connectivity is not available then a server can be setup and access controls adjusted to allow/block access to that server for employees vs. guests.

-4-

1.2 Guest account provisioning
Test case Verify support for guest accounts to be dynamically created using a special administrative login that allows a user, such as a front desk receptionist, to create guest accounts on a WebUI page. 1 WLAN controller 1 AP 1 Laptop – Windows XP SP2 1 L2/L3 switch (optional)

Equipment required

Topology

Description and testing steps

Expected results.

1. Assign the controller an IP address and default gateway (statically or via DHCP) 2. Create VLANs for employees and guests, and for APs 3. Configure the employee and guests to be NAT’d using the controller’s IP address 4. Configure the DHCP server for employees, guests, and APs 5. Configure an employee SSID to support WPA 6. Configure an employee account on the controller 7. Configure a guest SSID to be open-system and use captive portal 8. Create a special administrative account that is only allowed to create guest accounts 9. Configure a guest account on the controller using the administrative login 10. Associate a laptop configured to use open-system to the guest SSID and logon using the new guest ID and password 11. Verify that the laptop gets an IP address from the configured DHCP server and verify connectivity 12. Associate a laptop configured to use WPA to the employee SSID and logon using the employee SSID and password Employees and guests should be able to connect to their respective SSIDs and access control should allow employees full access while limiting guests to Internet only for http and https. If external/Internet connectivity is not available then a server can be setup and access controls adjusted to allow/block access to that server for employees vs. guests.

-5-

1.3 Automatic channel and power assignment
Test case Equipment required Topology Performs automatic initial channel and power assignment for all access points in the network. 4+ APs 1 WLAN switch 1 L2/L3 switch (optional)

Description and testing steps

Expected results.

1. Enable the automatic resource management feature for the WLAN solution, if required. 2. Verify that the access points initially come up with the default channel. 3. Verify that the APs are allocated channels and power to minimize interference and optimize coverage. The adjacent APs should be on different channels and APs on the same channel should be on lower power levels to minimize interference as opposed to APs that are unique on a single channel. The WLAN solution assigns channels and power to the access points in a manner to minimize interference and optimize coverage. Also it takes into account interference from other sources (other than the Vendor’s access points).

-6-

1.4 Dynamic RF intelligence
Test case Verify that the WLAN solution can dynamically adapt to changing RF environments. 3 APs 1 WLAN switch 2+ 3rd Party APs 3 wireless clients/laptops 1 File/FTP server 1 L2/L3 switch/hub for 3rd party APs and File server 1 L2/L3 switch (optional)

Equipment required

Topology

Description and testing steps

Expected results.

1. Connect the APs and let the automatic resource management algorithm converge to a channel plan. If three APs are used in a clean environment on a 802.11b/g band, it should generally default to a channel plan with the APs on channels 1,6 and 11 respectively. 2. Use 2 (or more) 3rd party APs and a few wireless clients (associated to the 3rd party APs) to generate interference on one of the channels being used by the “infrastructure” APs (channel 11 in the topology shown). The wireless client can download a file from a file server at the same time to generate the interference. 3. If enough interference is detected by the AP on channel 11, it will change channels and cause a change in channel/power assignment for other APs as well. Note change in channel and power assignment for all APs. The WLAN solution can detect 802.11 interference and adapt the RF network to minimize impact due to the interference.

-7-

2. Security - Intrusion Detection/Prevention capabilities
This section outlines the test cases needed to test the capabilities provided by the wireless LAN solution to protect the network from various kinds of threats and vulnerabilities on the wireless network. These capabilities are critical to ensuring the security and high availability of the network.

2.1 Rogue AP (WEP) detection/classification/containment
Test case Test the capability of the wireless LAN solution to detect an un-trusted AP and classify it as being interfering (un=trusted AP not connected to the network) or rogue (un-trusted AP connected to the network and therefore being a security threat). The interfering/rogue AP must be running WEP or WPA-PSK (not open-system). 1 WLAN controller 1 AP 1 Third Party AP 1 wireless client 1 L2/L3 switch (optional)

Equipment required

Topology

Description and testing steps

1. Configure the WLAN switch and AP to be operational. 2. Start the 3rd party AP and configure it to accept clients using WEP or WPA-PSK, but do NOT connect it to the network. 3. Verify that the WLAN solution detects the AP as an interfering AP. 4. Connect the 3rd party AP to the switch and configure it to accept client using WEP or WPA-PSK (as an example to

-8-

Expected results.

illustrate that the WLAN solution can detect rogue APs that use encryption as well). Also configure the 3rd party AP NOT to broadcast the SSID. 5. Associate the client to the rogue AP and ping a destination using this connection. 6. Verify on the WLAN switch console that the AP is detected and classified as Rogue. 7. Enable Rogue AP containment. 8. Verify that the WLAN solution is able to shut down the AP detected as Rogue (no wireless client should be able to associate and send traffic through this rogue access point). The WLAN solution should be able to detect un-trusted access points and be able to detect whether this access point is connected to the network or not. This determines whether the access point is a security threat or just the cause of interference.

-9-

2.2 Ad-hoc networks detection and containment
Test case Test the capability of the wireless LAN solution to detect an ad-hoc network and classify it as being insecure if it detects the ad-hoc network as being connected to the network. 1 WLAN switch 1 AP 2 laptops (supporting ad-hoc networks) with wireless NICs 1 L2/L3 switch (optional)

Equipment required

Topology

Description and testing steps

Expected results.

1. Configure the WLAN switch and AP to be operational. 2. Configure two wireless clients to set up an ad-hoc network. In the first case do not connect either of these clients to the network. 3. Verify that the WLAN solution detects the Ad-hoc network as an interfering Ad-hoc network 4. Connect one of the wireless clients to the network using a wired connection 5. Verify that the WLAN solution detects and classifies the Ad-hoc network as being insecure by determining it is connected to the network. 6. Enable Ad-hoc network protection and verify that the WLAN solution can shut down the Ad-hoc network when it is detected as being insecure. The WLAN solution should be able to perform the following IDS/IPS activities: 1. Detect the presence of Ad-hoc networks 2. Classify the Ad-hoc network as being interfering or insecure by determining if any of the clients is connected to the wired network. 3. Contain the Ad-hoc network by shutting it down. Note: some ad-hoc clients (Intel Centrino being most common) do not respond properly to de-authentication packets and will also change channels to avoid being contained.

- 10 -

2.3 Blacklist WiFi client based on firewall violations
Test case Test the capability of the wireless LAN solution to detect an violation of firewall policies and automatically blacklist a client and prevent that client from associating to the wireless network. 1 WLAN switch 1 AP 1 wireless client 1 file server 1 L2/L3 switch (optional)

Equipment required

Topology

Description and testing steps

Expected results.

1. Configure the WLAN switch and AP to be operational with guest access on an open-system SSID with permission to use HTTP and HTTPS with FTP denied and blacklisting if FTP is used. 2. Associate the client to the guest SSID and authenticate to the captive portal 3. Connect the file server to the network using a wired connection 4. Verify that the wireless client can access the file server using HTTP and/or HTTPS 5. Attempt to access the file server using FTP 6. Verify that the client cannot FTP files from the file server and that the client is blacklisted from the WLAN The WLAN solution should be able to block FTP access and also blacklist the client from the WLAN. This is different from just blocking FTP at a firewall somewhere in the network after the WLAN controller as it is actually preventing the violating client from even access the WLAN.

- 11 -

3. Performance and Scalability
This section covers the test cases that verify support for Mobility, Redundancy, QoS, and Load Balancing. NOTE: the roaming tests are extremely dependent on the client cards used and hence it is recommended that a variety of client cards be used for the mobility test cases.

3.1 Intra-VLAN roaming
Test case Test to verify that a client can roam between access points managed by the same WLAN switch and present on the same wireless user VLAN. It also aims to measure the time required for a client to roam between the access points. 2 APs 1 WLAN switch 1 wireless client 1 L2/L3 switch between the WLAN switch and the APs (optional)

Equipment required

Topology

Description and testing steps

Expected results.

1. Configure a WLAN network with the test SSID and WPA2 and a valid user for authentication. (This can also be done with WPA, WPA-PSK or WEP as some clients may not have WPA2 drivers but also confirm that the WLAN system is WPA2 certified.) 2. Connect the two access points on the same management VLAN – you can connect the AP directly to the WLAN switch or to a L2/L3 switch between the WLAN switch and the AP. 3. Associate the client to the WLAN network. Note the AP that the client connects to. Start a continuous ping from the wireless client. 4. Shut down the AP that the client is connected to (NOTE: this is not the a natural roaming scenario and therefore if possible, position the APs such that one of the APs is physically close to the wireless client while the other is farther away. Roaming can then be tested by physically moving the wireless client from one AP towards the second AP. Alternatively roaming can be induced by slowly placing aluminum foil over the AP antennas to block the signal.) 5. Measure the number of pings lost during the roam. With a well designed client driver roaming should incur minimal packet loss. 802.1x authentication will incur some latency/loss on roaming. Note: roaming ping loss will be greater if performing the test by shutting down the access point.

- 12 -

3.2 Inter-VLAN roaming
Test case Test to verify that a client can roam between access points connected to the same WLAN switch and present on two different subnets/VLANs. It also aims to measure the time required for a client to roam between the access points. 2 APs 1 WLAN switch 1 wireless client 1 L2/L3 switch between the WLAN switch and the APs (optional)

Equipment required

Topology

Description and testing steps

Expected results.

1. Configure a WLAN network with the test SSID and WPA2 and a valid user for authentication. (This can also be done with WPA, WPA-PSK or WEP as some clients may not have WPA2 drivers but also confirm that the WLAN system is WPA2 certified.) 2. Configure the two access points to use different user VLANs for the test SSID (e.g. AP1 assigns users to VLAN 10 while AP2 assigns users to VLAN20). Connect the two access points on the same management VLAN – you can connect the AP directly to the WLAN switch or to a L2/L3 switch between the WLAN switch and the AP. 3. Associate the client to the WLAN network. Note the AP that the client connects to. Start a continuous ping from the wireless client. 4. Shut down the AP that the client is connected to (NOTE: this is not the a natural roaming scenario and therefore if possible, position the APs such that one of the APs is physically close to the wireless client while the other is farther away. Roaming can then be tested by physically moving the wireless client from one AP towards the second AP. Alternatively roaming can be induced by slowly placing aluminum foil over the AP antennas to block the signal.) 5. Measure the number of pings lost during the roam. With a well designed client driver roaming should incur minimal packet loss and the client should not obtain a new IP address. 802.1x authentication will incur some latency/loss on roaming. Note: roaming ping loss will be greater if performing the test by shutting down the access point.

- 13 -

3.3 Secure Inter-switch mobility
Test case Test to verify that a client can roam between access points connected to two different WLAN switches It also aims to measure the time required for a client to roam between the access points. 2 APs 2 WLAN switches 1 wireless client 1 L2/L3 switch between the WLAN switch and the APs (optional)

Equipment required

Topology

Description and testing steps

1. Configure two WLAN controllers. One of the WLAN controllers as the master controller and the other is configured as a local controller. 2. Configure a WLAN network with the test SSID and WPA2 and a valid user for authentication. (This can also be done with WPA, WPA-PSK or WEP as some clients may not have WPA2 drivers but also confirm that the WLAN system is WPA2 certified.) 3. Configure one of the APs to connect to the master controller and the other AP to connect to the local controller. 4. Verify the validity of all configuration by associating a client with each of the APs and verifying connectivity 5. Associate the client to the WLAN network. Note the AP that the client connects to. Start a continuous ping from the wireless client. 6. Shut down the AP that the client is connected to (NOTE: this is not the a natural roaming scenario and therefore if possible, position the APs such that one of the APs is physically close to the wireless client while the other is farther away. Roaming can then be tested by physically moving the wireless client from one AP towards the second AP. Alternatively roaming can be induced by slowly placing aluminum foil over the AP antennas to block the signal.) 7. Verify that the client regains connectivity and retains the same IP address and all application sessions are maintained intact. 8. Measure the number of pings lost during the roam. Measure

- 14 -

the time for lost connectivity during the roam if possible.

Expected results.

The WLAN solution maintains the sessions when the client roams across switches and subnets. The client still maintains the same user role and privileges after roaming. With a well designed client driver roaming should incur minimal packet loss and the client should not obtain a new IP address. 802.1x authentication will incur some latency/loss on roaming. Note: roaming ping loss will be greater if performing the test by shutting down the access point.

- 15 -

3.4 Self-Healing – AP failure due to AP shut down
Test case Verify how Vendor APs dynamically adjust their channel and power settings to compensate for a failed neighbor AP.

Equipment required

1 WLAN controller 4 APs 1 Wireless Client 1 L2/L3 Switch (optional)

Topology

Description and testing steps

Expected results.

1. Configure the 4 APs and WLAN controller so that they are operational. 2. Configure the APs to be on a 3 channel plan for 802.11bg (1,6, and 11) 3. Have the APs dynamically choose their channel and power settings. 4. Note down each Vendor AP’s channel and power setting after a couple of minutes. 5. Have a wireless client associate to one of the APs and send a continuous ICMP ping 6. Check what AP the wireless client is connected to and pull the power from that AP. 7. After a few minutes have passed, check the channel and power settings of each AP. First of all, the 4 APs should dynamically choose the best 802.11bg channels and power settings for their environment. After the one AP is powered down you should see some of its neighbor APs adjust to higher power settings (or even change 802.11 bg channel settings) to compensate for the failed AP without dropping more than a few packets from the wireless client’s session.

- 16 -

3.5 Self-Healing – AP failure due to Radio failure
Test case Verify how Vendor APs dynamically adjust their channel and power settings to compensate for an AP that has an Antenna or Radio failure.

Equipment required

1 WLAN controller 4 APs Enough aluminum foil to wrap one AP three times 1 L2/L3 Switch (optional)

Topology

Description and testing steps

1. Configure the 4 APs and WLAN controller so that they are operational. 2. Configure the APs to be on a 3 channel plan for 802.11bg (1,6, and 11) 3. Have the APs dynamically choose their channel and power settings. 4. Note down each AP’s channel and power setting after a couple of minutes. 5. Now cover one of the APs with aluminum foil (make sure it is well wrapped at least 3 times and if it the AP has any external antennas then remove them so that hardly any RF can be seen from that AP) 6. After several minutes have passed after that AP was covered in aluminum foil, check the channel and power settings of each Vendor AP. First of all, the 4 APs should dynamically choose the best 802.11bg channels and power settings for their environment. After the one AP is well covered in aluminum foil you should see some of its neighbor APs adjust to higher power settings (or even change 802.11 bg channel settings) to compensate for the AP that has its RF hampered or antennas removed.

Expected results.

- 17 -

3.6 Controller Redundancy
Test case Verify that the WLAN solution can offer a redundancy solution that helps the clients regain connectivity in an acceptable time in the event of a controller failure or loss of connectivity. 1 AP 2 WLAN controllers 1 L2/L3 switch between Vendor’s WLAN switch and AP 1 Wireless client 1 Workstation/Server

Equipment required

Topology

Description 1. Configure a redundant topology between the two wireless LAN controllers. and testing 2. Verify that the access point is connected to one of the controllers. steps 3. Associate the client to the access point. Run a continuous ping from the client to a server to monitor loss of connectivity. 4. Shut down the active switch or disconnect it from the network. 5. Measure the time it takes for the client to regain connectivity through the backup switch. Expected Ping loss should be minimal (2-3 pings in most cases) and the client should not results. get a new IP address with the failover.

- 18 -

3.7 QoS prioritization of user-specified traffic on single SSID
Test case Verify that the WLAN solution can provide the ability to prioritize voice traffic over data traffic.

Equipment required

1 AP 1 WLAN Switch 1 wireless client (configured as Iperf Client) 2 VoWLAN handsets (that support SIP protocol) 1 wired phone that supports SIP protocol (or wireless handset) 1 L2/L3 switch between WLAN switch and APs (optional) 2 Wired Desktop (1 configured as Iperf Server and 1 configured as SIP Server)

Topology

Description and testing steps

Expected results.

1. Configure SIP server to allow 3 SIP phones to communicate with each other. 2. Have all wireless devices associate to the same AP using the same SSID. 3. Have 1 VoWLAN handset configured with a QoS profile. 4. Have the other handset and wireless device (iperf client) configured with no QoS profile. 5. Configure and run iperf server with the following setting: iperf -s -u -t 300 -i 1 6. Configure and run iperf client with the following setting: iperf -c <IP address of iperf server> -t 300 -i 1 -u -b 256k 7. Make a phone call from the wired SIP phone to the VoWLAN handset that has no QoS profile. (take note of the voice quality) 8. Make a phone call from the wired SIP phone to the VoWLAN handset that has a QoS profile. (take note of the voice quality) The WLAN solution should demonstrate that the VoWLAN handset with no QoS profile has bad voice quality (choppy and not clear) to the wired SIP phone during high data traffic congestion while the VoWLAN handset with a QoS profile has great voice quality to the wired SIP phone even with the same high data traffic congestion.

- 19 -

3.8 Load balancing based on user thresholds
Test case Verify that the WLAN solution can perform load balancing on the basis of thresholds set for number of users per access point. 1 WLAN controller 2 APs 3 wireless clients L2/L3 switch between WLAN switch and APs (optional)

Equipment required

Topology

Description and testing steps

Expected results.

1. Position the APs such that one AP is close to the wireless clients while the other AP is “farther” away from the clients 2. Enable load balancing on the controller. 3. Set the user threshold to a number greater than 3. 4. Connect the wireless clients one at a time. All three clients should connect to the AP that is closer. 5. Disconnect all clients from the AP. 6. Change the user threshold to 2. 7. Connect the wireless clients one at a time. 8. Verify that the third client connects to the second AP. Normal wireless NIC driver behavior is to associate to the AP with the strongest signal. Load balancing should cause any clients attempting to associate after the threshold is reached on an AP to associate to another available AP. Note: configurations that use “local probe response” will require this feature to be turned off for load balancing to operate, but voice call admission control will continue to work even with local probe response enabled.

- 20 -

Load balancing based on bandwidth thresholds
Test case Verify that the WLAN solution can perform load balancing on the basis of thresholds set for bandwidth consumption on each access point. WLAN controller 2 APs 3 wireless clients L2/L3 switch between WLAN switch and APs(optional)

Equipment required

Topology

Description and testing steps

Expected results.

1. Position the APs such that one AP is close to the wireless clients while the other AP is “farther” away from the clients 2. Enable load balancing on the controller. 3. Set the load balancing bandwidth threshold to about 5 Mbps 4. Connect the wireless clients one at a time and start a large ftp download or video stream. All three clients should connect to the AP that is closer. 5. Disconnect all clients from the AP. 6. Change the load balancing bandwidth threshold to 2 Mbps 7. Connect the wireless clients one at a time and start a large ftp download or video stream with each passing about 1 Mbps of traffic 8. Verify that the third client connects to the second AP. Normal wireless NIC driver behavior is to associate to the AP with the strongest signal. Load balancing should cause any clients attempting to associate after the threshold is reached on an AP to associate to another available AP. Note: configurations that use “local probe response” will require this feature to be turned off for load balancing to operate, but voice call admission control will continue to work even with local probe response enabled.

- 21 -

4. Troubleshooting and Management
4.1 Station statistics
Test case Verify that the WLAN solution supports collecting statistics about individual stations/clients. This is a critical requirement in a wireless LAN solution to ensure that the administrators can monitor and troubleshoot individual clients when required. 1 WLAN controller 1 AP 1 wireless client 1 L2/L3 switch between the WLAN switch and AP (optional)

Equipment required

Topology

Description and testing steps

Expected results.

1. Configure the WLAN controller and AP to accept connections from wireless clients. 2. Connect a wireless client to the wireless network. Verify that the client is able to communicate with a server. 3. Run any data transaction from the client to the file server. 4. Monitor the client statistics if they are available. The wireless client should be on the list. 5. Move the client away from the access points (such that the rate of data transfer drops for this particular client). This should be reflected in the statistics. 6. The statistics that can be monitored on a per-client basis should include: a. RSSI/Signal level: current and low/high watermarks. b. 802.11 packet type distribution c. Packet size distribution d. Packet rate distribution The WLAN solution supports the ability to monitor detailed statistics on a perclient basis.

- 22 -

4.2 Per-user debugging capabilities
Test case Verify that the WLAN solution supports the ability to monitor and debug a client’s activity. This is a critical feature that is required to troubleshoot a issue about a client from a centralized location in an easy manner. 1 WLAN controller 1 AP 1 wireless client 1 file server 1 L2/L3 switch between the WLAN switch and AP (optional)

Equipment required

Topology

Description and testing steps

Expected results.

1. Configure the WLAN controller and AP to accept connections from wireless clients, preferably using 802.1x/WPA/WPA2. 2. Connect a wireless client to the wireless network. Verify that the client is able to communicate with a server. 3. Run any data transaction from the client to the file server. 4. If the WLAN solution provides the capability to do “per-user debugging”, use this feature to monitor the activities of the client at different layers (physical to application layer). 5. This should provide a log of all activity related to that client. This includes: a. 802.11 events b. Authentication events c. DHCP events d. Access control events The WLAN solution supports an extremely sophisticated per-client debugging capability to monitor and troubleshoot issues on a per-client basis if required.

- 23 -

4.3 Remote packet capture
Test case Verify that the WLAN solution supports the ability to capture live packet traces, including 802.11 frames from a remote host/workstation. Packet capture should be possible for only the client, for all traffic on the specific channel, and the option to do packet capture from another device to monitor communication between the client and an AP. Optionally, perform the same test via remote AP (without a remote controller). 1 WLAN controller 1 AP + 1 Air Monitor 1 Wireless client Monitoring Station running Ethereal and/or Airopeek L2/L3 switch between WLAN switch and AP (optional)

Equipment required

Topology

Description 1. Configure the AP/controller to accept connections. and testing 2. If the WLAN solution offers the capability to redirect packet capture from a steps wireless AP to a remote monitoring station, enable the same. 3. Direct the packet capture to the monitoring station’s IP address and configure the format to be compatible with Ethereal or Airopeek as required. 4. Verify that there is no firewall/ACL blocking the traffic types used by the Aruba APs to communicate with the monitoring station. 5. Start packet analysis software on the Monitoring Station and if it requires configuration for a remote sensor, apply the required configuration. 6. Verify that the administrator can view the packets from a remote location and apply filters as required. 7. Repeat to capture all traffic on the channel 8. Repeat to capture traffic from a third device to monitor communication between the client and the AP Expected The WLAN solution supports remote packet capture to allow the administrators results. the ability to troubleshoot events from a remote location.

- 24 -

4.4 Session mirroring
Test case Verify that the WLAN solution supports the capability to do session mirroring. This gives the administrator the ability to monitor and receive all packets for a session at a remote location. This is an excellent tool for troubleshooting. 1 WLAN controller 1 AP Wireless client(s) Monitoring Station running Ethereal or any such packet analysis software L2/L3 switch between the AP and WLAN switch (optional)

Equipment required

Topology

Description 1. Configure the AP and controller to accept wireless clients. and testing 2. Connect the client and authenticate the client to place the client in a role steps that allows FTP traffic 3. Run a FTP transaction to get a file from a FTP server. 4. Configure the WLAN controller to perform session mirroring for the FTP session and send the packet capture to the monitoring station (If this feature is supported) 5. Run Ethereal on the monitoring station to verify that the session can be monitored from a remote location. 6. Verify that only packets from the session are received on the monitoring station. Expected The WLAN solution supports an extremely sophisticated troubleshooting results. mechanism (session mirroring) that provides the administrator with a powerful tool to troubleshoot issues from a remote location.

- 25 -

4.5 RF heat maps
Test case Test the ability of the WLAN solution to display RF heat maps that provide an important tool to monitor and troubleshoot the wireless network. 4+ APs 1 WLAN controller Floor plan of the site L2/L3 switch between the APs and the WLAN switch (optional)

Equipment required

Topology

Description and testing steps

Expected results.

1. Deploy multiple access points (at least 4-5 access points) on a floor or a section of a floor. 2. Import the floor plan on the controller/management software and note the physical locations of the access points on the floor plan. 3. Verify that RF characteristics such as RF coverage/interference/SNR are displayed in an easy-to-use and understand way. The WLAN solution provides a comprehensive set of monitoring RF environments from a central location – including the ability to monitor coverage and interference for different bands and rates.

- 26 -

4.6 Location tracking
Test case Test the ability of the WLAN solution to display location information for any WiFi device without the need for a site survey or any type of walkabout/calibration. 4+ APs/AMs 1 WLAN controller Floor plan of the site L2/L3 switch between the APs and the WLAN switch (optional)

Equipment required

Topology

Description 1. Deploy multiple access points (at least 4-5 access points) on a floor or a and testing section of a floor. For greater accuracy and quicker location results deploy steps one or two AMs or convert one or two of the APs to AMs. 2. Import the floor plan on the controller/management software and note the physical locations of the access points on the floor plan. 3. Position the APs as accurately as possible on the floor plan 4. Identify a WiFi device to locate (a PC, PDA, rogue AP, etc.) and verify that the location is accurate within 3-10 meters. Expected The WLAN solution provides a location tracking capability without any results. additional servers or software, site surveys or calibration. Note: Location accuracy may improve over time as the device is being tracked and additional RF samples are taken. Accuracy is highest when more than 3 APs or AMs can “hear” the device on the same channel.

- 27 -


相关文章:
Experimental Evaluation of UMTS and Wireless LAN for Inter-....pdf
Experimental Evaluation of UMTS and Wireless LAN for Inter-Vehicle ...We tested over this long period of time to see whether there is in?...
EPA_Evaluation_Plan.doc
Plan evaluation under un... 暂无评价 16页 免费 Generic Wireless LAN eva... 27页 5财富值 3.2recall plan test and ... 暂无评价 14页 免费...
TCP and UDP performance over a wireless LAN.pdf
Performance Evaluation o... 暂无评价 5页 免费 ...GHz DSSS wireless LAN and analyze its behavior. ...Our TCP tests show for the ?rst time the ...
...based CRC computation scheme for high-speed wireless LAN ....pdf
high-speed wireless LAN design_IT/计算机_专业资料...2 N-byte message block for processor Evaluation ...Memory 7 is used to store test input data, ...
...of IEEE802.11b for Performance Analysis of Wireless LAN ....pdf
The model is suitable for performance evaluation and investigation of wireless...test beds and simulation of large-scale IPv6 networks utilizing wireless LAN...
...for IEEE 802.11 Wireless LAN P.pdf
Performance Evaluation of Distributed Co-Ordination Function for IEEE 802.11 Wireless LAN P This paper investigates the performance of IEEE 802.11 wireless...
...methods for position estimation system using wireless LAN_....pdf
Evaluation of pre-acquisition methods for position estimation system using wireless LAN_专业资料。In recent years, position estimation systems using wireless ...
...a MAC Protocol for Radio over Fiber Wireless LAN operating....pdf
Performance Evaluation of a MAC Protocol for Radio over Fiber Wireless LAN operating in the_专业资料。Abstract Wireless networks using radio over fiber ...
Energy efficient scheduler design in wireless networks in_....pdf
We propose a PSM for a generic wireless LAN, which is different in many...This scenario is “static” in that, for each test case, once packets ...
...in Evaluating PublishSubscribe Services in a Wireless ....pdf
PublishSubscribe Services in a Wireless Network_... at network planning, not performance evaluation. ...Siena uses a generic message-based communication ...
...Point Coordination Function in IEEE 802.11 Wireless LAN_....pdf
A Modified Point Coordination Function in IEEE 802.11 Wireless LAN_专业资料...VII. EVALUATION OF THE RESULTS As the results show, the modified PCF ...
...and evaluation of iMesh An infrastructure-mode wireless ....pdf
Design and evaluation of iMesh An infrastructure-...[2] IEEE 802.11b/d3.0 Wireless LAN Medium ...http://hostap.epitest.?. [14] D. Maltz, J...
Wireless Network Support for Adaptive Real-Time App....pdf
Wireless Network Support for Adaptive Real-Time Applications Abstract- We ... through the evaluation of several scenarios simulated on NS the Network...
English Evaluation Test.doc
2. Wai Lan told them that Peter has hurt his foot the day before. 3....The father was hated by all his daughters 6 English Evaluation Test Name:...
Enhancements and Performance Evaluation of Wireless Local ....pdf
Enhancements and Performance Evaluation of Wireless ... a wireless LAN interface, and a receiver/...Two states, (PT_TEST and PT_BACKOFF), and ...
Open Source Software for Evaluation of Applications and ....pdf
Open Source Software for Evaluation of Applications...(LANs), a wireless LAN and a MPLS/Diffserv ...The results of all tests verified that the ...
Broadband Wireless Local Loop Evaluation Via an Active TCP ....pdf
Broadband Wireless Local Loop Evaluation Via an Active TCP Connection ...We test this tool over wired LAN, cable modem and broadband wireless ...
Performance evaluation of TCP over WLAN 802.11 with the Snoop....pdf
Performance evaluation of TCP over WLAN 802.11 with the Snoop performance ...To facilitate testing of the Snoop protocol, we implemented an additional ...
LAN8710 Customer Evaluation Board.pdf
LAN8710 Customer Evaluation Board_信息与通信_工程科技_专业资料。LAN8710 用户...LAN8710(i) and Magnetics +5V 1 2 E +3.3V TP1 TEST_POINT Yellow FB1 ...
Experimental Evaluation of a Wireless Ad Hoc Network.pdf
Experimental Evaluation of a Wireless Ad Hoc ...Each card contains a LAN controller, modem ...In our future work, we plan to use newer ...