NDISTest 6.5 - WlanPerformance

This automated test suite verifies the performance of the 802.11 extensible wireless drivers and the miniport drivers in hibernation and resume scenarios.

Test details

Associated requirements	Device.Network.WLAN.Base.ConformToNDIS Device.Network.WLAN.Base.MeetPerformanceReq Device.Network.WLAN.Base.OnlyWDFOrNDIS630Calls Device.Network.WLAN.Base.SupportWiFiAutoSaveMode Device.Network.WLAN.CSBBase.ConformToNDIS Device.Network.WLAN.CSBBase.MeetPerformanceReq Device.Network.WLAN.CSBBase.OnlyWDFOrNDIS630Calls Device.Network.WLAN.CSBBase.SupportWiFiAutoSaveMode See the device hardware requirements.
Platforms	Windows 7 (x64) Windows 7 (x86) Windows RT (ARM-based) Windows 8 (x64) Windows 8 (x86) Windows RT 8.1 Windows 8.1 x64 Windows 8.1 x86
Expected run time	~60 minutes
Categories	Certification Reliability
Type	Automated

 

Running the test

Before you run the test, complete the test setup as described in the test requirements: Wireless LAN (802.11) Testing Prerequisites.

The following suites are available:

• Performance_cmn

• Performance_ext

• VWiFiPerformance_ext

The Performance_cmn suite consists of the following:

Name	Description
	Send data from the DUT to an access point and collect statistics (cipher: {0}, packet size: {1}, packet lists per send: {2}, time duration: 30 seconds}) Ciphers used: None,WEP,TKIP,CCMP Packet size: 1500
	Send data from an access point to the DUT and collect statistics (cipher: {0}, packet size: {1}, packet lists per send: 40, time duration: 30) Ciphers used: None,WEP,TKIP,CCMP Packet size: 1500
	Send data from the DUT to an access point and verify the send data rate (cipher: None, packet size: 1488, packet lists per send: 21, time duration: 30, data rate sample interval: 5ms)

 

The Performance_ext suite consists of the following:

Name	Description
VerifyScanning	Scan the list with an access point using the following channel pairs: 1 and 11, 1 and 6, and 6 and 11. Verify that the scan completed within the required time constraint and that two known access points on the same PHY but with different channels and different SSIDs are returned in the scan list. Scan the list with an access point using 10 random pairs from channels between 1 and 12. Verify that the scan completed within the required time constraint and that two known access points on the same PHY but with different channels and different SSIDs are returned in the scan list.
VerifyAPLossDetection	Verify the DUT successfully detected that the hidden access point disappeared within 2 seconds. Verify the DUT successfully detected that the visible access point disappeared within 2 seconds.
VerifyFirstTimeConnection	Verify the DUT successfully associates with a visible access point within 10 seconds. Verify the DUT successfully associates with a hidden access point within 10 seconds.
ValidateStaleScanListAfterResumingFromSleep	Verify that a driver does not return an outdated scan list on resume without a forced active scan. Connect to the first access point. Shut down the first and second access point with delay. Resume the DUT when it hibernates. Verify that a driver does not return an outdated scan list on resume with a forced active scan. Verify that a driver does not return an outdated scan list on resume without a forced active scan. Do not connect to the first access point. Shut down the first and second access point with delay. Resume the DUT when it hibernates. Validate that a driver does not return outdated scan list on resume with forced active scan Verify that a driver does not return an outdated scan list on resume without a forced active scan. Connect to the first access point. Shut down the first and second access point with delay. Resume the DUT when it goes to standby. Verify that a driver does not return an outdated scan list on resume with a forced active scan. Verify that a driver does not return an outdated scan list on resume without a forced active scan. Do not connect to the first access point. Shut down the first and second access point with delay. Resume the DUT when it goes to standby. Verify that a driver does not return an outdated scan list on resume with a forced active scan.
VerifyScanningAfterResumingFromSleep	Hibernate the DUT and verify that DUT miniport completes a scan within 4 seconds after resuming from hibernate.
VerifyLowPowerSameNetworkSameAP	Verify that the DUT successfully associates with a hidden access point within 1 second after resuming from hibernate. Verify that the DUT successfully associates with a visible access point within 1 seconds after resuming from hibernate.
VerifyLowPowerSameNetworkDifferentAP	Verify that the DUT roams to a new hidden access point after the original access point disappears during hibernate. The DUT must successfully associate with the new access point within 4 seconds after resuming from hibernate. Verify that the DUT roams to a new visible access point after the original access point disappears during hibernate. The DUT must successfully associate with new access point within 4 seconds after resuming from hibernate.
VerifyScanningAfterResumingFromSleep	Put the DUT into standby mode. Verify that the DUT miniport completes a scan within 4 seconds after resuming from standby.
VerifyLowPowerSameNetworkSameAP	Verify that the DUT successfully associates with a hidden access point within 1 second after resuming from standby. Verify that the DUT successfully associates with a visible access point within 1 second after resuming from standby.
VerifyLowPowerSameNetworkDifferentAP	Verify that the DUT roams to a new hidden access point after the original access point disappears during Standby. The DUT must successfully associate with the new access point within 4 seconds after resuming from standby. Verify that the DUT roams to new visible access point after the original access point disappears during standby. The DUT must successfully associate with the new access point within 4 seconds after resuming from standby.

 

The VWiFiPerformance_ext suite consists of the following:

Name	Description
Scenario setup – Virtualization is disabled and the PrimaryPort(STA) is connected.	Measure data throughput on the primary port sent by PrimaryPort(STA). Measure data throughput on the primary port sent by TestAP.
Scenario setup – Virtualization is enabled, the PrimaryPort(STA) is connected, and the SecondaryPort (SoftAP) is not running.	Measure data throughput on the primary port sent by PrimaryPort(STA). Compare data throughput and see if performance has degraded beyond an acceptable limit. Measure data throughput on the primary port sent by TestAP. Compare data throughput and see if performance has degraded beyond an acceptable limit.
Scenario setup – Virtualization is enabled, the PrimaryPort(STA) is connected, the SecondaryPort (SoftAP) is running, and the SUT is not connected to the SoftAP.	Measure data throughput on the primary port sent by PrimaryPort(STA). Compare data throughput and see if performance has degraded beyond an acceptable limit. Measure data throughput on the primary port sent by TestAP. Compare data throughput and see if performance has degraded beyond an acceptable limit.
Scenario setup – Virtualization is enabled, the PrimaryPort(STA) is connected, the SecondaryPort (SoftAP) is running, and the SUT is connected to the SoftAP.	Measure data throughput on the primary port sent by PrimaryPort(STA). Compare data throughput and see if performance has degraded beyond an acceptable limit. Measure data throughput on the primary port sent by TestAP. Compare data throughput and see if performance has degraded beyond an acceptable limit.
Scenario setup – Virtualization is enabled, the PrimaryPort(STA) is connected, the SecondaryPort (SoftAP) is running, and the SUT is connected to the SoftAP.	Measure data throughput on the primary port sent by PrimaryPort(STA). Measure data throughput on secondary port sent by: SecondaryPort(SoftAP). Compare data throughput and see if performance has degraded beyond an acceptable limit. Measure data throughput on the primary port sent by TestAP. Measure data throughput on the secondary port sent by SUT(STA). Compare data throughput and see if performance has degraded beyond an acceptable limit.

 

Troubleshooting

For troubleshooting information, see Troubleshooting Wireless LAN (802.11) Tests.

If you receive the failure message Cannot load Counter Name data because an invalid index was read from the registry, the performance counters in the system need to be rebuilt. This can be done by using the following procedure:

To rebuild the performance counters in the system

1. From an elevated command prompt, run the following command:

   lodctr /r

   You will receive the following message:

   Info: Successfully rebuilt performance counter setting from system backup store.

2. After this action, some providers might be disabled. Run the following command to check status:

   lodctr /q

   The output will be similar to the following:

   Performance Counter ID Queries [PERFLIB]:    Base Index: 0x00000737 (1847)    Last Counter Text ID: 0x00001560 (5472)    Last Help Text ID: 0x00001561 (5473)[.NET CLR Data] Performance Counters (Enabled)    DLL Name: netfxperf.dll    Open Procedure: OpenPerformanceData    Collect Procedure: CollectPerformanceData    Close Procedure: ClosePerformanceData    First Counter ID: 0x00001080 (4224)    Last Counter ID: 0x0000108C (4236)    First Help ID: 0x00001081 (4225)    Last Help ID: 0x0000108D (4237)
   

3. If it says (Disabled) next to a provider, you can enable it by using the following command:

   lodctr /e*:<provider name>*

   Where <provider name> is the string between the [ ] brackets at the start of the entry.

4. Rerun the test.

 

 

Send comments about this topic to Microsoft