Share via

Running the LAN (Ethernet) Tests

  • Article

To schedule the LAN (Ethernet) device tests, you can use the Device Console window in DTM Studio.

The following logo submission procedure demonstrates how to run the LAN device tests:

  1. Open DTM Studio.

  2. On the Explorers menu, click Device Console. (You can also switch to the Device Console window by clicking the Device Console tab in the lower left corner of DTM Studio.)

    Bb961478.LANTesting_RunningTest1(en-us,MSDN.10).png

  3. In the View By area, select Submission, and then in the Submission list, click <New Submission>.

    Bb961478.LANTesting_RunningTest2(en-us,MSDN.10).png

  4. Click Windows Vista Client.

    Bb961478.LANTesting_RunningTest3(en-us,MSDN.10).png

  5. Click Device Submission.

    Bb961478.LANTesting_RunningTest4(en-us,MSDN.10).png

  6. Click Network > LAN (Ethernet).

    Bb961478.LANTesting_RunningTest5(en-us,MSDN.10).png

  7. Click Basic.

    Bb961478.LANTesting_RunningTest6(en-us,MSDN.10).png

  8. In the Name for new submission box, enter a name for the submission, and then select the machine pool that the submission will be associated with.

    Bb961478.LANTesting_RunningTest7(en-us,MSDN.10).png

  9. In the Driver Install File (INF) box, locate the device’s INF file.

    Bb961478.LANTesting_RunningTest8(en-us,MSDN.10).png

  10. Review the summary page to make sure the information is correct, and then click Finish.

    Bb961478.LANTesting_RunningTest9(en-us,MSDN.10).png

  11. In the Available Devices area of the Device Console window, select a test device from the devices that appear. In the Available Jobs area, place a check next to the logo job, then right-click the logo job, and click Add Information.

    Bb961478.LANTesting_RunningTest10(en-us,MSDN.10).png

    The Job extension dialog box will open.

  12. In the Job extension dialog box, do the following:

    Bb961478.LANEthernetTesting_RunningTest11(en-us,MSDN.10).png

    1. In the Local Support Device area, select the support test device that is connected to the Test network Switch.
    2. From the Local Message Device list, select a device that is connected to the Support network Switch.
    3. In the Remote Machines area, select the computer (DTM Client 1) which hosts the Remote Support Device.
    4. In the Remote Support Device area, select the support test device that is connected to the Test network Switch.
    5. In the Remote Message Device list, select the device that is connected to the Support network Switch.
    6. Click Advanced Test Device Info to provide additional information of the test device. A detailed description of Advanced Test Device Info is given later in this subsection.
    7. Click Save.

Note The Local Test Device, Local Support Device, and Remote Support Device entries must be identical. This rule is the requirement of the logo submission. Although the Job extension dialog box does not enforce this policy, the actual test will fail if the three network devices are not the same.

The **Advanced Test Device Info** button gives the user a chance to provide more information about the device under test. After you click the button, the **Advanced Options** dialog box appears.  

![Bb961478.LANEthernetTesting\_AdvancedOptions(en-us,MSDN.10).png](images/Bb961478.LANEthernetTesting_AdvancedOptions(en-us,MSDN.10).png "Bb961478.LANEthernetTesting_AdvancedOptions(en-us,MSDN.10).png")

  
The following table provides a detailed description of every property in the **Advanced Options** window.

<table>
<thead>
<tr class="header">
<th>PropertyName</th>
<th>Type</th>
<th>Default value</th>
<th>Description</th>
</tr>
</thead>
<tbody>
<tr class="odd">
<td>CardBusAdapter</td>
<td>Bool</td>
<td>False</td>
<td>Is the device under test a Card Bus device?</td>
</tr>
<tr class="even">
<td>DisconnectSupported</td>
<td>Bool</td>
<td>True</td>
<td>Can the device under test generate disconnect and subsequent connect events under any scenario?</td>
</tr>
<tr class="odd">
<td>FiberOpticDevice</td>
<td>Bool</td>
<td>False</td>
<td>Is the device under test using Optical Fiber as the transmission medium?</td>
</tr>
<tr class="even">
<td>MapsExternalIoSpace</td>
<td>Bool</td>
<td>False</td>
<td>Does the device under test map IoSpace that falls outside of the range assigned to the device by the operating system?</td>
</tr>
<tr class="odd">
<td>MultipleDeviceInstancesSupported</td>
<td>Bool</td>
<td>True</td>
<td>Can two instances of the device under test be installed on a single machine?</td>
</tr>
<tr class="even">
<td>SupportNdisScatterGatherDma</td>
<td>Bool</td>
<td>True</td>
<td>Virtual network drivers should set to False as they are not required to support Scatter Gather DMA.</td>
</tr>
<tr class="odd">
<td>SystemIntegratedDevice</td>
<td>Bool</td>
<td>False</td>
<td>Is the device under test physically integrated on the system you are testing with and cannot be used on any other system?</td>
</tr>
</tbody>
</table>

The information provided in the **Advanced Options** dialog box helps **NDISTest** adjust its test cases to fit the capabilities of the test device. For example, if MultipleDeviceInstancesSupported is set as False, the **NDISTest** does not require the existence of the local support device during the logo submission. The default values of the properties should fit most LAN Ethernet devices.

After the user clicks **Save** on the Job Extension UI, the data in **Advanced Options** persists on the machine where the DTM Studio is installed. When a user launches a job more than once for the same test device, they do not have to add these properties again.

  1. Click Add Selected to add the job to the configured job list.

    Bb961478.LANTesting_RunningTest12(en-us,MSDN.10).png

After you complete the preceding steps, the job is ready for scheduling. After you click Schedule Jobs, DTM Studio will send the job to the DTM controller and dispatch the job on the designated DTM client machines. You can also put multiple configured jobs into the configured job list first, and then schedule them in one batch.

Send feedback on this topic
Built on December 10, 2009