terewbowl.blogg.se

1. ETHERNET TESTING PROCEDURES DRIVER
2. ETHERNET TESTING PROCEDURES SOFTWARE
3. ETHERNET TESTING PROCEDURES WINDOWS

This means a software iSCSI target must be configured on the SUT or an SMB share must be shared out. The test machine topology is such that the test network is back-to-back which means the support machine must also serve as a storage target. The test target on the DUT machine must have connectivity to network-based storage using either iSCSI or SMB. The below list outlines which tests require unique configurations. Some tests require unique configuration that is not or cannot be automatically taken care of by test jobs. HypervisorEnforcedCodeIntegrity:REG_DWORD Once that has occurred, the following Registry key must be created and set: HKLM\System\CurrentControlSet\Control\DeviceGuard

ETHERNET TESTING PROCEDURES WINDOWS

The Virtualization Based Security feature (VBS) of Windows Server 2016 must be enabled using Server Manager first. Test personnel must make sure that the first test computer in the list meets the minimum hardware requirements.

The default computer is the first test computer in the list. You must manually configure this computer to have multiple processor groups.

ETHERNET TESTING PROCEDURES DRIVER

If the driver is the same on all the computers in the pool, the system creates a schedule to run against all test computers.įor tests that do not include a driver to test, such as hard disk drive tests, the Windows HLK scheduler constrains the tests that validate the device's and driver's rebalance, D3 state, and multiple processor groups functionality to run on the default test computer. Additionally, that computer must contain the device and the driver that you want to test. If you use a pool of test computers to test devices, at least one computer in the pool must contain four processors and a minimum of 1 GB of RAM. For more information see Windows Server Installation Options. Additionally, the server system(s) being used for device or driver testing must have Server Core installed prior to testing. You do not need a computer that actually has more than 64 processors to test your device. These system capabilities are required to test the Rebalance, D3 State, and Multiple Processor Group functionality of the device and driver. To certify your product for use on servers, the test computer must support four processors and a minimum of 1 GB of RAM. Certification on client SKUs will require 2 processing cores while certification on server SKUs will require 4 processing cores. The machine requirements are often dictated by the features which the test target supports. It is recommended that this network be DHCP enabled. It is recommended that the backchannel switch be the same network which the test machines will use to communicate with the HLK controller. Tests which send 802.1q-tagged (VlanSendRecv, VMQ, 1c_priority, maybe others) DCB) (priority flow control, LLDP/DCBX interop, ETS (as some switches may strip 802.1p tags) The back-to-back connection is preferred in general as it takes away the possibility of the switch from interfering with the test (VLAN misconfigurations, flow control packets, and so on)Ī back-to-back connection is required for tests which a network switch may interfere with the result. The following diagram shows the recommended topology:

The interface alias names are as follows: Recently developed HLK tests prefixed with "" or "" in the title are single machine tests and require 3 network adapters on that machine. Machine topology for Network Adapter tests This is the topology that applies to all LAN devices (including devices which support QoS and Chimney). Topologies that differ from this are highly discouraged as they may require extra effort in order to get the tests running correctly. The following diagram shows the recommended machine topology. No name necessary, HLK jobs will automatically choose it This content applies to both stand-alone network adapters and integrated network devices.