Share via


LLD2 Responder Verification Tests

Note  This content applies to the Windows Logo Kit (WLK). For the latest information using the new Windows Hardware Certification Kit (HCK), see Windows HCK User's Guide on the Windows Hardware Dev Center.

Type: Automated Test

Overview

The LLD2 verification tool runs a series of tests against a device that implements the LLD2 responder protocol.

Details

This tool tests several aspects of the responder in accordance with the Router logo program's specification requirements. These tests include state transition, credit management, topology discovery, rouge mapper detection, sequence number management, generation number management, and performance and reliability tests.

Run Time: 1 day

Log File:

System Restart Required: No

Test Category:

Supported operating systems for Logo or Signature testing:

  • Windows 7

  • Windows Vista

Program:

Requirements

Software Requirements

The test tool requires the following software:

  • Supported operating system (see list above).

  • Software components included with the device that is being tested.

Hardware Requirements

  • Device to be tested

  • Computer that meets the minimum software requirements

  • Windows keyboard

  • Two-button pointing device

  • Color display monitor capable of at least 1024 by 768 resolution, 32-bits per pixel, 60 Hz

  • Hard drive with a minimum of 20 GB available on partition C:

Processor

  • x86

Running LLD2 Responder Verification Tests

To run this tool manually, do the following:

  1. Install the RawEther driver. You can find this driver under \nttest\NetTest\netxp\homenet\lld2\tools in the DTM controller's tests directory.

  2. In this same directory, run instrawether -i to install the driver.

  3. Next, run net start rawether from the command line as an administrator to start the driver.

  4. Copy veritool to a local directory to run it. You can find this tool in the \nttest\NetTest\netxp\veritool directory on the DTM controller.

You can run Veritool with the following options:

Usage: VeriTool [options] <responder address> <test id>

Options:

-v : verbose

-s : save trace

-e : enumerate the adapters

-a <adapter index> : specify the adapter to use

-t : list available tests

Note Using a wildcard character (*) for your test ID runs all working tests. If you use 1 for your test ID, all in the 1.x range will be run.

The test machine must have two network interface cards. One must be connected to the same network as the DTM controller and the other must be connected to a LAN port on the IGD.

Command Syntax

Command option Description

-v

Verbose

-s

Save the trace

-e

Enumerate adapters

-a <adapter index>

Specify the adapter to use

-t

List available tests

 

Cautions

If you have multiple responders that are connected to the IGD, errors might occur during testing. Also, if the responder is not directly connected to the IGD, the test might have failures because of packet loss on the intermediate device.

Troubleshooting

The LLD2 tests rely on the proper MAC address being entered for the device's wired LAN side. In DTM, this address is added properly when setting the IGD_Mac dimension in the router configuration job. If an LLD2 job stops responding (that is, "hangs"), and the Job Monitor window says "Scheduler" for the status, you likely do not have the LAN dimension set as True for the machines that are connected to the LAN side of the IGD.

If the tests are running, but you are getting failures, try to run the test manually. Also, try running a network analyzer to help understand what is going on with the LLTD traffic.

Code Tour

File Manifest

File Location

veritool.exe

nttest\NetTest\netxp\veritool

 

Test Assertions

The responder must make proper state transitions according to its current state and or the protocol event.

Test Assertion GUID: 588D5CA9-7650-4b3c-9BBE-7ECD0A7B82D7

Windows Logo Program: NETWORK-0071 Router, WLAN AP, or Wireless Router has properly formatted metadata for mandatory TLVs according to LLTD

Additional Information: The responder implements a state machine, which consists of five states: Quiescent, Hello Pending, Hello Sent, Command Loop, and Emitting State. The responder makes proper transition according to its current state or the protocol event.

The responder must properly manage its CTC values.

Test Assertion GUID: 512622DA-0B9E-4269-AC30-54AB9D308670

Windows Logo Program: NETWORK-0071 Router, WLAN AP, or Wireless Router has properly formatted metadata for mandatory TLVs according to LLTD

Additional Information: The responder maintains a record of the maximum packets and bytes of the frame that an Emit frame can request it to send. This record, which is called CTC in bytes and packets, is changed by Charge/Emit frames.

The LLTD responder must behave properly during topology discovery sessions.

Test Assertion GUID: BC49A296-98F9-46bc-9493-7CA744F7E7DD

Windows Logo Program: NETWORK-0071 Router, WLAN AP, or Wireless Router has properly formatted metadata for mandatory TLVs according to LLTD

Additional Information: The responder transmits Probe/Train frame when it receives the Emit frame and reports observed Probe frames when it receives the Query frame.

The responder must properly detect rogue mapping sessions.

Test Assertion GUID: 1F011CDB-33F2-4d4c-B4FA-0FE8DB44E9CD

Windows Logo Program: NETWORK-0071 Router, WLAN AP, or Wireless Router has properly formatted metadata for mandatory TLVs according to LLTD

Additional Information: The responder can attend only one mapper's discovery session. During its current session, it should transmit Hello frame to the rogue mapper if it detects.

The responder must properly keep track of sequence numbers.

Test Assertion GUID: 50DD834C-13E1-4394-943D-1BE5A6D26950

Windows Logo Program: NETWORK-0071 Router, WLAN AP, or Wireless Router has properly formatted metadata for mandatory TLVs according to LLTD

Additional Information: Some of the frames from the mapper, such as Charge, Emit and Query frame, carries sequence number. To provide acknowledging response and also allow simple error recovery, the responder keeps track of the sequence number.

The responder must properly keep track of its generation number.

Test Assertion GUID: A70690A8-535A-4338-BFEE-F4FDA91D9430

Windows Logo Program: NETWORK-0071 Router, WLAN AP, or Wireless Router has properly formatted metadata for mandatory TLVs according to LLTD

Additional Information: The responder should keep the previous session's generation number and update its current generation number when it receives updates in the Discover frame from the mapper.

The responder must be reliable and have adiquate performance to participate in mapping sessions.

Test Assertion GUID: D17D1A95-2897-41cf-93CF-D5D4B7678428

Windows Logo Program: NETWORK-0073 Router, WLAN AP, or Wireless Router has properly formatted metadata for mandatory TLVs according to LLTD

Additional Information: These tests seek to ensure that the responder not only meets the requirements of the protocol, but also the expectations of the user. Responders must be able to handle requests in a prompt manner even under load for extended periods of time.

 

 

Build date: 9/14/2012