Share via

LAN CS Test - IPv6 Longhaul

  • Article

This test verifies that the LAN device on systems that support InstantGo delivers reliable connectivity in Connected Standby.

The device seamlessly transitions between D0 and D2 states while in Connected Standby. The device maintains L2 connectivity while in Connected Standby. The device wakes up on matching wake patterns only. There are no spurious wakes while in Connected Standby. The wake packets are delivered without delay or buffering. The Real Time Communication app stays connected over IPv6 while in Connected Standby for 12 hours.

Test details

   
Specifications
  • Device.Network.LAN.CS.ReliableCSConnectivity
Platforms
  • Windows 10, client editions (x86)
  • Windows 10, client editions (x64)
Supported Releases
  • Windows 10
  • Windows 10, version 1511
  • Windows 10, version 1607
  • Windows 10, version 1703
  • Windows 10, version 1709
  • Windows 10, version 1803
  • Windows 10, version 1809
  • Windows 10, version 1903
  • Next update to Windows 10
Expected run time (in minutes) 720
Category Development
Timeout (in minutes) 43200
Requires reboot false
Requires special configuration false
Type automatic

 

Additional documentation

Tests in this feature area might have additional documentation, including prerequisites, setup, and troubleshooting information, that can be found in the following topic(s):

Running the test

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

Troubleshooting

For generic troubleshooting of HLK test failures, see Troubleshooting Windows HLK Test Failures.

For troubleshooting information, see Troubleshooting LAN Testing.

If you are still having problems completing this test, try the following:

  • If the device exits Connected Standby earlier than expected, make sure the device under test remains idle while the test runs.

  • If you get a system error for a control channel trigger, ensure that the network adapter is compatible with Connected Standby and it complies with NDIS 6.30 requirements.

  • If the OID request for a network adapter fails, ensure that the network adapter complies with NDIS 6.30 requirements.

  • If the network device removes unexpectedly, ensure that the driver is not crashing.

  • If the control channel trigger is detached, ensure that there is good reception and that the network adapter maintains L2 connectivity in Connected Standby.

  • If the network adapter disconnects, ensure that there is good reception.

  • If the push notification is triggered too early, ensure that the network adapter complies with NDIS 6.30 requirements and that the network adapter maintains L2 connectivity in Connected Standby.

  • If the push notification is triggered too late, ensure that the network adapter complies with NDIS 6.30 requirements and that the network adapter maintains L2 connectivity in Connected Standby.

  • If the push notification did not trigger on time, ensure that the network adapter complies with NDIS 6.30 requirements and that the network adapter maintains L2 connectivity in Connected Standby.

  • If you cannot install the package, ensure that the device under test is configured with the correct date and time. For more information, check the error description.

More information

Parameters

Parameter name Parameter description
queryTestDeviceID
TestInterfaceIndex
TestDeviceStaticIPV6
SupportInterfaceIndex
SupportDeviceStaticIPV6
CsDuration